diff --git a/raw/rel-18/23_series/23003/raw.md b/raw/rel-18/23_series/23003/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..147bdaca116d18505b76fe0cb774a506b608640f --- /dev/null +++ b/raw/rel-18/23_series/23003/raw.md @@ -0,0 +1,6936 @@ + + +# 3GPP TS 23.003 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in small capital letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in small capital letters. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | | +|------------|-----------------------------------------------------------------------------------------------------|----| +| 1 | Scope..... | 12 | +| 1.1 | References..... | 13 | +| 1.1.1 | Normative references..... | 13 | +| 1.1.2 | Informative references..... | 18 | +| 1.2 | Abbreviations..... | 18 | +| 1.3 | General comments to references..... | 19 | +| 1.4 | Conventions on bit ordering..... | 19 | +| 2 | Identification of mobile subscribers..... | 19 | +| 2.1 | General..... | 19 | +| 2.2 | Composition of IMSI..... | 20 | +| 2.2A | Subscription Permanent Identifier (SUPI)..... | 20 | +| 2.2B | Subscription Concealed Identifier (SUCI)..... | 20 | +| 2.3 | Allocation and assignment principles..... | 23 | +| 2.4 | Structure of TMSI..... | 24 | +| 2.5 | Structure of LMSI..... | 24 | +| 2.6 | Structure of TLLI..... | 24 | +| 2.7 | Structure of P-TMSI Signature..... | 25 | +| 2.8 | Globally Unique Temporary UE Identity (GUTI)..... | 25 | +| 2.8.1 | Introduction..... | 25 | +| 2.8.2 | Mapping between Temporary and Area Identities for the EUTRAN and the UTRAN/GERAN based systems..... | 26 | +| 2.8.2.0 | Introduction..... | 26 | +| 2.8.2.1 | Mapping from GUTI to RAI, P-TMSI and P-TMSI signature..... | 27 | +| 2.8.2.1.1 | Introduction..... | 27 | +| 2.8.2.1.2 | Mapping in the UE..... | 27 | +| 2.8.2.1.3 | Mapping in the old MME..... | 27 | +| 2.8.2.2 | Mapping from RAI and P-TMSI to GUTI..... | 28 | +| 2.8.2.2.1 | Introduction..... | 28 | +| 2.8.2.2.2 | Mapping in the UE..... | 28 | +| 2.8.2.2.3 | Mapping in the new MME..... | 28 | +| 2.9 | Structure of the S-Temporary Mobile Subscriber Identity (S-TMSI)..... | 29 | +| 2.10 | 5G Globally Unique Temporary UE Identity (5G-GUTI)..... | 29 | +| 2.10.1 | Introduction..... | 29 | +| 2.10.2 | Mapping between Temporary Identities for the 5GS and the E-UTRAN..... | 30 | +| 2.10.2.0 | Introduction..... | 30 | +| 2.10.2.1 | Mapping from 5G-GUTI to GUTI..... | 30 | +| 2.10.2.1.1 | Introduction..... | 30 | +| 2.10.2.1.2 | Mapping in the UE..... | 30 | +| 2.10.2.1.3 | Mapping in the old AMF..... | 30 | +| 2.10.2.2 | Mapping from GUTI to 5G-GUTI..... | 31 | +| 2.10.2.2.1 | Introduction..... | 31 | +| 2.10.2.2.2 | Mapping in the UE..... | 31 | +| 2.10.2.2.3 | Mapping in the new AMF..... | 31 | +| 2.11 | Structure of the 5G-S-Temporary Mobile Subscriber Identity (5G-S-TMSI)..... | 31 | +| 2.12 | Structure of the Truncated 5G-S-Temporary Mobile Subscriber Identity (Truncated 5G-S-TMSI)..... | 31 | +| 3 | Numbering plan for mobile stations..... | 32 | +| 3.1 | General..... | 32 | +| 3.2 | Numbering plan requirements..... | 32 | +| 3.3 | Structure of Mobile Subscriber ISDN number (MSISDN)..... | 33 | +| 3.4 | Mobile Station Roaming Number (MSRN) for PSTN/ISDN routeing..... | 34 | +| 3.5 | Structure of Mobile Station International Data Number..... | 34 | +| 3.6 | Handover Number..... | 34 | +| 3.7 | Structure of an IP v4 address..... | 34 | +| 3.8 | Structure of an IP v6 address..... | 34 | + +| | | | +|----------|-------------------------------------------------------------------------------------------------------------------|----| +| 4 | Identification of location areas and base stations..... | 35 | +| 4.1 | Composition of the Location Area Identification (LAI) ..... | 35 | +| 4.2 | Composition of the Routing Area Identification (RAI) ..... | 35 | +| 4.3 | Base station identification ..... | 35 | +| 4.3.1 | Cell Identity (CI) and Cell Global Identification (CGI) ..... | 35 | +| 4.3.2 | Base Station Identity Code (BSIC) ..... | 36 | +| 4.4 | Regional Subscription Zone Identity (RSZI) ..... | 37 | +| 4.5 | Location Number..... | 37 | +| 4.6 | Composition of the Service Area Identification (SAI)..... | 38 | +| 4.7 | Closed Subscriber Group ..... | 38 | +| 4.8 | HNB Name..... | 38 | +| 4.9 | CSG Type..... | 38 | +| 4.10 | HNB Unique Identity ..... | 38 | +| 4.11 | HRNN..... | 38 | +| 5 | Identification of MSCs, GSNs, location registers and CSSs ..... | 39 | +| 5.1 | Identification for routing purposes ..... | 39 | +| 5.2 | Identification of HLR for HLR restoration application ..... | 39 | +| 5.3 | Identification of the HSS for SMS ..... | 39 | +| 6 | International Mobile Station Equipment Identity, Software Version Number and Permanent Equipment Identifier ..... | 40 | +| 6.1 | General ..... | 40 | +| 6.2 | Composition of IMEI and IMEISV ..... | 40 | +| 6.2.1 | Composition of IMEI ..... | 40 | +| 6.2.2 | Composition of IMEISV ..... | 40 | +| 6.3 | Allocation principles ..... | 41 | +| 6.4 | Permanent Equipment Identifier (PEI)..... | 41 | +| 7 | Identification of Voice Group Call and Voice Broadcast Call Entities ..... | 42 | +| 7.1 | Group Identities..... | 42 | +| 7.2 | Group Call Area Identification..... | 42 | +| 7.3 | Voice Group Call and Voice Broadcast Call References..... | 42 | +| 8 | SCCP subsystem numbers ..... | 43 | +| 8.1 | Globally standardized subsystem numbers used for GSM/UMTS ..... | 43 | +| 8.2 | National network subsystem numbers used for GSM/UMTS..... | 43 | +| 9 | Definition of Access Point Name..... | 44 | +| 9A | Definition of Data Network Name..... | 44 | +| 9.0 | General ..... | 44 | +| 9.1 | Structure of APN..... | 44 | +| 9.1.1 | Format of APN Network Identifier ..... | 45 | +| 9.1.2 | Format of APN Operator Identifier ..... | 45 | +| 9.2 | Definition of the Wild Card APN ..... | 46 | +| 9.2.1 | Coding of the Wild Card APN ..... | 46 | +| 9.3 | Definition of Emergency APN..... | 46 | +| 10 | Identification of the Cordless Telephony System entities ..... | 46 | +| 10.1 | General description of CTS-MS and CTS-FP Identities..... | 46 | +| 10.2 | CTS Mobile Subscriber Identities ..... | 46 | +| 10.2.1 | General ..... | 46 | +| 10.2.2 | Composition of the CTSMSI..... | 47 | +| 10.2.3 | Allocation principles ..... | 47 | +| 10.2.4 | CTSMSI hexadecimal representation..... | 47 | +| 10.3 | Fixed Part Beacon Identity ..... | 47 | +| 10.3.1 | General ..... | 47 | +| 10.3.2 | Composition of the FPBI..... | 48 | +| 10.3.2.1 | FPBI general structure ..... | 48 | +| 10.3.2.2 | FPBI class A ..... | 48 | +| 10.3.2.3 | FPBI class B..... | 48 | +| 10.3.3 | Allocation principles ..... | 49 | +| 10.4 | International Fixed Part Equipment Identity ..... | 49 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------|----| +| 10.4.1 | General ..... | 49 | +| 10.4.2 | Composition of the IFPEI..... | 49 | +| 10.4.3 | Allocation and assignment principles..... | 50 | +| 10.5 | International Fixed Part Subscription Identity ..... | 50 | +| 10.5.1 | General ..... | 50 | +| 10.5.2 | Composition of the IFPSI..... | 50 | +| 10.5.3 | Allocation and assignment principles..... | 50 | +| 11 | Identification of Localised Service Area ..... | 51 | +| 12 | Identification of PLMN, RNC, Service Area, CN domain and Shared Network Area ..... | 51 | +| 12.1 | PLMN Identifier..... | 51 | +| 12.2 | CN Domain Identifier..... | 51 | +| 12.3 | CN Identifier ..... | 52 | +| 12.4 | RNC Identifier..... | 52 | +| 12.5 | Service Area Identifier ..... | 52 | +| 12.6 | Shared Network Area Identifier ..... | 52 | +| 12.7 | Stand-Alone Non-Public Network Identifier ..... | 53 | +| 12.7.1 | Network Identifier (NID) ..... | 53 | +| 12.7.2 | NID of assignment mode 0..... | 53 | +| 12.7.3 | Group ID for Network Selection (GIN) ..... | 54 | +| 13 | Numbering, addressing and identification within the IP multimedia core network subsystem..... | 54 | +| 13.1 | Introduction ..... | 54 | +| 13.2 | Home network domain name ..... | 54 | +| 13.3 | Private User Identity..... | 55 | +| 13.4 | Public User Identity..... | 56 | +| 13.4A | Wildcarded Public User Identity ..... | 56 | +| 13.4B | Temporary Public User Identity ..... | 57 | +| 13.5 | Public Service Identity (PSI)..... | 57 | +| 13.5A | Private Service Identity ..... | 58 | +| 13.6 | Anonymous User Identity ..... | 58 | +| 13.7 | Unavailable User Identity..... | 58 | +| 13.8 | Instance-ID ..... | 58 | +| 13.9 | XCAP Root URI..... | 59 | +| 13.9.1 | XCAP Root URI on Ut interface..... | 59 | +| 13.9.1.1 | General..... | 59 | +| 13.9.1.2 | Format of XCAP Root URI ..... | 59 | +| 13.10 | Default Conference Factory URI for MMTel ..... | 60 | +| 13.11 | Unknown User Identity ..... | 60 | +| 13.12 | Default WWSF URI..... | 60 | +| 13.12.1 | General ..... | 60 | +| 13.12.2 | Format of the Default WWSF URI ..... | 60 | +| 13.13 | IMEI based identity..... | 61 | +| 14 | Numbering, addressing and identification for 3GPP System to WLAN Interworking ..... | 61 | +| 14.1 | Introduction ..... | 61 | +| 14.2 | Home network realm..... | 61 | +| 14.3 | Root NAI..... | 62 | +| 14.4 | Decorated NAI ..... | 62 | +| 14.4A | Fast Re-authentication NAI..... | 63 | +| 14.5 | Temporary identities ..... | 63 | +| 14.6 | Alternative NAI..... | 64 | +| 14.7 | W-APN..... | 64 | +| 14.7.1 | Format of W-APN Network Identifier ..... | 64 | +| 14.7.2 | Format of W-APN Operator Identifier ..... | 65 | +| 14.7.3 | Alternative Format of W-APN Operator Identifier ..... | 65 | +| 14.8 | Emergency Realm and Emergency NAI for Emergency Cases..... | 66 | +| 15 | Identification of Multimedia Broadcast/Multicast Service ..... | 66 | +| 15.1 | Introduction ..... | 66 | +| 15.2 | Structure of TMGI..... | 67 | +| 15.3 | Structure of MBMS SAI ..... | 67 | +| 15.4 | Home Network Realm..... | 67 | + +| | | | +|------------|------------------------------------------------------------------------------------------------------|----| +| 15.5 | Addressing and identification for Bootstrapping MBMS Service Announcement..... | 68 | +| 16 | Numbering, addressing and identification within the GAA subsystem..... | 69 | +| 16.1 | Introduction ..... | 69 | +| 16.2 | BSF address..... | 69 | +| 17 | Numbering, addressing and identification within the Generic Access Network ..... | 70 | +| 17.1 | Introduction ..... | 70 | +| 17.2 | Network Access Identifiers ..... | 70 | +| 17.2.1 | Home network realm ..... | 70 | +| 17.2.2 | Full Authentication NAI..... | 70 | +| 17.2.3 | Fast Re-authentication NAI..... | 71 | +| 17.3 | Node Identifiers..... | 71 | +| 17.3.1 | Home network domain name..... | 71 | +| 17.3.2 | Provisioning GANC-SEGW identifier ..... | 72 | +| 17.3.3 | Provisioning GANC identifier..... | 72 | +| 18 | Addressing and Identification for IMS Service Continuity and Single-Radio Voice Call Continuity..... | 73 | +| 18.1 | Introduction ..... | 73 | +| 18.2 | CS Domain Routeing Number (CSRN) ..... | 73 | +| 18.3 | IP Multimedia Routeing Number (IMRN)..... | 73 | +| 18.4 | Session Transfer Number (STN)..... | 73 | +| 18.5 | Session Transfer Identifier (STI)..... | 73 | +| 18.6 | Session Transfer Number for Single Radio Voice Call Continuity (STN-SR)..... | 73 | +| 18.7 | Correlation MSISDN..... | 73 | +| 18.8 | Transfer Identifier for CS to PS Single Radio Voice Call Continuity (STI-rSR) ..... | 74 | +| 18.9 | Additional MSISDN..... | 74 | +| 19 | Numbering, addressing and identification for the Evolved Packet Core (EPC) ..... | 74 | +| 19.1 | Introduction ..... | 74 | +| 19.2 | Home Network Realm/Domain..... | 74 | +| 19.3 | 3GPP access to non-3GPP access interworking..... | 75 | +| 19.3.1 | Introduction ..... | 75 | +| 19.3.2 | Root NAI ..... | 75 | +| 19.3.3 | Decorated NAI..... | 76 | +| 19.3.4 | Fast Re-authentication NAI..... | 77 | +| 19.3.5 | Pseudonym Identities..... | 77 | +| 19.3.6 | Emergency NAI for Limited Service State..... | 78 | +| 19.3.7 | Alternative NAI ..... | 79 | +| 19.3.8 | Keyname NAI..... | 79 | +| 19.3.9 | IMSI-based Emergency NAI..... | 79 | +| 19.4 | Identifiers for Domain Name System procedures ..... | 79 | +| 19.4.1 | Introduction ..... | 79 | +| 19.4.2 | Fully Qualified Domain Names (FQDNs) ..... | 80 | +| 19.4.2.1 | General ..... | 80 | +| 19.4.2.2 | Access Point Name FQDN (APN-FQDN) ..... | 80 | +| 19.4.2.2.1 | Structure ..... | 80 | +| 19.4.2.2.2 | Void..... | 81 | +| 19.4.2.2.3 | Void..... | 81 | +| 19.4.2.2.4 | Void..... | 81 | +| 19.4.2.3 | Tracking Area Identity (TAI) ..... | 81 | +| 19.4.2.4 | Mobility Management Entity (MME)..... | 81 | +| 19.4.2.5 | Routing Area Identity (RAI) - EPC ..... | 82 | +| 19.4.2.6 | Serving GPRS Support Node (SGSN) within SGSN pool ..... | 82 | +| 19.4.2.7 | Target RNC-ID for U-TRAN ..... | 82 | +| 19.4.2.8 | DNS subdomain for operator usage in EPC ..... | 83 | +| 19.4.2.9 | ePDG FQDN and Visited Country FQDN for non-emergency bearer services ..... | 83 | +| 19.4.2.9.1 | General ..... | 83 | +| 19.4.2.9.2 | Operator Identifier based ePDG FQDN ..... | 83 | +| 19.4.2.9.3 | Tracking/Location Area Identity based ePDG FQDN ..... | 84 | +| 19.4.2.9.4 | Visited Country FQDN ..... | 85 | +| 19.4.2.9.5 | Replacement field used in DNS-based Discovery of regulatory requirements..... | 85 | + +| | | | +|-------------|------------------------------------------------------------------------------------------------------|-----| +| 19.4.2.9A | ePDG FQDN for emergency bearer services..... | 86 | +| 19.4.2.9A.1 | General ..... | 86 | +| 19.4.2.9A.2 | Operator Identifier based Emergency ePDG FQDN..... | 86 | +| 19.4.2.9A.3 | Tracking/Location Area Identity based Emergency ePDG FQDN..... | 86 | +| 19.4.2.9A.4 | Visited Country Emergency FQDN..... | 87 | +| 19.4.2.9A.5 | Replacement field used in DNS-based Discovery of regulatory requirements for emergency services..... | 87 | +| 19.4.2.9A.6 | Country based Emergency Numbers FQDN..... | 87 | +| 19.4.2.9A.7 | Replacement field used in DNS-based Discovery of Emergency Numbers ..... | 88 | +| 19.4.2.10 | Global eNodeB-ID for eNodeB ..... | 88 | +| 19.4.2.11 | Local Home Network identifier..... | 88 | +| 19.4.2.12 | UCMF ..... | 89 | +| 19.4.2.13 | PGW Set FQDN..... | 89 | +| 19.4.3 | Service and Protocol service names for 3GPP ..... | 89 | +| 19.5 | Access Network Identity ..... | 91 | +| 19.6 | E-UTRAN Cell Identity (ECI) and E-UTRAN Cell Global Identification (ECGI)..... | 91 | +| 19.6A | NR Cell Identity (NCI) and NR Cell Global Identity (NCGI)..... | 91 | +| 19.7 | Identifiers for communications with packet data networks and applications ..... | 92 | +| 19.7.1 | Introduction ..... | 92 | +| 19.7.2 | External Identifier..... | 92 | +| 19.7.3 | External Group Identifier ..... | 92 | +| 19.8 | TWAN Operator Name..... | 93 | +| 19.9 | IMSI-Group Identifier..... | 93 | +| 19.10 | Presence Reporting Area Identifier (PRA ID) ..... | 94 | +| 19.11 | Dedicated Core Networks Identifier ..... | 94 | +| 20 | Addressing and Identification for IMS Centralized Services ..... | 94 | +| 20.1 | Introduction ..... | 94 | +| 20.2 | UE based solution..... | 94 | +| 20.3 | Network based solution..... | 95 | +| 20.3.1 | General ..... | 95 | +| 20.3.2 | Home network domain name..... | 95 | +| 20.3.3 | Private User Identity ..... | 95 | +| 20.3.4 | Public User Identity ..... | 95 | +| 20.3.5 | Conference Factory URI..... | 96 | +| 21 | Addressing and Identification for Dual Stack Mobile IPv6 (DSMIPv6)..... | 96 | +| 21.1 | Introduction ..... | 96 | +| 21.2 | Home Agent – Access Point Name (HA-APN) ..... | 96 | +| 21.2.1 | General ..... | 96 | +| 21.2.2 | Format of HA-APN Network Identifier ..... | 96 | +| 21.2.3 | Format of HA-APN Operator Identifier ..... | 97 | +| 22 | Addressing and identification for ANDSF..... | 97 | +| 22.1 | Introduction ..... | 97 | +| 22.2 | ANDSF Server Name (ANDSF-SN)..... | 97 | +| 22.2.1 | General ..... | 97 | +| 22.2.2 | Format of ANDSF-SN..... | 98 | +| 23 | Numbering, addressing and identification for the OAM System..... | 98 | +| 23.1 | Introduction ..... | 98 | +| 23.2 | OAM System Realm/Domain ..... | 98 | +| 23.3 | Identifiers for Domain Name System procedures ..... | 99 | +| 23.3.1 | Introduction ..... | 99 | +| 23.3.2 | Fully Qualified Domain Names (FQDNs) ..... | 99 | +| 23.3.2.1 | General..... | 99 | +| 23.3.2.2 | Relay Node Vendor-Specific OAM System..... | 99 | +| 23.3.2.3 | Multi-vendor eNodeB Plug-and Play Vendor-Specific OAM System..... | 100 | +| 23.3.2.3.1 | General ..... | 100 | +| 23.3.2.3.2 | Certification Authority server ..... | 100 | +| 23.3.2.3.3 | Security Gateway ..... | 100 | +| 23.3.2.3.4 | Element Manager ..... | 101 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------|-----| +| 24 | Numbering, addressing and identification for Proximity-based Services (ProSe) ..... | 101 | +| 24.1 | Introduction ..... | 101 | +| 24.2 | ProSe Application ID ..... | 101 | +| 24.2.1 | General ..... | 101 | +| 24.2.2 | Format of ProSe Application ID Name in ProSe Application ID ..... | 102 | +| 24.2.3 | Format of PLMN ID in ProSe Application ID ..... | 102 | +| 24.2.4 | Usage of wild cards in place of PLMN ID in ProSe Application ID ..... | 102 | +| 24.2.5 | Informative examples of ProSe Application ID ..... | 103 | +| 24.3 | ProSe Application Code ..... | 103 | +| 24.3.1 | General ..... | 103 | +| 24.3.2 | Format of PLMN ID in ProSe Application Code ..... | 103 | +| 24.3.3 | Format of temporary identity in ProSe Application Code ..... | 104 | +| 24.3A | ProSe Application Code Prefix ..... | 104 | +| 24.3B | ProSe Application Code Suffix ..... | 104 | +| 24.4 | EPC ProSe User ID ..... | 104 | +| 24.4.1 | General ..... | 104 | +| 24.4.2 | Format of EPC ProSe User ID ..... | 105 | +| 24.5 | Home PLMN ProSe Function Address ..... | 105 | +| 24.6 | ProSe Restricted Code ..... | 105 | +| 24.7 | ProSe Restricted Code Prefix ..... | 105 | +| 24.8 | ProSe Restricted Code Suffix ..... | 105 | +| 24.9 | ProSe Query Code ..... | 106 | +| 24.10 | ProSe Response Code ..... | 106 | +| 24.11 | ProSe Discovery UE ID ..... | 106 | +| 24.11.1 | General ..... | 106 | +| 24.11.2 | Format of ProSe Discovery UE ID ..... | 106 | +| 24.12 | ProSe UE ID ..... | 106 | +| 24.13 | ProSe Relay UE ID ..... | 106 | +| 24.14 | User Info ID ..... | 107 | +| 24.15 | Relay Service Code ..... | 107 | +| 24.16 | Discovery Group ID ..... | 107 | +| 24.17 | Service ID ..... | 107 | +| 25 | Identification of Online Charging System ..... | 107 | +| 25.1 | Introduction ..... | 107 | +| 25.2 | Home network domain name ..... | 107 | +| 26 | Numbering, addressing and identification for Mission Critical Services ..... | 108 | +| 26.1 | Introduction ..... | 108 | +| 26.2 | Domain name for MC services confidentiality protection of MC services identities ..... | 108 | +| 27 | Numbering, addressing and identification for V2X ..... | 108 | +| 27.1 | Introduction ..... | 108 | +| 27.2 | V2X Control Function FQDN ..... | 109 | +| 27.2.1 | General ..... | 109 | +| 27.2.2 | Format of V2X Control Function FQDN ..... | 109 | +| 28 | Numbering, addressing and identification for 5G System (5GS) ..... | 109 | +| 28.1 | Introduction ..... | 109 | +| 28.2 | Home Network Domain ..... | 109 | +| 28.3 | Identifiers for Domain Name System procedures ..... | 110 | +| 28.3.1 | Introduction ..... | 110 | +| 28.3.2 | Fully Qualified Domain Names (FQDNs) ..... | 110 | +| 28.3.2.1 | General ..... | 110 | +| 28.3.2.2 | N3IWF FQDN ..... | 110 | +| 28.3.2.2.1 | General ..... | 110 | +| 28.3.2.2.2 | Operator Identifier based N3IWF FQDN ..... | 111 | +| 28.3.2.2.3 | Tracking Area Identity based N3IWF FQDN ..... | 111 | +| 28.3.2.2.4 | Visited Country FQDN for N3IWF ..... | 112 | +| 28.3.2.2.5 | Replacement field used in DNS-based Discovery of regulatory requirements ..... | 113 | +| 28.3.2.2.6 | FQDN for SNPN N3IWF ..... | 114 | +| 28.3.2.2.7 | Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements ..... | 116 | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-----| +| 28.3.2.2.8 | Prefixed Operator Identifier based N3IWF FQDN ..... | 117 | +| 28.3.2.2.9 | Prefixed Tracking Area Identity based N3IWF FQDN ..... | 117 | +| 28.3.2.3 | PLMN level and Home NF Repository Function (NRF) FQDN ..... | 118 | +| 28.3.2.3.1 | General ..... | 118 | +| 28.3.2.3.2 | Format of NRF FQDN ..... | 118 | +| 28.3.2.3.3 | NRF URI ..... | 118 | +| 28.3.2.4 | Network Slice Selection Function (NSSF) FQDN ..... | 119 | +| 28.3.2.4.1 | General ..... | 119 | +| 28.3.2.4.2 | Format of NSSF FQDN ..... | 119 | +| 28.3.2.4.3 | NSSF URI ..... | 119 | +| 28.3.2.5 | AMF Name ..... | 119 | +| 28.3.2.6 | 5GS Tracking Area Identity (TAI) FQDN ..... | 120 | +| 28.3.2.7 | AMF Set FQDN ..... | 120 | +| 28.3.2.8 | AMF Instance FQDN ..... | 121 | +| 28.3.2.9 | SMF Set FQDN ..... | 122 | +| 28.3.2.10 | Short Message Service Function (SMSF) FQDN ..... | 122 | +| 28.3.2.11 | 5G DDNMF FQDN ..... | 122 | +| 28.4 | Information for Network Slicing ..... | 123 | +| 28.4.1 | General ..... | 123 | +| 28.4.2 | Format of the S-NSSAI ..... | 123 | +| 28.4.3 | Ranges of S-NSSAIs ..... | 123 | +| 28.4.4 | Network Slice Instance Identifier (NSI ID) ..... | 124 | +| 28.4.5 | Network Slice Admission Control (NSAC) Service Area Identifier (SAI) ..... | 124 | +| 28.5 | NF FQDN Format for Inter PLMN Routing ..... | 124 | +| 28.5.1 | General ..... | 124 | +| 28.5.2 | Telescopic FQDN ..... | 124 | +| 28.6 | 5GS Tracking Area Identity (TAI) ..... | 124 | +| 28.7 | Network Access Identifier (NAI) ..... | 125 | +| 28.7.1 | Introduction ..... | 125 | +| 28.7.2 | NAI format for SUPI ..... | 125 | +| 28.7.3 | NAI format for SUCI ..... | 125 | +| 28.7.4 | Emergency NAI for Limited Service State ..... | 127 | +| 28.7.5 | Alternative NAI ..... | 127 | +| 28.7.6 | NAI used for 5G registration via trusted non-3GPP access ..... | 127 | +| 28.7.7 | NAI used by N5CW devices via trusted non-3GPP access ..... | 128 | +| 28.7.7.0 | General ..... | 128 | +| 28.7.7.1 | Decorated NAI used for N5CW devices via trusted non-3GPP access ..... | 129 | +| 28.7.7.2 | Decorated NAI used for N5CW devices via trusted non-3GPP access for SNPn ..... | 129 | +| where the <5G_device_unique_identity> is to identify the N5CW device as defined in clause 28.7.7.0, the
shall be encoded as hexadecimal digits as specified in clause 12.7, and the
and are used to identify the PLMN based credentials holder. 28.7.8NAI format for 5G-GUTI | | | +| 28.7.9 | Decorated NAI format for SUCI ..... | 130 | +| 28.7.9.1 | General ..... | 130 | +| 28.7.9.2 | Decorated NAI used for 5G NSWO ..... | 131 | +| 28.7.10 | NAI format for UP-PRUK ID ..... | 132 | +| 28.7.11 | NAI format for CP-PRUK ID ..... | 132 | +| 28.7.12 | NAI used for 5G NSWO ..... | 132 | +| 28.8 | Generic Public Subscription Identifier (GPSI) ..... | 133 | +| 28.9 | Internal-Group Identifier ..... | 133 | +| 28.10 | Presence Reporting Area Identifier (PRA ID) ..... | 133 | +| 28.11 | CAG-Identifier ..... | 133 | +| 28.12 | NF Set Identifier (NF Set ID) ..... | 134 | +| 28.13 | NF Service Set Identifier (NF Service Set ID) ..... | 135 | +| 28.14 | Data Network Access Identifier (DNAI) ..... | 136 | +| 28.15 | Global Cable Identifier (GCI) ..... | 136 | +| 28.15.1 | Introduction ..... | 136 | +| 28.15.2 | NAI format for SUPI containing a GCI ..... | 136 | +| 28.15.3 | User Location Information for RG accessing the 5GC via W-5GCAN (HFC Node ID) ..... | 136 | +| 28.15.4 | GCI ..... | 136 | +| 28.15.5 | NAI format for SUCI containing a GCI ..... | 136 | +| 28.16 | Global Line Identifier (GLI) ..... | 137 | +| 28.16.1 | Introduction ..... | 137 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------|------------| +| 28.16.2 | NAI format for SUPI containing a GLI..... | 137 | +| 28.16.3 | User Location Information for RG accessing the 5GC via W-5GBAN..... | 137 | +| 28.16.4 | GLI ..... | 137 | +| 28.16.5 | NAI format for SUCI containing a GLI ..... | 137 | +| 28.17 | DNS subdomain for operator usage in 5GC..... | 138 | +| 28.18 | NF FQDN Format for Inter SNPN Routing ..... | 138 | +| 28.18.1 | General ..... | 138 | +| 29 | Numbering, addressing and identification for RACS ..... | 138 | +| 29.1 | Introduction ..... | 138 | +| 29.2 | UE radio capability ID ..... | 138 | +| 30 | Identification of 5GS Multicast and Broadcast Services ..... | 139 | +| 30.1 | Introduction ..... | 139 | +| 30.2 | Structure of TMGI..... | 139 | +| 30.3 | Structure of Area Session ID..... | 140 | +| 30.4 | Structure of MBS Frequency Selection Area ID..... | 140 | +| 30.5 | Structure of Associated Session ID..... | 140 | +| Annex A (informative): | Colour Codes ..... | 141 | +| A.1 | Utilization of the BSIC ..... | 141 | +| A.2 | Guidance for planning..... | 141 | +| A.3 | Example of PLMN Colour Codes (NCCs) for the European region ..... | 142 | +| Annex B (normative): | IMEI Check Digit computation ..... | 143 | +| B.1 | Representation of IMEI..... | 143 | +| B.2 | Computation of CD for an IMEI..... | 143 | +| B.3 | Example of computation ..... | 143 | +| Annex C (normative): | Naming convention..... | 145 | +| C.1 | Routing Area Identities ..... | 145 | +| C.2 | GPRS Support Nodes..... | 146 | +| C.3 | Target ID..... | 146 | +| Annex D (informative): | Applicability and use of the ".3gppnetwork.org" domain name ..... | 147 | +| Annex E (normative): | Procedure for sub-domain allocation ..... | 148 | +| Annex F (informative): | Change history..... | 150 | + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document +- might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +--- + +## 1 Scope + +The present document defines the principal purpose and use of different naming, numbering, addressing and identification resources (i.e. Identifiers (ID)) within the digital cellular telecommunications system and the 3GPP system. + +IDs that are covered by this specification includes both public IDs, private IDs and IDs that are assigned to MSs/UEs. Many of the IDs are used temporary in the networks and are allocated and assigned by the operators and some other IDs are allocated and assigned on either global, regional and national level by an administrator. See ITU-T Recommendation E.101 [122]. + +NOTE: Allocation means the process of opening a numbering, naming or addressing resource in a plan for the purpose of its use by a telecommunication service under specified conditions. The allocation in itself does not yet give rights for any user, whether an operator, service provider, user or someone else, to use the resource. Assignment means authorization given to an applicant for the right of use of number, naming or addressing resources under specified conditions. + +The present document defines: + +- 0) the principal purpose and use of International Mobile station Equipment Identities (IMEI) within the digital cellular telecommunications system and the 3GPP system +- a) an identification plan for public networks and subscriptions in the 3GPP systems; +- b) principles of assigning telephone numbers to MSs in the country of registration of the MS; +- c) principles of assigning Mobile Station (MS) roaming numbers to visiting MSs; +- d) an identification plan for location areas, routing areas, and base stations in the GSM system; +- e) an identification plan for MSCs, SGSNs, GGSNs, and location registers in the GSM/UMTS system; +- f) principles of assigning international mobile equipment identities; +- g) principles of assigning zones for regional subscription; +- h) an identification plan for groups of subscribers to the Voice Group Call Service (VGCS) and to the Voice Broadcast Service (VBS); and identification plan for voice group calls and voice broadcast calls; an identification plan for group call areas; +- i) principles for assigning Packet Data Protocol (PDP) addresses to mobile stations; +- j) an identification plan for point-to-multipoint data transmission groups; +- k) an identification plan for CN domain, RNC and service area in the UTRAN system. +- l) an identification plan for mobile subscribers in the WLAN system. +- m) addressing and identification for IMS Service Continuity +- n) an identification plan together with principles of assignment and mapping of identities for the Evolved Packet System; and +- o) addressing and identification for Proximity-based (ProSe) Services. +- p) an identification for Online Charging System (OCS). + +- q) an identification plan together with principles of assignment and mapping of identities for the 5G System. + +The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. + +## 1.1 References + +### 1.1.1 Normative references + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications ". +- [2] 3GPP TS 23.008: "Organization of subscriber data". +- [3] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2" +- [4] 3GPP TS 23.070: "Routeing of calls to/from Public Data Networks (PDN)". +- [5] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". +- [6] 3GPP TS 29.060: "GPRS Tunnelling protocol (GTP) across the Gn and Gp interface". +- [7] 3GPP TS 43.020: "Digital cellular telecommunications system (Phase 2+); Security related network functions". +- [8] void +- [9] 3GPP TS 51.011: " Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". +- [10] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [11] ITU-T Recommendation E.212: "The international identification plan for public networks and subscriptions ". +- [12] ITU-T Recommendation E.213: "Telephone and ISDN numbering plan for land Mobile Stations in public land mobile networks (PLMN)". +- [13] ITU-T Recommendation X.121: "International numbering plan for public data networks". +- [14] IETF RFC 791: "Internet Protocol". +- [15] IETF RFC 2373: "IP Version 6 Addressing Architecture". +- [16] 3GPP TS 25.401: "UTRAN Overall Description". +- [17] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". +- [18] IETF RFC 2181: "Clarifications to the DNS Specification". +- [19] IETF RFC 1035: "Domain Names - Implementation and Specification". +- [20] IETF RFC 1123: "Requirements for Internet Hosts -- Application and Support". + +- [21] IETF RFC 2462: "IPv6 Stateless Address Autoconfiguration". +- [22] IETF RFC 3041: "Privacy Extensions for Stateless Address Autoconfiguration in IPv6". +- [23] 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes". +- [24] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem – Stage 2" +- [25] Void +- [26] IETF RFC 3261: "SIP: Session Initiation Protocol" +- [27] 3GPP TS 31.102: "Characteristics of the USIM Application." +- [28] Void +- [29] 3GPP TS 44.118: "Radio Resource Control (RRC) Protocol, Iu Mode". +- [30] Void +- [31] 3GPP TS 29.002: "Mobile Application Part (MAP) specification" +- [32] 3GPP TS 22.016: "International Mobile Equipment Identities (IMEI)" +- [33] Void +- [34] Void +- [35] 3GPP TS 45.056: "CTS-FP Radio Sub-system" +- [36] 3GPP TS 42.009: "Security aspects" +- [37] 3GPP TS 25.423: "UTRAN Iur interface RNSAP signalling" +- [38] 3GPP TS 25.419: "UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP)" +- [39] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles" +- [40] ISO/IEC 7812: "Identification cards - Numbering system and registration procedure for issuer identifiers" +- [41] Void +- [42] 3GPP TS 33.102 "3G security; Security architecture" +- [43] 3GPP TS 43.130: "Iur-g interface; Stage 2" +- [45] IETF RFC 3966: "The tel URI for Telephone Numbers" +- [46] 3GPP TS 44.068: "Group Call Control (GCC) protocol". +- [47] 3GPP TS 44.069: "Broadcast Call Control (BCC) Protocol ". +- [48] 3GPP TS 24.234 Release 12: "3GPP System to WLAN Interworking; UE to Network protocols; Stage 3". +- [49] Void +- [50] IETF RFC 4187: "EAP AKA Authentication". +- [51] IETF RFC 4186: "EAP SIM Authentication". +- [52] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description" +- [53] IETF RFC 4282: "The Network Access Identifier". +- [54] IETF RFC 2279: "UTF-8, a transformation format of ISO 10646". + +- [55] 3GPP TS 33.234 Release 12: "Wireless Local Area Network (WLAN) interworking security". +- [56] Void +- [58] 3GPP TS 33.221 "Generic Authentication Architecture (GAA); Support for Subscriber Certificates". +- [60] IEEE 1003.1-2004, Part 1: Base Definitions +- [61] 3GPP TS 43.318: "Generic Access to the A/Gb interface; Stage 2" +- [62] 3GPP TS 44.318: "Generic Access (GA) to the A/Gb interface; Mobile GA interface layer 3 specification" +- [63] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks" +- [64] IETF RFC 2606: "Reserved Top Level DNS Names" +- [65] Void +- [66] 3GPP TS 51.011 Release 4: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface" +- [67] 3GPP2 X.S0013-004: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3" +- [68] 3GPP TS 23.402: "Architecture Enhancements for non-3GPP accesses" +- [69] 3GPP TS 33.402: "3GPP System Architecture Evolution: Security Aspects of non-3GPP accesses" +- [70] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2" +- [71] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity" +- [72] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" +- [73] 3GPP TS 29.303: "Domain Name System Procedures; Stage 3" +- [74] IETF RFC 3958: "Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)" +- [75] Void +- [76] 3GPP TS 23.237: "Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems" +- [77] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3" +- [78] 3GPP TS 29.273: "Evolved Packet System; 3GPP EPS AAA Interfaces" +- [79] IETF RFC 7254: "A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)". +- [80] IETF RFC 4122: "A Universally Unique Identifier (UUID) URN Namespace". +- [81] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [82] IETF RFC5448: "Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA') " +- [83] 3GPP TS 22.011: "Service accessibility". +- [84] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN) ; S1 Application Protocol (S1AP)". + +- [85] Guidelines for use of a 48-bit Extended Unique Identifier (EUI-48™), +- [86] GUIDELINES FOR 64-BIT GLOBAL IDENTIFIER (EUI-64) REGISTRATION AUTHORITY, +- [87] The Broadband Forum TR-069: "CPE WAN Management Protocol v1.1", Issue 1 Amendment 2, December 2007 +- [88] 3GPP TS 29.274: "Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3". +- [89] 3GPP TS 33.401: "3GPP System Architecture Evolution: Security Architecture". +- [90] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [91] 3GPP TS 36.300: " Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [92] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC)". +- [93] 3GPP TS 31.103: "IP Multimedia Services Identity Module (ISIM) application". +- [94] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)". +- [95] 3GPP TS 29.229: " Cx and Dx interfaces based on the Diameter protocol; Protocol details". +- [96] 3GPP TS 29.329: " Sh Interface based on the Diameter protocol; Protocol details". +- [97] 3GPP TS 29.165: "Inter-IMS Network to Network Interface (NNI); Stage 3". +- [98] 3GPP TS 23.682: "Architecture Enhancements to facilitate communications with Packet Data Networks and Applications". +- [99] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". +- [100] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) – Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol". +- [101] 3GPP TS 23.251: "Network Sharing; Architecture and functional description". +- [102] 3GPP TS 32.508: "Procedure flows for multi-vendor plug-and-play eNB connection to the network". +- [103] 3GPP TS 23.303: "Proximity-based services (ProSe)". +- [104] IETF RFC 7255: "Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance ID". +- [105] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". +- [106] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [107] 3GPP TS 23.203: "Policy and charging control architecture". +- [108] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [110] Void. +- [111] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification". +- [112] 3GPP TS 43.064: "General Packet Radio Service (GPRS); Overall description of the GPRS Radio Interface; Stage 2". + +- [113] IETF RFC 6696: "EAP Extensions for the EAP Re-authentication Protocol (ERP)". +- [114] 3GPP TS 23.280: "Common functional architecture to support mission critical services". +- [115] 3GPP TS 24.281: "Mission Critical Video (MCVideo) signalling control; Protocol specification". +- [116] 3GPP TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification". +- [117] 3GPP TS 23.285: "Architecture enhancements for V2X services". +- [118] 3GPP TS 24.116: "Stage 3 aspects of system architecture enhancements for TV services". +- [119] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [120] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [121] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [122] ITU-T Recommendation E.101: "Definitions of terms used for identifiers (names, numbers, addresses and other identifiers) for public telecommunication services and networks in the E-series Recommendations". +- [123] 3GPP TS 38.413: "NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP)". +- [124] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [125] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); stage 3". +- [126] IETF RFC 7542: "The Network Access Identifier". +- [127] IETF RFC 2818: "HTTP over TLS". +- [128] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". +- [129] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [130] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [131] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS); Stage 2". +- [132] IETF RFC 7042: "IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters". +- [133] BBF WT-470: "5G FMC Architecture". +- [134] CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture". +- [135] CableLabs DOCSIS MULPI: "Data-Over-Cable Service Interface Specifications DOCSIS 3.1, MAC and Upper Layer Protocols Interface Specification". +- [136] IEEE "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)", +- [137] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification" +- [138] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification". +- [139] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [140] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services". +- [141] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". + +- [142] 3GPP TS 33.503: "Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS)". +- [143] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS); Stage 2". +- [144] 3GPP TS 24.526: "UE policies for 5G System (5GS); Stage 3". + +### 1.1.2 Informative references + +- [44] Void +- [57] GSMA PRD IR.34 "Inter-PLMN Backbone Guidelines" +- [59] Void +- [109] GSMA TS.06 "IMEI Allocation and Approval Process" + + +## 1.2 Abbreviations + +For the purposes of the present document, the abbreviations defined in 3GPP TS 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-----------|------------------------------------------------------------| +| 5G-BRG | 5G Broadband Residential Gateway | +| 5G-CRG | 5G Cable Residential Gateway | +| 5G-GUTI | 5G Globally Unique Temporary Identifier | +| 5G NSWO | 5G Non-Seamless WLAN offload | +| 5G-RG | 5G Residential Gateway | +| 5GS | 5G System | +| 5G-S-TMSI | 5G S-Temporary Mobile Subscription Identifier | +| AMF | Access and Mobility Management Function | +| CP-PRUK | Control Plane Prose Remote User Key | +| EPS | Evolved Packet System | +| ER | EAP Re-authentication | +| ERP | EAP Re-authentication Protocol | +| FN-BRG | Fixed Network Broadband Residential Gateway | +| FN-CRG | Fixed Network Cable RGGUAMI Globally Unique AMF Identifier | +| FN-RG | Fixed Network RG | +| GUTI | Globally Unique Temporary UE Identity | +| GCI | Global Cable Identifier | +| GLI | Global Line Identifier | +| GUTI | Globally Unique Temporary UE Identity | +| HFC | Hybrid Fiber Coax | +| HRNN | Human Readable Network Name | +| ICS | IMS Centralized Services | +| MTC | Machine Type Communication | +| N5CW | Non 5G Capable over WLAN | +| NCGI | NR Cell Global Identity | +| NCI | NR Cell Identity | +| NSI | Network Specific Identifier | +| OCS | Online Charging System | +| PEI | Permanent Equipment Identifier | +| RACS | Radio Capability Signalling Optimisation | +| RG | Residential Gateway | +| SNPN | Stand-alone Non-Public Network | +| SUCI | Subscription Concealed Identifier | +| SUPI | Subscription Permanent Identifier | +| TWAP | Trusted WLAN AAA Proxy | +| UP-PRUK | User Plane ProSe Remote User Key | +| UUID | Universally Unique Identifier | +| V2X | Vehicle-to-Everything | + +| | | +|---------|----------------------------------| +| W-5GAN | Wireline 5G Access Network | +| W-5GCAN | Wireline 5G Cable Access Network | +| W-5GBAN | Wireline BBF Access Network | +| WebRTC | Web Real-Time Communication | +| WLAN | Wireless Local Area Network | +| WWSF | WebRTC Web Server Function | + +## 1.3 General comments to references + +The identification plan for public networks and subscriptions defined below is that defined in ITU-T Recommendation E.212. + +The ISDN numbering plan for MSs and the allocation of mobile station roaming numbers is that defined in ITU-T Recommendation E.213. Only one of the principles for allocating ISDN numbers is proposed for PLMNs. Only the method for allocating MS roaming numbers contained in the main text of ITU-T Recommendation E.213 is recommended for use in PLMNs. If there is any difference between the present document and the ITU-T Recommendations, the former shall prevail. + +For terminology, see also ITU-T Recommendations E.101, E.164 and X.121. + +## 1.4 Conventions on bit ordering + +The following conventions hold for the coding of the different identities appearing in the present document and in other GSM Technical Specifications if not indicated otherwise: + +- the different parts of an identity are shown in the figures in order of significance; +- the most significant part of an identity is on the left part of the figure and the least significant on the right. + +When an identity appears in other Technical Specifications, the following conventions hold if not indicated otherwise: + +- digits are numbered by order of significance, with digit 1 being the most significant; +- bits are numbered by order of significance, with the lowest bit number corresponding to the least significant bit. + +# 2 Identification of mobile subscribers + +## 2.1 General + +A unique International Mobile Subscription Identity (IMSI) shall be allocated to each mobile subscriber in the GSM/UMTS/EPS system. + +NOTE: This IMSI is the concept referred to by ITU-T as "International Mobile Subscription Identity". + +In order to support the subscriber identity confidentiality service the VLRs, SGSNs and MME may allocate Temporary Mobile Subscriber Identities (TMSI) to visiting mobile subscribers. The VLR, SGSN and MME must be capable of correlating an allocated TMSI with the IMSI of the MS to which it is allocated. + +An MS may be allocated three TMSIs, one for services provided through the MSC, one for services provided through the SGSN (P-TMSI for short) and one for the services provided via the MME (M-TMSI part GUTI for short). + +For addressing on resources used for GPRS, a Temporary Logical Link Identity (TLLI) is used. The TLLI to use is built by the MS either on the basis of the P-TMSI (local or foreign TLLI), or directly (random TLLI). + +In order to speed up the search for subscriber data in the VLR a supplementary Local Mobile Station Identity (LMSI) is defined. + +The LMSI may be allocated by the VLR at location updating and is sent to the HLR together with the IMSI. The HLR makes no use of it but includes it together with the IMSI in all messages sent to the VLR concerning that MS. + +## 2.2 Composition of IMSI + +IMSI is composed as shown in figure 1. + +![Figure 1: Structure of IMSI. The diagram shows the IMSI as a sequence of three parts: MCC (3 digits), MNC (2 or 3 digits), and MSIN. The total length of the IMSI is not more than 15 digits.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +The diagram illustrates the structure of an IMSI. It is enclosed in a rectangular box. At the top, a double-headed arrow spans the entire width, labeled "Not more than 15 digits". Below this, the IMSI is shown as a sequence of three parts: "MCC" (Mobile Country Code), "MNC" (Mobile Network Code), and "MSIN" (Mobile Subscriber Identification Number). Above the "MCC" part, a double-headed arrow indicates it consists of "3 digits". Above the "MNC" part, a double-headed arrow indicates it consists of "2 or 3" digits. Below the "MSIN" part, a double-headed arrow spans the entire width, labeled "IMSI". + +Figure 1: Structure of IMSI. The diagram shows the IMSI as a sequence of three parts: MCC (3 digits), MNC (2 or 3 digits), and MSIN. The total length of the IMSI is not more than 15 digits. + +**Figure 1: Structure of IMSI** + +IMSI is composed of three parts: + +- 1) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the mobile subscription; +- 2) Mobile Network Code (MNC) consisting of two or three digits for 3GPP network applications. The MNC identifies the home PLMN of the mobile subscription within its country of domicile, or it identifies together with MCC and NID the mobile subscription's SNPN. The length of the MNC (two or three digits) depends on the value of the MCC. A mixture of two and three digit MNC codes within a single MCC area is not recommended and is outside the scope of this specification. +- 3) Mobile Subscriber Identification Number (MSIN) identifying the mobile subscription within a PLMN or SNPN. + +### 2.2A Subscription Permanent Identifier (SUPI) + +The SUPI is a globally unique 5G Subscription Permanent Identifier allocated to each subscriber in the 5G System. It is defined in clause 5.9.2 of 3GPP TS 23.501 [119]. + +The SUPI is defined as: + +- a SUPI type: in this release of the specification, it may indicate an IMSI, a Network Specific Identifier (NSI), a Global Line Identifier (GLI) or a Global Cable Identifier (GCI); and +- dependent on the value of the SUPI type: + - an IMSI as defined in clause 2.1; + - a Network Specific Identifier (NSI), taking the form of a Network Access Identifier (NAI) as defined in clause 28.7.2; + - a Global Cable Identifier (GCI) taking the form of a NAI as defined in clause 28.15.2; + - a Global Line Identifier (GLI) taking the form of an NAI as defined in clause 28.16.2. + +NOTE: Depending on the protocol used to convey the SUPI, the SUPI type can take different formats. + +See clauses 4.7.2, 4.7.3 and 4.7.4 of 3GPP TS 23.316 [131] for details on which types of SUPI are supported by 5G-BRG, FN-BRG, 5G-CRG and FN-CRG. + +### 2.2B Subscription Concealed Identifier (SUCI) + +The SUCI is a privacy preserving identifier containing the concealed SUPI. It is defined in clause 6.12.2 of 3GPP TS 33.501 [124]. + +![Figure 2.2B-1: Structure of SUCI. The diagram shows the SUCI (Subscription Concealed Identifier) as a sequence of six fields. From left to right: 1. SUPI Type (value in range 0-7), 2. Home Network Identifier (format dependent on SUPI type), 3. Routing Indicator (1-4 digits), 4. Protection Scheme Id (value in range 0-15), 5. Home Network Public Key Id (value in range 0-255), and 6. Scheme Output (format dependent on protection scheme). Each field is represented by a box with a double-headed arrow below it indicating its range or format.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) + +Figure 2.2B-1: Structure of SUCI. The diagram shows the SUCI (Subscription Concealed Identifier) as a sequence of six fields. From left to right: 1. SUPI Type (value in range 0-7), 2. Home Network Identifier (format dependent on SUPI type), 3. Routing Indicator (1-4 digits), 4. Protection Scheme Id (value in range 0-15), 5. Home Network Public Key Id (value in range 0-255), and 6. Scheme Output (format dependent on protection scheme). Each field is represented by a box with a double-headed arrow below it indicating its range or format. + +**Figure 2.2B-1: Structure of SUCI** + +The SUCI is composed of the following parts: + +- 1) SUPI Type, consisting in a value in the range 0 to 7. It identifies the type of the SUPI concealed in the SUCI. The following values are defined: + +- 0: IMSI +- 1: Network Specific Identifier (NSI) +- 2: Global Line Identifier (GLI) +- 3: Global Cable Identifier (GCI) +- 4 to 7: spare values for future use. + +- 2) Home Network Identifier, identifying the home network of the subscriber. + +When the SUPI Type is an IMSI, the Home Network Identifier is composed of two parts: + +- Mobile Country Code (MCC), consisting of three decimal digits. The MCC identifies uniquely the country of domicile of the mobile subscription; +- Mobile Network Code (MNC), consisting of two or three decimal digits. The MNC identifies the home PLMN or SNPN of the mobile subscription. + +When the SUPI type is a Network Specific Identifier (NSI), a GLI or a GCI, the Home Network Identifier consists of a string of characters with a variable length representing a domain name as specified in clause 2.2 of IETF RFC 7542 [126]. For a GLI or a GCI, the domain name shall correspond to the realm part specified in the NAI format for SUPI in clauses 28.15.2 and 28.16.2. + +- 3) Routing Indicator, consisting of 1 to 4 decimal digits assigned by the home network operator and provisioned in the USIM, that allow together with the Home Network Identifier to route network signalling with SUCI to AUSF and UDM instances capable to serve the subscriber. + +Each decimal digit present in the Routing Indicator shall be regarded as meaningful (e.g. value "012" is not the same as value "12"). If no Routing Indicator is configured on the USIM or the ME, this data field shall be set to the value 0 (i.e. only consist of one decimal digit of "0"). + +- 4) Protection Scheme Identifier, consisting in a value in the range of 0 to 15 (see Annex C.1 of 3GPP TS 33.501 [124]). It represents the null scheme or a non-null scheme specified in Annex C of 3GPP TS 33.501 [124] or a protection scheme specified by the HPLMN; the null scheme shall be used if the SUPI type is a GLI or GCI. + +- 5) Home Network Public Key Identifier, consisting in a value in the range 0 to 255. It represents a public key provisioned by the HPLMN or SNPN and it is used to identify the key used for SUPI protection. This data field shall be set to the value 0 if and only if null protection scheme is used; + +- 6) Scheme Output, consisting of a string of characters with a variable length or hexadecimal digits, dependent on the used protection scheme, as defined below. It represents the output of a public key protection scheme specified in Annex C of 3GPP TS 33.501 [124] or the output of a protection scheme specified by the HPLMN. + +Figure 2.2B-2 defines the scheme output for the null protection scheme. + +![Diagram of Scheme Output for the null protection scheme](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram shows a rectangular box representing the scheme output. Inside this box, at the top, is a smaller rectangular box containing the text: "MSIN (for SUPI type IMSI) or username (for SUPI type Network-Specific Identifier, GLI or GCI)". Below this inner box, a horizontal double-headed arrow spans the width of the inner box, with the word "Characters" centered below it. + +Diagram of Scheme Output for the null protection scheme + +**Figure 2.2B-2: Scheme Output for the null protection scheme** + +The Mobile Subscriber Identification Number ("MSIN") is defined in clause 2.2; the "username" corresponds to the username part of a NAI, and it is applicable to SUPI types Network-Specific Identifier (clause 28.7.2), GLI (clause 28.16.2) or GCI (clause 28.15.2). + +NOTE 1: For a SUCI with SUPI Type 2 or 3 (i.e. GLI or GCI), the SUCI can, based on subscription information, act as a pseudonym of the actual SUPI containing an IMSI (see 3GPP TS 23.316 [131], clauses 4.7.3 and 4.7.4). If so, the UDM derives the actual SUPI (IMSI) from the de-concealed SUCI (GLI/GCI). + +An anonymous SUCI is composed by setting the SUPI Type field to 1 (Network-Specific Identifier), using the null protection scheme, and where the scheme output corresponds to a username set to either the "anonymous" string or to an empty string (see IETF RFC 7542 [126], clause 2.4). + +The scheme output is formatted as a variable length of characters as specified for the username in clause 2.2 of IETF RFC 7542 [126]. + +NOTE 2: If the null protection scheme is used, the NFs can derive SUPI from SUCI when needed. The AMF derives SUPI used for AUSF discovery from SUCI when the Routing-Indicator is zero and the protection scheme is null. For an anonymous SUCI, an NF can derive an anonymous SUPI from an anonymous SUCI when needed; this is, the NF can derive a SUPI in NAI format for which the "username" part of the SUPI is "anonymous" or omitted. + +Figure 2.2B-3 defines the scheme output for the Elliptic Curve Integrated Encryption Scheme Profile A. + +![Diagram of Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile A](2834bdd6eb8540277e609decbb924003_img.jpg) + +The diagram shows a rectangular box representing the scheme output. Inside this box, there are three adjacent rectangular boxes. The first box is labeled "ECC ephemeral public key" and has a double-headed arrow below it labeled "64 hexadecimal digits". The second box is labeled "Ciphertext value" and has a double-headed arrow below it labeled "hexadecimal digits". The third box is labeled "MAC tag value" and has a double-headed arrow below it labeled "16 hexadecimal digits". + +Diagram of Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile A + +**Figure 2.2B-3: Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile A** + +The ECC ephemeral public key is formatted as 64 hexadecimal digits, which allows to encode 256 bits. + +The ciphertext value is formatted as a variable length of hexadecimal digits. + +The MAC tag value is formatted as 16 hexadecimal digits, which allows to encode 64 bits. + +**Editor's Note:** clause C.3.2 of TS 33.501 specifies that the scheme output may contain other parameters (not further defined in the specification). It is FFS how to format these parameters. + +Figure 2.2B-4 defines the scheme output for the Elliptic Curve Integrated Encryption Scheme Profile B. + +![Figure 2.2B-4: Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile B. The diagram shows three components in a row: 'ECC ephemeral public key' (66 hexadecimal digits), 'Ciphertext value' (hexadecimal digits), and 'MAC tag value' (16 hexadecimal digits).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the scheme output for Elliptic Curve Integrated Encryption Scheme Profile B. It consists of three distinct parts arranged horizontally within a rectangular border. The first part is labeled 'ECC ephemeral public key' and is associated with a double-headed arrow indicating a length of '66 hexadecimal digits'. The second part is labeled 'Ciphertext value' and is associated with a double-headed arrow indicating a length of 'hexadecimal digits'. The third part is labeled 'MAC tag value' and is associated with a double-headed arrow indicating a length of '16 hexadecimal digits'. + +Figure 2.2B-4: Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile B. The diagram shows three components in a row: 'ECC ephemeral public key' (66 hexadecimal digits), 'Ciphertext value' (hexadecimal digits), and 'MAC tag value' (16 hexadecimal digits). + +**Figure 2.2B-4: Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile B** + +The ECC ephemeral public key is formatted as 66 hexadecimal digits, which allows to encode 264 bits. + +The ciphertext value is formatted as a variable length of hexadecimal digits. + +The MAC tag value is formatted as 16 hexadecimal digits, which allows to encode 64 bits. + +**Editor's Note:** clause C.3.2 of TS 33.501 specifies that the scheme output may contain other parameters (not further defined in the specification). It is FFS how to format these parameters. + +Figure 2.2B-5 defines the scheme output for Home Network proprietary protection schemes. + +![Figure 2.2B-5: Scheme Output for Home Network proprietary protection schemes. The diagram shows a single component labeled 'Home Network defined Scheme Output' with a double-headed arrow indicating a length of 'hexadecimal digits'.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) + +The diagram illustrates the scheme output for Home Network proprietary protection schemes. It consists of a single component labeled 'Home Network defined Scheme Output' enclosed in a rectangular box. Below this box is a double-headed arrow indicating a length of 'hexadecimal digits'. + +Figure 2.2B-5: Scheme Output for Home Network proprietary protection schemes. The diagram shows a single component labeled 'Home Network defined Scheme Output' with a double-headed arrow indicating a length of 'hexadecimal digits'. + +**Figure 2.2B-5: Scheme Output for Home Network proprietary protection schemes** + +The Home Network defined scheme output is formatted as a variable length of hexadecimal digits. Its format is not further defined in 3GPP specifications. + +As examples, assuming the IMSI 234150999999999, where MCC=234, MNC=15 and MSISN=09999999999, the Routing Indicator 678, and a Home Network Public Key Identifier of 27: + +- the SUCI for the null protection scheme is composed of: 0, 234, 15, 678, 0, 0 and 09999999999 +- the SUCI for the Profile protection scheme is composed of: 0, 234, 15, 678, 1, 27, , and + +## 2.3 Allocation and assignment principles + +IMSI shall consist of decimal digits (0 through 9) only. + +The number of digits in IMSI shall not exceed 15. + +The allocation and assignment of Mobile Country Codes (MCCs) is administered by the ITU. The current assignment is available on ITU web site (). + +The assignment of Mobile network Codes (MNC) is the responsibility of each national numbering plan administrator. MNCs under MCC ranges 90x are administered by the ITU. The MSIN is the third field of the IMSI, and is administered by the relevant MNC assignee to identify individual subscriptions. + +If more than one PLMN exists in a country, the same Mobile Network Code should not be assigned to more than one PLMN. + +The allocation of IMSIs should be such that not more than the digits MCC + MNC of the IMSI have to be analysed in a foreign PLMN for information transfer. + +## 2.4 Structure of TMSI + +Since the TMSI has only local significance (i.e. within a VLR and the area controlled by a VLR, or within an SGSN and the area controlled by an SGSN, or within an MME and the area controlled by an MME), the structure and coding of it can be chosen by agreement between operator and manufacturer in order to meet local needs. + +The TMSI consists of 4 octets. It can be coded using a full hexadecimal representation. + +In order to avoid double allocation of TMSIs after a restart of an allocating node, some part of the TMSI may be related to the time when it was allocated or contain a bit field which is changed when the allocating node has recovered from the restart. + +In areas where both MSC-based services and SGSN-based services are provided, some discrimination is needed between the allocation of TMSIs for MSC-based services and the allocation of TMSIs for SGSN-based services. The discrimination shall be done on the 2 most significant bits, with values 00, 01, and 10 being used by the VLR, and 11 being used by the SGSN. + +If intra domain connection of RAN nodes to multiple CN nodes as described in 3GPP TS 23.236 [23] is applied in the MSC/VLR or SGSN, then the NRI shall be part of the TMSI. The NRI has a configurable length of 0 to 10 bits. A configurable length of 0 bits indicates that the NRI is not used and this feature is not applied in the MSC/VLR or SGSN. The NRI shall be coded in bits 23 to 14. An NRI shorter than 10 bits shall be encoded with the most significant bit of the NRI field in bit 23. + +The TMSI shall be allocated only in ciphered form. See also 3GPP TS 43.020 [7] and 3GPP TS 33.102 [42]. + +The network shall not allocate a TMSI with all 32 bits equal to 1 (this is because the TMSI must be stored in the SIM, and the SIM uses 4 octets with all bits equal to 1 to indicate that no valid TMSI is available). + +To allow for eventual modifications of the management of the TMSI code space management, MSs shall not check if an allocated TMSI belongs to the range allocated to the allocating node. MSs shall use an allocated TMSI according to the specifications, whatever its value. + +## 2.5 Structure of LMSI + +The LMSI consists of 4 octets and may be allocated by the VLR. The VLR shall not allocate the value zero. The value zero is reserved to indicate that an LMSI parameter sent from the HLR to the VLR shall not be interpreted. + +## 2.6 Structure of TLLI + +A TLLI is built by the MS or by the SGSN either on the basis of the P-TMSI (local or foreign TLLI), or directly (random or auxiliary TLLI), according to the following rules. + +The TLLI consists of 32 bits, numbered from 0 to 31 by order of significance, with bit 0 being the LSB. + +A local TLLI is built by an MS which has a valid P-TMSI as follows: + +bits 31 down to 30 are set to 1; and + +bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI. + +A foreign TLLI is built by an MS which has a valid P-TMSI as follows: + +bit 31 is set to 1 and bit 30 is set to 0; and + +bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI. + +A random TLLI is built by an MS as follows: + +bit 31 is set to 0; + +bits 30 down to 27 are set to 1; and + +bits 0 to 26 are chosen randomly. + +An auxiliary TLLI is built by the SGSN as follows: + +bit 31 is set to 0; + +bits 30 down to 28 are set to 1; + +bit 27 is set to 0; and + +bits 0 to 26 can be assigned independently. + +Other types of TLLI may be introduced in the future. + +Part of the TLLI codespace is re-used in GERAN to allow for the inclusion of the GERAN Radio Network Temporary Identifier in RLC/MAC messages. The G-RNTI is defined in 3GPP TS 44.118 [29]. + +The structure of the TLLI is summarised in table 1. + +**Table 1: TLLI structure** + +| 31 | 30 | 29 | 28 | 27 | 26 to 0 | Type of TLLI | +|----|----|----|----|----|---------|-----------------------------| +| 1 | 1 | T | T | T | T | Local TLLI | +| 1 | 0 | T | T | T | T | Foreign TLLI | +| 0 | 1 | 1 | 1 | 1 | R | Random TLLI | +| 0 | 1 | 1 | 1 | 0 | A | Auxiliary TLLI | +| 0 | 1 | 1 | 0 | X | X | Reserved | +| 0 | 1 | 0 | X | X | X | Reserved | +| 0 | 0 | 0 | 0 | G | G | Part of the assigned G-RNTI | +| 0 | 0 | 0 | 1 | R | R | Random G-RNTI | + +'T', 'R', 'A' and 'X' indicate bits which can take any value for the type of TLLI. More precisely, 'T' indicates bits derived from a P-TMSI, 'R' indicates bits chosen randomly, 'A' indicates bits chosen by the SGSN, 'G' indicates bits derived from the assigned G-RNTI and 'X' indicates bits in reserved ranges. + +## 2.7 Structure of P-TMSI Signature + +The P-TMSI Signature consists of 3 octets and may be allocated by the SGSN. + +The network shall not allocate a P-TMSI Signature with all 24 bits equal to 1 (this is because the P-TMSI Signature must be stored in the SIM, and the SIM uses 3 octets with all bits equal to 1 to indicate that no valid P-TMSI signature is available). + +## 2.8 Globally Unique Temporary UE Identity (GUTI) + +### 2.8.1 Introduction + +The purpose of the GUTI is to provide an unambiguous identification of the UE that does not reveal the UE or the user's permanent identity in the Evolved Packet System (EPS). It also allows the identification of the MME and network. It + +can be used by the network and the UE to establish the UE's identity during signalling between them in the EPS. See 3GPP TS 23.401 [72]. + +The GUTI has two main components: + +- one that uniquely identifies the MME which allocated the GUTI; and +- one that uniquely identifies the UE within the MME that allocated the GUTI. + +Within the MME, the mobile shall be identified by the M-TMSI. + +The Globally Unique MME Identifier (GUMMEI) shall be constructed from the MCC, MNC and MME Identifier (MMEI). + +The MMEI shall be constructed from an MME Group ID (MMEGI) and an MME Code (MMEC). + +The GUTI shall be constructed from the GUMMEI and the M-TMSI. + +For paging purposes, the mobile is paged with the S-TMSI. The S-TMSI shall be constructed from the MMEC and the M-TMSI. + +The operator shall need to ensure that the MMEC is unique within the MME pool area and, if overlapping pool areas are in use, unique within the area of overlapping MME pools. + +NOTE: In some network sharing cases it is required that the MMEC and NRI values are coordinated between the sharing operators, as described in 3GPP TS 23.251 [101]. In order to achieve CS/PS coordination in shared GERAN/UTRAN networks, the MMEC included in the GUTI can be set to identify the CS operator serving the UE. + +The GUTI shall be used to support subscriber identity confidentiality, and, in the shortened S-TMSI form, to enable more efficient radio signalling procedures (e.g. paging and Service Request). + +The format and size of the GUTI is therefore the following: + +$\langle \text{GUTI} \rangle = \langle \text{GUMMEI} \rangle \langle \text{M-TMSI} \rangle$ , + +where $\langle \text{GUMMEI} \rangle = \langle \text{MCC} \rangle \langle \text{MNC} \rangle \langle \text{MME Identifier} \rangle$ + +and $\langle \text{MME Identifier} \rangle = \langle \text{MME Group ID} \rangle \langle \text{MME Code} \rangle$ + +MCC and MNC shall have the same field size as in earlier 3GPP systems. + +M-TMSI shall be of 32 bits length. + +MME Group ID shall be of 16 bits length. + +MME Code shall be of 8 bits length. + +## 2.8.2 Mapping between Temporary and Area Identities for the EUTRAN and the UTRAN/GERAN based systems + +### 2.8.2.0 Introduction + +This clause provides information on the mapping of the temporary and location area identities, e.g. for the construction of the Routing Area Update Request message in GERAN/UTRAN or Tracking Area Update Request message in E-UTRAN. + +In GERAN and UTRAN: + +$\langle \text{RAI} \rangle = \langle \text{MCC} \rangle \langle \text{MNC} \rangle \langle \text{LAC} \rangle \langle \text{RAC} \rangle$ + +$\langle \text{P-TMSI/TLLI} \rangle$ includes the mapped NRI + +P-TMSI shall be of 32 bits length where the two topmost bits are reserved and always set to '11'. Hence, for a UE which may handover to GERAN/UTRAN (based on subscription and UE capabilities), the corresponding bits in the M-TMSI are set to '11' (see clause 2.8.2.1.3). + +3GPP TS 23.236 [23] specifies that the NRI field is of variable length and shall be mapped into the P-TMSI starting at bit 23 and down to bit 14. The most significant bit of the NRI is located at bit 23 of the P-TMSI regardless of the configured length of the NRI. To support mobility between GERAN/UTRAN and E-UTRAN, the NRI length is limited to a maximum of 8 bits to be compatible for the mapping to MME Code within GUTI (see clause 2.8.2.2). + +The P-TMSI and NRI are defined elsewhere in this specification. + +In the case of a combined MME-SGSN node, the NRI of the SGSN part and the MME code of the MME part, refer to the same combined node. RAN configuration allows NAS messages on GERAN/UTRAN and E-UTRAN to be routed to the same combined node. The same or different values of NRI and MME code may be used for a combined node. + +## 2.8.2.1 Mapping from GUTI to RAI, P-TMSI and P-TMSI signature + +### 2.8.2.1.1 Introduction + +This clause addresses the case when a UE moves from an MME to an SGSN. The SGSN may be either an S4 SGSN or a Gn/Gp SGSN. + +### 2.8.2.1.2 Mapping in the UE + +When a UE moves from an E-UTRAN to a GERAN/UTRAN, the UE needs to map the GUTI to an RAI, a P-TMSI and a P-TMSI Signature, for them to be sent to the SGSN. For GERAN, the TLLI is derived from the P-TMSI by the UE and is a foreign TLLI (see clause 2.6). + +The mapping of the GUTI shall be done to the combination of RAI of GERAN / UTRAN and the P-TMSI: + +E-UTRAN maps to GERAN/UTRAN + +E-UTRAN maps to GERAN/UTRAN + +E-UTRAN maps to GERAN/UTRAN + +E-UTRAN maps to GERAN/UTRAN and is also copied into the 8 Most Significant Bits of the NRI field within the P-TMSI; + +E-UTRAN maps as follows: + +- 6 bits of the E-UTRAN starting at bit 29 and down to bit 24 are mapped into bit 29 and down to bit 24 of the GERAN/UTRAN ; +- 16 bits of the E-UTRAN starting at bit 15 and down to bit 0 are mapped into bit 15 and down to bit 0 of the GERAN/UTRAN ; +- and the remaining 8 bits of the E-UTRAN are mapped into the 8 Most Significant Bits of the field. + +The UE shall fill the remaining 2 octets of the according to clauses 9.1.1, 9.4.1, 10.2.1, or 10.5.1 of 3GPP TS.33.401 [89], as appropriate, for RAU/Attach procedures. + +For UTRAN, the 10-bit long NRI bits are masked out from the P-TMSI and are also supplied by the UE to the RAN node as IDNNS (Intra Domain NAS Node Selector) (see 3GPP TS 23.236 [23]). However, the RAN configured NRI length should not exceed 8 bits. + +### 2.8.2.1.3 Mapping in the old MME + +A new SGSN attempts to retrieve information regarding the UE, e.g. the IMSI, from the old MME. In order to find the UE context, the MME needs to map the RAI, P-TMSI (or TLLI) and the P-TMSI Signature (sent by the SGSN) to create the GUTI and compare it with the stored GUTI. + +The MME shall perform a reverse mapping to the mapping procedure specified in clause 2.8.2.1.2 "Mapping in the UE" (see 3GPP TS 29.060 [6] and 3GPP TS 29.274 [88] for specifics of the messaging). For the reverse mapping, the E-UTRAN within the GUTI shall be set either to bits 23 to 16 of the GERAN/UTRAN (i.e., the NRI field) or to the GERAN/UTRAN . For GERAN TLLI, the old MME replaces the two topmost bits of TLLI, received from new SGSN via GTPv1, with '11' before mapping the TLLI to the GUTI used for looking up the "UE Context". + +## 2.8.2.2 Mapping from RAI and P-TMSI to GUTI + +### 2.8.2.2.1 Introduction + +This clause addresses the case when a UE moves from an SGSN to an MME (i.e. during a TAU or an Attach to MME). The SGSN may be either an S4 SGSN or a Gn/Gp SGSN. + +### 2.8.2.2.2 Mapping in the UE + +When the UE moves from the GERAN/UTRAN to the E-UTRAN, the UE needs to map the RAI and P-TMSI to a GUTI to be sent to the MME. The P-TMSI signature is sent intact to the MME. + +The mapping of P-TMSI (TLLI) and RAI in GERAN/UTRAN to GUTI in E-UTRAN shall be performed as follows: + +GERAN/UTRAN maps to E-UTRAN + +GERAN/UTRAN maps to E-UTRAN + +GERAN/UTRAN maps to E-UTRAN + +GERAN/UTRAN maps into bit 23 and down to bit 16 of the M-TMSI + +The 8 most significant bits of GERAN/UTRAN map to the MME code. + +GERAN/UTRAN maps as follows: + +- 6 bits of the GERAN/UTRAN starting at bit 29 and down to bit 24 are mapped into bit 29 and down to bit 24 of the E-UTRAN ; +- 16 bits of the GERAN/UTRAN starting at bit 15 and down to bit 0 are mapped into bit 15 and down to bit 0 of the E-UTRAN . + +The values of and shall be disjoint, so that they can be differentiated. + +The most significant bit of the shall be set to zero; and the most significant bit of shall be set to one. Based on this definition, the most significant bit of the can be used to distinguish the node type, i.e. whether it is an MME or SGSN. The UE copies the received old SGSN's into the when sending a message to an MME, regardless of the value of the most significant bit of the . + +In networks where this definition is not applied (e.g. in networks already configured with LAC with the most significant bit set to 1 before LTE deployment), the information in the TAU/RAU request indicating whether the provided GUTI/P-TMSI is "native" (i.e. no system change) or "mapped" (i.e. system change) can be used to distinguish the node type for UEs implemented according to this release of the specification (see 3GPP TS 24.301 [90] and 3GPP TS 24.008 [5]). Specific network implementations still satisfying 3GPP standard interfaces can be used for pre-Rel-10 UEs to distinguish the node type. + +NOTE 1: As an example, at NAS level, the MME/SGSN can retrieve the old SGSN/MME by using additional GUTI/additional RAI/P-TMSI with double DNS query to solve the first time the UE moves between E-UTRAN and GERAN/UTRAN. As another example, the MME/SGSN can retrieve the old SGSN/MME by using double DNS query. + +### 2.8.2.2.3 Mapping in the new MME + +In order to retrieve the UE's information, e.g. the IMSI, from the old SGSN, the new MME extracts only the RAI and P-TMSI from the GUTI via the reverse mapping procedure to that specified in clause 2.8.2.2.2. This is done in order to be able to include the mapped RAI and P-TMSI, along with the P-TMSI Signature received by the MME from the UE, in the corresponding message sent to the old SGSN (see 3GPP TS 29.060 [6] and 3GPP TS 29.274 [88] for specifics of the + +messaging). The old SGSN compares the received RAI, P-TMSI and P-TMSI Signature with the stored values for identifying the UE. + +## 2.9 Structure of the S-Temporary Mobile Subscriber Identity (S-TMSI) + +The S-TMSI is the shortened form of the GUTI to enable more efficient radio signalling procedures (e.g. paging and Service Request). For paging purposes, the mobile is paged with the S-TMSI. The S-TMSI shall be constructed from the MMEC and the M-TMSI: + +$$\langle \text{S-TMSI} \rangle = \langle \text{MMEC} \rangle \langle \text{M-TMSI} \rangle$$ + +See clause 2.8 for these definitions and the mapping. + +## 2.10 5G Globally Unique Temporary UE Identity (5G-GUTI) + +### 2.10.1 Introduction + +The purpose of the 5G-GUTI is to provide an unambiguous identification of the UE that does not reveal the UE or the user's permanent identity in the 5G System (5GS). It also allows the identification of the Access and Mobility Management Function (AMF) and network. It can be used by the network and the UE to establish the UE's identity during signalling between them in the 5GS. See 3GPP TS 23.501 [119]. + +The 5G-GUTI has two main components: + +- one that identifies the AMF(s) which allocated the 5G-GUTI; and +- one that uniquely identifies the UE within the AMF(s) that allocated the 5G-GUTI. + +Within the AMF(s), the mobile shall be identified by the 5G-TMSI. + +The Globally Unique AMF Identifier (GUAMI) shall be constructed from the MCC, MNC and AMF Identifier (AMFI). + +The AMFI shall be constructed from an AMF Region ID, an AMF Set ID and an AMF Pointer. The AMF Region ID identifies the region, the AMF Set ID uniquely identifies the AMF Set within the AMF Region, and the AMF Pointer identifies one or more AMFs within the AMF Set. + +NOTE: When the UE is assigned a 5G-GUTI with an AMF Pointer value used by more than one AMF, the AMFs need to ensure that the 5G-TMSI value used within the assigned 5G-GUTI is not already in use within the AMF's sharing that pointer value. + +The 5G-GUTI shall be constructed from the GUAMI and the 5G-TMSI. + +For paging purposes, the mobile is paged with the 5G-S-TMSI. The 5G-S-TMSI shall be constructed from the AMF Set ID, the AMF Pointer and the 5G-TMSI. + +The operator shall need to ensure that the combination of the AMF Set ID and AMF Pointer is unique within the AMF Region and, if overlapping AMF Regions are in use, unique within the area of overlapping AMF Regions. + +The 5G-GUTI shall be used to support subscriber identity confidentiality, and, in the shortened 5G-S-TMSI form, to enable more efficient radio signalling procedures (e.g. paging and Service Request). + +The format and size of the 5G-GUTI is therefore the following: + +$$\langle \text{5G-GUTI} \rangle = \langle \text{GUAMI} \rangle \langle \text{5G-TMSI} \rangle,$$ + +where $\langle \text{GUAMI} \rangle = \langle \text{MCC} \rangle \langle \text{MNC} \rangle \langle \text{AMF Identifier} \rangle$ + +and $\langle \text{AMF Identifier} \rangle = \langle \text{AMF Region ID} \rangle \langle \text{AMF Set ID} \rangle \langle \text{AMF Pointer} \rangle$ + +MCC and MNC shall have the same field size as in earlier 3GPP systems. + +5G-TMSI shall be of 32 bits length. + +AMF Region ID shall be of 8 bits length. + +AMF Set ID shall be of 10 bits length. + +AMF Pointer shall be of 6 bits length. + +## 2.10.2 Mapping between Temporary Identities for the 5GS and the E-UTRAN + +### 2.10.2.0 Introduction + +This clause provides information on the mapping of the temporary identities, e.g. for the construction of the Tracking Area Update Request message in E-UTRAN. + +In E-UTRAN: + + = + +### 2.10.2.1 Mapping from 5G-GUTI to GUTI + +#### 2.10.2.1.1 Introduction + +This clause addresses the case when a UE moves from an AMF to an MME. + +#### 2.10.2.1.2 Mapping in the UE + +When a UE moves from 5GS to an E-UTRAN, the UE needs to map the 5G-GUTI to a GUTI. + +The mapping of the 5G-GUTI to a GUTI shall be done as follows: + +5GS maps to E-UTRAN + +5GS maps to E-UTRAN + +5GS and 5GS map to E-UTRAN and part of E-UTRAN as follows: + +- 8 bits of the 5GS starting at bit 7 and down to bit 0 are mapped into bit 15 and down to bit 8 of the E-UTRAN ; +- 8 bits of the 5GS starting at bit 9 and down to bit 2 are mapped into bit 7 and down to bit 0 of the E-UTRAN ; +- 2 bits of the 5GS starting at bit 1 and down to bit 0 are mapped into bit 7 and down to bit 6 of the E-UTRAN ; + +5GS maps to part of E-UTRAN as follows: + +- 6 bits of the 5GS starting at bit 5 and down to bit 0 are mapped into bit 5 and down to bit 0 of the E-UTRAN . + +5GS <5G-TMSI> maps to E-UTRAN + +#### 2.10.2.1.3 Mapping in the old AMF + +A new MME attempts to retrieve information regarding the UE, e.g. the IMSI, from the old AMF. In order to find the UE context, the AMF needs to map the GUTI (sent by the MME) to create the 5G-GUTI and compare it with the stored 5G-GUTI. + +The AMF shall perform a reverse mapping to the mapping procedure specified in clause 2.10.2.1.2 "Mapping in the UE". + +## 2.10.2.2 Mapping from GUTI to 5G-GUTI + +### 2.10.2.2.1 Introduction + +This clause addresses the case when a UE moves from an MME to an AMF (i.e. during a Registration Update or an Initial Registration to an AMF). + +### 2.10.2.2.2 Mapping in the UE + +When the UE moves from the E-UTRAN to 5GS, the UE needs to map the GUTI to a 5G-GUTI to be sent to the AMF. + +The mapping of the GUTI to a 5G-GUTI shall be performed as follows: + +E-UTRAN maps to 5GS + +E-UTRAN maps to 5GS + +E-UTRAN maps to 5GS and part of 5GS as follows: + +- 8 bits of the E-UTRAN starting at bit 15 and down to bit 8 are mapped into bit 7 and down to bit 0 of the 5GS ; +- 8 bits of the E-UTRAN starting at bit 7 and down to bit 0 are mapped into bit 9 and down to bit 2 of the 5GS ; E-UTRAN maps to 5GS and 5GS as follows: + - 2 bits of the E-UTRAN starting at bit 7 and down to bit 6 are mapped into bit 1 and down to bit 0 of the 5GS ; + - 6 bits of the E-UTRAN starting at bit 5 and down to bit 0 are mapped into bit 5 and down to bit 0 of the 5GS ; + +E-UTRAN maps to 5GS <5G-TMSI> + +### 2.10.2.2.3 Mapping in the new AMF + +In order to retrieve the UE's information, e.g. the IMSI, from the old MME, the new AMF shall perform a reverse mapping to the mapping procedure specified in clause 2.10.2.2.2 "Mapping in the UE". This is done in order to be able to include the mapped GUTI in the corresponding message sent to the old MME. The old MME compares the received GUTI with the stored values for identifying the UE. + +## 2.11 Structure of the 5G-S-Temporary Mobile Subscriber Identity (5G-S-TMSI) + +The 5G-S-TMSI is the shortened form of the 5G-GUTI to enable more efficient radio signalling procedures (e.g. paging and Service Request). For paging purposes, the mobile is paged with the 5G-S-TMSI. The 5G-S-TMSI shall be constructed from the AMF Set ID, the AMF Pointer and the 5G-TMSI: + +$$\langle 5G-S-TMSI \rangle = \langle AMF Set ID \rangle \langle AMF Pointer \rangle \langle 5G-TMSI \rangle$$ + +See clause 2.10.1 for these definitions and clause 2.10.2 for the mapping. + +## 2.12 Structure of the Truncated 5G-S-Temporary Mobile Subscriber Identity (Truncated 5G-S-TMSI) + +The Truncated 5G-S-TMSI is a 40 bit UE identifier constructed from the 5G-S-TMSI. It is used in RRC Connection Re-Establishment for the control plane for NB-IoT as described in 3GPP TS 36.300 [91]. The Truncated 5G-S-TMSI shall be constructed from the Truncated AMF set ID, the Truncated AMF Pointer and the Truncated 5G-TMSI: + +$$\langle \text{Truncated 5G-S-TMSI} \rangle = \langle \text{Truncated AMF set ID} \rangle \langle \text{Truncated AMF Pointer} \rangle \langle \text{Truncated 5G-TMSI} \rangle$$ + +Truncated AMF set ID is n least significant bits of AMF Set ID, where n is no greater than 10 bits. + +Truncated AMF Pointer is m least significant bits of AMF Pointer, where m is no greater than 6 bits. + +Truncated 5G-TMSI is (40-n-m) least significant bits of 5G-TMSI. + +The values n and m are configurable based on network deployment. The value n+m shall be larger or equal to 8 bits. + +NOTE: Depending on network deployment it is up to operator configuration to ensure that Truncated AMF Set ID and Truncated AMF Pointer identify the AMF uniquely, and that Truncated 5G-TMSI identifies the UE uniquely within the serving AMF. + +The NG-RAN and AMF are configured with the values n and m respectively, and NG-RAN is configured with how to recreate AMF Set ID from Truncated AMF Set ID, AMF Pointer from Truncated AMF Pointer, and 5G-TMSI from Truncated 5G-TMSI. The configuration of these parameters are specific to each PLMN. + +The AMF configures the UE with the Truncated 5G-S-TMSI Configuration that provides the sizes of the components of the Truncated 5G-S-TMSI as described in 3GPP TS 24.501 [125] during the Registration and UE Configuration Update procedures. + +For Network Sharing, the sharing NG-RAN is configured with the respective values n and m that are specific to each PLMN, and AMF is configured with the same values n and m as ones configured on NG-RAN per PLMN. The AMF configures the UE with the corresponding values n and m according to the PLMN which the UE accesses to during the Registration procedure. + +--- + +## 3 Numbering plan for mobile stations + +### 3.1 General + +The structure of the following numbers is defined below: + +- the telephone number used by a subscriber of a fixed (or mobile) network to call a mobile station of a PLMN; +- the network addresses used for packet data communication between a mobile station and a fixed (or mobile) station; +- mobile station roaming numbers. + +One or more numbers of the E.164 numbering plan shall be assigned to a mobile station to be used for all calls to that station, i.e. the assignment of at least one MSISDN (i.e. E.164 number) to a mobile station is mandatory. As an exception, GPRS and EPS allow for operation whereby a MSISDN is not allocated as part of the subscription data (see 3GPP TS 23.060 [3] clause 5.3.17 and 3GPP TS 23.401 [72]). + +NOTE: For card operated stations the E.164 number should be assigned to the holder of the card (personal number). + +### 3.2 Numbering plan requirements + +In principle, it should be possible for any subscriber of the ISDN or PSTN to call any MS in a PLMN. This implies that E.164 numbers for MSs should comply with the E.164 numbering plan in the home country of the MS. + +The E.164 numbers of MSs should be composed in such a way that standard ISDN/PSTN charging can be used for calls to MSs. + +It should be possible for each national numbering plan administrator to develop its own independent numbering/addressing plan for MSs. + +The numbering/addressing plan should not limit the possibility for MSs to roam among PLMNs. + +It should be possible to change the IMSI without changing the E.164 number assigned to an MS and vice versa. + +In principle, it should be possible for any subscriber of the CSPDN/PSPDN to call any MS in a PLMN. This implies that it may be necessary for an MS to have a X.121 number. + +In principle, it should be possible for any fixed or mobile terminal to communicate with a mobile terminal using an IP v4 address or IP v6 address. + +### 3.3 Structure of Mobile Subscriber ISDN number (MSISDN) + +Mobile Subscriber ISDN numbers (i.e. E.164 numbers) are assigned from the E.164 numbering plan [10]; see also ITU-T Recommendation E.213 [12]. The structure of the MSISDN will then be as shown in figure 2. + +![Diagram illustrating the number structure of MSISDN. It shows three components: CC (Country Code), NDC (National Destination Code), and SN (Subscriber Number). The NDC and SN are grouped together as the 'National (significant) number'. The entire combination of CC, NDC, and SN is labeled as the 'Mobile Subscriber ISDN number'.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +The diagram shows three boxes labeled CC, NDC, and SN. Below the NDC and SN boxes, a horizontal line with arrows at both ends spans their combined width and is labeled "National (significant) number". Below this, another horizontal line with arrows at both ends spans the width of the CC, NDC, and SN boxes and is labeled "Mobile Subscriber ISDN number". + +Diagram illustrating the number structure of MSISDN. It shows three components: CC (Country Code), NDC (National Destination Code), and SN (Subscriber Number). The NDC and SN are grouped together as the 'National (significant) number'. The entire combination of CC, NDC, and SN is labeled as the 'Mobile Subscriber ISDN number'. + +**Figure 2: Number Structure of MSISDN** + +The number consists of: + +- Country Code (CC) of the country in which the MS is registered, followed by: +- National (significant) number, which consists of: + - National Destination Code (NDC) and + - Subscriber Number (SN). + +For GSM/UMTS applications, a National Destination Code is allocated to each PLMN. In some countries more than one NDC may be required for each PLMN/mobile number ranges. + +The composition of the MSISDN should be such that it can be used as a global title address in the Signalling Connection Control Part (SCCP) for routing messages to the home location register of the MS. The country code (CC) and the national destination code (NDC) will provide such routing information. If further routing information is required, it should be contained in the first few digits of the subscriber number (SN). + +A sub-address may be appended to an E.164 number for use in call setup and in supplementary service operations where an E.164 number is required (see ITU-T Recommendations E.164, clause Annex B, B.3.3, and X.213 annex A). The sub-address is transferred to the terminal equipment denoted by the ISDN number. + +The maximum length of a sub-address is 20 octets, including one octet to identify the coding scheme for the sub-address (see ITU-T Recommendation X.213, annex A). All coding schemes described in ITU-T Recommendation X.213, annex A are supported in 3GPP networks + +As an exception to the rules above, the MSISDN shall take the dummy MSISDN value composed of 15 digits set to 0 (encoded as an international E.164 number) when the MSISDN is not available in messages in which the presence of the MSISDN parameter is required for backward compatibility reason. See the relevant stage 3 specifications. + +### 3.4 Mobile Station Roaming Number (MSRN) for PSTN/ISDN routing + +The Mobile Station Roaming Number (MSRN) is used to route calls directed to an MS. On request from the Gateway MSC via the HLR it is temporarily allocated to an MS by the VLR with which the MS is registered; it addresses the Visited MSC collocated with the assigning VLR. More than one MSRN may be assigned simultaneously to an MS. + +The MSRN is passed by the HLR to the Gateway MSC to route calls to the MS. + +The Mobile Station Roaming Number for PSTN/ISDN routing shall have the same structure as international E.164 numbers in the area in which the roaming number is allocated, i.e.: + +- the country code of the country in which the visitor location register is located; +- the national destination code of the visited PLMN or numbering area; +- a subscriber number with the appropriate structure for that numbering area. + +The MSRN shall not be used for subscriber dialling. It should be noted that the MSRN can be identical to the MSISDN (clause 3.3) in certain circumstances. In order to discriminate between subscriber generated access to these numbers and re-routing performed by the network, re-routing or redirection indicators or other signalling means should be used, if available. + +### 3.5 Structure of Mobile Station International Data Number + +The structure of MS international data numbers should comply with the data numbering plan of ITU-T Recommendation X.121 as applied in the home country of the mobile subscriber. Implications for numbering interworking functions which may need to be provided by the PLMN (if the use of X.121 numbers is required) are indicated in 3GPP TS 23.070 [4]. + +### 3.6 Handover Number + +The handover number is used for establishment of a circuit between MSCs to be used for a call being handed over. The structure of the handover number is the same as the structure of the MSRN. The handover number may be reused in the same way as the MSRN. + +### 3.7 Structure of an IP v4 address + +One or more IP address domains may be allocated to each PLMN. The IP v4 address structure is defined in RFC 791 [14]. + +An IP v4 address may be allocated to an MS either permanently or temporarily during a connection with the network. + +### 3.8 Structure of an IP v6 address + +One or more IP address domains could be allocated to each PLMN. The IP v6 address structure is defined in RFC 2373 [15]. + +An IP v6 address may be allocated to an MS either permanently or temporarily during a connection with the network + +If the dynamic IPv6 stateless address autoconfiguration procedure is used, then each PDP context, or group of PDP contexts sharing the same IP address, is assigned a unique prefix as defined in 3GPP TS 23.060 [3]. + +As described in RFC 2462 [21] and RFC 3041 [22], the MS can change its interface identifier without the GPRS network being aware of the change. + +## 4 Identification of location areas and base stations + +### 4.1 Composition of the Location Area Identification (LAI) + +The Location Area Identification shall be composed as shown in figure 3: + +![Figure 3: Structure of Location Area Identification. A diagram showing three boxes labeled MCC, MNC, and LAC. Below these boxes is a double-headed arrow labeled 'Location Area Identification'.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +The diagram shows three rectangular boxes labeled 'MCC', 'MNC', and 'LAC' arranged horizontally. Below these boxes is a double-headed arrow pointing left and right, with the text 'Location Area Identification' centered below it. + +Figure 3: Structure of Location Area Identification. A diagram showing three boxes labeled MCC, MNC, and LAC. Below these boxes is a double-headed arrow labeled 'Location Area Identification'. + +**Figure 3: Structure of Location Area Identification** + +The LAI is composed of the following elements: + +- Mobile Country Code (MCC) identifies the country in which the GSM PLMN is located. The value of the MCC is the same as the three digit MCC contained in international mobile subscriber identity (IMSI); +- Mobile Network Code (MNC) is a code identifying the GSM PLMN in that country. The MNC takes the same value as the two or three digit MNC contained in IMSI; +- Location Area Code (LAC) is a fixed length code (of 2 octets) identifying a location area within a PLMN. This part of the location area identification can be coded using a full hexadecimal representation except for the following reserved hexadecimal values: + +0000, and + +FFFE. + +These reserved values are used in some special cases when no valid LAI exists in the MS (see 3GPP TS 24.008 [5], 3GPP TS 31.102 [27] and 3GPP TS 51.011 [9]). + +### 4.2 Composition of the Routing Area Identification (RAI) + +The Routing Area Identification shall be composed as shown in figure 4: + +![Figure 4: Structure of Routing Area Identification. A diagram showing two boxes labeled LAI and RAC. Below these boxes is a double-headed arrow labeled 'Routeing Area Identification'.](10d81b2cc455e3563e3e562a7f451124_img.jpg) + +The diagram shows two rectangular boxes labeled 'LAI' and 'RAC' arranged horizontally. Below these boxes is a double-headed arrow pointing left and right, with the text 'Routeing Area Identification' centered below it. + +Figure 4: Structure of Routing Area Identification. A diagram showing two boxes labeled LAI and RAC. Below these boxes is a double-headed arrow labeled 'Routeing Area Identification'. + +**Figure 4: Structure of Routing Area Identification** + +The RAI is composed of the following elements: + +- A valid Location Area Identity (LAI) as defined in clause 4.1. Invalid LAI values are used in some special cases when no valid RAI exists in the mobile station (see 3GPP TS 24.008 [5], 3GPP TS 31.102 [27] and 3GPP TS 51.011 [9]). +- Routeing Area Code (RAC) which is a fixed length code (of 1 octet) identifying a routeing area within a location area. + +### 4.3 Base station identification + +#### 4.3.1 Cell Identity (CI) and Cell Global Identification (CGI) + +The BSS and cell within the BSS are identified within a location area or routeing area by adding a Cell Identity (CI) to the location area or routeing area identification, as shown in figure 5. The CI is of fixed length with 2 octets and it can be coded using a full hexadecimal representation. + +The Cell Global Identification is the concatenation of the Location Area Identification and the Cell Identity. Cell Identity shall be unique within a location area. + +![Figure 5: Structure of Cell Global Identification. The diagram shows a horizontal bar divided into four segments: MCC, MNC, LAC, and CI. A bracket labeled 'Location Area Identification' spans the MCC, MNC, and LAC segments. A longer bracket labeled 'Cell Global Identification (CGI)' spans all four segments: MCC, MNC, LAC, and CI.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Figure 5: Structure of Cell Global Identification. The diagram shows a horizontal bar divided into four segments: MCC, MNC, LAC, and CI. A bracket labeled 'Location Area Identification' spans the MCC, MNC, and LAC segments. A longer bracket labeled 'Cell Global Identification (CGI)' spans all four segments: MCC, MNC, LAC, and CI. + +Figure 5: Structure of Cell Global Identification + +#### 4.3.2 Base Station Identify Code (BSIC) + +The base station identity code is a local colour code that allows an MS to distinguish between different neighbouring base stations. BSIC is a 6 bit code which is structured as shown in Figure 6. Exceptions apply to networks supporting EC-GSM-IoT or PEO and for mobile stations in EC or PEO operation (see 3GPP TS 43.064 [112]) where the BSIC is a 9 bit code which is structured as shown in Figure 6a. + +![Figure 6: Structure of 6 bit BSIC. The diagram shows a horizontal bar divided into two segments: NCC and BCC. Below the NCC segment is a double-headed arrow labeled '3 bits' and 'PLMN colour code'. Below the BCC segment is a double-headed arrow labeled '3 bits' and 'BS colour code'.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +Figure 6: Structure of 6 bit BSIC. The diagram shows a horizontal bar divided into two segments: NCC and BCC. Below the NCC segment is a double-headed arrow labeled '3 bits' and 'PLMN colour code'. Below the BCC segment is a double-headed arrow labeled '3 bits' and 'BS colour code'. + +Figure 6: Structure of 6 bit BSIC + +![Figure 6a: Structure of 9 bit BSIC. The diagram shows a horizontal bar divided into three segments: NCC, BCC, and RCC. Below the NCC segment is a double-headed arrow labeled '3 bits' and 'PLMN colour code'. Below the BCC segment is a double-headed arrow labeled '3 bits' and 'BS colour code'. Below the RCC segment is a double-headed arrow labeled '3 bits' and 'Radio frequency colour code'.](c85b57b2414f341860dfc338e1cf2509_img.jpg) + +Figure 6a: Structure of 9 bit BSIC. The diagram shows a horizontal bar divided into three segments: NCC, BCC, and RCC. Below the NCC segment is a double-headed arrow labeled '3 bits' and 'PLMN colour code'. Below the BCC segment is a double-headed arrow labeled '3 bits' and 'BS colour code'. Below the RCC segment is a double-headed arrow labeled '3 bits' and 'Radio frequency colour code'. + +Figure 6a: Structure of 9 bit BSIC + +In the definition of the NCC, care should be taken to ensure that the same NCC is not used in adjacent PLMNs which may use the same BCCH carrier frequencies in neighbouring areas. Therefore, to prevent potential deadlocks, a definition of the NCC appears in annex A. This annex will be reviewed in a co-ordinated manner when a PLMN is created. + +In addition to the above, the GERAN networks should be configured so that: + +- in a cell shared between different PLMNs as per GERAN network sharing (see 3GPP TS 44.018 [99] and 3GPP TS 44.060 [100]), the NCC used in this cell is different from the NCC used in the neighbouring non-shared cells of these PLMNs; and that +- these PLMNs use different NCCs in non-shared cells neighbouring this shared cell. + +Furthermore, GERAN networks supporting the 9 bit BSIC shall also support the 6 bit BSIC field and when supporting both the 6 bit BSIC and 9 bit BSIC the network shall ensure that the NCC and BCC parts are identical between the 6 bit and 9 bit BSIC fields. + +## 4.4 Regional Subscription Zone Identity (RSZI) + +A PLMN-specific regional subscription defines unambiguously for the entire PLMN the regions in which roaming is allowed. It consists of one or more regional subscription zones. The regional subscription zone is identified by a Regional Subscription Zone Identity (RSZI). A regional subscription zone identity is composed as shown in figure 7. + +![Figure 7: Structure of Regional Subscription Zone Identity (RSZI). The diagram shows a large rectangle labeled 'RSZI' at the top. Inside this rectangle, there are two main parts: a box on the left containing 'CC' and 'NDC', and a box on the right containing 'ZC'. Below the 'ZC' box, a double-headed arrow indicates its length, labeled 'Zone Code, Two octets'.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +Figure 7: Structure of Regional Subscription Zone Identity (RSZI). The diagram shows a large rectangle labeled 'RSZI' at the top. Inside this rectangle, there are two main parts: a box on the left containing 'CC' and 'NDC', and a box on the right containing 'ZC'. Below the 'ZC' box, a double-headed arrow indicates its length, labeled 'Zone Code, Two octets'. + +**Figure 7: Structure of Regional Subscription Zone Identity (RSZI)** + +The elements of the regional subscription zone identity are: + +- 1) the Country Code (CC) which identifies the country in which the PLMN is located; +- 2) the National Destination Code (NDC) which identifies the PLMN in that country; +- 3) the Zone Code (ZC) which identifies a regional subscription zone as a pattern of allowed and not allowed location areas uniquely within that PLMN. + +CC and NDC are those of an ITU-T E.164 VLR or SGSN number (see clause 5.1) of the PLMN; they are coded with a trailing filler, if required. ZC has fixed length of two octets and is coded in full hexadecimal representation. + +RSZIs, including the zone codes, are assigned by the VPLMN operator. The zone code is evaluated in the VLR or SGSN by information stored in the VLR or SGSN as a result of administrative action. If a zone code is received by a VLR or SGSN during updating by the HLR and this zone code is related to that VLR or SGSN, the VLR or SGSN shall be able to decide for all its MSC or SGSN areas and all its location areas whether they are allowed or not allowed. + +For details of assignment of RSZI and of ZC as subscriber data see 3GPP TS 23.008 [2]. + +For selection of RSZI at location updating by comparison with the leading digits of the VLR or SGSN number and for transfer of ZC from the HLR to VLR and SGSN see 3GPP TS 29.002 [31]. + +## 4.5 Location Number + +A location number is a number which defines a specific location within a PLMN. The location number is formatted according to ITU-T Recommendation E.164, as shown in figure 8. The Country Code (CC) and National Destination Code (NDC) fields of the location number are those which define the PLMN of which the location is part. + +![Figure 8: Location Number Structure. The diagram shows a large rectangle containing three separate boxes labeled 'CC', 'NDC', and 'LSP' from left to right.](a9bd36d25444d896e8d6941ff59d8f2d_img.jpg) + +Figure 8: Location Number Structure. The diagram shows a large rectangle containing three separate boxes labeled 'CC', 'NDC', and 'LSP' from left to right. + +**Figure 8: Location Number Structure** + +The structure of the locally significant part (LSP) of the location number is a matter for agreement between the PLMN operator and the national numbering plan administrator in the PLMN's country. It is desirable that the location number can be interpreted without the need for detailed knowledge of the internal structure of the PLMN; the LSP should therefore include the national destination code in the national numbering plan for the fixed network which defines the geographic area in which the location lies. + +The set of location numbers for a PLMN shall be chosen so that a location number can be distinguished from the MSISDN of a subscriber of the PLMN. This will allow the PLMN to trap attempts by users to dial a location number. + +## 4.6 Composition of the Service Area Identification (SAI) + +Void (see clause 12.5). + +## 4.7 Closed Subscriber Group + +A Closed Subscriber Group consists of a single cell or a collection of cells within an E-UTRAN and UTRAN that are open to only a certain group of subscribers. + +Within a PLMN, a Closed Subscriber Group is identified by a Closed Subscriber Group Identity (CSG-ID). The CSG-ID shall be a fixed length 27 bit value. + +## 4.8 HNB Name + +HNB Name shall be a broadcast string in free text format that provides a human readable name for the Home NodeB or Home eNodeB CSG identity. + +HNB Name shall be coded in UTF-8 format with variable number of bytes per character. The maximum length of HNB Name shall be 48 bytes. + +See 3GPP TS 22.011 [83] for details. + +## 4.9 CSG Type + +CSG Type shall provide the type of a CSG identity in a human readable form. It shall reside in the UE only. See 3GPP TS 22.011 [83] for details. + +When the CSG Type has a text component, the CSG Type shall be coded in UTF-8 format with variable number of bytes per character. The maximum text length shall not exceed 12 characters in any language. + +## 4.10 HNB Unique Identity + +HNB Unique Identity uniquely identifies a Home NodeB or Home eNodeB. + +The HNB unique identity shall be defined as either a 48-bit or 64-bit extended unique identifier (EUI-48 or EUI-64) as defined in [45] (EUI-48) and [46] (EUI-64). + +For use in HNB certificates, the HNB Unique Identity shall be transformed into a FQDN in the form: + +- . + + is the first label which shall be the EUI-48 or EUI-64, represented as a string of 12 or 16 hexadecimal digits including any leading zeros. denotes the realm which may consist of 3 labels, e.g. hnb.femtocellvendor.com. + +## 4.11 HRNN + +HRNN shall be a broadcast string in free text format that provides a human readable name for manual CAG or SNPN selection. + +HRNN shall be coded in UTF-8 format with variable number of bytes per character. The maximum length of HRNN shall be 48 bytes. + +See 3GPP TS 23.501 [119] and 3GPP TS 38.331 [138] for details. + +## 5 Identification of MSCs, GSNs, location registers and CSSs + +### 5.1 Identification for routing purposes + +MSCs, GSNs, location registers and CSSs are identified by international E.164 numbers and/or Signalling Point Codes ("entity number", i.e., "HLR number", "VLR number", "MSC number", "SGSN number", "GGSN number" and "CSS number") in each PLMN. + +MMEs that support "SMS in MME" are identified by international PSTN/ISDN numbers for SM Routing via an IWF (i.e. "MME number for MT SMS"). + +Additionally SGSNs and GGSNs are identified by GSN Addresses. These are the SGSN Address and the GGSN Address. + +A GSN Address shall be composed as shown in figure 9. + +![Figure 9: Structure of GSN Address. The diagram shows a GSN Address composed of three fields: Address Type (2 bits), Address Length (6 bits), and Address (4 to 16 octets).](f1091147d93cee4dfa88498610e395a7_img.jpg) + +The diagram illustrates the structure of a GSN Address. It is a horizontal bar divided into three segments. The first segment is labeled "Address Type" and has a width of "2 bits". The second segment is labeled "Address Length" and has a width of "6 bits". The third segment is labeled "Address" and has a width of "4 to 16 octets". Above the entire bar is a double-headed arrow labeled "GSN Address". + +Figure 9: Structure of GSN Address. The diagram shows a GSN Address composed of three fields: Address Type (2 bits), Address Length (6 bits), and Address (4 to 16 octets). + +**Figure 9: Structure of GSN Address** + +The GSN Address is composed of the following elements: + +- 1) The Address Type, which is a fixed length code (of 2 bits) identifying the type of address that is used in the Address field. +- 2) The Address Length, which is a fixed length code (of 6 bits) identifying the length of the Address field. +- 3) The Address, which is a variable length field which contains either an IPv4 address or an IPv6 address. + +Address Type 0 and Address Length 4 are used when Address is an IPv4 address. + +Address Type 1 and Address Length 16 are used when Address is an IPv6 address. + +The IP v4 address structure is defined in RFC 791 [14]. + +The IP v6 address structure is defined in RFC 2373 [15]. + +### 5.2 Identification of HLR for HLR restoration application + +HLR may also be identified by one or several "HLR id(s)", consisting of the leading digits of the IMSI (MCC + MNC + leading digits of MSIN). + +### 5.3 Identification of the HSS for SMS + +The HSS may also be identified by a HSS-ID. + +The HSS-ID shall consist of decimal digits (0 through 9) only and be composed of the MCC consisting of three digits, the MNC consisting of two or three digits and an index consisting of one to several digits. The number of digits in the HSS-ID shall not exceed 15. This composition is compatible with the IMSI one. The HSS-ID shall not be identical to the complete IMSI of a UE. + +NOTE: The composition of the HSS-ID is compatible with the composition of the IMSI in clause 2.2 for routing purposes. + +## 6 International Mobile Station Equipment Identity, Software Version Number and Permanent Equipment Identifier + +### 6.1 General + +The structure and allocation principles of the International Mobile station Equipment Identity and Software Version number (IMEISV) and the International Mobile station Equipment Identity (IMEI) are defined below. + +The Mobile Station Equipment is uniquely defined by the IMEI or the IMEISV. + +### 6.2 Composition of IMEI and IMEISV + +#### 6.2.1 Composition of IMEI + +The International Mobile station Equipment Identity (IMEI) is composed as shown in figure 10. + +![Figure 10: Structure of IMEI. The diagram shows the IMEI as a 15-digit number composed of three parts: TAC (8 digits), SNR (6 digits), and CD/SD (1 digit).](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +The diagram illustrates the structure of the IMEI (International Mobile Equipment Identity). It is shown as a horizontal sequence of three components within a rectangular box. Above the first component, 'TAC', is a double-headed arrow labeled '8 digits'. Above the second component, 'SNR', is a double-headed arrow labeled '6 digits'. Above the third component, 'CD/SD', is a double-headed arrow labeled '1 digit'. Below these three components, a single long double-headed arrow spans the entire width, labeled 'IMEI 15 digits'. + +Figure 10: Structure of IMEI. The diagram shows the IMEI as a 15-digit number composed of three parts: TAC (8 digits), SNR (6 digits), and CD/SD (1 digit). + +**Figure 10: Structure of IMEI** + +The IMEI is composed of the following elements (each element shall consist of decimal digits only): + +- Type Allocation Code (TAC). Its length is 8 digits; +- Serial Number (SNR) is an individual serial number uniquely identifying each equipment within the TAC. Its length is 6 digits; +- Check Digit (CD) / Spare Digit (SD): If this is the Check Digit see paragraph below; if this digit is Spare Digit it shall be set to zero, when transmitted by the MS. + +The IMEI (14 digits) is complemented by a Check Digit (CD). The Check Digit is not part of the digits transmitted when the IMEI is checked, as described below. The Check Digit is intended to avoid manual transmission errors, e.g. when customers register stolen MEs at the operator's customer care desk. The Check Digit is defined according to the Luhn formula, as defined in annex B. + +NOTE: The Check Digit is not applied to the Software Version Number. + +The security requirements of the IMEI are defined in 3GPP TS 22.016 [32]. + +#### 6.2.2 Composition of IMEISV + +The International Mobile station Equipment Identity and Software Version Number (IMEISV) is composed as shown in figure 11. + +![Diagram showing the structure of IMEISV. It consists of three parts: TAC (8 digits), SNR (6 digits), and SVN (2 digits). The TAC and SNR parts are grouped together as 'IMEISV 16 digits'.](95e259e8cb3519025066052af263f8c0_img.jpg) + +The diagram illustrates the structure of the IMEISV (International Mobile Equipment Identity-Software Version Number). It is composed of three main components: + +- TAC (Type Allocation Code):** 8 digits +- SNR (Serial Number):** 6 digits +- SVN (Software Version Number):** 2 digits + +The TAC and SNR components are grouped together and labeled as "IMEISV 16 digits". The SVN component is separate. The entire structure is shown within a rectangular box. + +Diagram showing the structure of IMEISV. It consists of three parts: TAC (8 digits), SNR (6 digits), and SVN (2 digits). The TAC and SNR parts are grouped together as 'IMEISV 16 digits'. + +**Figure 11: Structure of IMEISV** + +The IMEISV is composed of the following elements (each element shall consist of decimal digits only): + +- Type Allocation Code (TAC). Its length is 8 digits; +- Serial Number (SNR) is an individual serial number uniquely identifying each equipment within each TAC. Its length is 6 digits; +- Software Version Number (SVN) identifies the software version number of the mobile equipment. Its length is 2 digits. + +Regarding updates of the IMEISV: The security requirements of 3GPP TS 22.016 [32] apply only to the TAC and SNR, but not to the SVN part of the IMEISV. + +## 6.3 Allocation principles + +The Type Allocation Code (TAC) is issued by the GSM Association in its capacity as the Global Decimal Administrator. Further information can be found in the GSMA TS.06 [109] . + +Manufacturers shall allocate individual serial numbers (SNR) in a sequential order. + +For a given ME, the combination of TAC and SNR used in the IMEI shall duplicate the combination of TAC and SNR used in the IMEISV. + +The Software Version Number is allocated by the manufacturer. SVN value 99 is reserved for future use. + +## 6.4 Permanent Equipment Identifier (PEI) + +In 5GS, the Permanent Equipment Identifier (PEI) identifies a UE. + +The PEI is defined as: + +- a PEI type: in this release of the specification, it may indicate an IMEI or IMEISV, a MAC address or an IEEE Extended Unique Identifier (EUI-64); and +- dependent on the value of the PEI type: + - an IMEI as defined in clause 6.2.1; or + - an IMEISV as defined in clause 6.2.2; or + - a MAC address (48-bit MAC identifier, as defined in IETF RFC 7042 [132]); or + - an IEEE Extended Unique Identifier (EUI-64), for UEs not supporting any 3GPP access technologies, as defined in IEEE "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)" [136]. + +## 7 Identification of Voice Group Call and Voice Broadcast Call Entities + +### 7.1 Group Identities + +Logical groups of subscribers to the Voice Group Call Service or to the Voice Broadcast Service are identified by a Group Identity (Group ID). Group IDs for VGCS are unique within a PLMN. Likewise, Group IDs for VBS are unique within a PLMN. However, no uniqueness is required between the sets of Group IDs. These sets may be intersecting or even identical, at the option of the network operator. + +The Group ID is a number with a maximum value depending on the composition of the voice group call reference or voice broadcast call reference defined in clause 7.3. + +For definition of Group ID on the radio interface, A interface and Abis interface, see 3GPP TS 44.068 [46] and 3GPP TS 44.069 [47]. + +For definition of Group ID coding on MAP protocol interfaces, see 3GPP TS 29.002 [31]. + +VGCS or VBS shall also be provided for roaming. If this applies, certain Group IDs shall be defined as supra-PLMN Group IDs which have to be co-ordinated between the network operators and which shall be known in the networks and in the SIM. + +The format of the Group ID is identical for VBS and VGCS. + +### 7.2 Group Call Area Identification + +Grouping of cells into specific group call areas occurs in support of both the Voice Group Call Service and the Voice Broadcast Service. These service areas are known by a "Group Call Area Identity" (Group Call Area Id). No restrictions are placed on what cells may be grouped into a given group call area. + +The Group Call Area ID is a number uniquely assigned to a group call area in one network and with a maximum value depending on the composition of the voice group call reference or voice broadcast reference defined under 7.3. + +The formats of the Group Call Area ID for VGCS and the Group Call Area ID for VBS are identical. + +### 7.3 Voice Group Call and Voice Broadcast Call References + +Specific instances of voice group calls (VGCS) and voice broadcast calls (VBS) within a given group call area are known by a "Voice Group Call Reference" or by a "Voice Broadcast Call Reference" respectively. + +Each voice group call or voice broadcast call in one network is uniquely identified by its Voice Group Call Reference or Voice Broadcast Call Reference. The Voice Group Call Reference or Voice Broadcast Call Reference is composed of the Group ID and the Group Call Area ID. The composition of the group call area ID and the group ID can be specific for each network operator. + +For definition of Group Call Reference (with leading zeros inserted as necessary) on the radio interface, A interface and Abis interface, see 3GPP TS 24.008 [5], 3GPP TS 44.068 [46] and 3GPP TS 44.069 [47]. + +For definition of Group Call Reference (also known as ASCII Call Reference, Voice Group Call Reference or Voice Broadcast Call Reference) coding on MAP protocol interfaces, see 3GPP TS 29.002 [31]. + +The format is given in figure 12. + +![Diagram showing the relationship between Group Call Area ID, Group ID, and Voice Group Call Reference / Voice Broadcast Call Reference.](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) + +The diagram illustrates the relationship between two identifiers and a reference. On the left, a box contains the text 'Group Call Area ID'. On the right, a box contains the text 'Group ID'. Below these boxes, the text 'Voice Group Call Reference / Voice Broadcast Call Reference' is displayed. A double-headed horizontal arrow spans from the left box to the right box, positioned directly beneath the reference text, indicating that the reference is associated with both identifiers. + +Diagram showing the relationship between Group Call Area ID, Group ID, and Voice Group Call Reference / Voice Broadcast Call Reference. + +**Figure 12: Voice Group Call Reference / Voice Broadcast Call Reference** + +## 8 SCCP subsystem numbers + +Subsystem numbers are used to identify applications within network entities which use SCCP signalling. In GSM and UMTS, subsystem numbers may be used between PLMNs, in which case they are taken from the globally standardized range (1 - 31) or the part of the national network range (129 - 150) reserved for GSM/UMTS use between PLMNs. For use within a PLMN, they are taken from the part of the national network range (32 - 128 & 151 - 254) not reserved for GSM/UMTS use between PLMNs. + +### 8.1 Globally standardized subsystem numbers used for GSM/UMTS + +The following globally standardised subsystem numbers have been allocated for use by GSM/UMTS: + +0000 0110HLR (MAP); + +0000 0111VLR (MAP); + +0000 1000MSC (MAP); + +0000 1001EIR (MAP); + +0000 1010 is allocated for evolution (possible Authentication Centre). + +### 8.2 National network subsystem numbers used for GSM/UMTS + +The following national network subsystem numbers have been allocated for use within GSM/UMTS networks: + +1111 1000CSS (MAP); + +1111 1001PCAP; + +1111 1010BSC (BSSAP-LE); + +1111 1011MSC (BSSAP-LE); + +1111 1100SMLC (BSSAP-LE); + +1111 1101BSS O&M (A interface); + +1111 1110BSSAP (A interface). + +The following national network subsystem numbers have been allocated for use within and between GSM/UMTS networks: + +1000 1110RANAP; + +1000 1111RNSAP; + +1001 0001GMLC (MAP); + +1001 0010CAP; + +1001 0011gsmSCF (MAP) or IM-SSF (MAP) or Presence Network Agent; + +1001 0100SIWF (MAP); + +1001 0101SGSN (MAP); + +1001 0110GGSN (MAP). + +## 9 Definition of Access Point Name + +In the GPRS backbone, an Access Point Name (APN) is a reference to a GGSN. To support inter-PLMN roaming, the internal GPRS DNS functionality is used to translate the APN into the IP address of the GGSN. + +## 9A Definition of Data Network Name + +In 5GS, the Data Network Name (DNN) is equivalent to an APN in EPS. The DNN is a reference to a data network, it may be used e.g. to select SMF or UPF. + +The requirements for APN in clause 9 shall apply for DNN in a 5GS as well. + +In SNPNs the DNN Operator Identifier shall take the format + +"nid.mnc.mcc.gprs" + +where: + +"nid", "mnc" and "mcc" serve as invariable identifiers for the following digits. + +## 9.0 General + +Access Point Name as used in the Domain Name System (DNS) Procedures defined in 3GPP TS 29.303 [73] is specified in clause 19.4.2.2. + +## 9.1 Structure of APN + +The APN is composed of two parts as follows: + +- The APN Network Identifier; this defines to which external network the GGSN/PGW is connected and optionally a requested service by the MS. This part of the APN is mandatory. +- The APN Operator Identifier; this defines in which PLMN GPRS/EPS backbone the GGSN/PGW is located. This part of the APN is optional. + +NOTE 1: The APN Operator Identifier is mandatory on certain interfaces, see the relevant stage 3 specifications. + +The APN Operator Identifier is placed after the APN Network Identifier. An APN consisting of both the Network Identifier and Operator Identifier corresponds to a DNS name of a GGSN/PGW; the APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. + +The encoding of the APN shall follow the Name Syntax defined in RFC 2181 [18], RFC 1035 [19] and RFC 1123 [20]. The APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The APN is not terminated by a length byte of zero. + +NOTE 2: A length byte of zero is added by the SGSN/MME at the end of the APN before interrogating a DNS server. + +For the purpose of presentation, an APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +### 9.1.1 Format of APN Network Identifier + +The APN Network Identifier shall contain at least one label and shall have, after encoding as defined in clause 9.1 above, a maximum length of 63 octets. An APN Network Identifier shall not start with any of the strings "rac", "lac", "sgsn" or "rnc", and it shall not end in ".gprs", i.e. the last label of the APN Network Identifier shall not be "gprs". Further, it shall not take the value "\*". + +In order to guarantee uniqueness of APN Network Identifiers within or between GPRS/EPS PLMN, an APN Network Identifier containing more than one label shall correspond to an Internet domain name. This name should only be allocated by the PLMN if that PLMN belongs to an organisation which has officially reserved this name in the Internet domain. Other types of APN Network Identifiers are not guaranteed to be unique within or between GPRS/EPS PLMNs. + +An APN Network Identifier may be used to access a service associated with a GGSN/PGW. This may be achieved by defining: + +- an APN which corresponds to a FQDN of a GGSN/PGW, and which is locally interpreted by the GGSN/PGW as a request for a specific service, or +- an APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or an APN Network Identifier consisting of a Reserved Service Label alone, which indicates a GGSN/PGW by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have GPRS/EPS roaming agreements. + +### 9.1.2 Format of APN Operator Identifier + +The APN Operator Identifier is composed of three labels. The last label (or domain) shall be "gprs". The first and second labels together shall uniquely identify the GPRS/EPS PLMN. + +For each operator, there is a default APN Operator Identifier (i.e. domain name). This default APN Operator Identifier is derived from the IMSI as follows: + +"mnc.mcc.gprs" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + + and are derived from the components of the IMSI defined in clause 2.2. + +This default APN Operator Identifier is used for home routed inter-PLMN roaming situations when attempting to translate an APN consisting only of a Network Identifier into the IP address of the GGSN/PGW in the HPLMN. The PLMN may provide DNS translations for other, more human-readable, APN Operator Identifiers in addition to the default Operator Identifier described above. + +Alternatively, in the roaming case if the GGSN/PGW from the VPLMN is to be selected, the APN Operator Identifier for the UE is constructed from the serving network PLMN ID. In this case, the APN-OI replacement field, if received, shall be ignored. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "mnc.mcc.gprs" format of the APN OI shall be: + +- = 3 digits +- = 3 digits +- If there are only 2 significant digits in the MNC, one "0" digit is inserted at the left side to fill the 3 digits coding of MNC in the APN OI. + +As an example, the APN OI for MCC 345 and MNC 12 will be coded in the DNS as "mnc012.mcc345.gprs". + +The APN-OI replacement is used for selecting the GGSN/PGW for non-roaming and home routed scenarios. The format of the domain name used in the APN-OI replacement field (as defined in 3GPP TS 23.060 [3] and 3GPP TS 23.401 [72]) is the same as the default APN-OI as defined above except that it may be preceded by one or more labels each separated by a dot. It is up to the operators to determine what labels shall precede the "mnc.mcc.gprs" trailing labels (see clause 5.1.1.1 in TS 29.303 [73] and also clause 13.1 in TS 23.060 [3]). + +EXAMPLE 1: province1.mnc012.mcc345.gprs + +EXAMPLE 2: ggsn-cluster-A.provinceB.mnc012.mcc345.gprs + +The APN constructed using the APN-OI replacement field is only used for DNS translation. The APN when being sent to other network entities over GTP interfaces shall follow the rules as specified in 3GPP TS 23.060 [3] and 3GPP TS 23.401 [72]. + +## 9.2 Definition of the Wild Card APN + +The APN field in the HLR may contain a wild card APN if the HPLMN operator allows the subscriber to access any network of a given PDP Type. If an SGSN has received such a wild card APN, it may either choose the APN Network Identifier received from the Mobile Station or a default APN Network Identifier for addressing the GGSN when activating a PDP context. + +### 9.2.1 Coding of the Wild Card APN + +The wild card APN is coded as an APN with "\*" as its single label, (i.e. a length octet with value one, followed by the ASCII code for the asterisk). + +## 9.3 Definition of Emergency APN + +The Emergency APN (Em-APN) is an APN used to derive a PDN GW selected for IMS Emergency call support. The exact encoding of the Em-APN is the responsibility of each PLMN operator as it is only valid within a given PLMN. + +--- + +## 10 Identification of the Cordless Telephony System entities + +### 10.1 General description of CTS-MS and CTS-FP Identities + +Every CTS-FP broadcasts a local identity - the Fixed Part Beacon Identity (FPBI) - which contains an Access Rights Identity. Every CTS-MS has both an Access Rights Key and a CTS Mobile Subscriber Identity (CTSMSI). These operate as a pair. A CTS-MS is allowed to access any CTS-FP which broadcasts an FPBI which can be identified by any of the CTS-MS Access Rights Keys of that CTS-MS. The CTS-MS Access Rights Key contains the FPBI and the FPBI Length Indicator (FLI) indicating the relevant part of the FPBI used to control access. + +### 10.2 CTS Mobile Subscriber Identities + +#### 10.2.1 General + +Each CTS-MS has one or more temporary identities which are used for paging and to request access. The structure and allocation principles of the CTS Mobile Subscriber Identities (CTSMSI) are defined below. + +### 10.2.2 Composition of the CTSMSI + +![](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + + bit No 22 1 + +--------------------------------------+ + | | | | | | | | | | | | | | | | | | | | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + Type|<-----------Significant Part--------->| + + <----------- CTSMSI 22 bits ----------> + +``` + +Figure 13: Structure of CTSMSI + +The CTSMSI is composed of the following elements: + +- CTSMSI Type. Its length is 2 bits; +- Significant Part. Its length is 20 bits. + +The following CTSMSI Type values have been allocated for use by CTS: + +- 00 Default Individual CTSMSI; +- 01 Reserved; +- 10 Assigned Individual CTSMSI; +- 11 Assigned Connectionless Group CTSMSI. + +### 10.2.3 Allocation principles + +The default Individual CTSMSI contains the least significant portion of the IMSI. This is the default CTS-MS identity. + +Assigned CTSMSIs are allocated by the CTS-FP during enrolment, registration and other access procedures. Significant Part of the assigned CTSMSI shall be allocated in the range 00001-FFFFE. CTS-FP shall not allocate Significant Part equal to 00000 or to FFFFF and shall not allocate Assigned CTSMSI using Reserved Type value. Such assignments shall be ignored by the CTS-MS. + +Assigned CTSMSIs are allocated in ciphered mode. + +**NOTE:** The assigned individual CTSMSI should be updated whenever it is sent in clear text on the CTS radio interface during RR connection establishment. + +The value FFFFF from the set of Assigned Connectionless Group CTSMSI shall be considered in all CTS-MS as the value of the Connectionless Broadcast Identifier. + +### 10.2.4 CTSMSI hexadecimal representation + +The 22 bits of CTSMSI are padded with 2 leading zeroes to give a 6 digit hexadecimal value. + +EXAMPLE: binary CTSMSI value: 11 1001 0010 0000 1011 1100 + hexadecimal CTSMSI value: 39 20 BC. + +## 10.3 Fixed Part Beacon Identity + +### 10.3.1 General + +Each CTS-FP has one Fixed Part Beacon Identity known by the enrolled CTS-MSs. The FPBI is periodically broadcast on the BCH logical channel so that the CTS-MSs are able to recognise the identity of the CTS-FP. The FPBI contains an Access Rights Identity. + +Enrolled CTS-MSs shall store the FPBI to which their assigned CTSMSIs are related. + +Below the structure and allocation principles of the Fixed Part Beacon Identity (FPBI) are defined. + +## 10.3.2 Composition of the FPBI + +### 10.3.2.1 FPBI general structure + +![Figure 14: General structure of FPBI. A diagram showing a 19-bit word. Bit 19 is at the top left, and bit 1 is at the top right. The word is divided into two parts: 'Type' (bits 19 and 18) and 'Significant Part' (bits 17 down to 1). A dashed line with arrows at both ends below the word indicates the total length is 'FPBI 19 bits'.](73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg) + +Figure 14: General structure of FPBI. A diagram showing a 19-bit word. Bit 19 is at the top left, and bit 1 is at the top right. The word is divided into two parts: 'Type' (bits 19 and 18) and 'Significant Part' (bits 17 down to 1). A dashed line with arrows at both ends below the word indicates the total length is 'FPBI 19 bits'. + +**Figure 14: General structure of FPBI** + +The FPBI is composed of the following elements: + +- FPBI Type. Its length is 2 bits; +- FPBI Significant Part. Its length is 17 bits. + +NOTE: The three LSBs bits of the FPBI form the 3-bit training sequence code (TSC). See 3GPP TS 45.056 [35]. + +The following FPBI Type values have been allocated for use by CTS: + +- 00 FPBI class A: residential and single-cell systems; +- 01 FPBI class B: multi-cell PABXs. + +All other values are reserved and CTS-MSs shall treat these values as FPBI class A. + +### 10.3.2.2 FPBI class A + +This class is intended to be used for small residential and private (PBX) single cell CTS-FP. + +![Figure 15: Structure of FPBI class A. A diagram showing a 19-bit word. Bit 19 is at the top left, and bit 1 is at the top right. The word is divided into two parts: 'Type' (bits 19 and 18, with values '0' and '0' shown) and 'FPN' (bits 17 down to 1). A dashed line with arrows at both ends below the word indicates the total length is 'FPBI 19 bits'.](1b3c088f23921d4eeb45ffc05586e59b_img.jpg) + +Figure 15: Structure of FPBI class A. A diagram showing a 19-bit word. Bit 19 is at the top left, and bit 1 is at the top right. The word is divided into two parts: 'Type' (bits 19 and 18, with values '0' and '0' shown) and 'FPN' (bits 17 down to 1). A dashed line with arrows at both ends below the word indicates the total length is 'FPBI 19 bits'. + +**Figure 15: Structure of FPBI class A** + +The FPBI class A is composed of the following elements: + +- FPBI Class A Type. Its length is 2 bits and its value is 00; +- Fixed Part Number (FPN). Its length is 17 bits. The FPN contains the least significant bits of the Serial Number part of the IFPEI. + +The FPBI Length Indicator shall be set to 19 for a class A FPBI. + +### 10.3.2.3 FPBI class B + +This class is reserved for more complex private installation such as multi-cell PABXs. + +![](01e00200a536673d6cd0e6d8705047a0_img.jpg) + +``` + +bit No 19 1 + +---------------------------------------+ + |0 1|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_| + +---+-----------------------------------+ + Type| CNN + FPN + RPN | + + <---------------- FPBI 19 bits ---------------> + +``` + +**Figure 16: Structure of FPBI class B** + +The FPBI class B is composed of the following elements: + +- FPBI Class B Type. Its length is 2 bits and its value is 01; +- CTS Network Number (CNN). Its length is defined by the manufacturer or the system installer; +- Fixed Part Number (FPN). Its length is defined by the manufacturer or the system installer; +- Radio Part Number (RPN) assigned by the CTS manufacturer or system installer. Its length is defined by the manufacturer or the system installer. + +NOTE: RPN is used to separate a maximum of $2^{\text{RPN length}}$ different cells from each other. This defines a cluster of cells supporting intercell handover. RPN length is submitted to a CTS-MS as a result of a successful attachment. + +The FPBI Length Indicator shall be set to (2 + CNN Length) for a class B FPBI. + +### 10.3.3 Allocation principles + +The FPBI shall be allocated during the CTS-FP initialisation procedure. Any change to the value of the FPBI of a given CTS-FP shall be considered as a CTS-FP re-initialisation; i.e. each enrolled CTS-MS needs to be enrolled again. + +FPBI are not required to be unique (i.e. several CTS-FP can have the same FPBI in different areas). Care should be taken to limit CTS-MS registration attempts to a fixed part with the same FPBI as another fixed part. + +## 10.4 International Fixed Part Equipment Identity + +### 10.4.1 General + +The structure and allocation principles of the International Fixed Part Equipment Identity (IFPEI) are defined below. + +### 10.4.2 Composition of the IFPEI + +![](1878426572e3fcbc4483578a685d7c7d_img.jpg) + +``` + + 6 digits 2d 6 digits 2d + <----------><---><----------><---> + +-----------++---++-----------++---+ + | || || || | + +-+-+-+-+-+-++-+-++-+-+-+-+-+-++-+-+ + TAC FAC SNR SVN + + IFPEI 16 digits + <----------------------------------> + +``` + +**Figure 17: Structure of IFPEI** + +The IFPEI is composed of the following elements (each element shall consist of decimal digits only): + +- Type Approval Code (TAC). Its length is 6 decimal digits; +- Final Assembly Code (FAC). Its length is 2 decimal digits; +- Serial Number (SNR). Its length is 6 decimal digits; +- Software Version Number (SVN). Its length is 2 decimal digits; + +- Software Version Number (SVN) identifies the software version number of the fixed part equipment. Its length is 2 digits. + +Regarding updates of the IFPEI: the TAC, FAC and SNR shall be physically protected against unauthorised change (see 3GPP TS 42.009 [36]); i.e. only the SVN part of the IFPEI can be modified. + +### 10.4.3 Allocation and assignment principles + +The Type Approval Code (TAC) is issued by a global administrator. + +The place of final assembly (FAC) is encoded by the manufacturer. + +Manufacturers shall allocate unique serial numbers (SNR) in a sequential order. + +The Software Version Number (SVN) is allocated by the manufacturer after authorisation by the type approval authority. SVN value 99 is reserved for future use. + +## 10.5 International Fixed Part Subscription Identity + +### 10.5.1 General + +The structure and allocation principles of the International Fixed Part Subscription Identity (IFPSI) are defined below. + +### 10.5.2 Composition of the IFPSI + +![Diagram illustrating the structure of IFPSI. It shows a hierarchical breakdown of the IFPSI into its components: MCC (3 digits), CON (3 digits), and FPIN (up to 15 digits). The NFPSI is shown as the combination of CON and FPIN. The IFPSI is the combination of MCC and NFPSI.](f9528ea5b0d2cd0192b7242e5a6af969_img.jpg) + +``` + + No more than 15 digits + <-----> + 3d 3d + <-----><-----><-----//-----> + +-----+-----+-----//-----+ + | | | | | | | | | | | | | | | | | | + +-----+-----+-----//-----+ + MCC CON FPIN + + NFPSI + <-----> + + IFPSI + <-----> + +``` + +Diagram illustrating the structure of IFPSI. It shows a hierarchical breakdown of the IFPSI into its components: MCC (3 digits), CON (3 digits), and FPIN (up to 15 digits). The NFPSI is shown as the combination of CON and FPIN. The IFPSI is the combination of MCC and NFPSI. + +**Figure 18: Structure of IFPSI** + +The IFPSI is composed of the following elements (each element shall consist of decimal digits only): + +- Mobile Country Code (MCC) consisting of three digits. The MCC identifies the country of the CTS-FP subscriber (e.g. 208 for France); +- CTS Operator Number (CON). Its length is three digits; +- Fixed Part Identification Number (FPIN) identifying the CTS-FP subscriber. + +The National Fixed Part Subscriber Identity (NFPSI) consists of the CTS Operator Number and the Fixed Part Identification Number. + +### 10.5.3 Allocation and assignment principles + +IFPSI shall consist of decimal characters (0 to 9) only. + +The allocation of Mobile Country Codes (MCCs) is administered by the ITU. + +The allocation of CTS Operator Number (CON) and the structure of National Fixed Part Subscriber Identity (NFPSI) may be responsibility of each national numbering plan administrator. + +CTS Operators shall allocate unique Fixed Part Identification Numbers. + +## 11 Identification of Localised Service Area + +Cells may be grouped into specific localised service areas. Each localised service area is identified by a localised service area identity (LSA ID). No restrictions are placed on what cells may be grouped into a given localised service area. + +The LSA ID can either be a PLMN significant number or a universal identity. This shall be known both in the networks and in the SIM. + +The LSA ID consists of 24 bits, numbered from 0 to 23, with bit 0 being the LSB. Bit 0 indicates whether the LSA is a PLMN significant number or a universal LSA. If the bit is set to 0 the LSA is a PLMN significant number; if it is set to 1 it is a universal LSA. + +The LSA ID shall be composed as shown in figure 19: + +![Figure 19: Structure of LSA ID. The diagram shows a 24-bit LSA ID. The Most Significant Bit (MSB) is bit 23, and the Least Significant Bit (LSB) is bit 0. The MSB is a single bit, and the remaining 23 bits are grouped together. A double-headed arrow below the diagram indicates the full 24-bit LSA ID.](396197257cf9437b526bb6585b6a9c8a_img.jpg) + +The diagram illustrates the structure of the LSA ID. It is a 24-bit identifier. The left side, labeled 'MSB', contains 23 bits. The right side, labeled 'LSB', contains 1 bit. A double-headed arrow labeled 'LSA ID' spans the entire 24 bits. + +Figure 19: Structure of LSA ID. The diagram shows a 24-bit LSA ID. The Most Significant Bit (MSB) is bit 23, and the Least Significant Bit (LSB) is bit 0. The MSB is a single bit, and the remaining 23 bits are grouped together. A double-headed arrow below the diagram indicates the full 24-bit LSA ID. + +Figure 19: Structure of LSA ID + +## 12 Identification of PLMN, RNC, Service Area, CN domain and Shared Network Area + +The following clauses describe identifiers which are used by both the CN and the UTRAN across the Iu interface. For identifiers which are solely used within the UTRAN, see 3GPP TS 25.401 [16]. + +NOTE: in the following clauses, the double vertical bar notation || indicates the concatenation operator. + +### 12.1 PLMN Identifier + +A Public Land Mobile Network is uniquely identified by its PLMN identifier. PLMN-Id consists of Mobile Country Code (MCC) and Mobile Network Code (MNC). + +- PLMN-Id = MCC || MNC + +The MCC and MNC are predefined within a UTRAN, and set in the RNC via O&M. + +### 12.2 CN Domain Identifier + +A CN Domain Edge Node is identified within the UTRAN by its CN Domain Identifier. The CN Domain identifier is used over UTRAN interfaces to identify a particular CN Domain Edge Node for relocation purposes. The CN Domain identifier for Circuit Switching (CS) consists of the PLMN-Id and the LAC, whereas for Packet Switching (PS) it consists of the PLMN-Id, the LAC, and the RAC of the first accessed cell in the target RNS. + +The two following CN Domain Identifiers are defined: + +- CN CS Domain-Id = PLMN-Id || LAC +- CN PS Domain-Id = PLMN-Id || LAC || RAC + +The LAC and RAC are defined by the operator, and set in the RNC via O&M. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +## 12.3 CN Identifier + +A CN node is uniquely identified within a PLMN by its CN Identifier (CN-Id). The CN-Id together with the PLMN identifier globally identifies the CN node. The CN-Id together with the PLMN-Id is used as the CN node identifier in RANAP signalling over the Iu interface. + +- Global CN-Id = PLMN-Id || CN-Id + +The CN-Id is defined by the operator, and set in the nodes via O&M. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +## 12.4 RNC Identifier + +An RNC node is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of an RNC is used in the UTRAN, in a GERAN which is operating in GERAN Iu mode and between them. A BSC which is part of a GERAN operating in Iu mode is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of a BSC is used in a GERAN which is operating in GERAN Iu mode, in the UTRAN and between them. RNC-Id together with the PLMN identifier globally identifies the RNC. The RNC-Id on its own or the RNC-Id together with the PLMN-Id is used as the RNC identifier in the UTRAN Iub, Iur and Iu interfaces. The SRNC-Id is the RNC-Id of the SRNC. The C-RNC-Id is the RNC-Id of the controlling RNC. The D-RNC-Id is the RNC Id of the drift RNC. + +- Global RNC-Id = PLMN-Id || RNC-Id + +The RNC-Id is defined by the operator, and set in the RNC via O&M + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +For the usage of this identifier on Iur-g, see 3GPP TS 43.130 [43]. + +## 12.5 Service Area Identifier + +The Service Area Identifier (SAI) is used to identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN. + +The Service Area Code (SAC) together with the PLMN-Id and the LAC constitute the Service Area Identifier. + +- SAI = PLMN-Id || LAC || SAC + +The SAC is defined by the operator, and set in the RNC via O&M. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. 3GPP TS 25.423 [37] and 3GPP TS 25.419 [38] define the use of this identifier in RNSAP and SABP signalling. + +A cell may belong to one or two Service Areas. If it belongs to two Service Areas, one is applicable in the Broadcast (BC) domain and the other is applicable in both the CS and PS domains. + +The Broadcast (BC) domain requires that its Service Areas each consist of only one cell. This does not limit the use of Service Areas for other domains. Refer to 3GPP TS 25.410 [39] for a definition of the BC domain. + +## 12.6 Shared Network Area Identifier + +The Shared Network Area Identifier (SNA-Id) is used to identify an area consisting of one or more Location Areas. Such an area is called a Shared Network Area and can be used to grant access rights to parts of a Shared Network to a UE in connected mode (see 3GPP TS 25.401 [39]). + +The Shared Network Area Identifier consists of the PLMN-Id followed by the Shared Network Area Code (SNAC). + +- SNA-Id = PLMN-Id || SNAC + +The SNAC is defined by the operator. + +For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413 [17]. + +## 12.7 Stand-Alone Non-Public Network Identifier + +### 12.7.1 Network Identifier (NID) + +A Stand-Alone Non-Public Network (SNPN) is identified by a combination of PLMN-Identifier (see clause 12.1) and Network Identifier (NID) (see 3GPP TS 23.501 [119] clause 5.30.2). + +The NID shall consist of 11 hexadecimal digits, one digit for representing an assignment mode and 10 digits for a NID value, as shown in figure 12.7.1-1. + +![Diagram of Network Identifier (NID) structure showing Assignment mode (1 digit) and NID value (10 digits)](c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg) + +The diagram illustrates the structure of a Network Identifier (NID). It is a rectangular box containing two main sections: 'Assignment mode' and 'NID value'. Below the 'Assignment mode' section, there is a double-headed arrow labeled 'one hexadecimal digit'. Below the 'NID value' section, there is a double-headed arrow labeled '10 hexadecimal digits'. A larger double-headed arrow at the bottom, spanning both sections, is labeled 'Network Identifier'. + +Diagram of Network Identifier (NID) structure showing Assignment mode (1 digit) and NID value (10 digits) + +**Figure 12.7.1-1: Network Identifier (NID)** + +The NID can be assigned using the following assignment models: + +- a) Self-assignment: NIDs are chosen individually by SNPNs at deployment time; this assignment model is encoded by setting the assignment mode to value 1. +- b) Coordinated assignment: NIDs are assigned using one of the following two options: + - option 1: the NID assigned such that it is globally unique independent of the PLMN ID used. Option 1 of this assignment model is encoded by setting the assignment mode to value 0. + - option 2: the NID assigned such that the combination of the NID and the PLMN ID is globally unique. Option 2 of this assignment model is encoded by setting the assignment mode to value 2. + +The self-assignment NID model should not be used, if UE accesses SNPN using e.g. credentials from Credentials Holder via AAA Server, as specified in clause 5.30.2.1 in 3GPP TS 23.501 [119]. + +Other Assignment mode values are spare, for future use. + +### 12.7.2 NID of assignment mode 0 + +The NID value of a NID of the assignment mode 0 consists of a NID PEN and a NID code, as shown in figure 12.7.2-1. + +The NID PEN is a private enterprise number issued to service provider of the SNPN by Internet Assigned Numbers Authority (IANA) in its capacity as the private enterprise number administrator, as maintained at + +Note: The private enterprise number issued by IANA is a decimal number that needs to be converted to a fixed length 8 digit hexadecimal number when used within the NID. E.g. 32473 is converted to 00007ed9. + +The NID code identifies the SNPN within the service provider identified by the NID PEN. + +![Diagram of NID of assignment mode 0 structure](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) + +The diagram illustrates the structure of the Network Identifier (NID) for assignment mode 0. It is divided into three main fields: 'Assignment mode (Assignment mode 0)', 'NID PEN', and 'NID code'. Below the 'Assignment mode' field, a double-headed arrow indicates it represents 'one hexadecimal digit'. Below the 'NID PEN' field, a double-headed arrow indicates it represents '8 hexadecimal digits'. Below the 'NID code' field, a double-headed arrow indicates it represents '2 hexadecimal digits'. A long double-headed arrow at the bottom, spanning the 'NID PEN' and 'NID code' fields, is labeled 'Network Identifier'. + +Diagram of NID of assignment mode 0 structure + +**Figure 12.7.2-1: NID of assignment mode 0** + +### 12.7.3 Group ID for Network Selection (GIN) + +The "Group ID for Network Selection" (GIN) identifies a group (e.g. a consortium) of Credential Holders or Default Credential Servers (see 3GPP TS 23.501 [119], clause 5.30.2) that can be used to authenticate and authorize the access to an SNPN; the GIN is used during SNPN selection by the UE to enhance the likelihood of selecting a preferred SNPN. + +The GIN has the same structure as the SNPN identifier (see clause 12.7.1) and shall consist of MCC, MNC and NID, where the NID contains 44 bits, i.e. 11 hexadecimal digits; one digit (4 bits) for representing an assignment mode and 10 digits (40 bits) for a NID value, as shown in figure 12.7.1-1. + +The GIN can be assigned using the following assignment models: + +- Self-assignment: GINs are chosen individually and may therefore not be unique; this assignment model is encoded by setting the assignment mode to value 1. +- Coordinated assignment: GINs are assigned using one of the following two options: + - option 1: the GIN is assigned such that the NID is globally unique independent of the PLMN ID used. Option 1 of this assignment model is encoded by setting the assignment mode to value 0. + - option 2: the GIN is assigned such that the combination of the NID and the PLMN ID is globally unique. Option 2 of this assignment model is encoded by setting the assignment mode to value 2. + +Other Assignment mode values are spare, for future use. + +--- + +## 13 Numbering, addressing and identification within the IP multimedia core network subsystem + +### 13.1 Introduction + +This clause describes the format of the parameters needed to access the IP multimedia core network subsystem. For further information on the use of the parameters see 3GPP TS 23.228 [24] and 3GPP TS 29.163 [63]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. For more information on the ".invalid" top level domain see IETF RFC 2606 [64]. + +### 13.2 Home network domain name + +The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +For 3GPP systems, if there is no ISIM application, the UE shall derive the home network domain name from the IMSI as described in the following steps: + +1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning. +2. Use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name. +3. Add the label "ims." to the beginning of the domain. + +An example of a home network domain name is: + +IMSI in use: 234150999999999; + +where: + +- MCC = 234; +- MNC = 15; and +- MSIN = 0999999999, + +which gives the home network domain name: ims.mnc015.mcc234.3gppnetwork.org. + +The Home Network Domain for a Stand-alone Non-Public Network (SNPN) subscriber with an IMSI-based SUPI type, shall use the IMSI-based derivation described above, and append nid of the SNPN, between the "ims." and "mnc" labels. + +NOTE: The UE takes the NID from "list of subscriber data" as specified in 3GPP TS 23.122 [139], from the entry selected by the UE. + +An example of a home SNPN network domain name using the above IMSI and NID 000007ed9d5 is ims.nid000007ed9d5.mnc015.mcc234.3gppnetwork.org. + +The Home Network Domain for a Stand-alone Non-Public Network (SNPN) subscriber identified by a SUPI containing a network-specific identifier that takes the form of an NAI consists of the string "ims." appended with the realm part of the NAI. + +For 3GPP2 systems, if there is no IMC present, the UE shall derive the home network domain name as described in Annex C of 3GPP2 X.S0013-004 [67]. + +## 13.3 Private User Identity + +The private user identity shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. + +NOTE 1: It is possible for a representation of the IMSI to be contained within the NAI for the private identity. + +For 3GPP systems, the private user identity used for the user shall be as specified in clause 4.2 of 3GPP TS 24.229 [81] and in 3GPP TS 23.228 [24] Annex E.3.1. If the private user identity is not known, the private user identity shall be derived from the IMSI. + +The following steps show how to build the private user identity out of the IMSI: + +1. Use the whole string of digits as the username part of the private user identity; and +2. convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 13.2. + +The result will be a private user identity of the form "@ims.mnc.mcc.3gppnetwork.org". For example: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identity then takes the form "234150999999999@ims.mnc015.mcc234.3gppnetwork.org".. + +The private user identity for a Stand-alone Non-Public Network (SNPN) subscriber with an IMSI-based SUPI type, shall use the IMSI-based derivation described above, and append nid of the SNPN, between the "ims." and "mnc" labels. + +NOTE 2: The UE takes the NID from "list of subscriber data" as specified in 3GPP TS 23.122 [139], from the entry selected by the UE. + +For an SNPN, if IMSI is as above, and for a NID of 000007ed9d5, the private user identity takes the form "234150999999999@ims.nid000007ed9d5.mnc015.mcc234.3gppnetwork.org". + +The Private User Identity for a Stand-alone Non-Public Network (SNPN) subscriber identified by a SUPI containing a network-specific identifier that takes the form of an NAI is obtained as follows: the username is the same as the username in the NAI, and the realm portion is identical with the Home domain defined in clause 13.2. + +For 3GPP2 systems, if there is no IMC present, the UE shall derive the private user identity as described in Annex C of 3GPP2 X.S0013-004 [67]. + +## 13.4 Public User Identity + +A Public User Identity is any identity used by a user within the IMS subsystem for requesting communication to another user. + +The Public User Identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a Tel URI (see IETF RFC 3966 [45]). + +The 3GPP specifications describing the interfaces over which Public User Identities are transferred specify the allowed Public User Identity formats, in particular 3GPP TS 24.229 [81] for SIP signalling interfaces, 3GPP TS 29.229 [95] for Cx and Dx interfaces, 3GPP TS 29.329 [96] for Sh interface, 3GPP TS 29.165 [97] for II-NNI interface. + +In the case the user identity is a telephone number, it shall be represented either by a Tel URI or by a SIP URI that includes a "user=phone" URI parameter and a "userinfo" part that shall follow the same format as the Tel URI. + +According to 3GPP TS 24.229 [81], the UE can use either: + +- a global number as defined in IETF RFC 3966 [45] and following E.164 format, as defined by ITU-T Recommendation E.164 [10] or +- a local number, that shall include a "phone-context" parameter that identifies the scope of its validity, as per IETF RFC 3966 [45]. + +According to 3GPP TS 29.165 [97] a global number as defined in IETF RFC 3966 [45] shall be used in a tel-URI or in the user portion of a SIP URI with the user=phone parameter when conveyed via a non-roaming II-NNI except when agreement exists between the operators to also allow other kinds of numbers. + +According to 3GPP TS 29.229 [95] and 3GPP TS 29.329 [96] the canonical forms of SIP URI and Tel URI shall be used over the corresponding Diameter interfaces. + +The canonical form of a SIP URI for a Public User Identity shall take the form "sip:username@domain" as specified in IETF RFC 3261 [26], clause 10.3. SIP URI comparisons shall be performed as defined in IETF RFC 3261 [26], clause 19.1.4. + +The canonical form of a Tel URI for a Public User Identity shall take the form "tel:+" (max number of digits is 15), that represents an E.164 number and shall contain a global number without parameters and visual separators (see IETF RFC 3966[45], clause 3). Tel URI comparisons shall be performed as defined in IETF RFC 3966[45], clause 4. + +Public User Identities are stored in the HSS either as a distinct Public User Identity or as a Wildcarded Public User Identity. A distinct Public User Identity contains the Public User Identity that is used in routing and it is explicitly provisioned in the HSS. + +## 13.4A Wildcarded Public User Identity + +Public User Identities may be stored in the HSS as Wildcarded Public User Identities. A Wildcarded Public User Identity represents a collection of Public User Identities that share the same service profile and are included in the same implicit registration set. Wildcarded Public User Identities enable optimisation of the operation and maintenance of the nodes for the case in which a large amount of users are registered together and handled in the same way by the network. The format of a Wildcarded Public User Identity is the same as for the Wildcarded PSI described in clause 13.5. + +## 13.4B Temporary Public User Identity + +For 3GPP systems, if there is no ISIM application to host the Public User Identity, a Temporary Public User Identity shall be derived, based on the IMSI. The Temporary Public User Identity shall be of the form as described in clause 13.4 and shall consist of the string "sip:" appended with a username and domain portion equal to the IMSI derived Private User Identity, as described in clause 13.2. An example using the same example IMSI from clause 13.2 can be found below: + +EXAMPLE: "sip:234150999999999@ims.mnc015.mcc234.3gppnetwork.org". + +The temporary public user identity for a Stand-alone Non-Public Network (SNPN) subscriber with an IMSI-based SUPI type, shall use the IMSI-based derivation described above, and append nid of the SNPN, in between the "ims." and "mnc" labels. + +NOTE: The UE takes the NID from "list of subscriber data" as specified in 3GPP TS 23.122 [139], from the entry selected by the UE. + +EXAMPLE for an SNPN: "sip:234150999999999@ims.nid000007ed9d5.mnc015.mcc234.3gppnetwork.org". + +The temporary Public User Identity for a Stand-alone Non-Public Network (SNPN) subscriber identified by a SUPI containing a network-specific identifier that takes the form of an NAI consists of the string "sip:" appended with a username and realm portion equal to the NAI SUPI derived Private User Identity. + +For 3GPP2 systems, if there is no IMC present, the UE shall derive the public user identity as described in Annex C of 3GPP2 X.S0013-004 [67]. + +## 13.5 Public Service Identity (PSI) + +The public service identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a Tel URI (see IETF RFC 3966 [45]). A public service identity identifies a service, or a specific resource created for a service on an application server. The domain part is pre-defined by the IMS operators and the IMS system provides the flexibility to dynamically create the user part of the PSIs. + +The PSIs are stored in the HSS either as a distinct PSI or as a wildcarded PSI. A distinct PSI contains the PSI that is used in routing, whilst a wildcarded PSI represents a collection of PSIs. Wildcarded PSIs enable optimisation of the operation and maintenance of the nodes. A wildcarded PSI consists of a delimited regular expression located either in the userinfo portion of the SIP URI or in the telephone-subscriber portion of the Tel URI. The regular expression in the wildcarded PSI shall take the form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [60]. The delimiter shall be the exclamation mark character ("!"). If more than two exclamation mark characters are present in the userinfo portion or telephone-subscriber portion of a wildcarded PSI then the outside pair of exclamation mark characters is regarded as the pair of delimiters (i.e. no exclamation mark characters are allowed to be present in the fixed parts of the userinfo portion or telephone-subscriber portion). + +When stored in the HSS, the wildcarded PSI shall include the delimiter character to indicate the extent of the part of the PSI that is wildcarded. It is used to separate the regular expression from the fixed part of the wildcarded PSI. + +Example: The following PSI could be stored in the HSS - "sip:chatlist!.\*!@example.com". + +When used on an interface, the exclamation mark characters within a PSI shall not be interpreted as delimiter.. + +Example: The following PSIs communicated in interface messages to the HSS will match to the wildcarded PSI of "sip:chatlist!.\*!@example.com" stored in the HSS: + +sip:chatlist1@example.com + +sip:chatlist2@example.com + +sip:chatlist42@example.com + +sip:chatlistAbC@example.com + +sip:chatlist!1@example.com + +Note that sip:chatlist1@example.com and sip:chatlist!1@example.com are regarded different specific PSIs, both matching the wildcarded PSI sip:chatlist!.\*!@example.com. + +When used by an application server to identify a specific resource (e.g. a chat session) over Inter Operator Network to Network Interface (II-NNI), the PSI should be a SIP URI without including a port number. + +NOTE: Based on local configuration policy, a PSI can be routed over Inter Operator Network to Network Interface (II-NNI). Details of this routing are operator specific and out of scope of this specification. + +## 13.5A Private Service Identity + +The Private Service Identity is applicable to a PSI user and is similar to a Private User Identity in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [53]. The Private Service Identity is operator defined and although not operationally used for registration, authorisation and authentication in the same way as Private User Identity, it enables Public Service Identities to be associated to a Private Service Identity which is required for compatibility with the Cx procedures. + +## 13.6 Anonymous User Identity + +The Anonymous User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Anonymous User Identity shall take the form "sip:user@domain". The user part shall be the string "anonymous" and the domain part shall be the string "anonymous.invalid". The full SIP URI for Anonymous User Identity is thus: + +"sip:anonymous@anonymous.invalid" + +For more information on the Anonymous User Identity and when it is used, see 3GPP TS 29.163 [63]. + +## 13.7 Unavailable User Identity + +The Unavailable User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Unavailable User Identity shall take the form "sip:user@domain". The user part shall be the string "unavailable" and the domain part shall be the string "unknown.invalid". The full SIP URI for Unavailable User Identity is thus: + +"sip:unavailable@unknown.invalid" + +For more information on the Unavailable User Identity and when it is used, see 3GPP TS 29.163 [63]. + +## 13.8 Instance-ID + +An instance-id is a SIP Contact header parameter that uniquely identifies the SIP UA performing a registration. + +When an IMEI is available, the instance-id shall take the form of a IMEI URN (see RFC 7254 [79]). The format of the instance-id shall take the form "urn:gsma:imei:" where by the imeival shall contain the IMEI encoded as defined in RFC 7254 [79]. The optional and parameters shall not be included in the instance-id. RFC 7255 [104] specifies additional considerations for using the IMEI as an instance-id. An example of such an instance-id is as follows: + +EXAMPLE: urn:gsma:imei:90420156-025763-0 + +If no IMEI is available, the instance-id shall take the form of a string representation of a UUID as a URN as defined in IETF RFC 4122 [80]. An example of such an instance-id is as follows: + +EXAMPLE: urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 + +For more information on the instance-id and when it is used, see 3GPP TS 24.229 [81]. + +## 13.9 XCAP Root URI + +### 13.9.1 XCAP Root URI on Ut interface + +#### 13.9.1.1 General + +XCAP Root URI is an HTTP URI that represents the XCAP Root. Although a valid URI, the XCAP Root URI does not correspond to an actual resource. + +#### 13.9.1.2 Format of XCAP Root URI + +The XCAP Root URI, as defined in IETF RFC 4825 [94], is an HTTP URI that should have the following format: + +"http://xcap." + +in which "" identifies the domain hosting the XCAP server. + +NOTE 1: The XCAP Root URI does not contain a port portion or an abs path portion of a standard HTTP URI. + +If a preconfigured or provisioned XCAP Root URI is available then the UE shall use it. When a preconfigured or provisioned XCAP Root URI does not exist then the UE shall create the XCAP Root URI as follows: + +- The first label shall be "xcap". +- The next label(s) shall identify the home network as follows: + 1. When the UE has an ISIM, the domain name from the IMPI shall be used (see 3GPP TS 31.103 [93]) as follows: + - a. if the last two labels of the domain name from the IMPI are "3gppnetwork.org": + - i. the next labels shall be all labels of the domain name from the IMPI apart from the last two labels; and + - ii. the last three labels shall be "pub.3gppnetwork.org"; + - b. if the last two labels of the domain name from the IMPI are other than the "3gppnetwork.org": + - i. the next labels shall be all labels of the domain name from the IMPI; + 2. When the UE has a USIM and does not have ISIM, the home network shall be "ims.mnc.mcc.pub.3gppnetwork.org" where and shall be derived from the components of the IMSI defined in clause 2.2. If there are only two significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the FQDN of XCAP Root URI. + +As an example for the case when the UE has ISIM, where the IMPI is "user@operator.com", the overall XCAP Root URI used by the UE would be: + +"http://xcap.operator.com". + +As an example for the case when the UE has ISIM, where the IMPI is "234150999999999@ims.mnc015.mcc234.3gppnetwork.org", the overall XCAP Root URI used by the UE would be: + +"xcap.ims.mnc015.mcc234.pub.3gppnetwork.org". + +As an example for the case when the UE has USIM and does not have ISIM, where the MCC is 345 and the MNC is 12, the overall XCAP Root URI created and used by the UE would be: + +"xcap.ims.mnc012.mcc345.pub.3gppnetwork.org" + +## 13.10 Default Conference Factory URI for MMTel + +The Default Conference Factory URI for MMTel shall take the form of a SIP URI (see IETF RFC 3261 [26]) with a host portion set to the home network domain name as described in clause 13.2 prefixed with "conf-factory.". The user portion shall be set to "mmtel". + +Examples of the Default Conference Factory URI for MMTel can be found below: + +EXAMPLE 1: "sip:mmtel@conf-factory.operator.com" + +when the UE has a home network domain name of operator.com. + +EXAMPLE 2: "sip:mmtel@conf-factory.ims.mnc015.mcc234.3gppnetwork.org" + +for 3GPP systems, when the UE with no ISIM application has a home network domain name of ims.mnc015.mcc234.3gppnetwork.org derived from the same example IMSI as described in clause 13.2. + +## 13.11 Unknown User Identity + +The Unknown User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). A SIP URI for an Unknown User Identity shall take the form "sip:user@domain". The user part shall be the string "unknown" and the domain part shall be the string "unknown.invalid". The full SIP URI for Unknown User Identity is thus: + +"sip:unknown@unknown.invalid" + +For more information on the Unknown User Identity and when it is used, see 3GPP TS 29.163 [63], clauses 7.4.6 and 7.5.4. + +## 13.12 Default WWSF URI + +### 13.12.1 General + +Default WWSF URI is an HTTP URI that represents the WebRTC Web Server Function (WWSF) defined in 3GPP TS 23.228 [24]. + +### 13.12.2 Format of the Default WWSF URI + +The Default WWSF URI is an HTTP URI that should have the following format: + +"http://wwsf." + +in which "" identifies the domain hosting the WWSF. + +If a preconfigured or provisioned WWSF URI is available then the UE shall use it. When a preconfigured or provisioned WWSF URI does not exist then the UE shall create the Default WWSF URI as follows: + +- The first label shall be "wwsf". +- The next label(s) shall identify the home network as follows: + 1. When the UE has an ISIM, the domain name from the IMPI shall be used (see 3GPP TS 31.103 [93]) as follows: + - a. if the last two labels of the domain name from the IMPI are "3gppnetwork.org": + - i. the next labels shall be all labels of the domain name from the IMPI apart from the last two labels; and + - ii. the last three labels shall be "pub.3gppnetwork.org"; + - b. if the last two labels of the domain name from the IMPI are other than the "3gppnetwork.org": + +- i. the next labels shall be all labels of the domain name from the IMPI; +2. When the UE has a USIM and does not have an ISIM, the home network shall be "ims.mnc.mcc.pub.3gppnetwork.org" where and shall be derived from the components of the IMSI defined in clause 2.2. If there are only two significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the FQDN of WWSF URI. + +As an example for the case when the UE has the ISIM, where the IMPI is "user@operator.com", the Default WWSF URI used by the UE would be: + +EXAMPLE 1: "http://wwsf.operator.com". + +As an example for the case when the UE has the ISIM, where the IMPI is + +"234150999999999@ims.mnc015.mcc234.3gppnetwork.org", the Default WWSF URI used by the UE would be: + +EXAMPLE 2: "http://wwsf.ims.mnc015.mcc234.pub.3gppnetwork.org". + +As an example for the case when the UE has the USIM and does not have the ISIM, where the MCC is 345 and the MNC is 12, the Default WWSF URI created and used by the UE would be: + +EXAMPLE 3: "http://wwsf.ims.mnc012.mcc345.pub.3gppnetwork.org". + +## 13.13 IMEI based identity + +The IMEI based identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). The IMEI based identity is included in P-Preferred-Identity header field of SIP INVITE request by the UE and used in cases of unauthenticated emergency sessions as specified in clause 5.1.6.8.2 of 3GPP TS 24.229 [81]. A SIP URI for an IMEI based identity shall take the form "sip:user@domain" where by the user part shall contain the IMEI. The IMEI shall be encoded according to ABNF of imeival as defined in IETF RFC 7254 [79]. The domain part shall contain the home network domain named derived as specified in clause 13.2. + +An example for the case when the UE has a home network domain name of operator.com is: + +EXAMPLE 1: "sip:90420156-025763-0@operator.com" + +An example for 3GPP systems, when the UE with no ISIM application has a home network domain name of ims.mnc015.mcc234.3gppnetwork.org derived from the same example IMSI from clause 13.2 is: + +EXAMPLE 2: "sip:90420156-025763-0@ims.mnc015.mcc234.3gppnetwork.org" + +# 14 Numbering, addressing and identification for 3GPP System to WLAN Interworking + +## 14.1 Introduction + +This clause describes the format of the parameters needed to access the 3GPP system supporting the WLAN interworking. For further information on the use of the parameters see 3GPP TS 24.234 [48]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN related requirements specified in the present Clause are no longer maintained. + +## 14.2 Home network realm + +The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in RFC 1035 [19]. + +When attempting to authenticate within WLAN access, the WLAN UE shall derive the home network domain name from the IMSI as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name; +3. add the label "wlan." to the beginning of the domain name. + +An example of a WLAN NAI realm is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999 + +Which gives the home network domain name: wlan.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for the WLAN UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the WLAN UE determines the length of the MNC (2 or 3 digits). + +## 14.3 Root NAI + +The Root NAI shall take the form of a NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. + +The username part format of the Root NAI shall comply with IETF RFC 4187 [50] when EAP AKA authentication is used and with IETF RFC 4186 [51], when EAP SIM authentication is used. + +When the username part includes the IMSI, the Root NAI shall be built according to the following steps: + +1. Generate an identity conforming to NAI format from IMSI as defined in EAP SIM [51] and EAP AKA [50] as appropriate; +2. Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 14.2. + +The result will be a root NAI of the form: + +"0@wlan.mnc.mcc.3gppnetwork.org", for EAP AKA authentication and + "1@wlan.mnc.mcc.3gppnetwork.org", for EAP SIM authentication + +For example, for EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the root NAI then takes the form 023415099999999@wlan.mnc015.mcc234.3gppnetwork.org. + +## 14.4 Decorated NAI + +The Decorated NAI shall take the form of a NAI and shall have the form 'homerealm!username@otherrealm' as specified in clause 2.7 of the IETF RFC 4282 [53]. + +The realm part of Decorated NAI consists of 'otherrealm', see the IETF draft 2486-bis RFC 4282 [53]. 'Homerealm' is the realm as specified in clause 14.2, using the HPLMN ID ('homeMCC' + 'homeMNC'). 'Otherrealm' is the realm built using the PLMN ID (visitedMCC + visited MNC) of the PLMN selected as a result of WLAN PLMN selection (see 3GPP TS 24.234 [48]). + +The username part format of the Root NAI shall comply with IETF RFC 4187 [50] when EAP AKA authentication is used and with IETF RFC 4186 [51], when EAP SIM authentication is used. + +When the username part of Decorated NAI includes the IMSI, it shall be built following the same steps specified for Root NAI in clause 14.3. + +The result will be a decorated NAI of the form: + +"wlan.mnc.mcc.3gppnetwork.org + !0@wlan.mnc.mcc.3gppnetwork.org", for EAP AKA authentication and " + wlan.mnc.mcc.3gppnetwork.org + !1@wlan.mnc.mcc.3gppnetwork.org ", for EAP SIM authentication + +For example, for EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15) and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71 then the Decorated NAI takes the form + wlan.mnc015.mcc234.3gppnetwork.org!023415099999999@wlan.mnc071.mcc610.3gppnetwork.org. + +NOTE: the 'otherrealm' specified in the present document is resolved by the WLAN AN. If the WLAN AN does not have access to the GRX, then the WLAN AN should resolve the realm by other means e.g. static look-up table, private local DNS server acting as an authoritative name server for that sub-domain. + +## 14.4A Fast Re-authentication NAI + +The Fast Re-authentication NAI in both EAP-SIM and EAP-AKA shall take the form of a NAI as specified in clause 2.1 of IETF RFC 4282 [53]. If the 3GPP AAA server does not return a complete NAI, the Fast Re-authentication NAI shall consist of the username part of the fast re-authentication identity as returned from the 3GPP AAA server and the same realm as used in the permanent user identity. If the 3GPP AAA server returns a complete NAI as the re-authentication identity, then this NAI shall be used. The username part of the fast re-authentication identity shall be decorated as described in 14.4 if the Selected PLMN is different from the HPLMN. + +NOTE: The permanent user identity is either the root or decorated NAI as defined in clauses 14.3 and 14.4. + +EXAMPLE 1: If the fast re-authentication identity returned by the 3GPP AAA Server is 458405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: 458405627015@wlan.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 2: If the fast re-authentication identity returned by the 3GPP AAA Server is "458405627015@aaa1.wlan.mnc015.mcc234.3gppnetwork.org" and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: 458405627015@aaa1.wlan.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 3: If the fast re-authentication identity returned by the 3GPP AAA Server is 458405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the Fast Re-authentication NAI takes the form: wlan.mnc015.mcc234.3gppnetwork.org!458405627015@wlan.mnc071.mcc610.3gppnetwork.org + +## 14.5 Temporary identities + +The Temporary identities (Pseudonyms and re-authentication identities) shall take the form of a NAI username as specified in clause 2.1 of the IETF RFC 4282 [53]. + +Temporary identity shall be generated as specified in clause 6.4.1 of 3GPP TS 33.234 [55]. This part of the temporary identity shall follow the UTF-8 transformation format specified in IETF RFC 2279 [54] except for the following reserved hexadecimal octet value: + +FF. + +When the temporary identity username is coded with FF, this reserved value is used to indicate the special case when no valid temporary identity exists in the WLAN UE (see 3GPP TS 24.234 [48]). The network shall not allocate a temporary identity with the whole username coded with the reserved hexadecimal value FF. + +For EAP-AKA authentication, the username portion of the pseudonym identity shall be prepended with the single digit "2" and the username portion of the fast re-authentication identity shall be prepended with the single digit "4" as specified in clause 4.1.1.7 of IETF RFC 4187 [50]. + +For EAP-SIM authentication, the username portion of the pseudonym identity shall be prepended with the single digit "3" and the username portion of the fast re-authentication identity shall be prepended with the single digit "5" as specified in clause 4.2.1.7 of IETF RFC 4186 [51]. + +## 14.6 Alternative NAI + +The Alternative NAI shall take the form of a NAI, i.e. 'any\_username@REALM' as specified of IETF RFC 4282 [53]. The Alternative NAI shall not be routable from any AAA server. + +The Alternative NAI shall contain a username part which is not derived from the IMSI. The username part shall not be a null string. + +The REALM part of the NAI shall be "unreachable.3gppnetwork.org". + +The result shall be an NAI in the form of: + +"@unreachable.3gppnetwork.org" + +## 14.7 W-APN + +The W-APN is composed of two parts as follows: + +- The W-APN Network Identifier; this defines to which external network the PDG is connected. +- The W-APN Operator Identifier; this defines in which PLMN the PDG serving the W-APN is located. + +The W-APN Operator Identifier is placed after the W-APN Network Identifier. The W-APN consisting of both the Network Identifier and Operator Identifier corresponds to a FQDN of a PDG; the W-APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. + +The encoding of the W-APN shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. The W-APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The W-APN is not terminated by a length byte of zero. + +For the purpose of presentation, a W-APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +The W-APN for the support of IMS Emergency calls shall take the form of a common, reserved Network Identifier described in clause 14.7.1 together with the usual W-APN Operator Identifier as described in clause 14.7.2. + +### 14.7.1 Format of W-APN Network Identifier + +The W-APN Network Identifier follows the format defined for APNs in clause 9.1.1. In addition to what has been defined in clause 9.1.1 the W-APN Network Identifier shall not contain "w-apn." and not end in ".3gppnetwork.org". + +A W-APN Network Identifier may be used to access a service associated with a PDG. This may be achieved by defining: + +- a W-APN which corresponds to a FQDN of a PDG, and which is locally interpreted by the PDG as a request for a specific service, or +- a W-APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or a W-APN Network Identifier consisting of a Reserved Service Label alone, which indicates a PDG by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have WLAN roaming agreements. + +The W-APN Network Identifier for the support of IMS Emergency calls shall take the form of a common, reserved Network Identifier of the form "sos". + +As an example, the W-APN for MCC 345 and MNC 12 is coded in the DNS as: + +"sos.w-apn.mnc012.mcc345.pub.3gppnetwork.org". + +where "sos" is the W-APN Network Identifier and " mnc012.mcc345.pub.3gppnetwork.org " is the W-APN Operator Identifier. + +## 14.7.2 Format of W-APN Operator Identifier + +The W-APN Operator Identifier is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label distinguishes the domain name as a W-APN. + +For each operator, there is a default W-APN Operator Identifier (i.e. domain name). This default W-APN Operator Identifier is derived from the IMSI as follows: + +"w-apn.mnc.mcc.pub.3gppnetwork.org" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + + and are derived from the components of the IMSI defined in clause 2.2. + +Alternatively, the default W-APN Operator Identifier is derived using the MNC and MCC of the VPLMN. See 3GPP TS 24.234 [48] for more information. + +The default W-APN Operator Identifier is used in both non-roaming and roaming situations when attempting to translate a W-APN consisting only of a Network Identifier into the IP address of the PDG in the HPLMN. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "w-apn.mnc.mcc.pub.3gppnetwork.org" format of the W-APN OI shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the W-APN OI. + +As an example, the W-APN OI for MCC 345 and MNC 12 is coded in the DNS as: + +"w-apn.mnc012.mcc345.pub.3gppnetwork.org". + +## 14.7.3 Alternative Format of W-APN Operator Identifier + +For situations when the PDG serving the W-APN is located in such network that is not part of the GRX (i.e. the Interoperator IP backbone), the default Operator Identifier described in clause 14.7.2 is not available for use. This restriction originates from the ".3gppnetwork.org" domain, which is only available in GRX DNS for actual use. Thus an alternative format of W-APN Operator Identifier is required for this case. + +The Alternative W-APN Operator Identifiers shall be constructed as follows: + +"w-apn." + +where: + + corresponds to REALM names owned by the operator hosting the PDG serving the desired W-APN. + +REALM names are required to be unique, and are piggybacked on the administration of the Public Internet DNS namespace. REALM names may also belong to the operator of the VPLMN. + +As an example, the W-APN OI for the Operator REALM "notareal.com" is coded in the Public Internet DNS as: + +"w-apn.notareal.com". + +## 14.8 Emergency Realm and Emergency NAI for Emergency Cases + +The emergency realm shall be of the form of a home network realm as described in clause 14.2 prefixed with the label "sos." at the beginning of the domain name. + +An example of a WLAN emergency NAI realm is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999 + +Which gives the home network domain name: sos.wlan.mnc015.mcc234.3gppnetwork.org. + +The NAI for emergency cases shall be of the form as specified in clauses 14.3 and 14.4, with the addition of the emergency realm as described above for PLMNs where the emergency realm is supported. + +When UE is using I-WLAN as the access network for IMS emergency calls and IMSI is not available, the Emergency NAI shall be an NAI compliant with IETF RFC 4282 [53] consisting of username and realm, either constructed with IMEI or MAC address, as specified in 3GPP TS 33.234 [55]. The exact format shall be: + +imei@sos.wlan.mnc.mcc.3gppnetwork.org + +or if IMEI is not available, + +mac@sos.wlan.mnc.mcc.3gppnetwork.org + +The realm part of the above NAI consists of the realm built using the PLMN ID (visitedMCC + visitedMNC) of the PLMN selected as a result of the network selection procedure, as specified in clause 5.2.5.4 of the 3GPP TS 24.234 [48]. + +The MNC and MCC shall be with 3 digits coded. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the realm of the NAI. + +For example, if the IMEI is 219551288888888, and the selected PLMN is with MCC 345 and MNC 12, the Emergency NAI then takes the form of imei219551288888888@sos.wlan.mnc012.mcc345.3gppnetwork.org. + +For example, if the MAC address is 44-45-53-54-00-AB, and the selected PLMN is with MCC 345 and MNC 12, the Emergency NAI then takes the form of mac4445535400AB@sos.wlan.mnc012.mcc345.3gppnetwork.org, where the MAC address is represented in hexadecimal format without separators. + +--- + +## 15 Identification of Multimedia Broadcast/Multicast Service + +### 15.1 Introduction + +This clause describes the format of the parameters needed to access the Multimedia Broadcast/Multicast service. For further information on the use of the parameters see 3GPP TS 23.246 [52]. + +## 15.2 Structure of TMGI + +Temporary Mobile Group Identity (TMGI) is used within MBMS to uniquely identify Multicast and Broadcast bearer services. + +TMGI is composed as shown in figure 15.2.1. + +![Diagram showing the structure of TMGI. It is composed of three parts: MBMS Service ID (6 digits), MCC (3 digits), and MNC (2 or 3 digits).](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +The diagram illustrates the structure of the Temporary Mobile Group Identity (TMGI). It is shown as a horizontal sequence of three components: + + +- MBMS Service ID**: Represented by a box labeled "MBMS Service ID" with a double-headed arrow above it indicating a length of "6 digits". +- MCC**: Represented by a box labeled "MCC" with a double-headed arrow above it indicating a length of "3 digits". +- MNC**: Represented by a box labeled "MNC" with a double-headed arrow above it indicating a length of "2 or 3 digits". + + Below these three components, a single long double-headed arrow spans the entire length, labeled "TMGI", indicating the concatenation of these three parts into the full identity. + +Diagram showing the structure of TMGI. It is composed of three parts: MBMS Service ID (6 digits), MCC (3 digits), and MNC (2 or 3 digits). + +**Figure 15.2.1: Structure of TMGI** + +The TMGI is composed of three parts: + +- 1) MBMS Service ID consisting of three octets. MBMS Service ID consists of a 6-digit fixed-length hexadecimal number between 000000 and FFFFFFFF. MBMS Service ID uniquely identifies an MBMS bearer service within a PLMN. The structure of MBMS Service ID for services for Receive only mode is defined in 3GPP TS 24.116 [118]. +- 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the BM-SC, except for the MCC value of 901, which does not identify any country and is assigned globally by ITU; +- 3) Mobile Network Code (MNC) consisting of two or three digits (depending on the assignment to the PLMN by its national numbering plan administrator). The MNC identifies the PLMN which the BM-SC belongs to, except for the MNC value of 56 when the MCC value is 901, which does not identify any PLMN. For more information on the use of the TMGI, see 3GPP TS 23.246 [52]. + +Any TMGI with MCC=901 and MNC=56 is used only for services for Receive Only Mode (see TS 23.246 [52] and 3GPP TS 24.116 [118]). + +## 15.3 Structure of MBMS SAI + +The MBMS Service Area (MBMS SA) is defined in 3GPP TS 23.246 [52]. It comprises of one or more MBMS Service Area Identities (MBMS SAIs), in any case each MBMS SA shall not include more than 256 MBMS SAIs. An MBMS SAI shall identify a group of cells within a PLMN, that is independent of the associated Location/Routing/Service Area and the physical location of the cell(s). A cell shall be able to belong to one or more MBMS SAs, and therefore is addressable by one or more MBMS SAIs. + +The MBMS SAI shall be a decimal number between 0 and 65,535 (inclusive). The value 0 has a special meaning; it shall denote the whole PLMN as the MBMS Service Area and it shall indicate to a receiving RNC/BSS/MCE that all cells reachable by that RNC/BSS/MCE shall be part of the MBMS Service Area. + +With the exception of the specific MBMS Service Area Identity with value 0, the MBMS Service Area Identity shall be unique within a PLMN and shall be defined in such a way that all the corresponding cells are MBMS capable. + +## 15.4 Home Network Realm + +The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network realm consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF + +RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +During the MBMS service activation in roaming scenario, the BM-SC in the visited network shall derive the home network domain name from the IMSI as described in the following steps: + +1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. Use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" realm name; +3. Add the label "mbms." to the beginning of the realm name. + +An example of a home realm used in the MBMS roaming case is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999 + +Which gives the home network realm: mbms.mnc015.mcc234.3gppnetwork.org. + +## 15.5 Addressing and identification for Bootstrapping MBMS Service Announcement + +The UE needs a Service Announcement Fully Qualified Domain Name (FQDN) to bootstrap MBMS Service Announcement as specified in 3GPP TS 26.346 [105]. + +The Service Announcement FQDN is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label shall be "mbmsbs". + +The Service Announcement FQDN is derived from the IMSI or Visited PLMN Identity as follows: + +"mbmsbs.mnc.mcc.pub.3gppnetwork.org" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + +- When using the Service Announcement FQDN in a visited network, the and shall be derived from the visited PLMN Identity as defined in clause 12.1. +- When using the Service Announcement FQDN in the home network, the and shall be derived from the components of the IMSI as defined in clause 2.2. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "mbmsbs.mnc.mcc.pub.3gppnetwork.org" format of the Service Announcement FQDN shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the Service Announcement FQDN. + +As an example, the Service Announcement FQDN for MCC 345 and MNC 12 is coded in the DNS as: + +"mbmsbs.mnc012.mcc345.pub.3gppnetwork.org". + +## 16 Numbering, addressing and identification within the GAA subsystem + +### 16.1 Introduction + +This clause describes the format of the parameters needed to access the GAA system. For further information on the use of the parameters see 3GPP TS 33.221 [58]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +### 16.2 BSF address + +The Bootstrapping Server Function (BSF) address is in the form of a Fully Qualified Domain Name as defined in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The BSF address consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +For 3GPP systems, the UE shall discover the BSF address from the identity information related to the UICC application that is used during the bootstrapping procedure i.e. IMSI for USIM, or IMPI for ISIM, in the following way: + +- In the case where the USIM is used in bootstrapping, the BSF address shall be derived as follows: + 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; + 2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.pub.3gppnetwork.org" domain name; + 3. add the label "bsf." to the beginning of the domain. + +Example 1: If IMSI in use is "234150999999999", where MCC=234, MNC=15, and MSIN=0999999999, the BSF address would be "bsf.mnc015.mcc234.pub.3gppnetwork.org". + +- In the case where ISIM is used in bootstrapping, the BSF address shall be derived as follows: + 1. extract the domain name from the IMPI; + 2. if the last two labels of the domain name extracted from the IMPI are "3gppnetwork.org": + - a. the first label is "bsf"; + - b. the next labels are all labels of the domain name extracted from the IMPI apart from the last two labels; and + - c. the last three labels are "pub.3gppnetwork.org"; + +Example 2: If the IMPI in use is "234150999999999@ims.mnc015.mcc234.3gppnetwork.org", the BSF address would be "bsf.ims.mnc015.mcc234.pub.3gppnetwork.org". + +3. if the last two labels of the domain name extracted from the IMPI are other than the "3gppnetwork.org": + - a. add the label "bsf." to the beginning of the domain. + +Example 3: If the IMPI in use is "user@operator.com", the BSF address would be "bsf.operator.com". + +# 17 Numbering, addressing and identification within the Generic Access Network + +## 17.1 Introduction + +This clause describes the format of the parameters needed to access the Generic Access Network (GAN). For further information on the use of the parameters and GAN in general, see 3GPP TS 43.318 [61] and 3GPP TS 44.318 [62]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +## 17.2 Network Access Identifiers + +### 17.2.1 Home network realm + +The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network realm consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +The UE shall derive the home network realm from the IMSI as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" network realm; +3. add the label "gan." to the beginning of the network realm. + +An example of a home network realm is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the home network realm: gan.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +### 17.2.2 Full Authentication NAI + +The Full Authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of IETF RFC 4282 [53]. The format of the Full Authentication NAI shall comply with IETF RFC 4187 [50] when EAP-AKA authentication is used and with IETF RFC 4186 [51], when EAP-SIM authentication is used. The realm used shall be a home network realm as defined in clause 17.2.1. + +The result will therefore be an identity of the form: + +"0@gan.mnc.mcc.3gppnetwork.org", for EAP-AKA authentication and +"1@gan.mnc.mcc.3gppnetwork.org", for EAP-SIM authentication + +- EXAMPLE 1: For EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Full Authentication NAI takes the form 0234150999999999@gan.mnc015.mcc234.3gppnetwork.org. +- EXAMPLE 2: For EAP SIM authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Full Authentication NAI takes the form 1234150999999999@gan.mnc015.mcc234.3gppnetwork.org. + +## 17.2.3 Fast Re-authentication NAI + +The Fast Re-authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of IETF RFC 4282 [53]. The UE shall use the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure. If such an NAI contains a realm part then the UE should not modify it, otherwise it shall use a home network realm as defined in clause 17.2.1. + +The result will therefore be an identity of the form: + +"@" for both EAP-SIM and EAP-AKA authentication when a realm is present in the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure and + +"@gan.mnc.mcc.3gppnetwork.org", for both EAP-SIM and EAP-AKA authentication when a realm is *not* present in the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure. + +- EXAMPLE 1: If the re-authentication identity is "12345" and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI takes the form 12345@gan.mnc015.mcc234.3gppnetwork.org +- EXAMPLE 2: If the re-authentication identity is "12345@aaa1.gan.mnc015.mcc234.3gppnetwork.org", the Fast Re-authentication NAI takes the form 12345@aaa1.gan.mnc015.mcc234.3gppnetwork.org + +## 17.3 Node Identifiers + +### 17.3.1 Home network domain name + +The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +The UE shall derive the home network domain name from the IMSI as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27], 3GPP TS 51.011 [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.pub.3gppnetwork.org" domain name; +3. add the label "gan." to the beginning of the domain name. + +An example of a home network domain name is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the home network domain name: gan.mnc015.mcc234.pub.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +### 17.3.2 Provisioning GANC-SEGW identifier + +The Provisioning GANC-SEGW identifier shall take the form of a fully qualified domain name (FQDN) as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The Provisioning GANC-SEGW identifier consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +If the (U)SIM is not provisioned with the FQDN or IP address of the Provisioning GANC-SEGW, the UE derives an FQDN from the IMSI to identify the Provisioning GANC-SEGW. The UE shall derive such an FQDN as follows: + +1. create a domain name as specified in 17.3.1; +2. add the label "psegw." to the beginning of the domain name. + +An example of an FQDN for a Provisioning GANC-SEGW is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the FQDN: psegw.gan.mnc015.mcc234.pub.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +### 17.3.3 Provisioning GANC identifier + +The Provisioning GANC identifier shall take the form of a fully qualified domain name (FQDN) as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The Provisioning GANC identifier consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +If the (U)SIM is not provisioned with the FQDN or IP address of the Provisioning GANC, the UE derives an FQDN from the IMSI to identify the Provisioning GANC. The UE shall derive such an FQDN as follows: + +1. create a domain name as specified in 17.3.1; +2. add the label "pganc." to the beginning of the domain name. + +An example of an FQDN for a Provisioning GANC is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999, + +Which gives the FQDN: pganc.gan.mnc015.mcc234.pub.3gppnetwork.org. + +NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +--- + +## 18 Addressing and Identification for IMS Service Continuity and Single-Radio Voice Call Continuity + +### 18.1 Introduction + +This clause describes the format of the parameters needed for the support of IMS Service Continuity. For further information on the use of the parameters see 3GPP TS 23.237 [71] and also 3GPP TS 23.292 [70]. + +### 18.2 CS Domain Routeing Number (CSRN) + +A CS Domain Routeing Number (CSRN) is a number that is used to route a call from the IM CN subsystem to the user in the CS domain. The structure is as defined in clause 3.4. + +### 18.3 IP Multimedia Routeing Number (IMRN) + +An IP Multimedia Routeing Number (IMRN) is a routable number that points to the IM CN subsystem. In a roaming scenario, the IMRN has the same structure as an international ISDN number (see clause 3.4). The Tel URI format of the IMRN (see IETF RFC 3966 [45]) is treated as a PSI (see clause 13.5) within the IM CN subsystem. + +### 18.4 Session Transfer Number (STN) + +A Session Transfer Number (STN) is a public telecommunication number, as defined by ITU-T Recommendation E.164 [10] and is used by the UE to request Session Transfer of the media path from PS to CS access. + +### 18.5 Session Transfer Identifier (STI) + +A Session Transfer Identifier (STI) is a SIP URI or SIP dialogue ID (see IETF RFC 3261 [26] for more information) and is used by the UE to request Session Transfer of a media path. + +### 18.6 Session Transfer Number for Single Radio Voice Call Continuity (STN-SR) + +The Session Transfer Number for Single Radio Voice Call Continuity (STN-SR) is a public telecommunication number, as defined by ITU-T Recommendation E.164 [10] and is used by the MSC Server to request session transfer of the media path from the PS domain to CS domain. + +### 18.7 Correlation MSISDN + +A Correlation MSISDN (C-MSISDN) is an MSISDN (see clause 3.3) that is used for correlation of sessions at access transfer and to route a call from the IM CN subsystem to the same user in the CS domain. The C-MSISDN is equal to the MSISDN or the basic MSISDN if multinumbering option is used (see 3GPP TS 23.008 [2], clause 2.1.3) of the CS access. Any MSISDN of a user that can be used for TS11 (telephony) in the CS domain which is not shared by more than one IMS Private Identity in an IMS CN subsystem, can serve as the user's C-MSISDN. + +The C-MSISDN is bound to the IMS Private User Identity and is uniquely assigned per IMSI and IMS Private User Identity. + +If A-MSISDN is available it shall be used as the C-MSISDN. For the definition of A-MSISDN refer to clause 18.9. + +## 18.8 Transfer Identifier for CS to PS Single Radio Voice Call Continuity (STI-rSR) + +A Session Transfer Identifier for CS to PS Single Radio Voice Call Continuity (STI-rSR) is a SIP URI (see IETF RFC 3261 [26] for more information) and is used by the UE to request access transfer of a media path. + +## 18.9 Additional MSISDN + +An Additional MSISDN (A-MSISDN) is an MSISDN (see clause 3.3) that is assigned to a user with PS subscription in addition to the already assigned MSISDN(s). + +The structure of an A-MSISDN should follow the structure of an MSISDN number as defined in clause 3.3. + +The A-MSISDN shall be able to be used for TS11 (telephony) in the CS domain and shall be uniquely assigned per IMSI. + +--- + +# 19 Numbering, addressing and identification for the Evolved Packet Core (EPC) + +## 19.1 Introduction + +This clause describes the format of the parameters needed to access the Enhanced Packet Core (EPC). For further information on the use of the parameters see 3GPP TS 23.401 [72] and 3GPP TS 23.402 [68]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document + +## 19.2 Home Network Realm/Domain + +The home Network Realm/Domain shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home Network Realm/Domain consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +The Home Network Realm/Domain shall be in the form of "epc.mnc.mcc.3gppnetwork.org", where "" and "" fields correspond to the MNC and MCC of the operator's PLMN. Both the "" and "" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning. + +For example, the Home Network Realm/Domain of an IMSI shall be derived as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name; +3. add the label "epc" to the beginning of the domain name. + +An example of a Home Network Realm/Domain is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999; + +Which gives the Home Network Realm/Domain name: epc.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for a UE to identify whether a 2 or 3 digit MNC is used (e.g. USIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). + +## 19.3 3GPP access to non-3GPP access interworking + +### 19.3.1 Introduction + +This clause describes the format of the UE identification needed to access the 3GPP EPC from both 3GPP and non-3GPP accesses. + +The NAI is generated respectively by the S-GW at the S5/S8 reference point and by the UE for the S2a, S2b and S2c reference points. + +The NAI shall be generated as follows: + +- based on the IMSI when the UE is performing a non-emergency Attach; +- based on the IMEI when the UE is performing an emergency attach and IMSI is not available (see clause 19.3.6); or +- based on the IMSI or the IMEI (depending on the interface and information element) when the UE is performing an emergency attach and IMSI is available in the UE, as follows: + - a UE that has an IMSI shall construct an Emergency NAI based on IMSI (see clause 4.6.1 of 3GPP TS 23.402 [68] and clause 19.3.9 of this specification); + - if the IMSI is not authenticated by the network, the network requests the IMEI from the UE and the network shall then construct a NAI based on the IMEI for identifying the user in the EPC (see 3GPP TS 29.273 [78]). + +For further information on the use of the parameters see the clauses below and 3GPP TS 33.402 [69] and 3GPP TS 29.273 [78]. + +### 19.3.2 Root NAI + +The Root NAI shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. + +When the username part is the IMSI, the realm part of Root NAI shall be built according to the following steps: + +1. Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 19.2. +2. Prefix domain name with the label "nai". + +The resulting realm part of the Root NAI will be in the form: + +"@nai.epc.mnc.mcc.3gppnetwork.org" + +When including the IMSI, the Root NAI is prepended with a specific leading digit when used for EAP authentication (see 3GPP TS 29.273 [78]) in order to differentiate between EAP authentication method. The leading digit is: + +- "0" when used in EAP-AKA, as specified in IETF RFC 4187 [50] +- "6" when used in EAP-AKA', as specified in IETF RFC 5448 [82]. + +The resulting Root NAI will be in the form: + +"0@nai.epc.mnc.mcc.3gppnetwork.org" when used for EAP AKA authentication + +"6@nai.epc.mnc.mcc.3gppnetwork.org" when used for EAP AKA' authentication + +For example, if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Root NAI takes the form 023415099999999@nai.epc.mnc015.mcc234.3gppnetwork.org for EAP AKA authentication and the Root NAI takes the form 623415099999999@nai.epc.mnc015.mcc234.3gppnetwork.org for EAP AKA' authentication. + +The NAI sent in the Mobile Node Identifier field in PMIPv6 shall not include the digit prepended in front of the IMSI based username that is described above. + +### 19.3.3 Decorated NAI + +The Decorated NAI shall take the form of a NAI and shall have the form 'homerealm!username@otherrealm' or 'Visitedrealm!homerealm!username@otherrealm' as specified in clause 2.7 of the IETF RFC 4282 [53]. + +The realm part of Decorated NAI consists of 'otherrealm', see the IETF RFC 4282 [53]. 'Homerealm' is the realm as specified in clause 19.2, using the HPLMN ID ('homeMCC' + 'homeMNC'). 'Visitedrealm' is the realm built using the VPLMN ID ('VisitedMCC' + 'VisitedMNC'), 'Otherrealm' is: + +- the realm built using the PLMN ID (visitedMCC + visited MNC) if the service provider selected as a result of the service provider selection (see 3GPP TS 24.302 [77]) has a PLMN ID; or +- a domain name of a service provider if the selected service provider does not have a PLMN ID (3GPP TS 24.302 [77]). + +When the username part of Decorated NAI includes the IMSI and the service provider has a PLMN ID, the Decorated NAI shall be built following the same steps as specified for Root NAI in clause 19.3.2. + +The result will be a decorated NAI of the form: + +- nai.epc.mnc.mcc.3gppnetwork.org +!0@nai.epc.mnc.mcc.3gppnetwork.org for EAP AKA authentication. + +or + +- nai.epc.mnc.mcc.3gppnetwork.org +!6@nai.epc.mnc.mcc.3gppnetwork.org for EAP AKA' authentication. + +For example, if the service provider has a PLMN ID and the IMSI is 234150999999999 (MCC = 234, MNC = 15) and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, then the Decorated NAI takes the form either as: + +- nai.epc.mnc015.mcc234.3gppnetwork.org!023415099999999@nai.epc.mnc071.mcc610.3gppnetwork.org for EAP AKA authentication + +or + +- nai.epc.mnc015.mcc234.3gppnetwork.org!623415099999999@nai.epc.mnc071.mcc610.3gppnetwork.org for EAP AKA' authentication. + +For example, if the domain name of a service provider is 'realm.org' and IMSI-based permanent username is used, then the Decorated NAI takes the form either as: + +- nai.epc.mnc.mcc.3gppnetwork.org !0@realm.org for EAP AKA authentication + +or + +- nai.epc.mnc.mcc.3gppnetwork.org !6@realm.org for EAP AKA' authentication. + +If the UE has selected a WLAN that directly interworks with a service provider in the Equivalent Visited Service Providers (EVSP) list provided by the RPLMN, see 3GPP TS 23.402 [77], clause 4.8.2b, then the decorated NAI is constructed to include the realm of this service provider and the realm of RPLMN. If the domain name of a service + +provider is 'realm.org' and IMSI-based permanent username is used, then the Decorated NAI with double decoration takes the form either as: + +- nai.epc.mnc.mcc.3gppnetwork.org +!nai.epc.mnc.mcc.3gppnetwork.org!0@realm.org for EAP AKA authentication + +or + +- nai.epc.mnc.mcc.3gppnetwork.org +!nai.epc.mnc.mcc.3gppnetwork.org!6@realm.org for EAP AKA' authentication. + +When the username part of Decorated NAI includes a Fast Re-authentication NAI, the Decorated NAI shall be built following the same steps as specified for the Fast Re-authentication NAI in clause 19.3.4. + +When the username part of Decorated NAI includes a Pseudonym, the Decorated NAI shall be built following the same steps as specified for the Pseudonym identity in clause 19.3.5. + +### 19.3.4 Fast Re-authentication NAI + +The Fast Re-authentication NAI shall take the form of a NAI as specified in clause 2.1 of IETF RFC 4282 [53]. If the 3GPP AAA server does not return a complete NAI, the Fast Re-authentication NAI shall consist of the username part of the fast re-authentication identity as returned from the 3GPP AAA server and the same realm as used in the permanent user identity. If the 3GPP AAA server returns a complete NAI as the re-authentication identity, then this NAI shall be used. The username part of the fast re-authentication identity shall be decorated as described in 19.3.3 if the Selected PLMN is different from the HPLMN. + +For EAP-AKA authentication, the username portion of the fast re-authentication identity shall be prepended with the single digit "4" as specified in clause 4.1.1.7 of IETF RFC 4187 [50]. + +For EAP AKA', see IETF RFC 5448 [82], the Fast Re-authentication NAI shall comply with IETF RFC 4187 [50] except that the username part of the NAI shall be prepended with single digit "8". + +NOTE: The permanent user identity is either the Root NAI or Decorated NAI as defined in clauses 19.3.2 and 19.3.3, respectively. + +EXAMPLE 1: If the fast re-authentication identity returned by the 3GPP AAA Server is 358405627015, the IMSI is 234150999999999 (MCC = 234, MNC = 15) and EAP-AKA is used, the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: +4358405627015@nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 2: If the fast re-authentication identity returned by the 3GPP AAA Server is "358405627015@aaa1.nai.epc.mnc015.mcc234.3gppnetwork.org", the IMSI is 234150999999999 (MCC = 234, MNC = 15) and EAP-AKA' is used, the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: +8358405627015@aaa1.nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 3: If the fast re-authentication identity returned by the 3GPP AAA Server is 358405627015, the IMSI is 234150999999999 (MCC = 234, MNC = 15), the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71 and EAP-AKA is used, the Fast Re-authentication NAI takes the form: +nai.epc.mnc015.mcc234.3gppnetwork.org +!4358405627015@nai.epc.mnc071.mcc610.3gppnetwork.org. + +### 19.3.5 Pseudonym Identities + +The pseudonym shall take the form of an NAI, as specified in clause 2.1 of IETF RFC 4282 [53]. + +The pseudonym shall be generated as specified in clause 6.4.1 of 3GPP TS 33.234 [55]. This part of the pseudonym shall follow the UTF-8 transformation format specified in IETF RFC 2279 [54] except for the following reserved hexadecimal octet value: + +FF + +When the pseudonym username is coded with FF, this reserved value is used to indicate the special case when no valid temporary identity exists in the UE (see 3GPP TS 24.234 [48] for more information). The network shall not allocate a temporary identity with the whole username coded with the reserved hexadecimal value FF. + +The username portion of the pseudonym identity shall be prepended with the single digit "2" as specified in clause 4.1.1.7 of IETF RFC 4187 [50] for EAP-AKA. For EAP AKA', see IETF RFC 5448 [82], the pseudonym NAI shall comply with IETF RFC 4187 [50] except that the username part of the NAI shall be prepended with single digit "7". + +NOTE: The permanent user identity is either the Root NAI or Decorated NAI as defined in clauses 19.3.2 and 19.3.3, respectively. + +EXAMPLE 1: For EAP AKA, if the pseudonym returned by the 3GPP AAA Server is 258405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the pseudonym NAI for the case when NAI decoration is not used takes the form: 258405627015@nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 2: For EAP AKA', if the pseudonym returned by the 3GPP AAA Server is 758405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the pseudonym NAI for the case when NAI decoration is not used takes the form: 758405627015@nai.epc.mnc015.mcc234.3gppnetwork.org + +EXAMPLE 3: For EAP AKA, if the pseudonym returned by the 3GPP AAA Server is 258405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the pseudonym NAI takes the form: +nai.epc.mnc015.mcc234.3gppnetwork.org! +258405627015@nai.epc.mnc071.mcc610.3gppnetwork.org + +EXAMPLE 4: For EAP AKA', if the pseudonym returned by the 3GPP AAA Server is 758405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the pseudonym NAI takes the form: +nai.epc.mnc015.mcc234.3gppnetwork.org! +758405627015@nai.epc.mnc071.mcc610.3gppnetwork.org + +### 19.3.6 Emergency NAI for Limited Service State + +This clause describes the format of the UE identification needed to access the 3GPP EPC from both 3GPP and non-3GPP accesses, when UE is performing an emergency attach and IMSI is not available or not authenticated (see clause 19.3.1). For more information, see clauses 4.6.1 and 5.2 of 3GPP TS 23.402 [68]. + +The Emergency NAI for Limited Service State shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. The exact format shall be: + +imei@sos.invalid + +NOTE: The top level domain ".invalid" is a reserved top level domain, as specified in IETF RFC 2606 [64], and is used here due to the fact that this NAI never needs to be resolved for routing (as specified in 3GPP TS 23.402 [68]). + +or + +mac@sos.invalid + +For example, if the IMEI is 219551288888888, the Emergency NAI for Limited Service State then takes the form of imei219551288888888@sos.invalid. + +For example, if the MAC address is 44-45-53-54-00-AB, the Emergency NAI for Limited Service State then takes the form of mac4445535400AB@sos.invalid, where the MAC address is represented in hexadecimal format without separators. + +### 19.3.7 Alternative NAI + +The Alternative NAI shall take the form of a NAI, i.e. 'any\_username@REALM' as specified of IETF RFC 4282 [53]. The Alternative NAI shall not be routable from any AAA server. + +The Alternative NAI shall contain a username part which is not derived from the IMSI. The username part shall not be a null string. + +The REALM part of the NAI shall be "unreachable.3gppnetwork.org". + +The result shall be an NAI in the form of: + +"@unreachable.3gppnetwork.org". + +### 19.3.8 Keyname NAI + +The keyname NAI shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. + +The username part is the EMSK name as defined in IETF RFC 6696 [113]. + +For ERP exchange with an ER server located in the 3GPP AAA Server, the realm part of the keyname NAI shall be the realm part of the Root NAI of the UE as described in clause 19.3.2, i.e. the realm part of the keyName-NAI will be in the form: + +"@nai.epc.mnc.mcc.3gppnetwork.org" + +For ERP exchange with an ER server located in the TWAP or in the 3GPP AAA Proxy, the realm part of the keyname NAI shall be the realm discovered by the UE in the non-3GPP access network (received at the lower layer or through an ERP exchange as described in IETF RFC 6696 [113]). + +### 19.3.9 IMSI-based Emergency NAI + +This clause describes the format of the UE identification needed to access the 3GPP EPC from non-3GPP accesses, when UE is performing an emergency attach and IMSI is available. For more information, see clause 4.4.1 of 3GPP TS 24.302 [77]. + +The IMSI-based Emergency NAI shall take the form of an NAI and shall be encoded as the Root NAI as specified in clause 19.3.2, but with the realm name prepended by the "sos" label. The resulting realm part of the IMSI-based Emergency NAI will be in the form: + +"@sos.nai.epc.mnc.mcc.3gppnetwork.org" + +The resulting IMSI-based Emergency NAI will be in the form: + +"0@sos.nai.epc.mnc.mcc.3gppnetwork.org" when used for EAP AKA authentication + +"6@sos.nai.epc.mnc.mcc.3gppnetwork.org" when used for EAP AKA' authentication + +For example, if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the IMSI-based Emergency NAI takes the form 0234150999999999@sos.nai.epc.mnc015.mcc234.3gppnetwork.org for EAP AKA authentication and it takes the form 6234150999999999@sos.nai.epc.mnc015.mcc234.3gppnetwork.org for EAP AKA' authentication. + +## 19.4 Identifiers for Domain Name System procedures + +### 19.4.1 Introduction + +This clause describes Domain Name System (DNS) related identifiers used by the procedures specified in 3GPP TS 29.303 [73]. + +The DNS identifiers for APNs for legacy systems (as defined in clause 9), RAIs (as defined in clause C.1), GSNs (as defined in clause C.2) and RNCs (as defined in clause C.3) in the present document use the top level domain ".gprs" and + +have a similar purpose and function as those described below. These clauses are still valid and DNS records based on these and the below types of identifiers are expected to coexist in an operator's network for the purpose of backwards compatibility and interworking with legacy networks. + +The APN as defined in clause 9 is used also in EPC to identify the access network to be used for a specific PDN connection or PDP Context. In addition, the APN Network Identifier (APN-NI) part of the APN as defined in clause 9.1.1 of the present document may be used to access a service associated with a PDN-GW or GGSN. This is achieved by defining an APN which in addition to being usable to select a PDN-GW or GGSN is locally interpreted by the PDN-GW or GGSN as a request for a specific service. + +For DNS procedures defined in 3GPP TS 29.303 [73], an APN-FQDN derived from a given APN is used instead of the APN itself as defined in clause 19.4.2.2. For all other purposes, including communication between EPC nodes and to the UE, the APN format defined in clause 9 is used. In order to support backwards compatibility with existing GPRS/PS roaming using the Gn/Gp interfaces, the APN as specified in clause 9 of the present document may also be used for the DNS procedures as defined in 3GPP TS 23.060 [3]. + +## 19.4.2 Fully Qualified Domain Names (FQDNs) + +### 19.4.2.1 General + +The encoding of any identifier used as part of a Fully Qualified Domain Name (FQDN) shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. An FQDN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. Identifiers are not terminated by a length byte of zero. + +NOTE: A length byte of zero is added by the querying entity at the end of the FQDN before interrogating a DNS server. + +For the purpose of presentation, identifiers are usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +### 19.4.2.2 Access Point Name FQDN (APN-FQDN) + +#### 19.4.2.2.1 Structure + +The Access Point Name FQDN (APN-FQDN) is derived from an APN as follows. The APN consists of an APN Network Identifier (APN-NI) and an APN Operator Identifier (APN-OI), which are as defined in clause 9.1.1 and 9.1.2 of the present document. + +If an APN is constructed using the default APN-OI, the APN-FQDN shall be obtained from the APN by inserting the labels "apn.epc." between the APN-NI and the default APN - OI, and by replacing the label ".gprs" at the end of the default APN-OI with the labels ".3gppnetwork.org". + +EXAMPLE1: For an APN of internet.mnc015.mcc234.gprs, the derived APN-FQDN is internet.apn.epc.mnc015.mcc234.3gppnetwork.org + +If an APN is constructed using the APN-OI Replacement field (as defined in 3GPP TS 23.060 [3] and 3GPP TS 23.401 [72]), the APN-FQDN shall be obtained from the APN by inserting the labels "apn.epc." between the label "mnc" and its preceding label, and by replacing the label ".gprs" at the end of the APN-OI Replacement field with the labels ".3gppnetwork.org". + +EXAMPLE 2: If an APN-OI Replacement field is province1.mnc015.mcc234.gprs and an APN-NI is internet, the derived APN-FQDN is internet.province1.apn.epc.mnc015.mcc234.3gppnetwork.org + +19.4.2.2.2 Void + +19.4.2.2.3 Void + +19.4.2.2.4 Void + +### 19.4.2.3 Tracking Area Identity (TAI) + +The Tracking Area Identity (TAI) consists of a Mobile Country Code (MCC), Mobile Network Code (MNC), and Tracking Area Code (TAC). It is composed as shown in figure 19.4.2.3.1. + +![Diagram showing the structure of the Tracking Area Identity (TAI). It consists of three boxes labeled MCC, MNC, and TAC. Below these boxes, a double-headed arrow labeled 'Tracking Area Identity' spans the width of the three boxes, indicating that the entire combination is the TAI.](53001b5ae3f65139f78db410bb41ae30_img.jpg) + +Diagram showing the structure of the Tracking Area Identity (TAI). It consists of three boxes labeled MCC, MNC, and TAC. Below these boxes, a double-headed arrow labeled 'Tracking Area Identity' spans the width of the three boxes, indicating that the entire combination is the TAI. + +**Figure 19.4.2.3.1: Structure of the Tracking Area Identity (TAI)** + +The TAI is composed of the following elements: + +- Mobile Country Code (MCC) identifies the country in which the PLMN is located. The value of the MCC is the same as the three digit MCC contained in the IMSI; +- Mobile Network Code (MNC) is a code identifying the PLMN in that country. The value of the MNC is the same as the two or three digit MNC contained in the IMSI; +- Tracking Area Code (TAC) is a fixed length code (of 2 octets) identifying a Tracking Area within a PLMN. This part of the tracking area identification shall be coded using a full hexadecimal representation. The following are reserved hexadecimal values of the TAC: + - 0000, and + - FFFE. + +NOTE: The above reserved values are used in some special cases when no valid TAI exists in the MS (see 3GPP TS 24.301 [90] for more information). + +A subdomain name can be derived from the TAI. This shall be done by adding the label "tac" to the beginning of the Home Network Realm/Domain (see clause 19.2) and encoding the TAC as a sub-domain. This is called the TAI FQDN.. + +The TAI FQDN shall be constructed as follows: + +tac-lb.tac-hb.tac.epc.mnc.mcc.3gppnetwork.org + +The TAC is a 16-bit integer. The is the hexadecimal string of the most significant byte in the TAC and the is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. + +### 19.4.2.4 Mobility Management Entity (MME) + +A Mobility Management Entity (MME) within an operator's network is identified using a MME Group ID (MMEGI), and an MME Code (MMEC). + +A subdomain name shall be derived from the MNC and MCC by adding the label "mme" to the beginning of the Home Network Realm/Domain (see clause 19.2). + +The MME node FQDN shall be constructed as: + +mme.mme.mme.epc.mnc.mcc.3gppnetwork.org + +Where and are the hexadecimal strings of the MMEC and MMEGI. + +An MME pool FQDN shall be constructed as: + +mme.mme.epc.mnc.mcc.3gppnetwork.org + +If there are less than 2 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. If there are less than 4 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 4 digit coding. + +#### 19.4.2.5      Routing Area Identity (RAI) - EPC + +The Routing Area Identity (RAI) consists of a RAC, LAC, MNC and MCC. + +A subdomain name for use by core network nodes based on RAI shall be derived from the MNC and MCC by adding the label "rac" to the beginning of the Home Network Realm/Domain (see clause 19.2). + +The RAI FQDN shall be constructed as: + +rac.lac.rac.epc.mnc.mcc.3gppnetwork.org + + and shall be Hex coded digits representing the LAC and RAC codes respectively. + +If there are less than 4 significant digits in or , one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. + +Note:      Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.2 are still used for existing A/AAAA records for pre-Release 8 nodes and are also still used for backward compatibility. + +#### 19.4.2.6      Serving GPRS Support Node (SGSN) within SGSN pool + +A specific SGSN within an operator's network is identified using the RAI FQDN (clause 19.4.2.5) and the Network Resource Identifier (NRI) (see 3GPP TS 23.236 [23]). Such an identifier can be used by a target MME or SGSN node to connect to the source SGSN node. + +The SGSN FQDN shall be constructed as: + +nri-sgsn.rac.lac.rac.epc.mnc.mcc.3gppnetwork.org + + shall be Hex coded digits representing the NRI code of the SGSN. + +If there are less than 4 significant digits in , one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. Coding for other fields is the same as in Clause 19.4.2.5. + +When a target MME constructs the FQDN of the source SGSN in the case of SGSN pooling, it should derive the NRI from the 8-bit MME Code received in the GUTI from the UE. However, if the length of the NRI, e.g., X, which is configured in the MME is less than 8 bits, then the MME should use only the most significant X bits of the MME Code as the NRI within the SGSN FQDN. + +Note:      Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.2 are still used for existing A/AAAA records for pre-Release 8 nodes and are also still used for backward compatibility. . + +#### 19.4.2.7      Target RNC-ID for U-TRAN + +In the special case of a UTRAN target RNC a possible SGSN that can control that RNC can be identified by RNC-ID. This identifier can be used for SRNS relocation with a U-TRAN target RNC. + +A subdomain name for use by core network nodes based on RNC-ID shall be derived from the MNC and MCC by adding the label "rnc" to the beginning of the Home Network Realm/Domain (see clause 19.2). + +The RNC FQDN shall be constructed as: + +`rnc.rnc.epc.mnc.mcc.3gppnetwork.org` + + shall be Hex coded digits representing the RNC-ID code of the RNC. + +If there are less than 4 significant digits in , one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. + +NOTE: Above subdomain is for release 8 core network nodes to allow DNS records other than A/AAAA records. The subdomain name in Annex C.3 are still used for existing A/AAAA records for pre-Release 8 nodes and are still used for backward compatibility. However, RNC-ID in Annex C.3 was originally intended for the case where only one SGSN controlled an RNC-ID and gave the SGSN IP address. The usage for the above RNC FQDN is potentially broader and can target an SGSN pool. + +#### 19.4.2.8 DNS subdomain for operator usage in EPC + +The EPC nodes DNS subdomain (DNS zone) shall be derived from the MNC and MCC by adding the label "node" to the beginning of the Home Network Realm/Domain (see clause 19.2) and shall be constructed as: + +`node.epc.mnc.mcc.3gppnetwork.org` + +This DNS subdomain is formally placed into the operator's control. 3GPP shall never take this DNS subdomain back or any zone cut/subdomain within it for any purpose. As a result the operator can safely provision any DNS records it chooses under this subdomain without concern about future 3GPP standards encroaching on the DNS names within this zone. + +#### 19.4.2.9 ePDG FQDN and Visited Country FQDN for non-emergency bearer services + +##### 19.4.2.9.1 General + +The ePDG Fully Qualified Domain Name (ePDG FQDN), for non-emergency bearers services, shall be constructed using one of the following formats, as specified in clause 4.5.4 of 3GPP TS 23.402 [68]: + +- Operator Identifier based ePDG FQDN; +- Tracking/Location Area Identity based ePDG FQDN; +- the ePDG FQDN configured in the UE by the HPLMN. + +NOTE: The ePDG FQDN configured in the UE can have a different format than those specified in the following clauses. + +The Visited Country FQDN is used by a roaming UE to determine whether the visited country mandates the selection of an ePDG in this country (see clause 4.5.4.5 of 3GPP TS 23.402 [68]). The Visited Country FQDN shall be constructed as specified in clause 19.4.2.9.4. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 19.4.2.9.5. + +##### 19.4.2.9.2 Operator Identifier based ePDG FQDN + +The ePDG Fully Qualified Domain Name (ePDG FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the ePDG is located. The ePDG FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "epdg.epc". The ePDG FQDN shall be constructed as follows: + +`"epdg.epc.mnc.mcc.pub.3gppnetwork.org"` + +In the roaming case, the UE can utilise the services of the VPLMN or the HPLMN (see 3GPP TS 23.402 [68] and 3GPP TS 24.302 [77]). In this case, the Operator Identifier based ePDG FQDN shall be constructed as described above, but using the MNC and MCC of the VPLMN or the HPLMN. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "epdg.epc.mnc.mcc.pub.3gppnetwork.org" format of the Operator Identifier based ePDG FQDN shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ePDG FQDN. + +As an example, the Operator Identifier based ePDG FQDN for MCC 345 and MNC 12 is coded in the DNS as: + +"epdg.epc.mnc012.mcc345.pub.3gppnetwork.org". + +### 19.4.2.9.3 Tracking/Location Area Identity based ePDG FQDN + +The Tracking/Location Area Identity based ePDG FQDN is used to support location based ePDG selection within a PLMN. + +There are two Tracking Area Identity based ePDG FQDNs defined: one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. + +- 1) The Tracking Area Identity based ePDG FQDN using a 2 octet TAC and the Location Area Identity based ePDG FQDN shall be constructed respectively as: + +"tac-lb.tac-hb.tac.epdg.epc.mnc.mcc.pub.3gppnetwork.org" + +and + +"lac.epdg.epc.mnc.mcc.pub.3gppnetwork.org" + +where + +- the and shall identify the PLMN where the ePDG is located and shall be encoded as + - = 3 digits + - = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ePDG FQDN. + +- the , together with the and shall identify the Tracking Area Identity the UE is located in. + +The TAC is a 16-bit integer. The is the hexadecimal string of the most significant byte in the TAC and the is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding; + +- the , together with the and shall identify the Location Area Identity the UE is located in. + +The LAC shall be hexadecimal coded digits representing the LAC; if there are less than 4 significant digits in , one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding; + +As examples, + +- the Tracking Area Identity based ePDG FQDN for the TAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: + +"tac-lb21.tac-hb0b.tac.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" + +- the Location Area Identity based ePDG FQDN for the LAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: + +"lac0b21.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" + +- 2) The 5GS Tracking Area Identity based ePDG FQDN using a 3 octet TAC shall be constructed respectively as: + +"tac-lb.tac-mb.tac-hb.5gstac. +epdg.epc.mnc.mcc.pub.3gppnetwork.org" + +where + +- the and shall identify the PLMN where the ePDG is located and shall be encoded as + - = 3 digits + - = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ePDG FQDN. + +- the , together with the and shall identify the 5GS Tracking Area Identity the UE is located in. + +The 5GS TAC is a 24-bit integer. The is the hexadecimal string of the most significant byte in the TAC and the is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in , or , "0" digit(s) shall be inserted at the left side to fill the 2 digits coding; + +As examples, + +- the 5GS Tracking Area Identity based ePDG FQDN for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: + +"tac-lb21.tac-mb1a.tac-hb0b.5gstac.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" + +#### 19.4.2.9.4 Visited Country FQDN + +The Visited Country FQDN, used by a roaming UE to determine whether the visited country mandates the selection of an ePDG in this country, shall be constructed as described below. + +The Visited Country FQDN shall contain a MCC that uniquely identifies the country in which the UE is located. + +The Visited Country FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The fourth label shall be "visited-country". The third label shall uniquely identify the MCC of the visited country. The first and second labels shall be "epdg.epc". The Visited Country FQDN shall be constructed as follows: + +"epdg.epc.mcc.visited-country.pub.3gppnetwork.org" + +The coding used in this FQDN shall be: + +- = 3 digits + +As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as: + +"epdg.epc.mcc345.visited-country.pub.3gppnetwork.org". + +#### 19.4.2.9.5 Replacement field used in DNS-based Discovery of regulatory requirements + +If the visited country mandates the selection of an ePDG in this country (see clause 4.5.4.5 of 3GPP TS 23.402 [68]), the NAPTR record(s) associated to the Visited Country FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country which may be used for ePDG selection. + +The replacement field shall take the form of an Operator Identifier based ePDG FQDN as specified in clause 19.4.2.9.2. + +For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN. + +As an example, the NAPTR records associated to the Visited Country FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: + +``` + +epdg.epc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement + IN NAPTR 100 999 "" "" epdg.epc.mnc012.mcc345.pub.3gppnetwork.org + IN NAPTR 100 999 "" "" epdg.epc.mnc013.mcc345.pub.3gppnetwork.org + IN NAPTR 100 999 "" "" epdg.epc.mnc014.mcc345.pub.3gppnetwork.org + +``` + +## 19.4.2.9A ePDG FQDN for emergency bearer services + +### 19.4.2.9A.1 General + +The ePDG FQDN used for the selection of an ePDG supporting emergency bearer services shall be constructed using one of the following formats, as specified in clause 4.5.4a of 3GPP TS 23.402 [68] and 3GPP TS 24.302 [77]: + +- an Operator Identifier based Emergency ePDG FQDN; +- a Tracking/Location Area Identity based Emergency ePDG FQDN; +- an Emergency ePDG FQDN configured in the UE by the HPLMN, which may have a different format than the one specified in the following clause. + +The Visited Country Emergency FQDN is used by a roaming UE, in the context of an emergency session, to determine whether the visited country mandates the selection of an ePDG in this country. The Visited Country Emergency FQDN shall be constructed as specified in clause 19.4.2.9A.4. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 19.4.2.9A.5. + +The Visited Country Emergency Numbers FQDN is used by a roaming UE to determine the list of emergency numbers and related emergency service types in the the visited country. + +### 19.4.2.9A.2 Operator Identifier based Emergency ePDG FQDN + +The Operator Identifier based Emergency ePDG FQDN shall be constructed as specified for the Operator Identifier based ePDG FQDN in clause 19.4.2.9.2, with the addition of the label "sos" before the labels "epdg.epc". The Emergency ePDG FQDN shall be constructed as follows: + +"sos.epdg.epc.mnc.mcc.pub.3gppnetwork.org" + +As an example, the Operator Identifier based Emergency ePDG FQDN for MCC 345 and MNC 12 is coded in the DNS as: + +"sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org". + +### 19.4.2.9A.3 Tracking/Location Area Identity based Emergency ePDG FQDN + +There are two Tracking Area Identity based Emergency ePDG FQDNs defined: one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. + +- 1) The Tracking Area Identity based Emergency ePDG FQDN using a 2 octet TAC and the Location Area Identity based Emergency ePDG FQDN shall be constructed as specified for the Tracking Area Identity based ePDG FQDN and the Location Area Identity based ePDG FQDN in clause 19.4.2.9.3, with the addition of the label "sos" before the labels "epdg.epc". + +The Tracking Area Identity based Emergency ePDG FQDN and the Location Area Identity based Emergency ePDG FQDN shall be constructed as follows: + +"tac-lb.tac-hb.tac.sos.epdg.epc.mnc.mcc.pub.3gppnetwork.org" + +and + +"lac.sos.epdg.epc.mnc.mcc.pub.3gppnetwork.org" + +As examples, + +- the Tracking Area Identity based Emergency ePDG FQDN for the TAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: + +" tac-lb21.tac-hb0b.tac.sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" + +- the Location Area Identity based Emergency ePDG FQDN for the LAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: + +" lac0b21.sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" + +- 2) The 5GS Tracking Area Identity based Emergency ePDG FQDN using a 3 octet TAC shall be constructed as specified for the 5GS Tracking Area Identity based ePDG FQDN in clause 19.4.2.9.3, with the addition of the label "sos" before the labels "epdg.epc". + +The 5GS Tracking Area Identity based Emergency ePDG FQDN shall be constructed as follows: + +"tac-lb.tac-mb.tac-hb.5gstac.sos.epdg.epc.mnc.mcc.pub.3gppnetwork.org " + +As examples, + +- the 5GS Tracking Area Identity based Emergency ePDG FQDN for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: + +"tac-lb21.tac-mb1a.tac-hb0b.5gstac.sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" + +#### 19.4.2.9.A.4 Visited Country Emergency FQDN + +The Visited Country Emergency FQDN shall be constructed as specified for the Visited Country FQDN in clause 19.4.2.9.4, with the addition of the label "sos" before the labels "epdg.epc". + +The Visited Country Emergency FQDN shall be constructed as follows: + +"sos.epdg.epc.mcc.visited-country.pub.3gppnetwork.org" + +As an example, the Visited Country Emergency FQDN for MCC 345 is coded in the DNS as: + +"sos.epdg.epc.mcc345.visited-country.pub.3gppnetwork.org". + +#### 19.4.2.9.A.5 Replacement field used in DNS-based Discovery of regulatory requirements for emergency services + +The requirements specified in clause 19.4.2.9.5 for the Replacement field used in DNS-based Discovery of regulatory requirements shall apply with the following modification. + +The replacement field shall take the form of an Operator Identifier based Emergency ePDG FQDN as specified in clause 19.4.2.9.A.2. + +As an example, the NAPTR records associated to the Visited Country FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: + +``` +sos.epdg.epc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement +IN NAPTR 100 999 "" "" sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" sos.epdg.epc.mnc013.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" sos.epdg.epc.mnc014.mcc345.pub.3gppnetwork.org +``` + +#### 19.4.2.9.A.6 Country based Emergency Numbers FQDN + +The Country based Emergency Numbers FQDN shall be constructed as specified for the Visited Country Emergency FQDN in clause 19.4.2.9.A.4, but with replacing the label "epdg" by the label "en". + +The Country based Emergency Numbers FQDN shall be constructed as follows: + +"sos.en.epc.mcc.visited-country.pub.3gppnetwork.org" + +NOTE: Even though a label named "visited-country" is present, operators in the home country can use the same mechanism to provide emergency numbers and associated type(s). + +As an example, the Country based Emergency Numbers FQDN for MCC 345 is coded in the DNS as: + +"sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org". + +#### 19.4.2.9A.7 Replacement field used in DNS-based Discovery of Emergency Numbers + +The NAPTR record(s) associated to the Country based Emergency Numbers FQDN shall be provisioned with the replacement field containing the emergency numbers and related emergency service types. + +The replacement field shall take the following form and include both an emergency number and at least one emergency service type: + +..sos.en.epc.mcc.visited-country.pub.3gppnetwork.org + +The and shall follow the syntax defined in Table 19.4.2.9A.7-1. The shall consist of a single label. The shall consist of at least one label. + +**Table 19.4.2.9A.7-1: Syntax of emergency number and emergency type** + +``` + +emergency-number = DIGIT*DIGIT ; at least one DIGIT +emergency-type = "sos" *("." sub-label) +sub-label = let-dig [ *61let-dig-hyp let-dig ] +let-dig-hyp = let-dig / "-" +let-dig = ALPHA / DIGIT +ALPHA = %x41-5A / %x61-7A ; A-Z / a-z + +``` + +As an example, the NAPTR records associated to the Country based Emergency Numbers FQDN for MCC 345 are provisioned in the DNS as: + +``` + +sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement + IN NAPTR 100 999 "" "" sos.ambulance.15.sos.en.epc.mcc345.visited- +country.pub.3gppnetwork.org + IN NAPTR 100 999 "" "" sos.police.17.sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org + IN NAPTR 100 999 "" "" sos.fire.18.sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org + IN NAPTR 100 999 "" "" sos.marine.196.sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org + +``` + +#### 19.4.2.10 Global eNodeB-ID for eNodeB + +The Global eNodeB-ID is used to identify eNodeBs globally which is composed of the concatenation of MCC, MNC and the eNodeBID. The MCC and MNC are the same as included in the E-UTRAN Cell Global Identifier (ECGI) (see clause 19.6). + +A subdomain name shall be derived from the MNC and MCC by adding the label "enb" to the beginning of the Home Network Realm/Domain (see clause 19.2). + +The Global eNodeB-ID FQDN shall be constructed as: + +enb.enb.epc.mnc.mcc.3gppnetwork.org + +The shall be coded using a full hexadecimal representation. If there are less than 4 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 4 digit coding. + +#### 19.4.2.11 Local Home Network identifier + +The Local Home Network identifier uniquely identifies a local home network. For the definition of a local home network see 3GPP TS 23.060 [3] and 3GPP TS 23.401 [72]. + +A subdomain name shall be derived from the MNC and MCC from the visited network by adding the label "lhn" to the beginning of the Home Network Realm/Domain (see clause 19.2). + +The Local Home Network-ID FQDN shall be constructed as: + +lhn< LHN name >.lhn.epc.mnc.mcc.3gppnetwork.org + +The length and content is an operator choice. The labels shall follow the rules specified in clause 19.4.2.1. + +### 19.4.2.12 UCMF + +The UCMF FQDN shall be constructed as: + +ucmf.epc.mnc.mcc.3gppnetwork.org + +Where and are taken from the serving network identity. + +### 19.4.2.13 PGW Set FQDN + +A PGW Set Identifier is a globally unique identifier of a set of equivalent and interchangeable PGWs from a given network that provides distribution, redundancy and scalability. + +A PGW Set Identifier shall be constructed from the MCC, MNC and a Set ID. + +The PGW Set FQDN shall be constructed as follows: + +set.pgwset.epc.mnc.mcc.3gppnetwork.org + +where + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the PGW Set FQDN. + +- is the string representing a PGW Set within the PLMN, chosen by the operator, that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit, where the case of alphabetic characters is not significant (i.e. two PGW Set IDs with the same characters but using different lower and upper cases identify the same PGW Set). + +EXAMPLE: "set12.pgwset.epc.mnc012.mcc345.3gppnetwork.org" (for the PGW set from MCC 345, MNC 12 and Set ID "12") + +### 19.4.3 Service and Protocol service names for 3GPP + +A list of standardized "service-parms" names is required to identify a "service" as defined in clause 6.5 of IETF RFC 3958 [74]. + +The following table defines the names to be used in the procedures specified in 3GPP TS 29.303 [73]: + +Table 19.4.3.1: List of 'app-service' and 'app-protocol' names + +| Description | IETF RFC 3958 clause 6.5
'app-service' name | IETF RFC 3958 clause 6.5
'app-protocol' name | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| +| PGW and interface types supported by the PGW | x-3gpp-pgw | x-s5-gtp, x-s5-pmip, x-s8-gtp, x-s8-pmip, x-s2a-pmip, x-s2a-mipv4, x-s2a-gtp, x-s2b-pmip, x-s2b-gtp, x-s2c-dsmip, x-gn, x-gp
See NOTE. | +| SGW and interface types supported by the SGW | x-3gpp-sgw | x-s5-gtp, x-s5-pmip, x-s8-gtp, x-s8-pmip, x-s11, x-s12, x-s4, x-s1-u, x-s2a-pmip, x-s2b-pmip
See NOTE. | +| GGSN | x-3gpp-ggsn | x-gn, x-gp
See NOTE. | +| SGSN | x-3gpp-sgsn | x-gn, x-gp, x-s4, x-s3, x-s16, x-sv, x-nqprime
See NOTE. | +| MME and interface types supported by the MME | x-3gpp-mme | x-s10, x-s11, x-s3, x-s6a, x-s1-mme, x-gn, x-gp, x-sv, x-nq
See NOTE. | +| MSC Server | x-3gpp-msc | x-sv | +| UP function | x-3gpp-upf | x-sxa, x-sxb, x-sxc, x-n4, x-n4mb
See NOTE. | +| AMF | x-3gpp-amf | x-n2
x-n26
See NOTE. | +| UCMF | x-3gpp-ucmf | x-urcmp
x-n55 | +|

NOTE: When using Dedicated Core Networks, the character string "+ue-<ue usage type>" shall be appended to the 'app-protocol' name, for the interfaces applicable to Dedicated Core Networks, where <ue-usage-type> contains one or more UE usage type values. See 3GPP TS 29.303 [73], 3GPP TS 29.272 [108] and 3GPP TS 29.273 [78].

Example: x-s5-gtp+ue-<ue usage type>

If multiple UE usage type values are embedded in the "+ue-<ue usage type>", they shall be separated by the symbol ".", e.g. "+ue-1.3.4.20" as specified in IETF RFC 3958 [74].

To select a network node with a particular network capability needed, the character string "+nc-<network capability>" shall be appended to the 'app-protocol' name, where < network capability > contains one or more network capability of the node. See 3GPP TS 29.303 [73].

Example: x-s5-gtp+nc-<network capability>

If multiple network capability of the node are embedded in the "+nc-<network capability>", they shall be separated by the symbol ".", e.g. "+nc-nr.smf", as specified in IETF RFC 3958 [74].

To select a network node with a particular network capability needed within a certain Dedicated Core Networks, the character string "+nc-<network capability>" and "+ue-<ue usage type>" shall be appended to the 'app-protocol' name, where <ue usage type> contains one or more UE usage type values and the

Example: x-s5-gtp+nc-<network capability>+ue-<ue usage type> or x-s5-gtp+ue-<ue usage type>+nc-<network capability>

| | | + +NOTE 1: The formats follow the experimental format as specified in IETF RFC 3958 [74]. For example, to find the S8 PMIP interfaces on a PGW the Service Parameter of "3gpp-pgw:x-s8-pmip" would be used as input in the procedures defined in IETF RFC 3958 [74]. + +NOTE 2: Currently 'app-service' names identify 3GPP node type and 'app-protocol' identify 3GPP interfaces, which differs from more common usage of S-NAPTR where app-protocol is used for transport protocol. Type of nodes (i.e PGW, SGW, SGSN, MME, MSC Server etc) and interfaces (i.e. S11, S5, S8, Sv, etc.) follow the standard names from 3GPP TS 23.401 [72], 3GPP TS 29.060 [6] and 3GPP TS 23.216 [92] with prefix "x-" added. + +NOTE 3: x-gn denotes an intra-PLMN interface using GTPv1-C, x-gp denotes an inter-PLMN interface using GTPv1-C. + +NOTE 4: The app-service of x-3gpp-pgw with app-protocols x-gn or x-gp identifies the co-located GGSN function on a PGW. The app-service of x-3gpp-ggsn with app-protocols x-gn or x-gp identifies a GGSN function that is not co-located with a PGW. + +NOTE 5: The app-service of x-3gpp-msc with app-protocol x-sv identifies the MSC Sv interface service. + +NOTE 6: The app-service of x-3gpp-amf with app-protocol x-n2 identifies the AMF N2 interface service. The app-service of x-3gpp-amf with app-protocol x-n26 identifies the AMF N26 interface service. + +## 19.5 Access Network Identity + +A trusted non-3GPP access network used by the UE to access EPS can be identified using the Access Network Identity. The Access Network Identity is used as an input parameter in the EPS security procedures as specified in 3GPP TS 33.402 [69]. The format and signalling of the parameter between the network and the UE is specified in 3GPP TS 24.302 [77] and the format and signalling of this parameter between access network and core network is specified in 3GPP TS 29.273 [78]. + +The encoding of the Access Network Identity shall be specified within 3GPP, but the Access Network Identity definition for each non-3GPP access network is under the responsibility of the corresponding standardisation organisation respectively. + +## 19.6 E-UTRAN Cell Identity (ECI) and E-UTRAN Cell Global Identification (ECGI) + +The E-UTRAN Cell Global Identification (ECGI) shall be composed of the concatenation of the PLMN Identifier (PLMN-Id) and the E-UTRAN Cell Identity (ECI) as shown in figure 19.6-1 and shall be globally unique: + +![Diagram showing the structure of E-UTRAN Cell Global Identification (ECGI). It consists of three boxes labeled MCC, MNC, and ECI. Below these boxes is a double-headed arrow labeled 'E-UTRAN Cell Global Identification'.](f43d225d8fed2845b8d7e5afecbfe636_img.jpg) + +The diagram illustrates the structure of the E-UTRAN Cell Global Identification (ECGI). It is composed of three distinct parts: MCC (Mobile Country Code), MNC (Mobile Network Code), and ECI (E-UTRAN Cell Identity). These three components are shown in separate rectangular boxes arranged horizontally. Below these boxes, a horizontal double-headed arrow spans the entire width, with the text "E-UTRAN Cell Global Identification" centered beneath it, indicating that the concatenation of MCC, MNC, and ECI forms the ECGI. + +Diagram showing the structure of E-UTRAN Cell Global Identification (ECGI). It consists of three boxes labeled MCC, MNC, and ECI. Below these boxes is a double-headed arrow labeled 'E-UTRAN Cell Global Identification'. + +**Figure 19.6-1: Structure of E-UTRAN Cell Global Identification** + +The ECI shall be of fixed length of 28 bits and shall be coded using full hexadecimal representation. The exact coding of the ECI is the responsibility of each PLMN operator. + +For more details on ECI and ECGI, see 3GPP TS 36.413 [84]. + +NOTE: In the 5G Core Network protocols, when the ECGI needs to be identified in the context of Standalone Non-Public Networks (SNPN), the Network Identifier (NID) of the SNPN is included as part of the ECGI Information Element (see 3GPP TS 29.571 [129]); this is a protocol aspect that does not imply any change on the system-wide definition of the ECGI. + +## 19.6A NR Cell Identity (NCI) and NR Cell Global Identity (NCGI) + +The NR Cell Global Identity (NCGI) shall be composed of the concatenation of the PLMN Identifier (PLMN-Id) and the NR Cell Identity (NCI) as shown in figure 19.6A-1 and shall be globally unique: + +![Diagram showing the structure of NR Cell Global Identity. It consists of three boxes labeled MCC, MNC, and NCI. Below these boxes is a double-headed arrow labeled 'NR Cell Global Identification'.](8a781a0a8c956859f63a1ca7f2bb1644_img.jpg) + +The diagram illustrates the structure of the NR Cell Global Identity. It features three rectangular boxes arranged horizontally, labeled 'MCC', 'MNC', and 'NCI' from left to right. Below these boxes, a horizontal double-headed arrow spans the width, with the text 'NR Cell Global Identification' centered above it. + +Diagram showing the structure of NR Cell Global Identity. It consists of three boxes labeled MCC, MNC, and NCI. Below these boxes is a double-headed arrow labeled 'NR Cell Global Identification'. + +**Figure 19.6A-1: Structure of NR Cell Global Identity** + +The NCI shall be of fixed length of 36 bits and shall be coded using full hexadecimal representation. The exact coding of the NCI is the responsibility of each PLMN operator. + +For more details on NCI and NCGI, see 3GPP TS 38.413 [123]. + +**NOTE:** In the 5G Core Network protocols, when the NCGI needs to be identified in the context of Standalone Non-Public Networks (SNPN), the Network Identifier (NID) of the SNPN is included as part of the NCGI Information Element (see 3GPP TS 29.571 [129]); this is a protocol aspect that does not imply any change on the system-wide definition of the NCGI. + +## 19.7 Identifiers for communications with packet data networks and applications + +### 19.7.1 Introduction + +This clause describes external identifiers used to facilitate communications with packet data networks and applications (e.g. Machine Type Communication (MTC) applications on the external network/MTC servers) as specified in 3GPP TS 23.682 [98], 3GPP TS 23.501 [119] and 3GPP TS 23.502 [120]. + +### 19.7.2 External Identifier + +An External Identifier identifies a subscription associated to an IMSI. A subscription associated to an IMSI may have one or several External Identifier(s). + +The External Identifier shall have the form `username@realm` as specified in clause 2.1 of IETF RFC 4282 [53]. + +The username part format of the External Identifier shall contain a Local Identifier as specified in 3GPP TS 23.682 [98]. The realm part format of the External Identifier shall contain a Domain Identifier as specified in 3GPP TS 23.682 [98]. As specified in clause 4 of IETF RFC 4282 [53], the Domain Identifier shall be a duly registered Internet domain name. The combination of Local Identifier and Domain Identifier makes the External Identifier globally unique. + +The result of the External Identifier form is: + +`"@"` + +An example of an External Identifier is: + +Local Identifier in use: "123456789"; + +Domain Identifier = "domain.com"; + +Which gives the External Identifier as: + +`123456789@domain.com` + +### 19.7.3 External Group Identifier + +An External Group Identifier identifies a group made up of one or more subscriptions associated to a group of IMSIs. + +The External Group Identifier shall have the form `groupname@realm` as specified in clause 2.1 of IETF RFC 4282 [53]. + +The groupname part format of the External Group Identifier shall contain a Local Identifier as specified in 3GPP TS 23.682 [98]. The realm part format of the External Group Identifier shall contain a Domain Identifier as specified in 3GPP TS 23.682 [98]. As specified in clause 4 of IETF RFC 4282 [53], the Domain Identifier shall be a duly registered Internet domain name. The combination of Local Identifier and Domain Identifier makes the External Group Identifier globally unique. + +The result of the External Group Identifier form is: + +"@" + +An example of an External Group Identifier is: + +Local Identifier in use: "Group1"; + +Domain Identifier = "domain.com"; + +Which gives the External Group Identifier as: + +Group1@domain.com + +## 19.8 TWAN Operator Name + +The TWAN Operator Name identifies the TWAN operator when the TWAN is not operated by a mobile operator. + +The TWAN Operator Name shall be encoded as a realm in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The TWAN Operator Name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +NOTE: The TWAN Operator Name is encoded as a dotted string. + +## 19.9 IMSI-Group Identifier + +IMSI-Group Identifier is a network internal globally unique ID which identifies a set of IMSIs (e.g. MTC devices) from a given network that are grouped together for one specific group related services. It is used e.g. for group specific NAS level congestion control (see 3GPP TS 23.401 [72]). + +An IMSI-Group Identifier shall be composed as shown in figure 19.9-1. + +![Diagram showing the structure of the IMSI-Group Identifier, composed of four parts: Group Service Identifier (4 octets), Mobile Country Code (MCC) (3 digits), Mobile Network Code (MNC) (2-3 digits), and Local Group Id (Up to 10 octets).](b22a2b17c5f35e4706033e34ab0f3e9a_img.jpg) + +The diagram illustrates the structure of the IMSI-Group Identifier. It is a horizontal bar divided into four segments, each with a label above it and a dimension below it. The segments are: + + +- Group Service Identifier**: 4 octets +- Mobile Country Code (MCC)**: 3 digits +- Mobile Network Code (MNC)**: 2-3 digits +- Local Group Id**: Up to 10 octets + + A long double-headed arrow above the segments is labeled "IMSI-Group Identifier", indicating the entire bar represents this identifier. + +Diagram showing the structure of the IMSI-Group Identifier, composed of four parts: Group Service Identifier (4 octets), Mobile Country Code (MCC) (3 digits), Mobile Network Code (MNC) (2-3 digits), and Local Group Id (Up to 10 octets). + +**Figure 19.9-1: Structure of IMSI-Group Identifier** + +IMSI-Group Identifier is composed of four parts: + +- 1) Group Service Identifier, identifies the service (4 Octets) for which the IMSI-Group Identifier is valid. +- 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the mobile subscriber; +- 3) Mobile Network Code (MNC) consisting of two or three digits. The MNC identifies the home PLMN of the mobile subscriber. The length of the MNC (two or three digits) depends on the value of the MCC. A mixture of + +two and three digit MNC codes within a single MCC area is not recommended and is outside the scope of this specification. + +- 4) the Local Group Id is assigned by the network operator and may have a length of up to 10 octets. + +Two different IMSI-Group Identifier values, with the same Group Service Identifier and with MCC/MNC values that point to the same PLMN, shall have two different Local Group Ids. + +## 19.10 Presence Reporting Area Identifier (PRA ID) + +The Presence Reporting Area Identifier (PRA ID) is used to identify a Presence Reporting Area (PRA). + +PRAs can be used for reporting changes of UE presence in a PRA, e.g. for policy control or charging decisions. See 3GPP TS 23.401 [72], 3GPP TS 23.060 [3] and 3GPP TS 23.203 [107]. + +A PRA is composed of a short list of TAs/RAs, or eNBs and/or cells/SAs in a PLMN. A PRA can be: + +- either a "UE-dedicated PRA", defined in the subscriber profile; +- or a "Core Network predefined PRA", pre-configured in MME/S4-SGSN. + +PRA IDs used to identify "Core Network predefined PRAs" shall not be used for identifying "UE-dedicated PRAs". + +The same PRA ID may be used for different UEs to identify different "UE-dedicated PRAs", i.e. PRA IDs may overlap between different UEs, while identifying different "UE-dedicated PRAs". + +The PRA ID shall be encoded as an integer on 3 octets. The most significant bit of the PRA ID shall be set to 0 for UE-dedicated PRA and shall be to 1 for Core Network predefined PRA. + +## 19.11 Dedicated Core Networks Identifier + +A Dedicated Core Network ID (DCN-ID) identifies a Dedicated Core Network (DCN) within a PLMN. + +The allowed values of DCN-ID shall be in the range of 0 to 65535. + +Values in the range of 0 to 127 are standardized and defined as follows: + +0: Spare, for future use + +... + +127: Spare, for future use + +Values in the range of 128 to 65535 are operator-specific. + +The use of the standardized DCN-ID is specified in 3GPP TS 23.401 [72]. + +--- + +# 20 Addressing and Identification for IMS Centralized Services + +## 20.1 Introduction + +This clause describes the format of the parameters needed specifically for IMS Centralized Services (ICS). For further information on the use of ICS parameters, see 3GPP TS 23.292 [70]. + +## 20.2 UE based solution + +In this solution, the UE is provisioned with an ICS specific client that simply reuses IMS registration as defined in 3GPP TS 23.228 [24]. Therefore, ICS capable UE shall reuse the identities defined in clause 13. + +## 20.3 Network based solution + +### 20.3.1 General + +In this solution the MSC Server enhanced for ICS performs a special IMS registration on behalf of the UE. Thus, the MSC Server enhanced for ICS shall use a Private User Identity and Temporary Public User Identity that are different to those defined in clause 13 (see 3GPP TS 23.292 [70], clause 4.6.2 for more information). Furthermore, the MSC Server enhanced for ICS derives a Conference Factory URI that is known to the home IMS. These are defined in the following clauses. + +### 20.3.2 Home network domain name + +The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +The MSC Server enhanced for ICS shall derive the home network domain name from the subscriber's IMSI as described in the following steps: + +1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning. +2. Use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name. +3. Add the label "ics." to the beginning of the domain. + +An example of a home network domain name is: + +IMSI in use: 234150999999999; + +where: + +- MCC = 234; +- MNC = 15; and +- MSIN = 0999999999, + +which gives the home network domain name: ics.mnc015.mcc234.3gppnetwork.org + +### 20.3.3 Private User Identity + +The Private User Identity shall take the form of an NAI, and shall have the form "username@realm" as specified in clause 2.1 of IETF RFC 4282 [53]. + +The MSC Server enhanced for ICS shall derive the Private User Identity from the subscriber's IMSI as follows: + +1. Use the whole string of digits as the username part of the private user identity; and +2. convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 20.3.2. + +The result will be a Private User Identity of the form "@ics.mnc.mcc.3gppnetwork.org". For example if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identity then takes the form 234150999999999@ics.mnc015.mcc234.3gppnetwork.org + +### 20.3.4 Public User Identity + +The Public User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]), and shall have the form "sip:username@domain". + +The MSC Server enhanced for ICS shall derive the Public User Identity from the subscriber's IMSI. The Public User Identity shall consist of the string "sip:" appended with a username and domain portion equal to the IMSI derived Private User Identity described in clause 20.3.3. An example using the same example IMSI from clause 20.3.3 can be found below: + +EXAMPLE: "sip:234150999999999@ics.mnc015.mcc234.3gppnetwork.org". + +## 20.3.5 Conference Factory URI + +The Conference Factory URI shall take the form of a SIP URI (see IETF RFC 3261 [26]) with a host portion set to the home network domain name as described in clause 20.3.2 prefixed with "conf-factory.". An example using the same example IMSI from clause 20.3.2 can be found below: + +EXAMPLE: "sip:conf-factory.ics.mnc015.mcc234.3gppnetwork.org". + +The user portion of the SIP URI is optional and implementation specific. + +--- + +# 21 Addressing and Identification for Dual Stack Mobile IPv6 (DSMIPv6) + +## 21.1 Introduction + +This clause describes the format of the parameters needed by the UE to use Dual Stack Mobile IPv6 (DSMIPv6) as specified in 3GPP TS 23.327 [76] and 3GPP TS 23.402 [68]. + +## 21.2 Home Agent – Access Point Name (HA-APN) + +### 21.2.1 General + +The HA-APN is composed of two parts as follows: + +- The HA-APN Network Identifier; this defines to which external network the HA is connected. +- The HA-APN Operator Identifier; this defines in which PLMN the HA serving the HA-APN is located. + +The HA-APN Operator Identifier is placed after the HA-APN Network Identifier. The HA-APN consisting of both the Network Identifier and Operator Identifier corresponds to a FQDN of a HA; the HA-APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. + +The encoding of the HA-APN shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. The HA-APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The HA-APN is not terminated by a length byte of zero. + +For the purpose of presentation, a HA-APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). + +### 21.2.2 Format of HA-APN Network Identifier + +The HA-APN Network Identifier follows the format defined for APNs in clause 9.1.1. In addition to what has been defined in clause 9.1.1 the HA-APN Network Identifier shall not contain "ha-apn." or "w-apn." and not end in ".3gppnetwork.org". + +A HA-APN Network Identifier may be used to access a service associated with a HA. This may be achieved by defining: + +- a HA-APN which corresponds to a FQDN of a HA, and which is locally interpreted by the HA as a request for a specific service, or +- a HA-APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or a HA-APN Network Identifier consisting of a Reserved Service Label alone, which indicates a HA by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have roaming agreements. + +As an example, the HA-APN for MCC 345 and MNC 12 is coded in the DNS as: + +"internet.ha-apn.mnc012.mcc345.pub.3gppnetwork.org". + +where "internet" is the HA-APN Network Identifier and "mnc012.mcc345.pub.3gppnetwork.org" is the HA-APN Operator Identifier. + +### 21.2.3 Format of HA-APN Operator Identifier + +The HA-APN Operator Identifier is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label distinguishes the domain name as a HA-APN. + +For each operator, there is a default HA-APN Operator Identifier (i.e. domain name). This default HA-APN Operator Identifier is derived from the IMSI as follows: + +"ha-apn.mnc.mcc.pub.3gppnetwork.org" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + + and are derived from the components of the IMSI defined in clause 2.2. + +Alternatively, the default HA-APN Operator Identifier is derived using the MNC and MCC of the VPLMN. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "ha-apn.mnc.mcc.pub.3gppnetwork.org" format of the HA-APN OI shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the HA-APN OI. + +As an example, the HA-APN OI for MCC 345 and MNC 12 is coded in the DNS as: + +"ha-apn.mnc012.mcc345.pub.3gppnetwork.org". + +## 22 Addressing and identification for ANDSF + +### 22.1 Introduction + +This clause describes the format of the parameters needed by the UE to use Access Network Discovery and Selection Function (ANDSF) as specified in 3GPP TS 23.402 [68]. + +### 22.2 ANDSF Server Name (ANDSF-SN) + +#### 22.2.1 General + +ANDSF Server Name (ANDSF-SN) is used by UE to discover ANDSF Server in the network. + +## 22.2.2 Format of ANDSF-SN + +The ANDSF-SN is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label shall be "andsf". + +The ANDSF-SN is derived from the IMSI or Visited PLMN Identity as follows: + +"andsf.mnc.mcc.pub.3gppnetwork.org" + +where: + +"mnc" and "mcc" serve as invariable identifiers for the following digits. + +- When contacting Visited ANDSF (V-ANDSF), the and shall be derived from the Visited PLMN Identity as defined in clause 12.1. +- When contacting Home ANDSF (H-ANDSF), the and shall be derived from the components of the IMSI defined in clause 2.2. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "andsf.mnc.mcc.pub.3gppnetwork.org" format of the ANDSF-SN shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ANDSF-SN. + +As an example, the ANDSF-SN OI for MCC 345 and MNC 12 is coded in the DNS as: + +"andsf.mnc012.mcc345.pub.3gppnetwork.org". + +# 23 Numbering, addressing and identification for the OAM System + +## 23.1 Introduction + +This clause describes some information needed to access the OAM system as specified in TS 36.300 [91]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +## 23.2 OAM System Realm/Domain + +The OAM System Realm/Domain shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The OAM System Realm/Domain consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +The OAM System Realm/Domain shall be in the form of "oam.mnc.mcc.3gppnetwork.org", where "" and "" fields correspond to the MNC and MCC of the operator's PLMN. Both the "" and "" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning. + +For example, the OAM System Realm/Domain of an IMSI shall be derived as described in the following steps: + +1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name; + +3. add the label "oam" to the beginning of the domain name. + +An example of an OAM System Realm/Domain is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 0999999999; + +Which gives the OAM System Realm/Domain name: oam.mnc015.mcc234.3gppnetwork.org. + +NOTE: If it is not possible for a Relay Node to identify whether a 2 or 3 digit MNC is used (e.g. USIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the Relay Node determines the length of the MNC (2 or 3 digits). + +## 23.3 Identifiers for Domain Name System procedures + +### 23.3.1 Introduction + +This clause describes Domain Name System (DNS) related identifiers used by the procedures specified in 3GPP TS 29.303 [73]. + +### 23.3.2 Fully Qualified Domain Names (FQDNs) + +#### 23.3.2.1 General + +See clause 19.4.2.1. + +#### 23.3.2.2 Relay Node Vendor-Specific OAM System + +As part of the startup procedure, relay nodes (see 3GPP TS 36.300 [91], clause 4.7) needs to discover its Operations and Maintenance (OAM) system. A relay node vendor-specific OAM system within an operator's network is identified using the relay node type allocation code from IMEI or IMEISV (IMEI-TAC), MNC and MCC from IMSI and in some cases also tracking area code information associated to the eNB serving the relay node. + +A subdomain name for use by EUTRAN OAM system nodes shall be derived from the MNC and MCC by adding the label "eutran" to the beginning of the OAM System Realm/Domain (see clause 23.2). + +The vendor-specific relay node OAM system FQDN shall be constructed as following: + +- tac-lb.tac-hb.imei-tac.eutran-rn.oam.mnc.mcc.3gppnetwork.org + +The IMEI-TAC is 8 decimal digits (see clause 6.2). + +NOTE: IMEI-TAC is used for the type allocation code from IMEI or IMEISV instead of TAC in this clause in order to separate it from the tracking area code (TAC). + +The TAC is a 16 bit integer. is the hexadecimal string of the most significant byte in the TAC and is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. + +### 23.3.2.3 Multi-vendor eNodeB Plug-and Play Vendor-Specific OAM System + +#### 23.3.2.3.1 General + +This clause describes the Fully Qualified Domain Names (FQDNs) used in Multi Vendor Plug and Connect (MvPnC) procedures (see 3GPP TS 32.508 [102]). + +The FQDNs used in MvPnC shall be in the form of an Internet domain name and follow the general encoding rules specified in clause 19.4.2.1. + +The format of FQDNs used in MvPnC shall follow the ".." pattern. + +NOTE: "..oam" represents the shown in the first row of table E.1. + +The label is optional and is only used in the operator deployments where multiple instances of a particular network entity type are not provided by the same vendor. If present, the label shall be in the form "vendor", where field corresponds to the ID of the vendor. + +The format of the ViD is vendor specific. + +The details of the label are specified in the clauses below. + +#### 23.3.2.3.2 Certification Authority server + +The Certification Authority server (CA/RA) FQDN shall be derived as follows. The "cara" label is added in front of the operator's OAM realm domain name: + +cara.oam.mnc.mcc.3gppnetwork.org + +If particular operator deployment scenarios where there are multiple CA/RA servers (one per vendor), the label is added in front of the "cara" label: + +vendor.cara.oam.mnc.mcc.3gppnetwork.org + +An example of a CA/RA FQDN is: + +MCC = 123; + +MNC = 45; + +ViD = abcd; + +which gives the CA/RA FQDN: "cara.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.cara.mnc045.mcc123.3gppnetwork.org". + +#### 23.3.2.3.3 Security Gateway + +The Security Gateway (SeGW) FQDN shall be derived as follows. The "segw" label is added in front of the operator's OAM realm domain name: + +segw.oam.mnc.mcc.3gppnetwork.org + +If particular operator deployment scenarios where there are multiple Security Gateways (one per vendor), the label is added in front of the "segw" label: + +vendor.segw.oam.mnc.mcc.3gppnetwork.org + +An example of a SeGW FQDN is: + +MCC = 123; + +MNC = 45; + +ViD = abcd; + +which gives the SeGW FQDN: "segw.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.segw.mnc045.mcc123.3gppnetwork.org". + +### 23.3.2.3.4 Element Manager + +The Element Manager (EM) FQDN shall be derived as follows. The "em" label is added in front of the operator's OAM realm domain name: + +em.oam.mnc.mcc.3gppnetwork.org + +If particular operator deployment scenarios where there are multiple Element Managers (one per vendor), the label is added in front of the "em" label: + +vendor.em.oam.mnc.mcc.3gppnetwork.org + +An example of a EM FQDN is: + +MCC = 123; + +MNC = 45; + +ViD = abcd; + +which gives the EM FQDN: "em.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.em.mnc045.mcc123.3gppnetwork.org". + +--- + +## 24 Numbering, addressing and identification for Proximity-based Services (ProSe) + +### 24.1 Introduction + +This clause describes the format of the parameters used for ProSe. For further information on the use of the parameters see 3GPP TS 23.303 [103]. + +### 24.2 ProSe Application ID + +#### 24.2.1 General + +The ProSe Application ID is composed of two parts as follows: + +- The ProSe Application ID Name, which is described in its entirety by a data structure characterized by different levels e.g, broad-level business category (Level 0) / business sub-category (Level 1) / business name (Level 2) / shop ID (Level 3). +- The PLMN ID, which corresponds to the PLMN that assigned the ProSe Application ID Name. + +The PLMN ID is placed before the ProSe Application ID Name as shown in Figure 24.2.1. The PLMN ID and the ProSe Application ID Name shall be separated by a dot. + +![Diagram showing the structure of a ProSe Application ID. It consists of a sequence of boxes: 'mcc', 'mnc', 'ProSeApp', 'Label1', 'Label2', '...', and 'Labeln'. Below the boxes, three double-headed arrows indicate the scope of different parts of the ID: the first arrow covers 'mcc' and 'mnc' and is labeled 'PLMN ID'; the second arrow covers 'ProSeApp' through 'Labeln' and is labeled 'ProSe Application ID Name'; the third, longest arrow covers the entire sequence from 'mcc' to 'Labeln' and is labeled 'ProSe Application ID'.](56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg) + +Diagram showing the structure of a ProSe Application ID. It consists of a sequence of boxes: 'mcc', 'mnc', 'ProSeApp', 'Label1', 'Label2', '...', and 'Labeln'. Below the boxes, three double-headed arrows indicate the scope of different parts of the ID: the first arrow covers 'mcc' and 'mnc' and is labeled 'PLMN ID'; the second arrow covers 'ProSeApp' through 'Labeln' and is labeled 'ProSe Application ID Name'; the third, longest arrow covers the entire sequence from 'mcc' to 'Labeln' and is labeled 'ProSe Application ID'. + +Figure 24.2.1-1: Structure of ProSe Application ID + +## 24.2.2 Format of ProSe Application ID Name in ProSe Application ID + +The ProSe Application ID Name is composed of a string of labels. These labels represent hierarchical levels and shall be separated by dots (e.g. "Label1.Label2.Label3"). The ProSe Application ID Name shall contain at least one label. The first label on the left shall be "ProSeApp". + +NOTE: The hierarchical structure and the content of the ProSe Application ID Name are outside the scope of 3GPP. + +Any label in the ProSe Application ID Name except the first label on the left ("ProSeApp") can be wild carded. A wild card label is represented as "\*", + +EXAMPLE: A ProSe Application ID Name used to discover nearby Italian restaurants could be "ProSeApp.Food.Restaurants.Italian". + +## 24.2.3 Format of PLMN ID in ProSe Application ID + +The PLMN ID shall uniquely identify the PLMN of the ProSe Function that has assigned the ProSe Application ID. The PLMN ID is composed of two labels which shall be separated by a dot as follows: + +"mcc.mnc" + +where: + +"mcc" and "mnc" serve as invariable identifiers for the following digits. + + contains the MCC (Mobile Country Code) of the ProSe Function that has assigned the ProSe Application ID. + + contains the MNC (Mobile Network Code) of the ProSe Function that has assigned the ProSe Application ID. + +In order to guarantee inter-PLMN operability, the and the shall be represented by 3 digits. If there are only 2 significant digits in the MNC, one "0" digit is inserted at the left side of the MNC to form the in the "mnc" label. + +EXAMPLE: The PLMN ID for MCC 345 and MNC 12 will be "mcc345.mnc012". + +## 24.2.4 Usage of wild cards in place of PLMN ID in ProSe Application ID + +If the scope of the ProSe Application ID is country-specific, the PLMN ID part in the ProSe Application ID shall be replaced by "mcc.mnc\*" with set to the MCC of the corresponding country. + +NOTE: Handling of the case when a country has been allocated more than one MCC value is outside the scope of 3GPP. + +If the scope of the ProSe Application ID is global, the PLMN ID part in the ProSe Application ID shall be replaced by "mcc\*.mnc\*." + +EXAMPLE: For a ProSe Application ID specific to a country with MCC 345, the PLMN ID part will be replaced by "mcc345.mnc\*." + +## 24.2.5 Informative examples of ProSe Application ID + +Examples of ProSe Application IDs following the format defined in the previous clauses are provided for information below. + +EXAMPLE 1: "mcc345.mnc012.ProSeApp.Food.Restaurants.Italian" + +EXAMPLE 2: "mcc300.mnc165.ProSeApp.Shops.Sports.Surfing" + +EXAMPLE 3: "mcc300.mnc165.ProSeApp.\*.Sports.Surfing" + +EXAMPLE 4: "mcc208.mnc\*.ProSeApp.Shops.Food.Wine" + +EXAMPLE 5: "mcc\*.mnc\*.ProSeApp.Food.Restaurants.Coffee" + +## 24.3 ProSe Application Code + +### 24.3.1 General + +The ProSe Application Code as described in 3GPP TS 23.303 [103] is composed of the following two parts: + +- The PLMN ID of the ProSe Function that assigned the ProSe Application Code, i.e. Mobile Country Code (MCC) and Mobile Network Code (MNC). +- A temporary identity that corresponds to the ProSe Application ID Name. The temporary identity is allocated by the ProSe Function and it may contain a metadata index. The internal structure of the temporary identity is not specified in 3GPP. + +The ProSe Application Code shall have a fixed length of 184 bits. + +### 24.3.2 Format of PLMN ID in ProSe Application Code + +The PLMN ID in the ProSe Application Code is composed as shown in Figure 24.3.2-1: + +![Diagram showing the structure of PLMN ID in ProSe Application Code. It consists of four fields: Scope (2 bits), Spare (1 bit), E (1 bit), MCC (10 bits), and MNC (10 bits). The first three fields are grouped together, and the last two are grouped together by dashed lines.](34f9874474c0f8f03423fce29f2c2ded_img.jpg) + +| | | | | | +|--------|-------|-------|---------|---------| +| Scope | Spare | E | MCC | MNC | +| 2 bits | 1 bit | 1 bit | 10 bits | 10 bits | + +Diagram showing the structure of PLMN ID in ProSe Application Code. It consists of four fields: Scope (2 bits), Spare (1 bit), E (1 bit), MCC (10 bits), and MNC (10 bits). The first three fields are grouped together, and the last two are grouped together by dashed lines. + +**Figure 24.3.2-1: Structure of PLMN ID in ProSe Application Code** + +The PLMN-ID is composed of four parts: + +- Scope indicates whether the MNC, or both the MCC and the MNC, or neither are wild carded in the ProSe Application ID associated with the ProSe Application Code, with the following mapping: + +00 global scope. + +01 reserved. + +10 country-specific scope. + +11 PLMN-specific scope. + +- Spare bit that shall be set to 0 and shall be ignored if set to 1. + +- E bit indicates whether the MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code are included in the PLMN ID in ProSe Application Code, with the following mapping: + - 0 Neither MCC nor MNC is included. + - 1 MCC and MNC included. +- When present, the MCC and the MNC shall each have a fixed length of 10 bits and shall be coded as the binary representation of their decimal value. + +In this release, the MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code shall always be included in the PLMN ID in ProSe Application Code. The E bit shall always be set to 1. + +### 24.3.3 Format of temporary identity in ProSe Application Code + +The temporary identity in the ProSe Application Code is a bit string whose value is allocated by the ProSe Function. The length of the temporary identity in the ProSe Application Code is equal to: + +- 180 bits when the E bit of the PLMN ID in the ProSe Application Code is set to 0. +- 160 bits when the E bit of the PLMN ID in the ProSe Application Code is set to 1. + +The temporary identity in the ProSe Application Code shall contain a metadata index to reflect the current metadata version if dynamic metadata is used when allocating the ProSe Application Code. The content, position and length of metadata index is operator specific. + +In this release, the MCC and the MNC of the ProSe Function that has assigned the ProSe Application Code are always included in the PLMN ID in ProSe Application Code. The length of the temporary identity in the ProSe Application Code shall always be equal to 160 bits. + +## 24.3A ProSe Application Code Prefix + +The ProSe Application Code Prefix as described in 3GPP TS 23.303 [103] is to be used with a ProSe Application Code Suffix. The ProSe Application Code Prefix has the same composition and format as the ProSe Application Code, with the following exceptions: + +- The temporary identity part of the ProSe Application Code Prefix is of variable length. The length of the temporary identity part shall be incremented in multiple of 8, with a minimum size of 8 bits and a maximum size of 152 bits. +- The sum of the length of the ProSe Application Code Prefix and the length of the ProSe Application Code Suffix shall be 184 bits. + +## 24.3B ProSe Application Code Suffix + +The ProSe Application Code Suffix as described in 3GPP TS 23.303 [103] is an identifier to be appended to a ProSe Application Code Prefix. The ProSe Application Code Suffix is of variable length. The length of the ProSe Application Code Suffix shall be incremented in multiple of 8, with a minimum size of 8 bits and a maximum size of 152 bits. The sum of the length of the ProSe Application Code Prefix and the length of the ProSe Application Code Suffix shall be 184 bits. + +## 24.4 EPC ProSe User ID + +### 24.4.1 General + +The EPC ProSe User ID as described in 3GPP TS 23.303 [103] identifies the UE registered for EPC-level ProSe Discovery in the context of the ProSe Function. + +## 24.4.2 Format of EPC ProSe User ID + +The EPC ProSe User ID is a bit string whose value is allocated by the ProSe Function. The length of the EPC ProSe User ID is equal to 32 bits. + +## 24.5 Home PLMN ProSe Function Address + +The Home PLMN ProSe Function address is in the form of a Fully Qualified Domain Name as defined in IETF RFC 1035 [19] and IETF RFC 1123 [20]. This address consists of six labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +For 3GPP systems, if not pre-configured on the UE or provisioned by the network, the UE shall derive the Home PLMN ProSe Function address from the IMSI as described in the following steps: + +1. Take the first 5 or 6 digits, depending on whether a 2 or 3-digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2-digit MNC then a zero shall be added at the beginning. +2. Use the MCC and MNC derived in step 1 to create the "mnc.mcc.pub.3gppnetwork.org" domain name. +3. Add the label "prose-function." to the beginning of the domain. + +An example of a Home PLMN ProSe Function address is: + +IMSI in use: 234150999999999; + +where: + +- MCC = 234; +- MNC = 15; and +- MSIN = 0999999999, + +which gives the following Home PLMN ProSe Function address: + +"prose-function.mnc015.mcc234.pub.3gppnetwork.org". + +## 24.6 ProSe Restricted Code + +The ProSe Restricted Code as described in 3GPP TS 23.303 [103] is a single 64-bit identifier that corresponds to one or more Restricted ProSe Application User ID(s) (as defined in 3GPP TS 23.303 [103]). The exact content of the identifier is not specified in 3GPP. + +## 24.7 ProSe Restricted Code Prefix + +The ProSe Restricted Code Prefix as described in 3GPP TS 23.303 [103] is a ProSe Restricted Code which to be used with a ProSe Restricted Code Suffix. It shall have the same size and format as the ProSe Restricted Code. + +## 24.8 ProSe Restricted Code Suffix + +The ProSe Restricted Code Suffix as described in 3GPP TS 23.303 [103] is an identifier to be appended to a ProSe Restricted Code Prefix. Depending on the application configuration, the bit length of a ProSe Restricted Code Suffix varies from 8 to 120, incremented by multiples of 8. + +## 24.9 ProSe Query Code + +The ProSe Query Code as described in 3GPP TS 23.303 [103] is a ProSe Restricted Code allocated by the ProSe Function to the Discoverer UE for restricted ProSe direct discovery model B. The format of the ProSe Query Code is the same as that of the ProSe Restricted Code defined in clause 24.6. + +## 24.10 ProSe Response Code + +The ProSe Response Code as described in 3GPP TS 23.303 [103] is a ProSe Restricted Code allocated by the ProSe Function to the Discoveree UE for restricted ProSe direct discovery model B. The format of the ProSe Response Code is the same as that of the ProSe Restricted Code defined in clause 24.6. + +## 24.11 ProSe Discovery UE ID + +### 24.11.1 General + +The ProSe Discovery UE ID as described in 3GPP TS 23.303 [103] identifies the UE participating in restricted ProSe direct discovery in the context of the ProSe Function. + +It is composed of two parts as follows: + +- The PLMN ID of the ProSe Function that assigned the ProSe Discovery UE ID, i.e. Mobile Country Code (MCC) and Mobile Network Code (MNC). +- A temporary identifier allocated by the ProSe Function. The content of the temporary identifier is not specified in 3GPP. + +### 24.11.2 Format of ProSe Discovery UE ID + +The ProSe Discovery UE ID is a bit string whose value is allocated by the ProSe Function. The length of the ProSe Discovery UE ID is equal to 64 bits and the format is described as shown in Figure 24.11.2-1. + +![Diagram showing the structure of ProSe Discovery UE ID, consisting of a 24-bit PLMN ID and a 40-bit Temporary ID.](3c04a06e1bebf2ba5a6af7a74285bfc3_img.jpg) + +The diagram illustrates the structure of the ProSe Discovery UE ID. It is a horizontal rectangle divided into two main sections. The left section is labeled 'PLMN ID' and has a double-headed arrow below it labeled '24 bits'. The right section is labeled 'Temporary ID' and has a double-headed arrow below it labeled '40 bits'. The two sections are separated by a vertical line. + +Diagram showing the structure of ProSe Discovery UE ID, consisting of a 24-bit PLMN ID and a 40-bit Temporary ID. + +Figure 24.11.2-1: Structure of ProSe Discovery UE ID + +## 24.12 ProSe UE ID + +The ProSe UE ID as described in 3GPP TS 23.303 [103] identifies the link layer address used for ProSe direct communication by a ProSe-enabled Public Safety UE. + +The format of ProSe UE ID is a bit string whose length is equal to 24 bits. + +## 24.13 ProSe Relay UE ID + +The ProSe Relay UE ID as described in 3GPP TS 23.303 [103] identifies the link layer address used for ProSe direct communication by a ProSe UE-to-network relay UE. + +The format of ProSe Relay UE ID is a bit string whose length is equal to 24 bits. + +## 24.14 User Info ID + +The User Info ID as described in 3GPP TS 23.303 [103] is used to identify the user information to be discovered for public safety use case. The value of User Info ID is allocated either by the operator or 3rd-party public safety provider application server. + +The format of the User Info ID is a 48-bit bit-string. + +## 24.15 Relay Service Code + +The Relay Service Code as described in 3GPP TS 23.303 [103] identifies a connectivity service the ProSe UE-to-network relay provides. + +The format of the Relay Service Code is a 24-bit bit-string. + +## 24.16 Discovery Group ID + +The Discovery Group ID as described in 3GPP TS 23.303 [103] identifies a group of Public Safety users that are affiliated for Group Member Discovery. + +The format of the Discovery Group ID is a 24-bit bit-string. + +## 24.17 Service ID + +The Service ID is specified in 3GPP TS 23.303 [103], Annex C and specifies the 3GPP service category for ProSe. The Service ID shall be the string "3GPP ProSe Service Category". + +--- + +# 25 Identification of Online Charging System + +## 25.1 Introduction + +This clause describes the format of the home network domain name of the Online Charging System (OCS), needed to access the Online Charging System. For further information on the use of this home network domain name, see 3GPP TS 29.212 [106]. For more information on the ".3gppnetwork.org" domain name and its applicability, see Annex D of the present document. + +## 25.2 Home network domain name + +The home network domain name of the OCS shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain of the OCS consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. + +If the home network domain of the OCS is not known (e.g. through an available static address or through its reception from another node), it shall be: + +- in the form of "ocs.mnc.mcc.3gppnetwork.org", where "" and "" fields correspond to the MNC and MCC of the operator's PLMN to which the OCS belongs. Both the "" and "" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning; and +- derived from the subscriber's IMSI, as described in the following steps: + 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102 [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; + +2. use the MCC and MNC derived in step 1 to create the "mnc.mcc.3gppnetwork.org" domain name; +3. add the label "ocs" to the beginning of the domain name. + +An example of a home network domain name is: + +IMSI in use: 234150999999999; + +Where: + +MCC = 234; + +MNC = 15; + +MSIN = 099999999; + +Which gives the home network domain name: ocs.mnc015.mcc234.3gppnetwork.org. + +NOTE: It is implementation dependent to determine that the length of the MNC is 2 or 3 digits. + +--- + +## 26 Numbering, addressing and identification for Mission Critical Services + +### 26.1 Introduction + +This clause describes the format of the parameters used for Mission Critical Services. + +For further information on the use of the parameters see 3GPP TS 23.280 [114]. + +### 26.2 Domain name for MC services confidentiality protection of MC services identities + +A Domain Name for MC Services confidentiality protection used in a host part of a SIP URI indicates that the user part of the SIP URI contains a confidentiality protected MC Services identity. This Domain Name shall be the string "mc1-encrypted.3gppnetwork.org". + +Protected MCPTT identities are constructed according to 3GPP TS 24.379 [111]. + +Protected MCData identities are constructed according to 3GPP TS 24.282 [116]. + +Protected MCVideo identities are constructed according to 3GPP TS 24.281 [115]. + +--- + +## 27 Numbering, addressing and identification for V2X + +### 27.1 Introduction + +This clause describes the format of the parameters used for V2X. For further information on the use of the parameters see 3GPP TS 23.285 [117]. + +## 27.2 V2X Control Function FQDN + +### 27.2.1 General + +In order to retrieve V2X communication parameters, the UE needs to connect to the V2X Control Function. The address of the V2X control Function can be provisioned to the UE, or the UE can be pre-configured with the FQDN of the V2X Control Function. If the address of the V2X Control Function is not provisioned, and the UE is not pre-configured with the FQDN of the V2X Control Function FQDN, the UE self-constructs the V2X Control Function FQDN as per the format specified in clause 27.2.2. + +### 27.2.2 Format of V2X Control Function FQDN + +The V2X Control Function Fully Qualified Domain Name (V2X Control Function FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the V2X Control Function is located. The V2X Control Function FQDN is composed of six labels. The last two labels shall be "3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "v2xcontrollfunction.epc". The V2X Control Function FQDN shall be constructed as follows: + +"v2xcontrollfunction.epc.mnc.mcc.3gppnetwork.org" + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "v2xcontrollfunction.epc.mnc.mcc.3gppnetwork.org" format of the V2X Control Function FQDN shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the V2X Control Function FQDN. + +As an example, the V2X Control Function FQDN for MCC 345 and MNC 12 is coded in the DNS as: + +"v2xcontrollfunction.epc.mnc012.mcc345.3gppnetwork.org". + +--- + +## 28 Numbering, addressing and identification for 5G System (5GS) + +### 28.1 Introduction + +This clause describes the format of the parameters, identifiers and information used for the 5G system. For further information on these, see 3GPP TS 23.501 [119], 3GPP TS 23.502 [120] and 3GPP TS 23.503 [121]. + +### 28.2 Home Network Domain + +The Home Network Domain for 5GC shall be in the format specified in IETF RFC 1035 [19] and IETF RFC 1123 [20] and shall be structured as: + +"5gc.mnc.mcc.3gppnetwork.org", + +where "" and "" fields correspond to the MNC and MCC of the operator's PLMN. Both the "" and "" fields are 3 digits long. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the NF service endpoint format for inter PLMN routing. + +As an example, the Home Network Domain for MCC 345 and MNC 12 is coded as: + +"5gc.mnc012.mcc345.3gppnetwork.org". + +The Home Network Domain for a Stand-alone Non-Public Network (SNPN) shall be in the format specified in IETF RFC 1035 [19] and IETF RFC 1123 [20] and, if not pre-configured in the NF, shall be structured as: + +"5gc.nid.mnc.mcc.3gppnetwork.org", + +where and shall be encoded as specified above, and the NID shall be encoded as hexadecimal digits as specified in clause 12.7. + +As an example, the Home Network Domain for MCC 345, MNC 12 and NID 000007ed9d5 (hexadecimal: assignment mode = 0, PEN = 00007ed9, NID code = d5) is coded as: + +"5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org". + +NOTE: For interworking with an SNPN (e.g. discovery of AMFs from an SNPN by a shared NG RAN), the above sub-domain can be used when the MCC, MNC and NID uniquely identifies the SNPN. For signalling within an SNPN, the above sub-domain can be used regardless of whether the MCC, MNC and NID uniquely identifies the SNPN or not. + +## 28.3 Identifiers for Domain Name System procedures + +### 28.3.1 Introduction + +This clause describes Domain Name System (DNS) related identifiers used by the procedures specified in 3GPP TS 29.303 [73]. + +### 28.3.2 Fully Qualified Domain Names (FQDNs) + +#### 28.3.2.1 General + +See clause 19.4.2.1. + +#### 28.3.2.2 N3IWF FQDN + +##### 28.3.2.2.1 General + +The N3IWF Fully Qualified Domain Name (N3IWF FQDN) shall be constructed using one of the following formats, as specified in clause 6.3.6 of 3GPP TS 23.501 [119]: + +- Operator Identifier based N3IWF FQDN; +- Tracking Area Identity based N3IWF FQDN; +- the N3IWF FQDN configured in the UE by the HPLMN. +- SNPN Identifier based N3IWF FQDN. + +NOTE 1: If the N3IWF FQDN is configured in the UE by HPLMN, it can have a different format than those specified in the following clauses. The actual format is out of 3GPP scope. + +The Visited Country FQDN for N3IWF is used by a roaming UE to determine whether the visited country mandates the selection of an N3IWF in this country. The Visited Country FQDN for N3IWF shall be constructed as specified in clause 28.3.2.2.4. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 28.3.2.2.5.1. + +The Visited Country FQDN for SNPN N3IWF is used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for the SNPN identified by the SNPN Identifier provided by the UE. The Visited Country FQDN for SNPN N3IWF shall be constructed as specified in clause 28.3.2.2.6. The Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements shall be constructed as specified in clause 28.3.2.2.7.2. + +The Visited Country FQDN for N3IWF supporting Onboarding is used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for onboarding services. The Visited Country FQDN with N3IWF supporting Onboarding shall be constructed as specified in clause 28.3.2.2.4.3. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 28.3.2.2.5.3. + +The Visited Country FQDN for SNPN N3IWF supporting Onboarding is used by a UE in the visited country to determine whether the visited country mandates the selection of an SNPN N3IWF in this country for onboarding services. The Visited Country FQDN with SNPN N3IWF supporting Onboarding shall be constructed as specified in clause 28.3.2.2.6.2. The Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements shall be constructed as specified in clause 28.3.2.2.7.2 + +NOTE 2: The DNS can be configured to return no records for the visited country regardless of the SNPN ID provided by the UE. This addresses the scenario that the visited country in general does not mandate selection of a local N3IWF. + +#### 28.3.2.2.2 Operator Identifier based N3IWF FQDN + +The N3IWF Fully Qualified Domain Name (N3IWF FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the N3IWF is located. The N3IWF FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "n3iwf.5gc". The N3IWF FQDN shall be constructed as follows: + +"n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" + +In the roaming case, the UE can utilise the services of the VPLMN or the HPLMN. In this case, the Operator Identifier based N3IWF FQDN shall be constructed as described above, but using the MNC and MCC of the VPLMN or the HPLMN. + +In order to guarantee inter-PLMN DNS translation, the and coding used in the "n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" format of the Operator Identifier based N3IWF FQDN shall be: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the N3IWF FQDN. + +As an example, the Operator Identifier based N3IWF FQDN for MCC 345 and MNC 12 is coded in the DNS as: + +"n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org". + +#### 28.3.2.2.3 Tracking Area Identity based N3IWF FQDN + +The Tracking Area Identity based N3IWF FQDN is used to support location based N3IWF selection within a PLMN. + +There are two N3IWF FQDNs defined one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. + +- 1) The Tracking Area Identity based N3IWF FQDN using a 2 octet TAC shall be constructed respectively as: + +"tac-lb.tac-hb.tac.n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" + +where + +- the and shall identify the PLMN where the N3IWF is located and shall be encoded as + - = 3 digits + - = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the N3IWF FQDN. + +- the , together with the and shall identify the Tracking Area Identity the UE is located in. + +The TAC is a 16-bit integer. The is the hexadecimal string of the most significant byte in the TAC and the is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding; + +As examples, + +- the Tracking Area Identity based N3IWF FQDN for the TAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: + +"tac-lb21.tac-hb0b.tac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" + +- 2) The 5GS Tracking Area Identity based N3IWF FQDN using a 3 octet TAC shall be constructed respectively as: + +"tac-lb.tac-mb.tac-hb.5gstac.n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" + +where + +- the and shall identify the PLMN where the N3IWF is located and shall be encoded as + - = 3 digits + - = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the N3IWF FQDN. + +- the , together with the and shall identify the 5GSTRacking Area Identity the UE is located in. + +The 5GS TAC is a 24-bit integer. The is the hexadecimal string of the most significant byte in the TAC and the is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in , or , "0" digit(s) shall be inserted at the left side to fill the 2 digit coding; + +As examples, + +- the 5GS Tracking Area Identity based N3IWF FQDN for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: + +"tac-lb21.tac-mb1a.tac-hb0b.5gstac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" + +## 28.3.2.2.4 Visited Country FQDN for N3IWF + +### 28.3.2.2.4.1 General + +The Visited Country FQDN for N3IWF, used by a roaming UE to determine whether the visited country mandates the selection of an N3IWF in this country, shall be constructed as described below. + +The Visited Country FQDN shall contain a MCC that uniquely identifies the country in which the UE is located. + +The Visited Country FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The fourth label shall be "visited-country". The third label shall uniquely identify the MCC of the visited country. The first and second labels shall be "n3iwf.5gc". The resulting Visited Country FQDN of N3IWF shall be constructed as follows: + +"n3iwf.5gc.mcc.visited-country.pub.3gppnetwork.org" + +The coding used in this FQDN shall be: + +- = 3 digits + +As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as: + +"n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org". + +#### 28.3.2.2.4.2 Visited Country Emergency N3IWF FQDN + +The Visited Country Emergency N3IWF FQDN, used by a roaming UE shall be constructed as specified for the Visited Country FQDN for N3IWF in clause 28.3.2.2.4.1, with the addition of the label "sos" before the labels "n3iwf.5gc". + +The resulting Visited Country Emergency N3IWF FQDN shall be constructed as follows: + +"sos.n3iwf.5gc.mcc.visited-country.pub.3gppnetwork.org" + +As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as: + +"sos.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org". + +#### 28.3.2.2.4.3 Visited Country FQDN for N3IWF supporting Onboarding + +UE onboarding for access to SNPN services is specified in clause 5.30.2.12 of 3GPP TS 23.501 [119]. Visited Country FQDN for N3IWF supporting Onboarding encoding is constructed by adding a label "onboarding" to Visited Country FQDN for N3IWF FQDN (see clause 28.3.2.2.4.1), indicating that the N3IWF identified by the N3IWF identifier in the DNS response shall supports onboarding. + +Visited Country FQDN for N3IWF supporting Onboarding is constructed as follows: + +"onboarding.n3iwf.5gc.mcc.visited-country. pub.3gppnetwork.org" + +As an example, the Visited Country FQDN for N3IWF supporting Onboarding for MCC 345, is coded in the DNS as: + +"onboarding.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org". + +#### 28.3.2.2.5 Replacement field used in DNS-based Discovery of regulatory requirements + +##### 28.3.2.2.5.1 General + +If the visited country mandates the selection of an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country which may be used for N3IWF selection. + +The replacement field shall take the form of an Operator Identifier based N3IWF FQDN as specified in clause 28.3.2.2.2. + +For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN. + +As an example, the NAPTR records associated to the Visited Country FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: + +``` +n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement +IN NAPTR 100 999 "" "" n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org +``` + +##### 28.3.2.2.5.2 Replacement field used in DNS-based Discovery of regulatory requirements for emergency services via N3IWF + +The NAPTR record(s) associated to the Visited Country Emergency N3IWF FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country supporting emergency services in non-3GPP access via N3IWF. + +The replacement field shall take the form of an operator identifier based N3IWF FQDN as specified clause 28.3.2.2.2, with the addition of the label "sos" before the labels "n3iwf.5gc". + +As an example, the NAPTR records associated to the Visited Country Emergency N3IWF FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: + +``` +sos.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement +IN NAPTR 100 999 "" "" sos.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" sos.n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" sos.n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org +``` + +#### 28.3.2.2.5.3 Replacement field used in DNS-based Discovery of N3IWF supporting Onboarding + +If the visited country mandates the selection of an N3IWF supporting onboarding in this country, the NAPTR record(s) associated to the Visited Country FQDN for N3IWF supporting Onboarding shall be provisioned with the replacement field containing the Operator Identifier based Onboarding FQDN for N3IWF located in the visited country. + +When UE sends the DNS query to the DNS server containing the Visited Country Onboarding FQDN for N3IWF (see clause 28.3.2.2.4.3), the DNS response should contain the Operator Identifier based Onboarding FQDN for N3IWF containing the identity of the PLMN(s) in the visited country which may be used for N3IWF selection in the visited country supporting Untrusted non-3GPP access for UE Onboarding via N3IWF. + +If the UE has selected an PLMN for onboarding, the UE sends DNS query to the DNS server containing the Operator Identifier based Onboarding FQDN for N3IWF to query the identifier of the N3IWF supporting Onboarding, the DNS response should contain the identifier of the N3IWF supporting the onboarding in the PLMN identified by the PLMN ID. + +The replacement field shall take the form of Operator Identifier based Onboarding FQDN for N3IWF as below: + +"onboarding.n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" + +For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN for N3IWF supporting Onboarding. + +As an example, the NAPTR records associated to the Visited Country FQDN for N3IWF supporting Onboarding for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: + +``` +onboarding.n3iwf.5gc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement +IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.mnc013.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" onboarding.n3iwf.5gc.mnc014.mcc345.pub.3gppnetwork.org +``` + +#### 28.3.2.2.6 FQDN for SNPN N3IWF + +##### 28.3.2.2.6.1 SNPN Identifier based N3IWF FQDN and Visited Country FQDN for SNPN N3IWF + +The SNPN Identifier based N3IWF FQDN is used by a UE to access SNPN service in its subscribed SNPN via PLMN or directly via an untrusted non-3GPP access, as specified in clause 6.3.6.2a of 3GPP TS 23.501 [119]. The N3IWF FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third label and fourth labels together shall identify the SNPN (the country where it is located along with the SNPN ID). The first two labels shall be "n3iwf.5gc". Hence, the SNPN Identifier based N3IWF FQDN shall be constructed as follows: + +"n3iwf.5gc.snpid.mcc.pub.3gppnetwork.org". + +The coding used in this FQDN shall be: + +- = 3 digits + +The coding used in this FQDN shall be: + +- = PLMN ID || NID + +where, PLMN ID = MCC || MNC + +NOTE 1: The MCC used in the SNPNID is not necessarily the same (e.g. it can be 999 reserved for internal use) as the one used in coding the . + +NOTE 2: Locally assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same locally assigned NID. + +As an example, SNPN Identifier based N3IWF FQDN for MCC 098, SNPN MCC 999, MNC 305, and NID 456789ABCDE is coded in the DNS as: + +"n3iwf.5gc.snpid999305456789ABCDE.mcc098.pub.3gppnetwork.org" + +The Visited Country FQDN for SNPN N3IWF, used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for the SNPN identified by the SNPN Identifier provided by the UE, shall be constructed as described below. + +The Visited Country FQDN for SNPN N3IWF shall contain a MCC that uniquely identifies the country in which the UE is located, and the SNPN Identifier. + +The Visited Country FQDN for SNPN N3IWF is composed of eight labels. The last three labels shall be "pub.3gppnetwork.org". The fifth label shall be "visited-country". The fourth label shall uniquely identify the MCC of the visited country. The third label shall be the SNPN Identifier as specified in clause 12.7. The first and second labels shall be "n3iwf.5gc". The Visited Country FQDN for SNPN N3IWF shall be constructed as follows: + +"n3iwf.5gc.snpid.mcc.visited-country.pub.3gppnetwork.org" + +The coding used in this FQDN shall be: + +- = 3 digits + +The coding used in this FQDN shall be: + +- = MCC || MNC || NID + +NOTE 1: The MCC used in the SNPNID is not necessarily the same (e.g. it can be 999 reserved for internal use) as the one used in coding the . + +NOTE 2: Locally assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same locally assigned NID. + +As an example, the Visited Country FQDN for SNPN N3IWF for MCC 345, SNPN MCC 999, MNC 123, and NID 456789ABCDE is coded in the DNS as: + +"n3iwf.5gc.snpid999123456789ABCDE.mcc345.visited-country.pub.3gppnetwork.org" + +NOTE 3: The identity (i.e. the corresponding DNS record) of an SNPN's N3IWF in the visited country can be any FQDN and is not required to include the SNPN identifier. + +#### 28.3.2.2.6.2 Visited Country FQDN for SNPN N3IWF supporting Onboarding + +SNPN N3IWF supporting Onboarding is specified in clause 5.30.2.12 of 3GPP TS 23.501 [119]. If an SNPN for onboarding has been selected, Visited Country FQDN for SNPN N3IWF indicates that the SNPN identified by the SNPN in the DNS response shall support onboarding. + +Visited Country FQDN for SNPN N3IWF supporting Onboarding is composed of eight labels. The last four labels shall be "visited-country.pub.3gppnetwork.org". The fourth label shall uniquely identify the MCC of the visited country. The second and third labels shall be "n3iwf.snpn-5gc". The first label shall be "onboarding". + +The resultant Visited Country FQDN for SNPN N3IWF supporting Onboarding shall be constructed as follows: + +"onboarding.n3iwf.snpn-5gc.mcc.visited-country.pub.3gppnetwork.org" + +As an example, the Visited Country FQDN for SNPN N3IWF, which also supports Onboarding for MCC 345 is coded in the DNS as: + +"onboarding.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org". + +### 28.3.2.2.6.3 Visited Country Emergency SNPN FQDN + +The Visited Country Emergency SNPN FQDN, used by a UE to determine whether the visited country mandates the selection of an SNPN N3IWF for emergency service in this country, shall be constructed as described below. + +The Visited Country Emergency SNPN FQDN shall contain a MCC that uniquely identifies the country in which the UE is located. + +The Visited Country Emergency SNPN FQDN is composed of eight labels. The last three labels shall be "pub.3gppnetwork.org". The fifth label shall be "visited-country". The fourth label shall uniquely identify the MCC of the visited country. The second and third labels shall be "n3iwf.snpn-5gc". The first label shall be "sos". The resulting Visited Country Emergency SNPN FQDN shall be constructed as follows: + +"sos.n3iwf.snpn-5gc.mcc.visited-country.pub.3gppnetwork.org". + +As an example, the Visited Country Emergency SNPN FQDN for MCC 345 is coded in the DNS as: + +"sos.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org". + +### 28.3.2.2.6.4 Replacement field used in DNS-based Discovery of regulatory requirements for emergency services in SNPN + +If the visited country mandates the selection of an SNPN N3IWF for emergency services in this country, the NAPTR record(s) associated to the Visited Country Emergency SNPN FQDN shall be provisioned with the replacement field containing the identity of the SNPN(s) in the visited country which may be used for N3IWF selection. + +The replacement field shall take the form of an SNPN Identifier based N3IWF FQDN as specified in clause 28.3.2.2.6.1 with the addition of the label "sos" before the labels "n3iwf.5gc" as "sos.n3iwf.5gc.snpid.mcc.pub.3gppnetwork.org". + +As an example, the NAPTR records associated to the Visited Country Emergency SNPN FQDN for MCC 345, and for a) SNPN MCC 999, MNC 012, and NID 345678ABCDE; b) SNPN MCC 345, MNC 013, and NID 345678BCDEF; and c) SNPN MCC 999, MNC 014, and NID 234567CDEFG, are provisioned in the DNS as: + +``` +sos.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement +IN NAPTR 100 999 "" "" sos.n3iwf.5gc.snpid999012345678ABCDE.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" sos.n3iwf.5gc.snpid345013345678BCDEF.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" sos.n3iwf.5gc.snpid999014234567CDEFG.mcc345.pub.3gppnetwork.org +``` + +NOTE: The SNPN ID in the NAPTR records do not contain the NID using self-assignment model since a DNS cannot be properly configured for multiple SNPNs using the same self-assigned NID. + +### 28.3.2.2.7 Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements + +#### 28.3.2.2.7.1 General + +If the visited country mandates the selection of an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN shall be provisioned with the replacement field containing FQDNs of SNPN N3IWFs located in the visited country. + +NOTE: If the visited country mandates the selection of the N3IWF in this country and the SNPN does not have an N3IWF in this country, the NAPTR record(s) associated to the Visited Country FQDN are provisioned with the replacement field containing an FQDN that cannot be resolved to an IP address. + +#### 28.3.2.2.7.2 Replacement field used in DNS-based Discovery of SNPN N3IWF supporting Onboarding + +If the visited country mandates the selection of an SNPN N3IWF supporting onboarding in this country, the NAPTR record(s) associated to the Visited Country FQDN for SNPN N3IWF supporting Onboarding shall be provisioned with the replacement field containing Operator Identifier based Onboarding FQDN for SNPN N3IWF located in the visited country. + +When UE sends the DNS query to the DNS server containing the Visited Country Onboarding FQDN for SNPN N3IWF (see clause 28.3.2.2.6.2), the DNS response should contain the Operator Identifier based Onboarding FQDN for SNPN N3IWF with the identity of an SNPN in the visited country supporting Untrusted non-3GPP access for UE Onboarding via N3IWF. + +If the UE has selected an SNPN for onboarding, the UE sends DNS query to the DNS server containing the Operator Identifier based Onboarding FQDN for SNPN N3IWF to query the identifier of the N3IWF supporting Onboarding, the DNS response should contain the identifier of the N3IWF supporting the onboarding in the SNPN identified by the SNPN ID. + +The replacement field shall take the form of Operator Identifier based Onboarding FQDN for SNPN N3IWF as below: + +"onboarding.n3iwf.5gc.snpid.mcc.pub.3gppnetwork.org" + +As an example, the NAPTR records associated to the Visited Country Emergency SNPN FQDN for MCC 345, and for a) SNPN MCC 999, MNC 123, and NID 456789ABCDE; b) SNPN MCC 999, MNC 013, and NID 345678BCDEF, are provisioned in the DNS as: + +``` +onboarding.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org +; IN NAPTR order pref. flag service regexp replacement +IN NAPTR 100 999 "" "" +onboarding.n3iwf.5gc.snpid999123456789ABCDE.mcc345.pub.3gppnetwork.org +IN NAPTR 100 999 "" "" +onboarding.n3iwf.5gc.snpid999013345678BCDEF.mcc345.pub.3gppnetwork.org +``` + +#### 28.3.2.2.8 Prefixed Operator Identifier based N3IWF FQDN + +The Prefixed Operator Identifier based N3IWF FQDN, used by a UE that is configured with Slice-specific N3IWF prefix configuration, shall be constructed as specified for the Operator Identifier based N3IWF FQDN in clause 28.3.2.2.2, with the addition of before the labels "n3iwf.5gc". The is provided in the Slice-specific N3IWF prefix configuration for the selected PLMN that contains S-NSSAIs that match all (or most, in case there is no full match) of the S-NSSAIs that the UE is going to include in the Requested NSSAI in the subsequent Registration procedure, and is specified in 3GPP TS 24.526 [144]. + +The Prefixed Operator Identifier based N3IWF FQDN shall be constructed as follows: + +".n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" + +As an example, the Prefixed Operator Identifier based N3IWF FQDN for MNC 123, MCC 345 with an example value "ssn3iwfprefix-Y" is coded in the DNS as: + +"ssn3iwfprefix-Y.n3iwf.5gc.mnc123.mcc345.pub.3gppnetwork.org". + +#### 28.3.2.2.9 Prefixed Tracking Area Identity based N3IWF FQDN + +The Prefixed Tracking Area Identity based N3IWF FQDN, used by a UE that is configured with Slice-specific N3IWF prefix configuration, shall be constructed as specified for the Tracking Area Identity based N3IWF FQDN in clause 28.3.2.2.3, with the addition of before the TAC. The is provided in the Slice-specific N3IWF prefix configuration for the selected PLMN that contains S-NSSAIs that match all (or most, in case there is no full match) of the S-NSSAIs that the UE is going to include in the Requested NSSAI in the subsequent Registration procedure, and is specified in 3GPP TS 24.526 [144]. + +There are two Prefixed Tracking Area Identity based N3IWF FQDNs defined: one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. + +- 1) The Prefixed Tracking Area Identity based N3IWF FQDN using a 2 octet TAC shall be constructed respectively as: + +".tac-lb.tac-hb.tac.n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" + +The syntax and semantics of , , , and are specified in clause 28.3.2.2.3. + +As an example, the Prefixed Tracking Area Identity based N3IWF FQDN for the TAC H'0B21, MCC 345, MNC 12, and an example value "ssn3iwfprefix-Y" is coded in the DNS as: + +"ssn3iwfprefix-Y.tac-lb21.tac-hb0b.tac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" + +- 2) The 5GS Prefixed Tracking Area Identity based N3IWF FQDN using a 3 octet TAC shall be constructed respectively as: + +".tac-lb.tac-mb.tac-hb.5gstac.n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org" + +The syntax and semantics of , , , , and are specified in clause 28.3.2.2.3. + +As an example, the 5GS Prefixed Tracking Area Identity based N3IWF FQDN for the 5GS TAC H'0B1A21, MCC 345, MNC 12, and an example value "ssn3iwfprefix-Y" is coded in the DNS as: + +"ssn3iwfprefix-Y.tac-lb21.tac-mb1a.tac-hb0b.5gstac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" + +## 28.3.2.3 PLMN level and Home NF Repository Function (NRF) FQDN + +### 28.3.2.3.1 General + +When an NF is instantiated, it may register with a PLMN level NF Repository Function (NRF). It may then discover other NF instance(s) in the 5GC by querying the PLMN level NRF. The IP address of the PLMN level NRF can be provisioned into the NF, or the NF can be pre-configured with the FQDN of the PLMN level NRF. If the PLMN level NRF addresses and FQDN are not provisioned into the NF, the NF self-constructs the PLMN level NRF FQDN as per the format specified in clause 28.3.2.3.2. + +For NF discovery across PLMNs, the NRF (e.g vNRF) shall self-construct the PLMN level NRF FQDN of the target PLMN (e.g hNRF) as per the format specified in clause 28.3.2.3.2, and the hNRF URI as per the format specified in subclause 28.3.2.3.3, if the NRF has not obtained the NRF FQDN of the target PLMN. + +### 28.3.2.3.2 Format of NRF FQDN + +The NRF FQDN for an NRF in an operator's PLMN shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the PLMN in which the NRF is located with the label "nrf." as described below: + +- nrf.5gc.mnc.mcc.3gppnetwork.org + +If the SUPI of the UE for construction of the NRF FQDN is of a type other than IMSI (e.g., NSI such as user@operator.com), the NRF FQDN of an NRF in an operator's SNPN, if not pre-configured in the NF, shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the SNPN in which the NRF is located with the label "nrf."e.g. + +- nrf.operator.com : +- nrf.5gc.nid.mnc.mcc.3gppnetwork.org (for SNPN scenarios where NID is available) + +If the SUPI of the UE for construction of the NRF FQDN is of type IMSI, the NID is not available to the NF. Therefore, the NRF FQDN of an NRF in an operator's SNPN, if not pre-configured in the NF, is that of the NRF of the PLMN that owns the MCC and MNC as described below: + +- nrf.5gc.mnc.mcc.3gppnetwork.org + +### 28.3.2.3.3 NRF URI + +In absence of any other local configuration available in the vNRF, the API URIs of the hNRF shall be constructed by deriving the API root (see 3GPP TS 29.501 [128]) as follows: + +- the authority part shall be set to the NRF FQDN as specified in 28.3.2.3.2 +- the scheme shall be "https" +- the port shall be the default port for the "https" scheme, i.e. 443. +- the API prefix optional component shall not be used + +EXAMPLE: For an MCC = 012 and MNC = 345, the API root of the NRF services shall be: + +"https://nrf.5gc.mnc345.mcc012.3gppnetwork.org/" + +#### 28.3.2.4 Network Slice Selection Function (NSSF) FQDN + +##### 28.3.2.4.1 General + +For roaming service, the vNSSF may invoke the Nnssf\_NSSelection\_Get service operation from the hNSSF. For routing of the HTTP/2 messages across the PLMN, the vNSSF self-constructs the FQDN of the hNSSF as per the format specified in clause 28.3.2.4.2 and the URI of the hNSSF as per the format specified in clause 28.3.2.4.3. The Home Network is identified by the PLMN ID of the SUPI provided to the vNSSF by the NF Service Consumer (e.g. the AMF). + +##### 28.3.2.4.2 Format of NSSF FQDN + +The NSSF FQDN for an NSSF in an operator's PLMN shall be constructed by prefixing its Home Network Domain Name (see clause 28.2) with the label "nssf." as described below: + +- nssf.5gc.mnc.mcc.3gppnetwork.org + +The NSSF FQDN for an NSSF in an operator's SNPN, if not pre-configured in the NF, shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the SNPN in which the NSSF is located with the label "nssf." as described below: + +- nssf.5gc.nid.mnc.mcc.3gppnetwork.org + +##### 28.3.2.4.3 NSSF URI + +In absence of any other local configuration available in the vNSSF, the API URIs of the hNSSF shall be constructed by deriving the API root (see 3GPP TS 29.501 [128]) as follows: + +- the authority part shall be set to the NSSF FQDN as specified in 28.3.2.4.2 +- the scheme shall be "https" +- the port shall be the default port for the "https" scheme, i.e. 443. +- the API prefix optional component shall not be used + +EXAMPLE: For an MCC = 012 and MNC = 345, the API root of the NSSF services shall be: + +"https://nssf.5gc.mnc345.mcc012.3gppnetwork.org/" + +#### 28.3.2.5 AMF Name + +The AMF Name FQDN shall uniquely identify an AMF. + +The AMF Name FQDN for an AMF within an operator's PLMN shall be constructed as follows: + +".amf.5gc.mnc.mcc.3gppnetwork.org" + +where + +- the and shall identify the PLMN where the AMF is located and shall be encoded as + - = 3 digits + - = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the AMF Name FQDN. + +- the shall contain at least one label. + +As example, + +- If is amf1.cluster1.net2, the AMF Name FQDN for MCC 345 and MNC 12 is: +"amf1.cluster1.net2.amf.5gc.mnc012.mcc345.3gppnetwork.org" + +The AMF Name FQDN for an AMF within an operator's SNPN, if not pre-configured in the NF, shall be constructed as follows: + +".amf.5gc.nid.mnc.mcc.3gppnetwork.org" + +where + +- and shall be encoded as specified above; +- NID shall be encoded as hexadecimal digits as specified in clause 12.7. + +As example, + +- If is amf1.cluster1.net2, the AMF Name FQDN for MCC 345, MNC 12 and NID 000007ed9d5 (hexadecimal) is: +"amf1.cluster1.net2.amf.5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org" + +### 28.3.2.6 5GS Tracking Area Identity (TAI) FQDN + +The 5GS Tracking Area Identity (TAI) FQDN shall be constructed as follows: + +"tac-lb.tac-mb.tac-hb.5gstac.5gc.mnc.mcc.3gppnetwork.org" + +where the , together with the and shall identify the 5GS Tracking Area Identity, and shall be encoded as follows: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the 5GS TAI FQDN. + +- The 5GS TAC is a 24-bit integer. The is the hexadecimal string of the most significant byte in the TAC and the is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in , or , "0" digit(s) shall be inserted at the left side to fill the 2 digits coding; + +As an example, the 5GS Tracking Area Identity for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: + +"tac-lb21.tac-mb1a.tac-hb0b.5gstac.5gc.mnc012.mcc345.3gppnetwork.org" + +### 28.3.2.7 AMF Set FQDN + +An AMF Set within an operator's PLMN is identified by its AMF Set ID, AMF Region ID, MNC and MCC. + +A subdomain name shall be derived from the MNC and MCC by adding the label "amfset" to the beginning of the Home Network Realm/Domain (see clause 28.2). + +The AMF Set FQDN shall be constructed as follows: + +set.region.amfset.5gc.mnc.mcc.3gppnetwork.org + +where + +- = 3 digits + +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the AMF Set FQDN. + +- and are the hexadecimal strings of the AMF Set ID and AMF Region ID. If there are less than 2 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 2 digits coding. If there are less than 3 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 3 digits coding. + +As an example, the AMF Set FQDN for the AMF Set 1, AMF Region 48 (hexadecimal), MCC 345 and MNC 12 is coded as: + +"set001.region48.amfset.5gc.mnc012.mcc345.3gppnetwork.org" + +An AMF Set within an operator's Stand-alone Non-Public Network (SNPN) shall be identified by its AMF Set ID, AMF Region ID and by either its Network Identifier (NID), MNC and MCC or an SNPN domain name pre-configured in the NF. + +The AMF Set FQDN shall be constructed as follows: + +set.region.amfset.5gc.nid.mnc.mcc.3gppnetwork.org + +or + +set.region.amfset. + +where + +- and shall be encoded as specified above; +- NID shall be encoded as hexadecimal digits as specified in clause 12.7; +- is a domain name chosen by the SNPN operator. + +As an example, the AMF Set FQDN for the AMF Set 1, AMF Region 48 (hexadecimal), NID 000007ed9d5 (hexadecimal), MCC 345 and MNC 12 is coded as: + +"set001.region48.amfset.5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org" + +### 28.3.2.8 AMF Instance FQDN + +The AMF Instance FQDN shall uniquely identify an AMF instance. + +The AMF Instance FQDN shall be constructed as: + +pt.set.region.amfi.5gc.mnc.mcc.3gppnetwork.org + +where + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the AMF Instance FQDN. + +- , and are the hexadecimal strings of the AMF Pointer, AMF Set ID and AMF Region ID. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digits coding of the AMF Pointer or AMF Region Id respectively. If there are less than 3 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 3 digits coding. + +As an example, the AMF Instance FQDN for the AMF Pointer 12 (hexadecimal), AMF Set 1, AMF Region 48 (hexadecimal), MCC 345 and MNC 12 is coded as: + +"pt12.set001.region48.amfi.5gc.mnc012.mcc345.3gppnetwork.org" + +### 28.3.2.9 SMF Set FQDN + +An SMF Set within an operator's network is identified by its NF Set ID as defined in clause 28.12, with NFType set to "smf". + +For an SMF Set within an operator's PLMN, a subdomain name shall be derived from the MNC and MCC by adding the label "smfset" to the beginning of the Home Network Realm/Domain (see clause 28.2). + +The SMF Set FQDN shall be constructed as follows: + +set.smfset.5gc.mnc.mcc.3gppnetwork.org + +where + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the AMF Set FQDN. + +- is the string representing the Set ID part within the NF Set ID defined in clause 28.12. + +EXAMPLE: "set12.smfset.5gc.mnc012.mcc345.3gppnetwork.org" (for the SMF set from MCC 345, MNC 12 and SetID "12") + +NOTE: The labels preceding the ".3gppnetwork.org" domain correspond to the NF Set ID definition in clause 28.12. + +For an SMF Set within an operator's Stand-alone Non-Public Network (SNPN), the SMF Set FQDN shall be constructed from its Network Identifier (NID), MNC and MCC or an SNPN domain name pre-configured in the NF, as follows: + +set.smfset.5gc.nid.mnc.mcc.3gppnetwork.org + +or + +set.smfset. + +where + +- and shall be encoded as specified above; +- NID shall be encoded as hexadecimal digits as specified in clause 12.7; +- is a domain name chosen by the SNPN operator. + +EXAMPLE: "set12.smfset.5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org" (for an SMF set from MCC 345, MNC 12, NID 000007ed9d5 (hexadecimal) and SetID "12") + +### 28.3.2.10 Short Message Service Function (SMSF) FQDN + +The Short Message Service Function (SMSF) FQDN shall be constructed by prefixing its Home Network Domain Name (see clause 28.2) with the label "smf" and with label(s) assigned by a PLMN as described below: + +- .smf.5gc.mnc.mcc.3gppnetwork.org + +This format shall be used as a Diameter identity of an SMSF. A Diameter realm of an SMSF shall be a Home Network Domain Name (see clause 28.2), i.e.: + +- 5gc.mnc.mcc.3gppnetwork.org + +### 28.3.2.11 5G DDNMF FQDN + +The UE may construct the 5G DDNMF FQDN to discover the 5G DDNMF as specified in 3GPP TS 23.304 [143]. The 5G DDNMF FQDN shall be constructed as follows: + +"ddnmf.5gc.mnc.mcc.pub.3gppnetwork.org" + +where the and shall identify the PLMN where the 5G DDNMF is located. Both the "" and "" fields are 3 digits long. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the 5G DDNMF FQDN. + +## 28.4 Information for Network Slicing + +### 28.4.1 General + +In order to identify a Network Slice end to end, the 5GS uses information called S-NSSAI (Single Network Slice Selection Assistance Information). See clause 5.15.2 of 3GPP TS 23.501 [119]. + +An S-NSSAI is comprised of: + +- A Slice/Service type (SST), +- A Slice Differentiator (SD), which is optional information that complements the Slice/Service type(s) to differentiate amongst multiple Network Slices. + +### 28.4.2 Format of the S-NSSAI + +The structure of the S-NSSAI is depicted in Figure 28.4.2-1 + +![Diagram showing the structure of S-NSSAI. It consists of two fields: SST (8 bits) and SD (24 bits). The SST field is a solid rectangle on the left, and the SD field is a dashed rectangle on the right. A double-headed arrow labeled 'S-NSSAI' spans the entire length of both fields.](ed1994bc0ee2985615e5b31df0b48534_img.jpg) + +The diagram illustrates the structure of the S-NSSAI. It is a horizontal rectangle divided into two parts. The left part is labeled 'SST' and contains a smaller rectangle labeled '8 bits'. The right part is labeled 'SD' and contains a dashed rectangle labeled '24 bits'. Below the entire rectangle, a double-headed arrow labeled 'S-NSSAI' indicates the total length of the identifier. + +Diagram showing the structure of S-NSSAI. It consists of two fields: SST (8 bits) and SD (24 bits). The SST field is a solid rectangle on the left, and the SD field is a dashed rectangle on the right. A double-headed arrow labeled 'S-NSSAI' spans the entire length of both fields. + +Figure 28.4.2-1: Structure of S-NSSAI + +The S-NSSAI may include both the SST and SD fields (in which case the S-NSSAI length is 32 bits in total), or the S-NSSAI may just include the SST field (in which case the S-NSSAI length is 8 bits only). + +The SST field may have standardized and non-standardized values. Values 0 to 127 belong to the standardized SST range and they are defined in 3GPP TS 23.501 [119]. Values 128 to 255 belong to the Operator-specific range. + +The SD field has a reserved value "no SD value associated with the SST" defined as hexadecimal FFFFFFFF. In certain protocols, the SD field is not included to indicate that no SD value is associated with the SST. + +### 28.4.3 Ranges of S-NSSAIs + +In the 5G Core Network, an NF Instance may indicate (e.g., while registering its NF profile in the NRF) support for several S-NSSAIs having a common SST value and different SDs, by including such SST value and adding, either a list of ranges of SDs, or a "wildcard" flag representing all SD values for the common SST (see 3GPP TS 29.571 [129], clause 5.4.5.1). + +For an NF registering a list of supported S-NSSAIs in terms of ranges of SDs, or wildcard, the NF may associate a common network slicing policy (such as, e.g., for an AMF to assign a specific DNN to be used with a certain slice) to all S-NSSAIs derived from that SD range. + +NOTE: The usage of SD ranges to define sets of S-NSSAIs is restricted to be used only by certain protocols/APIs in the 5G Core Network (e.g., NRF, NSSF, AMF...). + +#### 28.4.4 Network Slice Instance Identifier (NSI ID) + +A Network Slice Instance Identifier (NSI ID) uniquely identifies a Network Slice Instance (NSI) within a PLMN or SNPN, when multiple NSIs of a same Network Slice are deployed and there is a need to differentiate between them in the 5GC. + +See 3GPP TS 23.501 [119] for the definition of the Network Slice Instance. An NSI may be associated with one or more S-NSSAIs, and an S-NSSAI may be associated with one or more NSIs. + +The NSI ID is defined as an operator specific string (see clause 6.1.6.2.2 of 3GPP TS 29.510 [130]). + +#### 28.4.5 Network Slice Admission Control (NSAC) Service Area Identifier (SAI) + +A Network Slice Admission Control (NSAC) Service Area Identifier (SAI) uniquely identifies a NSAC Service Area within a PLMN or SNPN. + +See 3GPP TS 23.501 [119] for the definition of the NSAC Service Area. + +The NSAC SAI is defined as an operator specific string (see 3GPP TS 29.571 [129]). + +### 28.5 NF FQDN Format for Inter PLMN Routing + +#### 28.5.1 General + +For routing HTTP/2 request messages to NF in a different PLMN, the FQDN of the target NF shall have the Home Network Domain (see clause 28.2) as the trailing part. + +#### 28.5.2 Telescopic FQDN + +The FQDN of the NF services or the authority part of URIs in another PLMN, may be appended with the PLMN Network Domain of the request initiating PLMN, as the trailing part to form a Telescopic FQDN as specified in 3GPP TS 33.501 [124]. The Telescopic FQDN shall be constructed as follows: + + protection scheme: + +type0.rid678.schid1.hnkey27.ecckey.cip< encryption of 09999999999>.mac@5gc.mnc015.mcc234.3gppnetwork.org + +Assuming the Network Specific Identifier user17@example.com, the Routing Indicator 678, and a Home Network Public Key Identifier of 27, the NAI format for the SUCI takes the form: + +- for the null-scheme: + +type1.rid678.schid0.useriduser17@example.com + +- for an anonymous SUCI: + +type1.rid678.schid0.useridanonymous@example.com (with username corresponding to "anonymous"), or + +type1.rid678.schid0.userid@example.com (with username corresponding to an empty string) + +- for the Profile protection scheme: + +type1.rid678.schid1.hnkey27.ecckey.cip< encryption of user17>.mac@example.com + +See clauses 28.15.5 and 28.16.5 for the NAI format for a SUCI containing a GCI or a GLI. + +## 28.7.4 Emergency NAI for Limited Service State + +This clause describes the format of the UE identification when UE is performing an emergency registration and IMSI is not available or not authenticated. + +The Emergency NAI for Limited Service State shall take the form of an NAI, and shall have the form `username@realm` as specified in clause 2.2 of IETF RFC 7542 [126]. The exact format shall be: + +`imei@sos.invalid` + +NOTE: The top level domain ".invalid" is a reserved top level domain, as specified in IETF RFC 2606 [64], and is used here due to the fact that this NAI never needs to be resolved for routing. + +or if IMEI is not available, + +`mac@sos.invalid` + +For example, if the IMEI is 219551288888888, the Emergency NAI for Limited Service State then takes the form of `imei219551288888888@sos.invalid`. + +For example, if the MAC address is 44-45-53-54-00-AB, the Emergency NAI for Limited Service State then takes the form of `mac4445535400AB@sos.invalid`, where the MAC address is represented in hexadecimal format without separators. + +## 28.7.5 Alternative NAI + +The Alternative NAI shall take the form of a NAI, i.e. '`any_username@realm`' as specified of IETF RFC 7542 [126]. The Alternative NAI shall not be routable from any AAA server. + +The Alternative NAI shall contain a username part that is not a null string. + +The realm part of the NAI shall be "unreachable.3gppnetwork.org". + +The result shall be an NAI in the form of: + +`"@unreachable.3gppnetwork.org"`. + +## 28.7.6 NAI used for 5G registration via trusted non-3GPP access + +While performing the EAP-authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected PLMN (see clause 4.12a in 3GPP TS 23.502 [120]), the UE shall derive a NAI from the identity of the selected PLMN in the following format: + +`"@nai.5gc.mnc.mcc.3gppnetwork.org"` + +where: + +- the username part `` is any non null string; and +- the `` and `` identify the PLMN (either HPLMN or VPLMN) to which the UE attempts to connect via the trusted non-3GPP access network as described in clause 6.3.12 in 3GPP TS 23.501 [119]. + +While performing the EAP-authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected SNPN (see clause 5.30.2.13 in 3GPP TS 23.501 [119]), the UE shall derive a NAI from the identity of the selected SNPN in the following format: + +`"@nai.5gc.nid.mnc.mcc.3gppnetwork.org"`; + +where: + +- the username part `` is any non null string; and +- the ``, `` and `` identify the SNPN to which the UE attempts to connect via the trusted non-3GPP access network. + +While performing the EAP authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected TNGF, the UE shall derive NAI from the identity of the selected TNGF in the following format: + +"@tngfid.nai.5gc.mnc.mcc.3gppnetwork.org"; + +where: + +- a) The username part is any non null string; and +- b) The and identify the PLMN (either HPLMN or VPLMN) to which the UE attempts to connect via the trusted non-3GPP access network; and +- c) identifies the TNGF. The TNGF ID value shall comply with the syntax specified in clause 2.2 of IETF RFC 7542 [126] for a label in the realm part of a NAI. + +While performing the EAP-authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected SNPN and TNGF, the UE shall derive a NAI from the identity of the selected SNPN and TNGF in the following format: + +"@tngfid.nai.5gc.nid.mnc.mcc.3gppnetwork.org"; + +where: + +- a) the username part is any non null string; and +- b) the , and identify the SNPN to which the UE attempts to connect via the trusted non-3GPP access network; and +- c) identifies the TNGF. The TNGF ID value shall comply with the syntax specified in clause 2.2 of IETF RFC 7542 [126] for a label in the realm part of a NAI. + +NOTE 1: The username part of the NAI is not used to identify the UE since the UE is identified by its NAS registration to the 5GCN independent of using the NAI. The realm part of the NAI is however used by the trusted non-3GPP access for TNGF selection. + +NOTE 2: In case of 5GCN, there is no need for a decorated NAI as in EPC (see clause 19.3.3), since the UE sends a NAS registration request to the PLMN including a SUCI or 5G-GUTI. + +## 28.7.7 NAI used by N5CW devices via trusted non-3GPP access + +### 28.7.7.0 General + +While performing the EAP authentication procedure when a non 5G capable over WLAN (N5CW) device attempts to register to 5GCN via a trusted non-3GPP access network in a selected PLMN (see clause 4.12 b in 3GPP TS 23.502 [120]), the N5CW device shall derive a NAI from the identity of the selected PLMN in the following format: + +"<5G\_device\_unique\_identity>@nai.5gc-nn.mnc.mcc.3gppnetwork.org"; + +where: + +- a) the username part <5G\_device\_unique\_identity> is to identify the N5CW device and contains either: + - SUCI as defined as the username part of the NAI format in clause 28.7.3, if the UE is not registered to 5GCN via NG-RAN; or + - 5G-GUTI as defined as the username part of the NAI format in clause 28.7.8, if the N5CW device is registered to 5GCN via NG-RAN; and +- b) the label '5gc-nn' in the realm part indicates the NAI is used by N5CW devices via trusted non-3GPP access. and identify the PLMN (either HPLMN or VPLMN) to which the N5CW device attempts to connect via the trusted non-3GPP access network as described in clause 6.3.12 in 3GPP TS 23.501 [119]. + +While performing the EAP authentication procedure when a non 5G capable over WLAN (N5CW) device attempts to register to 5GCN via a trusted non-3GPP access network in a selected SNPN (see clause 5.30.2.13 in 3GPP TS 23.501 [119]), the N5CW device shall derive a NAI from the identity of the selected SNPN in the following format: + +"<5G\_device\_unique\_identity>@nai.5gc-nn.nid.mnc.mcc.3gppnetwork.org"; + +where: + +- a) the username part <5G\_device\_unique\_identity> is to identify the N5CW device and contains either: + - SUCI as defined as the username part of the NAI format in clause 28.7.3; or + - 5G-GUTI as defined as the username part of the NAI format in clause 28.7.8, if the N5CW device is registered to 5GCN via NG-RAN; and +- b) the label '5gc-nn' in the realm part indicates the NAI is used by N5CW devices via trusted non-3GPP access. , and identify the SNPN to which the N5CW device attempts to connect via the trusted non-3GPP access network. + +NOTE: As defined in 3GPP TS 33.501 [124], an N5CW device is authenticated using EAP-AKA', thus, it has a USIM that stores the HPLMN identity. + +In roaming scenarios, the NAI shall use the decorated NAI format as specified in clause 28.7.7.1 or 28.7.7.2. + +#### 28.7.7.1 Decorated NAI used for N5CW devices via trusted non-3GPP access + +The Decorated NAI used for N5CW devices via trusted non-3GPP access roaming scenarios shall take the form: + +"nai.5gc-nn.mnc.mcc.3gppnetwork.org!<5G\_device\_unique\_identity>@nai.5gc-nn.mnc.mcc.3gppnetwork.org" + +where the <5G\_device\_unique\_identity> is to identify the N5CW device as defined in clause 28.7.7.0. + +#### 28.7.7.2 Decorated NAI used for N5CW devices via trusted non-3GPP access for SNPN + +If the credentials holder is constructed based on SNPN, the Decorated NAI used for N5CW devices via trusted non-3GPP access for SNPN scenarios shall take the form: + +"nai.5gc-nn.nid.mnc.mcc.3gppnetwork.org!<5G\_device\_unique\_identity>@nai.5gc-nn.nid.mnc.mcc.3gppnetwork.org" where the <5G\_device\_unique\_identity> is to identify the N5CW device as defined in clause 28.7.7.0, the or shall be encoded as hexadecimal digits as specified in clause 12.7, and the , , and are used to identify the SNPN based credentials holder. + +If the credentials holder is constructed based on PLMN, the Decorated NAI used for N5CW devices via trusted non-3GPP access for SNPN shall take the form: + +"nai.5gc-nn.mnc.mcc.3gppnetwork.org!<5G\_device\_unique\_identity>@nai.5gc-nn.nid.mnc.mcc.3gppnetwork.org" + +where the <5G\_device\_unique\_identity> is to identify the N5CW device as defined in clause 28.7.7.0, the shall be encoded as hexadecimal digits as specified in clause 12.7, and the and are used to identify the PLMN based credentials holder. + +#### 28.7.8 NAI format for 5G-GUTI + +The NAI format of the 5G-GUTI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126]. + +The username part of the NAI shall take the following form: + +tmsi<5G-TMSI>.pt.set.region + +<5G-TMSI>, , and are the hexadecimal strings of the 5G-TMSI, AMF Pointer, AMF Set ID and AMF Region ID. If there are less than 8 significant digits in <5G-TMSI>, "0" digit(s) shall be inserted at the left side to fill the 8 digits coding. If there are less than 2 significant digits in or , "0" digit(s) shall be inserted at the left side to fill the 2 digits coding of the AMF Pointer or AMF Region Id respectively. If there are less than 3 significant digits in , "0" digit(s) shall be inserted at the left side to fill the 3 digits coding. + +Example: + +Assuming 5G-TMSI = 06666666 (hexadecimal), AMF Pointer=12 (hexadecimal), AMF Set = 001 (hexadecimal), AMF Region = 48 (hexadecimal), the username part of the NAI is encoded as: + +"tmsi06666666.pt12.set001.region48" + +The NAI for an N5CW device in a PLMN (either HPLMN or VPLMN) with MNC=012 and MCC=345, to which the N5CW device attempts to connect via the trusted non-3GPP access, according to clause 28.7.7 is: + +"tmsi06666666.pt12.set001.region48@nai.5gc-nn.mnc012.mcc345.3gppnetwork.org" + +## 28.7.9 Decorated NAI format for SUCI + +### 28.7.9.1 General + +The Decorated NAI format for SUCI shall take the form of a NAI and shall have the form + +'Homerealm!username@otherrealm' + +as specified in clause 2.7 of the IETF RFC 4282 [53]. + +The username part of Decorated NAI shall contain the username of the NAI format for SUCI as specified in clause 28.7.3. + +'Homerealm' shall be the realm of the NAI format for SUCI as specified in clause 28.7.3, unless specified otherwise in relevant clauses. + +The realm part of Decorated NAI consists of 'otherrealm', see the IETF RFC 4282 [53]. Otherrealm' is the realm built using the PLMN ID (visited MCC + visited MNC) of the visited PLMN selected by the UE. In case of the SNPN scenarios, the "Otherrealm" is the realm build using the SNPN ID (PLMN ID + NID, where PLMN ID + NID are MCC + MNC + NID of the non-subscribed SNPN). + +The 'Homerealm' and the 'otherealm' may be preceded by one or more labels for specific use cases of the Decorated NAI format for SUCI, e.g. for 5G NSWO (see clause 28.7.9.2). + +The result is a decorated NAI should take the form as mentioned below: + +.mnc.mcc.3gppnetwork.org!@.mnc.mcc.3gppnetwork.org + +For the SNPN scenarios where the credential holder is a subscribed SNPN, the decorated NAI should have the form as mentioned below: + +.nid.mnc.mcc.3gppnetwork.org!@.nid.mnc.mcc.3gpp network.org + +For the SNPN scenarios where the credential holder is an HPLMN, the decorated NAI should have the form as mentioned below: + +.mnc< homeMNC>.mcc< homeMNC>.3gppnetwork.org!@.nid.mnc.mcc.3gppnetwork.org + +NOTE: In 3GPP TS 23.122 [139], the term "subscribed SNPN" refers to the SNPN for which UE has a subscription. The term "subscribedSNPNMCC" hence, refers to the MCC of the SNPN to which the UE is subscribed. The term "subscribedSNPNMNC" also refers to the MNC of the SNPN to which the UE is subscribed. + +## 28.7.9.2 Decorated NAI used for 5G NSWO + +The result is a decorated NAI of the form: + +5gc-nswo.mnc.mcc.3gppnetwork.org!@5gc-nswo.mnc.mcc.3gppnetwork.org + +For the SNPN scenarios where the credential holder is a subscribed SNPN, the decorated NAI should have the form as mentioned below: + +5gc-nswo.nid.mnc.mcc.3gppnetwork.org!@5gc-nswo.nid.mnc.mcc.3gppnetwork.org + +For the SNPN scenarios where the credential holder is an HPLMN, the decorated NAI should have the form as mentioned below: + +5gc-nswo.mnc.mcc.3gppnetwork.org!@5gc-nswo.nid.mnc.mcc.3gppnetwork.org + +### EXAMPLE: + +Assuming the IMSI 234150999999999, where MCC=234, MNC=15 and MSISN=09999999999, the Routing Indicator 678, a Home Network Public Key Identifier of 27, the null-scheme, and the Visited PLMN ID (MCC = 610, MNC = 71): + +- the NAI format for the SUCI for 5G NSWO takes the form: + +type0.rid678.schid0.userid09999999999@5gc-nswo.mnc015.mcc234.3gppnetwork.org + +- the Decorated NAI format for the SUCI for 5G NSWO roaming takes the form: + +5gc-nswo.mnc015.mcc234.3gppnetwork.org!type0.rid678.schid0.userid09999999999@5gc-nswo.mnc071.mcc610.3gppnetwork.org + +For SNPN scenarios, decorated NAI format for SUCI for 5G-NSWO roaming shall take the following form: + +Assuming the IMSI 234150999999999, where the subscribed SNPN that has MCC 234, MNC 015, and NID 345678ABCD and the non-subscribed SNPN (MCC =999, MNC =012, and NID 45678ABCDE).5gc-nswo.nid345678ABCD.mnc015.mcc234.3gppnetwork.org!type0.rid678.schid0.userid09999999999@5gc-nswo.nid45678ABCDE.mnc012.mcc999.3gppnetwork.org + +Assuming the IMSI 234150999999999, where the HPLMN that has MCC 234 and MNC 015 and the non-subscribed SNPN (MCC =999, MNC =012, and NID 45678ABCDE). + +5gc-nswo.nid345678ABCD.mnc015.mcc234.3gppnetwork.org!type0.rid678.schid0.userid09999999999@5gc-nswo.nid45678ABCDE.mnc012.mcc999.3gppnetwork.org + +## 28.7.10 NAI format for UP-PRUK ID + +The NAI format for UP-PRUK ID shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126], where: + +- the realm part shall be in the form: + +"prose-up.5gc.mnc.mcc.3gppnetwork.org" + +- the username part shall be a non-empty string which is unique in the realm, as specified in 3GPP TS 33.503 [142]. + +The maximum length of a UP-PRUK ID in NAI format is 254 octets. + +## 28.7.11 NAI format for CP-PRUK ID + +The NAI format for CP-PRUK ID shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126]. + +The realm part shall be in the form: + +"prose-cp.5gc.mnc.mcc.3gppnetwork.org" + +The username part of the NAI shall take one of the following forms: + +"rid.pid" + +- the part is the "Routing Indicator" as specified in clause 2.2B. +- the part is the hexadecimal representation of the CP-PRUK ID\* specified in clause A.3 of 3GPP TS 33.503 [142]. + +The maximum length of a CP-PRUK ID in NAI format is 254 octets. + +## 28.7.12 NAI used for 5G NSWO + +When the UE decides to use 5G NSWO to connect to the WLAN access network using its 5GS credentials but without registration to 5GS, the NAI format for 5G NSWO in non-roaming scenarios is used. See clause 28.7.9.2 for the NAI format for 5G NSWO in roaming scenarios. + +NOTE: In this case the NAI realm is different than the realm defined for usage during 5G registration via of Trusted non-3GPP access to the 5GCN (see clause 28.7.6) or when N5CW devices access 5GCN via Trusted non-3GPP access to the 5GCN (see clause 28.7.7). See clause 5.42 in 3GPP TS 23.501 [119]. + +In the 5G NSWO use case, the UE shall use a NAI in the following format: + +- For PLMNs: "@5gc-nswo.mnc.mcc.3gppnetwork.org" +- For SNPNS: "@5gc-nswo.nid.mnc.mcc.3gppnetwork.org" + +In the above use cases: + +- The entire NAI is constructed by the definition of the username part in clause 28.7.3, along with the realm mentioned in this section. +- the label '5gc-nswo' in the realm part indicates that the NAI is used for 5G NSWO. For PLMNs, and identify the PLMN, and for SNPNS, , and identify the SNPN, to which the UE attempts to connect via the 5G NSWO as described in clause 4.2.15 of 3GPP TS 23.501 [119]. + +For an anonymous SUCI in the 5G NSWO use case, assuming that, a MCC=234, MNC=15 and the Routing Indicator 678, the UE shall use the NAI in the following format: + +type1.rid678.schid0.useridanonymous@5gc-nswo.nid.mnc015.mcc234.3gppnetwork.org (with username corresponding to "anonymous"), or + +type1.rid678.schid0.userid@5gc-nswo.nid.mnc015.mcc234.3gppnetwork.org (with username corresponding to an empty string) + +## 28.8 Generic Public Subscription Identifier (GPSI) + +The Generic Public Subscription Identifier (GPSI) is defined in clause 5.9.8 of 3GPP TS 23.501 [119]. + +The GPSI is defined as: + +- a GPSI type: in this release of the specification, it may indicate an MSISDN or an External Identifier; and +- dependent on the value of the GPSI type: + - an MSISDN as defined in clause 3.3; or + - an External Identifier as defined in clause 19.7.2. + +NOTE: Depending on the protocol used to convey the GPSI, the GPSI type can take different formats. + +## 28.9 Internal-Group Identifier + +Internal-Group Identifier is a network internal globally unique ID which identifies a set of SUPIs (e.g. MTC devices) from a given network that are grouped together for one specific group related service (see 3GPP TS 23.501 [119] clause 5.9.7). + +An Internal-Group Identifier shall be composed in the same way as IMSI-Group Identifier (see clause 19.9). + +If a 5G subscriber's IMSI belongs to an IMSI-Group identified by a given IMSI-Group Identifier X, the IMSI shall also belong to the Internal-Group identified by the Internal-Group Identifier X. + +## 28.10 Presence Reporting Area Identifier (PRA ID) + +The Presence Reporting Area Identifier (PRA ID) is used to identify a Presence Reporting Area (PRA). + +PRAs can be used for reporting changes of UE presence in a PRA, e.g. for policy control or charging decisions. See 3GPP TS 23.501 [119] and 3GPP TS 23.503 [121]. + +A PRA is composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN. A PRA can be: + +- either a "UE-dedicated PRA", defined in the subscriber profile; +- or a "Core Network predefined PRA", pre-configured in AMF. + +PRA IDs used to identify "Core Network predefined PRAs" shall not be used for identifying "UE-dedicated PRAs". + +The same PRA ID may be used for different UEs to identify different "UE-dedicated PRAs", i.e. PRA IDs may overlap between different UEs, while identifying different "UE-dedicated PRAs". + +The PRA ID shall be formatted as an integer within the following ranges: + +0 .. 8 388 607 for UE-dedicated PRA + +8 388 608 to 16 777 215 for Core Network predefined PRA. + +NOTE: The PRA ID is encoded over the Service Based Interfaces as a string of digits representing an integer. See 3GPP TS 29.571 [129]. + +## 28.11 CAG-Identifier + +A Closed Access Group (CAG) within a PLMN is uniquely identified by a CAG-Identifier (see 3GPP TS 23.501 [119]). + +The CAG-Identifier shall be a fixed length 32 bit value. + +## 28.12 NF Set Identifier (NF Set ID) + +A NF Set Identifier is a globally unique identifier of a set of equivalent and interchangeable CP NFs from a given network that provide distribution, redundancy and scalability (see clause 5.21.3 of 3GPP TS 23.501 [119]). + +An NF Set Identifier shall be constructed from the MCC, MNC, NID (for SNPN), NF type and a Set ID. + +A NF Set Identifier shall be formatted as the following string: + +set.set.5gc.mnc.mcc for a NF Set in a PLMN, or + +set.set.5gc.nid.mnc.mcc for a NF Set in a SNPN. + +where: + +- the and shall identify the PLMN of the NF Set and shall be encoded as follows: + - = 3 digits + - = 3 digits + If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC. +- the Network Identifier (NID) shall be encoded as hexadecimal digits as specified in clause 12.7. +- the shall identify the NF type of the NFs within the NF set and shall be encoded as a value of Table 6.1.6.3.3-1 of 3GPP TS 29.510 [130] but with lower case characters; +- the Set ID shall be a NF type specific Set ID within the PLMN, chosen by the operator, that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit; +- the case of alphabetic characters is not significant (i.e. two NF Set IDs with the same characters but using different lower and upper cases identify the same NF Set). + +For an AMF set, the Set ID shall be set to "-region", with the AMF Region ID and AMF Set ID encoded as defined in 3GPP TS 29.571 [129]. + +EXAMPLE 1: setxyz.smfset.5gc.mnc012.mcc345 + +EXAMPLE 2: set12.pcfset.5gc.mnc012.mcc345 + +EXAMPLE 3: set001-region48.amfset.5gc.mnc012.mcc345 (for AMF Region 48 (hexadecimal) and AMF Set 1) + +EXAMPLE 4: setxyz.smfset.5gc.nid000007ed9d5.mnc012.mcc345 for a SNPN with the NID 000007ed9d5 (hexadecimal). + +NOTE 1: If needed, an FQDN can be derived from a given NF Set ID by appending the ".3gppnetwork.org" domain to the NF Set ID, see e.g. SMF Set FQDN in clause 28.3.2.9. For NFs whose NF type contains an underscore and for which an FQDN needs to be derived, the underscore is replaced by a hyphen in the corresponding label of the FQDN. As an exception, the AMF Set FQDN defined in clause 28.3.2.7 is not derived by merely appending the ".3gppnetwork.org" domain to the NF Set ID of an AMF set defined in this clause. + +NF Instances of an NF Set are equivalent and share the same MCC, MNC, NID (for SNPN), NF type and NF Set ID. + +In earlier versions of this specification, the Set ID of an AMF Set was defined to be set to the string ".region". For backward compatibility with AMF implementations complying with these earlier versions of the specifications, AMF peers' implementations shall: + +- support receiving such a former encoding of an AMF Set ID in 3GPP custom HTTP headers (e.g. 3gpp-Sbi-Binding header or 3gpp-Sbi-Producer header) and shall interpret it the same as if they receive these headers with the AMF Set format defined in the current version of the specification; and +- use the amf-region-id and the amf-set-id query parameters when they need to discover the AMF profiles of the AMF set registered at the NRF, when receiving a binding header with such a former encoding of the AMF Set ID. + +NOTE 2: The NF Set ID format for an AMF set defined in earlier versions of the specification cannot be encoded in JSON attributes defined with the NfSetId data type of 3GPP TS 29.571 [129] which does not allow to encode a period ".". Accordingly, any such attribute encodes the Set ID of an AMF set as defined above (i.e. -region"). + +## 28.13 NF Service Set Identifier (NF Service Set ID) + +A NF Service Set Identifier is a globally unique identifier of a set of equivalent and interchangeable CP NF service instances within a NF instance from a given network that provide distribution, redundancy and scalability (see clause 5.21.3 of 3GPP TS 23.501 [119]). + +An NF Service Set Identifier shall be constructed from the MCC, MNC, NID (for SNPN), NF instance Identifier, service name and a Set ID. + +A NF Service Set Identifier shall be formatted as the following string: + +set.sn.nfi.5gc.mnc.mcc for a NF Service Set in a PLMN, or + +set.sn.nfi.5gc.nid.mnc.mcc for a NF Service Set in a SNPN. + +where: + +- the and shall identify the PLMN of the NF Service Set and shall be encoded as follows: + +- = 3 digits +- = 3 digits + +If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC. + +- the Network Identifier (NID) shall be encoded as hexadecimal digits as specified in clause 12.7. +- the NFInstanceID shall identify the NF instance of the NF Service set, as defined by 3GPP TS 23.501 [119] and 3GPP TS 29.510 [130]; +- the ServiceName shall identify the NF service of the NF Service set, as defined by 3GPP TS 29.510 [130]; +- the Set ID shall be a service specific Set ID within the NF instance, chosen by the operator that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit; +- the case of alphabetic characters is not significant (i.e. two NF Service Set IDs with the same characters but using different lower and upper cases identify the same NF Service Set). + +EXAMPLE 1: setxyz.snsmf-pdusession.nfi54804518-4191-46b3-955c-ac631f953ed8.5gc.mnc012.mcc345 + +EXAMPLE 2: set2.snnpcf-smppolicycontrol.nfi54804518-4191-46b3-955c-ac631f953ed8.5gc.mnc012.mcc345 + +EXAMPLE 3: setxyz.snsmf-pdusession.nfi54804518-4191-46b3-955c-ac631f953ed8.5gc.nid000007ed9d5.mnc012.mcc345 for a SNPN with the NID 000007ed9d5 (hexadecimal). + +NF service instances from different NF instances are equivalent NF service instances if they share the same MCC, MNC, NID (for SNPN), ServiceName and Set ID. + +NF Service Sets belonging to different NF Instances are said to be equivalent, if they share the same MCC, MNC, NID (for SNPN), ServiceName and Set ID. + +## 28.14 Data Network Access Identifier (DNAI) + +A Data Network Access Identifier (DNAI) is an operator defined identifier of a user plane access to one or more DN(s) where applications are deployed (see clauses 3.1 and 5.6.7 in 3GPP TS 23.501 [119]). The same DN may also be referred to by multiple DNAIs. + +DNAI is represented as an operator specific string (see clause A.2 in 3GPP TS 29.571 [129]). The format of the DNAI is defined by the operator and is not standardized. + +## 28.15 Global Cable Identifier (GCI) + +### 28.15.1 Introduction + +This clause describes the GCI formats used in the 5G System. + +### 28.15.2 NAI format for SUPI containing a GCI + +A SUPI containing a GCI shall take the form of a Network Access Identifier (NAI). + +The NAI for SUPI shall have the form `username@realm` as specified in clause 2.2 of IETF RFC 7542 [126], where: + +- the username part shall be the GCI, as defined in clause 28.15.4; +- the realm part shall identify the operator owning the subscription; if the operator owns a PLMN ID, the realm part should be in the form: + +`"5gc.mnc.mcc.3gppnetwork.org"` + +EXAMPLE 1: `00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org` + +EXAMPLE 2: `00-00-5E-00-53-00@operator.com` + +### 28.15.3 User Location Information for RG accessing the 5GC via W-5GCAN (HFC Node ID) + +The User Location information for a 5G-CRG/FN-CRG accessing the 5GC via a Wireline 5G Cable Access network (W-5GCAN) shall take the form of an HFC Node ID. The HFC Node ID consists of a string of up to six characters as specified in CableLabs WR-TR-5WWC-ARCH [134]. + +The User Location information shall include the GCI and HFC Node ID for a AUN3 device connected behind the 5G-CRG (see clause 7.2.8.1 of 3GPP TS 23.316 [131]). + +### 28.15.4 GCI + +The GCI uniquely identifies the line connecting the 5G-CRG or FN-CRG to the 5GS. + +The GCI is a variable length opaque identifier, encoded as specified in CableLabs WR-TR-5WWC-ARCH [134] and CableLabs DOCSIS MULPI [135]. It shall comply with the syntax specified in clause 2.2 of IETF RFC 7542 [126] for the username part of a NAI. + +NOTE: The GCI contains an HFC\_Identifier, see WR-TR-5WWC-ARCH [134] and CableLabs DOCSIS MULPI [135]. + +EXAMPLE: `00-00-5E-00-53-00` + +### 28.15.5 NAI format for SUCI containing a GCI + +The SUCI containing a GCI shall take the form of a Network Access Identifier (NAI). + +The NAI format of the SUCI shall have the form `username@realm` as specified in clause 2.2 of IETF RFC 7542 [126], where the realm part shall be identical to the realm part of the SUPI (see clause 28.15.2). + +The username part of the NAI shall be encoded as specified for the null-scheme in clause 28.7.3, i.e. it shall take the following form: + +`type3.rid0.schid0.userid` + +where the username shall be encoded as the username part of the SUPI (see clause 28.15.2). + +EXAMPLE 1: `type3.rid0.schid0.userid00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org` + +EXAMPLE 2: type3.rid0.schid0.userid00-00-5E-00-53-00@operator.com + +## 28.16 Global Line Identifier (GLI) + +### 28.16.1 Introduction + +This clause describes the GLI formats used in the 5G System. + +### 28.16.2 NAI format for SUPI containing a GLI + +A SUPI containing a GLI shall take the form of a Network Access Identifier (NAI). + +The NAI for SUPI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126], where: + +- the username part shall be the GLI, as defined in clause 28.16.4; +- the realm part shall identify the operator owning the subscription; if the operator owns a PLMN ID, the realm part should be in the form: + +"5gc.mnc.mcc.3gppnetwork.org" + +### 28.16.3 User Location Information for RG accessing the 5GC via W-5GBAN + +The User Location information for a 5G-BRG/FN-BRG accessing the 5GC via a Wireline BBF Access Network (W-5GBAN), and for a AUN3 device connected behind the 5G-BRG (see clause 7.2.8.1 of 3GPP TS 23.316 [131]), shall take the form of a GLI as defined in clause 28.16.4. + +### 28.16.4 GLI + +The GLI uniquely identifies the line connecting the 5G-BRG or FN-BRG to the 5GS. + +The GLI is a variable length opaque identifier, consisting of a string of up to 200 base64-encoded characters, representing the GLI value (up to 150 bytes) encoded as specified in BBF WT-470 [133]. + +NOTE: The GLI contains an identifier of the Line ID source and the Line ID value, see BBF WT-470 [133]. + +### 28.16.5 NAI format for SUCI containing a GLI + +The SUCI containing a GLI shall take the form of a Network Access Identifier (NAI). + +The NAI format of the SUCI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126], where the realm part shall be identical to the realm part of the SUPI (see clause 28.16.2). + +The username part of the NAI shall be encoded as specified for the null-scheme in clause 28.7.3, i.e. it shall take the following form: + +type2.rid0.schid0.userid + +where the username shall be encoded as the username part of the SUPI (see clause 28.16.2). + +## 28.17 DNS subdomain for operator usage in 5GC + +The 5GC nodes DNS subdomain (DNS zone) shall be derived from the MNC and MCC by adding the label "node" to the beginning of the Home Network Domain for 5GC (see clause 28.2) and shall be constructed as: + +node.5gc.mnc.mcc.3gppnetwork.org + +This DNS subdomain is formally placed into the operator's control. 3GPP shall never take this DNS subdomain back or any zone cut/subdomain within it for any purpose. As a result the operator can safely provision any DNS records it chooses under this subdomain without concern about future 3GPP standards encroaching on the DNS names within this zone. + +## 28.18 NF FQDN Format for Inter SNPN Routing + +### 28.18.1 General + +For routing HTTP/2 request messages to NF in a different SNPN, the FQDN of the target NF shall have the Home Network Domain of the SNPN (see clause 28.2) as the trailing part. + +NOTE 1: The MCC used in the SNPNs can be 999, which is allocated for internal use within a private network. + +NOTE 2: Locally assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same locally assigned NID. + +## 29 Numbering, addressing and identification for RACS + +### 29.1 Introduction + +This clause describes the format of the parameters used for Radio Capability Signalling Optimisation (RACS). For further information on the use of the parameters see 3GPP TS 23.401 [72] and 3GPP TS 23.501 [119]. + +### 29.2 UE radio capability ID + +The UE radio capability ID is an identifier used to represent a set of UE radio capabilities, defined in 3GPP TS 23.501 [119] and in 3GPP TS 23.401 [72], composed as shown in figure 29.2-1. + +![Figure 29.2-1: Structure of UE radio capability ID. The diagram shows a horizontal sequence of four fields: TF (1 digit), Vendor ID (8 digits), Version ID (2 digits), and RCI (11 digits). The first three fields (TF, Vendor ID, and Version ID) are grouped together by a dashed box labeled 'UE radio capability ID'. The RCI field is separate. Arrows above each field indicate its length in digits.](3ae0872dc01de8bf4c43996b9507914b_img.jpg) + +The diagram illustrates the structure of the UE radio capability ID. It consists of four main components arranged horizontally: + + +- TF**: 1 digit +- Vendor ID**: 8 digits (indicated by a dashed box) +- Version ID**: 2 digits (indicated by a dashed box) +- RCI**: 11 digits + + The first three components (TF, Vendor ID, and Version ID) are collectively labeled as 'UE radio capability ID' within a dashed box. Arrows above each component indicate its length in digits. + +Figure 29.2-1: Structure of UE radio capability ID. The diagram shows a horizontal sequence of four fields: TF (1 digit), Vendor ID (8 digits), Version ID (2 digits), and RCI (11 digits). The first three fields (TF, Vendor ID, and Version ID) are grouped together by a dashed box labeled 'UE radio capability ID'. The RCI field is separate. Arrows above each field indicate its length in digits. + +**Figure 29.2-1: Structure of UE radio capability ID** + +The UE radio capability ID is composed of the following elements (each element shall consist of hexadecimal digits only): + +- 1) Type Field (TF): identifies the type of UE radio capability ID. The following values are defined: + - 0: manufacturer-assigned UE radio capability ID; + - 1: network-assigned UE radio capability ID; and + - 2 to F: spare values for future use. + +- 2) The Vendor ID is an identifier of UE manufacturer. This is defined by a value of Private Enterprise Number issued by Internet Assigned Numbers Authority (IANA) in its capacity as the private enterprise number administrator, as maintained at . Its length is 8 hexadecimal digits. This field is present only if the Type Field is set to 0; + +NOTE: The private enterprise number issued by IANA is a decimal number in the range between 0 and 4294967295 that needs to be converted to a fixed length 8 digit hexadecimal number when used within the UE Radio Capability ID. E.g. 32473 is converted to 00007ED9. + +- 3) The Version ID is the current Version ID configured in the UCMF. This field is present only if the Type Field is set to 1. Its length is 2 hexadecimal digits. +- 4) Radio Configuration Identifier (RCI): identifies the UE radio configuration. Its length is 11 hexadecimal digits. + +## 30 Identification of 5GS Multicast and Broadcast Services + +### 30.1 Introduction + +This clause describes the format of the parameters needed to access the Multicast and Broadcast Services in 5GS. For further information on the use of the parameters see 3GPP TS 23.247 [140]. + +### 30.2 Structure of TMGI + +Temporary Mobile Group Identity (TMGI) is used within MBS to uniquely identify a broadcast MBS session or a multicast MBS session. + +TMGI is composed as shown in figure 30.2.1. + +![Diagram showing the structure of TMGI, composed of MBS Service ID (6 digits), MCC (3 digits), and MNC (2 or 3 digits).](d21ff621d2cff0d2b4b5a97009b23eb3_img.jpg) + +The diagram illustrates the structure of the Temporary Mobile Group Identity (TMGI). It is shown as a horizontal sequence of three components: 'MBS Service ID', 'MCC', and 'MNC'. Above the 'MBS Service ID' box is a double-headed arrow labeled '6 digits'. Above the 'MCC' box is a double-headed arrow labeled '3 digits'. Above the 'MNC' box is a double-headed arrow labeled '2 or 3 digits'. Below these three boxes, a single long double-headed arrow labeled 'TMGI' spans the entire width, indicating the concatenation of the three parts. + +Diagram showing the structure of TMGI, composed of MBS Service ID (6 digits), MCC (3 digits), and MNC (2 or 3 digits). + +Figure 30.2.1: Structure of TMGI + +The TMGI is composed of three parts: + +- 1) MBS Service ID consisting of three octets. MBS Service ID consists of a 6-digit fixed-length hexadecimal number between 000000 and FFFFFFF. MBS Service ID uniquely identifies an MBS service within a PLMN. +- 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the MB-SMF, except for the MCC value of 901, which does not identify any country and is assigned globally by ITU; +- 3) Mobile Network Code (MNC) consisting of two or three digits (depending on the assignment to the PLMN by its national numbering plan administrator). The MNC identifies the PLMN which the MB-SMF belongs to, except for the MNC value of 56 when the MCC value is 901, which does not identify any PLMN. For more information on the use of the TMGI, see 3GPP TS 23.247 [140]. + +NOTE: The structure of TMGI for MBS in 5GS is similar to the structure of TMGI for MBMS in EPS defined in clause 15.2. + +In a SNPN (Stand-alone Non-Public Network), TMGI is used together with NID (Network Identifier) to identify an MBS Session. + +### 30.3 Structure of Area Session ID + +The concept of Area Session ID is defined in 3GPP TS 23.247 [140]. + +Area Session IDs are used for MBS sessions with location dependent content. An Area Session ID together with an MBS Session ID (i.e. TMGI or Source Specific IP Multicast address) shall uniquely identify an MBS session in a specific MBS Service Area. + +NOTE: For a location-dependent MBS session, the same MBS Session ID but a different Area Session ID are used for each MBS Service Area. Different MB-SMFs and/or MB-UPFs can be assigned for different MBS service areas in an MBS session. + +An Area Session Identity shall be a decimal number between 0 and 65535 (inclusive). + +### 30.4 Structure of MBS Frequency Selection Area ID + +The concept of MBS Frequency Selection Area ID is defined in clause 6.5.4 of 3GPP TS 23.247 [140]. + +The MBS Frequency Selection Area (FSA) ID is used for broadcast MBS session to guide the frequency selection of the UE. + +The MBS FSA ID identifies a preconfigured area within, and in proximity to, which the cell(s) announces the MBS FSA ID and the associating frequency (for details see 3GPP TS 38.300 [141]). MBS FSA ID and their mapping to frequencies are provided to RAN nodes via OAM. + +An MBS FSA ID shall be a string of 6 hexadecimal digits. + +### 30.5 Structure of Associated Session ID + +The concept of Associated Session ID is defined in 3GPP TS 23.247 [140]. + +The Associated Session ID is used to enable NG-RAN to identify the multiple MBS sessions delivering the same content when AF creates multiple broadcast MBS Sessions via different Core Networks in network sharing scenarios. + +An Associated Session ID may comprise a Source Specific IP Multicast Address (SSM) or a string. See clause 5.9.4.21.1 of 3GPP TS 29.571 [129] for the encoding of Associated Session ID in 5GC SBIs. + +--- + +## Annex A (informative): Colour Codes + +### A.1 Utilization of the BSIC + +A BSIC is allocated to each cell. A BSIC can take one of 64 values. In each cell the BSIC is broadcast in each burst sent on the SCH, and is then known by all MSs which synchronise with this cell. The BSIC is used by the MS for several purposes, all aiming at avoiding ambiguity or interference which can arise when an MS in a given position can receive signals from two cells *using the same BCCH frequency*. + +Some of the uses of the BSIC relate to cases where the MS is attached to one of the cells. Other uses relate to cases where the MS is attached to a third cell, usually somewhere between the two cells in question. + +The first category of uses includes: + +- The three least significant bits of the BSIC indicate which of the 8 training sequences is used in the bursts sent on the downlink common channels of the cell. Different training sequences allow for a better transmission if there is interference. The group of the three least significant bits of the BSIC is called the BCC (Base station Colour Code). +- The BSIC is used to modify the bursts sent by the MSs on the access bursts. This aims to avoid one cell correctly decoding access bursts sent to another cell. + +The second category of uses includes: + +- When in connected mode, the MSs measure and report the level they receive on a number of frequencies, corresponding to the BCCH frequencies of neighbouring cells in the same network as the used cell. Along with the measurement result, the MS sends to the network the BSIC which it has received on that frequency. This enables the network to discriminate between several cells which happen to use the same BCCH frequency. Poor discrimination might result in faulty handovers. +- The content of the measurement report messages is limited to information for 6 neighbour cells. It is therefore useful to limit the reported cells to those to which handovers are accepted. For this purpose, each cell provides a list of the values of the three most significant bits of the BSICs which are allocated to the cells which are useful to consider for handovers (usually excluding cells in other PLMNs). This information enables the MS to discard information for cells with non-conformant BSICs and not to report them. The group of the three most significant bits of the BSIC is called the NCC (Network Colour Code). + +It should be noted that when in idle mode, the MS identifies a cell (for cell selection purposes) according to the cell identity broadcast on the BCCH and *not* by the BSIC. + +## A.2 Guidance for planning + +From these uses, the following planning rule can be derived: + +*If there exist places where MSs can receive signals from two cells, whether in the same PLMN or in different PLMNs, which use the same BCCH frequency, it is highly preferable that these two cells have different BSICs.* + +Where the coverage areas of two PLMNs overlap, the rule above is respected if: + +- 1) The PLMNs use different sets of BCCH frequencies (In particular, this is the case if no frequency is common to the two PLMNs. This usually holds for PLMNs in the same country), or +- 2) The PLMNs use different sets of NCCs, or +- 3) BSIC and BCCH frequency planning is co-ordinated. + +Recognizing that method 3) is more cumbersome than method 2), and that method 1) is too constraining, it is suggested that overlapping PLMNs which use a common part of the spectrum agree on different NCCs to be used in any overlapping areas. As an example, a preliminary NCC allocation for countries in the European region can be found in clause A.3 of this annex. + +This example can be used as a basis for bilateral agreements. However, the use of the NCCs allocated in clause A.3 is not compulsory. PLMN operators can agree on different BSIC allocation rules in border areas. The use of BSICs is not constrained in non-overlapping areas, or if ambiguities are resolved by using different sets of BCCH frequencies. + +If the PLMNs share one or more cells with other PLMNs, the planning rule above should be applied also when the BCCH frequency is different. The rule should be respected by using different sets of NCCs. In addition to that, the PLMN sharing one or more cells with other PLMNs should use different NCCs for shared and non-shared neighbouring cells. + +## A.3 Example of PLMN Colour Codes (NCCs) for the European region + +Austria : 0 + +| | | | +|---------------|---|-------------------------| +| Belgium | : | 1 | +| Cyprus | : | 3 | +| Denmark | : | 1 | +| Finland | : | 0 | +| France | : | 0 | +| Germany | : | 3 | +| Greece | : | 0 | +| Iceland | : | 0 | +| Ireland | : | 3 | +| Italy | : | 2 | +| Liechtenstein | : | 2 | +| Luxembourg | : | 2 | +| Malta | : | 1 | +| Monaco | : | 3 (possibly 0(=France)) | +| Netherlands | : | 0 | +| Norway | : | 3 | +| Portugal | : | 3 | +| San Marino | : | 0 (possibly 2(= Italy)) | +| Spain | : | 1 | +| Sweden | : | 2 | +| Switzerland | : | 1 | +| Turkey | : | 2 | +| UK | : | 2 | +| Vatican | : | 1 (possibly 2(=Italy)) | +| Yugoslavia | : | 3 | + +This allows a second operator for each country by allocating the colour codes $n$ (in the table) and $n + 4$ . More than 2 colour codes per country may be used provided that in border areas only the values $n$ and/or $n+4$ are used. + +## Annex B (normative): IMEI Check Digit computation + +### B.1 Representation of IMEI + +The International Mobile station Equipment Identity and Software Version number (IMEISV), as defined in clause 6, is a 16 digit decimal number composed of three distinct elements: + +- an 8 digit Type Allocation Code (TAC); +- a 6 digit Serial Number (SNR); and +- a 2 digit Software Version Number (SVN). + +The IMEISV is formed by concatenating these three elements as illustrated below: + +| | | | +|-----|-----|-----| +| TAC | SNR | SVN | +|-----|-----|-----| + +**Figure A.1: Composition of the IMEISV** + +The IMEI is complemented by a check digit as defined in clause 3. The Luhn Check Digit (CD) is computed on the 14 most significant digits of the IMEISV, that is on the value obtained by ignoring the SVN digits. + +The method for computing the Luhn check is defined in Annex B of the International Standard "Identification cards - Numbering system and registration procedure for issuer identifiers" (ISO/IEC 7812 [3]). + +In order to specify precisely how the CD is computed for the IMEI, it is necessary to label the individual digits of the IMEISV, excluding the SVN. This is done as follows: + +The (14 most significant) digits of the IMEISV are labelled D14, D13 ... D1, where: + +- TAC = D14, D13 ... D7 (with D7 the least significant digit of TAC); +- SNR = D6, D5 ... D1 (with D1 the least significant digit of SNR). + +### B.2 Computation of CD for an IMEI + +Computation of CD from the IMEI proceeds as follows: + +Step 1: Double the values of the odd labelled digits D1, D3, D5 ... D13 of the IMEI. + +Step 2: Add together the individual digits of all the seven numbers obtained in Step 1, and then add this sum to the sum of all the even labelled digits D2, D4, D6 ... D14 of the IMEI. + +Step 3: If the number obtained in Step 2 ends in 0, then set CD to be 0. If the number obtained in Step 2 does not end in 0, then set CD to be that number subtracted from the next higher number which does end in 0. + +### B.3 Example of computation + +**IMEI (14 most significant digits):** + +| TAC | | | | | | | | SNR | | | | | | +|-----|-----|-----|-----|-----|----|----|----|-----|----|----|----|----|----| +| D14 | D13 | D12 | D11 | D10 | D9 | D8 | D7 | D6 | D5 | D4 | D3 | D2 | D1 | +| 2 | 6 | 0 | 5 | 3 | 1 | 7 | 9 | 3 | 1 | 1 | 3 | 8 | 3 | + +**Step 1:** + +| | | | | | | | | | | | | | | +|----|----|----|----|---|---|---|---|----|----|----|---|---|---| +| 2 | 6 | 0 | 5 | 3 | 1 | 7 | 9 | 3 | 1 | 1 | 3 | 8 | 3 | +| x2 | x2 | x2 | x2 | | | | | x2 | x2 | x2 | | | | +| 12 | 10 | 2 | 18 | | | | | 2 | 6 | 6 | | | | + +**Step 2:** + +$$2 + 1 + 2 + 0 + 1 + 0 + 3 + 2 + 7 + 1 + 8 + 3 + 2 + 1 + 6 + 8 + 6 = 53$$ + +**Step 3:** + +$$CD = 60 - 53 = 7$$ + +--- + +## Annex C (normative): Naming convention + +This normative annex defines a naming convention which will make it possible for DNS servers to translate logical names for GSNs and RAs to physical IP addresses. The use of logical names is optional, but if the option is used, it shall comply with the naming convention described in this annex. The fully qualified domain names used throughout this annex shall follow the general encoding rules specified in clause 19.4.2.1. + +--- + +### C.1 Routing Area Identities + +This clause describes a possible way to support inter-PLMN roaming. + +When an MS roams between two SGSNs within the same PLMN, the new SGSN finds the address of the old SGSN from the identity of the old RA. Thus, each SGSN can determine the address of every other SGSN in the PLMN. + +When an MS roams from an SGSN in one PLMN to an SGSN in another PLMN, the new SGSN may be unable to determine the address of the old SGSN. Instead, the SGSN transforms the old RA information to a logical name of the form: + +*racAAAA.lacBBBB.mncYYY.mccZZZ.gprs* + +A and B shall be Hex coded digits; Y and Z shall be encoded as single digits (in the range 0-9). + +If there are less than 4 significant digits in AAAA or BBBB, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. + +As an example, the logical name for RAC 123A, LAC 234B, MCC 167 and MNC 92 will be coded in the DNS server as: + +*rac123A.lac234B.mnc092.mcc167.gprs.* + +The SGSN may then acquire the IP address of the old SGSN from a DNS server, using the logical address. Introducing the DNS concept in GPRS enables operators to use logical names instead of IP addresses when referring to nodes (e.g. GSNs), thus providing flexibility and transparency in addressing. Each PLMN should include at least one DNS server (which may optionally be connected via the DNS service provided by the GSM Association). Note that these DNS servers are GPRS internal entities, unknown outside the GPRS system. + +The above implies that at least MCC || MNC || LAC || RAC (= RAI) is sent as the RA parameter over the radio interface when an MS roams to another RA. + +If for any reason the new SGSN fails to obtain the address of the old SGSN, the new SGSN takes the same actions as when the corresponding event occurs within one PLMN. + +Another way to support seamless inter-PLMN roaming is to store the SGSN IP addresses in the HLR and request them when necessary. + +If Intra Domain Connection of RAN Nodes to Multiple CN Nodes (see 3GPP TS 23.236 [23]) is applied then the Network Resource Identifier (NRI) identifies uniquely a given SGSN node out of all the SGSNs serving the same pool area. + +If the new SGSN is not able to extract the NRI from the old P-TMSI, it shall retrieve the address of the default SGSN (see 3GPP TS 23.236 [23]) serving the old RA, using the logical name described earlier in this clause. The default SGSN in the old RA relays the GTP signalling to the old SGSN identified by the NRI in the old P-TMSI unless the default SGSN itself is the old SGSN. + +If the new SGSN is able to extract the NRI from the old P-TMSI, then it shall attempt to derive the address of the old SGSN from the NRI and the old RAI. NRI-to-SGSN assignments may be either configured (by O&M) in the new SGSN, or retrieved from a DNS server. If a DNS server is used, it shall be queried using the following logical name, derived from the old RAI and NRI information: + +*nriCCCC.racDDDD.lacEEEE.mncYYY.mccZZZ.gprs* + +C, D and E shall be Hex coded digits, Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in CCCC, DDDD or EEEE, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digits coding. + +As an example, the logical name for NRI 3A, RAC 123A, LAC 234B, MCC 167 and MNC 92 will be coded in the DNS server as: + +*nri003A.rac123A.lac234B.mnc092.mcc167.gprs.* + +If for any reason the new SGSN fails to obtain the address of the old SGSN using this method, then as a fallback method it shall retrieve the address of the default SGSN serving the old RA. + +## C.2 GPRS Support Nodes + +This clause defines a naming convention for GSNs. + +It shall be possible to refer to a GSN by a logical name which shall then be translated into a physical IP address. This clause proposes a GSN naming convention which would make it possible for an internal GPRS DNS server to make the translation. + +An example of how a logical name of an SGSN could appear is: + +*sgsnXXXX.mncYYY.mccZZZ.gprs* + +X, shall be Hex coded digits, Y and Z shall be encoded as single digits (in the range 0-9). + +If there are less than 4 significant digits in XXXX one or more "0" digit(s) is/are inserted at the left side to fill the 4 digits coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. + +As an example, the logical name for SGSN 1B34, MCC 167 and MNC 92 will be coded in the DNS server as: + +*sgsn1B34.mnc092.mcc167.gprs* + +## C.3 Target ID + +This clause describes a possible way to support SRNS relocation. + +In UMTS, when SRNS relocation is executed, a target ID which consists of MCC, MNC and RNC ID is used as routing information to route to the target RNC via the new SGSN. An old SGSN shall resolve a new SGSN IP address by a target ID to send the Forward Relocation Request message to the new SGSN. + +It shall be possible to refer to a target ID by a logical name which shall be translated into an SGSN IP address to take into account inter-PLMN handover. The old SGSN transforms the target ID information into a logical name of the form: + +*rncXXXX.mncYYY.mccZZZ.gprs* + +X shall be Hex coded digits; Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in XXXX, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digits coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. Then, for example, a DNS server is used to translate the logical name to an SGSN IP address. + +As an example, the logical name for RNC 1B34, MCC 167 and MNC 92 will be coded in the DNS server as: + +*rnc1B34.mnc092.mcc167.gprs* + +--- + +## Annex D (informative): Applicability and use of the ".3gppnetwork.org" domain name + +There currently exists a private IP network between operators to provide connectivity for user transparent services that utilise protocols that rely on IP. This includes (but is not necessarily limited to) such services as GPRS/PS roaming, WLAN roaming, GPRS/PS inter-PLMN handover and inter-MMSC MM delivery. This inter-PLMN IP backbone network consists of indirect connections using brokers (known as GRXs – GPRS Roaming Exchanges) and direct inter-PLMN connections (e.g. private wire); it is however *not* connected to the Internet. More details can be found in GSMA PRD IR.34 [57]. + +Within this inter-PLMN IP backbone network, the domain name ".gprs" was originally conceived as the only domain name to be used to enable DNS servers to translate logical names for network nodes to IP addresses (and vice versa). However, after feedback from the Internet Engineering Task Force (IETF) it was identified that use of this domain name has the following drawbacks: + +1. Leakage of DNS requests for the ".gprs" top level domain into the public Internet is inevitable at sometime or other, especially as the number of services (and therefore number of nodes) using the inter-PLMN IP backbone increases. In the worst case scenario of faulty clients, the performance of the Internet's root DNS servers would be seriously degraded by having to process requests for a top level domain that does not exist. +2. It would be very difficult for network operators to detect if/when DNS requests for the ".gprs" domain were leaked to the public Internet (and therefore the security policies of the inter-PLMN IP backbone network were breached), because the Internet's root DNS servers would simply return an error message to the sender of the request only. + +To address the above, the IETF recommended using a domain name that is *routable* in the public domain but which requests to it are not actually *serviced* in the public domain. The domain name ".3gppnetwork.org" was chosen as the new top level domain name to be used (as far as possible) within the inter-PLMN IP backbone network. + +Originally, only the DNS servers connected to the inter-PLMN IP backbone network were populated with the correct information needed to service requests for *all* sub-domains of this domain. However, it was later identified that some new services needed their allocated sub-domain(s) to be resolvable by the UE and not just inter-PLMN IP network nodes. To address this, additional, higher-level sub-domains were created: + +- "pub.3gppnetwork.org", which is to be used for domain names that need to be resolvable by UEs (and possibly network nodes too) that are connected to a local area network that is connected to the Internet; and +- "ipxuni.3gppnetwork.org", which is to be used for domain names for UNI interfaces that need to be resolvable by UEs that are connected to a local area network that is not connected to the Internet (e.g. local area networks connected to the inter-PLMN IP network of the IPX). + +Therefore, DNS requests for the above domain names can be resolved, while requests for all other sub-domains of "3gppnetwork.org" can simply be configured to return the usual DNS error for unknown hosts (thereby avoiding potential extra, redundant load on the Internet's root DNS servers). + +The GSM Association is in charge of allocating new sub-domains of the ".3gppnetwork.org" domain name. The procedure for requesting new sub-domains can be found in Annex E. + +## Annex E (normative): Procedure for sub-domain allocation + +When a 3GPP member company identifies the need for a new sub-domain name of ".3gppnetwork.org", that 3GPP member company shall propose a CR to this specification at the earliest available meeting of the responsible working group for this TS. The CR shall propose a new sub-domain name. The new sub-domain proposed shall be formatted in one of the formats as described in the following table. + +| Sub-domain Format | Intended Usage | +|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| .mnc.mcc.3gppnetwork.org
(see notes 1 and 2) | Domain name that is to be resolvable by network nodes only. This format inherently adds protection to the identified node, in that attempted DNS resolutions instigated directly from end user equipment will fail indefinitely. | +| .mnc.mcc.pub.3gppnetwork.org
(see notes 1 and 2) | Domain name that is to be resolvable by UEs and/or network nodes. This format inherently adds global resolution capability, but at the expense of confidentiality of network topology. | +| .mnc.mcc.ipxuni.3gppnetwork.org
(see notes 1 and 2) | Domain name for UNI interface that is to be resolvable by UEs that are connected to an inter-PLMN IP network that has no connectivity to the Internet.
This format inherently adds resolution capability for UEs in closed IP networks e.g. IPX. | +| .mcc.visited-country.pub.3gppnetwork.org
(see notes 1 and 2) | Domain name in the visited country that is to be resolvable by UEs and/or network nodes, which is not specific to an individual operator. | +| .nid.mnc.mcc.3gppnetwork.org
(see notes 1 and 3) | Domain name of a Stand-alone non-public network that is to be resolvable by network nodes only. This format inherently adds protection to the identified node, in that attempted DNS resolutions instigated directly from end user equipment will fail indefinitely. | + +**Table E.1: Sub-domain formats for the "3gppnetwork.org" domain and their respective intended usage** + +NOTE 1: "" is a chosen label, conformant to DNS naming conventions (usually IETF RFC 1035 [19] and IETF RFC 1123 [20]) that clearly and succinctly describe the service and/or operation that is intended to use this sub-domain. + +NOTE 2: "" and "" are the MNC (padded to the left with a zero, if only a 2-digit MNC) and MCC of a PLMN. + +NOTE 3: "NID", "" and "" are the NID (hexadecimal digits as specified in clause 12.7), MNC (padded to the left with a zero, if only a 2-digit MNC) and MCC identifying a Stand-alone Non-Public Network (SNPN). + +Care should be taken when choosing which format a domain name should use. Once a format has been chosen, the responsible working group shall then check the CR and either endorse it or reject it. If the CR is endorsed, then the responsible working group shall send an LS to the GSMA NG with TSG-CT in copy. The LS shall describe the following key points: + +- the context +- the service +- intended use +- involved actors +- proposed new sub-domain name + +GSMA NG will then verify the consistence of the proposal and its usage within the domain's structure and interworking rules (e.g. access to the GRX/IPX Root DNS servers). GSMA NG will then endorse or reject the proposal and inform the responsible working group (in 3GPP) and also TSG CT. It is possible that GSMA NG will also specify, changes to the newly proposed sub-domain name (e.g. due to requested sub-domain name already allocated). + +NOTE 4: There is no need to request GSMA NG for new labels to the left of an already GSMA NG approved "". It is the responsibility of the responsible working group to ensure uniqueness of such new labels. + +It should be noted that services already defined to use the ".gprs" domain name will continue to do so and shall not use the new domain name of ".3gppnetwork.org"; this is to avoid destabilising services that are already live. + +## Annex F (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New version | +|----------|---------------|----------|-------|-----|-----|------------------------------------------------------------------------------------------|-------------| +| Apr 1999 | GSM 03
.03 | | | | | Transferred to 3GPP CN1 | | +| CN#03 | 23.003 | | | | | Approved at CN#03 | 3.0.0 | +| CN#04 | 23.003 | | 001 | | | Definition of escape PLMN code | 3.1.0 | +| CN#04 | 23.003 | | 002r1 | | | SSN reallocation for CAP, gsmSCF, SIWF, GGSN, SGSN, | 3.1.0 | +| CN#04 | 23.003 | | 003 | | | Correction of VGC/VBC reference | 3.1.0 | +| CN#04 | 23.003 | | 004 | | | Harmonisation of the MNC-length; correction of CR A019r1 | 3.1.0 | +| CN#04 | 23.003 | | 005 | | | Correction to the MNC length | 3.1.0 | +| CN#05 | 23.003 | | 007r1 | | | ASCII coding of and in APN OI | 3.2.0 | +| CN#05 | 23.003 | | 008 | | | New SSN allocation for RANAP and RNSAP | 3.2.0 | +| CN#06 | 23.003 | | 011 | | | Support of VLR and HLR Data Restoration procedures with LCS | 3.3.0 | +| CN#07 | 23.003 | | 014 | | | Necessity of the function of the calculation of an SGSN IP address from the target ID | 3.4.0 | +| CN#07 | 23.003 | | 016 | | | Definition of Service Area Identification | 3.4.0 | +| CN#07 | 23.003 | | 017r2 | | | Modification of clause 6.2 to enhance IMEI security | 3.4.0 | +| CN#07 | 23.003 | | 018 | | | Coding of a deleted P-TMSI signature | 3.4.0 | +| CN#07 | 23.003 | | 013r2 | | | Introduction of Reserved Service Labels in the APN | 3.4.1 | +| CN#08 | 23.003 | | 019 | | | Missing UTRAN identifiers | 3.5.0 | +| CN#08 | 23.003 | | 021r1 | | | Editorial Modification of clause 6.2.2. | 3.5.0 | +| CN#08 | 23.003 | | 022 | | | IMEI Formats and Encoding | 3.5.0 | +| CN#09 | 23.003 | | 023 | | | Alignment of 23.003 with text from 25.401 | 3.6.0 | +| CN#10 | 23.003 | | 024 | | | Moving informative Annex A from 3G TS 29.060 and making it normative. | 3.7.0 | +| CN#11 | 23.003 | | 025 | | | Clarification to Definition of Service Area Identifier | 3.8.0 | +| CN#11 | 23.003 | | 026 | | | Forbidden APN network identifier labels | 3.8.0 | +| CN#11 | 23.003 | | | | | Updated from R99 to Rel-4 after CN#11 | 4.0.0 | +| CN#12 | 23.003 | | 028r1 | | | Remove reference to TS23.022 | 4.1.0 | +| CN#12 | 23.003 | | 029r1 | | | New Subsystem Number for the Position Calculation Application Part on the lupc interface | 5.0.0 | +| CN#13 | 23.003 | | 032 | | | Clarification on APN labels that begin with a digit | 5.1.0 | +| CN#13 | 23.003 | | | | | Editorial clean up | 5.1.0 | +| CN#14 | 23.003 | | 033 | | | Rules for TMSI partitioning | 5.2.0 | +| CN#14 | 23.003 | | 035 | | | Introduction of Global CN-ID definition | 5.2.0 | +| CN#16 | 23.003 | | 037r1 | | | luFlex support for determining old SGSN during handover/relocation | 5.3.0 | +| CN#16 | 23.003 | | 038 | | | Allocation of unique prefixes to IPv6 terminals | 5.3.0 | +| CN#16 | 23.003 | | 041r2 | | | Use of a temporary public user identity | 5.3.0 | +| CN#16 | 23.003 | | 044 | | | Restructuring the IMEI to combine the TAC and FAC | 5.3.0 | +| CN#16 | 23.003 | | 045 | | | Use of the TLLI codespace in GERAN lu mode | 5.3.0 | +| CN#17 | 23.003 | | 048r3 | | | Clarification on the definition of DNS | 5.4.0 | +| CN#17 | 23.003 | | 050r1 | | | Support for Shared Network in connected mode: definition of SNA | 5.4.0 | +| CN#17 | 23.003 | | 053r1 | | | Restructuring the IMEI to combine the TAC and FAC in Annex B | 5.4.0 | +| CN#17 | 23.003 | | 054 | | | SCCP sub-system Number for IM-SSF | 5.4.0 | +| CN#18 | 23.003 | | 055r1 | | | Iur-g Introduction | 5.5.0 | +| CN#18 | 23.003 | | 056r2 | | | Editorial clean-up | 5.5.0 | +| CN#18 | 23.003 | | 057 | | | Correction of the private user identity's form | 5.5.0 | +| CN#18 | 23.003 | | 058 | | | Addition of a reference to the ITU-T RECOMMENDATION E.212 for Mobile Country Codes | 5.5.0 | +| CN#18 | 23.003 | | 059 | | | Correction to the form of public user identity | 5.5.0 | +| CN#18 | 23.003 | | 062 | | | Fix miss-interworking for LMSI handling (LMSI definition) | 5.5.0 | +| CN#18 | 23.003 | | | | | Corrupted figures 13 – 18 fixed | 5.5.1 | + +| | | | | | | | | +|-------|--------|--|--------|--|--|-----------------------------------------------------------------------------------|--------| +| CN#20 | 23.003 | | 065 | | | Correction to Annex C.3 – Target ID | 5.6.0 | +| CN#21 | 23.003 | | 072 | | | Correction to definition of Group-ID, Group call area ID and Group Call Reference | 5.7.0 | +| CN#21 | 23.003 | | 073r2 | | | PSI definition | 6.0.0 | +| CN#22 | 23.003 | | 078 | | | On the length of the APN NI | 6.1.0 | +| CN#23 | 23.003 | | 081 | | | Changes and corrections to DNS names | 6.2.0 | +| CN#23 | 23.003 | | 083r2 | | | Changes to enable the GSMA root DNS architecture using ".3gppnetwork.org" TLD | 6.2.0 | +| CN#23 | 23.003 | | 085r1 | | | WLAN access parameters moved from TS 24.234 to TS 23.003 | 6.2.0 | +| CN#23 | 23.003 | | 087 | | | Assignment of SSN for Presence Network Agent | 6.2.0 | +| CN#24 | 23.003 | | 086r4 | | | Clarification of the uses of SIP URIs for Public User ID | 6.3.0 | +| CN#24 | 23.003 | | 088r1 | | | Addition of TMGI | 6.3.0 | +| CN#25 | 23.003 | | 089 | | | Background of and procedures for the ".3gppnetwork.org" domain name | 6.4.0 | +| CN#25 | 23.003 | | 090r2 | | | Decorated NAI format | 6.4.0 | +| CN#25 | 23.003 | | 091r1 | | | Introduction of temporary identities | 6.4.0 | +| CN#26 | 23.003 | | 092r2 | | | 'otherrealm' format of Decorated NAI | 6.5.0 | +| CN#26 | 23.003 | | 095r1 | | | Clarification of NRI position within (P)-TMSI | 6.5.0 | +| CN#26 | 23.003 | | 096r1 | | | BSF address | 6.5.0 | +| CN#27 | 23.003 | | 097 | | | Clarification of the TMGI | 6.6.0 | +| CN#27 | 23.003 | | 093r3 | | | Definition of Alternative NAI | 6.6.0 | +| CT#28 | 23.003 | | 0099r4 | | | W-APN Definition | 6.7.0 | +| CT#28 | 23.003 | | 0100r5 | | | Correction to wildcards in PSI | 6.7.0 | +| | | | | | | 2005-07: Correct line break before clause 14 header | 6.7.1 | +| CT#29 | 23.003 | | 0102r2 | | | Corrections to "3gppnetwork.org" addressing | 6.8.0 | +| CT#29 | 23.003 | | 0103 | | | Addition of addressing for the Generic Access Network | 6.8.0 | +| CT#29 | 23.003 | | 0104r1 | | | PSI routing | 6.8.0 | +| CT#31 | 23.003 | | 0106r1 | | | IETF references update | 6.9.0 | +| CT#32 | 23.003 | | 0107r1 | | | Fast re-authentication identity clarification | 6.10.0 | +| CT#32 | 23.003 | | 0109r1 | | | Case insensitive naming convention | 6.10.0 | +| | | | 0111r1 | | | Correction to the W-APN definition | | +| CT#32 | 23.003 | | 0112r1 | | | Definition of Anonymous URI in IMS | 7.0.0 | +| CT#33 | 23.003 | | 0117r1 | | | Re-authentication identity definition correction | 7.1.0 | +| | | | 0115r3 | | | Definition of MBMS SAI | | +| CT#34 | 23.003 | | 0118 | | | Voice Call Continuity Identification and Addressing | 7.2.0 | +| | | | 0119r2 | | | Unavailable User Identity | | +| | | | 0120 | | | Emergency Realm for I-WLAN network advertisement | | +| | | | 0121 | | | Definition of emergency W-APN | | +| | | | 0122r2 | | | Format of emergency public identity | | +| CT#35 | 23.003 | | 0128r2 | | | Definition of Private Service identity | 7.3.0 | +| | | | 0126r2 | | | Definition of emergency APN for IMS em-calls | | +| | | | 0129r2 | | | Clarification to TMGI definition | | +| CT#36 | 23.003 | | 0131r2 | | | Correction of derivation of identifiers, by the UE, using the IMSI | 7.4.0 | +| CT#37 | 23.003 | | 0134r1 | | | Home realm construction for MBMS roaming | 7.5.0 | +| | | | 0135r2 | | | PSI clarification | | +| | | | 0136 | | | Remove emergency APN | | +| CT#38 | 23.003 | | 0138 | | | Correction to text describing W-APN format | 7.6.0 | +| CT#39 | 23.003 | | 0141r1 | | | Structure of TMGI | 7.7.0 | +| CT#39 | 23.003 | | 0140 | | | Wildcarded Public User Identities format | 8.0.0 | +| CT#40 | 23.003 | | 0142r2 | | | IMS public and private identity derivation in 3GPP2 | 8.1.0 | +| | | | 0144 | | | Minor corrections to the IMS clause | | +| | | | 0146r2 | | | NAI for 3GPP access to Non-3GPP Access Interworking | | +| | | | 0143r2 | | | Addition of IMS Centralized Services related identities | | +| CT#41 | 23.003 | | 0150 | | | Emergency Public User Identity Removal | 8.2.0 | +| | | | 0152r3 | | | Introduction of IMC in support of common IMS | | +| | | | 0153r1 | | | Introduction of STN-SR | | +| | | | 0154r1 | | | Addition and correction of DNS related identifiers for EPC | | +| | | | 0155r1 | | | Definition of Globally Unique Temporary UE Identity | | +| | | | 0156 | | | Reference correction | | +| | | | 0158r1 | | | Addition of Conference Factory URI for IMS Centralized | | + +| | | | | | | | | +|-------|--------|--|--------|--|--|---------------------------------------------------------------------------------------|--------| +| | | | | | | Services | | +| | | | 0159r1 | | | Naming for HA discovery HA-APN | | +| | | | 0160r2 | | | Definition and format of access network identifier | | +| CT#42 | 23.003 | | 0161 | | | SGSN related FQDNs | 8.3.0 | +| | | | 0162 | | | New "nodes" subdomain for EPC | | +| | | | 0165 | | | Clarify the mapping between M-TMSI and P-TMSI | | +| | | | 0166 | | | Revising the GUTI Definition | | +| | | | 0163r4 | | | Closed Subscriber Group | | +| | | | 0167r1 | | | Adding the S-TMSI Definition | | +| | | | 0168r1 | | | Definition of instance Id | | +| | | | 0169 | | | STN-SR in SGSN | | +| CT#43 | 23.003 | | 0170 | | | Correction to NAI format | 8.4.0 | +| | | | 0172 | | | Missing service identifiers for DNS procedures | | +| | | | 0174 | | | Correction of the GUTI format | | +| | | | 0176r1 | | | Correction of the GUTI P-TMSI mapping | | +| | | | 0177 | | | Corrections to Service Continuity addressing | | +| | | | 0178r1 | | | Support of EAP-AKA' | | +| | | | 0179r2 | | | Naming for ANDSF discovery | | +| | | | 0180r1 | | | ePDG naming | | +| | | | 0181r2 | | | Clarification about canonical form of IMS Public User Identity when format is TEL URL | | +| | | | 0182 | | | Temporary Identity Tag Values for Fast Re-authentication Ids | | +| | | | 0187r2 | | | DNS-APN-OI | | +| CT#44 | 23.003 | | 0189r1 | | | HNB Name Definition | 8.5.0 | +| | | | 0190r1 | | | Clarification on TAI FQDN | | +| | | | 0191 | | | Service Parameters for S2c | | +| | | | 0193r2 | | | Reference update for draft-montemurro-gsma-imei-urn | | +| CT#45 | 23.003 | | 0194r1 | | | Public User Identity definition in TS 23.003 | 8.6.0 | +| | | | 0197r1 | | | Inclusion of CSG Type | | +| CT#45 | 23.003 | | 0199r1 | | | IMEI Based NAI definitions for emergency services | 9.0.0 | +| CT#46 | 23.003 | | 0200r1 | | | IMEI based NAI | 9.1.0 | +| | | | 0205r4 | | | IMEI Based NAI | | +| | | | 0210r1 | | | Reintroducing Emergency APN definition for IMS based Emergency Call | | +| | | | 0212r1 | | | Clarification for the format of ANDSF-SN in roaming scenario | | +| | | | 0215 | | | Tracking Area Code | | +| | | | 0217 | | | E-UTRAN Cell Global Identification definition | | +| CT#47 | 23.003 | | 0213r4 | | | Defining H(e)NB identity | 9.2.0 | +| | | | 0219r2 | | | Exclude prepended digit from the NAI in PMIPv6 | | +| | | | 0221r2 | | | APN-FQDN construction | | +| | | | 0223 | | | Corrections to APN structure | | +| | | | 0225r1 | | | Correction on Home Network Realm/Domain | | +| | | | 0227 | | | Corrections to IMS Public Identity | | +| CT#48 | 23.003 | | 0229r1 | | | Removal of the redundancy reference to 23.401 | 9.3.0 | +| | | | 0232r1 | | | IMEI and IMEISV | | +| | | | 0235r1 | | | Remove ambiguities and improved definition of HNB Unique Identity | | +| | | | 0237r2 | | | Essential corrections to GUTI mapping | | +| CT#49 | 23.003 | | 0242r1 | | | PSI use for services hosted in an AS | 9.4.0 | +| | | | 0246r3 | | | Essential corrections to GUTI mapping | | +| | | | 0247r2 | | | Use of NRI | | +| | | | 0256 | | | Format of the Unavailable User Identity | | +| | | | 0257 | | | Clarification of UE behaviour with regards to LAC format | | +| CT#50 | 23.003 | | 0252r2 | | | Correction of C-MSISDN definition | 9.5.0 | +| | | | 0265 | | | Updating IMEI URN draft reference | | +| | | | 0268r1 | | | Determination of type of source node during TAU/RAU | | +| CT#50 | 23.003 | | 0258r3 | | | eNodeB-ID FQDN for DNS procedures | 10.0.0 | +| | | | 0269r1 | | | Determination of type of source node during TAU/RAU | | +| | | | 0259 | | | Service Parameter on PGW selection for GTP based S2b | | +| CT#51 | 23.003 | | 0274r3 | | | Relay Node OAM system identification | 10.1.0 | + +| | | | | | | | | +|---------|--------|--|--------|--|--|-------------------------------------------------------------------|--------| +| | | | 0279r3 | | | Correction of C-MSISDN definition | | +| | | | 0277r1 | | | Determination of type of source node during TAU/RAU | | +| | | | 0285 | | | Correction to a reference of an outdated IETF draft to an RFC | | +| | | | 0280r2 | | | Correction to the reserved values for Tracking Area Code (TAC) | | +| | | | 0286 | | | DNS Service Support For Sv | | +| | | | 0289 | | | Clarification of decoding of NRI | | +| CT#52 | 23.003 | | 0290 | | | Closed Subscriber Group clarification | 10.2.0 | +| | | | 0293r2 | | | UE moving from E-UTRAN to GERAN | | +| | | | 0294r2 | | | XCAP Addressing | | +| | | | 0296r1 | | | APN Network Identifier | | +| | | | 0299 | | | Updating IMEI URN draft reference | | +| CT#53 | 23.003 | | 0307 | | | Updating IMEI URN draft reference | 10.3.0 | +| | | | 0282r4 | | | Format of Public User Identities and SIP/TEL URI | | +| | | | 0303r3 | | | Emergency NAI for UICC-less Terminal | | +| CT#54 | 23.003 | | 0316r1 | | | Definition of Distinct Public User Identity | 10.4.0 | +| | | | 0309r1 | | | Emergency NAI for UICC-less Terminal | | +| CT#54 | 23.003 | | 0308r2 | | | APN Operator Identifier for local breakout | 11.0.0 | +| | | | 0312r2 | | | Definition of STI-rSR | | +| CT#55 | 23.003 | | 0334 | | | BSF address correction | 11.1.0 | +| | | | 0322r2 | | | Correction to domain name for XCAP Root URI | | +| | | | 0325 | | | Updating IMEI URN draft reference | | +| | | | 0317r2 | | | Clarification of GUTI mapping | | +| | | | 0318 | | | Service Parameter on PGW selection for GTP based S2a | | +| CT#56 | 23.003 | | 0320r6 | | | MTC External Identifier | 11.2.0 | +| | | | 0337r1 | | | New Service Parameters for CS to PS SRVCC | | +| | | | 0319r5 | | | Definition of A-MSISDN | | +| | | | 0335r2 | | | MME Number for SMS in MME | | +| | | | 0311r7 | | | SSN Reallocation for CSS and its Number Definition | | +| CT#57 | 23.003 | | 0338r1 | | | External Identifier definition | 11.3.0 | +| | | | 0339r1 | | | PS only subscription w/o MSISDN | | +| | | | 0340r1 | | | NCC allocation in a shared network | | +| | | | 0342r1 | | | MSB in the GUTI and P-TMSI mapping | | +| | | | 0345r2 | | | Clarification to MME FQDN | | +| CT#58 | 23.003 | | 0347 | | | Clarification on the use of APN Operator Identifier | 11.4.0 | +| | | | 0348r1 | | | PS only subscription without MSISDN | | +| | | | 0352r1 | | | Updating IMEI URN draft reference | | +| CT#59 | 23.003 | | 0346r5 | | | MME FQDN Clarification | 11.5.0 | +| CT#61 | 23.003 | | 0358 | | | Updating IMEI URN draft reference | 11.6.0 | +| | | | 0361r1 | | | MBMS SAI Definition Correction for LTE Access | | +| | | | 0363r2 | | | NRI and MMEC coordination | | +| CT#61 | 23.003 | | 0362r2 | | | SIPTO permission for Local Network LHN ID definition | 12.0.0 | +| | | | 0364 | | | GERAN Iu Mode | 12.0.0 | +| CT#62 | 23.003 | | 0370 | | | Updating IMEI URN draft reference | 12.1.0 | +| | | | 0365r3 | | | Multi-Vendor eNB Plug and Play | 12.1.0 | +| CT#63 | 23.003 | | 0379 | | | Updating IMEI URN draft reference | 12.2.0 | +| | | | 0371r2 | | | Update of working procedures with GSMA IREG | 12.2.0 | +| | | | 0372r1 | | | TWAN Operator Name | 12.2.0 | +| CT#64 | 23.003 | | 0381r4 | | | Addition of ProSe Application ID format | 12.3.0 | +| | | | 0382r5 | | | Addition of ProSe Application Code format | 12.3.0 | +| | | | 0383r1 | | | Correct definition of Decorated NAI for Evolved Packet Core (EPC) | 12.3.0 | +| | | | 0384r1 | | | Definition of Alternative NAI for Evolved Packet Core (EPC) | 12.3.0 | +| | | | 0386r6 | | | Conference Factory URI for IMS | 12.3.0 | +| 07-2014 | 23.003 | | | | | Clause 19.3.7 title corrected | 12.3.1 | +| CT#65 | 23.003 | | 0391 | | | Updating IMEI URN draft reference to RFC 7254 | 12.4.0 | +| | | | 0392r2 | | | Identification of the HSS | 12.4.0 | +| | | | 0393r2 | | | Update of ProSe Application Code format | 12.4.0 | +| | | | 0394 | | | IMSI based Decorated NAI | 12.4.0 | +| 10-2014 | 23.003 | | | | | Clause number 10.2.2 added. | 12.4.1 | +| CT#66 | 23.003 | | 0398r1 | | | Clarification of NAI handling | 12.5.0 | + +| | | | | | | | | +|---------|--------|-----------|--------|---|--|-------------------------------------------------------------------------------------|--------| +| | | | 0399r2 | | | Maintenance of I-WLAN requirements | 12.5.0 | +| | | | 0402 | | | Addressing and Identifications for Bootstrapping MBMS Service Announcement | 12.5.0 | +| | | | 0401r1 | | | Definition for EPC Prose User ID | 12.5.0 | +| | | | 0403r1 | | | Prose Application ID Name description | 12.5.0 | +| CT#66 | 23.003 | | 0396r3 | | | Defining app protocol name for Nq and Nq' | 13.0.0 | +| CT#67 | 23.003 | | 0409r2 | | | Extension of decorated NAI | 13.1.0 | +| | | | 0414 | | | Definition of Vendor ID | 13.1.0 | +| | | | 0413r2 | | | Clarification in the definition of the ProSe Application Code | 13.1.0 | +| CT#68 | 23.003 | | 0412r6 | | | Clarification of Root NAI and Decorated NAI | 13.2.0 | +| | | | 0416r1 | | | Correction of examples for the Fast-Reauth NAI | 13.2.0 | +| | | | 0417r1 | | | Domain name starting by a digit | 13.2.0 | +| CT#69 | 23.003 | | 0420 | | | Removal of Editor's Note about ProSe Application Code Length | 13.3.0 | +| | | | 0418r3 | | | Definition of IMSI-Group Identifier | 13.3.0 | +| | | | 0421r1 | | | FQDN format for ProSe Function | 13.3.0 | +| CT#70 | 23.003 | | 0423r2 | | | FQDN for ePDG selection for emergency bearer services | 13.4.0 | +| | | | 0424r1 | | | FQDN for ePDG selection (for non-emergency bearer services) | 13.4.0 | +| | | | 0431r4 | | | Introduce home network domain name for OCS | 13.4.0 | +| | | | 0426r2 | | | ProSe Application code and Metadata index | 13.4.0 | +| | | | 0427r1 | | | ProSe identifiers for restricted ProSe direct discovery | 13.4.0 | +| | | | 0433r1 | | | ProSe identifiers used in direct discovery for public safety | 13.4.0 | +| | | | 0429r1 | | | Presence Reporting Area Identifier | 13.4.0 | +| | | | 0432r2 | | | Enhancement of service parameters to support Decor | 13.4.0 | +| CT#71 | 23.003 | | 0434r1 | | | Addition of ProSe Application Code Prefix and ProSe Application Code Suffix formats | 13.5.0 | +| | | | 0437r1 | | | ePDG selection with DNS-based Discovery of Regulatory Requirements | 13.5.0 | +| | | | 0438r1 | | | Clarification of TAC Allocation | 13.5.0 | +| 2016-06 | CT#72 | CP-160237 | 0441 | 1 | | Replacement field used in DNS-based Discovery of regulatory requirements | 13.6.0 | +| 2016-06 | CT#72 | CP-160237 | 0441 | 1 | | Replacement field used in DNS-based Discovery of regulatory requirements | 13.6.0 | +| 2016-06 | CT#72 | CP-160219 | 0439 | 3 | | Clarification on the construction of the private user identity | 14.0.0 | +| 2016-09 | CT#73 | CP-160425 | 0443 | 1 | | Domain Name for MCPTT confidentiality protection | 14.1.0 | +| 2016-09 | CT#73 | CP-160417 | 0445 | - | | Update of definition of BSIC to include Radio frequency Colour Code | 14.1.0 | +| 2016-12 | CT#74 | CP-160679 | 0448 | 1 | | FQDNs for ePDG selection for Emergency services | 14.2.0 | +| 2016-12 | CT#74 | CP-160679 | 0449 | 1 | | NAI for Emergency services for UEs without IMSI or with unauthenticated IMSI | 14.2.0 | +| 2016-12 | CT#74 | CP-160672 | 0456 | 1 | | Unknown User Identity | 14.2.0 | +| 2016-12 | CT#74 | CP-160666 | 0458 | 1 | | IMSI-Group-Id | 14.2.0 | +| 2016-12 | CT#74 | CP-160781 | 0459 | 3 | | KeyName-NAI format | 14.2.0 | +| 2017-03 | CT#75 | CP-170042 | 0447 | 4 | | DCN Identifier | 14.3.0 | +| 2017-03 | CT#75 | CP-170045 | 0460 | - | | Mission Critical Services | 14.3.0 | +| 2017-06 | CT#76 | CP-171016 | 0464 | 1 | | Add an explicit reference to TS33.234 and TS24.234 | 14.4.0 | +| 2017-06 | CT#76 | CP-171033 | 0465 | 2 | | FQDN for DNS Query of Local Emergency Numbers | 14.4.0 | +| 2017-06 | CT#76 | CP-171033 | 0466 | 1 | | NAI for emergency services over WLAN access to EPC | 14.4.0 | +| 2017-06 | CT#76 | CP-171032 | 0467 | 1 | | Addition of V2X Control Function FQDN format | 14.4.0 | +| 2017-06 | CT#76 | CP-171029 | 0470 | 1 | | External Group Identifier | 14.4.0 | +| 2017-06 | CT#76 | CP-171036 | 0471 | 2 | | Sx Service Parameters | 14.4.0 | +| 2017-06 | CT#76 | CP-171031 | 0472 | 1 | | Reserved range of TMGI for Receive Only Mode | 14.4.0 | +| 2017-06 | CT#76 | CP-171040 | 0468 | 1 | | External Identifier on Sh | 15.0.0 | +| 2017-09 | CT#77 | CP-172015 | 0475 | - | | PGW selection for WLAN with deployed DCNs | 15.1.0 | +| 2017-09 | CT#77 | CP-172024 | 0476 | 1 | | WebRTC Web Server Function discovery | 15.1.0 | +| 2017-12 | CT#78 | CP-173034 | 0479 | 1 | | N3IWF FQDN | 15.2.0 | +| 2017-12 | CT#78 | CP-173034 | 0480 | 1 | | Definition of 5G-GUTI and mapping between 5G-GUTI and EPS GUTI | 15.2.0 | +| 2017-12 | CT#78 | CP-173034 | 0485 | 1 | | Introducing the S-NSSAI definition | 15.2.0 | +| 2017-12 | CT#78 | CP-173036 | 0482 | 1 | | SGW/PGW selection for NR | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--|------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2017-12 | CT#78 | CP-173022 | 0484 | 2 | | Align emergency number FQDN and Replacement field with procedures in TS 24.302 | 15.2.0 | +| 2017-12 | CT#78 | CP-173024 | 0486 | 2 | | IMEI based SIP URI for P-Preferred-Identity | 15.2.0 | +| 2018-03 | CT#79 | CP-180017 | 0488 | - | | Specifying the length of the sub-label of the Country based Emergency Numbers FQDN | 15.3.0 | +| 2018-03 | CT#79 | CP-180024 | 0489 | 1 | | Definition of Service ID for WLAN based ProSe Direct Discovery | 15.3.0 | +| 2018-03 | CT#79 | CP-180022 | 0490 | 2 | | Rename entity that do national allocation/assignment of numbering/addressing/identification resources | 15.3.0 | +| 2018-03 | CT#79 | CP-180022 | 0491 | 2 | | Correct parts concerning ITU-T Rec. E.212 that is not correct in TS 23.003 | 15.3.0 | +| 2018-03 | CT#79 | CP-180022 | 0492 | 2 | | Change terminology from ISDN number/ISDN numbering plan to E.164 number and E.164 numbering plan and adjust abbreviation of MSISDN | 15.3.0 | +| 2018-03 | CT#79 | CP-180026 | 0494 | 1 | | Definition of NCI and NCGI | 15.3.0 | +| 2018-03 | CT#79 | CP-180026 | 0498 | 1 | | External identifier in 5G | 15.3.0 | +| 2018-06 | CT#80 | CP-181132 | 0497 | 4 | | NF Service Endpoint Format for Inter PLMN Routing | 15.4.0 | +| 2018-06 | CT#80 | CP-181132 | 0500 | 2 | | NRF FQDN specification for NRF discoverability | 15.4.0 | +| 2018-06 | CT#80 | CP-181132 | 0501 | 2 | | NSSF FQDN for NSSF discovery before NRF is queried | 15.4.0 | +| 2018-06 | CT#80 | CP-181132 | 0502 | 1 | | AMF Name | 15.4.0 | +| 2018-06 | CT#80 | CP-181132 | 0504 | 2 | | Structure of SUPI and SUCI | 15.4.0 | +| 2018-06 | CT#80 | CP-181132 | 0505 | 1 | | GUAMI | 15.4.0 | +| 2018-06 | CT#80 | CP-181132 | 0508 | 2 | | Definition of DNN | 15.4.0 | +| 2018-06 | CT#80 | CP-181182 | 0503 | 2 | | Changed length and mapping of 5GS Temporary Identifiers | 15.4.0 | +| 2018-09 | CT#81 | CP-182084 | 0509 | 5 | | TAI in 5GC | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0511 | 3 | | SST value not associated with any valid SD | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0512 | 3 | | Definition of PEI | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0514 | 1 | | 5GS TAI FQDN | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0515 | - | | 5GS Tracking Area Identity based ePDG FQDN | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0516 | 1 | | SUPI definition and NAI format | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0517 | 4 | | SUCI definition and NAI format | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0518 | 1 | | Network Capability SMF | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0519 | 1 | | AMF Discovery by 5G-AN | 15.5.0 | +| 2018-09 | CT#81 | CP-182067 | 0510 | 1 | | DNS records for selecting a node with a network capability in a Dedicated Core Network | 15.5.0 | +| 2018-12 | CT#82 | CP-183092 | 0529 | 3 | | SUCI definition and NAI format | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0520 | 1 | | Internal-Group Identifier | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0521 | 1 | | Definition of GPSI | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0522 | - | | Selection of a PGW-U/UPF | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0523 | 1 | | Correct missing 5GC NAI | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0524 | 2 | | Telescopic FQDN | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0525 | 1 | | Clarification of MSIN in SUCI | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0526 | - | | Routing ID | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0527 | 1 | | SUPI definition | 15.6.0 | +| 2018-12 | CT#82 | CP-183092 | 0528 | - | | EPS interworking with 5GS | 15.6.0 | +| 2019-06 | CT#84 | CP-191058 | 0530 | 1 | | Derivation of SUPI from SUCI | 15.7.0 | +| 2019-06 | CT#84 | CP-191058 | 0533 | - | | NRF and NSSF URIs | 15.7.0 | +| 2019-09 | CT#85 | CP-182116 | 0541 | - | | Presence Reporting Area Identifier (PRA ID) in 5GS | 15.8.0 | +| 2019-09 | CT#85 | CP-182232 | 0540 | 3 | | Clarification about the Routing Indicator | 15.8.0 | +| 2019-09 | CT#85 | CP-192133 | 0534 | - | | Closed Access Group | 16.0.0 | +| 2019-09 | CT#85 | CP-192133 | 0539 | 2 | | Network Identifier for SNPN | 16.0.0 | +| 2019-09 | CT#85 | CP-192189 | 0543 | 1 | | UE radio capability ID format | 16.0.0 | +| 2019-09 | CT#85 | CP-192194 | 0536 | 2 | | Definition of NF Set ID | 16.0.0 | +| 2019-09 | CT#85 | CP-192194 | 0537 | 1 | | Definition of NF Service Set ID | 16.0.0 | +| 2019-09 | CT#85 | CP-192194 | 0538 | 1 | | Definition of SMF Set FQDN | 16.0.0 | +| 2019-12 | CT#86 | CP-193037 | 0549 | - | | Clarification of possible values for Home Network Public Key Identifier of SUCI | 16.1.0 | +| 2019-12 | CT#86 | CP-193037 | 0556 | 1 | | Slice Differentiator (SD) in S-NSSAI | 16.1.0 | +| 2019-12 | CT#86 | CP-193037 | 0560 | 1 | | DNAI definition | 16.1.0 | +| 2019-12 | CT#86 | CP-193046 | 0550 | 1 | | Definition of Global Line Identifier | 16.1.0 | +| 2019-12 | CT#86 | CP-193046 | 0552 | 1 | | MAC Address as PEI format | 16.1.0 | +| 2019-12 | CT#86 | CP-193046 | 0558 | 1 | | NAI format used for 5G registration via trusted non-3GPP access | 16.1.0 | +| 2019-12 | CT#86 | CP-193050 | 0559 | - | | FQDNs for Stand-alone Non-Public Networks | 16.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------|--------| +| 2019-12 | CT#86 | CP-193240 | 0553 | 4 | | Global uniqueness of NID | 16.1.0 | +| 2019-12 | CT#86 | CP-193057 | 0544 | 1 | | Format of NF (Service) Set ID | 16.1.0 | +| 2019-12 | CT#86 | CP-193062 | 0548 | - | | Update of UE radio capability ID format | 16.1.0 | +| 2019-12 | CT#86 | CP-193062 | 0561 | | | Removal of TAC+SVN from network assigned UE Radio Capability IDs | 16.1.0 | +| 2020-03 | CT#87e | CP-200032 | 0563 | 1 | | NID | 16.2.0 | +| 2020-03 | CT#87e | CP-200032 | 0565 | 2 | | NF (Service) Set ID definitions for Standalone Non-Public Networks | 16.2.0 | +| 2020-03 | CT#87e | CP-200032 | 0571 | 1 | | CAG-ID size | 16.2.0 | +| 2020-03 | CT#87e | CP-200032 | 0572 | 1 | | UE identifier for SNPN | 16.2.0 | +| 2020-03 | CT#87e | CP-200021 | 0564 | 2 | | UE Radio Capability ID | 16.2.0 | +| 2020-03 | CT#87e | CP-200021 | 0574 | - | | DNS identifiers for UCMF | 16.2.0 | +| 2020-03 | CT#87e | CP-200035 | 0567 | | | SUPI definition for 5G-RG and FN-RG | 16.2.0 | +| 2020-03 | CT#87e | CP-200035 | 0568 | 3 | | SUCI definition for 5G-RG and FN-RG | 16.2.0 | +| 2020-03 | CT#87e | CP-200035 | 0569 | 3 | | User Location for RG accessing the 5GC via W-5GCAN or W-5GBAN | 16.2.0 | +| 2020-03 | CT#87e | CP-200035 | 0570 | 3 | | PEI for UEs not supporting any 3GPP access technologies | 16.2.0 | +| 2020-03 | CT#87e | CP-200035 | 0573 | 3 | | NAI format used for 5G registration via trusted non-3GPP access - part 2 | 16.2.0 | +| 2020-06 | CT#88e | CP-201014 | 0578 | 1 | | DNS subdomain for operator usage in 5GC | 16.3.0 | +| 2020-06 | CT#88e | CP-201046 | 0577 | 1 | | Definition of Truncated 5G-S-TMSI | 16.3.0 | +| 2020-06 | CT#88e | CP-201045 | 0579 | - | | Remove Editor's Note on New sub-domain for Interworking with SNPN | 16.3.0 | +| 2020-06 | CT#88e | CP-201045 | 0591 | 1 | | NID in TAI / ECGI / NCGI for SNPNs | 16.3.0 | +| 2020-06 | CT#88e | CP-201048 | 0580 | 1 | | Removal of the Editor's Notes | 16.3.0 | +| 2020-06 | CT#88e | CP-201048 | 0590 | - | | NAI format for SUCI containing a GLI or GCI | 16.3.0 | +| 2020-06 | CT#88e | CP-201035 | 0587 | - | | Version ID in UE Radio Capability ID | 16.3.0 | +| 2020-06 | CT#88e | CP-201030 | 0588 | 1 | | Equivalent Service Sets | 16.3.0 | +| 2020-06 | CT#88e | CP-201030 | 0589 | 1 | | Equivalent NF Instances | 16.3.0 | +| 2020-09 | CT#89e | CP-202043 | 0594 | 1 | | SMSF FQDN | 16.4.0 | +| 2020-09 | CT#89e | CP-202095 | 0592 | 1 | | Editor's note in introduction clauses | 16.4.0 | +| 2020-09 | CT#89e | CP-202106 | 0595 | - | | Adding definition for HRNN | 16.4.0 | +| 2020-09 | CT#89e | CP-202105 | 0596 | 1 | | Correction on Truncated 5G-S-TMSI | 16.4.0 | +| 2020-12 | CT#90e | CP-203039 | 0559 | - | | Removal of Editor's note for N5CW | 16.5.0 | +| 2020-12 | CT#90e | CP-203039 | 0598 | 1 | | GLI and GCI in SUCI | 16.5.0 | +| 2020-12 | CT#90e | CP-203058 | 0597 | 1 | | Support of PGW-C/SMF change | 17.0.0 | +| 2021-03 | CT#91e | CP-210052 | 0604 | - | | Correcting APN-OI replacement specification mismatch between stage 2 and stage 3 | 17.1.0 | +| 2021-03 | CT#91e | CP-210049 | 0606 | - | | DCN support for AMF discovery | 17.1.0 | +| 2021-03 | CT#91e | CP-210047 | 0609 | 1 | | Visited Country FQDN for SNPN N3IWF | 17.1.0 | +| 2021-06 | CT#92e | CP-211059 | 0615 | 1 | | Essential Correction on AMF Set ID | 17.2.0 | +| 2021-06 | CT#92e | CP-211034 | 0610 | 1 | | NSI based SUPI/SUCI | 17.2.0 | +| 2021-06 | CT#92e | CP-211034 | 0611 | 1 | | Including support for SNPN-based IMS identities | 17.2.0 | +| 2021-06 | CT#92e | CP-211034 | 0612 | 1 | | Home Network Identifier for SNPN | 17.2.0 | +| 2021-09 | CT#93e | CP-212039 | 0616 | - | F | Self-assignment NID | 17.3.0 | +| 2021-09 | CT#93e | CP-212035 | 0618 | - | B | Definition of Area Session ID | 17.3.0 | +| 2021-09 | CT#93e | CP-212035 | 0617 | - | B | Definition of TMGI for MBS in 5GS | 17.3.0 | +| 2021-09 | CT#93e | CP-212058 | 0619 | 1 | F | FQDN for N3IWF selection for emergency services | 17.3.0 | +| 2021-09 | CT#93e | CP-212026 | 0620 | - | F | Slice SD ranges | 17.3.0 | +| 2021-12 | CT#94e | CP-213148 | 0624 | 1 | A | Realm in SUCI in NAI format | 17.4.0 | +| 2021-12 | CT#94e | CP-213097 | 0621 | - | B | Selection of a combined UPF/MB-UPF | 17.4.0 | +| 2022-03 | CT#95e | CP-220073 | 0632 | - | A | RID for SNPN UEs | 17.5.0 | +| 2022-03 | CT#95e | CP-220047 | 0625 | 1 | F | SNPN impacts - NID length | 17.5.0 | +| 2022-03 | CT#95e | CP-220047 | 0626 | 1 | B | Anonymous SUCI | 17.5.0 | +| 2022-06 | CT#96 | CP-221023 | 0635 | 1 | B | MBS Frequency Selection Area ID | 17.6.0 | +| 2022-06 | CT#96 | CP-221030 | 0633 | 2 | F | Decorated NAI format for SUCI | 17.6.0 | +| 2022-06 | CT#96 | CP-221036 | 0628 | 4 | F | Correction to SNPN realm part of NAI | 17.6.0 | +| 2022-06 | CT#96 | CP-221036 | 0636 | - | F | Group Identifier for Network Selection | 17.6.0 | +| 2022-06 | CT#96 | CP-221045 | 0634 | - | F | Realm in SUCI in NAI format | 17.6.0 | +| 2022-09 | CT#97e | CP-222064 | 0639 | 1 | A | DNN Operator Identifier in SNPN | 17.7.0 | +| 2022-09 | CT#97e | CP-222031 | 0643 | - | F | Editor's note on Structure of TMGI | 17.7.0 | +| 2022-09 | CT#97e | CP-222035 | 0644 | 1 | F | NAI Format for PRUK ID and 5G PRUK ID | 17.7.0 | +| 2022-12 | CT#98e | CP-223048 | 0642 | 7 | F | NAI format for 5G NSWO | 17.8.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------|--------| +| 2022-12 | CT#98e | CP-223054 | 0645 | 1 | F | Definition of 5G DDNMF FQDN | 17.8.0 | +| 2022-12 | CT#98e | CP-223054 | 0646 | 2 | F | PRUK and 5GPRUK Name Alignment | 17.8.0 | +| 2022-12 | CT#98e | CP-223031 | 0647 | - | B | Slice-specific N3IWF FQDNs | 18.0.0 | +| 2022-12 | CT#98e | CP-223264 | 0648 | 5 | B | NAI format for 5G registration via trusted access using SNPN | 18.0.0 | +| 2023-03 | CT#99 | CP-230091 | 0662 | 1 | A | NF Set ID encoding for an AMF set | 18.1.0 | +| 2023-03 | CT#99 | CP-230079 | 0659 | 1 | A | Stage 2 alignments for Non-seamless WLAN offload in 5GS | 18.1.0 | +| 2023-03 | CT#99 | CP-230037 | 0652 | 1 | B | N3IWF FQDN with Onboarding support | 18.1.0 | +| 2023-03 | CT#99 | CP-230037 | 0663 | - | B | Definition of NAI format for support of NSWO using SNPN Credentials | 18.1.0 | +| 2023-03 | CT#99 | CP-230037 | 0665 | - | B | NAI format for N5CW device 5G registration via trusted access using SNPN | 18.1.0 | +| 2023-03 | CT#99 | CP-230050 | 0651 | 2 | F | Updating the NOTE on UE configured N3IWF FQDN | 18.1.0 | +| 2023-03 | CT#99 | CP-230050 | 0653 | - | F | Normative statements on FQDN format | 18.1.0 | +| 2023-03 | CT#99 | CP-230050 | 0654 | - | F | APN-OI replacement usage | 18.1.0 | +| 2023-06 | CT#100 | CP-231037 | 0666 | 1 | B | Associated session ID for Multicast and Broadcast Services | 18.2.0 | +| 2023-06 | CT#100 | CP-231040 | 0671 | 2 | B | Visited Country Emergency SNPN FQDN | 18.2.0 | +| 2023-06 | CT#100 | CP-231040 | 0674 | 2 | B | FQDN for SNPN N3IWF supporting Onboarding | 18.2.0 | +| 2023-06 | CT#100 | CP-231040 | 0675 | 1 | B | Support of N5CW device using decorated NAI | 18.2.0 | +| 2023-06 | CT#100 | CP-231041 | 0670 | 1 | B | Support of TNGF selection based on the slices | 18.2.0 | +| 2023-06 | CT#100 | CP-231069 | 0678 | 1 | F | NSI Identifier definition | 18.2.0 | +| 2023-06 | CT#100 | CP-231079 | 0673 | - | A | Missing NF FQDN for inter-SNPN Routing | 18.2.0 | +| 2023-06 | CT#100 | CP-231088 | 0669 | 1 | A | Removal of Network Identifiers (NID) from the realm for IMSI based SUCI. | 18.2.0 | +| 2023-06 | CT#100 | CP-231091 | 0681 | 1 | A | NAI format for 5GWC roaming case | 18.2.0 | +| 2023-09 | CT#101 | CP-232048 | 0684 | - | F | Correction on NAI used for N5CW devices | 18.3.0 | +| 2023-12 | CT#102 | CP-233044 | 0677 | 3 | F | NSAC Service Area Identifier | 18.4.0 | +| 2023-12 | CT#102 | CP-233049 | 0687 | 2 | B | SNPN Identifier based N3IWF FQDN | 18.4.0 | +| 2023-12 | CT#102 | CP-233049 | 0689 | 1 | B | Update decorate NAI for N5CW device | 18.4.0 | +| 2023-12 | CT#102 | CP-233049 | 0691 | 1 | B | Decorated NAI format for 5G-NSWO | 18.4.0 | +| 2023-12 | CT#102 | CP-233054 | 0685 | - | B | TNGF ID format in NAI used for 5G registration via trusted non-3GPP access | 18.4.0 | +| 2023-12 | CT#102 | CP-233054 | 0688 | 1 | B | ULI of AUN3 device connected behind the 5G-CRG | 18.4.0 | +| 2023-12 | CT#102 | CP-233056 | 0690 | 3 | F | Clarification of NAI format for Anonymous SUCI | 18.4.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23032/raw.md b/raw/rel-18/23_series/23032/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a79c60b0319596e2987a31f4bc1c5e771be37532 --- /dev/null +++ b/raw/rel-18/23_series/23032/raw.md @@ -0,0 +1,1385 @@ + + +# 3GPP TS 23.032 V18.1.0 (2023-09) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Universal Geographical Area Description (GAD) (Release 18)** + +![3GPP logo with the text 'A GLOBAL INITIATIVE' below it.](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 3GPP logo features the letters '3GPP' in a stylized, bold font. The '3' and 'G' are connected at the top, and the 'P' has a small red signal icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo with the text 'A GLOBAL INITIATIVE' below it. + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Reference system ..... | 8 | +| 5 Shapes ..... | 8 | +| 5.1 Ellipsoid Point..... | 9 | +| 5.2 Ellipsoid point with uncertainty circle ..... | 9 | +| 5.3 Ellipsoid point with uncertainty ellipse..... | 10 | +| 5.3a High Accuracy Ellipsoid point with uncertainty ellipse ..... | 10 | +| 5.3b High Accuracy Ellipsoid point with scalable uncertainty ellipse ..... | 10 | +| 5.4 Polygon..... | 11 | +| 5.5 Ellipsoid Point with Altitude..... | 11 | +| 5.6 Ellipsoid point with altitude and uncertainty ellipsoid..... | 12 | +| 5.6a High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid ..... | 12 | +| 5.6b High Accuracy Ellipsoid point with altitude and scalable uncertainty ellipsoid ..... | 13 | +| 5.7 Ellipsoid Arc ..... | 13 | +| 5.8 Local 2D point with uncertainty ellipse ..... | 13 | +| 5.9 Local 3D point with uncertainty ellipsoid..... | 14 | +| 5.10 Range and Direction..... | 14 | +| 5.11 Relative 2D Location with uncertainty ellipse..... | 14 | +| 5.12 Relative 3D Location with uncertainty ellipsoid..... | 15 | +| 6 Coding..... | 15 | +| 6.1 Point ..... | 15 | +| 6.1a High Accuracy Point..... | 15 | +| 6.2 Uncertainty..... | 16 | +| 6.2a High Accuracy Uncertainty..... | 16 | +| 6.2b High Accuracy Extended Uncertainty..... | 17 | +| 6.3 Altitude..... | 18 | +| 6.3a High Accuracy Altitude ..... | 18 | +| 6.4 Uncertainty Altitude..... | 18 | +| 6.5 Confidence ..... | 18 | +| 6.6 Radius..... | 19 | +| 6.7 Angle..... | 19 | +| 7 General message format and information elements coding..... | 19 | +| 7.1 Overview ..... | 20 | +| 7.2 Type of Shape..... | 20 | +| 7.3 Shape description ..... | 21 | +| 7.3.1 Ellipsoid Point ..... | 21 | +| 7.3.2 Ellipsoid Point with uncertainty Circle ..... | 22 | +| 7.3.3 Ellipsoid Point with uncertainty Ellipse..... | 23 | +| 7.3.3a High Accuracy Ellipsoid point with uncertainty ellipse..... | 24 | +| 7.3.3b High Accuracy Ellipsoid point with scalable uncertainty ellipse..... | 25 | +| 7.3.4 Polygon..... | 26 | +| 7.3.5 Ellipsoid Point with Altitude ..... | 27 | +| 7.3.6 Ellipsoid Point with altitude and uncertainty ellipsoid..... | 28 | +| 7.3.6a High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid ..... | 29 | +| 7.3.6b High Accuracy Ellipsoid point with altitude and scalable uncertainty ellipsoid..... | 30 | +| 7.3.7 Ellipsoid Arc..... | 31 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|-----------| +| 8 | Description of Velocity ..... | 32 | +| 8.1 | Horizontal Velocity ..... | 32 | +| 8.2 | Horizontal and Vertical Velocity ..... | 32 | +| 8.3 | Horizontal Velocity with Uncertainty ..... | 32 | +| 8.4 | Horizontal and Vertical Velocity with Uncertainty ..... | 32 | +| 8.4a | Relative Velocity with Uncertainty ..... | 33 | +| 8.5 | Coding Principles ..... | 33 | +| 8.6 | Coding of Velocity Type ..... | 33 | +| 8.7 | Coding of Horizontal Speed ..... | 34 | +| 8.8 | Coding of Bearing ..... | 34 | +| 8.9 | Coding of Vertical Speed ..... | 34 | +| 8.10 | Coding of Vertical Speed Direction ..... | 34 | +| 8.11 | Coding of Uncertainty Speed ..... | 34 | +| 8.12 | Coding of Horizontal Velocity ..... | 35 | +| 8.13 | Coding of Horizontal with Vertical Velocity ..... | 35 | +| 8.14 | Coding of Horizontal Velocity with Uncertainty ..... | 35 | +| 8.15 | Coding of Horizontal with Vertical Velocity and Uncertainty ..... | 36 | +| Annex A (informative): | Element description in compact notation..... | 37 | +| Annex B (informative): | Change history ..... | 39 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document defines an intermediate universal Geographical Area Description which subscriber applications, GSM, UMTS, EPS or 5GS services can use and the network can convert into an equivalent radio coverage map. + +For GSM, UMTS, EPS or 5GS services which involve the use of an "area", it can be assumed that in the majority of cases the Service Requester will be forbidden access to data on the radio coverage map of a particular PLMN and that the Service Requester will not have direct access to network entities (e.g. BSC/BTS, RNC/Node B, eNB or gNB). + +The interpretation by the PLMN operator of the geographical area in terms of cells actually used, cells that are partly within the given area and all other technical and quality of service aspects are out of the scope of the present document. + +This specification also provides a description of velocity that may be associated with a universal Geographical Area Description when both are applied to a common entity at a common time. + +The specification further provides a description of range and direction, relative location and relative velocity for a pair of devices such as 2 UEs. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". +- [2] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface signalling layer 3 General aspects". +- [3] Military Standard WGS84 Metric MIL-STD-2401 (11 January 1994): "Military Standard Department of Defence World Geodetic System (WGS)". +- [4] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following definitions apply. + +**Coordinate ID:** an identifier for a reference point that defines the origin of a particular local Cartesian System. + +**Local Co-ordinates:** co-ordinates relative to a local Cartesian System whose origin is expressed by a reference point. The origin may have known WGS84 coordinates. Local Co-ordinates are only applicable in 5GS. + +**Service Requester:** Entity, which uses the Geographical Area Description in any protocol to inform the network about a defined area. + +**Target:** Entity whose precise geographic position is to be described. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in GSM 01.04 [1] and the following apply. + +| | | +|-----|-------------------------------| +| GAD | Geographical Area Description | +| GPS | Global Positioning System | +| WGS | World Geodetic System | + +# --- 4 Reference system + +Except for local co-ordinates, the reference system chosen for the coding of locations is the World Geodetic System 1984, (WGS 84), which is also used by the Global Positioning System, (GPS). The origin of the WGS 84 co-ordinate system is the geometric centre of the WGS 84 ellipsoid. The ellipsoid is constructed by the rotation of an ellipse around the minor axis which is oriented in the North-South direction. The rotation axis is the polar axis of the ellipsoid, and the plane orthogonal to it and including the centre of symmetry is the equatorial plane. + +The relevant dimensions are as follows: + +Major Axis (a) = 6378137 m + +Minor Axis (b) = 6356752,314 m + +$$\text{First eccentricity of the ellipsoid} = \frac{a^2 - b^2}{b^2} = 0,0066943800668$$ + +Co-ordinates are then expressed in terms of longitude and latitude relevant to this ellipsoid. The range of longitude is -180° to +180°, and the range of latitude is -90° to +90°. 0° longitude corresponds to the Greenwich Meridian, and positive angles are to the East, while negative angles are to the West. 0° latitude corresponds to the equator, and positive angles are to the North, while negative angles are to the South. Altitudes are defined as the distance between the ellipsoid and the point, along a line orthogonal to the ellipsoid. + +Local Co-ordinates are relative to a known reference point defined by an unique Coordinate ID configured by the PLMN operator. Local co-ordinates are then expressed in a local Cartesian co-ordinates system relative to the reference point. + +# --- 5 Shapes + +The intention is to incorporate a number of different shapes, that can be chosen according to need. + +- Ellipsoid Point; +- Ellipsoid point with uncertainty circle; +- Ellipsoid point with uncertainty ellipse; +- Polygon; +- Ellipsoid point with altitude; +- Ellipsoid point with altitude and uncertainty ellipsoid; +- Ellipsoid Arc; +- High Accuracy Ellipsoid point with uncertainty ellipse; +- High Accuracy Ellipsoid point with scalable uncertainty ellipse; +- High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid; +- High Accuracy Ellipsoid point with altitude and scalable uncertainty ellipsoid. + +Shapes relevant to Local Co-ordinates: + +- Local 2D point with uncertainty ellipse (only in 5GS); +- Local 3D point with uncertainty ellipsoid (only in 5GS). + +Shapes relevant to a pair of devices: + +- Range and Direction (only in 5GS); +- Relative Location (only in 5GS). + +Each shape is discussed individually. + +## 5.1 Ellipsoid Point + +The description of an ellipsoid point is that of a point on the surface of the ellipsoid, and consists of a latitude and a longitude. In practice, such a description can be used to refer to a point on Earth's surface, or close to Earth's surface, with the same longitude and latitude. No provision is made in this version of the standard to give the height of a point. + +Figure 1 illustrates a point on the surface of the ellipsoid and its co-ordinates. + +The latitude is the angle between the equatorial plane and the perpendicular to the plane tangent to the ellipsoid surface at the point. Positive latitudes correspond to the North hemisphere. The longitude is the angle between the half-plane determined by the Greenwich meridian and the half-plane defined by the point and the polar axis, measured Eastward. + +![Figure 1: Description of a Point as two co-ordinates. The diagram shows an ellipsoid with a horizontal equatorial plane and a vertical polar axis. A point is marked on the surface. The 'Latitude' is indicated by an arc between the equatorial plane and a line perpendicular to the tangent at the point. The 'Longitude' is indicated by an arc in the equatorial plane between the Greenwich meridian and the projection of the point onto the plane.](6786ba12e3eceb3cf496108a02a37f09_img.jpg) + +Figure 1: Description of a Point as two co-ordinates. The diagram shows an ellipsoid with a horizontal equatorial plane and a vertical polar axis. A point is marked on the surface. The 'Latitude' is indicated by an arc between the equatorial plane and a line perpendicular to the tangent at the point. The 'Longitude' is indicated by an arc in the equatorial plane between the Greenwich meridian and the projection of the point onto the plane. + +**Figure 1: Description of a Point as two co-ordinates** + +## 5.2 Ellipsoid point with uncertainty circle + +The "ellipsoid point with uncertainty circle" is characterised by the co-ordinates of an ellipsoid point (the origin) and a distance $r$ . It describes formally the set of points on the ellipsoid which are at a distance from the origin less than or equal to $r$ , the distance being the geodesic distance over the ellipsoid, i.e., the minimum length of a path staying on the ellipsoid and joining the two points, as shown in figure 2. + +As for the ellipsoid point, this can be used to indicate points on the Earth surface, or near the Earth surface, of same latitude and longitude. + +The typical use of this shape is to indicate a point when its position is known only with a limited accuracy. + +![Figure 2: Description of an uncertainty Circle. A circle with a center point marked by a crosshair. A horizontal line segment extends from the center to the right edge, labeled 'r'.](07f537f57749b75157f742525e6a8dbc_img.jpg) + +Figure 2: Description of an uncertainty Circle. A circle with a center point marked by a crosshair. A horizontal line segment extends from the center to the right edge, labeled 'r'. + +Figure 2: Description of an uncertainty Circle + +## 5.3 Ellipsoid point with uncertainty ellipse + +The "ellipsoid point with uncertainty ellipse" is characterised by the co-ordinates of an ellipsoid point (the origin), distances $r1$ and $r2$ and an angle of orientation $A$ . It describes formally the set of points on the ellipsoid which fall within or on the boundary of an ellipse with semi-major axis of length $r1$ oriented at angle $A$ (0 to $180^\circ$ ) measured clockwise from north and semi-minor axis of length $r2$ , the distances being the geodesic distance over the ellipsoid, i.e., the minimum length of a path staying on the ellipsoid and joining the two points, as shown in figure 2a. + +As for the ellipsoid point, this can be used to indicate points on the Earth's surface, or near the Earth's surface, of same latitude and longitude. The confidence level with which the position of a target entity is included within this set of points is also included with this shape. + +The typical use of this shape is to indicate a point when its position is known only with a limited accuracy, but the geometrical contributions to uncertainty can be quantified. + +![Figure 2a: Description of an uncertainty Ellipse. An ellipse centered at the origin of a coordinate system. A vertical arrow points up from the origin, labeled 'North'. A horizontal line extends to the right from the origin. An arc indicates an angle 'angle, A' clockwise from the North arrow to the semi-major axis. The semi-major axis is labeled 'semi-major axis, r1' and the semi-minor axis is labeled 'semi-minor axis, r2'.](0a90113d6c8989e8b3c89c5cf9f926d7_img.jpg) + +Figure 2a: Description of an uncertainty Ellipse. An ellipse centered at the origin of a coordinate system. A vertical arrow points up from the origin, labeled 'North'. A horizontal line extends to the right from the origin. An arc indicates an angle 'angle, A' clockwise from the North arrow to the semi-major axis. The semi-major axis is labeled 'semi-major axis, r1' and the semi-minor axis is labeled 'semi-minor axis, r2'. + +Figure 2a: Description of an uncertainty Ellipse + +### 5.3a High Accuracy Ellipsoid point with uncertainty ellipse + +The "high accuracy ellipsoid point with uncertainty ellipse" is characterised by the co-ordinates of an ellipsoid point (the origin), distances $r1$ and $r2$ and an angle of orientation $A$ , as described in clause 5.3. Compared to the "ellipsoid point with uncertainty ellipse", the "high accuracy ellipsoid point with uncertainty ellipse" provides finer resolution for the co-ordinates, and distances $r1$ and $r2$ . + +### 5.3b High Accuracy Ellipsoid point with scalable uncertainty ellipse + +The "high accuracy ellipsoid point with scalable uncertainty ellipse" is characterised by the co-ordinates of an ellipsoid point (the origin), distances $r1$ and $r2$ and an angle of orientation $A$ , as described in clause 5.3. Compared to the "ellipsoid point with uncertainty ellipse", the "high accuracy ellipsoid point with scalable uncertainty ellipse" provides + +finer resolution for the co-ordinates, and distances $r1$ and $r2$ , and additionally provides possibility to choose uncertainty range compared to "high accuracy ellipsoid point with uncertainty ellipse". + +## 5.4 Polygon + +A polygon is an arbitrary shape described by an ordered series of points (in the example pictured in the drawing, A to E). The minimum number of points allowed is 3, and the maximum number of points allowed is 15. The points shall be connected in the order that they are given. A connecting line is defined as the line over the ellipsoid joining the two points and of minimum distance (geodesic). The last point is connected to the first. The list of points shall respect a number of conditions: + +- a connecting line shall not cross another connecting line; +- two successive points must not be diametrically opposed on the ellipsoid. + +The described area is situated to the right of the lines with the downward direction being toward the Earth's centre and the forward direction being from a point to the next. + +NOTE: This definition does not permit connecting lines greater than roughly 20 000 km. If such a need arises, the polygon can be described by adding an intermediate point. + +Computation of geodesic lines is not simple. Approximations leading to a maximum distance between the computed line and the geodesic line of less than 3 metres are acceptable. + +![Figure 3: Description of a Polygon. The diagram shows a polygon with five vertices labeled A, B, C, D, and E. The vertices are connected in the order A-B-C-D-E-A. The lines are straight segments. The vertices are marked with 'X' symbols. The polygon is oriented such that the interior is to the right of the directed edges (A to B, B to C, C to D, D to E, E to A).](18442e4e239480f0c3c95b547aa8fde2_img.jpg) + +Figure 3: Description of a Polygon. The diagram shows a polygon with five vertices labeled A, B, C, D, and E. The vertices are connected in the order A-B-C-D-E-A. The lines are straight segments. The vertices are marked with 'X' symbols. The polygon is oriented such that the interior is to the right of the directed edges (A to B, B to C, C to D, D to E, E to A). + +Figure 3: Description of a Polygon + +## 5.5 Ellipsoid Point with Altitude + +The description of an ellipsoid point with altitude is that of a point at a specified distance above or below a point on the earth's surface. This is defined by an ellipsoid point with the given longitude and latitude and the altitude above or below the ellipsoid point. Figure 3a illustrates the altitude aspect of this description. + +![Figure 3a: Description of an Ellipsoid Point with Altitude. The diagram shows a circle representing a horizontal plane. A horizontal line extends from the center to the right edge, with a double-headed arrow labeled 'Altitude'. A diagonal line extends from the center to the upper-left edge, also with a double-headed arrow labeled 'Altitude'. Two points are marked on the circle's circumference: one in the upper-left quadrant labeled 'Point with negative altitude' and one on the right edge labeled 'Point with positive altitude'.](10953d657a5f47fdc829a800419dd370_img.jpg) + +Figure 3a: Description of an Ellipsoid Point with Altitude. The diagram shows a circle representing a horizontal plane. A horizontal line extends from the center to the right edge, with a double-headed arrow labeled 'Altitude'. A diagonal line extends from the center to the upper-left edge, also with a double-headed arrow labeled 'Altitude'. Two points are marked on the circle's circumference: one in the upper-left quadrant labeled 'Point with negative altitude' and one on the right edge labeled 'Point with positive altitude'. + +Figure 3a: Description of an Ellipsoid Point with Altitude + +## 5.6 Ellipsoid point with altitude and uncertainty ellipsoid + +The "ellipsoid point with altitude and uncertainty ellipsoid" is characterised by the co-ordinates of an ellipsoid point with altitude, distances $r1$ (the "semi-major uncertainty"), $r2$ (the "semi-minor uncertainty") and $r3$ (the "vertical uncertainty") and an angle of orientation $A$ (the "angle of the major axis"). It describes formally the set of points which fall within or on the surface of a general (three dimensional) ellipsoid centred on an ellipsoid point with altitude whose real semi-major, semi-mean and semi-minor axis are some permutation of $r1$ , $r2$ , $r3$ with $r1 \geq r2$ . The $r3$ axis is aligned vertically, while the $r1$ axis, which is the semi-major axis of the ellipse in a horizontal plane that bisects the ellipsoid, is oriented at an angle $A$ (0 to 180 degrees) measured clockwise from north, as illustrated in Figure 3b. + +![Figure 3b: Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid. The diagram shows a 3D ellipsoid. A vertical axis is labeled 'vertical' with an upward arrow. The horizontal plane contains two axes: the semi-major axis labeled 'r1' and the semi-minor axis labeled 'r2'. The vertical axis is labeled 'r3'. An angle 'A' is shown between a north arrow 'N' and the 'r1' axis. A point on the ellipsoid's surface is labeled 'ellipsoid point with altitude'.](53298644c66fa3fca81d6eec654afec5_img.jpg) + +Figure 3b: Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid. The diagram shows a 3D ellipsoid. A vertical axis is labeled 'vertical' with an upward arrow. The horizontal plane contains two axes: the semi-major axis labeled 'r1' and the semi-minor axis labeled 'r2'. The vertical axis is labeled 'r3'. An angle 'A' is shown between a north arrow 'N' and the 'r1' axis. A point on the ellipsoid's surface is labeled 'ellipsoid point with altitude'. + +Figure 3b: Description of an Ellipsoid Point with Altitude and Uncertainty Ellipsoid + +The typical use of this shape is to indicate a point when its horizontal position and altitude are known only with a limited accuracy, but the geometrical contributions to uncertainty can be quantified. The confidence level with which the position of a target entity is included within the shape is also included. + +### 5.6a High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid + +The "high accuracy ellipsoid point with altitude and uncertainty ellipsoid" is characterised by the co-ordinates of an ellipsoid point with altitude, distances $r1$ (the "semi-major uncertainty"), $r2$ (the "semi-minor uncertainty") and $r3$ (the "vertical uncertainty") and an angle of orientation $A$ (the "angle of the major axis"), as described in clause 5.6. Compared to the "ellipsoid point with altitude and uncertainty ellipsoid", the "high accuracy ellipsoid point with altitude and uncertainty ellipsoid" provides finer resolution for the co-ordinates, and distances $r1$ , $r2$ , and $r3$ . + +### 5.6b High Accuracy Ellipsoid point with altitude and scalable uncertainty ellipsoid + +The "high accuracy ellipsoid point with altitude and scalable uncertainty ellipsoid" is characterised by the co-ordinates of an ellipsoid point with altitude, distances $r1$ (the "semi-major uncertainty"), $r2$ (the "semi-minor uncertainty") and $r3$ (the "vertical uncertainty") and an angle of orientation $A$ (the "angle of the major axis"), as described in clause 5.6. Compared to the "ellipsoid point with altitude and uncertainty ellipsoid", the "high accuracy ellipsoid point with altitude and scalable uncertainty ellipsoid" provides finer resolution for the co-ordinates, and distances $r1$ , $r2$ , and $r3$ , and additionally provides possibility to choose uncertainty range compared to "high accuracy ellipsoid point with altitude and uncertainty ellipse". + +## 5.7 Ellipsoid Arc + +An ellipsoid arc is a shape characterised by the co-ordinates of an ellipsoid point $o$ (the origin), inner radius $r1$ , uncertainty radius $r2$ , both radii being geodesic distances over the surface of the ellipsoid, the offset angle ( $\theta$ ) between the first defining radius of the ellipsoid arc and North, and the included angle ( $\beta$ ) being the angle between the first and second defining radii. The offset angle is within the range of $0^\circ$ to $359,999...^\circ$ while the included angle is within the range from $0,000...1^\circ$ to $360^\circ$ . This is to be able to describe a full circle, $0^\circ$ to $360^\circ$ . + +This shape-definition can also be used to describe a sector (inner radius equal to zero), a circle (included angle equal to $360^\circ$ ) and other circular shaped areas. The confidence level with which the position of a target entity is included within the shape is also included. + +![Figure 3c: Description of an Ellipsoid Arc. The diagram shows a blue arc segment. A vertical arrow points upwards from the origin 'Point (o)' to 'North'. A line segment labeled 'r1' extends from 'Point (o)' to the inner edge of the arc. Another line segment labeled 'r2' extends from the inner edge to the outer edge of the arc. The angle between the North arrow and the 'r1' line is labeled 'theta'. The angle between the 'r1' line and the outer edge of the arc is labeled 'beta'.](34fccc54a5930cbdf0f07e02c3745e35_img.jpg) + +Figure 3c: Description of an Ellipsoid Arc. The diagram shows a blue arc segment. A vertical arrow points upwards from the origin 'Point (o)' to 'North'. A line segment labeled 'r1' extends from 'Point (o)' to the inner edge of the arc. Another line segment labeled 'r2' extends from the inner edge to the outer edge of the arc. The angle between the North arrow and the 'r1' line is labeled 'theta'. The angle between the 'r1' line and the outer edge of the arc is labeled 'beta'. + +Figure 3c: Description of an Ellipsoid Arc + +## 5.8 Local 2D point with uncertainty ellipse + +The "local 2D point with uncertainty ellipse" is characterised by a point described in 2D local co-ordinates with origin in a known reference location, distances $r1$ and $r2$ and an angle of orientation $A$ . The local Cartesian co-ordinates system and the reference location shall be identified with a unique identifier. It describes formally the set of points which fall within or on the boundary of an ellipse with semi-major axis of length $r1$ oriented at angle $A$ ( $0$ to $180^\circ$ ) measured clockwise from north and semi-minor axis of length $r2$ . The confidence level with which the position of a target entity is included within this set of points is also included with this shape. + +This shape is only applicable to 5GS. + +The structure of local 2D point with uncertainty ellipse is defined in clause 6.1.6.2.38 in TS 29.572 [4]. + +## 5.9 Local 3D point with uncertainty ellipsoid + +The "local 3D point with uncertainty ellipsoid" is characterised by a point described in 3D local co-ordinates with origin in a known reference location, distances $r1$ (the "semi-major uncertainty"), $r2$ (the "semi-minor uncertainty") and $r3$ (the "vertical uncertainty") and an angle of orientation $A$ (the "angle of the major axis"). The local Cartesian co-ordinates system and the reference location shall be identified with a unique identifier. It describes formally the set of points which fall within or on the surface of a general (three dimensional) ellipsoid centred on a 3D point whose real semi-major, semi-mean and semi-minor axis are some permutation of $r1$ , $r2$ , $r3$ with $r1 \geq r2$ . The $r3$ axis is aligned vertically, while the $r1$ axis, which is the semi-major axis of the ellipse in a horizontal plane, is oriented at an angle $A$ (0 to 180 degrees) measured clockwise from north. The confidence level with which the position of a target entity is included within the shape is also included. + +This shape is only applicable to 5GS. + +The structure of local 3D point with uncertainty ellipsoid is defined in clause 6.1.6.2.39 in TS 29.572 [4]. + +## 5.10 Range and Direction + +The "range and direction" from a point A to a point B is characterised by three components comprising a range from point A to point B, an azimuth direction from point A to point B and an elevation direction from point A to point B as shown in Figure 3d. The range provides a straight-line distance from point A to point B. The azimuth provides a direction to point B from point A in a horizontal plane through point A and as measured clockwise from North. The elevation provides a direction to point B from point A in a vertical plane through the points A and B and as measured upwards or downwards from a horizontal plane through point A. The range, azimuth and elevation can be each independently included or excluded in a "range and direction" and each has an uncertainty and a confidence. + +![Figure 3d: Description of a Range and Direction. The diagram shows a horizontal plane through point A, represented by an ellipse. A vector labeled 'North' points upwards and to the left from point A. A vector labeled 'Azimuth' points to the right from point A. A vector labeled 'Range' points from point A to point B, which is above the horizontal plane. The angle between the 'North' vector and the 'Range' vector is labeled 'Azimuth'. The angle between the 'Range' vector and the 'Horizontal Plane through Point A' is labeled 'Elevation'.](b77cd8b2f763af8d453537177ac5942f_img.jpg) + +Figure 3d: Description of a Range and Direction. The diagram shows a horizontal plane through point A, represented by an ellipse. A vector labeled 'North' points upwards and to the left from point A. A vector labeled 'Azimuth' points to the right from point A. A vector labeled 'Range' points from point A to point B, which is above the horizontal plane. The angle between the 'North' vector and the 'Range' vector is labeled 'Azimuth'. The angle between the 'Range' vector and the 'Horizontal Plane through Point A' is labeled 'Elevation'. + +Figure 3d: Description of a Range and Direction + +Editor's note: Support of this shape will be confirmed by RAN WGs. + +## 5.11 Relative 2D Location with uncertainty ellipse + +The "relative 2D location with uncertainty ellipse" is characterised by a point described in 2D local co-ordinates with origin corresponding to another known point, distances $r1$ and $r2$ and an angle of orientation $A$ . It describes formally a set of points which fall within or on the boundary of an ellipse centered on a 2D point with semi-major axis of length $r1$ oriented at angle $A$ (0 to 180°) measured clockwise from North and semi-minor axis of length $r2$ . The confidence level with which the position of a target entity is included within this set of points is also included with this shape. + +This shape is only applicable to 5GS. + +Editor's note: The structure of a relative 2D location with uncertainty ellipse will be defined by CT WGs. + +Editor's note: Support of this shape will be confirmed by RAN WGs. + +## 5.12 Relative 3D Location with uncertainty ellipsoid + +The "relative 3D location with uncertainty ellipsoid" is characterised by a point described in 3D local co-ordinates with origin corresponding to another known point, distances $r_1$ (the "semi-major uncertainty"), $r_2$ (the "semi-minor uncertainty") and $r_3$ (the "vertical uncertainty") and an angle of orientation $A$ (the "angle of the major axis"). It describes formally the set of points which fall within or on the surface of a general (three dimensional) ellipsoid centred on a 3D point whose semi-major, semi-minor and semi-mean axis are, respectively, $r_1$ , $r_2$ , $r_3$ with $r_1 \geq r_2$ . The $r_3$ axis is aligned vertically, while the $r_1$ axis, which is the semi-major axis of the ellipse in a horizontal plane, is oriented at an angle $A$ (0 to 180 degrees) measured clockwise from North. The confidence level with which the position of a target entity is included within the shape is also included. + +This shape is only applicable to 5GS. + +Editor's note: The structure of a relative 3D location with uncertainty ellipsoid will be defined by CT WGs. + +Editor's note: Support of this shape will be confirmed by RAN WGs. + +# 6 Coding + +## 6.1 Point + +The co-ordinates of an ellipsoid point are coded with an uncertainty of less than 3 metres. + +The latitude is coded with 24 bits: 1 bit of sign and a number between 0 and $2^{23}-1$ coded in binary on 23 bits. The relation between the coded number $N$ and the range of (absolute) latitudes $X$ it encodes is the following ( $X$ in degrees): + +$$N \leq \frac{2^{23}}{90} X < N + 1$$ + +except for $N=2^{23}-1$ , for which the range is extended to include $N+1$ . + +The longitude, expressed in the range $-180^\circ$ , $+180^\circ$ , is coded as a number between $-2^{23}$ and $2^{23}-1$ , coded in 2's complement binary on 24 bits. The relation between the coded number $N$ and the range of longitude $X$ it encodes is the following ( $X$ in degrees): + +$$N \leq \frac{2^{24}}{360} X < N + 1$$ + +### 6.1a High Accuracy Point + +The co-ordinates of a high accuracy ellipsoid point are coded with a resolution of less than 5 millimetre for latitude, and less than 10 millimetre for longitude. + +The latitude for a high accuracy point, expressed in the range $-90^\circ$ , $+90^\circ$ , is coded as a number between $-2^{31}$ and $2^{31}-1$ , coded in 2's complement binary on 32 bits. The relation between the latitude $X$ in the range $[-90^\circ, 90^\circ]$ and the coded number $N$ is: + +$$N = \left\lfloor \frac{X}{90^\circ} 2^{31} \right\rfloor$$ + +where $\lfloor x \rfloor$ denotes the greatest integer less than or equal to $x$ (floor operator). + +The longitude for a high accuracy point, expressed in the range $-180^\circ$ , $+180^\circ$ , is coded as a number between $-2^{31}$ and $2^{31}-1$ , coded in 2's complement binary on 32 bits. The relation between the longitude $X$ in the range $[-180^\circ, 180^\circ]$ and the coded number $N$ is: + +$$N = \left\lfloor \frac{X}{180^\circ} 2^{31} \right\rfloor$$ + +## 6.2 Uncertainty + +A method of describing the uncertainty for latitude and longitude has been sought which is both flexible (can cover wide differences in range) and efficient. The proposed solution makes use of a variation on the Binomial expansion. The uncertainty $r$ , expressed in metres, is mapped to a number $K$ , with the following formula: + +$$r = C((1+x)^K - 1)$$ + +with $C = 10$ and $x = 0.1$ . With $0 \leq K \leq 127$ , a suitably useful range between 0 and 1800 kilometres is achieved for the uncertainty, while still being able to code down to values as small as 1 metre. The uncertainty can then be coded on 7 bits, as the binary encoding of $K$ . + +**Table 1: Example values for the uncertainty Function** + +| Value of $K$ | Value of uncertainty | +|--------------|----------------------| +| 0 | 0 m | +| 1 | 1 m | +| 2 | 2,1 m | +| - | - | +| 20 | 57,3 m | +| - | - | +| 40 | 443 m | +| - | - | +| 60 | 3 km | +| - | - | +| 80 | 20 km | +| - | - | +| 100 | 138 km | +| - | - | +| 120 | 927 km | +| - | - | +| 127 | 1800 km | + +### 6.2a High Accuracy Uncertainty + +The high accuracy uncertainty $r$ , expressed in metres, is mapped to a number $K$ , with the following formula: + +$$r = C((1+x)^K - 1)$$ + +with $C = 0.3$ and $x = 0.02$ . With $0 \leq K \leq 255$ , a suitably useful range between 0 and 46.49129 metres is achieved for the high accuracy uncertainty, while still being able to code down to values as small as 6 millimetre. The uncertainty can then be coded on 8 bits, as the binary encoding of $K$ . + +**Table 6.2a-1: Example values for the high accuracy uncertainty function** + +| Value of K | Value of uncertainty | +|--------------------------------|-----------------------------| +| 0 | 0 m | +| 1 | 0.006 m | +| 2 | 0.01212 m | +| - | - | +| 20 | 0.14578 m | +| - | - | +| 40 | 0.36241 m | +| - | - | +| 60 | 0.68430 m | +| - | - | +| 80 | 1.16263 m | +| - | - | +| 100 | 1.87339 m | +| - | - | +| 120 | 2.92954 m | +| - | - | +| 127 | 3.40973 m | +| - | - | +| 255 | 46.49129 m | + +### 6.2b High Accuracy Extended Uncertainty + +The high accuracy extended uncertainty $r$ , expressed in metres, is mapped to a number $K$ , with the following formula: + +$$r = C((1+x)^K - 1)$$ + +with $C = 0.3$ and $x = 0.02594$ , with $0 \leq K \leq 253$ , and $r = 200$ m with $K=254$ , and $r > 200$ m with $K=255$ a suitably useful range between 0 and 200 metres is achieved for the high accuracy uncertainty, while still being able to code down to values as small as 8 millimetres. The uncertainty can then be coded on 8 bits, as the binary encoding of $K$ . + +**Table 6.2b-1: Example values for the high accuracy uncertainty function** + +| Value of K | Value of uncertainty | +|--------------------------------|-----------------------------| +| 0 | 0 m | +| 1 | 0.00778 m | +| 2 | 0.01577 m | +| - | - | +| 20 | 0.20068 m | +| - | - | +| 40 | 0.53560 m | +| - | - | +| 60 | 1.09457 m | +| - | - | +| 80 | 2.02744 m | +| - | - | +| 100 | 3.58434 m | +| - | - | +| 120 | 6.18271 m | +| - | - | +| 127 | 7.45551 m | +| - | - | +| 253 | 195.12396 m | +| 254 | 200 m | +| 255 | > 200 m | + +## 6.3 Altitude + +Altitude is encoded in increments of 1 meter using a 15 bit binary coded number $N$ . The relation between the number $N$ and the range of altitudes $a$ (in metres) it encodes is described by the following equation: + +$$N \leq a < N + 1$$ + +Except for $N=2^{15}-1$ for which the range is extended to include all greater values of $a$ . + +The direction of altitude is encoded by a single bit with bit value 0 representing height above the WGS84 ellipsoid surface and bit value 1 representing depth below the WGS84 ellipsoid surface. + +### 6.3a High Accuracy Altitude + +High accuracy altitude is encoded as a number $N$ between -64000 and 1280000 using 2's complement binary on 22 bits. The relation between the number $N$ and the altitude $a$ (in metres) it encodes is described by the following equation: + +$$a = N \times 2^{-7}$$ + +So, the altitude for a high accuracy point, with a scale factor of $2^{-7}$ , ranges between -500 metres and 10000 metres. The altitude is encoded representing height above (plus) or below (minus) the WGS84 ellipsoid surface. + +## 6.4 Uncertainty Altitude + +The uncertainty in altitude, $h$ , expressed in metres is mapped from the binary number $K$ , with the following formula: + +$$h = C((1 + x)^K - 1)$$ + +with $C = 45$ and $x = 0,025$ . With $0 \leq K \leq 127$ , a suitably useful range between 0 and 990 meters is achieved for the uncertainty altitude. The uncertainty can then be coded on 7 bits, as the binary encoding of $K$ . + +**Table 2: Example values for the uncertainty altitude Function** + +| Value of $K$ | Value of uncertainty altitude | +|--------------|-------------------------------| +| 0 | 0 m | +| 1 | 1,13 m | +| 2 | 2,28 m | +| - | - | +| 20 | 28,7 m | +| - | - | +| 40 | 75,8 m | +| - | - | +| 60 | 153,0 m | +| - | - | +| 80 | 279,4 m | +| - | - | +| 100 | 486,6 m | +| - | - | +| 120 | 826,1 m | +| - | - | +| 127 | 990,5 m | + +## 6.5 Confidence + +The confidence by which the position of a target entity is known to be within the shape description, (expressed as a percentage) is directly mapped from the 7 bit binary number $K$ , except for $K=0$ which is used to indicate 'no information', and $100 < K \leq 128$ which should not be used but may be interpreted as "no information" if received. + +## 6.6 Radius + +Inner radius is encoded in increments of 5 meters using a 16 bit binary coded number $N$ . The relation between the number $N$ and the range of radius $r$ (in metres) it encodes is described by the following equation: + +$$5N \leq r < 5(N + 1)$$ + +Except for $N=2^{16}-1$ for which the range is extended to include all greater values of $r$ . +This provides a true maximum radius of 327,675 meters. + +The uncertainty radius is encoded as for the uncertainty latitude and longitude. + +## 6.7 Angle + +Offset and Included angle are encoded in increments of $2^\circ$ using an 8 bit binary coded number $N$ in the range 0 to 179. The relation between the number $N$ and the range offset ( $ao$ ) and included ( $ai$ ) of angles (in degrees) it encodes is described by the following equations: + +Offset angle ( $ao$ ) + +$2 N \leq ao < 2 (N+1)$ Accepted values for $ao$ are within the range from 0 to 359,9...9 degrees. + +Included angle ( $ai$ ) + +$2 N < ai \leq 2 (N+1)$ Accepted values for $ai$ are within the range from 0,0...1 to 360 degrees. + +# --- 7 General message format and information elements coding + +This clause describes a coding method for geographical area descriptions. A geographical area description is coded as a finite bit string. In the figures, the bit string is described by octets from top downward, and in the octet from left to right. Number encoding strings start with the most significant bit. + +## 7.1 Overview + +A bit string encoding a geographical description shall consist of the following parts: + +- Type of Shape; +- Shape Description. + +Such a bit string is usually part of an information element. The structure of the information element (e.g., element identifier, length) depends on the protocol in which the message containing the description is defined, and is specified in the protocol specification. + +This organisation is illustrated in the example shown in figure 4. + +![Figure 4: Example diagram showing the structure of a geographical description. It consists of a bit string divided into octets. The first octet (Octet 1) is split into two parts: the first four bits (8, 7, 6, 5) are labeled 'Type of shape', and the remaining bits (4, 3, 2, 1) are part of the 'Shape description'. Subsequent octets (Octet 2, etc.) are entirely part of the 'Shape description'.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +| | | +|-------------------------------|---------| +| 8   7   6   5   4   3   2   1 | | +| Type of shape | Octet 1 | +| Shape description | Octet 2 | +| | Etc... | + +Figure 4: Example diagram showing the structure of a geographical description. It consists of a bit string divided into octets. The first octet (Octet 1) is split into two parts: the first four bits (8, 7, 6, 5) are labeled 'Type of shape', and the remaining bits (4, 3, 2, 1) are part of the 'Shape description'. Subsequent octets (Octet 2, etc.) are entirely part of the 'Shape description'. + +Figure 4: Example + +## 7.2 Type of Shape + +The Type of Shape information field identifies the type which is being coded in the Shape Description. The Type of Shape is coded as shown in table 2a. + +Table 2a: Coding of Type of Shape + +| Bits | | +|--------------|--------------------------------------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | Ellipsoid Point | +| 0 0 0 1 | Ellipsoid point with uncertainty Circle | +| 0 0 1 1 | Ellipsoid point with uncertainty Ellipse | +| 0 1 0 1 | Polygon | +| 1 0 0 0 | Ellipsoid point with altitude | +| 1 0 0 1 | Ellipsoid point with altitude and uncertainty Ellipsoid | +| 1 0 1 0 | Ellipsoid Arc | +| 1 0 1 1 | High Accuracy Ellipsoid point with uncertainty ellipse | +| 1 1 0 0 | High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid | +| 1 1 0 1 | High Accuracy Ellipsoid point with scalable uncertainty ellipse | +| 1 1 1 0 | High Accuracy Ellipsoid point with altitude and scalable uncertainty ellipsoid | +| other values | reserved for future use | + +## 7.3 Shape description + +The shape description consist of different elements. + +### 7.3.1 Ellipsoid Point + +The coding of a point is described in figure 5. + +![](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------|---|---|---|-------|---|---|---|---------| +| 0 | 0 | 0 | 0 | spare | | | | Octet 1 | +| S | | | | | | | | Octet 2 | +| Degrees of latitude | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| | | | | | | | | Octet 5 | +| Degrees of longitude | | | | | | | | Octet 6 | +| | | | | | | | | Octet 7 | + +Figure 5: Shape description of a point + +S: Sign of latitude + +Bit value 0 North + +Bit value 1 South + +Degrees of latitude + +Bit 1 of octet 4 is the low order bit + +Degrees of longitude + +Bit 1 of octet 7 is the low order bit + +### 7.3.2 Ellipsoid Point with uncertainty Circle + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | +|----------------------|------------------|---|---|-------|---|---|---|---------|--|--|--|--|--|--|--|--|--|--|--| +| 0 | 0 | 0 | 1 | spare | | | | Octet 1 | | | | | | | | | | | | +| S | | | | | | | | Octet 2 | | | | | | | | | | | | +| Degrees of latitude | | | | | | | | Octet 3 | | | | | | | | | | | | +| | | | | | | | | Octet 4 | | | | | | | | | | | | +| | | | | | | | | Octet 5 | | | | | | | | | | | | +| Degrees of longitude | | | | | | | | Octet 6 | | | | | | | | | | | | +| | | | | | | | | Octet 7 | | | | | | | | | | | | +| 0
spare | Uncertainty code | | | | | | | Octet 8 | | | | | | | | | | | | + +Figure 6: Shape description of an ellipsoid point with uncertainty circle + +### 7.3.3 Ellipsoid Point with uncertainty Ellipse + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | +|---------------------------|------------------------|---|---|-------|---|---|---|----------|--|--|--|--|--|--|--|--|--|--|--| +| 0 | 0 | 1 | 1 | spare | | | | Octet 1 | | | | | | | | | | | | +| S | | | | | | | | Octet 2 | | | | | | | | | | | | +| Degrees of latitude | | | | | | | | Octet 3 | | | | | | | | | | | | +| | | | | | | | | Octet 4 | | | | | | | | | | | | +| | | | | | | | | Octet 5 | | | | | | | | | | | | +| Degrees of longitude | | | | | | | | Octet 6 | | | | | | | | | | | | +| | | | | | | | | Octet 7 | | | | | | | | | | | | +| 0
spare | Uncertainty semi-major | | | | | | | Octet 8 | | | | | | | | | | | | +| 0
spare | Uncertainty semi-minor | | | | | | | Octet 9 | | | | | | | | | | | | +| Orientation of major axis | | | | | | | | Octet 10 | | | | | | | | | | | | +| 0
spare | Confidence | | | | | | | Octet 11 | | | | | | | | | | | | + +**Figure 6a: Shape description of an ellipsoid point with uncertainty ellipse** + +Orientation of major axis + +angle in degrees between the major axis and north + +(0 = north, 90 = east, values of 180 and above are not used) + +#### 7.3.3a High Accuracy Ellipsoid point with uncertainty ellipse + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | +|--------------------------------------|------------|-------------------------------------------------------------|---|-------|---|---|---|----------|--|--|--|--|--|--|--|--|--|--| +| 1011 | | | | Spare | | | | Octet 1 | | | | | | | | | | | +| | | | | | | | | Octet 2 | | | | | | | | | | | +| ..... | | High Accuracy Degrees of Latitude
(High Accuracy Point) | | | | | | Octet 3 | | | | | | | | | | | +| ..... | | | | | | | | Octet 4 | | | | | | | | | | | +| | | | | | | | | Octet 5 | | | | | | | | | | | +| | | | | | | | | Octet 6 | | | | | | | | | | | +| ..... | | High Accuracy Degrees of Longitude
(High Accuracy Point) | | | | | | Octet 7 | | | | | | | | | | | +| ..... | | | | | | | | Octet 8 | | | | | | | | | | | +| | | | | | | | | Octet 9 | | | | | | | | | | | +| High Accuracy Uncertainty semi-major | | | | | | | | Octet 10 | | | | | | | | | | | +| High Accuracy Uncertainty semi-minor | | | | | | | | Octet 11 | | | | | | | | | | | +| Orientation of major axis | | | | | | | | Octet 12 | | | | | | | | | | | +| 0
Spare | Confidence | | | | | | | Octet 13 | | | | | | | | | | | + +**Figure 7.3.3a-1: Shape description of a high accuracy ellipsoid point with uncertainty ellipse** + +High Accuracy Degrees of Latitude: + +Bit 8 of octet 2 is the high order bit. + +Bit 1 of octet 5 is the low order bit. + +High Accuracy Degrees of Longitude: + +Bit 8 of octet 6 is the high order bit. + +Bit 1 of octet 9 is the low order bit. + +Orientation of major axis: + +angle in degrees between the major axis and north + +(0 = north, 90 = east, values of 180 and above are not used). + +#### 7.3.3b High Accuracy Ellipsoid point with scalable uncertainty ellipse + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-------------------------------------------------------------|------------|---|---|-------|---|---|---|----------|--|--|--|--| +| 1101 | | | | Spare | | | | Octet 1 | | | | | +| | | | | | | | | Octet 2 | | | | | +| High Accuracy Degrees of Latitude
(High Accuracy Point) | | | | | | | | Octet 3 | | | | | +| | | | | | | | | Octet 4 | | | | | +| | | | | | | | | Octet 5 | | | | | +| | | | | | | | | Octet 6 | | | | | +| High Accuracy Degrees of Longitude
(High Accuracy Point) | | | | | | | | Octet 7 | | | | | +| | | | | | | | | Octet 8 | | | | | +| | | | | | | | | Octet 9 | | | | | +| High Accuracy Uncertainty semi-major | | | | | | | | Octet 10 | | | | | +| High Accuracy Uncertainty semi-minor | | | | | | | | Octet 11 | | | | | +| Orientation of major axis | | | | | | | | Octet 12 | | | | | +| U | Confidence | | | | | | | Octet 13 | | | | | + +**Figure 7.3.3b-1: Shape description of a high accuracy ellipsoid point with uncertainty ellipse** + +High Accuracy Degrees of Latitude: + +Bit 8 of octet 2 is the high order bit. + +Bit 1 of octet 5 is the low order bit. + +High Accuracy Degrees of Longitude: + +Bit 8 of octet 6 is the high order bit. + +Bit 1 of octet 9 is the low order bit. + +Orientation of major axis: + +angle in degrees between the major axis and north + +(0 = north, 90 = east, values of 180 and above are not used). + +U: Uncertainty Range + +Bit value 0 High Accuracy default uncertainty range used. + +Bit value 1 High Accuracy Extended Uncertainty Range used. + +### 7.3.4 Polygon + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | | | | +|---------------------------------|---|---|---|------------------|---|---|---|--|------------|--|--|--|--|--|--|--|--|--|--|--|--|--| +| 0 | 1 | 0 | 1 | Number of points | | | | | Octet 1 | | | | | | | | | | | | | | +| S1 | | | | | | | | | Octet 2 | | | | | | | | | | | | | | +| Degrees of latitude of point 1 | | | | | | | | | Octet 3 | | | | | | | | | | | | | | +| | | | | | | | | | Octet 4 | | | | | | | | | | | | | | +| | | | | | | | | | Octet 5 | | | | | | | | | | | | | | +| Degrees of longitude of point 1 | | | | | | | | | Octet 6 | | | | | | | | | | | | | | +| | | | | | | | | | Octet 7 | | | | | | | | | | | | | | +| | | | | | | | | | | | | | | | | | | | | | | | +| Sn | | | | | | | | | Octet 6n-4 | | | | | | | | | | | | | | +| Degrees of latitude of point n | | | | | | | | | Octet 6n-3 | | | | | | | | | | | | | | +| | | | | | | | | | Octet 6n-2 | | | | | | | | | | | | | | +| | | | | | | | | | Octet 6n-1 | | | | | | | | | | | | | | +| Degrees of longitude of point n | | | | | | | | | Octet 6n | | | | | | | | | | | | | | +| | | | | | | | | | Octet 6n+1 | | | | | | | | | | | | | | + +Figure 7: Shape description of a polygon + +The number of points field encodes in binary on 4 bits the number $n$ of points in the description, and ranges from 3 to 15. + +### 7.3.5 Ellipsoid Point with Altitude + +The coding of an ellipsoid point with altitude is described in figure 8. + +![Figure 8: Shape description of an ellipsoid point with altitude. The diagram shows a table with 9 octets. Octet 1 contains bits 8-1 (1, 0, 0, 0, spare). Octet 2 starts with bit S. Octets 3-4 contain Degrees of latitude. Octets 5-7 contain Degrees of longitude. Octet 8 starts with bit D. Octet 9 contains Altitude.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | +|----------------------|---|---|---|-------|---|---|---|---------|---------| +| 1 | 0 | 0 | 0 | spare | | | | Octet 1 | | +| S | | | | | | | | | Octet 2 | +| Degrees of latitude | | | | | | | | | Octet 3 | +| | | | | | | | | | Octet 4 | +| | | | | | | | | | Octet 5 | +| Degrees of longitude | | | | | | | | | Octet 6 | +| | | | | | | | | | Octet 7 | +| D | | | | | | | | | Octet 8 | +| Altitude | | | | | | | | | Octet 9 | + +Figure 8: Shape description of an ellipsoid point with altitude. The diagram shows a table with 9 octets. Octet 1 contains bits 8-1 (1, 0, 0, 0, spare). Octet 2 starts with bit S. Octets 3-4 contain Degrees of latitude. Octets 5-7 contain Degrees of longitude. Octet 8 starts with bit D. Octet 9 contains Altitude. + +**Figure 8: Shape description of an ellipsoid point with altitude** + +D: Direction of Altitude + +Bit value 0 Altitude expresses height + +Bit value 1 Altitude expresses depth + +Altitude + +Bit 1 of octet 9 is the low order bit + +### 7.3.6 Ellipsoid Point with altitude and uncertainty ellipsoid + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | | | | | +|---------------------------|------------------------|---|---|-------|---|---|---|----------|--|--|--|--|--|--|--|--|--|--|--| +| 1 | 0 | 0 | 1 | spare | | | | Octet 1 | | | | | | | | | | | | +| S | | | | | | | | Octet 2 | | | | | | | | | | | | +| Degrees of latitude | | | | | | | | Octet 3 | | | | | | | | | | | | +| | | | | | | | | Octet 4 | | | | | | | | | | | | +| | | | | | | | | Octet 5 | | | | | | | | | | | | +| Degrees of longitude | | | | | | | | Octet 6 | | | | | | | | | | | | +| | | | | | | | | Octet 7 | | | | | | | | | | | | +| D | | | | | | | | Octet 8 | | | | | | | | | | | | +| Altitude | | | | | | | | Octet 9 | | | | | | | | | | | | +| 0
spare | Uncertainty semi-major | | | | | | | Octet 10 | | | | | | | | | | | | +| 0
spare | Uncertainty semi-minor | | | | | | | Octet 11 | | | | | | | | | | | | +| Orientation of major axis | | | | | | | | Octet 12 | | | | | | | | | | | | +| 0
spare | Uncertainty Altitude | | | | | | | Octet 13 | | | | | | | | | | | | +| 0
spare | Confidence | | | | | | | Octet 14 | | | | | | | | | | | | + +Figure 9: Shape description of an ellipsoid point with altitude and uncertainty ellipsoid + +#### 7.3.6a High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid + +![](474a819357587e34949a3e110ff19b30_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------------|-----------------------|---|---|-------|---|---|---|----------| +| 1100 | | | | Spare | | | | Octet 1 | +| | | | | | | | | Octet 2 | +| High Accuracy Degrees of Latitude
(High Accuracy Point) | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| | | | | | | | | Octet 5 | +| | | | | | | | | Octet 6 | +| High Accuracy Degrees of Longitude
(High Accuracy Point) | | | | | | | | Octet 7 | +| | | | | | | | | Octet 8 | +| | | | | | | | | Octet 9 | +| 0 Spare | 0 Spare | | | | | | | Octet 10 | +| High Accuracy Altitude | | | | | | | | Octet 11 | +| | | | | | | | | Octet 12 | +| High Accuracy Uncertainty semi-major | | | | | | | | Octet 13 | +| High Accuracy Uncertainty semi-minor | | | | | | | | Octet 14 | +| Orientation of major axis | | | | | | | | Octet 15 | +| 0 Spare | Horizontal Confidence | | | | | | | Octet 16 | +| High Accuracy Uncertainty Altitude | | | | | | | | Octet 17 | +| 0 Spare | Vertical Confidence | | | | | | | Octet 18 | + +**Figure 7.3.6a-1: Shape description of an High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid** + +High Accuracy Degrees of Latitude: + +Bit 8 of octet 2 is the high order bit. + +Bit 1 of octet 5 is the low order bit. + +High Accuracy Degrees of Longitude: + +Bit 8 of octet 6 is the high order bit. + +Bit 1 of octet 9 is the low order bit. + +High Accuracy Altitude: + +Bit 6 of octet 10 is the high order bit. + +Bit 1 of octet 12 is the low order bit. + +Orientation of major axis: + +angle in degrees between the major axis and north + +(0 = north, 90 = east, values of 180 and above are not used). + +NOTE: The same "High Accuracy Uncertainty" (defined in clause 6.2a) is used for both horizontal and vertical location. + +#### 7.3.6b High Accuracy Ellipsoid point with altitude and scalable uncertainty ellipsoid + +![](7d2d1d3870cd224c4430d19334557716_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------------------------|-----------------------|---|---|-------|---|---|---|----------| +| 1110 | | | | Spare | | | | Octet 1 | +| | | | | | | | | Octet 2 | +| High Accuracy Degrees of Latitude
(High Accuracy Point) | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| | | | | | | | | Octet 5 | +| | | | | | | | | Octet 6 | +| High Accuracy Degrees of Longitude
(High Accuracy Point) | | | | | | | | Octet 7 | +| | | | | | | | | Octet 8 | +| | | | | | | | | Octet 9 | +| 0 Spare | 0 Spare | | | | | | | Octet 10 | +| High Accuracy Altitude | | | | | | | | Octet 11 | +| | | | | | | | | Octet 12 | +| High Accuracy Uncertainty semi-major | | | | | | | | Octet 13 | +| High Accuracy Uncertainty semi-minor | | | | | | | | Octet 14 | +| Orientation of major axis | | | | | | | | Octet 15 | +| HU | Horizontal Confidence | | | | | | | Octet 16 | +| High Accuracy Uncertainty Altitude | | | | | | | | Octet 17 | +| VU | Vertical Confidence | | | | | | | Octet 18 | + +**Figure 7.3.6b-1: Shape description of a High Accuracy Ellipsoid point with altitude and uncertainty ellipsoid** + +High Accuracy Degrees of Latitude: + +Bit 8 of octet 2 is the high order bit. + +Bit 1 of octet 5 is the low order bit. + +High Accuracy Degrees of Longitude: + +Bit 8 of octet 6 is the high order bit. + +Bit 1 of octet 9 is the low order bit. + +High Accuracy Altitude: + +Bit 6 of octet 10 is the high order bit. + +Bit 1 of octet 12 is the low order bit. + +Orientation of major axis: + +angle in degrees between the major axis and north + +(0 = north, 90 = east, values of 180 and above are not used). + +##### HU: Horizontal Uncertainty Range + +Bit value 0 High Accuracy default uncertainty range used. + +Bit value 1 High Accuracy Extended Uncertainty Range used. + +##### VU: Vertical Uncertainty Range + +Bit value 0 High Accuracy default uncertainty range used. + +Bit value 1 High Accuracy Extended Uncertainty Range used. + +NOTE: Horizontal and vertical accuracy are coded as specified by "High Accuracy Uncertainty" (defined in clause 6.2a) or "High Accuracy Extended Uncertainty" (defined in clause 6.2b). Different coding can be used for horizontal and vertical location components. + +### 7.3.7 Ellipsoid Arc + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | | +|----------------------|--------------------|---|---|-------|---|---|---|---------|----------|--|--|--|--|--|--| +| 1 | 0 | 1 | 0 | Spare | | | | Octet 1 | | | | | | | | +| S | | | | | | | | | Octet 2 | | | | | | | +| Degrees of latitude | | | | | | | | | Octet 3 | | | | | | | +| | | | | | | | | | Octet 4 | | | | | | | +| | | | | | | | | | Octet 5 | | | | | | | +| Degrees of longitude | | | | | | | | | Octet 6 | | | | | | | +| | | | | | | | | | Octet 7 | | | | | | | +| Inner radius | | | | | | | | | Octet 8 | | | | | | | +| | | | | | | | | | Octet 9 | | | | | | | +| 0
spare | Uncertainty radius | | | | | | | | Octet 10 | | | | | | | +| Offset angle | | | | | | | | | Octet 11 | | | | | | | +| Included angle | | | | | | | | | Octet 12 | | | | | | | +| 0
spare | Confidence | | | | | | | | Octet 13 | | | | | | | + +Figure 10: Shape description of an Ellipsoid arc + +Inner radius: + +Bit 8 of octet 8 is the high order bit. + +Bit 1 of octet 9 is the low order bit. + +# 8 Description of Velocity + +A description of velocity is applicable to any target entity on or close to the surface of the WGS84 ellipsoid. + +## 8.1 Horizontal Velocity + +Horizontal velocity is characterised by the horizontal speed and bearing. The horizontal speed gives the magnitude of the horizontal component of the velocity of a target entity. The bearing provides the direction of the horizontal component of velocity taken clockwise from North. + +![Figure 11: Description of Horizontal Velocity with Uncertainty. A diagram showing a horizontal plane with a North arrow pointing upwards. A vector is drawn from the origin, labeled 'Magnitude'. The angle between the North arrow and the vector is labeled 'Bearing'. The vector is shown as a double-headed arrow, indicating uncertainty.](d9a8b92ba7fc661ebe736ba3e4088eb5_img.jpg) + +Figure 11: Description of Horizontal Velocity with Uncertainty. A diagram showing a horizontal plane with a North arrow pointing upwards. A vector is drawn from the origin, labeled 'Magnitude'. The angle between the North arrow and the vector is labeled 'Bearing'. The vector is shown as a double-headed arrow, indicating uncertainty. + +Figure 11: Description of Horizontal Velocity with Uncertainty + +## 8.2 Horizontal and Vertical Velocity + +Horizontal and vertical velocity is characterised by horizontal speed, bearing, vertical speed and direction. The horizontal speed and bearing characterise the horizontal component of velocity. The vertical speed and direction provides the component of velocity of a target entity in a vertical direction. + +## 8.3 Horizontal Velocity with Uncertainty + +Horizontal velocity with uncertainty is characterised by a horizontal speed and bearing, giving a horizontal velocity vector $\underline{V}$ and an uncertainty speed $s$ . It describes the set of velocity vectors $\underline{v}$ related to the given velocity $\underline{V}$ as follows: + +$$|\underline{v} - \underline{V}| \leq s$$ + +![Figure 12: Description of Horizontal Velocity with Uncertainty. A 2D coordinate system with horizontal axis Vx and vertical axis Vy. A vector V is drawn from the origin. A dashed circle of radius s is centered at the tip of vector V. Another vector v is drawn from the origin to a point on the circle, representing a possible velocity vector within the uncertainty range.](e15f9dc3ef94138759781dc3c620b48d_img.jpg) + +Figure 12: Description of Horizontal Velocity with Uncertainty. A 2D coordinate system with horizontal axis Vx and vertical axis Vy. A vector V is drawn from the origin. A dashed circle of radius s is centered at the tip of vector V. Another vector v is drawn from the origin to a point on the circle, representing a possible velocity vector within the uncertainty range. + +Figure 12: Description of Horizontal Velocity with Uncertainty + +## 8.4 Horizontal and Vertical Velocity with Uncertainty + +Horizontal and vertical velocity with uncertainty is characterised by a horizontal speed and bearing, giving a horizontal velocity vector $\underline{V}_{x,y}$ , a vertical speed and direction giving a vertical velocity component $V_z$ and uncertainty speeds $s_1$ and + +s2. It describes the set of velocity vectors $\underline{v}$ with horizontal and vertical components $\underline{v}_{x,y}$ , and $v_z$ that are related to the given velocity components $\underline{V}_{x,y}$ , and $V_z$ as follows: + +$$|\underline{v}_{x,y} - \underline{V}_{x,y}| \leq s1$$ + +$$|v_z - V_z| \leq s2$$ + +### 8.4a Relative Velocity with Uncertainty + +The relative velocity with uncertainty of a device B relative to a device A is characterised by a radial velocity component and a perpendicular transverse velocity component. The radial velocity component is characterized by a rate of change of a range between the device A and device B. The transverse velocity component is characterized by a rate of change of a direction to the device B from the device A, where the direction includes an angle of azimuth measured clockwise from North in a horizontal plane through the device A and an angle of elevation measured upwards or downwards in a vertical plane through the devices A and B from a horizontal plane through the device A. The rates of change of the range and the angles of azimuth and elevation can be each independently included or excluded in the relative velocity and each has an uncertainty and a confidence, + +![Figure 12a: Description of a Relative Velocity with Uncertainty. The diagram shows a horizontal plane through device A, with a North arrow pointing upwards. A vector from A to B represents the relative velocity. This vector is decomposed into a radial velocity component (along the line AB) and a transverse velocity component (perpendicular to the radial component). The azimuth angle is measured clockwise from North in the horizontal plane. The elevation angle is measured upwards from the horizontal plane.](d8b92bdf09d07cb6c7b6961db9f6c4bb_img.jpg) + +Figure 12a: Description of a Relative Velocity with Uncertainty. The diagram shows a horizontal plane through device A, with a North arrow pointing upwards. A vector from A to B represents the relative velocity. This vector is decomposed into a radial velocity component (along the line AB) and a transverse velocity component (perpendicular to the radial component). The azimuth angle is measured clockwise from North in the horizontal plane. The elevation angle is measured upwards from the horizontal plane. + +Figure 12a: Description of a Relative Velocity with Uncertainty + +## 8.5 Coding Principles + +Velocity is encoded as shown in Figure 13. The velocity type in bits 8-5 of octet 1 defines the type of velocity information in succeeding bits. + +![](6361dfaef83c9ffc3b147e1627ba76a1_img.jpg) + +| | | +|-------------------------------|---------| +| 8   7   6   5   4   3   2   1 | | +| Velocity Type | Octet 1 | +| Velocity Information | Octet 2 | +| | Etc... | + +Figure 13: General Coding of Velocity + +## 8.6 Coding of Velocity Type + +Table 3 shows the coding of the velocity type. + +**Table 3: Coding of Velocity Type** + +| Bits | | +|--------------|---------------------------------------------------| +| 4 3 2 1 | | +| 0 0 0 0 | Horizontal Velocity | +| 0 0 0 1 | Horizontal with Vertical Velocity | +| 0 0 1 0 | Horizontal Velocity with Uncertainty | +| 0 0 1 1 | Horizontal with Vertical Velocity and Uncertainty | +| other values | reserved for future use | + +## 8.7 Coding of Horizontal Speed + +Horizontal speed is encoded in increments of 1 kilometre per hour using a 16 bit binary coded number N. The relation between the number N and the horizontal speed $h$ (in kilometres per hour) it encodes is described by the following equations: + +$$N \leq h < N + 0.5 \quad (N = 0)$$ + +$$N - 0.5 \leq h < N + 0.5 \quad (0 < N < 2^{16}-1)$$ + +$$N - 0.5 \leq h \quad (N = 2^{16}-1)$$ + +## 8.8 Coding of Bearing + +Bearing is encoded in increments of 1 degree measured clockwise from North using a 9 bit binary coded number N. The relation between the number N and the bearing $b$ (in degrees) it encodes is described by the following equation: + +$$N \leq b < N+1$$ + +except for $360 \leq N < 511$ which are not used. + +## 8.9 Coding of Vertical Speed + +Vertical speed is encoded in increments of 1 kilometre per hour using 8 bits giving a number N between 0 and $2^8-1$ . The relation between the number N and the vertical speed $v$ (in kilometres per hour) it encodes is described by the following equations: + +$$N \leq v < N + 0.5 \quad (N = 0)$$ + +$$N - 0.5 \leq v < N + 0.5 \quad (0 < N < 2^8-1)$$ + +$$N - 0.5 \leq v \quad (N = 2^8-1)$$ + +## 8.10 Coding of Vertical Speed Direction + +Vertical speed direction is encoded using 1 bit: a bit value of 0 indicates upward speed; a bit value of 1 indicates downward speed. + +## 8.11 Coding of Uncertainty Speed + +Uncertainty speed is encoded in increments of 1 kilometre per hour using an 8 bit binary coded number N. The value of N gives the uncertainty speed except for $N=255$ which indicates that the uncertainty is not specified. + +## 8.12 Coding of Horizontal Velocity + +The coding of horizontal velocity is described in figure 14. + +![](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------|---|---|---|-------|---|---|---|---------| +| 0 | 0 | 0 | 0 | spare | | | | Octet 1 | +| Bearing | | | | | | | | Octet 2 | +| Horizontal Speed | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | + +**Figure 14: Coding of Horizontal Velocity** + +Bearing + +Bit 1 of octet 1 is the high order bit; bit 1 of octet 2 is the low order bit + +Horizontal Speed + +Bit 1 of octet 4 is the low order bit + +## 8.13 Coding of Horizontal with Vertical Velocity + +The coding of horizontal with vertical velocity is described in figure 15. + +![](40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------|---|---|---|-------|---|---|---|---------| +| 0 | 0 | 0 | 1 | spare | | D | | Octet 1 | +| Bearing | | | | | | | | Octet 2 | +| Horizontal Speed | | | | | | | | Octet 3 | +| | | | | | | | | Octet 4 | +| Vertical Speed | | | | | | | | Octet 5 | + +**Figure 15: Coding of Horizontal with Vertical Velocity** + +D: Direction of Vertical Speed + +Bit value 0 Upward + +Bit value 1 Downward + +## 8.14 Coding of Horizontal Velocity with Uncertainty + +The coding of horizontal velocity with uncertainty is described in figure 16. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | +|-------------------|---|---|---|-------|---|---|---|---------|--|--|--|--| +| 0 | 0 | 1 | 0 | spare | | | | Octet 1 | | | | | +| Bearing | | | | | | | | Octet 2 | | | | | +| Horizontal Speed | | | | | | | | Octet 3 | | | | | +| | | | | | | | | Octet 4 | | | | | +| Uncertainty Speed | | | | | | | | Octet 5 | | | | | + +Figure 16: Coding of Horizontal Velocity with Uncertainty + +## 8.15 Coding of Horizontal with Vertical Velocity and Uncertainty + +The coding of horizontal with vertical velocity and uncertainty is described in figure 17. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | +|------------------------------|---|---|---|-------|---|---|---|---------|--|--|--| +| 0 | 0 | 1 | 0 | spare | | | D | Octet 1 | | | | +| Bearing | | | | | | | | Octet 2 | | | | +| Horizontal Speed | | | | | | | | Octet 3 | | | | +| | | | | | | | | Octet 4 | | | | +| Vertical Speed | | | | | | | | Octet 5 | | | | +| Horizontal Uncertainty Speed | | | | | | | | Octet 6 | | | | +| Vertical Uncertainty Speed | | | | | | | | Octet 7 | | | | + +Figure 17: Coding of Horizontal with Vertical Velocity and Uncertainty + +# Annex A (informative): Element description in compact notation + +The notation is the one described in GSM 04.07 [2]. + +``` + + ::= + | + | + | + | + | + | + ; + + : := + 0000 (4) + ; + + ::= + + ; + + ::= + 0001 (4) + + ; + + ::= + 0011 (4) + + + + + ; + + ::= + 0101 + (val(Number of points)) ; + + ::= + 0011 | 0100 | 0101 | 0110 | 0111 | 1000 | 1001 | 1010 | + 1011 | 1100 | 1101 | 1110 | 1111 ; + + ::= + 1000 (4) + + ; + + ::= + + + ::= + 1001 (4) + + + + + +``` + +``` + + + ; + + ::= + <1010> spare(4) + + + ; + + + + ; + + ::= + | + | + | + ; + + : := + 0000 (3) + + ; + + : := + 0001 (2) + + + + ; + + : := + 0010 (3) + + + ; + + : := + 0011 (2) + + + + + + ; +``` + +# Annex B (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2004-12 | SP-26 | | | | | Created version 6.0.0 | | 6.0.0 | +| 2007-06 | SP-36 | - | - | - | | Update to Rel-7 version (MCC) | | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | | Update to Rel-8 version (MCC) | | 8.0.0 | +| 2009-12 | SP-46 | - | - | - | | Update to Rel-9 version (MCC) | | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | - | Update to Rel-10 version (MCC) | | 10.0.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | - | Update to Rel-12 version (MCC) | | 12.0.0 | +| 2015-12 | - | - | - | - | - | Update to Rel-13 version (MCC) | | 13.0.0 | +| 2017-03 | - | - | - | - | - | Update to Rel-14 version (MCC) | | 14.0.0 | +| 2018-03 | SP-79 | SP-180089 | 0014 | - | F | Correction to the speed encoding | | 14.1.0 | +| 2018-06 | SP-80 | - | - | - | | Update to Rel-15 version (MCC) | | 15.0.0 | +| 2018-09 | SP-81 | SP-180729 | 0015 | 1 | F | GAD shape(s) for high accuracy positioning | | 15.1.0 | +| 2020-07 | SP-88E | - | - | - | - | Update to Rel-16 version (MCC) | | 16.0.0 | +| 2021-03 | SP-91E | SP-210063 | 0018 | 1 | C | GAD shape for location estimate in Local Coordinates | | 17.0.0 | +| 2021-09 | SP-93E | SP-210913 | 0019 | 1 | F | Add message formats for Local 2D point with uncertainty ellipse and Local 3D point with uncertainty ellipsoid | | 17.1.0 | +| 2021-12 | SP-94E | SP-211279 | 0021 | 1 | A | Introducing new high accuracy GAD shape with scalable uncertainty | | 17.2.0 | +| 2023-06 | SP-100 | SP-230485 | 0022 | 1 | B | New GAD Shapes for Ranging and Sidelink Positioning Location Results | | 18.0.0 | +| 2023-09 | SP-101 | SP-230855 | 0025 | - | F | Remove Editor's Note on feasibility of the Relative Velocity with Uncertainty shape | | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23122/raw.md b/raw/rel-18/23_series/23122/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..11fafee929e7e1f13298ed2a43a43b633b5e83fd --- /dev/null +++ b/raw/rel-18/23_series/23122/raw.md @@ -0,0 +1,5056 @@ + + +# 3GPP TS 23.122 V18.5.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 1.1 References..... | 6 | +| 1.2 Definitions and abbreviations..... | 10 | +| 2 General description of idle mode ..... | 16 | +| 3 Requirements and technical solutions..... | 17 | +| 3.0 General ..... | 17 | +| 3.1 PLMN selection and roaming ..... | 18 | +| 3.1A CSG selection / restriction..... | 22 | +| 3.1B PLMN selection triggered by ProSe communications ..... | 23 | +| 3.1C PLMN selection triggered by V2X communication over PC5 ..... | 25 | +| 3.1D PLMN selection triggered by A2X communication over PC5 ..... | 27 | +| 3.2 Regional provision of service..... | 29 | +| 3.3 Borders between registration areas ..... | 30 | +| 3.4 Access control ..... | 30 | +| 3.4.1 Access control ..... | 30 | +| 3.4.2 Forbidden LA or TA for regional provision of service ..... | 31 | +| 3.5 No suitable cell (limited service state)..... | 31 | +| 3.6 CTS fixed part selection (A/Gb mode only) ..... | 33 | +| 3.7 NAS behaviour configuration ..... | 34 | +| 3.8 CAG selection (N1 mode only)..... | 34 | +| 3.9 SNPN selection ..... | 35 | +| 3.10 Minimization of service interruption..... | 36 | +| 3.11 Signal level enhanced network selection ..... | 38 | +| 4 Overall process structure..... | 39 | +| 4.1 Process goal..... | 39 | +| 4.2 States description..... | 39 | +| 4.3 List of states ..... | 40 | +| 4.3.1 List of states for the PLMN selection process..... | 40 | +| 4.3.1.1 List of states for automatic mode (figure 2a)..... | 40 | +| 4.3.1.2 List of states for manual mode (figure 2b) ..... | 40 | +| 4.3.2 Void ..... | 40 | +| 4.3.3 List of states for location registration (figure 3)..... | 40 | +| 4.4 PLMN selection process..... | 41 | +| 4.4.1 Introduction ..... | 41 | +| 4.4.2 Registration on a PLMN..... | 42 | +| 4.4.3 PLMN selection..... | 42 | +| 4.4.3.1 At switch-on or recovery from lack of coverage ..... | 43 | +| 4.4.3.1.1 Automatic Network Selection Mode Procedure..... | 44 | +| 4.4.3.1.2 Manual Network Selection Mode Procedure ..... | 49 | +| 4.4.3.1.3 Manual CSG selection..... | 52 | +| 4.4.3.2 User reselection..... | 54 | +| 4.4.3.2.1 Automatic Network Selection Mode..... | 54 | +| 4.4.3.2.2 Manual Network Selection Mode ..... | 54 | +| 4.4.3.2.3 Manual CSG selection..... | 54 | +| 4.4.3.3 In VPLMN ..... | 55 | +| 4.4.3.3.1 Automatic and manual network selection modes..... | 55 | +| 4.4.3.3.2 Manual CSG selection..... | 58 | +| 4.4.3.4 Investigation Scan for higher prioritized PLMN ..... | 58 | +| 4.4.3.5 Periodic attempts for signal level enhanced network selection ..... | 59 | +| 4.4.4 Abnormal cases ..... | 60 | +| 4.4.5 Roaming not allowed in this LA or TA..... | 60 | +| 4.4.6 Steering of roaming ..... | 60 | +| 4.5 Location registration process ..... | 61 | +| 4.5.1 General ..... | 61 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|------------| +| 4.5.2 | Initiation of Location Registration ..... | 61 | +| 4.5.3 | Periodic Location Registration ..... | 63 | +| 4.5.4 | IMSI attach/detach operation..... | 64 | +| 4.5.5 | No Suitable Cells In Location Area..... | 64 | +| 4.6 | Service indication (A/Gb mode only) ..... | 64 | +| 4.7 | Pageability of the mobile subscriber ..... | 64 | +| 4.8 | MM Restart Procedure ..... | 65 | +| 4.9 | SNPN selection process ..... | 65 | +| 4.9.1 | General ..... | 65 | +| 4.9.2 | Registration on an SNPN..... | 65 | +| 4.9.3 | SNPN selection..... | 65 | +| 4.9.3.0 | General..... | 65 | +| 4.9.3.1 | At switch-on or recovery from lack of coverage ..... | 73 | +| 4.9.3.1.0 | General ..... | 73 | +| 4.9.3.1.1 | Automatic SNPN selection mode procedure..... | 73 | +| 4.9.3.1.2 | Manual SNPN selection mode procedure ..... | 75 | +| 4.9.3.1.3 | Automatic SNPN selection mode procedure for onboarding services in SNPN ..... | 78 | +| 4.9.3.1.4 | Manual SNPN selection mode procedure for onboarding services in SNPN ..... | 79 | +| 4.9.3.1.5 | Void..... | 79 | +| 4.9.3.2 | User reselection..... | 79 | +| 4.9.3.2.0 | General ..... | 79 | +| 4.9.3.2.1 | Automatic SNPN selection mode..... | 80 | +| 4.9.3.2.2 | Manual SNPN selection mode procedure ..... | 81 | +| 4.9.3.3 | Additional conditions for SNPN selection for MS supports access to an SNPN providing access
for localized services in SNPN ..... | 81 | +| 4.9.4 | Abnormal cases ..... | 81 | +| 5 | Tables and Figures ..... | 83 | +| 6 | MS supporting access technologies defined both by 3GPP and 3GPP2 ..... | 89 | +| 6.1 | General ..... | 89 | +| Annex A (normative): | HPLMN Matching Criteria..... | 91 | +| Annex B (normative): | PLMN matching criteria to be of same country as VPLMN..... | 95 | +| Annex C (normative): | Control plane solution for steering of roaming in 5GS..... | 96 | +| C.0 | Requirements for 5G steering of roaming over the control plane..... | 96 | +| C.1 | General..... | 96 | +| C.1.1 | Steering of roaming over the control plane in a PLMN ..... | 96 | +| C.1.2 | Steering of roaming over the control plane in an SNPN ..... | 98 | +| C.2 | Stage-2 flow for steering of UE in VPLMN during registration ..... | 101 | +| C.3 | Stage-2 flow for steering of UE in HPLMN or VPLMN after registration ..... | 108 | +| C.4 | Enhanced 5G control plane steering of roaming for the UE in connected mode..... | 113 | +| C.4.1 | General ..... | 113 | +| C.4.2 | Applying SOR-CMCI in the UE ..... | 115 | +| C.4.3 | Stage-2 flow for providing UE with SOR-CMCI in HPLMN, VPLMN, subscribed SNPN or non-
subscribed SNPN after registration..... | 118 | +| C.5 | Stage-2 flow for steering of UE in SNPN during registration ..... | 121 | +| C.6 | Stage-2 flow for steering of UE in SNPN after registration ..... | 128 | +| C.7 | Stage-2 flow for providing UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in HPLMN or VPLMN
after registration ..... | 132 | +| C.8 | Stage-2 flow for providing UE with list of preferred PLMN/access technology combinations in
SNPN after registration..... | 135 | +| Annex D (informative): | Change history..... | 138 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document gives an overview of the tasks undertaken by the Core network protocols of a Mobile Station (MS) when in idle mode, that is, switched on but typically not having a dedicated channel allocated. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The conditions when the idle mode functions are performed by an MS in the UTRA RRC connected mode states are specified in 3GPP TS 25.331 [33]. The conditions when the idle mode functions are performed by an MS in the E-UTRAN are specified in 3GPP TS 36.304 [43]. The conditions when the idle mode functions are performed by an MS in the NG-RAN are specified in 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. The conditions when the idle mode functions are performed by an MS in the NG-RAN RRC inactive state are specified in 3GPP TS 36.331 [42] and 3GPP TS 38.331 [65]. + +The present document defines the PLMN selection for a multi mode MS that supports both 3GPP and 3GPP2 systems. The common PLMN selection logic covers also PLMNs that are available in 3GPP2 system, but the present document makes no changes on the cdma2000® signalling towards networks that are available via 3GPP2 system. + +The present document gives procedures for using the CSG cells, whenever such use is permitted. + +The present document gives procedures for using the CAG cells, when the MS supports CAG. + +The present document specifies the SNPN selection. + +This 3GPP TS outlines how the requirements of the 22 series Technical Specifications (especially 3GPP TS 22.011 [9]) on idle mode operation shall be implemented. Further details are given in 3GPP TS 24.008 [23]. + +Clause 2 of this 3GPP TS gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses. + +NOTE: cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA). + +The present document describes the procedures for control plane solution of steering of roaming in 5GS in annex C. + +Annex C is applicable to the MS, the AMF, the UDM and the SOR-AF in the 5GS. + +The present document does not consider GERAN Iu mode. + +## 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +[1] Void. + +- [2] Void. +- [3] Void. +- [4] Void. +- [5] Void. +- [6] Void. +- [7] Void. +- [8] Void. +- [9] 3GPP TS 22.011: "Service accessibility". +- [10] Void. +- [11] Void. +- [12] Void. +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. +- [18] Void. +- [19] Void. +- [20] Void. +- [21] Void. +- [22] Void. +- [22A] 3GPP TS 23.003: "Numbering, addressing and identification". +- [23] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification, Core Network Protocols - Stage 3". +- [23A] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [24] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path". +- [25] 3GPP TS 45.008: "Radio subsystem link control". +- [26] Void. +- [27] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [27A] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [28] Void. +- [29] Void. +- [30] Void. +- [31] Void. + +- [32] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". +- [33] 3GPP TS 25.331: "RRC Protocol Specification". +- [34] 3GPP TS 44.018: "Mobile radio interface layer 3 specification, Radio Resource Control Protocol". +- [35] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode". +- [35A] 3GPP TS 43.318: "Generic Access Network (GAN); Stage 2". +- [35B] 3GPP TS 44.318: "Generic Access Network (GAN); Mobile GAN interface layer 3 specification; Stage 3". +- [36] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [37] Void. +- [38] 3GPP TS 21.111: "USIM and IC card requirements". +- [39] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [40] 3GPP TS 31.102: "Characteristics of the USIM Application". +- [41] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM), Application Toolkit (USAT)". +- [42] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification". +- [43] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode". +- [44] 3GPP2 C.S0016-D v1.0: "Over-the-Air Service Provisioning of Mobile Stations in Spread Spectrum Standards". +- [45] 3GPP2 C.S0011-C v2.0: "Recommended Minimum Performance Standards for cdma2000 Spread Spectrum Mobile Stations". +- [46] 3GPP2 C.S0033-A v2.0: "Recommended Minimum Performance Standards for cdma2000 High Rate Packet Data Access Terminal". +- [47] 3GPP TS 24.285: "Allowed Closed Subscriber Group (CSG) List Management Object (MO)". +- [48] Void. +- [49] 3GPP TS 22.220: "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)". +- [50] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)". +- [51] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3". +- [52] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO)". +- [53] 3GPP TS 24.105: "Application specific Congestion control for Data Communication (ACDC) Management Object (MO)". +- [54] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities". +- [55] 3GPP TS 43.064: "Overall description of the GPRS Radio Interface; Stage 2". +- [56] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description". +- [57] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". + +- [58] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access". +- [59] 3GPP TS 24.386: "User Equipment (UE) to V2X control function; protocol aspects; Stage 3". +- [60] 3GPP TS 24.385: "V2X services Management Object (MO)". +- [61] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state". +- [62] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [63] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [64] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [65] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification". +- [66] 3GPP TS 33.501: "Security architecture and procedures for 5G System". +- [67] 3GPP TS 31.115: "Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications". +- [68] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and Functional Description". +- [69] 3GPP TS 23.221: "Architectural requirements". +- [70] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS)". +- [71] 3GPP TS 29.544: "5G System (5GS); Secured Packet Application Function (SP-AF) services; Stage 3". +- [72] 3GPP TS 29.571: "5G System (5GS); Common Data Types for Service Based Interfaces; Stage 3". +- [73] ETSI TS 102 225: "Smart Cards; Secured packet structure for UICC based applications". +- [74] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1". +- [75] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3". +- [76] ITU-T Recommendation E.212: "The international identification plan for public networks and subscriptions". +- [77] 3GPP TS 24.526: "UE policies for 5G System (5GS); Stage 3". +- [78] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3". +- [79] 3GPP TS 24.588: "Vehicle-to-Everything (V2X) services in 5G System (5GS); User Equipment (UE) policies; Stage 3". +- [80] 3GPP TS 24.554: " Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3". +- [81] 3GPP TS 24.555: "Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3". +- [82] 3GPP TS 29.504: "5G System; Unified Data Repository Services; Stage 3". +- [83] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository services for Subscription Data; Stage 3". +- [84] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [85] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2". +- [86] 3GPP TS 24.577: "Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3". + +- [87] 3GPP TS 24.578: "Aircraft-to-Everything (A2X) services in 5G System (5GS); UE policies; Stage 3". +- [88] 3GPP TS 29.550: "5G System; Steering of roaming application function services; Stage 3". + +## 1.2 Definitions and abbreviations + +For the purposes of the present document, the abbreviations defined in 3GPP TR 21.905 [36] apply. + +**(A/Gb mode only):** Indicates this clause applies only to a GSM system which operates in A/Gb mode. For multi system case this is determined by the current serving radio access network. + +**(Iu mode only):** Indicates this clause applies only to UMTS. For multi system case this is determined by the current serving radio access network. + +NOTE 1: In accordance with the description of packet services in Iu mode in 3GPP TS 24.008 [23], the terms 'CS/PS mode of operation' and 'PS mode of operation' are not used in the present document. Instead the terms 'MS operation mode A' and 'MS operation mode C' are used. + +**(S1 mode only):** Indicates this clause applies only to an EPS. For multi system case this is determined by the current serving radio access network. + +**Acceptable Cell:** This is a cell that the MS may camp on to make emergency calls or to access RLOS. It must satisfy criteria which are defined for A/Gb mode in 3GPP TS 43.022 [35], for Iu mode in 3GPP TS 25.304 [32], for S1 mode in 3GPP TS 36.304 [43], and for NR access in N1 mode in 3GPP TS 38.304 [61] and for E-UTRA access in N1 mode in 3GPP TS 36.304 [43]. For an MS in eCall only mode, an acceptable cell must further satisfy the criteria defined in clause 4.4.3.1.1. + +**Access Technology:** The access technology associated with a PLMN or SNPN. The MS uses this information to determine what type(s) of radio carrier to search for when attempting to select a specific PLMN or SNPN. The following access technologies are defined: GSM, UTRAN, GSM COMPACT, EC-GSM-IoT, cdma2000 1xRTT, cdma2000 HRPD, E-UTRAN (WB-S1 mode and NB-S1 mode), NG-RAN, satellite NG-RAN and satellite E-UTRAN (WB-S1 mode and NB-S1 mode). A PLMN may support more than one access technology. SNPNs only support NG-RAN. + +NOTE 2: Access technology "E-UTRAN" maps to core network type "EPC" and access technology "NG-RAN" maps to core network type "5GCN", see 3GPP TS 24.501 [64]. + +**ACDC:** Application specific Congestion control for Data Communication, see 3GPP TS 22.011 [9]. + +**Allowable PLMN:** In the case of an MS operating in MS operation mode A or B, this is a PLMN which is not in the list of "forbidden PLMNs" in the MS. In the case of an MS operating in MS operation mode C or an MS not supporting A/Gb mode and not supporting Iu mode, this is a PLMN which is not in the list of "forbidden PLMNs" and not in the list of "forbidden PLMNs for GPRS service" in the MS. + +**Allowable SNPN:** In the case of an MS operating in SNPN access operation mode over 3GPP access and for an SNPN candidate which is not an SNPN selected for localized services in SNPN, this is an SNPN which is not in the list of "permanently forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, and is not in the list of "temporarily forbidden SNPNs" which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. In the case of an MS operating in SNPN access mode and for an SNPN candidate which is an SNPN selected for localized services in SNPN, this is an SNPN which is not in the list of "permanently forbidden SNPNs for access for localized services in SNPN" which is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, and is not in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" which is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. + +**Allowable PLMN/access technology combination:** For an MS operating in MS operation mode C or an MS not supporting A/Gb mode and not supporting Iu mode, this is an allowable PLMN in any specific access technology. For an MS operating in MS operation mode A or B, this is a PLMN/access technology combination where: + +- the PLMN is an allowable PLMN and the specific access technology is supporting non-GPRS services; or + +- the PLMN is not in the list of "forbidden PLMNs" and not in the list of "forbidden PLMNs for GPRS service" in the MS and the specific access technology is only supporting GPRS services. + +EXAMPLE: E-UTRAN, satellite E-UTRAN, satellite NG-RAN (see 3GPP TS 22.261 [74]) and NG-RAN are access technologies that are only supporting GPRS services. + +**Available PLMN:** For GERAN A/Gb mode see 3GPP TS 43.022 [35]. For UTRAN see 3GPP TS 25.304 [32]. For E-UTRAN see 3GPP TS 36.304 [43]. For satellite E-UTRAN see 3GPP TS 36.304 [43]. For NG-RAN see 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. For satellite NG-RAN, see 3GPP TS 38.304 [61]. For cdma2000® 1xRTT and cdma2000® HRPD see 3GPP2 C.S0016 [44]. + +**Available SNPN:** For NG-RAN see 3GPP TS 38.304 [61]. + +**Available PLMN/access technology combination:** This is an available PLMN in a specific access technology. + +**CAG-ID authorized based on "Allowed CAG list":** A CAG-ID in an "Allowed CAG list", without a time validity information, or with a time validity information with at least one time period matching UE's current time. + +**Camped on a cell:** The MS (ME if there is no SIM) has completed the cell selection/reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN or the SNPN may not be aware of the existence of the MS (ME) within the chosen cell. + +**Country:** A country is identified by a single MCC value defined in ITU-T recommendation E.212 [76], with the exception of the following MCC ranges that identify a single country: + +- values 310 through 316 (USA); +- values 404 through 406 (India); +- values 440 through 441 (Japan); +- values 460 through 461 (China); and +- values 234 through 235 (United Kingdom). + +**Permitted CSG list:** See 3GPP TS 36.304 [43]. + +**Current serving cell:** This is the cell on which the MS is camped. + +**CTS MS:** An MS capable of CTS services is a CTS MS. + +**Discontinuous coverage:** Deployment option for satellite E-UTRAN access, in which shorter periods of satellite E-UTRAN access radio coverage are followed by longer periods of satellite E-UTRAN access coverage gaps. During coverage gaps, the access stratum may be deactivated. For more details see 3GPP TS 23.401 [58] and 3GPP TS 36.304 [43]. + +**EAB:** Extended Access Barring, see 3GPP TS 22.011 [9]. + +**Extended Coverage in GSM for Internet of Things (EC-GSM-IoT):** Extended coverage in GSM for IoT is a feature which enables extended coverage operation. See 3GPP TS 43.064 [55]. + +**EHPLMN:** Any of the PLMN entries contained in the Equivalent HPLMN list. + +**Equivalent HPLMN list:** To allow provision for multiple HPLMN codes, PLMN codes that are present within this list shall replace the HPLMN code derived from the IMSI for PLMN selection purposes. This list is stored on the USIM and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the HPLMN code derived from the IMSI is not present in the EHPLMN list then it shall be treated as a Visited PLMN for PLMN selection purposes. + +**Generic Access Network (GAN):** See 3GPP TS 43.318 [35A]. + +**GAN mode:** See 3GPP TS 43.318 [35A]. + +**GPRS MS:** An MS capable of GPRS services is a GPRS MS. + +**MS operation mode:** See 3GPP TS 23.060 [27]. + +**High quality signal:** The high quality signal limit is used in the PLMN selection procedure. It is defined in the appropriate AS specification: 3GPP TS 43.022 [35] for the GSM radio access technology, 3GPP TS 25.304 [32] for the UMTS radio access technology (FDD or TDD mode), 3GPP TS 36.304 [43] for the E-UTRAN radio access technology (WB-S1 mode, NB-S1 mode, WB-N1 mode or NB-N1 mode), 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61] for the NG-RAN radio access technology. For 3GPP2 access technologies the high quality signal limit is defined in 3GPP2 C.S0011 [45] for cdma2000® 1xRTT and in 3GPP2 C.S0033 [46] for cdma2000® HRPD. A mobile station attempting to find a cell that supports EC-GSM-IoT (see 3GPP TS 43.064 [55]) does not use high quality signal limit in the PLMN selection procedure, i.e. for the purpose of PLMN selection, when attempting to find a cell that supports EC-GSM-IoT, any found cell supporting EC-GSM-IoT is considered to be received with high quality signal. A UE attempting to find a cell that supports enhanced coverage when operating in any WB-S1 or WB-N1 enhanced coverage mode does not use high quality signal limit in the PLMN selection procedure, i.e. for the purpose of PLMN selection, when attempting to find a cell that supports enhanced coverage, any found cell supporting enhanced coverage and satisfying the coverage specific quality signal limit defined for CE mode (see 3GPP TS 36.304 [43]) is considered to be received with high quality signal. + +**Home PLMN:** This is a PLMN where the MCC and MNC of the PLMN identity match the MCC and MNC of the IMSI. Matching criteria are defined in Annex A. + +**In A/Gb mode:** Indicates this clause applies only to a GSM system which operates in A/Gb mode. For multi system case this is determined by the current serving radio access network. + +**In Iu mode:** Indicates this clause applies only to UMTS. For multi system case this is determined by the current serving radio access network. + +**In N1 mode:** Indicates this clause applies only to an 5GS. For multi system case this is determined by the current serving radio access network. + +**In NB-N1 mode:** Indicates this paragraph applies only to a system which operates in NB-N1 mode. For a multi-access system this case applies if the current serving radio access network provides access to 5G network services via E-UTRA connected to 5GCN by NB-IoT (see 3GPP TS 36.300 [56], 3GPP TS 36.331 [42], 3GPP TS 36.306 [54]). + +**In WB-N1 mode:** Indicates this paragraph applies only to a system which operates in WB-N1 mode. For a multi-access system this case applies if the system operates in N1 mode with E-UTRA connected to 5GCN, but not in NB-N1 mode. + +**In S1 mode:** Indicates this clause applies only to an EPS. The S1 mode includes WB-S1 mode and NB-S1 mode. For multi system case this is determined by the current serving radio access network. + +**In NB-S1 mode:** Indicates this paragraph applies only to a system which operates in NB-S1 mode. For a multi-access system this case applies if the current serving radio access network provides access to network services via E-UTRA by NB-IoT (see 3GPP TS 36.300 [56], 3GPP TS 36.331 [22], 3GPP TS 36.306 [54]). + +**In WB-S1 mode:** Indicates this paragraph applies only to a system which operates in WB-S1 mode. For a multi-access system this case applies if the system operates in S1 mode, but not in NB-S1 mode. + +**Limited Service State:** See clause 3.5. + +**Localised Service Area (LSA):** A localised service area consists of a cell or a number of cells. The cells constituting a LSA may not necessarily provide contiguous coverage. + +**Localized services in NPN:** Localized services in NPN are services, which are provided by an NPN at specific or limited area, are bounded in time, or both. + +**Localized services in SNPN:** Localized services in SNPN are localized services in NPN, which are provided by an SNPN at specific or limited area, are bounded in time, or both. + +**Location Registration (LR):** An MS which is IMSI attached to non-GPRS services only performs location registration by the location updating procedure. A GPRS MS which is IMSI attached to GPRS services or to GPRS and non-GPRS services performs location registration by the routing area update procedure only when in a network of network operation mode I. Both location updating and routing area update procedures are performed independently by the GPRS MS when it is IMSI attached to GPRS and non-GPRS services in a network of network operation mode II (see 3GPP TS 23.060 [27]). An MS which is attached via the E-UTRAN performs location registration by the tracking area update procedure. An MS which is registered via the NG-RAN performs location registration by the registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]). + +**MINT: Minimization of service interruption (see 3GPP TS 22.261 [71]).** + +**MS:** Mobile Station. The present document makes no distinction between MS and UE. + +**N1 mode capability:** Capability of the UE associated with an N1 NAS signalling connection between the UE and network. The present document refers to the N1 mode capability over 3GPP access only (see 3GPP TS 24.501 [64]). + +**NarrowBand Internet of Things (NB-IoT):** NB-IoT is a non-backward compatible variant of E-UTRAN supporting a reduced set of functionality. NB-IoT allows access to EPC or 5GCN network services via E-UTRA with a channel bandwidth limited to 180 kHz (see 3GPP TS 36.300 [20], 3GPP TS 36.331 [42], 3GPP TS 36.306 [44]). + +**Network Type:** The network type associated with HPLMN or a PLMN on the PLMN selector (see 3GPP TS 31.102 [40]). The MS uses this information to determine what type of radio carrier to search for when attempting to select a specific PLMN. A PLMN may support more than one network type. + +**Onboarding services in SNPN:** Onboarding services in SNPN allow an MS to access an SNPN indicating that onboarding is allowed, using default UE credentials for primary authentication in order for the MS to be configured with one or more entries of the "list of subscriber data". + +NOTE 3: When the MS is registered for onboarding services in SNPN, services other than the onboarding services in SNPN are not available. When the MS is not registered for onboarding services in SNPN, onboarding services in SNPN are not available. + +**MS determined PLMN with disaster condition:** A PLMN to which a disaster condition applies, determined as described in clause 4.4.3.1.1. + +**Registered PLMN (RPLMN):** This is the PLMN on which certain LR outcomes have occurred (see table 1). In a shared network the RPLMN is the PLMN defined by the PLMN identity of the CN operator that has accepted the LR. + +**Registered SNPN (RSNPN):** This is the SNPN on which certain LR outcomes have occurred. In a shared network the RSNPN is the SNPN defined by the SNPN identity of the CN operator that has accepted the LR. + +**Registration:** This is the process of camping on a cell of the PLMN or the SNPN and doing any necessary LRs. + +**Registration Area:** A registration area is an area in which mobile stations may roam without a need to perform location registration. The registration area corresponds to location area (LA) for performing location updating procedure, to routing area for performing the GPRS attach or routing area update procedures, and to a list of tracking areas (TAs) for performing the EPS attach, tracking area update, or 5GS registration procedure. + +The PLMN to which a cell belongs (PLMN identity): + +- for GERAN, in the system information (MCC + MNC part of LAI) broadcast as specified in 3GPP TS 44.018 [34]; +- for UTRA, see the broadcast information as specified in 3GPP TS 25.331 [33]; +- for E-UTRA, see the broadcast information as specified in 3GPP TS 36.331 [42]; and +- for NR, see the broadcast information as specified in 3GPP TS 38.331 [65]. + +The SNPN to which a cell belongs (SNPN identity): + +- for NR, see the broadcast information as specified in 3GPP TS 38.331 [65]. + +In a shared network, a cell belongs to all PLMNs given in the system information broadcasted as specified in 3GPP TS 44.018 [34] for GERAN, in 3GPP TS 25.331 [33] for UTRAN, and in 3GPP TS 36.331 [42] for E-UTRAN, and a cell belongs to all PLMNs, all SNPNs, or all PLMNs and all SNPNs, given in the system information broadcasted as specified in 3GPP TS 36.331 [42] for E-UTRA connected to 5GCN, and in 3GPP TS 38.331 [65] for NR. + +**Secured packet:** In this specification, a secured packet contains one or more of the following: + +- list of preferred PLMN/access technology combinations; +- SOR-CMCI; and +- SOR-SENSE + +encapsulated with a security mechanism as described in 3GPP TS 31.115 [67]. + +**Selected PLMN:** This is the PLMN that has been selected according to clause 3.1, either manually or automatically. + +**Selected SNPN:** This is the SNPN that has been selected according to clause 3.9, either manually or automatically. + +**Shared MCC:** MCC assigned by ITU-T as shared MCC according to ITU-T E.212 [76], except within this specification for PLMN selection purposes the MCC of value 999 is not considered a shared MCC. + +**Shared Network:** An MS considers a cell to be part of a shared network, when multiple PLMN identities are received as specified in 3GPP TS 44.018 [34] for GERAN, in 3GPP TS 25.331 [33] for UTRAN, and in 3GPP TS 36.331 [42] for E-UTRAN, and when multiple PLMN identities, multiple SNPN identities or one or more PLMN identities and one or more SNPN identities are received as specified in 3GPP TS 36.331 [42] for E-UTRA connected to 5GCN, and in 3GPP TS 38.331 [65] for NR. + +**SIM:** Subscriber Identity Module (see 3GPP TS 21.111 [38]). The present document makes no distinction between SIM and USIM. + +**SNPN identity:** a PLMN ID and an NID combination. + +**SoLSA exclusive access:** Cells on which normal camping is allowed only for MS with Localised Service Area (LSA) subscription. + +**Steering of Roaming (SOR):** A technique whereby a roaming UE is encouraged to roam to a preferred roamed-to-network indicated by the HPLMN. + +**Steering of Roaming application function (SOR-AF):** An application function that can provide UDM with one of the following: + +- a) one or more of the following: + - list of preferred PLMN/access technology combinations; + - SOR-CMCI, together with the "Store SOR-CMCI in ME" indicator if applicable; + - SOR-SNPN-SI; and + - SOR-SNPN-SI-LS; +- b) a secured packet, together with the indicator, if applicable, that "the list of preferred PLMN/access technology combinations is not included in the secured packet"; or +- c) neither of a) or b), + +generated dynamically based on operator specific data analytics solutions. + +**Steering of roaming connected mode control information (SOR-CMCI):** HPLMN information to control the timing for a UE in connected mode to move to idle mode in order to perform steering of roaming. + +**Steering of roaming operator controlled signal threshold per access technology information (SOR-SENSE):** Home operator's provision of "Operator controlled signal threshold per access technology" for signal level enhance network selection (SENSE). This information is the EFOCST file provided in the secured packet by network. + +**Steering of Roaming information:** This consists of the following HPLMN or subscribed SNPN protected information (see 3GPP TS 33.501 [66]): + +- a) the following indicators, of whether: + - the UDM requests an acknowledgement from the UE for successful reception of the steering of roaming information. + - the UDM requests the UE to store the SOR-CMCI in the ME, which is provided along with the SOR-CMCI in plain text; and +- b) one of the following: + - 1) one or more of the following: + - list of preferred PLMN/access technology combinations with an indication that it is included; + +- SOR-CMCI; + - SOR-SNPN-SI; and + - SOR-SNPN-SI-LS; +- 2) a secured packet with an indication that it is included; + - 3) the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'; or + - 4) the subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'. + +**Steering of roaming SNPN selection information (SOR-SNPN-SI):** Provisioning information for SNPN selection consisting of: + +- a) the credentials holder controlled prioritized list of preferred SNPNs; +- b) the credentials holder controlled prioritized list of GINs; or +- c) both of the above. + +**Steering of roaming SNPN selection information for localized services in SNPN (SOR-SNPN-SI-LS):** Provisioning information for SNPN selection by an MS supporting access to an SNPN providing access for localized services in SNPN consisting of: + +- a) a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", where each entry contains: + - 1) an SNPN identity; + - 2) a validity information consisting of time validity information and optionally, location validity information; and + - 3) optionally, location assistance information; +- b) a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains: + - 1) a GIN; + - 2) a validity information consisting of time validity information and optionally, location validity information; and + - 3) optionally, location assistance information; or +- c) both of the above. + +**Subscribed SNPN:** An SNPN for which the UE has a subscription. + +**Suitable Cell:** This is a cell on which an MS may camp. It must satisfy criteria which are defined for GERAN A/Gb mode in 3GPP TS 43.022 [35], for UTRAN in 3GPP TS 25.304 [32], for E-UTRAN in 3GPP TS 36.304 [43] and for NG-RAN see 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. For 3GPP2 access technologies the criteria are defined in 3GPP2 C.S0011 [45] for cdma2000® 1xRTT and in 3GPP2 C.S0033 [46] for cdma2000® HRPD. For an MS in eCall only mode, a suitable cell must further satisfy the criteria defined in clause 4.4.3.1.1. + +**Visited PLMN:** This is a PLMN different from the HPLMN (if the EHPLMN list is not present or is empty) or different from an EHPLMN (if the EHPLMN list is present). + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.167 [57] apply: + +**eCall over IMS** +**EPC** +**E-UTRAN** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.401 [58] apply: + +### **eCall only mode** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.221 [69] apply: + +### **Restricted local operator services (RLOS)** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [62] apply: + +### **Closed Access Group (CAG)** + +### **Credentials holder** + +### **Group ID for Network Selection (GIN)** + +### **Network identifier (NID)** + +### **NG-RAN** + +### **NR RedCap** + +### **Stand-alone Non-Public Network (SNPN)** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.501 [64] apply: + +### **5GCN** + +### **CAG cell** + +### **Emergency PDU session** + +### **Initial registration for emergency services** + +### **Initial registration for onboarding services in SNPN** + +### **Non-CAG cell** + +### **NSSAI** + +#### **Registered for emergency services** + +### **Registered for onboarding services in SNPN** + +### **SNPN access operation mode** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.261 [74] apply: + +### **Disaster condition** + +### **Disaster roaming** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.501 [66] apply: + +### **Default UE credentials for primary authentication** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.229 [84] apply: + +### **IMS registration related signalling** + +# --- 2 General description of idle mode + +When an MS is switched on, it attempts to make contact with a public land mobile network (PLMN) or stand-alone non-public network (SNPN). The particular PLMN or SNPN to be contacted may be selected either automatically or manually. + +The MS looks for a suitable cell of the chosen PLMN or SNPN and chooses that cell to provide available services, and tunes to its control channel. This choosing is known as "camping on the cell". The MS will then register its presence in the registration area of the chosen cell if necessary, by means of a location registration (LR), GPRS attach, IMSI attach or registration procedure. + +If the MS loses coverage of a cell, or find a more suitable cell, it reselects onto the most suitable cell of the selected PLMN or SNPN and camps on that cell. If the new cell is in a different registration area, an LR request is performed. + +If the MS loses coverage of a PLMN or SNPN, either a new PLMN or SNPN is selected automatically, or an indication of which PLMNs or SNPNs are available is given to the user, so that a manual selection can be made. + +Registration is not performed by MSs only capable of services that need no registration. + +The purpose of camping on a cell in idle mode is fourfold: + +- a) It enables the MS to receive system information from the PLMN or SNPN. +- b) If the MS wishes to initiate a call, it can do this by initially accessing the network on the control channel of the cell on which it is camped. +- c) If the PLMN or SNPN receives a call for the MS, it knows (in most cases) the registration area of the cell in which the MS is camped. It can then send a "paging" message for the MS on control channels of all the cells in the registration area. The MS will then receive the paging message because it is tuned to the control channel of a cell in that registration area, and the MS can respond on that control channel. +- d) It enables the MS to receive cell broadcast messages. + +If the MS is unable to find a suitable cell to camp on, or the SIM is not inserted, or there is no valid entry in "list of subscriber data" in case the MS is operating in SNPN access operation mode over 3GPP access, or if it receives certain responses to an LR request (e.g., "illegal MS"), it attempts to camp on a cell irrespective of the PLMN identity or the SNPN identity, and enters a "limited service" state in which it can only attempt to make emergency calls or to access RLOS. An MS operating in NB-S1 mode, never attempts to make emergency calls or to access RLOS. An MS operating in N1 mode never attempts to access RLOS. + +If the MS is in eCall only mode, it attempts to camp on a suitable cell and enters an "eCall inactive" state in which it can only attempt an eCall over IMS, or a call to a non-emergency MSISDN or URI for test or terminal reconfiguration services as specified in 3GPP TS 31.102 [40]. + +If the MS is in eCall only mode and is unable to find a suitable cell to camp on, it attempts to camp on an acceptable cell in limited service state, and enters an "eCall inactive" state in which it can only attempt an eCall over IMS. + +While in eCall inactive state, the MS does not perform LR with the PLMN of the cell on which the MS is camped. + +In A/Gb mode, if the CTS MS is in CTS mode only or in automatic mode with CTS preferred, it will start by attempting to find a CTS fixed part on which it is enrolled. + +The idle mode tasks can be subdivided into the following processes: + +- PLMN selection; +- SNPN selection (N1 mode only); +- CSG selection (Iu mode and S1 mode only); +- Cell selection and reselection; +- Location registration; +- CTS fixed part selection (A/Gb mode only); and +- CAG selection (N1 mode only). + +In A/Gb mode, to make this initial CTS fixed part selection, the MS shall be enrolled on at least one fixed part. + +Except for SNPN selection, the relationship between these processes is illustrated in figure 1 in clause 5. The states and state transitions within each process are shown in figure 2a, figure 2b, and figure 3 in clause 5. + +In the present document, EMM-IDLE mode with suspend indication (see 3GPP TS 24.301 [23A]) and 5GMM-IDLE mode with suspend indication (see 3GPP TS 24.501 [64]) shall be considered the same as idle mode. + +# --- 3 Requirements and technical solutions + +## 3.0 General + +The following clauses list the main requirements of idle mode operation and give an outline of the technical solution. + +## 3.1 PLMN selection and roaming + +The MS normally operates on its home PLMN (HPLMN) or equivalent home PLMN (EHPLMN). However, a visited PLMN (VPLMN) may be selected, e.g., if the MS loses coverage. There are two modes for PLMN selection: + +- i) Automatic mode - This mode utilizes a list of PLMN/access technology combinations in priority order. The highest priority PLMN/access technology combination which is available and allowable is selected. +- ii) Manual mode - Here the MS indicates to the user which PLMNs are available. Only when the user makes a manual selection does the MS try to obtain normal service on the VPLMN. + +To prevent repeated attempts to have roaming service on a not allowed area (i.e. LA or TA), when the MS is informed that an area is forbidden, the LA or TA is added to a list of "forbidden location areas for roaming" or "forbidden tracking areas for roaming" respectively which is stored in the MS. These lists, if existing, are deleted when the MS is switched off or when the SIM is removed, and periodically (with period in the range 12 to 24 hours). LA area restrictions are always valid for complete location areas independent of possible subdivision into GPRS routing areas. The structure of the routing area identifier (see 3GPP TS 23.003 [22A]) supports area restriction on LA basis. + +To prevent repeated attempts to obtain service on a PLMN through satellite NG-RAN or satellite E-UTRAN access technology, when the MS receives an integrity protected reject message with cause value #78 "PLMNs not allowed to operate at the present UE location" from a satellite NG-RAN cell or a satellite E-UTRAN cell, the MS maintains a list of "PLMNs not allowed to operate at the present UE location" in which it stores the PLMN ID of the rejecting PLMN, the current geographical location, if known by the MS. A timer is started when the PLMN ID of the rejecting PLMN is added to the list of "PLMNs not allowed to operate at the present UE location". If the geographical location exists, a MS implementation specific distance value needs to be stored. An entry in the list is deleted if the timer associated to the entry expires or the MS successfully registers to the PLMN stored in the entry. An entry in the list may be deleted if the current UE location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current UE location is larger than a UE implementation specific value. For details see 3GPP TS 24.501 [64] and 3GPP TS 24.301 [23A]. + +NOTE 1: The list of "PLMNs not allowed to operate at the present UE location" is provided to the AS, see 3GPP TS 38.304 [61]. + +In automatic PLMN selection mode, if the MS detects a PLMN in satellite NG-RAN access technology which is part of the list of "PLMNs not allowed to operate at the present UE location" the MS shall consider the PLMN as PLMN selection candidate for satellite NG-RAN access technology only if the current MS location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current MS location is larger than a MS implementation specific value. + +This does not prevent selection of such a PLMN if it is available in another RAT. + +A timer is started when the PLMN ID of the rejecting PLMN is added to the list of "PLMNs not allowed to operate at the present UE location". + +In automatic PLMN selection mode, if the MS detects a PLMN in satellite E-UTRAN access technology which is part of the list of "PLMNs not allowed to operate at the present UE location" the MS shall consider the PLMN as PLMN selection candidate for satellite E-UTRAN access technology only if the current MS location is known, a geographical location is stored for the entry of this PLMN, and the distance to the current UE location is larger than a UE implementation specific value. + +This does not prevent selection of such a PLMN if it is available in another RAT. + +If a message with cause value #15 (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]) is received by an MS, then the MS shall take the following actions depending on the mode in which the message was received: + +A/Gb mode or Iu mode: + +The location area is added to the list of "forbidden location areas for roaming" which is stored in the MS. The MS shall then search for a suitable cell in the same PLMN but belonging to an LA or TA which is not in the "forbidden location areas for roaming" or "forbidden tracking areas for roaming" list respectively. + +S1-mode: + +The tracking area is added to the list of "forbidden tracking areas for roaming" which is stored in the MS. The MS shall then search for a suitable cell in the same PLMN but belonging to a TA or LA which is not in the "forbidden tracking areas for roaming" or "forbidden location areas for roaming" list respectively + +N1-mode: + +The tracking area is added to the list of "5GS forbidden tracking areas for roaming" which is stored in the MS. The MS shall then search for a suitable cell in the same PLMN but belonging to a tracking area which is not in the "5GS forbidden tracking areas for roaming" list. + +In manual or automatic mode, a VPLMN is added to a list of "forbidden PLMNs" in the SIM if a message with cause value "PLMN not allowed" or "Requested service option not authorized in this PLMN" or "Serving network not authorized" is received by an MS in response to an LR request from that VPLMN and: + +- the MS is configured to use timer T3245 as defined in 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A], and 3GPP TS 24.501 [64]; +- the MS is not configured to use timer T3245 and the message is integrity-protected; +- the MS is not configured to use timer T3245, the message is not integrity-protected and the MS does not maintain a list of PLMN-specific attempt counters; or +- the MS is not configured to use timer T3245, the message is not integrity-protected, the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is equal to the MS implementation specific maximum value as defined in 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]. + +If: + +- after a subsequent manual selection of that PLMN, there is a successful LR not for disaster roaming services, then the PLMN is removed from the "forbidden PLMNs" list; +- the MS is configured to use timer T3245 and the timer T3245 expires, then the PLMN is removed from the "forbidden PLMNs" list ; or +- the MS is not configured to use timer T3245 and: + - 1) the MS maintains a list of PLMN-specific attempt counters, the value of the PLMN-specific attempt counter for that PLMN is greater than zero and less than the MS implementation specific maximum value, and timer T3247 expires, then the PLMN is removed from the "forbidden PLMNs" list stored in memory as defined in 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]; or + - 2) the MS does not maintain a list of PLMN-specific attempt counters, the PLMN is stored in the "forbidden PLMNs" list in the SIM, and the timer T3247 expires, then the PLMN is removed from the "forbidden PLMNs" list in the SIM as defined in 3GPP TS 24.301 [23A]. + +This list is retained when the MS is switched off or the SIM is removed. The HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present) shall not be stored on the list of "forbidden PLMNs". + +In A/Gb mode, an ME not supporting SoLSA may consider a cell with the escape PLMN code (see 3GPP TS 23.073) to be a part of a PLMN belonging to the list of "forbidden PLMNs". + +Optionally the ME may store in its memory an extension of the "forbidden PLMNs" list. The contents of the extension of the list shall be deleted when the MS is switched off or the SIM is removed. + +A VPLMN may be stored in the extension of the "forbidden PLMNs" list if a message with cause value "PLMN not allowed" or "Requested service option not authorized in this PLMN" or "Serving network not authorized" is received by an MS in response to an LR request from that VPLMN, and the following is valid: + +- the MS is not configured to use timer T3245, the message is not integrity-protected, the MS maintains a list of PLMN-specific attempt counters and the value of the PLMN-specific attempt counter for that VPLMN is less than an MS implementation specific maximum value as defined in 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]. + +In manual or automatic mode, if a message with cause value "GPRS services not allowed in this PLMN" or "EPS services not allowed in this PLMN" is received by an MS in response to an GPRS attach, routing area update, EPS attach or tracking area update request or received in a network initiated GPRS detach or EPS detach request (see 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A]) from a VPLMN, that VPLMN is added to a list of "forbidden PLMNs for GPRS service" which is stored in the MS. This list is deleted when the MS is switched off or when the SIM is removed. A PLMN is removed from the list of "forbidden PLMNs for GPRS service" if: + +- after a subsequent manual selection of that PLMN, there is a successful GPRS attach, routing area update, EPS attach, tracking area update or registration procedure (see 3GPP TS 24.501 [64]); +- the MS is configured to use timer T3245 and timer T3245 expires; or +- the MS is not configured to use timer T3245, the MS maintains a list of PLMN-specific PS-attempt counters as specified in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], the value of the PLMN-specific PS-attempt counter for that PLMN has a value greater than zero and less than the MS implementation-specific maximum value as defined in clause 5.3.7b in 3GPP TS 24.301 [23A], and T3247 expires. + +The maximum number of possible entries in this list is implementation dependant, but must be at least one entry. The HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present) shall not be stored on the list of "forbidden PLMNs for GPRS service". + +An MS that is attaching for emergency bearer services or for access to RLOS, or is attached for emergency bearer services or for access to RLOS, may access PLMNs in the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service". The MS shall not remove any entry from the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service" as a result of such accesses. + +An MS that is registered for disaster roaming services, may access PLMNs in the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service" following the criteria as specified in clause 4.4.3.1.1 and shall not remove any entry from the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service" as a result of such accesses. + +A UE capable of S101 mode maintains a list "forbidden PLMNs for attach in S101 mode"; the properties and handling in NAS signalling is defined in clause 5.3.3 of 3GPP TS 24.301 [23A]. + +If the MS is in GAN mode and a "Location not allowed" message is received (see 3GPP TS 44.318 [35B]), then the MS may attempt to select another PLMN so that further GAN registrations may again be attempted. The selection of the PLMN either automatically or manually is implementation dependent. + +If an MS that has disabled its E-UTRA capability re-enables it when PLMN selection is performed, then the MS of which usage setting is "voice centric": + +- should, for duration of timer TD, memorize the PLMNs where E-UTRA capability was disabled as PLMNs where voice service was not possible in E-UTRAN. The number of PLMNs where voice service was not possible in E-UTRAN that the MS can store is implementation specific, but it shall be at least one. The value of timer TD is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1. +- in automatic PLMN selection, shall not consider PLMNs where voice service was not possible in E-UTRAN as PLMN selection candidates for E-UTRA access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; and +- shall delete stored information on PLMNs where voice service was not possible in E-UTRAN when the MS is switched off, the USIM is removed, timer TD expires or MS voice domain configuration changes so that E-UTRA capability disabling is no longer necessary. + +The MS may support "E-UTRA Disabling for EMM cause #15" as specified in 3GPP TS 24.301 [23A]. If the MS supports "E-UTRA Disabling for EMM cause #15" and the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40] is present and set to enabled: + +- the MS shall maintain a list of "PLMNs with E-UTRAN not allowed"; +- when the MS disables its E-UTRA capability on a PLMN due to E-UTRAN not allowed, it shall add the PLMN to the "PLMNs with E-UTRAN not allowed" list, and start timer TE if timer TE is not already running; + +- the number of PLMNs that the MS can store in the "PLMNs with E-UTRAN not allowed" list is implementation specific, but it shall be at least one; +- the value of timer TE is MS implementation specific, but it shall not exceed the maximum possible value of background scanning timer T (8 hours or 240 hours for MSs supporting EC-GSM-IoT, Category M1 or Category NB1 as defined in 3GPP TS 36.306 [54]) as specified in clause 4.4.3.3.1; +- in automatic PLMN selection the MS shall not consider PLMNs included in the "PLMNs with E-UTRAN not allowed" list as PLMN selection candidates for E-UTRAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; and +- the MS shall delete stored information in the "PLMNs with E-UTRAN not allowed" list when the MS is switched off, the USIM is removed or timer TE expires. + +The MS should maintain a list of PLMNs where the N1 mode capability was disabled because IMS voice was not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible in N1 mode. When the MS disables its N1 mode capability because IMS voice was not available and the MS's usage setting was "voice centric": + +- the MS should add the identity of the PLMN to the list of PLMNs where voice service was not possible in N1 mode and should start timer TF if timer TF is not already running. The number of PLMNs that the MS can store where voice services is not possible is implementation specific, but it shall be at least one. The value of timer TF is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1; +- in automatic PLMN selection the MS shall not consider PLMNs where voice service was not possible in N1 mode as PLMN selection candidates for NG-RAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; and +- the MS shall delete stored information on PLMNs where voice service was not possible in N1 mode when the MS is switched off, the USIM is removed, timer TF expires or the MS's usage setting changes so that N1 mode capability disabling is no longer necessary. + +The MS should maintain a list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed", as PLMNs where N1 mode is not allowed for 3GPP access. When the MS disables its N1 mode capability due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed": + +- the MS should add the identity of the PLMN to the list of PLMNs where N1 mode is not allowed for 3GPP access and should start timer TG if timer TG is not already running. The number of PLMNs that the MS can store where N1 mode is not allowed for 3GPP access is implementation specific, but it shall be at least one. The value of timer TG is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1; +- in automatic PLMN selection the MS shall not consider PLMNs where N1 mode is not allowed for 3GPP access as PLMN selection candidates for NG-RAN access technology, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; +- if the MS is not configured to use timer T3245, the MS maintains a list of PLMN-specific N1 mode attempt counters for 3GPP access as specified in 3GPP TS 24.501 [64] and T3247 expires, then the MS removes for each PLMN-specific N1 mode attempt counter for 3GPP access that has a value greater than zero and less than the MS implementation-specific maximum value the respective PLMN from the list of PLMNs where N1 mode is not allowed for 3GPP access, as specified in clause 5.3.20.2 in 3GPP TS 24.501 [64]; and +- the MS shall delete stored information on PLMNs where N1 mode is not allowed for 3GPP access when the MS is switched off, the USIM is removed or timer TG expires. + +NOTE 2: The expiry of timer TG does not cause a reset of the PLMN-specific N1 mode attempt counters for 3GPP access (see 3GPP TS 24.501 [64]). + +NOTE 3: If an access technology is disabled for a PLMN that is part of the list of "equivalent PLMNs", the UE implementation ensures that registration to a different PLMN within the list of "equivalent PLMNs" does not result in reselection or inter-system change to the disabled access technology of that PLMN. + +The MS in NB-S1 mode may maintain a list of "PLMNs with NB-IoT not allowed" where the NB-IoT capability was disabled due to receipt of a reject from the network with EMM cause #15 "no suitable cells in tracking area" and an Extended EMM cause IE with value "NB-IoT not allowed", as PLMNs where NB-S1 mode is not allowed. When the MS disables its NB-IoT capability due to receipt of a reject from the network with EMM cause #15 "no suitable cells in tracking area" and an Extended EMM cause IE with value "NB-IoT not allowed": + +- the MS may add the identity of the PLMN to the list of "PLMNs with NB-IoT not allowed" and start timer TH if timer TH is not already running. The number of PLMNs that the MS can store in the "PLMNs with NB-IoT not allowed" list is implementation specific, but it shall be at least one. The value of timer TH is MS implementation specific, but shall not exceed the maximum possible value of background scanning timer T as specified in clause 4.4.3.3.1; +- in automatic PLMN selection the MS shall not consider PLMNs included in the "PLMNs with NB-IoT not allowed" list as PLMN selection candidates for the access technology E-UTRAN in NB-S1 mode, unless no other PLMN is available. This does not prevent selection of such a PLMN if it is available in another RAT; and +- the MS shall delete stored information in the "PLMNs with NB-IoT not allowed" list when the MS is switched off, the USIM is removed or timer TH expires. + +### 3.1A CSG selection / restriction + +If the MS supports CSG, it is provisioned with an Allowed CSG list and an Operator CSG list and associated PLMN identities. Both lists can be retrieved either from the USIM if the lists are available in the USIM, or as described in 3GPP TS 24.285 [47] if the lists are not available in the USIM. These lists have zero or more entries. + +NOTE 1: The network also updates the Allowed CSG list in the same updating operation if one or more entries are removed from the Operator CSG list. This avoids an entry removed from the Operator CSG list remaining in the Allowed CSG list. + +There are two modes of CSG selection: + +- Automatic mode: This mode utilizes the Allowed CSG list and the Operator CSG list. After a PLMN is selected, the MS camps on a cell in that PLMN only if the cell is either not a CSG cell or it is a CSG cell with a CSG identity that is in the Allowed CSG list or in the Operator CSG List. The idle mode procedures of NAS are not impacted by this mode. Upon switch on the MS is in automatic mode. +- Manual mode: In this mode, the MS indicates to the user a list of available CSGs and the associated PLMNs. Based on configuration by the HPLMN, the list of CSGs provided to the user for a certain PLMN is either: + - not restricted by the Allowed CSG list and the Operator CSG List stored in the MS; or + - restricted to entries in the Operator CSG List only. + +After the user makes a selection, the MS camps on a cell with the selected CSG identity and may attempt to register with the associated PLMN (see 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A]). + +The permitted CSG list is a combination of Operator CSG list and the Allowed CSG list. NAS shall provide the permitted CSG list to the AS. If the contents of the permitted CSG list have changed, NAS shall provide an updated permitted CSG list to the AS. + +NOTE 2: The same CSG ID and its associated PLMN can exist in both the Operator CSG list and the Allowed CSG list. Such duplicates can be removed when combining these lists to form the permitted CSG list. + +If an integrity protected message with cause value #25 (see 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A]) is received by an MS for a CSG ID and associated PLMN identity present in the Operator CSG list, then for an implementation dependent time which is not shorter than 60 minutes, or until the MS is switched off, or the SIM/USIM is removed, or the Operator CSG list is updated: + +- a) The NAS shall not include this CSG ID and the associated PLMN identity in the permitted CSG list provided to the AS; and +- b) In CSG manual mode selection, the MS shall not indicate to the user that this CSG ID and the associated PLMN identity is in the Operator CSG List stored in the MS. + +NOTE 3: As an implementation option, the user can be informed that the MS has not been authorized for a CSG included in the Operator CSG list. + +### 3.1B PLMN selection triggered by ProSe communications + +If the MS supports ProSe communications and needs to perform PLMN selection for ProSe communications as specified in 3GPP TS 24.334 [51] or 3GPP TS 24.554 [80], then the MS shall proceed as follows: + +- i) the MS shall store a duplicate value of the RPLMN and a duplicate of the PLMN selection mode that were in use before PLMN selection due to ProSe communications was initiated, unless this PLMN selection due to ProSe communications follows another PLMN selection due to ProSe communications or a manual CSG selection as specified in clause 4.4.3.1.3.3; +- ii) the MS shall enter into Automatic mode of PLMN selection as specified in clause 4.4 taking into account the additional requirements in items iii) to x) below; +- iii) among the PLMNs advertised by the E-UTRA cell or NR cell operating in the radio resources provisioned to the MS for ProSe communications as specified in 3GPP TS 24.333 [52], 3GPP TS 24.555 [81] or 3GPP TS 31.102 [40], the MS shall choose one allowable PLMN which meets: + +1) the following: + +- is advertised by the E-UTRA cell; +- provides radio resources for ProSe communications over E-UTRA PC5; +- is in the list of authorised PLMNs for ProSe communications as specified in 3GPP TS 24.334 [51]; and +- is not in the list of "PLMNs with E-UTRAN not allowed" as specified in clause 3.1; or + +2) the following: + +- is advertised by the NR cell; +- provides radio resources for 5G ProSe communications over NR PC5; +- is in the list of authorised PLMNs for 5G ProSe communications over PC5 as specified in 3GPP TS 24.554 [80]; +- is the advertised PLMN(s) of the 5G ProSe layer-2 UE-to-network relay UE if the MS is acting as a 5G ProSe layer-2 remote UE; +- is not in the list of PLMNs where the N1 mode capability was disabled due to IMS voice not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible; and +- is not in the list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" in N1 mode as specified in clause 3.1; + +if either condition 1) or condition 2) above is met then the MS shall attempt to register on that PLMN. If none of the PLMNs meet either condition 1) or condition 2) above, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; + +- iv) if the registration fails due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.334 [51], or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.554 [80], then the MS shall update the appropriate list of forbidden PLMNs as specified in clause 3.1, and shall either: + +A) if the PLMN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform ProSe communications on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of ProSe communications; + +B) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; or + +- C) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register. + +Whether the MS performs A), B) or C) above is left up to MS implementation. + +- v) if the registration fails due to causes other than "PLMN not allowed" or "EPS services not allowed" or "5GS services not allowed", the MS shall: + - if the handling of the failure requires updating a list of forbidden PLMNs, update the appropriate list (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]); and + - if the handling of the failure does not require updating a list of forbidden PLMNs (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]), remember the PLMN as a PLMN on which the MS has failed to register; + +NOTE 1: How long the MS memorizes the PLMNs on which it has failed to register is implementation dependent. + +and the MS shall either: + +- A1) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; +- B1) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register; or +- C1) perform ProSe communications in limited service state on a PLMN advertised by the cell operating in the radio resources provisioned to the MS for ProSe communications as specified in 3GPP TS 24.333 [52], 3GPP TS 24.555 [81] or 3GPP TS 31.102 [40], if registration on this PLMN has previously failed due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.334 [51] or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.554 [80] and if this PLMN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65]. In this case the MS shall not search for available and allowable PLMNs during the duration of ProSe communications; + +Whether the MS performs A1), B1) or C1) above is left up to MS implementation. + +vi) if the MS is no longer in the coverage of the selected PLMN, then the MS shall either: + +- A2) perform ProSe communications procedures for MS to use provisioned radio resources as specified in 3GPP TS 24.334 [51] or 3GPP TS 24.554 [80]; or +- B2) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +Whether the MS performs A2) or B2) above is left up to MS implementation. + +vii) if the MS is unable to find a suitable cell on the selected PLMN as specified in 3GPP TS 24.334 [51], then the MS shall either: + +- A3) if the PLMN provides common radio resources needed by the MS to do ProSe communications as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform ProSe communications on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of ProSe communications; or +- B3) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +Whether the MS performs A3) or B3) above is left up to MS implementation. + +viii) if the MS is switched off while on the selected PLMN and switched on again, the MS shall use the stored duplicate value of RPLMN as RPLMN and behave as specified in clause 4.4.3.1; + +ix) if the user initiates a PLMN selection while on the selected cell, the MS shall delete the stored duplicate value of PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the MS has successfully registered to the selected PLMN; and + +- x) if the MS no longer needs to perform Prose communications, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +NOTE 2: If the MS returns to the RPLMN due to a failure to register in the selected PLMN, the upper layers of the MS can trigger PLMN selection again to initiate ProSe communications. + +If the PLMN selected for ProSe communications is a VPLMN, the MS shall not periodically scan for higher priority PLMNs during the duration of ProSe communications. + +The solution to prevent potential ping-pong between the RPLMN and the PLMN selected for ProSe communications is MS implementation specific. + +### 3.1C PLMN selection triggered by V2X communication over PC5 + +If the MS supports V2X communication over E-UTRA-PC5 or NR-PC5 and needs to perform PLMN selection for V2X communication over PC5 as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75], then the MS shall proceed as follows: + +- i) the MS shall store a duplicate value of the RPLMN and a duplicate of the PLMN selection mode that were in use before PLMN selection due to V2X communication over PC5 was initiated, unless this PLMN selection due to V2X communication over PC5 follows another PLMN selection due to V2X communication over PC5 or a manual CSG selection as specified in clause 4.4.3.1.3.3; +- ii) the MS shall enter into Automatic mode of PLMN selection as specified in clause 4.4 taking into account the additional requirements in items iii) to x) below; +- iii) Among the PLMNs advertised by the E-UTRA or NG-RAN cell operating in the radio resources provisioned to the MS for V2X communication over PC5 as specified in 3GPP TS 24.385 [60], 3GPP TS 24.588 [79] or 3GPP TS 31.102 [40], the MS shall choose one allowable PLMN which meets: + - 1) the following: + - provides radio resources for V2X communication over PC5; + - is in the list of authorised PLMNs for V2X communication over PC5 as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75]; and + - is not in the list of "PLMNs with E-UTRAN not allowed" as specified in clause 3.1; or + - 2) the following: + - provides radio resources for V2X communication over PC5; + - is in the list of authorised PLMNs for V2X communication over PC5 as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75]; + - is not in the list of PLMNs where the N1 mode capability was disabled due to IMS voice not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible; and + - is not in the list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" in N1 mode as specified in clause 3.1; + +if condition 1) or 2) above are met then the MS shall attempt to register on that PLMN. If none of the PLMNs meet condition 1) or 2) above, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; + +- iv) if the registration fails due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.386 [59], or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.587 [75], or both, then the MS shall update the appropriate list of forbidden PLMNs as specified in clause 3.1, and shall: + +- A) if the PLMN provides common radio resources needed by the MS to do V2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform V2X communication over PC5 on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of V2X communication over PC5; + +- B) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; or +- C) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register. + +Whether the MS performs A), B) or C) above is left up to MS implementation. + +- v) if the registration fails due to causes other than "PLMN not allowed" or "EPS services not allowed" or "5GS services not allowed", the MS shall: + - if the handling of the failure requires updating a list of forbidden PLMNs, update the appropriate list (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]); and + - if the handling of the failure does not require updating a list of forbidden PLMNs (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]), remember the PLMN as a PLMN on which the MS has failed to register; + +NOTE 1: How long the MS memorizes the PLMNs on which it has failed to register is implementation dependent. + +and the MS shall: + +- A1) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; +- B1) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register; or +- C1) perform V2X communication over PC5 in limited service state on a PLMN advertised by the cell operating in the radio resources provisioned to the MS for V2X communication over PC5 as specified in 3GPP TS 24.385 [60], 3GPP TS 24.588 [79] or 3GPP TS 31.102 [40], if registration on this PLMN has previously failed due to "PLMN not allowed" or "EPS services not allowed" as specified in 3GPP TS 24.386 [59], or due to "PLMN not allowed" or "5GS services not allowed" as specified in 3GPP TS 24.587 [75], or both, and if this PLMN provides common radio resources needed by the MS to do V2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65]. In this case the MS shall not search for available and allowable PLMNs during the duration of V2X communication over PC5; + +Whether the MS performs A1), B1) or C1) above is left up to MS implementation. + +- vi) if the MS is no longer in the coverage of the selected PLMN, then the MS shall: + +- A2) perform V2X communication over PC5 procedures for MS to use provisioned radio resources as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75]; or +- B2) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +Whether the MS performs A2) or B2) above is left up to MS implementation. + +- vii) if the MS is unable to find a suitable cell on the selected PLMN as specified in 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75], then the MS shall: + +- A3) if the PLMN provides common radio resources needed by the MS to do V2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform V2X communication over PC5 on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of V2X communication over PC5; or +- B3) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +Whether the MS performs A3) or B3) above is left up to MS implementation. + +- viii) if the MS is switched off while on the selected PLMN and switched on again, the MS shall use the stored duplicate value of RPLMN as RPLMN and behave as specified in clause 4.4.3.1; + +- ix) if the user initiates a PLMN selection while on the selected cell, the MS shall delete the stored duplicate value of PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the MS has successfully registered to the selected PLMN; and +- x) if the MS no longer needs to perform V2X communication over PC5, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +NOTE 2: If the MS returns to the RPLMN due to a failure to register in the selected PLMN, the upper layers of the MS can trigger PLMN selection again to initiate V2X communication over PC5. + +If the PLMN selected for V2X communication over PC5 is a VPLMN, the MS shall not periodically scan for higher priority PLMNs during the duration of V2X communication over PC5. + +The solution to prevent potential ping-pong between the RPLMN and the PLMN selected for V2X communication over PC5 is MS implementation specific. + +### 3.1D PLMN selection triggered by A2X communication over PC5 + +If the MS supports A2X communication over E-UTRA-PC5 or NR-PC5 and needs to perform PLMN selection for A2X communication over PC5 as specified in 3GPP TS 24.577 [86], then the MS shall proceed as follows: + +- i) the MS shall store a duplicate value of the RPLMN and a duplicate of the PLMN selection mode that were in use before PLMN selection due to A2X communication over PC5 was initiated, unless this PLMN selection due to A2X communication over PC5 follows another PLMN selection due to A2X communication over PC5 or a manual CSG selection as specified in clause 4.4.3.1.3.3; +- ii) the MS shall enter into Automatic mode of PLMN selection as specified in clause 4.4 taking into account the additional requirements in items iii) to x) below; +- iii) among the PLMNs advertised by the E-UTRA cell or NR cell operating in the radio resources provisioned to the MS for A2X communication over PC5 as specified in 3GPP TS 24.577 [86], 3GPP TS 24.578 [87] or 3GPP TS 31.102 [40], the MS shall choose one allowable PLMN which meets: + - 1) the following: + - provides radio resources for A2X communication over PC5; + - is in the list of authorised PLMNs for A2X communication over PC5 as specified in 3GPP TS 24.577 [86]; and + - is not in the list of "PLMNs with E-UTRAN not allowed" as specified in clause 3.1; or + - 2) the following: + - provides radio resources for A2X communication over PC5; + - is in the list of authorised PLMNs for A2X communication over PC5 as specified in 3GPP TS 24.577 [86]; + - is not in the list of PLMNs where the N1 mode capability was disabled due to IMS voice not available and the MS's usage setting was "voice centric" as PLMNs where voice service was not possible; and + - is not in the list of PLMNs where the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" in N1 mode as specified in clause 3.1; + +if either condition 1) or condition 2) above is met then the MS shall attempt to register on that PLMN. If none of the PLMNs meet either condition 1) or condition 2) above, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; +- iv) if the registration fails due to "PLMN not allowed" or "EPS services not allowed" in case of EPS, due to "PLMN not allowed" or "5GS services not allowed" in case of 5GS, or both as specified in 3GPP TS 24.577 [86], then the MS shall update the appropriate list of forbidden PLMNs as specified in clause 3.1, and shall: + +- A) if the PLMN provides common radio resources needed by the MS to do A2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform A2X communication over PC5 on the selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of A2X communication over PC5; + +**Editor's note (pCR, UAS\_Ph2): 3GPP TS 38.331 and 3GPP TS 36.331 still need to be updated for A2X communication over PC5.** + +- B) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; or +- C) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register. + +Whether the MS performs A), B) or C) above is left up to MS implementation. + +- v) if the registration fails due to causes other than "PLMN not allowed" or "EPS services not allowed" or "5GS services not allowed", the MS shall: + - if the handling of the failure requires updating a list of forbidden PLMNs, update the appropriate list (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]); and + - if the handling of the failure does not require updating a list of forbidden PLMNs (as specified in 3GPP TS 24.301 [23A] or 3GPP TS 24.501 [64]), remember the PLMN as a PLMN on which the MS has failed to register; + +NOTE 1: How long the MS memorizes the PLMNs on which it has failed to register is implementation dependent. and the MS shall either: + +- A1) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action; +- B1) perform the action described in iii) again with the choice of PLMNs further excluding the PLMNs on which the MS has failed to register; or +- C1) perform A2X communication over PC5 in limited service state on a PLMN advertised by the cell operating in the radio resources provisioned to the MS for A2X communication over PC5 as specified in 3GPP TS 24.577 [86], 3GPP TS 24.578 [87] or 3GPP TS 31.102 [40], if registration on this PLMN has previously failed due to "PLMN not allowed" or "EPS services not allowed" in case of EPS, due to "PLMN not allowed" or "5GS services not allowed" in case of 5GS, or both as specified in 3GPP TS 24.577 [86], and if this PLMN provides common radio resources needed by the MS to do A2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65]. In this case the MS shall not search for available and allowable PLMNs during the duration of A2X communication over PC5; + +**Editor's note (pCR, UAS\_Ph2): 3GPP TS 38.331 and 3GPP TS 36.331 still need to be updated for A2X communication over PC5.** + +Whether the MS performs A1), B1) or C1) above is left up to MS implementation. + +- vi) if the MS is no longer in the coverage of the selected PLMN, then the MS shall: + +- A2) perform A2X communication over PC5 procedures for MS to use provisioned radio resources as specified in 3GPP TS 24.577 [86]; or +- B2) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +Whether the MS performs A2) or B2) above is left up to MS implementation. + +- vii) if the MS is unable to find a suitable cell on the selected PLMN as specified in 3GPP TS 24.577 [86], then the MS shall: + +- A3) if the PLMN provides common radio resources needed by the MS to do A2X communication over PC5 as specified in 3GPP TS 36.331 [42] or 3GPP TS 38.331 [65], perform A2X communication over PC5 on the + +selected PLMN in limited service state. In this case the MS shall not search for available and allowable PLMNs during the duration of A2X communication over PC5; or + +**Editor's note (pCR, UAS\_Ph2): 3GPP TS 38.331 and 3GPP TS 36.331 still need to be updated for A2X communication over PC5.** + +- B3) return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +Whether the MS performs A3) or B3) above is left up to MS implementation. + +- viii) if the MS is switched off while on the selected PLMN and switched on again, the MS shall use the stored duplicate value of RPLMN as RPLMN and behave as specified in clause 4.4.3.1; +- ix) if the user initiates a PLMN selection while on the selected cell, the MS shall delete the stored duplicate value of PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the MS has successfully registered to the selected PLMN; and +- x) if the MS no longer needs to perform A2X communication over PC5, the MS shall return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN for further action. + +NOTE 2: If the MS returns to the RPLMN due to a failure to register in the selected PLMN, the upper layers of the MS can trigger PLMN selection again to initiate A2X communication over PC5. + +If the PLMN selected for A2X communication over PC5 is a VPLMN, the MS shall not periodically scan for higher priority PLMNs during the duration of A2X communication over PC5. + +The solution to prevent potential ping-pong between the RPLMN and the PLMN selected for A2X communication over PC5 is MS implementation specific. + +## 3.2 Regional provision of service + +An MS may have a "regionally restricted service" where it can only obtain service on certain areas (i.e. LAs or TAs). If such an MS attempts to camp on a cell of an area for which it does not have service entitlement, when it does an LR request, it will receive a message with cause value #12 (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]). In this case, the MS shall take the following actions depending on the mode in which the message was received: + +A/Gb mode or Iu mode: + +- The MS stores the forbidden LA identity (LAI) in a list of "forbidden location areas for regional provision of service", to prevent repeated access attempts on a cell of the forbidden LA. This list is deleted when the MS is switched off, the SIM is removed or periodically (with period in the range 12 to 24 hours). The MS enters the limited service state. + +S1-mode: + +The MS stores the forbidden TA identity (TAI) in a list of "forbidden tracking areas for regional provision of service", to prevent repeated access attempts on a cell of the forbidden TA. This list is deleted when the MS is switched off, the SIM is removed or periodically (with period in the range 12 to 24 hours). The MS enters the limited service state. + +N1-mode: + +The MS stores the forbidden TA identity (TAI) in a list of "5GS forbidden tracking areas for regional provision of service", to prevent repeated access attempts on a cell of the forbidden TA. This list is deleted when the MS is switched off, the SIM is removed or periodically (with period in the range 12 to 24 hours). The MS enters the limited service state. + +In A/Gb mode, a cell may be reserved for SoLSA exclusive access (see 3GPP TS 24.008 [23] and 3GPP TS 44.060 [39]). An MS is only allowed to camp normally on such a cell if it has a Localised Service Area subscription to the cell. Other MS may enter the limited service state. + +NOTE 1: In A/Gb mode, in a SoLSA exclusive cell the MCC+MNC code is replaced by a unique escape PLMN code (see 3GPP TS 23.073), not assigned to any PLMN, in SI3 and SI4. An MS not supporting SoLSA may request for location update to an exclusive access cell. In this case the location attempt is rejected with the cause "PLMN not allowed" and the escape PLMN code is added to the list of the "forbidden PLMNs". + +The MS operating in SNPN access operation mode over 3GPP access shall maintain one or more lists of "5GS forbidden tracking areas for regional provision of service", each associated with an SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, entry of the "list of subscriber data" or, if the MS supports access to an SNPN using credentials from a credentials holder, the PLMN subscription. The MS shall use the list of "5GS forbidden tracking areas for regional provision of service" associated with the selected SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the MS selects a new SNPN, the MS shall keep the list of "5GS forbidden tracking areas for regional provision of service" associated with the previously selected SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the previously selected entry of the "list of subscriber data" or the previously selected PLMN subscription. If the number of the lists to be kept is higher than supported, the MS shall delete the oldest stored list of "5GS forbidden tracking areas for regional provision of service". The MS shall delete all lists of "5GS forbidden tracking areas for regional provision of service", when the MS is switched off. The MS shall delete the list of "5GS forbidden tracking areas for regional provision of service" associated with an SNPN: + +- a) when the entry with the subscribed SNPN identifying the SNPN in the "list of subscriber data" is updated; +- b) when the USIM is removed if: + - EAP based primary authentication and key agreement procedure using EAP-AKA'; or + - 5G AKA based primary authentication and key agreement procedure;was performed in the selected SNPN; or +- c) if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, when the list of "5GS forbidden tracking areas for regional provision of service" is associated with: + - the entry of the "list of subscriber data" and the entry of the "list of subscriber data" is updated; or + - the PLMN subscription and USIM is removed. + +NOTE 2: The number of the lists of "5GS forbidden tracking areas for regional provision of service" supported by the MS is MS implementation specific. + +## 3.3 Borders between registration areas + +If the MS is moving in a border area between registration areas, it might repeatedly change between cells of different registration areas. Each change of registration area would require an LR, which would cause a heavy signalling load and increase the risk of a paging message being lost. The access stratum shall provide a mechanism to limit this effect. + +## 3.4 Access control + +### 3.4.1 Access control + +Due to problems in certain areas, network operators may decide to restrict access from some MSs (e.g., in case of congestion), and for this reason, a mechanism for common access control is provided. In A/Gb mode and Iu mode a mechanism for domain specific access control is also provided (see 3GPP TS 43.022 [35], 3GPP TS 44.018 [34] and 3GPP TS 25.304 [32]). + +A mechanism to restrict access is provided via EAB. A network operator can restrict network access of those MSs that are configured for EAB in addition to common access control and domain specific access control. + +The MS can be configured for EAB in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]). An MS that supports EAB shall follow the EAB mechanism (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A], 3GPP TS 44.018 [34], 3GPP TS 25.331 [33], 3GPP TS 36.331 [42]) when configured for EAB. + +The MS can be configured for ACDC in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.105 [53]). An MS that supports ACDC shall follow the ACDC mechanism (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A], 3GPP TS 25.331 [33], 3GPP TS 36.331 [42]) when configured for ACDC. + +The MS can be configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]) to override EAB. An MS that supports overriding EAB shall follow the overriding EAB mechanism (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A]) when configured to allow overriding EAB. + +In the case that a network operator decides to restrict access they may as an option allow restricted MSs to respond to paging messages and/or to perform location registrations. Mechanisms to allow this optional access are provided (see 3GPP TS 25.304 [32]). + +A network operator can also restrict some MSs to access the network for location registration, although via common access class control or domain specific access class control the MSs are permitted to access the network for other purposes. + +If the MS is accessing the network with a special access class (Access classes 11 to 15), then the MS shall ignore EAB and ACDC. + +NOTE: The conditions when the MS is allowed to access the network with access class 11 – 15 are specified in 3GPP TS 22.011 [138]. + +If an MS configured for EAB is initiating an emergency call, then the MS shall ignore EAB. + +If an MS configured for EAB is responding to paging, then the MS shall ignore EAB. + +If an MS configured for ACDC is responding to paging, then the MS shall ignore ACDC. + +If an MS configured for ACDC is initiating an emergency call, then the MS shall ignore ACDC. + +If an MS configured for ACDC and the MO MMTEL voice call is started, the MO MMTEL video call is started or the MO SMSoIP is started (see 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A]), then the MS shall ignore ACDC. + +### 3.4.2 Forbidden LA or TA for regional provision of service + +The MS is not allowed to initiate establishment of a CM connection except for an emergency call when camped on a cell of an LA or TA of which belongs to the list of "forbidden location areas for regional provision of service" or "forbidden tracking areas for regional provision of service". The MS may respond to paging. + +The MS is not allowed to request GPRS services except for an emergency bearer services or for access to RLOS when camped on a cell of an LA or TA of which belongs to the list of "forbidden location areas for regional provision of service" or "forbidden tracking areas for regional provision of service". + +The MS is not allowed to request 5GS services except emergency services when camped on a cell of a TA of which belongs to the list of "5GS forbidden tracking areas for regional provision of service". + +### 3.5 No suitable cell (limited service state) + +There are a number of situations in which the MS is unable to obtain normal service from a PLMN or SNPN. These include: + +- Failure to find a suitable cell of the selected PLMN or of the selected SNPN; +- No SIM in the MS or the "list of subscriber data" with no valid entry; +- A "PLMN not allowed", "Requested service option not authorized in this PLMN", "Serving network not authorized" or "PLMNs not allowed to operate at the present UE location" response in case of PLMN or a "Temporarily not authorized for this SNPN" or "Permanently not authorized for this SNPN" response in case of SNPN when an LR is received; + +- d) An "illegal MS" or "illegal ME" response when an LR is received (Any SIM or the corresponding entry of the "list of subscriber data" in the ME is then considered "invalid"); +- e) An "IMSI unknown in HLR" response when an LR is received (Any SIM in the ME is then considered "invalid" for non-GPRS services); +- f) A "GPRS services not allowed" response when an LR of a GPRS MS attached to GPRS services only is received (The cell selection state of GPRS MSs attached to GPRS and non-GPRS depends on the outcome of the location updating), or an "EPS services not allowed" response is received when an EPS attach, tracking area update or service request is performed, or a "5GS services not allowed" response is received when a registration or service request is performed; +- g) Void; +- h) Void; +- i) MS supporting CAG is camped on a CAG cell belonging to a PLMN, the CAG-ID of the CAG cell is not manually selected by the user and none of the CAG-ID(s) of the CAG cell are authorized based on the "Allowed CAG list" associated with that PLMN in the "CAG information list"; +- j) MS supporting CAG is camped on a non-CAG cell belonging to a PLMN, the PLMN ID of the non-CAG cell without a CAG-ID is not manually selected by the user and the UE is configured with "indication that the MS is only allowed to access 5GS via CAG cells" for that PLMN in the "CAG information list"; and +- k) MS supporting CAG is camped on a CAG cell belonging to a PLMN, the CAG-ID of the CAG cell is not manually selected by the user and the "CAG information list" does not contain an entry for the PLMN (e.g. because the UE is not (pre-)configured with a "CAG information list"). +- l) MS selected a PLMN for disaster roaming, the timer precluding registration for disaster roaming in the selected PLMN for disaster roaming is running and the MS is not registering or registered for emergency services in the selected PLMN for disaster roaming. +- m) MS determined that a disaster condition has ended, selected the PLMN previously with disaster condition, the timer precluding registration in the PLMN previously with disaster condition is running and the MS is not registering or registered for emergency services in the PLMN previously with disaster condition. + +(In automatic PLMN selection mode, items a, c and f would normally cause a new PLMN selection, but even in this case, the situation may arise when no PLMNs are available and allowable for use). + +(In automatic SNPN selection mode, items a, c, d, and f would normally cause a new SNPN selection if there are two or more entries in the "list of subscriber data", but even in this case, the situation may arise when no SNPNs are available and allowable for use). + +For the items a to f, if the MS does not operate in SNPN access operation mode over 3GPP access, the MS attempts to camp on an acceptable cell, irrespective of its PLMN identity, so that emergency calls or access to RLOS can be made if necessary, with the exception that an MS operating in NB-S1 mode, shall never attempt to make emergency calls or to access RLOS. When in the limited service state with a valid SIM, the MS shall search for available and allowable PLMNs in the manner described in clause 4.4.3.1 and when indicated in the SIM also as described in clause 4.4.3.4. For an MS that is not in eCall only mode, with the exception of performing GPRS attach or EPS attach for emergency bearer services, performing an initial registration for emergency services, or performing EPS attach for access to RLOS, no LR requests are made until a valid SIM is present and either a suitable cell is found or a manual network reselection is performed. For an MS in eCall only mode, no LR requests are made except for performing EPS attach for emergency bearer services or an initial registration for emergency services. When performing GPRS attach or EPS attach for emergency bearer services, an initial registration for emergency services, or performing EPS attach for access to RLOS, the PLMN of the current serving cell is considered as the selected PLMN for the duration the MS is attached for emergency bearer services, registered for emergency services, or attached for access to RLOS. In the limited service state the presence of the MS need not be known to the PLMN on whose cell it has camped. If the MS is enabled for SNPN, the MS needs to make an emergency call, there is no available PLMN supporting emergency services and the MS determines that there is an available SNPN supporting emergency services (based on broadcasted information of SNPN support for emergency services), the MS may start operating in SNPN access operation mode over 3GPP access and attempt to camp on a cell of the SNPN supporting emergency services. After an emergency call is released, the MS should stop operating in SNPN access operation mode over 3GPP access and perform PLMN selection. If the MS is enabled for SNPN and wants to perform configuration of SNPN subscription parameters in PLMN via the user plane, but there is no available PLMN for normal services, either because of no available PLMN or all available PLMNs being + +in forbidden PLMN list due to LR failure, the MS may start operating in SNPN access operation mode over 3GPP access (if the MS is configured with default UE credentials) and perform SNPN selection as per subclause 4.9.3.1.3 or 4.9.3.1.4. After the onboarding services in SNPN are complete, the MS may stop operating in SNPN access operation mode over 3GPP access and perform PLMN selection. + +For the items a, c, d and f, if the MS operates in SNPN access operation mode over 3GPP access and the MS has a valid entry in the "list of subscriber data", the MS shall search for available and allowable SNPNs in the manner described in clause 4.9.3.1. For the item b, if the MS operates in SNPN access operation mode over 3GPP access, the MS: + +- attempts to camp on an acceptable cell so that emergency calls can be made if supported and necessary; and +- may perform SNPN selection procedure for onboarding services in SNPN if the MS is configured with the default UE credentials for primary authentication. + +For the item l, the MS shall search for available and allowable PLMNs in the manner described in clause 4.4.3.1 and when indicated in the SIM also as described in clause 4.4.3.4. + +When in the limited service state, with the exception of performing an initial registration for emergency services, no LR requests are made until a valid entry of the "list of subscriber data" is present and either a suitable cell is found or a manual network reselection is performed. In the limited service state, the presence of the MS need not be known to the SNPN on whose cell it has camped. If the MS needs to make an emergency call, the MS supports accessing a PLMN, and there is no available SNPN supporting emergency services and the MS determines that there is an available PLMN supporting emergency services (based on broadcasted information of PLMN support for emergency services), the MS shall stop operating in SNPN access operation mode over 3GPP access and attempt to camp on a cell of the PLMN supporting emergency services so that emergency calls can be made. After an emergency call is released, the MS may re-start operating in SNPN access operation mode over 3GPP access and perform SNPN selection. If the MS is enabled for SNPN and wants to select an SNPN for onboarding services in SNPN, but finds no suitable SNPN as per subclause 4.9.3.1.3 or 4.9.3.1.4, the MS may stop operating in SNPN access operation mode over 3GPP access, and perform PLMN selection (if the MS is configured with PLMN credentials in USIM). The MS may perform PLMN selection as per clause 4.4. After the configuration of SNPN subscription parameters in PLMN via the user plane is complete, the MS may start operating in SNPN access operation mode over 3GPP access and perform SNPN selection. If the MS supports access to an SNPN providing access for localized services in SNPN and access for localized services in SNPN is enabled, and the MS is in limited service state because no SNPN is available as per subclause 4.9.3.1, when the validity information of an SNPN based on the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" changes from not met to met, the MS shall perform an SNPN selection as per subclause 4.9.3.1. + +There are also other conditions under which only emergency calls or access to RLOS may be made if the MS does not operate in SNPN access operation mode over 3GPP access. These are shown in table 2 in clause 5. ProSe communications can be initiated in case of PLMN if necessary (see 3GPP TS 24.334 [51] or 3GPP TS 24.554 [80]) when in the limited service state due to items a) or c) or f). V2X communication over PC5 can be initiated if necessary (see 3GPP TS 24.386 [59] or 3GPP TS 24.587 [75]) when in the limited service state due to items a) or c) or f). A2X communication over PC5 can be initiated if necessary (see 3GPP TS 24.577 [86]) when in the limited service state due to items a) or c) or f). + +## 3.6 CTS fixed part selection (A/Gb mode only) + +In CTS mode only or in automatic mode with CTS preferred, the CTS MS normally operates on a CTS fixed part on which the mobile station is already enrolled. If the CTS MS loses CTS coverage in these modes, it shall attempt periodically to select again a CTS fixed part. + +To select a CTS fixed part, the CTS MS shall listen to the CTSBCH frequencies of all the fixed parts on which the MS is currently enrolled. + +If the CTS MS is moving in a border area between one area with CTS coverage and one without it, it might repeatedly require CTS attachments and LU on the PLMN. To prevent this, the criteria C1\_CTS and C2\_CTS (defined in 3GPP TS 45.008 [25] clause 11.1) are used. To attach to a CTS FP, the C1\_CTS criterion shall be greater than zero. When the C2\_CTS criterion falls below zero, the CTS MS shall consider itself to be no more under CTS coverage. + +## 3.7 NAS behaviour configuration + +NAS behaviour can be operator configurable using parameters in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]). For parameters available in both the USIM and the ME, precedence is specified in 3GPP TS 31.102 [40] clause 5.2.29. + +## 3.8 CAG selection (N1 mode only) + +The MS may support CAG. + +The MS may support enhanced CAG information. If the MS supports enhanced CAG information, the MS shall support CAG. + +If the MS supports CAG, the MS can be provisioned by the network with a "CAG information list", consisting of zero or more entries, each containing: + +- a) a PLMN ID; +- b) an "Allowed CAG list". The "Allowed CAG list" contains zero or more CAG-IDs. If the UE supports enhanced CAG information, each CAG-ID in the "Allowed CAG list" can be associated with time validity information. The time validity information contains one or more time periods; and +- c) an optional "indication that the MS is only allowed to access 5GS via CAG cells". + +The "CAG information list" provisioned by the network is stored in the non-volatile memory of the ME, as specified in 3GPP TS 24.501 [64] annex C. + +NOTE 1: When the MS is registering or registered to a PLMN other than the HPLMN or EHPLMN, then the HPLMN will send a "CAG information list" consisting of CAG subscription information related to the serving PLMN only. When the MS is registering or registered to the HPLMN or EHPLMN then the HPLMN or EHPLMN can send CAG subscription information related to any PLMN in the "CAG information list". + +In addition, the MS can also be pre-configured with a "CAG information list" stored in the USIM (see 3GPP TS 31.102 [40]). The "Allowed CAG list" included in the entry for the HPLMN or EHPLMN in "CAG information list" stored in the USIM can contain a range of CAG-IDs. + +NOTE 2: For a given PLMN ID, no more than one entry containing the MCC value and the MNC value of the PLMN ID is necessary to be provided in the "CAG information list" stored in the USIM (see TS 31.102 [22]). + +3GPP TS 24.501 [64] annex C specifies condition under which the "CAG information list" stored in the ME is deleted. Additionally, when a USIM is inserted, if: + +- no "CAG information list" is stored in the non-volatile memory of the ME; or +- the SUPI from the USIM does not match the SUPI stored together with the "CAG information list" in the non-volatile memory of the ME; + +and the MS has a "CAG information list" stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the "CAG information list" from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C. If an entry in the "CAG information list" stored in the USIM includes an "Allowed CAG list" which contains a range of CAG-IDs, the range of CAG-IDs can be replaced with individual CAG-IDs matching the range up to ME implementation. + +NOTE 3: The MS ignores the "CAG information list" stored in the USIM except when the USIM is inserted. + +If the MS supports CAG and a PLMN is selected as described in clause 4.4.3.1.1, the automatic CAG selection is performed as part of clause 4.4.3.1.1. + +If the MS supports CAG and a PLMN is selected as described in clause 4.4.3.1.2, the manual CAG selection is performed as part of clause 4.4.3.1.2. + +The NAS shall provide the AS with a "CAG information list", if available, where the "CAG information list" contains only the CAG-IDs authorized by the "Allowed CAG list" for the entries in the "CAG information list", if available. If + +the contents of the "CAG information list" have changed, or the time validity information of an entry of "Allowed CAG list" in the "CAG information list" starts or stops matching the MS's current time, the NAS shall provide an updated "CAG information list" to the AS, where the "CAG information list" contains only the CAG-IDs authorized by the "Allowed CAG list" for the entries in the "CAG information list", if available. If an entry in the "CAG information list" includes an "Allowed CAG list" which contains a range of CAG-IDs, whether the NAS provides the AS the range of CAG-IDs or individual CAG-IDs matching the range is up to ME implementation. + +The "indication that the MS is only allowed to access 5GS via CAG cells" is not applicable in EPS. + +## 3.9 SNPN selection + +An MS may be enabled for SNPN. + +An MS enabled for SNPN may operate in SNPN access operation mode over 3GPP access. + +An MS may support onboarding services in SNPN. + +An MS enabled for SNPN may support access to an SNPN using credentials from a credentials holder. + +An MS enabled for SNPN may support access to an SNPN providing access for localized services in SNPN. If the MS supports access to an SNPN providing access for localized services in SNPN, the MS shall support access to an SNPN using credentials from a credentials holder. + +With the exception of onboarding services in SNPN, the MS operating in SNPN access operation mode over 3GPP access selects: + +- a) an SNPN for which it is configured with a subscriber identifier and credentials; +- b) if the MS supports equivalent SNPNs, an equivalent SNPN; or +- c) if the MS supports access to an SNPN using credentials from a credentials holder, an SNPN which supports access using credentials from a credentials holder. + +The MS can have several sets of subscriber identifiers, credentials, SNPN identities, and other parameters related to SNPN selection (see clause 4.9.3.0). There are two modes for SNPN selection: + +- i) Automatic SNPN selection mode. +- ii) Manual SNPN selection mode. + +For onboarding services in SNPN, the MS operating in SNPN access operation mode over 3GPP access selects an SNPN indicating that onboarding is allowed. There are two modes for SNPN selection for onboarding services in SNPN: + +- i) Automatic SNPN selection mode. +- ii) Manual SNPN selection mode. + +An SNPN selected for localized services in SNPN is an SNPN that is selected by an MS supporting access to an SNPN providing access for localized services in SNPN, when the access for localized services in SNPN is enabled, and the SNPN is selected according to: + +- a) clause 4.9.3.1.1 bullet a0); +- b) clause 4.9.3.2.1 bullet a0); or +- c) is manually selected by the user; and + - i) the validity information of the SNPN is met; + - ii) the validity information of GIN(s) broadcasted by the SNPN is met; or + - iii) both. + +## 3.10 Minimization of service interruption + +The MS may support Minimization of service interruption (MINT). + +MINT is not applicable in SNPNs. + +For a PLMN that provides disaster roaming services, if one of the CAG-ID(s) broadcasted by a CAG cell for the PLMN is authorized based on the "Allowed CAG list" included in the entry for the PLMN in the "CAG information list", then the UE may attempt to access the PLMN on the CAG cell for disaster roaming services. + +If the MS supports MINT, the MS can be provisioned by the network with: + +- a) an indication of whether disaster roaming is enabled in the UE, provided by the HPLMN; +- b) a "list of PLMN(s) to be used in disaster condition" provided by the HPLMN, consisting of zero or more entries, each containing a PLMN ID. The PLMNs are listed in order of decreasing priority, with the first PLMN being the highest priority PLMN; +- c) one or more "list of PLMN(s) to be used in disaster condition", where each VPLMN can provide one "list of PLMN(s) to be used in disaster condition", consisting of zero or more entries, each containing a PLMN ID. The PLMNs are listed in order of decreasing priority, with the first PLMN being the highest priority PLMN; +- d) a disaster roaming wait range consisting of a minimum wait time and a maximum wait time; +- e) a disaster return wait range consisting of a minimum wait time and a maximum wait time; and +- f) an indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', provided by the HPLMN. + +The network may provide the "list of PLMN(s) to be used in disaster condition", the disaster roaming wait range and the disaster return wait range to the UE during a successful registration procedure or a generic UE configuration update procedure. The network may also provide the disaster return wait range to the UE during a network initiated de-registration procedure, an unsuccessful registration procedure or an unsuccessful service request procedure. The HPLMN may also provide an indication of whether disaster roaming is enabled in the UE and an indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' during a UE parameters update procedure. + +The indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', one or more instances of "list of PLMN(s) to be used in disaster condition" each stored with the PLMN identity of the PLMN that provided it, the disaster roaming wait range and the disaster return wait range provisioned by the network are stored in the non-volatile memory of the ME, as specified in 3GPP TS 24.501 [64] annex C. + +In addition, the MS can also be pre-configured with an indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', a "list of PLMN(s) to be used in disaster condition" provided by the HPLMN, a disaster roaming wait range and a disaster return wait range stored in the USIM (see 3GPP TS 31.102 [40]). + +3GPP TS 24.501 [64] annex C specifies the conditions under which the indication of whether disaster roaming is enabled in the UE, the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN', the one or more "lists of PLMN(s) to be used in disaster condition", the disaster roaming wait range and the disaster return wait range stored in the ME are deleted. Additionally: + +- a) when a USIM is inserted: + - 1) if: + - i) no indication of whether disaster roaming is enabled in the UE is stored in the non-volatile memory of the ME; or + - ii) the SUPI from the USIM does not match the SUPI stored together with the indication of whether disaster roaming is enabled in the UE in the non-volatile memory of the ME; + +and the MS has an indication of whether disaster roaming is enabled in the UE stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the indication of whether disaster roaming is enabled in the UE from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; + +2) if: + +- i) no disaster roaming wait range is stored in the non-volatile memory of the ME; or +- ii) the SUPI from the USIM does not match the SUPI stored together with the disaster roaming wait range in the non-volatile memory of the ME; + +and the MS has a disaster roaming wait range stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the disaster roaming wait range from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; and + +3) if: + +- i) no disaster return wait range is stored in the non-volatile memory of the ME; or +- ii) the SUPI from the USIM does not match the SUPI stored together with the disaster return wait range in the non-volatile memory of the ME; + +and the MS has a disaster return wait range stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the disaster return wait range from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; + +4) if: + +- i) the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' is stored in the non-volatile memory of the ME; or +- ii) the SUPI from the USIM does not match the SUPI stored together with the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' in the non-volatile memory of the ME; + +and the MS has an indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; and + +5) if: + +- i) no "list of PLMN(s) to be used in disaster condition" provided by the HPLMN is stored in the non-volatile memory of the ME; or +- ii) the SUPI from the USIM does not match the SUPI stored together with the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN in the non-volatile memory of the ME; + +and the MS has a "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM (see 3GPP TS 31.102 [22]), the MS shall store the "list of PLMN(s) to be used in disaster condition" provided by HPLMN from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; + +b) when the ME receives a USAT REFRESH command indicating that: + +- 1) the indication of whether disaster roaming is enabled in the UE stored in the USIM has been updated, the MS shall store the indication of whether disaster roaming is enabled in the UE from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; +- 2) the disaster roaming wait range stored in the USIM has been updated, the MS shall store the disaster roaming wait range from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; +- 3) the disaster return wait range stored in the USIM has been updated, the MS shall store the disaster return wait range from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; +- 4) the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM has been updated, the MS shall store the indication of 'applicability of "lists of PLMN(s) + +to be used in disaster condition" provided by a VPLMN' from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; or + +- 5) the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM has been updated, the MS shall store the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN from the USIM into the ME, as specified in 3GPP TS 24.501 [64] annex C; or + +NOTE 1: The MS ignores the indication of whether disaster roaming is enabled in the UE stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the indication of whether disaster roaming is enabled in the UE stored in the USIM has been updated. + +NOTE 2: The MS ignores the disaster roaming wait range stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the disaster roaming wait range stored in the USIM has been updated. + +NOTE 3: The MS ignores the disaster return wait range stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the disaster return wait range stored in the USIM has been updated. + +NOTE 4: The MS ignores the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the USIM has been updated. + +NOTE 5: The MS ignores the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM except when the USIM is inserted or when the ME receives a USAT REFRESH command indicating that the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN stored in the USIM has been updated. + +If the MS does not have an indication of whether disaster roaming is enabled in the UE stored in the ME, or the indication of whether disaster roaming is enabled in the UE stored in the ME is set to "Disaster roaming is disabled in the UE", disaster roaming is disabled at the MS. In this case, the MS shall not perform disaster roaming. + +Upon selecting a PLMN for disaster roaming, if there is a disaster roaming wait range stored in the ME, the MS shall generate a random number within the disaster roaming wait range and start a timer set to the generated random number. While the timer is running, the MS shall not initiate registration with the exception of performing an initial registration for emergency services, in the selected PLMN. If performing an initial registration for emergency services in the selected PLMN, the MS shall keep the timer running. Upon expiration of the timer, if the MS does not have an emergency PDU session, the MS may initiate registration, if still camped on the selected PLMN. Upon expiration of the timer, if the MS has an emergency PDU session, the MS shall initiate registration after release of the emergency PDU session, if still camped on the selected PLMN. + +Upon determining that a disaster condition has ended and selecting the PLMN previously with disaster condition, if there is a disaster return wait range stored in the ME, the MS shall generate a random number within the disaster return wait range and start a timer set to the generated random number. While the timer is running, the MS shall not initiate registration with the exception of performing an initial registration for emergency services, in the selected PLMN. If performing an initial registration for emergency services in the selected PLMN, the MS shall keep the timer running. Upon expiration of the timer, if the MS does not have an emergency PDU session, the MS may initiate registration, if still camped on the selected PLMN. Upon expiration of the timer, if the MS has an emergency PDU session, the MS shall initiate registration after release of the emergency PDU session, if still camped on the selected PLMN. + +## 3.11 Signal level enhanced network selection + +Signal level enhanced network selection is optionally supported by the home operator. + +Signal level enhanced network selection applies only to NB-IoT, GERAN EC-GSM-IoT and Category M1 or M2 of E-UTRA. An MS supporting any, or a combination, of NB-IoT, GERAN EC-GSM-IoT and Category M1 or M2 of E-UTRA shall apply signal level enhanced network selection if the following conditions are fulfilled: + +- 1) The MS is in automatic PLMN selection mode; +- 2) The MS supports the "Operator controlled signal threshold per access technology" as specified in 3GPP TS 22.011 [19]; + +- 3) The MS is configured for using signal level enhanced network selection as specified in 3GPP TS 24.368 [50]; +- 4) The MS is configured for using signal level enhanced network selection as specified in 3GPP TS 31.102 [40]; and +- 5) The "Operator controlled signal threshold per access technology" is configured in the USIM as specified in 3GPP TS 31.102 [40]. + +NOTE 1: The usage of the "Operator controlled signal threshold per access technology" is intended only for IoT stationary devices (see 3GPP TS 22.011 [19]). + +NOTE 2: "Operator controlled signal threshold per access technology" is not expected to be supported by non-IoT devices. + +The HPLMN can configure the MS with an "Operator controlled signal threshold per access technology" stored in the USIM (see 3GPP TS 31.102 [40]), which consists of one or more entries, each containing: + +- a) a home operator controlled signal threshold; and +- b) an access technology. + +The "Operator controlled signal threshold per access technology" is specific for a certain access technology and when applicable, applies to all allowable PLMNs with the corresponding access technology combination. + +The HPLMN can update the "Operator controlled signal threshold per access technology" via steering of roaming information. When the ME receives a USAT REFRESH command indicating that the "Operator controlled signal threshold per access technology" stored in the USIM has been updated, an MS which applies SENSE shall use the "Operator controlled signal threshold per access technology" provided by the HPLMN for the subsequent PLMN selections. + +The "Operator controlled signal threshold per access technology" can also be received from the HPLMN over the control plane steering of roaming mechanism. + +# --- 4 Overall process structure + +## 4.1 Process goal + +The aim of the idle mode processes is to ensure that the registered PLMN is the selected PLMN and that the registered SNPN is the selected SNPN. + +## 4.2 States description + +Each of the processes of PLMN selection and SNPN selection, cell selection and location registration can be described by a set of states. The overall state of the mobile is thus a composite of the states of the three processes. In some cases, an event which causes a change of state in one process may trigger a change of state in another process, e.g., camping on a cell in a new registration area triggers an LR request. Except for SNPN selection, the relationship between the processes is illustrated in figure 1 in clause 5. + +Except for SNPN selection, the states in which the MS may be, for each of the processes, are described below and illustrated in figures 2a, 2b and 3 in clause 5. For many of the states, a fuller description can be found in other Technical Specifications, and a reference to the Technical Specification is given after the state description. + +In the event of any conflict between the diagrams and the text in the present document, the text takes precedence. + +## 4.3 List of states + +### 4.3.1 List of states for the PLMN selection process + +#### 4.3.1.1 List of states for automatic mode (figure 2a) + +- A1 Trying RPLMN - The MS is trying to perform a Location Registration on the registered PLMN. +- A2 On PLMN - The MS has successfully registered on a PLMN. +- A3 Trying PLMN - The MS is trying to register on a PLMN in the ordered list of PLMNs. +- A4 Wait for PLMNs to appear - There are no allowable and available PLMNs at present and the MS is waiting for one to appear. +- A5 HPLMN search in progress - The MS is trying to find if the HPLMN is available. +- A6 No SIM - There is no SIM in the MS, or certain LR responses have been received. + +#### 4.3.1.2 List of states for manual mode (figure 2b) + +- M1 Trying registered PLMN - The MS is trying to perform a Location Registration on the registered PLMN. +- M2 On PLMN - The MS has successfully registered on a PLMN. +- M3 Not on PLMN - The MS has failed to register on the selected PLMN. +- M4 Trying PLMN - The MS is trying to register on a user selected PLMN. +- M5 No SIM - There is no SIM in the MS, or certain LR responses have been received. + +### 4.3.2 Void + +### 4.3.3 List of states for location registration (figure 3) + +The states are entered depending on responses to location registration (LR) requests. Independent update states exist for GPRS and for non-GPRS operation in MSs capable of GPRS and non-GPRS services. + +- L0 Null – The MS is considered in this state when switched off. +- L1 Updated - The MS enters this state if an LR request is accepted. The update status is set to "UPDATED". The GPRS and the non-GPRS update state of an MS may enter "Updated" as a result of combined signalling or as a result of individual signalling depending on the capabilities of the network. +- L2 Idle, No IMSI - The MS enters this state if an LR request is rejected with cause: + - a) IMSI unknown in HLR; + - b) illegal ME; + - c) illegal MS; + - d) GPRS services not allowed, + - e) GPRS services and non-GPRS services not allowed, + +or if there is no SIM. All update states of an MS enter this state regardless whether received by individual or combined signalling for events b) and c). Event a) has no influence on the GPRS update state. Events b) and c) result in "ROAMING NOT ALLOWED" for the GPRS and/or non-GPRS update status depending on the specific location registration procedure. Event d) results in "ROAMING NOT ALLOWED" for the GPRS update status. Event e) results in "ROAMING NOT ALLOWED" for the GPRS update status and non-GPRS update status. + +If a SIM is present, the non-GPRS update status of the SIM is set to "ROAMING NOT ALLOWED". + +L3 Roaming not allowed - The MS enters this state if it receives an LR reject message with the cause: + +- a) PLMN not allowed; +- b) Location area not allowed; +- c) Tracking area not allowed; +- d) Roaming not allowed in this location area; +- e) Roaming not allowed in this tracking area; +- f) GPRS services not allowed in this PLMN; +- g) No suitable cells in location area; +- h) No suitable cells in tracking area; +- i) Not authorized for this CSG. + +Except from event f) all update states of the MS are set to "Roaming not allowed" regardless whether received by individual or combined signalling. Event f) results in "Roaming not allowed" for the GPRS update state only. Event f) has no influence on the non-GPRS update state. The behaviour of the MS in the roaming not allowed state is dependent on the LR reject cause as shown in table 2 in clause 5. Additionally: + +- in automatic mode, "PLMN not allowed", "Roaming not allowed in this location area" and "Roaming not allowed in this tracking area" cause the Automatic Network Selection procedure of clause 4.4.3.1.1 to be started; it is also caused by "GPRS services not allowed in this PLMN" when received by a GPRS MS operating in MS operation mode C; +- in manual mode, "PLMN not allowed" and "Roaming not allowed" cause the Manual Network Selection procedure of clause 4.4.3.1.2 to be started; it is also caused by "GPRS services not allowed in this PLMN" when received by a GPRS MS operating in MS operation mode C. + +L4 Not updated - The MS enters this state if any LR failure not specified for states L2 or L3 occurs, in which cases the MS is not certain whether or not the network has received and accepted the LR attempt. The non-GPRS update status on the SIM and/or the GPRS update status are set to "NOT UPDATED" depending on the specific location registration procedure and their outcome. + +L5 LR request – The MS enters this state when determining that a LR request is to be made. + +L6 LR pending – The MS enters this state after having started the LR, waiting for the outcome (response message from the network). + +NOTE This clause does not describe all the cases. For more details refer to 3GPP TS 24.008 [23], 3GPP TS 24.301 [23A] and 3GPP TS 24.501 [64]. + +## 4.4 PLMN selection process + +### 4.4.1 Introduction + +There are two modes for PLMN selection, automatic and manual. These are described in clauses 4.4.3 below and illustrated in figures 2a to 2b in clause 5. + +NOTE: Figures 2a to 2b in clause 5 do not cover CAG selection aspects. + +The MS not operating in SNPN access operation mode over 3GPP access shall perform PLMN selection process. + +The MS operating in SNPN access operation mode over 3GPP access shall not perform PLMN selection process. + +### 4.4.2 Registration on a PLMN + +The MS shall perform registration on the PLMN if the MS is capable of services which require registration. In both automatic and manual modes, the concept of registration on a PLMN is used. An MS successfully registers on a PLMN if: + +- a) the MS has found a suitable cell of the PLMN to camp on; and +- b) an LR request from the MS has been accepted in the registration area of the cell on which the MS is camped (see table 1). + +### 4.4.3 PLMN selection + +The registration on the selected PLMN and the location registration are only necessary if the MS is capable of services which require registration. Otherwise, the PLMN selection procedures are performed without registration. + +The ME shall utilise all the information stored in the SIM related to the PLMN selection; e.g. "HPLMN Selector with Access Technology", "User Controlled PLMN Selector with Access Technology", "Forbidden PLMNs", "Equivalent HPLMN", see 3GPP TS 31.102 [40]. The ME shall also utilise the extension of the "forbidden PLMNs" list that it has stored locally on the ME if available. + +The ME shall either utilise the "Operator controlled PLMN Selector with Access Technology" that it has stored locally on the ME, or the Operator controlled PLMN Selector with Access Technology" stored in the SIM, for the purposes of PLMN selection. + +The "HPLMN Selector with Access Technology", "User Controlled PLMN Selector with Access Technology" and "Operator Controlled PLMN Selector with Access Technology" data files in the SIM include associated access technologies for each PLMN entry, see 3GPP TS 31.102 [40]. The PLMN/access technology combinations are listed in priority order. If an entry indicates more than one access technology, then no priority is defined for the access technologies within this entry and the priority applied to each access technology within this entry is an implementation issue. If no particular access technology is indicated in an entry, it shall be assumed that all access technologies supported by the ME apply to the entry. If an entry only indicates access technologies not supported by the ME, the entry shall be ignored. If an entry indicates at least one access technology supported by the ME, the entry shall be used in the PLMN selection procedures if the other criteria defined for the specific PLMN selection procedures are fulfilled. + +The Mobile Equipment stores a list of "equivalent PLMNs". This list is replaced or deleted at the end of each location update procedure, routing area update procedure, GPRS attach procedure, tracking area update procedure, EPS attach procedure, and registration procedure. The list is deleted by an MS attached for emergency bearer services or for access to RLOS after detach or registered for emergency services after de-registration. The stored list consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that downloaded the list. All PLMNs in the stored list, in all access technologies supported by the PLMN, are regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover. + +When the MS reselects to a cell in a shared network, and the cell is a suitable cell for multiple PLMN identities received on the BCCH or on the EC-BCCH the AS indicates these multiple PLMN identities to the NAS according to 3GPP TS 44.018 [34], 3GPP TS 44.060 [39], 3GPP TS 25.304 [32], 3GPP TS 36.304 [43] and 3GPP TS 38.304 [61]. The MS shall choose one of these PLMNs. If the registered PLMN is available among these PLMNs, the MS shall not choose a different PLMN. + +The MS shall not use the PLMN codes contained in the "HPLMN Selector with Access Technology" data file. + +It is possible for the home network operator to identify alternative Network IDs as the HPLMN. If the EHPLMN list is present, and not empty, the entries in the EHPLMN list are used in the network selection procedures. When attempting to select a network the highest priority EHPLMN that is available shall be selected. If the EHPLMN list is present and is empty or if the EHPLMN list is not present, the HPLMN derived from the IMSI is used for network selection procedures. + +- NOTE 1: The "HPLMN Selector with Access Technology" data file is only used by the MS to get the HPLMN access technologies related to the HPLMN code which corresponds to the PLMN code included in the IMSI if the EHPLMN list is not present or is empty. If the EHPLMN list is present then this data field is applicable to all the entries within the EHPLMN list. +- NOTE 2: Different GSM frequency bands (e.g. 900, 1800, 1900, 400) are all considered GSM access technology. An MS supporting more than one band should scan all the bands it's supports when scanning for GSM frequencies. However GSM COMPACT systems which use GSM frequency bands but with the CBPCCH broadcast channel are considered as a separate access technology from GSM. +- NOTE 3: The inclusion of the HPLMN derived from the IMSI in the EHPLMN list is allowed. The priority of the HPLMN derived from the IMSI is given by its position in the EHPLMN list, see 3GPP TS 31.102 [40]. + +The MS may support minimization of service interruption (MINT). + +#### 4.4.3.1 At switch-on or recovery from lack of coverage + +a) if + +- signal level enhanced network selection is not applicable (see clause 3.11); or +- the MS has stopped applying signal level enhanced network selection according to requirement v) of clause 4.4.3.1.1; + +then the MS selects the registered PLMN or equivalent PLMN (if it is available) using all access technologies that the MS is capable of without considering the "Operator controlled signal threshold per access technology" stored in the USIM; or + +b) if: + +- signal level enhanced network selection is applicable (see clause 3.11); and +- the received signal quality from a candidate PLMN/access technology combination comprising of a registered PLMN or an equivalent PLMN (if it is available) is equal to or greater than the "Operator controlled signal threshold per access technology" of the access technology configured in the USIM. + +the MS shall select the registered PLMN or equivalent PLMN (if it is available) and the access technology for which the received signal quality is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM. If for the registered PLMN or equivalent PLMN there are two or more access technologies for which the received signal quality is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM, it is up to implementation which access technology is selected by the MS. + +and if necessary (in the case of recovery from lack of coverage, see clause 4.5.2) attempts to perform a Location Registration. + +NOTE 1: The MS in automatic network selection mode can end the PLMN search procedure once the registered PLMN or equivalent PLMN is found on an access technology. + +NOTE 2: An MS in automatic network selection mode can use location information to determine which PLMNs can be available in its present location. + +EXCEPTION: As an alternative option to this, if the MS is in automatic network selection mode and it finds coverage of an EHPLMN, the MS may register to that EHPLMN and not return to the registered PLMN or equivalent PLMN. If the EHPLMN list is not present or is empty, and the HPLMN is available, the MS may register on the HPLMN and not return to the registered PLMN or equivalent PLMN. The operator shall be able to control by SIM configuration whether an MS that supports this option is permitted to perform this alternative behaviour. If signal level enhanced network selection is applicable (see clause 3.11), the MS may register to that EHPLMN or HPLMN only over an access technology for which the received signal quality is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM. + +EXCEPTION: As an alternative option to this, if the MS is in automatic network selection mode, the MS has a list of "PLMNs where registration was aborted due to SOR" and the registered PLMN is part of the list of "PLMNs where registration was aborted due to SOR", the MS may choose not to return to the registered PLMN or equivalent PLMN + +and proceed as defined in clause 4.4.3.1.1 with the exception that in iii), the MS considers PLMNs which are in the list of "PLMNs where registration was aborted due to SOR" as lowest priority. + +EXCEPTION: In A/Gb mode an MS with voice capability, shall not search for CPBCCH carriers. In A/Gb mode an MS not supporting packet services shall not search for CPBCCH carriers. + +If successful registration is achieved, the MS indicates the selected PLMN. + +If: + +- there is no registered PLMN; +- registration is not possible due to the PLMN being unavailable or registration failure; or +- signal level enhanced network selection is applicable (see clause 3.11) and the received signal quality of all access technologies (if the MS is capable of and if it is available) from the registered PLMN or equivalent PLMN (if available) is lower than the "Operator controlled signal threshold per access technology" stored in the USIM of the corresponding access technology. + +the MS follows one of the following two procedures depending on its PLMN selection operating mode. At switch on, if the MS provides the optional feature of user preferred PLMN selection operating mode at switch on then this operating mode shall be used. Otherwise, the MS shall use the PLMN selection mode that was used before switching off. + +EXCEPTION: At switch on, if the MS is in manual mode and neither registered PLMN nor PLMN that is equivalent to it is available, but EHPLMN is available, then instead of performing the manual network selection mode procedure of clause 4.4.3.1.2 the MS may select and attempt registration on the highest priority EHPLMN. If the EHPLMN list is not available or is empty and the HPLMN is available, then the MS may select and attempt registration on the HPLMN. If the MS supports CAG and needs to select or attempt registration on the highest priority EHPLMN or HPLMN, the MS follows network selection procedures of clause 4.4.3.1.1 bullet m). The MS shall remain in manual mode. + +NOTE 3: If successful registration is achieved, then the current serving PLMN becomes the registered PLMN and the MS does not store the previous registered PLMN for later use. + +EXCEPTION: If registration is not possible on recovery from lack of coverage due to the registered PLMN being unavailable, an MS attached to GPRS services, attached via E-UTRAN or registered via the NG-RAN may, optionally, continue looking for the registered PLMN for an implementation dependent time. + +NOTE 4: An MS attached to GPRS services, attached via E-UTRAN or registered via the NG-RAN should use the above exception only if one or more PDP contexts, PDN connections or PDU sessions are currently active. + +EXCEPTION: At switch on, if the RPLMN is a PLMN with which the MS was registered for disaster roaming services and the MS is registered via non-3GPP access connected to 5GCN or an NG-RAN cell of the RPLMN broadcasts neither the disaster related indication nor a "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" including the MS determined PLMN with disaster condition or an allowable PLMN is available then the MS will ignore RPLMN and its equivalent PLMN. + +##### 4.4.3.1.1 Automatic Network Selection Mode Procedure + +The MS selects and attempts registration on other PLMN/access technology combinations, if available and, for bullets i, ii, iii, iv, v, allowable, in the following order: + +- i) either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present); +- ii) each PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order); +- iii) each PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order); +- iv) other PLMN/access technology combinations with received high quality signal in random order; + +NOTE 1: High quality signal is defined in the appropriate AS specification. + +- v) other PLMN/access technology combinations in order of decreasing signal quality. +- vi) PLMN/NG-RAN combinations for any forbidden PLMNs broadcasting the PLMN ID of the MS determined PLMN with disaster condition or broadcasting the disaster related indication and matching the below conditions: + - a) if the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' is set to true: + - each PLMN in the "list of PLMN(s) to be used in disaster condition" stored in the ME which is associated with the PLMN ID of the MS determined PLMN with disaster condition, if any, ordered based on this list; otherwise + - if the ME does not have a stored "list of PLMN(s) to be used in disaster condition" associated with the PLMN ID of the MS determined PLMN with disaster condition, each PLMN in the "list of PLMN(s) to be used in disaster condition" stored in the ME which is associated with the PLMN ID of the HPLMN, if any, ordered based on this list. + - b) if the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' is set to false: + - each PLMN in the "list of PLMN(s) to be used in disaster condition" stored in the ME which is associated with the HPLMN, if any, ordered based on this list. +- vii) PLMN /NG-RAN combinations for other forbidden PLMNs broadcasting the PLMN ID of the MS determined PLMN with disaster condition or broadcasting the disaster related indication, in random order. + +When following the above procedure the following requirements apply: + +- a) An MS with voice capability shall ignore PLMNs for which the MS has identified at least one GSM COMPACT. +- b) In A/Gb mode or GSM COMPACT, an MS with voice capability, or an MS not supporting packet services shall not search for CPBCCH carriers. +- c) In ii and iii, the MS should limit its search for the PLMN to the access technology or access technologies associated with the PLMN in the appropriate PLMN Selector with Access Technology list (User Controlled or Operator Controlled selector list). + +An MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of. The priority ordering amongst the access technologies is implementation dependent. + +- d) In iv, v, vi and vii, the MS shall search for all access technologies it is capable of, before deciding which PLMN to select. +- e) In ii, and iii, a packet only MS which supports GSM COMPACT, but using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of and shall assume GSM COMPACT access technology as the lowest priority radio access technology. +- f) In i, the MS shall search for all access technologies it is capable of. No priority is defined for the preferred access technology and the priority is an implementation issue, but "HPLMN Selector with Access Technology" data file on the SIM may be used to optimise the procedure. +- g) In i, an MS using a SIM without access technology information storage (i.e. the "HPLMN Selector with Access Technology" data file is not present) shall search for all access technologies it is capable of. The priority ordering amongst the access technologies is implementation dependent. A packet only MS which supports GSM COMPACT using a SIM without access technology information storage shall also assume GSM COMPACT access technology as the lowest priority radio access technology. + +NOTE 2: For f) and g), the MS in automatic network selection mode can end the PLMN search procedure once the HPLMN or the highest priority EHPLMN is found on an access technology. + +NOTE 3: For i, ii and iii, the MS can use location information to determine which PLMNs can be available in its present location. + +- h) In v, the MS shall order the PLMN/access technology combinations in order of decreasing signal quality within each access technology. The order between PLMN/access technology combinations with different access technologies is an MS implementation issue. + +NOTE 4: Requirements a) and b) apply also to requirement d), so a GSM voice capable MS should not search for GSM COMPACT PLMNs, even if capable of GSM COMPACT. + +NOTE 5: Requirements a) and b) apply also to requirement f), so a GSM voice capable MS should not search for GSM COMPACT PLMNs, even if this is the only access technology on the "HPLMN Selector with Access Technology" data file on the SIM. + +- i) In i to vii, the MS shall not consider PLMNs where voice service was not possible as PLMN selection candidate, unless such PLMN is available in GERAN or UTRAN or no other allowed PLMN is available. + +- j) In i to v, if the MS only supports EMM-REGISTERED without PDN connection (see 3GPP TS 24.301 [23A]), the MS shall not consider PLMNs which do not advertise support of EMM-REGISTERED without PDN connection. + +- k) In i to v, if the MS only supports control plane CIoT EPS optimization (see 3GPP TS 24.301 [23A]) and the MS camps on a E-UTRA cell which is not NB-IoT cell (see 3GPP TS 36.304 [43], 3GPP TS 36.331 [42]), the MS shall not consider PLMNs which do not advertise support of EPS services with control plane CIoT EPS optimization. + +- l) In i to vii, if the MS is in eCall only mode, the MS shall not consider PLMNs which do not advertise support for eCall over IMS, unless such PLMNs are available in GERAN or UTRAN. + +NOTE 6: As an implementation option, an MS in eCall only mode that was not able to select any PLMN according to l) can perform a second iteration of i to v with no restriction. + +- m) In i to vii, if the MS supports CAG and: + +- 1) is provisioned with a non-empty "CAG information list", the MS shall consider a PLMN indicated by an NG-RAN cell only if: + +- A) the cell is a CAG cell and broadcasts a CAG-ID for the PLMN such that there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is authorized based on the "Allowed CAG list" of the entry; or + +- B) the cell is not a CAG cell and: + +- there is no entry with the PLMN ID of the PLMN in the "CAG information list"; or +- there exists an entry with the PLMN ID of the PLMN in the "CAG information list" but the "indication that the MS is only allowed to access 5GS via CAG cells" is not included in the entry; or + +- 2) is provisioned with an empty "CAG information list" or is not provisioned with a "CAG information list", the MS shall consider a PLMN indicated by an NG-RAN cell only if the cell is not a CAG cell. + +- n) In i to vii, if the MS only supports control plane CIoT 5GS optimization (see 3GPP TS 23.501 [62]) and the MS camps on an E-UTRA cell connected to 5GCN, which is not NB-IoT cell (see 3GPP TS 36.304 [43], 3GPP TS 36.331 [42]), the MS shall not consider PLMNs which do not advertise support of 5GS services with control plane CIoT 5GS optimization. + +- o) In i to vii, if the MS supports CIoT 5GS optimizations, the MS shall not consider the PLMN/access technology combinations for which the MS preferred CIoT network behaviour is not advertised as supported by the PLMN/access technology combination (see 3GPP TS 24.501 [64]). + +NOTE 7: As an implementation option, the MS supporting CIoT 5GS optimizations that was not able to select any PLMN according to o) can perform a second iteration of i to v with no restriction. + +- p) In iii, the MS shall use the PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" stored in the ME, if the last update of the "Operator Controlled PLMN Selector with Access Technology" was due to receiving steering of roaming information containing the "list of preferred + +PLMN/access technology combinations" (see annex C) and storing it in the ME. Otherwise, the MS shall use the "Operator Controlled PLMN Selector with Access Technology" list retrieved from the SIM. + +q1) for vi and vii, if a forbidden PLMN is broadcasting the "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN", the MS shall determine the MS determined PLMN with disaster condition as follows: + +i) if the MS's RPLMN is included in any "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" broadcast by any NG-RAN cell and is allowable, the MS shall consider that the MS's RPLMN is the MS determined PLMN with disaster condition; or + +ii) if the MS's RPLMN is not included in any "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" broadcast by any NG-RAN cell or the MS's RPLMN is not allowable or the MS does not have a RPLMN (see table 1), the MS shall determine the MS determined PLMN with disaster condition from PLMNs: + +- in the "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" broadcast by any NG-RAN cell; and +- which are allowable; + +in the following order: + +- either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present); +- each PLMN in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order); +- each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order); and +- other PLMNs. + +q2) for vi and vii, if a forbidden PLMN is broadcasting the "disaster related indication", the MS shall attempt to determine the MS determined PLMN with disaster condition as follows: + +1) if the country of the MS's RPLMN matches the country of a PLMN for which any NG-RAN cell broadcasts the "disaster related indication" and the MS's RPLMN is allowable, the MS shall consider that the MS's RPLMN is the MS determined PLMN with disaster condition; or + +2) if the country of the MS's RPLMN does not match the country of any PLMN for which any NG-RAN cell broadcasts the "disaster related indication" or the MS's RPLMN is not allowable, the MS shall determine the MS determined PLMN with disaster condition from allowable PLMN(s) where the country of allowable PLMN(s) matches the country of a PLMN for which any NG-RAN cell broadcasts the "disaster related indication" in the following order: + +- either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present); +- each PLMN in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order); +- each PLMN in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order). + +r) The MS shall perform vi and vii to select a PLMN for disaster roaming services only if: + +- 1) the MS supports MINT; +- 2) the indication of whether disaster roaming is enabled in the UE stored in the ME is set to "Disaster roaming is enabled in the UE"; +- 3) there is no available PLMN which is allowable; + +- 4) the MS is not in 5GMM-REGISTERED state and 5GMM-CONNECTED mode over non-3GPP access (see 3GPP TS 24.501 [64]); +- 4a) the MS does not have a PDN connection via an ePDG connected to EPC; and +- 5) an NG-RAN cell of the PLMN or of a shared network where the PLMN is available: + - A) broadcasts the disaster related indication for the PLMN. The disaster related indication broadcasted by the NG-RAN cell for the PLMN indicates that the PLMN is accessible for disaster inbound roamers, that this PLMN accepts disaster inbound roamers from any PLMN(s) other than the PLMN(s) available on the NG-RAN cell, and that a disaster condition applies to all PLMN(s) other than the PLMN(s) available on the NG-RAN cell in the location of the broadcast. If the disaster related indication is broadcasted, the disaster inbound roamers attempt to determine the MS determined PLMN with disaster condition as per bullet q2); or + +NOTE 8: In case of a shared network, the disaster related indication is broadcasted per PLMN. + +- B) broadcasts a "list of one or more PLMN(s) with disaster condition for which disaster roaming services is offered by the available PLMN" which includes the MS determined PLMN with disaster condition as determined in bullet q1). +- s) In i to vii, if the MS only supports NR RedCap and the MS camps on an NR cell connected to 5GCN, the MS shall not consider PLMNs which do not advertise support of NR RedCap. +- t) In i to vii, if the MS detects a PLMN in satellite NG-RAN access technology which fulfils the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, it shall not consider the PLMN as PLMN selection candidate for satellite NG-RAN access technology. +- u) In i to vii, if the MS detects a PLMN in a satellite E-UTRAN access technology which fulfils the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, it shall not consider the PLMN as PLMN selection candidate for the satellite E-UTRAN access technology. +- v) In i), ii), iii), and v), if: + - signal level enhanced network selection is applicable (see clause 3.11); and + - the received signal quality of the candidate PLMN/access technology combination is lower than the threshold value indicated for the access technology in the "Operator controlled signal threshold per access technology" stored in the USIM. + +the MS shall not consider the PLMN(s) in i) and PLMN/access technology combination(s) in ii), iii) and v) as selection candidate. If the received signal quality from none of the candidate PLMN(s) or PLMN/access technology combination(s) is equal to or greater than the "Operator controlled signal threshold per access technology" stored in the USIM, the MS shall stop applying signal level enhanced network selection and repeat the network selection procedure as specified in clause 4.4.3.1. + +If successful registration is achieved, the MS indicates the selected PLMN. + +If registration cannot be achieved because no PLMNs are available and allowable, and the MS does not support access to RLOS, the MS indicates "no service" to the user, waits until a new PLMN is available and allowable and then repeats the procedure. + +If there were one or more PLMNs which were available and allowable, but an LR failure made registration on those PLMNs unsuccessful or an entry in any of the lists "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "CAG information list", or "PLMNs not allowed to operate at the present UE location" prevented a registration attempt, the MS selects the first such PLMN again and enters a limited service state. + +If: + +- the MS supports access to RLOS; +- either the UICC containing the USIM is not present in the MS, or the UICC containing the USIM is present in the MS and the MCC part of the IMSI in the USIM is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]); + +- one or more PLMNs offering access to RLOS has been found; +- registration cannot be achieved on any PLMN; and +- the MS is in limited service state, + +the MS shall select a PLMN offering access to RLOS as follows: + +- a) if at least one preferred PLMN exists based on the RLOS preferred PLMN list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]) and the MCC part of the preferred PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]), the MS shall select the preferred PLMN offering access to RLOS and indicate the selected preferred PLMN for access to RLOS; and +- b) if none of the preferred PLMNs for access to RLOS is available, the MS shall evaluate the remaining PLMNs offering access to RLOS that are not in the RLOS preferred PLMN list. If the MCC part of a PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]), the MS shall select this PLMN and indicate the selected PLMN for access to RLOS. + +If registration cannot be achieved because no PLMNs are available and allowable, and if no PLMN offering access to RLOS has been found, or none of the PLMNs offering access to RLOS is allowed to be accessed according to the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]), or the MS does not support access to RLOS, the MS indicates "no service" to the user, waits until a new PLMN is available and then repeats the procedure. + +##### 4.4.3.1.2 Manual Network Selection Mode Procedure + +The MS indicates whether there are any PLMNs, which are available using all supported access technologies. This includes PLMNs in the "forbidden PLMNs" list, "forbidden PLMNs for GPRS service" list, PLMNs which only offer services not supported by the MS, and the list of "PLMNs not allowed to operate at the present UE location". An MS which supports GSM COMPACT shall also indicate GSM COMPACT PLMNs (which use PBCCH). + +If displayed, PLMNs meeting the criteria above are presented in the following order: + +- i) either the HPLMN (if the EHPLMN list is not present or is empty) or, if one or more of the EHPLMNs are available then based on an optional data field on the SIM either only the highest priority available EHPLMN is to be presented to the user or all available EHPLMNs are presented to the user in priority order. If the data field is not present on the SIM, then only the highest priority available EHPLMN is presented; + - ii) PLMN/access technology combinations contained in the " User Controlled PLMN Selector with Access Technology " data file in the SIM (in priority order); + - iii) PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order); + - iv) other PLMN/access technology combinations with received high quality signal in random order; +- NOTE 1: High quality signal is defined in the appropriate AS specification. +- v) other PLMN/access technology combinations in order of decreasing signal quality. + +In ii and iii, an MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead present the PLMNs contained in the "PLMN Selector" data file in the SIM (in priority order). + +In v, requirement h) in clause 4.4.3.1.1 applies. + +In i to v, requirements j), k) and l) in clause 4.4.3.1.1 apply. + +In iii, requirement p) in clause 4.4.3.1.1 applies. + +In GSM COMPACT, the non-support of voice services shall be indicated to the user. + +The HPLMN may provide on the SIM additional information on the available PLMNs. If this information is provided, then the MS shall indicate it to the user. This information, provided as free text may include: + +- preferred partner, +- roaming agreement status, +- supported services + +Furthermore, the MS may indicate whether the available PLMNs are present on the EHPLMN list, the Forbidden list, the User Controlled PLMN List or the Operator Controlled PLMN List. The MS may also indicate that the PLMN is not present on any of these lists. + +If: + +- the MS supports MINT; +- the MS is not registered via non-3GPP access connected to 5GCN; +- the MS has detected that the RPLMN is a MS determined PLMN with disaster condition as broadcasted by an NG-RAN cell of an available PLMN(s) (see clause 4.4.3.1.1); +- only forbidden PLMN(s) are available; and +- the MS receives indication that some of the forbidden PLMN(s) provide disaster roaming services to the MS(s) of the RPLMN (see clause 4.4.3.1.1), + +then the MS may indicate to the user that those PLMN(s) support disaster roaming services. + +In i to v, if the MS supports CAG, for each PLMN/access technology combination of NG-RAN access technology, the MS shall present to the user: + +- a) the PLMN/access technology combination and a list of CAG-IDs composed of one or more CAG-IDs such that for each CAG-ID: + - 1) there is an available CAG cell which broadcasts the CAG-ID for the PLMN; and + - 2) the following is true: + - i) there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is authorized based on the "Allowed CAG list" of the entry; or + - ii) the available CAG cell broadcasting the CAG-ID for the PLMN also broadcasts that the PLMN allows a user to manually select the CAG-ID. + +For each of the presented CAG-ID, the MS may indicate to the user whether the CAG-ID is authorized based on the "Allowed CAG list" stored in the UE; and + +- b) the PLMN/access technology combination without a list of CAG-IDs, if there is an available NG-RAN cell which is not a CAG cell for the PLMN. If there exists an entry for the presented PLMN in the "CAG information list" and the entry includes an "indication that the MS is only allowed to access 5GS via CAG cells", the MS may indicate to the user that the MS is only allowed to access the PLMN via CAG cells. + +If the NAS receives a human-readable network name associated with a CAG-ID and a PLMN ID from the AS, the human-readable network name shall be sent along with the CAG-ID and PLMN ID to the upper layer for use in manual CAG selection. + +NOTE 2: A human-readable network name can be broadcasted per CAG-ID and PLMN ID by a CAG cell. + +Upon selection of a PLMN (and CAG-ID if the user selected a desired CAG-ID as well) by the user, the NAS shall provide the AS with the selected PLMN ID (and CAG-ID if the user selected a desired CAG-ID as well or an indication to select a non-CAG cell if the user did not select any CAG-ID) and the MS initiates registration on this PLMN (and on a cell which broadcasts the CAG-ID if the user selected a desired CAG-ID as well) using the access technology chosen by the user for that PLMN or using the highest priority available access technology for that PLMN, if the associated access technologies have a priority order (this may take place at any time during the presentation of PLMNs). For such a registration, the MS shall ignore the contents of the "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of + +service", "forbidden PLMNs for GPRS service", "PLMNs not allowed to operate at the present UE location" and "forbidden PLMNs" lists. Also for such a registration, if the NAS has provided the AS with an indication to select: + +- a non-CAG cell, the MS shall ignore the "indication that the MS is only allowed to access 5GS via CAG cells", if any, in the "CAG information list" for the selected PLMN; or +- a selected CAG-ID and the CAG-ID is not authorized based on the "Allowed CAG list" associated with that PLMN in the "CAG information list", the MS shall consider the selected CAG-ID of the selected PLMN as authorized based on the "Allowed CAG list" for the selected PLMN for this registration attempt. + +NOTE 3: It is an MS implementation option whether to indicate access technologies to the user. If the MS does display access technologies, then the access technology selected by the user is only used for initial registration on the selected PLMN. If the MS does not display access technologies, then the access technology chosen for a particular PLMN should be the highest priority available access technology for that PLMN, if the associated access technologies have a priority order, and is only used for initial registration. + +If the MS has, or is establishing, a PDU session for emergency services, a PDN connection for emergency bearer services or a PDP context for emergency bearer services or CS emergency call, being registered for emergency services or having an ongoing emergency services fallback procedure, manual network selection shall not be performed. + +After selection of a PLMN and CAG-ID, if the AS does not provide an indication of finding a cell belonging to the selected PLMN and which broadcasts the selected CAG-ID for the registration procedure (see 3GPP TS 38.304 [40]), then: + +- i) the MS shall indicate to user that it can not find the selected PLMN and CAG-ID; and +- ii) If there is an "indication that the MS is only allowed to access 5GS via CAG cells" in the "CAG information list" for the selected PLMN, the MS may attempt to camp on a suitable CAG cell broadcasting a CAG-ID authorized based on the "Allowed CAG list" for the selected PLMN or an acceptable cell, otherwise the MS may attempt to camp on a suitable cell belonging to the selected PLMN (i.e. a non-CAG cell or a CAG cell broadcasting a CAG-ID authorized based on the "Allowed CAG list" for the selected PLMN) or an acceptable cell. + +Once the MS has registered on a PLMN selected by the user, the MS shall not automatically register on a different PLMN unless: + +- i) the new PLMN is declared as an equivalent PLMN by the registered PLMN. If the MS is registered for disaster roaming services, the UE shall also detect that the new PLMN offers disaster roaming services to the MS determined PLMN with disaster condition as broadcasted by the NG-RAN cell of the new PLMN (see clause 4.4.3.1.1) and that the MS determined PLMN with disaster condition in the old PLMN is also a MS determined PLMN with disaster condition in the new PLMN; +- ii) the user selects automatic mode; +- iii) the user initiates an emergency call while the MS is in limited service state and either the network does not broadcast the indication of support of emergency calls in limited service state, the registration request for emergency services is rejected by the network or the attach request for emergency bearer services is rejected by the network; or +- iv) the user initiates access to RLOS, while the MS is in limited service state and either the network does not broadcast the indication of support of RLOS in limited service state, or the EPS attach request for access to RLOS is rejected by the network, or the EPS tracking area update request for access to RLOS is rejected by the network. + +NOTE 4: If case iii) or iv) occurs, the MS can provide an indication to the upper layers that the MS has exited manual network selection mode. + +Once the MS has registered on a PLMN selected by the user, the MS may automatically register on a different PLMN if: + +- 1) the MS supports MINT; +- 2) the "list of PLMN(s) to be used in disaster condition" is non-empty; +- 3) there is no available PLMN which is declared as an equivalent PLMN by the RPLMN; and + +- 4) the RPLMN of the MS is considered as the MS determined PLMN with disaster condition based on the determination of the MS determined PLMN with disaster condition as specified in clause 4.4.3.1.1. + +NOTE 5: If the above case occurs, the MS can provide an indication to the upper layers that the MS has exited manual network selection mode. + +If the user does not select a PLMN (or PLMN and CAG-ID), the selected PLMN shall be the one that was selected before the PLMN selection procedure started. If no such PLMN was selected or that PLMN is no longer available, then the MS shall attempt to camp on any acceptable cell and enter the limited service state. + +If: + +- the MS supports access to RLOS; +- either the UICC containing the USIM is not present in the MS, or the UICC containing the USIM is present in the MS and the MCC part of the IMSI in the USIM is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]); +- one or more PLMNs offering access to RLOS has been found; +- registration cannot be achieved on any PLMN; and +- the MS is in limited service state, + +the MS indicates the PLMNs offering access to RLOS, presented in the following order: + +- i) PLMNs contained in the RLOS preferred PLMN list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]) (in priority order) if the MCC part of the preferred PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]); and +- ii) any of the remaining PLMNs offering access to RLOS that are not in the RLOS preferred PLMN list if the MCC part of the PLMN ID is present in the RLOS allowed MCC list configured in the USIM (see 3GPP TS 31.102 [40]) or in the ME (see 3GPP TS 24.368 [50]). + +Upon selection of a PLMN by the user, the MS initiates registration for access to RLOS on the PLMN chosen by the user (this may take place at any time during the presentation of PLMNs). + +##### 4.4.3.1.3 Manual CSG selection + +###### 4.4.3.1.3.1 General + +The HPLMN may configure the MS whether to provide to the user CSGs for a certain PLMN without any restriction or to provide to the user only CSGs in the Operator CSG List for that PLMN. This configuration may be done either: + +- in the USIM if the Operator CSG list is available in the USIM; or +- as described in 3GPP TS 24.285 [47]. + +In the absence of such configuration from the HPLMN for a certain PLMN, the MS shall by default provide to the user CSGs for that PLMN without any restriction. + +For PLMNs where no restriction is configured, the MS provides to the user the CSGs that are available and the associated PLMNs using all access technologies which support CSGs (see 3GPP TS 23.003 [22A]) and which are supported by the MS. For each entry in the list, an indication is provided whether that CSG identity is in the Allowed CSG list or in the Operator CSG list stored in the MS for this PLMN. + +For PLMNs where the MS is configured to provide to the user only CSGs in the Operator CSG List, the MS provides to the user the CSGs that are available and in the Operator CSG list, using all access technologies which support CSGs (see 3GPP TS 23.003 [22A]) and which are supported by the MS. For each entry in the list, the MS provides to the user the associated PLMN and an indication that the CSG identity is in the Operator CSG List stored in the MS for this PLMN. + +Additional requirements for the display, including for the display of HNB name, can be found in 3GPP TS 22.220 [49]. + +The user may select a CSG from the indicated CSGs. + +If the MS has a PDN connection for emergency bearer services, manual CSG selection shall not be performed. + +###### 4.4.3.1.3.2 Manual CSG selection within the RPLMN + +If the user selects a CSG whose CSG identity is not included in the Allowed CSG list or Operator CSG list, then the MS shall attempt to register on a cell that corresponds to the CSG. For such a registration, the MS shall ignore the contents of the "forbidden location areas for roaming", "forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service" and "forbidden PLMNs for GPRS service" lists. + +Upon successful or unsuccessful completion of the registration or if registration is not possible, because the MS is no longer in the coverage of the selected CSG, the MS shall return to automatic CSG selection mode. + +Manual CSG selection within the RPLMN does not affect the current PLMN selection mode. + +###### 4.4.3.1.3.3 Manual CSG selection in a PLMN different from the RPLMN + +If the user selects a CSG in a PLMN that is different from the RPLMN, then the following applies: + +- i) The MS shall store a duplicate of the RPLMN and a duplicate of the PLMN selection mode that were in use before the manual CSG selection was initiated, unless this manual CSG selection follows another manual CSG selection or a PLMN selection triggered by ProSe communications as specified in clause 3.1B or a PLMN selection triggered by V2X communication over PC5 as specified in clause 3.1C or a PLMN selection triggered by A2X communication over PC5 as specified in clause 3.1D; +- ii) The MS shall enter into Manual mode of PLMN selection in state M4 (Trying PLMN) as defined in clause 4.3.1.2; +- iii) The MS shall select the PLMN corresponding to the CSG and attempt to register on the selected CSG cell in the PLMN. For such a registration, the MS shall ignore the contents of the "forbidden location areas for roaming", "forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" and "forbidden PLMNs" lists. If the registration is successful the MS remains in manual CSG selection mode, until the user selects automatic CSG selection mode, the MS is switched off or the condition of any of items iv) to viii) below is fulfilled; +- iv) If the registration fails or the MS is no longer in the coverage of the selected CSG, then the MS shall return to the stored duplicate PLMN selection mode and automatic CSG selection mode and use the stored duplicate value of RPLMN for further action; +- v) If the MS is switched off while on the selected CSG and switched on again, the MS should return to the stored duplicate PLMN selection mode, unless the MS provides the optional feature of user preferred PLMN selection operating mode at switch on. Additionally, the MS shall use the stored duplicate value of RPLMN and automatic CSG selection mode for further action; +- vi) If the user initiates a PLMN selection while on the selected CSG, the MS shall delete the stored duplicate PLMN selection mode, use the stored duplicate value of RPLMN as RPLMN, return to automatic CSG selection mode and follow the procedures (as specified for switch-on or recovery from lack of coverage) in clause 4.4.3.1. The MS shall delete the stored duplicate value of RPLMN once the PLMN selection has been completed successfully; +- vii) If the MS's E-UTRA capability is disabled as a result of successful registration (as described in 3GPP TS 24.301 [23A] clauses 5.5.1.3.4.2, 5.5.1.3.4.3, 5.5.3.3.4.2 and 5.5.3.3.4.3) and the selected CSG is not available on UTRAN radio access technology, the MS shall re-enable the E-UTRA capability, return to the stored duplicate PLMN selection mode and automatic CSG selection mode and use the stored duplicate value of RPLMN for further action; and +- viii) If the MS's E-UTRA capability is disabled as a result of performing the service request procedure (as described in 3GPP TS 24.301 [23A] clause 5.6.1.5), the selected CSG is not available on UTRAN radio access technology and the MS performed a CS call, then after the end of the call, the MS shall re-enable the E-UTRA capability, return to the stored duplicate PLMN selection mode and automatic CSG selection mode and use the stored duplicate value of RPLMN for further action. + +#### 4.4.3.2 User reselection + +At any time the user may request the MS to initiate reselection and registration onto an available PLMN, according to the following procedures, dependent upon the operating mode. + +##### 4.4.3.2.1 Automatic Network Selection Mode + +The MS selects and attempts registration on PLMN/access technology combinations, if available and allowable, in all of its bands of operation in accordance with the following order: + +- i) the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present); +- ii) PLMN/access technology combinations contained in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) excluding the previously selected PLMN/access technology combination; +- iii) PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order) excluding the previously selected PLMN/access technology combination; +- iv) other PLMN/access technology combinations with the received high quality signal in random order excluding the previously selected PLMN/access technology combination; + +NOTE 1: High quality signal is defined in the appropriate AS specification. + +- v) other PLMN/access technology combinations, excluding the previously selected PLMN/access technology combination in order of decreasing signal quality or, alternatively, the previously selected PLMN/access technology combination may be chosen ignoring its signal quality; +- vi) The previously selected PLMN/access technology combination. + +The previously selected PLMN/access technology combination is the PLMN/access technology combination which the MS has selected prior to the start of the user reselection procedure. + +NOTE 2: If the previously selected PLMN is chosen, and registration has not been attempted on any other PLMNs, then the MS is already registered on the PLMN, and so registration is not necessary. + +The equivalent PLMNs list shall not be applied to the user reselection in Automatic Network Selection Mode. + +When following the above procedure, the requirements a), b), c), e), f), g), h), j), k), l), m), n), o), p) and v) in clause 4.4.3.1.1 apply: Requirement d) shall apply as shown below: + +- d) In iv, v, and vi, the MS shall search for all access technologies it is capable of before deciding which PLMN/access technology combination to select. + +##### 4.4.3.2.2 Manual Network Selection Mode + +The Manual Network Selection Mode Procedure of clause 4.4.3.1.2 is followed. + +##### 4.4.3.2.3 Manual CSG selection + +The procedure of clause 4.4.3.1.3 is followed. + +#### 4.4.3.3 In VPLMN + +##### 4.4.3.3.1 Automatic and manual network selection modes + +###### 4.4.3.3.1.1 Automatic and manual network selection modes when not registered for disaster roaming services + +If the MS is in a VPLMN and not registered for disaster roaming services, and the MS shall periodically attempt to obtain service on its HPLMN (if the EHPLMN list is not present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a higher priority PLMN/access technology combinations listed in "user controlled PLMN selector" or "operator controlled PLMN selector" by scanning in accordance with the requirements that are applicable to i), ii) and iii) as defined in the Automatic Network Selection Mode in clause 4.4.3.1.1. + +NOTE 1: Additionally if signal level enhanced network selection is applicable and the received signal quality of the registered PLMN is lower than the "Operator controlled signal threshold per access technology", the procedures defined in clause 4.4.3.5 are applicable. + +For this purpose, a value of timer T may be stored in the SIM. The interpretation of the stored value depends on the radio capabilities supported by the MS: + +- For an MS that does not support any of the following: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]); + - a) if the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, T is in the range 6 multiplied by integer M minutes to 8 multiplied by integer M hours in 6 multiplied by integer M minutes steps or T indicates that no periodic attempts shall be made. If no value for M is stored in the SIM, a default value of M equal to one is used; or + - b) otherwise, T is either in the range 6 minutes to 8 hours in 6 minutes steps or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 60 minutes is used for T. +- For an MS that only supports any of the following or a combination of: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using 2 hour steps from 2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 72 hours is used. +- For an MS that supports both: + - a) any of the following or a combination of: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]); and + - b) any other than the following: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]), + +T is interpreted depending on what is in use as specified below: + +- a) if the MS is using any of the following at the time of starting timer T: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 2 hours to 240 hours, using 2 hour steps from 2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 72 hours is used; and +- b) if the MS is not using any of the following at the time of starting timer T: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]), T is either in the range 6 minutes to 8 hours in 6 minutes steps or it indicates that no periodic attempts shall be made. If the MS is using the satellite NG-RAN access technology or the satellite E-UTRAN access technology with a shared MCC at the time of starting timer T: T is in the range 6 multiplied by integer M minutes to 8 multiplied by integer M hours in 6 multiplied by integer M minutes steps. If no value for M is stored in the SIM, a default value of M equal to one is used. If no value for T is stored in the SIM, a default value of 60 minutes is used for T. + +If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer. + +The MS does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or mobile initiated connection only mode (MICO) as described in 3GPP TS 24.501 [64]. + +The MS does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when the access stratum is de-activated due to discontinuous coverage (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]). + +The MS does not stop timer T when it activates unavailability period as described in 3GPP TS 24.501 [64]. + +The MS can be configured for Fast First Higher Priority PLMN search as specified in 3GPP TS 31.102 [40] or 3GPP TS 24.368 [50]. Fast First Higher Priority PLMN search is enabled if the corresponding configuration parameter is present and set to enabled. Otherwise, Fast First Higher Priority PLMN search is disabled. + +The attempts to access the HPLMN or an EHPLMN or higher priority PLMN shall be as specified below: + +- a) The periodic attempts shall only be performed in automatic mode when the MS is roaming, and not while the MS is attached for emergency bearer services, is registered for emergency services, has a PDU session for emergency services or has a PDN connection for emergency bearer services; +- b) The MS shall make the first attempt after a period of at least 2 minutes and at most the time configured for T: + - only after switch on if Fast First Higher Priority PLMN search is disabled; or + - after switch on or upon selecting a VPLMN if Fast First Higher Priority PLMN search is enabled. +- c) The MS shall make the following attempts if the MS is on the VPLMN at time T after the last attempt according to the present clause or according to clause 4.4.3.5; +- d) Periodic attempts shall only be performed by the MS while in idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); +- d1) Periodic attempts may be postponed while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or when the access stratum is deactivated due to discontinuous coverage (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]). +- d2) Periodic attempts may be postponed while the MS is receiving eMBMS transport service in idle mode (see 3GPP TS 23.246 [68]). +- d3) Periodic attempts may be postponed while the MS is receiving broadcast MBS service in idle mode (see 3GPP TS 23.247 [85]). +- d4) Periodic attempts may be postponed till the next eDRX occasion while the MS is configured with eDRX. +- d5) Periodic attempts may be postponed while the MS is in relaxed monitoring (see 3GPP TS 36.304 [43]). +- d6) Periodic attempts may be postponed while the MS is in Mobile Initiated Connection Only mode (MICO). +- d7) Periodic attempts may be postponed while the MS unavailability period is activated as described in 3GPP TS 24.501 [64]. +- e) If the HPLMN (if the EHPLMN list is not present or is empty) or a EHPLMN (if the list is present) or a higher priority PLMN is not found, the MS shall remain on the VPLMN. +- f) In steps i), ii) and iii) of clause 4.4.3.1.1 the MS shall limit its attempts to access higher priority PLMN/access technology combinations to PLMN/access technology combinations of the same country as the current serving VPLMN, as defined in Annex B. + +EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS may attempt to access higher priority PLMN/access technology combinations irrespective of their MCC values. + +EXCEPTION: If the MS is in a VPLMN, the MS may attempt to access higher priority PLMNs with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology irrespective of their MCC values. + +- fl) In the case that the MS has a stored "Equivalent PLMNs" list the MS shall only select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN which are stored in the "Equivalent PLMNs" list. + +EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS shall only select a PLMN if it is of a higher priority than those which are stored in the "Equivalent PLMNs" list. + +EXCEPTION: If the MS is in a VPLMN, the MS shall only select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN or those with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology which are stored in the "Equivalent PLMNs" list. + +- g) Only the priority levels of Equivalent PLMNs of the same country as the current serving VPLMN, as defined in Annex B, and which are not in the list of "PLMNs where registration was aborted due to SOR" if the UE has a list of "PLMNs where registration was aborted due to SOR" shall be taken into account to compare with the priority level of a selected PLMN. +- h) If the PLMN of the highest priority PLMN/access technology combination available is the current VPLMN, or one of the PLMNs in the "Equivalent PLMNs" list and is not in the list of "PLMNs where registration was aborted due to SOR" if the UE has a list of "PLMNs where registration was aborted due to SOR", the MS shall remain on the current PLMN/access technology combination. +- i) In step iii) of clause 4.4.3.1.1 the MS shall consider PLMNs which are in the list of "PLMNs where registration was aborted due to SOR" as lowest priority, if the UE has a list of "PLMNs where registration was aborted due to SOR". +- j) In steps i), ii) and iii) of clause 4.4.3.1.1, if signal level enhanced network selection is applicable (see clause 3.11 and step d) of clause 4.4.3.5), the MS shall only select a PLMN, if the received signal quality of the candidate PLMN/access technology combination is equal to or greater than the "Operator controlled signal threshold per access technology". + +NOTE 2: As an MS implementation option, the MS can make an attempt when the timer TD, TE, TF, TG or TH expires and there is a PLMN/access technology combination which the MS could not select while the timer was running (e.g. the PLMN was in the list of PLMNs where voice service was not possible in E-UTRAN) that is higher priority than the current serving PLMN and belongs to the same country as the current serving PLMN, as defined in Annex B. + +NOTE 3: As an MS implementation option, upon a transition in or out of international areas, a UE supporting satellite NG-RAN or satellite E-UTRAN can attempt to obtain service on a higher priority PLMN as defined in this clause. It is up to the UE implementation to determine when it is transitioning in and out of international areas. What constitutes an international area is out of scope of this specification and not the responsibility of 3GPP. + +###### 4.4.3.3.1.2 Automatic and manual network selection modes when registered for disaster roaming services + +If the MS is registered for disaster roaming services, the MS shall periodically attempt to obtain service on an allowable PLMN of the same country as the current serving PLMN in accordance with the requirements as defined in the Automatic Network Selection Mode in clause 4.4.3.1.1. + +If the MS is registered for disaster roaming services, timer T is either in the range 30 minutes to 40 hours in 30 minute steps, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 60 minutes is used for T. + +If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer. + +The MS does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or mobile initiated connection only mode (MICO) as described in 3GPP TS 24.501 [64]. + +The MS does not stop timer T when it activates unavailability period as described in 3GPP TS 24.501 [64]. + +The attempts to obtain service on an allowable PLMN shall be as specified below: + +- a) The periodic attempts shall only be performed in automatic mode when the MS is registered for disaster roaming services and does not have a PDU session for emergency services; + - a1) The MS shall make the first attempt after a period of at least 2 minutes and at most the time configured for T upon selecting a VPLMN for disaster roaming; +- b) The MS shall make the following attempts if the MS is registered for disaster roaming services at time T after the last attempt; +- c) The periodic attempts shall only be performed by the MS while in idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); +- d) The periodic attempts may be postponed: + - while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]); + - while the MS is receiving eMBMS transport service in idle mode (see 3GPP TS 23.246 [68]); + - while the MS is receiving broadcast MBS service in idle mode (see 3GPP TS 23.247 [85]); + - till the next eDRX occasion while the MS is configured with eDRX; + - while the MS is in relaxed monitoring (see 3GPP TS 36.304 [43]); + - while the MS is in Mobile Initiated Connection Only mode (MICO). + - while the unavailability period is activated in MS as described in 3GPP TS 24.501 [64]. +- e) The MS shall limit its attempts to access allowable PLMN/access technology combinations of the same country as the current serving VPLMN, as defined in Annex B. + +EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS may attempt to access higher priority PLMN/access technology combinations irrespective of their MCC values. + +EXCEPTION: If the MS is in a VPLMN through non-satellite access, the MS may attempt to access higher priority PLMNs with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology. + +##### 4.4.3.3.2 Manual CSG selection + +The procedure of clause 4.4.3.1.3 is followed. + +#### 4.4.3.4 Investigation Scan for higher prioritized PLMN + +The support of this procedure is mandatory if the ME supports GSM COMPACT and otherwise optional. + +An MS capable of both GSM voice and packet service shall, when indicated in the SIM, investigate if there is service from a higher prioritized PLMN not offering GSM voice service, either HPLMN (if the EHPLMN list is not present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a PLMN in a "PLMN Selector with Access Technology " data file on the SIM. + +The MS shall scan for PLMNs in accordance with the requirements described for automatic network selection mode in clause 4.4.3.1.1 that are applicable to i), ii) and iii) with the exception of requirement a) and b) in clause 4.4.3.1. Requirement a) and b) that are specified for automatic network selection mode in clause 4.4.3.1 shall be ignored during the investigation scan. + +If indicated on the SIM, the investigation scan shall be performed: + +- i) After each successful PLMN selection and registration is completed, when the MS is in idle mode. This investigation scan may rely on the information from the already performed PLMN selection and may not necessarily require a rescan +- ii) When the MS is unable to obtain normal service from a PLMN, (limited service state) see clause 3.5. + +The investigation scan is restricted to automatic selection mode and shall only be performed by an MS that is capable of both voice and packet data. It shall only be performed if the selected PLMN is not already the highest prioritized PLMN in the current country. (HPLMN in home country, otherwise according to PLMN selector lists) + +The MS shall return to RPLMN after the investigation scan is performed. + +If a higher prioritized PLMN not offering GSM voice service is found, this shall be indicated to the user. The MS shall not select the PLMN unless requested by the user. + +#### 4.4.3.5 Periodic attempts for signal level enhanced network selection + +If signal level enhanced network selection is applicable (see clause 3.11) and the received signal quality of registered PLMN observed over an averaging window is lower than the "Operator controlled signal threshold per access technology" the MS shall periodically attempt to obtain service on an allowable PLMN/access technology combination for which the received signal quality of the candidate PLMN/access technology combination is equal to or greater than the "Operator controlled signal threshold per access technology" in accordance with the requirements that are applicable to i), ii), iii), iv) and v) as defined in the Automatic Network Selection Mode in clause 4.4.3.1.1. For this purpose, the value of the timer $T_{\text{SENSE}}$ is configured with an MS implementation specific value with a minimum value of 2 min and a maximum value set to the value applicable for timer T as defined in clause 4.4.3.1.1. + +The averaging window shall be shorter than the value of the timer $T_{\text{SENSE}}$ . + +The MS does not stop timer $T_{\text{SENSE}}$ , as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or mobile initiated connection only mode (MICO) as described in 3GPP TS 24.501 [64]. + +The MS does not stop timer $T_{\text{SENSE}}$ , as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when the access stratum is de-activated due to discontinuous coverage (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]) or when the MS activates unavailability period as described in 3GPP TS 24.501 [64]. + +The attempts to obtain service on an allowable PLMN shall be as specified below: + +- a) The periodic attempts shall only be performed in automatic mode, and not while the MS is attached for emergency bearer services, is registered for emergency services, has a PDN connection for emergency bearer services or has a PDU session for emergency services. +- b) When the MS detects that the received signal quality of the current cell of the registered PLMN is below the "Operator controlled signal threshold per access technology" either upon registration or any time later, the MS shall start timer $T_{\text{SENSE}}$ , if not already running. +- c) If upon expiry of timer $T_{\text{SENSE}}$ the received signal quality of the registered PLMN observed over an averaging window is equal to or greater than the "Operator controlled signal threshold per access technology" the MS shall stay on the current selected PLMN. If timer T defined in clause 4.4.3.1.1 expires while timer $T_{\text{SENSE}}$ is running and the received signal quality of registered PLMN observed over an averaging window is lower than the "Operator controlled signal threshold per access technology", the MS shall stop timer $T_{\text{SENSE}}$ and shall perform the actions defined in this clause instead of the action defined for timer T expiry defined in clause 4.4.3.1.1. +- d) If the received signal quality of the registered PLMN and all other available and allowable PLMN/access technology combinations are lower than the "Operator controlled signal threshold per access technology", the MS shall stop applying signal level enhanced network selection and repeat the network selection procedure as specified in clause 4.4.3.1.1. +- e) The attempts shall only be performed by the MS while in idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). +- f) The attempts may be postponed: + +- while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]) or when the access stratum is deactivated due to discontinuous coverage or when the UE activated unavailability period (see 3GPP TS 23.401 [58] and 3GPP TS 24.301 [23A]); + - while the MS is receiving eMBMS transport service in idle mode (see 3GPP TS 23.246 [68]); + - till the next eDRX occasion while the MS is configured with eDRX; + - while the MS is in relaxed monitoring (see 3GPP TS 36.304 [43]); + - while the MS is in Mobile Initiated Connection Only mode (MICO). +- g) The MS shall limit its attempts to access allowable PLMN/access technology combinations of the same country as the current serving VPLMN, as defined in Annex B. + +EXCEPTION: If the MS is in a VPLMN through satellite NG-RAN access or satellite E-UTRAN access with a shared MCC, the MS may attempt to access higher priority PLMN/access technology combinations irrespective of their MCC values. + +EXCEPTION: If the MS is in a VPLMN through non-satellite access, the MS may attempt to access higher priority PLMNs with a shared MCC with satellite NG-RAN access technology or satellite E-UTRAN access technology. + +### 4.4.4 Abnormal cases + +If there is no SIM in the MS, if there is an authentication failure, or if the MS receives an "IMSI unknown in HLR", "illegal ME" or "illegal MS" response to an LR request, then effectively there is no selected PLMN ("No SIM" state). In these cases, the states of the cell selection process are such that no PLMN selection information is used. Except when performing GPRS attach, EPS attach for emergency bearer services, an initial registration for emergency services, or EPS attach for access to RLOS, no further attempts at registration on any PLMN are made until the MS is switched off and on again, or a SIM is inserted. When performing GPRS attach, EPS attach for emergency bearer services, an initial registration for emergency services or EPS attach for access to RLOS, the PLMN of the current serving cell is temporarily considered as the selected PLMN. + +When in Automatic Network Selection mode and the MS is in the "not updated" state with one or more suitable cells to camp on; then after the maximum allowed unsuccessful LR requests (controlled by the specific attempt counters) the MS may continue (or start if it is not running) the user reselection procedure of clause 4.4.3.2.1. + +A multi mode MS that also supports 3GPP2 access technology may fall back to 3GPP2 mode if no SIM is inserted. + +### 4.4.5 Roaming not allowed in this LA or TA + +If in either PLMN selection mode the LR response "Roaming not allowed in this LA" or "Roaming not allowed in this TA" is received: + +The PLMN Automatic or Manual Mode Selection Procedure of clause 4.4.3.1 are followed, depending on whether the MS is in automatic or manual mode. + +### 4.4.6 Steering of roaming + +If the MS receives a USAT REFRESH command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming", the MS shall: + +- a) replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME with the list provided in the REFRESH command, if any, or replace the SOR-CMCI in the ME with the SOR-CMCI provided in REFRESH command, if any, or both; +- b) delete the PLMNs identified by the list in the REFRESH command from the Forbidden PLMN list and from the Forbidden PLMNs for GPRS service list, if they are present in these lists. This includes any information stored in the SIM and the ME internal memory; +- c) take the new information into account in subsequent attempts to access a higher priority PLMN; and + +- d) attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired. + +In order to avoid unnecessary signalling, the network operator should avoid repeatedly using steering of roaming of a particular MS. + +## 4.5 Location registration process + +### 4.5.1 General + +When the MS is switched on and capable of services requiring registration, the action taken by the location registration process is as follows: + +- a) SIM present and no LR needed (because of the status of the stored registration area identity and "attach" flag): The MS is in the update state "Updated"; +- b) SIM present and LR needed: A LR request is made; +- c) No SIM present: The MS enters the update state "Idle, No IMSI". + +In case b) above, and subsequently whenever a LR request is made, the MS enters a state depending on the outcome of the LR request, as listed in clause 4.3.3 above. In case c) the GPRS and the non-GPRS update state enters "Idle, No IMSI". + +Whenever the MS goes to connected mode and then returns to idle mode again, the MS selects the appropriate state. + +A multi mode MS that also supports 3GPP2 access technology may fall back to 3GPP2 mode if no SIM is inserted. + +### 4.5.2 Initiation of Location Registration + +An LR request indicating Normal Updating is made when, in idle mode, + +- the MS changes cell while the update status is "NOT UPDATED"; (for MS capable of GPRS and non-GPRS services when at least one of both update statuses is "NOT UPDATED") +- the MS detects that it has entered a new registration area, i.e., when the received registration area identity differs from the one stored in the MS, and the LAI, TAI or PLMN identity is not contained in any of the lists of "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" respectively, while being in one of the following update statuses: + - UPDATED; + - NOT UPDATED; + - ROAMING NOT ALLOWED. +- the MS detects that it has entered a new registration area, i.e., when the received registration area identity differs from the one stored in the MS, and the MS is attached for access to RLOS; +- the MS detects that it has entered a registration area that has the same identity as the one stored in the MS, while the update status is "ROAMING NOT ALLOWED", and + - the LAI, TAI or PLMN identity is not contained in any of the lists of "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs" respectively; and +- if the selected cell is a satellite NG-RAN cell or a satellite E-UTRAN cell, it does not fulfil the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, i.e. it is considered as candidate for PLMN selection. + +- the periodic location updating timer expires while the non-GPRS update status is "NOT UPDATED" (triggers location updating); +- the periodic routing area update timer expires while the GPRS update status is "NOT UPDATED" (triggers routing area update); +- the periodic tracking area update timer expires while the EPS update status is "NOT UPDATED" (triggers tracking area update); +- the periodic registration update timer expires while the 5GS update status is "NOT UPDATED" (triggers mobility and periodic registration update procedure); +- a manual network reselection has been performed, an acceptable cell of the selected PLMN or the selected SNPN is present, and the MS is not in the update status "UPDATED" on the selected PLMN or the selected SNPN; or +- emergency bearer services over packet services are requested by upper layers. + +An MS which is attached for PS services other than RLOS and enters a new PLMN shall perform a routing area update or a tracking area update or an MS which is registered via NG-RAN and enters a new PLMN or SNPN shall perform a registration update if the following conditions are fulfilled: + +- a) if the MS: + - 1) does not operate in SNPN access operation mode over 3GPP access, is in S1 mode or N1 mode and the currently stored TAI list does not contain the TAI of the current serving cell; or + - 2) operates in SNPN access operation mode over 3GPP access; +- b) the LAI, TAI or PLMN identity of the current serving cell is not contained in any of the lists "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" or "forbidden PLMNs", or the MS has a PDN connection for emergency bearer services, or the MS has a PDU session for emergency services; +- b1) if the selected cell is a satellite NG-RAN cell or a satellite E-UTRAN cell, it does not fulfil the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, i.e. it is considered as candidate for PLMN selection; and +- c) the current update state is different from "Idle, No IMSI"; and + - 1) the MS is configured to perform the attach procedure with IMSI at PLMN change (see "AttachWithIMSI" leaf of the NAS configuration MO in 3GPP TS 24.368 [50] or USIM file NASCONFIG in 3GPP TS 31.102 [40]) and the new PLMN is the registered PLMN or an equivalent PLMN; or + - 2) the MS is not configured to perform the attach procedure with IMSI at PLMN change. + +An MS which is attached for access to RLOS and enters a new PLMN shall perform tracking area update if the following condition is fulfilled: + +- the currently stored TAI list does not contain the TAI of the current serving cell. + +If the new PLMN the MS has entered is neither the registered PLMN nor an equivalent PLMN, an MS which is attached for PS services and configured to perform the attach procedure with IMSI at PLMN change (see "AttachWithIMSI" leaf of the NAS configuration MO in 3GPP TS 24.368 [50] or USIM file NASCONFIG in 3GPP TS 31.102 [40]) shall perform an attach procedure using IMSI as mobile identity. + +An LR request indicating periodic location updating is made when, in idle mode, the periodic location updating timer expires while the non-GPRS update status is "UPDATED". + +An LR request indicating periodic routing area update is made when the periodic routing area update timer expires while the GPRS update status is "UPDATED", except when the MS is attached for emergency bearer services. + +An LR request indicating periodic tracking area update is made when the periodic tracking area update timer expires while the EPS update status is "UPDATED", except when the MS is attached for emergency bearer services. + +An LR request indicating Periodic Registration Updating is made when the periodic registration timer expires while the 5GS update status is "UPDATED", except when the MS is registered for emergency services. + +An LR request indicating IMSI attach is made when the MS is activated in the same location area in which it was deactivated while the non-GPRS update status is "UPDATED", and the system information indicates that IMSI attach/detach shall be used. + +A GPRS attach is made by a GPRS MS when activated and capable of services which require registration. A GPRS attach may only be performed if the selected PLMN is not contained in the list of "forbidden PLMNs for GPRS service". Depending on system information about GPRS network operation mode MSs operating in MS operation mode A or B perform combined or non-combined location registration procedures. When the combined routing area update or GPRS attach is accepted with indication "MSC not reachable" or is not answered the MS performs also the corresponding location updating procedure or falls back to a GPRS only MS. When the combined routing area update or GPRS attach is rejected with cause "GPRS not allowed" the GPRS update status is "ROAMING NOT ALLOWED" and the MS performs the corresponding location updating procedure. + +An LR request indicating Disaster Roaming registration updating is made when the MS supporting MINT needs to register to the PLMN offering disaster roaming services for the first time. + +Furthermore, an LR request indicating normal location updating is also made when the response to an outgoing request shows that the MS is unknown in the VLR or SGSN, respectively. + +Table 2 in clause 5 summarizes the events in each state that trigger a new LR request. The actions that may be taken while being in the various states are also outlined in table 2. + +A GPRS MS which is both IMSI attached for GPRS and non-GPRS services and which is capable of simultaneous operation of GPRS and non-GPRS services shall perform routing area update in connected mode when it has entered a new routing area which is not part of a LA contained in the list of "forbidden location areas for roaming" or "forbidden location areas for regional provision of service". + +### 4.5.3 Periodic Location Registration + +A Periodic Location Updating timer (for non-GPRS operation), a Periodic Routing Area Update timer (for GPRS operation), a Periodic Tracking Area Update timer (for EPS operation) and a Periodic Registration Update timer (for 5GS operation) with the following characteristics shall be implemented in the MS (MS shall implement all timers corresponding to supported operations): + +- i) Upon switch on of the MS or when the system information indicates that periodic location registration shall be applied, and the timer is not running, the timer shall be loaded with a random value between 0 and the broadcast or signalled time-out value and started. +- ii) The time-out value for the periodic location updating timer shall be within the range of 1 deci-hour to 255 deci-hours with a granularity of 1 deci-hour. +- iii) When the timer reaches its expiry value, it shall be initiated with respect to the relevant time-out value, and the MS shall initiate the periodic location registration corresponding to the expired timer. If the MS is attached for emergency bearer services or the MS is registered for emergency services, the MS shall locally detach instead of performing periodic location registration. +- iv) The periodic location updating timer shall be prevented from triggering periodic location updating during connected mode. When the MS returns to idle mode, the periodic location updating timer shall be initiated with respect to the broadcast time-out value, then started. Thereafter, the procedure in iii) shall be followed. +- v) The periodic routing area update timer shall be prevented from triggering the periodic routing area update during Ready state. At transition from Ready to Standby state the periodic routing area update timer shall be initiated with respect to its time-out value, then started. Thereafter, the procedure in iii) shall be followed. +- vi) If the MS performs a successful combined routing area update the periodic location updating timer shall be prevented from triggering the periodic location updating until the MS starts using location updating procedure, for example because of a changed network operation mode or the MS uses non-GPRS services only. +- vii) When a change in the time-out value occurs (at a change of serving cell or a change in the broadcast time-out value or a change in the signalled time-out value), the related timer shall be reloaded so that the new time to expiry will be: "old time to expiry" modulo "new time-out value". + +- viii) The periodic tracking area update timer shall be prevented from triggering periodic tracking Area updating during connected mode. When the MS returns to idle mode, the periodic tracking area update timer shall be initiated with respect to the signalled time-out value, then started. Thereafter, the procedure in iii) shall be followed. +- ix) The periodic registration update timer shall be prevented from triggering periodic registration updating during connected mode. If periodic timer is not running due to Strictly periodic registration feature, when the MS returns to idle mode, the periodic registration update timer shall be initiated with respect to the signalled time-out value, then started. Thereafter, the procedure in iii) shall be followed. + +### 4.5.4 IMSI attach/detach operation + +The system information will contain an indicator indicating whether or not IMSI attach/detach operation is mandatory to use in the cell. The MS shall operate in accordance with the received value of the indicator. + +A GPRS MS shall perform GPRS attach/detach procedures independent of the value of the IMSI attach/detach indicator. When a GPRS MS has to perform IMSI attach/detach independent of GPRS procedures (for example GPRS network operation mode 2) the handling described in the clause above applies. + +When IMSI attach/detach operation applies, an MS shall send the IMSI detach message to the network when the MS is powered down or the SIM is removed while the update status is "UPDATED". The IMSI detach message will not be acknowledged by the network. + +When the MS returns to the active state, the MS shall perform an LR request indicating IMSI attach, provided that the MS still is in the same registration area. If the registration area has changed, an LR request indicating normal location updating according to clause 4.5.2 shall be performed. + +### 4.5.5 No Suitable Cells In Location Area + +If during location registration the LR response "No Suitable Cells In Location Area" or "No Suitable Cells In Tracking Area" is received: + +- The MS shall attempt to find another LA or TA of the same PLMN, the same SNPN, an equivalent PLMN or an equivalent SNPN, on which it received the LR response. If the MS is able to find another LA or TA it shall attempt registration. If the MS is unable to find an LA or TA, the PLMN Automatic or Manual Mode Selection Procedure of clause 4.4.3.1 or the SNPN Automatic or Manual Mode Selection Procedure of clause 4.9.3.1 shall be followed, depending on whether the MS is in automatic or manual mode and whether the MS operates in SNPN access operation mode over 3GPP access. + +## 4.6 Service indication (A/Gb mode only) + +This is an indication to the user that service or CTS service is available. + +The service indication should be set if the following conditions are all satisfied: + +- a) Cell Selection: Camped on a suitable cell and in updated state, or in connected mode having been camped on a suitable cell. +- b) Location registration: In updated state, for MSs capable of services requiring registration. + +A specific CTS service indication should be set when the CTS MS is attached to a CTS FP. + +However due to the fact that there may be some transitory changes of state, the service indication is permitted to continue to be set for up to 10 seconds after the above conditions cease to be met. Also the service indication is permitted to take up to 1 second to be set after the above conditions are met. + +## 4.7 Pageability of the mobile subscriber + +An MS is required to listen to all paging messages that could address it (see 3GPP TS 45.002 [24]), when the following conditions are all satisfied: + +- A SIM is inserted; +- The MS is camped on a cell; +- The MS is not in state "Idle, No IMSI"; and +- The MS is not performing the task to search for available PLMNs or available SNPNs. (Whenever possible during this task, the MS should listen for paging.). However, when the MS is camped on a cell, is registered in a PLMN and is performing its regular search for a higher priority PLMN, as specified in 3GPP TS 22.011 [9], then it shall listen to all paging messages that could address it. + +NOTE: In A/Gb mode, during cell reselection there is a certain period when the MS is no longer camped on the old cell but must decode the full BCCH, CPBCCH or EC-BCCH before camping on the new cell. This leads to a period of slightly more than 8 51 frame multiframes when the MS will not necessarily be pageable (full BCCH or CPBCCH is decoded) or up to 32 51 frame multiframes when the MS will not necessarily be pageable (full EC-BCCH is decoded). + +## 4.8 MM Restart Procedure + +In some cases, e.g. on change of SIM data, there is a need for the MM to be restarted without the need for user intervention. + +To perform the procedure the MS shall behave as if the SIM is removed and afterwards a new SIM is inserted. + +## 4.9 SNPN selection process + +### 4.9.1 General + +The MS operating in SNPN access operation mode over 3GPP access shall perform the SNPN selection process. + +The MS not operating in SNPN access operation mode over 3GPP access shall not perform the SNPN selection process. + +There are two SNPN selection modes - automatic SNPN selection mode and manual SNPN selection mode. + +In the SNPN selection process, the MS shall consider only the access networks of the NG-RAN access technology. + +### 4.9.2 Registration on an SNPN + +The MS shall perform registration on the SNPN if the MS is capable of services which require registration. In both automatic SNPN selection mode and manual SNPN selection mode, the concept of registration on an SNPN is used. An MS successfully registers on an SNPN if: + +- a) the MS has found a suitable cell of the SNPN to camp on; and +- b) an LR request from the MS has been accepted in the registration area of the cell on which the MS is camped. + +### 4.9.3 SNPN selection + +#### 4.9.3.0 General + +The ME is configured with a "list of subscriber data" containing zero or more entries. Each entry of the "list of subscriber data" consists of: + +- a) a subscriber identifier in the form of a SUPI with the SUPI format "network specific identifier" containing a network-specific identifier or with the SUPI format "IMSI" containing an IMSI, except when the subscribed SNPN uses: + - 1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or + - 2) the 5G AKA based primary authentication and key agreement procedure; + +NOTE 1: A subscriber identifier in the form of a SUPI with the SUPI format "network specific identifier" containing a network-specific identifier or with the SUPI format "IMSI" containing an IMSI, is available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure. + +NOTE 2: If the MS supports access to an SNPN using credentials from a credentials holder and is configured with the SNPN selection parameters as described in h), the subscriber identifier in the form of a SUPI configured in the ME or the USIM needs to be: + +- with the SUPI format "network specific identifier"; or +- with the SUPI format "IMSI", if the subscribed SNPN has an assigned PLMN ID. + +b) credentials except when the subscribed SNPN uses: + +- 1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or +- 2) the 5G AKA based primary authentication and key agreement procedure. + +If the MS supports access to an SNPN using credentials from a credentials holder, the credentials can include an indication to use MSK for derivation of $K_{AUSF}$ after success of primary authentication and key agreement procedure; + +NOTE 3: Credentials are available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure. If the MS supports access to an SNPN using credentials from a credentials holder, credentials available in USIM can include an indication to use MSK for derivation of $K_{AUSF}$ after success of primary authentication and key agreement procedure. + +ba) optionally, a routing indicator, except when the subscribed SNPN uses: + +- 1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or +- 2) the 5G AKA based primary authentication and key agreement procedure; + +NOTE 3A: Routing indicator is available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure. + +bb) optionally, the protection scheme identifier as specified in 3GPP TS 33.501 [66], except when the subscribed SNPN uses: + +- 1) the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or +- 2) the 5G AKA based primary authentication and key agreement procedure; + +If the protection scheme identifier is configured in the entry of the "list of subscriber data" and not set to "null-scheme", the entry of the "list of subscriber data" also contains the home network public key and the home network public key identifier as specified in 3GPP TS 33.501 [66]; + +NOTE 3B: The protection scheme identifier, the home network public key and the home network public key identifier are available in USIM if the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure. + +c) an SNPN identity of the subscribed SNPN; + +d) optionally, the unified access control configuration indicating for which access identities (see 3GPP TS 24.501 [64]) the ME is configured, when the MS accesses an SNPN using the entry. + +Access identity 11 or 15, if configured, is applicable for the MS only in the subscribed SNPN. + +Access identity 12, 13 or 14, if configured, is applicable for the MS only: + +- 1) in the subscribed SNPN; and + +- 2) if the MCC of the SNPN identity of the subscribed SNPN is not the MCC of value 999, in the non-subscribed SNPNs of the same country as the subscribed SNPN; + +Access identity 1 or 2, if configured, is applicable for the MS only: + +- 1) in the subscribed SNPN; + - 2) if the MCC of the SNPN identity of the subscribed SNPN is not the MCC of value 999, in the non-subscribed SNPNs of the same country as the subscribed SNPN; and + - 3) in an SNPN equivalent to the subscribed SNPN; +- e) zero or more sets of pre-configured URSP rules (see 3GPP TS 24.526 [77]), each set for the subscribed SNPN or a non-subscribed SNPN; + - f) optionally, the default configured NSSAI (see 3GPP TS 24.501 [64]); + - g) optionally, if the MS supports access to an SNPN using credentials from a credentials holder: + - 1) the SNPN selection parameters, consisting of: + - i) a user controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity; + - ii) a credentials holder controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity; + - iii) a credentials holder controlled prioritized list of Group IDs for Network Selection (GINs); and + - iv) optionally, if the MS supports access to an SNPN providing access for localized services in SNPN, the SNPN selection parameters for access for localized services in SNPN, consisting of: + - A) a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", where each entry contains: + - an SNPN identity; + - validity information consisting of time validity information and optionally, location validity information; and + - optionally, location assistance information; and + - B) a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains: + - a GIN; + - validity information consisting of time validity information and optionally, location validity information; and + - optionally, location assistance information; and + - 2) optionally, an indication to expect to receive the steering of roaming information due to initial registration in a non-subscribed SNPN; + +NOTE 4: How the ME is configured with the "list of subscriber data" is out of scope of 3GPP in this release of the specification. + +NOTE 5: Multiple entries can include the same subscriber identifier and credentials. + +NOTE 6: Handling of more than one entry with the same SNPN identity is left up to MS implementation. + +NOTE 7: Handling of the case when the subscribed SNPN uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure and the MS has multiple valid USIMs (3GPP TS 31.102 [40]) is left up to MS implementation. + +NOTE 8: To enable UE mobility between SNPNs in 5GMM-IDLE mode, SNPN identities in the credentials holder controlled prioritized list of preferred SNPNs are assumed to be globally-unique SNPN identities. + +h) optionally: + +- 1) an indication of whether the MS shall ignore all warning messages received in the subscribed SNPN or an equivalent SNPN of the subscribed SNPN; and +- 2) an indication of whether the MS shall ignore all warning messages received in an non-subscribed SNPN or an equivalent SNPN of the non-subscribed SNPN. + +NOTE 9: The ME can be configured with an indication to use anonymous SUCI associated with an entry of "list of subscriber data" when the EAP method associated with the credentials of the entry supports SUPI privacy at the EAP layer. + +NOTE 10: Anonymous SUCI is not used if the subscribed SNPN of the entry uses the EAP based primary authentication and key agreement procedure using the EAP-AKA' or the 5G AKA based primary authentication and key agreement procedure. + +The MS which supports onboarding services in SNPN shall be pre-configured with default UE credentials for primary authentication and may be pre-configured with onboarding SNPN selection information. Contents of the onboarding SNPN selection information are MS implementation specific. Contents of default UE credentials for primary authentication are out of scope of 3GPP. + +Additionally, if the MS has a USIM with a PLMN subscription, the ME may be configured with the SNPN selection parameters associated with the PLMN subscription, consisting of: + +- a) a user controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity; +- b) a credentials holder controlled prioritized list of preferred SNPNs, where each entry contains an SNPN identity; +- c) a credentials holder controlled prioritized list of GINs; and +- d) optionally, if the MS supports access to an SNPN providing access for localized services in SNPN, with the following SNPN selection parameters for access for localized services in SNPN associated with the PLMN subscription, consisting of: + - 1) a "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", where each entry contains: + - an SNPN identity; + - validity information consisting of time validity information and optionally, location validity information; and + - optionally, location assistance information; and + - 2) a "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", where each entry contains: + - a GIN; + - validity information consisting of time validity information and optionally, location validity information; and + - optionally, location assistance information + +and with the following configuration parameters associated with the PLMN subscription: + +- a) zero or more sets of pre-configured URSP rules (see 3GPP TS 24.526 [77]), each set for the HPLMN or a non-subscribed SNPN; and +- b) optionally, an indication to expect to receive the steering of roaming information due to initial registration in a non-subscribed SNPN. + +NOTE 11: To enable MS mobility between SNPNs in 5GMM-IDLE mode, SNPN identities in the credentials holder controlled prioritized list of preferred SNPNs are assumed to be globally-unique SNPN identities. + +NOTE 12: If an MS accesses an SNPN using the PLMN subscription, access identity 1, 2, 12, 13, or 14 is configured in the USIM of the MS, and the SNPN is of the same country as the HPLMN, then the configured access identity 1, 2, 12, 13, or 14 is applicable for the MS. + +NOTE 13: If an MS accesses an SNPN using the PLMN subscription, an indication of whether the MS shall ignore all warning messages in an SNPN is configured in the USIM of the MS. + +NOTE 14: Handling of URSP rules is specified in 3GPP TS 24.526 [77]. + +The time validity information contains one or more time periods. + +The location validity information contains one or more location information. + +If: + +- a) the location validity information is not available and at least one time period of the time validity information matches UE's current time; or +- b) the location validity information is available, at least one time period of the time validity information matches UE's current time and at least one location information of the location validity information matches UE's current location; + +then the validity information is met otherwise the validity information is not met. + +The MS shall maintain a list of "temporarily forbidden SNPNs" and a list of "permanently forbidden SNPNs" in the ME. Each entry of those lists consists of an SNPN identity. If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the MS shall maintain one list of "temporarily forbidden SNPNs" and one list of "permanently forbidden SNPNs" per entry of the "list of subscriber data". If the MS supports access to an SNPN using credentials from a credentials holder, the MS shall maintain one list of "temporarily forbidden SNPNs" and one list of "permanently forbidden SNPNs" per the PLMN subscription. If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the MS shall use the lists associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. In addition, if the MS supports access to an SNPN providing access for localized services in SNPN, the MS shall maintain one list of "temporarily forbidden SNPNs for access for localized services in SNPN" and one list of "permanently forbidden SNPNs for access for localized services in SNPN" per entry of the "list of subscriber data" and per the PLMN subscription. If the MS supports access to an SNPN providing access for localized services in SNPN, the MS shall use the lists associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. In addition, if the MS supports onboarding services in SNPN, a "permanently forbidden SNPNs" list for onboarding services and a "temporarily forbidden SNPNs" list for onboarding services shall be maintained. + +The MS shall add an SNPN to the list of "temporarily forbidden SNPNs" (for access for localized services in SNPN, if the SNPN is an SNPN selected for localized services in SNPN) (for onboarding services, if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN) which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if a message with cause value #74 "Temporarily not authorized for this SNPN" (see 3GPP TS 24.501 [64]) is received by the MS in response to an LR request from the SNPN. In addition, if: + +- the message is integrity-protected; or +- the message is not integrity-protected, and the value of the SNPN-specific attempt counter for that SNPN is equal to the MS implementation specific maximum value as defined in 3GPP TS 24.501 [64]; + +then the MS shall start an MS implementation specific timer not shorter than 60 minutes. + +The MS shall remove an SNPN from the list of "temporarily forbidden SNPNs" (for access for localized services in SNPN, if the SNPN is an SNPN selected for localized services in SNPN) (for onboarding services, if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN) which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if: + +- a) there is a successful LR after a subsequent manual selection of the SNPN; +- b) the MS implementation specific timer not shorter than 60 minutes expires; + +- c) the MS is configured to use timer T3245 and timer T3245 expires; +- d) the MS is not configured to use timer T3245, the timer T3247 expires and the value of the SNPN-specific attempt counter for that SNPN is less than the MS implementation specific maximum value as defined in 3GPP TS 24.501 [64]; +- e) the MS is switched off; +- f) an entry of the "list of subscriber data" with the subscribed SNPN identity identifying the SNPN is updated or the USIM is removed if: + - EAP based primary authentication and key agreement procedure using EAP-AKA'; or + - 5G AKA based primary authentication and key agreement procedure;was performed in the selected SNPN; or +- g) the selected entry of the "list of subscriber data" is updated or USIM is removed for the selected PLMN subscription. + +If an SNPN is removed from the list of "temporarily forbidden SNPNs" list, the MS shall stop the MS implementation specific timer not shorter than 60 minutes, if running. + +NOTE 15: If the MS supports access to an SNPN providing access for localized services in SNPN, the UE ensures that such an SNPN is not inaccessible due to being in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" when the validity information of the SNPN changes from not met to met. As a UE implementation option, the MS can remove an SNPN from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, when the validity information of the SNPN changes from not met to met. + +The MS shall add an SNPN to the list of "permanently forbidden SNPNs" (for access for localized services in SNPN, if the SNPN is an SNPN selected for localized services in SNPN) (for onboarding services, if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN) which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if a message with cause value #75 "Permanently not authorized for this SNPN", #3 "Illegal UE" (applicable in an onboarding SNPN only), #6 "Illegal ME" (applicable in an onboarding SNPN only), or #7 "5GS services not allowed" (applicable in an onboarding SNPN only) (see 3GPP TS 24.501 [64]) is received by the MS in response to an LR request from the SNPN. + +The MS shall remove an SNPN from the list of "permanently forbidden SNPNs" (for access for localized services in SNPN, if the SNPN is an SNPN selected for localized services in SNPN) (for onboarding services, if the MS is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN) which is, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if: + +- a) there is a successful LR after a subsequent manual selection of the SNPN; +- b) the MS is configured to use timer T3245 and timer T3245 expires; +- c) the MS is not configured to use timer T3245, the timer T3247 expires and the value of the SNPN-specific attempt counter for that SNPN is less than the MS implementation specific maximum value as defined in 3GPP TS 24.501 [64]; +- d) an entry of the "list of subscriber data" with the subscribed SNPN identity identifying the SNPN is updated or the USIM is removed if: + - EAP based primary authentication and key agreement procedure using EAP-AKA'; or + - 5G AKA based primary authentication and key agreement procedure;was performed in the selected SNPN; or +- e) the selected entry of the "list of subscriber data" is updated or USIM is removed for the selected PLMN subscription. + +NOTE 16: If the MS supports access to an SNPN providing access for localized services in SNPN, the UE ensures that such an SNPN is not inaccessible due to being in the list of "permanently forbidden SNPNs for access for localized services in SNPN" when the validity information of the SNPN changes from not met to met. As a UE implementation option the MS can remove an SNPN from the list of "permanently forbidden SNPNs for access for localized services in SNPN" associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, when the validity information of the SNPN changes from not met to met. + +When the MS reselects to a cell in a shared network, and the cell is a suitable cell for multiple SNPN identities received in the broadcast information as specified in 3GPP TS 38.331 [65], the AS indicates these multiple SNPN identities to the NAS according to 3GPP TS 38.304 [61]. The MS shall select one of these SNPNs. If the registered SNPN is available among these SNPNs, the MS shall not select a different SNPN. + +The MS operating in SNPN access operation mode over 3GPP access shall maintain one or more lists of "5GS forbidden tracking areas for roaming", each associated with an SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, entry of the "list of subscriber data" or, if the MS supports access to an SNPN using credentials from a credentials holder, the PLMN subscription. The MS shall use the list of "5GS forbidden tracking areas for roaming" associated with the selected SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the MS selects a new SNPN, the MS shall keep the list of "5GS forbidden tracking areas for roaming" associated with the previously selected SNPN and, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the number of the lists to be kept is higher than supported, the MS shall delete the oldest stored list of "5GS forbidden tracking areas for roaming". The MS shall delete all lists of "5GS forbidden tracking areas for roaming", periodically (with period in the range 12 to 24 hours) or when the MS is switched off. The MS shall delete the list of "5GS forbidden tracking areas for roaming" associated with an SNPN: + +- a) when the entry with the subscribed SNPN identifying the SNPN in the "list of subscriber data" is updated; +- b) when the USIM is removed if: + - the EAP based primary authentication and key agreement procedure using the EAP-AKA'; or + - the 5G AKA based primary authentication and key agreement procedure;was performed in the selected SNPN; or +- c) if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, when the list of "5GS forbidden tracking areas for roaming" is associated with: + - the entry of the "list of subscriber data" and the entry of the "list of subscriber data" is updated; or + - the PLMN subscription and USIM is removed. + +NOTE 17: The number of the lists of "5GS forbidden tracking areas for roaming" supported by the MS is MS implementation specific. + +If a message with cause value #15 (see 3GPP TS 24.501 [64]) is received by an MS operating in SNPN access operation mode over 3GPP access, the TA is added to the list of "5GS forbidden tracking areas for roaming" of the selected SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription,. The MS shall then search for a suitable cell in the same SNPN but belonging to a TA which is not in the "5GS forbidden tracking areas for roaming" list of the selected SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription. + +The MS should maintain a list of SNPNs for which the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed". When the MS disables its N1 mode capability due to receipt of a reject from an SNPN with 5GMM cause #27 "N1 mode not allowed": + +- the MS should add the SNPN identity of the SNPN which sent a reject with 5GMM cause #27 "N1 mode not allowed" to the list of SNPNs for which the N1 mode capability was disabled and should start timer TJ if timer TJ is not already running. The number of SNPNs for which the N1 mode capability was disabled that the MS can store is implementation specific, but it shall be at least one. The value of timer TJ is MS implementation specific; + +- in automatic SNPN selection, the MS shall not select an SNPN for which the N1 mode capability was disabled as SNPN selection candidates, unless no other SNPN is available; +- if the MS is not configured to use timer T3245, the MS maintains a list of SNPN-specific attempt counters for 3GPP access as specified in 3GPP TS 24.501 [64], and T3247 expires, then the MS removes for each SNPN-specific attempt counter for 3GPP access that has a value greater than zero and less than the MS implementation-specific maximum value the respective SNPN from the list of SNPNs for which the N1 mode capability was disabled, as specified in clause 5.3.20.3 in 3GPP TS 24.501 [64]; and +- the MS shall delete stored information on SNPNs for which the N1 mode capability was disabled when the MS is switched off, the USIM is removed, the entries of the "list of subscriber data" for the SNPNs are updated, or timer TJ expires. + +NOTE 18: The expiry of timer TJ does not cause a reset of the SNPN-specific attempt counters for 3GPP access (see 3GPP TS 24.501 [64]). + +If the MS does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the MS should maintain a list of SNPNs where the N1 mode capability was disabled because IMS voice was not available and the MS's usage setting was "voice centric". If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both the MS should maintain one or more lists of SNPNs where the N1 mode capability was disabled because IMS voice was not available and the MS's usage setting was "voice centric", each associated with an entry of the "list of subscriber data" or with the PLMN subscription. If the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the MS shall use the lists associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription. When the MS disables its N1 mode capability due to IMS voice not available and the MS's usage setting was "voice centric": + +- the MS should add the SNPN identity of the SNPN to the list of SNPNs where voice service was not possible in N1 mode and should start timer TK if timer TK is not already running. The number of SNPNs that the MS can store where voice services is not possible is implementation specific, but it shall be at least one. The value of timer TK is MS implementation specific; +- in automatic SNPN selection the MS shall not consider SNPNs where voice service was not possible in N1 mode as SNPN selection candidates, unless no other SNPN is available; and +- the MS shall delete stored information on SNPNs where voice service was not possible in N1 mode when the MS is switched off, the USIM is removed, the entries of the "list of subscriber data" for the SNPNs are updated, or timer TK expires. + +The MS may support equivalent SNPNs. If the MS supports equivalent SNPNs, the ME shall store up to one list of equivalent SNPNs: + +- per entry of "list of subscriber data"; or +- per the PLMN subscription, if the MS supports access to an SNPN using credentials from a credentials holder. + +SNPNs in the list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription shall be regarded by the MS as equivalent to each other for SNPN selection, cell selection, and cell re-selection. The list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription is created, replaced or deleted at the end of each registration procedure. The stored list consists of a list of equivalent SNPNs as provided by the network plus the SNPN identity of the registered SNPN that provided the list. When the MS is switched off, the MS shall keep the stored list(s) so that they can be used for SNPN selection after switch on. The MS shall delete the stored list associated with an entry of "list of subscriber data" or the PLMN subscription, when the USIM is removed, the associated entry of "list of subscriber data" is updated, or the MS registered for emergency services deregisters. + +NOTE 19: The MS can provide the list of equivalent SNPNs associated with the selected entry of "list of subscriber data" or the selected PLMN subscription to the lower layers. + +NOTE 20: The list of equivalent SNPNs is not provided by the network when the MS is registering or is registered for onboarding services in SNPN. + +#### 4.9.3.1 At switch-on or recovery from lack of coverage + +##### 4.9.3.1.0 General + +At switch on, following recovery from lack of coverage, or when the MS starts operating in the SNPN access operation mode over 3GPP access, the MS selects the registered SNPN or an equivalent SNPN (if it is available) using NG-RAN access technology and if necessary (in the case of recovery from lack of coverage, see clause 4.5.2) attempts to perform an LR. + +NOTE 1: The MS in automatic SNPN selection mode can end the SNPN search procedure once the registered SNPN or an equivalent SNPN is found on NG-RAN access technology. + +NOTE 2: An MS in automatic SNPN selection mode can use location information to determine which SNPNs can be available in its present location. + +If successful registration is achieved, the MS indicates the selected SNPN. + +If there is no registered SNPN, or registration is not possible due to the SNPN and all equivalent SNPNs, if any, being unavailable or registration failure, unless the MS needs to select an SNPN for onboarding services in SNPN, the MS follows the procedure in clause 4.9.3.1.1 or clause 4.9.3.1.2 depending on its SNPN selection mode. If the MS needs to select an SNPN for onboarding services in SNPN, the MS follows the procedure in clause 4.9.3.1.3 or clause 4.9.3.1.4 depending on its SNPN selection mode for onboarding services in SNPN. At switch on, the MS shall use the SNPN selection mode and the SNPN selection mode for onboarding services in SNPN that were used before switching off. + +NOTE 3: If successful registration is achieved, then the current serving SNPN becomes the registered SNPN and the MS does not store the previous registered SNPN for later use. + +If registration is not possible on recovery from lack of coverage due to the registered SNPN and all equivalent SNPNs, if any, being unavailable, an MS may, optionally, continue looking for the registered SNPN or an equivalent SNPN for an implementation dependent time. + +NOTE 4: An MS registered to an SNPN should behave as described above only if one or more PDU sessions are currently active. + +EXCEPTION: As an alternative option to this, if the MS is in automatic SNPN selection mode and it finds coverage of a subscribed SNPN (for the selected entry of "list of subscriber data"), the MS may register to that SNPN and not return to the registered SNPN or equivalent SNPN. + +##### 4.9.3.1.1 Automatic SNPN selection mode procedure + +If: + +- there is at least one entry in the "list of subscriber data"; or +- there is zero or more entries in the "list of subscriber data", the MS has a USIM with a PLMN subscription and the ME is provisioned with the SNPN selection parameters associated with the PLMN subscription, + +the MS shall select one entry in the "list of subscriber data", if any, or the PLMN subscription, if any, to be used for automatic SNPN selection. How the MS selects the entry in the "list of subscriber data" or the PLMN subscription is MS implementation specific. + +The MS selects an SNPN, if available and allowable, in the following order: + +- a0) if the MS supports access to an SNPN providing access for localized services in SNPN and access for localized services in SNPN is enabled, then, using the SNPN selection parameters for access for localized services in SNPN in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription: + - 1) the SNPN previously selected as result of an entry of a list of bullet a0) 2) or a0) 3) with which the UE was last registered, if validity information of the entry is still met, or the equivalent SNPN if it is available and validity information of the entry of the SNPN previously selected as result of an entry of a list of bullet a0) 2) or a0) 3) with which the UE was last registered is still met; + - 2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in an entry of the "credentials holder + +controlled prioritized list of preferred SNPNs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met; and + +- 3) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which broadcast a GIN contained in an entry of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met. If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific; +- a) the SNPN with which the UE was last registered or an equivalent SNPN, except if the registered SNPN was previously selected as result of an entry of a list of bullet a0) 2) or a0) 3) and validity information of the entry is no longer met or access for localized services in SNPN is no longer enabled; + - b) the SNPN identified by an SNPN identity of the subscribed SNPN in the selected entry of the "list of subscriber data" in the ME, if any; + - c) if the MS supports access to an SNPN using credentials from a credentials holder, using the SNPN selection parameters in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription: + - 1) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the user controlled prioritized list of preferred SNPNs (in priority order); + - 2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the credentials holder controlled prioritized list of preferred SNPNs (in priority order); + - 3) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which broadcast a GIN contained in the credentials holder controlled prioritized list of GINs (in priority order). If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific; and + - 4) each SNPN identified by an SNPN identity which is included neither in the SNPN selection parameters of the entries of the "list of subscriber data" nor in the SNPN selection parameters associated with the PLMN subscription, which does not broadcast a GIN which is included in the credentials holder controlled prioritized list of GINs, and which broadcasts an indication that the SNPN allows registration attempts from MSs that are not explicitly configured to select the SNPN. If more than one such SNPN is available, the order in which the MS attempts registration on those SNPNs is MS implementation specific. + +The MS shall limit its search for the SNPN to the NG-RAN access technology. + +Once the MS selects the SNPN, the MS attempts registrations on the selected SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from the selected entry of the "list of subscriber data" or from the USIM, if the PLMN subscription is selected. + +If successful registration is achieved, the MS indicates the selected SNPN. + +If: + +- a) in bullet a0), the MS is unable to select an SNPN for access for localized services in SNPN and the validity information of + - an entry of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN"; or + - an entry of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN",of the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription is still met; +- b) the MS is not registered for emergency services; and +- c) the MS does not have an established emergency PDU session, + +the MS shall re-attempt to perform the SNPN selection to select an SNPN providing access for localized services in SNPN in accordance with the requirements that are applicable to bullets a0). This re-attempt and subsequent re-attempts if still required is determined by the MS in an implementation specific way, and should be triggered if the validity information is still met. + +If registration cannot be achieved because no SNPNs are available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, the MS indicates "no service" to the user, waits until a new SNPN is available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME and then repeats the procedure. + +If there were one or more SNPNs which were available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME but an LR failure made registration on those SNPNs unsuccessful, the MS selects one of those SNPNs again and enters a limited service state. + +If an SNPN is being removed from the "temporarily forbidden SNPNs" or the "permanently forbidden SNPNs" list (e.g due to MS implementation specific timer not shorter than 60 minutes expires or timer T3245 expires), and the MS is in limited service state, and the MS does not have a PDU session for emergency services, the MS shall perform SNPN selection as described in subclause 4.9.3.1. If the MS has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection subsequently after the emergency PDU session is released. + +If: + +- a) the MS supports access to an SNPN providing access for localized services in SNPN; +- b) the access for localized services in SNPN has been enabled; +- c) the MS is in limited service state; +- d) the MS does not have a PDU session for emergency services; and +- e) an SNPN is being removed from the list of "permanently forbidden SNPNs for access for localized services in SNPN" or "temporarily forbidden SNPNs for access for localized services in SNPN" (e.g due to MS implementation specific timer not shorter than 60 minutes expires, timer T3245 expires or validity information of the SNPN becomes valid); + +the MS shall perform SNPN selection as described in subclause 4.9.3.1. If the MS has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection subsequently after the emergency PDU session is released. + +##### 4.9.3.1.2 Manual SNPN selection mode procedure + +The MS indicates to the user any available SNPNs which meet the criteria specified in bullets a) and b). If the MS does not support access to an SNPN using credentials from a credentials holder, this includes SNPNs in the list of "permanently forbidden SNPNs", and the list of "temporarily forbidden SNPNs". The MS may indicate to the user whether the available SNPNs are present in the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs". If the MS supports access to an SNPN using credentials from a credentials holder, this includes SNPNs in the lists of "permanently forbidden SNPNs", and the lists of "temporarily forbidden SNPNs" associated with each entry of the "list of subscriber data" or the PLMN subscription. If the MS supports equivalent SNPNs, this includes SNPNs in the lists of "permanently forbidden SNPNs", and the lists of "temporarily forbidden SNPNs" associated with each entry of the "list of subscriber data". The MS may indicate to the user whether the available SNPNs are present in a list of "temporarily forbidden SNPNs" or a list of "permanently forbidden SNPNs" for an entry of the "list of subscriber data" or the PLMN subscription. If the MS supports access to an SNPN providing access for localized services in SNPN, this includes SNPNs in the lists of "permanently forbidden SNPNs for access for localized services in SNPN", and the lists of "temporarily forbidden SNPNs for access for localized services in SNPN" associated with each entry of the "list of subscriber data" or the PLMN subscription. If the MS supports access to an SNPN providing access for localized services in SNPN, the MS may indicate to the user whether an available SNPN is identified by an SNPN identity contained in an entry of one of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" and whether the validity information of the entry is met, whether an available SNPN is broadcasting a GIN contained in an entry of one of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" and whether the validity information of the entry is met and whether an available SNPNs are present in a list of "temporarily forbidden SNPNs for access for localized services in SNPN" or a list of "permanently forbidden SNPNs for access for localized services in SNPN" for an entry of the "list of subscriber data" or the PLMN subscription. + +- a) SNPNs with the following order: + - 1) identified by an SNPN identity contained in one of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" configured in the ME if the validity information of the entry is met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific; + - 2) broadcast a GIN contained in one of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" configured in the ME if the validity information of the entry is met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific. If more than one SNPN broadcast the same GIN, the order in which those SNPNs are indicated is MS implementation specific; + - 3) identified by an SNPN identity contained in one of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" configured in the ME if the validity information of the entry is not met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific; + - 4) broadcast a GIN contained in one of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" configured in the ME if the validity information of the entry is not met, the MS supports access to an SNPN providing access for localized services in SNPN. Prioritization between the different lists is MS implementation specific. If more than one SNPN broadcast the same GIN, the order in which those SNPNs are indicated is MS implementation specific; and + - 5) identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, if any. The order in which those SNPNs are indicated is MS implementation specific; +- b) if the MS supports access to an SNPN using credentials from a credentials holder, for the SNPNs which broadcast the indication that access using credentials from a credentials holder is supported: + - 1) each SNPN which is identified by an SNPN identity contained in one of the user controlled prioritized lists of preferred SNPNs configured in the ME. SNPNs included in the same list are indicated in the order in which they are included in the list. Prioritization between the different lists is MS implementation specific; + - 2) each SNPN which is identified by an SNPN identity contained in one of the credentials holder controlled prioritized lists of preferred SNPNs configured in the ME. SNPNs included in the same list are indicated in the order in which they are included in the list. Prioritization between the different lists is MS implementation specific; + - 3) each SNPN which broadcasts a GIN contained in one of the credentials holder controlled prioritized lists of GINs configured in the ME. SNPNs broadcasting a GIN included in the same list are indicated in the order in which the GIN is included in the list. Prioritization between the different lists is MS implementation specific. If more than one SNPN broadcast the same GIN, the order in which those SNPNs are indicated is MS implementation specific; and + - 4) each SNPN identified by an SNPN identity which is not indicated in any of bullets a), b) 1), b) 2) or b) 3). The order in which those SNPNs are indicated is MS implementation specific. + +For each of the SNPNs indicated to the user, the MS shall forward a human-readable network name along with the SNPN identity to the upper layers if the system information broadcasted for the SNPN includes the human-readable network name for the SNPN. + +The MS shall limit its search for the SNPN to the NG-RAN access technology. + +If the UE has a PDU session for emergency services manual SNPN selection shall not be performed. + +The user may select an SNPN. If the user selects an SNPN, the MS then initiates registration on this SNPN using the NG-RAN access technology and for such registration the MS shall ignore the contents of the "5GS forbidden tracking areas for roaming", "5GS forbidden tracking areas for regional provision of service", "temporarily forbidden SNPNs", "permanently forbidden SNPNs", "permanently forbidden SNPNs for access for localized services in SNPN" and "temporarily forbidden SNPNs for access for localized services in SNPN". For such registration, the subscriber identifier and the credentials from the selected entry of the "list of subscriber data" or from USIM, if the PLMN subscription is selected, are determined as follows: + +- for bullet a) 1) above: + +- i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is met; or + - ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" associated with the PLMN subscription includes the SNPN identity of the selected SNPN and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is met; +- for bullet a) 2) above: + - i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcast by the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcasted by the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is met; or + - ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" associated with the PLMN subscription includes the GIN broadcast by the selected SNPN and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is met; + - for bullet a) 3) above: + - i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is not met; or + - ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" associated with the PLMN subscription includes the SNPN identity of the selected SNPN and validity information of the selected SNPN in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" that includes the SNPN identity of the selected SNPN is not met; + - for bullet a) 4) above: + - i) the entry of the "list of subscriber data" which contains the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcast by the selected SNPN shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN broadcasted by the selected SNPN is included in the entry of the "list of subscriber data" and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is not met; or + - ii) the PLMN subscription shall be considered as selected, if the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" associated with the PLMN subscription includes the GIN broadcast by the selected SNPN and validity information of the GIN in the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" that includes the GIN is not met; + - for bullet a) 5) above, the entry of the "list of subscriber data", with the SNPN identity matching the selected SNPN (this may take place at any time during the presentation of SNPNs), shall be considered as selected; + +- for bullet b-1) above: + - i) the entry of the "list of subscriber data" which contains the user controlled prioritized lists of preferred SNPNs that includes the SNPN identity of the selected SNPN shall be considered as selected, if the user controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data"; or + - the PLMN subscription shall be considered as selected, if the user controlled prioritized list of preferred SNPNs associated with the PLMN subscription includes the SNPN identity of the selected SNPN; +- for bullet b-2) above: + - i) the entry of the "list of subscriber data" which contains the credentials holder controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN shall be considered as selected, if the credentials holder controlled prioritized list of preferred SNPNs that includes the SNPN identity of the selected SNPN is included in the entry of the "list of subscriber data"; or + - ii) the PLMN subscription shall be considered as selected, if the credentials holder controlled prioritized list of preferred SNPNs associated with the PLMN subscription includes the SNPN identity of the selected SNPN; +- for bullet b-3) above: + - i) the entry of the "list of subscriber data" which contains the credentials holder controlled prioritized list of GINs that includes the GIN broadcast by the selected SNPN shall be considered as selected, if the credentials holder controlled prioritized list of GINs that includes the GIN broadcast by the selected SNPN is included in the entry of the "list of subscriber data"; or + - ii) the PLMN subscription shall be considered as selected, if the credentials holder controlled prioritized list of GINs associated with the PLMN subscription includes the GIN broadcast by the selected SNPN; and +- for bullet b-4) above, the entry of the "list of subscriber data" or the PLMN subscription shall be selected by MS implementation specific means. + +NOTE1: If the SNPN identity of the selected SNPN is included in more than one of the following: one or more user controlled prioritized list(s) of preferred SNPNs configured in the ME, one or more credentials holder controlled prioritized list(s) of preferred SNPNs configured in the ME or the list of SNPNs which are broadcasting a GIN included in one or more credentials holder controlled prioritized list(s) of GINs configured in the ME, which subscription is selected is MS implementation specific. + +Once the MS has registered on an SNPN selected by the user, the MS shall not automatically register on a different SNPN unless: + +- a) the user selects automatic SNPN selection mode; +- b) the user initiates an emergency call while the MS is in limited service state and either the SNPN does not broadcast the indication of support of emergency calls in limited service state or the registration request for emergency services is rejected by the network; or +- c) the new SNPN is declared as an equivalent SNPN by the registered SNPN. + +NOTE 2: If case b) occurs, the MS can provide an indication to the upper layers that the MS has exited manual network SNPN selection mode. + +If the user does not select an SNPN, the selected SNPN shall be the one that was selected either automatically or manually before the SNPN selection procedure started. If no such SNPN was selected or that SNPN is no longer available, then the MS shall attempt to camp on any acceptable cell and enter the limited service state. + +##### 4.9.3.1.3 Automatic SNPN selection mode procedure for onboarding services in SNPN + +When the MS needs to access an SNPN for onboarding services in SNPN, the MS shall select an SNPN indicating that onboarding is allowed and, if the onboarding SNPN selection information is pre-configured, also matching the onboarding SNPN selection information. If more than one such SNPNs are available, how the MS selects one of those SNPNs is MS implementation specific. The MS shall not select an SNPN not indicating that onboarding is allowed or not matching the onboarding SNPN selection information, if pre-configured, for onboarding services in SNPN. + +The MS shall limit its search for the SNPN to the NG-RAN access technology. + +Once the MS selects the SNPN, the MS shall attempt initial registration for onboarding services in SNPN on the selected SNPN using the NG-RAN access technology and the default UE credentials for primary authentication. + +If successful registration is achieved, the MS may indicate to upper layers the selected SNPN. How this indication is displayed by upper layers is implementation specific. + +If successful registration is not achieved and one or more other SNPNs indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, are available, the MS can select such other SNPN and attempt initial registration for onboarding services in SNPN on the selected SNPN using the NG-RAN access technology and the default UE credentials for primary authentication, or the MS can perform SNPN selection not for onboarding services in SNPN as specified in clause 4.9.3.1.1 or clause 4.9.3.1.2 depending on its SNPN selection mode. + +If: + +- registration cannot be achieved because no SNPNs indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, are available; or +- there were one or more SNPNs indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, but an LR failure made registration on all those SNPNs unsuccessful; + +the MS can indicate no onboarding services to upper layers, enter limited service state and wait until a new SNPN indicating that onboarding is allowed and matching the onboarding SNPN selection information, if pre-configured, is available and then repeat the procedure, or the MS can perform SNPN selection not for onboarding services in SNPN as specified in clause 4.9.3.1.1 or clause 4.9.3.1.2 depending on its SNPN selection mode. + +##### 4.9.3.1.4 Manual SNPN selection mode procedure for onboarding services in SNPN + +The MS shall indicate to upper layers one or more SNPNs, which are available and indicate that onboarding is allowed. + +These include SNPNs in the list of "permanently forbidden SNPNs" for onboarding services and the list of "temporarily forbidden SNPNs" for onboarding services. The MS may indicate to the user whether the available SNPNs are present in the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs". + +The MS shall limit its search for the SNPN to the NG-RAN access technology. + +For each SNPN indicated to upper layers, the MS shall indicate to the upper layers along with the SNPN identity: + +- a) whether the SNPN matches the onboarding SNPN selection information, if pre-configured; and +- b) the human-readable network name, if the system information broadcast includes the human-readable network name for the SNPN. + +Once the user selects the SNPN for onboarding services, the MS shall attempt initial registration for onboarding services in SNPN on the selected SNPN using the default UE credentials for primary authentication. For such a registration the MS shall ignore the contents of the "5GS forbidden tracking areas for roaming", "5GS forbidden tracking areas for regional provision of service", "temporarily forbidden SNPNs" for onboarding services and "permanently forbidden SNPNs" for onboarding services. + +##### 4.9.3.1.5 Void + +#### 4.9.3.2 User reselection + +##### 4.9.3.2.0 General + +At any time the user may request the MS to initiate reselection and registration onto an available SNPN, according to the following procedures, dependent upon the SNPN selection mode of the UE. + +##### 4.9.3.2.1 Automatic SNPN selection mode + +If: + +- there is at least one entry in the "list of subscriber data"; or +- there is zero or more entries in the "list of subscriber data", the MS has a USIM with a PLMN subscription and the ME is provisioned with the SNPN selection parameters associated with the PLMN subscription, + +the MS shall select one entry in the "list of subscriber data", or the PLMN subscription, if any, to be used for automatic SNPN selection. How the MS selects the entry in the "list of subscriber data" or the PLMN subscription is MS implementation specific. + +The MS selects an SNPNs, if available and allowable, in accordance with the following order: + +- a) if the MS supports access to an SNPN providing access for localized services in SNPN and access for localized services in SNPN is enabled, then, using the SNPN selection parameters for access for localized services in SNPN in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription: + - 1) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and is identified by an SNPN identity contained in an entry of the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met, excluding the previously selected SNPN; and + - 2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and broadcasts a GIN contained in an entry of the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" (in priority order), if the validity information of the entry is met, excluding the previously selected SNPN. If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific; +- a) the SNPN identified by an SNPN identity of the subscribed SNPN in the selected entry of the "list of subscriber data" in the ME, if any, excluding the previously selected SNPN; +- b) if the MS supports access to an SNPN using credentials from a credentials holder, using the SNPN selection parameters in the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription: + - 1) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the user controlled prioritized list of preferred SNPNs (in priority order), excluding the previously selected SNPN; + - 2) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which is identified by an SNPN identity contained in the credentials holder controlled prioritized list of preferred SNPNs (in priority order), excluding the previously selected SNPN; + - 3) each SNPN which broadcasts the indication that access using credentials from a credentials holder is supported and which broadcast a GIN contained in the credentials holder controlled prioritized list of GINs (in priority order), excluding the previously selected SNPN. If more than one such SNPN broadcast the same GIN, the order in which the MS attempts registration on those SNPNs is MS implementation specific; and + - 4) each SNPN identified by an SNPN identity which is included neither in the SNPN selection parameters of the entries of the "list of subscriber data" nor in the SNPN selection parameters associated with the PLMN subscription and which broadcasts an indication that the SNPN allows registration attempts from MSs that are not explicitly configured to select the SNPN, excluding the previously selected SNPN. If more than one such SNPN is available, the order in which the MS attempts registration on those SNPNs is MS implementation specific. +- c) the previously selected SNPN. + +The MS shall limit its search for the SNPN to the NG-RAN access technology. + +The previously selected SNPN is the SNPN which the MS has selected prior to the start of the user reselection procedure. + +The equivalent SNPNs list shall not be applied to the user reselection in automatic SNPN selection mode. + +Once the MS selects an SNPN, if the selected SNPN is other than the previously selected SNPN, the MS attempts registrations on the selected SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from the selected entry of the "list of subscriber data" or from the USIM, if the PLMN subscription is selected. + +NOTE: If the previously selected SNPN is selected, and registration has not been attempted on any other SNPNs, then the MS is already registered on the SNPN, and so registration is not necessary. + +##### 4.9.3.2.2 Manual SNPN selection mode procedure + +The manual SNPN selection mode procedure of clause 4.9.3.1.2 is followed. + +#### 4.9.3.3 Additional conditions for SNPN selection for MS supports access to an SNPN providing access for localized services in SNPN + +If the MS supports access to an SNPN providing access for localized services in SNPN, the UE is in automatic SNPN selection mode and: + +- a) access for localized services in SNPN is changed between disabled and enabled; or +- b) access for localized services in SNPN is enabled; and: + - 1) the selected SNPN is an SNPN selected for localized services in SNPN, and the validity information for the selected SNPN is no longer met; or + - 2) the selected SNPN is not an SNPN selected for localized services in SNPN, and the validity information for an entry in the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" changes from not met to met; + +then: + +- if the MS does not have an emergency PDU session and is not registered for emergency services, the MS may perform SNPN selection according to clause 4.9.3.1.1; or +- otherwise, if the validity information for the selected SNPN is no longer met the MS shall perform a local release of all PDU sessions except for the emergency PDU session. The MS may perform SNPN selection according to clause 4.9.3.1.1 after the emergency PDU session is released. + +### 4.9.4 Abnormal cases + +If: + +- a) the MS does not support access to an SNPN using credentials from a credentials holder and: + - 1) the "list of subscriber data" is empty; or + - 2) for each entry of the "list of subscriber data", such that an SNPN with the SNPN identity of the entry or an equivalent SNPN, is available: + - i) there has been an authentication failure for the subscriber identifier of the entry on the SNPN or an equivalent SNPN; or + - ii) the MS has received an "illegal ME" or "illegal UE" response to an LR request for the subscriber identifier of entry on the SNPN or an equivalent SNPN; or +- b) the MS supports access to an SNPN using credentials from a credentials holder and: + - 1) the "list of subscriber data" is empty and: + - i) the MS is not provisioned with SNPN selection parameters associated with the PLMN subscription; + - ii) the MS does not have a USIM; or + - iii) both of the above; + +- 2) for each entry of the "list of subscriber data", such that an SNPN with the SNPN identity of the subscribed SNPN of the entry or an equivalent SNPN, is available: + - i) there has been an authentication failure for the subscriber identifier of the entry on the SNPN or an equivalent SNPN; or + - ii) the MS has received an "illegal ME" or "illegal UE" response to an LR request for the subscriber identifier of entry on the SNPN or an equivalent SNPN;and: + - i) the MS is not provisioned with SNPN selection parameters associated with the PLMN subscription; + - ii) the MS does not have a USIM; or + - iii) both of the above; or +- 3) for each available SNPN which broadcasts an indication that access using credentials from a credentials holder is supported and: + - i) is identified by an SNPN identity contained in one of the user controlled prioritized lists of preferred SNPNs configured in the ME; + - ii) is identified by an SNPN identity contained in one of: + - the credentials holder controlled prioritized lists of preferred SNPNs configured in the ME; or + - the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" configured in the ME supporting access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN is enabled and the validity information of the SNPN is met; + - iii) broadcasts a GIN contained in one of: + - the credentials holder controlled prioritized lists of GINs configured in the ME; or + - the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" configured in the ME supporting access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN is enabled and the validity information of the SNPN is met; + - iv) is identified by an SNPN identity which is included neither in the SNPN selection parameters of the entries of the "list of subscriber data" nor in the SNPN selection parameters associated with the PLMN subscription, which does not broadcast a GIN which is included in one of the credentials holder controlled prioritized lists of GINs configured in the ME and which broadcasts an indication that the SNPN allows registration attempts from MSs that are not explicitly configured to select the SNPN; + +the following applies: + +- i) there has been an authentication failure in the SNPN; or +- ii) the MS has received an "illegal ME" or "illegal UE" response to an LR request from the SNPN; + +then effectively there is no selected SNPN ("No SIM" state). + +In these cases, the states of the cell selection process are such that the "list of subscriber data" (if any) or the PLMN subscription (if any) is not used. An MS in "No SIM" state configured with default UE credentials for primary authentication may perform SNPN selection procedure for onboarding services in SNPN. Except when an MS in "No SIM" state performs an initial registration for emergency services to an SNPN or an MS in "No SIM" state configured with default UE credentials for primary authentication performs registration for onboarding services in SNPN, no further attempts at registration on any SNPN are made until the MS is switched off and on again, or an entry of the "list of subscriber data" with the SNPN identity of the SNPN is updated or the USIM is inserted. When performing an initial registration for emergency services, an SNPN supporting emergency services, of the current serving cell is temporarily considered as the selected SNPN. If the MS needs to make an emergency call, the MS supports accessing a PLMN and there is no available SNPN supporting emergency services, the MS shall stop operating in SNPN access operation mode over 3GPP access and attempt to camp on a cell of a PLMN so that emergency calls can be made. After an emergency call is released, the MS may re-start operating in SNPN access operation mode over 3GPP access and perform SNPN selection. + +When in automatic SNPN selection mode and the MS is in the "not updated" state with one or more suitable cells to camp on; then after the maximum allowed unsuccessful LR requests (controlled by the specific attempt counters) the MS may continue (or start if it is not running) the user reselection procedure in clause 4.9.3.2.1. + +# 5 Tables and Figures + +**Table 1: Effect of LR Outcomes on PLMN Registration** + +| Location Registration Task State | Registration Status | Registered PLMN is | +|-----------------------------------------------------------------------------|---------------------|----------------------------------------------------| +| Updated | Successful | Indicated in the stored registration area identity | +| Idle, No IMSI | Unsuccessful | No registered PLMN (3) (4) | +| Roaming not allowed:
a) PLMN not allowed | Unsuccessful | No registered PLMN (4) | +| b) LA not allowed or TA not allowed | Indeterminate(1) | No registered PLMN | +| c) Roaming not allowed in this LA or Roaming not allowed in this TA | Indeterminate (2) | No registered PLMN (4) | +| d) No suitable cells in location area or No suitable cells in tracking area | Indeterminate (5) | No registered PLMN | +| e) Not authorized for this CSG | Indeterminate (6) | No registered PLMN | +| Not updated | Unsuccessful | No registered PLMN (4) | + +1) The MS will perform a cell selection and will eventually either enter a different state when the registration status will be determined, or fail to be able to camp on a new cell, when registration status will be unsuccessful. + +2) The MS will select the HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present) if in automatic mode and will enter Automatic Network Selection Mode Procedure of clause 4.4.3.1.1. If in manual mode, the MS will display the list of available PLMNs and follow the Manual Network Selection Mode Procedure of clause 4.4.3.1.2 If the appropriate process does not result in registration, the MS will eventually enter the limited service state. + +3) An MS may have different update states for GPRS and non-GPRS. A PLMN is registered when at least one of both update states is updated. + +4) The stored list of equivalent PLMNs is invalid and can be deleted. + +5) The MS will attempt registration on another LA or TA of the same PLMN, or equivalent PLMN if available. Otherwise it will enter either the Automatic Network Selection Mode procedure of clause 4.4.3.1.1 or follow the Manual Network Selection Mode procedure of clause 4.4.3.1.2. If the appropriate process does not result in registration, the MS will eventually enter the limited service state. + +6) The MS will attempt registration on another cell of the same PLMN, or equivalent PLMN if available. Otherwise it will enter either the Automatic Network Selection Mode procedure of clause 4.4.3.1.1 or follow the Manual Network Selection Mode procedure of clause 4.4.3.1.2. If the appropriate process does not result in registration, the MS will eventually enter the limited service state. + +NOTE 1: MSs capable of GPRS and non-GPRS services may have different registration status for GPRS and for non-GPRS. + +NOTE 2: The registered PLMN is determined by looking at the stored registration area identity and stored location registration status. + +Table 2: LR Process States and Allowed Actions + +| Location Registration
Task State | New LR request when | | | | Normal Calls | Paging
responded
to | +|-----------------------------------------------------------------------------|---------------------|----------------------------------|------------------|---------|---------------|---------------------------| +| | Changing
Cell | Changing
registration
area | Changing
PLMN | Other | Supported (1) | | +| Null (4) | No | Yes | Yes | No | No | No | +| Updated, (5) | No | Yes | Yes | (2) | Yes | Yes | +| Idle, No IMSI (7) | No | No | No | No | No | No | +| Roaming not allowed:
a) Idle, PLMN not allowed | No | No | Yes | No | No | Optional if with IMSI | +| b) Idle, LA not allowed or TA not allowed | No | Yes(6) | Yes | No | No | Optional if with IMSI | +| c) Idle, Roaming not allowed in this LA or Roaming not allowed in this TA | No | Yes(6,8) | Yes | No | No | Optional if with IMSI | +| d) No suitable cells in location area or No suitable cells in tracking area | No | Yes(6,8) | Yes | No | No | Optional if with IMSI | +| e) Not authorized for this CSG | No | Yes (6,8) | Yes | No | No | Optional if with IMSI | +| Not updated | Yes | Yes | Yes | (2)&(3) | (3) | Yes if with IMSI | + +1): Emergency calls may always be made, subject to access control permitting it. +2): A new LR is made when the periodic registration timer expires. +3): If a normal call request is made, an LR request is made. If successful the updated state is entered and the call may be made. +4): The MS is in the null state from switch on until it has camped on a cell and either made an LR attempt or decided that no LR attempt is needed. +5): In this state, IMSI detach is performed if the MS is deactivated and the BCCH indicates that IMSI attach/detach shall be used. An LR request indicating IMSI attach is performed if the MS is activated in the same registration area in which it was deactivated while being in this state. +6): An MS shall not perform a new LR when the new routing area is part of an LA or TA contained in any of the lists "forbidden location areas for roaming", "forbidden tracking areas for roaming", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS forbidden tracking areas for regional provision of service" or the new cell is a CSG cell which is not part of any of the lists "Allowed CSG list", "Operator CSG list". The MS shall not perform a LR on a satellite NG-RAN cell or a satellite E-UTRAN cell if it fulfils the conditions related to the list of "PLMNs not allowed to operate at the present UE location" as defined in clause 3.1, i.e. if it is not considered as candidate for PLMN selection. +7): The conditions in which the GPRS and/or non-GPRS registration status "Idle, No IMSI" is entered are specified in clause 4.3.3. +8): An MS shall perform a LR if it has entered a registration area whatever the registration area stored in the MS. + +![Figure 1: Overall Idle Mode process flowchart. The process starts with 'Service Indication' (14) leading to 'Cell selection' (7). 'Cell selection' (7) leads to 'Location registration' (10a) via 'Cell & registration area changes' (10). 'Location registration' (10a) leads to 'LR responses' (11), which then leads to 'PLMN's available' (12). 'PLMN's available' (12) leads to 'PLMN selection' (13). 'PLMN selection' (13) leads to 'PLMN Indication to the user' (2). 'PLMN selection' (13) also leads to 'Automatic/ Manual mode selection' (1). 'Automatic/ Manual mode selection' (1) leads to 'User selection of (PLMN, CSG)' (6). 'User selection of (PLMN, CSG)' (6) leads to '(PLMN, CSG) selection / restriction*' (dashed box). '(PLMN, CSG) selection / restriction*' (dashed box) leads to 'CSG in RPLMN ?*' (dashed decision box). 'CSG in RPLMN ?*' (dashed decision box) leads to 'Yes' (7) and 'No' (8). 'Yes' (7) leads to 'CSG selected (in RPLMN)' (9). 'No' (8) leads to '(PLMN, CSG) selected' (8). '(PLMN, CSG) selected' (8) leads to 'PLMN selected (optional CSG)' (9). 'PLMN selected (optional CSG)' (9) leads to 'Cell selection' (7). 'Cell selection' (7) also leads to '(PLMN, CSG)'s available' (4), which leads to '(PLMN, CSG) Indication to the user' (5). 'CM requests' (10a) also lead to 'Location registration' (10a).](c07e21a8d65991db04263322f859c94f_img.jpg) + +Figure 1: Overall Idle Mode process flowchart. The process starts with 'Service Indication' (14) leading to 'Cell selection' (7). 'Cell selection' (7) leads to 'Location registration' (10a) via 'Cell & registration area changes' (10). 'Location registration' (10a) leads to 'LR responses' (11), which then leads to 'PLMN's available' (12). 'PLMN's available' (12) leads to 'PLMN selection' (13). 'PLMN selection' (13) leads to 'PLMN Indication to the user' (2). 'PLMN selection' (13) also leads to 'Automatic/ Manual mode selection' (1). 'Automatic/ Manual mode selection' (1) leads to 'User selection of (PLMN, CSG)' (6). 'User selection of (PLMN, CSG)' (6) leads to '(PLMN, CSG) selection / restriction\*' (dashed box). '(PLMN, CSG) selection / restriction\*' (dashed box) leads to 'CSG in RPLMN ?\*' (dashed decision box). 'CSG in RPLMN ?\*' (dashed decision box) leads to 'Yes' (7) and 'No' (8). 'Yes' (7) leads to 'CSG selected (in RPLMN)' (9). 'No' (8) leads to '(PLMN, CSG) selected' (8). '(PLMN, CSG) selected' (8) leads to 'PLMN selected (optional CSG)' (9). 'PLMN selected (optional CSG)' (9) leads to 'Cell selection' (7). 'Cell selection' (7) also leads to '(PLMN, CSG)'s available' (4), which leads to '(PLMN, CSG) Indication to the user' (5). 'CM requests' (10a) also lead to 'Location registration' (10a). + +\*) dashed parts apply only for MEs supporting CSGs and are executed for manual CSG selection + +**Figure 1: Overall Idle Mode process** + +The individual steps are the following (they are not necessarily executed in the number sequence): + +- (1) The PLMN selection mode is set (e.g. by the user via the user interface or by AT command). +- (2) The list of available PLMNs is presented to the user, according to the rules given in clause 4.4.3.1.2. +- (3) In manual PLMN selection mode the user selects from the available PLMNs. +- (4) If the MS supports CSGs, the list of available PLMNs and CSGs, together with an indication as to which of the available CSGs is in the Allowed or Operator CSG list, is presented to the user upon request. The detailed rules are defined in clause 5.5.4 of 3GPP TS 22.220 [49]. +- (5) Only for MSs supporting CSGs: when camping on a cell, the available CSGs (with PLMN information) are conveyed to the CSG selection/restriction procedure (see clause 3.1A). +- (6) Only for MSs supporting CSGs: in manual CSG selection mode the user selects from the available CSGs. +- (7) Only for MSs supporting CSGs: if the selected CSG is associated with the RPLMN, the MS performs selection of a cell belonging to this CSG. +- (8) Only for MSs supporting CSGs: if the selected CSG is associated with a PLMN different from the RPLMN, the MS enters the PLMN selection process and performs the parts applicable after manual selection of a PLMN. +- (9) After it has selected a PLMN, the MS performs selection of a cell belonging to this PLMN; this selection is additionally restricted by the selected CSG, if the PLMN selection was triggered by a manual CSG selection. +- (10) After having selected a new cell and the registration area has changed, the MS shall enter the LR process (see figure 3). + +- (10a) An MS's CM requests may lead to a registration request. +- (11) If the LR is not successful, and if the cause received from the network does not exclude the RPLMN, the MS performs another cell selection (i.e. cell re-selection) within the RPLMN. +- (12) The information on available PLMNs, as detected by the cell selection process from detectable broadcast information, is made available to the PLMN selection process. +- (13) If the LR is not successful, and if the cause received from the network excludes the RPLMN, the MS performs PLMN selection. +- (14) The positive result of cell selection (suitable cell and in updated state, or in connected mode having been camped on a suitable cell) and location registration (updated, for MSs capable of services requiring registration) is indicated to the user. + +Possible sequences of steps are e.g.: + +- 1) 1 → 2 → 3 → 9 → 10 → 11 (manual PLMN selection, MS is not CSG capable) +- 2) 1 → 9 → 4 → 5 → 6 → 8 → 9 → 10 → 11 (automatic PLMN selection, MS is CSG capable, manual CSG selection); + +![PLMN Selection State diagram (automatic mode)](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Null + Null --> No SIM: Switch on, SIM not available + Null --> Is there a RPLMN?: Switch on with SIM + No SIM --> [*]: SIM not available or invalid SIM + Is there a RPLMN? --> Select registered PLMN: Yes + Is there a RPLMN? --> Trying RPLMN: No + Select registered PLMN --> Trying RPLMN + Trying RPLMN --> Indicate selected PLMN: Registration success + Trying RPLMN --> Select first * PLMN in list: Registration failure + Indicate selected PLMN --> On PLMN + On PLMN --> [*]: On VPLMN and timeout occurs + On PLMN --> Any allowable PLMNs available?: Loss of radio coverage of selected PLMN ** + On PLMN --> A: LR response "Roaming not allowed" + Any allowable PLMNs available? --> Wait for PLMNs to appear: No + Any allowable PLMNs available? --> [*]: Yes + Wait for PLMNs to appear --> [*]: Registered PLMN available and allowable + Wait for PLMNs to appear --> A: PLMN available and allowable, which is not RPLMN + Select first * PLMN in list --> Trying PLMN + Select next * PLMN in list --> Trying PLMN + Trying PLMN --> [*]: Registration successful + Trying PLMN --> Any PLMNs available & allowable?: Registration failure, no more in list + Trying PLMN --> Select next * PLMN in list: Registration failure, more in list + Any PLMNs available & allowable? --> Select first available and allowable PLMN in list: Yes + Any PLMNs available & allowable? --> Select RPLMN or HPLMN or EHPLMN if No RPLMN***: No + Select first available and allowable PLMN in list --> [*] + Select RPLMN or HPLMN or EHPLMN if No RPLMN*** --> [*] + Move last selected PLMN temporarily into list --> A + User re-selection --> A + Higher priority PLMN search --> [*]: Higher priority PLMN not found + Higher priority PLMN search --> A: Higher priority PLMN found + PLMN background search --> [*]: Higher priority PLMN not found + PLMN background search --> A: Higher priority PLMN found + +``` + +The state diagram illustrates the PLMN selection process in automatic mode. It begins with a 'Null' state, which transitions to 'No SIM' if the SIM is not available upon switching on, or to a decision 'Is there a RPLMN?' if the SIM is available. If no RPLMN exists, it proceeds to 'Trying RPLMN'. If an RPLMN is found, it goes to 'Select registered PLMN' and then to 'Trying RPLMN'. 'Trying RPLMN' leads to 'Indicate selected PLMN' on success or to 'Select first \* PLMN in list' on failure. 'Indicate selected PLMN' leads to 'On PLMN', which can lead to [\*] if on a VPLMN and a timeout occurs, or to a decision 'Any allowable PLMNs available?' if there is a loss of radio coverage. If no allowable PLMNs are available, it goes to 'Wait for PLMNs to appear', which leads to [\*] if a registered PLMN becomes available or to 'A' if a PLMN becomes available but is not an RPLMN. If allowable PLMNs are available, it leads to [\*]. 'Select first \* PLMN in list' and 'Select next \* PLMN in list' both lead to 'Trying PLMN'. 'Trying PLMN' leads to [\*] on success, to 'Any PLMNs available & allowable?' on failure if no more in list, or to 'Select next \* PLMN in list' on failure if more in list. 'Any PLMNs available & allowable?' leads to 'Select first available and allowable PLMN in list' if yes, or to 'Select RPLMN or HPLMN or EHPLMN if No RPLMN\*\*\*' if no. Both lead to [\*]. 'Move last selected PLMN temporarily into list' leads to 'A'. 'User re-selection' leads to 'A'. 'Higher priority PLMN search' leads to [\*] if not found or to 'A' if found. 'PLMN background search' leads to [\*] if not found or to 'A' if found. + +PLMN Selection State diagram (automatic mode) + +\* "List" consists of points i) to v) as defined in section 4.4.3.1.1 except in case of a user re-selection in which case "list" consists of points i) to vi) as defined in section 4.4.3.2.1 + +\*\* Includes effective loss of coverage due to LAs/TAs being forbidden in all potentially suitable cells + +\*\*\* HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the list is present) + +Figure 2a: PLMN Selection State diagram (automatic mode) + +![PLMN Selection State diagram (manual mode) flowchart showing the process from switching on the device to selecting a PLMN, including decision points for RPLMN availability and SIM status.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +``` +graph TD; Start(( )) -- "Switch Off" --> Null([Null]); Null -- "Switch on (with SIM)" --> RPLMN{Is there an RPLMN on SIM}; Null -- "Switch on , SIM not available" --> NoSIM([No SIM]); NoSIM -- "SIM available" --> RPLMN; NoSIM -- "SIM not available" --> D((D)); RPLMN -- Yes --> SelectRPLMN[Select registered PLMN]; RPLMN -- No --> DisplayPLMNs[Display PLMNs]; SelectRPLMN --> TryingRPLMN([Trying selected PLMN]); TryingRPLMN -- "Registration success" --> Indicate[Indicate selected PLMN]; TryingRPLMN -- "Invalid SIM" --> D; TryingRPLMN -- "Registration failure" --> DisplayPLMNs; Indicate --> OnPLMN([On PLMN]); OnPLMN -- "LR response 'Roaming not allowed', 'PLMN not allowed' or 'GPRS services not allowed'" --> C((C)); OnPLMN -- "Invalid SIM" --> D; OnPLMN -- "User reselection" --> C; OnPLMN --> A((A)); OnPLMN --> B((B)); OnPLMN --> NotOnPLMN([Not on PLMN]); NotOnPLMN -- "previously selected PLMN becomes available again" --> E((E)); NotOnPLMN -- "user chooses PLMN" --> SelectUser[Select user chosen PLMN]; SelectUser --> TryingUser([Trying PLMN]); TryingUser -- "Registration success" --> A; TryingUser -- "Invalid SIM" --> D; TryingUser -- "Registration failure" --> B; +``` + +PLMN Selection State diagram (manual mode) flowchart showing the process from switching on the device to selecting a PLMN, including decision points for RPLMN availability and SIM status. + +Figure 2b: PLMN Selection State diagram (manual mode) + +![Figure 3: Location Registration Task State diagram. This state machine diagram shows the transitions between four main states: Null, Idle, No IMSI, LR pending, Updated, Not updated, and Roaming not allowed. Transitions are triggered by events like 'Switch on', 'SIM available', 'LR request', 'LR accepted', 'LR rejected', 'Cell change', 'LA/TA change', 'CM request performed', or 'Timer for periodic LR expires'. The diagram includes detailed rejection reasons for various states.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` + +stateDiagram-v2 + [*] --> Null + Null --> Idle, No IMSI: Switch on, SIM not available + Null --> LR pending: Switch on, SIM available - LR needed + Null --> Updated: Switch on SIM available - no LR needed + Idle, No IMSI --> Null: SIM available + Idle, No IMSI --> LR pending: LR failure - New attempt required + LR pending --> Null: LR rejected: "IMSI unknown in HLR", "Illegal ME", "Illegal MS", "GPRS not allowed", "GPRS and non-GPRS not allowed" + LR pending --> Updated: LR accepted + LR pending --> Roaming not allowed: "Roaming not allowed in TA", "GPRS not allowed in this PLMN", "No suitable cell in LA", "No suitable cell in TA", "Not authorized for this CSG" + LR pending --> Not updated: Other LR failure + Updated --> [*]: Timer for periodic LR expires + Updated --> [*]: New LA/TA entered + Not updated --> [*]: Cell change + Not updated --> [*]: LA/TA change + Not updated --> [*]: CM request performed + Not updated --> [*]: Timer for periodic LR expires + Roaming not allowed --> [*]: LR rejected: "PLMN not allowed", "LA not allowed", "TA not allowed", "Roaming not allowed in LA" + Roaming not allowed --> [*]: "Roaming not allowed in TA", "GPRS not allowed in this PLMN", "No suitable cell in LA", "No suitable cell in TA", "Not authorized for this CSG" + Roaming not allowed --> [*]: LR rejected: "PLMN not allowed", "GPRS not allowed in this PLMN" & new PLMN selected + Roaming not allowed --> [*]: LR rejected: "LA not allowed", "TA not allowed" & (new PLMN selected or new LA/TA entered) + Roaming not allowed --> [*]: LR rejected: "Roaming not allowed in LA", "Roaming not allowed in TA" & HPLMN selected + Roaming not allowed --> [*]: LR rejected: "Not authorized for this CSG" & new cell selected + Roaming not allowed --> [*]: LR rejected: "No suitable cell in LA", "No suitable cell in TA" & new LA/TA selected + +``` + +Figure 3: Location Registration Task State diagram. This state machine diagram shows the transitions between four main states: Null, Idle, No IMSI, LR pending, Updated, Not updated, and Roaming not allowed. Transitions are triggered by events like 'Switch on', 'SIM available', 'LR request', 'LR accepted', 'LR rejected', 'Cell change', 'LA/TA change', 'CM request performed', or 'Timer for periodic LR expires'. The diagram includes detailed rejection reasons for various states. + +NOTE 1: Whenever the MS goes to connected mode and then returns to idle mode again the MS selects appropriate state. + +NOTE 2: An MS capable of GPRS and non-GPRS services has two Task State machines one for GPRS and one for non-GPRS operation. + +Figure 3: Location Registration Task State diagram + +# 6 MS supporting access technologies defined both by 3GPP and 3GPP2 + +## 6.1 General + +An MS that supports access technologies defined both by 3GPP and 3GPP2 (see 3GPP TS 31.102 [40]) shall consider all supported access technologies in all supported bands when performing PLMN selection. + +The goal of the PLMN selection process for such a multi mode MS is to find the highest priority PLMN and to attempt to register to it. + +A multi mode MS shall follow the requirements in the present document for the PLMN selection procedures across both 3GPP and 3GPP2 access technologies. Additionally, the MS shall follow the requirements of the present document in its signalling procedures towards any 3GPP network. If the common PLMN selection procedure leads to selection of a + +3GPP2 network, then the MS shall follow 3GPP2 specifications in meeting any 3GPP2 specific system selection constraints and in all signalling procedures towards the 3GPP2 network. + +While registered to VPLMN via 3GPP2 access, the MS shall follow the 3GPP2 specifications for scan of higher priority PLMNs. Additionally to the requirements specified for 3GPP2 system, a multi mode MS while registered to a 3GPP2 VPLMN shall follow the requirements specified in clause 4.4.3.3. + +NOTE: It is assumed that the MS can determine the PLMN identity of networks supporting 3GPP2 technologies from the information broadcast over the air. + +# Annex A (normative): HPLMN Matching Criteria + +With the introduction of PCS1900 with the regulatory mandate to allocate 3-digit MNC codes, additional functionality is required to identify the HPLMN. + +## Assumptions + +An MNC code shall consist of 2 or 3 decimal digits. In NA PCS1900, all SIMs shall store 3 digit MNCs. + +Any network using a 2 digit MNC code shall broadcast the hexadecimal code "F" in place of the 3rd digit. + +For PCS1900 for North America, regulations mandate that a 3-digit MNC shall be used; however during a transition period, a 2 digit MNC may be broadcast by the Network and, in this case, the 3rd digit of the SIM is stored as 0 (this is the 0 suffix rule). + +With the exception of North America during the transition period: + +- a) Within a single country (or area identified by a MCC) all networks shall broadcast a 2 digit MNC code, or all networks shall broadcast a 3 digit MNC code. A mixture of broadcast 2 and 3 digit MNC codes is not permitted within a single country (or area identified by a MCC). +- b) A network which broadcasts a 2 digit MNC code, will issue SIMs with a 2 digit MNC code in the IMSI on the SIM. A network which broadcasts a 3 digit MNC code, will issue SIMs with a 3 digit MNC code in the IMSI on the SIM. + +## Definitions and abbreviations + +- BCCH-MCC** For GERAN, the MCC part of the LAI read from System Information type 3 messages broadcast on the BCCH by the network (see 3GPP TS 44.018 [34]), for UTRA, the MCC part of the PLMN broadcasted as specified in 3GPP TS 25.331 [33], for E-UTRA, the MCC part of the PLMN broadcasted as specified in 3GPP TS 36.331 [42], or for NR, the MCC part of the PLMN broadcasted as specified in 3GPP TS 38.331 [65]. +- BCCH-MNC** For GERAN the MNC part of the LAI read from System Information type 3 messages broadcast on the BCCH by the network (see 3GPP TS 44.018 [34]), for UTRA, the MNC part of the PLMN broadcasted as specified in 3GPP TS 25.331 [33], for E-UTRA, the MNC part of the PLMN broadcasted as specified in 3GPP TS 36.331 [42], or for NR, the MNC part of the PLMN broadcasted as specified in 3GPP TS 38.331 [65]. +- SIM-MCC** The MCC part of the IMSI or of additional entries in the EHPLMN list read from the SIM. +- SIM-MNC** The MNC part of the IMSI or of additional entries in the EHPLMN list read from the SIM. + +## HPLMN Matching Criteria in mobiles which don't support PCS1900 for NA: + +Figure A.1 illustrates the logic flow described below. The text below is normative. Figure A.1 is informative. + +- (1) The MS shall compare using all 3 digits of the SIM-MCC with the BCCH-MCC. If the values do not match, then the HPLMN match fails. + +NOTE: If the MCC codes match, then the number of digits used for the SIM-MNC must be the same as the number of digits used for the BCCH-MNC. + +- (2) The MS shall read the 3rd digit of the BCCH-MNC. If the 3rd digit is Hex F, then proceed to step (4). +- (3) The MS shall compare using all 3 digits of the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. +- (4) The MS shall compare using just the 1st 2 digits the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. + +If the EHPLMN list is present and is empty or if the EHPLMN list is not present, the matching procedure shall be done for the MCC/MNC of the IMSI. + +If the EHPLMN list is present and is not empty, the matching procedure shall be done for all entries in the EHPLMN list until a match is found or all matches fail. + +![Flowchart of HPLMN Matching Criteria Logic Flow for mobiles which support GSM and DCS1800. The flow starts with step 1: SIM-MCC = BCCH-MCC. If No, it fails. If Yes, it proceeds to step 2: 3rd digit of BCCH-MNC is Hex F. If No, it proceeds to step 3: 3 digit SIM-MNC and BCCH-MNC match. If Yes, it proceeds to step 4: 1st 2 digits of SIM-MNC and BCCH-MNC match. If No, it fails. If Yes, it succeeds.](333992a0b3b7a9d826f72f7bf199221b_img.jpg) + +``` + +graph TD + Step1{{1. +SIM-MCC = +BCCH-MCC}} -- No --> Fail1[Fail] + Step1 -- Yes --> Step2{{2. 3rd digit of +BCCH-MNC is +Hex F}} + Step2 -- No --> Step3{{3. +3 digit SIM-MNC and +BCCH-MNC match}} + Step2 -- Yes --> Step4{{4. +1st 2 digits of SIM-MNC +and BCCH-MNC match}} + Step3 -- No --> Fail2[Fail] + Step3 -- Yes --> Succeed1[Succeed] + Step4 -- No --> Fail3[Fail] + Step4 -- Yes --> Succeed2[Succeed] + +``` + +Flowchart of HPLMN Matching Criteria Logic Flow for mobiles which support GSM and DCS1800. The flow starts with step 1: SIM-MCC = BCCH-MCC. If No, it fails. If Yes, it proceeds to step 2: 3rd digit of BCCH-MNC is Hex F. If No, it proceeds to step 3: 3 digit SIM-MNC and BCCH-MNC match. If Yes, it proceeds to step 4: 1st 2 digits of SIM-MNC and BCCH-MNC match. If No, it fails. If Yes, it succeeds. + +**Figure A.1: HPLMN Matching Criteria Logic Flow for mobiles which support GSM and DCS1800 (informative)** + +## HPLMN Matching Criteria for mobiles which support PCS1900 for NA: + +Figure A.2 illustrates the logic flow described below. The text below is normative. Figure A.2 is informative. + +- (1) The MS shall compare using all 3 digits the SIM-MCC with the BCCH-MCC. If the values do not match, then the HPLMN match fails. +- (2) The MS shall read the 3rd digit of the BCCH-MNC. If the 3rd digit is Hex F, then proceed to step (4). +- (3) The MS shall compare using all 3 digits the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. + +NOTE: These rules (1) – (3) are the same as for mobiles which don't support PCS1900 for NA, except step (4) is different. + +- (4) The MS shall determine if the BCCH-MCC lies in the range 310-316 (i.e., whether this network is a PCS1900 for NA network). If the BCCH-MCC lies outside the range 310-316, then proceed to step (6). +- (5) The MS shall compare the 3rd digit of the SIM-MNC with '0'. If the 3rd digit is not '0' then the HPLMN match fails. + +NOTE: This is the '0' suffix rule. + +- (6) The MS shall compare using just the 1st 2 digits of the SIM-MNC with the BCCH-MNC. If the values match, then the HPLMN match succeeds, otherwise the HPLMN match fails. + +NOTE: When PCS1900 for NA switches over to broadcasting 3 digit MNCs in all networks, then the additional requirements for PCS1900 for NA can be deleted. + +If the EHPLMN list is present and is empty or if the EHPLMN list is not present, the matching procedure shall be done for the MCC/MNC of the IMSI. + +If the EHPLMN list is present and is not empty, the matching procedure shall be done for all entries in the EHPLMN list until a match is found or all matches fail. + +### **Guidance for Networks in PCS1900 for NA** + +There may be some problems in the transition period from broadcasting 2 MNC digits to broadcasting 3 MNC digits. Here are some guidelines to avoid these problems. + +- (1) Existing network codes. Operators who currently use a 2 digit BCCH-MNC *xy* should use the new code *xy0*. +- (2) New operators allocated 3 digit MNC codes with the same 1st 2 digits as an existing operator shall not use a 3rd digit of 0. + +![Flowchart of HPLMN Matching Criteria Logic Flow for mobiles which support PCS1900 for NA. The flow starts with SIM-MCC = BCCH-MCC. If No, Fail. If Yes, check if 3rd digit of BCCH-MNC is Hex F. If No, check if 3 digit SIM-MNC and BCCH-MNC match. If Yes, Succeed. If No, Fail. If Yes to Hex F, check if BCCH-MCC is in range 310-316. If No, proceed to step 6. If Yes, check if 3rd digit of SIM-MNC is 0. If No, Fail. If Yes, proceed to step 6. Step 6: 1st 2 digits of SIM-MNC and BCCH MNC match. If Yes, Succeed. If No, Fail.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +``` +graph TD; Step1{{1. SIM-MCC = BCCH-MCC}} -- No --> Fail1[Fail]; Step1 -- Yes --> Step2{{2. 3rd digit of BCCH-MNC is Hex F}}; Step2 -- No --> Step3{{3. 3 digit SIM-MNC and BCCH-MNC match}}; Step2 -- Yes --> Step4{{4. BCCH-MCC in the range 310-316}}; Step3 -- No --> Fail2[Fail]; Step3 -- Yes --> Succeed1[Succeed]; Step4 -- No --> Step6{{6. 1st 2 digits of SIM-MNC and BCCH MNC match}}; Step4 -- Yes --> Step5{{5. 3rd digit of SIM-MNC is 0}}; Step5 -- No --> Fail3[Fail]; Step5 -- Yes --> Step6; Step6 -- No --> Fail4[Fail]; Step6 -- Yes --> Succeed2[Succeed]; +``` + +Flowchart of HPLMN Matching Criteria Logic Flow for mobiles which support PCS1900 for NA. The flow starts with SIM-MCC = BCCH-MCC. If No, Fail. If Yes, check if 3rd digit of BCCH-MNC is Hex F. If No, check if 3 digit SIM-MNC and BCCH-MNC match. If Yes, Succeed. If No, Fail. If Yes to Hex F, check if BCCH-MCC is in range 310-316. If No, proceed to step 6. If Yes, check if 3rd digit of SIM-MNC is 0. If No, Fail. If Yes, proceed to step 6. Step 6: 1st 2 digits of SIM-MNC and BCCH MNC match. If Yes, Succeed. If No, Fail. + +Figure A.2: HPLMN Matching Criteria Logic Flow for mobiles which support PCS1900 for NA (informative) + +# --- Annex B (normative): PLMN matching criteria to be of same country as VPLMN + +While an MS is roaming on a VPLMN, the VPLMN and a PLMN are of the same country only if their MCC values identify the same country. See clause 1.2 for the definition of country. + +# --- Annex C (normative): Control plane solution for steering of roaming in 5GS + +## C.0 Requirements for 5G steering of roaming over the control plane + +In addition to the requirements specified in 3GPP TS 22.011 [9] clause 3.2.2.8, 3GPP TS 22.261 [74] clause 6.30 and 3GPP TS 23.501 [62] clause 5.30.2.2, the requirements in this clause apply. + +The UE supporting N1 mode shall support the control plane solution for steering of roaming in 5GS. If the HPLMN or subscribed SNPN supports and wants to use the control plane solution for steering of roaming in 5GS, then the HPLMN or subscribed SNPN shall provide the steering of roaming information to the UE using the control plane mechanism defined in this annex. + +The VPLMN shall transparently relay the steering of roaming information received from the HPLMN to the UE. The UE shall be able to detect whether the VPLMN removed the steering of roaming information during the initial registration procedure in the VPLMN. The UE shall be able to detect whether the VPLMN altered the steering of roaming information. If the UE detects that the VPLMN altered or removed the steering of roaming information then the UE shall consider the current VPLMN as the lowest priority PLMN and perform PLMN selection as defined in this annex. + +The non-subscribed SNPN shall transparently relay the steering of roaming information received from the HPLMN or subscribed SNPN to the UE. The UE shall be able to detect whether the non-subscribed SNPN removed the steering of roaming information during the initial registration procedure in the non-subscribed SNPN. The UE shall be able to detect whether the non-subscribed SNPN altered the steering of roaming information. If the UE detects that the non-subscribed SNPN altered or removed the steering of roaming information then the UE shall consider the current SNPN as the lowest priority SNPN and perform SNPN selection as defined in this annex. + +## --- C.1 General + +### C.1.1 Steering of roaming over the control plane in a PLMN + +The purpose of the control plane solution for steering of roaming in 5GS procedure in a PLMN is to allow the HPLMN to update one or more of the following via NAS signalling: + +- the "Operator Controlled PLMN Selector with Access Technology" list in the UE by providing the HPLMN protected list of preferred PLMN/access technology combinations or a secured packet; +- the SOR-CMCI; +- the SOR-SNPN-SI associated with the selected PLMN subscription in the ME; +- the SOR-SNPN-SI-LS associated with the selected PLMN subscription in the ME; and +- the SOR-SENSE (i.e the "Operator controlled signal threshold per access technology") provided in a secured packet. + +If the selected PLMN is a VPLMN, the HPLMN can provide the steering of roaming information to the UE using the control plane mechanism during and after registration. If the selected PLMN is the HPLMN, the HPLMN can provide the steering of roaming information to the UE using the control plane mechanism after registration only. The HPLMN updates the "Operator Controlled PLMN Selector with Access Technology" based on the operator policies, which can be based on the registered VPLMN, the location of the UE, etc. + +The HPLMN may update the "Operator controlled signal threshold per access technology" based on the operator policies and the operator specific data analytic information. + +The HPLMN can configure their subscribed UE's USIM to indicate that the UE is expected to receive the steering of roaming information due to initial registration in 5GS in a VPLMN. At the same time the HPLMN will mark the UE is expected to receive the steering of roaming information due to initial registration in 5GS in a VPLMN, in the subscription information in the UDM. In this case, it is mandatory for the HPLMN to provide the steering of roaming information to the UE during initial registration in a VPLMN. Otherwise, if such configuration is not provided in the USIM, it is optional for the HPLMN to provide the steering of roaming information to the UE during initial registration (based on operator policy). The HPLMN can provide the steering of roaming information to the UE during the registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) and initial registration procedure for emergency services. In addition, the HPLMN can request the UE to provide an acknowledgement of successful reception of the steering of roaming information. + +NOTE 1: In annex C of this specification, the User Data Repository (UDR) is considered as part of the UDM. + +As the HPLMN needs to consider certain criteria including the number of customers distributed through multiple VPLMNs in the same country or region, the list of the preferred PLMN/access technology combinations is not necessarily the same at all times and for all users. The list of the preferred PLMN/access technology combinations needs to be dynamically generated, e.g. generated on demand, by a dedicated steering of roaming application function (SOR-AF) providing operator specific data analytics solutions. + +NOTE 2: The functional description of this dedicated application function (SOR-AF) is out of scope of 3GPP. + +The steering of roaming connected mode control information (SOR-CMCI) enables the HPLMN to control the timing of a UE in 5GS connected mode to move to idle mode to perform the steering of roaming. If the UE selects a cell of any access technology other than NG-RAN, the SOR procedure is terminated (see clause C.4.2). The UE shall support the SOR-CMCI. The support and use of SOR-CMCI by the HPLMN is based on the HPLMN's operator policy. + +The following requirements are applicable for the SOR-CMCI: + +- The HPLMN may configure SOR-CMCI in the UE and may also send SOR-CMCI over N1 NAS signalling. The SOR-CMCI received over N1 NAS signalling has precedence over the SOR-CMCI configured in the UE. + +NOTE 3: Based on HPLMN policy, while setting the SOR-CMCI the HPLMN can take into consideration the user preference for the service(s) not to be interrupted due to SOR (e.g. MMTEL voice call, MMTEL video call, HPLMN defined services, among others). The user can communicate its preference for the service(s) not to be interrupted due to SOR to the HPLMN utilizing non-standard operator-specific mechanisms, e.g. web-based. + +- The UE shall indicate ME's support for SOR-CMCI to the HPLMN. + +NOTE 4: The HPLMN has the knowledge of the USIM's capabilities in supporting SOR-CMCI. + +- While performing SOR, the UE shall consider the list of preferred PLMN/access technology combinations or secured packet received in the SOR information together with the available SOR-CMCI. +- The HPLMN may provision the SOR-CMCI in the UE over N1 NAS signalling. The UE shall store the configured SOR-CMCI in the non-volatile memory of the ME or in the USIM as described in clause C.4. + +The following requirement is applicable for the SOR-SNPN-SI: + +- If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall indicate ME's support for SOR-SNPN-SI to the HPLMN. + +The following requirement is applicable for the SOR-SNPN-SI-LS: + +- If the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall indicate ME's support for SOR-SNPN-SI-LS to the HPLMN. + +In order to support various deployment scenarios, the UDM may support at least one of the following functionalities: + +- a) obtaining a list of preferred PLMN/access technology combinations, SOR-CMCI, if any (if supported by the UDM and required by the HPLMN), or a secured packet which is available or becomes available in the UDM (i.e. retrieved from the UDR); or + +NOTE 5: A secured packet can be made available at the UDR via implementation specific means. In this case the implementation specific means are required to ensure that the secured packet satisfies the "Replay detection and Sequence Integrity counter" (see ETSI TS 102 225 [73]) every time it is sent out from the HPLMN to the UE. + +- b) obtaining a list of preferred PLMN/access technology combinations, SOR-CMCI, if any (if supported by the UDM and required by the HPLMN), or a secured packet from the SOR-AF. + +The HPLMN policy for the SOR-AF invocation can be present in the UDM only if the UDM supports obtaining a list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or a secured packet from the SOR-AF. + +The UDM discards any list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or any secured packet obtained from the SOR-AF or which is or becomes available in the UDM (i.e. retrieved from the UDR), either during registration (as specified in annex C.2) or after registration (as specified in annex C.3 and C.4.3), when the UDM cannot successfully forward the SOR information to the AMF (e.g. in case the UDM receives the response from the SOR-AF with the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, if any, the secured packet after the expiration of the operator specific timer, or if there is no AMF registered for the UE). + +The UE maintains a list of "PLMNs where registration was aborted due to SOR". If the UE receives steering of roaming information in the REGISTRATION ACCEPT or DL NAS TRANSPORT message and the security check to verify that the steering of roaming information is provided by HPLMN is successful, the UE shall remove the current selected PLMN from the list of "PLMNs where registration was aborted due to SOR". The UE shall delete the list of "PLMNs where registration was aborted due to SOR" when the MS is switched off or the USIM is removed. The UE may also remove PLMN(s) from the list of "PLMNs where registration was aborted due to SOR" after a UE implementation dependent time. + +If: + +- a) the UE's USIM is configured to indicate that the UE shall expect to receive the steering of roaming information during initial registration procedure but did not receive it or security check on the steering of roaming information fails; +- b) the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR"; +- c) the current chosen VPLMN is not part of "User Controlled PLMN Selector with Access Technology" list; and +- d) the UE is not in manual mode of operation; + +then the UE will perform PLMN selection with the current VPLMN considered as lowest priority. + +It is mandatory for the VPLMN to transparently forward to the UE the steering of roaming information received from HPLMN and to transparently forward to the HPLMN the acknowledgement of successful reception of the steering of roaming information received from UE, both while the UE is trying to register onto the VPLMN as described in clause C.2, and after the UE has registered onto the VPLMN as described in clause C.3 and C.4.3. + +If the last received steering of roaming information contains the list of preferred PLMN/access technology combinations then the ME shall not delete the "Operator Controlled PLMN Selector with Access Technology" list stored in the non-volatile memory of the ME when the UE is switched off. + +The "Operator Controlled PLMN Selector with Access Technology" list shall be stored in the non-volatile memory of the ME together with the SUPI from the USIM. The ME shall delete the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME when a new USIM is inserted. + +The procedure in this annex for steering of UE in VPLMN can be initiated by the network while the UE is trying to register onto the VPLMN as described in clause C.2, or after the UE has registered onto the HPLMN or the VPLMN as described in clause C.3, C.7 and C.4.3. + +### C.1.2 Steering of roaming over the control plane in an SNPN + +The purpose of the control plane solution for steering of roaming in 5GS procedure in an SNPN is to allow the HPLMN or subscribed SNPN to update one or more of the following via NAS signalling: + +- a) the SOR-SNPN-SI associated with the selected entry of "list of subscriber data" or the selected PLMN subscription in the ME, for a UE which supports access to an SNPN using credentials from a credential holder; + +- b) the SOR-CMCI; and +- c) the SOR-SNPN-SI-LS associated with the selected entry of "list of subscriber data" or the selected PLMN subscription in the ME, if the UE supports access to an SNPN providing access for localized services in SNPN. + +The control plane solution for steering of roaming in 5GS procedure in an SNPN can also be used by the HPLMN to update the "Operator Controlled PLMN Selector with Access Technology" list in the UE by providing the HPLMN protected list of preferred PLMN/access technology combinations or a secured packet via NAS signalling. + +The HPLMN or subscribed SNPN can provide the steering of roaming information to the UE using the control plane mechanism during and after registration. The HPLMN or subscribed SNPN updates the SOR-SNPN-SI based on the HPLMN or subscribed SNPN policies, which can be based on the registered SNPN, the location of the UE, etc. The control plane solution for steering of roaming in 5GS procedure in an SNPN is not applicable for credentials holder with AAA server. + +If the UE supports access to an SNPN using credentials from a credentials holder: + +- a) the UE shall indicate ME's support for SOR-SNPN-SI when registering in a subscribed SNPN or in the HPLMN; and +- b) the UE may indicate ME's support for SOR-SNPN-SI when sending an SOR transparent container including a UE acknowledgement in a PLMN. + +When the UE indicates ME's support for SOR-SNPN-SI in the 5GMM capability in initial registration or emergency registration or when ME's support for SOR-SNPN-SI changes in mobility registration update, the AMF shall inform the UDM. + +The HPLMN or subscribed SNPN can configure their subscribed UEs' SNPN configuration parameters associated with the PLMN subscription or the selected entry of the "list of subscriber data", respectively, to expect to receive the steering of roaming information due to initial registration in a non-subscribed SNPN. At the same time the HPLMN or subscribed SNPN will mark the UE as expecting to receive the steering of roaming information due to initial registration in a non-subscribed SNPN, in the subscription information in the UDM. In this case, it is mandatory for the HPLMN or subscribed SNPN to provide the steering of roaming information to the UE during initial registration in a non-subscribed SNPN. Otherwise if such configuration is not provided in the ME, it is optional for the HPLMN or subscribed SNPN to provide the steering of roaming information to the UE during initial registration (based on HPLMN or subscribed SNPN policy). The HPLMN or subscribed SNPN can provide the steering of roaming information to the UE during the registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) and initial registration procedure for emergency services. In addition, the HPLMN or subscribed SNPN can request the UE to provide an acknowledgement of successful reception of the steering of roaming information. + +NOTE 1: In annex C of this specification, the User Data Repository (UDR) is considered as part of the UDM. + +As the HPLMN or subscribed SNPN needs to consider certain criteria including the number of customers distributed through multiple SNPNs in the same country or region, the SOR-SNPN-SI is not necessarily the same at all times and for all users. + +NOTE 2: The functional description of this dedicated application function (SOR-AF) is out of scope of 3GPP. + +The steering of roaming connected mode control information (SOR-CMCI) enables the HPLMN or subscribed SNPN to control the timing of a UE in connected mode to move to idle mode, if the UE decides to perform SNPN selection upon receiving the steering of roaming information. The UE shall support the SOR-CMCI. The support and use of SOR-CMCI by the HPLMN or subscribed SNPN is based on the HPLMN or subscribed SNPN policy. + +The following requirements are applicable for the SOR-CMCI: + +- The HPLMN or subscribed SNPN may configure SOR-CMCI in the UE and may also send SOR-CMCI over N1 NAS signalling. The SOR-CMCI received over N1 NAS signalling has precedence over the SOR-CMCI configured in the UE. +- The UE shall indicate ME's support for SOR-CMCI to the HPLMN or subscribed SNPN. + +NOTE 3: If the credentials holder is the HPLMN, the HPLMN has the knowledge of the USIM's capabilities in supporting SOR-CMCI. + +- While performing SOR, the UE shall consider the SOR-SNPN-SI and SOR-SNPN-SI-LS (if any) received in the SOR information together with the available SOR-CMCI. +- The HPLMN or subscribed SNPN may provision the SOR-CMCI in the UE over N1 NAS signalling. The UE shall store the configured SOR-CMCI in the non-volatile memory of the ME or in the USIM as described in clause C.4. + +The following requirement is applicable for the SOR-SNPN-SI-LS: + +- If the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall indicate ME's support for SOR-SNPN-SI-LS to the subscribed SNPN or the HPLMN. + +In order to support various deployment scenarios, the UDM may support: + +- obtaining the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any (if supported by the UDM and required by the HPLMN), which are or becomes available in the UDM (i.e. retrieved from the UDR); +- obtaining the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any (if supported by the UDM and required by the HPLMN), from the SOR-AF; or +- both of the above. + +The HPLMN or subscribed SNPN policy for the SOR-AF invocation can be present in the UDM only if the UDM supports obtaining the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any, from the SOR-AF. + +The UDM discards any SOR-SNPN-SI and SOR-SNPN-SI-LS, if any, obtained from the SOR-AF or which are or becomes available in the UDM (i.e. retrieved from the UDR), either during registration (as specified in annex C.5) or after registration (as specified in annex C.6), when the UDM cannot successfully forward the SOR information to the AMF (e.g. in case the UDM receives the response from the SOR-AF with the SOR-SNPN-SI and SOR-SNPN-SI-LS, if any, after the expiration of the HPLMN or subscribed SNPN specific timer, or if there is no AMF registered for the UE). + +The UE maintains a list of "SNPNs where registration was aborted due to SOR" per entry of the "list of subscriber data" or the PLMN subscription. If the UE receives steering of roaming information in the REGISTRATION ACCEPT or DL NAS TRANSPORT message in an SNPN and the security check to verify that the steering of roaming information is provided by the HPLMN or subscribed SNPN is successful, the UE shall remove the current selected SNPN from the list of "SNPNs where registration was aborted due to SOR" for the selected entry of the "list of subscriber data" or the selected PLMN subscription. The UE shall delete the list of "SNPNs where registration was aborted due to SOR" when the selected entry of the "list of subscriber data" is updated or the UICC containing the USIM is removed. + +If: + +- the UE's ME is configured to indicate that the UE shall expect to receive the steering of roaming information during initial registration procedure for the selected entry of the "list of subscriber data" or the selected PLMN subscription but did not receive it or security check on the steering of roaming information fails; +- the current chosen non-subscribed SNPN is not contained in the list of "SNPNs where registration was aborted due to SOR" for the selected entry of the "list of subscriber data" or the selected PLMN subscription; +- the current chosen non-subscribed SNPN is not part of the user controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" or the selected PLMN subscription; and +- the UE is not in manual mode of operation; + +then the UE will perform SNPN selection with the current SNPN considered as lowest priority. + +It is mandatory for the non-subscribed SNPN to transparently forward to the UE the steering of roaming information received from the HPLMN or subscribed SNPN and to transparently forward to the HPLMN or subscribed SNPN the acknowledgement of successful reception of the steering of roaming information received from the UE, both while the UE is trying to register onto the non-subscribed SNPN as described in clause C.5, and after the UE has registered onto the non-subscribed SNPN as described in clause C.6. + +The ME shall delete the SOR-SNPN-SI and SOR-SNPN-SI-LS (if available) stored in the ME when the subscriber identifier, the SNPN identity of the subscribed SNPN, or both, of the selected entry of the "list of subscriber data" are updated or the UICC containing the USIM is removed. + +The procedure in this annex for steering of UE in an SNPN can be initiated by the network while the UE is trying to register onto a non-subscribed SNPN as described in clause C.5, or after the UE has registered onto the subscribed SNPN or a non-subscribed SNPN as described in clause C.6 and C.8. + +### C.2 Stage-2 flow for steering of UE in VPLMN during registration + +The stage-2 flow for the case when the UE registers with VPLMN AMF is described below in figure C.2.1. The selected PLMN is the VPLMN. The AMF is located in the selected VPLMN. + +![Sequence diagram showing the stage-2 flow for steering of UE in VPLMN during registration. The diagram involves four main entities: UE, VPLMN AMF, HPLMN UDM, and SOR-AF. The process starts with a REGISTRATION REQUEST from UE to VPLMN AMF. The AMF initiates the registration procedure with the UDM via Nudm_UECM_Registration request. The UDM deletes the 'ME support of SOR-CMCI' indicator if the registration type is 'initial' or 'emergency'. The AMF then sends a REGISTRATION ACCEPT to the UE. The UDM makes a decision to send steering information and requests it from the SOR-AF via Nsoraf_SoR_Get request. The SOR-AF responds with Nsoraf_SoR_Get response. The AMF secures the information and sends a Nudm_SDM_Get response to the UDM. The UDM sends a Nudm_SDM_Subscribe request to the AMF. The AMF sends a REGISTRATION ACCEPT to the UE. The UE performs a steering of roaming information security check. If the security check fails or the UE is configured to receive steering of roaming information but did not receive it, the UE performs a PLMN selection procedure and ends the procedure. The AMF sends a REGISTRATION COMPLETE to the UE. The UE sends a REGISTRATION COMPLETE to the AMF. The AMF sends a Nudm_SDM_Info request to the UDM. The UDM sends a Nsoraf_SoR_Info request to the SOR-AF. The UE performs a PLMN selection procedure if a higher priority PLMN is available.](691626a7032a642bb74793336c37e274_img.jpg) + +``` + +sequenceDiagram + participant UE + participant VPLMN AMF + participant HPLMN UDM + participant SOR-AF + + Note right of SOR-AF: Delete "ME support of SOR-CMCI" indicator if NAS registration type is either "initial" or "emergency" + + Note right of HPLMN UDM: 3a. Decision to send steering of roaming information, whether to request ACK from the UE, and how to obtain the list of preferred PLMN/access technology combinations or the secured packet. + + Note right of HPLMN UDM: 3d. Securing information + + Note left of UE: 7. Steering of roaming information security check + + Note left of UE: 8. If the security check fails or the UE is configured to receive steering of roaming information but did not receive it, then perform PLMN selection procedure and end the procedure + + Note left of UE: 11. UE performs PLMN selection procedure if higher priority PLMN is available + + UE->>VPLMN AMF: 1. REGISTRATION REQUEST + VPLMN AMF->>HPLMN UDM: 2. Registration procedure initiation Nudm_UECM_Registration request + HPLMN UDM-->>VPLMN AMF: Nudm_UECM_Registration response + VPLMN AMF->>UE: REGISTRATION ACCEPT + HPLMN UDM->>SOR-AF: 3b. Nsoraf_SoR_Get request + SOR-AF-->>HPLMN UDM: 3c. Nsoraf_SoR_Get response + HPLMN UDM-->>VPLMN AMF: 4. Nudm_SDM_Get response + VPLMN AMF->>HPLMN UDM: 5. Nudm_SDM_Subscribe request + VPLMN AMF->>UE: 6. REGISTRATION ACCEPT + UE->>VPLMN AMF: REGISTRATION COMPLETE + VPLMN AMF->>HPLMN UDM: 10. Nudm_SDM_Info request + HPLMN UDM->>SOR-AF: 10a. Nsoraf_SoR_Info request + UE->>VPLMN AMF: 9. REGISTRATION COMPLETE + VPLMN AMF-->>UE: REGISTRATION COMPLETE + +``` + +Sequence diagram showing the stage-2 flow for steering of UE in VPLMN during registration. The diagram involves four main entities: UE, VPLMN AMF, HPLMN UDM, and SOR-AF. The process starts with a REGISTRATION REQUEST from UE to VPLMN AMF. The AMF initiates the registration procedure with the UDM via Nudm\_UECM\_Registration request. The UDM deletes the 'ME support of SOR-CMCI' indicator if the registration type is 'initial' or 'emergency'. The AMF then sends a REGISTRATION ACCEPT to the UE. The UDM makes a decision to send steering information and requests it from the SOR-AF via Nsoraf\_SoR\_Get request. The SOR-AF responds with Nsoraf\_SoR\_Get response. The AMF secures the information and sends a Nudm\_SDM\_Get response to the UDM. The UDM sends a Nudm\_SDM\_Subscribe request to the AMF. The AMF sends a REGISTRATION ACCEPT to the UE. The UE performs a steering of roaming information security check. If the security check fails or the UE is configured to receive steering of roaming information but did not receive it, the UE performs a PLMN selection procedure and ends the procedure. The AMF sends a REGISTRATION COMPLETE to the UE. The UE sends a REGISTRATION COMPLETE to the AMF. The AMF sends a Nudm\_SDM\_Info request to the UDM. The UDM sends a Nsoraf\_SoR\_Info request to the SOR-AF. The UE performs a PLMN selection procedure if a higher priority PLMN is available. + +**Figure C.2.1: Procedure for providing list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, or secured packet during registration** + +For the steps below, security protection is described in 3GPP TS 33.501 [66]. + +- 1) The UE to the VPLMN AMF: The UE initiates initial registration, emergency registration or registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) to the VPLMN AMF by sending REGISTRATION REQUEST message with the 5GS registration type IE indicating "initial registration", "emergency registration" or "mobility registration updating"; +- 2) Upon receiving REGISTRATION REQUEST message, the VPLMN AMF executes the registration procedure as defined in clause 4.2.2.2 of 3GPP TS 23.502 [63]. As part of the registration procedure: + - a) the AMF provides the registration type to the UDM using Nudm\_UECM\_Registration. As a consequence, in case of the 5GS registration type message indicates "initial registration" or "emergency registration" the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any, the stored "ME support of SOR-SNPN-SI" indicator, if any, and the stored "ME support of SOR-SNPN-SI-LS" indicator, if any, in UDR using Nudr\_DM\_Update service operation (see 3GPP TS 23.502 [63]). + +NOTE 1: Nudr\_DM\_Update service operation corresponds to Nudr\_DR\_Update service operation (see 3GPP TS 29.504 [82] and 3GPP TS 29.505 [83]). + +In addition: + +- a) if the VPLMN AMF does not have subscription data for the UE, the VPLMN AMF invokes Nudm\_SDM\_Get service operation to the HPLMN UDM to get amongst other information the Access and Mobility Subscription data for the UE (see step 14b in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); or +- b) if the VPLMN AMF already has subscription data for the UE and: + - i) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "initial registration" and the "SoR Update Indicator for Initial Registration" field in the UE context is set to 'the UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type "initial registration"' as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]); or + - ii) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "emergency registration" and the "SoR Update Indicator for Emergency Registration" field in the UE context is set to 'the UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type "emergency registration"' as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]); + +then the VPLMN AMF invokes Nudm\_SDM\_Get service operation message to the HPLMN UDM to retrieve the steering of roaming information (see step 14b in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); + +otherwise the VPLMN AMF sends a REGISTRATION ACCEPT message without the steering of roaming information to the UE and steps 3a, 3b, 3c, 3d, 4, 5, 6 are skipped; + +- 3a) If the user subscription information indicates to send the steering of roaming information due to initial registration in a VPLMN, then the HPLMN UDM shall provide the steering of roaming information to the UE when the UE performs initial registration in a VPLMN, otherwise the HPLMN UDM may provide the steering of roaming information to the UE, based on operator policy. + +NOTE 2: Based on operator deployment and policy, if the UDM receives the list of preferred PLMN/access technology combinations from the UDR, and the UDM supports communication with the SP-AF, the UDM can send this list to the SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544 [71]. + +If the HPLMN UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a VPLMN, and the HPLMN policy for the SOR-AF invocation is absent then steps 3b and 3c are not performed and the HPLMN UDM obtains the available list of preferred PLMN/access technology combinations or the available secured packet (i.e. all retrieved from the UDR). In addition, if the HPLMN UDM obtains the list of preferred PLMN/access technology combinations and the "ME support of SOR-CMCI" indicator is stored for the UE, then the HPLMN UDM shall obtain the SOR-CMCI, if available, otherwise the HPLMN UDM shall not obtain the SOR-CMCI. If the SOR-CMCI is provided then the HPLMN UDM may indicate to the UE to store the SOR-CMCI in the ME by providing the "Store SOR-CMCI in ME" indicator set to "Store SOR-CMCI in ME". + +NOTE 3: The secured packet obtained by the UDM can include SOR-CMCI only if the "ME support of SOR-CMCI" indicator is stored for the UE and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then SOR-CMCI, if any, cannot be included in the secured packet. + +NOTE 4: The secured packet obtained by the UDM can include SOR-SENSE only if the USIM of the indicated SUPI supports SOR-SENSE. + +If the HPLMN UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a VPLMN, and the HPLMN policy for the SOR-AF invocation is present, then the HPLMN UDM obtains the list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or the secured packet from the SOR-AF using steps 3b and 3c; + +3b) The HPLMN UDM to the SOR-AF: Nsoraf\_SoR\_Get request (VPLMN ID, SUPI of the UE, access type (see 3GPP TS 29.550 [88])). The VPLMN ID and the access type parameters, indicating where the UE is registering, are stored in the HPLMN UDM; + +NOTE 5: Information about UE supporting SOR-SENSE can be available directly in SOR-AF (or in OAM which configures the secure packet in UDM/UDR). + +3c) The SOR-AF to the HPLMN UDM: Nsoraf\_SoR\_Get response (the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet, or neither of them); + +Based on the information received in step 3b and any operator specific criteria, the SOR-AF may either: + +- include the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and optionally the "Store SOR-CMCI in ME" indicator, if any; +- provide the secured packet in the Nsoraf\_SoR\_Get response; or +- provide the Nsoraf\_SoR\_Get response with neither of the information above. + +If the SOR-AF includes the list of preferred PLMN/access technology combinations and the ME supports the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally the "Store SOR-CMCI in ME" indicator, otherwise the SOR-AF shall provide neither the SOR-CMCI nor "Store the SOR-CMCI in ME" indicator. + +NOTE 6: In this version of the specification, when the access type where the UE is registering indicates 3GPP access, then the UE is registering over the NG-RAN access technology. + +NOTE 7: Based on operator deployment and policy, if the UDM receives the list of preferred PLMN/access technology combinations, and the SOR-CMCI, if any, in the Nsoraf\_SoR\_Get response from the SOR-AF, and the UDM supports communication with SP-AF, it can send this list, and the SOR-CMCI, if any, to SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544 [71]. + +NOTE 8: The SOR-AF can include a different list of preferred PLMN/access technology combinations, different SOR-CMCI, if any, and different "Store SOR-CMCI in ME" indicator, if any, or a different secured packet for each Nsoraf\_SoR\_Get request even if the same VPLMN ID, the SUPI of the UE, and the access type are provided to the SOR-AF. + +NOTE 9: The SOR-AF can subscribe to the HPLMN UDM to be notified about the changes of the roaming status of the UE identified by SUPI. + +NOTE 10: The SOR-AF can determine that the ME supports the SOR-CMCI if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-CMCI" indicator. + +NOTE 11: Secured packet provided by the SOR-AF can include SOR-CMCI only if the SOR-AF has determined that the ME supports the SOR-CMCI and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then SOR-CMCI, if any, cannot be included in the secured packet. + +NOTE 12: Secured packets do not include the "Store SOR-CMCI in ME" indicator. + +3d) The HPLMN UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from: + +- the list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or the secured packet obtained in step 3a; or + +the list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, and "Store the SOR-CMCI in ME" indicator, if any, or the secured packet, obtained in step 3c. + +If: + +- neither the list of preferred PLMN/access technology combinations nor the secured packet was obtained in steps 3a or 3c; or +- the SOR-AF has not sent to the HPLMN UDM an Nsoraf\_SoR\_Get response (step 3c) within an operator defined time after the HPLMN UDM sending to the SOR-AF an Nsoraf\_SoR\_Get request (step 3b); + +NOTE 13: Stage 3 to define the timer needed for the SOR-AF to respond to the HPLMN UDM. The max time needs to be defined considering that this procedure is part of the registration procedure. + +and the UE is performing initial registration in a VPLMN and the user subscription information indicates to send the steering of roaming information due to initial registration in a VPLMN, then the HPLMN UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'; + +If the "Store SOR-CMCI in ME" indicator was not obtained in step 3a or 3c and the "ME support of SOR-CMCI" indicator is stored for the UE in the HPLMN UDM, the HPLMN UDM forms the steering of roaming information with the "Store SOR-CMCI in ME" indicator set to "Do not store SOR-CMCI in ME"; + +- 4) The HPLMN UDM to the VPLMN AMF: The HPLMN UDM sends a response to the Nudm\_SDM\_Get service operation to the VPLMN AMF, which includes the steering of roaming information within the Access and Mobility Subscription data. The Access and Mobility Subscription data type is defined in clause 5.2.3.3.1 of 3GPP TS 23.502 [63]. + +NOTE 14: The UDM cannot provide the SOR-CMCI, if any, to the VPLMN AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). + +If the UE is performing initial registration or emergency registration and the HPLMN UDM supports SOR-CMCI, the HPLMN shall request the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering of roaming information in the Nudm\_SDM\_Get response service operation. Otherwise, the HPLMN may request the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering of roaming information in the Nudm\_SDM\_Get response service operation; + +NOTE 15: If the UE is performing registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) after inter-system change from S1 mode to N1 mode and the HPLMN UDM supports SOR-CMCI, the HPLMN requests the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering of roaming information in the Nudm\_SDM\_Get response service operation, unless the HPLMN UDM has already received and stored the "ME support of SOR-CMCI" indicator for the UE during its former registration on the current VPLMN. + +- 5) The VPLMN AMF to the HPLMN UDM: As part of the registration procedure, the VPLMN AMF also invokes Nudm\_SDM\_Subscribe service operation to the HPLMN UDM to subscribe to notification of changes of the subscription data (e.g. received in step 4) including notification of updates of the steering of roaming information included in the Access and Mobility Subscription data (see step 14c in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); +- 6) The VPLMN AMF to the UE: The VPLMN AMF shall transparently send the received steering of roaming information to the UE in the REGISTRATION ACCEPT message; +- 7) If the steering of roaming information is received and the security check is successful, then: + - a) if the UDM has not requested an acknowledgement from the UE, then the UE shall send the REGISTRATION COMPLETE message to the serving AMF without including an SOR transparent container; + - b) if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]): + - the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41], if the service "data download via SMS Point-to-point" is allocated and activated in the USIM Service Table (see 3GPP TS 31.102 [40]); + +NOTE 16: How the ME handles UICC responses and failures in communication between the ME and UICC is implementation specific and out of scope of this release of the specification. + +NOTE 17: If the SOR-SENSE has been updated in the USIM, the UE uses the "Operator controlled signal threshold per access technology" information stored on the USIM in accordance to clause 3.11 of this specification. + +- if the UDM has not requested an acknowledgement from the UE and: + - A) the ME receives a USAT REFRESH with command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming" and either a SOR-CMCI is included, or the UE is configured with the SOR-CMCI, the UE shall perform items a), b) and c) of the procedure for steering of roaming in clause 4.4.6, and if the UE is in automatic network selection mode, then it shall apply the actions in clause C.4.2. In this case steps 8 to 11 are skipped; or + - B) the ME receives a USAT REFRESH command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming" and neither a SOR-CMCI is included, nor the UE is configured with the SOR-CMCI, it shall perform items a), b) and c) of the procedure for steering of roaming in clause 4.4.6 and if: + - i) the UE has a list of available and allowable PLMNs in the area and based on this list or any other implementation specific means the UE determines that there is a higher priority PLMN than the selected VPLMN; or + - ii) the UE does not have a list of available and allowable PLMNs in the area and is unable to determine whether there is a higher priority PLMN than the selected VPLMN using any other implementation specific means; +- and the UE is in automatic network selection mode, then the UE shall either: +- i) release the current N1 NAS signalling connection locally and then attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired. In this case, steps 8 to 11 are skipped. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency service fallback until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session or is performing emergency services fallback (see 3GPP TS 24.501 [64]), the receipt of the steering of roaming information shall not trigger the release of the N1 NAS signalling connection. If camped on a NG-RAN cell, the UE shall release the current N1 NAS signalling connection locally subsequently after the emergency PDU session is released, otherwise the UE shall not take any further actions; or + - ii) not release the current N1 NAS signalling connection locally (e.g. if the UE has established PDU session(s)) and skip steps 8 to 10; +- c) if the steering of roaming information contains the list of preferred PLMN/access technology combinations, the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME with the received list of preferred PLMN/access technology combinations, and delete the PLMNs identified by the list of preferred PLMN/access technology combinations from the Forbidden PLMN list and from the Forbidden PLMNs for GPRS service list, if they are present in these lists. Additionally, if: + - i) the UE has a list of available and allowable PLMNs in the area and based on this list or any other implementation specific means the UE determines that there is a higher priority PLMN than the selected VPLMN; or + - ii) the UE does not have a list of available and allowable PLMNs in the area and is unable to determine whether there is a higher priority PLMN than the selected VPLMN using any other implementation specific means; +- and the UE is in automatic network selection mode: +- A) if the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE shall apply the actions in clause C.4.2. In this case steps 8 to 11 are skipped; + +B) otherwise, the UE shall: + +- i) release the current N1 NAS signalling connection locally and then attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired. In this case, steps 8 to 11 are skipped. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session or is performing emergency services fallback (see 3GPP TS 24.501 [64]), the receipt of the steering of roaming information shall not trigger the release of the N1 NAS signalling connection. If camped on a NG-RAN cell, the UE shall release the current N1 NAS signalling connection locally subsequently after the emergency PDU session is released, otherwise the UE shall not take any further actions. If the UE needs to disable the N1 mode capability (see 3GPP TS 24.501 [64]) and there is no emergency service pending, the UE shall first attempt to obtain service on a higher priority PLMN as described in this step, and if no higher priority PLMN can be selected but the last registered PLMN is selected, then the UE shall disable the N1 mode capability; or +- ii) not release the current N1 NAS signalling connection locally (e.g. if the UE has established PDU session(s)) and skip steps 8 to 10; + +NOTE 18: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User Controlled PLMN Selector with Access Technology" list, the UE stays on the VPLMN. + +- 8) If the UE's USIM is configured with indication that the UE is to receive the steering of roaming information due to initial registration in a VPLMN, but neither the list of preferred PLMN/access technology combinations nor the secured packet nor the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided' is received in the REGISTRATION ACCEPT message, when the UE performs initial registration in a VPLMN or if the steering of roaming information is received but the security check is not successful, then the UE shall: + - a) if the SOR transparent container is included in the REGISTRATION ACCEPT message, send the REGISTRATION COMPLETE message to the serving AMF without including an SOR transparent container; + - b) if the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR", and is not part of "User Controlled PLMN Selector with Access Technology" list and the UE is not in manual mode of operation: + - i) if the steering of roaming information is received but the security check is not successful when the UE performs registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) in a VPLMN and the UE has a stored SOR-CMCI, and there are ongoing PDU sessions or services, the UE shall apply the actions in clause C.4.2. In this case, current PLMN is considered as lowest priority and steps 9 to 11 are skipped; + - ii) otherwise, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that the current PLMN is considered as lowest priority, and skip steps 9 to 11. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency services fallback until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]), if camped on a NG-RAN cell, the UE shall release the current N1 NAS signalling connection locally after the release of the emergency PDU session, otherwise the UE shall not take any further actions. If the UE needs to disable the N1 mode capability (see 3GPP TS 24.501 [64]) and there is no emergency service pending, the UE shall first attempt to obtain service on a higher priority PLMN as described in this step, and if no higher priority PLMN can be selected but the last registered PLMN is selected, then the UE shall disable the N1 mode capability; and + - c) if the current chosen VPLMN is not contained in the list of "PLMNs where registration was aborted due to SOR", store the PLMN identity in the list of "PLMNs where registration was aborted due to SOR"; + +NOTE 19: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User Controlled PLMN Selector with Access Technology" list, the UE stays on the VPLMN. + +- 9) The UE to the VPLMN AMF: If the UDM has requested an acknowledgement from the UE and the UE verified that the steering of roaming information has been provided by the HPLMN in step 7, then: +- a) the UE sends the REGISTRATION COMPLETE message to the serving AMF with an SOR transparent container including the UE acknowledgement; + - b) the UE shall set the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container to "supported"; + - c) if the UE supports access to an SNPN using credentials from a credentials holder, the UE may set the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container to "supported"; + - c1) if the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported"; and + - d) if: + - the steering of roaming information contained a secured packet, then when the UE receives the USAT REFRESH command qualifier of type "Steering of Roaming" and neither a SOR-CMCI is included, nor the UE is configured with the SOR-CMCI, it performs items a), b) and c) of the procedure for steering of roaming in clause 4.4.6; + - the steering of roaming information contained a secured packet, then when the UE receives a USAT REFRESH with command qualifier (3GPP TS 31.111 [41]) of type "Steering of Roaming" and either a SOR-CMCI is included, or the UE is configured with the SOR-CMCI, the UE shall perform items a), b) and c) of the procedure for steering of roaming in clause 4.4.6 and if the UE is in automatic network selection mode, then it shall apply the actions in clause C.4.2, and step 11 is skipped; + - the steering of roaming information contains the list of preferred PLMN/access technology combinations, the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, and the UE is in automatic network selection mode, then the UE shall apply the actions in clause C.4.2, and step 11 is skipped; or + - the steering of roaming information contains an indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided', then step 11 is skipped; +- 10) The VPLMN AMF to the HPLMN UDM: If an SOR transparent container is received in the REGISTRATION COMPLETE message, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. If the HPLMN decided that the UE is to acknowledge the successful security check of the received steering of roaming information in step 4, the UDM verifies that the acknowledgement is provided by the UE as specified in 3GPP TS 33.501 [66]. If: +- the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any; + - the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-SNPN-SI" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-SNPN-SI" indicator, if any; and + - the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any. + +NOTE 20: The UDM cannot receive the "ME support of SOR-CMCI" indicator, the "ME support of SOR-SNPN-SI" indicator, or "ME support of SOR-SNPN-SI-LS" indicator from the VPLMN AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). + +- 10a) The HPLMN UDM to the SOR-AF: Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery, "ME support of SOR-CMCI" indicator, if any, "ME support of SOR-SNPN-SI" indicator, if any, "ME support of SOR-SNPN-SI- + +LS" indicator, if any). If the HPLMN policy for the SOR-AF invocation is present and the HPLMN UDM received and verified the UE acknowledgement in step 10, then the HPLMN UDM informs the SOR-AF about successful delivery of the list of preferred PLMN/access technology combinations, or of the secured packet to the UE. If: + +- the "ME support of SOR-CMCI" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-CMCI" indicator +- the "ME support of SOR-SNPN-SI" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-SNPN-SI" indicator; and +- the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator; and + +NOTE 21: How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific. + +- 11) If the UE has a list of available PLMNs in the area and based on this list the UE determines that there is a higher priority PLMN than the selected VPLMN and the UE is in automatic network selection mode, then the UE shall attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired after the release of the N1 NAS signalling connection. If within an implementation dependent time the N1 NAS signalling connection is not released, then the UE may locally release the N1 NAS signalling connection except when the UE has an established emergency PDU session or is performing emergency services fallback (see 3GPP TS 24.501 [64]). The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. + +When the UE performs initial registration for emergency services (see 3GPP TS 24.501 [64] and 3GPP TS 23.502 [63]) while the UE has a valid USIM and the AMF performs the authentication procedure, then based on HPLMN policy, the SOR procedure described in this clause may apply. + +If: + +- the UE in manual mode of operation encounters scenario mentioned in step 8 above; and +- upon switching to automatic network selection mode, the UE remembers that it is still registered on the PLMN where the missing or security check failure of SOR information was encountered as described in clause 8; + +the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3, by acting as if timer T that controls periodic attempts has expired, with an exception that the current registered PLMN is considered as lowest priority. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, emergency services fallback or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed. If the UE has an established emergency PDU session, then the UE shall attempt to perform the PLMN selection subsequently after the emergency PDU session is released. + +NOTE 22: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. + +NOTE 23: The list of available and allowable PLMNs in the area is implementation specific. + +NOTE 24: If the UE is served by any access technology other than NG-RAN, the HPLMN can initiate a steering of roaming procedure as specified in clause 4.4.6. + +## C.3 Stage-2 flow for steering of UE in HPLMN or VPLMN after registration + +The stage-2 flow for the steering of UE in HPLMN or VPLMN after registration is indicated in figure C.3.1. The selected PLMN can be the HPLMN or a VPLMN. The AMF is located in the selected PLMN. In this procedure, the + +SOR-CMCI, if any, is sent together with the list of preferred PLMN/access technology combinations in plain text or is sent within the secured packet. + +The procedure is triggered: + +- If the HPLMN UDM supports obtaining a list of preferred PLMN/access technology combinations and SOR-CMCI, if any, or a secured packet from the SOR-AF, the HPLMN policy for the SOR-AF invocation is present in the HPLMN UDM, and the SOR-AF provides the HPLMN UDM with a new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI. If the ME supports the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally provides the "Store SOR-CMCI in ME" indicator otherwise the SOR-AF shall provide neither the SOR-CMCI nor the "Store SOR-CMCI in ME" indicator. + +The secured packet provided by the SOR-AF may include SOR-CMCI only if the SOR-AF has determined that the ME supports the SOR-CMCI and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then the SOR-AF shall not include the SOR-CMCI, if any, in the secured packet; or + +NOTE 1: The SOR-AF can determine that the ME supports the SOR-CMCI if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-CMCI" indicator. How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific. + +- When a new list of preferred PLMN/access technology combinations or a secured packet becomes available in the HPLMN UDM (i.e. retrieved from the UDR). + +If the "ME support of SOR-CMCI" indicator is stored for the UE and the new list of preferred PLMN/access technology combinations becomes available in the HPLMN UDM (i.e. retrieved from the UDR), the HPLMN UDM shall obtain the SOR-CMCI and the "Store SOR-CMCI in ME" indicator, if available, otherwise the HPLMN UDM shall obtain neither the SOR-CMCI nor the "Store SOR-CMCI in ME" indicator. + +NOTE 3: Based on operator deployment and policy, if the UDM receives the list of preferred PLMN/access technology combinations, SOR-CMCI, if any, the "Store SOR-CMCI in ME" indicator, if any, and the USIM of the indicated SUPI supports SOR-CMCI from the UDR, and the UDM supports communication with the SP-AF, the UDM can send this list and SOR-CMCI to the SP-AF requesting it to provide this information in a secured packet as defined in 3GPP TS 29.544 [71]. + +NOTE 4: Before providing the HPLMN UDM with a new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI, the SOR-AF, based on operator policies or criteria, can obtain the user location information by triggering the unified location service exposure procedure as defined in 3GPP TS 23.273 [70] clause 6.5, or additionally based on implementation specific criteria, by requesting the UE location information from other application function using implementation specific method. This user location information can then be used in the SOR-AF algorithms. + +NOTE 5: The secured packet obtained by the UDM can include SOR-CMCI only if the "ME support of SOR-CMCI" indicator is stored for the UE and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then the SOR-CMCI, if any, cannot be included in the secured packet. + +![Sequence diagram illustrating the procedure for providing list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, or secured packet after registration. The diagram shows interactions between UE, AMF, HPLMN UDM, and SOR-AF.](a5404b7275b06497eecf9b5883604753_img.jpg) + +``` + +sequenceDiagram + participant SOR-AF + participant HPLMN_UDM as HPLMN UDM + participant AMF + participant UE + + Note right of SOR-AF: 1. Nudm_ParameterProvision_Update request + SOR-AF-->>HPLMN_UDM: 1. Nudm_ParameterProvision_Update request + Note right of HPLMN_UDM: 2. Nudm_SDM_Notification request + HPLMN_UDM-->>AMF: 2. Nudm_SDM_Notification request + Note right of AMF: 3. DL NAS Transport + AMF-->>UE: 3. DL NAS Transport + Note left of UE: 4. Steering of roaming information security check + UE-->>AMF: UL NAS Transport + Note right of AMF: 5. Nudm_SDM_Info request + AMF-->>HPLMN_UDM: 5. Nudm_SDM_Info request + Note right of HPLMN_UDM: 6. Nsoraf_SoR_Info request + HPLMN_UDM-->>SOR-AF: 6. Nsoraf_SoR_Info request + +``` + +Sequence diagram illustrating the procedure for providing list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, or secured packet after registration. The diagram shows interactions between UE, AMF, HPLMN UDM, and SOR-AF. + +**Figure C.3.1: Procedure for providing list of preferred PLMN/access technology combinations and the SOR-CMCI, if any, or secured packet after registration** + +For the steps below, security protection is described in 3GPP TS 33.501 [66]. + +- 1) The SOR-AF to the HPLMN UDM: Nudm\_ParameterProvision\_Update request is sent to the HPLMN UDM to trigger the update of the UE with the new list of preferred PLMN/access technology combinations, the SOR-CMCI, if any, and the "Store SOR-CMCI in ME" indicator, if any, or a secured packet for a UE identified by SUPI. +- 2) The HPLMN UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm\_SDM\_Notification service operation. The Nudm\_SDM\_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm\_SDM\_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. If the SOR-CMCI was obtained, the HPLMN UDM shall include the SOR-CMCI into the steering of roaming information. If the "Store SOR-CMCI in ME" indicator was obtained, the HPLMN UDM shall include the "Store SOR-CMCI in ME" indicator; otherwise, the HPLMN UDM shall include the "Store SOR-CMCI in ME" indicator set to "Do not store SOR-CMCI in ME"; + +NOTE 6: The UDM cannot provide the SOR-CMCI, if any, to the VPLMN AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). + +- 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. +- 4) Upon receiving the steering of roaming information, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN, and: + - if the security check is successful and: + - a) if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]) and the service "data download via SMS Point-to-point" is allocated and activated in the USIM Service Table (see 3GPP TS 31.102 [40]), the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41]. + +If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message and the ME receives UICC responses indicating that the UICC has received the secured packet successfully, + +then the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE: + +- shall set the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container to "supported"; +- may set the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN using credentials from a credentials holder; and +- shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN; and + +NOTE 7: How the ME handles UICC responses that do not indicate that the UICC has received the secured packet successfully and failures in communication between the ME and UICC is implementation specific and out of scope of this release of the specification. + +- when the ME receives a USAT REFRESH command qualifier (see 3GPP TS 31.111 [41]) of type "Steering of Roaming" and neither a SOR-CMCI is included, nor the UE is configured with the SOR-CMCI, it performs the procedure for steering of roaming in clause 4.4.6 with an exception that if the UE is in automatic network selection mode, then the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN (specified in clause 4.4.6 bullet d); or + - when the ME receives a USAT REFRESH with command qualifier (see 3GPP TS 31.111 [41]) of type "Steering of Roaming" and either a SOR-CMCI is included, or the UE is configured with the SOR-CMCI, the UE shall perform items a), b) and c) of the procedure for steering of roaming in clause 4.4.6. If the UE is in automatic network selection mode it shall apply the actions in clause C.4.2; +- b) if the steering of roaming information contains the list of preferred PLMN/access technology combinations, the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME with the received list of preferred PLMN/access technology combinations, and delete the PLMNs identified by the list of preferred PLMN/access technology combinations from the Forbidden PLMN list and from the Forbidden PLMNs for GPRS service list, if they are present in these lists. + +If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE: + +- shall set the "ME support of SOR-CMCI" indicator to "supported" +- may set the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN using credentials from a credentials holder; and +- shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN. + +If the UE is in automatic network selection mode and the selected PLMN is a VPLMN, then: + +- if the UE has a stored SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE shall apply the actions in clause C.4; or +- the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, emergency services fallback or establishing an emergency PDU session, until the attempts to obtain service on a higher priority PLMN are completed. + +If the selected PLMN is a VPLMN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection subsequently after the emergency PDU session is released, if the UE is in automatic network selection mode. + +If the UDM has not requested an acknowledgement from the UE, then step 5 is skipped; and + +- if the selected PLMN is a VPLMN, the security check is not successful and the UE is in automatic network selection mode, then: + - if the UE has a stored SOR-CMCI, the current PLMN is considered as lowest priority and the UE shall apply the actions in clause C.4.2; or + - if there are ongoing PDU sessions or services, the UE shall apply the actions in clause C.4.2; or + - the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed; +- if the UE does not have a stored SOR-CMCI, then: + - if there are ongoing PDU sessions or services, the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that the current PLMN is considered as lowest priority. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session, then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released; or + - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that the current PLMN is considered as lowest priority. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. + +Step 5 is skipped; + +NOTE 8: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User Controlled PLMN Selector with Access Technology" list, the UE stays on the VPLMN. + +5) The AMF to the HPLMN UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. If the HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information in step 1, the UDM verifies that the acknowledgement is provided by the UE. If: + +- the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any; +- the "ME support of SOR-SNPN-SI" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-SNPN-SI" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-SNPN-SI" indicator, if any; and +- the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the HPLMN UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the HPLMN UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any; and + +- 6) The HPLMN UDM to the SOR-AF: Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery, "ME support of SOR-CMCI" indicator, if any, "ME support of SOR-SNPN-SI" indicator, if any, "ME support of SOR-SNPN-SI-LS" indicator, if any). If the HPLMN policy for the SOR-AF invocation is present and the HPLMN UDM received and verified the UE acknowledgement in step 5, then the HPLMN UDM informs the SOR-AF about successful delivery of the list of preferred PLMN/access technology combinations, SOR-CMCI, if any, or of the secured packet to the UE. If: + - the "ME support of SOR-CMCI" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-CMCI" indicator; + - the "ME support of SOR-SNPN-SI" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-SNPN-SI" indicator; and + - the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the HPLMN UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator. + +If the selected PLMN is a VPLMN and: + +- the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and +- upon switching to automatic network selection mode, the UE remembers that it is still registered on the PLMN where the security check failure of SOR information was encountered; + +the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3, by acting as if timer T that controls periodic attempts has expired, with an exception that the current registered PLMN is considered as lowest priority. The UE shall not initiate the establishment of a new N1 NAS signalling connection, unless for the purpose of initiating a registration procedure for emergency services, establishing an emergency PDU session or performing emergency services fallback, until the attempts to obtain service on a higher priority PLMN are completed. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session, then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released. + +NOTE 9: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. + +NOTE 10: If the selected PLMN is the HPLMN, regardless of whether the UE is in automatic network selection mode or manual network selection mode, regardless of whether the UE has an established emergency PDU session or not, and regardless of whether the security check is successful or not successful, the UE is not required to perform the PLMN selection. + +## --- C.4 Enhanced 5G control plane steering of roaming for the UE in connected mode + +### C.4.1 General + +The HPLMN or subscribed SNPN, based on operator policy, may provide the UE with SOR-CMCI to control the timing when the UE enters idle mode and performs higher priority PLMN/access technology or SNPN selection. This is achieved by the HPLMN indicating to the UE the criteria for releasing specific PDU session(s) or services and entering idle mode. + +NOTE 1: The released PDU sessions may be re-established by the application once the UE successfully registers on a higher priority PLMN or SNPN. User interaction is required for some applications. + +The HPLMN or subscribed SNPN may configure the SOR-CMCI in the UE, and may also provide the SOR-CMCI to the UE over N1 NAS signalling. The SOR-CMCI received over N1 NAS signalling takes precedence over the SOR-CMCI stored in the non-volatile memory of the ME or stored in the USIM. + +NOTE 2: The SOR-CMCI received over N1 NAS signalling in the steering of roaming information is either the SOR-CMCI in the USAT REFRESH with command qualifier of type "Steering of Roaming" (see 3GPP TS 31.111 [41]) which is received in a secured packet, or the SOR-CMCI received in plain text. + +If the UE receives SOR information containing the list of preferred PLMN/access technology combinations or SOR-SNPN-SI without SOR-CMCI, or the ME receives USAT REFRESH with command qualifier (see 3GPP TS 31.111 [41]) of type "Steering of Roaming" without SOR-CMCI, or the security check of the received steering of roaming information is not successful as described in clause C.2, clause C.3 and clause C.4.3, then: + +- 1) if the UE has SOR-CMCI stored in the non-volatile memory of the ME, the UE shall use the SOR-CMCI stored in the non-volatile memory of the ME; and +- 2) if the UE has no SOR-CMCI stored in the non-volatile memory of the ME, the UE shall use the SOR-CMCI stored in the USIM, if any. + +The UE shall delete the stored SOR-CMCI, if any, in the non-volatile memory of the ME and store the received SOR-CMCI in the non-volatile memory of the ME when: + +- 1) the ME receives SOR-CMCI in the USAT REFRESH with command qualifier (see 3GPP TS 31.111 [41]) of type "Steering of Roaming"; or +- 2) the UE receives the steering of roaming information containing the SOR-CMCI over N1 NAS signalling and the UE receives the "Store SOR-CMCI in ME" indicator set to "Store SOR-CMCI in ME"; + +The SOR-CMCI shall be stored in the non-volatile memory of the ME together with the SUPI from the USIM. The ME shall not delete the SOR-CMCI when the UE is switched off. The ME shall delete the SOR-CMCI when a new USIM is inserted. + +The MS shall be able to handle at least: + +- 4 SOR-CMCI rules for PDU session attribute type criterion DNN of the PDU session; +- 4 SOR-CMCI rules for PDU session attribute type criterion S-NSSAI STT of the PDU session or S-NSSAI SST and SD of the PDU session; and +- 6 SOR-CMCI rules for any of the following types: service type criterion, SOR security check criterion or match all type criterion. + +If the UE receives the steering of roaming information over N1 NAS signalling containing the SOR-CMCI together with the "Store SOR-CMCI in ME" indicator set to "Do no store SOR-CMCI in ME", the UE shall not overwrite the SOR-CMCI stored in the ME, if any, with the received SOR-CMCI, and shall apply the received SOR-CMCI for the procedure triggered by receiving the steering of roaming information containing that SOR-CMCI. If there is an ongoing SOR procedure, then the UE shall apply the received SOR-CMCI as described in clause C.4.2. + +SOR-CMCI consists of SOR-CMCI rules. Each SOR-CMCI rule consists of the following parameters: + +- i) a criterion of one of the following types: + - PDU session attribute type criterion; + - service type criterion; + - SOR security check criterion; or + - match all type criterion; and +- ii) a value for Tsor-cm timer associated with each criterion presented in i) indicating the time the UE shall wait before releasing the PDU sessions or the services and entering idle mode. + +SOR-CMCI contains zero, one or more SOR-CMCI rules with PDU session attribute type criterion, zero, one or more SOR-CMCI rules with service type criterion, and zero or one SOR-CMCI rule with match all type criterion. + +PDU session attribute type criterion consists of one of the following: + +- a) DNN of the PDU session; +- b) S-NSSAI STT of the PDU session; or + +- c) S-NSSAI SST and SD of the PDU session. + +Service type criterion consists of one of the following: + +- a) IMS registration related signalling; +- b) MMTEL voice call; +- c) MMTEL video call; or +- d) SMS over NAS or SMSoIP. + +SOR security check criterion consists of: + +- a) SOR security check not successful. + +Match all type criterion consists of: + +- a) match all. + +When the SOR-CMCI received by the UE over N1 NAS signalling contains no SOR-CMCI rules, the UE shall stop all running Tsor-cm timers, if any, and act as if no SOR-CMCI is configured. Additionally: + +- if the SOR-CMCI is received in plain text and it also contains the "Store SOR-CMCI in ME" indicator set to "Store SOR-CMCI in ME", the UE shall delete the stored SOR-CMCI in the non-volatile memory of the ME, if any; and +- if the SOR-CMCI is received in a secured packet, and the USIM provides the ME with the SOR-CMCI in the USAT REFRESH with command qualifier of type "Steering of Roaming" (see 3GPP TS 31.111 [41]), then the UE shall delete the stored SOR-CMCI in the non-volatile memory of the ME, if any. + +The HPLMN may update the SOR-CMCI in the USIM such that it contains no SOR-CMCI rules, in which case the UE behaviour described in clause C.4.2 applies. Also the HPLMN may make the SOR-CMCI file in the USIM unavailable (see 3GPP TS 31.102 [40]). + +If there are more than one criterion applicable for a PDU session (e.g., a criterion for the PDU session and another one for the service) then the Tsor-cm timer with the highest value shall apply. + +If there are more than one criterion applicable to different ongoing PDU sessions or services leading to multiple applicable Tsor-cm timers, then all the applicable Tsor-cm timers shall be started. Further handling of such cases is described in clause C.4.2. + +If the value for Tsor-cm timer equals "infinity" then the UE shall wait until the PDU session is released or the service is stopped. + +The Tsor-cm timer is applicable only if the UE is in automatic network selection mode. + +Upon switching to the manual network selection mode, the UE shall stop any Tsor-cm timer, if running. In this case, the UE is not required to enter idle mode and perform the de-registration procedure. + +The UE shall consider the following services as exempted from being forced to release the related established PDU session, if any, enter idle mode and perform high priority PLMN/access technology or SNPN selection. These services are known to the UE by default and the UE shall not follow the SOR-CMCI criteria even if configured to interrupt such services: + +- i) emergency services. + +The UE configured with high priority access in the selected PLMN or SNPN shall consider all services and all related established PDU sessions, if any, to be exempted from being forced to be released to enter idle mode and perform high priority PLMN/access technology or SNPN selection. + +### C.4.2 Applying SOR-CMCI in the UE + +During SOR procedure and while applying SOR-CMCI, the UE shall determine the time to release the PDU session(s) or the services as follows: + +- If the UE encounters SOR security check not successful on the received steering of roaming information, and: + - if a matching criterion "SOR security check not successful" is included in the stored SOR-CMCI, then the UE shall: + - if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; + - stop all other running Tsor-cm timers, if any; and + - not start any new Tsor-cm timer while Tsor-cm timer associated with "SOR security check not successful" criterion is running; + - otherwise, the UE shall keep the Tsor-cm timers running, if any, and apply actions when the timers expire as described in this clause. +- If one or more SOR-CMCI rules are included in SOR-CMCI, where for each criterion: + - a) DNN of the PDU session: + +the UE shall check whether it has a PDU session with a DNN matching to the DNN included in SOR-CMCI, and if any, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; + - b) S-NSSAI SST of the PDU session: + +the UE shall check whether it has a PDU session with a S-NSSAI SST matching the S-NSSAI SST included in SOR-CMCI, and if any, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; + - b1) S-NSSAI SST and SD of the PDU session: + +the UE shall check whether it has a PDU session with a S-NSSAI SST and SD matching the S-NSSAI SST and SD included in SOR-CMCI, and if any, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; + - c) IMS registration related signalling: + +the UE shall check whether IMS registration related signalling is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; + - d) MMTEL voice call: + +the UE shall check whether MMTEL voice call is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; + - e) MMTEL video call: + +the UE shall check whether MMTEL video call is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; + - f) SMS over NAS or SMSoIP: + +the UE shall check whether SMS over NAS or SMSoIP services is ongoing, and if it is ongoing, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI; or + - g) match all: + +the UE shall check whether there are any PDU sessions or services for which there is no matching criterion in a) to f) above. If such PDU session or service exists, then for each of these PDU sessions or services, the UE shall, if the timer value is not zero, start an associated Tsor-cm timer with the value included in the SOR-CMCI. + +If the SOR-CMCI is available, and: + +- the SOR-CMCI used is in the USIM, contains no SOR-CMCI rule; + +- there are one or more SOR-CMCI rules but there is no criterion matched with any ongoing PDU session or service; or +- there are one or more SOR-CMCI rules and there is one or more criteria matched with an ongoing PDU session or service, but the highest Tsor-cm timer value associated with the matched criteria is equal to zero; + +then there is no Tsor-cm timer started for any PDU session or service. + +While one or more Tsor-cm timers are running, the UE shall check the newly established PDU session or service for a matching criterion in the SOR-CMCI: + +- If a matching criterion is found and the applicable Tsor-cm timer indicated the value "infinity" then the UE shall start the Tsor-cm timer associated to the newly established PDU session or service with the value set to infinity; or +- For all other cases, if a matching criterion is found and the timer value is not zero then the UE shall start the Tsor-cm timer associated to the newly established PDU session or service with the value included in the SOR-CMCI, with the exception that if the value of the Tsor-cm timer included in the SOR-CMCI exceeds the highest value among the current values of all running Tsor-cm timers, then the value of the Tsor-cm timer for the newly established PDU session or service shall be set to the highest value among the current values of all running Tsor-cm timers. + +NOTE 1: For newly established PDU session or service as described above, the timer is set irrespective of whether other ongoing PDU sessions or services that match the same criteria exist and for which corresponding Tsor-cm timers are running. + +NOTE 2: NAS 5GMM layer will receive an explicit indication from the upper layers that a service is started or stopped. When a service is started, it is handled as a new service in the procedures described in this clause. + +NOTE 3: While one or more Tsor-cm timers are running, the UE can trigger any 5GSM procedure or start new services. + +While one or more Tsor-cm timers are running, upon receiving a new SOR-CMCI as described in annex C.4.3, the UE shall check if there is a matching criterion found for any ongoing PDU session or service in the new SOR-CMCI: + +- if a matching criterion is found and the value of Tsor-cm timer in the new SOR-CMCI indicates the value "infinity", then: + - a) if the Tsor-cm timer associated to the PDU session or service is not running, then the UE shall start the Tsor-cm timer associated to the PDU session or service with the value set to infinity; or + - b) if the Tsor-cm timer associated to the PDU session or service is already running, then the UE shall set the value of the Tsor-cm timer associated to the PDU session or service to infinity without stopping and restarting the timer; +- if a matching criterion is found and the value of Tsor-cm timer in the new SOR-CMCI is other than infinity and is smaller than the current value of the running Tsor-cm timer for the associated PDU session or service, then the Tsor-cm timer value for the associated PDU session or service shall be replaced with the value in the new SOR-CMCI without stopping and restarting the timer; or +- for all other cases, the running Tsor-cm timers for the associated PDU sessions or services are kept unchanged. + +The Tsor-cm timer shall be stopped when the associated PDU session is released or the associated service is stopped. + +If the security check on the received steering of roaming information is successful, the UE shall stop the Tsor-cm timer associated with "SOR security check not successful", if running, and act on the received steering of roaming information. The current PLMN or SNPN is not considered as lowest priority. + +NOTE 4: This also applies to the case when the current PLMN or SNPN is different from the PLMN or SNPN in which the Tsor-cm timer associated with "SOR security check not successful" was started. + +If the UE, while one or more Tsor-cm timers are running: + +- a) enters idle mode not due to lower layer failure (see 3GPP TS 24.501 [64]); + +- b) is not able to successfully recover the N1 NAS signalling connection (see 3GPP TS 24.501 [64]); or +- c) enters 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); + +then the UE shall stop the timer(s). In these cases, if: + +- a) the UE has a list of available and allowable PLMNs or SNPNs in the area and based on this list or any other implementation specific means, the UE determines that there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPN; or +- b) the UE does not have a list of available and allowable PLMNs or SNPNs in the area and is unable to determine whether there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPN using any other implementation specific means; + +then the UE shall attempt to obtain service on a higher priority PLMN or SNPN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired or as specified in clause 4.9.3. + +NOTE 5: When the UE enters idle mode due to lower layer failure while one or more Tsor-cm timers are running, then the UE does not stop Tsor-cm timer(s) as recovery of NAS signalling connection is possible (see 3GPP TS 24.501 [64]). + +When the UE determines that no Tsor-cm timer is started for any PDU session or service, the last running Tsor-cm timer is stopped due to release of the associated PDU sessions or stop of the associated services, or the last running Tsor-cm timer expires, if: + +- i) the UE has a list of available and allowable PLMNs or SNPNs in the area and based on this list or any other implementation specific means, the UE determines that there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPN; or +- ii) the UE does not have a list of available and allowable PLMNs or SNPNs in the area and is unable to determine whether there is a higher priority PLMN or SNPN than the selected VPLMN or non-subscribed SNPN using any other implementation specific means; + +then if the UE is in 5GMM-CONNECTED mode, the UE shall perform the de-registration procedure (see clause 4.2.2.3 of 3GPP TS 23.502 [63]) that releases all the established PDU sessions and services, if any, and once the UE enters idle mode it shall attempt to obtain service on a higher priority PLMN or SNPN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired or as specified in clause 4.9.3. + +NOTE 6: The list of available and allowable PLMNs or SNPNs in the area is implementation specific. + +The UE which has an emergency PDU session, receives a request from the upper layers to establish an emergency PDU session or perform emergency services fallback, registers for emergency services, or is configured for high priority access in the selected PLMN or SNPN is not required to enter idle mode if the last running Tsor-cm timer for any PDU session or service stops or expires. In this case, the UE shall attempt to perform the PLMN or SNPN selection after the emergency PDU session or the high priority service is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). + +If the UE selects a cell of any access technology other than NG-RAN, the ongoing SOR procedure is terminated and the UE shall stop applying SOR-CMCI and stop all running Tsor-cm timers without triggering any further actions. + +NOTE 7: If the UE is served by any access technology other than NG-RAN, the HPLMN can initiate a steering of roaming procedure as specified in clause 4.4.6. + +### C.4.3 Stage-2 flow for providing UE with SOR-CMCI in HPLMN, VPLMN, subscribed SNPN or non-subscribed SNPN after registration + +The stage-2 flow for providing UE with SOR-CMCI in HPLMN, VPLMN, subscribed SNPN or non-subscribed SNPN after registration is indicated in figure C.4.3.1, when the ME supports the SOR-CMCI. The selected PLMN or SNPN can be the HPLMN, a VPLMN, the subscribed SNPN or a non-subscribed SNPN. The AMF is located in the selected PLMN or SNPN. The UDM is located in the HPLMN or the subscribed SNPN. + +In this procedure, the SOR-CMCI is sent without the list of preferred PLMN/access technology combinations and the SOR-SNPN-SI. In this procedure, the SOR-CMCI is sent in plain text or is sent within the secured packet. + +NOTE 0: When the UE is registered in a non-subscribed SNPN, the SOR-CMCI can be provided in a secured packet only if the UE is using a PLMN subscription to access the non-subscribed SNPN. + +NOTE 1: The SOR-AF can determine that the ME supports the SOR-CMCI if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-CMCI" indicator. The UDM can determine that the ME supports the SOR-CMCI if the "ME support of SOR-CMCI" indicator is stored for the UE. How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific. + +NOTE 2: The secured packet provided by the SOR-AF can include SOR-CMCI only if the SOR-AF has determined that the ME supports the SOR-CMCI and the USIM of the indicated SUPI supports SOR-CMCI. Otherwise if only the "ME support of SOR-CMCI" indicator is stored for the UE, then SOR-CMCI, if any, cannot be included in the secured packet. + +The procedure is triggered: + +- If the UDM supports obtaining the parameters of the list of preferred PLMN/access technology combinations, the SOR-SNPN-SI, the SOR-CMCI, and the "Store SOR-CMCI in ME" indicator, if any, or a secured packet from the SOR-AF, the HPLMN or subscribed SNPN policy for the SOR-AF invocation is present in the UDM and the SOR-AF provides the UDM with the SOR-CMCI for a UE identified by SUPI; or +- When the SOR-CMCI becomes available in the UDM (i.e., retrieved from the UDR). + +![Sequence diagram for Figure C.4.3.1: Procedure for configuring UE with SOR-CMCI after registration. The diagram shows interactions between UE, AMF, UDM, and SOR-AF. The SOR-AF sends a Nudm_ParameterProvision_Update request to the UDM. The UDM sends a Nudm_SDM_Notification request to the AMF. The AMF sends a DL NAS Transport to the UE. The UE performs a steering of roaming information security check and sends a UL NAS Transport to the AMF. The AMF sends a Nudm_SDM_Info request to the UDM. The UDM sends a Nsoraf_SoR_Info request to the SOR-AF.](a48594f1a3fecef5e047a7c3a63b1220_img.jpg) + +``` + +sequenceDiagram + participant SOR-AF + participant UDM + participant AMF + participant UE + + Note right of SOR-AF: 1. Nudm_ParameterProvision_Update request + SOR-AF-->>UDM: 1. Nudm_ParameterProvision_Update request + Note right of UDM: 2. Nudm_SDM_Notification request + UDM-->>AMF: 2. Nudm_SDM_Notification request + Note right of AMF: 3. DL NAS Transport + AMF-->>UE: 3. DL NAS Transport + Note left of UE: 4. Steering of roaming information security check + Note left of UE: UL NAS Transport + UE-->>AMF: UL NAS Transport + Note right of AMF: 5. Nudm_SDM_Info request + AMF-->>UDM: 5. Nudm_SDM_Info request + Note right of UDM: 6. Nsoraf_SoR_Info request + UDM-->>SOR-AF: 6. Nsoraf_SoR_Info request + +``` + +Sequence diagram for Figure C.4.3.1: Procedure for configuring UE with SOR-CMCI after registration. The diagram shows interactions between UE, AMF, UDM, and SOR-AF. The SOR-AF sends a Nudm\_ParameterProvision\_Update request to the UDM. The UDM sends a Nudm\_SDM\_Notification request to the AMF. The AMF sends a DL NAS Transport to the UE. The UE performs a steering of roaming information security check and sends a UL NAS Transport to the AMF. The AMF sends a Nudm\_SDM\_Info request to the UDM. The UDM sends a Nsoraf\_SoR\_Info request to the SOR-AF. + +**Figure C.4.3.1: Procedure for configuring UE with SOR-CMCI after registration** + +For the steps below, security protection is described in 3GPP TS 33.501 [66]. + +- 1) The SOR-AF to the UDM: Nudm\_ParameterProvision\_Update request is sent to the UDM to trigger the update of the UE with the SOR-CMCI (in plain text or secured packet). In case of providing SOR-CMCI in plain text, include the "Store SOR-CMCI in ME" indicator, if applicable. In case of providing SOR-CMCI in a secured packet, include an indication that "the list of preferred PLMN/access technology combinations is not included in the secured packet". +- 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm\_SDM\_Notification service operation. The Nudm\_SDM\_Notification service operation contains + +the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the HPLMN or subscribed SNPN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm\_SDM\_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. The UDM: + +- upon receiving the SOR-CMCI (in plain text), shall: + - i) if the UE is registered in the HPLMN or a VPLMN, include the SOR-CMCI, the "Store SOR-CMCI in ME" indicator, if any, and the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'; + - ii) if the UE is registered in a non-subscribed SNPN, include the SOR-CMCI, the "Store SOR-CMCI in ME" indicator, if any, and the HPLMN or subscribed SNPN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'; and + - iii) if the UE is registered in a subscribed SNPN and the AMF has reported to the UDM that the UE supports SOR-SNPN-SI, include the SOR-CMCI, the "Store SOR-CMCI in ME" indicator, if any, and the HPLMN or subscribed SNPN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'; or +- upon receiving the SOR-CMCI in secured packet, shall include the secured packet into the steering of roaming information; + +NOTE 3: The UDM considers "the list of preferred PLMN/access technology combinations is not included in the secured packet" received together with the secured packet from the SOR-AF to indicate that the UE is not expected to perform SOR based on the associated steering of roaming information sent to the UE. However, the SOR-CMCI included in the secured packet can be applied by the UE if the UE has one or more Tsor-cm timers running as described in C.4.2. + +NOTE 4: The UDM cannot provide the SOR-CMCI, if any, to the AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). + +- 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. +- 4) Upon receiving the steering of roaming information containing the SOR-CMCI and the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided' or the HPLMN or subscribed SNPN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided', or the secured packet, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN or subscribed SNPN, and: + - a) if the security check is successful, the UE shall store the SOR-CMCI according to clause C.4.1. If the UE has one or more Tsor-cm timers running, the UE shall apply the received SOR-CMCI as described in C.4.2. + +If the steering of roaming information contains a secured packet and the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set the "ME support of SOR-CMCI" indicator to "supported" only after the ME receives UICC responses indicating that the UICC has received the secured packet successfully. Otherwise, if the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set the "ME support of SOR-CMCI" indicator to "supported". Additionally, if the UE supports access to an SNPN using credentials from a credentials holder and the UE is in a PLMN, the UE may set the "ME support of SOR-SNPN-SI" indicator to "supported". + +If the UDM has not requested an acknowledgement from the UE then step 5 is skipped; and + +- b) if the selected PLMN is a VPLMN or a non-subscribed SNPN, the security check is not successful and the UE is in automatic network selection mode, then: + +- if the UE has a stored SOR-CMCI, the current PLMN is considered as lowest priority and the UE shall apply the actions in clause C.4.2; +- otherwise, the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that the current PLMN is considered as lowest priority, or before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the selected PLMN or SNPN is a VPLMN or a non-subscribed SNPN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). + +Step 5 is skipped; + +NOTE 5: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User Controlled PLMN Selector with Access Technology" list or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" the selected PLMN subscription, the UE stays on the VPLMN or non-subscribed SNPN. + +- 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. If the HPLMN or subscribed SNPN decided that the UE is to acknowledge successful security check of the received steering of roaming information in step 2, the UDM verifies that the acknowledgement is provided by the UE. The UDM shall store the "ME support of SOR-CMCI" indicator and the "ME support of SOR-SNPN-SI" indicator, if any; and +- 6) The UDM to the SOR-AF: Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery, "ME support of SOR-CMCI" indicator, "ME support of SOR-SNPN-SI" indicator, if any). If the HPLMN or subscribed SNPN policy for the SOR-AF invocation is present and the UDM received and verified the UE acknowledgement in step 5, then the UDM informs the SOR-AF about successful delivery of the SOR-CMCI to the UE. The UDM shall include the "ME support of SOR-CMCI" indicator and the "ME support of SOR-SNPN-SI" indicator, if any. + +If the selected PLMN is a VPLMN or a non-subscribed SNPN and: + +- the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and +- upon switching to automatic network selection mode the UE remembers that it is still registered on the PLMN the non-subscribed SNPN where the security check failure of SOR information was encountered; + +the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3, by acting as if timer T that controls periodic attempts has expired, with an exception that the current registered PLMN is considered as lowest priority, or before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the selected PLMN is a VPLMN or the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). + +NOTE 6: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. + +## --- C.5 Stage-2 flow for steering of UE in SNPN during registration + +The stage-2 flow for the case when the UE registers in a non-subscribed SNPN is described below in figure C.5.1. The AMF is located in the non-subscribed SNPN. The UDM is located in the HPLMN or subscribed SNPN. + +![Sequence diagram showing the procedure for providing SOR-SNPN-SI and SOR-SNPN-SI-LS (if any) during registration. The diagram involves four lifelines: UE, AMF, UDM, and SOR-AF. The process starts with a REGISTRATION REQUEST from UE to AMF. The AMF initiates the registration procedure by sending a Nudm_UECM_Registration request to the UDM. The UDM checks for 'ME support of SOR-CMCI' and if the registration type is 'initial' or 'emergency', it deletes this indicator. The AMF then sends a REGISTRATION ACCEPT to the UE. The UDM makes a decision to send SOR information (3a), sends a Nsoraf_SoR_Get request to SOR-AF (3b), receives a response (3c), and secures the information (3d). The AMF sends a Nudm_SDM_Get response to the UDM (4) and a Nudm_SDM_Subscribe request (5). The AMF sends a REGISTRATION ACCEPT to the UE (6). The UE performs a steering of roaming information security check (7) and sends a REGISTRATION COMPLETE to the AMF. If the security check fails, the UE performs SNPN or PLMN selection and ends the procedure (8), sending a REGISTRATION COMPLETE to the AMF. The AMF sends a REGISTRATION COMPLETE to the UE (9) and a Nudm_SDM_Info request to the UDM (10). The UDM sends a Nsoraf_SoR_Info request to SOR-AF (10a). Finally, the UE performs SNPN or SNPN selection if a higher priority SNPN or PLMN is available (11).](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant UDM + participant SOR-AF + + Note right of UDM: Delete "ME support of SOR-CMCI" indicator if NAS registration type is either "initial" or "emergency" + + Note right of UDM: 3a. Decision to send SOR information, whether to request ACK from the UE, and how to obtain the SOR-SNPN-SI + + Note right of UDM: 3b. Nsoraf_SoR_Get request + + Note right of UDM: 3c. Nsoraf_SoR_Get response + + Note right of UDM: 3d. Securing information + + Note left of UE: 7. Steering of roaming information security check + + Note left of UE: 8. If the security check fails, then perform SNPN or PLMN selection procedure and end the procedure + + Note left of UE: 11. UE performs SNPN or SNPN selection procedure if higher priority SNPN or PLMN is available + + UE->>AMF: 1. REGISTRATION REQUEST + AMF->>UDM: 2. Registration procedure initiation Nudm_UECM_Registration request + UDM-->>AMF: Nudm_UECM_Registration response + AMF->>UE: REGISTRATION ACCEPT + AMF->>UDM: Nudm_SDM_Get request + UDM-->>AMF: 4. Nudm_SDM_Get response + AMF->>UDM: 5. Nudm_SDM_Subscribe request + AMF->>UE: 6. REGISTRATION ACCEPT + UE-->>AMF: REGISTRATION COMPLETE + AMF-->>UE: 9. REGISTRATION COMPLETE + AMF->>UDM: 10. Nudm_SDM_Info request + UDM->>SOR-AF: 10a. Nsoraf_SoR_Info request + +``` + +Sequence diagram showing the procedure for providing SOR-SNPN-SI and SOR-SNPN-SI-LS (if any) during registration. The diagram involves four lifelines: UE, AMF, UDM, and SOR-AF. The process starts with a REGISTRATION REQUEST from UE to AMF. The AMF initiates the registration procedure by sending a Nudm\_UECM\_Registration request to the UDM. The UDM checks for 'ME support of SOR-CMCI' and if the registration type is 'initial' or 'emergency', it deletes this indicator. The AMF then sends a REGISTRATION ACCEPT to the UE. The UDM makes a decision to send SOR information (3a), sends a Nsoraf\_SoR\_Get request to SOR-AF (3b), receives a response (3c), and secures the information (3d). The AMF sends a Nudm\_SDM\_Get response to the UDM (4) and a Nudm\_SDM\_Subscribe request (5). The AMF sends a REGISTRATION ACCEPT to the UE (6). The UE performs a steering of roaming information security check (7) and sends a REGISTRATION COMPLETE to the AMF. If the security check fails, the UE performs SNPN or PLMN selection and ends the procedure (8), sending a REGISTRATION COMPLETE to the AMF. The AMF sends a REGISTRATION COMPLETE to the UE (9) and a Nudm\_SDM\_Info request to the UDM (10). The UDM sends a Nsoraf\_SoR\_Info request to SOR-AF (10a). Finally, the UE performs SNPN or SNPN selection if a higher priority SNPN or PLMN is available (11). + +**Figure C.5.1: Procedure for providing SOR-SNPN-SI and SOR-SNPN-SI-LS (if any) during registration** + +For the steps below, security protection is described in 3GPP TS 33.501 [66]. + +- 1) The UE to the AMF: The UE initiates initial registration, emergency registration or registration procedure for mobility and periodic registration update (see 3GPP TS 24.501 [64]) to the AMF by sending REGISTRATION REQUEST message with the 5GS registration type IE indicating "initial registration", "emergency registration" or "mobility registration updating"; +- 2) Upon receiving the REGISTRATION REQUEST message, the AMF executes the registration procedure as defined in clause 4.2.2.2 of 3GPP TS 23.502 [63]. As part of the registration procedure: + - a) the AMF provides the registration type to the UDM using Nudm\_UECM\_Registration. As a consequence, in case of the 5GS registration type message indicates "initial registration" or "emergency registration" the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any, and the stored "ME support of SOR-SNPN-SI-LS" indicator, if any, in UDR using Nudr\_DM\_Update service operation (see 3GPP TS 23.502 [63]). + +NOTE 1: Nudr\_DM\_Update service operation corresponds to Nudr\_DR\_Update service operation (see 3GPP TS 29.504 [82] and 3GPP TS 29.505 [83]). + +In addition: + +- a) if the AMF does not have subscription data for the UE, the AMF invokes Nudm\_SDM\_Get service operation to the UDM to get amongst other information the Access and Mobility Subscription data for the UE (see step 14b in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); or +- b) if the AMF already has subscription data for the UE and: + - i) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "initial registration" and the "SoR Update Indicator for Initial Registration" field in the UE context is set to 'the UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type "initial registration"' as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]; or + - ii) the 5GS registration type IE in the received REGISTRATION REQUEST message indicates "emergency registration" and the "SoR Update Indicator for Emergency Registration" field in the UE context is set to 'the UDM requests the AMF to retrieve SoR information when the UE performs NAS registration type "emergency registration"' as specified in table 5.2.2.2.2-1 of 3GPP TS 23.502 [63]; + +then the AMF invokes Nudm\_SDM\_Get service operation message to the UDM to retrieve the steering of roaming information (see step 14b in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); + +otherwise the AMF sends a REGISTRATION ACCEPT message without the steering of roaming information to the UE and steps 3a, 3b, 3c, 3d, 4, 5, 6 are skipped; + +3a) If the user subscription information indicates to send the steering of roaming information due to initial registration in a non-subscribed SNPN, then the UDM shall store the "ME support of SOR-SNPN-SI" indicator and shall provide the steering of roaming information to the UE when the UE performs initial registration in a non-subscribed SNPN. Otherwise: + +- a) If the UE is registering on the subscribed SNPN and the UE has not indicated support for SOR-SNPN-SI in the REGISTRATION REQUEST message, the UDM shall delete the stored "ME support of SOR-SNPN-SI" indicator, if any, and shall not provide the SOR-SNPN-SI to the UE; and +- b) If: + - a) the UE is registering on the subscribed SNPN and the UE has indicated support for SOR-SNPN-SI in the REGISTRATION REQUEST message; or + - b) the UE is registering on a non-subscribed SNPN; + +the UDM shall store the "ME support of SOR-SNPN-SI" indicator and may provide the SOR-SNPN-SI to the UE based on the subscribed SNPN or HPLMN policy. + +If the UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a non-subscribed SNPN and the subscribed SNPN or HPLMN policy for the SOR-AF invocation is absent then steps 3b and 3c are not performed and the UDM obtains the available SOR-SNPN-SI (i.e. all retrieved from the UDR). In addition, if the UDM obtains the SOR-SNPN-SI and + +- the "ME support of SOR-CMCI" indicator is stored for the UE, then the UDM shall obtain the SOR-CMCI, if available, otherwise the UDM shall not obtain the SOR-CMCI. If the SOR-CMCI is provided then the UDM may indicate to the UE to store the SOR-CMCI in the ME by providing the "Store the SOR-CMCI in the ME" indicator; and +- the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, then the UDM shall obtain the SOR-SNPN-SI-LS, if available, otherwise the UDM shall not obtain the SOR-SNPN-SI-LS. + +If the UDM is to provide the steering of roaming information to the UE when the UE performs the registration in a non-subscribed SNPN and the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present, then the UDM obtains the SOR-SNPN-SI, SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, from the SOR-AF using steps 3b and 3c; + +- 3b) The UDM to the SOR-AF: Nsoraf\_SoR\_Get request (SNPN identity, SUPI of the UE, access type (see 3GPP TS 29.571 [72])). The SNPN identity and the access type parameters, indicating where the UE is registering, are stored in the UDM; +- 3c) The SOR-AF to the UDM: Nsoraf\_SoR\_Get response (the SOR-SNPN-SI, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and the SOR-SNPN-SI-LS, if any); + +Based on the information received in step 3b and any subscribed SNPN or HPLMN specific criteria, the SOR-AF may include the SOR-SNPN-SI, the SOR-CMCI, if any, optionally the "Store the SOR-CMCI in the ME" indicator, if any, and the SOR-SNPN-SI-LS, if any. + +If the SOR-AF includes the SOR-SNPN-SI and the ME supports: + +- the SOR-CMCI, the SOR-AF may provide the SOR-CMCI and optionally the "Store the SOR-CMCI in the ME" indicator, otherwise the SOR-AF shall provide neither the SOR-CMCI nor the "Store the SOR-CMCI in the ME" indicator; and +- the SOR-SNPN-SI-LS, the SOR-AF may provide the SOR-SNPN-SI-LS, otherwise the SOR-AF shall not provide SOR-SNPN-SI-LS. + +NOTE 1: In this version of the specification, when the access type where the UE is registering indicates 3GPP access, then the UE is registering over the NG-RAN access technology. + +NOTE 2: The SOR-AF can include a different SOR-SNPN-SI, different SOR-CMCI, if any, different "Store the SOR-CMCI in the ME" indicator, if any, and different SOR-SNPN-SI-LS, if any, for each Nsoraf\_SoR\_Get request even if the same SNPN identity, the SUPI of the UE, and the access type are provided to the SOR-AF. + +NOTE 3: The SOR-AF can subscribe to the UDM to be notified about the changes of the roaming status of the UE identified by SUPI. + +NOTE 4: The SOR-AF can determine that the ME supports the SOR-CMCI or the SOR-SNPN-SI-LS if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-CMCI" indicator or the "ME support of SOR-SNPN-SI-LS" indicator, respectively. + +- 3d) The UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from the SOR-SNPN-SI, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and SOR-SNPN-SI-LS, if any, obtained in step 3a or the SOR-SNPN-SI, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and SOR-SNPN-SI-LS, if any, obtained in step 3c. + +If: + +- the SOR-SNPN-SI was not obtained in steps 3a or 3c; or +- the SOR-AF has not sent to the UDM an Nsoraf\_SoR\_Get response (step 3c) within an operator defined time after the UDM sending to the SOR-AF an Nsoraf\_SoR\_Get request (step 3b); + +NOTE 5: Stage 3 to define the timer needed for the SOR-AF to respond to the UDM. The max time needs to be defined considering that this procedure is part of the registration procedure. + +and the UE is performing initial registration in a non-subscribed SNPN and the user subscription information indicates to send the steering of roaming information due to initial registration in a non-subscribed SNPN, then the UDM forms the steering of roaming information as specified in 3GPP TS 33.501 [66] from the subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'; + +- 4) The UDM to the AMF: The UDM sends a response to the Nudm\_SDM\_Get service operation to the AMF, which includes the steering of roaming information within the Access and Mobility Subscription data. The Access and Mobility Subscription data type is defined in clause 5.2.3.3.1 of 3GPP TS 23.502 [63]). + +NOTE 6: The UDM cannot provide the SOR-SNPN-SI, the SOR-CMCI, if any, or the SOR-SNPN-SI-LS to the AMF which does not support receiving SOR transparent container (see 3GPP TS 29.503 [78]). + +If the UE is performing initial registration or emergency registration and the UDM supports SOR-CMCI or SOR-SNPN-SI-LS, the subscribed SNPN or HPLMN shall request the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering + +of roaming information in the Nudm\_SDM\_Get response service operation. Otherwise, the subscribed SNPN or HPLMN may request the UE to acknowledge the successful security check of the received steering of roaming information, by providing the indication as part of the steering of roaming information in the Nudm\_SDM\_Get response service operation; + +- 5) The AMF to the UDM: As part of the registration procedure, the SNPN also invokes Nudm\_SDM\_Subscribe service operation to the UDM to subscribe to notification of changes of the subscription data (e.g. received in step 4) including notification of updates of the steering of roaming information included in the Access and Mobility Subscription data (see step 14c in clause 4.2.2.2.2 of 3GPP TS 23.502 [63]); +- 6) The AMF to the UE: The AMF shall transparently send the received steering of roaming information to the UE in the REGISTRATION ACCEPT message; +- 7) If the steering of roaming information is received and the security check is successful, then: + - a) if the UDM has not requested an acknowledgement from the UE, then the UE shall send the REGISTRATION COMPLETE message to the serving AMF without including an SOR transparent container; and + - b) if the steering of roaming information contains the SOR-SNPN-SI, the ME shall replace the credentials holder controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of preferred SNPNs, if any, and the ME shall replace the credentials holder controlled prioritized list of GINs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of GINs, if any, and delete the SNPNs identified by the credentials holder controlled prioritized list of preferred SNPNs or the SNPN(s) stored along with GIN(s) identified by the credentials holder controlled prioritized list of GINs from the list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs", if they are present in these lists. If the SOR information contains the SOR-SNPN-SI-LS, the ME shall replace the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", if any, and the ME shall replace the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", if any, and delete the SNPNs identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or the SNPN(s) stored along with GIN(s) identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" and the list of "permanently forbidden SNPNs for access for localized services in SNPN", if they are present in these lists. Additionally, the UE may perform SNPN selection. + - i) if the UE has a list of available and allowable SNPN in the area and based on this list or any other implementation specific means the UE determines that there is a higher priority SNPN than the selected SNPN; or + - ii) the UE does not have a list of available and allowable SNPN in the area and is unable to determine whether there is a higher priority SNPN than the selected SNPN using any other implementation specific means; + +and the UE is in automatic network selection mode: + +- A) if the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE shall apply the actions in clause C.4.2. In this case steps 8 to 11 are skipped; +- B) otherwise, the UE shall: + - i) release the current N1 NAS signalling connection locally and then attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3. In this case, steps 8 to 11 are skipped. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. The UE shall not initiate the establishment of a new N1 signalling connection, unless for the purpose of initiating a registration procedure for emergency services or establishing an emergency PDU session, until the attempts to obtain service on a higher priority SNPN are completed. If the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]), the receipt of the steering of roaming + +information shall not trigger the release of the N1 NAS signalling connection. The UE shall release the current N1 NAS signalling connection locally subsequently after the emergency PDU session is released. If the UE needs to disable the N1 mode capability (see 3GPP TS 24.501 [64]) and there is no emergency service pending, the UE shall first attempt to obtain service on a higher priority SNPN as described in this step, and if no higher priority SNPN can be selected but the last registered SNPN is selected, then the UE shall disable the N1 mode capability; or + +- ii) not release the current N1 NAS signalling connection locally (e.g. if the UE has established PDU session(s)) and skip steps 8 to 10; + +NOTE 7: When the UE is in the manual mode of operation or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on the current chosen non-subscribed SNPN. + +- 8) If the UE's ME is configured with an indication that the UE is to receive the steering of roaming information due to initial registration in a non-subscribed SNPN, but neither the SOR-SNPN-SI nor the subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided' is received in the REGISTRATION ACCEPT message, when the UE performs initial registration in a VPLMN or if the steering of roaming information is received but the security check is not successful, then the UE shall: + +- a) if the SOR transparent container is included in the REGISTRATION ACCEPT message, send the REGISTRATION COMPLETE message to the serving AMF without including an SOR transparent container; +- b) if the current chosen non-subscribed SNPN is not contained in the list of "SNPNs where registration was aborted due to SOR" for the selected entry in the "list of subscriber data" or the selected PLMN subscription, and is not part of the user controlled prioritized list of preferred SNPNs for the selected entry in the "list of subscriber data" or the selected PLMN subscription, and the UE is not in manual mode of operation, release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority, and skip steps 9 to 11. The UE shall suspend the transmission of 5GSM messages until the N1 NAS signalling is released. If the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]), the UE shall release the current N1 NAS signalling connection locally after the release of the emergency PDU session. If the UE needs to disable the N1 mode capability (see 3GPP TS 24.501 [64]) and there is no emergency service pending, the UE shall first attempt to obtain service on a higher priority SNPN as described in this step, and if no higher priority SNPN can be selected but the last registered SNPN is selected, then the UE shall disable the N1 mode capability; and +- c) if the current chosen non-subscribed SNPN is not contained in the list of "SNPNs where registration was aborted due to SOR" for the selected entry in the "list of subscriber data" or the selected PLMN subscription, store the SNPN identity in the list of "SNPNs where registration was aborted due to SOR" for the selected entry in the "list of subscriber data" or the selected PLMN subscription; + +NOTE 8: When the UE is in the manual mode of operation or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on the current chosen non-subscribed SNPN. + +- 9) The UE to the AMF: If the UDM has requested an acknowledgement from the UE and the UE verified that the steering of roaming information has been provided by the subscribed SNPN or HPLMN in step 7, then: + +- a) the UE sends the REGISTRATION COMPLETE message to the serving AMF with an SOR transparent container including the UE acknowledgement; +- b) the UE shall set the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container to "supported"; +- b1) if the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall set the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container to "supported"; and +- c) if: + +- 1) the steering of roaming information contains the SOR-SNPN-SI, the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE is in automatic network selection mode and the UE decides to perform SNPN selection, then the UE shall apply the actions in clause C.4.2, and step 11 is skipped; or + - 2) the steering of roaming information contains subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided', then step 11 is skipped; +- 10) The AMF to the UDM: If an SOR transparent container is received in the REGISTRATION COMPLETE message, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. If the subscribed SNPN or HPLMN decided that the UE is to acknowledge the successful security check of the received steering of roaming information in step 4, the UDM verifies that the acknowledgement is provided by the UE as specified in 3GPP TS 33.501 [66]. If: +- the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any; and + - the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any + +NOTE 9: The UDM cannot receive the "ME support of SOR-CMCI" indicator or the "ME support of SOR-SNPN-SI-LS" indicator from the AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). + +10a) The UDM to the SOR-AF: Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery, "ME support of SOR-CMCI" indicator, if any, "ME support of SOR-SNPN-SI-LS" indicator, if any). If the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present and the UDM received and verified the UE acknowledgement in step 10, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI to the UE. If: + +- the "ME support of SOR-CMCI" indicator is stored for the UE, the UDM shall include the "ME support of SOR-CMCI" indicator; and +- the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator; and + +11) If the UE has a list of available SNPNs in the area and based on this list the UE determines that there is a higher priority SNPN than the selected SNPN and the UE is in automatic network selection mode, then the UE may attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3 after the release of the N1 NAS signalling connection. If within an implementation dependent time the N1 NAS signalling connection is not released, then the UE may locally release the N1 signalling connection except when the UE has an established emergency PDU session (see 3GPP TS 24.501 [64]). + +When the UE performs initial registration for emergency services (see 3GPP TS 24.501 [64] and 3GPP TS 23.502 [63]) and the AMF performs the authentication procedure, then based on subscribed SNPN or HPLMN policy, the SOR procedure described in this clause may apply. + +If: + +- the UE in manual mode of operation encounters scenario mentioned in step 8 above; and +- upon switching to automatic network selection mode, the UE remembers that it is still registered on the where the security check failure of SOR information was encountered as described in step 8; + +the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the UE has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection subsequently after the emergency PDU session is released. + +NOTE 10: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. + +NOTE 11: The list of available and allowable SNPNs in the area is implementation specific. + +## C.6 Stage-2 flow for steering of UE in SNPN after registration + +The stage-2 flow for the steering of UE in SNPN after registration is indicated in figure C.6.1. The UE is registered on an SNPN which can be the subscribed SNPN or a non-subscribed SNPN. The AMF is located in the selected SNPN. The UDM is located in the HPLMN or subscribed SNPN. + +The procedure is triggered if: + +- a) the UDM supports obtaining SOR-SNPN-SI, if any, SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, from the SOR-AF, the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present in the UDM, and the SOR-AF provides the UDM with: + - the SOR-SNPN-SI for a UE identified by SUPI if the ME supports SOR-SNPN-SI; + - the SOR-CMCI for a UE identified by SUPI if the ME supports SOR-CMCI; or + - the SOR-SNPN-SI-LS for a UE identified by SUPI if the ME supports SOR-SNPN-SI-LS; or + +NOTE 0: The SOR-AF can determine that the ME supports SOR-SNPN-SI if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-SNPN-SI" indicator. The UDM determines that the ME supports SOR-SNPN-SI if the UDM stores "ME support of SOR-SNPN-SI" indicator. + +NOTE 1: The SOR-AF can determine that the ME supports the SOR-CMCI if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-CMCI" indicator. How the SOR-AF determines that the USIM for the indicated SUPI supports SOR-CMCI is implementation specific. + +NOTE 1a: The SOR-AF can determine that the ME supports SOR-SNPN-SI-LS if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-SNPN-SI-LS" indicator. The UDM determines that the ME supports SOR-SNPN-SI-LS. + +- b) a SOR-SNPN-SI (if supported by ME), a SOR-CMCI (if supported by ME), or a SOR-SNPN-SI-LS (if supported by ME) becomes available in the UDM (i.e. retrieved from the UDR). + +NOTE 2: Before providing the UDM with SOR-SNPN-SI for a UE identified by SUPI, the SOR-AF, based on subscribed SNPN or HPLMN policies or criteria, can obtain the user location information by triggering the unified location service exposure procedure as defined in 3GPP TS 23.273 [70] clause 6.5, or additionally based on implementation specific criteria, by requesting the UE location information from other application function using implementation specific method. This user location information can then be used in the SOR-AF algorithms. + +NOTE 3: Before providing the UDM with a new SOR-SNPN-SI for a UE identified by SUPI, the SOR-AF, based on subscribed SNPN or HPLMN policies or criteria, can obtain the user location information by triggering the unified location service exposure procedure as defined in 3GPP TS 23.273 [70] clause 6.5, or additionally based on implementation specific criteria, by requesting the UE location information from other application function using implementation specific method. This user location information can then be used in the SOR-AF algorithms. + +![Sequence diagram illustrating the procedure for providing SOR-SNPN-SI (if any) and SOR-SNPN-SI-LS (if any) after registration. The diagram shows interactions between UE, AMF, UDM, and SOR-AF. The sequence is: 1. SOR-AF to UDM: Nudm_ParameterProvision_Update request; 2. UDM to AMF: Nudm_SDM_Notification request; 3. AMF to UE: DL NAS Transport; 4. UE performs steering of roaming information security check; 5. UE to AMF: UL NAS Transport; 6. AMF to UDM: Nudm_SDM_Info request; 7. UDM to SOR-AF: Nsoraf_SoR_Info request.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +``` + +sequenceDiagram + participant SOR-AF + participant UDM + participant AMF + participant UE + Note right of SOR-AF: 1. Nudm_ParameterProvision_Update request + SOR-AF-->>UDM: 1. Nudm_ParameterProvision_Update request + Note right of UDM: 2. Nudm_SDM_Notification request + UDM-->>AMF: 2. Nudm_SDM_Notification request + Note right of AMF: 3. DL NAS Transport + AMF-->>UE: 3. DL NAS Transport + Note left of UE: 4. Steering of roaming information security check + Note right of UE: UL NAS Transport + UE-->>AMF: UL NAS Transport + Note right of AMF: 5. Nudm_SDM_Info request + AMF-->>UDM: 5. Nudm_SDM_Info request + Note right of UDM: 6. Nsoraf_SoR_Info request + UDM-->>SOR-AF: 6. Nsoraf_SoR_Info request + +``` + +Sequence diagram illustrating the procedure for providing SOR-SNPN-SI (if any) and SOR-SNPN-SI-LS (if any) after registration. The diagram shows interactions between UE, AMF, UDM, and SOR-AF. The sequence is: 1. SOR-AF to UDM: Nudm\_ParameterProvision\_Update request; 2. UDM to AMF: Nudm\_SDM\_Notification request; 3. AMF to UE: DL NAS Transport; 4. UE performs steering of roaming information security check; 5. UE to AMF: UL NAS Transport; 6. AMF to UDM: Nudm\_SDM\_Info request; 7. UDM to SOR-AF: Nsoraf\_SoR\_Info request. + +**Figure C.6.1: Procedure for providing SOR-SNPN-SI (if any) and SOR-SNPN-SI-LS (if any) after registration** + +For the steps below, security protection is described in 3GPP TS 33.501 [66]. + +- 1) The SOR-AF to the UDM: Nudm\_ParameterProvision\_Update request is sent to the UDM to trigger the update of the UE with the SOR-SNPN-SI, if any, the SOR-CMCI, if any, the "Store the SOR-CMCI in the ME" indicator, if any, and the SOR-SNPN-SI-LS, if any, for a UE identified by SUPI. +- 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm\_SDM\_Notification service operation. The Nudm\_SDM\_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the subscribed SNPN or HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm\_SDM\_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. If the SOR-SNPN-SI was obtained, the UDM shall include the SOR-SNPN-SI in to the SOR information. If the SOR-CMCI was obtained, the UDM shall include the SOR-CMCI into the steering of roaming information and shall requests an acknowledgement from the UE as part of the steering of roaming information. If the "Store the SOR-CMCI in the ME" indicator was obtained, the UDM shall include the "Store the SOR-CMCI in the ME" indicator If the SOR-SNPN-SI-LS was obtained, the UDM shall include the SOR-SNPN-SI-LS into the SOR information; + +NOTE 4: The UDM cannot provide the SOR-SNPN-SI SOR-CMCI, or SOR-SNPN-SI-LS to the AMF which does not support receiving SOR transparent container (see 3GPP TS 29.503 [78]). + +- 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. +- 4) Upon receiving the steering of roaming information, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by the subscribed SNPN or HPLMN, and + +- i) if the security check is successful, then: + - a) if the steering of roaming information contains the SOR-SNPN-SI, the ME shall replace the credentials holder controlled prioritized list of preferred SNPNs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of preferred SNPNs, if any, the ME shall replace the credentials holder controlled prioritized list of GINs for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received credentials holder controlled prioritized list of GINs, if any, and the ME shall delete the SNPNs identified by the credentials holder controlled prioritized list of preferred SNPNs or the SNPN(s) stored along with GIN(s) identified by the credentials holder controlled prioritized list of GINs from the list of "temporarily + +forbidden SNPNs" and the list of "permanently forbidden SNPNs", if they are present in these lists. If the SOR information contains the SOR-SNPN-SI-LS, the ME shall replace the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", if any, and the ME shall replace the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" for the selected entry of the "list of subscriber data" or the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", if any, and delete the SNPNs identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or the SNPN(s) stored along with GIN(s) identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" and the list of "permanently forbidden SNPNs for access for localized services in SNPN", if they are present in these lists; + +- b) if the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set: + - the "ME support of SOR-CMCI" indicator to "supported"; and + - the "ME support of SOR-SNPN-SI-LS" indicator to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN. +- c) if the UE is in automatic network selection mode, the selected SNPN is a non-subscribed SNPN and the UE decides to perform SNPN selection, then: + - if the UE is configured with the SOR-CMCI or received the SOR-CMCI over N1 NAS signalling, the UE shall apply the actions in clause C.4; or + - the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3. +- d) if the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session then the UE may attempt to perform the SNPN selection subsequently after the emergency PDU session is released, if the UE is in automatic network selection mode. +- e) if the UDM has not requested an acknowledgement from the UE, then steps 4 is skipped; and + +ii) the security check is not successful: + +- a) step 5 is skipped; and +- b) if the selected SNPN is a non-subscribed SNPN and the UE is in automatic network selection mode, then: + - A) if the UE has a stored SOR-CMCI, then: + - if there are ongoing PDU sessions or services, the UE shall apply the actions in clause C.4.2, and the current SNPN is considered as lowest priority; or + - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority; + - B) if the UE does not have a stored SOR-CMCI, then: + - if there are ongoing PDU sessions or services, the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. If the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released; or + +- if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. + +NOTE 5: When the UE is in the manual mode of operation and the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on the current chosen non-subscribed SNPN. + +- 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. If the subscribed SNPN or HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information in step 1, the UDM verifies that the acknowledgement is provided by the UE. If: + - the "ME support of SOR-CMCI" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-CMCI" indicator, otherwise the UDM shall delete the stored "ME support of SOR-CMCI" indicator, if any; and + - the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any. + +If the present flow was invoked by the UDM after receiving from the SOR-AF the SOR-SNPN-SI, if any, SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, for a UE identified by SUPI using an Nudm\_ParameterProvision\_Update request, and the UDM verification of the UE acknowledgement is successful, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI, if any, SOR-CMCI, if any, and SOR-SNPN-SI-LS, if any, using Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery); and + +- 6) The UDM to the SOR-AF: Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery, "ME support of SOR-CMCI" indicator, if any, "ME support of SOR-SNPN-SI-LS" indicator, if any). If the subscribed SNPN or HPLMN policy for the SOR-AF invocation is present and the UDM received and verified the UE acknowledgement in step 5, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI, if any, SOR-CMCI, if any, SOR-SNPN-SI-LS, if any, to the UE. If: + - the "ME support of SOR-CMCI" indicator is stored for the UE, the UDM shall include the "ME support of SOR-CMCI" indicator; and + - the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator. + +If the selected SNPN is a non-subscribed SNPN and: + +- the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and +- upon switching to automatic network selection mode, the UE remembers that it is still registered on the where the security check failure of SOR information was encountered; + +the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the selected SNPN is a non-subscribed SNPN and the UE has an established emergency PDU session, then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released. + +NOTE 6: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. + +NOTE 7: If the selected SNPN is the subscribed SNPN, regardless of whether the UE is in automatic network selection mode or manual network selection mode, regardless of whether the UE has an established emergency PDU session or not, and regardless of whether the security check is successful or not successful, the UE is not required to perform the SNPN selection. + +## C.7 Stage-2 flow for providing UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in HPLMN or VPLMN after registration + +The stage-2 flow for providing UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in HPLMN or VPLMN after registration is indicated in figure C.7.1, when the ME and the HPLMN support the SOR-SNPN-SI or SOR-SNPN-SI-LS, respectively. The selected PLMN can be the HPLMN or a VPLMN. The AMF is located in the selected PLMN. The UDM is located in the HPLMN. + +In this procedure, the SOR-SNPN-SI or SOR-SNPN-SI-LS is sent without the list of preferred PLMN/access technology combinations. + +NOTE 1: The SOR-AF can determine that the ME supports the SOR-SNPN-SI or SOR-SNPN-SI-LS if the Nsoraf\_SoR\_Info service operation has returned the "ME support of SOR-SNPN-SI" indicator or "ME support of SOR-SNPN-SI-LS" indicator, respectively. The UDM can determine that the ME supports the SOR-SNPN-SI or SOR-SNPN-SI-LS if the "ME support of SOR-SNPN-SI" indicator or "ME support of SOR-SNPN-SI-LS" indicator, respectively, is stored for the UE. + +The procedure is triggered if: + +- a) the UDM supports obtaining the SOR-SNPN-SI or SOR-SNPN-SI-LS from the SOR-AF, the HPLMN policy for the SOR-AF invocation is present in the UDM, and the SOR-AF provides the UDM with the SOR-SNPN-SI or the SOR-SNPN-SI-LS for a UE identified by SUPI; or +- b) the SOR-SNPN-SI or the SOR-SNPN-SI-LS becomes available in the UDM (i.e., retrieved from the UDR). + +![Sequence diagram showing the procedure for configuring UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in a PLMN after registration. The diagram involves four main entities: UE, AMF, UDM, and SOR-AF (dashed box). The sequence of messages is: 1. SOR-AF to UDM: Nudm_ParameterProvision_Update request; 2. UDM to AMF: Nudm_SDM_Notification request; 3. AMF to UE: DL NAS Transport; 4. UE internal process: Steering of roaming information security check; 5. UE to AMF: UL NAS Transport; 6. AMF to UDM: Nudm_SDM_Info request; 7. UDM to SOR-AF: Nsoraf_SoR_Info request.](7c4726a694799239785f7869a6947472_img.jpg) + +``` + +sequenceDiagram + participant SOR-AF as SOR-AF (dashed) + participant UDM as UDM + participant AMF as AMF + participant UE as UE + + Note right of SOR-AF: 1. Nudm_ParameterProvision_Update request + SOR-AF-->>UDM: 1. Nudm_ParameterProvision_Update request + Note right of UDM: 2. Nudm_SDM_Notification request + UDM-->>AMF: 2. Nudm_SDM_Notification request + Note right of AMF: 3. DL NAS Transport + AMF-->>UE: 3. DL NAS Transport + Note left of UE: 4. Steering of roaming information security check + Note left of UE: UL NAS Transport + UE-->>AMF: UL NAS Transport + Note right of AMF: 5. Nudm_SDM_Info request + AMF-->>UDM: 5. Nudm_SDM_Info request + Note right of UDM: 6. Nsoraf_SoR_Info request + UDM-->>SOR-AF: 6. Nsoraf_SoR_Info request + +``` + +Sequence diagram showing the procedure for configuring UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in a PLMN after registration. The diagram involves four main entities: UE, AMF, UDM, and SOR-AF (dashed box). The sequence of messages is: 1. SOR-AF to UDM: Nudm\_ParameterProvision\_Update request; 2. UDM to AMF: Nudm\_SDM\_Notification request; 3. AMF to UE: DL NAS Transport; 4. UE internal process: Steering of roaming information security check; 5. UE to AMF: UL NAS Transport; 6. AMF to UDM: Nudm\_SDM\_Info request; 7. UDM to SOR-AF: Nsoraf\_SoR\_Info request. + +**Figure C.7.1: Procedure for configuring UE with SOR-SNPN-SI or SOR-SNPN-SI-LS in a PLMN after registration** + +For the steps below, security protection is described in 3GPP TS 33.501 [66]. + +- 1) The SOR-AF to the UDM: Nudm\_ParameterProvision\_Update request is sent to the UDM to trigger the update of the UE with the SOR-SNPN-SI or SOR-SNPN-SI-LS. +- 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm\_SDM\_Notification service operation. The Nudm\_SDM\_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the + +Access and Mobility Subscription data. If the HPLMN or subscribed SNPN decided that the UE is to acknowledge successful security check of the received steering of roaming information, the Nudm\_SDM\_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. Upon receiving the SOR-SNPN-SI or the SOR-SNPN-SI-LS, the UDM shall include the SOR-SNPN-SI (if any), SOR-SNPN-SI-LS (if any), and the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'. + +NOTE 2: The UDM cannot provide the SOR-SNPN-SI, or the SOR-SNPN-SI-LS to the AMF which does not support receiving SoR transparent container (see 3GPP TS 29.503 [78]). + +- 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. +- 4) Upon receiving the steering of roaming information containing the SOR-SNPN-SI (if any), the SOR-SNPN-SI-LS (if any), and the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided', the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN, and: + +- a) if the security check is successful, then: + - the ME shall replace the credentials holder controlled prioritized list of preferred SNPNs for the selected PLMN subscription with the received credentials holder controlled prioritized list of preferred SNPNs, if any, the ME shall replace the credentials holder controlled prioritized list of GINs for the selected PLMN subscription with the received credentials holder controlled prioritized list of GINs, if any, and the ME shall delete the SNPNs identified by the credentials holder controlled prioritized list of preferred SNPNs or the SNPN(s) stored along with GIN(s) identified by the credentials holder controlled prioritized list of GINs from the list of "temporarily forbidden SNPNs" and the list of "permanently forbidden SNPNs", if they are present in these lists; and + - the ME shall replace the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" for the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN", if any, the ME shall replace the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" for the selected PLMN subscription with the received "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN", if any, and the ME shall delete the SNPNs identified by the "credentials holder controlled prioritized list of preferred SNPNs for access for localized services in SNPN" or the SNPN(s) stored along with GIN(s) identified by the "credentials holder controlled prioritized list of preferred GINs for access for localized services in SNPN" from the list of "temporarily forbidden SNPNs for access for localized services in SNPN" and the list of "permanently forbidden SNPNs for access for localized services in SNPN", if they are present in these lists. + +If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set: + +- the "ME support of SOR-SNPN-SI" indicator to "supported"; and +- the "ME support of SOR-SNPN-SI-LS" indicator to "supported" if the UE supports access to an SNPN providing access for localized services in SNPN. + +If the UDM has not requested an acknowledgement from the UE then step 5 is skipped; and + +- b) if the selected PLMN is a VPLMN, the security check is not successful and the UE is in automatic network, then + - if the UE has a stored SOR-CMCI, then: + - if there are ongoing PDU sessions or services, the current PLMN is considered as lowest priority and the UE shall apply the actions in clause C.4.2; + +- if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority PLMN as specified in clause 4.9.3, with an exception that the current PLMN is considered as lowest priority; +- if the UE does not have a SOR-CMCI stored in the non-volatile memory of the ME, then: + - if there are ongoing PDU sessions or services, the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3 by acting as if timer T that controls periodic attempts has expired, with an exception that the current PLMN is considered as lowest priority. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); or + - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority PLMN as specified in clause 4.9.3, with an exception that the current PLMN is considered as lowest priority. + +Step 5 is skipped; + +NOTE 3: When the UE is in the manual mode of operation or the current chosen VPLMN is part of the "User Controlled PLMN Selector with Access Technology" list, the UE stays on the VPLMN. + +- 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. If the HPLMN decided that the UE is to acknowledge successful security check of the received steering of roaming information in step 2, the UDM verifies that the acknowledgement is provided by the UE. The UDM shall store the "ME support of SOR-SNPN-SI" indicator. If the "ME support of SOR-SNPN-SI-LS" indicator in the header of the SOR transparent container is set to "supported", then the UDM shall store the "ME support of SOR-SNPN-SI-LS" indicator, otherwise the UDM shall delete the stored "ME support of SOR-SNPN-SI-LS" indicator, if any. + +If the present flow was invoked by the UDM after receiving from the SOR-AF the SOR-SNPN-SI or the SOR-SNPN-SI-LS for a UE identified by SUPI using an Nudm\_ParameterProvision\_Update request, and the UDM verification of the UE acknowledgement is successful, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI or the SOR-SNPN-SI-LS using Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery); and + +- 6) The UDM to the SOR-AF: Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery, "ME support of SOR-SNPN-SI" indicator, "ME support of SOR-SNPN-SI-LS" indicator, if any). If the HPLMN policy for the SOR-AF invocation is present and the HPLMN UDM received and verified the UE acknowledgement in step 5, then the UDM informs the SOR-AF about successful delivery of the SOR-SNPN-SI or the SOR-SNPN-SI-LS to the UE. The UDM shall include the "ME support of SOR-SNPN-SI" indicator. If the "ME support of SOR-SNPN-SI-LS" indicator is stored for the UE, the UDM shall include the "ME support of SOR-SNPN-SI-LS" indicator. + +If the selected PLMN is a VPLMN and: + +- the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and +- upon switching to automatic network selection mode the UE remembers that it is still registered on the PLMN where the security check failure of SOR information was encountered; + +the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority PLMN as specified in clause 4.4.3.3, by acting as if timer T that controls periodic attempts has expired, with an exception that the current registered PLMN is considered as lowest priority. If the selected PLMN is a VPLMN and the UE has an established emergency PDU session then the UE shall attempt to perform the PLMN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). + +NOTE 4: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. + +## C.8 Stage-2 flow for providing UE with list of preferred PLMN/access technology combinations in SNPN after registration + +The stage-2 flow for providing UE with the list of preferred PLMN/access technology combinations in an SNPN after registration is indicated in figure C.8.1. The selected SNPN is a non-subscribed SNPN. The AMF is located in the selected SNPN. The UDM is located in the HPLMN. + +In this procedure, the list of preferred PLMN/access technology combinations is sent in plain text or sent within the secured packet, without the SOR-SNPN-SI. + +Based on HPLMN policy, if the HPLMN supports sending the list of preferred PLMN/access technology combinations in plain text or secured packet to the UE when the UE is registered to an SNPN, then the procedure is triggered: + +- If the UDM supports obtaining a list of preferred PLMN/access technology combinations or a secured packet from the SOR-AF, the HPLMN policy for the SOR-AF invocation is present in the UDM and the SOR-AF provides the UDM with a new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI; or +- When a new list of preferred PLMN/access technology combinations or a secured packet becomes available in the UDM (i.e., retrieved from the UDR). + +![Sequence diagram showing the procedure for configuring UE with list of preferred PLMN/access technology combinations in an SNPN after registration. The diagram involves four entities: UE, AMF, UDM, and SOR-AF. The sequence of messages is: 1. SOR-AF to UDM: Nudm_ParameterProvision_Update request; 2. UDM to AMF: Nudm_SDM_Notification request; 3. AMF to UE: DL NAS Transport; 4. UE internal: Steering of roaming information security check; 5. AMF to UDM: Nudm_SDM_Info request; 6. UDM to SOR-AF: Nsoraf_SoR_Info request. A dashed box labeled 'UL NAS Transport' is shown between the UE and AMF.](e684118e43323b2c210c8dbc975db92a_img.jpg) + +``` + +sequenceDiagram + participant SOR-AF + participant UDM + participant AMF + participant UE + + Note right of SOR-AF: 1. Nudm_ParameterProvision_Update request + SOR-AF-->>UDM: 1. Nudm_ParameterProvision_Update request + Note right of UDM: 2. Nudm_SDM_Notification request + UDM-->>AMF: 2. Nudm_SDM_Notification request + Note right of AMF: 3. DL NAS Transport + AMF-->>UE: 3. DL NAS Transport + Note left of UE: 4. Steering of roaming information security check + UE-->>AMF: UL NAS Transport + Note right of AMF: 5. Nudm_SDM_Info request + AMF-->>UDM: 5. Nudm_SDM_Info request + Note right of UDM: 6. Nsoraf_SoR_Info request + UDM-->>SOR-AF: 6. Nsoraf_SoR_Info request + +``` + +Sequence diagram showing the procedure for configuring UE with list of preferred PLMN/access technology combinations in an SNPN after registration. The diagram involves four entities: UE, AMF, UDM, and SOR-AF. The sequence of messages is: 1. SOR-AF to UDM: Nudm\_ParameterProvision\_Update request; 2. UDM to AMF: Nudm\_SDM\_Notification request; 3. AMF to UE: DL NAS Transport; 4. UE internal: Steering of roaming information security check; 5. AMF to UDM: Nudm\_SDM\_Info request; 6. UDM to SOR-AF: Nsoraf\_SoR\_Info request. A dashed box labeled 'UL NAS Transport' is shown between the UE and AMF. + +**Figure C.8.1: Procedure for configuring UE with list of preferred PLMN/access technology combinations in an SNPN after registration** + +For the steps below, security protection is described in 3GPP TS 33.501 [66]. + +- 1) The SOR-AF to the UDM: Nudm\_ParameterProvision\_Update request is sent to the UDM to trigger the update of the UE with the new list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI. +- 2) The UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm\_SDM\_Notification service operation. The Nudm\_SDM\_Notification service operation contains the steering of roaming information that needs to be delivered transparently to the UE over NAS within the Access and Mobility Subscription data. If the HPLMN or subscribed SNPN decided that the UE is to + +acknowledge successful security check of the received steering of roaming information, the Nudm\_SDM\_Notification service operation also contains an indication that the UDM requests an acknowledgement from the UE as part of the steering of roaming information. + +- 3) The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. +- 4) Upon receiving the steering of roaming information, the UE shall perform a security check on the steering of roaming information included in the DL NAS TRANSPORT message to verify that the steering of roaming information is provided by HPLMN, and: + - a) if the security check is successful: + - if the steering of roaming information contains a secured packet (see 3GPP TS 31.115 [67]) and the service "data download via SMS Point-to-point" is allocated and activated in the USIM Service Table (see 3GPP TS 31.102 [40]), the ME shall upload the secured packet to the USIM using procedures in 3GPP TS 31.111 [41]; and + - if the steering of roaming information contains the list of preferred PLMN/access technology combinations, the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME with the received list of preferred PLMN/access technology combinations, and delete the PLMNs identified by the list of preferred PLMN/access technology combinations from the Forbidden PLMN list and from the Forbidden PLMNs for GPRS service list, if they are present in these lists. + +If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement and the UE shall set the "ME support of SOR-SNPN-SI" indicator to "supported". + +If the UDM has not requested an acknowledgement from the UE then step 5 is skipped; and + +- b) if the security check is not successful and the UE is in automatic network selection mode, then: + - if the UE has a stored SOR-CMCI, then: + - if there are ongoing PDU sessions or services, the current SNPN is considered as lowest priority and the UE shall apply the actions in clause C.4.2; + - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority; + - if the UE does not have a SOR-CMCI stored in the non-volatile memory of the ME, then: + - if there are ongoing PDU sessions or services, the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. If the UE has an established emergency PDU session then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]); or + - if there are no ongoing PDU sessions or services, the UE shall release the current N1 NAS signalling connection locally and attempt to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current SNPN is considered as lowest priority. + +Step 5 is skipped; + +NOTE 1: When the UE is in the manual mode of operation or the current chosen non-subscribed SNPN is part of the user controlled prioritized list of preferred SNPNs, the UE stays on current chosen non-subscribed SNPN. + +- 5) The AMF to the UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. If the HPLMN decided that the UE is to acknowledge successful security check of the received steering + +of roaming information in step 2, the UDM verifies that the acknowledgement is provided by the UE. The UDM shall store the "ME support of SOR-SNPN-SI" indicator. + +If the present flow was invoked by the UDM after receiving from the SOR-AF a list of preferred PLMN/access technology combinations or a secured packet for a UE identified by SUPI using an Nudm\_ParameterProvision\_Update request, and the UDM verification of the UE acknowledgement is successful, then the UDM informs the SOR-AF about successful delivery of the steering of roaming information using Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery); and + +- 6) The UDM to the SOR-AF: Nsoraf\_SoR\_Info (SUPI of the UE, successful delivery, "ME support of SOR-SNPN-SI" indicator). If the HPLMN policy for the SOR-AF invocation is present and the HPLMN UDM received and verified the UE acknowledgement in step 5, then the UDM informs the SOR-AF about successful delivery of the steering of roaming information to the UE. The UDM shall include the "ME support of SOR-SNPN-SI" indicator. + +If: + +- the UE in manual mode of operation encounters security check failure of SOR information in DL NAS TRANSPORT message; and +- upon switching to automatic network selection mode the UE remembers that it is still registered on non-subscribed SNPN where the security check failure of SOR information was encountered; + +the UE shall wait until it moves to idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]) before attempting to obtain service on a higher priority SNPN as specified in clause 4.9.3, with an exception that the current registered SNPN is considered as lowest priority. If the UE has an established emergency PDU session then the UE shall attempt to perform the SNPN selection after the emergency PDU session is released and after the UE enters idle mode or 5GMM-CONNECTED mode with RRC inactive indication (see 3GPP TS 24.501 [64]). + +NOTE 2: The receipt of the steering of roaming information by itself does not trigger the release of the emergency PDU session. + +# --- Annex D (informative): Change history + +| TSG# | Tdoc | SPEC | VERS | CR | REV | PHASE | CAT | N_VER | SUBJECT | comment | +|-------|-------------------------|--------|-------|-----|-----|-------|-----|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| | | 03.22 | 8.2.0 | | | R99 | | | Split of 03.22/R99 to 03.22 and 23.122 | | +| #6 | | 23.122 | 0.0.0 | | | R99 | | 3.0.0 | | Was approved in the TSGN#6 plenary | +| #4 | N1-99573 | 23.102 | 3.0.0 | 001 | | R99 | F | 3.1.0 | PLMN selection for GPRS mobiles | Mirrored from CRA032r2 REMOVED in V3.1.1, where it is not approved by SMG2 | +| #6 | N1-99D13 | 23.122 | 3.0.0 | 002 | | R99 | A | 3.1.0 | Correction of Figure A.2 in Annex A | Mirrored from CR006r1for 23.022 | +| #7 | N1-000546 | 23.122 | 3.1.1 | 004 | 1 | R99 | D | 3.2.0 | UMTS references in 23.122 | Correction of references | +| #8 | N1-000796 | 23.122 | 3.2.0 | 003 | 5 | R99 | F | 3.3.0 | Modification of PLMN Selection Procedures to support UMTS+COMPACT Network Selection | WI: GSM/UMTS interworking
Note As a result of two conflicting CRs N1-000796 is merged with the existing text in V.3.2.0 by the rapporteur | +| #9 | NP-000443/
N1-001020 | 23.122 | 3.3.0 | 009 | 2 | R99 | F | 3.4.0 | Clarifications of the PLMN Selection procedures for UMTS and COMPACT. | | +| | | 23.122 | 3.4.0 | | | | | 3.4.1 | Correction of text in version3.4.0 (There was text to be deleted in clause 4.4.3.2.1 bullet point 2) | 23.Oct.2000
Implementation correction | +| | | 23.122 | 3.4.1 | | | | | 3.4.2 | Correction of a systematic search for "TS" and replace it with "3GPP TS" has gone wrong as much more than the TSs for Technical Specifications have been changed also. | 1 Nov..2000
Implementation correction | +| #10 | NP-000674/
N1-001415 | 23.122 | 3.4.2 | 010 | 1 | R99 | F | 3.5.0 | Correction of terminology "In UMTS", "In GSM" | Cat F/ WI=TEI | +| #10 | NP-000671/
N1-001236 | 23.122 | 3.4.2 | 012 | | R99 | F | 3.5.0 | Restoration of figure A.1 | Cat F/ WI=GSM - UMTS Interworking | +| #10 | NP-000671/
N1-001237 | 23.122 | 3.4.2 | 013 | | R99 | F | 3.5.0 | Alignment of figure 2a with PLMN selection for UMTS | Cat F/ WI=GSM - UMTS Interworking | +| #11 | NP-010207/
N1-010472 | 23.122 | 3.5.0 | 014 | 3 | R99 | F | 3.6.0 | Clarification of the PLMN selection for UMTS regarding high quality signal | GSM - UMTS Interworking | +| #11 | NP-010168/
N1-010224 | 23.122 | 3.5.0 | 016 | 1 | R99 | F | 3.6.0 | Roaming restrictions for GPRS service | GSM - UMTS Interworking | +| #11 | NP-010205/
N1-010334 | 23.122 | 3.5.0 | 017 | | R99 | F | 3.6.0 | remove use of GSM as default access technology in PLMN search | T.E.I | +| #11 | NP-01089/
N1-010443 | 23.122 | 3.5.0 | 018 | | R99 | F | 3.6.0 | Requirement of priority on High Quality Signal cell concerning Acceptable cell (for limited service as emergency call) | T.E.I | +| #11 | NP-010186/
N1-010489 | 23.122 | 3.5.0 | 019 | 4 | R99 | F | 3.6.0 | Clarifications to PLMN search | T.E.I | +| #11 | NP-010186/
N1-010490 | 23.122 | 3.5.0 | 020 | 1 | R99 | F | 3.6.0 | Clarifications to PLMN search | T.E.I | +| #11 | NP-010180 | 23.122 | 3.5.0 | 022 | 1 | R99 | F | 3.6.0 | Equivalent handling of PLMNs with different PLMN codes | GSM - UMTS Interworking | +| #11 | | | 3.6.0 | | | | | 4.0.0 | Upgraded to Release 4. | | +| #12 | NP-010352 | 23.122 | 4.0.0 | 024 | 1 | Rel-4 | A | 4.1.0 | Stored list of equivalent PLMNs and error/abnormal cases | GSM-UMTS INTERWORKING | +| #12 | NP-010276 | 23.122 | 4.0.0 | 027 | 1 | Rel-4 | A | 4.1.0 | Corrections and clarifications to PLMN Selection | GSM-UMTS INTERWORKING | +| #12 | NP-010275 | 23.122 | 4.0.0 | 030 | 3 | Rel-4 | A | 4.1.0 | Partial Roaming – restriction by location area | TEI | +| #12 | NP-010276 | 23.122 | 4.0.0 | 032 | | Rel-4 | A | 4.1.0 | Removal of 'Requirement of priority on High Quality Signal cell concerning Acceptable cell | TEI | +| #12 | NP-010276 | 23.122 | 4.0.0 | 034 | | Rel-4 | A | 4.1.0 | Alignment with stage 1 specification on PLMN background search | TEI | +| NP-16 | NP-020243 | 23.122 | 4.1.0 | 048 | | Rel-5 | F | 5.0.0 | Role of the equivalent PLMNs list in the PLMN user reselection | TEI5 | +| NP-17 | NP-020369 | 23.122 | 5.0.0 | 051 | | Rel-5 | A | 5.1.0 | Removal of CBQ2 | COMPACT | +| NP-17 | NP-020383 | 23.122 | 5.0.0 | 052 | 1 | Rel-5 | F | 5.1.0 | Applicability of the lists of "forbidden LAs" | TEI5 | +| NP-17 | NP-020367 | 23.122 | 5.0.0 | 055 | | Rel-5 | A | 5.1.0 | Routing Area Update at network change | TEI | +| NP-18 | NP-020549 | 23.122 | 5.1.0 | 058 | | Rel-5 | A | 5.2.0 | Correction of references | TEI | +| | | | 5.1.0 | | | Rel-5 | | 5.2.0 | Additional cleanup done to references by ETSI/MCC | | +| NP-21 | NP-030405 | 23.122 | 5.2.0 | 061 | | Rel-5 | A | 5.3.0 | Removal of RPLMNAct field | TEI | +| NP-23 | NP-040037 | 23.122 | 5.3.0 | 067 | 1 | Rel-6 | F | 6.0.0 | Definition of MS idle mode | TEI6 | +| NP-23 | NP-040037 | 23.122 | 5.3.0 | 068 | | Rel-6 | F | 6.0.0 | Usage of HPLMNAct by the UE | TEI6 | + +| TSG# | Tdoc | SPEC | VERS | CR | REV | PHASE | CAT | N_VER | SUBJECT | comment | +|-------|-----------|--------|--------|------|-----|-------|-----|--------|--------------------------------------------------------------------------------------------------|-----------------------| +| NP-24 | NP-040202 | 23.122 | 6.0.0 | 069 | 5 | Rel-6 | F | 6.1.0 | Clarification on the use of the RAT during background scanning. | TEI6 | +| NP-24 | NP-040202 | 23.122 | 6.0.0 | 071 | 1 | Rel-6 | F | 6.1.0 | Role of ePLMN list in manual PLMN selection mode | TEI6 | +| NP-24 | NP-040202 | 23.122 | 6.0.0 | 072 | 1 | Rel-6 | F | 6.1.0 | Roaming not allowed for GPRS update state | TEI6 | +| NP-24 | NP-040202 | 23.122 | 6.0.0 | 073 | | Rel-6 | D | 6.1.0 | Data field -> data file | TEI6 | +| NP-25 | NP-040375 | 23.122 | 6.1.0 | | | Rel-6 | B | 6.2.0 | Clarification on the registered PLMN for UEs that support network sharing in a shared network | NTShar | +| NP-25 | NP-040378 | 23.122 | 6.1.0 | 76 | 2 | Rel-6 | F | 6.2.0 | Correction of definitions of PLMNs in the same country | TEI6 | +| NP-26 | NP-040513 | 23.122 | 6.2.0 | 77 | 1 | Rel-6 | B | 6.3.0 | Clarification of PLMN selection in shared networks | NTShar | +| NP-26 | NP-040514 | 23.122 | 6.2.0 | 086 | 1 | Rel-6 | F | 6.3.0 | Clarification on the use of the RAT during background scanning | TEI6 | +| NP-26 | NP-040516 | 23.122 | 6.2.0 | 084 | 1 | Rel-7 | C | 7.0.0 | Support of multiple HPLMN codes | TEI7 | +| NP-27 | NP-050083 | 23.122 | 7.0.0 | 082 | | Rel-7 | | 7.1.0 | Addition of domain specific access control description | ACBOP | +| NP-27 | NP-050086 | 23.122 | 7.0.0 | 089 | | Rel-7 | A | 7.1.0 | Minor Clarifications to EHPLMN handling | TEI7 | +| CP-28 | CP-050068 | 23.122 | 7.1.0 | 087 | 1 | Rel-7 | F | 7.2.0 | Correction of the PLMN Selection State diagram (automatic mode) | TEI6 | +| CP-29 | CP-050366 | 23.122 | 7.2.0 | 91 | | Rel-7 | A | 7.3.0 | Enhancement of the EHPLMN feature to allow load balancing | TEI7 | +| CP-31 | CP-060126 | 23.122 | 7.3.0 | 93 | 1 | Rel-7 | C | 7.4.0 | EPLMN list is not invalid on receipt of reject cause values #12 and #15 | TEI7 | +| CP-31 | CP-060126 | 23.122 | 7.3.0 | 0094 | - | Rel-7 | F | 7.4.0 | EHPLMN in automatic network selection mode | TEI7 | +| CP-31 | CP-060175 | 23.122 | 7.3.0 | 0095 | - | Rel-7 | F | 7.4.0 | First higher priority PLMN scan in VPLMN | TEI7 | +| CP-32 | CP-060359 | 23.122 | 7.4.0 | 0096 | 4 | Rel-7 | C | 7.5.0 | ME capability for Network Selection | TEI7 | +| CP-33 | CP-060460 | 23.122 | 7.5.0 | 0098 | 2 | Rel-7 | B | 7.6.0 | Manual PLMN selection power-on | NSP-CR | +| CP-34 | CP-060668 | 23.122 | 7.6.0 | 0099 | 1 | Rel-7 | C | 7.7.0 | Presentation of EHPLMN | NSP-CR | +| CP-34 | CP-060668 | 23.122 | 7.6.0 | 0101 | 1 | Rel-7 | C | 7.7.0 | Presentation of Additional Information in Manual Mode | NSP-CR | +| CP-34 | CP-060670 | 23.122 | 7.6.0 | 0102 | 2 | Rel-7 | C | 7.7.0 | Correction to the definition of national roaming and international roaming to include the EHPLMN | TEI7 | +| CP-34 | CP-060670 | 23.122 | 7.6.0 | 0103 | 1 | Rel-7 | F | 7.7.0 | Correction of the PLMN Selection state diagram (automatic mode) | TEI7 | +| CP-35 | CP-070152 | 23.122 | 7.7.0 | 0104 | - | Rel-7 | F | 7.8.0 | Last RPLMN | NSP-CR | +| CP-35 | CP-070152 | 23.122 | 7.7.0 | 0111 | 3 | Rel-7 | B | 7.8.0 | Optional network selection mode at switch-on | NSP-CR | +| CP-35 | CP-070173 | 23.122 | 7.7.0 | 0113 | 1 | Rel-7 | B | 7.8.0 | Pingpong avoidance on PLMN change for search for higher priority PLMNs | TEI7 | +| CP-36 | CP-070477 | 23.122 | 7.8.0 | 0106 | 2 | Rel-7 | C | 7.9.0 | PLMN selection for steering of roaming | NSP-CR | +| CP-37 | CP-070597 | 23.122 | 7.9.0 | 0114 | 4 | Rel-7 | B | 7.10.0 | | | +| CP-38 | CP-070802 | 23.122 | 7.10.0 | 0115 | 1 | Rel-7 | C | 7.11.0 | Steering of Roaming procedure | NSP-CR | +| CP-38 | CP-070813 | 23.122 | 7.11.0 | 0117 | | Rel-8 | F | 8.0.0 | Single EHPLMN Display Name in Manual Mode | TEI7 | +| CP-39 | CP-080125 | 23.122 | 8.0.0 | 0118 | 1 | Rel-8 | B | 8.1.0 | PPACR CR to 23.122 | PPACR-CT1 | +| CP-40 | CP-080361 | 23.122 | 8.1.0 | 0120 | 1 | Rel-8 | A | 8.2.0 | Inclusion of EHPLMN in the optimisation for automatic network selection | NSP-CR | +| CP-41 | CP-080536 | 23.122 | 8.2.0 | 0119 | 3 | Rel-8 | B | 8.3.0 | PLMN Selection on receipt of GAN cause Location not allowed | TEI8 | +| CP-41 | CP-080536 | 23.122 | 8.2.0 | 0121 | 0 | Rel-8 | F | 8.3.0 | Clarifications for RAT usage in manual network selection mode | TEI8 | +| CP-42 | CP-080866 | 23.122 | 8.3.0 | 0122 | 1 | Rel-8 | F | 8.4.0 | Clarification on MS behavior further to LU Reject causes #13 and #15 | TEI8 | +| CP-42 | CP-080860 | 23.122 | 8.3.0 | 0124 | 1 | Rel-8 | B | 8.4.0 | Multi system PLMN selection | SAES | +| CP-42 | CP-080866 | 23.122 | 8.3.0 | 0125 | 1 | Rel-8 | B | 8.4.0 | CR on description of PPAC | PPACR-CT1 | +| CP-42 | CP-080966 | 23.122 | 8.3.0 | 0126 | 1 | Rel-8 | B | 8.4.0 | 3GPP2 system selection | SAES | +| CP-42 | CP-080966 | 23.122 | 8.3.0 | 0128 | 2 | Rel-8 | B | 8.4.0 | CSG selection – NAS aspects | HomeNB-3G, HomeNB-LTE | +| CP-43 | CP-090157 | 23.122 | 8.4.0 | | | Rel-8 | | 8.5.0 | Editorial cleanup by MCC | | +| CP-43 | CP-090222 | 23.122 | 8.4.0 | 0129 | 1 | Rel-8 | | 8.5.0 | Correction on CSG related NAS requirement | HomeNB-LTE, HomeNB-3G | +| | | 23.122 | 8.4.0 | 0130 | 2 | Rel-8 | | 8.5.0 | CSG selection process in idle mode | HomeNB-LTE, HomeNB-3G | + +| TSG# | Tdoc | SPEC | VERS | CR | REV | PHASE | CAT | N_VER | SUBJECT | comment | +|-------|-----------|--------|--------|------|-----|--------|-----|--------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| CP-43 | CP-090157 | 23.122 | 8.4.0 | 0132 | 1 | Rel-8 | | 8.5.0 | Introduction of cause#25 handling in LR state diagram | HomeNB-3G | +| CP-44 | CP-090413 | 23.122 | 8.5.0 | 0131 | 1 | Rel-8 | F | 8.6.0 | Addition of missing requirements for tracking area updating | SAES | +| CP-45 | | 23.122 | 8.6.0 | | | Rel-8 | | 8.7.0 | RAT selection when "HPLMN selector with access technology" data file is missing in the SIM or "PLMN selector" data file is used | | +| | CP-090679 | | | 0133 | 2 | | F | | | TEI8 | +| CP-45 | CP-090694 | 23.122 | 8.7.0 | 0139 | 1 | Rel-9 | B | 9.0.0 | Introduction of Operator CSG List | EHNB-CT1 | +| CP-45 | CP-090694 | 23.122 | 8.7.0 | 0140 | 1 | Rel-9 | F | 9.0.0 | Manual CSG selection across PLMN | EHNB-CT1 | +| CP-46 | | 23.122 | 9.0.0 | | | Rel-9 | | 9.1.0 | PLMN selection during emergency attach | | +| | CP-090930 | | | 0142 | 2 | | F | | | IMS_EMER_GPRS_EPS | +| CP-46 | CP-090935 | 23.122 | 9.0.0 | 0143 | | Rel-9 | F | 9.1.0 | Correct definitions related to CSG | EHNB-CT1 | +| CP-46 | | 23.122 | 9.0.0 | | | Rel-9 | | 9.1.0 | Correction of condition for tracking area updating | | +| | CP-090922 | | | 0146 | | | F | | | TEI9 | +| CP-46 | | 23.122 | 9.0.0 | | | Rel-9 | | 9.1.0 | Adding missing requirements for PLMN selection in EPS | | +| | CP-090900 | | | 0148 | | | A | | | SAES | +| CP-47 | CP-100148 | 23.122 | 9.1.0 | 0144 | 4 | Rel-9 | F | 9.2.0 | Support for Operator CSG List | EHNB-CT1 | +| CP-47 | | 23.122 | 9.1.0 | | | Rel-9 | | 9.2.0 | Manual CSG selection during emergency | | +| | CP-100144 | | | 0149 | 1 | | F | | | IMS_EMER_GPRS_EPS | +| CP-47 | | 23.122 | 9.1.0 | | | Rel-9 | | 9.2.0 | Clarification to LR state when rejected for cause value #25. | HomeNB-LTE, HomeNB-3G | +| | CP-100130 | | | 0151 | 1 | | A | | | | +| CP-47 | | 23.122 | 9.1.0 | | | Rel-9 | | 9.2.0 | Clarification to the LR Process States and Allowed Actions | | +| | CP-100148 | | | 0152 | 1 | | F | | | EHNB-CT1 | +| CP-47 | | 23.122 | 9.1.0 | | | Rel-9 | | 9.2.0 | Clarify manual CSG selection across technologies | HomeNB-LTE, HomeNB-3G | +| | CP-100130 | | | 0156 | 1 | | A | | | | +| CP-47 | | 23.122 | 9.1.0 | | | Rel-9 | | 9.2.0 | Correct definition of "acceptable cell" to include criteria for E-UTRAN (S1-mode) | | +| | CP-100144 | | | 0160 | 1 | | F | | | IMS_EMER_GPRS_EPS | +| CP-47 | | 23.122 | 9.1.0 | | | Rel-9 | | 9.2.0 | Correction to the manual CSG ID selection in Release 9 | | +| | CP-100148 | | | 0161 | | | F | | | EHNB-CT1 | +| CP-47 | | 23.122 | 9.1.0 | | | Rel-9 | | 9.2.0 | Corrections/clarifications for equivalent and forbidden PLMN handling, state descriptions and overall idle mode procedure | | +| | CP-100134 | | | 0162 | 1 | | F | | | TEI9 | +| CP-48 | | 23.122 | 9.2.0 | | | Rel-9 | | 9.3.0 | Deleting editor's note related manual CSG selection | | +| | CP-100362 | | | 0165 | | | F | | | EHNB-CT1 | +| CP-48 | CP-100339 | 23.122 | 9.2.0 | 0168 | 1 | Rel-9 | A | 9.3.0 | Reference Update | SAES | +| CP-48 | | 23.122 | 9.3.0 | | | Rel-10 | | 10.0.0 | Manual CSG Selection using CSG Identities not in Allowed CSG List and Operator CSG List | | +| | CP-100370 | | | 0166 | 1 | | F | | | TEI10 | +| CP-49 | CP-100521 | 23.122 | 10.0.0 | 0171 | 2 | Rel-10 | A | 10.1.0 | Definition of CSG whitelist | EHNB-CT1 | +| CP-49 | | 23.122 | 10.0.0 | | | Rel-10 | | 10.1.0 | | HomeNB-LTE, HomeNB-3G | +| | CP-100498 | | | 0176 | 1 | | A | | HeNB name for manual CSG selection | | +| CP-49 | | 23.122 | 10.0.0 | | | Rel-10 | | 10.1.0 | Correction to Initiation of Location Registration | | +| | CP-100518 | | | 0178 | 1 | | F | | | TEI10 | +| CP-49 | CP-100518 | 23.122 | 10.0.0 | 0179 | | Rel-10 | F | 10.1.0 | Adding Reference for PLMN selection | TEI10 | +| CP-50 | | 23.122 | 10.1.0 | | | Rel-10 | | 10.2.0 | Support for displaying only CSGs in the Operator CSG List for manual selection | | +| | CP-100748 | | | 0182 | 3 | | A | | | EHNB-CT1 | +| CP-50 | | 23.122 | 10.1.0 | | | Rel-10 | | 10.2.0 | Inter PLMN mobility for emergency bearer services | | +| | CP-100747 | | | 0184 | 1 | | A | | | IMS_EMER_GPRS_EPS | +| CP-50 | | 23.122 | 10.1.0 | | | Rel-10 | | 10.2.0 | Handling forbidden PLMN list for emergency bearer services | | +| | CP-100747 | | | 0186 | 2 | | A | | | IMS_EMER_GPRS_EPS | +| CP-50 | | 23.122 | 10.1.0 | | | Rel-10 | | 10.2.0 | Handling of equivalent PLMN list when attached for emergency bearer services only | | +| | CP-100747 | | | 0188 | 1 | | A | | | IMS_EMER_GPRS_EPS | +| CP-50 | | 23.122 | 10.1.0 | | | Rel-10 | | 10.2.0 | MTC/Low-Priority PLMN Reselection Timer value | | +| | CP-100887 | | | 0192 | 3 | | C | | | NIMTC | +| CP-50 | | 23.122 | 10.1.0 | | | Rel-10 | | 10.2.0 | Removing the CSG ID from ACL and OCL simultaneously | | +| | CP-100748 | | | 0195 | | | A | | | EHNB-CT1 | +| CP-50 | | 23.122 | 10.1.0 | | | Rel-10 | | 10.2.0 | Location Registration when entering new PLMN | | +| | CP-100664 | | | 0190 | 3 | | F | | | NIMTC, TEI10 | +| CP-51 | | 23.122 | 10.2.0 | | | Rel-10 | | 10.3.0 | UEs configured with long minimum periodic PLMN search time limit | | +| | CP-110193 | | | 0196 | 1 | | F | | | NIMTC | +| CP-51 | CP-110193 | 23.122 | 10.2.0 | 0198 | 5 | Rel-10 | B | 10.3.0 | EAB support | NIMTC | +| CP-52 | | 23.122 | 10.3.0 | | | Rel-10 | | 10.4.0 | | HomeNB-3G, HomeNB-LTE | +| | CP-110446 | | | 0205 | 1 | | A | | Aligning NAS and AS on CSG | | +| CP-52 | | 23.122 | 10.3.0 | | | Rel-10 | | 10.4.0 | Reference to NAS configuration in USIM | | +| | CP-110462 | | | 0206 | 1 | | B | | | NIMTC | +| CP-53 | CP-110680 | 23.122 | 10.4.0 | 0210 | 1 | Rel-10 | F | 10.5.0 | Correction to EAB | NIMTC | +| CP-53 | CP-110695 | 23.122 | 10.5.0 | 0207 | 4 | Rel-11 | B | 11.0.0 | Support for multiple MCC countries | TEI11 | +| CP-53 | CP-110737 | 23.122 | 10.5.0 | 0208 | 2 | Rel-11 | B | 11.0.0 | EAB references | SIMTC-RAN_OC | + +| TSG# | Tdoc | SPEC | VERS | CR | REV | PHASE | CAT | N_VER | SUBJECT | comment | +|-------|-----------|--------|--------|------|-----|--------|-----|--------|-------------------------------------------------------------------------------------------------------------------|------------------------| +| CP-54 | CP-110888 | 23.122 | 11.0.0 | 0211 | 1 | Rel-11 | F | 11.1.0 | Clarification to the manual PLMN selection procedure | SAES2 | +| CP-56 | CP-120309 | 23.122 | 11.1.0 | 0212 | | Rel-11 | F | 11.2.0 | Correction on location registration task state | TEI11 | +| CP-56 | CP-120315 | 23.122 | 11.1.0 | 0213 | | Rel-11 | F | 11.2.0 | EAB configuration | SIMTC-RAN_OC | +| CP-56 | | 23.122 | 11.1.0 | | | Rel-11 | | 11.2.0 | UE configured for EAB accessing with access class 11-15 or initiating emergency call | SIMTC-RAN_OC | +| CP-56 | CP-120315 | 23.122 | 11.1.0 | 0214 | 1 | Rel-11 | F | 11.2.0 | Applicability of EAB when the UE is responding to paging | SIMTC-RAN_OC | +| CP-56 | CP-120309 | 23.122 | 11.1.0 | 0217 | | Rel-11 | F | 11.2.0 | Handling of forbidden PLMNs for GPRS service list | TEI11 | +| CP-57 | CP-120595 | 23.122 | 11.2.0 | 0216 | 4 | Rel-11 | F | 11.3.0 | PLMN selection timer for E-UTRA disabling | SAES2, SAES2-CSFB | +| CP-57 | CP-120589 | 23.122 | 11.2.0 | 0219 | 2 | Rel-11 | F | 11.3.0 | EAB overriding handling | SIMTC-Reach | +| CP-57 | CP-120584 | 23.122 | 11.2.0 | 0220 | | Rel-11 | F | 11.3.0 | Removing NMO III | TEI11 | +| CP-58 | CP-120794 | 23.122 | 11.3.0 | 0218 | 2 | Rel-11 | F | 11.4.0 | Correction on cause #2 in response to an LR | TEI11 | +| CP-58 | CP-120807 | 23.122 | 11.3.0 | 0221 | 3 | Rel-11 | F | 11.4.0 | E-UTRA disabling stored information deletion criteria correction | SAES2 | +| CP-58 | CP-120794 | 23.122 | 11.3.0 | 0222 | | Rel-11 | F | 11.4.0 | Corrections to steps in clause 5 related to CSG selection | TEI11 | +| CP-58 | CP-120797 | 23.122 | 11.3.0 | 0223 | 3 | Rel-11 | B | 11.4.0 | Access control and DSAC for shared networks | GDSAC, FULL_MOCN-GERAN | +| CP-58 | CP-120794 | 23.122 | 11.3.0 | 0224 | 1 | Rel-11 | F | 11.4.0 | Ignoring Forbidden Lists During Manual CSG Selection | TEI11 | +| CP-58 | CP-120794 | 23.122 | 11.3.0 | 0225 | 3 | Rel-11 | F | 11.4.0 | HPLMN or RPLMN selection clarification | TEI11 | +| CP-58 | CP-120807 | 23.122 | 11.3.0 | 0226 | 1 | Rel-11 | F | 11.4.0 | Clean-up the confusion between the term update state and update status | SAES2, TEI11 | +| CP-59 | CP-130129 | 23.122 | 11.4.0 | 0229 | 2 | Rel-12 | F | 12.0.0 | EHPLMN selection clarification | TEI12 | +| CP-60 | CP-130264 | 23.122 | 12.0.0 | 0230 | 2 | Rel-12 | F | 12.1.0 | Corrections to manual CSG selection | TEI12 | +| CP-60 | CP-130264 | 23.122 | 12.0.0 | 0231 | 2 | Rel-12 | F | 12.1.0 | GERAN Iu mode | TEI12 | +| CP-60 | CP-130264 | 23.122 | 12.0.0 | 0232 | 1 | Rel-12 | F | 12.1.0 | Missing reference for GERAN specification | TEI12 | +| CP-61 | CP-130510 | 23.122 | 12.1.0 | 0234 | 1 | Rel-12 | F | 12.2.0 | Last PLMN selection mode at switch on | TEI12 | +| CP-61 | CP-130510 | 23.122 | 12.1.0 | 0235 | 1 | Rel-12 | F | 12.2.0 | Switch off after manual CSG selection in a PLMN different from the RPLMN | TEI12 | +| CP-61 | CP-130510 | 23.122 | 12.1.0 | 0237 | | Rel-12 | F | 12.2.0 | Clarifying requirement for steering of roaming | TEI12 | +| CP-61 | CP-130510 | 23.122 | 12.1.0 | 0238 | | Rel-12 | F | 12.2.0 | Handling the received error cause #25 | TEI12 | +| CP-62 | CP-130762 | 23.122 | 12.2.0 | 0236 | 4 | Rel-12 | C | 12.3.0 | Fast higher priority PLMN search upon entering VPLMN | TEI12 | +| CP-62 | CP-130762 | 23.122 | 12.2.0 | 0241 | 1 | Rel-12 | F | 12.3.0 | Terminology Alignment for name of forbidden lists between Stage 2 and Stage 3 | TEI12 | +| CP-62 | CP-130762 | 23.122 | 12.2.0 | 0242 | | Rel-12 | F | 12.3.0 | Duplicate entries in ACL and OCL when forming CSG Whitelist | TEI12 | +| CP-62 | CP-130762 | 23.122 | 12.2.0 | 0243 | 4 | Rel-12 | F | 12.3.0 | User initiated PLMN selection after manual CSG selection and registration on a CSG cell. | TEI12 | +| CP-62 | CP-130762 | 23.122 | 12.2.0 | 0244 | | Rel-12 | D | 12.3.0 | Clean-up of references | TEI12 | +| CP-62 | CP-130762 | 23.122 | 12.2.0 | 0246 | | Rel-12 | F | 12.3.0 | HPLMN criteria matching correction | TEI12 | +| CP-63 | | 23.122 | 12.3.0 | | | Rel-12 | | 12.4.0 | Incorrect combination of stored duplicate of RPLMN and current PLMN selection mode due to multiple CSG selections | | +| CP-63 | CP-140144 | | | 0250 | 2 | | F | | | TEI12 | +| CP-63 | CP-140144 | 23.122 | 12.3.0 | 0251 | 1 | Rel-12 | F | 12.4.0 | No CSG cell and re-enable E-UTRA | TEI12 | +| CP-64 | | 23.122 | 12.4.0 | | | Rel-12 | | 12.5.0 | PLMN selection timer for enhanced EMM cause #15 | | +| CP-64 | CP-140331 | | | 0249 | 4 | | F | | | TEI12 | +| CP-64 | CP-140323 | 23.122 | 12.4.0 | 0253 | 1 | Rel-12 | F | 12.5.0 | Updates due to power saving mode | MTCe-UEPCOP-CT | +| CP-64 | CP-140331 | 23.122 | 12.4.0 | 0255 | | Rel-12 | F | 12.5.0 | Clarification regarding cause #25 received by the UE | TEI12 | +| CP-64 | CP-140328 | 23.122 | 12.4.0 | 0257 | 2 | Rel-12 | F | 12.5.0 | Triggering a CS call from the selected CSG | SAES3-CSFB | +| CP-66 | | 23.122 | 12.5.0 | | | Rel-13 | | 13.0.0 | Correct Automatic Network Selection Mode Procedure for UE supporting E-UTRAN | | +| CP-66 | CP-140862 | | | 0262 | 5 | | F | | | SAES4 | +| CP-67 | CP-150205 | 23.122 | 13.0.0 | 0272 | 2 | Rel-13 | A | 13.1.0 | Clarification on limited service state | ProSe-CT | +| CP-67 | CP-150206 | 23.122 | 13.0.0 | 0273 | 2 | Rel-13 | A | 13.1.0 | Clarification on limited service state | TEI12 | +| CP-68 | CP-150316 | 23.122 | 13.1.0 | 0269 | 8 | Rel-13 | A | 13.2.0 | PLMN selection triggered by ProSe direct communication | ProSe-CT | + +| TSG# | Tdoc | SPEC | VERS | CR | REV | PHASE | CAT | N_VER | SUBJECT | comment | +|-------|-----------|--------|--------|------|-----|--------|-----|--------|---------------------------------------------------------------------------------------------------------|--------------------| +| CP-68 | CP-150323 | 23.122 | 13.1.0 | 0274 | | Rel-13 | F | 13.2.0 | Correct Automatic Network Selection Mode Procedure for UE supporting E-UTRA | SAES4 | +| CP-68 | CP-150316 | 23.122 | 13.1.0 | 0280 | | Rel-13 | A | 13.2.0 | Correction of limited service state for ProSe direct communication | ProSe-CT | +| CP-69 | CP-150534 | 23.122 | 13.2.0 | 0278 | 3 | Rel-13 | B | 13.3.0 | Introduction of ACDC for access control | ACDC-CT | +| CP-69 | CP-150517 | 23.122 | 13.2.0 | 0282 | 1 | Rel-13 | A | 13.3.0 | Correction of limited service state for ProSe direct communication | ProSe-CT | +| CP-69 | CP-150529 | 23.122 | 13.2.0 | 0283 | 1 | Rel-13 | F | 13.3.0 | Inconsistency where PLMN selection in automatic mode is performed while GPRS services are not available | TEI13 | +| CP-71 | CP-160157 | 23.122 | 13.3.0 | 0289 | 1 | Rel-13 | F | 13.4.0 | ProSe direct discovery for public safety use in limited service state | eProSe-Ext-CT | +| CP-72 | CP-160309 | 23.122 | 13.4.0 | 0293 | 2 | Rel-13 | C | 13.5.0 | Disabling emergency calls for NB-IoT devices in limited service state | CIoT-CT | +| CP-72 | CP-160318 | 23.122 | 13.4.0 | 0295 | 1 | Rel-13 | F | 13.5.0 | Handling of PLMN background scan during PSM | TEI13 | +| CP-72 | CP-160302 | 23.122 | 13.4.0 | 0300 | 1 | Rel-13 | A | 13.5.0 | PLMN selection triggered by ProSe communication in manually selected CSG cell | ProSe-CT, TEI12 | +| CP-72 | CP-160309 | 23.122 | 13.4.0 | 0292 | 7 | Rel-13 | C | 13.5.0 | Extend search cycle for higher priority PLMN | CIoT-CT | +| CP-72 | CP-160318 | 23.122 | 13.4.0 | 0297 | 2 | Rel-13 | B | 13.5.0 | Addition of EC-GSM-IoT access to PLMN selection | TEI13, CIoT_EC_GSM | +| CP-72 | CP-160309 | 23.122 | 13.4.0 | 0298 | 3 | Rel-13 | B | 13.5.0 | PLMN selection when the network and UE capabilities for CIoT do not match | CIoT-CT | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | CP-73 | CP-160486 | 0302 | | F | Addition of NB-S1 mode to PLMN selection | 13.6.0 | +| 2016-09 | CP-73 | CP-160487 | 0304 | | F | Corrections due to added CIoT requirements | 13.6.0 | +| 2016-09 | CP-73 | CP-160519 | 0301 | 1 | F | Minor corrections for EC GPRS | 14.0.0 | +| 2016-09 | CP-73 | CP-160512 | 0303 | 1 | B | PLMN selection for eCall over IMS | 14.0.0 | +| 2016-12 | CP-74 | CP-160739 | 0305 | | F | MS in eCall only mode | 14.1.0 | +| 2016-12 | CP-74 | CP-160739 | 0306 | 1 | B | Update of requirements on limited service state for MS in eCall only mode | 14.1.0 | +| 2016-12 | CP-74 | CP-160753 | 0308 | 1 | F | Skip ACDC for emergency call, MO MMTEL voice/video and MO SMSSoP | 14.1.0 | +| 2016-12 | CP-74 | CP-160754 | 0310 | 1 | F | V2X communication over PC5 is used for UEs in limited service state | 14.1.0 | +| 2017-03 | CP-75 | CP-170138 | 0315 | | F | PLMN selection triggered by V2X communication over PC5 | 14.2.0 | +| 2017-06 | CP-76 | CP-171092 | 0321 | | F | Correction in handling of cause value "GPRS services not allowed in this PLMN" or "EPS services not allowed in this PLMN" | 14.3.0 | +| 2017-06 | CP-76 | CP-171094 | 0318 | 1 | F | Adding a NOTE for HPLMN and RPLMN selection | 15.0.0 | +| 2017-09 | CP-77 | CP-172122 | 0322 | 1 | F | Clarification to network selection procedures | 15.1.0 | +| 2017-09 | CP-77 | CP-172132 | 0326 | | A | Corrections to handling of EFFPLMN file in the SIM and of "forbidden PLMNs for GPRS service" list | 15.1.0 | +| 2017-12 | CP-78 | CP-173067 | 0327 | | A | Max length of timer TE for IoT devices | 15.2.0 | +| 2017-12 | CP-78 | CP-173079 | 0328 | | D | Editorial correction: wrong color | 15.2.0 | +| 2017-12 | CP-78 | CP-173079 | 0329 | | F | Correction for classification of EC-GSM-IoT high quality signal | 15.2.0 | +| 2017-12 | CP-78 | CP-173079 | 0332 | 1 | F | Allow exiting manual PLMN selection mode due to emergency call | 15.2.0 | +| 2018-03 | CP-79 | CP-180076 | 0333 | 4 | B | Addition of NG-RAN | 15.3.0 | +| 2018-03 | CP-79 | CP-180089 | 0334 | 1 | F | Informing user of exit from manual network selection mode | 15.3.0 | +| 2018-03 | CP-79 | CP-180076 | 0335 | 1 | B | Addition of 5GS forbidden TA lists | 15.3.0 | +| 2018-03 | CP-79 | CP-180076 | 0337 | 1 | B | N1 mode disabling - use of PLMN id in subsequent PLMN selections | 15.3.0 | +| 2018-03 | CP-79 | CP-180076 | 0339 | 2 | B | 5GS forbidden TA for regional provision of service | 15.3.0 | +| 2018-03 | CP-79 | CP-180157 | 0340 | 5 | B | Stage 2 solution of Steering Of Roaming (SOR) | 15.3.0 | +| 2018-06 | CP-80 | CP-181057 | 0343 | 1 | F | Terminology correction in handling of PLMNs where N1 mode was disabled | 15.4.0 | +| 2018-06 | CP-80 | CP-181057 | 0344 | | B | Adding support for eCall over IMS in 5GS | 15.4.0 | +| 2018-06 | CP-80 | CP-181057 | 0345 | 3 | B | Alignment: replacing the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list | 15.4.0 | +| 2018-06 | CP-80 | CP-181058 | 0347 | 6 | B | Updates to Stage 2 solution of Steering Of Roaming (SOR) | 15.4.0 | +| 2018-06 | CP-80 | CP-181058 | 0348 | 1 | F | Disabling and re-enabling capabilities in the NAS layer | 15.4.0 | +| 2018-06 | CP-80 | CP-181076 | 0349 | 2 | B | PLMN selection for disabling NB-IoT | 15.4.0 | +| 2018-06 | CP-80 | CP-181058 | 0350 | 1 | B | Updating terms in definitions and abbreviations due to 5GS | 15.4.0 | +| 2018-06 | CP-80 | CP-181053 | 0352 | | A | Forbidden PLMN operation for cause value "Requested service option not authorized in this PLMN" | 15.4.0 | +| 2018-06 | CP-80 | CP-181058 | 0356 | 1 | C | Updates due to network sharing for 5GS | 15.4.0 | +| 2018-09 | CP-81 | CP-182128 | 0357 | 2 | F | Introduce 5GS registration procedure | 15.5.0 | +| 2018-09 | CP-81 | CP-182106 | 0358 | 4 | B | Updates to Stage 2 solution of Steering Of Roaming (SOR) | 15.5.0 | +| 2018-09 | CP-81 | CP-182128 | 0359 | 2 | F | Unclear how to derive PLMN ID from broadcast in 3G, 4G, and 5G | 15.5.0 | +| 2018-09 | CP-81 | CP-182158 | 0360 | | C | Per RAT higher priority PLMN search timer T for UEs supporting IoT and non IoT RATs | 15.5.0 | +| 2018-09 | CP-81 | CP-182158 | 0361 | | F | Alignment on handling of forbidden LAI/TAI list | 15.5.0 | +| 2018-09 | CP-81 | CP-182128 | 0364 | 1 | B | Cause #15 has been successfully used for releases. | 15.5.0 | +| 2018-09 | CP-81 | CP-182128 | 0365 | 7 | B | Aligning SOR stage-2 flow as per SA3 agreements and other editorials | 15.5.0 | +| 2018-09 | CP-81 | CP-182106 | 0366 | 3 | F | Steering of Roaming for IMS emergency sessions and correction for NAS Transport for SOR | 15.5.0 | +| 2018-09 | CP-81 | CP-182128 | 0367 | 2 | F | PLMN selection when UE's N1 mode capability is disabled per access type | 15.5.0 | +| 2018-12 | CP-82 | CP-183030 | 0368 | | F | Correction to Nudm_SDM_UpdateNotification service operation name | 15.6.0 | +| 2018-12 | CP-82 | CP-183134 | 0369 | 2 | F | Correction for sending of Nudm_SDM_info | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0370 | 3 | F | Updates on steering of roaming call flow | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0371 | | F | Corrections to SoR procedure after registration | 15.6.0 | +| 2018-12 | CP-82 | CP-183076 | 0372 | 1 | F | Correction of requirements for the extension of the "forbidden PLMNs" list | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0373 | 3 | F | Correction to location registration for N1 mode | 15.6.0 | +| 2018-12 | CP-82 | CP-183076 | 0375 | 1 | F | Correction to handling of cause #15 | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0377 | 1 | F | VPLMN AMF behavior clarification. | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0378 | 1 | F | SOR stage-2 requirements | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0381 | 1 | F | Resolving inconsistencies in terminology | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0382 | | F | Clarification on mandatory conditions and INACTIVE state. | 15.6.0 | +| 2018-12 | CP-82 | CP-183030 | 0383 | 1 | F | Managing OPLMN list | 15.6.0 | +| 2018-12 | CP-82 | CP-183077 | 0374 | 1 | C | Delaying periodic higher priority PLMN searches when receiving eMBMS service in idle mode | 16.0.0 | +| 2019-03 | CP-83 | CP-190082 | 0384 | 4 | A | Correct procedure for SOR using secured packet over NAS after receiving REFRESH | 16.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | CP-83 | CP-190082 | 0386 | 1 | A | Correct procedure for identifying the PLMN to which a NR cell belongs | 16.1.0 | +| 2019-03 | CP-83 | CP-190082 | 0390 | 1 | A | Correction of text - SOR procedure | 16.1.0 | +| 2019-03 | CP-83 | CP-190082 | 0392 | | A | UE behaviour in connected mode when receiving SOR info in a secured packet | 16.1.0 | +| 2019-03 | CP-83 | CP-190101 | 0393 | | F | Missing references to 24.501 | 16.1.0 | +| 2019-03 | CP-83 | CP-190082 | 0395 | 1 | A | Inhibition of NAS signalling local release upon receiving SoR information during emergency services | 16.1.0 | +| 2019-03 | CP-83 | CP-190101 | 0398 | 2 | F | Adding clarification on CN Type | 16.1.0 | +| 2019-03 | CP-83 | CP-190082 | 0400 | 2 | A | Providing SoR information due to mobility registration update | 16.1.0 | +| 2019-03 | CP-83 | CP-190082 | 0402 | 1 | A | Correction to condition when list of PLMNs where registration was aborted due to SOR is deleted | 16.1.0 | +| 2019-03 | CP-83 | CP-190202 | 0404 | 2 | | Idle mode procedures for access to restricted local operator services | 16.1.0 | +| 2019-03 | CP-83 | CP-190082 | 0407 | 1 | A | Clarification and resolving editors notes in SOR procedure. | 16.1.0 | +| 2019-03 | CP-83 | CP-190108 | 0408 | | F | Clause correction. | 16.1.0 | +| 2019-03 | CP-83 | CP-190108 | 0409 | 1 | F | Consideration of WB-S1/CE mode in the PLMN selection procedure | 16.1.0 | +| 2019-03 | CP-83 | CP-190202 | 0410 | 2 | B | Support of restricted local operator services for UEs in limited service state | 16.1.0 | +| 2019-03 | CP-83 | CP-190082 | 0412 | 2 | A | Mandating UE sending registration complete for SOR | 16.1.0 | +| 2019-06 | CP-84 | CP-191148 | 0403 | 2 | B | CAG selection | 16.2.0 | +| 2019-06 | CP-84 | CP-191148 | 0413 | 2 | B | SNPN selection - new clauses | 16.2.0 | +| 2019-06 | CP-84 | CP-191148 | 0414 | 3 | B | SNPN selection - update of existing clauses | 16.2.0 | +| 2019-06 | CP-84 | CP-191144 | 0415 | 2 | B | Configuration of RLOS preferred PLMN list | 16.2.0 | +| 2019-06 | CP-84 | CP-191131 | 0418 | 1 | F | Add MICO requirements to the clause on "No suitable cell" | 16.2.0 | +| 2019-06 | CP-84 | CP-191147 | 0419 | 1 | F | Adding "limited service state" as a definition | 16.2.0 | +| 2019-06 | CP-84 | CP-191131 | 0420 | 1 | F | E-UTRA access in N1 mode | 16.2.0 | +| 2019-06 | CP-84 | CP-191128 | 0421 | 1 | B | PLMN selection based on Preferred CIoT Network Behavior | 16.2.0 | +| 2019-06 | CP-84 | CP-191144 | 0424 | 1 | B | Additional updates to Network Selection procedure for access to RLOS | 16.2.0 | +| 2019-06 | CP-84 | CP-191128 | 0425 | 1 | B | PLMN selection for WB-N1 UEs operating in CE mode | 16.2.0 | +| 2019-06 | CP-84 | CP-191144 | 0426 | 2 | F | NO Service and RLOS | 16.2.0 | +| 2019-06 | CP-84 | CP-191131 | 0427 | 4 | F | Managing OPLMN list | 16.2.0 | +| 2019-06 | CP-84 | CP-191144 | 0429 | 1 | B | Manual PLMN selection for RLOS | 16.2.0 | +| 2019-06 | CP-84 | CP-191131 | 0431 | 1 | F | Dynamic generation of SOR Information | 16.2.0 | +| 2019-06 | CP-84 | CP-191131 | 0432 | 1 | F | Emergency service handling for SOR | 16.2.0 | +| 2019-06 | CP-84 | CP-191131 | 0433 | | F | Scope update for RRC inactive | 16.2.0 | +| 2019-09 | CP-85 | CP-192072 | 0435 | 3 | F | Corrections for CAG selection | 16.3.0 | +| 2019-09 | CP-85 | CP-192072 | 0436 | 1 | F | Missing SNPN terms | 16.3.0 | +| 2019-09 | CP-85 | CP-192072 | 0437 | 1 | F | Corrections for SNPN selection | 16.3.0 | +| 2019-09 | CP-85 | CP-192072 | 0438 | 1 | F | Lists of temporarily and permanently forbidden SNPNs | 16.3.0 | +| 2019-09 | CP-85 | CP-192072 | 0439 | 2 | F | "5GS forbidden tracking areas for regional provision of service" and MS operating in SNPN access mode | 16.3.0 | +| 2019-09 | CP-85 | CP-192055 | 0440 | 4 | F | Interactions between SOR-AF and other core network entities | 16.3.0 | +| 2019-09 | CP-85 | CP-192055 | 0441 | | F | Clarification of possible PLMN/RAT selection due to cause value#15 | 16.3.0 | +| 2019-09 | CP-85 | CP-192071 | 0442 | 3 | F | eDRX/relaxed monitoring HPLMN scan conflicts | 16.3.0 | +| 2019-09 | CP-85 | CP-192055 | 0444 | 1 | F | Handling of SOR failure encountered in manual mode of operation | 16.3.0 | +| 2019-09 | CP-85 | CP-192072 | 0446 | 1 | F | Addition of unified access control configuration to the "list of subscriber data" for access to SNPNs | 16.3.0 | +| 2019-09 | CP-85 | CP-192055 | 0449 | 1 | F | OPLMN list handling | 16.3.0 | +| 2019-12 | CP-86 | CP-193092 | 0445 | 2 | F | Clarification on sending of REGISTRATION COMPLETE message for SOR during registration | 16.4.0 | +| 2019-12 | CP-86 | CP-193092 | 0448 | 2 | F | Periodic location registration for 5GS operation | 16.4.0 | +| 2019-12 | CP-86 | CP-193112 | 0451 | 3 | B | RLOS conditions for LR | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0453 | 1 | F | SNPN and credentials of AKA based authentication | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0454 | 1 | F | "5GS forbidden tracking areas for roaming" and MS operating in SNPN access mode | 16.4.0 | +| 2019-12 | CP-86 | CP-193092 | 0455 | | F | Forbidden PLMNs related updates | 16.4.0 | +| 2019-12 | CP-86 | CP-193092 | 0456 | | F | Corrections to SOR procedures | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0458 | | F | Manual CAG selection not allowed during emergency PDU session. | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0459 | 2 | F | Handling of the forbidden TAI list for regional provision of service and forbidden SNPN lists when the SIM is removed in case of AKA-based SNPN | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0460 | 2 | F | IMSI-based SUPI in an SNPN and impact to the "list of subscriber data" | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0461 | 1 | F | No suitable cell in an SNPN | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0462 | 1 | F | Resolution of editor's notes on states, figures and tables for SNPN | 16.4.0 | +| 2019-12 | CP-86 | CP-193092 | 0465 | 4 | F | Acquiring user location information for SOR | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0467 | | C | Handling of multiple entries with same SNPNt | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------|--------| +| 2019-12 | CP-86 | CP-193117 | 0468 | | F | Definitions and abbreviations update for SNPN Access Technology and other correction | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0469 | | F | Missing condition for entering limited service in SNPN access mode | 16.4.0 | +| 2019-12 | CP-86 | CP-193114 | 0470 | | F | Handling of CSG selection mode | 16.4.0 | +| 2019-12 | CP-86 | CP-193092 | 0474 | | F | Adding definition for SoR-AF function | 16.4.0 | +| 2019-12 | CP-86 | CP-193099 | 0475 | 2 | F | SOR - adding a reference to OTAF specification | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0477 | 1 | F | NAS providing AS with a "CAG information list" | 16.4.0 | +| 2019-12 | CP-86 | CP-193117 | 0478 | 1 | F | Clarification on figures for PLMN selection | 16.4.0 | +| 2019-12 | CP-86 | CP-193092 | 0479 | 2 | F | SOR call flow corrections in 23.122 | 16.4.0 | +| 2020-03 | CP-87e | CP-200110 | 0482 | | F | Streamlining RAT's that can be scanned after E-UTRAN disable due to no voice service | 16.5.0 | +| 2020-03 | CP-87e | CP-200110 | 0483 | | F | Emergency service missing condition for performing registration update | 16.5.0 | +| 2020-03 | CP-87e | CP-200110 | 0484 | 2 | F | Clarification of forbidden PLMNs list | 16.5.0 | +| 2020-03 | CP-87e | CP-200094 | 0485 | 3 | F | Update of steering of roaming information for different registration types | 16.5.0 | +| 2020-03 | CP-87e | CP-200110 | 0486 | 1 | F | Usage of SoR-AF function | 16.5.0 | +| 2020-03 | CP-87e | CP-200110 | 0488 | 4 | F | Correction to handling of a PDU session for emergency service at SOR | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0489 | | F | Clarification to manual CAG selection | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0491 | 1 | B | Limited Service state on CAG cell. | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0492 | 1 | F | Correction to Limited service state for SNPN | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0493 | 2 | F | Presentation of PLMN with non-CAG cells for manual selection | 16.5.0 | +| 2020-03 | CP-87e | CP-200124 | 0494 | 1 | F | Clarify that a UE operating in N1 mode do not attempt to access RLOS. | 16.5.0 | +| 2020-03 | CP-87e | CP-200124 | 0495 | 2 | B | Support of restriction on access to RLOS | 16.5.0 | +| 2020-03 | CP-87e | CP-200124 | 0496 | | B | Manual network selection procedure for access to RLOS | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0497 | 1 | F | Correction on term "shared network" definition for SNPN | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0498 | | C | UE identifier for SNPN | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0500 | | F | Determination of CAG cell | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0502 | 1 | F | List of SNPNs for which the N1 mode capability was disabled | 16.5.0 | +| 2020-03 | CP-87e | CP-200129 | 0503 | 1 | F | Display of the human readable name of an SNPN | 16.5.0 | +| 2020-03 | CP-87e | CP-200105 | 0504 | | F | "CAG information list" preventing selection of any available and allowable PLMN | 16.5.0 | +| 2020-06 | CP-88e | CP-201100 | 0481 | 5 | F | Correction for SoR-AF | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0499 | 7 | C | Manual CAG selection | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0508 | | F | SoR in HPLMN after registration | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0509 | 1 | F | Modification of exchanges between SOR-AF and UDM | 16.6.0 | +| 2020-06 | CP-88e | CP-201107 | 0510 | 1 | F | OTAF renamed to SP-AF | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0511 | 1 | C | Management of forbidden SNPNs list upon receipt of a non-integrity protected reject message | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0513 | | F | Correction of the handling of timer TG | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0517 | 1 | F | Correction on no suitable cell | 16.6.0 | +| 2020-06 | CP-88e | CP-201360 | 0518 | 5 | C | Presentation of Human readable name for CAG cell | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0522 | 2 | F | Sending CAG information list – option 1 | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0524 | | F | figures 1, 2a, 2b, 3 and table 2 not applicable in SNPN | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0525 | 1 | C | Selected CAG-ID from the NAS layer to the AS layer | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0526 | 1 | F | CAG selection is optional in the manual network selection mode | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0528 | 2 | F | correction to network selection in case of multiple subscribed SNPNs | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0529 | | F | Correction to Manual CAG selection procedure | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0530 | 1 | F | UDM support of communication with SOR-AF | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0532 | 1 | F | SOR-AF in scope | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0536 | 2 | F | Updates to SNPN selection | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0538 | | F | Storing the PLMN identity in the "forbidden PLMN list" for 5GMM cause #73 "Serving network not authorized" | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0539 | | F | Clarification of the use of T3245 | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0540 | | F | Reference correction for SNPN | 16.6.0 | +| 2020-06 | CP-88e | CP-201131 | 0544 | 1 | F | Clarification of cause #35 in limited service state | 16.6.0 | +| 2020-06 | CP-88e | CP-201314 | 0545 | 2 | F | Correction to CAG selection in automatic mode. | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0547 | | F | Resolving editor's note in Limited service condition on a CAG cell. | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0548 | 1 | F | Removal of selected CAG-ID in automatic selection mode. | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0549 | | F | Clarification to SNPN manual selection. | 16.6.0 | +| 2020-06 | CP-88e | CP-201135 | 0550 | 1 | F | Clarification to SNPN registration after SNPN selection. | 16.6.0 | +| 2020-06 | CP-88e | CP-201100 | 0552 | 2 | F | On the parameters provided to the SOR-AF from the UDM. | 16.6.0 | +| 2020-06 | CP-88e | CP-201107 | 0554 | | F | SP-AF services. | 16.6.0 | +| 2020-07 | CP-88e | | | | | Editorial corrections by rapporteur | 16.6.1 | +| 2020-09 | CP-89e | CP-202170 | 0527 | 5 | F | Human readable network name for SNPN | 16.7.0 | + +| | | | | | | | | +|----------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-09 | CP-89e | CP-202170 | 0542 | 2 | F | Alternative to CR#0514: Correction of the handling of timer TG for SNPNS | 16.7.0 | +| 2020-09 | CP-89e | CP-202170 | 0559 | | F | Correction of implementation of CP-201314 | 16.7.0 | +| 2020-09 | CP-89e | CP-202257 | 0561 | 3 | F | SUPI types of subscriber identifier in "list of subscriber data" | 16.7.0 | +| 2020-09 | CP-89e | CP-202149 | 0564 | 1 | F | Security checking of Steering of roaming | 16.7.0 | +| 2020-09 | CP-89e | CP-202149 | 0565 | | F | Steering of roaming to a forbidden PLMN | 16.7.0 | +| 2020-09 | CP-89e | CP-202170 | 0568 | 1 | F | Automatic selection with empty "CAG information list" | 16.7.0 | +| 2020-09 | CP-89e | CP-202170 | 0569 | | F | Correction for CAG selection | 16.7.0 | +| 2020-09 | CP-89e | CP-202149 | 0570 | 1 | F | Storage of SOR related information in the UDR | 16.7.0 | +| 2020-09 | CP-89e | CP-202149 | 0571 | | F | SOR-AF UDM exchanges alignment in after registration case | 16.7.0 | +| 2020-09 | CP-89e | CP-202170 | 0583 | | F | Resolution of Editors Note related to HRNN handling of CAG | 16.7.0 | +| 2020-09 | CP-89e | CP-202149 | 0584 | 3 | F | Storage of SOR related information in the UDM/UDR | 16.7.0 | +| 2020-09 | CP-89e | CP-202149 | 0585 | 1 | F | Editor's Note resolution for SOR | 16.7.0 | +| 2020-09 | CP-89e | CP-202173 | 0560 | | F | Periodic removal of "forbidden location areas for regional provision of service" | 17.0.0 | +| 2020-09 | CP-89e | CP-202175 | 0566 | 1 | B | Enhancement for CP-SOR for UE in connected mode | 17.0.0 | +| 2020-09 | CP-89e | CP-202175 | 0572 | 2 | B | Introducing the definition "Steering of roaming connected mode control information" | 17.0.0 | +| 2020-09 | CP-89e | CP-202173 | 0574 | 1 | F | Removal of a VPLMN from the forbidden PLMNs list upon T3247 expiry | 17.0.0 | +| 2020-09 | CP-89e | CP-202173 | 0580 | 1 | F | Clarification on the successfully received SoR case when UE is in manual mode | 17.0.0 | +| 2020-12 | CP-90e | CP-203168 | 0573 | 3 | D | Editorial corrections | 17.1.0 | +| 2020-12 | CP-90e | CP-203167 | 0587 | 2 | A | Correction of the Service Operation of SoR-AF | 17.1.0 | +| 2020-12 | CP-90e | CP-203181 | 0591 | 1 | B | Introducing new requirements for CP-SOR in connected mode | 17.1.0 | +| 2020-12 | CP-90e | CP-203181 | 0592 | 1 | B | Updating the requirements for CP-SOR in 5GS | 17.1.0 | +| 2020-12 | CP-90e | CP-203181 | 0593 | 2 | B | SOR-CMCI configuration and session handling for enhanced control plane SOR in connected mode | 17.1.0 | +| 2020-12 | CP-90e | CP-203167 | 0595 | 3 | A | Suspending transmission of 5GSM messages during SOR procedure | 17.1.0 | +| 2020-12 | CP-90e | CP-203218 | 0597 | 1 | A | Aligning to TS 22.261 requirements on manual CAG selection | 17.1.0 | +| 2020-12 | CP-90e | CP-203103 | 0600 | 5 | F | Handling of Higher Priority PLMN selection with the presence of "PLMNs where registration was aborted due to SOR" list | 17.1.0 | +| 2020-12 | CP-90e | CP-203167 | 0601 | 1 | A | In SoR error cases, UE to always send Registration Complete at the end of Registration procedure if UE is either in Manual mode of operation or camped in UPLMN | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0605 | 1 | F | Use of T3245 in an SNPNS | 17.1.0 | +| 2020-12 | CP-90e | CP-203167 | 0606 | | A | Clarification on High Priority Search in 5GMM-Connected Mode with RRC Inactive | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0611 | 3 | B | Initial CAG information list | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0613 | 5 | F | No need to release NAS signalling connection when the selected VPLMN is the highest priority PLMN | 17.1.0 | +| 2020-12 | CP-90e | CP-203181 | 0615 | 1 | F | Obtaining SOR-CMCI | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0618 | 1 | F | Handling of periodic registration timer expiry | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0619 | | F | Periodic PLMN searches in MICO mode | 17.1.0 | +| 2020-12 | CP-90e | CP-203188 | 0620 | | A | Add reference to 24.587 and 38.331 in V2X triggered PLMN selection | 17.1.0 | +| 2020-12 | CP-90e | CP-203167 | 0621 | 1 | A | Skipping step 9 if UDM has not requested an acknowledgment from the UE | 17.1.0 | +| 2020-12 | CP-90e | CP-203215 | 0624 | 1 | F | CAG support and CAG information are only applicable when MS is in 5GS | 17.1.0 | +| 2020-12 | CP-90e | CP-203102 | 0629 | 3 | F | Handling of "PLMNs where registration was aborted due to SOR" list | 17.1.0 | +| 2020-12 | CP-90e | CP-203101 | 0630 | 2 | F | Conflict between PLMN reselection due to SOR and RAT disabling due to missing Voice support | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0632 | 1 | F | The definition of non-CAG cell | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0635 | 1 | F | Adding the definition of CAG cell | 17.1.0 | +| 2020-12 | CP-90e | CP-203214 | 0639 | 1 | F | Secured packet upload of ME | 17.1.0 | +| 2020-12 | CP-90e | CP-203165 | 0640 | 3 | F | Sending acknowledgement for steering of roaming procedure after registration | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0641 | 1 | F | Clarification of Country definition | 17.1.0 | +| 2020-12 | CP-90e | CP-203168 | 0643 | 1 | F | REGISTRATION COMPLETE sending | 17.1.0 | +| 2021-012 | | | | | | Deletion of extra instances of figure C.2.1 | 17.1.1 | +| 2021-03 | CP-91e | CP-210116 | 0602 | 6 | F | Handling of PLMN selection with presence of PLMNs where registration was aborted due to SOR list | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0644 | 1 | B | Handling and coordination of multiple Tsor-cm timers | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0645 | 3 | B | Setting Tsor-cm timer for new PDU session or service | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0646 | 3 | B | Removing resolved Editor's Notes and general corrections | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0647 | 1 | F | No de-registration signalling when Tsor-cm stops due to going to idle mode | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0651 | 1 | F | Configuring UE with SOR-CMCI | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0652 | 1 | B | Configuration of services exempted from release due to SOR at the UE | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0653 | 1 | B | Storage of SOR-CMCI in the UE | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0654 | 1 | F | Correction of CP-SOR | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0655 | 1 | F | Providing SOR-CMCI in figures | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------|--------| +| 2021-03 | CP-91e | CP-210122 | 0656 | 1 | F | UDM obtaining SOR-CMCI | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0657 | 3 | B | UE behavior upon receiving new timer valuer for Tsor-cm timer | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0658 | 1 | B | Handling of timer Tsor-cm when changing the network selection mode to manual mode | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0660 | 1 | F | PLMN selection when the emergency PDU session is released | 17.2.0 | +| 2021-03 | CP-91e | CP-210114 | 0662 | | A | Correction of handling of CAG information from a "PLMN equivalent to the HPLMN" | 17.2.0 | +| 2021-03 | CP-91e | CP-210135 | 0669 | 1 | D | Inclusive language review | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0670 | 1 | F | Including the SOR-CMCI in the steering of roaming information | 17.2.0 | +| 2021-03 | CP-91e | CP-210133 | 0672 | | D | Editorial corrections | 17.2.0 | +| 2021-03 | CP-91e | CP-210116 | 0673 | 1 | F | Clarifications on PLMN and SNPN URSP storage - 23.122 part | 17.2.0 | +| 2021-03 | CP-91e | CP-210116 | 0674 | | F | Correction to automatic PLMN selection rule for a data centric MS | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0675 | 1 | F | Clarification on SOR with SOR-CMCI and emergency PDU session | 17.2.0 | +| 2021-03 | CP-91e | CP-210122 | 0676 | 2 | B | Prevention of SOR-CMCI provisioning when a UE does not support SOR-CMCI | 17.2.0 | +| 2021-06 | CP-92e | CP-211128 | 0708 | 1 | A | PLMN selection triggered by V2X communication over PC5 | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0663 | 3 | C | SNPN selection for access to SNPNs using credentials from an entity separate from the SNPN | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0694 | 1 | B | Lists of 5GS forbidden tracking areas | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0695 | 1 | B | Forbidden SNPNs | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0702 | 1 | C | SUPI for an SNPN using credentials owned by an SNPN CH | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0703 | 5 | C | Emergency registration to an SNPN by a UE in the limited service state or no SIM state | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0710 | 1 | B | Mobility registration update upon entering a new SNPN | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0711 | 1 | B | Selection for onboarding in SNPN | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0713 | 1 | B | SNPN selection for voice centric UE | 17.3.0 | +| 2021-06 | CP-92e | CP-211137 | 0719 | | B | Adding default configured NSSAI in the "list of subscriber data" | 17.3.0 | +| 2021-06 | CP-92e | CP-211144 | 0712 | | F | Removal of editor's note on CAG information list in USIM | 17.3.0 | +| 2021-06 | CP-92e | CP-211145 | 0714 | 1 | F | The handling of wildcard CAG ID-solution#1 | 17.3.0 | +| 2021-06 | CP-92e | CP-211146 | 0718 | 1 | D | Editorial corrections in TS 23.122 | 17.3.0 | +| 2021-06 | CP-92e | CP-211147 | 0724 | 1 | F | Send REGISTRATION COMPLETE message only if the SOR information is received | 17.3.0 | +| 2021-06 | CP-92e | CP-211150 | 0716 | 2 | F | Clarification to few scenarios related to manual CAG selection | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0679 | 1 | F | General corrections and alignments for SOR | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0684 | 1 | F | Clarify the UE behaviour when the emergency PDU session is released | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0685 | 1 | F | Clarify the UE behaviour when the the last running Tsor-cm timer expires | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0687 | 1 | B | UE behavior upon updating "user controlled list of services exempted from release | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0688 | 1 | F | SOR-CMCI provision with legacy AMF | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0691 | 1 | B | Resolve EN on the SOR-CMCI storage in the UE | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0692 | 1 | F | Clarification on handling the storage of the SOR-CMCI in the ME | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0696 | 1 | F | Preventing configuring SOR-CMCI when the UE does not support SOR-CMCI | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0697 | 1 | F | Consider stored/configured SOR-CMCI information when processing REFRESH due to SOR | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0699 | 1 | F | Maintaining the user controlled list of services exempted from release due to SOR | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0700 | 1 | F | Setting the timer value of Tsor-cm | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0704 | 1 | C | Correction of setting the SOR-CMCI criteria | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0705 | 1 | C | Correcting the SOR-CMCI format sent to the UE | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0717 | 1 | F | Removal of ENs related to SOR-CMCI criteria | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0720 | 1 | F | Performing PLMN selection after the emergency PDU session is released | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0721 | 2 | C | Radio link failure during Tsor timer is running | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0726 | 1 | C | Remove unnecessary requirement on handling on receipt of SOR-CMCI | 17.3.0 | +| 2021-06 | CP-92e | CP-211151 | 0727 | 1 | B | Storage of user controlled list of services exempted from release due to SOR | 17.3.0 | +| 2021-06 | CP-92e | CP-211152 | 0681 | 1 | B | Access Technology Identifier "satellite NG-RAN" | 17.3.0 | +| 2021-09 | CP-93e | CP-212158 | 0777 | 1 | F | No use of non-globally-unique SNPN identity for accessing SNPN using credentials from CH | 17.4.0 | +| 2021-09 | CP-93e | CP-212230 | 0739 | 3 | F | Attempt to select a higher priority PLMN/RAT combination when a PLMN/RAT combination is re-enabled | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-09 | CP-93e | CP-212141 | 0731 | 1 | C | Corrections to the procedure in C.4.3 and other editorial corrections | 17.4.0 | +| 2021-09 | CP-93e | CP-212141 | 0732 | - | F | Removing resolved Editor's Notes in Annex C | 17.4.0 | +| 2021-09 | CP-93e | CP-212125 | 0734 | 1 | B | Automatic PLMN selection updates for MINT | 17.4.0 | +| 2021-09 | CP-93e | CP-212152 | 0735 | - | F | Resolution of an EN about a range of CAG IDs | 17.4.0 | +| 2021-09 | CP-93e | CP-212140 | 0737 | 1 | F | Correction on the description of TJ in SNPN selection-Rel17 | 17.4.0 | +| 2021-09 | CP-93e | CP-212125 | 0742 | 2 | B | Provisioning of list of PLMN(s) to be used in disaster condition in the UE | 17.4.0 | +| 2021-09 | CP-93e | CP-212155 | 0744 | 1 | F | Clarification for Manual PLMN selection when emergency PDU or PDN connection exists | 17.4.0 | +| 2021-09 | CP-93e | CP-212124 | 0745 | 1 | B | Adding support for PWS in SNPNs | 17.4.0 | +| 2021-09 | CP-93e | CP-212141 | 0746 | 1 | F | Correction to SOR-CMCI attribute type criterion. | 17.4.0 | +| 2021-09 | CP-93e | CP-212141 | 0748 | - | F | Correction of secured packet definition | 17.4.0 | +| 2021-09 | CP-93e | CP-212117 | 0749 | 1 | A | Miscellaneous changes on PLMN selection triggered by V2X communication in 5G | 17.4.0 | +| 2021-09 | CP-93e | CP-212134 | 0751 | 1 | B | PLMN selection triggered by ProSe communications over NR-PC5 | 17.4.0 | +| 2021-09 | CP-93e | CP-212129 | 0756 | - | F | Reference for the abbreviation of GIN | 17.4.0 | +| 2021-09 | CP-93e | CP-212125 | 0757 | 2 | B | Higher priority PLMN search in disaster roaming scenario | 17.4.0 | +| 2021-09 | CP-93e | CP-212155 | 0758 | 1 | F | The condition to store the PLMN identity in the list of PLMNs where registration was aborted due to SOR | 17.4.0 | +| 2021-09 | CP-93e | CP-212141 | 0760 | 1 | F | Tsor-cm not related with PDU sessions | 17.4.0 | +| 2021-09 | CP-93e | CP-212141 | 0761 | 1 | F | The timer value for Tsor-cm being zero | 17.4.0 | +| 2021-09 | CP-93e | CP-212141 | 0762 | 1 | F | SOR-CMCI content definition | 17.4.0 | +| 2021-09 | CP-93e | CP-212129 | 0764 | 2 | F | Attempt to obtain onboarding services during the No SIM state | 17.4.0 | +| 2021-09 | CP-93e | CP-212129 | 0765 | - | F | Correction on a UE supporting access to an SNPN using credentials from a CH configured with the SNPN selection parameters | 17.4.0 | +| 2021-09 | CP-93e | CP-212129 | 0766 | 1 | F | Re-enable SNPN access mode after emergency call is finished | 17.4.0 | +| 2021-09 | CP-93e | CP-212140 | 0771 | 1 | F | Camp on acceptable cell no need consider CAG information | 17.4.0 | +| 2021-09 | CP-93e | CP-212141 | 0774 | - | F | Removal of editor's notes on SOR-CMCI | 17.4.0 | +| 2021-09 | CP-93e | CP-212129 | 0776 | - | F | Obtaining emergency call in SNPN limited service state | 17.4.0 | +| 2021-12 | CP-94e | CP-213034 | 0837 | - | F | Resolution of an EN about CAG-ID range-23.122 | 17.5.0 | +| 2021-12 | CP-94e | CP-213037 | 0778 | 1 | F | IMSI based SUPI | 17.5.0 | +| 2021-12 | CP-94e | CP-213037 | 0822 | 2 | F | Pre-configured AIs, URSP, and default configured NSSAI in an SNPN accessed using the PLMN subscription | 17.5.0 | +| 2021-12 | CP-94e | CP-213037 | 0790 | 5 | B | Use of SOR to update the credentials holder controlled prioritized lists of preferred SNPNs and GINs | 17.5.0 | +| 2021-12 | CP-94e | CP-213048 | 0830 | 2 | F | UDM not interrogating SOR-AF if no acknowledgement received from UE | 17.5.0 | +| 2021-12 | CP-94e | CP-213048 | 0834 | 1 | F | Acknowledgment for the security packet of SOR information | 17.5.0 | +| 2021-12 | CP-94e | CP-213048 | 0835 | 1 | F | Clarification when receiving no change of Operator Controlled PLMN | 17.5.0 | +| 2021-12 | CP-94e | CP-213048 | 0850 | 1 | F | Deletion of PLMNs where registration was aborted due to SOR | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0788 | 3 | B | Update of UE provisioning information for disaster roaming | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0792 | 1 | B | Initiation of location registration for MINT | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0794 | 3 | B | Clarification regarding reselection to EPLMN in manual mode disaster roaming. | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0795 | 3 | B | Sending indication to user regarding disaster roaming support in Manual mode. | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0796 | 3 | B | Clarification of provision of 'list of PLMNs to be used in Disaster condition during registration procedure. | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0808 | 1 | F | UE leaving manual mode when the RPLMN is considered as the PLMN with disaster condition | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0810 | 1 | F | Ignore RPLMN if UE not eligible for disaster roaming. | 17.5.0 | +| 2021-12 | CP-94e | CP-213055 | 0841 | 1 | F | Disaster related indication | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0783 | 1 | C | Removal of the user controlled list of services exempted from release due to SOR | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0784 | 3 | C | Clarifying the conditions when SOR-CMCI is empty | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0785 | 3 | F | SOR-CMCI rule for SMS | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0798 | 1 | F | Clarification on match all type criterion in SOR-CMCI | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0799 | 1 | F | Correction on timers when applying SOR-CMCI | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0800 | 1 | F | USIM and SOR-CMCI in after registration scenario | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0801 | 1 | D | Corrections in Annex C of 23.122 | 17.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------|--------| +| 2021-12 | CP-94e | CP-213056 | 0805 | 1 | F | Release of high priority access PDU sessions while receiving SOR-CMCI | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0806 | 1 | D | ME supporting the SOR-CMCI | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0809 | 1 | B | SOR-CMCI configuration for SOR security check failure | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0814 | 1 | F | Trigger on providing UE with SOR-CMCI after registration | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0815 | 1 | F | Clarification on SSCMI | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0816 | 2 | F | Clarification for storage of Operator Controlled PLMN list and SOR-CMCI along with SUPI | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0827 | 1 | C | Correcting when the HPLMN requests ACK while supporting SOR-CMCI | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0831 | - | F | Clarification on timer associated with SST and SD | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0833 | 1 | F | Update of conditions to use Operator Controlled PLMN Selector with Access Technology list stored in the ME | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0843 | 1 | F | Correction on content of SOR information | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0844 | - | F | Store SOR-CMCI in ME indicator only in plain text | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0845 | 1 | F | Providing UE with SOR-CMCI in secured packet after registration | 17.5.0 | +| 2021-12 | CP-94e | CP-213056 | 0846 | 2 | F | Providing UE with SOR-CMCI no SOR-CMCI rules included | 17.5.0 | +| 2021-12 | CP-94e | CP-213057 | 0807 | - | F | Access Technology Identifier including satellite NG-RAN | 17.5.0 | +| 2022-03 | CP-95e | CP-220229 | 0883 | 1 | A | RID for SNPN UEs | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0863 | - | F | Resolution of editor's note in clause 3.5 | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0864 | - | F | Resolution of editor's note in clause 4.9.4 | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0865 | - | F | Resolution of editor's note in clause 4.9.3.1.3 | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0867 | - | F | Onboarding SNPN network selection information | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0868 | - | B | PLMN/SNPN selection upon stopping/starting operating in SNPN access mode | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0791 | 6 | C | Allowing SNPN-enabled UE not operating in SNPN access mode to obtain emergency services in any SNPN | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0858 | 1 | B | Enabling update of SOR-SNPN-SI in a PLMN | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0859 | 1 | C | UE configuration for warning message reception in SNPNs | 17.6.0 | +| 2022-03 | CP-95e | CP-220236 | 0872 | 1 | B | SNPN selection for onboarding services with lists of forbidden SNPNs | 17.6.0 | +| 2022-03 | CP-95e | CP-220237 | 0866 | 1 | F | Resolution of editor's note in clause 4.9.3.1.4 | 17.6.0 | +| 2022-03 | CP-95e | CP-220237 | 0862 | 1 | B | Indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure | 17.6.0 | +| 2022-03 | CP-95e | CP-220237 | 0884 | - | F | Editor's note in clause 4.9.3.0 | 17.6.0 | +| 2022-03 | CP-95e | CP-220237 | 0896 | - | F | No SOR-SNPN-SI via CP-SoR for CH with AAA server | 17.6.0 | +| 2022-03 | CP-95e | CP-220238 | 0892 | 1 | F | Exiting manual network SNPN selection mode by a UE in the limited service state | 17.6.0 | +| 2022-03 | CP-95e | CP-220238 | 0885 | 1 | B | Enabling update of list of preferred PLMNs in an SNPN | 17.6.0 | +| 2022-03 | CP-95e | CP-220238 | 0893 | 1 | F | Correction for voice-centric UEs | 17.6.0 | +| 2022-03 | CP-95e | CP-220245 | 0861 | 1 | F | L2 remote UE PLMN selection | 17.6.0 | +| 2022-03 | CP-95e | CP-220248 | 0826 | 3 | F | SOR signalling connection handling in case of an emergency session | 17.6.0 | +| 2022-03 | CP-95e | CP-220248 | 0880 | 1 | F | Clarification to when the UE performs higher priority PLMN selection | 17.6.0 | +| 2022-03 | CP-95e | CP-220260 | 0879 | 1 | F | Clarify condition to use MINT based on non-3GPP access | 17.6.0 | +| 2022-03 | CP-95e | CP-220260 | 0873 | 1 | B | Handling of forbidden PLMN list for disaster roaming | 17.6.0 | +| 2022-03 | CP-95e | CP-220260 | 0870 | 2 | F | HPLMN control in the roaming area. | 17.6.0 | +| 2022-03 | CP-95e | CP-220260 | 0891 | 1 | F | Pre-configuration of 'list of PLMNs to be used in disaster condition' in USIM. | 17.6.0 | +| 2022-03 | CP-95e | CP-220260 | 0895 | 1 | F | Storage of 'List of PLMNs to be used in disaster condition' in NVM | 17.6.0 | +| 2022-03 | CP-95e | CP-220260 | 0876 | 2 | F | Clarification on the applicability of MINT in a CAG cell. | 17.6.0 | +| 2022-03 | CP-95e | CP-220261 | 0852 | 1 | F | Correcting the service operation leading to deleting the ME support of SOR-CMCI | 17.6.0 | +| 2022-03 | CP-95e | CP-220261 | 0853 | 1 | F | Corrections in the SOR procedures after registration | 17.6.0 | +| 2022-03 | CP-95e | CP-220261 | 0701 | 4 | F | Tsor-cm timer handling in case of IRAT transitions | 17.6.0 | +| 2022-03 | CP-95e | CP-220261 | 0874 | 1 | F | HPLMN indication not apply for secured packet | 17.6.0 | +| 2022-03 | CP-95e | CP-220261 | 0854 | 1 | F | Including the Store SOR-CMCI in ME indicator in the secured packet | 17.6.0 | +| 2022-03 | CP-95e | CP-220261 | 0889 | 1 | F | Handling of MT services in SOR-CMCI - 23.122 | 17.6.0 | +| 2022-03 | CP-95e | CP-220261 | 0894 | 1 | F | Tsor-cm for security check failure upon successful check of the received SOR | 17.6.0 | +| 2022-03 | CP-95e | CP-220262 | 0877 | - | B | Adding requirements for NR RedCap devices | 17.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------|--------| +| 2022-03 | CP-95e | CP-220265 | 0825 | 4 | C | PLMN selection for satellite access | 17.6.0 | +| 2022-03 | CP-95e | CP-220265 | 0828 | 4 | B | Higher priority PLMN search for MS in satellite NG-RAN access | 17.6.0 | +| 2022-03 | CP-95e | CP-220265 | 0887 | 1 | B | Interval of Time between Searches for Higher Priority PLMN via Satellite NG-RAN | 17.6.0 | +| 2022-03 | CP-95e | CP-220265 | 0741 | 7 | B | Validity of cause code #78 | 17.6.0 | +| 2022-06 | CP-96 | CP-221190 | 0905 | 3 | F | Configuration for anonymous SUCI usage | 17.7.0 | +| 2022-06 | | | | | | set of CR Pack approved CRs were not implemented by mistake. All CRs below dated 2022-06 belong to this group. | 17.7.1 | +| 2022-06 | CP-96 | CP-221203 | 0930 | - | F | Editor's notes in clause 1.2 and clause C.7 | 17.7.1 | +| 2022-06 | CP-96 | CP-221203 | 0931 | - | F | Editor's note in C.5 | 17.7.1 | +| 2022-06 | CP-96 | CP-221203 | 0935 | 1 | F | Removal of Editor's note on encoding of the indication of whether the MS shall ignore all warning messages in an SNPN in the USIM | 17.7.1 | +| 2022-06 | CP-96 | CP-221212 | 0933 | 1 | F | Manual Selection of a non-member CAG cell | 17.7.1 | +| 2022-06 | CP-96 | CP-221212 | 0937 | 1 | F | Remove manual selected PLMN from the forbidden PLMNs for GPRS service list | 17.7.1 | +| 2022-06 | CP-96 | CP-221212 | 0939 | 1 | F | Procedure name correction | 17.7.1 | +| 2022-06 | CP-96 | CP-221213 | 0936 | 1 | F | Release N1 NAS signalling connection when security check fails | 17.7.1 | +| 2022-06 | CP-96 | CP-221213 | 0942 | 1 | F | At switch on and no RPLMN in manual mode when UE support CAG | 17.7.1 | +| 2022-06 | CP-96 | CP-221219 | 0869 | 3 | F | MINT and higher priority PLMN Selection | 17.7.1 | +| 2022-06 | CP-96 | CP-221219 | 0906 | 1 | B | Disaster related indication and UE determined PLMN with disaster condition | 17.7.1 | +| 2022-06 | CP-96 | CP-221219 | 0911 | 1 | F | Removing the editor's note related to CT6 | 17.7.1 | +| 2022-06 | CP-96 | CP-221219 | 0923 | 1 | F | Clarification on provision of disaster romaing related information | 17.7.1 | +| 2022-06 | CP-96 | CP-221219 | 0932 | 2 | F | UE without RPLMN | 17.7.1 | +| 2022-06 | CP-96 | CP-221219 | 0943 | 1 | F | Clarification to Manual CAG selection | 17.7.1 | +| 2022-06 | CP-96 | CP-221220 | 0924 | 1 | F | Correction on Steering of Roaming information | 17.7.1 | +| 2022-06 | CP-96 | CP-221220 | 0925 | 1 | F | Starting Tsor-cm timer associated with SOR security check not successful criterion | 17.7.1 | +| 2022-06 | CP-96 | CP-221220 | 0928 | 1 | F | Correction that UE needs to wait for UICC to reply to network | 17.7.1 | +| 2022-06 | CP-96 | CP-221220 | 0929 | 1 | F | Clarification when no change to SOR-SNPI-SI | 17.7.1 | +| 2022-06 | CP-96 | CP-221221 | 0910 | 4 | C | Handling of discontinuous coverage | 17.7.1 | +| 2022-06 | CP-96 | CP-221221 | 0914 | 1 | B | PLMN selection for satellite E-UTRAN access | 17.7.1 | +| 2022-06 | CP-96 | CP-221221 | 0917 | - | F | Availability of a PLMN via satellite E-UTRAN | 17.7.1 | +| 2022-06 | CP-96 | CP-221224 | 0900 | - | F | Correction for CR 0828, deletion of moved sentence | 17.7.1 | +| 2022-06 | CP-96 | CP-221224 | 0909 | 1 | F | Correction to the rules for higher priority PLMN selection in VPLMN | 17.7.1 | +| 2022-06 | CP-96 | CP-221224 | 0916 | - | F | Availability of a PLMN via satellite NG-RAN | 17.7.1 | +| 2022-06 | CP-96 | CP-221224 | 0941 | 1 | F | Storage Information alignment on list of PLMNs not allowed to operate at the present UE location | 17.7.1 | +| 2022-06 | CP-96 | CP-221241 | 0907 | - | F | PLMN selection based on RRC container from L2 relay | 17.7.1 | +| 2022-06 | CP-96 | CP-221249 | 0901 | 1 | F | Editor's note in C.1.2 | 17.7.1 | +| 2022-06 | CP-96 | CP-221249 | 0902 | 1 | F | Access identity applicability in non-subscribed SNPN | 17.7.1 | +| 2022-06 | CP-96 | CP-221249 | 0903 | - | F | Editor's note in clause 4.9.3.0 | 17.7.1 | +| 2022-06 | CP-96 | CP-221249 | 0915 | 1 | F | Signalling UE support for SOR-SNPN-SI in SOR ACK | 17.7.1 | +| 2022-06 | CP-96 | CP-221249 | 0920 | 1 | F | URSP rules for SNPN | 17.7.1 | +| 2022-09 | CP-97e | CP-222137 | 0945 | - | F | Default UE credentials for primary authentication | 17.8.0 | +| 2022-09 | CP-97e | CP-222137 | 0946 | 1 | F | Correction in configuration for anonymous SUCI usage | 17.8.0 | +| 2022-09 | CP-97e | CP-222137 | 0964 | 1 | F | Perform automatic network selection in SNPN access mode | 17.8.0 | +| 2022-09 | CP-97e | CP-222147 | 0950 | 1 | F | Suspension of NAS signalling during SOR triggered higher priority PLMN selection | 17.8.0 | +| 2022-09 | CP-97e | CP-222152 | 0958 | 1 | F | Disaster related indication semantic update | 17.8.0 | +| 2022-09 | CP-97e | CP-222153 | 0962 | 1 | F | Clarification on UE behavior due to handover | 17.8.0 | +| 2022-09 | CP-97e | CP-222153 | 0965 | - | F | Correction on UE behavior with no SOR-CMCI in ME | 17.8.0 | +| 2022-09 | CP-97e | CP-222156 | 0960 | 1 | F | UE operation in terms of a VPLMN through satellite NG-RAN access with a shared MCC | 17.8.0 | +| 2022-09 | CP-97e | CP-222159 | 0951 | 1 | F | Clarification on the timer handling for #78 | 17.8.0 | +| 2022-09 | CP-97e | CP-222159 | 0956 | 1 | F | Update of conditions for deleting entries in # 78 list to align with 24.501 | 17.8.0 | +| 2022-09 | CP-97e | CP-222152 | 0947 | 1 | F | Correction for PLMN with disaster condition | 18.0.0 | +| 2022-09 | CP-97e | CP-222165 | 0968 | 1 | F | Clarification on first attempt for higher priority search | 18.0.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|--------------------------------------------------------------------------------------|--------| +| 2022-09 | CP-97e | CP-222165 | 0967 | 1 | F | Clarification on IMS registration related signalling | 18.0.0 | +| 2022-09 | CP-97e | CP-222165 | 0969 | 1 | F | Clarification on the storage to NVM in the ME | 18.0.0 | +| 2022-09 | CP-97e | CP-222172 | 0966 | - | D | Fixing unnecessary capitalization in procedures naming and other corrections | 18.0.0 | +| 2022-09 | CP-97e | CP-222185 | 0961 | 2 | F | Timer T handling | 18.0.0 | +| 2022-09 | CP-97e | CP-222200 | 0949 | 1 | F | Correction to the handling of PSM and MICO mode | 18.0.0 | +| 2022-09 | CP-97e | CP-222234 | 0948 | 1 | F | Correction on manual mode PLMN selection state diagram | 18.0.0 | +| 2022-12 | CP-98e | CP-223133 | 0976 | 1 | A | Correction to name of List of PLMNs offering disaster roaming services | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 0977 | 2 | F | Correction to mode switching between SNPN and PLMN modes for emergency services | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 0978 | 1 | F | Correction to steering of UE in SNPN after registration | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 0979 | 1 | F | Manual PLMN selection to HPLMN/EHPLMN when MS supports CAG | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 0980 | | F | Correction on reference no. of 33.501 | 18.1.0 | +| 2022-12 | CP-98e | CP-223115 | 0984 | 1 | A | Correct the value of higher priority PLMN search timer T | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 0986 | 2 | F | Providing a geographical location to the AS-23.122 | 18.1.0 | +| 2022-12 | CP-98e | CP-223133 | 0990 | 1 | A | Allowed access attempts while timer precluding registration is running | 18.1.0 | +| 2022-12 | CP-98e | CP-223133 | 0992 | 1 | A | State while timer precluding registration is running | 18.1.0 | +| 2022-12 | CP-98e | CP-223148 | 0995 | 1 | A | ProSe communications in limited service states | 18.1.0 | +| 2022-12 | CP-98e | CP-223117 | 0997 | 1 | A | Postponing periodic PLMN reselection attempts for broadcast MBS services | 18.1.0 | +| 2022-12 | CP-98e | CP-223122 | 0998 | 1 | A | Clarification on secured packet is provided by HPLMN in SNPN access mode R18 | 18.1.0 | +| 2022-12 | CP-98e | CP-223129 | 1000 | 2 | A | Clarification regarding deactivation of the access stratum in discontinuous coverage | 18.1.0 | +| 2022-12 | CP-98e | CP-223122 | 1002 | 1 | A | UE configuration with protection scheme for concealing the SUPI | 18.1.0 | +| 2022-12 | CP-98e | CP-223120 | 1003 | 2 | B | Equivalent SNPN usage in SNPN selection | 18.1.0 | +| 2022-12 | CP-98e | CP-223120 | 1004 | | B | Equivalent SNPN usage in UAC configuration validity | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 1006 | 1 | F | Access mode during SNPN onboarding. | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 1007 | 1 | F | Perform SNPN selection in limited service state. | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 1008 | | F | Common requirements on satellite access technologies | 18.1.0 | +| 2022-12 | CP-98e | CP-223122 | 1010 | 1 | A | UE behavior when receiving unsuccessful security check SOR information R18 | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 1012 | 1 | F | No suppress of NAS signalling transmission for purpose of emergency services R18 | 18.1.0 | +| 2022-12 | CP-98e | CP-223157 | 1014 | 1 | F | Handling for the running Tsor-cm timer when security check fail | 18.1.0 | +| 2022-12 | CP-98e | CP-223115 | 1016 | | F | Correction to #78 timer handling | 18.1.0 | +| 2022-12 | CP-98e | CP-223144 | 1017 | | F | Correction to #78 timer handling | 18.1.0 | +| 2022-12 | CP-98e | CP-223239 | 1021 | 1 | F | Clarification on the UE behaviour upon receiving "do not store SOR-CMCI in ME" | 18.1.0 | +| 2023-03 | CP-99 | CP-230285 | 1022 | - | F | Correction for using the stored SOR-CMCI in the UE | 18.2.0 | +| 2023-03 | CP-99 | CP-230231 | 1037 | - | B | Equivalent SNPNs: forbidden SNPNs in TS 23.122 | 18.2.0 | +| 2023-03 | CP-99 | CP-230215 | 1018 | 2 | F | Clarification on #11, #35 with integrity protection in HPLMN | 18.2.0 | +| 2023-03 | CP-99 | CP-230231 | 1049 | - | F | Single CH-controlled prioritized list of preferred SNPNs/GINs | 18.2.0 | +| 2023-03 | CP-99 | CP-230231 | 1050 | - | F | SOR information delivery via an SNPN | 18.2.0 | +| 2023-03 | CP-99 | CP-230278 | 1028 | 1 | F | Equivalent SNPNs: completion of selection | 18.2.0 | +| 2023-03 | CP-99 | CP-230278 | 1036 | 1 | B | Equivalent SNPNs: 5GS forbidden tracking areas in TS 23.122 | 18.2.0 | +| 2023-03 | CP-99 | CP-230278 | 1038 | 2 | B | Equivalent SNPN information provided to lower layers for cell reselection | 18.2.0 | +| 2023-03 | CP-99 | CP-230214 | 1059 | 3 | F | Clarification of USAT REFRESH command qualifier of type of Steering of Roaming | 18.2.0 | +| 2023-03 | CP-99 | CP-230278 | 1039 | 2 | B | SOR-SNPN-SI for access for localized services in SNPN | 18.2.0 | +| 2023-03 | CP-99 | CP-230278 | 1029 | 4 | B | Access for localized services | 18.2.0 | +| 2023-03 | CP-99 | CP-230278 | 1035 | 1 | F | Term reference for SNPN access mode | 18.2.0 | +| 2023-03 | CP-99 | CP-230265 | 1026 | 1 | B | Enhanced CAG selection - additional information | 18.2.0 | +| 2023-03 | CP-99 | CP-230265 | 1027 | 1 | B | Enhanced CAG selection - enforcement in idle mode procedures | 18.2.0 | +| 2023-03 | CP-99 | CP-230319 | 0952 | 13 | B | Signal level enhanced network selection requirements for PLMN selection | 18.2.0 | +| 2023-03 | CP-99 | CP-230209 | 1031 | 2 | F | Emergency service and limited service state for satellite access | 18.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | CP-99 | CP-230317 | 0985 | 10 | B | Updates to Automatic PLMN Selection for SENSE | 18.2.0 | +| 2023-06 | CP-100 | CP-231232 | 1061 | 2 | F | Handling of forbidden PLMN lists when MS is in manual mode | 18.3.0 | +| 2023-06 | CP-100 | CP-231271 | 1066 | 1 | B | Periodic PLMN searches when unavailability period is activated | 18.3.0 | +| 2023-06 | CP-100 | CP-231217 | 1075 | 1 | F | Handling last registered SNPN | 18.3.0 | +| 2023-06 | CP-100 | CP-231232 | 1076 | 1 | F | SOR related information in list of subscriber data for SNPN | 18.3.0 | +| 2023-06 | CP-100 | CP-231238 | 1090 | 1 | B | Forbidden SNPN lists for localized services | 18.3.0 | +| 2023-06 | CP-100 | CP-231217 | 1080 | 1 | F | Correction to SOR for SNPN during registration | 18.3.0 | +| 2023-06 | CP-100 | CP-231217 | 1087 | 1 | F | Clarification on the deletion of PLMNs where registration was aborted due to SOR | 18.3.0 | +| 2023-06 | CP-100 | CP-231270 | 1073 | 1 | B | Adding USAT REFRESH for updating operator threshold for SENSE | 18.3.0 | +| 2023-06 | CP-100 | CP-231238 | 1068 | 1 | B | SNPN selection for the localized services | 18.3.0 | +| 2023-06 | CP-100 | CP-231232 | 1091 | - | F | Handling of the list of forbidden PLMN for GPRS service when MS is in manual mode | 18.3.0 | +| 2023-06 | CP-100 | CP-231232 | 1095 | - | D | Reordering of definitions | 18.3.0 | +| 2023-06 | CP-100 | CP-231277 | 1100 | - | B | PLMN selection triggered by A2X communication over PC5 | 18.3.0 | +| 2023-06 | CP-100 | CP-231232 | 1118 | - | F | Restricting manual selection during emergency services | 18.3.0 | +| 2023-06 | CP-100 | CP-231270 | 1005 | 7 | B | Periodic attempts for signal level enhanced network selection | 18.3.0 | +| 2023-06 | CP-100 | CP-231270 | 1072 | 2 | B | Resolution of editor's note on updation of operator threshold via CP-SOR | 18.3.0 | +| 2023-06 | CP-100 | CP-231238 | 1114 | 1 | F | Removing references of SNPN access mode. | 18.3.0 | +| 2023-06 | CP-100 | CP-231239 | 1083 | 3 | B | SNPN manual selection and credentials holder controlled prioritized list of preferred SNPNs and GINs for access for localized services in SNPN | 18.3.0 | +| 2023-06 | CP-100 | CP-231239 | 1115 | 1 | C | SNPN selection on validity condition change | 18.3.0 | +| 2023-06 | CP-100 | CP-231239 | 1107 | 1 | F | Clear forbidden SNPN list for localized service on receiving SOR-SNPN-SI-LS | 18.3.0 | +| 2023-06 | CP-100 | CP-231282 | 1113 | 1 | F | Provide CAG information list authorized by allowed CAG list to AS. | 18.3.0 | +| 2023-06 | CP-100 | CP-231282 | 1105 | 1 | F | Location validity information for enhanced CAG list in TS 23.122 | 18.3.0 | +| 2023-06 | CP-100 | CP-231217 | 1093 | 1 | F | Clarification for manual SNPN selection mode procedure for onboarding services | 18.3.0 | +| 2023-06 | CP-100 | CP-231232 | 1096 | 1 | F | Definition of Access Technology | 18.3.0 | +| 2023-06 | CP-100 | CP-231232 | 1092 | 1 | F | Clarification on handling equivalent PLMN(s) when PLMN is considered disabled on one or more RAT(s) | 18.3.0 | +| 2023-06 | CP-100 | CP-231217 | 1097 | 2 | F | SOR-CMCI: number of rules supported by the UE | 18.3.0 | +| 2023-06 | CP-100 | CP-231270 | 1013 | 8 | B | CP-SOR for SENSE capable UE | 18.3.0 | +| 2023-06 | CP-100 | CP-231283 | 1025 | 7 | B | Introduction of Enhanced Access to Support Network Slice - slice-based PLMN selection | 18.3.0 | +| 2023-06 | CP-100 | CP-231270 | 1109 | 3 | F | Clarification for SENSE applicability considering the EFOCST in the USIM | 18.3.0 | +| 2023-06 | CP-100 | CP-231239 | 1069 | 4 | B | Handling of location assistance information provided in the SoR SNPN selection information for localized services | 18.3.0 | +| 2023-06 | CP-100 | | | | | Fixing Errors | 18.3.1 | +| 2023-08 | CP-100 | | | | | Section 4.4.3.5 not listed in ToC | 18.3.2 | +| 2023-09 | CP-101 | CP-232222 | 1130 | - | F | Providing UE's subscribed S-NSSAI(s) to the SOR-AF | 18.4.0 | +| 2023-09 | CP-101 | CP-232217 | 1147 | - | F | Correction for the SOR-SENSE | 18.4.0 | +| 2023-09 | CP-101 | CP-232191 | 1150 | - | F | Clarification whether a CAG ID is authorized or CAG IDs of a CAG cell is authorized needs to be considered during manual selection | 18.4.0 | +| 2023-09 | CP-101 | CP-232222 | 1137 | 1 | C | Add the additional requirements for slice-based PLMN selection | 18.4.0 | +| 2023-09 | CP-101 | CP-232191 | 1131 | 1 | F | Equivalent SNPN Enhancements for Warning Message Configurations | 18.4.0 | +| 2023-09 | CP-101 | CP-232191 | 1120 | 1 | F | Time validity information structure and evaluation | 18.4.0 | +| 2023-09 | CP-101 | CP-232217 | 1125 | 1 | F | Updating the requirements for SENSE | 18.4.0 | +| 2023-09 | CP-101 | CP-232217 | 1128 | 1 | F | Miscellaneous corrections for SENSE | 18.4.0 | +| 2023-09 | CP-101 | CP-232191 | 1135 | 1 | F | Condition on enabling localized services in SNPN | 18.4.0 | +| 2023-09 | CP-101 | CP-232191 | 1136 | 1 | F | EN resolution on location validity information | 18.4.0 | +| 2023-09 | CP-101 | CP-232195 | 1122 | 1 | D | Editorial issues | 18.4.0 | +| 2023-09 | CP-101 | CP-232217 | 1129 | 1 | F | Correction to periodic PLMN selection for Signal level enhanced network selection | 18.4.0 | +| 2023-09 | CP-101 | CP-232191 | 1143 | 1 | F | Limited state system selection for localized services | 18.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------|--------| +| 2023-09 | CP-101 | CP-232191 | 1144 | 1 | F | No SIM state in the UE while accessing localized services in SNPN | 18.4.0 | +| 2023-09 | CP-101 | CP-232191 | 1149 | 1 | F | Clarification on SNPN selection procedure when emergency is ongoing | 18.4.0 | +| 2023-09 | CP-101 | CP-232192 | 1108 | 4 | F | Clear forbidden SNPN list for localized service on validation criterion met | 18.4.0 | +| 2023-09 | CP-101 | CP-232192 | 1141 | 3 | F | Resolution of EN on equivalent SNPNs assignment during onboarding registration | 18.4.0 | +| 2023-09 | CP-101 | CP-232192 | 1121 | 4 | F | SNPN selection upon validity condition changing between met and not met | 18.4.0 | +| 2023-12 | CP-102 | CP-233162 | 1165 | - | D | Editorial correction to SOR-SNPN-SI-LS | 18.5.0 | +| 2023-12 | CP-102 | CP-233143 | 1167 | - | F | Delete SNPN identified by GIN in SOR-SNPN-SI from forbidden SNPN list | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1174 | - | B | Manual selected SNPN and forbidden lists handling | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1175 | - | B | User reselection and localized service | 18.5.0 | +| 2023-12 | CP-102 | CP-233145 | 1172 | 1 | B | Clarification to timer Tsense for unavailability period | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1173 | 1 | B | equivalent SNPN used by the UE for Localized Services | 18.5.0 | +| 2023-12 | CP-102 | CP-233141 | 1177 | 2 | F | Correction to the list of PLMNs to be used in Disaster condition by VPLMNs | 18.5.0 | +| 2023-12 | CP-102 | CP-233141 | 1178 | 1 | F | Allowing EMSFB during SOR | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1161 | 2 | B | SNPN selection for localized services in case of SNPN is not available | 18.5.0 | +| 2023-12 | CP-102 | CP-233189 | 1163 | 3 | F | Up to one entry associated with same PLMN | 18.5.0 | +| 2023-12 | CP-102 | CP-233142 | 1181 | - | D | Editorial correction in forbidden SNPN list names | 18.5.0 | +| 2023-12 | CP-102 | CP-233143 | 1189 | 1 | F | CP-SOR corrections in 23.122 | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1168 | 4 | F | Forbidden SNPN lists for localized services for manual SNPN selection | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1185 | 1 | F | Covering user reselection for localized service | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1186 | 1 | F | Correction on SNPN selection for localized services | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1196 | 1 | F | For Consistency text in SNPN selection clause | 18.5.0 | +| 2023-12 | CP-102 | CP-233189 | 1184 | 1 | F | PLMN search in IDLE with suspend indication | 18.5.0 | +| 2023-12 | CP-102 | CP-233184 | 1190 | 2 | F | Clarification for SOR procedure for signal level enhanced network selection | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1194 | 2 | F | Minor Corrections for clarification in SNPN selection clause in TS 23.122 | 18.5.0 | +| 2023-12 | CP-102 | CP-233162 | 1162 | 5 | B | Location validity information for localized services | 18.5.0 | +| 2023-12 | CP-102 | CP-233181 | 1197 | - | C | Removal of slice-based PLMN selection feature | 18.5.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23222/042af54276c75e7b7b48a3af1f0a84e5_img.jpg b/raw/rel-18/23_series/23222/042af54276c75e7b7b48a3af1f0a84e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba0b4842469d18c2afd671086ae6b1187d66e26c --- /dev/null +++ b/raw/rel-18/23_series/23222/042af54276c75e7b7b48a3af1f0a84e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f85640148a941552fb07562f90c2d584f3f3058987f6c013ad31a0b781a1a8a +size 28363 diff --git a/raw/rel-18/23_series/23222/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/raw/rel-18/23_series/23222/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a62e16046e9fda2718953b4295d4a47c45b080a --- /dev/null +++ b/raw/rel-18/23_series/23222/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9938a946ec5bebb6915f8d7c2a88498e1dba6ed026eac6608f75fa6cce8051b1 +size 70536 diff --git a/raw/rel-18/23_series/23222/0a73b03fba21af142d619a9a662e6490_img.jpg b/raw/rel-18/23_series/23222/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a5aaa6f4eeff6264e47c809d2743fde5d1ad8e6 --- /dev/null +++ b/raw/rel-18/23_series/23222/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a3ac609dae122f76fbf587b70a38bf5cb2fed5e3966c728c9fe526fbd06ab09 +size 26693 diff --git a/raw/rel-18/23_series/23222/1187dbd674a100960ed23efa54ccd6c1_img.jpg b/raw/rel-18/23_series/23222/1187dbd674a100960ed23efa54ccd6c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f29798cd586ae673798d3ca8e368454be8a34344 --- /dev/null +++ b/raw/rel-18/23_series/23222/1187dbd674a100960ed23efa54ccd6c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ded643ac6efa3551a4d2e7d15f6d79b11319a97de54073a92ce5299c8e626f4 +size 106933 diff --git a/raw/rel-18/23_series/23222/11f18bf0233d812ad2604f88f3385d60_img.jpg b/raw/rel-18/23_series/23222/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88944280fda3ed7cd28cb963eba7b8a11cf5ae63 --- /dev/null +++ b/raw/rel-18/23_series/23222/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7ab9f60c07802521f50b81ec63876f4c5fa36eb37232632a21e9933fef03bad +size 37083 diff --git a/raw/rel-18/23_series/23222/12936f2edb05b1f2f43702086d1de2cc_img.jpg b/raw/rel-18/23_series/23222/12936f2edb05b1f2f43702086d1de2cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89cdc3eb8aea5fc3e82fdd4a872795dbc724c404 --- /dev/null +++ b/raw/rel-18/23_series/23222/12936f2edb05b1f2f43702086d1de2cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5678d987c929168c008c32ffa79f82fbc028623b6ed19f98981f1f1de849d40 +size 27063 diff --git a/raw/rel-18/23_series/23222/1bf34e86af3591c80bfbc1c318f811c0_img.jpg b/raw/rel-18/23_series/23222/1bf34e86af3591c80bfbc1c318f811c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42897a4adbb10e1be692c03c54403d1b842b6f8d --- /dev/null +++ b/raw/rel-18/23_series/23222/1bf34e86af3591c80bfbc1c318f811c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53a039ffe0d345739b1d522e0d6479dde2fc9de7ec7a90eba2afac7b9941e620 +size 34654 diff --git a/raw/rel-18/23_series/23222/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/raw/rel-18/23_series/23222/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0ffa9139111844fe6087655d5d053112888d684 --- /dev/null +++ b/raw/rel-18/23_series/23222/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b63b6e72fd7fed341c4397b2c8e67d21666c0691e6a0484d78a4e0dd587e81d5 +size 70230 diff --git a/raw/rel-18/23_series/23222/24a89bcaba787f2bc1721356480a4a01_img.jpg b/raw/rel-18/23_series/23222/24a89bcaba787f2bc1721356480a4a01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8b46f94a822c34803b5fa9f02a9b22703a90330 --- /dev/null +++ b/raw/rel-18/23_series/23222/24a89bcaba787f2bc1721356480a4a01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a26d9610397177173cf2da694423d32d19a3d10f489c5620d32d43769bc56038 +size 27870 diff --git a/raw/rel-18/23_series/23222/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/raw/rel-18/23_series/23222/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73fd28044835e85d8f03d94f94afbe21ed8997bc --- /dev/null +++ b/raw/rel-18/23_series/23222/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:685283f9082f362b219f753c919545424b40e0906b96034bc08b71337c452ba7 +size 76792 diff --git a/raw/rel-18/23_series/23222/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/raw/rel-18/23_series/23222/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a84f248afa1fae9b18fa514d332e37657094760 --- /dev/null +++ b/raw/rel-18/23_series/23222/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:743f68b90ccd3b8eb67ab4d91ea0b4b2a795e4b12b43458c6dc36b814854ac39 +size 22923 diff --git a/raw/rel-18/23_series/23222/2b00743506f6a3bbd17af764162dc76d_img.jpg b/raw/rel-18/23_series/23222/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b3c3d0fd551c029b8fc75512926806fb0a57ebf --- /dev/null +++ b/raw/rel-18/23_series/23222/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f247429ae5834c59fd90c71b09ca135380e95e6a525734eb2ab89fe1282edc82 +size 72982 diff --git a/raw/rel-18/23_series/23222/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/raw/rel-18/23_series/23222/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bb230013bc951949efbcfff15889ef1811ca8a8 --- /dev/null +++ b/raw/rel-18/23_series/23222/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdfd2d8ea30468a043f3fa178fe21a07fbd5653db02bd251ad0291d435ff4c44 +size 29327 diff --git a/raw/rel-18/23_series/23222/38d82ffe820e339811b396206f40a201_img.jpg b/raw/rel-18/23_series/23222/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8053fe8e4aa0669dbb371ec4ef9fe450a905e38 --- /dev/null +++ b/raw/rel-18/23_series/23222/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0238562bf0f7efc699c9869a177e6ee79b4757d8d2cb13aab2c5e6a23ac48112 +size 50208 diff --git a/raw/rel-18/23_series/23222/3bd9d303382ff0566369ed81a9226ade_img.jpg b/raw/rel-18/23_series/23222/3bd9d303382ff0566369ed81a9226ade_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39608986587a2a665fd8e2cc0ffe83f866b2da41 --- /dev/null +++ b/raw/rel-18/23_series/23222/3bd9d303382ff0566369ed81a9226ade_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54700695ed40e4ba9ae864bf1c6d0ac06dd4d97d4f42477507fd57db95f761b0 +size 23121 diff --git a/raw/rel-18/23_series/23222/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/raw/rel-18/23_series/23222/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3a82ab5b4dafb39659aab5b8a181d51a73b1f85 --- /dev/null +++ b/raw/rel-18/23_series/23222/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4781d02da292abf9f28de764716cfb5c1f0ba59080849371eda2ed051a95798a +size 24430 diff --git a/raw/rel-18/23_series/23222/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/raw/rel-18/23_series/23222/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25991617a5e893e83b5544d507aab52f51c4446f --- /dev/null +++ b/raw/rel-18/23_series/23222/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83fe841e78e8619c11cb8560eae14203b6ecff1ab09db136a4c2320aa634c147 +size 51273 diff --git a/raw/rel-18/23_series/23222/4a9454b4354535e1b61423084da1424b_img.jpg b/raw/rel-18/23_series/23222/4a9454b4354535e1b61423084da1424b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3adb506e033df681de9cbb4d565a244b534c8654 --- /dev/null +++ b/raw/rel-18/23_series/23222/4a9454b4354535e1b61423084da1424b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:413ffa9321d454f46fe69908311aab3332643fbc696e8075a90a1eb3550cea68 +size 116693 diff --git a/raw/rel-18/23_series/23222/53e80f05e45f132bf76a96442a5507e9_img.jpg b/raw/rel-18/23_series/23222/53e80f05e45f132bf76a96442a5507e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b14215e61e4503d863a9b5cdaba0ed929d18284 --- /dev/null +++ b/raw/rel-18/23_series/23222/53e80f05e45f132bf76a96442a5507e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c11a65f3b1c7980ae6f4ca23de91edda1991df05dd0a1c8d63714ae8533d5bd +size 74460 diff --git a/raw/rel-18/23_series/23222/578160bbc1592eab2db5f845bc95633d_img.jpg b/raw/rel-18/23_series/23222/578160bbc1592eab2db5f845bc95633d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0ab2ee05f715467d4ab3549974654055698744d --- /dev/null +++ b/raw/rel-18/23_series/23222/578160bbc1592eab2db5f845bc95633d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc46737081e4956e3c0c96d9d5290e5d3c8ff893c3b5d82b57be8ab5912994c1 +size 20619 diff --git a/raw/rel-18/23_series/23222/5801c19431e76330430e92a598cc7a16_img.jpg b/raw/rel-18/23_series/23222/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ca7315e8e2fbb1bef96cbb6304799d18f8ed59e --- /dev/null +++ b/raw/rel-18/23_series/23222/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52b7fe92b877ee91eea7fc29509d8c709b3eb09fa2b75bcddf96403d0d897ded +size 48350 diff --git a/raw/rel-18/23_series/23222/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/raw/rel-18/23_series/23222/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98a689bddfe6d1bb534718ed56560b53f4b5c350 --- /dev/null +++ b/raw/rel-18/23_series/23222/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70816a70595b1870272fd75aa0cabfbd145933f55ff8aadbdb218ea6e9a1aa1b +size 68238 diff --git a/raw/rel-18/23_series/23222/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23222/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d268ebe2e6120b5c25f83822832ba9f91b9b2d6 --- /dev/null +++ b/raw/rel-18/23_series/23222/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4deb1facc0e84ff9f622973e0eb22cfefa24fa44271727910d1641abb6211956 +size 9305 diff --git a/raw/rel-18/23_series/23222/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/raw/rel-18/23_series/23222/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8222e70ab7dbcc9ec8b0b44036c6f7d42dc02709 --- /dev/null +++ b/raw/rel-18/23_series/23222/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a03cd76590f8967b8840e132ee3e16a2884911b9a69a613e6bb6e9d145882d06 +size 44532 diff --git a/raw/rel-18/23_series/23222/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23222/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b7f5255e604447180259ef853a1e69e9529465f --- /dev/null +++ b/raw/rel-18/23_series/23222/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:354707ba231a0662964da917f5ddbe8c544d1b605c32e13c31bba5ef2bba5a03 +size 5696 diff --git a/raw/rel-18/23_series/23222/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/raw/rel-18/23_series/23222/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4aefbbe489a6709b8961f650d33d440a8efa043d --- /dev/null +++ b/raw/rel-18/23_series/23222/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da1a9fcb5deb5ade04db242f88aec2203a1205bc45d55975fab0177a08903182 +size 30123 diff --git a/raw/rel-18/23_series/23222/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/raw/rel-18/23_series/23222/6be06b7dc72bb42afcb3465394667c3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482897d201924c79b72a286754169def93a1c71b --- /dev/null +++ b/raw/rel-18/23_series/23222/6be06b7dc72bb42afcb3465394667c3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a13303a7fd957c17030a7b23812f0688211331b8a4ab4b88a528ffc7ff5ea69 +size 50170 diff --git a/raw/rel-18/23_series/23222/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/raw/rel-18/23_series/23222/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe0926e757aebd7b20805b102af3d0e0f2f17051 --- /dev/null +++ b/raw/rel-18/23_series/23222/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5718dc24569b29693f4d43297a99a0380ba67bdbd4dcfb47773523f5fd64e376 +size 43294 diff --git a/raw/rel-18/23_series/23222/6e9d059430baba0c363e33749f68b107_img.jpg b/raw/rel-18/23_series/23222/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..080e4d5ae89db9c1b6c8a901befa99c7280e9f11 --- /dev/null +++ b/raw/rel-18/23_series/23222/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84814f0207c7d94488cefce365cbb394aa7e5c1b5905678198d5ad9cbc50f1b4 +size 53285 diff --git a/raw/rel-18/23_series/23222/719ef0f734259484038b2434e5dc3f24_img.jpg b/raw/rel-18/23_series/23222/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be42a69f953a068c52541c08585b8ba861a53826 --- /dev/null +++ b/raw/rel-18/23_series/23222/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2177914da324b27eaffe2034142c418073011d671afd3b03e77ae76661c42ef0 +size 51162 diff --git a/raw/rel-18/23_series/23222/71b0a68b4dd64961465d2b0e790538de_img.jpg b/raw/rel-18/23_series/23222/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba680043198d19097760c560a8aa047c7274688b --- /dev/null +++ b/raw/rel-18/23_series/23222/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2edf75dd4dd0664a725d9b2ab483d158002c69bf479f36b04f879c4e3979fad7 +size 29775 diff --git a/raw/rel-18/23_series/23222/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/raw/rel-18/23_series/23222/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e6dae9ed57bada6591eec3a2e9b1648905b609d --- /dev/null +++ b/raw/rel-18/23_series/23222/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04c9a69a8825c0c6254025c1eed5fe4a5cefe08d776aa0c9e32d6031d698fc6f +size 45029 diff --git a/raw/rel-18/23_series/23222/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/raw/rel-18/23_series/23222/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c39f7766e1e0d6c83cc1aa49653b09a88e3938a --- /dev/null +++ b/raw/rel-18/23_series/23222/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdba549ad6fc5c4dc934645d146c47c5b10828a5c93f567fc93e301bea9fc401 +size 75071 diff --git a/raw/rel-18/23_series/23222/832a0ce332e784fe80289e9f00f56574_img.jpg b/raw/rel-18/23_series/23222/832a0ce332e784fe80289e9f00f56574_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e084649a05899af12b2f05393b2a36a34709933 --- /dev/null +++ b/raw/rel-18/23_series/23222/832a0ce332e784fe80289e9f00f56574_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c53f027afc46c3d9724388d2dde9ad1c2ce1ca43e118bcc8fff58765c5fd458 +size 52212 diff --git a/raw/rel-18/23_series/23222/896e86ed12aff206d302c64f2e3091fa_img.jpg b/raw/rel-18/23_series/23222/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..425ca2a77f3f687d93d32a6b7de88c8e1a317d1a --- /dev/null +++ b/raw/rel-18/23_series/23222/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d62f61ff6b9bafb1e58d18650271512fcff1d47cbf2755475755d2e0cd7b18d +size 53990 diff --git a/raw/rel-18/23_series/23222/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/raw/rel-18/23_series/23222/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bc43a2dc155f85927d92180e24c7bbac1476aa4 --- /dev/null +++ b/raw/rel-18/23_series/23222/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95ef337c2e52150f926550a41aa5b61e48b95bf5784723a2ad365ea01dc4741c +size 29817 diff --git a/raw/rel-18/23_series/23222/8fe194ec0e70ac418890f8f1ad02a102_img.jpg b/raw/rel-18/23_series/23222/8fe194ec0e70ac418890f8f1ad02a102_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50cbe6c589d54a77950cb5589ad4ad3ef95d5c10 --- /dev/null +++ b/raw/rel-18/23_series/23222/8fe194ec0e70ac418890f8f1ad02a102_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b366dda96d347aa6e79c6e1d543ce1707a049df17bb8b1fc5e8e873e96c54f7e +size 51117 diff --git a/raw/rel-18/23_series/23222/926e16abf793df297dae7b334069f69b_img.jpg b/raw/rel-18/23_series/23222/926e16abf793df297dae7b334069f69b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4bd11954d3eb0ee8a430990a46bd06172325d13 --- /dev/null +++ b/raw/rel-18/23_series/23222/926e16abf793df297dae7b334069f69b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8acac1c3a34e5224d4e5cead4604f77e8d0ef310b3fce08eb92d1c08b8b2c8fe +size 27104 diff --git a/raw/rel-18/23_series/23222/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/raw/rel-18/23_series/23222/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0477dfad25e76eb991361d227cc4f097b13be646 --- /dev/null +++ b/raw/rel-18/23_series/23222/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eccca38be4623be3024baa53628158d7f2b408ec8c749b41be082a22320ac6f0 +size 74792 diff --git a/raw/rel-18/23_series/23222/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/raw/rel-18/23_series/23222/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3408ba20eab4a393b65497c7d754f7b490256d9 --- /dev/null +++ b/raw/rel-18/23_series/23222/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d0d3c48d36e217a94146bf00b5ef97e8eb8d77c36110d55e86008f70b4a3114 +size 87661 diff --git a/raw/rel-18/23_series/23222/a265aba1737da6f0200faac85366b163_img.jpg b/raw/rel-18/23_series/23222/a265aba1737da6f0200faac85366b163_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9373b637a048f0a24179088c6b0b89eedc895bb --- /dev/null +++ b/raw/rel-18/23_series/23222/a265aba1737da6f0200faac85366b163_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fca4ad6eeecbb72c49605296c2bb254b08e994661a60d1e56dc15050797597c +size 100448 diff --git a/raw/rel-18/23_series/23222/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/raw/rel-18/23_series/23222/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42a5fb5d38139b8cced28462c66ca56eacbd369d --- /dev/null +++ b/raw/rel-18/23_series/23222/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85277c2afb824838ad26ba0c288af91a235cdb464eac78f7439ab1a96c2ded5d +size 23206 diff --git a/raw/rel-18/23_series/23222/af3d1702fb2fcdf2f9ec1a985afc085f_img.jpg b/raw/rel-18/23_series/23222/af3d1702fb2fcdf2f9ec1a985afc085f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb053bca4132ff9fb6e718097b4bda1aaa14947 --- /dev/null +++ b/raw/rel-18/23_series/23222/af3d1702fb2fcdf2f9ec1a985afc085f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4110928ac0eb1236b8370343f25e273245131f8701c6d215c6a9ce304c341547 +size 20359 diff --git a/raw/rel-18/23_series/23222/b033fab424e6df728345cfa04df83fcc_img.jpg b/raw/rel-18/23_series/23222/b033fab424e6df728345cfa04df83fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bff5a85afe8a0bd26b469ae09de3de9b8529377 --- /dev/null +++ b/raw/rel-18/23_series/23222/b033fab424e6df728345cfa04df83fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f75286b16397a9fc04514c31be3dc30c51f2211dfe882a05d5a074612b25b8ce +size 39056 diff --git a/raw/rel-18/23_series/23222/b6b53a74ad203c01b81e5427e9d6a898_img.jpg b/raw/rel-18/23_series/23222/b6b53a74ad203c01b81e5427e9d6a898_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a40887e5101d29e9ccf6df409ea507b13c7408e3 --- /dev/null +++ b/raw/rel-18/23_series/23222/b6b53a74ad203c01b81e5427e9d6a898_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb1b3c13a1aa296a13aa1daa690c864ba2212e0cab8dd52799361948c4d77b00 +size 63253 diff --git a/raw/rel-18/23_series/23222/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/raw/rel-18/23_series/23222/bb3063a33c89b248574f64b6d8dfc404_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6ef02fde2e0a7dfd775c16515793d60edff5adc --- /dev/null +++ b/raw/rel-18/23_series/23222/bb3063a33c89b248574f64b6d8dfc404_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0a93c75026ecb24f0e96176ec7f2bbd24e72134626693767ec95aba428f3d43 +size 32013 diff --git a/raw/rel-18/23_series/23222/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/raw/rel-18/23_series/23222/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb154fa69b01c5c6b3fd5209b802c587a5b4265b --- /dev/null +++ b/raw/rel-18/23_series/23222/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0532db877a696412fbdb7b078a62a56c5dc080e73879b5033014147609fb192e +size 27451 diff --git a/raw/rel-18/23_series/23222/c923e830926610e73d6cbcdedb9e5ea4_img.jpg b/raw/rel-18/23_series/23222/c923e830926610e73d6cbcdedb9e5ea4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..597eaa19debd30f2a0b390ae0699bfcfe1c46cee --- /dev/null +++ b/raw/rel-18/23_series/23222/c923e830926610e73d6cbcdedb9e5ea4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50374555a8d8008f1d931d4846ad1ae0afe483a77a98f7adad75498d8f707dcb +size 20680 diff --git a/raw/rel-18/23_series/23222/cbefcea7209aad70adeda96999ecffde_img.jpg b/raw/rel-18/23_series/23222/cbefcea7209aad70adeda96999ecffde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..008e24a99e4526d391abc2ff73a6e8c453b1b642 --- /dev/null +++ b/raw/rel-18/23_series/23222/cbefcea7209aad70adeda96999ecffde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c75b8685c7302804553c02145371ad1200c2b8b272d35c22dbfc8d9acd5958b +size 45154 diff --git a/raw/rel-18/23_series/23222/ccf6853c7291703cb04568057fef5849_img.jpg b/raw/rel-18/23_series/23222/ccf6853c7291703cb04568057fef5849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc6d4588ef310f06416b01bcf26e12fe39a84550 --- /dev/null +++ b/raw/rel-18/23_series/23222/ccf6853c7291703cb04568057fef5849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d1f43bcce61839ab68ba302be98011565afbe91446d65ef1183bc131d29de40 +size 27478 diff --git a/raw/rel-18/23_series/23222/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/raw/rel-18/23_series/23222/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..430e22ef6f739fdcfe361366c64cd9b3b62ac0ae --- /dev/null +++ b/raw/rel-18/23_series/23222/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ca786714a34349506000f3b4e6968bf533912a8ddac044e7b06167a36e2a664 +size 22747 diff --git a/raw/rel-18/23_series/23222/d3b5eac55166fc428a223bba5c46961b_img.jpg b/raw/rel-18/23_series/23222/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e7a798deb285aa2f7d8bd55fee3ad9ab6ad711f --- /dev/null +++ b/raw/rel-18/23_series/23222/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccc1ffb6f1c202c9a6fef348af7788a0a4128b9dc4229a14b24b75f3f60dbd1d +size 117805 diff --git a/raw/rel-18/23_series/23222/d6015fcef74bce83d04acd2e17b4fc15_img.jpg b/raw/rel-18/23_series/23222/d6015fcef74bce83d04acd2e17b4fc15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38372a2bc85e28797cd8d6441bbe1d3bb6d305c9 --- /dev/null +++ b/raw/rel-18/23_series/23222/d6015fcef74bce83d04acd2e17b4fc15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35e3271c07e13b2fe69f3640d2c3b2d59c0ba3b266b9fb694b71daf708177ce0 +size 28218 diff --git a/raw/rel-18/23_series/23222/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/raw/rel-18/23_series/23222/db5ab5d386827a5d5f5fad0f45612b90_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..988b6c6fbf6e7cf67b7b2c2a285d182e5e49e0a7 --- /dev/null +++ b/raw/rel-18/23_series/23222/db5ab5d386827a5d5f5fad0f45612b90_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7905f5c8e852b1d797490151e563d4aa0847424042959a4a731425b97dfc1631 +size 79180 diff --git a/raw/rel-18/23_series/23222/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/raw/rel-18/23_series/23222/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3c2e77fe9784dea6b453e861dd48053bf7e475a --- /dev/null +++ b/raw/rel-18/23_series/23222/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb5b92e243f9bfdacafe2e80e17a15636fb4e3a99a8aabc803b2205c44574380 +size 32276 diff --git a/raw/rel-18/23_series/23222/e05122559f56af5699789b7118d8fe87_img.jpg b/raw/rel-18/23_series/23222/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77b757ba9f3bf68bdce90a73183bc0c90cee8878 --- /dev/null +++ b/raw/rel-18/23_series/23222/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3acffa581b032cb6046a7b3be1a1e8a40823cb31a1f0bacae99bbb678e21eac7 +size 25344 diff --git a/raw/rel-18/23_series/23222/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/raw/rel-18/23_series/23222/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8fd80db4aef88f2cb70daf0e53fa7a73fdabb1d --- /dev/null +++ b/raw/rel-18/23_series/23222/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d584330a370927ad3b141d53e2fa006492d90bd10de8ac495d346eb83820e4df +size 34376 diff --git a/raw/rel-18/23_series/23222/e3eebf9854831ba50eca8b26c468f65e_img.jpg b/raw/rel-18/23_series/23222/e3eebf9854831ba50eca8b26c468f65e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fa21e5c66f8c658d61c94d7ab38bef7c32aa4d4 --- /dev/null +++ b/raw/rel-18/23_series/23222/e3eebf9854831ba50eca8b26c468f65e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ca4d20ed3f4b2d7b12b4e1109cc27af75f0d38de8488e2ec6091e36bc71c7f9 +size 40333 diff --git a/raw/rel-18/23_series/23222/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg b/raw/rel-18/23_series/23222/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..111d2ff2a9c05a6bdb5947ca23fc6f98930f0b79 --- /dev/null +++ b/raw/rel-18/23_series/23222/e6d2a5fe2df965cbe598f8ea80fbb7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e8fbebb4ac07dd28b591b3245b0bdbf549101b8c5572a0cce5a1589d011e5ad +size 19443 diff --git a/raw/rel-18/23_series/23222/e7010c66da16316c2935dfbbef5056b3_img.jpg b/raw/rel-18/23_series/23222/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52f7d5219a6ba1ef0d5944cbac83ba4a17d43557 --- /dev/null +++ b/raw/rel-18/23_series/23222/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc372acfcea422806ceed715c3991cd42f6c4c3edadb60a13e83aa2e2deb091c +size 24964 diff --git a/raw/rel-18/23_series/23222/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/raw/rel-18/23_series/23222/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3dd175deba649a752a507004f15376738afa0315 --- /dev/null +++ b/raw/rel-18/23_series/23222/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2030d087eb5221f0b7a9e9bba5a8726d0639733c861d30e2c58ec3931f7bba21 +size 61648 diff --git a/raw/rel-18/23_series/23222/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/23_series/23222/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b62579317cc9280a92c2d82f0dd67e99cd0be3e --- /dev/null +++ b/raw/rel-18/23_series/23222/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4479ffd1efe18755c26e5f086bd672c68edddcc5c7a61de7e0d0f00576f1686 +size 39020 diff --git a/raw/rel-18/23_series/23222/ef45b00396c293be0b18d32b97118bf4_img.jpg b/raw/rel-18/23_series/23222/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98c3d5d237470693f9239cd8ba5f386b45b6cebc --- /dev/null +++ b/raw/rel-18/23_series/23222/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b523499cbe3820109025de53315238bd137fa61be79ac7eaa69d4cb526e46d9 +size 75682 diff --git a/raw/rel-18/23_series/23222/f732d3320afe06d979aabbd366184254_img.jpg b/raw/rel-18/23_series/23222/f732d3320afe06d979aabbd366184254_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61fe7bbda76a4bb1aab761d8a9a47e1a692a08c2 --- /dev/null +++ b/raw/rel-18/23_series/23222/f732d3320afe06d979aabbd366184254_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e1752e3d25c3f4c0490ae077fb91ad5dc072927612a22aa96bfea4c3b784e1b +size 46309 diff --git a/raw/rel-18/23_series/23222/faa6766e9ed23a192edcbbbbb753e88c_img.jpg b/raw/rel-18/23_series/23222/faa6766e9ed23a192edcbbbbb753e88c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54e8fd72e2be527c9e3dc6128aa6780866a553ed --- /dev/null +++ b/raw/rel-18/23_series/23222/faa6766e9ed23a192edcbbbbb753e88c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f692a1fadb93c5e24463123478f9922c8cfac7cbf6b2de87bd7bdc5b66c14f70 +size 38621 diff --git a/raw/rel-18/23_series/23222/ffb6acd27b8e3a54392840948a75869f_img.jpg b/raw/rel-18/23_series/23222/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6a016ec10ff798b092b335815011e4c094fe819 --- /dev/null +++ b/raw/rel-18/23_series/23222/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58532123fd16a417cfd11798a8da6e817fcda9dd4101c9493402f11ba4ef11af +size 52421 diff --git a/raw/rel-18/23_series/23255/raw.md b/raw/rel-18/23_series/23255/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..adb43dde9885736d94a21c9dd411adbc56014da7 --- /dev/null +++ b/raw/rel-18/23_series/23255/raw.md @@ -0,0 +1,3498 @@ + + +# 3GPP TS 23.255 V18.2.0 (2023-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------|----| +| Foreword ..... | 8 | +| Introduction ..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions of terms and abbreviations ..... | 11 | +| 3.1 Terms..... | 11 | +| 3.2 Abbreviations ..... | 11 | +| 4 Architectural requirements..... | 13 | +| 4.1 General ..... | 13 | +| 4.2 Support for communications between UAVs..... | 13 | +| 4.2.1 Description ..... | 13 | +| 4.2.2 Requirements..... | 13 | +| 4.3 QoS provisioning for C2 communication ..... | 13 | +| 4.3.1 Description ..... | 13 | +| 4.3.2 Requirements..... | 13 | +| 4.4 C2 communication mode switching..... | 13 | +| 4.4.1 Description ..... | 13 | +| 4.4.2 Requirements..... | 13 | +| 4.5 Support for monitoring of UAV location deviation ..... | 14 | +| 4.5.1 Description ..... | 14 | +| 4.5.2 Requirements..... | 14 | +| 4.6 Support for reporting of UAV events..... | 14 | +| 4.6.1 Description ..... | 14 | +| 4.6.2 Requirements..... | 14 | +| 4.7 Support for multi-USS deployments ..... | 14 | +| 4.7.1 Description ..... | 14 | +| 4.7.2 Requirements..... | 14 | +| 4.8 Support of detect and avoid services and applications..... | 15 | +| 4.8.1 Description ..... | 15 | +| 4.8.2 Requirements..... | 15 | +| 5 Functional model..... | 15 | +| 5.1 General ..... | 15 | +| 5.2 Functional model description..... | 15 | +| 5.3 Functional entities description ..... | 18 | +| 5.3.1 General ..... | 18 | +| 5.3.2 UAS application specific client..... | 18 | +| 5.3.3 UAS application specific server ..... | 19 | +| 5.3.4 UAE client..... | 19 | +| 5.3.5 UAE server ..... | 19 | +| 5.3.6 SEAL client ..... | 20 | +| 5.3.7 SEAL server ..... | 20 | +| 5.4 Reference points description..... | 20 | +| 5.4.1 General ..... | 20 | +| 5.4.2 U1-AE..... | 20 | +| 5.4.3 U1-APP..... | 20 | +| 5.4.4 U2-AE..... | 20 | +| 5.4.5 U2-APP..... | 20 | +| 5.4.6 Us..... | 21 | +| 5.4.7 Uc ..... | 21 | +| 5.4.8 SEAL-C ..... | 21 | +| 5.4.9 SEAL-S..... | 21 | +| 5.4.10 SEAL-PC5 ..... | 21 | +| 5.4.11 SEAL-UU ..... | 21 | + +| | | | +|------------|-------------------------------------------------------------------------------|----| +| 5.4.12 | UAE-E ..... | 22 | +| 5.5 | External reference points..... | 22 | +| 5.5.1 | General ..... | 22 | +| 5.5.2 | Rx ..... | 22 | +| 5.5.3 | MB2-C ..... | 22 | +| 5.5.4 | MB2-U..... | 22 | +| 5.5.5 | xMB-C..... | 22 | +| 5.5.6 | xMB-U..... | 22 | +| 5.5.7 | T8..... | 22 | +| 5.5.8 | N5 ..... | 23 | +| 5.5.9 | N33/Nnef ..... | 23 | +| 6 | Identities..... | 23 | +| 6.1 | General ..... | 23 | +| 6.2 | UAV Identifier (UAV ID)..... | 23 | +| 6.3 | UAS Identifier (UAS ID)..... | 23 | +| 6.4 | UAS Application Specific Server Identifier (UASS ID) ..... | 23 | +| 6.5 | UAE Server Identifier (UAE Server ID)..... | 23 | +| 7 | Procedures and information flows ..... | 23 | +| 7.1 | Usage of SEAL services..... | 23 | +| 7.1.1 | General ..... | 23 | +| 7.1.2 | Group management service ..... | 24 | +| 7.1.2.1 | General..... | 24 | +| 7.1.2.2 | Information flows ..... | 24 | +| 7.1.2.3 | Procedures..... | 25 | +| 7.1.2.4 | APIs ..... | 25 | +| 7.1.3 | Location management service ..... | 25 | +| 7.1.3.1 | General..... | 25 | +| 7.1.3.2 | Information flows ..... | 26 | +| 7.1.3.3 | Procedures..... | 26 | +| 7.1.3.4 | APIs ..... | 26 | +| 7.1.4 | Network resource management service..... | 27 | +| 7.1.4.1 | General..... | 27 | +| 7.1.4.2 | Information flows ..... | 27 | +| 7.1.4.3 | Procedures..... | 27 | +| 7.1.4.4 | APIs ..... | 28 | +| 7.1a | UAE layer registration ..... | 28 | +| 7.1a.1 | General ..... | 28 | +| 7.1a.2 | Procedures ..... | 28 | +| 7.1a.2.1 | UAS UE registration..... | 28 | +| 7.1a.2.1.1 | General ..... | 28 | +| 7.1a.2.1.2 | Procedure..... | 28 | +| 7.1a.2.2 | UAS UE deregistration ..... | 29 | +| 7.1a.2.2.1 | General ..... | 29 | +| 7.1a.2.2.2 | Procedure..... | 29 | +| 7.1a.2.3 | UAS UE registration update ..... | 29 | +| 7.1a.2.3.1 | General ..... | 29 | +| 7.1a.2.3.2 | Procedure..... | 29 | +| 7.1a.3 | Information flows ..... | 30 | +| 7.1a.3.1 | Registration request ..... | 30 | +| 7.1a.3.2 | Registration response..... | 30 | +| 7.1a.3.3 | Deregistration request..... | 30 | +| 7.1a.3.4 | Deregistration response..... | 30 | +| 7.1a.3.5 | Registration update request..... | 30 | +| 7.1a.3.6 | Registration update response ..... | 31 | +| 7.2 | Communications between UAVs within a geographical area..... | 31 | +| 7.2.1 | General ..... | 31 | +| 7.2.2 | Procedures ..... | 31 | +| 7.2.2.1 | Communications between UAVs within a geographical area using unicast Uu ..... | 31 | +| 7.2.3 | Information flows ..... | 32 | +| 7.2.3.1 | UAV application message ..... | 32 | + +| | | | +|----------|--------------------------------------------------------------------------------------------|----| +| 7.3 | UAV and UAV-C Pairing and C2 QoS Provisioning using Group ID ..... | 32 | +| 7.3.1 | General ..... | 32 | +| 7.3.2 | Procedures ..... | 33 | +| 7.3.2.1 | Procedure for group creation for one pair of UAV and UAV-C ..... | 33 | +| 7.3.2.2 | Procedure for group-based approach for C2 QoS provisioning ..... | 33 | +| 7.3.3 | Information flows ..... | 35 | +| 7.4 | C2 Communication mode selection and switching ..... | 35 | +| 7.4.1 | General ..... | 35 | +| 7.4.2 | Procedures ..... | 35 | +| 7.4.2.1 | Management of C2 mode selection / switching capability ..... | 35 | +| 7.4.2.2 | C2 communication modes configuration ..... | 36 | +| 7.4.2.3 | C2 communication mode selection by UAE Client ..... | 37 | +| 7.4.2.4 | UAE-layer assisted dynamic C2 mode switching ..... | 38 | +| 7.4.2.5 | UAS application specific server triggered C2 communication mode switching ..... | 39 | +| 7.4.3 | Information flows ..... | 40 | +| 7.4.3.1 | C2 operation mode management request ..... | 40 | +| 7.4.3.2 | C2 operation mode management response ..... | 41 | +| 7.4.3.3 | C2 operation mode management complete ..... | 41 | +| 7.4.3.4 | C2-related trigger event report ..... | 41 | +| 7.4.3.5 | C2 mode switching confirmation request ..... | 41 | +| 7.4.3.6 | C2 mode switching confirmation response ..... | 42 | +| 7.4.3.7 | C2 operation mode switching ..... | 42 | +| 7.4.3.8 | C2 communication modes configuration request ..... | 42 | +| 7.4.3.9 | C2 communication modes configuration response ..... | 43 | +| 7.4.3.10 | C2 communication mode notification ..... | 43 | +| 7.4.3.11 | C2 communication mode notification acknowledgement ..... | 44 | +| 7.4.3.12 | C2 operation mode switching performed ..... | 44 | +| 7.5 | Real-Time UAV Connection Status Monitoring and Location reporting ..... | 44 | +| 7.5.1 | General ..... | 44 | +| 7.5.2 | Procedures ..... | 44 | +| 7.5.2.1 | Procedure for real-time UAV network connection status monitoring and location update ..... | 44 | +| 7.5.2.2 | Subscription for real-time UAV status information ..... | 45 | +| 7.5.2.3 | Notification of real-time UAV status information ..... | 46 | +| 7.5.2.4 | Unsubscription for real-time UAV status information ..... | 46 | +| 7.5.3 | Information flows ..... | 46 | +| 7.5.3.1 | Information flows between UAE server and SEAL servers ..... | 46 | +| 7.5.3.2 | Subscribe real-time UAV status information request ..... | 47 | +| 7.5.3.3 | Subscribe real-time UAV status information response ..... | 47 | +| 7.5.3.4 | Notify real-time UAV status information ..... | 47 | +| 7.5.3.5 | Unsubscribe real-time UAV status information request ..... | 47 | +| 7.5.3.6 | Unsubscribe real-time UAV status information response ..... | 48 | +| 7.6 | Change of USS during flight ..... | 48 | +| 7.6.1 | General ..... | 48 | +| 7.6.2 | Procedures ..... | 48 | +| 7.6.2.1 | Management of multi-USS configuration ..... | 48 | +| 7.6.2.2 | Multi-USS configuration ..... | 49 | +| 7.6.2.3 | UAE layer assisted change of USS ..... | 49 | +| 7.6.2.4 | UAE client assisted change of USS ..... | 50 | +| 7.6.2.5 | UAE server triggered change of USS ..... | 51 | +| 7.6.3 | Information flows ..... | 52 | +| 7.6.3.1 | Multi-USS management request ..... | 52 | +| 7.6.3.2 | Multi-USS management response ..... | 53 | +| 7.6.3.3 | Multi-USS management complete ..... | 53 | +| 7.6.3.4 | Multi-USS configuration request ..... | 54 | +| 7.6.3.5 | Multi-USS configuration response ..... | 54 | +| 7.6.3.6 | USS change request ..... | 54 | +| 7.6.3.7 | USS change response ..... | 55 | +| 7.6.3.8 | USS change notification ..... | 55 | +| 7.6.3.9 | USS change trigger notify ..... | 55 | +| 7.7 | UAE layer support for DAA services and applications ..... | 56 | +| 7.7.1 | General ..... | 56 | +| 7.7.2 | Procedures ..... | 56 | + +| | | | +|-----------|---------------------------------------------------------------------------------------|----| +| 7.7.2.1 | Configuration of DAA policies to the UAE layer and the UAS client..... | 56 | +| 7.7.2.1.1 | Management of DAA support configuration ..... | 56 | +| 7.7.2.1.2 | DAA support configuration procedure..... | 57 | +| 7.7.2.2 | UAE layer support for DAA applications..... | 57 | +| 7.7.2.2.1 | DAA support involving UAVs with U2X support..... | 57 | +| 7.7.2.2.2 | DAA support involving UAVs without U2X support..... | 58 | +| 7.7.3 | Information flows ..... | 59 | +| 7.7.3.1 | DAA support management request..... | 59 | +| 7.7.3.2 | DAA support management response ..... | 59 | +| 7.7.3.3 | DAA support management complete..... | 59 | +| 7.7.3.4 | DAA support configuration request..... | 60 | +| 7.7.3.5 | DAA support configuration response ..... | 60 | +| 7.7.3.6 | DAA client event information ..... | 60 | +| 7.7.3.7 | DAA client event information acknowledgement ..... | 60 | +| 7.7.3.8 | DAA server event information ..... | 61 | +| 7.7.3.9 | DAA server event information acknowledgement ..... | 61 | +| 7.8 | Tracking dynamic UAVs in an application defined area relative to a host UAV ..... | 61 | +| 7.8.1 | General ..... | 61 | +| 7.8.2 | Procedures ..... | 62 | +| 7.8.2.1 | Subscription for host UAV dynamic information..... | 62 | +| 7.8.2.2 | Management of dynamic UE location based group..... | 62 | +| 7.8.2.3 | Obtaining dynamic information of the UEs in application defined proximity range ..... | 64 | +| 7.8.2.3.1 | Subscription procedure within UAS operator ..... | 64 | +| 7.8.2.3.2 | Subscription procedure across UAS operators..... | 64 | +| 7.8.2.3.3 | Notification procedure..... | 65 | +| 7.8.2.4 | Notification of host UAV dynamic information..... | 65 | +| 7.8.2.5 | Unsubscription for host UAV dynamic information ..... | 66 | +| 7.8.3 | Information flows ..... | 66 | +| 7.8.3.1 | Subscribe host UAV dynamic information request ..... | 66 | +| 7.8.3.2 | Subscribe host UAV dynamic information response..... | 66 | +| 7.8.3.3 | Notify Host UAV dynamic information ..... | 67 | +| 7.8.3.4 | Notification of dynamic information ..... | 67 | +| 7.8.3.5 | Unsubscribe host UAV dynamic information request..... | 67 | +| 7.8.3.6 | Unsubscribe host UAV dynamic information response ..... | 67 | +| 8 | APIs..... | 68 | +| 8.1 | General ..... | 68 | +| 8.2 | UAE server APIs..... | 68 | +| 8.2.1 | General ..... | 68 | +| 8.2.2 | UAE_C2OperationModeManagement API..... | 70 | +| 8.2.2.1 | General..... | 70 | +| 8.2.2.2 | Manage_C2OperationMode operation ..... | 70 | +| 8.2.2.3 | Notify_SelectedC2Mode ..... | 70 | +| 8.2.2.4 | Notify_C2ModeSwitching..... | 70 | +| 8.2.2.5 | Notify_C2OperationModeManagementComplete..... | 70 | +| 8.2.3 | UAE_ RealtimeUAVStatus API..... | 71 | +| 8.2.3.1 | General..... | 71 | +| 8.2.3.2 | Subscribe_RealtimeUAVStatus operation..... | 71 | +| 8.2.3.3 | Unsubscribe_RealtimeUAVStatus operation ..... | 71 | +| 8.2.3.4 | Notify_RealtimeUAVStatus operation ..... | 71 | +| 8.2.4 | UAE_ChangeUSSManagement API..... | 71 | +| 8.2.4.1 | General..... | 71 | +| 8.2.4.2 | Manage_USSManagement operation ..... | 71 | +| 8.2.4.3 | Notify_USSManagementComplete operation ..... | 72 | +| 8.2.4.4 | Manage_USSChange operation..... | 72 | +| 8.2.4.5 | Notify_USSChange operation ..... | 72 | +| 8.2.4.6 | Notify_USSChangeTrigger ..... | 72 | +| 8.2.5 | UAE_DAASupport API..... | 73 | +| 8.2.5.1 | General..... | 73 | +| 8.2.5.2 | Manage_DAAManagement operation..... | 73 | +| 8.2.5.3 | Notify_DAAManagementComplete operation..... | 73 | +| 8.2.5.4 | Notify_DAAClientSupportEvent operation ..... | 73 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------|-----------| +| 8.2.5.5 | Manage_DAA ServerSupportEvent operation ..... | 73 | +| 8.2.6 | UAE_UAVDynamicInfo API ..... | 74 | +| 8.2.6.1 | General..... | 74 | +| 8.2.6.2 | Subscribe_UAVDynamicInfo operation..... | 74 | +| 8.2.6.3 | Unsubscribe_UAVDynamicInfo operation ..... | 74 | +| 8.2.6.4 | Notify_UAVDynamicInfo operation..... | 74 | +| Annex A (informative): | Support for edge deployments ..... | 75 | +| Annex B (Informative): | Deployment models ..... | 75 | +| B.1 | General..... | 75 | +| B.2 | Deployment of UAE server..... | 76 | +| B.2.1 | Centralized deployments..... | 76 | +| B.2.2 | Distributed deployment..... | 78 | +| Annex C (informative): | Examples of usage of SEAL by UAS application specific server ..... | 80 | +| Annex D (informative): | Change history..... | 82 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +In order to ensure efficient use and deployment of UAS on 3GPP networks an architecture for UAS application layer consisting of UAS application enabler is specified in this document. + +The UAE application enabler capabilities takes into consideration the existing stage 1 and stage 2 work within 3GPP related to UAS in 3GPP TS 22.125 [2] and 3GPP TS 23.256 [4]. + +# --- 1 Scope + +The present document specifies the functional architecture, procedures and information flows for UAS application enabler layer. This specification includes the capabilities of the application layer support for UAS that are necessary to ensure efficient use and deployment of UAS over 3GPP systems. The UAS application enabler capabilities applies to both EPS and 5GS. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP; Stage 1". +- [3] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2". +- [4] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification, and tracking; Stage 2". +- [5] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [6] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2". +- [7] 3GPP TS 23.558: "Architecture for enabling Edge Applications" +- [8] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [9] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". +- [10] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". +- [11] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". +- [12] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 Reference Point; Stage 3". +- [13] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". + +# 3 Definitions of terms and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**DAA application policy:** The configuration provided to the UAS application specific client by a UAS application specific server for handling of detect and avoid. + +**DAA assist capability:** The functionality for the UAE layer to assist the UAV application specific layer with handling of detect and avoid during flight. + +**Multi-USS capability:** The functionality for the UAE layer to assist at change of USS during flight. + +**NOTE:** A UAV with Multi-USS capability can be controlled by more than one USS during a flight, but at any given time, the UAV is under the control of only one USS. + +**Multi-USS policy:** The configuration provided by a UAS application specific server to assist at change of USS. + +**Remote Identification (Remote ID) of UAS:** The ability of a UAS to provide identification and tracking information that can be received by other parties, to facilitate advanced operations for the UAS (such as Beyond Visual Line of Sight operations as well as operations over people), assist regulatory agencies, air traffic management agencies, law enforcement, and security agencies when a UAS appears to be flying in an unsafe manner or where the UAS is not allowed to fly. + +**UAS Service Supplier (USS):** An entity that provides services to support the safe and efficient use of airspace by providing services to the operator / pilot of a UAS in meeting UTM operational requirements. A USS can provide any subset of functionality to meet the provider's business objectives (e.g., UTM, Remote Identification). In the scope of this specification, the term USS refers to both USS and USS/UTM. + +**UAV:** The Uncrewed Aerial Vehicle (also called remotely piloted aircraft or drone) of a UAS. + +For the purposes of the present document, the following terms given in 3GPP TS 22.125 [2] apply + +**Command and Control (C2) Communication** + +**Uncrewed Aerial System (UAS)** + +**Uncrewed Aerial System Traffic Management (UTM)** + +**UAV controller** + +For the purposes of the present document, the following terms given in clause 4.2 of 3GPP TS 22.125 [2] apply + +**Direct C2 Communication** + +**Network-Assisted C2 communication** + +**UTM-Navigated C2 communication** + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|------------------------------------------| +| BVLOS | Beyond Visual Line Of Sight | +| C2 | Command and Control | +| CAPIF | Common API Framework for northbound APIs | +| DAA | Detect And Avoid | +| QoS | Quality of Service | + +| | | +|-------|------------------------------------| +| SEAL | Service Enabler Architecture Layer | +| UAE | UAS Application Enabler | +| UAS | Uncrewed Aerial System | +| UAV | Uncrewed Aerial Vehicle | +| UAV-C | Uncrewed Aerial Vehicle-Controller | +| USS | UAS Service Supplier | +| UTM | UAS Traffic Management | + +# --- 4 Architectural requirements + +## 4.1 General + +[AR-4.1-a] The UAS application enabler layer shall support one or more UAS applications. + +[AR-4.1-b] The UAE capabilities should be offered as APIs to the UAS applications. + +## 4.2 Support for communications between UAVs + +### 4.2.1 Description + +This clause specifies the requirements for support for communications between UAVs. + +### 4.2.2 Requirements + +[AR-4.2-a] The UAS application enabler layer shall provide mechanism to support communications between UAVs in a geographical area using unicast Uu. + +## 4.3 QoS provisioning for C2 communication + +### 4.3.1 Description + +This clause specifies the C2 QoS provisioning related requirements. + +### 4.3.2 Requirements + +[AR-4.3.2-a] The UAE layer capabilities shall enable C2 application QoS parameter provisioning for network-assisted C2 communications to the 3GPP network system. + +[AR-4.3.2-b] The UAE layer capabilities shall enable QoS differentiation for UAV operations. + +[AR-4.3.2-c] The UAE server shall be capable of obtaining monitoring events related to the C2 QoS fulfilment/unfulfilment from the UAE clients (UAV and/or UAV controller). + +[AR-4.3.2-d] The UAE layer capabilities shall enable QoS parameters modification to support meeting the C2 end-to-end application requirements, for paired-Uu connections between a UAV and UE-based UAV-C. + +## 4.4 C2 communication mode switching + +### 4.4.1 Description + +This clause specifies the C2 communication mode switching related requirements. + +### 4.4.2 Requirements + +[AR-4.4.2-a] The UAE Server shall provide a mechanism for configuring the C2 communication modes at the UAE Client (UAV and UAV-C). + +[AR-4.4.2-b] The UAE Client (UAV and UAV-C) and UAV Server shall provide mechanisms for switching between the C2 communication links. + +[AR-4.4.2-c] The UAE Client (UAV and UAV-C) shall provide a mechanism for selecting a primary and a secondary communication link based on C2 communication mode configuration information. + +[AR-4.4.2-d] The UAE Client (UAV or UAV-C) shall provide a mechanism to switch C2 communication link without involving the UAE Server when an immediate change of C2 communication mode is needed. + +[AR-4.4.2-e] The UAE Server shall provide a mechanism for monitoring the availability of ProSe/PC5 link for C2 communications. + +[AR-4.4.2-f] The UAE Client shall be capable of reporting the availability of ProSe/PC5 link for C2 communications. + +## 4.5 Support for monitoring of UAV location deviation + +### 4.5.1 Description + +This clause specifies the requirements for location reporting capabilities to monitor the UAV location deviation. + +### 4.5.2 Requirements + +[AR-4.5.2-a] The SEAL layer shall provide mechanism to support the monitoring of UAV location. + +## 4.6 Support for reporting of UAV events + +### 4.6.1 Description + +This clause specifies the requirements for support for reporting of UAV events to USS/UTM. + +### 4.6.2 Requirements + +[AR-4.6.2-a] The SEAL layer shall provide mechanism to support the reporting of the 3GPP related UAV events to the USS/UTM. + +## 4.7 Support for multi-USS deployments + +### 4.7.1 Description + +This clause specifies the requirements for support of multi-USS deployments. + +### 4.7.2 Requirements + +[AR-4.7.2-a] The UAE Server shall provide a mechanism for the UAE Client to report its multi-USS capability to the UAE Server. + +[AR-4.7.2-b] The UAE Server shall provide a mechanism for enabling USS for configuring the Multi-USS policies to the UAE Client (UAV). + +[AR-4.7.2-c] The UAV Server shall provide a mechanism to support change of USS during UAS operations. + +[AR-4.7.2-d] The UAE Client (UAV) shall provide a mechanism to support change of USS based on the policies for multi-USS configuration when an immediate change of USS is needed. + +## 4.8 Support of detect and avoid services and applications + +### 4.8.1 Description + +This clause specifies the requirements related to support for detect and avoid services and applications. + +### 4.8.2 Requirements + +[AR-4.8.2-a] The UAE Server shall provide a mechanism for the UAE Client to report its DAA assist capability to the UAE Server. + +[AR-4.8.2-b] The UAE Server shall provide a mechanism for enabling USS for configuring the DAA policies to the UAE Client (UAV). + +[AR-4.8.2-c] The UAE layer shall provide a mechanism for a UAS application specific server to obtain DAA related events for a UAV. + +[AR-4.8.2-d] The UAS application enabler layer shall provide a mechanism for a UAS application specific client to obtain DAA related events for a UAV. + +# --- 5 Functional model + +## 5.1 General + +The functional model for the UAS application layer is organized into functional entities to describe a functional architecture which addresses the application layer support aspects for UAS applications. + +## 5.2 Functional model description + +Figures 5.2-1 and 5.2-2 illustrates the simplified architectural models for the UAS application layer. + +![Figure 5.2-1: Simplified architectural model for the UAS application layer](57f8e374b0e99c488f68c46b713ffc64_img.jpg) + +A block diagram showing three entities connected in a linear fashion. From left to right: a box labeled 'UAS UE2', a box labeled 'UAS UE1', and a box labeled 'UAS application server'. A horizontal line labeled 'U2' connects 'UAS UE2' and 'UAS UE1'. Another horizontal line labeled 'U1' connects 'UAS UE1' and 'UAS application server'. + +Figure 5.2-1: Simplified architectural model for the UAS application layer + +**Figure 5.2-1: Simplified architectural model for the UAS application layer** + +![Figure 5.2-2: Simplified architectural model for U2 connectivity between UAS UE1 and UAS UE2 at the UAS application layer](95cd9f56a54683029052b8c644228506_img.jpg) + +A block diagram showing two entities connected by a single line. From left to right: a box labeled 'UAS UE2' and a box labeled 'UAS UE1'. A horizontal line labeled 'U2' connects the two boxes. + +Figure 5.2-2: Simplified architectural model for U2 connectivity between UAS UE1 and UAS UE2 at the UAS application layer + +**Figure 5.2-2: Simplified architectural model for U2 connectivity between UAS UE1 and UAS UE2 at the UAS application layer** + +The UAS UE1 communicates with UAS application server over U1 reference point. The UAS UE1 and UAS UE2 communicate over U2 reference point. + +NOTE 1: Support for UE-to-network relay architecture for UAS communications is out of scope of the present document. + +The UAS UE1 and the UAS UE2 may be a UAV Controller or a UAV. + +NOTE 2: The UAV Controller can connect to the UAV via a transport independent of 3GPP. Such UAV Controller is not a 3GPP UE and is out of scope of the present document. + +NOTE 3: Support of PC5 at the U2 reference point for 5GS is out of scope of the present document. + +The reference point U1 supports the UAS application related interactions between UAS UE and UAS application server. It is expected that this reference point is supported at least for unicast delivery mode, and may support multicast delivery mode. The reference point U2 supports the interactions between the UAS UEs. The UAS application server can be the USS/UTM. + +The reference point U1 is based on Uu connectivity as specified in 3GPP TS 23.256 [4]. + +The reference point U2 is based on Uu connectivity as specified in 3GPP TS 23.256 [4]. + +NOTE 4: Support of multicast delivery over Uu for 5GS is out of scope of the present document. + +Figure 5.2-3 illustrates the detailed UAS application layer functional model. It enhances the simplified architectural model for the UAS application layer by specifying the functional entities at the UAS application layer. + +![Figure 5.2-3: UAS application layer functional model. This diagram illustrates the functional architecture of the UAS application layer, showing interactions between UAS UEs (UAV-C or UAV), the UAS application server, and the 3GPP network system across three layers: UAS application specific layer, UAE layer, and SEAL layer.](b90144cfbb81a2d610d920240fda689d_img.jpg) + +The diagram shows the following functional entities and interfaces: + +- UAS UE 2 (UAV-C or UAV):** Contains a "UAS application specific client" in the UAS application specific layer, a "UAE client" in the UAE layer, and "SEAL clients" in the SEAL layer. Interfaces include U2-APP, U2-AE, SEAL-C, and SEAL-PCS. +- UAS UE 1 (UAV-C or UAV):** Contains a "UAS application specific client" in the UAS application specific layer, a "UAE client" in the UAE layer, and "SEAL clients" in the SEAL layer. Interfaces include U1-APP, U1-AE, SEAL-C, and SEAL-UU. +- UAS application server:** Contains a "UAS application specific server" in the UAS application specific layer, a "UAE server" in the UAE layer, and "SEAL servers" in the SEAL layer. Interfaces include U1-APP, U1-AE, SEAL-S, and SEAL-UU. +- 3GPP network system:** Acts as a central hub with interfaces Nnnef, T8, MB2-U, xMB-U, MB2-C/xMB-C, Rx, and T8. +- Layers:** + - UAS application specific layer:** Top layer containing application-specific clients and servers. + - UAE layer:** Middle layer containing UAE clients and servers. + - SEAL layer:** Bottom layer containing SEAL clients and servers. + +Figure 5.2-3: UAS application layer functional model. This diagram illustrates the functional architecture of the UAS application layer, showing interactions between UAS UEs (UAV-C or UAV), the UAS application server, and the 3GPP network system across three layers: UAS application specific layer, UAE layer, and SEAL layer. + +**Figure 5.2-3: UAS application layer functional model** + +Figure 5.2-4 illustrates the detailed UAS application layer functional model where the UAV-C has a network-assisted connectivity with the UAV. + +![Figure 5.2-4: UAS application layer functional model with UAV-C having network-assisted connectivity with UAV. The diagram shows three layers: UAS application specific layer, UAE layer, and SEAL. On the left, UAS UE2 (UAV-C) contains a UAS application specific client, a UAE client, and SEAL clients. On the right, UAS UE1 (UAV) contains a UAS application specific client, a UAE client, and SEAL clients. A central 3GPP network system is shown. Connections include U2-APP between UAS application specific clients, U2-AE between UAE clients, SEAL-UU between SEAL clients, and SEAL-C between SEAL clients and UAE clients. Reference points U2, Uc, and SEAL-C are indicated.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 5.2-4: UAS application layer functional model with UAV-C having network-assisted connectivity with UAV. The diagram shows three layers: UAS application specific layer, UAE layer, and SEAL. On the left, UAS UE2 (UAV-C) contains a UAS application specific client, a UAE client, and SEAL clients. On the right, UAS UE1 (UAV) contains a UAS application specific client, a UAE client, and SEAL clients. A central 3GPP network system is shown. Connections include U2-APP between UAS application specific clients, U2-AE between UAE clients, SEAL-UU between SEAL clients, and SEAL-C between SEAL clients and UAE clients. Reference points U2, Uc, and SEAL-C are indicated. + +**Figure 5.2-4: UAS application layer functional model with UAV-C having network-assisted connectivity with UAV** + +The UAS application layer functional entities for the UAS UE and the UAS application server are grouped into the UAS application specific layer and the UAE layer. The UAE layer offers the UAE capabilities to the UAS application specific layer. The UAS application layer functional model utilizes the SEAL services as specified in 3GPP TS 23.434 [5]. + +The UAE server is located in the UAE layer. The SEAL services/UAS application specific layer utilized by UAE layer may include location management, group management, configuration management, identity management, key management and network resource management. The UAS application specific layer consists of the UAS application specific functionalities. + +NOTE 5: The functionalities of the UAS application specific layer include the USS/UTM and are out of scope of the present document. + +The following connectivity path for the UAS is supported when both the UAV-C and the UAV are 3GPP UEs: + +- UAV-C to UAV over U2 (Uu connectivity). + +The UAS application server consists of the UAE server, the SEAL servers and the UAS application specific server. The UAE server provides the UAS application layer support functions to the UAS application specific server over Us reference point. The SEAL servers provide the SEAL services to the UAS application specific server/UAE server over SEAL-S reference point. + +The UAS UE consists of the UAE client, the SEAL clients and the UAS application specific client. The UAE client provides the UAS application layer support functions to the UAS application specific client over Uc reference point. The SEAL clients provide the SEAL services to the UAS application specific client/UAE client over SEAL-C reference point. + +NOTE 6: In some deployments, the client and server entities of SEAL can be part of UAE client and UAE server respectively. + +The UAS application specific client/UAE client acts as a VAL client for its interaction with the SEAL clients as specified in 3GPP TS 23.434 [5]. The UAS application specific server/UAE server acts as a VAL server for its interaction with the SEAL servers as specified in 3GPP TS 23.434 [5]. + +In the UAE layer, the UAE client communicates with the UAE server over U1-AE reference point. In the UAS application specific layer, the UAS application specific client communicates with UAS application specific server over U1-APP reference point. + +NOTE 7: The U1-APP reference point includes UAV Controller/UAV to USS/UTM communication and is out of scope of the present document. + +In the UAE layer, the UAE client of UAS UE2 communicates with UAE client of UAS UE1 over U2-AE reference point. In the UAS application specific layer, the UAS application specific client of UAS UE2 communicates with UAE client of UAS UE1 over U2-APP reference point. + +NOTE 8: The U2-APP reference point is out of scope of the present document. + +The following SEAL services for UAS applications may include: + +- Location management as specified in 3GPP TS 23.434 [5]; +- Group management as specified in 3GPP TS 23.434 [5]; +- Configuration management as specified in 3GPP TS 23.434 [5]; +- Identity management as specified in 3GPP TS 23.434 [5]; +- Key management as specified in 3GPP TS 23.434 [5]; and +- Network resource management as specified in 3GPP TS 23.434 [5]. + +The UAS application specific client/UAE client interacts with SEAL clients over the SEAL-C reference point specified for each SEAL service. The UAS application specific server/UAE server interacts with SEAL servers over the SEAL-S reference point specified for each SEAL service. The interaction between the SEAL clients is supported by SEAL-PC5 reference point specified for each SEAL service. The interaction between a SEAL client and the corresponding SEAL server is supported by SEAL-UU reference point specified for each SEAL service. + +NOTE 9: The SEAL-C, SEAL-S, SEAL-PC5, SEAL-UU reference points for each SEAL service is specified in 3GPP TS 23.434 [5]. + +To support distributed UAE server deployments, the UAE server interacts with another UAE server over UAE-E reference point. + +A U1-AE message can be sent over at least unicast, and may be sent over transparent multicast via xMB or transparent multicast via MB2. The non-transparent multicast via xMB (as specified in 3GPP TS 26.348 [10]) is triggered by a U1-AE message. Multicast distribution can be supported by both transparent and non-transparent multicast modes. + +The UAE server interacts with the 3GPP network system over U2, MB2, xMB, Rx, T8 and Nnef reference points. + +## 5.3 Functional entities description + +### 5.3.1 General + +Each clause specifies a description of a functional entity corresponding to UAS application layer and does not imply a physical entity. + +### 5.3.2 UAS application specific client + +The UAS application specific client provides the client side functionalities corresponding to the UAS applications (e.g. Client interacting with USS/UTM). The UAS application specific client utilizes the UAE client for the UAS application layer support functions. + +NOTE: The details of the UAS application specific client is out of scope of the present document. + +### 5.3.3 UAS application specific server + +The UAS application specific server provides the server side functionalities corresponding to the UAS applications (e.g. USS/UTM). The UAS application specific server utilizes the UAE server for the UAS application layer support functions. If CAPIF is supported, the UAS application specific server acts as CAPIF's API invoker as specified in 3GPP TS 23.222 [3]. + +NOTE: The details of the UAS application specific server is out of scope of the present document. + +### 5.3.4 UAE client + +The UAE client supports interactions with the UAS application specific client(s). + +The UAE client provides the client side UAS application layer support functions as below: + +- receiving and storing C2 operation mode configurations; +- selecting primary and secondary C2 communication modes based on the configurations; +- switching of C2 communication in emergency scenarios; +- supporting UAV application message communication handling; +- providing the UAE server with the Multi-USS capability; +- receiving and storing Multi-USS and DAA application policies; +- based on Multi-USS policies, switching of UAS application specific server in emergency scenarios. +- determining information of UAVs in proximity of the UAV and providing to the UAE server and/or UAS application specific client; and +- receiving information of UAVs in application defined proximity range/area of the host UAV from UAE server and providing to the UAS application specific client. + +### 5.3.5 UAE server + +If CAPIF is supported, the UAE server acts as CAPIF's API exposing function to provide service APIs to the UAS application specific server (e.g. USS/UTM) or another UAE server as specified in 3GPP TS 23.222 [3], or acts as CAPIF's API invoker to consume the service APIs provided by another UAE server. + +The UAE server provides the server side UAS application layer support functions as below: + +- performing group based QoS management for the UAS (i.e. pair of UAV and UAV-C) by using SEAL APIs. +- receiving C2 operation mode configuration from UAS application specific servers (e.g. USS/UTM) and further configuring the UAS UEs (i.e. UAV, UAV-C); +- triggering C2 communication mode switching with the UAS UEs; +- receiving and storing the selected C2 communication modes from the UAS UEs; +- monitoring the real-time status of UAS UEs by using SEAL APIs; +- supporting UAV application message communications between UAVs; +- receiving Multi-USS and DAA application policies from UAS application specific servers and further configuring the UAS UEs (i.e. UAV). +- determining location information of UAVs and providing to the UAE client and/or UAS application specific server; and +- providing information of UAVs in application defined proximity range/area of the host UAV to the UAE client and the UAS application specific server. + +### 5.3.6 SEAL client + +The following SEAL clients as specified in 3GPP TS 23.434 [5] are supported: + +- Location management client; +- Group management client; +- Configuration management client; +- Identity management client; +- Key management client; and +- Network resource management client. + +### 5.3.7 SEAL server + +The following SEAL servers as specified in 3GPP TS 23.434 [5] are supported: + +- Location management server; +- Group management server; +- Configuration management server; +- Identity management server; +- Key management server; and +- Network resource management server. + +## 5.4 Reference points description + +### 5.4.1 General + +The reference points for the UAS application layer are described in the following clauses. + +### 5.4.2 U1-AE + +The interactions related to UAS application layer support functions between UAE client and UAE server are supported by U1-AE reference point. + +### 5.4.3 U1-APP + +The interactions related to UAS applications between UAS application specific client and UAS application specific server are supported by U1-APP reference point. The details of U1-APP reference point is out of scope of the present document. + +### 5.4.4 U2-AE + +The interactions related to UAS application layer support functions between the UAE clients are supported by U2-AE reference point. + +### 5.4.5 U2-APP + +The interactions related to UAS applications between UAS application specific clients are supported by U2-APP reference point. The details of U2-APP reference point is out of scope of the present document. + +### 5.4.6 Us + +The interactions related to UAS application layer support functions between the UAE server and the UAS application specific server are supported by Us reference point. If CAPIF is supported, this reference point is an instance of CAPIF-2/2e reference point as specified in 3GPP TS 23.222 [3]. + +### 5.4.7 Uc + +The interactions related to UAS application layer support functions between the UAE client and the UAS application specific client are supported by Uc reference point. + +### 5.4.8 SEAL-C + +The following SEAL-C reference points specified in 3GPP TS 23.434 [5] are supported: + +- LM-C reference point for location management; +- GM-C reference point for group management; +- CM-C reference point for configuration management; +- IM-C reference point for identity management; +- KM-C reference point for key management; and +- NRM-C reference point for network resource management. + +### 5.4.9 SEAL-S + +The following SEAL-S reference points specified in 3GPP TS 23.434 [5] are supported: + +- LM-S reference point for location management; +- GM-S reference point for group management; +- CM-S reference point for configuration management; +- IM-S reference point for identity management; +- KM-S reference point for key management; and +- NRM-S reference point for network resource management. + +### 5.4.10 SEAL-PC5 + +The following SEAL-PC5 reference points specified in 3GPP TS 23.434 [5] are supported: + +- LM-PC5 reference point for location management; +- GM-PC5 reference point for group management; +- CM-PC5 reference point for configuration management; +- IM-PC5 reference point for identity management; +- KM-PC5 reference point for key management; and +- NRM-PC5 reference point for network resource management. + +### 5.4.11 SEAL-UU + +The following SEAL-UU reference points specified in 3GPP TS 23.434 [5] are supported: + +- LM-UU reference point for location management; +- GM-UU reference point for group management; +- CM-UU reference point for configuration management; +- IM-UU reference point for identity management; +- KM-UU reference point for key management; and +- NRM-UU reference point for network resource management. + +### 5.4.12 UAE-E + +The interactions related to UAS application support functions between the UAE servers in a distributed deployment are supported by UAE-E reference point. If CAPIF is supported, this reference point is an instance of CAPIF-2/2e reference point as specified in 3GPP TS 23.222 [3]. + +## 5.5 External reference points + +### 5.5.1 General + +The reference points between the UAS application layer and the 3GPP network systems (EPS, 5GS) are described in the following clauses. + +### 5.5.2 Rx + +The reference point Rx supports the interactions between the UAS application server and the PCRF and is specified in 3GPP TS 29.214 [11]. The functions for Rx reference point are supported by the network resource management server of the SEAL. + +### 5.5.3 MB2-C + +The reference point MB2-C supports the control plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 29.468 [12]. The functions for MB2-C reference point are supported by the network resource management server of the SEAL. + +### 5.5.4 MB2-U + +The reference point MB2-U supports the user plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 29.468 [12]. The functions for MB2-U reference point are supported by the UAE server. + +### 5.5.5 xMB-C + +The reference point xMB-C supports the control plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 26.346 [9]. The functions for xMB reference point are supported by the network resource management server of the SEAL. + +### 5.5.6 xMB-U + +The reference point xMB-U supports the user plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 26.346 [9]. The functions for xMB-U reference point are supported by the UAE server. + +### 5.5.7 T8 + +The reference point T8 supports the interactions between the UAS application server and the SCEF and is specified in 3GPP TS 23.682 [8]. The functions of T8 interface are supported by UAE server and the functions related to location management of T8 are supported by the location management server. + +### 5.5.8 N5 + +The reference point N5 supports the interactions between the UAS application server and the PCF and is specified in 3GPP TS 23.501 [6]. The functions of N5 interface are supported by UAE server. + +### 5.5.9 N33/Nnef + +The reference point N33 supports the interactions between the UAS application server and the NEF and is specified in 3GPP TS 23.501 [6]. Nnef is the service based interface exposed by the NEF as per the N33 reference point. The functions of Nnef interface are supported by UAE server and the functions related to location management of Nnef are supported by the location management server. + +# --- 6 Identities + +## 6.1 General + +This clause describes the identities associated with the entities in the UAS application layer and used in this specification. + +## 6.2 UAV Identifier (UAV ID) + +The UAV identifier is used to uniquely identify a UAV. The UAV ID is in the form of a 3GPP UE ID (e.g. GPSI, External Identifier) as specified in 3GPP TS 23.501 [6] or CAA level UAV ID as assigned by civil aviation authorities (e.g. FAA) via USS/UTM. + +## 6.3 UAS Identifier (UAS ID) + +The UAS identifier is used to uniquely identify a pair of UAV and UAV-C collectively known as UAS. The UAS ID is in the form of a Group ID as specified in 3GPP TS 23.434 [5] or a collection of individual identifiers of the entities in the UAS (e.g. CAA level UAV IDs, 3GPP UE IDs). + +## 6.4 UAS Application Specific Server Identifier (UASS ID) + +The UAS application specific server identifier is used to uniquely identify the UAS application specific server. The UASS ID is in the form of URI. + +## 6.5 UAE Server Identifier (UAE Server ID) + +The UAE server identifier is used to uniquely identify the UAE server. The UAE Server ID is in the form of URI. + +# --- 7 Procedures and information flows + +## 7.1 Usage of SEAL services + +### 7.1.1 General + +The UAE capabilities (UAE client and UAE server) utilize the SEAL services. Also the UAS application specific server(s) may directly utilize the SEAL services. All SEAL services specified in 3GPP TS 23.434 [5] are available to the UAS application layer (i.e. the UAE layer and the UAS application specific layer). + +In this clause, the details of the information flows, procedures and APIs utilized by the UAS application layer are described. + +### 7.1.2 Group management service + +#### 7.1.2.1 General + +The UAE capabilities (UAE client and UAE server) utilize the group management service procedures (e.g. creation, join, leave) of SEAL based on the group configuration information (e.g. group join policy, group leader) provided by the UAS application specific layer. The decisions and corresponding triggers (e.g. group creation, join, leave) for group management are responsibility of the UAS application specific layer. The group management service of SEAL provides support for creating group for UAS for supporting UAS applications and C2 communications. + +The UAS application specific server(s) may directly utilize the group management service procedures of SEAL. + +#### 7.1.2.2 Information flows + +The following information flows of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications: + +- Group creation request specified in clause 10.3.2.1; +- Group creation response specified in clause 10.3.2.2; +- Group creation notification specified in clause 10.3.2.3; +- Group information query request specified in clause 10.3.2.4; +- Group information query response specified in clause 10.3.2.5; +- Group membership update request specified in clause 10.3.2.6; +- Group membership update response specified in clause 10.3.2.7; +- Group membership notification specified in clause 10.3.2.8; +- Group deletion request specified in clause 10.3.2.9; +- Group deletion response specified in clause 10.3.2.10; +- Group deletion notification specified in clause 10.3.2.11; +- Group information request specified in clause 10.3.2.12; +- Group information response specified in clause 10.3.2.13; +- Group information subscribe request specified in clause 10.3.2.14; +- Group information subscribe response specified in clause 10.3.2.15; +- Group information notify request specified in clause 10.3.2.16; +- Group information notify response specified in clause 10.3.2.17; +- Store group configuration request specified in clause 10.3.2.18; +- Store group configuration response specified in clause 10.3.2.19; +- Get group configuration request specified in clause 10.3.2.20; +- Get group configuration response specified in clause 10.3.2.21; +- Subscribe group configuration request specified in clause 10.3.2.22; +- Subscribe group configuration response specified in clause 10.3.2.23; + +- Notify group configuration request specified in clause 10.3.2.24; +- Notify group configuration response specified in clause 10.3.2.25; +- Configure VAL group request specified in clause 10.3.2.26; +- Configure VAL group response specified in clause 10.3.2.27; +- Group announcement specified in clause 10.3.2.28; +- Group registration request specified in clause 10.3.2.29; +- Group registration response specified in clause 10.3.2.30; +- Identity list notification specified in clause 10.3.2.31; +- Group de-registration request specified in clause 10.3.2.32; +- Group de-registration response specified in clause 10.3.2.33; + +The usage of the above information flows are clarified as below: + +- The identity is the UE ID or CAA Level ID; +- The identity list or identities list is the list of UE IDs or CAA Level IDs; and +- The VAL server is the UAE server or the UAS application specific server. + +#### 7.1.2.3 Procedures + +The following procedures of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications: + +- Group creation specified in clause 10.3.3; +- Group information query specified in clause 10.3.4; +- Group membership specified in clause 10.3.5; +- Group configuration management specified in clause 10.3.6; +- Group announcement and join specified in clause 10.3.8; +- Group member leave specified in clause 10.3.9; + +#### 7.1.2.4 APIs + +The following APIs of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications: + +- SS\_GroupManagement API specified in clause 10.4.2; + +### 7.1.3 Location management service + +#### 7.1.3.1 General + +The UAE capabilities (UAE client and UAE server) utilize location management (e.g. network location of UEs) service procedures of SEAL to support UAS applications. + +The UAS application specific server(s) may directly utilize the location management service procedures of SEAL. + +#### 7.1.3.2 Information flows + +The following information flows of location management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications: + +- Location reporting configuration request specified in clause 9.3.2.0; +- Location reporting configuration response specified in clause 9.3.2.1; +- Location information report specified in clause 9.3.2.2; +- Location information request specified in clause 9.3.2.3; +- Location reporting trigger specified in clause 9.3.2.4; +- Location information subscription request specified in clause 9.3.2.5; +- Location information subscription response specified in clause 9.3.2.6; +- Location information notification specified in clause 9.3.2.7; +- Location reporting configuration cancel specified in clause 9.3.2.8; +- Get UE(s) information request specified in clause 9.3.2.9; +- Get UE(s) information response specified in clause 9.3.2.10; +- Monitor location subscription request specified in clause 9.3.2.11; +- Monitor location subscription response specified in clause 9.3.2.12; +- Notify location monitoring event specified in clause 9.3.2.13; + +The usage of the above information flows are clarified as below: + +- The identity is the UE ID or CAA Level ID; +- The identity list or identities list is the list of UE IDs or CAA Level IDs; and +- The VAL server is the UAE server or the UAS application specific server. + +#### 7.1.3.3 Procedures + +The following procedures of location management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications: + +- Event-triggered location reporting procedure specified in clause 9.3.3; +- On-demand location reporting procedure specified in clause 9.3.4; +- Location reporting event triggers configuration cancel specified in clause 9.3.6; +- Location information subscription procedure specified in clause 9.3.7; +- Event-trigger location information notification procedure specified in clause 9.3.8; +- On-demand usage of location information procedure specified in clause 9.3.9; +- Obtaining UE(s) information at a location specified in clause 9.3.10; +- Monitoring Location Deviation specified in clause 9.3.11 + +#### 7.1.3.4 APIs + +The following APIs of location management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications: + +- SS\_LocationReporting API as specified in clause 9.4.2; +- SS\_LocationInfoEvent API as specified in clause 9.4.3; +- SS\_LocationInfoRetrieval API as specified in clause 9.4.4; +- SS\_LocationAreaInfoRetrieval API as specified in clause 9.4.5; +- SS\_LocationMonitoring API as specified in clause 9.4.6; + +### 7.1.4 Network resource management service + +#### 7.1.4.1 General + +The UAE capabilities (UAE client and UAE server) and UAS application specific servers utilize network resource management service procedures of SEAL to support UAS applications and C2 communications. + +The UAS application specific server(s) may directly utilize the network management service procedures of SEAL. + +#### 7.1.4.2 Information flows + +The following information flows of network resource management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications: + +- Network resource adaptation request specified in clause 14.3.2.1; +- Network resource adaptation response specified in clause 14.3.2.2; +- Resource request specified in clause 14.3.2.6; +- Resource response specified in clause 14.3.2.7; +- Resource modification request specified in clause 14.3.2.8; +- Resource modification response specified in clause 14.3.2.9; +- Monitoring Events Subscription Request specified in clause 14.3.2.17; +- Monitoring Events Subscription Response specified in clause 14.3.2.18; +- Monitoring Events Notification message specified in clause 14.3.2.19; + +The usage of the information flows are clarified as below: + +- The identity is the 3GPP UE ID or CAA Level UAV ID; +- The identity list or identities list is the list of 3GPP UE IDs or CAA Level UAV IDs; and +- The VAL server is the UAE server or the UAS application specific server. + +#### 7.1.4.3 Procedures + +The following procedures of network resource management service of SEAL specified 3GPP TS 23.434 [5] are applicable for the UAS applications and C2 communications: + +- Request for unicast resources at VAL service communication establishment specified in clause 14.3.3.2.1; +- Request for modification of unicast resources specified in clause 14.3.3.2.2; +- Network resource adaptation specified in clause 14.3.3.3.1; +- QoS/resource management capability initiation in network assisted UE-to-UE communications procedure specified in clause 14.3.5.2; + +- Coordinated QoS provisioning operation in network assisted UE-to-UE communications procedure specified in clause 14.3.5.3; +- Monitoring Events Subscription procedure specified in clause 14.3.6.2; +- Monitoring Events Notification procedure specified in clause 14.3.6.3; + +#### 7.1.4.4 APIs + +The following APIs of network resource management service of SEAL specified 3GPP TS 23.434 [5] are applicable for the UAS applications and C2 communications: + +- SS\_NetworkResourceAdaptation API specified in clause 14.4.2; +- SS\_EventsMonitoring API specified in clause 14.4.3; + +## 7.1a UAE layer registration + +### 7.1a.1 General + +The UAE capabilities provide support for registering UAV/UAV-C at the UAE server. The UAE server uses the registration information to distribute UAE layer messages or UAS application specific layer messages to the appropriate UAS UEs. + +### 7.1a.2 Procedures + +#### 7.1a.2.1 UAS UE registration + +##### 7.1a.2.1.1 General + +This clause describes the procedure for UAS UE (UAV/UAV-C) to register with the UAE server. + +##### 7.1a.2.1.2 Procedure + +Pre-conditions: + +- The UAE client has discovered the UAE server and is aware of the address of the UAE server (e.g. FDQN). + +NOTE: How the UAE client is provisioned with the UAE server information is outside the scope of the current document. + +- The UAV/UAV-C has already been assigned with the UAV ID. + +![Sequence diagram showing the procedure for registering the UAE client at the UAE server. The diagram consists of two lifelines: 'UAE client' on the left and 'UAE server' on the right. The sequence of messages is: 1. A 'Registration request' message is sent from the UAE client to the UAE server. 2. The UAE server performs an 'Authentication and authorization check' (indicated by a self-message box). 3. A 'Registration response' message is sent from the UAE server back to the UAE client.](5b226cae3053d5c1f14f0ca28f31e296_img.jpg) + +``` +sequenceDiagram + participant UAE client + participant UAE server + Note right of UAE server: 2. Authentication and authorization check + UAE client->>UAE server: 1. Registration request + UAE server-->>UAE client: 3. Registration response +``` + +Sequence diagram showing the procedure for registering the UAE client at the UAE server. The diagram consists of two lifelines: 'UAE client' on the left and 'UAE server' on the right. The sequence of messages is: 1. A 'Registration request' message is sent from the UAE client to the UAE server. 2. The UAE server performs an 'Authentication and authorization check' (indicated by a self-message box). 3. A 'Registration response' message is sent from the UAE server back to the UAE client. + +**Figure 7.1a.2.1.1-1: Procedure for registering the UAE client at the UAE server** + +1. The UAE client sends a registration request to the UAE server. + +2. The UAE server performs authentication and authorization check (e.g. based on pre-provisioned security information or by interacting with UAS application specific server (e.g. USS/UTM)). +3. The UAE server sends a registration response to the UAE client indicating success or failure of the registration. + +#### 7.1a.2.2 UAS UE deregistration + +##### 7.1a.2.2.1 General + +This clause describes the procedures for UAS UE (UAV/UAV-C) to deregister at the UAE server. + +##### 7.1a.2.2.2 Procedure + +Pre-condition: + +- The UAE client has already registered with the UAE server as described in subclause 7.1a.2.1. + +![Sequence diagram for UAS UE deregistration procedure](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +``` +sequenceDiagram + participant UAE client + participant UAE server + Note left of UAE client: Pre-condition: already registered + UAE client->>UAE server: 1. Deregistration request + UAE server-->>UAE client: 2. Deregistration response +``` + +The diagram shows a sequence of two messages between a UAE client and a UAE server. The UAE client sends a '1. Deregistration request' to the UAE server, and the UAE server responds with a '2. Deregistration response'. + +Sequence diagram for UAS UE deregistration procedure + +**Figure 7.1a.2.2.2-1: Procedure for deregistering the UAE client at the UAE server** + +1. The UAE client sends a deregistration request to the UAE server. +2. The UAE server sends a deregistration response to the UAE client. + +#### 7.1a.2.3 UAS UE registration update + +##### 7.1a.2.3.1 General + +This clause describes the procedures for UAS UE (UAV/UAV-C) to update its registration with the UAE server. + +##### 7.1a.2.3.2 Procedure + +Pre-conditions: + +- The UAE client has already registered with the UAE server as described in subclause 7.1a.2.1. + +![Sequence diagram for UAS UE registration update procedure](cd1731bf5e9e6baa73b786b2dcc80168_img.jpg) + +``` +sequenceDiagram + participant UAE client + participant UAE server + Note left of UAE client: Pre-condition: already registered + UAE client->>UAE server: 1. Registration update request + UAE server-->>UAE client: 2. Registration update response +``` + +The diagram shows a sequence of two messages between a UAE client and a UAE server. The UAE client sends a '1. Registration update request' to the UAE server, and the UAE server responds with a '2. Registration update response'. + +Sequence diagram for UAS UE registration update procedure + +**Figure 7.1a.2.3.1-1: Procedure for registration update by the UAE client at the UAE server** + +1. The UAE client sends a registration update request to the UAE server. +2. The UAE server sends an acknowledgement to the UAE client. + +### 7.1a.3 Information flows + +#### 7.1a.3.1 Registration request + +Table 7.1a.3.1-1 describes the information flow for a UAE client to register with the UAE server. + +**Table 7.1a.3.1-1: Registration request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------| +| UAV ID | M | The identifier of the UAV/UAV-C (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the registration request | +| UAS UE information | O | UAS UE information like IP address, Multi-USS capability, DAA assist capability, etc. | +| Proposed registration lifetime (NOTE) | O | Proposed registration lifetime. | +| NOTE: If Proposed registration lifetime IE is not included, then the registration lifetime is valid until explicit deregistration is performed. | | | + +#### 7.1a.3.2 Registration response + +Table 7.1a.3.2-1 describes the information flow for UAE server to respond for registration request from the UAE client. + +**Table 7.1a.3.2-1: Registration response** + +| Information element | Status | Description | +|-----------------------|--------|----------------------------------------------------------------------------------------------| +| Result | M | Result from the UAE server in response to registration request indicating success or failure | +| Registration lifetime | O | The registration lifetime provided by UAE server if registration is successful | + +#### 7.1a.3.3 Deregistration request + +Table 7.1a.3.3-1 describes the information flow for a UAE client to deregister at the UAE server. + +**Table 7.1a.3.3-1: Deregistration request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------| +| UAV ID | M | The identifier of the UAV/UAV-C (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the deregistration request | + +#### 7.1a.3.4 Deregistration response + +Table 7.1a.3.4-1 describes the information flow for UAE server to respond for deregistration request from the UAE client. + +**Table 7.1a.3.4-1: Deregistration response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------| +| Result | M | Result from the UAE server in response to the deregistration request | + +#### 7.1a.3.5 Registration update request + +Table 7.1a.3.5-1 describes the information flow for a UAE client to update registration with the UAE server. + +**Table 7.1a.3.5-1: Registration update request** + +| Information element | Status | Description | +|--------------------------------|--------|----------------------------------------------------------------------------------------------------------------| +| UAV ID | M | The identifier of the UAV/UAV-C (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the registration request | +| UAS UE information | M | UAS UE information like IP address, Multi-USS capability, DAA assist capability, etc. | +| Proposed registration lifetime | O | Proposed registration lifetime. | + +#### 7.1a.3.6 Registration update response + +Table 7.1a.3.6-1 describes the information flow for UAE server to respond for registration update request from the UAE client. + +**Table 7.1a.3.6-1: Registration update response** + +| Information element | Status | Description | +|-----------------------|--------|-----------------------------------------------------------------------------------------------------| +| Result | M | Result from the UAE server in response to registration update request indicating success or failure | +| Registration lifetime | O | The registration lifetime provided by UAE server if registration update is successful | + +## 7.2 Communications between UAVs within a geographical area + +### 7.2.1 General + +This clause describes the procedure for communications between UAVs within a geographical area. The geographical area is from the perspective of the UAV initiating the communication with other UAVs. + +The following transport mechanisms can be supported for communications between UAVs within a geographical area: + +- Using unicast Uu. + +NOTE: The mechanisms for communications between UAVs using multicast/broadcast Uu and ProSe are out of scope of the current release of the present document. + +### 7.2.2 Procedures + +#### 7.2.2.1 Communications between UAVs within a geographical area using unicast Uu + +Figure 7.2.2.1-1 illustrates the procedure for communications between UAVs within a geographical area using unicast Uu. + +Pre-conditions: + +- The UAE clients of UAVs have successfully registered and connected to the UAE server. +- The SEAL's LM server information is configured at the UAE server. + +![Sequence diagram showing communications between UAVs within a geographical area using unicast Uu. The diagram involves three participants: UAE client, UAE server, and LM server. The sequence is: 1. UAE client sends a 'UAV application message' to the UAE server. 2. The UAE server sends a request to the LM server to 'Get UAV(s) information in a range of the UAV location.' 3. The LM server responds with a message to the UAE server to 'Send the UAV application message to the UAV(s) via unicast'. 4. The UAE server sends an 'Acknowledgement' back to the UAE client via a dashed line.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant UAE client + participant UAE server + participant LM server + Note right of UAE server: 2. Get UAV(s) information in a range of the UAV location. + Note right of LM server: 3. Send the UAV application message to the UAV(s) via unicast + UAE client->>UAE server: 1. UAV application message + UAE server->>LM server: 2. Get UAV(s) information in a range of the UAV location. + LM server-->>UAE server: 3. Send the UAV application message to the UAV(s) via unicast + UAE server-->>UAE client: 4. Acknowledgement + +``` + +Sequence diagram showing communications between UAVs within a geographical area using unicast Uu. The diagram involves three participants: UAE client, UAE server, and LM server. The sequence is: 1. UAE client sends a 'UAV application message' to the UAE server. 2. The UAE server sends a request to the LM server to 'Get UAV(s) information in a range of the UAV location.' 3. The LM server responds with a message to the UAE server to 'Send the UAV application message to the UAV(s) via unicast'. 4. The UAE server sends an 'Acknowledgement' back to the UAE client via a dashed line. + +**Figure 7.2.2.1-1: Communications between UAVs within a geographical area using unicast Uu** + +1. The UAE client of UAV sends a UAV application message to the UAE server in order to communicate the payload information of the UAV application message to other UAVs in a range of the location corresponding to the UAV. +2. The UAE server obtains the other UAV(s) information in the location of the UAV from the LMS as specified in 3GPP TS 23.434 [5]. +3. Upon receiving the list of other UAV(s), the UAE server sends the payload in UAV application message to each of the UAV via unicast channel. +4. Upon completing step 3, the UAE server may send an acknowledgement to the UAE client. + +### 7.2.3 Information flows + +#### 7.2.3.1 UAV application message + +Table 7.2.3.1-1 describes the information flow for the UAV application message from UAE client to UAE server and from UAE server to UAE client. + +**Table 7.2.3.1-1: UAV application message** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------| +| UAV ID | M | The identifier of the UAV (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the UAV application message. | +| Application defined proximity range information (NOTE 2) | M | Description of the range information over which the UAV application message is to be sent. | +| Application Payload (NOTE 1) | M | Application payload that is to be delivered to the other UAVs | +| NOTE 1: This IE is provided by the UAS application specific client and its details are out of scope of 3GPP.
NOTE 2: This IE is not included when the UAV application message is sent from UAE server to UAE client. | | | + +## 7.3 UAV and UAV-C Pairing and C2 QoS Provisioning using Group ID + +### 7.3.1 General + +This clause describes the procedure for UAV and UAV-C grouping C2 QoS provisioning using subsequent group ID. It also provides the procedure for UAV replacement resulting in group ID update. + +### 7.3.2 Procedures + +#### 7.3.2.1 Procedure for group creation for one pair of UAV and UAV-C + +Figure 7.3.2.1-1 illustrates a high-level procedure for group creation. + +Pre-conditions: + +- Both UAV-C and UAV have successfully registered and connected to the UAE server. +- A CAA-level UAV ID is already assigned to the UAV-C and UAV. + +![Sequence diagram for group creation procedure](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +The diagram is a sequence diagram showing the interaction between four entities: UAV-C, UAV, UAE server, and GM server (SEAL). The sequence of events is as follows: + +- The UAE server recognizes a pair of UAV and UAV-C. +- The UAE server sends a Group ID request and creation message to the GM server (SEAL). +- The UAE server uses the assigned unique group ID to manage QoS monitoring and adjustment. + +Sequence diagram for group creation procedure + +**Figure 7.3.2.1-1: Procedure for group creation for one pair of UAV and UAV-C** + +1. The UAE server recognizes a unique pair of UAV and UAV-C either by 3GPP UE ID or CAA-level UAV ID. + +NOTE: The mechanisms for how the UAE server recognizes a pair of UAV-C and UAV is out of scope of the present document. + +2. The UAE server sends a group creation request to the SEAL GM server, if there is no pre-assigned group ID, by using the GM-S reference link as specified in 3GPP TS 23.434 [5] using the procedure defined in clause 10.3. The SEAL GM server creates one group ID for one pair of UAV and UAV-C as specified in 3GPP TS 23.434 [5]. +3. The UAE server uses the returned group ID for UAS for QoS management. + +#### 7.3.2.2 Procedure for group-based approach for C2 QoS provisioning + +Figure 7.3.2.2-1 illustrates a high-level workflow of group-based C2 QoS provisioning. + +Pre-conditions: + +- Both UAV and UAV-C have registered to 3GPP 5G network respectively. C2 communication is established. +- The procedure specified in clause 7.3.2.1 is performed and the group ID for the UAS group is available at the UAE server. + +![Sequence diagram for Figure 7.3.2.2-1: Procedure of group-based approach for C2 QoS provisioning. Lifelines: UAV-C/UAV, UAE client, UAE server, NRM server (SEAL), 3GPP core network. Steps: 1. UAE server monitors the QoS subscription for UAV and UAV-C; 2. UAE server triggers QoS adaptation; 3. The VAL service is established using new QoS; 4. UAS application layer adapts to new QoS allocation (dashed box).](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant UAV-C/UAV + participant UAE client + participant UAE server + participant NRM server (SEAL) + participant 3GPP core network + + Note right of UAE server: 1. UAE server monitors the QoS subscription for UAV and UAV-C + Note right of UAE server: 2. UAE server triggers QoS adaptation + Note right of UAE server: 3. The VAL service is established using new QoS + Note right of UAE server: 4. UAS application layer adapts to new QoS allocation + +``` + +Sequence diagram for Figure 7.3.2.2-1: Procedure of group-based approach for C2 QoS provisioning. Lifelines: UAV-C/UAV, UAE client, UAE server, NRM server (SEAL), 3GPP core network. Steps: 1. UAE server monitors the QoS subscription for UAV and UAV-C; 2. UAE server triggers QoS adaptation; 3. The VAL service is established using new QoS; 4. UAS application layer adapts to new QoS allocation (dashed box). + +**Figure 7.3.2.2-1: Procedure of group-based approach for C2 QoS provisioning.** + +1. The UAE server monitors the QoS for the UAS group (which includes a UAV and UAV-C) by SEAL NRM as specified in 3GPP TS 23.434 [5]. +2. In cases where the network condition for C2 communication does not satisfy the pre-defined QoS requirement, the UAE server may choose to send QoS adaptation request to the SEAL NRM server using the NRM-S reference point as specified in 3GPP TS 23.434 [5]. The QoS adaptation request needs to be sent per group ID for a pair of UAV and UAV-C created in the procedure specified in clause 7.3.2.1. The subsequent network resource adaptation procedure is triggered by the UAE server as specified in clause 14.3.3.3.1 of 3GPP TS 23.434 [5]. +3. The UAE client and UAE server established communication based on new QoS requirements as specified in clause 14.3.3.2.1.2 of 3GPP TS 23.434 [5]. +4. UAS application layer adapts the updated QoS assignment. + +NOTE: The mechanisms for how the UAS application layer is adapting newly assigned QoS is out of scope of the present document. + +#### 7.3.2.3 Procedure for group update + +Figure 7.3.2.3-1 illustrates the group membership update when UAV-2 is used to replace UAV-1. + +Pre-conditions: + +- The UAV-C, UAV-1, and UAV-2 are all previously successfully subscribed with 3GPP Core Network and UAS application specific server (e.g. USS/UTM) and have received a 3GPP UE ID (e.g. GPSI) and a CAA-level UAV ID. +- The UAV-1 and UAV-C have been grouped by a group ID by SEAL GMS as specified in clause 7.3.2.1. + +![Sequence diagram for Figure 7.3.2.3-1: Procedure for group update. Lifelines: UAV-C, UAV-1, UAV-2, UAE Server, SEAL GM Server. Steps: 1. UAE Server recognizes a new UAS compose of UAV-C and UAV-2; 2. Group membership update.](b54ce9bffd341cd643e196d5f4538829_img.jpg) + +``` + +sequenceDiagram + participant UAV-C + participant UAV-1 + participant UAV-2 + participant UAE Server + participant SEAL GM Server + + Note right of UAE Server: 1. UAE Server recognizes a new UAS compose of UAV-C and UAV-2 + Note right of UAE Server: 2. Group membership update + +``` + +Sequence diagram for Figure 7.3.2.3-1: Procedure for group update. Lifelines: UAV-C, UAV-1, UAV-2, UAE Server, SEAL GM Server. Steps: 1. UAE Server recognizes a new UAS compose of UAV-C and UAV-2; 2. Group membership update. + +**Figure 7.3.2.3-1: Procedure for group update** + +1. The UAE server recognizes a new pair of UAV-2 and UAV-C by the new CAA-level UAV ID. + +NOTE: The mechanisms for how the UAE server recognizes a new pair of UAV-C and UAV is out of scope of the present document. + +2. The UAE server sends a group membership update request to the SEAL GM server using the procedure specified in clause 10.3.2.6 of 3GPP TS 23.434 [5]. The SEAL GM server sends a group membership update response as specified in clause 10.3.2.7 of 3GPP TS 23.434 [5]. + +### 7.3.3 Information flows + +The usage of information flows between UAE server and SEAL's Group management Server is specified in clause 7.1.2.2. + +The usage of information flows between UAE server and SEAL's Network Resource Management Server is specified in clause 7.1.4.2. + +## 7.4 C2 Communication mode selection and switching + +### 7.4.1 General + +This feature introduces the UAS application enablement services for supporting the selection and re-selection of C2 communication modes. In particular, the UAE layer provides support for the following operations: + +- Support the switch between the Network-Assisted C2 communication and Direct C2 communication (e.g. when the direct link becomes feasible/available, or when a UAV is moving towards BVLOS or has poor direct link conditions, etc.) as described in clause 7.4.2.4. +- Support the switch between the Network-Assisted/Direct C2 communication and UTM-Navigated C2 communication (e.g. for air traffic control, the UAV is approaching a No Drone Zone, and detected potential security threats, etc.) as described in clause 7.4.2.5. +- Support the selection of the communication mode between: utilizing more than one C2 communication links, and among applicable C2 communication links, selecting a mode as the primary one as described in clause 7.4.2.3. +- Activation for the support of the above operations in the UAE Server in the UAE client is performed using procedure described respectively in clause 7.4.2.1 and clause 7.4.2.2. +- Support for C2 direct mode availability reporting to provide the awareness to the UAE server to switch to direct C2 communication if it is possible, as described in clause 7.4.2.1 and 7.4.2.4. + +Below, the different procedures for C2 communication mode selection and switching are described using UAE Client assisted and UAE Server controlled based mechanisms. Such functionality is supported by means of policies delivered to the UAV/UAV-C via the UAE layer and assisting the dynamic switching of C2 modes. + +### 7.4.2 Procedures + +#### 7.4.2.1 Management of C2 mode selection / switching capability + +This procedure manages the C2 mode selection/switching capability at the UAE server, based on an application request from UAS application specific server (which can be the USS/UTM) to manage the C2 operation modes (direct, network-assisted) of C2 communication for a UAS. + +Figure 7.4.2.1-1 illustrates the procedure where the UAE server receives an application request for managing the operation mode for C2 communications for a UAS. + +Pre-condition: + +- The UAV has received its UAS ID from the UAS application specific server. + +![Sequence diagram for C2 operation mode management request / response](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` +sequenceDiagram + participant UAS application specific server + participant UAE server + Note left of UAE server: 3. C2 configuration (clause 7.4.2.2) + UAS application specific server->>UAE server: 1. C2 operation mode management request + UAE server-->>UAS application specific server: 2. C2 operation mode management response + Note right of UAE server: 3. C2 configuration (clause 7.4.2.2) + UAE server->>UAS application specific server: 4. C2 operation mode management complete +``` + +The diagram illustrates a sequence of four messages between a UAS application specific server and a UAE server. The sequence starts with the UAS application specific server sending a '1. C2 operation mode management request' to the UAE server. The UAE server responds with '2. C2 operation mode management response'. A note on the UAE server side indicates '3. C2 configuration (clause 7.4.2.2)'. Finally, the UAE server sends '4. C2 operation mode management complete' to the UAS application specific server. + +Sequence diagram for C2 operation mode management request / response + +**Figure 7.4.2.1-1: C2 operation mode management request / response** + +1. The UAS application specific server sends to the UAE Server a C2 operation mode management request for managing the operation modes for the C2 communication for a UAS (consisting a UAV and a UAV-C) and to subscribe for UAE notifications. If ProSE/PC5 is supported for direct C2 communications, such request may also include a C2 direct mode availability reporting requirement including the ProSe configuration information for direct C2 operation, the UAV and UAV-C IDs and addresses, and the time and area for which the monitoring of availability will apply. +2. The UAE Server sends to the UAS application specific server a C2 operation mode management response with a positive or negative acknowledgement of the request, based on capability of UAE server to undertake this task. +3. UAE server executes C2 communication modes configuration according to clause 7.4.2.2. +4. After execution of C2 communication modes configuration, the UAE server notifies the UAS application specific server with a C2 operation mode management complete. + +#### 7.4.2.2 C2 communication modes configuration + +This procedure enables the configuration of the UAE Client, based on an application request from UAS application specific server (which can be the USS/UTM) to manage the C2 operation modes (direct, network-assisted) of C2 communication for a UAS. + +Figure 7.4.2.2-1 illustrates the C2 communication modes configuration procedure. + +Pre-conditions: + +1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4]. +2. UAE Server has established a UAE session with the respective UAE Clients as the UAE clients are successfully registered to the UAE server. +3. UAE Server has performed the C2 mode switching/selection capability initiation as in clause 7.4.2.1. + +![Sequence diagram for C2 communication modes configuration. Lifelines: UAE client (UAV or UAV-C), 5GC, and UAE server. Step 1: UAE server sends a 'C2 Communication Modes Configuration request' to the UAE client. Step 2: The UAE client performs an internal action 'Store or remove C2 communication mode configuration parameters'. Step 3: The UAE client sends a 'C2 Communication Modes Configuration response' back to the UAE server.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant UAE_server as UAE server + participant 5GC + participant UAE_client as UAE client (UAV or UAV-C) + Note left of UAE_client: 2. Store or remove C2 communication mode configuration parameters + UAE_server->>UAE_client: 1. C2 Communication Modes Configuration request + UAE_client-->>UAE_server: 3. C2 Communication Modes Configuration response + +``` + +Sequence diagram for C2 communication modes configuration. Lifelines: UAE client (UAV or UAV-C), 5GC, and UAE server. Step 1: UAE server sends a 'C2 Communication Modes Configuration request' to the UAE client. Step 2: The UAE client performs an internal action 'Store or remove C2 communication mode configuration parameters'. Step 3: The UAE client sends a 'C2 Communication Modes Configuration response' back to the UAE server. + +Figure 7.4.2.2-1: C2 communication modes configuration + +1. The UAE Server sends a C2 communication modes configuration request including the UAS identifier, allowed C2 communication modes (e.g., direct, network assisted, UTM-Navigated), primary and optionally secondary C2 communication mode and policy for switching. In the case of removal of C2 communication mode configuration parameters from the UAV or UAV-C, then the request shall only include the UAS identifier. +2. The UAE Client stores or removes the C2 communication mode configuration parameters as per the information received in step 1. +3. The UAE Client sends a C2 communication modes configuration response to the UAE Server. + +#### 7.4.2.3 C2 communication mode selection by UAE Client + +This procedure provides a mechanism for the UAE client to select a primary C2 communication mode and optional secondary C2 communication mode based on C2 communication mode configuration enabled as described in clause 7.4.2.2. + +Figure 7.4.2.3-1 illustrates the C2 communication mode selection and redundant C2 link negotiation. + +Pre-conditions: + +1. The UAE Clients are configured with a C2 communication modes configuration as described in clause 7.4.2.2. +2. UAE Server has activated the dynamic C2 mode switching capability, as described in clause 7.4.2.1. + +![Sequence diagram for C2 communication mode selection. Lifelines: UAE client (UAV), 5GC, UAE client (UAV-C), UAE server, and UAS application specific server. Step 1: The UAE client (UAV) performs an internal action 'Selects primary and secondary C2 communication mode(s) based on configuration'. Step 2: The UAE client (UAV-C) sends a 'C2 communication mode notification' to the UAE server. Step 3: The UAE server performs an internal action 'Store C2 communication modes information'. Step 4a: The UAE server sends a 'C2 communication mode notification' to the UAS application specific server. Step 4b: The UAS application specific server sends a 'C2 communication mode notification acknowledgement' back to the UAE server. Step 5: The UAE server sends a 'C2 communication mode notification acknowledgement' to the UAE client (UAV-C). Step 6: A 'C2 communication between UAV and UAV-C' occurs.](e38206fcefa2045af01d494b2956775a_img.jpg) + +``` + +sequenceDiagram + participant UAV as UAE client (UAV) + participant 5GC + participant UAVC as UAE client (UAV-C) + participant UAE_server as UAE server + participant UAS_server as UAS application specific server + Note left of UAV: 1. Selects primary and secondary C2 communication mode(s) based on configuration + UAVC->>UAE_server: 2. C2 communication mode notification + Note right of UAE_server: 3. Store C2 communication modes information + UAE_server->>UAS_server: 4a. C2 communication mode notification + UAS_server-->>UAE_server: 4b. C2 communication mode notification acknowledgement + UAE_server-->>UAVC: 5. C2 communication mode notification acknowledgement + Note left of UAV: 6. C2 communication between UAV and UAV-C + +``` + +Sequence diagram for C2 communication mode selection. Lifelines: UAE client (UAV), 5GC, UAE client (UAV-C), UAE server, and UAS application specific server. Step 1: The UAE client (UAV) performs an internal action 'Selects primary and secondary C2 communication mode(s) based on configuration'. Step 2: The UAE client (UAV-C) sends a 'C2 communication mode notification' to the UAE server. Step 3: The UAE server performs an internal action 'Store C2 communication modes information'. Step 4a: The UAE server sends a 'C2 communication mode notification' to the UAS application specific server. Step 4b: The UAS application specific server sends a 'C2 communication mode notification acknowledgement' back to the UAE server. Step 5: The UAE server sends a 'C2 communication mode notification acknowledgement' to the UAE client (UAV-C). Step 6: A 'C2 communication between UAV and UAV-C' occurs. + +Figure 7.4.2.3-1: C2 communication mode selection + +1. UAE Clients (UAV and UAV-C) select a primary and secondary C2 communication mode based on C2 communication mode configuration. +2. The UAE Client sends a C2 communication mode notification to the UAE Server indicating the selected primary and secondary C2 communication modes and associated C2 link information which may include UAE Client and peer address information (e.g., IP/MAC address). +3. The UAE Server stores the C2 communication modes and links information. +- 4a-4b. The UAE Server forwards the C2 communication mode and links information to the UAS application specific server and receives a C2 communication mode notification acknowledgement from the UAS application specific server. +5. The UAE Server may forward the C2 communication mode notification acknowledgement to the UAE Client. +6. The UAV and UAV-C start C2 communication using the selected C2 communication mode. + +NOTE: The details of step 6 are outside the scope of the present specification. + +#### 7.4.2.4 UAE-layer assisted dynamic C2 mode switching + +This procedure provides a mechanism for supporting dynamic switching between direct and network assisted C2 communications, which may be required while the UAV flight is ongoing, due to possible change of network conditions, expected location/mobility of the UAV, unpredictable events etc. + +Figure 7.4.2.4-1 illustrates the procedure where the UAE server supports the dynamic C2 mode switching for network-assisted C2 communications. + +Pre-conditions: + +1. UAE Server has activated the dynamic C2 mode switching capability, as described in clause 7.4.2.1 +2. UAE Server has subscribed for using SEAL/LMS services and has configured the location event reporting, based on 3GPP TS 23.434 [5]. +3. UAE Client has selected a C2 communication mode as described in clause 7.4.2.3, and UAV and UAV-C are engaged in C2 communication. + +![Sequence diagram for UAE-assisted dynamic C2 mode switching. Lifelines: UAE client #2 (UAV-C), UAE client #1 (UAV), LM server (SEAL), UAE server, and UAS application specific server. The sequence shows a trigger event report from a client to the server, a location event report from the server to the LM server, a switching trigger from the LM server to the server, a confirmation request from the server to the application server, a confirmation response from the application server to the server, and finally the switching operation performed between the clients and the server.](257c8341b41f1f4a287f27d33227974c_img.jpg) + +``` + +sequenceDiagram + participant UAV-C as UAE client #2 (UAV-C) + participant UAV as UAE client #1 (UAV) + participant SEAL as LM server (SEAL) + participant Server as UAE server + participant AppServer as UAS application specific server + + Note right of UAV: 1. C2-related trigger event report + UAV->>Server: + Note right of Server: 2. Location Event Report + Server->>SEAL: + Note right of SEAL: 3. C2 mode switching trigger + SEAL->>Server: + Note right of Server: 4. C2 mode switching confirmation request + Server-->>AppServer: + Note right of AppServer: 5. C2 mode switching confirmation response + AppServer-->>Server: + Note right of Server: 6. C2 operation mode switching + Server->>UAV: + Note right of UAV: 7. C2 operation mode switching performed + UAV->>Server: + +``` + +Sequence diagram for UAE-assisted dynamic C2 mode switching. Lifelines: UAE client #2 (UAV-C), UAE client #1 (UAV), LM server (SEAL), UAE server, and UAS application specific server. The sequence shows a trigger event report from a client to the server, a location event report from the server to the LM server, a switching trigger from the LM server to the server, a confirmation request from the server to the application server, a confirmation response from the application server to the server, and finally the switching operation performed between the clients and the server. + +Figure 7.4.2.4-1: UAE-assisted dynamic C2 mode switching + +1. The UAE Client detects a condition for switching C2 communication mode based on local conditions (e.g. using the C2 communication mode switching policy) or based on a command from the UAS application specific server (as described in clause 7.4.2.5). A C2-related trigger event report is sent from the UAE Client of the UAV and/or the UAV-C to the UAE Server, denoting a command from the UAS application specific server or an application + +QoS attribute change (experienced or expected) e.g. based on the experienced packet delay or packet loss for the Uu or direct link (e.g. packet loss greater than a pre-defined threshold). + +If a C2 direct mode availability reporting requirement exists based on clause 7.4.2.1 step 1, the detection of UAV/UAV-C(s) can be based on the PC5 discovery due to the configurations received due procedures in clause 7.4.2.1 and clause 7.4.2.2. In this case, the C2-related trigger event report message can include also a C2 direct mode availability report including PC5 related configuration information. + +2. Additionally, the UAE Server receives a location report for the UAV/UAV-C by the SEAL's LM server. The report can be either periodical or event-based (e.g. UAV moving towards an area covered by a different cell or different operator), as specified in 3GPP TS 23.434 [5] SEAL's LM server procedures (UAE Server acting as a VAL server). +3. The UAE Server determines the switching of the C2 mode from direct to network assisted or vice versa or to UTM-Navigated. If the switching is from direct to network assisted or vice versa, this is done by calculating the relative actual or expected UAV-to-UAV-C location, as well as other factors like QoS fulfilment/unfulfilment, augmented location, mobility/speed, direction, topography, weather conditions. +4. The UAE Server sends a C2 mode switching confirmation request to the UAS application specific server, which includes the UAS identifier as well as the cause for switching and the switching option (direct to network-assisted or network-assisted to direct or to UTM-Navigated). The UAE Server sends this request to obtain confirmation from the UAS application specific server before proceeding with switching to UTM-Navigated. This step is optional in the case of switching from direct to network assisted or vice versa. +5. Conditional on Step 3, the UAE Server receives from the UAS application specific server a C2 mode switching confirmation response indicating a positive or negative result for the requested change. +6. The UAE Server sends to the involved UAE Clients, a C2 operation mode switching message which provides an instruction to the UAV and UAV-C to switch to network-assisted mode or to direct mode or to UTM-Navigated. The UAV and UAV-C start C2 communication using the indicated C2 communication mode (e.g., direct, network assisted, UTM-Navigated). +7. If an emergency switch of the C2 communication is deemed necessary by the UAE Client (e.g. sudden loss of the active C2 link), the UAE Client changes the link prior to the steps 1-6, which are skipped. The UAE Clients send a C2 operation mode switching performed message to the UAE Server to confirm the switching of the C2 communication mode. + +#### 7.4.2.5 UAS application specific server triggered C2 communication mode switching + +This procedure provides a mechanism for supporting dynamic switching between direct or network assisted C2 communications to UTM-Navigated, initiated by the UAS application specific server (which can be the USS/UTM) after detecting a C2 switching condition which may be required while the UAV enters a no-fly zone. For example, the UAS application specific server needs to take over the control of UAV and fly it to safety (see 3GPP TS 22.125 [2] clause 4.2). + +Figure 7.4.2.5-1 illustrates a UAS application specific server triggered C2 communication mode switching. + +Pre-conditions: + +1. UAE Server has activated the dynamic C2 mode switching capability, as described in clause 7.4.2.1. +2. UAE Client has selected a primary C2 communication mode as described in clause 7.4.2.3, and UAV and UAV-C are engaged in (e.g., direct or network assisted) C2 communication. + +![Sequence diagram illustrating UAS application specific server triggered C2 communication mode switching. The diagram shows four lifelines: UAE client (containing UAV and UAV-C), UAS application specific client, UAE server, and UAS application specific server. Step 1, 'C2 communication mode switching (out of scope)', is shown as a dashed arrow from the UAS application specific server to the UAE server. Step 2, 'UAE-layer assisted dynamic C2 mode switching (clause 7.4.2.4)', is shown as a solid arrow from the UAS application specific client to the UAE server.](f10dc32e3673e1392029a49e958a9d6c_img.jpg) + +``` + +sequenceDiagram + participant UAE_client as UAE client (UAV, UAV-C) + participant UAS_app_client as UAS application specific client + participant UAE_server as UAE server + participant UAS_app_server as UAS application specific server + + Note right of UAS_app_server: 1. C2 communication mode switching (out of scope) + UAS_app_server-->>UAE_server: 1. C2 communication mode switching (out of scope) + + Note right of UAS_app_client: 2. UAE-layer assisted dynamic C2 mode switching (clause 7.4.2.4) + UAS_app_client->>UAE_server: 2. UAE-layer assisted dynamic C2 mode switching (clause 7.4.2.4) + +``` + +Sequence diagram illustrating UAS application specific server triggered C2 communication mode switching. The diagram shows four lifelines: UAE client (containing UAV and UAV-C), UAS application specific client, UAE server, and UAS application specific server. Step 1, 'C2 communication mode switching (out of scope)', is shown as a dashed arrow from the UAS application specific server to the UAE server. Step 2, 'UAE-layer assisted dynamic C2 mode switching (clause 7.4.2.4)', is shown as a solid arrow from the UAS application specific client to the UAE server. + +Figure 7.4.2.5-1: UAS application specific server triggered C2 communication mode switching + +1. The UAS application specific client is instructed directly by a command from the UAS application specific server to switch to UTM-Navigated mode. + +NOTE: This procedure between the UAS application specific server and the UAS application specific client is out of scope of the present document. + +2. The UAE Client initiates the procedure described in clause 7.4.2.4. + +### 7.4.3 Information flows + +#### 7.4.3.1 C2 operation mode management request + +Table 7.4.3.1-1 describes the information flow C2 operation mode management request from the UAS application specific server to the UAE server. + +**Table 7.4.3.1-1: C2 operation mode management request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UASS ID | M | Identity of the UAS application specific server which requests the C2 operation mode management. This ID can be the USS/UTM identifier, when the UAS application specific server is the USS/UTM. | +| UAS ID | M | The identification of the UAS for which the C2 QoS management request applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI | +| C2 operation mode management container (see NOTE 2) | O | The C2 operation mode management container consists of the requirements and policy for C2 operation mode management | +| > C2 operation mode management requirement | M | Identification of the type of the C2 mode switching to be supported by the UAE server. This can be either from direct to network-assisted C2, or from network-assisted to direct C2 or to UTM-Navigated. | +| > Allowed C2 communication modes | M | direct, network assisted, UTM-Navigated | +| > Primary C2 communication mode | M | Primary C2 communication mode (direct, network assisted) | +| > Secondary C2 communication mode | O | Secondary C2 communication mode (direct, network assisted) | +| > Policy of C2 switching | M | Parameters for C2 switching
  • - QoS thresholds on active link
  • - QoS thresholds on target link
| +| > C2 service area | O | The area where the C2 operation mode management request applies. This can be geographical area, or topological area in which the capability is active. | +| > C2 direct mode availability reporting requirement | O | A requirement for C2 direct mode reporting. | +| >> ProSe application codes | O | The ProSe codes used for direct C2 communications. The ProSe codes are used for the ProSe Direct Discovery as specified in [4]. | +| >>Time of validity | O | The time for which the C2 direct mode availability/feasibility checking applies. | +| >>Reporting configuration | O | The configuration of the reporting and periodicity/frequency of reporting required. | +| NOTE 1: Void | | | +| NOTE 2: If C2 operation mode management container IE is not included, it indicates removal of the C2 operation mode management related information. | | | + +#### 7.4.3.2 C2 operation mode management response + +Table 7.4.3.2-1 describes the information flow C2 operation mode management response from the UAE server to the UAS application specific server. + +**Table 7.4.3.2-1: C2 operation mode management response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------| +| Result | M | The positive or negative result of the C2 operation mode management request. | + +#### 7.4.3.3 C2 operation mode management complete + +Table 7.4.3.3-1 describes the information flow C2 operation mode management complete from the UAE server to the UAS application specific server. + +**Table 7.4.3.3-1: C2 operation mode management complete** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------| +| Result | M | The positive or negative result of the C2 communication mode configuration. | + +#### 7.4.3.4 C2-related trigger event report + +Table 7.4.3.4-1 describes the information flow C2-related trigger event report from the UAE client (of the UAV or the UAV-C) to the UAE server. + +**Table 7.4.3.4-1: C2-related trigger event report** + +| Information element | Status | Description | +|-------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAE client ID | M | The identifier of the UAE client which indicates the QoS downgrade | +| UAS UE ID(s) | O | The identifier of the UE ID(s) for which the PC5 connectivity is feasible/available.. | +| Application QoS-related event | M | The report including the expected or actual application QoS / QoE parameters which were change (i.e. latency, throughput, reliability, jitter). The event configuration (thresholds, policies) is provided to the UAE client as described in clause 7.3.2.2. | +| PC5 availability indication | O | The PC5 availability indication for the direct C2 mode. | +| > PC5 capabilities | O | The PC5/ProSe capabilities and configuration information of the involved UAS UEs. | +| > PC5 QoS/access information | O | The PC5 QoS (list of PQIs) and access related information (e.g. DRX cycles, resource pools). | +| > Time of validity | O | The time for which the direct mode is available. | + +#### 7.4.3.5 C2 mode switching confirmation request + +Table 7.4.3.5-1 describes the information flow C2 mode switching confirmation request from the UAE server to the UAS application specific server. + +**Table 7.4.3.5-1: C2 mode switching confirmation request** + +| Information element | Status | Description | +|----------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAE server ID | M | The identifier of the UAE server which requests the C2 mode switching confirmation from USS/UTM | +| UAS ID | M | The identification of the UAS. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI. | +| C2 operation mode switching type | M | The type of the C2 mode switching to be applied (direct to network-assisted, or network-assisted to direct, or to UTM-Navigated). | +| Switching cause | O | Cause information for initiating the switching (e.g. poor radio link quality) | + +#### 7.4.3.6 C2 mode switching confirmation response + +Table 7.4.3.6-1 describes the information flow C2 mode switching confirmation response from the UAS application specific server (USS/UTM) to the UAE server. + +**Table 7.4.3.6-1: C2 mode switching confirmation response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------| +| Result | M | The positive or negative result of the C2 mode switching confirmation response. | + +#### 7.4.3.7 C2 operation mode switching + +Table 7.4.3.7-1 describes the information flow C2 operation mode switching from the UAE server to the UAE client(s) of the affected UAS. + +**Table 7.4.3.7-1: C2 operation mode switching** + +| Information element | Status | Description | +|-----------------------------------------|--------|--------------------------------------------------------------------------------------------------------------| +| UAE server ID | M | The identifier of the UAE server which instructs the UAS to apply the C2 mode switching. | +| C2 operation mode switching requirement | M | The type of the C2 mode switching to be applied (direct to network-assisted, or network-assisted to direct). | +| Time Validity | O | Time validity for the C2 switching requirement | +| Geographical Area | O | Area for which the C2 switching applies | + +#### 7.4.3.8 C2 communication modes configuration request + +Table 7.4.3.8-1 describes the information flow C2 communication modes configuration request from the UAE server to the UAE client. + +**Table 7.4.3.8-1: C2 communication modes configuration request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAS ID | M | The identification of the UAS for which the C2 QoS management request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI. | +| C2 operation mode management configuration (see NOTE 2) | O | The C2 operation mode management configuration information to be configured at the UAS | +| > C2 operation mode management requirement | M | Identification of the type of the C2 mode switching to be supported by the UAE server. This can be either from direct to network-assisted C2, or from network-assisted to direct C2 or to UTM-Navigated. | +| > Allowed C2 communication modes | M | direct, network assisted, UTM-Navigated | +| > Primary C2 communication mode | M | Primary C2 communication mode (direct, network assisted) | +| > Secondary C2 communication mode | O | Secondary C2 communication mode (direct, network assisted) | +| > Policy of C2 switching | M | Parameters for C2 switching
  • - QoS thresholds on active link
  • - QoS thresholds on target link
| +| NOTE 1: Void | | | +| NOTE 2: If C2 operation mode management configuration IE is not included, it indicates removal of the C2 operation mode management configuration at the UAS ID. | | | + +#### 7.4.3.9 C2 communication modes configuration response + +Table 7.4.3.9-1 describes the information flow C2 communication modes configuration response from the UAE client to the UAE server. + +**Table 7.4.3.9-1: C2 communication modes configuration response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------------| +| Result | M | The positive or negative result of reception and storing or removal of the communication mode configuration parameters | + +#### 7.4.3.10 C2 communication mode notification + +Table 7.4.3.10-1 describes the information flow C2 communication mode notification from the UAE client to the UAE server and from the UAE server to the UAS application specific server. + +**Table 7.4.3.10-1: C2 communication mode notification** + +| Information element | Status | Description | +|------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAS ID | M | The identification of the UAS. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI. | +| Selected primary C2 communication mode | M | Selected primary C2 communication mode (direct, network assisted) | +| Selected secondary C2 communication mode | O | Selected secondary C2 communication mode (direct, network assisted) | + +#### 7.4.3.11 C2 communication mode notification acknowledgement + +Table 7.4.3.11-1 describes the information flow C2 communication mode notification acknowledgement from the UAE server to the UAE client and from the UAS application specific server to the UAE server. + +**Table 7.4.3.11-1: C2 communication mode notification acknowledgement** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------| +| Acknowledgement | M | Acknowledgement of selected C2 communication mode(s) | + +#### 7.4.3.12 C2 operation mode switching performed + +Table 7.4.3.12-1 describes the information flow C2 operation mode switching performed from the UAE client to the UAE server. + +**Table 7.4.3.12-1: C2 operation mode switching performed** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------| +| Result | M | The result of the C2 mode switching | + +## 7.5 Real-Time UAV Connection Status Monitoring and Location reporting + +### 7.5.1 General + +This clause enables the UAE server to provide a real-time view of UAV network status and location reporting based on current network connection status, in particular with the supporting of following use cases: + +- Support of real-time monitor the 3GPP network connection with UAVs. +- Support of reporting of loss of communication with UAVs. +- Support of location reporting such as last known location after loss of communication. + +### 7.5.2 Procedures + +#### 7.5.2.1 Procedure for real-time UAV network connection status monitoring and location update + +Figure 7.5.2.1-1 illustrates the real-time network monitoring and location update support for UAV operations. + +Pre-conditions: + +- UAE server has subscribed to the monitoring event API for connection monitoring by the NRM server for both UAV and/or UAV client as specified in clause 14.3.6.2.2 of 3GPP TS 23.434 [5]. +- UAE server has subscribed for the location information and location deviation monitoring events of UAV from LM server as per the clause 9.3.7 and clause 9.3.11.2 specified in 3GPP TS 23.434 [5]. +- Subscription for real-time UAV status information is performed as specified in clause 7.5.2.2. + +![Sequence diagram for real-time UAV network connection status monitoring and location update. Lifelines: LM client (SEAL), LM server (SEAL), UAE server, NRM server (SEAL). Steps: 1. UAE server records current location report; 2. UAE server receives UE connectivity loss; 3. NRM server notifies UE re-connected status; 4. UAE server records the timestamp and triggers location update.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant LM client (SEAL) + participant LM server (SEAL) + participant UAE server + participant NRM server (SEAL) + Note right of UAE server: 1. UAE server records current location report + Note right of UAE server: 2. UAE server receives UE connectivity loss + Note right of NRM server: 3. NRM server notifies UE re-connected status + Note right of UAE server: 4. UAE server records the timestamp and triggers location update + +``` + +Sequence diagram for real-time UAV network connection status monitoring and location update. Lifelines: LM client (SEAL), LM server (SEAL), UAE server, NRM server (SEAL). Steps: 1. UAE server records current location report; 2. UAE server receives UE connectivity loss; 3. NRM server notifies UE re-connected status; 4. UAE server records the timestamp and triggers location update. + +**Figure 7.5.2.1-1: Real-time UAV network connection status monitoring and location update** + +1. The UAE server receives location report and location deviation monitoring event notifications from LM server as specified in clause 9.3.8 and clause 9.3.11.2 of 3GPP TS 23.434 [5]. UAE server shall record the current location reporting timestamp as specified in clause 9.3.2.2 of 3GPP TS 23.434 [5]. +2. The UAE server receives monitoring events notification as specified in clause 14.3.6.3.2 of 3GPP TS 23.434 [5]. If events are regarding loss of UE reachability such as when received "Loss\_of\_connectivity\_notification", the UAE server shall record such event with current timestamp. +3. NRM server sends notification when UE re-connected status is detected as specified in clause 14.3.6.3.2 of 3GPP TS 23.434 [5]. +4. The UAE server shall record such event with current timestamp, plus with last known location information and timestamp as specified in clause 9.3.2.7 of 3GPP TS 23.434 [5] and trigger location update as specified in clause 9.3.4 of 3GPP TS 23.434 [5]. + +#### 7.5.2.2 Subscription for real-time UAV status information + +Figure 7.5.2.2-1 describes the procedure for subscription for real-time UAV status information. + +Pre-condition: + +- UAS application specific server has been provisioned with UAE server information. + +![Sequence diagram for subscription for real-time UAV status information. Lifelines: UAS application specific server, UAE server. Steps: 1. Subscribe realtime UAV status information request; 2. Store subscription; 3. Subscription response.](080a7af02bc47cf21ebfae4e0be39745_img.jpg) + +``` + +sequenceDiagram + participant UAS application specific server + participant UAE server + Note right of UAS application specific server: 1. Subscribe realtime UAV status information request + Note right of UAE server: 2. Store subscription + Note right of UAE server: 3. Subscription response + +``` + +Sequence diagram for subscription for real-time UAV status information. Lifelines: UAS application specific server, UAE server. Steps: 1. Subscribe realtime UAV status information request; 2. Store subscription; 3. Subscription response. + +**Figure 7.5.2.2-1: Subscription for real-time UAV status information** + +1. The UAE application specific server sends subscribe real-time UAV status information request to the UAE server. The request includes one or more UAV ID(s). +2. The UAE server stores the subscription information. +3. The UAE server sends subscription response to the UAS application specific server. + +#### 7.5.2.3 Notification of real-time UAV status information + +Pre-conditions: + +- UAS application specific server has performed subscription as per procedure in clause 7.5.2.2 with UAE server and the procedure for processing real-time UAV status as specified in clause 7.5.2.1 has performed. + +![Sequence diagram for real-time UAV status notification](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` +sequenceDiagram + participant UAE server + participant UAS application specific server + Note left of UAE server: 1. Notify realtime UAV status information + UAE server->>UAS application specific server: + Note right of UAS application specific server: +``` + +A sequence diagram showing the notification of real-time UAV status information. It consists of two lifelines: 'UAE server' on the left and 'UAS application specific server' on the right. A horizontal arrow labeled '1. Notify realtime UAV status information' points from the UAE server to the UAS application specific server. Vertical dashed lines extend downwards from both lifelines. + +Sequence diagram for real-time UAV status notification + +**Figure 7.5.2.3-1: Notification for real-time UAV status information** + +1. When real-time UAV status information is available at the UAE as per the subscription then, the UAE server sends notification of one or more real-time UAV(s) status information to the UAS application specific server. + +#### 7.5.2.4 Unsubscription for real-time UAV status information + +Figure 7.5.2.4-1 describes the procedure for unsubscription for real-time UAV status information. + +Pre-condition: + +- UAS application specific server has performed the subscription procedure as specified in clause 7.5.2.2. + +![Sequence diagram for real-time UAV status unsubscription](2beb95006f1933bed737cfe1e6598db8_img.jpg) + +``` +sequenceDiagram + participant UAS application specific server + participant UAE server + Note left of UAS application specific server: 1. Unsubscribe realtime UAV status information request + UAS application specific server->>UAE server: + Note right of UAE server: 2. Cancel subscription + Note right of UAE server: + UAE server->>UAS application specific server: 3. Unsubscription response + Note left of UAS application specific server: +``` + +A sequence diagram showing the unsubscription for real-time UAV status information. It consists of two lifelines: 'UAS application specific server' on the left and 'UAE server' on the right. Step 1: A horizontal arrow labeled '1. Unsubscribe realtime UAV status information request' points from the UAS application specific server to the UAE server. Step 2: A self-call message labeled '2. Cancel subscription' is shown on the UAE server lifeline. Step 3: A horizontal arrow labeled '3. Unsubscription response' points from the UAE server back to the UAS application specific server. Vertical dashed lines extend downwards from both lifelines. + +Sequence diagram for real-time UAV status unsubscription + +**Figure 7.5.2.4-1: Unsubscription for real-time UAV status information** + +1. The UAE application specific server sends unsubscribe real-time UAV status information request to the UAE server. The request includes the subscription ID. +2. The UAE server cancels the subscription information. +3. The UAE server sends unsubscription response to the UAS application specific server. + +### 7.5.3 Information flows + +#### 7.5.3.1 Information flows between UAE server and SEAL servers + +The usage of information flows between UAE server and SEAL's Location Management Server is specified in clause 7.1.3.2. + +The usage of information flows between UAE server and SEAL's Network Resource Management Server is specified in clause 7.1.4.2. + +#### 7.5.3.2 Subscribe real-time UAV status information request + +Table 7.5.3.2-1 describes the information flow for a UAS application specific server to subscribe to real-time UAV status information at the UAE server. + +**Table 7.5.3.2-1: Subscribe real-time UAV status information request** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------| +| UASS ID | M | The identifier of the UAS application specific server which initiated this request. | +| UAV ID (s) | M | The identifier of one or more UAV(s) (e.g. 3GPP UE ID or CAA level UAV ID) for which the real-time UAV status is requested. | +| Area of Interest | M | Geographic area location information where the UASS server wishes to monitor the UAS's location adherence. | +| Notification Target URI | M | Target URI where the UAS application specific server wishes to receive the notifications about real-time UAV status information. | + +#### 7.5.3.3 Subscribe real-time UAV status information response + +Table 7.5.3.3-1 describes the information flow for UAE server to respond for real-time UAV status subscription request from the UAS application specific server. + +**Table 7.5.3.3-1: Subscribe real-time UAV status information response** + +| Information element | Status | Description | +|-------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| Result | M | Result from the UAE server in response to subscription request indicating success or failure | +| Subscription ID (NOTE) | O | Identifier of a successful subscription. | +| NOTE: This IE is included when the Result indicates success | | | + +### 7.5.3.4 Notify real-time UAV status information + +Table 7.5.3.4-1 describes the information flow for a UAS application specific server to receive notification about real-time UAV status information from the UAE server. + +**Table 7.5.3.4-1: Notify real-time UAV status information** + +| Information element | Status | Description | +|-------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------| +| Subscription ID | M | Identifier of the subscription for this notification. | +| Real-time UAV(s) status information | M | One or more real-time UAV(s) status information | +| >UAV ID | M | The identifier of the UAV (e.g. 3GPP UE ID or CAA level UAV ID) for which the real-time UAV status information is notified. | +| >UAV status information | M | The UAV status information includes the UAV network connection status information, location information and timestamp. | + +### 7.5.3.5 Unsubscribe real-time UAV status information request + +Table 7.5.3.5-1 describes the information flow for a UAS application specific server to unsubscribe to real-time UAV status information at the UAE server. + +**Table 7.5.3.5-1: Unsubscribe real-time UAV status information request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| Subscription ID | M | Identifier of the subscription for this notification. | + +### 7.5.3.6 Unsubscribe real-time UAV status information response + +Table 7.5.3.6-1 describes the information flow for UAE server to respond for real-time UAV status unsubscription request from the UAS application specific server. + +**Table 7.5.3.6-1: Unsubscribe real-time UAV status information response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------| +| Result | M | Result from the UAE server in response to unsubscription request indicating success or failure | + +## 7.6 Change of USS during flight + +### 7.6.1 General + +This feature introduces the UAS application enablement services for supporting change of UAS application specific server. In particular, the UAE layer provides support for the following operations: + +- Support of the registration of the UAE clients multi-USS capability to the UAE server as described in clause 7.1a. +- Support the distribution of the for multi-USS policies from the UAS application specific server to the UAE server and the UAE client, as described in clause 7.6.2.1 and clause 7.6.2.2. +- Support the change of UAS application specific server, as described in clause 7.6.2.3. +- Support the UAE server triggered change of USS, as described in clause 7.6.2.5. + +NOTE: The functions of the USS are out of scope of the present specification. + +### 7.6.2 Procedures + +#### 7.6.2.1 Management of multi-USS configuration + +This procedure manages the multi-USS policies at the UAE server, based on an application request from UAS application specific server to support the change of USS for a UAS. + +Figure 7.6.2.1-1 illustrates the procedure where the UAE server receives an application request for managing the multi-USS policies for a UAS from the UAS application specific server. + +Pre-condition: + +- The UAV has received its UAS ID from the UAS application specific server. +- The UAV has performed the UAS UE registration procedure. + +![Sequence diagram illustrating the Multi-USS management procedure between the UAE server and the UAS application specific server.](2349d057cdc64596dc83dc213b8663a8_img.jpg) + +``` + +sequenceDiagram + participant UAS as UAS application specific server + participant UAE as UAE server + Note left of UAE: 3. Multi-USS configuration (clause 7.6.2.2) + UAS->>UAE: 1. Multi-USS management request + UAE-->>UAS: 2. Multi-USS management response + Note right of UAE: 4. Multi-USS management complete + UAE->>UAS: 4. Multi-USS management complete + +``` + +The diagram shows a sequence of four messages between the UAS application specific server and the UAE server. + 1. The UAS application specific server sends a 'Multi-USS management request' to the UAE server. + 2. The UAE server responds with a 'Multi-USS management response'. + 3. A note on the UAE server side indicates 'Multi-USS configuration (clause 7.6.2.2)'. + 4. Finally, the UAE server sends a 'Multi-USS management complete' message to the UAS application specific server. + +Sequence diagram illustrating the Multi-USS management procedure between the UAE server and the UAS application specific server. + +**Figure 7.6.2.1-1: Multi-USS management procedure** + +1. The UAS application specific server sends to the UAE server a Multi-USS management request. The request includes the UAV (UAE client) identifier and the Multi-USS policies. A Multi-USS policy contains: allowed target USSes (identified by e.g. FQDN), serving USS information, and additional information for change of USS (USS change constraints parameter geo location/area threshold for change of USS by UAV). The UAE server stores the Multi-USS policies corresponding to the UAV ID. In case of removal of a Multi-USS policy for a USS from the UAE server, the request shall include the UAV identifier and a USS identifier (e.g. FQDN) for the USS that will be removed. +2. The UAE server sends to the UAS application specific server a Multi-USS management response with a positive or negative acknowledgement of the request. +3. UAE server executes the multi-USS configuration according to clause 7.6.2.2. +4. After execution of USS management configuration, the UAE server notifies the UAS application specific server with a Multi-USS management complete based on the configured capabilities of the UAE client. + +### 7.6.2.2 Multi-USS configuration + +This procedure enables the configuration of the UAE client, based on a request from UAS application specific server to configure multi-USS policies to the UAE client. + +Figure 7.6.2.2-1 illustrates the Multi-USS configuration procedure. + +Pre-conditions: + +1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4]. +2. UAE server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server. +3. UAE server has performed the Multi-USS management procedure according to clause 7.6.2.1. + +![Sequence diagram for Multi-USS configuration showing interactions between UAE client (UAV), 5GC, and UAE server.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +``` +sequenceDiagram + participant UAV as UAE client (UAV) + participant 5GC as 5GC + participant USS as UAE server + Note left of UAV: 2. Store or remove Multi-USS configuration parameters + USS->>UAV: 1. Multi-USS Configuration request + UAV->>USS: 3. Multi-USS Configuration response +``` + +The diagram illustrates the Multi-USS configuration procedure. It features three lifelines: UAE client (UAV), 5GC, and UAE server. The sequence of messages is as follows: 1. A 'Multi-USS Configuration request' is sent from the UAE server to the UAE client. 2. The UAE client performs an internal action labeled 'Store or remove Multi-USS configuration parameters'. 3. A 'Multi-USS Configuration response' is sent from the UAE client to the UAE server. + +Sequence diagram for Multi-USS configuration showing interactions between UAE client (UAV), 5GC, and UAE server. + +Figure 7.6.2.2-1: Multi-USS configuration + +1. The UAE server sends a Multi-USS configuration request to the UAE client. The UAE client receives a Multi-USS configuration request that includes the Multi-USS policies from the UAE server. In case of removal of one or more Multi-USS policies for a USS from the UAE client, then the request shall only include a USS identifier (e.g. FQDN) for the USSes that will be removed. +2. The UAE client stores or removes the Multi-USS policies as per the information received in step 1. +3. The UAE client sends a Multi-USS configuration response to the UAE server. + +### 7.6.2.3 UAE layer assisted change of USS + +This procedure provides a mechanism for supporting dynamic change of USS which may be performed while the UAV flight is ongoing, due to expected location/mobility of the UAV, emergency events, etc. + +Figure 7.6.2.3-1 illustrates the procedure where the UAE server supports the change of USS. + +Pre-conditions: + +1. UAE client has indicated support of change of USS by the Multi-USS capability. +2. UAS application specific server has provided Multi-USS policies to the UAE client and the UAE server. + +![Sequence diagram illustrating the UAE layer assisted change of USS. The diagram shows five lifelines: UAE client (UAV), 5GC, UAE server, UAS application specific server #1, and UAS application specific server #2. The sequence of messages is: 1. USS change request from UAS application specific server #1 to UAE server; 2. Translation of USS change to UP path change (DNAI change) via AF traffic influence (dashed box); 3. USS change request from UAE server to UAE client (UAV); 4. Perform change of USS (horizontal bar across 5GC, UAE server, and UAS application specific server #1); 5. USS change response from UAE client (UAV) to UAE server; 6. USS change response from UAE server to UAS application specific server #1.](552328a9daaf3bc0069424b500025880_img.jpg) + +``` + +sequenceDiagram + participant UAV as UAE client (UAV) + participant 5GC + participant US as UAE server + participant USS1 as UAS application specific server #1 + participant USS2 as UAS application specific server #2 + + USS1->>US: 1. USS change request + Note right of US: 2. Translation of USS change to UP path change (DNAI change) via AF traffic influence + US->>UAV: 3. USS change request + Note over 5GC, US, USS1: 4. Perform change of USS + UAV->>US: 5. USS change response + US->>USS1: 6. USS change response + +``` + +Sequence diagram illustrating the UAE layer assisted change of USS. The diagram shows five lifelines: UAE client (UAV), 5GC, UAE server, UAS application specific server #1, and UAS application specific server #2. The sequence of messages is: 1. USS change request from UAS application specific server #1 to UAE server; 2. Translation of USS change to UP path change (DNAI change) via AF traffic influence (dashed box); 3. USS change request from UAE server to UAE client (UAV); 4. Perform change of USS (horizontal bar across 5GC, UAE server, and UAS application specific server #1); 5. USS change response from UAE client (UAV) to UAE server; 6. USS change response from UAE server to UAS application specific server #1. + +Figure 7.6.2.3-1: UAE layer assisted change of USS + +1. The UAE server receives a USS change request from a serving USS (UAS application specific server #1), indicating that a target USS (UAS application specific server #2) take over the communication. The request includes the UAV (UAE client) identification information, target USS information and USS change authorization information (e.g. authorization token). Optionally, updated Multi-USS policies for one or more USSes can be included. The UAE server verifies that the request is authorized (e.g., Multi-USS capability is enabled, new USS part of the allowed USS information). +2. If required, the UAE server translates this to a UP path change and interacts with NEF as AF for influence UP path (switching to target DNAI). In particular UAE server (acting as AF) checks whether it can serve the target DNAI corresponding to the target USS based on the mapping of USS to DNAI which was performed in step 2 of clause 7.6.2.5. Interaction with 5GC is performed according to functionality for application function influence on traffic routing, see 3GPP TS 23.502 [13] clause 4.3.6.3. +3. The UAE server forwards the USS change request to the UAE client including target USS information and updated Multi-USS policies. +4. Perform change of USS. +The UAE client initiates communication with the target USS based on the USS change request and the Multi-USS policies. +5. The UAE client sends a USS change response indicating to what USS the change of USS has been performed. +6. The UAE server sends a USS change response to the UAS application specific server indicating that a change of USS has been performed. + +## 7.6.2.4 UAE client assisted change of USS + +This procedure enables the UAE client to provide a dynamic change of USS while the UAV flight is ongoing, due to an emergency change of USS deemed necessary by the UAE client. The UAE client initiates the change of USS on behalf of the USS based on previously provided Multi-USS policy. + +Figure 7.6.2.4-1 illustrates the procedure where the UAE server supports the change of USS. + +Pre-conditions: + +1. UAE client has indicated support of change of USS by the Multi-USS capability. + +2. UAS application specific server has provided Multi-USS policies to the UAE client and the UAE server. + +![Sequence diagram illustrating the UAE client assisted change of USS. The diagram shows four lifelines: UAE client (UAV), UAE server, UAS application specific server #1, and UAS application specific server #2. The sequence of messages is: 1. Emergency change of USS identified by UAE client (from UAE client to UAE server); 2. Perform change of USS (from UAE client to UAS application specific server #2); 3. USS change notification (from UAE client to UAE server); 4. USS change notification (from UAE server to UAS application specific server #1).](08f6ace0c83e7394657fa372b47aec04_img.jpg) + +``` +sequenceDiagram + participant UAV as UAE client (UAV) + participant US as UAE server + participant USS1 as UAS application specific server #1 + participant USS2 as UAS application specific server #2 + Note left of US: 1. Emergency change of USS identified by UAE client + Note over USS1, USS2: 2. Perform change of USS + UAV-->US: 3. USS change notification + US-->USS1: 4. USS change notification +``` + +Sequence diagram illustrating the UAE client assisted change of USS. The diagram shows four lifelines: UAE client (UAV), UAE server, UAS application specific server #1, and UAS application specific server #2. The sequence of messages is: 1. Emergency change of USS identified by UAE client (from UAE client to UAE server); 2. Perform change of USS (from UAE client to UAS application specific server #2); 3. USS change notification (from UAE client to UAE server); 4. USS change notification (from UAE server to UAS application specific server #1). + +**Figure 7.6.2.4-1: UAE client assisted change of USS** + +1. An emergency change of USS is deemed necessary by the UAE Client, and the UAE client initiates the change of USS on behalf of the USS based on previously provided Multi-USS policy. +2. Perform change of USS. The UAE client initiates communication with the target USS (UAS application specific server #2) based on the previously provided Multi-USS policies. +3. The UAE client sends a USS change notification indicating to what USS the change of USS has been performed. The identity of the target USS (UAS application specific server #2) is included. The USS change notification is only sent if the UAE client has a connection to the UAE server. +4. The UAE server sends a USS change notification to the UAS application specific server #1 indicating that a change of USS has been performed. + +### 7.6.2.5 UAE server triggered change of USS + +In multi-USS scenarios, each USS can be physically located in different clouds, and it is also possible that a USS is deployed at the edge. + +Figure 7.6.2.5-1 illustrates the procedure where the UAE server supports change of USS for a multi-USS/LUN scenario, where the interaction with the communication network for supporting a UAS session requires the interaction to more than one USS e.g., due to UAV mobility to different geographical area covered by different edge clouds. + +Pre-conditions: + +- The UAV has performed the UAS UE registration procedure. +- UAE client and UAE server have indicated multi-USS support. + +![Sequence diagram illustrating the UAE server triggered change of USS. The diagram shows interactions between SEAL LMS, UAE server, and UAS application specific server. The steps are: 1. Multi-USS management procedure (between UAE server and UAS application specific server); 2. Mapping of UAS to list of allowable USSs & USS service areas to list of cells (between UAE server and SEAL LMS); 3. Subscribe for UAV Location tracking (between SEAL LMS and UAE server); 4. Detect UAV mobility to target USS area (between UAE server and SEAL LMS); 5. USS change trigger notify (between UAE server and UAS application specific server); 6. Change of USS for UAS (between SEAL LMS and UAE server).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant SEAL LMS + participant UAE server + participant UAS application specific server + Note right of UAE server: 1. Multi-USS management procedure + Note right of SEAL LMS: 2. Mapping of UAS to list of allowable USSs & USS service areas to list of cells + Note right of SEAL LMS: 3. Subscribe for UAV Location tracking + Note right of SEAL LMS: 4. Detect UAV mobility to target USS area + Note right of UAE server: 5. USS change trigger notify + Note right of SEAL LMS: 6. Change of USS for UAS + +``` + +Sequence diagram illustrating the UAE server triggered change of USS. The diagram shows interactions between SEAL LMS, UAE server, and UAS application specific server. The steps are: 1. Multi-USS management procedure (between UAE server and UAS application specific server); 2. Mapping of UAS to list of allowable USSs & USS service areas to list of cells (between UAE server and SEAL LMS); 3. Subscribe for UAV Location tracking (between SEAL LMS and UAE server); 4. Detect UAV mobility to target USS area (between UAE server and SEAL LMS); 5. USS change trigger notify (between UAE server and UAS application specific server); 6. Change of USS for UAS (between SEAL LMS and UAE server). + +**Figure 7.6.2.5-1: UAE server triggered change of USS** + +1. The UAE server has performed the USS management procedure of clause 7.6.3.1; however, at the multi-USS management request, UAE server also receives from UAS application specific server the USS service areas (geographical) for all allowed USSs, and optionally the USS to DNAI mapping and a USS list per given Local USS network (LUN). +2. The UAE server maps each USS with different topological areas based on the USS to DNAI mapping (based on step 1), for all USSs which are allowed for a target area where the UAV is allowed to fly (e.g. within the LUN). Then it also maps and stores all pairs of per LUN or for the areas of interest for the UAV (e.g., based on the allowable routes). +3. The UAE server tracks the location of the UAV, by requesting on-demand location monitoring from SEAL LMS (acting as VAL server in procedure of clause 9.3.4 or clause 9.3.5 of 3GPP TS 23.434 [5]) or via subscribing for monitoring the UAV location deviation (specified in clause 9.3.11 of 3GPP TS 23.434 [5]). +4. The UAE server detects an expected UAV location change to an area covered by a different USS (based on SEAL LMS monitoring subscription/request as in step 3), it generates a trigger event indicating that the UE moves to an area where the USS is overlapping with other USS, or another overlapping USS within LUN area is not available. + +If it is an overlap, the UAE server checks whether the performance of serving USS is expected to get impacted (e.g., by requesting DN performance analytics for the target area) or if the serving USS is not supported at target area, checks what is the best available USS and whether this can provide the same services. The criteria for the best available USS may relate to the location of the UAV, but it can also be the priorities of the USS (based on the policies received) at the target area and the capabilities (services) provided by the target USS. + +5. The UAE server sends to the UAS application specific server a USS change trigger notify indicating the recommendation for a USS change for the UAS and provides the target USS ID. Alternatively, the trigger message indicates a UAV mobility event, based on steps 3/4. +6. The UAS change procedure follows as specified in 7.6.2.3. + +## 7.6.3 Information flows + +### 7.6.3.1 Multi-USS management request + +Table 7.6.3.1-1 describes the information flow Multi-USS management request from the UAS application specific server to the UAE server. + +**Table 7.6.3.1-1: Multi-USS management request** + +| Information element | Status | Description | +|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UASS ID | M | Identity of the UAS application specific server which requests the Multi-USS management. This ID can be the USS identifier, when the UAS application specific server is the USS. | +| UAS ID | M | The identification of the UAS for which the Multi-USS management request applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI | +| UAS registration area | O | The registration area where the UAV is allowed to fly | +| UAS allowed route | O | The UAV allowed route within the registration area. | +| Multi-USS policy management container (see NOTE) | O | The Multi-USS policy management container consists of the requirements and policy for Multi-USS management. | +| > Serving USS information | M | Information about the serving USS identifier | +| > Additional information for change of USS | M | Information about the serving USS, related with the switch to a particular target USS | +| > Area for change of USS | M | The area where the Multi-USS management request applies. This can be geographical area, or topological area in which the capability is active. | +| > Allowed USS(s) information | O | The information for the allowed USSs for the UAS. | +| >> USS ID | M | The identity of the allowed USS from the list of USSs for the target UAS (identified e.g. by FQDN) | +| >> USS service area | M | The geographical area per USS | +| >> USS service requirements | M | The capabilities and key performance requirements per each USS service. | +| >> List of USS DNAI(s) | M | DNAI(s) associated with the target USS. | +| >> LUN ID | M | Identity of the LUN where the report applies | +| NOTE: | If Multi-USS policy management container is not included for a USS, it indicates removal of the Multi-USS policy management related information for this USS. | | + +### 7.6.3.2 Multi-USS management response + +Table 7.6.3.2-1 describes the information flow Multi-USS management response from the UAE server to the UAS application specific server. + +**Table 7.6.3.2-1: Multi-USS management response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------| +| Result | M | The positive or negative result of the Multi-USS management request. | + +### 7.6.3.3 Multi-USS management complete + +Table 7.6.3.3-1 describes the information flow Multi-USS management complete from the UAE server to the UAS application specific server. + +**Table 7.6.3.3-1: Multi-USS management complete** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------| +| Result | M | The positive or negative result of the Multi-USS configuration. | + +### 7.6.3.4 Multi-USS configuration request + +Table 7.6.3.4-1 describes the information flow Multi-USS configuration request from the UAE server to the UAE client. + +**Table 7.6.3.4-1: Multi-USS configuration request** + +| Information element | Status | Description | +|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAS ID | M | The identification of the UAS for which the Multi-USS configuration request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI. | +| Multi-USS policy management configuration (see NOTE) | O | The Multi-USS policy management configuration information to be configured at the UAS. | +| > Allowed USS | M | Identifier of a USS that can be the target of a switch (identified e.g. by FQDN) | +| > Serving USS information | M | Information about the serving USS identifier | +| > Additional information for change of USS | M | Information about the serving USS, related with the switch to a particular target USS | +| > Area for change of USS | M | The area where the Multi-USS management request applies. This can be geographical area, or topological area in which the capability is active. | +| NOTE: | If Multi-USS policy management configuration is not included for a USS, it indicates removal of the Multi-USS policy management configuration for this USS. | | + +### 7.6.3.5 Multi-USS configuration response + +Table 7.6.3.5-1 describes the information flow Multi-USS configuration response from the UAE client to the UAE server. + +**Table 7.6.3.5-1: Multi-USS configuration response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| Result | M | The positive or negative result of the Multi-USS configuration | + +### 7.6.3.6 USS change request + +Table 7.6.3.6-1 describes the information flow USS change request from the UAS application specific server to the UAE server and from the UAE server to the UAE client. + +**Table 7.6.3.6-1: USS change request** + +| Information element | Status | Description | +|--------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UASS ID | M | Identity of the UAS application specific server which requests the change of USS. This ID can be the USS identifier, when the UAS application specific server is the USS. | +| UAS ID | M | The identification of the UAS for which the USS change request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI. | +| USS change authorization information | M | An authorization token to verify the request. | +| Target USS | M | Identification of the USS that is the target of a switch (identified e.g. by FQDN) | +| Target USS info | M | Information for the target USS | +| > USS endpoint | M | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the USS. | +| > USS capabilities | O | The capabilities supported by the target USS | +| > LUN ID | O | Identity of the LUN where the serving/target USS belongs | +| >List of USS DNAI(s) | O | DNAI(s) associated with the target USS. | + +### 7.6.3.7 USS change response + +Table 7.6.3.7-1 describes the information flow USS change response from the UAE client to the UAE server and from the UAE server to the UAS application specific server. + +**Table 7.6.3.7-1: USS change response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| Result | M | The positive or negative result of the USS change request. | + +### 7.6.3.8 USS change notification + +Table 7.6.3.8-1 describes the information flow USS change notification from the UAE client to the UAE server and from the UAE server to the UAS application specific server. + +**Table 7.6.3.8-1: USS change notification** + +| Information element | Status | Description | +|------------------------|--------|------------------------------------------------------------------------------------| +| Reason | M | Reason for change of /USS. | +| Target USS information | M | Identifier of the new USS that the UAV has connected to (identified e.g. by FQDN). | + +### 7.6.3.9 USS change trigger notify + +Table 7.6.3.9-1 describes the information flow USS change trigger notify from the UAE server to the UAS application specific server. + +Table 7.6.3.9-1: USS change trigger notify + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------| +| UAS ID | M | Identity of the UAS for which the trigger applies | +| Serving USS ID | M | Identity of the serving USS | +| Target USS ID | O | Identity of the target USS based on the recommendation | +| LUN ID | O | Identity of the LUN where the serving USS belongs | +| UAV mobility event | O | The mobility event e.g., expected UE mobility to a service area outside the current USS serving area | + +## 7.7 UAE layer support for DAA services and applications + +### 7.7.1 General + +This feature enables the UAS application enablement services for assisting the UAS application with DAA handling. In particular, the UAE layer provides support for the following operations: + +- Support of the registration of the UAE clients DAA assistance capability to the UAE server as described in clause 7.1a. +- Support the distribution of the DAA application policy from the UAS application specific server to the UAE server and the UAE client, as described in clause 7.7.2.1. +- Support the UAS application with DAA, as described in clause 7.7.2.2. + +NOTE: The Detect and Avoid operations are out of scope of the present specification. + +### 7.7.2 Procedures + +#### 7.7.2.1 Configuration of DAA policies to the UAE layer and the UAS client + +##### 7.7.2.1.1 Management of DAA support configuration + +Figure 7.7.2.1.1-1 illustrates the DAA support management procedure where the UAE server receives an application request for managing the DAA application policy from the UAS application specific server. + +Pre-condition: + +1. The UAV has received its UAS ID from the UAS application specific server. +2. The UAV has performed the UAS UE registration procedure. + +![Sequence diagram illustrating the DAA support management procedure. The diagram shows four steps: 1. DAA Support management request from UAS application specific server to UAE server; 2. DAA Support management response from UAE server to UAS application specific server; 3. DAA configuration from UAE server to UAS application specific server; 4. DAA Support management complete from UAS application specific server to UAE server.](9b25cfd1657391070da4ca3e922b82b1_img.jpg) + +``` + +sequenceDiagram + participant UAS as UAS application specific server + participant UAE as UAE server + Note left of UAE: 3. DAA configuration + UAS->>UAE: 1. DAA Support management request + UAE-->>UAS: 2. DAA Support management response + UAE->>UAS: 4. DAA Support management complete + +``` + +Sequence diagram illustrating the DAA support management procedure. The diagram shows four steps: 1. DAA Support management request from UAS application specific server to UAE server; 2. DAA Support management response from UAE server to UAS application specific server; 3. DAA configuration from UAE server to UAS application specific server; 4. DAA Support management complete from UAS application specific server to UAE server. + +Figure 7.7.2.1.1-1: DAA support management procedure + +1. The UAS application specific server sends to the UAE server a DAA support management request. The request includes the UAV (UAE client) identifier and the DAA application policy. + +2. The UAE server shall send to the UAS application specific server a DAA support management response with a positive or negative acknowledgement of the request. +3. The UAE server shall timestamp and store the DAA application policy and execute the DAA configuration according to clause 7.7.2.1.2. +4. After execution of DAA configuration, the UAE server shall send a DAA support management complete to the UAS application specific server. + +#### 7.7.2.1.2 DAA support configuration procedure + +Figure 7.7.2.1.2-1 illustrates the DAA support configuration procedure. This procedure enables the configuration of the UAE client, based on a request from UAS application specific server to configure the DAA application policy to the UAE client. + +Pre-conditions: + +1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4]. +2. UAE server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server. +3. UAE server has performed the DAA support management procedure according to clause 7.7.2.1.1. + +![Sequence diagram of the DAA support configuration procedure. The diagram shows three lifelines: UAE client (UAV), 5GC, and UAE server. The sequence of messages is: 1. A 'DAA Support configuration request' is sent from the UAE server to the UAE client. 2. Inside the UAE client lifeline, there is a self-call labeled 'Store or remove DAA configuration parameters'. 3. A 'DAA Support configuration response' is sent from the UAE client to the UAE server.](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +``` +sequenceDiagram + participant UAV as UAE client (UAV) + participant 5GC as 5GC + participant US as UAE server + Note left of UAV: 2. Store or remove DAA configuration parameters + US->>UAV: 1. DAA Support configuration request + UAV-->>US: 3. DAA Support configuration response +``` + +Sequence diagram of the DAA support configuration procedure. The diagram shows three lifelines: UAE client (UAV), 5GC, and UAE server. The sequence of messages is: 1. A 'DAA Support configuration request' is sent from the UAE server to the UAE client. 2. Inside the UAE client lifeline, there is a self-call labeled 'Store or remove DAA configuration parameters'. 3. A 'DAA Support configuration response' is sent from the UAE client to the UAE server. + +Figure 7.7.2.1.2-1: DAA support configuration procedure + +1. The UAE server shall send a DAA support configuration request to the UAE client. The UAE client receives a DAA support configuration request from the UAE server that includes the DAA application policy. +2. The UAE client shall store or remove the DAA application policy as per the information received in step 1. The DAA application policy is forwarded to the UAS application. +3. The UAE client shall send a DAA support configuration response to the UAE server. + +#### 7.7.2.2 UAE layer support for DAA applications + +##### 7.7.2.2.1 DAA support involving UAVs with U2X support + +Figure 7.7.2.2.1-1 illustrates the procedure with DAA support involving UAVs with U2X support. + +Pre-conditions: + +1. UAE server has provided the DAA application policy to the UAE client. + +![Sequence diagram for DAA support involving UAVs with U2X support. The diagram shows three lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence of messages is: 1. Detect UAVs in proximity (internal to UAV), 2. DAA client event information (UAV to server), 3. DAA client event information (server to application), 4. DAA client event information acknowledge (application to server), 5. DAA client event information acknowledge (server to UAV).](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant UAV as UAE client (UAV) + participant Server as UAE server + participant Application as UAS application specific server + Note left of UAV: 1. Detect UAVs in proximity + UAV->>Server: 2. DAA client event information + Server->>Application: 3. DAA client event information + Application->>Server: 4. DAA client event information acknowledge + Server->>UAV: 5. DAA client event information acknowledge + +``` + +Sequence diagram for DAA support involving UAVs with U2X support. The diagram shows three lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence of messages is: 1. Detect UAVs in proximity (internal to UAV), 2. DAA client event information (UAV to server), 3. DAA client event information (server to application), 4. DAA client event information acknowledge (application to server), 5. DAA client event information acknowledge (server to UAV). + +**Figure 7.7.2.2.1-1: DAA support involving UAVs with U2X support** + +1. The UAE layer has, e.g. based on information provided by the U2X layer, detected UAVs in proximity, see 3GPP TS 23.256 [4] clause 5.6. The UAV informs its own UAS application specific server about the detected collision. +2. The UAE client shall send a DAA client event information to the UAE server with information about one or more UAVs in proximity as detected in step 1. +3. The UAE server shall record the DAA client event information with current timestamp. UAE server shall request UAE client location information from the SEAL location services. The UAE server shall record the received location information with current timestamp. The UAE server shall send the DAA client event information to the UAS application specific server. +4. The UAS application specific server provides a DAA client event information acknowledge to the UAE server. The UAS application specific server may include more information in the acknowledgement (e.g., other UAVs detected information by UAS application layer mechanisms). +5. The UAE server shall send a DAA client event information acknowledge to the UAE client, and the UAE client shall provide the application layer (i.e. UAS client) with the consolidated information from the UAS application specific server. + +#### 7.7.2.2.2 DAA support involving UAVs without U2X support + +Figure 7.7.2.2.2-1 illustrates the procedure with DAA support involving UAVs without U2X support. + +Pre-conditions: + +1. UAS application specific server has provided DAA configuration parameters to the UAE client. +2. The UAV does not support U2X layer. + +![Sequence diagram for DAA support involving UAVs without U2X support. The diagram shows three lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence of messages is: 1. Determines UAVs in the proximity of the UAV (internal to application), 2. DAA server event information (application to server), 3. DAA server event information (server to UAV), 4. DAA server event information acknowledge (UAV to server), 5. DAA server event information acknowledge (server to application).](17439b945bd5156395c7ba15bf04f8fb_img.jpg) + +``` + +sequenceDiagram + participant UAV as UAE client (UAV) + participant Server as UAE server + participant Application as UAS application specific server + Note right of Application: 1. Determines UAVs in the proximity of the UAV + Application->>Server: 2. DAA server event information + Server->>UAV: 3. DAA server event information + UAV->>Server: 4. DAA server event information acknowledge + Server->>Application: 5. DAA server event information acknowledge + +``` + +Sequence diagram for DAA support involving UAVs without U2X support. The diagram shows three lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence of messages is: 1. Determines UAVs in the proximity of the UAV (internal to application), 2. DAA server event information (application to server), 3. DAA server event information (server to UAV), 4. DAA server event information acknowledge (UAV to server), 5. DAA server event information acknowledge (server to application). + +**Figure 7.7.2.2.2-1: DAA support involving UAVs without U2X support** + +1. The UAS application specific server has received information about UAVs (e.g. via UAS application layer mechanism or as in step 3 of clause 7.7.2.2.1). The UAS application specific server determines the information of the UAVs which may be in the proximity of the UAV. + +2. The UAS application specific server sends a DAA server event information to the UAE server which includes information of other UAVs in the proximity of the UAV. The UAE server shall verify that the request is authorized before sending the DAA server event information to the UAE client. +3. The UAE server performs coordination with Real-Time UAV connection status monitoring and location reporting is performed by the UAE server, see clause 7.5 and 3GPP TS 23.434 [5], clause 9.3. The UAE server shall send a DAA server event information to the UAE client comprising the UAVs information and location of each UAV in proximity of the UAV. +4. The UAE client shall send to the UAE server a DAA server event information acknowledge. +5. The UAE server shall send a DAA server event information acknowledge to the UAS application specific server. + +### 7.7.3 Information flows + +#### 7.7.3.1 DAA support management request + +Table 7.7.3.1-1 describes the information flow DAA support management request from the UAS application specific server to the UAE server. + +**Table 7.7.3.1-1: DAA support management request** + +| Information element | Status | Description | +|----------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UASS ID | M | Identity of the UAS application specific server which requests the DAA management. This ID can be the USS identifier, when the UAS application specific server is the USS. | +| UAS ID | M | The identification of the UAS for which the DAA support management request applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI | +| The DAA application policy | O | The DAA application policy. | + +#### 7.7.3.2 DAA support management response + +Table 7.7.3.2-1 describes the information flow DAA support management response from the UAE server to the UAS application specific server. + +**Table 7.7.3.2-1: DAA support management response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| Result | M | The positive or negative result of the DAA support management request. | + +#### 7.7.3.3 DAA support management complete + +Table 7.7.3.3-1 describes the information flow DAA support management complete from the UAE server to the UAS application specific server. + +**Table 7.7.3.3-1: DAA support management complete** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------| +| Result | M | The positive or negative result of provision of the DAA application policy to the UAS application. | + +### 7.7.3.4 DAA support configuration request + +Table 7.7.3.4-1 describes the information flow DAA support configuration request from the UAE server to the UAE client. + +**Table 7.7.3.4-1: DAA support configuration request** + +| Information element | Status | Description | +|----------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAS ID | M | The identification of the UAS for which the DAA management request applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI | +| The DAA application policy | O | The DAA application policy. | + +### 7.7.3.5 DAA support configuration response + +Table 7.7.3.5-1 describes the information flow DAA support configuration response from the UAE client to the UAE server. + +**Table 7.7.3.5-1: DAA support configuration response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------| +| Result | M | The positive or negative result of provision of the DAA application policy to the UAS application. | + +### 7.7.3.6 DAA client event information + +Table 7.7.3.6-1 describes the information flow DAA client event information from the UAE client to the UAE server and from the UAE server to the UAS application specific server. + +**Table 7.7.3.6-1: DAA client event information** + +| Information element | Status | Description | +|--------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAS ID | M | The identification of the UAS for which the DAA client support information applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI. | +| UAE layer detected information | M | List of UASes where e.g. U2X layer has detected possible flight path conflict. | +| > UAS identity | M | The identification of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict. | +| > Location information | M | Location of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict. | + +### 7.7.3.7 DAA client event information acknowledge + +Table 7.7.3.7-1 describes the information flow DAA client event information acknowledge from the UAS application specific server to the UAE server and from the UAE server to the UAE client. + +**Table 7.7.3.7-1: DAA client event information acknowledge** + +| Information element | Status | Description | +|--------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAS ID | M | The identification of the UAS for which the DAA client support information acknowledge applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI | +| UAE layer detected information | M | List of UASes where the UAS application specific server has confirmed possible flight path conflict. | +| > UAS identity | M | The identification of a UAS where UAS application specific server has confirmed possible flight path conflict. | +| > Location information | M | Location of a UAS where UAS application specific server has confirmed possible flight path conflict. | + +### 7.7.3.8 DAA server event information + +Table 7.7.3.8-1 describes the information flow DAA server event information from the UAS application specific server to the UAE server and from the UAE server to the UAE client. + +**Table 7.7.3.8-1: DAA server event information** + +| Information element | Status | Description | +|--------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UAS ID | M | The identification of the UAS for which the DAA server support information applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI | +| UAE layer detected information | M | List of UASes where the UAS application specific server has confirmed possible flight path conflict. | +| > UAS identity | M | The identification of an UAS where UAS application specific server has confirmed possible flight path conflict. | +| > Location information | M | Location of an UAS where UAS application specific server has confirmed possible flight path conflict. | + +### 7.7.3.9 DAA server event information acknowledge + +Table 7.7.3.9-1 describes the information flow DAA server event information acknowledge from the UAE client to the UAE server and from the UAE server to the UAS application specific server. + +**Table 7.7.3.9-1: DAA server event information acknowledge** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------| +| Reason | M | Acknowledgement of DAA server event information. | + +## 7.8 Tracking dynamic UAVs in an application defined area relative to a host UAV + +### 7.8.1 General + +The UAE server can be responsible for tracking a host UAV's dynamic information (i.e., information of other dynamic UAVs in an application defined area relative to a host UAV). As per a proximity range set by the application layer (e.g. UAS Application Specific Server), the UAE layer supports providing the dynamic information (i.e. other UAVs' location information) to the UAS Application Specific Server (UTM/USS) and/or to the host UAV. This feature can be utilized by UAS applications (e.g. DAA, Dynamic maps). + +This feature utilizes the following procedures: + +- UAS Application Specific Server or the host UAV subscription for host UAV's dynamic information with UAE server. +- UAE server tracking host UAV's UE location with support from SEAL's location management server. +- UAE server management of dynamic UE location based group. +- UAE server obtaining dynamic information from the UAVs in application defined proximity range of the host UAV. +- UAE server notification of host UAV's dynamic information to the UAS Application Specific Server and/or to the host UAV. + +NOTE: The details of the usage of dynamic information of host UAV by UAS Application Specific Server or by the host UAV is out of scope of this specification. + +## 7.8.2 Procedures + +### 7.8.2.1 Subscription for host UAV dynamic information + +Figure 7.8.2.1-1 describes the procedure for subscription for host UAV's dynamic information. + +Pre-condition: + +- UAS Application Specific Server has registered with UAE server 1 which is responsible for the host UAV. +- The UAV ID and application defined proximity range information are configured on the host UAV. + +![Sequence diagram for subscription for host UAV dynamic information](faa6766e9ed23a192edcbbbbb753e88c_img.jpg) + +``` +sequenceDiagram + participant UAS as UAS Application Specific Server or UAE client of the Host UAV + participant UAE as UAE server 1 (responsible for the host UAV) + participant LMS as Location management server 1 + + Note right of UAE: 2. Store subscription + Note right of LMS: 4. Obtain and track dynamic UE location for the UAV ID + + UAS->>UAE: 1. Subscribe host UAV dynamic information request + UAE->>UAS: 3. Subscribe host UAV dynamic information response + Note right of UAE: 2. Store subscription + Note right of LMS: 4. Obtain and track dynamic UE location for the UAV ID +``` + +The diagram is a sequence diagram illustrating the procedure for subscription for host UAV dynamic information. It involves three participants: UAS Application Specific Server or UAE client of the Host UAV, UAE server 1 (responsible for the host UAV), and Location management server 1. The sequence of messages is: 1. The UAS sends a 'Subscribe host UAV dynamic information request' to the UAE server 1. 2. The UAE server 1 stores the subscription information. 3. The UAE server 1 sends a 'Subscribe host UAV dynamic information response' back to the UAS. 4. The UAE server 1 obtains and initiates tracking the host UAV location from the location management server 1. + +Sequence diagram for subscription for host UAV dynamic information + +Figure 7.8.2.1-1: Subscription for host UAV dynamic information + +1. The UAS Application Specific Server or UAE client of host UAV sends a subscribe host UAV dynamic information request to the UAE server 1. The request includes the UAV ID of the host UAV, application defined proximity range information. +2. The UAE server 1 stores the subscription information. +3. The UAE server 1 sends subscription response to the UAS Application Specific Server. +4. The UAE server 1 obtains and initiates tracking the host UAV location from the location management server 1 as specified in 3GPP TS 23.434 [5]. + +### 7.8.2.2 Management of dynamic UE location based group + +Figure 7.8.2.2-1 describes the procedure for management of dynamic UE location based group. + +Pre-condition: + +- UAE server 1 has received an updated location of the host UAV as per procedure specified in 3GPP TS 23.434 [5]. + +- UAE server 1 is configured with UAE server 2..N information of other UAS operator and their supported region of operation. + +![Sequence diagram illustrating the management of dynamic UE location group. The diagram shows interactions between UAE server 1 (responsible for host UAV), Location management server 1, UAE server 2..N (Other UAS operators in the UE location), and Location Management Server 2..N. The steps are: 1. Trigger for dynamic UE location group creation/update; 2. Get Dynamic UEs information at the UE location; 3. Determine the UAE server(s) of other UAS operators operating in the UE location and Range; 4. Get Dynamic UEs information at the UE location from UAE server 2..N; 5. Get Dynamic UEs information at the UE location; 6. Get response with UE list; 7. Create/update the Dynamic UE location-based group.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant UAE_server_1 as UAE server 1 +(responsible for host UAV) + participant LMS_1 as Location management server 1 + participant UAE_server_2N as UAE server 2..N +(Other UAS operators in the UE location) + participant LMS_2N as Location Management Server 2..N + + Note left of UAE_server_1: 1. Trigger for dynamic UE location group creation/update + UAE_server_1->>LMS_1: 2. Get Dynamic UEs information at the UE location + Note left of UAE_server_1: 3. Determine the UAE server(s) of other UAS operators operating in the UE location and Range. + UAE_server_1->>UAE_server_2N: 4. Get Dynamic UEs information at the UE location from UAE server 2..N + Note right of UAE_server_2N: 5. Get Dynamic UEs information at the UE location + UAE_server_2N->>UAE_server_1: 6. Get response with UE list + Note left of UAE_server_1: 7. Create/update the Dynamic UE location-based group + +``` + +Sequence diagram illustrating the management of dynamic UE location group. The diagram shows interactions between UAE server 1 (responsible for host UAV), Location management server 1, UAE server 2..N (Other UAS operators in the UE location), and Location Management Server 2..N. The steps are: 1. Trigger for dynamic UE location group creation/update; 2. Get Dynamic UEs information at the UE location; 3. Determine the UAE server(s) of other UAS operators operating in the UE location and Range; 4. Get Dynamic UEs information at the UE location from UAE server 2..N; 5. Get Dynamic UEs information at the UE location; 6. Get response with UE list; 7. Create/update the Dynamic UE location-based group. + +**Figure 7.8.2.2-1: Management of dynamic UE location group** + +1. Dynamic UE location based group creation or update is triggered (e.g. notified of the UE location of host UAV) via the step 4 in clause 7.8.2.1 for the UAV ID of the host UAV. +2. UAE server 1 uses its associated LMS 1 to obtain the dynamic UE list and the corresponding location information in the proximity area of the host UAV by providing the application defined proximity range and the UE location of the host UAV as specified in clause 9.3.10 of 3GPP TS 23.434 [5]. +3. UAE server 1 determines the list of other UAE servers 2..N operating in the same location. +4. For each UAE server determined in step 3, UAE server 1 requests the dynamic UE list and its corresponding location information for the application defined proximity range by providing the UE location of the host UAV. +5. The UAE server(s) 2..N obtain UE information corresponding to the UE location and application defined proximity range from its corresponding LMS 2..N as specified in 3GPP TS 23.434 [5]. +6. The UAE server(s) 2..N sends get response with UE list in the UE location and application defined proximity range to UAE server 1. +7. If UAE server 1 has no dynamic UE location group for the UAV ID, the UAE server 1 creates a dynamic UE location based group with the UE list received from its LMS and other UAE server(s) 2..N. Further UAE server 1 stores the dynamic UE location based group. Otherwise, the UAE server 1 updates the dynamic UE location group with the latest UE information. The UAVs whose locations are no more within the application defined proximity range are removed from the dynamic UE location group. + +### 7.8.2.3 Obtaining dynamic information of the UEs in application defined proximity range + +#### 7.8.2.3.1 Subscription procedure within UAS operator + +Figure 7.8.2.3.1-1 describes the subscription procedure within UAS operator to obtain dynamic information from the UEs in application defined proximity range. + +Pre-condition: + +- UAE server 1 is tracking the host UAV and has created the dynamic UE location based group as per procedure in clause 7.8.2.2. + +![Sequence diagram for subscription procedure within UAS operator](a057800564be3506d2d87b6a4daee25b_img.jpg) + +``` +sequenceDiagram + participant UAE server 1 + participant UAE client(s) + Note right of UAE client(s): 2. Store subscription + UAE server 1->>UAE client(s): 1. Subscribe dynamic information request + Note right of UAE client(s): 2. Store subscription + UAE client(s)-->>UAE server 1: 3. Subscription response +``` + +The diagram shows a sequence of three messages between 'UAE server 1' and 'UAE client(s)'. 1. 'UAE server 1' sends a 'Subscribe dynamic information request' to 'UAE client(s)'. 2. 'UAE client(s)' performs an internal action 'Store subscription'. 3. 'UAE client(s)' sends a 'Subscription response' back to 'UAE server 1'. + +Sequence diagram for subscription procedure within UAS operator + +Figure 7.8.2.3.1-1: Subscription procedure within UAS operator + +1. The UAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the UAE clients who are part of the dynamic UE location group. These UAE clients (UAVs) belong to the same UAS operator as the host UAV. The request consists of reporting configuration (e.g. frequency of reporting, event based). +2. The UAE client(s) store the subscription information. +3. The UAE client(s) send a subscription response to the UAE server 1. + +#### 7.8.2.3.2 Subscription procedure across UAS operators + +Figure 7.8.2.3.2-1 describes the subscription procedure across UAS operators to obtain dynamic information from the UEs in application defined proximity range. + +Pre-condition: + +- UAE server 1 has created the dynamic UE location based group as per procedure in clause 7.8.2.2. + +![Sequence diagram for subscription procedure across UAS operators](ac42de838505beb048fb1267c46de428_img.jpg) + +``` +sequenceDiagram + participant UAE server 1 + participant UAE server 2 + participant UAE client(s) + Note right of UAE server 2: 2. Perform subscription + UAE server 1->>UAE server 2: 1. Subscribe dynamic information request + Note right of UAE server 2: 2. Perform subscription + UAE server 2-->>UAE server 1: 3. Subscription response +``` + +The diagram shows a sequence of three messages between 'UAE server 1', 'UAE server 2', and 'UAE client(s)'. 1. 'UAE server 1' sends a 'Subscribe dynamic information request' to 'UAE server 2'. 2. 'UAE server 2' performs an internal action 'Perform subscription' which involves 'UAE client(s)'. 3. 'UAE server 2' sends a 'Subscription response' back to 'UAE server 1'. + +Sequence diagram for subscription procedure across UAS operators + +Figure 7.8.2.3.2-1: Subscription procedure across UAS operators + +1. The UAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the UAE server(s) who's UAVs are part of the dynamic UE location group. The request consists of UAV IDs, reporting configuration (e.g. frequency of reporting, event based). +2. The UAE server 2 performs subscription procedure as specified in clause 7.8.2.3.1 with the UAE client(s). +3. The UAE server 2 sends a subscription response to the UAE server 1. + +NOTE: UAE server 1 initiates this procedure with other UAE servers operating in the area. + +### 7.8.2.3.3 Notification procedure + +Figure 7.8.2.3.3-1 describes the notification procedure of dynamic information from the UEs in application defined proximity range. + +Pre-condition: + +- UAE server 2 has received the notification of dynamic information from its subscribed UAE client(s). + +![Sequence diagram for Figure 7.8.2.3.3-1: Notification procedure. Lifelines: UAE Server 2, UAE Client 2, UAE Client 1, UAE Server 1. Step 1: UAE Client 1 sends '1. Notification of dynamic information' to UAE Server 1. Step 2: UAE Server 1 performs internal action '2. Prepare host UAV dynamic information including all the aggregate information from different UAE clients'.](921458d4fc1b778c2450592ac9745b48_img.jpg) + +``` + +sequenceDiagram + participant UC1 as UAE Client 1 + participant US1 as UAE Server 1 + Note right of US1: 2. Prepare host UAV dynamic information including all the aggregate information from different UAE clients + Note left of US1: 1. Notification of dynamic information + UC1->>US1: 1. Notification of dynamic information + +``` + +Sequence diagram for Figure 7.8.2.3.3-1: Notification procedure. Lifelines: UAE Server 2, UAE Client 2, UAE Client 1, UAE Server 1. Step 1: UAE Client 1 sends '1. Notification of dynamic information' to UAE Server 1. Step 2: UAE Server 1 performs internal action '2. Prepare host UAV dynamic information including all the aggregate information from different UAE clients'. + +Figure 7.8.2.3.3-1: Notification procedure + +1. As per subscription procedure in clause 7.8.2.3.1 and clause 7.8.2.3.2, the UAE client(s) and UAE server 2 (of another UAS operator) send notification of dynamic information to the UAE server 1. The notification includes the nearby UE information (e.g. UAVs), distance with nearby UEs, UEs location information. +2. The UAE server 1 aggregates information from different UAE clients to create the host UAV dynamic information. + +### 7.8.2.4 Notification of host UAV dynamic information + +Pre-conditions: + +- UAS Application Specific Server has performed subscription as per procedure in clause 7.8.2.1 with UAE server 1. +- UAE server 1 has prepared the host UAV dynamic information as per procedure in clause 7.8.2.3.3. + +![Sequence diagram for Figure 7.8.2.4-1: Notification for host UAV dynamic information. Lifelines: UAE server 1 (responsible for host UAV), UAS Application Specific Server or UAE client of Host UAV. Step 1: UAE server 1 sends '1. Notify host UAV dynamic information' to the UAS Application Specific Server. Step 2: The UAS Application Specific Server performs internal action '2. Update the host UAV dynamic information'.](0856d34939157228ac3a54a59882fb10_img.jpg) + +``` + +sequenceDiagram + participant US1 as UAE server 1 (responsible for host UAV) + participant UAS as UAS Application Specific Server or UAE client of Host UAV + Note right of UAS: 2. Update the host UAV dynamic information + Note left of UAS: 1. Notify host UAV dynamic information + US1->>UAS: 1. Notify host UAV dynamic information + +``` + +Sequence diagram for Figure 7.8.2.4-1: Notification for host UAV dynamic information. Lifelines: UAE server 1 (responsible for host UAV), UAS Application Specific Server or UAE client of Host UAV. Step 1: UAE server 1 sends '1. Notify host UAV dynamic information' to the UAS Application Specific Server. Step 2: The UAS Application Specific Server performs internal action '2. Update the host UAV dynamic information'. + +Figure 7.8.2.4-1: Notification for host UAV dynamic information + +1. The UAE server 1 sends notification of host UAV dynamic information to the subscribed entity (i.e. UAS Application Specific Server and/or to the subscribed UAE client of the host UAV). The notification includes the + +aggregated information of all the UEs in the application defined proximity range of the host UAV and the location of the host UAV. + +2. The UAS Application Specific Server or the UAE client of the host UAV updates the host UAV dynamic information with the host UAV dynamic information received in step 1. The UAE client provides the host UAV dynamic information to the UAS Client. + +### 7.8.2.5 Unsubscription for host UAV dynamic information + +Figure 7.8.2.5-1 describes the procedure for unsubscription for host UAV's dynamic information. + +Pre-condition: + +- The UAS Application Specific Server or UAE client of the host UAV have performed the subscription procedure as specified in clause 7.8.2.1 + +![Sequence diagram for unsubscription for host UAV dynamic information. The diagram shows three lifelines: UAS Application Specific Server or UAE client of the Host UAV, UAE server 1 (responsible for the host UAV), and Location management server 1. The sequence of messages is: 1. Unsubscribe host UAV dynamic information request from the first lifeline to the second. 2. Remove subscription from the second lifeline to itself. 3. Unsubscribe host UAV dynamic information response from the second lifeline to the first. 4. Stop tracking dynamic UE location for the UAV ID from the second lifeline to the third.](e42cc691d9c7c4d23e66b04472bb494e_img.jpg) + +``` + +sequenceDiagram + participant UAS as UAS Application Specific Server or UAE client of the Host UAV + participant UAE as UAE server 1 (responsible for the host UAV) + participant LMS as Location management server 1 + Note right of UAE: 2. Remove subscription + UAS->>UAE: 1. Unsubscribe host UAV dynamic information request + UAE->>UAE: 2. Remove subscription + UAE->>UAS: 3. Unsubscribe host UAV dynamic information response + Note right of UAE: 4. Stop tracking dynamic UE location for the UAV ID + UAE->>LMS: 4. Stop tracking dynamic UE location for the UAV ID + +``` + +Sequence diagram for unsubscription for host UAV dynamic information. The diagram shows three lifelines: UAS Application Specific Server or UAE client of the Host UAV, UAE server 1 (responsible for the host UAV), and Location management server 1. The sequence of messages is: 1. Unsubscribe host UAV dynamic information request from the first lifeline to the second. 2. Remove subscription from the second lifeline to itself. 3. Unsubscribe host UAV dynamic information response from the second lifeline to the first. 4. Stop tracking dynamic UE location for the UAV ID from the second lifeline to the third. + +**Figure 7.8.2.5-1: Unsubscription for host UAV dynamic information** + +1. The UAS Application Specific Server or UAE client of host UAV sends a unsubscribe host UAV dynamic information request to the UAE server 1. The request includes subscription ID. +2. The UAE server 1 removes the previously stored subscription information. +3. The UAE server 1 sends unsubscribe response to the UAS Application Specific Server. +4. The UAE server 1 stops tracking the host UAV location from the location management server 1 as specified in 3GPP TS 23.434 [5]. + +## 7.8.3 Information flows + +### 7.8.3.1 Subscribe host UAV dynamic information request + +Table 7.8.3.1-1 describes the information flow for a UAS application specific server to subscribe to host UAV dynamic information at the UAE server. + +**Table 7.8.3.1-1: Subscribe host UAV dynamic information request** + +| Information element | Status | Description | +|-------------------------------------------------|--------|-------------------------------------------------------------------------------------------------| +| UAV ID | M | Identifier of the host UAV. | +| Application defined proximity range information | M | Description of the range information over which the host UAV's dynamic information is required. | + +### 7.8.3.2 Subscribe host UAV dynamic information response + +Table 7.8.3.2-1 describes the information flow for UAE server to respond for host UAV dynamic subscription request from the UAS application specific server. + +**Table 7.8.3.2-1: Subscribe host UAV dynamic information response** + +| Information element | Status | Description | +|-------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| Result | M | Result from the UAE server in response to subscription request indicating success or failure | +| Subscription ID (NOTE) | O | Identifier of a successful subscription. | +| NOTE: This IE is included when the Result indicates success | | | + +### 7.8.3.3 Notify Host UAV dynamic information + +Table 7.8.3.3-1 describes the information flow for a UAS application specific server to receive notification about Host UAV dynamic information from the UAE server. + +**Table 7.8.3.3-1: Notify Host UAV dynamic information** + +| Information element | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------| +| Subscription ID | M | Identifier of the subscription for this notification. | +| Location of the host UAV | M | The location of the host UAV during the Host UAV dynamic information subscription. | +| List of UAVs information | M | The information of the UAVs which were detected in the application defined proximity range. | +| >Nearby UAV ID | M | The identifier of nearby UAS | +| >Location information | M | Location information of the nearby UAV within the application defined proximity range | +| >Distance information | M | Distance information of the nearby UAV, relative to the host UAV. | + +### 7.8.3.4 Notification of dynamic information + +Table 7.8.3.4-1 describes the information flow for notification of dynamic information from UAE client to the UAE server. + +**Table 7.8.3.4-1: Notification of dynamic information** + +| Information element | Status | Description | +|----------------------------|--------|---------------------------------------------------------------------------------------------| +| Subscription ID | M | Identifier of the subscription for this notification. | +| List of UAVs information | M | The information of the UAVs which were detected in the proximity area of the reporting UAV. | +| >Nearby UAV ID | M | The identifier of nearby UAV | +| >Local dynamic information | M | The local dynamic information of the nearby UAV (e.g. location) | + +### 7.8.3.5 Unsubscribe host UAV dynamic information request + +Table 7.8.3.5-1 describes the information flow for a UAS application specific server to unsubscribe the host UAV dynamic information at the UAE server. + +**Table 7.8.3.5-1: Unsubscribe host UAV dynamic information request** + +| Information element | Status | Description | +|------------------------|--------|------------------------------------------| +| Subscription ID (NOTE) | M | Identifier of a successful subscription. | + +### 7.8.3.6 Unsubscribe host UAV dynamic information response + +Table 7.8.3.6-1 describes the information flow for UAE server to respond for host UAV dynamic unsubscribe request from the UAS application specific server. + +**Table 7.8.3.6-1: Unsubscribe host UAV dynamic information response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------| +| Result | M | Result from the UAE server in response to unsubscribe request indicating success or failure | + +## 8 APIs + +### 8.1 General + +The following UAE capabilities are offered as APIs: + +- UAE server APIs; + +The following SEAL service APIs are specified in 3GPP TS 23.434 [5]: + +- Group management server APIs; +- Location management server APIs; +- Configuration management server APIs; +- Identity management server APIs; and +- Key management server APIs. + +When UAS application specific server invokes a SEAL server API directly, the UAS application specific server acting as VAL server shall interact with the corresponding SEAL server over the SEAL-S reference point for the API invocation request and response as specified in 3GPP TS 23.434 [5]. + +### 8.2 UAE server APIs + +#### 8.2.1 General + +Table 8.2.1-1 illustrates the UAE server APIs. + +**Table 8.2.1-1: List of UAE server APIs** + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|-----------------------------------|-------------------------------------------------|---------------------------------|--------------------| +| UAE_C2OperationModeManagement API | Manage_C2OperationMode | UAS application specific server | Request/Response | +| | Notify_SelectedC2Mode (NOTE) | UAS application specific server | Subscribe/notify | +| | Notify_C2ModeSwitching (NOTE) | UAS application specific server | Subscribe/notify | +| | Notify_C2OperationModeManagementComplete (NOTE) | UAS application specific server | Subscribe/notify | +| UAE_RealtimeUAVStatus API | Subscribe_RealtimeUAVStatus | UAS application specific | Subscribe/notify | + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---------------------------------|------------------| +| | | server | | +| | Unsubscribe_RealtimeUAVStatus | UAS application specific server | Subscribe/notify | +| | Notify_RealtimeUAVStatus | UAS application specific server | Subscribe/notify | +| UAE_ChangeUSSManagement API | Manage_USSManagement | UAS application specific server | Request/Response | +| | Notify_USSManagementComplete | UAS application specific server | Subscribe/notify | +| | Manage_USSChange | UAS application specific server | Request/Response | +| | Notify_USSChange | UAS application specific server | Subscribe/notify | +| | Notify_USSChangeTrigger | UAS application specific server | Subscribe/notify | +| | Manage_DAAManagement | UAS application specific server | Request/Response | +| | Notify_DAAManagementComplete | UAS application specific server | Subscribe/notify | +| | Notify_DAAClientSupportEvent | UAS application specific server | Subscribe/notify | +| | Manage_DAAServerSupportEvent | UAS application specific server | Request/Response | +| UAE_UAVDynamicInfo API | Subscribe_UAVDynamicInfo | UAS application specific server | Subscribe/notify | +| | Unsubscribe_UAVDynamicInfo | UAS application specific server | Subscribe/notify | +| | Notify_UAVDynamicInfo | UAS application specific server | Subscribe/notify | +| NOTE: The subscribe operation for Notify_C2OperationModeManagementComplete, Notify_SelectedC2Mode and Notify_C2ModeSwitching is part of Manage_C2OperationMode | | | | + +## 8.2.2 UAE\_C2OperationModeManagement API + +### 8.2.2.1 General + +**API description:** This API enables the UAS application specific server to communicate with the UAE server to send configurations for C2 operation modes for the UAS and receive notifications of the selected C2 communication modes from the UAS UEs (i.e. UAV, UAV-C). + +### 8.2.2.2 Manage\_C2OperationMode operation + +**API operation name:** Manage\_C2OperationMode + +**Description:** Manage (initiate, change or delete) the configuration of the C2 operation modes for the UAS UEs. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.4.3.1. + +**Outputs:** Refer clause 7.4.3.2. + +See clause 7.4.2.1 for the details of usage of this API operation. + +### 8.2.2.3 Notify\_SelectedC2Mode + +**API operation name:** Notify\_SelectedC2Mode + +**Description:** Notification of the selected C2 communication modes from the UAS UEs. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.4.3.10. + +**Outputs:** Refer clause 7.4.3.11. + +See clause 7.4.2.3 for the details of usage of this API operation. + +### 8.2.2.4 Notify\_C2ModeSwitching + +**API operation name:** Notify\_C2ModeSwitching + +**Description:** Notification of the C2 communication mode switching from the UAS UEs. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.4.3.5. + +**Outputs:** Refer clause 7.4.3.6. + +See clause 7.4.2.4 for the details of usage of this API operation. + +### 8.2.2.5 Notify\_C2OperationModeManagementComplete + +**API operation name:** Notify\_C2OperationModeManagementComplete + +**Description:** Notification about the C2 operation mode management completion by UAE server. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.4.3.3. + +**Outputs:** None. + +See clause 7.4.2.1 for the details of usage of this API operation. + +## 8.2.3 UAE\_ RealtimeUAVStatus API + +### 8.2.3.1 General + +**API description:** This API enables the UAS application specific server to subscribe for and receive notifications for the realtime status information of the UAV. + +### 8.2.3.2 Subscribe\_RealtimeUAVStatus operation + +**API operation name:** Subscribe\_RealtimeUAVStatus + +**Description:** Subscription for obtaining the realtime UAV status information. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.5.3.2. + +**Outputs:** Refer clause 7.5.3.3. + +See clause 7.5.2.2 for the details of usage of this API operation. + +### 8.2.3.3 Unsubscribe\_RealtimeUAVStatus operation + +**API operation name:** Unsubscribe\_RealtimeUAVStatus + +**Description:** Unsubscription for a existing subscription for obtaining the realtime UAV status information. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.5.3.5. + +**Outputs:** Refer clause 7.5.3.6. + +See clause 7.5.2.4 for the details of usage of this API operation. + +### 8.2.3.4 Notify\_RealtimeUAVStatus operation + +**API operation name:** Notify\_RealtimeUAVStatus + +**Description:** Notification of the realtime UAV status information. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.5.3.4. + +**Outputs:** None. + +See clause 7.5.2.3 for the details of usage of this API operation. + +## 8.2.4 UAE\_ChangeUSSManagement API + +### 8.2.4.1 General + +**API description:** This API enables the UAS application specific server to communicate with the UAE server to send policies, requests for change of USS for the UAS and receive notifications from the UAS UEs (i.e. UAV) about change of USS. + +### 8.2.4.2 Manage\_USSManagement operation + +**API operation name:** Manage\_USSManagement + +**Description:** Manage (initiate, change or delete) the configuration of the policies for change of USS for the UAS UEs. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.6.3.1. + +**Outputs:** Refer clause 7.6.3.2. + +See clause 7.6.2.1 for the details of usage of this API operation. + +#### 8.2.4.3 Notify\_USSManagementComplete operation + +**API operation name:** Notify\_USSManagementComplete + +**Description:** Notification about the USS management completion by UAE server. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.6.3.3. + +**Outputs:** None. + +See clause 7.6.2.1 for the details of usage of this API operation. + +#### 8.2.4.4 Manage\_USSChange operation + +**API operation name:** Manage\_USSChange + +**Description:** Manage change of USS on request from UAS application specific server. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.6.3.6. + +**Outputs:** Refer clause 7.6.3.7. + +See clause 7.6.2.3 for the details of usage of this API operation. + +#### 8.2.4.5 Notify\_USSChange operation + +**API operation name:** Notify\_USSChange + +**Description:** Notification about the change of USS required by UAS UE. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.6.3.8. + +**Outputs:** None. + +See clause 7.6.2.4 for the details of usage of this API operation. + +#### 8.2.4.6 Notify\_USSChangeTrigger + +**API operation name:** Notify\_USSChangeTrigger + +**Description:** Notify a trigger event related to the recommended change of USS. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.6.3.9. + +**Outputs:** None. + +See clause 7.6.2.5 for the details of usage of this API operation. + +## 8.2.5 UAE\_DAASupport API + +### 8.2.5.1 General + +**API description:** This API enables the UAS application specific server to communicate with the UAE server for the DAA application policy and send and receive notifications related with DAA support aspects between the USS and the UAE client. + +### 8.2.5.2 Manage\_DAAManagement operation + +**API operation name:** Manage\_DAAManagement + +**Description:** Manage (initiate, change or delete) configuration of the DAA application policy. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.7.3.1. + +**Outputs:** Refer clause 7.7.3.2. + +See clause 7.7.2.1.1 for the details of usage of this API operation. + +### 8.2.5.3 Notify\_DAAManagementComplete operation + +**API operation name:** Notify\_DAAManagementComplete + +**Description:** Notification about the DAA management completion by UAE server. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.7.3.3. + +**Outputs:** None. + +See clause 7.7.2.1.1 for the details of usage of this API operation. + +### 8.2.5.4 Notify\_DAAClientSupportEvent operation + +**API operation name:** Notify\_DAAClientSupportEvent + +**Description:** Notification about possible UAVs in proximity, identified by the client. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.7.3.6. + +**Outputs:** Refer clause 7.7.3.7. + +See clause 7.7.2.2.1 for the details of usage of this API operation. + +### 8.2.5.5 Manage\_DAA ServerSupportEvent operation + +**API operation name:** Manage\_DAA ServerSupport + +**Description:** Notification about possible UAVs in proximity, identified by the server. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.7.3.8. + +**Outputs:** Refer clause 7.7.3.9. + +See clause 7.7.2.2.2 for the details of usage of this API operation. + +## 8.2.6 UAE\_UAVDynamicInfo API + +### 8.2.6.1 General + +**API description:** This API enables the UAS application specific server to subscribe for and receive notifications for the host UAV dynamic information. + +### 8.2.6.2 Subscribe\_UAVDynamicInfo operation + +**API operation name:** Subscribe\_UAVDynamicInfo + +**Description:** Subscription for obtaining the UAV dynamic information. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.8.3.1. + +**Outputs:** Refer clause 7.8.3.2. + +See clause 7.8.2.1 for the details of usage of this API operation. + +### 8.2.6.3 Unsubscribe\_UAVDynamicInfo operation + +**API operation name:** Unsubscribe\_UAVDynamicInfo + +**Description:** Unsubscription for a existing subscription for obtaining the UAV dynamic information. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.8.3.5. + +**Outputs:** Refer clause 7.8.3.6. + +See clause 7.8.2.x for the details of usage of this API operation. + +### 8.2.6.4 Notify\_UAVDynamicInfo operation + +**API operation name:** Notify\_UAVDynamicInfo + +**Description:** Notification of the UAV dynamic information. + +**Known Consumers:** UAS application specific server. + +**Inputs:** Refer clause 7.8.3.4. + +**Outputs:** None. + +See clause 7.8.2.4 for the details of usage of this API operation. + +## Annex A (informative): Support for edge deployments + +The application architecture for supporting edge applications are specified in 3GPP TS 23.558 [7]. The UAS application layer as specified in clause 5 can be deployed in edge computing environment. + +Figure A-1 illustrates a UAS application layer deployment in edge computing environments. + +![Figure A-1: UAS application layer deployment in edge computing environment. The diagram shows the interaction between a User Equipment (UE) and an Edge Data Network (EDN) through a 5GS. The UE contains layers for UAS application specific client(s), UAE Client, SEAL clients, and Edge Enabler Client (EEC). The EDN contains layers for UAS application specific server(s), UAE server, SEAL servers, Edge Enabler Server (EES), and Edge Configuration Server. Reference points U1-APP, U1-AE, SEAL-UU, EDGE-1, EDGE-3, EDGE-4, and EDGE-5 are shown between the layers and the 5GS.](64544fbada794f3cdf4f78f5d83613e4_img.jpg) + +The diagram illustrates the UAS application layer deployment in an edge computing environment. It is divided into two main entities: User Equipment (UE) and Edge Data Network (EDN), connected via a 5GS (5G System). + +- UE (User Equipment):** + - UAS application specific layer:** Contains "UAS application specific client(s)". + - UAE layer:** Contains "UAE Client". + - SEAL layer:** Contains "SEAL clients". + - EDGE Enabler layer:** Contains "Edge Enabler Client (EEC)". +- EDN (Edge Data Network):** + - UAS application specific layer:** Contains "UAS application specific server(s)". + - UAE layer:** Contains "UAE server". + - SEAL layer:** Contains "SEAL servers". + - EDGE Enabler layer:** Contains "Edge Enabler Server (EES)". + - EDGE-6 layer:** Contains "Edge Configuration Server". +- Reference Points:** + - U1-APP:** Between UAS application specific client(s) in UE and UAS application specific server(s) in EDN. + - U1-AE:** Between UAE Client in UE and UAE server in EDN. + - SEAL-UU:** Between SEAL clients in UE and SEAL servers in EDN. + - EDGE-1:** Between Edge Enabler Client (EEC) in UE and Edge Enabler Server (EES) in EDN. + - EDGE-3:** Between SEAL servers in EDN and Edge Enabler Server (EES) in EDN. + - EDGE-4:** Between Edge Enabler Client (EEC) in UE and Edge Configuration Server in EDN. + - EDGE-5:** Between SEAL clients in UE and Edge Enabler Client (EEC) in UE. + +Figure A-1: UAS application layer deployment in edge computing environment. The diagram shows the interaction between a User Equipment (UE) and an Edge Data Network (EDN) through a 5GS. The UE contains layers for UAS application specific client(s), UAE Client, SEAL clients, and Edge Enabler Client (EEC). The EDN contains layers for UAS application specific server(s), UAE server, SEAL servers, Edge Enabler Server (EES), and Edge Configuration Server. Reference points U1-APP, U1-AE, SEAL-UU, EDGE-1, EDGE-3, EDGE-4, and EDGE-5 are shown between the layers and the 5GS. + +**Figure A-1: UAS application layer deployment in edge computing environment** + +Figure A-1 illustrates how the UAS application architecture with EDGEAPP support for edge deployments can be deployed. In a UE, the UAS application specific client(s), UAE client and SEAL clients interact with the Edge Enabler Client (EEC) via EDGE-5 reference point in order to consume edge services. In an Edge Data Network (EDN), the UAS application specific server(s), UAE server and SEAL servers acting as Edge Application Server (EAS), interacts with the Edge Enabler Server (EES) via EDGE-3 reference point. The service provisioning and EAS discovery enable the UAS application layer entities in the UE to communicate with the application layer entities in the EDN. The interactions between the entities and 5GS are not shown for the sake of simplicity. + +**NOTE:** This clause illustrates an example edge deployment using edge enabler layer. There can be other valid edge deployments enabled for UAS application layer. + +## Annex B (Informative): Deployment models + +### B.1 General + +This clause describes deployments of the functional model specified in clause 5. The reference points utilized from underlying 3GPP network as specified in clause 5.5 is represented as 3GPP interfaces in the deployment models. + +NOTE: The representation of SEAL functionalities in the vertical deployment is specified in 3GPP TS 23.434 [5]. + +## B.2 Deployment of UAE server + +The UAE server deployments can be centralized and distributed. + +### B.2.1 Centralized deployments + +A centralized deployment is where a single UAE server offers the UAE capabilities to one or more UAS application specific servers (e.g. USS/UTM). The UAE server and the UAS application specific server can be co-located in a single physical entity. The UAE server can be deployed either in the PLMN operator domain or deployed in the UAS operator domain. The UAE server connects with the 3GPP network systems (EPS, 5GS) in one or more PLMN operator domain. When UAE server and UAS application specific server are co-located in a single physical entity, the Us reference point between the UAE server and the UAS application specific server is not used. + +Figure B.2.1-1 illustrates a deployment of the UAE server and the UAS application specific server in a single physical entity and deployed in UAS operator domain. The UAE server can be deployed in a separate physical entity from the UAS application specific server in the UAS operator domain. In such deployments, the Us reference point is used for the communication between the UAE server and the UAS application specific server. + +![Diagram of UAE server co-located with UAS application specific server in a single physical entity.](149826281804ec51b5cca5603c88b23b_img.jpg) + +The diagram illustrates a deployment scenario where the UAE server and the UAS application specific server are co-located within a single physical entity, represented by a dashed rectangular box. Inside this box, the 'UAS application specific server' is positioned above the 'UAE server'. This entire entity is situated within the 'UAS operator domain', which is demarcated by a horizontal dashed line. Below this line, the 'PLMN operator domain' is shown. A vertical line, labeled '3GPP interfaces', connects the 'UAE server' inside the dashed box to the '3GPP network systems' located in the PLMN operator domain. + +Diagram of UAE server co-located with UAS application specific server in a single physical entity. + +**Figure B.2.1-1: UAE server co-located with UAS application specific server in a single physical entity** + +Figure B.2.1-2 illustrates a deployment of the UAE server in the PLMN operator domain and the UAS application specific server in the UAS operator domain. The Us reference point is used for the communication between UAS application specific server and the UAE server. The UAE server can support multiple UAS application specific servers. + +![Diagram of UAE server deployment in the PLMN operator domain.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +This diagram illustrates a deployment where the UAE server is located within the PLMN operator domain. At the top, a box labeled 'UAS application specific server' is enclosed in a dashed rectangle labeled 'UAS operator domain'. Below this box is a reference point labeled 'Us'. A horizontal dashed line separates the UAS operator domain from the 'PLMN operator domain' below. In the PLMN operator domain, a box labeled 'UAE server' is enclosed in another dashed rectangle. A vertical line connects the 'UAS application specific server' to the 'UAE server' through the 'Us' reference point. From the bottom of the 'UAE server' box, a vertical line labeled '3GPP interfaces' extends down to a box labeled '3GPP network systems'. + +Diagram of UAE server deployment in the PLMN operator domain. + +**Figure B.2.1-2: UAE server deployed in the PLMN operator domain** + +Figure B.2.1-3 illustrates a deployment of the UAE server which connects to the 3GPP network systems (EPS, 5GS) in multiple PLMN operator domain. The UAE server can be co-located with the UAS application specific server in a single physical entity or deployed in different physical entities. + +![Diagram of UAE server deployment with connections to 3GPP network systems in multiple PLMN operator domains.](cc893412ff9ca2426705e878c75548ba_img.jpg) + +This diagram shows a central 'UAS operator domain' (enclosed in a dashed rectangle) containing two stacked boxes: 'UAS application specific server' on top and 'UAE server' on the bottom. Below the 'UAE server' box, two vertical lines extend downwards, each labeled '3GPP interfaces'. These lines connect to two separate boxes labeled '3GPP network systems'. The left '3GPP network systems' box is located in 'PLMN operator domain 1', and the right one is in 'PLMN operator domain 2'. Both PLMN operator domains are separated from the central UAS operator domain by vertical dashed lines. + +Diagram of UAE server deployment with connections to 3GPP network systems in multiple PLMN operator domains. + +**Figure B.2.1-3: Deployment of UAE server with connections to 3GPP network systems in multiple PLMN operator domains** + +Figure B.2.1-4 illustrates a deployment of the UAE server which provides UAE capabilities to multiple UAS application specific servers over Us reference point and connects to the 3GPP network systems (EPS, 5GS) in multiple PLMN operator domain. + +![Diagram of UAE server deployment with multiple UAS application specific servers.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +The diagram illustrates the deployment of a UAE server within the UAS operator domain. At the top, three separate boxes represent 'UAS application specific server 1', 'UAS application specific server 2', and 'UAS application specific server 3', each enclosed in a dashed rectangle. These three servers are connected via lines labeled 'Us' to a central box labeled 'UAE server', which is also enclosed in a dashed rectangle. Below the UAE server, two vertical boxes labeled '3GPP network systems' are shown, one on the left and one on the right. Each 3GPP network system is connected to the UAE server via a line labeled '3GPP interfaces'. The entire setup is divided into three vertical zones by dashed lines: 'PLMN operator domain 1' on the left, 'UAS operator domain' in the center, and 'PLMN operator domain 2' on the right. The UAE server and the three application-specific servers are all located within the UAS operator domain. + +Diagram of UAE server deployment with multiple UAS application specific servers. + +**Figure B.2.1-4: Deployment of UAE server with connections to multiple UAS application specific servers** + +## B.2.2 Distributed deployment + +The distributed deployment is where multiple UAE servers are deployed either in the UAS operator domain or in the PLMN operator domain. The distributed deployment of the UAE servers provide geographical coverage or support multiple PLMN operator domains in a geographical location. The UAE servers interconnect via UAE-E and the Us reference point is used for interaction between UAS application specific server and the UAE server. + +Figure B.2.2-1 illustrates the deployment of UAE servers in multiple PLMN operator domain and provides UAE capabilities to the UAS application specific server deployed in the UAS operator domain. The UAS application specific server connects via Us to the UAE servers. + +![Figure B.2.2-1: Distributed deployment of UAE servers in multiple PLMN operator domain without interconnection between UAE servers](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +This diagram illustrates a distributed deployment of UAE servers across multiple PLMN operator domains without interconnection between them. At the top, a dashed box labeled 'UAS application specific server' is situated within the 'UAS operator domain'. Below this, a horizontal dashed line separates it from two separate PLMN operator domains: 'PLMN operator domain 1' on the left and 'PLMN operator domain 2' on the right. In each PLMN domain, there is a dashed box containing a 'UAE server'. The 'UAS application specific server' connects via 'Us' interfaces to both the 'UAE server' in domain 1 and the 'UAE server' in domain 2. Each 'UAE server' is connected via '3GPP interfaces' to a '3GPP network systems' box at the bottom of its respective domain. A vertical dashed line runs down the center, separating the two PLMN operator domains. + +Figure B.2.2-1: Distributed deployment of UAE servers in multiple PLMN operator domain without interconnection between UAE servers + +**Figure B.2.2-1: Distributed deployment of UAE servers in multiple PLMN operator domain without interconnection between UAE servers** + +Figure B.2.2-2 illustrates the deployment of multiple UAE servers deployed in multiple PLMN operator domains. The UAS application specific server connects via Us to the UAE server. The interconnection between UAE servers is via UAE-E and supports the UAS applications for the UAS UEs connected to the UAE servers in multiple PLMN operator domains. + +![Figure B.2.2-2: Distributed deployment of UAE servers in multiple PLMN operator domain with interconnection between UAE servers](907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg) + +This diagram illustrates a distributed deployment of UAE servers across multiple PLMN operator domains with interconnection between them. At the top, a dashed box labeled 'UAS application specific server' is shown. Below it, a horizontal dashed line separates it from two PLMN operator domains: 'PLMN operator domain 1' on the left and 'PLMN operator domain 2' on the right. In each domain, there is a dashed box containing a 'UAE server'. The 'UAS application specific server' connects via a 'Us' interface to the 'UAE server' in domain 1. The 'UAE server' in domain 1 is connected via a 'UAE-E' interface to the 'UAE server' in domain 2. Each 'UAE server' is also connected via '3GPP interfaces' to a '3GPP network systems' box at the bottom of its respective domain. A vertical dashed line runs down the center, separating the two PLMN operator domains. + +Figure B.2.2-2: Distributed deployment of UAE servers in multiple PLMN operator domain with interconnection between UAE servers + +**Figure B.2.2-2: Distributed deployment of UAE servers in multiple PLMN operator domain with interconnection between UAE servers** + +Figure B.2.2-3 illustrates the deployment of multiple UAE servers in PLMN operator domain based on geographical coverage. The UAS application specific server connects via Us to the UAE server 1. The UAE servers interconnect via UAE-E and support the UAS communications to the UAS UEs (i.e., UAV, UAV-C) connected to the UAE servers. + +![Figure B.2.2-3: Distributed deployment of UAE servers in PLMN operator domain. The diagram shows a UAS operator domain at the top containing a 'UAS application specific server'. This server connects via a 'Us' interface to the PLMN operator domain below. In the PLMN operator domain, there are two 'UAE server' boxes, 'UAE server 1' and 'UAE server 2', which are interconnected by a 'UAE-E' interface. Both UAE servers connect via '3GPP interfaces' to a common '3GPP network systems' box at the bottom.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +Figure B.2.2-3: Distributed deployment of UAE servers in PLMN operator domain. The diagram shows a UAS operator domain at the top containing a 'UAS application specific server'. This server connects via a 'Us' interface to the PLMN operator domain below. In the PLMN operator domain, there are two 'UAE server' boxes, 'UAE server 1' and 'UAE server 2', which are interconnected by a 'UAE-E' interface. Both UAE servers connect via '3GPP interfaces' to a common '3GPP network systems' box at the bottom. + +**Figure B.2.2-3: Distributed deployment of UAE servers in PLMN operator domain** + +Figure B.2.2-4 illustrates the deployment of multiple UAE servers in the UAS operator domain where UAE server 1 and UAE server 2 connect with 3GPP network system of PLMN operator domain 1 and PLMN operator domain 2 respectively. The UAS application specific server connects via Us to the UAE server 1. The UAE servers interconnect via UAE-E and support the UAS applications for the UAS UEs connected via both the PLMN operator domains. + +![Figure B.2.2-4: Distributed deployment of UAE servers in UAS operator domain. The diagram shows a 'UAS application specific server 1' in the UAS operator domain connecting via a 'Us' interface to 'UAE server 1'. 'UAE server 1' and 'UAE server 2' are interconnected by a 'UAE-E' interface. 'UAE server 1' connects via '3GPP interfaces' to '3GPP network systems' in 'PLMN operator domain 1'. 'UAE server 2' connects via '3GPP interfaces' to '3GPP network systems' in 'PLMN operator domain 2'. A dashed vertical line separates the two PLMN operator domains.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +Figure B.2.2-4: Distributed deployment of UAE servers in UAS operator domain. The diagram shows a 'UAS application specific server 1' in the UAS operator domain connecting via a 'Us' interface to 'UAE server 1'. 'UAE server 1' and 'UAE server 2' are interconnected by a 'UAE-E' interface. 'UAE server 1' connects via '3GPP interfaces' to '3GPP network systems' in 'PLMN operator domain 1'. 'UAE server 2' connects via '3GPP interfaces' to '3GPP network systems' in 'PLMN operator domain 2'. A dashed vertical line separates the two PLMN operator domains. + +**Figure B.2.2-4: Distributed deployment of UAE servers in UAS operator domain** + +## Annex C (informative): Examples of usage of SEAL by UAS application specific server + +All procedures of SEAL services (e.g. GMS, LMS) are available directly for usage by UAS application specific server. Some examples of the usage of SEAL by the UAS application specific server is illustrated below: + +- Group creation procedures of Group Management server provides support for the UAS applications (e.g. paired UAV and UAV-C are grouped) to provide a dedicated group for the UAV and UAV-C to communicate with each other. +- The UAS application specific server (e.g. USS/UTM) monitors the presence of UAVs in a given geographic area by using the Monitoring Location Deviation procedure of the LM server. +- The UAS application specific server (e.g. USS/UTM) can directly fetch the multiple UAV related events from NRM server (e.g. to detect any events related to the UAV, the UAS application specific server can need multiple events related to the UAV (UE) from the 3GPP core network). +- The UAS application specific client and UAS application specific server can utilize the resource management procedures of the NRM server to manage unicast resources associated to SIP sessions. + +## Annex D (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2020-11 | SA6#40-e | | | | | TS skeleton approved in S6-202322 | 0.0.0 | | +| 2020-11 | SA6#40-e | | | | | Implementation of the following pCRs approved by SA6: S6-202204, S6-202324, S6-202354 | 0.1.0 | | +| 2021-01 | SA6#41-e | | | | | Implementation of the following pCRs approved by SA6: S6-210149, S6-210296, S6-210349 | 0.2.0 | | +| 2021-01 | SA6#41-e | | | | | Editorial correction of ref [3] specification number from 23.254 to 23.256. | 0.2.1 | | +| 2021-03 | SA6#42-e | | | | | Implementation of the following pCRs approved by SA6: S6-210555, S6-210556, S6-210718, S6-210719 | 0.3.0 | | +| 2021-04 | SA6#42-BIS-e | | | | | Implementation of the following pCRs approved by SA6: S6-211008, S6-211035, S6-211099, S6-211100, S6-211101, S6-211102, S6-211103, S6-211104, S6-211105 | 0.4.0 | | +| 2021-04 | SA6#43-e | | | | | Implementation of the following pCRs approved by SA6: S6-211254, S6-211304, S6-211308, S6-211311, S6-211363, S6-211364, S6-211365, S6-211366, S6-211386, S6-211458, S6-211459, S6-211460, S6-211461, S6-211462, S6-211463, S6-211468 | 0.5.0 | | +| 2021-06 | SA#92-e | SP-210471 | | | | Presentation for approval at SA#92-e | 1.0.0 | | +| 2021-06 | SA#92-e | SP-210471 | | | | MCC Editorial update for publication after TSG SA approval (SA#92) | 17.0.0 | | +| 2021-06 | SA#92-e | SP-210579 | | | | MCC Editorial update of the titles of the present document as well as ref [4] to align UAS terminology (SA#92) | 17.0.1 | | +| 2021-09 | SA#93-e | SP-210966 | 0003 | 1 | F | Correction of SEAL references | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0004 | 1 | D | Terminology alignment to use uncrewed | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0005 | 1 | F | Alignment with 5GC architecture | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0006 | 1 | F | Resolve EN about Geographical Area | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0007 | | F | Alignment of text in clause 7.4.2.3 | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0008 | | F | Correction to the UAV ID assignment assumption | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0009 | | F | Correction to add the missing reference of UUAA 5GC procedure | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0010 | | F | Correction to the UAV application message information flow | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0011 | | F | Correction to the input and output of Notify C2 communication mode switching operation | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0012 | 1 | F | Correction to add the missing API operation for C2 operation mode configuration complete notification | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0013 | 1 | F | Correction about IP address use as UAV ID | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0014 | 1 | F | Correction to the usage of UAS ID | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0015 | | F | Correction to the C2 operation mode switching confirmation | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0016 | 1 | F | Correction to add the missing UAE layer registration procedure | 17.1.0 | | +| 2021-09 | SA#93-e | SP-210966 | 0017 | 1 | F | Resolving the editor's note regarding usage of realtime UAV status | 17.1.0 | | +| 2021-12 | SA#94-e | SP-211528 | 0018 | | F | Missing API on Realtime UAV status | 17.2.0 | | +| 2021-12 | SA#94-e | SP-211528 | 0019 | | F | Alignment of the term "USS/UTM" throughout TS 23.255 | 17.2.0 | | +| 2021-12 | SA#94-e | SP-211528 | 0020 | | D | Removal of Editor's Note in Introduction | 17.2.0 | | +| 2021-12 | SA#94-e | SP-211528 | 0021 | | F | Missing IE for Realtime UAV status subscription request | 17.2.0 | | +| 2021-12 | SA#94-e | SP-211528 | 0022 | | F | Removal of Editor's Notes in clause 5.2 | 17.2.0 | | +| 2021-12 | SA#94-e | SP-211528 | 0023 | 1 | F | Removal of Editor's Notes in clause 7.3 | 17.2.0 | | +| 2022-03 | SA#95-e | SP-220104 | 0024 | 1 | F | Corrections for operations of C2 communication mode switching | 17.3.0 | | +| 2022-03 | SA#95-e | SP-220104 | 0025 | | F | Correction for realtime UAV status | 17.3.0 | | +| 2022-12 | SA#98-e | SP-221237 | 0027 | 2 | F | Clarifications on usage of EDGE in Annex A | 17.4.0 | | +| 2022-12 | SA#98-e | SP-221237 | 0028 | | F | Removal of normative text in an informative annex | 17.4.0 | | +| 2022-12 | SA#98-e | SP-221251 | 0026 | 1 | B | Requirements for support for multi-USS deployments | 18.0.0 | | +| 2022-12 | SA#98-e | SP-221251 | 0029 | 1 | B | Additions to functional entities on support for multi-USS deployments | 18.0.0 | | +| 2022-12 | SA#98-e | SP-221251 | 0030 | 1 | B | Addition of multi-USS capabilities to UAE layer registration | 18.0.0 | | +| 2022-12 | SA#98-e | SP-221251 | 0031 | 2 | B | Addition of procedures for multi-USS configuration and support at change of USS | 18.0.0 | | +| 2022-03 | SA#99 | SP-230277 | 0033 | 2 | A | Correction of various inconsistencies and unclarities | 18.1.0 | | +| 2022-03 | SA#99 | SP-230297 | 0034 | 2 | B | Addition of IEs to messages related with change of USS | 18.1.0 | | +| 2022-03 | SA#99 | SP-230297 | 0035 | 1 | B | Addition of API for change of USS | 18.1.0 | | +| 2022-03 | SA#99 | SP-230297 | 0036 | 2 | B | Requirements for support for DAA | 18.1.0 | | +| 2022-03 | SA#99 | SP-230297 | 0037 | 4 | B | Additions to functional entities on support for DAA deployments | 18.1.0 | | +| 2022-03 | SA#99 | SP-230297 | 0038 | 1 | B | Addition of DAA assist capability to UAE layer registration | 18.1.0 | | +| 2022-03 | SA#99 | SP-230297 | 0039 | 4 | B | Addition of procedures for DAA configuration | 18.1.0 | | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------|--------| +| 2022-03 | SA#99 | SP-230297 | 0040 | 2 | B | Addition of API for DAA | 18.1.0 | +| 2022-03 | SA#99 | SP-230297 | 0041 | 1 | B | Support the USS re-mapping for a UAS | 18.1.0 | +| 2022-03 | SA#99 | SP-230297 | 0042 | 1 | B | Enhancements to Realtime UAVs status for DAA support | 18.1.0 | +| 2022-03 | SA#99 | SP-230297 | 0043 | 2 | B | Tracking UAVs in an application defined area for DAA support | 18.1.0 | +| 2023-06 | SA#100 | SP-230715 | 0044 | | F | Removal of Editor's Note on multi-USS | 18.2.0 | +| 2023-06 | SA#100 | SP-230715 | 0045 | | F | Removal of Editor's Note on DAA | 18.2.0 | +| 2023-06 | SA#100 | SP-230715 | 0046 | 3 | B | Support for C2 direct mode availability reporting | 18.2.0 | +| 2023-06 | SA#100 | SP-230715 | 0047 | 1 | B | Unsubscribe UAV dynamic information | 18.2.0 | +| 2023-06 | SA#100 | SP-230715 | 0048 | | B | UAV dynamic information API | 18.2.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23282/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/23_series/23282/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..842bc7f393da1eb2b3f3a21ae243828a11836144 --- /dev/null +++ b/raw/rel-18/23_series/23282/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:237e35fe7aa893fc1ab9ac6746c2ab6b038c1a3003ca47a94970c8fc73e4c12a +size 69651 diff --git a/raw/rel-18/23_series/23282/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/raw/rel-18/23_series/23282/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..815195d60b8e18ba31899431525c86770cac1794 --- /dev/null +++ b/raw/rel-18/23_series/23282/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3de183673b3b7158473c4611279ef5cc78bf15b5b80db604f599d6683b3e004 +size 69297 diff --git a/raw/rel-18/23_series/23282/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/raw/rel-18/23_series/23282/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8eb41112cda059c262b36eada9b9ca9a3f696fa --- /dev/null +++ b/raw/rel-18/23_series/23282/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6d73729c5fef9c75c52d777c3b5e3b73bf1ccc9035c0e1e50b139ccd866e43c +size 56611 diff --git a/raw/rel-18/23_series/23282/164d1b48231be457522b31965610ea3b_img.jpg b/raw/rel-18/23_series/23282/164d1b48231be457522b31965610ea3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cea79e5ae8d920403333f0249765a4964abbb27c --- /dev/null +++ b/raw/rel-18/23_series/23282/164d1b48231be457522b31965610ea3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:452b8292bbfc9e8ca46da0b35627e645a28c5c541742d2c20ba679f9c64afa7c +size 34767 diff --git a/raw/rel-18/23_series/23282/17b9d89b91e10c3efc38193baedee268_img.jpg b/raw/rel-18/23_series/23282/17b9d89b91e10c3efc38193baedee268_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc42dedaae3ea8f6538c163cc7365a9c4f72a75e --- /dev/null +++ b/raw/rel-18/23_series/23282/17b9d89b91e10c3efc38193baedee268_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:620e4733fd5d1b2859f101b80b3a56721cfa0508c9d981dd243f92a4dea90e04 +size 33297 diff --git a/raw/rel-18/23_series/23282/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg b/raw/rel-18/23_series/23282/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3330b1cab9b25580a138bb962cf42743c47623c --- /dev/null +++ b/raw/rel-18/23_series/23282/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1430c783de60f9ecab30b8ef0cae5f81a925bc4786c9042711defa2301c038b +size 40512 diff --git a/raw/rel-18/23_series/23282/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/23_series/23282/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5658b30a2ee440a112aa5a2572d861bb6757669a --- /dev/null +++ b/raw/rel-18/23_series/23282/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f593762f25c383f1a46e0aea679f848498bcea3da3196340d3cecc042b22c409 +size 64279 diff --git a/raw/rel-18/23_series/23282/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg b/raw/rel-18/23_series/23282/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e731448cf767ef8fa4c0cd67144cad265f2238b --- /dev/null +++ b/raw/rel-18/23_series/23282/1be8e9cad5f38fa47bdb81e549a3bec9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c45ab127910f9b09479bea1ab99600e99faf67bdc54e28e429f61892c931ba5 +size 59063 diff --git a/raw/rel-18/23_series/23282/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/raw/rel-18/23_series/23282/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e8fc28a08bd5555e98b4f79237425b345b5ad03 --- /dev/null +++ b/raw/rel-18/23_series/23282/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6e579006e9a63a9e0b6b4fe5865f6cc326b3d3fdb603cc99d2517d26d389f52 +size 27128 diff --git a/raw/rel-18/23_series/23282/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/23_series/23282/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da0938102798061bd25273a83a8b486c3662dfcd --- /dev/null +++ b/raw/rel-18/23_series/23282/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afcf4f6a1569dfd57fccbd733c7242fdb7ad081d1f33129d2a96f59b0f75f578 +size 34583 diff --git a/raw/rel-18/23_series/23282/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/raw/rel-18/23_series/23282/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..630414941180bee05dd7c30257151ed6de25634d --- /dev/null +++ b/raw/rel-18/23_series/23282/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06b5ba527f9ed41847ed540a146970effaa32980f9ade25f528e29312e4c6a0c +size 58288 diff --git a/raw/rel-18/23_series/23282/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/23_series/23282/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5eea6bbf1948dd22c2efcc76c7cda250fa86d8c4 --- /dev/null +++ b/raw/rel-18/23_series/23282/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:077826e05004ec8f631c2130d234cd2374e4c31143f1ae3333b499470e0532ef +size 87597 diff --git a/raw/rel-18/23_series/23282/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/23_series/23282/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1fc9d3254c46f631dbcf27dd8a039da89f39586 --- /dev/null +++ b/raw/rel-18/23_series/23282/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9e6968ede968446b3e2bd35dfe08e44c2e262ce9c352d7a56fac3bf3b657631 +size 44104 diff --git a/raw/rel-18/23_series/23282/2f58bcce74146d4d983070d93be12291_img.jpg b/raw/rel-18/23_series/23282/2f58bcce74146d4d983070d93be12291_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fae83a5ea52aa8d722edceeae916040d3ed3657c --- /dev/null +++ b/raw/rel-18/23_series/23282/2f58bcce74146d4d983070d93be12291_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99a3d7a20ec312d3bcd458646e7b2c250d22bb090d9be33a68f39a899283794c +size 23256 diff --git a/raw/rel-18/23_series/23282/303fadfb9def251d1575d6221199b158_img.jpg b/raw/rel-18/23_series/23282/303fadfb9def251d1575d6221199b158_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59e23bb83a9e1584194de5f3fb92625e799f5464 --- /dev/null +++ b/raw/rel-18/23_series/23282/303fadfb9def251d1575d6221199b158_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8094e85a12b1274dbe4adc80d200994019727030613d77beedc5ee81cd76f6b9 +size 55013 diff --git a/raw/rel-18/23_series/23282/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/raw/rel-18/23_series/23282/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d2fb0923b44ae0927e5eabc274f637323957908 --- /dev/null +++ b/raw/rel-18/23_series/23282/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8b5d820b09faf9bd6ada79ce4b6c3c38ac5641a7c01201396ff1ed6b5fcd624 +size 19229 diff --git a/raw/rel-18/23_series/23282/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/raw/rel-18/23_series/23282/3f1987804d7d78bc3b3bc560e974280a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..169ca8df7bb37ce976e03ee6fd617c50c2c6644e --- /dev/null +++ b/raw/rel-18/23_series/23282/3f1987804d7d78bc3b3bc560e974280a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da8ffdea8b67e0220a1bcc0d86362d51567fd53f0ed41d290ea9b5201ec5b1cd +size 42917 diff --git a/raw/rel-18/23_series/23282/4356776ca004ecba5d599667a155d7d4_img.jpg b/raw/rel-18/23_series/23282/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..837dcbdb80e64130ce6e4c143c6139fa1fc15b2a --- /dev/null +++ b/raw/rel-18/23_series/23282/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de7ec087b39668c049a8f5ea34fcc66a303961dbda324c38f5fb657a3c713060 +size 29617 diff --git a/raw/rel-18/23_series/23282/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/raw/rel-18/23_series/23282/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17353e60568c8f1e8d20ece1d854eb1074edf6d7 --- /dev/null +++ b/raw/rel-18/23_series/23282/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4899a7343539e1b3fc26d386cb445d65830fecb44505e7bf9ecbcec14159c2d6 +size 22919 diff --git a/raw/rel-18/23_series/23282/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/raw/rel-18/23_series/23282/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9cab22e15f18c7b495f3503fc3b5014b1b3ef37 --- /dev/null +++ b/raw/rel-18/23_series/23282/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62a38b8cb966f070bb53c2e037a745e8f0d2a150ca13c5448f5d4b7d9bf33a01 +size 75416 diff --git a/raw/rel-18/23_series/23282/474a819357587e34949a3e110ff19b30_img.jpg b/raw/rel-18/23_series/23282/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d889172d60df9ed3d894a23ad54c6cd89ce7ea4 --- /dev/null +++ b/raw/rel-18/23_series/23282/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50509729d1130ff9f4595f720ad5205ef6241729e46a44d2f4dc1d1cc01bc410 +size 62784 diff --git a/raw/rel-18/23_series/23282/4792a2ccd62226861fadc22117edb7b1_img.jpg b/raw/rel-18/23_series/23282/4792a2ccd62226861fadc22117edb7b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d57cd452f721c0f2c32a82831269d556488ddb59 --- /dev/null +++ b/raw/rel-18/23_series/23282/4792a2ccd62226861fadc22117edb7b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20388c59049d0f50d851d8a9a907e81b22006313b895033aeb0aef0dc902a3ca +size 45102 diff --git a/raw/rel-18/23_series/23282/50214d232017279410e9c9db8eb75119_img.jpg b/raw/rel-18/23_series/23282/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb37a2d4da75a6c2b09c5e31ad023e1d7bcc9ad7 --- /dev/null +++ b/raw/rel-18/23_series/23282/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1126427d43dbb0ddebd24c28bbf4b3fb7e130cc5d6012d7b68b1ca8dfa30d89 +size 80904 diff --git a/raw/rel-18/23_series/23282/523ab7b925beb555f88b2e1e1336974f_img.jpg b/raw/rel-18/23_series/23282/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17e1244726610ccc740858e8b055000b68f2e7dc --- /dev/null +++ b/raw/rel-18/23_series/23282/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e011b8e2d355116855fa8d39fae124a43a40ef75cdb6ac439398a4778100ac6b +size 56795 diff --git a/raw/rel-18/23_series/23282/54a53f959bb7758332532c1cd5f0ad75_img.jpg b/raw/rel-18/23_series/23282/54a53f959bb7758332532c1cd5f0ad75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd4278cf20fe8fb6b9ec72f164ef370f2116563b --- /dev/null +++ b/raw/rel-18/23_series/23282/54a53f959bb7758332532c1cd5f0ad75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b6faeecae2b25523f19c073f56692cb0c968135d04caf04674f7be80cada22c +size 19750 diff --git a/raw/rel-18/23_series/23282/55136bc716146672fc680fa05989f1d2_img.jpg b/raw/rel-18/23_series/23282/55136bc716146672fc680fa05989f1d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1f970ba54fdab45dfc69026a5bc557ef8dd5d1d --- /dev/null +++ b/raw/rel-18/23_series/23282/55136bc716146672fc680fa05989f1d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95e82734cec7e0904530c390fe420115ac48c36057c5ba0af8cecba947ec066a +size 19495 diff --git a/raw/rel-18/23_series/23282/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/raw/rel-18/23_series/23282/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c2284e93c9d8cfc24a6d7b11716d95986d4098a --- /dev/null +++ b/raw/rel-18/23_series/23282/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99c0102fdd34343ede518057e60fb99d7aa324a0064c1a4ddb87b934b485cc50 +size 62644 diff --git a/raw/rel-18/23_series/23282/5a4e62bead259c258d069fd3663ea670_img.jpg b/raw/rel-18/23_series/23282/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5e9a2c6e148bd341843b54b61c791d45e1e1229 --- /dev/null +++ b/raw/rel-18/23_series/23282/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32507680db2fe236d1817954044c50f174284d89a50b3dbe70d3ac8a27fbc163 +size 41277 diff --git a/raw/rel-18/23_series/23282/5d76c2e9976aaf97001ee189908830fb_img.jpg b/raw/rel-18/23_series/23282/5d76c2e9976aaf97001ee189908830fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d8c8408aec16326f7e866a4de79b0705b575996 --- /dev/null +++ b/raw/rel-18/23_series/23282/5d76c2e9976aaf97001ee189908830fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:213ab157eebe9b3429cc93f0c86d56fbd5bb205c46a70b6ac7c54f0f807ba808 +size 24976 diff --git a/raw/rel-18/23_series/23282/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23282/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1336537ea24b263d6e72d4c0b08c151e2fd17d38 --- /dev/null +++ b/raw/rel-18/23_series/23282/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d8d2ca43f7a92e6b2e4e5ad7020fd87ab1bd2a0801cc5a15e7402b2fa644ec5 +size 9571 diff --git a/raw/rel-18/23_series/23282/6324b252294c0f5d4e34dad4a1202075_img.jpg b/raw/rel-18/23_series/23282/6324b252294c0f5d4e34dad4a1202075_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6644e4fc3f1f21ad648b17b40a333207188a9db --- /dev/null +++ b/raw/rel-18/23_series/23282/6324b252294c0f5d4e34dad4a1202075_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3d64aba190c79fbbf56bf1d6af8c47bc68ab86eed66153d3218d91f9a4c3af4 +size 54851 diff --git a/raw/rel-18/23_series/23282/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23282/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d11a84925375a7bfe4c4cb5df0df597b8b8e3ae4 --- /dev/null +++ b/raw/rel-18/23_series/23282/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd04f99d8abca3de3f4ec7ee170aceee8d0dd26cd26ae07c05bf12b3b39e2df1 +size 5687 diff --git a/raw/rel-18/23_series/23282/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg b/raw/rel-18/23_series/23282/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b67e1ecd7729de1cbbf35cfc1c9ebb51aa2946c6 --- /dev/null +++ b/raw/rel-18/23_series/23282/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1c9c536c6a12289acff1ec11df24736243aed5d93f4784234ca3087ca7f21ae +size 76080 diff --git a/raw/rel-18/23_series/23282/69edc2887e907309499ac95b47ab6905_img.jpg b/raw/rel-18/23_series/23282/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cbfee375fbdef2273eee18a0d7cf4cf299f85b4 --- /dev/null +++ b/raw/rel-18/23_series/23282/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5148dc0c7d907b0ab0e0b74cd1f1c982cb2e0e9ee7f2ade7375406883a7040a7 +size 95131 diff --git a/raw/rel-18/23_series/23282/6a555cff11e140861ce08db72b01a6a2_img.jpg b/raw/rel-18/23_series/23282/6a555cff11e140861ce08db72b01a6a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b6df165ad984b56cc93787877b80dfaef1c380a --- /dev/null +++ b/raw/rel-18/23_series/23282/6a555cff11e140861ce08db72b01a6a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5976b8df200deff6bc690242ec6d1ea4a9d29fd5e2524fb2d5a03cf327d6c9ae +size 43602 diff --git a/raw/rel-18/23_series/23282/759c7d62402f0b4651ddce292be5bdef_img.jpg b/raw/rel-18/23_series/23282/759c7d62402f0b4651ddce292be5bdef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6809a1ce763270c53d43e4776d1c56ff9836215e --- /dev/null +++ b/raw/rel-18/23_series/23282/759c7d62402f0b4651ddce292be5bdef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2f9825caf6f094b65c2e8020d6bc4c4fce914d6aac176af904276e6f0f210b6 +size 63074 diff --git a/raw/rel-18/23_series/23282/75e4b78ee25f885d73120e3066a5253e_img.jpg b/raw/rel-18/23_series/23282/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf7d4cabf4faef197460a5f3be8a26aa8221967c --- /dev/null +++ b/raw/rel-18/23_series/23282/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58a6909bb75b04ad9eda9f3ce6ee38b7c15d8adfa6616a4e79d8f975591016b4 +size 35300 diff --git a/raw/rel-18/23_series/23282/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/23_series/23282/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d28e52e7defe07906db0b5cf0f21a9a0dce2077 --- /dev/null +++ b/raw/rel-18/23_series/23282/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f18296b4520801cc65d0d3a8e63056fac7be226ea46a72db02a081b2a71a83d +size 110434 diff --git a/raw/rel-18/23_series/23282/7b8b192e2853ef28d28eff0241ebe86b_img.jpg b/raw/rel-18/23_series/23282/7b8b192e2853ef28d28eff0241ebe86b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd4d161b6370970ac7b429a08d7ef61c8c6b1296 --- /dev/null +++ b/raw/rel-18/23_series/23282/7b8b192e2853ef28d28eff0241ebe86b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3d90f8ed2304901c852b5d6cd2ac2c9a8f083b8d467f1e53a5f7fed22e67147 +size 75238 diff --git a/raw/rel-18/23_series/23282/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/raw/rel-18/23_series/23282/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2f0f5a15611cfb2da1f1d9a0bab77a406db3c7b --- /dev/null +++ b/raw/rel-18/23_series/23282/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87641e9f0c8e584586f1d1a54a2d348ed9fdd3b7fcf18daa08f983915284a845 +size 59693 diff --git a/raw/rel-18/23_series/23282/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/raw/rel-18/23_series/23282/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f2923731b7c5bdb5c9aee148b9657df4341df8d --- /dev/null +++ b/raw/rel-18/23_series/23282/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5117a8de0066e8683a8bcd0bf30a93a84821a6c074af917ad1dbe41d99a17c1 +size 170018 diff --git a/raw/rel-18/23_series/23282/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/23_series/23282/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b37cda7849225f4717588beceb059598dbc9bd57 --- /dev/null +++ b/raw/rel-18/23_series/23282/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f553680b1a51f9550585b624c984b5d95ee346df41b6bc3dfa19b9d52333561 +size 30847 diff --git a/raw/rel-18/23_series/23282/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/raw/rel-18/23_series/23282/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..564b4c0ddfb4ed2e388a82f41b7c0c1791071852 --- /dev/null +++ b/raw/rel-18/23_series/23282/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88448258e1497668f0df3b3d8ecbb4c1c212826c5332bcae67eb09e2906587a3 +size 39233 diff --git a/raw/rel-18/23_series/23282/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/23_series/23282/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d60a0925b2aef8f49968207f920b178865530e2 --- /dev/null +++ b/raw/rel-18/23_series/23282/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd5f075439e30f8dca84dda4153dc6430642684498d3cfa42dd121688d71baab +size 122148 diff --git a/raw/rel-18/23_series/23282/84a01685710d24f113b18758ed3c6fcb_img.jpg b/raw/rel-18/23_series/23282/84a01685710d24f113b18758ed3c6fcb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcda4b61d2cc45c7e28a41d5daf589482fe6efb --- /dev/null +++ b/raw/rel-18/23_series/23282/84a01685710d24f113b18758ed3c6fcb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:626de6762dc2317876e1cc3aef23936d02d9ee6038bddd141a958e27b70386e8 +size 53752 diff --git a/raw/rel-18/23_series/23282/853f59c89931a666c07903b31d098277_img.jpg b/raw/rel-18/23_series/23282/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3024202815b9e5f7ec30e6aae6cb962be6d90c91 --- /dev/null +++ b/raw/rel-18/23_series/23282/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c586e5144c89fe21ce3d7c8addb35bd417aae2880a23b0ccce824553adf89633 +size 48526 diff --git a/raw/rel-18/23_series/23282/868ef3e0abb37916a7af1e923995f329_img.jpg b/raw/rel-18/23_series/23282/868ef3e0abb37916a7af1e923995f329_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..310403f76288673a194858a2e39da26cb619a0ac --- /dev/null +++ b/raw/rel-18/23_series/23282/868ef3e0abb37916a7af1e923995f329_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b75ce9fcb119e82f07a43a40bf4290eea38aa95235a04ba0ad55dfe008a5251 +size 29800 diff --git a/raw/rel-18/23_series/23282/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/raw/rel-18/23_series/23282/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fceb4e30992b578b7abed11c1b4bf5a7a126a69 --- /dev/null +++ b/raw/rel-18/23_series/23282/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:412e9b84b286fe4912fcbd63ed7742b6fe65129999177b39b811eb19d8b6c4a2 +size 82971 diff --git a/raw/rel-18/23_series/23282/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/raw/rel-18/23_series/23282/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32dc2c80d9380bb34135c03f55bcb05489d46ee8 --- /dev/null +++ b/raw/rel-18/23_series/23282/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c0d0103156d86f4d1c8c34a3a23180e12eaec4d91a3a90bc9e7e64570bf8e08 +size 90462 diff --git a/raw/rel-18/23_series/23282/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/raw/rel-18/23_series/23282/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6d0e1cc043eaae72cf6a143f1d07133b51091c5 --- /dev/null +++ b/raw/rel-18/23_series/23282/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce5dab37f5fd5778df8f3f6824683bd88d477faddcf0ab3e8f3bdb2f4099d708 +size 148550 diff --git a/raw/rel-18/23_series/23282/90ddb84c323b956e2d50a54d3f870566_img.jpg b/raw/rel-18/23_series/23282/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3858b89743325a1ed3323e43ca8b9195df48f7fb --- /dev/null +++ b/raw/rel-18/23_series/23282/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8c1c84be672c192236467426b904ced5b29240df01f45727b46cf98301a0531 +size 82142 diff --git a/raw/rel-18/23_series/23282/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/raw/rel-18/23_series/23282/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01c093557f30d08e428959904ecabb07e7351156 --- /dev/null +++ b/raw/rel-18/23_series/23282/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc718af4baa8ba6c78931bd542f5775970a9bd11b8ef88ffca416a8f2e29b6cb +size 24299 diff --git a/raw/rel-18/23_series/23282/997233d405f0d4b89ddeb7683e047f66_img.jpg b/raw/rel-18/23_series/23282/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..173fc0863cb8384e8447fa472db360c36d0a6c2b --- /dev/null +++ b/raw/rel-18/23_series/23282/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:632bb2747c3bce3c165b4e82cf03eb704d3a5e9d4b6fe226f4a06e0d2e9098b3 +size 118099 diff --git a/raw/rel-18/23_series/23282/9b62a616c7a1097c5da57f001ab6dd64_img.jpg b/raw/rel-18/23_series/23282/9b62a616c7a1097c5da57f001ab6dd64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79065ecfb12ba71c60d48d1e28a9c3fcc5ac56a3 --- /dev/null +++ b/raw/rel-18/23_series/23282/9b62a616c7a1097c5da57f001ab6dd64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b5663f9b3fc8cb2e0fb0c26a1fc6cbd55ff1712356c0e31de76368c879c0941 +size 50895 diff --git a/raw/rel-18/23_series/23282/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/23_series/23282/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..464ba82192c08f927a3c6b7c64e9c3ba3ee759b0 --- /dev/null +++ b/raw/rel-18/23_series/23282/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd4a43587b3b19517adb618732b3c3a7826e8aa9d8c019874db4696de492a28e +size 57180 diff --git a/raw/rel-18/23_series/23282/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/23_series/23282/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7e4b7ad4fa63010ec30bcb8da210b829ef987f8 --- /dev/null +++ b/raw/rel-18/23_series/23282/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e89eaaffd8084b654bb90701dce118813c8d0706cc6c91f823bf15f6054d7c7f +size 30132 diff --git a/raw/rel-18/23_series/23282/a3472689858b068ef469213682965325_img.jpg b/raw/rel-18/23_series/23282/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aa9839fb664fe2bf7339425156e54aaf03efff3 --- /dev/null +++ b/raw/rel-18/23_series/23282/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912e4d6e05f74dda0adaf5a1878604568ddfd21e9fe3329216bc49b8d62c9fb1 +size 20820 diff --git a/raw/rel-18/23_series/23282/a51105b2031bad93b818b82f071c6add_img.jpg b/raw/rel-18/23_series/23282/a51105b2031bad93b818b82f071c6add_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..379ef8b3c3f6f032b307cd8b64d564fc84180e2d --- /dev/null +++ b/raw/rel-18/23_series/23282/a51105b2031bad93b818b82f071c6add_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ff60491e2906c502fef2aa4009494a7c1fa4a45c414da764dcb5bd6dbc0e91b +size 27074 diff --git a/raw/rel-18/23_series/23282/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/raw/rel-18/23_series/23282/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82ac1dde7988673ad3494989dd797be250d03c1a --- /dev/null +++ b/raw/rel-18/23_series/23282/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8098c4ae12b3261c710d0524ff9bfb2aabce318b67e94482e121a0a338fe0de +size 45759 diff --git a/raw/rel-18/23_series/23282/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/raw/rel-18/23_series/23282/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c80dfe2c69db73f4918ec3f53170ddae608e23a --- /dev/null +++ b/raw/rel-18/23_series/23282/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d44f749259e112407c434a090e7b32339e8ecd94d915764a233e84a907ff6358 +size 38322 diff --git a/raw/rel-18/23_series/23282/aec7150315249ac202a63cc0e32323b8_img.jpg b/raw/rel-18/23_series/23282/aec7150315249ac202a63cc0e32323b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92ea1d80d00d843ef560530a270d92f6df63f09a --- /dev/null +++ b/raw/rel-18/23_series/23282/aec7150315249ac202a63cc0e32323b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a6c3775ee6017f681251953fd9891a7c5b64a28ad56a6f968777e6cdabb513f +size 47245 diff --git a/raw/rel-18/23_series/23282/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/raw/rel-18/23_series/23282/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce84f18db0d5c616674cfda80437735140a2ba43 --- /dev/null +++ b/raw/rel-18/23_series/23282/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9297fa37602d8c11cf227371e6d3a618ee80bc80ba0438835338ab5cf56e469c +size 71808 diff --git a/raw/rel-18/23_series/23282/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/raw/rel-18/23_series/23282/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a92caaf34debcb1dd80b404a769923d1f8e44bab --- /dev/null +++ b/raw/rel-18/23_series/23282/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0839d6ac2b10f2eba3c555104a62c5cc8c4fd329f49cf02bbd34fb79ea6abc87 +size 57165 diff --git a/raw/rel-18/23_series/23282/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg b/raw/rel-18/23_series/23282/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..933259869a34eaf7b80b7df3b67afbbdddddf47b --- /dev/null +++ b/raw/rel-18/23_series/23282/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b5462c51d2ddf372ba0b6aae48c578b67e4082e9ab5ff13d94a0b3b625f2464 +size 97531 diff --git a/raw/rel-18/23_series/23282/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/raw/rel-18/23_series/23282/bffdddb47fced140f8d17fdc2a29f592_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8305ec6133f60ebf12087dc58706908e615003a4 --- /dev/null +++ b/raw/rel-18/23_series/23282/bffdddb47fced140f8d17fdc2a29f592_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0aa6576a2886ec2fb78c9871dcd69f5238392ab03bc636ed57ae1f51953812cd +size 90995 diff --git a/raw/rel-18/23_series/23282/d0abac95583b52a3b35f74a215567334_img.jpg b/raw/rel-18/23_series/23282/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dc44b18fab0e3c4f58579233eabffcc67d310a3 --- /dev/null +++ b/raw/rel-18/23_series/23282/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eabb1da558000ab1d11eb580155a65e644d84aa62ac948655628c8cae1d7ba5 +size 30429 diff --git a/raw/rel-18/23_series/23282/d26959f4514c26ca19c3d6f00da85956_img.jpg b/raw/rel-18/23_series/23282/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28ad1b83ab9210d71385c4c6c7a3b0f5bed7b64f --- /dev/null +++ b/raw/rel-18/23_series/23282/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9719237f628e4f34c02e856580988551430d8bc88aa49fa936ee24692b6f499 +size 77232 diff --git a/raw/rel-18/23_series/23282/d3ca266c298aeb34b019960c6c36f187_img.jpg b/raw/rel-18/23_series/23282/d3ca266c298aeb34b019960c6c36f187_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e64e4cc4e7c7fba9985ee64efd934ae7818e81b2 --- /dev/null +++ b/raw/rel-18/23_series/23282/d3ca266c298aeb34b019960c6c36f187_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d200c8da8d2ff21987035302b9f073d22b99cba863a03aebb9a678dbd2a0d570 +size 87900 diff --git a/raw/rel-18/23_series/23282/d980a3f9608055996a07f31788baf827_img.jpg b/raw/rel-18/23_series/23282/d980a3f9608055996a07f31788baf827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..489798c89edc26856b610f8bce97e80736df0cec --- /dev/null +++ b/raw/rel-18/23_series/23282/d980a3f9608055996a07f31788baf827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3145eb32d4ee207360bb4001a58ebb4e627b4f2dd1bf34fee1e1ed9cc525ab87 +size 53251 diff --git a/raw/rel-18/23_series/23282/dd5771673aececa53d42ece89218299d_img.jpg b/raw/rel-18/23_series/23282/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6625ae94aea68cd91bef96944c7ecefc03632303 --- /dev/null +++ b/raw/rel-18/23_series/23282/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8829d730f3cdde88dee8de684449f0a45dd83efebe286c260e897ebb0fe49d4d +size 41404 diff --git a/raw/rel-18/23_series/23282/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/raw/rel-18/23_series/23282/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28657c1228d44014ad9aafa77aa5f85611de76c7 --- /dev/null +++ b/raw/rel-18/23_series/23282/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ad8a2d8e377e9f931f99367a24f45c08e86c49fb7a92d5779d5a30e8759e78b +size 60554 diff --git a/raw/rel-18/23_series/23282/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/raw/rel-18/23_series/23282/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97208180ceef26449869e2253cd3d1dc7fd013a8 --- /dev/null +++ b/raw/rel-18/23_series/23282/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d671c117d596b9fb14089c3b925dc344d00484dacfe1aed293195a7b77eed725 +size 31219 diff --git a/raw/rel-18/23_series/23282/e636d7ccca0ad14c6b95201404324823_img.jpg b/raw/rel-18/23_series/23282/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2086ae3b511b474ade674007e6fc0c78eccaedac --- /dev/null +++ b/raw/rel-18/23_series/23282/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c2d0bc1be5af1ccf4b5ccbafea85034ac7d481e8238de664df207a63daa976f +size 66129 diff --git a/raw/rel-18/23_series/23282/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/23_series/23282/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f30f60ade0a0e7f764bb21d5498594bb4295c3c --- /dev/null +++ b/raw/rel-18/23_series/23282/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a6a08b57a50413930dea16d6d98ebf95e3d7c44dacce1590d00a9e5ded31902 +size 106200 diff --git a/raw/rel-18/23_series/23282/e787e02d9214556476d95941bda1d350_img.jpg b/raw/rel-18/23_series/23282/e787e02d9214556476d95941bda1d350_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9faa4369b90499f760121d8b62b6585a767ee76d --- /dev/null +++ b/raw/rel-18/23_series/23282/e787e02d9214556476d95941bda1d350_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:198186077fcc177cbf960332b7658e10d8963483798ee4f65c117729c6703aa4 +size 52163 diff --git a/raw/rel-18/23_series/23282/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/raw/rel-18/23_series/23282/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57898b0968a692f835c52c82fbf13bb65002eb6c --- /dev/null +++ b/raw/rel-18/23_series/23282/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:104449ea1cf8323da4126c5be985d5b2e43d31fe7d6db5aabf9713f852f94e2b +size 35860 diff --git a/raw/rel-18/23_series/23282/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/raw/rel-18/23_series/23282/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..500f9137a4885efb5297027ca13dab615ad77cfa --- /dev/null +++ b/raw/rel-18/23_series/23282/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7a08d978da5be62b9d7e9ae5a3e2bc8bfd2e6e4c2f9f1637caadac6fc0bae7e +size 36431 diff --git a/raw/rel-18/23_series/23282/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/23_series/23282/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfe19128c93873100ec26026dee80bb3c211ce63 --- /dev/null +++ b/raw/rel-18/23_series/23282/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88b59c4a75f4f216e0ef03ecfdb10f531b4be0c718dcb1df827270c70a7183ae +size 34812 diff --git a/raw/rel-18/23_series/23282/f20786b603b41e24b5d5899f710b5947_img.jpg b/raw/rel-18/23_series/23282/f20786b603b41e24b5d5899f710b5947_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5ecb28903832df7262295db9df568e62a3241f7 --- /dev/null +++ b/raw/rel-18/23_series/23282/f20786b603b41e24b5d5899f710b5947_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5d3698802a10231994c59ff166929dea286eb80ec9eb7f689a8805940415700 +size 57119 diff --git a/raw/rel-18/23_series/23282/f6d72d7c790e7f585532140f3971639a_img.jpg b/raw/rel-18/23_series/23282/f6d72d7c790e7f585532140f3971639a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..764fc175aee47a6e35b3dcbee431c8a3d03a7437 --- /dev/null +++ b/raw/rel-18/23_series/23282/f6d72d7c790e7f585532140f3971639a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:365f80d66a29a4942f0327b7642a7ca42ab844af9bb73b4f80a34108075435c9 +size 118499 diff --git a/raw/rel-18/23_series/23282/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/23_series/23282/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f7c373aaf428772e83519e7d84930637b34be68 --- /dev/null +++ b/raw/rel-18/23_series/23282/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6215601b209f8ec421c6d9af14435846d4516dac28747c0fabceaeaa54b1b70b +size 29122 diff --git a/raw/rel-18/23_series/23283/01832e59ebad7ada5e790de6f90cc9b6_img.jpg b/raw/rel-18/23_series/23283/01832e59ebad7ada5e790de6f90cc9b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b7c225c464cacf204138b2bfe462ebc31d132d --- /dev/null +++ b/raw/rel-18/23_series/23283/01832e59ebad7ada5e790de6f90cc9b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af6079cdd7b9cb59aad155571a08d60377499e44e6122dccf01e1c446467967b +size 63358 diff --git a/raw/rel-18/23_series/23283/01e00200a536673d6cd0e6d8705047a0_img.jpg b/raw/rel-18/23_series/23283/01e00200a536673d6cd0e6d8705047a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6018c79ec88438f1ea329bb2648e6285731bdbd --- /dev/null +++ b/raw/rel-18/23_series/23283/01e00200a536673d6cd0e6d8705047a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b2ac96bd6e42ec3d43f50fb6b74469787dc91eab4289bf8f699ec0a22bd13d4 +size 48750 diff --git a/raw/rel-18/23_series/23283/04f1a971a602ced3c6096d46de1cf29c_img.jpg b/raw/rel-18/23_series/23283/04f1a971a602ced3c6096d46de1cf29c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba1e2781b58e1e83e5d355652cc665270379e159 --- /dev/null +++ b/raw/rel-18/23_series/23283/04f1a971a602ced3c6096d46de1cf29c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c00dbd6ea5843f8a06f9e508611c16a7d70707898b2fba478436acc9dd48ed1b +size 42227 diff --git a/raw/rel-18/23_series/23283/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/raw/rel-18/23_series/23283/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c00fa36fd31e1ad74591992cd5cee214f6d99b04 --- /dev/null +++ b/raw/rel-18/23_series/23283/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6567846ed03394c352c8eac666b340abfa5b6f46db9a0284f58957b4061dbf2 +size 17173 diff --git a/raw/rel-18/23_series/23283/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/raw/rel-18/23_series/23283/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b326451600997fd5e8b76c34a509162e8b4b2eec --- /dev/null +++ b/raw/rel-18/23_series/23283/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf6efe06afb7c39f1a3f50aaa90e945a8b5bd9167435183b970da98e5256229e +size 52735 diff --git a/raw/rel-18/23_series/23283/107c8e1abcb7033ad244e30e7a910045_img.jpg b/raw/rel-18/23_series/23283/107c8e1abcb7033ad244e30e7a910045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11f1e2dfc23d806c457e10791c127e13c17c2262 --- /dev/null +++ b/raw/rel-18/23_series/23283/107c8e1abcb7033ad244e30e7a910045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5317e2741c032dc9f7840d1ebb1bb14e2d5efc2a3300407a68b87f97bf988322 +size 28318 diff --git a/raw/rel-18/23_series/23283/10f4e3a2f3c016555ee12a5b556ba834_img.jpg b/raw/rel-18/23_series/23283/10f4e3a2f3c016555ee12a5b556ba834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a199c95d14d7ad2fdbd9756f9990cdb3bbecfba3 --- /dev/null +++ b/raw/rel-18/23_series/23283/10f4e3a2f3c016555ee12a5b556ba834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e44fc312486d8243b3791ea9e7829e314894e3bd772d40251bef10d1047225fb +size 76167 diff --git a/raw/rel-18/23_series/23283/114a0aef3954cf8b22aa8e081fe1061d_img.jpg b/raw/rel-18/23_series/23283/114a0aef3954cf8b22aa8e081fe1061d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c022bd2cb1d678cbec8baf2172a19345a09f7144 --- /dev/null +++ b/raw/rel-18/23_series/23283/114a0aef3954cf8b22aa8e081fe1061d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3b617c190e4abc4619ca5e353e2ed154a37823216a6a0085800de656a774c00 +size 42365 diff --git a/raw/rel-18/23_series/23283/19a8fc45b10957bab04a686521657f46_img.jpg b/raw/rel-18/23_series/23283/19a8fc45b10957bab04a686521657f46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..853d2b32d09a960a83e1bf7013893edba543d9c9 --- /dev/null +++ b/raw/rel-18/23_series/23283/19a8fc45b10957bab04a686521657f46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14ebc71da82f04e2692150b885e09eca1e34997505e21885cf38cff31475d348 +size 42281 diff --git a/raw/rel-18/23_series/23283/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/raw/rel-18/23_series/23283/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10ca0caec3769cf3de8b66b22fa715790de947aa --- /dev/null +++ b/raw/rel-18/23_series/23283/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b38a9d76c4972c985724e24ff6edb775ed51485927ad8ec7192add84149344a +size 34135 diff --git a/raw/rel-18/23_series/23283/245166735676c675f98f535bc4c6f0a1_img.jpg b/raw/rel-18/23_series/23283/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36a6c4338ae717b6de0eb2020b5910b97e036ea3 --- /dev/null +++ b/raw/rel-18/23_series/23283/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f745501472c7909ff681e3683f8402416ea0274df38b1dc1f41e1689b59a79e +size 59363 diff --git a/raw/rel-18/23_series/23283/24c9e038a791677ed33100667b64f7e6_img.jpg b/raw/rel-18/23_series/23283/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d2ec18666690a1ffc2801264170ef935ecfcfb4 --- /dev/null +++ b/raw/rel-18/23_series/23283/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87384ea21d23d5ee87f2d1d26c04b917f450f11518e5769a5541db6b5b13785c +size 18597 diff --git a/raw/rel-18/23_series/23283/24ca460ee3381aee781887e9e586ec67_img.jpg b/raw/rel-18/23_series/23283/24ca460ee3381aee781887e9e586ec67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8253115cde11a2e9e939e2d605cabde6502a6f76 --- /dev/null +++ b/raw/rel-18/23_series/23283/24ca460ee3381aee781887e9e586ec67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59cdfc7f013d68e742b07040e94b420a2c8f4b36044e1efeddb74411f8989d89 +size 40997 diff --git a/raw/rel-18/23_series/23283/255efa1d461fc79b4ed367aaec11637f_img.jpg b/raw/rel-18/23_series/23283/255efa1d461fc79b4ed367aaec11637f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30f2afb39b93b62625a4df61dc8ce2906c0c0733 --- /dev/null +++ b/raw/rel-18/23_series/23283/255efa1d461fc79b4ed367aaec11637f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d78d711109c9f24005d4e7cb014d346febce67d4f5dac3d2bc1ff73b8401d9e7 +size 112858 diff --git a/raw/rel-18/23_series/23283/29997432244f81212ee1e6c94f308f1b_img.jpg b/raw/rel-18/23_series/23283/29997432244f81212ee1e6c94f308f1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a656a2ee788094c75bf88ecd49ebc3bb192c3833 --- /dev/null +++ b/raw/rel-18/23_series/23283/29997432244f81212ee1e6c94f308f1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51d4a0d13b77620c7af3efe2e11cb11420a0df81d2321cae0b59379cb6e9a237 +size 56931 diff --git a/raw/rel-18/23_series/23283/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/raw/rel-18/23_series/23283/2b3a967f6ce4f23649be995a353e39f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b335c1ffbdd9514528db382a238ede9cc04c502d --- /dev/null +++ b/raw/rel-18/23_series/23283/2b3a967f6ce4f23649be995a353e39f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebc11bba11f8a3e21eba96f80b72ce24c6069c42461f91088ebe0f4289f4dd87 +size 42436 diff --git a/raw/rel-18/23_series/23283/2b60ebe01f77d22e53da1fbe73083b01_img.jpg b/raw/rel-18/23_series/23283/2b60ebe01f77d22e53da1fbe73083b01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2cacf5e4db0c01f799cd636111e3965ea859c2f --- /dev/null +++ b/raw/rel-18/23_series/23283/2b60ebe01f77d22e53da1fbe73083b01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cc937d53356013132a867d5cbc9940f656c2f1b9b6933522380a68608f58a22 +size 75098 diff --git a/raw/rel-18/23_series/23283/30387053b5b3fede6873f6a46a9ca4a9_img.jpg b/raw/rel-18/23_series/23283/30387053b5b3fede6873f6a46a9ca4a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d37780e5f05bc01b1fe7db945a6ecb9e8658043 --- /dev/null +++ b/raw/rel-18/23_series/23283/30387053b5b3fede6873f6a46a9ca4a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:387560a3a8f486cbc971411b4de7cd2492928d330544203ad94c618c5f760dc1 +size 47853 diff --git a/raw/rel-18/23_series/23283/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/raw/rel-18/23_series/23283/318886a86a1dcc59e1fc83db6f157c60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91cb257cc21983b5610752da330b54de26a39258 --- /dev/null +++ b/raw/rel-18/23_series/23283/318886a86a1dcc59e1fc83db6f157c60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a1c7c4e366f8abb9cc34a06978c621ae5c5236627694db42cab42d76b496b2f +size 16997 diff --git a/raw/rel-18/23_series/23283/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/raw/rel-18/23_series/23283/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6052d2821b3b0a8bfe3d52904b2a971eef210eac --- /dev/null +++ b/raw/rel-18/23_series/23283/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92112d03c34a26c8b4cc8afb44450cc39a2c18da55c7461e966c7aee0a657129 +size 39124 diff --git a/raw/rel-18/23_series/23283/3220d3a933797114c1ba20d5c4ec093d_img.jpg b/raw/rel-18/23_series/23283/3220d3a933797114c1ba20d5c4ec093d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ba21b4aeeb2147ff74ac32822c305d3d243c32e --- /dev/null +++ b/raw/rel-18/23_series/23283/3220d3a933797114c1ba20d5c4ec093d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6dab518e24403a794f3256d735cde1d8cca8e32fd3da57e59d41bc5fc2f3e6d +size 22783 diff --git a/raw/rel-18/23_series/23283/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/raw/rel-18/23_series/23283/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7a5fc9f0ec23e4a4e86205dae97ad78e191ed84 --- /dev/null +++ b/raw/rel-18/23_series/23283/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eeb5363fb49e31b67fce284b3f25fced730d65633eda1e40db914359de688899 +size 40673 diff --git a/raw/rel-18/23_series/23283/365ac42391d8f7b1dac76b967a948788_img.jpg b/raw/rel-18/23_series/23283/365ac42391d8f7b1dac76b967a948788_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..821022c0e1ef8afca02558b95d207933aef43d07 --- /dev/null +++ b/raw/rel-18/23_series/23283/365ac42391d8f7b1dac76b967a948788_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8282beaaaf075b740e093070411b1db0dbf1073ec1fc86d7d4c84ee8dba8af0f +size 45461 diff --git a/raw/rel-18/23_series/23283/36e11608a186ec372afec7470985ff56_img.jpg b/raw/rel-18/23_series/23283/36e11608a186ec372afec7470985ff56_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2956381bdb37ce3a0e4399fa4d9f92bd7bdc4faa --- /dev/null +++ b/raw/rel-18/23_series/23283/36e11608a186ec372afec7470985ff56_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3d819ec0706c9e440e2e46aeeef600f4bf4f24521953fa979122452102b3d28 +size 52264 diff --git a/raw/rel-18/23_series/23283/387a316ca4f909a5260b0c5e232d5cc8_img.jpg b/raw/rel-18/23_series/23283/387a316ca4f909a5260b0c5e232d5cc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c3aca11b1ede402f1ecddd3749fb508700fe3af --- /dev/null +++ b/raw/rel-18/23_series/23283/387a316ca4f909a5260b0c5e232d5cc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e64510da42d0dfdec88bd8224fcd90eb3bbdfb50b52f9ef1c0e58203586b66a5 +size 68777 diff --git a/raw/rel-18/23_series/23283/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg b/raw/rel-18/23_series/23283/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cec875ea92ddf0c97ae59d21d12e3b328c4b0086 --- /dev/null +++ b/raw/rel-18/23_series/23283/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcf7fb7f07560581887f04e075f7dbf4765849d22d76c2e7e5d2af8e0b9d196b +size 39080 diff --git a/raw/rel-18/23_series/23283/41aef1f5efab13d4f38f69e86c726062_img.jpg b/raw/rel-18/23_series/23283/41aef1f5efab13d4f38f69e86c726062_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..401bc07736fb8fd880224c08c24ab9ebe6a19fc7 --- /dev/null +++ b/raw/rel-18/23_series/23283/41aef1f5efab13d4f38f69e86c726062_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2196525d59ab819dcbe9b9a230a861df17b365cd0113bfee1f6b35769af71c60 +size 70740 diff --git a/raw/rel-18/23_series/23283/433e43d1c6dedf2fb2bc15a34b656b79_img.jpg b/raw/rel-18/23_series/23283/433e43d1c6dedf2fb2bc15a34b656b79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c93a0c7fa63da6f81e14683673185fe75612231f --- /dev/null +++ b/raw/rel-18/23_series/23283/433e43d1c6dedf2fb2bc15a34b656b79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd919c11a1cac29f062aa12ef99616b26f6d4f171b7a347b23c85169c44d92a4 +size 24235 diff --git a/raw/rel-18/23_series/23283/4430c1d8e78ac97fda782321410349a9_img.jpg b/raw/rel-18/23_series/23283/4430c1d8e78ac97fda782321410349a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6acbd2528bfdb64ecd6699b562a604d12f08f8d6 --- /dev/null +++ b/raw/rel-18/23_series/23283/4430c1d8e78ac97fda782321410349a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84648d7a003ad47829a4d9a653ea0d0db5dc7824a2b9f394c547c7ae25704a2d +size 36897 diff --git a/raw/rel-18/23_series/23283/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/raw/rel-18/23_series/23283/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7026456f01756b66fa5c135c16fe9d673be2d3fa --- /dev/null +++ b/raw/rel-18/23_series/23283/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08c79c865f9062309cf1d2d80235de1ffb62ef501034016481d254314bf95e04 +size 55037 diff --git a/raw/rel-18/23_series/23283/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/raw/rel-18/23_series/23283/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c1c2cad46a706c9a17fd1d8ebb999d671f07957 --- /dev/null +++ b/raw/rel-18/23_series/23283/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3821c37d1dce606bae41e805cfc9d6eaddf89643fd02dc6fa5e1d94287792c5 +size 68796 diff --git a/raw/rel-18/23_series/23283/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg b/raw/rel-18/23_series/23283/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52f7667e5b5f91aa4eb4c6d994bed644738eec5d --- /dev/null +++ b/raw/rel-18/23_series/23283/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:774ed4f79ac0fe4f350cdd125a65ea87e9da42ada4f853c220c6547926443c37 +size 62343 diff --git a/raw/rel-18/23_series/23283/4c63a0e17b54c7e61d512c276932114c_img.jpg b/raw/rel-18/23_series/23283/4c63a0e17b54c7e61d512c276932114c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15b3ca6bbf7a86419120c14ad1e479cbbc582253 --- /dev/null +++ b/raw/rel-18/23_series/23283/4c63a0e17b54c7e61d512c276932114c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b67f6c2a16c196eb351e68781ca5e5cd86fb82f92f7d825654cd132960ea1c56 +size 76281 diff --git a/raw/rel-18/23_series/23283/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/raw/rel-18/23_series/23283/52c40e2f443985dc63f45dec57d90c8c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29958a42fbe0214be480e7cd577540a31ea03452 --- /dev/null +++ b/raw/rel-18/23_series/23283/52c40e2f443985dc63f45dec57d90c8c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6127248a0b736a4b2f1c034e12a3b1a522eb5a7281cc7c7d5a58465e31b445cb +size 39884 diff --git a/raw/rel-18/23_series/23283/53499879d98034410ecba2c386c58f0c_img.jpg b/raw/rel-18/23_series/23283/53499879d98034410ecba2c386c58f0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d10e305221b4b04c9a5febe83083f82d1394222c --- /dev/null +++ b/raw/rel-18/23_series/23283/53499879d98034410ecba2c386c58f0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80c4c8635193e7bf19a5560f08fd0f9be2aba63facdb908cd1f15002844c9f4d +size 56712 diff --git a/raw/rel-18/23_series/23283/5445597cceefaca1ac89e710fe339325_img.jpg b/raw/rel-18/23_series/23283/5445597cceefaca1ac89e710fe339325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cb04cff4622c18787636d35499bb07252fd59a0 --- /dev/null +++ b/raw/rel-18/23_series/23283/5445597cceefaca1ac89e710fe339325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67d8999e5e5206c651e774c01ea24bd5acb5b7edab975f0335abb286d8188f95 +size 28509 diff --git a/raw/rel-18/23_series/23283/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg b/raw/rel-18/23_series/23283/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..411da3ad991e6279d6500bdcf86c5000aef89366 --- /dev/null +++ b/raw/rel-18/23_series/23283/55f11fbbe5ef616ee7a1814f932acbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fea49443a54fbfc3d97ca89d817161a6baabd773f44d5ca718b100ede69ccc35 +size 39842 diff --git a/raw/rel-18/23_series/23283/5661815043254c37a4e3e4833f51e727_img.jpg b/raw/rel-18/23_series/23283/5661815043254c37a4e3e4833f51e727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c593ceb60ddc48c137325131c12b6aa28b9b7cf7 --- /dev/null +++ b/raw/rel-18/23_series/23283/5661815043254c37a4e3e4833f51e727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9807139ff40542080f328c702f13bf1c1b33f605bdee098b077cf83a8d5e3690 +size 61730 diff --git a/raw/rel-18/23_series/23283/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23283/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f2434f204301bdddd0d7051570639fd9c53ac6d --- /dev/null +++ b/raw/rel-18/23_series/23283/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:238a4f1407b2e241873ee2724279180dfe051fb2635294aa2eb7d53a70a711a7 +size 9478 diff --git a/raw/rel-18/23_series/23283/633486b12958f97e062b5cf9e0801e99_img.jpg b/raw/rel-18/23_series/23283/633486b12958f97e062b5cf9e0801e99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb8da20197b36677974ffd538cbe1e2cb44f82df --- /dev/null +++ b/raw/rel-18/23_series/23283/633486b12958f97e062b5cf9e0801e99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:609158aea42d06abb9fa240f2d382226da4c18024e40a6b78090dd39469a8045 +size 80066 diff --git a/raw/rel-18/23_series/23283/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23283/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50cfebe2ee367cdda900184f11dddbe8d42f9b10 --- /dev/null +++ b/raw/rel-18/23_series/23283/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c05aaecc78d8512dedab3079355b3a1c3241889147365272bb0d18898470fc0 +size 5671 diff --git a/raw/rel-18/23_series/23283/66b2567aa84dd1d036931b056352e11e_img.jpg b/raw/rel-18/23_series/23283/66b2567aa84dd1d036931b056352e11e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25a32bd4ec7d25cb52d9720b66024fe76a479064 --- /dev/null +++ b/raw/rel-18/23_series/23283/66b2567aa84dd1d036931b056352e11e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da320086be8c4f504c9b52629bbe0e5690f7717fa44f6f137189316afbff14ca +size 42232 diff --git a/raw/rel-18/23_series/23283/66e89867f97592fd4bfab0e4f2b2054f_img.jpg b/raw/rel-18/23_series/23283/66e89867f97592fd4bfab0e4f2b2054f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..535b9209d699f23feaf966ea2c1eaf5ab0b1d535 --- /dev/null +++ b/raw/rel-18/23_series/23283/66e89867f97592fd4bfab0e4f2b2054f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27b6e3b53ee512351078347aec1deaba57bae3061cec82b041a0c7e26e3d81c2 +size 36593 diff --git a/raw/rel-18/23_series/23283/67725cb5fabfd68d3a6e8c12589d4c06_img.jpg b/raw/rel-18/23_series/23283/67725cb5fabfd68d3a6e8c12589d4c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7e2a8a84e2489bbc727cf74c4638cd17a483ec4 --- /dev/null +++ b/raw/rel-18/23_series/23283/67725cb5fabfd68d3a6e8c12589d4c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:340a467db792c09aae145e522050c4e6fb1eacb475d35ef6fae4b3aa1ea0bb11 +size 50345 diff --git a/raw/rel-18/23_series/23283/6a2b92323d788c2e7e9e570025885181_img.jpg b/raw/rel-18/23_series/23283/6a2b92323d788c2e7e9e570025885181_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5142f9746eddbf7aba822c5176ae217a20211e2a --- /dev/null +++ b/raw/rel-18/23_series/23283/6a2b92323d788c2e7e9e570025885181_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d81c9ea441beb4bd2a2fd228c38e9ff69f2a6e1202d221e3549832918f8d596 +size 41267 diff --git a/raw/rel-18/23_series/23283/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/raw/rel-18/23_series/23283/789ee0a267b24f34bd1f45313e86c9a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a926008c2fea8aee045f7121d62bf9d966761948 --- /dev/null +++ b/raw/rel-18/23_series/23283/789ee0a267b24f34bd1f45313e86c9a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5792b7e3d4b5d890e83fc738e84b5815a95e8e4d7eab9cce7d9a57d5c8f4d223 +size 66790 diff --git a/raw/rel-18/23_series/23283/78de09c382ab51b5c3e87979204228c8_img.jpg b/raw/rel-18/23_series/23283/78de09c382ab51b5c3e87979204228c8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..894666dce300c908dc1c075ac9766c38a1b5bb74 --- /dev/null +++ b/raw/rel-18/23_series/23283/78de09c382ab51b5c3e87979204228c8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ae92593a4750270744d2d04f26027c1acd358ec923235575c63057734e0b004 +size 44162 diff --git a/raw/rel-18/23_series/23283/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/raw/rel-18/23_series/23283/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27c7b91623040613d82c80f3dd31a4000854d125 --- /dev/null +++ b/raw/rel-18/23_series/23283/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:526b3fa2e678f8b9064571836adbcd8a7b94444fe319878a71b3aa7294152991 +size 52958 diff --git a/raw/rel-18/23_series/23283/7bfe80acfdafd78f610d8b66e3cc6161_img.jpg b/raw/rel-18/23_series/23283/7bfe80acfdafd78f610d8b66e3cc6161_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ac601fc618d373ef69ed776e98be57117520939 --- /dev/null +++ b/raw/rel-18/23_series/23283/7bfe80acfdafd78f610d8b66e3cc6161_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a04a7e83731e893519f029329590db854ac46bd986ef839918f6d88e948f3a +size 41209 diff --git a/raw/rel-18/23_series/23283/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/raw/rel-18/23_series/23283/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..559a2fe4fd25d06c0b48a8dd0fffdd71512f9c1e --- /dev/null +++ b/raw/rel-18/23_series/23283/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cdf111abe74a11052081770897b0c4222295eebea1ee8af5817cad7e1e43681 +size 49947 diff --git a/raw/rel-18/23_series/23283/802707b774f2d2973b49cea2020e8453_img.jpg b/raw/rel-18/23_series/23283/802707b774f2d2973b49cea2020e8453_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff5e7c20b29a024dc3972bd2927e548876f8bbe5 --- /dev/null +++ b/raw/rel-18/23_series/23283/802707b774f2d2973b49cea2020e8453_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6167a6a0c9c9e558ff8b9c910600103acdf413504ba5decc51cfc9ad01ecb87 +size 72909 diff --git a/raw/rel-18/23_series/23283/813ef40a14c7e2a52988a63e33c2b59f_img.jpg b/raw/rel-18/23_series/23283/813ef40a14c7e2a52988a63e33c2b59f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bf56c936ad2d45408ad4b17c0d83b44e0af1ff8 --- /dev/null +++ b/raw/rel-18/23_series/23283/813ef40a14c7e2a52988a63e33c2b59f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:429d3349f686526e29c81c2d4632ecffa56859a37fa8d6b2293091003f04816b +size 22824 diff --git a/raw/rel-18/23_series/23283/81a0abf9a79b27cf9d765553216b173c_img.jpg b/raw/rel-18/23_series/23283/81a0abf9a79b27cf9d765553216b173c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2bc9fce3291fe0c9f13096432c0837f54645e9c --- /dev/null +++ b/raw/rel-18/23_series/23283/81a0abf9a79b27cf9d765553216b173c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbc46a7aa5d8aaf57dca1110bbd9aa862ac2c08800231d7635d350c816784697 +size 59309 diff --git a/raw/rel-18/23_series/23283/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/raw/rel-18/23_series/23283/834fb96b114b8fdc001625e1ae28e8b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4f58a09300fcfa2a115050b042b45944064bbd1 --- /dev/null +++ b/raw/rel-18/23_series/23283/834fb96b114b8fdc001625e1ae28e8b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac04db40b998a416b32c92139050d01e58f02dce655c5670727c303dc9092ab3 +size 46578 diff --git a/raw/rel-18/23_series/23283/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg b/raw/rel-18/23_series/23283/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1239f1205407808136296e098c7cf17a88baa42 --- /dev/null +++ b/raw/rel-18/23_series/23283/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:717239759630a09394300f499a97751c72727f9ef3f77e97756ddd00d3d30868 +size 33342 diff --git a/raw/rel-18/23_series/23283/912a57b374babddd0201eecb2e9e1e4b_img.jpg b/raw/rel-18/23_series/23283/912a57b374babddd0201eecb2e9e1e4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f348f0aaa5b9c9b30b3cf05f952384aecbec5d3 --- /dev/null +++ b/raw/rel-18/23_series/23283/912a57b374babddd0201eecb2e9e1e4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:399046efecf530b47ae4afe489df4b4e090ef20c0a2fcaed75f58a7ea9db8022 +size 50286 diff --git a/raw/rel-18/23_series/23283/92c9263daf7fbd044894e2b273ae21af_img.jpg b/raw/rel-18/23_series/23283/92c9263daf7fbd044894e2b273ae21af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bb92ac77fa63803103947ef8c5feec80d67aeba --- /dev/null +++ b/raw/rel-18/23_series/23283/92c9263daf7fbd044894e2b273ae21af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b7e2c78dce6af9a37ef36e81978dd2f21f7ca6e4726e3bdaafe6d5593e3a8fe +size 39651 diff --git a/raw/rel-18/23_series/23283/935075de5250cfe8aa0fb9d65d63dde5_img.jpg b/raw/rel-18/23_series/23283/935075de5250cfe8aa0fb9d65d63dde5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df514d99def28815b8bd014ed40ca454fbb0ff37 --- /dev/null +++ b/raw/rel-18/23_series/23283/935075de5250cfe8aa0fb9d65d63dde5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b195d617f0ea32ebec28e403d083c8264be5f018410376b39cf1a062b7ed1a0f +size 56166 diff --git a/raw/rel-18/23_series/23283/93699fb71e95b4df5a3871fdcf818982_img.jpg b/raw/rel-18/23_series/23283/93699fb71e95b4df5a3871fdcf818982_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbe21701e599d66bac7024cb2660543aa18892ce --- /dev/null +++ b/raw/rel-18/23_series/23283/93699fb71e95b4df5a3871fdcf818982_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f919d71a07ca313fa0061827714cf99a90c5eb344046a3e7f147dac81b2f494a +size 71885 diff --git a/raw/rel-18/23_series/23283/936af4a8c1a8e4095b87b65c5b79137c_img.jpg b/raw/rel-18/23_series/23283/936af4a8c1a8e4095b87b65c5b79137c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7df9cc44a2d757e868e3c59c364b4db4f68a2c31 --- /dev/null +++ b/raw/rel-18/23_series/23283/936af4a8c1a8e4095b87b65c5b79137c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e62a97479b7261cf5c96982f69927d3ffb027236179d766dd4672a9369d89c2d +size 30143 diff --git a/raw/rel-18/23_series/23283/94fd137860c16c8dfd75512f10161fe8_img.jpg b/raw/rel-18/23_series/23283/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c857fff53bf37b3e02994b9aa127ad0fef65aba --- /dev/null +++ b/raw/rel-18/23_series/23283/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c3f3319074e8e9d0f6356738329c4761ff6b1a6c7cdb45f5051e54fb12210d0 +size 18164 diff --git a/raw/rel-18/23_series/23283/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg b/raw/rel-18/23_series/23283/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..547f0b9e6d3fde36090a1b2279a3d1ac72240a43 --- /dev/null +++ b/raw/rel-18/23_series/23283/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8965143b44ef4db1bd26a4e5154f274895246d49fce197ed41c3edb74f75c36c +size 40464 diff --git a/raw/rel-18/23_series/23283/9edb407536d4d4d4a6ac391527af047c_img.jpg b/raw/rel-18/23_series/23283/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73fdffcff0f37a7144c93c1edd9ef9d8aa5a436f --- /dev/null +++ b/raw/rel-18/23_series/23283/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d851288ecea0ac8852f5d4f522bf05b543190f32ad1d513e5ebc1dc8d0fde6f +size 46408 diff --git a/raw/rel-18/23_series/23283/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/raw/rel-18/23_series/23283/a149b400127a3e3e50b3c98d27c5935c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..078f3dc10c9b304fcba6b606eedb2628a5adbb1c --- /dev/null +++ b/raw/rel-18/23_series/23283/a149b400127a3e3e50b3c98d27c5935c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:619bfe01134e2122a85bc2db85ee689feae5fce42ff6a0cffef3527467bd282a +size 89521 diff --git a/raw/rel-18/23_series/23283/a5184899f915014fa38608754efcc9c7_img.jpg b/raw/rel-18/23_series/23283/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b71d89974389135640697ecde4deeda28990707 --- /dev/null +++ b/raw/rel-18/23_series/23283/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e651a3fbfa0c91e61102c9fac2bfbb759c64c2ca56edc631634f133d38df72c4 +size 55399 diff --git a/raw/rel-18/23_series/23283/a780a960b3f2de2493d5785bedae10ff_img.jpg b/raw/rel-18/23_series/23283/a780a960b3f2de2493d5785bedae10ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8abb86c447fafdc437d4ab3ee9577f693cbcf17 --- /dev/null +++ b/raw/rel-18/23_series/23283/a780a960b3f2de2493d5785bedae10ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4222fc63928e549b9bbe18d5126d53b364e178139c718e916352ca888736350 +size 109693 diff --git a/raw/rel-18/23_series/23283/a969a3a831d0967b54efe1400846ed30_img.jpg b/raw/rel-18/23_series/23283/a969a3a831d0967b54efe1400846ed30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbfc25d50c8b540913d76766b19c4ff98b22c707 --- /dev/null +++ b/raw/rel-18/23_series/23283/a969a3a831d0967b54efe1400846ed30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:214f8d90d3128d8e52a7927e0f674f2ca08ef856934dfacee94fc8098946bff7 +size 61547 diff --git a/raw/rel-18/23_series/23283/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg b/raw/rel-18/23_series/23283/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f32c8fdcac799e0ae404f89c383f807fa37bb3ce --- /dev/null +++ b/raw/rel-18/23_series/23283/afd9ce64c136f2090b978ea5f3ef9d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b858e99b47de459719bebca380f73f34105c2ff8d861a2c4e51d26755df30fcb +size 26662 diff --git a/raw/rel-18/23_series/23283/b0b9bc3067d012eb2fa3539217b9c34d_img.jpg b/raw/rel-18/23_series/23283/b0b9bc3067d012eb2fa3539217b9c34d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16feabe492a8317dec0b2472bb2dbcf7c1558c1b --- /dev/null +++ b/raw/rel-18/23_series/23283/b0b9bc3067d012eb2fa3539217b9c34d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3c0a9d27c655b8f65dc45929f8789964bdc09b4ddb74f3d3ad9fd4a4cecfd30 +size 65402 diff --git a/raw/rel-18/23_series/23283/b35ea3e304aad7d350a9902270413930_img.jpg b/raw/rel-18/23_series/23283/b35ea3e304aad7d350a9902270413930_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f5e79826d7da5e5ce4dcf4e09ab9f6454c2638e --- /dev/null +++ b/raw/rel-18/23_series/23283/b35ea3e304aad7d350a9902270413930_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc711ccea959e339e8c432648dffe99daac6398cb86c5a85d0fc97f6d9490093 +size 43607 diff --git a/raw/rel-18/23_series/23283/b3d488012fdceacab867cf24c5efef05_img.jpg b/raw/rel-18/23_series/23283/b3d488012fdceacab867cf24c5efef05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba7cea0b1418bafea20825dfc3a4fe367737d28b --- /dev/null +++ b/raw/rel-18/23_series/23283/b3d488012fdceacab867cf24c5efef05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f26823f58e39f1e0fa53f8a009016df97ec06fb2d23f3037dcf1192eedef5db +size 47039 diff --git a/raw/rel-18/23_series/23283/c020c072c67473d7823d1f9551942732_img.jpg b/raw/rel-18/23_series/23283/c020c072c67473d7823d1f9551942732_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0a2c75a1f30eccd01a5b98db43507f3612f6bcd --- /dev/null +++ b/raw/rel-18/23_series/23283/c020c072c67473d7823d1f9551942732_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a5df79d1211a64572ee33917daa6071f33a82534afd7b8a48d291d4c5fc24ef +size 32212 diff --git a/raw/rel-18/23_series/23283/c05763eff20551449de1eac378fed769_img.jpg b/raw/rel-18/23_series/23283/c05763eff20551449de1eac378fed769_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1dc15113731447f090e41070c990cccdfbca8b06 --- /dev/null +++ b/raw/rel-18/23_series/23283/c05763eff20551449de1eac378fed769_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86a80d0542471df80e87492eee1b812911c6a3cdf4cd4d47e253356344def204 +size 67332 diff --git a/raw/rel-18/23_series/23283/c06fd7dbef68a8b788158f2081d9d734_img.jpg b/raw/rel-18/23_series/23283/c06fd7dbef68a8b788158f2081d9d734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbb86c98d2d04f492093e8f815167ba19a634813 --- /dev/null +++ b/raw/rel-18/23_series/23283/c06fd7dbef68a8b788158f2081d9d734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52c7d393611ea1e0c07426335e6f3c222edd9b6bf037542042ed70962abd8133 +size 38330 diff --git a/raw/rel-18/23_series/23283/c24164782e328c82ba89b80c0ef8c3d7_img.jpg b/raw/rel-18/23_series/23283/c24164782e328c82ba89b80c0ef8c3d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..004af834dd7827b9335bee8751de39c00cca0a4c --- /dev/null +++ b/raw/rel-18/23_series/23283/c24164782e328c82ba89b80c0ef8c3d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce872bd3794fdf31d35fb66710774552f881288613f22730bd30bad9843a17d7 +size 43300 diff --git a/raw/rel-18/23_series/23283/c3254408eadbf152632a8faf16310722_img.jpg b/raw/rel-18/23_series/23283/c3254408eadbf152632a8faf16310722_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef80a157b750140c13a897199db07bd8374d60f0 --- /dev/null +++ b/raw/rel-18/23_series/23283/c3254408eadbf152632a8faf16310722_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0618db76918a0d82581fa32423e80e2d015b6fe157c7670ae627ad4288fffc2a +size 53416 diff --git a/raw/rel-18/23_series/23283/c355b8056bdd4728357d7d5ed18792ca_img.jpg b/raw/rel-18/23_series/23283/c355b8056bdd4728357d7d5ed18792ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6866d73cd420b6901171f45a2516daf3b6ae075e --- /dev/null +++ b/raw/rel-18/23_series/23283/c355b8056bdd4728357d7d5ed18792ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20fbd58465cf73a986ff721b72f23792f0dc91583a7fa43095ede49627da2186 +size 25275 diff --git a/raw/rel-18/23_series/23283/c3d58ba0812530ed8c8a9c9f68c209b1_img.jpg b/raw/rel-18/23_series/23283/c3d58ba0812530ed8c8a9c9f68c209b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d743e6f6026ce586304eb30356389f2f8b3f9b1 --- /dev/null +++ b/raw/rel-18/23_series/23283/c3d58ba0812530ed8c8a9c9f68c209b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03e13675d26b1f58054294ced5e8adbf58286e60e3fd3215f795efa5d0502d74 +size 47317 diff --git a/raw/rel-18/23_series/23283/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/raw/rel-18/23_series/23283/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ff0d68c7833e8de47c3befd1f8a7404c119d636 --- /dev/null +++ b/raw/rel-18/23_series/23283/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf8bd7c9d3baf59da4a5fb68057d6988c909cb256b5bfadc29679906c4993efa +size 38926 diff --git a/raw/rel-18/23_series/23283/c7e196e0c468cc7b9a84c12c951209a0_img.jpg b/raw/rel-18/23_series/23283/c7e196e0c468cc7b9a84c12c951209a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..264ee2b623f5ab8f79761989606ac7201454e52c --- /dev/null +++ b/raw/rel-18/23_series/23283/c7e196e0c468cc7b9a84c12c951209a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be8ecae4b26846a1ea1f36ebbde298b0a3ac804d2cec6fcb7da47be39f9edc2e +size 58360 diff --git a/raw/rel-18/23_series/23283/c96780e69fd790e1e62e1c3e5431636a_img.jpg b/raw/rel-18/23_series/23283/c96780e69fd790e1e62e1c3e5431636a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c971704b41f442c178dc1fe0ac7df0a111ba9f69 --- /dev/null +++ b/raw/rel-18/23_series/23283/c96780e69fd790e1e62e1c3e5431636a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5cc04a324689c375a0a89eaffc3f0d6ebc20c9a21c939f817891b2ca099f41d +size 47920 diff --git a/raw/rel-18/23_series/23283/c995e0bb4efc8c0f2994428aa1245709_img.jpg b/raw/rel-18/23_series/23283/c995e0bb4efc8c0f2994428aa1245709_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0e848855d7e140583bc3fb39816970d949c349a --- /dev/null +++ b/raw/rel-18/23_series/23283/c995e0bb4efc8c0f2994428aa1245709_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a742f64ebe04a96e0763a768e164b64cf631b0d3b447b4d270085ddc038407b +size 68224 diff --git a/raw/rel-18/23_series/23283/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg b/raw/rel-18/23_series/23283/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2060ebd9ace7909b992f0ed3e19d0c741e67123 --- /dev/null +++ b/raw/rel-18/23_series/23283/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:002027bd076c195612c5c6e3dc7aec9480c6bd792d96051142843bab77c3970d +size 32473 diff --git a/raw/rel-18/23_series/23283/cad41f28af38bf1707891b7ab8746331_img.jpg b/raw/rel-18/23_series/23283/cad41f28af38bf1707891b7ab8746331_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59d3623d57bd5aeaf3da7395d3da8e8a2f5b279a --- /dev/null +++ b/raw/rel-18/23_series/23283/cad41f28af38bf1707891b7ab8746331_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:799401bb0b99f0cb6e13814fd89c7478801e92ca344774bbc85b8f04c18d0c7d +size 42563 diff --git a/raw/rel-18/23_series/23283/ceb6fe29e2d57711907569c31182b3c2_img.jpg b/raw/rel-18/23_series/23283/ceb6fe29e2d57711907569c31182b3c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06df5d069e8b86d66a23b95a40775821a4e650db --- /dev/null +++ b/raw/rel-18/23_series/23283/ceb6fe29e2d57711907569c31182b3c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45e20da7cdae28db134d260d604a6e40d6f856ad72cfb0762f6e7f4e5be4a1fc +size 40797 diff --git a/raw/rel-18/23_series/23283/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg b/raw/rel-18/23_series/23283/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e105dd3e244247bb2c3d0c4f17fd922da9df53cc --- /dev/null +++ b/raw/rel-18/23_series/23283/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97805cf67639e481d085cf3f04ad10c5e09c8ac38d23d8494f0fba4ce2d42a43 +size 48735 diff --git a/raw/rel-18/23_series/23283/da5916a6e0721dae9522ac5b8abd218f_img.jpg b/raw/rel-18/23_series/23283/da5916a6e0721dae9522ac5b8abd218f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c50da01bf75b2de60a35a8762d6bc63d084a370 --- /dev/null +++ b/raw/rel-18/23_series/23283/da5916a6e0721dae9522ac5b8abd218f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b9729020dface9822285c2ef32d6c4bbd2f0743a44b44f343378a56ba19e1e +size 42611 diff --git a/raw/rel-18/23_series/23283/da90447206621f137780272a2bf807a4_img.jpg b/raw/rel-18/23_series/23283/da90447206621f137780272a2bf807a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47a29543df51e50b5aef1c8756704ffb212c7abe --- /dev/null +++ b/raw/rel-18/23_series/23283/da90447206621f137780272a2bf807a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d9f6a865298954c111e1e9c2fe128e3c5b18243f801f750d08a93038ac482e6 +size 30162 diff --git a/raw/rel-18/23_series/23283/dbe8bef1723acb3e03e8616be4faf939_img.jpg b/raw/rel-18/23_series/23283/dbe8bef1723acb3e03e8616be4faf939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc0308292588d9a0059055378b0bb8a5349135e5 --- /dev/null +++ b/raw/rel-18/23_series/23283/dbe8bef1723acb3e03e8616be4faf939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7304d1bbe7df053e4fcde25410ab8b12f04250b64d9cf6716ce2a2107ca8cf8 +size 53305 diff --git a/raw/rel-18/23_series/23283/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg b/raw/rel-18/23_series/23283/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a57477b5f516593dc977ef8302a2c708d3dbb6e --- /dev/null +++ b/raw/rel-18/23_series/23283/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7ea971c6ac6cd982487e47e5213d60aa5d7ac59573b79c06e7f57f24ff4f73f +size 56013 diff --git a/raw/rel-18/23_series/23283/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/raw/rel-18/23_series/23283/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7261cffef6fd8c1f1e9fb9eab986938d5c991e6e --- /dev/null +++ b/raw/rel-18/23_series/23283/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5207d08f571722f35288351ce698a0bc8dc88df419ca49529b4910176a2734b +size 17349 diff --git a/raw/rel-18/23_series/23283/dfaa8b98082261913dac00eae86b2889_img.jpg b/raw/rel-18/23_series/23283/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..511f0e2ffdb19f5289301d5ab458ea5ac452935c --- /dev/null +++ b/raw/rel-18/23_series/23283/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1604edf5e148887c24decb8d2e10350f550489db7f651bf3762a2c185ee2c8ac +size 15953 diff --git a/raw/rel-18/23_series/23283/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/raw/rel-18/23_series/23283/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34df4da7439a01b1de5aca64981c4208fcd9d4da --- /dev/null +++ b/raw/rel-18/23_series/23283/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20ef4eba0c164d7796f9f00b472a7483256ab532984de700b9312fea344c0f99 +size 49353 diff --git a/raw/rel-18/23_series/23283/e3e8a926bfe6337a654ecac063ba3682_img.jpg b/raw/rel-18/23_series/23283/e3e8a926bfe6337a654ecac063ba3682_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f6b49d6338171515d3e0100742117cb7927692b --- /dev/null +++ b/raw/rel-18/23_series/23283/e3e8a926bfe6337a654ecac063ba3682_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ce28571291f8b38b7cb0790661518133551058dc1428cd67092176d98c72737 +size 53139 diff --git a/raw/rel-18/23_series/23283/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg b/raw/rel-18/23_series/23283/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20828a3105df650b096c8e4792ec0cdf66aaa6a1 --- /dev/null +++ b/raw/rel-18/23_series/23283/e8f5277dca9bb75e7ba79d96c568db4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7427f835567f91c7a5d6a53877ebed038eafd737678a2df49a435c1b3a0fa63 +size 37223 diff --git a/raw/rel-18/23_series/23283/e93f2f4b0bf7e94139c1a2f1357962da_img.jpg b/raw/rel-18/23_series/23283/e93f2f4b0bf7e94139c1a2f1357962da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58309ea783568dd905b4137b5e27d5017a71954f --- /dev/null +++ b/raw/rel-18/23_series/23283/e93f2f4b0bf7e94139c1a2f1357962da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7c5405ccc0aa15c6b8f206ef44a9b528059a7ddadf1abafdb54c809630b8f92 +size 42535 diff --git a/raw/rel-18/23_series/23283/ecae674475cecdd0962200a5d1e2591e_img.jpg b/raw/rel-18/23_series/23283/ecae674475cecdd0962200a5d1e2591e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa092bf9115e984a6d1a3a7b338330788b0dfef6 --- /dev/null +++ b/raw/rel-18/23_series/23283/ecae674475cecdd0962200a5d1e2591e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:136c76620d455ec9b0ea0933ceca513ac770b632ac31debd5b92288b627f4d22 +size 49511 diff --git a/raw/rel-18/23_series/23283/efb282bed9f06eef1987a14fb27bc599_img.jpg b/raw/rel-18/23_series/23283/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bde302b7c0fa3f1562010a66be240cb0312e959 --- /dev/null +++ b/raw/rel-18/23_series/23283/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c943d41bc900bb349c52117155fd951029d77ff02c74bb288e1cace674caa38 +size 20697 diff --git a/raw/rel-18/23_series/23283/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg b/raw/rel-18/23_series/23283/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48abe1c83229e8719e76c1e5ab8e64e9eb007a7b --- /dev/null +++ b/raw/rel-18/23_series/23283/f448b5e4d6e55f3fbf9f3953acbbd8b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dc8099dd9950ae5e81d00f00a340c8703d2d3fe27ad1faf74e25556346e7a94 +size 56617 diff --git a/raw/rel-18/23_series/23283/f4b570ddd089f54943d46e9f8776f9f9_img.jpg b/raw/rel-18/23_series/23283/f4b570ddd089f54943d46e9f8776f9f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..151d2db51cc34c216227ae3d0f9dd382d8de6976 --- /dev/null +++ b/raw/rel-18/23_series/23283/f4b570ddd089f54943d46e9f8776f9f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a806eec27c659d1ba70f8fd43fd800491a466650e242b90554d5ee99241431b0 +size 43655 diff --git a/raw/rel-18/23_series/23283/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/raw/rel-18/23_series/23283/f64e1e0997695248c0cd4122c5b1a170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e82f08d88b34ed8a797f0cd461e2cb8b164a25ce --- /dev/null +++ b/raw/rel-18/23_series/23283/f64e1e0997695248c0cd4122c5b1a170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:624b665389a9fcc26b1d33c79dedd3b19f4244ee3822c937976ef1e74d87866b +size 18553 diff --git a/raw/rel-18/23_series/23283/f732d3320afe06d979aabbd366184254_img.jpg b/raw/rel-18/23_series/23283/f732d3320afe06d979aabbd366184254_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..011b0f09d6b476837fbb4750f81799b373be4583 --- /dev/null +++ b/raw/rel-18/23_series/23283/f732d3320afe06d979aabbd366184254_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89c5be54b314bf950c07bbaf181922629261abdcf38cb05de9d561849b7f9e77 +size 16447 diff --git a/raw/rel-18/23_series/23283/fcc757566216206ceddbd6c775e8db02_img.jpg b/raw/rel-18/23_series/23283/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40f52f8dec4fa740fc5f011252d2a092e0e08728 --- /dev/null +++ b/raw/rel-18/23_series/23283/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b79735163a7f2265b00b59b5028080d81ec90a0d2c35cceab9677847240ae95 +size 34012 diff --git a/raw/rel-18/23_series/23283/fdc47b9a20953c3611add6122f6831bf_img.jpg b/raw/rel-18/23_series/23283/fdc47b9a20953c3611add6122f6831bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..265281527e91766d2da49e415bf406ad86c2caa1 --- /dev/null +++ b/raw/rel-18/23_series/23283/fdc47b9a20953c3611add6122f6831bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e0df421a39476413f36a772923e9d7be38bc60bf5da756327aab139f71c3e30 +size 64708 diff --git a/raw/rel-18/23_series/23283/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/raw/rel-18/23_series/23283/fed4a04822c24fb22cca3a14f4ddae83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81bc6bf7385ddb6e2798ed145c0c361b11a349d9 --- /dev/null +++ b/raw/rel-18/23_series/23283/fed4a04822c24fb22cca3a14f4ddae83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7a167cf8c3d2a39002f69d51d179872684f4056c734cfd1a3bbff8197b86f4b +size 30793 diff --git a/raw/rel-18/23_series/23304/raw.md b/raw/rel-18/23_series/23304/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b1f824aecd9e15c51ad5b727b1eafe4192c22d4e --- /dev/null +++ b/raw/rel-18/23_series/23304/raw.md @@ -0,0 +1,5328 @@ + + +# 3GPP TS 23.304 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Proximity based Services (ProSe) in the 5G System (5GS) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions of terms and abbreviations ..... | 12 | +| 3.1 Terms..... | 12 | +| 3.2 Abbreviations ..... | 14 | +| 4 Architecture model and concepts..... | 14 | +| 4.1 General concept..... | 14 | +| 4.2 Architectural reference model..... | 14 | +| 4.2.1 Non-roaming reference architecture ..... | 14 | +| 4.2.2 Roaming reference architecture..... | 16 | +| 4.2.3 Inter-PLMN reference architecture ..... | 17 | +| 4.2.4 AF-based service parameter provisioning ..... | 19 | +| 4.2.5 Reference points ..... | 20 | +| 4.2.6 Service-based interfaces ..... | 21 | +| 4.2.7 5G ProSe UE-to-Network Relay reference architecture..... | 21 | +| 4.2.7.1 5G ProSe Layer-3 UE-to-Network Relay reference architecture ..... | 21 | +| 4.2.7.2 5G ProSe Layer-2 UE-to-Network Relay reference architecture ..... | 23 | +| 4.2.8 5G ProSe UE-to-UE Relay reference architecture ..... | 24 | +| 4.3 Functional Entities..... | 24 | +| 4.3.1 UE..... | 24 | +| 4.3.2 5G DDNMF ..... | 25 | +| 4.3.2.1 General..... | 25 | +| 4.3.2.2 5G DDNMF Discovery..... | 26 | +| 4.3.3 PCF ..... | 26 | +| 4.3.4 AMF ..... | 26 | +| 4.3.5 UDM..... | 27 | +| 4.3.6 UDR..... | 27 | +| 4.3.7 NRF ..... | 27 | +| 4.3.8 ProSe Application Server ..... | 27 | +| 4.3.9 5G ProSe UE-to-Network Relay ..... | 28 | +| 4.3.9.1 General..... | 28 | +| 4.3.9.2 5G ProSe Layer-3 UE-to-Network Relay ..... | 28 | +| 4.3.9.3 5G ProSe Layer-2 UE-to-Network Relay ..... | 29 | +| 4.3.10 SMF ..... | 29 | +| 4.3.11 NEF..... | 29 | +| 4.3.12 5G ProSe UE-to-UE Relay ..... | 29 | +| 4.3.12.1 General..... | 29 | +| 4.3.12.2 5G ProSe Layer-3 UE-to-UE Relay..... | 29 | +| 4.3.12.3 5G ProSe Layer-2 UE-to-UE Relay..... | 30 | +| 5 High level functionality and features..... | 30 | +| 5.1 Authorization and Provisioning for ProSe service..... | 30 | +| 5.1.1 General ..... | 30 | +| 5.1.1a General principles for applying policy/parameters ..... | 31 | +| 5.1.2 Authorization and Provisioning for 5G ProSe Direct Discovery ..... | 33 | +| 5.1.2.1 Policy/Parameter provisioning for 5G ProSe Direct Discovery ..... | 33 | +| 5.1.2.2 Principles for applying parameters for 5G ProSe Direct Discovery ..... | 34 | +| 5.1.3 Authorization and Provisioning for 5G ProSe Direct Communication..... | 35 | +| 5.1.3.1 Policy/Parameter provisioning for 5G ProSe Direct Communication..... | 35 | +| 5.1.3.2 Principles for applying parameters for 5G ProSe Direct Communication ..... | 36 | +| 5.1.4 Authorization and Provisioning for 5G ProSe UE-to-Network Relay ..... | 36 | +| 5.1.4.1 Policy/Parameter provisioning for 5G ProSe UE-to-Network Relay ..... | 36 | +| 5.1.4.2 Principles for applying parameters for 5G ProSe UE-to-Network Relay..... | 39 | +| 5.1.4.2.1 Principles for applying parameters for ProSe UE-to-Network Relay discovery ..... | 39 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------|----| +| 5.1.4.2.2 | Principles for applying parameters for 5G ProSe UE-to-Network Relay communication ..... | 39 | +| 5.1.4.3 | Network controlled security procedures for 5G ProSe UE-to-Network Relay ..... | 39 | +| 5.1.4.3.1 | General ..... | 39 | +| 5.1.4.3.2 | Control Plane based security procedures for 5G ProSe UE-to-Network Relay ..... | 39 | +| 5.1.4.3.3 | User Plane based security procedures ..... | 40 | +| 5.1.5 | Authorization and Provisioning for 5G ProSe UE-to-UE Relay ..... | 40 | +| 5.1.5.1 | Policy/Parameter provisioning for 5G ProSe UE-to-UE Relay ..... | 40 | +| 5.1.5.2 | Principles for applying parameters for 5G ProSe UE-to-UE Relay ..... | 42 | +| 5.1.5.2.1 | Principles for applying parameters for ProSe UE-to-UE Relay discovery ..... | 42 | +| 5.1.5.2.2 | Principles for applying parameters for 5G ProSe UE-to-UE Relay communication ..... | 42 | +| 5.2 | 5G ProSe Direct Discovery ..... | 42 | +| 5.2.1 | General ..... | 42 | +| 5.2.2 | 5G ProSe Direct Discovery Models ..... | 42 | +| 5.2.3 | 5G ProSe UE-to-Network Relay Discovery ..... | 42 | +| 5.2.4 | 5G ProSe Direct Discovery Characteristics ..... | 43 | +| 5.2.5 | 5G ProSe UE-to-UE Relay Discovery ..... | 43 | +| 5.3 | 5G ProSe Direct Communication ..... | 44 | +| 5.3.1 | General ..... | 44 | +| 5.3.2 | Broadcast mode 5G ProSe Direct Communication ..... | 44 | +| 5.3.3 | Groupcast mode 5G ProSe Direct Communication ..... | 44 | +| 5.3.4 | Unicast mode 5G ProSe Direct Communication ..... | 44 | +| 5.4 | 5G ProSe UE-to-Network Relay ..... | 45 | +| 5.4.1 | 5G ProSe Layer-3 UE-to-Network Relay ..... | 45 | +| 5.4.1.1 | General ..... | 45 | +| 5.4.1.2 | 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support ..... | 45 | +| 5.4.1.3 | Policy control and session binding to support 5G ProSe Layer-3 UE-to-Network Relay without N3IWF ..... | 46 | +| 5.4.2 | 5G ProSe Layer-2 UE-to-Network Relay ..... | 46 | +| 5.4.3 | Mobility Restrictions for 5G ProSe UE-to-Network Relaying ..... | 47 | +| 5.4.4 | Support of emergency service from 5G ProSe Remote UE via 5G ProSe UE-to-Network Relay ..... | 47 | +| 5.4.4.1 | General ..... | 47 | +| 5.4.4.2 | Emergency service from 5G ProSe Remote UE via 5G ProSe Layer-2 UE-to-Network Relay ..... | 48 | +| 5.4.4.3 | Emergency service from 5G ProSe Remote UE via 5G ProSe Layer-3 UE-to-Network Relay ..... | 48 | +| 5.5 | IP address allocation ..... | 49 | +| 5.5.1 | General ..... | 49 | +| 5.5.1.1 | IP address allocation for unicast mode of 5G ProSe direct communication ..... | 49 | +| 5.5.1.2 | IP address allocation for broadcast and groupcast modes of 5G ProSe direct communication ..... | 49 | +| 5.5.1.3 | IP address allocation for communication with a 5G ProSe Layer-3 ProSe UE-to-Network Relay ..... | 50 | +| 5.5.1.4 | IP address allocation for communication with a 5G ProSe Layer-3 UE-to-UE Relay ..... | 50 | +| 5.5.2 | IPv6 Prefix Delegation via DHCPv6 for 5G ProSe Layer-3 UE-to-Network Relay ..... | 51 | +| 5.6 | QoS handling ..... | 51 | +| 5.6.1 | QoS handling for 5G ProSe Direct Communication ..... | 51 | +| 5.6.2 | QoS handling for 5G ProSe UE-to-Network Relay operations ..... | 52 | +| 5.6.2.1 | QoS handling for 5G ProSe Layer-3 UE-to-Network Relay without N3IWF ..... | 52 | +| 5.6.2.2 | QoS handling for 5G ProSe Layer-3 UE-to-Network relay with N3IWF ..... | 54 | +| 5.6.2.3 | QoS handling for 5G ProSe Layer-2 UE-to-Network Relay ..... | 55 | +| 5.6.3 | QoS handling for 5G ProSe UE-to-UE Relay operations ..... | 55 | +| 5.6.3.1 | QoS handling for 5G ProSe Layer-3 UE-to-UE Relay ..... | 55 | +| 5.6.3.2 | QoS handling for 5G ProSe Layer-2 UE-to-UE Relay ..... | 56 | +| 5.7 | Subscription to 5G ProSe ..... | 56 | +| 5.8 | Identifiers ..... | 57 | +| 5.8.1 | Identifiers for 5G ProSe Direct Discovery ..... | 57 | +| 5.8.1.0 | General ..... | 57 | +| 5.8.1.1 | ProSe Application ID ..... | 58 | +| 5.8.1.2 | Destination Layer-2 ID ..... | 58 | +| 5.8.1.3 | Source Layer-2 ID ..... | 58 | +| 5.8.1.4 | ProSe Application Code ..... | 58 | +| 5.8.1.5 | ProSe Restricted Code ..... | 58 | +| 5.8.1.6 | ProSe Query Code ..... | 58 | +| 5.8.1.7 | ProSe Response Code ..... | 58 | +| 5.8.1.8 | User Info ID ..... | 58 | +| 5.8.1.9 | ProSe Discovery UE ID ..... | 58 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------------|----| +| 5.8.1.10 | Restricted ProSe Application User ID ..... | 59 | +| 5.8.1.11 | Announcing PLMN ID ..... | 59 | +| 5.8.1.12 | Announcer Info ..... | 59 | +| 5.8.1.13 | Discoverer Info ..... | 59 | +| 5.8.1.14 | Target Info ..... | 59 | +| 5.8.1.15 | Discoveree Info..... | 59 | +| 5.8.1.16 | Application Layer Group ID ..... | 59 | +| 5.8.2 | Identifiers for 5G ProSe Direct Communication ..... | 59 | +| 5.8.2.1 | General ..... | 59 | +| 5.8.2.2 | Identifiers for broadcast mode 5G ProSe direct communication..... | 59 | +| 5.8.2.3 | Identifiers for groupcast mode 5G ProSe direct communication ..... | 60 | +| 5.8.2.4 | Identifiers for unicast mode 5G ProSe direct communication..... | 60 | +| 5.8.3 | Identifiers for 5G ProSe UE-to-Network Relay ..... | 60 | +| 5.8.3.1 | Common identifiers for 5G ProSe UE-to-Network Relay..... | 60 | +| 5.8.3.2 | Identifiers for 5G ProSe Layer-3 UE-to-Network Relay ..... | 62 | +| 5.8.3.3 | Identifiers for 5G ProSe Layer-2 UE-to-Network Relay..... | 62 | +| 5.8.4 | Identifiers for 5G ProSe UE-to-UE Relay Discovery ..... | 62 | +| 5.8.4.1 | General ..... | 62 | +| 5.8.4.2 | Common identifiers for 5G ProSe UE-to-UE Relay Discovery ..... | 62 | +| 5.8.5 | Identifiers for 5G ProSe UE-to-UE Relay Communication with integrated Discovery..... | 64 | +| 5.9 | Support for 5G ProSe for UEs in limited service state ..... | 64 | +| 5.10 | PC5 operation in EPS for Public Safety UE ..... | 65 | +| 5.11 | Communication path selection between PC5 and Uu reference points ..... | 65 | +| 5.12 | NAS level congestion control for 5G ProSe UE-to-Network Relay ..... | 66 | +| 5.13 | Support for PC5 DRX operations..... | 66 | +| 5.13.1 | General ..... | 66 | +| 5.13.2 | PC5 DRX operations for 5G ProSe Direct Discovery and 5G ProSe UE-to-Network Relay Discovery ... | 66 | +| 5.13.3 | PC5 DRX operations for 5G ProSe Direct Communication and 5G ProSe UE-to-Network Relay
Communication ..... | 66 | +| 5.14 | 5G ProSe UE-to-UE Relay Communication..... | 67 | +| 5.14.1 | 5G ProSe Layer-3 UE-to-UE Relay Communication..... | 67 | +| 5.14.2 | 5G ProSe Layer-2 UE-to-UE Relay Communication..... | 67 | +| 5.15 | Path switching between two UE-to-Network Relays..... | 67 | +| 5.16 | Communication path switching between PC5 and Uu reference points ..... | 68 | +| 5.17 | Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay ..... | 69 | +| 5.17.1 | General ..... | 69 | +| 5.17.2 | Multi-path communication via direct Uu path and via 5G ProSe Layer-3 UE-to-Network Relay ..... | 69 | +| 5.18 | Support of Public Warning Notification Relaying..... | 70 | +| 6 | Functional description and information flows ..... | 70 | +| 6.1 | Control and user plane stacks..... | 70 | +| 6.1.1 | Control Plane ..... | 70 | +| 6.1.1.1 | General ..... | 70 | +| 6.1.1.2 | UE - UE ..... | 71 | +| 6.1.1.2.1 | Discovery plane PC5 interface..... | 71 | +| 6.1.1.2.2 | PC5 Signalling Protocol ..... | 71 | +| 6.1.1.3 | UE - 5G DDNMF ..... | 72 | +| 6.1.1.4 | 5G DDNMF – UDM..... | 72 | +| 6.1.1.5 | 5G DDNMF – 5G DDNMF ..... | 72 | +| 6.1.1.6 | 5G DDNMF – ProSe Application Server ..... | 72 | +| 6.1.1.7 | 5G ProSe UE-to-Network Relay..... | 72 | +| 6.1.1.7.1 | 5G ProSe Layer-3 UE-to-Network Relay ..... | 72 | +| 6.1.1.7.2 | 5G ProSe Layer-2 UE-to-Network Relay ..... | 73 | +| 6.1.1.8 | 5G ProSe UE-to-UE Relay ..... | 74 | +| 6.1.1.8.1 | 5G ProSe Layer-2 UE-to-UE Relay ..... | 74 | +| 6.1.1.8.2 | 5G ProSe Layer-3 UE-to-UE Relay ..... | 74 | +| 6.1.2 | User Plane..... | 75 | +| 6.1.2.1 | General ..... | 75 | +| 6.1.2.2 | UE - UE ..... | 75 | +| 6.1.2.3 | 5G ProSe UE-to-Network Relay..... | 76 | +| 6.1.2.3.1 | 5G ProSe Layer-3 UE-to-Network Relay ..... | 76 | +| 6.1.2.3.2 | 5G ProSe Layer-2 UE-to-Network Relay ..... | 76 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------------------------|-----| +| 6.1.2.4 | 5G ProSe UE-to-UE Relay ..... | 77 | +| 6.1.2.4.1 | 5G ProSe Layer-2 UE-to-UE Relay ..... | 77 | +| 6.1.2.4.2 | 5G ProSe Layer-3 UE-to-UE Relay ..... | 77 | +| 6.2 | Procedures for Service Authorization and Provisioning to UE..... | 77 | +| 6.2.1 | General ..... | 77 | +| 6.2.2 | PCF based Service Authorization and Provisioning to UE ..... | 78 | +| 6.2.3 | PCF discovery ..... | 78 | +| 6.2.4 | Procedure for UE triggered ProSe Policy provisioning ..... | 78 | +| 6.2.5 | AF-based service parameter provisioning for ProSe over control plane..... | 79 | +| 6.3 | 5G ProSe Direct Discovery ..... | 79 | +| 6.3.1 | 5G ProSe Direct Discovery with 5G DDNMF ..... | 79 | +| 6.3.1.1 | Overview..... | 79 | +| 6.3.1.2 | Overall procedure for 5G ProSe Direct Discovery (Model A)..... | 80 | +| 6.3.1.3 | Overall procedure for 5G ProSe Direct Discovery (Model B) ..... | 81 | +| 6.3.1.4 | Discovery Request procedures..... | 82 | +| 6.3.1.5 | Discovery Reporting procedures ..... | 83 | +| 6.3.1.6 | Announcing Alert Procedures for restricted discovery..... | 83 | +| 6.3.1.7 | Direct Discovery Update Procedures..... | 83 | +| 6.3.2 | 5G ProSe Direct Discovery procedures over PC5 reference point..... | 84 | +| 6.3.2.1 | General..... | 84 | +| 6.3.2.2 | Group Member Discovery ..... | 85 | +| 6.3.2.2.1 | General ..... | 85 | +| 6.3.2.2.2 | Procedure for Group Member Discovery with Model A ..... | 86 | +| 6.3.2.2.3 | Procedure for Group Member Discovery with Model B..... | 86 | +| 6.3.2.3 | 5G ProSe UE-to-Network Relay Discovery ..... | 87 | +| 6.3.2.3.1 | General ..... | 87 | +| 6.3.2.3.2 | Procedure for 5G ProSe UE-to-Network Relay Discovery with Model A ..... | 87 | +| 6.3.2.3.3 | Procedure for 5G ProSe UE-to-Network Relay Discovery with Model B ..... | 88 | +| 6.3.2.4 | 5G ProSe UE-to-UE Relay Discovery..... | 89 | +| 6.3.2.4.1 | General ..... | 89 | +| 6.3.2.4.2 | Procedure for 5G ProSe UE-to-UE Relay Discovery with Model A ..... | 89 | +| 6.3.2.4.3 | Procedure for 5G ProSe UE-to-UE Relay Discovery with Model B ..... | 90 | +| 6.3.2.4.4 | Candidate 5G ProSe UE-to-UE Relay Discovery ..... | 91 | +| 6.4 | 5G ProSe Direct Communication..... | 91 | +| 6.4.1 | Broadcast mode 5G ProSe Direct Communication ..... | 91 | +| 6.4.2 | Groupcast mode 5G ProSe Direct Communication..... | 92 | +| 6.4.3 | Unicast mode 5G ProSe Direct Communication..... | 94 | +| 6.4.3.1 | Layer-2 link establishment over PC5 reference point ..... | 94 | +| 6.4.3.2 | Link identifier update for a unicast link..... | 98 | +| 6.4.3.3 | Layer-2 link release over PC5 reference point ..... | 99 | +| 6.4.3.4 | Layer-2 link modification for a unicast link ..... | 100 | +| 6.4.3.5 | Layer-2 link maintenance over PC5 reference point ..... | 101 | +| 6.4.3.6 | Layer-2 link management over PC5 reference point for 5G ProSe UE-to-Network Relay..... | 102 | +| 6.4.3.7 | Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay ..... | 103 | +| 6.4.3.7.1 | Common part for Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay ..... | 103 | +| 6.4.3.7.2 | Layer-2 link management over PC5 reference point for 5G ProSe Layer-2 UE-to-UE Relay ..... | 104 | +| 6.4.3.7.3 | Layer-2 link management over PC5 reference point for 5G ProSe Layer-3 UE-to-UE Relay ..... | 105 | +| 6.4.3.7.4 | Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay Communication with integrated Discovery..... | 106 | +| 6.5 | 5G ProSe UE-to-Network Relay Communication ..... | 107 | +| 6.5.1 | 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay..... | 107 | +| 6.5.1.0 | General..... | 107 | +| 6.5.1.1 | 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF ..... | 107 | +| 6.5.1.2 | 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support ..... | 110 | +| 6.5.1.2.1 | Connection management via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support ..... | 110 | +| 6.5.1.2.2 | N3IWF selection for 5G ProSe Layer-3 Remote UE procedure ..... | 112 | +| 6.5.1.2.3 | Mobility of 5G ProSe Layer-3 Remote UE between Direct and Indirect Network communication path ..... | 112 | +| 6.5.1.3 | Additional parameters announcement procedure ..... | 112 | +| 6.5.2 | 5G ProSe Communication via 5G ProSe Layer-2 UE-to-Network Relay..... | 114 | +| 6.5.2.1 | Registration and Connection Management..... | 114 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.5.2.1.1 | Registration Management ..... | 114 | +| 6.5.2.1.2 | Connection Management..... | 114 | +| 6.5.2.2 | Connection establishment..... | 115 | +| 6.5.2.3 | Path switching between direct network communication path and indirect network communication path via 5G ProSe Layer-2 UE-to-Network Relay ..... | 116 | +| 6.5.3 | 5G ProSe UE-to-Network Relay reselection..... | 116 | +| 6.5.4 | 5G ProSe Remote UE traffic handling for 5G ProSe UE-to-Network Relay support..... | 116 | +| 6.5.5 | Procedures for Communication Path Switching between Two UE-to-Network Relays ..... | 117 | +| 6.5.5.1 | General..... | 117 | +| 6.5.5.2 | Procedures for Communication Path Switching between UE-to-Network Relays..... | 118 | +| 6.6 | Procedures for Service Authorization to NG-RAN..... | 118 | +| 6.6.1 | General ..... | 118 | +| 6.6.2 | Registration procedure..... | 118 | +| 6.6.3 | Service Request procedure ..... | 119 | +| 6.6.4 | N2 Handover procedure ..... | 120 | +| 6.6.5 | Xn Handover procedure ..... | 120 | +| 6.6.6 | Subscriber Data Update Notification to AMF..... | 120 | +| 6.6.7 | Delivery of PC5 QoS parameters for ProSe to NG-RAN ..... | 120 | +| 6.7 | 5G ProSe UE-to-UE Relay Communication..... | 121 | +| 6.7.1 | 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay ..... | 121 | +| 6.7.1.1 | Layer-2 link establishment for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay ..... | 121 | +| 6.7.1.2 | Link identifier update for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay ..... | 123 | +| 6.7.1.3 | Layer-2 link release for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay ..... | 125 | +| 6.7.1.4 | Layer-2 link modification for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay ..... | 126 | +| 6.7.1.5 | Layer-2 link maintenance for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay ..... | 126 | +| 6.7.2 | 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay ..... | 126 | +| 6.7.3 | 5G ProSe UE-to-UE Relay Communication with integrated Discovery..... | 128 | +| 6.7.3.1 | General..... | 128 | +| 6.7.3.2 | Procedure for Communication via Layer-3 UE-to-UE Relay ..... | 128 | +| 6.7.3.3 | Procedure for Communication via Layer-2 UE-to-UE Relay ..... | 130 | +| 6.7.4 | 5G ProSe UE-to-UE Relay reselection..... | 131 | +| 6.7.4.1 | General..... | 131 | +| 6.7.4.2 | Negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection..... | 131 | +| 6.7.4.3 | Negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection..... | 132 | +| 6.8 | Procedures for communication path switching between PC5 and Uu reference points..... | 134 | +| 6.8.1 | Procedure for communication path switching from Uu reference point to PC5 reference point ..... | 134 | +| 6.8.2 | Procedure for communication path switching from PC5 reference point to Uu reference point ..... | 135 | +| 6.9 | Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay ..... | 137 | +| 6.9.1 | General ..... | 137 | +| 6.9.2 | Multi-path communication via direct Uu path and via 5G ProSe Layer-3 UE-to-Network Relay ..... | 137 | +| 6.9.3 | Multi-path communication via direct Uu path and via 5G ProSe Layer-2 UE-to-Network Relay ..... | 137 | +| 7 | Network Function Services..... | 138 | +| 7.1 | 5G DDNMF Services..... | 138 | +| 7.1.1 | General ..... | 138 | +| 7.1.2 | N5g-ddnmf_Discovery service..... | 138 | +| 7.1.2.1 | General..... | 138 | +| 7.1.2.2 | N5g-ddnmf_Discovery_AnnounceAuthorize service operation ..... | 138 | +| 7.1.2.3 | N5g-ddnmf_Discovery_AnnounceUpdate service operation..... | 138 | +| 7.1.2.4 | N5g-ddnmf_Discovery_MonitorAuthorize service operation..... | 139 | +| 7.1.2.5 | N5g-ddnmf_Discovery_MonitorUpdate service operation ..... | 139 | +| 7.1.2.6 | N5g-ddnmf_Discovery_MonitorUpdateResult service operation ..... | 139 | +| 7.1.2.7 | N5g-ddnmf_Discovery_DiscoveryAuthorize service operation ..... | 139 | +| 7.1.2.8 | N5g-ddnmf_Discovery_MatchReport service operation..... | 140 | +| 7.1.2.9 | N5g-ddnmf_Discovery_MatchInformation service operation..... | 140 | +| 7.2 | AF Services ..... | 140 | +| 7.2.1 | General ..... | 140 | +| 7.2.2 | Naf_ProSe service ..... | 140 | +| 7.2.2.1 | General..... | 140 | +| 7.2.2.2 | Naf_ProSe_DiscoveryAuthorization service operation..... | 141 | +| 7.2.2.3 | Naf_ProSe_DiscoveryAuthorizationUpdateNotify service operation..... | 141 | +| 7.2.2.4 | Naf_ProSe_DiscoveryAuthorizationResultUpdate service operation..... | 141 | + +**Annex A (informative): Change history.................................................................................................. 142** + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +--- + +# 1 Scope + +The present document specifies the Stage 2 of the Proximity based Services (ProSe) features in 5GS. 5G ProSe features consist of: 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay and 5G ProSe UE-to-UE Relay. + +5G ProSe Direct Discovery identifies that 5G ProSe-enabled UEs are in proximity using NR. + +5G ProSe Direct Communication enables establishment of communication paths between two or more 5G ProSe-enabled UEs that are in direct communication range using NR. + +5G ProSe UE-to-Network Relay enables indirect communication between the 5G network and UEs (e.g. for UEs that are out of coverage of the network). + +5G ProSe UE-to-UE Relay enables indirect communication between two 5G ProSe End UEs. + +Security aspects of ProSe in 5GS are defined in TS 33.503 [29]. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [3] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [4] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [5] 3GPP TS 23.502: "Procedures for the 5G System (5GS); Stage 2". +- [6] 3GPP TS 22.261: "Service requirements for next generation new services and markets; Stage 1". +- [7] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)". +- [8] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [9] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System". +- [10] Void. +- [11] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [12] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [13] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode". +- [14] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode". + +- [15] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [16] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification". +- [17] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration". +- [18] IETF RFC 3927: "Dynamic Configuration of IPv4 Link-Local Addresses". +- [19] IETF RFC 826: "An Ethernet Address Resolution Protocol". +- [20] Void. +- [21] 3GPP TR 23.752: "Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS)". +- [22] 3GPP TS 32.277: "Proximity-based Services (ProSe) charging". +- [23] 3GPP TS 24.554: "Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3". +- [24] IETF RFC 2131: "Dynamic Host Configuration Protocol". +- [25] IETF RFC 4039: "Rapid Commit Option for the Dynamic Host Configuration Protocol version 4 (DHCPv4)". +- [26] Void. +- [27] Void. +- [28] 3GPP TS 38.351: "NR; Sidelink Adaptation Layer Protocol". +- [29] 3GPP TS 33.503: "Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS)". +- [30] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [31] 3GPP TS 23.167: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS) emergency sessions". +- [32] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [33] 3GPP TS 22.268: "Public Warning System (PWS) requirements". + +--- + +## 3 Definitions of terms and abbreviations + +### 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**5G ProSe-enabled UE:** A UE that supports 5G ProSe requirements and associated procedures. + +**5G ProSe Direct Discovery:** A procedure employed by a 5G ProSe-enabled UE to discover other 5G ProSe-enabled UEs in its vicinity based on direct radio transmissions between the two UEs with NR technology. + +**5G ProSe Direct Communication:** A communication between two or more UEs in proximity that are 5G ProSe-enabled, by means of user plane transmission using NR technology via a path not traversing any network node. + +**5G ProSe UE-to-Network Relay:** A 5G ProSe-enabled UE that provides functionality to support connectivity to the network for 5G ProSe Remote UE(s). + +**5G ProSe Remote UE:** A 5G ProSe-enabled UE that communicates with a DN via a 5G ProSe UE-to-Network Relay. + +**5G ProSe UE-to-UE Relay:** A 5G ProSe-enabled UE that provides functionality to support connectivity between 5G ProSe End UEs. + +**5G ProSe End UE:** A 5G ProSe-enabled UE that connects with another 5G ProSe-enabled UE(s) via a 5G ProSe UE-to-UE Relay. + +**Application Layer ID:** An identifier identifying a 5G ProSe-enabled UE within the context of a specific application. The format of this identifier is outside the scope of 3GPP. + +**Direct Network Communication:** One mode of network communication, where there is no 5G ProSe UE-to-Network Relay between a UE and the 5G network. + +**Indirect Network Communication:** One mode of network communication, where there is a 5G ProSe UE-to-Network Relay between a UE and the 5G network. + +**Member ID:** An identifier uniquely identifying a member in the Application Layer managed group and that is managed by the ProSe application layer. + +**Mode of communication:** Mode of communication to be used by the 5G ProSe-enabled UE over PC5 reference point, i.e. broadcast mode, groupcast mode or unicast mode. + +**Open ProSe Discovery:** ProSe Direct Discovery without explicit permission from the 5G ProSe-enabled UE being discovered, according to TS 22.278 [7]. + +**ProSe identifier:** A globally unique identifier used to identify the ProSe Application associated with the ProSe operation in 5G ProSe Direct Discovery and 5G ProSe Direct Communication. In this Release, the "Application ID" defined in TS 23.303 [3] can be used as the ProSe identifier in 5G ProSe Direct Discovery and in a consequent 5G ProSe Direct Communication. + +**Restricted ProSe Discovery:** ProSe Direct Discovery that only takes place with explicit permission from the 5G ProSe-enabled UE being discovered, according to TS 22.278 [7]. + +**Relay Service Code:** A Relay Service Code is used for the case of UE-to-Network Relay as well as for the case of UE-to-UE Relay. The definition for the case of UE-to-Network Relay is in TS 23.303 [3]. For the case of UE-to-UE Relay, the Relay Service Code is used to identify a connectivity service the 5G ProSe UE-to-UE Relay provides and the authorized users the 5G ProSe UE-to-UE Relay would offer service to. The definition of values of Relay Service Code for the case of UE-to-UE Relay is out of scope of this specification. + +**User Info ID:** The User Info ID is configured for Model A or Model B Group Member Discovery, 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery, either for public safety or commercial applications based on the policy of the HPLMN or via the ProSe application server that allocates it. The definition of values of User Info ID is out of scope of this specification. + +For the purposes of the present document, the following term and definition given in TS 23.303 [3] apply: + +**Application Layer Group ID** +**Destination Layer-2 ID** +**Discovery Entry ID** +**Discovery Filter** +**Discovery Query Filter** +**Discovery Response Filter** +**Geographical Area** +**Local PLMN** +**Model A** +**Model B** +**Metadata Index Mask** +**ProSe Application ID** +**ProSe Application Code** +**ProSe Application Mask** +**ProSe Query Code** +**ProSe Response Code** +**ProSe Restricted Code** +**ProSe Restricted Code Prefix** +**ProSe Restricted Code Suffix** + +**ProSe Discovery UE ID** +**ProSe Layer-2 Group ID** +**Restricted ProSe Application User ID** +**Source Layer-2 ID** + +For the purposes of the present document, the following term and definition given in TS 23.287 [2] apply: + +**NR Tx Profile** + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|----------|----------------------------------------------| +| 5G DDNMF | 5G Direct Discovery Name Management Function | +| AS layer | Access Stratum layer | +| NCGI | NR Cell Global ID | +| PDUID | ProSe Discovery UE ID | +| PFI | PC5 QoS Flow Identifier | +| PQI | PC5 5QI | +| ProSe | Proximity based Services | +| RPAUID | Restricted ProSe Application User ID | +| RSC | Relay Service Code | +| RSD | Rule Selection Descriptor | +| TAI | Tracking Area Identity | + +--- + +## 4 Architecture model and concepts + +### 4.1 General concept + +Proximity based Services (ProSe) are services that can be provided by the 5GS based on UEs being in proximity to each other. + +The 5GS enablers for ProSe include the following functions: + +- 5G ProSe Direct Discovery; +- 5G ProSe Direct Communication; +- 5G ProSe UE-to-Network Relay; +- 5G ProSe UE-to-UE Relay. + +### 4.2 Architectural reference model + +#### 4.2.1 Non-roaming reference architecture + +Figure 4.2.1-1 shows the high-level view of the non-roaming 5G System architecture for Proximity-based Services (ProSe) with service-based interfaces within the Control Plane. In this figure, UE A and UE B use a subscription of the same PLMN. + +![Diagram of Non-roaming 5G System architecture for Proximity-based Services. It shows the Data Network (ProSe Application Server) connected to the 5GC (UPF) via the N6 interface. The 5GC contains UDM, PCF, NEF, 5G DDNMF, NRF, UDR, AMF, SMF, and UPF. The AMF is connected to the NG-RAN, which is connected to UE A and UE B via Uu interfaces. UE A and UE B are connected to ProSe Applications. Reference points PC3a, PC3a, PC5, and PC1 are indicated between the UE and the 5GC components.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the non-roaming 5G system architecture for Proximity-based Services (ProSe). At the top, the Data Network contains a ProSe Application Server. This server connects to the 5G Core (5GC) via the N6 interface. The 5GC is composed of several Network Functions (NFs): UDM, PCF, NEF, 5G DDNMF, NRF, UDR, AMF, SMF, and UPF. The UDM, PCF, NEF, and 5G DDNMF are connected to a common Service Based Interface (SBI). Below this SBI, the NRF, UDR, AMF, and SMF are also connected to another SBI. The AMF connects to the NG-RAN. The NG-RAN is connected to two User Equipment (UE) units, UE A and UE B, via Uu interfaces. UE A and UE B each have a ProSe Application. Reference points are labeled: PC3a between UE A and the AMF, PC3a between UE B and the UPF, PC5 between UE A and UE B, and PC1 between UE A and the Data Network. + +Diagram of Non-roaming 5G System architecture for Proximity-based Services. It shows the Data Network (ProSe Application Server) connected to the 5GC (UPF) via the N6 interface. The 5GC contains UDM, PCF, NEF, 5G DDNMF, NRF, UDR, AMF, SMF, and UPF. The AMF is connected to the NG-RAN, which is connected to UE A and UE B via Uu interfaces. UE A and UE B are connected to ProSe Applications. Reference points PC3a, PC3a, PC5, and PC1 are indicated between the UE and the 5GC components. + +**Figure 4.2.1-1: Non-roaming 5G System architecture for Proximity-based Services** + +Figure 4.2.1-2 shows the high-level view of the non-roaming 5G System architecture for Proximity-based Services (ProSe) in reference point representation. In this figure, UE A and UE B use a subscription of the same PLMN. + +![Figure 4.2.1-2: Non-roaming 5G System architecture for Proximity-based Services in reference point representation. The diagram shows the 5G Core (5GC) containing SMF, PCF, AMF, UDM, 5G DDNMF, and NEF. External to the 5GC are NG-RAN, UE A, UE B, ProSe Applications, and a ProSe Application Server. UE A connects to NG-RAN via Uu and to UE B via PC5. UE B connects to NG-RAN via Uu. NG-RAN connects to AMF via N2. Within 5GC: AMF connects to SMF (N11), PCF (N15), UDM (N8), and 5G DDNMF (Npc3a). SMF connects to PCF (N7). PCF connects to UDM (Npc8). UDM connects to NEF (Npc4). 5G DDNMF connects to NEF (Npc2). NEF connects to ProSe Application Server (N33). ProSe Application Server connects to UE A and UE B via PC1. ProSe Applications on UEs connect to the ProSe Application Server via PC1.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +graph TD + subgraph 5GC + SMF + PCF + AMF + UDM + DDNMF[5G DDNMF] + NEF + end + + UE_A[UE A] -- PC5 --- UE_B[UE B] + UE_A -- Uu --- NGRAN[NG-RAN] + UE_B -- Uu --- NGRAN + NGRAN -- N2 --- AMF + + AMF -- N11 --- SMF + AMF -- N15 --- PCF + AMF -- N8 --- UDM + AMF -- PC3a --- DDNMF + + SMF -- N7 --- PCF + PCF -- Npc8 --- UDM + UDM -- Npc4 --- NEF + DDNMF -- Npc2 --- NEF + NEF -- N33 --- PAS[ProSe Application Server] + + UE_A -- PC1 --- PAS + UE_B -- PC1 --- PAS + + ProSe_App_A[ProSe Application] --- UE_A + ProSe_App_B[ProSe Application] --- UE_B + + UE_A -- PC3a --- DDNMF + UE_B -- PC3a --- DDNMF + +``` + +Figure 4.2.1-2: Non-roaming 5G System architecture for Proximity-based Services in reference point representation. The diagram shows the 5G Core (5GC) containing SMF, PCF, AMF, UDM, 5G DDNMF, and NEF. External to the 5GC are NG-RAN, UE A, UE B, ProSe Applications, and a ProSe Application Server. UE A connects to NG-RAN via Uu and to UE B via PC5. UE B connects to NG-RAN via Uu. NG-RAN connects to AMF via N2. Within 5GC: AMF connects to SMF (N11), PCF (N15), UDM (N8), and 5G DDNMF (Npc3a). SMF connects to PCF (N7). PCF connects to UDM (Npc8). UDM connects to NEF (Npc4). 5G DDNMF connects to NEF (Npc2). NEF connects to ProSe Application Server (N33). ProSe Application Server connects to UE A and UE B via PC1. ProSe Applications on UEs connect to the ProSe Application Server via PC1. + +**Figure 4.2.1-2: Non-roaming 5G System architecture for Proximity-based Services in reference point representation** + +## 4.2.2 Roaming reference architecture + +Figure 4.2.2-1 shows the high-level view of the roaming 5G System architecture for Proximity-based Services (ProSe) with service-based interfaces within the Control Plane. In the figure, UE A uses a subscription of HPLMN. + +![Roaming 5G System architecture for Proximity-based Services diagram](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates a roaming 5G system architecture for proximity-based services. It features two 5G Core (5GC) networks: the Home PLMN (HPLMN) and the Visited PLMN (VPLMN). The HPLMN 5GC includes the 5G DDNMF, PCF, NEF, UDM, SMF, and UPF. The VPLMN 5GC includes the 5G DDNMF, NRF, PCF, AMF, SMF, and UPF. User Equipment (UE) A is connected to an NG-RAN, which is connected to the VPLMN 5GC. UE B is also connected to the NG-RAN. Both UEs have associated ProSe Applications. A ProSe Application Server is connected to a Data Network. Interfaces shown include PC3a, PC5, and PC1. The NG-RAN is connected to the AMF in the VPLMN 5GC, which is connected to the SMF and UPF. The SMF is connected to the UPF. The AMF is connected to the NG-RAN. The NG-RAN is connected to the AMF. The AMF is connected to the SMF. The SMF is connected to the UPF. The UPF is connected to the Data Network. The Data Network is connected to the ProSe Application Server. The ProSe Application Server is connected to the ProSe Application on UE B. The ProSe Application on UE A is connected to the PC1 interface. The PC1 interface is connected to the ProSe Application Server. The PC5 interface is between UE A and UE B. The PC3a interface is between the NG-RAN and the HPLMN 5GC. + +Roaming 5G System architecture for Proximity-based Services diagram + +Figure 4.2.2-1: Roaming 5G System architecture for Proximity-based Services + +### 4.2.3 Inter-PLMN reference architecture + +The following figure 4.2.3-1 shows the high level view of the non-roaming inter-PLMN architecture with service-based interfaces within the Control Plane. In this figure, PLMN A is the HPLMN of UE A and PLMN B is the HPLMN of UE B. + +![Diagram of Non-roaming Inter-PLMN 5G System architecture for Proximity-based Services. It shows two PLMNs, PLMN B and PLMN A, each with its own 5GC. UE B is connected to NG-RAN in PLMN B, which is connected to AMF, SMF, UPF, and other 5GC components (NRF, UDR, PCF, NEF, UDM, 5G DDNMF). UE A is connected to NG-RAN in PLMN A, which is connected to AMF, SMF, UPF, and other 5GC components. Both UEs are connected to a ProSe Application. A ProSe Application Server is connected to a Data Network. Interfaces shown include PC1, PC3a, PC5, and Uu.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Diagram of Non-roaming Inter-PLMN 5G System architecture for Proximity-based Services. It shows two PLMNs, PLMN B and PLMN A, each with its own 5GC. UE B is connected to NG-RAN in PLMN B, which is connected to AMF, SMF, UPF, and other 5GC components (NRF, UDR, PCF, NEF, UDM, 5G DDNMF). UE A is connected to NG-RAN in PLMN A, which is connected to AMF, SMF, UPF, and other 5GC components. Both UEs are connected to a ProSe Application. A ProSe Application Server is connected to a Data Network. Interfaces shown include PC1, PC3a, PC5, and Uu. + +**Figure 4.2.3-1: Non-roaming Inter-PLMN 5G System architecture for Proximity-based Services** + +Figure 4.2.3-2 shows the high level view of the roaming architecture with service-based interfaces within the Control Plane. In this figure, UE A uses a subscription of PLMN A and UE B uses a subscription of PLMN B; UE A is roaming in PLMN C while UE B is not roaming. + +![Figure 4.2.3-2: Roaming Inter-PLMN 5G System architecture for Proximity-based Services. The diagram illustrates a roaming scenario between PLMN A and PLMN B, with an intermediate PLMN C. UE A is connected to NG-RAN in PLMN C, which is connected to 5GC in PLMN C. UE B is connected to NG-RAN in PLMN B, which is connected to 5GC in PLMN B. Both 5GCs are connected to a central 5G DDNMF. The 5G DDNMF is connected to a ProSe Application Server in the Data Network. The ProSe Application Server is connected to the 5G DDNMF via the PC1 interface. The 5G DDNMF is also connected to the NRF, UDR, AMF, SMF, UPF, PCF, NEF, and UDM in the respective PLMN. The interfaces PC3a, PC5, and Uu are also shown.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram shows a roaming architecture for Proximity-based Services across three PLMNs: PLMN A, PLMN B, and PLMN C. + +- **PLMN B (Top):** Contains UE B connected to NG-RAN via a Uu interface. NG-RAN is connected to a 5GC. The 5GC includes NRF, UDR, AMF, SMF, UPF, 5G DDNMF, PCF, NEF, and UDM. A ProSe Application is connected to UE B via a PC3a interface. + +- **PLMN C (Middle):** Contains UE A connected to NG-RAN via a Uu interface. NG-RAN is connected to a 5GC. The 5GC includes 5G DDNMF and AMF. A ProSe Application is connected to UE A via a PC3a interface. + +- **PLMN A (Bottom):** Contains 5G DDNMF, AMF, NEF, UDM, UPF, NRF, UDR, PCF, and SMF. + +- **Interconnections:** + +- UE B (PC3a) connects to 5G DDNMF in PLMN B. +- UE A (PC3a) connects to 5G DDNMF in PLMN C. +- 5G DDNMF in PLMN B connects to 5G DDNMF in PLMN C via a PC5 interface. +- 5G DDNMF in PLMN C connects to 5G DDNMF in PLMN A via a PC3a interface. +- Both 5G DDNMF in PLMN B and PLMN C connect to a central ProSe Application Server in the Data Network via a PC1 interface. + +Figure 4.2.3-2: Roaming Inter-PLMN 5G System architecture for Proximity-based Services. The diagram illustrates a roaming scenario between PLMN A and PLMN B, with an intermediate PLMN C. UE A is connected to NG-RAN in PLMN C, which is connected to 5GC in PLMN C. UE B is connected to NG-RAN in PLMN B, which is connected to 5GC in PLMN B. Both 5GCs are connected to a central 5G DDNMF. The 5G DDNMF is connected to a ProSe Application Server in the Data Network. The ProSe Application Server is connected to the 5G DDNMF via the PC1 interface. The 5G DDNMF is also connected to the NRF, UDR, AMF, SMF, UPF, PCF, NEF, and UDM in the respective PLMN. The interfaces PC3a, PC5, and Uu are also shown. + +Figure 4.2.3-2: Roaming Inter-PLMN 5G System architecture for Proximity-based Services + +#### 4.2.4 AF-based service parameter provisioning + +The 5G System provides NEF services to enable communication between NFs in the PLMN and a ProSe Application Server. Figure 4.2.4-1 shows the high level view of AF-based service parameter provisioning for 5G ProSe communications. The ProSe Application Server may provide ProSe service parameters to the PLMN via NEF. The NEF stores the ProSe service parameters in the UDR. + +![Figure 4.2.4-1: 5G System architecture for AF-based service parameter provisioning for 5G ProSe communications. The diagram shows a vertical stack of network elements: ProSe Application Server (top), 5GC (containing NEF, UDR, PCF, AMF), 5G-AN, UE, and ProSe Application (bottom). Reference points are labeled: N33 between ProSe Application Server and NEF; N37 between NEF and UDR; N30 between NEF and PCF; N36 between UDR and PCF; N15 between PCF and AMF; N1 between AMF and 5G-AN; N2 between AMF and 5G-AN; Uu between 5G-AN and UE. A long vertical line labeled PC1 connects the ProSe Application Server and the ProSe Application in the UE.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Figure 4.2.4-1: 5G System architecture for AF-based service parameter provisioning for 5G ProSe communications. The diagram shows a vertical stack of network elements: ProSe Application Server (top), 5GC (containing NEF, UDR, PCF, AMF), 5G-AN, UE, and ProSe Application (bottom). Reference points are labeled: N33 between ProSe Application Server and NEF; N37 between NEF and UDR; N30 between NEF and PCF; N36 between UDR and PCF; N15 between PCF and AMF; N1 between AMF and 5G-AN; N2 between AMF and 5G-AN; Uu between 5G-AN and UE. A long vertical line labeled PC1 connects the ProSe Application Server and the ProSe Application in the UE. + +**Figure 4.2.4-1: 5G System architecture for AF-based service parameter provisioning for 5G ProSe communications** + +#### 4.2.5 Reference points + +- PC1:** The reference point between the ProSe application in the UE and in the ProSe Application Server. It is used to define application level signalling requirements. This reference point is not specified in this release of the specification. +- PC3a:** The reference point between the UE and the 5G DDNMF. PC3a relies on 5GC user plane for transport (i.e. an "over IP" reference point). It is used to authorise 5G ProSe Direct Discovery request and perform allocation of ProSe Application Codes / ProSe Restricted Codes corresponding to ProSe Application Identities used for 5G ProSe Direct Discovery. +- PC5:** The reference point between ProSe-enabled UEs used for control and user plane for 5G ProSe Direct Discovery, 5G ProSe Direct Communication and 5G ProSe UE-to-Network Relay. +- PC8:** The reference point between the UE and the 5G ProSe Key Management Function (5G PKMF). The details are defined in TS 33.503 [29]. +- Npc2:** The reference point between the ProSe Application Server and the 5G DDNMF. It is used to define the interaction between ProSe Application Server and 5G DDNMF for 5G ProSe Direct Discovery. +- Npc4:** The reference point between the UDM and 5G DDNMF. It is used to provide subscription information in order to authorise 5G ProSe Direct Discovery request. +- Npc6:** The reference point between the 5G DDNMF in the HPLMN and the 5G DDNMF in a Local PLMN (5G ProSe Direct Discovery). This reference point is used for HPLMN control of ProSe service authorization. +- Npc7:** The reference point between the 5G DDNMF in the HPLMN and the 5G DDNMF in the VPLMN. It is used for HPLMN control of ProSe service authorization. +- Npc8:** The reference point between the PCF and the 5G DDNMF. It is used to define the interactions between the 5G DDNMF and the PCF to e.g. get a PDUID from the PCF. +- Npc9:** The reference point between the 5G PKMF of the 5G ProSe Remote UE and the 5G PKMF of the 5G ProSe UE-to-Network Relay. The details are defined in TS 33.503 [29]. +- Npc10:** The reference point between the 5G PKMF and UDM. The details are specified in TS 33.503 [29]. + +**Npc11:** The reference point between the AUSF and Prose Anchor Function (PAnF). The details are specified in TS 33.503 [29]. + +**Npc12:** The reference point between the PAnF and UDM. The details are specified in TS 33.503 [29]. + +**Npc13:** The reference point between the SMF and PKMF. The details are specified in TS 33.503 [29]. + +**Npc14:** The reference point between the SMF and PAnF. The details are specified in TS 33.503 [29]. + +**NOTE:** Npc2, Npc4, Npc6, Npc7, Npc8, Npc9, Npc10, Npc11, Npc12, Npc13 and Npc14 show the interactions that exist between the NF services in the NFs. These reference points are realised by corresponding NF service-based interfaces and by specifying the identified consumer and producer NF service as well as their interaction in order to realize a particular system procedure. + +## 4.2.6 Service-based interfaces + +**N5g-ddnmf:** Services provided by 5G DDNMF to manage inter-PLMN 5G ProSe Direct Discovery operations. + +**Npkmf:** Service provided by 5G PKMF to support inter-PLMN ProSe security management. The function of Npkmf is defined in TS 33.503 [29]. + +In addition to the relevant services defined in TS 23.501 [4] for the following service-based interfaces, in the case of ProSe Service, the services can be provided by corresponding NF are as follows: + +**Nudm:** Services provided by UDM are used to get 5G ProSe Service related subscription information to the AMF during Initial Registration procedure or UE Configuration Update (UCU) procedure to inform the AMF the subscription information has changed and to provide ProSe Service related subscription information to 5G DDNMF for the authorisation of 5G ProSe Direct Discovery requests. The subscription information is described in TS 23.502 [5]. Services provided by UDM may also be used by the 5G PKMF for relay service authorisation, see TS 33.503 [29]. + +**Npcf:** Services provided by H-PCF are used to provide 5G ProSe Service related parameters to V-PCF for the UE and NG-RAN in the roaming case and to enable the 5G DDNMF to get a PDUID or be notified of PDUID change. + +**Nudr:** Services provided by UDR are used to notify the PCF and the UDM of the update of the 5G ProSe Service related information as described in TS 23.502 [5]. + +**Nnef:** Services provided by NEF are used by the ProSe Application Server to update 5G ProSe Service related information of 5GC. + +**Namf:** Services provided by AMF are consumed by PCF to provide the 5G ProSe Service related parameters for the UE and the NG-RAN to the AMF and to enable the AMF create or update the UE context related to 5G ProSe service. + +**Nnrf:** Services provided by NRF are used to discover the PCF that supports 5G ProSe service and for 5G DDNMF in HPLMN to discover other 5G DDNMFs in VPLMN or local PLMN. + +**Naf:** Services provided by AF are consumed by the DDNMF to request authorization for Discovery Request. The AF may update the authorization information to revoke the Restricted ProSe Direct Discovery permission. + +## 4.2.7 5G ProSe UE-to-Network Relay reference architecture + +### 4.2.7.1 5G ProSe Layer-3 UE-to-Network Relay reference architecture + +The following figure 4.2.7.1-1 shows the high level reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. In this figure, the 5G ProSe Layer-3 UE-to-Network Relay may be in the HPLMN or a VPLMN. + +![Figure 4.2.7.1-1: Reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. The diagram shows a linear flow: Remote UE connected to a Layer 3 UE-to-Network Relay via a PC5 interface. The Layer 3 UE-to-Network Relay is connected to an NG-RAN via a Uu interface. The NG-RAN is connected to a 5GC (5G Core) cloud, which is then connected to a Data Network via an N6 interface.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 4.2.7.1-1: Reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. The diagram shows a linear flow: Remote UE connected to a Layer 3 UE-to-Network Relay via a PC5 interface. The Layer 3 UE-to-Network Relay is connected to an NG-RAN via a Uu interface. The NG-RAN is connected to a 5GC (5G Core) cloud, which is then connected to a Data Network via an N6 interface. + +**Figure 4.2.7.1-1: Reference architecture for 5G ProSe Layer-3 UE-to-Network Relay** + +The following figure 4.2.7.1-2 shows the non-roaming reference architecture for 5G ProSe Layer-3 UE-to-Network Relay when N3IWF is supported. In this figure, the PLMN A and PLMN B may be the same or different. When the 5G ProSe Layer-3 Remote UE may connect to NG-RAN directly to access PLMN B and in that case it would take the role of UE in the figure. The N3IWF may be connected to Relay UE UPF via a Data Network. + +![Figure 4.2.7.1-2: Non-roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support. This complex diagram shows two PLMNs, PLMN A and PLMN B, separated by a dashed line. In PLMN B (top), a UE connects to an NG-RAN (Uu), which connects to a Remote UE AMF (N2) and a Remote UE SMF (N3). The Remote UE AMF connects to a 5GC containing UDM, UDR, and PCF. The Remote UE SMF connects to a Remote UE UPF (N4) and an N3IWF (N3). The Remote UE UPF connects to a Data Network (N6). The N3IWF connects to a Relay UE UPF in PLMN A (N6) and to a Data Network (N3Wu). In PLMN A (bottom), a Remote UE connects to an L3 UE-to-Network Relay (PC5), which connects to an NG-RAN (Uu). The NG-RAN connects to a Relay UE AMF (N2) and a Relay UE UPF (N3). The Relay UE AMF connects to a 5GC containing UDM, UDR, and PCF. The Relay UE UPF connects to a Data Network (N6).](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +Figure 4.2.7.1-2: Non-roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support. This complex diagram shows two PLMNs, PLMN A and PLMN B, separated by a dashed line. In PLMN B (top), a UE connects to an NG-RAN (Uu), which connects to a Remote UE AMF (N2) and a Remote UE SMF (N3). The Remote UE AMF connects to a 5GC containing UDM, UDR, and PCF. The Remote UE SMF connects to a Remote UE UPF (N4) and an N3IWF (N3). The Remote UE UPF connects to a Data Network (N6). The N3IWF connects to a Relay UE UPF in PLMN A (N6) and to a Data Network (N3Wu). In PLMN A (bottom), a Remote UE connects to an L3 UE-to-Network Relay (PC5), which connects to an NG-RAN (Uu). The NG-RAN connects to a Relay UE AMF (N2) and a Relay UE UPF (N3). The Relay UE AMF connects to a 5GC containing UDM, UDR, and PCF. The Relay UE UPF connects to a Data Network (N6). + +**Figure 4.2.7.1-2: Non-roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support** + +The following figure 4.2.7.1-3 shows the roaming reference architecture for 5G ProSe Layer-3 UE-to-Network Relay. In this figure, the PLMN A and PLMN B may be the same or different and/or the PLMN A and PLMN C may be the same or different. The N3IWF may be connected to Relay UE UPF via a Data Network. + +![Roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates a roaming architecture involving three Public Land Mobile Networks (PLMNs): PLMN A, PLMN B, and PLMN C. + +- Top Section (PLMN B):** Shows a UE connected via Uu interface to an NG-RAN. The NG-RAN connects to a 5GC containing Remote UE AMF, Remote UE SMF, UDM, UDR, and PCF. It also connects to an N3IWF via NWu and N3 interfaces. The N3IWF connects to a Remote UE UPF, which connects to a Data Network via N6. +- Middle Section (PLMN A):** Shows a Remote UE connected via PC5 to an L3 UE-to-Network Relay. The Relay connects via Uu to an NG-RAN. This NG-RAN connects to a Relay UE UPF. The Relay UE UPF connects to a Data Network (N6) and is controlled by a Relay UE SMF and Relay UE AMF in a 5GC that includes UDM, UDR, and V-PCF. +- Bottom Section (PLMN C):** Represents the Home PLMN for the relay. It contains a 5GC with Relay UE SMF, UDM, UDR, and H-PCF. A Relay UE UPF in this PLMN connects to a Data Network via N6. +- Interconnections:** Various reference points (N2, N3, N4, N6, N9) connect the entities across the PLMN boundaries. + +Roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support + +**Figure 4.2.7.1-3: Roaming architecture model for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support** + +#### 4.2.7.2 5G ProSe Layer-2 UE-to-Network Relay reference architecture + +Figure 4.2.7.2-1 shows the 5G ProSe Layer-2 UE-to-Network Relay reference architecture. The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay may be served by the same or different PLMNs. If the serving PLMNs of the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay are different then NG-RAN is shared by the serving PLMNs, see the 5G MOCN architecture in clause 5.18 of TS 23.501 [4]. + +![Figure 4.2.7.2-1: 5G ProSe Layer-2 UE-to-Network Relay reference architecture. The diagram shows a Remote UE connected to a Layer-2 ProSe UE-to-Network Relay via a PC5 interface. The Relay is connected to an NG-RAN via a Uu interface. The NG-RAN is connected to a Remote UE AMF via an N2 interface and to a Relay UE AMF via an N2 interface. The Remote UE AMF is connected to a Remote UE SMF via an N11 interface. The Remote UE SMF is connected to a Remote UE UPF via an N4 interface. The Remote UE UPF is connected to a Data Network via an N6 interface. The Relay UE AMF is connected to a Relay UE SMF via an N11 interface. The Relay UE SMF is connected to a Relay UE UPF via an N4 interface. The Relay UE UPF is connected to a Data Network via an N6 interface. The NG-RAN is also connected to the Data Network via an N3 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via a Uu interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N1 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N3 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N2 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N11 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N4 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N6 interface.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Figure 4.2.7.2-1: 5G ProSe Layer-2 UE-to-Network Relay reference architecture. The diagram shows a Remote UE connected to a Layer-2 ProSe UE-to-Network Relay via a PC5 interface. The Relay is connected to an NG-RAN via a Uu interface. The NG-RAN is connected to a Remote UE AMF via an N2 interface and to a Relay UE AMF via an N2 interface. The Remote UE AMF is connected to a Remote UE SMF via an N11 interface. The Remote UE SMF is connected to a Remote UE UPF via an N4 interface. The Remote UE UPF is connected to a Data Network via an N6 interface. The Relay UE AMF is connected to a Relay UE SMF via an N11 interface. The Relay UE SMF is connected to a Relay UE UPF via an N4 interface. The Relay UE UPF is connected to a Data Network via an N6 interface. The NG-RAN is also connected to the Data Network via an N3 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via a Uu interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N1 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N3 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N2 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N11 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N4 interface. The Remote UE and the Relay UE are both connected to the NG-RAN via an N6 interface. + +**Figure 4.2.7.2-1: 5G ProSe Layer-2 UE-to-Network Relay reference architecture** + +NOTE 1: Uu between the 5G ProSe Layer-2 Remote UE and NG-RAN consists of RRC, SDAP and PDCP. + +NOTE 2: The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay are served by the same NG-RAN. The Core Network entities (e.g., AMF, SMF, UPF) serving the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay can be the same or different. + +## 4.2.8 5G ProSe UE-to-UE Relay reference architecture + +Figure 4.2.8-1 shows the Layer-2 and Layer-3 5G ProSe UE-to-UE Relay reference architecture. The 5G ProSe End UEs communicate with each other via a 5G ProSe UE-to-UE Relay. + +![Figure 4.2.8-1: Reference architecture for 5G ProSe UE-to-UE Relay. The diagram shows a 5G ProSe End UE connected to a 5G ProSe UE-to-UE Relay via a PC5 interface. The 5G ProSe UE-to-UE Relay is connected to another 5G ProSe End UE via a PC5 interface.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +Figure 4.2.8-1: Reference architecture for 5G ProSe UE-to-UE Relay. The diagram shows a 5G ProSe End UE connected to a 5G ProSe UE-to-UE Relay via a PC5 interface. The 5G ProSe UE-to-UE Relay is connected to another 5G ProSe End UE via a PC5 interface. + +**Figure 4.2.8-1: Reference architecture for 5G ProSe UE-to-UE Relay** + +Each 5G ProSe End UE and the 5G ProSe UE-to-UE Relay may have subscriptions from the same PLMN or different PLMNs. + +## 4.3 Functional Entities + +### 4.3.1 UE + +Any 5G ProSe-enabled UE may support the following functions: + +- Exchange of information for 5G ProSe Direct Discovery between 5G ProSe-enabled UE and the 5G DDNMF over PC3a reference point. +- Procedures for 5G ProSe Direct Discovery of other 5G ProSe-enabled UEs over PC5 reference point. +- Procedures for 5G ProSe Direct Communication over PC5 reference point, including Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication. +- Procedures to act as a 5G ProSe Layer-2 UE-to-Network Relay. +- Procedures to act as a 5G ProSe Layer-3 UE-to-Network Relay. +- Procedures to act as a 5G ProSe Layer-2 Remote UE. +- Procedures to act as a 5G ProSe Layer-3 Remote UE. +- Procedures to act as a 5G ProSe Layer-2 UE-to-UE Relay. + +- Procedures to act as a 5G ProSe Layer-3 UE-to-UE Relay. +- Procedures to act as a 5G ProSe Layer-2 End UE. +- Procedures to act as a 5G ProSe Layer-3 End UE. +- Procedures for communication path switching between PC5 and Uu reference points. +- Procedures for Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay. +- Indicating UE Policy Provisioning Request in UE Policy Container for UE triggered 5G ProSe Policy provisioning, which requests one or multiple types of policies/parameters as listed below: + - Policy/parameters for 5G ProSe Direct Discovery; + - Policy/parameters for 5G ProSe Direct Communication; + - Policy/parameters for 5G ProSe Layer-2 Remote UE; + - Policy/parameters for 5G ProSe Layer-3 Remote UE; + - Policy/parameters for 5G ProSe Layer-2 UE-to-Network Relay; + - Policy/parameters for 5G ProSe Layer-3 UE-to-Network Relay; + - Policy/parameters for 5G ProSe Layer-2 End UE; + - Policy/parameters for 5G ProSe Layer-3 End UE; + - Policy/parameters for 5G ProSe Layer-2 UE-to-UE Relay; + - Policy/parameters for 5G ProSe Layer-3 UE-to-UE Relay. +- Receiving the 5G ProSe Policy from 5GC over N1 reference point. +- Configuration of parameters for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay (e.g. including IP addresses, ProSe Layer-2 Group IDs, see clause 5.1) and 5G ProSe UE-to-UE Relay. These parameters can be pre-configured in the UE, or, if in coverage, provisioned or updated by signalling over the N1 reference point from the PCF in the HPLMN or over PC1 reference point from the ProSe Application Server. +- Reporting the following capabilities to 5GC over the N1 reference point: + - 5G ProSe Capability. + +## 4.3.2 5G DDNMF + +### 4.3.2.1 General + +The 5G DDNMF is the logical function handling network related actions required for dynamic 5G ProSe Direct Discovery. In this version of the specification, it is assumed that there is only one logical 5G DDNMF in each PLMN that supports 5G ProSe Direct Discovery service. + +NOTE: If multiple 5G DDNMFs are deployed within the same PLMN (e.g., for load reasons), the method to locate the 5G DDNMF that has allocated a specific ProSe Application Code or ProSe Restricted Code (e.g. through a database lookup, etc.) is not defined in this version of the specification. + +The 5G DDNMF interacts with the 5G ProSe-enabled UE using procedures over PC3a reference point defined in clause 6.3.1 to allocate and resolve the mapping of ProSe Applications IDs and ProSe Application Codes used in 5G ProSe Direct Discovery. It uses ProSe related subscriber data stored in UDM for the authorisation of each discovery request. It also provides the UE with the necessary security material in order to protect discovery messages transmitted over the air. In restricted 5G ProSe Direct Discovery, it also interacts with the Application Server via Npc2 reference points or with other 5G DDNMFs via Npc6/Npc7 reference points for the authorization of the discovery requests. + +The 5G ProSe-enabled UE use procedure defined in clause 4.3.2.2 to discovery the 5G DDNMF in the HPLMN. Based on the UE Local Configuration or URSP as defined in TS 23.503 [9], an existing PDU session is selected or a new PDU session is established, to carry the control signalling between the UE and the 5G DDNMF in the HPLMN. + +The 5G DDNMF provides the necessary charging functionality or charging information for the usage of 5G ProSe Direct Discovery and/or ProSe Direct Communication to interact with CHF or for the provision to CEF. + +The 5G DDNMF in the HPLMN may interact with the 5G DDNMF in a VPLMN or Local PLMN in order to manage the 5G ProSe Direct Discovery service. + +The 5G DDNMF gets the address of the PCF for the UE from the BSF. + +The 5G DDNMF gets the PDUID from the PCF and subscribes to notifications on Change of PDUID. + +#### 4.3.2.2 5G DDNMF Discovery + +The 5G DDNMF of HPLMN is discovered through interaction with the Domain Name Service function. The UE may have the 5G DDNMF address in the Home PLMN (either as a FQDN or an IP address) pre-configured or provisioned as specified in clause 5.1.2.1. If it is not pre-configured or provisioned then the UE self-constructs the FQDN for it using e.g. the PLMN ID of the HPLMN. + +The 5G DDNMF in the HPLMN uses the NRF to discovery other 5G DDNMFs in a VPLMN or local PLMN. + +#### 4.3.3 PCF + +In addition to the functions defined in TS 23.501 [4] and TS 23.503 [9], the PCF includes functions to provision the UE with necessary policies and parameters to use 5G ProSe services, as part of the UE ProSe Policy information as defined in TS 23.503 [9] clause 4.2.2: + +- PC5 usage reporting configuration. +- Authorization policy and parameters for 5G ProSe Direct Discovery and Communication. +- Authorization policy and parameters for 5G ProSe UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 Remote UE, as 5G ProSe Layer-3 Remote UE, as 5G ProSe Layer-2 UE-to-Network Relay, as 5G ProSe Layer-3 UE-to-Network Relay). +- PDUID allocation with its validity timer. +- Authorization policy and parameters for 5G ProSe UE-to-UE Relay Discovery and Communication. + +The PCF may update the 5G ProSe policy and parameters to the UE under certain conditions. + +When receiving the 5G ProSe Capability in Npcf\_UEPolicyControl\_Create Request from the AMF or when receiving the updated subscription data from UDR, the PCF generates the PC5 QoS parameters used by NG-RAN corresponding to a UE as defined in clause 5.4.2 of TS 23.287 [2]. + +#### 4.3.4 AMF + +In addition to the functions defined in TS 23.501 [4], the AMF performs the following functions: + +- Select a PCF supporting 5G ProSe Policy/Parameter provisioning based on indication of 5G ProSe Capability as part of the "5GMM capability" in the Registration Request. +- Store the 5G ProSe Capability. +- Forward the 5G ProSe Capability to PCF in Npcf\_UEPolicyControl\_Create Request. +- Obtain from UDM the subscription information related to 5G ProSe and store them as part of the UE context data. +- Obtain PC5 QoS parameters from the PCF and store them as part of the UE context data. +- Provision the NG-RAN with indication about the UE authorization status about the following: + +- 5G ProSe Direct Discovery and 5G ProSe Direct Communication (i.e. as 5G ProSe-enabled UE for ProSe Direct Discovery, as 5G ProSe-enabled UE for ProSe Direct Communication); +- 5G ProSe UE-to-Network Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 Remote UE, as 5G ProSe Layer-2 UE-to-Network Relay, as 5G ProSe Layer-3 UE-to-Network Relay); +- Multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE; +- 5G ProSe UE-to-UE Relay Discovery and Communication (i.e. as 5G ProSe Layer-2 End UE, as 5G ProSe Layer-2 UE-to-UE Relay). +- Provision the NG-RAN with PC5 QoS parameters related to 5G ProSe Direct Communication. +- Optionally support security procedures over Control Plane for 5G ProSe UE-to-Network relaying as defined in TS 33.503 [29]. + +#### 4.3.5 UDM + +In addition to the functions defined in TS 23.501 [4], the UDM performs the following functions: + +- Subscription management for 5G ProSe Direct Discovery and Communication. +- Subscription management for 5G ProSe UE-to-Network Relay Discovery and Communication. +- Subscription management for multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE. +- Subscription management for 5G ProSe UE-to-UE Relay Discovery and Communication. + +#### 4.3.6 UDR + +In addition to the functions defined in TS 23.501 [4], the UDR performs the following functions: + +- Stores a path preference for ProSe services provided by the AF. +- Stores ProSe service parameters. + +#### 4.3.7 NRF + +In addition to the functions defined in TS 23.501 [4], the NRF performs the following functions: + +- PCF discovery by considering 5G ProSe Capability. +- 5G DDNMF Discovery. + +Similar procedure can be used for 5G DDNMF discovery across PLMNs as specified in clause 4.17.5 of TS 23.502 [5] with the difference as below: + +- The serving PLMN is replaced by home PLMN and home PLMN is replaced by local PLMN or serving PLMN. + +#### 4.3.8 ProSe Application Server + +The ProSe Application Server supports the following functionalities. + +For 5G ProSe Direct Discovery: + +- Maintains permission information for the restricted 5G ProSe Direct Discovery using RPAUIDs; +- Storage of ProSe Discovery UE IDs and metadata; +- Mapping of RPAUID and PDUID for restricted 5G ProSe Direct Discovery; +- Provisioning parameters for Group Member Discovery to UE. + +- Interaction with 5G DDNMF for 5G ProSe Direct Discovery, including: + - Allocation of the ProSe Restricted Code Suffix pool, if restricted Direct Discovery with application-controlled extension is used; + - Allocation of the mask(s) for ProSe Restricted Code Suffix, if restricted Direct Discovery with application-controlled extension is used. + +For 5G ProSe Direct Communication: + +- Provisioning a path preference for 5G ProSe Services to UDR; +- Provisioning parameters for 5G ProSe Direct Communication to UE. + +For 5G ProSe UE-to-Network Relay service: + +- Provisioning parameters for 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communication to UDR. + +For 5G ProSe UE-to-UE Relay service: + +- Provisioning parameters for 5G ProSe UE-to-UE Relay Discovery and 5G ProSe UE-to-UE Relay Communication to UDR. + +### 4.3.9 5G ProSe UE-to-Network Relay + +#### 4.3.9.1 General + +Both 5G ProSe Layer-2 and Layer-3 UE-to-Network Relay entity provides the relaying functionality to support connectivity to the network for 5G ProSe Remote UEs. It can be used for both public safety services and commercial services (e.g. interactive service). + +Both 5G ProSe Layer-2 and Layer-3 UE-to-Network Relay supports the following functions to enable connectivity to the network: + +- 5G ProSe UE-to-Network Relay Discovery service as defined in clause 6.3.2.3, to allow discovery by the 5G ProSe Remote UE; +- access the 5GS as a UE as defined in TS 23.501 [4] with the enhancements as specified in clauses 6.2 and 6.6; +- relays unicast traffic (uplink and downlink) between the 5G ProSe Remote UE and the network, supporting IP, Ethernet or Unstructured traffic type. + +NOTE: Relaying MBS traffic to a 5G ProSe Remote UE by a 5G ProSe UE-to-Network Relay is not supported in this release of the specification. + +#### 4.3.9.2 5G ProSe Layer-3 UE-to-Network Relay + +In addition to the common 5G ProSe UE-to-Network Relay functions defined in clause 4.3.9.1, 5G ProSe Layer-3 UE-to-Network Relay supports the following functions to enable connectivity to the network: + +- 5G ProSe Direct Communication via 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 6.5.1, for the communication with the 5G ProSe Layer-3 Remote UEs for the relay operations; +- end-to-end QoS treatment for the 5G ProSe Layer-3 Remote UE's traffic without N3IWF as defined in clause 5.6.2.1 and when accessing via an N3IWF as defined in clause 5.6.2.2; +- IP address management for the 5G ProSe Layer-3 Remote UE as defined in clause 5.5.1.3 in case the 5G ProSe Layer-3 Remote UE uses IP traffic type. +- Emergency PDU Session establishment for 5G ProSe Layer-3 Remote UE via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF support. + +NOTE: For emergency service via N3IWF, see clause 5.4.4.3. + +#### 4.3.9.3 5G ProSe Layer-2 UE-to-Network Relay + +In addition to the common 5G ProSe UE-to-Network Relay functions defined in clause 4.3.9.1, 5G ProSe Layer-2 UE-to-Network Relay supports the following functions to enable connectivity to the network: + +- 5G ProSe Direct Communication via 5G ProSe Layer-2 UE-to-Network Relay as specified in clause 6.5.2, for the communication with the 5G ProSe Layer-2 Remote UEs for the relay operations; +- QoS handling for 5G ProSe Layer-2 UE-to-Network Relay and end-to-end QoS treatment as defined in clause 5.6.2.3. +- For a 5G ProSe Layer-2 UE-to-Network Relay to participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message), the serving NG-RAN support of emergency services is required as the Layer-2 Remote UE may select a different PLMN from the Layer-2 Relay. + +#### 4.3.10 SMF + +In addition to the functions defined in TS 23.501 [4], the SMF supports the following function: + +- Receiving 5G ProSe Layer-3 Remote UE report and maintaining the information of 5G ProSe Layer-3 Remote UE(s) handled by a 5G ProSe Layer-3 UE-to-Network Relay in the 5G ProSe Layer-3 UE-to-Network Relay's SM context for the PDU Session associated with the relay. + +#### 4.3.11 NEF + +In addition to the functions defined in TS 23.501 [4], the NEF supports the following: + +- To enable AFs to provide service specific information to the 3GPP network, the NEF supports additional service parameters for ProSe policy as specified in clause 6.2.5. + +#### 4.3.12 5G ProSe UE-to-UE Relay + +##### 4.3.12.1 General + +Both 5G ProSe Layer-2 and Layer-3 UE-to-UE Relay provides the relaying functionality to support connectivity between 5G ProSe End UEs. 5G ProSe UE-to-UE Relay can be used for both public safety services and commercial services (e.g. interactive service). + +Both 5G ProSe Layer-2 and Layer-3 UE-to-UE Relay supports the following functions to enable connectivity between 5G ProSe End UEs: + +- 5G ProSe UE-to-UE Relay Discovery service as defined in clause 6.3.2.4, to allow discovery by the 5G ProSe End UE; +- 5G ProSe Discovery integrated into PC5 unicast link establishment as specified in clause 6.7.3; +- Access 5GS as a UE as defined in TS 23.501 [4] with the enhancements as specified in clauses 6.2; +- Relay unicast traffic between the 5G ProSe End UEs, supporting IP, Ethernet or Unstructured traffic type. + +NOTE: Relaying groupcast and broadcast traffic to a 5G ProSe End UE by a 5G ProSe UE-to-UE Relay is not supported in this release of the specification. + +##### 4.3.12.2 5G ProSe Layer-3 UE-to-UE Relay + +In addition to the common 5G ProSe UE-to-UE Relay functionality defined in clause 4.3.12.1, a 5G ProSe Layer-3 UE-to-UE Relay supports the following functions: + +- 5G ProSe Direct Communication via 5G ProSe Layer-3 UE-to-UE Relay as specified in clause 6.7.1, for the communication between 5G ProSe Layer-3 End UEs for relay operations; + +- QoS handling and end-to-end QoS treatment for the 5G ProSe Layer-3 End UE's traffic as defined in clause 5.6.3.1; +- IP address management for the 5G ProSe Layer-3 End UE as defined in clause 5.5.1.4 when the 5G ProSe Layer-3 End UE uses IP traffic type; +- 5G ProSe UE-to-UE Relay reselection as specified in clause 6.7.4.3. + +#### 4.3.12.3 5G ProSe Layer-2 UE-to-UE Relay + +In addition to the common 5G ProSe UE-to-UE Relay functions defined in clause 4.3.12.1, 5G ProSe Layer-2 UE-to-UE Relay supports the following functions: + +- 5G ProSe Direct Communication via 5G ProSe Layer-2 UE-to-UE Relay as specified in clause 6.7.2, for the communication between 5G ProSe Layer-2 End UEs for relay operations; +- QoS handling and end-to-end QoS treatment for 5G ProSe Layer-2 End UE's traffic as defined in clause 5.6.3.2; +- 5G ProSe UE-to-UE Relay reselection as specified in clause 6.7.4.2. + +--- + +## 5 High level functionality and features + +### 5.1 Authorization and Provisioning for ProSe service + +#### 5.1.1 General + +In 5GS, the parameters for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay and 5G ProSe UE-to-UE Relay services may be made available to the UE in following ways: + +- provisioned in the ME; or +- configured in the UICC; or +- provisioned in the ME and configured in the UICC; or +- provided or updated by the ProSe Application Server via PCF and/or PC1 reference point; or +- provided or updated by the PCF to the UE. + +If the same parameters described in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1 are provided by different sources, the UE shall consider them in the following priority order: + +- provided or updated by the PCF (including parameters determined by the PCF itself and parameters provided by the ProSe Application Server to the PCF as specified in clause 6.2.5); +- provided or updated by the ProSe Application Server via PC1 reference point; +- configured in the UICC; +- provisioned in the ME. + +The parameters provided or updated by the ProSe Application Server via PC1 reference point may need to be complemented with configuration data from other sources listed above. + +NOTE: The ProSe Application Server can provision the same ProSe parameters via 5GC as specified in clause 6.2.5 or directly to the UE via PC1 reference point and can revoke (e.g. delete) the ProSe parameters via 5GC as specified in clause 6.2.5 in order for the provisioning via PC1 reference point to take effect. + +The basic principles of service authorization and provisioning for 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay and 5G ProSe UE-to-UE Relay services are as follows: + +- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorized to use 5G ProSe Direct Discovery. +- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to use 5G ProSe Direct Communication. +- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe UE-to-Network Relay. Authorisation for 5G ProSe Layer-2 UE-to-Network Relay and 5G ProSe Layer-3 UE-to-Network Relay are independent of each other. +- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to access 5GC via 5G ProSe UE-to-Network Relay (i.e. to act as 5G ProSe Remote UE). Authorisation to access via 5G ProSe Layer-2 UE-to-Network Relay and via 5G ProSe Layer-3 UE-to-Network Relay are independent of each other. +- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to act as 5G ProSe UE-to-UE Relay. Authorisation for 5G ProSe Layer-2 UE-to-UE Relay and 5G ProSe Layer-3 UE-to-UE Relay are independent of each other. +- The PCF in the HPLMN may configure a list of PLMNs where the UE is authorised to access 5G ProSe UE-to-UE Relay (i.e. to act as 5G ProSe End UE). Authorisation to access via 5G ProSe Layer-2 UE-to-UE Relay and via 5G ProSe Layer-3 UE-to-UE Relay are independent of each other. +- The PCF in the HPLMN merges authorization information from home and other PLMNs and provides the UE with the final authorization information. +- The PCF in the VPLMN or HPLMN may revoke the authorization (via H-PCF when roaming) at any time by using the UE Configuration Update procedure for transparent UE Policy delivery procedure defined in clause 4.2.4.3 of TS 23.502 [5]. +- The ProSe Policy/parameters provisioning to UE is controlled by the PCF and may be triggered by UE. The PCF provisions one or more of the following ProSe Policy/parameters: + - ProSe Policy/parameters for 5G ProSe Direct Discovery as specified in clause 5.1.2.1; + - ProSe Policy/parameters for 5G ProSe Direct Communications as specified in clause 5.1.3.1; + - ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 UE-to-Network Relay as specified in clause 5.1.4.1; + - ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 Remote UE as specified in clause 5.1.4.1. + - ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 UE-to-UE Relay as specified in clause 5.1.5.1. + - ProSe Policy/parameters for 5G ProSe Layer-2 and/or Layer-3 End UE as specified in clause 5.1.5.1. +- The PCF includes the 5G ProSe Policy/parameters in a Policy Section identified by a Policy Section Identifier (PSI) as specified in clause 6.1.2.2.2 of TS 23.503 [9]. + +In addition to the above, ProSe usage reporting configuration and rules for charging can be (pre)configured in the UE or provided by the PCF. + +In addition to the above, the path selection policy can be (pre)configured in the UE or provided by the PCF as defined in clause 5.11. A path preference for ProSe Services can be provided by ProSe Application Server to UDR and may be used by PCF for path selection policy generation and update. + +When a 5G ProSe Layer-3 Remote UE is using a 5G ProSe Layer-3 UE-to-Network Relay without involving N3IWF, the PCF based provisioning and update of 5G ProSe Policy/parameters to the 5G ProSe Layer-3 Remote UE are not supported. + +### 5.1.1a General principles for applying policy/parameters + +For services (i.e. 5G ProSe Direct Discovery, 5G ProSe Direct Communication, 5G ProSe UE-to-Network Relay discovery, 5G ProSe UE-to-Network Relay communication, 5G ProSe UE-to-UE Relay discovery and 5G ProSe UE-to-UE Relay communication) over PC5 reference point, the operator may pre-configure the UEs with the required + +provisioning parameters for the service, without the need for the UEs to connect to the 5GC to get this initial configuration. The following apply: + +- The provisioning parameters for the service could be from different sources and their priorities are described in clause 5.1.1. +- The ME provisioning parameters shall not be erased when a USIM is deselected or replaced. +- The UE shall use radio resources for the service as follows: + - While a UE has a serving cell and is camped on a cell and the UE intends to use for 5G ProSe the radio resources (i.e. carrier frequency) operated by this cell, then the UE shall use the radio resource description indicated by this cell the UE is camped on and ignore any radio resource description of the same radio resource provisioned in the ME or the UICC. If the cell does not provide radio resources for ProSe, the UE shall not perform ProSe message transmission and reception on radio resources operated by this cell. The UE is allowed to perform the service with another UE not served by the same PLMN; + - If the UE intends to use "operator-managed" radio resources (i.e. carrier frequency) for 5G ProSe that are not operated by the UE's serving cell, as specified in the related Policy/Parameter provisioning, or if the UE is out of coverage, the UE shall search for a cell in any PLMN that is operating the provisioned radio resources (i.e. carrier frequency) as defined in TS 38.300 [12] and TS 38.304 [13]; and: + - If the UE finds such a cell in the registered PLMN or a PLMN equivalent to the registered PLMN and authorization for the service to this PLMN is confirmed, the UE shall use the radio resource description indicated by that cell. If that cell does not provide radio resources for ProSe, the UE shall not perform ProSe message transmission and reception on those radio resources; + - If the UE finds such a cell but not in the registered PLMN or a PLMN equivalent to the registered PLMN and that cell belongs to a PLMN authorized for the service and provides radio resources for ProSe then the UE shall perform PLMN selection triggered by the service as defined in TS 23.122 [14]; + - If the UE finds such cell but not in a PLMN authorized for the service the UE shall not use the service; + - If the UE does not find any such cell in any PLMN, then the UE shall consider itself "not served by NG-RAN" and use radio resources provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize the service, then the UE is not authorized to transmit; + - The UE is allowed to use "operator-managed" radio resources (i.e. carrier frequency) provisioned in the ME or the UICC for the service if the UICC indicates it is authorized; + - If the UE intends to use "non-operator-managed" radio resources (i.e. carrier frequency) for 5G ProSe, according to TS 36.331 [15] or TS 38.331 [16] and as specified in clause 5.1.2.1, then the UE shall perform the service using resource provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize the service, then the UE is not authorized to transmit; + +NOTE 1: It is possible for operators to configure UEs (e.g. Public Safety UEs) to use only "operator-managed" radio resources (i.e. carrier frequency) for the service when the UE is "not served by NG-RAN". + +- The UE provisioning shall support setting Geographical Areas; + +NOTE 2: It is possible for a UE to use other radio resources for 5G ProSe based on the Geographical Area instead of those operated by the serving NG-RAN cell, when provisioned in the UE, even if the UE's serving cell offers normal service and the SIBs for NR Sidelink communication defined in TS 38.331 [16] indicates that the service (the service) is available. This is to cover the scenario when e.g. the radio resources used for the service are not owned by the serving network of the UE. + +NOTE 3: When cross-carrier operation is supported, according to TS 36.331 [15] or TS 38.331 [16], a UE can be instructed by its serving cell to perform the service over a different carrier frequency. The UE is still considered as "served by NG-RAN" in this case. + +NOTE 4: The scenario that a cell is detected and the cell does not provide support for the service when the UE attempts to use a carrier frequency configured for the service, is considered a configuration error. Therefore, the UE does not transmit on that frequency to avoid interference to the network. + +- The service is only specified for NR. + +NOTE 5: It is out of scope of the present specification to define how the UE can locate itself in a specific Geographical Area. When the UE is in coverage of a 3GPP RAT, it can for example, use information derived from the serving PLMN. When the UE is not in coverage of a 3GPP RAT, it can use other techniques, e.g. Global Navigation Satellite System (GNSS). User provided location is not a valid input. + +## 5.1.2 Authorization and Provisioning for 5G ProSe Direct Discovery + +### 5.1.2.1 Policy/Parameter provisioning for 5G ProSe Direct Discovery + +The following sets of information for 5G ProSe Direct Discovery over PC5 reference point is provisioned to the UE: + +1) Authorization policy for 5G ProSe Direct Discovery: + +- When the UE is "served by NG-RAN": + - For open 5G ProSe Direct Discovery: + - a) open 5G ProSe Direct Discovery Model A monitoring authorization policy: + - PLMNs in which the UE is authorised to perform 5G ProSe Direct Discovery monitoring. + - b) open 5G ProSe Direct Discovery Model A announcing authorization policy: + - PLMNs in which the UE is authorized to perform announcing. + - For restricted 5G ProSe Direct Discovery: + - a) restricted 5G ProSe Direct Discovery Model A monitoring authorization policy: + - PLMNs in which the UE is authorised to perform restricted 5G ProSe Direct Discovery Model A monitoring. + - b) restricted 5G ProSe Direct Discovery Model A announcing authorization policy: + - PLMNs in which the UE is authorized to perform restricted 5G ProSe Direct Discovery Model A announcing. + - c) restricted 5G ProSe Direct Discovery Model B Discoverer operation authorization policy: + - PLMNs in which the UE is authorized to perform Model B Discoverer operation. + - d) restricted 5G ProSe Direct Discovery Model B Discoveree operation authorization policy: + - PLMNs in which the UE is authorized to perform Model B Discoveree operation. + +NOTE 1: In this specification, [When the UE is "served by NG-RAN"] and [When the UE is "not served by NG-RAN"] have similar meaning as in "served by E-UTRAN" and "not served by E-UTRAN" in TS 23.303 [3], but applied to 5G ProSe Direct discovery/communications over NR PC5 reference point. + +- When the UE is "not served by NG-RAN": + - Indicates whether the UE is authorized to perform 5G ProSe Direct Discovery for Model A and Model B when "not served by NG-RAN". + +NOTE 2: If both Model A and Model B are authorized for 5G ProSe Direct Discovery, it is up to UE and application implementation to select a discovery model or perform both models simultaneously. + +2) Parameters used for 5G ProSe Direct Discovery: + +- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for sending/receiving initial signalling of discovery messages. + +NOTE 3: The same Destination Layer-2 ID for 5G ProSe Direct Discovery can be mapped to more than one ProSe services. + +NOTE 4: The values provisioned for the Destination Layer-2 ID(s) for 5G ProSe Direct Discovery, for Destination Layer-2 ID(s) for 5G ProSe Direct Communication, defined in clause 5.1.3.1, for Destination Layer-2 ID(s) for 5G ProSe UE-to-Network Relay Discovery defined in clause 5.1.4.1 and for Destination Layer-2 ID(s) for 5G ProSe UE-to-UE Relay Discovery defined in clause 5.1.5.1, are different from each other. + +NOTE 5: A "catch all" entry with the lowest priority can be used for the ProSe services that do not have explicit mapping to the Destination Layer-2 ID(s) for sending/receiving initial signalling of discovery messages. + +- Application identifiers to be used for 5G ProSe Direct Discovery over PC5 interface. + +NOTE 6: The Security parameters for 5G ProSe Direct Discovery can be provisioned by 5G DDNMF as defined in TS 33.503 [29]. + +3) Radio parameters when the UE is "not served by NG-RAN": + +- Includes the radio parameters per NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit. + +NOTE 7: Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations. + +- Default PC5 DRX configuration (see TS 38.331 [16]). + +NOTE 8: Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" in clause 5.1.5.2.1 and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery are expected to be aligned for direct and relayed discovery for UE to UE communication. + +4) Restricted ProSe Discovery UE ID for Restricted Direct Discovery: + +- ProSe Discovery UE ID. + +5) Group Member Discovery parameters: + +- For each discovery group that the UE belongs to include the following parameters that enable the UE to perform Group Member Discovery when provided by PCF or provisioned in the ME or configured in the UICC: + - Application Layer Group ID: Identifies an application layer group or a discovery group that the UE belongs to; + - Layer-2 Group ID: layer-2 ID for Application Layer Group ID; + - User Info ID: For Model A, this corresponds to the Announcer Info parameter when the UE is acting as an announcing UE. For Model B, this corresponds to the Discoverer Info in Solicitation messages and the Discoveree Info in Response messages, when the UE is acting as a discoverer or discoveree UE respectively. + +NOTE 9: User Info ID is expected to be assigned uniquely to a user within the discovery group. + +6) Optionally, the 5G DDNMF address (either FQDN or IP address) in the Home PLMN. + +7) Validity timer indicating the expiration time of the Policy/Parameter for 5G ProSe Direct Discovery. + +The above parameter sets bullet 2), bullet 3), bullet 5) and bullet 7) may be provided or updated to the UE by the ProSe Application Server, except for the Security parameters in bullet 2). + +## 5.1.2.2 Principles for applying parameters for 5G ProSe Direct Discovery + +The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Direct Discovery service. + +## 5.1.3 Authorization and Provisioning for 5G ProSe Direct Communication + +### 5.1.3.1 Policy/Parameter provisioning for 5G ProSe Direct Communication + +The following sets of information for 5G ProSe Direct Communications over PC5 reference point is provisioned to the UE: + +1) Authorization policy: + +- When the UE is "served by NG-RAN": + - PLMNs in which the UE is authorized to perform 5G ProSe Direct Communications over PC5 reference point when "served by NG-RAN". +- When the UE is "not served by NG-RAN": + - Indicates whether the UE is authorized to perform 5G ProSe Direct Communications over PC5 reference point when "not served by NG-RAN". + +NOTE 1: In this specification, [When the UE is "served by NG-RAN"] and [When the UE is "not served by NG-RAN"] are relevant to 5G ProSe Direct Communications over NR PC5 reference point. + +2) Groupcast mode 5G ProSe Direct Communication policy/parameters: + +- For each application layer group supported include the parameters that enable the UE to perform Groupcast mode 5G ProSe Direct Communication when provided by PCF or provisioned in the ME or configured in the UICC: + - Application Layer Group ID: Identifies an application layer group that the UE belongs to. + - ProSe Layer-2 Group ID: Destination Layer-2 ID applicable only when the Application Layer Group ID is provided by the application layer + - ProSe Group IP multicast address + - Indication whether the UE should use IPv4 or IPv6 for that group + - For a specific Group configured to operate using IPv4, optionally an IPv4 address to be used by the UE as a source address. If none is provisioned, then the UE shall use Dynamic Configuration of IPv4 Link-Local Addresses RFC 3927 [18] to obtain a link local address for the Group. + +3) Radio parameters when the UE is "not served by NG-RAN": + +- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform ProSe Direct Communications over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit. + +NOTE 2: Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations. + +NOTE 3: Radio parameters for 5G ProSe Direct Communication when the UE is not "served by NG-RAN" in clause 5.1.5.2.1 and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe UE-to-UE Relay communication are expected to be aligned for direct and relayed UE to UE communication. + +4) Policy/parameters related to privacy: + +- The list of ProSe services (i.e. ProSe identifiers) with Geographical Area(s) that require privacy support. +- A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required. + +5) Policy/parameters when NR PC5 is selected: + +- The mapping of ProSe services (i.e. ProSe identifiers) to radio frequencies with Geographical Area(s). + +- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for broadcast. +- The mapping of ProSe services (i.e. ProSe identifiers) to Destination Layer-2 ID(s) for groupcast. +- The mapping of ProSe services (i.e. ProSe identifiers) to default Destination Layer-2 ID(s) for initial signalling to establish unicast connection. + +NOTE 4: The same default Destination Layer-2 ID for unicast initial signalling can be mapped to more than one ProSe service. In the case where different ProSe services are mapped to distinct default Destination Layer-2 IDs, when the UE intends to establish a single unicast link that can be used for more than one ProSe service, the UE can select any of the default Destination Layer-2 IDs to use for the initial signalling. + +NOTE 5: Security policies for Unicast mode 5G ProSe Direct Communication can be provisioned by PCF as defined in TS 33.503 [29]. + +- The mapping of ProSe services (i.e. ProSe identifiers) to PC5 QoS parameters defined in clause 5.6.1 (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.). +- The mapping of ProSe services (i.e. ProSe identifiers) to the corresponding NR Tx Profiles for broadcast and groupcast (see TS 38.300 [12] and TS 38.331 [16] for further information). + +NOTE 6: A "catch all" entry with the lowest priority in each above mapping can be used for the ProSe services that do not have explicit policy/parameters mapping above. + +- AS layer configurations (see TS 38.331 [16]), i.e. the mapping of PC5 QoS profile(s) to radio bearer(s), when the UE is "not served by NG-RAN". + - The PC5 QoS profile contains PC5 QoS parameters described in clause 5.4.2 of TS 23.287 [2] and value for the QoS characteristics regarding Priority Level, Averaging Window, Maximum Data Burst Volume if default value is not used as defined in Table 5.4.4-1 of TS 23.287 [2] and in Table 5.6.1-1. +- For broadcast, groupcast and initial signalling to establish unicast connection, PC5 DRX configuration (see TS 38.331 [16]), e.g. the mapping of PC5 QoS profile(s) to PC5 DRX cycle(s), default PC5 DRX configuration, when the UE is "not served by NG-RAN". + +6) Path selection policy: + +- The mapping of ProSe services (i.e. ProSe identifiers) to path preference (i.e. PC5 preferred, Uu preferred, or no preference) as defined in clause 5.11. + +NOTE 7: The path selection policy can be a one mapping for all ProSe services, i.e. same path preference for all ProSe services. + +7) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe Direct Communication. + +The above parameter sets from bullet 2) to 7) may be provided or updated to the UE by the ProSe Application Server. + +### 5.1.3.2 Principles for applying parameters for 5G ProSe Direct Communication + +The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe Direct Communication service. + +## 5.1.4 Authorization and Provisioning for 5G ProSe UE-to-Network Relay + +### 5.1.4.1 Policy/Parameter provisioning for 5G ProSe UE-to-Network Relay + +The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-Network Relay: + +- 1) Authorisation policy for acting as a 5G ProSe Layer-3 and/or Layer-2 UE-to-Network Relay when "served by NG-RAN": + - PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 Remote UEs. + +The authorisation for a UE to act as a 5G ProSe UE-to-Network Relay also authorizes the use of 5G ProSe UE-to-Network Relay Discovery with Model A and Model B. + +NOTE 1: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously. + +2) ProSe Relay Discovery policy/parameters for 5G ProSe UE-to-Network Relay: + +- Includes the parameters that enable the UE to perform 5G ProSe UE-to-Network Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC: + - 5G ProSe UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer Indicator per RSC, optional Control Plane Security Indicator per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. If the Control Plane Security Indicator is provided for a RSC, then the Control Plane based security procedure as described in clause 5.1.4.3.2 is performed for UE-to-Network Relay Communication for that RSC, otherwise if it is not provided for a RSC, then the User Plane based security procedure as described in clause 5.1.4.3.3 is performed for that RSC. RSC dedicated for emergency service may also be provisioned. + - Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement and Relay Discovery Additional Information messages and receiving Relay Discovery Solicitation messages; + - For 5G ProSe Layer-3 UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic for each ProSe Relay Service Code; + - Includes security related content for 5G ProSe UE-to-Network Relay, see TS 33.503 [29]. + +NOTE 2: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe UE-to-Network Relay, except for the Security parameters in bullet 2). + +3) For 5G ProSe Layer-3 UE-to-Network Relay, QoS mapping(s): + +- Each QoS mapping entry includes: + - a mapping between a 5QI value and a PQI value; + - a PQI PDB adjustment factor, for the PC5 communication for the 5G ProSe Layer-3 UE-to-Network Relay operation; + - optional the Relay Service Code(s) associates with the QoS mapping entry. + +4) For 5G ProSe Layer-3 UE-to-Network Relay to relay Ethernet or Unstructured traffic from 5G ProSe Layer-3 Remote UE by using IP type PDU Session: + +- Mapping of ProSe Service(s) to ProSe Application Server address information (consisting of IP address/FQDN and transport layer port number). + +5) Parameters to broadcast warning messages: + +- Configured Destination Layer-2 ID(s); +- PC5 QoS parameters defined in clause 5.6.1; +- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1. + +NOTE 3: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying. + +6) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-Network Relay discovery and communication. + +The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe Remote UE and thereby enabling the use of a 5G ProSe UE-to-Network Relay: + +1) Authorisation policy for using a 5G ProSe Layer-3 and/or Layer-2 UE-to-Network Relay: + +- For 5G ProSe Layer-3 Remote UE, indicates whether the UE is authorised to use a 5G ProSe Layer-3 UE-to-Network Relay. +- For 5G ProSe Layer-2 Remote UE, indicates the PLMNs in which the UE is authorized to use a 5G ProSe Layer-2 UE-to-Network Relay. + +The authorisation for a UE to act as a 5G ProSe Remote UE also authorizes the use of 5G ProSe UE-to-Network Relay discovery with Model A and Model B. + +NOTE 4: It is up to UE and application implementation to select a discovery model or whether to perform both models simultaneously. + +2) Policy/parameters for 5G ProSe UE-to-Network Relay Discovery: + +- Includes the parameters for 5G ProSe Relay Discovery and for enabling the UE to connect to the 5G ProSe UE-to-Network Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC: +- 5G ProSe UE-to-Network Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-Network Relay Layer indicator per RSC, optional Control Plane Security Indicator per RSC). The UE-to-Network Relay Layer Indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service. If the Control Plane Security Indicator is provided for a RSC, then the Control Plane based security procedures as described in clause 5.1.4.3.2 is performed for UE-to-Network Relay Communication for that RSC, otherwise if it is not provided for a RSC, then the User Plane based security procedures as described in clause 5.1.4.3.3 is performed for that RSC. RSC(s) dedicated for emergency service may be provisioned to enable the support of emergency services for UE-to-Network Relaying. +- Default Destination Layer-2 ID(s) for sending Relay Discovery Solicitation messages and receiving Relay Discovery Announcement and Relay Discovery Additional Information messages; +- For 5G ProSe Layer-3 UE-to-Network Relay, the PDU Session parameters (PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference) to be used for the relayed traffic without using N3IWF access, or an indication of N3IWF access, for each ProSe Relay Service Code; +- For 5G ProSe Layer-3 UE-to-Network Relay, optionally the ProSe application Traffic Descriptor(s) (as defined in TS 23.503 [9]) to be used for the relayed traffic for each ProSe Relay Service Code; +- Includes security related content for 5G ProSe UE-to-Network Relay, see TS 33.503 [29]. + +3) Policy/parameters for N3IWF selection for 5G ProSe Layer-3 Remote UE: + +- N3IWF identifier configuration for 5G ProSe Layer-3 Remote UE (either FQDN or IP address) in the HPLMN. +- 5G ProSe Layer-3 UE-to-Network Relay access node selection information - a prioritized list of PLMNs for N3IWF selection. It also indicates if selection of an N3IWF in a PLMN should be based on Tracking Area Identity FQDN or on Operator Identifier FQDN. + +NOTE 5: 5G ProSe Relay Discovery policy/parameters can be provided from ProSe Application Server to the 5G ProSe Remote UE, except for the Security parameters in bullet 2). + +4) Parameters to receive warning messages: + +- Configured Destination Layer-2 ID(s); +- PC5 QoS parameters defined in clause 5.6.1; +- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1. + +NOTE 6: It is up to inter operator alignment and network configuration whether a common Destination Layer-2 ID or IDs are used for all UEs cross PLMNs in a particular region for Public Warning Notification Relaying. + +5) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-Network Relay discovery and communication. + +The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-Network Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe Remote UE and thereby enabling the use of a 5G ProSe UE-to-Network Relay: + +- 1) Radio parameters for 5G ProSe UE-to-Network Relay Discovery when the UE is not "served by NG-RAN": + - Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit. + - Default PC5 DRX configuration (see TS 38.331 [16]). + - 2) Radio parameters for 5G ProSe UE-to-Network Relay communication when the UE is not "served by NG-RAN": + - Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit. +- NOTE 7: The validity time of these radio parameters is the same as the validity time of the Policy/Parameter listed above for 5G ProSe UE-to-Network Relay or 5G ProSe Remote UE. +- 3) Policy/parameters related to privacy: + - A privacy timer value indicating the duration after which the UE shall change each source Layer-2 ID self-assigned by the UE when privacy is required. + +#### 5.1.4.2 Principles for applying parameters for 5G ProSe UE-to-Network Relay + +##### 5.1.4.2.1 Principles for applying parameters for ProSe UE-to-Network Relay discovery + +The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-Network Relay discovery service. + +##### 5.1.4.2.2 Principles for applying parameters for 5G ProSe UE-to-Network Relay communication + +The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-Network Relay communication service. + +#### 5.1.4.3 Network controlled security procedures for 5G ProSe UE-to-Network Relay + +##### 5.1.4.3.1 General + +Security procedures over Control Plane and User Plane are specified for 5G ProSe UE-to-Network relaying in TS 33.503 [29]. + +##### 5.1.4.3.2 Control Plane based security procedures for 5G ProSe UE-to-Network Relay + +Control Plane-based security procedures for 5G ProSe UE-to-Network Relay call flow and procedure are defined in TS 33.503 [29], characterised by the following principles: + +- 5G ProSe UE-to-Network Relay's NAS signalling is used for the control plane based security procedure to authenticate and authorize a 5G ProSe Remote UE. +- A UE assuming the role of 5G ProSe UE-to-Network Relay can be configured to use a set of slices supporting Control Plane based security procedure. An AMF supporting Control Plane based security procedure for a 5G ProSe UE-to-Network Relay is selected as part of the slice. The 5G ProSe UE-to-Network Relay shall include in discovery messages the RSCs with the Control Plane Security Indicator set, as specified in clause 5.1.4.1, when the requested slice(s) corresponds to Control Plane based security procedure is(are) accepted. In addition, the 5G + +ProSe UE-to-Network Relay shall include in discovery messages the RSCs without Control Plane Security Indicator as specified in clause 5.1.4.1. + +- A 5G ProSe-enabled UE shall use Control Plane based security procedures if a RSC with Control Plane Security Indicator set is used by the Remote UE to establish the connection. Otherwise, if a RSC without Control Plane Security Indicator is used by the Remote UE to establish the connection, the 5G ProSe-enabled UEs shall use User Plane based security procedures as specified in clause 5.1.4.3.3. +- The AMF serving the 5G ProSe UE-to-Network Relay selects AUSF as specified in clause 6.3.4 of TS 23.501 [4] using the identification information the 5G ProSe Remote UE provided as specified in clause 6.3.3.2 of TS 33.503 [29]. +- If the 5G ProSe Remote UE is configured by HPLMN to use control plane security procedure, the 5G ProSe Remote UE's HPLMN AUSF shall support control plane based security procedure. +- If a network intends to use control plane security procedure, then all the AMFs within the network slices that the 5G ProSe UE-to-Network Relay uses shall support the control plane based security procedures. + +NOTE: If the control plane security procedure is not supported, then the 5G ProSe Remote UE can select another 5G ProSe UE-to-Network Relay or user plane based security can be used. + +#### 5.1.4.3.3 User Plane based security procedures + +User Plane-based security procedures for 5G ProSe UE-to-Network Relay are defined in TS 33.503 [29]. + +### 5.1.5 Authorization and Provisioning for 5G ProSe UE-to-UE Relay + +#### 5.1.5.1 Policy/Parameter provisioning for 5G ProSe UE-to-UE Relay + +The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-UE Relay: + +1) Authorisation policy for acting as a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay: + +- when the UE is "served by NG-RAN": + - PLMNs in which the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 End UEs accessing 5G ProSe UE-to-UE Relays over PC5 reference point. +- when the UE is not "served by NG-RAN": + - Indicates whether the UE is authorized to relay traffic for 5G ProSe Layer-3 and/or Layer-2 End UEs accessing 5G ProSe UE-to-UE Relays over PC5 reference point. +- The authorisation for a UE to act as a 5G ProSe UE-to-UE Relay also authorizes the use of 5G ProSe UE-to-UE Relay Discovery with Model A and Model B. + +NOTE 1: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously. + +2) ProSe Relay Discovery policy/parameters for 5G ProSe UE-to-UE Relay: + +- Includes the parameters that enable the UE to perform 5G ProSe UE-to-UE Relay Discovery when provided by PCF or provisioned in the ME or configured in the UICC: + - 5G ProSe UE-to-UE Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-UE Relay Layer indicator). The UE-to-UE Relay Layer indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service. + - Default Destination Layer-2 ID(s) for sending Relay Discovery Announcement message and receiving Relay Discovery Solicitation messages; + - Default Destination Layer-2 ID(s) for sending/receiving Direct Communication Request message for ProSe UE-to-UE Relay Communication with integrated Discovery; + +- For 5G ProSe Layer-3 UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code; +- Includes security related content for Relay Discovery for each Relay Service Code. + +NOTE 2: SA WG3 will determine the security related content for 5G ProSe UE-to-UE Relay. + +- 3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-UE Relay discovery and communication. + +The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe End UE and thereby enabling the use of a 5G ProSe UE-to-UE Relay: + +- 1) Authorisation policy for using a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay: + +- When the UE is "served by NG-RAN": + - PLMNs in which the UE is authorized to use a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay. +- When the UE is "not served by NG-RAN": + - Indicates whether the UE is authorised to use a 5G ProSe Layer-3 and/or Layer-2 UE-to-UE Relay. + +The authorisation for a UE to act as a 5G ProSe End UE also authorizes the use of 5G ProSe UE-to-UE Relay discovery with Model A and Model B. + +NOTE 3: It is up to UE and application implementation to select a discovery model, or whether to perform both models simultaneously. + +- 2) Policy/parameters for 5G ProSe UE-to-UE Relay Discovery: + +- Includes the parameters for 5G ProSe UE-to-UE Relay Discovery as a 5G ProSe End UE and for enabling the UE to connect to the 5G ProSe UE-to-UE Relay after discovery when provided by PCF or provisioned in the ME or configured in the UICC: +- 5G ProSe UE-to-UE Relay Discovery parameters (User Info ID, Relay Service Code(s), UE-to-UE Relay Layer indicator). The UE-to-UE Relay Layer indicator indicates whether the associated RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service. +- Default Destination Layer-2 ID(s) for sending Relay Discovery Solicitation messages and receiving Relay Discovery Announcement message; +- Default Destination Layer-2 ID(s) for sending/receiving Direct Communication Request message for ProSe UE-to-UE Relay Communication with integrated Discovery; +- For 5G ProSe Layer-3 UE-to-UE Relay, the traffic type (IP, Ethernet, Unstructured) to be used for the relayed traffic for each Relay Service Code; +- Includes security related content for Relay Discovery for each Relay Service Code. + +NOTE 4: SA WG3 will determine the security related content for 5G ProSe UE-to-UE Relay. + +- 3) Validity time indicating the expiration time of the Policy/Parameter for 5G ProSe UE-to-UE Relay discovery and communication. + +The following information is provisioned in the UE in support of the UE assuming the role of a 5G ProSe UE-to-UE Relay as well as in the UE in support of the UE assuming the role of a 5G ProSe End UE and thereby enabling the use of a 5G ProSe UE-to-UE Relay: + +- 1) Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN": + +- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Discovery over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit. +- Default PC5 DRX configuration (see TS 38.331 [16]). + +NOTE 5: RAN WG2 will determine the default PC5 DRX configuration for 5G ProSe UE-to-UE relay scenario. + +NOTE 6: Radio parameters for 5G ProSe UE-to-UE Relay Discovery when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Discovery in clause 5.1.2.1 are expected to be aligned for direct and relayed discovery for UE to UE communication. + +2) Radio parameters for 5G ProSe UE-to-UE Relay communication when the UE is not "served by NG-RAN": + +- Includes the radio parameters NR PC5 with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". The UE uses the radio parameters to perform 5G ProSe Direct Communication over PC5 reference point when "not served by NG-RAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit. + +NOTE 7: Radio parameters for 5G ProSe UE-to-UE Relay communication when the UE is not "served by NG-RAN" and Radio parameters when the UE is "not served by NG-RAN" for 5G ProSe Direct Communication in clause 5.1.3.1 are expected to be aligned for direct and relayed UE to UE communication. + +### 5.1.5.2 Principles for applying parameters for 5G ProSe UE-to-UE Relay + +#### 5.1.5.2.1 Principles for applying parameters for ProSe UE-to-UE Relay discovery + +The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-UE Relay discovery service. + +#### 5.1.5.2.2 Principles for applying parameters for 5G ProSe UE-to-UE Relay communication + +The general principles for applying policy/parameters defined in clause 5.1.1a apply to the 5G ProSe UE-to-UE Relay communication service. + +## 5.2 5G ProSe Direct Discovery + +### 5.2.1 General + +5G ProSe Direct Discovery is defined as the process that detects and identifies another UE in proximity via NR PC5 reference point. As defined in clause 5.3.3.1 in TS 23.303 [3], 5G ProSe Direct Discovery can be open or restricted; it can be standalone or used for subsequent actions e.g. to initiate 5G ProSe Direct Communication. + +In the case of inter-PLMN ProSe discovery and communication over PC5 reference point, the PC5 parameters need to be configured in a consistent way among the UEs within a certain region. The architecture for the Inter-PLMN PC5 case is defined in clause 4.2.3. + +The UEs may use the PC5 DRX mechanism to perform 5G ProSe Direct Discovery and 5G ProSe UE-to-Network Relay Discovery over PC5 reference point as specified in clause 5.13. + +### 5.2.2 5G ProSe Direct Discovery Models + +There are two models for 5G ProSe Direct Discovery: Model A and Model B which are defined in clause 5.3.1.2 in TS 23.303 [3]. + +### 5.2.3 5G ProSe UE-to-Network Relay Discovery + +For 5G ProSe UE-to-Network Relay discovery, both Model A and Model B discovery are supported: + +- Model A uses a single discovery protocol message (Announcement). +- Model B uses two discovery protocol messages (Solicitation and Response). + +For Relay Discovery Additional Information, only Model A discovery is used. + +The procedures for 5G ProSe UE-to-Network Relay discovery are defined in clause 6.3.2.3. + +## 5.2.4 5G ProSe Direct Discovery Characteristics + +5G ProSe Direct Discovery over the PC5 reference point has the following characteristics: + +- PC5 communication channel is used to carry the discovery message over PC5. The discovery message over PC5 is differentiated with other PC5 messages by AS layer. +- ProSe layer shall indicate to AS layer whether the signalling is discovery message or PC5-S message. + +NOTE 1: The discovery message format is defined in stage 3. + +Group discovery/management to support on demand-based group communication for commercial services has the following characteristics: + +- The group discovery/formation/management can be carried out in the Application layer in coordination with the Application Server. +- Application layer signalling between the UE and the Application Server is out of scope of this specification. + +5G ProSe Direct Discovery with 5G DDNMF has the following characteristics: + +- 5G DDNMF in the 5GS is used for 5G ProSe Discovery Direct Code management (including allocation and resolution). The 5G DDNMF gets the PDUID from the PCF and subscribes to notifications on Change of PDUID. +- 5G DDNMF is defined in clause 4.3.2 and the detail procedure for 5G ProSe Direct Discovery with 5G DDNMF is defined in clause 6.3. + +Group discovery/management to support public safety has the following characteristics: + +- Pre-configured or provisioned information can be used for the 5G ProSe Direct Discovery procedure as defined in clause 5.1.2. + +The information elements included in the 5G ProSe Direct Discovery messages are described in clause 5.8.1 and clause 6.3.2. + +NOTE 2: Based on UE implementation, the application layer discovery messages are exchanged either as user traffic over PC5 or alternatively as part of metadata in PC5 Direct Discovery message as specified in clause 6.3.2.1 and clause 6.4.2. In the latter case, the PC5 Direct Discovery message can contain additional field carrying application layer metadata information, e.g., the Application layer discovery messages for group discovery. The format and contents of this additional field is out of scope of 3GPP. Performance of the PC5 Direct Discovery message including the application layer information will be affected if the resulted PC5 Direct Discovery message size is too big, e.g. longer delay and lower reliability. + +## 5.2.5 5G ProSe UE-to-UE Relay Discovery + +For 5G ProSe UE-to-UE Relay Discovery, both Model A and Model B discovery are supported: + +- Model A uses a single discovery protocol message (Announcement). +- Model B uses two discovery protocol messages (Solicitation and Response). + +The procedures for 5G ProSe UE-to-UE Relay Discovery with Model A/Model B are defined in clause 6.3.2.4. + +5G ProSe UE-to-UE Relay Communication with integrated Discovery is also supported as specified in clause 6.7.3. + +## 5.3 5G ProSe Direct Communication + +### 5.3.1 General + +5G ProSe Direct Communication over PC5 reference point is supported when the UE is "served by NG-RAN" or when the UE is "not served by NG-RAN". A UE is authorized to perform 5G ProSe Direct Communication when it has valid authorization and configuration as specified in clause 5.1.3. 5G ProSe Direct Communication supports both the cases of public safety and commercial service. + +5G ProSe Direct Communication over NR based PC5 reference point supports broadcast mode, groupcast mode and unicast mode. + +For broadcast and groupcast mode 5G ProSe Direct Communication, the following data unit types are supported: IPv4, IPv6, Ethernet, Unstructured and Address Resolution Protocol (see RFC 826 [19]). + +For unicast mode 5G ProSe Direct Communication, the following data unit types are supported: IPv4, IPv6, Ethernet and Unstructured. + +The identifiers used in the 5G ProSe Direct Communication over PC5 reference point are described in clause 5.8.2. + +The QoS handling and procedures for the 5G ProSe Direct Communication over PC5 reference point are defined in clauses 5.6 and 6.4. + +The UEs may use the PC5 DRX mechanism to perform 5G ProSe Direct Communication over PC5 reference point as specified in clause 5.13. + +### 5.3.2 Broadcast mode 5G ProSe Direct Communication + +Broadcast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. The transmitting UE in broadcast communication determines the destination Layer-2 ID for broadcast as specified in clause 5.8.2 and assigns itself a source Layer-2 ID. The receiving UE determines the destination Layer-2 ID for broadcast reception as specified in clause 5.8.2. The transmitting UE determines the PC5 QoS parameters for this broadcast as specified in clause 5.6.1. The transmitting UE sends the service data using the source Layer-2 ID and the destination Layer-2 ID. + +For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address allocation is described in clause 5.5.1.2. + +### 5.3.3 Groupcast mode 5G ProSe Direct Communication + +Groupcast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. Group management is carried out by the application layer in coordination with Application Server and is out of scope of this specification. For commercial services, the Application Layer Group ID is provided by Application Server; and for public safety services, the pre-configured or provisioned Application Layer Group ID will be used for groupcast communication. The group size and member ID information could be used for groupcast control if it is provided by the application layer. + +The transmitting UE in groupcast communication determines a source Layer-2 ID and a destination Layer-2 ID and the receiving UE determines destination Layer-2 ID, as specified in clause 5.8.2. The transmitting UE determines the PC5 QoS parameters for this groupcast as specified in clause 5.6.1. The transmitting UE sends the service data using the source Layer-2 ID and the destination Layer-2 ID. + +For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address allocation is described in clause 5.5.1.2. + +### 5.3.4 Unicast mode 5G ProSe Direct Communication + +Unicast mode of 5G ProSe direct communication is supported over NR based PC5 reference point. A PC5 unicast link between two UEs is established for the 5G ProSe direct communication; and the PC5 unicast link could be maintained, modified and released according to the application layer requests or communication requirements. + +For the PC5 unicast link of the 5G ProSe direct communication, the principal for the PC5 unicast link of V2X communication described in TS 23.287 [2] clause 5.2.1.4 is reused with the following differences: + +- V2X service is replaced by ProSe Application; +- V2X service type is replaced by ProSe identifier; +- New data unit types are supported (including IPv4, Ethernet and Unstructured). + +For IP type 5G ProSe direct communication over PC5 reference point, the mechanism for IP address/prefix allocation is described in clause 5.5.1.1. The PC5 QoS handling for the unicast mode 5G ProSe direct communication is specified in clause 5.6.1. + +## 5.4 5G ProSe UE-to-Network Relay + +### 5.4.1 5G ProSe Layer-3 UE-to-Network Relay + +#### 5.4.1.1 General + +The 5G ProSe Layer-3 UE-to-Network Relay shall provide generic function that can relay any IP, Ethernet or Unstructured traffic: + +- For IP traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay uses IP type PDU Session towards 5GC. +- For Ethernet traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay can use Ethernet type PDU Session or IP type PDU Session towards 5GC. +- For Unstructured traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay can use Unstructured type PDU Session or IP type PDU Session (i.e. IP encapsulation/de-capsulation by 5G ProSe Layer-3 UE-to-Network Relay) towards 5GC. + +The type of traffic supported over PC5 reference point is indicated by the 5G ProSe Layer-3 UE-to-Network Relay e.g. using the corresponding RSC. The 5G ProSe Layer-3 UE-to-Network Relay determines the PDU Session Type based on configuration of the mapping between PDU Session parameters and RSC, as specified in clause 5.1.4.1. + +IP type PDU Session and Ethernet type PDU Session can be used to support more than one 5G ProSe Layer-3 Remote UEs while Unstructured type PDU Session can be used to support only one 5G ProSe Layer-3 Remote UE. + +NOTE: The maximum number of PDU Sessions can affect the maximum number of 5G ProSe Layer-3 Remote UEs that the 5G ProSe UE-to-Network Relay can support. + +The 5G ProSe Layer-3 UE-to-Network Relay provides the functionality to support indirect connectivity to the 5GS for 5G ProSe Layer-3 Remote UEs. A 5G ProSe Layer-3 Remote UE can be located within NG-RAN coverage or outside of NG-RAN coverage. + +The 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay may use the PC5 DRX mechanism to perform 5G ProSe UE-to-Network Relay Communications over PC5 reference point as specified in clause 5.13. + +#### 5.4.1.2 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support + +To support 5G ProSe Layer-3 Remote UE services with end-to-end confidentiality and IP address preservation requirements, the 5G ProSe Layer-3 UE-to-Network Relay with N3IWF shall provide access to the 5GC for the 5G ProSe Layer-3 Remote UE via N3IWF using the features defined in clause 4.2.8 of TS 23.501 [4]. + +5G ProSe Layer-3 UE-to-Network Relay is provisioned with RSC(s) and the corresponding PDU session parameters (e.g. S-NSSAI) to support N3IWF access as part of 5G ProSe Layer-3 UE-to-Network Relay Policy/parameters. When a 5G ProSe Layer-3 Remote UE connects with the corresponding RSC, the 5G ProSe Layer-3 UE-to-Network Relay determines the corresponding PDU session parameters based on the requested RSC. + +NOTE: The 5G ProSe Layer-3 UE-to-Network Relay only includes a RSC in discovery message when the corresponding PDU session parameters (e.g. S-NSSAI) are authorized to be used in the accessed network. + +The 5G ProSe Layer-3 Remote UE selects N3IWF as specified in clause 6.5.1.2.2. The selection of N3IWF follows the regulatory rules of the country where it is located and when required by the regulations the 5G ProSe Layer-3 Remote UE only selects a N3IWF within the local country. QoS differentiation can be provided on per-IPsec Child Security Association basis and the details are provided in clause 5.6.2.2. + +The 5GC to which the 5G ProSe Layer-3 UE-to-Network Relay registers and the 5GC to which the 5G ProSe Layer-3 Remote UE registers may be in the same PLMN or different PLMN. + +#### 5.4.1.3 Policy control and session binding to support 5G ProSe Layer-3 UE-to-Network Relay without N3IWF + +To enable support for policy control for 5G ProSe Layer-3 Remote UEs accessing 5GC via a 5G ProSe Layer-3 UE-to-Network Relay without involving N3IWF, the policy control functionality specified in TS 23.503 [9] is applied with the following functionalities: + +- For non-emergency service over the 5G ProSe Layer-3 UE-to-Network Relay, the SMF and PCF shall be configured with DNN(s) dedicated for UE-to-Network Relay connectivity, as specified in clause 5.1.4.1. + +NOTE 1: If Local Breakout configuration is supported for relay connectivity, the DNN dedicated for UE-to-Network Relay connectivity needs to be well-known DNN to allow seamless operation across various operators' networks. + +NOTE 2: For emergency service over the 5G ProSe Layer-3 UE-to-Network Relay (as specified in clause 5.4.4.3), emergency DNN configured in the Relay's AMF (as specified in clause 5.16.4 of TS 23.501 [4]) is used. + +- The AF discovers the PCF serving the 5G ProSe Layer-3 UE-to-Network Relay PDU Session as specified in clause 6.1.1.2 of TS 23.503 [9]. +- The PCF may validate any 5G ProSe Layer-3 Remote UE related service information from the AF based on roaming agreement and the DNN dedicated for UE-to-Network Relay connectivity for non-emergency service from the 5G ProSe Layer-3 Remote UE or emergency DNN for emergency service from the 5G ProSe Layer-3 Remote UE. + +NOTE 3: For 5G ProSe Layer-3 UE-to-Network Relay connectivity, the UE identity that the SMF has provided (i.e. 5G ProSe Layer-3 UE-to-Network Relay Identity) and a UE identity provided by the AF (i.e. 5G ProSe Layer-3 Remote UE Identity) can be different, while the Session binding with the PDU Session is valid. + +- The 5G ProSe Layer-3 Remote UEs may be assigned a /64 IPv6 Prefix from a shorter IPv6 prefix by the 5G ProSe Layer-3 UE-to-Network Relay. +- For a PDU Session to the DNN dedicated for 5G ProSe Layer-3 UE-to-Network Relay connectivity and using IPv6 prefix delegation (i.e. the assigned IPv6 network prefix is shorter than 64), the PCF shall perform session binding based on the IPv6 network prefix only. A successful session binding occurs whenever a longer prefix received from an AF matches the prefix value of the PDU Session. PCF shall not use the UE Identity for session binding for this PDU Session. + +NOTE 4: Support for policy control of Remote UEs behind a 5G ProSe Layer-3 UE-Network Relay using IPv4 is not available. + +#### 5.4.2 5G ProSe Layer-2 UE-to-Network Relay + +The 5G ProSe Layer-2 UE-to-Network Relay provides forwarding functionality that can relay any type of traffic over the PC5 link. + +The 5G ProSe Layer-2 UE-to-Network Relay provides the functionality to support connectivity to the 5GS for 5G ProSe Layer-2 Remote UEs. A UE is considered to be a 5G ProSe Layer-2 Remote UE if it has successfully established a PC5 link to the 5G ProSe Layer-2 UE-to-Network Relay. A 5G ProSe Layer-2 Remote UE can be located within NG-RAN coverage or outside of NG-RAN coverage. + +For PLMN selection and relay selection in the 5G ProSe Layer-2 Remote UE: + +- The 5G ProSe Layer-2 Remote UE checks whether the PLMN(s) within the RRC Container (see clause 5.8.3.3) obtained from the 5G ProSe Layer-2 UE-to-Network Relay(s) during 5G ProSe UE-to-Network Relay Discovery + +in clause 6.3.2.3 are authorized to be connected to via a 5G ProSe Layer-2 UE-to-Network Relay(s) and only the authorized PLMN(s) are then available PLMNs for NAS PLMN selection; + +- The 5G ProSe Layer-2 Remote UE selects the 5G ProSe Layer-2 UE-to-Network Relay considering the selected PLMN by NAS layer. + +NOTE: A Layer-2 Remote UE can select a PLMN different from the 5G ProSe Layer-2 UE-to-Network Relay's serving PLMN to access emergency and non-emergency services. + +The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay may use the PC5 DRX mechanism to perform 5G ProSe UE-to-Network Relay Communications over PC5 reference point as specified in clause 5.13. + +### 5.4.3 Mobility Restrictions for 5G ProSe UE-to-Network Relaying + +The handling of Mobility Restrictions for 5G ProSe enabled UE follows the principles as specified in clause 5.3.4.1 of TS 23.501 [4] with the following additions and clarifications: + +- **Forbidden Area:** + - In a Forbidden Area, a 5G ProSe enabled UE is not allowed to perform the Relay operation. If the 5G ProSe UE-to-Network Relay operates in a Forbidden Area of the 5G ProSe Remote UE, the 5G ProSe Remote UE is not allowed to access the network via this 5G ProSe UE-to-Network Relay unless the 5G ProSe Remote UE is attempting for emergency service. +- **Service Area Restriction:** + - Service Area Restriction is not applicable to 5G ProSe Layer-3 Remote UE. + - Service Area Restriction is not applicable to 5G ProSe enabled MCX-subscribed UEs as defined in clause 5.3.4.1 of TS 23.501 [4]. + +NOTE 1: It is expected that all 5G ProSe enabled Public Safety UEs are MCX-subscribed as defined in clause 5.16.6 of TS 23.501 [4]. + +- In a Non-Allowed Area, a 5G ProSe enabled UE follows the principles of a UE in limited service state as specified in clause 5.9. It cannot perform the Relay operation as 5G ProSe Layer-2 UE-to-Network Relay or 5G ProSe Layer-3 UE-to-Network Relay based on the conditions described in clause 5.9 except for emergency service from the 5G ProSe Remote UE as specified in clause 5.4.4. +- In a Non-Allowed Area, a 5G ProSe Layer-2 Remote UE follows the principles as specified in clause 5.3.4.1 of TS 23.501 [4], for communication with the network via the 5G ProSe Layer-2 UE-to-Network Relay. +- **Core Network type restriction, RAT type restriction:** + +In these cases, a 5G ProSe enabled UE is not able to register in the network for normal service and stays in limited service state and the principles in clause 5.9 shall apply. The 5G ProSe Layer-2 Remote UE is allowed to register to the network via the 5G ProSe UE-to-Network Relay for emergency service. + +NOTE 2: Closed Access Group information is not specified for 5G ProSe. + +### 5.4.4 Support of emergency service from 5G ProSe Remote UE via 5G ProSe UE-to-Network Relay + +#### 5.4.4.1 General + +When a 5G ProSe enabled UE does not have direct connection to the network for emergency service, the UE may attempt to obtain emergency service via 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay. + +NOTE: Direct connection refers to the UE connected to the network via Uu or WLAN. No direct connection to the network for emergency service includes also the case that the RAN broadcast SIB indicates no emergency support as specified in TS 23.122 [14]. + +A 5G ProSe enabled UE acting as 5G ProSe UE-to-Network Relay shall have a normal registration (including also normal registration for a 5G ProSe Relay enabled UE in Non-Allowed Area). A 5G ProSe enabled UE in limited-service state shall not act as 5G ProSe UE-to-Network Relay. Mobility Restrictions that are overruled for UE requesting direct emergency service are overruled also for 5G ProSe UE-to-Network Relay that is relaying emergency service as specified in clause 5.4.3. + +A 5G ProSe enabled UE acting as 5G ProSe UE-to-Network Relay shall only advertise its support for relaying emergency services as defined in clause 5.4.4.2 and clause 5.4.4.3 during 5G ProSe UE-to-Network Relay Discovery. + +Dedicated RSC(s) for emergency service needs to be provisioned in the 5G ProSe enabled UEs with capability of 5G ProSe UE-to-Network Relay and/or 5G ProSe Remote UE as specified in clause 5.1.4. + +The dedicated RSC(s) for emergency service are used by the 5G ProSe UE-to-Network Relay and 5G ProSe Remote UE during 5G ProSe UE-to-Network Relay Discovery and PC5 link establishment. + +A PC5 link associated with a dedicated emergency RSC shall be used for emergency service and for emergency service only. + +If the 5G ProSe UE-to-Network Relay needs to establish RRC Connection when the 5G ProSe Remote UE has requested emergency service over the PC5 link, the 5G ProSe UE-to-Network Relay shall use RRC establishment cause "emergency". + +The existing positioning function as applicable is reused for the 5G ProSe Remote UE. If no other information is available, the location of the 5G ProSe UE-to-Network Relay can be used as Remote UE location estimate. + +For more information on UE specific behaviour and location handling, refer to TS 23.167 [31]. + +PC5 link for emergency services over 5G ProSe UE-to-Network Relay can be established with or without PC5 security; how to establish PC5 security link for emergency service is specified in TS 33.503 [29]. + +#### 5.4.4.2 Emergency service from 5G ProSe Remote UE via 5G ProSe Layer-2 UE-to-Network Relay + +For a 5G ProSe Layer-2 UE-to-Network Relay to participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message), the serving NG-RAN support of emergency services is required, indicated by it broadcasting *ims-EmergencySupport* in system information as specified in TS 38.300 [12] and TS 38.331 [16]. The 5G ProSe Layer-2 Remote UE may select a different PLMN from the 5G ProSe Layer-2 UE-to-Network Relay. The 5G ProSe Layer-2 Remote UE may select any PLMN within the RRC Container (see clause 5.8.3.3) obtained from any 5G ProSe Layer-2 UE-to-Network Relay(s) which has announced the RSC dedicated for emergency service during 5G ProSe UE-to-Network Relay Discovery in clause 6.3.2.3. + +**NOTE:** When emergency support is indicated by RAN, 5G ProSe Layer-2 UE-to-Network Relay can participate in the 5G ProSe UE-to-Network Relay Discovery procedure for emergency service (i.e. sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message) even if its serving PLMN does not support emergency service. + +#### 5.4.4.3 Emergency service from 5G ProSe Remote UE via 5G ProSe Layer-3 UE-to-Network Relay + +A 5G ProSe Layer-3 UE-to-Network Relay participates in the 5G ProSe UE-to-Network Relay Discovery procedure (i.e., sending the UE-to-Network Relay Discovery Announcement message or UE-to-Network Relay Discovery Response message) for emergency service only when it has received the Emergency Service Support indicator in its latest Registration Accept from the AMF. + +If PC5 connection is requested using dedicated RSC for emergency service, then the 5G ProSe Layer-3 UE-to-Network Relay sets the RRC Establishment cause to "emergency" when establishing an RRC connection. + +For 5G ProSe Layer-3 UE-to-Network Relay without N3IWF: + +- the 5G ProSe Layer-3 UE-to-Network Relay sets up an emergency PDU Session to support the 5G ProSe Remote UE's emergency service. + +- A 5G ProSe Layer-3 UE-to-Network Relay shall only serve emergency services for either itself or for one 5G ProSe Layer-3 Remote UE but not for more than one UE at the same time. In possible conflict case, the prioritisation between the emergency calls is determined by the local regulations, if available. In the absence of local regulations, prioritisation between the emergency calls is 5G ProSe Layer-3 UE-to-Network Relay implementation specific. +- If a 5G ProSe Layer-3 UE-to-Network Relay is not able to handle relayed emergency services due to having an active emergency service (of its own or for a 5G ProSe Layer-3 Remote UE emergency service), the 5G ProSe Layer-3 UE-to-Network Relay shall not advertise its support of emergency service and shall not respond to any new 5G ProSe Layer-3 Remote UE's requests for relaying emergency services. + +NOTE: The 5G ProSe Layer-3 Remote UE's requests refers to either 5G ProSe UE-to-Network Relay Discovery Solicitation message with model B, or Direct Communication Request message including the dedicated RSC for emergency service. + +When a 5G ProSe Layer-3 Remote UE needs to initiate emergency service, it should attempt to use 5G ProSe Communication for emergency service via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF procedures before attempting to establish an emergency PDU Session via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support. + +For information on the handling of emergency number, P-CSCF address and access type setting, refer to TS 23.167 [31]. + +## 5.5 IP address allocation + +### 5.5.1 General + +#### 5.5.1.1 IP address allocation for unicast mode of 5G ProSe direct communication + +For unicast mode of 5G ProSe direct communication, the following mechanism for IP address/prefix allocation may be used: + +- a) DHCP-based IPv4 address allocation with one of the two UEs acting as a DHCP server. +- b) IPv6 Stateless Address auto configuration specified in RFC 4862 [17] for assignment of IPv6 prefix, with one of the two UEs acting as IPv6 default router. + +NOTE: Which UE acts as a DHCPv4 server or IPv6 default router is negotiated during secure layer-2 link establishment by exchanging the IP Address Configuration as described in clause 6.4.3. + +- c) IPv6 link-local addresses as defined in RFC 4862 [17] are formed by UEs locally. The IPv6 link-local addresses are exchanged during the establishment of a secure layer-2 link over PC5. The UEs shall disable duplicate address detection after the layer-2 link is established. + +#### 5.5.1.2 IP address allocation for broadcast and groupcast modes of 5G ProSe direct communication + +For broadcast and groupcast modes of 5G ProSe direct communication, the following source IP address management applies: + +- a) the UE configures a link local IPv4 address to be used as the source IP address, as defined in clause 4.5.3 of TS 23.303 [3]. If it is not configured with an address, it uses Dynamic Configuration of IPv4 Link-Local Addresses RFC 3927 [18]. +- b) the UE configures a link local IPv6 address to be used as the source IP address, as defined in clause 4.5.3 of TS 23.303 [3]. The UE may use this IP address for direct communication without sending Neighbour Solicitation and Neighbour Advertisement message for Duplicate Address Detection. + +NOTE: The destination IP address management for broadcast and groupcast modes of ProSe direct communication is left to UE implementation. + +### 5.5.1.3 IP address allocation for communication with a 5G ProSe Layer-3 ProSe UE-to-Network Relay + +For communication with a 5G ProSe Layer-3 UE-to-Network Relay, the following mechanism for IP address/prefix allocation applies: + +- The PDU Session Type used for the relay traffic shall support the IP version used by the 5G ProSe Layer-3 Remote UE. If the 5G ProSe Layer-3 Remote UE initiates an allocation of IPv4 address or an IPv6 prefix when the requested IP version is not supported in the corresponding PDU Session then IP address/prefix allocation fails. +- a) When the 5G ProSe Layer-3 Remote UE uses IPv4 to access the external DN: + - a1) The IPv4 address allocation and IPv4 parameter configuration via DHCPv4 are performed according to RFC 2131 [24] and RFC 4039 [25] procedures. The IPv4 address provided to the 5G ProSe Layer-3 Remote UE from the 5G ProSe Layer-3 UE-to-Network Relay by DHCPv4 procedure shall correspond to a local IPv4 address range configured in the 5G ProSe Layer-3 UE-to-Network Relay. + - a2) The DHCPv4 request from the 5G ProSe Layer-3 Remote UE is always sent subsequent to the establishment of the one-to-one 5G ProSe Direct Communication between the 5G ProSe Layer-3 Remote UE and the 5G ProSe Layer-3 UE-to-Network Relay, see details for the IPv4 address allocation in clause 5.4.4.3 of TS 23.303 [3] with the following difference: + - The ProSe Relay UE ID of the ProSe UE-to-Network Relay is replaced by the source Layer-2 ID of the 5G ProSe UE-to-Network Relay for PC5 unicast communication. +- b) When the 5G ProSe Layer-3 Remote UE uses IPv6 to access the external DN: + - b1) IPv6 network prefix allocation via IPv6 Stateless Address auto-configuration. Router solicitation from the 5G ProSe Layer-3 Remote UE is always sent subsequent to the establishment of the one-to-one ProSe Direct Communication between the 5G ProSe Layer-3 Remote UE and the 5G ProSe Layer-3 UE-to-Network Relay, see details for IPv6 prefix allocation in clause 5.4.4.2 of TS 23.303 [3] with the following differences: + - The 5G ProSe Layer-3 UE-to-Network Relay shall obtain the IPv6 prefix assigned to the 5G ProSe Layer-3 Remote UE via prefix delegation function from the network as defined in clause 5.5.2. + - The ProSe Relay UE ID of the ProSe UE-to-Network Relay is replaced by the source Layer-2 ID of the 5G ProSe UE-to-Network Relay for PC5 unicast communication. + - PDN connection is replaced by PDU Session. + - b2) IPv6 parameter configuration via Stateless DHCPv6: The UE may use stateless DHCPv6 for additional parameter configuration. + - b3) The 5G ProSe Layer-3 UE-to-Network Relay assigns IPv6 prefixes from IPv6 prefix range that have been assigned to the PDU Session used for the relay traffic via IPv6 prefix delegation. + +### 5.5.1.4 IP address allocation for communication with a 5G ProSe Layer-3 UE-to-UE Relay + +For communication with a 5G ProSe Layer-3 UE-to-UE Relay, the following mechanism for IP address/prefix allocation applies: + +- IP address allocation mechanisms of unicast mode of 5G ProSe direct communication as described in clause 5.5.1.1 can be reused on each hop between a 5G ProSe End UE and the 5G ProSe Layer-3 UE-to-UE Relay. +- The 5G ProSe Layer-3 UE-to-UE Relay may provide the IP address of the target 5G ProSe End UE to the source 5G ProSe End UE in the Direct Communication Accept message, if the target 5G ProSe End UE IP address is available at the time. +- The 5G ProSe End UE may obtain the IP address of other 5G ProSe End UEs via the 5G ProSe Layer-3 UE-to-UE Relay using DNS query. + +NOTE: 5G ProSe Layer-3 UE-to-UE Relay may support 5G ProSe End UEs of different IP versions by performing IP conversions. + +## 5.5.2 IPv6 Prefix Delegation via DHCPv6 for 5G ProSe Layer-3 UE-to-Network Relay + +IPv6 Prefix Delegation via DHCPv6 for 5G ProSe Layer-3 UE-to-Network Relay is defined in clause 5.8.2.2.4 of TS 23.501 [4]. + +## 5.6 QoS handling + +### 5.6.1 QoS handling for 5G ProSe Direct Communication + +In order to support QoS handling for 5G ProSe Direct Communication, the mechanism defined in clause 5.4 of TS 23.287 [2] is reused with the following differences: + +- Only NR PC5 QoS model is used. +- PC5 Packet Filter Set supports three types of packet filters, i.e. the Prose IP Packet Filter Set, ProSe Ethernet Packet Filter Set and the Prose Packet Filter Set. Each PC5 QoS Rule additionally contains the ProSe identifier when the ProSe identifier is not included in the PC5 Packet Filter Set. +- V2X IP Packet Filter Set is replaced by ProSe IP Packet Filter Set. +- V2X Packet Filter Set is replaced by ProSe Packet Filter Set. ProSe Packet Filter Set shall support Packet Filters based on at least any combination of: + - ProSe identifier; + - Source/Destination Layer-2 ID; + - Application Layer ID. +- ProSe Ethernet Packet Filter Set that has the same format as the Ethernet Packet Filter Set defined in clause 5.7.6.3 of TS 23.501 [4] is additionally defined. +- V2X application layer is replaced by ProSe application layer. +- V2X layer is replaced by ProSe layer. +- V2X service type is replaced by ProSe identifier. +- UE-PC5-AMBR is only applied for NR PC5. +- The PQI values are additionally defined. The one-to-one mapping of standardized PQI values that are additionally defined to PC5 QoS characteristics is specified in table 5.6.1-1. + +Table 5.6.1-1: Standardized PQI values that are additionally defined to QoS characteristics mapping + +| PQI Value | Resource Type | Default Priority Level | Packet Delay Budget | Packet Error Rate | Default Maximum Data Burst Volume | Default Averaging Window | Example Services | +|-----------|-----------------------------|------------------------|---------------------|-------------------|-----------------------------------|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| 24 | GBR (NOTE 1) | 1 | 150 ms | $10^{-2}$ | N/A | 2000 ms | Mission Critical user plane Push To Talk voice (e.g. MCPTT) | +| 25 | | 2 | 200 ms | $10^{-2}$ | N/A | 2000 ms | Non-Mission-Critical user plane Push To Talk voice, Conversational Voice | +| 26 | | 2 | 200 ms | $10^{-3}$ | N/A | 2000 ms | Mission Critical Video user plane | +| 32 | | 4 | 300 ms | $10^{-3}$ | N/A | 2000 ms | Conversational Video (Live Streaming) | +| 33 | | 3 | 100 ms | $10^{-3}$ | N/A | 2000 ms | Real Time Gaming, Process automation monitoring | +| 34 | | 5 | 600 ms | $10^{-6}$ | N/A | 2000 ms | Non-Conversational Video (Buffered Streaming) | +| 60 | Non-GBR | 1 | 120 ms | $10^{-6}$ | N/A | N/A | Mission Critical delay sensitive signalling (e.g. MC-PTT signalling) | +| 61 | | 6 | 400 ms | $10^{-6}$ | N/A | N/A | Mission Critical Data (e.g. example services are the same as 5QI 6/8/9 as specified in TS 23.501 [4]) | +| 70 | | 7 | 200 ms | $10^{-3}$ | N/A | N/A | Voice, Video (Live Streaming) Interactive Gaming | +| 71 | | 7 | 20 ms | $10^{-6}$ | N/A | N/A | Low Latency eMBB applications Augmented Reality | +| 92 | Delay Critical GBR (NOTE 1) | 5 | 5ms | $10^{-4}$ | 20000 bytes | 2000 ms | Interactive service - consume VR content with high compression rate via tethered VR headset (See TS 22.261 [6]) | +| 93 | | 6 | 10ms | $10^{-4}$ | 20000 bytes | 2000 ms | interactive service - consume VR content with low compression rate via tethered VR headset; Gaming or Interactive Data Exchanging (See TS 22.261 [6]) | + +NOTE 1: GBR and Delay Critical GBR PQIs can only be used for unicast PC5 communications. + +## 5.6.2 QoS handling for 5G ProSe UE-to-Network Relay operations + +### 5.6.2.1 QoS handling for 5G ProSe Layer-3 UE-to-Network Relay without N3IWF + +For a 5G ProSe Layer-3 Remote UE accessing network via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF, the QoS requirement of the relay traffic between 5G ProSe Layer-3 Remote UE and UPF can be satisfied by the corresponding QoS control for the PC5 link between 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay (PC5 QoS control) and the QoS control for the PDU session established between 5G ProSe Layer-3 UE-to-Network Relay and UPF (i.e. Uu QoS control). The PC5 QoS is controlled with PC5 QoS rules and PC5 QoS parameters (e.g. PQI, GFBR, MFBR, PC5 LINK-AMBR) as specified in clause 5.4 of TS 23.287 [2]. The QoS for the PDU session established between the 5G ProSe Layer-3 UE-to-Network Relay and UPF (i.e. Uu QoS control) is controlled with QoS rules and 5G QoS parameters (e.g. 5QI, GFBR, MFBR) as specified in clause 5.7 of TS 23.501 [4]. + +As shown in figure 5.6.2.1-1 below, the end-to-end QoS can be met only when the QoS requirements are properly translated and satisfied over the two legs respectively. + +![Diagram illustrating End-to-End QoS translation for 5G ProSe Layer-3 UE-to-Network Relay operation. The diagram shows a flow from Remote UE to UE-to-NW Relay, then to NG-RAN, 5GC, and finally AS. Red double-headed arrows indicate QoS translation: PC5 QoS (PQI) between Remote UE and UE-to-NW Relay, Uu QoS (5QI) between UE-to-NW Relay and NG-RAN, and End-to-End QoS for a relay service spanning from Remote UE to NG-RAN.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` + +graph LR + RemoteUE[Remote UE] --- PC5[PC5] --- UEtoNW[UE-to-NW Relay] + UEtoNW --- Uu[Uu] --- NG_RAN[NG-RAN] + NG_RAN --- 5GC((5GC)) + 5GC --- N6[N6] --- AS[AS] + style RemoteUE fill:#fff,stroke:#000 + style UEtoNW fill:#fff,stroke:#000 + style NG_RAN fill:#fff,stroke:#000 + style 5GC fill:#fff,stroke:#000 + style AS fill:#fff,stroke:#000 + style PC5 fill:#fff,stroke:#000 + style Uu fill:#fff,stroke:#000 + style N6 fill:#fff,stroke:#000 + +``` + +Diagram illustrating End-to-End QoS translation for 5G ProSe Layer-3 UE-to-Network Relay operation. The diagram shows a flow from Remote UE to UE-to-NW Relay, then to NG-RAN, 5GC, and finally AS. Red double-headed arrows indicate QoS translation: PC5 QoS (PQI) between Remote UE and UE-to-NW Relay, Uu QoS (5QI) between UE-to-NW Relay and NG-RAN, and End-to-End QoS for a relay service spanning from Remote UE to NG-RAN. + +**Figure 5.6.2.1-1: End-to-End QoS translation for 5G ProSe Layer-3 UE-to-Network Relay operation** + +To achieve this, the QoS mapping can be pre-configured or provided to the 5G ProSe Layer-3 UE-to-Network Relay by the PCF using Prose Policy as specified in clause 5.1.4.1. The QoS mapping includes combinations of the 5QIs and PQIs mapping as entries. The PQI shall have standardized values as defined in Table 5.6.1-1 and in Table 5.4.4-1 of TS 23.287 [2]. The 5QI shall have standardized values as defined in TS 23.501 [4] clause 5.7.4. The QoS mapping also includes an adjustment factor for the PQI's PDB, e.g. 1/5 of the standardized PDB value in Table 5.6.1-1 and Table 5.4.4-1 of TS 23.287 [2]. + +If the QoS Flows setup are initiated by network, the SMF can base on the PCC rules or its local configuration to generates the QoS rules and QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR) and signal to the 5G ProSe Layer-3 UE-to-Network Relay using PDU Session Establishment/Modification procedure. For the PDU sessions used for relaying, the SMF always provides the QoS Flow level QoS parameters to the 5G ProSe Layer-3 UE-to-Network Relay when establishes a QoS Flow. Then the 5G ProSe Layer-3 UE-to-Network Relay decides the PC5 QoS parameters for the corresponding PC5 QoS Flow by determining the PQI based the QoS mapping and the GFBR and MFBR values for the PC5 GBR QoS Flow are set equal to the GFBR and MFBR values for the GBR QoS Flow respectively. The PCF differentiates the relay traffic based on either local configuration, e.g. by a dedicated DNN or S-NSSAI used for relay traffic or by the traffic filters. + +**NOTE:** Separate QoS mappings can be configured for different RSCs. + +If the 5G ProSe Layer-3 Remote UE initiates PC5 QoS Flows setup or modification during the Layer-2 link establishment or modification procedure, the 5G ProSe Layer-3 Remote UE provides the QoS Info as described in clause 6.4.3.6 to the 5G ProSe Layer-3 UE-to-Network Relay. The received PC5 QoS parameters of the QoS Info (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) are interpreted as the end-to-end QoS requirements by the 5G ProSe Layer-3 UE-to-Network Relay for the traffic transmission between 5G ProSe Layer-3 Remote UE and UPF. If the end-to-end QoS requirements can be supported by an entry in QoS mapping, the 5G ProSe Layer-3 UE-to-Network Relay uses the 5QI of the entry for the Uu QoS control and uses the PQI of the entry for the PC5 QoS control. If the end-to-end QoS requirements cannot be supported by any entries in QoS mapping, the 5G ProSe Layer-3 UE-to-Network Relay, based on its implementation, decides the 5QI for the Uu QoS control and PQI for the PC5 QoS control. The 5G ProSe Layer-3 UE-to-Network Relay provides the QoS Info (including PQI value chosen by the 5G ProSe Layer-3 UE-to-Network Relay) as part of the Accept message to the 5G ProSe Layer-3 Remote UE. If the 5G ProSe Layer-3 Remote UE performs the Layer-2 link modification procedure to add new PC5 QoS Flow(s) or modify the existing PC5 QoS Flow(s) for IP traffic or Ethernet traffic over PC5 reference point, the 5G ProSe Layer-3 Remote UE may also provide the PC5 QoS Rule(s) for the PC5 QoS Flow(s) to be added or modified to the 5G ProSe Layer-3 UE-to-Network Relay. The 5G ProSe Layer-3 UE-to-Network Relay may generate the Packet Filters used over Uu reference point based on the received PC5 QoS Rule(s). + +The 5G ProSe Layer-3 UE-to-Network Relay performs the UE requested PDU session Modification as defined in TS 23.502 [5], clause 4.3.3 for authorizing the requested QoS including the 5QI and the Packet Filters. If the PCF authorizes the requested QoS with a different 5QI value, the 5G ProSe Layer-3 UE-to-Network Relay may further update the PQI value based on the authorized 5QI value and the 5G ProSe Layer-3 UE-to-Network Relay performs the Layer-2 link modification procedure as defined in clause 6.4.3.6 to update the corresponding PC5 QoS Flow with the updated PQI value. + +Alternatively, reflective QoS control over Uu as defined in TS 23.501 [4], clause 5.6.5.3 can be leveraged for dynamic QoS handling of 5G ProSe Layer-3 Remote UE to save on signalling between SMF and 5G ProSe Layer-3 UE-to-Network Relay. Upon reception of a DL packet with RQI on the Uu for the 5G ProSe Layer-3 Remote UE, based on the indicated QFI, the 5G ProSe Layer-3 UE-to-Network Relay creates a new derived QoS rule or updates existing derived QoS rule corresponding to the remote UE, as defined in TS 23.501 [4]. The derived QoS rule is for UL packets from the 5G ProSe Layer-3 Remote UE at Uu interface. + +Based on signalled QoS rules (via SMF) or derived QoS rules (Uplink Uu via reflective QoS), the 5G ProSe Layer-3 UE-to-Network Relay may generate the Packet Filters used over PC5 reference point and use the L2 Link Modification procedures as defined in clause 6.4.3.6 to either update existing PC5 QoS Flow(s) or to set up new PC5 QoS Flow(s) + +(when the QFI to PC5 QoS Flow mapping does not exist). The 5G ProSe Layer-3 UE-to-Network Relay may also provide the PC5 QoS Rule(s) for the PC5 QoS Flow(s) to be added or modified to the 5G ProSe Layer-3 Remote UE. + +When the 5G ProSe Layer-3 UE-to-Network relay deletes the derived QoS rule e.g. after the RQ Timer expires, the 5G ProSe Layer-3 UE-to-Network Relay may perform L2 Link Modification procedures defined in clause 6.4.3.6 accordingly using the PQI mapped from the 5QI of the currently used QoS rule after the deletion of the derived QoS rule(s). + +### 5.6.2.2 QoS handling for 5G ProSe Layer-3 UE-to-Network relay with N3IWF + +When accessing 5GS via a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF, the 5G ProSe Layer-3 Remote UE can request for PDU Session establishment or handover an existing PDU session to the N3IWF using UE requested PDU Session Establishment procedure defined in TS 23.502 [5] clause 4.12.5. + +![Diagram illustrating End-to-End QoS support via Layer-3 UE-to-Network Relay with N3IWF. The diagram shows a flow from Remote UE to Relay UE (PC5), then to NG RAN (Uu), then to a cloud containing Relay UE 5GC, UPF (Relay), and N3IWF (N6). The N3IWF connects to another cloud containing Remote UE 5GC and UPF (Remote). Two horizontal double-headed arrows below the diagram indicate 'IPsec security association' and 'End-to-end QoS for relay service' spanning from the Remote UE to the Remote UPF.](db5deafdae53dbc7d5972957f708c691_img.jpg) + +Diagram illustrating End-to-End QoS support via Layer-3 UE-to-Network Relay with N3IWF. The diagram shows a flow from Remote UE to Relay UE (PC5), then to NG RAN (Uu), then to a cloud containing Relay UE 5GC, UPF (Relay), and N3IWF (N6). The N3IWF connects to another cloud containing Remote UE 5GC and UPF (Remote). Two horizontal double-headed arrows below the diagram indicate 'IPsec security association' and 'End-to-end QoS for relay service' spanning from the Remote UE to the Remote UPF. + +**Figure 5.6.2.2-1: End-to-End QoS support via Layer-3 UE-to-Network Relay with N3IWF** + +For the 5G ProSe Layer-3 Remote UE's PDU session(s) established via N3IWF, QoS differentiation can be provided on per-IPsec Child Security Association basis. N3IWF determines the IPsec child SAs as defined in TS 23.502 [5] clause 4.12. The N3IWF is preconfigured to allocate different IPsec child SAs for QoS Flows with different QoS profiles. + +Based on configuration, the N3IWF can use one of the options below for QoS support in 5G ProSe Layer-3 UE-to-Network Relay UE's serving PLMN: + +- a static QoS mapping mechanism; +- a dynamic QoS signalling based mechanism. + +For the static QoS mapping mechanism, a SLA is established to govern the QoS handling between the 5G ProSe Layer-3 Remote UE's 5GC and the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC, e.g. when the RSC is configured. The SLA can include the mapping between the DSCP markings for the IPsec child SAs with the Remote UE and the corresponding QoS and N3IWF IP address(es). The non-alteration of the DSCP field between N3IWF and the 5G ProSe Layer-3 UE-to-Network Relay UE's UPF is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters at the 5G ProSe Layer-3 UE-to-Network Relay UE's UPF can be based on the N3IWF IP address and the DSCP markings. + +When the dynamic QoS signalling based mechanism is used by N3IWF, it works as follows: + +- When the 5G ProSe Layer-3 Remote UE establishes or handovers a PDU session via the N3IWF as described in clause 4.12.5 of TS 23.502 [5], the PCF serving the PDU Session in the 5G ProSe Layer-3 Remote UE's 5GC detects need for specific QoS and provides corresponding PCC rules to SMF in the 5G ProSe Layer-3 Remote UE's 5GC. The resulted QoS information is provided to N3IWF in step 2b of clause 4.12.5 of TS 23.502 [5]. The N3IWF determines the IPSec Child SA(s) and signals to the 5G ProSe Layer-3 Remote UE, as in step 4 of clause 4.12.5 of TS 23.502 [5] via IKE signalling including the PDU Session ID, the QFI(s), optionally a DSCP value and optionally the Additional QoS Information specified in clause 4.12.5 of TS 23.502 [5]. The PDU Session Establishment Accept message will be sent to the 5G ProSe Layer-3 Remote UE as in step 5 of clause 4.12.5 of TS 23.502 [5]. +- Based on Additional QoS Information received from the N3IWF, the 5G ProSe Layer-3 Remote UE determines whether it is necessary to request for QoS session modification for the dedicated QoS Flows toward the 5G + +ProSe Layer-3 UE-to-Network Relay as described in clause 5.6.2.1. The 5G ProSe Layer-3 Remote UE also provides the N3IWF address, DSCP and the SPI as the traffic filter to enable filtering and mapping of DL traffic towards the right PDU Session/QoS Flow within the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC. + +NOTE: This mechanism allows to communicate GBR related parameters such as GFBR and MFBR from the PCF of the 5G ProSe Layer-3 Remote UE via the N3IWF and the 5G ProSe Layer-3 Remote UE to the 5G ProSe Layer-3 UE-to-Network Relay UE. The 5G ProSe Layer-3 UE-to-Network Relay UE would be able to request the GBR resources from its serving network using UE requested PDU session modification as in clause 4.3.3. of TS 23.502 [5]. + +- If the 5G ProSe Layer-3 UE-to-Network Relay performs the PDU Session Modification procedure, the PCF in the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC authorizes the QoS parameters. If the PDU Session Modification procedure authorized the requested QoS parameters, the 5G ProSe Layer-3 UE-to-Network Relay acknowledges the 5G ProSe Layer-3 Remote UE over PC5. The 5G ProSe Layer-3 UE-to-Network Relay also provides the traffic filter provided by the 5G ProSe Layer-3 Remote UE to the SMF during the PDU Session Modification procedure and the SMF updates the PSA UPF with DL Packet Detection Rules. +- The PSA UPF in the 5G ProSe Layer-3 UE-to-Network Relay UE's 5GC maps the DL traffic from IPSec Child SA tunnel to appropriate PDU Session/QoS Flow considering SPI and N3IWF address (filters provided by the 5G ProSe Layer-3 Remote UE). +- The 5G ProSe Layer-3 Remote UE's or the 5G ProSe Layer-3 Remote UE's 5GC may initiated PDU Session Modification procedures as specified in clause 4.12.6 of TS 23.502 [5]. When the 5G ProSe Layer-3 Remote UE received QoS information from the N3IWF, the same interactions between the 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay and between the 5G ProSe Layer-3 UE-to-Network Relay and its 5GC as described above apply. + +### 5.6.2.3 QoS handling for 5G ProSe Layer-2 UE-to-Network Relay + +For a 5G ProSe Layer-2 Remote UE accessing network via 5G ProSe Layer-2 UE-to-Network Relay, the existing 5G QoS control is reused between the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 Remote UE's core network. The 5G ProSe Layer-2 Remote UE's SMF provides QoS profiles to NG-RAN, how NG-RAN performs QoS enforcement for PC5 interface (between the 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay) and Uu interface (between the 5G ProSe Layer-2 UE-to-Network Relay and RAN) is specified in TS 38.300 [12]. + +## 5.6.3 QoS handling for 5G ProSe UE-to-UE Relay operations + +### 5.6.3.1 QoS handling for 5G ProSe Layer-3 UE-to-UE Relay + +For a 5G ProSe Layer-3 End UE connecting with another 5G ProSe Layer-3 End UE(s) via 5G ProSe Layer-3 UE-to-UE Relay, the QoS requirement of the relay traffic between the peer 5G ProSe Layer-3 End UE(s) can be satisfied by the corresponding QoS control for the PC5 link between source 5G ProSe Layer-3 End UE and 5G ProSe Layer-3 UE-to-UE Relay (i.e. first hop PC5 QoS control) and the QoS control for the PC5 link between 5G ProSe Layer-3 UE-to-UE Relay and target 5G ProSe Layer-3 End UE (i.e. second hop PC5 QoS control). The first hop PC5 QoS and second hop PC5 QoS is controlled with PC5 QoS rules and PC5 QoS parameters (e.g. PQI, GFBR, MFBR, PC5 LINK-AMBR) as specified in clause 5.6.1. + +As shown in figure 5.6.3.1-1 below, the end-to-end QoS is met only when the QoS requirements are properly translated and satisfied over the two legs respectively. + +![Diagram illustrating End-to-End QoS for 5G ProSe Layer-3 UE-to-UE Relay operation. The diagram shows three main components: End UE, UE-to-UE Relay, and End UE, connected in a linear sequence. The first hop is between the first End UE and the UE-to-UE Relay, labeled 'PC5'. The second hop is between the UE-to-UE Relay and the second End UE, also labeled 'PC5'. Below the diagram, three red arrows indicate QoS levels: 'First hop PC5 QoS (PQI)' for the first hop, 'second hop PC5 QoS (PQI)' for the second hop, and 'End-to-End QoS for a relay service' spanning both hops.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Diagram illustrating End-to-End QoS for 5G ProSe Layer-3 UE-to-UE Relay operation. The diagram shows three main components: End UE, UE-to-UE Relay, and End UE, connected in a linear sequence. The first hop is between the first End UE and the UE-to-UE Relay, labeled 'PC5'. The second hop is between the UE-to-UE Relay and the second End UE, also labeled 'PC5'. Below the diagram, three red arrows indicate QoS levels: 'First hop PC5 QoS (PQI)' for the first hop, 'second hop PC5 QoS (PQI)' for the second hop, and 'End-to-End QoS for a relay service' spanning both hops. + +**Figure 5.6.3.1-1: End-to-End QoS for 5G ProSe Layer-3 UE-to-UE Relay operation** + +To achieve this, the source 5G ProSe Layer-3 End UE initiates PC5 QoS Flows setup or modification during the Layer-2 link establishment or modification procedure, the source 5G ProSe Layer-3 End UE provides the QoS Info as described in clause 6.4.3.7.3 to the 5G ProSe Layer-3 UE-to-UE Relay. The received PC5 QoS parameters of the QoS Info (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) are interpreted as the end-to-end QoS requirements by the 5G ProSe Layer-3 UE-to-UE Relay for the traffic transmission between source 5G ProSe Layer-3 End UE and target 5G ProSe Layer-3 End UE. The source 5G ProSe Layer-3 End UE derives the end-to-end QoS parameters as defined in clause 5.6.1. The 5G ProSe Layer-3 UE-to-UE Relay, based on its implementation, decides the PQI for the first hop PC5 QoS control and the PQI for the second hop PC5 QoS control, by considering the received PC5 QoS parameters from the source 5G ProSe Layer-3 End UE. The 5G ProSe Layer-3 UE-to-UE Relay provides the QoS Info (including PQI value chosen by the 5G ProSe Layer-3 UE-to-UE Relay for the second hop) to the target 5G ProSe Layer-3 End UE. After accepted QoS Info of the second hop QoS from the target 5G ProSe Layer-3 End UE is received, 5G ProSe Layer-3 UE-to-UE Relay provides the QoS Info (including PQI value chosen by the 5G ProSe Layer-3 UE-to-UE Relay for the first hop) to the source 5G ProSe Layer-3 End UE with considering the received second hop QoS. If the source 5G ProSe Layer-3 End UE performs the Layer-2 link modification procedure to add new PC5 QoS Flow(s) or modify the existing PC5 QoS Flow(s) for IP traffic or Ethernet traffic over PC5 reference point, the source 5G ProSe Layer-3 End UE may also provide the PC5 QoS Rule(s) for the PC5 QoS Flow(s) to be added or modified to the 5G ProSe Layer-3 UE-to-UE Relay. The 5G ProSe Layer-3 UE-to-UE Relay may generate the Packet Filters used over the second hop based on the received PC5 QoS Rule(s). + +### 5.6.3.2 QoS handling for 5G ProSe Layer-2 UE-to-UE Relay + +For a 5G ProSe Layer-2 End UE connecting with another 5G ProSe Layer-2 End UE(s) via 5G ProSe Layer-2 UE-to-UE Relay, the source 5G ProSe Layer-2 End UE and the target 5G ProSe Layer-2 End UE negotiate the end-to-end QoS for the traffic transmission between source 5G ProSe Layer-2 End UE and target 5G ProSe Layer-2 End UE. + +**Editor's note:** It is FFS whether and how to perform QoS enforcement for first hop PC5 interface (between the source 5G ProSe Layer-2 End UE and 5G ProSe Layer-2 UE-to-UE Relay) and second hop PC5 interface (between the 5G ProSe Layer-2 UE-to-UE Relay and the target 5G ProSe Layer-2 End UE). + +## 5.7 Subscription to 5G ProSe + +The subscription information in the UDM contains information to give the user permission to use 5G ProSe. + +At any time, the operator can amend or remove the ProSe UE subscription rights from subscription information in the UDM, or to revoke the user's permission to use 5G ProSe. + +The following subscription information is defined for 5G ProSe: + +- subscription for open 5G ProSe Direct Discovery for NR PC5: + - open 5G ProSe Direct Discovery Model A. +- subscription for restricted 5G ProSe Direct Discovery for NR PC5: + - restricted 5G ProSe Direct Discovery Model A; + - restricted 5G ProSe Direct Discovery Model A with application-controlled extension; + - restricted 5G ProSe Direct Discovery Model A with "on demand" announcing; + +- restricted 5G ProSe Direct Discovery Model B. +- subscription for Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication for NR PC5. +- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-Network Relay. +- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-Network Relay. +- subscription for 5G ProSe Layer-2 Remote UE access via 5G ProSe Layer-2 UE-to-Network Relay. +- subscription for 5G ProSe Layer-3 Remote UE access via 5G ProSe Layer-3 UE-to-Network Relay. +- subscription for multi-path communication via direct Uu path and via 5G ProSe Layer 2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE. +- subscription for 5G ProSe UE acting as 5G ProSe Layer-2 UE-to-UE Relay. +- subscription for 5G ProSe UE acting as 5G ProSe Layer-3 UE-to-UE Relay. +- subscription for 5G ProSe Layer-2 End UE access via 5G ProSe Layer-2 UE-to-UE Relay. +- subscription for 5G ProSe Layer-3 End UE access via 5G ProSe Layer-3 UE-to-UE Relay. +- UE-PC5-AMBR for NR PC5. +- PC5 QoS parameters as defined in clause 5.6.1 used by NG-RAN. +- the list of the PLMNs authorized for 5G ProSe services, including: + - the list of the PLMNs where the UE is authorised for open 5G Direct Discovery Model A, i.e. to announce or monitor or both. + - the list of the PLMNs where the UE is authorised for restricted 5G ProSe Direct Discovery Model A, i.e. to announce or monitor or both. + - the list of the PLMNs where the UE is authorised for restricted 5G ProSe Direct Discovery Model B, i.e. to perform Discoverer operation or Discoveree operation or both. + - the list of the PLMNs where the UE is authorised to perform Broadcast, Groupcast and Unicast mode 5G ProSe Direct Communication for NR PC5. + - the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-Network Relay. + - the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-Network Relay. + - the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 Remote UE. + - the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 UE-to-UE Relay. + - the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 UE-to-UE Relay. + - the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-2 End UE. + - the list of the PLMNs where the UE is authorised to act as a 5G ProSe Layer-3 End UE. + +## 5.8 Identifiers + +### 5.8.1 Identifiers for 5G ProSe Direct Discovery + +#### 5.8.1.0 General + +NOTE: The 5G DDNMF takes the role of "ProSe Function" if it exists in the following definitions in TS 23.303 [3]. + +#### 5.8.1.1 ProSe Application ID + +ProSe Application ID is defined in TS 23.303 [3]. + +#### 5.8.1.2 Destination Layer-2 ID + +Destination Layer-2 ID is defined in clause 5.6.1 of TS 23.287 [2]. + +The Destination Layer-2 ID for 5G ProSe Direct Discovery with Model A is selected based on the configuration as described in clause 5.1.2.1. The Destination Layer-2 ID for a Solicitation message for Model B is selected based on the configuration as described in clause 5.1.2.1. + +For Group member discovery: + +- If an Application Layer Group ID has a configured Layer-2 Group ID, which is provisioned as specified in clause 5.1.2.1, the UE uses this Layer-2 Group ID as the Destination Layer-2 ID, +- otherwise, the UE converts the Application Layer Group ID into a Destination Layer-2 ID. + +NOTE: The mechanism for converting the application layer provided Application Layer Group ID to the Destination Layer-2 ID is defined in Stage 3. + +#### 5.8.1.3 Source Layer-2 ID + +Source Layer-2 ID is defined in clause 5.6.1 of TS 23.287 [2]. + +The UE self-selects a Source Layer-2 ID for 5G ProSe Direct Discovery and Group member discovery. + +NOTE: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication) in clauses 6.4, 6.5 and 6.7 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) with a different discovery model. + +#### 5.8.1.4 ProSe Application Code + +ProSe Application Code is defined in TS 23.303 [3]. + +#### 5.8.1.5 ProSe Restricted Code + +ProSe Restricted Code is defined in TS 23.303 [3]. + +#### 5.8.1.6 ProSe Query Code + +ProSe Query Code is defined in TS 23.303 [3]. + +#### 5.8.1.7 ProSe Response Code + +ProSe Response Code is defined in TS 23.303 [3]. + +#### 5.8.1.8 User Info ID + +User Info ID (including Announcer Info, Discoverer Info, Discoveree Info) is defined in clause 3.1. + +#### 5.8.1.9 ProSe Discovery UE ID + +ProSe Discovery UE ID is defined in TS 23.303 [3]. + +#### 5.8.1.10 Restricted ProSe Application User ID + +Restricted ProSe Application User ID is defined in TS 23.303 [3]. + +#### 5.8.1.11 Announcing PLMN ID + +Announcing PLMN ID is defined in TS 32.277 [22]. + +#### 5.8.1.12 Announcer Info + +Announcer Info is one of the uses of User Info ID as described in clause 5.8.1.8. + +#### 5.8.1.13 Discoverer Info + +Discoverer Info is one of the uses of User Info ID as described in clause 5.8.1.8. + +#### 5.8.1.14 Target Info + +Target Info provides information about the targeted discoveree in the Group Member Discovery Solicitation message specified in clause 6.3.2.2.3 and in the 5G ProSe UE-to-Network Relay Discovery Solicitation message specified in clause 6.3.2.3.3. The Target Info is the User Info ID of the discoveree. + +#### 5.8.1.15 Discoveree Info + +Discoveree Info is one of the uses of User Info ID as described in clause 5.8.1.8. + +#### 5.8.1.16 Application Layer Group ID + +Application Layer Group ID is defined in TS 23.303 [3]. + +### 5.8.2 Identifiers for 5G ProSe Direct Communication + +#### 5.8.2.1 General + +Each UE has one or more Layer-2 IDs for 5G ProSe direct communication over PC5 reference point, consisting of: + +- Source Layer-2 ID(s); and +- Destination Layer-2 ID(s). + +Source and Destination Layer-2 IDs are included in layer-2 frames sent on the layer-2 link of the PC5 reference point identifying the layer-2 source and destination of these frames. Source Layer-2 IDs are always self-assigned by the UE originating the corresponding layer-2 frames. + +The selection of the Source and Destination Layer-2 ID(s) by a UE depends on the communication mode of 5G ProSe direct communication over PC5 reference point for this layer-2 link, as described in clauses 5.8.2.2, 5.8.2.3 and 5.8.2.4. The Source Layer-2 IDs may differ between different communication modes. + +#### 5.8.2.2 Identifiers for broadcast mode 5G ProSe direct communication + +For broadcast mode of 5G ProSe direct communication over PC5 reference point, the UE is configured with the Destination Layer-2 ID(s) to be used for ProSe applications. The Destination Layer-2 ID for a 5G ProSe direct communication is selected based on the configuration as described in clause 5.1.3.1. + +The UE self-selects a Source Layer-2 ID. + +### 5.8.2.3 Identifiers for groupcast mode 5G ProSe direct communication + +For groupcast mode of 5G ProSe direct communication over PC5 reference point, the application layer may provide Application Layer Group ID. + +The UE determines a Destination Layer-2 ID as below: + +- When the Application Layer Group ID is provided by the application layer, + - and when ProSe Layer-2 Group ID is configured for the Application Layer Group ID provided by the application layer as specified in clause 5.1.3.1, the UE uses the ProSe Layer-2 Group ID as the Destination Layer-2 ID; or + - and when ProSe Layer-2 Group ID is not configured for the Application Layer Group ID provided by the application layer, the UE converts the Application Layer Group ID into a Destination Layer-2 ID. +- When the Application Layer Group ID is not provided by the application layer, the UE determines the Destination Layer-2 ID based on configuration of the mapping between ProSe Identifier and Layer-2 ID, as specified in clause 5.1.3.1. + +NOTE: The mechanism for converting the application layer provided Application Layer Group ID to the Destination Layer-2 ID is defined in Stage 3. + +The UE self-selects a Source Layer-2 ID. + +### 5.8.2.4 Identifiers for unicast mode 5G ProSe direct communication + +For unicast mode of 5G ProSe direct communication over PC5 reference point, the Destination Layer-2 ID used depends on the communication peer. The Layer-2 ID of the communication peer, identified by the peer's Application Layer ID, may be discovered during the establishment of the PC5 unicast link, or known to the UE via prior ProSe direct communications, e.g. existing or prior unicast link to the same Application Layer ID, or obtained from 5G ProSe direct discovery process. The initial signalling for the establishment of the PC5 unicast link may use the known Layer-2 ID of the communication peer, or a default destination Layer-2 ID associated with the ProSe service (i.e. ProSe identifier) configured for PC5 unicast link establishment, as specified in clause 5.1.3.1. During the PC5 unicast link establishment procedure, Layer-2 IDs are exchanged and should be used for future communication between the two UEs, as specified in clause 6.4.3. + +The UE maintains a mapping between the Application Layer IDs and the source Layer-2 IDs used for the PC5 unicast links, as the ProSe application layer does not use the Layer-2 IDs. This allows the change of source Layer-2 ID without interrupting the ProSe applications. + +When Application Layer IDs change, the source Layer-2 ID(s) of the PC5 unicast link(s) shall be changed if the link(s) was used for 5G ProSe communication with the changed Application Layer IDs. + +Based on privacy configuration as specified in clause 5.1.3.1, the update of the new identifiers of a source UE to the peer UE for the established unicast link may cause the peer UE to change its Layer-2 ID and optionally IP address/prefix if IP communication is used as defined in clause 6.4.3.2. + +## 5.8.3 Identifiers for 5G ProSe UE-to-Network Relay + +### 5.8.3.1 Common identifiers for 5G ProSe UE-to-Network Relay + +The following parameters are used for the 5G ProSe UE-to-Network Relay Discovery Announcement message (Model A), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Announcer Info and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery. +- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery is selected based on the configuration as described in clause 5.1.4.1. +- Announcer Info: provides information (i.e. User Info ID) about the announcing user. + +- Relay Service Code: parameter identifying a connectivity service the 5G ProSe UE-to-Network Relay provides to a 5G ProSe Remote UE. The Relay Service Codes are configured in a 5G ProSe UE-to-Network Relay for advertisement. Additionally, the Relay Service Code may also identifies authorized users the 5G ProSe UE-to-Network Relay would offer service to and may be used to select the related security policies or information e.g. necessary for authentication and authorization between the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay (e.g. a Relay Service Code for relays for police members only would be different than a Relay Service Code for relays for Fire Fighters only, even though potentially they provided connectivity to same DN e.g. to support Internet Access). + +The following parameters are used for the 5G ProSe UE-to-Network Relay Discovery Solicitation message (Model B), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Discoverer Info and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the 5G ProSe Remote-UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery. +- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery is selected based on the configuration as described in clause 5.1.4.1. +- Discoverer Info: provides information (i.e. User Info ID) about the discoverer user. +- Target Info: provides information (i.e. User Info ID) about the targeted discoveree user. +- Relay Service Code: information about connectivity that the discoverer UE is interested in. The Relay Service Codes are configured in the 5G ProSe Remote UEs interested in related connectivity services. + +The following parameters are used in the 5G ProSe UE-to-Network Relay Discovery Response message (Model B), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and Discoveree Info and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-Network Relay Discovery. +- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-Network Relay Discovery Solicitation message. +- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-Network Relay provides to 5G ProSe Remote UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message. +- Discoveree Info: provides information (i.e. User Info ID) about the discoveree. + +The following parameters may be used in the Relay Discovery Additional Information message (using Model A) based on the procedure defined in clause 6.5.1.3 for 5G ProSe UE-to-Network Relay where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and the other parameters are contained in the message: + +- Source Layer-2 ID: the 5G ProSe UE-to-Network Relay self-selects a Source Layer-2 ID to send the Relay Discovery Additional Information message. +- Destination Layer-2 ID: the Destination Layer-2 ID to send the Relay Discovery Additional Information message is selected based on the configuration as described in clause 5.1.4.1. +- Relay Service Code: the Relay Service Code associated with the message. The Relay Service Code is used to identify the security parameters needed by the receiving UE to process the discovery message. +- Announcer Info: provides information about the announcing user. +- Additional parameters: the additional parameters for 5G ProSe Layer-3 UE-to-Network Relay (when applicable) are defined in clause 5.8.3.2. + +NOTE: The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication) in clause 6.4 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery) with a different discovery model. + +### 5.8.3.2 Identifiers for 5G ProSe Layer-3 UE-to-Network Relay + +For 5G ProSe Layer-3 UE-to-Network relay, a Relay Service Code in the Announcement Message is associated with a set of PDU session parameters (e.g. PDU Session type, DNN, SSC Mode, S-NSSAI, Access Type Preference). The Relay Service Code may also represent if the relay UE can provide secure N3IWF connection. + +For 5G ProSe Layer-3 Remote UE discovering 5G ProSe Layer-3 UE-to-Network relay, the Relay Service Code in the Solicitation Message represents the PDU session parameters that a PDU session of the relay should be able to support. The Relay Service Code may also represent if the remote UE requires secure N3IWF connection. + +The following additional parameters may be used in the Relay Discovery Additional Information message (using Model A) for 5G ProSe Layer-3 UE-to-Network Relay: + +- NCGI: indicates the NCGI of the serving cell of the 5G ProSe Layer-3 UE-to-Network Relay. This parameter may be requested by application running on 5G ProSe Layer-3 Remote UE. +- TAI: indicates the Tracking Area Identity of the serving cell of the 5G ProSe Layer-3 UE-to-Network Relay. This parameter may be used by 5G ProSe Layer-3 Remote UE to select a N3IWF. + +### 5.8.3.3 Identifiers for 5G ProSe Layer-2 UE-to-Network Relay + +The following parameters may be used in Announcement message (Model A) or Response message (Model B) in addition to the parameters as specified in clause 5.8.3.1: + +- NCGI: indicates the NCGI of the serving cell of the 5G ProSe Layer-2 UE-to-Network Relay for 5G ProSe Layer-2 UE-to-Network Relay (re)selection. +- RRC Container: An RRC container, as defined in TS 38.331 [16], which includes the cell access related information for the serving cell of the 5G ProSe Layer-2 UE-to-Network Relay. + +## 5.8.4 Identifiers for 5G ProSe UE-to-UE Relay Discovery + +### 5.8.4.1 General + +The 5G ProSe UE-to-UE Relay Discovery message contains two sets of identifiers, a Direct Discovery set and a UE-to-UE Relay Discovery set. + +- The Direct Discovery set of identifiers are part of the contents of the 5G ProSe Direct Discovery message as defined in clause 5.8.1. +- The UE-to-UE Relay Discovery set of identifiers contain information to support the discovery of the 5G ProSe UE-to-UE Relay and extensions of the Direct Discovery. + +5G ProSe UE-to-UE Relay shall modify the UE-to-UE Relay Discovery set of identifiers and forward the Direct Discovery set and the UE-to-UE Relay Discovery set of identifiers during the discovery procedures. + +### 5.8.4.2 Common identifiers for 5G ProSe UE-to-UE Relay Discovery + +The following parameters are used for the 5G ProSe UE-to-UE Relay Discovery Announcement message (Model A), where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Announcement message. + +- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Announcement message is selected based on the configuration as described in clause 5.1.5.1. +- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay. +- list of User Info ID of 5G ProSe End UE: provides information about the 5G ProSe End UE. +- Relay Service Code: information to indicate the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs. + +The following parameters are used for the 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) between discoverer 5G ProSe End UE and 5G ProSe UE-to-UE Relay, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the discoverer 5G ProSe End UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message. +- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message is selected based on the configuration as described in clause 5.1.5.1. +- User Info ID of discoverer 5G ProSe End UE: provides information about the discoverer 5G ProSe End UE. +- User Info ID of discoveree 5G ProSe End UE: provides information about the discoveree 5G ProSe End UE. +- Relay Service Code: information about connectivity service that the discoverer 5G ProSe End UE is interested in. + +The following parameters are used in the 5G ProSe UE-to-UE Relay Discovery Response message (Model B) between discoverer 5G ProSe End UE and 5G ProSe UE-to-UE Relay, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Response message. +- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Solicitation message. +- User Info ID of discoveree 5G ProSe End UE: provides information about the discoveree 5G ProSe End UE. +- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay. +- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message. + +The following parameters are used for the 5G ProSe UE-to-UE Relay Discovery Solicitation message (Model B) between 5G ProSe UE-to-UE Relay and discoveree 5G ProSe End UE, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the 5G ProSe UE-to-UE Relay self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message. +- Destination Layer-2 ID: the Destination Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Solicitation message is selected based on the configuration as described in clause 5.1.5.1. +- User Info ID of discoverer 5G ProSe End UE: provides information about the discoverer 5G ProSe End UE. +- User Info ID of discoveree 5G ProSe End UE: provides information about the discoveree 5G ProSe End UE. +- User Info ID of 5G ProSe UE-to-UE Relay: provides information about the 5G ProSe UE-to-UE Relay. +- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs. + +The following parameters are used in the 5G ProSe UE-to-UE Relay Discovery Response message (Model B) between 5G ProSe UE-to-UE Relay and discoveree 5G ProSe End UE, where Source Layer-2 ID and Destination Layer-2 ID are used for sending and receiving the message and User Info ID and Relay Service Code are contained in the message: + +- Source Layer-2 ID: the discoveree 5G ProSe End UE self-selects a Source Layer-2 ID for 5G ProSe UE-to-UE Relay Discovery Response message. +- Destination Layer-2 ID: set to the Source Layer-2 ID of the received 5G ProSe UE-to-UE Relay Discovery Solicitation message. +- User Info ID of discoveree 5G ProSe End UE: provides information about the discoveree 5G ProSe End UE. +- User Info ID of discoverer 5G ProSe End UE: provides information about the discoverer 5G ProSe End UE. +- Relay Service Code: identifies the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs that matches the Relay Service Code from the corresponding Discovery Solicitation message. + +**NOTE:** The UE implementation needs to ensure that when the UE self-selects Source Layer-2 IDs, the self-selected Source Layer-2 IDs are different between 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) in clause 6.3.2 and 5G ProSe Direct Communication (including 5G ProSe UE-to-Network Relay Communication and 5G ProSe UE-to-UE Relay Communication) in clause 6.4, 6.5 and 6.7 and are different from any other provisioned Destination Layer-2 IDs as described in clause 5.1 and any other self-selected Source Layer-2 IDs used in a simultaneous 5G ProSe Direct Discovery (including 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-UE Relay Discovery) with a different discovery model. + +### 5.8.5 Identifiers for 5G ProSe UE-to-UE Relay Communication with integrated Discovery + +For the broadcast Direct Communication Request message over the first hop PC5 reference point, the Source Layer-2 ID is self-selected by the source 5G ProSe End UE and the Destination Layer-2 ID is selected based on the configuration as described in clause 5.1. + +For the broadcast Direct Communication Request message over the second hop PC5 reference point, the Source Layer-2 ID is self-selected by the 5G ProSe UE-to-UE Relay and the Destination Layer-2 ID is selected based on the configuration as described in clause 5.1. + +5G ProSe UE-to-UE Relay may send a unicast Direct Communication Request message to the target 5G ProSe End UE by setting the Destination Layer-2 ID with a received unicast Destination Layer-2 ID of the target 5G ProSe End UE as specified in clause 6.4.3.7. The Source Layer-2 ID is self-selected by the 5G ProSe UE-to-UE Relay. + +For unicast Direct Communication Accept message, the Source Layer-2 ID is self-selected by the target 5G ProSe End UE or 5G ProSe UE-to-UE Relay. + +## 5.9 Support for 5G ProSe for UEs in limited service state + +For UE in limited service state, as defined in TS 23.122 [14], 5G ProSe can be used over PC5 reference point with the following considerations. + +UEs that are authorized to use 5G ProSe over PC5 reference point according to clause 5.1 shall be able to use the corresponding services following the principles defined in clause 5.1.2.2 for 5G ProSe Direct Discovery, clause 5.1.3.2 for 5G ProSe Direct Communication, clause 5.1.4.2 for 5G ProSe UE-to-Network Relay and clause 5.1.5.2 for 5G ProSe UE-to-UE Relay when the UE enters in limited service state in 5GS: + +- because UE cannot find a suitable cell of the selected PLMN as described in TS 23.122 [14]; or +- as the result of receiving one of the following reject reasons defined in TS 23.122 [14]: + - a "PLMN not allowed" response to a registration request or; + - a "5GS services not allowed" response to a registration request or service request. + +A UE in limited service state shall only use the radio resources and procedure available in CM-IDLE mode for ProSe over PC5 reference point, for details see TS 36.300 [11] and TS 38.300 [12]. + +UEs shall not use 5G ProSe over PC5 reference point using the "operator-managed" radio resources, as specified in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1, if the UE has entered in limited service state due to all other situations (e.g. no SIM in the MS, an "illegal MS" or "illegal ME" response to a registration request, or an "IMSI unknown in HLR" response to a registration request) defined in TS 23.122 [14], where the UE is unable to obtain normal service from a PLMN. The UEs may use ProSe over PC5 reference point using the "non-operator-managed" radio resources, as specified in clauses 5.1.2.1, 5.1.3.1, 5.1.4.1 and 5.1.5.1, according to the corresponding principles defined in clauses 5.1.2.2, 5.1.3.2, 5.1.4.2 and 5.1.5.2. + +## 5.10 PC5 operation in EPS for Public Safety UE + +When the UE is in EPS, the UE shall use the valid ProSe policy and parameters provisioned by the ProSe Function in EPC for ProSe Direct Discovery and Prose Direct Communication. If the UE does not have valid ProSe policy and parameters, the UE shall request the network to provision the ProSe policy and parameters. + +The UE that is authorized to perform ProSe Direct Discovery and/or ProSe Direct Communication in EPS can perform the authorized PC5 operation in EPS as specified in TS 23.303 [3]. + +## 5.11 Communication path selection between PC5 and Uu reference points + +The "communication path selection between PC5 and Uu reference points" refers to the procedure on how a UE selects a communication path between PC5 reference point and Uu reference point before it communicates with another UE. The communication path over PC5 reference point means that the communication with another UE is performed by using 5G ProSe Direct Communication only. The communication path over Uu reference point means that the communication with another UE is performed via the network. + +NOTE 1: The communication via 5G ProSe UE-to-Network Relay (Layer-2 or Layer-3) can be considered as the communication path over Uu reference point, as it involves communication via the network. + +Path selection policy is provided to the UE to indicate which path(s) is preferred for all or specific ProSe services (i.e. PC5 preferred, Uu preferred or no preference indicated) as specified in clause 5.1.3.1. + +The ProSe Application Server can provide a path preference for ProSe Services to UDR as specified in clause 6.2.5 and this may be used by PCF for path selection policy generation and update as specified in clause 6.2.2. + +NOTE 2: ProSe Application Server can use QoS Sustainability analytics defined in TS 23.288 [8] to determine the path preference. + +The UE may use the provisioned path selection policy to select the appropriate communication path for all or specific ProSe services. + +UE operation related to the path selection for ProSe service is as follows: + +- The UE evaluates the path selection policy in the policy and parameters for ProSe Direct Communication applicable to the ProSe service and selects the communication path as below: + - If PC5 preferred is indicated, the UE should prefer to use the PC5 for communication path for the ProSe service. + - If Uu preferred is indicated, the UE should prefer to use the Uu for communication path for the ProSe service. + - If no preference is indicated or no path selection policy is provisioned, the UE selects either a Uu or PC5 communication path based on its pre-configuration or implementation for the ProSe service. + +NOTE 3: When either PC5 preferred or Uu preferred is indicated, the UE can still select the other non-preferred path, e.g. because the peer UE is not in proximity. + +## 5.12 NAS level congestion control for 5G ProSe UE-to-Network Relay + +The 5G ProSe UE-to-Network Relay may be subject to NAS level congestion control, as specified in clause 5.19.7 of TS 23.501 [4]. + +Both 5G ProSe Layer-2 UE-to-Network Relays and Layer-3 UE-to-Network Relays, when NAS Mobility Management congestion control as specified in clause 5.19.7.2 of TS 23.501 [4] is activated, i.e. the 5G ProSe UE-to-Network Relay receives a Mobility Management back-off timer from the AMF, the 5G ProSe UE-to-Network Relay is not able to serve the 5G ProSe Remote UE after the 5G ProSe UE-to-Network Relay enters CM\_IDLE state. If the 5G ProSe UE-to-Network Relay has a Mobility Management back-off timer when it enters CM\_IDLE state the 5G ProSe UE-to-Network Relay releases the PC5 connections with its 5G ProSe Remote UEs indicating it is temporarily not available, so the Remote UE can (re)select another 5G ProSe UE-to-Network Relay. The 5G ProSe UE-to-Network Relay does not perform UE-to-Network Relay Discovery as described in clause 6.3.2.3 and does not accept any PC5 connections for relaying until the back-off timer expires if the 5G ProSe UE-to-Network Relay is in CM\_IDLE state. + +A Remote UE may also be subject to NAS level congestion control as specified in TS 23.501 [4]. + +NOTE: The form of the temporarily not available indication will be determined by stage 3. + +## 5.13 Support for PC5 DRX operations + +### 5.13.1 General + +PC5 DRX operations are supported to enable 5G ProSe-enabled UE power saving for the following functions: + +- 5G ProSe Direct Discovery; +- Unicast, groupcast and broadcast mode 5G ProSe Direct Communication; +- 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communication. + +Support for PC5 DRX operations in the AS layer is specified in TS 38.300 [12]. + +### 5.13.2 PC5 DRX operations for 5G ProSe Direct Discovery and 5G ProSe UE-to-Network Relay Discovery + +For 5G ProSe Direct Discovery and 5G ProSe UE-to-Network Relay Discovery when the UE is "not served by NG-RAN", the UE uses the provisioned default PC5 DRX configuration for PC5 DRX operation as specified in clause 5.1.2.1 and clause 5.1.4.1, respectively. + +### 5.13.3 PC5 DRX operations for 5G ProSe Direct Communication and 5G ProSe UE-to-Network Relay Communication + +The ProSe layer determines the respective ProSe services (i.e. ProSe identifiers) and derives the corresponding PC5 QoS parameters based on either the mapping of ProSe services (i.e. ProSe identifiers) to PC5 QoS parameters, or the ProSe Application Requirements for the ProSe services (i.e. ProSe identifiers) provided by the application layer. For broadcast and groupcast, the ProSe layer also determines the NR Tx Profile based on the mapping of ProSe services (i.e. ProSe identifiers) to NR Tx Profiles as described in clause 5.1.3.1. The ProSe layer passes the PC5 QoS parameters and destination Layer-2 ID to the AS layer as specified in clauses 6.4.1, 6.4.2 and 6.4.3. The ProSe layer also passes the corresponding NR Tx Profile to the AS layer, if the ProSe layer has determined the corresponding NR Tx Profile. + +NOTE: For broadcast and groupcast, the AS layer needs PC5 QoS parameters as well to determine the PC5 DRX parameter values for reception operation over PC5 reference point. Therefore, the ProSe layer determines the interested ProSe services (i.e. ProSe identifiers) and derives the PC5 QoS parameters based on its reception needs besides the transmission needs. How to derive the PC5 QoS parameters based on its reception needs (e.g. without establishing the PC5 QoS Flows) depends on UE implementation. + +For broadcast or groupcast, the ProSe layer maintains a list of all ProSe services (i.e. ProSe identifiers), i.e. activated ProSe services and/or ProSe services that the UE is interested for reception, for a given destination Layer-2 ID and determines the NR Tx Profile to be mapped for the respective ProSe service based on the configuration described in clause 5.1.3.1. Whenever the list of the ProSe services for a given destination Layer-2 ID changes, the ProSe layer updates the AS layer for the NR Tx Profiles information by providing all the mapped NR Tx Profiles to the AS layer for the given destination Layer-2 ID, e.g. when providing other information such as the destination Layer-2 ID, PC5 QoS parameters. + +For broadcast, the mapping from destination Layer-2 ID to NR Tx Profile is configured in the NG-RAN. The NG-RAN may derive the NR Tx Profile from the destination Layer-2 ID to perform the network scheduled operation mode, alignment of Uu DRX and PC5 DRX, etc. + +When the PC5 DRX operation is needed, the AS layer determines the PC5 DRX parameter values for 5G ProSe Direct Communication or 5G ProSe UE-to-Network Relay Communication over PC5 reference point, taking into account, e.g., PC5 QoS parameters and/or destination Layer-2 ID provided by the ProSe layer. + +For broadcast and groupcast, the UE enables the PC5 DRX based on the NR Tx Profile. + +For unicast mode 5G ProSe Direct Communication and 5G ProSe UE-to-Network Relay Communication, two UEs may negotiate the PC5 DRX configuration in the AS layer and the PC5 DRX parameter values can be configured per pair of source and destination Layer-2 IDs in the AS layer. For transmitting and receiving Direct Communication Request messages, a default PC5 DRX configuration may be used (see TS 38.300 [12]). + +For broadcast and groupcast when the UE is "not served by NG-RAN", the UE uses the provisioned PC5 DRX configuration for PC5 DRX operation as specified in clause 5.1.3.1. + +## 5.14 5G ProSe UE-to-UE Relay Communication + +### 5.14.1 5G ProSe Layer-3 UE-to-UE Relay Communication + +The 5G ProSe Layer-3 UE-to-UE Relay shall provide generic function that can relay any IP, Ethernet or Unstructured traffic. + +The 5G ProSe Layer-3 UE-to-UE Relay provides the functionality to support connectivity between 5G ProSe Layer-3 End UEs. A 5G ProSe Layer-3 UE-to-UE Relay and 5G ProSe Layer-3 End UEs can be located within NG-RAN coverage or outside of NG-RAN coverage. + +The type of traffic supported over PC5 reference point is indicated by the 5G ProSe Layer-3 UE-to-UE Relay e.g. using the corresponding RSC. + +### 5.14.2 5G ProSe Layer-2 UE-to-UE Relay Communication + +The 5G ProSe Layer-2 UE-to-UE Relay provides forwarding functionality that can relay any type of traffic over the PC5 link. + +The 5G ProSe Layer-2 UE-to-UE Relay provides the functionality to support connectivity between 5G ProSe Layer-2 End UEs. A 5G ProSe Layer-2 UE-to-UE Relay and 5G ProSe Layer-2 End UEs can be located within NG-RAN coverage or outside of NG-RAN coverage. + +## 5.15 Path switching between two UE-to-Network Relays + +If relay reselection has been triggered (see clause 6.5.3), the 5G ProSe Remote UE performs the path switching between two UE-to-Network Relays based on the URSP rules of the 5G ProSe Remote UE traffic handling described in clause 6.5.4, 5G ProSe Policy in clause 5.1.4, or information from application layer (if available) with following considerations: + +- The 5G ProSe Remote UE shall first select the target path which has same type with the original path (i.e. 5G ProSe Layer-2 UE-to-Network Relay, 5G ProSe Layer-3 UE-to-Network Relay with N3IWF and 5G ProSe Layer-3 UE-to-Network Relay without N3IWF). + +- If the same type target path is not available, then this 5G ProSe Remote UE re-evaluates the URSP as specified in clause 6.5.4, or 5G ProSe Policy in clause 5.1.4 for the target path selection. + +NOTE: If there is the information from the application layer (e.g. provided by an application server), the 5G ProSe Remote UE can use this information to discover the target 5G ProSe UE-to-Network Relay UE. If there are multiple discovered 5G ProSe UE-to-Network Relay UEs, the 5G ProSe Remote UE selects the target 5G ProSe UE-to-Network Relay based on the priority, if any, in the information from the application layer. + +The principles from the 5G ProSe Policy in clause 5.1.4 and URSP rules of the 5G ProSe Remote UE traffic handling described in clause 6.5.4 take the higher priority than the information from the application layer. + +The path switching procedures between two indirect network communication paths are as described in clause 6.5.5. + +## 5.16 Communication path switching between PC5 and Uu reference points + +The "communication path switching between PC5 and Uu reference points" refers to the procedure on how a UE switches between Uu communication path and direct PC5 communication path when it is communicating with another UE as illustrated in Figure 5.16-1. The direct communication path over PC5 reference point means that the communication with another UE is performed by using 5G ProSe Direct Communication only. The communication path over Uu reference point means that the communication with another UE is performed via the network. + +![Figure 5.16-1: Example scenario of communication path switching between PC5 and Uu reference points. The diagram shows two scenarios: (a) Uu Path and (b) PC5 Path. In both, a Data Network is connected to a 5GC, which is connected to two NG-RANs. In (a), UE 1 and UE 2 are connected to the NG-RANs via Uu reference points. In (b), UE 1 and UE 2 are connected to the NG-RANs via Uu reference points, but they are also connected to each other via a PC5 reference point.](f796c4b6ef101faa39b887a86820c3d1_img.jpg) + +The diagram illustrates two communication path scenarios between two User Equipment (UE) units, UE 1 and UE 2, through a 5G Core (5GC) and Network Radio Access Network (NG-RAN) units. Both UEs are connected to the 5GC via their respective NG-RANs. In scenario (a), labeled 'Uu Path', the communication between UE 1 and UE 2 is routed through the 5GC and the NG-RANs via the Uu reference points. In scenario (b), labeled 'PC5 Path', the communication between UE 1 and UE 2 is routed directly between the UEs via the PC5 reference point, bypassing the 5GC and NG-RANs for the data path. Both scenarios show the Data Network connected to the 5GC via the N6 interface. + +Figure 5.16-1: Example scenario of communication path switching between PC5 and Uu reference points. The diagram shows two scenarios: (a) Uu Path and (b) PC5 Path. In both, a Data Network is connected to a 5GC, which is connected to two NG-RANs. In (a), UE 1 and UE 2 are connected to the NG-RANs via Uu reference points. In (b), UE 1 and UE 2 are connected to the NG-RANs via Uu reference points, but they are also connected to each other via a PC5 reference point. + +**Figure 5.16-1: Example scenario of communication path switching between PC5 and Uu reference points (i.e. switching between Figure a and Figure b)** + +Communication path switching between PC5 and Uu reference points is performed at ProSe service level, e.g. some of ProSe services of PC5 unicast link or PDU Session, all ProSe services of PC5 unicast link or PDU Session. + +The UE takes the path selection policy into account to determine whether and for which ProSe service(s) to switch the communication path. UE operation related to the path switch for ProSe service is as follows: + +- The UE evaluates the path selection policy in the policy and parameters for ProSe Direct Communication applicable to the ProSe service and switches the communication path as below: + - If the Uu path is used and PC5 preferred is indicated, the UE should prefer to switch to the PC5 communication path for the ProSe service. + - If the PC5 path is used and Uu preferred is indicated, the UE should prefer to switch to the Uu communication path for the ProSe service. + - If no preference is indicated or no path selection policy is provisioned, the UE switches between Uu and PC5 communication path based on its pre-configuration or implementation for the ProSe service. + +NOTE 1: When either PC5 preferred or Uu preferred is indicated, the UE can still switch to the other non-preferred path, e.g. signal strength of any path below a certain configured signal strength threshold. + +The UE may decide to perform path switching from Uu path to PC5 path, e.g. because the peer UE is in proximity or for offloading some traffic from the network. The UE may decide to perform path switching from PC5 path to Uu path, e.g. when the PC5 signal strength of the unicast link with the peer UE becomes weak. + +At path switching, the same traffic type between for PDU Session and for PC5 unicast link is maintained, i.e. IP type, Ethernet type and Unstructured type. + +For communication path switching from PC5 to Uu reference point, the Uu QoS parameters of each UE are decided based on PC5 QoS parameters and negotiated via the existing PC5 connection between two UEs. Each UE may perform the UE requested PDU Session Modification as defined in TS 23.502 [5] clause 4.3.3 to request the Uu QoS parameters. For IP type traffic, the IP addresses/prefixes of the peer UEs over the Uu reference point can be shared via the existing PC5 connection between the UEs by using application layer signalling to assist them to establish communication with each other via the communication path over the Uu reference point. + +When both Uu path and PC5 path are available, a make-before-break mechanism is used when switching between PC5 path and Uu path. That is, the UEs first prepare the target path to communicate with each other and then perform the path switching and communicate over the target path and after this the former path may be released. + +NOTE 2: It is not targeted to support session continuity (e.g. IP address preservation) during path switching between PC5 and Uu reference points. + +## 5.17 Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay + +### 5.17.1 General + +Multi-path communication uses one direct network communication path and one indirect network communication path with UE-to-Network Relay as illustrated in Figure 5.17.1-1, where path #1 shows the direct communication path via Uu and path #2 is shows the indirect communication path via 5G ProSe UE-to-Network Relay. + +![Diagram illustrating multi-path communication via Uu and via 5G ProSe UE-to-Network Relay. A UE is connected to a Network via two paths: Path #1 is a direct Uu path, and Path #2 is an indirect path via a UE-to-Network Relay.](1e56c223f51992d193febf7a161af7be_img.jpg) + +``` + +graph LR + UE[UE] -- "#1" --- Network[Network] + UE -- "#2" --- UNR[UE-to-Network Relay] + UNR --- Network + +``` + +Diagram illustrating multi-path communication via Uu and via 5G ProSe UE-to-Network Relay. A UE is connected to a Network via two paths: Path #1 is a direct Uu path, and Path #2 is an indirect path via a UE-to-Network Relay. + +Figure 5.17.1-1: Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay + +The indirect communication path may be via a 5G ProSe Layer-2 UE-to-Network Relay, or via a 5G ProSe Layer-3 UE-to-Network Relay with or without N3IWF. + +### 5.17.2 Multi-path communication via direct Uu path and via 5G ProSe Layer-3 UE-to-Network Relay + +A 5G ProSe Layer-3 Remote UE may access the network via a 5G ProSe Layer-3 UE-to-Network Relay with or without N3IWF. + +When a 5G ProSe Layer-3 Remote UE accesses the network via a 5G ProSe Layer-3 UE-to-Network Relay without N3IWF, the multi-path communication via direct Uu path and via the UE-to-Network Relay may be applied to the application traffic. + +When a 5G ProSe Layer-3 Remote UE accesses the network via a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF, the Layer-3 Remote UE connection via Layer-3 UE-to-Network Relay with N3IWF is considered as "untrusted + +non-3GPP access to 5GC via N3IWF", therefore the multi-path communication can be achieved using MA PDU Session in ATSSS features specified in clause 5.32 of TS 23.501 [4]. + +NOTE: MA PDU Session requires ATSSS Information in SM subscription data as specified in TS 23.502 [5]. + +## 5.18 Support of Public Warning Notification Relaying + +As specified in TS 22.268 [33], if UE that is authorised to act as 5G ProSe UE-to-Network Relay receives Public Warning Notification from the network and the UE is configured to perform Public Warning relaying, it shall handle the Public Warning message acting in the role of 5G ProSe UE-to-Network Relay. + +The 5G ProSe UE-to-Network Relay broadcasts the warning message i.e. SIB 6/7/8 received from the network to the 5G ProSe Remote UE(s) by using Broadcast mode of 5G ProSe direct communication as specified in clause 5.3.2. The 5G ProSe UE-to-Network Relay uses a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1 when broadcasting the warning message and the 5G ProSe Remote UE receives warning messages broadcasted over PC5 reference point by using a configured Destination Layer-2 ID(s) as specified in clause 5.1.4.1. The PC5 QoS parameters as specified in clause 5.1.4.1 are used to broadcast and receive the warning message for the 5G ProSe UE-to-Network Relay and the 5G ProSe Remote UE, respectively. + +A 5G ProSe Remote UE can receive the broadcasted warning message without establishing a connection to the 5G ProSe UE-to-Network Relay. + +The 5G ProSe UE-to-Network Relay performs the duplication detection function as specified in TS 23.041 [32] to suppress the received duplicated warning messages over Uu. The 5G ProSe UE-to-Network Remote UE performs the duplication detection function as specified in TS 23.041 [32] to detect duplicated warning messages received over PC5 and/or Uu. + +NOTE: The duplication detection function in the 5G ProSe UE-to-Network Relay avoids broadcasting the duplicated warning message over PC5. + +If the 5G ProSe Layer-2 UE-to-Network Relay does not have Destination Layer-2 ID to broadcast Public Warning messages, the 5G ProSe Layer-2 UE-to-Network Relay forwards the PWS SIBs (i.e. SIB 6/7/8) to a connected 5G ProSe Layer-2 Remote UE over the unicast link as specified in TS 38.300 [12]. + +The Public Warning System architecture for 5G System is specified in TS 23.041 [32]. + +--- + +## 6 Functional description and information flows + +### 6.1 Control and user plane stacks + +#### 6.1.1 Control Plane + +##### 6.1.1.1 General + +The control plane stack consists of protocols for controlling: + +- 5G ProSe Direct Discovery, specified in clause 6.1.1.2.1, clause 6.1.1.3, clause 6.1.1.4, clause 6.1.1.5 and clause 6.1.1.6; +- 5G ProSe Direct Communication, specified in clause 6.1.1.2.2; +- 5G ProSe UE-to-Network Relay, specified in clause 6.1.1.7; +- 5G ProSe UE-to-UE Relay, specified in clause 6.1.1.8. + +### 6.1.1.2 UE - UE + +#### 6.1.1.2.1 Discovery plane PC5 interface + +The PC5 communication channel is used to carry the discovery messages over PC5 which are differentiated from other PC5 messages by the AS layer. + +Figure 6.1.1.2.1-1 depicts a discovery plane for NR PC5 reference point. + +![Diagram of the Discovery Plane PC5 Interface showing the protocol stacks for UE A and UE B.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +The diagram illustrates the Discovery Plane PC5 Interface between UE A and UE B. Both User Equipment (UE) are represented by dashed boxes containing their respective protocol stacks. The stacks are identical and consist of five layers: ProSe Discovery protocol, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the corresponding layers of UE A and UE B, indicating bidirectional communication. The entire stack is labeled PC5-D at the bottom center. + +Diagram of the Discovery Plane PC5 Interface showing the protocol stacks for UE A and UE B. + +#### Legend: + +- **PC5-D:** The PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [12]. +- The "ProSe Discovery protocol" is used for handling ProSe Direct Discovery as specified in clause 6.3.2. + +**Figure 6.1.1.2.1-1: Discovery Plane PC5 Interface** + +#### 6.1.1.2.2 PC5 Signalling Protocol + +The PC5 Signalling Protocol stack specified in clause 6.1.2 of TS 23.287 [2] is used. The protocol used for the control plane signalling over the PC5 reference point for the secure layer-2 link is specified in clauses 6.4.3, 6.5.1 and 6.5.2. + +### 6.1.1.3 UE - 5G DDNMF + +![Figure 6.1.1.3-1 Control Plane for PC3a Interface. The diagram shows the protocol stack for the PC3a interface between a UE and a 5G DDNMF. The UE side includes PC3 Control, IP, and 5G-AN Protocol Layers. The 5G AN side includes 5G-AN Protocol Layers, GTP/U, UDP/IP, L2, and L1. The UPF side includes two Relay blocks, each containing GTP/U, UDP/IP, L2, and L1. The UPF (PDU session anchor) side includes IP, GTP/U, UDP/IP, L2, and L1. The 5G DDNMF side includes PC3 Control, IP, L2, and L1. The interfaces are labeled N3, N9, and N6. A dashed line labeled PC3a indicates the control plane signaling path.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +Figure 6.1.1.3-1 Control Plane for PC3a Interface. The diagram shows the protocol stack for the PC3a interface between a UE and a 5G DDNMF. The UE side includes PC3 Control, IP, and 5G-AN Protocol Layers. The 5G AN side includes 5G-AN Protocol Layers, GTP/U, UDP/IP, L2, and L1. The UPF side includes two Relay blocks, each containing GTP/U, UDP/IP, L2, and L1. The UPF (PDU session anchor) side includes IP, GTP/U, UDP/IP, L2, and L1. The 5G DDNMF side includes PC3 Control, IP, L2, and L1. The interfaces are labeled N3, N9, and N6. A dashed line labeled PC3a indicates the control plane signaling path. + +#### Legend: + +- ProSe Control Signalling between UE and 5G DDNMF is carried over the user plane and using the PC3a protocol as specified in TS 24.554 [23]. + +NOTE 1: PC3a may be realized with one or more protocols. + +NOTE 2: If 5G DDNMF is integrated with ProSe Application Server, 5G DDNMF provides PC3a interface towards UE and ProSe Application Server provides PC1 interface towards UE. + +**Figure 6.1.1.3-1 Control Plane for PC3a Interface** + +### 6.1.1.4 5G DDNMF – UDM + +5G DDNMF uses Nudm interface defined in TS 23.501 [4] to obtain the UE's subscription information for the authorization of the 5G ProSe Direct Discovery requests. + +### 6.1.1.5 5G DDNMF – 5G DDNMF + +The control plane protocol(s) between 5G DDNMFs are defined in TS 29.500 [30]. + +The 5G DDNMFs uses N5g-ddnmf 5G DDNMF services defined in clause 7.1 to access the services provided by the other 5G DDNMF(s). The 5G DDNMF in HPLMN uses NRF to discover the 5G DDNMFs in VPLMN and Local PLMNs. + +### 6.1.1.6 5G DDNMF – ProSe Application Server + +The 5G System architecture supports the service based Npc2 interface between 5G DDNMF and ProSe Application Server and optionally supports PC2 interface between 5G DDNMF and ProSe Application Server, to enable Proximity Services. See TS 23.501 [4] and TS 23.303 [3]. + +NOTE: PC2 support between 5G DDNMF and ProSe Application Server is for backwards compatibility for early deployments using Diameter. PC2 interface is used for 5G ProSe Direct Discovery authorization. + +### 6.1.1.7 5G ProSe UE-to-Network Relay + +#### 6.1.1.7.1 5G ProSe Layer-3 UE-to-Network Relay + +The UE-UE protocol stacks for discovery and PC5 link management as defined in clause 6.1.1.2 apply to 5G ProSe Remote UE and 5G ProSe Layer-3 UE-to-Network Relay. + +Additionally, when N3IWF is supported by the 5G ProSe Layer-3 UE-to-Network Relay, the following control plane protocol stack apply. + +![Figure 6.1.1.7.1-1: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay before the signalling IPSec SA is established. The diagram shows the protocol stack for NAS, EAP-5G, IKEv2, IP, and PCS between the Remote UE and the N3IWF, with a UE-to-Network Relay and NG-RAN in between. The stack at the Remote UE includes NAS, EAP-5G, IKEv2, IP, and PCS. The stack at the UE-to-Network Relay includes IP-Relay, PCS, and Uu. The stack at the NG-RAN includes Uu, Relay, and N3 stack. The stack at the UPF includes IP, N3 stack, and L2/L1. The stack at the N3IWF includes EAP-5G, IKEv2, IP, and L2/L1. The stack at the AMF includes NAS, N2 stack, and N2.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +Figure 6.1.1.7.1-1: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay before the signalling IPSec SA is established. The diagram shows the protocol stack for NAS, EAP-5G, IKEv2, IP, and PCS between the Remote UE and the N3IWF, with a UE-to-Network Relay and NG-RAN in between. The stack at the Remote UE includes NAS, EAP-5G, IKEv2, IP, and PCS. The stack at the UE-to-Network Relay includes IP-Relay, PCS, and Uu. The stack at the NG-RAN includes Uu, Relay, and N3 stack. The stack at the UPF includes IP, N3 stack, and L2/L1. The stack at the N3IWF includes EAP-5G, IKEv2, IP, and L2/L1. The stack at the AMF includes NAS, N2 stack, and N2. + +#### Legend: + +- NAS, EAP-5G and IKEv2 between the Remote UE and the N3IWF are defined in clause 8.2.4 of TS 23.501 [4]. + +**Figure 6.1.1.7.1-1: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay before the signalling IPSec SA is established** + +![Figure 6.1.1.7.1-2: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay after the signalling IPSec SA is established. This diagram is similar to Figure 6.1.1.7.1-1 but replaces IKEv2 with TCP and Inner IP. The stack at the Remote UE includes NAS, TCP, Inner IP, IPsec(Tunnel mode), IP, and PCS. The stack at the UE-to-Network Relay includes IP-Relay, PCS, and Uu. The stack at the NG-RAN includes Uu, Relay, and N3 stack. The stack at the UPF includes IP, N3 stack, and L2/L1. The stack at the N3IWF includes TCP, Inner IP, IPsec(Tunnel mode), IP, and L2/L1. The stack at the AMF includes NAS, N2 stack, and N2.](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) + +Figure 6.1.1.7.1-2: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay after the signalling IPSec SA is established. This diagram is similar to Figure 6.1.1.7.1-1 but replaces IKEv2 with TCP and Inner IP. The stack at the Remote UE includes NAS, TCP, Inner IP, IPsec(Tunnel mode), IP, and PCS. The stack at the UE-to-Network Relay includes IP-Relay, PCS, and Uu. The stack at the NG-RAN includes Uu, Relay, and N3 stack. The stack at the UPF includes IP, N3 stack, and L2/L1. The stack at the N3IWF includes TCP, Inner IP, IPsec(Tunnel mode), IP, and L2/L1. The stack at the AMF includes NAS, N2 stack, and N2. + +#### Legend: + +- NAS, TCP and IPsec between the Remote UE and the N3IWF are defined in TS 23.501 [4] clause 8.2.4. + +**Figure 6.1.1.7.1-2: Control plane protocol stacks between 5G ProSe Layer-3 Remote UE and N3IWF over 5G ProSe Layer-3 UE-to-Network Relay after the signalling IPSec SA is established** + +### 6.1.1.7.2 5G ProSe Layer-2 UE-to-Network Relay + +The UE-UE protocol stacks for discovery and PC5 signalling defined in clause 6.1.1.2 apply to 5G ProSe Remote UE and 5G ProSe Layer-2 UE-to-Network Relay. + +Figure 6.1.1.7.2-1 illustrates the protocol stack of the NAS connection for the 5G ProSe Layer-2 Remote UE for NAS-MM and NAS-SM. The NAS messages are transparently transferred between the 5G ProSe Layer-2 Remote UE and NG-RAN over the 5G ProSe Layer-2 UE-to-Network Relay using: + +- PDCP end-to-end connection between the 5G ProSe Layer-2 Remote UE and NG-RAN, where the role of the 5G ProSe Layer-2 UE-to-Network Relay is to relay the PDUs over the signalling radio bear without any modifications and using the functionality of the adaptation layer as specified in TS 38.300 [12]. +- Connection between NG-RAN and AMF over N2. +- Connection between AMF and SMF over N11. + +![Figure 6.1.1.7.2-1: End-to-End Control Plane for a Remote UE using Layer-2 UE-to-Network Relay. The diagram shows the control plane protocol stacks for a Remote UE, a UE-to-Network Relay UE, an NG-RAN, a Remote UE's AMF, and a Remote UE's SMF. The Remote UE stack includes NAS-SM, NAS-MM, Uu-RRC, Uu-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The UE-to-Network Relay UE stack includes PC5 Adaptation, PC5-RLC, PC5-MAC, PC5-PHY, Uu-RLC, Uu-MAC, and Uu-PHY. The NG-RAN stack includes Uu-RRC, Uu-PDCP, Adaptation, Uu-RLC, Uu-MAC, and Uu-PHY. The Remote UE's AMF stack includes NAS-MM, N11 Stack, and N2 Stack. The Remote UE's SMF stack includes NAS-SM and N11 Stack. Arrows indicate the flow of control plane messages between the Remote UE and the Remote UE's AMF/SMF via the UE-to-Network Relay UE and NG-RAN. Interfaces PC5, Uu, N2, and N11 are labeled at the bottom.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +Figure 6.1.1.7.2-1: End-to-End Control Plane for a Remote UE using Layer-2 UE-to-Network Relay. The diagram shows the control plane protocol stacks for a Remote UE, a UE-to-Network Relay UE, an NG-RAN, a Remote UE's AMF, and a Remote UE's SMF. The Remote UE stack includes NAS-SM, NAS-MM, Uu-RRC, Uu-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The UE-to-Network Relay UE stack includes PC5 Adaptation, PC5-RLC, PC5-MAC, PC5-PHY, Uu-RLC, Uu-MAC, and Uu-PHY. The NG-RAN stack includes Uu-RRC, Uu-PDCP, Adaptation, Uu-RLC, Uu-MAC, and Uu-PHY. The Remote UE's AMF stack includes NAS-MM, N11 Stack, and N2 Stack. The Remote UE's SMF stack includes NAS-SM and N11 Stack. Arrows indicate the flow of control plane messages between the Remote UE and the Remote UE's AMF/SMF via the UE-to-Network Relay UE and NG-RAN. Interfaces PC5, Uu, N2, and N11 are labeled at the bottom. + +**Figure 6.1.1.7.2-1: End-to-End Control Plane for a Remote UE using Layer-2 UE-to-Network Relay** + +The control plane protocol stack used by the 5G ProSe Layer-2 UE-to-Network Relay is defined in clause 8.2.2 of TS 23.501 [4]. + +### 6.1.1.8 5G ProSe UE-to-UE Relay + +#### 6.1.1.8.1 5G ProSe Layer-2 UE-to-UE Relay + +Figure 6.1.1.8.1-1 illustrates control plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. Security is established end-to-end between 5G ProSe End UEs as shown by the PDCP layer terminating in the 5G ProSe End UEs. + +![Figure 6.1.1.8.1-1: End-to-End Control Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. The diagram shows the control plane protocol stacks for two 5G ProSe End UEs and a 5G ProSe UE-to-UE Relay. The 5G ProSe End UE stack includes PC5-S, PC5-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The 5G ProSe UE-to-UE Relay stack includes PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. Arrows indicate the flow of control plane messages between the two 5G ProSe End UEs via the 5G ProSe UE-to-UE Relay. The PC5-S and PC5-PDCP layers are shown terminating at the 5G ProSe End UEs.](ddcdc1712375261ba1d89165fdf12aa6_img.jpg) + +Figure 6.1.1.8.1-1: End-to-End Control Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. The diagram shows the control plane protocol stacks for two 5G ProSe End UEs and a 5G ProSe UE-to-UE Relay. The 5G ProSe End UE stack includes PC5-S, PC5-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The 5G ProSe UE-to-UE Relay stack includes PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. Arrows indicate the flow of control plane messages between the two 5G ProSe End UEs via the 5G ProSe UE-to-UE Relay. The PC5-S and PC5-PDCP layers are shown terminating at the 5G ProSe End UEs. + +**Figure 6.1.1.8.1-1: End-to-End Control Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay** + +NOTE 1: Only the End-to-End control plane protocol stack is shown. The control plane protocol stack of the per-hop PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-2 UE-to-UE Relay reuses the PC5-S protocol stack defined in clause 6.1.1.2. + +NOTE 2: PC5-S messages over per-hop PC5 unicast links and over End-to-End PC5 unicast links are supported. A End-to-End PC5-S message is the message transferred between the 5G ProSe End UEs and a direct PC5-S message is the message transferred between a 5G ProSe End UE and a 5G ProSe Layer-2 UE-to-UE Relay. + +#### 6.1.1.8.2 5G ProSe Layer-3 UE-to-UE Relay + +The control plane protocol stack of the PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-3 UE-to-UE Relay reuses the PC5-S protocol stack defined in clause 6.1.1.2. + +## 6.1.2 User Plane + +### 6.1.2.1 General + +The user plane stack consists of protocols for data transmission via: + +- 5G ProSe Direct Communication, specified in clause 6.1.2.2; +- 5G ProSe UE-to-Network Relay, specified in clause 6.1.2.3; +- 5G ProSe UE-to-UE Relay, specified in clause 6.1.2.4. + +### 6.1.2.2 UE - UE + +Figure 6.1.2.2-1 depicts a user plane for NR PC5 reference point, i.e. PC5 User Plane Protocol stack. + +![Diagram of the User Plane for NR PC5 reference point showing the protocol stack for UE A and UE B. The stack consists of seven layers: ProSe App, IP, Ethernet, Unstructured, Address Resolution Protocol, SDAP, PDCP, RLC, MAC, and PHY. The layers are connected between UE A and UE B via horizontal double-headed arrows. The bottom layer (PHY) is labeled PC5-U.](f4b570ddd089f54943d46e9f8776f9f9_img.jpg) + +``` + +graph LR + subgraph UE_A [UE A] + direction TB + P1[ProSe App] + P2["IP, Ethernet, Unstructured, Address Resolution Protocol"] + P3[SDAP] + P4[PDCP] + P5[RLC] + P6[MAC] + P7[PHY] + P1 <--> P2 + P2 <--> P3 + P3 <--> P4 + P4 <--> P5 + P5 <--> P6 + P6 <--> P7 + end + subgraph UE_B [UE B] + direction TB + P1[ProSe App] + P2["IP, Ethernet, Unstructured, Address Resolution Protocol"] + P3[SDAP] + P4[PDCP] + P5[RLC] + P6[MAC] + P7[PHY] + P1 <--> P2 + P2 <--> P3 + P3 <--> P4 + P4 <--> P5 + P5 <--> P6 + P6 <--> P7 + end + P1 <--> P1 + P2 <--> P2 + P3 <--> P3 + P4 <--> P4 + P5 <--> P5 + P6 <--> P6 + P7 <--> P7 + P7 --- PC5_U[PC5-U] + +``` + +Diagram of the User Plane for NR PC5 reference point showing the protocol stack for UE A and UE B. The stack consists of seven layers: ProSe App, IP, Ethernet, Unstructured, Address Resolution Protocol, SDAP, PDCP, RLC, MAC, and PHY. The layers are connected between UE A and UE B via horizontal double-headed arrows. The bottom layer (PHY) is labeled PC5-U. + +#### Legend: + +- **PC5-U:** The SDAP/PDCP/RLC/MAC/PHY functionality is specified in TS 38.300 [12]. + +**Figure 6.1.2.2-1: User Plane for NR PC5 reference point** + +PDCP SDU types of IP, Ethernet, Unstructured and Address Resolution Protocol are supported. For IP PDCP SDU type, both IPv4 and IPv6 are supported. + +NOTE: Address Resolution Protocol is only supported for broadcast and groupcast mode 5G ProSe Direct Communication. + +The packets from ProSe application layer are handled by the ProSe layer before transmitting them to the AS layer, e.g. ProSe layer maps the IP, Ethernet and Unstructured packets to PC5 QoS Flow and marks the corresponding PFI. + +### 6.1.2.3 5G ProSe UE-to-Network Relay + +#### 6.1.2.3.1 5G ProSe Layer-3 UE-to-Network Relay + +![Figure 6.1.2.3.1-1: User plane protocol stack for Layer-3 UE-to-Network Relay. The diagram shows the protocol stack across five entities: UE, PC5-U, UE-Network Relay, NG-RAN node, and UPF. The UE stack includes Application, PDU layer, SDAP, PDCP, RLC, MAC, and L1. The PC5-U interface connects the UE to the UE-Network Relay. The UE-Network Relay stack includes PDU_Relay, SDAP, PDCP, RLC, MAC, and L1. The NG-RAN node stack includes SDAP, PDCP, RLC, MAC, and L1, with a 'Relay' function that encapsulates the PDU into GTP-U, UDP/IP, L2, and L1. The NG-RAN node connects to the UPF via the N3 interface. The UPF stack includes PDU layer, GTP-U, UDP/IP, L2, and L1. The N6 interface connects the UPF to the Data Network (DN).](57939c16065211317c5442cf2a4009e0_img.jpg) + +Figure 6.1.2.3.1-1: User plane protocol stack for Layer-3 UE-to-Network Relay. The diagram shows the protocol stack across five entities: UE, PC5-U, UE-Network Relay, NG-RAN node, and UPF. The UE stack includes Application, PDU layer, SDAP, PDCP, RLC, MAC, and L1. The PC5-U interface connects the UE to the UE-Network Relay. The UE-Network Relay stack includes PDU\_Relay, SDAP, PDCP, RLC, MAC, and L1. The NG-RAN node stack includes SDAP, PDCP, RLC, MAC, and L1, with a 'Relay' function that encapsulates the PDU into GTP-U, UDP/IP, L2, and L1. The NG-RAN node connects to the UPF via the N3 interface. The UPF stack includes PDU layer, GTP-U, UDP/IP, L2, and L1. The N6 interface connects the UPF to the Data Network (DN). + +#### Legend: + +- GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol tunnels user data between NG-RAN node and UPF as well as between the UPFs in the backbone network (not shown in the figure). GTP-U shall encapsulate all end user PDU packets. +- SMF controls the user plane tunnel establishment and establishes User Plane Bearers between NG-RAN node and UPF. +- UDP/IP: These are the backbone network protocols used for routing user data and control signalling. +- Uu: The NR Uu radio protocols of NG-RAN between the UE-to-Network Relay and the NG-RAN node are specified in TS 38.300 [12]. +- PC5-U: The radio protocols between the UE and the UE-to-Network Relay are specified in clause 6.1.2.2. + +Figure 6.1.2.3.1-1: User plane protocol stack for Layer-3 UE-to-Network Relay + +![Figure 6.1.2.3.1-2: User plane protocol stacks for Layer-3 UE-to-Network Relay with N3IWF support. The diagram shows the protocol stack across several entities: UE, PC5, UE-to-Network Relay, Uu, NG-RAN, N3, Relay UE UPF, N6, N3IWF, N3, UPF, and N9. The UE stack includes PDU Layer, GRE, Inner IP, IPsec (tunnel mode), IP, and PCS. The PC5 interface connects the UE to the UE-to-Network Relay. The UE-to-Network Relay stack includes IP, PCS, and Uu. The NG-RAN stack includes Uu, Relay N3 stack, and N3 stack. The Relay UE UPF stack includes IP, N3 stack, and L2/L1. The N3IWF stack includes GRE, Inner IP, IPsec (tunnel mode), IP, and Lower layers. The UPF stack includes PDU Layer, GTP-U, UDP/IP, L2, and L1. The N9 interface connects the UPF to the Data Network (DN).](149826281804ec51b5cca5603c88b23b_img.jpg) + +Figure 6.1.2.3.1-2: User plane protocol stacks for Layer-3 UE-to-Network Relay with N3IWF support. The diagram shows the protocol stack across several entities: UE, PC5, UE-to-Network Relay, Uu, NG-RAN, N3, Relay UE UPF, N6, N3IWF, N3, UPF, and N9. The UE stack includes PDU Layer, GRE, Inner IP, IPsec (tunnel mode), IP, and PCS. The PC5 interface connects the UE to the UE-to-Network Relay. The UE-to-Network Relay stack includes IP, PCS, and Uu. The NG-RAN stack includes Uu, Relay N3 stack, and N3 stack. The Relay UE UPF stack includes IP, N3 stack, and L2/L1. The N3IWF stack includes GRE, Inner IP, IPsec (tunnel mode), IP, and Lower layers. The UPF stack includes PDU Layer, GTP-U, UDP/IP, L2, and L1. The N9 interface connects the UPF to the Data Network (DN). + +#### Legend: + +- IPsec, Inner IP and GRE between the UE and the N3IWF are defined in TS 23.501 [4] clause 8.3.2. + +Figure 6.1.2.3.1-2: User plane protocol stacks for Layer-3 UE-to-Network Relay with N3IWF support + +#### 6.1.2.3.2 5G ProSe Layer-2 UE-to-Network Relay + +Figure 6.1.2.2.2-1 illustrates the protocol stack for the user plane transport, related to a PDU Session, including a 5G ProSe Layer 2 UE-to-Network Relay. The PDU layer corresponds to the PDU carried between the 5G ProSe Layer-2 Remote UE and the Data Network (DN) over the PDU session. The SDAP and PDCP protocols are specified in TS 38.300 [12]. PDCP end-to-end connection is between the 5G ProSe Layer-2 Remote UE and NG-RAN. The functionality of the adaptation layer is specified in TS 38.351 [28]. + +![Figure 6.1.2.3.2-1: End-to-End User Plane Stack for a 5G ProSe Remote UE using 5G ProSe Layer-2 UE-to-Network Relay. The diagram shows four entities: Remote UE, UE-to-Network Relay UE, NG-RAN, and Remote UE's UPF. The Remote UE stack includes APP, PDU layer, Uu-SDAP, Uu-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The UE-to-Network Relay UE stack includes PC5 Adaptation, PC5-RLC, PC5-MAC, PC5-PHY, Uu-PHY, Uu-MAC, Uu-RLC, Adaptation, Uu-PDCP, and Uu-SDAP. The NG-RAN stack includes Uu-PHY, Uu-MAC, Uu-RLC, Adaptation, Uu-PDCP, GTP-U, UDP, IP, L2, and L1. The Remote UE's UPF stack includes PDU layer, GTP-U, UDP, IP, L2, and L1. Arrows indicate data flow from the Remote UE's APP through the relay to the UPF, with specific layers highlighted for the PC5 and Uu interfaces.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +Figure 6.1.2.3.2-1: End-to-End User Plane Stack for a 5G ProSe Remote UE using 5G ProSe Layer-2 UE-to-Network Relay. The diagram shows four entities: Remote UE, UE-to-Network Relay UE, NG-RAN, and Remote UE's UPF. The Remote UE stack includes APP, PDU layer, Uu-SDAP, Uu-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The UE-to-Network Relay UE stack includes PC5 Adaptation, PC5-RLC, PC5-MAC, PC5-PHY, Uu-PHY, Uu-MAC, Uu-RLC, Adaptation, Uu-PDCP, and Uu-SDAP. The NG-RAN stack includes Uu-PHY, Uu-MAC, Uu-RLC, Adaptation, Uu-PDCP, GTP-U, UDP, IP, L2, and L1. The Remote UE's UPF stack includes PDU layer, GTP-U, UDP, IP, L2, and L1. Arrows indicate data flow from the Remote UE's APP through the relay to the UPF, with specific layers highlighted for the PC5 and Uu interfaces. + +**Figure 6.1.2.3.2-1: End-to-End User Plane Stack for a 5G ProSe Remote UE using 5G ProSe Layer-2 UE-to-Network Relay** + +## 6.1.2.4 5G ProSe UE-to-UE Relay + +### 6.1.2.4.1 5G ProSe Layer-2 UE-to-UE Relay + +Figure 6.1.2.4.1-1 illustrates user plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. Security is established end-to-end between 5G ProSe End UEs as shown by the PDCP layer terminating in the 5G ProSe End UEs. + +![Figure 6.1.2.4.1-1: End-to-End User Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. The diagram shows three entities: 5G ProSe End UE, 5G ProSe UE-to-UE Relay, and 5G ProSe End UE. The 5G ProSe End UE stack includes ProSe App, IP/Ethernet, Unstructured, PC5-SDAP, PC5-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The 5G ProSe UE-to-UE Relay stack includes PC5-PHY, PC5-MAC, PC5-RLC, PC5 Adaptation, and PC5-PDCP. Arrows show data flow from the first 5G ProSe End UE through the relay to the second 5G ProSe End UE, with the PC5-PDCP layer being continuous across all three entities.](7f663b2f8632236c6e40ca16272d62df_img.jpg) + +Figure 6.1.2.4.1-1: End-to-End User Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay. The diagram shows three entities: 5G ProSe End UE, 5G ProSe UE-to-UE Relay, and 5G ProSe End UE. The 5G ProSe End UE stack includes ProSe App, IP/Ethernet, Unstructured, PC5-SDAP, PC5-PDCP, PC5 Adaptation, PC5-RLC, PC5-MAC, and PC5-PHY. The 5G ProSe UE-to-UE Relay stack includes PC5-PHY, PC5-MAC, PC5-RLC, PC5 Adaptation, and PC5-PDCP. Arrows show data flow from the first 5G ProSe End UE through the relay to the second 5G ProSe End UE, with the PC5-PDCP layer being continuous across all three entities. + +**Figure 6.1.2.4.1-1: End-to-End User Plane protocol stacks using a 5G ProSe Layer-2 UE-to-UE Relay** + +NOTE: IP, Ethernet and Unstructured traffic types are supported. + +### 6.1.2.4.2 5G ProSe Layer-3 UE-to-UE Relay + +The user plane protocol stack of the PC5 unicast link between 5G ProSe End UEs and 5G ProSe Layer-3 UE-to-UE Relay reuses the user plane protocol stack defined in clause 6.1.2.2. + +## 6.2 Procedures for Service Authorization and Provisioning to UE + +### 6.2.1 General + +The procedures for service authorization and provisioning to UE may be initiated by the PCF (as described in clause 6.2.2), by the UE (as described in clause 6.2.4), or by the AF (as described in clause 6.2.5). + +## 6.2.2 PCF based Service Authorization and Provisioning to UE + +For PCF based Service Authorization and Provisioning to UE, the Registration procedures as defined in clause 4.2.2.2 of TS 23.502 [5], UE Policy Association Establishment procedure as defined in clause 4.16.11 of TS 23.502 [5] and UE Policy Association Modification procedure as defined in clause 4.16.12 of TS 23.502 [5] apply with the following additions: + +- If the UE indicates 5G ProSe Capability in the Registration Request message and if the UE is authorized to use 5G ProSe service based on subscription data, the AMF selects the PCF which supports 5G ProSe Policy/Parameter provisioning as described in clause 6.2.3 and establishes a UE policy association with the PCF for 5G ProSe Policy/Parameter delivery. The AMF reports the authorized 5G ProSe Capability to the selected PCF, which may determine the 5G ProSe Policy/Parameter based on the UE's authorized 5G ProSe Capability. + +The PCF may update the 5G ProSe Policy/parameters to the UE in following conditions: + +- UE Mobility, e.g. UE moves from one PLMN to another PLMN. This is achieved by using the procedure of UE Policy Association Modification initiated by the AMF, as defined in clause 4.16.12.1 of TS 23.502 [5]. +- When there is a subscription change in the list of PLMNs where the UE is authorized to perform 5G ProSe services. This is achieved by using UE Policy Association Modification initiated by the PCF procedure as defined in clause 4.16.12.2 of TS 23.502 [5]. +- When there is a change of service specific parameter (including path selection policy) as described in clause 6.2.5 (performing the procedure in clause 4.15.6.7 of TS 23.502 [5]). +- When the timer associated with some Policy/parameter expires. +- When the UE determines that the ProSe Policy/parameter(s) is invalid and performs UE triggered Policy Provisioning procedure to the PCF. + +If the serving PLMN is removed from the list of PLMNs in the service authorization parameters, the service authorization is revoked in the UE. + +When the UE is roaming, the change of subscription resulting in updates of the service authorization parameters are transferred to the UE by H-PCF via V-PCF. + +The UE may perform ProSe UE triggered Policy Provisioning procedure to the PCF, after Registration procedure has been completed, as specified in clause 6.2.4 when the UE determines the 5G ProSe Policy/Parameter is invalid (e.g. Policy/Parameter is outdated, missing or invalid). + +When the UE disables a ProSe capability, the PCF may stop updating the corresponding ProSe Policy/parameter(s) and when the UE enables a ProSe capability the PCF may need to provide or update the corresponding ProSe Policy/parameter(s). + +When a 5G ProSe Layer-3 Remote UE is accessing to 5GC via a 5G ProSe Layer-3 UE-to-Network Relay without involving N3IWF, the PCF based provisioning and update of 5G ProSe Policy/parameters to the 5G ProSe Layer-3 Remote UE are not supported. + +## 6.2.3 PCF discovery + +PCF discovery and selection mechanism defined in clause 6.3.7.1 of TS 23.501 [4] applies with the following addition to enable a PCF instance is selected for 5G ProSe service and for UE: + +- Based on the indication from the UE and/or UE subscription data during the Registration procedure as specified in clause 6.2.2, the AMF may include the 5G ProSe Capability indication in the Nnrf\_NFDiscovery\_Request message as the optional input parameter. If provided, the NRF takes the information into account for discovering the PCF instance. + +## 6.2.4 Procedure for UE triggered ProSe Policy provisioning + +The UE triggered Policy Provisioning procedure is initiated by the UE to request ProSe Policy/Parameter from the PCF when UE determines the 5G ProSe Policy/Parameter is invalid in the following cases: + +- if the validity timer indicated in the 5G ProSe Policy/Parameter expires; + +- if there are no valid parameters, e.g. for the 5G ProSe Identifier a UE wants to use, for current area, or due to abnormal situation. + +![Sequence diagram of UE triggered 5G ProSe Policy provisioning procedure. The diagram shows four lifelines: UE, (R)AN, AMF, and PCF. Step 1: UE sends a 'UE Policy provisioning request' to AMF. Step 2: AMF sends a 'Namf_Communication_N1MessageNotify' to PCF. Step 3: A box labeled '3. UE Policy delivery procedure defined in clause 4.2.4.3 of 23.502' spans across all lifelines, indicating a subsequent procedure.](04f7b8f64493f6d83188232f10f86fe2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant PCF + Note right of PCF: 3. UE Policy delivery procedure defined in clause 4.2.4.3 of 23.502 + UE->>AMF: 1. UE Policy provisioning request + AMF->>PCF: 2. Namf_Communication_N1MessageNotify + +``` + +Sequence diagram of UE triggered 5G ProSe Policy provisioning procedure. The diagram shows four lifelines: UE, (R)AN, AMF, and PCF. Step 1: UE sends a 'UE Policy provisioning request' to AMF. Step 2: AMF sends a 'Namf\_Communication\_N1MessageNotify' to PCF. Step 3: A box labeled '3. UE Policy delivery procedure defined in clause 4.2.4.3 of 23.502' spans across all lifelines, indicating a subsequent procedure. + +**Figure 6.2.4-1: UE triggered 5G ProSe Policy provisioning procedure** + +1. The UE sends the UL NAS TRANSPORT message carrying the UE Policy Container (UE Policy Provisioning Request to request 5G ProSe policies) to the AMF. +2. The AMF sends Namf\_Communication\_N1MessageNotify request to the PCF including the UE Policy Container received from UE. +3. The PCF receives UE Policy Container which indicates UE Policy Provisioning Request to request 5G ProSe policies. If the 5G ProSe policies are authorized based on AMF input, the PCF performs the UE Policy delivery procedure as defined in clause 4.2.4.3 of TS 23.502 [5]. + +## 6.2.5 AF-based service parameter provisioning for ProSe over control plane + +For 5G ProSe service parameter provisioning (i.e. creating, updating and deleting), the procedure defined in clause 4.15.6.7 of TS 23.502 [5] is performed with the following considerations: + +- The AF in TS 23.502 [5] is considered as ProSe Application Server in this specification. +- Service Description indicates 5G ProSe service domain information. +- Service Parameters include parameters for 5G ProSe Direct Discovery and 5G ProSe Direct Communications. The detailed information on the parameters is described in clause 5.1.2.1 and clause 5.1.3.1. +- Service Parameters for 5G ProSe UE-to-Network Relay Discovery and 5G ProSe UE-to-Network Relay Communications. The detailed information on the parameters is described in clause 5.1.4.1. +- Service Parameters for 5G ProSe UE-to-UE Relay Discovery and 5G ProSe UE-to-UE Relay Communications. The detailed information on the parameters is described in clause 5.1.5.1. + +NOTE: It is assumed that the ProSe service domain information is set based on the Service Level Agreement with the operator. + +## 6.3 5G ProSe Direct Discovery + +### 6.3.1 5G ProSe Direct Discovery with 5G DDNMF + +#### 6.3.1.1 Overview + +5G ProSe Direct Discovery is defined as the process that detects and identifies another UE in proximity using NR radio signals. There are two types of 5G ProSe Direct Discovery supported over PC3a reference point: open and restricted, as defined in TS 23.303 [3]. 5G ProSe Direct Discovery can be a standalone service or can be used for subsequent actions e.g. to initiate 5G ProSe Direct Communication. + +ProSe-enabled UEs which have obtained authorization to participate in 5G ProSe Direct Discovery shall not continue in participating in 5G ProSe Direct Discovery procedures over PC3a reference point defined in clause 6.3.1 when they detect loss of NG-RAN coverage in the serving PLMN. + +With 5G ProSe Direct Discovery, the UE can use inter-PLMN discovery transmission based on the indication from the serving NG-RAN or the provisioned radio resource on the UE. How the serving cell authorizes the UE to use inter-PLMN radio resource is specified in TS 38.331 [16]. + +### 6.3.1.2 Overall procedure for 5G ProSe Direct Discovery (Model A) + +![Sequence diagram for 5G ProSe Direct Discovery (Model A) showing interactions between UE, 5G DDNMF, H-PCF, V/L-PCF, and ProSe App Server across HPLMN and Other PLMN (VPLMN or Local).](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +The diagram illustrates the overall procedure for 5G ProSe Direct Discovery (Model A) across two network domains: HPLMN and Other PLMN (VPLMN or Local). The entities involved are UE, 5G DDNMF, H-PCF, V/L-PCF, and ProSe App Server. The sequence of messages is as follows: + +- 1. Service authorization:** The UE sends a service authorization request to the ProSe App Server via the 5G DDNMF and H-PCF in the HPLMN. +- 2a. Discovery Request (announce):** For the announcing UE, the UE sends a discovery request to the 5G DDNMF in the HPLMN. +- 3a. Discovery announce on PC5:** The 5G DDNMF in the HPLMN sends a discovery announce message to the UE on the PC5 interface. +- 2b. Discovery Request (monitor):** For the monitoring UE, the UE sends a discovery request to the 5G DDNMF in the HPLMN. +- 3b. Discovery monitor on PC5:** The 5G DDNMF in the HPLMN sends a discovery monitor message to the UE on the PC5 interface. +- 4b. Match report:** The UE sends a match report to the 5G DDNMF in the HPLMN. + +Sequence diagram for 5G ProSe Direct Discovery (Model A) showing interactions between UE, 5G DDNMF, H-PCF, V/L-PCF, and ProSe App Server across HPLMN and Other PLMN (VPLMN or Local). + +**Figure 6.3.1.2-1: Overall procedure for Model A 5G ProSe Direct Discovery** + +This procedure is applied for open and restricted 5G ProSe Direct Discovery when the ProSe enabled UE is served by NG-RAN. + +1. Service authorisation for 5G ProSe Direct Discovery services is performed for as defined in clause 6.2. + +If the UE is authorised to announce: + +- 2a. When the UE is triggered to announce, then it sends a discovery request for announcing to the 5G DDNMF in HPLMN as defined in clause 6.3.1.4. In addition, for restricted 5G ProSe Direct Discovery, the 5G DDNMF further interacts with the ProSe Application server for the authorization of the discovery request. +- 3a. If the request is successful and is provided with ProSe Application Code/ProSe Restricted Code, it starts announcing on PC5 interface. + +For ProSe restricted discovery and UE requests "on demand" announcing, ProSe Restricted Code may be provided to UE after this procedure. In this case, UE waits for the ProSe Restricted Code allocation and starts to announce the ProSe Restricted Code on PC5 after receiving it in Announcing Alert procedure specified in clause 6.3.1.6. + +NOTE 1: More details on the Access Stratum protocol of this step are provided in RAN specifications. + +If the UE is authorised to monitor: + +2b. When the UE is triggered to monitor, it sends a discovery request for monitoring to the 5G DDNMF as defined in clause 6.3.1.4. In addition, for restricted 5G ProSe Direct Discovery, the 5G DDNMF further interacts with the ProSe Application server for the authorization of the discovery request. + +3b. If the request is successful and the UE is provided with a Discovery Filter consisting of ProSe Application Code(s)/ProSe Restricted Code(s) and/or ProSe Application Mask(s), it starts monitoring for these ProSe Application Codes/ProSe Restricted Codes on the PC5 interface. + +NOTE 2: More details on the Access Stratum protocol of this step are provided in RAN specifications. + +4b. When the UE detects that one or more ProSe Application Code(s)/ProSe Restricted Code(s) that match the filter (see clause 5.8.1), it reports the ProSe Application Code(s)/ProSe Restricted Code(s) to the 5G DDNMF as defined in clause 6.3.1.5. + +Non-roaming direct discovery procedures cover the case where both the "announcing UE" and "monitoring UE" are served by their respective HPLMN. Roaming direct discovery procedures cover the other cases. + +### 6.3.1.3 Overall procedure for 5G ProSe Direct Discovery (Model B) + +![Sequence diagram for 5G ProSe Direct Discovery (Model B) showing interactions between UE, 5G DDNMF, H-PCF, V/L-PCF, and ProSe App Server across HPLMN and Other PLMN (VPLMN or Local).](04867b54e8cdb31a034edbb472a41162_img.jpg) + +The diagram illustrates the overall procedure for 5G ProSe Direct Discovery (Model B). It is divided into two main sections: "For the Discoveree UE" and "For the Discoverer UE". + +- 1. Service authorization:** A message from the UE to the ProSe App Server via the 5G DDNMF and H-PCF. +- For the Discoveree UE:** + - 2a. Discovery Request (monitor/announce):** A message from the UE to the 5G DDNMF. + - 3a. Monitor ProSe Query Code on PC5:** An internal UE action. + - 4a. Announce a ProSe Response Code on PC5 if a ProSe Query Code matches:** An internal UE action. +- For the Discoverer UE:** + - 2b. Discovery Request (announce/monitor):** A message from the UE to the 5G DDNMF. + - 3b. Announce a ProSe Query Code on PC5:** An internal UE action. + - 4b. Monitor a ProSe Response Code on PC5:** An internal UE action. + - 5b. Match report:** A message from the UE to the 5G DDNMF. + +The diagram is split into two PLMN domains: HPLMN (containing UE, 5G DDNMF, and H-PCF) and Other PLMN (VPLMN or Local) (containing 5G DDNMF, V/L-PCF, and ProSe App Server). + +Sequence diagram for 5G ProSe Direct Discovery (Model B) showing interactions between UE, 5G DDNMF, H-PCF, V/L-PCF, and ProSe App Server across HPLMN and Other PLMN (VPLMN or Local). + +Figure 6.3.1.3-1: Overall procedure for Model B 5G ProSe Direct Discovery + +This procedure is applied for restricted 5G ProSe Direct Discovery when the ProSe enabled UE is served by NG-RAN. + +1. Service authorisation for 5G ProSe Direct Discovery services is performed as defined in clause 6.2. + +If the UE is authorised to perform restricted 5G ProSe Direct Discovery, Model B, as a Discoveree UE, the following steps take place: + +- 2a. When the UE is triggered to perform restricted 5G ProSe Direct Discovery, Model B, it sends a discovery request to the 5G DDNMF in the HPLMN to obtain a ProSe Response Code as defined in clause 6.3.1.4. The 5G DDNMF further interacts with ProSe Application Server for the authorization of the discovery request. +- 3a. If the request is successful and the UE is provided with a ProSe Response Code and an associated Discovery Query Filter(s), then the UE starts monitoring for the ProSe Query Code on PC5 interface. +- 4a. If a received ProSe Query Code matches any of the Discovery Query Filter(s), the UE announces the associated ProSe Response Code on the PC5 interface. + +NOTE 1: More details on the Access Stratum protocol of this step are provided in RAN specifications. + +If the UE is authorised to perform restricted 5G ProSe Direct Discovery, Model B, as a Discoverer UE, the following steps take place: + +- 2b. When the UE is triggered to perform restricted 5G ProSe Direct Discovery, Model B, it sends a discovery request to the 5G DDNMF in the HPLMN for a ProSe Query Code as defined in clause 6.3.1.4. The 5G DDNMF further interacts with ProSe Application Server for the authorization of the discovery request. +- 3b. If the request is successful and the UE is provided with a ProSe Query Code and the Discovery Response Filter(s) consisting of ProSe Response Code(s) and ProSe Application Mask(s), the UE announces the ProSe Query Code on the PC5 interface. +- 4b. The UE starts to monitor on PC5 interface for any ProSe Response Code(s) that might match the Discovery Response Filter(s). + +NOTE 2: More details on the Access Stratum protocol of this step are provided in RAN specifications. + +- 5b. When the UE detects a match for one or more ProSe Response Code(s), it reports the ProSe Response Code to the 5G DDNMF as defined in clause 6.3.1.5. + +Non-roaming direct discovery procedures cover the case where both the Discoveree UE and Discoverer UE are served by their respective HPLMN. Roaming direct discovery procedures cover the other cases. + +### 6.3.1.4 Discovery Request procedures + +The Discovery Request procedure can be used by the "announcing UE" or "monitoring UE" in order to be authorised to access the discovery resources and perform 5G ProSe Direct Discovery. The exact signalling procedures involving the UE, the 5G DDNMFs and the ProSe Application Server are specified in TS 23.303 [3] clause 5.3.3, with the following modifications: + +- the 5G DDNMF takes the role of "ProSe Function" in the procedure; +- Upon receiving a Discovery Request for restricted discovery from a UE, if the 5G DDNMF does not have a valid PDUID for that UE, the 5G DDNMF searches the PCF for the UE using Nbsf\_Management\_Subscribe Request and BSF provides the address of the PCF for the UE in Nbsf\_Management\_Subscribe Response as defined in the clause 5.2.13.2.6 in TS 23.502 [5]. The 5G DDNMF gets the PDUID and subscribes to notifications on Change of PDUID using Npcf\_AMPolicyAuthorization\_Subscribe from the PCF for the UE as defined in the clause 5.2.5.8.6 in TS 23.502 [5], including the SUPI, Event ID set to "Change of PDUID" and immediate reporting flag to indicate that the current PDUID value should be provided to the consumer. The PCF provides the PDUID and its validity timer. + +NOTE: If the address of the PCF for the UE is changed, the BSF notifies the 5G DDNMF of the changed PCF address in Nbsf\_Management\_Notify as defined in the clause 5.2.13.2.8 in TS 23.502 [5]. + +- At the time the PCF generates a new PDUID, if the subscription to "Change of PDUID" is active it sends Npcf\_AMPolicyAuthorization\_Notify to the 5G DDNMF to report a new PDUID and its validity timer. +- the HSS is replaced by UDM; + +- the E-UTRAN is replaced by NG-RAN and E-UTRA is replaced with NR; +- corresponding 5GS identifiers replace the EPS identifiers, e.g. use SUPI instead of IMSI and use GPSI instead of MSISDN; +- PC5\_tech parameter is omitted and the intended PC5 radio technology is NR. + +The Discovery Request procedure can also be used by the Discoveree UE or the Discoverer UE in order to be authorised to access the discovery resources and perform 5G ProSe Direct Discovery, Model B. The exact signalling procedures are defined in TS 23.303 [3] clause 5.3.3A, with the same modifications as in the above list apply. + +The events reported by the PCF, described in clause 6.1.3.18 in TS 23.503 [9] are extended to report "Change of PDUID" to the 5G DDNMF. + +### 6.3.1.5 Discovery Reporting procedures + +The Discovery Reporting procedure can be used by the "monitoring UE" (in Model A) and Discoverer UE (in Model B) to request the 5G DDNMF to resolve a matched ProSe Discovery Code(s) (ProSe Application Code for open discovery and ProSe Restricted Code for restricted discovery) and obtain the corresponding ProSe Application ID(s) or RPAUID and additional information, e.g. metadata. + +The signalling procedures for the "monitoring UE" (in Model A) is specified in TS 23.303 [3] clause 5.3.4 and the signalling procedures for the Discoverer UE (in Model B) is specified in TS 23.303 [3] clause 5.3.4A, with the following modifications: + +- the 5G DDNMF takes the role of "ProSe Function" in the procedure; +- the HSS is replaced by UDM; +- corresponding 5GS identifiers replace the EPS identifiers, e.g. use SUPI instead of IMSI and use GPSI instead of MSISDN; +- PC5\_tech parameter is omitted and the intended PC5 radio technology is NR. + +### 6.3.1.6 Announcing Alert Procedures for restricted discovery + +When supported by the 5G DDNMF and the UE, the Announcing Alert procedure allows the 5G DDNMF to postpone the ProSe Restricted Code allocation, so that the announcing UE would be only triggered by this procedure to announce when the 5G DDNMF receives a Monitor Request from a UE in the vicinity of the announcing UE. This procedure is an optional step of the Discovery Request procedure defined in clause 6.3.1.4. + +The signalling procedure of Announcing Alert Procedure is specified in TS 23.303 [3] clause 5.3.5, with the same modifications listed in clause 6.3.1.4. + +### 6.3.1.7 Direct Discovery Update Procedures + +The 5G DDNMF can at any time update/revoke a previously allocated ProSe Application Code, or Discovery Filters. The UE can decide at any time to stop announcing a ProSe Application Code or monitoring set of Discovery Filter(s). The Direct Discovery Update procedure as specified in TS 23.303 [3] clause 5.3.6A.1 allows both the 5G DDNMF and the UE to update or revoke the previously authorized discovery. In the defined signalling procedures, the 5G DDNMF(s) takes the role of the "ProSe Function". + +A user may decide at any time to change the discovery permissions relating to other users in a ProSe Application Server; then the corresponding ProSe Application Server triggers the procedure as specified in clause 5.3.6A.2 of TS 23.303 [3] towards the affected 5G DDNMF(s) to update/revoke the discovery permissions. In the defined signalling procedures, the 5G DDNMF(s) takes the role of the "ProSe Function". + +## 6.3.2 5G ProSe Direct Discovery procedures over PC5 reference point + +### 6.3.2.1 General + +A PC5 communication channel is used to carry the discovery message over PC5 and the discovery message over PC5 is differentiated from other PC5 messages by AS layer. + +Both Model A and Model B discovery as defined in TS 23.303 [3] are supported: + +- Model A uses a single discovery protocol message (Announcement). +- Model B uses two discovery protocol messages (Solicitation and Response). + +Depicted in figure 6.3.2.1-1 is the procedure for 5G ProSe Direct Discovery with Model A. + +![Sequence diagram for 5G ProSe direct discovery with Model A. It shows five User Equipment (UE) entities: UE-1 (announcing), UE-2 (monitoring), UE-3 (monitoring), UE-4 (monitoring), and UE-5 (monitoring). UE-1 sends a single 'Announcement message' (labeled '1.') to all other UEs (UE-2, UE-3, UE-4, and UE-5) via horizontal arrows. A thick vertical bar on the timeline of UE-1 indicates the start of the announcement period.](205c14458d7f4e2d22c75354bb451e99_img.jpg) + +``` +sequenceDiagram + participant UE-1 as UE-1 (announcing) + participant UE-2 as UE-2 (monitoring) + participant UE-3 as UE-3 (monitoring) + participant UE-4 as UE-4 (monitoring) + participant UE-5 as UE-5 (monitoring) + Note left of UE-1: Start of Announcement message + UE-1->>UE-2: 1. Announcement message + UE-1->>UE-3: 1. Announcement message + UE-1->>UE-4: 1. Announcement message + UE-1->>UE-5: 1. Announcement message +``` + +Sequence diagram for 5G ProSe direct discovery with Model A. It shows five User Equipment (UE) entities: UE-1 (announcing), UE-2 (monitoring), UE-3 (monitoring), UE-4 (monitoring), and UE-5 (monitoring). UE-1 sends a single 'Announcement message' (labeled '1.') to all other UEs (UE-2, UE-3, UE-4, and UE-5) via horizontal arrows. A thick vertical bar on the timeline of UE-1 indicates the start of the announcement period. + +**Figure 6.3.2.1-1: 5G ProSe direct discovery with Model A** + +1. The Announcing UE sends an Announcement message. The Announcement message may include the Type of Discovery Message, ProSe Application Code or ProSe Restricted Code, security protection element, [metadata information]. The Application layer metadata information may be included as metadata in the Announcement message. + +The Destination Layer-2 ID and Source Layer-2 ID used to send the Announcement message are specified in clause 5.8.1.2 and clause 5.8.1.3. + +The Monitoring UE determines the Destination Layer-2 ID for signalling reception. The Destination Layer-2 ID is configured with the UE(s) as specified in clause 5.8.1.2. + +Depicted in figure 6.3.2.1-2 is the procedure for 5G ProSe Direct Discovery with Model B. + +![Sequence diagram for 5G ProSe direct discovery with Model B. The diagram shows five User Equipment (UE) entities: UE-1 (discoverer), UE-2 (discoveree), UE-3 (discoveree), UE-4 (discoveree), and UE-5 (discoveree). UE-1 sends a '1. Solicitation message' to UE-2, UE-3, UE-4, and UE-5. UE-2 responds with '2a. Response message' to UE-1. UE-3 responds with '2b. Response message' to UE-1. UE-4 and UE-5 do not respond.](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +sequenceDiagram + participant UE-1 as UE-1 (discoverer) + participant UE-2 as UE-2 (discoveree) + participant UE-3 as UE-3 (discoveree) + participant UE-4 as UE-4 (discoveree) + participant UE-5 as UE-5 (discoveree) + Note left of UE-1: + UE-1->>UE-2: 1. Solicitation message + UE-1->>UE-3: 1. Solicitation message + UE-1->>UE-4: 1. Solicitation message + UE-1->>UE-5: 1. Solicitation message + Note left of UE-2: + UE-2->>UE-1: 2a. Response message + Note left of UE-3: + UE-3->>UE-1: 2b. Response message + +``` + +Sequence diagram for 5G ProSe direct discovery with Model B. The diagram shows five User Equipment (UE) entities: UE-1 (discoverer), UE-2 (discoveree), UE-3 (discoveree), UE-4 (discoveree), and UE-5 (discoveree). UE-1 sends a '1. Solicitation message' to UE-2, UE-3, UE-4, and UE-5. UE-2 responds with '2a. Response message' to UE-1. UE-3 responds with '2b. Response message' to UE-1. UE-4 and UE-5 do not respond. + +**Figure 6.3.2.1-2: 5G ProSe direct discovery with Model B** + +1. The Discoverer UE sends a Solicitation message. The Solicitation message may include Type of Discovery Message, ProSe Query Code, security protection element. + +The Destination Layer-2 ID and Source Layer-2 ID used to send the Solicitation message are specified in clause 5.8.1.2 and clause 5.8.1.3. + +How the Discoveree UE determines the Destination Layer-2 ID for signalling reception is specified in clause 5.8.1.2. + +2. The Discoveree UE that matches the solicitation message responds to the Discoverer UE with the Response message. The Response message may include Type of Discovery Message, ProSe Response Code, security protection element, [metadata information]. The Application layer metadata information may be included as metadata in the Response message. + +The Source Layer-2 ID used to send the Response message is specified in clause 5.8.1.3. The Destination Layer-2 ID is set to the Source Layer-2 ID of the received Solicitation message. + +NOTE: Details of security protection element are specified in TS 33.503 [29]. + +## 6.3.2.2 Group Member Discovery + +### 6.3.2.2.1 General + +Group Member Discovery is applicable to public safety use and commercial services. To perform Group Member Discovery, the UE is configured with the related information as described in clause 5.2. + +Group Member Discovery is a form of restricted discovery in that only users that are affiliated with each other can discover each other (e.g. only users sharing the same Application Layer Group ID). + +In the case of Public Safety use, the ProSe Restricted Code is not used for Group Member Discovery and pre-configured or provisioned information for the Discovery procedures as defined in clause 5.2 is used. + +NOTE: The Group Member Discovery performed by Application Layer in coordination with Application Server is out of scope of this specification. + +Both Model A and Model B discovery are supported: + +- Model A uses a single discovery protocol message (Announcement). +- Model B uses two discovery protocol messages (Solicitation and Response). + +### 6.3.2.2.2 Procedure for Group Member Discovery with Model A + +Depicted in Figure 6.3.2.2.2-1 is the procedure for Group Member Discovery with Model A. + +![Sequence diagram for Group Member Discovery with Model A. UE-1 (announcing) sends a '1. Group Member Discovery Announcement message' to UE-2 (monitoring), UE-3 (monitoring), and UE-4 (monitoring).](64323b705244afc70bf77babdacb6ce5_img.jpg) + +``` + +sequenceDiagram + participant UE-1 as UE-1 (announcing) + participant UE-2 as UE-2 (monitoring) + participant UE-3 as UE-3 (monitoring) + participant UE-4 as UE-4 (monitoring) + Note left of UE-1: + UE-1->>UE-2: 1. Group Member Discovery Announcement message + UE-1->>UE-3: + UE-1->>UE-4: + +``` + +Sequence diagram for Group Member Discovery with Model A. UE-1 (announcing) sends a '1. Group Member Discovery Announcement message' to UE-2 (monitoring), UE-3 (monitoring), and UE-4 (monitoring). + +**Figure 6.3.2.2.2-1: Group Member Discovery with Model A** + +1. The announcing UE sends a Group Member Discovery Announcement message. The Group Member Discovery Announcement message includes the Type of Discovery Message, Announcer Info and Application Layer Group ID (See clause 5.8.1). + +The Destination Layer-2 ID and Source Layer-2 ID used to send the Group Member Discovery Announcement message are specified in clause 5.8.1.2 and clause 5.8.1.3. + +The Monitoring UE determines the Destination Layer-2 ID for signalling reception as specified in clause 5.8.1.2. + +NOTE: A UE may send multiple Group Member Discovery Announcement messages (Model A) if the UE belongs to more than one discovery group. + +### 6.3.2.2.3 Procedure for Group Member Discovery with Model B + +Depicted in Figure 6.3.2.2.3-1 is the procedure for Group Member Discovery with Model B. + +![Sequence diagram for Group Member Discovery with Model B. UE-1 (discoverer) sends a '1. Group Member Discovery Solicitation message' to UE-2 (discoveree), UE-3 (discoveree), and UE-4 (discoveree). UE-2 and UE-3 respond with '2a. Group Member Discovery Response message' and '2b. Group Member Discovery Response message' respectively.](ac8194ec0d833d53a0a36adada95b39e_img.jpg) + +``` + +sequenceDiagram + participant UE-1 as UE-1 (discoverer) + participant UE-2 as UE-2 (discoveree) + participant UE-3 as UE-3 (discoveree) + participant UE-4 as UE-4 (discoveree) + Note left of UE-1: + UE-1->>UE-2: 1. Group Member Discovery Solicitation message + UE-1->>UE-3: + UE-1->>UE-4: + Note left of UE-2: + UE-2->>UE-1: 2a. Group Member Discovery Response message + Note left of UE-3: + UE-3->>UE-1: 2b. Group Member Discovery Response message + +``` + +Sequence diagram for Group Member Discovery with Model B. UE-1 (discoverer) sends a '1. Group Member Discovery Solicitation message' to UE-2 (discoveree), UE-3 (discoveree), and UE-4 (discoveree). UE-2 and UE-3 respond with '2a. Group Member Discovery Response message' and '2b. Group Member Discovery Response message' respectively. + +**Figure 6.3.2.2.3-1: Group Member Discovery with Model B** + +1. The discoverer UE sends a Group Member Discovery Solicitation message. The Group Member Discovery Solicitation message includes the Type of Discovery Message, Discoverer Info, Application Layer Group ID and optionally Target Info (see clause 5.8.1). + +The Destination Layer-2 ID and Source Layer-2 ID used to send the Group Member Discovery Solicitation message are specified in clause 5.8.1.2 and clause 5.8.1.3. + +How the Discoveree UE determines the Destination Layer-2 ID for signalling reception is specified in clause 5.8.1.2. + +2. The discoveree UEs that match the values of the parameters (including Application Layer Group ID and Target Info) contained in the solicitation message, responds to the discoverer UE with a Group Member Discovery Response message. The Group Member Discovery Response message includes the Type of Discovery Message, Discoveree Info and Application Layer Group ID (see clause 5.8.1). + +The Source Layer-2 ID used to send the Group Member Discovery Response message is specified in clause 5.8.1.3. The Destination Layer-2 ID is set to the Source Layer-2 ID of the received Group Member Discovery Solicitation message. + +### 6.3.2.3 5G ProSe UE-to-Network Relay Discovery + +#### 6.3.2.3.1 General + +5G ProSe UE-to-Network Relay Discovery is applicable to both 5G ProSe Layer-3 and Layer-2 UE-to-Network relay discovery for public safety use and commercial services. To perform 5G ProSe UE-to-Network Relay Discovery, the 5G ProSe Remote UE and the 5G ProSe UE-to-Network Relay are pre-configured or provisioned with the related information as described in clause 5.1. + +In 5G ProSe UE-to-Network Relay Discovery, the UEs use pre-configured or provisioned information for the relay discovery procedures as defined in clause 5.1.4.1. + +The Relay Service Code (RSC) is used in the 5G ProSe UE-to-Network Relay discovery, to indicate the connectivity service the 5G ProSe UE-to-Network Relay provides to the 5G ProSe Remote UE. The RSCs (including the dedicated one(s) for emergency service) are configured on the 5G ProSe UE-to-Network Relay and the 5G ProSe Remote UE as defined in clause 5.1.4. The 5G ProSe UE-to-Network Relay and the 5G ProSe Remote UE are aware of whether a RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-Network Relay service and whether a RSC is for emergency service, based the policy as specified in clause 5.1.4. A 5G ProSe UE-to-Network Relay supporting multiple RSCs can advertise the RSCs using multiple discovery messages, with one RSC per discovery message. + +NOTE: When the 5G ProSe UE-to-Network Relay can advertise the emergency RSC(s) is specified in clause 5.4.4. + +Additional information not directly used for discovery can also be advertised using the PC5-D protocol stack in single or separate discovery messages of type "Relay Discovery Additional Information" as defined in clause 5.8.3.1. + +#### 6.3.2.3.2 Procedure for 5G ProSe UE-to-Network Relay Discovery with Model A + +Depicted in Figure 6.3.2.3.2-1 is the procedure for 5G ProSe UE-to-Network Discovery with Model A. + +![Sequence diagram for 5G ProSe UE-to-Network Relay Discovery with Model A. The diagram shows four lifelines: UE-to-Network Relay (announcing), Remote UE-1 (monitoring), Remote UE-2 (monitoring), and Remote UE-3 (monitoring). The process starts with the UE-to-Network Relay sending a '1. UE-to-Network Relay Discovery Announcement message' to Remote UE-1. Below this, there is an '[optional] UE-to-Network Relay Discovery Additional Information' section, represented by dashed lines, which is sent to all three monitoring UEs (Remote UE-1, Remote UE-2, and Remote UE-3).](44ffa7f0e6419d046ab4fed0faaf7738_img.jpg) + +``` + +sequenceDiagram + participant UNR as UE-to-Network Relay (announcing) + participant RUE1 as Remote UE-1 (monitoring) + participant RUE2 as Remote UE-2 (monitoring) + participant RUE3 as Remote UE-3 (monitoring) + Note left of UNR: 1. UE-to-Network Relay Discovery Announcement message + UNR->>RUE1: 1. UE-to-Network Relay Discovery Announcement message + Note left of UNR: [optional] UE-to-Network Relay Discovery Additional Information + UNR-->>RUE1: [optional] UE-to-Network Relay Discovery Additional Information + UNR-->>RUE2: [optional] UE-to-Network Relay Discovery Additional Information + UNR-->>RUE3: [optional] UE-to-Network Relay Discovery Additional Information + +``` + +Sequence diagram for 5G ProSe UE-to-Network Relay Discovery with Model A. The diagram shows four lifelines: UE-to-Network Relay (announcing), Remote UE-1 (monitoring), Remote UE-2 (monitoring), and Remote UE-3 (monitoring). The process starts with the UE-to-Network Relay sending a '1. UE-to-Network Relay Discovery Announcement message' to Remote UE-1. Below this, there is an '[optional] UE-to-Network Relay Discovery Additional Information' section, represented by dashed lines, which is sent to all three monitoring UEs (Remote UE-1, Remote UE-2, and Remote UE-3). + +Figure 6.3.2.3.2-1: 5G ProSe UE-to-Network Relay Discovery with Model A + +1. The 5G ProSe UE-to-Network Relay sends a UE-to-Network Relay Discovery Announcement message. The UE-to-Network Relay Discovery Announcement message contains the Type of Discovery Message, Announcer Info and RSC and is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.3. + +For 5G ProSe Layer-3 UE-to-Network Relay, the 5G ProSe Layer-3 UE-to-Network Relay shall only include a RSC in the UE-to-Network Relay Discovery Announcement when the S-NSSAI associated with that RSC belongs to the Allowed NSSAI of the UE-to-Network Relay. + +The 5G ProSe Remote UE (1 to 3) determines the Destination Layer-2 ID for signalling reception. The Destination Layer-2 ID is configured with the UE(s) as specified in clause 5.1.4.1. + +5G ProSe Remote UE (1 to 3) monitors announcement messages with the 5G ProSe UE-to-Network RSC corresponding to the desired services. + +Optionally, the 5G ProSe UE-to-Network Relay may also send Relay Discovery Additional Information messages as defined in clause 6.5.1.3. The parameters contained in this message and the Source Layer-2 ID and Destination Layer-2 ID used for sending and receiving the message are described in clause 5.8.3. + +The 5G ProSe Remote UE selects the 5G ProSe UE-to-Network Relay based on the information received in step 1. + +NOTE: Access Stratum layer information used for 5G ProSe UE-to-Network Relay selection is specified in RAN specifications. + +### 6.3.2.3.3 Procedure for 5G ProSe UE-to-Network Relay Discovery with Model B + +Depicted in Figure 6.3.2.3.3-1 is the procedure for 5G ProSe UE-to-Network Relay Discovery with Model B. + +![Sequence diagram for 5G ProSe UE-to-Network Relay Discovery with Model B. The diagram shows four lifelines: Remote UE (discoverer), UE-to-Network Relay -1 (discoveree), UE-to-Network Relay -2 (discoveree), and UE-to-Network Relay -3 (discoveree). Step 1: Remote UE sends a 'UE-to-Network Relay Discovery Solicitation message' to all three relays. Step 2: Relay -1 and Relay -2 both send a 'UE-to-Network Relay Discovery Response message' back to the Remote UE. Relay -3 does not respond. The response from Relay -1 is labeled '2a' and the response from Relay -2 is labeled '2b'.](7fb9ad30fcd499d82f0047335bb21b4a_img.jpg) + +``` + +sequenceDiagram + participant Remote UE as Remote UE (discoverer) + participant Relay 1 as UE-to-Network Relay -1 (discoveree) + participant Relay 2 as UE-to-Network Relay -2 (discoveree) + participant Relay 3 as UE-to-Network Relay -3 (discoveree) + Note left of Remote UE: 1. UE-to-Network Relay Discovery Solicitation message + Remote UE->>Relay 1: UE-to-Network Relay Discovery Solicitation message + Remote UE->>Relay 2: UE-to-Network Relay Discovery Solicitation message + Remote UE->>Relay 3: UE-to-Network Relay Discovery Solicitation message + Note left of Relay 1: 2a. UE-to-Network Relay Discovery Response message + Relay 1->>Remote UE: UE-to-Network Relay Discovery Response message + Note left of Relay 2: 2b. UE-to-Network Relay Discovery Response message + Relay 2->>Remote UE: UE-to-Network Relay Discovery Response message + +``` + +Sequence diagram for 5G ProSe UE-to-Network Relay Discovery with Model B. The diagram shows four lifelines: Remote UE (discoverer), UE-to-Network Relay -1 (discoveree), UE-to-Network Relay -2 (discoveree), and UE-to-Network Relay -3 (discoveree). Step 1: Remote UE sends a 'UE-to-Network Relay Discovery Solicitation message' to all three relays. Step 2: Relay -1 and Relay -2 both send a 'UE-to-Network Relay Discovery Response message' back to the Remote UE. Relay -3 does not respond. The response from Relay -1 is labeled '2a' and the response from Relay -2 is labeled '2b'. + +**Figure 6.3.2.3.3-1: 5G ProSe UE-to-Network Relay Discovery with Model B** + +1. The 5G ProSe Remote UE sends a 5G ProSe UE-to-Network Relay Discovery Solicitation message. The 5G ProSe UE-to-Network Discovery Solicitation message contains the Type of Discovery Message, Discoverer Info, RSC and optionally Target Info and is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.3. The 5G ProSe Remote UE discovering a 5G ProSe UE-to-Network Relay sends a solicitation message with the RSC which is associated to the desired connectivity service. The RSC is based on the Policy/Parameters specified in clause 5.1.4.1. + +How the 5G ProSe UE-to-Network Relays (1 to 3) determine the Destination Layer-2 ID for signalling reception is specified in clause 5.8.3. The Destination Layer-2 ID is configured with the UE(s) as specified in clause 5.1.4.1. + +2. If the RSC contained in the solicitation message matches any of the (pre)configured RSC(s), as specified in clause 5.1.4.1, of a 5G ProSe UE-to-Network Relay, and the Target Info contained in the solicitation message, if any, matches the 5G ProSe UE-to-Network Relay, the 5G ProSe UE-to-Network Relays (e.g. 1 and 2) respond to the 5G ProSe Remote UE with a UE-to-Network Relay Discovery Response message. The 5G ProSe UE-to-Network Relay Discovery Response message contains the Type of Discovery Message, Discoveree Info and RSC and is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.3. + +For 5G ProSe Layer-3 UE-to-Network Relay, the 5G ProSe UE-to-Network Relay shall only respond to a matching RSC in the UE-to-Network Relay Discovery Solicitation message when the S-NSSAI associated with that RSC belongs to the Allowed NSSAI of the 5G ProSe UE-to-Network Relay. + +The 5G ProSe Remote UE selects the 5G ProSe UE-to-Network Relay based on the information received in step 2. + +### 6.3.2.4 5G ProSe UE-to-UE Relay Discovery + +#### 6.3.2.4.1 General + +5G ProSe UE-to-UE Relay Discovery is applicable to both 5G ProSe Layer-3 and Layer-2 UE-to-UE Relay Discovery for public safety use and commercial services. To perform 5G ProSe UE-to-UE Relay Discovery, the 5G ProSe End UE and the 5G ProSe UE-to-UE Relay are pre-configured or provisioned with the related information as described in clause 5.1. + +A Relay Service Code (RSC) is used in the 5G ProSe UE-to-UE Relay Discovery, to indicate the connectivity service the 5G ProSe UE-to-UE Relay provides to 5G ProSe End UEs. The RSCs are pre-configured or provisioned on the 5G ProSe UE-to-UE Relay and the 5G ProSe End UE as defined in clause 5.1. The 5G ProSe UE-to-UE Relay and the 5G ProSe End UE are aware of whether a RSC is offering 5G ProSe Layer-2 or Layer-3 UE-to-UE Relay service based on the UE-to-UE Relay Layer indicator as specified in clause 5.1. A 5G ProSe UE-to-UE Relay supporting multiple RSCs advertises the RSCs using multiple discovery messages, with one RSC per discovery message. + +#### 6.3.2.4.2 Procedure for 5G ProSe UE-to-UE Relay Discovery with Model A + +Depicted in Figure 6.3.2.4.2-1 is the procedure for 5G ProSe UE-to-UE Discovery with Model A. + +![Sequence diagram for 5G ProSe UE-to-UE Relay Discovery with Model A. The diagram shows three participants: 5G ProSe End UE-1 (monitoring), 5G ProSe UE-to-UE Relay (announcing), and 5G ProSe End UE-2 (monitoring). The process starts with the relay discovering other UEs in proximity. It then sends a 'UE-to-UE Relay Discovery Announcement message' to both UE-1 and UE-2.](0779125369ae9c0108101b54fe2428bf_img.jpg) + +``` + +sequenceDiagram + participant UE1 as 5G ProSe End UE-1 (monitoring) + participant Relay as 5G ProSe UE-to-UE Relay (announcing) + participant UE2 as 5G ProSe End UE-2 (monitoring) + Note right of Relay: 1. UE-to-UE Relay has discovered other UEs in proximity + Relay->>UE1: 2. UE-to-UE Relay Discovery Announcement message + Relay->>UE2: 2. UE-to-UE Relay Discovery Announcement message + +``` + +Sequence diagram for 5G ProSe UE-to-UE Relay Discovery with Model A. The diagram shows three participants: 5G ProSe End UE-1 (monitoring), 5G ProSe UE-to-UE Relay (announcing), and 5G ProSe End UE-2 (monitoring). The process starts with the relay discovering other UEs in proximity. It then sends a 'UE-to-UE Relay Discovery Announcement message' to both UE-1 and UE-2. + +**Figure 6.3.2.4.2-1: 5G ProSe UE-to-UE Relay Discovery with Model A** + +1. The 5G ProSe UE-to-UE Relay has discovered other UEs in proximity (e.g. via a previous 5G ProSe UE-to-UE Relay Discovery or 5G ProSe UE-to-UE Relay Communication procedures). The 5G ProSe UE-to-UE Relay obtains the User Info ID of other UEs in proximity per RSC. +2. The 5G ProSe UE-to-UE Relay sends a UE-to-UE Relay Discovery Announcement message. The UE-to-UE Relay Discovery Announcement message contains the Type of Discovery Message, User Info ID of the 5G ProSe UE-to-UE Relay, RSC and list of User Info ID of the 5G ProSe End UEs supporting the RSC. The UE-to-UE Relay Discovery Announcement message is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.4. + +The 5G ProSe UE-to-UE Relay shall only announce User Info IDs of other UEs in proximity that did not include an Announce Prohibited Indication when they were previously discovered. + +NOTE: 5G ProSe UE-to-UE Relay announces User Info IDs of other UEs in proximity only if their PC5 signal strength measured by the 5G ProSe UE-to-UE Relay is above configured signal strength threshold as specified in TS 38.331 [16]. + +A 5G ProSe End UE monitors announcement messages from a 5G ProSe UE-to-UE Relay. The 5G ProSe End UEs determine the Destination Layer-2 ID for signalling reception as specified in clause 5.1. + +### 6.3.2.4.3 Procedure for 5G ProSe UE-to-UE Relay Discovery with Model B + +Depicted in Figure 6.3.2.4.3-1 is the procedure for 5G ProSe UE-to-UE Relay Discovery with Model B. + +![Sequence diagram for 5G ProSe UE-to-UE Relay Discovery with Model B. The diagram shows five lifelines: 5G ProSe End UE-1 (discoverer), 5G ProSe UE-to-UE Relay-1, 5G ProSe UE-to-UE Relay-2, 5G ProSe UE-to-UE Relay-3, and 5G ProSe End UE-2 (discoveree). The sequence of messages is: 1. UE-to-UE Relay Discovery Solicitation message from UE-1 to Relay-1, Relay-2, and Relay-3. 2. UE-to-UE Relay Discovery Solicitation message from Relay-1 to UE-2. 3. UE-to-UE Relay Discovery Response message from UE-2 to Relay-2. 4. UE-to-UE Relay Discovery Response message from Relay-2 to UE-1.](070352b751dd0711b8ac6ddfa6df1d98_img.jpg) + +``` + +sequenceDiagram + participant UE1 as 5G ProSe End UE-1 (discoverer) + participant R1 as 5G ProSe UE-to-UE Relay-1 + participant R2 as 5G ProSe UE-to-UE Relay-2 + participant R3 as 5G ProSe UE-to-UE Relay-3 + participant UE2 as 5G ProSe End UE-2 (discoveree) + + Note left of UE1: 1. UE-to-UE Relay Discovery Solicitation message + UE1->>R1: + UE1->>R2: + UE1->>R3: + Note left of R1: 2. UE-to-UE Relay Discovery Solicitation message + R1->>UE2: + Note left of UE2: 3. UE-to-UE Relay Discovery Response message + UE2->>R2: + Note left of R2: 4. UE-to-UE Relay Discovery Response message + R2->>UE1: + +``` + +Sequence diagram for 5G ProSe UE-to-UE Relay Discovery with Model B. The diagram shows five lifelines: 5G ProSe End UE-1 (discoverer), 5G ProSe UE-to-UE Relay-1, 5G ProSe UE-to-UE Relay-2, 5G ProSe UE-to-UE Relay-3, and 5G ProSe End UE-2 (discoveree). The sequence of messages is: 1. UE-to-UE Relay Discovery Solicitation message from UE-1 to Relay-1, Relay-2, and Relay-3. 2. UE-to-UE Relay Discovery Solicitation message from Relay-1 to UE-2. 3. UE-to-UE Relay Discovery Response message from UE-2 to Relay-2. 4. UE-to-UE Relay Discovery Response message from Relay-2 to UE-1. + +**Figure 6.3.2.4.3-1: 5G ProSe UE-to-UE Relay Discovery with Model B** + +- The discoverer 5G ProSe End UE (UE-1) sends a 5G ProSe UE-to-UE Relay Discovery Solicitation message. The 5G ProSe UE-to-UE Relay Discovery Solicitation message contains the Type of Discovery Message, User Info ID of itself, RSC and User Info ID of the discoveree 5G ProSe End UE (UE-2) and is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.4. + +A 5G ProSe UE-to-UE Relay determines the Destination Layer-2 ID for signalling reception as specified in clause 5.1. + +The discoverer 5G ProSe End UE may include an Announce Prohibited Indication in the UE-to-UE Relay Discovery Solicitation message. If a 5G ProSe UE-to-UE Relay receives a Relay Discovery Solicitation message with an Announce Prohibited Indication it does not consider the 5G ProSe End UE as discovered during this procedure for inclusion in 5G ProSe UE-to-UE Relay Discovery with Model A, see clause 6.3.2.4.2, step 1. + +- If the RSC contained in the solicitation message matches any of the (pre)configured RSC(s), as specified in clause 5.1.5.1, of a 5G ProSe UE-to-UE Relay, the 5G ProSe UE-to-UE Relay sends a 5G ProSe UE-to-UE Relay Discovery Solicitation message. The 5G ProSe UE-to-UE Relay Discovery Solicitation message contains the Type of Discovery Message, User Info ID of the discoverer 5G ProSe End UE (UE-1), User Info ID of UE-to-UE Relay, RSC and User Info ID of the discoveree 5G ProSe End UE (UE-2) and is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.4. + +A 5G ProSe End UE determines the Destination Layer-2 ID for signalling reception as specified in clause 5.1. + +- If the RSC contained in the solicitation message matches any of the (pre)configured RSC(s), as specified in clause 5.1.5.1, of the discoveree 5G ProSe End UE (UE-2), and the discoveree 5G ProSe End UE (UE-2) matches the User Info ID of the discoveree 5G ProSe End UE (UE-2) contained in the solicitation message, then the discoveree 5G ProSe End UE (UE-2) responds to the 5G ProSe UE-to-UE Relay with a 5G ProSe UE-to-UE Relay Discovery Response message. The 5G ProSe UE-to-UE Relay Discovery Response message contains the Type of Discovery Message, RSC, User Info ID of the discoverer 5G ProSe End UE (UE-1) and User Info ID of discoveree 5G ProSe End UE (UE-2) and is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.4. If the discoveree 5G ProSe End UE (UE-2) receives multiple UE-to-UE Relay Discovery Solicitation messages from different 5G ProSe UE-to-UE Relays with the same RSC and the User + +Info ID of the discoveree 5G ProSe End UE (UE-2), it may choose to respond or not to a 5G ProSe UE-to-UE Relay (e.g. based on the PC5 signal strength of each message received). + +The discoveree 5G ProSe End UE may include an Announce Prohibited Indication in the UE-to-UE Relay Discovery Response message. If a 5G ProSe UE-to-UE Relay receives a Relay Discovery Response message with an Announce Prohibited Indication it does not consider the 5G ProSe End UE as discovered during this procedure for inclusion in 5G ProSe UE-to-UE Relay Discovery with Model A, see clause 6.3.2.4.2, step 1. + +4. The 5G ProSe UE-to-UE Relay sends a 5G ProSe UE-to-UE Relay Discovery Response message. The 5G ProSe UE-to-UE Relay Discovery Response message contains the Type of Discovery Message, User Info ID of UE-to-UE Relay, RSC, User Info ID of the discoverer 5G ProSe End UE (UE-1) and User Info ID of the discoveree 5G ProSe End UE (UE-2) and is sent using the Source Layer-2 ID and Destination Layer-2 ID as described in clause 5.8.4. + +#### 6.3.2.4.4 Candidate 5G ProSe UE-to-UE Relay Discovery + +This procedure for candidate 5G ProSe UE-to-UE Relay Discovery to support the negotiated Relay reselection as described in clause 6.7.4 when the discoverer End UE discovers a candidate 5G ProSe UE-to-UE Relay. + +The procedure for 5G ProSe UE-to-UE Relay Discovery with Model B (see clause 6.3.2.4.3) is used with the following differences: + +- Step 1: In the 5G ProSe UE-to-UE Relay Discovery Solicitation message the RSC and the User Info ID of a candidate 5G ProSe UE-to-UE Relay are included, and the discoveree 5G ProSe End UE User Info ID is not included. If the 5G ProSe End UE receives the Layer-2 ID of the candidate 5G ProSe UE-to-UE Relay in a Link Modification Request message, it may set the Layer-2 ID of the candidate 5G ProSe UE-to-UE Relay as the Destination Layer-2 ID. + +NOTE: The User Info ID of the candidate 5G ProSe UE-to-UE Relay and the User Info ID of the discoveree 5G ProSe End UE can be distinguished by the 5G ProSe UE-to-UE Relay as different IEs in the message. + +- Step 2 and step 3 are skipped because the discoveree 5G ProSe End UE User Info ID is absent, and the User Info ID of the candidate 5G ProSe UE-to-UE Relay in the received 5G ProSe UE-to-UE Relay Discovery Solicitation message matches that of the 5G ProSe UE-to-UE Relay. +- Step 4: If a 5G ProSe UE-to-UE Relay matches the User Info ID of a candidate 5G ProSe UE-to-UE Relay received in the 5G ProSe UE-to-UE Relay Discovery Solicitation then it sends the 5G ProSe UE-to-UE Relay Discovery Response (with the RSC received in step 1) and does not include the User Info ID of the discoveree 5G ProSe End UE. + +## 6.4 5G ProSe Direct Communication + +### 6.4.1 Broadcast mode 5G ProSe Direct Communication + +To perform 5G ProSe direct communication over PC5 reference point in broadcast mode operation, the UE is configured with the related information as described in clause 5.1.3. + +Figure 6.4.1-1 shows the procedure for broadcast mode of 5G ProSe direct communication over PC5 reference point. + +![Sequence diagram illustrating the procedure for broadcast mode of 5G ProSe direct communication over PC5 reference point. The diagram shows a transmitting UE (Tx UE-1) and multiple receiving UEs (Rx UE-1, Rx UE-2, Rx UE-n). The process involves: 1. Receiving UEs determining destination Layer-2 IDs; 2. Tx UE-1's ProSe application layer providing data and QoS requirements; 3. Tx UE-1 determining source and destination Layer-2 IDs; 4. Broadcasting the ProSe Service from Tx UE-1 to all receiving UEs.](38d82ffe820e339811b396206f40a201_img.jpg) + +``` + +sequenceDiagram + participant Tx UE-1 + participant Rx UE-1 + participant Rx UE-2 + participant Rx UE-n + + Note right of Rx UE-1: 1. UE-1 determines destination Layer-2 ID for reception. + Note right of Rx UE-2: 1. UE-2 determines destination Layer-2 ID for reception. + Note right of Rx UE-n: 1. UE-n determines destination Layer-2 ID for reception. + + Note left of Tx UE-1: 2. ProSe application layer provides data unit and optional Qos requirements to ProSe layer. + Note left of Tx UE-1: 3. Tx UE determines source and destination Layer-2 ID + + Tx UE-1->>Rx UE-1: 4. ProSe Service (Broadcast) + Tx UE-1->>Rx UE-2: 4. ProSe Service (Broadcast) + Tx UE-1->>Rx UE-n: 4. ProSe Service (Broadcast) + +``` + +Sequence diagram illustrating the procedure for broadcast mode of 5G ProSe direct communication over PC5 reference point. The diagram shows a transmitting UE (Tx UE-1) and multiple receiving UEs (Rx UE-1, Rx UE-2, Rx UE-n). The process involves: 1. Receiving UEs determining destination Layer-2 IDs; 2. Tx UE-1's ProSe application layer providing data and QoS requirements; 3. Tx UE-1 determining source and destination Layer-2 IDs; 4. Broadcasting the ProSe Service from Tx UE-1 to all receiving UEs. + +**Figure 6.4.1-1: Procedure for Broadcast mode of 5G ProSe direct communication over PC5 reference point** + +- The ProSe layer of receiving UE(s) determines the following for the broadcast mode communication reception: + - the destination Layer-2 ID for broadcast reception as specified in clause 5.8.2.2; + - the PC5 QoS parameters for this broadcast ProSe service as specified in clause 5.6.1; and + - the NR Tx Profile based on the configuration as specified in clause 5.1.3.1. + +The destination Layer-2 ID, the NR Tx Profile and the PC5 QoS parameters are passed down to the AS layer of receiving UE(s) for the reception. + +The AS layer of receiving UE(s) determines the PC5 DRX parameter values as specified in clause 5.13. + +- The transmitting UE ProSe application layer provides data unit and may provide ProSe Application Requirements specified in clause 5.6.1 to ProSe layer. +- The ProSe layer of transmitting UE determines the following for the broadcast mode communication transmission: + - the destination Layer-2 ID for broadcast as specified in clause 5.8.2.2; + - the PC5 QoS parameters for this broadcast ProSe service as specified in clauses 5.6.1; and + - the NR Tx Profile based on the configuration as specified in clause 5.1.3.1. + +The transmitting UE self-assigns the source Layer-2 ID as specified in clause 5.8.2.2. + +The source Layer-2 ID, the destination Layer-2 ID, the NR Tx Profile and the PC5 QoS parameters are passed down to the AS layer of transmitting UE for the transmission. + +The AS layer of transmitting UE determines the PC5 DRX parameter values as specified in clause 5.13. + +- The transmitting UE sends the ProSe data using the source Layer-2 ID and the destination Layer-2 ID. + +NOTE: In step 4, there is only one broadcast message from the transmitting UE. + +## 6.4.2 Groupcast mode 5G ProSe Direct Communication + +Figure 6.4.2-1 shows the procedure for groupcast mode of 5G ProSe Direct Communication. + +![Sequence diagram illustrating the procedure for groupcast mode 5G ProSe Direct communication. The diagram shows interactions between a Transmitting UE (Tx UE), multiple Receiving UEs (Rx UE-1 to Rx UE-n), and a ProSe Application Server. The process involves group management, member discovery, identifier information provision, Layer-2 ID determination, and groupcast data transmission.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant Tx UE + participant Rx UE-1 + participant Rx UE-n + participant ProSe Application Server + + Note right of ProSe Application Server: 1. Group management is carried out in ProSe application layer + Note right of ProSe Application Server: 2. ProSe group member discovery + Note left of Tx UE: 3. ProSe application layer may provide group identifier information. + Note left of Rx UE-1: 3. ProSe application layer may provide group identifier information. + Note left of Rx UE-n: 3. ProSe application layer may provide group identifier information. + Note left of Tx UE: 4. Tx UE determines source/destination Layer-2 IDs. + Note left of Rx UE-1: 4. Rx UE determines destination Layer-2 ID. + Note left of Rx UE-n: 4. Rx UE determines destination Layer-2 ID. + Note right of Tx UE: 5. ProSe data (Groupcast) + Tx UE->>Rx UE-1: + Tx UE->>Rx UE-n: + +``` + +Sequence diagram illustrating the procedure for groupcast mode 5G ProSe Direct communication. The diagram shows interactions between a Transmitting UE (Tx UE), multiple Receiving UEs (Rx UE-1 to Rx UE-n), and a ProSe Application Server. The process involves group management, member discovery, identifier information provision, Layer-2 ID determination, and groupcast data transmission. + +**Figure 6.4.2-1: Procedure for groupcast mode 5G ProSe Direct communication** + +Steps 1 to 3 are optional, e.g. applicable for Application Layer managed group. Groupcast mode ProSe Direct communication can be performed without steps 1 to 3 based on the provisioned parameters as defined in clause 5.1.3.1. + +1. ProSe Group management is carried out at ProSe application layer. This may be performed in coordination with ProSe Application Server. + +Group Member Discovery parameters as specified in clause 5.1.2.1 can be provisioned in ME from PCF or configured in UICC or provided from ProSe Application Server to the UE. + +2. Each UE may perform a ProSe group member discovery (similar to the procedures in clause 6.3.2.2) that is restricted only to users sharing the same Application Layer Group ID obtained in step 1. + +The Application layer discovery messages including the Application Layer Group ID for Application Layer managed group may be exchanged between UEs to discover each other sharing the same Application Layer Group ID. When the group is formed, the Application layer discovery message including group size and member ID may be provided by one UE to all other UEs. The Application layer discovery messages may be included as metadata in a PC5 direct discovery message. + +3. The ProSe Application layer may provide group identifier information (i.e. the Application Layer Group ID discovered based on discovery messages exchanged in step 2) as specified in clause 5.8.2.3. + +The ProSe application layer may also provide ProSe Application Requirements for this communication. + +If the ProSe application layer does not provide ProSe Application Requirements, the ProSe layer determines the PC5 QoS parameters based on the mapping of ProSe service to PC5 QoS parameters as specified in clause 5.1.3.1. + +The ProSe application layer may provide a group size and a member ID (optionally based on discovery messages exchanged in step 2) as specified in clause 5.3.3 for Application Layer managed group. + +4. The ProSe layer of transmitting UE self-assigns a source Layer-2 ID and determines the following for the groupcast mode communication transmission: + +- a destination Layer-2 ID as specified in clauses 5.8.2.1 and 5.8.2.3. +- The PC5 QoS parameters for this groupcast mode communication as specified in clause 5.6.1. +- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1. + +The source Layer-2 ID, destination Layer-2 ID, the NR Tx Profile and the PC5 QoS parameters are passed down to the AS layer of transmitting UE for the groupcast mode communication transmission. + +The ProSe layer of receiving UE(s) determines the following for the groupcast mode communication reception: + +- destination Layer-2 ID as specified in clauses 5.8.2.1 and 5.8.2.3; +- the PC5 QoS parameters for this groupcast mode communication as specified in clause 5.6.1; and +- the NR Tx Profile based on the configuration as specified in clause 5.1.3.1. + +The destination Layer-2 ID, the NR Tx Profile and the PC5 QoS parameters are passed down to the AS layer of receiving UE(s) for the reception. + +If the group size and the member ID for Application Layer managed group are provided by the ProSe application layer, the ProSe layer passes them to the AS layer as described in clause 5.3.3. + +The AS layer of transmitting UE and the AS layer of receiving UE(s) determine the PC5 DRX parameter values as specified in clause 5.13. + +5. Transmitting UE sends the ProSe data using the source Layer-2 ID and the destination Layer-2 ID. + +NOTE: In step 5, there is only one groupcast message from the transmitting UE. That is, all receiving UEs can receive the groupcast message directly from the transmitting UE. + +## 6.4.3 Unicast mode 5G ProSe Direct Communication + +### 6.4.3.1 Layer-2 link establishment over PC5 reference point + +To perform unicast mode of ProSe Direct communication over PC5 reference point, the UE is configured with the related information as described in clause 5.1.3. + +Figure 6.4.3.1-1 shows the layer-2 link establishment procedure for the unicast mode of ProSe Direct communication over PC5 reference point. + +![Sequence diagram showing Layer-2 link establishment procedure between UE-1 and UE-2, UE-3, and UE-4. The diagram is divided into two main parts: A) UE oriented Layer-2 link establishment and B) ProSe Service oriented Layer-2 link establishment. UE-1 sends a Direct Communication Request to the others. UE-2, UE-3, and UE-4 determine destination Layer-2 IDs. Part A shows UE-1 and UE-2 establishing a link through security establishment, direct communication accept, and data transfer. Part B shows UE-1 establishing links with both UE-3 and UE-4 through similar steps.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +The diagram illustrates the Layer-2 link establishment procedure for PC5 unicast communication. It involves four User Equipment (UE) entities: UE-1, UE-2, UE-3, and UE-4. + +**Initial Steps:** + +- UE-1: 2. ProSe application layer provides application information for PC5 unicast communication. +- UE-2: 1. UE-2 determines the destination Layer-2 ID for signalling reception. +- UE-3: 1. UE-3 determines the destination Layer-2 ID for signalling reception. +- UE-4: 1. UE-4 determines the destination Layer-2 ID for signalling reception. + +UE-1 sends a **3. Direct Communication Request (Broadcast or Unicast)** to the other UEs. + +**A) *UE oriented Layer-2 link establishment*** (between UE-1 and UE-2): + +- 4a. Security Establishment +- 5a. Direct Communication Accept (Unicast) +6. ProSe data over unicast link + +**B) *ProSe Service oriented Layer-2 link establishment*** (between UE-1 and UE-3, and UE-1 and UE-4): + +- 4b. Security Establishement +- 5b. Direct Communication Accept (Unicast) +- 4b. Security Establishment +- 5b. Direct Communication Accept (Unicast) +6. ProSe data over unicast link +6. ProSe data over unicast link + +Sequence diagram showing Layer-2 link establishment procedure between UE-1 and UE-2, UE-3, and UE-4. The diagram is divided into two main parts: A) UE oriented Layer-2 link establishment and B) ProSe Service oriented Layer-2 link establishment. UE-1 sends a Direct Communication Request to the others. UE-2, UE-3, and UE-4 determine destination Layer-2 IDs. Part A shows UE-1 and UE-2 establishing a link through security establishment, direct communication accept, and data transfer. Part B shows UE-1 establishing links with both UE-3 and UE-4 through similar steps. + +**Figure 6.4.3.1-1: Layer-2 link establishment procedure** + +1. The UE(s) determine the destination Layer-2 ID for signalling reception for PC5 unicast link establishment as specified in clause 5.8.2.4. + +2. The ProSe application layer in UE-1 provides application information for PC5 unicast communication. The application information includes the ProSe Service Info, UE's Application Layer ID. The target UE's Application Layer ID may be included in the application information. + +The ProSe application layer in UE-1 may provide ProSe Application Requirements for this unicast communication. UE-1 determines the PC5 QoS parameters and PFI as specified in clause 5.6.1. + +If UE-1 decides to reuse the existing PC5 unicast link as specified in clause 5.3.4, the UE triggers the Layer-2 link modification procedure as specified in clause 6.4.3.4. + +3. UE-1 sends a Direct Communication Request message to initiate the unicast layer-2 link establishment procedure. The Direct Communication Request message includes: + - Source User Info: the initiating UE's Application Layer ID (i.e. UE-1's Application Layer ID). + - If the ProSe application layer provided the target UE's Application Layer ID in step 2, the following information is included: + - Target User Info: the target UE's Application Layer ID (i.e. UE-2's Application Layer ID). + - ProSe Service Info: the information about the ProSe identifier(s) requesting Layer-2 link establishment. + - Security Information: the information for the establishment of security. + +NOTE 1: The Security Information and the necessary protection of the Source User Info and Target User Info are defined in TS 33.503 [29]. + +The source Layer-2 ID and destination Layer-2 ID used to send the Direct Communication Request message are determined as specified in clauses 5.8.2.1 and 5.8.2.4. The destination Layer-2 ID may be broadcast or unicast Layer-2 ID. When unicast Layer-2 ID is used, the Target User Info shall be included in the Direct Communication Request message. + +UE-1 sends the Direct Communication Request message via PC5 broadcast or unicast using the source Layer-2 ID and the destination Layer-2 ID. + +A default PC5 DRX configuration may be used for transmitting and receiving of this message (see TS 38.300 [12]). + +4. Security with UE-1 is established as below: + - 4a. If the Target User Info is included in the Direct Communication Request message, the target UE, i.e. UE-2, responds by establishing the security with UE-1. + - 4b. If the Target User Info is not included in the Direct Communication Request message, the UEs that are interested in using the announced ProSe Service(s) over a PC5 unicast link with UE-1 responds by establishing the security with UE-1. + +NOTE 2: The signalling for the Security Procedure is defined in TS 33.503 [29]. + +When the security protection is enabled, UE-1 sends the following information to the target UE: + +- If IP communication is used: + - IP Address Configuration: For IP communication, IP address configuration is required for this link and indicates one of the following values: + - "DHCPv4 server" if only IPv4 address allocation mechanism is supported by the initiating UE, i.e., acting as a DHCPv4 server; or + - "IPv6 Router" if only IPv6 address allocation mechanism is supported by the initiating UE, i.e., acting as an IPv6 Router; or + - "DHCPv4 server & IPv6 Router" if both IPv4 and IPv6 address allocation mechanism are supported by the initiating UE; or + - "address allocation not supported" if neither IPv4 nor IPv6 address allocation mechanism is supported by the initiating UE. + +- Link-Local IPv6 Address: a link-local IPv6 address formed locally based on RFC 4862 [17] if UE-1 does not support the IPv6 IP address allocation mechanism, i.e. the IP Address Configuration indicates "address allocation not supported". +- QoS Info: the information about PC5 QoS Flow(s). For each PC5 QoS Flow, the PFI and the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and optionally the associated ProSe identifier(s). +- Optional PC5 QoS Rule(s). + +The source Layer-2 ID used for the security establishment procedure is determined as specified in clauses 5.8.2.1 and 5.8.2.4. The destination Layer-2 ID is set to the source Layer-2 ID of the received Direct Communication Request message. + +Upon receiving the security establishment procedure messages, UE-1 obtains the peer UE's Layer-2 ID for future communication, for signalling and data traffic for this unicast link. + +5. A Direct Communication Accept message is sent to UE-1 by the target UE(s) that has successfully established security with UE-1: + - 5a. (UE oriented Layer-2 link establishment) If the Target User Info is included in the Direct Communication Request message, the target UE, i.e. UE-2 responds with a Direct Communication Accept message if the Application Layer ID for UE-2 matches. + - 5b. (ProSe Service oriented Layer-2 link establishment) If the Target User Info is not included in the Direct Communication Request message, the UEs that are interested in using the announced ProSe Service(s) respond to the request by sending a Direct Communication Accept message (UE-2 and UE-4 in Figure 6.4.3.1-1). + +The Direct Communication Accept message includes: + +- Source User Info: Application Layer ID of the UE sending the Direct Communication Accept message. +- QoS Info: the information about PC5 QoS Flow(s). For each PC5 QoS Flow, the PFI and the corresponding PC5 QoS parameters requested by UE-1 (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and optionally the associated ProSe identifiers(s). +- Optional PC5 QoS Rule(s). +- If IP communication is used: + - IP Address Configuration: For IP communication, IP address configuration is required for this link and indicates one of the following values: + - "DHCPv4 server" if only IPv4 address allocation mechanism is supported by the target UE, i.e., acting as a DHCPv4 server; or + - "IPv6 Router" if only IPv6 address allocation mechanism is supported by the target UE, i.e., acting as an IPv6 Router; or + - "DHCPv4 server & IPv6 Router" if both IPv4 and IPv6 address allocation mechanism are supported by the target UE; or + - "address allocation not supported" if neither IPv4 nor IPv6 address allocation mechanism is supported by the target UE. + - Link-Local IPv6 Address: a link-local IPv6 address formed locally based on RFC 4862 [17] if the target UE does not support the IPv6 IP address allocation mechanism, i.e. the IP Address Configuration indicates "address allocation not supported" and UE-1 included a link-local IPv6 address in the security establishment in step 4. The target UE shall include a non-conflicting link-local IPv6 address. + +If both UEs (i.e. the initiating UE and the target UE) are selected to use link-local IPv6 address, they shall disable the duplicate address detection defined in RFC 4862 [17]. + +NOTE 3: When either the initiating UE or the target UE indicates the support of IPv6 routing, the corresponding address configuration procedure would be carried out after the establishment of the layer 2 link and the link-local IPv6 addresses are ignored. + +The ProSe layer of the UE that established PC5 unicast link passes the PC5 Link Identifier assigned for the unicast link and the PC5 unicast link related information down to the AS layer. The PC5 unicast link related information includes Layer-2 ID information (i.e. source Layer-2 ID and destination Layer-2 ID). This enables the AS layer to maintain the PC5 Link Identifier together with the PC5 unicast link related information. + +Two UEs may negotiate the PC5 DRX configuration in the AS layer and the PC5 DRX parameter values can be configured per pair of source and destination Layer-2 IDs in the AS layer. + +6. ProSe data is transmitted over the established unicast link as below: + +The PC5 Link Identifier and PFI are provided to the AS layer, together with the ProSe data. + +Optionally in addition, the Layer-2 ID information (i.e. source Layer-2 ID and destination Layer-2 ID) is provided to the AS layer. + +NOTE 4: It is up to UE implementation to provide the Layer-2 ID information to the AS layer. + +UE-1 sends the ProSe data using the source Layer-2 ID (i.e. UE-1's Layer-2 ID for this unicast link) and the destination Layer-2 ID (i.e. the peer UE's Layer-2 ID for this unicast link). + +NOTE 5: PC5 unicast link is bi-directional, therefore the peer UE of UE-1 can send the ProSe data to UE-1 over the unicast link with UE-1. + +### 6.4.3.2 Link identifier update for a unicast link + +Figure 6.4.3.2-1 shows the link identifier update procedure for a unicast link. When privacy requirements are configured for a ProSe Identifier associated with the unicast link, identifiers used for the unicast mode of 5G ProSe communication over PC5 reference point (e.g. Application Layer ID, Source Layer-2 ID and IP address/prefix) shall be changed over time as specified in clauses 5.8.2.1 and 5.8.2.4. A UE may decide to change the identifiers for other reasons, e.g. application layer requirement. This procedure is used to update and exchange new identifiers between the source and the peer UEs for a unicast link before using the new identifiers, to prevent service interruptions. When there are privacy requirements as indicated above, this procedure is executed over a security protected unicast link. + +If a UE has multiple unicast links using the same Application Layer IDs or Layer-2 IDs, the UE needs to perform the link identifier update procedure over each of the unicast links. + +![Sequence diagram illustrating the link identifier update procedure between UE-1 and UE-2. The diagram shows five steps: 0. Unicast link (established), 1. Link Identifier Update Request (UE-1 to UE-2), 2. Link Identifier Update Response (UE-2 to UE-1), 3. Link Identifier Update Ack (UE-1 to UE-2), 4. Start using each UE's new identifiers (UE-1), and 5. Start using each UE's new identifiers (UE-2).](047dcd17568e167181141afe7c0ee396_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + Note left of UE-1: 0. Unicast link + UE-1->>UE-2: 1. Link Identifier Update Request + UE-2-->>UE-1: 2. Link Identifier Update Response + UE-1->>UE-2: 3. Link Identifier Update Ack + Note left of UE-1: 4. Start using each UE's new identifiers + Note right of UE-2: 5. Start using each UE's new identifiers + +``` + +Sequence diagram illustrating the link identifier update procedure between UE-1 and UE-2. The diagram shows five steps: 0. Unicast link (established), 1. Link Identifier Update Request (UE-1 to UE-2), 2. Link Identifier Update Response (UE-2 to UE-1), 3. Link Identifier Update Ack (UE-1 to UE-2), 4. Start using each UE's new identifiers (UE-1), and 5. Start using each UE's new identifiers (UE-2). + +Figure 6.4.3.2-1: Link identifier update procedure + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.4.3.1. + +1. UE-1 decides to change its identifier(s), e.g. due to the Application Layer ID change or upon expiry of a timer. UE-1 generates its new Layer-2 ID and sends a Link Identifier Update Request message to UE-2 using the old identifiers. + +The Link Identifier Update Request message includes the new identifier(s) to use (including the new Layer-2 ID, Security Information, optionally the new Application Layer ID and optionally new IP address/prefix if IP communication is used). The new identifier(s) shall be cyphered to protect privacy if security is configured for the unicast link. After sending the Link Identifier Update Request message, if the UE-1 has data to send, UE-1 keeps sending data traffic to UE-2 with the old identifiers until UE-1 sends the Link Identifier Update Ack message to UE-2. + +NOTE 1: The timer is running on per Source Layer-2 ID. + +NOTE 2: When one of the two UEs acts as IPv6 router as described in clause 5.5.1.1 and the IP address/prefix also needs to be changed, the corresponding address configuration procedure would be carried out after the Link Identifier update procedure. + +2. Upon reception of the Link Identifier Update Request message, UE-2 changes its identifier(s). UE-2 responds with a Link Identifier Update Response message which includes the new identifier(s) to use (including the new Layer-2 ID, Security Information, optionally the new Application Layer ID and optionally a new IP address/prefix if IP communication is used). The new identifier(s) shall be cyphered to protect privacy if security is configured for the unicast link. The Link Identifier Update Response message is sent using the old identifiers. UE-2 continues to receive traffic with the old Layer-2 ID from UE-1 until UE-2 receives traffic with the new Layer-2 ID from UE-1. After sending the Link Identifier Update Response message, UE-2 keeps sending data traffic to UE-1 with the old identifier, if UE-2 has data to send, until UE-2 receives the Link Identifier Update Ack message from UE-1. +3. Upon reception of the Link Identifier Update Response message, UE-1 responds with a Link Identifier Update Ack message. The Link Identifier Update Ack message includes the new identifier(s) from UE-2, as received on the Link Identifier Update Response message. The Link Identifier Update Ack message is sent using the old identifiers. UE-1 continues to receive traffic with the old Layer-2 ID from UE-2 until UE-1 receives traffic with the new Layer-2 ID from UE-2. +4. The ProSe layer of UE-1 passes the PC5 Link Identifier for the unicast link and the updated Layer-2 IDs (i.e. new Layer-2 ID for UE-1 for the source and new Layer-2 ID of UE-2 for the destination) down to the AS layer. This enables the AS layer to update the provided Layer-2 IDs for the unicast link. + +UE-1 starts using its new identifiers and UE-2's new identifiers for this unicast link. + +5. Upon reception of the Link Identifier Update Ack message, the ProSe layer of UE-2 passes the PC5 Link Identifier for the unicast link and the updated Layer-2 IDs (i.e. new Layer-2 ID of UE-2 for the source and new Layer-2 ID for UE-1 for the destination) down to the AS layer. This enables the AS layer to update the provided Layer-2 IDs for the unicast link. + +UE-2 starts using its new identifiers and UE-1's new identifiers for this unicast link. + +NOTE 3: The Security Information in the above messages also needs to be updated at the same time as the Layer-2 IDs. This is defined in TS 33.503 [29]. + +### 6.4.3.3 Layer-2 link release over PC5 reference point + +Figure 6.4.3.3-1 shows the layer-2 link release procedure over PC5 reference point. + +![Sequence diagram illustrating the Layer-2 link release procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (established), 1. Disconnect Request (sent from UE-1 to UE-2), and 2. Disconnect Response (sent from UE-2 to UE-1).](16eeacaeaa3c80fca6d8c51ee721c7d9_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + Note right of UE-1: 0. Unicast link + UE-1->>UE-2: 1. Disconnect Request + UE-2-->>UE-1: 2. Disconnect Response + +``` + +Sequence diagram illustrating the Layer-2 link release procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (established), 1. Disconnect Request (sent from UE-1 to UE-2), and 2. Disconnect Response (sent from UE-2 to UE-1). + +Figure 6.4.3.3-1: Layer-2 link release procedure + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.4.3.1. + +1. UE-1 sends a Disconnect Request message to UE-2 in order to release the layer-2 link and deletes all context data associated with the layer-2 link. The Disconnect Request message includes Security Information. +2. Upon reception of the Disconnect Request message, UE-2 shall respond with a Disconnect Response message and deletes all context data associated with the layer-2 link. The Disconnect Response message includes Security Information. + +The ProSe layer of each UE informs the AS layer that the unicast link has been released. The ProSe layer uses PC5 Link Identifier to indicate the released unicast link. This enables the AS layer to delete the context related to the released unicast link. + +NOTE: The Security Information in the above messages is defined in TS 33.503 [29]. + +#### 6.4.3.4 Layer-2 link modification for a unicast link + +Figure 6.4.3.4-1 shows the layer-2 link modification procedure for a unicast link. This procedure is used to: + +- add new PC5 QoS Flow(s) in the existing PC5 unicast link. + - This covers the case for adding new PC5 QoS Flow(s) to the existing ProSe service(s) as well as the case for adding new PC5 QoS Flow(s) to new ProSe service(s). +- modify existing PC5 QoS Flow(s) in the existing PC5 unicast link. + - This covers the case for modifying the PC5 QoS parameters for existing PC5 QoS Flow(s). + - This also covers the case for removing the associated ProSe service(s) from existing PC5 QoS Flow(s) as well as the case for associating new ProSe service(s) with existing PC5 QoS Flow(s). +- remove existing PC5 QoS Flow(s) in the existing PC5 unicast link. + +![Sequence diagram illustrating the Layer-2 link modification procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (existing), 1. Link Modification Request (sent from UE-1 to UE-2), and 2. Link Modification Accept (sent from UE-2 to UE-1).](985267cff5b5d65ce5c180ff2ef37118_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + Note left of UE-1: 0. Unicast link + UE-1->>UE-2: 1. Link Modification Request + UE-2-->>UE-1: 2. Link Modification Accept + +``` + +Sequence diagram illustrating the Layer-2 link modification procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (existing), 1. Link Modification Request (sent from UE-1 to UE-2), and 2. Link Modification Accept (sent from UE-2 to UE-1). + +**Figure 6.4.3.4-1: Layer-2 link modification procedure** + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.4.3.1. +1. The ProSe application layer in UE-1 provides application information for PC5 unicast communication. The application information includes the ProSe Service Info and the initiating UE's Application Layer ID. The target UE's Application Layer ID may be included in the application information. If UE-1 decides to reuse the existing PC5 unicast link as specified in clause 5.3.4, so decides to modify the unicast link established with UE-2, UE-1 sends a Link Modification Request to UE-2. + +The Link Modification Request message includes: + +- a) To add new PC5 QoS Flow(s) in the existing PC5 unicast link: + - QoS Info: the information about PC5 QoS Flow(s) to be added. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and optionally the associated ProSe identifier(s). + - Optional PC5 QoS Rule(s). +- b) To modify PC5 QoS Flow(s) in the existing PC5 unicast link: + +- QoS Info: the information about PC5 QoS Flow(s) to be modified. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and optionally the associated ProSe identifier(s). + - Optional PC5 QoS Rule(s). +- c) To remove PC5 QoS Flow(s) in the existing PC5 unicast link: +- PFIs. +2. UE-2 responds with a Link Modification Accept message. + +The Link Modification Accept message includes: + +- For case a) and case b) described in step 1: + - QoS Info: the information about PC5 QoS Flow(s) requested by UE-1. For each PC5 QoS Flow, the PFI, the corresponding PC5 QoS parameters (i.e. PQI and conditionally other parameters such as MFBR/GFBR, etc.) and optionally the associated ProSe identifier(s). + - Optional PC5 QoS Rule(s). + +The ProSe layer of each UE provides information about the unicast link modification to the AS layer. This enables the AS layer to update the context related to the modified unicast link. + +#### 6.4.3.5 Layer-2 link maintenance over PC5 reference point + +The PC5 Signalling Protocol shall support keep-alive functionality that is used to detect if a particular PC5 unicast link is still valid. Either side of the PC5 unicast link can initiate the layer-2 link maintenance procedure (i.e. keep-alive procedure), based on for example triggers from the AS layer or internal timers. The UEs shall minimize the keep-alive signalling, e.g. cancel the procedure if data are successfully received over the PC5 unicast link. + +![Sequence diagram illustrating the Layer-2 link maintenance procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (established), 1. Keep-alive (sent from UE-1 to UE-2), and 2. Keep-alive Ack (sent from UE-2 to UE-1).](235d1bc77e04effc9c7d98ef154009be_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + Note right of UE-1: 0. Unicast link + UE-1->>UE-2: 1. Keep-alive + UE-2-->>UE-1: 2. Keep-alive Ack + +``` + +Sequence diagram illustrating the Layer-2 link maintenance procedure between UE-1 and UE-2. The diagram shows three steps: 0. Unicast link (established), 1. Keep-alive (sent from UE-1 to UE-2), and 2. Keep-alive Ack (sent from UE-2 to UE-1). + +**Figure 6.4.3.5-1: Layer-2 link maintenance procedure** + +0. UE-1 and UE-2 have a unicast link established as described in clause 6.4.3.1. +1. Based on trigger conditions, UE-1 sends a Keep-alive message to UE-2 in order to determine the status of the PC5 unicast link. + +NOTE 1: It is left to Stage 3 to determine the exact triggers for the keep-alive messages. For example, the trigger can be based on a timer associated with the Layer-2 link. The timer can be reset with a successful reception event defined by TS 38.300 [12]. + +2. Upon reception of the Keep-alive message, UE-2 responds with a Keep-alive Ack message. + +The UE initiating the keep-alive procedure shall determine the follow-up actions based on the result of the signalling, e.g. proceed with implicit layer-2 link release. + +NOTE 2: It is left to Stage 3 to determine the follow-up actions. For example, a successful reception event can also cancel the layer-2 link release if received in time. + +#### 6.4.3.6 Layer-2 link management over PC5 reference point for 5G ProSe UE-to-Network Relay + +The Layer-2 link procedures over PC5 reference point for unicast mode 5G ProSe Direct Communication as depicted from clause 6.4.3.1 to clause 6.4.3.5 can be used for the PC5 reference point between 5G ProSe Remote UE and 5G ProSe UE-to-Network Relay, with the following differences and clarifications: + +- The Layer-2 link modification procedure is applicable to ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay, other procedures are applicable to both ProSe Communication via 5G ProSe Layer-2 UE-to-Network Relay and ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay. +- The UE oriented Layer-2 link establishment is used with UE-1 representing the 5G ProSe Remote UE and UE-2 representing the 5G ProSe UE-to-Network Relay. For other procedures either UE-1 represents the 5G ProSe Remote UE and UE-2 represents the 5G ProSe UE-to-Network Relay, or UE-1 represents the 5G ProSe UE-to-Network Relay and UE-2 represents the 5G ProSe Remote UE. I.e. the Layer-2 link establishment is initiated by the 5G ProSe Remote UE, while other procedures may be initiated either by the 5G ProSe Remote UE or by the 5G ProSe UE-to-Network Relay. + +For the UE oriented Layer-2 link establishment as described in the clause 6.4.3.1, + +- In step 1, the 5G ProSe Remote UE determines the destination Layer-2 ID for PC5 unicast link establishment based on the unicast source Layer-2 ID of the selected 5G ProSe UE-to-Network Relay (as specified in clause 5.8.3) during UE-to-Network Relay discovery as specified in clause 6.3.2.3. +- In step 2, 5G ProSe Remote UE (UE-1) determines the Relay Service Code to be used. The Relay Service Code to be used is selected from the received Relay Service Code(s) during UE-to-Network Relay discovery as specified in clause 6.3.2.3. +- In step 3, 5G ProSe Remote UE (UE-1) sends a unicast Direct Communication Request message to the selected 5G ProSe UE-to-Network Relay. The destination Layer-2 ID used to send the Direct Communication Request message shall be unicast Layer-2 ID as determined in step 1. The Direct Communication Request message includes: +- Source User Info: the identity of the Remote UE requesting relay operation (i.e. User Info ID). + +NOTE 1: The details of which additional identity/identities of the Remote UE to be included during Layer-2 link establishment are specified in TS 33.503 [29]. + +- Target User Info: the identity of the UE-to-Network Relay provided to the 5G ProSe Remote UE during UE-to-Network Relay Discovery procedure (i.e. User Info ID). +- Relay Service Code: indicates the connectivity service (which may be non-emergency or emergency) provided by the 5G ProSe UE-to-Network Relay as requested by the 5G ProSe Remote UE. +- Security Information: the information for the establishment of security. + +NOTE 2: PC5 link for emergency RSC can be established with or without PC5 security; how to establish PC5 security link for emergency service is specified in TS 33.503 [29]. + +- In step 4 and step 5, step 4a and step 5a are performed if the 5G ProSe UE-to-Network Relay's identity matches the Target User Info and the Relay Service Code is one of the Relay Service Codes included during UE-to-Network Relay discovery as specified in clause 6.3.2.3. The Source User Info in the Direct Communication Accept message is the identity of the UE-to-Network Relay (i.e. User Info ID). In the case of 5G ProSe Layer-2 UE-to-Network Relay, the Remote UE does not send the IP Address Configuration, Link-Local IPv6 Address and QoS Info to the 5G ProSe Layer-2 UE-to-Network Relay and the Direct Communication Accept message does not include IP Address Configuration, Link-Local IPv6 Address and QoS Info. In the case of 5G ProSe Layer-3 UE-to-Network Relay, the Direct Communication Accept message does not include the IP Address Configuration indicating the value "address allocation not supported". +- In the case of 5G ProSe Layer-2 UE-to-Network Relay, step 6 is not performed. + +For the link identifier update as described in the clause 6.4.3.2, + +- Application Layer ID is replaced by User Info ID. + +- In the case of 5G ProSe Layer-2 UE-to-Network Relay, the changed identifiers do not include IP address/prefix. + +For the Layer-2 link release as described in the clause 6.4.3.3, + +- In step1, if the Layer-2 link release procedure is initiated by the 5G ProSe UE-to-Network Relay, the Disconnect Request message may indicate the 5G ProSe UE-to-Network Relay is temporarily not available as described in clause 5.12. + +NOTE 3: The form of the temporarily not available indication will be determined by stage 3. + +- If the service authorization for acting as a 5G ProSe Remote UE or as a 5G ProSe UE-to-Network Relay is revoked, the 5G ProSe Remote UE or the 5G ProSe UE-to-Network Relay should initiate the release of the layer-2 link that the revoked authorization affects. +- A 5G ProSe Layer-2 Remote UE or a 5G ProSe Layer-2 UE-to-Network Relay initiates the release of the layer-2 link upon receiving an indication from its AS layer to trigger PC5 unicast link release as specified in TS 38.331 [16]. + +NOTE 4: The timing to initiates layer-2 link release is up to UE implementation. + +A 5G ProSe Remote UE and a 5G ProSe UE-to-Network Relay shall set up a separate PC5 unicast links if an existing unicast link(s) was established with a different Relay Service Code or without a Relay Service Code. + +NOTE 5: A single PC5 unicast link is established between a 5G ProSe Layer-2 UE-to-Network Relay and a 5G ProSe Layer-2 Remote UE, as specified in TS 38.300 [12], for supporting PDU sessions of the 5G ProSe Layer-2 Remote UE. + +Each PC5 unicast link for 5G ProSe UE-to-Network Relay is associated with a Unicast Link Profile, which includes: + +- User Info ID and Layer-2 ID of 5G ProSe Remote UE; and +- User Info ID and Layer-2 ID of 5G ProSe UE-to-Network Relay; and +- Relay Service Code; and +- In the case of 5G ProSe Layer-3 UE-to-Network Relay, the network layer protocol and the information about PC5 QoS Flow(s). + +The Unicast Link Profile shall be updated accordingly after a Layer-2 link modification or Layer-2 link identifier update. + +### 6.4.3.7 Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay + +#### 6.4.3.7.1 Common part for Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay + +For the 5G ProSe Communication via 5G ProSe UE-to-UE Relay as described in clause 6.7.1 and clause 6.7.2: + +- The Direct Communication Request message over the first hop PC5 reference point includes: + - User Info ID of source 5G ProSe End UE: the identity of the source 5G ProSe End UE requesting relay operation. + - User Info ID of 5G ProSe UE-to-UE Relay: the identity of the UE-to-UE Relay provided to the source 5G ProSe End UE during 5G ProSe UE-to-UE Relay Discovery procedure. + - User Info ID of target 5G ProSe End UE: the identity of the target 5G ProSe End UE provided to the source 5G ProSe End UE during UE-to-UE Relay Discovery procedure. + - (optional) Destination Layer-2 ID of target 5G ProSe End UE: the unicast destination Layer-2 ID of the target 5G ProSe End UE determined by the source 5G ProSe End UE as specified in clause 5.8.2.4. + - ProSe Service Info: the information about the ProSe identifier(s) requesting Layer-2 link establishment. + +- RSC: the connectivity service provided by the 5G ProSe UE-to-UE Relay as requested by the source 5G ProSe End UE. +- Security Information: the information for the establishment of security for the first hop PC5 link establishment. + +NOTE 1: The Security Information is defined by SA WG3. + +The Direct Communication Request message over the second hop PC5 reference point includes: + +- User Info ID of source 5G ProSe End UE. +- User Info ID of target 5G ProSe End UE. +- User Info ID of 5G ProSe UE-to-UE Relay. +- ProSe Service Info: the information about the ProSe identifier(s). +- RSC: the connectivity service provided by the 5G ProSe UE-to-UE Relay as requested by the source 5G ProSe End UE. +- Security Information: the information for the establishment of security for the second hop PC5 link establishment. + +NOTE 2: The Security Information is defined by SA WG3. + +The Direct Communication Accept message over the second hop PC5 reference point includes: + +- User Info ID of target 5G ProSe End UE. + +The Direct Communication Accept message over the first hop PC5 reference point includes: + +- User Info ID of target 5G ProSe End UE. +- User Info ID of 5G ProSe UE-to-UE Relay. + +The Link Modification Request message over the first hop PC5 reference point includes: + +- User Info ID of target 5G ProSe End UE: the identity of the target 5G ProSe End UE provided to the source 5G ProSe End UE during UE-to-UE Relay Discovery procedure. +- (optional) Destination Layer-2 ID of target 5G ProSe End UE: the unicast destination Layer-2 ID of the target 5G ProSe End UE determined by the source 5G ProSe End UE as specified in clause 5.8.2.4. + +The Link Modification Request message over the second hop PC5 reference point includes: + +- User Info ID of source 5G ProSe End UE. +- User Info ID of target 5G ProSe End UE. + +The Link Modification Accept message over the second hop PC5 reference point includes: + +- User Info ID of target 5G ProSe End UE. + +The Link Modification Accept message over the first hop PC5 reference point includes: + +- User Info ID of target 5G ProSe End UE. + +#### 6.4.3.7.2 Layer-2 link management over PC5 reference point for 5G ProSe Layer-2 UE-to-UE Relay + +For the 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay as described in clause 6.7.2, the description in clause 6.4.3.7.1 applies. + +The message contents over PC5 reference point for unicast mode 5G ProSe Direct Communication as depicted from clause 6.4.3.1 to clause 6.4.3.5 are same for the end-to-end connection between peer 5G ProSe End UEs. + +**Editor's note:** Whether the LIU between peer Layer-2 End UEs has same message contents as direct PC5 LIU messages is FFS. + +#### 6.4.3.7.3 Layer-2 link management over PC5 reference point for 5G ProSe Layer-3 UE-to-UE Relay + +For the 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay as described in clause 6.7.1, the description in clause 6.4.3.7.1 applies with following differences and clarifications: + +- In the Security Procedure of the first hop PC5 reference point, the source 5G ProSe Layer-3 End UE provides the IP Address Configuration or Link-Local IPv6 Address and QoS Info of the end-to-end QoS to the 5G ProSe Layer-3 UE-to-UE Relay. If the PC5 link is used for transferring Ethernet traffic, the source 5G ProSe Layer-3 End UE provides its Ethernet MAC address instead of IP related information. +- In the Security Procedure of the second hop PC5 reference point, the 5G ProSe Layer-3 UE-to-UE Relay provides the IP Address Configuration or Link-Local IPv6 Address and QoS Info of the second hop QoS to the target 5G ProSe End UE. If the PC5 link is used for transferring Ethernet traffic, the 5G ProSe Layer-3 UE-to-UE Relay provides the Ethernet MAC address of the source 5G ProSe Layer-3 End UE instead of IP related information. +- The Direct Communication Accept message over the second hop PC5 reference point additionally includes IP Address Configuration or Link-Local IPv6 Address and QoS Info of the second hop QoS. If the PC5 link is used for transferring Ethernet traffic, the target 5G ProSe Layer-3 End UE provides its Ethernet MAC address instead of IP related information. +- The 5G ProSe Layer-3 UE-to-UE Relay decides the QoS Info of the first hop QoS with considering the received second hop QoS, the Direct Communication Accept message over the first hop PC5 reference point additionally includes IP Address Configuration or Link-Local IPv6 Address, QoS Info of the first hop QoS and may include IP address of the target 5G ProSe End UE. If the PC5 link is used for transferring Ethernet traffic, 5G ProSe Layer-3 UE-to-UE Relay provides the Ethernet MAC address of the target 5G ProSe Layer-3 End UE instead of IP related information. +- For adding new end-to-end QoS flow or modifying existing end-to-end QoS flow, in the Link Modification Request message over the first hop PC5 reference point, the source 5G ProSe End UE additionally includes QoS Info of the end-to-end QoS as described in the clause 6.4.3.4. For removing end-to-end QoS flows(s), in the Link Modification Request message over the first hop PC5 reference point, the source 5G ProSe End UE includes PFI(s) of the QoS flow(s) of the first hop as described in the clause 6.4.3.4. If the PC5 link is used for transferring Ethernet traffic, the source 5G ProSe Layer-3 End UE may provide its Ethernet MAC address. +- For adding new end-to-end QoS flow or modifying existing end-to-end QoS flow, in the Link Modification Request message over the second hop PC5 reference point, the 5G ProSe Layer-3 UE-to-UE Relay additionally includes QoS Info of the second hop QoS to the target 5G ProSe End UE. For removing end-to-end QoS flow(s), in the Link Modification Request message over the second hop PC5 reference point, the 5G ProSe Layer-3 UE-to-UE Relay includes PFI(s) of the QoS flow(s) of the second hop. If the PC5 link is used for transferring Ethernet traffic, the 5G ProSe Layer-3 UE-to-UE Relay provides the Ethernet MAC address of the source 5G ProSe Layer-3 End UE. +- For adding new end-to-end QoS flow or modifying existing end-to-end QoS flow, the Link Modification Accept message over the second hop PC5 reference point additionally includes QoS Info of the second hop QoS. If the PC5 link is used for transferring Ethernet traffic, the target 5G ProSe Layer-3 End UE may provide its Ethernet MAC address. +- For adding new end-to-end QoS flow or modifying existing end-to-end QoS flow, the 5G ProSe Layer-3 UE-to-UE Relay decides the QoS Info of the first hop QoS with considering the received second hop QoS, the Link Modification Accept message over the first hop PC5 reference point additionally includes QoS Info of the first hop QoS and may include IP address of the target 5G ProSe End UE. If the PC5 link is used for transferring Ethernet traffic, 5G ProSe Layer-3 UE-to-UE Relay provides the Ethernet MAC address of the target 5G ProSe Layer-3 End UE instead of IP related information. + +When the PC5 link between a 5G ProSe Layer-3 End UE and the 5G ProSe Layer-3 UE-to-UE Relay is released, the 5G ProSe Layer-3 UE-to-UE Relay may initiate the PC5 link release to the peer 5G ProSe Layer-3 End UE(s) or notify the peer 5G ProSe Layer-3 End UE(s) the peer PC5 link is released. + +#### 6.4.3.7.4 Layer-2 link management over PC5 reference point for 5G ProSe UE-to-UE Relay Communication with integrated Discovery + +This clause is for the 5G ProSe UE-to-UE Relay Communication with integrated Discovery procedure as described in clause 6.7.3. + +The Direct Communication Request message over the first hop PC5 reference point includes: + +- User Info ID of source 5G ProSe End UE. +- (optional) User Info ID of target 5G ProSe End UE: the identity of the target 5G ProSe End UE if provided from the ProSe application layer. +- (optional) Destination Layer-2 ID of target 5G ProSe End UE: the unicast destination Layer-2 ID of the target 5G ProSe End UE determined by the source 5G ProSe End UE as specified in clause 5.8.2.4. +- ProSe Service Info: the information about the ProSe identifier(s) requesting Layer-2 link establishment. +- RSC: the connectivity service provided by the 5G ProSe UE-to-UE Relay as requested by the source 5G ProSe End UE. +- Relay\_indication: indicates whether the Direct Communication Request message can be forwarded by a 5G ProSe UE-to-UE Relay. +- Security Information: the information for the establishment of security for the first hop PC5 link establishment. + +NOTE 1: The Security Information is defined by SA WG3. + +The Direct Communication Request message over the second hop PC5 reference point includes: + +- User Info ID of source 5G ProSe End UE. +- User Info ID of 5G ProSe UE-to-UE Relay. +- (optional) User Info ID of target 5G ProSe End UE. +- ProSe Service Info: the information about the ProSe identifier(s). +- RSC: the connectivity service provided by the 5G ProSe UE-to-UE Relay as requested by the source 5G ProSe End UE. +- Security Information: the information for the establishment of security for the second hop PC5 link establishment. + +NOTE 2: The Security Information is defined by SA WG3. + +The Direct Communication Accept message over the second hop PC5 reference point includes: + +- User Info ID of target 5G ProSe End UE. + +The Direct Communication Accept message over the first hop PC5 reference point includes: + +- User Info ID of target 5G ProSe End UE. +- User Info ID of 5G ProSe UE-to-UE Relay. + +For the 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay, additional clarifications are as following: + +- In the Security Procedure of the second hop PC5 reference point, the 5G ProSe Layer-3 UE-to-UE Relay provides the IP Address Configuration or Link-Local IPv6 Address to the target 5G ProSe End UE. +- The Direct Communication Accept message over the second hop PC5 reference point additionally includes IP Address Configuration or Link-Local IPv6 Address (if IP communication is used), Ethernet MAC address of target 5G ProSe End UE (if Ethernet communication is used). QoS Info is not included in the Security Procedure or Direct Communication Accept message of the second hop PC5 reference point. + +- In the Security Procedure of the first hop PC5 reference point, the source 5G ProSe End UE provides the IP Address Configuration, Link-Local IPv6 Address and QoS Info of the end-to-end QoS to the 5G ProSe Layer-3 UE-to-UE Relay. +- The 5G ProSe Layer-3 UE-to-UE Relay provides the QoS info of the second hop QoS to the target 5G ProSe End UE using the Layer-2 link modification as described in the clause 6.4.3.4. +- The 5G ProSe Layer-3 UE-to-UE Relay decides the QoS Info of the first hop QoS with considering the received second hop QoS from the target 5G ProSe End UE, the Direct Communication Accept message over the first hop PC5 reference point additionally includes IP Address Configuration or Link-Local IPv6 Address, QoS Info of the first hop QoS and may include IP address of the target 5G ProSe End UE (if IP communication is used) or Ethernet MAC address of target 5G ProSe End UE (if Ethernet communication is used). + +For the 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay, the message contents over PC5 reference point for unicast mode 5G ProSe Direct Communication as depicted from clause 6.4.3.1 to clause 6.4.3.5 are same for the end-to-end connection between peer 5G ProSe End UEs. + +## 6.5 5G ProSe UE-to-Network Relay Communication + +### 6.5.1 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay + +#### 6.5.1.0 General + +5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay may be performed with or without involving N3IWF for non-emergency service and for emergency service as specified in clause 5.4.4. + +#### 6.5.1.1 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF + +A 5G ProSe Layer-3 UE-to-Network Relay registers to the network (if not already registered). 5G ProSe Layer-3 UE-to-Network Relay establishes a PDU Session(s) or modifies an existing PDU Session(s) in order to provide relay traffic towards 5G ProSe Layer-3 Remote UE(s). PDU Session(s) supporting 5G ProSe Layer-3 UE-to-Network Relay shall only be used for 5G ProSe Layer-3 Remote UE(s) relay traffic. + +The PLMN serving the 5G ProSe Layer-3 UE-to-Network Relay and the PLMN to which the 5G ProSe Layer-3 Remote UE registers can be the same PLMN or two different PLMNs. + +![Sequence diagram for 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF. The diagram shows interactions between Remote UE, Layer-3 UE-to-NW Relay, NG-RAN, AMF, SMF, and UPF. Steps include: 1a. Authorization and Provisioning for Layer-3 UE-to-NW Relay; 1b. Authorization and Provisioning for Remote UE; 2. PDU Session establishment; 3. Discovery Procedure; 4. Establishment of connection For unicast mode communication; 5. IP address/prefix allocation; 6. Layer-2 link modification; 7. Remote UE Report (Remote User ID, Remote UE info). Relayed traffic is shown between the Remote UE and the UPF via the Layer-3 UE-to-NW Relay.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant Layer-3 UE-to-NW Relay + participant NG-RAN + participant AMF + participant SMF + participant UPF + + Note right of Layer-3 UE-to-NW Relay: 1a. Authorization and Provisioning for Layer-3 UE-to-NW Relay + Note right of Remote UE: 1b. Authorization and Provisioning for Remote UE + Note right of Layer-3 UE-to-NW Relay: 2. PDU Session establishment + Note right of Remote UE: 3. Discovery Procedure + Note right of Remote UE: 4. Establishment of connection For unicast mode communication + Note right of Layer-3 UE-to-NW Relay: 4. Relay UE may establish a new PDU Session + Note right of Remote UE: 5. IP address/prefix allocation + Note right of Remote UE: 6. Layer-2 link modification + Note right of Layer-3 UE-to-NW Relay: 6. Relay UE may modify existing PDU Session for relaying + Note right of Remote UE: 7. Remote UE Report (Remote User ID, Remote UE info) + Remote UE->>UPF: Relayed traffic + +``` + +Sequence diagram for 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF. The diagram shows interactions between Remote UE, Layer-3 UE-to-NW Relay, NG-RAN, AMF, SMF, and UPF. Steps include: 1a. Authorization and Provisioning for Layer-3 UE-to-NW Relay; 1b. Authorization and Provisioning for Remote UE; 2. PDU Session establishment; 3. Discovery Procedure; 4. Establishment of connection For unicast mode communication; 5. IP address/prefix allocation; 6. Layer-2 link modification; 7. Remote UE Report (Remote User ID, Remote UE info). Relayed traffic is shown between the Remote UE and the UPF via the Layer-3 UE-to-NW Relay. + +**Figure 6.5.1.1-1: 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF** + +- Service authorization and provisioning are performed for the 5G ProSe Layer-3 UE-to-Network Relay (step 1a) and 5G ProSe Layer-3 Remote UE (step 1b) as described in clause 6.2. +- The 5G ProSe Layer-3 UE-to-Network Relay may establish a PDU Session for relaying. In the case of IPv6, the 5G ProSe Layer-3 UE-to-Network Relay obtains the IPv6 prefix via prefix delegation function from the network as defined in TS 23.501 [4]. + +NOTE 1: 5G ProSe Layer-3 UE-to-Network Relay can establish a PDU Session for any Relay Service Code it supports before the connection is established with the 5G ProSe Layer-3 Remote UE. + +- The 5G ProSe Layer-3 Remote UE performs discovery of a 5G ProSe Layer-3 UE-to-Network Relay as described in clause 6.3.2.3. As part of the discovery procedure the 5G ProSe Layer-3 Remote UE learns about the connectivity service the 5G ProSe Layer-3 UE-to-Network Relay provides. +- The 5G ProSe Layer-3 Remote UE selects a 5G ProSe Layer-3 UE-to-Network Relay and establishes a connection for unicast mode communication as described in clause 6.4.3.6. If there is no PDU Session associated with the Relay Service Code or a new PDU Session for relaying is needed, the 5G ProSe Layer-3 UE-to-Network Relay initiates a new PDU Session establishment procedure for relaying before completing the PC5 connection establishment. + +When the 5G ProSe Layer-3 Remote UE sends the Direct Communication Request message including the dedicated emergency RSC, the 5G ProSe Layer-3 UE-to-Network Relay sets up an emergency PDU session for relaying the emergency service if there is not an emergency PDU Session established in step 2. + +NOTE 2: If the 5G ProSe Layer-3 UE-to-Network Relay has its own emergency service ongoing, how to handle the conflict case is specified in clause 5.4.4.3. + +The network decides that the PDU Session to be established is for relay traffic and then generates the QoS rules and QoS Flow level QoS parameters to 5G ProSe Layer-3 UE-to-Network Relay with relay consideration and can initiate the setup of QoS flows as specified in clause 5.6.2.1. The Remote UE can also initiate the setup of QoS flows by providing PC5 QoS info and (optionally) PC5 QoS rule(s) to the 5G ProSe Layer-3 UE-to-Network Relay during connection setup, according to the procedure as specified in clause 5.6.2.1. + +The 5G ProSe Layer-3 UE-to-Network Relay determines the PDU Session type for relaying as specified in clause 5.4.1.1. + +According to the PDU Session Type for relaying, the 5G ProSe Layer-3 UE-to-Network Relay performs relaying function at the corresponding layer as follows: + +- When the IP type PDU Session is used for IP traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay acts as an IP router. For IPv4, the 5G ProSe Layer-3 UE-to-Network Relay performs IPv4 NAT between IPv4 addresses assigned to the 5G ProSe Layer-3 Remote UE and the IPv4 address assigned to the PDU Session used for the relay traffic. + - When the Ethernet type PDU Session is used for Ethernet traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay acts as an Ethernet switch. + - When the Unstructured type PDU Session is used for Unstructured traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay performs traffic relaying based on a mapping between the PC5 Link Identifier and the PDU Session ID and a mapping between PFI for PC5 Layer-2 link and the QFI for the PDU Session. These mappings are created when the Unstructured type PDU Session is established for the 5G ProSe Layer-3 Remote UE. + - When the IP type PDU Session is used for Ethernet or Unstructured traffic over PC5 reference point, the 5G ProSe Layer-3 UE-to-Network Relay uses IP tunneling. For this IP tunnelling, the 5G ProSe Layer-3 UE-to-Network Relay locally assigns an IP address/prefix for the 5G ProSe Layer-3 Remote UE and uses it on the Uu reference point to encapsulate and decapsulate the uplink and downlink traffic for the 5G ProSe Layer-3 Remote UE. The tunnelled traffic over Uu reference point is transported over the PC5 reference point as Ethernet or Unstructured traffic. +5. For IP PDU Session Type and IP traffic over PC5 reference point, IPv6 prefix or IPv4 address (including NAT case) is allocated for the 5G ProSe Layer-3 Remote UE as defined in clause 5.5.1.3. + 6. The 5G ProSe Layer-3 Remote UE may provide PC5 QoS Info and PC5 QoS rule(s) to the 5G ProSe Layer-3 UE-to-Network Relay using Layer-2 link modification procedure as specified in clause 6.4.3.4. The 5G ProSe Layer-3 UE-to-Network Relay generates the Packet Filters used over Uu interface based on the received PC5 QoS Info and QoS Rule(s) as described in clause 5.6.2.1 and may perform the UE requested PDU Session Modification as defined in TS 23.502 [5] clause 4.3.3 to setup a new QoS Flow or bind the traffic to an existing QoS Flow. + +From this point the uplink and downlink relaying can start. For downlink traffic forwarding, the PC5 QoS Rule is used to map the downlink packet to the PC5 QoS Flow. For uplink traffic forwarding, the 5G QoS Rule is used to map the uplink packet to the Uu QoS Flow. + +7. The 5G ProSe Layer-3 UE-to-Network Relay shall send a Remote UE Report (Remote User ID, Remote UE info) message to the SMF for the PDU Session associated with the relay. The Remote User ID, as defined in TS 33.503 [29], is an identity of the 5G ProSe Layer-3 Remote UE user that was successfully connected in step 4. The Remote UE info is used to assist identifying the 5G ProSe Layer-3 Remote UE in the 5GC. For IP PDU Session Type, the Remote UE info is Remote UE IP info. For Ethernet PDU Session Type, the Remote UE info is Remote UE MAC address which is detected by the 5G ProSe Layer-3 UE-to-Network Relay. For Unstructured PDU Session Type, the Remote UE info is not included. The SMF stores the Remote User IDs and the related Remote UE info in the 5G ProSe Layer-3 UE-to-Network Relay's SM context for this PDU Session associated with the relay. + +The Remote UE Report is N1 SM NAS message sent with the PDU Session ID to the AMF, in turn delivered to the SMF. + +NOTE 3: The privacy protection for Remote User ID is specified in TS 33.503 [29]. + +For IP info the following principles apply: + +- for IPv4, the 5G ProSe Layer-3 UE-to-Network Relay shall report TCP/UDP port ranges assigned to individual 5G ProSe Layer-3 Remote UE(s) (along with the Remote User ID); +- for IPv6, the 5G ProSe Layer-3 UE-to-Network Relay shall report IPv6 prefix(es) assigned to individual 5G ProSe Layer-3 Remote UE(s) (along with the Remote User ID). + +If the PDU Session for relaying is released by the UE-to-Network Relay or the network as described in clause 4.3.4 of TS 23.502 [5], the UE-to-Network Relay should initiate the release of the layer-2 links associated with the released PDU Session using the procedure defined in clause 6.4.3.3. + +The PDU Session(s) used for relaying should be released as described in clause 4.3.4 of TS 23.502 [5] (e.g. by 5G ProSe Layer-3 UE-to-Network Relay), if the service authorization for acting as a 5G ProSe Layer-3 UE-to-Network Relay in the serving PLMN is revoked. + +The 5G ProSe Layer-3 UE-to-Network Relay shall send the Remote UE Report message when the 5G ProSe Layer-3 Remote UE disconnects from the 5G ProSe Layer-3 UE-to-Network Relay (e.g. upon explicit layer-2 link release or based on the absence of keep alive messages over PC5) to inform the SMF that the 5G ProSe Layer-3 Remote UE(s) have left. + +NOTE 4: In order for the SMF to have the 5G ProSe Layer-3 Remote UE(s) information, the HPLMN and the VPLMN where the 5G ProSe Layer-3 UE-to-Network Relay is authorised to operate, needs to support the transfer of the 5G ProSe Layer-3 Remote UE related parameters if the SMF is in the HPLMN. + +It is up to 5G ProSe Layer-3 UE-to-Network Relay implementation how PDU Session(s) used for relaying are released or QoS Flow(s) used for relaying are removed by the 5G ProSe Layer-3 UE-to-Network Relay when 5G ProSe Layer-3 Remote UE(s) disconnect from the 5G ProSe Layer-3 UE-to-Network Relay. + +### 6.5.1.2 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support + +#### 6.5.1.2.1 Connection management via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support + +In order to relay 5G ProSe Layer-3 Remote UE's traffic via N3IWF (see clause 6.5.1.2.2 for N3IWF selection), the 5G ProSe Layer-3 UE-to-Network Relay needs suitable ProSe Policies configured for establishing a PDU Session associated with a UPF that conveys the traffic towards the N3IWF. A 5G ProSe Layer-3 UE-to-Network Relay registers to the network as specified in clause 6.5.1.1. Based on configuration and authorization, the 5G ProSe Layer-3 UE-to-Network Relay is provisioned with PDU Session parameters in the ProSe Policy allowing the access to the N3IWF. When the corresponding PDU Session is established, the 5GS, e.g. SMF, based on the parameters (i.e. DNN, S-NSSAI) selects the UPF that ensures the connection to the N3IWF. The UPF for the 5G ProSe UE-to-Network Relay and the N3IWF may be collocated. + +A 5G ProSe Layer-3 UE-to-Network Relay with a PDU Session providing access via N3IWF may also have other PDU Sessions for supporting access from the 5G ProSe Layer-3 Remote UE without going through a N3IWF. + +NOTE 1: Whether a different PDU Sessions need to be established to serve traffics for Layer-3 Remote UE with or without going through a N3IWF is determined by Layer-3 Relay UE per TS 23.503 [9]. + +![Sequence diagram showing connection establishment over 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support. The diagram involves seven lifelines: Remote UE, UE-to-NW Relay UE, NG-RAN, AMF, SMF, UPF, and N3IWF. The sequence of messages is: 1. 5GS Registration and/or PDU session connectivity (UE ProSe policy) from Remote UE to AMF; 2. 5GS Registration, authorization and provisioning (UE ProSe policy, URSP) from AMF to Remote UE; 3. UE-to-NW Relay Discovery procedure from Remote UE to UE-to-NW Relay UE; 4. Establishment of connection for one-to-one PC5 communication session from Remote UE to UE-to-NW Relay UE; 5. Relay UE may establish new PDU session(s) for Relay from UE-to-NW Relay UE to SMF; 6. IP address/prefix allocation from SMF to UE-to-NW Relay UE; 7. UE selects an N3IWF and obtains its IP address from UE-to-NW Relay UE to Remote UE; 8. UE performs NAS Registration and establishes Ipsec tunnel using IKE procedures with N3IWF as provided in Figure 4.12.2.2-1 of TS 23.502 from Remote UE to N3IWF; 9. Additional Child SA, configuration and QoS policy's are exchanged as specified in clause 5.6.2.2 from N3IWF to Remote UE.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +``` + +sequenceDiagram + participant Remote UE + participant UE-to-NW Relay UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + participant N3IWF + + Note right of Remote UE: 1. 5GS Registration and/or PDU session connectivity (UE ProSe policy) + Remote UE->>AMF: 1. 5GS Registration and/or PDU session connectivity (UE ProSe policy) + Note right of AMF: 1. 5GS Registration, authorization and provisioning (UE ProSe policy, URSP) + AMF-->>Remote UE: 1. 5GS Registration, authorization and provisioning (UE ProSe policy, URSP) + Note right of Remote UE: 2. UE-to-NW Relay Discovery procedure + Remote UE->>UE-to-NW Relay UE: 2. UE-to-NW Relay Discovery procedure + Note right of Remote UE: 3. Establishment of connection for one-to-one PC5 communication session + Remote UE->>UE-to-NW Relay UE: 3. Establishment of connection for one-to-one PC5 communication session + Note right of UE-to-NW Relay UE: 3. Relay UE may establish new PDU session(s) for Relay + UE-to-NW Relay UE->>SMF: 3. Relay UE may establish new PDU session(s) for Relay + Note right of SMF: 4. IP address/prefix allocation + SMF-->>UE-to-NW Relay UE: 4. IP address/prefix allocation + Note right of UE-to-NW Relay UE: 5. UE selects an N3IWF and obtains its IP address + UE-to-NW Relay UE-->>Remote UE: 5. UE selects an N3IWF and obtains its IP address + Note right of Remote UE: 6. UE performs NAS Registration and establishes Ipsec tunnel using IKE procedures with N3IWF as provided in Figure 4.12.2.2-1 of TS 23.502 + Remote UE->>N3IWF: 6. UE performs NAS Registration and establishes Ipsec tunnel using IKE procedures with N3IWF as provided in Figure 4.12.2.2-1 of TS 23.502 + Note right of N3IWF: 7. Additional Child SA, configuration and QoS policy's are exchanged as specified in clause 5.6.2.2 + N3IWF-->>Remote UE: 7. Additional Child SA, configuration and QoS policy's are exchanged as specified in clause 5.6.2.2 + +``` + +Sequence diagram showing connection establishment over 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support. The diagram involves seven lifelines: Remote UE, UE-to-NW Relay UE, NG-RAN, AMF, SMF, UPF, and N3IWF. The sequence of messages is: 1. 5GS Registration and/or PDU session connectivity (UE ProSe policy) from Remote UE to AMF; 2. 5GS Registration, authorization and provisioning (UE ProSe policy, URSP) from AMF to Remote UE; 3. UE-to-NW Relay Discovery procedure from Remote UE to UE-to-NW Relay UE; 4. Establishment of connection for one-to-one PC5 communication session from Remote UE to UE-to-NW Relay UE; 5. Relay UE may establish new PDU session(s) for Relay from UE-to-NW Relay UE to SMF; 6. IP address/prefix allocation from SMF to UE-to-NW Relay UE; 7. UE selects an N3IWF and obtains its IP address from UE-to-NW Relay UE to Remote UE; 8. UE performs NAS Registration and establishes Ipsec tunnel using IKE procedures with N3IWF as provided in Figure 4.12.2.2-1 of TS 23.502 from Remote UE to N3IWF; 9. Additional Child SA, configuration and QoS policy's are exchanged as specified in clause 5.6.2.2 from N3IWF to Remote UE. + +**Figure 6.5.1.2.1-1: Connection establishment over 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support** + +1. 5G ProSe Layer-3 UE-to-Network Relay performs Registration procedures and obtains the ProSe Policy that corresponds to the operation supporting the access to N3IWF. The ProSe Policy includes the RSC and PDU Session parameters allowing the access to the N3IWF. + +The 5G ProSe Layer-3 Remote UE is configured with the corresponding ProSe Policy and URSP rules. The URSP policy indicates if a particular service needs to be accessed within a PDU Session and thus should use a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support as described in clause 6.5.4. + +- 2-4. A 5G ProSe Layer-3 UE-to-Network Relay and 5G ProSe Layer-3 Remote UE follow the procedures described in steps 3-5 in clause 6.5.1.1 using the RSC configured for making the 5G ProSe Layer-3 Remote UE access to 5GC via N3IWF. + +NOTE 2: The services requiring the access via N3IWF can be configured with the RSC(s) that can be served by the same 5G ProSe UE-to-Network Relay. + +5. The 5G ProSe Layer-3 Remote UE that connects to a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support selects an N3IWF and determines the N3IWF IP address. The 5G ProSe Layer-3 Remote UE follows the N3IWF selection procedure as described in clause 6.5.1.2.2. +6. The 5G ProSe Layer-3 Remote UE establishes a signalling IPsec tunnel using IKE procedures with a N3IWF and performs NAS Registration as shown in Figure 4.12.2.2-1 of TS 23.502 [5]. After the IPsec tunnel is established, the 5G ProSe Layer-3 Remote UE can perform any of the NAS procedures (incl. PDU Session establishment for the 5G ProSe Layer-3 UE-to-Network Relay PDU Sessions) as specified in clause 4.12 of TS 23.502 [5]. +7. After the PDU session(s) and associated QoS Flows are established in the 5G ProSe Layer-3 Remote UE's 5GC, the N3IWF determines the number of IPsec Child SA(s) that is needed and initiates the creation of the Child SA(s) as specified in clause 4.12.5 of TS 23.502 [5]. Once the Child SA(s) has been created the 5G ProSe Layer-3 Remote UE will have the mapping between the DSCP markings for the IPsec Child SA(s), the corresponding QoS and N3IWF IP address(es) and provides this information, if needed, to the 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 5.6.2.2. If needed, the 5G ProSe Layer-3 UE-to-Network Relay performs the PDU Session Modification procedure to request QoS flow(s) configuration that maps to the 5G ProSe Layer-3 Remote UE's Child SA(s). + +IKE keep alive(s) between the 5G ProSe Layer-3 Remote UE and the N3IWF are used for detecting possible path failure. The 5G ProSe Layer-3 Remote UE may change 5G ProSe Layer-3 UE-to-Network Relay(s) while maintain the session with the N3IWF when the 5G ProSe Layer-3 Remote UE and the N3IWF support MOBIKE. This is negotiated between the 5G ProSe Layer-3 Remote UE and the N3IWF as specified in TS 23.502 [5], clause 4.12.2.2). When IKE keep alive(s) are used, the 5G ProSe Layer-3 Remote UE needs to keep the PC5 connection and 5G ProSe Layer-3 UE-to-Network Relay keeps the PDU Session. + +When 5G ProSe Remote UE is in CM-CONNECTED state, the 5G ProSe Remote UE keeps the PC5 link. When the 5G ProSe Remote UE is in CM-IDLE state, it may either release the PC5 link for relaying or not. + +#### 6.5.1.2.2 N3IWF selection for 5G ProSe Layer-3 Remote UE procedure + +When the 5G ProSe Layer-3 Remote UE relays traffic over 5G ProSe Layer-3 UE-to-Network Relay that supports N3IWF, the 5G ProSe Layer-3 Remote UE selects the N3IWF using the N3IWF selection procedure that is specified in clause 6.3.6.2 of TS 23.501 [4] for untrusted non-3GPP access with the following differences. + +To support the N3IWF selection for 5G ProSe Layer-3 Remote UE, a 5G ProSe Layer-3 Remote UE is configured by HPLMN with N3IWF identifier configuration for 5G ProSe Layer-3 Remote UE and 5G ProSe Layer-3 UE-to-Network Relay access node selection information as described in clause 5.1.4.1. + +When the 5G ProSe Layer-3 Remote UE decides to select an N3IWF in the HPLMN, the 5G ProSe Layer-3 Remote UE uses the N3IWF identifier configuration for 5G ProSe Layer-3 Remote UE, if configured, to find the IP address of the N3IWF in the HPLMN. Otherwise, 5G ProSe Layer-3 Remote UE constructs N3IWF FQDN based on either the Tracking Area Identity FQDN or on Operator Identifier FQDN of the 5G ProSe Layer-3 UE-to-Network Relay node selection information. + +To assist the 5G ProSe Layer-3 Remote UE with N3IWF selection, the 5G ProSe Layer-3 UE-to-Network Relay supporting N3IWF access advertises the 5GS TAI corresponding to the serving cell, as defined in clause 5.8.3.2, in the 5G ProSe UE-to-Network Relay Discovery procedure as defined in clause 6.3.2.3. + +A 5G ProSe Layer-3 Remote UE constructs the FQDN using either Tracking Area Identity FQDN or on Operator Identifier FQDN and selects the N3IWF using the procedures of N3IWF selection in clause 6.3.6.2 of TS 23.501 [4]. + +When the 5G ProSe Layer-3 Remote UE relays traffic over 5G ProSe Layer-3 UE-to-Network Relay using N3IWF for emergency services, the 5G ProSe Layer-3 Remote UE selects the N3IWF using the N3IWF selection procedure that is specified in clause 6.3.6.4.2 of TS 23.501 [4]. + +#### 6.5.1.2.3 Mobility of 5G ProSe Layer-3 Remote UE between Direct and Indirect Network communication path + +When 5G ProSe Layer-3 Remote UE changes from Direct Network Communication to Indirect Network Communication path, TS 23.502 [5] clause 4.9.2.2 applies after the 5G ProSe Layer-3 Remote UE establishes PC5 connection to the 5G Layer-3 UE-to-Network Relay. + +When 5G ProSe Layer-3 Remote UE changes from Indirect Network Communication path to Direct Network Communication, the 5G ProSe Layer-3 Remote UE follows TS 23.502 [5] clause 4.9.2.1. + +#### 6.5.1.3 Additional parameters announcement procedure + +Additional parameters announcement procedure outlined in figure 6.5.1.3-1 is used by a 5G ProSe Remote UE to request a 5G ProSe UE-to-Network Relay to announce additional parameters (using Model A) as defined in clause 5.8.3. + +![Sequence diagram for Additional parameters announcement procedure involving 5G ProSe Remote UE, 5G ProSe UE-to-Network Relay, Network, and Application.](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +``` + +sequenceDiagram + participant RemoteUE as 5G ProSe Remote UE + participant Relay as 5G ProSe UE-to-Network Relay + participant Network as Network + participant Application as Application + + Note over RemoteUE, Application: 1. 5G ProSe Remote UE has discovered a Relay, and requires additional parameters. + RemoteUE->>Relay: 2. Additional Parameters Announcement Request () + Relay-->>RemoteUE: 3. Additional Parametrs Announcement Response (Additional_Parameters_Announcement_Request_Refresh Timer) + Relay-->>RemoteUE: 4. Relay Discovery Additional Information + Note over Relay: 5. The 5G ProSe UE-to-Network Relay detects new parameter(s). + Relay-->>RemoteUE: 6. Relay Discovery Additional Information + +``` + +The diagram shows a sequence of interactions between four entities: 5G ProSe Remote UE, 5G ProSe UE-to-Network Relay, Network, and Application. + Step 1: A box spanning all entities indicates the Remote UE has discovered a Relay and needs parameters. + Step 2: An arrow from Remote UE to Relay for 'Additional Parameters Announcement Request ()'. + Step 3: A dashed arrow from Relay to Remote UE for 'Additional Parametrs Announcement Response' containing a refresh timer. + Step 4: A dashed arrow from Relay to Remote UE for 'Relay Discovery Additional Information'. + Step 5: A box over the Relay lifeline indicates it detects new parameters. + Step 6: A dashed arrow from Relay to Remote UE for 'Relay Discovery Additional Information'. + +Sequence diagram for Additional parameters announcement procedure involving 5G ProSe Remote UE, 5G ProSe UE-to-Network Relay, Network, and Application. + +**Figure 6.5.1.3-1: Additional parameters announcement procedure** + +1. 5G ProSe Remote UE has discovered a 5G ProSe UE-to-Network Relay and requires additional parameters. + 2. The 5G ProSe Remote UE sends to the 5G ProSe UE-to-Network Relay an Additional Parameters Announcement Request to obtain additional parameters. + 3. The 5G ProSe UE-to-Network Relay acknowledges receipt of the request in step 2 with an Additional Parameters Announcement Response (Additional\_Parameters\_Announcement\_Request\_Refresh Timer). The Additional\_Parameters\_Announcement\_Request\_Refresh Timer (configurable in the 5G ProSe UE-to-Network Relay), is provided to the 5G ProSe Remote UE so that when this timer expires the 5G ProSe Remote UE repeats the Additional Parameters Announcement Request procedure if it still needs to obtain the additional parameters. If the 5G ProSe Remote UE does not initiate new Additional Parameters Announcement Request procedure when this Additional\_Parameters\_Announcement\_Request\_Refresh Timer expires and no other UE request additional parameters announcement before the Additional\_Parameters\_Announcement\_Request\_Refresh timer expires in the 5G ProSe UE-to-Network Relay, then the relay shall stop announcing the additional parameters. + 4. The 5G ProSe UE-to-Network Relay announces the additional parameters by sending Relay Discovery Additional Information message as defined in clause 5.8.3. This is repeated periodically with a configurable frequency (normally higher than the one related to the Additional\_Parameters\_Announcement\_Request\_Refresh Timer) until there is no UE requesting to announce the additional parameters as determined by the Additional\_Parameters\_Announcement\_Request\_Refresh Timer running in the 5G ProSe UE-to-Network Relay. +- NOTE: Based on UE implementation, the 5G ProSe UE-to-Network Relay can send the Relay Discovery Additional Information message several times consecutively in step 4 if there are other 5G ProSe Remote UE(s) that have connected to the 5G ProSe UE-to-Network Relay but not yet requested any additional parameters. This ensures the other 5G ProSe Remote UE(s) obtain such additional parameters without invoking any new request(s). +5. The 5G ProSe UE-to-Network Relay detects new or updated additional parameters. + 6. Detection of new or updated additional parameters in step 5 triggers the 5G ProSe UE-to-Network Relay to announce the additional parameters by sending a Relay Discovery Additional Information Message immediately and to repeat it periodically with a configurable frequency as in step 4 until there are no UEs requesting to announce the additional parameters, i.e. until the Additional\_Parameters\_Announcement\_Request\_Refresh Timer expires in the 5G ProSe UE-to-Network Relay. + +## 6.5.2 5G ProSe Communication via 5G ProSe Layer-2 UE-to-Network Relay + +### 6.5.2.1 Registration and Connection Management + +#### 6.5.2.1.1 Registration Management + +Registration Management for the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay follows the principles and procedures defined in TS 23.501 [4] and TS 23.502 [5]. The 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay may be served by the same AMF or different AMFs. + +#### 6.5.2.1.2 Connection Management + +Connection Management for the 5G ProSe Layer-2 Remote UE and the 5G ProSe Layer-2 UE-to-Network Relay follows the principles and procedures defined in TS 23.501 [4] and TS 23.502 [5] with the following modifications. + +The 5G ProSe Layer-2 UE-to-Network Relay may only relay data/signalling for the 5G ProSe Layer-2 Remote UE(s) when the 5G ProSe Layer-2 UE-to-Network Relay is in CM-CONNECTED state. If the 5G ProSe Layer-2 UE-to-Network Relay is in CM\_IDLE state and receives a connection request from the 5G ProSe Layer-2 Remote UE for relaying, the 5G ProSe Layer-2 UE-to-Network Relay shall trigger Service Request procedure to enter CM\_CONNECTED state before relaying the 5G ProSe Layer-2 Remote UEs traffic. If the 5G ProSe Layer-2 UE-to-Network Relay in RRC\_IDLE receives a connection request from the 5G ProSe Layer-2 Remote UE using emergency RSC, then 5G ProSe Layer-2 UE-to-Network Relay sets the establishment cause to "emergency". + +The state of 5G ProSe UE-to-Network Relay is controlled by NG-RAN with the following: + +- If any 5G ProSe Layer-2 Remote UE connected to the 5G ProSe Layer-2 UE-to-Network Relay is in CM-CONNECTED with RRC Connected state, the 5G ProSe Layer-2 UE-to-Network Relay shall remain CM-CONNECTED state with RRC Connected state unless the network needs to release the connection. +- If all 5G ProSe Layer-2 Remote UEs connected to the 5G ProSe Layer-2 UE-to-Network Relay enter CM-IDLE or CM-CONNECTED with RRC Inactive state, the 5G ProSe Layer-2 UE-to-Network Relay may enter CM-IDLE state or CM-CONNECTED with RRC Inactive state, or may remain CM-CONNECTED with RRC Connected state. + +When 5G ProSe Layer-2 Remote UE is in CM-CONNECTED state, the 5G ProSe Layer-2 UE-to-Network Relay and 5G ProSe Layer-2 Remote UE keep the PC5 link. When the 5G ProSe Remote UE is in CM-IDLE state, it may either release the PC5 link for relaying or not. + +For paging a 5G ProSe Layer-2 Remote UE, it follows the principles and procedures defined in TS 23.501 [4] and TS 23.502 [5] and the paging message delivery from NG-RAN to 5G ProSe Layer-2 Remote UE is specified in TS 38.300 [12]. + +## 6.5.2.2 Connection establishment + +![Sequence diagram illustrating the Connection Establishment for 5G ProSe Layer-2 UE-to-Network Relay. The diagram shows interactions between Remote UE, ProSe UE-to-Network Relay, NG-RAN, ProSe UE-to-Network Relay's AMF, Remote UE's AMF, PCF, Remote UE's SMF, and Remote UE's UPF. The steps are: 0. Initial Registration (dashed box), 1. Service Authorization retrieval, 2. UE-to-Network Relay discovery and selection, 3. PC5 connection establishment, 4. AS connection setup, 5. UE-to-Network Relay triggered Service Request (dashed box), 6. NAS connection setup (dashed box), 7. PDU Session Establishment procedure (dashed box), and 8. data transfer (indicated by a double-headed arrow at the bottom).](54159e6d8f5ecc73ad262758e3a60677_img.jpg) + +Sequence diagram illustrating the Connection Establishment for 5G ProSe Layer-2 UE-to-Network Relay. The diagram shows interactions between Remote UE, ProSe UE-to-Network Relay, NG-RAN, ProSe UE-to-Network Relay's AMF, Remote UE's AMF, PCF, Remote UE's SMF, and Remote UE's UPF. The steps are: 0. Initial Registration (dashed box), 1. Service Authorization retrieval, 2. UE-to-Network Relay discovery and selection, 3. PC5 connection establishment, 4. AS connection setup, 5. UE-to-Network Relay triggered Service Request (dashed box), 6. NAS connection setup (dashed box), 7. PDU Session Establishment procedure (dashed box), and 8. data transfer (indicated by a double-headed arrow at the bottom). + +**Figure 6.5.2.2-1: Connection Establishment for 5G ProSe Layer-2 UE-to-Network Relay** + +0. If in coverage, the 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay may independently perform the initial registration to the network according to registration procedures in TS 23.502 [5]. +1. If in coverage, the 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay independently get the service authorization for 5G ProSe Layer-2 UE-to-Network Relay operation from the network. Service authorization and parameters provisioning for 5G ProSe Layer-2 UE-to-Network Relay operation are performed for the 5G ProSe Layer-2 UE-to-Network Relay and 5G ProSe Layer-2 Remote UE as specified in clause 5.1.4. + +If the 5G ProSe Layer-2 Remote UE is "not served by NG-RAN", the pre-configured parameters are used and the service authorization and parameters may be updated after step 6. + +If the 5G ProSe Layer-2 Remote UE has not performed Initial Registration, the 5G ProSe Layer-2 Remote UE may perform the Initial Registration in step 6. + +2. The 5G ProSe Layer-2 Remote UE and 5G ProSe Layer-2 UE-to-Network Relay perform 5G ProSe UE-to-Network Relay Discovery and selection, as specified in clause 6.3.2.3. +3. The 5G ProSe Layer-2 Remote UE initiates a one-to-one communication connection with the selected 5G ProSe Layer-2 UE-to-Network Relay over PC5 using the procedure as described in clause 6.4.3. +4. The 5G ProSe Layer-2 Remote UE establishes an RRC Connection with the same NG-RAN serving the selected 5G ProSe Layer-2 UE-to-Network Relay, specified in TS 38.300 [12]. The 5G ProSe Layer-2 Remote UE sets the RRC Establishment Cause as defined in TS 38.331 [16]. +5. During step 4, if the 5G ProSe Layer-2 UE-to-Network Relay is in CM\_IDLE state and receives a trigger from the AS layer to enter CM\_CONNECTED state due to Remote UE's AS layer connection set up with the NG-RAN, the 5G ProSe Layer-2 UE-to-Network Relay performs Service Request procedure in the clause 4.2.3.2 of TS 23.502 [5]. +6. The 5G ProSe Layer-2 Remote UE sends a NAS message to the serving AMF. The NAS message is encapsulated in an Uu RRC message that is sent over PC5 to the 5G ProSe Layer-2 UE-to-Network Relay and the 5G ProSe Layer-2 UE-to-Network Relay forwards the Uu RRC message to the NG-RAN specified in + +TS 38.300 [12]. NG-RAN selects the 5G ProSe Layer-2 Remote UE's serving AMF and forwards the NAS message to this AMF. + +If 5G ProSe Layer-2 Remote UE has not performed the initial registration, the NAS message is an initial Registration message. Otherwise, the NAS message is either a service request message, or a mobility or periodic Registration message taking into account the TAI in the RRC container received from the 5G ProSe Layer-2 UE-to-Network Relay during Relay Discovery (see clause 5.8.3.3) or PC5-RRC message, as specified in TS 38.300 [12]. + +7. The 5G ProSe Layer-2 Remote UE may trigger the PDU Session Establishment procedure as defined in clause 4.3.2.2 of TS 23.502 [5]. +8. The data is transferred between the 5G ProSe Layer-2 Remote UE and UPF via the 5G ProSe Layer-2 UE-to-Network Relay and NG-RAN. The 5G ProSe Layer-2 UE-to-Network Relay forwards all the data messages between the 5G ProSe Layer-2 Remote UE and NG-RAN, as specified in TS 38.300 [12]. + +### 6.5.2.3 Path switching between direct network communication path and indirect network communication path via 5G ProSe Layer-2 UE-to-Network Relay + +Xn based (as defined in clause 4.9.1.2 of TS 23.502 [5]) and N2 based (as defined in clause 4.9.1.3 of TS 23.502 [5]) Handover procedure is used for inter-gNB indirect-to-direct and inter-gNB direct-to-indirect path switching for 5G ProSe Layer-2 Remote UE in CM-CONNECTED with RRC\_CONNECTED state. + +**Editor's note:** Mobility of 5G ProSe Layer-2 Remote UE between Direct and Indirect Network communication path will be defined by RAN WGs and alignment work (if any) will be made by SA2 based on RAN WGs conclusions. + +### 6.5.3 5G ProSe UE-to-Network Relay reselection + +After being connected to the 5G ProSe UE-to-Network Relay, the 5G ProSe Remote UE keeps performing the measurement of the signal strength of PC5 unicast link with the 5G ProSe UE-to-Network Relay for relay reselection. + +The 5G ProSe UE-to-Network Relay discovery procedures defined in clause 6.3.2.3 are used to discover available 5G ProSe UE-to-Network Relays for 5G ProSe UE-to-Network Relay reselection. + +### 6.5.4 5G ProSe Remote UE traffic handling for 5G ProSe UE-to-Network Relay support + +For the 5G ProSe Remote UE to access the service via 5G ProSe UE-to-Network Relay, the following apply: + +- The application traffic on the 5G ProSe Remote UE is managed by URSP rules (with consideration of local configurations), following the procedure defined in clauses 6.1.2.2.1 and 6.6.2.3 of TS 23.503 [9]. The URSP rules defined in clause 6.6.2.1 of TS 23.503 [9] applies for the 5G ProSe Remote UE, with RSD enhanced to include: + - a "ProSe Layer-3 UE-to-Network Relay Offload indication"; or + - a "ProSe Multi-path Preference". +- If an application or application traffic matches a URSP rule, corresponding RSDs shall be used to evaluate the existing PDU sessions, or establish a new PDU session, or determine to offload outside of a PDU session, or multi-path communication via 5G ProSe Layer-3 UE-to-Network Relay outside of a PDU session and a PDU Session over Uu reference point. +- If the selected RSD contains "ProSe Layer-3 UE-to-Network Relay Offload indication": + - The 5G ProSe Remote UE will route the traffic to the 5G ProSe Layer-3 UE-to-Network Relay connection without establishing a PDU session, when such connection is available. + +This may trigger the 5G ProSe Remote UE to start 5G ProSe UE-to-Network Relay discovery if it is not yet started. The discovery and establishment of the connection with the 5G ProSe Layer-3 UE-to-Network Relay is controlled by the ProSe Policy (pre-) configured on the 5G ProSe Remote UE. + +- If the matched URSP rule contains both a RSD with "Non-Seamless Offload indication" and a RSD with "ProSe Layer-3 UE-to-Network Relay Offload indication", whether to offload the traffic to non-3GPP access or the 5G ProSe Layer-3 UE-to-Network Relay connection depends on the priority of the RSDs and the availability of the connections, as specified in the clause 6.6.2.3 of TS 23.503 [9]. +- If the selected RSD does not contain the "ProSe Layer-3 UE-to-Network Relay Offload indication" or, "Non-Seamless Offload indication", the 5G ProSe Remote UE shall use a PDU session to route the corresponding application traffic. + +If configured in the ProSe Policy, the 5G ProSe Remote UE may attempt the discovery of a Relay Service Code corresponding to a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support in the discovery procedure, when the non-3GPP access type is preferred in the selected RSD. The 5G ProSe Remote UE may attempt the discovery of a Relay Service Code corresponding to a 5G ProSe Layer-2 UE-to-Network Relay in the discovery procedure, when the 3GPP access type is preferred in the selected RSD. + +- If the selected RSD contains "ProSe Multi-path Preference": + - The 5G ProSe Remote UE is preferred to route the traffic over a PC5 connection with a 5G ProSe Layer-3 UE-to-Network Relay and a PDU Session matched to other components (e.g., Network Slice Selection) in the selected RSD. If either connection is not available then the traffic may be routed via a PC5 connection with a 5G ProSe Layer-3 UE-to-Network Relay or a PDU Session matched to other components. + - If the PC5 connection with 5G ProSe Layer-3 UE-to-Network Relay associated with the desired RSC is not available, this may trigger the 5G ProSe Remote UE to start 5G ProSe UE-to-Network Relay discovery and connection establishment, controlled by the ProSe Policy configured on the 5G ProSe Remote UE. If the PC5 connection with 5G ProSe Layer-3 UE-to-Network Relay associated with the desired RSC is available, this may trigger Layer-2 link modification to associate the corresponding ProSe service into the PC5 connection. Determination on the desired RSC is based on the Policy/Parameters specified in clause 5.1.4.1. + - If the PDU Session matched to other components in the selected RSD is not available, this may trigger the establishment of a new PDU Session over Uu reference point using the values specified by the selected RSD. +- If the 5G ProSe Remote UE has an indirect connection via a 5G ProSe Layer-2 UE-to-Network Relay connection available, it will be treated as the "3GPP" access type. If the 5G ProSe Remote UE has an indirect connection via a 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support available, it will be treated as the "non-3GPP" access type. The URSP handling as defined in TS 23.503 [9] applies. + +For the 5G ProSe Layer-3 UE-to-Network Relay and 5G ProSe Layer-2 UE-to-Network Relay, the URSP handling does not apply to the relayed traffic from the 5G ProSe Remote UE. + +For the 5G ProSe Layer-3 UE-to-Network Relay, the PDU session established for relaying the 5G ProSe Remote UE's traffic is controlled by the ProSe Policy. + +## 6.5.5 Procedures for Communication Path Switching between Two UE-to-Network Relays + +### 6.5.5.1 General + +The communication path switching between two UE-to-Network Relays includes the following scenarios: + +- Layer-3 UE-to-Network Relay with N3IWF switching from/to Layer-3 UE-to-Network Relay with N3IWF. +- Layer-3 UE-to-Network Relay without N3IWF switching from/to Layer-3 UE-to-Network Relay without N3IWF. +- Layer-3 UE-to-Network Relay without N3IWF switching from/to Layer-3 UE-to-Network Relay with N3IWF. +- Layer-2 UE-to-Network Relay switching from/to Layer-2 UE-to-Network Relay. +- Layer-2 UE-to-Network Relay switching from/to Layer-3 UE-to-Network Relay without N3IWF. +- Layer-2 UE-to-Network Relay switching from/to Layer-3 UE-to-Network Relay with N3IWF. + +### 6.5.5.2 Procedures for Communication Path Switching between UE-to-Network Relays + +This clause specifies the communication path switching procedures between two UE-to-Network Relays. + +When performing the path switching between two 5G ProSe Layer-3 UE-to-Network Relay without N3IWF, or between 5G ProSe Layer-3 UE-to-Network Relay without N3IWF and 5G ProSe Layer-2 UE-to-Network Relay, or between 5G ProSe Layer-3 UE-to-Network Relay without N3IWF and 5G ProSe Layer-3 UE-to-Network Relay with N3IWF, the application layer procedures are used for service continuity support which is out of scope of this specification. + +Path switching between two 5G ProSe Layer-3 UE-to-Network Relay with N3IWF is performed using the mechanism specified for Local mobility anchor within untrusted non-3GPP access networks using MOBIKE in clause 6.2.9 of TS 23.501 [4]. + +When a 5G ProSe-enabled UE as a 5G ProSe Layer-2 Remote UE in CM-CONNECTED state switches the communication path to Layer-3 UE-to-Network Relay with N3IWF, 5G ProSe-enabled UE's PDU session(s) can handover to the indirect path via Layer-3 UE-to-Network Relay with N3IWF by reusing the procedures specified in clause 4.9.2 of TS 23.502 [5]. + +When a 5G ProSe-enabled UE as a 5G ProSe Layer-3 Remote UE switches the communication path from Layer-3 UE-to-Network Relay with N3IWF to an indirect path via Layer-2 UE-to-Network Relay, 5G ProSe-enabled UE's PDU session(s) can handover to the indirect path via Layer-2 UE-to-Network Relay by reusing the procedures specified in clause 4.9.2 of TS 23.502 [5]. + +Procedure on Path switching between two 5G ProSe Layer-2 UE-to-Network Relays is specified in TS 38.300 [12]. + +## 6.6 Procedures for Service Authorization to NG-RAN + +### 6.6.1 General + +In order to support PC5 radio resource control in NG-RAN, ProSe service Authorisation information and PC5 QoS parameters for ProSe need to be made available in NG-RAN. This clause describes the corresponding procedures and aspects. + +### 6.6.2 Registration procedure + +The Registration procedure for UE is performed as defined in TS 23.502 [5] clause 4.2.2.2 with the following additions: + +- The UE includes the 5G ProSe Capability as part of the "5GMM capability" in the Registration Request message. The AMF stores the 5G ProSe Capability for 5G ProSe operation. +- The 5G ProSe Capability indicates whether the UE supports one or more of the following ProSe capabilities: + - 5G ProSe Direct Discovery; + - 5G ProSe Direct Communication; + - 5G ProSe Layer-2 UE-to-Network Relay; + - 5G ProSe Layer-3 UE-to-Network Relay; + - 5G ProSe Layer-2 Remote UE; + - 5G ProSe Layer-3 Remote UE; + - 5G ProSe Layer-2 UE-to-UE Relay; + - 5G ProSe Layer-3 UE-to-UE Relay; + - 5G ProSe Layer-2 End UE; and + - 5G ProSe Layer-3 End UE. + +- The AMF obtains the 5G ProSe subscription data as part of the user subscription data from UDM during UE Registration procedure using Nudm\_SDM service as defined in clause 4.2.2.2.2 of TS 23.502 [5]. +- The AMF determines whether the UE is authorised to use 5G ProSe services based on UE's 5G ProSe Capability and the ProSe Service Authorisation included in the subscription data received from UDM as specified in clause 5.7. ProSe NR UE-PC5-AMBR is also provided to the AMF as part of the subscription data for 5G ProSe services. The AMF stores the authorized 5G ProSe Capability. +- The AMF sends the authorized 5G ProSe Capability for 5G ProSe operation to PCF. Based on the received 5G ProSe Capability from the AMF, the PCF provides the PC5 QoS parameters for 5G ProSe to AMF. The AMF stores such information as part of the UE context. +- If the UE is authorised to use 5G ProSe services, then the AMF shall include in a NGAP message sent to NG-RAN: + - "5G ProSe authorised" information, including one or more of the following: + - whether the UE is authorized to use 5G ProSe Direct Discovery; + - whether the UE is authorized to use 5G ProSe Direct Communication; + - whether the UE is authorized to act as a 5G ProSe Layer-2 UE-to-Network Relay; + - whether the UE is authorized to act as a 5G ProSe Layer-3 UE-to-Network Relay; + - whether the UE is authorized to act as a 5G ProSe Layer-2 Remote UE; + - whether the UE is authorized to use multi-path communication via direct Uu path and via 5G ProSe Layer-2 UE-to-Network Relay as a 5G ProSe Layer-2 Remote UE; + - whether the UE is authorized to act as a 5G ProSe Layer-2 UE-to-UE Relay; + - whether the UE is authorized to act as a 5G ProSe Layer-2 End UE. + +NOTE: The authorization for "5G ProSe Direct discovery" and "5G ProSe Direct communication" can be used for 5G ProSe Layer-3 UE-to-UE Relay and 5G ProSe Layer-3 End UE. + +- ProSe NR UE-PC5-AMBR, used by NG-RAN for the resource management of UE's PC5 transmission for 5G ProSe services in network scheduled mode. +- the PC5 QoS parameters for 5G ProSe used by the NG-RAN for the resource management of UE's PC5 transmission for ProSe services in network scheduled mode. +- If the UE is authorised to use 5G ProSe services, then the AMF should not initiate the release of the signalling connection after the completion of the Registration procedure. The release of the signalling connection relies on the decision of NG-RAN, as specified in TS 23.502 [5]. + +### 6.6.3 Service Request procedure + +The Service Request procedures for UE in CM-IDLE state are performed as defined in TS 23.502 [5] clause 4.2.3.2 and clause 4.2.3.3 with the following additions: + +- If the UE is authorised to use ProSe services, then the AMF shall include "ProSe authorised" information in the NGAP message, indicating which of the ProSe services the UE is authorised to use as described in clause 6.6.2. +- The AMF includes the ProSe NR UE-PC5-AMBR in the NGAP message to the NG-RAN as part of the UE context and NG-RAN may use in resource management of UE's PC5 transmission for ProSe services in network scheduled mode. +- The AMF sends the PC5 QoS parameters for ProSe to NG-RAN via N2 signalling. The PC5 QoS parameters for ProSe may be stored in the UE context after the registration procedure. If the UE is authorised to use ProSe services but AMF does not have PC5 QoS parameters for ProSe available, the AMF fetches the PC5 QoS parameters for ProSe from the PCF. + +## 6.6.4 N2 Handover procedure + +The N2 based handover procedures for UE are performed as defined in TS 23.502 [5] clause 4.9.1.3 with the following additions: + +- If the UE is authorised to use ProSe services, then the target AMF shall send the "ProSe authorised" information, ProSe NR UE-PC5-AMBR and PC5 QoS parameters for ProSe to the target NG-RAN in the NGAP Handover Request message. + +## 6.6.5 Xn Handover procedure + +The Xn based handover procedures for UE are performed as defined in TS 23.502 [5] clause 4.9.1.2 with the following additions: + +- If the "ProSe authorised" information is included in the UE context, then the source NG-RAN shall include a "ProSe authorised" information, ProSe NR UE-PC5-AMBR and PC5 QoS parameters for ProSe in the XnAP Handover Request message to the target NG-RAN. +- If the "ProSe authorised" information is included in the UE context, then the AMF shall send the "ProSe authorised" information, the ProSe NR UE-PC5-AMBR and PC5 QoS parameters for ProSe to the target NG-RAN in the Path Switch Request Acknowledge message. + +## 6.6.6 Subscriber Data Update Notification to AMF + +The procedure of Subscriber Data Update Notification to AMF is performed as defined in TS 23.502 [5] clause 4.5.1 with the following additions: + +- The Nudm\_SDM\_Notification service operation may contain the ProSe Service Authorisation or the ProSe NR UE-PC5-AMBR or any combination. +- The AMF updates the UE Context with the above new ProSe subscription data. +- When the AMF updates UE context stored at NG-RAN, the UE context contains the ProSe subscription data. + +## 6.6.7 Delivery of PC5 QoS parameters for ProSe to NG-RAN + +The UE Policy Association Establishment procedure and UE Policy Association Modification procedure, as defined in TS 23.502 [5], is used to provide the AMF with PC5 QoS parameters used by NG-RAN. When receiving the 5G ProSe Capability in Npcf\_UEPolicyControl\_Create Request from the AMF or when receiving the updated subscription data from UDR, the PCF generates the PC5 QoS parameters used by NG-RAN corresponding to a UE as defined in clause 5.4.2 of TS 23.287 [2]. + +The (V-)PCF provides the information to the AMF as follows: + +- In the roaming case, the H-PCF includes the PC5 QoS parameters used by NG-RAN in the Npcf\_UEPolicyControl\_Create Response message or Npcf\_UEPolicyControl\_UpdateNotify Request message sent to V-PCF in an N2 PC5 policy container and V-PCF relays this N2 PC5 policy container as the N2 container in the Namf\_Communication\_N1N2MessageTransfer message sent to AMF. +- In the non-roaming case, the PCF includes the PC5 QoS parameters used by NG-RAN in an N2 container in Namf\_Communication\_N1N2MessageTransfer message sent to AMF. + +When the AMF receives the N2 PC5 policy container from (V-)PCF, the AMF stores such information as part of the UE context. + +In the UE Configuration Update procedure triggered by UE Policy Association Establishment or UE Policy Association Modification: + +- The AMF forwards the PC5 QoS parameters in the NGAP message to the NG-RAN if a N2 PC5 policy container is received in the Namf\_Communication\_N1N2MessageTransfer message. + +NOTE 1: If the PC5 QoS parameters are provided to both NG-RAN and UE, both the N2 PC5 Policy Container and the UE Policy Container are included in the Namf\_Communication\_N1N2MessageTransfer message. + +NOTE 2: Non-UE specific PC5 QoS parameters, e.g. default PC5 QoS parameters, can also be locally configured in NG-RAN. How such configuration is performed is out of scope of this specification. + +## 6.7 5G ProSe UE-to-UE Relay Communication + +### 6.7.1 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay + +#### 6.7.1.1 Layer-2 link establishment for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay + +Figure 6.7.1.1-1 shows the procedure for Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay. + +![Sequence diagram illustrating the Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay. The diagram shows three main entities: source 5G ProSe Layer-3 End UE, 5G ProSe Layer-3 UE-to-UE Relay, and target 5G ProSe Layer-3 End UE. The process involves authorization, discovery, direct communication requests, security establishment, IP address allocation, DNS queries, and finally relayed traffic.](4a9454b4354535e1b61423084da1424b_img.jpg) + +``` +sequenceDiagram + participant Source as source 5G ProSe Layer-3 End UE + participant Relay as 5G ProSe Layer-3 UE-to-UE Relay + participant Target as target 5G ProSe Layer-3 End UE + + Note over Source: 1. Authorization and provisioning. + Note over Relay: 1. Authorization and provisioning. + Note over Target: 1. Authorization and provisioning. + + Source->>Target: 2. Discovery procedure + Note over Source: 3. Direct Communication Request (Unicast) + Source->>Relay: 4. Security Establishment + Relay->>Target: 5. Direct Communication Request (Unicast) + Relay->>Target: 6. Security Establishment + Relay->>Target: 7. Direct Communication Accept (Unicast) + Note over Target: 8. IP address/prefix allocation + Target->>Source: 9. Direct Communication Accept (Unicast) + Note over Source: 10. IP address/prefix allocation + Note over Source: 11a. DNS query (User Info ID of Target UE) + Source-->>Relay: 11b. DNS response (IP addr of Target UE) + Note over Source: 12. Relayed traffic + Source->>Target: 12. Relayed traffic +``` + +Sequence diagram illustrating the Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay. The diagram shows three main entities: source 5G ProSe Layer-3 End UE, 5G ProSe Layer-3 UE-to-UE Relay, and target 5G ProSe Layer-3 End UE. The process involves authorization, discovery, direct communication requests, security establishment, IP address allocation, DNS queries, and finally relayed traffic. + +Figure 6.7.1.1-1: Layer-2 link establishment via 5G ProSe Layer-3 UE-to-UE Relay + +1. Service authorization and provisioning are performed for source 5G ProSe Layer-3 End UE, target 5G ProSe Layer-3 End UE and 5G ProSe Layer-3 UE-to-UE Relay as described in clause 6.2. + +2. The source 5G ProSe Layer-3 End UE performs discovery of a 5G ProSe Layer-3 UE-to-UE Relay as described in clause 6.3.2.4. +3. The source 5G ProSe Layer-3 End UE sends a Direct Communication Request message to initiate the unicast Layer-2 link establishment procedure with the 5G ProSe Layer-3 UE-to-UE Relay. The parameters included in the Direct Communication Request message are described in clause 6.4.3.7. + +The Source Layer-2 ID of the Direct Communication Request message is self-assigned by the source 5G ProSe Layer-3 End UE and the Destination Layer-2 ID is set to the Source Layer-2 ID of the discovery message of the 5G ProSe Layer-3 UE-to-UE Relay. + +The source 5G ProSe Layer-3 End UE gets application information and optional ProSe Application Requirements from ProSe application layer, and determines the end-to-end QoS parameters as described in clause 5.6.3.1. + +4. If the User Info ID of 5G ProSe Layer-3 UE-to-UE Relay in the Direct Communication Request message matches the 5G ProSe UE-to-UE Relay's User Info ID and the RSC in the Direct Communication Request matches one RSC that the relay is (pre)configured with, as specified in clause 5.1.5.1, the 5G ProSe Layer-3 UE-to-UE Relay responds by establishing the security with the source 5G ProSe Layer-3 End UE. When the security protection is enabled, the source 5G ProSe Layer-3 End UE sends the parameters as described in clause 6.4.3.7 to the 5G ProSe Layer-3 UE-to-UE Relay. + +If the Ethernet MAC address of source 5G ProSe Layer-3 End UE is already used by another 5G ProSe Layer-3 End UE, then the 5G ProSe Layer-3 UE-to-UE Relay rejects the direct link establishment indicating that the MAC address is not unique. + +The Source Layer-2 ID used for the security establishment procedure is self-assigned by the 5G ProSe Layer-3 UE-to-UE Relay and the Destination Layer-2 ID is set to the Source Layer-2 ID of the received Direct Communication Request message. + +The 5G ProSe Layer-3 UE-to-UE Relay shall choose different Source Layer-2 IDs for PC5 links of different types of traffic, i.e., IP traffic, Ethernet traffic and Unstructured traffic. + +If the PC5 link is used for transferring Unstructured traffic, the 5G ProSe Layer-3 UE-to-UE Relay shall choose different Source Layer-2 IDs for different pair of source and target 5G ProSe Layer-3 End UEs. + +Upon receiving the security establishment procedure messages, the source 5G ProSe Layer-3 End UE obtains the 5G ProSe Layer-3 UE-to-UE Relay's Layer-2 ID for future communication, for signalling and data traffic for this unicast link. + +5. After the Security Establishment procedure in step 4 is completed, the 5G ProSe Layer-3 UE-to-UE Relay sends a Direct Communication Request message to initiate the unicast Layer-2 link establishment procedure with the target 5G ProSe Layer-3 End UE. The parameters included in the Direct Communication Request message are described in clause 6.4.3.7. + +The Source Layer-2 ID of the Direct Communication Request message is self-assigned by the 5G ProSe Layer-3 UE-to-UE Relay and the Destination Layer-2 ID is the unicast Layer-2 ID of target 5G ProSe Layer-3 End UE associated with the User Info ID of target 5G ProSe Layer-3 End UE. + +The 5G ProSe Layer-3 UE-to-UE Relay shall choose different Source Layer-2 IDs for PC5 links of different types of traffic, i.e., IP traffic, Ethernet traffic and Unstructured traffic. + +If the PC5 link is used for transferring Unstructured traffic, the 5G ProSe Layer-3 UE-to-UE Relay shall choose different Source Layer-2 IDs for different pair of source and target 5G ProSe Layer-3 End UEs. + +6. If the User Info ID of target 5G ProSe Layer-3 End UE and RSC included in the Direct Communication Request match the target UE's User Info ID and the RSC that the target UE is (pre)configured with as specified in clause 5.1.5.1, the target 5G ProSe Layer-3 End UE responds by establishing the security with the 5G ProSe Layer-3 UE-to-UE Relay. When the security protection is enabled, the 5G ProSe Layer-3 UE-to-UE Relay sends the parameters as described in clause 6.4.3.7 to the target 5G ProSe Layer-3 End UE. + +The Source Layer-2 ID used for the security establishment procedure is self-assigned by the target 5G ProSe Layer-3 End UE and the Destination Layer-2 ID is set to the Source Layer-2 ID of the received Direct Communication Request message. + +Upon receiving the security establishment procedure messages, the 5G ProSe Layer-3 UE-to-UE Relay obtains the target 5G ProSe Layer-3 End UE's Layer-2 ID for future communication, for signalling and data traffic for this unicast link. + +7. The target 5G ProSe Layer-3 End UE sends a Direct Communication Accept message to the 5G ProSe Layer-3 UE-to-UE Relay that has successfully established security with. The parameters included in the Direct Communication Accept message are described in clause 6.4.3.7. + +NOTE: The 5G ProSe Layer-3 UE-to-UE Relay can detect that the Ethernet MAC address of target 5G ProSe Layer-3 End UE is already used by another 5G ProSe Layer-3 End UE when it receives the Direct Communication Accept message. + +8. For IP traffic, IPv6 prefix or IPv4 address is allocated for the target 5G ProSe Layer-3 End UE as defined in clause 5.5.1.4. +9. After receiving the Direct Communication Accept message from the target 5G ProSe Layer-3 End UE, the 5G ProSe Layer-3 UE-to-UE Relay sends a Direct Communication Accept message to the source 5G ProSe Layer-3 End UE that has successfully established security with. The parameters included in the Direct Communication Accept message are described in clause 6.4.3.7. +10. For IP traffic, IPv6 prefix or IPv4 address is allocated for the source 5G ProSe Layer-3 End UE as defined in clause 5.5.1.4. +11. For IP communication, the 5G ProSe Layer-3 UE-to-UE Relay may store an association of User Info ID and the IP address of target 5G ProSe Layer-3 End UE into its DNS entries and the 5G ProSe Layer-3 UE-to-UE Relay may act as a DNS server to other UEs. The source 5G ProSe Layer-3 End UE may send a DNS query to the 5G ProSe Layer-3 UE-to-UE Relay to request IP address of target 5G ProSe Layer-3 End UE after step 10 if the IP address of target 5G ProSe Layer-3 End UE is not received in step 9 and the 5G ProSe Layer-3 UE-to-UE Relay returns the IP address of the target 5G ProSe Layer-3 End UE to the source 5G ProSe Layer-3 End UE. + +For Ethernet communication, the 5G ProSe Layer-3 UE-to-UE Relay maintains the association between PC5 links and Ethernet MAC addresses received from the 5G ProSe Layer-3 End UE. + +For Unstructured traffic communication, for each pair of source and target 5G ProSe Layer-3 End UEs, the 5G ProSe Layer-3 UE-to-UE Relay maintains the 1:1 mapping between the PC5 link with source 5G ProSe Layer-3 End UE and the PC5 link with target 5G ProSe Layer-3 End UE. + +12. The source 5G ProSe Layer-3 End UE communicates with the target 5G ProSe Layer-3 End UE via the 5G ProSe Layer-3 UE-to-UE Relay. + +In the case of one source 5G ProSe Layer-3 End UE communicates with multiple target 5G ProSe Layer-3 End UEs, the PC5 link between the source 5G ProSe Layer-3 End UE and the 5G ProSe Layer-3 UE-to-UE Relay can be shared for multiple target 5G ProSe Layer-3 End UEs per RSC while the PC5 links may be established individually between the 5G ProSe Layer-3 UE-to-UE Relay and target 5G ProSe Layer-3 End UEs per RSC. For the shared PC5 link, the Layer-2 link modification procedure shall be used. The parameters used in the Layer-2 link modification procedure are described in clause 6.4.3.7. + +In the case of multiple source 5G ProSe Layer-3 End UEs communicate with one target 5G ProSe Layer-3 End UE, the PC5 link between the 5G ProSe Layer-3 UE-to-UE Relay and the target 5G ProSe Layer-3 End UE can be shared per RSC while the PC5 links may be established individually between the source 5G ProSe Layer-3 End UEs and the 5G ProSe Layer-3 UE-to-UE Relay per RSC. For the shared PC5 link, the Layer-2 link modification procedure shall be used. The parameters used in the Layer-2 link modification procedure are described in clause 6.4.3.7. + +#### 6.7.1.2 Link identifier update for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay + +The Link Identifier Update procedure as defined in clause 6.4.3.2 is reused between source 5G ProSe Layer-3 End UE and 5G ProSe Layer-3 UE-to-UE Relay to perform a link identifier update. When the IP address/prefix is changed, the new one is shared between source 5G ProSe Layer-3 End UE and target 5G ProSe Layer-3 End UE as depicted in Figure 6.7.1.2-1. + +![Sequence diagram illustrating Link Identifier Update and IP address/prefix sharing via 5G ProSe Layer-3 UE-to-UE Relay. The diagram shows three entities: UE1, UE-to-UE Relay, and UE2. UE1 and UE-to-UE Relay establish a PC5 unicast link (0). UE1 sends a Link Identifier Update Request (1) to the relay. The relay sends a Relay Update Request (2) to UE2. UE2 sends a Relay Update Response (3) back to the relay. The relay sends a Link Identifier Update Response (4) to UE1. UE1 sends a Link Identifier Update ACK (5) to the relay.](72d448a65347c51989171748789c7d4b_img.jpg) + +``` + +sequenceDiagram + participant UE1 + participant Relay as UE-to-UE Relay + participant UE2 + Note left of UE1: 0. PC5 unicast link + UE1->>Relay: 1. Link Identifier Update Request + Relay-->>UE2: 2. Relay Update Request + UE2-->>Relay: 3. Relay Update Response + Relay-->>UE1: 4. Link Identifier Update Response + UE1->>Relay: 5. Link Identifier Update ACK + +``` + +Sequence diagram illustrating Link Identifier Update and IP address/prefix sharing via 5G ProSe Layer-3 UE-to-UE Relay. The diagram shows three entities: UE1, UE-to-UE Relay, and UE2. UE1 and UE-to-UE Relay establish a PC5 unicast link (0). UE1 sends a Link Identifier Update Request (1) to the relay. The relay sends a Relay Update Request (2) to UE2. UE2 sends a Relay Update Response (3) back to the relay. The relay sends a Link Identifier Update Response (4) to UE1. UE1 sends a Link Identifier Update ACK (5) to the relay. + +**Figure 6.7.1.2-1: Link Identifier Update and IP address/prefix sharing via 5G ProSe Layer-3 UE-to-UE Relay** + +0. A PC5 link is established between a source 5G ProSe Layer-3 End UE (i.e. UE1) and a 5G ProSe Layer-3 UE-to-UE Relay (i.e. UE-to-UE Relay). Another PC5 link is established between the UE-to-UE Relay and the target 5G ProSe Layer-3 End UE (i.e. UE2). IP data may be exchanged between UE1 and UE2 via the UE-to-UE Relay over the PC5 links. During the link establishment, UE1 informs the UE-to-UE Relay that the link requires privacy. +1. As stated in clause 6.4.3.2, according to the privacy requirement, UE1 may trigger link identifier update procedure. UE1 sends a Link Identifier Update Request message to the UE-to-UE Relay including the following parameters: + - its new Layer-2 ID, new security information, new Application layer ID (if provided by the upper layer). + - If UE1's IP address/prefix needs to be changed: + - if UE 1's IP address/prefix is allocated by the UE-to-UE Relay, UE1 includes "new IP address needed" indication. + - if UE1 self-assign its IP address/prefix, UE1 includes its new IP address/prefix. + - its peer UEs information (e.g. UE2's IP address, UE2's Application layer ID), allowing the UE-to-UE Relay to inform UE1's peer UEs (e.g. UE2) about UE1's new allocated IP address/prefix. +2. UE-to-UE Relay self-assigns a new L2 ID, new security information and possibly new IP address/prefix for PC5 link with UE1. + - a. If a "new IP address needed" indication is received, UE-to-UE Relay assigns a new IP address/prefix to UE1 and saves it locally. + +Based on peer UE's information, UE-to-UE Relay then sends a PC5 Relay Update Request message to each peer UE (e.g. UE2), including: UE1's old IP address/prefix, UE1's old and new Application layer ID, UE1's new IP address/prefix. + +3. UE2 receives the PC5 Relay Update Request message and saves UE1's new IP address/prefix. UE2 sends a PC5 Relay Update Response message to the UE-to-UE Relay including all parameters received on the PC5 Relay Update Request message. + +UE2 continues to receive IP data with UE1's old IP address (transit packets sent prior to UE1's receiving its new IP address) until an IP packet using UE1's new IP address is received. At this point, UE2 starts using UE1's new IP address and may forget UE1's old IP address. + +4. UE-to-UE Relay sends a Link Identifier Update Response message to UE1 including UE1's new IP address/prefix, UE-to-UE Relay's new Layer-2 ID, new security information and possibly new IP address/prefix and/or new Application layer ID. +5. UE1 saves its new IP address/prefix and UE-to-UE Relay's new parameters and sends a Link Identifier Update ACK message to the UE-to-UE Relay, including its new IP address received on the Link Identifier Update Response message. UE1 and UE-to-UE Relay start using the new Layer-2 IDs and new security information for PC5 communication. UE1 starts using its new IP address for IP data exchange with UE2. + +### 6.7.1.3 Layer-2 link release for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay + +Figure 6.7.1.3-1 shows the Layer-2 link release procedure via 5G ProSe Layer-3 UE-to-UE Relay. + +![Sequence diagram illustrating the Layer-2 Link Release procedure via 5G ProSe Layer-3 UE-to-UE Relay. The diagram shows three entities: source 5G ProSe Layer-3 End UE, 5G ProSe Layer-3 UE-to-UE Relay, and target 5G ProSe Layer-3 End UE. The procedure starts with a unicast link established between the source UE and the relay, and between the relay and the target UE. The source UE sends a Disconnect Request to the relay. The relay responds with a Disconnect Response. The relay then sends a Disconnect Request to the target UE. The target UE responds with a Disconnect Response. The relay then sends a Link Modification Request to the target UE. The target UE responds with a Link Modification Accept.](02d5078b2b1c8b2c1e8374d5dc17aa86_img.jpg) + +``` + +sequenceDiagram + participant Source UE as source 5G ProSe Layer-3 End UE + participant Relay as 5G ProSe Layer-3 UE-to-UE Relay + participant Target UE as target 5G ProSe Layer-3 End UE + + Note left of Source UE: 0. Unicast link + Note right of Target UE: 0. Unicast link + Source UE->>Relay: 1. Disconnect Request + Relay-->>Source UE: 2. Disconnect Response + Relay-->>Target UE: 3a. Disconnect Request + Target UE-->>Relay: 4a. Disconnect Response + Relay-->>Target UE: 3b. Link Modification Request + Target UE-->>Relay: 4b. Link Modification Accept + +``` + +Sequence diagram illustrating the Layer-2 Link Release procedure via 5G ProSe Layer-3 UE-to-UE Relay. The diagram shows three entities: source 5G ProSe Layer-3 End UE, 5G ProSe Layer-3 UE-to-UE Relay, and target 5G ProSe Layer-3 End UE. The procedure starts with a unicast link established between the source UE and the relay, and between the relay and the target UE. The source UE sends a Disconnect Request to the relay. The relay responds with a Disconnect Response. The relay then sends a Disconnect Request to the target UE. The target UE responds with a Disconnect Response. The relay then sends a Link Modification Request to the target UE. The target UE responds with a Link Modification Accept. + +**Figure 6.7.1.3-1: Layer-2 Link Release procedure via 5G ProSe Layer-3 UE-to-UE Relay** + +0. The source 5G ProSe Layer-3 End UE and the 5G ProSe Layer-3 UE-to-UE Relay and the 5G ProSe Layer-3 UE-to-UE Relay and the target 5G ProSe Layer-3 End UE have a unicast link established as described in clause 6.7.1.1. +1. The source 5G ProSe Layer-3 End UE sends a Disconnect Request message to the 5G ProSe Layer-3 UE-to-UE Relay in order to release the layer-2 link and deletes all context data associated with the layer-2 link. +2. Upon reception of the Disconnect Request message, the 5G ProSe Layer-3 UE-to-UE Relay shall respond with a Disconnect Response and deletes all context data associated with the layer-2 link. +- 3a. Upon reception of the Disconnect Request message, the 5G ProSe Layer-3 UE-to-UE Relay sends a Disconnect Request message to the target 5G ProSe Layer-3 End UE(s), which has a unicast link for the communication with the source 5G ProSe Layer-3 End UE if there are no other UEs using the layer-2 link. +- 4a. Upon reception of the Disconnect Request message, the target 5G ProSe Layer-3 End UE shall respond with a Disconnect Response message. +- 3b. Upon reception of the Disconnect Request message, the 5G ProSe Layer-3 UE-to-UE Relay sends a Link Modification Request message to the target 5G ProSe Layer-3 End UE(s), which has a unicast link for the communication with the source 5G ProSe Layer-3 End UE if there are other UEs using the layer-2 link in order to release the PC5 QoS Flow(s) and deletes the context data associated with the PC5 QoS Flow(s). + +- 4b. Upon reception of the Link Modification Request message, the target 5G ProSe Layer-3 End UE shall respond with a Link Modification Accept message and deletes the context data associated with the PC5 QoS Flow(s) used for the communication with the source 5G ProSe Layer-3 End UE. + +The ProSe layer of the 5G ProSe Layer-3 UE-to-UE Relay and the target 5G ProSe Layer-3 End UE provides information about the unicast link modification to the AS layer, which enables the AS layer to update the context related to the modified unicast link. + +#### 6.7.1.4 Layer-2 link modification for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay + +Figure 6.7.1.4-1 shows the Layer-2 link modification procedure via Layer-3 UE-to-UE Relay. This procedure is used to add/modify/remove PC5 QoS Flow(s) in the existing PC5 unicast link as described in clause 6.4.3.7.3. + +![Sequence diagram illustrating the Layer-2 link modification procedure via Layer-3 UE-to-UE Relay. The diagram shows three entities: UE-1, UE-to-UE Relay, and UE-2. The process starts with an established unicast link (0). UE-1 sends a Link Modification Request (1) to the Relay. The Relay forwards this request (2) to UE-2. UE-2 responds with a Link Modification Accept (3) to the Relay. Finally, the Relay sends the Link Modification Accept (4) back to UE-1.](c701a84b904fedcdb0316835eafbd39f_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant Relay as UE-to-UE Relay + participant UE-2 + Note left of UE-1: 0. Unicast link + UE-1->>Relay: 1. Link Modification Request + Relay->>UE-2: 2. Link Modification Request + UE-2-->>Relay: 3. Link Modification Accept + Relay-->>UE-1: 4. Link Modification Accept + +``` + +Sequence diagram illustrating the Layer-2 link modification procedure via Layer-3 UE-to-UE Relay. The diagram shows three entities: UE-1, UE-to-UE Relay, and UE-2. The process starts with an established unicast link (0). UE-1 sends a Link Modification Request (1) to the Relay. The Relay forwards this request (2) to UE-2. UE-2 responds with a Link Modification Accept (3) to the Relay. Finally, the Relay sends the Link Modification Accept (4) back to UE-1. + +**Figure 6.7.1.4-1: Layer-2 link modification procedure via Layer-3 UE-to-UE Relay** + +0. UE-1 and UE-to-UE Relay and UE-to-UE Relay and UE-2 have a unicast link established as described in clause 6.7.1.1. +1. UE-1 sends a Link Modification Request to UE-to-UE Relay as described in clause 6.4.3.7.3. +2. Upon reception of the Link Modification Request message from UE-1, the UE-to-UE Relay sends a Link Modification Request to UE-2 as described in clause 6.4.3.7.3. +3. UE-2 responds with a Link Modification Accept message to the UE-to-UE Relay as described in clause 6.4.3.7.3. +4. Upon reception of the Link Modification Accept message from UE-2, the UE-to-UE Relay responds with a Link Modification Accept message to the UE-1 as described in clause 6.4.3.7.3. + +#### 6.7.1.5 Layer-2 link maintenance for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay + +The Layer-2 link maintenance over the PC5 reference point procedure as described in clause 6.4.3.5 can be used for the Layer-2 link established between the source 5G ProSe Layer-3 End UE and the 5G ProSe Layer-3 UE-to-UE Relay and between the 5G ProSe Layer-3 UE-to-UE Relay and the target 5G ProSe Layer-3 End UE. + +### 6.7.2 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay + +This procedure applies to 5G ProSe Layer-2 UE-to-UE Relay. + +![Sequence diagram illustrating 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay. The diagram shows three entities: End UE (left), UE-to-UE Relay (middle), and End UE (right). The sequence of steps is: 1. UE-to-UE Relay Discovery Procedure; 2. Establishment or modification of connection for unicast mode communication (between source End UE and Relay); 3. Establishment or modification of connection for unicast mode communication (between Relay and target End UE); 4. Establishment of end-to-end connection for unicast mode communication. Below step 4, a double-headed arrow labeled 'Relayed traffic' spans between the two End UEs, passing through the Relay.](b13465efdac63129aef9b6f1787d0d00_img.jpg) + +Sequence diagram illustrating 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay. The diagram shows three entities: End UE (left), UE-to-UE Relay (middle), and End UE (right). The sequence of steps is: 1. UE-to-UE Relay Discovery Procedure; 2. Establishment or modification of connection for unicast mode communication (between source End UE and Relay); 3. Establishment or modification of connection for unicast mode communication (between Relay and target End UE); 4. Establishment of end-to-end connection for unicast mode communication. Below step 4, a double-headed arrow labeled 'Relayed traffic' spans between the two End UEs, passing through the Relay. + +**Figure 6.7.2-1: 5G ProSe Communication via 5G ProSe Layer-2 UE-to-UE Relay** + +Service authorization and provisioning has been performed for the 5G ProSe Layer-2 UE-to-UE Relay and the 5G ProSe End UEs as described in clause 6.2 before this procedure. + +1. Model A or Model B 5G ProSe UE-to-UE Relay Discovery as described in clause 6.3.2.4 is performed and a source 5G ProSe End UE selects a suitable 5G ProSe Layer-2 UE-to-UE Relay for the communication with a target 5G ProSe End UE. +2. The source 5G ProSe End UE decides whether to use an existing PC5 link with the 5G ProSe UE-to-UE Relay for the required service. If an existing PC5 link is used then the Layer-2 link modification procedure as specified in clause 6.4.3.7 is used towards a 5G ProSe UE-to-UE Relay, otherwise a Layer-2 link establishment procedure is used towards a 5G ProSe UE-to-UE Relay. + +This procedure is towards the selected 5G ProSe UE-to-UE Relay and for Layer-2 link establishment, the security establishment is performed before step 3 is initiated. + +3. The 5G ProSe Layer-2 UE-to-UE Relay decides whether to use an existing PC5 link between the 5G ProSe UE-to-UE Relay and the target 5G ProSe End UE for the required service and initiates Layer-2 link establishment procedure or Layer-2 link modification procedure as specified in clause 6.4.3.7 with the target 5G ProSe End UE. + +This procedure is performed towards the target 5G ProSe End UE using the unicast Layer-2 ID. + +The 5G ProSe Layer-2 UE-to-UE Relay sends a Direct Communication Accept message or Link Modification Accept message to the the source 5G ProSe End UE after step 3 is completed. + +4. The source 5G ProSe End UE establishes an end-to-end connection for unicast mode communication with the target 5G ProSe End UE as described in clause 6.4.3.7. + +The data and End-to-End PC5-S signalling is transferred between the source 5G ProSe End UE and the target 5G ProSe End UE via the 5G ProSe Layer-2 UE-to-UE Relay. The 5G ProSe Layer-2 UE-to-UE Relay forwards all the data traffic and End-to-End PC5-S signalling between the source 5G ProSe End UE and the target 5G ProSe End UE, as specified in TS 38.300 [12]. + +## 6.7.3 5G ProSe UE-to-UE Relay Communication with integrated Discovery + +### 6.7.3.1 General + +5G ProSe Communication via 5G ProSe UE-to-UE Relay with integrated Discovery is supported. + +For 5G ProSe UE-to-UE Relay Communication with integrated Discovery, when a UE allows a UE-to-UE relay to be involved in the Direct Communication Request to the other UE, the UE indicates it by including a relay\_indication in the broadcasted Direct Communication Request message. + +When a UE-to-UE relay receives a Direct Communication Request including a relay\_indication, it decides whether to forward the message according to e.g. Relay Service Code if there is any, Application ID, operator policy per Relay Service Code, signal strength and local policy. + +### 6.7.3.2 Procedure for Communication via Layer-3 UE-to-UE Relay + +![Sequence diagram illustrating the procedure for 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-3 UE-to-UE Relay. The diagram shows four participants: UE-1, Relay-1, Relay-2, and UE-2. The process starts with service authorization and parameter provisioning. UE-1 sends a Direct Communication Request with a relay_indication to Relay-1, which is then forwarded by Relay-2 to UE-2. UE-2 performs relay selection and initiates security establishment with Relay-2. Relay-2 sends a Direct Communication Accept to Relay-1, which then forwards it to UE-1. IP address/prefix allocation occurs between UE-1 and Relay-1, and between Relay-2 and UE-2. Security establishment also occurs between UE-1 and Relay-1. Finally, UE-1 sends a Link Modification Request to Relay-1, which is forwarded by Relay-2 to UE-2, and UE-2 responds with a Link Modification Accept. Relayed traffic then flows between UE-1 and UE-2 via the relays.](1ff2bf0c111f189bef30c0d6e84aeefe_img.jpg) + +``` +sequenceDiagram + participant UE-1 + participant Relay-1 + participant Relay-2 + participant UE-2 + + Note over all: 0. Service authorization and parameter provisioning + UE-1->>Relay-1: 1. Direct Communication Request (relay_indication) + Relay-1->>Relay-2: 2. Direct Communication Request + Relay-2->>UE-2: 2. Direct Communication Request + Note right of UE-2: 3. Relay selection + UE-2->>Relay-2: 4. Security Establishment + Relay-2->>Relay-1: 5. Direct Communication Accept + Relay-1->>UE-1: 5. Direct Communication Accept + Note over all: 6. IP address/prefix allocation + UE-1->>Relay-1: 7. Security Establishment + Relay-1->>Relay-2: 8. Link Modification Request + Relay-2->>UE-2: 8. Link Modification Request + UE-2->>Relay-2: 9. Link Modification Accept + Relay-2->>Relay-1: 9. Link Modification Accept + Relay-1->>UE-1: 10. Direct Communication Accept + Note over all: 11. IP address/prefix allocation + Note over all: 12. DNS query/response + UE-1->>Relay-1: Relayed traffic + Relay-1->>Relay-2: Relayed traffic + Relay-2->>UE-2: Relayed traffic +``` + +Sequence diagram illustrating the procedure for 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-3 UE-to-UE Relay. The diagram shows four participants: UE-1, Relay-1, Relay-2, and UE-2. The process starts with service authorization and parameter provisioning. UE-1 sends a Direct Communication Request with a relay\_indication to Relay-1, which is then forwarded by Relay-2 to UE-2. UE-2 performs relay selection and initiates security establishment with Relay-2. Relay-2 sends a Direct Communication Accept to Relay-1, which then forwards it to UE-1. IP address/prefix allocation occurs between UE-1 and Relay-1, and between Relay-2 and UE-2. Security establishment also occurs between UE-1 and Relay-1. Finally, UE-1 sends a Link Modification Request to Relay-1, which is forwarded by Relay-2 to UE-2, and UE-2 responds with a Link Modification Accept. Relayed traffic then flows between UE-1 and UE-2 via the relays. + +Figure 6.7.3.2-1: 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-3 UE-to-UE Relay + +0. 5G ProSe End UEs are authorized and provisioned with parameters to use the service provided by the 5G ProSe UE-to-UE Relays. 5G ProSe UE-to-UE Relays are authorized and provisioned with parameters to provide service of relaying traffic among 5G ProSe End UEs. +1. The source 5G ProSe End UE (i.e. UE-1) wants to establish a unicast communication with the target 5G ProSe End UE (i.e. UE-2) and broadcasts a Direct Communication Request. The parameters included in the Direct Communication Request message are described in clause 6.4.3.7. + +The relay\_indication in the Direct Communication Request is used to indicate whether 5G ProSe UE-to-UE Relay can forward the Direct Communication Request message or not. It is also used to limit the number of hops of 5G ProSe UE-to-UE Relay by removing relay\_indication in the Direct Communication Request message from the 5G ProSe UE-to-UE Relay. + +The Source Layer-2 ID and Destination Layer-2 ID used for the Direct Communication Request message are defined in clause 5.8.5. + +The source 5G ProSe End UE gets application information and optional ProSe Application Requirements from ProSe application layer, and determines the end-to-end QoS parameters as described in clause 5.6.3.1. + +NOTE 1: The data type of relay\_indication can be determined in Stage 3. + +2. When receiving Direct Communication Request with relay\_indication from UE-1, the 5G ProSe UE-to-UE Relay (i.e. Relay-1 and Relay-2) may decide to participate in the procedure and broadcast a Direct Communication Request message in its proximity without relay\_indication. The parameters included in the Direct Communication Request message are described in clause 6.4.3.7. + +The Source Layer-2 ID and Destination Layer-2 ID used for the Direct Communication Request message are defined in clause 5.8.5. + +3. When UE-2 receives a Direct Communication Request from one or multiple 5G ProSe UE-to-UE Relays, UE-2 select a 5G ProSe UE-to-UE Relay which UE-2 will respond. UE-2 may select the 5G ProSe UE-to-UE Relay according to e.g. the signal strength, local policy, operator policy per Relay Service Code if any. +4. The security establishment happens between UE-2 and the selected 5G ProSe UE-to-UE Relay (here Relay-1), if needed. + +If the existing PC5 link can be reused, Link Modification Request and Link Modification Accept messages are used. + +NOTE 2: The conflict between Link Modification Request and Direct Communication Request can be determined in Stage 3. + +5. UE-2 replies Direct Communication Accept message to Relay-1. The parameters included in the Direct Communication Accept message are described in clause 6.4.3.7. +6. For IP traffic, IPv6 prefix or IPv4 address is allocated for the target 5G ProSe Layer-3 End UE as defined in clause 5.5.1.4. +7. Security establishment happens between UE-1 and Relay-1, if needed. +8. For 5G ProSe UE-to-UE Relay Communication with integrated Discovery, after receiving QoS Info of the end-to-end QoS from UE-1, Relay-1 provides the QoS info of the second hop QoS to UE-2 with Link Modification Request message. +9. For 5G ProSe UE-to-UE Relay Communication with integrated Discovery, UE-2 responds with a Link Modification Accept message. +10. Relay-1 responds with Direct Communication Accept to the UE-1. The parameters included in the Direct Communication Accept message are described in clause 6.4.3.7. +11. For IP traffic, IPv6 prefix or IPv4 address is allocated for the source 5G ProSe Layer-3 End UE as defined in clause 5.5.1.4. +12. For IP communication, the 5G ProSe Layer-3 UE-to-UE Relay may store an association of User Info ID and the IP address of target 5G ProSe Layer-3 End UE into its DNS entries and the 5G ProSe Layer-3 UE-to-UE Relay may act as a DNS server to other UEs. The source 5G ProSe Layer-3 End UE may send a DNS query to the 5G + +ProSe Layer-3 UE-to-UE Relay to request IP address of target 5G ProSe Layer-3 End UE after step 11 if the IP address of target 5G ProSe Layer-3 End UE is not received in step 10 and the 5G ProSe Layer-3 UE-to-UE Relay returns the IP address of the target 5G ProSe Layer-3 End UE to the source 5G ProSe Layer-3 End UE. + +For Ethernet communication, the 5G ProSe Layer-3 UE-to-UE Relay is acting as an Ethernet switch by maintaining the association between PC5 links and Ethernet MAC addresses received from the 5G ProSe Layer-3 End UE. + +For Unstructured traffic communication, for each pair of source and target 5G ProSe Layer-3 End UEs, the 5G ProSe Layer-3 UE-to-UE Relay maintains the 1:1 mapping between the PC5 link with source 5G ProSe Layer-3 End UE and the PC5 link with target 5G ProSe Layer-3 End UE. + +The source 5G ProSe Layer-3 End UE communicates with the target 5G ProSe Layer-3 End UE via the 5G ProSe Layer-3 UE-to-UE Relay. + +### 6.7.3.3 Procedure for Communication via Layer-2 UE-to-UE Relay + +![Sequence diagram for 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-2 UE-to-UE Relay. The diagram shows four lifelines: UE-1, Relay-1, Relay-2, and UE-2. The sequence of messages is: 0. Service authorization and parameter provisioning (between UE-1 and UE-2); 1. Direct Communication Request (relay_indication enabled) from UE-1 to Relay-2; 2. Direct Communication Request from Relay-1 to UE-2; 2. Direct Communication Request from Relay-2 to UE-2; 3. Relay Selection (between Relay-2 and UE-2); 4. Security Establishment (between Relay-1 and UE-2); 5. Direct Communication Accept from Relay-1 to UE-1; 6. Security Establishment (between UE-1 and Relay-1); 7. Direct Communication Accept from UE-1 to Relay-1; 8. Establishment of end-to-end connection for unicast mode communication (between UE-1 and UE-2).](1c051a3d61003bc7d513e03015245317_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant Relay-1 + participant Relay-2 + participant UE-2 + + Note over UE-1, UE-2: 0. Service authorization and parameter provisioning + UE-1->>Relay-2: 1. Direct Communication Request (relay_indication enabled) + Relay-1->>UE-2: 2. Direct Communication Request + Relay-2->>UE-2: 2. Direct Communication Request + Note over Relay-2, UE-2: 3. Relay Selection + Note over Relay-1, UE-2: 4. Security Establishment + Relay-1->>UE-1: 5. Direct Communication Accept + Note over UE-1, Relay-1: 6. Security Establishment + UE-1->>Relay-1: 7. Direct Communication Accept + Note over UE-1, UE-2: 8. Establishment of end-to-end connection for unicast mode communication + +``` + +Sequence diagram for 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-2 UE-to-UE Relay. The diagram shows four lifelines: UE-1, Relay-1, Relay-2, and UE-2. The sequence of messages is: 0. Service authorization and parameter provisioning (between UE-1 and UE-2); 1. Direct Communication Request (relay\_indication enabled) from UE-1 to Relay-2; 2. Direct Communication Request from Relay-1 to UE-2; 2. Direct Communication Request from Relay-2 to UE-2; 3. Relay Selection (between Relay-2 and UE-2); 4. Security Establishment (between Relay-1 and UE-2); 5. Direct Communication Accept from Relay-1 to UE-1; 6. Security Establishment (between UE-1 and Relay-1); 7. Direct Communication Accept from UE-1 to Relay-1; 8. Establishment of end-to-end connection for unicast mode communication (between UE-1 and UE-2). + +**Figure 6.7.3.3-1: 5G ProSe UE-to-UE Relay Communication with integrated Discovery via Layer-2 UE-to-UE Relay** + +0-5. It is the same as steps 0-5 of Figure 6.7.3.2-1. + +6. It is the same as step 7 of Figure 6.7.3.2-1. + +7. It is the same as step 10 of Figure 6.7.3.2-1. + +The parameters included in the above messages are described in clause 6.4.3.7.4. + +8. For 5G ProSe UE-to-UE Relay Communication via Layer-2 UE-to-UE Relay, UE-1 establishes an end-to-end connection for unicast mode communication with UE-2. + +**Editor's note:** Any additional update of procedure via Layer-2 UE-to-UE Relay, e.g. according to RAN's decision, will be included here. + +## 6.7.4 5G ProSe UE-to-UE Relay reselection + +### 6.7.4.1 General + +After being connected to the 5G ProSe UE-to-UE Relay, the 5G ProSe End UEs may trigger the 5G ProSe UE-to-UE Relay reselection based on conditions (e.g. the measured signal strength of PC5 unicast link with the 5G ProSe UE-to-UE Relay) as specified in TS 38.300 [12]. + +For 5G ProSe UE-to-UE Relay reselection, a 5G ProSe UE-to-UE Relay may be discovered by either the discovery procedures defined in clause 6.3.2.4 or by the negotiated 5G ProSe UE-to-UE Relay reselection procedure defined in clause 6.7.4.2 or clause 6.7.4.3. + +In the negotiated UE-to-UE Relay reselection defined in clause 6.7.4.2 or clause 6.7.4.3, one 5G ProSe End UE initiates the UE-to-UE Relay reselection procedure, the 5G ProSe End UEs can negotiate a new 5G ProSe UE-to-UE Relay using the existing connection and to establish the communication via the reselected 5G ProSe UE-to-UE Relay prior to releasing the communication via the current 5G ProSe UE-to-UE Relay. + +### 6.7.4.2 Negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection + +Depicted in Figure 6.7.4.2-1 is the procedure for the negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection. + +![Sequence diagram illustrating the Negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection procedure. The diagram shows four entities: 5G ProSe End UE, Relay UE 1, Relay UE 2, and 5G ProSe End UE. The process starts with a connection setup between the two 5G ProSe End UEs via Relay UE 1. Traffic transfer occurs between the two 5G ProSe End UEs. The first 5G ProSe End UE then decides to perform UE reselection. It sends a Link Modification Request message to Relay UE 1. Relay UE 1 then sends a message to Relay UE 2 to decide on the new Relay UE. Relay UE 2 sends a Link Modification Accept message back to the first 5G ProSe End UE. Finally, a connection setup is performed between the two 5G ProSe End UEs via the new Relay UE (Relay UE 2).](4514db66fce4bb74f66cea56d5106b62_img.jpg) + +``` + +sequenceDiagram + participant UE1 as 5G ProSe End UE + participant R1 as Relay UE 1 + participant R2 as Relay UE 2 + participant UE2 as 5G ProSe End UE + + Note over UE1, R1: 1. Connection setup between 5G ProSe UEs via Relay UE 1 + UE1->>R1: Traffic transfer + R1->>UE2: Traffic transfer + Note left of UE1: 2. Decide to Relay UE reselection + UE1->>R1: 3. Link Modification Request message + Note right of R2: 4. Decide the new Relay UE + R2->>UE1: 5. Link Modification Accept message + Note over UE1, R2: 6. Connection setup between 5G ProSe UEs via new Relay UE + +``` + +Sequence diagram illustrating the Negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection procedure. The diagram shows four entities: 5G ProSe End UE, Relay UE 1, Relay UE 2, and 5G ProSe End UE. The process starts with a connection setup between the two 5G ProSe End UEs via Relay UE 1. Traffic transfer occurs between the two 5G ProSe End UEs. The first 5G ProSe End UE then decides to perform UE reselection. It sends a Link Modification Request message to Relay UE 1. Relay UE 1 then sends a message to Relay UE 2 to decide on the new Relay UE. Relay UE 2 sends a Link Modification Accept message back to the first 5G ProSe End UE. Finally, a connection setup is performed between the two 5G ProSe End UEs via the new Relay UE (Relay UE 2). + +**Figure 6.7.4.2-1: Negotiated 5G ProSe Layer-2 UE-to-UE Relay reselection** + +1. A PC5 unicast link is established between the 5G ProSe End UEs via a 5G ProSe UE-to-UE Relay, based on the procedure defined in clause 6.7.2. +2. The initiating 5G ProSe End UE determines, e.g. based on PC5 signal strength, to perform UE-to-UE Relay reselection and obtains a list of candidate UE-to-UE Relays per RSC. The initiating 5G ProSe End UE may receive UE-to-UE Relay Discovery Announcement messages from 5G ProSe UE-to-UE Relays or initiate the 5G ProSe UE-to-UE Relay discovery procedures to find the candidate 5G ProSe UE-to-UE Relays. The initiating 5G ProSe End UE determines the candidate 5G ProSe UE-to-UE Relays e.g., based on the PC5 signal strength of the received UE-to-UE Relay Discovery Announcement message, RSC within the UE-to-UE Relay Discovery + +Announcement message. The candidate 5G ProSe UE-to-UE Relays support the same RSC which is associated with the PC5 unicast link between the initiating 5G ProSe End UE and the 5G ProSe UE-to-UE Relay. + +3. The initiating 5G ProSe End UE sends a Link Modification Request message to the responding 5G ProSe End UE which includes a Relay re-selection indication, the User Info ID(s) of the candidate 5G ProSe UE-to-UE Relay(s) and optionally the Layer-2 ID(s) of the candidate 5G ProSe UE-to-UE Relay(s) and security information. +4. The responding 5G ProSe End UE selects a new 5G ProSe UE-to-UE Relay from the candidate 5G ProSe UE-to-UE Relays per RSC, based on the Relay re-selection indication in the Link Modification Request message. If the responding 5G ProSe End UE has not received a UE-to-UE Relay Discovery Announcement message from a candidate 5G ProSe UE-to-UE Relay (e.g. during a previous 5G ProSe UE-to-UE Relay Discovery procedure) or does not have a PC5 connection with the candidate 5G ProSe UE-to-UE Relay associated with the same RSC, then the responding 5G ProSe End UE may perform the Candidate 5G ProSe UE-to-UE Relay Discovery procedure defined in clause 6.3.2.4.4. The responding 5G ProSe End UE sets the candidate relay User Info ID to that of a candidate 5G ProSe UE-to-UE Relay in the discovery message and may set the Layer-2 ID of the candidate 5G ProSe UE-to-UE Relay, if received at step 3, as the Destination Layer-2 ID to carry the discovery message. The PC5 signal strength of the UE-to-UE Relay Discovery Announcement message or UE-to-UE Relay Discovery Response message may be used to select the new 5G ProSe UE-to-UE Relay. +5. The responding 5G ProSe End UE sends a Link Modification Accept message to the initiating 5G ProSe End UE, including the User Info ID of the new 5G ProSe UE-to-UE Relay and security information. +6. 5G ProSe End UEs set up PC5 unicast links, if not already set up, with the new 5G ProSe UE-to-UE Relay, by reusing the procedure defined in clause 6.7.2 and the PC5 unicast link is established between 5G ProSe End UEs via the new 5G ProSe UE-to-UE Relay. The 5G ProSe End UEs switch the data traffic via the new 5G ProSe UE-to-UE Relay. The security information is used to verify that the new link has been set up successfully. + +NOTE 1: The security information contents and usage will be defined by SA WG3. + +NOTE 2: Whether a 5G ProSe End UE releases a PC5 unicast link with the original 5G ProSe UE-to-UE Relay after reselection depends on whether the PC5 unicast link is still required and UE implementation. + +#### 6.7.4.3 Negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection + +Depicted in Figure 6.7.4.3-1 is the procedure for the negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection. + +![Sequence diagram illustrating Negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection. The diagram shows two 5G ProSe End UEs, Relay1, and Relay2. The sequence of messages is: 1. PC5 unicast from End UE to Relay1; 1a. PC5 unicast link from Relay1 to End UE; 2. PC5 unicast from End UE to Relay1; 2a. PC5 unicast link from Relay1 to End UE; 3. Traffic transfer (via Relay 1) from End UE to End UE; 4. Decide to do Relay UE reselection (internal message); 5. Link Modification Request from End UE to Relay1; 6. Link Modification Request from Relay1 to End UE; 7. Select Relay2 (internal message); 8. Link Modification Accept from End UE to Relay1; 9. Link Modification Accept from Relay1 to End UE; 10. Link Modification Ack from End UE to Relay1; 11. Link Modification Ack from Relay1 to End UE; 12. IP traffic via Relay 2 from End UE to End UE.](db7a693cf26f527ac6c0d4d41da20858_img.jpg) + +``` + +sequenceDiagram + participant EndUE1 as 5G ProSe End UE + participant Relay1 as Relay1 + participant Relay2 as Relay2 + participant EndUE2 as 5G ProSe End UE + + Note left of EndUE1: 4. Decide to do Relay UE reselection + EndUE1->>Relay1: 1. PC5 unicast + Relay1-->>EndUE2: 1a. PC5 unicast link + EndUE1->>Relay1: 2. PC5 unicast + Relay1-->>EndUE2: 2a. PC5 unicast link + EndUE1->>EndUE2: 3. Traffic transfer (via Relay 1) + Note left of EndUE1: 4. Decide to do Relay UE reselection + EndUE1->>Relay1: 5. Link Modification Request + Relay1->>EndUE2: 6. Link Modification Request + Note right of EndUE2: 7. Select Relay2 + EndUE2->>Relay1: 8. Link Modification Accept + Relay1->>EndUE1: 9. Link Modification Accept + EndUE1->>Relay1: 10. Link Modification Ack + Relay1->>EndUE2: 11. Link Modification Ack + EndUE1->>EndUE2: 12. IP traffic via Relay 2 + +``` + +Sequence diagram illustrating Negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection. The diagram shows two 5G ProSe End UEs, Relay1, and Relay2. The sequence of messages is: 1. PC5 unicast from End UE to Relay1; 1a. PC5 unicast link from Relay1 to End UE; 2. PC5 unicast from End UE to Relay1; 2a. PC5 unicast link from Relay1 to End UE; 3. Traffic transfer (via Relay 1) from End UE to End UE; 4. Decide to do Relay UE reselection (internal message); 5. Link Modification Request from End UE to Relay1; 6. Link Modification Request from Relay1 to End UE; 7. Select Relay2 (internal message); 8. Link Modification Accept from End UE to Relay1; 9. Link Modification Accept from Relay1 to End UE; 10. Link Modification Ack from End UE to Relay1; 11. Link Modification Ack from Relay1 to End UE; 12. IP traffic via Relay 2 from End UE to End UE. + +**Figure 6.7.4.3-1: Negotiated 5G ProSe Layer-3 UE-to-UE Relay reselection** + +1. 5G ProSe End UEs have set up PC5 unicast links with a 5G ProSe UE-to-UE Relay, based on the procedure defined in clause 6.7.1. +2. The 5G ProSe End UEs have additionally set up PC5 unicast links with a 5G ProSe UE-to-UE Relay, based on the procedure defined in clause 6.7.1. +3. The 5G ProSe End UEs are transferring traffic via the 5G ProSe UE-to-UE Relay. +4. The initiating 5G ProSe End UE determines, e.g. based on PC5 signal strength, to perform UE-to-UE Relay reselection and obtains a list of candidate UE-to-UE Relays per RSC. The initiating 5G ProSe End UE may receive UE-to-UE Relay Discovery Announcement messages from 5G ProSe UE-to-UE Relays or initiate the 5G ProSe UE-to-UE Relay discovery procedures to find the candidate 5G ProSe UE-to-UE Relays. The initiating 5G ProSe End UE determines the candidate 5G ProSe UE-to-UE Relays e.g., based on the PC5 signal strength of the received UE-to-UE Relay Discovery Announcement message, RSC within the UE-to-UE Relay Discovery Announcement message. The candidate 5G ProSe UE-to-UE Relays support the same RSC which is associated with the PC5 unicast link between the initiating 5G ProSe End UE and the 5G ProSe UE-to-UE Relay. +5. The initiating 5G ProSe End UE sends a Link Modification Request message to the responding 5G ProSe UE-to-UE Relay, which includes a Relay re-selection indication, the User Info ID(s) of the candidate 5G ProSe UE-to-UE Relay(s), the IP addresses of the responding 5G ProSe End UEs and optionally the Layer-2 ID(s) of the candidate 5G ProSe UE-to-UE Relay(s). + +Multiple 5G ProSe End UEs IP addresses may be included when the initiating 5G ProSe End UE is communicating with multiple 5G ProSe End UEs via the 5G ProSe UE-to-UE Relay. + +6. 5G ProSe UE-to-UE Relay determines the responding 5G ProSe End UE based on the IP address received from the initiating 5G ProSe End UE and sends a Link Modification Request message to the responding 5G ProSe End UE. The Link Modification Request message includes a Relay re-selection indication, User Info ID(s) of the candidate 5G ProSe UE-to-UE Relay(s), IP address of the initiating 5G ProSe End UE and optionally the Layer-2 ID(s) of the candidate 5G ProSe UE-to-UE Relay(s). + +If multiple 5G ProSe End UEs are specified in the Link Modification Request message received from the initiating 5G ProSe End UE, the 5G ProSe UE-to-UE Relay sends a PC5 Link Modification Request to each of the 5G ProSe End UEs. + +7. The responding 5G ProSe End UE selects a new 5G ProSe UE-to-UE Relay from the candidate 5G ProSe UE-to-UE Relays per RSC, based on the Relay re-selection indication in the Link Modification Request message. If the responding 5G ProSe End UE has not received a UE-to-UE Relay Discovery Announcement message from a candidate 5G ProSe UE-to-UE Relay (e.g. during a previous 5G ProSe UE-to-UE Relay Discovery procedure) or does not have a PC5 connection with the candidate 5G ProSe UE-to-UE Relay associated with the same RSC, then the responding 5G ProSe End UE may perform the Candidate 5G ProSe UE-to-UE Relay Discovery procedure defined in clause 6.3.2.4.4. The responding 5G ProSe End UE sets the candidate relay User Info ID to that of a candidate 5G ProSe UE-to-UE Relay in the discovery message and may set the Layer-2 ID of the candidate 5G ProSe UE-to-UE Relay, if received at step 6, as the Destination Layer-2 ID to carry the discovery message. The responding 5G ProSe End UE may initiate the procedure to set up PC5 unicast links with the new 5G ProSe UE-to-UE Relay, by reusing the procedure defined in clause 6.7.1. The PC5 signal strength of the UE-to-UE Relay Discovery Announcement message or UE-to-UE Relay Discovery Response message may be used to select the new 5G ProSe UE-to-UE Relay. +8. The responding 5G ProSe End UE sends a Link Modification Accept message to the 5G ProSe UE-to-UE Relay, including the User Info ID of the new 5G ProSe UE-to-UE Relay, IP address of the initiating 5G ProSe End UE, IP address of the responding 5G ProSe End UE for communication via the newly selected 5G ProSe UE-to-UE Relay and Relay re-selection indication. +9. 5G ProSe UE-to-UE Relay sends a Link Modification Accept message to the initiating 5G ProSe End UE, including the User Info ID of the new 5G ProSe UE-to-UE Relay, IP address of the responding 5G ProSe End UE, IP address of the responding 5G ProSe End UE for communication via the newly selected 5G ProSe UE-to-UE Relay and Relay re-selection indication. +- 10-11. Link Modification Ack is sent from the initiating 5G ProSe End UE to the responding the 5G ProSe End UE via the 5G ProSe UE-to-UE Relay, including the IP address of the initiating 5G ProSe End UE for communication via the newly selected 5G ProSe UE-to-UE Relay, the IP address of the responding 5G ProSe End UE and Relay re-selection indication. +12. The 5G ProSe End UEs transfer traffic via the newly selected 5G ProSe UE-to-UE Relay. + +NOTE: Whether a 5G ProSe End UE releases a PC5 unicast link with the original 5G ProSe UE-to-UE Relay after reselection depends on whether the PC5 unicast link is still required and UE implementation. + +## 6.8 Procedures for communication path switching between PC5 and Uu reference points + +### 6.8.1 Procedure for communication path switching from Uu reference point to PC5 reference point + +Figure 6.8.1-1 depicts the procedure for communication path switching from Uu reference point to PC5 reference point. + +![Sequence diagram illustrating the procedure for communication path switching from Uu reference point to PC5 reference point. The diagram shows five main steps between UE-1 and UE-2, with optional steps 5a and 5b involving the Data Network.](9958beca8f65818eb0ff893647af94de_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + participant NG-RAN + participant 5GC + participant DN as Data Network + + Note right of UE-1: 1. UE-1 and UE-2 communicate with each other via Uu path + Note right of UE-1: 2. UE-1 decides path switching to PC5 path. + Note right of UE-1: 3. UE-1 and UE-2 establish or modify PC5 unicast link. + Note right of UE-1: 4. Traffic for the ProSe service(s) is switched from Uu path to PC5 path. + Note right of UE-1: 5a. UE-1 may release or modify PDU Session. + Note right of UE-2: 5b. UE-2 may release or modify PDU Session. + +``` + +Sequence diagram illustrating the procedure for communication path switching from Uu reference point to PC5 reference point. The diagram shows five main steps between UE-1 and UE-2, with optional steps 5a and 5b involving the Data Network. + +**Figure 6.8.1-1: Procedure for communication path switching from Uu reference point to PC5 reference point** + +1. UE-1 and UE-2 communicate with each other via Uu path, i.e. by using established PDU Sessions. +2. UE-1 decides to perform path switching for ProSe service(s) from Uu path to PC5 path, e.g. because UE-1 and UE-2 are in proximity each other or for offloading some traffic from the network. + +NOTE 1: UE-1 can perform ProSe discovery to determine whether UE-2 is in proximity using the User Info of UE-2 provided by the application layer. + +UE-1 determines whether and which ProSe service(s) can be switched to PC5 path based on the path selection policy. + +3. UE-1 triggers the establishment of a PC5 unicast link by using the Layer-2 link establishment procedure as specified in clause 6.4.3.1. The PC5 unicast link is established including the ProSe service(s) that can be switched to PC5 path. If any Layer-2 link already established between UE-1 and UE-2 can be used for this path switching, the Layer-2 link modification as specified in clause 6.4.3.4 is used. +4. Traffic for the ProSe service(s) is switched from Uu path to PC5 path. +- 5a. UE-1 may release its PDU Session, e.g. if no traffic transmitted over the PDU Session, or modify its PDU Session, e.g. only part of the services is switched. +- 5b. UE-2 may release its PDU Session, e.g. if no traffic transmitted over the PDU Session, or modify its PDU Session, e.g. only part of the services is switched. + +NOTE 2: Steps 5a and 5b can be executed in parallel. + +NOTE 3: As an alternative to steps 5a and 5b, the UP connection of the relevant PDU Sessions can be deactivated as specified in clause 4.3.7 of TS 23.502 [5]. + +## 6.8.2 Procedure for communication path switching from PC5 reference point to Uu reference point + +Figure 6.8.2-1 depicts the procedure for communication path switching from PC5 reference point to Uu reference point. + +![Sequence diagram illustrating the procedure for communication path switching from PC5 reference point to Uu reference point. The diagram shows interactions between UE-1, UE-2, NG-RAN, 5GC, and Data Network. Steps include: 1. UE-1 and UE-2 communicate via PC5 path; 2. UE-1 sends Path Switch Request to UE-2; 3. UE-2 sends Path Switch Response to UE-1; 4a. UE-1 may establish or modify PDU Session; 4b. UE-2 may establish or modify PDU Session; 5. Traffic for ProSe service(s) is switched from PC5 path to Uu path; 6. UE-1 and UE-2 may release PC5 unicast link.](fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant UE-2 + participant NG-RAN + participant 5GC + participant DN as Data Network + + Note over UE-1, UE-2: 1. UE-1 and UE-2 communicate with each other via PC5 path + UE-1->>UE-2: 2. Path Switch Request + UE-2-->>UE-1: 3. Path Switch Response + Note over UE-1, NG-RAN, 5GC, DN: 4a. UE-1 may establish or modify PDU Session. + Note over UE-2, NG-RAN, 5GC, DN: 4b. UE-2 may establish or modify PDU Session. + Note over UE-1, UE-2, NG-RAN, 5GC, DN: 5. Traffic for the ProSe service(s) is switched from PC5 path to Uu path. + Note over UE-1, UE-2: 6. UE-1 and UE-2 may release PC5 unicast link. + +``` + +Sequence diagram illustrating the procedure for communication path switching from PC5 reference point to Uu reference point. The diagram shows interactions between UE-1, UE-2, NG-RAN, 5GC, and Data Network. Steps include: 1. UE-1 and UE-2 communicate via PC5 path; 2. UE-1 sends Path Switch Request to UE-2; 3. UE-2 sends Path Switch Response to UE-1; 4a. UE-1 may establish or modify PDU Session; 4b. UE-2 may establish or modify PDU Session; 5. Traffic for ProSe service(s) is switched from PC5 path to Uu path; 6. UE-1 and UE-2 may release PC5 unicast link. + +**Figure 6.8.2-1: Procedure for communication path switching from PC5 reference point to Uu reference point** + +1. UE-1 and UE-2 communicate with each other via PC5 path, i.e. by using the established PC5 unicast link between them. +2. UE-1 decides to path switch ProSe service(s) from PC5 path to Uu path, e.g. if the PC5 signal strength of the unicast link with UE-2 reaches or below certain configured signal strength threshold. + +UE-1 determines whether and which ProSe service(s) can be switched to Uu path based on e.g. the availability of the Uu path, the path selection policy, etc. + +UE-1 sends a Path Switch Request message to UE-2 to negotiate the ProSe service(s) to be switched. UE-1 includes the ProSe service(s) that can be switched to Uu path in the Path Switch Request message. + +Optionally, UE-1 can decide the Uu QoS parameters of each UE based on PC5 QoS parameters for each ProSe service. UE-1 may include Uu QoS parameters used for UE-2's Uu path for the ProSe service(s) that can be switched to a Uu path in the Path Switch Request message. + +3. UE-2 responds with a Path Switch Response message. + +UE-2 determines whether and which ProSe service(s) can be switched to Uu path based on e.g., the path selection policy, availability of Uu path, etc. + +If UE-2 accepts the path switch request from UE-1, UE-2 includes the accepted ProSe service(s) to be switched to Uu path in the Path Switch Response message from those indicated by UE-1. Otherwise, UE-2 rejects the path switch request with the appropriate cause (e.g. path switching to Uu path for the ProSe service(s) is not permitted, Uu path is not available) in the Path Switch Response message. + +- 4a. UE-1 may establish or modify PDU Session by using the PDU session establishment procedure as specified in clause 4.3.2 or the PDU session modification procedure as specified in clause 4.3.3 of TS 23.502 [5]. UE-1 may set the Requested QoS as the Uu QoS parameters used for UE-1's Uu path for the specific accepted ProSe service in the PDU Session Modification Request. The PDU Session needs to support QoS requirements for the ProSe service(s) to be switched from PC5 path. +- 4b. UE-2 may establish or modify PDU Session by using the PDU session establishment procedure as specified in clause 4.3.2 or the PDU session modification procedure as specified in clause 4.3.3 of TS 23.502 [5]. UE-2 may set the Requested QoS as the Uu QoS parameters used for UE-2's Uu path for the specific accepted ProSe service in the PDU Session Modification Request. The PDU Session needs to support QoS requirements for the ProSe service(s) to be switched from PC5 path. + +NOTE 1: Steps 4a and 4b can be executed in parallel and step 4b can be performed before step 3. + +5. Traffic for the accepted ProSe service(s) is switched from PC5 path to Uu path. + +6. The PC5 unicast link may be released, e.g. if no more ProSe services over the PC5 unicast link. + +NOTE 2: The UEs can agree to maintain the PC5 unicast link after path switching from PC5 path to Uu path. In this case, the UEs can determine to switch back to PC5 path from Uu path based on e.g. the path selection policy, the PC5 signal level of the maintained unicast link (e.g. the measured link quality is good). + +NOTE 3: When the UEs cannot successfully exchange Path Switch Request/Response due to, e.g. the PC5 unicast link suddenly breaks, whether to perform path switching to Uu path is left to UE implementation. + +## 6.9 Multi-path communication via Uu and via 5G ProSe UE-to-Network Relay + +### 6.9.1 General + +This clause describes the procedures to support multi-path communication via direct Uu path and via 5G ProSe UE-to-Network Relay. + +### 6.9.2 Multi-path communication via direct Uu path and via 5G ProSe Layer-3 UE-to-Network Relay + +When a 5G ProSe enabled UE accesses the network, if the UE decides to establish multi-path via direct Uu path and via the 5G ProSe Layer-3 UE-to-Network Relay without N3IWF based on "ProSe Multi-path Preference" in the selected RSD of the matched URSP rule for the application traffic as specified in clause 6.5.4, the following is performed: + +- The UE may establish a new PDU Session as specified in clause 4.3.2 of TS 23.502 [5] or modify an existing PDU Session as specified in clause 4.3.3 of TS 23.502 [5] for the direct Uu path. +- The UE takes the role of 5G ProSe Layer-3 Remote UE either establishes 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF as specified in clause 6.5.1.1 or modifies an existing PC5 connection with a 5G ProSe Layer-3 UE-to-Network Relay as specified in clause 6.4.3.6. + +NOTE 1: How to make use of the multi-path communication via direct Uu path and via a 5G ProSe Layer-3 UE-to-Network Relay for redundant or split traffic delivery is out of scope of this specifications. + +When a 5G ProSe enabled UE accesses the network, if the UE decides to establish multi-path via direct Uu path and via the 5G ProSe Layer-3 UE-to-Network Relay with N3IWF based on the "multi-access" Access Type of the selected RSD, the UE establishes a MA PDU Session as specified in clause 4.22 of TS 23.502 [5], the following is performed: + +- The UE sets up path over Uu by establishing a MA PDU session using the procedures for 3GPP access in clause 4.22 of TS 23.502 [5]. +- The UE taking the role of 5G ProSe Layer-3 Remote UE, if not connected and registered to the network via a Layer-3 UE-to-Network Relay with N3IWF, performs Relay (re)selection and performs registration with 5GC as specified in clause 6.5.1.2 and then performs MA PDU Session Establishment procedure or adds the user plane resources over the path via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF using the procedures for non-3GPP access in clause 4.22 of TS 23.502 [5]. + +NOTE 2: The Remote UE may establish MA PDU session over the path via 5G ProSe Layer-3 UE-to-Network Relay with N3IWF before the direct Uu path. The sequence could be arbitrary. + +### 6.9.3 Multi-path communication via direct Uu path and via 5G ProSe Layer-2 UE-to-Network Relay + +Procedure on Multi-path communication via direct Uu path and via 5G ProSe Layer-2 UE-to-Network Relay is specified in TS 38.300 [12]. + +## 7 Network Function Services + +### 7.1 5G DDNMF Services + +#### 7.1.1 General + +The following table illustrates the 5G DDNMF Services. + +**Table 7.1.1-1: Services provided by 5G DDNMF** + +| Service Name | Service Operations | Operation Semantics | Example Consumer(s) | +|---------------------|---------------------|---------------------|---------------------| +| N5g-ddnmf_Discovery | AnnounceAuthorize | Request/Response | 5G DDNMF | +| | AnnounceUpdate | Request/Response | 5G DDNMF | +| | MonitorAuthorize | Request/Response | 5G DDNMF | +| | MonitorUpdate | Request/Response | 5G DDNMF | +| | MonitorUpdateResult | Notify | 5G DDNMF | +| | DiscoveryAuthorize | Request/Response | 5G DDNMF | +| | MatchReport | Request/Response | 5G DDNMF | +| | MatchInformation | Notify | 5G DDNMF | + +#### 7.1.2 N5g-ddnmf\_Discovery service + +##### 7.1.2.1 General + +**Service description:** This service enables a 5G DDNMF to manage inter-PLMN ProSe Direct Discovery operations. + +##### 7.1.2.2 N5g-ddnmf\_Discovery\_AnnounceAuthorize service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_AnnounceAuthorize + +**Description:** The consumer NF obtains the authorization from the 5G DDNMF for announcing in the PLMN. + +**Input, Required:** Discovery type ("open" or "restricted ") and + +- (for "open" discovery type:) ProSe Application ID, ProSe Application Code, UE Identity, validity timer, Discovery Entry ID, +- (for "restricted" discovery type:) RPAUID, Application ID, ProSe Restricted Code/Prefix, UE Identity, Discovery Entry ID, + +**Input, Optional:** metadata, Restricted Code Suffix pool. + +**Output, Required:** authorization result. + +**Output, Optional:** None. + +##### 7.1.2.3 N5g-ddnmf\_Discovery\_AnnounceUpdate service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_AnnounceUpdate + +**Description:** The consumer NF updates or revoke the authorization from the 5G DDNMF for announcing in the PLMN. + +**Input, Required:** Discovery type = "open", UE Identity, validity timer, Discovery Entry ID + +**Input, Optional:** ProSe Application Code + +**Output, Required:** result. + +**Output, Optional:** None. + +#### 7.1.2.4 N5g-ddnmf\_Discovery\_MonitorAuthorize service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_MonitorAuthorize + +**Description:** The consumer NF obtains the authorization from the 5G DDNMF for monitoring in the PLMN. + +**Input, Required:** Discovery type ("open" or "restricted") and + +- (for "open" discovery type:) ProSe Application ID Name(s), UE Identity, Discovery Entry ID; +- (for "restricted" discovery type:) RPAUID, UE Identity, Target PDUID, Application ID, Target RPAUID, Discovery Entry ID, + +**Input, Optional:** None, + +**Output, Required:** (for "open" discovery) ProSe Application Code(s)/Prefix, ProSe Application Mask(s), TTL; or (for "restricted" discovery) ProSe Restricted Code, validity timer + +**Output, Optional:** None. + +#### 7.1.2.5 N5g-ddnmf\_Discovery\_MonitorUpdate service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_MonitorUpdate + +**Description:** The consumer NF updates or revoke the authorization for the indicated UE to monitor in the PLMN. + +**Input, Required:** Discovery type ("open" or "restricted"); and + +- (for "open" discovery type:) ProSe Application ID name, UE Identity, TTL, Discovery Entry ID; +- (for "restricted" discovery type:) ProSe Restricted Code, Application ID, Banned RPAUID, Banned PDUID. + +**Input, Optional:** None. + +**Output, Required:** Result. + +**Output, Optional:** None. + +#### 7.1.2.6 N5g-ddnmf\_Discovery\_MonitorUpdateResult service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_MonitorUpdateResult + +**Description:** The consumer NF informs the 5G DDNMF of the monitoring revocation results. + +**Input, Required:** Discovery type = "restricted", ProSe Restricted Code, Application ID, Banned RPAUID, Banned PDUID, Result. + +**Input, Optional:** None. + +**Output, Required:** None. + +**Output, Optional:** None. + +#### 7.1.2.7 N5g-ddnmf\_Discovery\_DiscoveryAuthorize service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_DiscoveryAuthorize + +**Description:** The consumer NF obtains the authorization from the 5G DDNMF for a discoverer UE in the PLMN to operate Model B restricted discovery. + +**Input, Required:** Discovery type = "restricted", Restricted ProSe App User ID, UE Identity, Target PDUID, Application ID, Target RPAUID, Discovery Entry ID. + +**Input, Optional:** None. + +**Output, Required:** ProSe Query Code(s), ProSe Response Code, validity timer. + +**Output, Optional:** None. + +#### 7.1.2.8 N5g-ddnmf\_Discovery\_MatchReport service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_MatchReport + +**Description:** The consumer NF obtains the information about the indicated discovery code from the 5G DDNMF. + +**Input, Required:** Discovery type = "open", ProSe Application Code(s), UE identity, Monitored PLMN ID. + +**Input, Optional:** None. + +**Output, Required:** ProSe Application ID Name(s), validity timer(s). + +**Output, Optional:** Metadata, Metadata Index Mask(s). + +#### 7.1.2.9 N5g-ddnmf\_Discovery\_MatchInformation service operation + +**Service operation name:** N5g-ddnmf\_Discovery\_MatchInformation + +**Description:** The consumer NF receives from the 5G DDNMF of a matching result and the information can be used for charging purpose. + +**Input, Required:** Discovery type ("open" or "restricted"); and + +- (for "open" type:) ProSe Application ID(s), UE Identity; +- (for "restricted" type:) RPAUID, Target RPAUID, UE Identity, ProSe Restricted Code. + +**Input, Optional:** None. + +**Output, Required:** None. + +**Output, Optional:** None. + +## 7.2 AF Services + +### 7.2.1 General + +This service enables consumer NF to request authorization for Discovery Request. This service is also used by producer NF to update the authorization of discovery request. + +**Table 7.2.1-1: Services provided by AF** + +| Service Name | Service Operations | Operation Semantics | Example Consumer(s) | +|--------------|------------------------------------|---------------------|---------------------| +| Naf_ProSe | DiscoveryAuthorization | Request/Response | 5G DDNMF | +| | DiscoveryAuthorizationUpdateNotify | Subscribe/Notify | 5G DDNMF | +| | DiscoveryAuthorizationResultUpdate | Request/Response | 5G DDNMF | + +### 7.2.2 Naf\_ProSe service + +#### 7.2.2.1 General + +**Service description:** This service enables consumer NF to request authorization for Discovery Request. The AF may update the authorization information to revoke the Restricted ProSe Direct Discovery permission. + +### 7.2.2.2 Naf\_ProSe\_DiscoveryAuthorization service operation + +**Service operation name:** Naf\_ProSe\_DiscoveryAuthorization + +**Description:** Authorize Discovery Request from the consumer NF. + +**Input, Required:** ProSe Application ID, Request Type. + +**Input, Optional:** Application Level Container, Allowed number of suffixes, RPAUID, ProSe Application ID, Target RPAUID. + +**Output, Required:** ProSe Application Code Suffix pool, Response Type, PDUID(s), Target PDUID. + +**Output, Optional:** PDUID(s), Target PDUID, ProSe Application Code Suffix pool, Mask(s) for the ProSe Application Code Suffix(es) corresponding to ProSe Application ID, N sets of Target PDUID - Target RPAUID - Metadata Indicator, Application Level Container. + +### 7.2.2.3 Naf\_ProSe\_DiscoveryAuthorizationUpdateNotify service operation + +**Service operation name:** Naf\_ProSe\_DiscoveryAuthorizationUpdateNotify + +**Description:** The AF update the authorization information to revoke discovery permissions relating to some other users in the NF consumer. + +**Input, Required:** Discovery type = "restricted", RPAUID, Banned RPAUID, Banned PDUID. + +**Input, Optional:** None. + +**Output, Required:** Result. + +**Output, Optional:** None. + +### 7.2.2.4 Naf\_ProSe\_DiscoveryAuthorizationResultUpdate service operation + +**Service operation name:** Naf\_ProSe\_DiscoveryAuthorizationResultUpdate + +**Description:** The NF consumer informs the AF of the revocation result because of update in authorization information. + +**Input, Required:** Discovery type = "restricted", RPAUID, Banned RPAUID, Banned PDUID. + +**Input, Optional:** None. + +**Output, Required:** Result. + +**Output, Optional:** None. + +--- + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-03 | SA2#143e | | | | | Skeleton for this TS (approved in S2-2101633) | 0.0.0 | +| 2021-06 | SA#92-e | SP-210367 | - | - | - | MCC editorial update for presentation to TSG SA#92E for information | 1.0.0 | +| 2021-09 | SA#93-e | SP-210940 | - | - | - | MCC editorial update for presentation to TSG SA#92E for approval | 2.0.0 | +| 2021-09 | SA#93-e | - | - | - | - | MCC editorial update for publication after TSG SA#92E approval | 17.0.0 | +| 2021-12 | SA#94-e | SP-211281 | 0001 | - | F | EN resolution about U2N Relay reselection | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0002 | 1 | F | Correction on IP address allocation for U2N Relay | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0003 | 1 | F | Clarification on scope | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0004 | - | F | Correction to UE triggered Policy provisioning Procedure | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0005 | 1 | F | PC5 Discovery Model Selection | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0012 | 2 | F | Clarification for the PC5 QoS parameters and PC5 QoS rule | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0013 | 1 | F | Removing the EN of policy control for L3 U2N Relay | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0014 | 1 | F | N3IWF connection via data network | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0015 | 1 | F | Clarification on Parameters Provided by ProSe Application Server | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0016 | 1 | F | Clarification on Discovery Request Procedure | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0017 | - | F | Change ProSe Service Type to ProSe Identifier | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0018 | 1 | F | Clarification on Layer-2 Relay selection | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0019 | 4 | F | Clarification on Relay Discovery Additional Information message | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0020 | 1 | B | Identifiers for Layer-2 UE-to-Network Relay discovery | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0021 | 1 | B | Remove ENs on RAN2 dependency issues | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0022 | - | F | Mega Editorial CR on 5G ProSe | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0023 | 1 | F | DDNMF stack | 17.1.0 | +| 2021-12 | SA#94-e | SP-211281 | 0026 | 1 | F | Clarifications on QoS handling for L3 relay | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0029 | 1 | F | Corrections on 5G ProSe UE-to-Network Relay | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0030 | 1 | F | Corrections on ProSe Direct Discovery with 5G DDNMF | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0031 | 1 | F | PDU Session release for L3 U2N Relay on authorisation revocation | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0037 | 1 | F | Update to ProSe identifier definition | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0038 | 2 | F | Update to Groupcast mode 5G ProSe Direct Communication | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0039 | - | F | terminology correction | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0049 | 1 | F | Miscellaneous clarifications and corrections | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0050 | 1 | F | Clarification on the ID for Group discovery | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0051 | 1 | F | PC5 link release and CM state update for L2 U2N relay | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0054 | 1 | F | Updates and alignments based on further RAN2 feedback | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0055 | - | F | Update on Unicast link profile for UE-to-Network Relay | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0056 | 1 | F | Clarification on subscription information to 5G ProSe | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0057 | 1 | F | N3IWF connection via Dual PDU sessions | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0058 | 1 | F | Clarification about path selection policy | 17.1.0 | +| 2021-12 | SA#94-e | SP-211282 | 0059 | 1 | F | User Info ID clarifications | 17.1.0 | +| 2022-01 | - | - | 0020 | 1 | B | Correction of CR0020R1 implementation: Removal of editor's notes in clause 5.8.3.3 | 17.1.1 | +| 2022-03 | SA#95-e | SP-220050 | 0024 | 2 | B | DRX support for direct discovery and communication and L3 relay | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0060 | 1 | F | Clarification on QoS handling for Layer-3 Relay with N3IWF | 17.2.0 | +| 2022-03 | SA#95-e | SP-220354 | 0061 | 4 | F | Resolve EN for Mobility Restriction | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0063 | 1 | F | Capture the reference point of PKMF | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0064 | 1 | F | Resolve ENs for Security Parameters Provisioning | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0065 | - | F | High-level description of UE-to-Network Relay discovery | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0066 | 1 | F | Editorial fixes related to referred clauses | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0067 | 1 | F | Update to metadata in PC5 Direct Discovery message | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0070 | - | F | Removal of discovery range | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0072 | 1 | F | NAS message type determination | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0074 | 1 | F | User info in discovery message | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0075 | 1 | F | Handling on discovery and data associated to different L2 IDs | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0079 | 1 | F | Support of RAN Sharing for L2 Relay | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0080 | 1 | B | RSC Determination by a Layer-3 Remote UE | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0081 | 1 | B | Security procedures for L3 relaying | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0082 | 1 | F | Use of discovery Model A and Model B | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0086 | 1 | F | Clarification on privacy timer | 17.2.0 | +| 2022-03 | SA#95-e | SP-220050 | 0087 | 1 | F | Clarification on Remote UE providing QoS Info | 17.2.0 | +| 2022-03 | SA#95-e | SP-220354 | - | - | - | MCC implementation correction of CR0061R4 | 17.2.1 | +| 2022-06 | SA#96 | SP-220393 | 0088 | 1 | F | Clarify for security procedure for UE-to-Network Relaying | 17.3.0 | +| 2022-06 | SA#96 | SP-220393 | 0089 | 1 | F | Adding reference point between 5G PKMF and UDM | 17.3.0 | +| 2022-06 | SA#96 | SP-220393 | 0090 | 1 | F | Mobility restrictions for MCX cleanup | 17.3.0 | +| 2022-06 | SA#96 | SP-220393 | 0091 | 1 | F | Clarifications on PC5 DRX operations | 17.3.0 | +| 2022-06 | SA#96 | SP-220393 | 0093 | 1 | F | TAI delivery | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|----------------------------------------------------------------------------------------------------------------------------|---------------| +| 2022-06 | SA#96 | SP-220393 | 0094 | 1 | F | Remove ENs on Security Parameters Provisioning for UE-NW Relay | 17.3.0 | +| 2022-06 | SA#96 | SP-220393 | 0098 | 1 | F | Miscellaneous corrections and alignments | 17.3.0 | +| 2022-06 | SA#96 | SP-220393 | 0099 | - | F | Modify description in clause 4.3.9.3 | 17.3.0 | +| 2022-06 | SA#96 | SP-220393 | 0100 | 1 | F | Clarification on DRX handling for unicast communication procedures | 17.3.0 | +| 2022-06 | SA#96 | SP-220713 | 0102 | 7 | F | AMF and AUSF selection for CP authentication and authorisation | 17.3.0 | +| 2022-09 | SA#97E | SP-220773 | 0107 | 1 | F | CP and UP-based security procedures for 5G ProSe UE-to-Network Relay | 17.4.0 | +| 2022-09 | SA#97E | SP-220773 | 0109 | 1 | F | Clarification on a single L2 link between L2 remote UE and L2 U2N relay UE for supporting PDU sessions of the L2 remote UE | 17.4.0 | +| 2022-09 | SA#97E | SP-220773 | 0110 | 1 | F | Clarification on PDCP SDU Types | 17.4.0 | +| 2022-09 | SA#97E | SP-220773 | 0111 | - | F | SL DRX for L2 U2N Relay | 17.4.0 | +| 2022-09 | SA#97E | SP-220773 | 0114 | 1 | F | Updates to Policy/Parameter provisioning for CP authentication and authorisation | 17.4.0 | +| 2022-12 | SA#98E | SP-221065 | 0118 | 1 | F | Clarifications on PC5 DRX operations | 17.5.0 | +| 2022-12 | SA#98E | SP-221065 | 0119 | - | F | Add 5G DDNMF Address in Parameter Provisioning for 5G ProSe Direct Discovery | 17.5.0 | +| 2022-12 | SA#98E | SP-221065 | 0120 | 1 | F | Correction on PC5 link release indication | 17.5.0 | +| 2022-12 | SA#98E | SP-221082 | 0124 | 4 | B | Layer-2 link management over PC5 reference point for U2U Relay | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0125 | 2 | B | 5G ProSe Communication via U2U Relay | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0126 | 1 | B | QoS handling for U2U Relay | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0129 | 1 | B | Terms related to U2U relaying | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0130 | 2 | B | Introduction of UE-to-UE Relay | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0131 | 2 | B | UE-to-UE Relay Discovery | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0132 | 2 | B | Layer-3 UE-to-UE Relay Communication | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0135 | 3 | B | Support path switching for U2N relay | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0139 | 3 | B | Procedures for Communication Path Switching between Two UE-to-Network Relays | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0144 | 3 | B | 5G ProSe UE-to-UE Relay reference architecture | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0148 | 3 | B | 5G ProSe UE-to-UE Relay reselection | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0150 | 3 | B | UE-to-UE Relay with Integrated Discovery | 18.0.0 | +| 2022-12 | SA#98E | SP-221082 | 0155 | 5 | B | 5.2.X 5G ProSe UE-to-UE Relay Discovery | 18.0.0 | +| 2023-03 | SA#99 | SP-230036 | 0157 | - | A | Removal of ProSe policy request during registration procedure | 18.1.0 | +| 2023-03 | SA#99 | SP-230036 | 0159 | - | A | Dedicated DNN for 5G ProSe L3 UE-to-Network Relay connectivity without N3IWF | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0161 | 1 | B | 5G ProSe Layer-3 UE-to-UE Relay Communication for Non-IP Traffic | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0162 | 5 | B | Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) | 18.1.0 | +| 2023-03 | SA#99 | SP-230081 | 0164 | - | B | IPv6 prefix delegation in 5GS | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0168 | 1 | B | Authorization information about multi-path transmission for L2 Remote UE | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0169 | 13 | B | Path switching between PC5 path and Uu path | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0170 | 1 | B | RSC for UE-to-UE relaying | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0172 | 1 | B | Layer-2 link management for 5G ProSe UE-to-UE Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0173 | 1 | C | Update for 5G ProSe UE-to-UE Relay Communication with integrated Discovery | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0174 | 1 | B | Identifiers for 5G ProSe UE-to-UE Relay Discovery | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0175 | 1 | B | Identifiers for Discovery integrated into PC5 unicast link establishment | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0177 | 1 | B | Path switching between direct and indirect path for Layer-2 UE-to-Network Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0180 | 1 | C | Update on path switching between different U2N relays | 18.1.0 | +| 2023-03 | SA#99 | SP-230036 | 0185 | 1 | A | Default configuration for ProSe Policy/Parameter | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0186 | - | B | Updates to U2U relay link management | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0195 | 1 | B | Protocol Stacks for 5G ProSe UE-to-UE Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0196 | 3 | B | 5G ProSe Remote UE traffic handling for multipath transmission via Layer-3 UE-to-Network Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230047 | 0201 | 4 | B | Update on UE-to-UE Relay reselection | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0202 | 1 | B | Support of UE-to-UE Relay operation during ProSe Direct Discovery | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0205 | 1 | B | Authorization and Provisioning for 5G ProSe UE-to-UE Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0208 | 1 | B | Link Management over PC5 reference point for 5G ProSe UE-to-UE Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230036 | 0211 | 1 | A | Alignment on Remote User ID for L3 U2N Relay w/o N3IWF | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0212 | 1 | B | IP address allocation for communication with a 5G ProSe Layer-3 UE-to-UE Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230036 | 0214 | 1 | A | Clarification of out-of-coverage operation R18 | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0215 | 1 | F | Clarification of out-of-coverage operation for U2U Relays | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0216 | 2 | B | Support of multi-path transmission for U2N Relay (KI#5): structure for high level description and procedures | 18.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|--------------------------------------------------------------------------------------------|--------| +| 2023-03 | SA#99 | SP-230048 | 0218 | 2 | C | Link sharing for UE-to-UE Relay with Integrated Discovery | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0224 | 1 | B | General description of 5G ProSe UE-to-UE Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0225 | 1 | B | Principles for applying parameters for 5G ProSe UE-to-UE Relay | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0226 | 1 | F | Correction on Procedure for 5G ProSe UE-to-UE Relay Discovery with Model A | 18.1.0 | +| 2023-03 | SA#99 | SP-230048 | 0227 | 1 | F | Clarification on Path switching between PC5 path and Uu path | 18.1.0 | +| 2023-06 | SA#100 | SP-230449 | 0141 | 10 | B | Support of Public Warning Notification Relaying by 5G ProSe UE-to-Network Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230448 | 0235 | 1 | A | Correction to the way that security function is described | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0236 | 4 | F | Update to 5G ProSe Layer-3 UE-to-UE Relay Communication for Ethernet Traffic | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0237 | 1 | F | KI#5 Resolve EN for authorization of multi-path via Uu and via L3 U2N Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0238 | 1 | F | KI#5 Resolve EN for term of multi-path via Uu and via U2N Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0240 | 1 | F | ENs resolution for path switching between PC5 path and Uu path | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0242 | 1 | B | Resolve EN on parameter provisioning for U2U Relay communication with integrated discovery | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0243 | 1 | B | Update of U2U Relay Communication with integrated Discovery procedure | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0248 | - | F | Provisioning for traffic type of L3 U2U Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0249 | 1 | F | Emergency Priority Handling for 5G ProSe Layer-3 Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0250 | 1 | F | Indication of Support for Emergency Relaying | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0252 | 1 | F | Emergency service via N3IWF | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0253 | 1 | F | Alignment of policy for U2U and Direct Discovery and Communication | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0255 | 2 | F | Clarification of multi-path communication | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0256 | 3 | B | Update of U2U Relay discovery to support negotiated Relay reselection | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0259 | 3 | F | Update on emergency service over U2N Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0261 | - | B | U2U relay capabilities and subscription | 18.2.0 | +| 2023-06 | SA#100 | SP-230449 | 0264 | 3 | B | KI#7_IP address allocation by Layer 3 Relay UE for emergency service | 18.2.0 | +| 2023-06 | SA#100 | SP-230448 | 0266 | 1 | A | Catch all entry for discovery | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0270 | - | B | MA PDU Session in multi-path transmission for L3 U2N Relay with N3IWF | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0272 | 1 | B | Clarification on 5G ProSe UE-to-Network Relay Reselection and Path Switching | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0273 | 1 | F | Clarification on AF-based Service Parameter Provisioning | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0276 | 1 | F | PLMN selection for L2 remote UE for emergency service | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0277 | 3 | F | DNN for emergency service | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0279 | 1 | B | Link Modification Procedure with L3 UE-to-UE Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0286 | 1 | F | Clarification of 5G ProSe UE-to-UE Relay reselection | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0288 | 2 | F | Layer-3 U2U Relay link release and maintenance procedures | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0292 | 2 | F | Clarification on QoS handling for 5G ProSe Layer-3 UE-to-UE Relay | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0302 | 2 | F | L2 Remote UE RRC Establishment Cause | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0303 | - | F | Use of emergency RSC | 18.2.0 | +| 2023-06 | SA#100 | SP-230450 | 0304 | - | F | Adding new PQIs to support path switching between PC5 and Uu | 18.2.0 | +| 2023-09 | SA#101 | SP-230840 | 0306 | 1 | F | ProSe Authorization info for Layer-2 U2U Relay operation | 18.3.0 | +| 2023-09 | SA#101 | SP-230832 | 0311 | 1 | A | Reference point alignment with TS33.503 | 18.3.0 | +| 2023-09 | SA#101 | SP-230840 | 0313 | 2 | F | Clarification on 5G ProSe UE-to-UE Relay Discovery with Model A | 18.3.0 | +| 2023-09 | SA#101 | SP-230840 | 0315 | 2 | F | Modification on Relay Discovery Additional Information Message | 18.3.0 | +| 2023-09 | SA#101 | SP-230840 | 0322 | 2 | F | Clarification on 5G ProSe UE-to-UE Relay Discovery | 18.3.0 | +| 2023-09 | SA#101 | SP-230840 | 0329 | 2 | F | U2U relay authorization updates | 18.3.0 | +| 2023-09 | SA#101 | SP-230840 | 0334 | 1 | F | Clarification on RSC usage during relay discovery and relay reselection | 18.3.0 | +| 2023-09 | SA#101 | SP-230840 | 0338 | - | F | Clarifications on U2U Relay reselection relay discovery | 18.3.0 | +| 2023-09 | SA#101 | SP-230840 | 0348 | 1 | F | Corrections on procedures for 5G ProSe UE-to-UE Relay Discovery | 18.3.0 | +| 2023-12 | SA#102 | SP-231247 | 0321 | 6 | F | Corrections to UE-to-UE Relay Discovery | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0330 | 3 | F | U2U relay features complement | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0331 | 3 | F | Multi-path communication complement | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0335 | 3 | F | Clarifications on U2U Relay and message handling | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0336 | 3 | F | Clarifications on Relay discovery for emergency service | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0341 | 4 | F | Relay UE requirement to forward PWS messages | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0350 | - | F | Clarification on Layer-2 link management on UE-to-UE Relay | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0352 | 3 | F | Update Terminologies | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0355 | 1 | F | Correction on Layer-2 U2U Relay Communication with integrated Discovery | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0356 | 1 | F | Correction on Layer-3 U2U Relay link identifier update procedure | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0358 | 1 | F | Removal of ENs having RAN dependency | 18.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------|--------| +| 2023-12 | SA#102 | SP-231247 | 0359 | 1 | F | Support for U2U Relay for UEs in limited service state | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0362 | - | F | Correction on link-local IPv6 address in DCA message | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0364 | 1 | F | Issue on U2U relay reselection triggered by PC5 RLF or PC5 link release | 18.4.0 | +| 2023-12 | SA#102 | SP-231248 | 0369 | 1 | F | Fixing reference and editorial errors | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0375 | 2 | F | Clarification on RSC and Target Info matching | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0376 | 2 | F | Correction on relay Indication | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0377 | 1 | F | Resolve the EN on PC5 Security Used for Emergency Services | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0381 | 1 | F | Parameter update for Link Modification with L3 U2U Relay | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0382 | 2 | F | Correction on UE-to-UE Relay discovery procedures | 18.4.0 | +| 2023-12 | SA#102 | SP-231247 | 0401 | 2 | F | Rejection of L3 U2U Connection Setup when Ethernet MAC address conflict is detected | 18.4.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23316/raw.md b/raw/rel-18/23_series/23316/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..aef20ede49f2bba05cb56bc13520a7482665a2ef --- /dev/null +++ b/raw/rel-18/23_series/23316/raw.md @@ -0,0 +1,3605 @@ + + +# 3GPP TS 23.316 V18.4.0 (2023-12) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Wireless and wireline convergence access support for the 5G System (5GS) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations ..... | 10 | +| 4 High level features ..... | 11 | +| 4.1 General ..... | 11 | +| 4.2 Network Access Control ..... | 11 | +| 4.2.0 General ..... | 11 | +| 4.2.1 Network selection..... | 11 | +| 4.2.2 Identification and authentication ..... | 11 | +| 4.2.3 Authorisation ..... | 12 | +| 4.2.4 Access control and barring ..... | 12 | +| 4.2.5 Policy control..... | 12 | +| 4.2.6 Lawful Interception ..... | 12 | +| 4.3 Registration and Connection Management ..... | 12 | +| 4.3.1 Registration management ..... | 12 | +| 4.3.2 Connection management ..... | 12 | +| 4.3.3 Mobility Restrictions..... | 13 | +| 4.3.3.1 General..... | 13 | +| 4.3.3.2 Management of Forbidden Area in wireline access..... | 13 | +| 4.3.3.3 Management of Service Area Restrictions in wireline access ..... | 13 | +| 4.4 Session management..... | 14 | +| 4.4.0 General ..... | 14 | +| 4.4.1 Session management for 5G-RG ..... | 14 | +| 4.4.2 Session management for FN-RG..... | 14 | +| 4.5 QoS model..... | 15 | +| 4.5.0 General overview..... | 15 | +| 4.5.1 Wireline access specific 5G QoS parameters ..... | 16 | +| 4.5.1.0 Overview..... | 16 | +| 4.5.1.1 Void ..... | 16 | +| 4.5.1.2 RG Level Wireline Access Characteristics..... | 16 | +| 4.5.2 QoS model applied to FN-RG ..... | 16 | +| 4.5.3 Differentiated QoS for devices behind 5G-RG ..... | 17 | +| 4.6 User Plane management..... | 17 | +| 4.6.1 General ..... | 17 | +| 4.6.2 IP address allocation..... | 17 | +| 4.6.2.1 General..... | 17 | +| 4.6.2.2 IPv6 Address Allocation using DHCPv6..... | 18 | +| 4.6.2.3 IPv6 Prefix Delegation via DHCPv6 ..... | 18 | +| 4.6.2.4 The procedure of Stateless IPv6 Address Autoconfiguration..... | 18 | +| 4.6.3 Packet Detection Rule ..... | 19 | +| 4.6.4 Forwarding Action Rule ..... | 19 | +| 4.6.5 Usage Reporting Rule..... | 19 | +| 4.6.6 Usage of N4 to support IPTV ..... | 20 | +| 4.7 Identifiers ..... | 20 | +| 4.7.1 General ..... | 20 | +| 4.7.2 SUPI and SUCI for 5G-BRG support ..... | 21 | +| 4.7.3 SUPI and SUCI for FN-BRG support ..... | 21 | +| 4.7.4 SUPI and SUCI for 5G-CRG and FN-CRG support ..... | 21 | +| 4.7.5 Line ID..... | 21 | +| 4.7.6 HFC identifier..... | 21 | +| 4.7.7 PEI ..... | 22 | +| 4.7.8 Global Line Identifier ..... | 22 | + +| | | | +|----------|--------------------------------------------------------------------------------------|----| +| 4.7.9 | Global Cable Identifier ..... | 22 | +| 4.7.10 | RAT types dedicated for Wireline access..... | 23 | +| 4.7.11 | SUPI and SUCI for N5GC device or AUN3 device support..... | 23 | +| 4.8 | Security aspects..... | 23 | +| 4.9 | Support of specific services..... | 23 | +| 4.9.0 | General ..... | 23 | +| 4.9.1 | IPTV ..... | 23 | +| 4.10 | UE behind 5G-RG and FN-RG ..... | 23 | +| 4.10a | Non-5G capable device behind 5G-CRG and FN-CRG ..... | 25 | +| 4.10b | Differentiated services for NAUN3 devices behind 5G-RG..... | 27 | +| 4.10c | Authenticable Non-3GPP devices behind 5G-RG ..... | 28 | +| 4.10d | Support of NSWO for 3GPP UE behind a RG..... | 29 | +| 4.11 | Fixed Wireless Access ..... | 29 | +| 4.12 | Hybrid Access ..... | 30 | +| 4.12.1 | General ..... | 30 | +| 4.12.2 | Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN..... | 30 | +| 4.12.3 | Hybrid Access with multi-access connectivity over E-UTRAN/EPC and W-5GAN ..... | 31 | +| 4.12.3.1 | General ..... | 31 | +| 4.12.3.2 | Void ..... | 31 | +| 4.12.3.3 | Void ..... | 31 | +| 4.13 | Support of FN-RG..... | 31 | +| 4.14 | Support of slicing ..... | 32 | +| 4.15 | Support for IMS services..... | 32 | +| 4.16 | Access to non-public networks via wireline access network ..... | 32 | +| 4.16.1 | Access to SNPN services via wireline access network ..... | 32 | +| 4.16.2 | Access to Public Network Integrated NPN services via wireline access network ..... | 33 | +| 5 | Network Function ..... | 33 | +| 5.0 | General ..... | 33 | +| 5.1 | Network Function Functional description..... | 33 | +| 5.1.1 | W-AGF ..... | 33 | +| 6 | Control and User Plane Protocol Stacks ..... | 34 | +| 6.1 | General ..... | 34 | +| 6.2 | Control Plane Protocol Stacks for W-5GAN ..... | 34 | +| 6.2.1 | Control Plane Protocol Stacks between the 5G-RG and the 5GC..... | 34 | +| 6.2.2 | Control Plane Protocol Stacks between the FN-RG and the 5GC..... | 35 | +| 6.3 | User Plane Protocol Stacks for W-5GAN ..... | 35 | +| 6.3.1 | User Plane Protocol Stacks between the 5G-RG and the 5GC..... | 35 | +| 6.3.2 | User Plane Protocol Stacks between the FN-RG and the 5GC ..... | 36 | +| 7 | System procedure ..... | 36 | +| 7.1 | General ..... | 36 | +| 7.2 | Connection, Registration and Mobility Management procedures..... | 36 | +| 7.2.1 | Registration Management procedures ..... | 37 | +| 7.2.1.1 | 5G-RG Registration via W-5GAN ..... | 37 | +| 7.2.1.2 | 5G-RG Deregistration via W-5GAN ..... | 40 | +| 7.2.1.3 | FN-RG Registration via W-5GAN ..... | 41 | +| 7.2.1.4 | FN-RG Deregistration via W-5GAN ..... | 43 | +| 7.2.2 | Service Request procedures..... | 43 | +| 7.2.2.1 | 5G-RG Service Request procedure via W-5GAN Access..... | 43 | +| 7.2.2.2 | FN-RG Service Request procedure via W-5GAN Access..... | 45 | +| 7.2.3 | 5G-RG and FN-RG Configuration Update..... | 47 | +| 7.2.3.0 | General ..... | 47 | +| 7.2.3.1 | 5G-RG Configuration Update via W-5GAN Access..... | 47 | +| 7.2.3.2 | FN-RG related Configuration Update via W-5GAN Access..... | 49 | +| 7.2.4 | Reachability procedures ..... | 51 | +| 7.2.5 | AN Release ..... | 51 | +| 7.2.5.1 | General ..... | 51 | +| 7.2.5.2 | 5G-RG AN Release via W-5GAN..... | 51 | +| 7.2.5.3 | FN-RG AN Release via W-5GAN..... | 53 | +| 7.2.6 | N2 procedures..... | 53 | +| 7.2.6.0 | General ..... | 53 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------------------|----| +| 7.2.6.1 | N2 procedures via W-5GAN Access ..... | 53 | +| 7.2.7 | 5G-RG and FN-RG Capability Match Request procedure..... | 54 | +| 7.2.8 | Connection, Registration and Mobility Management procedures for AUN3 devices..... | 54 | +| 7.2.8.1 | AUN3 device Registration via W-5GAN ..... | 54 | +| 7.2.8.2 | AUN3 device De-registration via W-5GAN ..... | 56 | +| 7.2.8.3 | 5G-RG Deregistration via W-5GAN when it is also serving AUN3 devices..... | 58 | +| 7.2.8.4 | N2 release related with a 5G-RG also serving AUN3 devices ..... | 59 | +| 7.3 | Session Management procedures ..... | 59 | +| 7.3.0 | General ..... | 59 | +| 7.3.1 | 5G-RG Requested PDU Session Establishment via W-5GAN ..... | 59 | +| 7.3.1.1 | 5G-RG PDU Session establishment via W-5GAN..... | 59 | +| 7.3.1.2 | PDU Session Establishment with ACS Discovery ..... | 60 | +| 7.3.2 | 5G-RG or Network Requested PDU Session Modification via W-5GAN..... | 61 | +| 7.3.3 | 5G-RG or Network Requested PDU Session Release via W-5GAN ..... | 62 | +| 7.3.4 | FN-RG related PDU Session Establishment via W-5GAN..... | 64 | +| 7.3.5 | CN-initiated selective deactivation of UP connection of an existing PDU Session associated with W-5GAN Access ..... | 65 | +| 7.3.6 | FN-RG or Network Requested PDU Session Modification via W-5GAN ..... | 66 | +| 7.3.7 | FN-RG or Network Requested PDU Session Release via W-5GAN ..... | 66 | +| 7.3.8 | Session Management Procedures for AUN3 devices ..... | 66 | +| 7.3.8.1 | PDU Session Establishment of AUN3 device behind 5G-RG ..... | 66 | +| 7.3.8.2 | PDU Session Modification of AUN3 device behind 5G-RG ..... | 67 | +| 7.3.8.3 | PDU Session Release of AUN3 device behind 5G-RG..... | 67 | +| 7.4 | SMF and UPF interactions ..... | 67 | +| 7.5 | User Profile management procedures ..... | 67 | +| 7.6 | Handover procedure ..... | 68 | +| 7.6.1 | General ..... | 68 | +| 7.6.2 | Handover within NG-RAN..... | 68 | +| 7.6.3 | Handover procedures between 3GPP access / 5GC and W-5GAN access..... | 68 | +| 7.6.3.1 | Handover of a PDU Session procedure from W-5GAN access to 3GPP access ..... | 68 | +| 7.6.3.2 | Handover of a PDU Session procedure from 3GPP to W-5GAN access ..... | 69 | +| 7.6.4 | Handover procedures between 3GPPaccess / EPS and W-5GAN/5GC access ..... | 69 | +| 7.6.4.1 | Handover from 3GPP access / EPS to W-5GAN / 5GC ..... | 69 | +| 7.6.4.2 | Handover from W-5GAN / 5GC access to 3GPP-access / EPS ..... | 70 | +| 7.7 | Support of specific services..... | 70 | +| 7.7.0 | General ..... | 70 | +| 7.7.1 | IPTV ..... | 70 | +| 7.7.1.1 | Overview..... | 70 | +| 7.7.1.1.1 | Registration and PDU Session Establishment procedure for IPTV ..... | 71 | +| 7.7.1.1.2 | IPTV Access procedure..... | 72 | +| 7.7.1.1.3 | Unicast/Multicast Packets transmission procedure..... | 72 | +| 7.7.1.1.4 | AF request to provision Multicast Access Control List information into UDR..... | 74 | +| 8 | Network Function services..... | 75 | +| 8.0 | General ..... | 75 | +| 8.1 | UDM Services ..... | 76 | +| 8.1.1 | Nudm_SubscriberDataManagement (SDM) Service ..... | 76 | +| 8.1.1.1 | General ..... | 76 | +| 8.2 | Void..... | 76 | +| 8.3 | BSF Services ..... | 76 | +| 8.3.1 | General ..... | 76 | +| 8.4 | PCF Services ..... | 76 | +| 8.4.1 | General ..... | 76 | +| 8.4.2 | Npcf_SMPolicyControl ..... | 76 | +| 8.4.3 | Npcf_AMPolicyControl ..... | 77 | +| 8.4.3.1 | Npcf_AMPolicyControl_Create service operation..... | 77 | +| 8.4.3.2 | Npcf_AMPolicyControl_Update service operation..... | 77 | +| 8.5 | Nnef_IPTVconfiguration service ..... | 77 | +| 8.5.1 | General ..... | 77 | +| 8.5.2 | Nnef_IPTVconfiguration_Create operation ..... | 77 | +| 8.5.3 | Nnef_IPTVconfiguration_Update operation ..... | 78 | +| 8.5.4 | Nnef_IPTVconfiguration_Delete operation ..... | 78 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------|-----------| +| 8.6 | UDR Services..... | 78 | +| 8.6.1 | Nudr_DataManagement (DM) Service ..... | 78 | +| 8.6.1.1 | General..... | 78 | +| 9 | Policy and Charging Control Framework and Configuration by ACS ..... | 79 | +| 9.0 | General ..... | 79 | +| 9.1 | Session management related policy control..... | 79 | +| 9.1.0 | General ..... | 79 | +| 9.1.1 | Session binding..... | 79 | +| 9.1.2 | Policy Control Request Triggers relevant for SMF and wireline access type..... | 79 | +| 9.2 | Network Functions and entities..... | 80 | +| 9.2.1 | General ..... | 80 | +| 9.2.2 | Policy Control Function (PCF)..... | 80 | +| 9.2.3 | Session Management Function (SMF) ..... | 80 | +| 9.2.4 | Application Function (AF) ..... | 81 | +| 9.2.5 | Access and Mobility Management Function (AMF)..... | 81 | +| 9.3 | Policy and charging control rule ..... | 81 | +| 9.3.1 | PCC rule information to support IPTV service ..... | 81 | +| 9.4 | PDU Session related policy information..... | 81 | +| 9.5 | Non-session management related policy information..... | 82 | +| 9.5.1 | Access and mobility related policy information..... | 82 | +| 9.5.2 | UE access selection and PDU Session selection related policy information ..... | 83 | +| 9.5.2.1 | 5G-RG..... | 83 | +| 9.5.2.2 | FN-RG ..... | 84 | +| 9.5.3 | Policy Control Request Triggers relevant for AMF and wireline access type ..... | 85 | +| 9.6 | Configuration and Management from ACS ..... | 85 | +| 9.6.1 | General ..... | 85 | +| 9.6.2 | ACS Discovery ..... | 85 | +| 9.6.3 | ACS Information Configuration by the 3rd party ..... | 86 | +| 9.6.4 | URSP for FN RG..... | 87 | +| 9.7 | new PCRT (Policy Control Request Trigger) ..... | 87 | +| 9.8 | AF-based service parameter provisioning for TNAP ID ..... | 87 | +| 9.9 | Policy control subscription information management ..... | 88 | +| 10 | Support of additional functionalities..... | 88 | +| 10.0 | General ..... | 88 | +| 10.1 | User Location Information ..... | 88 | +| Annex A (informative): | UE behind RG using untrusted Non-3GPP access procedures..... | 89 | +| Annex B (informative): | Support for differentiated charging and QoS for UEs behind RG..... | 91 | +| Annex C (informative): | Change history..... | 92 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the enhancements to Stage 2 system architecture, procedure and flows, Policy and Charging Control for the 5G System defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] in order to support wireline access network and Fixed Wireless Access. The specifications defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] apply to the wireline access network and Fixed Wireless Access. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G system, Stage 2". +- [4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System". +- [5] BBF TR-124 issue 5: "Functional Requirements for Broadband Residential Gateway Devices". +- [6] BBF TR-101 issue 2: "Migration to Ethernet-Based Broadband Aggregation". +- [7] BBF TR-178 issue 1: "Multi-service Broadband Network Architecture and Nodal Requirements". +- [8] CableLabs DOCSIS MULPI: "Data-Over-Cable Service Interface Specifications DOCSIS 3.1, MAC and Upper Layer Protocols Interface Specification". +- [9] BBF TR-456 issue 2: "AGF Functional Requirements". +- [10] BBF WT-457: "FMIF Functional Requirements". + +NOTE: Technical Report of BBF WT-457 will be TR-457 which will be available when finalized by BBF. + +- [11] 3GPP TS 33.501: "Security architecture and procedures for 5G System". +- [12] BBF TR-177 Issue 1 Corrigendum 1: "IPv6 in the context of TR-101". +- [13] IETF RFC 6788: "The Line-Identification Option". +- [14] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [15] Void. +- [16] IETF RFC 6603: "Prefix Exclude Option for DHCPv6-based Prefix Delegation". +- [17] Void. +- [18] BBF TR-069: "CPE WAN Management Protocol". +- [19] BBF TR-369: "User Services Platform (USP)". +- [20] IETF RFC 3046: "DHCP Relay Agent Information Option". + +- [21] IETF RFC 4604: "Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast". +- [22] 3GPP TR 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [23] 3GPP TS 38.413: "NG RAN; NG Application Protocol (NGAP)". +- [24] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [25] 3GPP TS 22.011: "Service accessibility". +- [26] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [27] CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture". +- [28] IETF RFC 3376: "Internet Group Management Protocol, Version 3". +- [29] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS)". +- [30] BBF TR-198: "DQS:DQM systems functional architecture and requirements". +- [31] 3GPP TS 23.203: "Policy and charging control architecture". +- [32] 3GPP TS 33.126: "Lawful Interception Requirements". +- [33] IETF RFC 2236: "Internet Group Management Protocol, Version 2". +- [34] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)". +- [35] IETF RFC 1112: "Internet Group Management Protocol". +- [36] IETF RFC 2710: "Multicast Listener Discovery Version for IPv6". +- [37] IETF RFC 2010: "Operational Criteria for Root Name Servers". +- [38] BBF TR-470: "5G FMC architecture". +- [39] 3GPP TS 29.519: "Policy Data, Application Data and Structured Data for exposure". +- [40] 3GPP TS 23.041: "Public Warning System". +- [41] IEEE Publication (2017): "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)". +. +- [42] 3GPP TS 29.413: "Application of the NG Application Protocol (NGAP) to non-3GPP access". +- [43] Void. +- [44] 3GPP TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks". +- [45] 3GPP TS 23.402: " Architecture enhancements for non-3GPP accesses". +- [46] BBF TR-181: "Device Data Model for TR-069". +- [47] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] apply. A term defined in TS 23.501 [2], TS 23.502 [3] or TS 23.503 [4] takes precedence over the definition of the same term, if any, in any other specifications. + +**RG Level Wireline Access Characteristics:** Wireline access technology specific QoS information corresponding to a specific wireline access subscription, which is provided by the AMF to the W-AGF at RG registration. + +**Wireline access Control Plane protocol (W-CP):** Protocol used to transport AS and NAS signalling between the 5G-RG and the W-AGF over the Y4 reference point. W-CP is specified by BBF and CableLabs. There is no assumption that W-CP refers to only a single protocol or only a specific protocol layer. + +**Wireline access User Plane protocol (W-UP):** Protocol used to carry PDU Session user plane traffic between the 5G-RG and the W-AGF over the Y4 reference point. W-UP is specified by BBF and CableLabs. There is no assumption that W-UP refers to only a single protocol or only a specific protocol layer. + +**Legacy Wireline access Control Plane protocol (L-W-CP):** L-W-CP is a legacy control plane protocol between the FN-RG and W-AGF. L-W-CP is specified by BBF and CableLabs. There is no assumption that L-W-CP refers to only a single protocol or only a specific protocol layer. + +**Legacy Wireline access User Plane protocol (L-W-UP):** L-W-UP is a legacy user plane protocol between the FN-RG and W-AGF. W-UP is specified by BBF and CableLabs. There is no assumption that L-W-UP refers to only a single protocol or only a specific protocol layer. + +**Authenticable Non-3GPP (AUN3) device:** A device that does not support NAS signalling, is connected to 5GC via a RG and can be authenticated by 5GC over the RG. + +5GS specifications do not support a device using the same subscription to access 5GS as a UE and as an AUN3 device. + +**Non-Authenticable Non-3GPP (NAUN3) device:** A device that does not support NAS signalling, is connected to 5GC via a RG and for which authentication with 5GC is not supported. + +NOTE 1: AUN3 and NAUN3 device can connect to RG through WLAN (collocated or not collocated with the RG) and/or wired Ethernet connections. + +NOTE 2: A device can operate as a UE over NG-RAN and as a AUN3 or NAUN3 via a RG, if the device implements UE functionality. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] apply. An abbreviation defined in TS 23.501 [2], TS 23.502 [3] or TS 23.503 [4] takes precedence over the same abbreviation, if any, in any other specifications. + +| | | +|---------|-----------------------------------------------| +| 5G-RG | 5G Residential Gateway | +| 5G-BRG | 5G Broadband Residential Gateway | +| 5G-CRG | 5G Cable Residential Gateway | +| ACS | Auto-Configuration Server | +| FN-RG | Fixed Network RG | +| FN-BRG | Fixed Network Broadband RG | +| FN-CRG | Fixed Network Cable RG | +| FWA | Fixed Wireless Access | +| IGMP | Internet Group Management Protocol | +| L-W-CP | Legacy Wireless access Control Plane Protocol | +| L-W-UP | Legacy Wireless access User Plane Protocol | +| MLD | Multicast Listener Discovery | +| RG | Residential Gateway | +| RG-LWAC | RG Level Wireline Access Characteristics | + +| | | +|---------|----------------------------------------| +| SNPN | Stand-alone Non Public Network | +| USP | User Services Platform | +| W-5GAN | Wireline 5G Access Network | +| W-5GCAN | Wireline 5G Cable Access Network | +| W-5GBAN | Wireline BBF Access Network | +| W-CP | Wireline access Control Plane protocol | +| W-UP | Wireline access User Plane protocol | + +# --- 4 High level features + +This clause specifies high level description equivalent to TS 23.501 [2]. + +## 4.1 General + +The roaming support for W-5GAN access is not specified in this release. + +The usage of Trusted or Untrusted access to 5GC by a 5G-RG or by a FN RG is not applicable. + +## 4.2 Network Access Control + +### 4.2.0 General + +This clause specifies the delta related to network access control defined in TS 23.501 [2] clause 5.2. + +### 4.2.1 Network selection + +In the case of 5G-RG or FN-RG connected via W-5GAN the PLMN selection specification defined in TS 22.011 [25] and in TS 23.122 [26] and the SNPN selection specification defined in TS 24.502 [44] is not applicable. The HPLMN is implicitly selected by wired physical connectivity between 5G-RG or FN-RG and W-AGF. + +NOTE 1: The 5G-RG or FN-RG can only connect to a single physical wired access W-5GAN to a W-AGF configured at line provisioning by the operator, in addition no PLMN information is advertised by AS protocols in W-5GAN, since the Network selection feature is not supported. + +The roaming scenario is not supported in this Release of the specification. + +In the case of 5G-RG connected via FWA TS 23.501 [2] clause 5.2.2 applies with the following difference: + +- The PLMN selection defined in TS 22.011 [25] and in TS 23.122 [26] applies with the UE replaced by 5G-RG. + +### 4.2.2 Identification and authentication + +In the case of 5G-RG connected via W-5GAN or FWA, the specification defined in TS 23.501 [2] clause 5.2.3 applies with the following difference: + +- UE is replaced by 5G-RG. + +In the case of FN-RG connected via W-5GAN, the specification defined in TS 23.501 [2] clause 5.2.3 applies with the following differences: + +- UE is replaced by FN-RG. +- The W-AGF provides the NAS signalling connection to the 5GC on behalf of the FN-RG. +- The W-5GAN may authenticate the FN-RG per BBF specification BBF TR-456 [9] and WT-457 [10]. The W-5GAN may authenticate the FN-CRG per CableLabs DOCSIS MULPI [8]. + +### 4.2.3 Authorisation + +In the case of 5G-RG connected via W-5GAN or FWA, the specification defined in TS 23.501 [2] clause 5.2.4 applies with the following differences: + +- UE is replaced by 5G-RG. + +In the case of FN-RG connected via W-5GAN, the specification defined in TS 23.501 [2] clause 5.2.4 applies with the following differences: + +- UE is replaced by FN-RG. +- W-AGF performs the UE Registration procedure on behalf of the FN-RG. + +### 4.2.4 Access control and barring + +In the case of 5G-RG or FN-RG connected via W-5GAN the Access Control and Barring defined in TS 23.501 [2] clause 5.2.5 is not applicable. + +In the case of 5G-RG connected via FWA the specification defined in TS 23.501 [2] clause 5.2.5 applies with the following difference: + +- UE is replaced by 5G-RG. + +### 4.2.5 Policy control + +Policy control is specified in clause 9. + +### 4.2.6 Lawful Interception + +In the case of 5G-RG connected via FWA the specification defined in TS 23.501 [2] clause 5.2.7 applies with the following difference: + +- UE is replaced by 5G-RG. + +In the case of 5G-RG connected via W-5GAN, the definition and functionality of Lawful Interception defined in TS 33.126 [32] applies with the following difference: + +- UE is replaced by 5G-RG. + +In the case of FN-RG connected via W-5GAN, the definition and functionality of Lawful Interception defined in TS 33.126 [32] applies with the following difference: + +- UE is replaced by FN-RG, with e.g. the difference that FN-RG may not have a globally unique PEI (as described in clause 4.7.7) and does not hold any 3GPP-based subscriber credentials or subscriber identity information. + +## 4.3 Registration and Connection Management + +### 4.3.1 Registration management + +Registration management when 5G-RG or FN-RG is connected to 5GC via wireline access is described in TS 23.501 [2] clause 5.5.1. + +Registration management when 5G-RG is connected to 5GC via NG RAN access is described in TS 23.501 [2], clause 5.3.2. + +### 4.3.2 Connection management + +Connection management when 5G-RG or FN-RG is connected to 5GC via wireline access is described in clause 5.5.2 of TS 23.501 [2]. + +Connection management when 5G-RG is connected to 5GC via NG RAN access is described in clause 5.3.3 of TS 23.501 [2]. + +### 4.3.3 Mobility Restrictions + +#### 4.3.3.1 General + +Mobility Restrictions restrict service access of an 5G-RG depending on RG location. + +For a 5G-RG connecting over NG-RAN, the Mobility Restriction functionality as described in clause 5.3.4.1 of TS 23.501 [2] applies. + +For an 5G-RG connecting over wireline access, the Mobility Restriction functionality is described in this clause. + +Mobility restrictions do not apply to scenarios with FN-BRG. + +NOTE 1: Since access to 5GC for FN-BRG subscriptions are identified by a SUPI determined from the GLI as described in clause 4.7.3 and clause 4.7.8. Such subscriptions are by definition restricted to a specific location. + +NOTE 2: For FN-CRG subscriptions, HFC Node ID is used to identify the location of FN-CRG, thus service area restrictions for the FN-CRG can be identified by an HFC\_Node ID, or by a list of HFC\_Node ID. + +Mobility Restrictions for wireline access consists of Forbidden Area and Service Area Restrictions, as described in the following clauses. + +#### 4.3.3.2 Management of Forbidden Area in wireline access + +In a Forbidden Area, the 5G-RG, based on subscription, is not permitted by the 5GC to initiate any communication with the 5GC for this PLMN or SNPN. + +The UDM stores the Forbidden Area for wireline access in the same way as for 3GPP access, with the following differences: + +- For subscriptions for 5G-BRG, GLI is used to describe the Forbidden Area. +- For subscriptions for 5G-CRG and FN-CRG, HFC Node IDs are used to describe the Forbidden Area (instead of TA). +- The Forbidden Area in UDM can be encoded as a "allow list" indicating the non-forbidden area. In this case all GLI or HFC\_Node ID values not included in the list are considered forbidden. + +NOTE: The use of "allow list" is to ensure an efficient Forbidden Area definition if only a small set of GLI / HFC Node ID values are not forbidden. + +Forbidden Area is enforced by AMF, based on subscription data and the location information received from W-AGF. The AMF rejects a Registration Request from a 5G-RG or the W-AGF acting on behalf of a FN-CRG in a Forbidden Area with a suitable cause code. The 5G-RG behaviour depends on the network response (cause code from AMF) that informs the RG that communication is forbidden. + +#### 4.3.3.3 Management of Service Area Restrictions in wireline access + +The subscription data in the UDM for a 5G-BRG includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas specified by using explicit GLI(s) and/or other geographical information (e.g., longitude/latitude, zip code, etc.). + +The subscription data in the UDM for a 5G-CRG and FN-CRG includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas specified by using explicit HFC Node IDs and/or other geographical information (e.g., longitude/latitude, zip code, etc.). + +The geographical information used to specify allowed or non-allowed area is only managed in the network, and the network will map it to a list of GLI(s) or HFC Node IDs before sending Service Area Restriction information to the PCF. + +The UDM stores the Service Area Restrictions for the 5G-RG or FN-CRG as part of the subscription data. The PCF in the serving network may (e.g. due to varying conditions such as 5G-RG's location, time and date) further adjust Service Area Restrictions of a 5G-RG, either by expanding an allowed area or by reducing a non-allowed area. The UDM and the PCF may update the Service Area Restrictions of a 5G-RG or a FN-CRG at any time. + +During registration, if the Service Area Restrictions of the 5G-RG or FN-CRG is not present in the AMF, the AMF fetches from the UDM the Service Area Restrictions of the 5G-RG or FN-CRG that may be further adjusted by the PCF. The serving AMF shall enforce the Service Area Restrictions of a 5G-RG and a FN-CRG. The AMF receives the location information (GLI, HFC Node IDs) where the RG is connected from the W-AGF via N2. + +The network does not send any Allowed Area or Non-Allowed Area to the 5G-RG for wireline access. If the 5G-RG initiates communication in an Allowed Area, the network accepts the communication as allowed by the subscription. If the 5G-RG initiates Service Request or SM signalling in a Non-Allowed Area, the AMF rejects the request with a suitable cause code indicating that the 5G-RG/W-AGF should not retry Service Request and SM signalling while being connected to the same line. + +Upon change of serving AMF due to mobility, the old AMF may provide the new AMF with the Service Area Restrictions of the 5G-RG that may be further adjusted by the PCF. + +## 4.4 Session management + +### 4.4.0 General + +This clause specifies the delta related to session management defined in TS 23.501 [2] clause 5.6. + +The LADN service defined in clause 5.6.5 in TS 23.501 [2] does not apply for RG connected to 5GC via wireline access. + +When handling DHCP signalling coming from a wireline BBF access, the SMF (as well as an external DHCP server used by SMF) shall support the DHCP signalling as described in in BBF TR-456 [9]. + +NOTE: As described in clause 5.6.14 of TS 23.501 [2], to enable Framed Routes for a PDU Session, SMF can take the UPF capabilities for Framed Routes into account when selecting a UPF for a PDU Session. + +### 4.4.1 Session management for 5G-RG + +Session management of 5G-RG connected to 5GC via wireline access follows the principle defined in TS 23.501 [2] clause 5.6 with the following difference: + +- UE is replaced by 5G-RG. +- 5G-RG is connected to 5GC via wireline RAT type instead of 3GPP access. + +### 4.4.2 Session management for FN-RG + +Session management of FN-RG follows the principle defined in TS 23.501 [2] clause 5.6 with the follow difference: + +- UE is replaced by W-AGF +- FN-RG is connected to 5GC via wireline access instead of 3GPP access. +- Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session is applicable neither to FN-RG nor to N5GC devices. +- For FN-BRG, only SSC modes 1 or 2 can be used, depending on the type of FN-BRG as described in TR-456 [9] and WT-457 [10]. + +## 4.5 QoS model + +### 4.5.0 General overview + +The QoS model of TS 23.501 [2] clause 5.7 is applicable to the W-5GAN scenario, with the difference that the W-AGF acts as an Access Network (AN). + +The principle for classification and marking of User Plane traffic and mapping of QoS flows to W-UP resources is illustrated in Figure 4.5-1. + +![Figure 4.5-1: The principle for classification and User Plane marking for QoS Flows and mapping to W-UP resources for a PDU Session. The diagram shows the flow of data packets from the Application/Service Layer through the 5G-RG, W-AGF, and UPF. It details the mapping of QoS flows to W-UP resources and the application of QoS rules and PDRs.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +The diagram illustrates the User Plane (UP) traffic flow and QoS handling across three main entities: Application / Service Layer, 5G-RG, and UPF (with an intermediate W-AGF). At the top, the Application / Service Layer sends 'Data Packets' to the 5G-RG. The 5G-RG uses 'QoS rules (mapping UL packets to QoS flows and apply QoS flow marking)' to identify 'QoS Flow (all packets marked with the same QFI)'. These flows are then handled by the 5G-RG's 'Mapping QoS flows to W-UP Resources and AN-specific QoS marking' block, which directs them to 'W-UP Resources'. The W-UP Resources connect to the W-AGF. The W-AGF is part of a 'PDU Session' and uses 'PDRs (classify packets for QoS flow marking and other actions)' to further process the traffic before it reaches the UPF. The UPF also uses PDRs for classification and marking. Arrows indicate the direction of traffic flow: UL from App to 5G-RG, then to W-AGF via W-UP Resources, and finally to UPF; DL from UPF to W-AGF, then to 5G-RG via W-UP Resources, and finally to App. + +Figure 4.5-1: The principle for classification and User Plane marking for QoS Flows and mapping to W-UP resources for a PDU Session. The diagram shows the flow of data packets from the Application/Service Layer through the 5G-RG, W-AGF, and UPF. It details the mapping of QoS flows to W-UP resources and the application of QoS rules and PDRs. + +**Figure 4.5-1: The principle for classification and User Plane marking for QoS Flows and mapping to W-UP resources for a PDU Session** + +When the W-AGF receives N2 requests related with PDU Session resources, the W-AGF maps the QoS profile(s) received from the 5GC to W-UP level QoS. + +When the 5G-RG receives NAS message related with PDU Session QoS, the 5G-RG maps the QoS rule(s) received in NAS to W-UP level QoS. + +One W-UP resource can be used as the default W-UP resource. There shall be one and only one Default W-UP resource per PDU session. The 5G-RG shall send all QoS Flows to this W-UP resource for which there is no mapping information to a specific W-UP resource. + +Handling of UL traffic by the 5G-RG: + +- When the 5G-RG transmits an UL PDU, the 5G-RG shall determine the QFI associated with the UL PDU (by using the QoS rules of the PDU Session), it shall encapsulate the UL PDU inside an access layer dependent W-UP packet and shall forward the W-UP packet to W-AGF via the W-UP resource associated with this QFI. + +Handling of DL traffic by W-AGF: + +- When the W-AGF receives a DL PDU via N3, it identifies of the PDU Session and optionally the QFI in order to determine the W-UP resource to use for sending the DL PDU to the 5G-RG. The W-AGF may include also in the W-UP header the Reflective QoS Indicator (RQI), which shall be used by the 5G-RG to enable reflective QoS. + +The W-AGF will map 5QI received from the 5GC into access-specific QoS parameters relevant to the wireline access network. The mapping of 5QI to W-5GBAN QoS parameters is specified by the BBF for W-5GBAN in [9]. The mapping of 5QI to W-5GCAN QoS parameters is specified for W-5GCAN in CableLabs WR-TR-5WWC-ARCH [27]. + +QFI or other QoS parameters are carried via W-UP to the 5G-CRG as specified in CableLabs WR-TR-5WWC-ARCH [27]. + +The QFI and RQI are carried via W-UP to 5G-RG as specified in BBF TR-456 [9]. + +### 4.5.1 Wireline access specific 5G QoS parameters + +#### 4.5.1.0 Overview + +The 5G QoS parameters specified in clause 5.7.2 of TS 23.501 [2] are applicable to wireline access network, with the following differences: + +- The parameters defined in clause 4.5.1.2 are applicable for the wireline access network related PDU sessions. +- UE-AMBR is not applicable to wireline access. The AMF should not provide the subscribed UE-AMBR to the W-AGF. + +#### 4.5.1.1 Void + +#### 4.5.1.2 RG Level Wireline Access Characteristics + +The wireline access networks may exhibit QoS control mechanisms and related thresholds, such as QoS class specific maximum bit rates, which the W-AGF needs to be aware of, in order to provide appropriate mapping of the QoS characteristics of the 5G QoS flows to the wireline technology specific QoS parameters. + +These wireline access characteristics are considered to be relevant for a specific wireline access subscription, and correspond to RG level QoS information in the 5GC. + +While the wireline access characteristics are important for implementing the end to end QoS mechanisms, across the 5G-RG/FN-RG, the W-5GAN and the 5GC, they only need to be acted on in the 5G-RG/FN-RG and the W-5GAN. + +In the case of 5G-RG serving the AUN3 devices, the RG Level Wireline Access Characteristics stored in 5G-RG's subscription includes a maximum bit rate for the aggregated traffic of the 5G-RG and of the AUN3 devices served by this 5G-RG. + +In order to support the W-AGF in implementing the mapping between 5G QoS parameters and wireline access specific parameters, the AMF may provide the RG Level Wireline Access Characteristics (RG-LWAC) to the W-AGF at the time of the RG registration. When the UDM notifies the AMF of the updated RG-LWAC via Nudm\_SDM\_Notification service, the AMF may update the RG-LWAC to the W-AGF via NGAP UE Context Modification procedure. + +Given that the 5GC does not act on these parameters, their structure is out of scope in 3GPP specifications and they are handled as a transparent data container. BBF and CableLabs may define the content and structure of this container for their own use. + +The UE subscription data parameters RG Level Wireline Access Characteristics are defined in clause 8.1.1. + +### 4.5.2 QoS model applied to FN-RG + +The FN-RG does not support 3GPP signalling and therefore, mapping and interworking between 5G QoS and the wireline access network resources is managed by the W-AGF on behalf of the FN-RG. + +The mapping of W-5GAN resources and 5GC QoS is configured in the W-AGF for the FN-CRG is specified by CableLabs. Resource management within the W-5GAN for the FN-CRG is specified by CableLabs. + +The mapping of W-5GAN resources and 5GC QoS is configured in the W-AGF for the FN-BRG is specified by BBF. Resource management within the W-5GAN for the FN-BRG is specified by BBF. + +### 4.5.3 Differentiated QoS for devices behind 5G-RG + +During PDU session establishment and PDU session modification, if the SMF provides the 5G-RG with QoS flow descriptions, the SMF may additionally signal Non-3GPP QoS Assistance Information (N3QAI) for each QoS flow to the 5G-RG). Based on the N3QAI together with QoS rule information, the 5G-RG may reserve resources in the non-3GPP network behind the 5G-RG (e.g. home LAN network). N3QAI consists of the following QoS information: QoS characteristics, GFBR/MFBR, Maximum Packet Loss Rate, ARP and Periodicity (if available at the SMF). + +NOTE 1: How 5G-RG uses the Non-3GPP QoS Assistance Information to enforce QoS in the non-3GPP network is outside the scope of 3GPP. + +NOTE 2: Transferring information like Periodicity to the 5G-RG is not meant to support TSC/TSN like flows but to support consumer real time applications like XR (extended Reality, etc.). + +## 4.6 User Plane management + +### 4.6.1 General + +The management of the user plane follows the description in clause 5.8 of TS 23.501 [2] with additional specification described below in this clause. + +### 4.6.2 IP address allocation + +#### 4.6.2.1 General + +IP address allocation is performed as described in TS 23.501 [2] clause 5.8.2.2, with the differences and additions described in this clause. + +Stateless IPv6 Address Autoconfiguration applies with the differences described in clause 4.6.2.4. + +In addition to the IP address management features described in TS 23.501 [2] clause 5.8.2.2 the 5GC network functions and RG support the following mechanisms: + +- a. IPv6 address allocation using DHCPv6 may be supported for allocating individual /128 IPv6 address(es) for a PDU Session. The details of IPv6 address allocation using DHCPv6 are described in clause 4.6.2.2. +- b. IPv6 Prefix Delegation using DHCPv6 may be supported for allocating additional IPv6 prefixes for a PDU Session. The details of Prefix Delegation are described in clause 4.6.2.3. + +The mechanisms in a. and b. above are only applicable for IPv6 and IPv4v6 PDU Session types. + +The requested IPv6 address or set of IPv6 Prefixes may be (as defined in TS 23.501 [2] clause 5.8.2.2.1): + +- allocated from a local pool in the SMF or +- obtained from the UPF. In that case the SMF shall interact with the UPF via N4 procedures to obtain a suitable IP address/Prefix, or +- obtained from an external server. + +When obtaining the IP address from the UPF, the SMF provides the UPF with the necessary information allowing the UPF to derive the proper IP address (e.g. the network instance, IP version, size of the IP address or Prefix the UPF is to allocate). + +The SMF may also provide IP configuration parameters (e.g. MTU value) to the 5G-RG, as described in clause 5.6.10 of TS 23.501 [2]. + +NOTE: In order to provide an IP MTU value that is specifically suitable for W-5GAN without considering N3 in case of combined W-AGF/UPF, the SMF can e.g. be configured with such MTU for a given DNN and/or for a given slice whether the DNN and/or the slice only serves wireline access and a UPF combined with the W-AGF has been selected for the PDU Session. + +In this clause, unless specified otherwise, the RG may correspond either to a 5G RG or to a FN RG. + +#### 4.6.2.2 IPv6 Address Allocation using DHCPv6 + +Optionally, and instead of using Stateless IPv6 Address Autoconfiguration, individual 128-bit IPv6 address(es) may be assigned to a PDU Session. + +In this case, after PDU Session Establishment, the SMF sends a Router Advertisement message (solicited or unsolicited) towards the RG. The SMF shall set the Managed Address Configuration Flag (M-flag) in the Router Advertisement messages to indicate towards the RG that IPv6 Address allocation using DHCPv6 is available, as described in RFC 4861 [34]. In that case the IPv6 address of the RG is allocated using DHCPv6 Identity Association for Non-temporary Addresses (IA\_NA) and mechanisms defined in RFC 8415 [47]. + +The SMF may receive a Router Solicitation message, soliciting a Router Advertisement message. + +When using DHCPv6 address allocation, a prefix (e.g. /64) may be allocated for the PDU Session at PDU Session Establishment from which the /128 addresses are selected. The SMF determines the size of the prefix for a PDU Session to a specific DNN and S-NSSAI based on subscription data and local configuration. The individual /128 address(es) allocated to the RG as part of DHCP IA\_NA procedure are then selected from the prefix allocated to the PDU Session. For statically assigned prefix, the subscription data in UDM for a DNN and S-NSSAI includes the prefix. Alternatively, individual 128-bit address(es) are allocated for the PDU Session without allocating a prefix to the PDU Session and provided to the RG as part of DHCP IA\_NA procedure. + +When a prefix is allocated to the PDU Session, the SMF provides the prefix to the PCF instead of each /128 address. When individual /128 address(es) are allocated without allocating a prefix to the PDU Session, the SMF provides the /128 bits address(es) to PCF. Whether the SMF allocates a prefix for the PDU Session or individual 128-bit addresses is transparent to the RG and W-5GAN. + +If Prefix Delegation (as described in clause 4.6.2.3) is also supported, a SMF may receive both DHCP options for IA\_NA and IA\_PD together in a single DHCPv6 message. An SMF may provide a reply to both IA\_NA and IA\_PD in the same message or alternatively process the DHCPv6 IA\_NA before the DHCPv6 IA\_PD. + +The SMF may receive multiple different IA\_NA related DHCP requests within the same PDU Session. + +NOTE: This is applicable if the RG acts as a DHCP relay for devices behind the RG. + +When IPv6 Address Allocation using DHCPv6 is used, 5GC does not support IPv6 multi-homing for enabling SSC mode 3 and PDU Sessions with multiple PDU Session Anchors. + +#### 4.6.2.3 IPv6 Prefix Delegation via DHCPv6 + +In addition to what is the specified in clause 5.8.2.2.4 of TS 23.501 [2], there is following difference: + +- UE is replaced by 5G-RG and FN-RG. +- For IPv6 stateless IPv6 address autoconfiguration or IPv6 address allocation using DHCPv6, the SMF determines the maximum size of the prefix that may be allocated for the PDU Session based on subscription data and local configuration. +- If IPv6 address allocation using DHCPv6 is used, the DHCPv6 message may include a request for a delegated prefix (IA\_PD) together with a request for an IPv6 address (IA\_NA). Alternatively, a delegated prefix may be requested after an IPv6 address has been assigned using IA\_NA. +- If the DHCPv6 request indicates support for prefix exclusion via the OPTION\_PD\_EXCLUDE option code in an OPTION\_ORO option and if the SMF accepts this option, the SMF delegates a prefix excluding the default prefix with help of OPTION\_PD\_EXCLUDE. Prefix exclusion procedures shall follow IETF RFC 6603 [16]. + +#### 4.6.2.4 The procedure of Stateless IPv6 Address Autoconfiguration + +Stateless IPv6 Address Autoconfiguration applies as described in clause 5.8.2.2.3 of TS 23.501 [2] with the differences described below. + +When the W-AGF is serving an FN-RG, the W-AGF may include in the PDU Session Establishment Request an interface identifier of the FN-RG IPv6 link-local address associated with the PDU Session. If the SMF receives an + +interface identifier in the PDU Session Establishment Request message, the SMF provides this interface identifier value as the UE interface identifier in the PDU Session Establishment Accept message. To ensure that the link-local address used by the FN-RG does not collide with the link-local address of the SMF in this case, the SMF selects a different link-local address for use as the SMF link local address for the PDU Session. If the PDU Session Establishment Request message does not contain an interface identifier, the SMF selects interface identifier for the UE, and SMF link-local address, as described in clause 5.8.2.2.3 of TS 23.501 [2]. + +NOTE 1: An FN-RG is configuring its IPv6 link local address based on its MAC address and is not able to use an interface identifier selected by SMF as described in clause 5.8.2.2.3 of TS 23.501 [2]. + +In case of wireline access, independent of whether SMF received an interface identifier in the PDU Session Establishment Request message or not, the SMF includes the SMF link local address in the PDU Session Establishment Accept message. + +NOTE 2: The SMF link local address is needed by the W-AGF to support procedures towards the FN-RG defined in BBF TR-456 [9]. + +### 4.6.3 Packet Detection Rule + +PDR used to support PDU Sessions for RG follow the specifications in TS 23.501 [2] clause 5.8.2.11.3 with the clarifications and additions shown below. + +For PDU Session used for IPTV service, (see also clause 4.6.6): + +- Packets Filter Set support Packet Filters for IGMP, including IGMPv2 specified in RFC 2236 [33], IGMPv3 specified in RFC 4604 [21], for MLDv1 specified in RFC 2710 [36] and MLDv2 specified in RFC 4604 [21]. The PDR may also contain IP Multicast addressing information that may refer to ranges of IP multicast addresses. Such IP Multicast addressing information is not part of the PDI. The packets filters for IGMPv1 defined in RFC 1112 [35] are not supported. + +### 4.6.4 Forwarding Action Rule + +FAR used to support PDU Sessions for RG follow the specifications in TS 23.501 [2] clause 5.8.2.11.6 with the clarifications and additions and difference shown below. + +For PDU Sessions used for IPTV service (see also clause 4.6.6): + +- Following additional "Action" values are used to support IPTV service: +- "IP Multicast Accept" indicates whether in the case of IGMP and MLD Membership Report message to accept the multicast join and add the PDU Session to the requested multicast group distribution. This may also imply acting as an IP Multicast Router as described in clause 7.7.1.1 + +NOTE 1: The IGMP "Join message" and MLD "Join message" are generic terms used in this document to indicate the request of a host to join a multicast group which can express via IGMP and MLD Report message (e.g. Membership Report) or via Join message. + +NOTE 2: In this specification the generic term IGMP refers to both IGMPv2 and IGMPv3 unless specifically defined. The term MLD refers to both MLDv1 and MLDv2 unless specifically defined. + +- "IP Multicast Accept" indicates that when UPF detects the IGMPv3 Leave message or a MLD Done message via the PDU Session, the UPF needs also to ensure that the PDU Session is removed from the requested multicast group distribution. +- "IP Multicast Deny" indicates that the UPF shall not accept the corresponding IGMP and MLD Membership Report message to join a multicast group. + +### 4.6.5 Usage Reporting Rule + +URR used to support PDU Sessions for RG follow the specifications in TS 23.501 [2] clause 5.8.2.11.5 with the clarifications and additions shown below: + +For PDU Sessions used for IPTV service (see also clause 4.6.6), an URR may indicate a Reporting trigger (defined in TS 23.501 [2] clause 5.8.2.11.5) with a value Reporting Trigger set to "IGMP reporting" for IGMP or set to "MLD reporting" for MLD where the UPF is to report to the SMF when + +- it adds a PDU session to the DL replication tree associated with an IP Multicast flow; +- it removes a PDU session from the DL replication tree associated with an IP Multicast flow. + +The corresponding notification shall contain the (Source IP address of the DL multicast flow, Destination IP address of the DL multicast flow). + +NOTE: The corresponding notification can be used by the SMF to report the information to the PCF and/or to CHF. + +### 4.6.6 Usage of N4 to support IPTV + +The SMF sends to the UPF acting as PSA N4 rules such as PDR, FAR related to IP Multicast traffic allowed for the PDU Session of a 5G-RG. IP Multicast traffic allowed for the PDU Session corresponds to IPTV services allowed for the user. IP Multicast Addressing information identifies such traffic. In the case Source Specific Multicast is configured to be used on the PDU Session, IP Multicast Addressing information refers to both IP Multicast address and Source IP address. + +The SMF may need to take into account UPF capability to support the features described in this clause when selecting an UPF to serve a PDU Session. For IPv6 PDU session IPTV services will be based on MLD , for IPv4 PDU session on IGMP. + +N4 rules for IP Multicast traffic related to IPTV service may correspond to: + +- Rules related with UL IGMP or MLD traffic: + - a PDR identifying IGMP signalling or MLD together with IP Multicast Addressing information identifying a set of IP multicast groups; + +NOTE 1: The IP Multicast Addressing information may correspond to ranges of IP Multicast addresses + +- a FAR with: + - an "IP Multicast Accept" action in order to request the UPF to accept UE requests to join the corresponding IP multicast group(s); or + - an "IP Multicast Deny" action in order to request the UPF to deny UE requests to join the corresponding IP multicast group(s); +- possibly a URR with a Reporting Trigger set to "IGMP reporting" for IGMP or set to "MLD reporting" for MLD; + +- Rules related with DL IP Multicast traffic: + +- a PDR identifying IP Multicast Addressing information (DL IP Multicast traffic); + +NOTE 2: The IP Multicast Addressing information may correspond to ranges of IP Multicast addresses + +- a FAR asking to add outer header = GTP-u tunnel related with the PDU Session of the 5G RG; +- a QER indicating the QoS to use towards the 5G-RG for the IP Multicast traffic that has been replicated. + +## 4.7 Identifiers + +### 4.7.1 General + +As described in TS 23.501 [2], each subscriber in the 5G System shall be allocated one 5G Subscription Permanent Identifier (SUPI) for use within the 3GPP system. As described in TS 23.501 [2], each FN-RG or 5G-RG accessing the 5G System shall be assigned a Permanent Equipment Identifier (PEI). + +The clauses below describe specific aspects for supporting 5G-RG and FN-RG. + +### 4.7.2 SUPI and SUCI for 5G-BRG support + +For PLMNs, the SUPI for a 5G-BRG shall contain an IMSI, as described in clause 5.9.2 of TS 23.501 [2]. The SUPI for accessing SNPN is defined in clause 4.16.1. + +The SUCI provided by the 5G-BRG to the network contains the concealed SUPI, as described in TS 33.501 [11]. + +### 4.7.3 SUPI and SUCI for FN-BRG support + +The SUPI for an FN-BRG subscription shall, based on operator configuration, either contain an IMSI or a GLI as defined in clause 4.7.8. A SUPI containing a GLI takes the form of a NAI whose user part is the GLI and whose realm part is an identifier of the operator owning the subscription. + +The SUCI provided by the W-AGF to the 5GC for FN-BRG always corresponds to a SUPI containing a GLI. This SUCI acts as pseudonym of the SUPI and the UDM performs a mapping to the actual SUPI that, depending on operator configuration, contains either an IMSI or the same GLI that was provided in the SUCI. + +As described in TS 23.003 [14], the SUCI also contains an identifier of the Home network, i.e. the identifier of the operator owning the subscription. + +### 4.7.4 SUPI and SUCI for 5G-CRG and FN-CRG support + +The SUPI for a FN-CRG subscription shall, based on operator configuration, contain either an IMSI, as described in clause 5.9.2 of TS 23.501 [2], or a GCI (Global Cable identifier defined in clause 4.7.9). + +The SUPI for a 5G-CRG subscription shall, based on operator configuration, contain either an IMSI, as described in clause 5.9.2 of TS 23.501 [2], or a GCI (Global Cable identifier defined in clause 4.7.9). + +For PLMNs, only 5G-CRG whose SUPI corresponds to an IMSI may use 3GPP access to connect to 5GC. The SUPI for accessing SNPN is defined in clause 4.16.1. + +A SUPI containing a GCI takes the form of a NAI where the user part is the GCI and the realm part is an identifier of the operator managing the subscription. + +NOTE 1: The realm part used to identify the operator managing the subscription can differ depending on whether the wireline access network belongs to a PLMN or SNPN. The NAI format for SUPI containing GCI for PLMN and SNPN is defined in TS 23.003 [14]. + +The SUCI provided by the 5G-CRG to the network contains the concealed SUPI, as described in TS 33.501 [11]. + +The SUCI provided to the network for FN-CRG support always corresponds to a SUPI containing a GCI. This SUCI acts as pseudonym of the SUPI and the UDM performs a mapping to the SUPI that, depending on operator configuration, contains either an IMSI or the same GCI than in the SUCI. + +As described in TS 23.003 [14], for both cases where the SUCI contains an IMSI or contains a GCI, the SUCI contains an identifier of the Home network i.e. an identifier of the operator managing the subscription. + +NOTE 2: If the SUCI contains an IMSI, the identifier of the operator managing the subscription is carried in the MCC/MNC part of the IMSI as defined in TS 23.003 [14]. + +### 4.7.5 Line ID + +The Line ID is defined in BBF Specifications, see BBF TR-470 [38]. + +### 4.7.6 HFC identifier + +The HFC\_Identifier may contain a cable modem MAC address or an overall HFC account identifier, as defined by CableLabs in DOCSIS MULPI [8]. + +### 4.7.7 PEI + +If the 5G-RG (i.e. 5G-BRG and 5G-CRG) supports at least one 3GPP access technology (i.e. NG-RAN, E-UTRAN), the 5G-RG must be allocated a Permanent Equipment Identifier (PEI) in the IMEI or IMEISV format, as described in TS 23.501 [2]. The 5G-RG shall present this PEI to the network independent of access technology used by the 5G-RG (3GPP access technology or W-5GAN access technology). + +If the 5G-BRG supports only W-5GAN access, the PEI shall contain the 5G-BRG MAC address. + +If the 5G-CRG supports only W-5GAN access, the PEI shall contain the cable modem MAC address. + +For FN-RG (i.e. FN-BRG and FN-CRG), the W-AGF shall provide a PEI containing: + +- The FN-RG MAC address: this shall be used by the W-AGF when it is known by configuration that the MAC address received by the W-AGF is unique (no other entity can use the same MAC address) and corresponds to the permanent MAC address configured on the RG by the manufacturer. + +NOTE 1: This assumes that the W-AGF can see the actual permanent MAC address of the FN-RG and not the MAC address of any intermediate entity (e.g. DSLAM). + +- The MAC address received by the W-AGF, together with an indication provided by the W-AGF that this address cannot be used as an Equipment identifier of the FN-RG: this shall be used by the W-AGF when the conditions to provide a PEI containing the FN-RG MAC address are not met. + +NOTE 2: This is to support the case of legacy deployments for FN RG where either multiple FN RG can share the same MAC address or where the MAC address received by the W-AGF is not that of the FN RG but the MAC address of an intermediate entity between the FN RG and the W-AGF. + +NOTE 3: When the PEI contains an indication that the MAC address cannot be used as an Equipment identifier of the FN-RG, the PEI cannot be trusted for regulatory purpose but it can be stored in CDR and used for troubleshooting. + +### 4.7.8 Global Line Identifier + +For usage with 5GC, a Global Line Identifier (GLI) is specified in order to define a globally unique identifier of the line connecting the RG to the network. In this release an RG is associated with a unique GLI. + +For FN BRG, the GLI is used to build a SUCI. For FN-BRG the GLI may be used to build a SUPI. See clause 4.7.3. For all types of RG, the GLI is used as User Location Information on wireline access. + +The GLI contains an identifier of the Line ID source and the Line ID value. The identifier of the Line ID source ensures the unicity of the GLI while the Line ID may not be unique in some deployments. The identifier of the Line ID source and Line ID are administered by the W-AGF operator. + +The Global Line Identifier is a variable length identifier encoded as defined in TS 23.003 [14] and in BBF TR-470 [38]. + +### 4.7.9 Global Cable Identifier + +For usage with 5GC, a Global Cable Identifier (GCI) is specified in order to define a globally unique identifier of the line connecting the CRG to the network. In this release an RG is associated with a unique GCI. + +The GCI contains the HFC\_Identifier which is defined in CableLabs WR-TR-5WWC-ARCH [27]. + +For FN CRG, the GCI is used to build a SUCI. For FN CRG the GCI may be used to build a SUPI. See clause 4.7.4. For all types of CRG the HFC Node ID is used to build User Location Information on Cable access. + +The identifier of the HFC Node ID and the HFC\_Identifier are administered by the W-AGF operator. + +The Global Cable Identifier is a variable length identifier encoded as defined in TS 23.003 [14] and CableLabs WR-TR-5WWC-ARCH [27]. + +### 4.7.10 RAT types dedicated for Wireline access + +The AMF, as described in TS 23.501 [2] clause 5.3.2.3, determines the RAT Type for Wireline access, taking into account the Global W-AGF Node ID and possibly ULI information provided by the W-AGF. The RAT Type may allow to distinguish between Wireline, Wireline-Cable access and Wireline-BBF access. + +### 4.7.11 SUPI and SUCI for N5GC device or AUN3 device support + +The SUPI for non-5G capable (N5GC) device or AUN3 device connecting via CRG shall contain a network-specific identifier. A SUPI containing a network-specific identifier takes the form of a Network Access Identifier (NAI) as defined in TS 23.003 [14]. + +The SUCI provided by the W-AGF to the AMF is derived from the EAP-Identity message received from the N5GC device or AUN3 device, as defined in TS 33.501 [11]. The format of this SUCI is defined in TS 23.003 [14]. + +## 4.8 Security aspects + +TS 23.501 [2] clause 5.10 applies to the FN-CRG with the following deltas: + +- Mutual authentication of the FN-CRG and the wireline access network is completed as specified by CableLabs DOCSIS MULPI [8]. The successful completion of the authentication of the FN-CRG is conveyed by the W-AGF serving the FN-CRG to the AMF. +- UE is replaced by W-AGF on behalf of the FN-CRG for the balance of TS 23.501 [2] clause 5.10 and clauses. +- See TS 33.501 [11] for additional requirements + +TS 23.501 [2] clause 5.10 applies to the 5G-CRG with the following deltas: + +- The UE is replaced by the 5G-CRG +- Signalling security aspects between the 5G-CRG and the W-AGF are specified by CableLabs in WR-TR-5WWC-ARCH [27]. +- See TS 33.501 [11] for additional requirements + +## 4.9 Support of specific services + +### 4.9.0 General + +This clause specifies high level definition of services specific for WWC scenario. + +PWS functionality as described in TS 23.041 [40] is not supported for Wireline access but may be supported by RG(s) connected over 3GPP access. + +### 4.9.1 IPTV + +IPTV is defined as multimedia services such as television/video/ audio/text/graphics/data delivered over IP-based networks managed to support the required level of QoS/QoE, security, interactivity and reliability. STB obtains IPTV service via RG, including 5G-RG and FN-RG, which are connected to 5GC. + +The procedures to support IPTV is specified in clause 7.7.1. + +## 4.10 UE behind 5G-RG and FN-RG + +An RG connecting via W-5GAN or NG-RAN access towards 5GC can provide connectivity for a UE behind the RG to access an N3IWF or TNGF. It is assumed that the UE is 5GC capable, i.e. supports untrusted non-3GPP access and/or trusted non-3GPP access. This allows the RG, W-5GAN and the RG's connectivity via 5GC to together act as untrusted/trusted N3GPP access to support UEs behind the RG. + +When FN-RG/5G-RG is serving a UE, the control and user plane packets of the UE is transported using a FN-RG/5G-RG IP PDU session and then from PSA UPF of that PDU session to an N3IWF or TNGF. A single FN-RG/5G-RG IP PDU session can be used to serve multiple UEs. + +Figure 4.10-1 shows the non-roaming architecture for a UE, behind a 5G-RG, accessing the 5GC via TNGF where the combination of 5G-RG, W-5GAN and UPF serving the 5G-RG is acting as a trusted Non-3GPP access network. + +Figure 4.10-2a shows the non-roaming architecture for a UE, behind a FN-RG, accessing the 5GC via N3IWF. + +Figure 4.10-2b shows the non-roaming architecture for a UE, behind a 5G-RG, accessing the 5GC via N3IWF. + +Annex A shows the non-roaming architecture for a UE, behind a FN-RG/5G-RG, accessing the 5GC via N3IWF where the combination of FN-RG/5G-RG, W-5GAN and UPF serving the FN-RG/5G-RG is acting as an untrusted Non-3GPP access network. + +NOTE 1: FN-RG and W-5GAN acting as trusted Non-3GPP access is not considered in this specification as it is assumed that FN-RG is not 5G capable and therefore it does not support Ta reference point. + +![Figure 4.10-1: Non-roaming architecture for UE behind 5G-RG using trusted N3GPP access. The diagram shows a UE connected to a 5G-RG (acting as a TNAP). The 5G-RG is connected to an NG-RAN and a W-5GAN. The NG-RAN is connected to an AMF via N2 and N1 interfaces. The W-5GAN is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to a TNGF via N6. The TNGF is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The UPF is connected to a DNN for UE via N6. A Ta reference point is shown between the 5G-RG and the TNGF.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +Figure 4.10-1: Non-roaming architecture for UE behind 5G-RG using trusted N3GPP access. The diagram shows a UE connected to a 5G-RG (acting as a TNAP). The 5G-RG is connected to an NG-RAN and a W-5GAN. The NG-RAN is connected to an AMF via N2 and N1 interfaces. The W-5GAN is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to a TNGF via N6. The TNGF is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The UPF is connected to a DNN for UE via N6. A Ta reference point is shown between the 5G-RG and the TNGF. + +**Figure 4.10-1: Non-roaming architecture for UE behind 5G-RG using trusted N3GPP access** + +The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via trusted non-3GPP access with 5G-RG acting as TNAP, NG-RAN or via both accesses. + +![Figure 4.10-2a: Architecture for UE behind FN-RG using untrusted N3GPP access. The diagram shows a UE connected to an FN-RG (acting as an untrusted non-3GPP access). The FN-RG is connected to a W-5GAN. The W-5GAN is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to an N3IWF via N6. The N3IWF is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The UPF is connected to a DNN for UE via N6.](14515d82ffeec9475b9add3036ff26ab_img.jpg) + +Figure 4.10-2a: Architecture for UE behind FN-RG using untrusted N3GPP access. The diagram shows a UE connected to an FN-RG (acting as an untrusted non-3GPP access). The FN-RG is connected to a W-5GAN. The W-5GAN is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to an N3IWF via N6. The N3IWF is connected to an AMF via N1 and N2 interfaces, and to a UPF via N3. The UPF is connected to a DNN for UE via N6. + +**Figure 4.10-2a: Architecture for UE behind FN-RG using untrusted N3GPP access** + +![Figure 4.10-2b: Architecture for UE behind 5G-RG using untrusted N3GPP access. The diagram shows a UE connected to a 5G-RG via the NwU interface. The 5G-RG is connected to an NG-RAN via N1 and N2 interfaces, and to a W-5GAN via N3. The NG-RAN is connected to an AMF via N1 and N2 interfaces. The AMF is connected to an SMF via N11 and to a UPF via N4. The W-5GAN is connected to the UPF via N3. The UPF is connected to an N3IWF via N6. The N3IWF is connected to another AMF via N1 and N2 interfaces. This second AMF is connected to another SMF via N11 and to another UPF via N4. The second UPF is connected to a DNN for UE via N6.](26d664119ad25250780f554633444e54_img.jpg) + +Figure 4.10-2b: Architecture for UE behind 5G-RG using untrusted N3GPP access. The diagram shows a UE connected to a 5G-RG via the NwU interface. The 5G-RG is connected to an NG-RAN via N1 and N2 interfaces, and to a W-5GAN via N3. The NG-RAN is connected to an AMF via N1 and N2 interfaces. The AMF is connected to an SMF via N11 and to a UPF via N4. The W-5GAN is connected to the UPF via N3. The UPF is connected to an N3IWF via N6. The N3IWF is connected to another AMF via N1 and N2 interfaces. This second AMF is connected to another SMF via N11 and to another UPF via N4. The second UPF is connected to a DNN for UE via N6. + +**Figure 4.10-2b: Architecture for UE behind 5G-RG using untrusted N3GPP access** + +The FN-RG can only be connected to 5GC via W-5GAN. The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via untrusted non-3GPP access with FN-RG/5G-RG acting as WLAN access point, NG-RAN or via both accesses. + +The TNGF and Ta reference point are defined in TS 23.501 [2]. In addition to the requirements described in TS 23.501 [2], the Ta reference point should be able to carry the TNAP ID to the TNGF. + +NOTE 2: The reference architecture in figure 4.10-1/4.10-2a/4.10-2b only shows the architecture and the network functions directly connected to W-5GAN or TNGF/N3IWF, and other parts of the architecture are the same as defined in clause 4.2 of TS 23.501 [2]. + +NOTE 3: The reference architecture in figure 4.10-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. + +NOTE 4: The two N2 instances in Figure 4.10-1/4.10-2b apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and W-5GAN. + +NOTE 5: For trusted non-3GPP access, UE connects to the overlay 5G network using the trusted non-3GPP access approach. In addition to being connected to the underlay 5G network, the 5G-RG also acts as TNAP with respect to the TNGF in the overlay network i.e. it has an established Ta reference point with the TNGF. + +NOTE 6: Support for QoS differentiation can be achieved in a similar way as it is handled when a UE connects to a PLMN via SNPN (as defined in clauses 5.30.2.7 and D.7 of TS 23.501 [2]). Also differentiated charging, both in the RG's PLMN and in the UE's PLMN, can be achieved based on existing mechanisms. This is further described in Annex B. + +Support of NSWO for 3GPP UE behind an RG is specified in clause 4.10d. + +A 5G-RG acting as a TNAP shall provide its TNAP ID to the TNGF and the TNGF provides this TNAP ID as part of ULI (User Location Information) sent to the 5GC; this information is propagated to the PCF that may use it to determine PCC rules depending on whether an UE is using a 5G-RG as a host or as a guest. + +NOTE 7: QoS and charging differentiation based on user location (e.g. home or guest users) can be applied when the user is connected via a TNGF reached over a 5G-RG. The PCF may use the TNAP ID, which is available to it as a part of ULI. For example, if the TNAP ID is included in the UE's policy control subscription information the UE is considered a home user. Alternatively, the PCF may use TNAP ID provided by an AF using the Service Specific parameter provisioning as defined in clause 9.8. + +## 4.10a Non-5G capable device behind 5G-CRG and FN-CRG + +For isolated 5G networks (i.e. roaming is not considered) with wireline access, non-5G capable (N5GC) devices connecting via W-5GAN can be authenticated by the 5GC using EAP based authentication method(s) as defined in TS 33.501 [11]. The following call flow describes the overall registration procedure of such a device. + +Roaming is not supported for N5GC devices. + +The usage of N5GC device correspond to a subscription record in UDM/UDR that is separate from that of the CRG. + +![Sequence diagram for 5GC registration of Non-5GC device. Lifelines: N5GC device, CRG, W-AGF, AMF, AUSF/UDM. The sequence shows: 1. W-AGF registers FN-CRG to 5GC OR 5G-CRG registers itself to 5GC; 2a. L2 establishment; 2b. EAPOL-start; 2c. EAP Req/Identity; 2d. EAP Resp/Identity; 3. NGAP Initial UE (NAS Registration request(SUCI, N5GC)); 4. AUSF selection; 5. EAP authentication procedures; 6. Registration of N5GC device; 7. Registration Accept.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant N5GC device + participant CRG + participant W-AGF + participant AMF + participant AUSF/UDM + + Note right of W-AGF: 1. W-AGF registers FN-CRG to 5GC OR 5G-CRG registers itself to 5GC + Note left of CRG: 2a. L2 establishment + Note left of W-AGF: 2b. EAPOL-start + Note left of W-AGF: 2c. EAP Req/Identity + Note left of W-AGF: 2d. EAP Resp/Identity + Note right of W-AGF: 3. NGAP Initial UE (NAS Registration request(SUCI, N5GC)) + Note right of AMF: 4. AUSF selection + Note left of N5GC device: 5. EAP authentication procedures + Note right of AUSF/UDM: 6. Registration of N5GC device + Note right of AMF: 7. Registration Accept + +``` + +Sequence diagram for 5GC registration of Non-5GC device. Lifelines: N5GC device, CRG, W-AGF, AMF, AUSF/UDM. The sequence shows: 1. W-AGF registers FN-CRG to 5GC OR 5G-CRG registers itself to 5GC; 2a. L2 establishment; 2b. EAPOL-start; 2c. EAP Req/Identity; 2d. EAP Resp/Identity; 3. NGAP Initial UE (NAS Registration request(SUCI, N5GC)); 4. AUSF selection; 5. EAP authentication procedures; 6. Registration of N5GC device; 7. Registration Accept. + +**Figure 4.10a-1: 5GC registration of Non-5GC device** + +1. The W-AGF registers the FN-CRG to 5GC as specified in clause 7.2.1.3 or the 5G-CRG registers to 5GC as specified in clause 7.2.1.1. +2. The CRG is configured as L2 bridge mode and forwards any L2 frame to W-AGF. 802.1x authentication may be triggered. This can be done either by N5GC device sending a EAPOL-start frame to W-AGF or W-AGF receives a frame from an unknown MAC address. + +How the CRG is configured to work in L2 bridge mode and how the W-AGF is triggered to apply procedures for N5GC devices is defined in CableLabs WR-TR-5WWC-ARCH [27]. + +The N5GC device send an EAP-Resp/Identity including its Network Access Identifier (NAI) in the form of username@realm. + +3. W-AGF, on behalf of the N5GC device, sends a NAS Registration Request message to AMF with a device capability indicator that the device is non-5G capable. For this purpose, the W-AGF creates a NAS Registration Request message containing a SUCI. The W-AGF constructs the SUCI from the NAI received within EAP-Identity from the N5GC device as defined in TS 33.501 [11]. + +Over N2 there is a separate NGAP connection per N5GC device served by the W-AGF. + +When it provides (over N2) ULI to be associated with a N5GC device, the W-AGF builds the N5GC's ULI using the GCI (see clause 4.7.9) of the CRG connecting the N5GC device. + +NOTE: How the W-AGF determines the CRG connecting a N5GC device is specified in CableLabs WR-TR-5WWC-ARCH [27]. + +4. AMF selects a suitable AUSF as specified in TS 23.501 [2] clause 6.3.4. +5. EAP based authentication defined in TS 33.501 [11] is performed between the AUSF and N5GC device. + +Once the N5GC device has been authenticated, the AUSF provides relevant security related information to the AMF. AUSF shall return the SUPI (this SUPI corresponds to a NAI that contains the username of the N5GC device and a realm as defined in TS 33.501 [11]) to AMF only after the authentication is successful. + +NOTE: Each N5GC device is registered to 5GC with its own unique SUPI. + +6. The AMF performs other registration procedures as required (see TS 23.502 [3] clause 4.2.2.2.2). + +When providing a PEI for a N5GC device, the W-AGF shall provide a PEI containing the MAC address of the N5GC device. The W-AGF may, based on operator policy, encode the MAC address of the N5GC device using the IEEE Extended Unique Identifier EUI-64 format (see IEE Publication [41]). + +7. The AMF sends Registration Accept message to W-AGF. + +Once the registration procedure is completed, the W-AGF requests the establishment of a PDU Session on behalf of the N5GC device. Only one PDU session per N5GC device is supported. The procedure is the same as the PDU Session establishment procedure specified in clause 7.3.4 with the difference as below: + +After successful registration, PDU Session establishment/modification/release procedure specified in clause 7.3.4, 7.3.6, and 7.3.7 apply with the difference as below: + +- FN-RG is replaced by N5GC device. + +The W-AGF shall request the release of the NGAP connection for each N5GC device served by a CRG whose NGAP connection has been released. + +5G-CRG behaves as FN-CRG (i.e. L2 bridge mode) when handling N5GC devices. + +## 4.10b Differentiated services for NAUN3 devices behind 5G-RG + +NAUN3 devices cannot be authenticated by 5GC but may e.g. be locally authenticated by the 5G-RG using e.g. pre-shared secret. Differentiated services (QoS, network slicing) may be provided for NAUN3 devices as defined in this clause. + +"Connectivity Group IDs" may be defined on the 5G-RG where each Connectivity Group ID corresponds to a separate physical or virtual port on the 5G-RG. These ports could, for example, refer to separate physical ethernet ports and/or to separate WLAN SSIDs and/or to a separate VLAN. The devices that connect to a certain logical port are considered part of the same Connectivity Group ID. How this configuration on the 5G-RG is done is out of scope of this specification. + +Each Connectivity Group ID is then mapped to a separate PDU Session that is established by the 5G-RG based on the procedures defined in clause 7. The overall architecture is illustrated in Figure-4.10b-1. + +![Figure 4.10b-1: Example scenario for NAUN3 devices behind 5G-RG based on connectivity groups. The diagram shows a 5G-RG connected to an AMF (N1, N2), which is connected to an SMF (N11), which is connected to an ACS. The 5G-RG is also connected to three separate PDU Sessions (A, B, C) via its internal W-AGF / NG-RAN. Each PDU Session is connected to a separate UPF (N3, N6). The UPFs are connected to a cloud representing the data network. The 5G-RG is connected to three groups of devices: SSID 1 (laptop, printer, smartphone), SSID 2 (monitor, laptop, game controller), and RG-45 (lock, camera).](6929132b4964d52244da61d4614bc4d6_img.jpg) + +Figure 4.10b-1: Example scenario for NAUN3 devices behind 5G-RG based on connectivity groups. The diagram shows a 5G-RG connected to an AMF (N1, N2), which is connected to an SMF (N11), which is connected to an ACS. The 5G-RG is also connected to three separate PDU Sessions (A, B, C) via its internal W-AGF / NG-RAN. Each PDU Session is connected to a separate UPF (N3, N6). The UPFs are connected to a cloud representing the data network. The 5G-RG is connected to three groups of devices: SSID 1 (laptop, printer, smartphone), SSID 2 (monitor, laptop, game controller), and RG-45 (lock, camera). + +**Figure 4.10b-1: Example scenario for NAUN3 devices behind 5G-RG based on connectivity groups** + +The 5G-RG is configured with the (virtual) port information (e.g. VLANs and SSIDs) based on TR-69 [18], TR-360 and TR-181 [46]. URSP rules can be provided to the 5G-RG to indicate how to map Connectivity Group ID to the parameters of the PDU Session used to carry the traffic of corresponding devices e.g. DNN, S-NSSAI, etc. + +NOTE: In addition, the mapping between a "virtual port" and DNN/S-NSSAI can be configured via TR-69 [18]/TR-181 [46]. + +Whether and how the NAUN3 devices are configured to use a specific SSID or connect to a certain Ethernet port on the 5G-RG is out of scope of this specification. + +Differentiation of charging and QoS may be provided via PCC rules (for different service flows) related with dedicated PDU Sessions for NAUN3 devices. Isolation of devices using a specific Connectivity Group ID into a specific network slice, i.e. with separate S-NSSAI may also be provided. + +## 4.10c Authenticable Non-3GPP devices behind 5G-RG + +This clause defines the support of AUN3 devices, i.e. Authenticable Non-3GPP devices (AUN3) as defined in clause 3.1, behind a 5G-RG. This clause applies only to 5G-RG connected via wireline access. + +Figure 4.10c-1 shows the architecture for support of AUN3 device. + +![Figure 4.10c-1: AUN3 device behind 5G-RG. The diagram shows the network architecture for an AUN3 device connected to a 5G-RG. The 5G-RG is connected to a W-AGF (part of a W-5GAN). The W-AGF is connected to an AMF via N1 and N2 interfaces. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to an external network via N6. The AUN3 device is connected to the 5G-RG via a Yt' interface. The 5G-RG is also connected to the W-AGF via a Y4 interface.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +graph LR + AUN3[AUN3 device] -- Yt' --> 5GRG[5G-RG] + 5GRG -- Y4 --> WAGF[W-AGF] + subgraph W5GAN [W-5GAN] + WAGF + end + WAGF -- N1 --> AMF[AMF] + WAGF -- N2 --> AMF + AMF -- N11 --> SMF[SMF] + SMF -- N4 --> UPF[UPF] + UPF -- N6 --> External[External Network] + +``` + +Figure 4.10c-1: AUN3 device behind 5G-RG. The diagram shows the network architecture for an AUN3 device connected to a 5G-RG. The 5G-RG is connected to a W-AGF (part of a W-5GAN). The W-AGF is connected to an AMF via N1 and N2 interfaces. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to an external network via N6. The AUN3 device is connected to the 5G-RG via a Yt' interface. The 5G-RG is also connected to the W-AGF via a Y4 interface. + +**Figure 4.10c-1: AUN3 device behind 5G-RG** + +Differentiated services for AUN3 devices behind 5G-RG are provided as specified below: + +- Each AUN3 device has its own UDM/UDR subscription data including its own SUPI and policy control subscription data. +- The interface between 5G-RG and AUN3 devices is out of scope of 3GPP. +- In order to serve the AUN3 device in 5GC, a 5G-RG issues a NAS register and handles RM and CM related signalling on behalf of an AUN3 device that it is requesting to be served and relays EAP signalling between the AUN3 device and the 5GC. +- A 5G-RG serving an AUN3 device establishes a single PDU Session on behalf on this AUN3 device. +- The AMF and the 5G-RG maintain a separate NAS connection per AUN3 device. This includes maintaining a GUTI and NAS (RM, CM, security, etc.) context per AUN3 device. +- A 5G-RG shall be connected to the 5GC (be in RM-REGISTERED and CM-CONNECTED mode) over Wireline access to serve an AUN3 device: the 5G-RG shall not issue a NAS register or service request on behalf of an AUN3 device if it is itself not registered and connected to the 5GC. +- The 5G-RG is configured with URSP for each AUN3 devices it serves. The UE PCF selected by the AMF at the registration of an AUN3 device sends this URSP to 5G-RG via the AMF and the NAS connection of the AUN3 device. +- The AUN3 devices and the 5G-RG belong to the same PLMN. +- A 5G-RG uses default values, which are the same for all AUN3 devices it serves, to populate the parameters in the Registration Request message built on behalf of an AUN3 device. For example, the 5G-RG issues the Registration Request with no S-NSSAI and the AMF selects the default S-NSSAI in the subscription of the AUN3 device. +- There shall be a separate N2 connection per AUN3 device that is in state CM-CONNECTED. +- The W-AGF shall determine that a W-CP connection is for an AUN3 device and apply corresponding policies. The W-AGF indicates to the AMF when an N2 connection relates to an AUN3 device. + +NOTE 1: How the W-AGF determines the W-CP connection is for an AUN3 device is defined by BBF and CableLabs. + +- The same W-AGF shall serve a 5G-RG and all AUN3 devices connected via this 5G-RG. + +- The W-CP and W-UP protocols shall be able to manage multiple connections for different subscribers (the 5G-RG itself and the different AUN3 devices) between the same pair of 5G-RG and W-AGF. In particular, W-CP needs to be able to differentiate NAS messages related to a 5G-RG and to each different AUN3 device served by this 5G-RG and W-UP needs to distinguish between user plane packets for a 5G-RG and user plane packets for each different AUN3 device served by this 5G-RG. +- When the registration of an AUN3 device has successfully completed, the 5G-RG establishes a PDU Session on behalf of the AUN3 device. This PDU Session is handled by 5GC as part of the AUN3 subscription and is associated with the SUPI of AUN3 device. An AUN3 device can at a given time only use a single PDU Session. The parameters to establish this PDU session are based on the URSP (if any) for the AUN3 device. +- Different QoS parameters may apply to PDU sessions of different AUN3 devices. +- Roaming is not applicable to subscriptions for AUN3 devices. +- The RG Level Wireline Access Characteristics sent to the W-AGF for a 5G-RG may contain a maximum bit rate for the aggregated traffic of the 5G-RG and of the AUN3 devices served by this 5G-RG. The W-AGF uses this information to limit the maximum bit rate of the aggregated user plane traffic of the 5G-RG and of the AUN3 devices served by this 5G-RG. + +NOTE 2: The coding of the maximum bit rate in RG Level Wireline Access Characteristics is defined by BBF and CableLabs specifications. + +If W-AGF detects that a 5G-RG is unreachable, then W-AGF triggers the N2 UE context release. The W-AGF identifies if there exists any AUN3 device connected to the 5G-RG through the W-AGF. For each identified AUN3 device, the W-AGF invokes step 5 and 6 of Figure 7.2.8.3-1 which releases the PDU sessions of these AUN3 devices. + +## 4.10d Support of NSWO for 3GPP UE behind a RG + +NSWO as defined in clauses 4.2.15 and 5.42 of TS 23.501 [2] may be supported for UE(s) connected via a 5G-RG, and/or for UE(s) connected via a FN-RG. + +When this feature is supported, the RG and the W-5GAN need to support the WLAN Access functionality defined in clauses 4.2.15 and 5.42 of TS 23.501 [2]. The WLAN Access functionality includes the support of the SWa' interface to NSWOF. The SWa' support in Wireline access network has no impact on 3GPP specifications. + +NOTE: W-5GAN specifications and deployments can ensure that a AAA proxy is used to support SWa' interface with NSWOF(s) on behalf of RG(s). This can be used for FN-RG that do not support SWa'. This AAA proxy does not need to support the functionalities of a 3GPP AAA proxy defined in TS 23.402 [45]. + +When NSWO applies, the user plane traffic of the UE is not traversing the UE's 5GC. + +The specification of functionalities to support NSWO in the wireline access network is out of 3GPP scope including specifications on how the offloaded traffic is carried in W-5GAN and bypass the 5GC of the UE. + +The UE can also connect to 5GC using 5GS credentials as defined in clause 5.42 of TS 23.501 [2]. + +A 5G RG shall not issue authentication request over SWa' for the UE if it is itself not registered to 5GC. + +## 4.11 Fixed Wireless Access + +For the 5G-RG connected to 5GC via NG-RAN the specifications defined TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] applies with the following modification: + +- The UE corresponds to the 5G-RG. +- The 5G-RG may support LTE access connected to EPC and EPC interworking as defined in TS 23.501 [2], clause 5.17. This is controlled by SMF Selection Subscription data defined in Table 5.2.3.3.1-1 of TS 23.502 [3]. +- The configuration of 5G-RG via ACS server based on TR-069 [18] and TR-369 [19] is specified clause 9.6. +- The Home Routing roaming is supported for 5G-RG connected via NG RAN in this release. + +- 5G Multi-Operator Core Network (5G MOCN) is supported for 5G-RG connected via NG RAN as defined in clause 5.18 of TS 23.501 [2] +- The LBO roaming for 5G-RG connected via NG RAN is not specified in this release. +- The LADN service defined in clause 5.6.5 in TS 23.501 [2] applies to the 5G-RG connected to 5GC via 3GPP access. The specification in clause 5.6.5 in TS 23.501 [2] applies via 5G-RG replacing UE with the following difference: + - UE Configuration Update procedure is referred to the procedures in clause 7.2.3.1. + +NOTE 1: HR roaming over 3GPP access is defined for 5G\_RG but in some countries it can not apply due to local regulations. + +- If the 5G-RG is registered via both 3GPP access and W-5GAN, and the AMF has received W-AGF identities from the AGF, the AMF may provide the W-AGF identities to the SMF also when AMF forwards N1 SM container sent by the 5G-RG via 3GPP access. + +NOTE 2: If the SMF receives the W-AGF information also in case of 5G-RG sending a PDU Session Establishment via 3GPP access, based on operator configuration, the SMF can take this into account for selecting a UPF collocated with the W-AGF. + +## 4.12 Hybrid Access + +### 4.12.1 General + +This clause specifies the support of Hybrid Access considering both the support of PDU session and MA PDU session. + +Hybrid Access applies to a 5G-RG capable of connecting to both NG-RAN and to W-5GAN. Hybrid Access also applies to a 5G-RG capable of connecting to W-5GAN/5GC and E-UTRAN/EPC using EPC interworking architecture. Hybrid Access does not apply to FN-RG. + +The following Hybrid Access scenarios are supported with single-access PDU sessions: + +- Hybrid Access using PDU session carried only on a single access, either NG-RAN or W-5GAN, but that cannot be simultaneously on both accesses. Such PDU Session can be handed over between NG-RAN and W-5GAN using procedures described in clause 4.9.2 of TS 23.502 [3], but with UE replaced by 5G-RG and N3IWF replaced by W-5GAN. +- Hybrid Access using single access connectivity for 5G-RG supporting LTE/EPC and EPC interworking. In that case mobility between W-5GAN/5GS and E-UTRAN/EPC is handled using interworking procedures described in clause 4.11.3 of TS 23.502 [3], but with UE replaced by 5G-RG and N3IWF replaced by W-5GAN. + +The following Hybrid Access scenarios are supported with multi-access connectivity: + +- Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN and operator-controlled traffic steering. This scenario is further detailed in clause 4.12.2. +- Hybrid Access with simultaneous multi-access connectivity to LTE/EPC and W-5GAN/5GS using EPC interworking. This scenario is further detailed in clause 4.12.3. + +In this Release of the specification, a RG that supports MA PDU Sessions and LTE/EPC access as described in clause 4.12.2, shall also support MA PDU using LTE/EPC as 3GPP access as defined in clause 4.12.3. + +### 4.12.2 Hybrid Access with Multi-Access PDU Session connectivity over NG-RAN and W-5GAN + +This clause applies to the case where multi-access PDU Session connectivity via NG-RAN and W-5GAN is supported in the 5G-RG and network. The Hybrid Access architecture of 5G-RG is defined in TS 23.501 [2] in Figure 4.2.8.4-1. This scenario uses the ATSSS solution described in clause 5.33 of the Release 16 version of TS 23.501 [2], with the following difference: + +- UE is replaced by 5G-RG. +- Non-3GPP access(es) is specifically referred to wireline access. + +The Release 17, ATSSS functionalities defined in TS 23.501 [2], TS 23.502 [3] and TS 23.503 [4] are not supported, except for the feature described in clause 4.12.3. + +### 4.12.3 Hybrid Access with multi-access connectivity over E-UTRAN/EPC and W-5GAN + +#### 4.12.3.1 General + +This clause applies to the case where multi-access connectivity via both EPC and 5GC is supported in the 5G-RG and network. In this case, multi-access connectivity using ATSSS via both EPC and 5GC may be provided as described in this clause. + +For a 5G-RG, a Multi-Access PDU Session may use user-plane resources of an associated PDN Connection on 3GPP access in EPC. This enables a scenario where a MA PDU Session can simultaneously be associated with user-plane resources on 3GPP access network connected to EPC and W-5GAN connected to 5GC. Such a PDN Connection in EPS would thus be associated with multi-access capability in 5G-RG and PGW-C+SMF. + +The feature is supported as defined in clause 5.32 of TS 23.501 [2] (Release 17) and TS 23.502 [3] (Release 17) with following differences: + +- UE is replaced by 5G-RG. +- 5G-RG is connected to 5GC via a non-3GPP access corresponding to W-5GAN. +- MA PDU Sessions of Ethernet PDU Session type where the 3GPP access corresponds to E-UTRAN/EPC are not applicable for 5G-RG. + +#### 4.12.3.2 Void + +#### 4.12.3.3 Void + +## 4.13 Support of FN-RG + +FN-RG is a legacy type of residential gateway that does not support N1 signalling and is not 5GC capable. The architecture to support FN-RG is depicted in clause 4.2.8.4 in TS 23.501 [2]. Support for FN-RG connectivity to 5GC is provided by means of W-AGF supporting 5G functionality on behalf of the FN-RG, e.g. UE NAS registration and session management functionality. In particular, the W-AGF supports the following functionality on behalf of the FN-RG: + +- Has access to configuration information, as defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27], to be able to serve FN-RGs and to construct AS and NAS messages. +- Acting as end-point of N1 towards AMF, including maintaining CM and RM states and related dynamic information received from 5GC. This also includes support of URSP. +- Mapping between Y5 towards FN-RG and N1/N2 towards 5GC as well as mapping between a Y5 user plane connection and a PDU Session user plane tunnel on N3. + +Authentication of FN-RG may be done by the W-AGF, as defined by BBF and Cablelabs. The W-AGF provides an indication on N2 that the FN-RG has been authenticated. The W-AGF also provides a SUCI or a 5G-GUTI as described in TS 23.501 [2]. + +## 4.14 Support of slicing + +Slicing as defined in TS 23.501 [2] is supported with following clarifications and modifications: + +- 5G-RG may receive USRP rules mapping application flows to S-NSSAI (and other 5GC related parameters). For 5G-RG, the detection of application flows may refer to traffic from devices within the customer premises. + +NOTE: In this case, even though an URSP rule refers to the IP PDU Session type, Non-IP Traffic descriptors e.g. layer 2 related Traffic descriptors can be used to identify application flows. + +- For 5G-RG access over 3GPP access (FWA), slicing is supported as described in TS 23.501 [2]. +- For 5G-RG access over Wireline, the Wireline access is assumed to be able to carry slicing information in W-CP together with NAS signalling between the 5G-RG and the W-AGF. +- The W-AGF shall support the same requirements for AMF selection based on slicing request from the UE than defined for N3IWF / TNGF in TS 23.501 [2] clause 5.15. + +## 4.15 Support for IMS services + +When FN RG is used, support IMS Emergency sessions without a SUPI are not supported. + +## 4.16 Access to non-public networks via wireline access network + +### 4.16.1 Access to SNPN services via wireline access network + +Access to SNPN defined in clause 5.30 of TS 23.501 [2] via a wireline access network follows the same specification and procedures used for accessing a PLMN via a wireline access with the following modifications: + +- The SNPN is implicitly selected by wired physical connectivity between 5G-RG or FN-RG and W-AGF. +- In the case of 5G-RG connected via FWA, the 5G-RG shall support the capability defined for the SNPN-enabled UE as specified in clauses 5.30.2.3 and 5.30.2.4.1 of TS 23.501 [2] where the UE is replaced by 5G-RG. +- The access to SNPN via FN-CRG is supported as follows: the W-AGF is configured to use a SNPN Identifier (as defined in clause 5.30.2.1 of TS 23.501 [2]) instead of a PLMN Identifier in the procedure for FN-CRG Registration via W-5GAN defined in clause 7.2.1.3. The access to SNPN via FN-BRG is not supported in this Release. +- The SUPI for a 5G-CRG containing IMSI is described in clause 5.9.2 of TS 23.501 [2]. The SUPI in NSI type may include the NID of SNPN as defined in clause 28.7.2 of TS 23.003 [14]. +- The SUPI for a 5G-CRG and FN-CRG containing GCI is specified in clause 4.7.4 and in clause 28.15.2 of TS 23.003 [14]. The realm part of NAI format for a SUPI containing a GCI identifying the operator owning the subscription may include the NID of the SNPN. +- The SUPI for a 5G-BRG and FN-BRG containing GLI is specified in clauses 4.7.2, 4.7.3 and 28.16.2 of TS 23.003 [14]. The realm part of NAI format for a SUPI containing a GLI identifying the operator owning the subscription may include the NID of the SNPN. +- RG using credentials owned by a Credentials Holder separate from the SNPN is not applicable. UE behind RG accessing to SNPN via N3IWF or TNGF as defined in clause 4.10 with credentials owned by Credentials Holder is supported as specified in clause 5.30.2.9 of TS 23.501 [2] where the Credentials Holder's AAA server or AUSF are reachable via N3IWF or TNGF. The support of UE behind a RG accessing to SNPN with credentials owned by Credentials Holder directly reachable from RG, i.e. without N3IWF and TNGF, is not specified in this Release. +- The onboarding procedure specified in clause 5.30.2.10 of TS 23.501 [2] is not applicable in this Release for a RG. + +### 4.16.2 Access to Public Network Integrated NPN services via wireline access network + +Considering that the Public Network Integrated NPNs are NPNs made available via PLMNs e.g. by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN and that the W-AGF may support more than one network slices and different W-AGFs may support different sets of network slices, therefore the access to PNI-NPN defined in clause 5.30 of TS 23.501 [2] via a wireline access network applies with the following modifications: + +- In case of 5G-RG and FN-RG connected via wired physical connectivity to W-AGF the Closed Access Group does not apply to 5G-RG/FN-RG and to W-AGF. The access restriction is implicitly applied since the RG's subscription information includes only the relevant network slice(s) (i.e. the network slice(s) related to PLMN and NPI-NPN subscribed) and the fact the 5G-RG/FN-RG is physically connected to W-AGF implies that the subscribed slice(s) are applicable from the user physical location. +- In the case of 5G-RG connected via FWA, the 5G-RG may support the CAG procedure as specified in clause 5.30.3 of TS 23.501 [2] where the 5G-RG replaces the UE. + +NOTE: The connection via FWA is not applicable to a FN-RG. + +# --- 5 Network Function + +## 5.0 General + +This clause specifies the definition network function specific for W-AGF and the delta to network function defined in TS 23.501 [2]. + +## 5.1 Network Function Functional description + +### 5.1.1 W-AGF + +The functionality of W-AGF in the case of Wireline 5G Access network includes the following: + +- Termination of N2 and N3 interfaces to 5G Core Network for control - plane and user-plane respectively. +- Handling of N2 signalling from SMF (relayed by AMF) related to PDU Sessions and QoS. +- Relaying uplink and downlink user-plane packets between the 5G-RG and UPF and between FN-RG and UPF. This involves: + - Enforcing QoS corresponding to N3 packet marking, taking into account QoS requirements associated to such marking received over N2. + - N3 user-plane packet marking in the uplink. +- Supporting AMF discovery and selection defined in TS 23.501 [2] clause 6.3.5 where the 5G-S-TMSI is not used for AMF selection since the wireline AS layer can only carry the GUAMI. +- Termination of wireline access protocol on Y4 and Y5. +- In the case of FN-RG the W-AGF acts as end point of N1 on behalf of the FN-RG. + +In the case of Wireline 5G Broadband Access network the definition of W-AGF functionalities is specified in BBF TR-456 [9] and WT-457 [10]. + +NOTE: The W-AGF is specified as AGF (Access Gateway Function) in BBF TR-456 [9] for supporting 5G-RG and FN-RG and as FMIF (Fixed Mobile Interworking Function) for supporting FN-RG only in the case of presence of BNG in WT-457 [10]. Both cases for FN-RG support, i.e. AGF and FMIF, have identical interfaces towards 5GC, i.e. it is transparent to 5GC whether AGF or FMIF is used and no difference between AGF or FMIF cases is defined in this specification. + +In the case of Wireline 5G Cable Access network the definition of W-AGF functionalities is specified by Cablelabs WR-TR-5WWC-ARCH [27]. + +# 6 Control and User Plane Protocol Stacks + +## 6.1 General + +This clause specifies the protocol stacks between 5G-RG, FN-RG and 5GS entities for supporting W-5GAN. + +## 6.2 Control Plane Protocol Stacks for W-5GAN + +### 6.2.1 Control Plane Protocol Stacks between the 5G-RG and the 5GC + +![Figure 6.2.1-1: Control Plane stack for W-5GAN for 5G-RG. The diagram shows the protocol stack between a 5G-RG and an AMF, with a W-AGF acting as a relay. The 5G-RG stack consists of NAS and W-CP. The W-AGF stack consists of W-CP, NG-AP, SCTP, IP, L2, and L1. The AMF stack consists of NAS, NG-AP, SCTP, IP, L2, and L1. The W-CP stack in the 5G-RG is connected to the W-CP stack in the W-AGF via the Y4 interface. The W-CP stack in the W-AGF is connected to the NG-AP stack in the W-AGF via the N2 interface. The NG-AP stack in the W-AGF is connected to the NG-AP stack in the AMF via the N2 interface.](1841f348dfa81a3438d4e1f8465d9ac7_img.jpg) + +Figure 6.2.1-1: Control Plane stack for W-5GAN for 5G-RG. The diagram shows the protocol stack between a 5G-RG and an AMF, with a W-AGF acting as a relay. The 5G-RG stack consists of NAS and W-CP. The W-AGF stack consists of W-CP, NG-AP, SCTP, IP, L2, and L1. The AMF stack consists of NAS, NG-AP, SCTP, IP, L2, and L1. The W-CP stack in the 5G-RG is connected to the W-CP stack in the W-AGF via the Y4 interface. The W-CP stack in the W-AGF is connected to the NG-AP stack in the W-AGF via the N2 interface. The NG-AP stack in the W-AGF is connected to the NG-AP stack in the AMF via the N2 interface. + +**Figure 6.2.1-1: Control Plane stack for W-5GAN for 5G-RG** + +The control plane protocol stack between 5G-RG and AMF is defined in figure 6.2.1-1. + +For W-5GBAN, the W-CP protocol stack between 5G-BRG and W-AGF is defined in BBF TR-456 [9]. For W-5GCAN, the W-CP protocol stack between 5G-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27]. + +The protocol stack between 5GC/AMF and W-AGF is defined in TS 23.501 [2] clause 8. + +The W-CP protocol stack: + +- supports transfer of NAS signalling between the 5G-RG and the W-AGF; +- supports to carry AS parameters (e.g. SUCI or 5G-GUTI, Requested NSSAI and Establishment Cause) and NAS packets; +- supports the setup, modification and removal of at least one W-UP resource per PDU session; +- may support the setup, modification and removal of multiple W-UP resources per PDU session. + +For the 5G-RG connected via NG-RAN the protocol stack defined in TS 23.501 [2] clause 8.2.2 applies with UE corresponding to 5G-RG. + +### 6.2.2 Control Plane Protocol Stacks between the FN-RG and the 5GC + +![Figure 6.2.2-1: Control Plane stack for W-5GAN for FN-RG. The diagram shows three main entities: FN-RG, W-AGF, and AMF, connected via Y5 and N2 interfaces. The FN-RG contains an L-W-CP block. The W-AGF contains an L-W-CP block and a protocol stack with layers NAS, NG-AP, SCTP, IP, L2, and L1. The AMF contains a protocol stack with layers NAS, NG-AP, SCTP, IP, L2, and L1. The L-W-CP block in the FN-RG is connected to the L-W-CP block in the W-AGF at the Y5 interface. The W-AGF's protocol stack is connected to the AMF's protocol stack at the N2 interface.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +Figure 6.2.2-1: Control Plane stack for W-5GAN for FN-RG. The diagram shows three main entities: FN-RG, W-AGF, and AMF, connected via Y5 and N2 interfaces. The FN-RG contains an L-W-CP block. The W-AGF contains an L-W-CP block and a protocol stack with layers NAS, NG-AP, SCTP, IP, L2, and L1. The AMF contains a protocol stack with layers NAS, NG-AP, SCTP, IP, L2, and L1. The L-W-CP block in the FN-RG is connected to the L-W-CP block in the W-AGF at the Y5 interface. The W-AGF's protocol stack is connected to the AMF's protocol stack at the N2 interface. + +**Figure 6.2.2-1: Control Plane stack for W-5GAN for FN-RG** + +The control plane protocol stack between FN-RG and AMF is defined in figure 6.2.2-1. The W-AGF acts as an N1 termination point on behalf of FN-RG. + +For W-5GBAN, the L-W-CP protocol stack, between FN-BRG and W-AGF is defined in BBF TR-456 [9] and WT-457 [10]. For W-5GCAN, the L-W-CP protocol stack between FN-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27]. + +## 6.3 User Plane Protocol Stacks for W-5GAN + +### 6.3.1 User Plane Protocol Stacks between the 5G-RG and the 5GC + +![Figure 6.3.1-1: User Plane stack for W-5GAN for 5G-RG. The diagram shows the user plane protocol stack across four entities: 5G-RG, W-AGF, UPF, and UPF (PDU Session Anchor), connected via N3, N9, and N6 interfaces. The 5G-RG contains Application, PDU Layer, and W-UP blocks. The W-AGF contains a Relay block, a W-UP block, and a protocol stack with layers GTP-U, UDP/IP, L2, and L1. The UPF contains a Relay block, a GTP-U block, and a protocol stack with layers GTP-U, UDP/IP, L2, and L1. The UPF (PDU Session Anchor) contains a PDU Layer and a protocol stack with layers GTP-U, UDP/IP, L2, and L1. The 5G-RG's W-UP block is connected to the W-AGF's W-UP block at the N3 interface. The W-AGF's protocol stack is connected to the UPF's protocol stack at the N9 interface. The UPF's protocol stack is connected to the UPF (PDU Session Anchor)'s protocol stack at the N6 interface.](05d8710f69c476939295486ab1440350_img.jpg) + +Figure 6.3.1-1: User Plane stack for W-5GAN for 5G-RG. The diagram shows the user plane protocol stack across four entities: 5G-RG, W-AGF, UPF, and UPF (PDU Session Anchor), connected via N3, N9, and N6 interfaces. The 5G-RG contains Application, PDU Layer, and W-UP blocks. The W-AGF contains a Relay block, a W-UP block, and a protocol stack with layers GTP-U, UDP/IP, L2, and L1. The UPF contains a Relay block, a GTP-U block, and a protocol stack with layers GTP-U, UDP/IP, L2, and L1. The UPF (PDU Session Anchor) contains a PDU Layer and a protocol stack with layers GTP-U, UDP/IP, L2, and L1. The 5G-RG's W-UP block is connected to the W-AGF's W-UP block at the N3 interface. The W-AGF's protocol stack is connected to the UPF's protocol stack at the N9 interface. The UPF's protocol stack is connected to the UPF (PDU Session Anchor)'s protocol stack at the N6 interface. + +**Figure 6.3.1-1: User Plane stack for W-5GAN for 5G-RG** + +The user plane protocol stack between 5G-RG and UPF is defined in figure 6.3.1-1. + +For W-5GBAN, the W-UP protocol stack between 5G-BRG and W-AGF is defined in BBF TR-456 [9]. For W-5GCAN, the W-UP protocol stack between 5G-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27]. + +The protocol stack between 5GC/UPF and W-AGF is defined in TS 23.501 [2] clause 8. + +For the W-UP protocol stack: + +- W-UP supports at least one W-UP resource per PDU session. This will be the default W-UP resource. +- W-UP may support multiple W-UP resources per PDU session and associate different QoS profiles (QFIs) to different W-UP resources. +- W-UP supports transmission of uplink and downlink PDUs according to clause 4.5. +- W-UP supports access specific QoS parameters that can be mapped from 3GPP QoS parameters (e.g. 5QI, RQI) received from the 5GC. + +For the 5G-RG connected via NG-RAN the protocol stack defined in TS 23.501 [2] clause 8.3.1 applies with 5G-RG replacing the UE. + +### 6.3.2 User Plane Protocol Stacks between the FN-RG and the 5GC + +![Figure 6.3.2-1: User Plane stack for W-5GAN for FN-RG. The diagram shows the protocol stack across four entities: FN-RG, W-AGF, UPF, and UPF (PDU Session Anchor). The FN-RG stack includes Application, PDU Layer, and L-W-UP. The W-AGF stack includes a Relay, L-W-UP, GTP-U, UDP/IP, L2, and L1. The UPF stack includes a Relay, GTP-U, UDP/IP, L2, and L1. The UPF (PDU Session Anchor) stack includes PDU Layer, GTP-U, UDP/IP, L2, and L1. Interfaces N3, N9, and N6 are indicated between the entities.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +Figure 6.3.2-1: User Plane stack for W-5GAN for FN-RG. The diagram shows the protocol stack across four entities: FN-RG, W-AGF, UPF, and UPF (PDU Session Anchor). The FN-RG stack includes Application, PDU Layer, and L-W-UP. The W-AGF stack includes a Relay, L-W-UP, GTP-U, UDP/IP, L2, and L1. The UPF stack includes a Relay, GTP-U, UDP/IP, L2, and L1. The UPF (PDU Session Anchor) stack includes PDU Layer, GTP-U, UDP/IP, L2, and L1. Interfaces N3, N9, and N6 are indicated between the entities. + +Figure 6.3.2-1: User Plane stack for W-5GAN for FN-RG + +The user plane protocol stack between FN-RG and UPF is defined in figure 6.3.2-1. + +For W-5GBAN, the L-W-UP protocol stack between FN-BRG and W-AGF is defined in BBF TR-456 [9] and WT-457 [10]. For W-5GCAN, the L-W-UP protocol stack between FN-CRG and W-AGF is defined in WR-TR-5WWC-ARCH [27]. + +# 7 System procedure + +## 7.1 General + +This clause describes the differences in respect the procedures defined in TS 23.502 [3] clause 4. + +## 7.2 Connection, Registration and Mobility Management procedures + +The listed parameters in the procedures are not exhaustive, but more parameters can be used as described in the protocol specifications. + +Where parameters have not been described, the meaning of the parameter is the same as for 3GPP access as described in TS 23.502 [3], TS 24.501 [22], TS 38.413 [23]. + +### 7.2.1 Registration Management procedures + +This clause specifies delta for Registration Management procedure defined in TS 23.502 [3] clause 4.2 for 5G-RG and FN-RG. + +#### 7.2.1.1 5G-RG Registration via W-5GAN + +The 5G-RG registration management procedures are followed for both W-5GBAN and W-5GCAN. + +Clause 7.2.1.1 specifies how a 5G-RG can register to 5GC via aW-5GAN. It is based on the Registration procedure specified in TS 23.502 [3] clause 4.2.2.2.2. The NAS protocol is transported between 5G-RG and W-AGF as documented in BBF TR-456 issue 2 [43] and CableLabs WR-TR-5WWC-ARCH [27]. If the 5G-RG needs to be authenticated, mutual authentication is executed between the 5G-RG and AUSF. The details of the authentication procedure are specified in TS 33.501 [11]. In Registration and subsequent Registration procedures via W-5GAN access, the NAS messages are always exchanged between the 5G-RG and the AMF. When possible, the 5G-RG can be authenticated by reusing the existing UE security context in AMF for the 5G-RG. + +Figure 7.2.1.1-1 only shows authentication flow using EAP-AKA' (specifically in step 6c, step 7a and step 7b) but other methods are possible: Authentication procedures that 5G-RG and the 5GC shall support, are specified in TS 33.501 [11]. Specific EAP authentication methods (see TS 33.501 [11]) for 5G-CRG with non-3GPP identities and credentials may be used for isolated network (see TS 33.501 [11]). + +![Sequence diagram for 5G-RG Registration via W-5GAN. Lifelines: 5G-RG, W-AGF, AMF, AUSF. The process involves W-CP connection establishment, AN-Params transfer, AMF Selection, N2 Initial UE message, Authentication and Security, SMC Request/Complete, Identity Req/Res., N2 Initial Ctx Request/Response, and NAS Registration Accept/Complete. Some steps are grouped into blocks referencing TS 23.502.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-AGF + participant AMF + participant AUSF + + Note right of AMF: EIR, UDM, PCF + + 5G-RG->>W-AGF: 1. W-CP connection establishment + 5G-RG->>W-AGF: 3. W-CP (AN-Params [GUAMI, Selected PLMN ID, Requested NSSAI], NAS-PDU [Registration Request]) + W-AGF->>AMF: 4a. AMF Selection + W-AGF->>AMF: 4b. N2 Initial UE message (NAS: Registration Request) + AMF-->>W-AGF: 5a. N2 Downlink/Uplink NAS (Identity Req./Res.) + W-AGF-->>5G-RG: 5b. W-CP (NAS-PDU [Identity Req./Res.]) + + Note over 5G-RG, AMF, AUSF: 6. Authentication and Security + + AMF->>W-AGF: 7a. N2 Downlink NAS (SMC Request [EAP-Success]) + W-AGF-->>5G-RG: 7b. W-CP (NAS-PDU [SMC Request (EAP-Success)]) + 5G-RG->>W-AGF: 7c. W-CP (NAS-PDU [SMC Complete]) + W-AGF->>AMF: 7d. N2 Uplink NAS (SMC Complete) + + AMF->>W-AGF: 8. N2 Downlink/Uplink NAS (Identity Req./Res.) + W-AGF-->>5G-RG: 8. W-CP (NAS-PDU [Identity Req./Res.]) + + Note right of AMF: Step 9: Perform step 12-16 in TS 23.502, clause 4.2.2.2.2-1 + AMF->>W-AGF: 10. N2 Initial Ctx Request (W-AGF key) + W-AGF->>AMF: 12. N2 Initial Ctx Response + + AMF->>W-AGF: 13a. N2 Downlink NAS (NAS Registration Accept) + W-AGF-->>5G-RG: 13b. W-CP (NAS-PDU [Registration Accept]) + 5G-RG->>W-AGF: 14a. W-CP (NAS-PDU [Registration Complete]) + W-AGF->>AMF: 14b. N2 Uplink NAS (Registration Complete) + + Note right of AMF: Step 15: Step 23-24 in TS 23.502, clause 4.2.2.2.2-1 + +``` + +Sequence diagram for 5G-RG Registration via W-5GAN. Lifelines: 5G-RG, W-AGF, AMF, AUSF. The process involves W-CP connection establishment, AN-Params transfer, AMF Selection, N2 Initial UE message, Authentication and Security, SMC Request/Complete, Identity Req/Res., N2 Initial Ctx Request/Response, and NAS Registration Accept/Complete. Some steps are grouped into blocks referencing TS 23.502. + +Figure 7.2.1.1-1: 5G-RG Registration via W-5GAN + +1. The 5G-RG connects to a W-5GAN with procedures outside the scope of 3GPP and creates an initial signalling connection using W-CP protocol stack. This connection shall support transfer of AS parameters and NAS messages between 5G-RG and W-AGF. +2. Void. +3. The 5G-RG using W-CP protocol stack sends a message that contains the Access Network parameters (GUAMI if available, the selected PLMN or SNPN, Requested NSSAI and Establishment Cause) and a NAS Registration Request message (SUCI or 5G-GUTI as defined in TS 24.501 [22], security parameters/UE security capability, NSSAI parameters, UE MM Core Network Capability, PDU session status, Follow-on request). The Establishment cause provides the reason for requesting a signalling connection with 5GC. + +NOTE 1: While PLMN or SNPN selection is not supported for W-5GAN access, the 5G RG provides a selected PLMN or SNPN ID in Access Network parameters sent to the W-AGF. In this version of the specifications, this selected PLMN or SNPN ID is the home domain of the SUCI. This information is transparently transferred from 5G RG to AUSF via the W-AGF and the AMF; it ensures the AUSF and the 5G RG consider the same information for Key derivations defined in TS 33.501 [11]. + +NOTE 2: The steps from 1 to 3 depend on BBF decision for what protocols to use for NAS transport. The step needs to be revised based on their decision. + +4. The W-AGF shall select an AMF based on the received AN parameters and local policy, as specified in clause 6.3.5 of TS 23.501 [2]. The W-AGF shall then forward the Registration Request received from the UE to the selected AMF within an N2 initial UE message (NAS message, ULI, Establishment cause, UE context request, selected PLMN or SNPN ID). +5. The selected AMF may decide to request the SUCI by sending a N2 Downlink NAS transport message (NAS Identity Request) message to W-AGF. This NAS message and the response are sent between W-AGF and 5G-RG as described in BBF TR-456 [43] and CableLabs WR-TR-5WWC-ARCH [27]. In this case the RG shall answer with a NAS Identity response. +6. The AMF may decide to authenticate the 5G-RG by invoking an AUSF. In this case, the AMF shall select an AUSF as specified in TS 23.501 [2] clause 6.3.4 based on SUPI or SUCI. As defined in 33.501 [11], the AMF transfers the SUCI and the selected PLMN or SNPN ID to the AUSF. + +The AUSF executes the authentication of the UE as specified in TS 33.501 [11]. The AUSF selects a UDM as described in clause 6.3.8 of TS 23.501 [2] and gets the authentication data from UDM. The authentication packets are encapsulated within NAS authentication messages. Between W-AGF and AMF, the messages are encapsulated within N2 downlink/uplink NAS transport messages. After the successful authentication the AUSF provides relevant security related information to the AMF. If the AMF provided a SUCI to AUSF, the AUSF shall return the SUPI to AMF only after the authentication is successful. + +The AMF decides if the Registration Request needs to be rerouted as described in clause TS 23.502 [3] clause 4.2.2.2.3, where the initial AMF refers to the AMF. + +- 7a. If NAS security context does not exist, the NAS security initiation is performed as described in TS 33.501 [11]: the AMF initiates NAS Security Mode command. If the 5G-RG had no NAS security context in step 1, the UE includes the full Registration Request message as defined in TS 24.501 [22]. If an EAP-AKA' authentication was successfully executed in step 6, the AMF shall encapsulate the EAP-Success received from AUSF within the NAS Security Mode Command message. The message is encapsulated within a N2 downlink NAS transport message. + +The AMF initiates a NGAP/N2 procedure to provide the 5G-AN with security context as specified in TS 38.413 [23]. + +- 7b. The W-AGF shall forward the NAS Security Mode Command message to 5G-RG. +- 7c. The 5G-RG completes the authentication procedure (if initiated in step 6), creates a NAS security context as defined in TS 33.501 [11] and sends the NAS Security Mode Complete message (IMEISV) to the AMF. +- 7d. The W-AGF relays the NAS Security Mode Complete message to the AMF in a N2 Uplink NAS transport message. +8. [Conditional] The AMF may request the PEI from the 5G-RG as described in clause 4.2.2.2.2, step 11 of TS 23.502 [3]. +9. The AMF performs step 12-16 in TS 23.502 [3] clause 4.2.2.2.2. At AMF registration to UDM for the 5G-RG, the Access Type non-3GPP access is used. The RAT type used toward PCF and UDM shall indicate wireline access. The AMF determines Access Type and RAT Type based on the Global RAN Node ID associated with the N2 interface. +10. The AMF sends an N2 Initial Context Setup Request message as defined in TS 38.413 [23] and TS 29.413 [42] possibly including as additional W-AGF specific parameter the RG Level Wireline Access Characteristics. +- 11a. Void. +- 11b. Void. +12. W-AGF notifies the AMF that the 5G-RG context was created by sending a N2 Initial Context Setup Response. +13. The AMF sends N2 Downlink NAS transport with the NAS Registration Accept message (as defined in step 21 TS 23.502 [3] clause 4.2.2.2.2) to the W-AGF, which forwards the NAS Registration accept message to the 5G-RG. +14. [Conditional] The 5G-RG responds with NAS Registration Complete message as described in TS 23.502 [3] clause 4.2.2.2.2 step 22 and W-AGF forwards the NAS Registration Complete message to AMF in a N2 Uplink + +NAS transport message. The N2 Uplink NAS transport message to AMF may contain W-AGF identities. The AMF stores the received W-AGF identities in the UE context. + +NOTE 3: The W-AGF identities contains a list of Identifiers (i.e. a list of FQDN and/or IP address(es)) of N3 terminations at W-AGF and can be used by SMF as input to select an UPF during PDU Session Establishment, as described in clauses 7.3.1.1 and 7.3.4. + +15. The AMF performs step 23-24 in TS 23.502 [3] clause 4.2.2.2.2. + +#### 7.2.1.2 5G-RG Deregistration via W-5GAN + +![Sequence diagram for 5G-RG Deregistration procedure via W-5GAN. The diagram shows interactions between 5G-RG, W-AGF, AMF, SMF, UPF, and PCF. It is divided into two main parts: 1a. UE-Initiated Deregistration procedure (steps 1 to 7) and 1b. Network Initiated deregistration procedure (steps 1 to 6). Both parts are enclosed in dashed boxes. Below these, the sequence continues with: 1. W-CP signalling connection release (between 5G-RG and W-AGF), 2. N2 UE Context Release Command (from AMF to W-AGF), 3. W-CP signalling connection release (between 5G-RG and W-AGF), and 4. N2 UE Context Release Complete (from W-AGF to AMF).](26e334e61dd059cff029338a2a604d8d_img.jpg) + +Sequence diagram for 5G-RG Deregistration procedure via W-5GAN. The diagram shows interactions between 5G-RG, W-AGF, AMF, SMF, UPF, and PCF. It is divided into two main parts: 1a. UE-Initiated Deregistration procedure (steps 1 to 7) and 1b. Network Initiated deregistration procedure (steps 1 to 6). Both parts are enclosed in dashed boxes. Below these, the sequence continues with: 1. W-CP signalling connection release (between 5G-RG and W-AGF), 2. N2 UE Context Release Command (from AMF to W-AGF), 3. W-CP signalling connection release (between 5G-RG and W-AGF), and 4. N2 UE Context Release Complete (from W-AGF to AMF). + +**Figure 7.2.1.2-1: 5G-RG Deregistration procedure via W-5GAN** + +1. The Deregistration procedure is triggered by one of the events: + +1a. For 5G-RG-initiated Deregistration as in Figure 4.2.2.3.2-1, steps 1 to 7 of TS 23.502 [3]. + +1b. For network initiated deregistration as in Figure 4.2.2.3.3-1, steps 1 to 6 of TS 23.502 [3]. + +If the 5G-RG is in CM-CONNECTED state either in 3GPP access, W-5GAN access or both: + +- the AMF may explicitly deregister the 5G-RG by sending a Deregistration request message (Deregistration type, access type set to -W-5GAN) to the 5G-RG as in Figure 4.2.2.3.3-1, step 2 of TS 23.502 [3]. The 5G-RG will interpret access type set to non-3GPP as referring to wireline access. + +- the UDM may want to request the deletion of the subscribers RM contexts and PDU Sessions with the reason for removal set to subscription withdrawn to the registered AMF as in Figure 4.2.2.3.3-1, step 1 of TS 23.502 [3]. + +2. AMF to W-AGF: The AMF sends a N2 UE Context Release Command message to the W-AGF with the cause set to Deregistration to release N2 signalling as defined in clause 4.12.4.2, step 4 of TS 23.502 [3]. + +3. The W-AGF may initiate the release of the signalling connection between 5G-RG and W-AGF. + +NOTE: Whether this step is needed, and if so, the details of this step is defined by BBF. + +4. W-AGF to AMF: The W-AGF acknowledges the N2 UE Context Release Command message by sending N2 UE Context Release Complete message to the AMF as defined in clause 4.12.4.2, step 7 of TS 23.502 [3]. + +#### 7.2.1.3 FN-RG Registration via W-5GAN + +The FN-RG registration management procedures are followed for both W-5GBAN and W-5GCAN. The FN-RG does not support N1 but instead the W-AGF handles the NAS signalling on behalf of the FN-RG as defined by BBF TR-456 [9] and WT-457 [10] for FN-BRG and by WT-TR-5WWC-ARCH [27] for FN-CRG. + +When the connectivity is established between the FN-RG and the W-AGF in the W-5GAN, the W-AGF may authenticate the FN-RG; this is controlled by local policies and defined in BBF specifications. Then when the RM state of the FN-RG is "RM-DEREGISTERED" the W-AGF shall perform registration to 5GC as described in this clause, otherwise it performs Service Request as defined in clause 7.2.2. + +Once the FN-RG is in RM-REGISTERED and CM-CONNECTED the W-AGF may setup PDU session(s) on behalf of the FN-RG (as described in clause 7.3.4). + +![Sequence diagram for FN-RG Registration via W-5GAN. The diagram shows the interaction between FN-RG, Wireline ANs, W-AGF, AMF, AUSF, UDM, and PCF. The process starts with Layer-2 connection establishment between FN-RG and Wireline ANs. The W-AGF then performs AMF Selection and sends an N2 UE initial message (NAS: Registration request) to the AMF. The AMF performs AUSF Selection and sends a Nausf_UEAuthentication_Authenticate request to the AUSF. The AUSF sends a Nudm_UEAuthentication_Get Request to the UDM. The UDM performs SUCI deconcatenation and maps SUCI to SUPI. The AUSF sends a Nudm_UEAuthentication_Get Response to the AMF. The AMF sends N2 Downlink NAS (SMC Request) to the W-AGF, which in turn sends N2 Uplink NAS (SMC Complete) to the AMF. The AMF then performs steps 11 - 16 in TS 23.502 clause 4.2.2.2.2-1. The W-AGF sends N2 Initial Ctx Request to the AMF, which responds with N2 Initial Ctx Response. The AMF sends N2 Downlink NAS (NAS Registration Accept) to the W-AGF, which sends N2 Uplink NAS (Registration Complete) to the AMF. Finally, the AMF performs steps 23-24 in TS 23.502 clause 4.2.2.2.2-1.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +``` + +sequenceDiagram + participant FN-RG + participant Wireline ANs + participant W-AGF + participant AMF + participant AUSF + participant UDM + participant PCF + + Note left of FN-RG: 1. Layer-2 (L2) connection establishment + FN-RG->>Wireline ANs: + Wireline ANs->>FN-RG: + Note right of W-AGF: 2. AMF Selection + W-AGF->>AMF: 3. N2 UE initial message (NAS: Registration request) (SUCI, Auth_Indicate) + Note right of AMF: 4. AUSF Selection + AMF->>AUSF: 5. Nausf_UEAuthentication_Authenticate (SUCI, Auth_Indicate) + AUSF->>UDM: 6. Nudm_UEAuthentication_Get Request (SUCI, Auth_Indicate) + Note right of UDM: 7. SUCI deconcatenation. SUCI mapped to SUPI + UDM->>AUSF: 8. Nudm_UEAuthentication_Get Response (SUPI) + AUSF->>AMF: 9. Nausf_UEAuthentication_Authenticate (SUPI) + AMF->>W-AGF: 10a. N2 Downlink NAS (SMC Request) + W-AGF->>AMF: 10b. N2 Uplink NAS (SMC Complete) + Note right of AMF: 11. Perform steps 11 - 16 in TS 23.502 clause 4.2.2.2.2-1 + W-AGF->>AMF: 12a. N2 Initial Ctx Request + AMF->>W-AGF: 12b. N2 Initial Ctx Response + AMF->>W-AGF: 13. N2 Downlink NAS (NAS Registration Accept) + W-AGF->>AMF: 14. N2 Uplink NAS (Registration Complete) + Note right of AMF: 15. Steps 23-24 in TS 23.502 clause 4.2.2.2.2-1 + +``` + +Sequence diagram for FN-RG Registration via W-5GAN. The diagram shows the interaction between FN-RG, Wireline ANs, W-AGF, AMF, AUSF, UDM, and PCF. The process starts with Layer-2 connection establishment between FN-RG and Wireline ANs. The W-AGF then performs AMF Selection and sends an N2 UE initial message (NAS: Registration request) to the AMF. The AMF performs AUSF Selection and sends a Nausf\_UEAuthentication\_Authenticate request to the AUSF. The AUSF sends a Nudm\_UEAuthentication\_Get Request to the UDM. The UDM performs SUCI deconcatenation and maps SUCI to SUPI. The AUSF sends a Nudm\_UEAuthentication\_Get Response to the AMF. The AMF sends N2 Downlink NAS (SMC Request) to the W-AGF, which in turn sends N2 Uplink NAS (SMC Complete) to the AMF. The AMF then performs steps 11 - 16 in TS 23.502 clause 4.2.2.2.2-1. The W-AGF sends N2 Initial Ctx Request to the AMF, which responds with N2 Initial Ctx Response. The AMF sends N2 Downlink NAS (NAS Registration Accept) to the W-AGF, which sends N2 Uplink NAS (Registration Complete) to the AMF. Finally, the AMF performs steps 23-24 in TS 23.502 clause 4.2.2.2.2-1. + +Figure 7.2.1.3-1: FN-RG Registration via W-5GAN + +1. The FN-RG connects to a W-AGF (W-5GAN) via a layer-2 (L2) connection, based on Wireline AN specific procedure. + +The FN-RG is authenticated by the W-5GAN based on Wireline AN specific mechanisms. + +2. W-AGF selects an AMF based on the AN parameters and local policy. W-AGF may use the Line ID / HFC identifier provided from the Wireline AN to determine the 5GC and AN parameters to be used for the FN-RG registration. How the W-AGF can determine the necessary 5GC and AN parameters is defined in BBF TR-456 [9], WT-457 [10] or CableLabs WR-TR-5WWC-ARCH [27]. +3. W-AGF performs initial registration on behalf of the FN-RG to the 5GC. The W-AGF sends a Registration Request to the selected AMF within an N2 initial UE message (NAS Registration Request, ULI, Establishment cause, UE context request, Allowed NSSAI, Authenticated Indication). + +The NAS Registration Request contains the SUCI or 5G-GUTI of the FN-RG, security parameters/UE security capability, UE MM Core Network Capability, PDU Session Status, Follow-on request, Requested NSSAI. The 5G-GUTI, if available, has been received from the AMF during a previous registration and stored in W-AGF. + +The NSSAI parameters are provided based on W-AGF configuration. Based on W-AGF configuration of the 5GC NAS parameters, one or multiple Requested S-NSSAI may be used; e.g. when the W-AGF has been configured to use a specific slice for RG management purposes. + +The following differences exist, compared to 5G-RG case: + +- The W-AGF use SUCI as defined in clause 4.7.3 and clause 4.7.4. +- The Authenticated Indication indicates to AMF and 5GC that the FN-RG has been authenticated by the access network. + +The SUCI is built by the W-AGF based on: + +- In the case of a BBF access: the GLI as defined in clause 4.7.8 together with an identifier of the Home network as described in TS 23.003 [14]. +- In the case of a Cable access: the GCI as defined in clause 4.7.8 together with an identifier of the Home network as described in TS 23.003 [14]. + +NOTE 1: Further description for how W-AGF obtain parameters required in AS and NAS message e.g. to build the SUCI is defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27]. + +- 4 If the AMF receives a SUCI, the AMF shall select an AUSF as specified in TS 23.501 [2] clause 6.3.4 based on SUCI. If 5G-GUTI is provided, there is no need to map SUCI to SUPI and steps 5-9 can be skipped. +5. AMF sends an authentication request to the AUSF in the form of, Nausf\_UEAuthentication\_Authenticate. It contains the SUCI of the FN-RG. It also contains an indication that the W-5GAN has authenticated the FN-RG. +6. AUSF selects a UDM as described in clause 6.3.8 of TS 23.501 [2] and sends a Nudm\_UEAuthentication\_Get Request to the UDM. It contains the SUCI of the FN-RG and indication that the W-5GAN has authenticated the FN-RG. +7. UDM invokes the SIDF to map the SUCI to a SUPI. +8. UDM sends a Nudm\_UEAuthentication\_Get Response to the AUSF. It contains the SUPI corresponding to the SUCI. It also contains an indication that authentication is not required for the FN-RG. +9. AUSF sends a Nausf\_UEAuthentication\_Authenticate Response to the AMF. This response from AUSF indicates that authentication is successful. The response contains the SUPI corresponding to the SUCI. + +The procedure described in TS 23.502 [3] clause 4.2.2.2.3 may apply (the AMF decides if the Registration Request needs to be rerouted, where the initial AMF refers to the AMF). + +- 10a. AMF initiates a NAS security mode command procedure upon successful authentication as defined in TS 33.501 [11]. + +The NAS security mode command is sent from the AMF to the W-AGF in a N2 Downlink NAS transport message. + +- 10b. W-AGF responds to the AMF with a NAS Security Mode Complete message in a N2 Uplink NAS transport message. A NAS security context is created between W-AGF and AMF. +11. The AMF performs steps 11-16 in TS 23.502 [3] clause 4.2.2.2.2. + +The AMF may be configured by local policies to issue EIR check: + +- Only if the PEI is an IMEI; or +- Only if the PEI is an IMEI or a user device trusted MAC address. + +These local policies may be defined on a per RAT Type basis. + +At FN-RG registration to UDM, the Access Type non-3GPP access is used. The UDM, based on Access and Mobility Subscription information authorizes the FN-RG to access the 5GC. For FN-CRG, the AMF compares the list of serving area restrictions it receives from the UDM against the ULI from the W-AGF to check if the location information is allowed for the FN-CRG, as defined in clause 9.5.1. The AMF may also interact with the PCF for obtaining the Access and Mobility policy for the FN-RG. + +- 12a. Upon receiving NAS Security Mode Complete, the AMF shall send an N2 Initial Context Setup Request message as defined in TS 38.413 [23] and TS 29.413 [42] including possibly as additional W-AGF specific parameter the RG Level Wireline Access Characteristics to the W-AGF. +- 12b W-AGF notifies to the AMF that the FN-RG context was created by sending a N2 Initial Context Setup Response. +13. The AMF sends the N2 Downlink NAS transport with NAS Registration Accept message (5GS registration result, 5G-GUTI, Equivalent PLMNs or SNPNS, Non-3GPP TAI, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, network slicing indication, Non-3GPP de-registration timer value, Emergency number lists, SOR transport container, NSSAI inclusion mode) to the W-AGF. + +The following parameters are ignored by the W-AGF if received from the AMF: Emergency number lists, SOR transport container, NSSAI inclusion mode. + +NOTE 2: Further description on how W-AGF handles the parameters received from 5GC is provided in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27]. + +14. The W-AGF sends a N2 Uplink NAS transport message, including a NAS Registration Complete message, back to the AMF when the procedure is completed. The W-AGF shall store the 5G-GUTI to be able to send it in potential later NAS procedures. +15. The AMF performs step 23-24 in TS 23.502 [3] clause 4.2.2.2.2. + +The W-AGF may continue by establishing PDU session(s) on behalf of the FN-RG. + +#### 7.2.1.4 FN-RG Deregistration via W-5GAN + +The deregistration procedure for the FN-RG is similar to that of 5G-RG described in clause 7.2.1.2 but with the following differences: + +- The 5G-RG is replaced with a FN-RG. +- In step 1a and 1b, the W-AGF sends and receives NAS deregistration request/accept messages on behalf of FN-RG. +- UE-initiated deregistration procedure can be initiated by the W-AGF, when it has lost connectivity to the FN-RG. +- For both UE/Network-initiated deregistration procedures, the W-AGF may initiate the release of the signalling connection between the FN-RG and W-AGF based on legacy protocols. + +NOTE: As described in clause 6.2.2, the message exchanges between the FN-RG and W-AGF are based on legacy protocols in the wireline access network. + +### 7.2.2 Service Request procedures + +#### 7.2.2.1 5G-RG Service Request procedure via W-5GAN Access + +The Service Request procedure via W-5GAN shall be used by a 5G-RG in CM-IDLE state over W-5GAN to request the re-establishment of the NAS signalling connection and the re-establishment of the user plane for all or some of the PDU Sessions which are associated to non-3GPP access. + +NOTE 1: For a W-5GAN access, the Service Request procedure is never a response to a Paging i.e. Paging does not apply on a W-5GAN access. + +The Service Request procedure via W-5GAN shall be used by a 5G-RG in CM-CONNECTED state over wireline access to request the re-establishment of the user plane for one or more PDU Sessions which are associated to non-3GPP access. + +![Sequence diagram of 5G-RG Triggered Service Request procedure via W-5GAN. Lifelines: 5G-RG, W-AGF, AMF, Other CP and UP functions. The sequence shows steps for connection establishment, NAS message exchange, authentication, and resource setup.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-AGF + participant AMF + participant Other CP and UP functions + + Note left of 5G-RG: 1. W-CP connection establishment + 5G-RG-->>W-AGF: + Note left of 5G-RG: 3. W-CP ( AN-Params [GUAMI, Establishment Cause], NAS-PDU [Service Request] ) + 5G-RG->>W-AGF: + Note right of W-AGF: 4. N2 Initial UE message (NAS: Service Request) + W-AGF->>AMF: + Note right of AMF: 5. Authentication and Key Agreement & Security Mode Command, Steps 6-7 in clause 7.2.1.1 + AMF-->>Other CP and UP functions: + Note right of Other CP and UP functions: 6. Steps 4-11 in TS 23.502, Figure 4.2.3.2-1 + Other CP and UP functions-->>AMF: + Note right of AMF: 7. NGAP Initial Ctxt Request (N2 SM info, MM NAS Service Accept, W-AGF Key) + AMF->>W-AGF: + Note left of 5G-RG: 9. W-CP signalling connection establishment + 5G-RG-->>W-AGF: + Note right of W-AGF: 10. Determine W-CP resources needed + W-AGF->>5G-RG: + Note left of 5G-RG: 11. W-UP resource(s) setup (W-5GAN AS parameters) + 5G-RG-->>W-AGF: + Note right of W-AGF: 12. NGAP Initial Ctxt Response + W-AGF->>AMF: + Note right of AMF: 13a. N2 Downlink NAS (NAS Service Accept) + AMF->>W-AGF: + Note left of 5G-RG: 13b. W-CP ( NAS-PDU[MM NAS Service Accept] ) + 5G-RG-->>W-AGF: + Note right of Other CP and UP functions: 14. All steps in TS 23.502, Figure 4.2.3.2.1-1 after step 14 + +``` + +Sequence diagram of 5G-RG Triggered Service Request procedure via W-5GAN. Lifelines: 5G-RG, W-AGF, AMF, Other CP and UP functions. The sequence shows steps for connection establishment, NAS message exchange, authentication, and resource setup. + +**Figure 7.2.2.1-1: 5G-RG Triggered Service Request procedure via W-5GAN** + +1. The 5G-RG connects to a W-5GAN as described in step 1 of Figure 7.2.1.1-1. +2. Void. +3. The 5G-RG using W-CP protocol stack sends a message that contains the Access Network parameters (GUAMI and Establishment Cause) and a NAS Service Request message (List Of PDU Sessions To Be Activated, security parameters, PDU Session status, Uplink Data Status, 5G-S-TMSI). The Establishment cause provides the reason for requesting a signalling connection with 5GC. In this release of the specification no Selected PLMN or SNPN parameter is sent by a 5G RG. +4. The W-AGF shall then forward the Service Request received from the 5G-RG to the selected AMF within an N2 initial UE message (NAS Service Request message, User Location Information, Establishment cause, UE context request). +5. The AMF may initiate NAS authentication/security procedure as defined in step 6 and step 7 in clause 7.2.1.1. +If the UE in CM-IDLE state triggered the Service Request to establish a signalling connection only, after successful establishment of the signalling connection the UE and the network can exchange NAS signalling and steps 6 and 14 are skipped. +6. Steps 4-11 in TS 23.502 [3] figure 4.2.3.2-1 are performed for each requested PDU session user plane. +7. (If the 5G RG was CM-IDLE) AMF sends an N2 Initial Context Setup Request message (N2 SM information received from SMF(s), RG Level Wireline Access Characteristics, GUAMI, Allowed NSSAI, UE security capability, Security Key, Trace Activation, Masked IMEISV). + +If the 5G RG was CM-CONNECTED the AMF sends N2 SM information received from SMF(s). + +The W-AGF ignores any UE security capability received in a N2 Initial Context Setup Request message. + +NOTE 2: The UE Security Capability IE is mandatory in NGAP protocol, but it is not applicable to wireline access, so the AMF can provide any value and the W-AGF ignores it. + +8. Void. + +9. [Conditional, if the 5G RG was CM-IDLE] A signalling connection using W-CP protocol stack is established between the 5G-RG and W-AGF. + +NOTE 3: Steps 9-11 are defined by BBF/Cablelabs. + +Steps 10 and 11 are carried out for each PDU Session indicated in step 7 + +10. Based on its own policies and configuration and based on the QoS flows and QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session. + +11. The W-AGF sets up the W-UP resources for the PDU session. This step is specified by BBF for W-5BGAN and by CableLabs for W-5GCAN. The access dependent W-UP resource setup procedure shall map to the identity of the PDU Session associated with the W-UP resource. + +12. W-AGF notifies the AMF that the 5G-RG context was created by sending a N2 Initial Context Setup Response (N2 SM information that provides AN Tunnel Info, List of accepted QoS Flows, List of rejected QoS Flows per PDU Session ID for PDU Sessions whose UP connections are activated). + +13. AMF sends NAS Service Accept via W-AGF to the 5G-RG. + +14. All steps after step 14 in TS 23.502 [3] figure 4.2.3.2-1 are performed for each requested PDU Session user plane. + +When the 5G-RG is in CM-CONNECTED state over W-5GAN access and the network receives downlink data for a PDU Session over wireline access that has no user plane connection, the steps 1-4a in clause 4.2.3.3 of TS 23.502 [3] (Network Triggered Service Request) shall be performed with the following exceptions: + +- The (R)AN corresponds to an W-AGF. +- The UE corresponds to the 5G-RG. +- In step 4a of TS 23.502 [3] clause 4.2.3.3, the steps 2b-6 in figure 7.3.1.1-1 are performed to establish the W-UP resources and to establish N3 tunnel. In steps 2b and 6, no NAS message is exchanged with the UE. + +#### 7.2.2.2 FN-RG Service Request procedure via W-5GAN Access + +The Service Request procedure via W-5GAN shall be used by a W-AGF when the CM state in W-AGF for a FN-RG is CM-IDLE over W-5GAN to request the re-establishment of the NAS signalling connection and the re-establishment of the user plane for all or some of the PDU Sessions which are associated to non-3GPP access. + +The Service Request procedure via W-5GAN shall be used by a W-AGF when the CM state in W-AGF for a FN-RG is CM-CONNECTED over wireline access to request the re-establishment of the user plane for one or more PDU Sessions which are associated to non-3GPP access. + +![Sequence diagram of the FN-RG Service Request procedure via W-5GAN. The diagram shows interactions between FN-RG, Wireline ANs, W-AGF, AMF, and Other CP and UP functions. The steps are: 1. Layer-2 (L2) connection establishment between FN-RG and W-AGF; 2. Authentication between FN-RG and W-AGF; 3. NGAP Initial UE message (NAS: Service Request, Auth_Indicate) from W-AGF to AMF; 4. Security Mode command from AMF to W-AGF; 5. Step 4-11 in TS 23.502 Figure 4.2.3.2-1 from AMF to W-AGF; 6. NGAP Initial Ctx Request from AMF to W-AGF; 7. Determine L-W-UP resources needed in W-AGF; 8. NGAP Initial Ctx Response from W-AGF to AMF; 9. N2 Downlink NAS (NAS Service Accept) from AMF to W-AGF; 10. All steps in TS 23.502 Figure 4.2.3.2.1-1 after step 14 from AMF to W-AGF.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + +sequenceDiagram + participant FN-RG + participant Wireline ANs + participant W-AGF + participant AMF + participant Other CP and UP functions + + Note left of FN-RG: 1. Layer-2 (L2) connection establishment + FN-RG-->>W-AGF: + Note left of FN-RG: 2. Authentication + FN-RG-->>W-AGF: + W-AGF->>AMF: 3. NGAP Initial UE message (NAS: Service Request, Auth_Indicate) + AMF-->>W-AGF: 4. Security Mode command, Step 11 Clause 7.2.1.3 + AMF-->>W-AGF: 5. Step 4-11 in TS 23.502 Figure 4.2.3.2-1 + AMF->>W-AGF: 6. NGAP Initial Ctx Request (N2 SM info, MM NAS Service Accept, W-AGF key) + Note right of W-AGF: 7. Determine L-W-UP resources needed + W-AGF->>AMF: 8. NGAP Initial Ctx Response + AMF->>W-AGF: 9. N2 Downlink NAS (NAS Service Accept) + AMF-->>W-AGF: 10. All steps in TS 23.502 Figure 4.2.3.2.1-1 after step 14 + +``` + +Sequence diagram of the FN-RG Service Request procedure via W-5GAN. The diagram shows interactions between FN-RG, Wireline ANs, W-AGF, AMF, and Other CP and UP functions. The steps are: 1. Layer-2 (L2) connection establishment between FN-RG and W-AGF; 2. Authentication between FN-RG and W-AGF; 3. NGAP Initial UE message (NAS: Service Request, Auth\_Indicate) from W-AGF to AMF; 4. Security Mode command from AMF to W-AGF; 5. Step 4-11 in TS 23.502 Figure 4.2.3.2-1 from AMF to W-AGF; 6. NGAP Initial Ctx Request from AMF to W-AGF; 7. Determine L-W-UP resources needed in W-AGF; 8. NGAP Initial Ctx Response from W-AGF to AMF; 9. N2 Downlink NAS (NAS Service Accept) from AMF to W-AGF; 10. All steps in TS 23.502 Figure 4.2.3.2.1-1 after step 14 from AMF to W-AGF. + +**Figure 7.2.2.2-1: FN-RG Service Request procedure via W-5GAN** + +1. If the FN-RG has lost the L2 connection with W-AGF, the FN-RG connects to a W-AGF (W-5GAN) via a layer-2 (L2) connection, based on Wireline AN specific procedure. +2. If step 1 was done, the FN-RG may be authenticated by the W-5GAN based on Wireline AN specific procedure. +3. The W-AGF shall then send a Service Request to the selected AMF within an N2 initial UE message (NAS Service Request message, User Location Information, Establishment cause, UE context request, Auth\_Indicate). +4. The AMF may initiate NAS authentication/security procedure as defined in steps 5-10 in clause 7.2.1.3. + +If the W-AGF triggered the Service Request to establish a signalling connection only, after successful establishment of the signalling connection the W-AGF and the network can exchange NAS signalling and steps 5 and 10 are skipped. + +5. Steps 4-11 in TS 23.502 [3] figure 4.2.3.2-1 are performed for each requested PDU session user plane. + +6. (If the FN-RG CM state was CM-IDLE) AMF sends an N2 Initial Context Setup Request message (N2 SM information received from SMF(s), RG Level Wireline Access Characteristics, GUAMI, Allowed NSSAI, UE security capability, Security Key, Trace Activation, Masked IMEISV). + +If the FN-RG CM state in W-AGF was CM-CONNECTED the AMF sends N2 SM information received from SMF(s). + +The W-AGF ignores any UE security capability received in a N2 Initial Context Setup Request message. + +NOTE: The UE Security Capability IE is mandatory in NGAP protocol, but it is not applicable to a wireline access, so the AMF can provide any value and the W-AGF ignores it. + +Step 7 is carried out for each PDU Session indicated in step 6. + +7. Based on its own policies and configuration and based on the QoS flows and QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session. + +The W-AGF may perform BBF specific resource reservation with the AN, that is, it sets up the L-W-UP resources for the PDU session. This step is specified by BBF for W-5GBAN and by CableLabs for W-5GCAN. + +8. W-AGF notifies the AMF that the FN-RG context in W-AGF was created by sending a N2 Initial Context Setup Response (N2 SM information that provides AN Tunnel Info, List of accepted QoS Flows, List of rejected QoS Flows per PDU Session ID for PDU Sessions whose UP connections are activated). +9. AMF sends NAS Service Accept to W-AGF. +10. All steps after step 14 in figure 4.2.3.2-1 of TS 23.502 [3] are performed for each requested PDU session user plane. + +When the FN-RG CM state in W-AGF is CM-CONNECTED over W-5GAN access and the network receives downlink data for a PDU Session over wireline access that has no user plane connection, the steps 1-4a in clause 4.2.3.3 of TS 23.502 [3] (Network Triggered Service Request) shall be performed with the following exceptions: + +- The (R)AN corresponds to an W-AGF. +- The UE corresponds to the FN-RG. +- In step 4a, the steps 6-10 in figure 7.2.2.2-1 are performed to establish the L-W-UP resources and to establish N3 tunnel. In step 6, the AMF does not send the NAS Service Accept message to the UE. + +### 7.2.3 5G-RG and FN-RG Configuration Update + +#### 7.2.3.0 General + +This clause specifies delta for Configuration Update procedure defined in TS 23.502 [3] clause 4.2.4 for 5G-RG and FN-RG. + +#### 7.2.3.1 5G-RG Configuration Update via W-5GAN Access + +The 5G-RG Configuration Update procedures via W-5GAN may be used by the network at any time to update 5G-RG configuration which includes: + +- Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI and its mapping to Subscribed S-NSSAIs. +- 5G-RG Policy (i.e. URSP) provided by the PCF. + +The procedure described in TS 23.502 [3] clause 4.2.4.2 is used for the AMF to change the 5G-RG configuration for access and mobility management related parameters, with the following differences: + +- The UE is replaced by the 5G-RG. +- The (R)AN corresponds to the W-5GAN. + +![Sequence diagram of the 5G-RG Configuration Update procedure for access and mobility management related parameters. The diagram shows interactions between 5G-RG, W-5GAN, AMF, SMF, and UDM. Step 0: AMF decides update. Step 1: AMF sends UE Configuration Update Command to 5G-RG. Step 2a: 5G-RG sends UE Configuration Update Complete to AMF. Step 2b: AMF sends Nudm_SDM_Info service to UDM. Step 2d: AMF informs lower layers. Step 3b: AMF does not trigger AN Release procedure. Step 3c: AMF triggers AN Release procedure. Step 4: 5G-RG initiates Registration procedure.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-5GAN + participant AMF + participant SMF + participant UDM + + Note over 5G-RG, UDM: 0. AMF decides update of 5G-RG configuration or need for re-registration + AMF->>5G-RG: 1. UE Configuration Update Command + 5G-RG-->>AMF: 2a. UE Configuration Update Complete + AMF-->>UDM: 2b. Nudm_SDM_Info service + Note left of 5G-RG: 2d. Inform lower layers + Note right of AMF: 3b. AMF does not trigger AN Release procedure as described in clause 4.2.6 in TS 23.502. Steps 3c and 4 are skipped + Note right of AMF: 3c. AMF triggers AN Release procedure unless there are PDU Session(s) associated with emergency services + Note right of 5G-RG: 4. 5G-RG initiates Registration procedure after 5G-RG enters CM-IDLE state + +``` + +Sequence diagram of the 5G-RG Configuration Update procedure for access and mobility management related parameters. The diagram shows interactions between 5G-RG, W-5GAN, AMF, SMF, and UDM. Step 0: AMF decides update. Step 1: AMF sends UE Configuration Update Command to 5G-RG. Step 2a: 5G-RG sends UE Configuration Update Complete to AMF. Step 2b: AMF sends Nudm\_SDM\_Info service to UDM. Step 2d: AMF informs lower layers. Step 3b: AMF does not trigger AN Release procedure. Step 3c: AMF triggers AN Release procedure. Step 4: 5G-RG initiates Registration procedure. + +**Figure 7.2.3.1-1: 5G-RG Configuration Update procedure for access and mobility management related parameters** + +In Step 0, the AMF determines the necessity of 5G-RG configuration change due to various reasons, but UE mobility change is not applicable in this release of specification. If a 5G-RG is in CM-IDLE, the AMF can wait until the 5G-RG is in CM-CONNECTED state as Network Triggered Service Request is not applicable. + +In step 1, the AMF sends UE Configuration Update Command to the 5G-RG. The following parameters are not included: Mapping Of Allowed NSSAI, Configured NSSAI for the Serving PLMN or SNPN, Mapping Of Configured NSSAI, MICO, Operator-defined access category definitions, SMS Subscribed Indication. + +Step 2c is not applicable in this procedure. + +Step 3a is not applicable since it is only for NAS parameters that can be updated without transition from CM-IDLE are included, e.g. MICO mode. + +The procedure for UE Configuration Update procedure for transparent UE Policy delivery described in TS 23.502 [3] clause 4.2.4.3 is used for the PCF to change or provide new 5G-RG policies in the 5G-RG, with the following differences: + +- The UE is replaced by the 5G-RG. +- The (R)AN corresponds to the W-5GAN. +- The means for carrying NAS messages between 5G-RG and W-AGF within the W-GAN are to be defined by BBF. +- Step 2 is not applicable since the Network Triggered Service Request is not applicable in the case of W-5GAN. + +![Sequence diagram for 5G-RG Configuration Update procedure for transparent UE Policy delivery. Lifelines: 5G-RG, W-5GAN, AMF, PCF. The sequence starts with the PCF deciding to update the 5G-RG policy (step 0). The PCF sends a Namf_Communication_N1N2MessageTransfer message to the AMF (step 1). The AMF sends a Delivery of 5G-RG policy message to the 5G-RG (step 3). The 5G-RG sends a Result of the delivery of 5G-RG policy message to the AMF (step 4). The AMF sends a Namf_N1MessageNotify message to the PCF (step 5).](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` +sequenceDiagram + participant 5G-RG + participant W-5GAN + participant AMF + participant PCF + Note right of PCF: 0. PCF decides to update 5G-RG policy + PCF-->>AMF: 1. Namf_Communication_N1N2MessageTransfer + AMF->>5G-RG: 3. Delivery of 5G-RG policy + 5G-RG->>AMF: 4. Result of the delivery of 5G-RG policy + AMF-->>PCF: 5. Namf_N1MessageNotify +``` + +Sequence diagram for 5G-RG Configuration Update procedure for transparent UE Policy delivery. Lifelines: 5G-RG, W-5GAN, AMF, PCF. The sequence starts with the PCF deciding to update the 5G-RG policy (step 0). The PCF sends a Namf\_Communication\_N1N2MessageTransfer message to the AMF (step 1). The AMF sends a Delivery of 5G-RG policy message to the 5G-RG (step 3). The 5G-RG sends a Result of the delivery of 5G-RG policy message to the AMF (step 4). The AMF sends a Namf\_N1MessageNotify message to the PCF (step 5). + +Figure 7.2.3.1-2: 5G-RG Configuration Update procedure for transparent UE Policy delivery + +#### 7.2.3.2 FN-RG related Configuration Update via W-5GAN Access + +The FN-RG related Configuration Update procedures via W-5GAN may be used by the network at any time to update FN-RG configuration in W-AGF which includes: + +- Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI and its mapping to Subscribed S-NSSAIs. +- FN-RG related Policy (i.e. URSP) provided by the PCF. + +The W-AGF acts as an N1 termination point on behalf of FN-RG. Therefore, the configuration update procedures described in clause 7.2.3.1, shown in figure 7.2.3.1-1, apply to the FN-RG, with the following additional differences: + +- The 5G-RG is replaced by the W-AGF which is acting as a UE towards the 5GC on behalf of the FN-RG. +- In step 1 the AMF sends the UE Configuration Update Command to the FN-RG, which is received by the W-AGF terminating the N1 and acting as a UE on behalf of the FN-RG. The W-AGF stores the UE Configuration as defined in clause 9.4. If requested by the AMF, the W-AGF shall acknowledge the UE Configuration Update Command. +- Step 2d is not applicable. +- When requested by the AMF, in step 4 the W-AGF starts the registration procedure described in clause 7.2.1.3. +- The Emergency service is not applicable. + +![Sequence diagram for FN-RG related Configuration Update procedure. Lifelines: FN-RG, W-AGF, AMF, SMF, UDM. The procedure starts with AMF deciding an update (0). AMF sends UE Configuration Update Command to W-AGF (1). W-AGF sends UE Configuration Update Complete to AMF (2a). AMF sends Nudm_SDM_Info service to UDM (2b). AMF then either does not trigger AN Release (3b) or triggers it (3c). Finally, FN-RG initiates Registration procedure (4).](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant FN-RG + participant W-AGF + participant AMF + participant SMF + participant UDM + + Note over AMF: 0. AMF decides update of 5G-RG configuration or need for re-registration + AMF->>W-AGF: 1. UE Configuration Update Command + W-AGF-->>AMF: 2a. UE Configuration Update Complete + AMF-->>UDM: 2b. Nudm_SDM_Info service + Note right of AMF: 3b. AMF does not trigger AN Release procedure as described in clause 4.2.6 in + Note right of AMF: 3c. AMF triggers AN Release procedure unless there are PDU Session(s) + Note right of AMF: 4. FN-RG initiates Registration procedure after FN-RG enters CM-IDLE state + +``` + +Sequence diagram for FN-RG related Configuration Update procedure. Lifelines: FN-RG, W-AGF, AMF, SMF, UDM. The procedure starts with AMF deciding an update (0). AMF sends UE Configuration Update Command to W-AGF (1). W-AGF sends UE Configuration Update Complete to AMF (2a). AMF sends Nudm\_SDM\_Info service to UDM (2b). AMF then either does not trigger AN Release (3b) or triggers it (3c). Finally, FN-RG initiates Registration procedure (4). + +**Figure 7.2.3.2-1: FN-RG related Configuration Update procedure for access and mobility management related parameters** + +The procedure of UE Configuration Update procedure for transparent UE Policy delivery described in TS 23.502 [3] clause 4.2.4.3 is used by the PCF to change or provide new FN-RG policies in the W-AGF, with the following differences: + +- The UE is replaced by the W-AGF which is acting as a UE towards the 5GC on behalf of the FN-RG. +- The (R)AN corresponds to the W-5GAN. +- The FN-RG is only registered over W-5GAN. +- Step 2 is not applicable since the Network Triggered Service Request is not applicable in the case of W-5GAN. +- In step 3, the W-AGF receives the delivery of UE policies on behalf of FN-RG. +- The FN-RG policies are managed by W-AGF as defined in clause 9.5.2.2. + +How the W-5GAN applies the configuration update to the wireline network is to be defined by the BBF for the FN-BRG and by CableLabs for the FN-CRG. + +The operator may configure the W-AGF locally by provisioning means not specified by 3GPP as an alternative to the Configuration Update procedure for UE Policy delivery. The 3GPP Configuration Update will take precedence over a locally configured policy for FN-BRGs or FN-CRGs being serviced by the 5GC. + +![Sequence diagram for FN-RG related Configuration Update procedure for transparent UE Policy delivery. The diagram shows four lifelines: FN-RG, W-AGF, AMF, and PCF. The procedure starts with the PCF deciding to update the FN-RG policy (step 0). The PCF then sends a Namf_Communication_N1N2MessageTransfer message to the AMF (step 1). The AMF sends a Delivery of FN-RG policy message to the W-AGF (step 3). The W-AGF sends a Result of the delivery of FN-RG policy message to the AMF (step 4). Finally, the AMF sends a Namf_N1MessageNotify message to the PCF (step 5).](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` +sequenceDiagram + participant FN-RG + participant W-AGF + participant AMF + participant PCF + Note right of PCF: 0. PCF decides to update FN-RG policy + PCF-->>AMF: 1. Namf_Communication_N1N2MessageTransfer + AMF->>W-AGF: 3. Delivery of FN-RG policy + W-AGF->>AMF: 4. Result of the delivery of FN-RG policy + AMF-->>PCF: 5. Namf_N1MessageNotify +``` + +Sequence diagram for FN-RG related Configuration Update procedure for transparent UE Policy delivery. The diagram shows four lifelines: FN-RG, W-AGF, AMF, and PCF. The procedure starts with the PCF deciding to update the FN-RG policy (step 0). The PCF then sends a Namf\_Communication\_N1N2MessageTransfer message to the AMF (step 1). The AMF sends a Delivery of FN-RG policy message to the W-AGF (step 3). The W-AGF sends a Result of the delivery of FN-RG policy message to the AMF (step 4). Finally, the AMF sends a Namf\_N1MessageNotify message to the PCF (step 5). + +Figure 7.2.3.2-2: FN-RG related Configuration Update procedure for transparent UE Policy delivery + +### 7.2.4 Reachability procedures + +The procedures described in TS 23.502 [3] clause 4.2.5 are not applicable for 5G-RG and FN-RG access via W-5GAN. + +### 7.2.5 AN Release + +#### 7.2.5.1 General + +The AN Release procedure via W-5GAN access is used by the W-5GAN or the AMF to release the logical NG-AP signalling connection and the associated N3 User Plane connections between the W-5GAN and the 5GC. + +#### 7.2.5.2 5G-RG AN Release via W-5GAN + +The procedure will move the 5G-RG from CM-CONNECTED to CM-IDLE in AMF, and all 5G-RG related context information is deleted in the W-AGF. + +Both W-AGF initiated and AMF-initiated AN release in the W-5GAN procedures are shown in Figure 7.2.5-1. + +![Sequence diagram illustrating the 5G-RG AN release in the W-AGF. The diagram shows interactions between 5G-RG, W-AGF, AMF, SMF, and UPF. The process starts with 5G-RG already registered. W-AGF detects 5G-RG is unreachable, sends an N2 UE Context Release Request to AMF. AMF responds with an N2 UE Context Release Command. W-AGF then releases W-CP signalling and W-UP resources (out of scope). Finally, W-AGF sends an N2 UE Context Release Complete to AMF, which triggers PDU session user plane de-activation.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-AGF + participant AMF + participant SMF + participant UPF + + Note over 5G-RG, AMF: 1. 5G-RG is already registered in the 5G Core network + Note over W-AGF: 2. 5G-RG is unreachable detected by W-AGF + W-AGF->>AMF: 3. N2 UE Context Release Request + AMF-->>W-AGF: 4. N2 UE Context Release Command + Note over 5G-RG, W-AGF: 5. W-CP signalling connection and W-UP resource release + W-AGF->>AMF: 6. N2 UE Context Release Complete + Note over AMF, SMF, UPF: 7. PDU session user plane de-activation as in steps 5-7 in TS 23.502 Figure 4.2.6-1 + +``` + +Sequence diagram illustrating the 5G-RG AN release in the W-AGF. The diagram shows interactions between 5G-RG, W-AGF, AMF, SMF, and UPF. The process starts with 5G-RG already registered. W-AGF detects 5G-RG is unreachable, sends an N2 UE Context Release Request to AMF. AMF responds with an N2 UE Context Release Command. W-AGF then releases W-CP signalling and W-UP resources (out of scope). Finally, W-AGF sends an N2 UE Context Release Complete to AMF, which triggers PDU session user plane de-activation. + +**Figure 7.2.5-1: 5G-RG AN release in the W-AGF** + +- 1 The 5G-RG has already registered in the 5GC and may have established one or multiple PDU Sessions. + 2. The W-AGF detects that the 5G-RG is not reachable. + 3. The W-AGF sends a N2 UE Context Release Request message to the AMF This step is equivalent to step 1b of Figure 4.2.6-1 in TS 23.502 [3]. +- NOTE 1: The triggers for W-AGF to send UE Context Release Request are defined by BBF in [9] and in CableLabs WR-TR-5WWC-ARCH [27] and may e.g. include events where W-AGF has lost of synchronisation of physical link, loss of PPPoE session, or detects that the RG has been replaced. +- NOTE 2: AN Release procedure can also be triggered by an AMF internal event and in that case step 2 and step 3 do not take place. +4. AMF to W-AGF: If the AMF receives the N2 UE Context Release Request from W-AGF or if due to an internal AMF event the AMF wants to release N2 signalling, the AMF sends an N2 UE Context Release Command (Cause) to the W-AGF. The cause indicated is cause from step 3 or a cause due to internal AMF event. This step is equivalent to step 2 in Figure 4.2.6-1 of TS 23.502 [3]. + 5. If the W-CP signalling connection and W-UP resources has not been released yet, the W-AGF releases the W-CP connection and W-UP resources with a procedure out of scope of 3GPP. The W-AGF sends to the 5G-RG the indication of the release reason if received in step 4. + 6. W-AGF to AMF: The W-AGF confirms the release of the 5G-RG-associated N2-logical connection by returning N2 UE Context Release Complete (list of PDU Session ID(s) with active N3 user plane) to the AMF as in step 4 defined in clause 4.2.6 of TS 23.502 [3]. The AMF marks the 5G-RG as CM-IDLE state in non-3GPP access. + 7. For each of the PDU Sessions in the N2 UE Context Release Complete, the steps 5 to 7 in TS 23.502 [3] clause 4.2.6 are performed (PDU Session Update SM Context). After the AMF receives the Nsmf\_PDUSession\_UpdateSMContext Response as in step 7 of TS 23.502 [3] clause 4.2.6, the AMF considers the N3 connection as released. If list of PDU Session ID(s) with active N3 user plane is included in step 3, then this step is performed before step 4. + +#### 7.2.5.3 FN-RG AN Release via W-5GAN + +The AN release procedure for the FN-RG is similar to that of 5G-RG described in clause 7.2.5.2 but with the following differences: + +- The 5G-RG is replaced with a FN-RG. +- In step 5, the W-AGF may initiate the release of the L-W-CP signalling and L-W-UP resources between the FN-RG and W-AGF based on legacy protocols. + +NOTE: The message exchanges between the FN-RG and W-AGF are based on legacy protocols in the wireline access network as described in clause 6.2.2. + +### 7.2.6 N2 procedures + +#### 7.2.6.0 General + +This clause specifies delta for N2 procedures defined in TS 23.502 [3] clause 4.2.7 for 5G-RG and FN-RG. + +#### 7.2.6.1 N2 procedures via W-5GAN Access + +At power up, restart and when modifications are applied, the W-AGF node and AMF use non-UE related N2 signalling to exchange configuration data. The N2 Configuration as described in TS 23.502 [3] clause 4.2.7.1 is used with the following differences: + +- The 5G-AN corresponds to the W-AGF. + +The Creating NGAP UE-TNLA-bindings during Registration and Service Request procedure as described in TS 23.502 [3] clause 4.2.7.2.1 is used for 5G-RG connecting to 5GC via W-5GAN Access, with the following differences: + +- The 5G-AN corresponds to the W-AGF. +- The UE corresponds to 5G-RG. + +The Creating NGAP UE-TNLA-bindings during Registration and Service Request procedure as described in TS 23.502 [3] clause 4.2.7.2.1 is used for FN-RG connecting to 5GC via W-5GAN Access with the following differences: + +- The 5G-AN corresponds to the W-AGF. +- The UE corresponds to W-AGF on behalf of FN-RG. +- If the W-AGF does not have any UE identities (i.e. a GUAMI or a 5G-S-TMSI) for the FN-RG, e.g. during Initial Registration procedure, the following differences are further applied: + - In step 2, the W-AGF shall handle the access specific messages received from the FN-RG as described in BBF TR456 [9] and WT-457 [10], e.g. PPPoE messages, and does not forward them to the AMF via the selected TNL association. Instead, the W-AGF shall send NAS messages on behalf of the FN-RG to the AMF via the selected TNL association. + - Step 3 can only take place during the Initial Registration procedure. +- The AMF may decide to modify the NGAP UE-TNLA-binding toward other 5G-AN nodes such as W-AGF. This is done if AMF is changed and old AMF have existing NGAP UE-TNLA-bindings toward another W-AGF. + +The Creating NGAP UE-TNLA-bindings during handovers as described in TS 23.502 [3] Clause 4.2.7.2.2 is not applicable to the scenario when 5G-RG or FN-RG is access to 5GC via W-5GAN. + +Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release as described in TS 23.502 [3] clause 4.2.7.2.3 is used for 5G-RG connecting to 5GC via W-5GAN Access with the following exceptions: + +- The 5G-AN corresponds to the W-AGF. + +- The UE corresponds to 5G-RG. + +Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release as described in TS 23.502 [3] clause 4.2.7.2.3 is used for FN-RG connecting to 5GC via W-5GAN Access with the following exceptions: + +- The 5G-AN corresponds to the W-AGF. +- The UE corresponds to W-AGF on behalf of FN-RG. + +### 7.2.7 5G-RG and FN-RG Capability Match Request procedure + +This procedure is not applicable to 5G-RG and FN-RG access via wireline access. + +### 7.2.8 Connection, Registration and Mobility Management procedures for AUN3 devices + +#### 7.2.8.1 AUN3 device Registration via W-5GAN + +An authenticable non-3GPP devices (AUN3) may get connected behind 5G-RG as defined in clause 4.10c. + +This clause specifies how an AUN3 device can be registered via 5G-RG. + +![Sequence diagram showing the 5GC registration of an AUN3 device. The diagram involves six lifelines: AUN3 device, 5G-RG, W-AGF, AMF, SMF, and AUSF/UDM. The process starts with 5G-RG registration with 5GC, followed by AUN3 device connection to 5G-RG, NAS Registration Request, AMF selection, AUSF selection, authentication, subscription data retrieval, registration accept/complete, and finally PDU session establishment.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant AUN3 device + participant 5G-RG + participant W-AGF + participant AMF + participant SMF + participant AUSF/UDM + + Note right of 5G-RG: 1. 5G-RG Registration with 5GC as per clause 7.2.1.1 +Reject any AUN3 connection request until 5G-RG registration completed + Note left of AUN3 device: 2. Connection of AUN3 device with 5G-RG + 5G-RG->>W-AGF: 3. NAS Registration Request, AN parameters + W-AGF->>AMF: 4. Selects AMF + W-AGF->>AMF: 4. N2 message (NAS Registration Request) + Note right of AMF: 5. AUSF Selection + Note right of AMF: 6. Authentication of AUN3 device + Note right of AMF: 7 AMF gets AUN3 subscription data and Registers AUN3 device onto UDM + AMF->>5G-RG: 8. Registration Accept + 5G-RG->>AMF: 9. Registration Complete + Note right of SMF: 10. PDU session establishment per 23.316 clause 7.3.1 + +``` + +Sequence diagram showing the 5GC registration of an AUN3 device. The diagram involves six lifelines: AUN3 device, 5G-RG, W-AGF, AMF, SMF, and AUSF/UDM. The process starts with 5G-RG registration with 5GC, followed by AUN3 device connection to 5G-RG, NAS Registration Request, AMF selection, AUSF selection, authentication, subscription data retrieval, registration accept/complete, and finally PDU session establishment. + +**Figure 7.2.8.1-1: 5GC registration of AUN3 device** + +1. The 5G-RG registers to 5GC as specified in clause 7.2.1.1: + +Any AUN3 device connection request prior to step 1 shall be rejected by the 5G-RG. + +2. The AUN3 device connects to the 5G-RG via non-3GPP access network (e.g., WLAN). An authentication procedure is triggered. This can be done either by AUN3 device sending a EAPOL-start frame to the 5G-RG or 5G-RG receives a frame from an unknown MAC address. The 5G-RG receives a permanent identifier from the AUN3 device (e.g. an NAI in form of username@realm). If the realm part is different from the realm associated with the PLMN that the 5G-RG belongs to, the 5G-RG stops performing following procedure and reject the AUN3 device. + +**NOTE:** How the 5G-RG is triggered to apply procedures for AUN3 devices is defined by BBF and/or CableLabs. For example, the realm of the NAI used by AUN3 device to contact the 5G-RG can be used as a trigger for 5G-RG to apply procedures for AUN3 devices. + +3. This shall be same as step 3 of 7.2.1.1-1 with the following addition: + +- W-CP AN parameters may contain an indicator that the W-CP connection is for an AUN3 device; + +- The 5G-RG always provides a SUCI as AUN3 device identity information in the registration request and constructs the SUCI from the NAI received within EAP-Identity issued by the AUN3 device as defined in TS 33.501 [11]; + - The 5G-RG uses default values, which are the same for all AUN3 devices it serves, to populate the parameters in the Registration Request message built on behalf of an AUN3 device. For example, the 5G-RG issues the Registration Request with no S-NSSAI; and + - When W-AGF provides (over N2) ULI to be associated with an AUN3 device, if the AUN3 device is connected behind a 5G-BRG, the W-AGF builds the AUN3's ULI using the ULI of the 5G-BRG connecting the AUN3 device. If AUN3 device is connected behind the 5G-CRG, the W-AGF builds the ULI using the GCI and HFC node ID of the 5G-CRG connecting the AUN3 device. +4. The W-AGF selects an AMF based on the received AN parameter provided by the 5G-RG and based on local policy, as specified in clause 6.3.5 of TS 23.501 [2]. The W-AGF shall determine that a W-CP connection is for an AUN3 device and apply corresponding policies.. + +The W-AGF sends an NGAP INITIAL UE message to the selected AMF. For an AUN3 device, the W-AGF indicates to AMF if the N2 connection relates to an AUN3 device and if there is an existing N2 connection for a 5G-RG connected to the same GLI/GCI (where the initial NAS message related with NGAP INITIAL UE message has been received). + +If the W-AGF indicated for an AUN3 device that there is no existing 5G-RG N2 connection for a 5G-RG connected to the same GLI/GCI, then the AMF rejects the registration request and further steps of this procedure are skipped. Otherwise, the procedure continues. + +5. AMF selects AUSF as specified in clause 6.3.4 of TS 23.501 [2]. +6. The AUSF executes the authentication of the AUN3 device following TS 33.501 [11]. The AUSF selects the UDM as described in clause 6.3.8 of TS 23.501 [2] and gets the authentication data of the AUN3 device, from UDM. EAP based authentication defined in TS 33.501 [11] is performed between the AUSF and the AUN3 device. Once the AUN3 device has been authenticated, the AUSF provides relevant security related information to the AMF. AUSF shall return the SUPI corresponding to the AUN3 device to AMF only after the authentication is successful. +7. Same as step 8 to 12 of figure 7.2.1.1-1 with following modifications +- The 5G RG uses the MAC address of the AUN3 device as a PEI; +8. The AMF sends the Registration Accept message related to the AUN3 device to the 5G-RG. This step is executed over the NAS signalling connection and the N2 connection related to the AUN3 device. +9. The 5G-RG sends the Registration Complete message related to the AUN3 device to the AMF, when the procedure is completed. This step is executed over NAS signalling connection and N2 connection related to the AUN3 device. The 5G-RG shall store the 5G-GUTI of AUN3 device to be able to use it potential later NAS procedures related with the AUN3 device. +10. The 5G-RG receives the URSP corresponding to the AUN3 device and continues by requesting the establishment of a PDU Session on behalf of the AUN3 device as specified in clause 7.3.1. + +#### 7.2.8.2 AUN3 device De-registration via W-5GAN + +AUN3 device may get connected behind 5G-RG as defined in clause 4.10c. This clause specifies how an AUN3 device can be de-registered via 5G-RG. + +![Sequence diagram for de-registration of an AUN3 device. Lifelines: 5G-RG, W-AGF, AMF, SMF, UPF, PCF. The diagram shows two main procedures: 1a. UE-Initiated Deregistration procedure (steps 1 to 7) and 1b. Network Initiated deregistration procedure (steps 1 to 6). Step 1a is triggered by the AUN3 device to the 5G-RG. Step 1b is triggered by the network (AMF or UDM) to the 5G-RG. Step 2: AMF sends N2 UE Context Release Command to W-AGF. Step 3: W-AGF performs W-CP signalling connection release. Step 4: W-AGF sends N2 UE Context Release Complete to AMF.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-AGF + participant AMF + participant SMF + participant UPF + participant PCF + + Note right of 5G-RG: 1a. UE-Initiated Deregistration procedure TS 23.502 Figure 4.2.2.3.2-1 steps 1 to 7 related with the AUN3 device + Note right of 5G-RG: 1b. Network Initiated deregistration procedure TS 23.502 Figure 4.2.2.3.3-1 steps 1 to 6 related with the AUN3 device + + 5G-RG->>W-AGF: 1a. UE-Initiated Deregistration procedure + W-AGF->>AMF: 1a. UE-Initiated Deregistration procedure + AMF->>SMF: 1a. UE-Initiated Deregistration procedure + SMF->>UPF: 1a. UE-Initiated Deregistration procedure + UPF->>PCF: 1a. UE-Initiated Deregistration procedure + + AMF->>W-AGF: 2. N2 UE Context Release Command + W-AGF->>W-AGF: 3. W-CP signalling connection release + W-AGF->>AMF: 4. N2 UE Context Release Complete + +``` + +Sequence diagram for de-registration of an AUN3 device. Lifelines: 5G-RG, W-AGF, AMF, SMF, UPF, PCF. The diagram shows two main procedures: 1a. UE-Initiated Deregistration procedure (steps 1 to 7) and 1b. Network Initiated deregistration procedure (steps 1 to 6). Step 1a is triggered by the AUN3 device to the 5G-RG. Step 1b is triggered by the network (AMF or UDM) to the 5G-RG. Step 2: AMF sends N2 UE Context Release Command to W-AGF. Step 3: W-AGF performs W-CP signalling connection release. Step 4: W-AGF sends N2 UE Context Release Complete to AMF. + +**Figure 7.2.8.2-1: De-registration of an AUN3 device** + +1a. The AUN3 device triggers a disconnection request to the 5G-RG. + +NOTE: Detail procedures how AUN3 device triggers the de-registration request is out of scope of 3GPP. + +1a. The 5G-RG sends a De-registration request on behalf of the AUN3 device. This triggers step 1a of Figure 7.2.1.2-1 with the deregistration targeting the AUN3 device and not the 5G-RG. This step is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection. + +1b. The network (AMF or UDM) may determine to de-register an AUN3. This triggers step 1b of Figure 7.2.1.2-1 with the deregistration targeting the AUN3 device and not the 5G-RG. + +2. AMF to W-AGF: The AMF sends a N2 UE Context Release Command message to the W-AGF as defined in step 2 of Figure 7.2.1.2-1 but for the N2 connection related with the AUN3 device. W-AGF removes W-CP AN context information for the AUN3 device. + +3. As defined in step 3 of Figure 7.2.1.2-1 but for the signalling connection related with the AUN3 device. + +4. The W-AGF sends a N2 UE Context Release Complete message to the AMF. + +#### 7.2.8.3 5G-RG Deregistration via W-5GAN when it is also serving AUN3 devices + +![Sequence diagram illustrating the 5G-RG Deregistration procedure via W-5GAN when serving AUN3 devices. The diagram shows interactions between AUN3, 5G-RG, W-AGF, AMF, SMF, UPF, and PCF. The procedure starts with UE-Initiated or Network Initiated deregistration (steps 1a and 1b). The AMF sends an N2 UE Context Release Command to the W-AGF (step 2), which responds with N2 UE Context Release Complete (step 3). The W-AGF then identifies AUN3 devices connected to the 5G-RG (step 4) and sends an AUN3: UE Context Release Request to the AMF (step 5). The AMF initiates deregistration of all AUN3 devices (step 6). The W-AGF then initiates W-CP signalling connection release (step 7), and finally, the 5G-RG disconnects the AUN3 device (step 8).](e417ae35ab07134888be901c201d54cd_img.jpg) + +``` + +sequenceDiagram + participant AUN3 + participant 5G-RG + participant W-AGF + participant AMF + participant SMF + participant UPF + participant PCF + + Note right of 5G-RG: 1a. UE-Initiated Deregistration procedure TS 23.502 Figure 4.2.2.3.2-1 steps 1 to 7 + Note right of 5G-RG: 1b. Network Initiated deregistration procedure TS 23.502 Figure 4.2.2.3.3-1 steps 1 to 6 + + AMF->>W-AGF: 2. N2 UE Context Release Command + W-AGF-->>AMF: 3. N2 UE Context Release Complete + Note right of W-AGF: 4. Identify AUN3 devices connected to the 5G-RG + W-AGF->>AMF: 5. AUN3: UE Context Release Request + Note right of AMF: 6. AMF-Initiated deregistration of all AUN3 devices + Note right of W-AGF: 7. W-CP signalling connection release + 5G-RG->>AUN3: 8. disconnection + +``` + +Sequence diagram illustrating the 5G-RG Deregistration procedure via W-5GAN when serving AUN3 devices. The diagram shows interactions between AUN3, 5G-RG, W-AGF, AMF, SMF, UPF, and PCF. The procedure starts with UE-Initiated or Network Initiated deregistration (steps 1a and 1b). The AMF sends an N2 UE Context Release Command to the W-AGF (step 2), which responds with N2 UE Context Release Complete (step 3). The W-AGF then identifies AUN3 devices connected to the 5G-RG (step 4) and sends an AUN3: UE Context Release Request to the AMF (step 5). The AMF initiates deregistration of all AUN3 devices (step 6). The W-AGF then initiates W-CP signalling connection release (step 7), and finally, the 5G-RG disconnects the AUN3 device (step 8). + +**Figure 7.2.8.3-1: 5G-RG Deregistration procedure via W-5GAN when serving AUN3 devices** + +1-3. The same as steps 1-3 for Figure 7.2.1-1 with the following modification: + +In the case of 5G-RG initiated deregistration, 5G-RG shall first deregister each of the registered AUN3 devices connected to it (if any) before initiating the deregistration of itself. + +4. W-AGF controls if there exist any AUN3 devices connected to the 5G-RG that are registered to the 5GC through the W-AGF. If there are no AUN3 devices, then steps 5 and 6 shall be ignored. + +NOTE 1: How the W-AGF temporarily maintains the mapping of AUN3 devices and 5G-RG to perform steps 5 and 6 when the 5G-RG's context is released is based on implementation. + +5. [conditional] For each AUN3 device identified in step 4, the W-AGF shall send AN Release request as specified in clause 4.2.6 of TS 23.502 [3]. Here, the cause should indicate the disconnection of 5G-RG. + +6. [conditional] Upon receiving the AN Release request with the cause specified in step 5, the AMF shall initiate deregistration of the AUN3 device as specified in clause 4.2.2.3.3 of TS 23.502 [3]. The cause in the deregistration message should indicate the disconnection of 5G-RG. + +7. The W-AGF may initiate the release of the signalling connection between 5G-RG and W-AGF. + +NOTE 2: Whether this step is needed, and if so, the details of this step are defined by BBF and/or CableLabs. + +8. The RG disconnects the AUN3 device. How this is done is outside of 3GPP scope. + +#### 7.2.8.4 N2 release related with a 5G-RG also serving AUN3 devices + +When a W-AGF receives a N2 UE Context Release Command for a N2 connection related with a 5G -RG, the W-AGF identifies if there exist any AUN3 device connected to the 5G-RG through the W-AGF. For each identified AUN3 device, the W-AGF invokes step 5 and 6 of Figure 7.2.8.3-1. + +## 7.3 Session Management procedures + +### 7.3.0 General + +This clause specifies the delta for Session Management procedure defined in TS 23.502 [3] clause 4.3 for 5G-RG and FN-RG. + +### 7.3.1 5G-RG Requested PDU Session Establishment via W-5GAN + +#### 7.3.1.1 5G-RG PDU Session establishment via W-5GAN + +Clause 7.3.1.1 specifies how a 5G-RG can establish a PDU Session via an W-5GAN as well as to hand over an existing PDU Session between 3GPP access and W-5GAN. The procedure applies in non-roaming scenarios. + +The PDU Session Establishment procedure specified in TS 23.502 [3] clause 4.3.2.2.1 applies with the following changes. + +![Sequence diagram for 5G-RG PDU Session establishment via W-5GAN. The diagram shows interactions between 5G-RG, W-AGF, AMF, and Other CP and UP functions. The process starts with a W-CP signalling connection between 5G-RG and W-AGF. Step 1a: 5G-RG sends a NAS-PDU (PDU Session Establishment Request) to W-AGF. Step 1b: W-AGF forwards it as an N2 Uplink NAS Transport (NAS-PDU) to AMF. Step 2a: AMF performs steps 2-11 from TS 23.502 Figure 4.3.2.2.1-1. Step 2b: AMF sends an N2 PDU Session Resource Setup Request (QoS profile(s), PDU Session ID, PDU Session Establishment Accept) to W-AGF. Step 3: W-AGF determines W-UP resources needed. Step 4: W-AGF sends a W-UP resource(s) setup (W-5GAN AS parameters) to 5G-RG. Step 5: W-AGF sends a NAS-PDU (PDU Session Establishment Accept) to 5G-RG. Step 6: W-AGF sends an N2 PDU Session Resource Setup Response to AMF. Step 7: AMF performs all steps in TS 23.502 Figure 4.3.2.2.1-1 after step 14.](ccf6853c7291703cb04568057fef5849_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-AGF + participant AMF + participant Other CP and UP functions + + Note left of 5G-RG: W-CP signalling connection + 5G-RG->>W-AGF: 1a. W-CP (NAS-PDU [PDU Session Establishment Request]) + W-AGF->>AMF: 1b. N2 Uplink NAS Transport (NAS-PDU) + Note right of AMF: 2a. Step 2-11 in TS 23.502 Figure 4.3.2.2.1-1 + AMF->>W-AGF: 2b. N2 PDU Session Resource Setup Request (QoS profile(s), PDU Session ID, PDU Session Establishment Accept) + Note right of W-AGF: 3. Determine W-UP resources needed + W-AGF->>5G-RG: 4. W-UP resource(s) setup (W-5GAN AS parameters) + W-AGF->>5G-RG: 5. W-CP (NAS-PDU [PDU Session Establishment Accept]) + W-AGF->>AMF: 6. N2 PDU Session Resource Setup Response + Note right of AMF: 7. All steps in TS 23.502 Figure 4.3.2.2.1-1 after step 14 + +``` + +Sequence diagram for 5G-RG PDU Session establishment via W-5GAN. The diagram shows interactions between 5G-RG, W-AGF, AMF, and Other CP and UP functions. The process starts with a W-CP signalling connection between 5G-RG and W-AGF. Step 1a: 5G-RG sends a NAS-PDU (PDU Session Establishment Request) to W-AGF. Step 1b: W-AGF forwards it as an N2 Uplink NAS Transport (NAS-PDU) to AMF. Step 2a: AMF performs steps 2-11 from TS 23.502 Figure 4.3.2.2.1-1. Step 2b: AMF sends an N2 PDU Session Resource Setup Request (QoS profile(s), PDU Session ID, PDU Session Establishment Accept) to W-AGF. Step 3: W-AGF determines W-UP resources needed. Step 4: W-AGF sends a W-UP resource(s) setup (W-5GAN AS parameters) to 5G-RG. Step 5: W-AGF sends a NAS-PDU (PDU Session Establishment Accept) to 5G-RG. Step 6: W-AGF sends an N2 PDU Session Resource Setup Response to AMF. Step 7: AMF performs all steps in TS 23.502 Figure 4.3.2.2.1-1 after step 14. + +Figure 7.3.1.1-1: 5G-RG PDU Session establishment via W-5GAN + +1. The 5G-RG shall send a PDU Session Establishment Request message to AMF as specified in step 1 in clause 4.3.2.2.1 of TS 23.502 [3]. This message shall be sent to W-AGF via the W-CP signalling connection and the W-AGF shall transparently forward it in a N2 Uplink NAS transport message (NAS message, User location information, W-AGF identities) to AMF in the 5GC. + +The W-AGF identities parameter may be included by the W-AGF and contains a list of Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations at W-AGF and can be used by SMF in step 8 in TS 23.502 [3] clause 4.3.2.2.1 as input to select an UPF. + +If the 5G-RG needs Hybrid Access with Multi-Access PDU Session service, the 5G-RG requests a MA PDU Session as defined in clause 4.12. In that case, Steps of TS 23.502 [3] clause 4.3.2.2.1 apply as modified by clause 4.12. + +- 2a. Steps 2-11 specified in TS 23.502 [3] clause 4.3.2.2.1 are executed according to the PDU Session Establishment procedure over 3GPP access with the deviation that in step 3 an additional parameter W-AGF identities received by the AMF from the W-AGF can be sent from AMF to SMF. SMF can use W-AGF identities in step 8 of TS 23.502 [3] clause 4.3.2.2.1 for UPF selection. + +For the LADN service, if the AMF detects the requested DNN is corresponding to a LADN DNN or the default DNN of the requesting S-NSSAI is a LADN DNN, and the access type of 5G-RG equals to wireline access, the AMF will assign "UE Presence in LADN service area" indication to be "OUT", and provide this indication to SMF. + +NOTE: This induces the SMF to reject the PDU Session establishment request + +- 2b. As described in steps 11 and 12 of TS 23.502 [3] clause 4.3.2.2.1, the AMF shall under request of the SMF send a N2 PDU Session Resource Setup Request message to W-AGF to establish the access resources for this PDU Session. The differences with steps 11 and 12 of TS 23.502 [3] clause 4.3.2.2.1 are: + - The W-AGF shall ignore RSN if received from 5GC. +3. Based on its own policies and configuration and based on the QoS flows and QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session. For example, the W-AGF may decide to establish one W-UP resource and associate all QoS profiles with this W-UP resource. In this case, all QoS Flows of the PDU Session would be transferred over one W-UP resource. +- 4a. The W-AGF sets up the W-UP resources for the PDU session. This step is specified by BBF for W-5BGAN and by CableLabs for W-5GCAN. The access dependent W-UP resource setup procedure shall provide the identity of the PDU Session associated with the W-UP resource. The W-UP resource setup procedure should support to bind W-UP resources to individual QFI(s) as specified in clause 4.4. The W-UP resource request may also contain other access layer information (e.g., VLAN id) specific for the W5GAN. +5. After all W-UP resources are established, the W-AGF shall forward to 5G-RG via the W-CP signalling connection the PDU Session Establishment Accept message received in step 2b. +6. The W-AGF shall send to AMF an N2 PDU Session Resource Setup Response (PDU Session ID, AN Tunnel Info, List of accepted/rejected QFI(s), User Plane Security Enforcement Policy Notification). +7. All steps specified in TS 23.502 [3] clause 4.3.2.2.1 after step 14 are executed according to the PDU Session Establishment procedure over 3GPP access. + +#### 7.3.1.2 PDU Session Establishment with ACS Discovery + +This clause specifies how a 5G-RG can establish a PDU Session with ACS Discovery. The ACS discovery mechanism is further specified in clause 9.6.2. + +When a 5G-RG performs ACS Discovery during PDU session establishment procedure, the UE Requested PDU Session Establishment via 3GPP Access as described in TS 23.502 [3] clause 4.3.2.2.1 is used, with the following differences: + +- UE is replaced by 5G-RG. +- In FWA scenario the (R)AN is replaced by NG RAN access network, in wireline scenario the (R)AN is replaced by W-5GAN and in HA scenario the (R)AN represents the selected access where the PDU session is being established. +- Step 1. When the 5G-RG sends the PDU session establishment request it includes the DNN which is corresponding to the ACS (per local configuration or per URSP policies). The UE may send in PCO a request to provide ACS information. The UE may include the ACS information request in a DHCP request sent after PDU Session has been established. +- Step 4. The UDM may send the ACS information to the SMF together with the subscription data based on the DNN. + +- Step 10. The SMF includes the ACS information in the N1 SM information (PCO) if it has been requested by the UE in step 1 and if it is available at the SMF (if received in Step4). +- Step 19: The 5G-RG may request to receive ACS information via DHCP as described in clause 9.6.2. +- The 5G-RG uses the received ACS information to establish a connection with the ACS. + +NOTE: The ACS discovery via PCO or via DHCP are mutually exclusive. + +### 7.3.2 5G-RG or Network Requested PDU Session Modification via W-5GAN + +The UE or network requested PDU Session Modification procedure via W-5GAN access is depicted in figure 7.3.2-1. The procedure applies in non-roaming scenarios. + +The procedure below is based on the PDU Session Modification procedure specified in TS 23.502 [3] clause 4.3.3.2. + +![Sequence diagram for 5G-RG or Network Requested PDU Session Modification via W-5GAN. Lifelines: 5G-RG, W-AGF, AMF, SMF, UPF, PCF. The diagram shows the flow of messages for PDU session modification, starting with a request from the 5G-RG to the AMF via the W-AGF, followed by internal network processing and responses back to the 5G-RG.](077f85b82901283b4657fd2b45fc0294_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-AGF + participant AMF + participant SMF + participant UPF + participant PCF + + Note left of 5G-RG: W-CP signalling connection + 5G-RG->>AMF: 1. PDU Session Modification Request + Note right of AMF: 2. UE or network requested PDU Session Modification TS 23.502 Figure 4.3.3.2-1, steps 1a-1e and steps 2-3 + AMF->>W-AGF: 3. N2 PDU Session Resource Modify Request + Note left of W-AGF: 4. W-CP resource modification + W-AGF->>AMF: 5. N2 PDU Session Resource Modify Response + Note right of AMF: 6. UE or network requested PDU Session Modification TS 23.502 Figure 4.3.3.2-1, step 7 + AMF->>W-AGF: 7a. NAS message (PDU Session Modification Command) + W-AGF->>5G-RG: 7b. NAS message (PDU Session Modification Ack) + AMF->>W-AGF: 8. N2 Uplink NAS transport + Note right of AMF: 9. UE or network requested PDU Session Modification TS 23.502 Figure 4.3.3.2-1, all steps after step 10 + +``` + +Sequence diagram for 5G-RG or Network Requested PDU Session Modification via W-5GAN. Lifelines: 5G-RG, W-AGF, AMF, SMF, UPF, PCF. The diagram shows the flow of messages for PDU session modification, starting with a request from the 5G-RG to the AMF via the W-AGF, followed by internal network processing and responses back to the 5G-RG. + +Figure 7.3.2-1: 5G-RG or Network Requested PDU Session Modification via W-5GAN + +1. If the PDU Session Modification procedure is initiated by the UE, the UE shall send a PDU Session Modification Request message to AMF as specified in TS 23.502 [3] step 1 of clause 4.3.2.2. The message shall be sent to W-AGF via W-CP signalling connection. The W-AGF shall transparently forward the PDU Session Modification Request to AMF/SMF. +2. The steps 1a (from AMF) to 1e and steps 2-3 as per the PDU Session Modification procedure in TS 23.502 [3] clause 4.3.3.2 are executed. + +3. The AMF sends N2 PDU Session Resource Modify Request (N2 SM information received from SMF, NAS message) message to the W-AGF. This step is the same as step 4 in clause 4.3.3.2. + 4. The W-AGF may issue W-CP resource modification procedure (out of scope of 3GPP) with the 5G-RG that is related with the information received from SMF. Based on the N2 SM information received from the SMF, the W-AGF may perform following: + - 4a. [Conditional] The W-AGF may decide to create a new W-UP resource for the new QoS Flow(s). + - 4b. [Conditional] The W-AGF may decide to add or remove QoS Flow(s) to/from an existing W-UP resource. + - 4c. [Conditional] The W-AGF may decide to delete an existing W-UP resource, e.g. when there is no QoS Flow mapped to this W-UP resource. +- NOTE: If the W-AGF has included the Default W-UP resource indication during the establishment of one of the W-UP resources of the PDU Session, the W-AGF may not update the mapping between QoS Flows and W-UP resources. +5. The W-AGF acknowledges N2 PDU Session Resource Modify Request by sending a N2 PDU Session Resource Modify Response Message to the AMF to acknowledge the success or failure of the request. + 6. Step 7 as per the PDU Session Modification procedure in TS 23.502 [3] clause 4.3.3.2 is executed. + 7. The W-AGF sends the PDU Session Modification Command to 5G-RG (if received in step 3) and receives the response message from 5G-RG. + +Steps 4a/4c and step 7 may happen consecutively. Steps 7b may happen before step 4b/4d. + 8. The W-AGF forwards the NAS message to the AMF. + 9. All the steps after step 10 in TS 23.502 [3] clause 4.3.3.2 are executed according to the general PDU Session Modification procedure. + +### 7.3.3 5G-RG or Network Requested PDU Session Release via W-5GAN + +Clause 7.3.3 specifies how a 5G-RG or network can release a PDU Session via a W-5GAN. The 5G-RG requested PDU Session Release procedure via W-5GAN access applies in non-roaming scenarios. + +If the 5G-RG is simultaneously registered to a 3GPP access in a PLMN or SNPN different from the PLMN or SNPN of the W-AGF, the functional entities in the following procedures are located in the PLMN or SNPN of the W-AGF. + +- NOTE: If the 5G-RG is simultaneously registered to 3GPP access in the same PLMN or SNPN as W-5GAN access, when W-5GAN is not available to the 5G-RG (e.g. 5G-RG is disconnected from W-5GAN) or 5G-RG is in CM-IDLE for W-5GAN access, the 5G-RG may perform the PDU Session Release procedure via 3GPP access as described in TS 23.502 [3] clause 4.3.4. + +![Sequence diagram for 5G-RG or Network Requested PDU Session Release via W-5GAN access. The diagram shows interactions between 5G-RG, W-AGF, AMF, SMF, UPF, and PCF. The process starts with existing PDU sessions, followed by a release request from 5G-RG to AMF via W-AGF. The AMF then initiates the release procedure (steps 1a to 3). The AMF sends an N2 PDU Session Resource Release Command to the W-AGF. The W-AGF triggers W-UP resource release. The W-AGF sends an N2 PDU Session Resource Release Response to the AMF. The AMF then initiates the release procedure (step 7). The W-AGF delivers the NAS message (PDU Session Release Command) to the 5G-RG. The 5G-RG sends a NAS message (PDU Session Release Ack) to the W-AGF. The W-AGF sends an N2 Uplink NAS transport to the AMF. Finally, the AMF initiates the release procedure (all steps after step 9).](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant W-AGF + participant AMF + participant SMF + participant UPF + participant PCF + + Note over 5G-RG: 1. One or more PDU Sessions are already established for the 5G-RG + 5G-RG->>AMF: 2. PDU Session Release Request + Note over AMF: 3. UE or network requested PDU Session Release TS 23.502 Figure 4.3.4.2-1, steps 1a to 3 + AMF->>W-AGF: 4. N2 PDU Session Resource Release Command + Note over W-AGF: 5. W-UP resource release + W-AGF->>AMF: 6. N2 PDU Session Resource Release Response + Note over AMF: 7. UE or network requested PDU Session Release TS 23.502 Figure 4.3.4.2-1, step 7 + AMF->>W-AGF: 8. NAS message (PDU Session Release Command) + W-AGF->>5G-RG: 8. NAS message (PDU Session Release Command) + 5G-RG->>W-AGF: 9. NAS message (PDU Session Release Ack) + W-AGF->>AMF: 10. N2 Uplink NAS transport + Note over AMF: 11. UE or network requested PDU Session Release TS 23.502 Figure 4.3.4.2-1, all steps after step 9 + +``` + +Sequence diagram for 5G-RG or Network Requested PDU Session Release via W-5GAN access. The diagram shows interactions between 5G-RG, W-AGF, AMF, SMF, UPF, and PCF. The process starts with existing PDU sessions, followed by a release request from 5G-RG to AMF via W-AGF. The AMF then initiates the release procedure (steps 1a to 3). The AMF sends an N2 PDU Session Resource Release Command to the W-AGF. The W-AGF triggers W-UP resource release. The W-AGF sends an N2 PDU Session Resource Release Response to the AMF. The AMF then initiates the release procedure (step 7). The W-AGF delivers the NAS message (PDU Session Release Command) to the 5G-RG. The 5G-RG sends a NAS message (PDU Session Release Ack) to the W-AGF. The W-AGF sends an N2 Uplink NAS transport to the AMF. Finally, the AMF initiates the release procedure (all steps after step 9). + +**Figure 7.3.3-1: 5G-RG or Network Requested PDU Session Release via W-5GAN access** + +1. One or more PDU Sessions are already established for the 5G-RG using the procedure described in clause 7.3.1. +2. The 5G-RG sends a PDU session release request (N1 SM container (PDU Session Release Request), PDU Session ID) to the AMF via the W-AGF as defined in clause 4.3.4 of TS 23.502 [3]. +3. The steps 1a (from AMF) to 3 according to the PDU Session Release procedure defined in TS 23.502 [3] clause 4.3.4.2 are executed. +4. This step is the same as step 4 in clause 4.3.4.2 of TS 23.502 [3]. +5. Upon receiving AN session release request message from the AMF, the W-AGF can trigger the release of the corresponding W-UP resource with procedure out of scope of 3GPP. +6. This step is the same as step 6 in clause 4.3.4.2 of TS 23.502 [3]. +7. Step 7 according to the PDU Session Release procedure defined in clause 4.3.4.2 are executed. +8. The W-AGF delivers the NAS message (N1 SM container (PDU Session Release Command), PDU Session ID, Cause) to the 5G-RG. +9. The 5G-RG sends a NAS message (N1 SM container (PDU Session Release Ack), PDU Session ID) to the W-AGF. +10. This step is the same as step 9 in clause 4.3.4.2 of TS 23.502 [3]. + +Steps 5 and 8 may happen consecutively. Step 9 may happen before step 5. + +11. All steps after step 9 in the PDU Session Release procedure defined in TS 23.502 [3] clause 4.3.4.2 are executed. + +The network requested PDU Session Release procedure via W-5GAN access is the same as the network requested PDU Session Release Procedure specified in TS 23.502 [3] clause 4.3.4.2 for Non-Roaming with the following differences: + +- The (R)AN corresponds to a W-AGF. +- In step 5, upon receiving N2 SM request to release the AN resources associated with the PDU Session from the AMF, the W-AGF can trigger the release of the corresponding W-UP resource to the 5G-RG as specified in step 5, in Figure 7.3.3-1. + +### 7.3.4 FN-RG related PDU Session Establishment via W-5GAN + +The procedure below is based on the PDU Session Establishment procedure specified in TS 23.502 [3] clause 4.3.2.2.1. + +![Sequence diagram for FN-RG related PDU Session Establishment via W-5GAN. The diagram shows interactions between FN-RG, Wireline ANs, W-AGF, AMF, and Other CP and UP functions. The process starts with an L2 message from FN-RG to W-AGF, followed by an N2 Uplink NAS Transport from W-AGF to AMF. The AMF then performs steps 2-11 from TS 23.502. The W-AGF determines W-UP resources needed and sends an N2 PDU Session Resource Setup Request to the AMF. The AMF responds with an N2 PDU Session Resource Setup Response. Finally, the W-AGF sends an L2 message (IP address/prefix response) to the FN-RG. A dashed box indicates a deferred IP address allocation step.](06291c5328a7a4335d41a48850a3a207_img.jpg) + +``` + +sequenceDiagram + participant FN-RG + participant Wireline ANs + participant W-AGF + participant AMF + participant Other CP and UP functions + + Note left of FN-RG: 0. [Optional] L2 message (IP address/prefix request) + FN-RG->>W-AGF: 0. L2 message (IP address/prefix request) + W-AGF->>AMF: 1. N2 Uplink NAS Transport (NAS-PDU (PDU Session Establishment Request)) + AMF->>Other CP and UP functions: 2a. Steps 2-11 in TS 23.502, figure 4.3.2.2.1-1. + AMF->>W-AGF: 2b. N2 PDU Session Resource Setup Request (QoS profile(s), PDU Session ID, PDU Session Establishment Accept) + W-AGF->>Wireline ANs: 3. Determine W-UP resources needed + W-AGF->>AMF: 4. N2 PDU Session Resource Setup Response + AMF->>Other CP and UP functions: 5. All steps in TS 23.502, figure 4.3.2.2.1-1 after step 13. + Note right of AMF: 6a. Deferred IP address allocation + W-AGF->>FN-RG: 6b. L2 message (IP address/prefix response) + +``` + +Sequence diagram for FN-RG related PDU Session Establishment via W-5GAN. The diagram shows interactions between FN-RG, Wireline ANs, W-AGF, AMF, and Other CP and UP functions. The process starts with an L2 message from FN-RG to W-AGF, followed by an N2 Uplink NAS Transport from W-AGF to AMF. The AMF then performs steps 2-11 from TS 23.502. The W-AGF determines W-UP resources needed and sends an N2 PDU Session Resource Setup Request to the AMF. The AMF responds with an N2 PDU Session Resource Setup Response. Finally, the W-AGF sends an L2 message (IP address/prefix response) to the FN-RG. A dashed box indicates a deferred IP address allocation step. + +Figure 7.3.4-1: FN-RG related PDU Session Establishment via W-5GAN + +0. [Optional] FN-RG sends an IP address/prefix request to the W-AGF via the L2 connection established in clause 7.2.1.3. + +NOTE: This IP address/prefix request can also be sent by FN-RG later in this procedure; the W-AGF may store this and complete the address allocation via 5GC after the PDU session setup. The means of carrying the IP address/prefix request/response between FN-BRG and W-AGF is defined in BBF TR-456 [9], WT-457 [10] and between FN-CRG and W-AGF is defined in CableLabs WR-TR-5WWC-ARCH [27]. + +1. After the registration procedure is completed, the W-AGF may establish PDU session(s) on behalf of the FN-RG. The trigger for W-AGF to initiate a PDU establishment process is defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27]. + +The W-AGF generates a PDU session ID and derives the parameters for the PDU Session (PDU Session type, S-NSSAI, DNN, SSC mode, etc.) based on signalling received from the FN-RG (DHCP, IPv6 RS, etc.), on local configuration, and on information received from the 5GC (e.g. during the Registration procedure or when received URSP rules) and stored on the W-AGF. + +If W-AGF has received a DHCPv4/DHCPv6 request from the FN-RG, it may request a PDU Session with deferred IP address allocation. + +The W-AGF sends a NAS PDU Establishment Request to the AMF. This request contains the PDU Session ID, and may contain a Requested PDU Session Type, a Requested SSC mode, 5GSM Capability PCO, SM PDU DN Request Container, Number of Packet Filters. In the case of PDU Session Type IPv6 or IPv4v6, the PDU Session Establishment Request may contain an interface identifier of the FN-RG IPv6 link local address associated with the PDU Session. + +The W-AGF sends NAS PDU Establishment Request in a N2 Uplink NAS transport message (NAS message, User location information, W-AGF identities). + +The W-AGF identities contains a list of Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations at W-AGF and can be used by SMF in step 8 in TS 23.502 [3] clause 4.3.2.2.1 as input to select an UPF. + +- 2a. The PDU session request is processed in the 5GC as per steps 2-11 of TS 23.502 [3] clause 4.3.2.2.1. These steps are for UPF selection and resource reservation/allocation in the UPF. With regard to TS 23.502 [3], an additional parameter is sent from AMF to SMF i.e. the list of Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations at W-AGF received by the AMF from the W-AGF. The SMF can use it in step 8 for UPF selection as per clause 4.3.2.2.1. In the case of PDU Session Type IPv6 or IPv4v6, in step 11 of TS 23.502 [3] clause 4.3.2.2.1: + +- The PDU Session Establishment Accept contains the SMF IPv6 link local address associated with the PDU Session if the RAT Type in the Nsmf\_PDUSession\_CreateSMContext request equals to wireline access. +- The PDU Session Establishment Accept contains the interface identifier of the FN-RG IPv6 link local address if provided in step 1. Otherwise a SMF allocated FN-RG interface identifier is provided. + +- 2b. The SMF responds via AMF as defined in step 11 of clause 4.3.2.2.1 in TS 23.502 [3] with an N2 PDU Session Resource Setup Request that includes QoS profile(s), PDU Session ID, PDU Session Establishment Accept and the N3 tunnel endpoint information for the UPF. The differences with step 11/12 of TS 23.502 [3] clause 4.3.2.2.1 are: + +- The W-AGF shall ignore RSN if received from 5GC. + +3. Based on its own policies, configuration and based on the QoS flows, QoS parameters received in the previous step, the W-AGF shall determine what W-UP resources are needed for the PDU session. + +The W-AGF may, as defined in BBF TR-456 [9], WT-457 [10] and CableLabs WR-TR-5WWC-ARCH [27], perform Access specific resource reservation with the AN, that is, it sets up the W-UP resources for the PDU session. + +4. The W-AGF allocates AN N3 tunnel information for the PDU Session and includes the AN N3 tunnel endpoint information in the N2 PDU Session Resource Setup Response message to the AMF. + +5. The PDU session setup procedure is completed in 5GC. All steps after step 13 as specified in TS 23.502 [3] figure 4.3.2.2.1 are executed. + +- 6a. If W-AGF requested deferred IP address allocation in step 1 and this was accepted by the network, the W-AGF sends on the user Plane of the PDU Session any DHCP or RS message received beforehand from the FN-RG to the 5GC to obtain the IP address/prefix. + +- 6b. W-AGF completes the IP address/prefix allocation with the FN-RG via the established L2 connection. If W-AGF did not request deferred IP address allocation in step 1a, the IP address/prefix sent back to the FN-RG is the UE IP address/prefix delivered in NAS message in step 2b. If W-AGF requested deferred IP address allocation in step 1a, the IP address/prefix sent back to the FN-RG is the UE IP address/prefix delivered via deferred IP address allocation procedures in step 6a. + +### 7.3.5 CN-initiated selective deactivation of UP connection of an existing PDU Session associated with W-5GAN Access + +The procedure described in TS 23.502 [3] clause 4.3.7 (CN-initiated selective deactivation of UP connection of an existing PDU Session) is used for CN-initiated selective deactivation of UP connection for an established PDU Session associated with W-5GAN Access of a 5G-RG/FN-RG in CM-CONNECTED state, with the following exceptions: + +- The NG-RAN corresponds to a W-AGF. + +- The user plane resource between the 5G-RG/FN-RG and W-AGF, is released not with RRC signalling but with procedure in the scope of BBF/Cablelabs. + +### 7.3.6 FN-RG or Network Requested PDU Session Modification via W-5GAN + +The PDU session modification procedure for the FN-RG is similar to that of 5G-RG described in clause 7.3.2 but with the following differences: + +- The 5G-RG is replaced with an FN-RG. +- W-AGF acts on behalf of FN-RG, as an endpoint for N1 signalling. The triggers for initiating PDU Session Modification by the W-AGF are defined by BBF (BBF TR-456 [9]) and Cablelabs. +- If applicable, based on BBF specification BBF TR-456 [9] and Cablelabs specification, in step 1, the W-AGF initiates a PDU Session Modification Request to the AMF on behalf of FN-RG. +- W-AGF may issue L-W-CP resource modification procedure with the FN-RG that is related with the information received from the SMF as in step 4. The actions performed by W-AGF are defined by BBF (BBF TR-456 [9]) and Cablelabs. +- In step 4, L-W-UP resources may be modified by the W-AGF. +- Steps 7a and 7b of clause 7.3.2 are not valid for the FN-RG. The W-AGF creates an Uplink NAS transport message to the AMF, which contains the PDU Session Modification Ack as in step 8. + +### 7.3.7 FN-RG or Network Requested PDU Session Release via W-5GAN + +The PDU session release procedure for the FN-RG is similar to that of 5G-RG described in clause 7.3.3 but with the following differences: + +- The 5G-RG is replaced with an FN-RG. +- W-AGF acts on behalf of FN-RG, as an endpoint for N1 signalling. +- In step 2, the W-AGF sends a PDU session release request to the AMF on behalf of FN-RG. +- In step 5, upon receiving AN session release request message from the AMF, the W-AGF can trigger the release of the corresponding L-W-UP resource with procedure in scope of BBF/CableLabs. +- Steps 8 and 9 of clause 7.3.3 are not valid for the FN-RG. The W-AGF creates an Uplink NAS transport message to the AMF, which contains the PDU Session Release Ack as in step 10. + +### 7.3.8 Session Management Procedures for AUN3 devices + +#### 7.3.8.1 PDU Session Establishment of AUN3 device behind 5G-RG + +This clause specifies the PDU Session Establishment for an AUN3 device served by a 5G-RG as defined in clause 4.10c. + +A distinct PDU session is established for each AUN3 device. + +After the registration from the AUN3 device, the 5G-RG initiates the establishment of a PDU Session on behalf of the AUN3 device + +The PDU Session is established as specified in clause 7.3.1.1 with following differences: + +- Steps 1a, 1b and 2b are executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection. +- At step 3 in figure 4.3.2.2.1 of TS 23.502 [3], the AMF sends the AUN3 SUPI as the SUPI of the PDU session in the Nsmf\_PDUSession\_CreateSMContext Request sent to the SMF. + +- Steps 5 and 6 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection. +- At step 7b in figure 4.3.2.2.1 [3] of TS 23.502 [3], the SMF sends in the Npcf\_SMPolicyControl\_Create Request the SUPI of the PDU session (i.e. the AUN3 SUPI). + +#### 7.3.8.2 PDU Session Modification of AUN3 device behind 5G-RG + +This clause specifies the PDU Session Modification for an AUN3 device served by a 5G-RG as defined in clause 4.5.3. + +The PDU Session modification procedure shall use clause 7.3.2 with following differences: + +- Step 1 is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection. +- At step 1a in figure 4.3.3.2-1 of TS 23.502 [3], the AMF sends the AUN3 SUPI as the SUPI of the PDU session. +- At step 2 in figure 4.3.3.2-1 of TS 23.502 [3], the SMF sends in the Npcf\_SMPolicyControl\_Update Request the SUPI of the PDU session (i.e. the AUN3 SUPI). +- Steps 3 and 5 are executed over the AUN3 device's N2 connection. +- Steps 7 and 8 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection. +- Only 5GC initiated PDU Session modification is supported in this Release. + +#### 7.3.8.3 PDU Session Release of AUN3 device behind 5G-RG + +This clause specifies the PDU Session Release for an AUN3 device served by a 5G-RG as defined in clause 4.10c. This clause applies only to 5G-RG. + +AUN3 device may trigger explicit request for connection release, or it may be unreachable (on the 5G-RG to AUN3 device interface). In such scenarios 5G-RG may need to release the PDU session of the AUN3 device. + +NOTE: How an AUN3 device can trigger the release of a PDU Session is out of scope of 3GPP specifications. + +PDU session release for a specific AUN3 device can also be initiated by the 5GC (e.g., the subscription of the AUN3 device expires). + +The PDU Session release procedure shall use clause 7.3.3 with following differences: + +- Step 1 is executed over the AUN3 device's NAS signalling connection and AUN3 device's N2 connection. +In step 1a of figure 4.3.4.2-1 of TS 23.502 [3], the 5G-RG sends the PDU Session Release message on the AUN3 device's NAS connection. +- Steps 4 and 6 are executed over the AUN3 device's N2 connection. +- Steps 8-10 are executed over the AUN3 device's N2 connection and AUN3 device's NAS signalling connection. + +## 7.4 SMF and UPF interactions + +SMF and UPF interactions for 5G-RG and FN-RG follow the procedures defined in TS 23.502 [3] clause 4.4. + +## 7.5 User Profile management procedures + +When 5G-RG or FN-RG is used, the User Profile management procedures in TS 23.502 [3] clause 4.5 apply, with the differences described below: + +- The UE in TS 23.502 [3] clause 4.5 is replaced by 5G-RG or FN-RG. +- When 5G-RG or FN-RG is connected via W-5GAN, steering of roaming information is not applicable, since roaming is not supported. + +- The AMF updates 5G-RG context and FN-RG context stored at W-AGF to modify the RG Level Wireline Access Characteristics. + +## 7.6 Handover procedure + +### 7.6.1 General + +This clause includes the differences for 5G-RG comparing to TS 23.502 [3] clause 4.9. + +Handover procedures in this clause are not supported for FN-RG. SRVCC is not applicable to RG. + +### 7.6.2 Handover within NG-RAN + +If the 5G-RG is connected via FWA, the procedures in TS 23.502 [3] clause 4.9.1 apply with the differences shown as below: + +- UE is replaced by 5G-RG. + +### 7.6.3 Handover procedures between 3GPP access / 5GC and W-5GAN access + +#### 7.6.3.1 Handover of a PDU Session procedure from W-5GAN access to 3GPP access + +This clause specifies how to hand over a 5G-RG from a source W-5GAN access to a target 3GPP access and how a 5G-RG can handover a PDU Session from W-5GAN access to 3GPP access. It is based on the PDU Session Establishment procedure for 3GPP access as specified in clause 4.3.2 of TS 23.502 [3]. + +![Sequence diagram illustrating the handover of a PDU Session procedure from W-5GAN access to 3GPP access. The diagram shows interactions between 5G-RG, W-5GAN access (including W-AGF), RAN, AMF, SMF, UPF, and PCF. The procedure consists of three main steps: 1. Registration via 3GPP access (indicated by dashed lines between 5G-RG and AMF); 2. PDU session establishment procedure in 3GPP access using TS 23.502, clause 4.3.2.2.1 (indicated by a solid line from AMF to UPF); 3. Release of W-5GAN access resources using clause 7.3.3 steps 4 to 6, and TS 23.502, clause 4.3.4.2 step 7a (indicated by a solid line from SMF to W-5GAN access).](2071a5d5382d83adafa96687d358e5b2_img.jpg) + +Sequence diagram illustrating the handover of a PDU Session procedure from W-5GAN access to 3GPP access. The diagram shows interactions between 5G-RG, W-5GAN access (including W-AGF), RAN, AMF, SMF, UPF, and PCF. The procedure consists of three main steps: 1. Registration via 3GPP access (indicated by dashed lines between 5G-RG and AMF); 2. PDU session establishment procedure in 3GPP access using TS 23.502, clause 4.3.2.2.1 (indicated by a solid line from AMF to UPF); 3. Release of W-5GAN access resources using clause 7.3.3 steps 4 to 6, and TS 23.502, clause 4.3.4.2 step 7a (indicated by a solid line from SMF to W-5GAN access). + +**Figure 7.6.3.1-1: Handover of a PDU Session procedure from W-5GAN access to 3GPP access** + +The Handover of a PDU Session procedure specified in TS 23.502 [3] clause 4.9.2.1 applies with the following changes. + +- 1-2. These steps are the same as steps 1-2 in TS 23.502 [3] clause 4.9.2.1 with the difference that the UE is replaced by 5G-RG. +3. The SMF executes the release of resources in W-5GAN access by performing steps 4 to 6 specified in clause 7.3.3, followed by step 7a specified in clause 4.3.4.2 of TS 23.502 [3] in order to release the resources over the source W-5GAN access. Because the PDU Session shall not be released, the SMF shall not send the NAS PDU Session Release Command to the 5G-RG. Hence, in steps 4 and 6 of clause 7.3.3 as well as in step 7a in clause 4.3.4.2 of TS 23.502 [3], the messages do not include the N1 SM container but only the N2 PDU Session Resource Release Command (resp. Response). Since the PDU Session is not to be released, the SMF shall not execute step 7b in clause 4.3.4.2 of TS 23.502 [3] and the SM context between the AMF and the SMF is maintained. + +Steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to W-5GAN access to 3GPP access. + +#### 7.6.3.2 Handover of a PDU Session procedure from 3GPP to W-5GAN access + +This clause specifies how to hand over a 5G-RG from a source 3GPP access to a target W-5GAN access and how a 5G-RG can handover a PDU Session from 3GPP access to W-5GAN access. It is based on the PDU Session Establishment procedure for W-5GAN access as specified in clause 7.3.1. + +![Sequence diagram for handover of a PDU Session from 3GPP to W-5GAN access. The diagram shows the interaction between 5G-RG, W-5GAN access (including W-AGF), RAN, AMF, SMF, UPF, and PCF. The procedure consists of three main steps: 1. Registration via W-5GAN access (indicated by a dashed line from 5G-RG to AMF); 2. PDU session establishment procedure in clause 7.3.1 (indicated by a solid line from 5G-RG to UPF); 3. Release of 3GPP access resources using TS 23.502, clause 4.3.4.2 step 3b, then from step 4 to step 7a (indicated by a solid line from AMF to RAN).](76d19e4271bf243b20d55a98efd51483_img.jpg) + +Sequence diagram for handover of a PDU Session from 3GPP to W-5GAN access. The diagram shows the interaction between 5G-RG, W-5GAN access (including W-AGF), RAN, AMF, SMF, UPF, and PCF. The procedure consists of three main steps: 1. Registration via W-5GAN access (indicated by a dashed line from 5G-RG to AMF); 2. PDU session establishment procedure in clause 7.3.1 (indicated by a solid line from 5G-RG to UPF); 3. Release of 3GPP access resources using TS 23.502, clause 4.3.4.2 step 3b, then from step 4 to step 7a (indicated by a solid line from AMF to RAN). + +**Figure 7.6.3.2-1: Handover of a PDU Session from 3GPP access to W-5GAN access** + +The Handover of a PDU Session procedure specified in TS 23.502 [3] clause 4.9.2.2 applies with the following changes. + +1. If the 5G-RG is not registered via W-5GAN access, the 5G-RG shall initiate Registration procedure as defined in clause 7.2.1.1. +2. The 5G-RG performs PDU Session Establishment procedure in W-5GAN access with the PDU Session ID of the PDU Session to be moved as specified in clause 7.3.1. +- 3 This step is the same as step 3 in TS 23.502 [3] clause 4.9.2.2 with the difference that the UE is replaced by 5G-RG. If the User Plane of the PDU Session is already deactivated in 3GPP access, this step is skipped. + +Steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to W-5GAN access. + +### 7.6.4 Handover procedures between 3GPP access / EPS and W-5GAN/5GC access + +#### 7.6.4.1 Handover from 3GPP access / EPS to W-5GAN / 5GC + +![Sequence diagram for handover from EPS to W-5GAN/5GC. The diagram shows the interaction between 5G-RG, E-UTRAN, W-5GAN, AMF, MME, SGW, PGW + SMF/UPF, and HSS + AUSF/UDM. The procedure consists of four main steps: 0. PDN Connection established in EPC/E-UTRAN (indicated by a dashed line from E-UTRAN to PGW + SMF/UPF); 1. Registration procedure in W-5GAN/5GC access per clause 7.2.1.1 (indicated by a solid line from 5G-RG to AMF); 2. PDU Session Establishment per clause 7.3.1 (indicated by a solid line from 5G-RG to PGW + SMF/UPF); 3. EPC and E-UTRAN resource release per TS 23.401 figure 5.4.4.1-1 (indicated by a solid line from AMF to E-UTRAN).](1e56c223f51992d193febf7a161af7be_img.jpg) + +Sequence diagram for handover from EPS to W-5GAN/5GC. The diagram shows the interaction between 5G-RG, E-UTRAN, W-5GAN, AMF, MME, SGW, PGW + SMF/UPF, and HSS + AUSF/UDM. The procedure consists of four main steps: 0. PDN Connection established in EPC/E-UTRAN (indicated by a dashed line from E-UTRAN to PGW + SMF/UPF); 1. Registration procedure in W-5GAN/5GC access per clause 7.2.1.1 (indicated by a solid line from 5G-RG to AMF); 2. PDU Session Establishment per clause 7.3.1 (indicated by a solid line from 5G-RG to PGW + SMF/UPF); 3. EPC and E-UTRAN resource release per TS 23.401 figure 5.4.4.1-1 (indicated by a solid line from AMF to E-UTRAN). + +**Figure 7.6.4.1-1: Handover from EPS to W-5GAN/5GC** + +The procedure specified in clause 4.11.3.1 of TS 23.502 [3] (Handover from EPS to 5GC-N3IWF) applies with the following changes. + +0. Initial status: one or more PDN connections have been established in EPC between the 5G-RG and the PGW-C+SMF via E-UTRAN. +1. The 5G-RG initiates Registration procedure via W-5GAN access according to clause 7.2.1.1. +2. The 5G-RG initiates a PDU Session Establishment with Existing PDU Session indication in 5GC via W-5GAN access according to clause 7.3.1. +3. This step is the same as step 3 in clause 4.11.3.1 of TS 23.502 [3]. + +#### 7.6.4.2 Handover from W-5GAN / 5GC access to 3GPP-access / EPS + +![Sequence diagram for Handover from W-5GAN/5GC to EPS. The diagram shows the interaction between 5G-RG, E-UTRAN, W-5GAN, AMF, MME, SGW, PGW + SMF/UPF, and HSS + AUSF/UDM. The sequence starts with '0. PDU Session established in W-5GAN/5GC'. Step 1 is 'E-UTRAN Initial Attach with handover indication or TAU followed by PDN connection establishment with handover indication'. Step 2 is 'W-5GAN/5GC resource release per clause 7.3.3, steps 4-7'.](9b9262a549828579ab904148450734f6_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant E-UTRAN + participant W-5GAN + participant AMF + participant MME + participant SGW + participant PGW+SMF/UPF as PGW + SMF/UPF + participant HSS+AUSF/UDM as HSS + AUSF/UDM + + Note over 5G-RG, PGW+SMF/UPF: 0. PDU Session established in W-5GAN/5GC + Note over E-UTRAN, HSS+AUSF/UDM: 1. E-UTRAN Initial Attach with handover indication or TAU followed by PDN connection establishment with handover indication + Note over W-5GAN, PGW+SMF/UPF: 2. W-5GAN/5GC resource release per clause 7.3.3, steps 4-7 + +``` + +Sequence diagram for Handover from W-5GAN/5GC to EPS. The diagram shows the interaction between 5G-RG, E-UTRAN, W-5GAN, AMF, MME, SGW, PGW + SMF/UPF, and HSS + AUSF/UDM. The sequence starts with '0. PDU Session established in W-5GAN/5GC'. Step 1 is 'E-UTRAN Initial Attach with handover indication or TAU followed by PDN connection establishment with handover indication'. Step 2 is 'W-5GAN/5GC resource release per clause 7.3.3, steps 4-7'. + +**Figure 7.6.4.2-1: Handover from W-5GAN/5GC to EPS** + +0. Initial status: one or more PDU Sessions have been established via W-5GAN / 5GC access. During PDU Session setup, and in addition to what is specified in clause 4.3.2.2.1 of TS 23.502 [3], the PGW-C+SMF sends the FQDN related to the S5/S8 interface to the HSS+UDM which stores it. +1. If the UE is not attached to EPC/E-UTRAN, the UE initiates Handover Attach procedure in E-UTRAN as described in TS 23.401 [24] for a non-3GPP to EPS handover with "Handover" indication, except note 17. +If the UE is attached in EPC/E-UTRAN, the UE initiates the PDN Connection establishment with "Handover" indication procedure as described in TS 23.401 [24]. +2. The combined PGW-C+SMF initiates a network requested PDU Session Release via W-5GAN access according to clause 7.3.3, steps 4-7 to release the 5GC and W-5GAN resources with the following exception: + - Nsmf\_PDUSession\_SMContextStatusNotify service operation invoked by the SMF indicates the PDU Session is moved to another system. + - The Npcf\_SMPolicyControl\_Delete service operation to PCF shall not be performed. + +## 7.7 Support of specific services + +### 7.7.0 General + +This clause specifies the procedure for specific services for WWC scenario defined in clause 5. + +### 7.7.1 IPTV + +#### 7.7.1.1 Overview + +In this Release of the specification, in order to support IPTV services, following principles apply: + +- the 5G-RG supports IP PDU Session Type; + +- IP multicast traffic received from N6 interface is replicated by UPF and sent over PDU Sessions; +- IGMP or MLD messages from the STB or from the 5G-RG are terminated and managed by the UPF acting as PSA; +- IGMPv2 specified in RFC 2236 [33], IGMPv3 specified in RFC 4604 [21], for MLDv1 specified in RFC 2710 [36] and MLDv2 specified in RFC 4604 [21] are supported + +NOTE 1: Whether IGMP or MLD is exchanged with 5G RG or another entity (e.g. STB) is out of the scope of 3GPP. + +NOTE 2: In this specification the generic term IGMP refers to both IGMPv2 and IGMPv3 unless specifically defined. The term MLD refers to both MLDv1 and MLDv2 unless specifically defined. + +NOTE 3: The IGMP "Join message" and MLD "Join message" are generic terms used in this document to indicate the request of a host to join a multicast group which can express via IGMP and MLD Report message (e.g. Membership Report) or via Join message. + +- The SMF controls the support of IPTV by the UPF acting as PSA using PDR, FAR, QER, URR. This includes control of which IGMP and MLD requests the UPF is to accept or to deny. + +This clause describes the procedures that support IPTV in 5G system including the procedures below: + +- Registration and PDU Session Establishment procedure for IPTV is shown in clause 7.7.1.1.1. The Registration Procedure is used to register to 5GS and the PDU Session Establishment Procedure is used to establish the PDU Session used for IPTV Service. +- IPTV Access procedure shown in clause 7.7.1.1.2 may, depending on the deployment, be used to access the IPTV network, e.g. completing the IPTV Authentication and IP allocation. +- Unicast/Multicast Packets transmission procedure shown in clause 7.7.1.1.3. The procedure specifies how to transmit unicast/multicast packets related with IPTV service over 5GC. + +In this Release of the specification, the 5GC does not assume any traffic replication capability in the 5G AN (NG-RAN or W-5GAN). + +NOTE 4: In this release of the specification, the case of different STBs behind a 5G-RG is supported only when the STBs share the same access right. + +##### 7.7.1.1.1 Registration and PDU Session Establishment procedure for IPTV + +5G-RG perform Registration procedure described in clause 4.2.2.2.2 of TS 23.502 [3] with the following differences: + +- UE is replaced by 5G-RG. + +5G-RG perform PDU Session establishment procedure described in clause 4.3.2.2.1 of TS 23.502 [3] applies with the following differences and clarifications: + +- UE is replaced by 5G-RG. +- In step 1 of clause 4.3.2.2.1 of TS 23.502 [3], 5G-RG may indicate within the Protocol Configuration Options element that the UE requests to obtain the IPv4 address with DHCPv4. +- 5G-RG shall establish an IP-based PDU Session with a specific (DNN, S-NSSAI) for IPTV service. +- In step 7b and 9 of clause 4.3.2.2.1 of TS 23.502 [3], the PCF provides PCC Rules including information related to IPTV Service. This is specified in clause 9.3.1. +- The SMF sends to the UPF acting as PSA N4 rules such as PDR, FAR related to IP Multicast traffic allowed for the PDU Session. This may take place at steps 10a and 16a of clause 4.3.2.2.1 of TS 23.502 [3]. Such N4 rules are further described in clause 4.6. IP Multicast traffic allowed for the PDU Session corresponds to IPTV services allowed for the user. + +NOTE: The interactions between STB and 5G-RG are specified in TR-124 [5] in BBF and not shown in this clause. + +##### 7.7.1.1.2 IPTV Access procedure + +In the case of IPTV network access control based on the DHCP procedure, 5G-RG may be configured to retrieve via DHCP the IP address that it will use to access IPTV services. The DHCP procedure described in TS 23.501 [2] clause 5.8.2.2 is carried out with the difference shown below: + +- When the SMF receives the Uplink DHCP message, the SMF may be configured to insert the IPTV access control information as received in subscription data from UDM to the uplink DHCP message. + +NOTE 1: The IPTV access control information can include a line ID defined in RFC 3046 [20] or any other identity which can be used to identify the IPTV subscriber. This is based on IPTV deployment and 3GPP doesn't define the IPTV access control information that the SMF copies from subscription data to DHCP signalling. + +NOTE 2: The interactions between STB and 5G-RG is specified in BBF TR-124 [5]. + +NOTE 3: The description of interactions among the elements part of the IPTV network is out of 3GPP scope. + +### 7.7.1.1.3 Unicast/Multicast Packets transmission procedure + +5GS can support Unicast Service from IPTV network directly. + +In order to obtain the multicast service from IPTV network, the Multicast Packets transmission procedure should be performed. The procedure in figure 7.7.1.1-3 describes how the 5G-RG joins an IP multicast group. + +![Sequence diagram illustrating the 5G-RG join IP Multicast Packets transmission procedure. The diagram shows interactions between 5G-RG, (R)AN, AMF, UPF, SMF, PGF, UDM, and IPTV Multicast Server. The steps are: 1. user plane data: IGMP/MLD Join message from 5G-RG to UPF; 2. Apply N4 rules from UPF to SMF; 2b. UPF Usage Report from UPF to SMF; 2c. PCRT Report from SMF to PGF; 3. Multicast packets transmission from IPTV Multicast Server to UPF; 4. Multicast packets transmission over PDU Session from UPF to 5G-RG.](4f2887d5043c0923cf5b37ca0d80c60b_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant (R)AN + participant AMF + participant UPF + participant SMF + participant PGF + participant UDM + participant IPTV Multicast Server + + Note right of UPF: 2. Apply N4 rules + 5G-RG->>UPF: 1. user plane data: IGMP/MLD Join message + UPF->>SMF: 2b. UPF Usage Report + SMF->>PGF: 2c. PCRT Report + IPTV Multicast Server->>UPF: 3. Multicast packets transmission + UPF->>5G-RG: 4. Multicast packets transmission over PDU Session + +``` + +Sequence diagram illustrating the 5G-RG join IP Multicast Packets transmission procedure. The diagram shows interactions between 5G-RG, (R)AN, AMF, UPF, SMF, PGF, UDM, and IPTV Multicast Server. The steps are: 1. user plane data: IGMP/MLD Join message from 5G-RG to UPF; 2. Apply N4 rules from UPF to SMF; 2b. UPF Usage Report from UPF to SMF; 2c. PCRT Report from SMF to PGF; 3. Multicast packets transmission from IPTV Multicast Server to UPF; 4. Multicast packets transmission over PDU Session from UPF to 5G-RG. + +**Figure 7.7.1.1-3: 5G-RG join IP Multicast Packets transmission procedure** + +1. The 5G-RG sends an IGMP or MLD Join message via the IP PDU Session user plane. +2. When UPF receives the IGMP or MLD Join, the UPF may identify IGMP and MLD packets based on PDR received over N4 as described in clause 4.6 and handle the IGMP and MLD Join accordingly based on FAR as described in clause 4.6. An example is given as below: + - If the IP Multicast Addressing information included in the IGMP or MLD Join message is allowed to be accessed via the PDU Session, the UPF shall add the PDU Session to the requested multicast group. If requested by an URR, the UPF notifies the SMF that the UE is joining to a multicast group, providing the associated IP Multicast Addressing information. + - If the IP Multicast Addressing information included in the IGMP or MLD Join message is not allowed to be accessed via the PDU Session, the UPF shall not add the PDU Session to the requested multicast group. + +The UPF acts as a Multicast Router as defined in IETF RFC 2236 [33], IETF RFC 4604 [21] and IETF RFC 2710 [36]. This may include following actions: + +- if the IGMP or MLD Join message is the first IGMP or MLD request the UPF has received about the target IP multicast traffic: the UPF exchanges N6 signalling such as PIM (Protocol-Independent Multicast) in order to connect to the N6 multicast distribution tree related with this IP multicast traffic; This ensures that the UPF receives the DL multicast traffic. +- The IP multicast related signalling protocol used on N6 (e.g. Sparse Mode PIM-SM) to be supported over N6 is defined by local policies on the UPF. + +- 2b. if the SMF had set the corresponding URR Reporting trigger with a value "IP multicast join/leave" (as defined in clause 4.6.5), the UPF issues an UPF report to the SMF and the corresponding IP Multicast addressing information + - 2c. if the PCF had set the corresponding Policy Control Request Trigger set to "UE join to a multicast group" trigger" (as defined in clause 9.7), the SMF issues a SMF initiated SM Policy Association Modification (as defined in TS 23.502 [3] clause 4.16.5) reporting to the PCF the corresponding IP Multicast addressing information. +- 3-4. When the UPF receives IP multicast packets from multicast server in IPTV network, the UPF select the PDU Session(s) where to transmit the multicast packets based on the multicast group, constructed in step 2 and fulfilling the FAR and QER rules described in clause 7.7.1.1.1. + +NOTE 1: The interactions between STB and 5G-RG are specified in BBF TR-124 [5] and are not shown in figure 7.7.1.1-3. + +The 5G-RG may leave the IP Multicast Group as follows: + +- sending an unsolicited IGMP Leave or MLD Done message; +- IGMPv2 Leave message or a IGMPv3 Membership Report with indication of State Change Record or MLD Done message to request to leave a specific IP Multicast Group. The Message may be solicited by UPF via an IGMP MLD Query message. + +NOTE 2: The Membership Query is typically used in IPTV system to recover from error conditions such as when the Leave message has been dropped by intermediate node or when the STB has been powered off without being able to send a Leave Message. + +![Sequence diagram illustrating the 5G-RG leave IP Multicast Packets transmission procedure. The diagram shows interactions between 5G-RG, (R)AN, AMF, UPF, SMF, PCF, UDM, and IPTV Multicast Server. The 5G-RG sends IGMP/MLD messages to the UPF via the (R)AN. The UPF then sends reports to the SMF and PCF, and stops forwarding multicast packets.](007fefafb4fcbdb7d388209f63a0ba5d_img.jpg) + +``` + +sequenceDiagram + participant 5G-RG + participant (R)AN + participant AMF + participant UPF + participant SMF + participant PCF + participant UDM + participant IPTV Multicast Server + + Note left of 5G-RG: 1.a user plane data: IGMP/MLD Query message + 5G-RG->>(R)AN: 1.a user plane data: IGMP/MLD Query message + (R)AN-->>UPF: 1.a user plane data: IGMP/MLD Query message + Note left of 5G-RG: 1.b user plane data: IGMP/MLD Report message + 5G-RG->>(R)AN: 1.b user plane data: IGMP/MLD Report message + (R)AN-->>UPF: 1.b user plane data: IGMP/MLD Report message + Note left of 5G-RG: 1.c user plane data: IGMP/MLD Leave message + 5G-RG->>(R)AN: 1.c user plane data: IGMP/MLD Leave message + (R)AN-->>UPF: 1.c user plane data: IGMP/MLD Leave message + Note right of UPF: 2. Stop forwarding Multicast packets + UPF->>SMF: 3. UPF Usage Report + SMF->>PCF: 4. PCRT Report + +``` + +Sequence diagram illustrating the 5G-RG leave IP Multicast Packets transmission procedure. The diagram shows interactions between 5G-RG, (R)AN, AMF, UPF, SMF, PCF, UDM, and IPTV Multicast Server. The 5G-RG sends IGMP/MLD messages to the UPF via the (R)AN. The UPF then sends reports to the SMF and PCF, and stops forwarding multicast packets. + +Figure 7.7.1.1-4: 5G-RG leave IP Multicast Packets transmission procedure + +- 1a The UPF acting as a Multicast Router as defined in IETF RFC 2236 [33] and IETF RFC 3376 [28] may send an IGMP Query or an MLD Query message. + - 1b The 5G-RG may send a IGMP or MLD Membership Report message where the address of a IP Multicast Group is no more included in the list. This message may be the answer to the query in step 1a or it may be sent unsolicited. + - 1c The 5G-RG may send an IGMPv2 Leave message or a IGMPv3 Membership Report with indication of State Change Record or MLD Done message to request to leave a specific IP Multicast Group. +- 2 When UPF receives the IGMP or MLD message in step 1b or 1c the UPF may identify the IGMP and MLD packets based on PDR received over N4 as described in clause 4.6.3 and handle the IGMP and MLD message accordingly as below: +- If the IP Multicast Addressing information included in the IGMP or MLD Report message does not include the IP address(es) of a multicast group the UPF stop forwarding the packet to the 5G-RG. + - if the UPF receives an IGMP Leave or MLD Done message, the UPF stops forwarding multicast packets related to the IP multicast Group to the 5G-RG. + +The UPF acts as a Multicast Router as defined in IETF RFC 2236 [33], IETF RFC 4604 [21] and IETF RFC 2010 [37]. This may include following actions: + +- the UPF may exchange N6 signalling such as PIM (Protocol-Independent Multicast) in order to leave a IP multicast Group if no other 5G-RG are connected to the same IP multicast Group; This ensures that the UPF does no more receive the DL multicast traffic, if not needed. + - The IP multicast related signalling protocol used on N6 (e.g. Sparse Mode PIM-SM) to be supported over N6 is defined by local policies on the UPF. +3. if the SMF had set the corresponding URR Reporting trigger with a value "IP multicast join/leave" (as defined in clause 4.6.5), the UPF issues an UPF report to the SMF the corresponding IP Multicast addressing information + 4. if the PCF had set the corresponding Policy Control Request Trigger set to "UE join to a multicast group" trigger", the SMF issues a SMF initiated SM Policy Association Modification (as defined in TS 23.502 [3] clause 4.16.5) reporting to the PCF the corresponding IP Multicast addressing information. + +#### 7.7.1.1.4 AF request to provision Multicast Access Control List information into UDR + +![Sequence diagram showing the interaction between PCF(s), UDR, NEF, and AF for provisioning Multicast Access Control List information. The sequence starts with the AF sending a request to the NEF, which then interacts with the UDR to create/update/remove the AC list, and finally notifies the PCF(s).](6231ba981d3d1ab7ce0cae71abd08c17_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDR + participant PCF as PCF(s) + + Note right of AF: 1. Creation of the AF request + AF->>NEF: 2 Nnef_IPTV configuration information Create + Note over UDR: 3a. Create/Update/ +Remove the Multicast AC +list per UE or group of +UEs in UDR + NEF->>UDR: + Note over UDR: 3b. Nnef_IPTV configuration +information Create/Remove/Update + UDR->>NEF: Response + Note over NEF: + UDR-->>PCF: 4. Nudr_DM_Notify + +``` + +Sequence diagram showing the interaction between PCF(s), UDR, NEF, and AF for provisioning Multicast Access Control List information. The sequence starts with the AF sending a request to the NEF, which then interacts with the UDR to create/update/remove the AC list, and finally notifies the PCF(s). + +**Figure 7.7.1.1.4: AF request to provision Multicast Access Control List information into UDR** + +NOTE 1: The 5GC NFs used in this scenario are assumed to all belong to the same PLMN (HPLMN). + +1. To create a new request, the AF invokes an Nnef\_IPTV\_configuration service operation. The request contains the Multicast Access Control List, a GPSI or an External Group Id, AF Transaction Id, application identifier and may contain a DNN and/or a S-NSSAI. To update or remove an existing request, the AF invokes Nnef\_IPTV\_configuration\_Update or Nnef\_IPTV\_configuration\_Delete service operation providing the corresponding AF Transaction Id. +2. The AF sends its request to the NEF. The NEF ensures the necessary authorization control, including throttling of AF requests and, as described in clause 4.3.6.1 of TS 23.502 [3], mapping from the information provided by the AF into information needed by the 5GC. +3. (in the case of Nnef\_IPTV\_configuration\_Create or Update): The NEF stores the AF request information in the UDR (Data Set = Application Data; Data Subset = IPTV\_configuration, Data Key = AF Transaction Internal ID, S-NSSAI and DNN and/or SUPI/Internal-Group-Id). + +(in the case of Nnef\_IPTV\_configuration\_Delete): The NEF deletes the AF requirements in the UDR (Data Set = Application Data; Data Subset = IPTV\_configuration, Data Key = AF Transaction Internal ID). + +The NEF responds to the AF. + +4. The PCF(s) that have subscribed to modifications of AF requests (Data Set = Application Data; Data Subset = IPTV\_configuration, Data Key = SUPI/Internal-Group-Id) receive a Nudr\_DM\_Notify notification of data change from the UDR. +5. The PCF determines if existing PDU Sessions are potentially impacted by the AF request. For each of these PDU Sessions, the PCF updates the SMF with corresponding new PCC rule(s) by invoking Npcf\_SMPolicyControl\_UpdateNotify service operation as described in steps 5 and 6 in clause 4.16.5 of TS 23.502 [3]. + +Table 7.7.1.1.4-1 shows an example of a Multicast Access Control list provided by the AF in the IPTV domain to the NEF. The Multicast Access Control List defines the access right status (i.e. fully allowed, preview allowed, not allowed) of each of the Multicast channels per subscriber identified by a GPSI. + +**Table 7.7.1.1.4-1: Example of a Multicast Access Control list provided by the AF in the IPTV domain** + +| | IP Multicast Addressing information 1 (related to Channel 1) | IP Multicast Addressing information 2 (related to Channel 2) | IP Multicast Addressing information 3 (related to Channel 3) | +|--------|--------------------------------------------------------------|--------------------------------------------------------------|--------------------------------------------------------------| +| GPSI 1 | Fully allowed | Not allowed | Preview allowed | + +The NEF maps the GPSI into the SUPI, assigned to a 5G-RG, as described in step 2 in Figure 7.7.1.1.4-1. and stores the Multicast Access Control List in the UDR as shown in Table 7.7.1.1.4-2. + +**Table 7.7.1.1.4-2: Example of a Multicast Access Control list stored in UDR within the Application Data Set** + +| DataKey | IP Multicast Addressing information 1 (related to TV Channel 1) | IP Multicast Addressing information 2 (related to TV Channel 2) | IP Multicast Addressing information 3 (related to TV Channel 3) | +|------------------|-----------------------------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------| +| SUPI for 5G-RG 1 | Fully allowed | Not allowed | Preview allowed | +| SUPI for 5G-RG 2 | Fully allowed | Fully allowed | Not allowed | +| SUPI for 5G-RG 3 | Fully allowed | Preview allowed | Preview allowed | + +If source Specific Multicast is to be used for a TV Channel, IP Multicast Addressing information corresponds to IP Multicast address and Source IP address. + +The PCF is assumed to have subscribed to relevant modifications of that UDR data defined in the Table 7.7.1.1.4-2. + +## 8 Network Function services + +### 8.0 General + +This clause specifies the delta related to Network Function services description defined in TS 23.502 [3] clause 5.2. For 5G RG in FWA mode TS 23.502 [3] clause 5.2 applies. + +## 8.1 UDM Services + +### 8.1.1 Nudm\_SubscriberDataManagement (SDM) Service + +#### 8.1.1.1 General + +In addition to the Subscription data types used in the Nudm\_SubscriberDataManagement Service, as defined in Table 5.2.3.3.1-1 of TS 23.502 [3], the additional data types defined in Table 8.1.1.1-1 below are applicable for RGs connected to 5GC via W-5GAN and AUN3 devices . + +**Table 8.1.1.1-1: Wireline access specific UE Subscription data types** + +| Subscription data type | Field | Description | +|-------------------------------------------------------------------------------------------------|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Access and Mobility Subscription data (data needed for UE Registration and Mobility Management) | RG Level Wireline Access Characteristics | The RG level Wireline Access Characteristics parameter provides QoS information for the W-AGF, as defined in clause 4.5.1.2. This parameter is handled by the UDM as a transparent container. This parameter may also be provisioned in subscriptions for AUN3 devices. | +| | AUN3 device connectivity allowed. | Indicates whether the subscriber is allowed to access as an AUN3 device. Only provisioned in subscriptions for AUN3 devices. | + +In the case of Wireline access, the Forbidden area information within Table 5.2.3.3.1-1 of TS 23.502 [3] may correspond to a (set of) allowed Global Line ID. + +## 8.2 Void + +## 8.3 BSF Services + +### 8.3.1 General + +The Nbsf\_Management\_Register/Deregister and Discovery service operations defined in TS 23.502 [3] are extended to allow registration/deregistration and discovery of the binding information when one or multiple /128 IPv6 address or UE IPv6 prefix shorter than /64 is/are assigned to a PDU session. + +## 8.4 PCF Services + +### 8.4.1 General + +PCF services defined in TS 23.502 [3] apply with modifications described in this clause. + +### 8.4.2 Npcf\_SMPolicyControl + +The Npcf\_SMPolicyControl\_Create and Npcf\_SMPolicyControl\_Update, defined in TS 23.502 [3], are extended to be able to provide PCF with one or multiple allocated /128 IPv6 UE address or with UE IPv6 prefix shorter than /64. + +The Npcf\_SMPolicyControl\_Update, defined in TS 23.502 [3], is extended to be able to provide PCF with information on a released /128 IPv6 address or on a released UE IPv6 prefix shorter than /64. + +### 8.4.3 Npcf\_AMPolicyControl + +#### 8.4.3.1 Npcf\_AMPolicyControl\_Create service operation + +The input data listed in clause 5.2.5.2.2 in TS 23.502 [3] apply when an AM Policy Association is created for a 5G-RG, except for the handling of RFSP information that applies only if a 5G RG is registered over 3GPP access. + +The input information when the UE registers via W-5GAN includes the Access type set to non-3GPP access, the User Location Information including the GLI or the HFC node Id. + +The output information when the UE registers via W-5GAN is defined in clause 9.5 and the Policy Control Request triggers applicable for for RG access via W-5GAN are defined in clause 9.5.3. + +#### 8.4.3.2 Npcf\_AMPolicyControl\_Update service operation + +The input data listed in clause 5.2.5.2.5 in TS 23.502 [3] apply when an AM Policy Association is updated for a 5G-RG or for a FN-RG, except for the notification of UE location change (if an RG registers only on Wireline access), PRA changes or RFSP index change. + +PCRT on UE location change apply when a 5G RG registers on a second access (5G RG using Hybrid access). + +The output information when the UE registers via W-5GAN is defined in clause 9.5 and the Policy Control Request triggers applicable when RG accesses via W-5GAN are defined in clause 9.5.3. + +The Access type change trigger requests the AMF to report a new Access Type and RAT Type to the PCF. When the UE simultaneous connects over both 3GPP and wireline non-3GPP access type, the AMF reports the list of Access Type and RAT combinations available in the UE access and mobility context in the Npcf\_AMPolicyControl\_Update service operation. + +## 8.5 Nnef\_IPTVconfiguration service + +### 8.5.1 General + +**Service description:** This service provides: + +- Request authorization of NF Service Consumer requests. +- Request parameter mapping from NF Service Consumer requests to 5GC parameters and vice versa as described in clause 7.7.1.1.x +- NF Service Consumer request configuration of Multicast Access control list as described in clause 7.7.1.1.4. + +### 8.5.2 Nnef\_IPTVconfiguration\_Create operation + +**Service operation name:** Nnef\_IPTVconfiguration\_Create + +**Description:** Authorize the request and forward the request for IPTV configuration information. + +**Inputs (required):** AF Transaction Id, GPSI or External-Group-ID, application identifier, Multicast Access Control List. + +The AF Transaction Id refers to the request. + +**Inputs (optional):** DNN, S-NSSAI. + +**Outputs (required):** Operation execution result indication. + +**Outputs (optional):** None. + +### 8.5.3 Nnef\_IPTVconfiguration\_Update operation + +**Service operation name:** Nnef\_IPTVconfiguration\_Update + +**Description:** Authorize the request and forward the request to update IPTV configuration information. + +**Inputs (required):** AF Transaction Id. + +The AF Transaction Id identifies the NF Service Consumer request to be updated. + +**Inputs (optional):** Multicast Access Control List. + +**Outputs (required):** Operation execution result indication. + +**Outputs (optional):** None. + +### 8.5.4 Nnef\_IPTVconfiguration\_Delete operation + +**Service operation name:** Nnef\_IPTVconfiguration\_Delete + +**Description:** Authorize the request and forward the request to delete(s) request for IPTV configuration information. + +**Inputs (required):** AF Transaction Id. + +The AF Transaction Id identifies the NF Service Consumer request for IPTV configuration to be deleted. + +**Inputs (optional):** None. + +**Outputs (required):** Operation execution result indication. + +**Outputs (optional):** None. + +## 8.6 UDR Services + +### 8.6.1 Nudr\_DataManagement (DM) Service + +#### 8.6.1.1 General + +The UDM makes use of the Nudr\_DM service to perform the mapping of the SUPI/IMSI associated with the Line ID or HFC-Identifier included in the SUCI. + +In addition to the Subscription data types and corresponding Subscription Data keys used in the Nudr\_DM\_Service, as defined in TS 23.502 [3], the Subscription data types and corresponding Subscription data keys defined for the Nudr\_DM Service in Table 8.6.1.1-1 and Table 8.6.1.1-2 are applicable for FN-RGs connected to 5GC. + +**Table 8.6.1.1-1: UE Subscription data types** + +| Subscription data type | Field | Description | +|-------------------------------------|--------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| +| Subscription identifier translation | Other Identifier Of The Subscription (Global Line ID or Global Cable ID) | Global Line ID or Global Cable ID included in SUCI provided by the W-AGF to the 5GC for FN-RG support and used as pseudonym of the SUPI. | +| | SUPI | Corresponding SUPI | + +**Table 8.6.1.1-2: Data keys** + +| Data Set | Data Subset | Data Key | Data Sub Key | +|-------------------|-------------------------------------|-----------------------------------|--------------| +| Subscription Data | Subscription identifier translation | Global Line ID or Global Cable ID | - | + +## 9 Policy and Charging Control Framework and Configuration by ACS + +### 9.0 General + +This clause specifies the delta related to Policy and charging control framework defined in TS 23.503 [4] and the configuration of the 5G-RG by the ACS. + +### 9.1 Session management related policy control + +#### 9.1.0 General + +This clause specifies the delta related to UE policy distribution defined in TS 23.503 [4] clause 6.1.3 for 5G-RG and FN-RG. + +#### 9.1.1 Session binding + +The session binding mechanism defined in TS 23.503 [4] clause 6.1.3.2.2 applies. In addition, the PDU session parameters considered for session binding are: + +- For IPv6 PDU session type, one or multiple UE IPv6 address or one or multiple IPv6 prefixes /64 or shorter prefixes. +- For IPv4v6 PDU session type, one UE IPv4 address and one or multiple IPv6 prefixes /64 or shorter prefixes. + +#### 9.1.2 Policy Control Request Triggers relevant for SMF and wireline access type + +The Policy Control Request Triggers relevant for SMF and wireline access define the conditions when the SMF shall interact again with PCF after a PDU Session established via W-5GAN. PCR triggers defined in Table 6.1.3.5 in TS 23.503 [4] are supported for W-5GAN scenario with the following not supporting ones: + +- PLMN change. +- Location change (serving area). +- Location change (serving CN node in 5GS). +- Location change (serving CN node in EPC). +- Change of UE presence in Presence Reporting Area. +- 3GPP PS Data Off status change. +- GFBR of the QoS Flow can no longer (or can again) be guaranteed. +- UE resumed from suspend data. +- Manageable Ethernet Port detected. +- Port Management Information Container available. + +Additionally, the new triggers defined in clause 9.7 for IPTV service are also applied for a 5G-RG connected via W-5GAN scenario. + +## 9.2 Network Functions and entities + +### 9.2.1 General + +This clause specifies the delta related to Network Function and entities defined in TS 23.503 [4] clause 6.2 for 5G-RG and FN-RG. + +The functional description of the NEF, NWDAF, UDR and CHF applies as described in TS 23.503 [4]. + +### 9.2.2 Policy Control Function (PCF) + +The PCF provides session management policy control for single access PDU sessions over non 3GPP wireline and multiaccess PDU sessions over both 3GPP and non 3GPP wireline access. + +The session management related functionality defined in clause 6.2.1 of TS 23.503 [4] applies for 5G-RG and FN-RG, with the following modifications for W-5GAN: + +- Determination of Maximum Packet Loss Rate for UL/DL does not apply. +- QoS Notification Control does not apply. + +NOTE: No requirements to support MPS or Mission Critical Services over wireline non 3GPP access are defined in this Release. + +The non-session management related functionality defined in clause 6.2.2 of TS 23.503 [4] applies for 5G-RG and FN-RG, with the following modifications for W-5GAN: + +- the UE-AMBR control by the Visited Network does not apply. +- the Service Area Restrictions for a FN-BRG does not apply. +- the 5G-RG and FN-RG replaces the UE. +- the PCF provides Access and mobility related policy control as described in clause 9.5.1. +- the PCF provides UE access selection and PDU session selection +- the PCF provides the UE access selection and PDU Session selection related policy control as defined in clause 9.5.2. + +The policy control subscription data defined in TS 23.503 [4] applies for 5G-RG and FN-RG connected via W-5GAN access, except for the definition of MPS data for a 5G-RG or FN-RG that is not applicable in this Release. + +The policy control subscription data defined in TS 23.503 [4] applies for a 5G-RG and FN-RG connected via W-5GAN, except for the definition of MPS data for a 5G-RG or FN-RG that is not applicable in this Release. + +The V-PCF and H-PCF functionality does not apply for session and non-session policy control for 5G-RG and FN-RG users in this Release. + +### 9.2.3 Session Management Function (SMF) + +The SMF enforces policy decisions related to service data flow detection, authorized QoS, charging, gating, traffic usage reporting, packet routing and forwarding and traffic steering for single access PDU session over W-5GAN and multiaccess PDU sessions over W-5GAN and 3GPP as defined in clause 6.2.2 of TS 23.503 [4] with the following modifications for W-5GAN: + +- Reporting RAN/NAS Release Cause over wireline is not supported. +- The Maximum Packet Loss Rate for UL and DL is not forwarded to the wireline non-3GPP access. + +## 9.2.4 Application Function (AF) + +The AF requests for policy control functionality described in clause 6.2.3 of TS 23.503 [4] applies with the following clarification for W-5GAN: + +- Indication that the QoS targets can no longer (or can again) be fulfilled is not supported. + +NOTE: No requirements to support MPS or Mission Critical Services over wireline non 3GPP access are defined in this release. + +## 9.2.5 Access and Mobility Management Function (AMF) + +The policy control related functionality defined in TS 23.503 [4] applies, with the clarification that the UE-AMBR control by the visited network is only applicable for a 5G-RG registered over 3GPP access. + +# 9.3 Policy and charging control rule + +Policy and charging control rule for 5G-RG PDU Session is described in TS 23.503 [4] clause 6.3 with the clarification and difference in this clause. + +## 9.3.1 PCC rule information to support IPTV service + +- PCF shall take Multicast Access Control list described in clause 7.7.1.1.4 as input to policy decision in the case of PDU Session used for IPTV service. PCC rules sent to SMF may indicate allowed IP Multicast Addressing information as defined in Table 9.3.1-1. +- The "Gate status" is not applicable to IGMP transmitted over PDU Session used for IPTV service. + +Comparing to Table 6.3.1 in TS 23.503 [4], additional PCC rule information for PDU Session used for IPTV service is described in Table 9.3.1-1. + +**Table 9.3.1-1: The additional PCC rule information for PDU Session used for IPTV service** + +| Information name | Description | Category | PCF permitted to modify for a dynamic PCC rule in the SMF | Differences compared with table 6.3. in TS 23.203 [31] | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------|-----------------------------------------------------------|--------------------------------------------------------| +| IPTV | This part defines the additional PCC rule information for PDU Session used for IPTV service. | | | | +| IP Multicast traffic control information | indicates whether the service data flow, corresponding to the service data flow template, may be allowed or not allowed (NOTE 1). | Optional | Yes | Added | +| NOTE 1: The corresponding IP Multicast Addressing information is provided in the SDF template. The SDF template may refer to "any" IP Multicast address (for example allowing the user to access to receive any IPTV channel). | | | | | + +## 9.4 PDU Session related policy information + +This clause specifies the delta related to PDU session related policy information defined in TS 23.503 [4] clause 6.4 for 5G-RG and FN-RG. + +## 9.5 Non-session management related policy information + +### 9.5.1 Access and mobility related policy information + +This clause specifies the delta related to Access and Mobility related policy information defined in TS 23.503 [4] clause 6.1.2.1 for 5G-RG and FN-RG. + +The access and mobility policy control encompass the management of service area restrictions for a 5G-BRG or a 5G-CRG connecting to 5GC via W-5GAN or simultaneously via NG-RAN and W-5GAN as well as AUN3 devices behind a 5G-RG. + +The management of service area restrictions enables the PCF of the serving PLMN or SNPN to modify the service area restrictions based on operator defined policies at any time, either by expanding a list of allowed GLIs or HFC Node IDs or by reducing the list of non-allowed GLIs or HFC Node IDs. Operator defined policies in the PCF may depend on input data such as time of day, or UE context information provided by other NFs, etc. + +The AMF reports the subscribed service area restrictions in NG-RAN received from UDM during 5G-RG Registration in NG-RAN procedure when local policies in the AMF indicate that Access and Mobility Control is enable within the PLMN or SNPN. The AMF may request update of the service area restrictions applicable to NG-RAN when the policy control request triggers listed in clause 6.1.2.5 in TS 23.503 [4], are met. + +The AMF reports the subscribed service area restrictions in W-5GAN received from UDM during 5G-RG or AUN3 device Registration in W-5GAN procedure when local policies in the AMF indicate that Access and Mobility Control is enable within the PLMN or SNPN. The AMF may request update of the service area restrictions applicable to W-5GAN when the policy control request triggers listed in clause 9.5.3 are met. + +The AMF receives the modified service area restrictions from the PCF and then use them as described in clause 4.3.3.3. + +No mobility events, such a change of UE location or change of AMF applies when provisioning the service area restrictions for a 5G-BRG or a 5G-CRG or AUN3 device when connected via W-5GAN. + +The PCF may provide the service area restrictions applicable to a 5G-RG connected to 5GC via W-5GAN or via NG-RAN or simultaneously connected to 5GC via W-5GAN and NG-RAN to AMF. The PCF may provide the service area restrictions applicable to a FN-CRG to the AMF. The PCF may provide the service area restrictions applicable to an AUN3 device behind 5G-RG connected to 5GC via W-5GAN to the AMF. + +The Service Area Restrictions provided to AMF for a 5G-RG connected via NG-RAN is according to the information listed in listed in TS 23.503 [4] clause 6.5. + +The Service Area Restrictions provided to AMF for a 5G-RG or AUN3 device connected via W-5GAN is according to the information listed in Table 9.5-1. + +For a 5G-RG simultaneously connected to 5GC via W-5GAN and NG-RAN the PCF provides Service Area Restrictions for both W-5GAN and NG-RAN. + +The Service Area Restrictions provided to AMF for a FN-CRG connected via W-5GAN is according to the information listed in Table 9.5-1. + +**Table 9.5-1: Access and mobility related policy control information for 5G-RG and FN-CRG accessing via W-5GAN** + +| Information name | Description | Category | PCF permitted to modify in a AM context in the AMF | Scope | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------|----------------------------------------------------|------------| +| Service Area Restrictions for a 5G-BRG or AUN3 device behind 5G-BRG | This part defines the service area restrictions applicable for a 5G-BRG or AUN3 device behind 5G-BRG. | | | | +| List of allowed GLIs | List of allowed GLIs (NOTE 2). | Conditional (NOTE 1) | Yes | AM context | +| List of non-allowed GLIs | List of non-allowed GLIs. | Conditional (NOTE 1) | Yes | AM context | +| Service Area Restrictions for a 5G-CRG or for a FN-CRG | This part defines the service area restrictions applicable for a 5G-CRG or for a FN-CRG | | | | +| List of allowed HFC Node IDs | List of allowed HFC Node IDs (NOTE 2) | Conditional (NOTE 1) | Yes | AM context | +| List of non-allowed HFC Node IDs | List of non-allowed HFC Node IDs (NOTE 2). | Conditional (NOTE 1) | Yes | AM context | +| Service Area Restrictions for an AUN3 device behind 5G-CRG | This part defines the service area restrictions applicable for an AUN3 device behind 5G-CRG | Conditional (NOTE 1) | Yes | AM context | +| List of allowed combinations of GCI and HFC Node IDs | List of allowed combinations of GCI and HFC Node ID (NOTE 3) | Conditional (NOTE 1) | Yes | AM context | +| NOTE 1: If service area restrictions is enable.
NOTE 2: Either the list of allowed (GLIs or HFC Node IDs) or the list of non-allowed (GLIs or HFC Node IDs) are provided by the PCF.
NOTE 3: Either the list of allowed (GCI and HFC Node ID combinations) or the list of non-allowed (GCI or HFC Node ID combinations) are provided by the PCF. | | | | | + +The *list of allowed GLIs or the list of allowed HFC Node IDs* indicates the locations where the 5G-RG is allowed to be registered, see clause 4.3.3.3 for the description on how AMF uses this information. + +## 9.5.2 UE access selection and PDU Session selection related policy information + +### 9.5.2.1 5G-RG + +This clause specifies the delta related to UE policy distribution defined in TS 23.503 [4] clause 6.1.2.2 and related to URSP defined in TS 23.503 [4] clause 6.6. for 5G-RG. + +If the PCF provides the URSP policy to the 5G-RG, the PCF should neither include NSWO indication nor any ANDSP policies. The 5G-RG shall ignore any NSWO indication or any ANDSP policies if received from the 5GC. The 5G-RG shall use the URSP policy as specified in TS 23.503 [4], for example for the association of application and PDU session, slices, etc. + +The URSP indicates for the application of Auto-Configuration Server (ACS) which PDU session type, NSSAI and/or DNN is to be used. The 5G-RG establishes the connectivity to the management entity (e.g. ACS) via user plane connection on a PDU session according to the URSP. + +UE Policy procedures defined in clause 6.1.2.2 of TS 23.503 [4] are applicable as follows: + +- Roaming is not applicable to W-5GAN access in this release of specification. + +In order to support the case when AUN3 devices may be connected via 5G-RG, specific URSP rules may be configured by the PCF for the SUPI associated with the AUN3 device. + +UE Route Selection Policy information targeting an AUN3 device (i.e. sent to a 5G-RG in the NAS connection corresponding to an AUN3 device) follows the structure defined in clause 6.2.2 of TS 23.503 [4] with following differences: + +- As an AUN3 can have only one PDU Session, its URSP shall contain a match all TD. + +In order to support the case when NAUN3 devices may be connected via 5G-RG, specific URSP rules may be configured by the PCF on 5G-RG. + +URSP rules for NAUN3 devices connected to 5G-RG follow the structure defined in clause 6.6.2 of TS 23.503 [4] and may contain any combination of the following traffic descriptors: + +- **IP Descriptors:** For IP traffic from NAUN3 devices connected to 5G-RG, IP descriptors are matched against header information contained in IP packets sent by NAUN3 devices; IP descriptors are only applicable for traffic from NAUN3 devices if network address translation (NAT) is performed for that traffic. +- **Non-IP descriptors:** For Ethernet traffic from NAUN3 devices connected to 5G-RG, Non-IP descriptors are matched against header information contained in Ethernet frames sent by NAUN3 devices. +- **Connectivity Group ID:** For traffic from a NAUN3 device connected to 5G-RG, Connectivity Group ID in the URSP rule is matched against the Connectivity Group ID that the NAUN3 device is associated with (see clause 4.10b). + +## 9.5.2.2 FN-RG + +This clause specifies the delta related to UE policy distribution defined in TS 23.503 [4] clause 6.1.2.2 and related to URSP defined in TS 23.503 [4] clause 6.6 for 5G-RG. + +If the PCF provides the URSP rules related to FN-RG to the W-AGF, the PCF should not include NSWO indication. The PCF should not provide ANDSP policies. The W-AGF shall ignore any NSWO indication or any ANDSP policies if received from the 5GC. + +The W-AGF shall use the URSP policy as specified in TS 23.503 [4] with the following modifications: + +- Traffic descriptor; +- the Application Descriptor is not applicable; +- the DNN is not applicable; +- The Connection Capabilities Descriptor is not applicable. + +NOTE 1: The FN-RG initiates the W-5GAN session with the W-AGF, for example PPPoE, and consequently the W-AGF does not receive any indication of the application used for that session (e.g. whether it used for web browsing or for any specific application) and any DNN indication from the application, hence the policy including the Application Descriptors and/or DNN will never match the traffic. + +If the PCF sends UE policy (e.g. URSP), the W-AGF shall store it for the duration that FN-RG is registered. When the FN-RG is deregistered, the UE policy can be removed. Whether it is done immediately, or after a certain period (e.g. for quick recovery from disconnection or fault), or stored permanently it is left to implementation and is out of the scope of this TS. + +If the URSP for the FN-RG are present in W-AGF (e.g. pre-configured or received from PCF) the W-AGF shall use them as defined for a UE with URSP. + +If the URSP for the FN-RG are not present in W-AGF, the W-AGF acts based on local configuration, as defined for a UE without URSP. + +It is assumed that the FN-RG configuration (provided via BBF TR-069 [18]/BBF TR-369 [19]), the URSP rules and the local configuration in the W-AGF are consistent with each other. If the W-AGF detects conflicting requirements based on URSP, local configuration, or requests from the FN-RG, then the URSP rules takes precedence since they are considered the most updated and aligned to the current 5G system conditions. + +UE Policy procedures defined in clause 6.1.2.2 of TS 23.503 [4] are applicable with the following modification: + +- Roaming is not applicable to W-5GAN access in this release of specification. + +### 9.5.3 Policy Control Request Triggers relevant for AMF and wireline access type + +The Policy Control Request Triggers relevant for AMF and wireline access type define the conditions when the AMF shall interact again with PCF after the AM Policy Association. PCR triggers defined in Table 6.1.2.5 in TS 23.503 [4] are supported for W-5GAN scenario with the following not supporting ones: + +- Location change (tracking area). +- Change of UE presence in Presence Reporting Area. +- RFSP index change. +- UE-AMBR change. +- PLMN change. + +Additionally, the following PCR triggers are added regarding the wireline access type: + +**Table 9.5.3-1: Policy Control Request Triggers relevant for AMF and wireline access type** + +| Policy Control Request Trigger | Description | Condition for reporting | +|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|-------------------------| +| Access Type change (NOTE 1) | The Access Type and the RAT Type has changed | PCF (AM Policy) | +| NOTE 1: The RAT type is reported for 3GPP access, or when the 5G-RG or FN-RG registers over wireline access (i.e. W-AGF). | | | + +The UE Policy related PCR triggers like location change, PRA change and PLMN change are not applicable for wireline access. + +## 9.6 Configuration and Management from ACS + +### 9.6.1 General + +Once the 5G-RG connects to 5GC, the 5G-RG shall establish a PDU session for interaction with the ACS to support the functionalities as described in BBF TR-069 [18] or in BBF TR-369 [19]. + +NOTE: Whether and how to use the objects received from the ACS by RG is out of 3GPP scope. + +### 9.6.2 ACS Discovery + +The ACS information may be associated to the RG subscription in the UDM / UDR. In this case the ACS information may be provided to the RG with at least one of the following methods: + +- via DHCP interaction if the RG sends DHCP signalling indicating a request for ACS information. The RG sends a DHCPv4 request including a request for ACS information and receives ACS information from the DHCP as specified in BBF TR-069 [18] clause 3.1 for ACS Discovery or in BBF TR-369 [19] R-DIS.1 and R-DIS.2. +- during the PDU session establishment procedure via PCO (protocol Configuration Option) sent in N1 SM message if the 5G-RG has asked to be provided with ACS information via PCO. This applies for 5G-RG only. + +The ACS information (e.g. URL of the ACS) is defined in BBF TR-069 [18] or in BBF TR-369 [19]. + +If the RG performs ACS discovery via DHCP process and the SMF is not the DHCP server (e.g. in the case of Ethernet PDU session), the ACS URL is provided by the external DHCP server. In this case, the whole process is transparent to the 5GC and the 5GC is not aware of the ACS information. If the RG performs ACS discovery via DHCP process and + +the SMF is the DHCP server the ACS information is provided by SMF as part of DHCP process and the SMF shall support the DHCP procedure defined in BBF TR-069 [18] Amendment 6 clause 3.2 or in USP (BBF TR-369 [19]). + +If the SMF is to provide ACS information to the RG (via PCO or DHCP), it gets this ACS information from SMF subscription data. + +The request of ACS information via PCO or via DHCP are mutually exclusive. + +The RG may be pre-configured with an ACS information. + +The 5G-RG shall consider the ACS information received with the following descending priority order: + +- 1) ACS information received during the DHCP process. +- 2) ACS information received during the PDU session establishment procedure from SMF PCO. This applies for 5G-RG only. +- 3) The pre-configured ACS information in the RG. + +### 9.6.3 ACS Information Configuration by the 3rd party + +The ACS information may be configured by a 3rd party AF to the 5GC per subscriber when the SMF is to provide ACS information to the RG. Subsequently, the ACS discovery via PCO or via DHCP with the DHCP server in the SMF may apply as described in clause 9.6.2. + +![Sequence diagram illustrating the ACS information configuration procedure. The diagram shows four participants: UDR, UDM, NEF, and AF. The sequence of messages is: 1. AF sends Nnef_ParameterProvision_Update request (ACS configuration) to NEF; 2. NEF sends Nudm_ParameterProvision_Update request (ACS configuration) to UDM; 3. UDM sends Nudr_DM_Update (ACS configuration) to UDR; 4. UDM sends Nudm_ParameterProvision_Update response to NEF; 5. NEF sends Nnef_ParameterProvision_Update response to AF.](91e400bc8bab58306b4d18432e94c9de_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDM + participant UDR + Note right of AF: 1. Nnef_ParameterProvision_Update request (ACS configuration) + AF->>NEF: 1. Nnef_ParameterProvision_Update request (ACS configuration) + Note right of NEF: 2. Nudm_ParameterProvision_Update request (ACS configuration) + NEF->>UDM: 2. Nudm_ParameterProvision_Update request (ACS configuration) + Note right of UDM: 3. Nudr_DM_Update (ACS configuration) + UDM->>UDR: 3. Nudr_DM_Update (ACS configuration) + Note right of UDM: 4. Nudm_ParameterProvision_Update response + UDM->>NEF: 4. Nudm_ParameterProvision_Update response + Note right of NEF: 5. Nnef_ParameterProvision_Update response + NEF->>AF: 5. Nnef_ParameterProvision_Update response + +``` + +Sequence diagram illustrating the ACS information configuration procedure. The diagram shows four participants: UDR, UDM, NEF, and AF. The sequence of messages is: 1. AF sends Nnef\_ParameterProvision\_Update request (ACS configuration) to NEF; 2. NEF sends Nudm\_ParameterProvision\_Update request (ACS configuration) to UDM; 3. UDM sends Nudr\_DM\_Update (ACS configuration) to UDR; 4. UDM sends Nudm\_ParameterProvision\_Update response to NEF; 5. NEF sends Nnef\_ParameterProvision\_Update response to AF. + +Figure 9.6.3-1: ACS information configuration procedure + +The ACS information configuration procedure enables the 3rd party AF to configure the ACS information (e.g. URL or IP address) to the 5GC. + +1. The 3rd party AF provides the ACS information, in the Nnef\_ParameterProvision\_Update Request to the NEF as in step 1 of TS 23.502 [3] figure 4.15.6.2-1. +2. As in step 2 of TS 23.502 [3] figure 4.15.6.2-1 where the provisioned data is the ACS information. +3. As in steps 3 and 4 of TS 23.502 [3] figure 4.15.6.2-1 where the provisioned data is the ACS information. +4. As in step 5 of TS 23.502 [3] figure 4.15.6.2-1. +5. As in step 6 of TS 23.502 [3] figure 4.15.6.2-1. +6. As in step 6 of TS 23.502 [3] figure 4.15.6.2-1 in order to update SMF with ACS information. + +## 9.6.4 URSP for FN RG + +A W-AGF needs to be able to determine the (DNN, S-NSSAI) parameters of the PDU Sessions it requests on behalf of a FN RG. The W-AGF requests such PDU Sessions upon data trigger (e.g. PPPoE, DHCP, etc.) received over a data path identified by a VLAN and a GLI; this is defined in BBF specifications (BBF TR-456 [9] and BBF TR-470 [38]). + +Thus the W-AGF needs to be configured to request different PDU Sessions for different VLAN(s) terminated at different FN RG(s). + +NOTE 1: The VLAN configuration depends on the served FN RG as a W-AGF service area can serve different Wireline access networks with different VLAN configurations. + +The corresponding W-AGF configuration about parameters of the PDU Sessions to request for a GLI corresponds to URSP that the W-AGF receives from the PCF for a SUPI corresponding to a GLI. + +The URSP(s) may be used to map VLAN(s) at transport level (S-tags as defined in BBF TR-470 [38]) on the V interface of the W-AGF (identifying the target service of the corresponding data flows, e.g. internet / IMS Voice / IPTV) towards Route Selection components including PDU Session type, DNN, S-NSSAI, SSC mode, etc. + +NOTE 2: UDR policy data related with a FN-RG subscription (UE Policy Section, see clause 5.4.2.3 of TS 29.519 [39]) can be configured accordingly. + +## 9.7 new PCRT (Policy Control Request Trigger) + +The Policy Control Request Triggers relevant for SMF are described in TS 23.503 [4] clause 6.1.3.5 with the clarification and difference shown in this clause. + +Table 9.7-1 + +| Policy Control Request Trigger | Description | Difference compared with table 6.2 and table A.4.3-2 in TS 23.203 [31] | Conditions for reporting | Motivation | +|-----------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|------------------------------------------------------------------------|--------------------------|--------------------------------------------| +| 5G-RG join to a multicast group | The 5G-RG has joined to an IP Multicast Group (NOTE 1). | New | PCF | To support IPTV as defined in clause 7.7.1 | +| 5G-RG Leave to a multicast group | The 5G-RG has left an IP Multicast Group (NOTE 1). | New | PCF | To support IPTV as defined in clause 7.7.1 | +| NOTE 1: When the SMF reports this condition it indicates the corresponding IP multicast Addressing information. | | | | | + +NOTE: The corresponding notification can be used by the PCF to manage Preview Rights related with an IP multicast flow corresponding to an IPTV channel. In this case the PCF is responsible to remove the 5G RG authorization to receive an IP multicast flow when the preview duration has elapsed. + +## 9.8 AF-based service parameter provisioning for TNAP ID + +To support location dependent policies when a UE connects using trusted non-3GPP access procedures via a TNAP collocated with a 5G-RG, as described in Figure 4.10-1, an AF may provide one or more TNAP IDs for a UE. A TNAP IDs provided by an AF refers to a TNAP that is collocated with a 5G-RG. + +The guidance provided by the AF is sent to the HPLMN of the UE and may apply to a single UE identified by GPSI. The request cannot be sent with Any UE or a group of UE as a target. + +For TNAP service parameter provisioning (i.e., creating, updating and deleting), the Nnef\_ServiceParameter service defined in clause 4.15.6.7 of TS 23.502 [3] is performed with the following modification: + +- Service Description contains an AF service Identifier indicating that the request is for providing TNAP information. +- The GPSI of the target UE is provided. + +- Service Parameters include TNAP ID(s). + +The PCF may compare the TNAP ID provided by the AF with the TNAP ID received in the User Location Information when the UE connects via trusted non-3GPP access. The PCF may apply different policies depending on whether UE is at the TNAP/RG indicated by the AF or not. In case the PCF has both subscribed TNAP ID and AF-provided TNAP ID, the PCF decides based on configuration whether to apply both or one of them. + +## 9.9 Policy control subscription information management + +This clause specifies the delta related to policy control subscription information defined in clause 6.2.1.3 of TS 23.503 [4] for 5G-RG and FN-RG. + +To support that the PCF of a PDU Session may, as described in clause 4.10, take the TNAP ID into account in policy decisions when the UE connects via trusted non-3GPP access over wireline access, following information may be supported in PDU Session policy control subscription information for the UE that is defined in Table 6.2-2 of TS 23.503 [4]: + +**Table 9.9-1: Extract of Table 6.2-2 of TS 23.503 [4]** + +| Information name | Description | Category | +|--------------------|--------------------------------------------------------------------------------------|----------| +| List of TNAP ID(s) | The list of identifiers of TNAP collocated with 5G-RG associated with the subscriber | Optional | + +--- + +## 10 Support of additional functionalities + +### 10.0 General + +This clause specifies the delta related to the Rel-16 additional specifications included in TS 23.273 [29] (LCS). + +### 10.1 User Location Information + +The User Location Information may correspond to: + +- In the case of W-5GCAN: TAI and HFC node ID. + +NOTE 1: HFC node ID identifies the point of attachment of the 5G-CRG. + +- In the case of W-5GBAN: TAI and GLI. The GLI contains an identifier of the Line ID source and the Line ID value. + +NOTE 2: A combination of Line ID and identifier of the Line ID source identifies the attachment point of the 5G-BRG. + +An indication of whether the ULI corresponds to a DSL or to a PON line may also be provided. + +- In the case of 5G-RG connected via 3GPP access: TAI and Cell Information (as described in TS 23.502 [3] clause 4.10 and TS 23.401 [24] clause 5.9.1). + +## Annex A (informative): UE behind RG using untrusted Non-3GPP access procedures + +This Annex describes how untrusted Non-3GPP access to 5GC can be provided to a UE via a 5G-RG and FN-RG connected to 5GC. + +![Figure A-1: Non-roaming architecture for UE behind 5G-RG using untrusted N3GPP access. The diagram shows a UE connected to a 5G-RG. The 5G-RG is connected to an NG-RAN (via N1) and a W-5GAN (via N2). The NG-RAN is connected to an AMF (via N2). The AMF is connected to an SMF (via N11) and a UPF (via N4). The W-5GAN is connected to the AMF (via N1) and the UPF (via N3). The UPF is connected to an N3IWF (via N6). The N3IWF is connected to an AMF (via N1) and an SMF (via N11). The SMF is connected to a DNN for UE (via N6).](dcf83796ccf494110638fbd4677b931d_img.jpg) + +Figure A-1: Non-roaming architecture for UE behind 5G-RG using untrusted N3GPP access. The diagram shows a UE connected to a 5G-RG. The 5G-RG is connected to an NG-RAN (via N1) and a W-5GAN (via N2). The NG-RAN is connected to an AMF (via N2). The AMF is connected to an SMF (via N11) and a UPF (via N4). The W-5GAN is connected to the AMF (via N1) and the UPF (via N3). The UPF is connected to an N3IWF (via N6). The N3IWF is connected to an AMF (via N1) and an SMF (via N11). The SMF is connected to a DNN for UE (via N6). + +**Figure A-1: Non-roaming architecture for UE behind 5G-RG using untrusted N3GPP access** + +The 5G-RG can be connected to 5GC via W-5GAN, NG-RAN or via both accesses. The UE can be connected to 5GC via untrusted non-3GPP access (via 5G-RG), NG-RAN or via both accesses. + +NOTE 1: The reference architecture in figure A-1 only shows the architecture and the network functions directly connected to W-5GAN or N3IWF, and other parts of the architecture are the same as defined in TS 23.501 [2] clause 4.2. + +NOTE 2: The reference architecture in figure A-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. + +NOTE 3: The two N2 instances in Figure A-1 apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and Wireline 5G Access Network. + +NOTE 4: The UE can as well be registered and connected via 3GPP access. + +![Figure A-2: Non-roaming architecture for UE behind FN-RG using untrusted N3GPP access. The diagram shows a UE connected to an FN-RG. The FN-RG is connected to a W-5GAN (via N2). The W-5GAN is connected to an AMF (via N1) and a UPF (via N3). The AMF is connected to an SMF (via N11). The UPF is connected to an N3IWF (via N6). The N3IWF is connected to an AMF (via N1) and an SMF (via N11). The SMF is connected to a DNN for UE (via N6).](4caed5b90277a5c5ee07547bfc8ff884_img.jpg) + +Figure A-2: Non-roaming architecture for UE behind FN-RG using untrusted N3GPP access. The diagram shows a UE connected to an FN-RG. The FN-RG is connected to a W-5GAN (via N2). The W-5GAN is connected to an AMF (via N1) and a UPF (via N3). The AMF is connected to an SMF (via N11). The UPF is connected to an N3IWF (via N6). The N3IWF is connected to an AMF (via N1) and an SMF (via N11). The SMF is connected to a DNN for UE (via N6). + +**Figure A-2: Non-roaming architecture for UE behind FN-RG using untrusted N3GPP access** + +The FN-RG can be connected to 5GC via W-5GAN. The UE can be connected to 5GC via untrusted non-3GPP access (via FN-RG), NG-RAN or via both accesses. + +NOTE 5: The reference architecture in figure A-2 only shows the architecture and the network functions directly connected to Wireline 5G Access Network or N3IWF, and other parts of the architecture are the same as defined in clause 4.2 of TS 23.501 [2]. + +NOTE 6: The reference architecture in figure A-2 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. + +NOTE 7: For untrusted non-3GPP access, UE connects to the overlay 5G network using the untrusted non-3GPP access approach as illustrated above. + +--- + +## Annex B (informative): Support for differentiated charging and QoS for UEs behind RG + +For the traffic of UEs behind a RG, QoS differentiation in the RG's PDU Session can be provided on a per UE's IPsec Child Security Association basis. The UE's N3IWF/TNGF determines the IPsec child SAs as defined in clauses 4.12 and 4.12a of TS 23.502 [3] as well as the DSCP value used in the outer IP header of that IPsec child SA. It is assumed that the same set of DSCP values and corresponding QoS are applicable independent of whether UE-requested or network-initiated QoS is used. + +To support QoS differentiation for the UE's traffic, QoS mapping rules between the RG's 5GC and the UE's 5GC are governed by an SLA (or network configuration in case of single operator), which includes the mapping between the DSCP marking for the IPsec child SAs and the corresponding QoS parameters and also the N3IWF/TNGF IP address(es). The non-alteration of the DSCP field on NWu/NWt is also governed by the SLA and by transport-level arrangements that are outside of 3GPP scope. The SLA also governs the RG PDU session IP addresses. + +The RG's PCF and SMF may provide PCC rules and QoS rules for the available mappings as determined by the SLA. The packet detection filters in the RG's UPF can be based on the N3IWF/TNGF IP address and the DSCP markings on NWu/NWt. + +UE's SMF/PCF may use the UE's local IP address, which is the N6 address of the RG's PDU session, to enable differentiated QoS and charging when the UE is accessing N3IWF/TNGF via a W-5GAN. + +Differentiated charging is enabled by the awareness of N3IWF/TNGF and RG PDU Session IP addresses and also the mapping between DSCP marking and QoS parameters included in the SLA. + +--- + +## Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2019-05 | SP#84 | SP-190458 | - | - | - | MCC Editorial update for presentation to TSG SA#84 for approval | 1.0.0 | +| 2019-06 | SP#84 | - | - | - | - | MCC editorial update for publication after approval | 16.0.0 | +| 2019-09 | SP#85 | SP-190609 | 0001 | 4 | F | Alignment of user location reporting for 5G-RG FWA to TS 23.273 | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0003 | - | B | Deregistration procedure for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0004 | 1 | B | Service request procedure for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0005 | 2 | B | Other procedures for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0006 | 1 | B | User profile management and handover clarifications for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0007 | 1 | B | PDU Session Modification and Release procedures for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0008 | 1 | F | PEI for 5G-RG and FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0009 | 2 | B | Features for W-AGF to act on behalf of FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0011 | 2 | C | Network Functions and entities - PCC clause | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0015 | 3 | B | Applicability of URSP policy | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0018 | 2 | B | Clarification of Network Access Control for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0020 | 3 | B | Clarification of N2 procedures for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0025 | 1 | B | FN-RG Configuration Update | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0026 | 1 | F | Update to FN-RG Registration via W-5GAN | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0027 | 2 | F | Update to PDU Session handling for FN-RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0028 | 2 | F | Update to Session Management procedures for RG | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0030 | 4 | F | Support of IPTV | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0032 | 1 | F | CableLabs, Charter Communications | 16.1.0 | +| 2019-09 | SP#85 | SP-190609 | 0034 | 2 | C | Coordination between PCF and ACS (for FN RG) | 16.1.0 | +| 2019-12 | SP#86 | SP-191076 | 0055 | 1 | F | Clean up of services Description | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0010 | 3 | F | Reporting wireline non-3GPP access in the AM Policy Association | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0012 | 1 | F | Scope of clause 9 | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0029 | 3 | F | Defining support of slicing for Wireline access | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0036 | 3 | F | Addition of support of IPv6 IPTV | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0038 | 6 | F | Line ID uniqueness | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0039 | 3 | F | UDM/UDR subscription data support for a mapping from Line ID to the the SUPI | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0040 | 4 | F | PEI for FN RG (BBF LIAISE-337 / 3GPP S2-1908758) | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0041 | 3 | F | Addition of support of IPTV Leave procedure | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0044 | 1 | F | Resolving open issue on IPv6 multi-homing | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0045 | 1 | F | Correction to the support of RG-LWAC and UDM procedures | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0046 | 2 | F | Correction on FN-RG procedure | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0048 | 3 | F | Clarification of UE behind 5G-RG through trusted Non-3GPP access | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0049 | 1 | F | Clarification of IP address allocation for FN-RG | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0050 | 3 | F | Clarification on 5G-RG with Hybrid access | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0051 | 1 | F | Triggers for procedures initiated by W-AGF | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0052 | 3 | F | Clarification of Session-TMBR | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0053 | 2 | F | QFI and RQI support in BBF W-5GBAN | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0054 | 2 | F | Update to Protocol Stacks for W-5GAN | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0056 | - | F | Service Area Restrictions applicability for FN-CRG, and not FN-BRG | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0057 | - | F | Correction to Clause 7.2.1.1 5G-RG Registration via W-5GAN | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0058 | 2 | F | Separate Multicast access control for multiple STBs behind 5G-RG | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0059 | 2 | F | Addition of Policy Control Request Triggers for wireline access | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0060 | 1 | F | Clarification of IPTV configuration create service operation | 16.2.0 | +| 2019-12 | SP#86 | SP-191076 | 0061 | 1 | F | Non-5G Capable (N5GC) devices alignment with SA3 | 16.2.0 | +| 2020-03 | SP#87E | SP-200068 | 0063 | 2 | F | Corrections to 5G-RG and FN-RG procedures | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 0064 | - | F | Resolving Editor's notes for Hybrid Access / ATSSS | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 0065 | 1 | F | Remove a batch of ENs for WWC | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1829 | 5 | F | Configuration of URSP for FN RG | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1831 | 1 | F | Reference Alignment with BBF | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1832 | 3 | F | TS23.316 - Correction on User Location Information | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1833 | 2 | F | Access type and RAT type per Non-3GPP accesses | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1834 | - | F | Clarification related with the (non) support of PWS and LADN on Wireline access | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1835 | 1 | F | Cable access related corrections | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1837 | 1 | F | AS level parameters to W-5GAN | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 1838 | - | F | Corrections to Hybrid Access | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 2034 | - | F | Mega CR on editorial corrections for 5WWC | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 2035 | 1 | F | Remove the Editor's note for 5WWC | 16.3.0 | +| 2020-03 | SP#87E | SP-200068 | 2036 | 1 | F | Correction to IPTV | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------|---------------| +| 2020-03 | SP#87E | SP-200068 | 2037 | 1 | F | Correction of EAP support in Registration procedure for 5G-RG | 16.3.0 | +| 2020-07 | SP#88E | SP-200427 | 2038 | 1 | F | Removing explicit signalling of RG-TMBR | 16.4.0 | +| 2020-07 | SP#88E | SP-200427 | 2039 | 1 | F | Corrections of RG procedures | 16.4.0 | +| 2020-07 | SP#88E | SP-200427 | 2040 | 1 | F | Correction on RAT types of wireline access | 16.4.0 | +| 2020-07 | SP#88E | SP-200427 | 2041 | 1 | F | Correction on wireline access | 16.4.0 | +| 2020-07 | SP#88E | SP-200427 | 2042 | 1 | F | Adding SUPI and SUCI for N5GC device support | 16.4.0 | +| 2020-07 | SP#88E | SP-200427 | 2044 | 1 | F | Correction of references causing wrong specification | 16.4.0 | +| 2020-07 | SP#88E | SP-200427 | 2045 | - | F | Corrections to description of lawful intercept | 16.4.0 | +| 2020-09 | SP#89E | SP-200676 | 2046 | 1 | F | Handling of IPv6 addresses for FN-RG | 16.5.0 | +| 2020-09 | SP#89E | SP-200676 | 2048 | - | F | Correction to the description of FN-RG Session Modification Procedure | 16.5.0 | +| 2020-09 | SP#89E | SP-200676 | 2049 | 1 | F | Correction on figure in 5WWC | 16.5.0 | +| 2020-12 | SP#90E | SP-200954 | 2050 | - | F | Alignment of 23.316 with TR-456 / TR-470 i.e. the BBF technical specifications | 16.6.0 | +| 2020-12 | SP#90E | SP-200954 | 2051 | 1 | F | Update RG-LWAC via UE context modification procedure | 16.6.0 | +| 2020-12 | SP#90E | SP-200954 | 2053 | 1 | F | Clarification on UDM and UDR services in 5WWC | 16.6.0 | +| 2020-12 | SP#90E | SP-200954 | 2054 | - | F | Correction on 5WWC | 16.6.0 | +| 2020-12 | SP#90E | SP-200954 | 2055 | 1 | F | 5GC Support of DHCP signalling for RG | 16.6.0 | +| 2021-06 | SP#92E | SP-210345 | 2056 | 1 | B | MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC | 17.0.0 | +| 2021-09 | SP#93E | SP-210912 | 2058 | - | A | SSC modes for FN-RG | 17.1.0 | +| 2021-12 | SP#94E | SP-211304 | 2061 | 1 | F | MTU value for wireline access | 17.2.0 | +| 2021-12 | SP#94E | SP-211288 | 2062 | 1 | F | Applicability of ATSSS to 5G-RG in Rel-17 | 17.2.0 | +| 2022-06 | SP#96 | SP-220391 | 2063 | 2 | A | Generalizing NAS transport between 5G and W-AGF to accommodate latest BBF developments | 17.3.0 | +| 2022-06 | SP#96 | SP-220411 | 2064 | 1 | F | Alignment to BBF LS 512 (Frame route, BBF references) | 17.3.0 | +| 2022-06 | SP#96 | SP-220411 | 2065 | 1 | F | Additional support for selecting UPF collocated with W-AGF | 17.3.0 | +| 2022-06 | SP#96 | SP-220391 | 2070 | 1 | A | Correction about 23.316 reference to UE Security Capabilities | 17.3.0 | +| 2022-12 | SP#98E | SP-221062 | 2072 | 1 | F | Change the direction of the arrow in figure | 17.4.0 | +| 2022-12 | SP#98E | SP-221080 | 2073 | - | F | ULI with TAI for wireline access | 17.4.0 | +| 2022-12 | SP#98E | SP-221087 | 2074 | 2 | B | Support of Non-3GPP access for SNPN | 18.0.0 | +| 2023-03 | SP#99 | SP-230081 | 2075 | 1 | B | IPv6 prefix delegation in 5GS | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 2076 | 6 | B | Support of wireline access as access to SNPN | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 2078 | 2 | B | Support for SNPN via wireline access | 18.1.0 | +| 2023-06 | SP#100 | SP-230456 | 2082 | 1 | B | Introducing non-3GPP QoS assistance information | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 2083 | 1 | F | Content of home network domain when SUPI is IMSI | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 2085 | 1 | B | Differentiation for UEs behind 5G-RG | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 2086 | 1 | B | Support for AF influence on TNAP ID | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 2087 | 7 | B | New feature for 5G-RG to support NSWO procedure to authorize UE behind RG | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 2091 | 8 | B | Support of AUN3 device | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 2095 | 4 | B | Support of wireline access as access to NPI-NPN and to SNPN | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 2097 | 1 | B | 5G-RG ID provided in Trusted Non-3GPP access procedure | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 2098 | 6 | B | Non-3GPP Device Category Definitions | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 2099 | 5 | B | Differentiated service for NAUN3 devices connected behind a 5G-RG | 18.2.0 | +| 2023-09 | SP#101 | SP-230838 | 2107 | - | A | RFCs related to DHCPv6 are obsoleted by RFC 8415 | 18.3.0 | +| 2023-09 | SP#101 | SP-230830 | 2109 | 1 | A | Correction of PDU Session Release for 5G-RG | 18.3.0 | +| 2023-12 | SP#102 | SP-231252 | 2113 | 2 | F | Corrections Not related with AUN3 devices | 18.4.0 | +| 2023-12 | SP#102 | SP-231252 | 2114 | 1 | F | Update on deregistration procedure of 5G-RG serving AUN3 devices | 18.4.0 | +| 2023-12 | SP#102 | SP-231252 | 2115 | 2 | F | Clarification on MBR determination for AUN3 device | 18.4.0 | +| 2023-12 | SP#102 | SP-231252 | 2116 | 1 | F | Clarification on UE behind 5G-RG and FN-RG | 18.4.0 | +| 2023-12 | SP#102 | SP-231252 | 2117 | 4 | F | Clarification on handling devices behind 5G-RG | 18.4.0 | +| 2023-12 | SP#102 | SP-231252 | 2119 | 2 | F | Corrections related with AUN3 devices | 18.4.0 | +| 2023-12 | SP#102 | SP-231252 | 2122 | 2 | F | Access restriction for AUN3 devices | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 2123 | 3 | F | SUPI for 5G-CRG support | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 2124 | 3 | F | SUPI for 5G-BRG support | 18.4.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23435/raw.md b/raw/rel-18/23_series/23435/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..19385434087619e2cbdb46368e9357f5ffbcc2ee --- /dev/null +++ b/raw/rel-18/23_series/23435/raw.md @@ -0,0 +1,4713 @@ + + +# 3GPP TS 23.435 V18.1.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for Network Slice Capability Exposure for Application Layer Enablement Service (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------|----| +| Foreword ..... | 10 | +| Introduction ..... | 11 | +| 1 Scope..... | 12 | +| 2 References..... | 12 | +| 3 Definitions of terms, symbols and abbreviations ..... | 13 | +| 3.1 Terms..... | 13 | +| 3.2 Symbols..... | 13 | +| 3.3 Abbreviations ..... | 14 | +| 4 Overview..... | 14 | +| 4.1 Registration ..... | 14 | +| 4.2 Slice API configuration and translation ..... | 14 | +| 4.3 Application layer network slice lifecycle management ..... | 14 | +| 4.4 Network slice optimization based on VAL server policy ..... | 15 | +| 4.5 Discovery of management service exposure..... | 15 | +| 4.6 Network slice performance and analytics monitoring..... | 15 | +| 4.7 Information collection from NSCE server(s)..... | 15 | +| 4.8 Predictive slice modification in edge based NSCE deployments ..... | 15 | +| 4.9 Multiple slices coordinated resource optimization..... | 15 | +| 4.10 Network slice adaptation for VAL application ..... | 15 | +| 4.11 Slice related communication service lifecycle management..... | 16 | +| 4.12 Predictive slice modification in Inter-PLMN based slice service continuity..... | 16 | +| 4.13 Network slice diagnostics..... | 16 | +| 4.14 Network slice fault management capability exposure..... | 16 | +| 4.15 Slice requirements verification and alignment capability exposure..... | 16 | +| 4.16 Network Slice Information delivery..... | 16 | +| 4.17 Network Slice Allocation..... | 16 | +| 5 Business models and relationships for NSCE..... | 17 | +| 6 Architectural requirements..... | 18 | +| 6.1 General Description..... | 18 | +| 6.2 General requirements ..... | 18 | +| 6.3 Network slice Lifecycle management requirements ..... | 18 | +| 6.4 Performance data retrieval requirement ..... | 18 | +| 6.5 Network slice adaption requirement ..... | 18 | +| 6.6 Network slice configuration and translation requirement..... | 18 | +| 6.7 Multiple slices combined management requirement..... | 19 | +| 6.8 Security requirements..... | 19 | +| 7 Application architecture for NSCE ..... | 19 | +| 7.1 General ..... | 19 | +| 7.2 Architecture description ..... | 19 | +| 7.3 Functional entities description ..... | 20 | +| 7.3.1 General ..... | 20 | +| 7.3.2 Network slice capability enablement server..... | 21 | +| 7.3.3 Network slice capability enablement client..... | 21 | +| 7.4 Reference points description ..... | 21 | +| 7.4.1 General ..... | 21 | +| 7.4.2 NSCE-UU ..... | 21 | +| 7.4.3 NSCE-C ..... | 21 | +| 7.4.4 NSCE-S ..... | 21 | +| 7.4.5 N33 ..... | 21 | +| 7.4.6 NSCE-E ..... | 21 | +| 7.4.7 NSCE-OAM ..... | 22 | +| 7.4.8 SEAL-X..... | 22 | + +| | | | +|-----------|------------------------------------------------------------------------------|----| +| 8 | Identities and commonly used values ..... | 22 | +| 8.1 | General ..... | 22 | +| 8.2 | NSCE server ID..... | 22 | +| 8.3 | NSCE client ID..... | 22 | +| 8.4 | Network Slice related Identifier ..... | 22 | +| 8.5 | Slice coverage area..... | 22 | +| 8.6 | NSCE service area..... | 22 | +| 9 | Procedures and information flows ..... | 23 | +| 9.1 | General ..... | 23 | +| 9.1.1 | Common Information Elements ..... | 23 | +| 9.1.1.2 | Service requirement ..... | 23 | +| 9.2 | Registration ..... | 23 | +| 9.3 | Slice API configuration and translation ..... | 23 | +| 9.3.1 | General ..... | 23 | +| 9.3.2 | Procedure..... | 24 | +| 9.3.2.1 | Procedures on slice API configuration ..... | 24 | +| 9.3.2.1.1 | General ..... | 24 | +| 9.3.2.1.2 | Initial Configuration..... | 24 | +| 9.3.2.1.3 | VAL server-initiated Configuration Update ..... | 25 | +| 9.3.2.2 | Procedure on slice API translation..... | 25 | +| 9.3.3 | Information flows ..... | 26 | +| 9.3.3.1 | General..... | 26 | +| 9.3.3.2 | VAL application requirement request..... | 26 | +| 9.3.3.3 | VAL application requirement response ..... | 27 | +| 9.3.3.4 | Slice API information notify..... | 27 | +| 9.3.3.5 | VAL server-initiated configuration update request ..... | 27 | +| 9.3.3.6 | VAL server-initiated configuration update response..... | 27 | +| 9.3.3.7 | slice API invocation request ..... | 28 | +| 9.3.3.8 | slice API invocation response..... | 28 | +| 9.3.4 | APIs..... | 28 | +| 9.3.4.1 | General..... | 28 | +| 9.3.4.2 | SS_NSCE_SliceApiConfiguration API..... | 29 | +| 9.3.4.2.1 | General ..... | 29 | +| 9.3.4.2.2 | SS_NSCE_Slice_API_configuration ..... | 29 | +| 9.3.4.2.3 | SS_NSCE_Slice_API_configuration_update..... | 29 | +| 9.3.4.2.4 | SS_NSCE_Slice_API_information_notify ..... | 29 | +| 9.3.4.3 | SS_NSCE_Slice_ApiInvocation API ..... | 29 | +| 9.3.4.3.1 | General ..... | 29 | +| 9.3.4.3.2 | SS_NSCE_Slice_API_invocation..... | 30 | +| 9.4 | Application layer network slice lifecycle management ..... | 30 | +| 9.4.1 | General ..... | 30 | +| 9.4.2 | Procedure..... | 30 | +| 9.4.2.1 | Procedures on slice lifecycle management..... | 30 | +| 9.4.3 | Information flows ..... | 32 | +| 9.4.3.1 | General..... | 32 | +| 9.4.3.2 | Application layer network slice lifecycle management subscribe request ..... | 32 | +| 9.4.3.3 | Application layer network slice lifecycle management response ..... | 32 | +| 9.4.3.4 | Application layer network slice lifecycle management notification ..... | 33 | +| 9.4.3.5 | QoE metrics subscribe ..... | 33 | +| 9.4.3.6 | QoE metrics response ..... | 34 | +| 9.4.3.7 | QoE metrics notification..... | 34 | +| 9.4.3.8 | Network slice LCM recommendation request..... | 34 | +| 9.4.3.9 | Network slice LCM recommendation response..... | 34 | +| 9.4.4 | APIs..... | 35 | +| 9.4.4.1 | General..... | 35 | +| 9.4.4.2 | SS_NSCE_AppLayerNSLCM_Subscribe operation..... | 35 | +| 9.4.4.3 | SS_NSCE_AppLayerNSLCM_Notify operation ..... | 35 | +| 9.4.4.4 | SS_NSCE_Val_QoEMetrics_Subscribe operation..... | 35 | +| 9.4.4.5 | SS_NSCE_Val_QoEMetrics_Notify operation..... | 36 | +| 9.4.4.6 | SS_NSCE_Val_NSLCMRecommendation_Request operation ..... | 36 | +| 9.5 | Network slice optimization based on VAL server policy ..... | 36 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------|----| +| 9.5.1 | General ..... | 36 | +| 9.5.2 | Procedure ..... | 36 | +| 9.5.2.1 | VAL server policy management..... | 36 | +| 9.5.2.1.1 | VAL server policy provisioning..... | 36 | +| 9.5.2.1.2 | VAL server policy Update ..... | 37 | +| 9.5.2.1.3 | VAL server policy Delete ..... | 38 | +| 9.5.2.1.4 | Policy harmonization..... | 39 | +| 9.5.2.1.5 | VAL server policy Usage Reporting data ..... | 39 | +| 9.5.2.2 | Network slice optimization based on VAL server policy..... | 40 | +| 9.5.2.3 | Network slice optimization report retrieval ..... | 41 | +| 9.5.3 | Information flows ..... | 42 | +| 9.5.3.1 | General..... | 42 | +| 9.5.3.2 | VAL server policy provisioning request..... | 42 | +| 9.5.3.3 | VAL server policy provisioning response ..... | 44 | +| 9.5.3.4 | VAL server policy update request ..... | 44 | +| 9.5.3.5 | VAL server policy update response..... | 45 | +| 9.5.3.6 | VAL server policy delete request ..... | 45 | +| 9.5.3.7 | VAL server policy delete response..... | 45 | +| 9.5.3.8 | VAL server policy usage reporting data subscribe request ..... | 46 | +| 9.5.3.9 | VAL server policy usage reporting data subscribe response ..... | 46 | +| 9.5.3.10 | VAL server policy usage reporting data notification..... | 46 | +| 9.5.3.11 | Network slice optimization subscription request..... | 47 | +| 9.5.3.12 | Network slice optimization subscription response ..... | 47 | +| 9.5.3.13 | Network slice optimization notification ..... | 47 | +| 9.5.3.14 | Network slice optimization report retrieval request ..... | 48 | +| 9.5.3.15 | Network slice optimization report retrieval response..... | 48 | +| 9.5.3.16 | Policy harmonization subscribe notify ..... | 49 | +| 9.5.4 | APIs ..... | 49 | +| 9.5.4.1 | General..... | 49 | +| 9.5.4.2 | SS_NSCE_Policy_Provisioning operation ..... | 49 | +| 9.5.4.3 | SS_NSCE_Policy_Update operation ..... | 49 | +| 9.5.4.4 | SS_NSCE_Policy_Delete operation ..... | 49 | +| 9.5.4.5 | SS_NSCE_Policy_harmonization Notify operation ..... | 50 | +| 9.5.4.6 | SS_NSCE_Policy_Usage_Reporting_Data_Subscribe operation ..... | 50 | +| 9.5.4.7 | SS_NSCE_Policy_Usage_Reporting_Data_Notification operation..... | 50 | +| 9.5.4.8 | SS_NSCE_NS_Optimization_Report_Retrieval operation ..... | 50 | +| 9.5.4.9 | SS_NSCE_NSOptimization_Subscribe Request operation..... | 50 | +| 9.5.4.10 | SS_NSCE_NSOptimization_Notification operation ..... | 51 | +| 9.6 | Discovery of management service exposure..... | 51 | +| 9.6.1 | General ..... | 51 | +| 9.6.2 | Procedure ..... | 51 | +| 9.6.2.1 | VAL-triggered MnS discovery procedure ..... | 51 | +| 9.6.2.2 | OAM-triggered new/modified MnS discovery..... | 52 | +| 9.6.3 | Information flows ..... | 53 | +| 9.6.3.1 | General..... | 53 | +| 9.6.3.2 | Management service discovery subscribe request..... | 53 | +| 9.6.3.3 | Management service discovery subscribe response..... | 54 | +| 9.6.3.4 | Management service discovery notify ..... | 54 | +| 9.6.4 | APIs ..... | 54 | +| 9.6.4.1 | General..... | 54 | +| 9.6.4.2 | SS_NSCE_Management_Service Discovery ..... | 55 | +| 9.6.4.2.1 | General ..... | 55 | +| 9.6.4.2.2 | SS_NSCE_Management_Service Discovery ..... | 55 | +| 9.7 | Network slice related performance and analytics monitoring..... | 55 | +| 9.7.1 | General ..... | 55 | +| 9.7.2 | Procedure ..... | 55 | +| 9.7.2.1 | Network slice related performance and analytics monitoring job creation request..... | 55 | +| 9.7.2.2 | Network slice related performance and analytics report subscription and report..... | 56 | +| 9.7.2.3 | Multiple slices related performance and analytics consolidated report request ..... | 57 | +| 9.7.3 | Information flows ..... | 58 | +| 9.7.3.1 | General..... | 58 | +| 9.7.3.2 | Network slice related performance and analytics monitoring job creation request and response..... | 59 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------|----| +| 9.7.3.3 | Network slice related performance and analytics report subscription ..... | 59 | +| 9.7.3.4 | Network slice related performance and analytics report Notify ..... | 60 | +| 9.7.3.5 | Multiple slices related performance and analytics consolidated report request and response..... | 61 | +| 9.7.4 | APIs ..... | 62 | +| 9.7.4.1 | General ..... | 62 | +| 9.7.4.2 | SS_NSCE_PerfMonitoring API ..... | 63 | +| 9.7.4.3 | SS_NSCE_PerfReportSubscription API..... | 63 | +| 9.7.4.4 | SS_NSCE_PerfReport API..... | 63 | +| 9.7.4.5 | SS_NSCE_MultiSlicePerfReport API..... | 63 | +| 9.8 | Information collection from NSCE server(s) ..... | 64 | +| 9.8.1 | General ..... | 64 | +| 9.8.2 | Procedure ..... | 64 | +| 9.8.2.1 | Information collection from NSCE server(s) subscribe request and response ..... | 64 | +| 9.8.2.2 | Information collection from NSCE server(s) Notify ..... | 65 | +| 9.8.3 | Information flows ..... | 65 | +| 9.8.3.1 | General ..... | 65 | +| 9.8.3.2 | Information collection from NSCE server(s) subscribe request..... | 65 | +| 9.8.3.3 | Information collection from NSCE server(s) subscribe response ..... | 65 | +| 9.8.3.4 | Information collection from NSCE server(s) notify ..... | 66 | +| 9.8.4 | APIs ..... | 66 | +| 9.8.4.1 | General ..... | 66 | +| 9.8.4.2 | SS_NSCE_InfoCollection_Subscribe operation..... | 66 | +| 9.8.4.3 | SS_NSCE_InfoCollection_Notify operation ..... | 66 | +| 9.9 | Predictive slice modification in edge based NSCE deployments ..... | 67 | +| 9.9.1 | General ..... | 67 | +| 9.9.2 | Procedure ..... | 67 | +| 9.9.2.1 | Procedures on slice API configuration ..... | 67 | +| 9.9.3 | Information flows ..... | 69 | +| 9.9.3.1 | General ..... | 69 | +| 9.9.3.2 | Application service continuity requirement request ..... | 69 | +| 9.9.3.3 | Application service continuity requirement response..... | 69 | +| 9.9.3.4 | Service continuity negotiation request..... | 70 | +| 9.9.3.5 | Service continuity negotiation response ..... | 70 | +| 9.9.3.6 | Slice modification notify ..... | 70 | +| 9.9.4 | APIs ..... | 71 | +| 9.9.4.1 | General ..... | 71 | +| 9.9.4.2 | SS_NSCE_Service_Continuity_Requirement ..... | 71 | +| 9.9.4.2.1 | General ..... | 71 | +| 9.9.4.2.2 | Service_Continuity_Requirement ..... | 71 | +| 9.9.4.3 | SS_NSCE_Service_Continuity_Negotiation ..... | 71 | +| 9.9.4.3.1 | General ..... | 71 | +| 9.9.4.3.2 | Service_Continuity_Negotiation ..... | 72 | +| 9.9.4.4 | SS_NSCE_Slice_Modification_Notify ..... | 72 | +| 9.9.4.4.1 | General ..... | 72 | +| 9.9.4.3.2 | Slice_Modification_Notify..... | 72 | +| 9.10 | Multiple slices coordinated resource optimization..... | 72 | +| 9.10.1 | General ..... | 72 | +| 9.10.2 | Procedure ..... | 72 | +| 9.10.2.1 | Procedure on multiple slices coordinated resource optimization ..... | 72 | +| 9.10.3 | Information flows ..... | 74 | +| 9.10.3.1 | General ..... | 74 | +| 9.10.3.2 | Multiple slices coordinated resource optimization request..... | 74 | +| 9.10.3.3 | Multiple slices coordinated resource optimization response ..... | 74 | +| 9.10.4 | APIs ..... | 74 | +| 9.10.4.1 | General ..... | 74 | +| 9.10.4.2 | SS_NSCE_MultiSlices_Optimization operation ..... | 75 | +| 9.11 | Network slice adaptation for VAL application ..... | 75 | +| 9.11.1 | General ..... | 75 | +| 9.11.2 | Procedures ..... | 75 | +| 9.11.2.1 | Procedure for VAL server-triggered and network-based network slice adaptation for VAL application..... | 75 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------|----| +| 9.11.2.2 | Procedure for VAL UE-triggered and network-based network slice adaptation for VAL application..... | 76 | +| 9.11.3 | Information flows ..... | 77 | +| 9.11.3.1 | Network slice adaptation request..... | 77 | +| 9.11.3.2 | Network slice adaptation response ..... | 78 | +| 9.11.3.3 | Network slice adaptation trigger..... | 78 | +| 9.11.3.4 | Network slice adaptation trigger response..... | 79 | +| 9.11.4 | APIs ..... | 79 | +| 9.11.4.1 | General..... | 79 | +| 9.11.4.2 | SS_NSCE_NetworkSliceAdaptation API..... | 80 | +| 9.11.4.2.1 | General ..... | 80 | +| 9.11.4.2.2 | Network_Slice_Adaptation ..... | 80 | +| 9.12 | Slice related communication service lifecycle management exposure ..... | 80 | +| 9.12.1 | General ..... | 80 | +| 9.12.2 | Procedure ..... | 80 | +| 9.12.2.1 | Procedures on slice related communication service lifecycle management exposure..... | 80 | +| 9.12.2.1.1 | Slice related Communication Service Creation ..... | 80 | +| 9.12.2.1.2 | Slice related Communication Service Reconfiguration ..... | 81 | +| 9.12.2.1.3 | Slice related Communication Service disengagement ..... | 82 | +| 9.12.3 | Information flows ..... | 83 | +| 9.12.3.1 | General..... | 83 | +| 9.12.3.2 | Slice related communication service creation ..... | 83 | +| 9.12.3.3 | Slice related communication service reconfiguration..... | 84 | +| 9.12.3.4 | Slice related communication service disengagement ..... | 86 | +| 9.12.4 | APIs ..... | 86 | +| 9.12.4.1 | General..... | 86 | +| 9.12.4.2 | SS_NSCE_SliceCommService_Creation API..... | 86 | +| 9.12.4.3 | SS_NSCE_SliceCommService_Reconfiguration API ..... | 87 | +| 9.12.4.4 | SS_NSCE_SliceCommService_Disengagement API..... | 87 | +| 9.13 | Predictive slice modification in Inter-PLMN based slice service continuity..... | 87 | +| 9.13.1 | General ..... | 87 | +| 9.13.2 | Procedure ..... | 87 | +| 9.13.3 | Information flows ..... | 89 | +| 9.13.3.1 | General..... | 89 | +| 9.13.3.2 | Inter-PLMN application service continuity requirement request ..... | 89 | +| 9.13.3.3 | Inter-PLMN slice modification notify ..... | 90 | +| 9.13.4 | APIs ..... | 90 | +| 9.13.4.1 | General..... | 90 | +| 9.13.4.2 | SS_NSCE_Inter-PLMN_Continuity API..... | 91 | +| 9.13.4.3 | SS_NSCE_Inter-PLMN_slice modification notify API ..... | 91 | +| 9.14 | Network slice diagnostics..... | 91 | +| 9.14.1 | General ..... | 91 | +| 9.14.2 | Procedure ..... | 91 | +| 9.14.2.1 | Network slice diagnostics procedure ..... | 91 | +| 9.14.3 | Information flows ..... | 92 | +| 9.14.3.1 | General..... | 92 | +| 9.14.3.2 | Network slice diagnostics request and response..... | 92 | +| 9.14.4 | APIs ..... | 93 | +| 9.14.4.1 | General..... | 93 | +| 9.14.4.2 | SS_NSCE_Network_Slice_Diagnostics..... | 94 | +| 9.14.4.2.1 | General ..... | 94 | +| 9.14.4.2.2 | Network_Slice_Diagnostics ..... | 94 | +| 9.15 | Network slice fault management capability exposure..... | 94 | +| 9.15.1 | General ..... | 94 | +| 9.15.2 | Procedure ..... | 94 | +| 9.15.2.1 | Procedures on network slice fault management capability exposure ..... | 94 | +| 9.15.3 | Information flows ..... | 96 | +| 9.15.3.1 | General..... | 96 | +| 9.15.3.2 | Fault diagnosis subscription request..... | 96 | +| 9.15.3.3 | Response of fault diagnosis subscription..... | 96 | +| 9.15.3.4 | Fault diagnosis notification..... | 96 | + +| | | | +|-------------------------------------------------------|---------------------------------------------------------------------------------------|------------| +| 9.15.4 | APIs ..... | 97 | +| 9.15.4.1 | General ..... | 97 | +| 9.15.4.2 | SS_NSCE_FaultDiagnosis API ..... | 97 | +| 9.15.4.2.1 | General ..... | 97 | +| 9.15.4.2.2 | Fault_Diagnosis_Subscribe ..... | 97 | +| 9.15.4.2.3 | Fault_Diagnosis_Notification ..... | 97 | +| 9.16 | Slice requirements verification and alignment capability exposure ..... | 98 | +| 9.16.1 | General ..... | 98 | +| 9.16.2 | Procedure ..... | 98 | +| 9.16.2.1 | Procedures on slice requirements verification and alignment capability exposure ..... | 98 | +| 9.16.3 | Information flows ..... | 100 | +| 9.16.3.1 | General ..... | 100 | +| 9.16.3.2 | Slice requirements verification and alignment subscription ..... | 100 | +| 9.16.3.3 | Response of slice requirements verification and alignment subscription ..... | 100 | +| 9.16.3.4 | Slice requirements verification and alignment notification ..... | 100 | +| 9.16.4 | APIs ..... | 101 | +| 9.16.4.1 | General ..... | 101 | +| 9.16.4.2 | SS_NSCE_SliceReq_VerifyAndAlign API ..... | 101 | +| 9.16.4.2.1 | General ..... | 101 | +| 9.16.4.2.2 | SliceReq_VerifyAndAlign_Subscribe ..... | 101 | +| 9.16.4.2.3 | SliceReq_VerifyAndAlign_Notification ..... | 101 | +| 9.17 | Network Slice Information delivery ..... | 102 | +| 9.17.1 | General ..... | 102 | +| 9.17.2 | Procedure ..... | 102 | +| 9.17.2.1 | Network Slice Information delivery request ..... | 102 | +| 9.17.2.2 | Network Slice Information delivery to NSCE client request ..... | 103 | +| 9.17.3 | Information flows ..... | 104 | +| 9.17.3.1 | Network Slice Information delivery request ..... | 104 | +| 9.17.3.2 | Network Slice Information delivery response ..... | 105 | +| 9.17.3.3 | Slice Information delivery to NSCE client ..... | 105 | +| 9.17.3.4 | Slice Information delivery to NSCE client ..... | 105 | +| 9.17.4 | APIs ..... | 106 | +| 9.17.4.1 | General ..... | 106 | +| 9.17.4.2 | SS_NSCE_NSInfoDelivery Get operation ..... | 106 | +| 9.17.4.3 | SS_NSCE_NSInfoDelivery_Client Request operation ..... | 106 | +| 9.18 | Network Slice Allocation in NSaaS model ..... | 106 | +| 9.18.1 | General ..... | 106 | +| 9.18.2 | Procedure ..... | 107 | +| 9.18.2.1 | Network Slice Allocation in NSaaS model ..... | 107 | +| 9.18.3 | Information flows ..... | 108 | +| 9.18.3.1 | General ..... | 108 | +| 9.18.3.2 | Network Slice Allocation ..... | 108 | +| 9.18.4 | APIs ..... | 109 | +| 9.18.4.1 | General ..... | 109 | +| 9.18.4.2 | SS_NSCE_NSAllocation_Request /Response operation ..... | 109 | +| 9.19 | Authorization and authentication ..... | 110 | +| Annex A (informative): Deployment models ..... | | 110 | +| A.1 | Deployment scenarios ..... | 110 | +| A.1.1 | General ..... | 110 | +| A.1.2 | Centralized NSCE deployment ..... | 110 | +| A.1.3 | Distributed NSCE deployment ..... | 111 | +| A.1.4 | NPN NSCE deployment ..... | 111 | +| A.1.5 | Edge NSCE deployment ..... | 112 | +| A.2 | Deployment of NSCE server(s) in relation to VAL server and 3GPP system ..... | 112 | +| A.2.1 | Centralized NSCE deployment ..... | 113 | +| A.2.2 | Distributed NSCE deployment ..... | 113 | + +A.3 Deployment of NSCE server(s) in relation to SEAL..... 113 + +Annex B (informative): Change history..... 114 + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +--- + +## Introduction + +Network slice capability enablement (NSCE) is a service that enables the network slice related capabilities towards 3rd party on the basis of R17 SEAL. The NSCE service provides additional functionality and exposes slice capabilities based on 5GS management system services (e.g MnS services) and 5GS network services (e.g. NEF APIs, NWDAF APIs, NSACF APIs). This technical specification provides architecture and procedures for enabling NSCE service over 3GPP networks. + +--- + +## 1 Scope + +The present document specifies the procedures and information flows necessary for Network Slice Capability Exposure for Application Layer Enablement on the basis of SEAL. + +--- + +## 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [3] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2". +- [4] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [5] GSMA NG.116 - Generic Network Slice Template. +- [6] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1". +- [7] 3GPP TS 28.532: "Management and orchestration; Generic management services". +- [8] 3GPP TS 28.531: "Management and orchestration; Provisioning". +- [9] 3GPP TS 28.537: "Management and orchestration; Management capabilities". +- [10] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3". +- [11] 3GPP TS 28.535: "Management and orchestration; Management services for communication service assurance; Requirements". +- [12] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". +- [13] 3GPP TS 29.536: "5G System; Network Slice Admission Control Service; Stage 3". +- [14] 3GPP TS 33.501: "Security architecture and procedures for 5G System" +- [15] 3GPP TS 28.530: "Management and orchestration; Concepts, use cases and requirements" +- [16] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [17] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [18] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [19] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". + +- [20] 3GPP TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)". +- [21] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics".[22] 3GPP TS 23.558: "Architecture for enabling Edge Applications". +- [22] 3GPP TS 33.434: "Service Enabler Architecture Layer (SEAL); Security aspects for Verticals". +- [23] 3GPP TS 28.545: "Management and orchestration; Fault Supervision (FS) " +- [24] 3GPP TS 32.111-1: "Management and orchestration; Fault management, Part 1: 3G fault management requirements". +- [25] 3GPP TS 28.533: "Management and orchestration; Architecture framework". +- [26] 3GPP TS 23.436: "Procedures for Application Data Analytics Enablement Service" +- [27] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction ". +- [28] 3GPP TS 28.202: "Charging management; Network slice management charging in the 5G System (5GS); Stage 2". + +... + +--- + +## 3 Definitions of terms, symbols and abbreviations + +### 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**VAL server policy:** Network slice management Policy which can be seen as application function policy from VAL Provider/ slice customer/ASP, abstracted based on the slice usage pattern of application, consisting of trigger event and expected action. When provided to NSCE server, the NSCE server will trigger the expected action based on the policy. + +**MNO policy:** The network slice management policy between the VAL and MNO pertaining to a specific service and slice, including ranges of network slice capabilities which can be adapted, i.e. Network slice Service level agreement. + +**NSCE service provider policy (NSPP):** The network slice capability enablement service policy between the VAL and NSCE service provider pertaining to a specific service and slice, including ranges of network slice capability enablement service which can be adapted, i.e. NSCE service level agreement. + +**Policy harmonization:** The NSCE service that harmonizing the VAL server policy parameter, to make sure the VAL server policy is compatible with the policies of the MNO and NSCE service provider policy for the same service or slice. + +**Requirement alignment:** The NSCE service that aligning the network slice performance and the VAL service requirement in the request. + +### 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------------|----------------------------------------------------------------| +| ASP | Application Service Provider | +| Auto-NS-LCM | Automatic Application Layer Network Slice Lifecycle Management | +| EDN | Edge Data Network | +| EGMF | Exposure Governance Management Function | +| GST | Generic Network Slice Template | +| KPI | Key Performance Indicator | +| KQI | Key Quality Indicator | +| MnS | Management Service | +| MNO | Mobile Network Operator | +| NEF | Network Exposure Function | +| NEST | Network Slice Template | +| NOP | Network Operator | +| NSCE | Network Slice Capability Enablement | +| NSaaS | Network Slice as a Service | +| NSI | Network Slice Instance | +| NSSI | Network Slice Subnet Instance | +| NWDAF | Network Data Analytics Function | +| NSACF | Network Slice Admission Control Function | +| NSC | Network Slice consumer | +| NSP | Network Slice Provider | +| NSMF | Network Slice Management Function | +| OAM | Operation, administration and maintenance | +| QoE | Quality of Experience | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| SLA | Service Level agreement | +| VAL | Vertical Application Layer | + +--- + +## 4 Overview + +### 4.1 Registration + +This functionality enables the VAL server to become a recognized user of CAPIF. VAL server registration procedures are specified in clause 9.2. + +### 4.2 Slice API configuration and translation + +This functionality is provided to the vertical application specific layer and configures the exposure of APIs in a slice-tailored manner. It is assumed that the VAL server is not initially aware of the all the API exposure capabilities and information which will be needed for the given slice based on the SLA, and NSCE plays a vital role in configuring and translating the slice API based on the per slice requirements to service APIs. Slice API configuration and translation procedures are specified in clause 9.3. + +### 4.3 Application layer network slice lifecycle management + +Application layer network slice lifecycle management is provided to the VAL to better meet consumer's requirement without having to interact with 5GS frequently, based on network slice status collected from 5GS and QoE collected from application layer. Application layer network slice lifecycle management procedures are specified in clause 9.4. + +## 4.4 Network slice optimization based on VAL server policy + +Network slice optimization based on VAL server policy optimizes the network slice for the vertical applications by triggering the network slice modification exposed by EGMF defined in SA5. Network slice optimization based on VAL server policy procedures are specified in clause 9.5. + +## 4.5 Discovery of management service exposure + +This network slice capability enablement feature supports the initial discovery of MnS for a given slice based on VAL server request, and the discovery of new/modified MnS with the required exposure (for example the permissions of the VAL server over the target MnS, e.g. read, write operations). This feature consists of two procedures, which are specified in clause 9.6: + +- Discovery of management service capabilities and related permissions (e.g. permitted CRUD operations) based on VAL server request; +- Discovery and exposure of new or modified management service capabilities based on changes at OAM. + +## 4.6 Network slice performance and analytics monitoring + +This functionality is provided to the VAL to get end to end network slice related performance and analytic monitoring. The NSCE server identifies which data are needed, collects the data from different data sources (e.g., the OAM system, the 5GC Network, etc.), performs data processing and abstraction, exposes the processed data to VAL servers. Network slice performance and analytics monitoring procedures are specified in clause 9.7. + +## 4.7 Information collection from NSCE server(s) + +The network slice status collected by the NSCE server could be exposed to other NSCE server(s) if some agreement has been made. Information collection from NSCE server(s) procedures are specified in clause 9.8. + +## 4.8 Predictive slice modification in edge based NSCE deployments + +This feature addresses scenarios where the NSCE server is deployed at the edge and the migration to different Data Network will require that the ongoing slice is supported at the target area to ensure meeting the application session requirements. The slice parameters monitoring at the target area (e.g. for per NSI/NSSI resource situation) need to be known at the server NSCE server to allow for pro-active slice (or slice subnet) modification trigger to avoid degradation of the application service performance. Predictive slice modification procedures are specified in clause 9.9. + +## 4.9 Multiple slices coordinated resource optimization + +This functionality is provided to the VAL to monitor the slice usage status of multiple slices (PNI-NPN slice(s) and its private slice in the PLMN) of the PNI-NPN owner in a combined manner. It makes resource adjustment between different slices in one PLMN to realize optimized and efficient resource usage among multiple slices sharing common network resources. Coordinated PLMN and PNI-NPN slice resource optimization procedures are specified in clause 9.10. + +## 4.10 Network slice adaptation for VAL application + +This functionality is provided to the VAL to adapt the network slice for the VAL application. Such adaptation assumes that the UE is subscribed to more than one slice and is done via providing a guidance to update the URSP rules at the 5GS. The network slice adaptation request can be triggered by VAL server or VAL UE. Network slice adaptation for VAL application procedures are specified in clause 9.11. + +## 4.11 Slice related communication service lifecycle management + +This functionality is provided to the VAL server to make slice related communication service lifecycle management. The NSCE server can acquire the application services related requirements for a specific VAL service from the vertical industry perspective, evaluate these requirements and then determines the network slice by pre-configured industry mapping relations or by KQI-KPI translation algorithms. After the network slice requirements are determined, the NSCE server allocates proper network slice resources to support the application services. Slice related communication service lifecycle management exposure procedures are specified in clause 9.12. + +## 4.12 Predictive slice modification in Inter-PLMN based slice service continuity + +This functionality is provided to the VAL to make predictive slice modification where NSCE service provider provides its services when connected to two PLMNs and has SLA with them. The NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target PLMN and make slice modification decision if needed. Predictive slice modification in Inter-PLMN based slice service continuity procedures are specified in clause 9.13. + +## 4.13 Network slice diagnostics + +Network slice diagnostics provides possibility for the vertical/ASP using VAL server to receive information about the specific event(s) related to service experience. The vertical/ASP using the VAL server has estimated bad QoE for a mobile user or service – either reported from a mobile user or service or detected by application, can initiate a check with NSCE. The NSCE server can provide Network slice diagnostics details related to the identified event as specified in clause 9.14. + +## 4.14 Network slice fault management capability exposure + +Network slice fault management capability exposure gathers data from different sources (e.g., OAM, VAL server, NSCE client) and provides fault data that characterize the quality of the network connections and services to ensure a quick reaction to identify network connectivity, performance related problems. The Network slice fault management capability exposure is specified in clause 9.15. + +## 4.15 Slice requirements verification and alignment capability exposure + +Slice requirements verification and alignment capability exposure provides the capability of comparing the QoS achievement status together with the OAM QoS data versus real customer QoS data (e.g., Mean Opinion Score) collected from VAL client by checking whether the existing QoS/Slice related data is able to satisfy the VAL clients. Periodically alignment notifications are sent to VAL server for the slice requirements alignment. The Slice requirements verification and alignment capability exposure is specified in clause 9.16. + +## 4.16 Network Slice Information delivery + +The Network Slice information delivery sends the Network Slice information to VAL server and NSCE client. With that information, the VAL server is able to manage the network slice for their service such as preparation, creation, activation and termination (tear-down) of network slice. The Network Slice Information delivery is specified in clause 9.17. + +## 4.17 Network Slice Allocation + +The NSCE server performs the Network Slice allocation operation on behalf of the VAL server if non-trusted 3rd party application (i.e., VAL server) cannot access to the 5GS management system directly. The specific service is specified in clause 9.18. + +## 5 Business models and relationships for NSCE + +NSCE layer provides value added services to VAL customers, based on consuming 5GS services related to slicing (from OAM, 5GC) and based on interacting with the VAL UE side. The variety of services and the deployment aspects depend on the different assumptions for the slice owner / provider, the slice customer and the SEAL service provider. With respect to NSCE, the NSCE server belongs to the SEAL provider (as stated in TS 23.434 [2] clause 5) who can be either the MNO itself, or the vertical customer (e.g. factory owner, automaker X) or the edge/cloud provider (e.g. hyperscaler) who provides such platform services related to slice capability exposure to the vertical customer on top of the MNO. Thus, NSCE can play different roles based on the business models. For example, NSCE server can be: + +- deployed by NOP / MNO. +- deployed by an Edge / Cloud Provider. In this case, it is assumed that the NSCE server is acting as an authorized AF/AS. +- deployed by a vertical industry, which can be the end slice customer. + +From business perspective, the following business model applies. In Figure 5-1, the different interactions among all the involved entities are provided. More specifically, in this model the end user is the consumer of the applications provided by the vertical/ASP and can have app-level service agreement with vertical/ASP(s). + +The end user/UE also has a PLMN subscription arrangement with the MNO. The UE used by the end user is allowed to be registered on the MNO's network. MNO (via OAM) can have a slice SLA with the vertical / ASP, which is optional when vertical customer is the NSC. In addition, due to the involvement of a NSCE service provider, additional agreements can be possible between the NSCE server and VAL/ASP layer and the NOP/MNO(s): + +- the enablement service agreement between VAL/ASP layer and the NSCE service provider include the agreement on the value-added services, which in case on NSaaS these are services related to the consumed slice from NOP. So, the end customer (VAL) subscribes to NSCE server for receiving additional services for optimizing the slice utilization. In case that the NSCE server is a NSP towards VAL customer, then such agreement can relate to slice SLA (for the slice provided by the NSCE server). When the NSCE server is part of the vertical, the service agreement between VAL/ASP layer and the NSCE service provider is internal to a single organization. +- the service agreement between MNO and NSCE service provider is for consuming 5GS services (and being also authorized to provide additional services on top). Such agreement could be also a slice SLA for the scenarios when NSCE server is the NSC of the MNO (in NSaaS model). + +![Figure 5-1: Business relationships diagram showing interactions between Vertical/ASP, End user/UE, Network Slice Capability Enabler (NSCE), and MNO.](29f586959675cafdf81cf934954908eb_img.jpg) + +``` + +graph TD + VASP[Vertical / ASP] <--> EUE[End user / UE] + VASP <--> NSCE[Network Slice Capability Enabler (NSCE)] + NSCE <--> MNO[MNO] + EUE <--> MNO + VASP -.-> MNO + +``` + +The diagram illustrates the business relationships between four entities: Vertical / ASP, End user / UE, Network Slice Capability Enabler (NSCE), and MNO. + - Vertical / ASP and End user / UE are connected by a double-headed arrow labeled 'App-level service agreement'. + - Vertical / ASP and Network Slice Capability Enabler (NSCE) are connected by a double-headed arrow labeled 'Enablement service agreement'. + - Network Slice Capability Enabler (NSCE) and MNO are connected by a double-headed arrow labeled 'Service agreement, Slice SLA'. + - End user / UE and MNO are connected by a double-headed arrow labeled 'PLMN subscription arrangement'. + - A dashed arrow points from Vertical / ASP to MNO, labeled 'slice SLA'. + +Figure 5-1: Business relationships diagram showing interactions between Vertical/ASP, End user/UE, Network Slice Capability Enabler (NSCE), and MNO. + +**Figure 5-1: Business relationships** + +In case of shared RAN between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL) using the shared RAN via one or both operators. + +In case of national roaming between operators, one NSCE service provider (slice service provider) can use NSCE to offer slice services using resources of these operators to end customer (VAL). + +--- + +## 6 Architectural requirements + +### 6.1 General Description + +The following clauses specify the requirements for network slice capability enablement services for application layers. + +### 6.2 General requirements + +[AR-6.2-1] The NSCE architecture shall support the NSCE server to communicate with the VAL server with one or more applications. + +[AR-6.2-2] The NSCE architecture shall support the NSCE server to communicate with one or more VAL servers. + +[AR-6.2-3] The NSCE architecture shall support the NSCE server to interact with 3GPP network management system(s) to consume network slice management services provided by MNO(s). The network management system(s) can belong to the same PLMN or different PLMNs on which the NSCE service provider offers its services. + +[AR-6.2-4] The APIs interactions between the vertical application server(s) and NSCE server(s) shall conform to CAPIF as specified in 3GPP TS 23.222 [3]. + +[AR-6.2-5] The NSCE architecture shall support the NSCE server to communicate with one or more other NSCE server(s). + +### 6.3 Network slice Lifecycle management requirements + +[AR-6.3-1] The NSCE architecture shall enable lifecycle management capability exposure of network slice by authorized VAL server. + +[AR-6.3-2] The NSCE architecture shall enable lifecycle management capability exposure of network slice communication service to authorized VAL server. + +[AR-6.3-3] The NSCE architecture shall support the interactions with 3GPP network management system to consume network slice lifecycle management service provided by MNO. + +### 6.4 Performance data retrieval requirement + +[AR-6.4-1] The NSCE architecture shall support the end-to-end network slice performance and analytics monitoring capability exposure to authorized VAL server. + +### 6.5 Network slice adaption requirement + +[AR-6.5-1] The NSCE architecture shall support the network slice adaption capability exposure to authorized VAL server. + +[AR-6.5-2] The NSCE architecture shall support the network slice adaption capability exposure to authorized NSCE client. + +### 6.6 Network slice configuration and translation requirement + +[AR-6.6-1] The NSCE architecture shall support the network slice configuration capability exposure to authorized VAL server. + +[AR-6.6-2] The NSCE architecture shall support the network slice translation capability to enable the translation of slice API invoked by VAL server. + +## 6.7 Multiple slices combined management requirement + +[AR-6.7-1] The NSCE architecture shall support the interactions with OAM or 5GC of 3GPP PLMN to provide multiple slices combined management service of that PLMN. + +[AR-6.7-2] The NSCE architecture shall provide multiple slices combined performance monitoring service of the PLMN and its PNI-NPNs to authorized VAL server. + +[AR-6.7-3] The NSCE architecture shall provide multiple slices coordinated resource optimization service between the PLMN and its PNI-NPNs to authorized VAL server. + +## 6.8 Security requirements + +[AR-6.8-1] The NSCE architecture shall provide mechanisms to authorize the usage of network slicing related services by the VAL servers and NSCE clients, conform to CAPIF as specified in 3GPP TS 23.222 [3]. + +[AR-6.8-2] The NSCE architecture shall support mutual authentication and authorization check between clients and servers, servers and servers that interact, conform to CAPIF as specified in 3GPP TS 23.222 [3]. + +NOTE: The authentication and authorization aspects related to VAL servers and NSCE enablers are out scope of this study and to be addressed by SA3, in TS 33.434[21]. + +# 7 Application architecture for NSCE + +## 7.1 General + +The architecture for the network slice capability enablement is based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [2]. It is organized into functional entities to describe a functional architecture which addresses the support for network slice capability enablement aspects for vertical applications. Since the slicing is a feature which considers the Uu interfaces, only the on-network functional model is specified in this clause. + +## 7.2 Architecture description + +Figure 7.2-1 depicts the network slice capability enablement architecture in the non-roaming case, using the reference point representation showing how various entities interact with each other. + +![Figure 7.2-1: Architecture for network slice capability enablement – reference points representation. The diagram shows three main entities: VAL UE, 3GPP network system, and VAL server(s). The VAL UE contains VAL client(s) and Network slice capability enablement client. The 3GPP network system contains NSCE-OAM. The VAL server(s) contains NSCE-S. Reference points are shown as VAL-UU, NSCE-UU, N33/N5, and NSCE-OAM. A dashed line separates the VAL and SEAL layers.](3191384ecc1531d40a00140dd21fd781_img.jpg) + +The diagram illustrates the architecture for network slice capability enablement. It is divided into three main vertical components: VAL UE, 3GPP network system, and VAL server(s). The VAL UE contains two sub-components: VAL client(s) and Network slice capability enablement client. The 3GPP network system contains NSCE-OAM. The VAL server(s) contains NSCE-S. Reference points are indicated by lines connecting these components: VAL-UU between VAL client(s) and 3GPP network system; NSCE-UU between Network slice capability enablement client and 3GPP network system; N33/N5 between 3GPP network system and Network slice capability enablement server; and NSCE-OAM between 3GPP network system and Network slice capability enablement server. A dashed horizontal line separates the VAL layer (top) from the SEAL layer (bottom). + +Figure 7.2-1: Architecture for network slice capability enablement – reference points representation. The diagram shows three main entities: VAL UE, 3GPP network system, and VAL server(s). The VAL UE contains VAL client(s) and Network slice capability enablement client. The 3GPP network system contains NSCE-OAM. The VAL server(s) contains NSCE-S. Reference points are shown as VAL-UU, NSCE-UU, N33/N5, and NSCE-OAM. A dashed line separates the VAL and SEAL layers. + +Figure 7.2-1: Architecture for network slice capability enablement – reference points representation + +The network slice capability enablement client communicates with the network slice capability enablement server over the NSCE-UU reference point. The network slice capability enablement client provides the support for network slice capability enablement functions to the VAL client(s) over NSCE-C reference point. The VAL server(s) communicates with the network slice capability enablement server over the NSCE-S reference point. It is assumed that the network slice capability enablement server is deployed at the 5G system domain. The network slice capability enablement server, acting as AF, may communicate with the 5G Core Network functions via NEF (N33) reference point (for interactions with PCF, NSACF, etc.). The network slice capability enablement server may interact with OAM system over NSCE-OAM reference point, as consumer in both NSaaS and NoP model defined in the clause 4.1.6 and clause 4.1.7 of 3GPP TS 28.530 [15] (for Network Slice Provisioning capabilities, Performance Assurance, Fault Supervision etc.). + +NOTE: OAM interfaces and/or network slice information can be exposed to an authorized (trusted) third-party (NSCE) only after a contract has been signed between the MNO and this third-party. Whether and how CAPIF/EGMF can be used to expose management services (MnS) is up to SA5 decision. + +Figure 7.2-2 illustrates the architecture for interconnection between NSCE servers. + +![Figure 7.2-2: Interconnection between NSCE servers. The diagram shows two VAL server(s) boxes at the top, separated by a dashed line labeled VAL. Below the dashed line is a SEAL layer. In the SEAL layer, there are two Network slice capability enablement server boxes, labeled 'Network slice capability enablement server 1' and 'Network slice capability enablement server 2'. Each VAL server(s) is connected to its corresponding Network slice capability enablement server via a vertical line labeled NSCE-S. The two Network slice capability enablement servers are connected to each other by a horizontal line labeled NSCE-E.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +Figure 7.2-2: Interconnection between NSCE servers. The diagram shows two VAL server(s) boxes at the top, separated by a dashed line labeled VAL. Below the dashed line is a SEAL layer. In the SEAL layer, there are two Network slice capability enablement server boxes, labeled 'Network slice capability enablement server 1' and 'Network slice capability enablement server 2'. Each VAL server(s) is connected to its corresponding Network slice capability enablement server via a vertical line labeled NSCE-S. The two Network slice capability enablement servers are connected to each other by a horizontal line labeled NSCE-E. + +**Figure 7.2-2: Interconnection between NSCE servers** + +The NSCE server could interact with another NSCE server over NSCE-E reference point. + +Figure 7.2-3 illustrates the architecture for inter-service communication between NSCE servers and other SEAL server. + +![Figure 7.2-3: Inter-service communication between NSCE server and other SEAL server. The diagram shows a VAL server(s) box at the top, separated by a dashed line labeled VAL. Below the dashed line is a SEAL layer. In the SEAL layer, there are two boxes: 'SEAL server (SEAL service a)' on the left and 'NSCE server (NSCE service)' on the right. The VAL server(s) is connected to the SEAL server (SEAL service a) via a vertical line labeled SEAL-S. The SEAL server (SEAL service a) and the NSCE server (NSCE service) are connected to each other by a horizontal line labeled SEAL-X.](552ca016af3d6240648ab5a2cad97f60_img.jpg) + +Figure 7.2-3: Inter-service communication between NSCE server and other SEAL server. The diagram shows a VAL server(s) box at the top, separated by a dashed line labeled VAL. Below the dashed line is a SEAL layer. In the SEAL layer, there are two boxes: 'SEAL server (SEAL service a)' on the left and 'NSCE server (NSCE service)' on the right. The VAL server(s) is connected to the SEAL server (SEAL service a) via a vertical line labeled SEAL-S. The SEAL server (SEAL service a) and the NSCE server (NSCE service) are connected to each other by a horizontal line labeled SEAL-X. + +**Figure 7.2-3: Inter-service communication between NSCE server and other SEAL server** + +The NSCE server interacts with another SEAL server for inter-service communication over SEAL-X reference point. + +## 7.3 Functional entities description + +### 7.3.1 General + +The functional entities for network slice capability enablement SEAL service are described in the following subclauses. + +### 7.3.2 Network slice capability enablement server + +The network slice capability enablement server functional entity provides the application layer enablement of the network slicing aspects to support the VAL applications. The network slice capability enablement server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [3]. + +### 7.3.3 Network slice capability enablement client + +The network slice capability enablement client functional entity acts as the application client for the slice enablement. The network slice capability enablement client interacts with the network slice capability enablement server to trigger network slice related operations such as adaptation due to an application requirement change. This trigger may be due to an application QoS requirement change, a service operation change. The NSCE client may receive a network slice / DNN re-mapping notification from the NSCE server. The NSCE client may optionally notify the VAL client on the network slice / DNN re-mapping. + +## 7.4 Reference points description + +### 7.4.1 General + +The reference points for the functional model for network slice capability enablement are described in the following subclauses. + +### 7.4.2 NSCE-UU + +The interactions related to network slice capability enablement functions between the network slice capability enablement server and the network slice capability enablement client are supported by NSCE-UU reference point. This reference point utilizes Uu reference point as described in 3GPP TS 23.501 [14]. + +### 7.4.3 NSCE-C + +The interactions related to network slice capability enablement functions between the VAL client(s) and the network slice capability enablement client within a VAL UE are supported by the NSCE-C reference point. The NSCE client may receive application requirement change, application client information (such as its KQI) over NSCE-C. Further, the NSCE client may provide a notification on the network slice adaptation upon successful adaptation of the slice to application mapping. + +### 7.4.4 NSCE-S + +The interactions related to network slice capability enablement functions between the VAL server(s) and the network slice capability enablement server are supported by the NSCE-S reference point. This reference point is an instance of CAPIF-2 reference point as specified in 3GPP TS 23.222 [3]. + +### 7.4.5 N33 + +The reference point N33 supports the interactions between the network slice capability enablement server and the NEF and is specified in 3GPP TS 23.501 [14]. N33 is used for the network-based mechanism for slice re-mapping, where NSCE server acting as AF influences the URSP rules for the application traffic per UE by providing a guidance on the route selection parameters (including the S-NSSAI and DNN mapping), as specified in 3GPP TS 23.502 [12] clause 4.15.6.10, 3GPP TS 23.503 [17] clause 6.6.2.2, 3GPP TS 23.548 [18] clause 6.2.4. + +### 7.4.6 NSCE-E + +The interactions between the NSCE servers are generically referred to as NSCE-E reference point. This reference point supports information collection from other NSCE servers as defined in clause 9.8, Service continuity negotiation as defined in clause 9.9.2. + +## 7.4.7 NSCE-OAM + +The interface between the NSCE server and the OAM system are generically referred to as NSCE-OAM reference point. This reference point supports provisioning of management service as defined in clause 6.1, 3GPP TS 28.531 [8]. + +NOTE: The NSCE-OAM reference point is out of scope of this specification, and is defined by SA5. + +## 7.4.8 SEAL-X + +The interactions between the NSCE servers and other SEAL servers are generically referred to as SEAL-X reference point. The specific SEAL server interactions corresponding to SEAL-X are described in 3GPP TS 23.434 [2]. + +--- + +# 8 Identities and commonly used values + +## 8.1 General + +The common identities for SEAL refer to TS 23.434[2]. The following clauses list the additional identities and commonly used values for Network Slice Capability Enablement. + +## 8.2 NSCE server ID + +The NSCE server ID uniquely identifies the Network Slice Capability enablement server. + +## 8.3 NSCE client ID + +The Network Slice Capability enablement client ID identifies a particular NSCE client. + +## 8.4 Network Slice related Identifier + +The network slice related identifier identifies the network slice, which is mapped to the VAL application. + +The identifier of the network slice is either S-NSSAI defined in 5.15.2.1 TS 23.501[16], or External Network Slice Information (ENSI) defined in TS 33.501[14]. + +Based on the operator's policy, if the service applies for a certain network slice instance, the identifier of Network Slice instance is used, i.e. NSI ID as defined in TS 23.501 or ENSI. If used, the NSI ID is associated with S-NSSAI. + +## 8.5 Slice coverage area + +The slice coverage area is the area where the network slice is available in the whole PLMN or in one or more Tracking Areas of the PLMN. The slice coverage area can be expressed as a Topological Service Area (e.g. a list of TA), a Geographical Service Area (e.g. geographical coordinates) or both. + +## 8.6 NSCE service area + +The NSCE service area is the area where the Network Slice Capability Enablement server owner provides its services. It is equal to the collection of coverage area of slices it can enable. + +The NSCE service area can be expressed as a Topological Service Area (e.g. a list of TA), a Geographical Service Area (e.g. geographical coordinates) or both. + +NOTE: The NSCE server service area shall not smaller than the collection of slice(s) coverage area(s) the NSCE server can enable. + +## 9 Procedures and information flows + +### 9.1 General + +#### 9.1.1 Common Information Elements + +##### 9.1.1.1 General + +This clause provides descriptions for Information Elements which are commonly used in several procedures. + +##### 9.1.1.2 Service requirement + +The service requirement indicates the VAL application requirements pertaining to the slice(s). + +**Table 9.1.1.2-1: Service requirement** + +| Information element | Status | Description | +|-------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL service ID | M | The identification of the application ID related with the service requirement. | +| VAL service KPIs | O | KPIs including application QoS requirements (latency, error rates, throughput, jitter,...) | +| Network slice related identifier(s) | M | Identifier of network slice for which the request applies | +| Application layer Service Profile | O | The properties of network slice related requirement. If Service Profile is known by the VAL server, it can be provided to the NSCE server. The GST defined by GSMA (see clause 2.2 in [5]) and the performance requirements defined in clause 7 TS 22.261 [6] are all considered as input for it. | +| Area of interest | O | The geographical or service area for which the requirement applies | + +## 9.2 Registration + +For registration of the VAL server to be a recognized user of the CAPIF, the VAL server triggers the CAPIF Onboarding the API invoker procedure defined in 3GPP TS 23.222[3] clause 8.1. The NSCE server could be deployed with CAPIF core function. + +NOTE: What additional information is needed, and if needed, whether it is specific for NSCE service or generally applicable for CAPIF is not specified in this release. + +For de-registration of the VAL server, the VAL server triggers the CAPIF Offboarding the API invoker procedure defined in 3GPP TS 23.222[3] clause 8.2. + +## 9.3 Slice API configuration and translation + +### 9.3.1 General + +This functionality is a service related to the translation of the service API as invoked by the end applications to slice APIs based on the API configuration and application to slice mapping. Slice APIs can be defined as customized/tailored sets of service APIs (which can be either NEF northbound APIs or OAM provided APIs or enabler layer/SEAL provided APIs) and can be mapped to particular slice instances. The slice APIs can be a bundled or combined API comprising of different types of APIs, which will be used to expose the telco (5GS/SEAL)-provided services as needed by the applications of the slice customer. Each slice API may be configured per network slice instance. + +## 9.3.2 Procedure + +### 9.3.2.1 Procedures on slice API configuration + +#### 9.3.2.1.1 General + +In the Initial Configuration procedure, the VAL server initially provides an application requirement to enabler server including the service KPIs and the subscribed/preferred slices. Then, the slice enabler configures the mapping of the VAL application to a slice API which is a combination/bundling of northbound APIs (from both management and control plane). In particular, a slice API consists of telco-provided/platform dependent service APIs (e.g., NEF, OAM, SEAL, etc), and provides an abstraction/simplification on top of them. The VAL server-initiated Configuration Update procedure covers the scenario where a trigger event occurs (e.g., QoS degradation, slice load) and the mapping configuration or the slice API configuration needed to be changed. In this scenario, the slice enabler updates the configuration of the API and provides a notification to the VAL server. + +These two procedures for the initial configuration and the configuration update are covered in 9.3.2.1 and 9.3.2.2 respectively. + +#### 9.3.2.1.2 Initial Configuration + +Figure 9.3.2.1.2-1 illustrates the procedure of the initial slice API configuration. + +Pre-conditions: + +1. The VAL server has registered to receive NSCE services. + +![Sequence diagram for Initial Slice API configuration showing interactions between VAL server, NSCE server, and SGS/SEAL service/API providers.](14515d82ffeec9475b9add3036ff26ab_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant SGS/SEAL service/API providers + + Note right of NSCE server: 2. slice API configuration, mapping to VAL application and storage + Note right of NSCE server: 3. subscription/ registration to SGS/SEAL service + + VAL server->>NSCE server: 1. VAL application requirement request + NSCE server->>VAL server: 4. VAL application requirement response + NSCE server->>VAL server: 5. slice API information notification + +``` + +The diagram illustrates the sequence of messages for the initial slice API configuration. It involves three main entities: VAL server, NSCE server, and SGS/SEAL service/API providers. The sequence starts with the VAL server sending a '1. VAL application requirement request' to the NSCE server. The NSCE server then performs internal actions: '2. slice API configuration, mapping to VAL application and storage' and '3. subscription/ registration to SGS/SEAL service'. After these, the NSCE server sends a '4. VAL application requirement response' back to the VAL server, followed by a '5. slice API information notification' to the VAL server. + +Sequence diagram for Initial Slice API configuration showing interactions between VAL server, NSCE server, and SGS/SEAL service/API providers. + +**Figure 9.3.2.1.2-1: Initial Slice API configuration** + +1. The VAL server sends a VAL application requirement request to the NSCE server. +2. The NSCE server maps the VAL application requirement to a slice API which includes a list of APIs which is needed to be consumed as part of this service capability exposure. + +The NSCE server may also store the mapping of the slice API to the service API list and per service API information (e.g. data encoding, transport technology, API protocol and versions) + +3. The NSCE server registers to consume the corresponding APIs from the 5GS (NEF and OAM) and SEAL service producers. The NSCE server registers to the following: + - to consume NEF monitoring events as specified in 3GPP TS 29.522 clause 5 e.g., network monitoring, slice status, analytics exposure, etc + - to consume PM services and KPI monitoring from OAM + +- to consume SEAL services based on 3GPP TS 23.434 +- 4. The NSCE server sends a VAL application requirement response to notify on the result of the request and indicate whether the configuration of slice API is possible or not. +- 5. The NSCE server sends the slice API information notification to the VAL server. + +### 9.3.2.1.3 VAL server-initiated Configuration Update + +Figure 9.3.2.1.3-1 illustrates the procedure of the slice API configuration updated based on a trigger event. + +Pre-conditions: + +1. Initial configuration of the slice API has been completed successfully. +2. A trigger event, which may result the need of a slice configuration change, is captured by the VAL server (application server relocation to different EDN/DN, UE mobility to different EDN, application change of behaviour). + +![Sequence diagram for Slice API configuration update. The diagram shows four steps: 1. VAL Server sends a 'VAL server-initiated configuration update request' to the NSCE server. 2. The NSCE server performs 'evaluation and slice API configuration update', shown as a self-call. 3. The NSCE server sends a 'subscription/ registration update to 5GS/SEAL services' to the 5GS/SEAL service/API providers. 4. The NSCE server sends a 'VAL server-initiated configuration update response' back to the VAL Server.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS/SEAL service/API providers + Note right of NSCE server: 2. evaluation and slice API configuration update + Note right of NSCE server: 3. subscription/ registration update to 5GS/SEAL services + VAL Server->>NSCE server: 1. VAL server-initiated configuration update request + NSCE server-->>VAL Server: 4. VAL server-initiated configuration update response + +``` + +Sequence diagram for Slice API configuration update. The diagram shows four steps: 1. VAL Server sends a 'VAL server-initiated configuration update request' to the NSCE server. 2. The NSCE server performs 'evaluation and slice API configuration update', shown as a self-call. 3. The NSCE server sends a 'subscription/ registration update to 5GS/SEAL services' to the 5GS/SEAL service/API providers. 4. The NSCE server sends a 'VAL server-initiated configuration update response' back to the VAL Server. + +**Figure 9.3.2.1.3-1: Slice API configuration update** + +1. The VAL server sends a VAL server-initiated configuration update request to the NSCE server. +2. The NSCE server processes the trigger event and checks the feasibility of such change and updates the mapping of service APIs to the slice APIs. One criterion for the update of the mapping is, if possible, to avoid changing the slice API configuration, which can be achieved by the re-mapping of the underlying service APIs +3. The NSCE server updates the subscription/registration to the underlying 5GS and SEAL service producers, if an update on the service APIs (e.g., NEF APIs, SEAL APIs, OAM provided APIs) is needed. +4. The NSCE server sends a VAL server-initiated configuration update response, containing the new slice API information, if an update has been carried out by the NSCE server. + +### 9.3.2.2 Procedure on slice API translation + +This procedure follows the 9.3.2.1 and aims to describe how the slice API invocation request is translated to service API invocations after the slice API configuration mapping. In this procedure, the NSCE server initially receives a slice API invocation request from the vertical application. Then, the NSCE server fetches the service APIs to be invoked based on the slice API configuration and performs invocation requests to the corresponding service API providers. + +Figure 9.3.2.2-1 illustrates the procedure of the slice API translation based on the initial configuration. + +Pre-conditions: + +1. The VAL server has registered to receive NSCE services. +2. The slice API mapping to the VAL server has been performed based on 9.3.2.1.2 step 2 and the slice API information is provided to the VAL server based on 9.3.2.1.2 step 5. + +![Sequence diagram for Slice API translation. Lifelines: VAL Server, NSCE server, and 5GS/SEAL service/API providers. The sequence is: 1. slice API invocation request from VAL Server to NSCE server; 2. mapping of the slice API to service APIs (based on clause 9.3.2) within NSCE server; 3. Trigger invocation requests for all service APIs of slice API within NSCE server; 4. service API invocations from NSCE server to 5GS/SEAL service/API providers; 5. slice API invocation response from NSCE server to VAL Server.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS/SEAL service/API providers + Note right of NSCE server: 2. mapping of the slice API to service APIs (based on clause 9.3.2) + Note right of NSCE server: 3. Trigger invocation requests for all service APIs of slice API + Note right of NSCE server: 4. service API invocations + VAL Server->>NSCE server: 1. slice API invocation request + NSCE server-->>VAL Server: 5. slice API invocation response + +``` + +Sequence diagram for Slice API translation. Lifelines: VAL Server, NSCE server, and 5GS/SEAL service/API providers. The sequence is: 1. slice API invocation request from VAL Server to NSCE server; 2. mapping of the slice API to service APIs (based on clause 9.3.2) within NSCE server; 3. Trigger invocation requests for all service APIs of slice API within NSCE server; 4. service API invocations from NSCE server to 5GS/SEAL service/API providers; 5. slice API invocation response from NSCE server to VAL Server. + +**Figure 9.3.2.2-1: Slice API translation** + +1. The VAL server sends a slice API invocation request to the NSCE server +2. The NSCE server checks that the user is authenticated and authorized to perform the slice API invocation and maps the requested slice API to a service APIs. If CAPIF is used, the NSCE server acts as AEF, and the authorization is obtained by CCF. +3. The NSCE server generates a trigger for service API invocation requests to all the service APIs within the slice API. +4. The NSCE server performs the corresponding service API invocation procedures based on CAPIF or via performing requests to the corresponding service API providers, which are mapped to the slice API. If CAPIF is used, the requests are sent to the corresponding AEFs of the API provider's domain, and the authorization is obtained by CCF. +5. The NSCE server sends a slice API invocation response to the VAL server, based on the result of the service API invocation response(s) of step 4. + +## 9.3.3 Information flows + +### 9.3.3.1 General + +The following information elements are specified for slice API translation and configuration specified in clause 9.3.2.1 and 9.3.2.2. + +### 9.3.3.2 VAL application requirement request + +Table 9.3.3.2-1 describes information elements for the VAL application requirement request from the VAL server to the NSCE server. + +This request provides the service requirements / KPIs, the capability exposure requirements and a preferred/subscribed slice identification (e.g., S-NSSAI or ENSI). + +**Table 9.3.3.2-1: VAL application requirement request** + +| Information element | Status | Description | +|------------------------------------|--------|-------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| List of service requirement(s) | M | The VAL application requirements pertaining to the slice(s) as defined in table 9.1.1.1-1 | +| Time validity | O | The time validity of the request | +| NOTE: One of this shall be present | | | + +### 9.3.3.3 VAL application requirement response + +Table 9.3.3.3-1 describes information elements for the VAL application requirement response from the NSCE server to the VAL server. + +**Table 9.3.3.3-1: VAL application requirement response** + +| Information element | Status | Description | +|------------------------------------------------------|-----------------|-------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the VAL application requirements request. | +| >Cause | O
(see NOTE) | Indicates the cause of failure | +| NOTE : May only be present if the result is failure. | | | + +### 9.3.3.4 Slice API information notify + +Table 9.3.3.4-1 describes information elements for the Slice API information notification from the NSCE server to the VAL server. The Slice API information notification is used by NSCE server to send Slice API information to VAL server in the Initial Configuration and Configuration Update procedures. + +**Table 9.3.3.4-1: Slice API information notify** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------| +| Slice API info | M | The information for the configured slice API | + +### 9.3.3.5 VAL server-initiated configuration update request + +Table 9.3.3.5-1 describes information elements of the VAL server-initiated configuration update request sent by the VAL server to the NSCE server. + +**Table 9.3.3.5-1: VAL server-initiated configuration update request** + +| Information element | Status | Description | +|-----------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| Network slice ID | O | Identifier of the network slice for which the API configuration update is requested | +| Trigger Event Details | M |

The trigger event details can be included, providing the cause for the need slice API configuration adaptation. Such trigger event can be:

  • - the UE mobility to a different service area (outside the original area of interest),
  • - application server migration to different edge/cloud platform,
  • - service API unavailability,
  • - VAL application QoS requirements change
| + +### 9.3.3.6 VAL server-initiated configuration update response + +Table 9.3.3.6-1 describes information elements of the VAL server-initiated configuration update response sent by the NSCE server to the VAL server. + +**Table 9.3.3.6-1: VAL server-initiated configuration update response** + +| Information element | Status | Description | +|--------------------------------------------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configuration changed | O
(see NOTE) | Indicates that the slice configuration has been changed. | +| > Updated slice API information | M | The information for the updated slice API | +| Configuration not changed | O
(see NOTE) | The trigger event details can be included, providing the cause for the need slice API configuration adaptation. Such trigger event can be | +| > Cause | M | Indicates the reason for not changing the slice configuration. The reason may be that no change was needed, failure of changing in 5GS/SEAL or other (e.g. server internal error). | +| NOTE: Only one of these IEs is present in the message. | | | + +### 9.3.3.7 slice API invocation request + +Table 9.3.3.7-1 describes information elements for the slice API invocation request from the VAL server to the NSCE server. + +**Table 9.3.3.7-1: slice API invocation request** + +| Information element | Status | Description | +|---------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| Authorization information | O | The authorization information obtained before initiating the slice API invocation request | +| Slice API identification | M | The identification information of the slice API for which invocation is requested. The slice API identification is part of the specific slice API invocation request. | + +### 9.3.3.8 slice API invocation response + +Table 9.3.3.8-1 describes information elements for the slice API invocation response from the NSCE server to the VAL server. + +**Table 9.3.3.8-1: slice API invocation response** + +| Information element | Status | Description | +|-----------------------------------------------------|-----------------|-------------------------------------------------------------------| +| Result | M | Indicates the success or failure of slice API invocation request. | +| >Cause | O
(see NOTE) | Indicates the cause of failure | +| NOTE: May only be present if the result is failure. | | | + +## 9.3.4 APIs + +### 9.3.4.1 General + +Table 9.3.4.1-1 illustrates the NSCE APIs for the slice API configuration and translation feature. + +**Table 9.3.4.1-1: List of APIs for slice API configuration and translation feature** + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|-------------------------------|--------------------------------|-------------------|--------------------| +| SS_NSCE_SliceApiConfiguration | Slice_API_configuration | VAL server | Request /Response | +| | Slice_API_configuration_update | VAL server | Request /Response | +| | Slice_API_information_notify | VAL server | Notify | +| SS_NSCE_Slice_ApiInvocation | Slice_API_invocation | VAL server | Request /Response | + +### 9.3.4.2 SS\_NSCE\_SliceApiConfiguration API + +#### 9.3.4.2.1 General + +**API description:** This API enables the VAL server to communicate with the NSCE server for the initial configuration of the slice API and possible subsequent slice API configuration update(s). + +#### 9.3.4.2.2 SS\_NSCE\_Slice\_API\_configuration + +**API operation name:** Slice\_API\_configuration + +**Description:** Providing for VAL\_Application\_requirement to the NSCE server. + +**Known Consumers:** VAL server + +**Inputs:** See subclause 9.3.3.2 + +**Outputs:** See subclause 9.3.3.3 + +#### 9.3.4.2.3 SS\_NSCE\_Slice\_API\_configuration\_update + +**API operation name:** Slice\_API\_configuration\_update + +**Description:** VAL server providing trigger event information to the NSCE server that may potentially invoke slice API configuration change(s). + +**Known Consumers:** VAL server + +**Inputs:** See subclause 9.3.3.5 + +**Outputs:** See subclause 9.3.3.6 + +#### 9.3.4.2.4 SS\_NSCE\_Slice\_API\_information\_notify + +**API operation name:** Slice\_API\_information\_notify + +**Description:** Notifying the slice API information + +**Known Consumers:** VAL server + +**Inputs:** None + +**Outputs:** See subclause 9.3.3.4 + +### 9.3.4.3 SS\_NSCE\_Slice\_ApiInvocation API + +#### 9.3.4.3.1 General + +**API description:** This API enables the VAL server to communicate with the NSCE server for invoking the slice API over NSCE-S. + +#### 9.3.4.3.2 SS\_NSCE\_Slice\_API\_invocation + +**API operation name:** Slice\_API\_invocation + +**Description:** Requesting slice API invocation from NSCE server. + +**Known Consumers:** VAL server + +**Inputs:** See subclause 9.3.3.7 + +**Outputs:** See subclause 9.3.3.8 + +## 9.4 Application layer network slice lifecycle management + +### 9.4.1 General + +When NSCE receives a request for application layer network slice lifecycle management (AppLayer\_NS\_LCM) from VAL server, the NSCE server performs the service operations including subscribing the event which may trigger the management system to do the network slice lifecycle management, making the network slice lifecycle management recommendation/decision, triggering the network slice lifecycle management operations, notifying the consumer about the network slice information. + +### 9.4.2 Procedure + +#### 9.4.2.1 Procedures on slice lifecycle management + +Figure 9.4.2.1-1 illustrates a procedure of application layer network slice lifecycle management based on network slice related data and QoE collected from application layer. + +Pre-conditions: + +1. The NSCE server has authenticated and authorized to the capabilities to collect current network slice from 5GS. +2. The NSCE server has authenticated and authorized to the capabilities trigger the network slice LCM operations. +3. There is signed contract for LCM between the entities using VAL server and entities using NSCE. + +![Sequence diagram for Application layer network slice lifecycle management. Lifelines: VAL server, network slice capability enablement server, and 5GS/OAM. The sequence starts with a subscribe request from VAL server to NSCE server. NSCE server performs authentication and determines operations. It then triggers the provision of network slice status or QoE. VAL server can subscribe to QoE metrics. NSCE server sends a response. It then processes the status and makes recommendations. VAL server sends a request for these recommendations. NSCE server responds. Finally, NSCE server triggers the actual lifecycle management operations and notifies the VAL server.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server as network slice capability enablement server + participant 5GS/OAM + + Note right of NSCE server: 2. Authentication and authorization and Network slice lifecycle management operation determination + Note right of NSCE server: 3. Trigger for providing the network slice status or QoE + Note right of NSCE server: 5. Network slice status or QoE process and Network slice lifecycle management recommendation + Note right of NSCE server: 8. Trigger Network slice lifecycle management operation(s) + + VAL server->>NSCE server: 1. AppLayer_NS_LCM subscribe request + NSCE server-->>VAL server: 4. AppLayer_NS_LCM response + NSCE server-->>VAL server: 7. Network slice lifecycle management recommendation response + NSCE server-->>VAL server: 9. AppLayer_NS_LCM notification + + VAL server-->>NSCE server: 3b. QoE metrics subscribe and response + NSCE server-->>5GS/OAM: 3a. network slice status + +``` + +Sequence diagram for Application layer network slice lifecycle management. Lifelines: VAL server, network slice capability enablement server, and 5GS/OAM. The sequence starts with a subscribe request from VAL server to NSCE server. NSCE server performs authentication and determines operations. It then triggers the provision of network slice status or QoE. VAL server can subscribe to QoE metrics. NSCE server sends a response. It then processes the status and makes recommendations. VAL server sends a request for these recommendations. NSCE server responds. Finally, NSCE server triggers the actual lifecycle management operations and notifies the VAL server. + +**Figure 9.4.2.1-1: Application layer network slice lifecycle management** + +1. The VAL server sends the application layer network slice lifecycle management (AppLayer-NS-LCM) subscribe request to NSCE server, with network slice requirements from VAL server/consumer (e.g. delay, throughput, load, the maximum number of users supported, etc.). The request can indicate whether the notification is needed before performing the AppLayer-NS-LCM. The request can also indicate the trigger conditions, such as by providing the monitored parameters and the corresponding thresholds as described in clause 9.4.3.2. +2. After receiving the request, the NSCE server checks that the user is authenticated and authorized to perform the corresponding AppLayer-NS-LCM operations, and filters the unauthorized requests, if any. +3. According to network slice requirements and/or the trigger conditions, NSCE server triggers the provision of network slice status and QoE metrics. If the trigger conditions are not indicated in the subscription, the NSCE server can help to configure an appropriate trigger condition, such as report period or thresholds. + - 3a. The network slice status could be collected through subscribing or requesting to 5GS. List of network slice status parameters to be collected are: + - Network Slice load statistics information, and/or Network Slice load predictions information from NWDAF/NEF as defined in TS 23.288 Table 6.3.3A. + - Performance metric in the performance data file from OAM as defined in clause 11.3 of TS 28.532 [7]. + - 3b. Also, the NSCE server could get the information of QoE metrics from the application layer domain by QoE metric subscribe as described in clause 9.4.3.5. +4. Once authenticated and authorized, the NSCE server sends the AppLayer-NS-LCM response to the VAL server. +5. The NSCE server may process and combine the collected network slice status and QoE metrics, if needed. The NSCE server may process and combine the parameters in the trigger conditions, if multiple trigger conditions were provided. Once the trigger condition or the combination of trigger conditions are met which indicating the network slice requirements from VAL server is not satisfied, the NSCE server determines whether and what network slice LCM operations should be taken based on requirements from VAL server/consumer and network slice status and QoE metrics, and makes the decision(s)/recommendation(s), such as modifyNsi/AllocateNsi/DeallocateNsi request as specified in TS 28.531 [8]. + +6. Optionally, if it is indicated in the request to notify the VAL server/consumer before performing the AppLayer-NS-LCM, the NSCE sends the network slice LCM recommendation(s) with network slice information to VAL server, to see whether takes the recommendation(s) or not. +7. Optionally, the VAL server sends the response to NSCE server. +8. Based on decision made by VAL server or NSCE server, the NSCE server sends the network slice LCM request to the OAM. +9. According to the corresponding operation(s) result, the NSCE server sends the response to the VAL server. + +### 9.4.3 Information flows + +#### 9.4.3.1 General + +The following information flows are specified for AppLayer\_NS\_LCM: + +- AppLayer\_NS\_LCM subscribe, response and notification; +- QoE metrics subscribe, response and notification; +- Network slice LCM recommendation request and response; + +#### 9.4.3.2 Application layer network slice lifecycle management subscribe request + +Table 9.4.3.2-1 describes information elements for the application layer network slice lifecycle management subscribe request from the VAL server to the NSCE server. + +**Table 9.4.3.2-1: AppLayer-NS-LCM Subscribe** + +| Information element | Status | Description | +|--------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. VAL server ID). | +| Security credentials | M | Security credentials resulting from a successful authorization for the NSCE service. | +| Service requirement | M | The VAL application requirements pertaining to the slice as defined in table 9.1.1.1-1 | +| AppLayer-NS-LCM notification indication | M | Indicates whether to notify the VAL server/consumer about the AppLayer-NS-LCM | +| >AppLayer-NS-LCM notification address (see NOTE) | O | The address (e.g. URL) of the consumer that can receive the AppLayer-NS-LCM notification | +| Trigger condition | O | Indicates the monitored parameters and the corresponding thresholds which could trigger the AppLayer-NS-LCM.
The supported trigger conditions are:
- The Network Slice load exceeds the threshold.
- The collected Network Slice performance exceeds the threshold;
- The collected QoE exceeds the threshold. | +| Proposed expiration time | O | Proposed expiration time for the subscription | +| NOTE: | | When the AppLayer-NS-LCM recommendation notification is needed, AppLayer-NS-LCM notification indication should be provided. | + +#### 9.4.3.3 Application layer network slice lifecycle management response + +The information elements specified in the Table 9.4.3.3-1 is used for the application layer network slice lifecycle management response sent from the NSCE server to the VAL server. + +**Table 9.4.3.3-1: AppLayer-NS-LCM Response** + +| Information element | Status | Description | +|-----------------------------------------------------|-----------------|--------------------------------------------------------| +| Result | M | Indicates that the success or failure. | +| > Cause | O
(see NOTE) | Indicates the cause of AppLayer-NS-LCM request failure | +| NOTE: May only be present if the result is failure. | | | + +#### 9.4.3.4 Application layer network slice lifecycle management notification + +The information elements specified in the Table 9.4.3.4-1 is used for the application layer network slice lifecycle management notification sent from the NSCE server to the VAL server. + +**Table 9.4.3.4-1: AppLayer-NS-LCM Notification** + +| Information element | Status | Description | +|---------------------------------------------------------|--------|-----------------------------------------------------------------------------------| +| Successful response (see NOTE) | O | Indicates that the AppLayer-NS-LCM request was successful. | +| >network slice information | M | Network slice information (i.e. NEST) with network slice identifier(i.e. S-NSSAI) | +| Failure response (see NOTE) | O | Indicates that the AppLayer-NS-LCM request failed. | +| > Cause | O | Indicates the cause of AppLayer-NS-LCM request failure | +| NOTE: One of these IEs shall be present in the message. | | | + +#### 9.4.3.5 QoE metrics subscribe + +Table 9.4.3.5-1 describes information elements for the QoE metrics subscribe from the NSCE server to the VAL server. + +**Table 9.4.3.5-1: QoE metrics Subscribe** + +| Information element | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. NSCE server ID). | +| Security credentials | M | Security credentials resulting from a successful authorization. | +| Notification Target Address | O | The Notification Target Address (e.g. URL) where the notifications destined for the requestor should be sent to. | +| Subscription ID | M | Identifier of the subscription. | +| Event Filter | M | The associated filter on a network slice to be notified | +| > Network slice related Identifier(s) | M | Identifier of the interested network slice | +| > VAL service ID | O | Indicator of the interested application (i.e. App ID) | +| >QoE type indicator | M | QoE metric type including latency, throughput, jitter, etc. | +| Event Reporting information | M | Information indicates how the notification is supposed to be sent, threshold based or the notification is periodical or the Immediate reporting is requested | +| >Threshold | O | Threshold of QoE metrics | +| >Reporting period | O | Indicating the metrics reporting period | +| >Immediate reporting flag | O | Indicating the request needs immediate reporting or not | +| Proposed expiration time | O | Proposed expiration time for the subscribe | + +### 9.4.3.6 QoE metrics response + +Table 9.4.3.6-1 describes the information elements for the QoE metrics response from the VAL server to the NSCE server. + +**Table 9.4.3.6-1: QoE metrics Response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the QoE metrics request. | +| > Subscription ID | O
(see NOTE1) | Subscription identifier corresponding to the subscription. | +| >QoE metrics report | O
(see NOTE2) | List of result values for the observed or computed QoE metrics value if the immediate reporting is needed. | +| > Cause | O
(see NOTE3) | Indicates the cause of QoE metrics request failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: May only be present if the result is success.
NOTE 3: May only be present if the result is failure. | | | + +### 9.4.3.7 QoE metrics notification + +Table 9.4.3.7-1 describes the information elements for the QoE metrics notification from the VAL server to the NSCE server. + +**Table 9.4.3.7-1: QoE metrics Notify** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| Subscription ID | M | Indicates that the QoE metrics request was successful. | +| QoE metrics report | M | List of result values for the observed or computed QoE metrics value. | + +### 9.4.3.8 Network slice LCM recommendation request + +Table 9.4.3.8-1 describes information elements for the Network slice LCM recommendation request from the NSCE server to the VAL server. + +**Table 9.4.3.8-1: Network slice LCM recommendation Request** + +| Information element | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. NSCE server ID). | +| Security credentials | M | Security credentials resulting from a successful authorization. | +| Network slice LCM recommendation | M | Recommended network slice lifecycle management operation | +| > Network slice related Identifier(s) | M | Identifier of the network slice | +| >Recommend network slice LCM action | M | Recommend network slice LCM action(i.e. modifying the configuration, allocating a network slice) | +| >Network slice information | O | Network slice information if the action is taken(i.e. NEST) | + +### 9.4.3.9 Network slice LCM recommendation response + +Table 9.4.3.9-1 describes the information elements for the Network slice LCM recommendation response from the VAL server to the NSCE server. + +**Table 9.4.3.9-1: Network slice LCM recommendation Response** + +| Information element | Status | Description | +|-----------------------------------------------------|-----------------|----------------------------------------------------------------------------------| +| Result | M | Indicates that the Network slice LCM recommendation request was accepted or not. | +| > Cause | O
(see NOTE) | Indicates the cause of failure. | +| NOTE: May only be present if the result is failure. | | | + +## 9.4.4 APIs + +### 9.4.4.1 General + +Table 9.4.4.1-1 illustrates the API for application layer network slice lifecycle management. + +**Table 9.4.4.1-1: API for application layer network slice lifecycle management** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|---------------------------------|----------------|---------------------|-------------| +| SS_NSCE_AppLayerNSLCM | Subscribe | Subscribe/Response | VAL server | +| | Notify | Notify | VAL server | +| SS_NSCE_Val_QoEMetrics | Subscribe | Subscribe/Response | NSCE | +| | Notify | Notify | NSCE | +| SS_NSCE_Val_NSLCMRecommendation | Subscribe | Subscribe/Response | NSCE | + +### 9.4.4.2 SS\_NSCE\_AppLayerNSLCM\_Subscribe operation + +**API operation name:** AppLayerNSLCM\_Request + +**Description:** The consumer subscribes for AppLayer\_NS\_LCM. + +**Inputs:** See clause 9.4.3.2. + +**Outputs:** See clause 9.4.3.3. + +See clause 9.4.2 for details of usage of this operation. + +### 9.4.4.3 SS\_NSCE\_AppLayerNSLCM\_Notify operation + +**API operation name:** AppLayerNSLCM\_Notify + +**Description:** The consumer is notified with result of AppLayer\_NS\_LCM. + +**Inputs:** See clause 9.4.3.4. + +**Outputs:** None + +See clause 9.4.2 for details of usage of this operation. + +### 9.4.4.4 SS\_NSCE\_Val\_QoEMetrics\_Subscribe operation + +**API operation name:** QoEMetrics\_Subscribe + +**Description:** The consumer subscribes for the QoE metrics. + +**Inputs:** See clause 9.4.3.5. + +**Outputs:** See clause 9.4.3.6. + +See clause 9.4.2 for details of usage of this operation. + +#### 9.4.4.5 SS\_NSCE\_Val\_QoEMetrics\_Notify operation + +**API operation name:** QoEMetrics\_Notify + +**Description:** The consumer is notified with the QoE metrics. + +**Inputs:** See clause 9.4.3.7. + +**Outputs:** None + +See clause 9.4.2 for details of usage of this operation. + +#### 9.4.4.6 SS\_NSCE\_Val\_NSLCMRecommendation\_Request operation + +**API operation name:** NSLCMRecommendation\_Request + +**Description:** The consumer request for whether to take the recommendation of the AppLayer\_NS\_LCM. + +**Inputs:** See clause 9.4.3.8. + +**Outputs:** See clause 9.4.3.9. + +See clause 9.4.2 for details of usage of this operation. + +### 9.5 Network slice optimization based on VAL server policy + +#### 9.5.1 General + +Based on policy from the vertical applications (e.g., to trigger some network slice operations when the pre-configured thresholds are met), the network slice parameters for the vertical applications could be optimized by triggering the slice modification. The slice optimization can be triggered by OAM, data/prediction retrieved from NWDAF via NEF, and NSCE server itself as describe in 9.5.2.2. + +#### 9.5.2 Procedure + +##### 9.5.2.1 VAL server policy management + +###### 9.5.2.1.1 VAL server policy provisioning + +Figure 9.5.2.1.1 illustrates the procedure of VAL server policy provisioning from the VAL server to the NSCE server. + +Pre-conditions: + +1. The NSCE server has information about the existing slice/slice profile/slice services which VAL server is using. + +![Sequence diagram illustrating VAL server policy provisioning. The diagram shows two lifelines: VAL server and NSCE server. The sequence of messages is: 1. VAL server sends a 'VAL server policy provisioning request' to NSCE server. 2. NSCE server performs a 'VAL server policy check' (shown in a box). 3. NSCE server performs 'policy harmonization' (shown in a dashed box). 4. NSCE server sends a 'VAL server policy provisioning response' back to VAL server.](d0703aa3d4cb275167aff5263eccd7b7_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server + Note right of NSCE server: 2.VAL server policy check + Note right of NSCE server: 3.policy harmonization + VAL server->>NSCE server: 1. VAL server policy provisioning request + NSCE server-->>VAL server: 4. VAL server policy provisioning response +``` + +Sequence diagram illustrating VAL server policy provisioning. The diagram shows two lifelines: VAL server and NSCE server. The sequence of messages is: 1. VAL server sends a 'VAL server policy provisioning request' to NSCE server. 2. NSCE server performs a 'VAL server policy check' (shown in a box). 3. NSCE server performs 'policy harmonization' (shown in a dashed box). 4. NSCE server sends a 'VAL server policy provisioning response' back to VAL server. + +Figure 9.5.2.1.1: VAL server policy provisioning + +1. VAL server sends VAL server policy provisioning request to NSCE server. The request contains the policy, VAL server ID, Default policy indication, and S-NSSAI. Optionally, the request contains the indicator of policy harmonization. + +The VAL server can request the NSCE server to mark the provisioned policy as the default policy using the Default policy indication. The default policy should serve as a VAL server policy for the slices provisioned without any policy. Either the policy or default policy indication can be provided by the VAL server. + +The VAL server policy is in form of a policy profile which contains list of trigger events associated with the parameters and expected actions. It contains priority and scheduling information with pre-emption capability for the policies. The scheduling information schedules the policy by defining the schedule (start and end time) for the policy. The pre-emption capability provides another, already successfully provisioned policy to pre-empt the scheduled policy in the scheduled period. + +The supported policies are: + +- Based on monitored performance metric from OAM, when the max number of PDU sessions or max number of UE is reached, trigger the slice modification with expected parameters. + - Based on monitored Network Slice load from NSACF, when the number of PDU sessions or number of UE exceeds the threshold, trigger the slice modification with expected parameters. + - Based on monitored Network Slice load predictions from NWDAF, when Network Slice load predictions (Predicted Number of PDU Session establishments at the Network Slice) exceeds the threshold with high confidence, trigger the slice modification with expected parameters. + - Based on the monitored the time period, when getting to a certain time period (e.g. summer vacation, spring festival etc.), trigger the slice modification with expected parameters. + - Based on the monitored time period, when getting to a certain time period, trigger the slice modification based on the expected QoS per UE. QoS is mapped/calculated by NSCE to specific parameters of the slice such as the dLThptPerUE, uLThptPerUE, dLThptPerSliceSubnet, uLThptPerSliceSubnet, delayTolerance, dLLatency, uLLatency. +2. The NSCE server checks whether the policy is conflict with the MNO policies or NSPP. One criterion is to translate the network slice parameters in the service profile to see whether it is conflict with that in the VAL provided policy. If policy harmonization is not requested and policies conflict then the request could be rejected. The NSCE server also checks the validity of the policy (policy is valid for the specified time period or until the specified threshold count of trigger events is achieved) to avoid a ping-pong effect of slice modification. If the policy is invalid, the request could be rejected. + 3. If the policy harmonization is requested, the NSCE server can harmonize the policy as per clause 9.5.2.1.4 and this may result in the changes to the current VAL server policy under provisioning. + 4. NSCE server sends the VAL server policy provisioning response to the VAL server to indicate whether the request is successful or not. If it is successful, policy ID is provided to VAL server. + +#### 9.5.2.1.2 VAL server policy Update + +Figure 9.5.2.1.2-1 illustrates the VAL server policy update procedure. + +Pre-conditions: + +1. The NSCE server has information about the existing slice/slice profile/slice services that the VAL server is using. +2. The VAL server has created policies in NSCE server using the procedure defined in clause 9.5.2.1.1. + +![Sequence diagram for VAL server policy update](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server + Note right of NSCE server: 2. policy check + Note right of NSCE server: 3. policy harmonization + VAL server->>NSCE server: 1. VAL server policy update request + NSCE server-->>VAL server: 4. VAL server policy update response +``` + +The diagram illustrates the interaction between a VAL server and an NSCE server for a policy update. The VAL server sends a 'VAL server policy update request' (1) to the NSCE server. The NSCE server performs a 'policy check' (2) and 'policy harmonization' (3). Finally, the NSCE server sends a 'VAL server policy update response' (4) back to the VAL server. + +Sequence diagram for VAL server policy update + +**Figure 9.5.2.1.2-1: VAL server policy update** + +1. VAL server sends VAL server policy update request to NSCE server. The request shall contain the policy ID and policy modification details for updating the policy in the NSCE server. The request can update the existing default policy or specify a new default policy for the mentioned slice in the request. The policy update procedure can update the scheduling and pre-emption information for the policy. +2. The NSCE server checks whether the policy is conflict with the MNO policies or NSPP. +3. If authorized, the NSCE server can harmonize the policy as per clause 9.5.2.1.4 and this may result in the changes to the current VAL server policy under update process. +4. If the VAL server is authorized to update the VAL server policy, the NSCE server checks the modification with existing policies to avoid conflict and provides the response to the VAL server. + +#### 9.5.2.1.3 VAL server policy Delete + +Figure 9.5.2.1.3-1 illustrates the VAL server policy delete procedure. + +Pre-conditions: + +1. The NSCE server has information about the existing slice/slice profile/slice services that the VAL server is using. +2. The VAL server has created one or more policies in NSCE server using the procedure defined in clause 9.5.2.1.1. + +![Sequence diagram for VAL server policy delete](257c8341b41f1f4a287f27d33227974c_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server + VAL server->>NSCE server: 1. VAL server policy delete request + NSCE server-->>VAL server: 2. VAL server policy delete response +``` + +The diagram illustrates the interaction between a VAL server and an NSCE server for a policy delete. The VAL server sends a 'VAL server policy delete request' (1) to the NSCE server. The NSCE server then sends a 'VAL server policy delete response' (2) back to the VAL server. + +Sequence diagram for VAL server policy delete + +**Figure 9.5.2.1.3-1: VAL server policy delete** + +1. VAL server sends VAL server policy delete request to NSCE server. The request contains the policy ID, and optionally default policy indication. The default policy indicates the update of the default policy in the case of a delete request for the default policy. The policy delete procedure can be used to delete one or more policies. +2. If the VAL server is authorized to delete the VAL server policy, the NSCE server deletes the policy. In the case of a default policy delete request, the NSCE server first updates the default policy with the policy mentioned in the delete request and then deletes the old default policy. The NSCE server reports the outcome of the deletion of the requested policy with policy ID and priority for the new default policy. + +#### 9.5.2.1.4 Policy harmonization + +Policy harmonization is to make sure the VAL server Policy (from VAL Provider/ slice customer/ASP) is compatible with the MNO policies and NSCE service provider policy for the same service or slice. The policy harmonization could be requested through the policy provisioning/update service. + +Figure 9.5.2.1.4-1 illustrates the procedure for policy harmonization. + +Pre-conditions: + +1. The NSCE service provider policy (NSPP) and MNO policy is available at the NSCE Server. +2. The VAL server is authorized to receive NSCE services. + +![Sequence diagram for Policy harmonization](f1091147d93cee4dfa88498610e395a7_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server + Note right of NSCE server: 1. Trigger of policy harmonization + Note right of NSCE server: 2. determine the parameters harmonizing the policy + NSCE server->>VAL server: 3. Policy harmonization notification +``` + +The diagram shows a sequence of three steps between the VAL server and the NSCE server. Step 1, 'Trigger of policy harmonization', occurs at the NSCE server. Step 2, 'determine the parameters harmonizing the policy', also occurs at the NSCE server. Step 3, 'Policy harmonization notification', is a message sent from the NSCE server to the VAL server. + +Sequence diagram for Policy harmonization + +**Figure 9.5.2.1.4-1: Policy harmonization** + +1. When receiving the policy provisioning, or policy update request, and the result of policy check turn out the policy is conflict, the policy harmonization is triggered. +2. The NSCE server determines parameters harmonizing the policy, if previously authorized. +3. NSCE server sends the VAL server a notification providing parameters values that allow the policies to be harmonized. Then the VAL server would decide whether to accept the provided optional parameters values. If they are accepted, the VAL server may invoke VAL server policy provisioning/ VAL server policy update procedure defined in clause 9.5.2.1.1, 9.5.2.1.2 with harmonized parameters values. + +#### 9.5.2.1.5 VAL server policy Usage Reporting data + +Figure 9.5.2.1.5-1 illustrates the VAL server policy usage reporting data procedure. + +Pre-conditions: + +1. The NSCE server has information about the existing slice/slice profile/slice services which VAL server is using. +2. The VAL server has created one or more policies using in the NSCE server the procedure defined in clause 9.5.2.1.1. + +![Sequence diagram for VAL server policy usage reporting data](61d6d7aae4cc4d0310bdf9ec29e221c5_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server + VAL server->>NSCE server: 1. VAL server policy usage reporting data subscribe request + NSCE server-->>VAL server: 2. VAL server policy usage reporting data subscribe response + NSCE server-->>VAL server: 3. VAL server policy usage reporting data notification +``` + +The diagram shows a sequence of three steps between the VAL server and the NSCE server. Step 1, 'VAL server policy usage reporting data subscribe request', is sent from the VAL server to the NSCE server. Step 2, 'VAL server policy usage reporting data subscribe response', is sent from the NSCE server back to the VAL server. Step 3, 'VAL server policy usage reporting data notification', is sent from the NSCE server to the VAL server. + +Sequence diagram for VAL server policy usage reporting data + +**Figure 9.5.2.1.5-1: VAL server policy usage reporting data** + +1. VAL server sends VAL server policy usage reporting data subscribe request to NSCE server. The request contains the policy ID, reporting interval, and the required duration of the data. + +2. The NSCE server responds with a VAL server policy usage reporting data subscribe response message indicating the success or failure of the subscription. +3. The NSCE server reports the policy reporting data containing the number of times the policy has been used and the duration for which the policy was active in the requested duration and details of the preemption of policies. The reporting interval enables the periodic reporting of the requested report. + +### 9.5.2.2 Network slice optimization based on VAL server policy + +Figure 9.5.2.2-1 illustrates the procedure of network slice optimization based on VAL server policy. + +Pre-conditions: + +1. The NSCE server is authorized to get network slice management data notification from OAM, and/or NWDAF via NEF. +2. The VAL server is authorized to the NSCE server for network slice optimization. +3. There is enough network capacity when the expected action is to expand the network slice. +4. The VAL server policy has been pre-configured on the VAL server. +5. The VAL server policy has been provided to the NSCE server as specified in clause 9.5.2.1. + +![Sequence diagram for Network slice optimization based on VAL server policy. The diagram shows four lifelines: VAL server, NSCE server, 5GC, and OAM. The sequence of messages is: 1. Network slice optimization subscription request from VAL server to NSCE server; 2. event subscribe from NSCE server to 5GC and OAM; 3. Network slice optimization subscription response from NSCE server to VAL server; 4. Slice modification from 5GC to OAM; 5. Network slice optimization notification from NSCE server to VAL server.](132cff7e872feb31f629703959beddd7_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant 5GC + participant OAM + Note left of VAL server: 1. Network slice optimization subscription request + VAL server->>NSCE server: 1. Network slice optimization subscription request + Note right of NSCE server: 2. event subscribe + NSCE server->>5GC: 2. event subscribe + NSCE server->>OAM: 2. event subscribe + Note left of VAL server: 3. Network slice optimization subscription response + NSCE server->>VAL server: 3. Network slice optimization subscription response + Note right of 5GC: 4. Slice modification + 5GC->>OAM: 4. Slice modification + Note left of VAL server: 5. Network slice optimization notification + NSCE server->>VAL server: 5. Network slice optimization notification + +``` + +Sequence diagram for Network slice optimization based on VAL server policy. The diagram shows four lifelines: VAL server, NSCE server, 5GC, and OAM. The sequence of messages is: 1. Network slice optimization subscription request from VAL server to NSCE server; 2. event subscribe from NSCE server to 5GC and OAM; 3. Network slice optimization subscription response from NSCE server to VAL server; 4. Slice modification from 5GC to OAM; 5. Network slice optimization notification from NSCE server to VAL server. + +**Figure 9.5.2.2-1: Network slice optimization based on VAL server policy** + +1. VAL server sends network slice optimization subscription request to NSCE server. The request contains the policy ID indicating the different policies. Optionally the request contains the Secondary policy ID indicating the fallback policy to be used for the failed network slice optimization. The NSCE server retries the network slice optimization using a Secondary policy in the case of a failed optimization. +2. The NSCE server translates the trigger event to service API(s) with necessary parameters, and subscribe to the related service if needed. + - To get the monitored performance metric from OAM, the notifyThresholdCrossing as defined in TS 28.532[7] clause 11.3.1.3 which is filled in with corresponding S-NSSAI in objectInstance could be used. + - To obtain the Network Slice load predictions from NWDAF, the NSCE server subscribes to the NWDAF prediction by invoking Nnef\_AnalyticsExposure\_Subscribe or Nnef\_AnalyticsExposure\_Fetch as defined in TS 23.288[4] clauses 6.1.1.2, and 6.1.1.2. + - To monitor the Network Slice load (e.g. the number of UEs or the number of PDU Sessions) from NSACF, the NSCE server subscribes to the NSACF by using the Nnef\_EventExposure\_Subscribe Request or Nnsacf\_SliceEventExposure\_Subscribe\_Request as defined in clause 4.15.3.2.10 of TS 23.502 [12], and the APIs defined in clause 6.2 of TS 29.536 [13] can be utilized. + - To monitor the time period, the NSCE server setup the timer. + +3. NSCE server sends the network slice optimization subscription response to the VAL server to confirm the subscription of network slice optimization. +4. Upon receiving the notification which indicating the trigger event is met, i.e., the monitored information reaches the threshold or specific time period is arrived, the NSCE server performs the expected action by triggering the slice modification as specified in the VAL server policy. The network slice modification could be triggered by consuming the Network Slice Provisioning service with the modifyMOIAttributes operation as specified in TS 28.531 [8]. The OAM responds back to NSCE server that the requested slice modification was successful or not. The slice modification requests contain the parameters need to be updated to fit the requirement of network slice (e.g., scale in or scale out the network slice capability), including at least one of the following, uLThptPerSlice, dLThptPerSlice, dLThptPerUE, uLThptPerUE, dLThptPerSliceSubnet, uLThptPerSliceSubnet, delayTolerance, dLLatency, uLLatency, maximum number of UEs, maximum number of PDU session as specified in TS 28.541 [10]. + +NOTE 1: The slice modification could be done by application layer network slice lifecycle management as defined in clause 9.4. + +5. The NSCE server provides a network slice optimization notification to the VAL server. The successful response optionally includes the Optimization time and the Enforced policy ID. The optimization time indicates the time the NSCE server has taken to optimize the slice. The Enforced policy ID indicates which secondary policy is used by the NSCE server for slice optimization in the case of a failed attempt for network slice optimization. + +NOTE 2: There is no expectation to have constant and exact mapping between slice configuration parameters and actual traffic load of the same slice. + +### 9.5.2.3 Network slice optimization report retrieval + +Figure 9.5.2.3-1 illustrates the Network slice optimization report retrieval procedure. + +Pre-conditions: + +1. The NSCE server has information about the existing slice/slice profile/slice services that the VAL server is using. +2. The VAL server has the created policies using the procedure defined in clause 9.5.2.1.1. +3. The VAL server has subscribed for the network slice optimization using the procedure defined in clause 9.5.2.2. + +![Sequence diagram showing Network slice optimization report retrieval between VAL Server and NSCE Server.](e97d663314aff9c29bf8971323e6539e_img.jpg) + +``` +sequenceDiagram + participant VAL Server + participant NSCE Server + Note left of VAL Server: Pre-conditions: 1. NSCE has info about slice/profile/services. 2. VAL has created policies. 3. VAL has subscribed for optimization. + VAL Server->>NSCE Server: 1. Network slice optimization report retrieval request + NSCE Server-->>VAL Server: 2. Network slice optimization report retrieval response +``` + +Sequence diagram showing Network slice optimization report retrieval between VAL Server and NSCE Server. + +**Figure 9.5.2.3-1: Network slice optimization report retrieval** + +1. The VAL server sends a Network slice optimization report request to the NSCE server. The request shall contain the subscription ID, optimization result window, and optional elements like optimization result filters, sorting rules, and result size. The VAL server creates a filter using the optimization result filter for the NSCE server requesting filtered successful or failed responses. The VAL server can create additional sorting rules for the NSCE server to request sorted results based on optimization time or policy ID or slice optimization event time in ascending or descending order. The result size indicates the number of results or responses for the report. +2. The NSCE server provides the report to the VAL server as per the request of the VAL server containing optimization response, optimization time, policy ID, and Enforced Policy information. + +## 9.5.3 Information flows + +### 9.5.3.1 General + +The following information flows are specified: + +- VAL server policy provisioning request and response; +- Network slice optimization subscription, response and notification; +- VAL server policy update request and response; +- VAL server policy delete request and response; +- VAL server policy usage reporting data subscribe request, response, and notification; and +- Network slice optimization report retrieval request and response. +- Policy harmonization notify. + +### 9.5.3.2 VAL server policy provisioning request + +Table 9.5.3.2-1 describes information elements for the VAL server policy provisioning request from the VAL server to the NSCE server. + +**Table 9.5.3.2-1: VAL server policy provisioning Request** + +| Information element | Status | Description | +|-------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. VAL server ID). | +| Security credentials | M | Security credentials resulting from a successful authorization. | +| Network slice related Identifier(s) | O | Identifier of the network slice. | +| Requested DNN | O | Indication of the DNN which is requested. | +| Indicator of policy harmonization | O | Indicating whether the policy harmonization is requested. | +| Policy | O | The policy profile is defined in Table 9.5.3.2-2. The supported VAL server policies are listed in Table 9.5.3.2-3 to Table 9.5.3.2-5. | +| Default policy indication | O | Indicates the policy in the request to mark as a default policy for slices provisioned without any policy. | + +Table 9.5.3.2-2 describes Policy profile of the VAL server policy provisioning request. + +**Table 9.5.3.2-2: Policy profile** + +| Information element | Status | Description | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------| +| Policy | O | The name of VAL server policy. | +| >Area of interest | M | The geographical or service area for which the policy profile applies. | +| >Trigger event | M | Indicating the event that should be monitored, associated with the threshold of the monitored parameter. | +| >Expected action | M | Indicating the expected actions associated with the updated parameter. | +| Lifetime or number of events | M | Time duration or number of times the policy can take action. | +| Priority | O | Indicates the priority of the policy. | +| Scheduling period | O | Indicates the scheduling of policy in terms of time. | +| >Start time | M | Indicates the scheduled start time. | +| >End time | M | Indicates the scheduled end time. | +| Preemption | O | Indicates the pre-empt capability of the policy. | + +Table 9.5.3.2-3 to Table 9.5.3.2-6 list the supported policies. + +**Table 9.5.3.2-3: Policy of Max number of PDU sessions/ max number of UEs** + +| Information element | Status | Description | +|------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Policy | O | Max number of PDU sessions/ max number of UEs | +| >Area of interest | M | The geographical or service area for which the policy profile applies. | +| >Trigger event | M | Threshold information, i.e. reached utilization of available capacity in %), or number of PDU sessions request/ UEs reached the threshold | +| >Expected action | M | Modification of PDU sessions / max number of UEs (step for increase in %) | +| Lifetime or number of events | M | Time duration or number of times the policy can take action. | +| Priority | O | Indicates the priority of the policy. | +| Scheduling period | O | Indicates the scheduling of policy in terms of time. | +| >Start time | M | Indicates the scheduled start time. | +| >End time | M | Indicates the scheduled end time. | +| Preemption | O | Indicates the pre-empt capability of the policy. | + +**Table 9.5.3.2-4: Policy of Network slice load prediction** + +| Information element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| Policy | O | Network slice load prediction | +| >Area of interest | M | The geographical or service area for which the policy profile applies. | +| >Trigger event | M | Network Slice load predictions information from NWDAF as defined in TS 23.288 [4] clause 6.1.1 (exceeding utilization of available capacity in %) | +| >Expected action | M | Modification of related network slice parameters (step for increase in %) | +| Lifetime or number of events | M | Time duration or number of times the policy can take action. | +| Priority | O | Indicates the priority of the policy. | +| Scheduling period | O | Indicates the scheduling of policy in terms of time. | +| >Start time | M | Indicates the scheduled start time. | +| >End time | M | Indicates the scheduled end time. | +| Preemption | O | Indicates the pre-empt capability of the policy. | + +**Table 9.5.3.2-5: Policy of Time period and average QoS per UE** + +| Information element | Status | Description | +|------------------------------|--------|--------------------------------------------------------------------------------------------------------------------| +| Policy | O | Time period and average QoS per UE | +| >Area of interest | M | The geographical or service area for which the policy profile applies. | +| >Trigger event | M | Time/day configuration where specific network slice capacity /QoS per UE is expected, average QoS per UE requested | +| >Expected action | M | Modification of slice capacity to the requested needs | +| Lifetime or number of events | M | Time duration or number of times the policy can take action. | +| Priority | O | Indicates the priority of the policy. | +| Scheduling period | O | Indicates the scheduling of policy in terms of time. | +| >Start time | M | Indicates the scheduled start time. | +| >End time | M | Indicates the scheduled end time. | +| Preemption | O | Indicates the pre-empt capability of the policy. | + +**Table 9.5.3.2-6: Policy of needed minimum QoS per UE** + +| Information element | Status | Description | +|------------------------------|--------|-----------------------------------------------------------------------------| +| Policy | O | Minimum QoS per UE | +| Area of interest | M | The geographical or service area for which the policy profile applies. | +| >Trigger event | M | Time/day where minimum QoS per UE is expected, minimum QoS per UE requested | +| >Expected action | M | Modification of slice capacity to have the needed QoS per UE | +| Lifetime or number of events | M | Time duration or number of times the policy can take action. | +| Priority | O | Indicates the priority of the policy. | +| Scheduling period | O | Indicates the scheduling of policy in terms of time. | +| >Start time | M | Indicates the scheduled start time. | +| >End time | M | Indicates the scheduled end time. | +| Preemption | O | Indicates the pre-empt capability of the policy. | + +### 9.5.3.3 VAL server policy provisioning response + +Table 9.5.3.3-1 describes the information elements for the VAL server policy provisioning response from the NSCE server to the VAL server. + +**Table 9.5.3.3-1: VAL server policy provisioning Response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|---------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the VAL server policy provisioning request. | +| > Policy ID | O
(see NOTE1) | Identifies the provided policy. | +| > Cause | O
(see NOTE2) | Indicates the cause of VAL server policy provisioning request failure. | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: Shall be present if the result is failure and shall not be present otherwise. | | | + +### 9.5.3.4 VAL server policy update request + +Table 9.5.3.4-1 describes the information elements for the VAL server policy update request from the VAL server to the NSCE server. + +**Table 9.5.3.4-1: VAL server policy update request** + +| Information element | Status | Description | +|--------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. VAL server ID). | +| Requested slice information | M | Indication of the slice which is requested. | +| Policy ID | M | Identifies the provided policy. | +| Policy modification details (see NOTE) | O | Describe the details for the policy update. The policy profile is defined in Table 9.5.3.2-2. The supported VAL server policies are listed in Table 9.5.3.2-3 to Table 9.5.3.2-5. | +| Priority (see NOTE) | O | Indicates the priority of the policy. | +| Default policy indication (see NOTE) | O | Indicates the default policy for slices provisioned without any policy. | +| NOTE: At least one of these information elements shall be present. | | | + +### 9.5.3.5 VAL server policy update response + +Table 9.5.3.5-1 describes the information elements for the VAL server policy update response from the NSCE server to the VAL server. + +**Table 9.5.3.5-1: VAL server policy update response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the VAL server policy update request. | +| >Policy ID | O
(see NOTE 1) | Identifies the provided policy. | +| >Updated Default policy indication | O
(see NOTE 2) | Indicates the update of default policy. | +| >Cause | O
(see NOTE 3) | Indicates the cause of the failure. | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise. | | | +| NOTE 2: May only be present if the result is success. | | | +| NOTE 3: May only be present if the result is failure. | | | + +### 9.5.3.6 VAL server policy delete request + +Table 9.5.3.6-1 describes the information elements for the VAL server policy delete request from the VAL server to the NSCE server. + +**Table 9.5.3.6-1: VAL server policy delete request** + +| Information element | Status | Description | +|----------------------------------|--------|--------------------------------------------| +| Policy ID | M | Identifies the provided policy for delete. | +| Update Default policy indication | O | Indicates the update of default policy. | +| >Policy ID | M | Identifies the provided policy. | + +### 9.5.3.7 VAL server policy delete response + +Table 9.5.3.7-1 describes the information elements for the VAL server policy delete response from the NSCE server to the VAL server. + +**Table 9.5.3.7-1: VAL server policy delete response** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the VAL server policy delete request. | +| >Updated default policy | O
(see NOTE 1) | Policies with updated priority values. | +| >>Policy ID | M | Identifies the provided policy. | +| >>Priority | O | Indicates the updated priority values. | +| >Cause | O
(see NOTE 2) | Indicates the cause of the failure. | +| NOTE 1: May only be present if the result is success.
NOTE 2: May only be present if the result is failure. | | | + +### 9.5.3.8 VAL server policy usage reporting data subscribe request + +Table 9.5.3.8-1 describes information elements for the VAL server policy usage reporting data subscribe request from the VAL server to the NSCE server. + +**Table 9.5.3.8-1: VAL server policy usage reporting data subscribe request** + +| Information element | Status | Description | +|---------------------------------|--------|----------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. VAL server ID). | +| Requested slice information | M | Indication of the slice which is requested. | +| Requested policy reporting data | M | Indicates the request for policy reporting data. | +| >Policy ID | M | Identifies the provided policy. | +| >Start time | M | Indicates start time for the policy reporting data. | +| >End time | M | Indicates end time for the policy reporting data. | +| Reporting interval | O | Indicates the policy report data reporting interval. | + +### 9.5.3.9 VAL server policy usage reporting data subscribe response + +Table 9.5.3.9-1 describes information elements for the VAL server policy usage reporting data subscribe response from the NSCE server to the VAL server. + +**Table 9.5.3.9-1: VAL server policy usage reporting data subscribe response** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the VAL server policy usage reporting data subscribe request. | +| >Subscribe ID | O
(see NOTE 1) | Identifies the VAL server policy reporting subscribe event. | +| >Cause | O
(see NOTE 2) | Indicates the cause of the failure. | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise
NOTE 2: May only be present if the result is failure. | | | + +### 9.5.3.10 VAL server policy usage reporting data notification + +Table 9.5.3.10-1 describes information elements for the VAL server policy usage reporting data notification from the NSCE server to the VAL server. + +**Table 9.5.3.10-1: VAL server policy usage reporting data notification** + +| Information element | Status | Description | +|-----------------------|--------|--------------------------------------------------------------------------| +| Subscribe ID | M | Identifies the VAL server policy usage reporting subscribe request. | +| Policy reporting data | M | Indicates the requested VAL server policy reporting data. | +| >Policy ID | M | Identifies the provided policy. | +| >Policy count | M | Indicates the number of times the policy is active. | +| >Policy time spent | M | Indicates the duration for usage of policy. | +| >Pre-empt count | O | Indicates the number of times the policy is preempt with another policy. | +| >Pre-empt policy ID | O | Indicates the policy used for pre-emption. | + +### 9.5.3.11 Network slice optimization subscription request + +Table 9.5.3.11-1 describes information elements for the Network slice optimization subscription request from the VAL server to the NSCE server. + +**Table 9.5.3.11-1: Network slice optimization subscription request** + +| Information element | Status | Description | +|-------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. VAL server ID). | +| Security credentials | M | Security credentials resulting from a successful authorization for the NSCE service. | +| Notification Target Address | O | The Notification Target Address (e.g. URL) where the notifications destined for the requestor should be sent to. | +| Network slice related Identifier(s) | O | Identifier of the network slice. | +| Requested DNN | O | Indication of the DNN which is requested. | +| Policy ID | O | Identifies the VAL server policy. | +| Proposed expiration time | O | Proposed expiration time for the subscription. | +| Secondary policy ID | O | Secondary policy act as a fallback policy for the network slice optimization in the case of a failed network slice optimization. | + +### 9.5.3.12 Network slice optimization subscription response + +The information elements specified in the table 9.5.3.12-1 is used for the Network slice optimization subscription response sent from the NSCE server to the VAL server. + +**Table 9.5.3.12-1: Network slice optimization subscription Response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the Network slice optimization subscription request. | +| > Subscribe ID | O
(see NOTE 1) | Identifies the Network slice optimization subscribe event. | +| > Cause | O
(see NOTE 2) | Indicates the cause of Network slice optimization subscription request failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: Shall be present if the result is failure and shall not be present otherwise. | | | + +### 9.5.3.13 Network slice optimization notification + +The information elements specified in the table 9.5.3.13-1 is used for the Network slice optimization notification sent from the NSCE server to the VAL server. + +**Table 9.5.3.13-1: Network slice optimization Notification** + +| Information element | Status | Description | +|---------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------| +| > Subscribe ID | M | Identifies the Network slice optimization subscribe event. | +| >Network slice information | M | Network slice information (i.e. NEST) with network slice identifier(i.e. S-NSSAI) | +| >Optimization time | O | Indicates time spent for slice optimization by the NSCE Server. | +| >Enforced policy ID | O | Indicates the policy used for slice optimization in the case of the failed network slice optimization. | +| NOTE: One of these IEs shall be present in the message. | | | + +### 9.5.3.14 Network slice optimization report retrieval request + +Table 9.5.3.14-1 describes information elements for the Network slice optimization report retrieval request from the VAL server to the NSCE server. + +**Table 9.5.3.14-1: Network slice optimization report retrieval request** + +| Information element | Status | Description | +|----------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Subscribe ID | M | Identifies the Network slice optimization subscribe event. | +| Optimization result filter | O | Filter for network slice optimization responses (successful or failure). The default value is successful responses. | +| Optimization result sort | O | Sort optimization results based on slice optimization event time or optimization time, or policy ID. The default value is Optimization time. | +| >Sort type | O | Indicate sort type (ascending or descending). The default value is ascending. | +| >Optimization result size | O | Indicate the number of results of network slice optimization responses. The default value is 1. | +| Optimization result window | M | Indicates the time duration window for the report. | +| >Start time | M | Indicates the start time for generating the report. | +| >End time | M | Indicates the end time to finish the capture of the report. | + +### 9.5.3.15 Network slice optimization report retrieval response + +Table 9.5.3.15-1 describes information elements for the Network slice optimization report retrieval response from the NSCE server to the VAL server. + +**Table 9.5.3.15-1: Network slice optimization report retrieval response** + +| Information element | Status | Description | +|-----------------------------|--------|--------------------------------------------------------------------------------------------------------| +| Optimization report results | M | Report results based on the network slice optimization request. | +| >Subscribe ID | M | Identifies the Network slice optimization subscribe event. | +| >Optimization response | M | Indicates network slice optimization response as per the filter in the request. | +| >Optimization time | M | Indicates time spent for slice optimization by the NSCE Server. | +| >Policy ID | O | Identifies the VAL server policy. | +| >Enforced policy ID | O | Indicates the policy used for slice optimization in the case of the failed network slice optimization. | + +### 9.5.3.16 Policy harmonization subscribe notify + +Table 9.5.3.16-1 describes information elements for the Policy harmonization subscribe notify from the NSCE server to the VAL server. + +**Table 9.5.3.16-1: Policy harmonization subscribe notify** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| Policy ID | M | Identifies of the harmonized policy. | +| >harmonized policy | M | Pairs of policy attribute and harmonized parameter | + +## 9.5.4 APIs + +### 9.5.4.1 General + +Table 9.5.4.1-1 illustrates the API for Network slice optimization based on VAL server policy. + +**Table 9.5.4.1-1: Network slice optimization based on VAL server policy** + +| API Name | API Operations | Operation Semantics | Consumer(s) | | +|------------------------------|------------------------------------------|---------------------|-------------|--| +| SS_NSCE_PolicyManagement | Policy_Provisioning | Request/Response | VAL server | | +| | Policy_Update | Request/Response | | | +| | Policy_Delete | Request/Response | | | +| | Policy_Usage_Reporting_Data_Subscribe | Subscribe/Notify | | | +| | Policy_Usage_Reporting_Data_Notification | | | | +| SS_NSCE_NSOptimization | NS_Optimization_Subscription | Subscribe/Notify | VAL server | | +| | NS_Optimization_Notification | | | | +| | NS_Optimization_Report_Retrieval | Request/Response | | | +| SS_NSCE_Policy_harmonization | Policy_harmonization_Notify | Notify | VAL server | | + +### 9.5.4.2 SS\_NSCE\_Policy\_Provisioning operation + +**API operation name:** Policy\_Provisioning\_Request + +**Description:** The consumer subscribes for VAL server policy Provisioning. + +**Inputs:** See clause 9.5.3.2. + +**Outputs:** See clause 9.5.3.3. + +See clause 9.5.2.1.1 for details of usage of this operation. + +### 9.5.4.3 SS\_NSCE\_Policy\_Update operation + +**API operation name:** Policy\_Update + +**Description:** Providing the policy update to the NSCE server. + +**Inputs:** Refer subclause 9.5.3.4. + +**Outputs:** Refer subclause 9.5.3.5. + +See subclause 9.5.2.1.2 for details of the usage of this operation. + +### 9.5.4.4 SS\_NSCE\_Policy\_Delete operation + +**API operation name:** Policy\_Delete + +**Description:** Requesting policy delete to the NSCE server. + +**Inputs:** Refer subclause 9.5.3.6. + +**Outputs:** Refer subclause 9.5.3.7. + +See subclause 9.5.2.1.3 for details of the usage of this operation. + +#### 9.5.4.5 SS\_NSCE\_Policy\_harmonization Notify\_operation + +**API operation name:** Policy\_harmonization\_Notify + +**Description:** The consumer is notified with result of Policy harmonization . + +**Inputs:** None. + +**Outputs:** See clause 9.5.3.16. + +See clause 9.5.2.1.4 for details of usage of this operation. + +#### 9.5.4.6 SS\_NSCE\_Policy\_Usage\_Reporting\_Data\_Subscribe operation + +**API operation name:** Policy\_Usage\_Reporting\_Data\_Subscribe + +**Description:** Subscription to the VAL server policy usage reporting data. + +**Inputs:** Refer subclause 9.5.3.8. + +**Outputs:** Refer subclause 9.5.3.9. + +See subclause 9.5.2.1.5 for details of the usage of this operation. + +#### 9.5.4.7 SS\_NSCE\_Policy\_Usage\_Reporting\_Data\_Notification operation + +**API operation name:** Policy\_Usage\_Reporting\_Data\_Notification + +**Description:** VAL server policy usage reporting data notification to the existing subscription. + +**Inputs:** Refer subclause 9.5.3.10. + +**Outputs:** None + +See subclause 9.5.2.1.5 for details of the usage of this operation. + +#### 9.5.4.8 SS\_NSCE\_NS\_Optimization\_Report\_Retrieval operation + +**API operation name:** NSOptimizationReportRetrieval + +**Description:** Providing the network slice optimization report to the VAL server. + +**Inputs:** Refer subclause 9.5.3.14. + +**Outputs:** Refer subclause 9.5.3.15. + +See subclause 9.5.2.3 for details of the usage of this operation. + +#### 9.5.4.9 SS\_NSCE\_NSOptimization\_Subscribe Request operation + +**API operation name:** Ensce\_NSOptimization \_ Subscribe + +**Description:** The consumer request for Network Slice Optimization. + +**Inputs:** See clause 9.5.3.11. + +**Outputs:** See clause 9.5.3.12. + +See clause 9.5.2.2 for details of usage of this operation. + +#### 9.5.4.10 SS\_NSCE\_NSOptimization\_Notification operation + +**API operation name:** Ensce\_NSOptimization\_Notification + +**Description:** The consumer is notified with result of Network Slice Optimization. + +**Inputs:** See clause 9.5.3.13. + +**Outputs:** None + +See clause 9.5.2.2 for details of usage of this operation. + +## 9.6 Discovery of management service exposure + +### 9.6.1 General + +A Management Domain (MD) feature/capability is anything of use offered by the management system to the 3rd party application. Therefore, a new feature could be a managed entity, a MnS or management API, any software, hardware, or other functionality – for example, new technology support, new coverage area, new network slice type or instance, new NFs or new network slice subnet type or instance. To be able to utilise capabilities/features of the management system the applications must be made aware of existence of such features and capabilities. All MD features/capabilities come with a pre-configured exposure, where this can be configured by the operator for a given slice. This exposure is used to decide which application can see which information regarding the capability/feature. Exposure refers to the permissions that the 3rd party entity has gained over its use of the management service, e.g., the ability to read, or execute or modify or delete can be considered as different sorts of exposure. + +The first procedure (9.6.2.1) provides the NSCE server support for translating the VAL server request to a MnS requirement and the exposure of service/management data related to his request. The second procedure (9.6.2.2) supports the notification to the VAL server, based on a new/modified MnS / capability for a target slice. + +### 9.6.2 Procedure + +#### 9.6.2.1 VAL-triggered MnS discovery procedure + +In this procedure, the VAL server initially requests the new MnS which are supported by a target slice and based on this request the NSCE server requests from the OAM/MnS registry the MnS discovery. Then, the OAM/MnS registry derives the details to be exposed based on the NSCE server/VAL server permissions and provides the list of MnS for the given slice and the access details via the NSCE server to the VAL server. + +Pre-conditions: + +1. The VAL server has registered to receive NSCE services. +2. The NSCE server is trusted by the OAM, and a contract has been signed between the MNO and NSCE server provider to allow OAM interfaces and/or network slice information exposure. +3. MnS registry at OAM is aware of the allowed MnS and the permissions for a given slice. + +Figure 9.6.2.1-1 illustrates a solution for the MnS discovery support. + +![Sequence diagram illustrating MnS discovery support. The diagram shows three main entities: Management Discovery Service Producer / OAM, NSCE server, and VAL server. The sequence of interactions is: 1. VAL server sends a Management Service Discovery subscribe request to NSCE server. 2. NSCE server sends a Management Service Discovery subscribe response to VAL server. 3. NSCE server performs translation of VAL request to MnS requirement. 4. NSCE server performs Discovery of MnS by NSCE server. 5. NSCE server sends a Management Service discovery notify to VAL server.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant MDS Producer / OAM + + Note right of NSCE server: 3. translation of VAL request to MnS requirement + Note left of MDS Producer / OAM: 4. Discovery of MnS by NSCE server + + VAL server->>NSCE server: 1. Management Service Discovery subscribe request + NSCE server-->>VAL server: 2. Management Service Discovery subscribe response + Note right of NSCE server: 3. translation of VAL request to MnS requirement + Note left of MDS Producer / OAM: 4. Discovery of MnS by NSCE server + NSCE server-->>VAL server: 5. Management Service discovery notify + +``` + +Sequence diagram illustrating MnS discovery support. The diagram shows three main entities: Management Discovery Service Producer / OAM, NSCE server, and VAL server. The sequence of interactions is: 1. VAL server sends a Management Service Discovery subscribe request to NSCE server. 2. NSCE server sends a Management Service Discovery subscribe response to VAL server. 3. NSCE server performs translation of VAL request to MnS requirement. 4. NSCE server performs Discovery of MnS by NSCE server. 5. NSCE server sends a Management Service discovery notify to VAL server. + +**Figure 9.6.2.1-1: MnS discovery support** + +The steps of this procedure are as follows: + +1. The VAL server sends a Management Service Discovery subscribe request message to NSCE server to indicate a requirement for receiving the expected exposure capability type and the related permissions for a target slice or for a given VAL application. +2. The NSCE server sends a response to the subscription request, indicating a success or failure of the subscription request. + +NOTE 1: If CAPIF is used, the API interactions for the MnS discovery subscription shall be compliant with CAPIF as specified in 3GPP TS 23.222. + +3. The NSCE server translates the requirement based on the subscription, and in particular identifies the needed exposure capability type and translates it to a MnS exposure requirement. Such translation of the requirement includes the mapping to a list of MnSs (specified in TS 28.532) which are needed for the given slice and VAL server permissions. +4. The NSCE server coordinates with the 5GS and discovers the related network service(s), by triggering the MnS service discovery as specified in TS 28.537[9], clause 5.2.1.3. In particular, NSCE server acts as MnS discovery service consumer (for all MnS needed for a target slice based on VAL requirement) requests from MnS discovery service producer(s) at OAM the discovery of MnS information for the MnS related to the target slice or VAL application. The 5GS, MnS discovery service producer(s) sends the discovery result including related exposure information such as management service identifier, management service information and management service producer information to the NSCE server. + +NOTE 2: The actual connectivity in step 4 (e.g., exposure of MnS via CAPIF or EGMF) follows the mechanism defined in SA5. + +5. The NSCE server sends a management service discovery subscription notify message to provide the service/management data based on step 4, including the list of MnS and the corresponding exposure details to the VAL server. + +## 9.6.2.2 OAM-triggered new/modified MnS discovery + +This procedure includes the case when a new/modified MnS is deployed at the MD for the given slice, and the OAM/MnS registry provides this information directly to VAL server (assuming that VAL server has registered to the MD). + +Pre-conditions: + +1. VAL server is registered to NSCE server based on clause 9.2. +2. NSCE server has subscribed to OAM / MnS discovery service registry. + +![Sequence diagram for OAM-triggered new/modified MnS discovery. The diagram shows three lifelines: Management Discovery Service Producer / OAM, NSCE server, and VAL server. Step 1: Discovery of new or modified MnS / capability for target slice (from Producer to NSCE server). Step 2: Determine the VAL server(s) to be notified and generate a notification (from NSCE server to VAL server). Step 3: Management Service discovery notify (from NSCE server to VAL server).](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` +sequenceDiagram + participant Producer as Management Discovery Service Producer / OAM + participant NSCE as NSCE server + participant VAL as VAL server + Note over Producer, NSCE: 1. Discovery of new or modified MnS / capability for target slice + Note over NSCE, VAL: 2. Determine the VAL server(s) to be notified and generate a notification + NSCE->>VAL: 3. Management Service discovery notify +``` + +Sequence diagram for OAM-triggered new/modified MnS discovery. The diagram shows three lifelines: Management Discovery Service Producer / OAM, NSCE server, and VAL server. Step 1: Discovery of new or modified MnS / capability for target slice (from Producer to NSCE server). Step 2: Determine the VAL server(s) to be notified and generate a notification (from NSCE server to VAL server). Step 3: Management Service discovery notify (from NSCE server to VAL server). + +**Figure 9.6.2.2-1: OAM-triggered new/modified MnS discovery** + +1. The MnS registry may discover new or modified MnS in the 3GPP MD. Such changes may be due to new/modified management service producers, new managed entities (such as new radio, new technology or new NFs), new/modified technical support (such as support in a new geography or coverage area), availability of new management data, e.g., related to slice performance. An example procedure related to the addition of a new MnS producer is provided in TS 28.537 clause 5.2.1.1. + +The MnS discovery service producer when capturing new or modified capability (e.g. new MnS producer) related to the target slice or VAL application identifies the NSCE server which needs to be informed (based on the subscription) on the new/modified capability and derives the details to be exposed to the VAL server (via the NSCE server). Then, the MnS registry sends to the NSCE server the new / modified MnS. + +NOTE: The actual connectivity in step 4 (e.g., exposure of MnS via CAPIF or EGMF) follows the mechanism defined in SA5. + +2. The NSCE server determines the VAL server(s) that needs to be notified on the new or modified MnS / MD capability based on their registrations. Then, NSCE server generates and sends a notification with the required information to be provided to the VAL server. +3. The information on the discovered new/modified MnS is sent as a management service discovery notification message from the NSCE server to VAL server. + +## 9.6.3 Information flows + +### 9.6.3.1 General + +The following information flows are specified for the MnS discovery support based on 9.6.2 and 9.6.3. + +### 9.6.3.2 Management service discovery subscribe request + +Table 9.6.4.2-1 describes information elements for the Management service discovery subscribe request from the VAL server to the NSCE server. + +**Table 9.6.3.2-1: Management service discovery subscribe request** + +| Information element | Status | Description | +|-------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | The identifier of the VAL service for which the MnS discovery request applies | +| Network slice related Identifier(s) | O | The slice identifier, if known by the VAL server | +| Exposure capability requirement | O | The requirement includes indication of the requested permissions for exposing information related to the target slice. Also, the requirement may include the exposure capability type which is supported (e.g. via EGMF or directly to MnS producer) | + +### 9.6.3.3 Management service discovery subscribe response + +Table 9.6.3.3-1 describes information elements for the Management service discovery subscribe response from the NSCE server to the VAL server. + +**Table 9.6.3.3-1: Management service discovery subscribe response** + +| Information element | Status | Description | +|-----------------------------------------------------|-----------------|-------------------------------------------------------------------------------| +| Result | M | The result of the subscription request (positive or negative acknowledgement) | +| > Cause | O
(see NOTE) | Indicates the cause of failure. | +| NOTE: May only be present if the result is failure. | | | + +### 9.6.3.4 Management service discovery notify + +Table 9.6.3.4-1 describes information elements for the Management service discovery notify message from the NSCE server to the VAL server. + +**Table 9.6.3.4-1: Management service discovery notify** + +| Information element | Status | Description | +|-------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL service ID | M | The identifier of the VAL application | +| Management Domain/System ID | M | The identifier of the management system/domain of interest | +| List of MnS IDs / MnS producer IDs | M | The list of identifiers of the needed MnSs / MnS producers | +| >MnS capability | M | The capability per needed MnS. Such capability may related to the managed elements such as considerations for radio, technology, coverage or NFs | +| >MnS permissions | O | Allowed permissions of the VAL server over the MnS, e.g. whether it is allowed to read, write, delete, and/or update. | +| Network slice related Identifier(s) | O | The slice identifier which is mapped to the VAL application and the list of MnSs. | + +## 9.6.4 APIs + +### 9.6.4.1 General + +Table 9.6.4.1-1 illustrates the NSCE APIs for the MnS discovery feature. + +**Table 9.6.4.1-1: List of APIs for the MnS discovery feature** + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|------------------------------------------|------------------------------|-------------------|--------------------| +| SS_NSCE_Management_Service_Disc
overy | Management_Service Discovery | VAL server | Subscribe/Notify | + +## 9.6.4.2 SS\_NSCE\_Management\_Service Discovery + +### 9.6.4.2.1 General + +**API description:** This API enables the VAL server to communicate with the network slice capability enablement server for requesting management service discovery over NSCE-S. + +### 9.6.4.2.2 SS\_NSCE\_Management\_Service Discovery + +**API operation name:** Management\_Service Discovery + +**Description:** Providing for Management\_Service Discovery subscribe to the NSCE server and receiving a confirmation. + +**Known Consumers:** VAL server. + +**Inputs:** See subclause 9.6.2.1 (step 1) + +**Outputs:** See subclause 9.6.2.1 (step 4), 9.6.2.2 (step 3) + +## 9.7 Network slice related performance and analytics monitoring + +### 9.7.1 General + +The NSCE server supports the end to end network slice related performance and analytic monitoring capability exposure. The NSCE server identifies which data are needed, collects the data from different data sources (e.g., the OAM system, the Core Network or the VAL end users), performs the data organizations and aggregations and expose the processed data to VAL servers for monitoring. Following clauses are for the procedures, information flows and APIs for Network slice related performance and analytics monitoring request and Network slice related performance and analytics reporting respectively. The procedure in clause 9.7.2.1 is for task creation of the network slice performance and analytics monitoring. The procedure in clause 9.7.2.2 is for the performance and analytics data retrieving when the data is available. The procedure in clause 9.7.2.3 is for multiple network slices performance and analytics consolidated report. + +### 9.7.2 Procedure + +#### 9.7.2.1 Network slice related performance and analytics monitoring job creation request + +For network slice related performance and analytics monitoring job creation capabilities exposed to the VAL server, the VAL server triggers the procedure by sending the network slice related performance and analytics monitoring job creation request to NSCE server as Figure 9.7.2.2-1 shows: + +![Sequence diagram for Request Network slice related performance and analytics job creation monitoring. Lifelines: VAL server, NSCE Server, NSCE client, 5GS. The sequence shows: 1. VAL server to NSCE Server: Network slice related performance and analytics monitoring job creation; 2. NSCE Server internal Authorization; 3. NSCE Server to 5GS: Subscribe to network slice performance data and analytics data from OAM and 5GC; 4. NSCE Server to NSCE client: Subscribe network and service related KQI or performance data from NSCE client; 5. NSCE Server to VAL server: Network slice related performance and analytics monitoring job creation response.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE Server + participant NSCE client + participant 5GS + Note right of NSCE Server: 2. Authorization + VAL server->>NSCE Server: 1. Network slice related performance and analytics monitoring job creation + NSCE Server->>5GS: 3. Subscribe to network slice performance data and analytics data from OAM and 5GC + NSCE Server-->>NSCE client: 4. Subscribe network and service related KQI or performance data from NSCE client + NSCE Server->>VAL server: 5. Network slice related performance and analytics monitoring job creation response + +``` + +Sequence diagram for Request Network slice related performance and analytics job creation monitoring. Lifelines: VAL server, NSCE Server, NSCE client, 5GS. The sequence shows: 1. VAL server to NSCE Server: Network slice related performance and analytics monitoring job creation; 2. NSCE Server internal Authorization; 3. NSCE Server to 5GS: Subscribe to network slice performance data and analytics data from OAM and 5GC; 4. NSCE Server to NSCE client: Subscribe network and service related KQI or performance data from NSCE client; 5. NSCE Server to VAL server: Network slice related performance and analytics monitoring job creation response. + +**Figure 9.7.2.1-1: Request Network slice related performance and analytics job creation monitoring** + +1. The VAL server sends a request to NSCE server to create the Network slice related performance and analytics monitoring job to collect the desired service/VAL service specific performance and analytics data, the detailed content of the reported data depends on the type of the VAL services. The required end-to-end network slice related data performance data are indicated by *Perflist* IE as described in table 9.7.3.2-1. + 2. The NSCE server shall check if the VAL server is authorized to request the network slice performance and analytics data monitoring job creation. + 3. NSCE server determines the requested data needed to collect from network side and collects the performance measurements and analytics data of network slice from 5GS. For OAM system, the APIs defined in clause 11.3, TS 28.532[7] is utilized, e.g., packet delay, radio resource utilization. For CN functions, the APIs of Nnwdaf\_AnalyticsInfo service defined in clause 7.3, TS 23.288 [4] is utilized, e.g., slice load level related network data analytics, slice load level related network data analytics. + 4. Optionally, NSCE server retrieves the KQI data of services, the QoE data and the end user's information from NSCE client. +- NOTE 1: The Data collection from NSCE client follows the mechanism defined in SA4 EVEX in TS 26.531 clause 5.6. +- NOTE 2: How the collected data is stored in the NSCE server is implementation based. +5. NSCE server responds to VAL server to inform the VAL server if the monitoring request is succeed. + +## 9.7.2.2 Network slice related performance and analytics report subscription and report + +For network slice related performance and analytics result subscription and report, the VAL server triggers the procedure by sending the network slice related performance and analytics report subscription to NSCE server, the NSCE server reports the performance and analytics report after the subscription is succeed, as Figure 9.7.2.2-1 shows: + +![Sequence diagram showing network slice related performance and analytics report subscription and report. The diagram involves two main lifelines: VAL Server and NSCE server. The sequence of messages is: 1. VAL Server sends a 'Network slice related performance and analytics Report subscription' to NSCE server. 2. NSCE server responds with a 'Network slice related performance and analytics Report subscription response'. 3. NSCE server performs 'Data correlation'. 4. NSCE server sends a 'Network slice related performance and analytics Report Notify' to VAL Server.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` +sequenceDiagram + participant VAL Server + participant NSCE server + Note right of NSCE server: 3. Data correlation + VAL Server->>NSCE server: 1. Network slice related performance and analytics Report subscription + NSCE server-->>VAL Server: 2. Network slice related performance and analytics Report subscription response + NSCE server-->>VAL Server: 4. Network slice related performance and analytics Report Notify +``` + +Sequence diagram showing network slice related performance and analytics report subscription and report. The diagram involves two main lifelines: VAL Server and NSCE server. The sequence of messages is: 1. VAL Server sends a 'Network slice related performance and analytics Report subscription' to NSCE server. 2. NSCE server responds with a 'Network slice related performance and analytics Report subscription response'. 3. NSCE server performs 'Data correlation'. 4. NSCE server sends a 'Network slice related performance and analytics Report Notify' to VAL Server. + +**Figure 9.7.2.2-1: Network slice related performance and analytics report subscription and report** + +1. The VAL server subscribes to the required performance and analytics report. +2. The NSCE server response to the VAL server to indicate whether the report is successfully generated and ready. +3. NSCE server correlates the performance data of network slice instance, the analytics data of group of UEs and the KQI/QoE data to generate the performance data and analytics data report as required by VAL server. +4. NSCE server sends the performance report Notify to VAL server if the report is ready. + +### 9.7.2.3 Multiple slices related performance and analytics consolidated report request + +Based on preferred performance report request from the vertical applications, the consolidated performance report for dedicated service from multiple slices (PNI-NPN slice and PLMN slice of one network) can be offered to trusted third-party AF. + +Figure 9.7.2.3-1 illustrates the procedure of multiple slices coordinated performance and analytics report service from VAL server to NSCE server. + +Pre-conditions: + +1. The network slice enabler layer is capable to interact with PLMN 5GC or OAM system to handle slices of PLMN and its PNI-NPNs. +2. PNI-NPNs are deployed as network slices of the PLMN. +3. NSCE server has subscribed for MDE and NWDAF analytics for the managed slices of PLMN and PNI-NPN. + +![Sequence diagram illustrating the Multiple slices performance and analytics consolidated report process. The diagram shows interactions between a VAL server and components within a PLMN Domain (5GS, MDE/NWDAF, PNI-NPN1, PNI-NPN2, NSCE Server).](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant VAL server + subgraph PLMN Domain + participant 5GS + participant MDE/NWDAF + participant PNI-NPN1 + participant PNI-NPN2 + participant NSCE Server + end + Note right of NSCE Server: 1. Multiple slices related performance and analytics consolidated report request + VAL server->>NSCE Server: 1. Multiple slices related performance and analytics consolidated report request + Note right of NSCE Server: 2. Request authentication and authorization + NSCE Server-->>VAL server: 2. Request authentication and authorization + Note right of NSCE Server: 3. Retrieve PNI-NPN slice analytics from MDE / NWDAF + NSCE Server->>MDE/NWDAF: 3. Retrieve PNI-NPN slice analytics from MDE / NWDAF + Note right of NSCE Server: 4. Retrieve PLMN slice analytics from MDE / NWDAF + NSCE Server->>MDE/NWDAF: 4. Retrieve PLMN slice analytics from MDE / NWDAF + Note right of NSCE Server: 5. Performance data verification and consolidation analysis + MDE/NWDAF-->>NSCE Server: 5. Performance data verification and consolidation analysis + Note right of NSCE Server: 6. Multiple slices related performance and analytics consolidated report response + NSCE Server-->>VAL server: 6. Multiple slices related performance and analytics consolidated report response + +``` + +Sequence diagram illustrating the Multiple slices performance and analytics consolidated report process. The diagram shows interactions between a VAL server and components within a PLMN Domain (5GS, MDE/NWDAF, PNI-NPN1, PNI-NPN2, NSCE Server). + +**Figure 9.7.2.3 -1: Multiple slices performance and analytics consolidated report process** + +1. The VAL server initiates multiple slices related performance and analytics consolidated report request towards the NSCE server. The request includes VAL server ID, VAL service ID. The message also includes application key performance indicator (such as end-to-end delay, throughput, etc.) list and monitoring period. +2. Upon receiving the request from the VAL server to manage the network slice QoS monitoring report, the NSCE server makes authentication and authorization of the VAL server and if VAL server is not authorized, the NSCE server replies with failure response. +3. The NSCE server makes mapping from application ID that received from VAL server to slice identities (S-NSSAIs allocated in each network) and retrieves the PNI-NPN slice related status information from MDE/NWDAF, i.e. analytics data specified in 3GPP TS 28.104 [21] and TS 23.288 [4]. +4. The NSCE server retrieves the PLMN slice related performance information from MDE/NWDAF. The services of Nnwdaf\_AnalyticsInfo service defined in clause 7.3 of TS 23.288 [4] and analytics data as specified in 3GPP TS 28.104 [21] can be utilized. +5. The NSCE server verifies and analyses analytics data of network slice instances that is received from MDE/NWDAF about both PNI-NPN and PLMN slices, then NSCE server makes consolidated performance report among different kinds of network slices in specific period of time/location zone. +6. The NSCE server sends the multiple slices related performance and analytics consolidated report response towards VAL server including application key performance indicator (such as end-to-end delay, throughput, etc.) list and monitoring period. + +## 9.7.3 Information flows + +### 9.7.3.1 General + +The following information flows are specified for Network slice related performance and analytics monitoring: + +- Network slice related performance and analytics monitoring job creation request and response +- Network slice related performance and analytics monitoring report subscription + +- Network slice related performance and analytics monitoring report Notify +- Multiple slices related performance and analytics consolidated report request and response + +### 9.7.3.2 Network slice related performance and analytics monitoring job creation request and response + +Table 9.7.3.2-1 and Table 9.7.3.2-2 describe information elements for the network slice related performance and analytics monitoring job creation request and response between the VAL server and the NSCE server. + +**Table 9.7.3.2-1: Network slice related performance and analytics monitoring job creation request** + +| Information element | Status | Description | +|----------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL information | M | The information of the VAL server | +| Performance Monitoring Request ID | M | Identifier of the performance and analytics monitoring job | +| Performance and analytics monitoring metrics | M | The information of performance and analytics monitoring | +| > VAL service identity | M | Identifier of the VAL service to be monitored | +| >PerfList | M | The list of performance to be monitored | +| >> PerfName | M | The name of the performance to be reported, e.g., the end to end round-trip time or the end to end network slice load. | +| > Network slice related Identifier(s) | O | Identifier(s) of the network slice to be monitored | +| >StartTime | M | The start time point of the performance and analytics monitoring | +| >EndTime | O | The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated. | + +**Table 9.7.3.2-2: Network slice related performance and analytics monitoring job creation response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the performance and analytics monitoring request | +| > Performance Monitoring Request ID | O
(see NOTE 1) | Identifier of the performance and analytics monitoring job | +| >StartTime | O
(see NOTE 1) | The start time point of the performance and analytics monitoring | +| >EndTime | O
(see NOTE 2) | The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated. | +| >Cause | O
(see NOTE 3) | Indicates the cause of VAL performance and analytics monitoring request failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise. | | | +| NOTE 2: May only be present if the result is success. | | | +| NOTE 3: Shall be present if the result is failure and shall not be present otherwise. | | | + +### 9.7.3.3 Network slice related performance and analytics report subscription + +Table 9.7.3.3-1 and 9.7.3.3-2 describe information elements for Network slice related performance and analytics report subscription from the NSCE server to the VAL server. + +**Table 9.7.3.3-1: Network slice related performance and analytics report subscription** + +| Information element | Status | Description | +|---------------------------------------|--------|---------------------------------------------------------------------------------------------------------------| +| VAL information | M | The information of the VAL server | +| >VAL server ID | M | The identifier of the VAL server | +| Report ID | M | Identifier of performance and analytics results the report | +| Report Information | M | The information of performance and analytics report retrieving | +| > VAL service identity | M | Identifier of the VAL service of which the performance and analytics results are required | +| > Network slice related Identifier(s) | O | Identifier(s) of the network slice | +| >StartTime | M | The start time point of the performance and analytics report | +| >EndTime | M | The end time point of the performance and analytics report | +| >Notification time interval | O | The time interval that the network slice related performance and analytics report are supposed to be notified | +| >PerfList | M | The list of performance to be reported | +| >>PerfName | M | The name of the performance to be reported | + +**Table 9.7.3.3-2: Response of Network slice related performance and analytics report subscription** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the performance and analytics subscription | +| >Report ID | O
(see NOTE 1) | Identifier of the performance and analytics report Id | +| >Cause | O
(see NOTE 2) | Indicates the cause of VAL performance and analytics subscription failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2 Shall be present if the result is failure and shall not be present otherwise. | | | + +### 9.7.3.4 Network slice related performance and analytics report Notify + +Table 9.7.3.4-1 and 9.7.3.4-2 describe information elements for Network slice related performance and analytics report Notify from the NSCE server to the VAL server. + +**Table 9.7.3.4-1: Network slice related performance and analytics report Notify** + +| Information element | Status | Description | +|---------------------------------------------------------|--------|--------------------------------------------------------------------------------------| +| VAL information | M | The information of the VAL server | +| >VAL server ID | M | The identifier of the VAL server | +| >Network slice related performance and analytics report | M | Network slice related performance and analytics report as defined in Table 9.7.3.4-2 | + +**Table 9.7.3.4-2: Network slice related performance and analytics report** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Report ID | M | Identifier of the report | +| PerfResultFile | CM
(see NOTE 1) | PerfResultFile contains one or more PerfResult | +| >PerfResult | CM | Information element containing the VAL service identity or S-NSSAI followed by a list of result values for the aggregated or analyzed network slice related performance | +| >VAL service identity | M | Identifier of the VAL service of which the performance and analytics results are reported | +| > Network slice related Identifier(s) | O | Identifier(s) of the network slice | +| >ResultsValueList | | List of ResultsValue | +| >>ResultsValue | M | Information element containing the perfName and perfValue. | +| >>>PerfName | M | The name of the performance to be reported | +| >>>PerfValue | M | The corresponding value of the monitored performance | +| Failure response | CM
(see NOTE 2) | Indicates that network slice related performance and analytics results reporting failed. | +| >Cause | CM
(see NOTE 2) | Indicates the cause of network slice related performance and analytics results report failure | +| NOTE 1: Information element shall be present when the network slice related performance and analytics results retrieving is successful. | | | +| NOTE 2: Information element shall be present when the network slice related performance and analytics results retrieving is failure. | | | + +### 9.7.3.5 Multiple slices related performance and analytics consolidated report request and response + +Table 9.7.3.x-1 and Table 9.7.3.x-2 describe information elements for the multiple slices related performance and analytics consolidated report request and response between the VAL server and the NSCE server. + +**Table 9.7.3.5-1: Multiple slices related performance and analytics consolidated report request** + +| Information element | Status | Description | +|----------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------| +| VAL information | M | The information of the VAL server | +| Performance Monitoring Request ID | M | Identifier of the performance and analytics monitoring | +| Performance and analytics monitoring metrics | M | The information of performance and analytics monitoring | +| > VAL service identity | M | Identifier of the VAL service to be monitored | +| >PerfList | M | The list of performance to be monitored | +| >> PerfName | M | The name of the performance to be reported, e.g., the end to end round-trip time or the end to end network slice load. | +| > Network slice related Identifier(s) | O | Identifier(s) of the network slice to be monitored | +| >StartTime | M | The start time point of the performance and analytics monitoring | +| >EndTime | M | The end time point of the performance and analytics monitoring. | +| > Report ID | M | Identifier of performance and analytics report. | + +**Table 9.7.3.5-2: Multiple slices related performance and analytics consolidated report response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the performance and analytics monitoring request | +| >StartTime | O
(see NOTE 1) | The start time point of the performance and analytics monitoring | +| >EndTime | O
(see NOTE 1) | The end time point of the performance and analytics monitoring, If the EndTime IE is not included, it indicates that the performance and analytics monitoring will not stop until the monitoring request is released or updated. | +| >Report ID | O
(see NOTE 1) | Identifier of the report | +| >VAL service identity | O
(see NOTE 1) | Identifier of the VAL service of which the performance and analytics results are reported | +| >>Network slice related Identifier | O
(see NOTE 1) | Identifier of the network slice. One VAL service can be offered on one or more network slices | +| >>>ResultsValue | O
(see NOTE 1) | Information element containing the perfName and perfValue | +| >>>>PerfName | O
(see NOTE 1) | The name of the performance to be reported | +| >>>>PerfValue | O
(see NOTE 1) | The corresponding value of the monitored performance | +| >Cause | O
(see NOTE 2) | Indicates the cause of VAL performance and analytics monitoring request failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: Shall be present if the result is failure and shall not be present otherwise. | | | + +## 9.7.4 APIs + +### 9.7.4.1 General + +Table 9.7.4.1-1 and 9.7.4.1-2 illustrate the API for network slice related performance and analytics monitoring. + +**Table 9.7.4.1-1: SS\_NSCE\_PerfMonitoring API** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|------------------------|-------------------------|---------------------|-------------| +| SS_NSCE_PerfMonitoring | Perf_Monitoring_Request | Request /Response | VAL server | + +**Table 9.7.4.1-2 SS\_NSCE\_PerfResultReport API** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|--------------------------------|------------------------------|-----------------------|-------------| +| SS_NSCE_PerfReportSubscription | Perf_PerfReport_Subscription | Subscription/response | VAL Server | + +**Table 9.7.4.1-3: SS\_NSCE\_PerfReport API** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|-----------------------|----------------|---------------------|-------------| +| SS_NSCE_PerfReporting | Perf_Report | Notify | VAL Server | + +Table 9.7.4.1-4: SS\_NSCE\_MultiSlicePerfReport API + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|------------------------------|-------------------------|----------------------|-------------| +| SS_NSCE_MultiSlicePerfReport | Multi_Slice_Perf_Report | Request
/Response | VAL Server | + +#### 9.7.4.2 SS\_NSCE\_PerfMonitoring API + +**API operation name:** Perf\_Monitoring + +**Description:** The consumer requests to monitor network slice related performance and analytics. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.7.3.2-1. + +**Outputs:** See table 9.7.2.2-2. + +See clause 9.7.2.1 for details of usage of this operation. + +#### 9.7.4.3 SS\_NSCE\_PerfReportSubscription API + +**API operation name:** Perf\_Result\_Reporting + +**Description:** The consumer requests to report network slice related performance and analytics. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.7.3.3-1. + +**Outputs:** See table 9.7.3.3-2. + +See clause 9.7.2.2 for details of usage of this operation. + +#### 9.7.4.4 SS\_NSCE\_PerfReport API + +**API operation name:** Perf\_Report + +**Description:** The consumer get notify of network slice related performance and analytics report. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.7.3.4-1. + +**Outputs:** See table 9.7.3.4-2. + +See clause 9.7.2.2 for details of usage of this operation. + +#### 9.7.4.5 SS\_NSCE\_MultiSlicePerfReport API + +**API operation name:** Multi\_Slice\_Perf\_Report + +**Description:** The consumer requests to get multiple slices related performance and analytics consolidated report. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.7.3.5-1. + +**Outputs:** See table 9.7.3.5-2. + +See clause 9.7.2.3 for details of usage of this operation. + +## 9.8 Information collection from NSCE server(s) + +### 9.8.1 General + +The collected information by NSCE server could be exposed to other NSCE server(s) to optimize network resource allocation, based on the agreement among the NSCE servers. Then the NSCE server providing network slice related information acts as the producer, while the NSCE server obtaining network slice related information is the consumer. + +### 9.8.2 Procedure + +#### 9.8.2.1 Information collection from NSCE server(s) subscribe request and response + +Pre-condition: + +1. The producer NSCE server #2 has agreement with consumer NSCE server #1 to provide the collected slice information. + +![Sequence diagram illustrating the information collection process between NSCE server #1, NSCE server #2, SGS, and NSCE Client.](2dc649aff45a8a0924db45fc3bd6aabb_img.jpg) + +``` +sequenceDiagram + participant NSCE server #1 + participant NSCE server #2 + participant SGS + participant NSCE Client + + Note left of NSCE server #1: 1. Information collection from NSCE server(s) subscribe request + NSCE server #1->>NSCE server #2: Request authorization + Note right of NSCE server #2: 2. Request authorization + Note right of NSCE server #2: 3. Information collection + Note left of NSCE server #1: 4. Information collection from NSCE server(s) subscribe response + NSCE server #2-->>NSCE server #1: Slice information aggregation + Note left of NSCE server #1: 5. Slice information aggregation +``` + +The diagram is a sequence diagram with four lifelines: NSCE server #1, NSCE server #2, SGS, and NSCE Client. The process starts with NSCE server #1 sending a 'Request authorization' message to NSCE server #2. NSCE server #2 then performs 'Information collection' (indicated by a note). Finally, NSCE server #2 sends a 'Slice information aggregation' response back to NSCE server #1. The response is enclosed in a dashed box labeled '5. Slice information aggregation'. + +Sequence diagram illustrating the information collection process between NSCE server #1, NSCE server #2, SGS, and NSCE Client. + +**Figure 9.8.2.1-1: Information collection from NSCE server(s) subscribe request and response** + +1. The NSCE server#1 sends out the information collection subscribe request with expected period and interested slice ID, e.g., List of SNSSAI. This step could be done by pre-configuration. +2. The NSCE server #2 shall check if the NSCE server #1 is authorized to get the network slice information. +3. After authentication, the NSCE server #2 collects slice information as defined in clause 9.7.2.1 step3, step4. + +NOTE: When the producer NCSE server is edge NSCE server, only local information is collected and provided. + +4. The NSCE server #2 sends collected slice information to NSCE server #1. +5. The NSCE server #1 may process the collected slice information (such as information aggregation), if needed. + +### 9.8.2.2 Information collection from NSCE server(s) Notify + +![Sequence diagram showing information collection notification from NSCE server #2 to NSCE server #1.](30387053b5b3fede6873f6a46a9ca4a9_img.jpg) + +``` + +sequenceDiagram + participant NSCE server #1 + participant NSCE server #2 + Note right of NSCE server #2: 1. Information collection from NSCE server(s) notify + NSCE server #2->>NSCE server #1: + +``` + +Sequence diagram showing information collection notification from NSCE server #2 to NSCE server #1. + +**Figure 9.8.2.2-1: Information collection from NSCE server(s) Notify** + +- Once the reporting period is reached or the threshold is crossed, the NSCE server #2 sends information collection notify to NSCE server #1. + +## 9.8.3 Information flows + +### 9.8.3.1 General + +The following information flows are specified for Information collection from NSCE server(s): + +- Information collection from NSCE server(s) subscribe request, response and notify; + +### 9.8.3.2 Information collection from NSCE server(s) subscribe request + +Table 9.8.3.2-1 describes information elements for the Information collection from NSCE server(s) subscribe request from the consumer NSCE server to the producer NSCE server(s). + +**Table 9.8.3.2-1: Information collection from NSCE server(s) subscribe request** + +| Information element | Status | Description | +|-----------------------------|--------|------------------------------------------------------------------------------------------------------------------| +| Requester Identifier | M | Unique identifier of the requester (i.e. NSCE server ID). | +| Security credentials | M | Security credentials resulting from a successful authorization for the NSCE service. | +| Notification Target Address | O | The Notification Target Address (e.g. URL) where the notifications destined for the requester should be sent to. | +| List of S-NSSAI(s) | M | Identifier of the interested network slice | +| >QoS type indicator | O | QoS metric type including latency, throughput, jitter, etc. | +| >Threshold | O | Threshold of QoS metrics | +| >Reporting period | O | Indicating the metrics reporting period | +| >Immediate reporting flag | O | Indicating the request needs immediate reporting or not | +| Proposed expiration time | O | Proposed expiration time for the subscription | + +### 9.8.3.3 Information collection from NSCE server(s) subscribe response + +The information elements specified in the Table 9.8.3.3-1 is used for the Information collection from NSCE server(s) subscribe response sent from the producer NSCE server to the consumer NSCE server. + +**Table 9.8.3.3-1: Information collection from NSCE server(s) subscribe Response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the performance and analytics subscription. | +| > Subscription ID | O
(see NOTE 1) | Subscription identifier corresponding to the subscription. | +| >Network slice related performance and analytics report | O
(see NOTE 2) | Network slice related performance and analytics report as defined in Table 9.7.3.4-2 | +| > Cause | O
(see NOTE 3) | Indicates the cause of request failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: May only be present if the result is success.
NOTE 3: May only be present if the result is failure. | | | + +### 9.8.3.4 Information collection from NSCE server(s) notify + +The information elements specified in Table 9.8.3.4-1 are used for the information collection from NSCE server(s) notify sent from the producer NSCE server to the consumer NSCE server. + +**Table 9.8.3.4-1: Information collection from NSCE server(s) Notify** + +| Information element | Status | Description | +|---------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------| +| Subscription ID | M | Subscription identifier corresponding to the subscription. | +| >Network slice related performance and analytics report | M | Network slice performance and analytics (i.e. slice load) with network slice identifier(i.e. S-NSSAI) | + +## 9.8.4 APIs + +### 9.8.4.1 General + +Table 9.8.4.1-1 illustrates the API for information collection from NSCE server(s). + +**Table 9.8.4.1-1: API for Information collection from NSCE server(s)** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|------------------------|----------------|---------------------|-------------| +| SS_NSCE_InfoCollection | Subscribe | Subscribe/Response | NSCE server | +| | Notify | Notify | NSCE server | + +### 9.8.4.2 SS\_NSCE\_InfoCollection\_Subscribe operation + +**API operation name:** InfoCollection\_Subscribe + +**Description:** The consumer subscribes for Information collection from NSCE server(s). + +**Inputs:** See clause 9.8.3.2. + +**Outputs:** See clause 9.8.3.3. + +See clause 9.8.2.1 for details of usage of this operation. + +### 9.8.4.3 SS\_NSCE\_InfoCollection\_Notify operation + +**API operation name:** InfoCollection\_Notify + +**Description:** The consumer is notified with result of information collection from NSCE server(s). + +**Inputs:** None. + +**Outputs:** See clause 9.8.3.4. + +See clause 9.8.2.2 for details of usage of this operation. + +## 9.9 Predictive slice modification in edge based NSCE deployments + +### 9.9.1 General + +In this feature, the NSCE server initially receives an expected/predicted UE location/mobility change request outside an EDN service area for one or more UEs within the VAL application session (e.g. such session can be an indirect V2V session or a multiplayer gaming session). Then, the source NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target EDN. Thereafter, NSCE server evaluates the need for a slice modification (e.g. a slice lifecycle related trigger change) e.g. a slice subnet resource adaptation to allow for optimizing the application performance at the target area. Based on this decision/recommendation, it provides the action to the OAM and supports the re-mapping of NSCE server for the NSCE client proactively, before UE mobility happens. + +### 9.9.2 Procedure + +#### 9.9.2.1 Procedures on slice API configuration + +In the procedure shown in Figure 9.9.2.1-1, a mechanism is provided to allow for slice modification when a vertical application of single or group of VAL UEs migrates (or is expected/predicted to migrate) to a different EDN supported by different NSCE server. + +Pre-conditions: + +1. The VAL server has subscribed to the network slice capability enablement server +2. The VAL client of VAL UE is mapped to Slice#1, and NSCE client of VAL UE has established a connection to NSCE server#1 (S-NSCE server). +3. The S-NSCE server has already discovered the T-NSCE server and its area of coverage. +4. The VAL server is subscribed to and received prediction of UE location change + +![Sequence diagram illustrating the support for predictive slice modification in distributed NSCE server deployments. The diagram shows interactions between VAL client, NSCE client, 5GS, S-NSCE server @ EDN#1, T-NSCE server @ EDN#2, and VAL Server. The process involves an application service continuity requirement request from the VAL Server to the S-NSCE server, followed by a response, a query to the 5GS and OAM for slice conditions, an evaluation of slice support, a negotiation request to the T-NSCE server, a determination of lifecycle changes, a negotiation response, a slice modification trigger, and finally a slice modification notify to the clients and server.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant VAL_client as VAL client + participant NSCE_client as NSCE client + participant 5GS + participant S_NSCE_server as S-NSCE server @ EDN#1 + participant T_NSCE_server as T-NSCE server @ EDN#2 + participant VAL_Server as VAL Server + + Note right of S_NSCE_server: 1. Application service continuity requirement request + S_NSCE_server->>VAL_Server: 2. Application service continuity requirement response + Note right of S_NSCE_server: 3. Determine to query network/slice conditions at target service area from 5GC and slice availability / parameters from OAM + Note right of S_NSCE_server: 4. Evaluate whether NSCE service area supports slice + Note right of S_NSCE_server: 5. Service continuity negotiation request + Note right of T_NSCE_server: 6. Determine the need for slice related lifecycle change and generate a trigger action based on the predicted VAL application mobility + Note right of T_NSCE_server: 7. Service continuity negotiation response + Note right of S_NSCE_server: 8. Slice modification trigger + S_NSCE_server->>VAL_client: 9. Slice modification notify + S_NSCE_server->>VAL_Server: 9. Slice modification notify + Note right of S_NSCE_server: 10. NSCE client association from S-NSCE server to T-NSCE server (NSCE session re-establishment, modification) + +``` + +Sequence diagram illustrating the support for predictive slice modification in distributed NSCE server deployments. The diagram shows interactions between VAL client, NSCE client, 5GS, S-NSCE server @ EDN#1, T-NSCE server @ EDN#2, and VAL Server. The process involves an application service continuity requirement request from the VAL Server to the S-NSCE server, followed by a response, a query to the 5GS and OAM for slice conditions, an evaluation of slice support, a negotiation request to the T-NSCE server, a determination of lifecycle changes, a negotiation response, a slice modification trigger, and finally a slice modification notify to the clients and server. + +**Figure 9.9.2.1-1: Support for predictive slice modification in distributed NSCE server deployments** + +1. The VAL server sends to S-NSCE server an application service continuity requirement request due to predicted/expected UE or group UE mobility to a target service area covered by a different EDN. + +NOTE: Such UE predicted mobility at the VAL server can be based on UE mobility analytics received by NWDAF or can be predicted by the VAL layer (VAL server or VAL UE). + +2. S-NSCE server sends an application service continuity requirement response to the VAL server as positive or negative acknowledgement. +3. S-NSCE server determines to query the underlying 3GPP system on the slice availability and conditions at the target service area (based on step 1 requirement). Such query may be in form of a request/response and include: + - a. S-NSCE server interacting with 5GC to query the UE specific information (location, UE connection capabilities) as well as network conditions (network monitoring from NEF) and/or slice related analytics on the slice load (from NWDAF as specified in TS 23.288 [4]). + - b. S-NSCE server may also interact with OAM to query on the target slice availability and the up-to-date configured slice parameters e.g. slice RRM policies, modification of the NSI/NSSI resources (see TS 28.531 [8], 5.1.12) at the target service area and measurements for the slice at the target area. +4. S-NSCE server evaluates whether new NSCE service area supports slice #1 and if slice #1 offers similar performance in target area. +5. If the current slice doesn't fulfil these requirements, S-NSCE sends to the T-NSCE server (covering the target area) a service continuity negotiation request (including the VAL application service continuity requirement and optionally a proposed action) to negotiate on the trigger action. +6. T-NSCE server determines the need for a slice lifecycle change at the target area and translates this to a trigger action. This trigger action can be based on the proposed action in step 5 and can be a requested slice modification or the slice #1 creation/instantiation at the target area (this may happen if a group of UEs are moving to the target area and use slice #1, so it may be beneficial to create slice #1 at the target area). + +7. T-NSCE server sends to the S-NSCE server a service continuity negotiation response including the determined trigger action. +8. The S- or T-NSCE server may send the trigger action as a slice modification trigger request to the slice provisioning MnS producer at OAM (e.g. slice modification for network slice) to extend slice availability to the target service area based on the expected/predicted VAL UE or VAL group mobility. As response to the trigger action, the provisioning MnS producer provides a slice modification trigger response to the corresponding NSCE server with a positive or negative result. +9. After the slice lifecycle change execution (based on the indication in step 5), the S-NSCE server sends a notification to the VAL server and optionally to the VAL client via S-NSCE client +10. If the NSCE client needs to be remapped to different NSCE server (due to the expected change of UE location), the NSCE client establishes a new connection with T-NSCE and terminates the one with S-NSCE (in case of subscription-based interaction), or in case of request-based interaction, it updates the mapping at the client side, and maintains the new NSCE server address / ID for the target NSCE area. + +### 9.9.3 Information flows + +#### 9.9.3.1 General + +The following information flows are specified for the predictive slice modification support based on 9.9.2. + +#### 9.9.3.2 Application service continuity requirement request + +Table 9.9.3.2-1 describes information elements for the Application service continuity requirement request from the VAL server to the NSCE server. + +**Table 9.9.3.2-1: Application service continuity requirement request** + +| Information element | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| Security credentials | M | Security credentials resulting from a successful authorization. | +| VAL service ID | M | The identifier of the VAL service for which the requirement request applies | +| VAL UE ID list | O | The list of VAL UE IDs for which the requirement request applies | +| Service Continuity Requirement | M | The service continuity requirement which can be the expected or predicted migration of the VAL application or a list of VAL UEs within the application to a target area. | +| Slice identifier | O | The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server | +| Target Service Area | O | The target area can be represented as the geographical coordinates / set of waypoints outside the original service area, where the VAL application/ UE(s) is expected or predicted to move. | +| Application QoS requirements | O | The QoS requirements / KPIs for the VAL service | + +#### 9.9.3.3 Application service continuity requirement response + +Table 9.9.3.3-1 describes information elements for the Application service continuity requirement response from the NSCE server to the VAL server. + +**Table 9.9.3.3-1: Application service continuity requirement response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------| +| Result | M | The result of the request (positive or negative acknowledgement) | + +### 9.9.3.4 Service continuity negotiation request + +Table 9.9.3.4-1 describes information elements for the service continuity negotiation request from the S-NSCE server to the T-NSCE server. + +**Table 9.9.3.4-1: service continuity negotiation request** + +| Information element | Status | Description | +|--------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| S-NSCE server ID | M | The identifier of the source NSCE server | +| VAL service ID | M | The identifier of the VAL service for which the request applies | +| VAL UE ID list | O | The list of VAL UE IDs for which the request applies | +| Service Continuity Requirement | M | The service continuity requirement which can be the expected or predicted migration of the VAL application or a list of VAL UEs within the application to a target area. | +| Proposed Trigger Action | O | The proposed slice lifecycle change for the target VAL UE or VAL application | +| Slice identifier | M | The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server | +| Application QoS requirements | O | The QoS requirements / KPIs for the VAL service | + +### 9.9.3.5 Service continuity negotiation response + +Table 9.9.3.5-1 describes information elements for the service continuity negotiation response from the T-NSCE server to the S-NSCE server. + +**Table 9.9.3.5-1: service continuity negotiation response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------| +| Result | M | The result of the request (positive or negative acknowledgement) | +| Trigger Action | O | The determined trigger action which can be the slice lifecycle change for the target VAL UE or VAL application | + +### 9.9.3.6 Slice modification notify + +Table 9.9.3.6-1 describes information elements for the slice modification notify message from the NSCE server to the VAL server or the VAL client (via NSCE client). + +Table 9.9.4.6-1: slice modification notify + +| Information element | Status | Description | +|-----------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL service ID | M | The identifier of the VAL application which is expected to be impacted by the slice modification | +| VAL UE ID list | O | The identifiers of the VAL UEs which are expected to be impacted by the slice modification | +| Slice identifier | M | The slice identifier (S-NSSAI, NSI ID or ENSI) which is expected or predicted to modify to extend slice availability to the target service area | +| Target NSCE server ID and address | M | The identifier and address of the target NSCE server | +| Target Service Area | M | The target area can be represented as the edge service area (including the target DNN/DNAI) or the topological area (e.g. list of cells/TAs) for which the slice modification applies. | + +## 9.9.4 APIs + +### 9.9.4.1 General + +Table 9.9.4.1-1 illustrates the NSCE APIs for the predictive slice modification support feature. + +Table 9.9.4.1-1: List of APIs for the predictive slice modification support feature + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|----------------------------------------|--------------------------------|--------------------------|--------------------| +| SS_NSCE_Service_Continuity_Requirement | Service_Continuity_Requirement | VAL server | Request / Response | +| SS_NSCE_Service_Continuity_Negotiation | Service_Continuity_Negotiation | NSCE server | Request / Response | +| SS_NSCE_Slice_Modification_Notify | Slice_Modification_Notify | VAL server or VAL client | Notify | + +### 9.9.4.2 SS\_NSCE\_Service\_Continuity\_Requirement + +#### 9.9.4.2.1 General + +**API description:** This API enables the VAL server to communicate with the network slice capability enablement server for requesting a service continuity requirement over NSCE-S. + +#### 9.9.4.2.2 Service\_Continuity\_Requirement + +**API operation name:** Service\_Continuity\_Requirement + +**Description:** Providing for Service\_Continuity\_Requirement to the NSCE server and receiving a response / result. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.9.3.2-1 + +**Outputs:** See table 9.9.3.3-1 + +### 9.9.4.3 SS\_NSCE\_Service\_Continuity\_Negotiation + +#### 9.9.4.3.1 General + +**API description:** This API enables the S-NSCE server to communicate with the T-NSCE server for requesting a service continuity negotiation over NSCE-X. + +#### 9.9.4.3.2 Service\_Continuity\_Negotiation + +**API operation name:** Service\_Continuity\_Negotiation + +**Description:** Providing for Service\_Continuity\_Negotiation to the T-NSCE server and receiving a response / result. + +**Known Consumers:** S-NSCE server. + +**Inputs:** See table 9.9.3.4-1 + +**Outputs:** See table 9.9.3.5-1 + +#### 9.9.4.4 SS\_NSCE\_Slice\_Modification\_Notify + +##### 9.9.4.4.1 General + +**API description:** This API enables the network slice capability enablement server to communicate with the VAL server or VAL UE (NSCE client or VAL client) for notifying the slice modification to extend to the target service area. + +#### 9.9.4.3.2 Slice\_Modification\_Notify + +**API operation name:** Slice\_Modification\_Notify + +**Description:** Notifying about the slice modification to extend to the target area. + +**Known Consumers:** VAL server. + +**Inputs:** None + +**Outputs:** See table 9.9.3.6-1 + +### 9.10 Multiple slices coordinated resource optimization + +#### 9.10.1 General + +Based on preferred QoS request from the vertical applications, the performance monitoring of multiple slices of one network (PNI-NPN slice and PLMN slice) and resource adjustment between different slices can be made to realize optimized and efficient resource usage. + +#### 9.10.2 Procedure + +##### 9.10.2.1 Procedure on multiple slices coordinated resource optimization + +Figure 9.10.2.1-1 illustrates the procedure of multiple slices coordinated resource optimization service from VAL server to NSCE server. + +Pre-conditions: + +1. The network slice enabler layer is capable to interact with PLMN 5GC or OAM system to handle slices of PLMN and its PNI-NPNs. +2. PNI-NPNs are deployed as network slices of the PLMN. + +![Sequence diagram illustrating the Multiple slices coordinated resource optimization process. The diagram shows interactions between a VAL server, an NSCE Server, PNI-NPN1, PNI-NPN2, and 5GS within a PLMN Domain. The process involves a request from the VAL server, authentication, status data retrieval, analysis, and subsequent LCM requests and responses to the network slices.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant VAL server + subgraph PLMN Domain + participant NSCE Server + participant PNI-NPN1 + participant PNI-NPN2 + participant 5GS + end + Note right of VAL server: 1. Multiple slices coordinated resource optimization Request + VAL server->>NSCE Server: 1. Multiple slices coordinated resource optimization Request + Note right of NSCE Server: 2. Request authentication and authorization + NSCE Server->>VAL server: 2. Request authentication and authorization + Note right of NSCE Server: 3. Retrieve PNI-NPN slice Status data + NSCE Server->>5GS: 3. Retrieve PNI-NPN slice Status data + Note right of NSCE Server: 4. Retrieve PLMN slice status data + NSCE Server->>5GS: 4. Retrieve PLMN slice status data + Note right of NSCE Server: 5. Data verification and optimization analysis + Note right of NSCE Server: 6. PNI-NPN Slice LCM (ModifyNsi) Request + NSCE Server->>PNI-NPN1: 6. PNI-NPN Slice LCM (ModifyNsi) Request + Note right of PNI-NPN1: 7. PNI-NPN Slice LCM (ModifyNsi) Response + PNI-NPN1->>NSCE Server: 7. PNI-NPN Slice LCM (ModifyNsi) Response + Note right of NSCE Server: 8. PLMN Slice LCM (ModifyNsi) Request + NSCE Server->>PNI-NPN2: 8. PLMN Slice LCM (ModifyNsi) Request + Note right of PNI-NPN2: 9. PLMN Slice LCM (ModifyNsi) Response + PNI-NPN2->>NSCE Server: 9. PLMN Slice LCM (ModifyNsi) Response + Note right of NSCE Server: 10. Multiple slices coordinated resource optimization Response + NSCE Server->>VAL server: 10. Multiple slices coordinated resource optimization Response + +``` + +Sequence diagram illustrating the Multiple slices coordinated resource optimization process. The diagram shows interactions between a VAL server, an NSCE Server, PNI-NPN1, PNI-NPN2, and 5GS within a PLMN Domain. The process involves a request from the VAL server, authentication, status data retrieval, analysis, and subsequent LCM requests and responses to the network slices. + +**Figure 9.10.2.1-1: Multiple slices coordinated resource optimization process** + +1. The VAL server initiates multiple slices coordinated resource optimization request towards the NSCE server. The request includes VAL server ID, VAL service ID. The message also includes preferred optimization zone. +2. Upon receiving the request from the VAL server to make the network slice resource optimization, the NSCE server makes authentication and authorization of the VAL server and if VAL server is not authorized to send multiple slices coordinated resource optimization request, the NSCE server replies with failure response. +3. The NSCE server makes mapping from VAL service ID that received from VAL server to slice identities (S-NSSAIs allocated in multiple networks) and retrieves the network slice related status information from 5GC or OAM of PLMN for PNI-NPN slices, such as NF(s) load in 5GC and network utilization in access network as defined in TS 28.535 [11]. +4. The NSCE server retrieves the network slice related status information for PLMN from 5GC or OAM of PLMN networks for PLMN slices, such as NF(s) load in 5GC and network utilization in access network as defined in TS 28.535 [11]. The PLMN operator can choose to deploy NSCE-Server acting as single entry of PLMN capability exposure which can be optional. +5. The NSCE server verifies and analyses status data of network slices instance as well as network slice performance monitoring response (optional), then NSCE server makes resource optimization (e.g. shared radio resources, etc.) decision among different kinds of slices in specific location zone. +- 6-7. The NSCE server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s), such as modifyNsi request as specified in TS 28.531 [8] to PNI-NPN slice. Based on decision made by NSCE server, the network slice management entity (such as NSMF) performs the corresponding operation(s) and sends LCM response including slice resource adjustment result. +- 8-9. The NSCE server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s), such as modifyNsi request as specified in TS 28.531 [8] to PLMN slice. Based on decision made by NSCE server, the network slice management entity (such as NSMF) performs the corresponding operation(s) and sends LCM response including slice resource adjustment result. The PLMN + +operator can choose to deploy NSCE-S acting as single entry of PLMN capability exposure which can be optional. + +10. The NSCE server sends the multiple slices coordinated resource optimization response towards VAL server. + +### 9.10.3 Information flows + +#### 9.10.3.1 General + +The following information flows are specified: + +- Multiple slices coordinated resource optimization request and response. + +#### 9.10.3.2 Multiple slices coordinated resource optimization request + +Table 9.10.3.2-1 describes information elements for the multiple slices coordinated resource optimization request from the VAL server to the NSCE server. + +**Table 9.10.3.2-1: Multiple slices coordinated resource optimization request** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. VAL server ID). | +| Security credentials | M | Security credentials resulting from a successful authorization. | +| VAL service identity | M | Identifier of the VAL service application to be monitored. | +| Optimization Zone | O | The preferred location area of the performance monitoring and optimization. | +| Requested S-NSSAI(s) | O | Indication of the S-NSSAI(s) which are requested. | + +#### 9.10.3.3 Multiple slices coordinated resource optimization response + +Table 9.10.3.3-1 describes the information elements for the multiple slices coordinated resource optimization response from the NSCE server to the VAL server. + +**Table 9.10.3.3-1: Multiple slices coordinated resource optimization response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the multiple slices resource optimization request. | +| > VAL service identity | O
(see NOTE 1) | Identifier of the VAL service application to be monitored. | +| > Cause | O
(see NOTE 2) | Indicates the cause of multiple slices resource optimization request failure. | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise.
NOTE 2: Shall be present if the result is failure and shall not be present otherwise. | | | + +### 9.10.4 APIs + +#### 9.10.4.1 General + +Table 9.10.4.1-1 illustrates the API for multiple slices coordinated resource optimization. + +Table 9.10.4.1-1: Multiple slices coordinated resource optimization + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|----------------------------------|--------------------------|-------------------|--------------------| +| SS_NSCE_MultiSlices_Optimization | MultiSlices_Optimization | VAL server | Request/Response | + +## 9.10.4.2 SS\_NSCE\_MultiSlices\_Optimization operation + +**API operation name:** SS\_NSCE\_MultiSlices\_Optimization\_Request + +**Description:** The consumer subscribes for multiple slices coordinated resource optimization . + +**Inputs:** See clause 9.10.3.2. + +**Outputs:** See clause 9.10.3.3. + +See clause 9.10.2 for details of usage of this operation. + +# 9.11 Network slice adaptation for VAL application + +## 9.11.1 General + +This subclause describes the procedure for network slice adaptation at the Network Slice Capability Enablement (NSCE) server, based on a request from a VAL server to adapt the network slice for the VAL application. This request is handled between the NSCE server and the NSCE client per each VAL UE of the VAL application. Such adaptation assumes that the UE is subscribed to more than one slice and is done via providing a guidance to update the URSP rules at the 5GS (denoted in clause 9.11.2.1 as network-based mechanism). + +## 9.11.2 Procedures + +### 9.11.2.1 Procedure for VAL server-triggered and network-based network slice adaptation for VAL application + +Figure 9.11.2.1-1 illustrates the VAL server-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application. + +![Sequence diagram illustrating the network slice adaptation procedure for VAL application. The diagram shows interactions between VAL Server, NSCE server, 5GC, and OAM. The steps are: 1. Network slice adaptation request from VAL Server to NSCE server; 2. Retrieving network slice status from NSCE server to 5GC and OAM; 3. Network slice adaptation trigger per VAL UE from NSCE server to 5GC; 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination) from 5GC to NSCE server; 5. Network slice adaptation response from NSCE server to VAL Server.](8a409adf6ffdc83b8ed449036013d6d9_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GC + participant OAM + + Note right of OAM: [ ] indicates optional or dashed interaction + + VAL Server->>NSCE server: 1. Network slice adaptation request + NSCE server-->>5GC: 2. Retrieving network slice status + NSCE server-->>OAM: 2. Retrieving network slice status + NSCE server->>5GC: 3. Network slice adaptation trigger per VAL UE + 5GC->>NSCE server: 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination) + NSCE server->>VAL Server: 5. Network slice adaptation response + +``` + +Sequence diagram illustrating the network slice adaptation procedure for VAL application. The diagram shows interactions between VAL Server, NSCE server, 5GC, and OAM. The steps are: 1. Network slice adaptation request from VAL Server to NSCE server; 2. Retrieving network slice status from NSCE server to 5GC and OAM; 3. Network slice adaptation trigger per VAL UE from NSCE server to 5GC; 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination) from 5GC to NSCE server; 5. Network slice adaptation response from NSCE server to VAL Server. + +Figure 9.11.2.1-1: Network slice adaptation for VAL application + +1. The VAL server sends a network slice adaptation request to the NSCE server for the VAL application (and the VAL UEs within the VAL application). This request may be in the form of exact requested network slice (and + +optionally DNN) for all the VAL UEs of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN). The request optionally includes the adaptation threshold of network slice adaptation as defined in Table 9.11.3.1-1. + +2. [Optional] NSCE server collects the network slice status information, including network slice performance measurements in clause 5.1.1.1, clause 5.1.1.2, clause 5.1.1.3, in 3GPP TS 28.552 [19] and key performance indicators in clause 6.3, in 3GPP TS 28.554 [20], and network slice related E2E latency analytics report in clause 8.4.2.4.3, in 3GPP TS 28.104 [21] from network slice management functions by utilizing MnS of create MOI operation defined in clause 11.1 and MnS of streaming data reporting service or file data reporting service defined in clause 11.5 and 11.6, 3GPP TS 28.532 [7]. +3. The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application. If network slice status from step 2 is considered, the NSCE server analyses the network slice status information before triggering the network slice configuration. If the threshold is crossed for the current network slice of adaptation and the objective network slice satisfy the requests, NSCE server triggers the network slice configuration per VAL UE within the VAL Application. +4. The NSCE server acting as AF provides the updated S-NSSAI and DNN per VAL UE. In particular, NSCE server sends this information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in 3GPP TS 23.502 [12] clause 4.15.6.10, 3GPP TS 23.503 [17] clause 6.6.2.2, 3GPP TS 23.548 [18] clause 6.2.4). This guidance may update the route selection parameters to indicate different sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic. + +NOTE: NSCE server provides the updated S-NSSAI/DNN as a suggestion/guidance to PCF; however it is up to PCF to decide whether to perform the slice/DNN re-mapping + +5. Upon successful adaptation of the route selection parameters, the NSCE server provides a network slice adaptation response to the VAL server, providing information on the fulfilment of the network slice adaptation request per VAL application. + +## 9.11.2.2 Procedure for VAL UE-triggered and network-based network slice adaptation for VAL application + +Figure 9.11.2.2-1 illustrates the VAL UE-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application. + +Pre-condition: + +- The NSCE client has connected to the NSCE server; + +![Sequence diagram illustrating the network slice adaptation procedure for VAL application. The diagram shows interactions between VAL UE (containing VAL client and NSCE client), NSCE server, and 5GC. The steps are: 1. VAL application requirement change; 2. Network slice adaptation trigger; 3. Network Slice adaption trigger per VAL UE; 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination); 5. Network slice adaptation trigger response.](b882c54d92390b4ca523f230e3e07617_img.jpg) + +``` + +sequenceDiagram + participant VAL_UE as VAL UE + subgraph VAL_UE + VAL_client[VAL client] + NSCE_client[NSCE client] + end + NSCE_server[NSCE server] + 5GC[5GC] + + Note left of VAL_UE: 1. VAL application requirement change + VAL_UE->>NSCE_server: 2. Network slice adaptation trigger + Note right of NSCE_server: 3. Network Slice adaption trigger per VAL UE + Note right of 5GC: 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination) + NSCE_server-->>VAL_UE: 5. Network slice adaptation trigger response + +``` + +Sequence diagram illustrating the network slice adaptation procedure for VAL application. The diagram shows interactions between VAL UE (containing VAL client and NSCE client), NSCE server, and 5GC. The steps are: 1. VAL application requirement change; 2. Network slice adaptation trigger; 3. Network Slice adaption trigger per VAL UE; 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination); 5. Network slice adaptation trigger response. + +**Figure 9.11.2.2-1: Network slice adaptation for VAL application** + +1. The VAL client provides a new application requirement to the NSCE client, indicating a new service profile for the VAL application. This may be in the form of a change at the application QoS requirements, location + +requirements, time window requirement, access type preference (e.g., 3GPP, non-3GPP or multi access) service operation change, or other application-related parameters. + +2. The NSCE client sends a network slice adaptation trigger to the NSCE server for the VAL application. This trigger may be in the form of exact requested network slice (and optionally DNN) for the VAL UE of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN). The trigger may also include additional application requirements based on step1, e.g., the requested location criteria, time window. + +NOTE 1 : How the requested network slice is known by the NSCE client is out of scope of this release. + +3. The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application. + +NOTE 2: Whether and how the NSCE server triggers the network slice adaptation for all the VAL UEs within the VAL Application is out of scope of this release. + +NOTE 3: How the NSCE server decides to trigger the network slice configuration is implementation dependent. + +4. The NSCE server acting as AF provides the updated S-NSSAI, application requirements and DNN per VAL UE. In particular, NSCE server sends this information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in 3GPP TS 23.502 [12] clause 4.15.6.10, 3GPP TS 23.503 [17] clause 6.6.2.2, 3GPP TS 23.548 [18] clause 6.2.4). This guidance may update the route selection parameters to indicate different sets of PDU Session information (DNN, S-NSSAI, application requirements) that can be associated with applications matching the application traffic. 5GC uses this information to update the URSP to the affected UE(s). + +NOTE 4: NSCE server provides the updated S-NSSAI/DNN as a suggestion/guidance to PCF; however it is up to PCF to decide whether to perform the slice/DNN re-mapping + +5. The NSCE server sends the response to the NSCE client indicating success or failure. + +### 9.11.3 Information flows + +#### 9.11.3.1 Network slice adaptation request + +Table 9.11.3.1-1 describes the information flow network slice adaptation request from the VAL server to the NSCE server. + +**Table 9.11.3.1-1: Network slice adaptation request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL service ID | M | The VAL service ID of the VAL application for which the network slice adaptation may corresponds to. | +| List of VAL UE IDs | M | List of the VAL UE IDs within the VAL service for which the slice adaptation request corresponds | +| Requested Network slice related identifier(s) | O | Identifier of network slice for which the VAL server requests to use for adaptation | +| Requested monitored Network slice related identifier(s) | O
(see NOTE 1) | Identifier of the provisioned network slice(s) which are provisioned for the listed UE(s) and requested to be monitored by NSCE server | +| Requested DNN | O | Indication of the new DNN which is requested. | +| Requested Adaptation threshold | O
(see NOTE 2) | The threshold of network slice adaptation | +| >Requested adaptation threshold of the delay of network slice | O | The network slice delay defined clause 5.1.1.1, 5.1.1.2, 5.1.1.3, in 3GPP TS 28.552 [19] and key performance indicators in clause 6.3, in TS 28.554 [20], and network slice related analytics report in clause 8.4.2.4.3, in 3GPP TS 28.104 [21]. | +| NOTE 1: If this IE is not present then the NSCE server monitors all the slices provisioned for the listed UE(s) mentioned in this request. If this IE is present, the NSCE server monitors the network slice(s) only indicated by the identifier(s). | | | +| NOTE 2: The NSCE is requested to adapt UE to the requested network slice only when the status of the provisioned network slice for the listed UE(s) crosses the requested threshold. | | | + +### 9.11.3.2 Network slice adaptation response + +Table 9.11.3.2-1 describes the information flow network slice adaptation response from the NSCE server to the VAL server. + +**Table 9.11.3.2-1: Network slice adaptation response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------| +| Result | M | Result includes success or failure of the network slice adaptation with the underlying network. | +| Cause | O | Indicates the cause of failure | + +### 9.11.3.3 Network slice adaptation trigger + +Table 9.11.3.3-1 describes the information flow Network slice adaptation trigger from the NSCE client to the NSCE server. + +**Table 9.11.3.3-1: Network slice adaptation trigger** + +| Information element | Status | Description | +|-------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------| +| VAL UE ID(s) | M | The VAL UE ID(s) within the VAL service, for which the network slice adaptation trigger applies | +| VAL service ID | M | The VAL service ID of the VAL application for which the network slice configuration may correspond to. | +| Requested S-NSSAI | M | Indication of the new S-NSSAI which is requested. | +| Requested DNN | O | Indication of the new DNN which is requested. | +| Request application requirements | O | The application-related request parameters | +| >Requested time window | O | Indication of the new scheduled time window that is requested | +| >Requested location criteria | O | Indication of the new location criteria that is requested | +| >Requested access type reference | O | Indication of the new access type (3GPP, non-3GPP or multi-access) preference that is requested. | +| >Requested UE IP address preservation indicator | O | Indication that UE IP address preservation is requested | + +### 9.11.3.4 Network slice adaptation trigger response + +Table 9.11.3.4-1 describes the information flow network slice adaptation trigger response from the NSCE server to the NSCE client and optionally to the VAL client. + +**Table 9.11.3.4-1: Network slice adaptation trigger response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| Result | M | Result includes success or failure of the network slice adaptation. | +| Cause | O | Indicates the cause of failure | + +## 9.11.4 APIs + +### 9.11.4.1 General + +Table 9.11.4.1-1 illustrates the APIs for VAL server-triggered and network-based network slice adaptation. + +**Table 9.11.4.1-1: List of APIs for network slice adaptation** + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|--------------------------------|--------------------------|-------------------|--------------------| +| SS_NSCE_NetworkSliceAdaptation | Network_slice_adaptation | VAL server | Request/Response | + +Table 9.11.4.1-2 illustrates the APIs for VAL UE-triggered and network-based network slice adaptation + +**Table 9.11.4.1-2: List of APIs for network slice capability adaptation trigger** + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|---------------------------------------|----------------------------------|-------------------|--------------------| +| SS_NSCE_NetworkSliceAdaptationTrigger | Network_slice_adaptation_trigger | VAL server | Request/Response | + +## 9.11.4.2 SS\_NSCE\_NetworkSliceAdaptation API + +### 9.11.4.2.1 General + +**API description:** This API enables the VAL server to communicate with the network slice capability enablement server for network slice adaptation over NSCE-S. + +### 9.11.4.2.2 Network\_Slice\_Adaptation + +**API operation name:** Network\_Slice\_Adaptation + +**Description:** Requesting for network slice adaptation. + +**Known Consumers:** VAL server. + +**Inputs:** See subclause 9.11.3.1 + +**Outputs:** See subclause 9.11.3.2 + +See subclause 9.11.2.1 for the details of usage of this API operation. + +## 9.12 Slice related communication service lifecycle management exposure + +### 9.12.1 General + +The NSCE server supports the slice related communication service lifecycle management exposure to VAL server. The NSCE server acquires the application services related requirements for a specific VAL service from the vertical industry perspective, evaluates these requirements and then determines the network slice by pre-configured industry mapping relations or by KQI-KPI translation algorithms. After the network slice requirements are determined the NSCE server allocate proper network slice resources to support the application services. The NSCE server also enables the VAL server to reconfigure or disengage the slice related communication services for the application. The procedures in clause 9.12.2 are for creation, reconfiguration and disengagement of slice related communication service respectively. + +### 9.12.2 Procedure + +#### 9.12.2.1 Procedures on slice related communication service lifecycle management exposure + +##### 9.12.2.1.1 Slice related Communication Service Creation + +Figure 9.12.2.1.1-1 illustrates the procedure of slice related communication service creation. The NSCE helps to allocate network slice resources to support the application service required by the verticals. + +Pre-conditions: + +1. The VAL server has registered to receive NSCE services. + +![Sequence diagram for Slice related communication service creation](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +``` +sequenceDiagram + participant VAL_Server + participant NSCE_Server + participant 5GS + Note right of NSCE_Server: 2.Slice determination + Note right of NSCE_Server: 3. Network Slice allocation + VAL_Server->>NSCE_Server: 1. Slice related communication service creation request + NSCE_Server->>5GS: 3. Network Slice allocation + NSCE_Server-->>VAL_Server: 4. Slice related communication service creation response +``` + +The diagram illustrates a sequence of interactions between three entities: VAL\_Server, NSCE\_Server, and 5GS. The sequence starts with the VAL\_Server sending a 'Slice related communication service creation request' to the NSCE\_Server. The NSCE\_Server then performs 'Slice determination' and 'Network Slice allocation' (these two steps are shown in boxes on the NSCE\_Server lifeline). Finally, the NSCE\_Server sends a 'Slice related communication service creation response' back to the VAL\_Server. The 5GS entity is involved in the 'Network Slice allocation' step. + +Sequence diagram for Slice related communication service creation + +**Figure 9.12.2.1.1-1: Slice related communication service creation** + +1. The VAL server sends a request to NSCE server to create a slice related communication service to support a specific application service, e.g., the VAL server wants to create a video streaming service in a future factory, the slice related communication service creation request carries the identifier of the video streaming service and the corresponding service attributes. +2. NSCE server translates the application service requirements (e.g., for a video streaming service, the service location and the resolution of the video) and then perform slice determination (e.g., dLtThptPerSlice, uLtThptPerSlice, latency as defined in serviceProfile TS 28.541[14]). The NSCE may perform the translation by pre-configured industry profiles or by KQI-KPI translation algorithms which are out scope of standard. The procedures of APIs translation defined in clause 9.3 are referred to. +3. NSCE server initiates the Slice Service subscription procedures by utilizing the management service of network slice creation as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5. The slice creation request may fail due to the shortage of network resources or other causes. +4. NCSE server sends the slice related communication service creation response to VAL server. If the slice creation is succeeded in step3, then the response from NSCE server should include the attributes and the values of network slice determined by NSCE server. If the slice creation failed in step3, the NSCE server shall indicate the cause of the creation failure, e.g. the shortage of network slice resources. + +#### 9.12.2.1.2 Slice related Communication Service Reconfiguration + +Figure 9.12.2.1.2-1 illustrates the procedure of slice related communication service reconfiguration to support the application service. The NSCE server provides the APIs to enable the VAL server to reconfigure the application service related requirements in case the current application service is not satisfied or application service is adjusted. + +Pre-conditions: + +1. The VAL server has registered to receive NSCE services. +2. The VAL server has requested the NSCE server to create a slice related communication service to support the application service. + +![Sequence diagram for Slice related communication service reconfiguration](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` +sequenceDiagram + participant VAL_Server + participant NSCE_Server + participant 5GS + Note right of NSCE_Server: 2. Slice update + Note right of NSCE_Server: 3. Network Slice modification + VAL_Server->>NSCE_Server: 1. Slice related communication service reconfiguration request + NSCE_Server-->>VAL_Server: 4. Slice related communication service reconfiguration response + Note right of NSCE_Server: 2. Slice update + Note right of NSCE_Server: 3. Network Slice modification +``` + +The diagram illustrates a sequence of interactions between three entities: VAL\_Server, NSCE\_Server, and 5GS. The sequence starts with the VAL\_Server sending a '1. Slice related communication service reconfiguration request' to the NSCE\_Server. The NSCE\_Server then performs two internal steps, '2. Slice update' and '3. Network Slice modification', indicated by notes. Finally, the NSCE\_Server sends a '4. Slice related communication service reconfiguration response' back to the VAL\_Server. + +Sequence diagram for Slice related communication service reconfiguration + +**Figure 9.12.2.1.2-1: Slice related communication service reconfiguration** + +1. VAL server sends the slice related communication service reconfiguration request to the NSCE server to reconfigure the properties of the application service (e.g., In case there is a downgrade/upgrade of the application service where the application service profile is changed). +2. NSCE server translates the application requirements according to the reconfigured application properties then updates the requested network slice. +3. NSCE server initiates the Slice Service update procedures by utilize the management service of network slice modification as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5. +4. NCSE server sends the slice related communication service modification response to VAL server. + +### 9.12.2.1.3 Slice related Communication Service disengagement + +Figure 9.12.2.1.3-1 illustrates the procedure of slice related communication service disengagement. The NSCE server provides the APIs to enable the VAL server to terminate an application service. + +Pre-conditions: + +1. The VAL server has registered to receive NSCE services. +2. The VAL server has requested the NSCE server to create a slice related communication service to support the application service. + +![Sequence diagram for Slice related Communication service disengagement](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +``` +sequenceDiagram + participant VAL_Server + participant NSCE_Server + participant 5GS + Note right of NSCE_Server: 2. Network Slice deallocation + VAL_Server->>NSCE_Server: 1. Slice related communication service disengagement request + NSCE_Server-->>VAL_Server: 3. Slice related communication service disengagement response +``` + +The diagram is a sequence diagram showing the interaction between three entities: VAL\_Server, NSCE\_Server, and 5GS. The sequence of messages is as follows: 1. VAL\_Server sends a 'Slice related communication service disengagement request' to NSCE\_Server. 2. NSCE\_Server initiates 'Network Slice deallocation' (indicated by a self-message box). 3. NSCE\_Server sends a 'Slice related communication service disengagement response' back to VAL\_Server. + +Sequence diagram for Slice related Communication service disengagement + +**Figure 9.12.2.1.3-1: Slice related Communication service disengagement** + +1. The VAL server sends a request to NSCE server to disengage the slice related communication service when the application service is to be terminated. +2. NSCE server initiates the Slice Service de-allocation procedures by utilizing the management service of network slice de-allocation as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5. +3. NCSE server sends the slice related communication service disengagement response to VAL server. + +## 9.12.3 Information flows + +### 9.12.3.1 General + +The following information flows are specified for slice related communication service lifecycle management: + +- slice related communication service creation +- slice related communication service reconfiguration +- slice related communication service disengagement + +### 9.12.3.2 Slice related communication service creation + +Table 9.12.3.2-1 and Table 9.12.3.2-2 describe information elements for slice related communication service creation request and response between the VAL server and the NSCE server. + +**Table 9.12.3.2-1: Slice related communication service creation request** + +| Information element | Status | Description | +|-----------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service name | M | The name of the application service to be supported by the created slice related communication service, the value can be as followings:
V2X service;
Video streaming service;
Remote control service;
... | +| VAL service ID | M | Identifier of the application service | +| Area of interest | M | The geographical or service area for which the application service profile applies. | +| Application service profile | M | The list of the requirements of the corresponding application service | +| > ReqInfo | M | The element containing the reqName and reqValue | +| >>ReqName | M | The name of the application service requirement, the value of this IE can be as followings:
the resolution of a video service,
the end user numbers,
the latency,
... | +| >>ReqValue | M | The corresponding value of the application service requirement | + +**Table 9.12.3.2-2: Slice related communication service creation response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | Identifier of the application service to be supported by the created slice related communication service. | +| Result | M | Indicates the success or failure of the slice related communication service creation | +| Network slice info List | O
(see NOTE 1) | The list of the network slice info determined by NSCE | +| > Network slice info | O
(see NOTE 1) | The network slice info which includes the attributes and the corresponding values of network slice | +| >>S-NSSAI | O
(see NOTE 1) | The identifier of network slice | +| >>attributes of network slice | O
(see NOTE 1) | The list of attributes of the serviceProfile e.g, dLtThptPerSlice or latencies of network slice as defined in serviceProfile TS 28.541[10] | +| >>AttributeValues | O
(see NOTE 1) | The corresponding values of the attributes of the service profiles that determined by the NSCE server | +| Cause | O
(see NOTE 2) | Indicates the cause of creation failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise | | | +| NOTE 2: Shall be present if the result is failure and shall not be present otherwise | | | + +### 9.12.3.3 Slice related communication service reconfiguration + +Table 9.12.3.3-1 and Table 9.12.3.3-2 describe information elements for slice related communication service reconfiguration request and response between the VAL server and the NSCE server. + +**Table 9.12.3.3-1: Slice related communication service reconfiguration request** + +| Information element | Status | Description | +|-----------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service name | M | The name of the application service to be upgrade/downgrade which requires the reconfiguration of the slice related communication service, the value can be as followings:
V2X service;
Video streaming service;
Remote control service;
... | +| VAL service ID | M | Identifier of the application service | +| Area of interest | M | The geographical or service area for which the application profile applies. | +| Application service profile | M | The list of the requirements of the corresponding application service to be changed | +| > ReqInfo | M | The element containing the reqName and reqValue | +| >>ReqName | M | The name of the application service requirement, the value of this IE can be as followings:
the resolution of a video service,
the end user numbers,
the latency,
... | +| >>ReqValue | M | The corresponding updated value of the application service requirement | + +**Table 9.12.3.3-2: Slice related communication service reconfiguration response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | Identifier of the application service | +| Result | M | Indicates the success or failure of the slice related communication service reconfiguration | +| Network slice info List | O
(see NOTE 1) | The list of the network slice info updated by NSCE | +| > Network slice info | O
(see NOTE 1) | The network slice info which includes the attributes and the corresponding values of network slice | +| >>S-NSSAI | O
(see NOTE 1) | The identifier of network slice | +| >>Attributes of network slice | O
(see NOTE 1) | The list of attributes of the serviceProfile e.g., dLtThptPerSlice or latencies of network slice as defined in serviceProfile TS 28.541[10] | +| >>AttributeValues | O
(see NOTE 1) | The corresponding values of the attributes of the service profiles that updated by the NSCE server | +| Cause | O
(see NOTE 2) | Indicates the cause of reconfiguration failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise | | | +| NOTE 2: Shall be present if the result is failure and shall not be present otherwise | | | + +### 9.12.3.4 Slice related communication service disengagement + +**Table 9.12.3.4-1: Slice related communication service disengagement request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service name | M | The name of the application service to be terminated which requires the disengagement of the slice related communication service, the value can be as followings:
V2X service;
Video streaming service;
Remote control service;
... | +| VAL service ID | M | Identifier of the application service | + +**Table 9.12.3.4-2: Slice related communication service disengagement response** + +| Information element | Status | Description | +|---------------------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the slice related communication service disengagement request | +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | Identifier of the application service | +| Cause | O(see NOTE) | Indicates the cause of disengagement failure | +| NOTE: | Shall be present if the result is failure and shall not be present otherwise | | + +## 9.12.4 APIs + +### 9.12.4.1 General + +Table 9.12.4.1-1 and 9.12.4.1-2 illustrate the API for slice related communication service lifecycle management exposure. + +**Table 9.12.4.1-1: SS\_NSCE\_SliceCommServiceCreation** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|-----------------------------------|-----------------------------------|---------------------|-------------| +| SS_NSCE_SliceCommService_Creation | SliceCommService_Creation_Request | Request /Response | VAL server | + +**Table 9.12.4.1-2 SS\_NSCE\_SliceCommServiceReconfiguration** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|------------------------------------------|------------------------------------------|---------------------|-------------| +| SS_NSCE_SliceCommService_Reconfiguration | SliceCommService_Reconfiguration_Request | Request /Response | VAL Server | + +**Table 9.12.4.1-3: SS\_NSCE\_SliceCommServiceDisengagement** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|----------------------------------------|----------------------------------------|---------------------|-------------| +| SS_NSCE_SliceCommService_Disengagement | SliceCommService_Disengagement_Request | Request /Response | VAL Server | + +### 9.12.4.2 SS\_NSCE\_SliceCommService\_Creation API + +**API operation name:** SliceCommService\_Creation + +**Description:** The consumer requests to create the slice related communication service + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.12.3.2-1. + +**Outputs:** See table 9.12.3.2-2. + +See clause 9.12.2.1.1 for details of usage of this operation. + +#### 9.12.4.3 SS\_NSCE\_SliceCommService\_Reconfiguration API + +**API operation name:** SliceCommService\_Reconfiguration + +**Description:** The consumer requests to report reconfigure the slice related communication service. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.12.3.3-1. + +**Outputs:** See table 9.12.3.3-2. + +See clause 9.12.2.1.2 for details of usage of this operation. + +#### 9.12.4.4 SS\_NSCE\_SliceCommService\_Disengagement API + +**API operation name:** SliceCommService\_Disengagement + +**Description:** The consumer requests to disengagement the slice related communication service. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.12.3.4-1. + +**Outputs:** See table 9.12.3.4-2. + +See clause 9.12.2.1.3 for details of usage of this operation. + +### 9.13 Predictive slice modification in Inter-PLMN based slice service continuity + +#### 9.13.1 General + +This feature applies to the specific deployment where NSCE service provider provides its services when connected to two PLMNs and has SLA with them. In this feature, the NSCE server initially receives an expected/predicted UE location/mobility change request outside a PLMN1 slice service area for one or more UEs within the VAL application session (e.g. such session can be a V2X session). Then, the NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target PLMN. The NSCE server evaluates the need for a slice modification (e.g. a slice lifecycle related trigger change). Based on this decision/recommendation, it provides the action to the OAM of PLMN2 proactively, before UE mobility happens. + +#### 9.13.2 Procedure + +In the procedure shown in Figure 9.13.2-1, a mechanism is provided to allow for slice modification when a vertical application of single or group of VAL UEs migrates (or is expected/predicted to migrate) to a different PLMN supported by the same NSCE server. + +Pre-conditions: + +1. Enterprise hosting the VAL server has SLA for slice services with NSCE service provider. + +2. The VAL server has subscribed to the network slice capability enablement server managing slice services from PLMN1 and PLMN2. +3. The VAL client of VAL UE is mapped to Slice#1, and NSCE client of VAL UE has established a connection to PLMN1. +4. The NSCE server is connected to OAMs of PLMN1 and PLMN2. +5. The VAL server is subscribed to and received prediction of UE location change from PLMN1 to PLMN2 in advance before the actual event. + +![Sequence diagram illustrating Predictive Inter-PLMN slice service continuity. Lifelines: VAL client, NSCE client, PLMN1 5GS, PLMN2 5GS, NSCE server, VAL Server. The sequence shows the VAL server sending a request to the NSCE server, which then queries the PLMN2 5GS and OAM. The NSCE server determines the need for a slice modification and triggers it to PLMN 2. The VAL server receives a notification. A dashed line indicates UE mobility from PLMN1 to PLMN2. After mobility, the NSCE server triggers a slice modification to PLMN 1.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +``` + +sequenceDiagram + participant VAL_client as VAL client + participant NSCE_client as NSCE client + participant PLMN1_5GS as PLMN1 5GS + participant PLMN2_5GS as PLMN2 5GS + participant NSCE_server as NSCE server + participant VAL_Server as VAL Server + + Note right of VAL_Server: 1. Inter-PLMN application service continuity requirement request + VAL_Server->>NSCE_server: 1. Inter-PLMN application service continuity requirement request + Note right of NSCE_server: 2. Inter-PLMN application service continuity requirement response + NSCE_server->>VAL_Server: 2. Inter-PLMN application service continuity requirement response + Note right of VAL_Server: 3. Determine to query Destination network/slice conditions at target service area from PLMN2 5GC and slice availability / parameters from OAM + VAL_Server->>NSCE_server: 3. Determine to query Destination network/slice conditions at target service area from PLMN2 5GC and slice availability / parameters from OAM + Note right of NSCE_server: 4. Determine the need for slice related lifecycle change and generate a trigger action based on the predicted VAL application mobility + NSCE_server->>VAL_Server: 4. Determine the need for slice related lifecycle change and generate a trigger action based on the predicted VAL application mobility + Note right of VAL_Server: 5. Slice modification trigger to PLMN 2 + VAL_Server->>NSCE_server: 5. Slice modification trigger to PLMN 2 + Note right of NSCE_server: 6. Slice modification notify + NSCE_server->>VAL_Server: 6. Slice modification notify + Note right of VAL_Server: UE mobility from PLMN1 to PLMN2 + VAL_Server-->>NSCE_server: UE mobility from PLMN1 to PLMN2 + Note right of NSCE_server: 7. Slice modification trigger to PLMN 1 + NSCE_server->>VAL_Server: 7. Slice modification trigger to PLMN 1 + +``` + +Sequence diagram illustrating Predictive Inter-PLMN slice service continuity. Lifelines: VAL client, NSCE client, PLMN1 5GS, PLMN2 5GS, NSCE server, VAL Server. The sequence shows the VAL server sending a request to the NSCE server, which then queries the PLMN2 5GS and OAM. The NSCE server determines the need for a slice modification and triggers it to PLMN 2. The VAL server receives a notification. A dashed line indicates UE mobility from PLMN1 to PLMN2. After mobility, the NSCE server triggers a slice modification to PLMN 1. + +**Figure 9.13.2-1: Predictive Inter-PLMN slice service continuity** + +1. The VAL server sends to NSCE server an Inter-PLMN application service continuity requirement due to predicted/expected UE or group UE mobility from source service area of slice1 in PLMN1 to a target service area covered by a different slice service area in slice#2/PLMN2. + +NOTE: Such UE predicted mobility at the VAL server can be available before the event based on UE mobility analytics received by NWDAF or can be predicted by the VAL layer (VAL server or VAL UE). + +2. NSCE server sends an Inter-PLMN application service continuity requirement response to the VAL server as positive or negative acknowledgement depending on its capability to provide such service serving both areas/slices in both PLMNs and available resources. +3. NSCE server determines to query the underlying 5G system on the slice availability and conditions at the target service area/slice2/PLMN2 (based on step 1 requirement). Such query may be in form of a request/response and include: + +- a. NSCE server interacting with 5GC/PLMN2 to query the UEs specific information (location, UEs connection capabilities) as well as network conditions (network monitoring from NEF) and/or slice related analytics on the slice load (from NWDAF as specified in TS 23.288 [4]). + - b. NSCE server may also interact with OAM/PLMN2 to query on the target slice availability and the up-to-date configured slice parameters e.g. slice RRM policies, modification of the NSI/NSSI resources (see TS 28.531 [8], 5.1.12) at the target service area and measurements for the slice at the target area. +4. NSCE server determines the need for a slice lifecycle change at the slice target area and translates this to a trigger action. This trigger action can be based on the outcome of step 3 and can be a requested slice modification (slice2/PLMN2) or creation/instantiation of new slice at the target area (this may happen if a group of UEs are moving to the target area and the requested slice2 is missing in the target area). +5. The NSCE server may send the trigger action as a slice modification trigger request to the slice provisioning MnS producer at OAM/PLMN2 (e.g. slice modification for network slice) to extend slice availability to the target service area based on the expected/predicted VAL UE or VAL group mobility. As response to the trigger action, the provisioning MnS producer provides a slice modification trigger response with a positive or negative result. +6. After the slice lifecycle change execution (based on the indication in step 5), the NSCE server sends a notification to the VAL server and optionally to the VAL client containing the positive or negative result from step5. +7. If big number of UEs is migrating from PLMN1 to PLMN2, there might be a need to further modify/reduce the respective slice resources of PLMN1. NSCE sends trigger request to the slice provisioning MnS producer at OAM/PLMN1 (e.g. slice modification for network slice) to decrease slice availability to the source area after the UEs have migrated. + +### 9.13.3 Information flows + +#### 9.13.3.1 General + +The following information flows are specified for predictive inter-PLMN slice service continuity: + +- Inter-PLMN application service continuity requirement +- Slice modification notification + +#### 9.13.3.2 Inter-PLMN application service continuity requirement request + +Table 9.13.3.2-1 and Table 9.13.3.2-2 describe information elements inter-PLMN application service continuity requirement request and response between the VAL server and the NSCE server. + +**Table 9.13.3.2-1: Inter-PLMN application service continuity requirement request** + +| Information element | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| Security credentials | M | Security credentials resulting from a successful authorization. | +| VAL service ID | M | The identifier of the VAL service for which the requirement request applies | +| VAL UE ID list | O | The list of VAL UE IDs for which the requirement request applies | +| Service Continuity Requirement | M | The service continuity requirement which can be the expected or predicted migration of the VAL application or a list of VAL UEs within the application to a target area. | +| Target PLMN ID | M | PLMN identifier of the target PLMN | +| Slice identifier | O | The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server | +| Target Service Area | O | The target area can be represented as the geographical coordinates / set of waypoints outside the original service area, where the VAL application/ UE(s) is expected or predicted to move. | +| Application QoS requirements | O | The QoS requirements / KPIs for the VAL service | + +**Table 9.13.3.2-2: Inter-PLMN application service continuity requirement response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------| +| Result | M | The result of the request (positive or negative acknowledgement) | + +### 9.13.3.3 Inter-PLMN slice modification notify + +Table 9.13.3.3-1 describes information elements for the inter-PLMN slice modification notify message from the NSCE server to the VAL server or the VAL client (via NSCE client). + +**Table 9.13.3.3-1: Inter-PLMN slice modification notify** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL service ID | M | The identifier of the VAL application which is impacted by the slice modification | +| VAL UE ID list | O | The identifiers of the VAL UEs which are impacted by the slice modification | +| Slice identifier | M | The slice identifier (S-NSSAI, NSI ID or ENSI) which is used and/or modified to extend slice availability to the target service area | +| PLMN ID | M | PLMN identifier of the PLMN where modification was performed | +| Target Service Area | M | The target area, can be represented as the geographical coordinates / set of waypoints outside the original service area, for which the modification applies. | + +## 9.13.4 APIs + +### 9.13.4.1 General + +Table 9.13.4.1-1 illustrates the API for inter-PLMN application service continuity exposure. + +**Table 9.13.4.1-1: Inter-PLMN application service continuity requirement** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|---------------------------------------------|--------------------------------------|---------------------|--------------------------| +| SS_NSCE_InterPLMN_Continuity | Inter-PLMN_Continuity_Requirement | Request/Response | VAL server | +| SS_NSCE_InterPLMN_Slice_Modification_Notify | Inter-PLMN_Slice_Modification_Notify | Notify | VAL server or VAL client | + +### 9.13.4.2 SS\_NSCE\_Inter-PLMN\_Continuity API + +**API operation name:** Inter-PLMN\_Continuity\_Requirement + +**Description:** The consumer requests to have inter-PLMN slice service continuity + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.13.3.2-1. + +**Outputs:** See table 9.13.3.2-2. + +See clause 9.13.2 for details of usage of this operation. + +### 9.13.4.3 SS\_NSCE\_Inter-PLMN\_slice modification notify API + +**API operation name:** Inter-PLMN\_Slice\_Modification\_Notify + +**Description:** The NSCE notifies about slice modification + +**Known Consumers:** VAL server. + +**Inputs:** None. + +**Outputs:** See table 9.13.3.3-1. + +See clause 9.13.2 for details of usage of this operation. + +## 9.14 Network slice diagnostics + +### 9.14.1 General + +Network slice diagnostics provides possibility for the vertical/ASP using VAL server to receive information about the specific event(s) related to service experience. The vertical/ASP using the VAL server has estimated bad QoE for a mobile user or service – either reported from a mobile user or service or detected by application and can initiate a check with NSCE. The NSCE server can provide details related to the identified event. + +### 9.14.2 Procedure + +#### 9.14.2.1 Network slice diagnostics procedure + +In the procedure shown in Figure 9.14.2.1-1, a mechanism is provided to allow for vertical/ASP using VAL server to initiate request for network slice diagnostics and receive all the relevant information about specific events. + +Pre-conditions: + +1. Enterprise hosting the VAL server has SLA for slice services with NSCE service provider. +2. The VAL server has subscribed to the network slice capability enablement server managing slice services. + +3. The NSCE server has initiated monitoring and gathering statistical data about its managed slices from ADAES according to TS 23.436 clause 8.3 and 8.7. +4. The VAL server has identified there is specific event where the application has experienced service degradation (reported errors from VAL client for degraded service (bad quality), reported errors from application (downgrade of communication, detected communication errors)). + +![Sequence diagram of Network slice diagnostics procedure](f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg) + +``` +sequenceDiagram + participant VAL Server + participant NSCE server + participant ADAES + Note left of NSCE server: 2. Determine and collect slice-specific application performance statistics and slice usage pattern statistics related to service degradation + Note left of NSCE server: 3. Corelate data and prepare network slice diagnostics report + VAL Server->>NSCE server: 1. Network slice diagnostics request + NSCE server->>ADAES: + Note right of ADAES: + NSCE server->>VAL Server: 4. Network slice diagnostics reply +``` + +The diagram illustrates the Network slice diagnostics procedure involving three entities: ADAES, NSCE server, and VAL Server. The sequence of interactions is as follows: 1. The VAL Server sends a 'Network slice diagnostics request' to the NSCE server. 2. The NSCE server performs an internal step: 'Determine and collect slice-specific application performance statistics and slice usage pattern statistics related to service degradation', which involves a message to the ADAES. 3. The NSCE server performs another internal step: 'Corelate data and prepare network slice diagnostics report'. 4. Finally, the NSCE server sends a 'Network slice diagnostics reply' back to the VAL Server. + +Sequence diagram of Network slice diagnostics procedure + +**Figure 9.14.2.1-1: Network slice diagnostics procedure** + +1. The VAL server sends to NSCE server a network slice diagnostics request containing information about detected service degradation. +2. NSCE server determines which specific statistics to request from ADAES based on the indicated service degradation. If the service degradation is related to detected communication error, then slice usage pattern statistics are needed. If bad quality is reported from the VAL client slice-specific application performance statistics are needed. NSCE server collects the needed statistics based on the procedure described in TS23.436 clause 8.7.3. +3. Based on the received statistics information and input from VAL server, the NSCE server correlated data and prepares network slice diagnostics report about the needed diagnostics. +4. NSCE server sends network slice diagnostics reply to VAL server. + +## 9.14.3 Information flows + +### 9.14.3.1 General + +The following information flows are specified for Network slice diagnostics: + +- Network slice diagnostics request and response + +### 9.14.3.2 Network slice diagnostics request and response + +Table 9.14.3.2-1 and Table 9.14.3.2-2 describe information elements for the network slice diagnostics request and response between the VAL server and the NSCE server. + +**Table 9.14.3.2-1: Network slice diagnostics request** + +| Information element | Status | Description | +|----------------------------------------|--------|-----------------------------------------------------------------------------------------------| +| VAL information | M | The information of the VAL server. | +| Network Slice Diagnostics ID | M | Identifier of the network slice diagnostics. | +| Service degradation type | M | The information of service degradation. | +| > VAL service identity | M | Identifier of the VAL service to be monitored. | +| >ErrorsList | M | The list of registered errors by VAL server. | +| >> ErrorName | M | The name of the reported error: detected communication error; RTT above limit; QoS downgrade. | +| >> Network slice related Identifier(s) | M | Identifier(s) of the network slice to be checked. | +| >> UE(s) related Identifier(s) | O | Identifier(s) of the related UE(s). | +| >> Area of interest | O | The geographical or service area for which the requirement applies | +| >>StartTime | M | The start time point of the registered service degradation. | +| >>EndTime | M | The end time point of the registered service degradation. | + +**Table 9.14.3.2-2: Network slice diagnostics response** + +| Information element | Status | Description | +|--------------------------------|-------------------|----------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of network slice diagnostics request. | +| > Network slice Diagnostics ID | O
(see NOTE 1) | Identifier of the network slice diagnostics. | +| >StartTime | O
(see NOTE 1) | The start time point of the available data for network slice service degradation. | +| >EndTime | O
(see NOTE 1) | The start time point of the available data for network slice service degradation. | +| >Data type | O
(see NOTE 1) | The type of the reported data samples (UE data, network data, application data). | +| >Data output | O
(see NOTE 1) | The reported data related to the reported error(s) in the network slice diagnostics request. | +| >Cause | O
(see NOTE 2) | Indicates the cause of the network slice diagnostics request failure. | + +NOTE 1: Shall be present if the result is success. +NOTE 2: Shall be present if the result is failure. + +## 9.14.4 APIs + +### 9.14.4.1 General + +Table 9.14.3.2-1 and 9.14.3.2-2 illustrate the API for network slice diagnostics. + +**Table 9.14.4.1-1: List of APIs for the network slice diagnostics feature** + +| API Name | API Operations | Known Consumer(s) | Communication Type | +|-----------------------------------|---------------------------|-------------------|--------------------| +| SS_NSCE_Network Slice Diagnostics | Network Slice Diagnostics | VAL server | Request / Response | + +## 9.14.4.2 SS\_NSCE\_Network\_Slice\_Diagnostics + +### 9.14.4.2.1 General + +**API description:** This API enables the VAL server to communicate with the network slice capability enablement server for requesting network slice diagnostics over NSCE-S. + +### 9.14.4.2.2 Network\_Slice\_Diagnostics + +**API operation name:** Network\_Slice\_Diagnostics + +**Description:** Request for Network\_Slice\_Diagnostics to the NSCE server and receiving a response / result. + +**Known Consumers:** VAL server. + +**Inputs:** See table 9.14.3.2-1. + +**Outputs:** See table 9.14.3.2-2. + +## 9.15 Network slice fault management capability exposure + +### 9.15.1 General + +5GS is required to provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party according to operator policies. And network diagnostics is of key importance that helps with scanning, diagnosing and identifying problems within a network. Diagnostics includes gathering data and continuously providing sufficient fault diagnosis results that characterize the quality of the network connections and services. Exposure of relevant (and possibly aggregated) performance parameters ensures a quick reaction in case of failure as well as identifying network connectivity, performance and other related problems. Also, the alarm data from different sources (e.g., OAM, VAL server, NSCE client) can be used to help the third-party to diagnose the fault problem of the services, locate the fault causes, and to be aware of the potential fault. In TS 28.545 [23], the fault supervision management services are standardized by which the alarm of the network slice instance from network resource aspects can be subscribed and reported. This alarm information together with the application function's fault report and communication service related knowledge can be utilized by the NSCE to diagnose the cause of the service performance deterioration, locate the fault of the communication services, and expose the fault report to the third-party. + +For example, if the status of the required communication is not correct, the SEAL/NSCE derives this alarm information from application functions. In this case, it is the SEAL/NSCE's responsibility to detect whether this fault is caused by the 5GS network or not and exposed the fault report to the third-party. If it is, then the SEAL/NSCE may inform the management functions the location of the fault and ask for the maintenance of the managed functions to clear the fault. + +This service provides a possible procedure to illustrate the network slice fault management capability exposed by NSCE server. The performance data and alarm data from multiple sources is helpful to characterize the quality of the network connection. + +### 9.15.2 Procedure + +#### 9.15.2.1 Procedures on network slice fault management capability exposure + +Figure 9.15.2.1-1 illustrates the network slice fault management process to address the key issue 4 of network slice fault management. + +Pre-conditions: + +1. The network slice enabler layer is capable to interact with NEF and OAM system. +2. The VAL server has checked the status of application layer. + +![Sequence diagram illustrating the support for predictive slice modification in distributed NSCE server deployments. The diagram shows interactions between VAL Server, NSCE Server, NSCE Client, OAM, 5GC, and ADAE. The sequence starts with the VAL Server sending a fault diagnosis subscription to the NSCE Server. The NSCE Server responds. Then, the NSCE Server sends a subscription for network slice specific performance data and analytics data from 5GC, OAM system, and ADAE. Next, the NSCE Server subscribes to fault data from the OAM system. The NSCE Client sends an application fault data subscription to the NSCE Server. The NSCE Client sends an application fault data report to the NSCE Server. The NSCE Server performs network and service diagnosis. Finally, the NSCE Server sends fault diagnosis notifications to the VAL Server and the OAM system.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE Server + participant NSCE Client + participant OAM + participant 5GC + participant ADAE + + Note right of NSCE Server: 3. Subscribe network slice specific performance data and analytics data from 5GC,OAM system and ADAE + Note right of NSCE Server: 4. Subscribe to the fault data from OAM system + Note right of NSCE Server: 7. Network and service diagnosis + + VAL Server->>NSCE Server: 1. Fault diagnosis subscription + NSCE Server-->>VAL Server: 2. Response of fault diagnosis subscription + NSCE Server-->>5GC: 3. Subscribe network slice specific performance data and analytics data from 5GC,OAM system and ADAE + NSCE Server-->>OAM: 4. Subscribe to the fault data from OAM system + NSCE Client->>NSCE Server: 5. Application fault data subscribe + NSCE Client-->>NSCE Server: 6. Application fault data report + NSCE Server-->>VAL Server: 9. Fault diagnosis notification + NSCE Server-->>OAM: 8. Fault diagnosis notification + +``` + +Sequence diagram illustrating the support for predictive slice modification in distributed NSCE server deployments. The diagram shows interactions between VAL Server, NSCE Server, NSCE Client, OAM, 5GC, and ADAE. The sequence starts with the VAL Server sending a fault diagnosis subscription to the NSCE Server. The NSCE Server responds. Then, the NSCE Server sends a subscription for network slice specific performance data and analytics data from 5GC, OAM system, and ADAE. Next, the NSCE Server subscribes to fault data from the OAM system. The NSCE Client sends an application fault data subscription to the NSCE Server. The NSCE Client sends an application fault data report to the NSCE Server. The NSCE Server performs network and service diagnosis. Finally, the NSCE Server sends fault diagnosis notifications to the VAL Server and the OAM system. + +**Figure 9.15.2.1-1: Support for predictive slice modification in distributed NSCE server deployments** + +1. The VAL server sends a subscription to NSCE server to subscribe the fault diagnosis of the applications and networks. This request may be triggered by the errors of the applications detected by the VAL server itself, or the VAL server may periodically collect the fault diagnostic report subscribing to the NSCE. +2. NSCE server sends the response of the subscription to VAL server. +3. Optionally, on receiving the request from VAL server, NSCE server subscribes the performance data of network slice from 5GS. For OAM system, the APIs defined in clause 11.3, TS 28.532[7] is utilized. For CN functions, the APIs of Nnwdaf\_AnalyticsInfo service defined in clause 7.3, TS 23.288[4] can be utilized. + +The analytics data defined in clause 6.3 to clause 6.14, TS 23.288[4], network slice instance related performance data defined in clause 5, TS 28.552[19] and network analytics data in clause 8.3 and clause 8.4 TS 28.104[21] exposed by OAM system may be acquired. Also, the analytics result of slice-specific performance and slice usage analytics defined in TS 23.436[26] can be utilized. + +4. NSCE server subscribes the alarms of network slice instances from OAM system via the procedures defined in clause 6.1, TS 28.545[23], and the alarms are defined in clause 4.1.1.1, TS 32.111-1 [24], e.g., the fault of communication, environmental, equipment, processing error, QoS for device/resource/file/functionality/smallest. +5. NSCE server may subscribe the alarm information (e.g., the 5GS network is not work or the required performance is under the threshold which leads the service's problem) collected by NSCE client if possible. The information collected by the NSCE client depends on the third-parties' requirements and implementation. +6. NSCE client report the requested fault information to NSCE server. + +Note: The collection of fault data from NSCE client follows the mechanism defined in EVEX in SA4. + +7. Every time the notifications from the OAM, NSCE client or ADAEs are received, NSCE server correlates this data, diagnoses the causes of the fault of the applications or services by analysing the fault information from different sources and prepares report for the VAL to be notified about the respective fault event. For example, the RAN function of the slice instance which is utilized to support the service of the smart grid application, for a certain time duration, the smart grid suffered the bad experience caused by Service Availability Failure Events, + +and in the RAN function is detected continuously to report an alarm of environmental fault in the same time duration, then the environment fault may be the root cause of the Service Availability Failure and should be prioritized to be solved. The fault may be identified with "critical", "major", "minor", "ignore" to show its prioritization. + +8. If the NSCE server detects that the application/service error (reported from NSCE client) is caused by the 5GS, the VAL server may send the fault diagnosis report to OAM system to indicate the server fault which causes the application/service failure by utilizing the NSCE-OAM interface. + +NOTE: The APIs utilized to send the fault diagnosis report to OAM will re-utilize the fault management services in TS 28.532[7] exposed by EGMF as defined in TS 28.533[25]. + +9. NSCE server send a notification to VAL server with the fault diagnostics report prepared in step 7. + +### 9.15.3 Information flows + +#### 9.15.3.1 General + +The following information flows are specified for the network slice fault management capability exposure. + +#### 9.15.3.2 Fault diagnosis subscription request + +Table 9.15.3.2-1 describes information elements for fault diagnosis subscription. + +**Table 9.15.3.2-1: Fault diagnosis subscription** + +| Information element | Status | Description | +|---------------------------------------|--------|-----------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | The identifier of the VAL service for which the request applies | +| VAL UE ID list | O | The list of VAL UE IDs for which the request applies | +| Fault diagnosis ID | M | Identifier of the fault diagnosis task | +| Fault diagnosis information | M | The information of performance and analytics monitoring | +| > Network slice related Identifier(s) | O | Identifier(s) of the network slice to be monitored | + +#### 9.15.3.3 Response of fault diagnosis subscription + +Table 9.15.3.3-1 describes information elements for response of fault diagnosis subscription. + +**Table 9.15.3.3-1: Response of fault diagnosis subscription** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------| +| Fault diagnosis ID | M | Identifier of the fault diagnosis task | +| Result | M | The result of the request (positive or negative acknowledgement) | + +#### 9.15.3.4 Fault diagnosis notification + +Table 9.15.3.4-1 describes information elements for fault diagnosis notification. + +**Table 9.15.3.3-4: Fault diagnosis notification** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------| +| Fault Report ID | M | Identifier of the fault Report | +| FaultReport | M | The report of the fault diagnosis | +| >CorrelatedAlarmList | M | The list of the correlated alarms | +| >>CorrelatedAlarm | M | The correlated alarms | +| >rootCause | M | The root cause of the fault | + +## 9.15.4 APIs + +### 9.15.4.1 General + +Table 9.15.4.1-1 illustrates the APIs for the network slice fault management capability exposure. + +**Table 9.15.4.1-1: fault diagnosis request.** + +| API Name | API Operations | Communication Type | Consumer(s) | +|------------------------|------------------------------|-----------------------------|-------------| +| SS_NSCE_FaultDiagnosis | Fault_Diagnosis_Subscribe | subscription / notification | VAL server | +| | Fault_Diagnosis_Notification | | | + +### 9.15.4.2 SS\_NSCE\_FaultDiagnosis API + +#### 9.15.4.2.1 General + +**API description:** This API enables the VAL server to communicate with the network slice capability enablement server to request the fault diagnosis over NSCE-S. + +#### 9.15.4.2.2 Fault\_Diagnosis\_Subscribe + +**API operation name:** Fault\_Diagnosis\_Subscribe + +**Description:** The consumer subscribes to the network slice fault diagnosis + +**Known Consumers:** VAL server + +**Inputs:** See table 9.15.3.2-1 + +**Outputs:** See table 9.15.3.3-1 + +#### 9.15.4.2.3 Fault\_Diagnosis\_Notification + +**API operation name:** Fault\_Diagnosis\_Notification + +**Description:** The consumer notifies the network slice fault diagnosis results + +**Known Consumers:** VAL server + +**Inputs:** None + +**Outputs:** See table 9.15.3.4-1 + +## 9.16 Slice requirements verification and alignment capability exposure + +### 9.16.1 General + +Verticals can compare the QoS achieved by the provider with the QoS/slice requirements and its own experience of the QoS to verify if the QoS/Slice requirements are reasonably configured. To order a slice with certain slice requirements parameters and their values, the verticals will put their best effort into slice requirements translation. However, they are not able to guarantee that all the potential factors will be considered to generate the optimal slice requirements parameters on the first try. + +In some cases, there may be some unforeseen exceptions (e.g., unexpected traffic changes) and the current configured slice requirements parameters are not able to fulfil the verticals requirements (e.g., more resources are required to address the exceptions), the VAL client may also suffer unsatisfied experience. Or in some other cases, when the service is executed on the required slice, the slice may not fully match the service real-time running conditions, for example, maybe only 60% of the slice resource is used to support the service, and rest of the slice resource is always idle, or the slice resource is insufficient due to under-provisioning. + +Hence, NSCE is able to provide the capability of comparing the QoS achievement status together with the OAM QoS data versus real customer QoS data (e.g., Mean Opinion Score) collected from VAL client to check whether the existing QoS/Slice related data is able to satisfy the VAL clients and send periodically alignment notifications to VAL server for the slice requirements. + +### 9.16.2 Procedure + +#### 9.16.2.1 Procedures on slice requirements verification and alignment capability exposure + +Figure 9.16.2.1-1 provides a possible procedure of slice requirements verification and alignment capability exposure. + +Pre-conditions: + +1. The NSCE Server has subscribed to the service of network slice performance management provided by EGMF. + +![Sequence diagram illustrating the Slice requirements verification and alignment process between VAL Server, NSCE Server, NSCE Client, ADAE Server, and OAM.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE Server + participant NSCE Client + participant ADAE Server + participant OAM + + Note right of NSCE Server: 2. Authorization + Note right of NSCE Client: 4. Subscribe QoE data + Note right of OAM: 5. Subscribe performance data and analytics data from OAM system or ADAEs + Note right of NSCE Server: 6. Slice requirements verification and update + + VAL Server->>NSCE Server: 1. Slice requirements verification and alignment subscription + NSCE Server-->>VAL Server: 3. Response of slice requirements verification and alignment subscription + NSCE Server->>NSCE Client: 4. Subscribe QoE data + NSCE Server->>OAM: 5. Subscribe performance data and analytics data from OAM system or ADAEs + NSCE Server-->>VAL Server: 7. Slice requirements verification and alignment Notification + +``` + +Sequence diagram illustrating the Slice requirements verification and alignment process between VAL Server, NSCE Server, NSCE Client, ADAE Server, and OAM. + +**Figure 9.16.2.1-1: Slice requirements verification and alignment process** + +1. The VAL server sends slice requirements verification and alignment subscription NSCE server to require the NSCE server to check whether the slice requirements (by configuring the attributes of *serviceProfile*) matches the real network slice usage status, the request may include the S-NSSAI, the ID of the VAL server, the slice requirements parameters (attributes of *serviceProfile*) which is requested to be aligned. +2. The NSCE server checks if the VAL server is authorized to trigger the service of slice requirements alignment. +3. The NSCE server response to VAL server with the result of slice requirements verification and alignment request, e.g., the slice requirements alignment request is accepted. +4. The NSCE server may optionally subscribe the QoE data from the NSCE client. The QoE data can refer to the data defined in clause 16, TS 26.114[27]. Note: The QoE data collection from NSCE client follows the mechanism defined in EVEX work in SA4. +5. The NSCE server subscribes the network slice related performance data and KPIs (e.g., the average PRB usage, the distribution of the PRB usage) defined in TS 28.552[19]. The NSCE server can also subscribe the analytics data (both statistics and predictions) from MDAS and ADAEs. +6. NSCE server periodically receives the subscribed data (from steps 4 and 5) and compares the slice requirement parameters of network slice (the values of attributes of *serviceProfile*, e.g., *radioSpectrum*, the *maxNumberOfUEs*) with network slice performance statistics (e.g., active number of users, the average PRB usage, the distribution of the PRB usage of the S-NSSAI) to generate the optimal slice requirements for the required service (represented by S-NSSAI) of the vertical. This step depends on implementation (e.g., if in + +implementation specific time window the VAL client experience is satisfied while the network slice resources are with low utilization, the resources required in the slice requirements could be reduced based on predictions and statistics). + +7. Based on the analysis in step 6, the NSCE server periodically sends notifications to VAL server to inform the recommended changes of the slice requirements parameters. + +### 9.16.3 Information flows + +#### 9.16.3.1 General + +The following information flows are specified for slice requirements verification and alignment capability exposure. + +#### 9.16.3.2 Slice requirements verification and alignment subscription + +Table 9.16.3.2-1 describes information elements for slice requirements verification and alignment subscription. + +**Table 9.16.3.2-1: Slice requirements verification and alignment subscription** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | The identifier of the VAL service for which the requirement request applies | +| VAL UE ID list | O | The list of VAL UE IDs for which the requirement request applies | +| Slice identifier | M | The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server | +| Slice Requirements List | M | The list of the slice requirements which need to be aligned. | +| >sliceRequirement | M | The requirement which need to be aligned, this parameter refers to the attribute of serviceProfile defined in TS 28.531[5] | + +#### 9.16.3.3 Response of slice requirements verification and alignment subscription + +Table 9.16.3.3-1 describes information elements for response of slice requirements verification and alignment subscription. + +**Table 9.16.3.3-1: Response of slice requirements verification and alignment subscription** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| Result | M | The result of the subscription (positive or negative acknowledgement) | + +#### 9.16.3.4 Slice requirements verification and alignment notification + +Table 9.16.3.4-1 describes information elements for slice requirements verification and alignment notification. + +**Table 9.16.3.4-1: Slice requirements verification and alignment notification** + +| Information element | Status | Description | +|---------------------------------|--------|-------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | The identifier of the VAL service for which the requirement request applies | +| VAL UE ID list | O | The list of VAL UE IDs for which the requirement request applies | +| Slice identifier | M | The slice identifier (S-NSSAI, NSI ID or ENSI) which is mapped to the VAL application, if known by the VAL server | +| Updated Slice requirements info | M | The attributes and values of slice requirements | + +## 9.16.4 APIs + +### 9.16.4.1 General + +Table 9.16.4.1-1 illustrates the APIs for the network slice verification and alignment capability exposure. + +**Table 9.16.4.1-1: List of APIs for network slice verification and alignment** + +| API Name | API Operations | Communication Type | Consumer(s) | +|---------------------------------|--------------------------------------|---------------------------|-------------| +| SS_NSCE_SliceReq_VerifyAndAlign | SliceReq_VerifyAndAlign_Subscribe | Subscription/Notification | VAL server | +| | SliceReq_VerifyAndAlign_Notification | | | + +### 9.16.4.2 SS\_NSCE\_SliceReq\_VerifyAndAlign API + +#### 9.16.4.2.1 General + +**API description:** This API enables the VAL server to communicate with the network slice capability enablement server to consume the network slice requirements verification and alignment service. + +#### 9.16.4.2.2 SliceReq\_VerifyAndAlign\_Subscribe + +**API operation name:** SliceReq\_VerifyAndAlign + +**Description:** The consumer subscribe to the network slice requirements verification and alignment. + +**Known Consumers:** VAL server + +**Inputs:** See table 9.16.3.2-1 + +**Outputs:** See table 9.16.3.3-1 + +#### 9.16.4.2.3 SliceReq\_VerifyAndAlign\_Notification + +**API operation name:** SliceReq\_VerifyAndAlign\_Notification + +**Description:** The consumer is notified with the updated network slice requirements information according to the slice requirements verification and alignment. + +**Known Consumers:** VAL server + +**Inputs:** None + +**Outputs:** See table 9.16.3.4-1 + +## 9.17 Network Slice Information delivery + +### 9.17.1 General + +The NSCE layer provides the feature of Network Slice information delivery. The Network Slice information is necessary for the VAL server to manage the network slice for their service such as preparation, creation, activation and termination (tear-down) of network slice. + +The Network Slice information that is delivered to the VAL server depends upon network operator policy. The network slice capabilities and management options offered to the customer are determined by a business agreement prior to and outside of the scope of 3GPP standards. + +The NSCE server performs the below. + +- Retrieval of Network Slice ServiceProfile in 5GS (e.g., NSMF) as specified in 3GPP TS 28.532 [7] +- Conversion of Network Slice ServiceProfile (specified in 3GPP TS 28.541 [10]) to Network Slice Information +- Creation of Network Slice Information +- Storing of Network Slice Information +- Delivery of Network Slice Information to VAL server that the Network Slice Customer is authorized to use. + +NOTE: The Network Slice Information provided to the VAL server depends on service agreements. + +The VAL server as a Network Slice consumer makes use of the delivered Network Slice information for the Network Slice Lifecycle management for its service. + +### 9.17.2 Procedure + +#### 9.17.2.1 Network Slice Information delivery request + +This subclause depicts the procedure of the Network Slice Information delivery to the VAL server via NSCE server, when the VAL server requests the Network Slice Information after registration. + +Pre-condition: + +1. The NSCE server should have the agreement with MNO (NOP) for retrieval of ServiceProfile, if the NSCE server is the external entity. + +![Sequence diagram for Network Slice Information delivery request. Lifelines: VAL Server, NSCE server, 5GS. The sequence starts with 1. NS ServiceProfile Retrieval from 5GS to NSCE server. Then 2. NS Information Compose & Store within NSCE server. Next, 3. NS Info. Request from VAL Server to NSCE server. Then 4. Authorization within NSCE server. Finally, 5. NS Info. Response from NSCE server to VAL Server.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS + Note right of NSCE server: 1. NS ServiceProfile Retrieval + NSCE server->>NSCE server: 2. NS Information Compose & Store + VAL Server->>NSCE server: 3. NS Info. Request + Note right of NSCE server: 4. Authorization + NSCE server->>VAL Server: 5. NS Info. Response + +``` + +Sequence diagram for Network Slice Information delivery request. Lifelines: VAL Server, NSCE server, 5GS. The sequence starts with 1. NS ServiceProfile Retrieval from 5GS to NSCE server. Then 2. NS Information Compose & Store within NSCE server. Next, 3. NS Info. Request from VAL Server to NSCE server. Then 4. Authorization within NSCE server. Finally, 5. NS Info. Response from NSCE server to VAL Server. + +**Figure 9.17.2.1-1: Network Slice Information delivery request** + +1. The NSCE server retrieves the Network Slice ServiceProfile from 5GS (e.g., NSMF) when the NSCE server acting as a NSP prepares a Network Slice to be provided. The NSCE server follows the procedure to request/receive the Network Slice Service Profile with 'getMOIAttributes' operation as specified in 3GPP TS 28.532[7]. + +NOTE: If NSCE server and NSMF are in same operator, then the NSCE server gets access directly to NSMF. The delivered Network Slice Service Profile contains the values of attributes such as PLMN, S-NSSAI, SST, maximum number of UEs, maximum number of PDU sessions, Slice Coverage Area, Latency, and, Data volume, which specify the Network Slice characteristics, as specified in clause of ServiceProfile in 3GPP TS 28.541 [10]. + +2. The NSCE server, as Network Slice as a Service, creates and stores the Network Slice information. When NSCE server retrieves the Network Slice Information, it is necessary for NSCE server to convert the attributes in Network Slice ServiceProfile to the Network Slice information for readable information and to compose the Network Slice information, according to the NSP's policy. + +In order to reduce to request often the Network Slice Information Retrieval, the NSCE server stores the Network Slice information. + +3. The VAL server requests the Network Slice Information to the NSCE server. If the VAL server needs to know the specific attribute value for its service, then the attribute name of Network Slice Information (e.g., S-NSSAI, SST, Slice Coverage Area, etc.) can be added in the Request message. +4. The NSCE server performs to check whether the requesting VAL server is registered or not. The NSCE server identifies which the Network Slice Customer is authorized to use. +5. The NSCE server sends the Network Slice Information, if the VAL server is registered and authorized. The NSCE server rejects to the request of the Network Slice Information, if not registered. + +## 9.17.2.2 Network Slice Information delivery to NSCE client request + +This subclause depicts the procedure of the Network Slice Information delivery to the NSCE client via NSCE server. + +Pre-condition: + +1. The network slice has been allocated/created to VAL server. + +![Sequence diagram showing Network Slice Information delivery to NSCE client. Lifelines: VAL server, NSCE server, NSCE client. Steps: 1. VAL server sends Network Slice Information delivery request to NSCE server. 2. NSCE server sends Slice information delivery to NSCE client. 3. NSCE client performs slice information storage. 4. NSCE client sends Slice information delivery response to NSCE server. 5. NSCE server sends Network Slice Information delivery response to VAL server.](a0eb8d30ac11ba97b2733c187b89ff22_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant NSCE client + Note right of NSCE client: 3. slice information storage + VAL server->>NSCE server: 1. Network Slice Information delivery to NSCE client request + NSCE server->>NSCE client: 2. Slice information delivery + NSCE client-->>NSCE server: 4. Slice information delivery response + NSCE server->>VAL server: 5. Network Slice Information delivery to NSCE client request + +``` + +Sequence diagram showing Network Slice Information delivery to NSCE client. Lifelines: VAL server, NSCE server, NSCE client. Steps: 1. VAL server sends Network Slice Information delivery request to NSCE server. 2. NSCE server sends Slice information delivery to NSCE client. 3. NSCE client performs slice information storage. 4. NSCE client sends Slice information delivery response to NSCE server. 5. NSCE server sends Network Slice Information delivery response to VAL server. + +**Figure 9.17.2.2-1: Network Slice Information delivery to NSCE client** + +1. The VAL server sends a request to NSCE server to deliver the Network Slice Information to the NSCE Clients. The request includes the network slice information and indication of the UE notification with VAL UE's ID List. +2. The NSCE server delivers the Network Slice Information to the NSCE Clients of VAL UEs based on the VAL UE's ID list from step 1, in case the Network Slice Allocation is successful, if the NSCE server does not perform AF-driven guidance for URSP determination to 5GS. + +The Network Slice Information contains the VAL service ID, S-NSSAI, and DNN. + +3. The NSCE client stores and applies the Network Slice Information. + +NOTE: If the UE is provisioned with URSP rules by the network operator, the UE handles the precedence between the delivered network slice info via NSCE layer info and URSP rules as defined in clause 6.1.2.2.1 of 3GPP TS 23.503 [17]. How the UE uses the Network Slice info delivered via NSCE layer in relation to the URSP is implementation dependent. + +4. The NSCE client sends the Network Slice Allocation Information response to the NSCE server. +5. The NSCE server sends the response to the Network Slice Information delivery to NSCE client request. + +## 9.17.3 Information flows + +### 9.17.3.1 Network Slice Information delivery request + +Table 9.17.3.1-1 describes the information flows for Network Slice Information delivery from the VAL server to the NSCE server. + +**Table 9.17.3.1-1: Network Slice Information delivery request** + +| Information element | Status | Description | +|-------------------------------------------|--------|-----------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| Security credentials | M | Security credentials resulting from a successful authorization. | +| VAL service ID | M | The VAL service ID of the VAL application | +| Requested network slice information list | O | Network slice information that is requested by the VAL server | +| > S-NSSAI information request | O | Indicates to request S-NSSAI | +| > SST information request | O | Indicates SST | +| > Slice Coverage Area information request | O | Indicates slice coverage area | + +### 9.17.3.2 Network Slice Information delivery response + +Table 9.17.3.2-1 describes the information flows for Network Slice Information delivery response from the NSCE server to the VAL server. + +**Table 9.17.3.2-1: Network slice information response** + +| Information element | Status | Description | +|-----------------------------|-------------------|--------------------------------------------------------------------------------------| +| Result | M | Result includes success or failure of the Network Slice Information delivery request | +| > Network slice Information | O
(see NOTE 1) | Network slice information | +| >> S-NSSAI | O | S-NSSAI | +| >> SST | O | Slice/Service Type | +| >> Slice Coverage Area | O | Coverage area of the network slice | +| > Cause | O
(see NOTE 2) | Indicates the cause of Network Slice Information delivery request failure. | + +NOTE 1: Shall be present if the result is success and shall not be present otherwise. +NOTE 2: Shall be present if the result is failure and shall not be present otherwise. + +### 9.17.3.3 Slice Information delivery to NSCE client + +Table 9.17.3.3-1 describes information elements for the Slice Information delivery to NSCE client request between the NSCE server and the NSCE client. + +**Table 9.17.3.3-1: Slice Information delivery to NSCE client request** + +| Information element | Status | Description | +|-------------------------------------|--------|-----------------------------------------------------------------------------| +| VAL service ID | M | The identifier of the VAL service | +| NSCE server ID and address | M | The identifier and address of the NSCE server | +| VAL UE ID list | O | The identifiers of the VAL UEs which are impacted by the slice modification | +| >Network slice information | M | Network slice information | +| >> Network Slice related Identifier | M | The allocated slice identifier | +| >>DNN | O | The allocated DNN | + +### 9.17.3.4 Slice Information delivery to NSCE client + +Table 9.17.3.4-1 describes information elements for the Slice Information delivery to NSCE client response between the NSCE server and the NSCE client. + +**Table 9.17.3.4-1: Slice Information delivery to NSCE client response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------|-----------------|---------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the Slice Information delivery. | +| > Cause | O
(see NOTE) | Indicates the cause of Slice Information delivery request failure. | +| NOTE: Shall be present if the result is failure and shall not be present otherwise. | | | + +## 9.17.4 APIs + +### 9.17.4.1 General + +Table 9.17.4.1-1 illustrates the APIs for the Network Slice Information delivery. + +**Table 9.17.4.1-1: List of APIs for Network Slice Information delivery** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|------------------------|------------------------|---------------------|-------------| +| SS_NSCE_NSInfoDelivery | NSInfoDelivery_request | Request/Response | VAL Server | + +Table 9.17.4.1-2 illustrates the APIs for the Network Slice Information delivery to NSCE client. + +**Table 9.17.4.1-2: List of APIs for Network Slice Information delivery to NSCE client** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|-------------------------------|-----------------------|---------------------|-------------| +| SS_NSCE_NSInfoDelivery_Client | NSInfoDelivery_Client | Request/Response | VAL Server | + +### 9.17.4.2 SS\_NSCE\_NSInfoDelivery Get operation + +**API operation name:** SS\_NSCE\_NSInfoDelivery Get + +**Description:** The consumer requests to get Network Slice Information. + +**Inputs:** See clause 9.17.3.1. + +**Outputs:** See clause 9.17.3.2. + +See clause 9.17.2.1 for details of usage of this operation. + +### 9.17.4.3 SS\_NSCE\_NSInfoDelivery\_Client Request operation + +**API operation name:** SS\_NSCE\_NSInfoDelivery\_Client Request + +**Description:** The consumer requests to deliver the network slice information to NSCE client. + +**Inputs:** See table 9.17.3.3-1. + +**Outputs:** See table 9.17.3.4-1. + +See clause 9.17.2.2 for details of usage of this operation. + +## 9.18 Network Slice Allocation in NSaaS model + +### 9.18.1 General + +When in NSaaS model, the NSCE server performs the Network Slice allocation operation on behalf of the VAL server. The non-trusted 3rd party application (i.e., VAL server) cannot access to the 5GS management system directly. So, the + +NSCE server needs to perform the authentication and authorization for the registration of VAL server on behalf of 5G MnS. + +The Network Slice creation that is triggered by the VAL server depends upon network operator policy. The network slice capabilities and management options offered to the customer are determined by a business agreement prior to and outside of the scope of 3GPP standards. + +The VAL server can identify the Network slice in Network Slice creation request with the Network Slice indicator (e.g., S-NSSAI). + +Upon network slice allocation, the NSCE server acts as the network slice provisioning MnS consumer. The NSCE server requests 'AllocacatedNsi' operation to the network slice provisioning MnS producer as specified in 3GPP TS 28.531 [8]. When the 'AllocatedNsi' operation is received, the network slice provisioning MnS Producer in 5GS performs charging mechanism as specified in 3GPP TS 28.202 [28]. + +The NSCE server sends the allocated Network Slice information (e.g., S-NSSAI) to the NSCE Client, after the Network Slice allocation to the VAL server is successful. + +With the above regards, the NSCE server performs the below for the Network Slice Allocation for the VAL server. + +- Network Slice Allocation operation on behalf of VAL Server as specified in TS 28.531 [8] +- Delivery of the Network Slice Allocation result +- Delivery of the allocated Network Slice Information to NSCE client + +The VAL server as a Network Slice consumer makes use of the APIs provided from NSCE server to allocate the Network Slice for the Network Slice Lifecycle management for its service. + +## 9.18.2 Procedure + +### 9.18.2.1 Network Slice Allocation in NSaaS model + +This subclause depicts the procedure of the Network Slice Allocation in NSaaS model, when the VAL server needs to allocate the Network Slice, interaction with 5GS via the NSCE server. + +![Sequence diagram showing Network Slice Allocation in NSaaS model. Lifelines: VAL server, NSCE server, 5GS, NSCE client. Steps: 1. Order a Network Slice (VAL server to NSCE server); 2. Network slice allocation request (VAL server to 5GS); 3. Network slice allocation & AF Guidance on URSP rule determination per VAL UE (5GS to NSCE server); 4. Network slice allocation response (NSCE server to VAL server); 5. Network slice information delivery to NSCE client (NSCE server to NSCE client). A 'Network slice Information Delivery' bar spans from step 1 to step 5.](ddb807b8170ff5d73761b94ed0e370e8_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server + participant 5GS + participant NSCE client + + Note over VAL server, 5GS: Network slice Information Delivery + + VAL server->>NSCE server: 1. Order a Network Slice + VAL server->>5GS: 2. Network slice allocation request + 5GS->>NSCE server: 3. Network slice allocation & AF Guidance on URSP rule determination per VAL UE + NSCE server->>VAL server: 4. Network slice allocation response + NSCE server->>NSCE client: 5. Network slice information delivery to NSCE client +``` + +Sequence diagram showing Network Slice Allocation in NSaaS model. Lifelines: VAL server, NSCE server, 5GS, NSCE client. Steps: 1. Order a Network Slice (VAL server to NSCE server); 2. Network slice allocation request (VAL server to 5GS); 3. Network slice allocation & AF Guidance on URSP rule determination per VAL UE (5GS to NSCE server); 4. Network slice allocation response (NSCE server to VAL server); 5. Network slice information delivery to NSCE client (NSCE server to NSCE client). A 'Network slice Information Delivery' bar spans from step 1 to step 5. + +Figure 9.18.2.1-1: Network Slice Allocation in NSaaS model + +1. The VAL server makes a request to order the Network Slice. The VAL server specifies the Network Slice requirements for the VAL service. The Network Slice requirement at the VAL server may be specified with the attributes of GST (which results in NEST) as specified in GSMA NG.116. +2. The VAL server requests the Network Slice allocation with the Network Slice requirements. The Network Slice allocation request includes the VAL Service ID, VAL UE's ID List, and S-NSSAI. +3. The NSCE server performs the Network Slice Allocation. If the NSCE server act as NSaaS provider, and the existing allocated network slice could satisfied the Network Slice requirements, the NSCE server allocates the existing network slice to the VAL. Otherwise, the NSCE server as network slice provisioning MnS consumer requests of 'AllocacatedNsi' operation as specified in 3GPP TS 28.531 [8]. + +When the 'AllocatedNsi' operation is received, the network slice provisioning MnS Producer performs charging mechanism as specified in 3GPP TS 28.202 [28]. + +The NSCE server performs AF-driven guidance for URSP determination to 5GS per VAL UE. + +NOTE 1: According to the network operator policy, the NSCE server acting as AF may send the created network slice information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in TS 23.501 [16]). This guidance may create the new route selection parameters to indicate sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic. + +4. The NSCE server sends the result of Network Slice Allocation to the VAL server. +5. The NSCE server delivers the Network Slice Allocation Information to the NSCE Clients of VAL UEs based on the VAL UE's ID list from step 2, using the procedure defined in 9.17.2.2 step 2 – step 4, in case the Network Slice Allocation is successful, if the NSCE server does not perform AF-driven guidance for URSP determination to 5GS in step 3. The Network Slice Allocation Information contains the VAL service ID, S-NSSAI, and DNN. + +NOTE 2: If the UE is provisioned with URSP rules by the network operator, the UE handles the precedence between the delivered network slice info via NSCE layer info and URSP rules as defined in clause 6.1.2.2.1 of 3GPP TS 23.503 [17]. How the UE uses the Network Slice info delivered via NSCE layer in relation to the URSP is implementation dependent. + +### 9.18.3 Information flows + +#### 9.18.3.1 General + +The following information flows are specified for Network Slice Allocation: + +- Network Slice Allocation request and response. + +#### 9.18.3.2 Network Slice Allocation + +Table 9.18.3.2-1 and Table 9.18.3.2-2 describe information elements for Network Slice Allocation request and response between the VAL server and the NSCE server. + +**Table 9.18.3.2-1: Network Slice Allocation request** + +| Information element | Status | Description | +|-------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | Identifier of the application service | +| VAL UE's ID List | O | The list of VAL UE IDs for which the request applies | +| Area of interest | M | The geographical or service area for which the application service profile applies. | +| Network slice related Identifier(s) | O | The slice identifier | +| Network Slice requirements | O | The properties of network slice related requirement. If Service Profile is known by the VAL server, it can be provided to the NSCE server. The GST defined by GSMA (see clause 2.2 in [5]) and the performance requirements defined in clause 7 TS 22.261 [6] are all considered as input for it. | + +**Table 9.18.3.2-2: Network Slice Allocation response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL server ID | M | The identifier of the VAL server | +| VAL service ID | M | Identifier of the application service to be supported by the created slice related communication service. | +| Result | M | Indicates the success or failure of the slice related communication service creation | +| Network slice info List | O
(see NOTE 1) | The list of the network slice info allocated by NSCE | +| > Network slice info | O
(see NOTE 1) | The network slice info which includes the attributes and the corresponding values of network slice | +| >>S-NSSAI | O
(see NOTE 1) | The identifier of network slice | +| >>attributes of network slice | O
(see NOTE 1) | The list of attributes of the serviceProfile e.g, dLtThptPerSlice or latencies of network slice as defined in serviceProfile TS 28.541[10] | +| >>AttributeValues | O
(see NOTE 1) | The corresponding values of the attributes of the service profiles that determined by the NSCE server | +| Cause | O
(see NOTE 2) | Indicates the cause of creation failure | +| NOTE 1: Shall be present if the result is success and shall not be present otherwise | | | +| NOTE 2: Shall be present if the result is failure and shall not be present otherwise | | | + +## 9.18.4 APIs + +### 9.18.4.1 General + +Table 9.18.4.1-1 illustrates the API for Network Slice Allocation. + +**Table 9.18.4.1-1: SS\_NSCE\_NSAllocation** + +| API Name | API Operations | Operation Semantics | Consumer(s) | +|----------------------|--------------------------------|---------------------|-------------| +| SS_NSCE_NSAllocation | NSAllocation_Request /Response | Request /Response | VAL server | + +### 9.18.4.2 SS\_NSCE\_NSAllocation\_Request /Response operation + +**API operation name:** SS\_NSCE\_NSAllocation\_Request /Response + +**Description:** The consumer requests the network slice allocation. + +**Inputs:** See table 9.18.3.2-1. + +**Outputs:** See table 9.18.3.2-2. + +See clause 9.18.2.1 for details of usage of this operation. + +## 9.19 Authorization and authentication + +VAL server authorization and authentication are specified in 3GPP TS 33.434 [22], clause 5.1.1.8. + +# Annex A (informative): Deployment models + +## A.1 Deployment scenarios + +### A.1.1 General + +Based on the network slicing capability of the S-NSSAI granularity provided by SA2 and the network slicing capability of the NSI/S-NSSAI granularity provided by SA5, the NSCE service is provides network slicing management and control capabilities in the S-NSSAI granularity for vertical industries. + +A network slice can have only one owner and one NSCE service provider. NSCE service provider and slice owner can be different. For example the slice owner is VAL server, but the NSCE service provider is MNO. + +This clause describes examples of deployment models with respect to different deployment scenarios as follows. + +### A.1.2 Centralized NSCE deployment + +Figure A.1.2 provides a example of centralized deployment of NSCE server whose service area covering the whole PLMN. It is also possible slice coverage area to be smaller than the NSCE service area. + +The network slice capability enablement service is provided with the view of whole PLMN in this scenario. + +![Diagram illustrating centralized NSCE deployment. The diagram shows a VAL server and an NSCE server above a dashed line representing the NSCE service area. Below the dashed line is a 3GPP network system containing a 3GPP management system, 5GC, and RAN. The RAN is connected to multiple network slices labeled S-NSSAI-1, ..., S-NSSAI-N.](1b767467f421db10b013da3b055b941f_img.jpg) + +The diagram illustrates the centralized NSCE deployment architecture. At the top, a 'VAL server' is shown. Below it, an 'NSCE server' is positioned just above a horizontal dashed line that defines the 'NSCE service area'. Below this line, a large box represents the '3GPP network system'. Inside this system, on the left, is the '3GPP management system'. To its right are two stacked boxes labeled '5GC' and 'RAN'. Below the 'RAN' box, there are several dashed rectangular boxes representing network slices, labeled 'S-NSSAI-1', '...', and 'S-NSSAI-N'. + +Diagram illustrating centralized NSCE deployment. The diagram shows a VAL server and an NSCE server above a dashed line representing the NSCE service area. Below the dashed line is a 3GPP network system containing a 3GPP management system, 5GC, and RAN. The RAN is connected to multiple network slices labeled S-NSSAI-1, ..., S-NSSAI-N. + +**Figure A.1.2: Illustration of centralized NSCE deployment** + +### A.1.3 Distributed NSCE deployment + +The distributed deployment refers to the deployment model in which multiple NSCE servers are deployed by same provider, whose service area only covers some specific areas as shown below (based on geographical coordinates or TA list(s)). + +![Diagram illustrating distributed NSCE deployment. At the top, a box labeled 'VAL server(s)' is connected by a dashed line to a 'PLMN domain' box. Below the 'PLMN domain' box, two boxes labeled 'NSCE server #1' and 'NSCE server #2' are shown. Each NSCE server is associated with an 'NSCE service area' (labeled 'NSCE service area 1' and 'NSCE service area 2'). Inside each service area, there is a box containing 'OAM', '5GC', and 'RAN' components, with 'S-NSSAI-1 ... S-NSSAI-N' listed below the RAN component.](584c8bae39761224bd920bbc68831c1e_img.jpg) + +Diagram illustrating distributed NSCE deployment. At the top, a box labeled 'VAL server(s)' is connected by a dashed line to a 'PLMN domain' box. Below the 'PLMN domain' box, two boxes labeled 'NSCE server #1' and 'NSCE server #2' are shown. Each NSCE server is associated with an 'NSCE service area' (labeled 'NSCE service area 1' and 'NSCE service area 2'). Inside each service area, there is a box containing 'OAM', '5GC', and 'RAN' components, with 'S-NSSAI-1 ... S-NSSAI-N' listed below the RAN component. + +**Figure A.1.3: Illustration of distributed NSCE deployment** + +When there are multiple NSCE servers managed by same provider, NSCE server(s) can be subscribed for providing the network slice statistics to another NSCE server to provide a global view. + +There can be two use cases to provide the NSCE service in the distributed deployment: + +One use case is that the distributed deployed NSCE is about a slice service area which is equivalent to the edge/NPN's service area. For this scenario, if the distributed deployed NSCE wants to access the NEF/NWDAF/NSACF services or to receive policies from OAM, it needs to interact to the global NSCE. + +A further use case could be that some NSCE services (e.g. MnS discovery) are locally provided to VAL servers (for example as a micro-service), whereas other capabilities are provided for the whole PLMN area. So, the distributed NSCE includes a subset of capabilities which are edge native. The local deployment of such capabilities can allow for more efficient services to the VAL servers (e.g. for QoS verification, the edge deployed NSCE can receive more timely KQI/QoE measurements and can process them locally before triggering an event). + +### A.1.4 NPN NSCE deployment + +The NSCE architecture supports the deployment that NSCE server is deployed in NPN. + +Figure A.1.4 shows a deployment example of NSCE server deployment in the NPN. This case is valid if a geographical match between slice coverage area, NPN coverage area and NSCE service area is pre-configured. The matching may be pre-configured in the NSCE server by network operator based on the TA list or geographical coordinates. The NSCE server is deployed in Non-public network to provide the network slice capabilities exposure application service based on the interaction with NPN-5GC and NPN management system. + +![Figure A.1.4: Illustration of NPN NSCE deployment. The diagram shows an NPN (Non-Public Network) box containing a VAL server and an NSCE server. Below these, there are two horizontal bars representing NPN-5GC and NPN-RAN. To the left of these bars is an NPN-OAM box. The bars are divided into segments by vertical dashed lines, labeled S-NSSAI-1, ..., S-NSSAI-N at the bottom.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +Figure A.1.4: Illustration of NPN NSCE deployment. The diagram shows an NPN (Non-Public Network) box containing a VAL server and an NSCE server. Below these, there are two horizontal bars representing NPN-5GC and NPN-RAN. To the left of these bars is an NPN-OAM box. The bars are divided into segments by vertical dashed lines, labeled S-NSSAI-1, ..., S-NSSAI-N at the bottom. + +Figure A.1.4: Illustration of NPN NSCE deployment + +## A.1.5 Edge NSCE deployment + +The NSCE architecture supports the deployment that the NSCE server is deployed in EDN as an EAS to provide the network slice capabilities exposure application service, based on the interaction with 5GS pertaining the network slice, and edge computing management system. + +Figure A.1.5 shows the edge NSCE deployment cases when the NSCE server is deployed in the EDN using LADNs as described in Annex A.2.4 of TS 23.558 [22]. This case is valid if a geographical match between slice coverage area, LADN service area (which is EDN service area) and NSCE service area is pre-configured in the NSCE server. The matching can be based on the TA list or geographical coordinates. + +![Figure A.1.5: Illustration of edge NSCE deployment. The diagram shows three LADN (DNN) boxes: LADN(DNN-1), LADN(DNN-2), and Centralized DN. Each LADN box contains an NSCE server (EAS) and an EES. Below these are DNAI (Data Network Access Identifier) circles labeled DNAI-1, DNAI-2, and DNAI-3. At the bottom, there are two boxes representing NSCE Service area 1 and NSCE Service area 2, each containing a group of circles and labeled S-NSSAI-1 ... S-NSSAI-N. To the right of these areas is a PLMN box.](53e80f05e45f132bf76a96442a5507e9_img.jpg) + +Figure A.1.5: Illustration of edge NSCE deployment. The diagram shows three LADN (DNN) boxes: LADN(DNN-1), LADN(DNN-2), and Centralized DN. Each LADN box contains an NSCE server (EAS) and an EES. Below these are DNAI (Data Network Access Identifier) circles labeled DNAI-1, DNAI-2, and DNAI-3. At the bottom, there are two boxes representing NSCE Service area 1 and NSCE Service area 2, each containing a group of circles and labeled S-NSSAI-1 ... S-NSSAI-N. To the right of these areas is a PLMN box. + +Figure A.1.5: Illustration of edge NSCE deployment + +## A.2 Deployment of NSCE server(s) in relation to VAL server and 3GPP system + +To support the centralized/distributed deployment, the NSCE server(s) will have different deployment models and different relation with VAL server and 3GPP system. + +## A.2.1 Centralized NSCE deployment + +The NSCE server can be deployed in single PLMN operator domain (as a SEAL server as specified in Figure 8.2.1-1 TS 23.434), deployed in VAL service provider domain by vertical (as a SEAL server as specified in Figure 8.2.2-1 TS 23.434), or deployed outside of both the VAL service provider domain and PLMN operator domain i.e. in 3rd party domain (as a SEAL server as specified in Figure 8.2.3-1 TS 23.434). + +The deployment of NSCE server(s), with connections to 3GPP network systems in multiple PLMN operator domains (as a SEAL server as specified in Figure 8.2.2-2) is also supported. When the vertical consumer wants to get NSCE services in two countries which are operated by two different MNOs, the NSCE service provider has to interact with two 3GPP network systems. The NSCE server is either deployed in the VAL service provider domain or deployed separately in the 3rd party domain. + +## A.2.2 Distributed NSCE deployment + +The NSCE servers can be distributed in multiple PLMN domains (as a SEAL server as specified in TS 23.434 Figure 8.2.1-2, Figure 8.2.1-3), or distributed in single PLMN operator domain (as a SEAL server as specified in TS 23.434 Figure 8.2.1-4). The NSCE servers can also distributed in VAL service provider domain by vertical (as a SEAL server as specified in TS 23.434 Figure 8.2.2-3), or distributed deployed in 3rd party domain by 3rd party. The VAL server can communicate with multiple NSCE servers via NSCE-S as long as other NSCE servers are discovered and accessible. Or, the VAL server can communicate with other NSCE servers via NSCE-E if needed. + +--- + +## A.3 Deployment of NSCE server(s) in relation to SEAL + +The NSCE server(s) supports standalone deployment independent with other SEAL services, it can interact with other SEAL service(s) via SEAL-X interface as specified in Clause 6.2 TS 23.434, . + +The NSCE service(s) supports combined deployment with other SEAL services, it can interact with other SEAL service via service API as specified in clause 15 TS 23.434. + +## Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-06 | SA6#49-bis-e | | | | | TS skeleton | 0.0.0 | +| 2022-07 | SA6#49-bis-e | | | | | TS Skeleton agreed in SA6#49-bis-e: S6-221640, Implemented pCRs approved in SA6#49-bis-e: S6-221641, S6-221642, S6-221643, S6-221822, S6-221818. | 0.1.0 | +| 2022-09 | SA6#50-e | | | | | Implemented pCRs approved in SA6#50: S6-222146, S6-222197, S6-222407
Editorial changes by the rapporteur. | 0.2.0 | +| 2022-10 | SA6#51-e | | | | | Implemented pCRs approved in SA6#51: S6-223036, S6-223035, S6-222901, S6-222764.
Editorial changes by the rapporteur. | 0.3.0 | +| 2022-11 | SA6#52 | | | | | Implemented pCRs approved in SA6#51: S6-223449, S6-223517, S6-223595, S6-223557, S6-223207, S6-223477
Editorial changes by the rapporteur. | 0.4.0 | +| 2023-01 | SA6#52-bis-e | | | | | Implemented pCRs approved in SA6#52-bis-e: S6-230053, S6-230054, S6-230353, S6-230467, S6-230355, S6-230359, S6-230379, S6-230397, S6-230459, S6-230360, S6-230460, S6-230352, S6-230403, S6-230136, S6-230417, S6-230419, S6-230420, S6-230421, S6-230422, S6-230461
Editorial changes by the rapporteur. | 0.5.0 | +| 2023-03 | SA6#53 | | | | | Implemented pCRs approved in SA6#53: S6-230960, S6-230961, S6-230616, S6-231027, S6-231028, S6-230997, S6-231069, S6-230967, S6-231009, S6-230968, S6-230598
Editorial changes by the rapporteur. | 0.6.0 | +| 2023-03 | SA#99 | SP-230272 | | | | Presentation for information at SA#99 | 1.0.0 | +| 2023-03 | SA#99 | SP-230346 | | | | Correction of implementation of pCR S6-231009 and presentation for information at SA#99 | 1.1.0 | +| 2023-04 | SA6#54 | | | | | Implemented pCRs approved in SA6#54: S6-231499, S6-231616, S6-231617, S6-231618, S6-231619, S6-231467, S6-231259, S6-231258, S6-231620, S6-231338, S6-231445, S6-231621
Editorial changes by the rapporteur. | 1.2.0 | +| 2023-05 | SA6#55 | | | | | Implemented pCRs approved in SA6#55: S6-232092, S6-231800, S6-231802, S6-231803, S6-232093, S6-231805, S6-231806, S6-232094, S6-232095, S6-232096.
Editorial changes by the rapporteur. | 1.3.0 | +| 2023-06 | SA#100 | SP-230686 | | | | Presentation for approval at SA#100 | 2.0.0 | +| 2023-06 | SA#100 | SP-230686 | | | | MCC Editorial update for publication after TSG SA approval (SA#100) | 18.0.0 | +| 2023-12 | SA#102 | SP-231561 | 0002 | 2 | F | Solve the EN in registration | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23501/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/raw/rel-18/23_series/23501/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64981bce4367ae58c719726b8b56430973202998 --- /dev/null +++ b/raw/rel-18/23_series/23501/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef6ee37867c341e12d7ee2c252a954ee13546310a1af855adbf0eaa7d683f73f +size 154942 diff --git a/raw/rel-18/23_series/23501/04c7ffb4a475a374f52b88704ecd295f_img.jpg b/raw/rel-18/23_series/23501/04c7ffb4a475a374f52b88704ecd295f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d00a3cfad7919090dbfcbe0f0e88c15b45bc7b50 --- /dev/null +++ b/raw/rel-18/23_series/23501/04c7ffb4a475a374f52b88704ecd295f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52b881cd9763d92c24a91107c3c21efe52b7f1d4ebfe053255e501b1e8dc06d3 +size 19802 diff --git a/raw/rel-18/23_series/23501/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/raw/rel-18/23_series/23501/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35c5968622dba7d551abe057069e4b785a55810c --- /dev/null +++ b/raw/rel-18/23_series/23501/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2efd1c877d2b838fd7df211cfcac3f389743793e9ae37fb490ecd527d05bb0c6 +size 32013 diff --git a/raw/rel-18/23_series/23501/062ad684575a714449a7e040c0e1ec00_img.jpg b/raw/rel-18/23_series/23501/062ad684575a714449a7e040c0e1ec00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f13c24404150821b40f4d4c2536ca011b1ffaa7d --- /dev/null +++ b/raw/rel-18/23_series/23501/062ad684575a714449a7e040c0e1ec00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee41985a52440189c342ede79f1aa889d972a4a4d4bb3d0eb0e12c121452c45e +size 66765 diff --git a/raw/rel-18/23_series/23501/07b17a620c75522d53916a11e12d1bff_img.jpg b/raw/rel-18/23_series/23501/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7de6fd7f5adbe1f453bdcf1515268df143449508 --- /dev/null +++ b/raw/rel-18/23_series/23501/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c253a1ada759204fee5e916ac03f2140b564dbeff9dc3ebfc6e97d449dc28acc +size 25003 diff --git a/raw/rel-18/23_series/23501/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/raw/rel-18/23_series/23501/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..192ec888edabfb3ae483fb3566a4266e4f309377 --- /dev/null +++ b/raw/rel-18/23_series/23501/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a8984f6a4f278a12c029b62c48630fa6beb1031bb60f91ff58dcef7fd8ae044 +size 64603 diff --git a/raw/rel-18/23_series/23501/0a73b03fba21af142d619a9a662e6490_img.jpg b/raw/rel-18/23_series/23501/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cd3f223781df921cb0863e3887a15df4aa790d0 --- /dev/null +++ b/raw/rel-18/23_series/23501/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90c3d55114e9f6fa030c735053858df95c2e4424f8d202f3a9d366e51a15129a +size 69738 diff --git a/raw/rel-18/23_series/23501/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/raw/rel-18/23_series/23501/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0340e49a046d0243089c9a36f34331ca7537356c --- /dev/null +++ b/raw/rel-18/23_series/23501/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000af49162c9344e0a9ea82731072c68eedf61370630478f20b5e8a4ef550b8b +size 14413 diff --git a/raw/rel-18/23_series/23501/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg b/raw/rel-18/23_series/23501/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceaff7dae46916598bc65eb67a8ae0987caa31cc --- /dev/null +++ b/raw/rel-18/23_series/23501/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f9a441f350b88739c439369a30e7177f40396e38217de98d7d80bd8ab49e5e8 +size 61694 diff --git a/raw/rel-18/23_series/23501/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/raw/rel-18/23_series/23501/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..131fc94b8d954e6bc8b0585d7d62b79382859ebf --- /dev/null +++ b/raw/rel-18/23_series/23501/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20f9b08fb22ba386b1b3bb38ac186517354bf94557f43a4b7c655f6ed3ee4654 +size 56645 diff --git a/raw/rel-18/23_series/23501/1033dc9fde75540d224c907681b1b7aa_img.jpg b/raw/rel-18/23_series/23501/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a6bacbe649471da9f7ccfcaa990afe55a1e8113 --- /dev/null +++ b/raw/rel-18/23_series/23501/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:684e5571eafc81a535abbee5afaf84e623fb45081f09debe49683cac89a25713 +size 35611 diff --git a/raw/rel-18/23_series/23501/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/raw/rel-18/23_series/23501/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d94e6b552d8fb51c53984cd1d0e4fd10927c4bf --- /dev/null +++ b/raw/rel-18/23_series/23501/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd29f4b9b99eda9b7f937f5f6458ec0ce7754316c5e0d61670e99d5d768f7de5 +size 21467 diff --git a/raw/rel-18/23_series/23501/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/raw/rel-18/23_series/23501/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c03711b333b7f920c2e92bbcd529ed56f6bb49f --- /dev/null +++ b/raw/rel-18/23_series/23501/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:155d75947208bfdc384bd78b08521b33e15cf1f96de2dcd4b5b2a66ef7d04c93 +size 58195 diff --git a/raw/rel-18/23_series/23501/187bba66c887c745c512add37a577c5e_img.jpg b/raw/rel-18/23_series/23501/187bba66c887c745c512add37a577c5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8d6ef7250640d5673e7722b1c4f28eb6e437715 --- /dev/null +++ b/raw/rel-18/23_series/23501/187bba66c887c745c512add37a577c5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:077e2194af9bb643c00cb27b47ba3984e4efc720f10d524fb3355e377826bdda +size 15712 diff --git a/raw/rel-18/23_series/23501/187d05bf7ead21e1394b61320d8b3632_img.jpg b/raw/rel-18/23_series/23501/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1475885585ad007821f9a215bd8bbc374642fbe0 --- /dev/null +++ b/raw/rel-18/23_series/23501/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b817fcae687bfb027c7cc9c1219548cc5216ff9a5350ad10151c9a746a148bf2 +size 75432 diff --git a/raw/rel-18/23_series/23501/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/raw/rel-18/23_series/23501/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6620b99fc1d4616f4ff2181e9a9180aed90bfa75 --- /dev/null +++ b/raw/rel-18/23_series/23501/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be4db0e7112b34b0c6c02bc5af3f00fd0fd8c142fbcf0fe72092e56cd641d25d +size 46357 diff --git a/raw/rel-18/23_series/23501/1ad662a678c4f002de911d403f00de8e_img.jpg b/raw/rel-18/23_series/23501/1ad662a678c4f002de911d403f00de8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad9e7f6ae9ff8f2a26de0f5ff1acd070a94e98d6 --- /dev/null +++ b/raw/rel-18/23_series/23501/1ad662a678c4f002de911d403f00de8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9795d82529227a48bddcb27a9a818e8fbaa908ea06716c247ec842cc9882aad5 +size 34690 diff --git a/raw/rel-18/23_series/23501/1c140ee5d1a87186977da94a96bfa700_img.jpg b/raw/rel-18/23_series/23501/1c140ee5d1a87186977da94a96bfa700_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e21bb412733c3e69a52fe25e3491937d386739d9 --- /dev/null +++ b/raw/rel-18/23_series/23501/1c140ee5d1a87186977da94a96bfa700_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de6912ffa6653bfb27ed09f54c323b87b02b5678d9640abee9bc0ce71632f7b1 +size 42606 diff --git a/raw/rel-18/23_series/23501/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/raw/rel-18/23_series/23501/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9939e8b8d0b8af0e65c5febf0e07661912dd36d --- /dev/null +++ b/raw/rel-18/23_series/23501/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fa89c7c88188bd11452f2425aac50179b85f2c1ba16abea2c7d3f71c5345be7 +size 13908 diff --git a/raw/rel-18/23_series/23501/20136850feb70fd71c7d41cdae203ebb_img.jpg b/raw/rel-18/23_series/23501/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fac36bd772118eabf3d5193ab394353295518fac --- /dev/null +++ b/raw/rel-18/23_series/23501/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7d15c9a56957449ce8fe729ee589c3f8668f5cedd44523577861f67b9c61948 +size 6317 diff --git a/raw/rel-18/23_series/23501/24c9e038a791677ed33100667b64f7e6_img.jpg b/raw/rel-18/23_series/23501/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1546ca1fb8265b531d006e53580d69a6932445d --- /dev/null +++ b/raw/rel-18/23_series/23501/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16f2028f1d058f2a488d123f08c8d4ee418d2171654a14ca78b8f2bd8d814acb +size 21575 diff --git a/raw/rel-18/23_series/23501/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/23_series/23501/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fecf5a04341c4a7660a8437b51177cdf0f75cf5 --- /dev/null +++ b/raw/rel-18/23_series/23501/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:985f0bac837bec483d129a305400fb0912ad73fd4e5fe7fd3767b312aebc18db +size 11491 diff --git a/raw/rel-18/23_series/23501/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/raw/rel-18/23_series/23501/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff1185ce6df73211e0c83463aa79e7895b33a12 --- /dev/null +++ b/raw/rel-18/23_series/23501/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e2b03c9b3f138a49f060c9b170383f9ffdba4ad487672bc1858ebee46793252 +size 60774 diff --git a/raw/rel-18/23_series/23501/32ff77da4286b58c4778033acaa10836_img.jpg b/raw/rel-18/23_series/23501/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0585666e73e05d93d6865d3eeda8c2afb242f20b --- /dev/null +++ b/raw/rel-18/23_series/23501/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a926bc7350ce74bcc9a1ec3867cd7f49a99968f18435c031641cffcd1938fd94 +size 56898 diff --git a/raw/rel-18/23_series/23501/3376375fe7236a570fd0ee9448d9c4ee_img.jpg b/raw/rel-18/23_series/23501/3376375fe7236a570fd0ee9448d9c4ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cedff53c636bc28946c12e44e4ee587d1bb05d8 --- /dev/null +++ b/raw/rel-18/23_series/23501/3376375fe7236a570fd0ee9448d9c4ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ede3e5e970d665ff75b6cf0a687816c084b0f21e9777062a2003c1bc0429ca3d +size 15961 diff --git a/raw/rel-18/23_series/23501/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/raw/rel-18/23_series/23501/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1375768ce2f7baa02b0bd16ded9990374a85db3c --- /dev/null +++ b/raw/rel-18/23_series/23501/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a72c5e26cb60c6a5524919e5d7b9e19b42cde853eea406fdf3f33f02d5a2de01 +size 88701 diff --git a/raw/rel-18/23_series/23501/382a9c9e4816bd229191ab4591424dd8_img.jpg b/raw/rel-18/23_series/23501/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f5f15905f95da9cddf13ed53cfd8b0370e4519e --- /dev/null +++ b/raw/rel-18/23_series/23501/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b4be9123c834dbb0caa72df2cd07e6e8a2f8b1872ea94f45d1cafaaefb82a6e +size 63059 diff --git a/raw/rel-18/23_series/23501/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/raw/rel-18/23_series/23501/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1c337f54735fc8165c8884dfbda50c16ebda87d --- /dev/null +++ b/raw/rel-18/23_series/23501/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70554bcb5aea8686e9850f108e5e6347b0a785f601fd58b15b941b35a213e48a +size 41599 diff --git a/raw/rel-18/23_series/23501/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/raw/rel-18/23_series/23501/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc110d2e038a583f869aee3e639d7299be7775eb --- /dev/null +++ b/raw/rel-18/23_series/23501/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d789b07cbf3bd0982b1bdae51b998bc8756bdfefb5f8cbae1328528b15b43b5 +size 87491 diff --git a/raw/rel-18/23_series/23501/474a819357587e34949a3e110ff19b30_img.jpg b/raw/rel-18/23_series/23501/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b95d9560cb8a1a25987a9b551e423af402c78615 --- /dev/null +++ b/raw/rel-18/23_series/23501/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19d830f1c6cff8cae2290e84331acb6b19816ce253ccf32ff418ee5e8419b40c +size 15720 diff --git a/raw/rel-18/23_series/23501/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/raw/rel-18/23_series/23501/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe3f49751e13e3de9a17300fca33245a8a7fdc6c --- /dev/null +++ b/raw/rel-18/23_series/23501/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e01a409409a0c40f6b00aea5689cd3e570820776fff8f3b2f6a2df45a63cd5dc +size 70954 diff --git a/raw/rel-18/23_series/23501/492256bb98eb10f95553a7b1983c4b96_img.jpg b/raw/rel-18/23_series/23501/492256bb98eb10f95553a7b1983c4b96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0fae7483ec78dba941c7383ffc331840b3328b55 --- /dev/null +++ b/raw/rel-18/23_series/23501/492256bb98eb10f95553a7b1983c4b96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f38e64d393551672fee80c3b0a2acf3283c0a464176976be4e3e68b909d2eaae +size 73320 diff --git a/raw/rel-18/23_series/23501/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/raw/rel-18/23_series/23501/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96b66db10469dd24287274aa8b5ba8feed121719 --- /dev/null +++ b/raw/rel-18/23_series/23501/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8c748e45f200ec9d62098de43c844ce824fd7b32778fb673999307d14b1cdc8 +size 75063 diff --git a/raw/rel-18/23_series/23501/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/raw/rel-18/23_series/23501/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81fcedf8647df62b6bac7b03c27312e520661e61 --- /dev/null +++ b/raw/rel-18/23_series/23501/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d76f1ee437f8bb1a913d3fe68069d26718afcca32b2962ba154a89a92ba86d2b +size 48692 diff --git a/raw/rel-18/23_series/23501/523ab7b925beb555f88b2e1e1336974f_img.jpg b/raw/rel-18/23_series/23501/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3d4dc87cfeb075e31839efaf4146f67140ca3d8 --- /dev/null +++ b/raw/rel-18/23_series/23501/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b71ebfe5ef3584dece4909f17afd99d608adf9797638aec34c412dc375bc2da +size 50122 diff --git a/raw/rel-18/23_series/23501/552328a9daaf3bc0069424b500025880_img.jpg b/raw/rel-18/23_series/23501/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37790c79da3c3cf4996adc9c313a7d79baf023d7 --- /dev/null +++ b/raw/rel-18/23_series/23501/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0135cad4f580c83ab597aae954e74a1d08da014e1d421e4dd629ff6724ec6657 +size 59768 diff --git a/raw/rel-18/23_series/23501/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/raw/rel-18/23_series/23501/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62f67db47dfee4e2964a9b91f617c244ad17481e --- /dev/null +++ b/raw/rel-18/23_series/23501/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2e4115948d603bf507b986d53686a9d8f838d85c4ea2b587c85ce9325cb2a86 +size 26953 diff --git a/raw/rel-18/23_series/23501/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/raw/rel-18/23_series/23501/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d38062ac82ad67761f5c2029946e3ad78a1c8daa --- /dev/null +++ b/raw/rel-18/23_series/23501/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dbeefecc2cb0372eed66181b6ba25e05c19db4f68182ecbc54092360d4e8e3d +size 57730 diff --git a/raw/rel-18/23_series/23501/5a95b187de0044da69b7322e04761b86_img.jpg b/raw/rel-18/23_series/23501/5a95b187de0044da69b7322e04761b86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faf61ad1220dab41ce396ac5ddd130d6c369bdcb --- /dev/null +++ b/raw/rel-18/23_series/23501/5a95b187de0044da69b7322e04761b86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7815b44cb32dd7014bdd4ca5821fafa429f85592656168ddbb9425683509d47c +size 21366 diff --git a/raw/rel-18/23_series/23501/5bcaa554999322056447df1b81256bfc_img.jpg b/raw/rel-18/23_series/23501/5bcaa554999322056447df1b81256bfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ee708922d96c5339ac662c534f3734321a4e002 --- /dev/null +++ b/raw/rel-18/23_series/23501/5bcaa554999322056447df1b81256bfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7de82f7ab69424833d3ae8fb114b3adbf651c0261eced970fd1da9783c7e1068 +size 52250 diff --git a/raw/rel-18/23_series/23501/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/raw/rel-18/23_series/23501/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29e28b4d40cb32ea3135b02588bb9d6ac325b93c --- /dev/null +++ b/raw/rel-18/23_series/23501/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9af98515f684c8e3666c814be8d42c8b5a824fe37480c59782bbf4ecf9e3b41b +size 13085 diff --git a/raw/rel-18/23_series/23501/5dfc130b129ace4df375839020a5700d_img.jpg b/raw/rel-18/23_series/23501/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45184970bbf55afe8c320ce9206e54c7331bf196 --- /dev/null +++ b/raw/rel-18/23_series/23501/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cac0f732fe5721a3c0b5bd31ac4039b0928e3087c9759c8197cac4e4e4060e0 +size 21565 diff --git a/raw/rel-18/23_series/23501/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23501/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a759d7a4248f9d901b046311819429fd50b62dce --- /dev/null +++ b/raw/rel-18/23_series/23501/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38ef9199d2c6b88bc93181e4ef127de08de078d0559b6ee23fd471c25df2045f +size 8632 diff --git a/raw/rel-18/23_series/23501/6584b95e34ea1f0b67144aa841db0863_img.jpg b/raw/rel-18/23_series/23501/6584b95e34ea1f0b67144aa841db0863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90e10cd7d6e165dfb3d09f0ea834ec525aca0634 --- /dev/null +++ b/raw/rel-18/23_series/23501/6584b95e34ea1f0b67144aa841db0863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:beed862b703a8318289dcebe653e9915f4824d44b5bfbf8526a2f277260a6d43 +size 22969 diff --git a/raw/rel-18/23_series/23501/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/raw/rel-18/23_series/23501/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c28ee03a4c75e79b70bed79f6806572aab3a553 --- /dev/null +++ b/raw/rel-18/23_series/23501/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32d6d140489215ef67612bd0c3632a9292bb1733278c850aef7a59f1af1d61d4 +size 22350 diff --git a/raw/rel-18/23_series/23501/69e5f1993021af230d08c08aac97d9df_img.jpg b/raw/rel-18/23_series/23501/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea4d97f4edf611c97f12538fe6171f790ed305ee --- /dev/null +++ b/raw/rel-18/23_series/23501/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd015fcd1ae1ec70c9f062e24ad7fa718a87e4641e9a4bc26326d93d1fea0607 +size 29905 diff --git a/raw/rel-18/23_series/23501/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/raw/rel-18/23_series/23501/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b06baeebec14583650cdbf7ebe39439317c40e3f --- /dev/null +++ b/raw/rel-18/23_series/23501/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3a4defeb56410bcc474312a95c958b5ad80e09636178fd7d9670a9d8caa6496 +size 59247 diff --git a/raw/rel-18/23_series/23501/72bc1a2b64dd6bac8285f560440c1218_img.jpg b/raw/rel-18/23_series/23501/72bc1a2b64dd6bac8285f560440c1218_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21e5ca02aac69be1f17b65d2a5485f08195b76a7 --- /dev/null +++ b/raw/rel-18/23_series/23501/72bc1a2b64dd6bac8285f560440c1218_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42b72152c26a366060e997d367622b54703cede27487093666d8e26d8e39a4e8 +size 58641 diff --git a/raw/rel-18/23_series/23501/731f533b0599c8e42a063f06e4332045_img.jpg b/raw/rel-18/23_series/23501/731f533b0599c8e42a063f06e4332045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac65d5867df8c0158c5f9f65b5019a561e276041 --- /dev/null +++ b/raw/rel-18/23_series/23501/731f533b0599c8e42a063f06e4332045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94d121dfb8794fd7ff5cdc26ef06a7917ad6800e6868fee67f0a90ec95371a97 +size 24728 diff --git a/raw/rel-18/23_series/23501/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/raw/rel-18/23_series/23501/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47f40839d0198f0c723fcc611df64a020e67fd14 --- /dev/null +++ b/raw/rel-18/23_series/23501/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a516c71e96b28ce29ae0c33719662052b3c080e1a90c4155db06ba703309b6f3 +size 27507 diff --git a/raw/rel-18/23_series/23501/740442c999390734911677f01af0316d_img.jpg b/raw/rel-18/23_series/23501/740442c999390734911677f01af0316d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ce1b83804a19e81c4396701a0e7b6b03577cdb3 --- /dev/null +++ b/raw/rel-18/23_series/23501/740442c999390734911677f01af0316d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46e80ee5436e25541a4bbd53097e4de2bd7fb28f1797d2c3680971ba2585bbd4 +size 19868 diff --git a/raw/rel-18/23_series/23501/7a1dee155822446f7828dcb055c465c3_img.jpg b/raw/rel-18/23_series/23501/7a1dee155822446f7828dcb055c465c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d208997468636bb00e6c1c3d3c1aed35bc8829b --- /dev/null +++ b/raw/rel-18/23_series/23501/7a1dee155822446f7828dcb055c465c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b3789a7d6db5d5327386134239697174f77a49efa32b1c536341514f4477244 +size 42695 diff --git a/raw/rel-18/23_series/23501/7ed5d5770331f31ade15439a21c31425_img.jpg b/raw/rel-18/23_series/23501/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aeb82f34c2db37c7c6426a041e8f2ca80829c8a7 --- /dev/null +++ b/raw/rel-18/23_series/23501/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2989ba6fc60fd1427b9c83c82e0033f48086dcefbbbedaf9c98a88e8f6959169 +size 30954 diff --git a/raw/rel-18/23_series/23501/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/raw/rel-18/23_series/23501/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f70ffa7af9830aff46c2a409730ecc6dd7ba7fd --- /dev/null +++ b/raw/rel-18/23_series/23501/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f31ed0fef199dc59e105fbaeec385dbdd7cd7715e88e83fee181cc157c78a49 +size 58460 diff --git a/raw/rel-18/23_series/23501/896e86ed12aff206d302c64f2e3091fa_img.jpg b/raw/rel-18/23_series/23501/896e86ed12aff206d302c64f2e3091fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3589f10ed5dd107cd6f5af129318c41e28ce526 --- /dev/null +++ b/raw/rel-18/23_series/23501/896e86ed12aff206d302c64f2e3091fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:865feddc156e0d78d34c0548e8c1064804084c2af41a710911610ebf89ebb75a +size 45436 diff --git a/raw/rel-18/23_series/23501/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/raw/rel-18/23_series/23501/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c4fb0cbc7bf5c6b5ca43e09b7848ffaf120e131 --- /dev/null +++ b/raw/rel-18/23_series/23501/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47e54dd63f138d39de47c2d413fdd442aa72ec82efd3fe5974cc23167ad40016 +size 43565 diff --git a/raw/rel-18/23_series/23501/8a8517bfa4f6191c52c47697716255a9_img.jpg b/raw/rel-18/23_series/23501/8a8517bfa4f6191c52c47697716255a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e46f926e1812e2158c8f177b3731af423e2a2b9 --- /dev/null +++ b/raw/rel-18/23_series/23501/8a8517bfa4f6191c52c47697716255a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d65846ae007726352d6aec4adede6d040ea024db8e20add3ae0fc84ac5725a1 +size 43192 diff --git a/raw/rel-18/23_series/23501/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/raw/rel-18/23_series/23501/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77b63480eac1a15900223206b2bffbc95922eec5 --- /dev/null +++ b/raw/rel-18/23_series/23501/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4634e801688578aa642047e5727fc9f4e4ae964e89573cd7dc00200bbd257a51 +size 24254 diff --git a/raw/rel-18/23_series/23501/90df9788d66ecf65abf861caf76be5ca_img.jpg b/raw/rel-18/23_series/23501/90df9788d66ecf65abf861caf76be5ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c52cfa7a6a703316be6259193ad847645682cba1 --- /dev/null +++ b/raw/rel-18/23_series/23501/90df9788d66ecf65abf861caf76be5ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b734beb55378c155aa149070cafe491b55cb912c37ac5857a9841a685966011c +size 54388 diff --git a/raw/rel-18/23_series/23501/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/raw/rel-18/23_series/23501/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c159696ee6fc89e2542cdfe6a66f0cfac1fc5122 --- /dev/null +++ b/raw/rel-18/23_series/23501/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b64ac375b5d8707e5a377692689b83bae0d198e5538eba7978de718104b8113b +size 49836 diff --git a/raw/rel-18/23_series/23501/981668c6be5792b778cccb1af38477e2_img.jpg b/raw/rel-18/23_series/23501/981668c6be5792b778cccb1af38477e2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58c0ec4bd95e081c7694dc06b43a2f5b7b9d825b --- /dev/null +++ b/raw/rel-18/23_series/23501/981668c6be5792b778cccb1af38477e2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b847dd3b4f5f76a79a36b62b3054979fd49249853c68bff616be5bc23195ea25 +size 60959 diff --git a/raw/rel-18/23_series/23501/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/raw/rel-18/23_series/23501/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38297c1b10195942cabb2f0c1b9986449cf378e9 --- /dev/null +++ b/raw/rel-18/23_series/23501/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:190b901ccd48d944a45196036f1d3c6c8b3613f8457fe18414fc68e1e2904a73 +size 44844 diff --git a/raw/rel-18/23_series/23501/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/raw/rel-18/23_series/23501/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18d85d625b76da3f3f927d4601593245c898ded2 --- /dev/null +++ b/raw/rel-18/23_series/23501/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff846eff25449fe41aa35016fecebdb6fa019c5a26d26907f7828e136b8253ae +size 55311 diff --git a/raw/rel-18/23_series/23501/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/raw/rel-18/23_series/23501/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f030d389c34b02e7444ff18bc7a193a8a56de41d --- /dev/null +++ b/raw/rel-18/23_series/23501/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fd11fa78920e28dfaed209c049b1c27140f3b470c4a6701138febe713aa9644 +size 43001 diff --git a/raw/rel-18/23_series/23501/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/23_series/23501/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38513b01d07dddc6ac2512a2b578423d04f7ac7a --- /dev/null +++ b/raw/rel-18/23_series/23501/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8643d2f3c6b5990e5ee15a050ee3ddc8d89cfcd1b264d1947add74fef2f34509 +size 23870 diff --git a/raw/rel-18/23_series/23501/9d4bac4111fe96f0d6f746b95343cbd8_img.jpg b/raw/rel-18/23_series/23501/9d4bac4111fe96f0d6f746b95343cbd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2eb1aacae1f4bb35f336f439a5517915c34a5ba --- /dev/null +++ b/raw/rel-18/23_series/23501/9d4bac4111fe96f0d6f746b95343cbd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a034b8f5cb721754610bdd54a0812b0a7d983a3efc87bb60be5553a730ad979 +size 5028 diff --git a/raw/rel-18/23_series/23501/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/raw/rel-18/23_series/23501/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c612e9f4104c3fa6d774b29d50d9a064d3d77ffb --- /dev/null +++ b/raw/rel-18/23_series/23501/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0054a6ea45478418976b476c15fa0516a9b4cbfd63a2dbe051b63a16d773266 +size 84214 diff --git a/raw/rel-18/23_series/23501/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/23_series/23501/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29015ce8ddc3289db6b6ab927d75f86e719aa205 --- /dev/null +++ b/raw/rel-18/23_series/23501/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e02564f8bcdf608f353a6529c6975d427a5de36ec4bc2c1de6c9bca1f7f86c7c +size 8779 diff --git a/raw/rel-18/23_series/23501/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/raw/rel-18/23_series/23501/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66842e88961996df1cfcaba82484c2bbe46d4c60 --- /dev/null +++ b/raw/rel-18/23_series/23501/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83e3fbd0e8b9aeb1ceb2256b998bfda8b03bdcec80ffe32c93a60bdfa9eb5864 +size 21314 diff --git a/raw/rel-18/23_series/23501/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/raw/rel-18/23_series/23501/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61badd5461afa753dd366eabf7285d07e2814625 --- /dev/null +++ b/raw/rel-18/23_series/23501/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e6d3acb3d3ece3fe04f28c6e80360001cc731ebc0128b38ed65d047f8361c81 +size 59831 diff --git a/raw/rel-18/23_series/23501/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/raw/rel-18/23_series/23501/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fff5d7c9bd7df775fc11d22b10a86a264f8efdd --- /dev/null +++ b/raw/rel-18/23_series/23501/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c859b75ba699222dca5e36d6e5cdd689ec56c9f90292d227bee76d9ce4cdae2d +size 12561 diff --git a/raw/rel-18/23_series/23501/a3472689858b068ef469213682965325_img.jpg b/raw/rel-18/23_series/23501/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58853eff2d52fa13a8ea75f3c3bf7659332711c8 --- /dev/null +++ b/raw/rel-18/23_series/23501/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46b5c0bc7ebd93d3b497ab5e32e13aa54366332c33b853546c6fda2f6a5c8298 +size 50583 diff --git a/raw/rel-18/23_series/23501/a4b963a07cc368283154762c4b156fe7_img.jpg b/raw/rel-18/23_series/23501/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c200ec02543d33adc6db7cf14fd4ef0b1f41778 --- /dev/null +++ b/raw/rel-18/23_series/23501/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34d435743b508cdf8656f7742d066a440789cc289c28835701ea8de94d60c4c0 +size 45188 diff --git a/raw/rel-18/23_series/23501/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/raw/rel-18/23_series/23501/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d77f4a6eefa78dd9f8fd3759a013057ae8c10a1 --- /dev/null +++ b/raw/rel-18/23_series/23501/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c046d500004d3c921f856273e0b149268c5541a34a2664b9d1bebe4c1f86ab5 +size 59405 diff --git a/raw/rel-18/23_series/23501/a963ca41bde1669b18a4b783616f228b_img.jpg b/raw/rel-18/23_series/23501/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..671fb96246f33c853ee61ffc4f5bc8ef36c12f2e --- /dev/null +++ b/raw/rel-18/23_series/23501/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c97739fd0b544ea3a2667f5b3c8171c3503bb7d03d4d29249834b2a85bf25e18 +size 35010 diff --git a/raw/rel-18/23_series/23501/aa9441a5971655a79987d70fc551b26a_img.jpg b/raw/rel-18/23_series/23501/aa9441a5971655a79987d70fc551b26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6847f951bef126e903b465b2b2964bd191951de2 --- /dev/null +++ b/raw/rel-18/23_series/23501/aa9441a5971655a79987d70fc551b26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be65af1e02dddd72ac8042742fe802fb35e6bae27c483b743c6b965f03eed87b +size 46269 diff --git a/raw/rel-18/23_series/23501/aeb2a26a07219661191294dba528067a_img.jpg b/raw/rel-18/23_series/23501/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd613cfd270935fbd78a359c42af3a81b14b4caa --- /dev/null +++ b/raw/rel-18/23_series/23501/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e02837fd8ff1c610630d41ab46ea9d8c06c7e5dba37f89804fb2c7c5e7d991e +size 31888 diff --git a/raw/rel-18/23_series/23501/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/raw/rel-18/23_series/23501/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35a5f1916b95908eaf6e43b584cd64ec3d2f4cc9 --- /dev/null +++ b/raw/rel-18/23_series/23501/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c68357a95dfaad116301ca890816bf3e6e777632f872f0dbc5decdeced2f80c9 +size 13998 diff --git a/raw/rel-18/23_series/23501/b54ce9bffd341cd643e196d5f4538829_img.jpg b/raw/rel-18/23_series/23501/b54ce9bffd341cd643e196d5f4538829_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b7c372b40c461c64b81f53a762d6aa48692cccd --- /dev/null +++ b/raw/rel-18/23_series/23501/b54ce9bffd341cd643e196d5f4538829_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ba867b3183450f807f0362400c54d0d60bb91407d6e35fcba3dc4a9b905b79e +size 29449 diff --git a/raw/rel-18/23_series/23501/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/raw/rel-18/23_series/23501/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b6132a33025fe6080e9dec6d4f13f35dd51fe6 --- /dev/null +++ b/raw/rel-18/23_series/23501/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6198fd3b28cf194d749c74f77768c537d3efaaaee0e91090183326d0f1b8c10 +size 42449 diff --git a/raw/rel-18/23_series/23501/c0ca823603794512478906b302176bca_img.jpg b/raw/rel-18/23_series/23501/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a96944d9a58d6f9c6b58a7c2993327de503e95fc --- /dev/null +++ b/raw/rel-18/23_series/23501/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd8734dd8eabce5c618299f112ae54fdfe64dee93b67fd91bab56b5eb18e5413 +size 50874 diff --git a/raw/rel-18/23_series/23501/c1278da91cbcabe32628e589ebc47418_img.jpg b/raw/rel-18/23_series/23501/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46a464aa0839fc587f129f45986b27d80d1635d5 --- /dev/null +++ b/raw/rel-18/23_series/23501/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cd632f75357f7959b16cded11619e1a54d5c87d94d362bd08e06de8f684fd9e +size 13418 diff --git a/raw/rel-18/23_series/23501/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/raw/rel-18/23_series/23501/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e59c76556fc9af6825f0bd5045e245d497486a4 --- /dev/null +++ b/raw/rel-18/23_series/23501/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9aeebf7e8de488875cac922c8b3864a3b474e2241c2aa63ae121b52435a65237 +size 22356 diff --git a/raw/rel-18/23_series/23501/c85b57b2414f341860dfc338e1cf2509_img.jpg b/raw/rel-18/23_series/23501/c85b57b2414f341860dfc338e1cf2509_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2d184fac7904087f709db2f6cff92adee2978d8 --- /dev/null +++ b/raw/rel-18/23_series/23501/c85b57b2414f341860dfc338e1cf2509_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2faad9285dc2e53db823d788e90a4769826bc3e4f2a6793519ffddde5963baac +size 20982 diff --git a/raw/rel-18/23_series/23501/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/raw/rel-18/23_series/23501/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a974d2968da6ae1ed90b34a40a1b7d4eceb9c43 --- /dev/null +++ b/raw/rel-18/23_series/23501/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c3f7ff8f8dcc9469283d78c2b4fae31625f763e52016d45cc3c800b45a68845 +size 24516 diff --git a/raw/rel-18/23_series/23501/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/raw/rel-18/23_series/23501/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e576d88940af3ed975748f2d60e83e5a1ca8c07 --- /dev/null +++ b/raw/rel-18/23_series/23501/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:993e80d551228463eb0aaf2a4e66fc6746e1eec32b3f9a2a6d9901cf68ec3179 +size 38973 diff --git a/raw/rel-18/23_series/23501/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/raw/rel-18/23_series/23501/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ca97a9c0ee7c411f7d8ab08e6dbbc5951325183 --- /dev/null +++ b/raw/rel-18/23_series/23501/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96bf15598d4147b9b97991c3c61c3dce45879bb62b3545720f13058ed627e423 +size 25086 diff --git a/raw/rel-18/23_series/23501/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/raw/rel-18/23_series/23501/d17f75945bbb3feb84a153ecfedb9b81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b8cccd9e12402b300365c6c58118b21d7f4df93 --- /dev/null +++ b/raw/rel-18/23_series/23501/d17f75945bbb3feb84a153ecfedb9b81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bed969845b5613ef73dcf0b214a8edfe0e9293511b8e30620930eabcaabca06 +size 55005 diff --git a/raw/rel-18/23_series/23501/d4ed35f72863013455b8f015e0f2e47e_img.jpg b/raw/rel-18/23_series/23501/d4ed35f72863013455b8f015e0f2e47e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6acea7dfdad189f41632590c3fb326af156b6bc --- /dev/null +++ b/raw/rel-18/23_series/23501/d4ed35f72863013455b8f015e0f2e47e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb77bfc5e5fa7750b7ea1fa052befc850922aa2aed9d71a2e43478c163f50053 +size 36245 diff --git a/raw/rel-18/23_series/23501/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/raw/rel-18/23_series/23501/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2f6ee3fe793fd477b4b1fbda5e08a0b3858d299 --- /dev/null +++ b/raw/rel-18/23_series/23501/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df168af5eed99838f1e835a6e8abb5c7e104b7ce0a4c291d82c9946b54565d93 +size 11582 diff --git a/raw/rel-18/23_series/23501/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/raw/rel-18/23_series/23501/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cde316488e1aedfa759e6b5d0aa2083c4e25a68 --- /dev/null +++ b/raw/rel-18/23_series/23501/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f72558083c78128ec43132908335ecb93c391a313fec65367d6005a1bf4188c +size 19375 diff --git a/raw/rel-18/23_series/23501/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/raw/rel-18/23_series/23501/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90edb707fdf3c45f9f4c705e66d25954d8afbe7f --- /dev/null +++ b/raw/rel-18/23_series/23501/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:495865ea082eb0fca42ab050f3449890b96720886682585fb50ef42b06d37211 +size 15502 diff --git a/raw/rel-18/23_series/23501/dd380ccd5aca1151074fede04826f1a4_img.jpg b/raw/rel-18/23_series/23501/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b2e85f84d88e23a3e0ca9beaccdc0f620d68c09 --- /dev/null +++ b/raw/rel-18/23_series/23501/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:975a38df87c8520b033c26033827da04f0d603715990fb8cad7060cc284ecb2d +size 62955 diff --git a/raw/rel-18/23_series/23501/dd5771673aececa53d42ece89218299d_img.jpg b/raw/rel-18/23_series/23501/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..310d7954035906226d3c3cc1b9bd92cb040c9324 --- /dev/null +++ b/raw/rel-18/23_series/23501/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4594513dd8a1c69d1fde8fa6d26f10fb88030495745e42d3cb9992fd120d5d57 +size 45219 diff --git a/raw/rel-18/23_series/23501/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg b/raw/rel-18/23_series/23501/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26a01088dba17efb288df1391aeb59410e731086 --- /dev/null +++ b/raw/rel-18/23_series/23501/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e86b1e5f650483a66cb2800f1bda4d60670febaeb3c6fd8c4fd0ea4d8f65f262 +size 52672 diff --git a/raw/rel-18/23_series/23501/e05122559f56af5699789b7118d8fe87_img.jpg b/raw/rel-18/23_series/23501/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..425f9432b91fe8bf9fe826d6f2b1691409a3612b --- /dev/null +++ b/raw/rel-18/23_series/23501/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a285917004547904e9ea35a08e0251251b8f25320aafe467aa812fdfa705a6d4 +size 46215 diff --git a/raw/rel-18/23_series/23501/e05434e963901d7e9c0bf5a6758200ed_img.jpg b/raw/rel-18/23_series/23501/e05434e963901d7e9c0bf5a6758200ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80e52f2b192d12146e73dd7f88d876f58b5028fb --- /dev/null +++ b/raw/rel-18/23_series/23501/e05434e963901d7e9c0bf5a6758200ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41184ebf8bbf4f4ad39b3d1d53b1449e00539da2c3d99b98d36fef40fcc254fc +size 34895 diff --git a/raw/rel-18/23_series/23501/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/raw/rel-18/23_series/23501/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58fad5399c04e021159c5c37943943dc62900d89 --- /dev/null +++ b/raw/rel-18/23_series/23501/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0959dc5f480d15b50fe4760078627b8fdd939571cd2ad6d64528c0821aad7a58 +size 60271 diff --git a/raw/rel-18/23_series/23501/e3eebf9854831ba50eca8b26c468f65e_img.jpg b/raw/rel-18/23_series/23501/e3eebf9854831ba50eca8b26c468f65e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb943e9c1209768b55776ca5c018e85d14c996c --- /dev/null +++ b/raw/rel-18/23_series/23501/e3eebf9854831ba50eca8b26c468f65e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03d9936d806f167e0114a82f0f56034496d47071baa7eedf5bb88acebda1527d +size 39196 diff --git a/raw/rel-18/23_series/23501/e4a14961bdc9882e296b25f7ae5f9760_img.jpg b/raw/rel-18/23_series/23501/e4a14961bdc9882e296b25f7ae5f9760_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e02ff4adb45ddb1815ccbe2da22e25b131dabb7c --- /dev/null +++ b/raw/rel-18/23_series/23501/e4a14961bdc9882e296b25f7ae5f9760_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e71b681b358399cc6d7a8fc850a7d5b2c862ccd5bda381197fafed6a93c73c2 +size 23934 diff --git a/raw/rel-18/23_series/23501/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg b/raw/rel-18/23_series/23501/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88ac2f7881f1302816a99b6810b2a4dbbc88e687 --- /dev/null +++ b/raw/rel-18/23_series/23501/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b6acc3b64538825399422bf8958ad17a64fa32d69aaf329e5d89a1e95ee3aa4 +size 27694 diff --git a/raw/rel-18/23_series/23501/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/23_series/23501/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7446d6fb5867847c969817467eddb1661a6c8a9d --- /dev/null +++ b/raw/rel-18/23_series/23501/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13a228e9c3259e3c69e50a1245b095aeb9222366468a25c55b6dd9ee35b9ecbb +size 60955 diff --git a/raw/rel-18/23_series/23501/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/raw/rel-18/23_series/23501/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c61fe7ef4b3fedd87e9df92868f5d0737905d07d --- /dev/null +++ b/raw/rel-18/23_series/23501/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:067ffeaac5bb5ec4e7d54f417b642688235b1e2feb4b700a5fccda73bf6f6df0 +size 62181 diff --git a/raw/rel-18/23_series/23501/f324fbc5d5af1e4da9cd932389f0064c_img.jpg b/raw/rel-18/23_series/23501/f324fbc5d5af1e4da9cd932389f0064c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..353977ce96060d1276152bb2260023487d1229d3 --- /dev/null +++ b/raw/rel-18/23_series/23501/f324fbc5d5af1e4da9cd932389f0064c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:544d6d85b3416a1c2df55b6be08b54ce0e078a16649ea62c4ef36ebc8bead46d +size 16901 diff --git a/raw/rel-18/23_series/23501/fbfa653853daf5541118a9ddecb92284_img.jpg b/raw/rel-18/23_series/23501/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b47d7be4ce0e0512bfacadb7117d3859f83074 --- /dev/null +++ b/raw/rel-18/23_series/23501/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17f240c139c2a294e43eb715aaecf7d88f2972d1a63f8afb77058743285e5e78 +size 13296 diff --git a/raw/rel-18/23_series/23501/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/raw/rel-18/23_series/23501/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6671f5dfd45c2b3dff478a75bff717a74d8b2dd2 --- /dev/null +++ b/raw/rel-18/23_series/23501/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac7c0075e0664240951a3e25f373fe2d54bf40478b86e05c44f799c450100bb8 +size 75682 diff --git a/raw/rel-18/23_series/23501/fd9522380f09785d1f781cfc81b3d56e_img.jpg b/raw/rel-18/23_series/23501/fd9522380f09785d1f781cfc81b3d56e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..417e7323025d6b6e8e6b7637c8515ddfac5f9c75 --- /dev/null +++ b/raw/rel-18/23_series/23501/fd9522380f09785d1f781cfc81b3d56e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f5feb887e552a43f27e638fa44d8e88d44d7519b532859fa0d31ded7766eaf1 +size 17404 diff --git a/raw/rel-18/23_series/23501/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/23_series/23501/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36c0ef99ba2fdb4f0cd4250075bc69b9a6892059 --- /dev/null +++ b/raw/rel-18/23_series/23501/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68cc4fb6436609892fde9861ab9053a822d4290234656002952c74dc145c0ec4 +size 40995 diff --git a/raw/rel-18/23_series/23501/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/raw/rel-18/23_series/23501/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4586db12819ee2bbf813c7a3bd3762fde5e9f904 --- /dev/null +++ b/raw/rel-18/23_series/23501/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2874fc5f03dcc51cadb56f7bf76d50d93ee0b172a93a1419935f1e596a3b14c9 +size 30547 diff --git a/raw/rel-18/23_series/23501/raw.md b/raw/rel-18/23_series/23501/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ed4ec169919b448f3a697e21dffe0a6e1eec3870 --- /dev/null +++ b/raw/rel-18/23_series/23501/raw.md @@ -0,0 +1,23632 @@ +# 3GPP TS 23.501 V18.4.0 (2023-12) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 22 | +| 1 Scope..... | 23 | +| 2 References..... | 23 | +| 3 Definitions and abbreviations ..... | 30 | +| 3.1 Definitions..... | 30 | +| 3.2 Abbreviations ..... | 37 | +| 4 Architecture model and concepts..... | 40 | +| 4.1 General concepts ..... | 40 | +| 4.2 Architecture reference model..... | 41 | +| 4.2.1 General ..... | 41 | +| 4.2.2 Network Functions and entities..... | 41 | +| 4.2.3 Non-roaming reference architecture..... | 42 | +| 4.2.4 Roaming reference architectures ..... | 46 | +| 4.2.5 Data Storage architectures..... | 50 | +| 4.2.5a Radio Capabilities Signalling optimisation ..... | 51 | +| 4.2.6 Service-based interfaces ..... | 52 | +| 4.2.7 Reference points ..... | 53 | +| 4.2.8 Support of non-3GPP access ..... | 56 | +| 4.2.8.0 General..... | 56 | +| 4.2.8.1 General Concepts to Support Trusted and Untrusted Non-3GPP Access ..... | 56 | +| 4.2.8.1A General Concepts to support Wireline Access ..... | 57 | +| 4.2.8.2 Architecture Reference Model for Trusted and Untrusted Non-3GPP Accesses ..... | 58 | +| 4.2.8.2.1 Non-roaming Architecture ..... | 58 | +| 4.2.8.2.2 LBO Roaming Architecture ..... | 59 | +| 4.2.8.2.3 Home-routed Roaming Architecture..... | 61 | +| 4.2.8.3 Reference Points for Non-3GPP Access..... | 63 | +| 4.2.8.3.1 Overview ..... | 63 | +| 4.2.8.3.2 Requirements on Ta ..... | 64 | +| 4.2.8.4 Architecture Reference Model for Wireline Access network..... | 64 | +| 4.2.8.5 Access to 5GC from devices that do not support 5GC NAS over WLAN access..... | 65 | +| 4.2.8.5.1 General ..... | 65 | +| 4.2.8.5.2 Reference Architecture..... | 66 | +| 4.2.8.5.3 Network Functions ..... | 66 | +| 4.2.8.5.4 Reference Points..... | 66 | +| 4.2.9 Network Analytics architecture..... | 67 | +| 4.2.10 Architecture Reference Model for ATSSS Support ..... | 67 | +| 4.2.11 Architecture for 5G multicast-broadcast services ..... | 69 | +| 4.2.12 Architecture for Proximity based Services (ProSe) in 5GS ..... | 69 | +| 4.2.13 Architecture enhancements for Edge Computing..... | 69 | +| 4.2.14 Architecture for Support of Uncrewed Aerial Systems connectivity, identification and tracking..... | 69 | +| 4.2.15 Architecture to support WLAN connection using 5G credentials without 5GS registration ..... | 69 | +| 4.2.16 Architecture to support User Plane Information Exposure via a service-based interface..... | 73 | +| 4.2.17 Architecture for Ranging based services and Sidelink Positioning..... | 73 | +| 4.3 Interworking with EPC..... | 74 | +| 4.3.1 Non-roaming architecture..... | 74 | +| 4.3.2 Roaming architecture..... | 74 | +| 4.3.3 Interworking between 5GC via non-3GPP access and E-UTRAN connected to EPC..... | 76 | +| 4.3.3.1 Non-roaming architecture ..... | 76 | +| 4.3.3.2 Roaming architecture..... | 77 | +| 4.3.4 Interworking between ePDG connected to EPC and 5GS..... | 79 | +| 4.3.4.1 Non-roaming architecture ..... | 79 | +| 4.3.4.2 Roaming architectures ..... | 80 | +| 4.3.5 Service Exposure in Interworking Scenarios..... | 82 | +| 4.3.5.1 Non-roaming architecture..... | 82 | +| 4.3.5.2 Roaming architectures ..... | 83 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------------|-----| +| 4.4 | Specific services..... | 84 | +| 4.4.1 | Public Warning System ..... | 84 | +| 4.4.2 | SMS over NAS ..... | 84 | +| 4.4.2.0 | General..... | 84 | +| 4.4.2.1 | Architecture to support SMS over NAS ..... | 84 | +| 4.4.2.2 | Reference point to support SMS over NAS..... | 86 | +| 4.4.2.3 | Service based interface to support SMS over NAS ..... | 86 | +| 4.4.3 | IMS support ..... | 86 | +| 4.4.4 | Location services ..... | 87 | +| 4.4.4.1 | Architecture to support Location Services..... | 87 | +| 4.4.4.2 | Reference point to support Location Services ..... | 87 | +| 4.4.4.3 | Service Based Interfaces to support Location Services ..... | 87 | +| 4.4.5 | Application Triggering Services..... | 87 | +| 4.4.6 | 5G LAN-type Services ..... | 87 | +| 4.4.6.1 | User plane architecture to support 5G LAN-type service..... | 87 | +| 4.4.6.2 | Reference points to support 5G LAN-type service..... | 88 | +| 4.4.7 | MSISDN-less MO SMS Service ..... | 88 | +| 4.4.8 | Architecture to enable Time Sensitive Communication, Time Synchronization and Deterministic Networking ..... | 88 | +| 4.4.8.1 | General..... | 88 | +| 4.4.8.2 | Architecture to support IEEE Time Sensitive Networking ..... | 89 | +| 4.4.8.3 | Architecture for AF requested support of Time Sensitive Communication and Time Synchronization ..... | 90 | +| 4.4.8.4 | Architecture to support IETF Deterministic Networking ..... | 90 | +| 5 | High level features ..... | 91 | +| 5.1 | General ..... | 91 | +| 5.2 | Network Access Control ..... | 92 | +| 5.2.1 | General ..... | 92 | +| 5.2.2 | Network selection..... | 92 | +| 5.2.2a | Void..... | 92 | +| 5.2.3 | Identification and authentication ..... | 92 | +| 5.2.4 | Authorisation ..... | 92 | +| 5.2.5 | Access control and barring ..... | 92 | +| 5.2.6 | Policy control..... | 93 | +| 5.2.7 | Lawful Interception ..... | 93 | +| 5.3 | Registration and Connection Management ..... | 93 | +| 5.3.1 | General ..... | 93 | +| 5.3.2 | Registration Management..... | 93 | +| 5.3.2.1 | General..... | 93 | +| 5.3.2.2 | 5GS Registration Management states ..... | 94 | +| 5.3.2.2.1 | General ..... | 94 | +| 5.3.2.2.2 | RM-DEREGISTERED state ..... | 94 | +| 5.3.2.2.3 | RM-REGISTERED state..... | 94 | +| 5.3.2.2.4 | 5GS Registration Management State models..... | 95 | +| 5.3.2.3 | Registration Area management..... | 95 | +| 5.3.2.4 | Support of a UE registered over both 3GPP and Non-3GPP access ..... | 97 | +| 5.3.3 | Connection Management..... | 98 | +| 5.3.3.1 | General..... | 98 | +| 5.3.3.2 | 5GS Connection Management states ..... | 99 | +| 5.3.3.2.1 | General ..... | 99 | +| 5.3.3.2.2 | CM-IDLE state..... | 99 | +| 5.3.3.2.3 | CM-CONNECTED state..... | 99 | +| 5.3.3.2.4 | 5GS Connection Management State models..... | 100 | +| 5.3.3.2.5 | CM-CONNECTED with RRC_INACTIVE state..... | 100 | +| 5.3.3.3 | NAS signalling connection management..... | 103 | +| 5.3.3.3.1 | General ..... | 103 | +| 5.3.3.3.2 | NAS signalling connection establishment..... | 103 | +| 5.3.3.3.3 | NAS signalling connection Release ..... | 103 | +| 5.3.3.4 | Support of a UE connected over both 3GPP and Non-3GPP access ..... | 103 | +| 5.3.4 | UE Mobility..... | 104 | +| 5.3.4.1 | Mobility Restrictions ..... | 104 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------|-----| +| 5.3.4.1.1 | General ..... | 104 | +| 5.3.4.1.2 | Management of Service Area Restrictions..... | 106 | +| 5.3.4.2 | Mobility Pattern ..... | 107 | +| 5.3.4.3 | Radio Resource Management functions ..... | 108 | +| 5.3.4.3.1 | General ..... | 108 | +| 5.3.4.3.2 | Preferred band(s) per data radio bearer(s)..... | 109 | +| 5.3.4.3.3 | Redirection to dedicated frequency band(s) for an S-NSSAI ..... | 109 | +| 5.3.4.3.4 | Network Slice based cell reselection and Random Access..... | 110 | +| 5.3.4.4 | UE mobility event notification ..... | 111 | +| 5.3.5 | Triggers for network analytics..... | 112 | +| 5.4 | 3GPP access specific aspects ..... | 112 | +| 5.4.1 | UE reachability in CM-IDLE ..... | 112 | +| 5.4.1.1 | General..... | 112 | +| 5.4.1.2 | UE reachability allowing mobile terminated data while the UE is CM-IDLE..... | 113 | +| 5.4.1.3 | Mobile Initiated Connection Only (MICO) mode ..... | 113 | +| 5.4.1.4 | Support of Unavailability Period ..... | 114 | +| 5.4.2 | UE reachability in CM-CONNECTED..... | 116 | +| 5.4.3 | Paging strategy handling ..... | 117 | +| 5.4.3.1 | General..... | 117 | +| 5.4.3.2 | Paging Policy Differentiation ..... | 117 | +| 5.4.3.3 | Paging Priority ..... | 118 | +| 5.4.4 | UE Radio Capability handling..... | 118 | +| 5.4.4.1 | UE radio capability information storage in the AMF ..... | 118 | +| 5.4.4.1a | UE radio capability signalling optimisation (RACS) ..... | 119 | +| 5.4.4.2 | Void ..... | 123 | +| 5.4.4.2a | UE Radio Capability Match Request..... | 123 | +| 5.4.4.3 | Paging assistance information ..... | 123 | +| 5.4.4a | UE MM Core Network Capability handling ..... | 124 | +| 5.4.4b | UE 5GSM Core Network Capability handling..... | 125 | +| 5.4.5 | DRX (Discontinuous Reception) framework ..... | 125 | +| 5.4.6 | Core Network assistance information for RAN optimization ..... | 126 | +| 5.4.6.1 | General..... | 126 | +| 5.4.6.2 | Core Network assisted RAN parameters tuning ..... | 126 | +| 5.4.6.3 | Core Network assisted RAN paging information ..... | 127 | +| 5.4.7 | NG-RAN location reporting ..... | 127 | +| 5.4.8 | Support for identification and restriction of using unlicensed spectrum..... | 128 | +| 5.4.9 | Wake Up Signal Assistance..... | 129 | +| 5.4.9.1 | General..... | 129 | +| 5.4.9.2 | Group Wake Up Signal..... | 129 | +| 5.4.10 | Support for identification and restriction of using NR satellite access ..... | 130 | +| 5.4.11 | Support for integrating NR satellite access into 5GS ..... | 130 | +| 5.4.11.1 | General..... | 130 | +| 5.4.11.2 | Support of RAT types defined in 5GC for satellite access ..... | 130 | +| 5.4.11.3 | Void ..... | 130 | +| 5.4.11.4 | Verification of UE location..... | 130 | +| 5.4.11.5 | Network selection for NR satellite access ..... | 131 | +| 5.4.11.6 | Support of Mobility Registration Update ..... | 131 | +| 5.4.11.7 | Tracking Area handling for NR satellite access ..... | 131 | +| 5.4.11.8 | Support for mobility Forbidden Area and Service Area Restrictions for NR satellite access..... | 131 | +| 5.4.12 | Paging Early Indication with Paging Subgrouping Assistance ..... | 132 | +| 5.4.12.1 | General..... | 132 | +| 5.4.12.2 | Core Network Assistance for PEIPS ..... | 132 | +| 5.4.13 | Support of discontinuous network coverage for satellite access ..... | 133 | +| 5.4.13.0 | General..... | 133 | +| 5.4.13.1 | Mobility Management and Power Saving Optimization ..... | 133 | +| 5.4.13.2 | Coverage availability information provisioning to the UE..... | 134 | +| 5.4.13.3 | Coverage availability information provisioning to the AMF ..... | 134 | +| 5.4.13.4 | Paging ..... | 134 | +| 5.4.13.5 | Overload control ..... | 134 | +| 5.5 | Non-3GPP access specific aspects ..... | 135 | +| 5.5.0 | General ..... | 135 | +| 5.5.1 | Registration Management..... | 135 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------------|-----| +| 5.5.2 | Connection Management..... | 136 | +| 5.5.3 | UE Reachability..... | 137 | +| 5.5.3.1 | UE reachability in CM-IDLE ..... | 137 | +| 5.5.3.2 | UE reachability in CM-CONNECTED ..... | 137 | +| 5.6 | Session Management..... | 138 | +| 5.6.1 | Overview ..... | 138 | +| 5.6.2 | Interaction between AMF and SMF ..... | 141 | +| 5.6.3 | Roaming ..... | 143 | +| 5.6.4 | Single PDU Session with multiple PDU Session Anchors ..... | 143 | +| 5.6.4.1 | General..... | 143 | +| 5.6.4.2 | Usage of an UL Classifier for a PDU Session..... | 144 | +| 5.6.4.3 | Usage of IPv6 multi-homing for a PDU Session..... | 146 | +| 5.6.5 | Support for Local Area Data Network ..... | 147 | +| 5.6.5a | Supporting LADN per DNN and S-NSSAI..... | 149 | +| 5.6.6 | Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session..... | 150 | +| 5.6.7 | Application Function influence on traffic routing ..... | 152 | +| 5.6.7.1 | General..... | 152 | +| 5.6.7.2 | Enhancement of UP path management based on the coordination with AFs ..... | 161 | +| 5.6.8 | Selective activation and deactivation of UP connection of existing PDU Session ..... | 163 | +| 5.6.9 | Session and Service Continuity ..... | 164 | +| 5.6.9.1 | General..... | 164 | +| 5.6.9.2 | SSC mode ..... | 164 | +| 5.6.9.2.1 | SSC Mode 1 ..... | 164 | +| 5.6.9.2.2 | SSC Mode 2 ..... | 164 | +| 5.6.9.2.3 | SSC Mode 3 ..... | 165 | +| 5.6.9.3 | SSC mode selection ..... | 165 | +| 5.6.10 | Specific aspects of different PDU Session types..... | 166 | +| 5.6.10.1 | Support of IP PDU Session type..... | 166 | +| 5.6.10.2 | Support of Ethernet PDU Session type..... | 166 | +| 5.6.10.3 | Support of Unstructured PDU Session type ..... | 168 | +| 5.6.10.4 | Maximum Transfer Unit size considerations..... | 169 | +| 5.6.11 | UE presence in Area of Interest reporting usage by SMF ..... | 169 | +| 5.6.12 | Use of Network Instance ..... | 171 | +| 5.6.13 | Always-on PDU session ..... | 171 | +| 5.6.14 | Support of Framed Routing ..... | 172 | +| 5.6.15 | Triggers for network analytics..... | 172 | +| 5.6.16 | Support for Service Function Chaining..... | 173 | +| 5.6.16.1 | General..... | 173 | +| 5.6.16.2 | Application Function influence on Service Function Chaining..... | 173 | +| 5.7 | QoS model..... | 174 | +| 5.7.1 | General Overview..... | 174 | +| 5.7.1.1 | QoS Flow ..... | 174 | +| 5.7.1.2 | QoS Profile ..... | 175 | +| 5.7.1.2a | Alternative QoS Profile ..... | 176 | +| 5.7.1.3 | Control of QoS Flows ..... | 176 | +| 5.7.1.4 | QoS Rules ..... | 176 | +| 5.7.1.5 | QoS Flow mapping ..... | 177 | +| 5.7.1.6 | DL traffic ..... | 179 | +| 5.7.1.7 | UL Traffic ..... | 179 | +| 5.7.1.8 | AMBR/MFBR enforcement and rate limitation ..... | 179 | +| 5.7.1.9 | Precedence Value..... | 180 | +| 5.7.1.10 | UE-Slice-MBR enforcement and rate limitation ..... | 180 | +| 5.7.1.11 | QoS aspects of home-routed roaming..... | 180 | +| 5.7.2 | 5G QoS Parameters ..... | 181 | +| 5.7.2.1 | 5QI ..... | 181 | +| 5.7.2.2 | ARP..... | 181 | +| 5.7.2.3 | RQA ..... | 182 | +| 5.7.2.4 | Notification control..... | 182 | +| 5.7.2.4.1 | General ..... | 182 | +| 5.7.2.4.1a | Notification Control without Alternative QoS Profiles..... | 182 | +| 5.7.2.4.1b | Notification control with Alternative QoS Profiles..... | 183 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------------------------|-----| +| 5.7.2.4.2 | Usage of Notification control with Alternative QoS Profiles at handover ..... | 184 | +| 5.7.2.4.3 | Usage of Notification control with Alternative QoS Profiles during QoS Flow establishment and modification..... | 184 | +| 5.7.2.5 | Flow Bit Rates ..... | 185 | +| 5.7.2.6 | Aggregate Bit Rates ..... | 185 | +| 5.7.2.7 | Default values ..... | 186 | +| 5.7.2.8 | Maximum Packet Loss Rate ..... | 186 | +| 5.7.2.9 | Wireline access network specific 5G QoS parameters ..... | 186 | +| 5.7.3 | 5G QoS characteristics ..... | 187 | +| 5.7.3.1 | General ..... | 187 | +| 5.7.3.2 | Resource Type ..... | 187 | +| 5.7.3.3 | Priority Level ..... | 187 | +| 5.7.3.4 | Packet Delay Budget..... | 188 | +| 5.7.3.5 | Packet Error Rate ..... | 189 | +| 5.7.3.6 | Averaging Window ..... | 189 | +| 5.7.3.7 | Maximum Data Burst Volume..... | 189 | +| 5.7.4 | Standardized 5QI to QoS characteristics mapping ..... | 189 | +| 5.7.5 | Reflective QoS..... | 194 | +| 5.7.5.1 | General ..... | 194 | +| 5.7.5.2 | UE Derived QoS Rule..... | 195 | +| 5.7.5.3 | Reflective QoS Control..... | 196 | +| 5.7.6 | Packet Filter Set..... | 197 | +| 5.7.6.1 | General ..... | 197 | +| 5.7.6.2 | IP Packet Filter Set ..... | 197 | +| 5.7.6.3 | Ethernet Packet Filter Set ..... | 198 | +| 5.7.7 | PDU Set QoS Parameters ..... | 198 | +| 5.7.7.1 | General ..... | 198 | +| 5.7.7.2 | PDU Set Delay Budget ..... | 198 | +| 5.7.7.3 | PDU Set Error Rate..... | 199 | +| 5.7.7.4 | PDU Set Integrated Handling Information ..... | 199 | +| 5.8 | User Plane Management..... | 199 | +| 5.8.1 | General ..... | 199 | +| 5.8.2 | Functional Description ..... | 200 | +| 5.8.2.1 | General ..... | 200 | +| 5.8.2.2 | UE IP Address Management..... | 200 | +| 5.8.2.2.1 | General ..... | 200 | +| 5.8.2.2.2 | Routing rules configuration..... | 202 | +| 5.8.2.2.3 | The procedure of Stateless IPv6 Address Autoconfiguration ..... | 202 | +| 5.8.2.2.4 | IPv6 Prefix Delegation via DHCPv6 ..... | 203 | +| 5.8.2.3 | Management of CN Tunnel Info..... | 204 | +| 5.8.2.3.1 | General ..... | 204 | +| 5.8.2.3.2 | Void..... | 204 | +| 5.8.2.3.3 | Management of CN Tunnel Info in the UPF ..... | 204 | +| 5.8.2.4 | Traffic Detection..... | 204 | +| 5.8.2.4.1 | General ..... | 204 | +| 5.8.2.4.2 | Traffic Detection Information ..... | 204 | +| 5.8.2.5 | Control of User Plane Forwarding..... | 205 | +| 5.8.2.5.1 | General ..... | 205 | +| 5.8.2.5.2 | Data forwarding between the SMF and UPF ..... | 205 | +| 5.8.2.5.3 | Support of Ethernet PDU Session type ..... | 206 | +| 5.8.2.6 | Charging and Usage Monitoring Handling..... | 207 | +| 5.8.2.6.1 | General ..... | 207 | +| 5.8.2.6.2 | Activation of Usage Reporting in UPF ..... | 207 | +| 5.8.2.6.3 | Reporting of Usage Information towards SMF ..... | 208 | +| 5.8.2.7 | PDU Session and QoS Flow Policing..... | 208 | +| 5.8.2.8 | PCC Related Functions..... | 208 | +| 5.8.2.8.1 | Activation/Deactivation of predefined PCC rules..... | 208 | +| 5.8.2.8.2 | Enforcement of Dynamic PCC Rules..... | 209 | +| 5.8.2.8.3 | Redirection ..... | 209 | +| 5.8.2.8.4 | Support of PFD Management..... | 210 | +| 5.8.2.9 | Functionality of Sending of "End marker" ..... | 210 | +| 5.8.2.9.0 | Introduction ..... | 210 | + +| | | | +|------------|------------------------------------------------------------------------|-----| +| 5.8.2.9.1 | UPF Constructing the "End marker" Packets..... | 210 | +| 5.8.2.9.2 | SMF Constructing the "End marker" Packets ..... | 211 | +| 5.8.2.10 | UP Tunnel Management ..... | 211 | +| 5.8.2.11 | Parameters for N4 session management (moved)..... | 211 | +| 5.8.2.12 | Reporting of the UE MAC addresses used in a PDU Session ..... | 212 | +| 5.8.2.13 | Support for 5G VN group communication ..... | 212 | +| 5.8.2.13.0 | General ..... | 212 | +| 5.8.2.13.1 | Support for unicast traffic forwarding of a 5G VN ..... | 213 | +| 5.8.2.13.2 | Support for unicast traffic forwarding update due to UE mobility ..... | 214 | +| 5.8.2.13.3 | Support for user plane traffic replication in a 5G VN ..... | 214 | +| 5.8.2.14 | Inter PLMN User Plane Security functionality..... | 216 | +| 5.8.2.15 | Void ..... | 217 | +| 5.8.2.16 | Support for L2TP tunnelling on N6 ..... | 217 | +| 5.8.2.17 | Data exposure via Service Based interface..... | 217 | +| 5.8.2.18 | QoS Flow related QoS monitoring and reporting ..... | 218 | +| 5.8.2.19 | Explicit Buffer Management ..... | 218 | +| 5.8.2.19.1 | General ..... | 218 | +| 5.8.2.19.2 | Buffering at UPF ..... | 218 | +| 5.8.2.19.3 | Buffering at SMF ..... | 219 | +| 5.8.2.20 | SMF Pause of Charging..... | 219 | +| 5.8.3 | Explicit Buffer Management (moved)..... | 220 | +| 5.8.4 | SMF Pause of Charging (moved)..... | 220 | +| 5.8.5 | Parameters for N4 session management..... | 220 | +| 5.8.5.1 | General..... | 220 | +| 5.8.5.2 | N4 Session Context..... | 221 | +| 5.8.5.3 | Packet Detection Rule..... | 221 | +| 5.8.5.4 | QoS Enforcement Rule ..... | 224 | +| 5.8.5.5 | Usage Reporting Rule..... | 227 | +| 5.8.5.6 | Forwarding Action Rule ..... | 230 | +| 5.8.5.7 | Usage Report generated by UPF ..... | 233 | +| 5.8.5.8 | Multi-Access Rule ..... | 234 | +| 5.8.5.9 | Bridge/Router Information ..... | 235 | +| 5.8.5.10 | Void ..... | 235 | +| 5.8.5.11 | Session Reporting Rule..... | 236 | +| 5.8.5.12 | Session reporting generated by UPF..... | 236 | +| 5.8.5.13 | Void ..... | 237 | +| 5.8.5.14 | TSC Management Information ..... | 237 | +| 5.8.5.15 | Downlink Data Report generated by UPF ..... | 237 | +| 5.9 | Identifiers ..... | 238 | +| 5.9.1 | General ..... | 238 | +| 5.9.2 | Subscription Permanent Identifier ..... | 238 | +| 5.9.2a | Subscription Concealed Identifier ..... | 238 | +| 5.9.3 | Permanent Equipment Identifier..... | 238 | +| 5.9.4 | 5G Globally Unique Temporary Identifier ..... | 239 | +| 5.9.5 | AMF Name ..... | 240 | +| 5.9.6 | Data Network Name (DNN)..... | 240 | +| 5.9.7 | Internal-Group Identifier ..... | 240 | +| 5.9.8 | Generic Public Subscription Identifier ..... | 240 | +| 5.9.9 | AMF UE NGAP ID ..... | 240 | +| 5.9.10 | UE Radio Capability ID ..... | 241 | +| 5.10 | Security aspects..... | 241 | +| 5.10.1 | General ..... | 241 | +| 5.10.2 | Security Model for non-3GPP access..... | 241 | +| 5.10.2.1 | Signalling Security..... | 241 | +| 5.10.3 | PDU Session User Plane Security ..... | 242 | +| 5.11 | Support for Dual Connectivity, Multi-Connectivity ..... | 244 | +| 5.11.1 | Support for Dual Connectivity ..... | 244 | +| 5.12 | Charging..... | 245 | +| 5.12.1 | General ..... | 245 | +| 5.12.2 | Usage Data Reporting for Secondary RAT ..... | 245 | +| 5.12.3 | Secondary RAT Periodic Usage Data Reporting Procedure ..... | 246 | +| 5.13 | Support for Edge Computing ..... | 246 | + +| | | | +|-------------|--------------------------------------------------------------------------------------------------------------------------------|-----| +| 5.14 | Policy Control ..... | 247 | +| 5.15 | Network slicing ..... | 247 | +| 5.15.1 | General ..... | 247 | +| 5.15.2 | Identification and selection of a Network Slice: the S-NSSAI and the NSSAI ..... | 248 | +| 5.15.2.1 | General ..... | 248 | +| 5.15.2.2 | Standardised SST values..... | 249 | +| 5.15.3 | Subscription aspects ..... | 250 | +| 5.15.4 | UE NSSAI configuration and NSSAI storage aspects ..... | 251 | +| 5.15.4.1 | General ..... | 251 | +| 5.15.4.1.1 | UE Network Slice configuration ..... | 251 | +| 5.15.4.1.2 | Mapping of S-NSSAIs values in the Allowed NSSAI and in the Requested NSSAI to the S-NSSAIs values used in the HPLMN ..... | 253 | +| 5.15.4.2 | Update of UE Network Slice configuration ..... | 254 | +| 5.15.5 | Detailed Operation Overview ..... | 255 | +| 5.15.5.1 | General ..... | 255 | +| 5.15.5.2 | Selection of a Serving AMF supporting the Network Slices ..... | 255 | +| 5.15.5.2.1 | Registration to a set of Network Slices ..... | 255 | +| 5.15.5.2.2 | Modification of the Set of Network Slice(s) for a UE ..... | 260 | +| 5.15.5.2.3 | AMF Re-allocation due to Network Slice(s) Support ..... | 262 | +| 5.15.5.3 | Establishing a PDU Session in a Network Slice ..... | 262 | +| 5.15.6 | Network Slicing Support for Roaming ..... | 263 | +| 5.15.7 | Network slicing and Interworking with EPS ..... | 265 | +| 5.15.7.1 | General ..... | 265 | +| 5.15.7.2 | Idle mode aspects..... | 265 | +| 5.15.7.3 | Connected mode aspects ..... | 266 | +| 5.15.7.4 | Support of Network Slice usage control and Interworking with EPC ..... | 266 | +| 5.15.8 | Configuration of Network Slice availability in a PLMN ..... | 266 | +| 5.15.9 | Operator-controlled inclusion of NSSAI in Access Stratum Connection Establishment ..... | 267 | +| 5.15.10 | Network Slice-Specific Authentication and Authorization ..... | 268 | +| 5.15.11 | Network Slice Admission Control ..... | 269 | +| 5.15.11.0 | General ..... | 269 | +| 5.15.11.1 | Network Slice Admission Control for maximum number of UEs..... | 270 | +| 5.15.11.1.1 | Non-Hierarchical NSAC architecture ..... | 270 | +| 5.15.11.1.2 | Hierarchical NSAC architecture..... | 271 | +| 5.15.11.1.3 | Centralized NSAC architecture ..... | 272 | +| 5.15.11.2 | Network Slice Admission Control for maximum number of PDU sessions ..... | 272 | +| 5.15.11.2.1 | Non- Hierarchical NSAC architecture ..... | 272 | +| 5.15.11.2.2 | Hierarchical NSAC architecture..... | 273 | +| 5.15.11.2.3 | Centralized NSAC architecture ..... | 273 | +| 5.15.11.3 | Network Slice Admission Control for Roaming..... | 273 | +| 5.15.11.3.0 | General ..... | 273 | +| 5.15.11.3.1 | VPLMN NSAC Admission Mode..... | 274 | +| 5.15.11.3.2 | VPLMN with HPLMN assistance NSAC Admission ..... | 274 | +| 5.15.11.3.3 | HPLMN NSAC Admission Mode..... | 275 | +| 5.15.11.4 | Network Slice status notifications and reports to a consumer NF ..... | 275 | +| 5.15.11.5 | Support of Network Slice Admission Control and Interworking with EPC ..... | 275 | +| 5.15.11.5a | Support of Network Slice Admission Control in 5GS for maximum number of UEs with at least one PDU Session/PDN Connection ..... | 277 | +| 5.15.12 | Support of subscription-based restrictions to simultaneous registration of network slices ..... | 278 | +| 5.15.12.1 | General ..... | 278 | +| 5.15.12.2 | UE and UE configuration aspects ..... | 279 | +| 5.15.13 | Support of data rate limitation per Network Slice for a UE ..... | 280 | +| 5.15.14 | Network Slice AS Groups support ..... | 280 | +| 5.15.15 | Support of Network Slice usage control ..... | 281 | +| 5.15.15.1 | General ..... | 281 | +| 5.15.15.2 | UE Configuration of network-controlled Slice Usage Policy ..... | 281 | +| 5.15.15.3 | Network-based per UE Network Slice usage behaviour control ..... | 282 | +| 5.15.16 | Optimized handling of temporarily available network slices ..... | 282 | +| 5.15.17 | Partial Network Slice support in a Registration Area..... | 284 | +| 5.15.18 | Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas ..... | 286 | +| 5.15.18.1 | General ..... | 286 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------|-----| +| 5.15.18.2 | S-NSSAI location availability information..... | 286 | +| 5.15.18.3 | Network based monitoring and enforcement of Network Slice Area of Service not matching deployed Tracking Areas..... | 287 | +| 5.15.19 | Support of Network Slice Replacement ..... | 288 | +| 5.15.20 | Support of Network Slice Instance Replacement..... | 290 | +| 5.16 | Support for specific services ..... | 291 | +| 5.16.1 | Public Warning System ..... | 291 | +| 5.16.2 | SMS over NAS ..... | 291 | +| 5.16.2.1 | General..... | 291 | +| 5.16.2.2 | SMS over NAS transport ..... | 291 | +| 5.16.3 | IMS support ..... | 291 | +| 5.16.3.1 | General..... | 291 | +| 5.16.3.2 | IMS voice over PS Session Supported Indication over 3GPP access..... | 292 | +| 5.16.3.2a | IMS voice over PS Session Supported Indication over non-3GPP access ..... | 293 | +| 5.16.3.3 | Homogeneous support for IMS voice over PS Session supported indication ..... | 293 | +| 5.16.3.4 | P-CSCF address delivery ..... | 293 | +| 5.16.3.5 | Domain selection for UE originating sessions / calls ..... | 293 | +| 5.16.3.6 | Terminating domain selection for IMS voice ..... | 294 | +| 5.16.3.7 | UE's usage setting ..... | 294 | +| 5.16.3.8 | Domain and Access Selection for UE originating SMS ..... | 295 | +| 5.16.3.8.1 | UE originating SMS for IMS Capable UEs supporting SMS over IP ..... | 295 | +| 5.16.3.8.2 | Access Selection for SMS over NAS..... | 295 | +| 5.16.3.9 | SMF support for P-CSCF restoration procedure ..... | 295 | +| 5.16.3.10 | IMS Voice Service via EPS Fallback or RAT fallback in 5GS..... | 295 | +| 5.16.3.11 | P-CSCF discovery and selection..... | 296 | +| 5.16.3.12 | HSS discovery and selection..... | 296 | +| 5.16.4 | Emergency Services ..... | 296 | +| 5.16.4.1 | Introduction..... | 296 | +| 5.16.4.2 | Architecture Reference Model for Emergency Services ..... | 299 | +| 5.16.4.3 | Mobility Restrictions and Access Restrictions for Emergency Services..... | 299 | +| 5.16.4.4 | Reachability Management ..... | 300 | +| 5.16.4.5 | SMF and UPF selection function for Emergency Services ..... | 300 | +| 5.16.4.6 | QoS for Emergency Services ..... | 300 | +| 5.16.4.7 | PCC for Emergency Services ..... | 300 | +| 5.16.4.8 | IP Address Allocation..... | 301 | +| 5.16.4.9 | Handling of PDU Sessions for Emergency Services ..... | 301 | +| 5.16.4.9a | Handling of PDU Sessions for normal services for Emergency Registered UEs..... | 301 | +| 5.16.4.10 | Support of eCall Only Mode..... | 301 | +| 5.16.4.11 | Emergency Services Fallback..... | 302 | +| 5.16.5 | Multimedia Priority Services..... | 302 | +| 5.16.6 | Mission Critical Services..... | 304 | +| 5.17 | Interworking and Migration ..... | 305 | +| 5.17.1 | Support for Migration from EPC to 5GC ..... | 305 | +| 5.17.1.1 | General..... | 305 | +| 5.17.1.2 | User Plane management to support interworking with EPS ..... | 307 | +| 5.17.1.3 | QoS handling for home routed roaming ..... | 307 | +| 5.17.2 | Interworking with EPC ..... | 307 | +| 5.17.2.1 | General..... | 307 | +| 5.17.2.2 | Interworking Procedures with N26 interface ..... | 311 | +| 5.17.2.2.1 | General ..... | 311 | +| 5.17.2.2.2 | Mobility for UEs in single-registration mode ..... | 312 | +| 5.17.2.3 | Interworking Procedures without N26 interface..... | 313 | +| 5.17.2.3.1 | General ..... | 313 | +| 5.17.2.3.2 | Mobility for UEs in single-registration mode ..... | 314 | +| 5.17.2.3.3 | Mobility for UEs in dual-registration mode ..... | 315 | +| 5.17.2.3.4 | Redirection for UEs in connected state ..... | 316 | +| 5.17.2.4 | Mobility between 5GS and GERAN/UTRAN..... | 316 | +| 5.17.2.5 | Secondary DN authentication and authorization in EPS Interworking case..... | 317 | +| 5.17.3 | Interworking with EPC in presence of Non-3GPP PDU Sessions ..... | 318 | +| 5.17.4 | Network sharing support and interworking between EPS and 5GS ..... | 318 | +| 5.17.5 | Service Exposure in Interworking Scenarios..... | 318 | +| 5.17.5.1 | General..... | 318 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------|-----| +| 5.17.5.2 | Support of interworking for Monitoring Events ..... | 319 | +| 5.17.5.2.1 | Interworking with N26 interface ..... | 319 | +| 5.17.5.2.2 | Interworking without N26 interface ..... | 319 | +| 5.17.5.3 | Availability or expected level of a service API ..... | 319 | +| 5.17.6 | Void ..... | 320 | +| 5.17.7 | Configuration Transfer Procedure between NG-RAN and E-UTRAN ..... | 320 | +| 5.17.7.1 | Architecture Principles for Configuration Transfer between NG-RAN and E-UTRAN ..... | 320 | +| 5.17.7.2 | Addressing, routing and relaying ..... | 321 | +| 5.17.7.2.1 | Addressing ..... | 321 | +| 5.17.7.2.2 | Routing ..... | 321 | +| 5.17.7.2.3 | Relaying ..... | 322 | +| 5.17.8 | URSP Provisioning in EPS ..... | 322 | +| 5.18 | Network Sharing ..... | 323 | +| 5.18.1 | General concepts ..... | 323 | +| 5.18.2 | Broadcast system information for network sharing ..... | 324 | +| 5.18.2a | PLMN list and SNPN list handling for network sharing ..... | 324 | +| 5.18.3 | Network selection by the UE ..... | 325 | +| 5.18.4 | Network selection by the network ..... | 325 | +| 5.18.5 | Network Sharing and Network Slicing ..... | 326 | +| 5.19 | Control Plane Load Control, Congestion and Overload Control ..... | 326 | +| 5.19.1 | General ..... | 326 | +| 5.19.2 | TNLA Load Balancing and TNLA Load Re-Balancing ..... | 326 | +| 5.19.3 | AMF Load Balancing ..... | 326 | +| 5.19.4 | AMF Load Re-Balancing ..... | 327 | +| 5.19.5 | AMF Control Of Overload ..... | 327 | +| 5.19.5.1 | General ..... | 327 | +| 5.19.5.2 | AMF Overload Control ..... | 327 | +| 5.19.6 | SMF Overload Control ..... | 328 | +| 5.19.7 | NAS level congestion control ..... | 329 | +| 5.19.7.1 | General ..... | 329 | +| 5.19.7.2 | General NAS level congestion control ..... | 329 | +| 5.19.7.3 | DNN based congestion control ..... | 330 | +| 5.19.7.4 | S-NSSAI based congestion control ..... | 331 | +| 5.19.7.5 | Group specific NAS level congestion control ..... | 333 | +| 5.19.7.6 | Control Plane data specific NAS level congestion control ..... | 333 | +| 5.20 | External Exposure of Network Capability ..... | 334 | +| 5.20a | Data Collection from an AF ..... | 336 | +| 5.20b | Support exposure of DNN and S-NSSAI specific Group Parameters ..... | 336 | +| 5.20b.1 | Group attribute provisioning ..... | 336 | +| 5.20b.2 | Support LADN service area for a group ..... | 336 | +| 5.20b.3 | Support QoS for a group ..... | 336 | +| 5.20b.4 | Void ..... | 336 | +| 5.20b.5 | Void ..... | 337 | +| 5.20c | Provisioning of traffic characteristics and monitoring of performance characteristics for a group ..... | 337 | +| 5.20d | User Plane Direct 5GS Information Exposure ..... | 337 | +| 5.20d.1 | General ..... | 337 | +| 5.21 | Architectural support for virtualized deployments ..... | 338 | +| 5.21.0 | General ..... | 338 | +| 5.21.1 | Architectural support for N2 ..... | 338 | +| 5.21.1.1 | TNL associations ..... | 338 | +| 5.21.1.2 | NGAP UE-TNLA-binding ..... | 339 | +| 5.21.1.3 | N2 TNL association selection ..... | 339 | +| 5.21.2 | AMF Management ..... | 339 | +| 5.21.2.1 | AMF Addition/Update ..... | 339 | +| 5.21.2.2 | AMF planned removal procedure ..... | 340 | +| 5.21.2.2.1 | AMF planned removal procedure with UDSF deployed ..... | 340 | +| 5.21.2.2.2 | AMF planned removal procedure without UDSF ..... | 341 | +| 5.21.2.3 | Procedure for AMF Auto-recovery ..... | 343 | +| 5.21.3 | Network Reliability support with Sets ..... | 344 | +| 5.21.3.1 | General ..... | 344 | +| 5.21.3.2 | NF Set and NF Service Set ..... | 345 | +| 5.21.3.3 | Reliability of NF instances within the same NF Set ..... | 345 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------|-----| +| 5.21.3.4 | Reliability of NF Services..... | 345 | +| 5.21.4 | Network Function/NF Service Context Transfer ..... | 345 | +| 5.21.4.1 | General..... | 345 | +| 5.22 | System Enablers for priority mechanism ..... | 346 | +| 5.22.1 | General ..... | 346 | +| 5.22.2 | Subscription-related Priority Mechanisms ..... | 346 | +| 5.22.3 | Invocation-related Priority Mechanisms ..... | 347 | +| 5.22.4 | QoS Mechanisms applied to established QoS Flows ..... | 348 | +| 5.23 | Supporting for Asynchronous Type Communication ..... | 348 | +| 5.24 | 3GPP PS Data Off ..... | 349 | +| 5.25 | Support of OAM Features ..... | 350 | +| 5.25.1 | Support of Tracing: Signalling Based Activation/Deactivation of Tracing ..... | 350 | +| 5.25.2 | Support of OAM-based 5G VN group management ..... | 350 | +| 5.26 | Configuration Transfer Procedure..... | 350 | +| 5.26.1 | Architecture Principles for Configuration Transfer..... | 351 | +| 5.26.2 | Addressing, routing and relaying ..... | 351 | +| 5.26.2.1 | Addressing ..... | 351 | +| 5.26.2.2 | Routing..... | 351 | +| 5.26.2.3 | Relaying..... | 352 | +| 5.27 | Enablers for Time Sensitive Communications, Time Synchronization and Deterministic Networking ..... | 352 | +| 5.27.0 | General ..... | 352 | +| 5.27.1 | Time Synchronization ..... | 352 | +| 5.27.1.1 | General..... | 352 | +| 5.27.1.2 | Distribution of timing information ..... | 354 | +| 5.27.1.2.1 | Distribution of 5G internal system clock ..... | 354 | +| 5.27.1.2.2 | Distribution of grandmaster clock and time-stamping..... | 354 | +| 5.27.1.3 | Support for multiple (g)PTP domains..... | 357 | +| 5.27.1.4 | DS-TT and NW-TT Time Synchronization functionality ..... | 357 | +| 5.27.1.5 | Detection of (g)PTP Sync and Announce timeouts ..... | 358 | +| 5.27.1.6 | Distribution of Announce messages and best master clock selection ..... | 358 | +| 5.27.1.7 | Support for PTP grandmaster function in 5GS ..... | 359 | +| 5.27.1.8 | Exposure of Time Synchronization ..... | 360 | +| 5.27.1.9 | Support for derivation of Uu time synchronization error budget ..... | 361 | +| 5.27.1.10 | Support for coverage area filters for time synchronization service ..... | 362 | +| 5.27.1.11 | Controlling time synchronization service based on the Subscription..... | 363 | +| 5.27.1.12 | Support for network timing synchronization status monitoring ..... | 365 | +| 5.27.1a | Periodic deterministic communication ..... | 368 | +| 5.27.2 | TSC Assistance Information (TSCAI) and TSC Assistance Container (TSCAC)..... | 369 | +| 5.27.2.1 | General..... | 369 | +| 5.27.2.2 | TSC Assistance Container determination based on PSFP ..... | 370 | +| 5.27.2.3 | TSC Assistance Container determination by TSCTSF..... | 371 | +| 5.27.2.4 | TSCAI determination based on TSC Assistance Container ..... | 371 | +| 5.27.2.5 | RAN feedback for Burst Arrival Time offset and adjusted Periodicity ..... | 372 | +| 5.27.2.5.1 | Overview ..... | 372 | +| 5.27.2.5.2 | Proactive RAN feedback for adaptation of Burst Arrival Time and Periodicity ..... | 373 | +| 5.27.2.5.3 | Reactive RAN feedback for Burst Arrival Time adaptation ..... | 373 | +| 5.27.3 | Support for TSC QoS Flows..... | 374 | +| 5.27.4 | Hold and Forward Buffering mechanism ..... | 374 | +| 5.27.5 | 5G System Bridge delay..... | 375 | +| 5.28 | Support of integration with TSN, Time Sensitive Communications, Time Synchronization and Deterministic Networking ..... | 375 | +| 5.28.0 | General ..... | 375 | +| 5.28.1 | 5GS bridge management for TSN ..... | 376 | +| 5.28.2 | 5GS Bridge configuration for TSN ..... | 378 | +| 5.28.3 | Port and user plane node management information exchange in 5GS ..... | 379 | +| 5.28.3.1 | General..... | 379 | +| 5.28.3.2 | Transfer of port or user plane node management information ..... | 381 | +| 5.28.3.3 | VLAN Configuration Information for TSN..... | 381 | +| 5.28.4 | QoS mapping tables for TSN ..... | 382 | +| 5.28.5 | Support of integration with IETF Deterministic Networking ..... | 383 | +| 5.28.5.1 | General..... | 383 | +| 5.28.5.2 | 5GS DetNet node reporting ..... | 383 | + +| | | | +|-------------|--------------------------------------------------------------------------------------------------------|-----| +| 5.28.5.3 | DetNet node configuration mapping in 5GS ..... | 384 | +| 5.28a | Support for TSN enabled Transport Network..... | 385 | +| 5.28a.1 | General ..... | 385 | +| 5.28a.2 | Transfer of TL-Container between SMF/CUC and AN-TL and CN-TL ..... | 386 | +| 5.28a.3 | Topology Information for TSN TN..... | 386 | +| 5.29 | Support for 5G LAN-type service..... | 387 | +| 5.29.1 | General ..... | 387 | +| 5.29.2 | 5G VN group management..... | 387 | +| 5.29.3 | PDU Session management ..... | 388 | +| 5.29.4 | User Plane handling..... | 390 | +| 5.30 | Support for non-public networks..... | 391 | +| 5.30.1 | General ..... | 391 | +| 5.30.2 | Stand-alone Non-Public Networks ..... | 391 | +| 5.30.2.0 | General..... | 391 | +| 5.30.2.1 | Identifiers ..... | 392 | +| 5.30.2.2 | Broadcast system information ..... | 392 | +| 5.30.2.3 | UE configuration and subscription aspects..... | 393 | +| 5.30.2.4 | Network selection in SNPN access mode..... | 395 | +| 5.30.2.4.1 | General ..... | 395 | +| 5.30.2.4.2 | Automatic network selection..... | 396 | +| 5.30.2.4.3 | Manual network selection ..... | 398 | +| 5.30.2.5 | Network access control..... | 398 | +| 5.30.2.6 | Cell (re-)selection in SNPN access mode..... | 398 | +| 5.30.2.7 | Access to PLMN services via stand-alone non-public networks..... | 398 | +| 5.30.2.8 | Access to stand-alone non-public network services via PLMN ..... | 399 | +| 5.30.2.9 | SNPN connectivity for UEs with credentials owned by Credentials Holder ..... | 399 | +| 5.30.2.9.1 | General ..... | 399 | +| 5.30.2.9.2 | Credentials Holder using AAA Server for primary authentication and authorization..... | 400 | +| 5.30.2.9.3 | Credentials Holder using AUSF and UDM for primary authentication and authorization..... | 401 | +| 5.30.2.10 | Onboarding of UEs for SNPNs..... | 402 | +| 5.30.2.10.1 | General ..... | 402 | +| 5.30.2.10.2 | Onboarding Network is an SNPN ..... | 402 | +| 5.30.2.10.3 | Onboarding Network is a PLMN ..... | 407 | +| 5.30.2.10.4 | Remote Provisioning of UEs in Onboarding Network..... | 407 | +| 5.30.2.11 | UE Mobility support for SNPN ..... | 409 | +| 5.30.2.12 | Access to SNPN services via Untrusted non-3GPP access ..... | 410 | +| 5.30.2.13 | Access to SNPN services via Trusted non-3GPP access ..... | 411 | +| 5.30.2.14 | Access to SNPN services via wireline access network..... | 412 | +| 5.30.2.15 | Access to SNPN services for N5CW devices..... | 412 | +| 5.30.3 | Public Network Integrated NPN..... | 412 | +| 5.30.3.1 | General ..... | 412 | +| 5.30.3.2 | Identifiers ..... | 413 | +| 5.30.3.3 | UE configuration, subscription aspects and storage ..... | 413 | +| 5.30.3.4 | Network and cell (re-)selection, and access control ..... | 414 | +| 5.30.3.5 | Support of emergency services in CAG cells ..... | 416 | +| 5.31 | Support for Cellular IoT ..... | 416 | +| 5.31.1 | General ..... | 416 | +| 5.31.2 | Preferred and Supported Network Behaviour ..... | 416 | +| 5.31.3 | Selection, steering and redirection between EPS and 5GS ..... | 417 | +| 5.31.4 | Control Plane CIoT 5GS Optimisation..... | 418 | +| 5.31.4.1 | General..... | 418 | +| 5.31.4.2 | Establishment of N3 data transfer during Data Transport in Control Plane CIoT 5GS
Optimisation..... | 419 | +| 5.31.4.3 | Control Plane Relocation Indication procedure..... | 419 | +| 5.31.5 | Non-IP Data Delivery (NIDD) ..... | 419 | +| 5.31.6 | Reliable Data Service ..... | 420 | +| 5.31.7 | Power Saving Enhancements ..... | 421 | +| 5.31.7.1 | General..... | 421 | +| 5.31.7.2 | Extended Discontinuous Reception (DRX) for CM-IDLE and CM-CONNECTED with RRC-
INACTIVE..... | 421 | +| 5.31.7.2.1 | Overview ..... | 421 | +| 5.31.7.2.2 | Paging for extended idle mode DRX in E-UTRA and NR connected to 5GC ..... | 423 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------|-----| +| 5.31.7.2.3 | Paging for a UE registered in a tracking area with heterogeneous support of extended idle mode DRX..... | 424 | +| 5.31.7.2.4 | Paging for extended DRX for RRC_INACTIVE in NR connected to 5GC ..... | 424 | +| 5.31.7.3 | MICO mode with Extended Connected Time ..... | 424 | +| 5.31.7.4 | MICO mode with Active Time ..... | 425 | +| 5.31.7.5 | MICO mode and Periodic Registration Timer Control ..... | 425 | +| 5.31.8 | High latency communication..... | 426 | +| 5.31.9 | Support for Monitoring Events ..... | 427 | +| 5.31.10 | NB-IoT UE Radio Capability Handling ..... | 427 | +| 5.31.11 | Inter-RAT idle mode mobility to and from NB-IoT ..... | 427 | +| 5.31.12 | Restriction of use of Enhanced Coverage..... | 428 | +| 5.31.13 | Paging for Enhanced Coverage ..... | 429 | +| 5.31.14 | Support of rate control of user data ..... | 429 | +| 5.31.14.1 | General..... | 429 | +| 5.31.14.2 | Serving PLMN Rate Control ..... | 429 | +| 5.31.14.3 | Small Data Rate Control..... | 430 | +| 5.31.15 | Control Plane Data Transfer Congestion Control ..... | 431 | +| 5.31.16 | Service Gap Control ..... | 431 | +| 5.31.17 | Inter-UE QoS for NB-IoT ..... | 433 | +| 5.31.18 | User Plane CIoT 5GS Optimisation ..... | 433 | +| 5.31.19 | QoS model for NB-IoT..... | 434 | +| 5.31.20 | Category M UEs differentiation ..... | 434 | +| 5.32 | Support for ATSSS..... | 435 | +| 5.32.1 | General ..... | 435 | +| 5.32.2 | Multi Access PDU Sessions ..... | 436 | +| 5.32.3 | Policy for ATSSS Control ..... | 441 | +| 5.32.4 | QoS Support ..... | 441 | +| 5.32.5 | Access Network Performance Measurements ..... | 443 | +| 5.32.5.1 | General principles ..... | 443 | +| 5.32.5.1a | Address of PMF messages..... | 445 | +| 5.32.5.2 | Round Trip Time Measurements ..... | 447 | +| 5.32.5.2a | Packet Loss Rate Measurements..... | 447 | +| 5.32.5.3 | Access Availability/Unavailability Report ..... | 448 | +| 5.32.5.4 | Protocol stack for user plane measurements and measurement reports..... | 448 | +| 5.32.5.5 | UE Assistance Operation ..... | 449 | +| 5.32.5.6 | Suspend and Resume Traffic Duplication ..... | 450 | +| 5.32.6 | Support of Steering Functionalities ..... | 450 | +| 5.32.6.1 | General..... | 450 | +| 5.32.6.2 | High-Layer Steering Functionalities..... | 453 | +| 5.32.6.2.1 | MPTCP Functionality ..... | 453 | +| 5.32.6.2.2 | MPQUIC Functionality ..... | 454 | +| 5.32.6.3 | Low-Layer Steering Functionalities ..... | 457 | +| 5.32.6.3.1 | ATSSS-LL Functionality ..... | 457 | +| 5.32.7 | Interworking with EPS ..... | 458 | +| 5.32.7.1 | General..... | 458 | +| 5.32.7.2 | Interworking with N26 Interface ..... | 458 | +| 5.32.7.3 | Interworking without N26 Interface ..... | 458 | +| 5.32.8 | ATSSS Rules ..... | 459 | +| 5.33 | Support for Ultra Reliable Low Latency Communication ..... | 463 | +| 5.33.1 | General ..... | 463 | +| 5.33.2 | Redundant transmission for high reliability communication ..... | 464 | +| 5.33.2.1 | Dual Connectivity based end to end Redundant User Plane Paths ..... | 464 | +| 5.33.2.2 | Support of redundant transmission on N3/N9 interfaces..... | 466 | +| 5.33.2.3 | Support for redundant transmission at transport layer..... | 468 | +| 5.33.3 | QoS Monitoring for packet delay ..... | 468 | +| 5.33.3.1 | General..... | 468 | +| 5.33.3.2 | Per QoS Flow per UE QoS Measurement ..... | 468 | +| 5.33.3.3 | GTP-U Path Measurement..... | 469 | +| 5.34 | Support of deployments topologies with specific SMF Service Areas..... | 471 | +| 5.34.1 | General ..... | 471 | +| 5.34.2 | Architecture ..... | 472 | +| 5.34.2.1 | SBA architecture..... | 472 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------------------|-----| +| 5.34.2.2 | Non-roaming architecture ..... | 472 | +| 5.34.2.3 | Roaming architecture ..... | 473 | +| 5.34.3 | I-SMF selection, V-SMF reselection..... | 474 | +| 5.34.4 | Usage of an UL Classifier for a PDU Session controlled by I-SMF..... | 475 | +| 5.34.5 | Usage of IPv6 multi-homing for a PDU Session controlled by I-SMF..... | 475 | +| 5.34.6 | Interaction between I-SMF and SMF for the support of traffic offload by UPF controlled by the I-SMF ..... | 476 | +| 5.34.6.1 | General ..... | 476 | +| 5.34.6.2 | N4 information sent from SMF to I-SMF for local traffic offload..... | 477 | +| 5.34.7 | Event Management ..... | 477 | +| 5.34.7.1 | UE's Mobility Event Management..... | 477 | +| 5.34.7.2 | SMF event exposure service ..... | 478 | +| 5.34.7.3 | AMF implicit subscription about events related with the PDU Session..... | 478 | +| 5.34.8 | Support for Cellular IoT ..... | 478 | +| 5.34.9 | Support of the Deployment Topologies with specific SMF Service Areas feature within and between PLMN(s)..... | 478 | +| 5.34.10 | Support for 5G LAN-type service ..... | 479 | +| 5.35 | Support for Integrated access and backhaul (IAB) ..... | 479 | +| 5.35.1 | IAB architecture and functional entities..... | 479 | +| 5.35.2 | 5G System enhancements to support IAB..... | 480 | +| 5.35.3 | Data handling and QoS support with IAB..... | 481 | +| 5.35.4 | Mobility support with IAB ..... | 481 | +| 5.35.5 | Charging support with IAB ..... | 481 | +| 5.35.6 | IAB operation involving EPC ..... | 481 | +| 5.35A | Support for Mobile Base Station Relay (MBSR)..... | 482 | +| 5.35A.1 | General ..... | 482 | +| 5.35A.2 | Configuration of the MBSR ..... | 482 | +| 5.35A.3 | Mobility support of UEs served by MBSR ..... | 483 | +| 5.35A.3.1 | UE mobility between a fixed cell and MBSR cell..... | 483 | +| 5.35A.3.2 | UE mobility between MBSR cells..... | 483 | +| 5.35A.3.3 | UE mobility when moving together with a MBSR cell..... | 483 | +| 5.35A.4 | MBSR authorization..... | 483 | +| 5.35A.5 | Location Service Support of UEs served by MBSR ..... | 484 | +| 5.35A.6 | Providing cell ID/TAC of MBSR for services ..... | 484 | +| 5.35A.7 | Control of UE access to MBSR..... | 485 | +| 5.36 | RIM Information Transfer..... | 485 | +| 5.37 | Support for high data rate low latency services, eXtended Reality (XR) and interactive media services ..... | 485 | +| 5.37.1 | General ..... | 485 | +| 5.37.2 | Policy control enhancements to support multi-modal services ..... | 486 | +| 5.37.3 | Support of ECN marking for L4S to expose the congestion information ..... | 486 | +| 5.37.3.1 | General ..... | 486 | +| 5.37.3.2 | Support of ECN marking for L4S in NG-RAN ..... | 487 | +| 5.37.3.3 | Support of ECN marking for L4S in PSA UPF ..... | 487 | +| 5.37.4 | Network Exposure of 5GS information ..... | 488 | +| 5.37.5 | PDU Set based Handling ..... | 488 | +| 5.37.5.1 | General ..... | 488 | +| 5.37.5.2 | PDU Set Information and Identification ..... | 490 | +| 5.37.5.3 | Non-homogenous support of PDU set based handling in NG-RAN ..... | 490 | +| 5.37.6 | UL/DL policy control based on round-trip latency requirement..... | 490 | +| 5.37.7 | 5GS Packet Delay Variation monitoring and reporting..... | 491 | +| 5.37.7.1 | General ..... | 491 | +| 5.37.8 | UE power saving management..... | 491 | +| 5.37.8.1 | General ..... | 491 | +| 5.37.8.2 | Periodicity and N6 Jitter Information associated with Periodicity ..... | 492 | +| 5.37.8.3 | End of Data Burst Indication ..... | 492 | +| 5.38 | Support for Multi-USIM UE ..... | 492 | +| 5.38.1 | General ..... | 492 | +| 5.38.2 | Connection Release ..... | 493 | +| 5.38.3 | Paging Cause Indication for Voice Service..... | 493 | +| 5.38.4 | Reject Paging Request..... | 494 | +| 5.38.5 | Paging Restriction ..... | 494 | +| 5.38.6 | Paging Timing Collision Control ..... | 495 | + +| | | | +|----------|----------------------------------------------------------------------------------------------------|-----| +| 5.39 | Remote provisioning of credentials for NSSAA or secondary authentication/authorization ..... | 495 | +| 5.39.1 | General ..... | 495 | +| 5.39.2 | Configuration for the UE ..... | 495 | +| 5.40 | Support of Disaster Roaming with Minimization of Service Interruption ..... | 496 | +| 5.40.1 | General ..... | 496 | +| 5.40.2 | UE configuration and provisioning for Disaster Roaming ..... | 496 | +| 5.40.3 | Disaster Condition Notification and Determination ..... | 497 | +| 5.40.4 | Registration for Disaster Roaming service ..... | 497 | +| 5.40.5 | Handling when a Disaster Condition is no longer applicable ..... | 498 | +| 5.40.6 | Prevention of signalling overload related to Disaster Condition and Disaster Roaming service ..... | 498 | +| 5.41 | NR RedCap UEs differentiation ..... | 499 | +| 5.42 | Support of Non-seamless WLAN offload ..... | 499 | +| 5.43 | Support for 5G Satellite Backhaul ..... | 500 | +| 5.43.1 | General ..... | 500 | +| 5.43.2 | Edge Computing via UPF deployed on satellite ..... | 500 | +| 5.43.3 | Local switch for UE-to-UE communications via UPF deployed on GEO satellite ..... | 501 | +| 5.43.3.1 | General ..... | 501 | +| 5.43.3.2 | Local switch with PSA UPF deployed on satellite ..... | 501 | +| 5.43.3.3 | Local switching with UL CL/BP and local PSA UPF deployed on satellite ..... | 502 | +| 5.43.4 | Reporting of satellite backhaul to SMF ..... | 502 | +| 5.43.5 | QoS monitoring when dynamic Satellite Backhaul is used ..... | 503 | +| 5.44 | Support of Personal IoT network service ..... | 503 | +| 5.44.1 | General ..... | 503 | +| 5.44.2 | UE policy delivery for PIN ..... | 503 | +| 5.44.3 | Session management enhancement for PIN service support ..... | 504 | +| 5.44.3.1 | PDU Session Establishment for PIN ..... | 504 | +| 5.44.3.2 | Session management related policy control ..... | 504 | +| 5.44.3.3 | Non-3GPP QoS Assistance Information ..... | 504 | +| 5.44.3.4 | Non-3GPP delay budget between PINE and PEGC ..... | 504 | +| 5.44.4 | Identifiers for PIN ..... | 505 | +| 5.45 | QoS Monitoring ..... | 505 | +| 5.45.1 | General ..... | 505 | +| 5.45.2 | Packet delay monitoring ..... | 506 | +| 5.45.3 | Congestion information monitoring ..... | 506 | +| 5.45.4 | Data rate monitoring ..... | 506 | +| 5.45.5 | Void ..... | 507 | +| 5.46 | Assistance to AI/ML Operations in the Application Layer ..... | 507 | +| 5.46.1 | General ..... | 507 | +| 5.46.2 | Member UE selection assistance functionality for application operation ..... | 508 | +| 6 | Network Functions ..... | 509 | +| 6.1 | General ..... | 509 | +| 6.2 | Network Function Functional description ..... | 509 | +| 6.2.1 | AMF ..... | 509 | +| 6.2.2 | SMF ..... | 511 | +| 6.2.3 | UPF ..... | 513 | +| 6.2.4 | PCF ..... | 514 | +| 6.2.5 | NEF ..... | 514 | +| 6.2.5.0 | NEF functionality ..... | 514 | +| 6.2.5.1 | Support for CAPIF ..... | 516 | +| 6.2.5a | Void ..... | 516 | +| 6.2.6 | NRF ..... | 516 | +| 6.2.6.1 | General ..... | 516 | +| 6.2.6.2 | NF profile ..... | 516 | +| 6.2.6.3 | SCP profile ..... | 519 | +| 6.2.7 | UDM ..... | 519 | +| 6.2.8 | AUSF ..... | 520 | +| 6.2.9 | N3IWF ..... | 520 | +| 6.2.9A | TNGF ..... | 521 | +| 6.2.10 | AF ..... | 521 | +| 6.2.11 | UDR ..... | 521 | +| 6.2.12 | UDSF ..... | 522 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------|-----| +| 6.2.13 | SMSF ..... | 522 | +| 6.2.14 | NSSF ..... | 522 | +| 6.2.15 | 5G-EIR ..... | 523 | +| 6.2.16 | LMF ..... | 523 | +| 6.2.16A | GMLC ..... | 523 | +| 6.2.17 | SEPP ..... | 523 | +| 6.2.18 | Network Data Analytics Function (NWDAF) ..... | 523 | +| 6.2.19 | SCP ..... | 524 | +| 6.2.20 | W-AGF ..... | 524 | +| 6.2.21 | UE radio Capability Management Function (UCMF) ..... | 524 | +| 6.2.22 | TWIF ..... | 525 | +| 6.2.23 | NSSAAF ..... | 525 | +| 6.2.24 | DCCF ..... | 525 | +| 6.2.25 | MFAF ..... | 525 | +| 6.2.26 | ADRF ..... | 526 | +| 6.2.27 | MB-SMF ..... | 526 | +| 6.2.27a | MB-UPF ..... | 526 | +| 6.2.27b | MBSF ..... | 526 | +| 6.2.27c | MBSTF ..... | 526 | +| 6.2.28 | NSACF ..... | 526 | +| 6.2.29 | TSCTSF ..... | 527 | +| 6.2.30 | 5G DDNMF ..... | 527 | +| 6.2.31 | EASDF ..... | 527 | +| 6.2.32 | TSN AF ..... | 528 | +| 6.2.33 | NSWOF ..... | 528 | +| 6.3 | Principles for Network Function and Network Function Service discovery and selection ..... | 528 | +| 6.3.1 | General ..... | 528 | +| 6.3.1.0 | Principles for Binding, Selection and Reselection ..... | 529 | +| 6.3.1.1 | NF Discovery and Selection aspects relevant with indirect communication ..... | 532 | +| 6.3.1.2 | Location information ..... | 532 | +| 6.3.2 | SMF discovery and selection ..... | 532 | +| 6.3.3 | User Plane Function Selection ..... | 535 | +| 6.3.3.1 | Overview ..... | 535 | +| 6.3.3.2 | SMF Provisioning of available UPF(s) ..... | 536 | +| 6.3.3.3 | Selection of an UPF for a particular PDU Session ..... | 536 | +| 6.3.4 | AUSF discovery and selection ..... | 537 | +| 6.3.5 | AMF discovery and selection ..... | 538 | +| 6.3.6 | N3IWF selection ..... | 541 | +| 6.3.6.1 | General ..... | 541 | +| 6.3.6.2 | Stand-alone N3IWF selection ..... | 543 | +| 6.3.6.2a | SNPN N3IWF selection ..... | 544 | +| 6.3.6.3 | Combined N3IWF/ePDG Selection ..... | 545 | +| 6.3.6.4 | PLMN and non-3GPP access node Selection for emergency services ..... | 547 | +| 6.3.6.4.1 | General ..... | 547 | +| 6.3.6.4.2 | Stand-alone N3IWF selection ..... | 547 | +| 6.3.6.3.3 | Combined N3IWF/ePDG Selection ..... | 548 | +| 6.3.7 | PCF discovery and selection ..... | 549 | +| 6.3.7.0 | General principles ..... | 549 | +| 6.3.7.1 | PCF discovery and selection for a UE or a PDU Session ..... | 549 | +| 6.3.7.2 | Providing policy requirements that apply to multiple UE and hence to multiple PCF ..... | 552 | +| 6.3.7.3 | Binding an AF request targeting a UE address to the relevant PCF ..... | 552 | +| 6.3.7.4 | Binding an AF request targeting a UE to the relevant PCF ..... | 552 | +| 6.3.8 | UDM discovery and selection ..... | 552 | +| 6.3.9 | UDR discovery and selection ..... | 553 | +| 6.3.10 | SMSF discovery and selection ..... | 554 | +| 6.3.11 | CHF discovery and selection ..... | 554 | +| 6.3.12 | Trusted Non-3GPP Access Network selection ..... | 555 | +| 6.3.12.1 | General ..... | 555 | +| 6.3.12.2 | Access Network Selection Procedure ..... | 557 | +| 6.3.12a | Access Network selection for devices that do not support 5GC NAS over WLAN ..... | 560 | +| 6.3.12a.1 | General ..... | 560 | +| 6.3.12a.2 | Access Network Selection Procedure ..... | 560 | + +| | | | +|---------|-------------------------------------------------------------------------------------|-----| +| 6.3.12b | Access Network selection for 5G NSWO ..... | 561 | +| 6.3.13 | NWDAF discovery and selection..... | 562 | +| 6.3.14 | NEF Discovery ..... | 563 | +| 6.3.15 | UCMF Discovery and Selection..... | 564 | +| 6.3.16 | SCP discovery and selection ..... | 564 | +| 6.3.17 | NSSAAF discovery and selection ..... | 564 | +| 6.3.18 | 5G-EIR discovery and selection..... | 565 | +| 6.3.19 | DCCF discovery and selection ..... | 565 | +| 6.3.20 | ADRF discovery and selection..... | 565 | +| 6.3.21 | MFAF discovery and selection..... | 566 | +| 6.3.22 | NSACF discovery and selection..... | 566 | +| 6.3.23 | EASDF discovery and selection..... | 567 | +| 6.3.24 | TSCTSF Discovery ..... | 567 | +| 6.3.25 | AF Discovery and Selection..... | 567 | +| 6.3.26 | NRF discovery and selection..... | 568 | +| 7 | Network Function Services and descriptions..... | 568 | +| 7.1 | Network Function Service Framework ..... | 568 | +| 7.1.1 | General ..... | 568 | +| 7.1.2 | NF Service Consumer - NF Service Producer interactions ..... | 569 | +| 7.1.3 | Network Function Service discovery ..... | 571 | +| 7.1.4 | Network Function Service Authorization..... | 571 | +| 7.1.5 | Network Function and Network Function Service registration and de-registration..... | 572 | +| 7.2 | Network Function Services ..... | 572 | +| 7.2.1 | General ..... | 572 | +| 7.2.2 | AMF Services..... | 573 | +| 7.2.3 | SMF Services..... | 574 | +| 7.2.4 | PCF Services ..... | 574 | +| 7.2.5 | UDM Services ..... | 575 | +| 7.2.6 | NRF Services..... | 576 | +| 7.2.7 | AUSF Services ..... | 577 | +| 7.2.8 | NEF Services ..... | 577 | +| 7.2.8A | Void..... | 580 | +| 7.2.9 | SMSF Services ..... | 580 | +| 7.2.10 | UDR Services ..... | 580 | +| 7.2.11 | 5G-EIR Services ..... | 581 | +| 7.2.12 | NWDAF Services..... | 581 | +| 7.2.13 | UDSF Services ..... | 582 | +| 7.2.14 | NSSF Services ..... | 582 | +| 7.2.15 | BSF Services ..... | 583 | +| 7.2.16 | LMF Services ..... | 583 | +| 7.2.16A | GMLC Services ..... | 583 | +| 7.2.17 | CHF Services..... | 583 | +| 7.2.18 | UCMF Services ..... | 584 | +| 7.2.19 | AF Services ..... | 584 | +| 7.2.20 | NSSAAF Services ..... | 585 | +| 7.2.21 | DCCF Services ..... | 585 | +| 7.2.22 | MFAF Services..... | 585 | +| 7.2.23 | ADRF Services ..... | 586 | +| 7.2.24 | 5G DDNMF Services ..... | 586 | +| 7.2.25 | EASDF Services ..... | 586 | +| 7.2.26 | TSCTSF Services ..... | 586 | +| 7.2.27 | NSACF Services..... | 587 | +| 7.2.28 | MB-SMF Services ..... | 587 | +| 7.2.29 | UPF Services ..... | 588 | +| 7.3 | Exposure..... | 588 | +| 8 | Control and User Plane Protocol Stacks ..... | 588 | +| 8.1 | General ..... | 588 | +| 8.2 | Control Plane Protocol Stacks..... | 588 | +| 8.2.1 | Control Plane Protocol Stacks between the 5G-AN and the 5G Core: N2 ..... | 588 | +| 8.2.1.1 | General..... | 588 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------| +| 8.2.1.2 | 5G-AN - AMF ..... | 589 | +| 8.2.1.3 | 5G-AN - SMF ..... | 590 | +| 8.2.2 | Control Plane Protocol Stacks between the UE and the 5GC ..... | 590 | +| 8.2.2.1 | General ..... | 590 | +| 8.2.2.2 | UE - AMF ..... | 592 | +| 8.2.2.3 | UE - SMF ..... | 592 | +| 8.2.3 | Control Plane Protocol Stacks between the network functions in 5GC ..... | 593 | +| 8.2.3.1 | The Control Plane Protocol Stack for the service based interface ..... | 593 | +| 8.2.3.2 | The Control Plane protocol stack for the N4 interface between SMF and UPF ..... | 593 | +| 8.2.4 | Control Plane for untrusted non 3GPP Access ..... | 593 | +| 8.2.5 | Control Plane for trusted non-3GPP Access ..... | 594 | +| 8.2.6 | Control Plane for W-5GAN Access ..... | 595 | +| 8.2.7 | Control Plane for Trusted WLAN Access for N5CW Device ..... | 595 | +| 8.3 | User Plane Protocol Stacks ..... | 595 | +| 8.3.1 | User Plane Protocol Stack for a PDU Session ..... | 595 | +| 8.3.2 | User Plane for untrusted non-3GPP Access ..... | 597 | +| 8.3.3 | User Plane for trusted non-3GPP Access ..... | 597 | +| 8.3.4 | User Plane for W-5GAN Access ..... | 597 | +| 8.3.5 | User Plane for N19-based forwarding of a 5G VN group ..... | 598 | +| 8.3.6 | User Plane for Trusted WLAN Access for N5CW Device ..... | 598 | +| Annex A (informative): | Relationship between Service-Based Interfaces and Reference Points .. | 599 | +| Annex B (normative): | Mapping between temporary identities ..... | 601 | +| Annex C (informative): | Guidelines and Principles for Compute-Storage Separation ..... | 602 | +| Annex D (informative): | 5GS support for Non-Public Network deployment options ..... | 603 | +| D.1 | Introduction ..... | 603 | +| D.2 | Support of Non-Public Network as a network slice of a PLMN ..... | 603 | +| D.3 | Support for access to PLMN services via Stand-alone Non-Public Network and access to Stand-alone Non Public Network services via PLMN ..... | 604 | +| D.4 | Support for UE capable of simultaneously connecting to an SNPN and a PLMN ..... | 605 | +| D.5 | Support for keeping UE in CM-CONNECTED state in overlay network when accessing services via NWu ..... | 605 | +| D.6 | Support for session/service continuity between SNPN and PLMN when using N3IWF ..... | 606 | +| D.7 | Guidance for underlay network to support QoS differentiation for User Plane IPsec Child SA ..... | 607 | +| D.7.1 | Network initiated QoS ..... | 607 | +| D.7.2 | UE initiated QoS ..... | 608 | +| Annex E (informative): | Communication models for NF/NF services interaction ..... | 610 | +| E.1 | General ..... | 610 | +| Annex F (informative): | Redundant user plane paths based on multiple UEs per device ..... | 612 | +| Annex G (informative): | SCP Deployment Examples ..... | 615 | +| G.1 | General ..... | 615 | +| G.2 | An SCP based on service mesh ..... | 615 | +| G.2.1 | Introduction ..... | 615 | +| G.2.2 | Communication across service mesh boundaries ..... | 616 | +| G.3 | An SCP based on independent deployment units ..... | 617 | +| G.4 | An SCP deployment example based on name-based routing ..... | 618 | +| G.4.0 | General Information ..... | 618 | +| G.4.1 | Service Registration and Service Discovery ..... | 619 | +| G.4.2 | Overview of Deployment Scenario ..... | 620 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------|------------| +| G.4.3 | References ..... | 620 | +| Annex H (normative): | PTP usage guidelines..... | 621 | +| H.1 | General..... | 621 | +| H.2 | Signalling of ingress time for time synchronization ..... | 621 | +| H.3 | Void..... | 621 | +| H.4 | Path and Link delay measurements..... | 621 | +| Annex I (normative): | TSN usage guidelines ..... | 623 | +| I.1 | Determination of traffic pattern information ..... | 623 | +| Annex J (informative): | Link MTU considerations..... | 625 | +| Annex K (normative): | Port and user plane node management information exchange..... | 627 | +| K.1 | Standardized port and user plane node management information ..... | 627 | +| K.2 | Port and user plane node management information exchange for time synchronization ..... | 643 | +| K.2.1 | Capability exchange..... | 643 | +| K.2.2 | PTP Instance configuration ..... | 644 | +| K.2.2.1 | General ..... | 644 | +| K.2.2.2 | Configuration for Sync and Announce reception timeouts ..... | 645 | +| K.2.2.3 | Configuration for PTP port states..... | 645 | +| K.2.2.4 | Configuration for PTP grandmaster function ..... | 646 | +| K.2.2.5 | Configuration for Sync and Announce intervals ..... | 646 | +| K.2.2.6 | Configuration for transport protocols ..... | 647 | +| Annex L (normative): | Support of GERAN/UTRAN access ..... | 648 | +| Annex M (normative): | Interworking with TSN deployed in the Transport Network ..... | 649 | +| M.1 | Mapping of the parameters between 5GS and TSN UNI..... | 649 | +| M.2 | TL-Container Information..... | 653 | +| Annex N (informative): | Support for access to Localized Services..... | 656 | +| N.1 | General..... | 656 | +| N.2 | Enabling access to Localized Services..... | 656 | +| N.2.1 | General ..... | 656 | +| N.2.2 | Configuration of network to provide access to Localized Services ..... | 657 | +| N.2.3 | Session Management aspects ..... | 657 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------|------------| +| N.3 | Selection of network providing access to Localized Services ..... | 657 | +| N.4 | Enabling the UE access to Localized Services ..... | 657 | +| N.5 | Support for leaving network that provides access to Localized Services ..... | 657 | +| N.6 | Configuration of Credentials Holder for determining SNPN selection information ..... | 658 | +| Annex O (informative): | Allowing UE to simultaneously send data to different groups with different QoS policy ..... | 660 | +| O.1 | A PDU Session with multiple QoS Flows for different groups ..... | 660 | +| O.2 | Multiple PDU Sessions for different groups..... | 661 | +| O.3 | A PDU Session targeting a predefined group formed of multiple sub-groups ..... | 662 | +| Annex P (informative): | Personal IoT Networks ..... | 664 | +| P.1 | PIN Reference Architecture ..... | 664 | +| P.2 | Session management and traffic routing for PIN ..... | 664 | +| Annex Q (informative): | Satellite coverage availability information ..... | 666 | +| Annex R (informative): | Change history..... | 667 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document defines the Stage 2 system architecture for the 5G System. The 5G System provides data connectivity and services. + +This specification covers both roaming and non-roaming scenarios in all aspects, including interworking between 5GS and EPS, mobility within 5GS, QoS, policy control and charging, authentication and in general 5G System wide features e.g. SMS, Location Services, Emergency Services. + +ITU-T Recommendation I.130 [11] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [12] defines Stage 2 of the method. + +TS 23.502 [3] contains the stage 2 procedures and flows for 5G System and it is a companion specification to this specification. + +TS 23.503 [45] contains the stage 2 Policy Control and Charging architecture for 5G System and it is a companion specification to this specification. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.261: "Service requirements for next generation new services and markets; Stage 1". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 23.203: "Policies and Charging control architecture; Stage 2". +- [5] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS); Stage 2". +- [6] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface: Stage 3". +- [7] IETF RFC 7157: "IPv6 Multihoming without Network Address Translation". +- [8] IETF RFC 4191: "Default Router Preferences and More-Specific Routes". +- [9] IETF RFC 2131: "Dynamic Host Configuration Protocol". +- [10] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration". +- [11] ITU-T Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN". +- [12] ITU-T Recommendation Q.65: "The unified functional methodology for the characterization of services and network capabilities". +- [13] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS): Stage 3". + +- [14] Void. +- [15] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [16] 3GPP TS 22.173: "IMS Multimedia Telephony Service and supplementary services; Stage 1". +- [17] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode". +- [18] 3GPP TS 23.167: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS) emergency sessions". +- [19] 3GPP TS 23.003: "Numbering, Addressing and Identification". +- [20] IETF RFC 7542: "The Network Access Identifier". +- [21] 3GPP TS 23.002: "Network Architecture". +- [22] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; Stage 2". +- [23] 3GPP TS 23.221: "Architectural requirements". +- [24] 3GPP TS 22.153: "Multimedia priority service". +- [25] 3GPP TS 22.011: "Service Accessibility". +- [26] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [27] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description". +- [28] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification". +- [29] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [30] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [31] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2". +- [32] 3GPP TS 23.214: "Architecture enhancements for control and user plane separation of EPC nodes; Stage 2". +- [33] 3GPP TS 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles". +- [34] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". +- [35] 3GPP TS 33.126: "Lawful Interception Requirements". +- [36] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [37] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1". +- [38] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [39] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2". +- [40] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2". +- [41] 3GPP TS 32.240: "Charging management; Charging architecture and principles". +- [42] 3GPP TS 38.401: "NG-RAN Architecture description". + +- [43] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [44] IETF RFC 4960: "Stream Control Transmission Protocol". +- [45] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System". +- [46] 3GPP TS 23.041: "Public Warning System". +- [47] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [48] 3GPP TS 24.502: "Access to the 5G System (5GS) via non-3GPP access networks; Stage 3". +- [49] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [50] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode". +- [51] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [52] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode". +- [53] Void. +- [54] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)". +- [55] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [56] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [57] IETF RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)". +- [58] 3GPP TS 29.510: "5G System: Network function repository services; Stage 3". +- [59] 3GPP TS 29.502: "5G System: Session Management Services: Stage 3". +- [60] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2) ". +- [61] 3GPP TS 23.380: "IMS Restoration Procedures". +- [62] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". + +- [63] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2". +- [64] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs". +- [65] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes; Stage 3". +- [66] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements". +- [67] 3GPP TS 32.290: "5G system; Services, operations and procedures of charging using Service Based Interface (SBI)". +- [68] 3GPP TS 32.255: "5G Data connectivity domain charging; Stage 2". +- [69] 3GPP TS 38.306: "NR; User Equipment -UE) radio access capabilities". +- [70] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access -E-UTRA); User Equipment -UE) radio access capabilities". +- [71] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3". +- [72] Void. +- [73] IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)". +- [74] IETF RFC 3162: "RADIUS and IPv6". +- [75] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". +- [76] 3GPP TS 26.238: "Uplink streaming". +- [77] 3GPP TR 26.939: "Guidelines on the Framework for Live Uplink Streaming (FLUS)". +- [78] International Telecommunication Union (ITU), Standardization Bureau (TSB): "Operational Bulletin No. 1156"; (retrieved October 5, 2018). +- [79] 3GPP TS 28.533: "Management and orchestration; Architecture framework". +- [80] 3GPP TS 24.250: "Protocol for Reliable Data Service; Stage 3". +- [81] IETF RFC 8684: "TCP Extensions for Multipath Operation with Multiple Addresses". +- [82] IETF RFC 8803: "0-RTT TCP Convert Protocol". +- [83] IEEE Std 802.1CB-2017: "IEEE Standard for Local and metropolitan area networks-Frame Replication and Elimination for Reliability". +- [84] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)". +- [85] WiFi Alliance Technical Committee, Hotspot 2.0 Technical Task Group: "Hotspot 2.0 (Release 2) Technical Specification". +- [86] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [87] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [88] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [89] CableLabs DOCSIS MULPI: "Data-Over-Cable Service Interface Specifications DOCSIS 3.1, MAC and Upper Layer Protocols Interface Specification". +- [90] BBF TR-124 issue 5: "Functional Requirements for Broadband Residential Gateway Devices". +- [91] BBF TR-101 issue 2: "Migration to Ethernet-Based Broadband Aggregation". + +- [92] BBF TR-178 issue 1: "Multi-service Broadband Network Architecture and Nodal Requirements". +- [93] BBF TR-456 issue 2: "AGF Functional Requirements". +- [94] BBF WT-457: "FMIF Functional Requirements". +- Editor's note:** The reference to BBF WT-457 will be revised when finalized by BBF. +- [95] Void. +- [96] Void. +- [97] IEEE Std 802.1AB-2016: "IEEE Standard for Local and metropolitan area networks -- Station and Media Access Control Connectivity Discovery". +- [98] IEEE Std 802.1Q-2022: "IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks". +- [99] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)". +- [100] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". +- [101] 3GPP TS 29.274: "Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3". +- [102] 3GPP TS 23.632: "User Data Interworking, Coexistence and Migration; stage 2". +- [103] 3GPP TS 29.563: "5G System (5GS); HSS services for interworking with UDM; Stage 3". +- [104] IEEE Std 802.1AS-2020: "IEEE Standard for Local and metropolitan area networks--Timing and Synchronization for Time-Sensitive Applications". +- [105] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains". +- [106] IEEE Std 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications". +- [107] IEEE Std 1588-2008: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". +- [108] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". +- [109] 3GPP TS 24.193: "Access Traffic Steering, Switching and Splitting; Stage 3". +- [110] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". +- [111] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1". +- [112] 3GPP TR 38.824: "Study on physical layer enhancements for NR ultra-reliable and low latency case (URLLC)". +- [113] IEEE: "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)", . +- [114] 3GPP TS 32.256: "Charging Management; 5G connection and mobility domain charging; Stage 2". +- [115] 3GPP TS 33.210: "Network Domain Security (NDS); IP network layer security". +- [116] 3GPP TS 38.415: "PDU Session User Plane Protocol". + +- [117] 3GPP TS 24.535: "Device-side Time-Sensitive Networking (TSN) Translator (DS-TT) to network-side TSN Translator (NW-TT) protocol aspects; Stage 3". +- [118] 3GPP TS 32.274: "Charging Management; Short Message Service (SMS) charging". +- [119] 3GPP TS 23.008: "Organization of subscriber data". +- [120] 3GPP TS 38.314: "NR; Layer 2 measurements". +- [121] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [122] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3". +- [123] 3GPP TS 32.254: "Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging". +- [124] 3GPP TS 33.535: "Authentication and Key Management for Applications based on 3GPP credentials in the 5G System (5GS)". +- [125] 3GPP TS 38.410: "NG-RAN; NG general aspects and principles". +- [126] IEEE Std 1588: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", Edition 2019. +- [127] ST 2059-2:2015: "SMPTE Standard - SMPTE Profile for Use of IEEE-1588 Precision Time Protocol in Professional Broadcast Applications". +- [128] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [129] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services". +- [130] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [131] IEEE Std 802.3: "Ethernet". +- [132] 3GPP TS 29.561: "5G System; Interworking between 5G Network and external Data Networks; Stage 3". +- [133] 3GPP TS 29.513: "Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3". +- [134] 3GPP TS 23.558: "Architecture for enabling Edge Applications (EA)". +- [135] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture". +- [136] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2". +- [137] GSMA NG.116: "Generic Network Slice Template". +- [138] IETF RFC 3948: "UDP Encapsulation of IPsec ESP Packets". +- [139] 3GPP TS 24.539: "5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3". +- [140] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping architecture". +- [141] 3GPP TS 33.223: "Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function". +- [142] 3GPP TS 23.540: "Technical realization of Service Based Short Message Service; Stage 2". +- [143] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". +- [144] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3". + +- [145] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository Services for Subscription Data; Stage 3". +- [146] IEEE Std P802.1Qdj-d1.3: "IEEE Draft Standard for Local and metropolitan area networks - Bridges and Bridged Networks - Amendment XX: Configuration Enhancements for Time-Sensitive Networking". +- [147] Void. +- [148] 3GPP TS 28.557: "Management and orchestration; Management of Non-Public Networks (NPN)". +- [149] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM)". +- [150] IETF RFC 8655: "Deterministic Networking Architecture". +- [151] IETF RFC 8343: "A YANG Data Model for Interface Management". +- [152] IETF RFC 8344: "A YANG Data Model for IP Management". +- [153] IETF RFC 7224: " IANA Interface Type YANG Module". +- [154] IETF draft-ietf-detnet-yang: "Deterministic Networking (DetNet) YANG Model". +- Editor's note: The reference to draft-ietf-detnet-yang will be revised to RFC when finalized by IETF.** +- [155] IETF RFC 6241: "Network Configuration Protocol (NETCONF)". +- [156] IETF RFC 8040: "RESTCONF Protocol". +- [157] IETF RFC 8939: "Deterministic Networking (DetNet) Data Plane: IP". +- [158] IETF RFC 5279: "A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)". +- [159] IETF RFC 9330: "Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture". +- [160] IETF RFC 9331: "Explicit Congestion Notification (ECN) Protocol for Very Low Queuing Delay (L4S)". +- [161] IETF RFC 9332: "Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)". +- [162] IETF RFC 6603: "Prefix Exclude Option for DHCPv6-based Prefix Delegation". +- [163] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". +- [164] ITU-T Recommendation G.810: "Definitions and terminology for synchronization networks". +- [165] 3GPP TS 38.470: "NG-RAN; F1 general aspects and principles". +- [166] IETF RFC 9000: "QUIC: A UDP-Based Multiplexed and Secure Transport". +- [167] IETF RFC 9001: "Using TLS to Secure QUIC". +- [168] IETF RFC 9002: "QUIC Loss Detection and Congestion Control". +- [169] IETF RFC 9221: "An Unreliable Datagram Extension to QUIC". +- [170] IETF RFC 9298: "Proxying UDP in HTTP". +- [171] IETF RFC 9114: "Hypertext Transfer Protocol Version 3 (HTTP/3)". +- [172] IETF RFC 9297: "HTTP Datagrams and the Capsule Protocol". +- [173] IETF RFC 9220: "Bootstrapping WebSockets with HTTP/3". +- [174] draft-ietf-quic-multipath: "Multipath Extension for QUIC". + +**Editor's note:** The above document cannot be formally referenced until it is published as an RFC. + +- [175] 3GPP TS 28.530: "Management and orchestration; Concepts, use cases and requirements". +- [176] 3GPP TS 28.531: "Management and orchestration; Provisioning". +- [177] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [178] IEEE Std 802.1CBdb-2021: "Amendment 2: Extend Stream Identification Functions". +- [179] 3GPP TS 26.522: "5G Real-time Media Transport Protocol Configurations". +- [180] 3GPP TS 23.586: "Architectural Enhancements to support Ranging based services and Sidelink Positioning". +- [181] 3GPP TS 23.542: "Application layer support for Personal IoT Network". +- [182] IETF RFC 8415: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". +- [183] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". +- [184] 3GPP TS 23.289: "Mission Critical services over 5G System; Stage 2". +- [185] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [186] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)". +- [187] IETF RFC 6184: "RTP Payload Format for H.264 Video". +- [188] IETF RFC 7798: "RTP Payload Format for High Efficiency Video Coding (HEVC) ". +- [189] IETF RFC 8285: "A General Mechanism for RTP Header Extensions". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**5G VN Group:** A set of UEs using private communication for 5G LAN-type service. + +**5G Access Network:** An access network comprising a NG-RAN and/or non-3GPP AN connecting to a 5G Core Network. + +**5G Access Stratum-based Time Distribution:** A time synchronization distribution method that is used by an NG-RAN to provide the 5GS time to the UE(s) over the radio interface using procedures specified in TS 38.331 [28]. + +**5G Core Network:** The core network specified in the present document. It connects to a 5G Access Network. + +**5G LAN-Type Service:** A service over the 5G system offering private communication using IP and/or non-IP type communications. + +**5G LAN-Virtual Network:** A virtual network over the 5G system capable of supporting 5G LAN-type service. + +**5G NSWO:** The 5G NSWO is the capability provided by 5G system and by UE to enable the connection to a WLAN access network using 5GS credentials without registration to 5GS. + +**5G QoS Flow or QoS Flow:** The finest granularity for QoS forwarding treatment in the 5G System. All traffic mapped to the same 5G QoS Flow receive the same forwarding treatment (e.g. scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). Providing different QoS forwarding treatment requires separate 5G QoS Flow. + +**5G QoS Identifier:** A scalar that is used as a reference to a specific QoS forwarding behaviour (e.g. packet loss rate, packet delay budget) to be provided to a 5G QoS Flow. This may be implemented in the access network by the 5QI referencing node specific parameters that control the QoS forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). + +**5G System:** 3GPP system consisting of 5G Access Network (AN), 5G Core Network and UE. + +**5G-BRG:** The 5G-BRG is a 5G-RG defined in BBF. + +**5G-CRG:** The 5G-CRG is a 5G-RG specified in DOCSIS MULPI [89]. + +**5G-RG:** A 5G-RG is a RG capable of connecting to 5GC playing the role of a UE with regard to the 5G core. It supports secure element and exchanges N1 signalling with 5GC. The 5G-RG can be either a 5G-BRG or 5G-CRG. + +**Access Traffic Steering:** The procedure that selects an access network for a new data flow and transfers the traffic of this data flow over the selected access network. Access traffic steering is applicable between one 3GPP access and one non-3GPP access. + +**Access Traffic Switching:** The procedure that moves all traffic of an ongoing data flow from one access network to another access network in a way that maintains the continuity of the data flow. Access traffic switching is applicable between one 3GPP access and one non-3GPP access. + +**Access Traffic Splitting:** The procedure that splits the traffic of a data flow across multiple access networks. When traffic splitting is applied to a data flow, some traffic of the data flow is transferred via one access and some other traffic of the same data flow is transferred via another access. Access traffic splitting is applicable between one 3GPP access and one non-3GPP access. + +**Allowed NSSAI:** Indicating the S-NSSAIs values the UE could use in the Serving PLMN in the current Registration Area. + +**Allowed Area:** Area where the UE is allowed to initiate communication as specified in clause 5.3.2.3. + +**Alternative S-NSSAI:** Indicating a compatible S-NSSAI for an S-NSSAI in the Allowed NSSAI that the AMF uses to replace an S-NSSAI when the S-NSSAI is not available or congested, as specified in clause 5.15.19. + +**AMF Region:** An AMF Region consists of one or multiple AMF Sets. + +**AMF Set:** An AMF Set consists of some AMFs that serve a given area and Network Slice(s). AMF Set is unique within an AMF Region and it comprises of AMFs that support the same Network Slice(s). Multiple AMF Sets may be defined per AMF Region. The AMF instances in the same AMF Set may be geographically distributed but have access to the same context data. + +**Application Identifier:** An identifier that can be mapped to a specific application traffic detection rule. + +**AUSF Group ID:** This refers to one or more AUSF instances managing a specific set of SUPIs. An AUSF Group consists of one or multiple AUSF Sets. + +**Binding Indication:** Information included by a NF service producer to a NF service consumer in request responses or notifications to convey the scope within which selection/reselection of target NF/NF Services may be performed, or information included by the NF service consumer in requests or subscriptions to convey the scope within which selection/reselection of notification targets or the selection of other service(s) that the NF consumer produces for the same data context may be performed. See clause 6.3.1.0. + +**BSF Group ID:** This refers to one or more BSF instances managing a specific set of SUPIs or GPSIs. A BSF Group consists of one or multiple BSF Sets. + +**Configured NSSAI:** NSSAI provisioned in the UE applicable to one or more PLMNs. + +**CHF Group ID:** This refers to one or more CHF instances managing a specific set of SUPIs. + +**Credentials Holder:** Entity which authenticates and authorizes access to an SNPN separate from the Credentials Holder. + +**Data Burst:** A set of multiple PDUs generated and sent by the application in a short period of time. + +NOTE 1: A Data Burst can be composed of one or multiple PDU Sets. + +**Default UE credentials:** Information configured in the UE to make the UE uniquely identifiable and verifiably secure to perform UE onboarding. + +**Default Credentials Server (DCS):** An entity that can perform authentication based on the Default UE credentials or provide means for another entity to perform authentication based on the Default UE credentials. + +**Delegated Discovery:** This refers to delegating the discovery and associated selection of NF instances or NF service instances to an SCP. + +**Direct Communication:** This refers to the communication between NFs or NF services without using an SCP. + +**Disaster Condition:** See definition in TS 22.261 [2]. + +**Disaster Inbound Roamer:** See definition in TS 22.261 [2]. + +**Disaster Roaming:** See definition in TS 22.261 [2]. + +**DN Access Identifier (DNAI):** Identifier of a user plane access to one or more DN(s) where applications are deployed. + +**Emergency Registered:** A UE is considered Emergency Registered over an Access Type in a PLMN when registered for emergency services only over this Access Type in this PLMN. + +**Endpoint Address:** An address in the format of an IP address or FQDN, which is used to determine the host/authority part of the target URI. This Target URI is used to access an NF service (i.e. to invoke service operations) of an NF service producer or for notifications to an NF service consumer. + +**En-gNB:** as defined in TS 37.340 [31]. + +**Expected UE Behaviour:** Set of parameters provisioned by an external party to 5G network functions on the foreseen or expected UE behaviour, see clause 5.20. + +**Fixed Network Residential Gateway:** A Fixed Network RG (FN-RG) is a RG that it does not support N1 signalling and it is not 5GC capable. + +**Fixed Network Broadband Residential Gateway:** A Fixed Network RG (FN-BRG) is a FN-RG specified in BBF TR-124 [90]. + +**Fixed Network Cable Residential Gateway:** A Fixed Network Cable RG (FN-CRG) is a FN-RG with cable modem specified in DOCSIS MULPI [89]. + +**Forbidden Area:** An area where the UE is not allowed to initiate communication as specified in clause 5.3.2.3. + +**GBR QoS Flow:** A QoS Flow using the GBR resource type or the Delay-critical GBR resource type and requiring guaranteed flow bit rate. + +**Group ID for Network Selection (GIN):** An identifier used during SNPN selection to enhance the likelihood of selecting a preferred SNPN that supports a Default Credentials Server or a Credentials Holder. + +**(g)PTP-based Time Distribution:** a method to distribute timing among entities in a (g)PTP domain using PTP messages generated by a GM (in the case the GM is external to 5GS) or by 5GS (in the case the 5GS acts as a GM for a given (g)PTP domain). Possible dependencies between (g)PTP-based Time Distribution and 5G Access Stratum-based Time Distribution are described in clause 5.27.1. The synchronization process is described in clause 5.27.1 and follows the applicable profiles of IEEE Std 802.1AS [104] or IEEE Std 1588 [126]. + +**Home Network Public Key Identifier:** An identifier used to indicate which public/private key pair is used for SUPI protection and de-concealment of the SUCI as specified in TS 23.003 [19]. + +**IAB-donor:** This is a NG-RAN node that supports Integrated access and backhaul (IAB) feature and provides connection to the core network to IAB-nodes. It supports the CU function of the CU/DU architecture for IAB defined in TS 38.401 [42]. + +**IAB-node:** A relay node that supports wireless in-band and out-of-band relaying of NR access traffic via NR Uu backhaul links. It supports the UE function and the DU function of the CU/DU architecture for IAB defined in TS 38.401 [42]. + +**Indirect Communication:** This refers to the communication between NFs or NF services via an SCP. + +**Initial Registration:** UE registration in RM-DEREGISTERED state as specified in clause 5.3.2. + +**Intermediate SMF (I-SMF):** An SMF that is inserted to support a PDU session as the UE is located in an area which cannot be controlled by the original SMF because the UPF(s) belong to a different SMF Service Area. + +**Local Area Data Network:** a DN that is accessible by the UE only in specific locations, that provides connectivity to a specific DNN, and whose availability is provided to the UE. + +**Local Break Out (LBO):** Roaming scenario for a PDU Session where the PDU Session Anchor and its controlling SMF are located in the serving PLMN (VPLMN). + +**LTE-M:** a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of E-UTRA RAT type, and defined to identify in the Core Network the E-UTRA when used by a UE indicating Category M. + +**MA PDU Session:** A PDU Session that provides a PDU connectivity service, which can use one access network at a time, or simultaneously one 3GPP access network and one non-3GPP access network. + +**Mobile Base Station Relay:** A mobile base station acts as a relay between a UE and the 5G network. Such mobile base station relay can for example be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle). See description of TS 22.261 [2]. A mobile Base Station Relay is supported in 5GS with the IAB-architecture with mobility as specified in clause 5.35A and that described in TS 38.401 [42]. + +**Master RAN node:** A Master node as defined in TS 37.340 [31]. + +**Mobility Pattern:** Network concept of determining within the AMF the UE mobility parameters as specified in clause 5.3.2.4. + +**Mobility Registration Update:** UE re-registration when entering new TA outside the TAI List as specified in clause 5.3.2. + +**MPS-subscribed UE:** A UE having a USIM with MPS subscription. + +**Multi-USIM UE:** A UE with multiple USIMs, capable of maintaining a separate registration state with a PLMN for each USIM at least over 3GPP Access and supporting one or more of the features described in clause 5.38. + +**NB-IoT UE Priority:** Numerical value used by the NG-RAN to prioritise between different UEs accessing via NB-IoT. + +**NGAP UE association:** The logical per UE association between a 5G-AN node and an AMF. + +**NGAP UE-TNLA-binding:** The binding between a NGAP UE association and a specific TNL association for a given UE. + +**Network Function:** A 3GPP adopted or 3GPP defined processing function in a network, which has defined functional behaviour and 3GPP defined interfaces. + +NOTE 2: A network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure. + +**Network Instance:** Information identifying a domain. Used by the UPF for traffic detection and routing. + +**Network Slice:** A logical network that provides specific network capabilities and network characteristics. + +**Network Slice Area of Service:** The area where a UE can access and get service of a particular network slice as more than zero resources are allocated to the network slice in the NG-RAN cells. + +**Network Slice instance:** A set of Network Function instances and the required resources (e.g. compute, storage and networking resources) which form a deployed Network Slice. + +**Non-GBR QoS Flow:** A QoS Flow using the Non-GBR resource type and not requiring guaranteed flow bit rate. + +**NSI ID:** an identifier for identifying the Core Network part of a Network Slice instance when multiple Network Slice instances of the same Network Slice are deployed, and there is a need to differentiate between them in the 5GC. + +**NF instance:** an identifiable instance of the NF. + +**NF service:** a functionality exposed by a NF through a service-based interface and consumed by other authorized NFs. + +**NF service instance:** an identifiable instance of the NF service. + +**NF service operation:** An elementary unit a NF service is composed of. + +**NF Service Set:** A group of interchangeable NF service instances of the same service type within an NF instance. The NF service instances in the same NF Service Set have access to the same context data. + +**NF Set:** A group of interchangeable NF instances of the same type, supporting the same services and the same Network Slice(s). The NF instances in the same NF Set may be geographically distributed but have access to the same context data. + +**NG-RAN:** A radio access network that supports one or more of the following options with the common characteristics that it connects to 5GC: + +- 1) Standalone New Radio. +- 2) New Radio is the anchor with E-UTRA extensions. +- 3) Standalone E-UTRA. +- 4) E-UTRA is the anchor with New Radio extensions. + +**Non-3GPP QoS Assistance Information:** A set of QoS assistance information provided to the UE (e.g. PEGC) to enable the UE to perform QoS differentiation for the connected devices in the non-3GPP network behind the UE. + +**Non-Allowed Area:** Area where the UE is allowed to initiate Registration procedure but no other communication as specified in clause 5.3.2.3. + +**Non-Public Network:** See definition in TS 22.261 [2]. + +**Non-Seamless Non-3GPP offload:** The offload of user plane traffic via non-3GPP access without traversing either N3IWF/TNGF or UPF. + +**Non-Seamless WLAN offload:** Non-Seamless Non-3GPP offload when the non-3GPP access network is WLAN. + +**Onboarding Network:** Either a PLMN enabling Remote Provisioning for a registered UE, or an Onboarding SNPN. + +**Onboarding Standalone Non-Public Network:** An SNPN providing Onboarding access and enabling Remote Provisioning for a UE registered for Onboarding as specified in clause 4.2.2.2.4 of TS 23.502 [3]. + +**Partially Allowed NSSAI:** Indicating the S-NSSAIs values the UE could use in the Serving PLMN or SNPN in some of the TAs in the current Registration Area. Each S-NSSAI in the Partially Allowed NSSAI is associated with a list of TAs where the S-NSSAI is supported. + +**PCF Group ID:** This refers to one or more PCF instances managing a specific set of SUPIs. A PCF Group consists of one or multiple PCF Sets. + +**PDU Connectivity Service:** A service that provides exchange of PDUs between a UE and a Data Network. + +**PDU Session:** Association between the UE and a Data Network that provides a PDU connectivity service. + +**PDU Session Type:** The type of PDU Session which can be IPv4, IPv6, IPv4v6, Ethernet or Unstructured. + +**PDU Set:** One or more PDUs carrying the payload of one unit of information generated at the application level (e.g. frame(s) or video slice(s) etc. for eXtended Reality (XR) Services). All the PDUs of a PDU set are transmitted within the same QoS Flow. + +**Pending NSSAI:** NSSAI provided by the Serving PLMN during a Registration procedure, indicating the S-NSSAI(s) for which the network slice-specific authentication and authorization procedure is pending. + +**Periodic Registration Update:** UE re-registration at expiry of periodic registration timer as specified in clause 5.3.2. + +**Personal IoT Network (PIN):** A network with group of element(s) (i.e. UE or non-3GPP device) that are able to communicate with each other directly, communicate with each other via intermediate element(s), communicate with each other via 5GS, or communicate with external DN via 5GS. + +**PIN Element (PINE):** A UE or non-3GPP device that is part of the group of elements in a PIN. + +**PIN Element with Gateway Capability (PEGC):** A PIN Element with the ability to provide DN connectivity via the 5G network for other PIN Elements and/or a PIN Element with the ability to provide relay functionality for communication between PIN Elements. Only a UE is able to act as a PEGC. A PIN includes at least one PEGC. + +NOTE 3: In the context of PIN, the terms PEGC and UE with PEGC capability are synonymous, therefore when the term PEGC is used, it is also intended as UE. + +**PIN Element with Management Capability (PEMC):** A PIN Element with capability to manage the PIN and the management is supported by an AF if deployed. A PIN includes at least one PEMC. + +NOTE 4: A UE that is a PIN Element may both act as PEMC and PEGC. + +**PIN management traffic:** The traffic among PINE, PEGC, PEMC and AF for PIN related to the management of PIN. + +**PIN-DN communication:** The communication between PINE and DN via a PEGC and 5G network, as well as the communication between PEGC and DN via 5G network. The communication includes both the data traffic and the PIN management traffic (e.g. the data traffic towards the internet or the PIN management traffic towards the PIN AF). + +**PIN direct communication:** The communication without traversing 5G network between two PIN Elements (e.g. between a PIN Element and a PEGC, between a PIN Element and a PEMC, between a PEMC and a PEGC and between two PEGCs). The communication traverses intermediate PIN Element(s) or not. The communication includes both the data traffic and the PIN management traffic (e.g. the data traffic between 2 PINEs or the PIN management traffic between PINE and PEMC). + +**PIN indirect communication:** The communication with traversing 5G network between PIN Elements connected to different PEGCs of the same PIN, and between a PIN Element and a PEMC via PEGC. The communication includes both the data traffic and the PIN management traffic (e.g. the data traffic between 2 PINEs or the PIN management traffic between PINE and PEMC). + +**PLMN with Disaster Condition:** A PLMN to which a Disaster Condition applies. + +**Pre-configured 5QI:** Pre-defined QoS characteristics configured in the AN and 5GC and referenced via a non-standardized 5QI value. + +**Primary cell:** as defined in TS 36.331 [51]. + +**Primary RAT:** RAT of the Master RAN node, when Dual Connectivity is used; otherwise RAT of the RAN node. + +**Private communication:** See definition in TS 22.261 [2]. + +**Provisioning Server:** Entity that provisions network credentials and other data in the UE to enable SNPN access. + +**PTP domain:** As defined in IEEE Std 1588 [126]. + +**Public network integrated NPN:** A non-public network deployed with the support of a PLMN. + +**(Radio) Access Network:** See 5G Access Network. + +**RAT type:** Identifies the transmission technology used in the access network for both 3GPP accesses and non-3GPP Accesses, for example, NR, NB-IOT, Untrusted Non-3GPP, Trusted Non-3GPP, Trusted IEEE 802.11 Non-3GPP access, Wireline, Wireline-Cable, Wireline-BBF, etc. + +**NR RedCap:** a 3GPP RAT type Identifier used in the Core Network only, which is a sub-type of NR RAT type, and defined to identify in the Core Network the NR when used by a UE indicating NR RedCap. + +**Requested NSSAI:** NSSAI provided by the UE to the Serving PLMN during registration. + +**Residential Gateway:** The Residential Gateway (RG) is a device providing, for example voice, data, broadcast video, video on demand, to other devices in customer premises. + +**Routing Binding Indication:** Information included in a request or notification and that can be used by the SCP for discovery and associated selection to of a suitable target. See clauses 6.3.1.0 and 7.1.2 + +**Routing Indicator:** Indicator that allows together with SUCI/SUPI Home Network Identifier to route network signalling to AUSF and UDM instances capable to serve the subscriber. + +**RRC\_IDLE, RRC\_CONNECTED, RRC\_INACTIVE:** As defined in TS 38.331 [28] and TS 38.306 [69]. + +**SCP Domain:** A configured group of one or more SCP(s) and zero or more NF instances(s). An SCP within the group can communicate with any NF instance or SCP within the same group directly, i.e. without passing through an intermediate SCP. + +**Secondary RAN node:** A Secondary node as defined in TS 37.340 [31]. + +**Secondary RAT:** RAT of the secondary RAN node. + +**SNPN-enabled UE:** A UE configured to use stand-alone Non-Public Networks. + +**SNPN access mode:** A UE operating in SNPN access mode only selects stand-alone Non-Public Networks over Uu, Yt, NWu. + +NOTE 5: If there are multiple instances of Uu/Yt/NWu, whether the UE is in SNPN access mode is determined for each instance independently. NWu can be either direct access via untrusted non-3GPP access or access via underlay network (see Annex D, clause D.3). + +**Service based interface:** It represents how a set of services is provided/exposed by a given NF. + +**Service Continuity:** The uninterrupted user experience of a service, including the cases where the IP address and/or anchoring point change. + +**Service Data Flow Filter:** A set of packet flow header parameter values/ranges used to identify one or more of the (IP or Ethernet) packet flows constituting a Service Data Flow. + +**Service Data Flow Template:** The set of Service Data Flow filters in a policy rule or an application identifier in a policy rule referring to an application detection filter, required for defining a Service Data Flow. + +**Session Continuity:** The continuity of a PDU Session. For PDU Session of IPv4 or IPv6 or IPv4v6 type "session continuity" implies that the IP address is preserved for the lifetime of the PDU Session. + +**SMF Service Area:** The collection of UPF Service Areas of all UPFs which can be controlled by one SMF. + +**SNPN ID:** PLMN ID and NID identifying an SNPN. + +**Stand-alone Non-Public Network:** A non-public network not relying on network functions provided by a PLMN + +**Subscribed S-NSSAI:** S-NSSAI based on subscriber information, which a UE is subscribed to use in a PLMN + +**Subscription Owner Standalone Non-Public Network:** A Standalone Non-Public Network owning the subscription of a UE and providing subscription data to the UE via a Provisioning Server during the onboarding procedure. + +**Survival Time:** The time that an application consuming a communication service may continue without an anticipated message. + +NOTE 6: Taken from clause 3.1 of TS 22.261 [2]. + +**Target NSSAI:** NSSAI provided by the Serving PLMN to the NG-RAN to cause the NG-RAN to attempt to steer the UE to a cell supporting the Network Slices identified by the S-NSSAIs in this NSSAI. See clause 5.3.4.3.3 for more details. + +**Time Sensitive Communication (TSC):** A communication service that supports deterministic communication (i.e. which ensures a maximum delay) and/or isochronous communication with high reliability and availability. It is about providing packet transport with QoS characteristics such as bounds on latency, loss, and reliability, where end systems and relay/transmit nodes may or may not be strictly synchronized. + +**TSN working domain:** Synchronization domain for a localized set of devices collaborating on a specific task or work function in a TSN network, corresponding to a gPTP domain defined in IEEE 802.1AS [104]. + +**UDM Group ID:** This refers to one or more UDM instances managing a specific set of SUPIs. An UDM Group consists of one or multiple UDM Sets. + +**UDR Group ID:** This refers to one or more UDR instances managing a specific set of SUPIs. An UDR Group consists of one or multiple UDR Sets. + +**UE-DS-TT Residence Time:** The time taken within the UE and DS-TT to forward a packet, i.e. between the ingress of the UE and the DS-TT port in the DL direction, or between the DS-TT port and the egress of the UE in the UL direction. UE-DS-TT Residence Time is provided at the time of PDU Session Establishment by the UE to the network. + +NOTE 7: UE-DS-TT Residence Time is the same for uplink and downlink traffic and applies to all QoS Flows. + +**UPF Service Area:** An area consisting of one or more TA(s) within which PDU Session associated with the UPF can be served by (R)AN nodes via a N3 interface between the (R)AN and the UPF without need to add a new UPF in between or to remove/re-allocate the UPF. + +**Uplink Classifier:** UPF functionality that aims at diverting Uplink traffic, based on filter rules provided by SMF, towards Data Network. + +**WB-E-UTRA:** In the RAN, WB-E-UTRA is the part of E-UTRA that excludes NB-IoT. In the Core Network, WB-E-UTRA also excludes LTE-M. + +**Wireline 5G Access Network:** The Wireline 5G Access Network (W-5GAN) is a wireline AN that connects to a 5GC via N2 and N3 reference points. The W-5GAN can be either a W-5GBAN or W-5GCAN. + +**Wireline 5G Cable Access Network:** The Wireline 5G Cable Access Network (W-5GCAN) is the Access Network defined in CableLabs. + +**Wireline BBF Access Network:** The Wireline 5G BBF Access Network (W-5GBAN) is the Access Network defined in BBF. + +**Wireline Access Gateway Function (W-AGF):** The Wireline Access Gateway Function (W-AGF) is a Network function in W-5GAN that provides connectivity to the 5G Core to 5G-RG and FN-RG. + +NOTE 8: If one AUSF/PCF/UDR/UDM group consists of multiple AUSF/PCF/UDR/UDM Sets, AUSF/PCF/UDR/UDM instance from different Set may be selected to serve the same UE. The temporary data which is not shared across different Sets may be lost, e.g. the event subscriptions stored at one UDM instance are lost if another UDM instance from different Set is selected and no data shared across the UDM Sets. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-----------|-----------------------------------------------| +| 5GC | 5G Core Network | +| 5G DDNMF | 5G Direct Discovery Name Management Function | +| 5G LAN | 5G Local Area Network | +| 5GS | 5G System | +| 5G-AN | 5G Access Network | +| 5G-AN PDB | 5G Access Network Packet Delay Budget | +| 5G-EIR | 5G-Equipment Identity Register | +| 5G-GUTI | 5G Globally Unique Temporary Identifier | +| 5G-BRG | 5G Broadband Residential Gateway | +| 5G-CRG | 5G Cable Residential Gateway | +| 5G GM | 5G Grand Master | +| 5G NSWO | 5G Non-Seamless WLAN offload | +| 5G-RG | 5G Residential Gateway | +| 5G-S-TMSI | 5G S-Temporary Mobile Subscription Identifier | +| 5G VN | 5G Virtual Network | +| 5QI | 5G QoS Identifier | + +| | | +|----------|----------------------------------------------------| +| ADRF | Analytics Data Repository Function | +| AF | Application Function | +| AI/ML | Artificial Intelligence/Machine Learning | +| AKMA | Authentication and Key Management for Applications | +| AnLF | Analytics Logical Function | +| AMF | Access and Mobility Management Function | +| AoI | Area of Interest | +| AS | Access Stratum | +| ATSSS | Access Traffic Steering, Switching, Splitting | +| ATSSS-LL | ATSSS Low-Layer | +| AUSF | Authentication Server Function | +| BMCA | Best Master Clock Algorithm | +| BSF | Binding Support Function | +| CAG | Closed Access Group | +| CAPIF | Common API Framework for 3GPP northbound APIs | +| CH | Credentials Holder | +| CHF | Charging Function | +| CN PDB | Core Network Packet Delay Budget | +| CP | Control Plane | +| CQRCI | Clock Quality Reporting Control Information | +| DAPS | Dual Active Protocol Stacks | +| DCCF | Data Collection Coordination Function | +| DCS | Default Credentials Server | +| DetNet | Deterministic Networking | +| DL | Downlink | +| DN | Data Network | +| DNAI | DN Access Identifier | +| DNN | Data Network Name | +| DRX | Discontinuous Reception | +| DS-TT | Device-side TSN translator | +| EAC | Early Admission Control | +| ePDG | evolved Packet Data Gateway | +| EBI | EPS Bearer Identity | +| EUI | Extended Unique Identifier | +| FAR | Forwarding Action Rule | +| FL | Federated Learning | +| FN-BRG | Fixed Network Broadband RG | +| FN-CRG | Fixed Network Cable RG | +| FN-RG | Fixed Network RG | +| FQDN | Fully Qualified Domain Name | +| GBA | Generic Bootstrapping Architecture | +| GEO | Geostationary Orbit | +| GFBR | Guaranteed Flow Bit Rate | +| GIN | Group ID for Network Selection | +| GMLC | Gateway Mobile Location Centre | +| GPSI | Generic Public Subscription Identifier | +| GUAMI | Globally Unique AMF Identifier | +| HMTC | High-Performance Machine-Type Communications | +| HR | Home Routed (roaming) | +| IAB | Integrated access and backhaul | +| IMEI/TAC | IMEI Type Allocation Code | +| IPUPS | Inter PLMN UP Security | +| I-SMF | Intermediate SMF | +| I-UPF | Intermediate UPF | +| LADN | Local Area Data Network | +| LBO | Local Break Out (roaming) | +| LEO | Low Earth Orbit | +| LMF | Location Management Function | +| LoA | Level of Automation | +| LPP | LTE Positioning Protocol | +| LRF | Location Retrieval Function | +| L4S | Low Latency, Low Loss and Scalable Throughput | + +| | | +|---------|---------------------------------------------------------------------------| +| MBS | Multicast/Broadcast Service | +| MBSF | Multicast/Broadcast Service Function | +| MBSR | Mobile Base Station Relay | +| MBSTF | Multicast/Broadcast Service Transport Function | +| MB-SMF | Multicast/Broadcast Session Management Function | +| MB-UPF | Multicast/Broadcast User Plane Function | +| MEO | Medium Earth Orbit | +| MFAF | Messaging Framework Adaptor Function | +| MCX | Mission Critical Service | +| MDBV | Maximum Data Burst Volume | +| MFBR | Maximum Flow Bit Rate | +| MICO | Mobile Initiated Connection Only | +| MINT | Minimization of Service Interruption | +| ML | Machine Learning | +| MPQUIC | Multi-Path QUIC | +| MPS | Multimedia Priority Service | +| MPTCP | Multi-Path TCP Protocol | +| MTLF | Model Training Logical Function | +| N3IWF | Non-3GPP InterWorking Function | +| N3QAI | Non-3GPP QoS Assistance Information | +| N5CW | Non-5G-Capable over WLAN | +| NAI | Network Access Identifier | +| NEF | Network Exposure Function | +| NF | Network Function | +| NGAP | Next Generation Application Protocol | +| NID | Network identifier | +| NPN | Non-Public Network | +| NR | New Radio | +| NRF | Network Repository Function | +| NS-AoS | Network Slice Area of Service | +| NSAC | Network Slice Admission Control | +| NSACF | Network Slice Admission Control Function | +| NSAG | Network Slice AS Group | +| NSI ID | Network Slice Instance Identifier | +| NSSAA | Network Slice-Specific Authentication and Authorization | +| NSSAAF | Network Slice-specific and SNPN Authentication and Authorization Function | +| NSSAI | Network Slice Selection Assistance Information | +| NSSF | Network Slice Selection Function | +| NSSP | Network Slice Selection Policy | +| NSSRG | Network Slice Simultaneous Registration Group | +| NSWO | Non-Seamless WLAN offload | +| NSWOF | Non-Seamless WLAN offload Function | +| NW-TT | Network-side TSN translator | +| NWDAF | Network Data Analytics Function | +| ONN | Onboarding Network | +| ON-SNPN | Onboarding Standalone Non-Public Network | +| PCF | Policy Control Function | +| PDB | Packet Delay Budget | +| PDR | Packet Detection Rule | +| PDU | Protocol Data Unit | +| PDV | Packet Delay Variation | +| PEGC | PIN Element with Gateway Capability | +| PEI | Permanent Equipment Identifier | +| PEMC | PIN Element with Management Capability | +| PER | Packet Error Rate | +| PFD | Packet Flow Description | +| PIN | Personal IoT Network | +| PINE | PIN Element | +| PLR | Packet Loss Rate | +| PNI-NPN | Public Network Integrated Non-Public Network | +| PPD | Paging Policy Differentiation | +| PPF | Paging Proceed Flag | + +| | | +|---------|----------------------------------------------------------------| +| PPI | Paging Policy Indicator | +| PSA | PDU Session Anchor | +| PSDB | PDU Set Delay Budget | +| PSER | PDU Set Error Rate | +| PSIHI | PDU Set Integrated Handling Information | +| PTP | Precision Time Protocol | +| PVS | Provisioning Server | +| QFI | QoS Flow Identifier | +| QoE | Quality of Experience | +| RACS | Radio Capabilities Signalling optimisation | +| (R)AN | (Radio) Access Network | +| RG | Residential Gateway | +| RIM | Remote Interference Management | +| RQA | Reflective QoS Attribute | +| RQI | Reflective QoS Indication | +| RSN | Redundancy Sequence Number | +| RTT | Round Trip Time | +| SA NR | Standalone New Radio | +| SBA | Service Based Architecture | +| SBI | Service Based Interface | +| SCP | Service Communication Proxy | +| SD | Slice Differentiator | +| SEAF | Security Anchor Functionality | +| SEPP | Security Edge Protection Proxy | +| SF | Service Function | +| SFC | Service Function Chain | +| SMF | Session Management Function | +| SMSF | Short Message Service Function | +| SN | Sequence Number | +| SNPN | Stand-alone Non-Public Network | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| SO-SNPN | Subscription Owner Standalone Non-Public Network | +| SSC | Session and Service Continuity | +| SSCMSP | Session and Service Continuity Mode Selection Policy | +| SST | Slice/Service Type | +| SUCI | Subscription Concealed Identifier | +| SUPI | Subscription Permanent Identifier | +| SV | Software Version | +| TA | Tracking Area | +| TAI | Tracking Area Identity | +| TNAN | Trusted Non-3GPP Access Network | +| TNAP | Trusted Non-3GPP Access Point | +| TNGF | Trusted Non-3GPP Gateway Function | +| TNL | Transport Network Layer | +| TNLA | Transport Network Layer Association | +| TSC | Time Sensitive Communication | +| TSCAI | TSC Assistance Information | +| TSCTSF | Time Sensitive Communication and Time Synchronization Function | +| TSN | Time Sensitive Networking | +| TSN GM | TSN Grand Master | +| TSP | Traffic Steering Policy | +| TSS | Timing Synchronization Status | +| TT | TSN Translator | +| TWIF | Trusted WLAN Interworking Function | +| UAS NF | Uncrewed Aerial System Network Function | +| UCMF | UE radio Capability Management Function | +| UDM | Unified Data Management | +| UDR | Unified Data Repository | +| UDSF | Unstructured Data Storage Function | +| UL | Uplink | +| UL CL | Uplink Classifier | +| UPF | User Plane Function | + +| | | +|----------|-------------------------------------------| +| URLLC | Ultra Reliable Low Latency Communication | +| URRP-AMF | UE Reachability Request Parameter for AMF | +| URSP | UE Route Selection Policy | +| VID | VLAN Identifier | +| VLAN | Virtual Local Area Network | +| W-5GAN | Wireline 5G Access Network | +| W-5GBAN | Wireline BBF Access Network | +| W-5GCAN | Wireline 5G Cable Access Network | +| W-AGF | Wireline Access Gateway Function | + +# --- 4 Architecture model and concepts + +## 4.1 General concepts + +The 5G System architecture is defined to support data connectivity and services enabling deployments to use techniques such as e.g. Network Function Virtualization and Software Defined Networking. The 5G System architecture shall leverage service-based interactions between Control Plane (CP) Network Functions where identified. Some key principles and concept are to: + +- Separate the User Plane (UP) functions from the Control Plane (CP) functions, allowing independent scalability, evolution and flexible deployments e.g. centralized location or distributed (remote) location. +- Modularize the function design, e.g. to enable flexible and efficient network slicing. +- Wherever applicable, define procedures (i.e. the set of interactions between network functions) as services, so that their re-use is possible. +- Enable each Network Function and its Network Function Services to interact with other NF and its Network Function Services directly or indirectly via a Service Communication Proxy if required. The architecture does not preclude the use of another intermediate function to help route Control Plane messages (e.g. like a DRA). +- Minimize dependencies between the Access Network (AN) and the Core Network (CN). The architecture is defined with a converged core network with a common AN - CN interface which integrates different Access Types e.g. 3GPP access and non-3GPP access. +- Support a unified authentication framework. +- Support "stateless" NFs, where the "compute" resource is decoupled from the "storage" resource. +- Support capability exposure. +- Support concurrent access to local and centralized services. To support low latency services and local access to data networks, UP functions can be deployed close to the Access Network. +- Support roaming with both Home routed traffic as well as Local breakout traffic in the visited PLMN. + +## 4.2 Architecture reference model + +### 4.2.1 General + +This specification describes the architecture for the 5G System. The 5G architecture is defined as service-based and the interaction between network functions is represented in two ways. + +- A service-based representation, where network functions (e.g. AMF) within the Control Plane enables other authorized network functions to access their services. This representation also includes point-to-point reference points where necessary. +- A reference point representation, shows the interaction exist between the NF services in the network functions described by point-to-point reference point (e.g. N11) between any two network functions (e.g. AMF and SMF). + +Service-based interfaces are listed in clause 4.2.6. Reference points are listed in clause 4.2.7. + +Network functions within the 5GC Control Plane shall only use service-based interfaces for their interactions. + +NOTE 1: The interactions between NF services within one NF are not specified in this Release of the specification. + +NFs and NF services can communicate directly, referred to as Direct Communication, or indirectly via the SCP, referred to as Indirect Communication. For more information on communication options, see Annex E and clauses under 6.3.1 and 7.1.2. + +In addition to the architecture descriptions in clause 4, the following areas are further described in other specifications: + +- NG-RAN architecture is described in TS 38.300 [27] and TS 38.401 [42]. +- Security architecture is described in TS 33.501 [29] and TS 33.535 [124]. +- Charging architecture is described in TS 32.240 [41]. +- 5G Media streaming architecture is described in TS 26.501 [135]. + +NOTE 3: The NFs listed in clause 4.2.2 are described in the following clauses or in the specifications above. + +### 4.2.2 Network Functions and entities + +The 5G System architecture consists of the following network functions (NF): + +- Authentication Server Function (AUSF). +- Access and Mobility Management Function (AMF). +- Data Network (DN), e.g. operator services, Internet access or 3rd party services. +- Unstructured Data Storage Function (UDSF). +- Network Exposure Function (NEF). +- Network Repository Function (NRF). +- Network Slice Admission Control Function (NSACF). +- Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF). +- Network Slice Selection Function (NSSF). +- Policy Control Function (PCF). +- Session Management Function (SMF). +- Unified Data Management (UDM). +- Unified Data Repository (UDR). +- User Plane Function (UPF). +- UE radio Capability Management Function (UCMF). +- Application Function (AF). +- User Equipment (UE). +- (Radio) Access Network ((R)AN). +- 5G-Equipment Identity Register (5G-EIR). +- Network Data Analytics Function (NWDAF). +- Charging Function (CHF). + +- Time Sensitive Networking AF (TSN AF). +- Time Sensitive Communication and Time Synchronization Function (TSCTSF). +- Data Collection Coordination Function (DCCF). +- Analytics Data Repository Function (ADRF). +- Messaging Framework Adaptor Function (MFAF). +- Non-Seamless WLAN Offload Function (NSWOF). + +NOTE: The functionalities provided by DCCF and/or ADRF can also be hosted by an NWDAF. + +- Edge Application Server Discovery Function (EASDF). + +The 5G System architecture also comprises the following network entities: + +- Service Communication Proxy (SCP). +- Security Edge Protection Proxy (SEPP). + +The functional descriptions of these Network Functions and entities are specified in clause 6. + +- Non-3GPP InterWorking Function (N3IWF). +- Trusted Non-3GPP Gateway Function (TNGF). +- Wireline Access Gateway Function (W-AGF). +- Trusted WLAN Interworking Function (TWIF). + +### 4.2.3 Non-roaming reference architecture + +Figure 4.2.3-1 depicts the non-roaming reference architecture. Service-based interfaces are used within the Control Plane. + +![Diagram of Non-Roaming 5G System Architecture showing various network functions and their interfaces.](aa9441a5971655a79987d70fc551b26a_img.jpg) + +The diagram illustrates the Non-Roaming 5G System Architecture. At the top, a horizontal line represents the Service Based Interface (SBI). Above this line are several Network Functions (NFs) connected via their respective service-based interfaces: NSSF (Nnssf), NEF (Nnef), NRF (Nnrf), PCF (Npcf), UDM (Nudm), AF (Naf), and EASDF (Neasdf). Below the SBI line, other NFs are connected: NSSAAF (NnssAAF), AUSF (Nausf), AMF (Namf), SMF (Nsmf), SCP (Nscp), and NSACF (NnsacF). The User Equipment (UE) is connected to the (R)AN via the N1 interface. The (R)AN is connected to the AMF via the N2 interface and to the UPF via the N3 interface. The AMF is connected to the SMF via the N4 interface. The UPF is connected to the DN (Data Network) via the N6 interface and has a service-based interface N9. The (R)AN is also connected to the UPF via the N3 interface. + +Diagram of Non-Roaming 5G System Architecture showing various network functions and their interfaces. + +Figure 4.2.3-1: Non-Roaming 5G System Architecture + +NOTE: If an SCP is deployed it can be used for indirect communication between NFs and NF services as described in Annex E. SCP does not expose services itself. + +Figure 4.2.3-2 depicts the 5G System architecture in the non-roaming case, using the reference point representation showing how various network functions interact with each other. + +![Figure 4.2.3-2: Non-Roaming 5G System Architecture in reference point representation. This diagram shows the interconnections between various 5G Network Functions (NFs). At the top, NSSAAF is connected to UDM via N59. NSSAF and AUSF are connected to AMF via N22 and N12 respectively. AUSF is also connected to UDM via N13. UDM is connected to NSACF via N80 and to AMF via N8. AMF is connected to SMF via N11 and to UPF via N4. SMF is connected to PCF via N7 and to DN via N6. PCF is connected to AF via N5. UE is connected to (R)AN via N1. (R)AN is connected to AMF via N2 and to UPF via N3. UPF is connected to DN via N6 and has interfaces N9 and N15. AMF is also connected to UDM via N10 and N81.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +``` + +graph TD + UE[UE] -- N1 --> AMF[AMF] + (R)AN[(R)AN] -- N2 --> AMF + (R)AN -- N3 --> UPF[UPF] + AMF -- N4 --> UPF + UPF -- N6 --> DN((DN)) + AMF -- N11 --> SMF[SMF] + SMF -- N7 --> PCF[PCF] + PCF -- N5 --> AF[AF] + AMF -- N8 --> UDM[UDM] + UDM -- N10 --> AMF + UDM -- N80 --> NSACF[NSACF] + UDM -- N13 --> AUSF[AUSF] + AUSF -- N12 --> AMF + NSSAF[NSSAF] -- N22 --> AMF + NSSAAF[NSSAAF] -- N59 --> UDM + AMF -- N14 --> UPF + UPF -- N9 --> UPF + AMF -- N15 --> UPF + SMF -- N15 --> UPF + +``` + +Figure 4.2.3-2: Non-Roaming 5G System Architecture in reference point representation. This diagram shows the interconnections between various 5G Network Functions (NFs). At the top, NSSAAF is connected to UDM via N59. NSSAF and AUSF are connected to AMF via N22 and N12 respectively. AUSF is also connected to UDM via N13. UDM is connected to NSACF via N80 and to AMF via N8. AMF is connected to SMF via N11 and to UPF via N4. SMF is connected to PCF via N7 and to DN via N6. PCF is connected to AF via N5. UE is connected to (R)AN via N1. (R)AN is connected to AMF via N2 and to UPF via N3. UPF is connected to DN via N6 and has interfaces N9 and N15. AMF is also connected to UDM via N10 and N81. + +**Figure 4.2.3-2: Non-Roaming 5G System Architecture in reference point representation** + +NOTE 1: N9, N14 are not shown in all other figures however they may also be applicable for other scenarios. + +NOTE 2: For the sake of clarity of the point-to-point diagrams, the UDSF, NEF and NRF have not been depicted. However, all depicted Network Functions can interact with the UDSF, UDR, NEF and NRF as necessary. + +NOTE 3: The UDM uses subscription data and authentication data and the PCF uses policy data that may be stored in UDR (refer to clause 4.2.5). + +NOTE 4: For clarity, the UDR and its connections with other NFs, e.g. PCF, are not depicted in the point-to-point and service-based architecture diagrams. For more information on data storage architectures refer to clause 4.2.5. + +NOTE 5: For clarity, the NWDAF(s), DCCF, MFAF and ADRF and their connections with other NFs, are not depicted in the point-to-point and service-based architecture diagrams. For more information on network data analytics architecture refer to TS 23.288 [86]. + +NOTE 6: For clarity, the 5G DDNMF and its connections with other NFs, e.g. UDM, PCF are not depicted in the point-to-point and service-based architecture diagrams. For more information on ProSe architecture refer to TS 23.304 [128]. + +NOTE 7: For clarity, the TSCTSF and its connections with other NFs, e.g. PCF, NEF, UDR are not depicted in the point-to-point and service-based architecture diagrams. For more information on TSC architecture refer to clause 4.4.8. + +NOTE 8: For exposure of the QoS monitoring information as specified in clause 5.8.2.18, exposure of data collected for analytics as specified in clause 5.2.26.2 of TS 23.502 [3], and exposure of the TSC management information as specified in clause 5.8.5.14, direct interaction between UPF and NFs can be supported via the Nupf interface (see clause 4.2.16). + +NOTE 9: For clarity, the EASDF and its connections with SMF is not depicted in the point-to-point and service-based architecture diagrams. For more information on edge computing architecture refer to TS 23.548 [130]. + +Figure 4.2.3-3 depicts the non-roaming architecture for UEs concurrently accessing two (e.g. local and central) data networks using multiple PDU Sessions, using the reference point representation. This figure shows the architecture for multiple PDU Sessions where two SMFs are selected for the two different PDU Sessions. However, each SMF may also have the capability to control both a local and a central UPF within a PDU Session. + +![Diagram of 5G system architecture for multiple PDU sessions.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +This diagram illustrates the 5G system architecture for multiple PDU sessions. At the top, the Network Slice Selection Function (NSSF) connects to the Network Slice Selection Assistance Information Function (NSSAAF) via the N59 interface. The AUSF connects to the NSSF via the N22 interface and to the UDM via the N13 interface. The UDM connects to the AMF via the N8 interface and to the NSACF via the N10 interface. The AMF connects to the UE via the (R)AN through the N1 and N2 interfaces. The AMF also connects to the NSACF via the N12 interface, to the UDM via the N15 interface, and to two separate SMFs via the N11 interface. The first SMF connects to the PCF via the N7 interface and to the UPF via the N4 interface. The PCF connects to the AF via the N5 interface. The second SMF connects to the UPF via the N4 interface and to the DN via the N6 interface. The UPF connects to the DN via the N6 and N9 interfaces. The (R)AN also connects to the UPF via the N3 and N4 interfaces. The UPF connects to the DN via the N6 and N9 interfaces. + +Diagram of 5G system architecture for multiple PDU sessions. + +**Figure 4.2.3-3: Applying Non-Roaming 5G System Architecture for multiple PDU Session in reference point representation** + +Figure 4.2.3-4 depicts the non-roaming architecture in the case of concurrent access to two (e.g. local and central) data networks is provided within a single PDU Session, using the reference point representation. + +![Diagram of 5G system architecture for concurrent access to two data networks within a single PDU session.](e636d7ccca0ad14c6b95201404324823_img.jpg) + +This diagram illustrates the 5G system architecture for concurrent access to two data networks within a single PDU session. The architecture is similar to Figure 4.2.3-3 but with a single PDU session. The UE connects to the (R)AN via the N1 and N2 interfaces. The (R)AN connects to the AMF via the N3 and N4 interfaces. The AMF connects to the UDM via the N15 interface and to the SMF via the N11 interface. The SMF connects to the PCF via the N7 interface and to two UPFs via the N4 interface. The PCF connects to the AF via the N5 interface. The first UPF connects to the DN via the N6 and N9 interfaces. The second UPF connects to the DN via the N6 and N9 interfaces. The UDM connects to the NSACF via the N10 interface. The NSACF connects to the AMF via the N12 interface. The AUSF connects to the NSSF via the N22 interface and to the UDM via the N13 interface. The NSSF connects to the NSSAAF via the N59 interface. + +Diagram of 5G system architecture for concurrent access to two data networks within a single PDU session. + +**Figure 4.2.3-4: Applying Non-Roaming 5G System Architecture for concurrent access to two (e.g. local and central) data networks (single PDU Session option) in reference point representation** + +Figure 4.2.3-5 depicts the non-roaming architecture for Network Exposure Function, using reference point representation. + +![Diagram of Non-Roaming Architecture for Network Exposure Function in reference point representation](a3472689858b068ef469213682965325_img.jpg) + +The diagram illustrates the non-roaming architecture for the Network Exposure Function (NEF). At the top, three Application Functions (AF) are shown. The left AF connects to the first NEF via an N33 interface. The middle AF connects to both the first and second NEFs via N33 interfaces. The right AF connects to the second NEF. A vertical double-headed arrow on the left is labeled 'TRUST DOMAIN', indicating the scope of the first NEF. The first NEF contains API 1 and API 2, and the second NEF contains API 3, an ellipsis, and API n. Below the first NEF, NF1 and NF2 are connected via '3GPP Interface (See Note 2)'. Below the second NEF, NFn is connected via a '3GPP Interface (See Note 2)'. An ellipsis between NF2 and NFn indicates additional network functions. A horizontal dotted line separates the AFs from the NEFs. + +Diagram of Non-Roaming Architecture for Network Exposure Function in reference point representation + +**Figure 4.2.3-5: Non-Roaming Architecture for Network Exposure Function in reference point representation** + +NOTE 1: In Figure 4.2.3-5, Trust domain for NEF is same as Trust domain for SCEF as defined in TS 23.682 [36]. + +NOTE 2: In Figure 4.2.3-5, 3GPP Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity. + +### 4.2.4 Roaming reference architectures + +Figure 4.2.4-1 depicts the 5G System roaming architecture with local breakout with service-based interfaces within the Control Plane. + +![Figure 4.2.4-1: Roaming 5G System architecture- local breakout scenario in service-based interface representation. The diagram shows the architecture for a local breakout (LBO) scenario in 5G roaming. It is divided into two main parts by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. In the VPLMN, the UE is connected to the (R)AN, which is connected to the AMF (N1, N2). The AMF is connected to the SMF (N4) and the NSACF (Nsmf). The SMF is connected to the UPF (N3, N9), which is connected to the DN (N6). The AMF is also connected to the vSEPP (N32). The vSEPP is connected to the hSEPP. The hSEPP is connected to the AUSF (Nausf). The AUSF is connected to the UDM (Nudm). The UDM is connected to the NRF (Nnrf). The NRF is connected to the NSSAAF (Nnssaaf). The NSSAAF is connected to the NSACF (Nnsacf). The NSACF is connected to the NEF (Nnef). The NEF is connected to the PCF (Npcf). The PCF is connected to the AF (Naf). The AF is connected to the NSSSF (Nnssf). The NSSSF is connected to the AMF (Namf). In the HPLMN, the hSEPP is connected to the AUSF (Nausf). The AUSF is connected to the UDM (Nudm). The UDM is connected to the NRF (Nnrf). The NRF is connected to the NSSAAF (Nnssaaf). The NSSAAF is connected to the NSACF (Nnsacf). The NSACF is connected to the NEF (Nnef). The NEF is connected to the PCF (Npcf). The PCF is connected to the AF (Naf). The AF is connected to the NSSSF (Nnssf). The NSSSF is connected to the AMF (Namf).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 4.2.4-1: Roaming 5G System architecture- local breakout scenario in service-based interface representation. The diagram shows the architecture for a local breakout (LBO) scenario in 5G roaming. It is divided into two main parts by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. In the VPLMN, the UE is connected to the (R)AN, which is connected to the AMF (N1, N2). The AMF is connected to the SMF (N4) and the NSACF (Nsmf). The SMF is connected to the UPF (N3, N9), which is connected to the DN (N6). The AMF is also connected to the vSEPP (N32). The vSEPP is connected to the hSEPP. The hSEPP is connected to the AUSF (Nausf). The AUSF is connected to the UDM (Nudm). The UDM is connected to the NRF (Nnrf). The NRF is connected to the NSSAAF (Nnssaaf). The NSSAAF is connected to the NSACF (Nnsacf). The NSACF is connected to the NEF (Nnef). The NEF is connected to the PCF (Npcf). The PCF is connected to the AF (Naf). The AF is connected to the NSSSF (Nnssf). The NSSSF is connected to the AMF (Namf). In the HPLMN, the hSEPP is connected to the AUSF (Nausf). The AUSF is connected to the UDM (Nudm). The UDM is connected to the NRF (Nnrf). The NRF is connected to the NSSAAF (Nnssaaf). The NSSAAF is connected to the NSACF (Nnsacf). The NSACF is connected to the NEF (Nnef). The NEF is connected to the PCF (Npcf). The PCF is connected to the AF (Naf). The AF is connected to the NSSSF (Nnssf). The NSSSF is connected to the AMF (Namf). + +**Figure 4.2.4-1: Roaming 5G System architecture- local breakout scenario in service-based interface representation** + +NOTE 1: In the LBO architecture, the PCF in the VPLMN may interact with the AF in order to generate PCC Rules for services delivered via the VPLMN, the PCF in the VPLMN uses locally configured policies according to the roaming agreement with the HPLMN operator as input for PCC Rule generation, the PCF in VPLMN has no access to subscriber policy information from the HPLMN. + +NOTE 2: An SCP can be used for indirect communication between NFs and NF services within the VPLMN, within the HPLMN, or in within both VPLMN and HPLMN. For simplicity, the SCP is not shown in the roaming architecture. + +NOTE 3: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the service-based architecture diagram. For more information on network data analytics architecture refer to TS 23.288 [86]. + +NOTE 4: Depending on the architecture deployed, the Primary or Centralized NSACF at the VPLMN can fetch the maximum number of registered UEs or the maximum number of LBO PDU sessions to be enforced from the HPLMN Primary or Centralized NSACF as described in clause 5.15.11.3.1. + +**Figure 4.2.4-2: Void** + +Figure 4.2.4-3 depicts the 5G System roaming architecture in the case of home routed scenario with service-based interfaces within the Control Plane. + +![Figure 4.2.4-3: Roaming 5G System architecture - home routed scenario in service-based interface representation. The diagram shows the VPLMN (Visited PLMN) on the left and the HPLMN (Home PLMN) on the right, separated by a dashed line. In the VPLMN, a UE connects to an (R)AN, which connects to an AMF via N1 and N2 interfaces. The AMF connects to an SMF via N4 and to an NSACF via N12. The SMF connects to a UPF via N3 and N4 interfaces. The UPF connects to the DN via N6 and N9 interfaces. The AMF also connects to the vSEPP via N32. The vSEPP connects to the hSEPP via N32. In the HPLMN, the hSEPP connects to the UDM via Nudm, to the NRF via Nnrf, to the NEF via Nnef, to the NSSSF via Nnssf, and to the NSACF via Nnsacf. The UDM connects to the AUSF via Nausf, which connects to the SMF via Nsmf. The SMF connects to the UPF via N4 and N9 interfaces. The UPF connects to the DN via N6 and N9 interfaces. The AUSF also connects to the PCF via Npcf and to the NSSAAF via NnssAAF. The PCF connects to the AF via Naf. The NSSAAF connects to the NSSSF via NnssAAF.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 4.2.4-3: Roaming 5G System architecture - home routed scenario in service-based interface representation. The diagram shows the VPLMN (Visited PLMN) on the left and the HPLMN (Home PLMN) on the right, separated by a dashed line. In the VPLMN, a UE connects to an (R)AN, which connects to an AMF via N1 and N2 interfaces. The AMF connects to an SMF via N4 and to an NSACF via N12. The SMF connects to a UPF via N3 and N4 interfaces. The UPF connects to the DN via N6 and N9 interfaces. The AMF also connects to the vSEPP via N32. The vSEPP connects to the hSEPP via N32. In the HPLMN, the hSEPP connects to the UDM via Nudm, to the NRF via Nnrf, to the NEF via Nnef, to the NSSSF via Nnssf, and to the NSACF via Nnsacf. The UDM connects to the AUSF via Nausf, which connects to the SMF via Nsmf. The SMF connects to the UPF via N4 and N9 interfaces. The UPF connects to the DN via N6 and N9 interfaces. The AUSF also connects to the PCF via Npcf and to the NSSAAF via NnssAAF. The PCF connects to the AF via Naf. The NSSAAF connects to the NSSSF via NnssAAF. + +**Figure 4.2.4-3: Roaming 5G System architecture - home routed scenario in service-based interface representation** + +NOTE 4: An SCP can be used for indirect communication between NFs and NF services within the VPLMN, within the HPLMN, or in within both VPLMN and HPLMN. For simplicity, the SCP is not shown in the roaming architecture. + +NOTE 5: UPFs in the home routed scenario can be used also to support the IPUPS functionality (see clause 5.8.2.14). + +NOTE 6: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the service-based architecture diagram. For more information on network data analytics architecture refer to TS 23.288 [86]. + +Figure 4.2.4-4 depicts 5G System roaming architecture in the case of local break out scenario using the reference point representation. + +![Figure 4.2.4-4: Roaming 5G System architecture - local breakout scenario in reference point representation. The diagram shows the VPLMN (Visited PLMN) on the left and the HPLMN (Home PLMN) on the right, separated by a dashed line. In the VPLMN, a UE connects to an (R)AN, which connects to an AMF via N1 and N2 interfaces. The AMF connects to an SMF via N11 and to an NSSSF via N22. The SMF connects to a vPCF via N7 and to a UPF via N4 and N15 interfaces. The UPF connects to the DN via N6 and N9 interfaces. The vPCF connects to the hPCF via N24 and to an AF via N5 interfaces. The AMF also connects to the UDM via N10 and N12 interfaces, and to the AUSF via N8 interfaces. In the HPLMN, the hPCF connects to the UDM via N13. The UDM connects to the AUSF via N13. The AUSF connects to the NSSAAF via N59. The NSSAAF connects to the NSSSF via NnssAAF.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +Figure 4.2.4-4: Roaming 5G System architecture - local breakout scenario in reference point representation. The diagram shows the VPLMN (Visited PLMN) on the left and the HPLMN (Home PLMN) on the right, separated by a dashed line. In the VPLMN, a UE connects to an (R)AN, which connects to an AMF via N1 and N2 interfaces. The AMF connects to an SMF via N11 and to an NSSSF via N22. The SMF connects to a vPCF via N7 and to a UPF via N4 and N15 interfaces. The UPF connects to the DN via N6 and N9 interfaces. The vPCF connects to the hPCF via N24 and to an AF via N5 interfaces. The AMF also connects to the UDM via N10 and N12 interfaces, and to the AUSF via N8 interfaces. In the HPLMN, the hPCF connects to the UDM via N13. The UDM connects to the AUSF via N13. The AUSF connects to the NSSAAF via N59. The NSSAAF connects to the NSSSF via NnssAAF. + +**Figure 4.2.4-4: Roaming 5G System architecture - local breakout scenario in reference point representation** + +NOTE 7: The NRF is not depicted in reference point architecture figures. Refer to Figure 4.2.4-7 for details on NRF and NF interfaces. + +NOTE 8: For the sake of clarity, SEPPs are not depicted in the roaming reference point architecture figures. + +NOTE 9: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the reference point architecture figure. For more information on network data analytics architecture refer to TS 23.288 [86]. + +The following figure 4.2.4-6 depicts the 5G System roaming architecture in the case of home routed scenario using the reference point representation. + +![Figure 4.2.4-6: Roaming 5G System architecture - Home routed scenario in reference point representation. The diagram shows the VPLMN on the left and HPLMN on the right, separated by a vertical dashed line. In VPLMN: UE connects to (R)AN (N1), (R)AN connects to AMF (N2) and UPF (N3). AMF connects to V-NSSF (N22), V-PCF (N15), V-SMF (N11). V-SMF connects to V-PCF (N38) and UPF (N4). In HPLMN: NSSAAF, AUSF, UDM, H-NSSF, H-SMF, H-PCF, AF, and UPF are shown. Cross-border connections include N31 (AMF to H-NSSF), N58 (AMF to NSSAAF), N12 (AMF to AUSF), N8 (AMF to UDM), N16 (V-SMF to H-SMF), N24 (V-PCF to H-PCF), and N9 (UPF to UPF). H-SMF connects to UDM (N10), H-PCF (N7), and UPF (N4). H-PCF connects to AF (N5). UPF connects to Data Network (N6).](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Figure 4.2.4-6: Roaming 5G System architecture - Home routed scenario in reference point representation. The diagram shows the VPLMN on the left and HPLMN on the right, separated by a vertical dashed line. In VPLMN: UE connects to (R)AN (N1), (R)AN connects to AMF (N2) and UPF (N3). AMF connects to V-NSSF (N22), V-PCF (N15), V-SMF (N11). V-SMF connects to V-PCF (N38) and UPF (N4). In HPLMN: NSSAAF, AUSF, UDM, H-NSSF, H-SMF, H-PCF, AF, and UPF are shown. Cross-border connections include N31 (AMF to H-NSSF), N58 (AMF to NSSAAF), N12 (AMF to AUSF), N8 (AMF to UDM), N16 (V-SMF to H-SMF), N24 (V-PCF to H-PCF), and N9 (UPF to UPF). H-SMF connects to UDM (N10), H-PCF (N7), and UPF (N4). H-PCF connects to AF (N5). UPF connects to Data Network (N6). + +**Figure 4.2.4-6: Roaming 5G System architecture - Home routed scenario in reference point representation** + +The N38 references point can be between V-SMFs in the same VPLMN, or between V-SMFs in different VPLMNs (to enable inter-PLMN mobility). + +NOTE 10: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the reference point architecture figure. For more information on network data analytics architecture refer to TS 23.288 [86]. + +For the roaming scenarios described above each PLMN implements proxy functionality to secure interconnection and hide topology on the inter-PLMN interfaces. + +![Figure 4.2.4-7: NRF Roaming architecture in reference point representation. The diagram shows three Network Functions (NFs) connected in a line: VPLMN NF, vNRF, and hNRF. The vNRF and hNRF are connected via an N27 interface. A vertical dashed line separates the VPLMN (left) and HPLMN (right) domains.](26d664119ad25250780f554633444e54_img.jpg) + +Figure 4.2.4-7: NRF Roaming architecture in reference point representation. The diagram shows three Network Functions (NFs) connected in a line: VPLMN NF, vNRF, and hNRF. The vNRF and hNRF are connected via an N27 interface. A vertical dashed line separates the VPLMN (left) and HPLMN (right) domains. + +**Figure 4.2.4-7: NRF Roaming architecture in reference point representation** + +NOTE 11: For the sake of clarity, SEPPs on both sides of PLMN borders are not depicted in figure 4.2.4-7. + +**Figure 4.2.4-8: Void** + +Operators can deploy UPFs supporting the Inter PLMN UP Security (IPUPS) functionality at the border of their network to protect their network from invalid inter PLMN N9 traffic in home routed roaming scenarios. The UPFs supporting the IPUPS functionality in VPLMN and HPLMN are controlled by the V-SMF and the H-SMF of that PDU Session respectively. A UPF supporting the IPUPS functionality terminates GTP-U N9 tunnels. The SMF can activate the IPUPS functionality together with other UP functionality in the same UPF, or insert a separate UPF for the IPUPS functionality in the UP path (which e.g. may be dedicated to be used for IPUPS functionality). Figure 4.2.4-9 depicts the home routed roaming architecture where a UPF is inserted in the UP path for the IPUPS functionality. Figure 4.2.4-3 depicts the home routed roaming architecture where the two UPFs perform the IPUPS functionality and other UP functionality for the PDU Session. + +NOTE 12: Operators are not prohibited from deploying the IPUPS functionality as a separate Network Function from the UPF, acting as a transparent proxy which can transparently read N4 and N9 interfaces. However, such deployment option is not specified and needs to take at least into account very long lasting PDU Sessions with infrequent traffic and Inter-PLMN handover. + +The IPUPS functionality is specified in clause 5.8.2.14 and TS 33.501 [29]. + +![Figure 4.2.4-9: Roaming 5G System architecture - home routed roaming scenario in service-based interface representation employing UPF dedicated to IPUPS. The diagram is split into two domains by a vertical dashed line: VPLMN (left) and HPLMN (right). In the VPLMN, a UE is connected to an (R)AN, which is connected to an AMF. The AMF is connected to an SMF and an NSACF. The SMF is connected to a UPF, which is connected to another UPF (IPUPS). The UPF (IPUPS) is connected to the HPLMN via an N9 interface. In the HPLMN, the UPF (IPUPS) is connected to an SMF. The SMF is connected to an AUSF, which is connected to an NSSAAF. The NSSAAF is connected to a UPF, which is connected to a DN. Various service-based interfaces (N1, N2, N3, N4, N5, N6, N7, N8, N9, N10, N11, N12, N13, N14, N15, N16, N17, N18, N19, N20, N21, N22, N23, N24, N25, N26, N27, N28, N29, N30, N31, N32, N33, N34, N35, N36, N37, N38, N39, N40, N41, N42, N43, N44, N45, N46, N47, N48, N49, N50) are shown between the various Network Functions (NFs).](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +Figure 4.2.4-9: Roaming 5G System architecture - home routed roaming scenario in service-based interface representation employing UPF dedicated to IPUPS. The diagram is split into two domains by a vertical dashed line: VPLMN (left) and HPLMN (right). In the VPLMN, a UE is connected to an (R)AN, which is connected to an AMF. The AMF is connected to an SMF and an NSACF. The SMF is connected to a UPF, which is connected to another UPF (IPUPS). The UPF (IPUPS) is connected to the HPLMN via an N9 interface. In the HPLMN, the UPF (IPUPS) is connected to an SMF. The SMF is connected to an AUSF, which is connected to an NSSAAF. The NSSAAF is connected to a UPF, which is connected to a DN. Various service-based interfaces (N1, N2, N3, N4, N5, N6, N7, N8, N9, N10, N11, N12, N13, N14, N15, N16, N17, N18, N19, N20, N21, N22, N23, N24, N25, N26, N27, N28, N29, N30, N31, N32, N33, N34, N35, N36, N37, N38, N39, N40, N41, N42, N43, N44, N45, N46, N47, N48, N49, N50) are shown between the various Network Functions (NFs). + +**Figure 4.2.4-9: Roaming 5G System architecture - home routed roaming scenario in service-based interface representation employing UPF dedicated to IPUPS** + +### 4.2.5 Data Storage architectures + +As depicted in Figure 4.2.5-1, the 5G System architecture allows any NF to create/read/update/delete its unstructured data in a UDSF (e.g. UE contexts). If such an NF is using UDSF is part of an NF set, then any of the NF instance within this NF set may read/update/delete the unstructured data that was created by this NF. The UDSF belongs to the same PLMN where the network function is located. CP NFs/NF Sets may share a UDSF for storing their respective unstructured data or may each have their own UDSF (e.g. a UDSF may be located close to the respective NF). + +NOTE 1: Structured data in this specification refers to data for which the structure is defined in 3GPP specifications. Unstructured data refers to data for which the structure is not defined in 3GPP specifications. + +NOTE 2: If a NF Set has its own UDSF, it is up to UDSF implementation and deployment that only the NF instance within the set can access the data created by another NF instance within the NF set. If a UDSF is shared between several NFs not part of the same set or is shared between several NF sets, it is up to UDSF implementation and deployment to make sure that only NFs that are authorized can access the data. For further information about Guidelines and Principles for Compute-Storage Separation see Annex C. + +![Diagram of Data Storage Architecture for unstructured data from any NF. It shows a box labeled 'Any NF' connected to a box labeled 'UDSF' via a line labeled 'N18/Nudsf'.](20136850feb70fd71c7d41cdae203ebb_img.jpg) + +``` + +graph LR + AnyNF[Any NF] -- N18/Nudsf --> UDSF[UDSF] + +``` + +Diagram of Data Storage Architecture for unstructured data from any NF. It shows a box labeled 'Any NF' connected to a box labeled 'UDSF' via a line labeled 'N18/Nudsf'. + +**Figure 4.2.5-1: Data Storage Architecture for unstructured data from any NF** + +NOTE 3: 3GPP will specify (possibly by referencing) the N18/Nudsf interface. + +As depicted in Figure 4.2.5-2, the 5G System architecture allows the UDM, PCF and NEF to store data in the UDR, including subscription data and policy data by UDM and PCF, structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs) by the NEF. UDR can be deployed in each PLMN and it can serve different functions as follows: + +- UDR accessed by the NEF belongs to the same PLMN where the NEF is located. +- UDR accessed by the UDM belongs to the same PLMN where the UDM is located if UDM supports a split architecture. +- UDR accessed by the PCF belongs to the same PLMN where the PCF is located. + +NOTE 4: The UDR deployed in each PLMN can store application data for roaming subscribers. + +![Diagram of Data Storage Architecture. It shows three boxes on the left: UDM, PCF, and NEF. UDM is connected to a central box labeled 'UDR' via an 'N35' interface. PCF is connected to the UDR via an 'N36' interface. NEF is connected to the UDR via an 'N37' interface. All three interfaces (N35, N36, N37) converge into a single connection labeled 'Nudr' which enters the UDR box. Inside the UDR box, the 'Nudr' connection leads to a 'Data Access Provider' box, which is connected to a large cylinder representing a database. The database contains four types of data: 'Subscription Data', 'Policy Data', 'Structured Data for exposure', and 'Application Data'.](1c140ee5d1a87186977da94a96bfa700_img.jpg) + +``` + +graph LR + UDM[UDM] -- N35 --> Nudr((Nudr)) + PCF[PCF] -- N36 --> Nudr + NEF[NEF] -- N37 --> Nudr + Nudr --> UDR[UDR] + subgraph UDR + DataAccessProvider[Data Access Provider] + Database[(Subscription Data +Policy Data +Structured Data for exposure +Application Data)] + DataAccessProvider -.-> Database + end + +``` + +Diagram of Data Storage Architecture. It shows three boxes on the left: UDM, PCF, and NEF. UDM is connected to a central box labeled 'UDR' via an 'N35' interface. PCF is connected to the UDR via an 'N36' interface. NEF is connected to the UDR via an 'N37' interface. All three interfaces (N35, N36, N37) converge into a single connection labeled 'Nudr' which enters the UDR box. Inside the UDR box, the 'Nudr' connection leads to a 'Data Access Provider' box, which is connected to a large cylinder representing a database. The database contains four types of data: 'Subscription Data', 'Policy Data', 'Structured Data for exposure', and 'Application Data'. + +**Figure 4.2.5-2: Data Storage Architecture** + +NOTE 5: There can be multiple UDRs deployed in the network, each of which can accommodate different data sets or subsets, (e.g. subscription data, subscription policy data, data for exposure, application data) and/or serve different sets of NFs. Deployments where a UDR serves a single NF and stores its data, and, thus, can be integrated with this NF, can be possible. + +NOTE 6: The internal structure of the UDR in figure 4.2.5-2 is shown for information only. + +The Nudr interface is defined for the network functions (i.e. NF Service Consumers), such as UDM, PCF and NEF, to access a particular set of the data stored and to read, update (including add, modify), delete, and subscribe to notification of relevant data changes in the UDR. + +Each NF Service Consumer accessing the UDR, via Nudr, shall be able to add, modify, update or delete only the data it is authorised to change. This authorisation shall be performed by the UDR on a per data set and NF service consumer basis and potentially on a per UE, subscription granularity. + +The following data in the UDR sets exposed via Nudr to the respective NF service consumer and stored shall be standardized: + +- Subscription Data, +- Policy Data, +- Structured Data for exposure, +- Application data: Packet Flow Descriptions (PFDs) for application detection and AF request information for multiple UEs, as defined in clause 5.6.7. + +The service based Nudr interface defines the content and format/encoding of the 3GPP defined information elements exposed by the data sets. + +In addition, it shall be possible to access operator specific data sets by the NF Service Consumers from the UDR as well as operator specific data for each data set. + +NOTE 7: The content and format/encoding of operator specific data and operator specific data sets are not subject to standardization. + +NOTE 8: The organization of the different data stored in the UDR is not to be standardized. + +### 4.2.5a Radio Capabilities Signalling optimisation + +Figure 4.2.5a-1 depicts the AMF to UCMF reference point and interface. Figure 4.2.5a-2 depicts the related interfaces in AMF and UCMF for the Radio Capabilities Signalling optimisation in the roaming architecture. + +![Diagram of Radio Capability Signalling optimisation architecture showing the flow of information between UE, RAN, AMF, UCMF, NEF, and AF.](db7ae70402c81d140ae7df14b002e057_img.jpg) + +``` + +graph TD + UE[UE] -- N1 --> AMF[AMF] + RAN[RAN] -- N2 --> AMF + AMF -- N55 --> UCMF[UCMF] + UCMF -- N56 --> NEF[NEF] + UCMF -- N57 --> AF[AF] + NEF -- N33 --> AF + +``` + +The diagram illustrates the Radio Capability Signalling optimisation architecture. At the bottom left, a UE (User Equipment) is connected to a RAN (Radio Access Network) via the N1 interface. The RAN is connected to an AMF (Access and Management Function) via the N2 interface. The AMF is connected to a UCMF (User Context Management Function) via the N55 interface. The UCMF is connected to both a NEF (Network Exposure Function) via the N56 interface and an AF (Application Function) via the N57 interface. Finally, the NEF is connected to the AF via the N33 interface. + +Diagram of Radio Capability Signalling optimisation architecture showing the flow of information between UE, RAN, AMF, UCMF, NEF, and AF. + +Figure 4.2.5a-1: Radio Capability Signalling optimisation architecture + +![Diagram of Roaming architecture for Radio Capability Signalling optimisation. The diagram shows a UE connected to a RAN in the VPLMN. The RAN is connected to an AMF in the HPLMN via an N2 interface. The AMF is connected to a UCMF in the HPLMN via an N1 interface. The UCMF is connected to an NEF in the VPLMN via an Nucmf interface. The NEF is connected to an AF in the VPLMN via an Nnef interface. The AF is connected to the AMF via an Naf interface. A dashed vertical line separates the VPLMN (left) and HPLMN (right).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +graph TD + subgraph VPLMN + UE[UE] --- RAN[RAN] + RAN --- AMF[AMF] + AMF --- UCMF[UCMF] + UCMF --- NEF[NEF] + NEF --- AF[AF] + end + subgraph HPLMN + AMF --- N1((N1)) + N1 --- UCMF + end + AF --- Naf((Naf)) + Naf --- AMF + UCMF --- Nucmf((Nucmf)) + Nucmf --- NEF + NEF --- Nnef((Nnef)) + Nnef --- AF + RAN --- N2((N2)) + N2 --- AMF + +``` + +Diagram of Roaming architecture for Radio Capability Signalling optimisation. The diagram shows a UE connected to a RAN in the VPLMN. The RAN is connected to an AMF in the HPLMN via an N2 interface. The AMF is connected to a UCMF in the HPLMN via an N1 interface. The UCMF is connected to an NEF in the VPLMN via an Nucmf interface. The NEF is connected to an AF in the VPLMN via an Nnef interface. The AF is connected to the AMF via an Naf interface. A dashed vertical line separates the VPLMN (left) and HPLMN (right). + +NOTE: The AF in the VPLMN (i.e. the one having a relationship with the VPLMN NEF) is the one which provisions Manufacturer Assigned UE radio capability IDs in the VPLMN UCMF. RACS is a serving PLMN only feature (it requires no specific support in the roaming agreement with the UE HPLMN to operate). + +**Figure 4.2.5a-2: Roaming architecture for Radio Capability Signalling optimisation** + +### 4.2.6 Service-based interfaces + +The 5G System Architecture contains the following service-based interfaces: + +- Namf:** Service-based interface exhibited by AMF. +- Nsmf:** Service-based interface exhibited by SMF. +- Nnef:** Service-based interface exhibited by NEF. +- Npcf:** Service-based interface exhibited by PCF. +- Nudm:** Service-based interface exhibited by UDM. +- Naf:** Service-based interface exhibited by AF. +- Nnrf:** Service-based interface exhibited by NRF. +- Nnsacf:** Service-based interface exhibited by NSACF. +- NnssAAF:** Service-based interface exhibited by NSSAAF. +- Nnssf:** Service-based interface exhibited by NSSF. +- Nausf:** Service-based interface exhibited by AUSF. +- Nudr:** Service-based interface exhibited by UDR. +- Nudsf:** Service-based interface exhibited by UDSF. +- N5g-eir:** Service-based interface exhibited by 5G-EIR. +- Nnwdaf:** Service-based interface exhibited by NWDAF. +- Nchf:** Service-based interface exhibited by CHF. +- Nucmf:** Service-based interface exhibited by UCMF. +- Ndccf:** Service based interface exhibited by DCCF. +- NmfaF:** Service based interface exhibited by MFAF. +- Nadrf:** Service based interface exhibited by ADRF. + +**Naanf:** Service-based interface exhibited by AANF. + +NOTE 1: The Service-based interface exhibited by AANF is defined in TS 33.535 [124]. + +**N5g-ddnmf:** Service-based interface exhibited by 5G DDNMF. + +**Nmbsmf:** Service-based interface exhibited by MB-SMF. + +**Nmbssf:** Service-based interface exhibited by MBSF. + +NOTE 2: The Service-based interfaces exhibited by MB-SMF and MBSF are defined in TS 23.247 [129]. + +**Ntctssf:** Service-based interface exhibited by TSCTSF. + +**Nbsp:** Service-based interface exhibited by an SBI capable Boostrapping Server Function in GBA. + +NOTE 2: The Service-based interfaces exhibited by an SBI capable Boostrapping Server Function are defined in TS 33.220 [140] and TS 33.223 [141]. + +**Neasdf:** Service-based interface exhibited by EASDF. + +NOTE 3: The Service-based interfaces exhibited by EASDF is defined in TS 23.548 [130]. + +**Nupf:** Service-based interface exhibited by UPF. + +### 4.2.7 Reference points + +The 5G System Architecture contains the following reference points: + +- N1:** Reference point between the UE and the AMF. +- N2:** Reference point between the (R)AN and the AMF. +- N3:** Reference point between the (R)AN and the UPF. +- N4:** Reference point between the SMF and the UPF. +- N6:** Reference point between the UPF and a Data Network. +- N9:** Reference point between two UPFs. + +The following reference points show the interactions that exist between the NF services in the NFs. These reference points are realized by corresponding NF service-based interfaces and by specifying the identified consumer and producer NF service as well as their interaction in order to realize a particular system procedure. + +- N5:** Reference point between the PCF and an AF or TSN AF. +- N7:** Reference point between the SMF and the PCF. +- N8:** Reference point between the UDM and the AMF. +- N10:** Reference point between the UDM and the SMF. +- N11:** Reference point between the AMF and the SMF. +- N12:** Reference point between AMF and AUSF. +- N13:** Reference point between the UDM and Authentication Server function the AUSF. +- N14:** Reference point between two AMFs. +- N15:** Reference point between the PCF and the AMF in the case of non-roaming scenario, PCF in the visited network and AMF in the case of roaming scenario. +- N16:** Reference point between two SMFs, (in roaming case between SMF in the visited network and the SMF in the home network). + +- N16a:** Reference point between SMF and I-SMF. +- N17:** Reference point between AMF and 5G-EIR. +- N18:** Reference point between any NF and UDSF. +- N19:** Reference point between two PSA UPFs for 5G LAN-type service. +- N22:** Reference point between AMF and NSSF. +- N23:** Reference point between PCF and NWDAF. +- N24:** Reference point between the PCF in the visited network and the PCF in the home network. +- N27:** Reference point between NRF in the visited network and the NRF in the home network. +- N28:** Reference point between PCF and CHF. +- N29:** Reference point between NEF and SMF. +- N30:** Reference point between PCF and NEF. +- NOTE 1: The functionality of N28 and N29 and N30 reference points are defined in TS 23.503 [45]. +- N31:** Reference point between the NSSF in the visited network and the NSSF in the home network. +- NOTE 2: In some cases, a couple of NFs may need to be associated with each other to serve a UE. +- N32:** Reference point between a SEPP in one PLMN or SNPN and a SEPP in another PLMN or SNPN; or between a SEPP in a SNPN and a SEPP in a CH/DCS, where the CH/DCS contains a UDM/AUSF. +- NOTE 3: The functionality of N32 reference point is defined in TS 33.501 [29]. +- N33:** Reference point between NEF and AF. +- N34:** Reference point between NSSF and NWDAF. +- N35:** Reference point between UDM and UDR. +- N36:** Reference point between PCF and UDR. +- N37:** Reference point between NEF and UDR. +- N38:** Reference point between I-SMFs and between V-SMFs. +- N40:** Reference point between SMF and the CHF. +- N41:** Reference point between AMF and CHF in HPLMN. +- N42:** Reference point between AMF and CHF in VPLMN. +- NOTE 4: The functionality of N40, N41 and N42 reference points are defined in TS 32.240 [41]. +- N43:** Reference point between PCFs. +- NOTE 5: The functionality of N43 reference point is defined in TS 23.503 [45]. +- NOTE 6: The reference points from N44 up to and including N49 are reserved for allocation and definition in TS 32.240 [41]. +- N50:** Reference point between AMF and the CBCF. +- N51:** Reference point between AMF and NEF. +- N52:** Reference point between NEF and UDM. +- N55:** Reference point between AMF and the UCMF. +- N56:** Reference point between NEF and the UCMF. + +**N57:** Reference point between AF and the UCMF. + +NOTE 7: The Public Warning System functionality of N50 reference point is defined in TS 23.041 [46]. + +**N58:** Reference point between AMF and the NSSAAF. + +**N59:** Reference point between UDM and the NSSAAF. + +**N60:** Reference point between AUSF and NSWOF. + +NOTE 8: The functionality of N60 reference point is defined in TS 33.501 [29]. + +**N80:** Reference point between AMF and NSACF. + +**N81:** Reference point between SMF and NSACF. + +**N82:** Reference point between NSACF and NEF. + +**N83:** Reference point between AUSF and NSSAAF. + +**N84:** Reference point between TSCTSF and PCF. + +**N85:** Reference point between TSCTSF and NEF. + +**N86:** Reference point between TSCTSF and AF. + +**N87:** Reference point between TSCTSF and UDM. + +**N88:** Reference point between SMF and EASDF. + +**N89:** Reference point between TSCTSF and AMF. + +**N96:** Reference point between TSCTSF and NRF. + +**N97:** Reference point between two NSACFs in different PLMNs. + +**N99:** Reference point between two NSACFs within the same PLMN. + +NOTE 9: The reference points from N90 up to and including N95 are reserved for allocation and definition in TS 23.503 [45]. + +NOTE 10: The reference points from N100 up to and including N109 are reserved for allocation and definition in TS 32.240 [41]. + +The reference points to support SMS over NAS are listed in clause 4.4.2.2. + +The reference points to support Location Services are listed in TS 23.273 [87]. + +The reference points to support SBA in IMS (N5, N70 and N71) are described in TS 23.228 [15]. + +The reference points to support AKMA (N61, N62 and N63) are described in TS 33.535 [124]. + +The reference points to support 5G ProSe are described in TS 23.304 [128]. + +The reference points to support 5G multicast-broadcast services are described in TS 23.247 [129]. + +The reference points to Support Uncrewed Aerial Systems (UAS) connectivity, identification and tracking are described in TS 23.256 [136]. + +The reference points to support SBA in GBA and GBA push (N65, N66, N67 and N68) are described in TS 33.220 [140] and TS 33.223 [141]. + +The reference points to support SMS delivery using SBA are described in TS 23.540 [142]. + +The reference points to support Ranging based services and Sidelink Positioning are described in TS 23.586 [180]. + +### 4.2.8 Support of non-3GPP access + +#### 4.2.8.0 General + +In this Release of the specification, the following types of non-3GPP access networks are defined: + +- Untrusted non-3GPP access networks; +- Trusted non-3GPP access networks; and +- Wireline access networks. + +The architecture to support Untrusted and Trusted non-3GPP access networks is defined in clause 4.2.8.2. The architecture to support Wireline access networks is defined in clause 4.2.8.2.4 and in TS 23.316 [84]. + +#### 4.2.8.1 General Concepts to Support Trusted and Untrusted Non-3GPP Access + +The 5G Core Network supports connectivity of UEs via non-3GPP access networks, e.g. WLAN access networks. + +Only the support of non-3GPP access networks deployed outside the NG-RAN is described in this clause. + +The 5G Core Network supports both untrusted non-3GPP access networks and trusted non-3GPP access networks (TNANs). + +An untrusted non-3GPP access network shall be connected to the 5G Core Network via a Non-3GPP InterWorking Function (N3IWF), whereas a trusted non-3GPP access network shall be connected to the 5G Core Network via a Trusted Non-3GPP Gateway Function (TNGF). Both the N3IWF and the TNGF interface with the 5G Core Network CP and UP functions via the N2 and N3 interfaces, respectively. + +A non-3GPP access network may advertise the PLMNs or SNPNs for which it supports trusted connectivity and the type of supported trusted connectivity (e.g. "5G connectivity"). Therefore, the UEs can discover the non-3GPP access networks that can provide trusted connectivity to one or more PLMNs or SNPNs. This is further specified in clause 6.3.12 (Trusted Non-3GPP Access Network selection). + +The UE decides to use trusted or untrusted non-3GPP access for connecting to a 5G PLMN or SNPNs by using procedures not specified in this document. Examples of such procedures are defined in clause 6.3.12.1. + +When the UE decides to use untrusted non-3GPP access to connect to a 5G Core Network in a PLMN: + +- the UE first selects and connects with a non-3GPP access network; and then +- the UE selects a PLMN/SNPN and an N3IWF in this PLMN/SNPN. The PLMN/SNPN/N3IWF selection and the non-3GPP access network selection are independent. The N3IWF selection is defined in clause 6.3.6. + +When the UE decides to use trusted non-3GPP access to connect to a 5G Core Network in a PLMN: + +- the UE first selects a PLMN/SNPN; and then +- the UE selects a non-3GPP access network (a TNAN) that supports trusted connectivity to the selected PLMN/SNPN. In this case, the non-3GPP access network selection is affected by the PLMN/SNPN selection. + +A UE that accesses the 5G Core Network over a non-3GPP access shall, after UE registration, support NAS signalling with 5G Core Network control-plane functions using the N1 reference point. + +When a UE is connected via a NG-RAN and via a non-3GPP access, multiple N1 instances shall exist for the UE i.e. there shall be one N1 instance over NG-RAN and one N1 instance over non-3GPP access. + +A UE simultaneously connected to the same 5G Core Network of a PLMN/SNPN over a 3GPP access and a non-3GPP access shall be served by a single AMF in this 5G Core Network. + +When a UE is connected to a 3GPP access of a PLMN, if the UE selects a N3IWF and the N3IWF is located in a PLMN different from the PLMN of the 3GPP access, e.g. in a different VPLMN or in the HPLMN, the UE is served separately by the two PLMNs. The UE is registered with two separate AMFs. PDU Sessions over the 3GPP access are served by V-SMFs different from the V-SMF serving the PDU Sessions over the non-3GPP access. The same can be true when + +the UE uses trusted non-3GPP access, i.e. the UE may select one PLMN for 3GPP access and a different PLMN for trusted non-3GPP access. + +NOTE: The registrations with different PLMNs over different Access Types doesn't apply to UE registered for Disaster Roaming service as described in the clause 5.40. + +The PLMN selection for the 3GPP access does not depend on the PLMN that is used for non-3GPP access. In other words, if a UE is registered with a PLMN over a non-3GPP access, the UE performs PLMN selection for the 3GPP access independently of this PLMN. + +A UE shall establish an IPsec tunnel with the N3IWF or with the TNGF in order to register with the 5G Core Network over non-3GPP access. Further details about the UE registration to 5G Core Network over untrusted non-3GPP access and over trusted non-3GPP access are described in clause 4.12.2 and in clause 4.12.2a of TS 23.502 [3], respectively. + +It shall be possible to maintain the UE NAS signalling connection with the AMF over the non-3GPP access after all the PDU Sessions for the UE over that access have been released or handed over to 3GPP access. + +N1 NAS signalling over non-3GPP accesses shall be protected with the same security mechanism applied for N1 over a 3GPP access. + +User plane QoS differentiation between UE and N3IWF is supported as described in clause 5.7 and clause 4.12.5 of TS 23.502 [3]. QoS differentiation between UE and TNGF is supported as described in clause 5.7 and clause 4.12a.5 of TS 23.502 [3]. + +#### 4.2.8.1A General Concepts to support Wireline Access + +Wireline 5G Access Network (W-5GAN) shall be connected to the 5G Core Network via a Wireline Access Gateway Function (W-AGF). The W-AGF interfaces the 5G Core Network CP and UP functions via N2 and N3 interfaces, respectively. + +For the scenario of 5G-RG connected via NG RAN the specification for UE defined in this TS, TS 23.502 [3] and TS 23.503 [45] are applicable as defined for UE connected to 5GC via NG RAN unless differently specified in this TS and in TS 23.316 [84]. + +When a 5G-RG is connected via a NG-RAN and via a W-5GAN, multiple N1 instances shall exist for the 5G-RG i.e. there shall be one N1 instance over NG-RAN and one N1 instance over W-5GAN. + +A 5G-RG simultaneously connected to the same 5G Core Network of a PLMN over a 3GPP access and a W-5GAN access shall be served by a single AMF in this 5G Core Network. + +5G-RG shall maintain the NAS signalling connection with the AMF over the W-5GAN after all the PDU Sessions for the 5G-RG over that access have been released or handed over to 3GPP access. + +The 5G-RG connected to 5GC via NG-RAN is specified in TS 23.316 [84]. + +For the scenario of FN-RG, which is not 5G capable, connected via W-5GAN to 5GC, the W-AGF provides the N1 interface to AMF on behalf of the FN-RG. + +An UE connected to a 5G-RG or FN-RG can access to the 5GC via the N3IWF or via the TNGF where the combination of 5G-RG/FN-RG, W-AGF and UPF serving the 5G-RG or FN-RG is acting respectively as Untrusted Non-3GPP access network or as a Trusted Non-3GPP access network defined in clause 4.2.8.2; for example a UE is connecting to 5G-RG by means of WLAN radio access and connected to 5GC via N3IWF. The detailed description is specified in TS 23.316 [84]. + +The roaming architecture for 5G-BRG, FN-BRG, 5G-CRG and FN-CRG with the W-5GAN is not specified in this Release. The Home Routed roaming scenario is supported for 5G-RG connected via NG RAN, while Local Breakout scenario is not supported. + +5G Multi-Operator Core Network (5G MOCN) is supported for 5G-RG connected via NG RAN as defined in clause 5.18 + +#### 4.2.8.2 Architecture Reference Model for Trusted and Untrusted Non-3GPP Accesses + +##### 4.2.8.2.1 Non-roaming Architecture + +![Figure 4.2.8.2.1-1: Non-roaming architecture for 5G Core Network with untrusted non-3GPP access. The diagram shows a UE connected to a 3GPP Access and an Untrusted Non-3GPP Access. The 3GPP Access connects to an AMF via N2 and N1 interfaces. The Untrusted Non-3GPP Access connects to the AMF via N1 and N2 interfaces. The AMF connects to an SMF via N11 and to an N3IWF via N2. The N3IWF connects to a UPF via N3. The SMF connects to the UPF via N4. The UPF connects to a Data Network via N6. A dashed red line separates the HPLMN (Home PLMN) from the Non-3GPP Networks. The UE is connected to the Untrusted Non-3GPP Access via Y1 and Y2 interfaces. The N3IWF is connected to the UE via NWu and Y1 interfaces.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +Figure 4.2.8.2.1-1: Non-roaming architecture for 5G Core Network with untrusted non-3GPP access. The diagram shows a UE connected to a 3GPP Access and an Untrusted Non-3GPP Access. The 3GPP Access connects to an AMF via N2 and N1 interfaces. The Untrusted Non-3GPP Access connects to the AMF via N1 and N2 interfaces. The AMF connects to an SMF via N11 and to an N3IWF via N2. The N3IWF connects to a UPF via N3. The SMF connects to the UPF via N4. The UPF connects to a Data Network via N6. A dashed red line separates the HPLMN (Home PLMN) from the Non-3GPP Networks. The UE is connected to the Untrusted Non-3GPP Access via Y1 and Y2 interfaces. The N3IWF is connected to the UE via NWu and Y1 interfaces. + +Figure 4.2.8.2.1-1: Non-roaming architecture for 5G Core Network with untrusted non-3GPP access + +![Figure 4.2.8.2.1-2: Non-roaming architecture for 5G Core Network with trusted non-3GPP access. The diagram shows a UE connected to a 3GPP Access and a Trusted Non-3GPP Access Network (TNAN). The 3GPP Access connects to an AMF via N2 and N1 interfaces. The TNAN contains a Trusted Non-3GPP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF). The UE connects to the TNAP via NWt and Yt interfaces. The TNAP connects to the TNGF via Ta and Tn interfaces. The TNGF connects to the AMF via N1 and N2 interfaces. The AMF connects to an SMF via N11 and to a UPF via N3. The SMF connects to the UPF via N4. The UPF connects to a Data Network via N6. A dashed red line separates the HPLMN (Home PLMN) from the TNAN.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +Figure 4.2.8.2.1-2: Non-roaming architecture for 5G Core Network with trusted non-3GPP access. The diagram shows a UE connected to a 3GPP Access and a Trusted Non-3GPP Access Network (TNAN). The 3GPP Access connects to an AMF via N2 and N1 interfaces. The TNAN contains a Trusted Non-3GPP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF). The UE connects to the TNAP via NWt and Yt interfaces. The TNAP connects to the TNGF via Ta and Tn interfaces. The TNGF connects to the AMF via N1 and N2 interfaces. The AMF connects to an SMF via N11 and to a UPF via N3. The SMF connects to the UPF via N4. The UPF connects to a Data Network via N6. A dashed red line separates the HPLMN (Home PLMN) from the TNAN. + +Figure 4.2.8.2.1-2: Non-roaming architecture for 5G Core Network with trusted non-3GPP access + +NOTE 1: The reference architecture in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 only shows the architecture and the network functions directly connected to non-3GPP access, and other parts of the architecture are the same as defined in clause 4.2. + +NOTE 2: The reference architecture in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. + +NOTE 3: The two N2 instances in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 terminate to a single AMF for a UE which is simultaneously connected to the same 5G Core Network over 3GPP access and non-3GPP access. + +NOTE 4 The two N3 instances in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 may terminate to different UPFs when different PDU Sessions are established over 3GPP access and non-3GPP access. + +##### 4.2.8.2.2 LBO Roaming Architecture + +![Diagram of LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access.](9870bf462aa0d916a16d14b5a100c60a_img.jpg) + +This diagram illustrates the LBO Roaming architecture for a 5G Core Network where the N3IWF is located in the same VPLMN as the 3GPP access. The architecture is divided into three horizontal sections by dashed red lines: VPLMN (top), Non-3GPP Networks (middle), and UE (bottom). In the VPLMN, the 3GPP Access (circle) connects to the AMF (rectangle) via N2 and N3 interfaces. The AMF connects to the SMF (rectangle) via N11 and to the N3IWF (rectangle) via N2. The N3IWF connects to the UPF (rectangle) via N3. The SMF connects to the UPF via N4. The UPF connects to the Data Network (circle) via N6. In the Non-3GPP Networks section, the UE (rectangle) connects to the Untrusted Non-3GPP Access (circle) via Y1 and Y2 interfaces. The Untrusted Non-3GPP Access connects to the N3IWF via NwU and N1 interfaces. A dashed line labeled N1 connects the 3GPP Access to the UE. + +Diagram of LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access. + +Figure 4.2.8.2.2-1: LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access + +![Diagram of LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different PLMN from 3GPP access.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) + +This diagram illustrates the LBO Roaming architecture for a 5G Core Network where the N3IWF is located in a different PLMN from the 3GPP access. The architecture is divided into three horizontal sections by dashed red lines: VPLMN1 (top), Non-3GPP Networks (middle), and VPLMN2 or HPLMN (bottom). In VPLMN1, the 3GPP Access (circle) connects to the AMF (rectangle) via N2 and N3 interfaces. The AMF connects to the SMF (rectangle) via N11 and to the UPF (rectangle) via N4. The UPF connects to the Data Network (circle) via N6. In the Non-3GPP Networks section, the UE (rectangle) connects to the Untrusted Non-3GPP Access (circle) via Y1 and Y2 interfaces. The Untrusted Non-3GPP Access connects to the N3IWF (rectangle) via NwU and N1 interfaces. A dashed line labeled N1 connects the 3GPP Access to the UE. In the VPLMN2 or HPLMN section, the N3IWF connects to the AMF (rectangle) via N2. The AMF connects to the SMF (rectangle) via N11. The SMF connects to the UPF (rectangle) via N4. The UPF connects to the Data Network (circle) via N6. The N3IWF also connects to the UPF via N3. + +Diagram of LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different PLMN from 3GPP access. + +Figure 4.2.8.2.2-2: LBO Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different PLMN from 3GPP access + +![Figure 4.2.8.2.2-3: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access. The diagram shows a UE connected to a Trusted Non-3GPP Access Network (TNAN) via NWt and Yt interfaces. The TNAN contains a Trusted Non-3GPP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF) connected by Ta and Tn interfaces. The TNGF is connected to a UPF via an N3 interface. The UPF is connected to a Data Network via an N6 interface and to an SMF via an N4 interface. The SMF is connected to an AMF via an N11 interface. The AMF is connected to a 3GPP Access via an N2 interface. The 3GPP Access is connected to the UE via an N1 interface. A dashed red line separates the UE and TNAN from the rest of the network, labeled VPLMN.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Figure 4.2.8.2.2-3: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access. The diagram shows a UE connected to a Trusted Non-3GPP Access Network (TNAN) via NWt and Yt interfaces. The TNAN contains a Trusted Non-3GPP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF) connected by Ta and Tn interfaces. The TNGF is connected to a UPF via an N3 interface. The UPF is connected to a Data Network via an N6 interface and to an SMF via an N4 interface. The SMF is connected to an AMF via an N11 interface. The AMF is connected to a 3GPP Access via an N2 interface. The 3GPP Access is connected to the UE via an N1 interface. A dashed red line separates the UE and TNAN from the rest of the network, labeled VPLMN. + +**Figure 4.2.8.2.2-3: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access** + +![Figure 4.2.8.2.2-4: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using a different PLMN than 3GPP access. The diagram shows a UE connected to a Trusted Non-3GPP Access Network (TNAN) via NWt and Yt interfaces. The TNAN contains a Trusted Non-3GPP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF) connected by Ta and Tn interfaces. The TNGF is connected to a UPF via an N3 interface. The UPF is connected to a Data Network via an N6 interface and to an SMF via an N4 interface. The SMF is connected to an AMF via an N11 interface. The AMF is connected to a 3GPP Access via an N2 interface. The 3GPP Access is connected to the UE via an N1 interface. A dashed red line separates the UE and TNAN from the rest of the network, labeled VPLMN1 and VPLMN2 or HPLMN.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +Figure 4.2.8.2.2-4: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using a different PLMN than 3GPP access. The diagram shows a UE connected to a Trusted Non-3GPP Access Network (TNAN) via NWt and Yt interfaces. The TNAN contains a Trusted Non-3GPP Access Point (TNAP) and a Trusted Non-3GPP Gateway Function (TNGF) connected by Ta and Tn interfaces. The TNGF is connected to a UPF via an N3 interface. The UPF is connected to a Data Network via an N6 interface and to an SMF via an N4 interface. The SMF is connected to an AMF via an N11 interface. The AMF is connected to a 3GPP Access via an N2 interface. The 3GPP Access is connected to the UE via an N1 interface. A dashed red line separates the UE and TNAN from the rest of the network, labeled VPLMN1 and VPLMN2 or HPLMN. + +**Figure 4.2.8.2.2-4: LBO Roaming architecture for 5G Core Network with trusted non-3GPP access using a different PLMN than 3GPP access** + +NOTE 1: The reference architecture in all above figures only shows the architecture and the network functions directly connected to support non-3GPP access, and other parts of the architecture are the same as defined in clause 4.2. + +NOTE 2: The reference architecture in all above figures supports service based interfaces for AMF, SMF and other NFs not represented in the figures. + +NOTE 3: The two N2 instances in Figure 4.2.8.2.2-1 and in Figure 4.2.8.2.2-3 terminate to a single AMF for a UE which is connected to the same 5G Core Network over 3GPP access and non-3GPP access simultaneously. + +NOTE 4: The two N3 instances in Figure 4.2.8.2.2-1 and in Figure 4.2.8.2.2-3 may terminate to different UPFs when different PDU Sessions are established over 3GPP access and non-3GPP access. + +##### 4.2.8.2.3 Home-routed Roaming Architecture + +![Diagram of Home-routed Roaming Architecture for 5G Core Network with untrusted non-3GPP access.](fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg) + +The diagram illustrates the Home-routed Roaming Architecture for a 5G Core Network. It is divided into two main domains by a vertical dashed red line: the Visited PLMN (VPLMN) on the left and the Home PLMN (HPLMN) on the right. A horizontal dashed red line separates the 'Non-3GPP Networks' at the bottom from the rest of the architecture. + +**VPLMN (Left Side):** + +- 3GPP Access:** An oval representing 3GPP access, connected to the AMF via an N2 interface and to the UPF via an N3 interface. +- Non-3GPP Networks:** A box labeled 'UE' (User Equipment) is connected to the AMF via an N1 interface. The UE is also connected to an 'Untrusted Non-3GPP Access' oval via a Y1 interface. This oval is connected to an 'N3IWF' (Non-3GPP Interworking Function) box via an NWu interface. The N3IWF is connected to the AMF via an N2 interface and to the UPF via an N3 interface. Additionally, the N3IWF is connected to the 'Untrusted Non-3GPP Access' oval via Y2 and N1 interfaces. + +**Core Network Elements:** + +- AMF (Access and Management Function):** Receives connections from 3GPP Access (N2), UE (N1), and N3IWF (N2). It is connected to the vSMF via an N11 interface. +- vSMF (Visited SMF):** Connected to the AMF (N11) and the hSMF via an N16 interface. It is also connected to the UPF via an N4 interface. +- UPF (User Plane Function):** Connected to the 3GPP Access (N3), N3IWF (N3), vSMF (N4), and hSMF (N9) via N9 interface. + +**HPLMN (Right Side):** + +- hSMF (Home SMF):** Connected to the vSMF via an N16 interface and to the UPF via an N4 interface. +- Data Network:** An oval representing the Data Network, connected to the UPF. + +Diagram of Home-routed Roaming Architecture for 5G Core Network with untrusted non-3GPP access. + +Figure 4.2.8.2.3-1: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access + +![Figure 4.2.8.2.3-2: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different VPLMN than 3GPP access](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates a 5G roaming architecture across four domains: VPLMN1, HPLMN, Non-3GPP Networks, and VPLMN2, separated by dashed red lines. + +- VPLMN1 (Top Left):** Contains '3GPP Access', 'AMF', 'vSMF', and 'UPF'. The UE connects to 3GPP Access via N1. 3GPP Access connects to AMF (N2) and UPF (N3). AMF connects to vSMF (N11). vSMF connects to UPF (N4). +- Non-3GPP Networks (Middle Left):** Contains the 'UE' and 'Untrusted Non-3GPP Access'. The UE connects to Untrusted Non-3GPP Access via Y1. +- VPLMN2 (Bottom Left):** Contains 'N3IWF', 'AMF', 'vSMF', and 'UPF'. Untrusted Non-3GPP Access connects to N3IWF via NWu and Y2. The UE has an N1 connection to the AMF in VPLMN2. N3IWF connects to AMF (N2) and UPF (N3). AMF connects to vSMF (N11). vSMF connects to UPF (N4). +- HPLMN (Right):** Contains 'hSMF', 'UPF', and 'Data Network'. The vSMF in VPLMN1 connects to hSMF via N16. The vSMF in VPLMN2 also connects to hSMF via N16. The UPF in VPLMN1 connects to the UPF in HPLMN via N9. The UPF in VPLMN2 also connects to the UPF in HPLMN via N9. The hSMF connects to the HPLMN UPF via N4. The HPLMN UPF connects to the Data Network. + +Figure 4.2.8.2.3-2: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different VPLMN than 3GPP access + +**Figure 4.2.8.2.3-2: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different VPLMN than 3GPP access** + +![Figure 4.2.8.2.3-3: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in HPLMN](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +The diagram illustrates a 5G roaming architecture across three domains: VPLMN, Non-3GPP Networks, and HPLMN, separated by dashed red lines. + +- VPLMN (Top Left):** Contains '3GPP Access', 'AMF', 'vSMF', and 'UPF'. The UE connects to 3GPP Access via N1. 3GPP Access connects to AMF (N2) and UPF (N3). AMF connects to vSMF (N11). vSMF connects to UPF (N4). +- Non-3GPP Networks (Bottom Left):** Contains the 'UE' and 'Untrusted Non-3GPP Access'. The UE connects to Untrusted Non-3GPP Access via Y1. +- HPLMN (Right):** Contains 'AMF', 'N3IWF', 'hSMF / SMF', 'UPF', and 'Data Network'. Untrusted Non-3GPP Access connects to N3IWF via NWu and Y2. The UE has an N1 connection to the AMF in HPLMN. N3IWF connects to AMF (N2) and the HPLMN UPF (N3). The vSMF in VPLMN connects to hSMF/SMF via N16. The AMF in HPLMN connects to hSMF/SMF via N11. The UPF in VPLMN connects to the UPF in HPLMN via N9. The hSMF/SMF connects to the HPLMN UPF via N4. The HPLMN UPF connects to the Data Network. + +Figure 4.2.8.2.3-3: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in HPLMN + +**Figure 4.2.8.2.3-3: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in HPLMN** + +![Figure 4.2.8.2.3-4: Home-routed Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access. The diagram shows a UE connected to a Trusted Non-3GPP Access Network (TNAN) via reference points NWt and Yt. The TNAN contains a Trusted Non-3GPP Access Point (connected to the UE via NWt) and a Trusted Non-3GPP Gateway Function (connected to the UE via Yt). The UE is also connected to 3GPP Access via N1 and N2. The 3GPP Access is connected to an AMF via N2. The AMF is connected to a vSMF via N11 and to a UPF via N3. The vSMF is connected to a hSMF via N16 and to a UPF via N4. The hSMF is connected to a UPF via N4. The UPF is connected to a Data Network via N6. The diagram is divided into two domains by a vertical dashed red line: VPLMN (left) and HPLMN (right). The UE, 3GPP Access, and TNAN are in the VPLMN. The AMF, vSMF, and UPF are in the HPLMN. The hSMF and Data Network are also in the HPLMN.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Figure 4.2.8.2.3-4: Home-routed Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access. The diagram shows a UE connected to a Trusted Non-3GPP Access Network (TNAN) via reference points NWt and Yt. The TNAN contains a Trusted Non-3GPP Access Point (connected to the UE via NWt) and a Trusted Non-3GPP Gateway Function (connected to the UE via Yt). The UE is also connected to 3GPP Access via N1 and N2. The 3GPP Access is connected to an AMF via N2. The AMF is connected to a vSMF via N11 and to a UPF via N3. The vSMF is connected to a hSMF via N16 and to a UPF via N4. The hSMF is connected to a UPF via N4. The UPF is connected to a Data Network via N6. The diagram is divided into two domains by a vertical dashed red line: VPLMN (left) and HPLMN (right). The UE, 3GPP Access, and TNAN are in the VPLMN. The AMF, vSMF, and UPF are in the HPLMN. The hSMF and Data Network are also in the HPLMN. + +**Figure 4.2.8.2.3-4: Home-routed Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access** + +NOTE 1: The reference architecture in all above figures only shows the architecture and the network functions directly connected to support non-3GPP access, and other parts of the architecture are the same as defined in clause 4.2. + +NOTE 2: The two N2 instances in Figure 4.2.8.2.3-1 and in Figure 4.2.8.2.3-4 terminate to a single AMF for a UE which is connected to the same 5G Core Network over 3GPP access and non-3GPP access simultaneously. + +#### 4.2.8.3 Reference Points for Non-3GPP Access + +##### 4.2.8.3.1 Overview + +The description of the reference points specific for the non-3GPP access: + +N2, N3, N4, N6: these are defined in clause 4.2. + +- Y1** Reference point between the UE and the untrusted non-3GPP access (e.g. WLAN). This depends on the non-3GPP access technology and is outside the scope of 3GPP. +- Y2** Reference point between the untrusted non-3GPP access and the N3IWF for the transport of NWu traffic. +- Y4** Reference point between the 5G-RG and the W-AGF which transports the user plane traffic and the N1 NAS protocol. The definition of this interface is outside the scope of 3GPP. +- Y5** Reference point between the FN-RG and the W-AGF. The definition of this interface is outside the scope of 3GPP. +- Yt** Reference point between the UE and the TNAP. See e.g. Figure 4.2.8.2.1-2. +- Yt'** Reference point between the N5CW devices and the TWAP. It is defined in clause 4.2.8.5. +- NWu** Reference point between the UE and N3IWF for establishing secure tunnel(s) between the UE and N3IWF so that control-plane and user-plane exchanged between the UE and the 5G Core Network is transferred securely over untrusted non-3GPP access. +- NWt** Reference point between the UE and the TNGF. A secure NWt connection is established over this reference point, as specified in clause 4.12a.2.2 of TS 23.502 [3]. NAS messages between the UE and the AMF are transferred via this NWt connection. + +**Ta** A reference point between the TNAP and the TNGF, which is used to support an AAA interface. Ta requirements are documented in clause 4.2.8.3.2. + +**Tn** A reference point between two TNGFs, which is used to facilitate UE mobility between different TNGFs (inter-TNGF mobility). + +Tn and inter-TNGF mobility are not specified in this Release of the specification. + +##### 4.2.8.3.2 Requirements on Ta + +Ta shall be able to + +- Carry EAP-5G traffic and user location information before the NWt connection is established between the UE and the TNGF. +- Allow the UE and the TNGF to exchange IP traffic. + +In deployments where the TNAP does not allocate the local IP addresses to UE(s), Ta shall be able to: + +- Allow the UE to request and receive IP configuration from the TNAN (including a local IP address), e.g. with DHCP. This is to allow the UE to use an IP stack to establish a NWt connection between the UE and the TNGF. + +NOTE: The "local IP address" is the IP address that allows the UE to contact the TNGF; the entity providing this local IP address is part of TNAN and out of 3GPP scope + +In this Release of the specification, Ta is not specified. + +#### 4.2.8.4 Architecture Reference Model for Wireline Access network + +![Figure 4.2.8.4-1: Non-roaming architecture for 5G Core Network for 5G-RG with Wireline 5G Access network and NG RAN. The diagram shows a 5G-RG connected to a W-AGF (part of W-5GAN) and a 3GPP Access. The W-AGF is connected to an AMF via N1 and N3 interfaces. The 3GPP Access is connected to the AMF via N2 and N3 interfaces. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to a Data Network via N6. The 5G-RG is also connected to the W-AGF via Y4 interface.](8a8517bfa4f6191c52c47697716255a9_img.jpg) + +``` + +graph LR + 5G-RG[5G-RG] --- N1((N1)) + N1 --- W-AGF[W-AGF] + 5G-RG --- Y4((Y4)) + Y4 --- W-AGF + 3GPP[3GPP Access] --- N2((N2)) + N2 --- AMF[AMF] + 3GPP --- N3((N3)) + N3 --- W-AGF + W-AGF --- N1((N1)) + N1 --- AMF + W-AGF --- N3((N3)) + N3 --- AMF + AMF --- N11((N11)) + N11 --- SMF[SMF] + SMF --- N4((N4)) + N4 --- UPF[UPF] + UPF --- N6((N6)) + N6 --- DN((Data Network)) + subgraph W-5GAN + W-AGF + end + +``` + +Figure 4.2.8.4-1: Non-roaming architecture for 5G Core Network for 5G-RG with Wireline 5G Access network and NG RAN. The diagram shows a 5G-RG connected to a W-AGF (part of W-5GAN) and a 3GPP Access. The W-AGF is connected to an AMF via N1 and N3 interfaces. The 3GPP Access is connected to the AMF via N2 and N3 interfaces. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to a Data Network via N6. The 5G-RG is also connected to the W-AGF via Y4 interface. + +**Figure 4.2.8.4-1: Non-roaming architecture for 5G Core Network for 5G-RG with Wireline 5G Access network and NG RAN** + +The 5G-RG can be connected to 5GC via W-5GAN, NG RAN or via both accesses. + +NOTE 1: The reference architecture in figure 4.2.8.4-1 only shows the architecture and the network functions directly connected to Wireline 5G Access Network, and other parts of the architecture are the same as defined in clause 4.2. + +NOTE 2: The reference architecture in figure 4.2.8.4-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. + +NOTE 3: The two N2 instances in Figure 4.2.8.4-1 apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and Wireline 5G Access Network. + +NOTE 4: The two N3 instances in Figure 4.2.8.4-1 may apply to different UPFs when different PDU Sessions are established over 3GPP access and Wireline 5G Access Network. + +![Figure 4.2.8.4-2: Non-roaming architecture for 5G Core Network for FN-RG with Wireline 5G Access network and NG RAN. The diagram shows an FN-RG connected to a W-AGF within a W-5GAN. The W-AGF connects to an AMF via the N1 interface. The AMF connects to an SMF via the N11 interface and to the W-AGF via the N2 interface. The SMF connects to a UPF via the N4 interface. The UPF connects to a Data Network via the N6 interface. The W-AGF also connects to the UPF via the N3 interface. The FN-RG is connected to the W-AGF via the Y5 interface.](34b047489058d6400b412cd0ae2334ba_img.jpg) + +``` + +graph TD + FN_RG[FN-RG] -- Y5 --> W_AGF[W-AGF] + subgraph W_5GAN [W-5GAN] + W_AGF + end + W_AGF -- N1 --> AMF[AMF] + AMF -- N2 --> W_AGF + AMF -- N11 --> SMF[SMF] + SMF -- N4 --> UPF[UPF] + UPF -- N6 --> DN((Data Network)) + W_AGF -- N3 --> UPF + +``` + +Figure 4.2.8.4-2: Non-roaming architecture for 5G Core Network for FN-RG with Wireline 5G Access network and NG RAN. The diagram shows an FN-RG connected to a W-AGF within a W-5GAN. The W-AGF connects to an AMF via the N1 interface. The AMF connects to an SMF via the N11 interface and to the W-AGF via the N2 interface. The SMF connects to a UPF via the N4 interface. The UPF connects to a Data Network via the N6 interface. The W-AGF also connects to the UPF via the N3 interface. The FN-RG is connected to the W-AGF via the Y5 interface. + +**Figure 4.2.8.4-2: Non-roaming architecture for 5G Core Network for FN-RG with Wireline 5G Access network and NG RAN** + +The N1 for the FN-RG, which is not 5G capable, is terminated on W-AGF which acts on behalf of the FN-RG. + +The FN-RG can only be connected to 5GC via W-5GAN. + +NOTE 5: The reference architecture in figure 4.2.8.4-2 only shows the architecture and the network functions directly connected to Wireline 5G Access Network, and other parts of the architecture are the same as defined in clause 4.2. + +NOTE 6: The reference architecture in figure 4.2.8.4-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. + +#### 4.2.8.5 Access to 5GC from devices that do not support 5GC NAS over WLAN access + +##### 4.2.8.5.1 General + +The devices that do not support 5GC NAS signalling over WLAN access are referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short. A N5CW device is not capable to operate as a 5G UE that supports 5GC NAS signalling over a WLAN access network, however, it may be capable to operate as a 5G UE over NG-RAN. + +Clause 4.2.8.5 specifies the 5GC architectural enhancements that enable N5CW devices to access 5GC via trusted WLAN access networks. A trusted WLAN access network is a particular type of a Trusted Non-3GPP Access Network (TNAN) that supports a WLAN access technology, e.g. IEEE 802.11. Not all trusted WLAN access networks support 5GC access from N5CW devices. To support 5GC access from N5CW devices, a trusted WLAN access network must support the special functionality specified below (e.g. it must support a TWIF function). + +When a N5CW device performs an EAP-based access authentication procedure to connect to a trusted WLAN access network, the N5CW device may simultaneously be registered to a 5GC of a PLMN or SNPN. The 5GC registration is performed by the TWIF function (see next clause) in the trusted WLAN access network, on behalf of the N5CW device. The type of EAP authentication procedure, which is used during the 5GC registration to authenticate the N5CW device, is specified in TS 33.501 [29]. In this Release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type. + +##### 4.2.8.5.2 Reference Architecture + +The architecture diagram in Figure 4.2.8.5.2-1 is based on the general 5GS architecture diagrams in clause 4.2 and shows the main network functions required to support 5GC access from N5CW devices. Other network functions are not shown for simplicity. + +![Figure 4.2.8.5.2-1: Non-roaming and LBO Roaming Architecture for supporting 5GC access from N5CW devices. The diagram shows an N5CW device connected to a Trusted WLAN Access Point (TWAP) via the Yt' reference point. The TWAP is connected to a Trusted WLAN Interworking Function (TWIF) via the Yw reference point. Both TWAP and TWIF are part of a Trusted WLAN Access Network. The TWIF connects to the AMF via the N1 and N2 interfaces. The AMF connects to the SMF via the N11 interface. The SMF connects to the UPF via the N4 interface. The UPF connects to the Data Network via the N6 interface. The TWIF also connects to the UPF via the N3 interface.](e05122559f56af5699789b7118d8fe87_img.jpg) + +``` + +graph TD + N5CW[N5CW device] -- Yt' --> TWAP[Trusted WLAN Access Point] + TWAP -- Yw --> TWIF[Trusted WLAN Interworking Function] + subgraph TWAN [Trusted WLAN Access Network] + TWAP + TWIF + end + TWIF -- N1 --> AMF[AMF] + TWIF -- N2 --> AMF + TWIF -- N3 --> UPF[UPF] + AMF -- N11 --> SMF[SMF] + SMF -- N4 --> UPF + UPF -- N6 --> DN((Data Network)) + +``` + +Figure 4.2.8.5.2-1: Non-roaming and LBO Roaming Architecture for supporting 5GC access from N5CW devices. The diagram shows an N5CW device connected to a Trusted WLAN Access Point (TWAP) via the Yt' reference point. The TWAP is connected to a Trusted WLAN Interworking Function (TWIF) via the Yw reference point. Both TWAP and TWIF are part of a Trusted WLAN Access Network. The TWIF connects to the AMF via the N1 and N2 interfaces. The AMF connects to the SMF via the N11 interface. The SMF connects to the UPF via the N4 interface. The UPF connects to the Data Network via the N6 interface. The TWIF also connects to the UPF via the N3 interface. + +**Figure 4.2.8.5.2-1: Non-roaming and LBO Roaming Architecture for supporting 5GC access from N5CW devices** + +The reference architecture in Figure 4.2.8.5.2-1 also supports N5CW device access to the subscribed SNPN or access to the SNPN with credentials owned by Credentials Holder. Other parts of the architecture are the same as defined in clause 5.30.2.9. + +##### 4.2.8.5.3 Network Functions + +**Trusted WLAN Access Point (TWAP):** It is a particular type of a Trusted Non-3GPP Access Point (TNAP) specified in clause 4.2.8.2, that supports a WLAN access technology, e.g. IEEE 802.11. This function is outside the scope of the 3GPP specifications. + +**Trusted WLAN Interworking Function (TWIF):** It provides interworking functionality that enables N5CW devices to access 5GC. The TWIF supports the following functions: + +- Terminates the N1, N2 and N3 interfaces. +- Implements the AMF selection procedure. +- Implements the NAS protocol stack and exchanges NAS messages with the AMF on behalf of the N5CW device. +- On the user plane, it relays protocol data units (PDUs) between the Yw interface and the N3 interface. +- May implement a local mobility anchor within the trusted WLAN access network. + +##### 4.2.8.5.4 Reference Points + +The Yt' and Yw reference points are both outside the scope of the 3GPP specifications. The Yt' reference point transports WLAN messages (e.g. IEEE 802.11 messages), while the Yw reference point: + +- Shall be able to transport authentication messages between the TNAP and the TWIF for enabling authentication of a N5CW device; + +- Shall allow the N5CW device to request and receive IP configuration from the TWIF, including an IP address, e.g. with DHCP. +- Shall support the transport of user-plane traffic for the N5CW device. + +The N1, N2 and N3 reference points are the same reference points defined in clause 4.2.7. + +### 4.2.9 Network Analytics architecture + +The Network Analytics architecture is defined in TS 23.288 [86]. + +### 4.2.10 Architecture Reference Model for ATSSS Support + +In order to support the ATSSS feature, the 5G System Architecture is extended as shown in Figure 4.2.10-1, Figure 4.2.10-2 and Figure 4.2.10-3. The additional functionality that is supported by the UE and the network functions shown in these figures is specified in clause 5.32 below. In summary: + +- The UE supports one or more of the steering functionalities specified in clause 5.32.6, i.e. the MPTCP functionality, the MPQUIC functionality and the ATSSS-LL functionality. Each steering functionality in the UE enables traffic steering, switching and splitting across 3GPP access and non-3GPP access, in accordance with the ATSSS rules provided by the network. The ATSSS-LL functionality is mandatory in the UE for MA PDU Session of type Ethernet. +- The UPF may support the MPTCP Proxy functionality, which communicates with the MPTCP functionality in the UE by using the MPTCP protocol (IETF RFC 8684 [81]), as defined in clause 5.32.6.2.1. +- The UPF may support the MPQUIC Proxy functionality, which communicates with the MPQUIC functionality in the UE by using the QUIC protocol (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]) and its multipath extensions (draft-ietf-quic-multipath [174]), as defined in clause 5.32.6.2.2. +- The UPF may support ATSSS-LL functionality, which is similar to the ATSSS-LL functionality defined for the UE. There is no user plane protocol defined between the ATSSS-LL functionality in the UE and the ATSSS-LL functionality in the UPF. + +NOTE 1: ATSSS-LL functionality is needed in the 5GC for MA PDU Session of type Ethernet. + +- In addition, the UPF supports Performance Measurement Functionality (PMF), which may be used by the UE to obtain access performance measurements (see clause 5.32.5) over the user-plane of 3GPP access and/or over the user-plane of non-3GPP access. +- The AMF, SMF and PCF are extended with new functionality that is further discussed in clause 5.32. + +![Figure 4.2.10-1: Non-roaming and Roaming with Local Breakout architecture for ATSSS support. The diagram shows a User Equipment (UE) connected to 3GPP Access and Non-3GPP Access. The UE contains MPTCP, MPQUIC, ATSSS-LL, and PMF functionalities. The 3GPP Access connects to the AMF via N2 and N1 interfaces. The Non-3GPP Access connects to the AMF via N2 and N1 interfaces. The AMF connects to the SMF via N11. The SMF connects to the PCF via N7 and to the UPF via N4. The UPF contains MPTCP Proxy, MPQUIC Proxy, ATSSS-LL, and PMF functionalities. The UPF connects to the Data Network via N6. The UE also connects to the UPF via N3 interfaces from both 3GPP and Non-3GPP accesses.](ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg) + +Figure 4.2.10-1: Non-roaming and Roaming with Local Breakout architecture for ATSSS support. The diagram shows a User Equipment (UE) connected to 3GPP Access and Non-3GPP Access. The UE contains MPTCP, MPQUIC, ATSSS-LL, and PMF functionalities. The 3GPP Access connects to the AMF via N2 and N1 interfaces. The Non-3GPP Access connects to the AMF via N2 and N1 interfaces. The AMF connects to the SMF via N11. The SMF connects to the PCF via N7 and to the UPF via N4. The UPF contains MPTCP Proxy, MPQUIC Proxy, ATSSS-LL, and PMF functionalities. The UPF connects to the Data Network via N6. The UE also connects to the UPF via N3 interfaces from both 3GPP and Non-3GPP accesses. + +Figure 4.2.10-1: Non-roaming and Roaming with Local Breakout architecture for ATSSS support + +NOTE 2: The interactions between the UE and PCF that may be required for ATSSS control are specified in TS 23.503 [45]. + +NOTE 3: The UPF shown in Figure 4.2.10-1 can be connected via an N9 reference point, instead of the N3 reference point. + +Figure 4.2.10-2 shows the 5G System Architecture for ATSSS support in a roaming case with home-routed traffic and when the UE is registered to the same VPLMN over 3GPP and non-3GPP accesses. In this case, the MPTCP Proxy functionality, the MPQUIC Proxy functionality, the ATSSS-LL functionality and the PMF are located in the H-UPF. + +![Figure 4.2.10-2: Roaming with Home-routed architecture for ATSSS support (UE registered to the same VPLMN).](a5184899f915014fa38608754efcc9c7_img.jpg) + +This diagram illustrates the 5G system architecture for ATSSS support when the UE is registered to the same VPLMN over both 3GPP and non-3GPP accesses. The architecture is divided into VPLMN and HPLMN by a vertical dashed red line. On the UE side, the UE contains MPTCP, MPQUIC, ATSSS-LL, and PMF functionalities. It connects to 3GPP Access and Non-3GPP Access. Both accesses connect to the V-UPF via N3 interfaces. The 3GPP Access also connects to the AMF via N2 and N1 interfaces. The AMF connects to the V-SMF via N11. The V-SMF connects to the H-SMF via N16 and to the V-UPF via N4. The H-SMF connects to the H-PCF via N7 and to the H-UPF via N4. The H-UPF contains MPTCP Proxy, MPQUIC Proxy, ATSSS-LL, and PMF functionalities and connects to the Data Network via N6. The V-UPF and H-UPF are connected via N9 interfaces. + +Figure 4.2.10-2: Roaming with Home-routed architecture for ATSSS support (UE registered to the same VPLMN). + +**Figure 4.2.10-2: Roaming with Home-routed architecture for ATSSS support (UE registered to the same VPLMN)** + +Figure 4.2.10-3 shows the 5G System Architecture for ATSSS support in a roaming case with home-routed traffic and when the UE is registered to a VPLMN over 3GPP access and to HPLMN over non-3GPP access (i.e. the UE is registered to different PLMNs). In this case, the MPTCP Proxy functionality, the MPQUIC functionality, the ATSSS-LL functionality and the PMF are located in the H-UPF. + +![Figure 4.2.10-3: Roaming with Home-routed architecture for ATSSS support (UE registered to different PLMNs).](0d0897dd7f03672d186db9d56ea0d6f5_img.jpg) + +This diagram illustrates the 5G system architecture for ATSSS support when the UE is registered to different PLMNs: VPLMN over 3GPP access and HPLMN over non-3GPP access. The architecture is divided into VPLMN and HPLMN by a vertical dashed red line. On the UE side, the UE contains MPTCP, MPQUIC, ATSSS-LL, and PMF functionalities. It connects to 3GPP Access (in VPLMN) and Non-3GPP Access (in HPLMN). The 3GPP Access connects to the AMF (in VPLMN) via N2 and N1 interfaces. The AMF connects to the V-SMF via N11. The V-SMF connects to the H-SMF via N16 and to the V-UPF via N4. The H-SMF connects to the H-PCF via N7 and to the H-UPF via N4. The H-UPF contains MPTCP Proxy, MPQUIC Proxy, ATSSS-LL, and PMF functionalities and connects to the Data Network via N6. The V-UPF and H-UPF are connected via N9 interfaces. The Non-3GPP Access connects to the H-UPF via N3 and to the AMF (in HPLMN) via N2 and N1 interfaces. The AMF (in HPLMN) connects to the H-SMF via N11. A dashed red line also indicates the boundary between VPLMN and HPLMN for the Non-3GPP access path. + +Figure 4.2.10-3: Roaming with Home-routed architecture for ATSSS support (UE registered to different PLMNs). + +**Figure 4.2.10-3: Roaming with Home-routed architecture for ATSSS support (UE registered to different PLMNs)** + +### 4.2.11 Architecture for 5G multicast-broadcast services + +The architecture for 5G multicast-broadcast services is defined in TS 23.247 [129]. + +### 4.2.12 Architecture for Proximity based Services (ProSe) in 5GS + +The architecture for Proximity based Services (ProSe) in the 5G System is defined in TS 23.304 [128]. + +### 4.2.13 Architecture enhancements for Edge Computing + +The architecture enhancements for edge computing are outlined in clause 5.13 and further described in TS 23.548 [130]. + +### 4.2.14 Architecture for Support of Uncrewed Aerial Systems connectivity, identification and tracking + +The architecture for Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking is defined in TS 23.256 [136]. + +### 4.2.15 Architecture to support WLAN connection using 5G credentials without 5GS registration + +The reference architecture shown with reference point representation in Figure 4.2.15-1 and with Service Based Interface (SBI)-representation in Figure 4.2.15-2, enables a UE to connect to a WLAN access network using its 5GS credentials without registration to 5GS. This architecture is based on the Non-Seamless WLAN Offload Function (NSWOF), which interfaces to the WLAN access network using the SWa' reference point and interfaces to the AUSF using the Nausf SBI. The SWa' reference point corresponds to SWa reference point as defined in TS 23.402 [43] with the difference that SWa' the EAP procedure ensures that the permanent user ID is not visible over the access as defined in TS 33.501 [29] and that SWa' connects the Untrusted non-3GPP IP Access, possibly via 3GPP AAA Proxy, to the NSWOF and that the EAP user ID is a SUCI and not an IMSI. + +The functionality of the NSWOF and the procedures applied for supporting a WLAN connection using 5GS credentials for Non-seamless WLAN offload are further defined in TS 33.501 [29] Annex S. The roaming architectures are shown with reference point representation in Figure 4.2.15-3 and with SBI representation in Figure 4.2.15-4. The architecture in Figure 4.2.15-1 and Figure 4.2.15-2 applies to UEs with PLMN or SNPN credentials. + +NOTE 1: For a UE with SNPN credentials it is assumed that the realm part of UE identifier in SUCI format is defined in a way that enables routing of SWa requests from the WLAN AN to the NSWOF in the SNPN's 5GC. + +The architectures in Figure 4.2.15-3a and Figure 4.2.15-4a apply to UEs with PLMN or SNPN credentials from a CH using UDM. + +The architecture in Figure 4.2.15-3b applies to UEs with SNPN credentials from a CH using AAA Server. In this architecture the UE procedures for access selection for 5G NSWO defined in clause 6.3.12b apply. Except the UE, all NFs in Figure 4.2.15-3b are out of scope of 3GPP. + +The architectures in Figure 4.2.15-3c and Figure 4.2.15-4b apply to UEs with SNPN credentials from a CH using AAA Server via 5GC (NSWOF/AUSF/UDM/NSSAAF). In this architecture the UE procedures for access selection for 5G NSWO defined in clause 6.3.12b apply. + +NOTE 2: How to protect the user identity over the WLAN interface in architecture defined in Figure 4.2.15-3b and Figure 4.2.15-3c is defined in TS 33.501 [29]. + +The UE can also connect to a WLAN access network using 5GS credentials by performing the 5GS registration via Trusted non-3GPP access procedure defined in clause 4.12a.2.2 of TS 23.502 [3]. With this procedure, the UE connects to a WLAN access network using 5GS credentials and simultaneously registers in 5GS. However, the architecture defined in Figure 4.2.15-1, Figure 4.2.15-2, Figure 4.2.15-3 and in Figure 4.2.15-4, enables a UE to connect to a WLAN access network using 5GS credentials but without registration in 5GS. + +If the WLAN is configured as Untrusted Non-3GPP access, in the case that the WLAN supports IEEE 802.1x, the UE may first use the 5G NSWO procedure to obtain a connection with and the local IP address from the WLAN, and any time after that, the UE may initiate the Untrusted Non-3GPP Access to obtain the access to 5GC. + +![Reference architecture to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows a linear flow: UE connected to WLAN access, which is connected to NSWOF via an SWa' interface. NSWOF is connected to AUSF via an N60 interface, and AUSF is connected to UDM via an N13 interface.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +graph LR + UE[UE] --- WLAN[WLAN access] + WLAN -- SWa' --> NSWOF[NSWOF] + NSWOF -- N60 --> AUSF[AUSF] + AUSF -- N13 --> UDM[UDM] + +``` + +Reference architecture to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows a linear flow: UE connected to WLAN access, which is connected to NSWOF via an SWa' interface. NSWOF is connected to AUSF via an N60 interface, and AUSF is connected to UDM via an N13 interface. + +Figure 4.2.15-1: Reference architecture to support authentication for Non-seamless WLAN offload in 5GS + +![Service based reference architecture to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows a vertical stack: UE at the bottom connected to WLAN Access, which is connected to NSWOF. NSWOF, AUSF, and UDM are all connected to a common service interface line labeled Nausf and Nudm respectively.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` + +graph TD + UE[UE] --- WLAN[WLAN Access] + WLAN --- NSWOF[NSWOF] + NSWOF --- SBI((Service Based Interface)) + AUSF[AUSF] --- SBI + UDM[UDM] --- SBI + SBI -.-> Nausf + SBI -.-> Nudm + +``` + +Service based reference architecture to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows a vertical stack: UE at the bottom connected to WLAN Access, which is connected to NSWOF. NSWOF, AUSF, and UDM are all connected to a common service interface line labeled Nausf and Nudm respectively. + +Figure 4.2.15-2: Service based reference architecture to support authentication for Non-seamless WLAN offload in 5GS + +![Roaming reference architectures to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows two scenarios: 1) UE in VPLMN connected to WLAN access, then AAA Proxy, which connects to NSWOF in HPLMN via SWd'. NSWOF connects to AUSF via N60, and AUSF connects to UDM via N13. 2) UE in VPLMN connected to WLAN access, then AAA Proxy, which connects to another AAA Proxy in HPLMN via SWd'. This second AAA Proxy connects to NSWOF via SWd', which then connects to AUSF via N60, and AUSF connects to UDM via N13.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +1) + +``` + +graph LR + subgraph VPLMN + UE1[UE] --- WLAN1[WLAN access] + WLAN1 -- SWa' --> AAA1[AAA Proxy] + end + AAA1 -- SWd' --> NSWOF1[NSWOF] + subgraph HPLMN + NSWOF1 -- N60 --> AUSF1[AUSF] + AUSF1 -- N13 --> UDM1[UDM] + end + +``` + +2) + +``` + +graph LR + subgraph VPLMN + UE2[UE] --- WLAN2[WLAN access] + WLAN2 -- SWa' --> AAA2[AAA Proxy] + end + AAA2 -- SWd' --> AAA3[AAA Proxy] + subgraph HPLMN + AAA3 -- SWd' --> NSWOF2[NSWOF] + NSWOF2 -- N60 --> AUSF2[AUSF] + AUSF2 -- N13 --> UDM2[UDM] + end + +``` + +Roaming reference architectures to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows two scenarios: 1) UE in VPLMN connected to WLAN access, then AAA Proxy, which connects to NSWOF in HPLMN via SWd'. NSWOF connects to AUSF via N60, and AUSF connects to UDM via N13. 2) UE in VPLMN connected to WLAN access, then AAA Proxy, which connects to another AAA Proxy in HPLMN via SWd'. This second AAA Proxy connects to NSWOF via SWd', which then connects to AUSF via N60, and AUSF connects to UDM via N13. + +Figure 4.2.15-3: Roaming reference architectures to support authentication for Non-seamless WLAN offload in 5GS + +![Figure 4.2.15-3a: Reference architectures to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM. Configuration 1 shows UE to WLAN access to AAA Proxy in SNPN, then to NSWOF, AUSF, and UDM in CH. Configuration 2 adds an extra AAA Proxy between the SNPN and NSWOF.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + + graph LR + subgraph SNPN_1 [SNPN] + UE1[UE] --- WLAN1[WLAN access] + WLAN1 --- AAAP1[AAA Proxy] + end + AAAP1 -- Swa' --- NSWOF1[NSWOF] + subgraph CH_1 [CH] + NSWOF1 -- Swd' --- AUSF1[AUSF] + AUSF1 -- N60 --- UDM1[UDM] + end + + subgraph SNPN_2 [SNPN] + UE2[UE] --- WLAN2[WLAN access] + WLAN2 --- AAAP2[AAA Proxy] + end + AAAP2 -- Swa' --- AAAP3[AAA Proxy] + AAAP3 -- Swd' --- NSWOF2[NSWOF] + subgraph CH_2 [CH] + NSWOF2 -- Swd' --- AUSF2[AUSF] + AUSF2 -- N60 --- UDM2[UDM] + end + +``` + +Figure 4.2.15-3a: Reference architectures to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM. Configuration 1 shows UE to WLAN access to AAA Proxy in SNPN, then to NSWOF, AUSF, and UDM in CH. Configuration 2 adds an extra AAA Proxy between the SNPN and NSWOF. + +Figure 4.2.15-3a: Reference architectures to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM + +![Figure 4.2.15-3b: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +``` + + graph LR + subgraph SNPN + UE --- WLAN[WLAN access] + WLAN --- AAAP1[AAA Proxy] + end + AAAP1 -- Swa --- AAAP2[AAA Proxy] + subgraph CH + AAAP2 -- Swd --- AAAS[AAA Server] + end + +``` + +Figure 4.2.15-3b: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server. + +Figure 4.2.15-3b: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server + +![Figure 4.2.15-3c: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +``` + + graph LR + subgraph SNPN + UE --- WLAN[WLAN access] + WLAN --- NSWOF + end + NSWOF -- Swa' --- AUSF + subgraph CH + UDM -- N13 --- AUSF + AUSF -- N60 --- NSSAAF + NSSAAF -- N83 --- AAAP[AAA Proxy] + AAAP -- Swd --- AAAS[AAA Server] + end + +``` + +Figure 4.2.15-3c: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC. + +Figure 4.2.15-3c: Reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC + +NOTE 2: Configuration 2) in Figure 4.2.15-3 and Figure 4.2.15-3a is a deployment variant of configuration 1) + +![Service based Roaming reference architecture to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows a UE connected to a WLAN Access, which is connected to an AAA. The AAA is connected to an NSWOF via the Swd' interface. The NSWOF is connected to an AUSF via the Nausf interface and to a UDM via the Nudm interface. The AAA, NSWOF, AUSF, and UDM are all part of the HPLMN. The WLAN Access and UE are part of the VPLMN.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` +graph TD; UE[UE] --- WA[WLAN Access]; WA --- AAA[AAA]; AAA ---|Swd'| NSWOF[NSWOF]; NSWOF ---|Nausf| AUSF[AUSF]; NSWOF ---|Nudm| UDM[UDM]; +``` + +Service based Roaming reference architecture to support authentication for Non-seamless WLAN offload in 5GS. The diagram shows a UE connected to a WLAN Access, which is connected to an AAA. The AAA is connected to an NSWOF via the Swd' interface. The NSWOF is connected to an AUSF via the Nausf interface and to a UDM via the Nudm interface. The AAA, NSWOF, AUSF, and UDM are all part of the HPLMN. The WLAN Access and UE are part of the VPLMN. + +**Figure 4.2.15-4: Service based Roaming reference architecture to support authentication for Non-seamless WLAN offload in 5GS** + +The SWd' reference point corresponds to the SWd reference point as defined in TS 23.402 [43] with the difference that SWd' connects the 3GPP AAA Proxy, possibly via intermediate 3GPP AAA Proxy, to the NSWOF and that the EAP user ID is a SUCI and not an IMSI. + +In both roaming and non-roaming scenarios, the NSWOF acts towards the WLAN Access as a 3GPP AAA server, with the difference that the EAP user ID is a SUCI and not an IMSI. + +![Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM. The diagram shows a UE connected to a WLAN Access, which is connected to an AAA. The AAA is connected to an NSWOF via the Swd' interface. The NSWOF is connected to an AUSF via the Nausf interface and to a UDM via the Nudm interface. The AAA, NSWOF, AUSF, and UDM are all part of the CH. The WLAN Access and UE are part of the SNP.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +``` +graph TD; UE[UE] --- WA[WLAN Access]; WA --- AAA[AAA]; AAA ---|Swd'| NSWOF[NSWOF]; NSWOF ---|Nausf| AUSF[AUSF]; NSWOF ---|Nudm| UDM[UDM]; +``` + +Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM. The diagram shows a UE connected to a WLAN Access, which is connected to an AAA. The AAA is connected to an NSWOF via the Swd' interface. The NSWOF is connected to an AUSF via the Nausf interface and to a UDM via the Nudm interface. The AAA, NSWOF, AUSF, and UDM are all part of the CH. The WLAN Access and UE are part of the SNP. + +**Figure 4.2.15-4a: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using UDM** + +![Figure 4.2.15-4b: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC. The diagram shows a UE connected to a WLAN Access, which is connected to an NSWOF. The NSWOF is connected to a Service Based Interface (SBI) via the Swa' interface. On the SBI, the NSWOF is connected to AUSF (Nausf), UDM (Nudm), and NSSAAF (Nnssaaf). The AUSF, UDM, and NSSAAF are connected to each other via the SBI. The NSSAAF is connected to an AAA Proxy via the Swd interface. The AAA Proxy is connected to an AAA Server via the Swd interface. The AAA Server is connected to the SBI via the CH interface. The SBI is also connected to the SNPN.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Figure 4.2.15-4b: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC. The diagram shows a UE connected to a WLAN Access, which is connected to an NSWOF. The NSWOF is connected to a Service Based Interface (SBI) via the Swa' interface. On the SBI, the NSWOF is connected to AUSF (Nausf), UDM (Nudm), and NSSAAF (Nnssaaf). The AUSF, UDM, and NSSAAF are connected to each other via the SBI. The NSSAAF is connected to an AAA Proxy via the Swd interface. The AAA Proxy is connected to an AAA Server via the Swd interface. The AAA Server is connected to the SBI via the CH interface. The SBI is also connected to the SNPN. + +**Figure 4.2.15-4b: Service based reference architecture to support authentication for Non-seamless WLAN offload using credentials from Credentials Holder using AAA Server via 5GC** + +### 4.2.16 Architecture to support User Plane Information Exposure via a service-based interface + +As depicted in Figure 4.2.16-1, the 5G System architecture allows user plane information exposure to some NFs via service-based interface in UPF. + +![Figure 4.2.16-1: Architecture to support User Plane Information Exposure via a service-based interface. The diagram shows a UPF (Exposure Service) connected to a Service Based Interface (SBI). The SBI is connected to four Network Functions (NFs): SMF, NWDAF, NEF/AF, and TSNAP/TSCTSF. The UPF (Exposure Service) is connected to the SBI via a service-based interface.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) + +Figure 4.2.16-1: Architecture to support User Plane Information Exposure via a service-based interface. The diagram shows a UPF (Exposure Service) connected to a Service Based Interface (SBI). The SBI is connected to four Network Functions (NFs): SMF, NWDAF, NEF/AF, and TSNAP/TSCTSF. The UPF (Exposure Service) is connected to the SBI via a service-based interface. + +**Figure 4.2.16-1: Architecture to support User Plane Information Exposure via a service-based interface** + +NOTE 1: In this Release of the specification, only NWDAF/DCCF/MFAF, NEF/AF and TSNAP/TSCTSF are considered as the receiver of the UPF event notifications. + +NOTE 2: UPF information exposure is not restricted to SBI interface, i.e. reporting via PFCP over N4 to SMF is still applicable. + +Not all events can be subscribed to UPF directly. The details and constraints for the subscription to UPF event exposure service (i.e. direct vs. indirect) and the information exposed to certain NFs by UPF, as well as the information contained in the event notifications, are defined in clause 5.2.26.2 of TS 23.502 [3] and clause 5.8.2.17. + +### 4.2.17 Architecture for Ranging based services and Sidelink Positioning + +The architecture for Ranging based services and Sidelink Positioning is defined in TS 23.586 [180]. + +## 4.3 Interworking with EPC + +### 4.3.1 Non-roaming architecture + +Figure 4.3.1-1 represents the non-roaming architecture for interworking between 5GS and EPC/E-UTRAN. + +![Figure 4.3.1-1: Non-roaming architecture for interworking between 5GS and EPC/E-UTRAN. The diagram shows two parallel network paths. The left path represents the EPC/E-UTRAN architecture, consisting of a UE connected to an E-UTRAN, which is connected to an MME. The MME is connected to an SGW via S1-MME and S1-U interfaces. The SGW is connected to the HSS + UDM via S6a and S11 interfaces. The right path represents the 5GS architecture, consisting of a UE connected to an NG-RAN, which is connected to an AMF via N1 and N2 interfaces. The AMF is connected to the SMF + PGW-C via N15 and N11 interfaces. The SMF + PGW-C is connected to the UPF + PGW-U via N4. The UPF + PGW-U is connected to the HSS + UDM via N10. The HSS + UDM is also connected to the PCF via N7. The PCF is connected to the SMF + PGW-C via N7. The MME and AMF are connected via the N26 interface. The SGW is connected to the SMF + PGW-C via S5-C and S5-U interfaces.](552328a9daaf3bc0069424b500025880_img.jpg) + +Figure 4.3.1-1: Non-roaming architecture for interworking between 5GS and EPC/E-UTRAN. The diagram shows two parallel network paths. The left path represents the EPC/E-UTRAN architecture, consisting of a UE connected to an E-UTRAN, which is connected to an MME. The MME is connected to an SGW via S1-MME and S1-U interfaces. The SGW is connected to the HSS + UDM via S6a and S11 interfaces. The right path represents the 5GS architecture, consisting of a UE connected to an NG-RAN, which is connected to an AMF via N1 and N2 interfaces. The AMF is connected to the SMF + PGW-C via N15 and N11 interfaces. The SMF + PGW-C is connected to the UPF + PGW-U via N4. The UPF + PGW-U is connected to the HSS + UDM via N10. The HSS + UDM is also connected to the PCF via N7. The PCF is connected to the SMF + PGW-C via N7. The MME and AMF are connected via the N26 interface. The SGW is connected to the SMF + PGW-C via S5-C and S5-U interfaces. + +**Figure 4.3.1-1: Non-roaming architecture for interworking between 5GS and EPC/E-UTRAN** + +NOTE 1: N26 interface is an inter-CN interface between the MME and 5GS AMF in order to enable interworking between EPC and the NG core. Support of N26 interface in the network is optional for interworking. N26 supports subset of the functionalities (essential for interworking) that are supported over S10. + +NOTE 2: PGW-C + SMF and UPF + PGW-U are dedicated for interworking between 5GS and EPC, which are optional and are based on UE MM Core Network Capability and UE subscription. UEs that are not subject to 5GS and EPC interworking may be served by entities not dedicated for interworking, i.e. by either by PGW or SMF/UPF. + +NOTE 3: There can be another UPF (not shown in the figure above) between the NG-RAN and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards an additional UPF, if needed. + +NOTE 4: Figures and procedures in this specification that depict an SGW make no assumption whether the SGW is deployed as a monolithic SGW or as an SGW split into its control-plane and user-plane functionality as described in TS 23.214 [32]. + +### 4.3.2 Roaming architecture + +Figure 4.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GS and EPC/E-UTRAN. + +![Diagram of Local breakout roaming architecture for interworking between 5GS and EPC/E-UTRAN. The diagram shows two network paths separated by a dashed line representing the HPLMN/VPLMN boundary. On the left (EPC/E-UTRAN side), a UE connects to E-UTRAN, which connects to an MME via S1-MME. The MME connects to an SGW via S1-U and S11. The SGW connects to the HSS + UDM via S6a and to the SMF + PGW-C via S5-U. The SMF + PGW-C connects to the h-PCF via N10 and to the UPF + PGW-U via N4. The h-PCF connects to the v-PCF via N24. The v-PCF connects to the AMF via N15. The AMF connects to the NG-RAN via N2 and N3. The NG-RAN connects to the UPF + PGW-U via N11 and to the UE via N1. The UPF + PGW-U connects to the AMF via N8. The HSS + UDM also connects to the AMF via N8.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Diagram of Local breakout roaming architecture for interworking between 5GS and EPC/E-UTRAN. The diagram shows two network paths separated by a dashed line representing the HPLMN/VPLMN boundary. On the left (EPC/E-UTRAN side), a UE connects to E-UTRAN, which connects to an MME via S1-MME. The MME connects to an SGW via S1-U and S11. The SGW connects to the HSS + UDM via S6a and to the SMF + PGW-C via S5-U. The SMF + PGW-C connects to the h-PCF via N10 and to the UPF + PGW-U via N4. The h-PCF connects to the v-PCF via N24. The v-PCF connects to the AMF via N15. The AMF connects to the NG-RAN via N2 and N3. The NG-RAN connects to the UPF + PGW-U via N11 and to the UE via N1. The UPF + PGW-U connects to the AMF via N8. The HSS + UDM also connects to the AMF via N8. + +**Figure 4.3.2-1: Local breakout roaming architecture for interworking between 5GS and EPC/E-UTRAN** + +NOTE 1: There can be another UPF (not shown in the figure above) between the NG-RAN and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed. + +NOTE 2: S9 interface from EPC is not required since no known deployment exists. + +![Diagram of home-routed roaming architecture for interworking between 5GS and EPC/E-UTRAN. The diagram shows two network paths separated by a dashed line representing the HPLMN/VPLMN boundary. On the left (EPC side), a UE connects to E-UTRAN, which connects to an MME via S1-MME. The MME connects to an SGW via S1-U, and the SGW connects to the HSS + UDM via S6a. On the right (5GS side), a UE connects to NG-RAN, which connects to an AMF via N1. The AMF connects to a v-SMF via N11, and the v-SMF connects to a UPF via N4. The UPF connects to the HSS + UDM via N16. The MME and AMF are interconnected via N26. Other components include h-PCF, SMF + PGW-C, UPF + PGW-U, and v-PCF, with various interfaces like N10, N7, N4, N8, N9, N15, N24, and S8-C/U.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Diagram of home-routed roaming architecture for interworking between 5GS and EPC/E-UTRAN. The diagram shows two network paths separated by a dashed line representing the HPLMN/VPLMN boundary. On the left (EPC side), a UE connects to E-UTRAN, which connects to an MME via S1-MME. The MME connects to an SGW via S1-U, and the SGW connects to the HSS + UDM via S6a. On the right (5GS side), a UE connects to NG-RAN, which connects to an AMF via N1. The AMF connects to a v-SMF via N11, and the v-SMF connects to a UPF via N4. The UPF connects to the HSS + UDM via N16. The MME and AMF are interconnected via N26. Other components include h-PCF, SMF + PGW-C, UPF + PGW-U, and v-PCF, with various interfaces like N10, N7, N4, N8, N9, N15, N24, and S8-C/U. + +Figure 4.3.2-2: Home-routed roaming architecture for interworking between 5GS and EPC/E-UTRAN + +### 4.3.3 Interworking between 5GC via non-3GPP access and E-UTRAN connected to EPC + +#### 4.3.3.1 Non-roaming architecture + +Figure 4.3.3-1 represents the non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. + +![Figure 4.3.3.1-1: Non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. The diagram shows two User Equipment (UE) units connected to different access networks. The left UE is connected to E-UTRAN, which is connected to an MME. The MME is connected to an SGW via S1-MME and S1-U interfaces. The SGW is connected to the HSS + UDM via S6a and S11 interfaces. The HSS + UDM is connected to the PCF via N10. The PCF is connected to the SMF + PGW-C via N7. The SMF + PGW-C is connected to the UPF + PGW-U via N4. The UPF + PGW-U is connected to the AMF via N11. The AMF is connected to the N3IWF / TNGF via N2 and N3. The N3IWF / TNGF is connected to the right UE via N1. The AMF is also connected to the HSS + UDM via N8 and to the PCF via N15. The SMF + PGW-C is also connected to the SGW via S5-C and S5-U interfaces.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Figure 4.3.3.1-1: Non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. The diagram shows two User Equipment (UE) units connected to different access networks. The left UE is connected to E-UTRAN, which is connected to an MME. The MME is connected to an SGW via S1-MME and S1-U interfaces. The SGW is connected to the HSS + UDM via S6a and S11 interfaces. The HSS + UDM is connected to the PCF via N10. The PCF is connected to the SMF + PGW-C via N7. The SMF + PGW-C is connected to the UPF + PGW-U via N4. The UPF + PGW-U is connected to the AMF via N11. The AMF is connected to the N3IWF / TNGF via N2 and N3. The N3IWF / TNGF is connected to the right UE via N1. The AMF is also connected to the HSS + UDM via N8 and to the PCF via N15. The SMF + PGW-C is also connected to the SGW via S5-C and S5-U interfaces. + +**Figure 4.3.3.1-1: Non-roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN** + +NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards an additional UPF, if needed. + +NOTE 2: N26 interface is not precluded, but it is not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. + +#### 4.3.3.2 Roaming architecture + +Figure 4.3.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. + +![Diagram of Local breakout roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. The diagram shows two network paths separated by a dashed line representing the HPLMN/VPLMN boundary. On the left (EPC/E-UTRAN side), a UE connects to E-UTRAN, which connects to an MME via S1-MME. The MME connects to an SGW via S1-U and S11. The SGW connects to the UPF + PGW-U via S5-U. The UPF + PGW-U connects to the SMF + PGW-C via N4. The SMF + PGW-C connects to the v-PCF via N7 and to the AMF via N15. The v-PCF connects to the h-PCF via N24. The h-PCF connects to the HSS + UDM via N10. The HSS + UDM connects to the AMF via N8. On the right (5GC side), the AMF connects to the N3IWF / TNGF via N2 and N1. The N3IWF / TNGF connects to a UE via N3. The UPF + PGW-U also connects to the N3IWF / TNGF via N11. The HPLMN/VPLMN boundary is indicated by a dashed line between the HPLMN and VPLMN sections. The S6a interface is shown between the HPLMN and the SGW.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Diagram of Local breakout roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. The diagram shows two network paths separated by a dashed line representing the HPLMN/VPLMN boundary. On the left (EPC/E-UTRAN side), a UE connects to E-UTRAN, which connects to an MME via S1-MME. The MME connects to an SGW via S1-U and S11. The SGW connects to the UPF + PGW-U via S5-U. The UPF + PGW-U connects to the SMF + PGW-C via N4. The SMF + PGW-C connects to the v-PCF via N7 and to the AMF via N15. The v-PCF connects to the h-PCF via N24. The h-PCF connects to the HSS + UDM via N10. The HSS + UDM connects to the AMF via N8. On the right (5GC side), the AMF connects to the N3IWF / TNGF via N2 and N1. The N3IWF / TNGF connects to a UE via N3. The UPF + PGW-U also connects to the N3IWF / TNGF via N11. The HPLMN/VPLMN boundary is indicated by a dashed line between the HPLMN and VPLMN sections. The S6a interface is shown between the HPLMN and the SGW. + +**Figure 4.3.3.2-1: Local breakout roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN** + +NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed. + +NOTE 2: S9 interface from EPC is not required since no known deployment exists. + +NOTE 3: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. + +![Figure 4.3.3.2-2: Home-routed roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. The diagram shows two network domains separated by a dashed line: HPLMN (Home PLMN) above and VPLMN (Visited PLMN) below. In the HPLMN, the core network consists of HSS + UDM, h-PCF, SMF + PGW-C, and UPF + PGW-U. In the VPLMN, the core network consists of SGW, v-SMF, UPF, v-PCF, and AMF. On the left, an E-UTRAN access network connects to an MME, which is connected to a UE. The MME connects to the SGW via S1-U and S1-MME interfaces. The SGW connects to the UPF + PGW-U via S8-U and S8-C interfaces. The UPF + PGW-U connects to the v-SMF via N16 and N9 interfaces. The v-SMF connects to the AMF via N4 and N11 interfaces. The AMF connects to the N3IWF / TNGF via N2 and N1 interfaces, which in turn connects to a UE. The AMF also connects to the v-PCF via N15. The v-PCF connects to the UPF via N11. The UPF connects to the N3IWF / TNGF via N3. The SMF + PGW-C connects to the h-PCF via N7 and to the UPF + PGW-U via N4. The h-PCF connects to the HSS + UDM via N10. The HSS + UDM connects to the v-PCF via N8. The SMF + PGW-C also connects to the SGW via S11. The HPLMN/VPLMN boundary is indicated by a dashed line between the SGW and the UPF + PGW-U.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +Figure 4.3.3.2-2: Home-routed roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. The diagram shows two network domains separated by a dashed line: HPLMN (Home PLMN) above and VPLMN (Visited PLMN) below. In the HPLMN, the core network consists of HSS + UDM, h-PCF, SMF + PGW-C, and UPF + PGW-U. In the VPLMN, the core network consists of SGW, v-SMF, UPF, v-PCF, and AMF. On the left, an E-UTRAN access network connects to an MME, which is connected to a UE. The MME connects to the SGW via S1-U and S1-MME interfaces. The SGW connects to the UPF + PGW-U via S8-U and S8-C interfaces. The UPF + PGW-U connects to the v-SMF via N16 and N9 interfaces. The v-SMF connects to the AMF via N4 and N11 interfaces. The AMF connects to the N3IWF / TNGF via N2 and N1 interfaces, which in turn connects to a UE. The AMF also connects to the v-PCF via N15. The v-PCF connects to the UPF via N11. The UPF connects to the N3IWF / TNGF via N3. The SMF + PGW-C connects to the h-PCF via N7 and to the UPF + PGW-U via N4. The h-PCF connects to the HSS + UDM via N10. The HSS + UDM connects to the v-PCF via N8. The SMF + PGW-C also connects to the SGW via S11. The HPLMN/VPLMN boundary is indicated by a dashed line between the SGW and the UPF + PGW-U. + +**Figure 4.3.3.2-2: Home-routed roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN** + +NOTE 4: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. + +### 4.3.4 Interworking between ePDG connected to EPC and 5GS + +#### 4.3.4.1 Non-roaming architecture + +Figure 4.3.4.1-1 represents the non-roaming architecture for interworking between ePDG/EPC and 5GS. + +![Diagram of non-roaming architecture for interworking between ePDG/EPC and 5GS. It shows a UE connected to an ePDG, which is connected to a 3GPP AAA server and an SMF + PGW-C via S2b interfaces. The 3GPP AAA server is also connected to the SMF + PGW-C via S6b. The SMF + PGW-C is connected to a UPF + PGW-U via N4, and to an AMF via N15 and N11. The UPF + PGW-U is connected to the AMF via N3. The AMF is connected to an NG-RAN, which is connected to another UE. The NG-RAN is also connected to the AMF via N2 and N1. The AMF is connected to the SMF + PGW-C via N8. The SMF + PGW-C is connected to a PCF via N7, and the PCF is connected to the HSS + UDM via N10.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Diagram of non-roaming architecture for interworking between ePDG/EPC and 5GS. It shows a UE connected to an ePDG, which is connected to a 3GPP AAA server and an SMF + PGW-C via S2b interfaces. The 3GPP AAA server is also connected to the SMF + PGW-C via S6b. The SMF + PGW-C is connected to a UPF + PGW-U via N4, and to an AMF via N15 and N11. The UPF + PGW-U is connected to the AMF via N3. The AMF is connected to an NG-RAN, which is connected to another UE. The NG-RAN is also connected to the AMF via N2 and N1. The AMF is connected to the SMF + PGW-C via N8. The SMF + PGW-C is connected to a PCF via N7, and the PCF is connected to the HSS + UDM via N10. + +**Figure 4.3.4.1-1: Non-roaming architecture for interworking between ePDG/EPC and 5GS** + +NOTE 1: The details of the interfaces between the UE and the ePDG, and between EPC nodes (i.e. SWm, SWx, S2b and S6b), are documented in TS 23.402 [43]. + +NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502 [3]). + +#### 4.3.4.2 Roaming architectures + +Figure 4.3.4.2-1 represents the Roaming architecture with local breakout and Figure 4.3.4.2-2 represents the Roaming architecture with home-routed traffic for interworking between ePDG/EPC and 5GS. + +![Diagram of Local breakout roaming architecture for interworking between ePDG/EPC and 5GS. The diagram shows two network domains separated by a dashed line: HPLMN/VPLMN on the left and 5GS on the right. On the left, a UE connects to an ePDG, which connects to a 3GPP AAA proxy via SWm. The 3GPP AAA proxy connects to a 3GPP AAA server via SWd and to an SMF + PGW-C via S6b. The 3GPP AAA server connects to an HSS + UDM via SWx. The HSS + UDM connects to an h-PCF via N10. The h-PCF connects to a v-PCF via N24. The v-PCF connects to an AMF via N15. The SMF + PGW-C connects to the AMF via N11 and to the UPF + PGW-U via N4. The UPF + PGW-U connects to the AMF via N3. The AMF connects to an NG-RAN via N2, which connects to a UE via N1. The HSS + UDM also connects to the AMF via N8. The ePDG also connects to the SMF + PGW-C via S2b-C and S2b-U interfaces.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +Diagram of Local breakout roaming architecture for interworking between ePDG/EPC and 5GS. The diagram shows two network domains separated by a dashed line: HPLMN/VPLMN on the left and 5GS on the right. On the left, a UE connects to an ePDG, which connects to a 3GPP AAA proxy via SWm. The 3GPP AAA proxy connects to a 3GPP AAA server via SWd and to an SMF + PGW-C via S6b. The 3GPP AAA server connects to an HSS + UDM via SWx. The HSS + UDM connects to an h-PCF via N10. The h-PCF connects to a v-PCF via N24. The v-PCF connects to an AMF via N15. The SMF + PGW-C connects to the AMF via N11 and to the UPF + PGW-U via N4. The UPF + PGW-U connects to the AMF via N3. The AMF connects to an NG-RAN via N2, which connects to a UE via N1. The HSS + UDM also connects to the AMF via N8. The ePDG also connects to the SMF + PGW-C via S2b-C and S2b-U interfaces. + +**Figure 4.3.4.2-1: Local breakout roaming architecture for interworking between ePDG/EPC and 5GS** + +NOTE 1: The details of the interfaces between the UE and the ePDG, and between EPC nodes (i.e. SWm, SWd, SWx, S2b and S6b), are documented in TS 23.402 [43]. + +NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502 [3]). + +![Figure 4.3.4.2-2: Home-routed roaming architecture for interworking between ePDG/EPC and 5GS. The diagram shows a UE connected to an ePDG, which is connected to a 3GPP AAA proxy. The 3GPP AAA proxy is connected to a 3GPP AAA server. The 3GPP AAA server is connected to an HSS + UDM via the SWx interface. The HSS + UDM is connected to an h-PCF via the N10 interface. The h-PCF is connected to an SMF + PGW-C via the N7 interface. The SMF + PGW-C is connected to a UPF + PGW-U via the N4 interface. The SMF + PGW-C is also connected to a 3GPP AAA server via the S6b interface. The SMF + PGW-C is connected to a v-SMF via the N24 interface. The v-SMF is connected to a UPF via the N9 interface. The UPF is connected to an AMF via the N11 interface. The AMF is connected to an NG-RAN via the N3 interface. The NG-RAN is connected to a UE via the N1 interface. The AMF is also connected to a v-PCF via the N15 interface. The v-PCF is connected to the SMF + PGW-C via the N8 interface. The ePDG is connected to the SMF + PGW-C via the S2b-C and S2b-U interfaces. The 3GPP AAA proxy is connected to the SMF + PGW-C via the SWm interface. The 3GPP AAA server is connected to the SMF + PGW-C via the SWd interface. A dashed line separates the HPLMN (Home PLMN) from the VPLMN (Visited PLMN). The HPLMN includes the UE, ePDG, 3GPP AAA proxy, 3GPP AAA server, HSS + UDM, h-PCF, SMF + PGW-C, and UPF + PGW-U. The VPLMN includes the v-SMF, UPF, v-PCF, AMF, NG-RAN, and the second UE.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +Figure 4.3.4.2-2: Home-routed roaming architecture for interworking between ePDG/EPC and 5GS. The diagram shows a UE connected to an ePDG, which is connected to a 3GPP AAA proxy. The 3GPP AAA proxy is connected to a 3GPP AAA server. The 3GPP AAA server is connected to an HSS + UDM via the SWx interface. The HSS + UDM is connected to an h-PCF via the N10 interface. The h-PCF is connected to an SMF + PGW-C via the N7 interface. The SMF + PGW-C is connected to a UPF + PGW-U via the N4 interface. The SMF + PGW-C is also connected to a 3GPP AAA server via the S6b interface. The SMF + PGW-C is connected to a v-SMF via the N24 interface. The v-SMF is connected to a UPF via the N9 interface. The UPF is connected to an AMF via the N11 interface. The AMF is connected to an NG-RAN via the N3 interface. The NG-RAN is connected to a UE via the N1 interface. The AMF is also connected to a v-PCF via the N15 interface. The v-PCF is connected to the SMF + PGW-C via the N8 interface. The ePDG is connected to the SMF + PGW-C via the S2b-C and S2b-U interfaces. The 3GPP AAA proxy is connected to the SMF + PGW-C via the SWm interface. The 3GPP AAA server is connected to the SMF + PGW-C via the SWd interface. A dashed line separates the HPLMN (Home PLMN) from the VPLMN (Visited PLMN). The HPLMN includes the UE, ePDG, 3GPP AAA proxy, 3GPP AAA server, HSS + UDM, h-PCF, SMF + PGW-C, and UPF + PGW-U. The VPLMN includes the v-SMF, UPF, v-PCF, AMF, NG-RAN, and the second UE. + +**Figure 4.3.4.2-2: Home-routed roaming architecture for interworking between ePDG/EPC and 5GS** + +NOTE 1: The details of the interfaces between the UE and the ePDG, and between EPC nodes (i.e. SWm, SWd, SWx, S2b and S6b), are documented in TS 23.402 [43]. + +NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502 [3]). + +### 4.3.5 Service Exposure in Interworking Scenarios + +#### 4.3.5.1 Non-roaming architecture + +Figure 4.3.5.1-1 shows the non-roaming architecture for Service Exposure for EPC-5GC Interworking. If the UE is capable of mobility between EPS and 5GS, the network is expected to associate the UE with an SCEF+NEF node for Service Capability Exposure. + +![Figure 4.3.5.1 1: Non-roaming Service Exposure Architecture for EPC-5GC Interworking. The diagram shows a 'TRUST DOMAIN' containing two 'SCEF+NEF' units. Each unit has an 'API Set' connected to an 'AF/AS' via 'N33 and T8' interfaces. Below each 'SCEF+NEF' unit, there are 'EPC Interface (See Note 2)' connections to 'EPC node 1' and 'EPC node 2' (or 'EPC node n-1' and 'EPC node n'), and '5GC Interface (See Note 3)' connections to 'NF 1' and 'NF 2' (or 'NF n-1' and 'NF n'). An additional 'AF/AS' unit is shown above the central '...' indicating multiple such units.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Figure 4.3.5.1 1: Non-roaming Service Exposure Architecture for EPC-5GC Interworking. The diagram shows a 'TRUST DOMAIN' containing two 'SCEF+NEF' units. Each unit has an 'API Set' connected to an 'AF/AS' via 'N33 and T8' interfaces. Below each 'SCEF+NEF' unit, there are 'EPC Interface (See Note 2)' connections to 'EPC node 1' and 'EPC node 2' (or 'EPC node n-1' and 'EPC node n'), and '5GC Interface (See Note 3)' connections to 'NF 1' and 'NF 2' (or 'NF n-1' and 'NF n'). An additional 'AF/AS' unit is shown above the central '...' indicating multiple such units. + +**Figure 4.3.5.1 1: Non-roaming Service Exposure Architecture for EPC-5GC Interworking** + +NOTE 1: In Figure 4.3.5.1-1, Trust domain for SCEF+NEF is same as Trust domain for SCEF as defined in TS 23.682 [36]. + +NOTE 2: In Figure 4.3.5.1-1, EPC Interface represents southbound interfaces between SCEF and EPC nodes e.g. the S6t interface between SCEF and HSS, the T6a interface between SCEF and MME, etc. All southbound interfaces from SCEF are defined in TS 23.682 [36] and are not shown for the sake of simplicity. + +NOTE 3: In Figure 4.3.5.1-1, 5GC Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity. + +NOTE 4: Interaction between the SCEF and NEF within the combined SCEF+NEF is required. For example, when the SCEF+NEF supports monitoring APIs, the SCEF and NEF need to share context and state information on a UE's configured monitoring events if the UE moves between from EPC and 5GC. + +NOTE 5: The north-bound APIs which can be supported by an EPC or 5GC network are discovered by the SCEF+NEF node via the CAPIF function and/or via local configuration of the SCEF+NEF node. Different sets of APIs can be supported by the two network types. + +#### 4.3.5.2 Roaming architectures + +Figure 4.3.5.2-1 represents the roaming architecture for Service Exposure for EPC-5GC Interworking. This architecture is applicable to both the home routed roaming and local breakout roaming. + +![Figure 4.3.5.2-1: Roaming Service Exposure Architecture for EPC-5GC Interworking. The diagram illustrates the architecture for service exposure during roaming between an EPC and a 5GC. It shows two main domains: the TRUST DOMAIN (top) and the H-PLMN/V-PLMN (bottom). In the TRUST DOMAIN, AF/AS (Application Functions/AS) connect to an API Set, which in turn connects to an SCEF+NEF. The SCEF+NEF connects to various network elements: EPC nodes, HSS (via S6t), NFs, UDM (via Nudm), and AMF (via N51). The SCEF+NEF also connects to an IWK-SCEF, which connects to EPC nodes. The IWK-SCEF connects to the H-PLMN/V-PLMN via an EPC interface. In the H-PLMN/V-PLMN, the SCEF+NEF connects to EPC nodes, NFs, UDM (via Nudm), and AMF (via N51). The SCEF+NEF also connects to the AF/AS via N33 and T8 interfaces. The diagram is divided into two parts by a dashed line, with the top part representing the TRUST DOMAIN and the bottom part representing the H-PLMN/V-PLMN.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +Figure 4.3.5.2-1: Roaming Service Exposure Architecture for EPC-5GC Interworking. The diagram illustrates the architecture for service exposure during roaming between an EPC and a 5GC. It shows two main domains: the TRUST DOMAIN (top) and the H-PLMN/V-PLMN (bottom). In the TRUST DOMAIN, AF/AS (Application Functions/AS) connect to an API Set, which in turn connects to an SCEF+NEF. The SCEF+NEF connects to various network elements: EPC nodes, HSS (via S6t), NFs, UDM (via Nudm), and AMF (via N51). The SCEF+NEF also connects to an IWK-SCEF, which connects to EPC nodes. The IWK-SCEF connects to the H-PLMN/V-PLMN via an EPC interface. In the H-PLMN/V-PLMN, the SCEF+NEF connects to EPC nodes, NFs, UDM (via Nudm), and AMF (via N51). The SCEF+NEF also connects to the AF/AS via N33 and T8 interfaces. The diagram is divided into two parts by a dashed line, with the top part representing the TRUST DOMAIN and the bottom part representing the H-PLMN/V-PLMN. + +**Figure 4.3.5.2-1: Roaming Service Exposure Architecture for EPC-5GC Interworking** + +NOTE: Figure 4.3.5.2-1 does not include all the interfaces, and network elements or network functions that may be connected to SCEF+NEF. + +## 4.4 Specific services + +### 4.4.1 Public Warning System + +The Public Warning System architecture for 5G System is specified in TS 23.041 [46]. + +### 4.4.2 SMS over NAS + +#### 4.4.2.0 General + +This clause introduces legacy SMS over NAS architecture, in which the interfaces between SMSF/UDM and SMS-GMSC/SMS-IWMSC/IP-SM-GW/SMS Router are still based on legacy protocol (i.e. MAP or Diameter). + +The SBI-based SMS architecture and interfaces are specified in TS 23.540 [142]. + +#### 4.4.2.1 Architecture to support SMS over NAS + +Figure 4.4.2.1-1 shows the non-roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane. + +![Figure 4.4.2.1-1: Non-roaming System Architecture for SMS over NAS. This diagram shows a UE connected to an AMF via the N1 interface. The AMF is connected to a Service Based Interface (SBI) labeled Namf. On the SBI, the AMF connects to the SMSF via the Nsmssf interface and to the UDM via the Nudm interface. The SMSF is connected to an IP-SM-GW and to an SMS-GMSC/IWMSC SMS Router. The UDM is also connected to an SMS-GMSC/IWMSC SMS Router.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +Figure 4.4.2.1-1: Non-roaming System Architecture for SMS over NAS. This diagram shows a UE connected to an AMF via the N1 interface. The AMF is connected to a Service Based Interface (SBI) labeled Namf. On the SBI, the AMF connects to the SMSF via the Nsmssf interface and to the UDM via the Nudm interface. The SMSF is connected to an IP-SM-GW and to an SMS-GMSC/IWMSC SMS Router. The UDM is also connected to an SMS-GMSC/IWMSC SMS Router. + +**Figure 4.4.2.1-1: Non-roaming System Architecture for SMS over NAS** + +Figure 4.4.2.1-2 shows the non-roaming architecture to support SMS over NAS using the reference point representation. + +![Figure 4.4.2.1-2: Non-roaming System Architecture for SMS over NAS in reference point representation. This diagram shows a UE connected to an AMF via the N1 interface. The AMF is connected to the UDM via the N8 interface and to the SMSF (SMS Function) via the N20 interface. The UDM is connected to the SMSF via the N21 interface and to an SMS-GMSC/IWMSC SMS Router. The SMSF is connected to an IP-SM-GW and to an SMS-GMSC/IWMSC SMS Router.](e05434e963901d7e9c0bf5a6758200ed_img.jpg) + +Figure 4.4.2.1-2: Non-roaming System Architecture for SMS over NAS in reference point representation. This diagram shows a UE connected to an AMF via the N1 interface. The AMF is connected to the UDM via the N8 interface and to the SMSF (SMS Function) via the N20 interface. The UDM is connected to the SMSF via the N21 interface and to an SMS-GMSC/IWMSC SMS Router. The SMSF is connected to an IP-SM-GW and to an SMS-GMSC/IWMSC SMS Router. + +**Figure 4.4.2.1-2: Non-roaming System Architecture for SMS over NAS in reference point representation** + +NOTE 1: SMS Function (SMSF) may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040 [5]. + +NOTE 2: UDM may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040 [5]. + +NOTE 3: Each UE is associated with only one SMS Function in the registered PLMN. + +NOTE 4: SMSF re-allocation while the UE is in RM-REGISTERED state in the serving PLMN is not supported in this Release of the specification. When serving AMF is re-allocated for a given UE, the source AMF includes SMSF identifier as part of UE context transfer to target AMF. If the target AMF, e.g. in the case of inter-PLMN mobility, detects that no SMSF has been selected in the serving PLMN, then the AMF performs SMSF selection as specified in clause 6.3.10. + +NOTE 5: To support MT SMS domain selection by IP-SM-GW/SMS Router, IP-SM-GW/SMS Router may connect to SGs MSC, MME and SMSF via one of the standardized interfaces as shown in TS 23.040 [5]. + +Figure 4.4.2.1-3 shows the roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane. + +![Figure 4.4.2.1-3: Roaming architecture for SMS over NAS. The diagram shows a UE connected to an AMF via N1. The AMF is connected to an SMSF via Nsmf. The SMSF is connected to an IP-SM-GW and an SMS-GMSC/IWMSC SMS Router. The AMF is also connected to a UDM via Namf. The UDM is connected to an SMS-GMSC/IWMSC SMS Router. The diagram is split into VPLMN and HPLMN by a dashed line.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +graph TD + subgraph VPLMN + UE[UE] -- N1 --> AMF[AMF] + AMF -- Nsmf --> SMSF[SMSF] + AMF -- Namf --> UDM[UDM] + end + subgraph HPLMN + SMSF --> IP_SM_GW[to/from IP-SM-GW] + SMSF --> SMS_GMSC[SMS-GMSC/IWMSC SMS Router] + UDM --> SMS_GMSC_2[SMS-GMSC/IWMSC SMS Router] + end + +``` + +Figure 4.4.2.1-3: Roaming architecture for SMS over NAS. The diagram shows a UE connected to an AMF via N1. The AMF is connected to an SMSF via Nsmf. The SMSF is connected to an IP-SM-GW and an SMS-GMSC/IWMSC SMS Router. The AMF is also connected to a UDM via Namf. The UDM is connected to an SMS-GMSC/IWMSC SMS Router. The diagram is split into VPLMN and HPLMN by a dashed line. + +**Figure 4.4.2.1-3: Roaming architecture for SMS over NAS** + +Figure 4.4.2.1-4 shows the roaming architecture to support SMS over NAS using the reference point representation. + +![Figure 4.4.2.1-4: Roaming architecture for SMS over NAS in reference point representation. The diagram shows a UE connected to an AMF via N1. The AMF is connected to an SMSF (SMS Function) via N20. The AMF is also connected to a UDM via N8. The SMSF is connected to a UDM via N21. The SMSF is also connected to an IP-SM-GW and an SMS-GMSC/IWMSC SMS Router. The diagram is split into VPLMN and HPLMN by a dashed line.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` + +graph TD + subgraph VPLMN + UE[UE] -- N1 --> AMF[AMF] + AMF -- N20 --> SMSF[SMSF (SMS Function)] + AMF -- N8 --> UDM[UDM] + end + subgraph HPLMN + SMSF -- N21 --> UDM + SMSF --> IP_SM_GW[to/from IP-SM-GW] + SMSF --> SMS_GMSC[SMS-GMSC/IWMSC SMS Router] + end + +``` + +Figure 4.4.2.1-4: Roaming architecture for SMS over NAS in reference point representation. The diagram shows a UE connected to an AMF via N1. The AMF is connected to an SMSF (SMS Function) via N20. The AMF is also connected to a UDM via N8. The SMSF is connected to a UDM via N21. The SMSF is also connected to an IP-SM-GW and an SMS-GMSC/IWMSC SMS Router. The diagram is split into VPLMN and HPLMN by a dashed line. + +**Figure 4.4.2.1-4: Roaming architecture for SMS over NAS in reference point representation** + +#### 4.4.2.2 Reference point to support SMS over NAS + +**N1:** Reference point for SMS transfer between UE and AMF via NAS. + +Following reference points are realized by service based interfaces: + +**N8:** Reference point for SMS Subscription data retrieval between AMF and UDM. + +**N20:** Reference point for SMS transfer between AMF and SMS Function. + +**N21:** Reference point for SMS Function address registration management and SMS Management Subscription data retrieval between SMS Function and UDM. + +#### 4.4.2.3 Service based interface to support SMS over NAS + +**Nsmf:** Service-based interface exhibited by SMSF. + +### 4.4.3 IMS support + +IMS support for 5GC is defined in TS 23.228 [15]. + +The 5G System architecture supports N5 interface between PCF and P-CSCF and supports Rx interface between PCF and P-CSCF, to enable IMS service. See TS 23.228 [15], TS 23.503 [45] and TS 23.203 [4]. + +NOTE 1: Rx support between PCF and P-CSCF is for backwards compatibility for early deployments using Diameter between IMS and 5GC functions. + +NOTE 2: When service based interfaces are used between the PCF and P-CSCF in the same PLMN, the P-CSCF performs the functions of a trusted AF in the 5GC. + +### 4.4.4 Location services + +#### 4.4.4.1 Architecture to support Location Services + +Location Service feature is optional and applicable to both regulatory services and commercial services in this Release of the specification. The non-roaming and roaming architecture to support Location Services are defined in clause 4.2 of TS 23.273 [87]. + +#### 4.4.4.2 Reference point to support Location Services + +The reference points to support Location Services are defined in clause 4.4 of TS 23.273 [87]. + +#### 4.4.4.3 Service Based Interfaces to support Location Services + +The Service Based Interfaces to support Location Services are defined in clause 4.5 of TS 23.273 [87]. + +### 4.4.5 Application Triggering Services + +See clause 5.2.6.1 of TS 23.502 [3]. + +Application trigger message contains information that allows the network to route the message to the appropriate UE and the UE to route the message to the appropriate application. The information destined to the application, excluding the information to route it, is referred to as the Trigger payload. The Trigger payload is implementation specific. + +NOTE: The application in the UE may perform actions indicated by the Trigger payload when the Triggered payload is received at the UE. For example initiation of immediate or later communication with the application server based on the information contained in the Trigger payload, which includes the PDU Session Establishment procedure if the related PDU Session is not already established. + +### 4.4.6 5G LAN-type Services + +#### 4.4.6.1 User plane architecture to support 5G LAN-type service + +The general User Plane architectures described in clause 4.2.3 and clause 4.2.4 apply to 5G LAN-type services, with the additional options described in this clause. + +Figure 4.4.6.1-1 depicts the non-roaming user plane architecture to support 5G LAN-type service using local switch. + +![Diagram of local-switch based user plane architecture in non-roaming scenario. Two User Equipment (UE) units, UE 1 and UE 2, are connected to separate Radio Access Network (RAN) units. Each RAN is connected via an N3 interface to an intermediate UPF (I-UPF). Both I-UPFs are then connected via N9 interfaces to a single PSA UPF, which is labeled as a 'local switch'.](fd9522380f09785d1f781cfc81b3d56e_img.jpg) + +``` + +graph LR + UE1[UE 1] --- RAN1[(R)AN] + RAN1 -- N3 --> IUPF1[I-UPF] + UE2[UE 2] --- RAN2[(R)AN] + RAN2 -- N3 --> IUPF2[I-UPF] + IUPF1 -- N9 --> PSAUPF[PSA UPF +(local switch)] + IUPF2 -- N9 --> PSAUPF + +``` + +Diagram of local-switch based user plane architecture in non-roaming scenario. Two User Equipment (UE) units, UE 1 and UE 2, are connected to separate Radio Access Network (RAN) units. Each RAN is connected via an N3 interface to an intermediate UPF (I-UPF). Both I-UPFs are then connected via N9 interfaces to a single PSA UPF, which is labeled as a 'local switch'. + +**Figure 4.4.6.1-1: Local-switch based user plane architecture in non-roaming scenario** + +Figure 4.4.6.1-2 depicts the non-roaming user plane architecture to support 5G LAN-type service using N19 tunnel. + +![Diagram of N19-based user plane architecture in non-roaming scenario. Two User Equipment (UE) units, UE 1 and UE 2, are connected to their respective (R)AN units. Each (R)AN is connected to an I-UPF via an N3 interface. The I-UPFs are connected to a PSA via an N9 interface. The PSAs are interconnected by an N19 interface.](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +``` + +graph LR + UE1[UE 1] --- RAN1[(R)AN] + RAN1 -- N3 --> IUPF1[I-UPF] + IUPF1 -- N9 --> PSA1[PSA] + UE2[UE 2] --- RAN2[(R)AN] + RAN2 -- N3 --> IUPF2[I-UPF] + IUPF2 -- N9 --> PSA2[PSA] + PSA1 -- N19 --> PSA2 + +``` + +Diagram of N19-based user plane architecture in non-roaming scenario. Two User Equipment (UE) units, UE 1 and UE 2, are connected to their respective (R)AN units. Each (R)AN is connected to an I-UPF via an N3 interface. The I-UPFs are connected to a PSA via an N9 interface. The PSAs are interconnected by an N19 interface. + +**Figure 4.4.6.1-2: N19-based user plane architecture in non-roaming scenario** + +NOTE: As described in clause 5.29.3, the PSA UPFs can be controlled by a dedicated SMF, a dedicated SMF Set or multiple SMF Sets. + +#### 4.4.6.2 Reference points to support 5G LAN-type service + +**N19:** Reference point between two UPFs for direct routing of traffic between different PDU Sessions without using N6. It has a per 5G VN group granularity. + +### 4.4.7 MSISDN-less MO SMS Service + +MSISDN-less MO SMS via T4 is subscription based. The subscription provides the information whether a UE is allowed to originate MSISDN-less MO SMS. + +The UE is pre-configured with the Service Centre address that points to SMS-SC that performs this MO SMS delivery via NEF delivery procedure. The recipient of this short message is set to the pre-configured address of the AF (i.e. Address of the destination SME). If UE has multiple GPSIs associated to the same IMSI, the GPSI that is associated with an SMS may be determined from the UE's IMSI and the Application Port ID value in the TP-User-Data field (see TS 23.040 [5]). The NEF may obtain the GPSI by querying the UDM with the IMSI and application port ID. + +UE is aware whether the MO SMS delivery status (success or fail) based on the SMS delivery report from SMS-SC. The network does not perform any storing and forwarding functionality for MO SMS. + +See clause 5.2.6 of TS 23.502 [3] for a description of NEF Services and Service Operations. + +### 4.4.8 Architecture to enable Time Sensitive Communication, Time Synchronization and Deterministic Networking + +#### 4.4.8.1 General + +The 5G System can be extended to support the following: + +- Integration of 5GS into a TSN data network (DN):** Integration as a bridge in an IEEE 802.1 Time Sensitive Networking (TSN). The 5GS bridge supports the Time sensitive communication as defined in IEEE 802.1 Time Sensitive Networking (TSN) standards. The architecture is described in clause 4.4.8.2. + +This Release supports of the specification, integration of the 5G System with IEEE 802.1 TSN networks that apply the fully centralized configuration model as defined in IEEE Std 802.1Q [98]. IEEE TSN is a set of standards to define mechanisms for the time-sensitive (i.e. deterministic) transmission of data over Ethernet networks. + +- Enablers for AF requested support of Time Synchronization and/or some aspects of Time Sensitive Communication. The architecture is described in clause 4.4.8.3. +- Support for TSN enabled transport network (TN):** Enablers for interworking with TSN network deployed in the transport network. This option can be used simultaneously with either option a) or b). The architecture is described in clause 5.28a. The interworking is applicable when the transport network deploys the fully centralized configuration model as defined in IEEE Std 802.1Q [98]. In this scenario, a TSN TN is deployed to realize the N3 interface between (R)AN and UPF. From the perspective of the TSN TN, (R)AN and UPF act as End Stations of the TSN TN. +- Integration as a router in a Deterministic Network as defined in IETF RFC 8655 [150]. The architecture is described in clause 4.4.8.4. + +#### 4.4.8.2 Architecture to support IEEE Time Sensitive Networking + +The 5G System is integrated with the external network as a TSN bridge. This "logical" TSN bridge (see Figure 4.4.8.2-1) includes TSN Translator functionality for interoperation between TSN Systems and 5G System both for user plane and control plane. 5GS TSN translator functionality consists of Device-side TSN translator (DS-TT) and Network-side TSN translator (NW-TT). The TSN AF is part of 5GC and provides the control plane translator functionality for the integration of the 5GS with a TSN network, e.g. the interactions with the CNC. 5G System specific procedures in 5GC and RAN, wireless communication links, etc. remain hidden from the TSN network. To achieve such transparency to the TSN network and the 5GS to appear as any other TSN Bridge, the 5GS provides TSN ingress and egress ports via DS-TT and NW-TT. DS-TT and NW-TT optionally support: + +- hold and forward functionality for the purpose of de-jittering; +- per-stream filtering and policing as defined in clause 8.6.5.2.1 of IEEE Std 802.1Q [98]. + +DS-TT optionally supports link layer connectivity discovery and reporting as defined in IEEE Std 802.1AB [97] for discovery of Ethernet devices attached to DS-TT. NW-TT supports link layer connectivity discovery and reporting as defined in IEEE Std 802.1AB [97] for discovery of Ethernet devices attached to NW-TT. If a DS-TT does not support link layer connectivity discovery and reporting, then NW-TT performs link layer connectivity discovery and reporting as defined in IEEE Std 802.1AB [97] for discovery of Ethernet devices attached to DS-TT on behalf of DS-TT. + +NOTE 1: If NW-TT performs link layer connectivity discovery and reporting on behalf of DS-TT, it is assumed that LLDP frames are transmitted between NW-TT and UE on the QoS Flow with the default QoS rule as defined in the clause 5.7.1.1. Alternatively, SMF can establish a dedicated QoS Flow matching on the Ethertype defined for LLDP (IEEE Std 802.1AB [97]). + +There are three TSN configuration models defined in IEEE Std 802.1Q [98]. Amongst the three models: + +- fully centralized model is supported in this Release of the specification; +- fully distributed model is not supported in this Release of the specification; +- centralized network/distributed user model is not supported in this Release of the specification. + +NOTE 2: This Release supports interworking with TSN using clause 8.6.8.4 of IEEE Std 802.1Q [98] scheduled traffic and clause 8.6.5.2.1 of IEEE Std 802.1Q [98] per-stream filtering and policy. + +![Figure 4.4.8.2-1: System architecture view with 5GS appearing as TSN bridge. The diagram shows a 'Logical (TSN) Bridge' containing a 'Device side of Bridge' (DS-TT and UE) and a 'Network side of Bridge' (RAN, UPF, NW-TT). The DS-TT connects to a TSN System. The UE connects to the RAN via N1 and N2. The RAN connects to the UPF via N3. The UPF connects to the NW-TT via N4. The NW-TT connects to a TSN System via the U-plane. The UPF also connects to the SMF via N4 and to the PCF via N9. The SMF connects to the AMF via N11 and to the PCF via N7. The AMF connects to the UDM via N8 and N10. The UDM connects to the NEF via N52. The NEF connects to the TSN AF via N33. The TSN AF connects to a TSN System via the C-plane. The PCF connects to the NEF via N30.](72bc1a2b64dd6bac8285f560440c1218_img.jpg) + +Figure 4.4.8.2-1: System architecture view with 5GS appearing as TSN bridge. The diagram shows a 'Logical (TSN) Bridge' containing a 'Device side of Bridge' (DS-TT and UE) and a 'Network side of Bridge' (RAN, UPF, NW-TT). The DS-TT connects to a TSN System. The UE connects to the RAN via N1 and N2. The RAN connects to the UPF via N3. The UPF connects to the NW-TT via N4. The NW-TT connects to a TSN System via the U-plane. The UPF also connects to the SMF via N4 and to the PCF via N9. The SMF connects to the AMF via N11 and to the PCF via N7. The AMF connects to the UDM via N8 and N10. The UDM connects to the NEF via N52. The NEF connects to the TSN AF via N33. The TSN AF connects to a TSN System via the C-plane. The PCF connects to the NEF via N30. + +**Figure 4.4.8.2-1: System architecture view with 5GS appearing as TSN bridge** + +NOTE 3: Whether DS-TT and UE are combined or are separate is up to implementation. + +NOTE 4: TSN AF does not need to support N33 in this release of the specification. + +#### 4.4.8.3 Architecture for AF requested support of Time Sensitive Communication and Time Synchronization + +This clause describes the architecture to enable Time Sensitive Communication AF requested time sensitive communication and time synchronization services. The Time Sensitive Communication and Time Synchronization related features that are supported based on AF request are described in clauses 5.27.1 and 5.27.2, respectively. Figure 4.4.8.3-1 shows the architecture to support Time Sensitive Communication and Time Synchronization services. + +As shown in Figure 4.4.8.3-1, to support Time Synchronization service based on IEEE Std 802.1AS [104] or IEEE Std 1588 [126] for Ethernet or IP type PDU Sessions, the DS-TT, NW-TT and Time Sensitive Communication and Time Synchronization Function (TSCTSF) are required in order to support the features in IEEE Std 802.1AS [104] or IEEE Std 1588 [126] as described in clause 5.27. The NEF exposes 5GS capability to support Time Synchronization service as described in clause 5.27.1.8. TSCTSF controls the DS-TT(s) and NW-TT for the (g)PTP based time synchronization service. In addition, TSCTSF supports TSC assistance container related functionalities. + +![Figure 4.4.8.3-1: Architecture to enable Time Sensitive Communication and Time Synchronization services. The diagram shows a 'Device side' (dashed box) containing an 'End Station Device', 'DS-TT', and 'UE'. The 'UE' connects to '(R)AN' via N1 and N2. '(R)AN' connects to 'UPF' via N3. 'UPF' contains 'NW-TT' and connects to 'DN' via U-plane. 'UPF' also connects to 'SMF' via N4 and to 'PCF' via N9. 'SMF' connects to 'AMF' via N11 and to 'PCF' via N7. 'AMF' connects to 'UDM' via N8 and N10. 'UDM' connects to 'TSCTSF' via N87. 'TSCTSF' connects to 'NEF' via N85 and to 'PCF' via N84. 'NEF' connects to 'AF' via N33 and to 'PCF' via N30. 'PCF' connects to 'UDM' via N52.](7a1dee155822446f7828dcb055c465c3_img.jpg) + +Figure 4.4.8.3-1: Architecture to enable Time Sensitive Communication and Time Synchronization services. The diagram shows a 'Device side' (dashed box) containing an 'End Station Device', 'DS-TT', and 'UE'. The 'UE' connects to '(R)AN' via N1 and N2. '(R)AN' connects to 'UPF' via N3. 'UPF' contains 'NW-TT' and connects to 'DN' via U-plane. 'UPF' also connects to 'SMF' via N4 and to 'PCF' via N9. 'SMF' connects to 'AMF' via N11 and to 'PCF' via N7. 'AMF' connects to 'UDM' via N8 and N10. 'UDM' connects to 'TSCTSF' via N87. 'TSCTSF' connects to 'NEF' via N85 and to 'PCF' via N84. 'NEF' connects to 'AF' via N33 and to 'PCF' via N30. 'PCF' connects to 'UDM' via N52. + +**Figure 4.4.8.3-1: Architecture to enable Time Sensitive Communication and Time Synchronization services** + +NOTE 1: If the AF is considered to be trusted by the operator, the AF could interact directly with TSCTSF, the connection between AF and TSCTSF is not depicted in the architecture diagram for brevity. + +UPF/NW-TT distributes the (g)PTP messages as described in clause 5.27.1. + +When the UPF supports one or more NW-TT(s), there is one-to-one association between an NW-TT and the network instance or between an NW-TT and network instance together with DNN/S-NSSAI in the UPF. When there are multiple network instances within a UPF, each network instance is considered logically separate. The network instance for the N6 interface (clause 5.6.12) may be indicated by the SMF to the UPF for a given PDU Session during PDU Session establishment procedure. UPF allocates resources based on the Network Instance and S-NSSAI and it is supported according to TS 29.244 [65]. DNN/S-NSSAI may be indicated by the SMF together with the network instance to the UPF for a given PDU Session during PDU Session establishment procedure. + +NOTE 2: The same NW-TT is used for all PDU Sessions in the UPF for the given DNN/S-NSSAI; the NW-TT is unique per DNN/S-NSSAI. This ensures that the UPF selects an N4 session associated with the correct TSCTSF when the NW-TT initiates an UMIC or PMIC. At any given time, the NW-TT is associated with a single TSCTSF. + +#### 4.4.8.4 Architecture to support IETF Deterministic Networking + +The 5G System is integrated with the Deterministic Network as defined in IETF RFC 8655 [150] as a logical DetNet transit router, see Figure 4.4.8.4-1. The TSCTSF performs mapping in the control plane between the 5GS internal functions and the DetNet controller. 5G System specific procedures in 5GC and RAN remain hidden from the DetNet controller. + +![Figure 4.4.8.4-1: 5GS Architecture to support IETF Deterministic Networking. The diagram shows a 5GS logical DetNet Router (dashed box) containing UDM, AMF, SMF, TSCTSF, PCF, (R)AN, and UPF (with NW-TT and N9 interfaces). A UE is connected to a DetNet system and the (R)AN. The UPF is connected to a DetNet network via a U-plane. The CPF: DetNet controller is connected to the TSCTSF and the DetNet network.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +``` + +graph TD + subgraph 5GS_logical_DetNet_Router [5GS logical DetNet Router] + UDM[UDM] + AMF[AMF] + SMF[SMF] + TSCTSF[TSCTSF] + PCF[PCF] + RAN[(R)AN] + UPF[UPF] + NW_TT[NW-TT] + N9[N9] + + UDM -- N8 --> AMF + UDM -- N10 --> SMF + AMF -- N11 --> SMF + AMF -- N1 --> UE + AMF -- N2 --> RAN + SMF -- N7 --> PCF + SMF -- N4 --> UPF + RAN -- N3 --> UPF + UPF --- NW_TT + UPF --- N9 + end + + UE[UE] --- DetNet_system[DetNet system] + UE --- RAN + + TSCTSF -- N84 --> PCF + TSCTSF --- CPF[CPF: DetNet controller] + + UPF -- U-plane --> DetNet_network((DetNet network)) + CPF --- DetNet_network + +``` + +Figure 4.4.8.4-1: 5GS Architecture to support IETF Deterministic Networking. The diagram shows a 5GS logical DetNet Router (dashed box) containing UDM, AMF, SMF, TSCTSF, PCF, (R)AN, and UPF (with NW-TT and N9 interfaces). A UE is connected to a DetNet system and the (R)AN. The UPF is connected to a DetNet network via a U-plane. The CPF: DetNet controller is connected to the TSCTSF and the DetNet network. + +**Figure 4.4.8.4-1: 5GS Architecture to support IETF Deterministic Networking** + +On the device side, the UE is connected with a DetNet system, which may be a DetNet End System or a DetNet Node. + +The architecture does not require the DS-TT functionality to be supported in the device nor require the user plane NW-TT functionality to be supported in the UPF, however, it can co-exist with such functions. For the reporting of information of the network side ports, NW-TT control plane function is used. The architecture can be combined with architecture in clause 4.4.8.3 to support time synchronization and TSC. + +DetNet may be used in combination with time synchronization mechanisms as defined in clause 5.27, but it does not require usage of these mechanisms. + +5GS acts as a DetNet router in the DetNet domain. Use cases where the 5GS acts as a sub-network (see clause 4.1.2 of IETF RFC 8655 [150]) are also possible but do not require any additional 3GPP standardization. A special case where the 5GS can act as a sub-network is when the 5GS acts as a TSN network, which is supported by the 3GPP specifications based on the architecture in clause 4.4.8.2. + +**NOTE:** For DetNet interworking, it is assumed that there is a business agreement to support the use of the DetNet controller so that it can be regarded trusted for the operator. Depending on the needs of a given deployment, functions such as the authentication, authorization and potential throttling of signalling from the DetNet controller can be achieved by including such functionalities in the TSCTSF. + +The routing of the downlink packets is achieved using the existing 3GPP functions. + +# 5 High level features + +## 5.1 General + +Clause 5 specifies the high level functionality and features of the 5G System for both 3GPP and Non-3GPP access and for the interoperability with the EPC defined in TS 23.401 [26]. + +## 5.2 Network Access Control + +### 5.2.1 General + +Network access is the means for the user to connect to 5G CN. Network access control comprises the following functionality: + +- Network selection, +- Identification and authentication, +- Authorisation, +- Access control and barring, +- Policy control, +- Lawful Interception. + +### 5.2.2 Network selection + +In order to determine to which PLMN to attempt registration, the UE performs network selection. The network selection procedure comprises two main parts, PLMN selection and access network selection. The requirements for the PLMN selection are specified in TS 22.011 [25] and the procedures are in TS 23.122 [17]. The access network selection part for the 3GPP access networks is specified in TS 36.300 [30] for E-UTRAN and in TS 38.300 [27] for the NR. + +The network selection for the Disaster Roaming is described in TS 23.122 [17] and TS 24.501 [47]. + +#### 5.2.2a Void + +### 5.2.3 Identification and authentication + +The network may authenticate the UE during any procedure establishing a NAS signalling connection with the UE. The security architecture is specified in TS 33.501 [29]. The network may optionally perform an PEI check with 5G-EIR. + +### 5.2.4 Authorisation + +The authorisation for connectivity of the subscriber to the 5GC and the authorization for the services that the user is allowed to access based on subscription (e.g. Operator Determined Barring, Roaming restrictions, Access Type and RAT Type currently in use) is evaluated once the user is successfully identified and authenticated. This authorization is executed during UE Registration procedure. + +### 5.2.5 Access control and barring + +When the UE needs to transmit an initial NAS message, the UE shall request to establish an RRC Connection first and the NAS shall provide the RRC establishment related information to the lower layer. The RAN handles the RRC Connection with priority during and after RRC Connection Establishment procedure, when UE indicates priority in Establishment related information + +Under high network load conditions, the network may protect itself against overload by using the Unified Access Control functionality for 3GPP access specified in TS 22.261 [2], TS 24.501 [47] and TS 38.300 [27] to limit access attempts from UEs. Depending on network configuration, the network may determine whether certain access attempt should be allowed or blocked based on categorized criteria, as specified in TS 22.261 [2] and TS 24.501 [47]. The NG-RAN may broadcast barring control information associated with Access Categories and Access Identities as specified in TS 38.300 [27]. + +The NG-RAN node may initiate such Unified Access Control when: + +- AMFs request to restrict the load for UEs that access the network by sending OVERLOAD START message containing conditions defined in clause 5.19.5.2, or +- requested by OAM, or +- triggered by NG-RAN itself. + +If the NG-RAN node takes a decision to initiate UAC because of the reception of the N2 interface OVERLOAD START messages, the NG-RAN should only initiate such procedure if all the AMFs relevant to the request contained in the OVERLOAD START message and connected to this NG-RAN node request to restrict the load for UEs that access the network. + +If the UE supports both N1 and S1 modes NAS and, as defined in TS 23.401 [26], the UE is configured for Extended Access Barring (EAB) but is not configured with a permission for overriding Extended Access Barring (EAB), when the UE wants to access the 5GS it shall perform Unified Access Control checks for Access Category 1 on receiving an indication from the upper layers as defined in TS 24.501 [47], TS 38.331 [28], TS 36.331 [51]. + +If the UE supports both N1 and S1 modes NAS and, as defined in TS 23.401 [26], the UE is configured with a permission for overriding Extended Access Barring (EAB), when the UE wants to access the 5GS it shall ignore Unified Access Control checks for Access Category 1 on receiving an indication from the upper layers, as defined in TS 24.501 [47]. + +NOTE: UE signalling of Low Access Priority indication over N1 in 5GS is not supported in this release of the specification. + +Operator may provide one or more PLMN-specific Operator-defined access category definitions to the UE using NAS signalling, and the UE handles the Operator-defined access category definitions stored for the Registered PLMN, as specified in TS 24.501 [47]. + +The access control for the Disaster Roaming is described in TS 23.122 [17] and TS 24.501 [47]. + +### 5.2.6 Policy control + +Network access control including service authorization may be influenced by Policy control, as specified in clause 5.14. + +### 5.2.7 Lawful Interception + +For definition and functionality of Lawful Interception, please see TS 33.126 [35]. + +## 5.3 Registration and Connection Management + +### 5.3.1 General + +The Registration Management is used to register or deregister a UE/user with the network, and establish the user context in the network. The Connection Management is used to establish and release the signalling connection between the UE and the AMF. + +### 5.3.2 Registration Management + +#### 5.3.2.1 General + +A UE/user needs to register with the network to receive services that requires registration. Once registered and if applicable the UE updates its registration with the network (see TS 23.502 [3]): + +- periodically, in order to remain reachable (Periodic Registration Update); or +- upon mobility (Mobility Registration Update); or +- to update its capabilities or re-negotiate protocol parameters (Mobility Registration Update). + +The Initial Registration procedure involves execution of Network Access Control functions as defined in clause 5.2 (i.e. user authentication and access authorization based on subscription profiles in UDM). As result of the Registration procedure, the identifier of the serving AMF serving the UE in the access through which the UE has registered will be registered in UDM. + +The registration management procedures are applicable over both 3GPP access and Non-3GPP access. The 3GPP and Non-3GPP RM states are independent of each other, see clause 5.3.2.4. + +#### 5.3.2.2 5GS Registration Management states + +##### 5.3.2.2.1 General + +Two RM states are used in the UE and the AMF that reflect the registration status of the UE in the selected PLMN: + +- RM-DEREGISTERED. +- RM-REGISTERED. + +##### 5.3.2.2.2 RM-DEREGISTERED state + +In the RM-DEREGISTERED state, the UE is not registered with the network. The UE context in AMF holds no valid location or routing information for the UE so the UE is not reachable by the AMF. However, some parts of UE context may still be stored in the UE and the AMF e.g. to avoid running an authentication procedure during every Registration procedure. + +In the RM-DEREGISTERED state, the UE shall: + +- attempt to register with the selected PLMN using the Initial Registration procedure if it needs to receive service that requires registration (see clause 4.2.2.2 of TS 23.502 [3]). +- remain in RM-DEREGISTERED state if receiving a Registration Reject upon Initial Registration (see clause 4.2.2.2 of TS 23.502 [3]). +- enter RM-REGISTERED state upon receiving a Registration Accept (see clause 4.2.2.2 of TS 23.502 [3]). + +When the UE RM state in the AMF is RM-DEREGISTERED, the AMF shall: + +- when applicable, accept the Initial Registration of a UE by sending a Registration Accept to this UE and enter RM-REGISTERED state for the UE (see clause 4.2.2.2 of TS 23.502 [3]); or +- when applicable, reject the Initial Registration of a UE by sending a Registration Reject to this UE (see clause 4.2.2.2 of TS 23.502 [3]). + +##### 5.3.2.2.3 RM-REGISTERED state + +In the RM-REGISTERED state, the UE is registered with the network. In the RM-REGISTERED state, the UE can receive services that require registration with the network. + +In the RM-REGISTERED state, the UE shall: + +- perform Mobility Registration Update procedure if the current TAI of the serving cell (see TS 37.340 [31]) is not in the list of TAIs that the UE has received from the network in order to maintain the registration and enable the AMF to page the UE; + +NOTE: Additional considerations for Mobility Registration Update in case of NR satellite access are provided in clause 5.4.11.6. + +- perform Periodic Registration Update procedure triggered by expiration of the periodic update timer to notify the network that the UE is still active. +- perform a Mobility Registration Update procedure to update its capability information or to re-negotiate protocol parameters with the network; + +- perform Deregistration procedure (see clause 4.2.2.3.1 of TS 23.502 [3]), and enter RM-DEREGISTERED state, when the UE needs to be no longer registered with the PLMN. The UE may decide to deregister from the network at any time. +- enter RM-DEREGISTERED state when receiving a Registration Reject message or a Deregistration message. The actions of the UE depend upon the cause value' in the Registration Reject or Deregistration message. See clause 4.2.2 of TS 23.502 [3]. + +When the UE RM state in the AMF is RM-REGISTERED, the AMF shall: + +- perform Deregistration procedure (see clauses 4.2.2.3.2, 4.2.2.3.3 of TS 23.502 [3]), and enter RM-DEREGISTERED state for the UE, when the UE needs to be no longer registered with the PLMN. The network may decide to deregister the UE at any time; +- perform Implicit Deregistration at any time after the Implicit Deregistration timer expires. The AMF shall enter RM-DEREGISTERED state for the UE after Implicit Deregistration; +- when applicable, accept or reject Registration Requests or Service Requests from the UE. + +##### 5.3.2.2.4 5GS Registration Management State models + +![Figure 5.3.2.2.4-1: RM state model in UE. This state transition diagram shows two states: RM-DEREGISTERED and RM-REGISTERED. RM-DEREGISTERED has a self-loop labeled 'Registration Reject'. RM-REGISTERED has a self-loop labeled 'Registration Update Accept'. A transition arrow points from RM-REGISTERED to RM-DEREGISTERED, labeled 'Deregistration' and 'Registration Reject'. A transition arrow points from RM-DEREGISTERED to RM-REGISTERED, labeled 'Registration Accept'.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +``` + +stateDiagram-v2 + [*] --> RM-REGISTERED + RM-REGISTERED --> RM-REGISTERED : Registration Update Accept + RM-REGISTERED --> RM-DEREGISTERED : Deregistration, Registration Reject + RM-DEREGISTERED --> RM-REGISTERED : Registration Accept + RM-DEREGISTERED --> RM-DEREGISTERED : Registration Reject + +``` + +Figure 5.3.2.2.4-1: RM state model in UE. This state transition diagram shows two states: RM-DEREGISTERED and RM-REGISTERED. RM-DEREGISTERED has a self-loop labeled 'Registration Reject'. RM-REGISTERED has a self-loop labeled 'Registration Update Accept'. A transition arrow points from RM-REGISTERED to RM-DEREGISTERED, labeled 'Deregistration' and 'Registration Reject'. A transition arrow points from RM-DEREGISTERED to RM-REGISTERED, labeled 'Registration Accept'. + +Figure 5.3.2.2.4-1: RM state model in UE + +![Figure 5.3.2.2.4-2: RM state model in AMF. This state transition diagram is identical to Figure 5.3.2.2.4-1, showing two states: RM-DEREGISTERED and RM-REGISTERED. RM-DEREGISTERED has a self-loop labeled 'Registration Reject'. RM-REGISTERED has a self-loop labeled 'Registration Update Accept'. A transition arrow points from RM-REGISTERED to RM-DEREGISTERED, labeled 'Deregistration' and 'Registration Reject'. A transition arrow points from RM-DEREGISTERED to RM-REGISTERED, labeled 'Registration Accept'.](731f533b0599c8e42a063f06e4332045_img.jpg) + +``` + +stateDiagram-v2 + [*] --> RM-REGISTERED + RM-REGISTERED --> RM-REGISTERED : Registration Update Accept + RM-REGISTERED --> RM-DEREGISTERED : Deregistration, Registration Reject + RM-DEREGISTERED --> RM-REGISTERED : Registration Accept + RM-DEREGISTERED --> RM-DEREGISTERED : Registration Reject + +``` + +Figure 5.3.2.2.4-2: RM state model in AMF. This state transition diagram is identical to Figure 5.3.2.2.4-1, showing two states: RM-DEREGISTERED and RM-REGISTERED. RM-DEREGISTERED has a self-loop labeled 'Registration Reject'. RM-REGISTERED has a self-loop labeled 'Registration Update Accept'. A transition arrow points from RM-REGISTERED to RM-DEREGISTERED, labeled 'Deregistration' and 'Registration Reject'. A transition arrow points from RM-DEREGISTERED to RM-REGISTERED, labeled 'Registration Accept'. + +Figure 5.3.2.2.4-2: RM state model in AMF + +#### 5.3.2.3 Registration Area management + +Registration Area management comprises the functions to allocate and reallocate a Registration area to a UE. Registration area is managed per access type i.e. 3GPP access or Non-3GPP access. + +When a UE registers with the network over the 3GPP access, the AMF allocates a set of tracking areas in TAI List to the UE. When the AMF allocates registration area, i.e. the set of tracking areas in TAI List, to the UE it may take into account various information (e.g. Mobility Pattern and Allowed/Non-Allowed Area (refer to clause 5.3.4.1)). An AMF which has the whole PLMN as serving area may alternatively allocate the whole PLMN ("all PLMN") as registration area to a UE in MICO mode (refer to clause 5.4.1.3). When AMF allocates registration area for UE registered for Disaster Roaming service as specified in clause 5.40.4, AMF shall only consider TAIs covering the area with the Disaster Condition. + +The 5G System shall support allocating a Registration Area using a single TAI List which includes tracking areas of any NG-RAN nodes in the Registration Area for a UE. + +In the case of SNPN, the TAI list allocated by AMF does not support Tracking Areas belonging to different SNPNs. + +TAI used for non-3GPP access shall be dedicated to non-3GPP access. TAI(s) dedicated to Non-3GPP access may be defined in a PLMN and apply within this PLMN. Each N3IWF, TNGF, TWIF and W-AGF is locally configured with one TAI value. Each N3IWF, TNGF, TWIF and W-AGF may be configured with a different TAI value or with the same TAI value as other N3IWFs, TNGFs, TWIFs and/or W-AGFs. The TAI is provided to the AMF during N2 interface setup and as part of the User Location Information in UE associated messages as described in TS 38.413 [34]. + +When a UE registers with the network over a Non-3GPP access, the AMF allocates to the UE a registration area that only includes the TAI received from the serving N3IWF, TNGF, TWIF or W-AGF. + +NOTE 1: For example, two W-AGFs can each correspond to a different TAI (one TAI per W-AGF) and thus support different sets of S-NSSAI(s). + +When generating the TAI list, the AMF shall include only TAIs that are applicable on the access type (i.e. 3GPP access or Non-3GPP access) where the TAI list is sent. + +NOTE 2: To prevent extra signalling load resulting from Mobility Registration Update occurring at every RAT change, it is preferable to avoid generating a RAT-specific TAI list for a UE supporting more than one RAT. + +NOTE 3: For a UE registered on N3GPP access the TAI(s) provided to the UE as part of the Registration Area is expected to enable the support of the slices that are intended to be provided for this UE over this specific Non-3GPP access. In addition, the Registration Area provided to the UE for non-3GPP access will never change until the UE deregisters from non-3GPP access (either explicit deregistration or implicit deregistration due to Deregistration timer expiring due to UE entering CM\_IDLE state). + +For all 3GPP Access RATs in NG-RAN and for Non-3GPP Access, the 5G System supports the TAI format as specified in TS 23.003 [19] consisting of MCC, MNC and a 3-byte TAC only. + +The additional aspects for registration management when a UE is registered over one access type while the UE is already registered over the other access type is further described in clause 5.3.2.4. + +To ensure a UE initiates a Mobility Registration procedure when performing inter-RAT mobility to or from NB-IoT, a Tracking Area shall not contain both NB-IoT and other RATs cells (e.g. WB-E-UTRA, NR), and the AMF shall not allocate a TAI list that contains both NB-IoT and other RATs Tracking Areas. + +For 3GPP access the AMF determines the RAT type the UE is camping on based on the Global RAN Node IDs associated with the N2 interface and additionally the Tracking Area indicated by NG-RAN. When the UE is accessing NR using unlicensed bands, as defined in clause 5.4.8, an indication is provided in N2 interface as defined in TS 38.413 [34]. + +The AMF may also determine more precise RAT Type information based on further information received from NG-RAN: + +- The AMF may determine the RAT Type to be LTE-M as defined in clause 5.31.20; or +- The AMF may determine the RAT Type to be NR using unlicensed bands, as defined in clause 5.4.8. +- The AMF may determine the RAT Type to be one of the RAT types for satellite access, as defined in clause 5.4.10. +- The AMF may determine the RAT Type to be NR RedCap as defined in clause 5.41. + +For Non-3GPP accesses the AMF determines the RAT type the UE is camping based on the 5G-AN node associated with N2 interface as follows: + +- The RAT type is Untrusted Non-3GPP if the 5G-AN node has a Global N3IWF Node ID; +- The RAT type is Trusted Non-3GPP if the 5G-AN node has a Global TNGF Node ID or a Global TWIF Node ID; and +- The RAT type is Wireline -BBF if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline BBF Access Network. The RAT type is Wireline-Cable if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline Cable Access Network. If not possible to distinguish between the two, the RAT type is Wireline. + +NOTE 4: How to differentiate between W-AGF supporting either Wireline BBF Access Network or the Wireline (e.g. different Global W-AGF Node ID IE or the Global W-AGF Node ID including a field to distinguish between them) is left to Stage 3 definition. + +NOTE 5: If an operator supports only one kind of Wireline Access Network (either Wireline BBF Access Network or a Wireline Cable Access Network) the AMF may be configured to use RAT type Wireline or the specific one. + +For Non-3GPP access the AMF may also use the User Location Information provided at N2 connection setup to determine a more precise RAT Type, e.g. identifying IEEE 802.11 access, Wireline-Cable access, Wireline-BBF access. + +When the 5G-AN node has either a Global N3IWF Node ID, or a Global TNGF Node ID, or a Global TWIF Node ID, or a Global W-AGF Node ID, the Access Type is Non-3GPP Access. + +#### 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access + +This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to the 5G-RG. + +For a given serving PLMN there is one RM context for a UE for each access, e.g. when the UE is consecutively or simultaneously served by a 3GPP access and by a non-3GPP access (i.e. via an N3IWF, TNGF and W-AGF) of the same PLMN. UDM manages separate/independent UE Registration procedures for each access. + +When served by the same PLMN for 3GPP and non-3GPP accesses, an UE is served by the same AMF except in the temporary situation described in clause 5.17 i.e. after a mobility from EPS while the UE has PDU Sessions associated with non-3GPP access. + +The 5G NSWO authentication as defined in Annex S of TS 33.501 [29] does not impact the RM state. + +An AMF associates multiple access-specific RM contexts for an UE with: + +- a 5G-GUTI that is common to both 3GPP and Non-3GPP accesses. This 5G-GUTI is globally unique. +- a Registration state per access type (3GPP / Non-3GPP) +- a Registration Area per access type: one Registration Area for 3GPP access and another Registration Area for non 3GPP access. Registration Areas for the 3GPP access and the Non-3GPP access are independent. +- timers for 3GPP access: + - a Periodic Registration timer; and + - a Mobile Reachable timer and an Implicit Deregistration timer. +- timers for non-3GPP access: + - a UE Non-3GPP Deregistration timer; and + - a Network Non-3GPP Implicit Deregistration timer. + +The AMF shall not provide a Periodic Registration Timer for the UE over a Non-3GPP access. Consequently, the UE need not perform Periodic Registration Update procedure over Non-3GPP access. Instead, during the Initial Registration procedure and Re-registration, the UE is provided by the network with a UE Non-3GPP Deregistration timer that starts when the UE enters non-3GPP CM-IDLE state. + +When the 3GPP access and the non-3GPP access for the same UE are served by the same PLMN, the AMF assigns the same 5G-GUTI for use over both accesses. Such a 5G-GUTI may be assigned or re-assigned over any of the 3GPP and Non-3GPP accesses. The 5G-GUTI is assigned upon a successful registration of the UE, and is valid over both 3GPP and Non-3GPP access to the same PLMN for the UE. Upon performing an initial access over the Non-3GPP access or over the 3GPP access while the UE is already registered with the 5G System over another access of the same PLMN, the UE provides the native 5G-GUTI for the other access. This enables the AN to select an AMF that maintains the UE context created at the previous Registration procedure via the GUAMI derived from the 5G-GUTI, and enables the AMF to correlate the UE request to the existing UE context via the 5G-GUTI. + +If the UE is performing registration over one access and intends to perform registration over the other access in the same PLMN (e.g. the 3GPP access and the selected N3IWF, TNGF or W-AGF are located in the same PLMN), the UE shall not initiate the registration over the other access until the Registration procedure over first access is completed. + +NOTE: To which access the UE performs registration first is up to UE implementation. + +When the UE is successfully registered to an access (3GPP access or Non-3GPP access respectively) and the UE registers via the other access: + +- if the second access is located in the same PLMN (e.g. the UE is registered via a 3GPP access and selects a N3IWF, TNGF or W-AGF located in the same PLMN), the UE shall use for the registration to the PLMN associated with the new access the 5G-GUTI that the UE has been provided with at the previous registration or UE configuration update procedure for the first access in the same PLMN. Upon successful completion of the registration to the second access, if the network included a 5G-GUTI in the Registration Accept, the UE shall use the 5G-GUTI received in the Registration Accept for both registrations. If no 5G-GUTI is included in the Registration Accept, then the UE uses the 5G-GUTI assigned for the existing registration also for the new registration. +- if the second access is located in a PLMN different from the registered PLMN of the first access (i.e. not the registered PLMN), (e.g. the UE is registered to a 3GPP access and selects a N3IWF, TNGF or W-AGF located in a PLMN different from the PLMN of the 3GPP access, or the UE is registered over Non-3GPP and registers to a 3GPP access in a PLMN different from the PLMN of the N3IWF, TNGF or W-AGF), the UE shall use for the registration to the PLMN associated with the new access a 5G-GUTI only if it has got one previously received from a PLMN that is not the same as the PLMN the UE is already registered with. If the UE does not include a 5G-GUTI, the SUCI shall be used for the new registration. Upon successful completion of the registration to the second access, the UE has the two 5G-GUTIs (one per PLMN). + +A UE supporting registration over both 3GPP and Non-3GPP access to two PLMNs shall be able to handle two separate registrations, including two 5G-GUTIs, one per PLMN, and two associated equivalent PLMN lists. + +When a UE 5G-GUTI assigned during a Registration procedure over 3GPP (e.g. the UE registers first over a 3GPP access) is location-dependent, the same UE 5G-GUTI can be re-used over the Non-3GPP access when the selected N3IWF, TNGF or W-AGF function is in the same PLMN as the 3GPP access. When an UE 5G-GUTI is assigned during a Registration procedure performed over a Non 3GPP access (e.g. the UE registers first over a non-3GPP access), the UE 5G-GUTI may not be location-dependent, so that the UE 5G-GUTI may not be valid for NAS procedures over the 3GPP access and, in this case, a new AMF is allocated during the Registration procedure over the 3GPP access. + +When the UE is registered first via 3GPP access, if the UE registers to the same PLMN via Non-3GPP access, the UE shall send the GUAMI obtained via 3GPP access to the N3IWF, TNGF or W-AGF, which uses the received GUAMI to select the same AMF as the 3GPP access. + +The Deregistration Request message indicates whether it applies to the 3GPP access the Non-3GPP access, or both. + +If the UE is registered on both 3GPP and Non-3GPP accesses and it is in CM-IDLE over Non-3GPP access, then the UE or AMF may initiate a Deregistration procedure over the 3GPP access to deregister the UE only on the Non-3GPP access, in which case all the PDU Sessions which are associated with the Non-3GPP access shall be released. + +If the UE is registered on both 3GPP and non-3GPP accesses and it is in CM-IDLE over 3GPP access and in CM-CONNECTED over non-3GPP access, then the UE may initiate a Deregistration procedure over the non-3GPP access to deregister the UE only on the 3GPP access, in which case all the PDU Sessions which are associated with the 3GPP access shall be released. + +Registration Management over Non-3GPP access is further defined in clause 5.5.1. + +### 5.3.3 Connection Management + +#### 5.3.3.1 General + +Connection management comprises the functions of establishing and releasing a NAS signalling connection between a UE and the AMF over N1. This NAS signalling connection is used to enable NAS signalling exchange between the UE and the core network. It comprises both the AN signalling connection between the UE and the AN (RRC Connection + +over 3GPP access or UE-N3IWF connection over untrusted N3GPP access or UE-TNGF connection over trusted N3GPP access) and the N2 connection for this UE between the AN and the AMF. + +#### 5.3.3.2 5GS Connection Management states + +##### 5.3.3.2.1 General + +Two CM states are used to reflect the NAS signalling Connection of the UE with the AMF: + +- CM-IDLE +- CM-CONNECTED + +The CM state for 3GPP access and Non-3GPP access are independent of each other, i.e. one can be in CM-IDLE state at the same time when the other is in CM-CONNECTED state. + +##### 5.3.3.2.2 CM-IDLE state + +A UE in CM-IDLE state has no NAS signalling connection established with the AMF over N1. The UE performs cell selection/cell reselection according to TS 38.304 [50] and PLMN selection according to TS 23.122 [17]. + +There are no AN signalling connection, N2 connection and N3 connections for the UE in the CM-IDLE state. + +If the UE is both in CM-IDLE state and in RM-REGISTERED state, the UE shall, unless otherwise specified in clause 5.3.4.1: + +- Respond to paging by performing a Service Request procedure (see clause 4.2.3.2 of TS 23.502 [3]), unless the UE is in MICO mode (see clause 5.4.1.3); +- perform a Service Request procedure when the UE has uplink signalling or user data to be sent (see clause 4.2.3.2 of TS 23.502 [3]). Specific conditions apply for LADN, see clause 5.6.5. + +When the UE state in the AMF is RM-REGISTERED, UE information required for initiating communication with the UE shall be stored. The AMF shall be able to retrieve stored information required for initiating communication with the UE using the 5G-GUTI. + +NOTE: In 5GS there is no need for paging using the SUPI/SUCI of the UE. + +The UE provides 5G-S-TMSI as part of AN parameters during AN signalling connection establishment as specified in TS 38.331 [28] and TS 36.331 [51]. The UE shall enter CM-CONNECTED state whenever an AN signalling connection is established between the UE and the AN (entering RRC\_CONNECTED state over 3GPP access, or at the establishment of the UE-N3IWF connectivity over untrusted non-3GPP access or the UE-TNGF connectivity over trusted non-3GPP access). The transmission of an Initial NAS message (Registration Request, Service Request or Deregistration Request) initiates the transition from CM-IDLE to CM-CONNECTED state. + +When the UE states in the AMF are CM-IDLE and RM-REGISTERED, the AMF shall: + +- perform a network triggered Service Request procedure when it has signalling or mobile-terminated data to be sent to this UE, by sending a Paging Request to this UE (see clause 4.2.3.3 of TS 23.502 [3]), if a UE is not prevented from responding e.g. due to MICO mode or Mobility Restrictions. + +The AMF shall enter CM-CONNECTED state for the UE whenever an N2 connection is established for this UE between the AN and the AMF. The reception of initial N2 message (e.g. N2 INITIAL UE MESSAGE) initiates the transition of AMF from CM-IDLE to CM-CONNECTED state. + +The UE and the AMF may optimize the power efficiency and signalling efficiency of the UE when in CM-IDLE state e.g. by activating MICO mode (see clause 5.4.1.3). + +##### 5.3.3.2.3 CM-CONNECTED state + +A UE in CM-CONNECTED state has a NAS signalling connection with the AMF over N1. A NAS signalling connection uses an RRC Connection between the UE and the NG-RAN and an NGAP UE association between the AN and the AMF for 3GPP access. A UE can be in CM-CONNECTED state with an NGAP UE association that is not bound to any TNLA between the AN and the AMF. See clause 5.21.1.2 for details on the state of NGAP UE association + +for an UE in CM-CONNECTED state. Upon completion of a NAS signalling procedure, the AMF may decide to release the NAS signalling connection with the UE. + +In the CM-CONNECTED state, the UE shall: + +- enter CM-IDLE state whenever the AN signalling connection is released (entering RRC\_IDLE state over 3GPP access or when the release of the UE-N3IWF connectivity over untrusted non-3GPP access or the UE-TNGF connectivity over trusted non-3GPP access is detected by the UE), see TS 38.331 [28] for 3GPP access. + +When the UE CM state in the AMF is CM-CONNECTED, the AMF shall: + +- enter CM-IDLE state for the UE whenever the logical NGAP signalling connection and the N3 user plane connection for this UE are released upon completion of the AN Release procedure as specified in TS 23.502 [3]. + +The AMF may keep a UE CM state in the AMF in CM-CONNECTED state until the UE de-registers from the core network. + +A UE in CM-CONNECTED state can be in RRC\_INACTIVE state, see TS 38.300 [27]. When the UE is in RRC\_INACTIVE state the following applies: + +- UE reachability is managed by the RAN, with assistance information from core network; +- UE paging is managed by the RAN. +- UE monitors for paging with UE's CN (5G S-TMSI) and RAN identifier. + +##### 5.3.3.2.4 5GS Connection Management State models + +![Figure 5.3.3.2.4-1: CM state transition in UE. A diagram showing two states, CM-IDLE and CM-CONNECTED, represented by ovals. A transition arrow points from CM-CONNECTED to CM-IDLE, labeled 'AN signaling connection released'. A transition arrow points from CM-IDLE to CM-CONNECTED, labeled 'AN signaling connection established (Initial NAS message)'.](5dfc130b129ace4df375839020a5700d_img.jpg) + +``` + +stateDiagram-v2 + CM-IDLE <--> CM-CONNECTED : AN signaling connection released / established (Initial NAS message) + +``` + +Figure 5.3.3.2.4-1: CM state transition in UE. A diagram showing two states, CM-IDLE and CM-CONNECTED, represented by ovals. A transition arrow points from CM-CONNECTED to CM-IDLE, labeled 'AN signaling connection released'. A transition arrow points from CM-IDLE to CM-CONNECTED, labeled 'AN signaling connection established (Initial NAS message)'. + +Figure 5.3.3.2.4-1: CM state transition in UE + +![Figure 5.3.3.2.4-2: CM state transition in AMF. A diagram showing two states, CM-IDLE and CM-CONNECTED, represented by ovals. A transition arrow points from CM-CONNECTED to CM-IDLE, labeled 'N2 Context released'. A transition arrow points from CM-IDLE to CM-CONNECTED, labeled 'N2 Context established'.](3376375fe7236a570fd0ee9448d9c4ee_img.jpg) + +``` + +stateDiagram-v2 + CM-IDLE <--> CM-CONNECTED : N2 Context released / established + +``` + +Figure 5.3.3.2.4-2: CM state transition in AMF. A diagram showing two states, CM-IDLE and CM-CONNECTED, represented by ovals. A transition arrow points from CM-CONNECTED to CM-IDLE, labeled 'N2 Context released'. A transition arrow points from CM-IDLE to CM-CONNECTED, labeled 'N2 Context established'. + +Figure 5.3.3.2.4-2: CM state transition in AMF + +When a UE enters CM-IDLE state, the UP connection of the PDU Sessions that were active on this access are deactivated. + +NOTE: The activation of UP connection of PDU Sessions is documented in clause 5.6.8. + +##### 5.3.3.2.5 CM-CONNECTED with RRC\_INACTIVE state + +RRC\_INACTIVE state applies to NG-RAN. UE support for RRC\_INACTIVE state is defined in TS 38.306 [69] for NR and TS 36.306 [70] for E-UTRA connected to 5GC. RRC\_INACTIVE is not supported by NB-IoT connected to 5GC. + +The AMF shall provide assistance information to the NG-RAN, to assist the NG-RAN's decision whether the UE can be sent to RRC\_INACTIVE state except due to some exceptional cases such as: + +- PLMN (or AMF set) does not support RRC\_INACTIVE; +- The UE needs to be kept in CM-CONNECTED State (e.g. for tracking). + +The "RRC Inactive Assistance Information" includes: + +- UE specific DRX values; +- UE specific extended idle mode DRX values (cycle length and Paging Time Window length); +- The Registration Area provided to the UE; +- Periodic Registration Update timer; +- If the AMF has enabled MICO mode for the UE, an indication that the UE is in MICO mode; +- Information from the UE identifier, as defined in TS 38.304 [50] for NR and TS 36.304 [52] for E-UTRA connected to 5GC, that allows the RAN to calculate the UE's RAN paging occasions; +- An indication that Paging Cause Indication for Voice Service is supported; +- AMF PEIPS Assistance Information (see clause 5.4.12.2) for paging a UE in CM-CONNECTED with RRC\_INACTIVE state over NR as defined in TS 38.300 [27]; +- CN based MT communication handling support indication for RRC\_INACTIVE state (see clause 5.31.7.2.1). + +The RRC Inactive Assistance Information mentioned above is provided by the AMF during N2 activation with the (new) serving NG-RAN node (i.e. during Registration, Service Request, Handover) to assist the NG RAN's decision whether the UE can be sent to RRC\_INACTIVE state. If the AMF allocates a new Registration Area to the UE, the AMF should update the NG-RAN with the new Registration Area by sending the RRC Inactive Assistance Information accordingly. The Paging Cause Indication for Voice Service is used to assist NG RAN to perform RAN based paging. + +RRC\_INACTIVE state is part of RRC state machine, and it is up to the RAN to determine the conditions to enter RRC\_INACTIVE state. If any of the parameters included in the RRC Inactive Assistance Information changes as the result of NAS procedure, the AMF shall update the RRC Inactive Assistance Information to the NG-RAN node. + +When the UE is in CM-CONNECTED state, if the AMF has provided RRC Inactive assistance information, the RAN node may decide to move a UE to RRC\_INACTIVE state. + +The state and "endpoints" (in the case of Dual Connectivity configuration) of the N2 and N3 reference points are not changed by the UE entering RRC\_INACTIVE state. A UE in RRC\_INACTIVE state is aware of the RAN Notification area and periodic RAN Notification Area Update timer. + +The 5GC network is not aware of the UE transitions between CM-CONNECTED with RRC\_CONNECTED and CM-CONNECTED with RRC\_INACTIVE state, unless the 5GC network is notified via N2 notification procedure in clause 4.8.3 of TS 23.502 [3]. + +At transition into CM-CONNECTED with RRC\_INACTIVE state, the NG-RAN configures the UE with a periodic RAN Notification Area Update timer taking into account the value of the Periodic Registration Update timer value indicated in the RRC Inactive Assistance Information, and uses a guard timer with a value longer than the RAN Notification Area Update timer value provided to the UE. + +If the periodic RAN Notification Area Update guard timer expires in NG-RAN, the NG-RAN shall initiate AN Release procedure as specified in clause 4.2.6 of TS 23.502 [3]. + +When the UE is in CM-CONNECTED with RRC\_INACTIVE state, the UE performs PLMN selection procedures as defined in TS 23.122 [17] and TS 24.501 [47]. + +When the UE is CM-CONNECTED with RRC\_INACTIVE state, the UE may resume the RRC Connection due to: + +- Uplink data pending; +- Mobile initiated NAS signalling procedure; +- As a response to RAN paging; +- Notifying the network that it has left the RAN Notification Area; +- Upon periodic RAN Notification Area Update timer expiration. + +If the UE resumes the connection in a different NG-RAN node within the same PLMN or equivalent PLMN or within the same SNPN or equivalent SNPN, the UE AS context is retrieved from the old NG-RAN node and a procedure is triggered towards the CN (see clause 4.8.2 of TS 23.502 [3]). + +NOTE 1: With Dual Connectivity configuration if the UE resumes the RRC connection in the Master RAN node, the Secondary RAN node configuration is defined in TS 38.300 [27]. + +If the RAN paging procedure applying DRX or eDRX value no longer than 10.24s, as defined in TS 38.300 [27], is not successful in establishing contact with the UE the procedure shall be handled by the network as follows: + +- If NG-RAN has at least one pending NAS PDU for transmission, the RAN node shall initiate the AN Release procedure (see clause 4.2.6 of TS 23.502 [3]) to move the UE CM state in the AMF to CM-IDLE state and indicate to the AMF the NAS non-delivery. +- If NG RAN has only pending user plane data for transmission, the NG-RAN node may keep the N2 connection active or initiate the AN Release procedure (see clause 4.2.6 of TS 23.502 [3]) based on local configuration in NG-RAN. + +NOTE 2: The user plane data which triggers the RAN paging can be lost, e.g. in the case of RAN paging failure. + +If the RAN paging procedure applying eDRX value longer than 10.24s, as defined in TS 38.300 [27], has not requested the CN based mobile terminated (MT) communication handling as described in clause 5.31.7.2.1 and is not successful in establishing contact with the UE after paging the UE, the procedure shall be handled by network as follows: + +- If NG-RAN has at least one pending NAS PDU for transmission, the RAN node shall initiate the AN Release procedure (see clause 4.2.6 of TS 23.502 [3]) to move the UE CM state in the AMF to CM-IDLE state and indicate to the AMF the NAS non-delivery. +- If NG-RAN has only pending user plane data for transmission, the NG-RAN node may keep the N2 connection active and based on implementation send indication to the CN requesting the CN based mobile terminated (MT) communication handling as described in clause 5.31.7.2.1, or initiate the AN Release procedure (see clause 4.2.6 of TS 23.502 [3]) based on local configuration in NG-RAN. + +NOTE 3: The user plane data which triggers the RAN paging can be lost, e.g. in the case of RAN paging failure. + +If a UE in CM-CONNECTED with RRC\_INACTIVE state performs cell selection to GERAN/UTRAN/E-UTRAN, it shall follow idle mode procedures of the selected RAT as specified in clause 5.17. + +In addition, a UE in CM-CONNECTED state with RRC\_INACTIVE state shall enter CM-IDLE state and initiates the NAS signalling recovery (see TS 24.501 [47]) in the following cases: + +- If RRC resume procedure fails, +If the UE receives Core Network paging, +- If the periodic RAN Notification Area Update timer expires and the UE cannot successfully resume the RRC Connection, +- In any other failure scenario that cannot be resolved in RRC\_INACTIVE state and requires the UE to move to CM-IDLE state. + +When a UE is in CM-CONNECTED with RRC\_INACTIVE state, and a trigger to change the UE's NG-RAN or E-UTRAN UE Radio Capability information happens, the UE shall move to CM-IDLE state and initiate the procedure for updating UE Radio Capability defined in clause 5.4.4.1. (For specific requirements for a UE operating in dual-registration mode see clause 5.17.2.1) + +When UE is in CM-CONNECTED with RRC\_INACTIVE state, if RAN has received Location Reporting Control message from AMF with the Reporting Type indicating single stand-alone report or continuously reporting whenever the UE changes the cell, the RAN shall perform location reporting as specified in clause 4.10 of TS 23.502 [3]. + +When the UE is CM-CONNECTED with RRC\_INACTIVE state. If the AMF receives Nudm\_UECM\_DeregistrationNotification from UDM, the AMF shall initiate AN Release procedure as specified in clause 4.2.6 of TS 23.502 [3]. + +When UE is in CM-CONNECTED with RRC\_INACTIVE state, if RAN has received Location Reporting Control message from AMF with the Reporting Type of the Area Of Interest based reporting, the RAN shall send a Location Report message to AMF including UE presence in the Area Of Interest (i.e. IN, OUT, or UNKNOWN) and the UE's last known location with time stamp. + +When the UE is in CM-CONNECTED with RRC\_INACTIVE state, if the old NG-RAN node that sends the UE into RRC\_INACTIVE state receives the downlink N2 signalling, it initiates the RAN paging as defined in TS 38.300 [27]. If the UE resumes the RRC Connection towards a different NG-RAN node, the old NG-RAN node includes the "UE Context Transfer" indication into a response container to the NF (e.g. AMF or SMF) that generates such N2 downlink signalling. Then the NF shall reattempt the same procedure when the path switch from the old NG-RAN node to the new NG-RAN node is complete. + +#### 5.3.3.3 NAS signalling connection management + +##### 5.3.3.3.1 General + +NAS signalling connection management includes the functions of establishing and releasing a NAS signalling connection. + +##### 5.3.3.3.2 NAS signalling connection establishment + +NAS signalling connection establishment function is provided by the UE and the AMF to establish a NAS signalling connection for a UE in CM-IDLE state. The AMF shall provide the list of recommended cells/ TAs / NG-RAN node identifiers for paging, if the NG-RAN had provided that information in an earlier AN Release Procedure in the AN (see clause 4.2.6 of TS 23.502 [3]). + +When the UE in CM-IDLE state needs to transmit an NAS message, the UE shall initiate a Service Request, a Registration or a Deregistration procedure to establish a NAS signalling connection to the AMF as specified in clauses 4.2.2 and 4.2.3 of TS 23.502 [3]. If the NAS signalling connection is to be established via an NG-RAN node, but the AMF detects that this UE has already established a NAS signalling connection via old NG-RAN node, the AMF shall release the old established NAS signalling connection by triggering AN Release Procedure. + +Based on UE preferences, UE subscription, Mobility Pattern and network configuration, the AMF may keep the NAS signalling connection until the UE de-registers from the network. + +##### 5.3.3.3.3 NAS signalling connection Release + +The procedure of releasing a NAS signalling connection is initiated by the AN node (either 5G (R)AN node or N3IWF) or the AMF. The NG-RAN node may include the list of recommended cells/ TAs / NG-RAN node identifiers for paging, during the AN Release Procedure in the AN (see clause 4.2.6 of TS 23.502 [3]). The AMF stores this information, if provided by the NG-RAN. + +The UE considers the NAS signalling connection is released if it detects the AN signalling connection is released. The AMF considers the NAS signalling connection is released if it detects the N2 context is released. + +#### 5.3.3.4 Support of a UE connected over both 3GPP and Non-3GPP access + +The AMF manages two CM states for an UE: a CM state for 3GPP access and a CM state for Non-3GPP access. An N2 interface can serve the UE for either 3GPP access or for Non 3GPP access. UE connected over both 3GPP and Non-3GPP has got two N2 interfaces, one for each access. A UE may be in any combination of the CM states between 3GPP and Non-3GPP access, e.g. a UE may be CM-IDLE for one access and CM-CONNECTED for the other access, CM-IDLE for both accesses or CM-CONNECTED for both accesses. + +When the UE CM state in the AMF is CM-IDLE for 3GPP access and CM-CONNECTED for Non-3GPP access, the AMF shall perform a network triggered Service Request procedure, when it has downlink data to be sent to this UE for 3GPP access, by sending either the Paging Request via 3GPP access or the NAS notification via Non-3GPP access to this UE (see clause 4.2.3.3 of TS 23.502 [3]). + +Connection Management over Non-3GPP access is further defined in clause 5.5.2. + +### 5.3.4 UE Mobility + +#### 5.3.4.1 Mobility Restrictions + +##### 5.3.4.1.1 General + +Mobility Restrictions restrict mobility handling or service access of a UE. The Mobility Restriction functionality is provided by the UE (only for mobility restriction categories provided to the UE), the radio access network and the core network. + +Unless otherwise stated, Mobility Restrictions only apply to 3GPP access and wireline access, they do not apply to other non-3GPP accesses. + +The UE and the network shall override Mobility restriction as specified in clause 5.16.4.3 when accessing the network for Emergency Services. For MPS and MCX, service area restriction does not apply, as specified in TS 24.501 [47]. + +For UE requesting Disaster Roaming service, the UE is only allowed to receive services in the area with Disaster Condition as specified in clause 5.40.4. The other areas within the PLMN shall be considered as forbidden area for the UE registered for Disaster Roaming service. + +Service Area restrictions and handling of Forbidden Areas for CM-IDLE state and, for CM-CONNECTED state when in RRC\_INACTIVE state are executed by the UE based on information received from the core network. Mobility Restrictions for CM-CONNECTED state when in RRC\_CONNECTED state are executed by the radio access network and the core network. + +In CM-CONNECTED state, the core network provides Mobility Restrictions to the radio access network within Mobility Restriction List. + +Mobility Restrictions consists of RAT restriction, Forbidden Area, Service Area Restrictions, Core Network type restriction and Closed Access Group information as follows: + +###### - RAT restriction: + +Defines the 3GPP and non-3GPP Radio Access Technology(ies), a UE is not allowed to access in a PLMN. In a restricted RAT a UE based on subscription is not permitted access to the network for this PLMN. For 3GPP access and CM-CONNECTED state, when radio access network determines target RAT and target PLMN during Handover procedure, it should take per PLMN RAT restriction into consideration. The RAT restriction is enforced in the network, and not provided to the UE. + +###### - Forbidden Area: + +In a Forbidden Area, the UE, based on subscription, is not permitted to initiate any communication with the network for this PLMN. The UE behaviour in terms of cell selection, RAT selection and PLMN selection depends on the network response that informs the UE of Forbidden Area. A Forbidden Area applies either to 3GPP access or to non-3GPP access. + +Further description on Forbidden Area when using wireline access is available in TS 23.316 [84]. + +Support for Forbidden Area with NR satellite access is described in clause 5.4.11.8. + +Forbidden Areas should not be used for Untrusted or Trusted non-3GPP access. + +NOTE 1: If a UE receives that the UE is accessing from a forbidden tracking area when registering over untrusted non-3GPP access or trusted non-3GPP access, the UE cannot determine the corresponding TAI and thus needs to consider that access to untrusted non-3GPP access and to trusted non-3GPP access in this PLMN is forbidden until the forbidden area list is removed as described in TS 24.501 [47]. + +NOTE 2: The UE reactions to specific network responses are described in TS 24.501 [47]. + +###### - Service Area Restriction: + +Defines areas in which the UE may or may not initiate communication with the network as follows: + +###### - Allowed Area: + +In an Allowed Area, the UE is permitted to initiate communication with the network as allowed by the subscription. + +###### - Non-Allowed Area: + +In a Non-Allowed Area a UE is service area restricted based on subscription. The UE and the network are not allowed to initiate Service Request, or any connection requests for user plane data, control plane data, exception data reporting, or SM signalling (except for PS Data Off status change reporting) to obtain user services that are not related to mobility. + +The UE shall not use the entering of a Non-Allowed Area as a criterion for Cell Reselection, a trigger for PLMN Selection or Domain selection for UE originating sessions or calls. The RRC procedures while the UE is in CM-CONNECTED with RRC\_INACTIVE state are unchanged compared to when the UE is in an Allowed Area. The RM procedures are unchanged compared to when the UE is in an Allowed Area. The UE in a Non-Allowed Area shall respond to core network paging or NAS Notification message from non-3GPP access with Service Request and RAN paging. The UE in a Non-Allowed Area may initiate MA PDU Session establishment or activation over a non-3GPP access other than wireline access, but the User Plane resources on the 3GPP access for the MA-PDU shall not be established or activated. The handling of Non-Allowed Area when using wireline access is described in TS 23.316 [84]. + +NOTE 3: When the services are restricted in 5GS due to Service Area Restriction, then it is assumed that the services will be also restricted in all RATs/Systems at the same location(s) using appropriate mechanisms available in the other RATs/Systems. + +NOTE 4: Delivery of SOR transparent container, UE policy container, UE parameters update transparent container as defined in TS 24.501 [47], or removal of any stored Paging Restriction Information from network via Registration Request (see clause 5.38), is part of the mobility related service and is allowed in an area with service restriction. + +NOTE 5: For a UE in CM-CONNECTED state then neither control plane data transmission nor, if user plane resources are already established, user plane data transmission are restricted by a non-allowed area. + +###### - Core Network type restriction: + +Defines whether UE is allowed to connect to 5GC only, EPC only, both 5GC and EPC for this PLMN. The Core Network type restriction when received applies in the PLMN either to both 3GPP and non-3GPP Access Types or to non-3GPP Access Type only. + +NOTE 6: The Core Network type restriction can be used e.g. in network deployments where the E-UTRAN connects to both EPC and 5GC as described in clause 5.17. When the Core Network type restriction applies to non-3GPP Access Type, the UE is restricted from using any connectivity to an N3IWF. + +###### - Closed Access Group information: + +As defined in clause 5.30.3. + +For a given UE, the core network determines the Mobility Restrictions based on UE subscription information, UE location and/or local policy (e.g. if the HPLMN has not deployed 5GC, HPLMN ID of the UE and the operator's policy are used in the VPLMN for determining the Core Network type restriction). The Mobility Restriction may change due to e.g. UE's subscription, location change and local policy. Optionally the Service Area Restrictions or the Non-Allowed Area may in addition be fine-tuned by the PCF e.g. based on UE location, PEI and network policies. Service Area Restrictions may be updated during a Registration procedure or UE Configuration Update procedure. + +NOTE 7: The subscription management ensures that for MPS service subscriber the Mobility Restrictions is not included. + +If the network sends Service Area Restrictions to the UE, the network sends only either an Allowed Area, or a Non-Allowed Area, but not both at the same time, to the UE. If the UE has received an Allowed Area from the network, any TA not part of the Allowed Area is considered by the UE as non-allowed. If the UE has received a Non-Allowed Area from the network, any TA not part of the Non-Allowed Area is considered by the UE as allowed. If the UE has not received any Service Area Restrictions, any TA in the PLMN is considered as allowed. + +If the UE has overlapping areas between Forbidden Areas, Service Area Restrictions, or any combination of them, the UE shall proceed in the following precedence order: + +- The evaluation of Forbidden Areas shall take precedence over the evaluation of Service Area Restrictions. + +The UDM shall provide to the AMF the information defined in TS 23.008 [119] about the subscriber's NR or E-UTRA access restriction set by the operator determined e.g. by subscription scenario and roaming scenario: + +- For NR: + - NR not allowed as primary RAT. + - NR not allowed as secondary RAT. + - NR in unlicensed bands not allowed as primary RAT. + - NR in unlicensed bands not allowed as secondary RAT. + - NR(LEO) satellite access not allowed as primary RAT. + - NR(MEO) satellite access not allowed as primary RAT. + - NR(GEO) satellite access not allowed as primary RAT. + - NR(OTHERSAT) satellite access not allowed as primary RAT. + - NR RedCap not allowed as primary RAT. +- For E-UTRA: + - E-UTRA not allowed as primary RAT. + - E-UTRA not allowed as secondary RAT. + - E-UTRA in unlicensed bands not allowed as secondary RAT. + - NB-IoT not allowed as primary RAT. + - LTE-M not allowed as primary RAT. + +In order to enforce all primary RAT restrictions, the related RAT has to be deployed in different Tracking Area Codes and the subscriber shall not be allowed to access the network in TAs using the particular RAT. + +With all secondary RAT restrictions, the subscriber shall not be allowed to use this RAT as secondary RAT. + +##### 5.3.4.1.2 Management of Service Area Restrictions + +This clause describes Service Area Restrictions for 3GPP access. For Service Area Restrictions when using wireline access, see TS 23.316 [84]. + +A Service Area Restriction may contain one or more (e.g. up to 16) entire Tracking Areas each or the Service Area Restriction may be set as unlimited (i.e. contain all Tracking Areas of the PLMN). The UE's subscription data in the UDM includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas—specified by using explicit Tracking Area identities and/or other geographical information (e.g. longitude/latitude, zip code, etc). The geographical information used to specify Allowed or Non-Allowed Area is only managed in the network, and the network will map it to a list of TAs before sending Service Area Restriction information to the PCF, NG-RAN and UE. + +When the AMF assigns a limited allowed area to the UE, the AMF shall provide the UE with Service Area Restrictions which consist of either Allowed Areas or Non-Allowed Areas. The Allowed Areas included in the Service Area Restrictions can be pre-configured and/or dynamically assigned by the AMF. + +The Allowed Area may alternatively be configured as unlimited i.e. it may contain all Tracking Areas of the PLMN. The Registration Area of a UE in the Non-Allowed Area should consist of a set of TAs which belongs to a Non-Allowed Area of the UE. The Registration Area of a UE in the Allowed Area should consist of a set of TAs which belongs to an Allowed Area of the UE. The AMF provides the Service Area Restriction in the form of TA(s), which may be a subset of full list stored in UE's subscription data or provided by the PCF, to the UE during the Registration procedure. + +NOTE: As the finest granularity for Service Area Restrictions are at TA level, subscriptions with limited geographical extent, like subscriptions for Fixed Wireless Access, will be allocated one or a few TAs and will consequently be allowed to access services in a larger area than in e.g. a FWA system. + +The limited allowed area may also be limited by the AMF by a maximum allowed number of Tracking Areas, even though this limitation is not sent to the UE. If maximum allowed number of Tracking Areas is used in combination with Allowed Area, the maximum allowed number of Tracking Areas indicates (to the AMF) the maximum number of TAs allowed in limited allowed area inside the Allowed Area. If maximum allowed number of Tracking Areas is used in combination with Non-Allowed Area, the maximum allowed number of Tracking Areas indicates (to the AMF) the maximum number of TAs allowed in limited allowed area outside of the Non-Allowed Area. + +The UDM stores the Service Area Restrictions of a UE as part of the UE's subscription data. The PCF in the serving network may (e.g. due to varying conditions such as UE's location, application in use, time and date) further adjust Service Area Restrictions of a UE, either by expanding an Allowed Area or by reducing a Non-Allowed Area or by increasing the maximum allowed number of Tracking Areas. If NWDAF is deployed, the PCF may use analytics (i.e. statistics or predictions) on UE mobility from NWDAF (see TS 23.288 [86]) to adjust Service Area Restrictions. The UDM and the PCF may update the Service Area Restrictions of a UE at any time. For the UE in CM-CONNECTED state the AMF updates the UE and RAN immediately. For UE in CM-IDLE state the AMF may page the UE immediately or store the updated service area restriction and update the UE upon next signalling interaction with the UE, as defined in TS 24.501 [47]. + +During registration, if the Service Area Restrictions of the UE is not present in the AMF, the AMF fetches from the UDM the Service Area Restrictions of the UE that may be further adjusted by the PCF. The serving AMF shall enforce the Service Area Restrictions of a UE. A limited allowed area given by a maximum allowed number of Tracking Areas, may be dynamically assigned by the AMF adding any not yet visited (by the UE) Tracking Areas to the limited allowed area until the maximum allowed number of Tracking Areas is reached (i.e. the AMF adds new TAs to the limited allowed area until the number of TAs is equal to the maximum allowed number of Tracking Areas). The AMF deletes the list of TAs that have been used up under the maximum allowed number of Tracking Areas quota at every Initial Registration. + +For a UE in CM-CONNECTED state the AMF shall indicate the Service Area Restrictions of this UE to the RAN, using a Mobility Restriction List. + +The UE shall store the received Service Area Restrictions and, if there is previously stored Service Area Restrictions, replace them with the newly received information. If the Service Area Restrictions include a limited allowed area, the Service Area Restrictions are applicable for the Tracking areas indicated in Service Area Restrictions. If the Service Area Restrictions included an unlimited allowed area, the received Service Area Restrictions are either applicable for the registered PLMN and its equivalent PLMN(s) that are available in the Registration Area, or the registered SNPN that is available in the Registration Area. The RAN uses the Service Area Restrictions for target cell selection in Xn and N2 based handover. + +Upon change of serving AMF due to mobility, the old AMF may provide the new AMF with the Service Area Restrictions of the UE that may be further adjusted by the PCF. + +The network may perform paging for a UE to update Service Area Restrictions with Generic UE Configuration Update procedure (see clause 4.2.4 of TS 23.502 [3]). + +In the case of roaming, the Service Area Restrictions are transferred from the UDM via the serving AMF to the serving PCF in the visited network. The serving PCF in the visited network may further adjust the Service Area Restrictions. + +Support for Service Area Restrictions with NR satellite access is described in clause 5.4.11.8. + +#### 5.3.4.2 Mobility Pattern + +The Mobility Pattern is a concept that may be used by the AMF to characterise and optimise the UE mobility. The AMF determines and updates Mobility Pattern of the UE based on subscription of the UE, statistics of the UE mobility, network local policy, and the UE assisted information, or any combination of them. The statistics of the UE mobility can be historical or expected UE moving trajectory. If NWDAF is deployed, the statistics of the UE mobility can also be analytics (i.e. statistics or predictions) provided by the NWDAF (see TS 23.288 [86]). + +The Mobility Pattern can be used by the AMF to optimize mobility support provided to the UE, for example, Registration area allocation. + +#### 5.3.4.3 Radio Resource Management functions + +##### 5.3.4.3.1 General + +To support radio resource management in NG-RAN the AMF provides the parameter 'Index to RAT/Frequency Selection Priority' (RFSP Index) to NG-RAN across N2. The RFSP Index is mapped by the RAN to locally defined configuration in order to apply specific RRM strategies, taking into account any available information in RAN. The RFSP Index is UE specific and applies to all the Radio Bearers. Examples of how this parameter may be used by the RAN: + +- to derive UE specific cell reselection priorities to control idle mode camping. +- to decide on redirecting active mode UEs to different frequency layers or RATs (e.g. see clause 5.3.4.3.2). + +The HPLMN may set the RFSP Index taking into account the Subscribed S-NSSAIs. The AMF receives the subscribed RFSP Index from the UDM (e.g. during the Registration procedure). For non-roaming subscribers, the AMF chooses the RFSP Index in use according to one of the following procedures, depending on operator's configuration: + +- the RFSP Index in use is identical to the subscribed RFSP Index, or +- the AMF chooses the RFSP Index in use based on the subscribed RFSP Index, the locally configured operator's policies, the Allowed NSSAI and any Partially Allowed NSSAI, S-NSSAI(s) rejected partially in the RA, Rejected S-NSSAI(s) for the RA, Pending NSSAI and the UE related context information available at the AMF, including UE's usage setting, if received during Registration procedures (see clause TS 23.502 [3]). + +NOTE 1: One example of how the AMF can use the "UE's usage setting," is to select an RFSP value that enforces idle mode camping on E-UTRA for a UE acting in a "Voice centric" way, in the case voice over NR is not supported in the specific Registration Area and it contains NR cells. + +The AMF may report to the PCF the subscribed RFSP Index received from the UDM for further evaluation as described in clause 6.1.2.1 of TS 23.503 [45]. When receiving the authorized RFSP Index from the PCF, the AMF shall apply the authorized RFSP Index instead of the subscribed RFSP Index for choosing the RFSP index in use (as described above). + +For roaming subscribers, the AMF may choose the RFSP Index in use based on the visited network policy, but can take input from the HPLMN into account (e.g. an RFSP Index value pre-configured per HPLMN, or a single RFSP Index value to be used for all roamers independent of the HPLMN). If the AMF receives authorized RFSP Index value from the V-PCF, the AMF chooses the RFSP index in use based on the authorized RFSP Index value. + +NOTE 2: The PCF can provide validity time together with the authorized RFSP Index indicating a change in priority from 5G access to E-UTRAN access as specified in clause 5.17.2.2. + +The RFSP Index in use is also forwarded from source to target NG-RAN node when Xn or N2 is used for intra-NG-RAN handover. + +The AMF stores the subscribed RFSP Index value received and the RFSP Index value in use. During the Registration procedure, the AMF may update the RFSP Index value in use (e.g. the AMF may need to update the RFSP Index value in use if the UE related context information in the AMF has changed). When the RFSP Index value in use is changed, the AMF immediately provides the updated RFSP Index value in use to NG-RAN node by modifying an existing UE context or by establishing a new UE context in RAN or by being configured to include the updated RFSP Index value in use in the NGAP DOWNLINK NAS TRANSPORT message if the user plane establishment is not needed. During inter-AMF mobility procedures, the source AMF forwards both RFSP Index values to the target AMF. The target AMF may replace the received RFSP Index value in use with a new RFSP Index value in use that is based on the operator's policies and the UE related context information available at the target AMF. + +In order to enable UE idle mode mobility control and priority-based reselection mechanism considering availability of Network Slices at the network and the Network Slices allowed for a UE, an RFSP is derived as described in clause 5.3.4.3, considering also the Allowed NSSAI and any Partially Allowed NSSAI for the UE. + +A UE supporting NSAG (see clause 5.15.14) may be configured, for some of the S-NSSAIs in the configured NSSAI, with NSAGs it can use as described in TS 38.300 [27], TS 38.304 [50], TS 38.331 [28], TS 38.321 [143], TS 24.501 [47] and as described in clause 5.3.4.3.4. + +##### 5.3.4.3.2 Preferred band(s) per data radio bearer(s) + +The NG-RAN may prefer to use specific radio resources per data radio bearer(s), e.g. depending on the Network Slices associated to the data radio bearer used by the UE. The UE idle mode mobility control and priority-based reselection mechanism operates as described in clause 5.3.4.3.1, and when UP resources are activated e.g. for a specific S-NSSAI the NG-RAN can use local policies to decide on what specific radio resources to use for the associated data radio bearer(s). A UE may be served by a set of data radio bearers which may be served by cells in different bands, selected based on RRM policies. + +##### 5.3.4.3.3 Redirection to dedicated frequency band(s) for an S-NSSAI + +If a Network Slice, S-NSSAI, is configured to be available only in TAs covering specific dedicated frequency band(s), then there may be a need to redirect the UE to the dedicated frequency band(s) when such S-NSSAI is requested. If the Requested NSSAI contains S-NSSAI(s) that are not available in the UE's current TA, see clause 5.15.8, the AMF itself or by interacting with the NSSF as described in clause 5.15.5.2.1 may determine a Target NSSAI to be used by the NG-RAN, in addition to the information the AMF receives, such as the Allowed NSSAI and the RFSP for the Allowed NSSAI, to attempt to redirect the UE to a cell and TA in another frequency band and TA that supports the S-NSSAIs in the Target NSSAI. The Target NSSAI includes at least one S-NSSAI from the Requested NSSAI not available in the current TA, but available in another TA in different frequency band possibly overlapping with the current TA, and optionally additional S-NSSAIs from the Requested NSSAI that are configured to be available within the same TAs as the S-NSSAIs not available in the current TA. If the serving PLMN supports the subscription-based restrictions to simultaneous registration of network slices (see clause 5.15.12), and if the UE has NSSRG as part of the subscription information received from the HPLMN, the Target NSSAI includes only S-NSSAIs sharing at least one NSSRG. + +The Target NSSAI may be excluding some of the S-NSSAIs in the Allowed NSSAI and include some of the rejected S-NSSAIs due to lack of support in the TA where the UE is located based on network policies that are in line with customer and operator agreements. + +The Target NSSAI shall only include S-NSSAIs that can be provided in an Allowed NSSAI, or in an Allowed NSSAI and Partially Allowed NSSAI, for the UE. The Target NSSAI includes at least one Rejected S-NSSAI and may include e.g.: + +- all or a subset of the Rejected S-NSSAIs for RA, all or a subset of the S-NSSAIs rejected partially in the RA, all or a subset of Partially Allowed NSSAI when none of the S-NSSAIs in the Requested S-NSSAI were available in the TA where the UE is; +- all the S-NSSAIs of the Allowed NSSAI, all the S-NSSAIs of the Partially Allowed NSSAI and all or a subset of the Rejected S-NSSAIs for the RA and all or subset of S-NSSAIs rejected partially in the RA; +- a subset of the S-NSSAIs in the Allowed NSSAI, a subset of the S-NSSAIs in the Partially Allowed NSSAI and all or a subset of the Rejected S-NSSAIs for the RA and all or subset of S-NSSAIs rejected partially in the RA, if the operator policy is to prefer this Target S-NSSAI to the Allowed NSSAI. + +The AMF should retrieve an RFSP Index suitable for the Target NSSAI and includes the RFSP Index in the information sent to the NG-RAN. The AMF retrieves the RFSP Index from the PCF or, in case PCF is not deployed the AMF determines the RFSP Index according to local configuration. The RFSP index associated to the Target NSSAI is considered if the NG-RAN succeeds to redirect the UE to a new TA where the Target NSSAI, or some S-NSSAIs of the Target NSSAI are supported, otherwise the RFSP index of the Allowed NSSAI is considered. + +If the Requested NSSAI contains S-NSSAI(s) which map to S-NSSAI(s) of the HPLMN subject to Network Slice-Specific Authentication and Authorization that are not available in the UE's current TA, the AMF shall proceed with the Network Slice-Specific Authentication and Authorization procedure as described in clause 4.2.9 of TS 23.502 [3]. If the AMF determines a new Allowed NSSAI and/or Partially Allowed NSSAI at the end of Network Slice-Specific Authentication and Authorization steps and some S-NSSAI is not available in the UE's current TA, a Target NSSAI and corresponding RFSP index may be determined and provided to NG-RAN during UE Configuration Update procedure as described in clause 4.2.4.2 of TS 23.502 [3]. + +The NG-RAN shall attempt to find cells of TAs that can support all the S-NSSAIs in the Target S-NSSAIs, and if no such cell of a TA is available the RAN can attempt to select cells of TAs that best match the Target S-NSSAI. The NG-RAN shall attempt to ensure continuity of the PDU Sessions with activated User Plane associated with the S-NSSAIs in the Allowed NSSAI and/or Partially Allowed NSSAI which are in the Target NSSAI. Also, the NG-RAN should attempt to ensure continuity of service for the S-NSSAIs of the Allowed NSSAI and/or Partially Allowed NSSAI also + +available in the Target NSSAI, before prioritizing cells that are not supporting one or more of the S-NSSAI of the Allowed NSSAI and/or Partially Allowed NSSAI also available in the Target NSSAI. + +The NG-RAN attempts to determine target cell(s) supporting the Target NSSAI considering the UE Radio Capabilities (i.e. the AMF (if available in the UE context) shall provide the NG-RAN with the current UE Radio Capability Information or the RACS UE Radio Capability ID when a Target NSSAI is provided, if the NG-RAN had not yet received any of them, or, if the AMF cannot provide any of these, the UE Radio Capability Information may be retrieved by the NG-RAN from the UE). + +Once the target cells are determined, the NG-RAN initiates RRC redirection procedure towards the target cells, or the NG-RAN initiates handover for the UE with active PDU Sessions associated with the S-NSSAIs which are in the Target NSSAI, if possible. + +After a successful redirection or handover of the UE to a new TA inside the current RA, the UE may request a PDU Session and activate UP resources for a PDU Session for S-NSSAIs of Partially Allowed NSSAI that are supported in the new TA, and the UE may request to register S-NSSAIs rejected partially in the RA that are not rejected in the new TA, as described in clause 5.15.17. + +After a successful redirection or handover of the UE to a new TA outside the current RA, the UE shall perform a Mobility Registration Update procedure and the S-NSSAIs that the new TA supports can be allowed if the UE requests them. In order to ensure that the UE is redirected to a TA outside the current RA when there are S-NSSAIs Rejected for the RA, thus triggering a Mobility Registration Update procedure enabling the UE to request the S-NSSAI(s) that were rejected for the RA, the AMF shall set the RA so that the RA does not include TAs supporting the S-NSSAIs rejected for the RA included in the Target NSSAI when the AMF provides a Target NSSAI to the RAN. + +##### 5.3.4.3.4 Network Slice based cell reselection and Random Access + +When one or more S-NSSAI(s) are associated with NSAG(s), the UE may perform Network Slice based cell reselection and Random Access as described in TS 38.300 [27], TS 38.304 [50], TS 38.331 [28], TS 38.321 [143] and TS 24.501 [47]. + +When providing NSAG Information to the UE, the AMF shall also provide the NSAG priority information for the NSAGs provided in the NSAG Information. The AMF determines the NSAG priority information based on configured local policy of the serving PLMN or SNPN. + +NOTE 1: How the AMF assigns the NSAG priority information per UE is not specified but AMF can take into account information like e.g. UE MM capabilities, Subscribed S-NSSAIs and HPLMN. + +NOTE 2: The AMF can assign same priority value for NSAGs provided in the NSAG Information. + +If the UE has received NSAG Information from the AMF, the UE shall use the NSAG Information provided by the AMF for cell reselection and Random Access as described below. If the UE has not received any NSAG Information from the AMF, the UE shall not use Network Slice based cell reselection and Random Access at all. + +The UE NAS provides to the UE AS the NSAG Information as received from the AMF and the S-NSSAIs in the Allowed NSSAI and any Partially Allowed NSSAI as input to cell reselection, except when the UE intends to register with a new (including any S-NSSAIs rejected partially in the RA) set of S-NSSAIs with a Requested NSSAI different from the current Allowed NSSAI and any Partially Allowed NSSAI, in which case the UE NAS provides to the UE AS layer the NSAG Information as received from the AMF and the S-NSSAIs in the Requested NSSAI, and this may trigger a cell reselection, before sending the Registration Request including the new Requested NSSAI. + +For Network Slice based Random Access, different Random Access resources may be assigned to different NSAG(s). The UE determines Random Access configuration among NSAGs that are published in SIB for Random Access and that are associated to the S-NSSAIs triggering the access. If the signalling transaction triggering the access attempt is related to more than one network slice, and the S-NSSAIs of these network slices are associated with more than one NSAG for Random Access, the NSAG with the highest priority is selected. + +NOTE 3: How the UE NAS provides the NSAGs priorities to UE AS is based internal UE interface, and not specified. + +When a S-NSSAI is replaced by an Alternative S-NSSAI for a UE supporting the Network Slice Replacement feature (see clause 5.15.19) then the AMF provides updated NSAG information also including the Alternative S-NSSAI to the UE when the Alternative S-NSSAI was not part of the UE Configured NSSAI and is Added to the UE configured + +NSSAI. The NSAG priority may take into account the Alternative S-NSSAI is a replacement of the replaced NSSAI if the Alternative S-NSSAI is not part of the UE subscription. + +#### 5.3.4.4 UE mobility event notification + +5G System supports the functionality of tracking and reporting UE mobility events. + +The AMF provides the UE mobility related event reporting to NF that has been authorized to subscribe to the UE mobility event reporting service. Any NF service consumer such as SMF, NEF, TSCTSF or NWDAF that wants to be reported on the UE location is able to subscribe to the UE mobility event notification service to the AMF with the following parameters: + +- Event reporting type that specifies what to be reported on UE mobility (e.g. UE location, UE mobility on Area of Interest). +- Event filters indicating the: + - Area Of Interest that specifies a location area within 3GPP system. The Area Of Interest is represented by a list of Tracking Areas, list of cells or list of (R)AN node identifiers. In the case of LADN, the event consumer (e.g. SMF) provides the "LADN DNN" or "LADN DNN and S-NSSAI" to refer the LADN service area as the Area Of Interest. In the case of PRA, the event consumer (e.g. SMF or PCF) may provide an identifier for Area Of Interest to refer predefined area as the Area Of Interest. In the case of Partial Network Slice Support and Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas as described in clauses 5.15.17 and 5.15.18, the event consumer (e.g. SMF) provides the S-NSSAI to refer the slice restriction area (area restriction applies for the S-NSSAI) as the Area Of Interest. + - The Area Of Interest may include a "RAN timing synchronization status change event" indicator, indicating that the presence in Area of Interest can be determined based on the most recent N2 connection. + - The Area Of Interest may include an "Adjust AoI based on RA" indicator, indicating that the Area of Interest may be adjusted depending on UE's RA. + - The Area Of Interest may include the "Notify the consumer considering UE identity" indicator, containing a list of UE identities or Internal Group ID, and informing the AMF to notify the NF consumer about Area of Interest events only if an event is for the UE belonging to the provided list UEs. The indicator may be included when the request is targeted to Any UE. + - The Area Of Interest may include the "Notify the consumer considering DNN/S-NSSAI" indicator, containing one or more DNN(s)/S-NSSAI(s) and informing the AMF to notify the NF consumer about Area of Interest events only if an event is for the UE having a PDU sessions established for the specified DNN(s)/S-NSSAI(s). + - S-NSSAI and optionally the NSI ID(s). +- Event Reporting Information: event reporting mode, number of reports, maximum duration of reporting, event reporting condition (e.g. when the target UE moved into a specified Area Of Interest, immediate reporting flag). +- Notification Endpoint of NF service consumer to be notified. +- The target of event reporting that indicates a (list of) specific UE(s), a group of UE(s) or any UE (i.e. all UEs served by the AMF). Further details on the information provided by the NF service consumer are provided in clause 4.15 of TS 23.502 [3]. + +If an NF service consumer subscribes to the UE mobility event notification service provided by AMF for reporting of UE presence in Area Of Interest, the AMF tracks UE's location considering UE's CM state and using NG-RAN procedures (if RRC\_INACTIVE state applies to NG-RAN) in order to determine the UE presence in the Area Of Interest, as described in clause 4.15.4.2 of TS 23.502 [3]. Upon detecting the change of the UE presence in the Area Of Interest, the AMF notifies the UE presence in the Area Of Interest and the new UE location to the subscribed NF service consumer. + +If the Area Of Interest in the subscription to the UE mobility event notification includes "RAN timing synchronization status change event" indicator as described in Table 5.2.2.3.1-1 of TS 23.502 [3], and the registration request from the UE includes a UE 5GMM Core Network Capability with an indication for "support for network reconnection due to + +RAN timing synchronization status change " as described in clause 5.4.4.a, the AMF reports the UE presence in Area of Interest based on the most recent N2 connection as described in Annex D of TS 23.502 [3]. + +If the Area Of Interest in the subscription to the UE mobility event notification includes "Adjust AoI based on RA" indicator as described in Table 5.2.2.3.1-1 in TS 23.502 [3], the AMF reports the UE presence in Area of Interest based on the most recent N2 connection as described in Annex D in TS 23.502 [3]. + +When the AMF is changed, the subscription of mobility event for a UE or group of UEs is transferred from the old AMF. Subscriptions targeted to Any UE shall not be moved to another AMF due to UE mobility. The new AMF may decide not to notify the SMF with the current status related to the subscription of mobility event if the new AMF determines that, based on MM Context of the UE, the event is reported by the old AMF. + +In the network deployment where a UE may leave or enter the Area Of Interest without any notification to the 5GC in CM-CONNECTED state (i.e. in the case that RRC\_INACTIVE state applies to the NG-RAN), the AMF may initiate the NG-RAN location reporting as described in clause 5.4.7 or N2 Notification as described in clause 4.8.3 of TS 23.502 [3] to track the UE presence in the Area Of Interest. + +The AMF may provide UE mobility event reporting to PCF, using Policy Control Request Triggers defined in TS 23.503 [45]. + +### 5.3.5 Triggers for network analytics + +Triggers for the AMF to request for or subscribe to the analytics information from the NWDAF are internal logic in the AMF and may include for example: + +- UE access and mobility related event subscription by other NFs (e.g. SMF, NEF); +- locally detected events; +- analytics information received. + +The trigger conditions may depend on operator and implementation policy in the AMF. When a trigger condition happens, the AMF may decide if any analytics information is needed and if so, request for or subscription to the analytics information from the NWDAF. + +The AMF may, upon detection of certain local events, e.g. frequent mobility re-registration of one or more UEs, subscribe to mobility related abnormal behaviour analytics of the UE(s) as described in TS 23.288 [86] in order to trace UE mobility trend and take appropriate actions. + +## 5.4 3GPP access specific aspects + +### 5.4.1 UE reachability in CM-IDLE + +#### 5.4.1.1 General + +Reachability management is responsible for detecting whether the UE is reachable and providing UE location (i.e. access node) for the network to reach the UE. This is done by paging UE and UE location tracking. The UE location tracking includes both UE registration area tracking (i.e. UE registration area update) and UE reachability tracking ((i.e. UE periodic registration area update)). Such functionalities can be either located at 5GC (in the case of CM-IDLE state) or NG-RAN (in the case of CM-CONNECTED state). + +The UE and the AMF negotiate UE reachability characteristics for CM-IDLE state during Registration procedures. + +Three UE reachability categories are negotiated between UE and AMF for CM-IDLE state: + +1. UE reachability allowing Mobile Terminated data while the UE is CM-IDLE state. + - The UE location is known by the network on a Tracking Area List granularity + - Paging procedures apply to this category. + +- Mobile originating and mobile terminated data apply in this category for both CM-CONNECTED and CM-IDLE state. +2. Mobile Initiated Connection Only (MICO) mode: + - Mobile originated data applies in this category for both CM-CONNECTED and CM-IDLE state. + - Mobile terminated data is only supported when the UE is in CM-CONNECTED state. + 3. UE unreachability due to Unavailability Period: + - Mobile originated data and Mobile terminated data are not transmitted in this category (handling of data by extending buffering may apply). + - Paging procedure is not applicable to this category. + +Whenever a UE in RM-REGISTERED state enters CM-IDLE state, it starts a periodic registration timer according to the periodic registration timer value received from the AMF during a Registration procedure. + +The AMF allocates a periodic registration timer value to the UE based on local policies, subscription information and information provided by the UE. After the expiry of the periodic registration timer, the UE shall perform a periodic registration. If the UE moves out of network coverage when its periodic registration timer expires, the UE shall perform a Registration procedure when it next returns to the coverage. + +The AMF runs a Mobile Reachable timer for the UE. The timer is started with a value longer than the UE's periodic registration timer whenever the CM state for the UE in RM-REGISTERED state changes to CM-IDLE. If the AMF receives an elapsed time from RAN when RAN initiate UE context release indicating UE unreachable, the AMF should deduce a Mobile Reachable timer value based on the elapsed time received from RAN and the normal Mobile Reachable timer value. The AMF stops the Mobile Reachable timer, if the UE CM state in the AMF moves to CM-CONNECTED state. If the Mobile Reachable timer expires, the AMF determines that the UE is not reachable. + +However, the AMF does not know for how long the UE remains not reachable, thus the AMF shall not immediately de-register the UE. Instead, after the expiry of the Mobile Reachable timer, the AMF should clear the PPF and shall start an Implicit De-registration timer, with a relatively large value. The AMF shall stop the Implicit De-registration timer and set the PPF if the AMF moves the UE CM state in the AMF to CM-CONNECTED state. + +NOTE: If the UE CM state in the AMF is CM-IDLE, then AMF considers the UE always unreachable if the UE is in MICO mode (refer to clause 5.4.1.3). + +If the UE indicates an Unavailability Period Duration, then AMF shall consider the UE as unreachable and will not trigger the Paging procedure (e.g. clear the PPF) until the UE registers for normal service again (e.g. set the PPF). Once the event that makes the UE unavailable is completed or cancelled in the UE, the UE shall initiate the registration procedure in order to resume normal service. + +If the PPF is not set, the AMF does not page the UE and shall reject any request for delivering DL signalling or data to this UE. + +If the Implicit De-registration timer expires before the UE contacts the network, the AMF implicitly de-register the UE. + +As part of deregistration for a particular access (3GPP or non-3GPP), the AMF shall request the UE's related SMF to release the PDU Sessions established on that access. + +#### 5.4.1.2 UE reachability allowing mobile terminated data while the UE is CM-IDLE + +The AMF considers a UE in RM-REGISTERED state to be reachable by CN paging if the UE CM state in the AMF is CM-IDLE state unless the UE applies MICO mode or the UE has indicated Unavailability Period Duration.. + +#### 5.4.1.3 Mobile Initiated Connection Only (MICO) mode + +A UE may indicate preference for MICO mode during Initial Registration or Mobility Registration Update procedure. The AMF, based on local configuration, Expected UE Behaviour and/or Network Configuration parameters if available from the UDM, UE indicated preferences, UE subscription information and network policies, or any combination of them, determines whether MICO mode is allowed for the UE and indicates it to the UE during Registration procedure. If NWDAF is deployed, the AMF may also use analytics on UE mobility and/or UE communication generated by + +NWDAF (see TS 23.288 [86]) to decide MICO mode parameters. If the UE does not indicate preference for MICO mode during Registration procedure, the AMF shall not activate MICO mode for this UE. + +The UE and the AMF re-negotiate the MICO mode at every subsequent Registration procedure. When the UE is in CM-CONNECTED, the AMF may deactivate MICO mode by triggering Mobility Registration Update procedure through UE Configuration Update procedure as described in clause 4.2.4 of TS 23.502 [3]. + +The AMF assigns a registration area to the UE during the Registration procedure. When the AMF indicates MICO mode to a UE, the registration area is not constrained by paging area size. If the AMF serving area is the whole PLMN, based on local policy, and subscription information, may decide to provide an "all PLMN" registration area to the UE. In that case, re-registration to the same PLMN due to mobility does not apply. + +If Mobility Restrictions are applied to a UE in MICO mode, the AMF needs to allocate an Allowed Area/Non-Allowed Area to the UE as specified in clause 5.3.4.1. + +When the AMF indicates MICO mode to a UE, the AMF considers the UE always unreachable while the UE CM state in the AMF is CM-IDLE. The AMF rejects any request for downlink data delivery for UE in MICO mode and whose UE CM state in the AMF is CM-IDLE with an appropriate cause. For MT-SMS over NAS, the AMF notifies the SMSF that UE is not reachable, then the procedure of the unsuccessful Mobile terminating SMS delivery described in clause 4.13.3.9 of TS 23.502 [3] is performed. The AMF also defers location services, etc. The UE in MICO mode is only reachable for mobile terminated data or signalling when the UE is in CM-CONNECTED. + +A UE in MICO mode need not listen to paging while in CM-IDLE. A UE in MICO mode may stop any access stratum procedures in CM-IDLE, until the UE initiates transition from CM-IDLE to CM-CONNECTED due to one of the following triggers: + +- A change in the UE (e.g. change in configuration) requires an update of its registration with the network. +- Periodic registration timer expires. +- MO data pending. +- MO signalling pending (e.g. SM procedure initiated). + +If a registration area that is not the "all PLMN" registration area is allocated to a UE in MICO mode, then the UE determines if it is within the registration area or not when it has MO data or MO signalling, and the UE performs Mobility Registration Update before the UE initiates the MO data or MO signalling if it is not within the registration area. + +A UE initiating emergency service shall not indicate MICO preference during Registration procedure. When the MICO mode is already activated in the UE, the UE and AMF shall locally disable MICO mode after PDU Session Establishment procedure for Emergency Services is completed successfully. The UE and the AMF shall not enable MICO mode until the AMF accepts the use of MICO mode in the next registration procedure. To enable an emergency call back, the UE should wait for a UE implementation-specific duration of time before requesting the use of MICO mode after the release of the emergency PDU session. + +In order to enable power saving for MT reachability e.g. for Cellular IoT, enhancements to MICO mode are specified in clause 5.31.7: + +- MICO mode with Extended Connected Time. +- MICO mode with Active Time. +- MICO mode and Periodic Registration Timer Control. + +#### 5.4.1.4 Support of Unavailability Period + +During Registration procedure, the UE supporting the Unavailability Period feature provides "Unavailability Period Support" indication as part of 5GMM Core Network Capability in Registration Request message for initial registration and for every mobility registration. The AMF indicates whether the corresponding feature is supported in the AMF by providing the "Unavailability Period Support" indication in Registration Accept message. + +If the UE and network support Unavailability Period and an event is triggered in the UE that would make the UE unavailable or lose coverage (see clause 5.4.13.1) for a certain period of time, the UE uses Support of Unavailability Period to inform the AMF of the expected unavailability and whether it is due to NR satellite access discontinuous + +coverage. Use of Support of Unavailability Period for loss of coverage due to NR satellite access discontinuous coverage shall only be used if both UE and the AMF signalled "Unavailability Period Support", see clause 5.4.13.1. + +If the use of Support of Unavailability Period procedure is not due to NR satellite access discontinuous coverage, the UE may store its MM and SM context in the USIM or Non-Volatile memory in the ME to be able to reuse it after its unavailability period. If the UE can store its contexts the UE may trigger Mobility Registration Update procedure otherwise the UE shall trigger UE-initiated Deregistration procedure. + +NOTE 1: How and where the UE stores its contexts depends upon the UE implementation and the Unavailability Type. The UE can store some or all of its contexts in the ME or USIM using existing ME or USIM functionality. + +Before the start of an event that makes the UE unavailable, the UE triggers either Mobility Registration Update or UE initiated Deregistration procedure: + +a) If the UE initiates Mobility Registration Update procedure: + +- 0) The UE includes an Unavailability Type to describe the cause of unavailability (e.g. the unavailability caused by NR satellite access discontinuous coverage), the Start of the Unavailability Period if known and the Unavailability Period Duration (if known). +- 1) If the UE did not include a Start of Unavailability Period, the AMF considers implicitly the Start of Unavailability Period to be the time at which it has received the Registration Request message from the UE. If the UE included a Start of Unavailability Period, the Start of Unavailability Period indicates the time at which the UE determines it expects to be unavailable, i.e. time until which the UE determines it is available. +- 2) The AMF may determine, if not provided by the UE, or update the Unavailability Period Duration and/or the Start of Unavailability Period. + +If the AMF knows an Unavailability Period Duration and/or the Start of Unavailability Period (e.g. based on the Unavailability Type and other information available to the AMF as described in clause 5.4.13.3), and the UE did not include an Unavailability Period Duration and/or the Start of Unavailability Period or the UE included an Unavailability Period Duration and/or the Start of Unavailability Period different to the Unavailability Period Duration and/or the Start of Unavailability Period known to the AMF, the AMF may use either the Unavailability Period Duration and/or the Start of Unavailability Period known to the AMF or the Unavailability Period Duration and/or the Start of Unavailability Period from the UE as the Unavailability Period Duration and/or the Start of Unavailability Period. The AMF should include the Unavailability Period Duration and/or the Start of Unavailability Period known to the AMF in the Registration Accept. How the UE treats the AMF provided Unavailability Period Duration and/or the Start of Unavailability Period is up to UE implementation e.g. to help to determine when to return to coverage after a discontinuous coverage period, whether to listen to paging in eDRX, not to initiate any NAS signalling (including Service Request for MO data) within the discontinuous coverage period in case of any UL signalling/data request or the UE may deactivate its Access Stratum functions for NR satellite access in order to optimise power consumption until coverage returns, etc. + +- 3) The AMF indicates to the UE in the Registration Accept whether the UE is not required to perform a Registration procedure when the unavailability period has ended. +- 4) The AMF may take the Unavailability Period Duration (if available) and Start of Unavailability Period into account when determining Periodic Registration Update timer value. The AMF may provide a Periodic Registration Update time longer than or equal to the combination of the Unavailability Period Duration and Start of Unavailability Period to avoid interfering with the UE dealing with the event that causes the unavailability; +- 5) The AMF stores the information that the UE is unavailable at the Start of Unavailability Period in UE context, and considers the UE is unreachable (i.e. clear the PPF in AMF) from then until the UE enters CM-CONNECTED state; +- 6) While the UE is unreachable, all high latency communication solutions (see clause 5.31.8) apply if supported in the network, e.g. extended data buffering, downlink data buffering status report, etc; and +- 7) If there is "Loss of Connectivity" event subscription for the UE by AF, the AMF at the start of Unavailability Period considers the remaining time in the Unavailability Period (if available) when constructing the "Loss of + +Connectivity" event report towards the NEF and the remaining time in the Unavailability Period is reported to the respective subscribed AF. + +b) If the UE initiates UE-initiated Deregistration procedure: + +0) The UE includes Unavailability Period Duration (if known). + +1) If there is "Loss of Connectivity" event subscription for the UE by AF, the AMF considers the remaining time in the Unavailability Period when constructing the "Loss of Connectivity" event report towards the NEF and the Unavailability Period is reported to the respective subscribed AF; + +Unless the AMF indicated that the UE is not required to perform a Registration procedure when the unavailability period has ended, then once the event which makes the UE unavailable is completed in the UE, the UE triggers a Registration procedure. If the event which makes the UE unavailable is delayed to a future time or cancelled in the UE or unavailability period deviates from negotiated value, the UE triggers Registration procedure. The UE may also trigger a Registration procedure before the Unavailability Period has started for other reasons. Depending on the UE state, the Registration procedure can be Initial Registration procedure or Mobility Registration Update procedure. + +While the UE is in 5GS and if the UE determines that an upcoming loss of coverage no longer applies or determines a new Start of Unavailability Period or Unavailability Period Duration related to the upcoming loss of coverage, the UE sends a new Mobility Registration Update Request to the AMF to update the Start of Unavailability Period and/or Unavailability Period Duration. + +The UE and the AMF re-negotiate unavailability at every Registration procedure, if it is required. If Start of Unavailability Period and/or Unavailability Period Duration is not included in a Registration procedure any pending unavailability configuration stored in the UE context at AMF is discarded. + +If the UE moves to EPS, the UE performs Attach or Tracking Area update procedure depending on the interworking mechanisms defined in clause 5.17.2. + +For discontinuous coverage in E-UTRAN satellite access in EPS, the "Unavailability Period" is also supported (see clause 4.13.8.2 of TS 23.401 [26]). + +NOTE 2: In this release of specification there is no transfer of "unavailability period" between AMF and MME and vice versa. + +### 5.4.2 UE reachability in CM-CONNECTED + +For a UE in CM-CONNECTED state: + +- the AMF knows the UE location on a serving (R)AN node granularity. +- the NG-RAN notifies the AMF when UE becomes unreachable from RAN point of view. + +UE RAN reachability management is used by RAN for UEs in RRC\_INACTIVE state, see TS 38.300 [27]. The location of a UE in RRC\_INACTIVE state is known by the RAN on a RAN Notification area granularity. A UE in RRC\_INACTIVE state is paged in cells of the RAN Notification area that is assigned to the UEs. The RAN Notification area can be a subset of cells configured in UE's Registration Area or all cells configured in the UE's Registration Area. UE in RRC\_INACTIVE state performs RAN Notification Area Update when entering a cell that is not part of the RAN Notification area that is assigned to the UE. + +At transition into RRC\_INACTIVE state RAN configures the UE with a periodic RAN Notification Area Update timer value and the timer is restarted in the UE with this initial timer value. After the expiry of the periodic RAN Notification Area Update timer in the UE, the UE in RRC\_INACTIVE state performs periodic RAN Notification Area Update, as specified in TS 38.300 [27]. + +To aid the UE reachability management in the AMF, RAN uses a guard timer with a value longer than the RAN Notification Area Update timer value provided to the UE. Upon the expiry of the periodic RAN Notification Area Update guard timer in RAN, the RAN shall initiate the AN Release procedure as specified in TS 23.502 [3]. The RAN may provide the elapsed time since RAN's last contact with the UE to AMF. + +### 5.4.3 Paging strategy handling + +#### 5.4.3.1 General + +Based on operator configuration, the 5GS supports the AMF and NG-RAN to apply different paging strategies for different types of traffic. + +In the case of UE in CM-IDLE state, the AMF performs paging and determines the paging strategy based on e.g. local configuration, what NF triggered the paging and information available in the request that triggered the paging. If NWDAF is deployed, the AMF may also use analytics (i.e. statistics or predictions) on the UE's mobility as provided by NWDAF (see TS 23.288 [86]). + +In the case of UE in CM-CONNECTED with RRC\_INACTIVE state, the NG-RAN performs paging and determines the paging strategy based on e.g. local configuration, and information received from AMF as described in clause 5.4.6.3 and SMF as described in clause 5.4.3.2. + +In the case of Network Triggered Service Request from SMF, the SMF determines the 5QI and ARP based on the downlink packet (if the SMF performs buffering) or the Downlink Data Report received from UPF (if the UPF performs buffering). The SMF includes the 5QI and ARP corresponding to the QoS Flow of the received downlink PDU in the request sent to the AMF. If the UE is in CM IDLE, the AMF uses e.g. the 5QI and ARP to derive different paging strategies as described in clause 4.2.3.3 of TS 23.502 [3]. + +NOTE: The 5QI is used by AMF to determine suitable paging strategies. + +#### 5.4.3.2 Paging Policy Differentiation + +Paging policy differentiation is an optional feature that allows the AMF, based on operator configuration, to apply different paging strategies for different traffic or service types provided within the same PDU Session. In this Release of the specification this feature applies only to PDU Session of IP type. + +When the 5GS supports the Paging Policy Differentiation (PPD) feature, the DSCP value (TOS in IPv4 / TC in IPv6) is set by the application to indicate to the 5GS which Paging Policy should be applied for a certain IP packet. For example, as defined in TS 23.228 [15], the P-CSCF may support Paging Policy Differentiation by marking packet(s) to be sent towards the UE that relate to a specific IMS services (e.g. conversational voice as defined in IMS multimedia telephony service). + +NOTE 1: This PPD feature may be used to determine the Paging Cause Indication for Voice Service, as described in clause 5.38.3. + +It shall be possible for the operator to configure the SMF in such a way that the Paging Policy Differentiation feature only applies to certain HPLMNs, DNNs and 5QIs. In the case of HR roaming, this configuration is done in the SMF in the VPLMN. + +NOTE 2: Support of Paging Policy Differentiation in the case of HR roaming requires inter operator agreements including on the DSCP value associated with this feature. + +In the case of Network Triggered Service Request and UPF buffering downlink packets, the UPF shall include the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the downlink packet and an indication of the corresponding QoS Flow in the Downlink Data Report sent to the SMF. When PPD applies, the SMF determines the Paging Policy Indicator (PPI) based on the DSCP received from the UPF. + +In the case of Network Triggered Service Request and SMF buffering downlink packets, when PPD applies, the SMF determines the PPI based on the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the received downlink packet and identifies the corresponding QoS Flow from the QFI of the received downlink packet. + +The SMF includes the PPI, the ARP and the 5QI of the corresponding QoS Flow in the N11 message sent to the AMF. If the UE is in CM IDLE, the AMF uses this information to derive a paging strategy, and sends paging messages to NG-RAN over N2. + +NOTE 3: Network configuration needs to ensure that the information used as a trigger for Paging Policy Indication is not changed within the 5GS. + +NOTE 4: Network configuration needs to ensure that the specific DSCP in TOS (IPv4) / TC (IPv6) value, used as a trigger for Paging Policy Indication, is managed correctly in order to avoid the accidental use of certain paging policies. + +For a UE in RRC\_INACTIVE state the NG-RAN may enforce specific paging policies in the case of NG-RAN paging, based on 5QI, ARP and PPI associated with an incoming DL PDU. To enable this, the SMF instructs the UPF to detect the DSCP in the TOS (IPv4) / TC (IPv6) value in the IP header of the DL PDU (by using a DL PDR with the DSCP for this traffic) and to transfer the corresponding PPI in the CN tunnel header (by using a QER with the PPI value). The NG-RAN can then utilize the PPI received in the CN tunnel header of an incoming DL PDU in order to apply the corresponding paging policy for the case the UE needs to be paged when in RRC\_INACTIVE state. In the case of Home-Routed roaming, the V-SMF is responsible of controlling UPF setting of the PPI. In the case of PDU Session with I-SMF, the I-SMF is responsible of controlling UPF setting of the PPI. + +#### 5.4.3.3 Paging Priority + +Paging Priority is a feature that allows the AMF to include an indication in the Paging Message sent to NG-RAN that the UE be paged with priority. The decision by the AMF whether to include Paging Priority in the Paging Message is based on the ARP value in the message received from the SMF for an IP packet waiting to be delivered in the UPF. If the ARP value is associated with select priority services (e.g. MPS, MCS), the AMF includes Paging Priority in the Paging Message. When the NG-RAN receives a Paging Message with Paging Priority, it handles the page with priority. + +The AMF while waiting for the UE to respond to a page sent without priority receives another message from the SMF with an ARP associated with select priority services (e.g. MPS, MCS), the AMF sends another Paging message to the (R)AN including the Paging Priority. For subsequent messages, the AMF may determine whether to send the Paging message with higher Paging Priority based on local policy. + +For a UE in RRC\_INACTIVE state, the NG-RAN determines Paging Priority based on the ARP associated with the QoS Flow as provisioned by the operator policy, and the Core Network Assisted RAN paging information from AMF as described in clause 5.4.6.3. + +### 5.4.4 UE Radio Capability handling + +#### 5.4.4.1 UE radio capability information storage in the AMF + +This clause applies when no radio capability signalling optimisation is used between a UE and the network. + +The UE Radio Capability information is defined in TS 38.300 [27] and contains information on RATs that the UE supports (e.g. power class, frequency bands, etc). Consequently, this information can be sufficiently large that it is undesirable to send it across the radio interface at every transition of UE CM state in the AMF from CM-IDLE to CM-CONNECTED. To avoid this radio overhead, the AMF shall store the UE Radio Capability information during CM-IDLE state for the UE and RM-REGISTERED state for the UE and the AMF shall if it is available, send its most up to date UE Radio Capability information to the RAN in the N2 REQUEST message, i.e. INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY CHECK REQUEST. + +NOTE 1: Due to issues with the handling of dynamic UMTS security parameters, the UTRA UE Radio Capability information is excluded from the information that is uploaded and stored in the AMF (see TS 38.300 [27]). + +The AMF deletes the UE radio capability when the UE RM state in the AMF transitions to RM-DEREGISTERED. When the AMF receives Registration Request with the Registration type set to Initial Registration or when it receives the first Registration Request after E-UTRA/EPC Attach with Registration type set to Mobility Registration Update, the AMF deletes the UE radio capability. + +The UE Radio Capability is maintained in the core network, even during AMF reselection. + +NOTE 2: The UE Radio Capability is not transferred to EPC during the inter-system mobility. + +If the UE's NG-RAN or E-UTRAN UE Radio Capability information changes while in CM-IDLE state, the UE shall perform the Registration procedure with the Registration type set to Mobility Registration Update and it also includes "UE Radio Capability Update". (For specific requirements for a UE operating in dual-registration mode see clause 5.17.2.1). When the AMF receives Mobility Registration Update Request with "UE Radio Capability Update" requested by the UE, it shall delete any UE Radio Capability information that it has stored for the UE. If the UE's NG- + +RAN UE Radio Capability information changes when the UE is in CM-IDLE with Suspend, NAS shall trigger AS to establish a new RRC connection and not resume the existing one in order to perform the Registration procedure with the Registration type set to Mobility Registration Update including "UE Radio Capability Update". As a result of this, the access stratum in the UE will discard the AS information and establish a new RRC connection as defined in TS 36.331 [51]. + +If the trigger to change the UE's NG-RAN or E-UTRAN UE Radio Capability information happens when the UE is in CM-CONNECTED state, the UE shall first enter CM-IDLE state and then perform the Registration procedure with the Registration type set to Mobility Registration Update and it also includes "UE Radio Capability Update". + +The RAN stores the UE Radio Capability information, received in the N2 message or obtained from the UE, for the duration of the UE staying in RRC\_CONNECTED or RRC\_INACTIVE state. Before any 5G SRVCC handover attempt from NG-RAN to UTRAN, the RAN retrieves the UE's UTRA UE Radio Capabilities from the UE. (For specific requirements for a UE operating in dual-registration mode see clause 5.17.2.1). + +If the AMF sends N2 REQUEST (i.e. INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY CHECK REQUEST) message to NG-RAN without UE Radio Capability information in that message and there is no UE Radio Capability information available in RAN, this triggers the RAN to request the UE Radio Capability from the UE and to upload it to the AMF in the N2 UE RADIO CAPABILITY INFO INDICATION message. + +If a UE supports both NB-IoT and other RATs the UE handles the UE Radio capability information as follows: + +- When the UE is camping on NB-IoT the UE provides only NB-IoT UE radio capabilities to the network. +- When the UE is not camping on NB-IoT, the UE provides UE radio capabilities for the RAT but not NB-IoT UE radio capabilities to the network. + +In order to handle the distinct UE radio capabilities, the AMF stores a separate NB-IoT specific UE Radio Capability information when the UE provides the UE Radio Capability information while camping on NB-IoT. + +When the UE is camping on NB-IoT, the AMF sends, if available, the NB-IoT RAT specific UE Radio Capability information to the E-UTRAN. + +When the UE is not camping on NB-IoT, the AMF sends, if available, UE radio capabilities for the RAT but not NB-IoT radio capabilities. + +##### 5.4.4.1a UE radio capability signalling optimisation (RACS) + +With the increase of the size of UE radio capabilities driven e.g. by additional frequency bands and combinations thereof for E-UTRA and NR, an efficient approach to signal UE Radio Capability Information over the radio interface and other network interfaces is defined with RACS. + +In this Release of the specification, RACS does not apply to NB-IoT. + +RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called UE Radio Capability ID. A UE Radio Capability ID can be either UE manufacturer-assigned or PLMN-assigned, as specified in clause 5.9.10. The UE Radio Capability ID is an alternative to the signalling of the UE Radio Capability information over the radio interface, within NG-RAN, from NG-RAN to E-UTRAN, from AMF to NG-RAN and between CN nodes supporting RACS. + +PLMN-assigned UE Radio Capability ID is assigned to the UE using the UE Configuration Update Command, or Registration Accept as defined in TS 23.502 [3]. The UCMF shall be configured with a Version ID for PLMN-assigned UE Radio Capability IDs, defined in clause 5.9.10. + +The UCMF (UE radio Capability Management Function) stores all UE Radio Capability ID mappings in a PLMN and is responsible for assigning every PLMN-assigned UE Radio Capability ID in this PLMN, see clause 6.2.21. The UCMF stores the UE Radio Capability IDs alongside the UE Radio Capability information and the UE Radio Capability for Paging they map to. Each UE Radio Capability ID stored in the UCMF can be associated to one or both UE radio capabilities formats specified in TS 36.331 [51] and TS 38.331 [28]. The two UE radio capabilities formats shall be identifiable by the AMF and UCMF and the AMF shall store the TS 38.331 [28] format only. + +An NG-RAN which supports RACS can be configured to operate with one of two modes of operation when providing the UE radio capabilities to the AMF when the NG-RAN executes a UE Radio Capability Enquiry procedure (see TS 38.331 [28]) to retrieve UE radio capabilities from the UE: + +- Mode of operation A): The NG-RAN provides to the AMF both formats (i.e. the TS 38.331 [28] format and TS 36.331 [51] format). The NG-RAN derives one of the UE Radio Capability formats using local transcoding of the other format it receives from the UE and extracts the E-UTRAN UE Radio Capability for Paging and NR UE Radio Capability for Paging from the UE Radio capabilities. +- Mode of operation B): The NG-RAN provides to the AMF the TS 38.331 [28] format only. + +In a PLMN supporting RACS only in 5GS, Mode of Operation B shall be configured. + +If the PLMN supports RACS in both EPS and 5GS: + +- If RAN nodes in the EPS and 5GS are configured in Mode of operation B, then the UCMF shall be capable to transcode between TS 36.331 [51] and TS 38.331 [28] formats and the UCMF shall be able to generate the RAT-specific UE Radio Capability for Paging information from the UE Radio Capability. +- If the NG-RAN is configured to operate according to Mode A, then also the E-UTRAN shall be configured to operate according to mode A and the UCMF is not required to transcode between TS 36.331 [51] and TS 38.331 [28] formats and the AMF shall provide the UE Radio Capability for Paging information. + +When the NG-RAN updates the AMF with new UE radio capabilities information, the AMF provides the information obtained from the NG-RAN to the UCMF even if the AMF already has a UE Radio Capability ID for that UE. The UCMF then returns a value of UE Radio Capability ID. If the value is different from the one stored in the AMF, the AMF updates the UE Radio Capability ID it stores and provides this new value to the NG-RAN (if applicable) and to the UE. + +In order to be able to interpret the UE Radio Capability ID a Network Function or node may store a local copy of the mapping between the UE Radio Capability ID and its corresponding UE Radio Capability information i.e. a dictionary entry. When no mapping is available between a UE Radio Capability ID and the corresponding UE Radio Capability information in a Network Function or node, this Network Function or node shall be able to retrieve this mapping and store it. + +- An AMF which supports RACS shall store such UE Radio Capability ID mapping at least for all the UEs that it serves that have a UE Radio Capability ID assigned. +- The NG-RAN performs local caching of the UE Radio Capability information for the UE Radio Capability IDs for the UEs it is serving, and potentially for other UE Radio Capability IDs according to suitable local policies. +- When the NG-RAN needs to retrieve the mapping of a UE Radio Capability ID to the corresponding UE Radio Capability information, it queries the AMF using N2 signalling defined in TS 38.413 [34]. +- When the AMF needs to obtain a PLMN-assigned UE Radio Capability ID for a UE from the UCMF, it provides the UE Radio Capability information it has for the current radio configuration of the UE and the IMEI/TAC for the UE and the UCMF returns a UE Radio Capability ID. The AMF shall provide to the UCMF the UE Radio Capability information (and at least in Mode A, the UE Radio Capability for Paging) obtained from the NG-RAN in one or both the TS 36.331 [51] and TS 38.331 [28] formats depending on how the RAN is configured. The UCMF stores the association of this IMEI/TAC with this UE Radio Capability ID and the UE Radio Capability information and the UE Radio Capability for Paging in all the formats it receives. The UE Radio Capability information formats the AMF provides shall be identifiable at the UCMF. +- When the AMF needs to obtain the UE Radio Capability information and the UE Radio Capability for Paging associated to a UE Radio Capability ID it provides the UE Radio Capability ID to the UCMF with an indication that it is requesting the TS 38.331 [28] format and the UCMF returns a mapping of the UE Radio Capability ID to the corresponding UE Radio Capability information in TS 38.331 [28] format to the AMF. +- UEs, AMFs and RAN nodes which support RACS learn the current value of the Version ID when a new PLMN-assigned UE Radio Capability ID is received from the UCMF and the Version ID it contains is different from the ones in their PLMN Assigned UE Radio Capability ID cache. For a PLMN, PLMN-assigned UE Radio Capability IDs related to old values (i.e. not current value) of the Version ID can be removed from cache but, if so, prior to removing any cached PLMN-assigned UE radio Capability IDs with the current value of the Version ID. The AMF, RAN and UE may continue to use the stored PLMN assigned UE Radio Capability IDs with old values of the Version ID, until these are purged from cache. If an out of date PLMN assigned UE Radio Capability ID is removed from an AMF cache, the AMF shall proceed to assign a new PLMN assigned UE Radio Capability ID to all the UEs for which the UE context includes the removed PLMN-assigned UE Radio Capability ID using a UE Configuration Update procedure, or when these UEs perform a Registration. If the + +AMF attempts to resolve a PLMN assigned UE Radio capability ID with an old Version ID, the UCMF shall return an error code indicating that the Version ID in the UE radio capability ID is no longer current and proceed to assign a new UE Radio Capability ID to the UE. + +If at any time the AMF has neither a valid UE Radio Capability ID nor any stored UE radio capabilities for the UE, the AMF may trigger the RAN to provide the UE Radio Capability information and subsequently request the UCMF to allocate a UE Radio Capability ID. + +- The RAN, in order to support MOCN network sharing scenarios, shall be capable to cache PLMN assigned UE Radio Capability IDs per PLMN ID. + +A network may utilise the PLMN-assigned UE Radio Capability ID, without involving the UE, e.g. for use with legacy UEs. + +Mutual detection of the support of the RACS feature happens between directly connected NG-RAN nodes and between NG-RAN and AMF using protocol means as defined in TS 38.413 [34] and TS 38.423 [99]. To allow for a mix of RACS-supporting and non-RACS-supporting RAN nodes over the Xn interfaces, the UE Radio Capability ID should be included in the Path Switch signalling during Xn based handover and Handover Request during N2 based handover between AMF and NG-RAN. In addition, RACS-supporting RAN nodes can be discovered across inter-CN node boundaries by using the mechanism defined in TS 38.413 [34] that allows the source NG-RAN node to retrieve information on the level of support for a certain feature at the target NG-RAN side by means of information provided within the Source to Target and Target to Source transparent handover containers during handover procedure. The support of RACS by peer AMFs or MMEs is based on configuration in a PLMN or across PLMNs. + +A UE that supports WB-E-UTRA and/or NR indicates its support for RACS to AMF using UE MM Core Network Capability as defined in clause 5.4.4a. + +A UE that supports RACS and stores an applicable UE Radio Capability ID for the current UE Radio Configuration in the PLMN, shall signal the UE Radio Capability ID in the Initial, and Mobility Registration procedure as defined in TS 23.502 [3] and based on triggers defined in TS 24.501 [47]. If both PLMN-assigned for the current PLMN and UE manufacturer-assigned UE Radio Capability IDs are stored in the UE and applicable in the PLMN, the UE shall signal the PLMN-assigned UE Radio Capability ID in the Registration Request message. + +When a PLMN decides to switch to request a particular type of UE to use UE manufacturer-assigned UE Radio Capability ID(s): + +- The UCMF sends a Nucmf\_UECapabilityManagement\_Notify message to the AMF including either a list of UE Radio Capability IDs (if the UE was previously using any PLMN-assigned IDs) or the IMEI/TAC values corresponding to UE types that are requested to use UE manufacturer-assigned UE Radio Capability ID. These values are stored in a "UE Manufacturer Assigned operation requested list" in the AMF. +- The AMF uses the Registration Accept message or the UE Configuration Update command message to request the UE to delete all the PLMN-assigned UE Radio Capability ID(s) for this PLMN if the UE is, respectively, registering or is registered with PLMN-assigned ID or IMEI/TAC values matching one value in the "UE Manufacturer Assigned operation requested list". + +NOTE 1: It is expected that in a given PLMN the UCMF and AMFs will be configured to either use a UE manufacturer-assigned operation requested list based on a list of PLMN-assigned UE Radio Capability IDs or a list of IMEI/TACs, but not both. + +NOTE 2: The strategy for triggering of the deletion of PLMN-assigned UE Radio Capability ID(s) in the UE by the AMF is implementation-specific (e.g. can be used only towards UEs in CM-CONNECTED state). + +- a UE that receives indication to delete all the PLMN-assigned UE Radio Capability IDs in the Registration Accept message, or UE Configuration Update command message, shall delete any PLMN-assigned UE Radio Capability IDs for this PLMN. The UE proceeds to register with a UE manufacturer-assigned UE Radio Capability ID that is applicable to the current UE Radio configuration. +- When the "UE Manufacturer Assigned operation requested list" contains PLMN-assigned UE Radio Capability IDs, the UCMF shall avoid re-assigning PLMN-assigned UE Radio Capability IDs that were added to the "UE Manufacturer Assigned operation requested list" in the AMFs to any UE. +- The AMF stores a PLMN-assigned ID in the "UE Manufacturer Assigned operation requested list" for a time duration that is implementation specific, but IMEI/TACs are stored until the UCMF require to remove certain + +TACs from the list (i.e. the list of IMEI/TACs which are requested to use UE manufacturer-assigned IDs in the AMF and UCMF is synchronised at all times). + +- The UCMF can request at any time the AMF to remove PLMN-assigned ID(s) or IMEI/TAC(s) values from the UE manufacturer-assigned operation requested list. + +NOTE 3: The AMF can decide to remove a UE Radio Capability ID from the "UE Manufacturer Assigned operation requested list" list e.g. because no UE with that UE Radio Capability ID has connected to the network for long time. If later a UE with such UE Radio Capability ID connects to the network, the AMF contacts the UCMF to resolve the UE Radio Capability ID, and at this point the UCMF can trigger again the deletion of the UE Radio Capability ID by including this in the "UE Manufacturer Assigned operation requested list" of the AMF. + +The serving AMF stores the UE Radio Capability ID related to selected PLMN for a UE in the UE context and provides this UE Radio Capability ID to NG-RAN as part of the UE context information using N2 signalling. During inter PLMN mobility, the new AMF shall delete the UE Radio Capability ID received from the old AMF, unless the operator policy indicates that all UE Radio Capability IDs used in the old PLMN is also valid in the new PLMN. + +NOTE 4: If AMF decides to allocate TAIs of multiple PLMN IDs as part of Registration Area to the UE then AMF provides the UE Radio Capability ID of the new selected PLMN to the NG-RAN during UE mobility, whether the UE Radio Capability ID is taken from stored UE context previously assigned by the same new selected PLMN or generated freshly each time a new PLMN is selected is up to AMF implementation. + +The UE stores the PLMN-assigned UE Radio Capability ID in non-volatile memory when in RM-DEREGISTERED state and can use it again when it registers in the same PLMN. + +NOTE 5: It is assumed that UE does not need to store the access stratum information (i.e. UE-E-UTRA-Capability and UE-NR-Capability specified in TS 36.331 [51] and TS 38.331 [28], respectively) that was indicated by the UE to the network when the PLMN-assigned UE Radio Capability ID was assigned by the network. However, it is assumed that the UE does store the related UE configuration (e.g. whether or not GERAN or UTRAN or MBMS is enabled/disabled). + +At any given time at most one UE Radio Capability ID is used from the UE context in CN and RAN which is related to the selected PLMN. + +The number of PLMN-assigned UE Radio Capability IDs that the UE stores in non-volatile memory is left up to UE implementation. However, to minimise the load (e.g. from radio signalling) on the Uu interface and to provide smoother inter-PLMN mobility (e.g. at land borders) the UE shall be able to store at least the latest 16 PLMN-assigned UE Radio Capability IDs (along with the PLMN that assigned them). This number is independent of the UE manufacturer-assigned UE Radio Capability ID(s) the UE may store. + +It shall be possible for a UE to change, e.g. upon change in its usage settings, the set of UE radio capabilities in time and signal the associated UE Radio Capability ID, if available. The UE stores the mapping between the UE Radio Capability ID and the corresponding UE Radio Capability Information for every UE Radio Capability ID it stores. + +If the UE's Radio Capability Information changes and regardless of whether the UE has an associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall perform the Registration procedure by sending a Registration Request message to the AMF with the Registration type set to Mobility Registration Update which includes "UE Radio Capability Update" and: + +- If the UE has an associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall include it in the Registration Request message so that the AMF, upon receiving it, shall update the UE's context with this UE Radio Capability ID. +- If the UE does not have an associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall not include any UE Radio Capability ID in the Registration Request message so that the AMF, upon receiving this Registration Request without any UE Radio Capability ID, retrieves the UE radio capabilities from the UE as defined in clause 5.4.4.1. + +The NG-RAN may apply RRC filtering of UE radio capabilities when it retrieves the UE Radio Capability Information from the UE as defined in TS 38.331 [28]. + +NOTE 6: In a RACS supporting PLMN, the filter of UE radio capabilities configured in NG-RAN is preferably as wide in scope as possible (e.g. PLMN-wide). In this case, it corresponds e.g. to the super-set of bands, band-combinations and RATs the PLMN deploys and not only to the specific NG-RAN node or region. + +NOTE 7: If the filter, included in the UE Radio Capability information, of UE radio capabilities configured in two NG-RAN nodes is different, during handover between these two nodes, it is possible that the target NG-RAN node might need to enquire the UE for its UE Radio Capability Information again and trigger re-allocation of a PLMN-assigned UE Radio Capability ID leading to extra signalling. Additionally, a narrow filter might reduce the list of candidate target nodes. + +If a UE supports both NB-IoT and other RATs that do support RACS (e.g. WB-E-UTRA and/or NR) then (since there is no support for RACS in NB-IoT) the UE handles the RACS procedures as follows: + +- NB-IoT specific UE Radio Capability Information is handled in UE, NG-RAN and AMF according to clause 5.4.4.1 and in EPS according to TS 23.401 [26]. +- when the UE is not camping on NB-IoT, the RAN provides UE radio capabilities for other RATs but not NB-IoT UE radio capabilities, according to TS 38.300 [27] and TS 36.300 [30]. As a result the UE Radio Capability ID that is assigned by the network corresponds only to the UE radio capabilities of the non-NB-IoT RATs. The UE uses the UE Radio Capability IDs assigned only in Mobility Registration Update procedures performed over non-NB-IoT RATs. + +Support for RACS in EPS is defined in TS 23.401 [26]. + +#### 5.4.4.2 Void + +##### 5.4.4.2a UE Radio Capability Match Request + +If the AMF requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.16.3), then the AMF may send a UE Radio Capability Match Request message to the NG-RAN. This procedure is typically used during the Registration Procedure or when AMF has not received the Voice Support Match Indicator (as part of the 5GMM Context). + +NOTE: During the Registration Procedure, if the AMF does not already have the UEs radio capabilities, and if the RAT where the UE is requires the establishment of AN security context prior to retrieval of radio capabilities, the AMF needs to initiate "Initial Context Setup" procedure as defined in TS 38.413 [34] to provide the 5G-AN with security context, before sending a UE Radio Capability Match Request message. + +#### 5.4.4.3 Paging assistance information + +The paging assistance information contains UE radio related information that assists the RAN for efficient paging. The Paging assistance information contains: + +a) UE radio capability for paging information: + +- The UE Radio Capability for Paging Information contains information derived by the NG-RAN node (e.g. band support information) from the UE Radio Capability information. The AMF stores this information without needing to understand its contents. + +As the AMF only infrequently (e.g. at Initial Registration) prompts the NG-RAN to retrieve and upload the UE radio capabilities i.e. UE Radio Capability information to the AMF, and the AMF may be connected to more than one NG-RAN RAT, it is the responsibility of the NG-RAN to ensure that UE Radio Capability for Paging Information (which is derived by the NG-RAN node) contains information on all NG-RAN RATs that the UE supports in that PLMN. To assist the NG-RAN in this task, as specified in TS 38.413 [34], the AMF provides its stored UE Radio Capability for Paging Information in every NG-AP INITIAL CONTEXT SETUP REQUEST message sent to the NG-RAN. + +- The UE Radio Capability for Paging Information is maintained in the core network, even during AMF reselection, and is stored in the UCMF alongside the UE Radio Capability information associated to a UE Radio Capability ID. + +##### b) Information On Recommended Cells And RAN nodes For Paging: + +- Information sent by the NG-RAN, and used by the AMF when paging the UE to help determining the NG RAN nodes to be paged as well as to provide the information on recommended cells to each of these RAN nodes, in order to optimize the probability of successful paging while minimizing the signalling load on the radio path. +- The RAN provides this information during N2 release. + +### 5.4.4a UE MM Core Network Capability handling + +The UE MM Core Network Capability is split into the S1 UE network capability (mostly for E-UTRAN access related core network parameters) and the UE 5GMM Core Network Capability (mostly to include other UE capabilities related to 5GCN or interworking with EPS) as defined in TS 24.501 [47] and contains non radio-related capabilities, e.g. the NAS security algorithms, etc. The S1 UE network capability is transferred between all CN nodes at AMF to AMF, AMF to MME, MME to MME, and MME to AMF changes. The UE 5GMM Core Network Capability is transferred only at AMF to AMF changes. + +In order to ensure that the UE MM Core Network Capability information stored in the AMF is up to date (e.g. to handle the situation when the USIM is moved into a different device while out of coverage, and the old device did not send the Detach message; and the cases of inter-RAT Registration Area Update), the UE shall send the UE MM Core Network Capability information to the AMF during the Initial Registration and Mobility Registration Update procedure within the NAS message. + +The AMF shall store always the latest UE MM Core Network Capability received from the UE. Any UE MM Core Network Capability that an AMF receives from an old AMF/MME is replaced when the UE provides the UE MM Core Network Capability with Registration signalling. + +If the UE's UE MM Core Network Capability information changes (in either CM-CONNECTED or in CM-IDLE state), the UE shall perform a Mobility Registration Update procedure when it next returns to NG-RAN coverage. See clause 4.2.2 of TS 23.502 [3]. + +The UE shall indicate in the UE 5GMM Core Network Capability if the UE supports: + +- Attach in EPC with Request type "Handover" in PDN CONNECTIVITY Request message (clause 5.3.2.1 of TS 23.401 [26]). +- EPC NAS. +- SMS over NAS. +- LCS. +- 5G SRVCC from NG-RAN to UTRAN, as specified in TS 23.216 [88]. +- Radio Capabilities Signalling optimisation (RACS). +- Network Slice-Specific Authentication and Authorization. +- Network Slice Replacement as described in clause 5.15.19. +- Parameters in Supported Network Behaviour for 5G CIoT as described in clause 5.31.2. +- Receiving WUS Assistance Information (E-UTRA) see clause 5.4.9. +- Paging Subgrouping Support Indication (NR) see clause 5.4.12. +- CAG, see clause 5.30.3.3. +- CAG with validity information (if UE supports CAG), see clause 5.30.3.3. +- Subscription-based restrictions to simultaneous registration of network slices (see clause 5.15.12). +- Support of NSAG (see clause 5.15.14). +- Partial Network Slice support in a RA (see clause 5.15.17). + +- Minimization of Service Interruption (MINT), as described in clause 5.40. +- Equivalent SNPNs (see clause 5.30.2.11). +- Unavailability Period Support, as described in clause 5.4.1.4. +- Support for network reconnection due to RAN timing synchronization status change, see clause 5.3.4.4. +- UE Configuration of network-controlled Slice Usage Policy (see clause 5.15.15.2). +- Temporarily available network slices (see clause 5.15.16). +- Support of S-NSSAI location availability information, as described in clause 5.15.18.2. + +If a UE operating two or more USIMs, supports and intends to use one or more Multi-USIM features (see clause 5.38) in a PLMN for a USIM, it shall indicate in the UE 5GMM Core Network Capability for this USIM in this PLMN that it supports these one or more Multi-USIM features with the following indications: + +- Connection Release Supported. +- Paging Cause Indication for Voice Service Supported. +- Reject Paging Request Supported. +- Paging Restriction Supported. + +Otherwise, the UE with the capabilities of Multi-USIM features but does not intend to use them shall not indicate support of these one or more Multi-USIM features. + +A UE not operating two or more USIMs shall indicate the Multi-USIM features are not supported. + +NOTE: It is not necessary for a UE operating two or more USIMs to use Multi-USIM features with all USIMs. + +#### 5.4.4b UE 5GSM Core Network Capability handling + +The UE 5GSM Core Network Capability is included in PDU Session Establishment/Modification Request. + +The UE shall indicate in the UE 5GSM Core Network Capability whether the UE supports: + +- "Ethernet" PDU Session Type supported in EPC as PDN Type "Ethernet"; +- Reflective QoS; +- Multi-homed IPv6 PDU Session (only if the Requested PDU Type was set to "IPv6" or "IPv4v6"); +- ATSSS capability (as referred to clause 5.32.2); +- Transfer of Port Management Information containers; +- Support for secondary DN authentication and authorization over EPC (as referred to clause 5.17.2.5). + +The 5GSM Core Network Capability is transferred, if needed, from V-SMF to H-SMF during PDU Session Establishment/Modification procedure. + +After the first inter-system change from EPS to 5GS for a PDU session established in EPS, the 5GSM Core Network Capability is also included in the PDU Session Modification if the Reflective QoS and/or Multi-homed IPv6 PDU Session is present. + +### 5.4.5 DRX (Discontinuous Reception) framework + +The 5G System supports DRX architecture which allows Idle mode DRX cycle is negotiated between UE and the AMF. The Idle mode DRX cycle applies in CM-IDLE state and in CM-CONNECTED with RRC\_INACTIVE state. + +If the UE wants to use UE specific DRX parameters, the UE shall include its preferred values consistently in every Initial Registration and Mobility Registration procedure separately for NR/WB-EUTRA and NB-IoT. During Initial Registration and Mobility Registration procedures performed on NB-IoT cells, the normal 5GS procedures apply. For + +NB-IoT, the cell broadcasts an indication of support of UE specific DRX for NB-IoT in that cell, and the UE can request UE specific DRX for NB-IoT in the Registration procedure irrespective of whether the cell broadcasts that support indication. + +The AMF shall determine Accepted DRX parameters based on the received UE specific DRX parameters and the AMF should accept the UE requested values, but subject to operator policy the AMF may change the UE requested values. + +The AMF shall respond to the UE with the Accepted DRX parameters separately for NR/WB-EUTRA and NB-IoT. + +For details of DRX parameters, see TS 38.331 [28] and TS 36.331 [51]. + +The UE shall apply the DRX cycle broadcast in the cell by the RAN unless it has received Accepted DRX parameters for the RAT from the AMF and for NB-IoT the cell supports UE specific DRX for NB-IoT, in which case the UE shall apply either the DRX cycle broadcast in the cell or the Accepted DRX parameters for the RAT, as defined in TS 38.304 [50] and TS 36.304 [52]. + +The Periodic Registration procedure does not change the UE's DRX settings. + +In CM-CONNECTED with RRC\_INACTIVE state, the UE applies either the DRX cycle negotiated with AMF, or the DRX cycle broadcast by RAN or the UE specific DRX cycle configured by RAN, as defined in TS 38.300 [27] and TS 38.304 [50]. + +### 5.4.6 Core Network assistance information for RAN optimization + +#### 5.4.6.1 General + +Core Network assistance information for RAN aids the RAN to optimize the UE state transition steering and the RAN paging strategy formulation in RRC\_INACTIVE state. The Core Network assistance information includes the information set, Core Network assisted RAN parameters tuning, which assist RAN optimize the UE RRC state transition and CM state transition decision. It also includes the information set, Core Network assisted RAN paging information, which assist RAN to formulate an optimized paging strategy when RAN paging is triggered. + +#### 5.4.6.2 Core Network assisted RAN parameters tuning + +Core Network assisted RAN parameters tuning aids the RAN to minimize the UE state transitions and achieve optimum network behaviour. How the RAN uses the CN assistance information is not defined in this specification. + +Core Network assisted RAN parameters tuning may be derived by the AMF per UE in the AMF based on collection of UE behaviour statistics, Expected UE Behaviour and/or other available information about the UE (such as subscribed DNN, SUPI ranges, or other information). If the AMF maintains Expected UE Behaviour parameters, Network Configuration parameters (as described in clause 4.15.6.3 or 4.15.6.3a, TS 23.502 [3]) or SMF derived CN assisted RAN parameters tuning, the AMF may use this information for selecting the CN assisted RAN parameter values. If the AMF is able to derive the Mobility Pattern of the UE (as described in clause 5.3.4.2), the AMF may take the Mobility Pattern information into account when selecting the CN assisted RAN parameter values. + +The SMF uses the SMF-Associated parameters (e.g. Expected UE Behaviour parameters or Network Configuration parameters of the UE) to derive the SMF derived CN assisted RAN parameters tuning. The SMF sends the SMF derived CN assisted RAN parameters tuning to the AMF during the PDU Session establishment procedure and if the SMF-Associated parameters change the PDU Session modification procedure is applied. The AMF stores the SMF derived CN assisted RAN parameters tuning in the PDU Session level context. The AMF uses the SMF derived CN assisted RAN parameters tuning to determine a PDU Session level "Expected UE activity behaviour" parameters set, which may be associated with a PDU Session ID, as described below in this clause. + +The Expected UE Behaviour parameters or the Network Configuration parameters can be provisioned by external party via the NEF to the AMF or SMF, as described in clause 5.20. + +The CN assisted RAN parameters tuning provides the RAN with a way to understand the UE behaviour for these aspects: + +- "Expected UE activity behaviour", i.e. the expected pattern of the UE's changes between CM-CONNECTED and CM-IDLE states or the duration of CM-CONNECTED state. This may be derived e.g. from the statistical information, or Expected UE Behaviour or from subscription information. The AMF derives one or more sets of the "Expected UE activity behaviour" parameters for the UE as follows: + +- AMF may derive and provide to the RAN a UE level of "Expected UE activity behaviour" parameters set considering the Expected UE Behaviour parameters or Network Configuration parameters received from the UDM (see clauses 4.15.6.3 or 4.15.6.3a of TS 23.502 [3]) and the SMF derived CN assisted RAN parameters tuning associated with a PDU Session using Control Plane CIoT 5GS Optimisation. This set of "Expected UE activity behaviour" parameters is valid for the UE; and +- AMF may provide to the RAN a PDU Session level "Expected UE activity behaviour" parameters set, e.g. considering the SMF derived CN assisted RAN parameters tuning, per established PDU Session. The PDU Session level "Expected UE activity behaviour" set of parameters is associated with and valid for a PDU Session ID. The RAN may consider the PDU Session level "Expected UE activity behaviour" parameters when the User Plane resources for the PDU Session are activated; +- "Expected HO behaviour", i.e. the expected interval between inter-RAN handovers. This may be derived by the AMF e.g. from the Mobility Pattern information; +- "Expected UE mobility", i.e. whether the UE is expected to be stationary or mobile. This may be derived e.g. from the statistical information or Expected UE Behaviour parameters or from subscription information; +- "Expected UE moving trajectory" which may be derived e.g. from the statistical information or Expected UE Behaviour parameters or from subscription information; or +- "UE Differentiation Information" including the Expected UE Behaviour parameters excluding the Expected UE moving trajectory (see clause 4.15.6.3 of TS 23.502 [3]) to support Uu operation optimisation for NB-IoT UE differentiation if the RAT type is NB-IoT. + +The AMF decides when to send this information to the RAN as "Expected UE activity behaviour" carried in N2 request over the N2 interface (see TS 38.413 [34]). + +NOTE: The calculation of the CN assistance information, i.e. the algorithms used and related criteria, and the decision when it is considered suitable and stable to send to the RAN are vendor specific. + +#### 5.4.6.3 Core Network assisted RAN paging information + +Core Network assisted RAN paging information aids the RAN to formulate a RAN paging policy and strategy in RRC\_INACTIVE state, besides the PPI and QoS information associated to the QoS Flows as indicated in clause 5.4.3. + +CN assisted RAN paging information may be derived by the AMF per UE and/or per PDU Session based on collection of UE behaviour statistics, Expected UE Behaviour and/or other available information about the UE (such as subscribed DNN, SUPI ranges, Multimedia priority service), and/or information received from other network functions when downlink signalling is triggered. + +The CN assisted RAN paging information consists of a service priority (values 1 to 256) which provides AN with a way to understand how important the downlink signalling is. The AMF derives this service priority based on available information as described above. The method to derive the service priority is implementation depended and can be controlled by operator. + +The Core Network may provide the CN assisted RAN paging information to RAN in different occasions, e.g. during downlink N1 and N2 message delivery, etc. + +### 5.4.7 NG-RAN location reporting + +NG-RAN supports the NG-RAN location reporting for the services that require accurate cell identification (e.g. emergency services, lawful intercept, charging) or for the UE mobility event notification service subscribed to the AMF by other NFs. The NG-RAN location reporting may be used by the AMF when the target UE is in CM-CONNECTED state. The NG-RAN location reporting may be used by the AMF to determine the geographically located TAI in the case of NR satellite access. + +The AMF may request the NG-RAN location reporting with event reporting type (e.g. UE location or UE presence in Area of Interest), reporting mode and its related parameters (e.g. number of reporting). + +If the AMF requests UE location, the NG-RAN reports the current UE location (or last known UE location with time stamp if the UE is in RRC\_INACTIVE state) based on the requested reporting parameter (e.g. one-time reporting or continuous reporting). + +If the AMF requests UE location, in the case of NR satellite access, the NG-RAN provides all broadcast TAIs to the AMF as part of the ULI. The NG-RAN also reports the TAI where the UE is geographically located if this TAI can be determined. + +If the AMF requests UE presence in the Area Of Interest, the NG-RAN reports the UE location and the indication (i.e. IN, OUT or UNKNOWN) when the NG-RAN determines the change of UE presence in Area Of Interest. + +After N2 based Handover, if the NG-RAN location reporting information is required, the AMF shall re-request the NG-RAN location reporting to the target NG-RAN node. For Xn based Handover, the source NG-RAN shall transfer the requested NG-RAN location reporting information to target NG-RAN node. + +The AMF requests the location information of the UE either through independent N2 procedure (i.e. NG-RAN location reporting as specified in clause 4.10 of TS 23.502 [3]), or by including the request in some specific N2 messages as specified in TS 38.413 [34]. + +### 5.4.8 Support for identification and restriction of using unlicensed spectrum + +Support for NG-RAN using unlicensed spectrum is defined in TS 38.300 [27] and TS 36.300 [30]. + +For NG-RAN, in the case of NR in stand-alone mode, all cells are in unlicensed spectrum and the NR is used as primary RAT. NR or E-UTRA cells in unlicensed spectrum, can be used as secondary cells as specified in the Dual Connectivity architecture defined in clause 5.11 or in addition can be configured to support the Carrier Aggregation Architecture (CA) defined in TS 38.300 [27] and TS 36.300 [30]. + +For either case the serving PLMN can enforce Access Restriction for Unlicensed Spectrum (either signalled from the UDM, or, locally generated by VPLMN policy in the AMF) with the following: + +- To restrict the use of NR in unlicensed spectrum as primary RAT, the AMF rejects the UE Registration procedure with appropriate cause code defined in TS 24.501 [47] if the UE performs initial access from NR using unlicensed spectrum. If the UE is accessing through some other allowed RAT, the AMF signals this access restriction to NG-RAN as part of Mobility Restriction List. +- To restrict the use of use of unlicensed spectrum with NR or E-UTRA as secondary RAT using Dual Connectivity or Carrier Aggregation Architecture (CA) defined in TS 38.300 [27] and TS 36.300 [30], the AMF signals this access restriction to NG-RAN as part of Mobility Restriction List. + +An NG-RAN node supporting aggregation with unlicensed spectrum using either NR or E-UTRA checks whether the UE is allowed to use unlicensed spectrum based on received Mobility Restriction List. If the UE is not allowed to use Unlicensed Spectrum, the NG-RAN node shall restrict the using of unlicensed spectrum, either NR or E-UTRA as secondary RATs when using either Dual Connectivity or Carrier Aggregation (CA) as defined in TS 38.300 [27] and TS 36.300 [30]. + +At inter-RAT handover from E-UTRAN/EPS, the Access Restriction for Unlicensed Spectrum is either already in the AMF's UE context, or is obtained from the UDM during the subsequent Registration Area Update procedure (i.e. not from the source MME or source RAN). In both inter-RAT handover cases, any Access Restriction for use of Unlicensed Spectrum is then signalled to NG-RAN or enforced in AMF. + +**NOTE:** This signalling of the Access Restriction during the Registration Area Update after the inter-RAT handover procedure means that there is a small risk that unlicensed spectrum resources are transiently allocated. + +When the UE is accessing 5GS using unlicensed spectrum as primary RAT: + +- The NG-RAN node shall provide an indication to the AMF in N2 interface that NR access is using unlicensed spectrum as defined in TS 38.413 [34]. +- In order to restrict access to NR in unlicensed spectrum, cells supporting NR in unlicensed spectrum have to be deployed in Tracking Area(s) different to cells supporting licensed spectrum. +- When the AMF receives an indication from NG-RAN over N2 whether NR in unlicensed spectrum is being used as defined in TS 38.413 [34], the AMF provides to the SMF an indication that the RAT type is NR with usage of unlicensed spectrum during PDU Session Establishment or as part of the UP activation and Handover procedures. + +- The PCF will also receive the indication whether the UE is using NR in unlicensed spectrum, when applicable, from the SMF during SM Policy Association Establishment or SM Policy Association Modification procedure. +- The NFs generating CDRs shall include the indication that the UE is using NR in unlicensed spectrum in their CDRs. + +When the UE is accessing NR or E-UTRA using unlicensed spectrum as secondary RAT, procedures for Usage Data Reporting for Secondary RAT as defined in clause 5.12.2 can apply. + +### 5.4.9 Wake Up Signal Assistance + +#### 5.4.9.1 General + +The RAN and UE may use a Wake Up Signal (WUS) to reduce the UE's idle mode power consumption. The RAN sends the WUS shortly before the UE's paging occasion. The WUS feature enables UEs to determine that in the paging occasions immediately following their WUS occasion they will not be paged if their WUS is not transmitted, or that they might be paged if their WUS is transmitted (see TS 36.304 [52]). + +To avoid waking up UEs due to an AMF paging other UEs across multiple cells (e.g. due to frequent UE mobility and/or for low paging latency services such as VoLTE), the use of WUS by the ng-eNB and the UE is restricted to the last used cell, i.e. the cell in which the UE's RRC connection was last released. To support this: + +- ng-eNBs should provide the Recommended Cells for Paging IE in the *Information on Recommended Cells and RAN Nodes for Paging IE* (see TS 38.413 [34]) to the AMF in the NGAP UE Context Release Complete, UE Context Suspend Request and UE Context Resume Request messages; +- if received during the last NGAP UE Context Release Complete or UE Context Suspend Request message, the AMF provides (without modification) the *Recommended Cells for Paging as Assistance Data for Recommended Cells IE in the Assistance Data for Paging IE* within the NGAP Paging message to the RAN (see also TS 38.413 [34]); and +- the AMF shall delete (or mark as invalid) the *Information On Recommended Cells And RAND nodes For Paging* when a new NGAP association is established for the UE. + +In the NGAP Paging message, the last used cell ID is sent in the *Assistance Data for Recommended Cells IE* in the *Assistance Data for Paging IE* (see TS 38.413 [34]). When receiving an NGAP Paging message for a WUS-capable UE that also includes the *Assistance Data for Recommended Cells IE* then a WUS-capable ng-eNB shall only broadcast the WUS on the cell that matches the last used cell ID. + +#### 5.4.9.2 Group Wake Up Signal + +To support the Wake Up Signal (WUS), the WUS Assistance Information is used by the ng-eNB to help determine the WUS group used when paging the UE (see TS 36.300 [30]). + +The content of the WUS Assistance Information consists of the paging probability information. The paging probability information provides a metric on the probability of a UE receiving a paging message based on, e.g. statistical information. + +The UE may in the Registration Request message provide its capability to support receiving WUS Assistance Information. If WUS Assistance Information is supported by the UE, then the UE in the Registration Request message may provide the additional UE paging probability information. The AMF may use the UE provided paging probability, local configuration and/or previous statistical information for the UE, when determining the WUS Assistance Information. If the UE supports WUS Assistance Information, the AMF may assign WUS Assistance Information to the UE, even when the UE has not provided the additional UE paging probability information. + +If the AMF has determined WUS Assistance Information for the UE, the AMF provides it to the UE in every Registration Accept message. The AMF stores the WUS Assistance Information parameter in the MM context and provides it to the ng-eNB when paging the UE. + +UE and AMF shall not signal WUS Assistance Information in Registration Request, Registration Accept messages when the UE has an active emergency PDU session. + +### 5.4.10 Support for identification and restriction of using NR satellite access + +Support for NR satellite access is specified in TS 38.300 [27]. + +**Editor's note:** TS 38.300 [27] not yet updated by RAN groups. + +The AMF determines the RAT Type for NR satellite access, i.e. NR(LEO), NR(MEO), NR(GEO) and NR(OTHERSAT). When the UE is accessing NR using satellite access, an indication is provided in N2 interface indicating the type of NR satellite access, as defined in TS 38.413 [34]. + +**Editor's note:** Further details on what type of satellite platforms OTHERSAT includes is FFS and to be aligned with RAN WG3. + +The serving PLMN can enforce mobility restrictions for NR satellite access as specified in clause 5.3.4.1. + +In order to enable efficient enforcement of Mobility Restrictions, cells of each NR satellite RAT Type (NR(LEO), NR(MEO), NR(GEO) or NR(OTHERSAT)) need to be deployed in TAs different from TAs for other NR satellite RAT Types as well as different from TAs supporting terrestrial access RAT Types. + +The AMF may initiate deregistration of the UE when an N2 UE Context Release Request is received with cause value indicating that the UE is not in PLMN serving area, as specified in TS 38.413 [34]. + +### 5.4.11 Support for integrating NR satellite access into 5GS + +#### 5.4.11.1 General + +This clause describes the specific aspects for NR satellite access. + +#### 5.4.11.2 Support of RAT types defined in 5GC for satellite access + +In case of NR satellite access, the RAT Types values "NR(LEO)", "NR(MEO)", "NR(GEO)" and "NR(OTHERSAT)" are used in 5GC to distinguish the different NR satellite access types (see clause 5.4.10). + +When a UE is accessing to the network via satellite access, the AMF determines the RAT type as specified in clause 5.4.10. + +#### 5.4.11.3 Void + +#### 5.4.11.4 Verification of UE location + +In order to ensure that the regulatory requirements are met, the network may be configured to enforce that the selected PLMN is allowed to operate in the current UE location by verifying the UE location during Mobility Management and Session Management procedures. In this case, when the AMF receives a NGAP message containing User Location Information for a UE using NR satellite access, the AMF may decide to verify the UE location. If the AMF determines based on the Selected PLMN ID and ULI (including Cell ID) received from the gNB that it is not allowed to operate at the present UE location the AMF should reject any NAS request with a suitable cause value. If the UE is already registered to the network when the AMF determines that it is not allowed to operate at the present UE location, the AMF may initiate deregistration of the UE. The AMF should not reject the request or deregister the UE unless it has sufficiently accurate UE location information to determine that the UE is located in a geographical area where the PLMN is not allowed to operate. + +**NOTE:** The area where the UE is allowed to operate can be determined based on the regulatory area where the PLMN is allowed to operate based on its licensing conditions. + +If the AMF, based on the ULI, is not able to determine the UE's location with sufficient accuracy to make a final decision or if the received ULI is not sufficiently reliable, the AMF proceeds with the Mobility Management or Session Management procedure and may initiate UE location procedure after the Mobility Management or Session Management procedure is complete, as specified in clause 6.10.1 of TS 23.273 [87], to determine the UE location. The AMF shall be prepared to deregister the UE if the information received from LMF indicates that the UE is registered to a PLMN that is not allowed to operate in the UE location. In the case of a NAS procedure, the AMF should either reject any NAS + +request targeted towards a PLMN that is not allowed to operate in the known UE location and indicate a suitable cause value, or accept the NAS procedure and initiate deregistration procedure once the UE location is known. In the deregistration message to the UE, the AMF shall include a suitable cause value. For UE processing of the cause value indicating that the PLMN is not allowed to operate in the current UE location, see TS 23.122 [17] and TS 24.501 [47]. + +In the case of a handover procedure, if the (target) AMF determines that it is not allowed to operate at the current UE location, the AMF either rejects the handover, or accepts the handover and later deregisters the UE. + +##### 5.4.11.5 Network selection for NR satellite access + +Network selection principles specified in clause 5.2.2 apply also for NR satellite access. + +For NR satellite access, a UE with location capability should use its awareness of its location to select a PLMN that is allowed to operate in the UE location as specified in TS 23.122 [17]. + +In order to ensure that the regulatory requirements are met, the network may be configured to enforce this UE choice by verifying the UE location, as described in clause 5.4.11.4. + +#### 5.4.11.6 Support of Mobility Registration Update + +A moving radio cell for NR satellite access may indicate support for one or more TACs for each PLMN. A UE that is registered with a PLMN may access a radio cell and does not need to perform a Mobility Registration Update procedure as long as at least one supported TAC for the RPLMN or equivalent to the RPLMN is part of the UE Registration Area. A UE shall perform a Mobility Registration Update procedure when accessing a radio cell where none of the supported TACs for the RPLMN or equivalent to the RPLMN are part of the UE Registration Area. + +When indicating a last visited TAI in a Registration Update, a UE may indicate any TAI supported in a radio cell for the RPLMN or equivalent to the RPLMN for the last UE access prior to the Registration Update that is part of the UE Registration Area. + +#### 5.4.11.7 Tracking Area handling for NR satellite access + +In the case of NR satellite access with moving cells, in order to ensure that each TA is Earth-stationary even if the radio cells are moving across the Earth's surface, the NG-RAN may change the TAC values that are broadcast in a cell's system information as the cell moves, as described in TS 38.300 [27] and TS 38.331 [28]. + +NG-RAN may broadcast in a cell a single TAC per PLMN and change that TAC value as the cell moves. Alternatively, the NG-RAN may broadcast in a cell more than one TAC for a PLMN and add or remove TAC values as the cell moves. The NG-RAN provides either the single broadcast TAI or all broadcast TAIs corresponding to the Selected PLMN as described in TS 38.413 [34] to the AMF as part of the ULI, whenever the ULI is included in the NGAP message as described in TS 38.413 [34]. The NG-RAN indicates, if known, also the TAI where the UE is geographically located. + +NOTE: The AMF may take the TAI where the UE is geographically located into account to generate a suitable Registration Area for the UE. + +#### 5.4.11.8 Support for mobility Forbidden Area and Service Area Restrictions for NR satellite access + +Forbidden Area functionality is supported as described in clause 5.3.4.1.1 with the modifications described below: + +- The AMF and the UE receive the broadcast TAI (if a single TAI is broadcast) or all broadcast TAIs (if multiple TAIs are broadcast) from the NG-RAN as described clause 5.4.11.7. The AMF considers the UE to be in a Forbidden Area if the only received TAI is forbidden or if all received TAIs are forbidden based on subscription data. The UE considers it is in a Forbidden Area if the only received TAI is forbidden, or if all received TAIs are forbidden and is not within a Forbidden Area in the case that at least one broadcast TAI is not forbidden. +- If AMF receives multiple TAIs from the NG-RAN and determines that some, but not all of them are forbidden by subscription or by operator policy, the AMF shall send the forbidden TAI(s) to the UE as described in clauses 4.2.2.2 and 4.2.3 in TS 23.502 [3]. The UE stores the TAI(s) in the appropriate Forbidden Area list and removes the TAI(s) from Registration Area if present. + +Service Area Restrictions functionality is supported as described in clause 5.3.4.1.2 with the modifications described below: + +- The AMF receives the broadcast TAI (if a single TAI is broadcast) or all broadcast TAIs (if multiple TAIs are broadcast) from the NG-RAN as described clause 5.4.11.7. The AMF provides the UE with Service Area Restrictions which consist of either Allowed Areas or Non-Allowed Areas, as described in clause 5.3.4.1.2. The UE and AMF consider the UE to be in a Non-Allowed Area if none of the broadcast TAIs is Allowed. The UE and AMF consider the UE to be in an Allowed Area if at least one broadcast TAI is allowed. + +### 5.4.12 Paging Early Indication with Paging Subgrouping Assistance + +#### 5.4.12.1 General + +The RAN and UE may use a Paging Early Indication with Paging Subgrouping (PEIPS) to reduce the UE's power consumption in RRC\_IDLE and RRC\_INACTIVE over NR (see TS 38.304 [50]). + +The paging subgrouping can be based on either the UE's temporary ID or a Paging Subgroup ID allocated by the AMF. Paging subgrouping based on the UE's temporary ID is implemented within the NG-RAN. For paging subgrouping based on UE's temporary ID, the UE's support is included in the UE Radio Capability for Paging, either derived by the NG-RAN from UE provided UE radio capability (see clause 5.4.4) or based on UE Radio Capability ID if UE radio capability signalling optimisation is used (see clause 5.4.4.1a). + +The AMF, when determining its paging strategy (see clause 5.4.3), should take into consideration whether a gNB is using Paging subgrouping based on the UE's temporary ID. + +NOTE: Paging messages sent to that gNB can increase UE power consumption for other UEs that support Paging Subgrouping based on the UE's temporary ID. + +If paging subgroups are being allocated by the AMF, then all AMFs connected to one gNB (including the AMFs in different PLMNs using 5G MOCN network sharing) shall use a consistent policy in allocating UEs to the paging subgroups. The AMF may configure up to 8 different Paging Subgroup IDs. + +NOTE: Because the UE uses the AMF allocated paging subgroup across all cells in its TAI-list, and, different, overlapping TAI lists can be allocated to different UEs, then to avoid UE power consumption increasing, it is likely to be necessary that all AMFs with an overlapping coverage area use a consistent policy in allocating UEs to the paging subgroups. + +The NG-RAN node and the UE determine per cell which paging subgrouping method to use as defined in TS 38.304 [50] and TS 38.331 [28]. + +#### 5.4.12.2 Core Network Assistance for PEIPS + +To support the Paging Early Indication with Paging Subgrouping (PEIPS), Paging Subgrouping Support Indication and the PEIPS Assistance Information is used by the AMF and NG-RAN to help determine whether PEIPS applies to the UE and which paging subgroup used when paging the UE (see TS 38.300 [27]). + +In the Registration Request message, the Paging Subgrouping Support Indication indicates whether the UE supports PEIPS with AMF PEIPS Assistance Information. If the UE includes Paging Subgrouping Support Indication, the UE may also include the paging probability information to assist the AMF. If the AMF supports PEIPS assistance and if the UE provided Paging Subgrouping Support Indication, the AMF stores the indication in the UE context in AMF. The AMF may use local configuration, the UE's paging probability information if provided, information provided by the RAN (e.g. any of the *Information On Recommended Cells And RAN nodes For Paging*), and/or previous statistical information for the UE to determine the AMF PEIPS Assistance Information. The AMF PEIPS Assistance Information includes the Paging Subgroup ID. + +NOTE 1: To minimise MT voice call setup latency, the AMF could allocate Paging Subgroup IDs taking into account whether or not the UE is likely to receive IMS voice over PS session calls. + +NOTE 2: To avoid MT traffic for more mobile UEs causing more stationary UEs to be woken up, the AMF could allocate Paging Subgroup IDs taking into account the UE's mobility pattern. + +If the AMF has determined AMF PEIPS Assistance Information for the UE, the AMF stores it in the UE context in AMF and provides it to the UE in every Registration Accept message. + +If the AMF has determined AMF PEIPS Assistance Information, the AMF shall provide it to NG RAN when paging the UE. In addition, in order to support PEIPS for UEs in RRC\_INACTIVE mode, the AMF shall provide the AMF PEIPS Assistance Information to NG-RAN as part of the RRC Inactive Assistance Information. + +The NG-RAN chooses on a per-cell basis whether to use PEIPS and which paging subgrouping mechanism to use. When using AMF allocated subgroups, both the UE and NG-RAN use the AMF PEIPS Assistance Information to determine the paging subgroup to apply as defined in TS 38.300 [27]. + +The AMF may use the UE Configuration Update procedure (as described in clause 4.2.4 of TS 23.502 [3]) and N2 UE Context Modification procedure (as described in clause 8.3.4 of TS 38.413 [34]) to update the AMF PEIPS Assistance Information in the UE and NG-RAN. + +When the UE has an active emergency PDU Session: + +- The UE shall not signal Paging Subgrouping Support Indication in the Registration Request message. + +### 5.4.13 Support of discontinuous network coverage for satellite access + +#### 5.4.13.0 General + +The present clause 5.4.13 provides optional enhancements to support discontinuous coverage: + +- Mobility management and power saving optimization, see clause 5.4.13.1; and +- Coverage availability information provisioning to the UE, see clause 5.4.13.2; and +- Coverage availability information provisioning to the AMF, see clause 5.4.13.3; and +- Paging, see clause 5.4.13.4; and +- Overload control, see clause 5.4.13.5. + +NOTE: In this Release, there is no specified support for discontinuous coverage over NR in RAN specifications. + +#### 5.4.13.1 Mobility Management and Power Saving Optimization + +For NR satellite access that provides discontinuous network coverage the Mobility Management and Power Saving Optimization functionality may be used. + +If both the UE and the network support "Unavailability Period Support", and if the UE determines it will lose coverage and will become unavailable, and the UE decides to remain in no service during that time, then: + +- the UE triggers the Mobility Registration Update procedure to inform the network of its unavailability, as described in clause 5.4.1.4. +- The UE may be able to determine, including considering current and expected future locations of the UE, a Start of Unavailability Period and/or Unavailability Period Duration for when it expects to be out of coverage and include them in the Mobility Registration Update procedure, as described in clause 5.4.1.4. +- The UE should trigger the Mobility Registration Update procedure early enough such that the procedure, under normal conditions, is able to complete before the start of the unreachability period. + +NOTE 1: A UE based on implementation can combine successive periods of no satellite coverage into a single continuous period that is notified to the network if the UE does not require network access during this period. + +NOTE 2: UE informing the network of coverage gaps would increase signalling and UE power consumption if coverage gaps are more frequent than UE's communication period. + +In case the UE requests power saving features the AMF uses the procedures defined in other clauses to provide the UE with timers (e.g. Periodic Registration Update timer), extended DRX in CM-IDLE configuration (see clause 5.31.7.2), and MICO mode configuration (see clause 5.4.1.3), and to provide the NG-RAN with Extended Connected Time (see clause 5.31.7.3) and may also consider the Unavailability Period Duration and Start of Unavailability Period (if + +available). This is to keep UE in power saving mode and avoid the network attempting to page the UE if it is out of satellite network coverage. + +The AMF should adjust the mobile reachable timer or Implicit Deregistration timer or both such that the AMF does not implicitly deregister the UE while the UE is unavailable, see clause 5.4.1. Features described for High latency communication in clause 5.31.8 may be used to handle mobile terminated (MT) communication with UEs being unreachable due to NR satellite access discontinuous coverage and the Unavailability Period Duration (if available) and Start of Unavailability Period (if available) may be used when determining the Estimated Maximum Wait Time. + +Tracking Area or RAT specific configuration in the AMF may be used to set timer values based on typical coverage periods of a satellite system. + +NOTE 3: For example, if a satellite system only provides coverage to a UE for 20 minutes when a satellite passes, and the maximum time before a satellite passes any point on the earth is 10 hours, the AMF could configure the periodic registration timer and Mobile Reachable timer to be just greater than 20 minutes and the Implicit Deregistration timer to be greater than 10 hours to avoid unintended implicit detach due to coverage gap. Such configuration does not require AMF to be aware of detailed coverage times for each UE or for different locations. + +The UE may send Mobility Registration Update procedure to inform the network of its UE unavailability period (see clause 5.4.1.4) even if Mobility Management back-off timer is running. + +#### 5.4.13.2 Coverage availability information provisioning to the UE + +A UE may use satellite coverage availability information for satellite access to support discontinuous coverage operations. Satellite coverage availability information can be provided to a UE by an external server via a PDU Session or SMS. The protocol and format of satellite coverage availability information via PDU session or SMS is not defined in this release of the specification, but some examples on possible information that constitutes the satellite coverage availability information is defined in Annex Q. + +#### 5.4.13.3 Coverage availability information provisioning to the AMF + +The AMF may use satellite coverage availability information to support satellite access by UEs with discontinuous coverage operation. Satellite coverage availability information may be provisioned to the AMF by O&M. + +The satellite coverage availability information provisioned to the AMF describes when and where satellite coverage is expected to be available in an area. The satellite coverage availability information is not UE specific and can be applied by the AMF for any UE in the affected area. + +#### 5.4.13.4 Paging + +In the case of NR satellite access that provides discontinuous network coverage, AMF may utilize sub-area paging as described in clause 4.2.3.3 of TS 23.502 [3] (e.g. first page in the last known cell-id or TA and retransmission in all registered TAs). The AMF may utilize the location information as received at or before the AN release due to the discontinuous coverage for paging optimisation. + +The AMF may e.g. receive UE location from NG-RAN during the Registration procedure e.g. triggered for Mobility Management and Power Saving Optimization for discontinuous network coverage as described in clause 5.4.13.1, or the AMF may request NG-RAN location reporting when the UE is in CM-CONNECTED state as described in clause 5.4.7. + +#### 5.4.13.5 Overload control + +The AMF and UE may only use the procedure defined in this clause if both the UE and AMF indicate support for "Unavailability Period Support", see clause 5.4.13.1. A UE indicating support for "Unavailability Period Support" shall support the procedures defined in this clause when leaving coverage and re-gaining coverage for an NR satellite access. + +In order to avoid a large number of UEs causing excessive signalling load on the network when leaving coverage or re-gaining coverage after being out of coverage, the AMF may determine a Maximum Time Offset controlling when UEs are allowed to initiate NAS signalling with the network, as described in this clause. + +In this case, the AMF determines this Maximum Time Offset based on network configuration, high priority access and priority service as specified in TS 23.122 [17] and TS 24.501 [47]. The AMF sends this Maximum Time Offset to individual UEs during the Registration procedure or UE Configuration Update procedure. + +If the UE receives a Maximum Time Offset from the network in a Registration Accept or UE Configuration Update Command message, the UE shall replace any previously received Maximum Time Offset on the same RAT type and PLMN with this one. + +When the UE knows a later time at which coverage will be lost and when the UE does not send Mobility Registration Update to the AMF in advance (see clause 5.4.13.1), the UE determines a random value up to the minimum of the latest Maximum Time Offset for this PLMN and RAT type and the time until coverage will be lost. The UE shall send the Mobility Registration Update at the time when coverage will be lost less the random value to the AMF indicating the loss of coverage. + +Upon returning to coverage after being out of coverage due to discontinuous coverage, the UE sets the discontinuous coverage wait timer value to a random value up to and including the latest Maximum Time Offset for this PLMN and RAT type, and starts this timer. The UE shall not initiate any NAS signalling on that RAT Type and PLMN while the discontinuous coverage wait timer is running. + +The UE shall stop the discontinuous coverage wait timer and initiate NAS signalling if the UE receives paging message, has pending emergency services or when UE enters a TAI outside the registration area. + +## 5.5 Non-3GPP access specific aspects + +### 5.5.0 General + +This clause describes the specific aspects for untrusted non-3GPP access, trusted non-3GPP access and W-5GAN access. + +### 5.5.1 Registration Management + +This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG or to the W-AGF in the case of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. + +The UE shall enter RM-DEREGISTERED state and the AMF shall enter RM-DEREGISTERED state for the UE on non-3GPP access as follows: + +- at the UE and at the AMF, after performing an Explicit Deregistration procedure; +- at the AMF, after the Network non-3GPP Implicit Deregistration timer has expired. +- at the UE, after the UE non-3GPP Deregistration timer has expired. + +NOTE: This is assumed to leave sufficient time to allow the UE to re-activate UP connections for the established PDU Sessions over 3GPP or non-3GPP access. + +Whenever a UE registered over non-3GPP access enters CM-IDLE state for the non-3GPP access, it starts the UE non-3GPP Deregistration timer according to the value received from the AMF during a Registration procedure. + +Over non-3GPP access, the AMF runs the Network non-3GPP Implicit Deregistration timer. The Network non-3GPP Implicit Deregistration timer is started with a value longer than the UE's non-3GPP Deregistration timer, whenever the CM state for the UE registered over non-3GPP access changes to CM-IDLE for the non-3GPP access. + +For a UE that is registered over Non-3GPP access, a change of the point of attachment (e.g. change of WLAN AP) shall not lead the UE to perform a Registration procedure. + +A UE that is registered over non-3GPP access may trigger a Mobility Registration Update procedure via a new non-3GPP AN node (i.e. N3IWF or TNGF) to switch traffic from an old non-3GPP access to a new non-3GPP access. + +Traffic switching from an old non-3GPP access to and from a wireline access is not supported in this Release. + +Traffic switching from an old non-3GPP access to new non-3GPP access is supported only when PLMN of the new non-3GPP access is the same PLMN of the old non-3GPP access. + +A UE shall not provide 3GPP-specific parameters (e.g. indicate a preference for MICO mode) during registration over a non-3GPP access. + +During registration procedure the AMF may determine whether the serving N3IWF/TNGF is appropriate based on the slices supported by the N3IWFs/TNGFs as specified in clause 6.3.6 and clause 6.3.12 respectively. + +### 5.5.2 Connection Management + +This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. The UE mentioned in this clause corresponds to the 5G-RG in the case of W-5GAN and to the W-AGF in the case of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. + +A UE that successfully establishes a Non-3GPP Access Connection to the 5GC over a Non-3GPP access transitions to CM-CONNECTED state for the Non-3GPP access. + +In the case of Untrusted Non-3GPP access to 5GC, the Non-3GPP Access Connection corresponds to an NWu connection. + +In the case of Trusted access to 5GC, the Non-3GPP Access Connection corresponds to an NWt connection. + +In the case of N5CW devices access 5GC via trusted WLAN access networks, the Non-3GPP Access Connection corresponds to an Yt' connection. + +In the case of Wireline access to 5GC, the Non-3GPP Access Connection corresponds to a Y4 connection and to Y5 connection. + +A UE does not establish multiple simultaneous Non-3GPP Access Connection to the 5GC. + +The Non-3GPP Access Connection is released either as a result of an Explicit Deregistration procedure or an AN Release procedure. + +In the case of Untrusted Non-3GPP access, Trusted Non-3GPP access and W-5GAN access to 5GC, the N3IWF, TNGF, TWIF and W-AGF may in addition explicitly release the NWu, NWt, Yt', Y4 and Y5 signalling connection due to NWu, NWt, Yt', Y4 and Y5 connection failure, respectively. In the case of NWu and NWt, the release may be determined by the "dead peer detection" mechanism in IKEv2 defined in RFC 7296 [60]. In the case of Y4 and Y5 the release may be detected for example by lost of synchronisation of physical link, lost of PPPoE session, etc. Further details on how NWu, NWt, Yt', Y4 and Y5 connection failure is detected is out of scope of 3GPP specifications. + +For W-5GCAN, the W-AGF explicitly releases the N2 connection due to Y4 or Y5 connection failure, as determined by the "dead peer detection" mechanism in DOCSIS MULPI [89]. + +The release of the Non-3GPP Access Connection between the UE and the N3IWF, TNGF, TWIF or W-AGF shall be interpreted as follows: + +- By the N3IWF, TNGF, TWIF and W-AGF as a criterion to release the N2 connection. +- By the UE as a criterion for the UE to transition to CM-IDLE. A UE registered over non-3GPP access remains in RM-REGISTERED state, unless the Non-3GPP Access Connection release occurs as part of a Deregistration procedure over non-3GPP access in which case the UE enters the RM-DEREGISTERED state. When the UE in RM-REGISTERED transitions to CM-IDLE, the UE non-3GPP Deregistration timer starts running in the UE. The UE non-3GPP Deregistration timer stops when the UE moves to CM-CONNECTED state or to the RM-DEREGISTERED state. + +NOTE 1: When moved to CM-IDLE state over one access, the UE can attempt to re-activate UP connections for the PDU Sessions over other access, per UE policies and depending on the availability of these accesses. + +NOTE 2: The release of the NWu, NWt, Yt', Y4 or Y5 at the UE can occur as a result of explicit signalling from the N3IWF, TNGF, TWIF or W-AGF respectively, e.g. IKE INFORMATION EXCHANGE in the case of NWu or as a result of the UE detecting NWu, NWt, Yt', Y4 or Y5 connection failure, e.g. as determined by the "dead peer detection" mechanism in IKEv2 as defined in RFC 7296 [60] for NWu, NWt and Yt' or W-5GAN access specific mechanism for Y4 and Y5. Further details on how the UE detects NWu, NWt, Yt', Y4 or Y5 connection failure is out of scope of 3GPP specifications. + +In the case of Non-3GPP access, when the AMF releases the N2 interface, the N3IWF, TNGF, TWIF and W-AGF shall release all the resources associated with the UE including the Non-3GPP Access Connection with the UE and its corresponding N3 resources. A release of the N2 connection by the AMF shall set the CM state for the UE in the AMF to CM-IDLE. + +NOTE 3: It is assumed that a UE configured to receive services from a 5GC over non-3GPP access that is RM-DEREGISTERED or CM-IDLE over the non-3GPP access will attempt to establish Non-3GPP Access Connection and transition to CM-CONNECTED state whenever the UE successfully connects to a non-3GPP access unless prohibited by the network to make a N3GPP Access Connection (e.g. due to network congestion). + +An UE cannot be paged on Non-3GPP access network. + +When a UE registered simultaneously over a 3GPP access and a non-3GPP access moves all the PDU Sessions to one of the accesses, whether the UE initiates a Deregistration procedure in the access that has no PDU Sessions is up to the UE implementation. + +Release of PDU Sessions over the non-3GPP access does not imply the release of N2 connection. + +When the UE has PDU Sessions routed over the non-3GPP access and the UE state becomes CM-IDLE for the non-3GPP access, these PDU Sessions are not released to enable the UE to move the PDU Sessions over the 3GPP access based on UE policies. The core network maintains the PDU Sessions but deactivates the N3 user plane connection for such PDU Sessions. + +### 5.5.3 UE Reachability + +#### 5.5.3.1 UE reachability in CM-IDLE + +This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. The UE mentioned in this clause corresponds to 5G-RG, in the case of W-5GAN or to W-AGF in the case of support of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. + +An UE cannot be paged over Non-3GPP access network. + +If the UE states in the AMF are CM-IDLE and RM-REGISTERED for the non-3GPP access, there may be PDU Sessions that were last routed over the non-3GPP access and without user plane resources. If the AMF receives a message with a Non-3GPP Access Type indication from an SMF for a PDU Session corresponding to a UE that is CM-IDLE for non-3GPP access, and the UE is registered over 3GPP access in the same PLMN as the one registered over non-3GPP access, a Network Triggered Service Request may be performed over the 3GPP access independently of whether the UE is CM-IDLE or CM-CONNECTED over the 3GPP access. In this case, the AMF provides an indication that the procedure is related to non-3GPP access, as specified in clause 5.6.8. + +NOTE: The UE behaviour upon such network triggered Service Request is specified in clause 5.6.8. + +#### 5.5.3.2 UE reachability in CM-CONNECTED + +This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG and to W-AGF in the case of support of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. + +For a UE in CM-CONNECTED state: + +- the AMF knows the UE location on a N3IWF, TNGF, TWIF and W-AGF node granularity. + +- the N3IWF, TNGF, TWIF and W-AGF releases the N2 connection when UE becomes unreachable from N3IWF, TNGF, TWIF and W-AGF point of view, i.e. upon Non-3GPP Access Connection release. + +## 5.6 Session Management + +### 5.6.1 Overview + +The 5GC supports a PDU Connectivity Service i.e. a service that provides exchange of PDUs between a UE and a data network identified by a DNN. The PDU Connectivity Service is supported via PDU Sessions that are established upon request from the UE. + +The Subscription Information for each S-NSSAI may contain a Subscribed DNN list and one default DNN. When the UE does not provide a DNN in a NAS Message containing PDU Session Establishment Request for a given S-NSSAI, the serving AMF determines the DNN for the requested PDU Session by selecting the default DNN for this S-NSSAI if a default DNN is present in the UE's Subscription Information; otherwise the serving AMF selects a locally configured DNN for this S-NSSAI. + +The expectation is that the URSP in the UE is always up to date using the procedure defined in clause 4.16.12.2 of TS 23.502 [3] and therefore the UE requested DNN will be up to date. + +In order to cover cases that UE operates using local configuration, but also other cases where operator policies can be used in order to replace an "up to date" UE requested DNN with another DNN used only internally in the network, during UE Registration procedure the PCF may indicate, to the AMF, the operator policies to be used at PDU Session Establishment for DNN replacement of a UE requested DNN. PCF may indicate a policy for DNN replacement of UE requested DNNs not supported by the network, and/or indicate a list of UE requested DNNs per S-NSSAI valid for the serving network, that are subject for replacement (details are described in TS 23.503 [45]). + +If the DNN provided by the UE is not supported by the network and AMF cannot select an SMF by querying NRF, the AMF shall reject the NAS Message containing PDU Session Establishment Request from the UE with a cause indicating that the DNN is not supported unless the PCF provided the policy to perform a DNN replacement of unsupported DNNs. + +If the DNN requested by the UE is indicated for replacement or the DNN provided by the UE is not supported by the network and the PCF provided the policy to perform DNN replacement of UE requested DNNs not supported by the network, the AMF shall interact with the PCF to perform a DNN replacement. During PDU Session Establishment procedure and as a result of DNN replacement, the PCF provides the selected DNN that is applicable for the S-NSSAI requested by the UE at the PDU Session Establishment. The AMF uses the selected DNN in the query towards the NRF for the SMF selection, as specified in clause 6.3.2, and provides both requested and selected DNN to the selected SMF. For PDU Session with Home-routed Roaming whether to perform DNN replacement is based on operator agreements. + +NOTE 1: The selected DNN is determined based on operator preferences and can differ from subscribed DNNs. The matching of selected DNN to S-NSSAI is assumed to be based on network configuration. + +Each PDU Session supports a single PDU Session type i.e. supports the exchange of a single type of PDU requested by the UE at the establishment of the PDU Session. The following PDU Session types are defined: IPv4, IPv6, IPv4v6, Ethernet, Unstructured. + +PDU Sessions are established (upon UE request), modified (upon UE and 5GC request) and released (upon UE and 5GC request) using NAS SM signalling exchanged over N1 between the UE and the SMF. Upon request from an Application Server, the 5GC is able to trigger a specific application in the UE. When receiving that trigger message, the UE shall pass it to the identified application in the UE. The identified application in the UE may establish a PDU Session to a specific DNN, see clause 4.4.5. + +SMF may support PDU Sessions for LADN where the access to a DN is only available in a specific LADN service area. This is further defined in clause 5.6.5. + +SMF may support PDU Sessions for a 5G VN group which offers a virtual data network capable of supporting 5G LAN-type service over the 5G system. This is further defined in clause 5.8.2.13. + +The SMF is responsible of checking whether the UE requests are compliant with the user subscription. For this purpose, it retrieves and requests to receive update notifications on SMF level subscription data from the UDM. Such data may indicate per DNN and per S-NSSAI of the HPLMN: + +- The allowed PDU Session Types and the default PDU Session Type. +- The allowed SSC modes and the default SSC mode. +- QoS Information (refer to clause 5.7): the subscribed Session-AMBR, Default 5QI and Default ARP. +- The IP Index information. +- The static IP address/prefix. +- The subscribed User Plane Security Policy. +- the Charging Characteristics to be associated with the PDU Session. Whether this information is provided by the UDM to a SMF in another PLMN (for PDU Sessions in LBO mode) is defined by operator policies in the UDM/UDR. + +NOTE 2: The content of the Charging Characteristics as well as the usage of the Charging Characteristics by the SMF are defined in TS 32.255 [68]. + +A PDU Session may support: + +- (a) a single-access PDU Connectivity Service, in which case the PDU Session is associated with a single access type at a given time, i.e. either 3GPP access or non-3GPP access; or +- (b) a multi-access PDU Connectivity Service, in which case the PDU Session is simultaneously associated with both 3GPP access and non-3GPP access and simultaneously associated with two independent N3/N9 tunnels between the PSA and RAN/AN. + +A PDU Session supporting a single-access PDU Connectivity Service is also referred to as single-access PDU Session, while a PDU Session supporting a multi-access PDU Connectivity Service is referred to as Multi-Access PDU (MA PDU) Session and it is used to support the ATSSS feature (see clause 5.32 for details). + +A UE that is registered over multiple accesses chooses over which access to establish a PDU Session. As defined in TS 23.503 [45], the HPLMN may send policies to the UE to guide the UE selection of the access over which to establish a PDU Session. + +NOTE 3: In this Release of the specification, at any given time, a PDU Session is routed over only a single access network, unless it is an MA PDU Session in which case it can be routed over one 3GPP access network and one Non 3GPP access network concurrently. + +A UE may request to move a single-access PDU Session between 3GPP and Non 3GPP accesses. The decision to move single-access PDU Sessions between 3GPP access and Non 3GPP access is made on a per PDU Session basis, i.e. the UE may, at a given time, have some PDU Sessions using 3GPP access while other PDU Sessions are using Non 3GPP access. + +If the UE is attempting to move a single-access PDU session from 3GPP access to non-3GPP access and the PDU session is associated with control plane only indication, then the AMF shall reject the PDU Session Establishment request as related CIoT 5GS optimisation features are not supported over non-3GPP access as described in clause 5.4.5.2.5 of TS 24.501 [47]. If the UE is attempting to move a single-access PDU session from non-3GPP access to NB-N1 mode of 3GPP access, the PDU Session Establishment request would also be rejected by AMF when the UP resources for the UE exceed the maximum number of supported UP resources as described in clause 5.4.5.2.4 of TS 24.501 [47]. + +In a PDU Session Establishment Request message sent to the network, the UE shall provide a PDU Session ID. The PDU Session ID is unique per UE and is the identifier used to uniquely identify one of a UE's PDU Sessions. The PDU Session ID shall be stored in the UDM to support handover between 3GPP and non-3GPP access when different PLMNs are used for the two accesses. The UE also provides as described in TS 24.501 [47]: + +- (a) PDU Session Type. +- (b) S-NSSAI of the HPLMN that matches the application (that is triggering the PDU Session Request) within the NSSP in the URSP rules or within the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503 [45]. + +NOTE 4: If the UE cannot determine any S-NSSAI after performing the association of the application to a PDU Session, then it does not indicate any S-NSSAI in the PDU Session Establishment procedure as defined in clause 5.15.5.3. + +(c) S-NSSAI of the Serving PLMN from the Allowed NSSAI, corresponding to the S-NSSAI of the HPLMN (b). + +NOTE 5: In non-roaming scenario the mapping of the Allowed NSSAI to HPLMN S-NSSAIs is not provided to the UE (because the S-NSSAI of the Serving PLMN (c) has the same value of the S-NSSAI of the HPLMN (b)), therefore the UE provides in the PDU Session Request only the S-NSSAI of the Serving PLMN (c). + +NOTE 6: In roaming scenarios the UE provides in the PDU Session Request both the S-NSSAI of the HPLMN (b) and the S-NSSAI of the VPLMN from the Allowed NSSAI (c) that maps to the S-NSSAI of the HPLMN. + +(d) DNN (Data Network Name). + +(e) SSC mode (Service and Session Continuity mode defined in clause 5.6.9.2). + +Additionally, if the UE supports ATSSS and wants to activate a MA PDU Session, the UE shall provide Request Type as "MA PDU Request" and shall indicate the supported ATSSS capabilities (see clause 5.32 for details). + +**Table 5.6.1-1: Attributes of a PDU Session** + +| PDU Session attribute | May be modified later during the lifetime of the PDU Session | Notes | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|-----------------------------------------------------------------------------------------------| +| S-NSSAI of the HPLMN | No | (Note 1) (Note 2) | +| S-NSSAI of the Serving PLMN | Yes | (Note 1) (Note 2) (Note 4) | +| DNN (Data Network Name) | No | (Note 1) (Note 2) | +| PDU Session Type | No | (Note 1) | +| SSC mode | No | (Note 2)
The semantics of Service and Session Continuity mode is defined in clause 5.6.9.2 | +| PDU Session Id | No | | +| User Plane Security Enforcement information | No | (Note 3) | +| Multi-access PDU Connectivity Service | No | Indicates if the PDU Session provides multi-access PDU Connectivity Service or not. | +| NOTE 1: If it is not provided by the UE, the network determines the parameter based on default information received in user subscription. Subscription to different DNN(s) and S-NSSAI(s) may correspond to different default SSC modes and different default PDU Session Types | | | +| NOTE 2: S-NSSAI(s) and DNN are used by AMF to select the SMF(s) to handle a new session. Refer to clause 6.3.2. | | | +| NOTE 3: User Plane Security Enforcement information is defined in clause 5.10.3. | | | +| NOTE 4: The S-NSSAI value of the Serving PLMN associated to a PDU Session can change whenever the UE moves to a different PLMN, while keeping that PDU Session. | | | + +Subscription Information may include a wildcard DNN per subscribed S-NSSAI: when a wildcard DNN is associated with a subscribed S-NSSAI, the subscription allows, for this S-NSSAI, the UE to establish a PDU Session using any DNN value. + +NOTE 7: The SMF is made aware whether the DNN of a PDU Session being established corresponds to an explicitly subscribed DNN or corresponds to a wildcard DNN. Thus, the SMF can reject a PDU Session establishment if the DNN of the PDU Session is not part of explicitly subscribed DNN(s) and local policies in the SMF require UE to have a subscription to this DNN. + +A UE may establish multiple PDU Sessions, to the same data network or to different data networks, via 3GPP and via and Non-3GPP access networks at the same time. + +A UE may establish multiple PDU Sessions to the same Data Network and served by different UPF terminating N6. + +A UE with multiple established PDU Sessions may be served by different SMF. + +The SMF shall be registered and deregistered on a per PDU Session granularity in the UDM. + +The user plane paths of different PDU Sessions (to the same or to different DNN) belonging to the same UE may be completely disjoint between the AN and the UPF interfacing with the DN. + +When the SMF cannot control the UPF terminating the N3 interface used by a PDU Session and SSC mode 2/3 procedures are not applied to the PDU Session, an I-SMF is inserted between the SMF and the AMF and handling of PDU Session(s) is described in clause 5.34. + +NOTE 8: User Plane resources for PDU Sessions of a UE, except for regulatory prioritized service like Emergency Services and MPS, can be deactivated by the SMF if the UE is only reachable for regulatory prioritized services. + +The SMF serving a PDU session (i.e. Anchor) can be changed during lifetime of the PDU session either within the same SMF set or, if the Context Transfer Procedures as specified in clause 4.26 of TS 23.502 [3] are supported, between SMFs in different SMF sets. + +### 5.6.2 Interaction between AMF and SMF + +The AMF and SMF are separate Network Functions. + +N1 related interaction with SMF is as follows: + +- The single N1 termination point is located in AMF. The AMF forwards SM related NAS information to the SMF based on the PDU Session ID in the NAS message. Further SM NAS exchanges (e.g. SM NAS message responses) for N1 NAS signalling received by the AMF over an access (e.g. 3GPP access or non-3GPP access) are transported over the same access. +- The serving PLMN ensures that subsequent SM NAS exchanges (e.g. SM NAS message responses) for N1 NAS signalling received by the AMF over an access (e.g. 3GPP access or non-3GPP access) are transported over the same access. +- SMF handles the Session management part of NAS signalling exchanged with the UE. +- The UE shall only initiate PDU Session Establishment in RM-REGISTERED state. +- When a SMF has been selected to serve a specific PDU Session, AMF has to ensure that all NAS signalling related with this PDU Session is handled by the same SMF instance. +- Upon successful PDU Session Establishment, the AMF and SMF stores the Access Type that the PDU Session is associated. + +N11 related interaction with SMF is as follows: + +- The AMF reports the reachability of the UE based on a subscription from the SMF, including: + - The UE location information with respect to the area of interest indicated by the SMF. +- The SMF indicates to AMF when a PDU Session has been released. +- Upon successful PDU Session Establishment, AMF stores the identification of serving SMF of UE and SMF stores the identification of serving AMF of UE including the AMF set. When trying to reach the AMF serving the UE, the SMF may need to apply the behaviour described for "the other CP NFs" in clause 5.21. + +N2 related interaction with SMF is as follows: + +- Some N2 signalling (such as handover related signalling) may require the action of both AMF and SMF. In such case, the AMF is responsible to ensure the coordination between AMF and SMF. The AMF may forward the SM N2 signalling towards the corresponding SMF based on the PDU Session ID in N2 signalling. +- SMF shall provide PDU Session Type together with PDU Session ID to NG-RAN, in order to facilitate NG-RAN to apply suitable header compression mechanism to packet of different PDU type. Details refer to TS 38.413 [34]. + +N3 related interaction with SMF is as follows: + +- Selective activation and deactivation of UP connection of existing PDU Session is defined in clause 5.6.8. + +N4 related interaction with SMF is as follows: + +- When it is made aware by the UPF that some DL data has arrived for a UE without downlink N3 tunnel information, the SMF interacts with the AMF to initiate Network Triggered Service Request procedure. In this case, if the SMF is aware that the UE is unreachable or if the UE is reachable only for regulatory prioritized service and the PDU Session is not for regulatory prioritized service, then the SMF shall not inform DL data notification to the AMF + +The AMF is responsible of selecting the SMF per procedures described in clause 6.3.2. For this purpose, it gets subscription data from the UDM that are defined in that clause. Furthermore, it retrieves the subscribed UE-AMBR from the UDM, and optionally dynamic serving network UE-AMBR from PCF based on operator local policy, and sends to the (R)AN as defined in clause 5.7.2 + +AMF-SMF interactions to support LADN or LADN per DNN and S-NSSAI are defined in clause 5.6.5 and in clause 5.6.5a. + +In order to support charging and to fulfil regulatory requirement (in order to provide NPLI (Network Provided Location Information) as defined in TS 23.228 [15]) related with the set-up, modification and release of IMS Voice calls or with SMS transfer the following applies + +- At the time of the PDU Session Establishment, the AMF provides the SMF with the PEI of the UE if the PEI is available at the AMF. +- When it forwards UL NAS or N2 signalling to a peer NF (e.g. to SMF or to SMSF) or during the UP connection activation of a PDU Session, the AMF provides any User Location Information it has received from the 5G-AN as well as the Access Type (3GPP - Non 3GPP) of the AN over which it has received the UL NAS or N2 signalling. The AMF also provides the corresponding UE Time Zone. In addition, in order to fulfil regulatory requirement (i.e. providing Network Provided Location Information (NPLI), as defined in TS 23.228 [15]) when the access is non-3GPP, the AMF may also provide the last known 3GPP access User Location Information with its age, if the UE is still attached to the same AMF for 3GPP access (i.e. valid User Location Information). + +The User Location Information, the access type and the UE Time Zone may be further provided by SMF to PCF. The PCF may get this information from the SMF in order to provide NPLI to applications (such as IMS) that have requested it. + +The User Location Information may correspond to: + +- In the case of 3GPP access: TAI, Cell-Id. The AMF includes only the Primary Cell-Id even if it had received also the Cell-Id of the Primary cell in the Secondary RAN node from NG-RAN. +- In the case of Untrusted non-3GPP access: TAI, the UE local IP address used to reach the N3IWF and optionally the UDP source port number if NAT is detected. +- In the case of Trusted non-3GPP access: TAI, TNAP/TWAP Identifier, the UE/N5CW device local IP address used to reach the TNGF/TWIF and optionally the UDP source port number if NAT is detected. + +When the UE uses WLAN based on IEEE 802.11 technology to reach the TNGF, the TNAP Identifier shall include the SSID of the access point to which the UE is attached. The TNAP Identifier shall include at least one of the following elements, unless otherwise determined by the TWAN operator's policies: + +- the BSSID (see IEEE Std 802.11-2012 [106]); +- civic address information of the TNAP to which the UE is attached. + +The TWAP Identifier shall include the SSID of the access point to which the NC5W is attached. The TWAP Identifier shall also include at least one of the following elements, unless otherwise determined by the TWAN operator's policies: + +- the BSSID (see IEEE Std 802.11-2012 [106]); +- civic address information of the TWAP to which the UE is attached. + +NOTE 1: The SSID can be the same for several TNAPs/TWAPs and SSID only cannot provide a location, but it might be sufficient for charging. + +NOTE 2: the BSSID associated with a TNAP/TWAP is assumed to be static. + +- In the case of W-5GAN access: The User Location Information for W-5GAN is defined in TS 23.316 [84]. + +When the SMF receives a request to provide Access Network Information reporting while there is no action to carry out towards the 5G-AN or the UE (e.g. no QoS Flow to create / Update / modify), the SMF may request User Location Information from the AMF. + +The interaction between AMF and SMF(s) for the case of a I-SMF insertion, relocation or removal for a PDU session is described in clause 5.34. + +### 5.6.3 Roaming + +In the case of roaming the 5GC supports following possible deployments scenarios for a PDU Session: + +- "Local Break Out" (LBO) where the SMF and all UPF(s) involved by the PDU Session are under control of the VPLMN. +- "Home Routed" (HR) where the PDU Session is supported by a SMF function under control of the HPLMN, by a SMF function under control of the VPLMN, by at least one UPF under control of the HPLMN and by at least one UPF under control of the VPLMN. In this case the SMF in HPLMN selects the UPF(s) in the HPLMN and the SMF in VPLMN selects the UPF(s) in the VPLMN. This is further described in clause 6.3. Home Routed with Session Breakout in VPLMN (HR-SBO) is described in clause 6.7 of TS 23.548 [130]. + +NOTE 1: The use of an UPF in the VPLMN e.g. enables VPLMN charging, VPLMN LI and minimizes the impact on the HPLMN of the UE mobility within the VPLMN (e.g. for scenarios where SSC mode 1 applies). + +Different simultaneous PDU Sessions of an UE may use different modes: Home Routed and LBO. The HPLMN can control via subscription data per DNN and per S-NSSAI whether a PDU Session is to be set-up in HR or in LBO mode. + +In the case of PDU Sessions per Home Routed deployment: + +- NAS SM terminates in the SMF in VPLMN. +- The SMF in VPLMN forwards to the SMF in the HPLMN SM related information. +- The SMF in the HPLMN receives the SUPI of the UE from the SMF in the VPLMN during the PDU Session Establishment procedure. +- The SMF in HPLMN is responsible to check the UE request with regard to the user subscription and to possibly reject the UE request in the case of mismatch. The SMF in HPLMN obtains subscription data directly from the UDM. +- The SMF in HPLMN may send QoS requirements associated with a PDU Session to the SMF in VPLMN. This may happen during the PDU Session Establishment procedure and after the PDU Session is established. The interface between SMF in HPLMN and SMF in VPLMN is also able to carry (N9) User Plane forwarding information exchanged between SMF in HPLMN and SMF in VPLMN. The SMF in the VPLMN may check QoS requests from the SMF in HPLMN with respect to roaming agreements. + +In home routed roaming case, the AMF selects an SMF in the VPLMN and a SMF in the HPLMN as described in clause 6.3.2 and in clause 4.3.2.2.3.3 of TS 23.502 [3], and provides the identifier of the selected SMF in the HPLMN to the selected SMF in the VPLMN. + +In roaming with LBO, the AMF selects a SMF in the VPLMN as described in clause 6.3.2 and in clause 4.3.2.2.3.2 of TS 23.502 [3]. In this case, when handling a PDU Session Establishment Request message, the SMF in the VPLMN may reject the N11 message (related with the PDU Session Establishment Request message) with a proper N11 cause. This triggers the AMF to select both a new SMF in the VPLMN and a SMF in the HPLMN in order to handle the PDU Session using home routed roaming. + +### 5.6.4 Single PDU Session with multiple PDU Session Anchors + +#### 5.6.4.1 General + +In order to support selective traffic routing to the DN or to support SSC mode 3 as defined in clause 5.6.9.2.3, the SMF may control the data path of a PDU Session so that the PDU Session may simultaneously correspond to multiple N6 interfaces. The UPF that terminates each of these interfaces is said to support PDU Session Anchor functionality. Each PDU Session Anchor supporting a PDU Session provides a different access to the same DN. Further, the PDU Session + +Anchor assigned at PDU Session Establishment is associated with the SSC mode of the PDU Session and the additional PDU Session Anchor(s) assigned within the same PDU Session e.g. for selective traffic routing to the DN are independent of the SSC mode of the PDU Session. When a PCC rule including the Application Function influence on traffic routing Enforcement Control information defined in clause 6.3.1 of TS 23.503 [45] is provided to the SMF, the SMF can decide whether to apply traffic routing (by using UL Classifier functionality or IPv6 multi-homing) based on DNAI(s) included in the PCC rule. + +NOTE 1: Application Function influence on traffic routing Enforcement Control information can be either determined by the PCF when requested by AF via NEF as described in clause 5.6.7.1 or statically pre-configured in the PCF. + +NOTE 2: Selective traffic routing to the DN supports, for example, deployments where some selected traffic is forwarded on an N6 interface to the DN that is "close" to the AN serving the UE. + +This may correspond to + +- The Usage of UL Classifier functionality for a PDU Session defined in clause 5.6.4.2. +- The Usage of an IPv6 multi-homing for a PDU Session defined in clause 5.6.4.3. + +SMF may also take decision to apply traffic routing (by using UL Classifier functionality or IPv6 multi-homing) in EAS Discovery with EASDF procedure described in TS 23.548 [130]. + +#### 5.6.4.2 Usage of an UL Classifier for a PDU Session + +In the case of PDU Sessions of type IPv4 or IPv6 or IPv4v6 or Ethernet, the SMF may decide to insert in the data path of a PDU Session an "UL CL" (Uplink classifier). The UL CL is a functionality supported by an UPF that aims at diverting (locally) some traffic matching traffic filters provided by the SMF. The insertion and removal of an UL CL is decided by the SMF and controlled by the SMF using generic N4 and UPF capabilities. The SMF may decide to insert in the data path of a PDU Session a UPF supporting the UL CL functionality during or after the PDU Session Establishment, or to remove from the data path of a PDU Session a UPF supporting the UL CL functionality after the PDU Session Establishment. The SMF may include more than one UPF supporting the UL CL functionality in the data path of a PDU Session. + +The UE is unaware of the traffic diversion by the UL CL, and does not involve in both the insertion and the removal of UL CL. In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, the UE associates the PDU Session with either a single IPv4 address or a single IPv6 Prefix or both of them allocated by the network. + +When an UL CL functionality has been inserted in the data path of a PDU Session, there are multiple PDU Session Anchors for this PDU Session. These PDU Session Anchors provide different access to the same DN. In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, only one IPv4 address and/or IPv6 prefix is provided to the UE. The SMF may be configured with local policies for some (DNN, S-NSSAI) combinations to release the PDU Session when there is a PSA associated with the IPv4 address allocated to the UE and this PSA has been removed. + +NOTE 0: The use of only one IPv4 address and/or IPv6 prefix with multiple PDU Session Anchors assumes that when needed, appropriate mechanisms are in place to correctly forward packets on the N6 reference point. The mechanisms for packet forwarding on the N6 reference point between the PDU Session Anchor providing local access and the DN are outside the scope of this specification. + +The UL CL provides forwarding of UL traffic towards different PDU Session Anchors and merge of DL traffic to the UE i.e. merging the traffic from the different PDU Session Anchors on the link towards the UE. This is based on traffic detection and traffic forwarding rules provided by the SMF. + +The UL CL applies filtering rules (e.g. to examine the destination IP address/Prefix of UL IP packets sent by the UE) and determines how the packet should be routed. The UPF supporting an UL CL may also be controlled by the SMF to support traffic measurement for charging, traffic replication for LI and bit rate enforcement (Session-AMBR per PDU Session). + +NOTE 1: When N9 forwarding tunnel exists between source ULCL and target ULCL, the Session-AMBR per PDU Session can be enforced by the source UL CL UPF. + +NOTE 2: The UPF supporting an UL CL may also support a PDU Session Anchor for connectivity to the local access to the data network (including e.g. support of tunnelling or NAT on N6). This is controlled by the SMF. + +Additional UL CLs (and thus additional PDU Session Anchors) can be inserted in the data path of a PDU Session to create new data paths for the same PDU Session. The way to organize the data path of all UL CLs in a PDU Session is up to operator configuration and SMF logic and there is only one UPF supporting UL CL connecting to the (R)AN via N3 interface, except when session continuity upon UL CL relocation is used. + +The insertion of an ULCL in the data path of a PDU Session is depicted in Figure 5.6.4.2-1. + +![Figure 5.6.4.2-1: User plane Architecture for the Uplink Classifier. The diagram shows a UE connected to an AN, which is connected to a UPF Uplink Classifier via an N3 interface. The UPF Uplink Classifier is connected to an AMF via an N2 interface and to an SMF via an N4 interface. The SMF is connected to the AMF via an N11 interface and to two UPF PDU session anchors (anchor 1 and anchor 2) via N4 interfaces. The UPF Uplink Classifier is connected to the UPF PDU session anchor 1 via an N9 interface and to the UPF PDU session anchor 2 via an N9 interface. The UPF PDU session anchor 1 is connected to a DN via an N6 interface, and the UPF PDU session anchor 2 is connected to a DN via an N6 interface. The text 'Local access to the same DN' is placed below the two DN boxes.](1033dc9fde75540d224c907681b1b7aa_img.jpg) + +``` + +graph TD + UE[UE] --- AN[AN] + AN -- N3 --> UPF_UC[UPF Uplink Classifier] + UPF_UC -- N2 --> AMF[AMF] + UPF_UC -- N4 --> SMF[SMF] + SMF -- N11 --> AMF + SMF -- N4 --> UPF_A1[UPF PDU session anchor 1] + SMF -- N4 --> UPF_A2[UPF PDU session anchor 2] + UPF_UC -- N9 --> UPF_A1 + UPF_UC -- N9 --> UPF_A2 + UPF_A1 -- N6 --> DN1[DN] + UPF_A2 -- N6 --> DN2[DN] + subgraph Local_access_to_the_same_DN + DN1 + DN2 + end + +``` + +Figure 5.6.4.2-1: User plane Architecture for the Uplink Classifier. The diagram shows a UE connected to an AN, which is connected to a UPF Uplink Classifier via an N3 interface. The UPF Uplink Classifier is connected to an AMF via an N2 interface and to an SMF via an N4 interface. The SMF is connected to the AMF via an N11 interface and to two UPF PDU session anchors (anchor 1 and anchor 2) via N4 interfaces. The UPF Uplink Classifier is connected to the UPF PDU session anchor 1 via an N9 interface and to the UPF PDU session anchor 2 via an N9 interface. The UPF PDU session anchor 1 is connected to a DN via an N6 interface, and the UPF PDU session anchor 2 is connected to a DN via an N6 interface. The text 'Local access to the same DN' is placed below the two DN boxes. + +**Figure 5.6.4.2-1: User plane Architecture for the Uplink Classifier** + +NOTE 3: It is possible for a given UPF to support both the UL CL and the PDU Session Anchor functionalities. + +Due to UE mobility the network may need to relocate the UPF acting as UL CL and establish a new PSA for local access to the DN. To support session continuity during UL CL relocation the network may establish a temporary N9 forwarding tunnel between the source UL CL and target UL CL. The AF may influence the creation of the N9 forwarding tunnel as described in clause 5.6.7.1. + +The N9 forwarding tunnel is maintained until: + +- all active traffic flowing on it ceases to exist for: + - a configurable period of time; or + - a period of time indicated by the AF; +- until the AF informs the SMF that it can release the source PSA providing local access to the DN. + +During the existence of the N9 forwarding tunnel the UPF acting as target UL CL is configured with packet filters that: + +- force uplink traffic from existing data sessions between UE and the application in the source local part of the DN (as defined in TS 23.548 [130]) into the N9 forwarding tunnel towards the source UL CL. +- force any traffic related to the application in the target local part of the DN to go to the new local part of the DN via the target PSA. + +SMF may send a Late Notification to AF to inform it about the DNAI change as described in clause 4.3.6.3 of TS 23.502 [3]. This notification can be used by the AF e.g. to trigger mechanisms in the source local part of the DN to redirect the ongoing traffic sessions towards an application in the target local part of the DN. SMF can also send late notification to the target AF instance if associated with this target local part of the DN. + +The procedure for session continuity upon UL CL relocation is described in clause 4.3.5.7 of TS 23.502 [3]. + +When an I-SMF is inserted for a PDU Session, the details of UL CL insertion which is controlled by an I-SMF is described in clause 5.34.4. + +#### 5.6.4.3 Usage of IPv6 multi-homing for a PDU Session + +A PDU Session may be associated with multiple IPv6 prefixes. This is referred to as multi-homed PDU Session. The multi-homed PDU Session provides access to the Data Network via more than one PDU Session Anchor. The different user plane paths leading to the different PDU Session Anchors branch out at a "common" UPF referred to as a UPF supporting "Branching Point" functionality. The Branching Point provides forwarding of UL traffic towards the different PDU Session Anchors and merge of DL traffic to the UE i.e. merging the traffic from the different PDU Session Anchors on the link towards the UE. + +The UPF supporting a Branching Point functionality may also be controlled by the SMF to support traffic measurement for charging, traffic replication for LI and bit rate enforcement (Session-AMBR per PDU Session). The insertion and removal of a UPF supporting Branching Point is decided by the SMF and controlled by the SMF using generic N4 and UPF capabilities. The SMF may decide to insert in the data path of a PDU Session a UPF supporting the Branching Point functionality during or after the PDU Session Establishment, or to remove from the data path of a PDU Session a UPF supporting the Branching Point functionality after the PDU Session Establishment. + +Multi homing of a PDU Session applies only for PDU Sessions of IPv6 type. When the UE requests a PDU Session of type "IPv4v6" or "IPv6" the UE also provides an indication to the network whether it supports a Multi-homed IPv6 PDU Session. + +The use of multiple IPv6 prefixes in a PDU Session is characterised by the following: + +- The UPF supporting a Branching Point functionality is configured by the SMF to spread UL traffic between the PDU Session Anchors based on the Source Prefix of the PDU (which may be selected by the UE based on routing information and preferences received from the network). +- IETF RFC 4191 [8] is used to configure routing information and preferences into the UE to influence the selection of the source Prefix. + +NOTE 1: This corresponds to Scenario 1 defined in IETF RFC 7157 [7] "IPv6 Multi-homing without Network Address Translation". This allows to make the Branching Point unaware of the routing tables in the Data Network and to keep the first hop router function in the PDU Session Anchors. + +- The multi-homed PDU Session may be used to support make-before-break service continuity to support SSC mode 3. This is illustrated in Figure 5.6.4.3-1. +- The multi-homed PDU Session may also be used to support cases where UE needs to access both a local service (e.g. local server) and a central service (e.g. the internet), illustrated in Figure 5.6.4.3-2. +- The UE shall use the method specified in clause 4.3.5.3 of TS 23.502 [3] to determine if a multi-homed PDU Session is used to support the service continuity case shown in Figure 5.6.4.3-1, or if it is used to support the local access to DN case shown in Figure 5.6.4.3-2. + +![Diagram of Multi-homed PDU Session: service continuity case. The diagram shows a UE connected to an AN, which is connected to a UPF Branching Point. The AN is also connected to an AMF via N2. The AMF is connected to an SMF via N11. The SMF is connected to the UPF Branching Point via N4. The UPF Branching Point is connected to two UPF PDU session anchors (anchor 1 and anchor 2) via N9. The SMF is also connected to these anchors via N4. The anchors are connected to a DN via N6. A dashed arrow labeled 'make-before-break PSA relocation' points from anchor 1 to anchor 2.](d4ed35f72863013455b8f015e0f2e47e_img.jpg) + +``` + +graph LR + UE[UE] --- AN[AN] + AN -- N2 --> AMF[AMF] + AN -- N3 --> UPF_BP[UPF Branching Point] + AMF -- N11 --> SMF[SMF] + SMF -- N4 --> UPF_BP + SMF -- N4 --> UPF_A1[UPF PDU session anchor 1] + SMF -- N4 --> UPF_A2[UPF PDU session anchor 2] + UPF_BP -- N9 --> UPF_A1 + UPF_BP -- N9 --> UPF_A2 + UPF_A1 -- N6 --> DN[DN] + UPF_A2 -- N6 --> DN + UPF_A1 -- make-before-break PSA relocation --> UPF_A2 + +``` + +Diagram of Multi-homed PDU Session: service continuity case. The diagram shows a UE connected to an AN, which is connected to a UPF Branching Point. The AN is also connected to an AMF via N2. The AMF is connected to an SMF via N11. The SMF is connected to the UPF Branching Point via N4. The UPF Branching Point is connected to two UPF PDU session anchors (anchor 1 and anchor 2) via N9. The SMF is also connected to these anchors via N4. The anchors are connected to a DN via N6. A dashed arrow labeled 'make-before-break PSA relocation' points from anchor 1 to anchor 2. + +**Figure 5.6.4.3-1: Multi-homed PDU Session: service continuity case** + +NOTE 2: It is possible for a given UPF to support both the Branching Point and the PDU Session Anchor functionalities. + +![Diagram of Multi-homed PDU Session: local access to same DN. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an SMF via N11. The SMF is connected to a UPF Branching Point via N4. The UPF Branching Point is connected to a DN via N6 and to another UPF (PDU session anchor 2) via N9. The UPF Branching Point is also connected to a UPF (PDU session anchor 1) via N9. The UPF (PDU session anchor 1) is connected to a DN via N6. The UPF (PDU session anchor 2) is connected to a DN via N6. The text 'Local access to the same DN' is written below the diagram.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +graph TD + UE[UE] --- AN[AN] + AN --- AMF[AMF] + AMF -.-> SMF[SMF] + SMF -.-> UPF_BP[UPF Branching Point] + UPF_BP --- DN1[DN] + UPF_BP -.-> UPF_A1[UPF PDU session anchor 1] + UPF_A1 --- DN2[DN] + UPF_BP -.-> UPF_A2[UPF PDU session anchor 2] + UPF_A2 --- DN3[DN] + style UE fill:none,stroke:none + style AN fill:none,stroke:none + style AMF fill:none,stroke:none + style SMF fill:none,stroke:none + style UPF_BP fill:none,stroke:none + style DN1 fill:none,stroke:none + style UPF_A1 fill:none,stroke:none + style DN2 fill:none,stroke:none + style UPF_A2 fill:none,stroke:none + style DN3 fill:none,stroke:none + +``` + +*Local access to the same DN* + +Diagram of Multi-homed PDU Session: local access to same DN. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an SMF via N11. The SMF is connected to a UPF Branching Point via N4. The UPF Branching Point is connected to a DN via N6 and to another UPF (PDU session anchor 2) via N9. The UPF Branching Point is also connected to a UPF (PDU session anchor 1) via N9. The UPF (PDU session anchor 1) is connected to a DN via N6. The UPF (PDU session anchor 2) is connected to a DN via N6. The text 'Local access to the same DN' is written below the diagram. + +**Figure 5.6.4.3-2: Multi-homed PDU Session: local access to same DN** + +NOTE 3: It is possible for a given UPF to support both the Branching Point and the PDU Session Anchor functionalities. + +### 5.6.5 Support for Local Area Data Network + +The access to a DN via a PDU Session for a LADN is only available in a specific LADN service area. A LADN service area is a set of Tracking Areas. LADN is a service provided by the serving PLMN or the serving SNPN. It includes: + +- LADN service applies only to 3GPP accesses and does not apply in Home Routed case. +- The usage of LADN DNN requires an explicit subscription to this DNN or subscription to a wildcard DNN. +- Whether a DNN corresponds to a LADN service is an attribute of a DNN and is per PLMN or per SNPN. + +The UE is configured to know whether a DNN is a LADN DNN on a per-PLMN or per SNPN basis, and an association between application and LADN DNN. The configured association is considered to be a UE local configuration defined in TS 23.503 [45]. Alternatively, the UE gets the information whether a DNN is a LADN DNN from LADN Information during (re-)registration procedure as described in this clause. + +NOTE 1: No other procedure for configuring the UE to know whether a DNN is a LADN DNN is defined in this release of the specifications. + +NOTE 2: The procedure for configuring the UE to know an association between application and LADN DNN is not defined in this release of the specifications. + +LADN service area and LADN DNN are configured in the AMF on a per DN basis, i.e. for different UEs accessing the same LADN, the configured LADN service area is the same regardless of other factors (e.g. UE's Registration Area or UE subscription). + +NOTE 3: If a LADN is not available in any TA of an AMF's service area, the AMF is not required to be configured with any LADN related information for that DNN. + +LADN Information (i.e. LADN Service Area Information and LADN DNN) is provided by AMF to the UE during the Registration procedure or UE Configuration Update procedure. For each LADN DNN configured in the AMF, the corresponding LADN Service Area Information includes a set of Tracking Areas that belong to the Registration Area that the AMF assigns to the UE (i.e. the intersection of the LADN service area and the assigned Registration Area). The AMF shall not create Registration Area based on the availability of LADNs. + +NOTE 4: It is thus possible that the LADN Service Area Information sent by the AMF to the UE contains only a sub-set of the full LADN service area as the LADN service area can contain TA(s) outside of the registration area of the UE or outside of the area served by the AMF. + +When the UE performs a successful (re-)registration procedure, the AMF may provide to the UE, based on local configuration (e.g. via OAM) about LADN, on UE location, and on UE subscription information received from the + +UDM about subscribed DNN(s), the LADN Information for the list of LADN available to the UE in that Registration Area in the Registration Accept message. + +The UE may provide either the LADN DNN(s) to retrieve the LADN Information for the indicated LADN DNN(s) or an indication of Requesting LADN Information to retrieve the LADN Information for all LADN(s) available in the current Registration Area. + +The list of LADN is determined as follows: + +- If neither LADN DNN nor an indication of requesting LADN Information is provided in the Registration Request message, the list of LADN is the LADN DNN(s) in subscribed DNN list except for wildcard DNN. +- If the UE provides LADN DNN(s) in the Registration Request message, the list of LADN is LADN DNN(s) the UE requested if the UE subscribed DNN(s) includes the requested LADN DNN or if a wildcard DNN is included in the UE's subscription data. + +NOTE 5: It is assumed that an application can use only one LADN DNN at a time. + +- If the UE provides an indication of requesting LADN Information in the Registration Request message, the list of LADN is all the LADN DNN(s) configured in the AMF if the wildcard DNN is subscribed, or the LADN DNN(s) which is in subscribed DNN list and no wildcard DNN is subscribed. + +The UE considers the retrieved LADN Information valid only for the registered PLMN and the E-PLMN(s) if the LADN Service Area Information includes Tracking Areas that belong to E-PLMN(s). Additionally, an LADN DNN discovered by the UE via the retrieved LADN Information is considered an LADN DNN also in the E-PLMNs of the Registered PLMN, i.e. the UE can request LADN Information for the discovered LADN DNN in the E-PLMNs. + +During the subsequent Registration procedure, if the network does not provide LADN Information for a DNN, the UE deletes any LADN Information for that DNN. + +When the LADN Information for the UE in the 5GC is changed, the AMF shall update LADN Information to the UE through UE Configuration Update/Registration procedure as described in clauses 4.2.4 / 4.2.2.2.2 of TS 23.502 [3]. + +When receiving PDU Session Establishment with LADN DNN or Service Request for the established PDU Session corresponding to LADN, the AMF determines UE presence in LADN service area and forwards it to the SMF if the requested DNN is configured at the AMF as a LADN DNN. + +Based on the LADN Service Area Information in the UE, the UE determines whether it is in or out of a LADN service area. If the UE does not have the LADN Service Area Information for a LADN DNN, the UE shall consider it is out of the LADN service area. + +The UE takes actions as follows: + +- a) When the UE is out of a LADN service area, the UE: + - shall not request to activate UP connection of a PDU Session for this LADN DNN; + - shall not attempt to send user data as payload of a NAS message (see clause 5.31.4.1) using a PDU Session for this LADN DNN; + - shall not establish/modify a PDU Session for this LADN DNN (except for PS Data Off status change reporting for an established PDU Session); + - need not release any existing PDU Session for this LADN DNN unless UE receives explicit SM PDU Session Release Request message from the network. +- b) When the UE is in a LADN service area, the UE: + - may request a PDU Session Establishment/Modification for this LADN DNN; + - may request to activate UP connection of the existing PDU Session for this LADN DNN; + - may attempt to send user data as payload of a NAS message (see clause 5.31.4.1) using a PDU Session for this LADN DNN. + +NOTE 6: The evaluation of Service Area Restrictions will be performed before the evaluation of LADN service area, if the UE has overlapping areas between Service Area Restrictions and LADN service area. + +The SMF supporting a DNN is configured with information about whether this DNN is a LADN DNN or not. + +When receiving SM request corresponding an LADN from the AMF, the SMF determines whether the UE is inside LADN service area based on the indication (i.e. UE Presence in LADN service area) received from the AMF. If the SMF does not receive the indication, the SMF considers that the UE is outside of the LADN service area. The SMF shall reject the request if the UE is outside of the LADN service area. + +When the SMF receives a request for PDU Session Establishment with the LADN DNN, it shall subscribe to "UE mobility event notification" for reporting UE presence in Area of Interest by providing LADN DNN to the AMF as described in clauses 5.6.11 and 5.3.4.4. + +Based on the notification about the UE presence in LADN service area notified by AMF (i.e. IN, OUT, or UNKNOWN), the SMF takes actions as follows based on operator's policy: + +- a) When SMF is informed that the UE presence in a LADN service area is OUT, the SMF shall: + - release the PDU Session immediately; or + - deactivate the user plane connection for the PDU Session and it shall not attempt to send user data as payload of a NAS message (see clause 5.31.4.1) while maintaining the PDU Session and ensure the Data Notification is disabled and the SMF may release the PDU Session if the SMF is not informed that the UE moves into the LADN service area after a period. +- b) When SMF is informed that the UE presence a LADN service area is IN, the SMF shall: + - ensure that Data Notification is enabled. + - trigger the Network triggered Service Request procedure for a LADN PDU Session to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. +- c) When the SMF is informed that the UE presence in a LADN service area is UNKNOWN, the SMF may: + - ensure that Data Notification is enabled. + - trigger the Network triggered Service Request procedure for a LADN PDU Session to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. + +SMF may make use of UE mobility analytics provided by NWDAF, as described in clause 6.7.2 of TS 23.288 [86], to determine UE presence pattern in LADN service area and take a decision how to handle LADN PDN Session (e.g. release the PDU Session immediately, or deactivate the user plane connection for the PDU Session with maintaining the PDU Session). + +#### 5.6.5a Supporting LADN per DNN and S-NSSAI + +The 5GS may support LADN per DNN and S-NSSAI, and the functions specified in clause 5.6.5 are used (with the extension to apply per DNN and S-NSSAI whenever applicable) with the following enhancements: + +- The UE indicates the support of LADN per DNN and S-NSSAI in the UE MM Core Network Capability of the Registration Request message. +- The LADN service area can be provisioned for a group (e.g. 5G VN group) or an individual subscriber using UDM/NEF parameter provisioning service triggered by AF request as described in clause 4.15.6 of TS 23.502 [3]. +- LADN service area per DNN and S-NSSAI may be configured in the AMF. The LADN service area may also be provided to AMF as part of the subscription data from UDM. +- The LADN Service Area Information provided to the UE is determined by AMF, based on the Registration Area that the AMF assigns to the UE and either the local configured LADN service area or the LADN service area + +received from UDM. In case there is both a configured LADN service area and a LADN service area received from UDM, the AMF decides based on operator configuration which one takes precedence. + +- If the UE indicates support of LADN per DNN and S-NSSAI, the AMF may provide the LADN Service Area Information per LADN DNN and S-NSSAI to the UE. +- If the UE does not indicate support of LADN per DNN and S-NSSAI and the AMF has a LADN service area for the DNN as well as a LADN service area for the DNN and S-NSSAI, the AMF may determine the LADN Service Area Information per LADN DNN sent to UE using the LADN service area for the DNN as described in clause 5.6.5. +- If the UE does not indicate support of LADN per DNN and S-NSSAI and the AMF has no LADN service area for the DNN but there is a LADN service area for the DNN and S-NSSAI, then the AMF may determine the LADN Service Area Information per LADN DNN sent to UE using this LADN service area for the DNN and S-NSSAI as the LADN service area for that DNN as described in clause 5.6.5 if the UE is not subscribed to the same DNN for multiple S-NSSAI(s) (i.e. the UE is subscribed to the DNN for a single S-NSSAI only). + +NOTE 1: In order to serve the UEs that do not support LADN per DNN and S-NSSAIs, the operator can avoid using the same DNN for multiple S-NSSAIs if LADN service area is configured per DNN and S-NSSAI. + +- If the UE does not indicate support of LADN per DNN and S-NSSAI and the AMF neither has a LADN service area for the DNN nor has a LADN service area for the DNN and S-NSSAI, the AMF shall not provide any LADN Information to the UE. +- The AMF enforces the LADN Service Area per LADN DNN and S-NSSAI in the same way as is described in clause 5.6.5 with the difference that the LADN service area is defined per DNN and S-NSSAI. +- The UE enforces the LADN Service Area per LADN DNN and S-NSSAI, if received from the AMF, in the same way as is described in clause 5.6.5 with the difference that the LADN service area is defined per DNN and S-NSSAI. +- If the AMF enforces the LADN Service Area per LADN DNN and S-NSSAI for the UE, the AMF indicates to the SMF during PDU Session Establishment that the PDU Session is subject to LADN per LADN DNN and S-NSSAI. +- If indicated by AMF at PDU Session Establishment that PDU Session is subject to LADN per LADN DNN and S-NSSAI, the SMF configures the DNN of PDU Session as LADN DNN. The SMF shall subscribe to "UE mobility event notification" for reporting UE presence in Area of Interest by providing LADN DNN and S-NSSAI to the AMF as described in clauses 5.6.11 and 5.3.4.4. The SMF handles the PDU session in the same way as described in clause 5.6.5. + +NOTE 2: If the UE has overlapping areas between LADN service area configured per DNN & S-NSSAI, Partial network slice support area, or any combination of them, then the evaluation of Partial network slice support area take precedence over the evaluation of LADN service area configured per DNN and S-NSSAI. + +### 5.6.6 Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session + +At PDU Session Establishment to a DN: + +- The DN-specific identity (TS 33.501 [29]) of a UE may be authenticated/authorized by the DN. + +NOTE 1: the DN-AAA server may belong to the 5GC or to the DN. + +- If the UE provides authentication/authorization information corresponding to a DN-specific identity during the Establishment of the PDU Session, and the SMF determines that Secondary authentication/authorization of the PDU Session Establishment is required based on the SMF policy associated with the DN, the SMF passes the authentication/authorization information of the UE to the DN-AAA server via the UPF if the DN-AAA server is located in the DN. If the SMF determines that Secondary authentication/authorization of the PDU Session Establishment is required but the UE has not provided a DN-specific identity as part of the PDU Session Establishment request, the SMF requests the UE to indicate a DN-specific identity using EAP procedures as described in TS 33.501 [29]. If the Secondary authentication/authorization of the PDU Session Establishment fails, the SMF rejects the PDU Session Establishment. + +NOTE 2: If the DN-AAA server is located in the 5GC and reachable directly, then the SMF may communicate with it directly without involving the UPF. + +- The DN-AAA server may authenticate/authorize the PDU Session Establishment. +- When DN-AAA server authorizes the PDU Session Establishment, it may send DN Authorization Data for the established PDU Session to the SMF. The DN authorization data for the established PDU Session may include one or more of the following: + - A DN Authorization Profile Index which is a reference to authorization data for policy and charging control locally configured in the SMF or PCF. + - a list of allowed MAC addresses for the PDU Session; this shall apply only for PDU Session of Ethernet PDU type and is further described in clause 5.6.10.2. + - a list of allowed VLAN tags for the PDU Session; this shall apply only for PDU Session of Ethernet PDU type and is further described in clause 5.6.10.2. + - DN authorized Session AMBR for the PDU Session. The DN Authorized Session AMBR for the PDU Session takes precedence over the subscribed Session-AMBR received from the UDM. + - Framed Route information (see clause 5.6.14) for the PDU Session. + - L2TP information, such as LNS IP address and/or LNS host name, as described in TS 29.561 [132]. + +SMF policies may require DN authorization without Secondary authentication/authorization. In that case, when contacting the DN-AAA server for authorization, the SMF provides the GPSI of the UE if available. + +Such Secondary authentication/authorization takes place for the purpose of PDU Session authorization in addition to: + +- The 5GC access authentication handled by AMF and described in clause 5.2. +- The PDU Session authorization enforced by SMF with regards to subscription data retrieved from UDM. + +Based on local policies the SMF may initiate Secondary authentication/authorization at PDU Session Establishment. The SMF provides the GPSI, if available, in the signalling exchanged with the DN-AAA during Secondary authentication/authorization. + +After the successful Secondary authentication/authorization, a session is kept between the SMF and the DN-AAA. + +The UE provides the authentication/authorization information required to support Secondary authentication/authorization by the DN over NAS SM. + +If a UE is configured with DNNs, which are subject to secondary authentication/authorization, the UE stores an association between the DNN and corresponding credentials for the secondary authentication/authorization. + +NOTE 3: How the UE is aware that a DNN is subject to secondary authentication/authorization (e.g. based on local configuration) is out of scope of this specification. + +The UE may support remote provisioning of credentials for secondary authentication/authorization, as specified in clause 5.39. + +A UE that supports to be provisioned with the credentials used for secondary authentication/authorization over UP remote provisioning shall use connectivity over an S-NSSAI/DNN which can access the provisioning server to establish a PDU session for remote provisioning as defined in clause 5.39. + +NOTE 4: The credentials for secondary authentication/authorization are not specified. + +SMF policies or subscription information (such as defined in Table 5.2.3.3.1 of TS 23.502 [3]) may trigger the need for SMF to request the Secondary authentication/authorization and/or UE IP address / Prefix from the DN-AAA server. + +When SMF adds a PDU Session Anchor (such as defined in clause 5.6.4) to a PDU Session Secondary authentication/authorization is not carried out, but SMF policies may require SMF to notify the DN when a new prefix or address has been added to or removed from a PDU Session or N6 traffic routing information has been changed for a PDU Session. + +When SMF gets notified from UPF with the addition or removal of MAC addresses to/from a PDU Session, the SMF policies may require SMF to notify the DN-AAA server. + +Indication of PDU Session Establishment rejection is transferred by SMF to the UE via NAS SM. + +If the DN-AAA sends DN Authorization Data for the authorized PDU Session to the SMF and dynamic PCC is deployed, the SMF sends the PCF the DN authorized Session AMBR and/or DN Authorization Profile Index in the DN Authorization Data for the established PDU Session. + +If the DN-AAA sends DN Authorization Profile Index in DN Authorization Data to the SMF and dynamic PCC is not deployed, the SMF uses the DN Authorization Profile Index to refer the locally configured information. + +NOTE 5: DN Authorization Profile Index is assumed to be pre-negotiated between the operator and the administrator of DN-AAA server. + +If the DN-AAA does not send DN Authorization Data for the established PDU Session, the SMF may use locally configured information. + +At any time, a DN-AAA server may revoke the authorization for a PDU Session or update DN Authorization Data for a PDU Session. According to the request from DN-AAA server, the SMF may release or update the PDU Session. See clause 5.6.14 when the update involves Framed Route information. + +At any time, a DN-AAA server or SMF may trigger Secondary Re-authentication procedure for a PDU Session established with Secondary Authentication as specified in clause 11.1.3 of TS 33.501 [29]. + +During Secondary Re-authentication/Re-authorization, if the SMF receives from DN-AAA the DN authorized Session AMBR and/or DN Authorization Profile Index, the SMF shall report the received value(s) to the PCF. + +The procedure for secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session is described in clause 4.3.2.3 of TS 23.502 [3]. + +The support for L2TP on N6 is further specified in clause 5.8.2.16, and the procedure for establishment of L2TP tunnelling on N6 for a PDU Session is described in clause 4.3.2.4 of TS 23.502 [3]. + +NOTE 6: The L2TP Tunnel information sent to the SMF can, for example, be provisioned in the DN-AAA server per DNN/S-NSSAI or per SUPI or GPSI. + +### 5.6.7 Application Function influence on traffic routing + +#### 5.6.7.1 General + +The content of this clause applies to non-roaming and to LBO deployments i.e. to cases where the involved entities (AF, PCF, SMF, UPF) belong to the Serving PLMN or AF belongs to a third party with which the Serving PLMN has an SLA agreement. + +AF influence on traffic routing may apply in the case of Home Routed deployments with Session Breakout (HR SBO) as defined in TS 23.548 [130]. In that case when an AF belonging to the V-PLMN (or with an offloading SLA with the V PLMN) desires to provide Traffic Influence policies it may invoke at the V-NEF the API defined in this clause and provide the information listed in Table 5.6.7-1 below but the corresponding Traffic Influence information is provided directly from V-NEF to V-SMF bypassing the PCF. This is further defined in TS 23.548 [130] clause 6.7.2. and the rest of the clause 5.6.7.1 does not address how information related with AF influence on traffic routing may be provided to the SMF in the case of HR SBO. + +PCF shall not apply AF requests to influence traffic routing to PDU Sessions established in Home Routed mode. + +The AF may determine the common EAS/DNAI for the UE set in order to indicate a common EAS or common local part of DN, and provide the common EAS/DNAI to the 5GS. + +An AF may send requests to influence SMF routing decisions for traffic of PDU Session. The AF requests may influence UPF (re)selection and (I-)SMF (re)selection and allow routing user traffic to a local access to a Data Network (identified by a DNAI). + +The AF may issue requests on behalf of applications not owned by the PLMN serving the UE. + +If the operator does not allow an AF to access the network directly, the AF shall use the NEF to interact with the 5GC, as described in clause 6.2.10. + +The AF may be in charge of the (re)selection or relocation of the applications within the local part of the DN (as defined in TS 23.548 [130]). Such functionality is not defined. For this purpose, the AF may request to get notified about events related with PDU Sessions. + +In the case of AF instance change, the AF may send request of AF relocation information. + +The AF requests are sent to the PCF via N5 (in the case of requests targeting specific on-going PDU Sessions of individual UE(s), for an AF allowed to interact directly with the 5GC NFs) or via the NEF. The AF requests that target existing or future PDU Sessions of multiple UE(s) or of any UE are sent via the NEF and may target multiple PCF(s), as described in clause 6.3.7.2. The PCF(s) transform(s) the AF requests into policies that apply to PDU Sessions. When the AF has subscribed to UP path management event notifications from SMF(s) (including notifications on how to reach a GPSI over N6), such notifications are sent either directly to the AF or via an NEF (without involving the PCF). For AF interacting with PCF directly or via NEF, the AF requests may contain the information as described in the Table 5.6.7-1: + +**Table 5.6.7-1: Information element contained in AF request** + +| Information Name | Applicable for PCF or NEF
(NOTE 1) | Applicable for NEF only | Category | +|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| Traffic Description | Defines the target traffic to be influenced, represented by the combination of DNN and optionally S-NSSAI and optionally PLMN ID of the PLMN that the DNN/S-NSSAI belongs to and application identifier or traffic filtering information. (NOTE 7) (NOTE 8) | The target traffic can be represented by AF-Service-Identifier, instead of combination of DNN and optionally S-NSSAI. | Mandatory | +| Potential Locations of Applications | Indicates potential locations of applications, represented by a list of DNAI(s) and optionally PLMN ID of the PLMN that the list of DNAI(s) belongs to. (NOTE 8) | The potential locations of applications can be represented by AF-Service-Identifier. | Conditional
(NOTE 2) | +| Target UE Identifier(s) | Indicates the UE(s) that the request is targeting, i.e. one or a list of individual UE(s), a group of UE represented by Internal Group Identifier(s) (NOTE 3), or any UE accessing the combination of DNN, S-NSSAI and DNAI(s). | GPSI can be applied to identify the individual UE, or External Group Identifier(s) can be applied to identify a group of UE (NOTE 3). External Subscriber Category(s) (NOTE 5). | Mandatory | +| Spatial Validity Condition | Indicates that the request applies only to the traffic of UE(s) located in the specified location, represented by areas of validity. | The specified location can be represented by geographical area. | Optional | +| AF transaction identifier | The AF transaction identifier refers to the AF request. | N/A | Mandatory | +| N6 Traffic Routing requirements | Routing profile ID and/or N6 traffic routing information corresponding to each DNAI and an optional indication of traffic correlation (NOTE 4). | N/A | Optional
(NOTE 2) | +| Application Relocation Possibility | Indicates whether an application can be relocated once a location of the application is selected by the 5GC. | N/A | Optional | +| UE IP address preservation indication | Indicates UE IP address should be preserved. | N/A | Optional | +| Temporal Validity Condition | Time interval(s) or duration(s). | N/A | Optional | +| Information on AF subscription to corresponding SMF events | Indicates whether the AF subscribes to change of UP path of the PDU Session and the parameters of this subscription. | N/A | Optional | +| Information for EAS IP Replacement in 5GC | Indicates the Source EAS identifier and Target EAS identifier, (i.e. IP addresses and port numbers of the source and target EAS). | N/A | Optional | +| User Plane Latency Requirement | Indicates the user plane latency requirements | N/A | Optional | +| Information on AF change | N/A | Indicates the AF instance relocation and relocation information. | Optional | +| Indication for EAS Relocation | Indicates the EAS relocation of the application(s) | N/A | Optional | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----------| +| Indication for Simultaneous Connectivity over the source and target PSA at Edge Relocation | Indicates that simultaneous connectivity over the source and target PSA should be maintained at edge relocation and provides guidance to determine when the connectivity over the source PSA can be removed. | N/A | Optional | +| EAS Correlation indication | Indicates selecting a common EAS for the application identified by the Traffic Description for the set of UEs. | | Optional | +| Common EAS IP address | the common EAS for the application identified by the Traffic Description for a set of UEs the AF request aims at. | | Optional | +| Traffic Correlation ID | Identification of a set of UEs targeted at by the AF request, and accessing the application identified by the Traffic Description. | | Optional | +| FQDN(s) | FQDN(s) used for influencing EASDF-based DNS query procedure as defined in TS 23.548 [130] (NOTE 6). | | Optional | +| NOTE 1: When the AF request targets existing or future PDU Sessions of multiple UE(s) or of any UE and is sent via the NEF, as described in clause 6.3.7.2, the information is stored in the UDR by the NEF and notified to the PCF by the UDR. | | | | +| NOTE 2: The potential locations of applications and N6 traffic routing requirements may be absent only if the request is for subscription to notifications about UP path management events or the request is for indication of selecting Common EAS for a set of UEs. | | | | +| NOTE 3: Internal Group ID can only be used by an AF controlled by the operator and only towards PCF. If a list of Internal/External Group IDs is provided by the AF, the AF request applies to the UEs that belong to every one of these groups, i.e. a single UE needs to be a member of every group in the list of Internal/External Group IDs. | | | | +| NOTE 4: The indication of traffic correlation can be used for 5G VN groups as described in clause 5.29. | | | | +| NOTE 5: External Subscriber category(s) can be combined with External Group ID(s) or any UE. If a list of External Subscriber categories is provided by the AF, the AF request applies to the UEs that belong to every one of these Subscriber categories, i.e. the UE has all these Subscriber categories in its subscription data. | | | | +| NOTE 6: FQDN(s) is used for influencing EASDF-based DNS query procedure as defined in clause 6.2.3.2.2 of TS 23.548 [130]. | | | | +| NOTE 7: If the FQDN is included in the AF request, the EASDF-based EAS discovery procedure will be followed as defined in TS 23.548 [130] using this FQDN for the purpose of setting traffic route and finding DNAI, and Traffic Description will be ignored. | | | | +| NOTE 8: PLMN ID is used for HR-SBO case as defined in clause 4.3.6.1 of TS 23.502 [3]. In this case, DNN and S-NSSAI are the ones of the HPLMN. | | | | + +For each information element mentioned above in the AF request, the detailed description is as follows: + +1) Information to identify the traffic. The traffic can be identified in the AF request by + +- Either a DNN and possibly slicing information (S-NSSAI) or an AF-Service-Identifier + - When the AF provides an AF-Service-Identifier i.e. an identifier of the service on behalf of which the AF is issuing the request, the 5G Core maps this identifier into a target DNN and slicing information (S-NSSAI) + - When the NEF processes the AF request the AF-Service-Identifier may be used to authorize the AF request. +- An application identifier or traffic filtering information (e.g. IP 5 Tuple). The application identifier refers to an application handling UP traffic and is used by the UPF to detect the traffic of the application. + +When the AF request is for influencing SMF routing decisions, the information is to identify the traffic to be routed. + +When the AF request is for subscription to notifications about UP path management events, the information is to identify the traffic that the events relate to. The AF request may include a PLMN ID of the PLMN that the DNN and S-NSSAI belong to, as described in clause 4.3.6.1 of TS 23.502 [3]. + +2) Information about the N6 traffic routing requirements for traffic identified as defined in 1). This includes: + +- Information about the N6 traffic routing requirements that is provided per DNAI: for each DNAI, the N6 traffic routing requirements may contain a routing profile ID and/or N6 traffic routing information. +- An optional indication of traffic correlation, when the information in 4) identifies a group of UEs. This implies the targeted PDU Sessions should be correlated by a common DNAI in the user plane for the traffic identified in 1). If this indication is provided by the AF, the 5GC should select a common DNAI for the target PDU Sessions from the list of DNAI(s) specified in 3). + +NOTE 1: The N6 traffic routing requirements are related to the mechanism enabling traffic steering in the local access to the DN. The routing profile ID refers to a pre-agreed policy between the AF and the 5GC. This policy may refer to different steering policy ID(s) sent to SMF and e.g. based on time of the day etc. + +NOTE 2: The mechanisms enabling traffic steering in the local access to the DN are not defined. + +3) Potential locations of applications towards which the traffic routing should apply. The potential location of application is expressed as a list of DNAI(s). If the AF interacts with the PCF via the NEF, the NEF may map the AF-Service-Identifier information to a list of DNAI(s). The DNAI(s) may be used for UPF (re)selection and (I-)SMF (re)selection. When only one DNAI is included, and the Indication of traffic correlation is available, the DNAI is used as common DNAI for UEs identified by AF request. The AF request may include a PLMN ID of the PLMN that the list of DNAI(s) belongs to, as described in clause 4.3.6.1 of TS 23.502 [3]. + +4) Information on the set of target UE(s). This may correspond to: + +- Individual UEs (i.e. one or a list of UEs) identified using GPSI, or an IP address/Prefix or a MAC address. +- Group(s) of UEs identified by External Group Identifier(s) as defined in TS 23.682 [36] when the AF interacts via the NEF, or Internal-Group Identifier (see clause 5.9.7) when the AF interacts directly with the PCF. +- Any UE accessing the combination of DNN, S-NSSAI and DNAI(s). +- External Group ID(s) or any UE can both be complemented with External Subscriber Category(s) for a more granular selection of UEs. NEF may map this to Internal Group ID(s) or a combination of Internal Group ID(s) and Subscriber Category(s), defined in TS 23.503 [45]. + +NOTE 3: Only NEF is aware of the External Subscriber Category. As a user can be associated with multiple Subscriber Category(s), some values of Subscriber Category(s) can correspond to an SLA between an application provider represented by an AF and the 5GC operator. In the NEF API, the combination of application identifier and External Subscriber Category can also be used to refer to this SLA. + +When the PDU Session type is IPv4 or IPv6 or IPv4v6, and the AF provides an IP address and/or an IP Prefix, or when the PDU Session type is Ethernet and the AF provides a MAC address, this allows the PCF to identify the PDU Session for which this request applies and the AF request applies only to that specific PDU Session of the UE. In this case, additional information such as the UE identity may also be provided to help the PCF to identify the correct PDU Session. + +Otherwise, the request targets multiple UE(s) and shall apply to any existing or future PDU Sessions that match the parameters in the AF request. + +When the AF request targets an individual or a list of UE(s) and GPSI is provided within the AF request, the GPSI is mapped to SUPI according to the subscription information received from UDM. + +When the AF request targets any UE or a group of UE, the AF request is likely to influence multiple PDU Sessions possibly served by multiple SMFs and PCFs. + +When the AF request targets a group of UE it provides one or several group identifiers in its request. The group identifiers provided by the AF are mapped to Internal-Group identifiers. Members of the group have Group Identifier(s) in their subscription. The Internal-Group Identifier(s) is(are) stored in UDM, retrieved by SMF from UDM and passed by SMF to PCF at PDU Session set-up. The PCF can then map the AF request + +with user subscription and determine whether an AF request targeting a Group of users applies to a PDU Session. When External Subscriber Category(s) is provided, the NEF maps External Subscriber Category(s) into Subscriber Category(s), the PCF can map the AF request with user subscription and then creates PCC rules for UEs that have the Subscriber Category(s) in their subscription. + +When the AF request is for influencing SMF routing decisions, the information is to identify UE(s) whose traffic is to be routed. + +When the AF request is for subscription to notifications about UP path management events, the information is to identify UE(s) whose traffic the events relate to. + +When the AF request is for traffic forwarding in a PDU Session serving for TSC, the MAC address used by the PDU Session is determined by the AF to identify UE whose traffic is to be routed according to the previously stored binding relationship of the 5GS Bridge and the port number of the traffic forwarding information received from TSN network. + +- 5) Indication of application relocation possibility. This indicates whether an application can be relocated once a location of the application is selected by the 5GC. If application relocation is not possible, the 5GC shall ensure that for the traffic related with an application, no DNAI change takes place once selected for this application. +- 6) Temporal validity condition. This is provided in the form of time interval(s) or duration(s) during which the AF request is to be applied. + +When the AF request is for influencing SMF routing decisions, the temporal validity condition indicates when the traffic routing is to apply. + +When the AF request is for subscription to notifications about UP path management events, the temporal validity condition indicates when the notifications are to be generated. + +- 7) Spatial validity condition on the UE(s) location. This is provided in the form of validity area(s). If the AF interacts with the PCF via the NEF, it may provide geographical area (e.g. a civic address or shapes) and the NEF maps the information to areas of validity based on pre-configuration. The PCF in turn determines area(s) of interest based on validity area(s). + +When the AF request is for influencing SMF routing decisions, the spatial validity condition indicates that the request applies only to the traffic of UE(s) located in the specified location. + +When the AF request is for subscription to notifications about UP path management events, the spatial validity condition indicates that the subscription applies only to the traffic of UE(s) located in the specified location. + +- 8) Information on AF subscription to corresponding SMF events. + +The AF may request to be subscribed to change of UP path associated with traffic identified in the bullet 1) above. The AF request contains: + +- A type of subscription (subscription for Early and/or Late notifications). + +The AF subscription can be for Early notifications and/or Late notifications. In the case of a subscription for Early notifications, the SMF sends the notifications before the (new) UP path is configured. In the case of a subscription for Late notifications, the SMF sends the notification after the (new) UP path has been configured. + +- Notification target address for receiving event notification. +- Optionally, an indication of "AF acknowledgment to be expected". + +The indication implies that the AF will provide a response to the notifications of UP path management events to the 5GC. The SMF may, according to this indication, determine to wait for a response from the AF before the SMF configures in the case of early notification, or activates in the case of late notification, the new UP path as described in clause 5.6.7.2. + +- Optionally, an immediate reporting flag. + +The immediate reporting flag is included when AF subscribe for candidate DNAI(s) of UE for common EAS/DNAI selection. With this flag, SMF should immediately response AF with the candidate DNAI(s) using Notification of user plane management event as described in clause 4.3.6.3 in TS 23.502 [3]. + +The AF subscription can also request to receive information associating the GPSI of the UE with the IP address(es) of the UE and/or with actual N6 traffic routing to be used to reach the UE on the PDU Session; in this case the corresponding information is sent by the SMF regardless of whether a DNAI applies to the PDU Session. + +- 9) An AF transaction identifier referring to the AF request. This allows the AF to update or remove the AF request and to identify corresponding UP path management event notifications. The AF transaction identifier is generated by the AF. + +When the AF interacts with the PCF via the NEF, the NEF maps the AF transaction identifier to an AF transaction internal identifier, which is generated by the NEF and used within the 5GC to identify the information associated to the AF request. The NEF maintains the mapping between the AF transaction identifier and the AF transaction internal identifier. The relation between the two identifiers is implementation specific. + +When the AF interacts with the PCF directly, the AF transaction identifier provided by the AF is used as AF transaction internal identifier within the 5GC. + +- 10) Indication of UE IP address preservation. This indicates UE IP address related to the traffic identified in bullet 1) should be preserved. If this indication is provided by the AF, the 5GC should preserve the UE IP address by preventing reselection of PSA UPF for the identified traffic once the PSA UPF is selected. +- 11) Information for EAS IP Replacement in 5GC. This indicates the Source EAS identifier and Target EAS identifier (i.e. IP addresses and port numbers of the source and target EAS) for a service subject to Edge Computing. +- 12) User Plane Latency Requirement. This includes AF requirements for User Plane latency. (see clause 6.3.6 of TS 23.548 [130]). +- 13) Information on AF change. The AF relocation information includes: + - AF Identifier: the identifier of the target AF instance. + +NOTE 4: The AF relocation information is applicable for interaction with NEF only and it is not stored in UDR or transferred to PCF, even for the case AF directly interacts with PCF. + +- 14) Indication for EAS relocation. This indicates the application(s) are to be relocated. +- 15) Indication for Simultaneous Connectivity over source and target PSA at Edge Relocation (see clause 6.3.4 of TS 23.548 [130]). Indicates that source and target PSA should coexist for some time at PSA relocation, and may influence the establishment of a temporary N9 forwarding tunnel between the source UL CL and target UL CL. It may also provide guidance for the time interval after the described traffic ceases when the connectivity over the source PSA may be removed. +- 16) Traffic Correlation ID. Identification of a set of UEs subjecting to the AF request and accessing the application identified by the Traffic Description. UEs associated with the same Traffic Correlation ID and accessing the application identified by the Traffic Description should connect to a common EAS or EAS(es) corresponding to a common DNAI. + +The following attributes may be provided with the Traffic Correlation ID: + +- EAS Correlation indication. Indicates selecting a common EAS for a set of UEs identified by Traffic Correlation ID and accessing the application identified by the Traffic Description. +- Common EAS IP address. IP address of the common EAS to be accessed by the UEs in the set of UEs subject to AF request, for the application identified by the Traffic Description. + +NOTE 5: In the case of common EAS selection, if Traffic Correlation ID is provided, either EAS Correlation indication or Common EAS will be included in AF request. + +- FQDN(s). FQDN(s) corresponding to the application to be accessed by a set of UEs. When FQDN(s) is included, it is used for influencing EAS discovery procedure as defined in TS 23.548 [130]. +- Indication of traffic correlation as described in 2). + +An AF may send requests to influence SMF routing decisions, for event subscription or for both. + +The AF may request to be subscribed to notifications about UP path management events, i.e. a UP path change occurs for the PDU Session. The corresponding notification about a UP path change sent by the SMF to the AF may indicate the DNAI and /or the N6 traffic routing information and/or common EAS that has changed as described in clause 4.3.6.3 of TS 23.502 [3]. It may include the AF transaction internal identifier, the type of notification (i.e. early notification or late notification), the Identity of the source and/or target DNAI, the IP address/prefix of the UE or the MAC address used by the UE, the GPSI and the N6 traffic routing information related to the 5GC UP. The AF may subscribe for notifications of candidate DNAI(s) for UE if AF selection of common EAS/DNAI for a set of UEs is used. + +NOTE 6: The change from the UP path status where no DNAI applies to a status where a DNAI applies indicates the activation of this AF request; the change from the UP path status where a DNAI applies to a status where no DNAI applies indicates the de-activation of this AF request. + +In the case of IP PDU Session Type, the IP address/prefix of the UE together with N6 traffic routing information indicates to the AF how to reach over the User Plane the UE identified by its GPSI. N6 traffic routing information indicates any tunnelling that may be used over N6. The nature of this information depends on the deployment. + +NOTE 7: N6 traffic routing information can e.g. correspond to the identifier of a VPN or to explicit tunnelling information such as a tunnelling protocol identifier together with a Tunnel identifier. + +NOTE 8: In the case of Unstructured PDU Session type the nature of the N6 traffic routing information related to the 5GC UP is described in clause 5.6.10.3. + +In the case of Ethernet PDU Session Type, the MAC address of the UE together with N6 traffic routing information indicates to the AF how to reach over the User Plane the UE identified by its GPSI. The UE MAC address (es) is reported by the UPF as described in clause 5.8.2.12. The N6 traffic routing information can be, e.g. a VLAN ID or the identifier of a VPN or a tunnel identifier at the UPF. + +When notifications about UP path management events are sent to the AF via the NEF, if required, the NEF maps the UE identify information, e.g. SUPI, to the GPSI and the AF transaction internal identifier to the AF transaction identifier before sending the notifications to the AF. + +The PCF, based on information received from the AF, operator's policy, optionally service experience analytics per UP path received from NWDAF, etc. authorizes the request received from the AF and determines for each DNAI, a traffic steering policy ID (derived from the routing profile ID provided by the AF) and/or the N6 traffic routing information (as provided by the AF) to be sent to the SMF as part of the PCC rules. The traffic steering policy IDs are configured in the SMF or in the UPF. The traffic steering policy IDs are related to the mechanism enabling traffic steering to the DN. + +The DNAIs are related to the information considered by the SMF for UPF selection and (I-)SMF (re)selection, e.g. for diverting (locally) some traffic matching traffic filters provided by the PCF. + +The PCF acknowledges a request targeting an individual PDU Session to the AF or to the NEF. + +For PDU Session that corresponds to the AF request, the PCF provides the SMF with a PCC rule that is generated based on the AF request, Local routing indication from the PDU Session policy control subscription information and taking into account UE location presence in area of interest (i.e. Presence Reporting Area). The PCC rule contains the information to identify the traffic, information about the DNAI(s) towards which the traffic routing should apply and optionally, an indication of traffic correlation and/or an indication of application relocation possibility and/or indication of UE IP address preservation. The PCC rule also contains per DNAI a traffic steering policy ID and/or N6 traffic routing information, if the N6 traffic routing information is explicitly provided in the AF request. + +If Traffic Correlation ID is included in the AF request, with EAS Correlation Indication or Common EAS, and FQDN(s) parameters, the Traffic Correlation ID and the EAS Correlation Indication or Common EAS, and FQDN(s) will be included in the PCC rule sent to SMF. The SMF can use the Traffic Correlation ID to determine that the UE belongs to a set of UEs identified by Traffic Correlation ID and a common EAS should be selected for the set of UE for the traffic identified by Traffic Descriptor as described in clause 6.2.3.2.5 of TS 23.548 [130]. + +If Traffic Correlation ID is included in the AF request, NEF updates the AF influence data in the UDR with the NEF Notification Endpoint to indicate it as responsible of the set of UEs associated with the Traffic correlation ID and to be notified with 5GC determined information as described in clause 6.2.3.2.7 of TS 23.548 [130]. + +The PCF provides in the PCC rule with information including the NEF Notification Endpoint for the SMF to notify to the NEF with 5GC determined information related to the UE members of the set of UEs identified by traffic correlation ID. + +If Traffic Correlation ID, and traffic correlation indication and FQDN(s) is included in the AF request, the Traffic Correlation ID and the traffic correlation indication will be included in the PCC rule sent to SMF. The SMF can use the Traffic Correlation ID to determine that the UE belongs to a set of UEs identified by Traffic Correlation ID and the UE needs to connect to EAS(s) corresponding to a common DNAI selected for the set of UE for the traffic identified by Traffic Descriptor, as described in clause 6.2.3.2.6 of TS 23.548 [130]. + +The PCF may also provide in the PCC rule information to subscribe the AF (or the NEF) to SMF events (UP path changes) corresponding to the AF request in which case it provides the information on AF subscription to corresponding SMF events received in the AF request. This is done by providing policies at PDU Session set-up or by initiating a PDU Session Modification procedure. When initiating a PDU Session set-up or PDU Session Modification procedure, the PCF considers the latest known UE location to determine the PCC rules provided to the SMF. The PCF evaluates the temporal validity condition of the AF request and informs the SMF to activate or deactivate the corresponding PCC rules according to the evaluation result. When policies specific to the PDU Session and policies general to multiple PDU Sessions exist, the PCF gives precedence to the PDU Session specific policies over the general policies. The PCF authorizes the AF request of User Plane Latency Requirements. If the PCF determines that the requirements can't be authorized, the PCF rejects the AF request. + +The spatial validity condition is resolved at the PCF. In order to do that, the PCF subscribes to the SMF to receive notifications about change of UE location in an area of interest (i.e. Presence Reporting Area). The subscribed area of interest may be the same as spatial validity condition, or may be a subset of the spatial validity condition (e.g. a list of TAs) based on the latest known UE location. When the SMF detects that UE entered the area of interest subscribed by the PCF, the SMF notifies the PCF and the PCF provides to the SMF the PCC rules described above by triggering a PDU Session Modification. When the SMF becomes aware that the UE left the area subscribed by the PCF, the SMF notifies the PCF and the PCF provides updated PCC rules by triggering a PDU Session Modification. SMF notifications to the PCF about UE location in or out of the subscribed area of interest are triggered by UE location change notifications received from the AMF or by UE location information received during a Service Request or Handover procedure. + +When the PCC rules are activated, the SMF may, based on local policies, take the information in the PCC rules and, optionally, the Service Experience analytics and/or DN Performance analytics per UP path (including UPF and/or DNAI and/or AS instance) as defined in clause 6.4.3 and clause 6.14.3, respectively, of TS 23.288 [86] into account to: + +- (re)select UP paths (including DNAI(s)) for PDU Sessions. The SMF is responsible for handling the mapping between the UE location (TAI / Cell-Id) and DNAI(s) associated with UPF and applications and the selection of the UPF(s) that serve a PDU Session. This is described in clause 6.3.3. If the PDU Session is of IP type and if Indication of UE IP address preservation is included in the PCC rules, the SMF should preserve the UE IP address, by not reselecting the related PSA UPF once the PSA UPF is selected, for the traffic identified in the PCC rule. If the user plane latency requirement is included in the PCC rules, the SMF chooses the PSA UPF that satisfies the user plane latency requirement. If the PCC rules are related to a 5G VN group served by the SMF and if the PCC rule includes an indication of traffic correlation, the SMF should select a common DNAI for the PDU Sessions of the 5G VN group, see clause 5.29. +- configure traffic steering at UPF, including activating mechanisms for traffic multi-homing or enforcement of an UL Classifier (UL CL). Such mechanisms are defined in clause 5.6.4. This may include that the SMF is providing the UPF with packet handling instructions (i.e. PDRs and FARs) for steering traffic to the local access to the DN. The packet handling instructions are generated by the SMF using the traffic steering policy ID and/or the N6 traffic routing information in the PCC rules corresponding to the applied DNAI. In the case of UP path reselection, the SMF may configure the source UPF to forward traffic to the UL CL/BP so that the traffic is steered towards the target UPF. +- if Information on AF subscription to corresponding SMF events has been provided in the PCC rule, inform the AF of the (re)selection of the UP path (UP path change). If the information includes an indication of "AF acknowledgment to be expected", the SMF may decide to wait for a response from the AF before it activates the new UP path, as described in clause 5.6.7.2. + +When an I-SMF is inserted for a PDU Session, the I-SMF insertion, relocation or removal to a PDU session shall be transparent (i.e. not aware) to the PCF and to the AF. The processing of the AF influence on traffic routing is described in clause 5.34 and detailed procedure is described in clause 4.23.6 of TS 23.502 [3]. + +#### 5.6.7.2 Enhancement of UP path management based on the coordination with AFs + +In order to avoid or minimize service interruption during PSA relocation for a PDU session of SSC mode 3, or a PDU session with UL CL or branch point, according to the indication of "AF acknowledgment to be expected" on AF + +subscription to corresponding SMF events (DNAI change) (that may be provided in PCC rules received from the PCF as defined in clause 5.6.7.1 except in HR-SBO case or that may be provided directly by V-NEF to V-SMF as defined in TS 23.548 [130] clause 6.7.2 in case of HR-SBO) or according to local configuration (e.g. DN-related policies) the SMF may wait for a response from the AF after sending a notification (an early notification or a late notification) to the AF. In the case of late notification, based on the indication of "AF acknowledgment to be expected" on AF subscription, the SMF may send the notification before activating the UP path towards a new DNAI (possibly through a new PSA). + +NOTE 1: Before the UP path toward the new DNAI is activated, application traffic data (if any exists) is still routed toward the old DNAI. + +The notification sent from the SMF to the AF indicates UP path management events (DNAI change) as described in clause 5.6.7.1. The AF can confirm the DNAI change indicated in the notification with the SMF by sending a positive response to the notification to the SMF or reject the DNAI change by sending a negative response. + +NOTE 2: The AF can determine whether application relocation is needed according to the notification of DNAI change. If not, the AF can send a positive response to the SMF immediately; otherwise, the AF sends the positive response after application relocation is completed or a negative response if the AF determines that the application relocation cannot be completed on time (e.g. due to temporary congestion). The AF decision and behaviours on application relocation are not defined. However, the new DNAI may be associated with a new AF. In such cases, the SMF and the old AF cancel earlier subscribed UP path management event notifications, and the new AF subscribes to receive UP path management event notifications from the SMF. + +The AF can include N6 traffic routing information related to the target DNAI in a positive response sent to the SMF. The SMF configures the N6 traffic routing information from the AF response to the PSA on the UP path. + +The AF can include the EAS relocation Indication to indicate the application(s) to be relocated. + +In the case of early notification, based on the indication of "AF acknowledgment to be expected" on AF subscription, the SMF does not configure the UP path towards the new DNAI until it receives a positive AF response as specified in clause 4.3.6.3 of TS 23.502 [3]. + +In the case of late notification, based on the indication of "AF acknowledgment to be expected" on AF subscription, the SMF does not activate the UP path towards the new DNAI until it receives a positive AF response as specified in clause 4.3.5 of TS 23.502 [3]. + +NOTE 3: After the UP path toward the new DNAI is activated, data is routed toward the new DNAI. + +If the SMF receives a negative response at any time, the SMF keeps using the original DNAI and may cancel related PSA relocation or addition. The SMF may perform DNAI reselection afterwards if needed. + +The SMF can assume according to local policy a negative response if a response is expected and but not received from the AF within a certain time window. + +When Early/Late Notification happens, the SMF notifies AF about the target DNAI and may indicate capability of supporting EAS IP replacement in 5GC. When EAS relocation is performed, the AF sends an/a early/late notification response to the SMF after the EAS relocation is completed, which may include the Information for EAS IP Replacement in 5GC. The SMF may instruct the local PSA with the EAS IP address replacement using "Outer Header Creation" as defined in clause 5.8.5.6 and "Outer Header Removal" as defined in clause 5.8.5.3. If local PSA relocation is required, the SMF may request the target local PSA to buffer uplink traffic as described in clause 6.3.5 of TS 23.548 [130]. + +AF relocation may be triggered by SMF e.g. in relationship with DNAI change due to UE mobility. In the case of AF relocation involving different DNAI(s), it is possible that the source EHE is unaware of other/target EHE specific deployment details. In such cases, when SMF selects a target DNAI (e.g. based on current UE location), the SMF may determine based on the EDI that the target DNAI is not supported by the source AF. The SMF determines the target AF ID based on the target DNAI and the EDI. Accordingly, as part of Early/Late Notification, the SMF provides the target AF ID to the source AF as described in clause 4.3.6.3 of TS 23.502 [3]. + +### 5.6.8 Selective activation and deactivation of UP connection of existing PDU Session + +This clause applies to the case when a UE has established multiple PDU Sessions. The activation of a UP connection of an existing PDU Session causes the activation of its UE-CN User Plane connection (i.e. data radio bearer and N3 tunnel). + +For the activation of a UP connection the service area restrictions as specified in clause 5.3.4.1.1 apply. + +For the UE in the CM-IDLE state in 3GPP access, either UE or Network-Triggered Service Request procedure may support independent activation of UP connection of existing PDU Session. For the UE in the CM-IDLE state in non-3GPP access, UE-Triggered Service Request procedure allows the re-activation of UP connection of existing PDU Sessions, and may support independent activation of UP connection of existing PDU Session. + +A UE in the CM-CONNECTED state invokes a Service Request (see clause 4.2.3.2 of TS 23.502 [3]) procedure to request the independent activation of the UP connection of existing PDU Sessions. + +Network Triggered re-activation of UP connection of existing PDU Sessions is handled as follows: + +- If the UE CM state in the AMF is already CM-CONNECTED on the access (3GPP, non-3GPP) associated to the PDU Session in the SMF, the network may re-activate the UP connection of a PDU Session using a Network Initiated Service Request procedure. + +Otherwise: + +- If the UE is registered in both 3GPP and non-3GPP accesses and the UE CM state in the AMF is CM-IDLE in non-3GPP access, the UE can be paged or notified through the 3GPP access for a PDU Session associated in the SMF (i.e. last routed) to the non-3GPP access: +- If the UE CM state in the AMF is CM-IDLE in 3GPP access, the paging message may include the access type associated with the PDU Session in the SMF. The UE, upon reception of the paging message containing an access type, shall reply to the 5GC via the 3GPP access using the NAS Service Request message, which shall contain the list of PDU Sessions associated with the received access type and whose UP connections can be re-activated over 3GPP (i.e. the list does not contain the PDU Sessions whose UP connections cannot be re-activated on 3GPP based on UE policies and whether the S-NSSAIs of these PDU Sessions are within the Allowed NSSAI for 3GPP access). If the PDU Session for which the UE has been paged is in the list of the PDU Sessions provided in the NAS Service Request and the paging was triggered by pending DL data, the 5GC shall re-activate the PDU Session UP connection over 3GPP access. If the paging was triggered by pending DL signalling, the Service Request succeeds without re-activating the PDU session UP connection over the 3GPP access and the pending DL signalling is delivered to the UE over the 3GPP access; +- If the UE CM state in the AMF is CM-CONNECTED in 3GPP access, the notification message shall include the non-3GPP Access Type. The UE, upon reception of the notification message, shall reply to the 5GC via the 3GPP access using the NAS Service Request message, which shall contain the List of Allowed PDU Sessions that can be re-activated over 3GPP or an empty List of Allowed PDU Sessions if no PDU Sessions are allowed to be re-activated over 3GPP access. + +NOTE: A UE that is in a coverage of a non-3GPP access and has PDU Session(s) that are associated in the UE (i.e. last routed) to non-3GPP access, is assumed to attempt to connect to it without the need to be paged. + +- If the UE is registered in both 3GPP and non-3GPP accesses served by the same AMF and the UE CM state in the AMF is CM-IDLE in 3GPP access and is in CM-CONNECTED in non 3GPP access, the UE can be notified through the non-3GPP for a PDU Session associated in the SMF (i.e. last routed) to the 3GPP access. The notification message shall include the 3GPP Access Type. Upon reception of the notification message, when 3GPP access is available, the UE shall reply to the 5GC via the 3GPP access using the NAS Service Request message. + +In addition to the above, a PDU Session may be established as an always-on PDU Session as described in clause 5.6.13. + +The deactivation of the UP connection of an existing PDU Session causes the corresponding data radio bearer and N3 tunnel to be deactivated. The UP connection of different PDU Sessions can be deactivated independently when a UE is in CM-CONNECTED state in 3GPP access or non-3GPP access. At the deactivation of the UP of a PDU Session using a N9 tunnel whose end-point is controlled by an I-SMF, the N9 tunnel is preserved. If a PDU Session is an always-on PDU Session, the SMF should not deactivate a UP connection of this PDU Session due to inactivity. + +### 5.6.9 Session and Service Continuity + +#### 5.6.9.1 General + +The support for session and service continuity in 5G System architecture enables to address the various continuity requirements of different applications/services for the UE. The 5G System supports different session and service continuity (SSC) modes defined in this clause. The SSC mode associated with a PDU Session does not change during the lifetime of a PDU Session. The following three modes are specified with further details provided in the next clause: + +- With SSC mode 1, the network preserves the connectivity service provided to the UE. For the case of PDU Session of IPv4 or IPv6 or IPv4v6 type, the IP address is preserved. +- With SSC mode 2, the network may release the connectivity service delivered to the UE and release the corresponding PDU Session(s). For the case of IPv4 or IPv6 or IPv4v6 type, the release of the PDU Session induces the release of IP address(es) that had been allocated to the UE. +- With SSC mode 3, changes to the user plane can be visible to the UE, while the network ensures that the UE suffers no loss of connectivity. A connection through new PDU Session Anchor point is established before the previous connection is terminated in order to allow for better service continuity. For the case of IPv4 or IPv6 or IPv4v6 type, the IP address is not preserved in this mode when the PDU Session Anchor changes. + +NOTE: In this Release of the specification, the addition/removal procedure of additional PDU Session Anchor in a PDU Session for local access to a DN is independent from the SSC mode of the PDU Session. + +#### 5.6.9.2 SSC mode + +##### 5.6.9.2.1 SSC Mode 1 + +For a PDU Session of SSC mode 1, the UPF acting as PDU Session Anchor at the establishment of the PDU Session is maintained regardless of the access technology (e.g. Access Type and cells) a UE is successively using to access the network. + +In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, IP continuity is supported regardless of UE mobility events. + +In this Release of the specification, when IPv6 multihoming or UL CL applies to a PDU Session of in SSC mode 1, and the network allocates (based on local policies) additional PDU Session Anchors to such a PDU Session, these additional PDU Session Anchors may be released or allocated, and the UE does not expect that the additional IPv6 prefix is maintained during the lifetime of PDU Session. + +SSC mode 1 may apply to any PDU Session type and to any access type. + +A UE supporting PDU Connectivity shall support SSC mode 1. + +##### 5.6.9.2.2 SSC Mode 2 + +If a PDU Session of SSC mode 2 has a single PDU Session Anchor, the network may trigger the release of the PDU Session and instruct the UE to establish a new PDU Session to the same data network immediately. The trigger condition depends on operator policy e.g. request from Application Function, based on load status, etc. At establishment of the new PDU Session, a new UPF acting as PDU Session Anchor can be selected. + +Otherwise, if a PDU Session of SSC mode 2 has multiple PDU Session Anchors (i.e. in the case of multi-homed PDU Sessions or in the case that UL CL applies to a PDU Session of SSC mode 2), the additional PDU Session Anchors may be released or allocated. + +SSC mode 2 may apply to any PDU Session type and to any access type. + +SSC mode 2 is optional to be supported in the UE. + +NOTE 1: Features depending on SSC mode 2 will not work with the lack of support for SSC mode 2 in the UE. + +NOTE 2: In UL CL mode, the UE is not involved in PDU Session Anchor re-allocation, so that the existence of multiple PDU Session Anchors is not visible to the UE. + +##### 5.6.9.2.3 SSC Mode 3 + +For PDU Session of SSC mode 3, the network allows the establishment of UE connectivity via a new PDU Session Anchor to the same data network before connectivity between the UE and the previous PDU Session Anchor is released. When trigger conditions apply, the network decides whether to select a PDU Session Anchor UPF suitable for the UE's new conditions (e.g. point of attachment to the network). + +In this Release of specification, SSC mode 3 only applies to IP PDU Session type and to any access type. + +In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, during the procedure of change of PDU Session Anchor, the following applies: + +- a. For a PDU Session of IPv6 type, the new IP prefix anchored on the new PDU Session Anchor may be allocated within the same PDU Session (relying on IPv6 multi-homing specified in clause 5.6.4.3), or +- b. The new IP address and/or IP prefix may be allocated within a new PDU Session that the UE is triggered to establish. + +After the new IP address/prefix has been allocated, the old IP address/prefix is maintained during some time indicated to the UE via NAS signalling (as described in clause 4.3.5.2 of TS 23.502 [3]) or via Router Advertisement (as described in clause 4.3.5.3 of TS 23.502 [3]) and then released. + +If a PDU Session of SSC mode 3 has multiple PDU Session Anchors (i.e. in the case of multi-homed PDU Sessions or in the case that UL CL applies to a PDU Session of SSC mode 3), the additional PDU Session Anchors may be released or allocated. + +SSC mode 3 is optional to be supported in the UE. + +NOTE: Features depending on SSC mode 3 will not work with the lack of support for SSC mode 3 in the UE. + +#### 5.6.9.3 SSC mode selection + +SSC mode selection is done by the SMF based on the allowed SSC modes (including the default SSC mode) in the user subscription as well as the PDU Session type and if present, the SSC mode requested by the UE. + +The operator may provision a SSC mode selection policy (SSCMSP) to the UE as part of the URSP rule (see clause 6.6.2 of TS 23.503 [45]). The UE shall use the SSCMSP to determine the type of session and service continuity mode associated with an application or group of applications for the UE as described in clause 6.6.2.3 of TS 23.503 [45]. If the UE does not have SSCMSP, the UE can select a SSC mode based on UE Local Configuration as described in TS 23.503 [45], if applicable. If the UE cannot select a SSC mode, the UE requests the PDU Session without providing the SSC mode. + +NOTE 1: The UE can use the SSC Mode Selection component of the URSP rule with match-all traffic descriptor if there is no SSC mode in the UE local configuration. + +The SSC mode selection policy rules provided to the UE can be updated by the operator by updating the URSP rule. + +The SMF receives from the UDM the list of allowed SSC modes and the default SSC mode per DNN per S-NSSAI as part of the subscription information. + +If a UE provides an SSC mode when requesting a new PDU Session, the SMF selects the SSC mode by either accepting the requested SSC mode or rejecting the PDU Session Establishment Request message with the cause value and the SSC mode(s) allowed to be used back to UE based on the PDU Session type, subscription and/or local configuration. Based on that cause value and the SSC mode(s) allowed to be used, the UE may re-attempt to request the establishment of that PDU Session with the SSC mode allowed to be used or using another URSP rule. + +If a UE does not provide an SSC mode when requesting a new PDU Session, then the SMF selects the default SSC mode for the data network listed in the subscription or applies local configuration to select the SSC mode. + +SSC mode 1 shall be assigned to the PDU Session when static IP address/prefix is allocated to the PDU Session based on the static IP address/prefix subscription for the DNN and S-NSSAI. The SMF shall inform the UE of the selected SSC mode for a PDU Session. + +The UE shall not request and the network shall not assign SSC mode 3 for the PDU Session of Unstructured type or Ethernet type. + +NOTE 2: To avoid issues for UEs not supporting all SSC modes, the operator can, in the subscription data and local configuration, include at least SSC mode 1 in the allowed SSC modes, and set default SSC mode to 1 (since all UEs supporting PDU sessions are mandated to support SSC mode 1). Still the 5GC can trigger PDU session release with a cause code indicating reactivation due to, e.g. restoration or user plane path optimization purposes, though this may cause interruption of the service. + +### 5.6.10 Specific aspects of different PDU Session types + +#### 5.6.10.1 Support of IP PDU Session type + +The IP address allocation is defined in clause 5.8.1 + +The UE may acquire following configuration information from the SMF, during the lifetime of a PDU Session: + +- Address(es) of P-CSCF(s); +- Address(es) of DNS server(s). +- If the UE indicates support of DNS with security as defined in TS 33.501 [29] to the network in PCO and the network wants to enforce the use of DNS with security, the configuration information sent by the SMF via PCO may also include the corresponding DNS server security information as specified in TS 24.501 [47] and TS 33.501 [29]. +- the GPSI of the UE. + +The UE may acquire from the SMF, at PDU Session Establishment, the MTU that the UE shall consider, see clause 5.6.10.4. + +The UE may provide following information to the SMF during the lifetime of a PDU Session: + +- an indication of the support of P-CSCF re-selection based on procedures specified in TS 24.229 [62] (clauses B.2.2.1C and L.2.2.1C). +- PS data off status of the UE. + +NOTE 2: An operator can deploy NAT functionality in the network; the support of NAT is not specified in this release of the specification, though UPF can expose mapping between public and private IP addresses. + +#### 5.6.10.2 Support of Ethernet PDU Session type + +For a PDU Session set up with the Ethernet PDU Session type, the SMF and the UPF acting as PDU Session Anchor (PSA) can support specific behaviours related with the fact the PDU Session carries Ethernet frames. + +Depending on operator configuration related with the DNN, different configurations for how Ethernet traffic is handled on N6 may apply, for example: + +- Configurations with a 1-1 relationship between a PDU Session and a N6 interface possibly corresponding to a dedicated tunnel established over N6. In this case the UPF acting as PSA transparently forwards Ethernet frames between the PDU Session and its corresponding N6 interface, and it does not need to be aware of MAC addresses used by the UE in order to route down-link traffic. +- Configurations, where more than one PDU Session to the same DNN (e.g. for more than one UE) corresponds to the same N6 interface. In this case the UPF acting as PSA needs to be aware of MAC addresses used by the UE in the PDU Session in order to map down-link Ethernet frames received over N6 to the appropriate PDU Session. Forwarding behaviour of the UPF acting as PSA is managed by SMF as specified in clause 5.8.2.5. + +NOTE 1: The "MAC addresses used by the UE" correspond to any MAC address used by the UE or any device locally connected to the UE and using the PDU Session to communicate with the DN. + +Based on operator configuration, the SMF may request the UPF acting as the PDU Session Anchor to respond to ARP/IPv6 Neighbour Solicitation requests based on local cache information, i.e. the mapping between the UE MAC address to the UE IP address, and the DN where the PDU Session is connected to, or to redirect the ARP traffic from the UPF to the SMF. Responding to ARP/IPv6 ND based on local cache information applies to ARP/IPv6 ND received in both UL and DL directions. + +NOTE 2: Responding to ARP/ND from a local cache assumes the UE or the devices behind the UE acquire their IP address via in-band mechanisms that the SMF/UPF can detect and by this link the IP address to the MAC address. + +NOTE 3: This mechanism is intended to avoid broadcasting or multicasting the ARP/IPv6 ND to every UE. + +Ethernet Preamble and Start of Frame delimiter are not sent over 5GS: + +- For UL traffic the UE strips the preamble and frame check sequence (FCS) from the Ethernet frame. +- For DL traffic the PDU Session Anchor strips the preamble and frame check sequence (FCS) from the Ethernet frame. + +Neither a MAC nor an IP address is allocated by the 5GC to the UE for a PDU Session. + +The PSA shall store the MAC addresses received from the UE, and associate those with the appropriate PDU Session. + +The SMF may receive a list of allowed VLAN tags from DN-AAA (for a maximum of 16 VLAN tags) or may be locally configured with allowed VLAN tags values. The SMF may also be configured with instructions on VLAN handling (e.g. the VLAN tag to be inserted or removed, S-TAG to be inserted or removed). Taking this into account, the SMF determines the VLAN handling for the PDU Session, and instructs the UPF to accept or discard the UE traffic based on the allowed VLAN tags, as well as to handle VLAN tags (addition/removal) via PDR (Outer header removal) and FAR (UPF applying Outer header creation of a Forwarding policy). For example: + +- The UPF may insert (for uplink traffic) and remove (for downlink traffic) a S-TAG on N6 or N19 or internal interface ("5G VN internal") for the traffic from and to the UE. +- The UPF may insert (for uplink traffic) and remove (for downlink traffic) a VLAN tag on the N6 interface while there is no VLAN in the traffic to and from the UE. +- The UPF may discard any UE traffic that does not contain any allowed VLAN tag when the UPF handles the UE uplink or downlink traffic. + +NOTE 4: This can be used for traffic steering to N6-LAN but also for N6-based traffic forwarding related with 5G-VN service described in clause 5.29.4 + +Apart from specific conditions related to the support of PDU sessions over W-5GAN defined in TS 23.316 [84], the UPF shall not remove VLAN tags sent by the UE and the UPF shall not insert VLAN tags for the traffic sent to the UE. + +PDU(s) containing a VLAN tag shall be switched only within the same VLAN by a PDU Session Anchor. + +The UE may acquire from the SMF, at PDU Session Establishment, the MTU of the Ethernet frames' payload that the UE shall consider, see clause 5.6.10.4. + +NOTE 5: The UE may operate in bridge mode with regard to a LAN it is connecting to the 5GS, thus different MAC addresses may be used as source address of different frames sent UL over a single PDU Session (and destination MAC address of different frames sent DL over the same PDU Session). + +NOTE 6: Entities on the LAN connected to the 5GS by the UE may have an IP address allocated by the DN but the IP layer is considered as an application layer which is not part of the Ethernet PDU Session. + +NOTE 7: In this Release of the specification, only the UE connected to the 5GS is authenticated, not the devices behind such UE. + +NOTE 8: 5GS does not support the scenario where a MAC address or if VLAN applies a (MAC address, VLAN) combination is used on more than one PDU Session for the same DNN and S-NSSAI. + +NOTE 9: This Release of the specification does not guarantee that the Ethernet network remains loop-free. Deployments need to be verified on an individual basis that loops in the Ethernet network are avoided. + +NOTE 10: This Release of the specification does not guarantee that the Ethernet network properly and quickly reacts to topology changes. Deployments need to be verified on an individual basis how they react to topology changes. + +Different Frames exchanged on a PDU Session of Ethernet type may be served with different QoS over the 5GS. Thus, the SMF may provide to the UPF Ethernet Packet Filter Set and forwarding rule(s) based on the Ethernet frame + +structure and UE MAC address(es). The UPF detects and forwards Ethernet frames based on the Ethernet Packet Filter Set and forwarding rule(s) received from the SMF. This is further defined in clauses 5.7 and 5.8.2. + +When a PDU Session of Ethernet PDU type is authorized by a DN as described in clause 5.6.6, the DN-AAA server may, as part of authorization data, provide the SMF with a list of allowed MAC addresses for this PDU Session; the list is limited to a maximum of 16 MAC addresses. When the list has been provided for a PDU Session, the SMF sets corresponding filtering rules in the UPF(s) acting as PDU Session Anchor for the PDU Session. The UPF discards any UL traffic that does not contain one of these MAC addresses as a source address if the list of allowed MAC addresses is provided. + +In this Release of specification, the PDU Session of Ethernet PDU Session type is restricted to SSC mode 1 and SSC mode 2. + +For a PDU Session established with the Ethernet PDU Session type, the SMF may, upon PCF request, need to ensure reporting to the PCF of all Ethernet MAC addresses used as UE address in a PDU Session. In this case, as defined in clause 5.8.2.12, the SMF controls the UPF to report the different MAC addresses used as source address of frames sent UL by the UE in the PDU Session. + +NOTE 11: This relates to whether AF control on a per MAC address is allowed on the PDU Session as defined in clause 6.1.1.2 of TS 23.503 [45]. + +The PCF may activate or deactivate the reporting of the UE MAC address using the "UE MAC address change" Policy Control Request Trigger as defined in Table 6.1.3.5-1 of TS 23.503 [45]. + +The SMF may relocate the UPF acting as the PDU Session Anchor for an Ethernet PDU Session as defined in clause 4.3.5.8 of TS 23.502 [3]. The relocation may be triggered by a mobility event such as a handover, or may be triggered independent of UE mobility, e.g. due to load balancing reasons. In order to relocate the PSA UPF, the reporting of the UE MAC addresses needs to be activated by the SMF. + +#### 5.6.10.3 Support of Unstructured PDU Session type + +Different Point-to-Point (PtP) tunnelling techniques may be used to deliver Unstructured PDU Session type data to the destination (e.g. application server) in the Data Network via N6. + +Point-to-point tunnelling based on UDP/IP encapsulation as described below may be used. Other techniques may be supported. Regardless of addressing scheme used from the UPF to the DN, the UPF shall be able to map the address used between the UPF and the DN to the PDU Session. + +When Point-to-Point tunnelling based on UDP/IPv6 is used, the following considerations apply: + +- IPv6 prefix allocation for PDU Sessions are performed locally by the (H-)SMF without involving the UE. +- The UPF(s) acts as a transparent forwarding node for the payload between the UE and the destination in the DN. +- For uplink, the UPF forwards the received Unstructured PDU Session type data to the destination in the data network over the N6 PtP tunnel using UDP/IPv6 encapsulation. +- For downlink, the destination in the data network sends the Unstructured PDU Session type data using UDP/IPv6 encapsulation with the IPv6 address of the PDU Session and the 3GPP defined UDP port for Unstructured PDU Session type data. The UPF acting as PDU Session Anchor decapsulates the received data (i.e. removes the UDP/IPv6 headers) and forwards the data identified by the IPv6 prefix of the PDU Session for delivery to the UE. +- The (H-)SMF performs the IPv6 related operations but the IPv6 prefix is not provided to the UE, i.e. Router Advertisements and DHCPv6 are not performed. The SMF assigns an IPv6 Interface Identifier for the PDU Session. The allocated IPv6 prefix identifies the PDU Session of the UE. +- For AF influence on traffic routing (described in clause 5.6.7), when the N6 PtP tunnelling is used over the DNAI and the AF provides, by value, information about N6 traffic routing requirements in the AF request, the AF provides N6 PtP tunnelling requirements (IPv6 address and UDP port of the tunnel end in the DN) as the N6 traffic routing information associated to the DNAI; when the SMF notifies the AF of UP path management events, it includes the N6 PtP tunnel information related to the UP (the IPv6 address and the 3GPP defined UDP port of the tunnel end at the UPF) as N6 traffic routing information in the notification. + +In this Release of the specification there is support for maximum one 5G QoS Flow per PDU Session of Type Unstructured. + +In this Release of specification, the PDU Session of Unstructured PDU Session type is restricted to SSC mode 1 and SSC mode 2. + +The UE may acquire from the SMF, at PDU Session Establishment, the MTU that the UE shall consider, see clause 5.6.10.4. + +#### 5.6.10.4 Maximum Transfer Unit size considerations + +In order to avoid data packet fragmentation between the UE and the UPF acting as PSA, the link MTU size in the UE should be set to the value provided by the network as part of the IP configuration. The link MTU size for IPv4 is sent to the UE by including it in the PCO (see TS 24.501 [47]). The link MTU size for IPv6 is sent to the UE by including it in the IPv6 Router Advertisement message (see RFC 4861 [54]). + +NOTE 1: Ideally the network configuration ensures that for PDU Session type IPv4v6 the link MTU values provided to the UE via PCO and in the IPv6 Router Advertisement message are the same. In cases where this condition cannot be met, the MTU size selected by the UE is unspecified. + +When using a PDU Session type Unstructured, the maximum uplink packet size, and when using Ethernet, the Ethernet frames' payload, that the UE should use may be provided by the network as a part of the session management configuration by encoding it within the PCO (see TS 24.501 [47]). + +When using a PDU Session type Unstructured, to provide a consistent environment for application developers, the network shall use a maximum packet size of at least 128 octets (this applies to both uplink and downlink). + +When the MT and the TE are separated, the TE may either be pre-configured to use a specific default MTU size or the TE may use an MTU size provided by the network via the MT. Thus, it is not always possible to set the MTU value by means of information provided by the network. + +NOTE 2: In network deployments that have MTU size of 1500 octets in the transport network, providing a link MTU value of 1358 octets (as shown in Figure J-1) to the UE as part of the IP configuration information from the network will prevent the IP layer fragmentation within the transport network between the UE and the UPF. For network deployments that uniformly support transport with larger MTU size than 1500 octets (for example with ethernet jumbo frames of MTU size up to 9216 octets), providing a link MTU value of MTU minus 142 octets to the UE as part of the IP configuration information from the network will prevent the IP layer fragmentation within the transport network between the UE and the UPF. Link MTU considerations are discussed further in Annex J. + +NOTE 3: As the link MTU value is provided as a part of the session management configuration information, a link MTU value can be provided during each PDU Session establishment. In this release, dynamic adjustment of link MTU for scenarios where MTU is not uniform across transport are not addressed. + +### 5.6.11 UE presence in Area of Interest reporting usage by SMF + +When a PDU Session is established or modified, or when the user plane path has been changed (e.g. UPF re-allocation/addition/removal), SMF may determine an Area of Interest, e.g. based on UPF Service Area, subscription by PCF for reporting UE presence in Presence Reporting Area, etc. + +For 3GPP access, the Area of Interest corresponds: + +- either to Presence Information that may correspond to: + - a list of Tracking Areas; or + - a list of Presence Reporting Area ID(s) and optionally the elements comprising TAs and/or NG-RAN nodes and/or cells identifiers corresponding to the PRA ID(s); or + - a LADN DNN; or + - a LADN DNN and a S-NSSAI; or + - a S-NSSAI. + +For Non-3GPP access, the Area of Interest corresponds to: + +- N3GPP TAI (see clause 5.3.2.3). + +For UE location change into or out of an "area of interest", the SMF subscribes to "UE mobility event notification" service provided by AMF for reporting of UE presence in Area of Interest as described in clause 5.3.4.4. The AMF may send the UE location to the SMF along with the notification, e.g. for UPF selection. Upon reception of a notification from AMF, the SMF determines how to deal with the PDU Session, e.g. reallocate UPF. + +In the case of LADN, the SMF provides the LADN DNN to the AMF to subscribe to "UE mobility event notification" for reporting UE presence in LADN service area. Upon reception of a notification from the AMF, the SMF determines how to deal with the PDU Session as described in clause 5.6.5. + +In the case of Partial Network Slice Support and Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas as described in clauses 5.15.17 and 5.15.18, the SMF provides the S-NSSAI to the AMF to "UE mobility event notification" for reporting UE presence in slice restriction area. Upon reception of a notification from the AMF, the SMF determines how to deal with the PDU Session as described in clauses 5.15.17 and 5.15.18. + +For use cases related to policy control and charging decisions, the PCF may subscribe to event reporting from the SMF or the AMF, for UE presence in a Presence Reporting Area. + +A Presence Reporting Area can be: + +- A "UE-dedicated Presence Reporting Area", defined in the subscriber profile and composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN; or derived from the Area of Interest provided by the Application Function to the PCF (see clause 5.6.7) and composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN; or +- A "Core Network predefined Presence Reporting Area", predefined in the AMF and composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN. + +In the case of Change of UE Presence in Presence Reporting Area, for core network predefined Presence Reporting Area, the AMF determines the "area of interest" corresponding to the Presence Reporting Area Identifier(s), provided by the PCF or the SMF, as a list of TAIIs and/or cell identifiers and/or NG-RAN node identifiers based on local configuration. For UE-dedicated Presence Reporting Areas, the subscription for UE location change notification for an "area of interest" shall contain the PRA Identifier(s) and the list(s) of TAs, or NG-RAN Node identifier and/or cell identifiers composing the Presence Reporting Area(s). For Core Network predefined Presence Reporting Areas, the subscription for UE location change notification for an "area of interest" shall contain the PRA identifier(s). + +NOTE 1: If the Presence Reporting Area (PRA) and RAN Notification Area (RNA) are partially overlapping, the PCF will not get notified for the change of PRA when UE enters or leaves the PRA but remains in the RNA in CM-CONNECTED with RRC\_INACTIVE state, because AMF is not informed. + +Each Core Network predefined Presence Reporting Area can be configured with a priority level in the AMF. In order to prevent overload, the AMF may set the reporting for one or more of the received Presence Reporting Area(s) to inactive under consideration of the priority configured for each of Core Network predefined Presence Reporting Area(s), while storing the reporting request for this Presence Reporting Area in the UE context. + +NOTE 2: Change of UE presence in Presence Reporting Area reporting does not apply to home routed roaming. + +The AMF may be configured with a PRA identifier which refers to a Set of Core Network predefined Presence Reporting Areas. If the PCF subscribes to change of UE location for an area of interest for a Set of Presence reporting areas and provides a PRA identifier then the SMF may subscribe for event reporting for this Set of Presence Reporting Areas by only indicating this PRA Identifier in the area of interest. When the Presence Reporting Area(s) to be reported belong to a set of Core Network predefined Presence Reporting Areas in which the AMF is requested to report on change of UE presence, the AMF shall additionally add to the report the PRA Identifier of the Set of Core Network predefined Presence Reporting Areas. + +Upon change of AMF, the PRA identifier(s) and if provided, the list(s) of Presence Reporting Area elements are transferred for all PDU sessions as part of MM Context information to the target AMF during the mobility procedure. If one or more Presence Reporting Area(s) was set to inactive, the target AMF may decide to reactivate one or more of the inactive Presence Reporting Area(s). The target AMF indicates per PDU session to the corresponding SMF/PCF the PRA identifier(s) and whether the UE is inside or outside the Presence Reporting Area(s) as well as the inactive Presence Reporting Area(s), if any. + +NOTE 3: The target AMF cannot set the Presence Reporting Area(s) received from the source serving node to inactive. + +The subscription may be maintained during the life of PDU Session, regardless of the UP activation state of PDU Session (i.e. whether UP connection of the PDU Session is activated or not). + +SMF may determine a new area of interest, and send a new subscription to the AMF with the new area of interest. + +SMF un-subscribes to "UE mobility event notification" service when PDU Session is released. + +### 5.6.12 Use of Network Instance + +The SMF may provide a Network Instance to the UPF in FAR and/or PDR via N4 Session Establishment or N4 Modification procedures. + +NOTE 1: a Network Instance can be defined e.g. to separate IP domains, e.g. when a UPF is connected to 5G-ANs in different IP domains, overlapping UE IP addresses assigned by multiple Data Networks, transport network isolation in the same PLMN, etc. + +NOTE 2: As the SMF can provide over N2 the Network Instance it has selected for the N3 CN Tunnel Info, the 5G AN does not need to provide Network Instance to the 5GC. + +The SMF determines the Network Instance based on local configuration. + +The SMF may determine the Network Instance for N3 and N9 interfaces, taking into account e.g. UE location, registered PLMN ID of UE, S-NSSAI of the PDU Session. + +The SMF may determine the Network Instance for N6 interface taking into account e.g. (DNN, S-NSSAI) of the PDU Session. + +The SMF may determine the Network Instance for N19 interface taking into account e.g. the (DNN, S-NSSAI) identifying a 5G VN group. + +NOTE 3: As an example, the UPF can use the Network Instance included in the FAR, together with other information such as Outer header creation (IP address part) and Destination interface in the FAR, to determine the interface in UPF (e.g. VPN or Layer 2 technology) for forwarding of the traffic. + +### 5.6.13 Always-on PDU session + +An always-on PDU Session is a PDU Session for which User Plane resources have to be activated during every transition from CM-IDLE mode to CM-CONNECTED state. + +Based on an indication from upper layers, a UE may request to establish a PDU Session as an always-on PDU Session. The SMF decides whether the PDU Session can be established as an always-on PDU Session. In Home Routed roaming case, based on local policies, the V-SMF shall be involved to determine whether the PDU Session can be established as an always-on PDU Session. + +If the UE requests the 5GC to modify a PDU Session, which was established in EPS, to an always-on PDU Session after the first inter-system change from EPS to 5GS, the SMF decides whether the PDU Session can be established as an always-on PDU Session based on the procedure described above. + +The UE shall request activation of User Plane resources for always-on PDU Sessions even if there are no pending uplink data for this PDU Session or when the Service Request is triggered for signalling only or when the Service Request is triggered for paging response only. + +If the UE has one or more established PDU Sessions which are not accepted by the network as always-on PDU Sessions and the UE has no uplink user data pending to be sent for those PDU Sessions, the UE shall not request for activating User Plane resources for those PDU sessions. + +### 5.6.14 Support of Framed Routing + +Framed Routing is only defined for PDU Sessions of the IP type (IPv4, IPv6, IPv4v6) and allows to support an IP network behind a UE, such that a range of IPv4 addresses or IPv6 prefixes is reachable over a single PDU Session, e.g. for enterprise connectivity. Framed Routes are IP routes behind the UE. + +A PDU Session may be associated with multiple Framed Routes. Each Framed Route refers to a range of IPv4 addresses (i.e. an IPv4 address and an IPv4 address mask) or a range of IPv6 Prefixes (i.e. an IPv6 Prefix and an IPv6 Prefix length). The set of one or more Framed Routes associated to a PDU Session is contained in the Framed Route information. The network does not send Framed Route information to the UE: devices in the network(s) behind the UE get their IP address by mechanisms out of the scope of 3GPP specifications. See RFC 2865 [73], RFC 3162 [74]. + +Framed Route information is provided by the SMF to the UPF (acting as PSA) as part of Packet Detection Rule (PDR, see clause 5.8.5.3) related with the network side (N6) of the UPF. + +**NOTE:** SMF can take the UPF capabilities into account when selecting PSA UPF, to ensure that the SMF chooses PSA UPF(s) that support Framed Routing for PDU Sessions to DNN and/or slices deemed to support Framed Routing e.g. DNN and/or slices intended to support RG or if Framed Route information has been received as part of Session Management Subscription data. + +The Framed Route information may be provided to the SMF by: + +- the DN-AAA server as part of PDU Session Establishment authentication/authorization by a DN-AAA server (as defined in clause 5.6.6); or by +- Session Management Subscription data associated with DNN and S-NSSAI sent by UDM (as defined in clause 5.2.3.3.1 of TS 23.502 [3]). + +If the SMF receives Framed Route information both from DN-AAA and from UDM, the information received from DN-AAA takes precedence and supersedes the information received from UDM. + +The IPv4 address / IPv6 Prefix allocated to the UE as part of the PDU Session establishment (e.g. delivered in NAS PDU Session Establishment Accept) may belong to one of the Framed Routes associated with the PDU Session or may be dynamically allocated outside of such Framed Routes. + +If PCC applies to the PDU Session, at PDU Session establishment the SMF reports to the PCF the Framed Route information corresponding to the PDU Session (as described in clause 6.1.3.5 of TS 23.503 [45]). In this case, in order to support session binding, the PCF may further report to the BSF the Framed Route information corresponding to the PDU Session (as described in clause 6.1.2.2 of TS 23.503 [45]). + +If the UDM or DN-AAA updates the Framed Route information during the lifetime of the PDU Session, the SMF releases the PDU Session and may include in the release request an indication for the UE to re-establish the PDU Session. + +### 5.6.15 Triggers for network analytics + +Triggers for the SMF to request for or subscribe to the analytics information from the NWDAF are internal logic may include for example: + +- UE PDU Session related event subscription by other NFs (e.g. AMF, NEF); +- UE access and mobility event reports from the AMF; +- locally detected events; +- analytics information received. + +The trigger conditions may depend on operator and implementation policy in the SMF. When a trigger condition happens, the SMF may decide if any analytics information is needed and if so, request for or subscription to the analytics information from the NWDAF. + +The SMF may, upon detection of certain local events, e.g. number of PDU sessions establishment or released reaches a threshold in a specific area, request for or subscribe to network analytics related to "Abnormal behaviour" as described in TS 23.288 [86] to detect whether there are any exceptional UE behaviours in this area. + +### 5.6.16 Support for Service Function Chaining + +#### 5.6.16.1 General + +Service Function Chaining, also called N6-LAN Traffic Steering, refers to the steering of subscriber's traffic flows to appropriate operator or 3rd party Service Functions (e.g. NAT, antimalware, parental control, DDoS protection) in the N6-LAN. + +The content of this clause applies to non-roaming and to Home Routed roaming scenario, i.e. to cases where the involved entities (AF, PCF, SMF, UPF) belong to the Home PLMN and the AF has an agreement with the Home PLMN. + +The PCF controls Service Function Chaining by provisioning and modifying traffic steering control information for N6-LAN Traffic Steering as described in TS 23.503 [45], e.g. clause 6.1.3.14. The traffic steering control information for N6-LAN Traffic Steering consists of a traffic description and a reference to a traffic steering policy that is configured in the SMF/UPF. + +The PCF derives the TSP ID(s) (that can be different for uplink and downlink directions) based on operator configuration and sends the TSP ID(s) to the SMF as part of the N6-LAN Traffic Steering Enforcement Control information in the PCC rule as described in clause 6.3.1 of TS 23.503 [45]. + +When the PCC rule is activated or updated with N6-LAN Traffic Steering Enforcement Control information, the SMF sets the Forwarding Policy (uplink and/or downlink) within the FAR(s) based on the authorized TSP ID(s) in the PCC rule and under consideration of the direction. In case that Application Function influence on traffic routing Enforcement Control information and N6-LAN Traffic Steering Enforcement Control information are both provided for the uplink direction, the SMF shall derive N4 rules which instruct the UPF to pass the traffic through the relevant Service Function(s) deployed in the N6-LAN before steering the traffic to the local data network. The SMF provides instructions to UPF for N6-LAN traffic steering as further detailed in clause 5.8.5.6. + +The UPF applies traffic steering mechanism based on Forwarding Policy, i.e. the UPF performs deployment specific actions as configured for the Forwarding Policy. + +NOTE 1: It is assumed that all UPFs in the operator network serving as PSA for the DNN/S-NSSAI/DNAI subject to N6-LAN traffic steering need to be configured with the same traffic steering information for N6-LAN traffic steering. + +When performing deployment specific actions configured for the Forwarding Policy, the UPF may support traffic steering related functionality and user plane encapsulation protocols that are out of 3GPP scope (e.g. as defined by other standards organizations). + +NOTE 2: The existing user plane mechanisms (e.g. VXLAN, NSH, GENEVE, GRE, VLAN, etc.) defined at IETF are reused as applicable by the PSA UPF to support N6-LAN traffic steering. + +The mechanism used for forwarding the traffic between the Service Functions within the N6-LAN is out of 3GPP scope. + +#### 5.6.16.2 Application Function influence on Service Function Chaining + +An AF may request the steering of user plane traffic to a pre-configured chain of Service Functions on N6-LAN. + +In the non-roaming scenario, Application Function influence on Service Function Chaining and Application Function influence on traffic routing (as defined in clause 5.6.7) can be applicable to the same traffic simultaneously. + +It is assumed that a service level agreement exists between the operator and a third party that includes a list of authorized predefined Service Function Chains (SFCs), each SFC being identified based on a Service Function Chaining identifier (SFC ID). The AF may request the selected traffic flows to be steered towards a specific SFC, either at PDU Session establishment or any time after PDU Session establishment. + +The AF requests may be sent to the PCF via the NEF. When SFC ID is included in the AF request, the parameters listed in Table 5.6.16.2-1 may be included in the AF request. + +**Table 5.6.16.2-1: Information element contained in AF request** + +| Information Name | Applicable for PCF or NEF
(NOTE 1) | Applicable for NEF only | Category | +|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------| +| Traffic Description | Defines the target traffic to be influenced, represented by the combination of DNN and optionally S-NSSAI, and application identifier or traffic filtering information. | The target traffic can be represented by AF-Service-Identifier, instead of combination of DNN and optionally S-NSSAI. | Mandatory | +| Target UE Identifier(s) | Indicates the UE(s) that the request is targeting, i.e. an individual UE, a group of UE represented by Internal Group Identifier (NOTE 2), or any UE accessing the combination of DNN and S-NSSAI. | GPSI can be applied to identify the individual UE, or External Group Identifier can be applied to identify a group of UE. | Mandatory | +| Spatial Validity Condition | Indicates that the request applies only to the traffic of UE(s) located in the specified location, represented by areas of validity. | The specified location can be represented by geographical area. | Optional | +| AF transaction identifier | The AF transaction identifier refers to the AF request. | N/A | Mandatory | +| SFC identifier(s) | Indicates the pre-defined Service Function Chain in downlink and/or uplink. | N/A | Mandatory | +| Metadata | Contains information that is transparently passed to UPF (NOTE 3) and provided by UPF to the Service Functions in N6-LAN. | N/A | Optional | + +NOTE 1: When the AF request targets existing or future PDU Sessions of multiple UE(s) or of any UE and is sent via the NEF, as described in clause 6.3.7.2, the information is stored in the UDR by the NEF and notified to the PCF by the UDR. + +NOTE 2: Internal Group ID can only be used by an AF controlled by the operator and only towards PCF. + +NOTE 3: The NEF, PCF and SMF do not need to understand the Metadata. + +The PCF checks whether the SFC ID received from the AF corresponds to an authorized predefined SFC according to the service level agreement with this AF. Based on the SFC ID received from the AF, the PCF derives the TSP ID(s) (that can be different for uplink and downlink directions) and sends the TSP ID(s) and optionally Metadata (as provided by the AF) to the SMF as part of the PCC rule(s) as described in clause 6.3.1 of TS 23.503 [45]. + +The SMF behaves in the same way it is described in clause 5.6.16.1. If the SMF has received Metadata in the N6-LAN Traffic Steering Enforcement Control information of the PCC rule, the SMF forwards the Metadata to the UPF via N4 in the corresponding FAR as described in clause 5.8.5.6. + +## 5.7 QoS model + +### 5.7.1 General Overview + +#### 5.7.1.1 QoS Flow + +The 5G QoS model is based on QoS Flows. The 5G QoS model supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (Non-GBR QoS Flows). The 5G QoS model also supports Reflective QoS (see clause 5.7.5). + +The QoS Flow is the finest granularity of QoS differentiation in the PDU Session. A QoS Flow ID (QFI) is used to identify a QoS Flow in the 5G System. User Plane traffic with the same QFI within a PDU Session receives the same traffic forwarding treatment (e.g. scheduling, admission threshold). The QFI is carried in an encapsulation header on N3 (and N9) i.e. without any changes to the e2e packet header. QFI shall be used for all PDU Session Types. The QFI shall be unique within a PDU Session. The QFI may be dynamically assigned or may be equal to the 5QI (see clause 5.7.2.1). + +Within the 5GS, a QoS Flow is controlled by the SMF and may be preconfigured, or established via the PDU Session Establishment procedure (see clause 4.3.2 of TS 23.502 [3]), or the PDU Session Modification procedure (see clause 4.3.3 of TS 23.502 [3]). + +Any QoS Flow is characterised by: + +- A QoS profile provided by the SMF to the AN via the AMF over the N2 reference point or preconfigured in the AN; +- One or more QoS rule(s) and optionally QoS Flow level QoS parameters (as specified in TS 24.501 [47]) associated with these QoS rule(s) which can be provided by the SMF to the UE via the AMF over the N1 reference point and/or derived by the UE by applying Reflective QoS control; and +- One or more UL and DL PDR(s) provided by the SMF to the UPF. + +Within the 5GS, a QoS Flow associated with the default QoS rule is required to be established for a PDU Session and remains established throughout the lifetime of the PDU Session. This QoS Flow should be a Non-GBR QoS Flow (further details are described in clause 5.7.2.7). + +A QoS Flow is associated with QoS requirements as specified by QoS parameters and QoS characteristics. + +NOTE: The QoS Flow associated with the default QoS rule provides the UE with connectivity throughout the lifetime of the PDU Session. Possible interworking with EPS motivates the recommendation for this QoS Flow to be of type Non-GBR. + +A QoS Flow may be enabled with PDU Set based QoS handling as described in clause 5.37.5. For such QoS Flows, PDU Set QoS Parameters (see clause 5.7.7) are determined by the PCF and provided by SMF to the NG-RAN as part of the QoS profile. + +#### 5.7.1.2 QoS Profile + +A QoS Flow may either be 'GBR' or 'Non-GBR' depending on its QoS profile. The QoS profile of a QoS Flow is sent to the (R)AN and it contains QoS parameters as described below (details of QoS parameters are described in clause 5.7.2): + +- For each QoS Flow, the QoS profile shall include the QoS parameters: + - 5G QoS Identifier (5QI); and + - Allocation and Retention Priority (ARP). +- For each QoS Flow, the QoS profile may also include the QoS parameters: + - PDU Set QoS Parameters (described in clause 5.7.7). +- For each Non-GBR QoS Flow only, the QoS profile may also include the QoS parameter: + - Reflective QoS Attribute (RQA). +- For each GBR QoS Flow only, the QoS profile shall also include the QoS parameters: + - Guaranteed Flow Bit Rate (GFBR) - UL and DL; and + - Maximum Flow Bit Rate (MFBR) - UL and DL; and +- In the case of a GBR QoS Flow only, the QoS profile may also include one or more of the QoS parameters: + - Notification control; + - Maximum Packet Loss Rate - UL and DL. + +NOTE: In this Release of the specification, the Maximum Packet Loss Rate (UL, DL) is only provided for a GBR QoS Flow belonging to voice media. + +Each QoS profile has one corresponding QoS Flow identifier (QFI) which is not included in the QoS profile itself. + +The usage of a dynamically assigned 5QI for a QoS Flow requires in addition the signalling of the complete 5G QoS characteristics (described in clause 5.7.3) as part of the QoS profile. + +When a standardized or pre-configured 5QI is used for a QoS Flow, some of the 5G QoS characteristics may be signalled as part of the QoS profile (as described in clause 5.7.3). + +##### 5.7.1.2a Alternative QoS Profile + +The Alternative QoS Profile(s) can be optionally provided for a GBR QoS Flow with Notification control enabled. If the corresponding PCC rule contains the related information (as described in TS 23.503 [45]), the SMF shall provide, in addition to the QoS profile, a prioritized list of Alternative QoS Profile(s) to the NG-RAN. If the SMF provides a new prioritized list of Alternative QoS Profile(s) to the NG-RAN (if the corresponding PCC rule information changes), the NG-RAN shall replace any previously stored list with it. + +An Alternative QoS Profile represents a combination of QoS parameters PDB, PER, Averaging Window and GFBR to which the application traffic is able to adapt. For delay-critical GBR QoS flows, an Alternative QoS Profile may also include an MDBV. + +NOTE 1: There is no requirement that the GFBR monotonically decreases, nor that the PDB or PER monotonically increase as the Alternative QoS Profiles become less preferred. + +When the NG-RAN sends a notification to the SMF that the QoS profile is not fulfilled, the NG-RAN shall, if the currently fulfilled values match an Alternative QoS Profile, include also the reference to the Alternative QoS Profile to indicate the QoS that the NG-RAN currently fulfils (see clause 5.7.2.4). The NG-RAN shall enable the SMF to determine when an NG-RAN node supports the Alternative QoS feature but cannot fulfil even the least preferred Alternative QoS Profile. + +NOTE 2: To reduce the risk that GBR QoS Flows are released in case of RAN resource limitations (and then experience difficulties in being re-established), Application Functions can set the least preferred Alternative Service Requirement to an undemanding level. + +#### 5.7.1.3 Control of QoS Flows + +The following options are supported to control QoS Flows: + +- 1) For Non-GBR QoS Flows, and when standardized 5QIs or pre-configured 5QIs are used and when the 5QI is within the range of the QFI (i.e. a value less than 64), the 5QI value may be used as the QFI of the QoS Flow. + - (a) A default ARP shall be pre-configured in the AN; or + - (b) The ARP and the QFI shall be sent to RAN over N2 at PDU Session Establishment or at PDU Session Modification and when NG-RAN is used every time the User Plane of the PDU Session is activated; and +- 2) For all other cases (including GBR and Non-GBR QoS Flows), a dynamically assigned QFI shall be used. The 5QI value may be a standardized, pre-configured or dynamically assigned. The QoS profile and the QFI of a QoS Flow shall be provided to the (R)AN over N2 at PDU Session Establishment/Modification and when NG-RAN is used every time the User Plane of the PDU Session is activated. + +Only options 1b and 2 may apply to 3GPP ANs. Options 1a, 1b and 2 may apply to Non-3GPP access. + +NOTE: Pre-configured 5QI values cannot be used when the UE is roaming. + +#### 5.7.1.4 QoS Rules + +The UE performs the classification and marking of UL User plane traffic, i.e. the association of UL traffic to QoS Flows, based on QoS rules. These QoS rules may be explicitly provided to the UE (i.e. explicitly signalled QoS rules using the PDU Session Establishment/Modification procedure), pre-configured in the UE or implicitly derived by the UE by applying Reflective QoS (see clause 5.7.5). A QoS rule contains the QFI of the associated QoS Flow, a Packet Filter Set (see clause 5.7.6) and a precedence value (see clause 5.7.1.9). An explicitly signalled QoS rule contains a QoS rule identifier which is unique within the PDU Session and is generated by SMF. + +There can be more than one QoS rule associated with the same QoS Flow (i.e. with the same QFI). + +When the UE informs the network about the number of supported Packet Filters for signalled QoS rules for the PDU Session (during the PDU Session Establishment procedure or using the PDU Session Modification procedure as described in clause 5.17.2.2.2 after the first inter-system change from EPS to 5GS for a PDU Session established in EPS + +and transferred from EPS with N26 interface), the SMF shall ensure that the sum of the Packet Filters used by all signalled QoS rules for a PDU Session does not exceed the number indicated by the UE. + +A default QoS rule is required to be sent to the UE for every PDU Session establishment and it is associated with a QoS Flow. For IP type PDU Session or Ethernet type PDU Session, the default QoS rule is the only QoS rule of a PDU Session which may contain a Packet Filter Set that allows all UL packets, and in this case, the highest precedence value shall be used for the QoS rule. + +NOTE 2: How the UE evaluates UL packets against the Packet Filter Set in a QoS rule is described in clause 5.7.1.5. + +NOTE 3: The QoS rule pre-configured in the UE is only used together with option 1a for control QoS Flows as described in clause 5.7.1.3. How to keep the consistency of QFI and Packet Filter Set between UE and network is out of scope in this release of the specification. + +For Unstructured type PDU Session, the default QoS rule does not contain a Packet Filter Set, and in this case the default QoS rule defines the treatment of all packets in the PDU Session. + +As long as the default QoS rule does not contain a Packet Filter Set or contains a Packet Filter Set that allows all UL packets, Reflective QoS should not be applied for the QoS Flow which the default QoS rule is associated with and the RQA should not be sent for this QoS Flow. + +#### 5.7.1.5 QoS Flow mapping + +The SMF performs the binding of PCC rules to QoS Flows based on the QoS and service requirements (as defined in TS 23.503 [45]). The SMF assigns the QFI for a new QoS Flow and derives its QoS profile, corresponding UPF instructions and QoS Rule(s) from the PCC rule(s) bound to the QoS Flow and other information provided by the PCF. + +When applicable, the SMF provides the following information for the QoS Flow to the (R)AN: + +- QFI; +- QoS profile as described in clause 5.7.1.2. +- optionally, Alternative QoS Profile(s) as described in clause 5.7.1.2a; + +For each PCC rule bound to a QoS Flow, the SMF provides the following information to the UPF enabling classification, bandwidth enforcement and marking of User Plane traffic (the details are described in clause 5.8): + +- a DL PDR containing the DL part of the SDF template; +- an UL PDR containing the UL part of the SDF template; + +NOTE 1: If a DL PDR for an bidirectional SDF is associated with a QoS Flow other than the one associated with the default QoS rule and the UE has not received any instruction to use this QoS Flow for the SDF in uplink direction (i.e. neither a corresponding QoS rule is sent to the UE nor the Reflective QoS Indication is set in the PCC rule), it means that the UL PDR for the same SDF has to be associated with the QoS Flow associated with the default QoS rule. + +- the PDR precedence value (see clause 5.7.1.9) for both PDRs is set to the precedence value of the PCC rule; +- QoS related information (e.g. MBR for an SDF, GFBR and MFBR for a GBR QoS Flow) as described in clause 5.8.2; +- the corresponding packet marking information (e.g. the QFI, the transport level packet marking value (e.g. the DSCP value of the outer IP header)); +- optionally, the Reflective QoS Indication is included in the QER associated with the DL PDR (as described in clause 5.7.5.3). + +For each PCC rule bound to a QoS Flow, when applicable, the SMF generates an explicitly signalled QoS rule (see clause 5.7.1.4) according to the following principles and provides it to the UE together with an add operation: + +- A unique (for the PDU Session) QoS rule identifier is assigned; +- The QFI in the QoS rule is set to the QFI of the QoS Flow to which the PCC rule is bound; + +- The Packet Filter Set of the QoS rule is generated from the UL SDF filters and optionally the DL SDF filters of the PCC rule (but only from those SDF filters that have an indication for being signalled to the UE, as defined in TS 23.503 [45]); +- The QoS rule precedence value is set to the precedence value of the PCC rule for which the QoS rule is generated; +- for a dynamically assigned QFI, the QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR, Averaging Window, see TS 24.501 [47]) are signalled to UE in addition to the QoS rule(s) associated to the QoS Flow. The QoS Flow level QoS parameters of an existing QoS Flow may be updated based on the MBR and GBR information received in the PCC rule (MBR and GBR per SDF are however not provided to UE over N1 in the case of more than one SDF) or, if the PCF has not indicated differently, when Notification control or handover related signalling indicates that the QoS parameter the NG-RAN is currently fulfilling for the QoS Flow have changed (see clause 5.7.2.4). + +Changes in the binding of PCC rules to QoS Flows as well as changes in the PCC rules or other information provided by the PCF can require QoS Flow changes which the SMF has to provide to (R)AN, UPF and/or UE. In the case of changes in the explicitly signalled QoS rules associated to a QoS Flow, the SMF provides the explicitly signalled QoS rules and their operation (i.e. add/modify/delete) to the UE. + +NOTE 2: The SMF cannot provide, update or remove pre-configured QoS rules or UE derived QoS rules. + +The principle for classification and marking of User Plane traffic and mapping of QoS Flows to AN resources is illustrated in Figure 5.7.1.5-1. + +![Diagram illustrating the principle for classification and User Plane marking for QoS Flows and mapping to AN Resources. The diagram shows three main components: Application / Service Layer, UE, and UPF, connected via an AN (Access Network). Data packets from applications are sent to the UE. In the UE, QoS rules (mapping UL packets to QoS flows and apply QoS flow marking) are applied, resulting in QoS Flows (all packets marked with the same QFI). These QoS Flows are then mapped to AN Resources. The AN (Access Network) contains a PDU Session and AN Resources. The UPF (User Plane Function) contains PDRs (classify packets for QoS flow marking and other actions). Arrows show the flow of data packets from the Application / Service Layer through the UE, AN, and UPF.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +Diagram illustrating the principle for classification and User Plane marking for QoS Flows and mapping to AN Resources. The diagram shows three main components: Application / Service Layer, UE, and UPF, connected via an AN (Access Network). Data packets from applications are sent to the UE. In the UE, QoS rules (mapping UL packets to QoS flows and apply QoS flow marking) are applied, resulting in QoS Flows (all packets marked with the same QFI). These QoS Flows are then mapped to AN Resources. The AN (Access Network) contains a PDU Session and AN Resources. The UPF (User Plane Function) contains PDRs (classify packets for QoS flow marking and other actions). Arrows show the flow of data packets from the Application / Service Layer through the UE, AN, and UPF. + +**Figure 5.7.1.5-1: The principle for classification and User Plane marking for QoS Flows and mapping to AN Resources** + +In DL, incoming data packets are classified by the UPF based on the Packet Filter Sets of the DL PDRs in the order of their precedence (without initiating additional N4 signalling). The UPF conveys the classification of the User Plane traffic belonging to a QoS Flow through an N3 (and N9) User Plane marking using a QFI. The AN binds QoS Flows to AN resources (i.e. Data Radio Bearers of in the case of 3GPP RAN). There is no strict 1:1 relation between QoS Flows and AN resources. It is up to the AN to establish the necessary AN resources that QoS Flows can be mapped to, and to release them. The AN shall indicate to the SMF when the AN resources onto which a QoS Flow is mapped are released. + +If no matching DL PDR is found, the UPF shall discard the DL data packet. + +In UL: + +- For a PDU Session of Type IP or Ethernet, the UE evaluates UL packets against the UL Packet Filters in the Packet Filter Set in the QoS rules based on the precedence value of QoS rules in increasing order until a matching QoS rule (i.e. whose Packet Filter matches the UL packet) is found. +- If no matching QoS rule is found, the UE shall discard the UL data packet. + +- For a PDU Session of Type Unstructured, the default QoS rule does not contain a Packet Filter Set and allows all UL packets. + +NOTE 3: Only the default QoS rule exist for a PDU Session of Type Unstructured. + +The UE uses the QFI in the corresponding matching QoS rule to bind the UL packet to a QoS Flow. The UE then binds QoS Flows to AN resources. + +#### 5.7.1.6 DL traffic + +The following characteristics apply for processing of DL traffic: + +- UPF maps User Plane traffic to QoS Flows based on the PDRs. +- UPF performs Session-AMBR enforcement as specified in clause 5.7.1.8 and performs counting of packets for charging. +- UPF transmits the PDUs of the PDU Session in a single tunnel between 5GC and (R)AN, the UPF includes the QFI in the encapsulation header. In addition, UPF may include an indication for Reflective QoS activation in the encapsulation header. +- UPF performs transport level packet marking in DL on a per QoS Flow basis. The UPF uses the transport level packet marking value provided by the SMF (as described in clause 5.8.2.7). +- (R)AN maps PDUs from QoS Flows to access-specific resources based on the QFI and the associated 5G QoS profile, also taking into account the N3 tunnel associated with the DL packet. + +NOTE: Packet Filters are not used for the mapping of QoS Flows onto access-specific resources in (R)AN. + +- If Reflective QoS applies, the UE creates a new derived QoS rule as defined in clause 5.7.5.2. + +#### 5.7.1.7 UL Traffic + +Following characteristics apply for processing of UL traffic: + +- UE uses the stored QoS rules to determine mapping between UL User Plane traffic and QoS Flows. UE marks the UL PDU with the QFI of the QoS rule containing the matching Packet Filter and transmits the UL PDUs using the corresponding access specific resource for the QoS Flow based on the mapping provided by (R)AN. For NG-RAN, the UL behaviour is specified in clause 10.5.2 of TS 38.300 [27]. +- (R)AN transmits the PDUs over N3 tunnel towards UPF. When passing an UL packet from (R)AN to CN, the (R)AN includes the QFI value, in the encapsulation header of the UL PDU, and selects the N3 tunnel. +- (R)AN performs transport level packet marking in the UL on a per QoS Flow basis with a transport level packet marking value that is determined based on the 5QI, the Priority Level (if explicitly signalled) and the ARP priority level of the associated QoS Flow. +- UPF verifies whether QFIs in the UL PDUs are aligned with the QoS Rules provided to the UE or implicitly derived by the UE in the case of Reflective QoS). +- UPF and UE perform Session-AMBR enforcement as specified in clause 5.7.1.8 and the UPF performs counting of packets for charging. + +#### 5.7.1.8 AMBR/MFBR enforcement and rate limitation + +UL and DL Session-AMBR (see clause 5.7.2.6) shall be enforced by the UPF, if the UPF receives the Session-AMBR values from the SMF as described in clause 5.8.2.7 and clause 5.8.5.4. + +For UL Classifier PDU Sessions, UL and DL Session-AMBR (see clause 5.7.2.6) shall be enforced in the SMF selected UPF that supports the UL Classifier functionality. In addition, the DL Session-AMBR shall be enforced separately in every UPF that terminates the N6 interface (i.e. without requiring interaction between the UPFs) (see clause 5.6.4). + +For multi-homed PDU Sessions, UL and DL Session-AMBR shall be enforced in the UPF that supports the Branching Point functionality. In addition, the DL Session-AMBR shall be enforced separately in every UPF that terminates the N6 interface (i.e. without requiring interaction between the UPFs) (see clause 5.6.4). + +**NOTE:** The DL Session-AMBR is enforced in every UPF terminating the N6 interface to reduce unnecessary transport of traffic which may be discarded by the UPF performing the UL Classifier/Branching Point functionality due to the amount of the DL traffic for the PDU Session exceeding the DL Session-AMBR. Discarding DL packets in the UL Classifier/Branching Point could cause erroneous PDU counting for support of charging + +The (R)AN shall enforce UE-AMBR (see clause 5.7.2.6) in UL and DL per UE for Non-GBR QoS Flows. + +The UE shall perform UL rate limitation on PDU Session basis for Non-GBR traffic using Session-AMBR, if the UE receives a Session-AMBR. + +MBR per SDF is mandatory for GBR QoS Flows but optional for Non-GBR QoS Flows. The MBR is enforced in the UPF. + +The MFBR is enforced in the UPF in the Downlink for GBR QoS Flows. The MFBR is enforced in the (R)AN in the Downlink and Uplink for GBR QoS Flows. For non-3GPP access, the UE should enforce MFBR in the Uplink for GBR QoS Flows. + +The QoS control for Unstructured PDUs is performed at the PDU Session level and in this Release of the specification there is only support for maximum of one 5G QoS Flow per PDU Session of Type Unstructured. + +When a PDU Session is set up for transferring unstructured PDUs, SMF provides the QFI which will be applied to any packet of the PDU Session to the UPF and UE. + +#### 5.7.1.9 Precedence Value + +The QoS rule precedence value and the PDR precedence value determine the order in which a QoS rule or a PDR, respectively, shall be evaluated. The evaluation of the QoS rules or PDRs is performed in increasing order of their precedence value. + +#### 5.7.1.10 UE-Slice-MBR enforcement and rate limitation + +If a supporting NG-RAN receives for a UE a UE-Slice-MBR (see clause 5.7.2.6) for an S-NSSAI from the AMF, the NG-RAN shall apply this UE-Slice-MBR for all PDU Sessions of that UE corresponding to the S-NSSAI which have an active user plane if feasible. In particular, the NG-RAN shall enforce this UE-Slice-MBR as follows: + +- 1) Whenever a request for a GBR QoS Flow establishment or modification is received, the NG-RAN admission control shall ensure that the sum of the GFBR values of the admitted GBR QoS Flows is not exceeding the UE-Slice-MBR and, if the QoS Flow cannot be admitted, the NG-RAN shall reject the establishment/modification of the QoS Flow. + +**NOTE:** If the UE-Slice-MBR would be exceeded by a new/modified GBR QoS Flow, the NG-RAN determines whether the new/modified GBR QoS Flow can pre-empt any existing GBR QoS Flow of the UE's PDU Session(s) corresponding to the same S-NSSAI based on their ARP values (as per clause 5.7.2.2), e.g. to support certain priority services (e.g. MPS). If this is not possible, the NG-RAN can reject the establishment/modification of the QoS Flow. + +- 2) The NG-RAN shall ensure that the aggregated bitrate across all GBR and Non-GBR QoS Flows belonging to those PDU Sessions is not exceeding the UE-Slice-MBR, while always guaranteeing the GFBR of every GBR QoS Flow of those PDU Sessions as described in clause 5.7.2.5. + +#### 5.7.1.11 QoS aspects of home-routed roaming + +In the case of home-routed roaming, the V-SMF may apply VPLMN policies related with the SLA negotiated with the HPLMN or with QoS values supported by the VPLMN. Such policies may result in a situation that the V-SMF does not accept the PDU Session or does not accept some of the QoS Flows requested by the H-SMF. + +QoS constraints represent the QoS that the VPLMN can accept for the QoS Flow associated with the default QoS rule and the PDU Session based on SLA or based on QoS values supported by the VPLMN. The QoS constraints may + +contain 5QI, 5QI Priority Level and ARP for the QoS Flow associated with the default QoS rule and highest Session-AMBR accepted by the VPLMN. + +NOTE: For this Release of the specification, QoS constraints apply only to the non-GBR default QoS Flow. + +At PDU Session Establishment for home-routed roaming, to reduce the risk of PDU Session establishment failure due to QoS from the HPLMN not being compliant with SLA, the V-SMF may provide the VPLMN local policy in QoS constraints to the H-SMF as specified in clause 4.3.2.2.2 of TS 23.502 [3]. + +For intra-5GS mobility with V-SMF insertion or V-SMF change (e.g. inter-PLMN mobility), as specified in clause 4.23 of TS 23.502 [3], the new/target V-SMF may validate the currently applied QoS against the QoS constraints. The new/target V-SMF provides QoS constraints to the H-SMF during the mobility procedure. The new/target V-SMF may temporarily accept a higher QoS even if the currently applied QoS exceeds the QoS constraints. Alternatively, for the QoS parameters related with the QoS constraints, the V-SMF may locally downgrade these values before providing the corresponding QoS profiles to 5G AN. The V-SMF may decide to release the PDU Session if the HPLMN does not provide updated QoS compliant with the QoS constraints after the mobility procedure. + +For IMS voice service (e.g. the IMS DNN defined by the GSMA), the V-SMF, based on local policy, may override the ARP received from HPLMN over N16 if the ARP indicates priority not in line with the local policy in VPLMN. The ARP override in the serving PLMN applies to both the QoS Flow associated with the default QoS rule and the QoS Flows for IMS voice, to apply the same allocation and retention priority for all users (i.e. roamers and non-roamers). For MPS (clause 5.16.5), the same allocation and retention priority is applied to all MPS service users (i.e. roamers and non-roamers), when roaming agreements are in place and where regulatory requirements apply. + +### 5.7.2 5G QoS Parameters + +#### 5.7.2.1 5QI + +A 5QI is a scalar that is used as a reference to 5G QoS characteristics defined in clause 5.7.4, i.e. access node-specific parameters that control QoS forwarding treatment for the QoS Flow (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). + +Standardized 5QI values have one-to-one mapping to a standardized combination of 5G QoS characteristics as specified in Table 5.7.4-1. + +The 5G QoS characteristics for pre-configured 5QI values are pre-configured in the AN. + +Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value, and are not signalled on any interface, unless certain 5G QoS characteristics are modified as specified in clauses 5.7.3.3, 5.7.3.4, 5.7.3.6, and 5.7.3.7. + +The 5G QoS characteristics for QoS Flows with dynamically assigned 5QI are signalled as part of the QoS profile. + +NOTE: On N3, each PDU (i.e. in the tunnel used for the PDU Session) is associated with one 5QI via the QFI carried in the encapsulation header. + +#### 5.7.2.2 ARP + +The QoS parameter ARP contains information about the priority level, the pre-emption capability and the pre-emption vulnerability. This allows deciding whether a QoS Flow establishment/modification/handover may be accepted or needs to be rejected in the case of resource limitations (typically used for admission control of GBR traffic). It may also be used to decide which existing QoS Flow to pre-empt during resource limitations, i.e. which QoS Flow to release to free up resources. + +The ARP priority level defines the relative importance of a QoS Flow. The range of the ARP priority level is 1 to 15 with 1 as the highest priority. + +The ARP priority levels 1-8 should only be assigned to QoS Flows for services that are authorized to receive prioritized treatment within an operator domain (i.e. that are authorized by the serving network). The ARP priority levels 9-15 may be assigned to QoS Flows for services that are authorized by the home network and thus applicable when a UE is roaming. + +NOTE: This ensures that future releases may use ARP priority level 1-8 to indicate e.g. emergency and other priority services within an operator domain in a backward compatible manner. This does not prevent the use of ARP priority level 1-8 in roaming situation in the case that appropriate roaming agreements exist that ensure a compatible use of these priority levels. + +The ARP pre-emption capability defines whether a QoS Flow may get resources that were already assigned to another QoS Flow with a lower priority. The ARP pre-emption vulnerability defines whether a QoS Flow may lose the resources assigned to it in order to admit a QoS Flow with higher priority. The ARP pre-emption capability and the ARP pre-emption vulnerability shall be either set to 'enabled' or 'disabled'. + +The ARP pre-emption vulnerability of the QoS Flow which the default QoS rule is associated with should be set appropriately to minimize the risk of a release of this QoS Flow. + +The details of how the SMF sets the ARP for a QoS Flow are further described in clause 5.7.2.7. + +#### 5.7.2.3 RQA + +The Reflective QoS Attribute (RQA) is an optional parameter which indicates that certain traffic (not necessarily all) carried on this QoS Flow is subject to Reflective QoS. Only when the RQA is signalled for a QoS Flow, the (R)AN enables the transfer of the RQI for AN resource corresponding to this QoS Flow. The RQA may be signalled to NG-RAN via the N2 reference point at UE context establishment in NG-RAN and at QoS Flow establishment or modification. + +#### 5.7.2.4 Notification control + +##### 5.7.2.4.1 General + +The QoS Parameter Notification control indicates whether notifications are requested from the NG-RAN when the "GFBR can no longer (or can again) be guaranteed" for a QoS Flow during the lifetime of the QoS Flow. Notification control may be used for a GBR QoS Flow if the application traffic is able to adapt to the change in the QoS (e.g. if the AF is capable to trigger rate adaptation). + +The SMF shall only enable Notification control when the QoS Notification Control parameter is set in the PCC rule (received from the PCF) that is bound to the QoS Flow. The Notification control parameter is signalled to the NG-RAN as part of the QoS profile. + +##### 5.7.2.4.1a Notification Control without Alternative QoS Profiles + +If, for a given GBR QoS Flow, Notification control is enabled and the NG-RAN determines that the GFBR, the PDB or the PER of the QoS profile cannot be fulfilled, NG-RAN shall send a notification towards SMF that the "GFBR can no longer be guaranteed". Furthermore, the NG-RAN shall keep the QoS Flow (i.e. while the NG-RAN is not fulfilling the requested QoS profile for this QoS Flow), unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion. The NG-RAN should try to fulfil the GFBR, the PDB and the PER of the QoS profile again. + +NOTE 1: NG-RAN can decide that the "GFBR can no longer be guaranteed" based on, e.g. measurements like queuing delay or system load. + +Upon receiving a notification from the NG-RAN that the "GFBR can no longer be guaranteed", the SMF may forward the notification to the PCF, see TS 23.503 [45]. + +When the NG-RAN determines that the GFBR, the PDB and the PER of the QoS profile can be fulfilled again for a QoS Flow (for which a notification that the "GFBR can no longer be guaranteed" has been sent), the NG-RAN shall send a notification, informing the SMF that the "GFBR can be guaranteed" again and the SMF may forward the notification to the PCF, see TS 23.503 [45]. The NG-RAN shall send a subsequent notification that the "GFBR can no longer be guaranteed" whenever necessary. + +NOTE 2: It is assumed that NG-RAN implementation will apply some hysteresis before determining that the "GFBR can be guaranteed again" and therefore a frequent signalling of "GFBR can be guaranteed again" followed by "GFBR can no longer be guaranteed" is not expected. + +NOTE 3: If the QoS Flow is modified, the NG-RAN restarts the check whether the "GFBR can no longer be guaranteed" according to the updated QoS profile. If the Notification control parameter is not included in the updated QoS profile, the Notification control is disabled. + +During a handover, the Source NG-RAN does not inform the Target NG-RAN about whether the Source NG-RAN has sent a notification for a QoS Flow that the "GFBR can no longer be guaranteed". The Target NG-RAN performs admission control rejecting any QoS Flows for which resources cannot be permanently allocated. The accepted QoS Flows are included in the N2 Path Switch Request or N2 Handover Request Acknowledge message from the NG-RAN to the AMF. The SMF shall interpret the fact that a QoS Flow is listed as transferred QoS Flow in the Nsmf\_PDUSession\_UpdateSMContext Request received from the AMF as a notification that "GFBR can be guaranteed again" for this QoS Flow unless the SMF is also receiving a reference to an Alternative QoS Profile for this QoS Flow (which is described in clause 5.7.2.4.2). After the handover is successfully completed, the Target NG-RAN shall send a subsequent notification that the "GFBR can no longer be guaranteed" for such a QoS Flow whenever necessary. If the SMF has previously notified the PCF that the "GFBR can no longer be guaranteed" and the SMF does not receive an explicit notification that the "GFBR can no longer be guaranteed" for that QoS Flow from the Target NG-RAN within a configured time, the SMF shall notify the PCF that the "GFBR can be guaranteed again". + +##### 5.7.2.4.1b Notification control with Alternative QoS Profiles + +If, for a given GBR QoS Flow, Notification control is enabled and the NG-RAN has received a list of Alternative QoS Profile(s) for this QoS Flow and supports the Alternative QoS Profile handling, the following shall apply: + +- 1) If the NG-RAN determines that the GFBR, the PDB or the PER of the QoS profile cannot be fulfilled, NG-RAN shall send a notification towards SMF that the "GFBR can no longer be guaranteed". Before sending a notification that the "GFBR can no longer be guaranteed" towards the SMF, the NG-RAN shall check whether the GFBR, the PDB and the PER that the NG-RAN currently fulfils match any of the Alternative QoS Profile(s) in the indicated priority order. If there is a match, the NG-RAN shall indicate the reference to the matching Alternative QoS Profile with the highest priority together with the notification to the SMF. + +If there is no match, the NG-RAN shall send a notification that the "GFBR can no longer be guaranteed" towards the SMF indicating that the lowest Alternative QoS Profile cannot be fulfilled (unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion). + +- 2) If a notification that the "GFBR can no longer be guaranteed" has been sent to the SMF and the NG-RAN determines that the currently fulfilled GFBR, PDB or PER are different (better or worse) from the situation indicated in the last notification, the NG-RAN shall send a notification (i.e. "GFBR can no longer be guaranteed" or "GFBR can be guaranteed again") to the SMF and indicate the current situation (unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion). + +NOTE 1: The current situation is either that the QoS Profile can be fulfilled (which is implicitly indicated by the "GFBR can be guaranteed again" notification itself), that a different Alternative QoS Profile can be fulfilled, or that the lowest priority Alternative QoS Profile cannot be fulfilled. + +- 3)- The NG-RAN should always try to fulfil the QoS profile and, if this is not possible, any Alternative QoS Profile that has higher priority. + +NOTE 2: In order to avoid a too frequent signalling to the SMF, it is assumed that NG-RAN implementation can apply hysteresis (e.g. via a configurable time interval) before notifying the SMF that the currently fulfilled values match the QoS Profile or a different Alternative QoS Profile of higher priority. It is also assumed that the PCF has ensured that the QoS values within the different Alternative QoS Profile(s) are not too close to each other. + +- 4) Upon receiving a notification from the NG-RAN, the SMF may inform the PCF. If it does so, the SMF shall indicate the currently fulfilled situation to the PCF. See TS 23.503 [45]. +- 5) If the PCF has not indicated differently, the SMF uses NAS signalling (that is sent transparently through the RAN) to inform the UE about changes in the QoS parameters (i.e. 5QI, GFBR, MFBR) that the NG-RAN is currently fulfilling for the QoS Flow after Notification control has occurred. + +##### 5.7.2.4.2 Usage of Notification control with Alternative QoS Profiles at handover + +During handover, the prioritized list of Alternative QoS Profile(s) (if available) is provided to the Target NG-RAN per QoS Flow in addition to the QoS profile. If the Target NG-RAN is not able to guarantee the GFBR, the PDB and the PER included in the QoS profile and if Alternative QoS Profiles are provided to the Target NG-RAN and the Target NG-RAN supports Alternative QoS Profiles, the Target NG-RAN checks whether the GFBR, the PDB and the PER values that it can fulfil match any of the Alternative QoS Profile(s) taking the priority order into account. If there is a match between one of the Alternative QoS Profiles and the GFBR, the PDB and the PER values that Target NG-RAN can fulfil, the Target NG-RAN shall accept the QoS Flow and indicate the reference to that Alternative QoS Profile to the Source NG-RAN. + +For delay-critical GBR QoS flows, the Target NG-RAN also takes into consideration whether it is able to accept the MDBV if it is included in the Alternative QoS profile. + +If there is no match to any Alternative QoS Profile, the Target NG-RAN rejects QoS Flows for which the Target NG-RAN is not able to guarantee the GFBR, the PDB, the PER and if available, an associated MDBV included in the QoS profile. + +After the handover is completed and a QoS Flow has been accepted by the Target NG-RAN based on an Alternative QoS Profile, the Target NG-RAN shall treat this QoS Flow in the same way as if it had sent a notification that the "GFBR can no longer be guaranteed" with a reference to that Alternative QoS Profile to the SMF (as described in clause 5.7.2.4.1b). + +If a QoS Flow has been accepted by the Target NG-RAN based on an Alternative QoS Profile, the reference to the matching Alternative QoS Profile is provided from the Target NG-RAN to the AMF (which forwards the message to the SMF) during the Xn and N2 based handover procedures as described in TS 23.502 [3]. After the handover is completed successfully, the SMF shall send a notification to the PCF that the "GFBR can no longer be guaranteed" for a QoS Flow (see TS 23.503 [45] for details) if the SMF has received a reference to an Alternative QoS Profile and this reference indicates a change in the previously notified state of this QoS Flow. If the PCF has not indicated differently, the SMF shall also use NAS signalling (that is sent transparently through the RAN) to inform the UE about the QoS parameters (i.e. 5QI, GFBR, MFBR) corresponding to the new state of the QoS Flow. + +NOTE: A state change for the QoS Flow comprises a change from QoS profile fulfilled to Alternative QoS Profile fulfilled as well as the state change between fulfilled Alternative QoS Profiles. + +If a QoS Flow has been accepted by the Target NG-RAN based on the QoS Profile, the SMF shall interpret the fact that a QoS Flow is listed as transferred QoS Flow in the message received from the AMF as a notification that "GFBR can be guaranteed again" for this QoS Flow. After the handover is successfully completed, the Target NG-RAN performs as described in clause 5.7.2.4.1b. If the SMF has previously notified the PCF that the "GFBR can no longer be guaranteed" and the SMF does not receive an explicit notification that the "GFBR can no longer be guaranteed" for that QoS Flow from the Target NG-RAN within a configured time, the SMF shall notify the PCF that the "GFBR can be guaranteed again". + +If a QoS Flow has been accepted by the Target NG-RAN and SMF did not receive from the Target NG-RAN a reference to any Alternative QoS Profile and the SMF has previously informed the UE about QoS parameters corresponding to any of the Alternative QoS Profile(s), the SMF shall use NAS signalling to inform the UE about the QoS parameters corresponding to the QoS Profile. + +##### 5.7.2.4.3 Usage of Notification control with Alternative QoS Profiles during QoS Flow establishment and modification + +During QoS Flow establishment and modification, a prioritized list of Alternative QoS Profile(s) can be provided to the NG-RAN for the QoS Flow in addition to the QoS profile. If the NG-RAN is not able to guarantee the GFBR, the PDB and the PER included in the QoS profile and if Alternative QoS Profiles are provided to the NG-RAN and the NG-RAN supports Alternative QoS Profiles, the NG-RAN shall check whether the GFBR, the PDB and the PER values that it can fulfil match at least one of the Alternative QoS Profile(s) taking the priority order into account. If there is a match between one of the Alternative QoS Profiles and the GFBR, the PDB and if available, associated MDBV and the PER values that the NG-RAN can fulfil, the NG-RAN shall accept the QoS Flow and indicate the reference to that Alternative QoS Profile to the SMF. If there is no match to any Alternative QoS Profile, the NG-RAN shall reject the QoS Flow establishment or modification. + +After a successful QoS Flow establishment or modification during which the NG-RAN indicated that the currently fulfilled QoS matches one of the Alternative QoS Profiles, the NG-RAN shall treat this QoS Flow in the same way as if + +it had sent a notification that the "GFBR can no longer be guaranteed" with a reference to that Alternative QoS Profile to the SMF (as described in clause 5.7.2.4.1b). + +If the SMF has received a reference to an Alternative QoS Profile during QoS Flow establishment and modification the SMF may inform the PCF about it (as described in TS 23.503 [45]). + +If the PCF has not indicated differently, the SMF shall use NAS signalling (that is sent transparently through the RAN) to inform the UE about the QoS parameters (i.e. 5QI, GFBR, MFBR) corresponding to the referenced Alternative QoS Profile. + +#### 5.7.2.5 Flow Bit Rates + +For GBR QoS Flows only, the following additional QoS parameters exist: + +- Guaranteed Flow Bit Rate (GFBR) - UL and DL; +- Maximum Flow Bit Rate (MFBR) -- UL and DL. + +The GFBR denotes the bit rate that is guaranteed to be provided by the network to the QoS Flow over the Averaging Time Window. The MFBR limits the bit rate to the highest bit rate that is expected by the QoS Flow (e.g. excess traffic may get discarded or delayed by a rate shaping or policing function at the UE, RAN, UPF). Bit rates above the GFBR value and up to the MFBR value, may be provided with relative priority determined by the Priority Level of the QoS Flows (see clause 5.7.3.3). + +GFBR and MFBR are signalled to the (R)AN in the QoS Profile and signalled to the UE as QoS Flow level QoS parameter (as specified in TS 24.501 [47]) for each individual QoS Flow. + +NOTE 1: The GFBR is recommended as the lowest acceptable service bitrate where the service will survive. + +NOTE 2: For each QoS Flow of Delay-critical GBR resource type, the SMF can ensure that the GFBR of the QoS Flow can be achieved with the MDBV of the QoS Flow using the QoS Flow binding functionality described in clause 6.1.3.2.4 of TS 23.503 [45]. + +NOTE 3: The network can set MFBR larger than GFBR for a particular QoS Flow based on operator policy and the knowledge of the end point capability, i.e. support of rate adaptation at application / service level. + +#### 5.7.2.6 Aggregate Bit Rates + +Each PDU Session of a UE is associated with the following aggregate rate limit QoS parameter: + +- per Session Aggregate Maximum Bit Rate (Session-AMBR). + +The Session-AMBR is signalled to the appropriate UPF entity/ies to the UE and to the (R)AN (to enable the calculation of the UE-AMBR). The Session-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows for a specific PDU Session. The Session-AMBR is measured over an AMBR averaging window which is a standardized value. The Session-AMBR is not applicable to GBR QoS Flows. + +Each UE is associated with the following aggregate rate limit QoS parameter: + +- per UE Aggregate Maximum Bit Rate (UE-AMBR). + +The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows of a UE. Each (R)AN shall set its UE-AMBR to the sum of the Session-AMBR of all PDU Sessions with active user plane to this (R)AN up to the value of the UE-AMBR received from AMF. The UE-AMBR is a parameter provided to the (R)AN by the AMF based on the value of the subscribed UE-AMBR retrieved from UDM or the dynamic serving network UE-AMBR retrieved from PCF (e.g. for roaming subscriber). The AMF provides the UE-AMBR provided by PCF to (R)AN if available. The UE-AMBR is measured over an AMBR averaging window which is a standardized value. The UE-AMBR is not applicable to GBR QoS Flows. + +Each group of PDU Sessions of the UE for the same slice (S-NSSAI) may be associated with the following aggregate rate limit QoS parameter: + +- per UE per Slice-Maximum Bit Rate (UE-Slice-MBR). + +The UE-Slice-MBR limits the aggregate bit rate that can be expected to be provided across all GBR and Non-GBR QoS Flows corresponding to PDU Sessions of the UE for the same slice (S-NSSAI) which have an active user plane. Each supporting NG-RAN shall set its UE-Slice-MBR to the sum of the Session-AMBR and MFBR for GBR QoS Flows of all PDU Sessions corresponding to the slice (S-NSSAI) with active user plane to this NG-RAN up to the value of the UE-Slice-MBR corresponding to the slice (S-NSSAI) received from AMF. The UE-Slice-MBR is measured over an AMBR averaging window which is a standardized value. The UE-Slice-MBR is an optional parameter provided to the NG-RAN by the AMF as described in clause 5.15.13. + +NOTE: The AMBR averaging window is only applied to Session-AMBR, UE-AMBR and UE-Slice-MBR measurement and the AMBR averaging windows for Session-AMBR and UE-AMBR are standardised to the same value. + +#### 5.7.2.7 Default values + +For each PDU Session Setup, the SMF retrieves the subscribed Session-AMBR values as well as the subscribed default values for the 5QI and the ARP and optionally, the 5QI Priority Level, from the UDM. The subscribed default 5QI value shall be a Non-GBR 5QI from the standardized value range. + +NOTE 1: The 5QI Priority Level can be added to the subscription information to achieve an overwriting of the standardized or preconfigured 5QI Priority Level e.g. in scenarios where dynamic PCC is not deployed or the PCF is unavailable or unreachable. + +The SMF may change the subscribed values for the default 5QI and the ARP and if received, the 5QI Priority Level, based on interaction with the PCF as described in TS 23.503 [45] or, if dynamic PCC is not deployed, based on local configuration, to set QoS parameters for the QoS Flow associated with the default QoS rule. + +For QoS Flow(s) of the PDU Session other than the QoS Flow associated with the default QoS rule, the SMF shall set the ARP priority level, the ARP pre-emption capability and the ARP pre-emption vulnerability to the respective values in the PCC rule(s) bound to that QoS Flow (as described in TS 23.503 [45]). If dynamic PCC is not deployed, the SMF shall set the ARP priority level, the ARP pre-emption capability and the ARP pre-emption vulnerability based on local configuration. + +NOTE 2: The local configuration in the SMF can e.g. make use of the subscribed value for the ARP priority level and apply locally configured values for the ARP pre-emption capability and ARP pre-emption vulnerability. + +If dynamic PCC is not deployed, the SMF can have a DNN based configuration to enable the establishment of a GBR QoS Flow as the QoS Flow that is associated with the default QoS rule. This configuration contains a standardized GBR 5QI as well as GFBR and MFBR for UL and DL. + +NOTE 3: Interworking with EPS is not possible for a PDU Session with a GBR QoS Flow as the QoS Flow that is associated with the default QoS rule. + +The SMF may change the subscribed Session-AMBR values (for UL and/or DL), based on interaction with the PCF as described in TS 23.503 [45] or, if dynamic PCC is not deployed, based on local configuration, to set the Session-AMBR values for the PDU Session. + +#### 5.7.2.8 Maximum Packet Loss Rate + +The Maximum Packet Loss Rate (UL, DL) indicates the maximum rate for lost packets of the QoS Flow that can be tolerated in the uplink and downlink direction. This is provided to the QoS Flow if it is compliant to the GFBR. + +NOTE: In this Release of the specification, the Maximum Packet Loss Rate (UL, DL) can only be provided for a GBR QoS Flow belonging to voice media. + +#### 5.7.2.9 Wireline access network specific 5G QoS parameters + +QoS parameters that are applicable only for or wireline access networks (W-5GAN) are specified in TS 23.316 [84]. + +### 5.7.3 5G QoS characteristics + +#### 5.7.3.1 General + +This clause specifies the 5G QoS characteristics associated with 5QI. The characteristics describe the packet forwarding treatment that a QoS Flow receives edge-to-edge between the UE and the UPF in terms of the following performance characteristics: + +- 1 Resource type (Non-GBR, GBR, Delay-critical GBR); +- 2 Priority Level; +- 3 Packet Delay Budget (including Core Network Packet Delay Budget); +- 4 Packet Error Rate; +- 5 Averaging window (for GBR and Delay-critical GBR resource type only); +- 6 Maximum Data Burst Volume (for Delay-critical GBR resource type only). + +The 5G QoS characteristics should be understood as guidelines for setting node specific parameters for each QoS Flow e.g. for 3GPP radio access link layer protocol configurations. + +Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value, and are not signalled on any interface, unless certain 5G QoS characteristics are modified as specified in clauses 5.7.3.3, 5.7.3.4, 5.7.3.6, and 5.7.3.7. + +NOTE: As there are no default values specified, pre-configured 5G QoS characteristics have to include all of the characteristics listed above. + +Signalled 5G QoS characteristics are provided as part of the QoS profile and shall include all of the characteristics listed above. + +#### 5.7.3.2 Resource Type + +The resource type determines if dedicated network resources related to a QoS Flow-level Guaranteed Flow Bit Rate (GFBR) value are permanently allocated (e.g. by an admission control function in a radio base station). + +GBR QoS Flows are therefore typically authorized "on demand" which requires dynamic policy and charging control. A GBR QoS Flow uses either the GBR resource type or the Delay-critical GBR resource type. The definition of PDB and PER are different for GBR and Delay-critical GBR resource types, and the MDBV parameter applies only to the Delay-critical GBR resource type. + +A Non-GBR QoS Flow may be pre-authorized through static policy and charging control. A Non-GBR QoS Flow uses only the Non-GBR resource type. + +#### 5.7.3.3 Priority Level + +The Priority Level associated with 5G QoS characteristics indicates a priority in scheduling resources among QoS Flows. The lowest Priority Level value corresponds to the highest priority. + +The Priority Level shall be used to differentiate between QoS Flows of the same UE, and it shall also be used to differentiate between QoS Flows from different UEs. + +In the case of congestion, when all QoS requirements cannot be fulfilled for one or more QoS Flows, the Priority Level shall be used to select for which QoS Flows the QoS requirements are prioritised such that a QoS Flow with Priority Level value N is prioritized over QoS Flows with higher Priority Level values (i.e. N+1, N+2, etc). In the case of no congestion, the Priority Level should be used to define the resource distribution between QoS Flows. In addition, the scheduler may prioritize QoS Flows based on other parameters (e.g. resource type, radio condition) in order to optimize application performance and network capacity. + +Every standardized 5QI is associated with a default value for the Priority Level -specified in QoS characteristics Table 5.7.4.1). Priority Level may also be signalled together with a standardized 5QI to the -R)AN, and if it is received, it shall be used instead of the default value. + +Priority Level may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it shall be used instead of the pre-configured value. + +#### 5.7.3.4 Packet Delay Budget + +The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the N6 termination point at the UPF. The PDB applies to the DL packet received by the UPF over the N6 interface, and to the UL packet sent by the UE. For a certain 5QI the value of the PDB is the same in UL and DL. In the case of 3GPP access, the PDB is used to support the configuration of scheduling and link layer functions (e.g. the setting of scheduling priority weights and HARQ target operating points). For GBR QoS Flows using the Delay-critical resource type, a packet delayed more than PDB is counted as lost if the data burst is not exceeding the MDBV within the period of PDB and the QoS Flow is not exceeding the GFBR. For GBR QoS Flows with GBR resource type not exceeding GFBR, 98 percent of the packets shall not experience a delay exceeding the 5QI's PDB. + +The 5G Access Network Packet Delay Budget (5G-AN PDB) is determined by subtracting a static value for the Core Network Packet Delay Budget (CN PDB), which represents the delay between any N6 termination point at the UPF (for any UPF that may possibly be selected for the PDU Session) and the 5G-AN from a given PDB. + +NOTE 1: For a standardized 5QI, the static value for the CN PDB is specified in the QoS characteristics Table 5.7.4-1. + +NOTE 2: For a non-standardized 5QI, the static value for the CN PDB is homogeneously configured in the network. + +For GBR QoS Flows using the Delay-critical resource type, in order to obtain a more accurate delay budget PDB available for the NG-RAN, a dynamic value for the CN PDB, which represents the delay between the UPF terminating N6 for the QoS Flow and the 5G-AN, can be used. If used for a QoS Flow, the NG-RAN shall apply the dynamic value for the CN PDB instead of the static value for the CN PDB (which is only related to the 5QI). Different dynamic value for CN PDB may be configured per uplink and downlink direction. + +NOTE 3: The configuration of transport network on CN tunnel can be different per UL and DL, which can be different value for CN PDB per UL and DL. + +NOTE 4: It is expected that the UPF deployment ensures that the dynamic value for the CN PDB is not larger than the static value for the CN PDB. This avoids that the functionality that is based on the 5G-AN PDB (e.g. MDBV, NG-RAN scheduler) has to handle an unexpected value. + +The dynamic value for the CN PDB of a Delay-critical GBR 5QI may be configured in the network in two ways: + +- Configured in each NG-RAN node, based on a variety of inputs such as different IP address(es) or TEID range of UPF terminating the N3 tunnel and based on different combinations of PSA UPF to NG-RAN under consideration of any potential I-UPF, etc; +- Configured in the SMF, based on different combinations of PSA UPF to NG-RAN under consideration of any potential I-UPF. The dynamic value for the CN PDB for a particular QoS Flow shall be signalled to NG-RAN (during PDU Session Establishment, PDU Session Modification, Xn/N2 handover and the Service Request procedures) when the QoS Flow is established or the dynamic value for the CN PDB of a QoS Flow changes, e.g. when an I-UPF is inserted by the SMF. + +If the NG-RAN node is configured locally with a dynamic value for the CN PDB for a Delay-critical GBR 5QI, and receives a different value via N2 signalling for a QoS Flow with the same 5QI, local configuration in RAN node determines which value takes precedence. + +Services using a GBR QoS Flow and sending at a rate smaller than or equal to the GFBR can in general assume that congestion related packet drops will not occur. + +NOTE 5: Exceptions (e.g. transient link outages) can always occur in a radio access system which may then lead to congestion related packet drops. Packets surviving congestion related packet dropping may still be subject to non-congestion related packet losses (see PER below). + +Services using Non-GBR QoS Flows should be prepared to experience congestion-related packet drops and delays. In uncongested scenarios, 98 percent of the packets should not experience a delay exceeding the 5QI's PDB. + +The PDB for Non-GBR and GBR resource types denotes a "soft upper bound" in the sense that an "expired" packet, e.g. a link layer SDU that has exceeded the PDB, does not need to be discarded and is not added to the PER. However, for a Delay-critical GBR resource type, packets delayed more than the PDB are added to the PER and can be discarded or delivered depending on local decision. + +#### 5.7.3.5 Packet Error Rate + +The Packet Error Rate (PER) defines an upper bound for the rate of PDUs (e.g. IP packets) that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). Thus, the PER defines an upper bound for a rate of non-congestion related packet losses. The purpose of the PER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP access). For every 5QI the value of the PER is the same in UL and DL. For GBR QoS Flows with Delay-critical GBR resource type, a packet which is delayed more than PDB is counted as lost, and included in the PER unless the data burst is exceeding the MDBV within the period of PDB or the QoS Flow is exceeding the GFBR. + +#### 5.7.3.6 Averaging Window + +Each GBR QoS Flow shall be associated with an Averaging window. The Averaging window represents the duration over which the GFBR and MFBR shall be calculated (e.g. in the (R)AN, UPF, UE). + +Every standardized 5QI (of GBR and Delay-critical GBR resource type) is associated with a default value for the Averaging window (specified in QoS characteristics Table 5.7.4.1). The averaging window may also be signalled together with a standardized 5QI to the (R)AN and UPF, and if it is received, it shall be used instead of the default value. + +The Averaging window may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it shall be used instead of the pre-configured value. + +#### 5.7.3.7 Maximum Data Burst Volume + +Each GBR QoS Flow with Delay-critical resource type shall be associated with a Maximum Data Burst Volume (MDBV). + +MDBV denotes the largest amount of data that the 5G-AN is required to serve within a period of 5G-AN PDB. + +Every standardized 5QI (of Delay-critical GBR resource type) is associated with a default value for the MDBV (specified in QoS characteristics Table 5.7.4.1). The MDBV may also be signalled together with a standardized 5QI to the (R)AN, and if it is received, it shall be used instead of the default value. + +The MDBV may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it shall be used instead of the pre-configured value. + +### 5.7.4 Standardized 5QI to QoS characteristics mapping + +Standardized 5QI values are specified for services that are assumed to be frequently used and thus benefit from optimized signalling by using standardized QoS characteristics. Dynamically assigned 5QI values (which require a signalling of QoS characteristics as part of the QoS profile) can be used for services for which standardized 5QI values are not defined. The one-to-one mapping of standardized 5QI values to 5G QoS characteristics is specified in table 5.7.4-1. + +**Table 5.7.4-1: Standardized 5QI to QoS characteristics mapping** + +| 5QI Value | Resource Type | Default Priority Level | Packet Delay Budget (NOTE 3) | Packet Error Rate | Default Maximum Data Burst Volume (NOTE 2) | Default Averaging Window | Example Services | +|----------------------|-----------------|------------------------|------------------------------------|-------------------|--------------------------------------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| 1 | GBR
(NOTE 1) | 20 | 100 ms (NOTE 11, NOTE 13) | $10^{-2}$ | N/A | 2000 ms | Conversational Voice | +| 2 | | 40 | 150 ms (NOTE 11, NOTE 13) | $10^{-3}$ | N/A | 2000 ms | Conversational Video (Live Streaming) | +| 3 | | 30 | 50 ms (NOTE 11, NOTE 13) | $10^{-3}$ | N/A | 2000 ms | Real Time Gaming, V2X messages (see TS 23.287 [121]).
Electricity distribution – medium voltage, Process automation monitoring | +| 4 | | 50 | 300 ms (NOTE 11, NOTE 13) | $10^{-6}$ | N/A | 2000 ms | Non-Conversational Video (Buffered Streaming) | +| 65 (NOTE 9, NOTE 12) | | 7 | 75 ms (NOTE 7, NOTE 8) | $10^{-2}$ | N/A | 2000 ms | Mission Critical user plane Push To Talk voice (e.g. MCPTT) | +| 66 (NOTE 12) | | 20 | 100 ms (NOTE 10, NOTE 13) | $10^{-2}$ | N/A | 2000 ms | Non-Mission-Critical user plane Push To Talk voice | +| 67 (NOTE 12) | | 15 | 100 ms (NOTE 10, NOTE 13) | $10^{-3}$ | N/A | 2000 ms | Mission Critical Video user plane | +| 75 (NOTE 14) | | 25 | 50 ms (NOTE 13) | $10^{-2}$ | N/A | 2000 ms | V2X messages (see TS 23.287 [121]).
A2X messages (see TS 23.256 [136]) | +| 71 | | 56 | 150 ms (NOTE 11, NOTE 13, NOTE 15) | $10^{-6}$ | N/A | 2000 ms | "Live" Uplink Streaming (e.g. TS 26.238 [76]) | +| 72 | | 56 | 300 ms (NOTE 11, NOTE 13, NOTE 15) | $10^{-4}$ | N/A | 2000 ms | "Live" Uplink Streaming (e.g. TS 26.238 [76]) | +| 73 | | 56 | 300 ms (NOTE 11, NOTE 13, NOTE 15) | $10^{-8}$ | N/A | 2000 ms | "Live" Uplink Streaming (e.g. TS 26.238 [76]) | +| 74 | | 56 | 500 ms (NOTE 11, NOTE 15) | $10^{-8}$ | N/A | 2000 ms | "Live" Uplink Streaming (e.g. TS 26.238 [76]) | +| 76 | | 56 | 500 ms (NOTE 11, NOTE 13, NOTE 15) | $10^{-4}$ | N/A | 2000 ms | "Live" Uplink Streaming (e.g. TS 26.238 [76]) | +| 5 | Non-GBR | 10 | 100 ms (NOTE 10, NOTE 13) | $10^{-6}$ | N/A | N/A | IMS Signalling | + +| | | | | | | | | +|----------------------------|--------------------|----|---------------------------------------------|-----------|------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6 | (NOTE 1) | 60 | 300 ms
(NOTE 10,
NOTE 13) | $10^{-6}$ | N/A | N/A | Video (Buffered Streaming)
TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.), AI/ML model download for image recognition (e.g. for model topology) (see TS 22.261 [2]) | +| 7 | | 70 | 100 ms
(NOTE 10,
NOTE 13) | $10^{-3}$ | N/A | N/A | Voice,
Video (Live Streaming)
Interactive Gaming,
AI/ML model download for image recognition (e.g. for model weight factors) (see TS 22.261 [2]) | +| 8 | | 80 | 300 ms
(NOTE 10,
NOTE 13) | $10^{-6}$ | N/A | N/A | Video (Buffered Streaming)
TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) | +| 9 | | 90 | | | | | | +| 10 | | 90 | 1100ms
(NOTE 10,
NOTE 13,
NOTE 17) | $10^{-6}$ | N/A | N/A | Video (Buffered Streaming)
TCP-based (e.g. www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) and any service that can be used over satellite access type with these characteristics | +| 69
(NOTE 9,
NOTE 12) | | 5 | 60 ms
(NOTE 7,
NOTE 8) | $10^{-6}$ | N/A | N/A | Mission Critical delay sensitive signalling (e.g. MC-PTT signalling) | +| 70
(NOTE 12) | | 55 | 200 ms
(NOTE 7,
NOTE 10) | $10^{-6}$ | N/A | N/A | Mission Critical Data (e.g. example services are the same as 5QI 6/8/9) | +| 79 | | 65 | 50 ms
(NOTE 10,
NOTE 13) | $10^{-2}$ | N/A | N/A | V2X messages (see TS 23.287 [121]) | +| 80 | | 68 | 10 ms
(NOTE 5,
NOTE 10) | $10^{-6}$ | N/A | N/A | Low Latency eMBB applications
Augmented Reality | +| 82 | Delay-critical GBR | 19 | 10 ms
(NOTE 4) | $10^{-4}$ | 255 bytes | 2000 ms | Discrete Automation (see TS 22.261 [2]) | +| 83 | | 22 | 10 ms
(NOTE 4) | $10^{-4}$ | 1354 bytes
(NOTE 3) | 2000 ms | Discrete Automation (see TS 22.261 [2]);
V2X messages (UE - RSU Platooning, Advanced Driving: Cooperative Lane Change with low LoA. See TS 22.186 [111], TS 23.287 [121]) | + +| | | | | | | | +|----|----|-------------------|-----------|------------------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 84 | 24 | 30 ms
(NOTE 6) | $10^{-5}$ | 1354 bytes
(NOTE 3) | 2000 ms | Intelligent transport systems (see TS 22.261 [2]) | +| 85 | 21 | 5 ms
(NOTE 5) | $10^{-5}$ | 255 bytes | 2000 ms | Electricity Distribution-high voltage (see TS 22.261 [2]). V2X messages (Remote Driving. See TS 22.186 [111], NOTE 16, see TS 23.287 [121]). Split AI/ML inference - DL Split AI/ML image recognition, (see TS 22.261 [2]) | +| 86 | 18 | 5 ms
(NOTE 5) | $10^{-4}$ | 1354 bytes | 2000 ms | V2X messages (Advanced Driving: Collision Avoidance, Platooning with high LoA. See TS 22.186 [111], TS 23.287 [121]) | +| 87 | 25 | 5 ms
(NOTE 4) | $10^{-3}$ | 500 bytes | 2000 ms | Interactive Service - Motion tracking data, (see TS 22.261 [2]) | +| 88 | 25 | 10 ms
(NOTE 4) | $10^{-3}$ | 1125 bytes | 2000 ms | Interactive Service - Motion tracking data, (see TS 22.261 [2]), split AI/ML inference - UL Split AI/ML image recognition, (see TS 22.261 [2]) | +| 89 | 25 | 15 ms
(NOTE 4) | $10^{-4}$ | 17000 bytes | 2000 ms | Visual content for cloud/edge/split rendering (see TS 22.261 [2]) | +| 90 | 25 | 20 ms
(NOTE 4) | $10^{-4}$ | 63000 bytes | 2000 ms | Visual content for cloud/edge/split rendering (see TS 22.261 [2]) | + +- NOTE 1: A packet which is delayed more than PDB is not counted as lost, thus not included in the PER. +- NOTE 2: It is required that default MDBV is supported by a PLMN supporting the related 5QIs. +- NOTE 3: The Maximum Transfer Unit (MTU) size considerations in clause 9.3 and Annex C of TS 23.060 [56] are also applicable. IP fragmentation may have impacts to CN PDB, and details are provided in clause 5.6.10. +- NOTE 4: A static value for the CN PDB of 1 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4. +- NOTE 5: A static value for the CN PDB of 2 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4. +- NOTE 6: A static value for the CN PDB of 5 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. When a dynamic CN PDB is used, see clause 5.7.3.4. +- NOTE 7: For Mission Critical services, it may be assumed that the UPF terminating N6 is located "close" to the 5G\_AN (roughly 10 ms) and is not normally used in a long distance, home routed roaming situation. Hence a static value for the CN PDB of 10 ms for the delay between a UPF terminating N6 and a 5G\_AN should be subtracted from this PDB to derive the packet delay budget that applies to the radio interface. +- NOTE 8: In RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED mode, the PDB requirement for these 5QIs can be relaxed (but not to a value greater than 320 ms) for the first packet(s) in a downlink data or signalling burst in order to permit reasonable battery saving (DRX) techniques. +- NOTE 9: It is expected that 5QI-65 and 5QI-69 are used together to provide Mission Critical Push to Talk service (e.g. 5QI-5 is not used for signalling). It is expected that the amount of traffic per UE will be similar or less compared to the IMS signalling. +- NOTE 10: In RRC\_IDLE, RRC\_INACTIVE and RRC\_CONNECTED mode, the PDB requirement for these 5QIs can be relaxed for the first packet(s) in a downlink data or signalling burst in order to permit battery saving (DRX) techniques. +- NOTE 11: In RRC\_IDLE and RRC\_INACTIVE mode, the PDB requirement for these 5QIs can be relaxed for the first packet(s) in a downlink data or signalling burst in order to permit battery saving (DRX) techniques. +- NOTE 12: This 5QI value can only be assigned upon request from the network side. The UE and any application running on the UE is not allowed to request this 5QI value. +- NOTE 13: A static value for the CN PDB of 20 ms for the delay between a UPF terminating N6 and a 5G-AN should be subtracted from a given PDB to derive the packet delay budget that applies to the radio interface. +- NOTE 14: This 5QI is only used for transmission of V2X messages as defined in TS 23.287 [121] and transmission of A2X messages as defined in TS 23.256 [136]. +- NOTE 15: For "live" uplink streaming (see TS 26.238 [76]), guidelines for PDB values of the different 5QIs correspond to the latency configurations defined in TR 26.939 [77]. In order to support higher latency reliable streaming services (above 500ms PDB), if different PDB and PER combinations are needed these configurations will have to use non-standardised 5QIs. +- NOTE 16: These services are expected to need much larger MDBV values to be signalled to the RAN. Support for such larger MDBV values with low latency and high reliability is likely to require a suitable RAN configuration, for which, the simulation scenarios in TR 38.824 [112] may contain some guidance. +- NOTE 17: The worst case one way propagation delay for GEO satellite is expected to be ~270ms, ~21 ms for LEO at 1200km, and 13 ms for LEO at 600km. The UL scheduling delay that needs to be added is also typically two way propagation delay e.g. ~540ms for GEO, ~42ms for LEO at 1200km, and ~26 ms for LEO at 600km. Based on that, the 5G-AN Packet delay budget is not applicable for 5QIs that require 5G-AN PDB lower than the sum of these values when the specific types of satellite access are used (see TS 38.300 [27]). 5QI-10 can accommodate the worst case PDB for GEO satellite type. + +NOTE: It is preferred that a value less than 64 is allocated for any new standardised 5QI of Non-GBR resource type. This is to allow for option 1 to be used as described in clause 5.7.1.3 (as the QFI is limited to less than 64). + +### 5.7.5 Reflective QoS + +#### 5.7.5.1 General + +Reflective QoS enables the UE to map UL User Plane traffic to QoS Flows without SMF provided QoS rules and it applies for IP PDU Session and Ethernet PDU Session. This is achieved by creating UE derived QoS rules in the UE based on the received DL traffic. It shall be possible to apply Reflective QoS and non-Reflective QoS concurrently within the same PDU Session. + +For a UE supporting Reflective QoS functionality, the UE shall create a UE derived QoS rule for the uplink traffic based on the received DL traffic if Reflective QoS function is used by the 5GC for some traffic flows. The UE shall use the UE derived QoS rules to determine mapping of UL traffic to QoS Flows. + +If the 3GPP UE supports Reflective QoS functionality, the UE should indicate support of Reflective QoS to the network (i.e. SMF) for every PDU Session. For PDU Sessions established in EPS and PDU Sessions transferred from EPS without N26 interface, the UE indicates Reflective QoS support using the PDU Session Establishment procedure. After the first inter-system change from EPS to 5GS for PDU Sessions established in EPS and transferred from EPS with N26 interface, the UE indicates Reflective QoS support using the PDU Session Modification procedure as described in clause 5.17.2.2.2. The UE as well as the network shall apply the information whether or not the UE indicated support of Reflective QoS throughout the lifetime of the PDU Session. + +NOTE: The logic driving a supporting UE under exceptional circumstances to not indicate support of Reflective QoS for a PDU Session is implementation dependent. + +Under exceptional circumstances, which are UE implementation dependent, the UE may decide to revoke previously indicated support for Reflective QoS using the PDU Session Modification procedure. In such a case, the UE shall delete all derived QoS rules for this PDU Session and the network shall stop any user plane enforcement actions related to Reflective QoS for this PDU Session. In addition, the network may provide signalled QoS rules for the SDFs for which Reflective QoS was used before. The UE shall not indicate support for Reflective QoS for this PDU Session for the remaining lifetime of the PDU Session. + +If under the same exceptional circumstances mentioned above and while NAS level MM or SM congestion control timer is running, the UE needs to revoke a previously indicated support for Reflective QoS, the UE performs PDU Session Release procedure that is exempt from MM and SM congestion control as defined in clause 5.19.7. + +#### 5.7.5.2 UE Derived QoS Rule + +The UE derived QoS rule contains following parameters: + +- One UL Packet Filter (in the Packet Filter Set as defined in clause 5.7.6); +- QFI; +- Precedence value (see clause 5.7.1.9). + +Upon receiving DL packet, one UL Packet Filter derived from the received DL packet as described in this clause is used to identify a UE derived QoS rule within a PDU Session. + +For PDU Session of IP type, the UL Packet Filter is derived based on the received DL packet as follows: + +- When Protocol ID / Next Header is set to TCP or UDP, by using the source and destination IP addresses, source and destination port numbers, and the Protocol ID / Next Header field itself. +- When Protocol ID / Next Header is set to UDP, if the received DL packet is UDP-encapsulated IPSec protected packet, by using the source and destination IP addresses, source and destination port numbers, the Security Parameter Index, and the Protocol ID / Next Header field itself. In this case, if an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL packet exists and the SPI of the uplink IPSec SA is known to the NAS layer, then the UL Packet Filter contains an SPI of the uplink IPSec SA. +- When Protocol ID / Next Header is set to ESP, by using the source and destination IP addresses, the Security Parameter Index, and the Protocol ID / Next Header field itself. If the received DL packet is an IPSec protected packet, and an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL packet exists and the SPI of the uplink IPSec SA is known to the NAS layer, then the UL Packet Filter contains an SPI of the uplink IPSec SA. + +NOTE 1: In this Release of the specification for PDU Sessions of IP type the use of Reflective QoS is restricted to service data flows for which Protocol ID / Next Header is set to TCP, UDP or ESP. + +NOTE 2: The UE does not verify whether the downlink packets with RQI indication match the restrictions on Reflective QoS. + +NOTE 3: How to determine the received DL packet is UDP-encapsulated IPSec protected packet is defined in RFC 3948 [138]. UDP encapsulation for ESP is used when a NAT is detected, and there can be different Security Parameter Indexes within the same IP-tuples. + +NOTE 4: Despite the indication of support for Reflective QoS, the UE might not be able to derive QoS Rules for ESP IPsec packets and UDP-encapsulated IPsec packets, if uplink IPsec SA corresponding to a downlink IPsec SA of the SPI in the DL packet exists and the SPI of the uplink IPsec SA is not known to the NAS layer. + +For PDU Session of Ethernet type the UL Packet Filter is derived based on the received DL packet by using the source and destination MAC addresses, the Ethertype on received DL packet is used as Ethertype for UL packet. In the case of presence of IEEE Std 802.1Q [98], the VID and PCP in IEEE Std 802.1Q [98] header(s) of the received DL packet is also used as the VID and PCP field for the UL Packet Filter. When double IEEE Std 802.1Q [98] tagging is used, only the outer (S-TAG) is taken into account for the UL Packet Filter derivation. + +NOTE 5: In this Release of the specification for PDU Sessions of Ethernet type the use of Reflective QoS is restricted to service data flows for which 802.1Q [98] tagging is used. + +The QFI of the UE derived QoS rule is set to the value received in the DL packet. + +When Reflective QoS is activated the precedence value for all UE derived QoS rules is set to a standardised value. + +#### 5.7.5.3 Reflective QoS Control + +Reflective QoS is controlled on per-packet basis by using the Reflective QoS Indication (RQI) in the encapsulation header on N3 (and N9) reference point together with the QFI and together with a Reflective QoS Timer (RQ Timer) value that is either signalled to the UE upon PDU Session Establishment (or upon PDU Session Modification as described in clause 5.17.2.2.2) or set to a default value. The RQ Timer value provided by the core network is at the granularity of PDU Session (the details are specified in TS 24.501 [47]). + +When the 5GC determines that Reflective QoS has to be used for a specific SDF belonging to a QoS Flow, the SMF shall provide the RQA (Reflective QoS Attribute) within the QoS Flow's QoS profile to the NG-RAN on N2 reference point unless it has been done so before. When the RQA has been provided to the NG-RAN for a QoS Flow and the 5GC determines that the QoS Flow carries no more SDF for which Reflective QoS has to be used, the SMF should signal the removal of the RQA (Reflective QoS Attribute) from the QoS Flow's QoS profile to the NG-RAN on N2 reference point. + +NOTE 1: The SMF could have a timer to delay the sending of the removal of the RQA. This would avoid signalling to the RAN in the case of new SDFs subject to Reflective QoS are bound to this QoS Flow in the meantime. + +When the 5GC determines to use Reflective QoS for a specific SDF, the SMF shall ensure that the UPF applies the RQI marking (e.g. by setting the indication to use Reflective QoS in the QER associated with the DL PDR if not already set) for this SDF. The SMF shall also ensure that the uplink packets for this SDF can be received by the UPF from the QoS Flow to which the DL PDR of the SDF is associated with as specified in TS 29.244 [65], e.g. by generating a new UL PDR for this SDF for that QoS Flow and providing it to the UPF. + +When the UPF is instructed by the SMF to apply RQI marking, the UPF shall set the RQI in the encapsulation header on the N3 (or N9) reference point for every DL packet corresponding to this SDF. + +When an RQI is received by (R)AN in a DL packet on N3 reference point, the (R)AN shall indicate to the UE the QFI and the RQI of that DL packet. + +Upon reception of a DL packet with RQI: + +- if a UE derived QoS rule with a Packet Filter corresponding to the DL packet does not already exist, + - the UE shall create a new UE derived QoS rule with a Packet Filter corresponding to the DL packet (as described in clause 5.7.5.2); and + - the UE shall start, for this UE derived QoS rule, a timer set to the RQ Timer value. +- otherwise, + - the UE shall restart the timer associated to this UE derived QoS rule; and + - if the QFI associated with the downlink packet is different from the QFI associated with the UE derived QoS rule, the UE shall update this UE derived QoS rule with the new QFI. + +NOTE 2: Non-3GPP ANs does not need N2 signalling to enable Reflective QoS. Non 3GPP accesses are expected to send transparently the QFI and RQI to the UE. If the UPF does not include the RQI, no UE derived QoS rule will be generated. If RQI is included to assist the UE to trigger an update of the UE derived QoS rule, the reception of PDU for a QFI restarts the RQ Timer. + +Upon timer expiry associated with a UE derived QoS rule the UE deletes the corresponding UE derived QoS rule. + +When the 5GC determines not to use Reflective QoS for a specific SDF any longer: + +- The SMF shall ensure that the UPF stops applying RQI marking as specified in TS 29.244 [65] (e.g. by removing the indication to use Reflective QoS from the QER associated with the DL PDR) for this SDF. +- When the UPF receives this instruction to stop applying RQI marking, the UPF shall no longer set the RQI in the encapsulation header on the N3 (or N9) reference point DL packets corresponding to this SDF. +- The SMF shall also ensure that, after an operator configurable time, the uplink packets for this SDF will not be accepted by the UPF over the QoS Flow on which Reflective QoS was applied for this SDF as specified in TS 29.244 [65], e.g. by removing the UL PDR for this SDF from that QoS Flow. + +NOTE 3: The operator configurable time has to be at least as long as the RQ Timer value to ensure that no UL packet would be dropped until the UE derived QoS rule is deleted by the UE. + +When the 5GC determines to change the binding of the SDF while Reflective QoS is used for this SDF, the SMF shall ensure that the uplink packets for this SDF are accepted over the newly bound QoS Flow and, for an operator configurable time, over the previously bound QoS Flow. + +### 5.7.6 Packet Filter Set + +#### 5.7.6.1 General + +The Packet Filter Set is used in the QoS rule and the PDR to identify one or more packet (IP or Ethernet) flow(s). + +NOTE 1: A QoS Flow is characterised by PDR(s) and QoS rule(s) as described in clause 5.7.1.1. + +NOTE 2: DL Packet Filter in a Packet Filter Set of a QoS rule may be needed by the UE e.g. for the purpose of IMS precondition. + +The Packet Filter Set may contain one or more Packet Filter(s). Every Packet Filter is applicable for the DL direction, the UL direction or both directions. + +NOTE 3: The Packet Filter in the Packet Filter Set of the default QoS rule that allows all UL traffic (also known as match-all Packet Filter) is described in TS 24.501 [47]. + +There are two types of Packet Filter Set, i.e. IP Packet Filter Set, and Ethernet Packet Filter Set, corresponding to those PDU Session Types. + +#### 5.7.6.2 IP Packet Filter Set + +For IP PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of: + +- Source/destination IP address or IPv6 prefix. +- Source / destination port number. +- Protocol ID of the protocol above IP/Next header type. +- Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask. +- Flow Label (IPv6). +- Security parameter index. +- Packet Filter direction. + +NOTE 1: A value left unspecified in a Packet Filter matches any value of the corresponding information in a packet. + +NOTE 2: An IP address or Prefix may be combined with a prefix mask. + +NOTE 3: Port numbers may be specified as port ranges. + +#### 5.7.6.3 Ethernet Packet Filter Set + +For Ethernet PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of: + +- Source/destination MAC address. +- Ethertype as defined in IEEE 802.3 [131]. +- Customer-VLAN tag (C-TAG) and/or Service-VLAN tag (S-TAG) VID fields as defined in IEEE Std 802.1Q [98]. +- Customer-VLAN tag (C-TAG) and/or Service-VLAN tag (S-TAG) PCP/DEI fields as defined in IEEE Std 802.1Q [98]. +- IP Packet Filter Set, in the case that Ethertype indicates IPv4/IPv6 payload. +- Packet Filter direction. + +NOTE 1: The MAC address may be specified as address ranges. + +NOTE 2: A value left unspecified in a Packet Filter matches any value of the corresponding information in a packet. + +### 5.7.7 PDU Set QoS Parameters + +#### 5.7.7.1 General + +PDU Set QoS Parameters are used to support PDU Set based QoS handling in the NG-RAN. At least one PDU Set QoS Parameter shall be sent to the NG-RAN to enable PDU Set based QoS handling. + +The following PDU Set QoS Parameters are specified: + +1. PDU Set Delay Budget (PSDB). +2. PDU Set Error Rate (PSER). +3. PDU Set Integrated Handling Information (PSIHI). + +For a given QoS Flow, the values of PSDB, PSER and PSIHI can be different for UL and DL. + +The QoS Profile may include the PDU Set QoS Parameters described in this clause (see clause 5.7.1.2) for UL and/or DL direction. The PCF determines the PDU Set QoS Parameters based on information provided by AF and/or local configuration. The PDU Set QoS parameters are sent to the SMF as part of PCC rule. The SMF sends them to NG-RAN as part of the QoS Profile. + +If the NG-RAN receives PDU Set QoS Parameters, it enables the PDU Set based QoS handling and applies PDU Set QoS Parameters as described in TS 38.300 [27], TS 38.413 [34] and TS 38.331 [51]. + +#### 5.7.7.2 PDU Set Delay Budget + +The PDU Set Delay Budget (PSDB) defines an upper bound for the delay that a PDU Set may experience for the transfer between the UE and the N6 termination point at the UPF, i.e. the duration between the reception time of the first PDU (at the N6 termination point for DL or the UE for UL) and the time when all PDUs of a PDU Set have been successfully received (at the UE for DL or N6 termination point for UL). PSDB applies to the DL PDU Set received by the PSA UPF over the N6 interface, and to the UL PDU Set sent by the UE. + +NOTE: To enable support for PSDB, it is required that a maximum inter arrival time between the first received PDU and the last received PDU of a PDU Set complies with SLA. This maximum inter arrival time does not exceed PSDB. NG-RAN behaviour when the SLA is not fulfilled is out of scope of this specification. + +A QoS Flow is associated with at most one PDU Set Delay Budget value per direction. PSDB is an optional parameter that may be provided by the PCF. The provided PSDB can be used by the NG-RAN to support the configuration of scheduling and link layer functions. + +When the PSDB is available, the PSDB supersedes the PDB for the given QoS Flow. + +The AN PSDB is derived at NG-RAN by subtracting CN PDB (as described in clause 5.7.3.4) from the PSDB. + +#### 5.7.7.3 PDU Set Error Rate + +The PDU Set Error Rate (PSER) defines an upper bound for the rate of PDU Sets that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). Thus, the PSER defines an upper bound for a rate of non-congestion related PDU Set losses. The purpose of the PSER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP access). + +NOTE 1: In this Release, a PDU Set is considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully. + +NOTE 2: How RAN enforces PSER is up to RAN implementation. + +A QoS Flow is associated with at most one PDU Set Error Rate value per direction. PSER is an optional parameter. If the PSER is available, the PSER supersedes the PER. + +#### 5.7.7.4 PDU Set Integrated Handling Information + +The PDU Set Integrated Handling Information (PSIHI) indicates whether all PDUs of the PDU Set are needed for the usage of the PDU Set by the application layer in the receiver side. PSIHI is an optional parameter. A QoS Flow is associated with at most one PSIHI value per direction. + +## 5.8 User Plane Management + +### 5.8.1 General + +User Plane Function(s) handle the user plane path of PDU Sessions. 3GPP specifications support deployments with a single UPF or multiple UPFs for a given PDU Session. UPF selection is performed by SMF. The details of UPF selection is described in clause 6.3.3. The number of UPFs supported for a PDU Session is unrestricted. + +For an IPv4 type PDU Session or an IPv6 type PDU Session without multi-homing or an IPv4v6 type PDU Session, when multiple PDU Session Anchors are used (due to UL CL being inserted), only one IPv4 address and/or IPv6 prefix is allocated for the PDU Session. For an IPv6 multi-homed PDU Session there are multiple IPv6 prefixes allocated for the PDU Session as described in clause 5.6.4.3. + +If the SMF had requested the UPF to proxy ARP or IPv6 Neighbour Solicitation for an Ethernet DNN, the UPF should respond to the ARP or IPv6 Neighbour Solicitation Request, itself. + +Deployments with one single UPF used to serve a PDU Session do not apply to the Home Routed case and may not apply to the cases described in clause 5.6.4. + +Deployments where a UPF is controlled either by a single SMF or multiple SMFs (for different PDU Sessions) are supported. + +UPF traffic detection capabilities may be used by the SMF in order to control at least following features of the UPF: + +- Traffic detection (e.g. classifying traffic of IP type, Ethernet type, or unstructured type) +- Traffic reporting (e.g. allowing SMF support for charging). + +- QoS enforcement (The corresponding requirements are defined in clause 5.7). +- Traffic routing (e.g. as defined in clause 5.6.4. for UL CL or IPv6 multi-homing). + +### 5.8.2 Functional Description + +#### 5.8.2.1 General + +This clause contains detailed functional descriptions for some of the functions provided by the UPF. It is described how the SMF instructs its corresponding UP function and which control parameters are used. + +#### 5.8.2.2 UE IP Address Management + +##### 5.8.2.2.1 General + +The UE IP address management includes allocation and release of the UE IP address as well as renewal of the allocated IP address, where applicable. + +The UE shall perform the association of the application to a new PDU Session described in clause 6.1.2.2.1 of TS 23.503 [45], with the following considerations: + +- If there is a matching URSP rule, except the URSP rule with the "match all" Traffic descriptor, or a matching UE Local Configuration containing a PDU Session Type of "IPv4", "IPv6" or "IPv4v6", then the UE shall set the requested PDU Session Type to the PDU Session Type contained in the matching URSP rule or in the matching UE Local Configuration, if this PDU Session Type is supported by the UE's IP stack capabilities. Detailed operation is described in TS 24.526 [110]. +- Otherwise, if a URSP Rule with the "match all" Traffic descriptor exists, the UE shall set the requested PDU Session Type to the PDU Session Type contained in the "match all" URSP Rule, if this PDU Session Type is supported by the UE's IP stack capabilities. Detailed operation is described in TS 24.526 [110]. +- Otherwise, the UE shall set the requested PDU Session Type during the PDU Session Establishment procedure based on its IP stack capabilities as follows: + - A UE which supports IPv6 and IPv4 shall set the requested PDU Session Type "IPv4v6". + - A UE which supports only IPv4 shall request for PDU Session Type "IPv4". + - A UE which supports only IPv6 shall request for PDU Session Type "IPv6". + - When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall request for PDU Session Type "IPv4v6". + +The SMF selects PDU Session Type of the PDU Session as follows: + +- If the SMF receives a request with PDU Session Type set to "IPv4v6", the SMF selects either PDU Session Type "IPv4" or "IPv6" or "IPv4v6" based on DNN configuration, subscription data and operator policies. +- If the SMF receives a request for PDU Session Type "IPv4" or "IPv6" and the requested IP version is supported by the DNN the SMF selects the requested PDU Session type. + +In its answer to the UE, the SMF may indicate the PDU Session Types not allowed for the combination of (DNN, S-NNSAI). In this case, the UE shall not request another PDU Session to the same (DNN, S-NNSAI) for PDU Session Types indicated as not allowed by the network. In the case that the initial PDU Session was established with a PDU Session Type and the UE needs another single IP version PDU Session Type, the UE may initiate another PDU Session Establishment procedure to this (DNN, S-NNSAI) in order to activate a second PDU session with that PDU Session Type. + +An SMF shall ensure that the IP address management procedure is based on the selected PDU Session Type. If IPv4 PDU Session Type is selected, an IPv4 address is allocated to the UE. Similarly, if IPv6 PDU Session type is selected, an IPv6 prefix is allocated. If IPv4v6 PDU Session Type is selected, both an IPv4 address and an IPv6 prefix are allocated. For Roaming case, the SMF in this clause refers to the SMF controlling the UPF(s) acting as PDU Session + +Anchor. i.e. H-SMF in home routed case and V-SMF in local breakout case. For home routed case, V-SMF forwards the PDU Session Type requested by UE to H-SMF without interpreting it. V-SMF sends back to UE the PDU Session Type selected by H-SMF. The SMF shall process the UE IP address management related messages, maintain the corresponding state information and provide the response messages to the UE. + +The 5GC and UE support the following mechanisms: + +- a. During PDU Session Establishment procedure, the SMF sends the IP address to the UE via SM NAS signalling. The IPv4 address allocation and/or IPv4 parameter configuration via DHCPv4 (according to RFC 2131 [9]) can also be used once PDU Session is established. +- b. /64 IPv6 prefix allocation shall be supported via IPv6 Stateless Auto-configuration according to RFC 4862 [10], if IPv6 is supported. The details of Stateless IPv6 Address Autoconfiguration are described in clause 5.8.2.2.3. IPv6 parameter configuration via Stateless DHCPv6 (according to RFC 8415 [182]) may also be supported. IPv6 Prefix Delegation using DHCPv6 may be supported for allocating additional IPv6 prefixes for a PDU Session. The details of Prefix Delegation are described in clause 5.8.2.2.4. + +For scenarios with RG connecting to 5GC, additional features for IPv6 address allocation and IPv6 prefix delegation are supported, as described in TS 23.316 [84]. + +To allocate the IP address via DHCPv4, the UE may indicate to the network within the Protocol Configuration Options that the UE requests to obtain the IPv4 address with DHCPv4, or obtain the IP address during the PDU Session Establishment procedure. This implies the following behaviour both for static and dynamic address allocation: + +- The UE may indicate that it requests to obtain an IPv4 address as part of the PDU Session Establishment procedure. In such a case, the UE relies on the 5GC network to provide IPv4 address to the UE as part of the PDU Session Establishment procedure. +- The UE may indicate that it requests to obtain the IPv4 address after the PDU Session Establishment procedure by DHCPv4. That is, when the 5GC network supports DHCPv4 and allows that, it does not provide the IPv4 address for the UE as part of the PDU Session Establishment procedure. The network may respond to the UE by setting the allocated IPv4 Address to 0.0.0.0. After the PDU Session Establishment procedure is completed, the UE uses the connectivity with the 5GC and initiates the IPv4 address allocation on its own using DHCPv4. However, if the 5GC network provides IPv4 address to the UE as part of the PDU Session Establishment procedure, the UE should accept the IPv4 address indicated in the PDU Session Establishment procedure. +- If the UE sends no IP Address Allocation request, the SMF determines whether DHCPv4 is used between the UE and the SMF or not, based on per DNN configuration. + +If dynamic policy provisioning is deployed, and the PCF was not informed of the IPv4 address at PDU Session Establishment procedure, the SMF shall inform the PCF about an allocated IPv4 address. If the IPv4 address is released, the SMF shall inform the PCF about the de-allocation of an IPv4 address. + +In order to support DHCP based IP address configuration, the SMF shall act as the DHCP server towards the UE. The PDU Session Anchor UPF does not have any related DHCP functionality. The SMF instructs the PDU Session Anchor UPF serving the PDU Session to forward DHCP packets between the UE and the SMF over the user plane. + +When DHCP is used for external data network assigned addressing and parameter configuration, the SMF shall act as the DHCP client towards the external DHCP server. The UPF does not have any related DHCP functionality. In the case of DHCP server on the external data network, the SMF instructs a UPF with N6 connectivity to forward DHCP packets between the UE and the SMF and the external DHCP server over the user plane. + +The 5GC may also support the allocation of a static IPv4 address and/or a static IPv6 prefix based on subscription information in the UDM or based on the configuration on a per-subscriber, per-DNN basis and per-S-NSSAI. + +If the static IP address/prefix is stored in the UDM, during PDU Session Establishment procedure, the SMF retrieves this static IP address/prefix from the UDM. If the static IP address/prefix is not stored in the UDM subscription record, it may be configured on a per-subscriber, per-DNN and per-S-NSSAI basis in the DHCP/DN-AAA server and the SMF retrieves the IP address/prefix for the UE from the DHCP/DN-AAA server. This IP address/prefix is delivered to the UE in the same way as a dynamic IP address/prefix. It is transparent to the UE whether the PLMN or the external data network allocates the IP address and whether the IP address is static or dynamic. + +For IPv4 or IPv6 or IPv4v6 PDU Session Type, during PDU Session Establishment procedure, the SMF may receive a Subscriber's IP Index from the UDM. If the UE IP address/prefix was not already allocated and provided to PCF when SMF initiates the SM policy association, the SMF may receive a Subscribers IP Index from the PCF. If the SMF + +received a Subscriber's IP index from both UDM and PCF, the SMF shall apply the Subscriber's IP Index received from the PCF. The SMF may use the Subscriber's IP Index to assist in selecting how the IP address is to be allocated when multiple allocation methods, or multiple instances of the same method are supported. In the case of Home Routed roaming, the H-SMF may receive the IP index from the H-PCF. + +**NOTE:** The IP Index can e.g. be used to select between different IP pools, including between IP pools with overlapping private address range. To support deployments with overlapping private IPv4 address, the IP domain corresponding to IP index can also be provided from UDM to SMF as part of the subscription data and then provided to PCF. + +When Static IP addresses for a PDU session are not used, the actual allocation of the IP Address(es) for a PDU Session may use any of the following mechanisms: + +- The SMF allocates the IP address from a pool that corresponds to the PDU Session Anchor (UPF) that has been selected +- The UE IP address is obtained from the UPF. In that case the SMF shall interact with the UPF via N4 procedures to obtain a suitable IP address. The SMF provides the UPF with the necessary information allowing the UPF to derive the proper IP address (e.g. the network instance). +- In the case that the UE IP address is obtained from the external data network, additionally, the SMF shall also send the allocation, renewal and release related request messages to the external data network, i.e. DHCP/DN-AAA server, and maintain the corresponding state information. The IP address allocation request sent to DHCP/DN-AAA server may include the IP address pool ID to identify which range of IP address is to be allocated. In this case the SMF is provisioned with separate IP address pool ID(s), and the mapping between IP address pool ID and UPF Id, DNN, S-NSSAI, IP version. The provision is done by OAM or during the N4 Association Setup procedure. + +A given IP address pool is controlled by a unique entity (either the SMF or the UPF or an external server). The IP address managed by the UPF can be partitioned into multiple IP address pool partition(s), i.e. associated with multiple IP address pool ID(s). + +When the SMF is configured to obtain UE IP addresses from the UPF, the SMF may select a UPF based upon support of this feature. The SMF determines whether the UPF supports this feature via NRF or via N4 capability negotiation during N4 Association Setup. If no appropriate UPF support the feature, the SMF may allocate UE IP addresses, if configured to do so. + +The IP address/prefix is released by the SMF (e.g. upon release of the PDU Session), likewise the UPF considers that any IP address it has allocated within a N4 session are released when this N4 session is released. + +UPF may use NAT between the UE and the Data Network, and thus the 5GC allocated (private) UE IP address may not be visible on the N6 reference point. + +##### 5.8.2.2.2            Routing rules configuration + +When the UE has an IPv6 multi-homed PDU Session the UE selects the source IPv6 prefix according to IPv6 multi-homed routing rules pre-configured in the UE or received from network. IPv6 multi-homed routing rules received from the network have a higher priority than IPv6 multi-homed routing rules pre-configured in the UE + +The SMF can generate the IPv6 multi-homed routing rules for a UE based on local configuration or dynamic PCC rules received from the PCF as defined in TS 23.503 [45]. If dynamic PCC is deployed, the SMF generates the IPv6 multi-home routing rules for a source IPv6 prefix based on the SDF Templates of those PCC rules which contain the DNAI corresponding to the newly assigned IPv6 prefix. The SMF can send IPv6 multi-homed routing rules to the UE to influence the source IPv6 prefix selection in IPv6 Router Advertisement (RA) messages according to RFC 4191 [8] at any time during the lifetime of the IPv6 multi-homed PDU Session. Such messages are sent via the UPF. + +**NOTE:** For multiple IPv4 PDU Session and multiple IPv6 PDU Session cases, routing rule based PDU Session selection is not specified in this Release of the specification. + +##### 5.8.2.2.3            The procedure of Stateless IPv6 Address Autoconfiguration + +If Stateless IPv6 Address Autoconfiguration is used for IPv6 address allocation to the UE, after PDU Session Establishment the UE may send a Router Solicitation message to the SMF to solicit a Router Advertisement message. + +The SMF sends a Router Advertisement message (solicited or unsolicited) to the UE. The Router Advertisement messages shall contain the IPv6 prefix. + +After the UE has received the Router Advertisement message, it constructs a full IPv6 address via IPv6 Stateless Address Autoconfiguration in accordance with RFC 4862 [10]. To ensure that the link-local address generated by the UE does not collide with the link-local address of the UPF and the SMF, the SMF shall provide an interface identifier (see RFC 4862 [10]) to the UE and the UE shall use this interface identifier to configure its link-local address. For Stateless Address Autoconfiguration however, the UE can choose any interface identifier to generate IPv6 addresses, other than link-local, without involving the network. However, the UE shall not use any identifiers defined in TS 23.003 [19] as the basis for generating the interface identifier. For privacy, the UE may change the interface identifier used to generate full IPv6 address, as defined in TS 23.221 [23] without involving the network. Any prefix that the SMF advertises to the UE is globally unique. The SMF shall also record the relationship between the UE's identity (SUPI) and the allocated IPv6 prefix. Because any prefix that the SMF advertises to the UE is globally unique, there is no need for the UE to perform Duplicate Address Detection for any IPv6 address configured from the allocated IPv6 prefix. Even if the UE does not need to use Neighbor Solicitation messages for Duplicate Address Detection, the UE may, for example, use them to perform Neighbor Unreachability Detection towards the SMF, as defined in RFC 4861 [54]. Therefore, the SMF shall respond with a Neighbor Advertisement upon receiving a Neighbor Solicitation message from the UE. + +In IPv6 multi-homing PDU session, SMF shall not allocate an interface identifier when a new IPv6 prefix allocated corresponding to the new PDU Session Anchor. + +The above IPv6 related messages (e.g. Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement) are transferred between the SMF and UE via the UPF(s). If the Control Plane CIoT 5GS Optimisation is enabled for a PDU session, the above IPv6 related messages are transferred between the SMF and UE via the AMF after PDU Session Establishment, see clauses 4.3.2.2.1 and 4.3.2.2.2 of TS 23.502 [3], using the Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedures. + +##### 5.8.2.2.4 IPv6 Prefix Delegation via DHCPv6 + +Optionally, a single network prefix shorter than the default /64 prefix may be assigned to a PDU Session. In this case, the /64 default prefix used for IPv6 stateless autoconfiguration will be allocated from this network prefix; the remaining address space from the network prefix can be delegated to the PDU Session using prefix delegation after the PDU Session establishment and IPv6 prefix allocation via IPv6 stateless address autoconfiguration as defined in clause 5.8.2.2.3. + +Depending on configuration, the SMF may obtain the prefix from a locally provisioned pool, from the PSA UPF or from the external DN. + +The address space provided is maintained as an IPv6 address space pool available to the PDU Session for DHCPv6 IPv6 prefix requests with the exclusion of the IPv6 prefix that is allocated to the PDU Session during PDU Session establishment as defined in clause 5.8.2.2.3. The total IPv6 address space available for the PDU Session (UE PDU Session prefix and UE PDU Session IPv6 address space pool) shall be possible to aggregate into one IPv6 prefix that will represent all IPv6 addresses that the UE may use. + +If the UE had indicated that it supports prefix exclusion and the prefix to be delegated to the UE includes the /64 prefix that was allocated to the PDU Session, the SMF shall utilise the prefix exclusion feature as specified for DHCPv6 Prefix Delegation in IETF RFC 6603 [162]. + +**NOTE:** Support of the IPv6 prefix delegation in the SMF is assumed to be ensured by the operator e.g. by configuring specific DNN/S-NSSAI for PDU Sessions that are used by UEs that utilize IPv6 prefix delegation. + +The UE uses DHCPv6 to request additional IPv6 prefixes (i.e. prefixes in addition to the default prefix) from the SMF after completing stateless IPv6 address autoconfiguration procedures. The UE acts as a "Requesting Router" as described in IETF RFC 8415 [163] and inserts one or more IA\_PD option(s) into a DHCPv6 Solicit message sent from the UE to the SMF via the user plane and the UPF. The SMF acts as the DHCP server and fulfils the role of a "Delegating Router" according to IETF RFC 8415 [163]. The UE optionally includes the RAPID\_COMMIT option in the DHCPv6 Solicit message to trigger two-message DHCPv6 procedure instead of the four-message DHCPv6 procedure. The UE shall include OPTION\_PD\_EXCLUDE option code in an OPTION\_ORO option to indicate support for prefix exclusion. In response to the DHCPv6 Solicit message, the UE receives a DHCPv6 Reply message with one or more IA\_PD prefix(es) for every IA\_PD option that it sent in the DHCPv6 Solicit message. The SMF delegates a + +prefix excluding the default prefix with help of OPTION\_PD\_EXCLUDE. Prefix exclusion procedures shall follow IETF RFC 6603 [162]. + +For scenarios with RG connecting to 5GC, additional feature for IPv6 Prefix Delegation via DHCPv6 is defined in TS 23.316 [84]. + +#### 5.8.2.3 Management of CN Tunnel Info + +##### 5.8.2.3.1 General + +CN Tunnel Info is the Core Network address of a N3/N9 tunnel corresponding to the PDU Session. It comprises the TEID and the IP address which is used by the UPF on the N3/N9 tunnel for the PDU Session. + +The CN Tunnel Info allocation and release is performed by the UPF. The SMF shall indicate to the UPF when the UPF is required to allocate/release CN Tunnel Info. + +##### 5.8.2.3.2 Void + +##### 5.8.2.3.3 Management of CN Tunnel Info in the UPF + +The UPF shall manage the CN Tunnel Info space. When a new CN Tunnel Info is needed, the SMF shall request over N4 the UPF to allocate CN Tunnel Info for the applicable N3/N9 reference point. In response, the UPF provides CN Tunnel Info to the SMF. In the case of PDU Session Release or a UPF is removed from the user plane path of an existing PDU Session, the SMF shall request UPF to release CN Tunnel Info for the PDU Session. If the corresponding N4 Session is released the UPF releases the associated CN Tunnel Info. + +#### 5.8.2.4 Traffic Detection + +##### 5.8.2.4.1 General + +This clause describes the detection process at the UPF that identifies the packets belonging to a session, or a service data flow. + +The SMF is responsible for instructing the UP function about how to detect user data traffic belonging to a Packet Detection Rule (PDR). The other parameters provided within a PDR describe how the UP function shall treat a packet that matches the detection information. + +##### 5.8.2.4.2 Traffic Detection Information + +The SMF controls the traffic detection at the UP function by providing detection information for every PDR. + +For IPv4 or IPv6 or IPv4v6 PDU Session type, detection information is a combination of: + +- CN tunnel info. +- Network instance. +- QFI. +- IP Packet Filter Set as defined in clause 5.7.6.2. +- Application Identifier: The Application Identifier is an index to a set of application detection rules configured in UPF. +- FQDN Filter for DNS Query message. + +For Ethernet PDU Session type, detection information is a combination of: + +- CN tunnel info. +- Network instance. + +- QFI. +- Ethernet Packet Filter Set as defined in clause 5.7.6.3. + +In this Release of the specification for Unstructured PDU Session Type, the UPF does not perform-QoS Flow level traffic detection for QoS enforcement. + +Traffic detection information sent by the SMF to the UPF for a PDU Session may be associated with Network instance for detection and routing of traffic over N6. In the case of IP PDU Session Type, Network Instances can, e.g. be used by the UPF for traffic detection and routing in the case of different IP domains or overlapping IP addresses. In the case of Ethernet PDU Session Type, different Network Instances can e.g. be configured in the UPF with different ways to handle the association between N6 and the PDU Sessions. + +Based on SMF instructions, UPF may identify the PDU Sets, according to the Protocol Description in PDR, to derive the PDU Set Information for DL traffics and send it to RAN via DL GTP-U header of each PDU identified as belonging to a PDU Set. The PDU Set Information, is described in clause 5.37.5. The PDU Set identification can be done by UPF implementation or by detecting RTP/SRTP header or payload. The details of the RTP/SRTP headers, header extensions and/or payloads used to identify PDU Sets are defined in TS 26.522 [179]. + +#### 5.8.2.5 Control of User Plane Forwarding + +##### 5.8.2.5.1 General + +The SMF controls user-plane packet forwarding for traffic detected by a PDR by providing a FAR with instructions to the UPF, including: + +- Forwarding operation information; +- Forwarding target information. + +The details of the forwarding target and operation will depend on the scenario and is described below. The following forwarding functionality is required by the UPF: + +- Apply N3 /N9 tunnel related handling, i.e. encapsulation. +- Forward the traffic to/from the SMF, e.g. as described in Table 5.8.2.5.2-1. +- Forward the SM PDU DN Request Container from SMF to DN-AAA server +- Forward the traffic according to locally configured policy for traffic steering. +- Forward the traffic according to N4 rules of a 5G VN group for 5G VN group communication. +- Forward the traffic to/from the EASDF. + +Data forwarding between the SMF and UPF is transmitted on the user plane tunnel established on N4 interface, defined in TS 29.244 [65]. + +##### 5.8.2.5.2 Data forwarding between the SMF and UPF + +Scenarios for data forwarding between the SMF and UPF are defined as below: + +**Table 5.8.2.5.2-1: Scenarios for data forwarding between the SMF and UPF** + +| | Scenario description | Data forwarding direction | +|---|-----------------------------------------------------------------------------------|----------------------------------| +| 1 | Forwarding of user-plane packets between the UE and the SMF e.g. DHCP signalling. | UPF to SMF
SMF to UPF | +| 2 | Forwarding of packets between the SMF and the external DN e.g. with DN-AAA server | UPF to SMF
SMF to UPF | +| 3 | Forwarding of packets subject to buffering in the SMF. | UPF to SMF
SMF to UPF | +| 4 | Forwarding of End Marker Packets constructed by the SMF to a downstream node. | SMF to UPF | +| 5 | Forwarding of user data using Control Plane CLoT 5GS Optimisation | UPF to SMF
SMF to UPF | + +##### 5.8.2.5.3 Support of Ethernet PDU Session type + +When configuring an UPF acting as PSA for an Ethernet PDU Session Type, the SMF may instruct the UPF to route the traffic based on detected MAC addresses as follows. + +- The UPF learns the MAC address(es) connected via N6 based on the source MAC addresses of the DL traffic received on a N6 Network Instance. +- The UPF learns the MAC address(es) of UE(s) and devices connected behind, if any, based on the source MAC address contained within the UL traffic received on a PDU Session (N3/N9 interface). +- The UPF forwards DL unicast traffic (with a known destination address) on a PDU Session determined based on the source MAC address(es) used by the UE for the UL traffic. +- The UPF forwards UL unicast traffic (with a known destination address) on a port (PDU Session or N6 interface) determined based on the source MAC address(es) learned beforehand. +- In the case of multicast and broadcast traffic (if the destination MAC address is a broadcast or multicast address): + - for DL traffic received by UPF on a N6 Network Instance the UPF should forward the traffic to every DL PDU Session (corresponding to any N4 Session) associated with this Network Instance + - for uplink traffic received by UPF over a PDU session on a N3/N9 interface, the UPF should forward the traffic to the N6 interface and downlink to every PDU session (except toward the one of the incoming traffic) associated with the same N6 Network Instance +- for uplink and downlink unicast traffic received by UPF, if the destination MAC has not been learnt, the UPF should forward the traffic to every PDU session associated with the same N6 Network Instance and towards the N6 interface. In any case the traffic is not replicated on the PDU Session or the N6 interface of the incoming traffic. + +NOTE 1: The UPF can consider a PDU Session or a N6 interface to be active or inactive in order to avoid forwarding loops. User data traffic is not sent on inactive PDU sessions or inactive N6 interface. This release of the specification does not further specify how the UPF determines whether a PDU Session or N6 interface is considered active or inactive. + +NOTE 2: This release of the specification supports only a single N6 interface in a UPF associated with the N6 Network Instance. + +- if the traffic is received with a VLAN ID, the above criteria apply only towards the N6 interface or PDU session matching the same VLAN ID, unless the UPF is instructed to remove the VLAN ID in the incoming traffic. + +NOTE 3: This release of the specification supports Independent VLAN Learning (IVL) and does not support Shared VLAN Learning (SVL), as described in IEEE Std 802.1Q [98]. + +- if the destination MAC address of traffic refers to the same N6 interface or PDU session on which the traffic has been received, the frame shall be dropped. + +In order to handle scenarios where a device behind a UE is moved from a source UE to a target UE, a MAC address is considered as no longer associated with a UPF interface (source UE's PDU session) when the MAC address has not + +been detected as Source MAC address in UL traffic for a pre-defined period of time or the MAC address has been detected under a different interface (target UE's PDU Session or N6). + +NOTE 4: The UPF/NW-TT may also be provided with static filtering entries as described in clause 5.28.3. How the UPF uses the static filtering entry to achieve forwarding of Ethernet frames to one or more egress ports is up to UPF implementation. The externally observable behaviour of 5GS Bridge needs to comply with IEEE Std 802.1Q [98]. + +For ARP/IPv6 Neighbour Solicitation traffic, a SMF's request to respond to ARP/IPv6 Neighbour Solicitation based on local cache information or to redirect such traffic from the UPF to the SMF overrules the traffic forwarding rules described above. + +NOTE 5: Local policies in UPF associated with the Network Instance can prevent local traffic switching in the UPF between PDU Sessions either for unicast traffic only or for any traffic. In the case where UPF policies prevent local traffic switching for any traffic (thus for broadcast/multicast traffic) some mechanism such as responding to ARP/ND based on local cache information or local multicast group handling is needed to ensure that upper layer protocol can run on the Ethernet PDU sessions. + +The SMF may ask to get notified with the source MAC addresses used by the UE, e.g. if the PCF has subscribed to UE MAC address change notifications, as described in TS 23.503 [45]. + +In order to request the UPF to act as defined above, the SMF may, for each PDU Session corresponding to a Network Instance, set an Ethernet PDU Session Information in a DL PDR that identifies all (DL) Ethernet packets matching the PDU session. Alternatively, for unicast traffic the SMF may provide UPF with dedicated forwarding rules related with MAC addresses notified by the UPF. + +#### 5.8.2.6 Charging and Usage Monitoring Handling + +##### 5.8.2.6.1 General + +The SMF shall support interfaces towards CHF and PCF. The SMF interacts with CHF and PCF based on information received from other control plane NFs and user plane related information received from the UPF. + +QoS Flow level, PDU Session level and subscriber related information remain at the SMF, and only usage information is requested from the UPF. + +##### 5.8.2.6.2 Activation of Usage Reporting in UPF + +Triggered by the PCC rules received from the PCF or preconfigured information available at SMF, as well as from the CHF for online charging method via quota management mechanisms, the SMF shall provide Usage Reporting Rules to the UPF for controlling how usage reporting is performed. + +The SMF shall request the report of the relevant usage information for Usage Monitoring, based on Monitoring Keys and triggers which are specified in TS 23.503 [45]. Each Usage Reporting Rule requested for usage monitoring control is associated with the PDR(s) whose traffic is to be accounted under this rule. The SMF shall generate the Usage Reporting Rule for each Monitoring-key within the active PCC Rule(s), either preconfigured or received from the PCF and also shall keep the mapping between them. Multiple Usage Reporting Rules may be associated with the same PDR. + +The SMF shall request the report of the relevant usage information for offline and online charging, based on Charging keys and additional triggers which are specified in TS 32.255 [68]. Each Usage Reporting Rule requested for offline or online charging is associated with the PDR(s) whose traffic is to be accounted under this rule. The SMF shall generate the Usage Reporting Rule for each Charging key and Sponsor Identity (if applicable) within the active PCC Rule(s), either preconfigured or received from the PCF, and also shall keep the mapping between them. Multiple Usage Reporting Rules may be associated with the same PDR. + +The SMF function shall also provide reporting trigger events to the UPF for when to report usage information. The reporting trigger events (e.g. triggers, threshold information etc.) shall be supported for the PDU Session level reporting as well as on Rule level basis as determined by the SMF. The triggers may be provided as a volume, time or event to cater for the different charging/usage monitoring models supported by the TS 23.503 [45] for usage monitoring and by TS 32.255 [68] for converged offline and online charging. The SMF shall decide on the thresholds value(s) based on allowance received from PCF, CHF or based on local configuration. Other parameters for instructing the UPF to report usage information are defined in TS 29.244 [65]. + +When the PCC Rule attribute Service Data flow handling while requesting credit (specified in TS 23.503 [45]) indicates "non-blocking", the SMF shall request the report of the relevant usage information for the Charging key and Sponsor Identity (if applicable) and provide a default threshold value to the UPF while waiting for the quota from the CHF. + +In some cases, the same Usage Reporting Rule can be used for different purposes (for both usage monitoring and charging), e.g. in the case that the same set of PDR(s), measurement method, trigger event, threshold, etc. apply. Similarly a reported measurement can be used for different purposes by the SMF. + +##### 5.8.2.6.3 Reporting of Usage Information towards SMF + +The UPF shall support reporting of usage information to the SMF. The UPF shall be capable to support reporting based on different triggers, including: + +- Periodic reporting with period defined by the SMF. +- Usage thresholds provided by the SMF. +- Report on demand received from the SMF. + +The SMF shall make sure that the multiple granularity levels required by the reporting keys in the Usage Reporting rules satisfy the following aggregation levels without requiring a knowledge of the granularity levels by the UPF: + +- PDU Session level reporting; +- Traffic flow (for both charging and usage monitoring) level reporting as defined by the reporting keys in the Usage Reporting Rule (see the description above). + +Based on the mapping between Monitoring key and PCC rule stored at the SMF, the SMF shall combine the reported information with session and subscriber related information which is available at the SMF, for Usage Monitoring reporting over the corresponding Npcf interface (N7 reference point). + +Based on the mapping between Charging key and Sponsor Identity (if applicable) and PCC rule stored at the SMF, the SMF shall combine the reported information with session and subscriber related information which is available at the SMF, for offline and online charging reporting over the corresponding charging interfaces. + +This functionality is specified in TS 32.255 [68]. + +The usage information shall be collected in the UPF and reported to the SMF as defined in 5.8.2.6, based on Monitoring Keys and triggers which are specified in TS 23.503 [45]. + +#### 5.8.2.7 PDU Session and QoS Flow Policing + +ARP is used for admission control (i.e. retention and pre-emption of the new QoS Flow). The value of ARP is not required to be provided to the UPF. + +For every QoS Flow, the SMF shall determine the transport level packet marking value (e.g. the DSCP in the outer IP header) based on the 5QI, the Priority Level (if explicitly signalled) and optionally, the ARP priority level and provide the transport level packet marking value to the UPF. + +The SMF shall provide the Session-AMBR values of the PDU Session to the UPF so that the UPF can enforce the Session-AMBR of the PDU Session across all Non-GBR QoS Flows of the PDU Session. + +SMF shall provide the GFBR and MFBR value for each GBR QoS Flow of the PDU Session to the UPF. SMF may also provide the Averaging window to the UPF, if Averaging window is not configured at the UPF or if it is different from the default value configured at the UPF. + +SMF may decide to activate ECN marking for L4S by PSA UPF for the QoS Flow (see clause 5.37). In this case, the SMF shall send an ECN marking for L4S indicator to UPF. + +#### 5.8.2.8 PCC Related Functions + +##### 5.8.2.8.1 Activation/Deactivation of predefined PCC rules + +A predefined PCC rule is configured in the SMF. + +The traffic detection filters, e.g. IP Packet Filter, required in the UP function can be configured either in the SMF and provided to the UPF, as service data flow filter(s), or be configured in the UPF, as the application detection filter identified by an application identifier. For the latter case, the application identifier has to be configured in the SMF and the UPF. + +The traffic steering policy information can be only configured in the UPF, together with traffic steering policy identifier(s), while the SMF has to be configured with the traffic steering policy identifier(s). + +Policies for traffic handling in the UPF, which are referred by some identifiers corresponding to the parameters of a PCC rule, can be configured in the UPF. These traffic handling policies are configured as predefined QER(s), FAR(s) and URR(s). + +When a predefined PCC rule is activated/deactivated by the PCF, SMF shall decide what information has to be provided to the UPF to enforce the rule based on where the traffic detection filters (i.e. service data flow filter(s) or application detection filter), traffic steering policy information and the policies used for the traffic handling in the UPF are configured and where they are enforced: + +- If the predefined PCC rule contains an application identifier for which corresponding application detection filters are configured in the UPF, the SMF shall provide a corresponding application identifier to the UPF; +- If the predefined PCC rule contains traffic steering policy identifier(s), the SMF shall provide a corresponding traffic steering policy identifier(s) to the UPF; +- If the predefined PCC rule contains service data flow filter(s), the SMF shall provide them to the UPF; +- If the predefined PCC rule contains some parameters for which corresponding policies for traffic handling in the UPF are configured in the UPF, the SMF shall activate those traffic handling policies via their rule ID(s). + +The SMF shall maintain the mapping between a PCC rule received over Npcf and the flow level PDR rule(s) used on N4 interface. + +##### 5.8.2.8.2 Enforcement of Dynamic PCC Rules + +The application detection filters required in the UPF can be configured either in the SMF and provided to the UPF as the service data flow filter, or be configured in the UP function identified by an application identifier. + +When receiving a dynamic PCC rule from the PCF which contains an application identifier and/or parameters for traffic handling in the UPF: + +- if the application detection filter is configured in the SMF, the SMF shall provide it in the service data flow filter to the UPF, as well as parameters for traffic handling in the UPF received from the dynamic PCC rule; +- otherwise, the application detection filters is configured in UPF, the SMF shall provide to UPF with the application identifier and the parameters for traffic handling in the UPF as required based on the dynamic PCC rule. + +The SMF shall maintain the mapping between a PCC rule received over Npcf and the flow level PDR(s) used on N4 interface. + +##### 5.8.2.8.3 Redirection + +The uplink application's traffic redirection may be enforced either in the SMF (as specified in 5.8.2.5 Control of user plane forwarding) or directly in the UPF. The redirect destination may be provided in the dynamic PCC rule or be preconfigured, either in the SMF or in the UPF. + +When receiving redirect information (redirection enabled/disabled and redirect destination) within a dynamic PCC rule or being activated/deactivated by the PCF for the predefined redirection policies, SMF shall decide whether to provide and what information to be provided to the UPF based on where the redirection is enforced and where the redirect destination is acquired/preconfigured. When redirection is enforced in the UPF and the redirect destination is acquired from the dynamic PCC rule or is configured in the SMF, SMF shall provide the redirect destination to the UPF. When redirection is enforced in the SMF, SMF shall instruct the UPF to forward applicable user plane traffic to the SMF. + +##### 5.8.2.8.4 Support of PFD Management + +The NEF (PFDF) shall provide PFD(s) to the SMF on the request of SMF (pull mode) or on the request of PFD management from NEF (push mode), as described in TS 23.503 [45]. In addition, the NEF (PFDF) may subscribe to NWDAF to be notified or request to get PFD "Determination analytics" for known applications (as specified in TS 23.288 [86]) and may decide whether to create, update, or delete PFD(s) based on the NWDAF analytics as specified in TS 23.503 [45]. The SMF shall provide the PFD(s) to the UPF, which have active PDR(s) with the application identifier corresponding to the PFD(s). + +The SMF supports the procedures in clause 4.4.3.5 of TS 23.502 [3], for management of PFDs. PFD(s) is cached in the SMF, and the SMF maintains a caching timer associated to the PFD(s). When the caching timer expires and there's no active PCC rule that refers to the corresponding application identifier, the SMF informs the UPF to remove the PFD(s) identified by the application identifier using the PFD management message. + +When a PDR is provided for an application identifier corresponding to the PFD(s) that are not already provided to the UPF, the SMF shall provide the PFD(s) to the UPF (if there are no PFD(s) cached, the SMF retrieves them from the NEF (PFDF) as specified in TS 23.503 [45]). When any update of the PFD(s) is received from NEF (PFDF) by SMF (using "push" or "pull" mode), and there are still active PDRs in UPF for the application identifier, the SMF shall provision the updated PFD set corresponding to the application identifier to the UPF using the PFD management message. + +NOTE 1: SMF can assure not to overload N4 signalling while managing PFD(s) to the UPF, e.g. forwarding the PFD(s) to the right UPF where the PFD(s) is enforced. + +When the UPF receives the updated PFD(s) from either the same or different SMF for the same application identifier, the latest received PFD(s) shall overwrite any existing PFD(s) stored in the UPF. + +NOTE 2: For the case a single UPF is controlled by multiple SMFs, the conflict of PFD(s) corresponding to the same application identifier provided by different SMF can be avoided by operator enforcing a well-planned NEF (PFDF) and SMF/UPF deployment. + +When a PFD is removed/modified and this PFD was used to detect application traffic related to an application identifier in a PDR of an N4 session and the UPF has reported the application start to the SMF as defined in clause 4.4.2.2 of TS 23.502 [3] for the application instance corresponding to this PFD, the UPF shall report the application stop to the SMF for the corresponding application instance identifier if the removed/modified PFD in UPF results in that the stop of the application instance is not being able to be detected. + +If the PFDs are managed by local O&M procedures, PFD retrieval is not used; otherwise, the PFDs retrieved from NEF (PFDF) override any PFDs pre-configured in the SMF. When all the PFDs retrieved from the NEF (PFDF) for an application identifier are removed, the pre-configured PFDs are used. The SMF shall provide either the PFDs retrieved from NEF (PFDF) or the pre-configured PFDs for an application identifier to the UPF. + +#### 5.8.2.9 Functionality of Sending of "End marker" + +##### 5.8.2.9.0 Introduction + +Sending of "end marker" is a functionality which involve SMF and UPF in order to assist the reordering function in the Target RAN. As part of the functionality, constructing of end marker packets can either be done in the SMF or in the UPF, as described in clauses 5.8.2.9.1 and 5.8.2.9.2. Whether constructing of end marker packets is performed by SMF or UPF is determined by network configuration. + +##### 5.8.2.9.1 UPF Constructing the "End marker" Packets + +In the case of inter NG-RAN Handover procedure without UPF change, SMF shall indicate the UPF to switch the N3 path(s) by sending an N4 Session Modification Request message with the new AN Tunnel Info of NG RAN and in addition, provide an indication to the UPF to send the end marker packet(s) on the old N3 user plane path. + +On receiving this indication, the UPF shall construct end marker packet(s) and send it for each N3 GTP-U tunnel towards the source NG RAN after sending the last PDU on the old path. + +In the case of inter NG-RAN Handover procedure with change of the UPF terminating N3, the SMF shall request the UPF with N9 reference point to the UPF terminating N3 to switch the N9 user plane path(s) by sending an N4 Session + +Modification Request message (N4 session ID, new CN Tunnel Info of the UPF terminating N3) and in addition, provide an indication to this UPF to send the end marker packet(s) on the old path. + +On receiving this indication, the UPF shall construct end marker packet(s) and send it for each N9 GTP-U tunnel towards the source UPF after sending the last PDU on the old path. + +On receiving the end marker packet(s) on N9 GTP-U tunnel, source UPF shall forward the end marker packet(s) and send it for each N3 GTP-U tunnel towards the source NG RAN. + +##### 5.8.2.9.2 SMF Constructing the "End marker" Packets + +UPF referred in this clause is the UPF terminates N3 reference point. + +It is assumed that the PDU Session for the UE comprises of an UPF that acts as a PDU Session Anchor and an intermediate UPF terminating N3 reference point at the time of this Handover procedure. + +In the case of inter NG-RAN Handover procedure without UPF change, SMF shall indicate the UPF to switch the N3 path(s) by sending an N4 Session Modification Request message (N4 session ID, new AN Tunnel Info of NG RAN). After sending the last PDU on the old path, UPF shall replace the old AN Tunnel Info with the new one and responds with an N4 Session Modification Response message to acknowledge the success of path switch. + +When the path switch is finished, SMF constructs the end marker packet(s) and sends it to the UPF. UPF then forwards the packet(s) to the source NG RAN. + +In the case of inter NG-RAN Handover procedure with UPF change, SMF shall indicate the PSA UPF to switch the N9 user plane path(s) by sending an N4 Session Modification Request message (N4 session ID, new CN Tunnel Info of UPF). After sending the last PDU on the old N9 path, PSA UPF shall replace the old CN Tunnel Info with the new one and responds with an N4 Session Modification Response message to acknowledge the success of path switch. + +When the path switch is finished, SMF constructs the end marker packet(s) and sends it to PSA UPF. PSA UPF then forwards the packet(s) to the source UPF. + +#### 5.8.2.10 UP Tunnel Management + +5GC shall support per PDU Session tunnelling on N3 between (R)AN and UPF and N9 between UPFs. If there exist more than one UPF involved for the PDU Session, any tunnel(s) between UPFs (e.g. in the case of two UPFs, between the UPF that is an N3 terminating point and the UPF for PDU Session Anchor) remains established when a UE enters CM-IDLE state. In the case of downlink data buffering by UPF, when mobile terminated (MT) traffic arrives at the PDU Session Anchor UPF, it is forwarded to the UPF which buffer the data packet via N9 tunnel. See clause 5.8.3 for more details on UPF buffering. In the case of Home Routed roaming, the SMF in HPLMN is not aware of the UP activation state of a PDU Session. + +When the UP connection of the PDU Session is deactivated, the SMF may release the UPF of N3 terminating point. In that case the UPF (e.g. the Branching Point/UL CL or PDU Session Anchor) connecting to the released UPF of N3 terminating point will buffer the DL packets. Otherwise, when the UPF with the N3 connection is not released, this UPF will buffer the DL packets. + +When the UP connection of the PDU Session is activated due to a down-link data arrived and a new UPF is allocated to terminate the N3 connection, a data forwarding tunnel between the UPF that has buffered packets and the newly allocated UPF is established, so that the buffered data packets are transferred from the old UPF that has buffered packets to the newly allocated UPF via the data forwarding tunnel. + +For a PDU Session whose the UP connection is deactivated and the SMF has subscribed the location change notification, when the SMF is notified of UE's new location from the AMF and detects that the UE has moved out of the service area of the existing intermediate UPF, the SMF may decide to maintain the intermediate UPF, remove the established tunnel between UPFs (in the case of removal of the intermediate UPF) or reallocate the tunnel between UPFs (in the case of reallocation of the intermediate UPF). + +#### 5.8.2.11 Parameters for N4 session management (moved) + +The parameters used by SMF to control the functionality of the UPF as well as to inform SMF about events occurring at the UPF are described in clause 5.8.5. + +#### 5.8.2.12 Reporting of the UE MAC addresses used in a PDU Session + +For Ethernet PDU Session type, the SMF may control the UPF to report the different MAC (Ethernet) addresses used as source address of frames sent UL by the UE in a PDU Session. These MAC addresses are called UE MAC addresses. + +This control and the corresponding reporting takes place over N4. + +NOTE: This is e.g. used to support reporting of all UE MAC addresses in a PDU Session to the PCF as described in clause 5.6.10.2. + +The UPF reports the removal of a UE MAC address based on the detection of absence of traffic during an inactivity time. The inactivity time value is provided by the SMF to the UPF. + +#### 5.8.2.13 Support for 5G VN group communication + +##### 5.8.2.13.0 General + +The SMF may configure the UPF(s) to apply different traffic forwarding methods to route traffic between PDU Sessions for a single 5G VN group. For example, depending on the destination address, some packet flows may be forwarded locally, while other packet flows are forwarded via N19 and other packet flows are forwarded to N6. + +If a single SMF serves the DNN/S-NSSAI of the 5G VN group, the UPF local switching, N6-based forwarding and N19-based forwarding methods described in clause 5.29.4 are coordinated by the SMF. If an SMF set serves the DNN/S-NSSAI of the 5G VN group, implementation based mechanisms can be used between SMF(s) that are part of the SMF set for controlling the connectivity between the PSA UPFs of the UE members of the 5G VN group. + +When a 5G VN group communication is extended in a wide area, bigger than the service area of any SMF set serving the DNN/S-NSSAI of the 5G VN group, multiple SMF sets might control the PDU Sessions of the UE members of the 5G VN group. In this case, N6/N19 connectivity between PSA UPFs of the UE members of the 5G VN group controlled by different SMF sets, is achieved via OAM configuration. As a deployment option, a subset of the UPFs controlled by an SMF Set may be configured with the N6/N19 connectivity to enable 5G VN group communication across SMF Sets. N6 connectivity between PSA UPFs via a DN may also exist. + +5G VN group communication includes one to one communication and one to many communication. One to one communication supports forwarding of unicast traffic between two UEs within a 5G VN, or between a UE and a device on the DN. One to many communication supports forwarding of multicast traffic and broadcast traffic from one UE (or device on the DN) to many/all UEs within a 5G VN and devices on the DN. + +Traffic forwarding within the 5G VN group is realized by using a UPF internal interface ("5G VN internal") and a two-step detection and forwarding process. In the first step, the packets received from any 5G VN group member (via its PDU Session, via N6 or via N19) are forwarded to the UPF internal interface (i.e. Destination Interface set to "5G VN internal"). In the second step, PDRs installed at the UPF internal interface (i.e. Source Interface set to "5G VN internal") detect the packet and forward it to the respective 5G VN group member (via its PDU Session, via N6 or via N19). The details of the PDR and FAR configuration are described in the following clauses. + +For UEs belonging to the same 5G VN group and having PDU Sessions that correspond to N4 Sessions in the same PSA UPF, the following applies for traffic that is sent from one of these UEs to another one of these UEs using local switching: The incoming traffic for one PDU Session will match the corresponding N4 Session's PDR(s) of the source PDU Session (based on GTP-U header information). The traffic is then sent back to classification in that UPF (via the internal interface) and will match another N4 Session corresponding to the destination PDU Session (based on destination address in the PDU). The PDU is then forwarded to the target UE. + +If 5G VN group members' PDU Sessions are served by different PSA UPFs and N19-based forwarding is applied, the SMF creates a group-level N4 Session with each involved UPF to enable N19-based forwarding and N6-based forwarding. When the traffic is then sent back to classification in that UPF (via the internal interface) it may match group-level N4 Session corresponding to the 5G VN group (based on destination address in the PDU or a default PDR rule with match-all packet filter). The PDU is then forwarded to N6 or to the UPF indicated in the group-level N4 Session via corresponding N19 tunnel. This enables the PDU to be sent to the target group member in the other UPF or to the device in the DN. + +In the case of N19-based forwarding is not applied for a 5G VN group, group level N4 session is not required. + +If more than one 5G VN group has to be supported in the PLMN, the N4 rule attribute Network Instance is used in addition to the UPF internal interface and set to a value representing the 5G VN group. This keeps the traffic of different 5G VN groups separate from each other and thus enables isolation of the 5G VN group communication during the packet detection and forwarding process. The SMF shall provide the PDRs and FARs related to the UPF internal interface as follows whenever more than one 5G VN group has to be supported in the PLMN: + +- The FAR with Destination Interface set to "5G VN internal" shall also contain the Network Instance set to the value representing the 5G VN group. +- The PDR with Source Interface set to "5G VN internal" shall also contain the Network Instance set to the value representing the 5G VN group. + +Forwarding Ethernet unicast traffic towards the PDU Session corresponding to the Destination MAC address of an Ethernet frame may correspond: + +- either to the SMF explicitly configuring DL PDR(s) with the MAC addresses detected by the UPF on PDU Sessions and reported to the SMF; this is further described in clause 5.8.2.13.1; +- or to the SMF relying on MAC address learning in UPF as defined in clause 5.8.2.5.3. To request this UPF behaviour the SMF sets the Ethernet PDU Session Information indication in the DL PDR of the "5G VN internal" interface related with a 5G VN group. This may apply in the case that all PDU Sessions related with this 5G VN group are served by the same PSA or by multiple PSAs not inter-connected via N19. + +For Ethernet traffic on 5G-VN, in the former case above where SMF explicitly configures DL PDR with the MAC addresses detected on PDU Sessions supporting a 5G VN group, the SMF acts as a central controller which is responsible for setting up the forwarding rules in the UPFs so that it avoids forwarding loops. The SMF becomes aware of the MAC addresses in use within a 5G VN group by the UPF's reporting of the MAC addresses. The SMF is responsible to react to topology changes in the Ethernet network. Local switching without SMF involvement is not specified for a 5G-VN when different PDU Sessions related with this 5G VN group may be served by different PSA(s) connected over N19. + +NOTE: The mechanisms described above implies signalling on N4 Sessions related with a VN group each time a new MAC address is detected as used (or no more used) within a PDU Session related with this 5G VN group. Hence the usage of the solution with SMF explicitly configuring DL PDR with the MAC addresses defined in this release can raise signalling scalability issues for large VN groups with lots of devices (MAC addresses) served by PDU sessions related with this VN group. + +##### 5.8.2.13.1 Support for unicast traffic forwarding of a 5G VN + +To enable unicast traffic forwarding in a UPF, the following applies: + +- The SMF provides for each 5G VN group member's N4 Session (i.e. N4 Session corresponding to PDU Session) the following N4 rules that enable the processing of packets received from this UE. + - in order to detect the traffic, a PDR containing Source Interface set to "access side", and CN Tunnel Information set to PDU Session tunnel header (i.e. N3 or N9 GTP-U F-TEID); and + - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal". +- The SMF provides for each 5G VN group member's N4 Session (i.e. N4 session corresponding to PDU Session) the following N4 rules that enable the processing of packets towards this UE. + - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", and Destination Address set to the IP/MAC address (es) of this 5G VN group member; and + - in order to forward the traffic, a FAR containing Outer Header Creation indicating the N3/N9 tunnel information, and Destination Interface set "access side". +- If N19-based forwarding is applied, the SMF configures the group-level N4 Session for processing packets received from a N19 tunnel with the following N4 rules for each N19 tunnel. + - in order to detect the traffic, a PDR containing Source Interface set to "core side", and CN Tunnel Information set to N19 tunnel header (i.e. N19 GTP-U F-TEID); and + - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal". + +- If N19-based forwarding is applied, the SMF configures the group-level N4 Session for processing packets towards 5G VN group members anchored at other UPFs with the following N4 rules for each N19 tunnel. + - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", and Destination Address set to the IP/MAC address (es) of UEs anchored at the peer UPF of this N19 tunnel (e.g. based on the IP address range supported by the peer UPF); and + - in order to forward the traffic to a 5G VN group member anchored at another UPF via the N19 tunnel, a FAR containing Outer Header Creation indicating the N19 tunnel information, Destination Interface set to "core side". +- The SMF configures the group-level N4 Session for processing packets received from a 5G VN group member connected via N6 with the following N4 rules. + - in order to detect the traffic, a PDR containing Source Interface set to "core side", and Source Address set to the IP/MAC address (es) of this 5G VN group member; and + - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal". +- The SMF configures the group-level N4 Session for processing packets towards a 5G VN group member connected via N6 or packets towards a device residing in DN with the following N4 rules. + - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", and Destination Address set to the IP/MAC address (es) of this 5G VN group member; and + - in order to forward the traffic to the 5G VN group member or device via N6, a FAR containing Destination Interface set to "core side". +- The SMF shall update N4 rules for group-level N4 Session to enable correct forwarding of packets towards UE who's PSA UPF has been reallocated and address is unchanged. +- The SMF may also configure the following N4 rules for the group-level N4 Session to process packets with an unknown destination address: + - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", a match-all Packet Filter, and a Precedence set to the lowest precedence value; and + - in order to process the traffic, a FAR containing Destination Interface set to "core side" to route the traffic via N6 by default, or in the case of local SMF configuration that N6-based forwarding is not applied a FAR instructing the UPF to drop the traffic. + +##### 5.8.2.13.2 Support for unicast traffic forwarding update due to UE mobility + +To enable the service continuity when the PSA UPF serving the UE changed, the following applies: + +- Keep the UE address unchanged if N6-based forwarding is not used. +- Configure the UE's N4 Session with N4 rules (PDR, FAR) to detect and forward the traffic to this UE via its PDU Session tunnel(i.e. N3 tunnel) on the target PSA UPF. +- If N19-based forwarding is applied: To switch the traffic towards this UE from the source PSA UPF to the target PSA UPF for N19-based forwarding, the SMF deletes the N4 rule (PDR) that detects the traffic towards this UE in the group-level N4 Session at UPFs involved in the 5G VN group (except the source PSA UPF), then adds or updates the PDR that detects the traffic towards this UE with the FAR containing the N19 tunnel information of the target PSA UPF in the group-level N4 Session at UPFs involved in the 5G VN group (except the target PSA UPF). + +##### 5.8.2.13.3 Support for user plane traffic replication in a 5G VN + +###### 5.8.2.13.3.1 User plane traffic replication based on UPF internal functionality + +For Ethernet PDU Sessions, the SMF may instruct the UPF to route traffic to be replicated as described in clause 5.8.2.5. + +For IP PDU Session types, the SMF may instruct the UPF to manage IP multicast traffic as described in clauses 4.6.6 and 7.7.1 of TS 23.316 [84]. The UPF replicates the IP multicast traffic received from PDU Sessions or N6 interface and sends the packets over other PDU Sessions and other N6 interface subscribed to the IP Multicast groups. + +Mechanisms described in clauses 4.6.6 and 7.7.1 of TS 23.316 [84] apply to support 5G VN group communication with following clarifications: + +- These mechanisms are not limited to Wireline access and can apply on any access, +- IP Multicast traffic allowed for a PDU Session is not meant for IPTV services reachable over N6, +- IGMP /MLD signalling does not relate with STB or 5G-RG: Clauses 4.6.6 and 7.7.1 of TS 23.316 [84], apply to UE members of a 5G VN group instead of 5G-RG, and +- Clauses 7.7.1.1.2 and 7.7.1.1.4 of TS 23.316 [84] are not applicable to 5G VN groups: members of the 5G VN groups may receive any multicast traffic associated with the (DNN, S-NSSAI) of the 5G VN group. +- UPF exchange of signalling such as PIM (Protocol-Independent Multicast) may apply as defined in TS 23.316, with following clarification: + - PIM signalling is generally exchanged over N6 but may be sent towards the PDU Session supporting the source address of multicast traffic identified by IGMP / MLD signalling for Source Specific Multicast. In the case of IGMP / MLD signalling not related with Source Specific Multicast no PIM signalling is sent towards any PDU Session + +###### 5.8.2.13.3.2 + +###### User plane traffic replication based on PDRs with replication instructions + +Alternatively, for IP or Ethernet type data communication, the SMF instructs the UPF via PDRs and FARs how to replicate user plane traffic. + +The mechanism is supported in the following conditions: + +- When N19 is used, there is a full mesh of N19 tunnels between UPFs controlled by each SMF Set serving the 5G VN group; +- There is no support for forwarding a broadcast/multicast packet with source address not known to SMF/UPF. +- Each UPF supports one N6 interface instance towards the data network, or only supports N19-based forwarding without N6; +- Multicast group formation of selected members of a 5G VN for Ethernet type data communication is not described in this release of the specification. + +In this case, when the UPF receives a broadcast packet of a 5G VN group from N19 or N6, it shall distribute it to all 5G VN group members connected to this UPF. When the UPF receives a broadcast packet from a UE (source UE) via PDU Session associated with a 5G VN group, it shall distribute it to: + +- All 5G VN group members (except the source UE) connected to this UPF via local switch; and +- All 5G VN group members connected to other UPFs via N19-based forwarding or N6-based forwarding; and +- The devices on the DN via N6-based forwarding. + +To enable broadcast traffic forwarding of a 5G VN group in a UPF, the following applies: + +- The SMF provides group-level N4 Session and each 5G VN group member' N4 Session with the PDR that detect the broadcast packet sent via "internal interface". When UPF receives the broadcast packets sent via "internal interface", it matches the broadcast packet against all PDRs installed at the "internal interface". A successful matching with a PDR that detect the broadcast packet instructs the UPF to continue the lookup of the other PDRs. A matching PDR that detects the broadcast packet shall instruct the UPF to duplicate the broadcast packet and perform processing (using associated FAR, URR, QER) on the copy instead of the original packet if the broadcast packet does not satisfy the packet replication skip information, otherwise the PDR instructs the UPF to skip the processing of the broadcast packet. +- The broadcast packets received from N19 or N6 are forwarded to the UPF internal interface together with a N19 or N6 indication. + +- The SMF provides for each 5G VN group member' N4 Session (i.e. N4 session corresponding to PDU Session) the following N4 rules that enable the processing of broadcast packets towards this UE. + - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", Destination Address set to the broadcast address, the Packet replication skip information set to the IP/MAC address (es) of this 5G VN group member, and the indication to carry on matching; and + - in order to forward the traffic, a FAR containing Outer Header Creation indicating the PDU Session tunnel information, and Destination Interface set "access side". +- The SMF configures the group-level N4 Session for processing packets received from a N19 tunnel with the following N4 rules for each N19 tunnel. + - in order to detect the traffic, a PDR containing Source Interface set to "core side", Destination Address set to the broadcast address, and CN Tunnel Information set to N19 tunnel header (i.e. N19 GTP-U TEID); and + - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal", Outer Header Creation with the N19 indication. +- The SMF provides for the group-level N4 Session the following N4 rules that enable the processing of broadcast packets towards the other UPFs. + - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", Destination Address set to the broadcast address, the Packet replication skip information set to the N19 indication, and the indication to carry on matching; and + - in order to forward the traffic to each involved UPF via the corresponding N19 tunnel, a FAR containing "Duplication" instruction, Outer Header Creation indicating the N19 tunnel information, Destination Interface set to "core side". +- The SMF configures the group-level N4 Session for processing packets received from N6 with the following N4 rules. + - in order to detect the traffic, a PDR containing Source Interface set to "core side", and Destination Address set to the broadcast address; and + - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal", Outer Header Creation with the N6 indication. +- The SMF provides for the group-level N4 Session the following N4 rules that enable the processing of broadcast packets towards N6. + - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal" and Destination Address set to the broadcast address and the Packet replication skip information set to the N6 indication; and + - in order to forward the traffic to N6, a FAR containing Destination Interface set to "core side". + +In this case, to enable multicast traffic forwarding of a 5G VN group in a UPF, broadcast traffic forwarding of a 5G VN applies to multicast traffic forwarding of a 5G VN with the following modifications: + +- The SMF installs PDRs for the multicast address instead of the broadcast address. +- The PDRs and FARs are installed for PDU Sessions corresponding to the members of the multicast group. +- In addition, the SMF installs the PDR identifying IGMP/MLD signalling for each 5G VN group member' N4 Session and a URR with a Reporting Trigger set to "IGMP reporting" for IGMP or set to "MLD reporting" for MLD. Based on the IP Multicast address in "IP multicast join" or "IP multicast leave" reports received from UPF, the SMF manipulates (delete or add) the PDR identifying the multicast traffic for the reported IP Multicast address at the corresponding 5G VN group member' N4 Session, and if required at the group-level N4 Session at the UPF(s) of the 5G VN group. + +#### 5.8.2.14 Inter PLMN User Plane Security functionality + +Operators can deploy UPF(s) supporting the Inter PLMN User Plane Security (IPUPS) functionality at the border of their network to protect their networks from invalid inter PLMN N9 traffic. + +The IPUPS functionality forwards GTP-U packets (received via the N9 interface) only if they belong to an active PDU Session and are not malformed, as described in TS 33.501 [29]. + +The SMF can activate the IPUPS functionality together with other UP functionality in the same UPF, or insert a separate UPF in the UP path for the IPUPS functionality. In both cases the UPF with IPUPS functionality is controlled by the SMF via the N4 interface. + +#### 5.8.2.15 Void + +#### 5.8.2.16 Support for L2TP tunnelling on N6 + +If requested by the SMF during N4 Session Establishment, the UPF (PSA) may setup L2TP towards an L2TP network server (LNS) in the DN and tunnel the PDU Session user plane traffic in this L2TP tunnel. In this case the UPF acts as a L2TP access concentrator (LAC). + +To enable this, the SMF may provide L2TP information to the UPF, such as LNS IP address and/or LNS host name, as described in TS 29.244 [65]. This L2TP information may be configured on the SMF as part of the DNN configuration or received from the DN-AAA Server during secondary authentication/authorization, as described in clause 5.6.6. Alternatively, the L2TP tunnel parameters may be configured in the UPF Function. The L2TP tunnel parameters include necessary parameters for setting up L2TP tunnel towards the LNS (e.g. LNS address, tunnel password, etc.). + +In addition, the SMF may provide PAP/CHAP authentication information to the UPF, for use in L2TP session establishment, in case it was received from the UE in the PDU Session Establishment Request. + +When L2TP is to be used for a PDU Session, the SMF may select a UPF based upon support of this feature. The SMF determines whether the UPF supports this feature via N4 capability negotiation during N4 Association Setup or via NRF discovery. + +If SMF requests the UPF to allocate UE IP address, as described in clause 5.8.2.2.1, the UPF (LAC) may retrieve this IP address from the LNS. In addition, if the SMF requests the UPF to provide DNS address(es), the UPF (LAC) may request the LNS to provide DNS address(es) and report such DNS address(es) to the SMF. + +#### 5.8.2.17 Data exposure via Service Based interface + +The UPF may expose information by means of UPF Event Exposure service as described in TS 23.502 [3] clause 5.2.26.2, via a service-based interface directly. The NF consumers, which may receive UPF event notifications, are AF/NEF, TSNAP/TSCTSF and NWDAF/DCCF/MFAF. + +When the UPF supports the data exposure via the service based interface, it may register its NF profile to the NRF including the UPF Event Exposure services and the related Event ID(s). + +For data collection from UPF (see clause 4.15.4.5 of TS 23.502 [3]), NF consumers do the subscription to the UPF directly or indirectly via SMF. An NF consumer may subscribe to the UPF Event Exposure service directly only for data collected for "any UE" e.g. to collect user data usage information for NWDAF NF Load analytic (see clause 6.5 of TS 23.288 [86]) and if the subscription is not including any of the following parameters: AoI, traffic filtering, BSSID/SSID and Application ID. + +To alleviate the load of UPF due to frequent event notification, the event subscription may include Reporting suggestion information. The Reporting suggestion information includes Report urgency and Reporting window information. Reporting urgency information represents whether this event report can be delay tolerant, i.e. the event report can be delayed. If the Reporting urgency information indicates "delay tolerant", the Reporting window is also provided, which defines the last valid reporting time, and UPF shall report the detected event before the last valid time. Per Reporting suggestion information UPF can concatenate several notification messages to the same notification endpoint in one notification message. + +The UPF may also expose UE information by means of the Nupf\_GetUEPrivateIPAddrAndIdentifiers service as described in TS 23.502 [3] clause 5.2.26.3. An UPF which is deployed with NAPT (Network Address Port Translation) functionality may support to provide the 5GC UE IP address to NEF based on NEF request containing public IP address and port number using the Nupf\_GetUEPrivateIPAddrAndIdentifiers service as described in clause 4.15.10 of TS 23.502 [3] for AF specific UE ID retrieval. + +#### 5.8.2.18 QoS Flow related QoS monitoring and reporting + +The SMF may configure the UPF to perform QoS monitoring for a QoS Flow and to report the monitoring results with the help of the following parameters provided in the Session Reporting Rule (SRR) described in clause 5.8.5.11: + +- *QoS monitoring parameter(s)* indicating the subject of the QoS monitoring as defined in clause 5.45; +- *Reporting period* indicating the time interval in which a new measurement result and a potential report has to be available. Generally, if no measurement result is available to the UPF within the *Reporting period*, the UPF shall report a measurement failure; however, for some QoS monitoring parameters (e.g. congestion information, PDV and data rate), the measurement failure report is not applicable. +- *Reporting frequency* indicating the type of the reporting as "periodic" or "event triggered": + - If the *Reporting frequency* indicates "periodic", the UPF shall send a report each time the reporting period is over. + - If the *Reporting frequency* indicates "event triggered", a *Reporting threshold* for each parameter in the *QoS monitoring parameter(s)* and a *Minimum waiting time* are provided as well. The UPF shall send a report when the measurement result matches or exceeds the indicated *Reporting threshold*. Subsequent reports shall not be sent by the UPF during the *Minimum waiting time*. If measurement results are received during the *Minimum waiting time*, the UPF shall report the minimum and the maximum measurement result when the *Minimum waiting time* is over. +- (Optional) *Target of the reporting and Indication of direct event notification* indicating that the UPF shall send the reports to a different NF than the SMF (e.g. to the NEF/AF or the NWDAF/DCCF/MFAF). The NF is identified by a Notification Target Address and a Notification Correlation ID. The SMF can also indicate that the UPF shall send the reports to both, the NF indicated by the *Target of reporting* and to the SMF. If so, the UPF shall send the reports to the SMF as well. If the *Indication of direct event notification* is not provided, the UPF shall send the reports to the SMF. +- (Optional) *Reporting suggestion information* as defined in clause 5.8.2.17 applicable to *Target of the reporting* to reduce the UPF performance impacts. +- (Optional) *Indication of QoS Flow associated with the default QoS Rule* (see clause 4.15.4.5.1 of TS 23.502 [3]). The UPF shall forward this indication, that the QoS monitoring report is for the QoS Flow associated with the default QoS Rule, in the Nupf\_EventExposure\_Notify service operation when sending reports. + +The UPF shall send the QoS Monitoring Report as follows: + +- when the UPF sends reports to the SMF, the UPF shall use QoS Monitoring Reports as described in clause 5.8.5.12; and/or +- When the UPF sends reports to a different NF than the SMF (e.g. the NEF/AF or the NWDAF/DCCF/MFAF), the UPF shall use the Nupf\_EventExposure\_Notify service operation described in clause 5.2.26.2.2 of TS 23.502 [3]. + +#### 5.8.2.19 Explicit Buffer Management + +##### 5.8.2.19.1 General + +5GC supports buffering of UE's downlink packets for deactivated PDU Sessions. + +Support for buffering in the UPF is mandatory and optional in the SMF. + +When the UP connection of a PDU Session is deactivated, buffering in UPF can be activated by the SMF. If the SMF supports buffering capability, the SMF can decide to activate buffering in SMF instead of buffering in UPF. + +##### 5.8.2.19.2 Buffering at UPF + +When the SMF decided to activate buffering in UPF, the SMF shall inform the UPF to start buffering packets for this PDU Session. + +The SMF provides instructions to the UPF for at least the following behaviour: + +- buffer downlink packets with the following additional options: + - reporting the arrival of first downlink packet (for a QoS Flow or a service data flow), and/or + - reporting the first discarded downlink packet (for a service data flow), or +- drop downlink packets with the following additional options: + - reporting the first discarded downlink packet (for a service data flow). +- buffer uplink packets. + +When the SMF instructs the UPF for a service data flow to buffer downlink packets and to report the first discarded downlink packet, the SMF shall also instruct the UPF to report the arrival of the first downlink packet for this service data flow to enable the SMF check if this is also the first report for the QoS Flow (as described below). + +Buffering in the UPF may be configured based on timers or the amount of downlink data to be buffered. The SMF decides whether buffering timers or amount of downlink data are handled by the UPF or SMF. + +After starting buffering, when the first downlink packet (of a QoS Flow or a service data flow) arrives, UPF shall inform the SMF if it is setup to report. UPF sends a Downlink Data Report to the SMF via N4 unless specified otherwise and indicates the PDR by which the downlink packet was received. If the SMF receives a Downlink Data Report for a service data flow, the SMF shall also check if this is the first report for the QoS Flow corresponding to the PDR. If so, the SMF shall also proceed as described in clause 5.4.3.1. + +After starting buffering, when the first downlink packet (of a service data flow) in a configured period of time that has been buffered is discarded by the UPF because the configured buffering time or amount of downlink data to be buffered is exceeded, the UPF shall inform the SMF if it is setup to report. UPF sends a Downlink Data Report to the SMF via N4 and indicates the PDR by which the discarded downlink packet was received. + +A new report is sent if the SMF terminates and subsequently re-activates the buffering action at the UPF and the UPF again receives downlink packets. + +NOTE: For the notification about the downlink data delivery status "buffered" or "discarded" related to packets from a particular AF as part of the Nsmf\_EventExposure service, it is expected that a PDR with a traffic filter identifying that AF as source and a Forwarding Action rule with action "buffer" is installed. + +When the UP connection of the PDU Session is activated, the SMF updates the UPF of the change in buffering state. The buffered downlink packets, if any, are then forwarded to the (R)AN by the UPF. + +If the UP connection of the PDU Session has been deactivated for a long time, the SMF may indicate the UPF to stop buffering for this PDU Session. + +The SMF may indicate to the UPF to start or stop the buffering of uplink packets of an application associated to the PCC rule as described in clause 6.3.5 of TS 23.548 [130]. When the buffering of uplink packets is stopped the UPF shall forward all buffered uplink packets before it forwards any new uplink packets. + +##### 5.8.2.19.3 Buffering at SMF + +When the SMF supports buffering capability and the SMF decided to activate buffering in SMF for the PDU Session, the SMF shall inform the UPF to start forwarding the downlink packets towards the SMF. + +When the UP connection of the PDU Session is activated, if there are buffered downlink packets available and their buffering duration has not expired, the SMF shall forward those packets to the UPF to relay them to the UE. These packets are then forwarded by the UPF to the (R)AN. + +#### 5.8.2.20 SMF Pause of Charging + +The SMF Pause of Charging functionality is supported with the purpose that the charging and usage monitoring data in the core network more accurately reflects the downlink traffic actually sent to the (R)AN. When the amount of downlink data incoming at the UPF for a PDU Session that is in deactivated state goes above a pre-configured threshold, the pause of charging functionality ensures that data that dropped in the core network is not included in charging and usage monitoring records. + +The procedures for SMF Pause of Charging are described in TS 23.502 [3]. + +### 5.8.3 Explicit Buffer Management (moved) + +The Explicit Buffer Management is described in clause 5.8.2.19. + +### 5.8.4 SMF Pause of Charging (moved) + +The SMF Pause of Charging is described in clause 5.8.2.20. + +### 5.8.5 Parameters for N4 session management + +#### 5.8.5.1 General + +These parameters are used by SMF to control the functionality of the UPF as well as to inform SMF about events occurring at the UPF. + +The N4 session management procedures defined in clause 4.4.1 of TS 23.502 [3] will use the relevant parameters in the same way for all N4 reference points: the N4 Session Establishment procedure as well as the N4 Session Modification procedure provide the control parameters to the UPF, the N4 Session Release procedure removes all control parameters related to an N4 session, and the N4 Session Level Reporting procedure informs the SMF about events related to the PDU Session that are detected by the UPF. + +The parameters over N4 reference point provided from SMF to UPF comprises an N4 Session ID and may also contain: + +- Packet Detection Rules (PDR) that contain information to classify traffic (PDU(s)) arriving at the UPF; +- Forwarding Action Rules (FAR) that contain information on whether forwarding, dropping or buffering is to be applied to a traffic identified by PDR(s); +- Multi-Access Rules (MAR) that contain information on how to handle traffic steering, switching and splitting for a MA PDU Session; +- Usage Reporting Rules (URR) contains information that defines how traffic identified by PDR(s) shall be accounted as well as how a certain measurement shall be reported; +- QoS Enforcement Rules (QER), that contain information related to QoS enforcement of traffic identified by PDR(s); +- Session Reporting Rules (SRR) that contain information to request the UP function to detect and report events for a PDU session that are not related to specific PDRs of the PDU session or that are not related to traffic usage measurement. +- Trace Requirements; +- Port Management Information Container in 5GS; +- Bridge/Router Information. + +The N4 Session ID is assigned by the SMF and uniquely identifies an N4 session. + +If the UPF indicated support of Trace, the SMF may activate a trace session during a N4 Session Establishment or a N4 Session Modification procedure. In that case it provides Trace Requirements to the UPF. The SMF may deactivate an on-going trace session using a N4 Session Modification procedure. There shall be at most one trace session activated per N4 Session at a time. + +For the MA PDU Session, the SMF may add an additional access tunnel information during an N4 Session Modification procedure by updating MAR with addition of an FAR ID which refers to an FAR containing the additional access tunnel information for the MA PDU session for traffic steering in the UPF. For the MA PDU Session, the SMF may request Access Availability report per N4 Session, during N4 Session Establishment procedure or N4 Session Modification procedure. + +A N4 Session may be used to control both UPF and NW-TT behaviour in the UPF. A N4 session support and enable exchange of bridge/router configuration between the SMF and the UPF: + +- Information that the SMF needs for bridge/router management (clause 5.8.5.9); +- Information that 5GS transparently relays between the TSN AF or TSCTSF and the NW-TT: transparent Port Management Information Container along with the associated NW-TT port number. +- Information that 5GS transparently relays between the TSN AF or TSCTSF and the NW-TT: transparent user plane node Management Information Container (clause 5.8.5.14). + +When a N4 Session related with bridge/router management is established, the UPF allocates a dedicated port number for the PDU Session. The UPF then provides to the SMF following configuration parameters for the N4 Session: + +- port number. +- user-plane node ID. + +To support TSN, the user-plane node ID is Bridge ID. To support integration with IETF DetNet, the user-plane node ID can be Router ID. The User Plane Node ID may be pre-configured in the UPF based on deployment. + +After the N4 session has been established, the SMF and UPF may at any time exchange transparent user plane node and Port Management Information Container over a N4 session. + +#### 5.8.5.2 N4 Session Context + +N4 Session Context is identified by an N4 Session ID. An N4 Session Context is generated by SMF and UPF respectively to store the parameters related to an N4 session, including the N4 session ID and following information (see TS 29.244 [65] for an exhaustive list): + +- 1) general session related parameters such as S-NSSAI, PDU Session Type, Trace Information, APN/DNN, ATSSS Control Information; +- 2) the PDRs, URRs, QERs, BAR(s), FARs, MARs used for this N4 session; +- 3) parameters sent to support UPF statistics. + +The UPF may use parameters listed above in bullets 1) (e.g. S-NSSAI) and 2) (e.g. Network Instance in PDR/FAR(s)) for determining internal UPF resources. + +#### 5.8.5.3 Packet Detection Rule + +The following table describes the Packet Detection Rule (PDR) containing information required to classify a packet arriving at the UPF. Every PDR is used to detect packets in a certain transmission direction, e.g. UL direction or DL direction. + +##### **Table 5.8.5.3-1: Attributes within Packet Detection Rule** + +| Attribute | | Description | Comment | +|---------------------------------------------------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| N4 Session ID | | Identifies the N4 session associated to this PDR.
NOTE 5. | | +| Rule ID | | Unique identifier to identify this rule. | | +| Precedence | | Determines the order, in which the detection information of all rules is applied. | | +| Packet
Detection
Information.
NOTE 4. | Source interface | Contains the values "access side", "core side", "SMF", "N6-LAN", "5G VN internal". | Combination of UE IP address (together with Network instance, if necessary), CN tunnel info, packet filter set, application identifier, Ethernet PDU Session Information and QFI are used for traffic detection. Source interface identifies the interface for incoming packets where the PDR applies, e.g. from access side (i.e. up-link), from core side (i.e. down-link), from SMF, from N6-LAN (i.e. the DN), or from "5G VN internal" (i.e. local switch). Details like all the combination possibilities on N3, N9 interfaces are left for stage 3 decision. The FQDN or FQDN range only used for detection of plain DNS Query message (i.e. not subject to ciphering). The usage is described in TS 23.548 [130]. | +| | UE IP address | One IPv4 address and/or one IPv6 prefix with prefix length (NOTE 3). | | +| | Network instance (NOTE 1) | Identifies the Network instance associated with the incoming packet. | | +| | CN tunnel info | CN tunnel info on N3, N9 interfaces, i.e. F-TEID. | | +| | Packet Filter Set | Details see clause 5.7.6. | | +| | Application identifier | | | +| | QoS Flow ID | Contains the value of 5QI or non-standardized QFI. | | +| | Ethernet PDU Session Information | Refers to all the (DL) Ethernet packets matching an Ethernet PDU session, as further described in clause 5.6.10.2 and in TS 29.244 [65]. | | +| | Framed Route Information | Refers to Framed Routes defined in clause 5.6.14. | | +| | FQDN Filter for DNS Query | Contains one or more FQDN, FQDN range, and/or any FQDN. | | +| | Protocol Description | Indicates service protocol used by the flow (NOTE 8). | | +| Packet replication and detection carry on information

NOTE 6 | Packet replication skip information
NOTE 7 | Contains UE address indication or N19/N6 indication. If the packet matches the packet replication skip information, i.e. source address of the packet is the UE address or the packet has been received on the interface in the packet replication skip information, the UP function neither creates a copy of the packet nor applies the corresponding processing (i.e. FAR, QER, URR). Otherwise the UPF performs a copy and applies the corresponding processing (i.e. FAR, QER, URR). | | +| | Carry on indication | Instructs the UP function to continue the packet detection process, i.e. lookup of the other PDRs. | | +| Outer header removal | | Instructs the UP function to remove one or more outer header(s) (e.g. IP+UDP+GTP, IP + possibly UDP, VLAN tag), from the incoming packet. | Any extension header shall be stored for this packet. | +| Forwarding Action Rule ID (NOTE 2) | | The Forwarding Action Rule ID identifies a forwarding action that has to be applied. | | +| Multi-Access Rule ID (NOTE 2) | | The Multi-Access Rule ID identifies an action to be applied for handling forwarding for a MA PDU Session. | | +| List of Usage Reporting Rule ID(s) | | Every Usage Reporting Rule ID identifies a measurement action that has to be applied. | | +| List of QoS Enforcement Rule ID(s) | | Every QoS Enforcement Rule ID identifies a QoS enforcement action that has to be applied. | | + +NOTE 1: Needed e.g. if: + +- UPF supports multiple DNN with overlapping IP addresses; +- UPF is connected to other UPF or AN node in different IP domains. +- UPF "local switch", N6-based forwarding and N19 forwarding is used for different 5G LAN groups. +- UPF "local switch" may be used for DNN/S-NSSAI dedicated for PIN. + +NOTE 2: Either a FAR ID or a MAR ID is included, not both. + +NOTE 3: The SMF may provide an indication asking the UPF to allocate one IPv4 address and/or IPv6 prefix. When asking to provide an IPv6 Prefix the SMF provides also an IPv6 prefix length. + +NOTE 4: When in the architecture defined in clause 5.34, a PDR is sent over N16a from SMF to I-SMF, the Packet Detection Information may indicate that CN tunnel info is to be locally determined. This is further defined in clause 5.34.6. + +NOTE 5: In the architecture defined in clause 5.34, the rules exchanged between I-SMF and SMF are not associated with a N4 Session ID but are associated with a N16a association. + +NOTE 6: Needed in the case of support for broadcast/multicast traffic forwarding using packet replication with SMF-provided PDRs and FARs as described in clause 5.8.2.13.3.2. + +NOTE 7: Needed in the case of packet replication with SMF-provided PDRs and FARs as described in clause 5.8.2.13.3.2, to prevent UPF from sending the broadcast/multicast packets back to the source UE or source N19/N6. + +NOTE 8: Not for PDR matching. It may be provided to assist PDU Set identification when PDU Set Identification and marking applies to the PDR. See TS 26.522 [179]. + +#### 5.8.5.4 QoS Enforcement Rule + +The following table describes the QoS Enforcement Rule (QER) that defines how a packet shall be treated in terms of bit rate limitation and packet marking for QoS purposes. All Packet Detection Rules that refer to the same QER share the same QoS resources, e.g. MFBR. + +**Table 5.8.5.4-1: Attributes within QoS Enforcement Rule** + +| Attribute | Description | Comment | +|----------------------------------------------|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| N4 Session ID | Identifies the N4 session associated to this QER | | +| Rule ID | Unique identifier to identify this information. | | +| QoS Enforcement Rule correlation ID (NOTE 1) | An identity allowing the UP function to correlate multiple Sessions for the same UE and APN. | Is used to correlate QoS Enforcement Rules for APN-AMBR enforcement. | +| Gate status UL/DL | Instructs the UP function to let the flow pass or to block the flow. | Values are: open, close, close after measurement report (for termination action "discard"). | +| Maximum bitrate | The uplink/downlink maximum bitrate to be enforced for the packets. | This field may e.g. contain any one of:
  • - APN-AMBR (for a QER that is referenced by all relevant Packet Detection Rules of all PDN Connections to an APN) (NOTE 1).
  • - Session-AMBR (for a QER that is referenced by all relevant Packet Detection Rules of the PDU Session)
  • - QoS Flow MBR (for a QER that is referenced by all Packet Detection Rules of a QoS Flow)
  • - SDF MBR (for a QER that is referenced by the uplink/downlink Packet Detection Rule of a SDF)
  • - Bearer MBR (for a QER that is referenced by all relevant Packet Detection Rules of a bearer) (NOTE 1).
| +| Guaranteed bitrate | The uplink/downlink guaranteed bitrate authorized for the packets. | This field contains:
  • - QoS Flow GBR (for a QER that is referenced by all Packet Detection Rules of a QoS Flow)
  • - Bearer GBR (for a QER that is referenced by all relevant Packet Detection Rules of a bearer) (NOTE 1).
| +| Averaging window | The time duration over which the Maximum and Guaranteed bitrate shall be calculated. | This is for counting the packets received during the time duration. | +| Down-link flow level marking | Flow level packet marking in the downlink. | For UPF, this is for controlling the setting of the RQI in the encapsulation header as described in clause 5.7.5.3. | +| QoS Flow ID | QoS Flow ID to be inserted by the UPF. | The UPF inserts the QFI value in the tunnel header of outgoing packets. | +| Paging Policy Indicator | Indicates the PPI value the UPF is required to insert in outgoing packets (see clause 5.4.3.2). | PPI applies only for DL traffic. The UPF inserts the PPI in the outer header of outgoing PDU. | + +| | | | +|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Packet rate (NOTE 1) | Number of packets per time interval to be enforced. | This field contains any one of:
- downlink packet rate for Serving PLMN Rate Control (the QER is referenced by all PDRs of the UE belonging to PDN connections using CIoT EPS Optimisations as described in TS 23.401 [26]).
- uplink/downlink packet rate for APN Rate Control (the QER is referenced by all PDRs of the UE belonging to PDN connections to the same APN using CIoT EPS Optimisations as described in TS 23.401 [26]). | +| End of Data Burst Marking Indication | Indicates to the UPF to provide an End of Data Burst indication of the last PDU of a Data burst to the NG-RAN over GTP-U | NG-RAN can configure UE power management schemes like connected mode DRX when UPF provides an indication of the End of Data Burst, see clause 5.37.8.3. | +| PDU Set Information marking Indicator | Indicates the UPF to insert PDU Set Information related to packets belonging to a PDU Set into GTP-U header. | UPF identifies PDU Sets in DL traffic and forwards PDU Set related information of each PDU to the NG-RAN over GTP-U, as described in clause 5.37.5. | +| ECN marking for L4S indicator | Indicates the UPF to perform ECN marking for L4S for the corresponding QoS Flow. | UPF uses information sent by NG-RAN in GTP-U header extension to perform ECN marking for L4S for the corresponding direction. | +| NOTE 1: This parameter is only used for interworking with EPC. | | | + +#### 5.8.5.5 Usage Reporting Rule + +The following table describes the Usage Reporting Rule (URR) that defines how a packet shall be accounted as well as when and how to report the measurements. + +##### **Table 5.8.5.5-1: Attributes within Usage Reporting Rule** + +| Attribute | Description | Comment | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| N4 Session ID | Identifies the N4 session associated to this URR | | +| Rule ID | Unique identifier to identify this information. | Used by UPF when reporting usage. | +| Reporting triggers | One or multiple of the events can be activated for the generation and reporting of the usage report. | Applicable events include:
- Start/stop of traffic detection with/without application instance identifier and deduced SDF filter reporting; Deletion of last PDR for a URR; Periodic measurement threshold reached; Volume/Time/Event measurement threshold reached; Immediate report requested; Measurement of incoming UL traffic; Measurement of discarded DL traffic; MAC address reporting in the UL traffic; unknown destination MAC/IP address; end marker packet has been received. | +| Periodic measurement threshold | Defines the point in time for sending a periodic report for this URR (e.g. timeofday). | This allows generation of periodic usage report for e.g. offline charging.
It can also be used for realizing the Monitoring time of the usage monitoring feature.
It can also be used for realizing the Quota-Idle-Timeout, i.e. to enable the CP function to check whether any traffic has passed during this time. | +| Volume measurement threshold | Value in terms of uplink and/or downlink and/or total byte-count when the measurement report is to be generated. | | +| Time measurement threshold | Value in terms of the time duration (e.g. in seconds) when the measurement report is to be generated. | | +| Event measurement threshold | Number of events (identified according to a locally configured policy) after which the measurement report is to be generated. | | +| Inactivity detection time | Defines the period of time after which the time measurement shall stop, if no packets are received. | Timer corresponding to this duration is restarted at the end of each transmitted packet. | +| Event based reporting | Points to a locally configured policy which identifies event(s) trigger for generating usage report. | | +| Linked URR ID(s) | Points to one or more other URR ID. | This enables the generation of a combined Usage Report for this and other URRs by triggering their reporting. See clause 5.2.2.4, TS 29.244 [65]. | +| Measurement Method | Indicates the method for measuring the network resources usage, i.e. the data volume, duration, combined volume/duration, or event. | | + +| | | | +|-------------------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Measurement information | Indicates specific conditions to be applied for measurements | It is used to request:
  • - measurement before QoS enforcement, and/or
  • - to pause or set to active a measurement as for the Pause of charging described in clause 4.4.4 and clause 4.23.14 of TS 23.502 [3], and/or
  • - to request reduced reporting for application start/stop events.
| +|-------------------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +#### 5.8.5.6 Forwarding Action Rule + +The following table describes the Forwarding Action Rule (FAR) that defines how a packet shall be buffered, dropped or forwarded, including packet encapsulation/decapsulation and forwarding destination. + +###### **Table 5.8.5.6-1: Attributes within Forwarding Action Rule** + +| Attribute | Description | Comment | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| N4 Session ID | Identifies the N4 session associated to this FAR. | NOTE 9. | +| Rule ID | Unique identifier to identify this information. | | +| Action | Identifies the action to apply to the packet | Indicates whether the packet is to be forwarded, duplicated, dropped or buffered.
When action indicates forwarding or duplicating, a number of additional attributes are included in the FAR.
For buffering action, a Buffer Action Rule is also included and the action can also indicate that a notification of the first buffered and/or a notification of first discarded packet is requested (see clause 5.8.3.2).
For drop action, a notification of the discarded packet may be requested (see clause 5.8.3.2). | +| Network instance (NOTE 2) | Identifies the Network instance associated with the outgoing packet (NOTE 1). | NOTE 8. | +| Destination interface (NOTE 3) (NOTE 7) | Contains the values "access side", "core side", "SMF", "N6-LAN", "5G VN internal". | Identifies the interface for outgoing packets towards the access side (i.e. down-link), the core side (i.e. up-link), the SMF, the N6-LAN (i.e. the DN), or to 5G VN internal (i.e. local switch). | +| Outer header creation (NOTE 3) | Instructs the UP function to add an outer header (e.g. IP+UDP+GTP, VLAN tag), IP + possibly UDP to the outgoing packet. | Contains the CN tunnel info, N6 tunnel info or AN tunnel info of peer entity (e.g. NG-RAN, another UPF, SMF, local access to a DN represented by a DNAI) (NOTE 8).
Any extension header stored for this packet shall be added.
The time stamps should be added in the GTP-U header if QoS Monitoring for packet delay is enabled for the traffic corresponding to the PDR(s). | +| Send end marker packet(s) (NOTE 2) | Instructs the UPF to construct end marker packet(s) and send them out as described in clause 5.8.1. | This parameter should be sent together with the "outer header creation" parameter of the new CN tunnel info. | +| Transport level marking (NOTE 3) | Transport level packet marking in the uplink and downlink, e.g. setting the DiffServ Code Point. | NOTE 8. | +| Forwarding policy (NOTE 3) | Reference to a preconfigured traffic steering policy or http redirection (NOTE 4). | The Forwarding policy refers to a preconfigured forwarding behaviour in UPF, which may be related to:
- N6-LAN steering to steer the subscriber's traffic to the appropriate N6 Service Functions deployed by the operator;
- local N6 steering to enable traffic steering in the local access to the DN according to the routing information provided by an AF as described in clause 5.6.7;
- a Redirect Destination and values for the forwarding behaviour (always, after measurement report (for termination action "redirect")). | + +| | | | +|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| +| Metadata (NOTE 10) | Metadata the UPF needs to add to traffic sent over a SFC. | The metadata information is associated with a TSP ID related to N6-LAN steering. | +| Request for Proxying in UPF | Indicates that the UPF shall perform ARP proxying and / or IPv6 Neighbour Solicitation Proxying as specified in clause 5.6.10.2. | Applies to the Ethernet PDU Session type. | +| Container for header enrichment (NOTE 2) | Contains information to be used by the UPF for header enrichment. | Only relevant for the uplink direction. | +| Buffering Action Rule (NOTE 5) | Reference to a Buffering Action Rule ID defining the buffering instructions to be applied by the UPF (NOTE 6) | | + +NOTE 1: Needed e.g. if: + +- UPF supports multiple DNN with overlapping IP addresses; +- UPF is connected to other UPF or NG-RAN node in different IP domains; +- UPF "local switch" and N19 forwarding is used for different 5G LAN groups. + +NOTE 2: These attributes are required for FAR action set to forwarding. + +NOTE 3: These attributes are required for FAR action set to forwarding or duplicating. + +NOTE 4: The TSP ID is preconfigured in the SMF and used to determine the Forwarding Policy included in the FAR according to the description in clause 5.6.7 and clause 6.1.3.14 of TS 23.503 [45] for local N6 steering and in clause 5.6.16 and clause 6.1.3.14 of TS 23.503 [45] for N6-LAN steering. The Forwarding Policy action is enforced before the Outer header creation actions. + +NOTE 5: This attribute is present for FAR action set to buffering. + +NOTE 6: The buffering action rule is created by the SMF and associated with the FAR in order to apply a specific buffering behaviour for UL/DL packets requested to be buffered, as described in clause 5.8.3 and clause 5.2.4 of TS 29.244 [65]. + +NOTE 7: The use of "5G VN internal" instructs the UPF to send the packet back for another round of ingress processing using the active PDRs pertaining to another N4 session of the same 5G VN group. + +NOTE 8: When in architectures defined in clause 5.34, a FAR is sent over N16a from SMF to I-SMF, the FAR sent by the SMF may indicate that the I-SMF is to locally determine the value of this attribute in order to build the N4 FAR rule sent to the actual UPF controlled by the I-SMF. This is further defined in clause 5.34.6. + +NOTE 9: In the architecture defined in clause 5.34, the rules exchanged between I-SMF and SMF are not associated with a N4 Session ID but are associated with a N16a association. + +NOTE 10: The use of Metadata is described in clause 5.6.16. How the UPF transforms the Metadata into actual information sent with the traffic (e.g. in the encapsulation header) is based on local policies related with the Forwarding Policy and not specified. + +#### 5.8.5.7 Usage Report generated by UPF + +The UPF sends the Usage Report to inform the SMF about the measurement of an active URR or about the detection of application traffic of an active Packet Detection Rule. For each URR, the Usage Report may be generated repeatedly, i.e. as long as any one of the valid event triggers applies. A final Usage Report is sent for a URR when it is no longer active, i.e. either the URR is removed or all the references to this URR in any of the Packet Detection Rules belonging to the N4 session. + +The following attributes can be included: + +**Table 5.8.5.7-1: Attributes within Usage Report** + +| Attribute | Description | Comment | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| N4 Session ID | Uniquely identifies a session. | Identifies the N4 session associated to this Usage Report | +| Rule ID | Uniquely identifies the Packet Detection Rule or Usage Reporting Rule within a session which triggered the report. | Packet Detection Rule is only indicated when Reporting trigger is Start/stop of traffic detection. Usage Reporting Rule is indicated for all other Reporting triggers. | +| Reporting trigger | Identifies the trigger for the usage report. | Applicable values are:
Start/stop of traffic detection with/without application instance identifier and deduced SDF filter reporting; Deletion of last PDR for a URR; Periodic measurement threshold reached; Volume/Time/Event measurement threshold reached; Immediate report requested; Measurement of incoming UL traffic; Measurement of discarded DL traffic; MAC address reporting in the UL traffic; reporting of unknown destination MAC/IP address; end marker packet has been received. | +| Start time | Provides the timestamp, in terms of absolute time, when the collection of the information provided within Usage-Information is started. | Not sent when Reporting trigger is Start/stop of traffic detection. | +| End time | Provides the timestamp, in terms of absolute time, when the information provided within Usage-Information is generated. | Not sent when Reporting trigger is Start/stop of traffic detection. | +| Measurement information | Defines the measured volume/time/events for this URR. | For details refer to clause 7.5.8.3 of TS 29.244 [65]. | +| Other information | Other events/information, e.g. related to reporting of UE MAC addresses. | For details refer to clause 7.5.8.3 of TS 29.244 [65]. | + +#### 5.8.5.8 Multi-Access Rule + +The following table describes the Multi-Access Rule (MAR) that includes the association to the two FARs for both 3GPP access and non-3GPP access in the case of supporting ATSSS. + +**Table 5.8.5.8-1: Attributes within Multi-Access Rule** + +| Attribute | Description | Comment | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| N4 Session ID | Identifies the N4 session associated to this MAR. | | +| Rule ID | Unique identifier to identify this rule. | | +| Steering functionality (NOTE 5) | Indicates the applicable traffic steering functionality:
Values "MPTCP functionality", "ATSSS-LL functionality", "MPQUIC functionality". | | +| Transport Mode | Identifies the transport mode (see clause 5.32.6.2.2.1) that should be used for the matching traffic, when the Steering functionality is the MPQUIC functionality. | The Transport Mode shall be included only when the Steering Functionality is the MPQUIC functionality. In all other cases, the Transport Mode shall not be included. | +| Steering mode (NOTE 5) | Values "Active-Standby", "Smallest Delay", "Load Balancing", or "Priority-based" or "Redundant". | | +| Steering Mode Indicator (NOTE 4) | Indicates either autonomous load-balance operation or UE-assistance operation if steering mode is set to "Load Balancing". | | +| Threshold values (NOTE 3, NOTE 4) | A Maximum RTT and/or a Maximum Packet Loss Rate | The Threshold Values are applied by UPF as described in clause 5.32.8. | +| Per-Access Forwarding Action information (NOTE 1) (NOTE 2) | Forwarding Action Rule ID | The Forwarding Action Rule ID identifies a forwarding action that has to be applied. | +| | Weight | Identifies the weight for the FAR if steering mode is "Load Balancing". The weights for all FARs need to sum up to 100. | +| | Priority | Values "Active or Standby" or "High or Low" for the FAR. "Active or Standby" for "Active-Standby" steering mode and "High or Low" for "Priority-based" steering mode. | +| | List of Usage Reporting Rule ID(s) | Every Usage Reporting Rule ID identifies a measurement action that has to be applied. This enables the SMF to request separate usage reports for different FARs (i.e. different accesses). | +| NOTE 1: The Per-Access Forwarding Action information is provided per access type (i.e. 3GPP access or Non-3GPP access). | | | +| NOTE 2: The Weight is treated as the default percentages if the Autonomous operation is allowed for the "Load Balancing" steering mode. | | | +| NOTE 3: The Threshold Values may be provided when the Steering Mode is Priority-based, or when the Steering Mode is Load-Balancing with fixed split percentages or when the Steering Mode is "Redundant". If the Steering Mode is "Redundant", either a Maximum RTT or a Maximum Packet Loss Rate may be provided, but not both.. | | | +| NOTE 4: The Steering Mode Indicator and the Threshold Values shall not be provided together. | | | +| NOTE 5: The Steering functionality "ATSSS-LL functionality" shall not be provided together with Steering Mode "Redundant". | | | + +#### 5.8.5.9 Bridge/Router Information + +The following table describes the User plane node Information (UI) that includes the information required to configure a 5GS logical bridge/router for TSC or Deterministic Networking PDU Sessions. + +**Table 5.8.5.9-1: User plane node Information** + +| Attribute | Description | Comment | +|--------------------|-----------------------------------------------------------------|----------------| +| Port Number | Port Number allocated by the node for a given PDU Session | | +| User plane node ID | Bridge identifier of the 5GS TSN bridge, or user-plane node ID. | | + +#### 5.8.5.10 Void + +#### 5.8.5.11 Session Reporting Rule + +The following table describes the Session Reporting Rule (SRR) that defines the detection and reporting events that the UPF shall report, that are not related to specific PDRs of the PDU Session, as follows: + +- Per QoS Flow per UE QoS Monitoring Report, as specified in clause 5.33.3.2. +- Change of 3GPP or non-3GPP access availability, for an MA PDU session. +- Per QoS Flow N6 Traffic Parameter Measurement Report. + +**Table 5.8.5.11-1: Attributes within Session Reporting Rule** + +| Attribute | Description | Comment | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| +| N4 Session ID | Identifies the N4 session associated to this SRR. | | +| Rule ID | Unique identifier to identify this information. | Used by UPF when reporting. | +| QoS Monitoring per QoS Flow Control Information | Indicates the UPF to apply perform the QoS Monitoring report for one or more QoS Flows. | The IE is defined in clause 7.5.2.9 of the TS 29.244 [65].
See NOTE 1. | +| Access Availability Control Information | Indicates the UPF to report when an access type becomes available or unavailable for an MA PDU Session. | The IE is defined in clause 7.5.2.9 of TS 29.244 [65]. | +| N6 Traffic Parameter Measurement Control Information | Indicates the UPF to report N6 Traffic parameter measurements for one QoS Flow, e.g. a measurement of N6 jitter range for a DL Periodicity and conditionally, a measurement of the UL/DL periodicity.
May indicate the DL Periodicity (See NOTE 2). | The IE is defined in clause 7.5.2.9 of TS 29.244 [65].
See NOTE 2. | +| NOTE 1: The QoS Monitoring per QoS Flow Control Information may contain an Indication of local direct event notification and. The Indication of local event notification includes a Notification Target Address (the details are described in clause 5.8.2.18) that identifies the recipient of the information being notified by the UPF (Local NEF/AF). The Indication of local direct event notification also indicates that the UPF reports the information to the NF indicated by the Target of reporting via Nupf_EventExposure_Notify service operation. | | | +| NOTE 2: The DL Periodicity is provided by the SMF in the N6 Traffic Parameters Measurement Control Information when the DL Periodicity is received from the PCF. | | | + +#### 5.8.5.12 Session reporting generated by UPF + +The UPF sends the session report to inform the SMF the detected events for a PDU Session that are related to an SRR. The UPF may support notification to the AF possibly via local NEF as described in clause 6.4 of TS 23.548 [130]. + +**Table 5.8.5.12-1: Attributes within Session Reporting** + +| Attribute | Description | Comment | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| N4 Session ID | Identifies the N4 session associated to the SRR which triggered the report. | | +| Rule ID | Unique identifier to identify the Session Reporting Rule within a session which triggered the report. | Used by UPF when reporting. | +| QoS Monitoring Report | Indicates the QoS Monitoring result for one or more QoS Flows. | The IE is defined in clause 7.5.8.6 of TS 29.244 [65]. | +| Access Availability Report | Indicates the change of 3GPP or non-3GPP access availability, for an MA PDU session. | The IE is defined in clause 7.5.8.6 of TS 29.244 [65]. | +| N6 Traffic Parameter Measurement Report | Indicates the N6 Traffic Parameter measurement result for one QoS Flow, e.g. a measurement of N6 jitter range associated with a DL Periodicity and conditionally, a measurement of the UL/DL periodicity. | The IE is defined in clause 7.5.8.6 of TS 29.244 [65]. | + +#### 5.8.5.13 Void + +#### 5.8.5.14 TSC Management Information + +The following table describes the TSC Management Information Container (TSC MIC) that includes UMIC, PMIC and the associated NW-TT port number. + +The SMF may include the notification target address for PMIC/UMIC UPF event provided by the PCF in the TSC Management Information sent to UPF if the UPF supports the related redirect reporting via Nupf. If the notification target address for PMIC/UMIC UPF event is provided by the SMF, the UPF may directly report TSC management information to the TSNAF or TSCTSF using Nupf\_EventExposure\_Notify service operation described in clause 7.2.29. + +**Table 5.8.5.14-1: TSC Management Information Container** + +| Attribute | Description | Comment | +|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| +| User plane node Management Information Container | 5GS TSN Bridge or Router information exchanged transparently between NW-TT and TSN AF or TSCTSF via 5GS (as in Table K.1-2). | | +| Port Management Information Container | Information exchanged transparently between NW-TT and TSN AF or TSCTSF via 5GS (as in Table K.1-1). | | +| NW-TT Port Number | NW-TT Port Number related to the PMIC. | Included when the PMIC information is present. | +| Notification Target Address for PMIC/UMIC UPF event (+ Notification Correlation ID) for PMIC/UMIC UPF event | Identifies the recipient of the information being notified by the UPF (TSNAF/TSCTSF). | | + +#### 5.8.5.15 Downlink Data Report generated by UPF + +The UPF sends the Downlink Data Report to inform the SMF about the events related to receiving or discarding of downlink packets. The SMF controls this type of UPF report by providing instructions in the Buffer Action Rule of a FAR. + +Following attributes can be included: + +**Table 5.8.5.15-1: Attributes within Downlink Data Report** + +| Attribute | Description | Comment | +|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| N4 Session ID | Uniquely identifies a session. | Identifies the N4 Session associated to this Usage Report | +| Rule ID | Uniquely identifies the Packet Detection Rule which triggered the report. | | +| Downlink Data Service Information | Indicates that the first downlink packet has been received for a QoS Flow at the UPF by reporting the QFI, if it is available. For the IP PDU Session Type, the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the downlink packet will also be reported. | This is used for downlink data notification related to QoS Flows. | +| Downlink Data Status | Indicates that the first downlink packet has been buffered or discarded for a service data flow at the UPF. | This is used for downlink data delivery status notification related to individual services. | + +## 5.9 Identifiers + +### 5.9.1 General + +Each subscriber in the 5G System shall be allocated one 5G Subscription Permanent Identifier (SUPI) for use within the 3GPP system. The 5G System supports identification of subscriptions independently of identification of the user equipment. Each UE accessing the 5G System shall be assigned a Permanent Equipment Identifier (PEI). + +The 5G System supports allocation of a temporary identifier (5G-GUTI) in order to support user confidentiality protection. + +### 5.9.2 Subscription Permanent Identifier + +A globally unique 5G Subscription Permanent Identifier (SUPI) shall be allocated to each subscriber in the 5G System and provisioned in the UDM/UDR. The SUPI is used only inside 3GPP system, and its privacy is specified in TS 33.501 [29]. + +The SUPI may contain: + +- an IMSI as defined in TS 23.003 [19], or +- a network-specific identifier, used for private networks as defined in TS 22.261 [2]. +- a GLI and an operator identifier of the 5GC operator, used for supporting FN-BRGs, as further described in TS 23.316 [84]. +- a GCI and an operator identifier of the 5GC operator, used for supporting FN-CRGs and 5G-CRG, as further described in TS 23.316 [84]. + +A SUPI containing a network-specific identifier shall take the form of a Network Access Identifier (NAI) using the NAI RFC 7542 [20] based user identification as defined in TS 23.003 [19]. + +When UE needs to indicate its SUPI to the network (e.g. as part of the Registration procedure), the UE provides the SUPI in concealed form as defined in TS 23.003 [19]. + +In order to enable roaming scenarios, the SUPI shall contain the address of the home network (e.g. the MCC and MNC in the case of an IMSI based SUPI). + +For interworking with the EPC, the SUPI allocated to the 3GPP UE shall always be based on an IMSI to enable the UE to present an IMSI to the EPC. + +The usage of SUPI for W-5GAN is further specified in TS 23.316 [84]. + +#### 5.9.2a Subscription Concealed Identifier + +The Subscription Concealed Identifier (SUCI) is a privacy preserving identifier containing the concealed SUPI. It is specified in TS 33.501 [29]. + +The usage of SUCI for W-5GAN access is further specified in TS 23.316 [84]. + +### 5.9.3 Permanent Equipment Identifier + +A Permanent Equipment Identifier (PEI) is defined for the 3GPP UE accessing the 5G System. + +The PEI can assume different formats for different UE types and use cases. The UE shall present the PEI to the network together with an indication of the PEI format being used. + +If the UE supports at least one 3GPP access technology (i.e. NG-RAN, E-UTRAN, UTRAN or GERAN), the UE must be allocated a PEI in the IMEI or IMEISV format. + +If a UE has registered with a network by using a network subscription and a PEI of the UE, then the UE shall keep the PEI to be used with the network subscription and shall not use that PEI with another network subscription while the UE is in registered state in the network. + +In the scope of this release, the PEI may be one of the following: + +- for UEs that support at least one 3GPP access technology, an IMEI or IMEISV, as defined in TS 23.003 [19]; +- PEI used in the case of W-5GAN access as further specified in TS 23.316 [84]. +- for UEs not supporting any 3GPP access technologies, the IEEE Extended Unique Identifier EUI-64 [113] of the access technology the UE uses to connect to the 5GC. + +### 5.9.4 5G Globally Unique Temporary Identifier + +The AMF shall allocate a 5G Globally Unique Temporary Identifier (5G-GUTI) to the UE that is common to both 3GPP and non-3GPP access. It shall be possible to use the same 5G-GUTI for accessing 3GPP access and non-3GPP access security context within the AMF for the given UE. An AMF may re-assign a new 5G-GUTI to the UE at any time. The AMF provides a new 5G-GUTI to the UE under the conditions specified in clause 6.12.3 of TS 33.501 [29]. When the UE is in CM-IDLE, the AMF may delay providing the UE with a new 5G-GUTI until the next NAS transaction. + +The 5G-GUTI shall be structured as: + +$$\langle 5G-GUTI \rangle := \langle GUAMI \rangle \langle 5G-TMSI \rangle$$ + +where GUAMI identifies one or more AMF(s). + +When the GUAMI identifies only one AMF, the 5G-TMSI identifies the UE uniquely within the AMF. However, when AMF assigns a 5G-GUTI to the UE with a GUAMI value used by more than one AMF, the AMF shall ensure that the 5G-TMSI value used within the assigned 5G-GUTI is not already in use by the other AMF(s) sharing that GUAMI value. + +The Globally Unique AMF ID (GUAMI) shall be structured as: + +$$\langle GUAMI \rangle := \langle MCC \rangle \langle MNC \rangle \langle AMF Region ID \rangle \langle AMF Set ID \rangle \langle AMF Pointer \rangle$$ + +where AMF Region ID identifies the region, AMF Set ID uniquely identifies the AMF Set within the AMF Region and AMF Pointer identifies one or more AMFs within the AMF Set. + +NOTE 1: The AMF Region ID addresses the case that there are more AMFs in the network than the number of AMFs that can be supported by AMF Set ID and AMF Pointer by enabling operators to re-use the same AMF Set IDs and AMF Pointers in different regions. + +NOTE 2: In the case of SNPNS, the PLMN IDs may be shared among SNPNS such that the constructed GUAMIs are not globally unique. However, PLMN ID and NID are provided together, separate from the GUAMI, to uniquely identify selected or supported SNPN in RRC and N2. + +NOTE 3: See TS 23.003 [19] for details on the structure of the fields of GUAMI. + +The 5G-S-TMSI is the shortened form of the GUTI to enable more efficient radio signalling procedures (e.g. during Paging and Service Request) and is defined as: + +$$\langle 5G-S-TMSI \rangle := \langle AMF Set ID \rangle \langle AMF Pointer \rangle \langle 5G-TMSI \rangle$$ + +As specified in TS 38.304 [50] and TS 36.304 [52] for 3GPP access, the NG-RAN uses the 10 Least Significant Bits of the 5G-TMSI in the determination of the time at which different UEs are paged. Hence, the AMF shall ensure that the 10 Least Significant Bits of the 5G-TMSI are evenly distributed. + +As specified in TS 38.331 [28] and TS 36.331 [51] for 3GPP access, the NG-RAN's RRC Connection Establishment's contention resolution process assumes that there is a low probability of the same 5G-TMSI being allocated by different AMFs to different UEs. The AMFs' process for allocating the 5G-TMSI should take this account. + +NOTE 4: To achieve this, the AMF could, for example, use a random seed number for any process it uses when choosing the UE's 5G-TMSI. + +### 5.9.5 AMF Name + +An AMF is identified by an AMF Name. AMF Name is a globally unique FQDN, the structure of AMF Name FQDN is defined in TS 23.003 [19]. An AMF can be configured with one or more GUAMIs. At a given time, GUAMI with distinct AMF Pointer value is associated to one AMF name only. + +### 5.9.6 Data Network Name (DNN) + +A DNN is equivalent to an APN as defined in TS 23.003 [19]. Both identifiers have an equivalent meaning and carry the same information. + +The DNN may be used e.g. to: + +- Select a SMF and UPF(s) for a PDU Session. +- Select N6 interface(s) for a PDU Session. +- Determine policies to apply to this PDU Session. + +The wildcard DNN is a value that can be used for the DNN field of Subscribed DNN list of Session Management Subscription data defined in clause 5.2.3.3 of TS 23.502 [3]. + +The wildcard DNN can be used with an S-NSSAI for operator to allow the subscriber to access any Data Network supported within the Network Slice associated with the S-NSSAI. + +### 5.9.7 Internal-Group Identifier + +The subscription data for an UE in UDR may associate the subscriber with groups. A group is identified by an Internal-Group Identifier. + +NOTE 1: A UE can belong to a limited number of groups, the exact number is defined in stage 3 specifications. + +NOTE 2: In this Release of the specification, the support of groups is only defined in non-roaming case. + +The Internal-Group Identifier(s) corresponding to an UE are provided by the UDM to the SMF as part Session Management Subscription data and (when PCC applies to a PDU Session) by the SMF to the PCF. The SMF may use this information to apply local policies and to store this information in CDR. The PCF may use this information to enforce AF requests as described in clause 5.6.7. + +The Internal-Group Identifier(s) corresponding to an UE are provided by the UDM to the AMF as part of Access and Mobility Subscription data. The AMF may use this information to apply local policies (such as Group specific NAS level congestion control defined in clause 5.19.7.5). + +### 5.9.8 Generic Public Subscription Identifier + +Generic Public Subscription Identifier (GPSI) is needed for addressing a 3GPP subscription in different data networks outside of the 3GPP system. The 3GPP system stores within the subscription data the association between the GPSI and the corresponding SUPI. + +GPSIs are public identifiers used both inside and outside of the 3GPP system. + +The GPSI is either an MSISDN or an External Identifier, see TS 23.003 [19]. If MSISDN is included in the subscription data, it shall be possible that the same MSISDN value is supported in both 5GS and EPS. + +NOTE: There is no implied 1-to-1 relationship between GPSI and SUPI. + +### 5.9.9 AMF UE NGAP ID + +An AMF UE NGAP ID is an identifier used to identify the UE in AMF on N2 reference point. AMF allocates the AMF UE NGAP ID and send it to the 5G-AN. For the following N2 signalling interaction sent from 5G-AN to AMF, AMF UE NGAP ID is used to identify the UE at the AMF. AMF UE NGAP ID is unique per AMF set. AMF UE NGAP ID may be updated without AMF change, or with AMF change as specified at clause 5.21.2.2. + +### 5.9.10 UE Radio Capability ID + +The UE Radio Capability ID is a short pointer with format defined in TS 23.003 [19] that is used to uniquely identify a set of UE Radio Capabilities (excluding UTRAN and NB-IoT capabilities). The UE Radio Capability ID is assigned either by the serving PLMN or by the UE manufacturer, as follows: + +- UE manufacturer-assigned: The UE Radio Capability ID may be assigned by the UE manufacturer in which case it includes a UE manufacturer identification (i.e. a Vendor ID). In this case, the UE Radio Capability ID uniquely identifies a set of UE radio capabilities and the UE Radio Capability for Paging for a UE by this manufacturer in any PLMN. +- PLMN-assigned: If a UE manufacturer-assigned UE Radio Capability ID is not used by the UE or the serving network, or it is not recognised by the serving PLMN UCMF, the UCMF may allocate UE Radio Capability IDs for the UE corresponding to each different set of UE radio capabilities the PLMN may receive from the UE at different times. In this case, the UE Radio Capability IDs the UE receives are applicable to the serving PLMN and uniquely identify the corresponding sets of UE radio capabilities and the UE Radio Capability for Paging(s) in this PLMN. The PLMN assigned UE Radio Capability ID includes a Version ID in its format. The value of the Version ID is the one configured in the UCMF, at time the UE Radio Capability ID value is assigned. The Version ID value makes it possible to detect whether a UE Radio Capability ID is current or outdated. + +NOTE: For the case the PLMN is configured to store PLMN assigned IDs in the UE manufacturer-assigned operation requested list defined in clause 5.4.4.1a, then the algorithm for assignment of PLMN-assigned UE Radio Capability ID shall assign different UE Radio Capability IDs for UEs with different TAC value. + +The type of UE Radio Capability ID (UE manufacturer-assigned or PLMN-assigned) is distinguished when a UE Radio Capability ID is signalled. + +## 5.10 Security aspects + +### 5.10.1 General + +The security features in the 5G System include: + +- Authentication of the UE by the network and vice versa (mutual authentication between UE and network). +- Security context generation and distribution. +- User Plane data confidentiality and integrity protection. +- Control Plane signalling confidentiality and integrity protection. +- User identity confidentiality. +- Support of LI requirements as specified in TS 33.126 [35] subject to regional/national regulatory requirements, including protection of LI data (e.g. target list) that may be stored or transferred by an NF. + +Detailed security related network functions for 5G are described in TS 33.501 [29]. + +### 5.10.2 Security Model for non-3GPP access + +#### 5.10.2.1 Signalling Security + +When a UE is connected via a NG-RAN and via a standalone non-3GPP accesses, the multiple N1 instances are secured using independent NAS security contexts, each created based on the security context in the corresponding SEAF (e.g. in the common AMF when the UE is served by the same AMF) derived from the UE authentication. + +### 5.10.3 PDU Session User Plane Security + +The User Plane Security Enforcement information provides the NG-RAN with User Plane security policies for a PDU session. It indicates: + +- whether UP integrity protection is: + - Required: for all the traffic on the PDU Session UP integrity protection shall apply. + - Preferred: for all the traffic on the PDU Session UP integrity protection should apply. + - Not Needed: UP integrity protection shall not apply on the PDU Session. +- whether UP confidentiality protection is: + - Required: for all the traffic on the PDU Session UP confidentiality protection shall apply. + - Preferred: for all the traffic on the PDU Session UP confidentiality protection should apply. + - Not Needed: UP confidentiality shall not apply on the PDU Session. + +User Plane Security Enforcement information applies only over 3GPP access. Once determined at the establishment of the PDU Session the User Plane Security Enforcement information applies for the life time of the PDU Session. + +NOTE 1: Applicability of UP integrity protection of UP Security Enforcement is defined in TS 33.501 [29] and TS 38.300 [27]. + +The SMF determines at PDU session establishment a User Plane Security Enforcement information for the user plane of a PDU session based on: + +- subscribed User Plane Security Policy which is part of SM subscription information received from UDM; and +- User Plane Security Policy locally configured per (DNN, S-NSSAI) in the SMF that is used when the UDM does not provide User Plane Security Policy information. +- The maximum supported data rate per UE for integrity protection for the DRBs, provided by the UE in the Integrity protection maximum data rate IE during PDU Session Establishment. The UE supporting NR as primary RAT, i.e. NG-RAN access via Standalone NR, shall set the Integrity protection maximum data rate IE for Uplink and Downlink to full rate at PDU Session Establishment as defined in TS 24.501 [47]. A UE not supporting NR as primary RAT and supporting E-UTRA connected to 5GC, shall set the Integrity protection maximum data rate IE for Uplink and Downlink to NULL at PDU Session Establishment as defined in TS 24.501 [47]. + +The User Plane Security Enforcement information provides the MME with User Plane integrity protection policies for the PDU session (PDN Connection). The information indicates whether UP integrity protection is: + +- Required: for all the traffic on the PDU Session (PDN Connection) UP integrity protection shall apply. +- Preferred: for all the traffic on the PDU Session (PDN Connection) UP integrity protection should apply. +- Not Needed: UP integrity protection shall not apply on the PDU Session (PDN Connection). + +In turn, the MME provides per EPS bearer User Plane Security Enforcement information to the E-UTRAN. All the bearers within a PDN Connection share the same User Plane integrity protection policies. + +The UE capability to support user plane integrity protection with EPS is indicated to AMF in the S1 UE network capability information. If the UE supports user plane integrity protection with EPS, and the AMF supports the associated functionality, the AMF indicates this to SMF at PDU Session Establishment using NG-RAN. If the UE and AMF support user plane integrity protection with EPS, for PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF may perform the EPS bearer ID allocation procedure as described in TS 23.502 [3] clause 4.11.1.4. If the UE does not support user plane integrity protection with EPS or the AMF does not support the associated functionality, the SMF shall not trigger the EPS bearer ID allocation procedure in clause 4.11.1.4 of TS 23.502 [3]. + +Unless the UE, the serving eNB and the MME support user plane integrity protection with EPS, the SMF+PGW-C shall reject a PDN Connection Establishment using EPS if the UP Security Enforcement Information has UP integrity protection set to Required. + +The SMF+PGW-C shall (e.g. based on the received RAT Type) reject a PDN Connection Establishment using GERAN/UTRAN if the UP Security Enforcement Information has UP integrity protection set to Required. + +NOTE 2: This assumes that the optional user plane integrity protection for GPRS specified in Release 13 has not been deployed. + +The SMF may, based on local configuration, reject the PDU Session Establishment request depending on the value of the maximum supported data rate per UE for integrity protection. + +NOTE 3: Reasons to reject a PDU Session Establishment request can e.g. be that the UP Integrity Protection is determined to be "Required" while the maximum supported data rate per UE for integrity protection is less than the expected required data rate for the DN. + +NOTE 4: The operator can take care to reduce the risk of such rejections when configuring the subscribed User Plane Security Policy for a DNN. For example, the operator may apply integrity protection "Required" only in scenarios where it can be assumed that the UE maximum supported data rate per UE for integrity protection is likely to be adequate for the DN. + +The User Plane Security Policy provide the same level of information than User Plane Security Enforcement information. + +User Plane Security Policy from UDM takes precedence over locally configured User Plane Security Policy. + +The User Plane Security Enforcement information may include the maximum supported data rate for integrity protection provided by the UE, is communicated from SMF to the NG-RAN for enforcement as part of PDU session related information. If the UP Integrity Protection is determined to be "Required" or "Preferred", the SMF also provides the maximum supported data rate per UE for integrity protection as received in the Integrity protection maximum data rate IE. This takes place at establishment of a PDU Session or at activation of the user plane of a PDU Session. The NG-RAN rejects the establishment of UP resources for the PDU Session when it cannot fulfil User Plane Security Enforcement information with a value of Required. The NG-RAN may also take the maximum supported data rate per UE for integrity protection into account in its decision on whether to accept or reject the establishment of UP resources. In this case the SMF releases the PDU Session. The NG-RAN notifies the SMF when it cannot fulfil a User Plane Security Enforcement with a value of Preferred. + +NOTE 5: For example, the NG-RAN cannot fulfil requirements in User Plane Security Enforcement information with UP integrity protection set to "Required" when it cannot negotiate UP integrity protection with the UE. + +It is responsibility of the NG-RAN to enforce that the maximum UP integrity protection data rate delivered to the UE in downlink is not exceeding the maximum supported data rate for integrity protection. + +It is expected that generally the UP integrity protection data rate applied by the UE in uplink will not exceed the indicated maximum supported data rate, but the UE is not required to perform strict rate enforcement. + +User Plane Security Enforcement information and the maximum supported data rate per UE for integrity protection is communicated from source to target NG-RAN node at handover. If the target RAN node cannot support requirements in User Plane Security Enforcement information, the target RAN node rejects the request to set up resources for the PDU Session. In this case the PDU Session is not handed over to the target RAN node and the PDU Session is released. + +If the UE or the new eNB or the MME does not indicate support of user plane integrity protection with EPS, PDU Sessions with UP integrity protection of the User Plane Security Enforcement information set to Required are not transferred to EPS as follows: + +- In the case of mobility without N26, the SMF+PGW-C shall reject a PDN connectivity request in EPS with handover indication if the UP integrity protection of the User Plane Security Enforcement is set to Required. + +NOTE 6: As described in clause 5.17.2.3.3, the UE does not know before trying to move a given PDU Session to EPC, whether that PDU session can be transferred to EPC. + +- In the case of idle mode and connected mode mobility with N26 to EPS, or mobility without N26, the SMF+PGW-C ensures that the PDU session is released. + +If the UE, target eNB and the target MME indicate support of User Plane Integrity Protection with EPS, PDU Sessions with UP integrity protection of the User Plane Security Enforcement information set to Required are transferred from 5GS to EPS according to existing procedures. + +For the bearers of PDN Connections with UP integrity protection set to Required, at (both idle mode and connected mode) mobility (including intra-TA mobility) to an eNB that does not support User Plane Integrity Protection with EPS, the MME shall inform the SMF+PGW-C and the SMF+PGW-C ensures that the PDU session is released. + +At connected mode mobility from EPS to GERAN/UTRAN or to a part of the EPS that does not support User Plane Integrity Protection, the source E-UTRAN shall ensure that EPS bearers with UP integrity protection of the User Plane Security Enforcement information set to Required are not handed over. + +In the case of idle mode mobility from an MME that supports User Plane Integrity Protection, to an MME that does not support User Plane Integrity Protection, the (home) SMF+PGW-C shall trigger (e.g. based on the lack of MME UIPIP capability information) the release of the bearers of PDN Connections with UP integrity protection set to Required. + +At any (e.g. idle mode) mobility from EPS to GERAN/UTRAN, the (home) SMF+PGW-C shall trigger (e.g. based on the received RAT Type) the release of the bearers of PDN Connections with UP integrity protection set to Required. + +PDU Sessions with UP confidentiality protection of the User Plane Security Enforcement information set to Required and UP integrity protection of the User Plane Security Enforcement information not set to Required, are allowed to be handed over to EPS regardless of how UP confidentiality protection applies in EPS. + +In the case of dual connectivity, the Integrity Protection is set to "Preferred", the Master RAN node may notify the SMF when it cannot fulfil a User Plane Security Enforcement with a value of Preferred. The SMF handling of the PDU session with respect to the Integrity Protection status is up to SMF implementation decision. + +## 5.11 Support for Dual Connectivity, Multi-Connectivity + +### 5.11.1 Support for Dual Connectivity + +Dual Connectivity involves two radio network nodes in providing radio resources to a given UE (with active radio bearers), while a single N2 termination point exists for the UE between an AMF and the RAN. The RAN architecture and related functions to support Dual Connectivity is further described in RAN specifications (e.g. TS 37.340 [31]). + +In this Release of the specification, the Dual Connectivity function does not apply to the NR RedCap UE. + +The RAN node at which the N2 terminates, performs all necessary N2 related functions such as mobility management, relaying of NAS signalling, etc. and manages the handling of user plane connection (e.g. transfer over N3). It is called the Master RAN Node. It may use resources of another RAN node, the Secondary RAN node, to exchange User Plane traffic of an UE. Master RAN node takes into account the RSN and/or PDU Session Pair ID to determine if dual connectivity shall be set up and ensure appropriate PDU session handling ensures fully redundant user plane path as described in clause 5.33.2.1. + +If the UE has Mobility Restriction (either signalled from the UDM, or, locally generated by the Serving PLMN policy in the AMF) the AMF signals these restrictions to the Master RAN Node as Mobility Restriction List; This may prevent the Master RAN node from setting up a Dual Connectivity for an UE. + +NOTE 1: Subject to policies in the NG-RAN, configuration of Dual Connectivity for a Data Radio Bearer can also be based on the Network Slice that the PDU Session belongs to. + +Dual Connectivity provides the possibility for the Master RAN node to request SMF: + +- For some or all PDU Sessions of an UE: Direct all the DL User Plane traffic of the PDU Session to the either the Master RAN Node or to the Secondary RAN Node. In this case, there is a single N3 tunnel termination at the RAN for such PDU Session. + +NOTE 2: The terminating RAN Node, can decide to keep traffic for specific QFI(s) in a PDU Session for a UE on a single RAT, or split them across the two RATs. + +- For some other PDU Sessions of an UE: Direct the DL User Plane traffic of some QoS Flows of the PDU Session to the Secondary (respectively Master) RAN Node while the remaining QoS Flows of the PDU Session + +are directed to the Master (respectively Secondary) RAN Node. In this case there are, irrespective of the number of QoS Flows, two N3 tunnel terminations at the RAN for such PDU Session. + +The Master RAN node may create and change this assignment for the user plane of a PDU Session at any time during the life time of the PDU Session; + +In both cases, a single PDU Session Id is used to identify the PDU Session. + +Additional functional characteristics are: + +- User location information is based on the identity of the cell that is serving the UE in the Master RAN node. The cell identity of the Primary cell in the secondary RAN node may also be included. NG-RAN includes the user location information in NGAP messages where the contents of the user location information may change during the corresponding procedure. +- Path update signalling related with Dual Connectivity and UPF re-allocation cannot occur at the same time. + +## 5.12 Charging + +### 5.12.1 General + +5GC supports interactions towards CHF for network resource usage, as defined in TS 32.240 [41]. The CHF and the Nchf service are defined in TS 32.290 [67]. + +The SMF supports the interactions towards the CHF, as defined in TS 32.255 [68]. The UPF supports functionality to collect and report usage data to SMF. The N4 reference point supports the SMF control of the UPF collection and reporting of usage data. + +The AMF supports interactions towards the CHF, as defined in TS 32.256 [114]. + +The SMSF supports interactions towards the CHF, as defined in TS 32.274 [118]. + +The NEF supports interactions towards the CHF, as defined in TS 32.254 [123]. + +### 5.12.2 Usage Data Reporting for Secondary RAT + +When NG-RAN is deployed in dual connectivity configuration, the HPLMN or VPLMN operator may wish to record the data volume sent and received on the Secondary RAT. + +In order to reduce the complexity of this procedure, the following principles are used in this release: + +- a) The PLMN locally activates the Secondary RAT Usage Data Reporting by NG-RAN OAM. The activation is based on configuration in NG-RAN and NG-RAN determines whether the data volume report will contain data volumes consumed for the whole PDU Session or for selected QoS Flows or both as described in TS 38.413 [34]. + +The activation can happen separately for Data Volume Reporting of NR in licensed or unlicensed spectrum and E-UTRA in licensed or unlicensed spectrum. If the PLMN uses this feature, it should ensure that this functionality is supported by all NG-RAN nodes that support NR or E-UTRA as a Secondary RAT. +- b) Depending on its configuration the NG-RAN reports uplink and downlink data volumes to the 5GC for the Secondary RAT (including the using of unlicensed spectrum for NR or E-UTRA) for the PDU Session or for selected QoS Flows or both and per time interval. +- c) During Xn handover and N2 handover, the source NG-RAN node reports the data volume to the 5GC. The reported data volume excludes data forwarded to the target RAN node. +- d) At the time of NG connection release, Secondary RAN Node change/release, deactivation of UP connection for a PDU Session, the NG-RAN node reports the data volumes to the 5GC. +- e) To assist "partial CDR" generation, NG-RAN OAM can instruct the NG-RAN to also make periodic reports (as described in clause 5.12.3) if no event has triggered a report before the period expires. + +NOTE 2: The timing of these periodic NG-RAN reports is not expected to align with the timing of partial CDR generation. Hence the frequency of NG-RAN reports might be greater than that of partial CDR generation. + +NOTE 3: RAN needs to be able to partition the measurements in a report to indicate usage that occurred before and after an absolute time. An example of the absolute time is that RAN is configured to partition data usage reports that occurred before and after midnight. + +### 5.12.3 Secondary RAT Periodic Usage Data Reporting Procedure + +Periodic reporting of the Secondary RAT usage data is an optional function. When NG-RAN, as defined in bullet e) of clause 5.12.12, is configured with a "time interval for Secondary RAT usage data reporting", the NG-RAN shall send a RAN Usage Data Report message for periodic reporting purposes to the SMF only when the timer expires for a UE for which Secondary RAT usage data reporting is ongoing. The timer runs from the last usage reporting for the UE. + +## 5.13 Support for Edge Computing + +Edge computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. Edge Computing support by 5GC is specified in this specification and in TS 23.548 [130]. + +NOTE: Edge Computing typically applies to non-roaming and LBO roaming scenarios. For HR roaming scenarios, Edge Computing applies only for "Home Routed with Session Breakout in VPLMN (HR-SBO)" which is described in clause 6.7 of TS 23.548 [130]. + +The 5G Core Network selects a UPF close to the UE and forwards traffic to enable the local access to the DN via a N6 interface according to the provided traffic steering rules to the UPF. This may be based on the UE's subscription data, UE location, the information from Application Function (AF) as defined in clause 5.6.7, the EAS information reported from EASDF (as defined in TS 23.548 [130]), policy or other related traffic rules. + +Due to user or Application Function mobility, the service or session continuity may be required based on the requirements of the service or the 5G network. + +The 5G Core Network may expose network information and capabilities to an Edge Computing Application Function. + +NOTE: Depending on the operator deployment, certain Application Functions can be allowed to interact directly with the Control Plane Network Functions with which they need to interact, while the other Application Functions need to use the external exposure framework via the NEF (see clause 6.2.10 for details). + +Edge computing can be supported by one or a combination of the following enablers: + +- User plane (re)selection: the 5G Core Network (re)selects UPF to route the user traffic to the local part of the DN as described in clause 6.3.3; +- Local Routing and Traffic Steering: the 5G Core Network selects the traffic to be routed to the applications in the local part of the DN; + - this includes the use of a single PDU Session with multiple PDU Session Anchor(s) (UL CL / IP v6 multi-homing) as described in clause 5.6.4 and the use of a PDU Session with Distributed Anchor Point using SSC mode 2/3. +- Session and service continuity to enable UE and application mobility as described in clause 5.6.9; +- An Application Function may influence UPF (re)selection and traffic routing via PCF or NEF as described in clause 5.6.7; +- Network capability exposure: 5G Core Network and Application Function to provide information to each other via NEF as described in clause 5.20 or directly as described in clause 4.15 of TS 23.502 [3] or from the UPF as described in clause 6.4 of TS 23.548 [130]; +- QoS and Charging: PCF provides rules for QoS Control and Charging for the traffic routed to the local part of the DN; + +- Support of Local Area Data Network: 5G Core Network provides support to connect to the LADN in a certain area where the applications are deployed as described in clause 5.6.5. +- Discovery and re-discovery of Edge Applications Servers as described in TS 23.548 [130]. +- Support of Edge Relocation as described in TS 23.548 [130] and the case of involving AF change as described in clauses 4.3.6.2, 4.3.6.3 and 4.3.6.4 of TS 23.502 [3]. Support of 5GC triggered Edge relocation within the same hosting PLMN's EHEs. +- Support of (I-)SMF (re)selection based on DNAI as described in clauses 4.3.5.1, 4.3.5.2 and 4.23.5.1 of TS 23.502 [3]. +- Support of finer sets of UEs. +- Support of common EAS discovery and common DNAI determination for set of UEs as described in clause 6.2 of TS 23.548 [130]. +- Support of mapping information between EAS IP/IP range and DNAI as described in clause 6.8 of TS 23.548 [130]. +- Support of AF request for DNAI as described in clause 6.8 of TS 23.548 [130]. + +## 5.14 Policy Control + +The policy and charging control framework for the 5G System is defined in TS 23.503 [45]. + +## 5.15 Network slicing + +### 5.15.1 General + +A Network Slice instance is defined within a PLMN or within an SNPN and shall include: + +- the Core Network Control Plane and User Plane Network Functions, as described in clause 4.2, + +and, in the serving PLMN, at least one of the following: + +- the NG-RAN described in TS 38.300 [27]; +- the N3IWF or TNGF functions to the non-3GPP Access Network described in clause 4.2.8.2 or the TWIF functions to the trusted WLAN in the case of support of N5CW devices described in clause 4.2.8.5; +- the W-AGF function to the Wireline Access Network described in clause 4.2.8.4. + +The 5G System deployed in a PLMN shall always support the procedures, information and configurations specified to support Network Slice instance selection in the present document, TS 23.502 [3] and TS 23.503 [45]. + +NOTE 1: Management of network slices are described in TS 28.530 [175], the procedures for provisioning of networks and network slices are described in TS 28.531 [176] and TS 28.541 [149] describes the resource model for managing the resources. + +Network slicing support for roaming is described in clause 5.15.6. + +Network slices may differ for supported features and network functions optimisations, in which case such Network Slices may have e.g. different S-NSSAIs with different Slice/Service Types (see clause 5.15.2.1). The operator can deploy multiple Network Slices delivering exactly the same features but for different groups of UEs, e.g. as they deliver a different committed service and/or because they are dedicated to a customer, in which case such Network Slices may have e.g. different S-NSSAIs with the same Slice/Service Type but different Slice Differentiators (see clause 5.15.2.1). + +The network may serve a single UE with one or more Network Slice instances simultaneously via a 5G-AN regardless of the access type(s) over which the UE is registered (i.e. 3GPP Access and/or N3GPP Access). The AMF instance serving the UE logically belongs to each of the Network Slice instances serving the UE, i.e. this AMF instance is common to the Network Slice instances serving a UE. + +NOTE 2: Number of simultaneous connection of Network Slice instances per UE is limited by the number of S-NSSAIs in the Requested/Allowed NSSAI as described in clause 5.15.2.1. + +NOTE 3: In this Release of the specification it is assumed that in any (home or visited) PLMN it is always possible to select an AMF that can serve any combination of S-NSSAIs that will be provided as an Allowed NSSAI. + +The selection of the set of Network Slice instances for a UE is triggered by the first contacted AMF in a Registration procedure normally by interacting with the NSSF, and can lead to a change of AMF. This is further described in clause 5.15.5. + +A PDU Session belongs to one and only one specific Network Slice instance per PLMN. Different Network Slice instances do not share a PDU Session, though different Network Slice instances may have slice-specific PDU Sessions using the same DNN. + +During the Handover procedure the source AMF selects a target AMF by interacting with the NRF as specified in clause 6.3.5. + +Network Slice-Specific Authentication and Authorization (NSSAA) enables Network Slice specific authentication as described in clause 5.15.10. + +Network Slice Admission Control (NSAC) controls the number of registered UEs per network slice, the number of UEs with at least one PDU Session/PDN Connection per network slice in the case of EPC interworking and the number of PDU Sessions per network slice as described in clause 5.15.11. + +Support of subscription-based restrictions to simultaneous registration of network slices uses Network Slice Simultaneous Registration Group (NSSRG) information to enable control of which Network Slices that can be registered simultaneously by a UE as described in clause 5.15.12. + +Support of data rate limitation per Network Slice for a UE enables enforcement of Maximum Bit Rate per Network Slice for a UE as described in clause 5.15.13. + +The selection of N3IWF/TNGF supporting a set of slice(s) is described in clause 6.3.6 and clause 6.3.12 respectively. + +The support of Network Slice usage control is described in clause 5.15.15. + +Support of Optimized handling of temporarily available network slices is described in clause 5.15.16. It also covers aspects related to graceful release of network slices connectivity during slice decommissioning. + +The Partial Network Slice support in a Registration Area is described in clause 5.15.17. + +Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas is described in clause 5.15.18. + +Support of Network Slice Replacement is described in clause 5.15.19. + +### 5.15.2 Identification and selection of a Network Slice: the S-NSSAI and the NSSAI + +#### 5.15.2.1 General + +An S-NSSAI identifies a Network Slice. + +An S-NSSAI is comprised of: + +- A Slice/Service type (SST), which refers to the expected Network Slice behaviour in terms of features and services; +- A Slice Differentiator (SD), which is optional information that complements the Slice/Service type(s) to differentiate amongst multiple Network Slices of the same Slice/Service type. + +An S-NSSAI can have standard values (i.e. such S-NSSAI is only comprised of an SST with a standardised SST value, see clause 5.15.2.2, and no SD) or non-standard values (i.e. such S-NSSAI is comprised of either both an SST and an SD or only an SST without a standardised SST value and no SD). An S-NSSAI with a non-standard value identifies a + +single Network Slice within the PLMN with which it is associated. An S-NSSAI with a non-standard value shall not be used by the UE in access stratum procedures in any PLMN other than the one to which the S-NSSAI is associated. + +The S-NSSAIs in the NSSP of the URSP rules (see clause 6.6.2 of TS 23.503 [45]) and in the Subscribed S-NSSAIs (see clause 5.15.3) contain only HPLMN S-NSSAI values. + +The S-NSSAIs in the Configured NSSAI, the Allowed NSSAI (see clause 5.15.4.1), the Requested NSSAI (see clause 5.15.5.2.1), the Rejected S-NSSAIs contain only values from the Serving PLMN. The Serving PLMN can be the HPLMN or a VPLMN. + +The S-NSSAI(s) in the PDU Session Establishment contain one Serving PLMN S-NSSAI value and in addition may contain a corresponding HPLMN S-NSSAI value to which this first value is mapped (see clause 5.15.5.3). Further information for slice replacement is described in clause 5.15.19. + +The optional mapping of Serving PLMN S-NSSAIs to HPLMN S-NSSAIs contains Serving PLMN S-NSSAI values and corresponding mapped HPLMN S-NSSAI values. + +The NSSAI is a collection of S-NSSAIs. An NSSAI may be a Configured NSSAI, a Requested NSSAI, Allowed NSSAI or a Partially Allowed NSSAI. There can be at most eight S-NSSAIs in Allowed NSSAI and Requested NSSAI sent in signalling messages between the UE and the Network. There can be at most seven S-NSSAIs in the Partially Allowed NSSAI and at most seven S-NSSAIs rejected partially in the RA, and the sum of S-NSSAIs in the Allowed NSSAI, and the Partially Allowed NSSAI shall be at most eight. The Requested NSSAI signalled by the UE to the network allows the network to select the Serving AMF, Network Slice(s) and Network Slice instance(s) for this UE, as specified in clause 5.15.5. + +NOTE 1: There can be at most a maximum of seven S-NSSAIs in the Partially Allowed NSSAI since there will always be an Allowed NSSAI allocated. + +Based on the operator's operational or deployment needs, a Network Slice instance can be associated with one or more S-NSSAIs, and an S-NSSAI can be associated with one or more Network Slice instances. Multiple Network Slice instances associated with the same S-NSSAI may be deployed in the same or in different Tracking Areas. When multiple Network Slice instances associated with the same S-NSSAI are deployed in the same Tracking Areas, the AMF instance serving the UE may logically belong to (i.e. be common to) more than one Network Slice instance associated with this S-NSSAI. + +In a PLMN, when an S-NSSAI is associated with more than one Network Slice instance, one of these Network Slice instances, as a result of the Network Slice instance selection procedure defined in clause 5.15.5, serves a UE that is allowed to use this S-NSSAI. For any S-NSSAI, the network may at any one time serve the UE with only one Network Slice instance associated with this S-NSSAI until cases occur where e.g. this Network Slice instance is no longer valid in a given Registration Area, or a change in UE's Allowed NSSAI occurs, etc. In such cases, procedures mentioned in clause 5.15.5.2.2 or clause 5.15.5.2.3 apply. + +Based on the Requested NSSAI (if any) and the Subscription Information, the 5GC is responsible for selection of a Network Slice instance(s) to serve a UE including the 5GC Control Plane and User Plane Network Functions corresponding to this Network Slice instance(s). The Subscription Information may contain restrictions to the simultaneous registration of network slices. This is provided to the serving AMF as part of the UE subscription, in the form of Network Slice Simultaneous Registration Group (NSSRG) information (see clause 5.15.12). + +The (R)AN may use Requested NSSAI in access stratum signalling to handle the UE Control Plane connection before the 5GC informs the (R)AN of the Allowed NSSAI. The Requested NSSAI is used by the RAN for AMF selection, as described in clause 6.3.5. The UE shall not include the Requested NSSAI in the RRC Resume when the UE asks to resume the RRC connection and is CM-CONNECTED with RRC\_INACTIVE state. + +When a UE is successfully registered over an Access Type, the CN informs the (R)AN by providing the Allowed NSSAI for the corresponding Access Type. + +NOTE 2: The details of how the RAN uses NSSAI information are described in TS 38.300 [27]. + +#### 5.15.2.2 Standardised SST values + +Standardized SST values provide a way for establishing global interoperability for slicing so that PLMNs can support the roaming use case more efficiently for the most commonly used Slice/Service Types. + +The SSTs which are standardised are in the following Table 5.15.2.2-1. + +**Table 5.15.2.2-1: Standardised SST values** + +| Slice/Service type | SST value | Characteristics | +|---------------------------|------------------|-----------------------------------------------------------------------------------| +| eMBB | 1 | Slice suitable for the handling of 5G enhanced Mobile Broadband. | +| URLLC | 2 | Slice suitable for the handling of ultra- reliable low latency communications. | +| MIoT | 3 | Slice suitable for the handling of massive IoT. | +| V2X | 4 | Slice suitable for the handling of V2X services. | +| HMTC | 5 | Slice suitable for the handling of High-Performance Machine-Type Communications. | +| HDLLC | 6 | Slice suitable for the handling of High Data rate and Low Latency Communications. | + +NOTE 1: The support of all standardised SST values is not required in a PLMN. Services indicated in this table for each SST value can also be supported by means of other SSTs. + +NOTE 2: A mapping of GSMA defined Network Slice Types (NEST) to standard SST values is defined in GSMA NG.116 [137]. + +### 5.15.3 Subscription aspects + +The Subscription Information shall contain one or more S-NSSAIs i.e. Subscribed S-NSSAIs. The subscription information shall include at least one default S-NSSAI. The UDM sends at the most 16 Subscribed S-NSSAIs to AMF, i.e. the number that can fit in a Configured NSSAI. The subscription information the UDM sends to the AMF shall include at least one default S-NSSAI. + +If an S-NSSAI is marked as default, then the network is expected to serve the UE with a related applicable Network Slice instance when the UE does not send any permitted S-NSSAI to the network in a Registration Request message as part of the Requested NSSAI. + +The Subscription Information for each S-NSSAI may contain: + +- a Subscribed DNN list and one default DNN; and +- the indication whether the S-NSSAI is marked as default Subscribed S-NSSAI; and +- the indication whether the S-NSSAI is subject to Network Slice-Specific Authentication and Authorization; and +- Network Slice Simultaneous Usage Group (NSSRG) information (see clause 5.15.12). + +The network verifies the Requested NSSAI the UE provides in the Registration Request against the Subscription Information. For the S-NSSAIs subject to Network Slice-Specific Authentication and Authorization the clause 5.15.10 applies. + +NOTE 1: It is recommended that at least one of the Subscribed S-NSSAIs marked as default S-NSSAI is not subject to Network Slice-specific Authentication and Authorization, in order to ensure access to services even when Network Slice-specific Authentication and Authorization fails. + +NOTE 2: It is recommended to minimize the number of Subscribed S-NSSAIs in subscriptions for NB-IoT or NR RedCap capable UEs to minimize overhead for signalling a large number of S-NSSAIs in Requested NSSAI in RRC and NAS via NB-IoT or NR RedCap. + +In roaming case, the UDM shall provide to the VPLMN only the S-NSSAIs from the Subscribed S-NSSAIs the HPLMN allows for the UE in the VPLMN. If the UE is subject to restrictions of simultaneous registration of network slices (i.e. if the Subscription Information for the S-NSSAIs contains NSSRG information), the UDM provides to the VPLMN a subscribed S-NSSAIs and, if applicable, NSSRG information, as described in clause 5.15.12. + +NOTE 3: Network slice instances supporting an S-NSSAI subject to Network Slice-Specific Authentication and Authorization need to be deployed with AMFs supporting Network Slice-Specific Authentication and Authorization, otherwise S-NSSAIs requiring Network Slice-Specific Authentication and Authorization would be incorrectly allowed without execution of Network Slice-Specific Authentication and Authorization. + +NOTE 4: Network slice instances supporting an S-NSSAI subject to Network Slice Admission Control (NSAC) for number of registered UE per network slice need to be deployed with AMFs supporting NSAC, otherwise S-NSSAIs requiring NSAC would be incorrectly allowed without execution of NSAC. + +When the UDM updates the Subscribed S-NSSAI(s) to the serving AMF, based on configuration in this AMF, the AMF itself or the NSSF determines the mapping of the Configured NSSAI for the Serving PLMN and/or Allowed NSSAI to the Subscribed S-NSSAI(s). The serving AMF then updates the UE with the above information as described in clause 5.15.4. + +### 5.15.4 UE NSSAI configuration and NSSAI storage aspects + +#### 5.15.4.1 General + +##### 5.15.4.1.1 UE Network Slice configuration + +The Network Slice configuration information contains one or more Configured NSSAI(s). A Configured NSSAI may either be configured by a Serving PLMN and apply to the Serving PLMN, or may be a Default Configured NSSAI configured by the HPLMN and that applies to any PLMNs for which no specific Configured NSSAI has been provided to the UE. There is at most one Configured NSSAI per PLMN. + +NOTE 1: The value(s) used in the Default Configured NSSAI are expected to be commonly decided by all roaming partners, e.g. by the use of values standardized by 3GPP or other bodies. + +The Default Configured NSSAI, if it is configured in the UE, is used by the UE in a Serving PLMN only if the UE has no Configured NSSAI for the Serving PLMN. + +The Configured NSSAI of a PLMN may include S-NSSAIs that have standard values or PLMN-specific values. + +The Configured NSSAI for the Serving PLMN includes the S-NSSAI values which can be used in the Serving PLMN and may be associated with mapping of each S-NSSAI of the Configured NSSAI to one or more corresponding HPLMN S-NSSAI values. In the non-roaming case, the network shall not provide any mapped S-NSSAI to the UE with the Configured NSSAI. In the roaming case, the AMF shall provide to the UE the mapping of each S-NSSAI of the Configured NSSAI for the Serving PLMN to the corresponding S-NSSAI values of the HPLMN when providing NSSAI information, as described in TS 24.501 [47]. + +A UE subscription may contain Network Slice Simultaneous Registration Group (NSSRG) information. If so, the UE configuration is performed as described in clause 5.15.12.2. + +The UE may be pre-configured with the Default Configured NSSAI. The UE may be provisioned/updated with the Default Configured NSSAI, determined by the UDM in the HPLMN, using the UE Parameters Update via UDM Control Plane procedure defined in clause 4.20 of TS 23.502 [3]. Each S-NSSAI in the Default Configured NSSAI may have a corresponding S-NSSAI as part of the Subscribed S-NSSAI(s). Consequently, if the Subscribed S-NSSAI(s) which are also present in the Default Configured NSSAI are updated the UDM should update the Default Configured NSSAI in the UE. + +In the HPLMN, the S-NSSAIs in the Configured NSSAI provided as described in clause 5.15.4.2, at the time when they are provided to the UE, shall match the Subscribed S-NSSAIs for the UE. + +When the Subscribed S-NSSAI(s) are updated (i.e. some existing S-NSSAIs are removed and/or some new S-NSSAIs are added) and one or more are applicable to the Serving PLMN the UE is registered in, as described in clause 5.15.3, or when the associated mapping is updated the AMF shall update the UE with the Configured NSSAI for the Serving PLMN and/or Allowed NSSAI and Partially Allowed NSSAI and/or the associated mapping to HPLMN S-NSSAIs (see clause 5.15.4.2). When there is the need to update the Allowed NSSAI or Partially Allowed NSSAI, the AMF shall provide the UE with the new Allowed NSSAI or Partially Allowed NSSAI and the associated mapping to HPLMN S-NSSAIs, unless the AMF cannot determine the new Allowed NSSAI (e.g. all S-NSSAIs in the old Allowed NSSAI have been removed from the Subscribed S-NSSAIs), in which case the AMF shall not send any Allowed NSSAI to the UE but indicate to the UE to perform a Registration procedure. If the UE is in a CM-IDLE state, the AMF may trigger Network Triggered Service Request or wait until the UE is in a CM-CONNECTED state as described in clause 4.2.4.2, TS 23.502 [3]. + +When providing a Requested NSSAI to the network upon registration, the UE in a given PLMN only includes and uses S-NSSAIs applying to this PLMN. The mapping of S-NSSAIs of the Requested NSSAI to HPLMN S-NSSAIs may also + +be provided (see clause 5.15.4.1.2 for when this is needed). The S-NSSAIs in the Requested NSSAI are part of the Configured and/or Allowed NSSAIs applicable for this PLMN, when they are available. If the UE has received NSSRG information together with the Configured NSSAI, it only includes in the Requested NSSAI S-NSSAIs that all share a common NSSRG. If the UE has stored Pending NSSAI and the UE is still interested in the Pending NSSAI then all the S-NSSAIs in the Requested NSSAI and the Pending S-NSSAI shall share a common NSSRG. If no Configured NSSAI and Allowed NSSAI for the PLMN are available, the S-NSSAIs in the Requested NSSAI correspond to the Default Configured NSSAI, if configured in the UE. Upon successful completion of a UE's Registration procedure over an Access Type, the UE obtains from the AMF an Allowed NSSAI or Partially Allowed NSSAI for this Access Type, which includes one or more S-NSSAIs and, if needed (see clause 5.15.4.1.2 for when this is needed), their mapping to the HPLMN S-NSSAIs. These S-NSSAIs are valid for the current Registration Area and Access Type provided by the AMF the UE has registered with and can be used simultaneously by the UE (up to the maximum number of simultaneous Network Slice instances or PDU Sessions). + +The UE might also obtain from the AMF, one or more rejected S-NSSAIs with cause and validity of rejection. An S-NSSAI may be rejected: + +- for the entire PLMN; +- for the current Registration Area; or +- partially in the current Registration Area. Such S-NSSAI rejected partially in the current Registration area is associated with a list of TAs where the S-NSSAI is not supported. + +The AMF may also reject the use of an S-NSSAI due to congestion as described in clause 5.19.7.4. + +While the UE remains RM-REGISTERED in the PLMN and regardless of the Access Type, the UE shall not re-attempt to register to an S-NSSAI rejected for the entire PLMN until this rejected S-NSSAI is deleted as specified below. + +While the UE remains RM-REGISTERED in the PLMN, the UE shall not re-attempt to register to an S-NSSAI rejected in the current Registration Area until it moves out of the current Registration Area. + +While the UE remains RM-REGISTERED in the PLMN, the UE shall not re-attempt to register to an S-NSSAI rejected partially in the RA until the UE moves into a TA which is not part of the list of TAs associated with the S-NSSAI. + +NOTE 2: The details and more cases of S-NSSAI rejection are described in TS 24.501 [47]. + +The S-NSSAIs that the UE provides in the Requested NSSAI which are neither in the Allowed NSSAI nor in the Partially Allowed NSSAI, nor provided as a rejected S-NSSAI, shall, by the UE, not be regarded as rejected, i.e. the UE may request to register these S-NSSAIs again next time the UE sends a Requested NSSAI. + +The UE stores (S-)NSSAIs as follows: + +- When provisioned with a Configured NSSAI for a PLMN and/or a mapping of Configured NSSAI to HPLMN S-NSSAIs and possibly NSSRG information for each S-NSSAI in the Configured NSSAI (if applicable and supported by the UE), or when requested to remove the configuration due to network slicing subscription change, the UE shall: + - replace any stored (old) Configured NSSAI for this PLMN with the new Configured NSSAI for this PLMN (if applicable); and + - delete any stored associated mapping of this old Configured NSSAI for this PLMN to HPLMN S-NSSAIs and, if present and applicable, store the mapping of Configured NSSAI to HPLMN S-NSSAIs; and + - delete any stored associated NSSRG information for each S-NSSAI of the Configured NSSAI and, if present, store the associated NSSRG information for each S-NSSAI of the Configured NSSAI; and + - delete any stored rejected S-NSSAI for this PLMN; + - keep the received Configured NSSAI for a PLMN (if applicable) and associated mapping to HPLMN S-NSSAIs (if applicable) and associated NSSRG information for each S-NSSAI of the Configured NSSAI (if applicable and supported by the UE) stored in the UE, even when registering in another PLMN, until a new Configured NSSAI for this PLMN and/or associated mapping are provisioned in the UE, or until the network slicing subscription changes, as described in clause 5.15.4.2. The number of Configured NSSAIs and associated mapping to be kept stored in the UE for PLMNs other than the HPLMN is up to UE implementation. A UE shall at least be capable of storing a Configured NSSAI for the serving PLMN + +including any necessary mapping of the Configured NSSAI for the Serving PLMN to HPLMN S-NSSAIs and the Default Configured NSSAI. + +- The Allowed NSSAI received in a Registration Accept message or a UE Configuration Update Command applies to a PLMN when at least a TAI of this PLMN is included in the RA/TAI list included in this Registration Accept message or UE Configuration Update Command. If the UE Configuration Update Command contains an Allowed NSSAI but not a TAI List, then the last received RA/TAI list applies for the decision on which PLMN(s) the Allowed NSSAI is applicable. If received, the Allowed NSSAI for a PLMN and Access Type and any associated mapping of this Allowed NSSAI to HPLMN S-NSSAIs shall be stored in the UE. The UE should store this Allowed NSSAI and any associated mapping of this Allowed NSSAI to HPLMN S-NSSAIs also when the UE is turned off, or until the network slicing subscription changes, as described in clause 5.15.4.2: + +NOTE 3: Whether the UE stores the Allowed NSSAI and any associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs also when the UE is turned off is left to UE implementation. + +- When a new Allowed NSSAI for a PLMN and any associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs are received over an Access Type, the UE shall: + - replace any stored (old) Allowed NSSAI and any associated mapping for these PLMN and Access Type with this new Allowed NSSAI; and + - delete any stored associated mapping of this old Allowed NSSAI for this PLMN to HPLMN S-NSSAIs and, if present, store the associated mapping of this new Allowed NSSAI to HPLMN S-NSSAIs; +- If received, a Partially Allowed NSSAI received in a Registration Accept message or a UE Configuration Update Command message applies to the current Registration Area. The UE stores the Partially Allowed NSSAI in the same way as described for the Allowed NSSAI (see also clause 5.15.17). +- If received, an S-NSSAI rejected for the entire PLMN shall be stored in the UE while RM-REGISTERED in this PLMN regardless of the Access Type or until it is deleted. +- If received, an S-NSSAI rejected for the current Registration Area shall be stored in the UE while RM-REGISTERED until the UE moves out of the current Registration Area or until the S-NSSAI is deleted. +- If received, an S-NSSAI rejected partially in the RA shall be stored in the UE while RM-REGISTERED until the UE moves out of the current Registration Area or until the S-NSSAI is deleted (see also clause 5.15.17). + +NOTE 4: The storage aspects of rejected S-NSSAIs are described in TS 24.501 [47]. + +- If received, the Pending NSSAI shall be stored in the UE as described in TS 24.501 [47]. +- If received, the S-NSSAI validity time information shall be stored in the UE in the UE as described in TS 24.501 [47]. +- If received, the S-NSSAI location availability information shall be stored in the UE as described in TS 24.501 [47]. +- If received, the mapping of old S-NSSAI to the Alternative S-NSSAI shall be stored in the UE as described in TS 24.501 [47]. + +UE configuration to guide UE selection of a N3IWF/TNGF that supports the S-NSSAIs needed by the UE is defined in clause 6.3.6 and clause 6.3.12 respectively. + +##### 5.15.4.1.2 Mapping of S-NSSAIs values in the Allowed NSSAI and in the Requested NSSAI to the S-NSSAIs values used in the HPLMN + +For the roaming case, one or more S-NSSAIs in an Allowed NSSAI provided to the UE can have values which are not part of the UE's current Network Slice configuration information for the Serving PLMN. In this case, the network provides the Allowed NSSAI together with the mapping of each S-NSSAI of the Allowed NSSAI to the corresponding S-NSSAI of the HPLMN. This mapping information allows the UE to associate Applications to S-NSSAIs of the HPLMN as per NSSP of the URSP rules or as per the UE Local Configuration, as defined in clause 6.1.2.2.1 of TS 23.503 [45] and to the corresponding S-NSSAI from the Allowed NSSAI. + +In the non-roaming case, the network shall not provide any mapped S-NSSAI to the UE with the Allowed NSSAI. + +In roaming case, the UE shall provide in the Requested NSSAI the mapping of S-NSSAIs of the Serving PLMN values to the corresponding S-NSSAI values of the HPLMN, for each S-NSSAI in the Requested NSSAI for which a mapping is available. These values are found in the mapping previously received from the Serving PLMN of the S-NSSAIs of the Configured NSSAI for the Serving PLMN or of the S-NSSAIs of the Allowed NSSAI for the Serving PLMN and Access Type to the corresponding S-NSSAIs values used in the HPLMN. + +If the AMF provides Partially Allowed NSSAI to the UE, in roaming case the AMF may provide the mapping information of each S-NSSAI of the Partially Allowed NSSAI to the corresponding HPLMN S-NSSAI as described in clause 5.15.17. + +#### 5.15.4.2 Update of UE Network Slice configuration + +At any time, the AMF may provide the UE with a new Configured NSSAI for the Serving PLMN, associated with mapping of the Configured NSSAI to HPLMN S-NSSAIs as specified in clause 5.15.4.1. The Configured NSSAI for the Serving PLMN and the mapping information is either determined in the AMF (if based on configuration, the AMF is allowed to determine the Network Slice configuration for the whole PLMN) or by the NSSF. The AMF provides an updated Configured NSSAI as specified in clause 4.2.4 of TS 23.502 [3], UE Configuration Update procedure. + +If an S-NSSAI is to be stopped to be used, e.g. due to the network slice is to be deleted as described in TS 28.541 [149], the AMFs may reject UE requests for the S-NSSAI based on the OAM state before the network slice becomes unavailable. The AMF may based on operator policies (e.g. when there is no timing information related to the termination or the AMF or UE does not support the timing information as described in in clause 5.15.16), release PDU Sessions associated with the S-NSSAI, and remove the S-NSSAI from e.g. the Allowed NSSAI and the Configured NSSAI before the Network Slice becomes unavailable. The AMF may use the timing information as described in clause 5.15.16 if it supports this feature and set validity time of the S-NSSAI accordingly. + +The AMF shall provide the UE with NSSRG information alongside the Configured NSSAI if NSSRG information is included in the subscription information received from the UDM and if the UE has indicated support for the feature as part of the registration request, see clause 5.15.12. + +The AMF may provide the UE with the mapping of old S-NSSAI to the Alternative S-NSSAI if the UE has indicated support for the feature as part of the registration request, see clause 5.15.19. + +If the HPLMN performs the configuration update of a UE registered in the HPLMN (e.g. due to a change in the Subscribed S-NSSAI(s) or due to a change of NSSRG information), this results in updates to the Configured NSSAI for the HPLMN and, if applicable, NSSRG information for each S-NSSAI of the Configured NSSAI. Updates to the Allowed NSSAI and/or, if present, to the associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs are also possible if the configuration update affects S-NSSAI(s) in the current Allowed NSSAI. + +If the VPLMN performs the configuration update of a UE registered in the VPLMN (e.g. due to a change in the Subscribed S-NSSAI(s), the associated mapping is updated, or due to a change of NSSRG information), this results in updates to the Configured NSSAI for the Serving PLMN and/or to the associated mapping of the Configured NSSAI for the Serving PLMN to HPLMN S-NSSAIs and, if applicable, NSSRG information for each S-NSSAI of the Configured NSSAI. Updates to the Allowed NSSAI and/or to the associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs are also possible if the configuration update affects S-NSSAI(s) in the current Allowed NSSAI. + +A UE for which the Configured NSSAI for the Serving PLMN has been updated as described in clause 5.15.4.1 and has been requested to perform a Registration procedure, shall initiate a Registration procedure to receive a new valid Allowed NSSAI (see clause 5.15.5.2.2). + +When the subscribed S-NSSAIs change, a UDR flag is set in the HPLMN to make sure the current PLMN (or, if the UE was not reachable, the next serving PLMN) is informed by the UDM that the subscription data for network slicing has changed. The AMF, when it receives the indication from the UDM subscription has changed, indicates the UE that subscription has changed and uses any updated subscription information from the UDM to update the UE. Once the AMF updates the UE and obtains an acknowledgment from the UE, the AMF informs the UDM that the configuration update was successful and the UDM clears the flag in the UDR. If the UE is in a CM-IDLE state, the AMF may trigger Network Triggered Service Request or wait until the UE is in a CM-CONNECTED state as described in clause 4.2.4.2, TS 23.502 [3]. + +If the UE receives indication from the AMF that Network Slicing subscription has changed, the UE locally deletes the network slicing information it has for all PLMNs, except the Default Configured NSSAI (if present). It also updates the current PLMN network slicing configuration information with any received values from the AMF. + +The update of URSP rules (which include the NSSP), if necessary at any time, is described in TS 23.503 [45]. + +### 5.15.5 Detailed Operation Overview + +#### 5.15.5.1 General + +The establishment of User Plane connectivity to a Data Network via a Network Slice instance(s) comprises two steps: + +- performing a RM procedure to select an AMF that supports the required Network Slices. +- establishing one or more PDU Session to the required Data network via the Network Slice instance(s). + +#### 5.15.5.2 Selection of a Serving AMF supporting the Network Slices + +##### 5.15.5.2.1 Registration to a set of Network Slices + +When a UE registers over an Access Type with a PLMN, if the UE has either or both of: + +- a Configured NSSAI for this PLMN; +- an Allowed NSSAI for this PLMN and Access Type; + +the UE shall provide to the network, in AS layer under the conditions described in clause 5.15.9 and in NAS layer, a Requested NSSAI containing the S-NSSAI(s) corresponding to the Network Slice(s) to which the UE wishes to register, unless they are stored in the UE in the Pending NSSAI. + +The Requested NSSAI shall be one of: + +- the Default Configured NSSAI, i.e. if the UE has no Configured NSSAI nor an Allowed NSSAI for the serving PLMN; +- the Configured-NSSAI, or a subset thereof as described below, e.g. if the UE has no Allowed NSSAI for the Access Type for the serving PLMN; +- the Allowed-NSSAI for the Access Type over which the Requested NSSAI is sent, or a subset thereof; or +- the Allowed-NSSAI for the Access Type over which the Requested NSSAI is sent, or a subset thereof, plus one or more S-NSSAIs from the Configured-NSSAI not yet in the Allowed NSSAI for the Access Type as described below. + +NOTE 1: If the UE wishes to register only a subset of the S-NSSAIs from the Configured NSSAI or the Allowed NSSAI, to be able to register with some Network Slices e.g. to establish PDU Sessions for some application(s), and the UE uses the URSP rules (which includes the NSSP) or the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503 [45], then the UE uses applicable the URSP rules or the UE Local Configuration to ensure that the S-NSSAIs included in the Requested NSSAI are not in conflict with the URSP rules or with the UE Local Configuration. + +The subset of S-NSSAIs in the Configured-NSSAI provided in the Requested NSSAI consists of one or more S-NSSAI(s) in the Configured NSSAI applicable to this PLMN, if one is present, and for which no corresponding S-NSSAI is already present in the Allowed NSSAI for the access type for this PLMN. The UE shall not include in the Requested NSSAI any S-NSSAI that is currently rejected by the network (i.e. rejected in the current registration area or rejected in the PLMN). For the registration to a PLMN for which neither a Configured NSSAI applicable to this PLMN or an Allowed NSSAI are present, the S-NSSAIs provided in the Requested NSSAI correspond to the S-NSSAI(s) in the Default Configured NSSAI unless the UE has HPLMN S-NSSAI for established PDU Session(s) in which case the HPLMN S-NSSAI(s) shall be provided in the mapping of Requested NSSAI in the NAS Registration Request message, with no corresponding VPLMN S-NSSAI in the Requested NSSAI. If the UE has been provided with NSSRG information together with the Configured NSSAI, the UE only includes in the Requested NSSAI S-NSSAIs that share a common NSSRG, see clause 5.15.12.2. If the UE has stored Pending NSSAI and the UE is still interested in the Pending NSSAI then all the S-NSSAIs in the Requested NSSAI and the Pending S-NSSAI shall share a common NSSRG. + +When a UE registers over an Access Type with a PLMN, the UE shall also indicate in the Registration Request message when the Requested NSSAI is based on the Default Configured NSSAI. + +The UE shall include the Requested NSSAI in the RRC Connection Establishment and in the establishment of the connection to the N3IWF/TNGF (as applicable) and in the NAS Registration procedure messages subject to conditions set out in clause 5.15.9. However, the UE shall not indicate any NSSAI in RRC Connection Establishment or Initial NAS message unless it has either a Configured NSSAI for the corresponding PLMN, an Allowed NSSAI for the corresponding PLMN and Access Type, or the Default Configured NSSAI. If the UE has HPLMN S-NSSAI(s) for established PDU Session(s), the HPLMN S-NSSAI(s) shall be provided in the mapping of Requested NSSAI in the NAS Registration Request message, independent of whether the UE has the corresponding VPLMN S-NSSAI. The (R)AN shall route the NAS signalling between this UE and an AMF selected using the Requested NSSAI obtained during RRC Connection Establishment or connection to N3IWF/TNGF respectively. If the (R)AN is unable to select an AMF based on the Requested NSSAI, it routes the NAS signalling to an AMF from a set of default AMFs. In the NAS signalling, if the UE is roaming, the UE provides the mapping of each S-NSSAI of the Requested NSSAI to a corresponding HPLMN S-NSSAI. + +When a UE registers with a PLMN, if for this PLMN the UE has not included a Requested NSSAI nor a GUAMI while establishing the connection to the (R)AN, the (R)AN shall route all NAS signalling from/to this UE to/from a default AMF. When receiving from the UE a Requested NSSAI and a 5G-S-TMSI or a GUAMI in RRC Connection Establishment or in the establishment of connection to N3IWF/TNGF, if the 5G-AN can reach an AMF corresponding to the 5G-S-TMSI or GUAMI, then 5G-AN forwards the request to this AMF. Otherwise, the 5G-AN selects a suitable AMF based on the Requested NSSAI provided by the UE and forwards the request to the selected AMF. If the 5G-AN is not able to select an AMF based on the Requested NSSAI, then the request is sent to a default AMF. + +When the AMF selected by the AN during Registration Procedure receives the UE Registration request, or after an AMF selection by MME (i.e. during EPS to 5GS handover) the AMF receives S-NSSAI(s) from SMF+PGW-C in 5GC: + +- As part of the Registration procedure described in clause 4.2.2.2.2 of TS 23.502 [3], or as part of the EPS to 5GS handover using N26 interface procedure described in clause 4.11.1.2.2 of TS 23.502 [3], the AMF may query the UDM to retrieve UE subscription information including the Subscribed S-NSSAIs. +- The AMF verifies whether the S-NSSAI(s) in the Requested NSSAI or the S-NSSAI(s) received from SMF+PGW-C are permitted based on the Subscribed S-NSSAIs (to identify the Subscribed S-NSSAIs the AMF may use the mapping to HPLMN S-NSSAIs provided by the UE, in the NAS message, for each S-NSSAI of the Requested NSSAI). +- When the UE context in the AMF does not yet include an Allowed NSSAI for the corresponding Access Type, the AMF queries the NSSF (see (B) below for subsequent handling), except in the case when, based on configuration in this AMF, the AMF is allowed to determine whether it can serve the UE (see (A) below for subsequent handling). The IP address or FQDN of the NSSF is locally configured in the AMF. + +NOTE 2: The configuration in the AMF depends on operator's policy. + +- When the UE context in the AMF already includes an Allowed NSSAI for the corresponding Access Type, based on the configuration for this AMF, the AMF may be allowed to determine whether it can serve the UE (see (A) below for subsequent handling). +- AMF or NSSF may have previously subscribed to slice load level and/or Observed Service Experience and/or Dispersion Analytics related network data analytics for a Network Slice from NWDAF, optionally for an Area of Interest composed of one or several TAIs. If AMF subscribes to analytics, AMF may determine that it cannot serve the UE based on received analytics (see (A) below). If AMF subscribes to notifications on changes on the Network Slice or Network Slice instance availability information from NSSF optionally indicating a list of supported TAIs, it may determine that it cannot serve the UE after the restriction notification is received (see (A) below). If AMF does not subscribe to notifications on changes on the availability information from NSSF, NSSF may take the analytics information into account when AMF queries NSSF (see (B) below). + +NOTE 3: The configuration in the AMF depends on the operator's policy. + +(A) Depending on fulfilling the configuration as described above, the AMF may be allowed to determine whether it can serve the UE, and the following is performed: + +- For the mobility from EPS to 5GS, the AMF first derives the serving PLMN value(s) of S-NSSAI(s) based on the HPLMN S-NSSAI(s) in the mapping of Requested NSSAI (in CM-IDLE state) or the HPLMN S-NSSAI(s) received from SMF+PGW-C (in CM-CONNECTED state). After that the AMF regards the derived value(s) as the Requested NSSAI. + +- For the inter PLMN within 5GC mobility, the new AMF derives the serving PLMN value(s) of S-NSSAI(s) based on the HPLMN S-NSSAI(s) in the mapping of Requested NSSAI. After that the AMF regards the derived value(s) as the Requested NSSAI. +- AMF checks whether it can serve all the S-NSSAI(s) from the Requested NSSAI present in the Subscribed S-NSSAIs (potentially using configuration for mapping S-NSSAI values between HPLMN and Serving PLMN), or all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs in the case that no Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI are permitted, i.e. do not match any of the Subscribed S-NSSAIs or not available at the current UE's Tracking Area (see clause 5.15.3). If the AMF is configured with a local policy to include in the Allowed NSSAI subscribed S-NSSAIs that are not in the Requested NSSAI and some of the Subscribed S-NSSAIs are not supported by the AMF, the AMF queries the NSSF (see (B) below). +- If AMF has subscribed to slice load level and/or Observed Service Experience and/or Dispersion Analytics related network data analytics for a Network Slice from NWDAF, or if AMF had received a Network Slice restriction from NSSF that applies to the list of TAs supported by the AMF, it may use that information to determine whether the AMF can serve the UE on the S-NSSAI(s) in the Requested NSSAI. +- If the AMF can serve the S-NSSAIs in the Requested NSSAI and any additional S-NSSAI added due to local policy as described below, the AMF remains the serving AMF for the UE. The Allowed NSSAI is then determined by taking into account the list of S-NSSAI(s) in the Requested NSSAI permitted based on the Subscribed S-NSSAIs and/or the list of S-NSSAI(s) for the Serving PLMN which are mapped to the HPLMN S-NSSAI(s) provided in the mapping of Requested NSSAI permitted based on the Subscribed S-NSSAIs, or, if neither Requested NSSAI nor the mapping of Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI are permitted, all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs and taking also into account the availability of the Network Slice instances as described in clause 5.15.8 that are able to serve the S-NSSAI(s) in the Allowed NSSAI in the current UE's Tracking Areas in addition to any Network Slice instance restriction for the S-NSSAI(s) in the Allowed NSSAI provided by the NSSF. The AMF based on local policy may determine to include in the Allowed NSSAI additional Subscribed S-NSSAIs e.g. Subscribed S-NSSAIs not marked as default and/or Subscribed S-NSSAIs that were not provided in the Requested NSSAI (See NOTE 4). If the AMF has received NSSRG Information for the Subscribed S-NSSAIs as part of the UE subscription information, it shall only include in the Allowed NSSAI S-NSSAIs that all share a common NSSRG (see clause 5.15.12). If at least one S-NSSAI in the Requested NSSAI is not available in the current UE's Tracking Area, then either the AMF may determine a Target NSSAI or step (B) is executed. The AMF also determines the mapping if the S-NSSAI(s) included in the Allowed NSSAI needs to be mapped to Subscribed S-NSSAI(s) values. If no Requested NSSAI is provided, or the mapping of the S-NSSAIs in Requested NSSAI to HPLMN S-NSSAIs is incorrect, or the Requested NSSAI includes an S-NSSAI that is not valid in the Serving PLMN, or the UE indicated that the Requested NSSAI is based on the Default Configured NSSAI, the AMF, based on the Subscribed S-NSSAI(s) and operator's configuration, may also determine the Configured NSSAI for the Serving PLMN and, if applicable, the associated mapping of the Configured NSSAI to HPLMN S-NSSAIs, so these can be configured in the UE. Then Step (C) is executed. + +NOTE 4: The ability for the AMF to construct the Allowed NSSAI with values not contained in Requested NSSAI but permitted by subscribed NSSAI can be used to allow the UE to use newly-added S-NSSAI(s) in the case of Network Slicing Subscription Change (see clause 4.2.2.2.2 of TS 23.502 [3]). + +- Else, the AMF queries the NSSF (see (B) below). + +(B) When required as described above, the AMF needs to query the NSSF, and the following is performed: + +- The AMF queries the NSSF, with Requested NSSAI, Default Configured NSSAI Indication, mapping of Requested NSSAI to HPLMN S-NSSAIs, the Subscribed S-NSSAIs (with an indication if marked as default S-NSSAI), NSSRG Information (if provided by the UDM, see clause 5.15.12), any Allowed NSSAI it might have for the other Access Type (including its mapping to HPLMN S-NSSAIs), PLMN ID of the SUPI and UE's current Tracking Area. If the AMF has pending NSSAI for the UE then the AMF includes pending NSSAI in the Requested NSSAI. + +NOTE 5: The Default Configured NSSAI Indication is provided when received from the UE or when the AMF indicates to the NSSF to return Configured NSSAI in case of the Network Slicing Subscription Change Indication is received from UDM. + +- Based on this information, local configuration, and other locally available information including RAN capabilities in the current Tracking Area for the UE or load level information for a Network Slice instance provided by the NWDAF, the NSSF does the following: + - It verifies which S-NSSAI(s) in the Requested NSSAI are permitted based on comparing the Subscribed S-NSSAIs with the S-NSSAIs in the mapping of Requested NSSAI to HPLMN S-NSSAIs. It considers the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs in the case that no Requested NSSAI was provided or no S-NSSAI from the Requested NSSAI are permitted i.e. are not present in the Subscribed S-NSSAIs or not available e.g. at the current UE's Tracking Area. If NSSRG information is provided, the NSSF only selects S-NSSAIs that share a common NSSRG (see clause 5.15.12). + - If AMF has not subscribed to notifications on changes on the Network Slice or Network Slice instance availability information from NSSF and NSSF has subscribed to slice load level and/or Observed Service Experience and/or Dispersion Analytics related network data analytics for a Network Slice from NWDAF, NSSF may use the analytics information for the determination of the (Network Slice instance(s) and the) list of S-NSSAI(s) in the Allowed NSSAI(s) to serve the UE. + - It selects the Network Slice instance(s) to serve the UE. When multiple Network Slice instances in the UE's Tracking Area are able to serve a given S-NSSAI, based on operator's configuration, the NSSF may select one of them to serve the UE, or the NSSF may defer the selection of the Network Slice instance until a NF/service within the Network Slice instance needs to be selected. + - It determines the target AMF Set to be used to serve the UE, or, based on configuration, the list of candidate AMF(s), possibly after querying the NRF. + +NOTE 6: If the target AMF(s) returned from the NSSF is the list of candidate AMF(s), the Registration Request message can only be redirected via the direct signalling between the initial AMF and the selected target AMF as described in clause 5.15.5.2.3. The NSSF does not provide the target AMF(s), when it provides a Target NSSAI in order to redirect or handover the UE to a cell of another TA as described in clause 5.3.4.3.3. + +- It determines the Allowed NSSAI(s) for the applicable Access Type, by taking into account the list of S-NSSAI(s) in the Requested NSSAI permitted based on the Subscribed S-NSSAIs and/or the list of S-NSSAI(s) for the Serving PLMN which are mapped to the HPLMN S-NSSAIs provided in the mapping of Requested NSSAI permitted based on the Subscribed S-NSSAIs, or, if neither Requested NSSAI nor the mapping of Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI are permitted, all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs, and taking also into account the availability of the Network Slice instances as described in clause 5.15.8 that are able to serve the S-NSSAI(s) in the Allowed NSSAI in the current UE's Tracking Areas and taking also into account local policy in the NSSF that may determine to include in the Allowed NSSAI additional Subscribed S-NSSAIs e.g. Subscribed S-NSSAIs not marked as default and/or Subscribed S-NSSAIs that were not provided in the Requested NSSAI (see NOTE 7). If NSSRG information applies, the NSSF only selects S-NSSAIs that share a common NSSRG (see clause 5.15.12). + +NOTE 7: The ability for the NSSF to construct the Allowed NSSAI with values not contained in Requested NSSAI but permitted by Subscribed NSSAIs can be used to allow the UE to use newly-added S-NSSAI(s) in the case of Network Slicing Subscription Change (see clause 4.2.2.2.2 of TS 23.502 [3]). + +- It also determines the mapping of each S-NSSAI of the Allowed NSSAI(s) to the Subscribed S-NSSAIs if necessary. +- Based on operator configuration, the NSSF may determine the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s). +- Additional processing to determine the Allowed NSSAI(s) in roaming scenarios and the mapping to the Subscribed S-NSSAIs, as described in clause 5.15.6. +- If no Requested NSSAI is provided or the Requested NSSAI includes an S-NSSAI that is not valid in the Serving PLMN, or the mapping of the S-NSSAIs in Requested NSSAI to HPLMN S-NSSAIs is incorrect, the NSSF based on the Subscribed S-NSSAI(s) and operator configuration may also determine the Configured NSSAI for the Serving PLMN and, if applicable, the associated mapping of the Configured NSSAI to HPLMN S-NSSAIs, so these can be configured in the UE. The NSSF shall return a Configured NSSAI when receiving Default Configured NSSAI Indication from the AMF. + +- If at least one S-NSSAI in the Requested NSSAI is not available in the current UE's Tracking Area, the NSSF may provide a Target NSSAI for the purpose of allowing the NG-RAN to redirect the UE to a cell of a TA in another frequency band supporting network slices not available in the current TA as described in clause 5.3.4.3.3. +- The NSSF returns to the current AMF the Allowed NSSAI for the applicable Access Type, the mapping of each S-NSSAI of the Allowed NSSAI to the Subscribed S-NSSAIs if determined and the target AMF Set, or, based on configuration, the list of candidate AMF(s). The NSSF may return the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s), and the NRF to be used to determine the list of candidate AMF(s) from the AMF Set. The NSSF may return NSI ID(s) to be associated to the Network Slice instance(s) corresponding to certain S-NSSAIs. NSSF may return the rejected S-NSSAI(s) as described in clause 5.15.4.1. The NSSF may return the Configured NSSAI for the Serving PLMN and the associated mapping of the Configured NSSAI to HPLMN S-NSSAIs. The NSSF may return Target NSSAI as described in clause 5.3.4.3.3. +- Depending on the available information and based on configuration, the AMF may query the appropriate NRF (e.g. locally pre-configured or provided by the NSSF) with the target AMF Set. The NRF returns a list of candidate AMFs. +- If AMF Re-allocation is necessary, the current AMF reroutes the Registration Request or forwards the UE context to a target serving AMF as described in clause 5.15.5.2.3. +- Step (C) is executed. + +(C) The serving AMF shall determine a Registration Area such that all S-NSSAIs of the Allowed NSSAI for this Registration Area are available in all Tracking Areas of the Registration Area (and also considering other aspects as described in clause 5.3.2.3 and clause 5.3.4.3.3) and then return to the UE this Allowed NSSAI and the mapping of the Allowed NSSAI to the Subscribed S-NSSAIs if provided. The AMF may return the rejected S-NSSAI(s) as described in clause 5.15.4.1. + +NOTE 8: The S-NSSAIs in the Allowed NSSAI for Non-3GPP access are available homogeneously "in the PLMN" for the N3IWF case since a N3IWF providing access to a 5GC can be reached from any IP location. For other types of Non-3GPP access the S-NSSAIs in the Allowed NSSAI for Non-3GPP access can be not available homogeneously, for example different W-AGFs/TNGF(s) can be deployed in different locations and support different TAIs that support different network slices. + +When either no Requested NSSAI was included, or the mapping of the S-NSSAIs in Requested NSSAI to HPLMN S-NSSAIs is incorrect, or a Requested NSSAI is not considered valid in the PLMN and as such at least one S-NSSAI in the Requested NSSAI was rejected as not usable by the UE in the PLMN, or the UE indicated that the Requested NSSAI is based on the Default Configured NSSAI, the AMF may update the UE slice configuration information for the PLMN as described in clause 5.15.4.2. + +If the Requested NSSAI does not include S-NSSAIs which map to S-NSSAIs of the HPLMN subject to Network Slice-Specific Authentication and Authorization and the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE in the current UE's Tracking Area and if no default S-NSSAI(s) could be added as described in step (A), the AMF shall reject the UE Registration and shall include in the rejection message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. + +If the Requested NSSAI includes S-NSSAIs which map to S-NSSAIs of the HPLMN subject to Network Slice-Specific Authentication and Authorization, the AMF shall include in the Registration Accept message an Allowed NSSAI containing only those S-NSSAIs that are not to be subject to Network Slice-Specific Authentication and Authorization and, based on the UE Context in AMF, those S-NSSAIs for which Network Slice-Specific Authentication and Authorization for at least one of the corresponding HPLMN S-NSSAIs succeeded previously regardless the Access Type, if any. + +The AMF shall also provide the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. + +If the AMF determined the Target NSSAI or received a Target NSSAI from the NSSF, the AMF should provide the Target NSSAI to the PCF for retrieving a corresponding RFSP as described in clause 5.3.4.3.1 or, if the PCF is not deployed, the AMF should determine a corresponding RFSP based on local configuration. Then the AMF provides the Target NSSAI and the corresponding RFSP to the NG-RAN as described in clause 5.3.4.3.3. The S-NSSAIs which map to S-NSSAIs of the HPLMN subject to an ongoing Network Slice-Specific Authentication and Authorization shall be included in the Pending NSSAI and removed from Allowed NSSAI. The Pending NSSAI may contain a mapping of the + +S-NSSAI(s) for the Serving PLMN to the HPLMN S-NSSAIs, if applicable. The UE shall not include in the Requested NSSAI any of the S-NSSAIs from the Pending NSSAI the UE stores, regardless of the Access Type. + +If: + +- all the S-NSSAI(s) in the Requested NSSAI are still to be subject to Network Slice-Specific Authentication and Authorization; or +- no Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI matches any of the Subscribed S-NSSAIs, and all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs are to be subject to Network Slice-Specific Authentication and Authorization; + +the AMF shall provide a "NSSAA to be performed" indicator and no Allowed NSSAI to the UE in the Registration Accept message. Upon receiving the Registration Accept message, the UE is registered in the PLMN but shall wait for the completion of the Network Slice-Specific Authentication and Authorization without attempting to use any service provided by the PLMN on any access, except e.g. emergency services (see TS 24.501 [47]), until the UE receives an allowed NSSAI. + +Then, the AMF shall initiate the Network Slice-Specific Authentication and Authorization procedure as described in clause 5.15.10 for each S-NSSAI that requires it, except, based on Network policies, for those S-NSSAIs for which Network Slice-Specific Authentication and Authorization have been already initiated on another Access Type for the same S-NSSAI(s). At the end of the Network Slice-Specific Authentication and Authorization steps, the AMF by means of the UE Configuration Update procedure shall provide a new Allowed NSSAI to the UE which also contains the S-NSSAIs subject to Network Slice-Specific Authentication and Authorization for which the authentication and authorization is successful. The AMF may perform AMF selection when NSSAA completes for the S-NSSAIs subject to NSSAA. If an AMF change is required, this shall be triggered by the AMF using the UE Configuration Update procedure indicating a UE re-registration is required. The S-NSSAIs which were not successfully authenticated and authorized are not included in the Allowed NSSAI and are included in the list of Rejected S-NSSAIs with a rejection cause value indicating Network Slice-Specific Authentication and Authorization failure. + +Once completed the Network Slice-Specific (re-)Authentication and (re-)Authorization procedure, if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE, which is already authenticated and authorized successfully by a PLMN, and if no default S-NSSAI(s) could be added as described in step (A), the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 of TS 23.502 [3] and shall include in the explicit De-Registration Request message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. + +If an S-NSSAI is rejected with a rejection cause value indicating Network Slice-Specific Authentication and Authorization failure or revocation, the UE can re-attempt to request the S-NSSAI based on policy, local in the UE. + +##### 5.15.5.2.2 Modification of the Set of Network Slice(s) for a UE + +The set of Network Slices for a UE can be changed at any time while the UE is registered with a network, and may be initiated by the network, or by the UE, under certain conditions as described below. + +The network, based on local policies, subscription changes and/or UE mobility and/or UE Dispersion data classification, operational reasons (e.g. a Network Slice instance is no longer available or load level information or service experience for a Network Slice or network slice instance provided by the NWDAF), may change the set of Network Slice(s) to which the UE is registered and provide the UE with a new Registration Area and/or Allowed NSSAI and the mapping of this Allowed NSSAI to HPLMN S-NSSAIs, for each Access Type over which the UE is registered. In addition, the network may provide the Configured NSSAI for the Serving PLMN, the associated mapping information, and the rejected S-NSSAIs. The network may perform such a change over each Access Type during a Registration procedure or trigger a notification towards the UE of the change of the Network Slices using a UE Configuration Update procedure as specified in clause 4.2.4 of TS 23.502 [3]. The new Allowed NSSAI(s) and the mapping to HPLMN S-NSSAIs are determined as described in clause 5.15.5.2.1 (an AMF Re-allocation may be needed). The AMF provides the UE with: + +- an indication that the acknowledgement from UE is required; +- Configured NSSAI for the Serving PLMN (if required), rejected S-NSSAI(s) (if required) and TAI list, and +- the new Allowed NSSAI with the associated mapping of Allowed NSSAI for each Access Type (as applicable) unless the AMF cannot determine the new Allowed NSSAI (e.g. all S-NSSAIs in the old Allowed NSSAI have been removed from the Subscribed S-NSSAIs). + +Furthermore: + +- If the changes to the Allowed NSSAI require the UE to perform immediately a Registration procedure because they affect the existing connectivity to AMF (e.g. the new S-NSSAIs require a separate AMF that cannot be determined by the current serving AMF, or the AMF cannot determine the Allowed NSSAI) or due to AMF local policies also when the changes does not affect the existing connectivity to AMF: +- The serving AMF indicates to the UE the need for the UE to perform a Registration procedure without including the GUAMI or 5G-S-TMSI in the access stratum signalling after entering CM-IDLE state. The AMF shall release the NAS signalling connection to the UE to allow to enter CM-IDLE after receiving the acknowledgement from UE. +- When the UE receives indications to perform a Registration procedure without including the GUAMI or 5G-S-TMSI in the access stratum signalling after entering CM-IDLE state, then: + - The UE deletes any stored (old) Allowed NSSAI and associated mapping as well as any (old) rejected S-NSSAI. + - The UE shall initiate a Registration procedure with the registration type Mobility Registration Update after the UE enters CM-IDLE state as specified in as described in step 4 of clause 4.2.4.2 of TS 23.502 [3]. The UE shall include a Requested NSSAI (as described in clause 5.15.5.2.1) with the associated mapping of Requested NSSAI in the Registration Request message. Also, the UE shall include, subject to the conditions set out in clause 5.15.9, a Requested NSSAI in access stratum signalling but no GUAMI. +- If the AMF determines that the S-NSSAI in the Allowed NSSAI is replaced with Alternative S-NSSAI, the AMF provides the mapping of old S-NSSAI to the Alternative S-NSSAI to the UE (as described in clause 5.15.19). + +If there is an established PDU Session associated with emergency services, then the serving AMF indicates to the UE the need for the UE to perform a Registration procedure but does not release the NAS signalling connection to the UE. The UE performs the Registration procedure only after the release of the PDU Session used for the emergency services. + +In addition to sending the new Allowed NSSAI to the UE, when a Network Slice used for a one or multiple PDU Sessions is no longer available for a UE, the following applies: + +- If the Network Slice becomes no longer available under the same AMF and the Network Slice Replacement is not used (e.g. due to UE subscription change), the AMF indicates to the SMF(s) which PDU Session ID(s) corresponding to the relevant S-NSSAI shall be released. SMF releases the PDU Session according to clause 4.3.4.2 of TS 23.502 [3]. If the Network Slice Replacement is used, the AMF performs Network Slice Replacement as described in clause 5.15.19. +- If the Network Slice becomes no longer available upon a change of AMF (e.g. due to Registration Area change), the new AMF indicates to the old AMF that the PDU Session(s) corresponding to the relevant S-NSSAI shall be released. The old AMF informs the corresponding SMF(s) to release the indicated PDU Session(s). The SMF(s) release the PDU Session(s) as described in clause 4.3.4 of TS 23.502 [3]. Then the new AMF modifies the PDU Session Status correspondingly. The PDU Session(s) context is locally released in the UE after receiving the PDU Session Status in the Registration Accept message. + +The UE uses either the URSP rules (which includes the NSSP) or the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503 [45] to determine whether ongoing traffic can be routed over existing PDU Sessions belonging to other Network Slices or establish new PDU Session(s) associated with same/other Network Slice. + +In order to change the set of S-NSSAIs the UE is registered to over an Access Type, the UE shall initiate a Registration procedure over this Access Type as specified in clause 5.15.5.2.1. + +If, for an established PDU Session: + +- none of the values of the S-NSSAIs of the HPLMN in the mapping of the Requested NSSAI to S-NSSAIs of the HPLMN included in the Registration Request matches the S-NSSAI of the HPLMN associated with the PDU Session; or +- none of the values of the S-NSSAIs in the Requested NSSAI matches the value of the S-NSSAI of HPLMN associated with the PDU Session and the mapping of the Requested NSSAI to S-NSSAIs of the HPLMN is not included in the Registration Request, + +the network shall release this PDU Session as follows. + +- the AMF informs the corresponding SMF(s) to release the indicated PDU Session(s). The SMF(s) release the PDU Session(s) as described in clause 4.3.4 of TS 23.502 [3]. Then the AMF modifies the PDU Session Status correspondingly. The PDU Session(s) context is locally released in the UE after receiving the PDU Session Status from the AMF. + +A change of the set of S-NSSAIs (whether UE or Network initiated) to which the UE is registered may, subject to operator policy, lead to AMF change, as described in clause 5.15.5.2.1. + +If the AMF supports the Network Slice Replacement feature and is configured to use the NSSF to trigger the Network Slice Replacement, the AMF subscribes with the NSSF for notifications when any of the S-NSSAIs served by the AMF (e.g. the S-NSSAI in the Serving PLMN and the HPLMN S-NSSAI in roaming case) has to be replaced as described in clause 5.15.19. + +If the AMF supports the Network Slice Instance Replacement and configured to use Network Slice Instance Replacement, the AMF subscribes with the NSSF for notifications when a Network Slice instances served by the AMF is congested or no longer available as described in clause 5.15.20. + +The AMF may perform Network Slice Replacement for the PDU Session as described in clause 5.15.19. + +##### 5.15.5.2.3 AMF Re-allocation due to Network Slice(s) Support + +During a Registration procedure in a PLMN, if the network decides that the UE should be served by a different AMF based on Network Slice(s) aspects, then the AMF that first received the Registration Request shall redirect the Registration request to target AMF via the 5G-AN or via direct signalling between the initial AMF and the target AMF. If the target AMF(s) are returned from the NSSF and identified by a list of candidate AMF(s), the redirection message shall only be sent via the direct signalling between the initial AMF and the target AMF. If the redirection message is sent by the AMF via the 5G-AN, the message shall include information for selection of a new AMF to serve the UE. + +When during a Registration procedure the UE requests a new S-NSSAI which is not supported in the UE's current Tracking Area, the serving AMF itself or by interacting with the NSSF as described in clause 5.15.5.2.1 may determine a Target NSSAI. The AMF provides the Target NSSAI to the NG-RAN and the NG-RAN may apply redirection or handover of the UE to a cell in another TA supporting the Target NSSAI as described in clause 5.3.4.3.3. + +During a EPS to 5GS handover using N26 interface procedure, if the network decides that the UE should be served by a different AMF based on Network Slice(s) aspects, then the AMF, which received the Forward Relocation Request from MME, shall forward the UE context to target AMF via direct signalling between the initial AMF and the target AMF as described in clause 4.11.1.2.2 of TS 23.502 [3]. + +For a UE that is already registered, the system shall support a redirection initiated by the network of a UE from its serving AMF to a target AMF due to Network Slice(s) considerations (e.g. the operator has changed the mapping between the Network Slice instances and their respective serving AMF(s)). Operator policy determines whether redirection between AMFs is allowed. + +#### 5.15.5.3 Establishing a PDU Session in a Network Slice + +The PDU Session Establishment in a Network Slice instance to a DN allows data transmission in a Network Slice instance. A PDU Session is associated to an S-NSSAI and a DNN. A UE that is registered in a PLMN over an Access Type and has obtained a corresponding Allowed NSSAI, shall indicate in the PDU Session Establishment procedure the S-NSSAI according to the NSSP in the URSP rules or according to the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503 [45], and, if available, the DNN the PDU Session is related to. The UE includes the appropriate S-NSSAI from this Allowed NSSAI and, if mapping of the Allowed NSSAI to HPLMN S-NSSAIs was provided, an S-NSSAI with the corresponding value from this mapping. + +If the UE cannot determine any S-NSSAI after performing the association of the application to a PDU Session according to clause 6.1.2.2.1 of TS 23.503 [45], the UE shall not indicate any S-NSSAI in the PDU Session Establishment procedure. + +The network (HPLMN) may provision the UE with Network Slice selection policy (NSSP) as part of the URSP rules, see clause 6.6.2 of TS 23.503 [45]. When the Subscription Information contains more than one S-NSSAI and the network wants to control/modify the UE usage of those S-NSSAIs, then the network provisions/updates the UE with NSSP as part of the URSP rules. When the Subscription Information contains only one S-NSSAI, the network needs not + +provision the UE with NSSP as part of the URSP rules. The NSSP rules associate an application with one or more HPLMN S-NSSAIs. A default rule which matches all applications to a HPLMN S-NSSAI may also be included. + +The UE shall store and use the URSP rules, including the NSSP, as described in TS 23.503 [45]. When a UE application associated with a specific S-NSSAI requests data transmission: + +- if the UE has one or more PDU Sessions established corresponding to the specific S-NSSAI, the UE routes the user data of this application in one of these PDU Sessions, unless other conditions in the UE prohibit the use of these PDU Sessions. If the application provides a DNN, then the UE considers also this DNN to determine which PDU Session to use. This is further described in clause 6.6.2 of TS 23.503 [45]. +- If the UE does not have a PDU Session established with this specific S-NSSAI, the UE requests a new PDU Session corresponding to this S-NSSAI and with the DNN that may be provided by the application. In order for the RAN to select a proper resource for supporting network slicing in the RAN, RAN needs to be aware of the Network Slices used by the UE. This is further described in clause 6.6.2 of TS 23.503 [45]. + +If the AMF is not able to determine the appropriate NRF to query for the S-NSSAI provided by the UE, the AMF may query the NSSF with this specific S-NSSAI, location information, PLMN ID of the SUPI. The NSSF determines and returns the appropriate NRF to be used to select NFs/services within the selected Network Slice instance. The NSSF may also return an NSI ID to be used to select NFs within the selected Network Slice instance to use for this S-NSSAI. + +The AMF or NSSF may select an S-NSSAI (if the UE does not provide an S-NSSAI for the PDU session establishment) and a Network Slice instance, based on load level and/or Observe Service Experience and/or Dispersion analytics from NWDAF, as described in TS 23.288 [86]. + +The IP address or FQDN of the NSSF is locally configured in the AMF. + +SMF discovery and selection within the selected Network Slice instance is initiated by the AMF when a SM message to establish a PDU Session is received from the UE. The appropriate NRF is used to assist the discovery and selection tasks of the required network functions for the selected Network Slice instance. + +The AMF queries the appropriate NRF to select an SMF in a Network Slice instance based on S-NSSAI, DNN, NSI-ID (if available) and other information e.g. UE subscription and local operator policies, when the UE triggers PDU Session Establishment. The AMF may select the SMF among the set of the SMF instance(s) returned by the NRF or locally configured in the AMF, based on network data analytics (NF load, etc.) from the NWDAF as described in TS 23.288 [86]. The selected SMF establishes a PDU Session based on S-NSSAI and DNN. + +When the AMF belongs to multiple Network Slice instances, based on configuration, the AMF may use an NRF at the appropriate level for the SMF selection. + +For further details on the SMF selection, refer to clause 4.3.2.2.3 of TS 23.502 [3]. + +When a PDU Session for a given S-NSSAI is established using a specific Network Slice instance, the CN provides to the (R)AN the S-NSSAI corresponding to this Network Slice instance to enable the RAN to perform access specific functions. + +The UE shall not perform PDU Session handover from one Access Type to another if the S-NSSAI of the PDU Session is not included in the Allowed NSSAI of the target Access Type. + +### 5.15.6 Network Slicing Support for Roaming + +For roaming scenarios: + +- If the UE only uses standard S-NSSAI values, then the same S-NSSAI values can be used in VPLMN as in the HPLMN. +- If the VPLMN and HPLMN have an SLA to support non-standard S-NSSAI values in the VPLMN, the NSSF of the VPLMN maps the Subscribed S-NSSAIs values to the respective S-NSSAI values to be used in the VPLMN. The S-NSSAI values to be used in the VPLMN are determined by the NSSF of the VPLMN based on the SLA. The NSSF of the VPLMN need not inform the HPLMN of which values are used in the VPLMN. + +Depending on operator's policy and the configuration in the AMF, the AMF may decide the S-NSSAI values to be used in the VPLMN and the mapping to the Subscribed S-NSSAIs. + +For the home routed case, the AMF or NSSF may select an S-NSSAI (if the UE does not provide an S-NSSAI for the PDU session establishment) and a Network Slice instance, based on load level and/or Observe Service Experience and/or Dispersion analytics of the VPLMN and/or that of the HPLMN from NWDAF as described in TS 23.288 [86]. + +- The UE constructs Requested NSSAI and provides the mapping of S-NSSAIs of the Requested NSSAI to HPLMN S-NSSAIs if the mapping is stored in the UE, as described in clause 5.15.5.2.1. +- The NSSF in the VPLMN determines the Allowed NSSAI without interacting with the HPLMN. +- the HPLMN may provide NSSRG Information as part of the Subscription information as described in clause 5.15.12. +- The Allowed NSSAI in the Registration Accept includes S-NSSAI values used in the VPLMN. The mapping information described above is also provided to the UE with the Allowed NSSAI as described in clause 5.15.4. +- If the S-NSSAI values are subject to NSAC, depending on operator's policy, a roaming agreement or an SLA between VPLMN and HPLMN, the AMF or SMF in VPLMN triggers a request for NSAC for these S-NSSAI values as described in clause 5.15.11.3. +- In PDU Session Establishment procedure, the UE includes both: + - (a) the S-NSSAI that matches the application (that is triggering the PDU Session Request) within the NSSP in the URSP rules or within the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503 [45]; the value of this S NSSAI is used in the HPLMN; and + - (b) an S-NSSAI belonging to the Allowed NSSAI that maps to (a) using the mapping of the Allowed NSSAI to HPLMN S-NSSAIs; the value of this S-NSSAI is used in the VPLMN. + +For the home routed case, the AMF may select the V-SMF and the H-SMF based on network data analytics (NF load, etc.) of the VPLMN and that of the HPLMN from the NWDAF as described in TS 23.288 [86]. The V-SMF sends the PDU Session Establishment Request message to the H-SMF along with the S-NSSAI with the value used in the HPLMN (a). If the S-NSSAI values are subject to NSAC, the V-SMF or H-SMF triggers a request for NSAC for these S-NSSAI values as described in clause 5.15.11.3. + +- When a PDU Session is established, the CN provides to the AN the S-NSSAI with the value from the VPLMN corresponding to this PDU Session, as described in clause 5.15.5.3. +- The Network Slice instance specific network functions in the VPLMN are selected by the VPLMN by using the S-NSSAI with the value used in the VPLMN and querying an NRF that has either been pre-configured, or provided by the NSSF in the VPLMN. The Network Slice specific functions of the HPLMN (if applicable) are selected by the VPLMN by using the related S-NSSAI with the value used in the HPLMN via the support from an appropriate NRF in the HPLMN, identified as specified in clause 4.17.5 of TS 23.502 [3] and, for SMF in clause 4.3.2.2.3.3 of TS 23.502 [3]. +- If the serving AMF supports the Network Slice Replacement feature and is configured to use the NSSF for Network Slice Replacement triggering, the AMF subscribes with the NSSF of the VPLMN for notifications when an HPLMN S-NSSAI needs to be replaced with an Alternative S-NSSAI, in addition to notifications for the Serving PLMN S-NSSAIs. The NSSF of the VPLMN shall subscribe with the NSSF of the HPLMN for notifications when an HPLMN S-NSSAI needs to be replaced with an Alternative S-NSSAI. +- If the serving AMF support the Network Slice Instance Replacement and configured to use Network Slice Instance Replacement, the AMF subscribes with the NSSF of the VPLMN for notifications when a Network Slice instance is congested or no longer available as described in clause 5.15.19. The NSSF of the VPLMN shall subscribe with the NSSF of the HPLMN for notifications when the Network Slice instance is congested or no longer available. + +### 5.15.7 Network slicing and Interworking with EPS + +#### 5.15.7.1 General + +A 5GS supports Network Slicing and might need to interwork with the EPS in its PLMN or in other PLMNs as specified in clause 5.17.2. The EPC may support the Dedicated Core Networks (DCN). In some deployments, the MME selection may be assisted by a DCN-ID provided by the UE to the RAN (see TS 23.401 [26]). + +Mobility between 5GC to EPC does not guarantee all active PDU Session(s) can be transferred to the EPC. + +During PDN connection establishment in the EPC, the UE allocates the PDU Session ID and sends it to the SMF+PGW-C via PCO. As described in clause 4.11.0a.5 of TS 23.502 [3], an S-NSSAI associated with the PDN connection is determined based on the S-NSSAI(s) supported by the SMF+PGW-C, the Subscribed S-NSSAI from UDM, whether interworking with EPS is supported for the DNN and S-NSSAI in the Session Management Subscription data and the operator policy by the SMF+PGW-C, e.g. based on a combination of SMF+PGW-C address and APN, and is sent to the UE in PCO together with a PLMN ID that the S-NSSAI relates to. In Home Routed roaming case, the UE receives a HPLMN S-NSSAI value from the SMF+PGW-C. If the SMF+PGW-C supports more than one S-NSSAI and the APN is valid for more than one S-NSSAI, the SMF+PGW-C should only select an S-NSSAI that is mapped to the subscribed S-NSSAI of the UE and this subscribed S-NSSAI is not subject to Network Slice-Specific Authentication and Authorization. The UE stores this S-NSSAI and the PLMN ID associated with the PDN connection. The UE derives Requested NSSAI by taking into account of the received PLMN ID. The Requested NSSAI is included in the NAS Registration Request message and, subject to the conditions in clause 5.15.9, the RRC message carrying this Registration Request when the UE registers in 5GC if the UE is non-roaming or the UE has Configured NSSAI for the VPLMN in roaming case. If the UE has no Configured NSSAI of the VPLMN, the UE includes the HPLMN S-NSSAIs in the NAS Registration Request message as described in clause 5.15.5.2.1. + +When UE moves from EPS to 5GS, AMF reallocation may happen as described in clause 5.15.7.2 and clause 5.15.7.3. + +NOTE: It is assumed that if a MME is configured with a N26 interface towards an AMF, the MME has N26 interfaces with all AMFs serving the same area than the initial AMF and that can serve UE subject to EPS to 5GS mobility. + +#### 5.15.7.2 Idle mode aspects + +In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking with N26: + +- When UE moves from 5GS to EPS, the UE context information sent by AMF to MME includes the UE Usage type, which is retrieved from UDM by AMF as part of subscription data. +- When UE moves from EPS to 5GS, then the UE includes the S-NSSAIs (with values for the Serving PLMN of the target 5GS, if available) associated with the established PDN connections in the Requested NSSAI in RRC Connection Establishment (subject to the conditions set out in clause 5.15.9) and NAS. The UE also provides to the AMF in the Registration Request message the mapping information as described in clause 5.15.6. The UE derives the S-NSSAIs values for the Serving PLMN by using the latest available information from EPS (if received in PCO) and from 5GS (e.g. based on URSP, Configured NSSAI, Allowed NSSAI). In the home-routed roaming case, the AMF selects default V-SMFs. The SMF+PGW-C sends PDU Session IDs and related S-NSSAIs to AMF. The AMF derives S-NSSAI values for the Serving PLMN as described in clause 5.15.5.2.1 and determines whether the AMF is the appropriate AMF to serve the UE. If not, the AMF reallocation may need be triggered. For each PDU Session the AMF determines whether the V-SMF need be reselected based on the associated S-NSSAI value for the Serving PLMN. If the V-SMF need be reallocated, i.e. change from the default V-SMF to another V-SMF, the AMF trigger the V-SMF reallocation as described in clause 4.23.3 of TS 23.502 [3]. + +In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking without N26: + +- When the UE initiates the Registration procedure, and subject to the conditions set out in clause 5.15.9, the UE includes the S-NSSAI (with values for the Serving PLMN of the target 5GS) associated with the established PDN connections in the Requested NSSAI in the RRC Connection Establishment. +- The UE includes the S-NSSAIs (with values for the Serving PLMN of the target 5GS, if available) and the HPLMN S-NSSAI received in the PCO for the PDN connections as mapping information when moving PDN connections to 5GC using PDU Session Establishment Request message. The UE derives the S-NSSAIs values + +for the Serving PLMN by using, the latest available information from EPS (if received in PCO) and from 5GS (e.g. based on URSP, Configured NSSAI, Allowed NSSAI). + +#### 5.15.7.3 Connected mode aspects + +In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking with N26: + +- When a UE is CM-CONNECTED in 5GC and a handover to EPS occur, the AMF selects the target MME based on the source AMF Region ID, AMF Set ID and target location information. The AMF forwards the UE context to the selected MME over the N26 Interface. In the UE context, the AMF also includes the UE Usage type, if it is received as part of subscription data. The Handover procedure is executed as documented in TS 23.502 [3]. When the Handover procedure completes successfully the UE performs a Tracking Area Update. This completes the UE registration in the target EPS. As part of this the UE obtains a DCN-ID if the target EPS uses it. +- When a UE is ECM-CONNECTED in EPC, and performs a handover to 5GS, the MME selects the target AMF based on target location information, e.g. TAI and any other available local information (including the UE Usage Type if one is available for the UE in the subscription data) and forwards the UE context to the selected AMF over the N26 interface. In the home-routed roaming case, the AMF selects default V-SMFs. The Handover procedure is executed as documented in TS 23.502 [3]. The SMF+PGW-C sends PDU Session IDs and related S-NSSAIs to AMF. Based on the received S-NSSAIs values the target AMF derives the S-NSSAI values for the Serving PLMN, the target AMF reselects a final target AMF if necessary as described in clause 5.15.5.2.1, the AMF reallocation procedure is triggered. For each PDU Session based on the associated derived S-NSSAI values if the V-SMF need be reallocated, the final target AMF triggers the V-SMF reallocation as described in clause 4.23.2 of TS 23.502 [3]. When the Handover procedure completes successfully the UE performs a Registration procedure. This completes the UE registration in the target 5GS and as part of this the UE obtains an Allowed NSSAI. + +#### 5.15.7.4 Support of Network Slice usage control and Interworking with EPC + +As described in clause 5.15.15, if Network Slice usage control is required for a PDN Connection, the SMF+PGW-C configures PDU Session inactivity timer to the UPF+PGW-U. When the SMF+PGW-C receives inactivity report of the PDN Connection from the UPF+PGW-U, the SMF+PGW-C releases the PDN Connection. + +### 5.15.8 Configuration of Network Slice availability in a PLMN + +A Network Slice may be supported in the whole PLMN or in one or more Tracking Areas of the PLMN. Network Slices may also be available with an NS-AoS not matching deployed Tracking Areas as defined in clause 5.15.18. + +The availability of a Network Slice refers to the support of the S-NSSAI in the involved NFs. In addition, policies in the NSSF may further restrict from using certain Network Slices in a particular TA, e.g. depending on the HPLMN of the UE. The UE can receive, for a Network Slice where the NS-AoS does not match the whole set of cells in one or more TAs, S-NSSAI location availability information as described in clause 5.15.18. + +The support of a Network Slice in a TA is established end-to-end using a combination of OAM and signalling among network functions. It is derived by using the S-NSSAIs supported per TA in 5G-AN, the S-NSSAIs supported in the AMF and operator policies per TA in the NSSF. + +The AMF learns the S-NSSAIs supported per TA by the 5G-AN when the 5G-AN nodes establish or update the N2 connection with the AMF (see TS 38.413 [34] and TS 38.300 [27]). One or all AMF per AMF Set provides and updates the NSSF with the S-NSSAIs support per TA. The 5G-AN learns the S-NSSAIs per PLMN ID the AMFs it connects to support when the 5G-AN nodes establishes the N2 connection with the AMF or when the AMF updates the N2 connection with the 5G-AN (see TS 38.413 [34] and TS 38.300 [27]). + +The NSSF may be configured with operator policies specifying under what conditions the S-NSSAIs can be restricted per TA and per HPLMN of the UE. + +The per TA restricted S-NSSAIs may be provided to the AMFs of the AMF Sets at setup of the network and whenever changed. + +The AMF may be configured for the S-NSSAIs it supports with operator policies specifying any restriction per TA and per HPLMN of the UE. + +### 5.15.9 Operator-controlled inclusion of NSSAI in Access Stratum Connection Establishment + +The Serving PLMN can control per Access Type which (if any) NSSAI the UE includes in the Access Stratum when establishing a connection caused by Service Request, Periodic Registration Update or Registration procedure used to update the UE capabilities. In addition, the Home and Visited PLMNs can also instruct the UE to never include NSSAI in the Access Stratum, regardless of the procedure that causes a RRC Connection to be established, i.e. to always enable privacy for the NSSAI). + +During the Registration procedure, the AMF may provide to the UE in the Registration Accept message, an Access Stratum Connection Establishment NSSAI Inclusion Mode parameter, indicating whether and when the UE shall include NSSAI information in the Access Stratum Connection Establishment (e.g. an RRC connection Establishment defined in TS 38.331 [28]) according to one of these modes: + +- a) The UE shall include an NSSAI set to the Allowed NSSAI, if available, in the Access Stratum Connection Establishment caused by a Service Request, Periodic Registration Update or Registration procedure used to update the UE capabilities; +- b) The UE shall include a NSSAI with the following content: + - for the case of Access Stratum Connection Establishment caused by a Service Request: an NSSAI including the S-NSSAI(s) of the Network Slice(s) that trigger the Access Stratum Connection Establishment; i.e. all the S-NSSAIs of the PDU sessions that have the User Plane reactivated by the Service Request, or the S-NSSAIs of the Network Slices a Control Plane interaction triggering the Service Request is related to, e.g. for SM it would be the S-NSSAI of the PDU Session the SM message is about; + - for the case of Access Stratum Connection Establishment caused by a Periodic Registration Update or Registration procedure used to update the UE capabilities, an NSSAI set to the Allowed NSSAI; +- c) The UE shall not include any NSSAI in the Access Stratum Connection Establishment caused by Service Request, Periodic Registration Update or Registration procedure used to update the UE capabilities; or +- d) The UE shall not provide NSSAI in the Access stratum. + +For the case of Access Stratum Connection Establishment caused by Mobility Registration Update or Initial Registration in modes a), b) or c) the UE shall include the Requested NSSAI provided by the NAS layer and defined in clause 5.15.5.2.1. + +For all UEs that are allowed to use modes a), b) or c), the Access Stratum Connection Establishment NSSAI Inclusion Mode should be the same over the same Registration Areas. The UE shall store and comply to the required behaviour for a PLMN per Access Type as part of the network slicing configuration. The Serving PLMN AMF shall not instruct the UE to operate in any other mode than mode d) in 3GPP Access Type unless the HPLMN provides an indication that it is allowed to do so (i.e. if a PLMN allows behaviours a,b,c, then its UDM sends to the serving AMF an explicit indication that the NSSAI can be included in RRC as part of the subscription data). + +The UE default mode of operation is the following: + +- For 3GPP access the UE shall by default operate in mode d) unless it has been provided with an indication to operate in mode a), b) or c). +- For untrusted non-3GPP access the UE shall operate by default in mode b) unless it has been provided with an indication to operate in mode a), c) or d). +- For trusted non-3GPP access the UE shall operate by default in mode d) unless it has been provided with an indication to operate in mode a), b) or c). +- For W-5GAN access the 5G-RG shall operate by default in mode b) unless it has been provided with an indication to operate in mode a), c) or d). + +An operator may pre-configure the UE to operate by default according to mode c) in the HPLMN (i.e. the UE by default includes NSSAI in the access stratum when it performs an Initial Registration and Mobility Registration Update with the HPLMN until the HPLMN changes the mode as described above). + +### 5.15.10 Network Slice-Specific Authentication and Authorization + +A serving PLMN or SNPN shall perform Network Slice-Specific Authentication and Authorization for the S-NSSAIs of the HPLMN or SNPN which are subject to it based on subscription information. The UE shall indicate in the Registration Request message in the UE 5GMM Core Network Capability whether it supports NSSAA feature. If the UE does not support NSSAA feature and if the UE requests any of these S-NSSAIs that are subject to Network Slice-Specific Authentication and Authorization, the AMF shall not trigger this procedure for the UE and they are rejected for the PLMN or SNPN. If the UE supports NSSAA feature and if the UE requests any of these S-NSSAIs that are subject to Network Slice-Specific Authentication and Authorization, they are included in the list of Pending NSSAI for the PLMN or SNPN, as described in clause 5.15.5.2.1. + +If a UE is configured with S-NSSAIs, which are subject to Network Slice-Specific Authentication and Authorization, the UE stores an association between the S-NSSAI and corresponding credentials for the Network Slice-Specific Authentication and Authorization. + +NOTE 1: How the UE is aware that an S-NSSAI is subject to Network Slice-Specific Authentication and Authorization (e.g. based on local configuration) is out of scope of this specification. + +The UE may support remote provisioning of credentials for NSSAA, specified in clause 5.39. + +A UE that supports to be provisioned with the credentials used for NSSAA over UP remote provisioning shall use connectivity over an S-NSSAI/DNN which can access the provisioning server to establish a PDU session for remote provisioning as defined in clause 5.39. + +NOTE 2: The credentials for Network Slice-Specific Authentication and Authorization are not specified. + +To perform the Network Slice-Specific Authentication and Authorization for an S-NSSAI, the AMF invokes an EAP-based Network Slice-Specific authorization procedure documented in clause 4.2.9 of TS 23.502 [3] (see also TS 33.501 [29]) for the S-NSSAI. When an NSSAA procedure is started and is ongoing for an S-NSSAI, the AMF stores the NSSAA status of the S-NSSAI as pending and when the NSSAA is completed the S-NSSAI becomes either part of the Allowed NSSAI or a Rejected S-NSSAI. The NSSAA status of each S-NSSAI, if any is stored, is transferred when the AMF changes. + +This procedure can be invoked for a supporting UE by an AMF at any time, e.g. when: + +- a. The UE registers with the AMF and one of the S-NSSAIs of the HPLMN or SNPN which maps to an S-NSSAI in the Requested NSSAI is requiring Network Slice-Specific Authentication and Authorization (see clause 5.15.5.2.1 for details), and the S-NSSAI in the Requested NSSAI can be added to the Allowed NSSAI by the AMF once the Network Slice-Specific Authentication and Authorization for the HPLMN or SNPN S-NSSAI succeeds; or +- b. The Network Slice-Specific AAA Server triggers a UE re-authentication and re-authorization for an S-NSSAI; or +- c. The AMF, based on operator policy or a subscription change, decides to initiate the Network Slice-Specific Authentication and Authorization procedure for a certain S-NSSAI which was previously authorized. + +In the case of re-authentication and re-authorization (b. and c. above) the following applies: + +- If S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization map to S-NSSAIs that are included in the Allowed NSSAI for each Access Type, AMF selects an Access Type to be used to perform the Network Slice Specific Authentication and Authorization procedure based on network policies. +- If the Network Slice-Specific Authentication and Authorization for some S-NSSAIs mapped to some S-NSSAIs in the Allowed NSSAI is unsuccessful, the AMF shall update the Allowed NSSAI for each Access Type to the UE via UE Configuration Update procedure. +- If the Network Slice-Specific Authentication and Authorization fails for all S-NSSAIs mapped to all S-NSSAIs in the Allowed NSSAI, the AMF determines a new Allowed NSSAI including default S-NSSAI(s). If no default S-NSSAI(s) could be added, the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 of TS 23.502 [3] and shall include in the explicit De-Registration Request message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. + +After a successful or unsuccessful UE Network Slice-Specific Authentication and Authorization, the UE context in the AMF shall retain the authentication and authorization status for the UE for the related specific S-NSSAI of the HPLMN + +or SNPN while the UE remains RM-REGISTERED in the PLMN or SNPN, so that the AMF is not required to execute a Network Slice-Specific Authentication and Authorization for a UE at every Periodic Registration Update or Mobility Registration procedure with the PLMN or SNPN. + +A Network Slice-Specific AAA server may revoke the authorization or challenge the authentication and authorization of a UE at any time. When authorization is revoked for an S-NSSAI that maps to an S-NSSAI in the current Allowed NSSAI for an Access Type, the AMF shall provide a new Allowed NSSAI to the UE and trigger the release of all PDU sessions associated with the S-NSSAI, for this Access Type. + +The AMF provides the GPSI of the UE related to the S-NSSAI to the AAA Server to allow the AAA server to initiate the Network Slice-Specific Authentication and Authorization, or the Authorization revocation procedure, where the current AMF serving the UE needs to be identified by the system, so the UE authorization status can be challenged or revoked. + +The Network Slice-Specific Authentication and Authorization requires that the UE Primary Authentication and Authorization of the SUPI has successfully completed. If the SUPI authorization is revoked, then also the Network Slice-Specific authorization is revoked. + +### 5.15.11 Network Slice Admission Control + +#### 5.15.11.0 General + +The Network Slice Admission Control Function (NSACF) monitors and controls the number of registered UEs per network slice and/or the number of PDU Sessions per network slice for the network slices that are subject to Network Slice Admission Control (NSAC). The NSACF is configured with the maximum number of UEs and/or the maximum number of PDU Sessions allowed to be served per S-NSSAI subject to NSAC. The NSACF is also configured with information indicating applicable access type(s) for the S-NSSAI (i.e. 3GPP Access Type, Non-3GPP Access Type, or both). + +The NSACF also provides event-based Network Slice status notifications and reports to the consumer NFs (e.g. AF). + +A NSACF can be configured with the NSAC Service Area(s) it serves. The NSAC Service Area Identifier is a unique identifier in a PLMN or SNPN. The consumer NFs which use the NSAC services are configured with a single and network slice independent value of the NSAC Service Area Identifier so they can discover the correct NSACF (see clause 6.3.22). + +The NSACF may be responsible for one or more S-NSSAIs. For one S-NSSAI there may be one or multiple NSACFs deployed in a network (a PLMN or a SNPN) as follows: + +- If a PLMN or SNPN is configured with a single NSAC service area, there is a single NSACF configured with the maximum number of UEs per network slice and/or the maximum number of PDU Sessions per network slice, which are valid in the network. In this case there is no need to provision any NSAC Service Area Identifier value in the PLMN or SNPN. +- If a PLMN or SNPN is configured with multiple NSAC service areas, an NSACF may be deployed on a NSAC service area basis, which can be one NSACF instance or one NSACF Set. There are three NSAC architecture options: + - Option 1: non-Hierarchical NSAC architecture. In this architecture, independent NSACFs are deployed in every NSAC service area. There is no interaction between the NSACFs deployed in different NSAC service areas. Each NSACF is configured with the maximum number of UEs per network slice and/or the maximum number of PDU Sessions which are valid in the NSAC service area (see clauses 5.15.11.1.1 and 5.15.11.2.1 for more details). + - Option 2: Centralized NSAC architecture. In this architecture, a single centralized NSACF is deployed in the network to handle admissions in all NSAC service areas. The centralized NSACF is configured with the total number of UEs per network slice and the maximum number of PDU Sessions for the entire PLMN. NSAC Requests from AMF or SMF to the single centralized NSCAF in this case includes the NSAC service area of the NF consumer if multiple NSAC service areas are deployed in PLMN. + +NOTE 1: It is possible to configure in the centralized architecture the maximum number of registered UEs and/or the maximum number of PDU sessions per NSAC service area if required by the operator. In this case, NSAC can be performed on a per NSAC service area. + +- Option 3: Hierarchical NSAC architecture is deployed in the network. There are two roles of NSACF and interaction between them may be required (see clauses 5.15.11.1.2 and 5.15.11.2.2 for more details): + - Primary NSACF, controls and distributes of the maximum number of UEs and/or the maximum number of PDU Sessions for other NSACF(s) deployed in different NSAC service Area. The Primary NSACF handles overall NSAC for an S-NSSAI at the global level (i.e. it is ultimately responsible for the NSAC for an S-NSSAI). + - NSACF is responsible for one or multiple NSAC service Area. And one NSAC service area is only associated with one NSACF instance or one NSACF Set. + +NOTE 2: When multiple NSACFs are deployed, how the maximum number of UEs per network slice and the maximum number of PDU Sessions per network slice is distributed (by OAM for Option 1 and by the primary NSACF for Option 3) among multiple NSACFs, i.e. the algorithm of the maximum number distribution, is implementation specific. + +NOTE 3: When multiple NSACFs are deployed based on option 1, the UE moves to new NSAC service area with a different NSACF, and if the number of UE or PDU Sessions in the target NSACF has reached the maximum number, whether the session continuity can be guaranteed is left to implementation. + +NOTE 4: When multiple NSACFs are deployed based on Hierarchical NSAC architecture, it is possible that the role of Primary NSACF and the role of NSACF are co-located at the same NSACF instance. + +Subject to operator policy and national/regional regulations, the AMF may exempt UEs and the SMF may exempt PDU sessions from NSAC when the UE and/or PDU Session is used for Emergency service or for Critical and Priority services (e.g. MCX, MPS). + +When the AMF receives a Registration Request for an Emergency Registration, or with a Registration Request with an Establishment Cause indicating a priority service (e.g. MCX, MPS) or when the AMF determines that there is a priority subscription (e.g. MPS, MCX) in the UDM, the AMF may accept the registration request without applying NSAC, i.e. the AMF triggers the NSAC procedure, but the response from the NSACF is ignored at the AMF. + +When the SMF receives a PDU Session Establishment Request for an emergency PDU Session or a PDU Session Establishment Request with a priority header, the SMF may accept the PDU Session Establishment Request without applying NSAC, i.e. the SMF triggers the NSAC procedure, but the response from the NSACF is ignored at the SMF. + +Alternatively, when NSAC is exempted for the UE and/or PDU Session, the AMF and the SMF skip the corresponding NSAC procedure, i.e. this UE (respectively PDU Session) is not counted towards the maximum number of UEs (respectively PDU Sessions). + +The support of NSAC for the S-NSSAI used for onboarding as described in clause 5.30.2.10 is optional and subject to Onboarding Network operator policies. However, NSAC for S-NSSAI used for onboarding is not applicable to UEs that registered in ON-SNPN with Registration Type "SNPN Onboarding". + +In the case of NSAC for maximum number of PDU Sessions, when the NSACF rejects the request from the SMF to increase the number of PDU Sessions, the SMF may provide to the UE a back-off timer associated with reject cause set to 'Maximum number of PDU Sessions per S-NSSAI reached' for an Access Type as described in clause 4.2.11.4 of TS 23.502 [3]. If the UE receives from the SMF a back-off timer associated with the reject cause set to 'Maximum number of PDU Sessions per S-NSSAI reached' for an Access Type, the UE shall not request the establishment of a PDU Session for this S-NSSAI on the indicated Access Type until the back-off timer expires. + +#### 5.15.11.1 Network Slice Admission Control for maximum number of UEs + +##### 5.15.11.1.1 Non-Hierarchical NSAC architecture + +The NSACF keeps track of the current number of UEs registered for a network slice so that it can ensure it does not exceed the maximum number of UEs allowed to register with the network slice. The NSACF also maintains a list of UE IDs registered with a network slice that is subject to NSAC. When an event related to a UE causes the current number of UEs registered with a network slice to increase, the NSACF first checks whether the UE Identity is already in the list of UEs registered with that network slice. If not, the NSACF checks whether the maximum number of UEs per network slice for that network slice has already been reached and if it has, the NSACF applies admission control policies. + +The AMF triggers a request to NSACF for NSAC for maximum number of UEs when the UE's registration status for a network slice subject to NSAC is changing, i.e. during the UE Registration procedure in clause 4.2.2.2.2 of + +TS 23.502 [3], UE Deregistration procedure in clause 4.2.2.3 of TS 23.502 [3], Network Slice-Specific Authentication and Authorisation procedure in clause 4.2.9.2 of TS 23.502 [3], AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure in clause 4.2.9.3 of TS 23.502 [3], AAA Server triggered Slice-Specific Authorization Revocation in clause 4.2.9.4 of TS 23.502 [3] and UE Configuration Update procedure in clause 4.2.4.2 of TS 23.502 [3]. + +NOTE 1: Early Admission Control (EAC) mode is applicable for Number of UEs per network slice admission control. The use of EAC in relation to the number of registered UEs is described in clauses 4.2.11.2 and 4.2.11.3 of TS 23.502 [3]. + +Since the UE may register or deregister for an S-NSSAI via 3GPP access and/or non-3GPP access as described in clause 5.15.5.2.1. The Allowed NSSAI for the access type may change while the UE is registering to a network. The AMF provides the Access Type to the NSACF when triggering a request to increase or decrease the current number of UEs registered with a S-NSSAI. The NSACF may take the Access Type into account for increasing and decreasing the number of UEs per network slice by storing the UE ID with the associated one or more Access Type(s), i.e. the NSACF is able to add or remove a registration for the UE ID for each Access Type and trigger the increase or decrease of the current number of UEs registered with a S-NSSAI based on a policy that takes the access type into account. If the Access Type provided by the AMF is not configured for NSAC in the NSACF, the NSACF always accepts the request from the AMF without increasing or decreasing the number of UEs. If the Access Type provided by the AMF is configured for NSAC in the NSACF and the maximum number is reached, the NSACF sends a reject response to the AMF including the access type. + +NOTE 2: For example, if the NSACF is configured to apply NSAC for 3GPP Access Type only, the NSACF counts registration via 3GPP access type only. If the NSACF is configured to apply NSAC for both Access Types, and the UE newly registers via 3GPP access while the UE is already registered via non-3GPP access (or vice versa), the NSACF updates the UE ID entry with both 3GPP Access Type and non-3GPP Access Type and the NSACF may count the UE once or twice based on its policy. + +##### 5.15.11.1.2 Hierarchical NSAC architecture + +In the Hierarchical NSAC architecture, the NSACFs deployed in the NSAC service areas interacts with the Primary NSACF when needed, and as explained below. + +The main differences between the non-Hierarchical architecture and the Hierarchical architecture is that the AMFs and the NSACFs deployed in the Hierarchical architecture support the following: + +- When the AMF triggers an NSAC request to the NSACF, the AMF includes the UE already Registered indication if the AMF can determine that the UE has been registered with the S-NSSAI in one NSAC service area before. If the AMF does not include the UE already Registered indication, the registration request to the indicated S-NSSAI is determined as initial registration, i.e. the UE has not been registered in any service area before. The AMF determines the UE already Registered indication based on the received Allowed NSSAI information from the source AMF (in case of inter AMF handover) or from SMF+PGW-C (in case of mobility from EPS to 5GS). +- There are two types of UE admission control: quota-based control or threshold-based control. A PLMN is configured to deploy only one type of UE admission control. Based on the type of UE admission control configured for the PLMN, the NSACF handles the NSAC request as described below: + - For NSACFs supporting quota-based control, if the NSACF receives a request to increase the number of UEs and the number of UEs registered for a network slice has reached the local maximum number of UEs provisioned in the NSACF, or upon receiving a request to decrease the number of UEs and no UE entry is present in the NSACF, the NSACF interacts with the Primary NSACF for the handling of the NSAC request for the UE. The Primary NSACF may return in the response an updated local maximum number of registered UEs value to the NSACF based on the status of registered UEs for the Network Slice and which enables the NSACF to handle locally the request. Alternatively, and if the request to increase the number of UEs includes the UE already Registered indication, the Primary NSACF may admit the UE request and store the UE entry which allows for service continuity. The Primary NSACF may also reject the request. If the NSACF receives a request to increase the number of UEs and the local maximum number of UEs is not reached, the NSACF handles the request locally and sends a response to the AMF without interaction with the Primary NSACF. + - For NSACF supporting threshold-based control, the NSACF is initially configured with a UE admission threshold and a local maximum number of Registered UEs to be admitted. Threshold-based control refers to an admission threshold, defined in percentage, against provisioned local maximum number in NSACF (e.g. + +an admission threshold of 80% refers to the case when 80% of the provisioned local maximum number should be used). If upon a receiving a request to increase the number of UEs without a UE already Registered indication and if UE admission threshold is at or above the threshold level configured at the NSACF, the NSACF immediately rejects the NSAC request. If the received request includes the UE already Registered indication and if UE admission is at or above the threshold level configured at the NSACF, the NSACF accepts the request to enable UE admission and allow for service continuity as long as the local maximum number of Registered UEs have not been reached. If the local maximum number of registered UEs value have been reached, the NSACF interacts with the Primary NSACF for the handling of the NSAC request for the UE. The NSACF does not include the UE already Registered indication in this case. The Primary NSACF may return an updated UE admission threshold value to the NSACF in the response which enables the NSACF to handle the request locally. Alternatively, the Primary NSACF may handle and store the UE entry. The Primary NSACF may also reject the request. + +- For both options, the Primary NSACF supports the following capabilities depending on the NSACF configuration: + - Returning a new updated local maximum number of Registered UEs for the NSACF to admit if the NSACF is configured to support the quota-based UE admission control; or + - Returning a new updated UE admission threshold for the NSACF to apply if the NSACF is configured to support the threshold-based UE admission control; + - The Primary NSACF handles, stores entries only related to UEs which the NSAC request includes the UE already Registered indication, that are already admitted in an existing NSAC service area but cannot be admitted in the new NSAC service area due to no remaining local maximum number of registered UEs, as long as the overall PLMN number of registered UEs at the Primary NSACF is not exhausted. The Primary NSACF informs the NSACF in its response; + - Based on the response from the Primary NSACF, the NSACF determines whether to accept or reject the NSAC request for UE registration. In addition, the NSACF may also update the local maximum number of Registered UEs or admission threshold respectively if the related updated value is received; + - At any time, the Primary NSACF can update the NSACFs local maximum number of Registered UEs or admission threshold through the Nnsacf\_NSAC\_LocalNumberUpdate operation as described in clause 4.2.11.6 of TS 23.502 [3]. The updated values provided from the Primary NSACF to the NSACFs may directly apply to current NSAC pending request in NSACF and are used for all future requests. +- The Primary NSACF subscribes with all NSACFs to obtain the number of currently registered UEs at all NSACFs. Based on the obtained information, the Primary NSACF can update the NSACF with local maximum number of registered UEs. + +##### 5.15.11.1.3 Centralized NSAC architecture + +The main differences between the NSACFs deployed in a non-Hierarchical architecture and NSACFs deployed in a Centralized NSAC architecture is as follows: + +- If multiple NSAC service areas are deployed in PLMN, the AMF provides the NSAC Service Area Identifier information to the centralized NSACF. The centralized NSACF also stores the NSAC Service Area Identifier of the AMF the UE is registered with. + +#### 5.15.11.2 Network Slice Admission Control for maximum number of PDU sessions + +##### 5.15.11.2.1 Non- Hierarchical NSAC architecture + +The NSACF keeps track of the current number of PDU Sessions per network slice so that it can ensure it does not exceed the maximum number of PDU session allowed to be served by the network slice. When an event related to a UE causes the current number of PDU sessions established within the network slice is to increase, the NSACF checks whether the maximum number of PDU sessions per network slice for that network slice has already been reached and if it has, the NSACF applies admission control policies. + +The anchor SMF triggers a request to NSACF for maximum number of PDU sessions per network slice control during PDU session establishment/release procedures in clauses 4.3.2 and 4.3.4 of TS 23.502 [3]. + +The SMF provides the Access Type to the NSACF when triggering a request to increase or decrease the number of PDU Sessions. The NSACF takes Access Type into account for increasing and decreasing the current number of PDU Sessions depending on the applicability of the Access Type for the NSAC for maximum number of PDU Sessions for the S-NSSAI. + +NOTE 1: For MA PDU Session, the SMF provides the Access Type to NSACF when the user plane connection is about to be established or released in the corresponding access network. With this, the SMF provides one or two Access Types for the MA PDU Session in the same request message to the NSACF. The NSACF can reject a single or both Access Types depending on the applicability of the Access Type for the NSAC. + +NOTE 2: I-SMF does not interact with NSCAF. + +##### 5.15.11.2.2 Hierarchical NSAC architecture + +The main differences between the NSACFs deployed in a non-Hierarchical architecture and NSACFs deployed in a Hierarchical architecture is as follows: + +- The NSCAF is enhanced to support PDU session admission quota-based control. +- When the local maximum number of PDU sessions is reached, the NSACF interacts with the Primary NSACF to handle the request. The Primary NSACF either return an increased local maximum number to the NSACF, or reject the local maximum number value update request if all the global maximum number are consumed based on the status of established PDU sessions to the network slice. + +NOTE: For Hierarchical NSAC architecture global maximum number used within this specification is synonymous with the maximum number of allowed registered UEs or established PDU Sessions for an S-NSSAI subject to Network Slice Admission Control (NSAC) for the entire PLMN and outbound roamers. + +- Based on the response from Primary NSACF, the NSACF updates the local maximum number if updated value is received from the Primary NSACF. The NSACF updates local maximum number value (if received) and determines whether to accept or reject the NSAC request for PDU session establishment based on the local maximum number value. +- The update of local maximum number value by the Primary NSACF can also happen at any time through the Nnsacf\_NSAC\_LocalNumberUpdate service operation as described in clause 4.2.11.6 TS 23.502 [3]. The updated values provided from the Primary NSACF to NSACFs may directly apply to current NSAC pending request in NSACF and are used for all future requests. +- The Primary NSACF subscribes with all NSACFs to obtain the number of currently established PDU sessions at all NSACFs. Based on the obtained information, the Primary NSACF can update the NSACF with local maximum number of established PDU sessions. + +##### 5.15.11.2.3 Centralized NSAC architecture + +The main differences between the NSACFs deployed in a non-Hierarchical NSAC architecture and NSACFs deployed in a Centralized NSAC architecture is as follows + +- If multiple NSAC service areas are deployed in a PLMN, the SMF provides the NSAC Service Area Identifier to the centralized NSACF. The centralized NSACF also stores the NSAC Service Area Identifier of the SMF the PDU session is established on. + +#### 5.15.11.3 Network Slice Admission Control for Roaming + +##### 5.15.11.3.0 General + +In the case of roaming, depending on operator's policy, a roaming agreement or an SLA between the VPLMN and the HPLMN, NSAC of roaming UEs is performed by one of the following modes of NSAC admission: + +- VPLMN NSAC Admission; or +- VPLMN with HPLMN assistance NSAC Admission; or +- HPLMN NSAC Admission. + +The VPLMN (AMF and SMF) identifies the mode to apply from the AMF subscription data at UE registration, and from the SMF subscription data at PDU session establishment. + +For all the above modes, for NSAC of roaming UEs for maximum number of UEs per network slice and/or maximum number of PDU Sessions per network slice managed by the VPLMN, each S-NSSAI of the HPLMN that is subject to NSAC is mapped to a corresponding S-NSSAI of the VPLMN subject to NSAC. + +For both VPLMN NSAC Admission and VPLMN with HPLMN assistance NSAC Admission modes, each configured S-NSSAI that is subject to NSAC and that is mapped from the HPLMN S-NSSAI, the SMF performs NSAC for home routed PDU sessions according to the principles described in clause 5.15.11.2. + +##### 5.15.11.3.1 VPLMN NSAC Admission Mode + +For NSAC of roaming UEs for maximum number of UEs per network slice and/or maximum number of PDU Sessions per network slice managed by the VPLMN, the following principles shall be used: + +- For NSAC for the maximum number of UEs for S-NSSAI of the HPLMN, a NSACF in the VPLMN can be configured with the maximum number of allowed roaming UEs per mapped S-NSSAI of the HPLMN for a S-NSSAI of the HPLMN that is subject to NSAC. In such a case, the AMFs trigger a request to a NSACF of the VPLMN. +- For NSAC for the maximum number of PDU Sessions for S-NSSAI of the HPLMN, a NSACF in the VPLMN can be configured with the maximum number of allowed PDU Sessions in LBO mode per mapped S-NSSAI of the HPLMN for a S-NSSAI of the HPLMN that is subject to NSAC. In such a case, the anchor SMF in the VPLMN triggers a request to a NSACF of the VPLMN. +- For NSAC for the maximum number of UEs for S-NSSAI of the VPLMN, AMFs trigger a request to a NSACF of the VPLMN to perform NSAC based on the S-NSSAI of the VPLMN subject to NSAC. The NSACF of the HPLMN is not involved. +- For NSAC for the maximum number of PDU Sessions for S-NSSAI of the VPLMN in the LBO roaming case, the SMF triggers a request to a NSACF of the VPLMN to perform NSAC based on the S-NSSAI of the VPLMN subject to NSAC. The NSACF of the HPLMN is not involved. +- The AMF or SMF (in LBO roaming case) in the VPLMN provides both the S-NSSAI in the VPLMN and the corresponding mapped S-NSSAI in the HPLMN to the NSACF in the VPLMN. The NSACF in the VPLMN performs NSAC for both S-NSSAI of the VPLMN and the corresponding mapped S-NSSAI of the HPLMN based on the SLA between the VPLMN and the HPLMN. + +In addition to configuring the VPLMN NFs with the maximum number of allowed roaming UEs per mapped S-NSSAI of the HPLMN subject to NSAC, and the maximum number of allowed PDU Sessions in LBO mode per mapped S-NSSAI of the HPLMN subject to NSAC, the VPLMN can optionally fetch this information from the HPLMN primary NSACF in a hierarchical architecture or centralized NSACF in a centralized architecture. If the NSACF in VPLMN does not have quota configured but can receive quota from the HPLMN, the NSACF in VPLMN may interact with the HPLMN for retrieving the quota before processing any incoming request. The VPLMN is either configured or discovers the NSACF in the HPLMN for quota retrieval. However, in this case, the VPLMN rejects any additional requests exceeding the received information. + +##### 5.15.11.3.2 VPLMN with HPLMN assistance NSAC Admission + +In this admission mode HPLMN delegates NSAC for S-NSSAIs subject to NSAC to the VPLMN, both for number of registered UEs and the number of LBO PDU sessions. + +Every NSACF performing admission in the VPLMN for each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, fetches from the VPLMN primary NSACF in a hierarchical architecture the maximum number of registered UEs to be admitted and/or the maximum number of LBO PDU sessions to be allowed. The VPLMN primary or central NSACF, in turn, acquires the information from the HPLMN central or primary NSACF depending on the deployed architecture. The VPLMN is either configured or discovers the NSACF in the HPLMN for quota retrieval. + +If re-distribution of quota is required in the VPLMN in a hierarchical architecture, amongst multiple NSACFs than this is handled by the primary NSACF in VPLMN with no involvement from the HPLMN. The VPLMN NSACF discovers the HPLMN primary or central NSACF or be configured with the needed information. + +For any request(s) received in any NSACF in the VPLMN exceeding the received maximum number information, the NSACF interacts with the VPLMN primary NSACF which in turn interacts with HPLMN primary or central NSACF to receive an updated roaming quota for the corresponding mapped S-NSSAI, which is used to determine whether admission request is accepted or rejected, unless forbidden by the SLA. If an admission request is accepted, the UE entry is stored in the NSACF performing admission in the VPLMN. This applies to the number of registered UEs as well as the number of LBO PDU sessions. The primary NSACF in VPLMN may re-distribute the received updated roaming quota to the NSACFs in VPLMN to perform NSAC for Roaming UEs according to the principles described in clauses 5.15.11.1 and 5.15.11.2. + +##### 5.15.11.3.3 HPLMN NSAC Admission Mode + +In this admission mode the AMF or SMF in VPLMN interacts with HPLMN for admission, both for number of registered UEs or the number of LBO PDU sessions respectively. + +For each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, AMF performs NSAC admission for the number of registered UEs with the HPLMN central or primary NSACF for all inbound roamers from that HPLMN when they register in this VPLMN. The AMF discovers the HPLMN primary or central NSACF or be configured with the needed information. + +For each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, every SMF in this VPLMN performs NSAC admission for the number of LBO PDU sessions with the HPLMN central or primary NSACF for all inbound roamers from that HPLMN when they initiate an LBO PDU session. The SMFs discover the HPLMN primary or central NSACF or be configured with the needed information. For each S-NSSAI of the HPLMN that is subject to NSAC, the SMF performs NSAC according to the principles described in clause 5.15.11.2 for home routed PDU sessions. + +In the HPLMN NSAC admission mode, the primary NSACF or central NSACF in HPLMN determines whether the NSAC admission request for a roaming UE is accepted or rejected. + +#### 5.15.11.4 Network Slice status notifications and reports to a consumer NF + +A consumer NF (e.g. AF, Primary NSACF) can subscribe with the NSACF for Network Slice status notifications and reports. Upon such subscription, the corresponding NSACF in different NSAC architecture as defined in clause 5.15.11.0 can provide event based notifications and reports to the consumer NF (e.g. to AF via NEF) related to the current number of UEs registered for a network slice or the current number of UEs with at least one PDU Session/PDN Connection in the case of EPC interworking or the current number of PDU Sessions established on a network slice. + +NOTE: The Primary NSACF subscribes Network Slice status from all the NSACF(s) it contacts with for the update of the maximum number of UE or PDU session configured at the NSACF. + +#### 5.15.11.5 Support of Network Slice Admission Control and Interworking with EPC + +This clause describes the NSAC for maximum number of registered UEs and for maximum number of PDU Sessions for network slice subjected to EPS interworking. The NSAC for maximum number of UE with at least one PDU Session/PDN Connection is described in clause 5.15.11.5a. A network slice subject to both NSAC and EPS counting shall be configured with only one of the options: + +- Maximum number of registered UEs and/or maximum number of PDU Session; or +- Maximum number of UEs with at least one PDU Session/PDN Connection and/or maximum number of PDU Session. + +If EPS counting is required for a network slice, the NSAC for maximum number of UEs and/or for maximum number of PDU Sessions per network slice is performed at the time of PDN connection establishment in case of EPC interworking. To support the NSAC for maximum number of UEs and/or for maximum number of PDU Sessions per network slice in EPC, the SMF+PGW-C is configured with the information indicating which network slice is subject to NSAC. During PDN connection establishment in EPC, the SMF+PGW-C selects an S-NSSAI associated with the PDN connection as described in clause 5.15.7.1. If the selected S-NSSAI by the SMF+PGW-C is subject to the NSAC, the SMF+PGW-C triggers interaction with NSACF to check the availability of the network slice by invoking separate NSAC procedures for number of UE and number of PDU Session (as described in clause 4.11.5.9 of TS 23.502 [3]), + +before the SMF+PGW-C provides the selected S-NSSAI to the UE. If the network slice is available, the SMF+PGW-C continues to proceed with the PDN connection establishment procedure. + +The NSACF performs the following for checking network slice availability prior to returning a response to the SMF+PGW-C: + +- For NSAC for number of UEs, if the UE identity is already included in the list of UE IDs registered with a network slice, or the UE identity is not included in the list of UE IDs registered with a network slice and the current number of UE registration did not reach the maximum number, the NSACF responds to the SMF+PGW-C with the information that the network slice is available. The NSACF includes the UE identity in the list of UE IDs if not already on the list and increases the current number of UE registration. Otherwise, the NSACF returns a response indicating that the maximum number with the network slice has been reached. + +If hierarchical NSAC architecture is deployed, when the local maximum number or local threshold is reached the NSACF may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C. For more details on handling at the NSACF and Primary NSACF see clause 5.15.11.1.2. + +- For NSAC for number of PDU Sessions, if the current number of PDU sessions is below the maximum number, the NSACF responds to the SMF+PGW-C with the information that the network slice is available. The NSACF increases the current number of PDU sessions. Otherwise, the NSACF returns the response indicating that the maximum number with the network slice has been reached. + +If hierarchical NSAC architecture is deployed, when the local maximum number is reached the NSACF may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C. For more details on handling at the NSACF and Primary NSACF see clause 5.15.11.2.2. + +If the maximum number of UEs and/or the maximum number of PDU sessions has already been reached, unless operator policy implements a different action, the SMF+PGW-C rejects the PDN connection. + +NOTE 1: As an implementation option, if the APN is mapped to more than one S-NSSAI and the first selected S-NSSAI is not available (e.g. either current number of UE registration reached maximum or current number of PDU sessions reached maximum), then based on the operator policy the PGW-C+SMF can try another mapped S-NSSAI for the PDN connection establishment procedure. + +If the establishment of a new PDN Connections is with a different SMF+PGW-C from the SMF+PGW-C used for already existing PDN connection associated with the same S-NSSAI, each SMF+PGW-C will send a request for update (e.g. increase or decrease) to the NSACF. The NSACF may maintain a registration entry per SMF+PGW-C for the same UE ID. + +The SMF+PGW-C provides the Access Type to the NSACF when triggering a request to increase or decrease the number of UEs and/or the number of PDU Sessions for an S-NSSAI. + +NOTE 2: The SMF+PGW-C determines the Access Type based on the RAT type parameter in the PMIP or GTP message received from the ePDG; or alternatively it can internally determine the Access Type based on the source node (e.g. SGW) sending the request for the PDN Connection establishment. + +When the UE with ongoing PDN connection(s) moves from EPC to 5GC, the SMF+PGW-C triggers a request to decrease the number of the UE registration in NSACF and the AMF triggers a request to increase the number of the UE registration in NSACF when the UE is registered in the new AMF. If there are more than one PDN connections associated with the S-NSSAI, the NSACF may receive multiple requests for the same S-NSSAI from different SMF+PGW-Cs. When the UE with ongoing PDU session(s) moves from 5GC to EPC, the SMF+PGW-C triggers a request to increase the number of the UE registration in NSACF and the old AMF triggers a request to decrease the number of the UE registration in NSACF when the UE is deregistered in old AMF. If there are more than one PDU sessions associated with the S-NSSAI, the NSACF may receive multiple requests for the same S-NSSAI from different SMF+PGW-Cs. The NSACF maintains a list of UE IDs based on the requests from SMF+PGW-C(s) and AMF, and adjusts the current number of registrations accordingly. + +When EPS counting is performed for a network slice, and the UE with ongoing PDN connection(s) moves from EPC to 5GC, session continuity is guaranteed from NSAC standpoint, as the admission was granted at the time of PDN connection establishment, i.e. the number of PDU session is not counted again in 5GC. Similarly, when the UE with ongoing PDU session(s) moves from 5GC to EPC, session continuity is guaranteed from NSAC standpoint as the admission of the PDN Connection(s) to the network slice was already granted at the time of PDU Session establishment in 5GC. + +If the PDN connection associated with S-NSSAI is released in EPC, the SMF+PGW-C triggers a request (i.e. decrease) to NSACF for maximum number of UEs and/or maximum number of PDU sessions per network slice control. The NSACF decreases the current number of registrations and removes the UE identity from the list of UE IDs if the PDN connection(s) associated with the S-NSSAI are all released in EPC. + +NOTE 3: NSAC in EPC is not performed for the attachment without PDN connectivity. + +If EPS counting is not required for a network slice, the NSAC for maximum number of UEs and/or for maximum number of PDU Sessions per network slice is performed when the UE moves from EPC to 5GC, i.e. when the UE performs mobility Registration procedure from EPC to 5GC (NSAC for maximum number of UEs per network slice) and/or when the PDN connections are handed over from EPC to 5GC (NSAC for maximum number of PDU Sessions per network slice). The SMF+PGW-C is configured with the information indicating the network slice is subject to NSAC only in 5GS. The PDN connection interworking procedure is performed as described in clause 5.15.7.1. Mobility from EPC to 5GC does not guarantee all active PDU Session(s) can be transferred to the 5GC in certain circumstances when either the current number of UE registration or the current number of PDU sessions would exceed the maximum number when the UE moves from EPC to 5GC. When the UE with ongoing PDU session(s) moves from 5GC to EPC, the SMF+PGW-C triggers a request to decrease the number of PDU Session to NSACF. If there are more than one PDU sessions associated with the S-NSSAI, the NSACF may receive multiple requests for the same S-NSSAI from different SMF+PGW-Cs and NSACF removes the PDU Session ID(s) while decreasing the number of PDU Session(s). + +NOTE 4: Given that session continuity is not guaranteed when EPS counting is not required, it is recommended for services which require the session continuity to support EPS counting. + +NOTE 5: When multiple NSACFs are deployed and if the number of UE in target NSACF has reached the maximum number, whether session continuity can be guaranteed is left to implementation. + +NOTE 6: When a centralized architecture is deployed, UE admission is guaranteed at inter-system and inter-AMF mobility if the same NSACF is selected. This is the case for non-roaming scenarios and for roaming scenarios with HPLMN NSAC Admission Mode described in clause 5.15.11.3. + +##### 5.15.11.5a Support of Network Slice Admission Control in 5GS for maximum number of UEs with at least one PDU Session/PDN Connection + +When EPS counting is required for a network slice and NSACF is configured with maximum number of UEs with at least one PDU Session/PDN Connection, the NSACF keeps track of the current number of UEs with at least one PDU session/PDN connection established on a network slice to ensure it does not exceed the maximum configured number. + +To support the NSAC for maximum number of UEs with at least one PDU Session/PDN Connection, the SMF+PGW-C may be configured with one of the following options: + +- **Option 1:** Triggering an Nnsacf\_NSAC\_NumOfUEsUpdate\_Request to NSACF for NSAC for maximum number of UEs when the UE establishes first PDU Session/PDN connection associated with the network slice in the SMF+PGW-C, or when the last PDU Session/PDN connection associated with the network slice is released. The NSACF performs admission control as described in clause 5.15.11.5 and the number of registered UE is replaced with number of UE with at least one PDU session/PDN connection. Also, if the maximum number of UEs with at least one PDU Session/PDN connection has already been reached and SMF+PGW-C receives the rejection from NSACF, unless operator policy implements a different action, the SMF+PGW-C rejects the PDU Session/PDN connection indicating the cause being the number of UEs in the network slice has been exceeded. The AMF is not configured for this S-NSSAI to be subject to NSAC; or +- **Option 2:** Triggering an Nnsacf\_NSAC\_NumOfPDUsUpdate\_Request as described in clause 5.15.11.5 to NSACF and the NSACF performs admission control for the number of UEs with at least one PDU Session/PDN connection as follows: + - The NSACF supports handling both for the number of UEs with at least one PDU Session/PDN Connection and number of PDU session for the S-NSSAI that is subject to EPC interworking and NSAC. In this case the AMF is not configured for this S-NSSAI to be subject to NSAC. As an optimization option, the SMF+PGW-C can be configured not to trigger the Nnsacf\_NSAC\_NumOfUEsUpdate\_Request to NSACF. + - When the NSACF receives request to increase the current number of PDU Session/PDN Connection established for the network slice, the NSACF checks whether this is the first PDU Session/PDN Connection associated with the network slice. If this is the first PDU Session/PDN Connection associated with the network slice the NSACF checks whether the maximum number of UEs with at least one PDU Session/PDN + +Connection has been reached. If the maximum number has not been reached then the NSACF increases the number of UE with at least one PDU session/PDN connection and add an entry for UE ID. If the maximum number of UEs has already been reached, unless operator policy implements a different action, the SMF+PGW-C rejects the PDU Session/PDN connection indicating the cause being the number of UEs in the network slice has been exceeded. + +- When the NSACF receives request to decrease the current number of PDU Session/PDN Connection established for the network slice, the NSACF locates the UE entry, checks whether this is the last PDU Session/PDN Connection associated with the network slice for the UE. If it is the last PDU Session/PDN Connection the NSACF decreases the number of UE with at least one PDU session/PDN connection and remove the associated UE entry. + +NOTE 1: A PLMN can deploy one of the above two options for a slice when EPS counting is required for a network slice and NSACF is configured with maximum number of UEs with at least one PDU Session/PDN Connection. + +NSACF is configured with the information of whether the NSAC for number of UEs with at least one PDU session/PDN connection is based on Option1 or Option 2. + +In both options, the SMF+PGW-C provides the Access Type to the NSACF when triggering a request to increase or decrease or update the number of UEs with at least one PDU Session/PDN Connection and/or the number of PDU Sessions for an S-NSSAI. + +In the case of roaming, same mechanisms in clause 5.15.11.3 are used and number of registered UE is replaced with number of UE with at least one PDU Session/PDN Connection. For home routed PDU Session/PDN Connection only HPLMN admission mode can be used in this case. + +If hierarchical NSAC architecture is deployed, when the local maximum number or local threshold is reached the NSAC may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C. For more details on handling at the NSACF and Primary NSACF see clause 5.15.11.1.2. + +NOTE 2: When NSAC for number of UEs with at least one PDU session or one PDN connection is used, the session continuity is guaranteed at inter-system mobility as the admission is granted during the establishment of the PDU Session/PDN Connection. + +### 5.15.12 Support of subscription-based restrictions to simultaneous registration of network slices + +#### 5.15.12.1 General + +The subscription information for a UE may include for each S-NSSAI Network Slice Simultaneous Registration Group (NSSRG) information constraining which S-NSSAIs can be simultaneously provided to the UE in the Allowed NSSAI. + +When S-NSSAIs have associated NSSRG information, then the S-NSSAIs in the Allowed NSSAI shall share at least one NSSRG. + +The NSSRG information, defining the association of S-NSSAIs to NSSRG, is provided as an additional and separate information. + +If the optional NSSRG information is not present for the S-NSSAIs of a subscription, and other restrictions do not apply e.g. availability at a specific location, then it is assumed that all the S-NSSAIs in the subscription information can be simultaneously provided to the UE in the Allowed NSSAI. However, if NSSRG information is present in the subscription information, at least one NSSRG shall be associated with each of the S-NSSAIs in the subscription information. At any time, if the AMF has received subscription information for a UE that includes NSSRG information, the Allowed NSSAI for the UE can only include S-NSSAIs which share a common NSSRG. + +NOTE 1: The AMF enforces NSSRG only for the access(es) the UE registered to the AMF. When the UE is registered to different PLMNs over 3GPP access and non-3GPP access, the AMF in one access cannot enforce a common NSSRG over both accesses. + +The default S-NSSAIs, if more than one is present, are associated with the same NSSRGs, i.e. the UE is always allowed to be registered with all the default S-NSSAIs simultaneously. The HPLMN only sends S-NSSAIs sharing all the NSSRGs of the Default S-NSSAIs to a non-supporting VPLMN as part of the subscription information, i.e. in addition + +to the default S-NSSAI(s), the HPLMN may send any other subscribed S-NSSAI which shares at least all the NSSRG defined for the default S-NSSAI(s), and the HPLMN sends no NSSRG information to the VPLMN. A subscription information that includes NSSRG information shall include at least one default S-NSSAI. + +A supporting AMF/NSSF, when it receives a Requested NSSAI, evaluates the S-NSSAIs of the HPLMN (in the mapping information of the Requested NSSAI, when a mapping information is applicable) based on any received NSSRG information for these S-NSSAIs, to determines whether they can be provided together in the Allowed NSSAI. + +NOTE 2: An HPLMN enabling support of subscription-based restrictions to simultaneous registration of network slices for a Subscriber, can set the subscribed S-NSSAI(s) already in the subscription information before the NSSRG information was added to the subscription information, to have the same NSSRGs defined for the default S-NSSAI(s) if it has to continue to support the same service behaviour for these S-NSSAIs. + +#### 5.15.12.2 UE and UE configuration aspects + +A UE may support the subscription-based restrictions to simultaneous registration of network slices feature. In this case, the UE indicates its support in the Registration Request message in the Initial Registration and the Mobility Registration Update as part of the UE 5GMM Core Network Capability. + +When the serving AMF provides the Configured NSSAI to the UE, and the UE has indicated it supports the subscription-based restrictions to simultaneous registration of network slices feature, the AMF also provides the UE with the NSSRG information related to the S-NSSAIs of the HPLMN which are in the mapping information of the Configured NSSAI. A UE which receives the NSSRG values in the network slicing configuration information shall only include in the Requested NSSAI S-NSSAIs that share a common NSSRG as per the received information. If the UE has stored Pending NSSAI and the UE is still interested in the Pending NSSAI then all the S-NSSAIs in the Requested NSSAI and the Pending S-NSSAI shall share a common NSSRG. If the HPLMN changes NSSRG information in the subscription information for a UE, the UDM updates the supporting AMF serving the UE with the new NSSRG information and the AMF, possibly after interaction with the NSSF (see clause 5.2.16.2.1 of TS 23.502 [3]), updates the UE as necessary with network slicing configuration by means of the UE Configuration Update procedure (this may include changes in the Configured NSSAI (and related mapping information) and changes in the Allowed NSSAI as applicable). The UE acknowledges this UE Configuration Update according to clause 4.2.4.2 of TS 23.502 [3]. + +At any time, a UE supporting subscription-based restrictions to simultaneous registration of network slices feature and that has received NSSRG information together with the Configured NSSAI shall only request S-NSSAIs, across all Access Type(s) regardless of whether the same PLMN or different PLMNs are used, that share one or more common NSSRG. + +NOTE: In Requested NSSAI across all Access Type(s), the UE needs to include S-NSSAIs that share at least one common NSSRG. + +An AMF which supports the subscription-based restrictions to simultaneous registration of network slice feature configures a non-supporting UE with a Configured NSSAI including only the S-NSSAIs sharing all the NSSRG values of the default S-NSSAI(s), except if it has been instructed otherwise by the UDM. In addition to the default S-NSSAI(s), the AMF sends to the UE in the Configured NSSAI any other subscribed S-NSSAI whose NSSRG match at least those defined for the default S-NSSAI(s). + +The UDM in a supporting HPLMN may optionally keep a record of the PEIs or Type Allocation Codes values regarding UE ability to handle network slices that cannot be provided simultaneously in Allowed NSSAI. + +The UDM may, based on configuration or the optional PEI records, indicate the AMF to provide the non-supporting UEs with the full set of subscribed S-NSSAIs even if they do not share a common NSSRG. The UDM instructs the supporting AMFs of a PLMN to do so by indicating that the UE can be given a Configured NSSAI with all the S-NSSAIs in the subscription information. If this indication is received from the UDM by the AMF, this is included in the UE context. + +Based on its policy (including configuration or optionally checking the specific PEI or Type Allocation Code used by the UE, and subject to roaming agreement) the UDM may also provide the serving AMF in a non-supporting VPLMN with all the S-NSSAI in the subscription information. In this case the AMF provides the UE with a Configured NSSAI including all the S-NSSAIs in the subscription information the AMF receives. + +The AMF provides no NSSRG information to a non-supporting UE. + +When an AMF which supports the subscription-based restrictions to simultaneous registration of network slice feature, receives from a UE a Requested NSSAI including S-NSSAIs that are supported in the Tracking Area but do not share a + +common NSSRG, or the AMF has pending NSSAI stored for the UE, and the S-NSSAI(s) of the requested NSSAI and the pending NSSAI do not share a common NSSRG, the AMF assumes the UE configuration is not up-to-date, and provides the following: + +- a supporting UE with an updated configuration including the up-to-date NSSRG information for the S-NSSAIs in the Configured NSSAI as described above. +- a non-supporting UE with an updated Configured NSSAI including only the S-NSSAIs sharing all the NSSRG values of the default S-NSSAI(s), only for the case where the UE context does not include an indication to provide all the subscribed S-NSSAIs in the subscription information in the Configured NSSAI for the UE. + +### 5.15.13 Support of data rate limitation per Network Slice for a UE + +A UE subscription information may include an optional Slice Maximum Bit Rate for the UE (Subscribed UE-Slice-MBR) for an S-NSSAI, which applies for 3GPP access type only. The Subscribed UE-Slice-MBR includes a UL and a DL value. If a Subscribed UE-Slice-MBR is associated to an S-NSSAI in the subscription information, it is provided by the AMF to the NG-RAN when the AMF provides the Allowed NSSAI for the UE to the NG-RAN as UE-Slice-MBR QoS parameter. The UE-Slice-MBR QoS parameter is defined in clause 5.7.2.6. If the Subscribed UE-Slice-MBR for a UE changes, the AMF updates UE-Slice-MBR in the NG-RAN accordingly. + +In roaming case, the UE-Slice-MBR is provided for the S-NSSAI of the VPLMN which maps to the S-NSSAI of the HPLMN and the AMF may first interact with the PCF for authorization of the Subscribed UE-Slice-MBR. If the AMF interacts with the PCF, the PCF may provide the Authorized UE-Slice-MBR that is used as UE-Slice-MBR by the AMF as described in clause 6.1.2.1 of TS 23.503 [45]. + +For a roaming UE, the S-NSSAI of the VPLMN maps to only one S-NSSAI of the HPLMN for which an UE-Slice-MBR is applied. + +The enforcement of the UE-Slice-MBR value, if present in the UE context in the NG-RAN for an S-NSSAI, is described in clause 5.7.1.10. + +NOTE: The PCF for the PDU Session may in addition be configured to monitor the data rate per Network Slice for a UE and to strengthen or relax the traffic restrictions for individual PDU Sessions or PCC rules accordingly, as described in TS 23.503 [45] clause 6.2.1.9. + +### 5.15.14 Network Slice AS Groups support + +The NG-RAN may support Network Slice AS Groups (NSAGs) which are used as specified in TS 38.300 [27], TS 38.331 [28], TS 38.321 [143] and TS 38.304 [50]. A Network Slice AS Group is an identifier of a group of network slices which are associated with it. A Network Slice AS Group association with a group of network slices may be valid in one or more Tracking Areas. An S-NSSAI can be associated with at most one NSAG values for Random Access and at most one NSAG value for Cell Reselection within a Tracking Area. An S-NSSAI can be associated with different NSAG values in different Tracking Areas. + +The NG-RAN provides (and updates) the AMF with the values of the NSAG(s) an S-NSSAI is associated with in a TA using the NG Set Up and RAN Configuration Update procedures (see TS 38.413 [34]). The AMF in turn provides this information to the NSSF. In deployments where the total number of groups does not exceed the number of groups associated with the NSAG size limit defined in TS 38.331 [28], all the NSAGs configured in the NG-RAN may be unique per PLMN or SNPN. If the UE has indicated that the UE supports NSAG in the 5GMM Core Network Capability (see clause 5.4.4a), the AMF may, with or without NSSF assistance, configure the UE with NSAG Information for one or more S-NSSAIs in the Configured NSSAI, by including this NSAG Information in the Registration Accept message or the UE Configuration Command message. The UE uses the NSAG Information as defined in clause 5.3.4.3.1. The AMF shall indicate in the NSAG Information in which TA a specific NSAG association to S-NSSAI(s) is valid if the AMF provides in the UE configuration a NSAG value which is used in different TAs with a different association with NSSAIs. The configuration the AMF provides includes at least the NSAGs for the UE for the TAs of the Registration Area. If the AMF does not include the list of TAs in association with an NSAG in the NSAG Information, the NSAG is valid in the Registered PLMN and equivalent PLMNs, or SNPN. + +NOTE: If the NSAGs for the PLMN and equivalent PLMNs have different associations to S-NSSAIs, then the AMF includes the list of TAs in the NSAG information. + +The UE shall store and consider the received NSAG Information, valid for the Registered PLMN and equivalent PLMNs, or SNPN until: + +- the UE receives new NSAG information in a Registration Accept message or UE Configuration Command message in this PLMN or SNPN; or +- the UE receives a Configured NSSAI without any NSAG information in this PLMN or SNPN. + +The UE shall store the currently valid NSAG information received in the Registered PLMN or SNPN when registered in this PLMN or SNPN and: + +- The UE should be able to store the NSAG information for at least the Registered-PLMN and equivalent PLMNs, or the Registered-SNPN and equivalent SNPNs. +- The Registered-PLMN can provide NSAG information to the UE for the PLMN and the equivalent PLMNs, and the Registered-SNPN can provide NSAG information to the UE for the SNPN. +- There can be at most 32 NSAGs configured in the UE at a time for a PLMN or SNPN. +- At most 4 NSAGs can have an optional TAI associated with it. + +The NSAG information is not required to be stored after power off or after the UE becomes Deregistered as it is not used for cell selection. + +### 5.15.15 Support of Network Slice usage control + +#### 5.15.15.1 General + +Network Slice usage control is achieved as follows: + +- 1) Configuring network-controlled Slice Usage Policy to supporting UEs (see clause 5.15.15.2). +- 2) Configuring PDU Sessions inactivity timers, and Network Slice deregistration inactivity timers (see clause 5.15.15.3). + +NOTE: Roaming is not supported in this Release of the specification. + +#### 5.15.15.2 UE Configuration of network-controlled Slice Usage Policy + +The UE during the Registration procedure may indicate in UE MM Core Network Capability that it supports UE configuration of network-controlled Slice Usage Policy. If so, the AMF determines Slice Usage Policy for one (or more) Network Slice(s) for the UE and configures the UE with this information together with Configured NSSAI to control the usage of this (or these) Network Slice(s). The AMF may be locally configured with network Slice Usage Policy, or receive the policy from the AM-PCF, or per the information received from UDM for AF managed timer values (see clause 5.15.15.3 for more details). + +The network-controlled Slice Usage Policy is provided to the UE in the Registration Accept or the UE Configuration Update Command and may include: + +- An indication, for one or more of S-NSSAI(s) of the HPLMN in the Configured NSSAI, whether the UE only registers with the Network Slice with the network when applications in the UE require data transmission in the Network Slice (i.e. the UE can only register the Network Slice only on demand and consider the Network Slice as on demand S-NSSAI). + +NOTE: All Other Network Slices in the Configured NSSAI are handled by the UE using UE specific policies (e.g. they may be registered irrespective of applications need). + +- For all on demand S-NSSAI(s) of the HPLMN in the Configured NSSAI, a deregistration inactivity timer that causes the UE to deregister the Network Slice after the last PDU Session associated with the S-NSSAI is released. This deregistration inactivity timer is started at the UE and AMF per access type when the last PDU Session associated with the S-NSSAI is released, or the Network Slice is included in the Allowed NSSAI and no PDU session is established. The deregistration inactivity timer is stopped and reset when the first PDU session is established or the S-NSSAI is removed from the Allowed NSSAI. The AMF and UE may locally remove the S-NSSAI from the Allowed NSSAI when the timer expires. The AMF may also send a UE Configuration Update Command to remove the slice from the Allowed NSSAI. + +If the UE and network state became misaligned, the UE may, for example, request connectivity in a Network Slice which is no longer allowed. In this case, the AMF shall provide the updated Allowed NSSAI in a UE Configuration Update Command after rejecting the PDU Session establishment. The UE may then re-register with the Network Slice if needed. + +The UE stores the received Slice Usage Policy with the Configured NSSAI for the serving PLMN and this is kept stored for as long as a Configured NSSAI remains stored for the PLMN. When the Configured NSSAI is updated, the AMF may also provide a new Slice Usage Policy to the UE. + +The AMF receives deregistration inactivity timer values as described in clause 5.15.15.3. If the slice deregistration inactivity timer value is updated, the AMF provides the updated value to the UE, if the UE supports UE configuration of network-controlled Slice Usage Policy, during the registration procedure (i.e. subsequent registration if there is no ongoing registration). The AMF and the UE, if the update been provided to the UE successfully, use the updated slice deregistration inactivity timer value next time the slice deregistration inactivity timer starts. + +#### 5.15.15.3 Network-based per UE Network Slice usage behaviour control + +The 5GC performs Network Slice usage monitoring to be able to enforce the release of inactive PDU Sessions, and deregistering of UEs from Network Slices with no PDU Sessions on them according to its own policies. In order to support usage monitoring for a Network Slice: + +- the AMF runs a slice deregistration inactivity timer per S-NSSAI and access type to deregister the Network Slice which is started when the Network Slice is not used by any PDU Session over the corresponding access type. The slice deregistration inactivity timer is stopped and reset when at least a PDU Session associated with the Network Slice is successfully established or the Network Slice is removed from the Allowed NSSAI. When the slice deregistration inactivity timer for a Network Slice over an access type expires, the AMF removes the Network Slice from the Allowed NSSAI over the access type by sending the UE Configuration Update Command to impacted UE(s). +- the SMFs provide to UPFs that handle the PDU sessions in the Network Slice a PDU Session inactivity timer. The PDU Session inactivity timer is started after no data packet is transmitted or received and runs until the next data packet is transmitted or received which restarts the timer again. If the PDU Session inactivity timer expires before any packet is received or transmitted, the UPF reports this PDU Session inactivity event to the SMF to cause the SMF to release the PDU Session. While releasing the PDU session the SMF may indicate the release cause because of slice inactivity. When the AMF receives the notification of PDU Session release and it includes the release cause of slice inactivity and if the Network Slice of the released PDU Session is not used by other PDU Sessions (i.e. the last PDU Session using the Network Slice is released) over the corresponding access type, the AMF may trigger the UE Configuration Update procedure to remove the Network Slice from the Allowed NSSAI over that corresponding access type or start slice deregistration inactivity timer for the Network Slice. + +If the PDU Session inactivity timer value is updated, the SMF provides the updated PDU Session inactivity timer value to the UPF. The UPF uses the updated PDU Session inactivity timer value immediately or next time the PDU Session inactivity timer starts. + +NOTE: For MA PDU Session, the PDU Session inactivity timer is independent of Access Type. + +If an S-NSSAI is dedicated for a single AF, and if authorized by operator policy to provide deregistration inactivity/PDU Session inactivity timer values for the S-NSSAI, the AF uses external parameter provisioning procedure to provide deregistration inactivity and PDU session inactivity timer values as described in clause 4.15.6.3g of TS 23.502 [3]. In this case, the AF provided timer values are stored in the UDM and provided to the AMF/SMF as part of subscription data for the corresponding S-NSSAI. If no AF is authorized to provide deregistration inactivity/PDU Session inactivity timer values for the S-NSSAI, i.e. no timer value received from UDM, the slice deregistration inactivity timer value and PDU Session inactivity timer value are either pre-configured in the AMF/SMF or received by the AMF/SMF during the AM Policy Association / SM Policy Association procedure respectively. + +To enable a serving network to direct UEs to a preferred Network Slice, the AMF may request the UE to transfer a PDU Session from one S-NSSAI to another S-NSSAI as described in clause 5.15.19. + +### 5.15.16 Optimized handling of temporarily available network slices + +A network slice may be available for all UEs or a limited number of UEs only for a limited time that is known at the network in advance e.g. by OAM or subscription. The limited time duration may be due to, for example, the fact that network slice is only temporarily or periodically active in the deployment (e.g. for a limited time to serve an event or a + +UE may be only authorized to access the network slice for a limited time known in advance), or the network slice is being decommissioned at a known future time. This feature is enabled by S-NSSAI validity time that the network and the UE can handle to reduce the signalling load associated to the transitions in RM and SM states for the network slice. + +The UE may indicate its support for temporarily available network slices in the UE MM Core Network Capability (see clause 5.4.4a) in the Registration Request. The AMF, based on OAM configuration or information received from the UDM or NSSF, may indicate to a supporting UE the validity time for one or more S-NSSAIs in the Configured NSSAI in the Registration Accept message or via the UE Configuration Update procedure. In roaming case, the AMF may include the validity time for an S-NSSAI in the Configured NSSAI either because of limited availability of the VPLMN S-NSSAI or the mapped S-NSSAI of the HPLMN. + +NOTE 1: When the validity time changes or a validity time is determined for a S-NSSAI in the configured NSSAI, the PLMN provides the new validity time for the S-NSSAIs in the Configured NSSAI to a supporting UE. + +If a supporting UE is configured with validity time for an S-NSSAI: + +- a) If the validity time indicates the S-NSSAI is available, the UE may request the S-NSSAI in a Requested NSSAI in a Registration request and, if the S-NSSAI is included in the Allowed NSSAI or in the Partially Allowed NSSAI, the UE may establish PDU sessions associated with the S-NSSAI. +- b) If the validity time indicates the S-NSSAI is not available + - The UE shall not include the S-NSSAI in the Requested NSSAI for any Access Types regardless of the validity time information was received; + - If the S-NSSAI is already part of the Allowed NSSAI or Partially Allowed NSSAI, the UE shall remove the S-NSSAI from the locally stored Allowed NSSAI or Partially Allowed NSSAI and the UE shall also locally release any PDU sessions associated with the S-NSSAI. + - If the validity time indicates the S-NSSAI will not be available again, the UE shall remove the S-NSSAI from the locally stored Configured NSSAI. + +NOTE 2: Subject to implementation decisions outside 3GPP scope, the UE may also use the validity time information to e.g. attempt to use another PDU sessions to continue supporting the connectivity with another connectivity option if possible according to the URSP rules, or, if not possible, e.g. provide implementation-dependent information on the availability of connectivity for specific applications affected by an impending connectivity loss, so the UE can let the end user prepare for the loss of connectivity. + +For a supporting UE, if validity time applies to an S-NSSAI, an AMF supporting temporarily available network slices shall: + +- If the S-NSSAI is provided in a Requested NSSAI in a Registration Request by the UE and the validity time indicates the S-NSSAI is not available, but it is going to become available again (i.e. the UE is detected as not having up to date validity time), then the AMF sends the Configured NSSAI to the UE including the validity time for the S-NSSAI in the Registration Accept message. If the validity time indicates the S-NSSAI is not available and will not become available again, then the AMF sends the Configured NSSAI to the UE, excluding the S-NSSAI from the Configured NSSAI. +- If the S-NSSAI is in the Allowed NSSAI or the Partially Allowed NSSAI for the UE and the validity time indicates that the S-NSSAI is not available, then locally remove (i.e. without sending any signalling to the UE) the S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI. If there is any PDU session established for the S-NSSAI, the AMF requests the SMF to release the PDU session: + - If the UE is in CM-CONNECTED state, the AMF releases the PDU session for the S-NSSAI by sending to the SMF, as per step 1f in clause 4.3.4.2 of TS 23.502 [3], a Nsmf\_PDUSession\_UpdateSMContext Request with a release indication to request the release of the PDU Session and then the AMF forwards the N2 SM request to release the AN resources associated with the PDU session + - If the UE is in CM-IDLE state, the AMF locally releases the PDU session without paging the UE and causes the SMF to locally release the SM context for the UE by a Nsmf\_PDUSession\_ReleaseSMContext, as in step 1c in clause 4.3.4.2 of TS 23.502 [3]. The PDU Session status is synchronized at next time when the UE connects to the network. + +For a non-supporting UE, if validity time applies to an S-NSSAI, an AMF supporting temporarily available network slices shall: + +- If the validity time indicates the S-NSSAI is available, allow or partially allow the network slice when requested, establish PDU sessions when requested. +- If the S-NSSAI is provided in a Requested NSSAI in a Registration Request by the UE and the validity time indicates the S-NSSAI is not available, reject the S-NSSAI and remove the S-NSSAI from the Configured NSSAI by providing an updated Configured NSSAI in the Registration Accept message. +- If the S-NSSAI is in the UE in the Allowed NSSAI or Partially Allowed NSSAI and the validity time indicates the S-NSSAI is not available, remove the S-NSSAI from the Configured NSSAI and the Allowed NSSAI or Partially Allowed NSSAI by a UE Configuration Update procedure. If there is any PDU session established for the S-NSSAI, the AMF requests the SMF to release the PDU session in the network: +- If the UE is in CM-CONNECTED state, the AMF releases the PDU session for the S-NSSAI by sending to the SMF, as in step 1f in clause 4.3.4.2 of TS 23.502 [3], a Nsmf\_PDUSession\_UpdateSMContext Request with a release indication to request the release of the PDU Session and then the AMF forwards the N2 SM request to release the AN resources associated with the PDU session +- If the UE is in CM-IDLE, the AMF locally releases the PDU session without paging the UE and causes the SMF to locally release the SM context for the UE by a Nsmf\_PDUSession\_ReleaseSMContext, as in step 1c in clause 4.3.4.2 of TS 23.502 [3]. The PDU Session status is synchronized at next time when the UE connects to the network + +NOTE 3: If the network slice becomes unavailable, and a large number of UEs are impacted, the AMF can send the updates to the non-supporting UEs in a manner that avoids surge in signalling (e.g. next time the UE becomes connected). + +- If the AMF detects from the validity time of a S-NSSAI that it is available again, then update the Configured NSSAI to include the S-NSSAI via a UE Configuration Update procedure. + +NOTE 4: The AMF, for the case of UE not performing any actions despite the validity timing information provided by the network, can terminate PDU Session(s) associated with S-NSSAI subject to be terminated according to the validity time by explicitly releasing the PDU Sessions associated with the S-NSSAI. + +### 5.15.17 Partial Network Slice support in a Registration Area + +A Network Slice may be supported in one or more TAs in a PLMN/SNPN. The Partial Network Slice support in a Registration Area for a UE includes configuring the UE with a Partially Allowed NSSAI and/or S-NSSAI(s) rejected partially in the RA. + +When creating a Registration Area for UEs registering over the 3GPP access and supporting the Partial Network Slice support in a Registration Area, the AMF may consider the trade-off between signalling for paging in TAs where the S-NSSAI is not supported versus the signalling for Mobility Registration Updates to register with the S-NSSAI in the TA(s) where the S-NSSAI is supported, so that the AMF may create a Registration Area including the TA(s) where a requested S-NSSAI is not supported. For supporting UEs, whether the AMF uses the Partially Allowed NSSAI or rejects the S-NSSAI partially in the RA, or whether the AMF rejects the S-NSSAI for the current RA, is a per S-NSSAI decision which is based on AMF local policy. If supported and allowed by local policy, the Partially Allowed NSSAI and S-NSSAI rejected partially in the RA may be applied simultaneously for one UE for different S-NSSAI. + +For such S-NSSAI: + +- If requested by the UE from a TA where the S-NSSAI is not supported (including the case when the S-NSSAI is provided as a rejected S-NSSAI for the TA from the NSSF): + - the S-NSSAI is included either in the Partially Allowed NSSAI or the AMF rejects the S-NSSAI partially in the RA; or + - if the S-NSSAI is subject to NSAC for maximum number of UEs, then the AMF should send this S-NSSAI as rejected partially in the RA, in the Registration Accept message. + - If the S-NSSAI is subject to NSSAA and successful NSSAA status for the S-NSSAI is not present in the AMF, then the AMF either sends this S-NSSAI as rejected partially in the RA in the Registration Accept + +message, or the AMF starts executing NSSAA and includes the S-NSSAI in the Pending NSSAI in the Registration Accept message. If the S-NSSAI is subject to NSSAA and successful NSSAA status for the S-NSSAI is present, then the AMF may include the S-NSSAI either in the Partially Allowed NSSAI or the AMF rejects the S-NSSAI partially in the RA. + +NOTE 1: In roaming case the NSSAA requirement is based on the mapped S-NSSAI of the HPLMN. + +- if the slice deregistration inactivity timer is configured for the S-NSSAI (see clause 5.15.15.3), then AMF should send this S-NSSAI as rejected partially in the RA. +- If requested by the UE from a TA where the S-NSSAI is supported (including the case when the S-NSSAI is provided in the Allowed NSSAI from the NSSF): + - the S-NSSAI is included in the Partially Allowed NSSAI; or + - if the S-NSSAI is subjected to NSAC for maximum number of UEs, then the AMF should restrict the RA so that the S-NSSAI is supported in all the TAs of the RA and includes the S-NSSAI in the Allowed NSSAI. + - If the S-NSSAI is subject to NSSAA, then the AMF starts executing NSSAA and sends this S-NSSAI in the Pending NSSAI in the Registration Accept message, unless successful NSSAA status is present in the AMF for this S-NSSAI (in which case it can be sent in the Partially Allowed NSSAI). + +NOTE 2: In roaming case the NSSAA requirement is based on the mapped S-NSSAI of the HPLMN. + +- if the S-NSSAI is included in neither the Partially Allowed NSSAI nor the Allowed NSSAI, the AMF may reject the S-NSSAI as described in clause 5.15.4.1.1. + +While the S-NSSAIs of the Allowed NSSAI are supported in all the TAs of the Registration Area, the S-NSSAIs of the Partially Allowed NSSAI are supported only in the TAs corresponding to the list of TAs (which are subset of the list of TAIIs forming the Registration Area) associated with the S-NSSAI. + +If the UE supports Partial Network Slice support in a Registration Area, the AMF may create a Registration Area for the UE considering the support of the S-NSSAIs of the Requested NSSAI in the current TA and in the neighbouring TAs and provides to the UE in the Registration Accept message or in the UE Configuration Update Command message the Partially Allowed NSSAI or the S-NSSAIs rejected partially in the RA as follows: + +- If one or more of the requested S-NSSAI(s) are supported in a subset of the TAs of the (potential) Registration Area, the AMF may include such S-NSSAI(s) in the Partially Allowed NSSAI and corresponding mapping information of the S-NSSAI(s) of the Partially Allowed NSSAI to the HPLMN S-NSSAI(s). For each S-NSSAI of the Partially Allowed NSSAI the AMF provides a list of TAs where the S-NSSAI is supported. The UE is considered registered with the S-NSSAI in the whole Registration area. The AMF also provides the Partially Allowed NSSAI (without indication of the TA list where the partially allowed S-NSSAIs are supported) to the NG-RAN together with the UE's context. +- Alternatively, the AMF may reject the S-NSSAI(s) with reject cause indicating "partially in the RA". For each S-NSSAI of the S-NSSAIs rejected partially in the RA the AMF provides a list of TAs where the S-NSSAI is not supported. + +NOTE 3: If the UE requests an S-NSSAI in a cell of a TA where the NS-AoS of the S-NSSAI does not match deployed Tracking Areas (see clause 5.15.18), the AMF includes the S-NSSAI in the Allowed NSSAI or Partially Allowed NSSAI. + +When the UE stores Partially Allowed NSSAI the following applies: + +- the UE is considered registered with an S-NSSAI of the Partially Allowed NSSAI in the whole Registration area. The UE does not trigger registration when moving between the TAs of support and non-support for the S-NSSAI within the RA. +- The UE is allowed to initiate PDU Session establishment for the S-NSSAI only when the UE is in a TA where the S-NSSAI is supported. +- If the AMF determines a PDU Session is associated with S-NSSAI present in the Partially Allowed NSSAI, the AMF indicates to the SMF that the PDU Session is subject to area restrictions for the S-NSSAI. As a result, the SMF subscribes to "UE mobility event notification" for reporting UE presence in Area of Interest by providing S-NSSAI to the AMF as described in clauses 5.6.11 and 5.3.4.4. + +- When the UE has already established a PDU Session with an S-NSSAI part of the Partially Allowed NSSAI, the UE is allowed to activate the User Plane resources of the PDU Session only when the UE is in a TA part of the list of TAs associated with the S-NSSAI. +- When the User Plane resources are activated for a PDU Session of an S-NSSAI part of the Partially Allowed NSSAI and the UE moves to a TA which is not part of the list of TAs associated with the S-NSSAI, the User Plane resources for the PDU Session shall be deactivated, but the PDU Session context in UE and SMF is not released. The User Plane resources for the PDU Session shall not be activated as long as the UE is located in a TA which is not part of the list of TAs associated with the S-NSSAI of the Partially Allowed NSSAI. The UE shall not send user data as payload of a NAS message (see clause 5.31.4.1) in uplink directions. When the SMF is notified by the AMF that the UE location is outside of the Area of Interest, the SMF shall not send user data as payload of NAS message (see clause 5.31.4.1) in downlink directions and disable data notification. When the SMF is notified by the AMF that the UE location is UNKNOWN as defined in Annex D, clauses D.1 and D.2 of TS 23.502 [3], then based on operator policy SMF may enable downlink data notification and trigger the Network triggered Service Request procedure to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. + +**Editor's note:** Whether and based on what criteria to trigger the reporting and the applicability to the CP CIOT optimization use cases are FFS. + +For an already established PDU Session associated with an S-NSSAI included in the Partially Allowed NSSAI, even when the UE is in a TA where the S-NSSAI is not supported, the UE and the SMF may initiate a PDU Session release procedure or PDU Session modification procedure (i.e. for PS data off status change reporting). + +When the UE stores a S-NSSAI rejected partially in the RA with the associated list of TAs, the UE is allowed to initiate a Mobility Registration Update procedure to request registration with the S-NSSAI only when the UE is in a TA which is not part of the list of TAs associated with this S-NSSAI. + +For a UE in CM-CONNECTED state, when a PDU Session is established on an S-NSSAI included in the Partially Allowed NSSAI, the User Plane resources are activated and the UE moves to a TA where the S-NSSAI is not supported, the NG-RAN releases the User Plane resources of the PDU sessions associated with the S-NSSAIs, as described in step 1d of clause 4.3.4.2 of TS 23.502 [3] and the SMF deactivates the PDU session as described in step 3a of clause 4.3.4.2 of TS 23.502 [3]. + +### 5.15.18 Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas + +#### 5.15.18.1 General + +The network support for a Network Slice is defined on a per Tracking Area granularity. It may be beneficial to deploy some Network Slices such that the Network Slice have a limited geographical availability that is not matching existing Tracking Area boundaries. + +The operator can in this case decide to change the topology of the Tracking Areas so they match the boundaries of the Network Slice, or the operator may configure resources for the Network Slices in the cells of TAs where the Network Slices are to be available, and in areas of the TAs where the network slice is defined to be not available the cells are configured with zero resources. + +The AMF receives from the OAM the information on availability of a network slice when the granularity is smaller than TA, i.e. if the NS-AoS includes TAs where the network slice is not available in some cells of the TA. + +In order to optimize the end-to-end behaviour, the AMF can, based on NS-AoS information received from OAM, configure supporting UEs with S-NSSAI location availability information, and the network may need to monitor the S-NSSAI usage and enforce the NS-AoS e.g. if the UE does not support the S-NSSAI location availability information. + +#### 5.15.18.2 S-NSSAI location availability information + +S-NSSAI location availability information defines additional restrictions to the usage of an S-NSSAI in TAs where the Network Slice availability does not match the TA boundaries. The AMF is configured per S-NSSAI whether to send the S-NSSAI location availability information to supporting UEs. + +The S-NSSAI location availability information sent to the UE includes, for each applicable S-NSSAI of the Configured NSSAI, Location information indicating the cells of TAs in the RA where the related S-NSSAI is available if the S-NSSAI is not available in all the cells of the TA. + +If the UE has indicated that the UE supports S-NSSAI location availability information in the 5GMM Core Network Capability (see clause 5.4.4a), the AMF may, based on OAM configuration, configure the UE with S-NSSAI location availability information for one or more S-NSSAIs when the AMF allocates an RA where the Network Slice availability does not match whole TAs, by including the S-NSSAI location availability information in the Registration Accept message or the UE Configuration Command message. A UE that receives S-NSSAI location availability information applies the information as follows. + +1. If the S-NSSAI is rejected in the RA or rejected partially in the RA or rejected with a cause code that allows attempting to register the S-NSSAI again, the UE can request the S-NSSAI only if the S-NSSAI location availability information indicates that the S-NSSAI is available at the cell where the UE is camping. +2. If the S-NSSAI is in the Partially Allowed NSSAI or in the Allowed NSSAI and the UE is in a cell within the RA but outside the NS-AoS of the S-NSSAI, the following applies: + - a. The UE shall not activate User Plane resources for any already established PDU Session with that S-NSSAI. + - b. The UE shall not send user data as payload of a NAS message (see clause 5.31.4.1) in uplink direction. + - c. For an already established PDU Session, the UE and the SMF may initiate signalling for PDU Session release procedure or PDU Session modification procedure (i.e. for PS data off status change reporting). +3. If the S-NSSAI is in the Partially Allowed NSSAI or in the Allowed NSSAI, and the UE in CM-CONNECTED state moves from a cell inside the NS-AoS to a cell outside the NS-AoS and the User Plane resources are active for a PDU Session on that S-NSSAI, the NG-RAN deactivates the User Plane resources as described in the AN initiated modification of a PDU Session in clause 4.3.3.2 of TS 23.502 [3]. + +NOTE 1: By Radio Resource Management and existing mechanisms in NG-RAN, handover can be used to keep the UE in the NS-AoS or steer the UE to enter the NS-AoS as long as radio conditions allow it. + +NOTE 2: Since the S-NSSAI location availability information is not used as a trigger for the UE to perform MRU due to mobility, i.e. the UE performs MRU due to mobility upon changing to a new TA outside the UE's Registration Area, the S-NSSAI remains registered and is included in the Allowed NSSAI when the UE exits the NS-AoS. If the S-NSSAI is subject for NSAC, the S-NSSAI is counted towards NSAC as described in clause 5.15.11 also when the UE is outside the NS-AoS. + +#### 5.15.18.3 Network based monitoring and enforcement of Network Slice Area of Service not matching deployed Tracking Areas + +OAM may configure RRM policies for S-NSSAIs on a per cell basis as defined in TS 28.541 [149], i.e. cells outside the Network Slice Area of Service while in a TA supporting the S-NSSAI are allocated with no RRM resources for the S-NSSAI. + +The network may enforce the NS-AoS for an S-NSSAI as follows: + +1. The network may monitor the validity of the S-NSSAI for UE in CM-CONNECTED state, i.e. the AMF subscribes to the AoI using the Location information of the S-NSSAI location availability information as described in TS 38.413 [34]. +2. If the non-supporting UE makes a PDU Session establishment request with an S-NSSAI that is not valid as per the S-NSSAI location availability information, the AMF may reject the NAS Transport message with a back-off timer using S-NSSAI based congestion control as described in clause 5.19.7.4. +3. If the AMF determines that the UE in CM-CONNECTED has moved outside the NS-AoS, the AMF performs the following logic: + - a) If the non-supporting UE has other S-NSSAI(s) in the Allowed NSSAI, then the AMF may update the UE with a UE Configuration Update by removing the S-NSSAI from the Allowed NSSAI (which causes the UE to locally release the PDU Sessions) and optionally removing the S-NSSAI from the Configured NSSAI and then, the AMF requests the SMF to locally release in the network any PDU Sessions with that S-NSSAI as + +per step 1f in clause 4.2.3.4 in TS 23.502 [3]. Alternatively, the AMF requests the SMF to release PDU Sessions with that S-NSSAI. + +- b) If the non-supporting UE does not have any other S-NSSAI in the Allowed NSSAI, then the AMF may update the UE with a UE Configuration Update by removing the S-NSSAI from the Allowed NSSAI (which causes the UE to locally release the PDU Sessions) and optionally removing the S-NSSAI from the Configured NSSAI, and adding a default S-NSSAI to the Allowed NSSAI and then, the AMF requests the SMF to locally release in the network any PDU Sessions with the removed S-NSSAI as per step 1f in clause 4.2.3.4 in TS 23.502 [3]. Alternatively, the AMF requests the SMF to release PDU Sessions with that S-NSSAI. + +NOTE: Whether the AMF removes the S-NSSAI from Allowed NSSAI and Configured NSSAI or only releases the associated PDU Sessions when the AMF enforces the NS-AoS is up to AMF configuration. + +- c) For a non-supporting UE that does not have any other S-NSSAI in the Allowed NSSAI nor in the Configured NSSAI, then the AMF indicates to the SMF to release the PDU Session. +4. If the AMF determines that the S-NSSAI becomes valid e.g. the UE has moved into the NS-AoS, the AMF may update the UE with a UCU e.g. including the S-NSSAI in the Configured NSSAI. + 5. When the AMF determines that the S-NSSAI of a PDU Session is restricted to an NS-AoS in the PDU session, the AMF indicates to the SMF that the PDU Session is subject to area restriction for the S-NSSAI. As a result, the SMF subscribes to "UE mobility event notification" for reporting UE presence in Area of Interest by providing S-NSSAI to the AMF as described in clauses 5.6.11 and 5.3.4.4. When SMF is notified that the UE location is outside of Area of Interest, SMF shall not send user data as payload of NAS message (see clause 5.31.4.1) in downlink directions and disable data notification. + 6. When the SMF is notified by the AMF that the UE location is UNKNOWN as defined in Annex D, clauses D.1 and D.2 of TS 23.502 [3], then based on operator policy SMF may enable downlink data notification and trigger the Network triggered Service Request procedure to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. + +**Editor's note:** Whether and based on what criteria to trigger the reporting and the applicability to the CP CIOT optimization use cases are FFS. + +### 5.15.19 Support of Network Slice Replacement + +The Network Slice Replacement feature is used to temporarily replace an S-NSSAI with an Alternative S-NSSAI when an S-NSSAI becomes unavailable or congested. The Network Slice Replacement may be triggered in the following cases: + +- If the NSSF detects that an S-NSSAI becomes unavailable or congested (e.g. based on OAM or NWDAF analytics output), it sends network slice availability notification for the S-NSSAI to the AMF. The notification may include an Alternative S-NSSAI which can be used by the AMF to replace the S-NSSAI. The NSSF notifies the AMF when the S-NSSAI is available again. +- If the PCF detects that an S-NSSAI becomes unavailable or congested for a UE (e.g. based on OAM or NWDAF analytics output), it sends access and mobility related policy notification to the AMF. The notification may include an Alternative S-NSSAI which can be used by the AMF to replace the S-NSSAI. The PCF notifies the AMF when the S-NSSAI is available again for the UE. +- The OAM sends notification to AMF when an S-NSSAI becomes unavailable or congested (and also when this S-NSSAI becomes available again) and provides the Alternative S-NSSAI to AMF. + +The network slice associated with the Alternative S-NSSAI is assumed in this specification to have NS-AoS to be covering at least the NS-AoS of the replaced network slice. + +NOTE 1: It is recommended to use a network slice associated with the Alternative S-NSSAI that is able to support requirements for the services that the replaced network slice supports. + +NOTE 2: There are no means for the PLMN to prevent the UE from obtaining service in the Alternative network slice in cells outside the NS-AoS of the replaced network slice but within the NS-AoS of the Alternative network slice if the Alternative network slice NS-AoS exceeds the NS-AoS of the replaced network slice. + +Based on the notification above from NSSF or PCF or OAM, the AMF may determine that an S-NSSAI is to be replaced with Alternative S-NSSAI. For roaming case, the AMF subscribes the network slice availability notification of the HPLMN S-NSSAI from the NSSF in VPLMN and the NSSF in VPLMN subscribes the notification from NSSF in the HPLMN as described in clause 5.15.6. + +NOTE 3: It is recommended that, the operator configures to use only one option, i.e. OAM, PCF or NSSF, for determining an Alternative S-NSSAI and triggering the Network Slice Replacement for S-NSSAI. + +The AMF uses the Alternative S-NSSAI received in the notification from the NSSF, or from OAM or from the PCF If the NSSF or PCF or OAM do not provide an Alternative S-NSSAI in the notification, the AMF uses an Alternative S-NSSAI based on local configuration. The Alternative S-NSSAI shall be supported in the UE Registration Area. If AMF cannot determine the Alternative S-NSSAI for the S-NSSAI, e.g. OAM or NSSF doesn't provide Alternative S-NSSAI and there is no Alternative S-NSSAI in the AMF local configuration, the AMF may further interact with the PCF to determine the Alternative S-NSSAI. The event trigger in AMF for interacting with PCF is described in clause 6.1.2.5 of TS 23.503 [45]. + +If the Alternative S-NSSAI is subject to NSSAA, the Alternative S-NSSAI shall only be used for UEs for which the Alternative S-NSSAI is included in the Subscribed S-NSSAIs. In this case, the AMF performs the NSSAA procedure for the Alternative S-NSSAI as described in clause 5.15.10 before the AMF triggers Network Slice Replacement as specified below. + +The UE indicates the support of Network Slice Replacement feature during the UE Registration procedure. For supporting UE in CM-CONNECTED state and if there is a PDU Sessions in the UE context associated with the S-NSSAI that needs to be replaced, the AMF additionally provides the Alternative S-NSSAI for this S-NSSAI in the Allowed NSSAI and in the Configured NSSAI, if not included yet, and the mapping between S-NSSAI(s) to Alternative S-NSSAI(s) to the UE in UE Configuration Update message as follows: + +- for non-roaming UEs, the AMF provides the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE. + +NOTE 4: In the non-roaming case, the Alternative S-NSSAI does not have to be a Subscribed S-NSSAIs, as the replaced S-NSSAI is always a subscribed S-NSSAI. + +- for roaming UEs when the VPLMN S-NSSAI has to be replaced by a VPLMN Alternative S-NSSAI, the AMF provides the mapping of the VPLMN S-NSSAI to the Alternative VPLMN S-NSSAI to the UE. +- for roaming UEs when the HPLMN S-NSSAI has to be replaced by an Alternative HPLMN S-NSSAI, the AMF provides the mapping of the HPLMN S-NSSAI to the Alternative HPLMN S-NSSAI to the UE. + +NOTE 5: In the roaming cases, the Alternative HPLMN S-NSSAI does not have to be one of the Subscribed S-NSSAIs as the replaced HPLMN S-NSSAI is always part of the Subscribed S-NSSAIs. + +For the supporting UE when the UE has a NAS signalling connection, i.e. it is CM-CONNECTED or it has become CM-CONNECTED, e.g. through a Service Request procedure or through a UE registration procedure, if the AMF determines that the S-NSSAI is to be replaced and there is a PDU Session associated with the S-NSSAI in the UE context (see also NOTE 3), the AMF sends the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE in the UE Configuration Update message or in the Registration Accept message. + +NOTE 6: It is left to AMF local policy whether to send the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE when there is no PDU session associated with the S-NSSAI or wait and send the mapping of the S-NSSAI to the Alternative S-NSSAI to the UE when the UE establishes a PDU Session associated with the S-NSSAI. + +During a new PDU Session establishment procedure for a S-NSSAI, + +- if the UE has received together with the Allowed NSSAI a mapping of the S-NSSAI to an Alternative S-NSSAI, the UE shall provide both the Alternative S-NSSAI and the S-NSSAI in the PDU Session Establishment message. When the AMF receives the Alternative S-NSSAI and the S-NSSAI in the PDU Session Establishment message, the AMF includes both the Alternative S-NSSAI and the S-NSSAI to the SMF in Nsmf\_PDUSession\_CreateSMContext service operation. +- if the UE has not yet received with the Allowed NSSAI a mapping of the S-NSSAI to the Alternative S-NSSAI, the UE provides only the S-NSSAI in the PDU Session Establishment message. If the AMF determines that the requested S-NSSAI is to be replaced with the Alternative S-NSSAI and if the UE supports Network Slice Replacement, the AMF performs UE Configuration Update procedure to reconfigure the UE with the Alternative S-NSSAI. The AMF continues the PDU Session establishment procedure with the Alternative S-NSSAI and + +provides both the Alternative S-NSSAI and the S-NSSAI to the SMF in Nsmf\_PDUSession\_CreateSMContext service operation. + +The SMF proceeds with the PDU Session establishment using the Alternative S-NSSAI. The SMF sends the Alternative S-NSSAI to NG-RAN in N2 SM information and to UE in PDU Session Establishment Accept message. + +For existing PDU Session associated with an S-NSSAI that is replaced with the Alternative S-NSSAI, after the AMF sends mapping of the S-NSSAI to the Alternative S-NSSAI to the supporting UE in UE Configuration Update message, the AMF sends updates to the SMF of the PDU Session, e.g. triggering Nsmf\_PDUSession\_UpdateSMContext service operation, that the PDU Session is to be transferred to Alternative S-NSSAI and includes the Alternative S-NSSAI as follows (see details in clause 4.3.3 of TS 23.502 [3]): + +- If the SMF determines that the PDU Session is to be retained (e.g. if the anchor UPF can be reused with the alternative S-NSSAI and SSC mode 1), the SMF sends the Alternative S-NSSAI to the UPF in the N4 message, to the NG-RAN in N2 message and to the supporting UE in PDU Session Modification Command message. The S-NSSAI provided to the (R)AN and to the UPF is the Alternative S-NSSAI. +- If the SMF determines that the PDU Session is to be re-established, the SMF sends the Alternative S-NSSAI to the supporting UE either in PDU Session Modification Command if the PDU Session is of SSC mode 3, or in PDU Session Release if the PDU Session is of SSC mode 2 or SSC mode 1, to trigger the re-establishment of the PDU Session. The UE includes both, the S-NSSAI and the Alternative S-NSSAI in the PDU Session Establishment message. + +When the AMF is notified that the S-NSSAI is available again (e.g. the congestion of the S-NSSAI has been mitigated), if the AMF has configured the supporting UE with the Alternative S-NSSAI, and the AMF determines for the UE to use the replaced S-NSSAI again, the AMF reconfigures the supporting UE (e.g. by using UE Configuration Update procedure or in the next registration procedure) to use the replaced S-NSSAI again by removing the mapping of the replaced S-NSSAI to Alternative S-NSSAI. + +If there is an existing PDU Session associated with the Alternative S-NSSAI, the AMF updates the SMF(s) of the PDU Session(s), by Nsmf\_PDUSession\_UpdateSMContext service operation, causing the PDU Session to be transferred to the S-NSSAI. The event trigger in SMF for interacting with PCF is described in clause 6.1.3.5 of TS 23.503 [45]. + +During a handover procedure, if an S-NSSAI has to be replaced with an Alternative S-NSSAI, the handover procedure (including any PDU session associated with the S-NSSAI to be replaced) shall continue unaffected by the Network Slice Replacement. Any Network Slice Replacement for the S-NSSAI shall not take place during the handover. + +During NSSAA re-authentication procedure for an S-NSSAI, if the S-NSSAI has to be replaced with Alternative S-NSSAI, the AMF shall continue with the NSSAA procedure unaffected by the Network Slice Replacement and the AMF executes the Network Slice Replacement after the NSSAA procedure is completed. + +### 5.15.20 Support of Network Slice Instance Replacement + +The Network Slice Instance Replacement is used when a PDU Session for a given S-NSSAI is established using a selected Network Slice instance and the S-NSSAI corresponding to this Network Slice instance is associated with multiple Network Slice instances. In this case, the network may change the Network Slice instance for the S-NSSAI if the selected Network Slice instance is no longer available (e.g. due to overload). The AMF may subscribe with the NSSF for notifications when any of the Network Slice instances served by the AMF is congested or no longer available. In case of roaming, the NSSF of VPLMN subscribes with the NSSF of the HPLMN for notifications. When the NSSF notifies the AMF that a Network Slice instance is congested or no longer available, for some of PDU Sessions associated with the Network Slice instance that is no longer available, the AMF may delete old NSI ID corresponding to the Network Slice instance that is no longer available and the SMF of the PDU Session(s) selected by using such old NSI ID is informed by the AMF to release the PDU Session(s). Subsequently, the SMF triggers the impacted UE(s) to establish new PDU session(s) associated with the same S-NSSAI as described in clause 5.6.9.2 for PDU Session(s) of SSC Mode 2 and SSC Mode 3. The AMF selects a new Network Slice instance for the given S-NSSAI during PDU Session Establishment. + +## 5.16 Support for specific services + +### 5.16.1 Public Warning System + +The functional description for supporting Public Warning System for 5G System can be found in TS 23.041 [46]. + +### 5.16.2 SMS over NAS + +#### 5.16.2.1 General + +This clause includes feature description for supporting SMS over NAS in 5G System. Support for SMS incurs the following functionality: + +- Support for SMS over NAS transport between UE and AMF. This applies to both 3GPP and Non 3GPP accesses. +- Support for AMF determining the SMSF for a given UE. +- Support for subscription checking and actual transmission of MO/MT-SMS transfer by the SMSF. +- Support for MO/MT-SMS transmission for both roaming and non-roaming scenarios. +- Support for selecting proper domains for MT SMS message delivery including initial delivery and re-attempting in other domains. + +#### 5.16.2.2 SMS over NAS transport + +5G System supports SMS over NAS via both 3GPP access and non-3GPP access. + +During Registration procedure, a UE that wants to use SMS provides an "SMS supported" indication over NAS signalling indicating the UE's capability for SMS over NAS transport. "SMS supported" indication indicates whether UE can support SMS delivery over NAS. If the core network supports SMS functionality, the AMF includes "SMS allowed" indication to the UE, and whether SMS delivery over NAS is accepted by the network. + +SMS is transported via NAS transport message, which can carry SMS messages as payload. + +### 5.16.3 IMS support + +#### 5.16.3.1 General + +IP-Connectivity Access Network specific concepts when using 5GS to access IMS can be found in TS 23.228 [15]. + +5GS supports IMS with the following functionality: + +- Indication toward the UE if IMS voice over PS session is supported. +- Capability to transport the P-CSCF address(es) to UE. +- Paging Policy Differentiation for IMS as defined in TS 23.228 [15]. +- IMS emergency service as defined in TS 23.167 [18]. +- Domain selection for UE originating sessions. +- Terminating domain selection for IMS voice. +- Support of P-CSCF restoration procedure (clause 5.16.3.9). +- NRF based P-CSCF discovery (clause 5.16.3.11). + +NOTE: The NRF based P-CSCF discovery has no impact on the UE, i.e. the UE does not need to know how P-CSCF IP address(es) is discovered in the network. + +- NRF based HSS discovery (clause 5.16.3.12). + +#### 5.16.3.2 IMS voice over PS Session Supported Indication over 3GPP access + +The serving PLMN AMF shall send an indication toward the UE during the Registration procedure over 3GPP access to indicate if an IMS voice over PS session is supported or not supported in 3GPP access and non-3GPP access. A UE with "IMS voice over PS" voice capability over 3GPP access should take this indication into account when performing voice domain selection, as described in clause 5.16.3.5. + +The serving PLMN AMF may only indicate IMS voice over PS session supported over 3GPP access in one of the following cases: + +- If the network and the UE are able to support IMS voice over PS session in the current Registration Area with a 5G QoS Flow that supports voice as specified in clause 5.7. +- If the network or the UE are not able to support IMS voice over PS session over NR connected to 5GC, but is able for one of the following: + - If the network and the UE are able to support IMS voice over PS session over E-UTRA connected to 5GC, and the NG-RAN supports a handover or redirection to E-UTRA connected to 5GC for this UE at QoS Flow establishment for IMS voice; + - If the UE supports handover to EPS, the EPS supports IMS voice, and the NG-RAN supports a handover to EPS for this UE at QoS Flow establishment for IMS voice; or + - If the UE supports redirection to EPS, the EPS supports IMS voice, and the NG-RAN supports redirection to EPS for this UE at QoS Flow establishment for IMS voice. +- If the network is not able to provide a successful IMS voice over PS session over E-UTRA connected to 5GC, but is able for one of the following: + - If the UE supports handover to EPS, the EPS supports IMS voice, and the NG-RAN supports a handover to EPS for this UE at QoS Flow establishment for IMS voice; or + - If the UE supports redirection to EPS, the EPS supports IMS voice, and the NG-RAN supports redirection to EPS for this UE at QoS Flow establishment for IMS voice. + +The serving PLMN provides this indication based e.g. on local policy, UE capabilities, HPLMN, whether IP address preservation is possible, whether NG-RAN to UTRAN SRVCC is supported and how extended NG-RAN coverage is, and the Voice Support Match Indicator from the NG-RAN (see clause 4.2.8a of TS 23.502 [3]). + +NOTE 1: The terms "UE supports handover to EPS" or "UE supports redirection to EPS" used above also consider the case that the UE has signalled that S1 mode is enabled. In case the UE has signalled that S1 mode is disabled for a network that only supports IMS voice via EPS Fallback, the AMF will not indicate that IMS voice over PS session is supported over 3GPP access. A voice centric UE ensures its voice service as described in clauses 5.16.3.5 and 5.16.3.6. + +The AMF in serving PLMN shall indicate that IMS voice over PS is supported only if the serving PLMN has a roaming agreement that covers support of IMS voice with the HPLMN. This indication is per Registration Area. + +NOTE 2: If the network supports EPS fallback for voice the 5GC can be configured not to perform the Voice Support Match Indicator procedure in order to set the IMS voice over PS session Supported Indication. + +The serving SNPN provides the IMS voice over PS indication based e.g. on local policy, UE capabilities, whether IP address preservation is possible, and how extended NR coverage is. This indication is per Registration Area. + +NOTE 3: Since over 3GPP access, in SNPN access mode there is only support for NR and the "voice centric" UE cannot reselect to another RAT in the same registered SNPN if the first Registration Area that the UE tries to register from cannot support IMS voice, it is recommended that support for IMS voice is provided homogeneously in the whole SNPN if at all. + +#### 5.16.3.2a IMS voice over PS Session Supported Indication over non-3GPP access + +The serving PLMN AMF shall send an indication toward the UE during the Registration procedure over non-3GPP access to indicate whether an IMS voice over PS session is supported or not supported via non-3GPP access. A UE with "IMS voice over PS" voice capability over non-3GPP access should take this indication (received in the Registration procedure performed over either 3GPP access or Non-3GPP access) into account when performing the selection between N3IWF/TNGF and ePDG described in clause 6.3.6. + +The serving PLMN AMF may only indicate IMS voice over PS session supported over non-3GPP access if the network is able to provide a successful IMS voice over PS session over N3IWF/TNGF connected to 5GC with a 5G QoS Flow that supports voice as specified in clause 5.7. + +#### 5.16.3.3 Homogeneous support for IMS voice over PS Session supported indication + +5GC shall support the usage of "Homogeneous Support of IMS Voice over PS Sessions" indication between AMF and UDM. + +When the AMF initiates Nudm\_UECM\_Registration operation to the UDM, it shall: + +- if "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving AMF for the UE, include the "Homogeneous Support of IMS Voice over PS Sessions" indication set to "Supported"; +- if none of the TAs of the serving AMF supports "IMS Voice over PS Sessions" for the UE, include the "Homogeneous Support of IMS Voice over PS Sessions" indication set to "Not supported"; +- if "IMS Voice over PS Sessions" support is either non-homogeneous or unknown, not include the "Homogeneous Support of IMS Voice over PS Sessions" indication. + +The AMF shall be able to provide the "Homogeneous Support of IMS Voice over PS Sessions" indication as described above to the UDM using Nudm\_UECM\_Update operation as specified in clause 4.2.2.2.2 of TS 23.502 [3]. + +The UDM shall take this indication into account when doing Terminating Access Domain Selection (T-ADS) procedure for IMS voice. + +NOTE: A TA supports "IMS Voice over PS Sessions" if the serving AMF indicates IMS voice over PS Session Supported Indication over 3GPP access to the UE, as described in clause 5.16.3.2. In order to support routing of incoming IMS voice calls to the correct domain, the network-based T-ADS (see TS 23.292 [63] and TS 23.221 [23]) requires that the "Homogeneous Support of IMS Voice over PS Sessions" indication is set to "Supported" for all registered TAs of the UE or "Not supported" for all registered TAs of the UE. + +#### 5.16.3.4 P-CSCF address delivery + +At PDU Session Establishment procedure related to IMS, SMF shall support the capability to send the P-CSCF address(es) to UE. The SMF is located in VPLMN if LBO is used. This is sent by visited SMF if LBO is used. For Home routed, this information is sent by the SMF in HPLMN. P-CSCF address(es) shall be sent transparently through AMF, and in the case of Home Routed also through the SMF in VPLMN. The P-CSCF IP address(es) may be locally configured in the SMF, or discovered using NRF as described in clause 5.16.3.11. + +NOTE 1: Other options to provide P-CSCF to the UE as defined in TS 23.228 [15] is not excluded. + +NOTE 2: PDU Session for IMS is identified by "APN" or "DNN". + +In the case of SNPN access the SMF is always located in the serving SNPN (no support for Home Routed traffic); therefore, the serving SMF sends the P-CSCF address(es) to the UE. + +#### 5.16.3.5 Domain selection for UE originating sessions / calls + +For UE originating calls, the 5GC capable UE performs access domain selection. The UE shall be able to take following factors into account for access domain selection decision: + +- The state of the UE in the IMS. The state information shall include: Registered, Unregistered. +- The "IMS voice over PS session supported indication" as defined in clause 5.16.3.2. + +- Whether the UE is expected to behave in a "voice centric" or "data centric" way for 5GS. +- UE capability of supporting IMS PS voice. +- UE capability for operating in dual-registration mode with selective PDU Session transfer as defined in clause 5.17.2.3.3. +- Whether 3GPP PS Data Off is active or not and whether IMS voice is included in 3GPP PS Data Off Exempt Services or not as defined in clause 5.24. + +NOTE 1: In this release of the specification, the exact logic of which PDU sessions are kept in which system for Dual Registration UE with selective transfer of certain PDU Sessions as defined in clause 5.17.2.3.3, is left up to UE implementation. The voice centric UE will keep the PDU Session used for IMS services to a system that supports voice over IMS. The voice centric UE can re-register with the IMS (if needed) when the IMS PDU session is transferred between 5GS and EPS. + +To allow for appropriate domain selection for originating voice calls, the UE shall attempt Initial Registration in 5GC. If the UE fails to use IMS for voice, e.g. due to "IMS voice over PS session supported indication" indicates voice is not supported in 5G System, the UE behaves as described below for "voice centric" for 5GS or "data centric" for 5GS: + +- A UE set to "voice centric" for 5GS shall always try to ensure that Voice service is possible. A voice centric 5GC capable and EPC capable UE unable to obtain voice service in 5GS shall not select a cell connected only to 5GC. By disabling capabilities to access 5GS, the UE re-selects to E-UTRAN connected to EPC first (if available). When the UE selects E-UTRAN connected to EPC, the UE performs Voice Domain Selection procedures as defined in TS 23.221 [23]. +- A UE set to "data centric" for 5GS does not need to perform any reselection if voice services cannot be obtained. + +NOTE 2: The related radio capabilities in order for the voice centric UE to not reselect to NR or E-UTRA cell connected to 5GC (i.e. avoid ping pong) will be defined by RAN WGs. + +#### 5.16.3.6 Terminating domain selection for IMS voice + +When requested by IMS, the UDM/HSS shall be able to query the serving AMF for T-ADS related information. T-ADS is a functionality located in the IMS and is performed as specified in TS 23.221 [23]. + +The AMF shall respond to the query with the following information unless the UE is detached: + +- whether or not IMS voice over PS Session is supported in the registration area (s) where the UE is currently registered; +- whether or not IMS voice over PS Session Supported Indication over non-3GPP access is supported in the WLAN where the UE is currently registered; +- the time of the last radio contact with the UE; and +- the current Access Type and RAT type. + +#### 5.16.3.7 UE's usage setting + +If the UE is configured to support IMS voice, the UE shall include the information element "UE's usage setting" in Registration Request messages. The UE's usage setting indicates whether the UE behaves in a "voice centric" or "data centric" way (as defined in clause 5.16.3.5). + +A UE supporting IMS voice over 3GPP access connected to 5GC and that is EPS capable shall also support IMS voice over E-UTRA connected to EPC. + +NOTE: Depending on operator's configuration, the UE's usage setting can be used by the network to choose the RFSP Index in use (see clause 5.3.4.3). As an example, this enables the enforcement of selective idle mode camping over E-UTRA for voice centric UEs. + +#### 5.16.3.8 Domain and Access Selection for UE originating SMS + +##### 5.16.3.8.1 UE originating SMS for IMS Capable UEs supporting SMS over IP + +To allow for appropriate domain selection for SMS delivery, it should be possible to provision UEs with the following HPLMN operator preferences on how an IMS enabled UE is supposed to handle SMS services: + +- SMS is not to be invoked over IP networks: the UE does not attempt to deliver SMS over IP networks. The UE attempts to deliver SMS over NAS signalling. +- SMS is preferred to be invoked over IP networks: the UE attempts to deliver SMS over IP networks. If delivery of SMS over IP networks is not available, the UE attempts to deliver SMS over NAS signalling. + +##### 5.16.3.8.2 Access Selection for SMS over NAS + +It should be possible to provision UEs with the HPLMN SMS over NAS operator preferences on access selection for delivering SMS over NAS signalling. + +Based on the SMS over NAS preference: + +- SMS is preferred to be invoked over 3GPP access for NAS transport: the UE attempts to deliver MO SMS over NAS via 3GPP access if the UE is both registered in 3GPP access and non-3GPP access. +- SMS is preferred to be invoked over non-3GPP access for NAS transport: the UE attempts to deliver MO SMS over NAS via non-3GPP access if the UE is both registered in 3GPP access and non-3GPP access. If delivery of SMS over NAS via non-3GPP access is not available, the UE attempts to deliver SMS over NAS via 3GPP access. + +#### 5.16.3.9 SMF support for P-CSCF restoration procedure + +For the support of P-CSCF restoration the SMF behaves as described in TS 23.380 [61]. + +#### 5.16.3.10 IMS Voice Service via EPS Fallback or RAT fallback in 5GS + +In order to support various deployment scenarios for obtaining IMS voice service, the UE and NG-RAN may support the mechanism to direct or redirect the UE from NG-RAN either towards E-UTRA connected to 5GC (RAT fallback) or towards EPS (E-UTRAN connected to EPC System fallback). + +Following principles apply for IMS Voice Service: + +- The serving AMF indicates toward the UE during the Registration procedure that IMS voice over PS session is supported. +- If a request for establishing the QoS Flow for IMS voice reaches the NG-RAN, the NG-RAN responds indicating rejection of the establishment request and the NG-RAN may trigger one of the following procedures depending on UE capabilities, N26 availability, network configuration and radio conditions: + - Redirection to EPS; + - Handover procedure to EPS; + - Redirection to E-UTRA connected to 5GC; or + - Handover to E-UTRA connected to 5GC. +- If needed, Network Provided Location Information is provided as described in clauses 4.13.6.1 and 4.13.6.2 of TS 23.502 [3]. +- The ongoing IMS voice session is not impacted by a change of the IMS voice over PS session indicator from supported to unsupported (e.g. the UE receives during RAT Fallback or EPS Fallback the IMS voice over PS session indicator indicating that IMS voice over PS sessions are not supported). + +NOTE: Any change in IMS voice over PS session indicator applies to new IMS sessions initiated only after the ongoing IMS voice session is terminated. + +During any release of RRC connection including after EPS/RAT fallback is performed, the eNB or NG-RAN node may provide to the UE dedicated idle mode priorities for NR as defined in TS 36.331 [51] taking into account RFSP, PLMNs contained in Handover Restriction List and local operator policy. If the UE remains ECM/CM-CONNECTED after the voice call has ended, the eNB or NG-RAN node may trigger handover to NR connected to 5GC, if configured to do so, taking into account local operator policy and Handover Restriction List. + +#### 5.16.3.11 P-CSCF discovery and selection + +P-CSCF selection functionality may be used by the SMF to select the P-CSCF for an IMS PDU Session of the UE. + +The SMF can utilize the Network Repository Function to discover the P-CSCF instance(s). The NRF provides the IP address or the FQDN of P-CSCF instance(s) to the SMF. The P-CSCF selection function in the SMF selects the P-CSCF instance(s) based on the available P-CSCF instances obtained from NRF or based on the configured P-CSCF information in the SMF. If the SMF receives FQDN(s) from the NRF or is configured with FQDN(s) the SMF shall resolve these to IP addresses for sending to the UE in the PDU session response. + +The following factors may be considered during the P-CSCF discovery and selection: + +- S-NSSAI of the PDU Session. +- UE location information. +- Local operator policies. +- Availability of candidate P-CSCFs. +- UE IP address. +- Access Type. +- Proximity to location of selected UPF. +- Selected Data Network Name (DNN). + +#### 5.16.3.12 HSS discovery and selection + +HSS discovery and selection functionality is used by the I-CSCF/S-CSCF/IMS-AS to select an HSS that manages the user's IMS subscriptions and has the ability to serve the IMS services for the UE, see clause AA.3.3 of TS 23.228 [15] and clause 6.3.1 for details. + +### 5.16.4 Emergency Services + +#### 5.16.4.1 Introduction + +Emergency Services are provided to support IMS emergency sessions. "Emergency Services" refers to functionalities provided by the serving network when the network is configured to support Emergency Services. Emergency Services are provided to normally registered UEs and to Emergency Registered UEs, that can be either normally registered or in limited service state. Depending on local regulation, receiving Emergency Services in limited service state does not require a valid subscription. Depending on local regulation and on operator's policy, the network may allow or reject a registration request for Emergency Services (i.e. Emergency Registration) from UEs that have been identified to be in limited service state. Four different behaviours of Emergency Services as defined in clause 4.3.12.1 of TS 23.401 [26] are supported. + +Emergency Services shall not be provided to a UE over 3GPP access and non-3GPP access concurrently. Transfer from one Access Type to the other takes place as follows: + +- a UE may be Emergency or normally Registered and have an emergency PDU session over non-3GPP access or may be attached with an emergency session to ePDG over untrusted WLAN (as defined in TS 23.402 [43]) when 3GPP access becomes available. In which case the UE may have to register over 3GPP access and check first the support for Emergency Services over the 3GPP RAT it has selected (e.g. based on Emergency Services Support indication, Emergency Services Fallback, AS broadcast indicator). If there is native support for Emergency Services in the selected 3GPP RAT the UE will attempt to transfer the emergency PDU session from non-3GPP access to 3GPP access (see clause 4.9.2 or clause 4.9.3 of TS 23.502 [3]). If there is no native support for + +Emergency Services in the selected RAT, but Emergency Services Fallback to another RAT in 5GS or to another System where Emergency Services is supported (based on the conditions defined in clause 5.16.4.11), the UE may trigger first Emergency Services Fallback (see clause 4.13.4.2 of TS 23.502 [3]) and then attempt to transfer the emergency PDU session from non-3GPP access to 3GPP access (see clause 4.9.2 of TS 23.502 [3]). During the session transfer the UE may be registered to receive emergency services over both 3GPP access and non-3GPP access concurrently. + +NOTE 1: The conditions upon which the UE determines that 3GPP access becomes available are implementation dependent. + +A UE may only attempt to use Emergency Services over non-3GPP access if it is unable to use Emergency Services over 3GPP access as specified in TS 23.167 [18]. + +The UE is only allowed to have one PDU session for Emergency services at a time. A PDU Session cannot be changed between a PDU Session for Non-Emergency services and a PDU Session for Emergency services. PDU session for emergency services can be transferred from one Access Type to another as specified in clause 5.16.4.9. + +To provide Emergency Services, the AMF is configured with Emergency Configuration Data that are applied to Emergency Services that are established by an AMF based on request from the UE. The AMF Emergency Configuration Data contains the S-NSSAI and Emergency DNN which is used to derive an SMF. In addition, the AMF Emergency Configuration Data contains UE-AMBR and may also contain the statically configured SMF for the Emergency DNN. The SMF may also store Emergency Configuration Data that contains statically configured UPF information for the Emergency DNN. + +NOTE 2: The Network slices associated with emergency services are assumed to be configured consistently in the AMF (i.e. emergency configuration data) and NG-RAN nodes within the corresponding Registration Area where emergency services are to be supported. + +When the UE is camped normally in the cell, i.e. not in limited service state, during Registration procedure described in clause 4.2.2.2 of TS 23.502 [3], the serving AMF includes an indication for Emergency Services Support within the Registration Accept to the UE. For 3GPP access, the Emergency Services Support indication is valid within the current Registration Area per RAT (i.e. this is to cover cases when the same registration area supports multiple RATs and they have different capability). + +The Emergency Services Support is configured in the AMF according to local regulations and network capabilities. AMF includes Emergency Services Support indicator in the Registration Accept message to indicate that the UE can setup emergency PDU Session to obtain emergency services. The AMF may include additional local emergency numbers associated with the serving network for the UE, further defined in TS 24.501 [47]. + +During Registration procedures over 3GPP access in a PLMN, the 5GC includes the Emergency Services Support indicator, valid for the current Registration Area and indicating per RAT that Emergency Services are supported if any of the following conditions is true within the current Registration Area: + +- the Network is able to support Emergency Services natively over 5GS; +- E-UTRA connected to 5GC supports IMS Emergency Services (e.g. voice), and the NG-RAN is able to trigger handover or redirection from NR to E-UTRA connected to 5GC at QoS Flow establishment for IMS Emergency Services (e.g. voice); +- NG-RAN is able to trigger handover to EPS at QoS Flow establishment for IMS Emergency Services (e.g. voice); +- NG-RAN is able to trigger redirection to EPS at QoS Flow establishment for IMS Emergency Services (e.g. voice); or +- NG-RAN is able to trigger 5G SRVCC handover to UTRAN for IMS Emergency Services (i.e. voice). + +During Registration procedures over non-3GPP access, the 5GC indicates that Emergency Services are supported if the Network is able to support Emergency Services natively over 5GS. + +In the case of SNPn, during Registration procedures over 3GPP access, the 5GC includes the Emergency Services Support indicator, valid for the current Registration Area indicating that Emergency Services are supported if the following condition is true within the current Registration Area: + +- the Network is able to support Emergency Services natively over 5GS. + +The 5GC includes an indication per RAT whether it supports Emergency Services Fallback (as defined in clause 5.16.4.11) to another RAT in 5GS or to another System where Emergency Services are supported natively. The Emergency Services Fallback support indicator is valid within the current Registration Area per RAT. + +If a certain RAT is restricted for Emergency Services, AMF signals that the corresponding RAT is restricted for Emergency Services Support to the Master RAN Node. This helps assist the Master RAN node determine whether to set up Dual Connectivity for Emergency Services. + +UEs that are in limited service state, as specified in TS 23.122 [17], or that camp normally on a cell but failed to register successfully to the network under conditions specified in TS 24.501 [47], initiate the Registration procedure by indicating that the registration is to receive Emergency Services, referred to as Emergency Registration, and a Follow-on request is included in the Registration Request to initiate PDU Session Establishment procedure with a Request Type indicating "Emergency Request". UEs that had registered for normal services and do not have emergency PDU Session established and that are subject to Mobility Restriction in the present area or RAT (e.g. because of restricted tracking area) shall initiate the UE Requested PDU Session Establishment procedure to receive Emergency Services, i.e. with a Request Type indicating "Emergency Request". Based on local regulation, the network supporting Emergency Services for UEs in limited service state provides Emergency Services to these UE, regardless whether the UE can be authenticated, has roaming or Mobility Restrictions or a valid subscription. + +For Emergency Services over 3GPP access via PLMN, other than eCall over IMS, the UEs in limited service state that do not operate in SNPN access mode determine that the cell supports Emergency Services over NG-RAN from a broadcast indicator in AS. The cell connected to EPC and 5GC broadcasts separate broadcast indicator for EPC and 5GC to indicate support of emergency services by the EPC and 5GC. If the UE supports SNPN access mode, is in limited service state, is not operating in SNPN access mode, needs to make an emergency call and cannot find an acceptable cell in any PLMN, the UE may activate SNPN access mode and attempt to camp on an acceptable cell of any available SNPN supporting emergency calls (irrespective of SNPN ID or GIN) as defined in TS 23.122 [17]. For Emergency Services over untrusted non-3GPP access, other than eCall over IMS, the UE in limited service state selects any N3IWF as specified in clause 6.3.6. Emergency calls for eCall Over IMS may only be performed if the UE has a USIM. + +For Emergency Services over NR via SNPN, other than eCall over IMS, the UEs in limited service state that operate in SNPN access mode determine that the cell supports Emergency Services over NR from a broadcast indicator in AS and indication that the SNPN supports Emergency Services. If the UE operates in SNPN access mode and is in limited service state, the UE shall attempt to camp on an acceptable cell of any available SNPN supporting emergency calls (irrespective of SNPN ID or GIN). If the UE cannot find acceptable cell on any available SNPN, the UE shall deactivate SNPN access mode and camp on any available PLMN cell supporting emergency calls (irrespective of PLMN ID) as defined in TS 23.122 [17]. + +For NR satellite access, if a UE in limited service state is aware of its location, the UE selects a PLMN that is allowed to operate in the UE location as specified in TS 23.122 [17]. The network may be configured to verify the location of a UE that is registering for emergency services as specified in clause 5.4.11.4. + +There is no support for eCall over IMS for SNPNs in this Release. + +A serving network shall provide an Access Stratum broadcast indication from NG-RAN (NR or E-UTRA connected to 5GC) to UEs indicating whether eCall Over IMS is supported: + +- When an E-UTRA cell is connected to EPC and 5GC, the cell broadcasts separate Access stratum broadcast indication for 5GC and EPC to indicate support of eCall over IMS by 5GC and EPC. +- A UE that is not in limited service state determines that the NG-RAN cell supports eCall Over IMS via 5GC using the broadcast indicator for eCall over IMS. Emergency calls for eCall over IMS are not supported over non-3GPP access. + +NOTE 3: The Access Stratum broadcast indicator is determined according to operator policies and minimally indicates that the PLMN, or all of the PLMNs in the case of network sharing, and at least one emergency centre or PSAP to which an eCall Over IMS can be routed, support eCall Over IMS. + +- A UE in limited service state determines that the cell supports eCall Over IMS using both the broadcast indicator for support of Emergency Services over NG-RAN and the broadcast indicator of NG-RAN for eCall over IMS. Emergency calls for eCall Over IMS are not supported over Non-3GPP access and NR via SNPN. + +NOTE 4: The broadcast indicator for eCall Over IMS does not indicate whether UEs in limited service state are supported. So, the broadcast indicator for support of Emergency Services over NG-RAN that indicates limited service state support needs to be applied in addition. + +For a UE that is Emergency Registered, if it is unauthenticated the security context is not set up on UE. + +In order to receive Emergency Services, UEs that camp on a suitable cell in RM-DEREGISTERED state (i.e. without any conditions that result in limited service state), or that decide to access 5GC via non-3GPP access (and not in limited service state over non-3GPP access), initiate the Initial Registration procedure for normal service instead of Emergency Registration. Upon successful registration, such UEs shall initiate the UE Requested PDU Session Establishment procedure with a Request Type indicating "Emergency Request" to receive Emergency Services if the AMF indicated support for Emergency Services in 5GC (for the RAT the UE is currently camped on when UE is camping on 3GPP access). The UEs that camp normally on a cell or that are connected via Non-3GPP access are informed that the PLMN supports Emergency Services over 5G-AN from the Emergency Services Support indicator in the Registration procedure. This applies to both 3GPP and non-3GPP Access Types. There is no support for Emergency Services for SNPN that is accessed via NWu from a PLMN. + +NOTE 5: The Emergency Services Support indicator in the Registration procedures does not indicate support for eCall Over IMS. + +For a UE that is Emergency Registered, normal PLMN or SNPN selection principles apply after the end of the IMS emergency session. + +NOTE 6: For Emergency Services, there is no support for inter PLMN mobility thus there is a risk of service disruption due to failed inter PLMN mobility attempts when there is no session continuity (e.g. change of anchor SMF/UPF due to mobility) for the PDU Session and/or based on operator policies. + +NOTE 7 Based on operator policies, Inter PLMN mobility with session continuity can be supported for Emergency Services if the anchor SMF/UPF for PDU Session supporting Emergency Services does not change. + +The UE shall set the RRC establishment cause to emergency as defined in TS 38.331 [28] when it requests an RRC Connection in relation to an emergency session. + +In the case of Limited Service state, UE shall not include any Network Slice related parameters when communicating with the network. + +When a PLMN or SNPN supports IMS and Emergency Services: + +- all AMFs in that PLMN or SNPN shall have the capability to support Emergency Services. +- at least one SMF shall have this capability. + +For other emergency scenarios (e.g. UE autonomous selection for initiating Emergency Services), refer to TS 23.167 [18] for domain selection principles. + +For emergency service support in Public network integrated NPNs, refer to clause 5.30.3.5. + +For emergency support via 5G ProSe UE-to-Network Relaying, refer to TS 23.304 [128]. + +#### 5.16.4.2 Architecture Reference Model for Emergency Services + +According to clause 4.2, the non-roaming architectures (Figure 4.2.3-1 and Figure 4.2.3-2) and roaming architecture with the visited operator's application function (Figure 4.2.4-1 and Figure 4.2.4-4) apply for Emergency Services. The other non-roaming and roaming architectures with services provided by the home network do not apply for Emergency Services. + +#### 5.16.4.3 Mobility Restrictions and Access Restrictions for Emergency Services + +When Emergency Services are supported and local regulation requires IMS Emergency Sessions to be provided regardless of Mobility Restrictions or Access Restrictions, the Mobility Restrictions or Access Restrictions (see clause 5.3.4.1) should not be applied to UEs receiving Emergency Services. Additionally, due to Mobility Restrictions or Access Restrictions (e.g. CAG restrictions) for normally registered UEs, that have established both non-emergency PDU Sessions and emergency PDU Session, the AMF indicates to the SMF to perform a local release of all non-emergency PDU Sessions via PDU Session Release procedure as specified in clause 4.3.4 of TS 23.502 [3]. The UE + +locally releases non-emergency PDU Sessions. The AMF and the UE behave as if the UE is emergency registered as described in TS 24.501 [47]. + +When the (R)AN resources for Emergency Services are established, the ARP value for Emergency Services indicates the usage for Emergency Services to the 5G-AN. + +During handover, the source NG-RAN and source AMF ignore any UE related restrictions during handover evaluation when there is an active PDU Session associated with emergency service. + +During Mobility Registration Update procedures, including a Mobility Registration Update as part of a handover, the target AMF ignores any Mobility Restrictions or access restrictions for UE with emergency services where required by local regulation. Any non-emergency services are not allowed, by the target network when not allowed by the subscription for the target location. To allow the UE in limited service state (either Emergency Registered or registered for normal service) over a given Access Type to get access to normal services over this Access Type after the Emergency Session has ended and when it has moved to a new area that is not stored by the UE as a forbidden area, after allowing a period of time for subsequent Emergency Services, the UE may explicitly deregister and register for normal services over this Access Type without waiting for the emergency PDU Session Release by the SMF. + +This functionality applies to all mobility procedures. + +#### 5.16.4.4 Reachability Management + +Over 3GPP access, an Emergency Registered UE when its Periodic Registration Update timer expires shall not initiate a Periodic Registration Update procedure but shall enter the RM-DEREGISTERED state. For such UEs, the AMF runs a mobile reachable timer with a similar value to the UE's Periodic Registration Update timer. After expiry of this timer the AMF may change the UE RM state for 3GPP Access in the AMF to RM-DEREGISTERED. The AMF assigns the Periodic Registration Update timer value to Emergency Registered UEs. This timer keeps the Emergency Registered UE registered for Emergency Services after change to CM-IDLE state to allow for a subsequent Emergency Service without a need for a new Emergency Registration. + +Over non-3GPP access, an Emergency Registered UE is only reachable in CM-CONNECTED state: since the UE may only use Emergency Services over Non-3GPP access when it is not possible over 3GPP access, 3GPP access is assumed to be unavailable for paging the UE. + +#### 5.16.4.5 SMF and UPF selection function for Emergency Services + +When a SMF is selected for Emergency Services, the SMF selection function described in clause 6.3.2 for normal services is applied to the Emergency DNN or the AMF selects the SMF directly from the AMF Emergency Configuration Data. If the SMF selection function described in clause 6.3.2 is used it shall always derive a SMF in the Serving PLMN or SNPN, which guarantees that the IP address is also allocated by the Serving PLMN or SNPN. When a UPF is selected for Emergency Services, the UPF selection function described in clause 6.3.3 for normal services is applied to the Emergency DNN or the SMF selects the UPF directly from the SMF Emergency Configuration Data. The information in the AMF Emergency Configuration Data and the SMF Emergency Configuration Data is specified in clause 5.16.4.1. + +#### 5.16.4.6 QoS for Emergency Services + +Local regulation may require supporting emergency calls from an unauthorised UE. In such a case, the SMF may not have subscription data. Additionally, the local network may want to provide Emergency Services support differently than what is allowed by a UE subscription. Therefore, the initial QoS parameters used for establishing Emergency Services are configured in the V-SMF (local network) in the SMF Emergency Configuration Data. + +This functionality is used by the UE Requested PDU Session Establishment procedure when establishing Emergency Services. + +#### 5.16.4.7 PCC for Emergency Services + +Dynamic PCC is used for UEs establishing emergency service and shall be used to manage IMS emergency sessions when an operator allows IMS emergency sessions. When establishing Emergency Services with a SMF, the PCF provides the SMF with the QoS parameters, including an ARP value reserved for the Emergency Services to prioritize the QoS Flows when performing admission control, as defined in TS 23.503 [45]. + +The PCF rejects an IMS session established via the emergency PDU Session if the AF (i.e. P-CSCF) does not provide an emergency indication to the PCF. + +#### 5.16.4.8 IP Address Allocation + +Emergency service is provided by the serving PLMN or SNPN. The UE and serving PLMN or SNPN must have compatible IP address versions in order for the UE to obtain a local emergency PDU Session. + +#### 5.16.4.9 Handling of PDU Sessions for Emergency Services + +The QoS Flows of a PDU Session associated with the emergency DNN shall be dedicated for IMS emergency sessions and shall not allow any other type of traffic. The emergency contexts shall not be changed to non-emergency contexts and vice versa. The UPF shall block any traffic that is not from or to addresses of network functions (e.g. P-CSCF) providing Emergency Services. + +If there is already an emergency PDU Session over a given Access Type (3GPP access or non-3GPP access), the UE shall not request another emergency PDU Session over any Access Type except for handing over the existing emergency PDU Session to the other Access Type. + +If the SMF receives a new emergency PDU session establishment request and an emergency PDU Session exists for the same UE over any Access Type, the SMF shall remove the existing SM context locally and clear the associated resources in the network and proceed with the new request. + +**NOTE:** If the UE releases emergency PDU session locally and requests for establishment of a new one before the SMF has released the emergency PDU session due to PDU session inactivity as specified in clause 4.3.4.2 of TS 23.502 [3], the above duplicate emergency PDU session handling in the network removes the old emergency PDU session as part of establishing a new one. This releases all emergency call back resources related with the old emergency PDU Session. + +The ARP reserved for emergency service shall only be assigned to QoS Flows associated with an emergency PDU Session. If the UE is Emergency Registered over a given access, it shall not request a PDU Session to any other DNN over this access. + +##### 5.16.4.9a Handling of PDU Sessions for normal services for Emergency Registered UEs + +For an Emergency Registered UE over a given Access Type: + +- the UE shall not initiate the UE Requested PDU Session Establishment procedure for normal service over this Access Type; and +- the network shall reject any PDU Session Establishment request for normal service from the UE on this Access Type; +- the UE may attempt to receive normal service over another Access Type if not otherwise prevented by the present document. + +#### 5.16.4.10 Support of eCall Only Mode + +For service requirements for eCall only mode, refer to TS 22.101 [33]. + +A UE configured for eCall Only Mode shall remain in RM-DEREGISTERED state, shall camp on a network cell when available but shall refrain from any Registration Management, Connection Management or other signalling with the network. The UE may instigate Registration Management and Connection Management procedures in order to establish, maintain and release an eCall Over IMS session or a session to any non-emergency MSISDN(s) or URI(s) configured in the USIM for test and/or terminal reconfiguration services. Following the release of either session and after the UE has left RRC\_CONNECTED state, the UE starts a timer whose value depends on the type of session (i.e. whether eCall or a session to a non-emergency MSISDN or URI for test/reconfiguration). While the timer is running, the UE shall perform normal RM/CM procedures and is permitted to respond to paging to accept and establish an incoming session (e.g. from an emergency centre, PSAP or HPLMN operator). When the timer expires, once the UE is + +not in RRC\_CONNECTED state, the UE shall perform a UE-initiated Deregistration procedure if still registered and enter RM-DEREGISTERED state. + +- NOTE 1: An HPLMN operator can change the eCall Only Mode configuration state of a UE in the USIM. An HPLMN operator can also instead add, modify or remove a non-emergency MSISDN or URI in the USIM for test and/or terminal reconfiguration services. This can occur following a UE call to a non-emergency MSISDN or URI configured for reconfiguration. When the eCall Only Mode configuration is removed, the UE operates as a normal UE that can support eCall over IMS. +- NOTE 2: A test call and a reconfiguration call can be seen as normal (non-emergency) call by a serving PLMN and normal charging rules can apply depending on operator policy. +- NOTE 3: An MSISDN configured in the USIM for test and/or terminal reconfiguration services for eCall Over IMS can differ from an MSISDN configured in the USIM for test services for eCall over the CS domain. + +#### 5.16.4.11 Emergency Services Fallback + +In order to support various deployment scenarios for obtaining Emergency Services, the UE and 5GC may support the mechanism to direct or redirect the UE either towards E-UTRA connected to 5GC (RAT fallback) when only NR does not support Emergency Services or towards EPS (E-UTRAN connected to EPC System fallback) when the 5GC does not support Emergency Services. Emergency Services fallback may be used when the 5GS does not indicate support for Emergency Services (see clause 5.16.4.1) and indicates support for Emergency Services fallback. + +Following principles apply for Emergency Services Fallback: + +- If the AMF indicates support for Emergency Services fallback in the Registration Accept message, then in order to initiate Emergency Service, normally registered UE supporting Emergency Services fallback shall initiate a Service Request with Service Type set to Emergency Services fallback as defined in clause 4.13.4.1 of TS 23.502 [3]. +- AMF uses the Service Type Indication within the Service Request to redirect the UE towards the appropriate RAT/System. The 5GS may, for Emergency Services, trigger one of the following procedures: + - Handover or redirection to EPS. + - Handover or redirection to E-UTRA connected to 5GC. +- After receiving the Service Request for Emergency Fallback, the AMF triggers N2 procedure resulting in either CONNECTED state mobility (Handover procedure) or IDLE state mobility (redirection) to either E-UTRA/5GC or to E-UTRAN/EPC depending on factors such as N26 availability, network configuration and radio conditions. In the N2 procedure, the AMF based on support for Emergency Services in 5GC or EPC may indicate the target CN for the RAN node to know whether inter-RAT fallback or inter-system fallback is to be performed. The target CN indicated in the N2 procedure is also conveyed to the UE in order to be able to perform the appropriate NAS procedures (S1 or N1 Mode). +- When the AS re-keying procedure and the Emergency Fallback procedure collides, the AMF gives up the AS re-keying procedure and only initiates the Emergency Fallback procedure. + +NOTE 1: Emergency Services Fallback to EPS can be followed by an onward movement to GERAN or UTRAN via CSFB procedures if the PLMN does not support IMS emergency services. + +NOTE 2: If the UE has signalled that S1 mode is disabled for a network that only supports IMS voice via EPS Fallback, the AMF will not indicate that Emergency Services Fallback is supported over 3GPP access. + +Emergency Services fallback is supported only in case of PLMN. Emergency Services Fallback is not supported for SNPN. + +### 5.16.5 Multimedia Priority Services + +TS 22.153 [24] specifies the service requirements for Multimedia Priority Service (MPS). MPS allows Service Users (as per TS 22.153 [24]) priority access to system resources in situations such as during congestion, creating the ability to deliver or complete sessions of a high priority nature. Service Users are government-authorized personnel, emergency management officials and/or other authorized users. MPS supports priority sessions on an "end-to-end" priority basis. + +MPS is based on the ability to invoke, modify, maintain and release sessions with priority, and deliver the priority media packets under network congestion conditions. MPS is supported in a roaming environment when roaming agreements are in place and where regulatory requirements apply. + +NOTE 1: If a session terminates on a server in the Internet (e.g. web-based service), then the remote end and the Internet transport are out of scope for this specification. + +MPS is supported for Service Users using UEs connecting via 3GPP access. MPS is also supported for Service Users using UEs that support connecting via Trusted or Untrusted non-3GPP access via WLAN for MPS. N3IWF selection is according to clause 6.3.6 for PLMN access. + +A Service User may use an MPS-subscribed UE or any other UE to obtain MPS. An MPS-subscribed UE obtains priority access to the Radio Access Network by using the Unified Access Control mechanism according to TS 22.261 [2]. This mechanism provides preferential access to UEs based on its assigned Access Identity. If an MPS-subscribed UE belongs to the special Access Identity as defined in TS 22.261 [2], the UE has preferential access to the network compared to ordinary UEs in periods of congestion. + +MPS subscription allows users to receive priority services, if the network supports MPS. The same MPS subscription applies to access via 3GPP access and non-3GPP access via WLAN. MPS subscription entitles a USIM with special Access Identity. MPS subscription includes indication for support of priority PDU connectivity service including MPS for Data Transport Service and IMS priority service support for the end user. Priority Level regarding QoS Flows and IMS are also part of the MPS subscription information. The usage of Priority Level is defined in TS 22.153 [24], TS 23.503 [45] and TS 23.228 [15]. + +NOTE 2: The same MPS subscription in the UDM and/or on the USIM is used for priority treatment of 3GPP procedures when the access is WLAN. + +NOTE 3: The term "Priority PDU connectivity services" is used to refer to 5G System functionality that corresponds to the functionality as provided by LTE/EPC Priority EPS bearer services in clause 4.3.18.3 of TS 23.401 [26]. + +MPS includes signalling priority and media priority. All MPS-subscribed UEs get priority for QoS Flows (e.g. used for IMS signalling) when established to the DN that is configured to have priority for a given Service User by setting MPS-appropriate values in the QoS profile in the UDM. + +Service Users are treated as On Demand MPS subscribers or not, based on regional/national regulatory requirements. On Demand service is based on Service User invocation/revocation explicitly and applied to the media QoS Flows being established. When not On Demand MPS service does not require invocation, and provides priority treatment for all QoS Flows only to the DN that is configured to have priority for a given Service User after attachment to the 5G network. + +MPS for Data Transport Service is an on-demand service that may be invoked/revoked by an authorized Service User using a UE with a subscription for MPS (i.e. according to its MPS profile), or using a UE that does not have a subscription for MPS (using methods not in scope of this specification). + +MPS for Data Transport Service requires explicit invocation. The Service User invokes the service by communicating with an AF. The authorization of an MPS for Data Transport Service request is done by the AF or the PCF according to clause 6.1.3.11 of TS 23.503 [45]. Upon successful authorization, the PCF performs the necessary actions to achieve appropriate ARP and 5QI settings for the QoS Flows (see clause 6.1.3.11 of TS 23.503 [45]). + +MPS for Data Transport Service enables the prioritization of all traffic on the QoS Flow associated with the default QoS rule and other QoS Flows upon AF request. The QoS modification to the QoS Flow associated with the default QoS rule and other QoS Flows is done based on operator policy and regulatory rules by means of local PCF configuration. + +NOTE 4: According to regional/national regulatory requirements and operator policy, On-Demand MPS (including MPS for Data Transport Service) Service Users can be assigned the highest priority. + +NOTE 5: If no configuration is provided, MPS for Data Transport Service applies only to the QoS Flow associated with the default QoS rule. + +NOTE 6: MPS for DTS controls the priority of traffic on QoS Flows independent of the application(s) being used. Other mechanisms (e.g. Priority PDU connectivity service) can be used to control the priority of traffic on other QoS Flows under the control of specific data application(s), based on operator policy. + +NOTE 7: MPS for Data Transport Service can be applied to any DNN other than the well-known DNN for IMS. + +For MPS for Data Transport Service, the AF may also create an SDF for priority signalling between the UE and the AF (see clause 6.1.3.11 of TS 23.503 [45]). + +Priority treatment is applicable to IMS based multimedia services and Priority PDU connectivity service including MPS for Data Transport Service. + +Priority treatment for MPS includes priority message handling, including priority treatment during authentication, security, and Mobility Management procedures. + +Priority treatment for MPS session requires appropriate ARP and 5QI (plus 5G QoS characteristics) setting for QoS Flows according to the operator's policy. + +NOTE 8: Use of QoS Flows for MPS with QoS characteristics signalled as part of QoS profile enables the flexible assignment of 5G QoS characteristics (e.g. Priority Level) for MPS. + +When an MPS session is requested by a Service User, the following principles apply in the network: + +- QoS Flows employed in an MPS session shall be assigned ARP value settings appropriate for the priority of the Service User. +- Setting ARP pre-emption capability and vulnerability for MPS QoS Flows, subject to operator policies and depending on national/regional regulatory requirements. +- Pre-emption of non-Service Users over Service Users during network congestion situation, subject to operator policy and national/regional regulations. + +The terminating network identifies the priority of the MPS session and applies priority treatment, including paging with priority, to ensure that the MPS session can be established with priority to the terminating user (either a Service User or normal user). + +MPS priority mechanisms can be classified as subscription-related, invocation-related, and those applied to existing QoS Flows. Subscription related mechanisms, as described in clause 5.22.2, are further divided into two groups: those which are always applied and those which are conditionally applied. Invocation-related mechanisms, as described in clause 5.22.3, are further divided into three groups: those that apply for mobile originated SIP call/sessions, those that apply for mobile terminated SIP call/sessions, and those that apply for the Priority PDU connectivity services including MPS for Data Transport Service. Methods applied to existing QoS Flows focus on handover and congestion control and are described in clause 5.22.4. + +NOTE 9: The network can hide its topology from the AF supporting MPS for Data Transport Service. At the same time, the UE needs to provide its locally known IP address to the AF supporting MPS for Data Transport Service to support interactions with the applicable PCF. Thus, there can be no NAT of the UE IP address between the UPF and the AF supporting MPS for Data Transport Service. + +For WLAN access, the UE may notify the TNAN/N3IWF of its MPS subscription before the NAS Registration Request. Based on operator policy, the TNAN/N3IWF may use this indication to provide this UE with priority treatment in the case of congestion/overload before receipt of the NAS Registration Request with an MPS priority establishment cause. + +### 5.16.6 Mission Critical Services + +According to TS 22.280 [37], a Mission Critical Service (MCX Service) is a communication service reflecting enabling capabilities Mission Critical Applications and provided to end users from Mission Critical Organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways). An MCX Service is either Mission + +Critical Push To Talk (MCPTT) as defined in TS 23.379 [38], Mission Critical Video (MCVideo) as defined in TS 23.281 [39], or Mission Critical Data (MCData) as defined in TS 23.282 [40] and represents a shared underlying set of requirements between two or more MCX Service types. MCX Services are not restricted only to the ones defined in this clause and such services can also have priority treatment, if defined via operator's policy and/or local regulation. + +MCX Services are based on the ability to invoke, modify, maintain and release sessions with priority, and deliver the priority media packets under network congestion conditions. As specified in clause 6.8 of TS 22.261 [2], MCX Users require 5GS functionality that allows for real-time, dynamic, secure and limited interaction with the QoS and policy framework for modification of the QoS and policy framework by authorized users. The limited interaction is based on operator policy, and provides specific limitations on what aspects of the QoS and policy framework an authorized MCX User can modify. MCX Services are supported in a roaming environment when roaming agreements are in place and where regulatory requirements apply. + +An MCX-subscribed UE obtains priority access to the Radio Access Network by using the Unified Access Control mechanism according to TS 22.261 [2]. This mechanism provides preferential access to UEs based on its assigned Access Identity. If an MCX-subscribed UE belongs to the special Access Identity as defined in TS 22.261 [2], the UE has preferential access to the network compared to ordinary UEs in periods of congestion. MCX subscription allows users to receive priority services, if the network supports MCX. MCX subscription entitles a USIM with special Access Identity. + +NOTE 1: For Mission Critical Services that require low latency and zero packet loss even for the first downlink packet(s), periodic keep-alive packets during interruptions of media transmission (e.g. Floor Idle as specified in TS 23.379 [38], referenced by TS 23.289 [184]), which is sent over user plane of PDU session, can be used so that the UE is kept in RRC\_CONNECTED state without being paged when unicast transmission is used. It is up to the implementation, the periodicity of the keep-alive packets configured in the AF can consider NG-RAN's configuration. + +NOTE 2: For support of Mission Critical Services that require low latency and zero packet loss when using MBS, see TS 23.247 [121]. + +MCX Services leverage the foundation of the 5G QoS Model as defined in clause 5.7, and 5G Policy Control as defined in clause 5.14. It requires that the necessary subscriptions are in place for both the 5G QoS Profile and the necessary Policies. In addition, MCX Services leverage priority mechanism as defined in clause 5.22. + +The terminating network identifies the priority of the MCX Service session and applies priority treatment, including paging with priority, to ensure that the MCX Service session can be established with priority to the terminating user (either an MCX User or normal user). + +Priority treatment for MCX Service includes priority message handling, including priority treatment during authentication, security, and Mobility Management procedures. + +Priority treatment for MCX Service sessions require appropriate ARP and 5QI (plus 5G QoS characteristics) setting for QoS Flows according to the operator's policy. + +NOTE 3: Use of QoS Flows for MCX Service sessions with non-standardized 5QI values enables the flexible assignment of 5G QoS characteristics (e.g. Priority Level). + +When a MCX Service session is requested by an MCX User, the following principles apply in the network: + +- QoS Flows employed in a MCX Service session shall be assigned ARP value settings appropriate for the priority of the MCX User. +- Setting ARP pre-emption capability and vulnerability of QoS Flows related to a MCX Service session, subject to operator policies and depending on national/regional regulatory requirements. +- Pre-emption of non-MCX Users over MCX Users during network congestion situations, subject to operator policy and national/regional regulations. + +Priority treatment is applicable to IMS based multimedia services and priority PDU connectivity services. + +Relative PDU priority decisions for MCX Service sessions are based on real-time data of the state of the network and/or based on modification of the QoS and policy framework by authorized users as described in clause 6.8 of TS 22.261 [2]. + +## 5.17 Interworking and Migration + +### 5.17.1 Support for Migration from EPC to 5GC + +#### 5.17.1.1 General + +Clause 5.17.1 describes the UE and network behaviour for the migration from EPC to 5GC. + +Deployments based on different 3GPP architecture options (i.e. EPC based or 5GC based) and UEs with different capabilities (EPC NAS and 5GC NAS) may coexist at the same time within one PLMN. + +It is assumed that a UE that is capable of supporting 5GC NAS procedures may also be capable of supporting EPC NAS (i.e. the NAS procedures defined in TS 24.301 [13]) to operate in legacy networks e.g. in the case of roaming. + +The UE will use EPC NAS or 5GC NAS procedures depending on the core network by which it is served. + +In order to support smooth migration, it is assumed that the EPC and the 5GC have access to a common subscriber database, that is HSS in the case of EPC and the UDM in the case of 5GC, acting as the master data base for a given user as defined in TS 23.002 [21]. The PCF has access to the UDR that acts as a common subscriber database for a given user identified by a SUPI using the Nudr services defined in TS 23.502 [3]. + +![Figure 5.17.1.1-1: Architecture for migration scenario for EPC and 5G CN. The diagram shows a central HSS + UDM connected to an EPC and a 5G CN. The EPC is connected to two E-UTRAN units, and the 5G CN is connected to an E-UTRAN unit and an NR unit. Four types of UEs are shown: EPC UE (E-UTRA only), EPC UE (E-UTRA + 5G RAN DC), N1 UE (E-UTRAN with or without 5G RAN DC), and N1 UE ((NR) with or without DC with E-UTRAN). Dashed lines represent NAS signaling paths: EPC NAS from EPC to E-UTRAN and UEs, and N1 from 5G CN to E-UTRAN, NR, and UEs. Solid lines represent data paths: S1 from EPC to E-UTRAN, and N2/N3 from 5G CN to E-UTRAN and NR.](062ad684575a714449a7e040c0e1ec00_img.jpg) + +Figure 5.17.1.1-1: Architecture for migration scenario for EPC and 5G CN. The diagram shows a central HSS + UDM connected to an EPC and a 5G CN. The EPC is connected to two E-UTRAN units, and the 5G CN is connected to an E-UTRAN unit and an NR unit. Four types of UEs are shown: EPC UE (E-UTRA only), EPC UE (E-UTRA + 5G RAN DC), N1 UE (E-UTRAN with or without 5G RAN DC), and N1 UE ((NR) with or without DC with E-UTRAN). Dashed lines represent NAS signaling paths: EPC NAS from EPC to E-UTRAN and UEs, and N1 from 5G CN to E-UTRAN, NR, and UEs. Solid lines represent data paths: S1 from EPC to E-UTRAN, and N2/N3 from 5G CN to E-UTRAN and NR. + +**Figure 5.17.1.1-1: Architecture for migration scenario for EPC and 5G CN** + +A UE that supports only EPC based Dual Connectivity with secondary RAT NR: + +- always performs initial access through E-UTRA (LTE-Uu) but never through NR; +- performs EPC NAS procedures over E-UTRA (i.e. Mobility Management, Session Management etc) as defined in TS 24.301 [13]. + +A UE that supports camping on 5G Systems with 5GC NAS: + +- performs initial access either through E-UTRAN that connects to 5GC or NR towards 5GC; +- performs initial access through E-UTRAN towards EPC, if supported and needed; +- performs EPC NAS or 5GC NAS procedures over E-UTRAN or NR respectively (i.e. Mobility Management, Session Management etc) depending on whether the UE requests 5GC access or EPC access, if the UE also supports EPC NAS. + +When camping on an E-UTRA cell connected to both EPC and 5GC, a UE supporting EPC NAS and 5GC NAS shall select a core network type (EPC or 5GC) and initiate the corresponding NAS procedure as specified in TS 23.122 [17]. + +In order to support different UEs with different capabilities in the same network, i.e. both UEs that are capable of only EPC NAS (possibly including EPC based Dual Connectivity with NR as secondary RAT) and UEs that support 5GC NAS procedures in the same network: + +- eNB that supports access to 5GC shall broadcast that it can connect to 5GC. Based on that, the UE AS layer indicates "E-UTRA connected to 5GC" capability to the UE NAS layer. In addition the eNB broadcasts the supported CIoT 5GS Optimisations that the UE uses for selecting a core network type. +- It is also expected that the UE AS layer is made aware by the UE NAS layer whether a NAS signalling connection is to be initiated to the 5GC. Based on that, UE AS layer indicates to the RAN whether it is requesting 5GC access (i.e. "5GC requested" indication). The RAN uses this indication to determine whether a UE is requesting 5GC access or an EPC access. RAN routes NAS signalling to the applicable AMF or MME accordingly. + +NOTE: The UE that supports EPC based Dual Connectivity with secondary RAT only does not provide this "5GC requested" indication at Access Stratum when it performs initial access and therefore eNB uses the "default" CN selection mechanism to direct this UE to an MME + +The 5GC network may steer the UE from 5GC based on: + +- Core Network type restriction (e.g. due to lack of roaming agreements) described in clause 5.3.4.1.1; +- Availability of EPC connectivity; +- UE indication of EPC Preferred Network Behaviour; and +- Supported Network Behaviour. + +The UE that wants to use one or more of these functionalities not supported by 5G System, when in CM-IDLE may disable all the related radio capabilities that allow the UE to access 5G System. The triggers to disable and re-enable the 5GS capabilities to access 5G System in this case are left up to UE implementation. + +#### 5.17.1.2 User Plane management to support interworking with EPS + +In order to support the interworking with EPC, the SMF+PGW-C provides information over N4 to the UPF+PGW-U related to the handling of traffic over S5-U. Functionality defined in TS 23.503 [45] for traffic steering control on SGi-LAN/N6 can be activated in UPF+PGW-U under consideration of whether the UE is connected to EPC or 5GC. + +When the UE is connected to EPC and establishes/releases PDN connections, the following differences apply to N4 compared to when the UE is connected to 5GC: + +- The CN Tunnel Info is allocated for each EPS Bearer. +- In addition to the Service Data Flow related information, the SMF+PGW-C shall be able to provide the GBR and MBR values for each GBR bearer of the PDN connection to the UPF+PGW-U. + +If the UE does not have preconfigured rules for associating an application to a PDN connection (i.e. the UE does not have rules in UE local configuration and is not provisioned with ANDSF rules), the UE should use a matching URSP rule as defined in TS 23.503 [45], if available, to derive the parameters, e.g. APN, for the PDN connection establishment and associating an application to the PDN connection. + +NOTE: The mapping between the parameters in the URSP rules and the parameters used for PDN connection establishment is defined in TS 24.526 [110]. + +#### 5.17.1.3 QoS handling for home routed roaming + +During mobility from EPS to 5GS, the handling of QoS constraints in V-SMF is specified in clauses 4.11.1.2.2 and 4.11.1.3.3 of TS 23.502 [3] and follows the same principle as described in clause 5.7.1.11. + +### 5.17.2 Interworking with EPC + +#### 5.17.2.1 General + +Interworking with EPC in this clause refers to mobility procedures between 5GC and EPC/E-UTRAN, except for clause 5.17.2.4. Network slicing aspects for EPS Interworking are specified in clause 5.15.7 + +In order to interwork with EPC, the UE that supports both 5GC and EPC NAS can operate in single-registration mode or dual-registration mode: + +- In single-registration mode, UE has only one active MM state (either RM state in 5GC or EMM state in EPC) and it is either in 5GC NAS mode or in EPC NAS mode (when connected to 5GC or EPC, respectively). UE maintains a single coordinated registration for 5GC and EPC. Accordingly, the UE maps the EPS-GUTI to 5G GUTI during mobility between EPC and 5GC and vice versa following the mapping rules in Annex B. To enable re-use of a previously established 5G security context when returning to 5GC, the UE also keeps the native 5G-GUTI and the native 5G security context when moving from 5GC to EPC. +- In dual-registration mode, UE handles independent registrations for 5GC and EPC using separate RRC connections. In this mode, UE maintains 5G-GUTI and EPS-GUTI independently. In this mode, UE provides native 5G-GUTI, if previously allocated by 5GC, for registrations towards 5GC and it provides native EPS-GUTI, if previously allocated by EPC, for Attach/TAU towards EPC. In this mode, the UE may be registered to 5GC only, EPC only, or to both 5GC and EPC. + +Dual-registration mode is intended for interworking between EPS/E-UTRAN and 5GS/NR. A dual-registered UE should not send its E-UTRA connected to 5GC and E-UTRAN radio capabilities to NR access when connected to 5GS/NR to avoid being handed over to 5GC-connected E-UTRA or to E-UTRAN. + +NOTE 1: This is to prevent the dual registered UE from being connected to the same E-UTRA cell either connected to EPC or 5GC simultaneously using separate RRC connections via single RAN node as a result of handover. If a dual-registered UE implementation chooses to send its E-UTRA capability when connected to 5GS/NR, the UE and the network behaviour when UE enters a 5GC-connected E-UTRA is not further specified. If however the UE is registered with 5GS/NR only, the UE can send its E-UTRA capability in order to allow inter-RAT handover to E-UTRA/5GC and Dual Connectivity with multiple RATs. + +If a dual-registered UE had not sent its E-UTRA connected to 5GC and E-UTRAN radio capabilities to 5GS and the UE needs to initiate emergency services, it shall locally re-enable its E-UTRA connected to 5GC and E-UTRAN radio capabilities in order to perform domain selection for emergency services as defined in TS 23.167 [18]. + +NOTE 2: However even in this case, the UE is still not expected to connect to E-UTRAN/EPC and E-UTRA/5GC simultaneously using separate RRC connection via single RAN node as a result of the domain selection for emergency services. + +The support of single registration mode is mandatory for UEs that support both 5GC and EPC NAS. + +During E-UTRAN Initial Attach, UE supporting both 5GC and EPC NAS shall indicate its support of 5G NAS in UE Network Capability described in clause 4.11.1.5.2 of TS 23.502 [3]. + +During registration to 5GC, UE supporting both 5GC and EPC NAS shall indicate its support of EPC NAS. + +NOTE 3: This indication may be used to give the priority towards selection of SMF+PGW-C for UEs that support both EPC and 5GC NAS. + +If the UE supports 5GC NAS, at PDN connection establishment in EPC, the UE may allocate a PDU Session ID and sends it via PCO, regardless of N1 mode status (i.e. enabled or disabled) in the UE. + +NOTE 4: UE providing a PDU Session ID at PDN connection establishment even when N1 mode is disabled allows for IP address preservation during EPC to 5GC mobility once the UE re-enables N1 mode. + +NOTE 5: For the case the MME has selected a standalone PGW for a PDN connection, if the UE re-enables N1 mode and reports the change in UE Network Capability, the MME can initiate PDN disconnection with reactivation required as described in clause 4.11.0a.8 of TS 23.502 [3] to allow selection of SMF+PGW-C thus session continuity at EPC to 5GC mobility. + +If the EPC supports "Ethernet" PDU Session Type, and the 5GSM Capabilities indicate that the UE supports Ethernet PDN type in EPC, then PDU Session type "Ethernet" is transferred to EPC as "Ethernet". Otherwise, PDU Session types "Ethernet" and "Unstructured" are transferred to EPC as "non-IP" PDN type (when supported by UE and network). If the UE or EPC does not support Ethernet PDN type in EPC, the UE sets the PDN type to non-IP when it moves from 5GS to EPS and after the transfer to EPS, and the UE and the SMF shall maintain information about the PDU Session type used in 5GS, i.e. information indicating that the PDN Connection with "non-IP" PDN type corresponds to PDU Session type Ethernet or Unstructured respectively. This is done to ensure that the appropriate PDU Session type will be used if the UE transfers to 5GS. + +PDN type "non-IP" is transferred to 5GS as "Unstructured" PDU Session type if it is successfully transferred. + +It is assumed that if a UE supports Ethernet PDU Session type and/or Unstructured PDU Session type in 5GS it will also support non-IP PDN type in EPS. If this is not the case, the UE shall locally delete any EBI(s) corresponding to the Ethernet/Unstructured PDU Session(s) to avoid that the Ethernet/Unstructured PDU Session(s) are transferred to EPS. + +MTU size consideration for PDU Sessions and PDN Connections towards a SMF+PGW-C follows the requirements in clause 5.6.10.4. + +Networks that support interworking with EPC, may support interworking procedures that use the N26 interface or interworking procedures that do not use the N26 interface. Interworking procedures with N26 support provides IP address continuity on inter-system mobility to UEs that support 5GC NAS and EPC NAS and that operate in single registration mode. Networks that support interworking procedures without N26 shall support procedures to provide IP address continuity on inter-system mobility to UEs operating in both single-registration mode and dual-registration mode. In such networks, AMF shall provide the indication that interworking without N26 is supported to UEs during initial Registration in 5GC or MME may optionally provide the indication that interworking without N26 is supported in the Attach procedure in EPC as defined in TS 23.401 [26]. + +If the network does not support interworking with EPC, network shall not indicate support for "interworking without N26" to the UE. + +When the HSS+UDM is required to provide the subscription data to the MME, for each APN, only one SMF+PGW-C FQDN and associated APN is provided to the MME according to TS 23.401 [26]. + +For interworking without N26 interface: + +- if the PDU session supports interworking, the SMF+PGW-C stores the SMF+PGW-C FQDN to SMF context in HSS+UDM when the SMF is registered to HSS+UDM. +- For an APN, the HSS+UDM selects one of the stored SMF+PGW-C FQDN based on operator's policy. + +For interworking with N26 interface: + +- For a DNN, AMF determines PDU session(s) associated with 3GPP access in only one SMF+PGW-C supporting EPS interworking via EBI allocation procedure as described in clause 4.11.1.4.1 of TS 23.502 [3]. +- If the network supports EPS interworking of non-3GPP access connected to 5GC, the AMF serving 3GPP access notifies the UDM to store the association between DNN and SMF+PGW-C FQDN which supports EPS interworking as Intersystem continuity context, to avoid MME receiving inconsistent SMF+PGW-C FQDN from AMF and HSS+UDM. +- The AMF updates Intersystem continuity context if the SMF+PGW-C and DNN association is changed due to the AMF selecting another SMF+PGW-C for EPS interworking for the same DNN. +- If the SMF+PGW-C FQDN and associated DNN exists in Intersystem continuity context, the HSS+UDM provides MME with SMF+PGW-C FQDN and associated APN. + +It does not assume that the HSS+UDM is aware of whether N26 is deployed in the serving network. The HSS+UDM check the Intersystem continuity context first. If no SMF+PGW-C FQDN associated with an DNN exists in Intersystem continuity context, the HSS+UDM selects one of the SMF+PGW-C FQDN for the APN from SMF context based on operator's policy. + +In entire clause 5.17.2 the terms "initial attach", "handover attach" and "TAU" for the UE procedures in EPC can alternatively be combined EPS/IMSI Attach and combined TA/LA depending on the UE configuration defined in TS 23.221 [23]. + +If a UE in MICO mode moves to E-UTRAN connected to EPC and any of the triggers defined in clause 5.4.1.3 occur, then the UE shall locally disable MICO mode and perform the TAU or Attach procedure as defined in clause 5.17.2. The UE can renegotiate MICO when it returns to 5GS during (re-)registration procedure. + +IP address preservation for IP PDU sessions cannot be ensured on subsequent mobility from EPC/E-UTRAN to GERAN/UTRAN to a UE that had initially registered in 5GS and moved to EPC/E-UTRAN. + +NOTE 6: The SMF+PGW-C might not include the GERAN/UTRAN PDP Context anchor functionality. Also, 5GC does not provide GERAN/UTRAN PDP Context parameters to the UE when QoS Flows of PDU Session are setup or modified in 5GS. Hence, the UE might not be able to activate the PDP contexts when it transitions to GERAN/UTRAN. + +IP address preservation for IP PDU sessions cannot be ensured on subsequent mobility from EPC/E-UTRAN to 5GS for a 5GS NAS capable UE that had initially established a PDP context via GERAN/UTRAN and moved to EPC/E-UTRAN. IP address preservation for IP PDU session mobility between EPC/E-UTRAN and 5GS may be re-ensured as specified in clause 5.17.2.4 when UE moves from GERAN/UTRAN into EPC/E-UTRAN. + +NOTE 7: The PGW acting as a GGSN might not support SMF+PGW-C functionality. GPRS does not support 5GS parameters transfer between UE and SMF+PGW-C (e.g. providing of PDU session ID and 5GS QoS information). + +When a PDU session is moved from 5GS to EPS, the SMF+PGW-C keeps the registration and subscription in HSS+UDM until the corresponding PDN connection is released. + +The SMF+PGW-C receives notification of subscription update regarding the 5G parameters (e.g. DNNs, S-NSSAIs) which are associated with the established PDN connection(s) connecting via EPS. If the subscription regarding DNN, QoS profile or PDN connection type associated with the PDN connection is updated, then the MME receives the subscription update and triggers corresponding actions according to TS 23.401 [26]. If the SMF+PGW-C receives subscription updates (e.g. change of 5GS Subscribed NSSAI) from the UDM the SMF+PGW-C triggers corresponding actions for the PDN connection. This may include (depending on the modified parameter) to: + +- update the UPF (e.g. for a change of Framed Route information); or +- release the PDN connection with an appropriate cause (e.g. for change of EPS/5GS interworking support, for subscription removal of S-NSSAI associated with the PDN connection); +- do nothing about changes to DNN and/or PDU Session type that are handled by the MME. + +If header compression is used for Control Plane CIoT EPS/5GS Optimisations and when the UE moves from EPS to 5GS or from 5GS to EPS, the UE may initiate the PDU Session Modification Procedure or UE requested bearer resource modification procedure to renegotiate the header compression configuration and to establish the compression context between the UE and MME/SMF, see TS 23.401 [26] and TS 24.501 [47]. + +If the UE is moving from 5GS to EPS and the RAT type is also moving from a "broadband" RAT (e.g. NR or WB-E-UTRA) to NB-IoT in EMM-IDLE state, the UE should set the mapped EPS bearer context for which the EPS bearer is a dedicated EPS bearer to state BEARER CONTEXT INACTIVE as for NB-IoT UEs in EPS only support the default bearers. In addition, UE shall locally deactivate the related bearers according to the maximum number of supported UP resources and send the latest bearer context status in the TAU Request. + +If APN Rate Control is used when the UE moves from EPC to 5GC then the P-GW/SCEF and UE store the current APN Rate Control Status for an APN. If while connected to 5GC the last PDU Session to a DNN that is the same as the APN identified in the APN Rate Control Status is released then the APN Rate Control Status may be stored in the AMF in addition to the Small Data Rate Control Status and the UE discards the APN Rate Control Status. The APN Rate Control Status is stored in the AMF so it can be provided to the MME during mobility to EPC and subsequently applied at establishment of a new first PDN Connection to the same APN, if valid. The APN Rate Control Status is provided to the UPF+PGW-U if a first new PDU Session is established towards the DNN that is the same as the APN identified in the APN Rate Control Status if the UE moves back to EPC, taking into account its validity period. + +The UE may be provided with initial APN Rate Control parameters by the SMF when a first new PDU Session is established for a DNN and S-NSSAI that supports interworking with EPS and the DNN matches an APN. The SMF provides the APN Rate Control Status for the APN that matches the DNN, if available at the SMF, otherwise the configured APN Rate Control parameters for the APN that matches the DNN are provided as the initially applied parameters. If the initially applied parameters differ from the configured APN Rate Control parameters and the first + +APN Rate Control validity period expires, the UE is updated with the configured APN Rate Control parameters once the UE has moved to EPC. + +NOTE 8: If the APN Rate Control Status is provided to a UPF+PGW-U it is not used for Small Data Rate Control while the UE is connected to 5GC, it is only used as the APN Rate Control Status if the UE moves to EPC. + +NOTE 9: Encoding of APN and DNN specified in TS 23.003 [19] allows the comparison of EPS APN and 5GS DNN. + +If a Service Gap timer is running in the AMF when the UE moves from 5GC to EPC, the AMF stops the running Service Gap timer. If the UE returns to 5GC from EPC the AMF provides the Service Gap Time to the UE as described in clause 5.31.16. + +If a Service Gap timer is running in the MME when the UE moves from EPC to 5GC, the MME stops the running Service Gap timer. If the UE returns to E-UTRAN connected to EPC from 5GC the MME provides the Service Gap Time to the UE as described in TS 23.401 [26]. + +If a Service Gap timer is running in the UE when the UE moves from 5GC to EPC and if Service Gap Time is received from the MME, the UE stores the received Service Gap Time for later use when the timer needs to be started next time, and the Service Gap timer that was started before the system change is kept running in the UE and applied for EPC. If a Service Gap timer is running in the UE when the UE moves to 5GC and if Service Gap Time is received from the AMF, the UE stores the received Service Gap Time for later use when the timer needs to be started next time, and the Service Gap timer that was started before the system change is kept running in the UE and applied in 5GS. + +For UE currently served by EPC, a SMF+PGW-C may support L2TP tunnelling on N6, as described in clause 5.8.2.16. + +#### 5.17.2.2 Interworking Procedures with N26 interface + +##### 5.17.2.2.1 General + +NOTE 1: Additional network slicing and Interworking with EPS with N26 aspects are specified in clause 5.15.7. + +Interworking procedures using the N26 interface, enables the exchange of MM and SM states between the source and target network. The N26 interface may be either intra-PLMN or inter-PLMN (e.g. to enable inter-PLMN mobility). When interworking procedures with N26 is used, the UE operates in single-registration mode. For the 3GPP access, the network keeps only one valid MM state for the UE, either in the AMF or MME. For the 3GPP access, either the AMF or the MME is registered in the HSS+UDM. + +The support for N26 interface between AMF in 5GC and MME in EPC is required to enable seamless session continuity (e.g. for voice services) for inter-system change. + +The UE's subscription may include restriction for Core Network Type (EPC) and RAT restriction for E-UTRA. If so, the UDM provides these restrictions to the AMF. The AMF includes RAT and Core Network type restrictions in the Handover Restriction List to the NR. The AMF and NR use these restrictions to determine if mobility of the UE to EPS or E-UTRA connected to EPS should be permitted. When the UE moves from 5GS to EPS, the SMF determines which PDU Sessions can be relocated to the target EPS, e.g. based on capability of the deployed EPS, operator policies for which PDU Session, seamless session continuity should be supported etc. The SMF can release the PDU Sessions that cannot be transferred as part of the handover or Idle mode mobility. However, whether the PDU Session is successfully moved to the target network is determined by target EPS. + +Similarly, the UE's subscription may include restriction for Core Network Type (5GC) and RAT restriction for NR. If so, the HSS provides these restrictions to the MME. The MME includes RAT and Core Network type restrictions in the Handover Restriction List to the E-UTRAN. The MME and E-UTRAN use these restrictions to determine if mobility of the UE to 5GS or NR connected to 5GS should be permitted. If the SMF+PGW-C receives the PDU session ID from UE via PCO and know 5GC is not restricted for the PDN connection by user subscription, the SMF+PGW-C sends the mapped QoS parameters to UE. When the UE moves from EPS to 5GS, for the case when the MME has selected SMF+PGW-C even for PDN connections that cannot be relocated to the target 5GS, the SMF+PGW-C determines which PDN Connections can be relocated to the target 5GS, e.g. based on capability of the deployed 5GS, subscription and operator policies for which PDN Connection, seamless session continuity should be supported etc. The SMF+PGW-C and NG-RAN can reject the PDN Connections that cannot be transferred as part of the handover or Idle mode mobility. + +For the case when the MME has selected standalone P-GW for a PDN connection for which session continuity is not supported and the AMF cannot retrieve the address of the corresponding SMF during EPS to 5GS mobility, the AMF does not move the PDN connection to 5GS. + +NOTE 2: When applying the AMF planned removal procedure or the procedure to handle AMF failures (see clause 5.21.2) implementations are expected to update the DNS configuration to enable MMEs to discover alternative AMFs if the MME tries to retrieve a UE context from an AMF that has been taken out of service or has failed. This addresses the scenario of UEs performing 5GS to EPS Idle mode mobility and presenting a mapped GUTI pointing to an AMF that has been taken out of service or has failed. + +In the case of mobility from 5GS to EPS, if the MME lacks certain capability, e.g. MME not supporting 15 EPS bearers, the 5GC shall not transfer the UE EPS bearers and/or EPS PDN connections that are not supported by the EPC network. If the MME does not support 15 EPS bearers, the AMF determines which EBIs cannot be transferred to EPS, and retrieves the EPS bearer contexts from the SMF+PGW-C for the EBIs that can be transferred to EPS. + +NOTE 3: How the AMF determines which EBIs can be transferred to EPS is according to local configuration, e.g. according to DNN, S-NSSAI, ARP associated with an EBI. + +In the case of mobility from 5GS to EPS, if the mobility is a result of the PCF modifying the RFSP Index value for the UE to indicate that EPC/E-UTRAN access is prioritized over the 5GS access, the AMF may be sent with a RFSP in Use Validity Time by the PCF as specified in TS 23.503 [45]. If the AMF receives RFSP in Use Validity Time and selects the RFSP Index in use identical to the authorized RFSP Index as specified in clause 5.3.4.3, then the AMF provides the MME with the RFSP Index in use and the RFSP in Use Validity Time, which indicates the time by which the RFSP Index in use will be used in the MME as specified in clause 4.11.1.5.8 of TS 23.502 [3]. + +NOTE 4: The RFSP in Use Validity Time is to allow the UE to stay in EPS for a period of time to avoid the potential ping-pong issue (i.e. 5GS keeps sending the UE to EPS based on authorized RFSP Index from PCF, and the EPS keeps sending the UE back to 5GS immediately based on the subscribed RFSP Index). + +NOTE 5: The RFSP in Use Validity Time applies only to EPS but not to 5GS, therefore in the case of mobility from EPS to 5GS, the RFSP in Use Validity Time if received from MME is ignored by the AMF. + +##### 5.17.2.2.2 Mobility for UEs in single-registration mode + +When the UE supports single-registration mode and network supports interworking procedure with the N26 interface: + +- For idle mode mobility from 5GS to EPS, the UE performs either TAU or Attach procedure with EPS GUTI mapped from 5G-GUTI sent as old Native GUTI, as described in clause 4.11.1.3.2.1 of TS 23.502 [3] and indicates that it is moving from 5GC. The UE includes in the RRC message a GUMMEI mapped from the 5G-GUTI and indicates it as a native GUMMEI and should in addition indicate it as "Mapped from 5G-GUTI". The MME retrieves the UE's MM and SM context from 5GC. For connected mode mobility from 5GS to EPS, either inter-system handover or RRC Connection Release with Redirection to E-UTRAN is performed. At inter-system handover, the AMF selects target MME based on 2 octet TAC format used in the Target ID as specified in TS 38.413 [34]. During the TAU or Attach procedure the HSS+UDM cancels any AMF registration associated with the 3GPP access (but not AMF registration associated with the non-3GPP access); an AMF that was serving the UE over both 3GPP and non-3GPP accesses does not consider the UE as deregistered over non 3GPP access. +- For the first TAU after 5GC initial Registration, the UE and MME for the handling of UE Radio Capabilities follow the procedures as defined in clause 5.11.2 of TS 23.401 [26] for first TAU after GERAN/UTRAN Attach. + +NOTE 1: MMEs supporting interworking with N26 interface are not required to process the indication from the UE that it is moving from 5GC and will assume that the UE is moving from another MME. + +- For idle mode mobility from EPC to 5GC, the UE performs mobility Registration procedure with the 5G GUTI mapped from EPS GUTI and indicates that it is moving from EPC. The UE derives GUAMI from the native 5G-GUTI and includes GUAMI in the RRC message to enable RAN to route to the corresponding AMF (if available). If the UE holds no native 5G-GUTI, then the UE provides in the RRC message a GUAMI mapped from the EPS GUTI and indicates it as "Mapped from EPS". The AMF and SMF retrieve the UE's MM and SM context from EPC. For connected mode mobility from EPC to 5GC, either inter-system handover or RRC Connection Release with Redirection to NG-RAN is performed. At inter-system handover, the MME selects target AMF based on TAC used in the Target ID as specified in TS 38.413 [34]. During the Registration procedure, the HSS+UDM cancels any MME registration. + +NOTE 2: During a transition period, the source eNB may be configured via O&M to know that the MME is not upgraded and thus supports only 2 octet TAC. The Target ID for the NG-RAN node is set as "Target eNB ID" in the existing IEs as defined in TS 38.413 [34]. + +For both idle mode and connected mode mobility from EPC to 5GC: + +- The UE includes the native 5G-GUTI as an additional GUTI in the Registration request; the AMF uses the native 5G-GUTI to retrieve MM context identified by the 5G-GUTI from old AMF or from UDSF (if UDSF is deployed and the old AMF is within the same AMF set). +- If this is the first mobility event for a PDU Session that was established while being connected to EPC, the UE shall trigger the PDU Session Modification procedure and: + - should indicate the support of Reflective QoS to the network (i.e. SMF) if the UE supports Reflective QoS functionality. If the UE indicated support of Reflective QoS, the network may provide a Reflective QoS Timer (RQ Timer) value to the UE; + - shall indicate the number of supported packet filters for signalled QoS rules, if the UE supports more than 16 packet filters for the PDU Session. The network shall store this information so that subsequent mobility events do not require another signalling of it. + - should indicate the support of Multi-homed IPv6 PDU session to the network (i.e. SMF) if the UE supports Multi-homed IPv6 PDU session. If the UE indicated support of Multi-homed IPv6 PDU session, the network shall consider that this PDU session is supported to use multiple IPv6 prefixes. + - should provide the UE Integrity Protection Maximum Data Rate to the network (i.e. SMF). The network shall consider that the maximum data rate per UE for user-plane integrity protection supported by the UE is valid for the lifetime of the PDU session. + +#### 5.17.2.3 Interworking Procedures without N26 interface + +##### 5.17.2.3.1 General + +For interworking without the N26 interface, IP address preservation is provided to the UEs on inter-system mobility by storing and fetching SMF+PGW-C and corresponding APN/DNN information via the HSS+UDM. In such networks AMF also provides an indication that interworking without N26 is supported to UEs during Initial Registration in 5GC or MME may optionally provide an indication that interworking without N26 is supported in the Attach procedure in EPC as defined in TS 23.502 [3] and TS 23.401 [26]. The UE provides an indication that it supports Request Type flag "handover" for PDN connectivity request during the attach procedure as described in clause 5.3.2.1 of TS 23.401 [26] and during initial Registration and Mobility Registration Update in 5GC. + +NOTE 1: The UE support of Request Type flag "handover" for PDN connectivity request during the attach procedure is needed for IP address preservation in the case of interworking without N26. + +The indication that interworking without N26 is valid for the entire Registered PLMN and for PLMNs equivalent to the Registered PLMN that are available in the Registration Area. The same indication is provided to all UEs served by the same PLMN. UEs that operate in interworking without N26 may use this indication to decide whether to register early in the target system. UEs that only support single registration mode may use this indication as described in clause 5.17.2.3.2. UE that support dual registration mode uses this indication as described in clause 5.17.2.3.3. + +Interworking procedures without N26 interface use the following two features: + +1. When UE performs Initial Attach in EPC (with or without "Handover" indication in PDN CONNECTIVITY Request message) and indicates that it is moving from 5GC, the MME indicates to the HSS+UDM not to cancel the registration of AMF, if any. +2. When UE performs Initial Registration in 5GC and indicates that it is moving from EPC, the AMF indicates to the HSS+UDM not to cancel the registration of MME, if any. + +To support mobility both for single and dual registration mode UEs, the following also are supported by the network: + +3. When PDU Session are created in 5GC, the SMF+PGW-C which supports EPS interworking stores the SMF+PGW-C FQDN along with DNN in the HSS+UDM. + +4. The HSS+UDM provides the information about dynamically allocated SMF+PGW-C and APN/DNN information to the target CN network. If there are multiple SMF+PGW-C serving the UE for the same DNN which support EPS interworking in 5GS, the HSS+UDM select one of them according to operator's policy and provides together with the associated APN to the MME. +5. When PDN connections are created in EPC, the MME stores the SMF+PGW-C and APN information in the HSS+UDM. + +NOTE 2: Items 3, 4 and 5 are also supported in networks that support interworking with N26 procedures. This enables a VPLMN that does not deploy N26 interface to provide IP address preservation to roamed-in single-registration mode UEs from a HPLMN that only supports interworking with N26 procedures. + +When the network serving the UE supports 5GS-EPS interworking procedures without N26 interface, the SMF shall not provide the UEs with mapped target system parameters of the target system when UE is in the source network. + +A UE that operates in dual registration mode ignores any received mapped target system parameters (e.g. QoS parameters, bearer IDs/QFI, PDU Session ID, etc.). + +##### 5.17.2.3.2 Mobility for UEs in single-registration mode + +When the UE supports single-registration mode and network supports interworking procedure without N26 interface: + +- For mobility from 5GC to EPC, the UE with at least one PDU Session established in 5GC may either: + - if supported and if it has received the network indication that interworking without N26 is supported, perform Attach in EPC with a native EPS GUTI, if available, otherwise with IMSI with Request type "Handover" in PDN CONNECTIVITY Request message (clause 5.3.2.1 of TS 23.401 [26]) and indicating that the UE is moving from 5GC and subsequently moves all its other PDU Session using the UE requested PDN connectivity establishment procedure with Request Type "handover" flag (clause 5.10.2 of TS 23.401 [26]), or. + - perform TAU with 4G-GUTI mapped from 5G-GUTI sent as old Native GUTI (clause 5.3.3 of TS 23.401 [26]) indicating that it is moving from 5GC, in which case the MME instructs the UE to re-attach. IP address preservation is not provided in this case. + - for the first TAU after 5GC initial Registration, the UE and MME for the handling of UE Radio Capabilities follow the procedures as defined in clause 5.11.2 TS 23.401 [26] for first TAU after GERAN/UTRAN Attach. + +NOTE 1: The first PDN connection may be established during the E-UTRAN Initial Attach procedure (see TS 23.401 [26]). + +NOTE 2: At inter-PLMN mobility to a PLMN that is not an equivalent PLMN the UE always uses the TAU procedure. + +- For mobility from 5GC to EPC, the UE with no PDU Session established in 5GC + - performs Attach in EPC (clause 5.3.2.1 of TS 23.401 [26]) indicating that the UE is moving from 5GC. +- For mobility from EPC to 5GC, the UE performs Mobility Registration Update in 5GC with 5G-GUTI mapped from EPS GUTI and a native 5G-GUTI, if available, as Additional GUTI and indicating that the UE is moving from EPC. In this case, the AMF determines that old node is an MME, but proceeds as if the Registration is of type "initial registration". The UE may either: + - if supported and if it has received the network indication "interworking without N26 supported", move all its PDN connections from EPC using the UE initiated PDU Session Establishment procedure with "Existing PDU Sessions" flag (clause 4.3.2.2.1 of TS 23.502 [3]), or + - re-establish PDU Sessions corresponding to the PDN connections that it had in EPS. IP address preservation is not provided in this case. + +NOTE 3: The additional native 5G-GUTI enables the AMF to find the UE's 5G security context (if available). + +NOTE 4: When single-registration mode UE uses interworking procedures without N26, the registration states during the transition period (e.g. while UE is transferring all PDU Sessions / PDN Connections on the target side) are defined in Stage 3 specifications. + +- If the network determines that the UE is changing RAT type, if the UE requests to relocate the PDU session from EPC to 5GC or 5GC to EPC, the SMF/MME uses the "PDU session continuity at inter RAT mobility" or "PDN continuity at inter-RAT mobility" information, respectively, in the subscription to determine whether to maintain the PDU session/PDN connection (if being handed over) or reject the PDU session request, with the relevant cause. +- If the UE requested to move the PDU session and the "PDN continuity at inter RAT mobility" information indicated "disconnect the PDN connection with a reactivation request" the network should provide a suitable cause code to the UE so that it can request a new PDU session. + +##### 5.17.2.3.3 Mobility for UEs in dual-registration mode + +To support mobility in dual-registration mode, the support of N26 interface between AMF in 5GC and MME in EPC is not required. A UE that supports dual registration mode may operate in this mode when it receives an indication from the network that interworking without N26 is supported. + +For UE operating in dual-registration mode the following principles apply for PDU Session transfer from 5GC to EPC: + +- UE operating in Dual Registration mode may register in EPC ahead of any PDU Session transfer using the Attach procedure indicating that the UE is moving from 5GC without establishing a PDN Connection in EPC if the EPC supports EPS Attach without PDN Connectivity as defined in TS 23.401 [26]. Support for EPS Attach without PDN Connectivity is mandatory for UE supporting dual-registration procedures. + +NOTE 1: Before attempting early registration in EPC the UE needs to check whether EPC supports EPS Attach without PDN Connectivity by reading the related SIB in the target cell. + +- UE performs PDU Session transfer from 5GC to EPC using the UE initiated PDN connection establishment procedure with "handover" indication in the PDN Connection Request message (clause 5.10.2 of TS 23.401 [26]). +- If the UE has not registered with EPC ahead of the PDU Session transfer, the UE can perform Attach in EPC with "handover" indication in the PDN Connection Request message (clause 5.3.2.1 of TS 23.401 [26]). +- UE may selectively transfer certain PDU Sessions to EPC, while keeping other PDU Sessions in 5GC. +- UE may maintain the registration up to date in both 5GC and EPC by re-registering periodically in both systems. If the registration in either 5GC or EPC times out (e.g. upon mobile reachable timer expiry), the corresponding network starts an implicit detach timer. + +NOTE 2: Whether UE transfers some or all PDU Sessions on the EPC side and whether it maintains the registration up to date in both EPC and 5GC can depend on UE capabilities that are implementation dependent. The information for determining which PDU Sessions are transferred on EPC side and the triggers can be pre-configured in the UE and are not specified in this Release of the specification. The UE does not know before-hand, i.e. before trying to move a given PDU session to EPC, whether that PDU session can be transferred to EPC. + +NOTE 3: The Start of Unavailability Period and/or Unavailability Period Duration that the UE determines for NR satellite access with discontinuous network coverage in 5GS (see clause 5.4.1.4) and determines for satellite access with discontinuous coverage in EPS (see clause 4.13.8.2 of TS 23.401 [26]) can be different between 5GS and EPS. + +For UE operating in dual-registration mode the following principles apply for PDN connection transfer from EPC to 5GC: + +- UE operating in Dual Registration mode may register in 5GC ahead of any PDN connection transfer using the Registration procedure indicating that the UE is moving from EPC (clause 4.2.2.2.2 of TS 23.502 [3]). +- UE performs PDN connection transfer from EPC to 5GC using the UE initiated PDU Session Establishment procedure with "Existing PDU Session" indication (clause 4.3.2.2.1 of TS 23.502 [3]). +- UE may selectively transfer certain PDN connections to 5GC, while keeping other PDN Connections in EPC. + +- UE may maintain the registration up to date in both EPC and 5GC by re-registering periodically in both systems. If the registration in either EPC or 5GC times out (e.g. upon mobile reachable timer expiry), the corresponding network starts an implicit detach timer. + +NOTE 4: Whether UE transfers some or all PDN connections on the 5GC side and whether it maintains the registration up to date in both 5GC and EPC can depend on UE capabilities that are implementation dependent. The information for determining which PDN connections are transferred on 5GC side and the triggers can be pre-configured in the UE and are not specified in this Release of the specification. The UE does not know before-hand, i.e. before trying to move a given PDN connection to 5GC, whether that PDN connection can be transferred to 5GC. + +NOTE 5: If EPC does not support EPS Attach without PDN Connectivity the MME detaches the UE when the last PDN connection is released by the PGW as described in clause 5.4.4.1 of TS 23.401 [26] (in relation to transfer of the last PDN connection to non-3GPP access). + +When sending a control plane request for MT services (e.g. MT SMS) the network routes it via either the EPC or the 5GC. In absence of UE response, the network should attempt routing the control plane request via the other system. + +NOTE 6: The choice of the system through which the network attempts to deliver the control plane request first is left to network configuration. + +##### 5.17.2.3.4 Redirection for UEs in connected state + +When the UE supports single-registration mode or dual-registration mode without N26 interface: + +- If the UE is in CM-CONNECTED state in 5GC, the NG-RAN may perform RRC Connection Release with Redirection to E-UTRAN based on certain criteria (e.g. based on local configuration in NG-RAN, or triggered by the AMF upon receiving Handover Request message from NG-RAN). +- If the UE is in ECM-CONNECTED state in EPC, the E-UTRAN may perform RRC Connection release with redirection to NG-RAN based on certain criteria (e.g. based on local configuration in E-UTRAN, or triggered by the MME upon receiving handover request from E-UTRAN). + +#### 5.17.2.4 Mobility between 5GS and GERAN/UTRAN + +IP address preservation upon direct mobility between 5GS and GERAN/UTRAN is not supported. + +Upon mobility from 5GS to GERAN/UTRAN (e.g. upon leaving NG-RAN coverage) the UE shall perform the A/Gb mode GPRS Attach procedure or Iu mode GPRS Attach procedure (see TS 23.060 [56]). + +As a UE option, to support IP address preservation at mobility from EPC to 5GS for PDN connections without 5GS related parameters, a 5GS capable UE may: + +- Following mobility from GERAN/UTRAN to EPS, release those PDN connection(s) and re-establish them as specified in clause 4.11.1.5.4.1 of TS 23.502 [3] so that they support interworking to 5GS. + +NOTE 1: It is recommended that a UE using this option does not do this behaviour after every change to EPS in PLMNs that do not support 5GS, nor for APNs that do not support mobility to 5GS; and, that such a UE supports storage of the 5GS related parameters while in GERAN/UTRAN. Whether and how the UE is aware of which PLMNs support 5GS and which APNs do not support mobility to 5GS is out of scope of this specification. + +To support mobility from EPC to 5GS to EPC to GERAN/UTRAN for PDN connections established in EPC: + +NOTE 2: For the use of N7 or N40 interfaces while the UE is in GERAN/UTRAN access, the SMF+PGW-C selected by the MME (using the existing selection procedures described in clause 4.11.0a of TS 23.502 [3] and clause 4.3.8 of TS 23.401 [26]) needs to support functionality (e.g. signalling of GERAN/UTRAN cell identification over N7) specified in Annex L. + +- in signalling sent on the N26 interface, the MME should send the TI and BSS Container in the EPS Bearer Context (see Table 7.3.1-3 of TS 29.274 [101]), if there is any, of the EPS bearer to the SMF (V-SMF / I-SMF) via the AMF in the Bearer Context within the PDN Connection IE in the Forward Relocation Request and Context Response messages (TS 29.274 [101]); the SMF (V-SMF / I-SMF) should store the TI and BSS Container and the SMF (V-SMF / I-SMF) should provide the TI and BSS Container to the AMF (as part of a + +procedure to deliver SM context to AMF) so that the AMF sends the TI and BSS Container of the related EPS bearer in the Bearer Context within the EPS PDN Connection information in any subsequent Forward Relocation Request and Context Response message sent to an MME. + +NOTE 3: At mobility from EPC, the SMF+PGW-C / V-SMF / I-SMF receives the TI and BSS Container as part of the UE EPS PDN Connection information from the AMF and stores the TI. At mobility to EPC, the SMF+PGW-C / V-SMF / I-SMF provides the AMF with the TI and BSS Container as part of the UE EPS PDN Connection information. The SMF+PGW-C / V-SMF / I-SMF is not meant to understand the TI/BSS Container nor to use it for any other purpose than providing it back to AMF. + +NOTE 4: GERAN/UTRAN Mobility Management Bearer Synchronisation procedures will release any dedicated QoS Flows established in 5GS. + +NOTE 5: When the UE access the network via GERAN/UTRAN over Gn/Gp interface, Secondary PDP Context Activation Procedure is not supported. + +IP address preservation at mobility from EPC to GERAN/UTRAN for PDU sessions established in 5GS is not supported. + +With regard to interworking between 5GS and the Circuit Switched domain when the GERAN or UTRAN network is operating in NMO II (i.e. no Gs interface between MSC and SGSN): + +- upon mobility from 5GS to GERAN/UTRAN, the UE shall either: + - act as if it is returning after a loss of GERAN/UTRAN coverage (and e.g. only perform a periodic LAU if the periodic LAU timer has expired), or, + - perform a Location Update to the MSC. If the UE is registered for IMS voice and is configured, using Device Management or initial provisioning, to perform additional mobility management procedures when it has moved from a RAT that supports IMS voice over PS sessions to one that does not (see TS 23.060 [56]), it shall follow this option. + +Upon mobility from GERAN/UTRAN to 5GS (e.g. upon selecting an NG-RAN cell) the UE shall perform the Registration procedure of "initial registration" type as described in TS 23.502 [3]. The UE shall indicate a 5G-GUTI as UE identity in the Registration procedure if it has a stored valid native 5G-GUTI (e.g. from an earlier registration in the 5G System). Otherwise the UE shall indicate a SUCI. + +If a UE in MICO mode moves to GERAN/UTRAN and any of the triggers defined in clause 5.4.1.3 occur, then the UE shall locally disable MICO mode and perform the A/Gb mode GPRS Attach procedure or Iu mode GPRS Attach procedure (see TS 23.060 [56]). The UE can renegotiate MICO when it returns to 5GS during (re-)registration procedure. + +In Single Registration mode, expiry of the periodic RAU timer, or, the periodic LAU timer shall not cause the UE to change RAT. + +The 5G SRVCC from NG-RAN to UTRAN is specified in the TS 23.216 [88]. After the 5G SRVCC to UTRAN, all the PDU sessions of the UE are released. + +#### 5.17.2.5 Secondary DN authentication and authorization in EPS Interworking case + +Secondary authentication/authorization by a DN-AAA server during the establishment of a PDN connection over 3GPP access to EPC, is supported based on following principles: + +- It is optional for the UE to support EAP-based secondary authentication and authorization by DN-AAA over EPC, +- A SMF+PGW-C shall be used to serve DNN(s) requiring secondary authentication/authorization by a DN-AAA server, +- For secondary authentication/authorization by a DN-AAA server, the SMF+PGW-C runs the same procedures with PCF, UDM and DN-AAA and uses the same corresponding interfaces regardless of whether the UE is served by EPS or 5GS, +- The interface towards the UE is different (usage of NAS for EPS instead of NAS for 5GS) between the EPS and 5GS cases. + +This is further specified in Annex H of TS 23.502 [3]. + +In this Release, EAP based Secondary authentication by a DN-AAA server during the establishment of a PDN connection over non-3GPP access to EPC is not supported. + +### 5.17.3 Interworking with EPC in presence of Non-3GPP PDU Sessions + +When a UE is simultaneously connected to the 5GC over a 3GPP access and a non-3GPP access, it may have PDU Sessions associated with 3GPP access and PDU Sessions associated with non-3GPP access. When inter-system handover from 5GS to EPS is performed for PDU Sessions associated with 3GPP access, the PDU Sessions associated with non-3GPP access are kept anchored by the network in 5GC and the UE may either: + +- keep PDU Sessions associated with non-3GPP access in 5GS (5GC+N3IWF or TNGF) (i.e. the UE is then registered both in EPS and, for non-3GPP access, in 5GS); or +- locally or explicitly release PDU Sessions associated with non-3GPP access; or +- once in EPS, transfer PDU Sessions associated with non-3GPP access to E-UTRAN by triggering PDN connection establishment with Request Type "Handover", as specified in TS 23.401 [26]. + +### 5.17.4 Network sharing support and interworking between EPS and 5GS + +The detailed description for supporting network sharing and interworking between EPS and 5GS is described in clauses 4.11.1.2.1, 4.11.1.2.2, 4.11.1.3.2 and 4.11.1.3.3 of TS 23.502 [3]. + +### 5.17.5 Service Exposure in Interworking Scenarios + +#### 5.17.5.1 General + +Clause 4.3.5 shows the Service Exposure Network Architecture in scenarios where for EPC-5GC Interworking is required. + +In scenarios where interworking between 5GS and EPC is possible, the network configuration is expected to associate UEs with SCEF+NEF node(s) for Service Capability Exposure. The SCEF+NEF hides the underlying 3GPP network topology from the AF (e.g. SCS/AS) and hides whether the UE is served by 5GC or EPC. + +If the service exposure function that is associated with a given service for a UE is configured in the UE's subscription information, then an SCEF+NEF identity shall be used to identify the exposure function. For example, if a UE is capable of switching between EPC and 5GC, then the SCEF ID that is associated with any of the UE's APN configurations should point to an SCEF+NEF node. + +For external exposure of services related to specific UE(s), the SCEF+NEF resides in the HPLMN. Depending on operator agreements, the SCEF+NEF in the HPLMN may have interface(s) with NF(s) in the VPLMN. + +The SCEF+NEF exposes over N33 the same API as the SCEF supports over T8. If CAPIF is not supported, the AF is locally configured with the API termination points for each service. If CAPIF is supported, the AF obtains the service API information from the CAPIF core function via the Availability of service APIs event notification or Service Discover Response as specified in TS 23.222 [64]. + +The common state information shall be maintained by the combined SCEF+NEF node in order to meet the external interface requirements of the combined node. The common state information includes at least the following data that needs to be common for the SCEF and NEF roles of SCEF+NEF: + +- SCEF+NEF ID (must be the same towards the AF). +- SCEF+NEF common IP address and port number. +- Monitoring state for any ongoing monitoring request. +- Configured set of APIs supported by SCEF+ NEF. +- PDN Connection/PDU Session State and NIDD Configuration Information, including Reliable Data Service state information. + +- Network Parameter Configuration Information (e.g. Maximum Response Time and Maximum Latency). + +The SCEF+NEF need not perform the same procedures for the configuration of monitoring events towards the HSS+UDM twice. For example, if the HSS+UDM is deployed as a combined node, a monitoring event only need to be configured by the SCEF+NEF just once. + +The SCEF+NEF may configure monitoring events applicable to both EPC and 5GC using only 5GC procedures towards UDM. In this case, the SCEF+NEF shall indicate that the monitoring event is also applicable to EPC (i.e. the event must be reported both by 5GC and EPC) and may include a SCEF address (i.e. if the event needs to be configured in a serving node in the EPC and the corresponding notification needs to be sent directly to the SCEF). If the HSS and UDM are deployed as separate network entities, UDM shall use HSS services to configure the monitoring event in EPC as defined in TS 23.632 [102]. The UDM shall return an indication to SCEF+NEF of whether the configuration of the monitoring event in EPC was successful. In the case that the UDM reports that the configuration of a monitoring event was not possible in EPC, then the SCEF+NEF may configure the monitoring event using EPC procedures via the HSS as defined in TS 23.682 [36]. + +NOTE 1: The SCEF+NEF uses only 5GC procedures to configure monitoring events in EPC and 5GC. + +NOTE 2: In terms of the CAPIF, the SCEF+NEF is considered a single node. + +#### 5.17.5.2 Support of interworking for Monitoring Events + +##### 5.17.5.2.1 Interworking with N26 interface + +In addition to the interworking principles documented in clause 5.17.2.2, the following applies for interworking with N26: + +- When UE moves from EPS to 5GS, when the AMF registers in UDM, if no event subscription via UDM is available, the AMF indicates the situation to the UDM, and in this case the UDM can decide if the event subscriptions should be provisioned, otherwise if the AMF has event subscription information, after the registration procedure is completed, the AMF may inform the UDM of the currently subscribed events, and UDM will do synchronization if needed. +- When UE moves from 5GS to EPS, the MME gets monitoring event configuration from HSS during as part of mobility procedure as specified in clause 4.11.1.3.2 of TS 23.502 [3]. + +##### 5.17.5.2.2 Interworking without N26 interface + +In addition to the interworking principles documented in clause 5.17.2.3, the additional behaviour at EPS to 5GS mobility in clause 5.17.5.2.1 also applies. + +When SCEF+NEF performs the procedure of monitoring via the AMF as described in clause 4.15.3.2.4 ("Exposure with bulk subscription") in TS 23.502 [3], if the AMF determines the interworking without N26 interface is supported, during mobility from 5GS to EPS, the AMF shall subscribe on behalf of SCEF+NEF for UDM+HSS notification of MME ID as described in clause 7.1.2 to trigger the SCEF+NEF to configure the monitoring request to the new MME. For single-registration mode, when UE's mobility from 5GS to EPS happens and Serving MME sends Update Location Request to the UDM+HSS, the UDM+HSS provides Serving MME ID to the SCEF+NEF which is the notification endpoint based on the subscription request from AMF. Then the SCEF+NEF performs the procedure of configuring monitoring via the MME for the same Monitoring Events as described in clause 5.6.2.1 of TS 23.682 [36]. + +When SCEF+NEF performs the procedure of monitoring via the UDM+HSS as described in clause 4.15.3.2.2 of TS 23.502 [3], when UE's mobility between 5GS and EPS happens, the UDM+HSS performs the procedure of configuring monitoring at the MME as described in clause 5.6.1.1 of TS 23.682 [36] and at the AMF as described in clause 4.15.3.2.1 of TS 23.502 [3]. + +#### 5.17.5.3 Availability or expected level of a service API + +A service related with common north-bound API may become unavailable due to UE being served by a CN node not supporting the service. If the availability or expected level of support of a service API associated with a UE changes, for example due to a mobility between 5GC and EPC, the AF shall be made aware of the change. + +NOTE 1: If CAPIF is supported and the service APIs become (un)available for the 5GC or EPC network, the AF obtains such information from the CAPIF core function. + +If the SCEF+NEF receives the subscription request from the AF for the availability or expected level of support of a service API, the SCEF+NEF subscribes a CN Type Change event for the UE or Group of UEs to the HSS+UDM. If the HSS+UDM receives the subscription for CN Type Change event, the HSS+UDM includes the latest CN type for the UE or Group of UEs in the response for the subscription. If the HSS+UDM detects that the UE switches between being served by the MME and the AMF, the CN Type Change event is triggered, and the HSS+UDM notifies the latest CN type for the UE or Group of UEs to the SCEF+NEF. Based on the CN type information, the SCEF+NEF can determine the availability or expected level of support of a given service. The AF will be informed of such information via a subscription/notification service operation. The AF can subscribe for the availability or expected level of support of a service API with report type indicating either One-time report or Continuous report. If there is no CN type information for the UE in the SCEF+NEF, the SCEF+NEF subscribes monitoring event for a new CN Type Change event for the UE or Group of UEs to the HSS+UDM, otherwise, SCEF+NEF determines the CN type locally in the following conditions: + +- If the AF subscribes with report type indicating One-time report, the SCEF+NEF may consider the Freshness Timer of the latest CN type information for the UE or Group of UEs. The Freshness Timer is a parameter that is configured based on local SCEF+NEF policy. When a subscription request with One-time report type is received the SCEF+NEF checks if there is the latest CN type information received from the HSS+UDM for the indicated UE ID or External Group ID. If the elapsed time for the CN type information since the last reception is less than the Freshness Timer, then the SCEF+NEF may respond to the AF with the latest CN type information in order to avoid repeated query to HSS+UDM. +- The SCEF+NEF has established a direct connection with MME or AMF or SMF. + +When the UE or all members of a Group of UEs are being served by a MME, EPC is determined as CN type. When the UE or all members of a Group of UEs are being served by an AMF, 5GC is determined as CN type. When the UE is registered both in EPC and 5GC, or some members of a Group of UEs are registered in EPC while some members are registered in 5GC, 5GC+EPC is determined as CN type. + +NOTE 2: If 5GC+EPC is determined as the CN type serving the UE or the group of UEs, the SCEF+NEF determines that service APIs for both 5GC and EPC are available to the UE or the group of UEs. + +### 5.17.6 Void + +### 5.17.7 Configuration Transfer Procedure between NG-RAN and E-UTRAN + +#### 5.17.7.1 Architecture Principles for Configuration Transfer between NG-RAN and E-UTRAN + +The purpose of the Configuration Transfer between NG-RAN and E-UTRAN is to enable the transfer the RAN configuration information between the gNB and eNodeB via MME and AMF. + +In order to make the information transparent for the MME and AMF, the information is included in a transparent container. The source and target RAN node addresses, which allows the Core Network nodes to route the messages. The mechanism depicted in Figure 5.17.7.1-1. + +![Diagram illustrating the Configuration Transfer between gNB and E-UTRAN basic network architecture. The diagram shows four main components: eNodeB, MME, gNB, and AMF. The eNodeB is connected to the MME via the S1 interface. The gNB is connected to the AMF via the N2 interface. The MME is connected to the AMF via the N26 interface. Arrows indicate the flow of Configuration Transfer Signaling: from eNodeB to MME over S1, from gNB to AMF over N2, and from AMF to MME over N26 (labeled 'Relaying Configuration Transfer Signaling').](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +graph TD + eNodeB[eNodeB] -- "Configuration Transfer Signaling" --> MME[MME] + gNB[gNB] -- "Configuration Transfer Signaling" --> AMF[AMF] + MME -- "Relaying Configuration Transfer Signaling" --> AMF + MME ---|N26| AMF + eNodeB ---|S1| MME + gNB ---|N2| AMF + +``` + +Diagram illustrating the Configuration Transfer between gNB and E-UTRAN basic network architecture. The diagram shows four main components: eNodeB, MME, gNB, and AMF. The eNodeB is connected to the MME via the S1 interface. The gNB is connected to the AMF via the N2 interface. The MME is connected to the AMF via the N26 interface. Arrows indicate the flow of Configuration Transfer Signaling: from eNodeB to MME over S1, from gNB to AMF over N2, and from AMF to MME over N26 (labeled 'Relaying Configuration Transfer Signaling'). + +**Figure 5.17.7.1-1: Configuration Transfer between gNB and E-UTRAN basic network architecture** + +The NG-RAN transparent containers are transferred from the source NG-RAN node to the destination E-UTRAN node and vice versa by use of Configuration Transfer messages. + +An ENB Configuration Transfer message is used from the E-UTRAN node to the MME over S1 interface as described in TS 36.413 [100], the destination RAN node includes the en-gNB Identifier and may include a TAI associated with the en-gNB. If MME is aware that the en-gNB serves cells which provide access to 5GC, the MME relays the request towards a suitable AMF via inter-system signalling based on a broadcast 5G TAC. An AMF Configuration Transfer message is used from the AMF to the NG-RAN over N2 interface. + +A Configuration Transfer message is used by the gNB node to the AMF over N2 interface for the reply, and a Configuration Transfer Tunnel message is used to tunnel the transparent container from AMF to MME over the N26 interface. MME relays this reply to the target eNB using a MME CONFIGURATION TRANSFER message. Transport of the RAN containers in E-UTRAN is specified in TS 23.401 [26]. + +Each Configuration Transfer message carrying the transparent container is routed and relayed independently by the core network node(s). Any relation between messages is transparent for the AMF and MME, i.e. a request/response exchange between applications, for example SON applications, is routed and relayed as two independent messages by the AMF and MME. + +#### 5.17.7.2 Addressing, routing and relaying + +##### 5.17.7.2.1 Addressing + +All the Configuration Transfer messages contain the addresses of the source and destination RAN nodes. + +An gNB node is addressed by the Target NG-RAN node identifier as described in TS 38.413 [34]. + +An eNodeB is addressed by the Target eNodeB identifier as described in TS 36.413 [100]. + +##### 5.17.7.2.2 Routing + +The source RAN node sends a message to its core network node including the source and destination addresses. + +MME uses the destination address to route the message to the correct AMF via N26 interface. AMF uses the destination address to route the message to the correct MME via N26 interface. + +The AMF connected to the destination RAN node decides which RAN node to send the message to, based on the destination address. + +The MME connected to the destination RAN node decides which RAN node to send the message to, based on the destination address. + +##### 5.17.7.2.3 Relaying + +The AMF performs relaying between N2 and N26 messages as described in TS 38.413 [34] and TS 29.274 [101]. + +The MME performs relaying between S1 and N26 message as described in TS 36.413 [100] and TS 29.274 [101]. + +### 5.17.8 URSP Provisioning in EPS + +When the UE registers in 5GS, the UE includes the Indication of URSP Provisioning Support in EPS in the UE Policy Container carried in Registration Request. On receiving this indication in the UE Policy Container, the PCF will provision the URSP to UE in EPS. + +The UE may include the indication of URSP Provisioning Support in EPS in PCO or ePCO to the SMF+PGW-C during: + +- Initial Attach with default PDN connection establishment (according to clause 5.3.2.1 of TS 23.401 [26]). +- Any UE requested PDN connectivity request to an additional PDN (according to clause 5.10.2 of TS 23.401 [26]). + +If the SMF+PGW-C supports URSP provisioning in EPS, it provides the Indication of URSP Provisioning Support in EPS in ePCO in the Create Session Response message. + +The UE ensures that there is only one PDN connection used for URSP rule delivery in EPS. When the UE receives an indication of URSP provisioning support in EPS in the PDN Connectivity Accept message and this PDN connection is not released, then for any subsequent PDN connectivity requests the UE does not include an indication of URSP Provisioning Support in EPS. + +When the UE receives the Indication of URSP Provisioning Support in EPS included in ePCO in the PDN Connectivity Accept message, then the UE initiates the UE requested bearer resource modification without QoS update procedure and includes the UE Policy Container ePCO in the Request Bearer Resource Modification message, the UE Policy Container in ePCO will be further forwarded by MME to SMF+PGW-C. When the UE Policy Container ePCO is received by SMF+PGW-C, it forwards transparently the UE Policy Container to PCF for the PDU Session, then the PCF for the PDU Session establishes the UE Policy Association with PCF for the UE. The PCF for the UE generates the corresponding URSP rules in a similar way as it is done in 5GS and sends the URSP rules to UE in the UE Policy Container as described in clause 4.11.0.a.5 of TS 23.502 [3]. + +NOTE 1: The UE includes the Indication of URSP Provisioning Support in EPS in PCO or ePCO in the PDN connectivity request according to clause 6.6.1.1 of TS 24.301 [13]. + +NOTE 2: The MME and Serving-GW can be configured to prioritize the selection of a SMF+PGW-C that support URSP Rule provisioning in EPS. + +If the UE does not receive the Indication of URSP Provisioning Support in EPS in ePCO in the PDN Connectivity Accept message, then the UE does not initiate the UE requested bearer resource modification procedure to send the UE Policy Container. + +The PDN Connection used by UE and SMF+PGW-C to convey UE Policy Container PCO shall be kept when the UE is in the CONNECTED mode. When the UE is attached to EPS, the PCF for the PDU Session retrieves the PCRTs for UE Policy from PCF for the UE and subscribes to the applicable PCRTs to SMF+PGW-C. The PCF for the PDU Session sends the UE Policy Container in the same PDN connection/PDU session in which the UE Policy Container was received. + +During EPS to 5GS mobility with N26, the UE Policy Association is terminated by PCF for PDU Session when it receives the indication of RAT type change from the SMF+PGW-C. + +During 5GS to EPS mobility with N26, the PCF for the PDU Session determines whether the UE supports URSP delivery in EPS by checking UE context policy control subscription information in UDR. The PCF for the PDU Session + +discovers the address of PCF for the UE serving the UE by querying BSF. The PCF for the UE recovers the information about the PSI list in the UE and the subscribed PCRTs in 5GS from former UE Policy Association for the UE after receiving the UE Policy Association Establishment request including a UE Policy Container only including an indication about the trigger for the UE Policy Association Establishment ("5GS to EPS mobility"). + +After the 5GS to EPS mobility, if PCF for the UE needs to provision the URSP to UE, the PCF for the UE sends the UE Policy Container in Npcf\_UEPolicyControl\_UpdateNotify Request to the PCF for the PDU Session as described in clause 4.11.0a.2a.10 of TS 23.502 [3]. In case there are more than one PDN connections for the UE, then the PCF for the PDU Session selects any of the ongoing PDN Connections via a SMF+PGW-C supporting URSP delivery in EPS for the UE. Then via the selected PDN Connection, the SMF+PGW-C sends the UE Policy Container via ePCO to UE by initiating the PDN GW initiated bearer modification without QoS update procedure as defined in clause 5.4.3 of TS 23.401 [26]. + +NOTE 3: At 5GS to EPS mobility with N26, the guard timer in the AMF (as specified in clauses 4.11.1.2.1 and 4.11.1.3.2 of TS 23.502 [3]) ensures that the UE Policy Association remains until the PCF for the UE detects that a UE Policy Association establishment is received from a PCF for the PDU Session indicating 5GS to EPS mobility. + +NOTE 4: In the case that the UE is still registered and reachable over non-3GPP access, the PCF for UE can have two UE policy associations for one UE, and based on local configuration the PCF can decide to use one of the UE policy associations to update URSP rule to the UE. The UE can receive URSP Rules over any of these two accesses. + +When the PCF for the UE decides to update the URSPs in the UE via EPS, the PCF for the UE sends the updated URSP rules in UE Policy Container to the PCF for the PDU Session, then the PCF for the PDU Session forwards it to the SMF+PGW-C. The SMF+PGW-C transfers the received UE Policy Container via ePCO to the UE by triggering PDN-GW initiated Bearer without QoS Modification procedure as described in clause 5.4.3 of TS 23.401 [26]. After update the UE policy provided by the PCF, the UE response about the delivery result via ePCO to the network. The SMF+PGW-C transparently forwards the UE response to the PCF for the PDU Session via Update Bearer Response message, and then the PCF for the PDU Session forwards it to the PCF for the UE via Npcf\_UEPolicyControl\_Update Request. If the SMF+PGW-C receives a rejection for Update Bearer Request message (e.g. due to paging failure), the delivery failure result is sent to PCF for the PDU Session and the PCF for the UE. To request to forward the result of delivery of UE policies, "Result of UE Policy Container delivery via EPS" PCRT is applied to the PCF for the PDU Session and the SMF+PGW-C as described in clause 4.11.0a.2a.10 of TS 23.502 [3]. + +## 5.18 Network Sharing + +### 5.18.1 General concepts + +A network sharing architecture shall allow multiple participating operators to share resources of a single shared network according to agreed allocation schemes. The shared network includes a radio access network. The shared resources include radio resources. + +The shared network operator allocates shared resources to the participating operators based on their planned and current needs and according to service level agreements. + +In this Release of the specification, only the 5G Multi-Operator Core Network (5G MOCN) network sharing architecture, in which only the RAN is shared in 5G System, is supported. 5G MOCN for 5G System, including UE, RAN and AMF, shall support operators' ability to use more than one PLMN ID (i.e. with same or different country code (MCC) some of which is specified in TS 23.122 [17] and different network codes (MNC)) or combinations of PLMN ID and NID. 5G MOCN supports NG-RAN Sharing with or without multiple Cell Identity broadcast as described in TS 38.300 [27]. + +5G MOCN also supports the following sharing scenarios involving non-public networks, i.e. NG-RAN can be shared by any combination of PLMNs, PNI-NPNs (with CAG), and SNPNs (each identified by PLMN ID and NID). + +NOTE 1: PNI-NPNs (without CAG) are not explicitly listed above as it does not require additional NG-RAN sharing functionality compared to sharing by one or multiple PLMNs. + +In all non-public network sharing scenarios, each Cell Identity as specified in TS 38.331 [28] is associated with one of the following configuration options: + +- one or multiple SNPNS; +- one or multiple PNI-NPNs (with CAG); or +- one or multiple PLMNs only. + +NOTE 2: This allows the assignment of multiple cell identities to a cell and also allows the cell identities to be independently assigned, i.e. without need for coordination, by the network sharing partners, between PLMNs and/or non-public networks. + +NOTE 3: Different PLMN IDs (or combinations of PLMN ID and NID) can also point to the same 5GC. When same 5GC supports multiple SNPNS (identified by PLMN ID and NID), it is up to the operator's policy whether they are used as equivalent SNPNS for a UE. + +NOTE 4: There is no standardized mechanism to avoid paging collisions if the same 5G-S-TMSI is allocated to different UEs by different PLMNs or SNPNS of the shared network, as the risk of paging collision is assumed to be very low. If such risk is to be eliminated then PLMNs and SNPNS of the shared network needs to coordinate the value space of the 5G-S-TMSI to differentiate the PLMNs and SNPNS of the shared network. + +![Diagram of a 5G Multi-Operator Core Network (5G MOCN) showing three 5GC Operators (A, B, and C) connected to a single shared NG RAN (Radio Access Network Operator X). The connections are labeled N2/N3.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +The diagram illustrates a 5G Multi-Operator Core Network (5G MOCN) architecture. At the top, three separate boxes represent '5GC Operator A', '5GC Operator B', and '5GC Operator C'. Dashed lines extend from each of these boxes to the left and right. Below these operators, a horizontal dashed line is labeled 'N2/N3', representing the interface between the core networks and the radio access network. Below this interface, a central box labeled 'NG RAN' is enclosed within a larger dashed oval labeled 'Radio Access Network Operator X'. Solid lines connect each of the three 5GC Operators (A, B, and C) directly to the 'NG RAN' box, indicating that multiple core networks share a single radio access network. + +Diagram of a 5G Multi-Operator Core Network (5G MOCN) showing three 5GC Operators (A, B, and C) connected to a single shared NG RAN (Radio Access Network Operator X). The connections are labeled N2/N3. + +**Figure 5.18.1-1: A 5G Multi-Operator Core Network (5G MOCN) in which multiple CNs are connected to the same NG-RAN** + +### 5.18.2 Broadcast system information for network sharing + +If a shared NG-RAN is configured to indicate available networks (PLMNs and/or SNPNS) for selection by UEs, each cell in the shared radio access network shall in the broadcast system information include available core network operators in the shared network. + +The Broadcast System Information broadcasts a set of PLMN IDs and/or PLMN IDs and NIDs and one or more additional set of parameters per PLMN e.g. cell-ID, Tracking Areas, CAG Identifiers. All 5G System capable UEs that connect to NG-RAN support reception of multiple PLMN IDs and per PLMN specific parameters. All SNPNS-enabled UEs support reception of multiple combinations of PLMN ID and NID and SNPNS-specific parameters. + +The available core network operators (PLMNs and/or SNPNS) shall be the same for all cells of a Tracking Area in a shared NG-RAN network. + +UEs not set to operate in SNPNS access mode decode the broadcast system information and take the information concerning available PLMN IDs into account in PLMN and cell (re-)selection procedures. UEs set to operate in SNPNS access mode decode the broadcast system information and take the information concerning available PLMN IDs and NIDs into account in network and cell (re-)selection procedures. Broadcast system information is specified in TS 38.331 [28] for NR, TS 36.331 [51] for E-UTRA and related UE access stratum idle mode procedures in TS 38.304 [50] for NR and TS 36.304 [52] for E-UTRA. + +### 5.18.2a PLMN list and SNPNS list handling for network sharing + +The AMF prepares lists of PLMN IDs or SNPNS IDs suitable as target PLMNs or target SNPNS for use at idle mode cell (re)selection and for use at handover and RRC Connection Release with redirection. The AMF: + +- provides the UE with the list of PLMNs or list of SNPNs that the UE shall consider as Equivalent to the serving PLMN or the serving SNPN (see TS 23.122 [17]); and +- provides the NG-RAN with a prioritised list of permitted PLMNs or a prioritized list of permitted SNPNs. When prioritising these PLMNs or SNPNs, the AMF may consider the following information: HPLMN of the UE or the subscribed SNPN of the UE, the serving PLMN or the serving SNPN, a preferred target PLMN (e.g. based on last used EPS PLMN) or a preferred target SNPN, or the policies of the operator(s). + +For a UE registered in an SNPN, the AMF shall not provide a list of equivalent PLMNs to the UE and shall not provide a list of permitted PLMNs to NG-RAN. + +For a UE registered in a PLMN, the AMF shall not provide a list of equivalent SNPNs to the UE and shall not provide a list of permitted SNPNs to NG-RAN. + +### 5.18.3 Network selection by the UE + +NOTE: This clause applies to UEs not operating in SNPN access mode. Network selection for UEs set to operate in SNPN access mode is described in clause 5.30.2.4. + +A UE that has a subscription to one of the sharing core network operators shall be able to select this core network operator while within the coverage area of the shared network and to receive subscribed services from that core network operator. + +Each cell in shared NG-RAN shall in the broadcast system information include the PLMN-IDs concerning available core network operators in the shared network. + +When a UE performs an Initial Registration to a network, one of available PLMNs shall be selected to serve the UE. UE uses all the received broadcast PLMN-IDs in its PLMN (re)selection processes which is specified in TS 23.122 [17]. UE shall inform the NG-RAN of the selected PLMN so that the NG-RAN can route correctly. The NG-RAN shall inform the core network of the selected PLMN. + +As per any network, after Initial Registration to the shared network and while remaining served by the shared network, the network selection procedures specified in TS 23.122 [17] may cause the UE to perform a reselection of another available PLMN. + +UE uses all of the received broadcast PLMN-IDs in its cell and PLMN (re)selection processes. + +### 5.18.4 Network selection by the network + +The NG-RAN uses the selected PLMN/SNPN (provided by the UE at RRC establishment, or, provided by the AMF/source NG-RAN at N2/Xn handover) to select target cells for future handovers (and radio resources in general) appropriately. The network should not move the UE to another available PLMN/SNPN, e.g. by handover, as long as the selected PLMN/SNPN is available to serve the UE's location. + +In the case of handover or network controlled release to a PLMN in a shared network: + +- When multiple PLMN IDs are broadcasted in a cell selected by NG-RAN, NG-RAN shall select a target PLMN, taking into account the prioritized list of PLMN IDs provided via Mobility Restriction List from AMF. +- For Xn based HO procedure, Source NG-RAN indicates the selected PLMN ID to the target NG-RAN, see TS 38.300 [27]. +- For N2 based HO procedure, the NG-RAN indicates a selected PLMN ID to the AMF as part of the TAI sent in the HO required message. Source AMF uses the TAI information supplied by the source NG-RAN to select the target AMF/MME. The source AMF should forward the selected PLMN ID to the target AMF/MME. The target AMF/MME indicates the selected PLMN ID to the target NG-RAN/eNB so that the target NG-RAN/eNB can select target cells for future handover appropriately. +- For RRC connection release with redirection to E-UTRAN procedure, NG-RAN decides the target network by using PLMN information as defined in the first bullet. + +A change in serving PLMN is indicated to the UE as part of the UE registration with the selected network via 5G-GUTI in 5GS. + +In the case of handover or network controlled release to an SNPN in a shared network, the following applies: + +- When multiple SNPN IDs are broadcasted in a cell selected by NG-RAN, NG-RAN shall select a target SNPN, taking into account the prioritized list of SNPN IDs provided via Mobility Restriction List from AMF. +- For Xn based HO procedure, Source NG-RAN indicates the selected SNPN ID to the target NG-RAN, see TS 38.300 [27]. +- For N2 based HO procedure, the NG-RAN indicates a selected SNPN ID to the AMF together with the TAI sent in the HO required message. Source AMF uses the selected SNPN ID together with the TAI information supplied by the source NG-RAN to select the target AMF. The source AMF should forward the selected SNPN ID to the target AMF. The target AMF indicates the selected SNPN ID to the target NG-RAN so that the target NG-RAN can select target cells for future handover appropriately. + +A change in serving SNPN is indicated to the UE as part of the UE registration with the selected network. + +### 5.18.5 Network Sharing and Network Slicing + +As defined in clause 5.15.1, a Network Slice is defined within a PLMN or SNPN. Network sharing is performed among different PLMNs and/or SNPNs. In the case of network sharing, each PLMN or SNPN sharing the NG-RAN defines and supports its PLMN- or SNPN- specific set of slices that are supported by the common NG-RAN. + +## 5.19 Control Plane Load Control, Congestion and Overload Control + +### 5.19.1 General + +In order to ensure that the network functions within 5G System are operating under nominal capacity for providing connectivity and necessary services to the UE. Thus, it supports various measures to guard itself under various operating conditions (e.g. peak operating hour, extreme situations). It includes support for load (re-)balancing, overload control and NAS level congestion control. A 5GC NF is considered to be in overload when it is operating over its nominal capacity resulting in diminished performance (including impacts to handling of incoming and outgoing traffic). + +### 5.19.2 TNLA Load Balancing and TNLA Load Re-Balancing + +AMF can support load balancing and re-balancing of TNL associations between 5G-AN and AMF by using mechanisms specified in clause 5.21.1. + +### 5.19.3 AMF Load Balancing + +The AMF Load Balancing functionality permits UEs that are entering into an AMF Region/AMF Set to be directed to an appropriate AMF in a manner that achieves load balancing between AMFs. This is achieved by setting a Weight Factor for each AMF, such that the probability of the 5G-AN selecting an AMF is proportional to Weight Factor of the AMF. The Weight Factor is typically set according to the capacity of an AMF node relative to other AMF nodes. The Weight Factor is sent from the AMF to the 5G-AN via NGAP messages (see TS 38.413 [34]). + +NOTE 1: An operator may decide to change the Weight Factor after the establishment of NGAP connectivity as a result of changes in the AMF capacities. e.g. a newly installed AMF may be given a very much higher Weight Factor for an initial period of time making it faster to increase its load. + +NOTE 2: It is intended that the Weight Factor is NOT changed frequently. e.g. in a mature network, changes on a monthly basis could be anticipated, e.g. due to the addition of 5G-AN or 5GC nodes. + +NOTE 3: Weight Factors for AMF Load Balancing are associated with AMF Names. + +Load balancing by 5G-AN node is only performed between AMFs that belong to the same AMF set, i.e. AMFs with the same PLMN, AMF Region ID and AMF Set ID value. + +The 5G-AN node may have their Load Balancing parameters adjusted (e.g. the Weight Factor is set to zero if all subscribers are to be removed from the AMF, which will route new entrants to other AMFs within an AMF Set). + +### 5.19.4 AMF Load Re-Balancing + +The AMF load re-balancing functionality permits cross-section of its subscribers that are registered on an AMF (within an AMF Set) to be moved to another AMF within the same AMF set with minimal impacts on the network and end users. AMF may request some or all of the 5G-AN node(s) to redirect a cross-section of UE(s) returning from CM-IDLE state to be redirected to another AMF within the same AMF set, if the 5G-AN is configured to support this. The AMF may request some or all of the 5G-AN node(s) to redirect the UEs served by one of its GUAMI(s) to a specific target AMF within the same AMF set or to any different AMF within the same AMF set. + +When indicating a specific target AMF, the AMF should ensure that the load re-balancing will not cause overload in the target AMF. + +NOTE: This requirement can be fulfilled by the AMF itself or by the OAM. + +For UE(s) in CM-IDLE state, when UE subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI pointing to an AMF that requested for redirection, the 5G-AN should select the specific target AMF (provided by the original AMF) or a different AMF from the same AMF set and forward the initial NAS message. + +For UE(s) in CONNECTED mode, similar mechanisms for AMF Management can be used to move the UE to another AMF in the same AMF set as described in clause 5.21.2, except that the old AMF deregisters itself from NRF. + +The newly selected/target AMF (which is now the serving AMF) will re-assign the GUTI (using its own GUAMI(s)) to the UE(s). It is not expected that the 5G-AN node rejects any request or enables access control restriction when it receives a request for redirection for load control from the connected AMF(s). + +When the AMF wants to stop redirection, the AMF can indicate that it can serve all UE(s) in CM-IDLE state to stop the redirection. + +NOTE 1: An example use for the AMF load re-balancing functionality is for the AMF to pro-actively re-balance its load prior to reaching overload i.e. to prevent overload situation. + +NOTE 2: Typically, AMF Load Re-Balancing is not needed when the AMF becomes overloaded because the Load Balancing function should have ensured that the other AMFs within the AMF Set are similarly overloaded. + +### 5.19.5 AMF Control Of Overload + +#### 5.19.5.1 General + +The AMF shall contain mechanisms for avoiding and handling overload situations. This includes the following measures: + +- N2 overload control that could result in RRC reject, RRC Connection Release and unified access barring. +- NAS congestion control. + +#### 5.19.5.2 AMF Overload Control + +Under unusual circumstances, if AMF has reached overload situation, the AMF activates NAS level congestion control as specified in Clause 5.19.7 and AMF restricts the load that the 5G-AN node(s) are generating, if the 5G-AN is configured to support overload control. N2 overload control can be achieved by the AMF invoking the N2 overload procedure (see TS 38.300 [27] and TS 38.413 [34]) to all or to a proportion of the 5G-AN nodes with which the AMF has N2 connections. The AMF may include the S-NSSAI(s) in NGAP OVERLOAD START message sent to 5G-AN node(s) to indicate the Network Slice(s) with which NAS signalling is to be restricted. To reflect the amount of load that the AMF wishes to reduce, the AMF can adjust the proportion of 5G-AN nodes which are sent NGAP OVERLOAD START message, and the content of the overload start procedure. + +When NGAP OVERLOAD START is sent by multiple AMFs or from the same AMF set in the same PLMN towards the 5G-AN, it should be ensured that the signalling load is evenly distributed within the PLMN and within each AMF set. + +A 5G-AN node supports restricting of 5G-AN signalling connection when a signalling connection establishment are attempted by certain UEs (which are registered or attempting to register with the 5GC), as specified in TS 38.331 [28] and TS 36.331 [51]. Additionally, a 5G-AN node provides support for the barring of UEs as described in TS 22.261 [2]. These mechanisms are further specified in TS 38.331 [28] and TS 36.331 [51]. For 3GPP Access Type, the signalling connection establishment attempt includes a RRC Connection Resume procedure from RRC\_INACTIVE. + +By sending the NGAP OVERLOAD START message, the AMF can request the 5G-AN node to apply the following behaviour for UEs that the AMF is serving: + +- a) Restrict 5G-AN signalling connection requests that are not for emergency, not for exception reporting and not for high priority mobile originated services; or +- b) Restrict 5G-AN signalling connection requests for uplink NAS signalling transmission to that AMF; +- c) Restrict 5G-AN signalling connection requests where the Requested NSSAI at AS layer only includes the indicated S-NSSAI(s) in the NGAP OVERLOAD START message. This applies also to RRC\_INACTIVE Connection Resume procedure where the Allowed NSSAI in the stored UE context in the RAN only includes S-NSSAIs included in the NGAP OVERLOAD START. +- d) only permit 5G-AN signalling connection requests for emergency sessions and mobile terminated services for that AMF; or +- e) only permit 5G-AN signalling connection requests for high priority sessions, exception reporting and mobile terminated services for that AMF; + +The above applies for RRC Connection Establishment procedure and RRC Connection Resume procedures over 3GPP access, as well as for the UE-N3IWF connection establishment over untrusted Non-3GPP access and for the UE-TNGF connection establishment over trusted Non-3GPP access. + +The AMF can provide a value that indicates the percentage of connection requests to be restricted in the NGAP OVERLOAD START, and the 5G-AN node may consider this value for congestion control. + +When restricting a 5G-AN signalling connection, the 5G-AN indicates to the UE an appropriate wait timer that limits further 5G-AN signalling connection requests until the wait timer expires. + +During an overload situation, the AMF should attempt to maintain support for emergency services and for MPS. + +When the AMF is recovering, the AMF can either: + +- send a NGAP OVERLOAD START message with a new percentage value that permits more connection requests to be successful, or +- send a NGAP OVERLOAD STOP message. + +to the same 5G-AN node(s) the NGAP OVERLOAD START was previously sent. + +### 5.19.6 SMF Overload Control + +The SMF shall contain mechanisms for avoiding and handling overload situations. This can include the following measures: + +- SMF overload control that could result in rejections of NAS requests. + +The SMF overload control may be activated by SMF due to congestion situation at SMF e.g. configuration, by a restart or recovery condition of a UPF, or by a partial failure or recovery of a UPF for a particular UPF(s). + +Under unusual circumstances, if the SMF has reached overload situation, the SMF activates NAS level congestion control as specified in clause 5.19.7. The SMF may restrict the load that the AMF(s) are generating, if the AMF is configured to enable the overload restriction. + +### 5.19.7 NAS level congestion control + +#### 5.19.7.1 General + +NAS level congestion control may be applied in general (i.e. for all NAS messages), per DNN, per S-NSSAI, per DNN and S-NSSAI, or for a specific group of UEs. + +NAS level congestion control is achieved by providing the UE a back-off time. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the 5GC should select each back-off time value so that the deferred requests are not synchronized. When the UE receives a back-off time, the UE shall not initiate any NAS signalling with regards to the applied congestion control until the back-off timer expires or the UE receives a mobile terminated request from the network, or the UE initiates signalling for emergency services or high priority access. + +AMFs and SMFs may apply NAS level congestion control, but should not apply NAS level congestion control for procedures not subject to congestion control. + +#### 5.19.7.2 General NAS level congestion control + +This clause only applies to NAS Mobility Management congestion control. + +Under general overload conditions the AMF may reject NAS messages from UEs using any 5G-AN. When a NAS request is rejected, a Mobility Management back-off time may be sent by the AMF to the UE. While the Mobility Management back-off timer is running, the UE shall not initiate any NAS request except for Deregistration procedure and procedures not subject to congestion control (e.g. high priority access, emergency services) and mobile terminated services. After any such Deregistration procedure, the back-off timer continues to run. While the Mobility Management back-off timer is running, the UE is allowed to perform Mobility Registration Update if the UE is already in CM-CONNECTED state. If the UE receives a paging request or a NAS notification message from the AMF while the Mobility Management back off timer is running, the UE shall stop the Mobility Management back-off timer and initiate the Service Request procedure or the Mobility Registration Update procedure over 3GPP access and/or non-3GPP access as applicable. Over non-3GPP access, if the UE is in CM-IDLE state when the back-off timer is stopped, it shall initiate the UE-triggered Service Request procedure as soon as it switches back to CM-CONNECTED state. + +In order to allow the UE to report the PS Data Off status change in PDU Session Modification Request message, the UE behaves as follows while keeping the NAS MM back-off timer running in the UE: + +- When the UE is in CM-IDLE state and has not moved out of the Registration Area, the UE is allowed to send a Service Request message with an indication that the message is exempted from NAS congestion control. When the UE is in CM-IDLE mode and has moved out of the Registration Area, the UE is allowed to send a Mobility Registration Update request message, with a Follow-on request, and with an indication that the message is exempted from NAS congestion control. +- When the UE is in CM-CONNECTED state, the UE sends a PDU Session Modification Request with PS Data Off status change carried in UL NAS Transport message with an indication that the message is exempted from NAS congestion control. + +When the NAS MM congestion control is activated at AMF, if the UE indicates that the NAS MM message is exempted from NAS congestion control, the AMF shall not reject the NAS MM message and shall forward the NAS SM message to the corresponding SMF with an indication that the NAS SM message was indicated to be exempted from NAS congestion control. The SMF ensures that the NAS SM message is not subject to congestion control otherwise the SMF rejects the message, e.g. the SMF shall reject PDU Session Modification received if it is not for Data Off status reporting. + +The Mobility Management back-off timer shall not impact Cell/RAT/Access Type and PLMN change. Cell/RAT/TA/Access Type change does not stop the Mobility Management back-off timer. The Mobility Management back-off timer shall not be a trigger for PLMN reselection or SNPN reselection. The back-off timer is stopped as defined in TS 24.501 [47] when a new PLMN or SNPN, that is not an equivalent PLMN or is not an equivalent SNPN, is accessed. + +To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the AMF should select the Mobility Management back-off timer value so that the deferred requests are not synchronized. + +If the UE required to report 5GSM Core Network Capability change, or the Always-on PDU Session Requested indication while the NAS MM congestion control timer was running and was unable to initiate MM signalling, the UE + +defers the related MM signalling until the MM congestion control timer expires and initiates after the expiry of the timer. + +In the case of a UE with scheduled communication pattern, the AMF may consider the UE's communication pattern while selecting a value for the Mobility Management back-off timer so that the UE does not miss its only scheduled communication window. + +The AMF should not reject Registration Request message for Mobility Registration Update that are performed when the UE is already in CM-CONNECTED state. + +The AMF may reject the Service Request message and a UL NAS Transfer with a Mobility Management back-off time when the UE is already in CM-CONNECTED state. If UE receives a DL NAS Transfer message from the AMF while the Mobility Management back off timer is running, the UE shall stop the Mobility Management back-off timer. + +For CM-IDLE state mobility, the AMF may reject Registration Request messages for Mobility Registration Update by including a Mobility Management back off time value in the Registration Reject message. + +If UE registered in the same PLMN for 3GPP access and non-3GPP access and receives a Mobility Management back-off time from the AMF, the back-off time (and corresponding start and stop) is applied equally to both 3GPP access and non-3GPP access. If UE registered in different PLMNs for 3GPP access and non-3GPP access respectively and receives a Mobility Management back-off time, the back-off time is only applied to the PLMN that provides the time to the UE. + +If the AMF rejects Registration Request messages or Service Request with a Mobility Management back-off time which is larger than the sum of the UE's Periodic Registration Update timer and the Implicit Deregistration timer, the AMF should adjust the mobile reachable timer and/or Implicit Deregistration timer such that the AMF does not implicitly deregister the UE while the Mobility Management back-off timer is running. + +NOTE: This is to minimize signalling after the Mobility Management back-off timer expires. + +If the AMF deregisters the UE with an indication of re-registration required, the UE behaviour for handling the back-off timer(s) is as specified in TS 24.501 [47]. + +#### 5.19.7.3 DNN based congestion control + +DNN based congestion control is designed for the purpose of avoiding and handling of NAS SM signalling congestion for the UEs with a back-off timer associated with or without a DNN regardless of the presence of an S-NSSAI. Both UE and 5GC shall support the functionality to enable DNN based congestion control. + +SMFs may apply DNN based congestion control towards the UE by rejecting PDU Session Establishment Request message, or PDU Session Modification Request message except for those sent for the purpose of reporting 3GPP PS Data Off status change for a specific DNN with a running back-off timer. The SMF may release PDU Sessions belonging to a congested DNN by sending a PDU Session Release Command message towards the UE with a DNN back-off timer. If a DNN back-off time is set in the PDU Session Release Command message, the cause value of "reactivation requested" shall not be set. + +If NWDAF is deployed, the SMF may make use of Session Management Congestion Control Experience analytics provided by NWDAF, as defined in clause 6.12 of TS 23.288 [86], to determine back-off timer provided to UEs. + +NOTE: For example, the SMF can apply a short back-off timer to the UEs in the list of high-experienced UEs while the SMF can apply a long back-off timer to the UEs in the list of low-experienced UEs. + +When DNN based congestion control is activated at AMF e.g. configured by OAM, the AMF provides a NAS Transport Error message for the NAS Transport message carrying an SM message, and in the NAS Transport Error message it includes a DNN back-off timer. + +The UE associates the received back-off time with the DNN (i.e. no DNN, DNN only) which the UE included in the uplink NAS MM message carrying the corresponding NAS SM request message. + +The UE associates the received back-off time with the DNN (i.e. no DNN, DNN only) in any PLMN unless the DNN associated with the back-off timer is an LADN DNN in which case the UE only associates it to the PLMN in which the back-off time was received. + +The UE behaves as follows when the DNN back-off timer is running: + +- If a DNN is associated with the back-off timer, the UE shall not initiate any Session Management procedures for the congested DNN. The UE may initiate Session Management procedures for other DNNs. The UE shall not initiate any Session Management procedure for the corresponding APN when UE moves to EPS. The UE may initiate Session Management procedures for other APNs when the UE moves to EPS; +- If no DNN is associated with the back-off timer, the UE may only initiate Session Management requests of any PDU Session Type for a specific DNN; +- Upon Cell/TA/PLMN/RAT change, change of untrusted non-3GPP access network or change of Access Type, the UE shall not stop the back-off timer; +- The UE is allowed to initiate the Session Management procedures for high priority access and emergency services; +- The UE is allowed to initiate the Session Management procedure for reporting Data Off status change to the network; +- If the UE receives a network initiated Session Management message other than PDU Session Release Command for the congested DNN associated to a running back-off timer, the UE shall stop the back-off timer and respond to the 5GC; +- If the UE receives a PDU Session Release Command message for the congested DNN, it shall stop the back-off timer unless it receives a new back-off time from SMF; +- The UE is allowed to initiate PDU Session Release procedure (i.e. sending PDU Session Release Request message). The UE shall not stop the back-off timer when the related PDU Session is released; +- The list above is not an exhaustive list, i.e. more details of the above actions and further conditions, if any, are specified in TS 24.501 [47]. + +If UE initiates one of the Session Management procedures that are exempted from NAS congestion control, the UE indicates that the carried NAS SM message is exempted from NAS congestion control in the UL NAS Transport message as described in TS 24.501 [47]. When the DNN based congestion control is activated at AMF, if the UE indicates that the NAS SM message in the UL NAS Transport message is exempted from NAS congestion control, the AMF shall not apply DNN based congestion control on the UL NAS Transport message and shall forward the NAS SM message to the corresponding SMF with an indication that the message was received with exemption indication. The SMF evaluates whether the NAS SM message is allowed to be exempted from DNN based congestion control. If it is not, the SMF rejects the message, e.g. the SMF shall reject PDU Session Modification received if it is not for Data Off status reporting). + +The UE shall maintain a separate back-off timer for each DNN that the UE may use. + +To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the 5GC should select the back-off timer value so that deferred requests are not synchronized. + +If the UE required to report 5GSM Core Network Capability change, or the Always-on PDU Session Requested indication while DNN based congestion control was running and was unable to initiate SM signalling, the UE defers the related SM signalling until the DNN based congestion control timer expires and initiates the necessary SM signalling after the expiry of the timer. + +The DNN based Session Management congestion control is applicable to the NAS SM signalling initiated from the UE in the Control Plane. The Session Management congestion control does not prevent the UE from sending and receiving data or initiating Service Request procedures for activating User Plane connection towards the DNN(s) that are under Session Management congestion control. + +#### 5.19.7.4 S-NSSAI based congestion control + +S-NSSAI based congestion control is designed for the purpose of avoiding and handling of NAS signalling congestion for the UEs with back-off timer associated with or without an S-NSSAI regardless of the presence of a DNN. + +The UE associates the received back-off time with the S-NSSAI and DNN (i.e. no S-NSSAI and no DNN, no S-NSSAI, S-NSSAI only, an S-NSSAI and a DNN) which was included in the uplink NAS MM message carrying the corresponding NAS SM request message for the PLMN which is under congestion. + +S-NSSAI based congestion control is applied as follows: + +- If an S-NSSAI is determined as congested, then the SMF may apply S-NSSAI based congestion control towards the UE for SM requests except for those sent for the purpose of reporting 3GPP PS Data Off status change for a specific S-NSSAI and provides a back-off time and an indication of HPLMN congestion; +- If the UE receives an S-NSSAI based back-off time without an indication of HPLMN congestion, the UE shall apply the S-NSSAI back-off timer only in the PLMN in which the back-off time was received. If the UE receives S-NSSAI based back-off time with an indication of HPLMN congestion, the UE shall apply the S-NSSAI based back-off timer in the PLMN in which the back-off time was received and in any other PLMN; +- The SMF may release PDU Sessions belonging to a congested S-NSSAI by sending a PDU Session Release Request message towards the UE with a back-off time associated either to the S-NSSAI only (i.e. with no specific DNN) or a combination of the S-NSSAI and a specific DNN. If NWDAF is deployed, the SMF may make use of Session Management Congestion Control Experience analytics provided by NWDAF, as defined in clause 6.12 of TS 23.288 [86], to determine back-off timer provided to UEs; + +NOTE: For example, the SMF can apply a short back-off timer to the UEs in the list of high-experienced UEs while the SMF can apply a long back-off timer to the UEs in the list of low-experienced UEs. + +- If S-NSSAI based congestion control is activated at AMF e.g. configured by OAM and an S-NSSAI is determined as congested, then the AMF applies S-NSSAI based congestion control towards the UE for UE-initiated Session Management requests. In this case, the AMF provides a NAS Transport Error message for the NAS Transport message carrying the SM message, and in the NAS Transport Error message it includes a back-off timer; If NWDAF is deployed, the AMF may determine that S-NSSAI is congested based on the network slice load level analytics defined in TS 23.288 [86]. +- The UE behaves as follows in the PLMN where the S-NSSAI based congestion control applies when the back-off timer is running: + - If the back-off timer was associated with an S-NSSAI only (i.e. not associated with an S-NSSAI and a DNN), the UE shall not initiate any Session Management procedures for the congested S-NSSAI; + - If the back-off timer was associated with an S-NSSAI and a DNN, then the UE shall not initiate any Session Management procedures for that combination of S-NSSAI and DNN; + - If the UE receives a network-initiated Session Management message other than PDU Session Release Command for the congested S-NSSAI, the UE shall stop this back-off timer and respond to the 5GC; + - If the UE receives a PDU Session Release Command message for the congested S-NSSAI, it shall stop the back-off timer unless it receives a new back-off time from SMF; + - Upon Cell/TA/PLMN/RAT change, change of untrusted non-3GPP access network or change of Access Type, the UE shall not stop the back-off timer for any S-NSSAI or any combination of S-NSSAI and DNN; + - The UE is allowed to initiate the Session Management procedures for high priority access and emergency services for the S-NSSAI; + - The UE is allowed to initiate the Session Management procedure for reporting Data Off status change for the S-NSSAI or the combination of S-NSSAI and DNN. +- If the back-off timer is not associated to any S-NSSAI, the UE may only initiate Session Management procedures for specific S-NSSAI; +- If the back-off timer is not associated to any S-NSSAI and DNN, the UE may only initiate Session Management procedures for specific S-NSSAI and DNN; +- The UE is allowed to initiate PDU Session Release procedure (e.g. sending PDU Session Release Request message). The UE shall not stop the back-off timer when the related PDU Session is released; +- The list above is not an exhaustive list, i.e. more details of the above actions and further conditions, if any, are specified in TS 24.501 [47]. + +The UE shall maintain a separate back-off timer for each S-NSSAI and for each combination of S-NSSAI and DNN that the UE may use. + +If UE initiates one of the Session Management procedure that are exempt from NAS congestion control, the UE indicates that the carried NAS SM message is exempted from NAS congestion control in the UL NAS Transport + +message as described in TS 24.501 [47]. When the S-NSSAI based congestion control is activated at AMF, if the UE indicates that the NAS SM message in the UL NAS Transport message is exempted from NAS congestion control, the AMF shall not apply S-NSSAI based congestion control on the UL NAS Transport message and shall forward the NAS SM message to the corresponding SMF with an indication that the message was received with exemption indication. The SMF evaluates whether that the NAS SM message is allowed to be exempted from S-NSSAI based congestion control. If it is not, the SMF rejects the message, e.g. the SMF shall reject PDU Session Modification received if it is not for Data Off status reporting. + +The back-off timer associated with an S-NSSAI or a combination of an S-NSSAI and a DNN shall only apply to congestion control for Session Management procedures when UE is in 5GS. + +To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the 5GC should select the value of the back-off timer for the S-NSSAI based congestion control so that deferred requests are not synchronized. + +If the UE required to report 5GS Core Network Capability change, or the Always-on PDU Session Requested indication while S-NSSAI based congestion control timer was running and was unable to initiate SM signalling, the UE defers the related SM signalling until the S-NSSAI based congestion control timer expires and initiates the necessary SM signalling after the expiry of the timer. + +The S-NSSAI based congestion control does not prevent the UE from sending and receiving data or initiating Service Request procedure for activating User Plane connection for a PDU Session associated to the S-NSSAI that is under the congestion control. + +#### 5.19.7.5 Group specific NAS level congestion control + +The group specific NAS level congestion control applies to a specific group of UEs. Group specific NAS level congestion control is performed at the 5GC only, and it is transparent to UE. The AMF or SMF or both may apply NAS level congestion control for a UE associated to an Internal-Group Identifier (see clause 5.9.7). + +NOTE: 5GC logic for Group specific NAS level congestion control is not described in this Release of the specification. + +#### 5.19.7.6 Control Plane data specific NAS level congestion control + +Under overload conditions the AMF may restrict requests from UEs for data transmission via Control Plane CIoT 5GS Optimisation. A Control Plane data back-off timer may be returned by the AMF (e.g. in Registration Accept messages, Service Reject message or Service Accept message). While the Control Plane data back-off timer is running, the UE shall not initiate any data transfer via Control Plane CIoT 5GS Optimisation, i.e. the UE shall not send any Control Plane Service Request with uplink data as defined in TS 24.501 [47]. The AMF shall store the Control Plane data back-off timer per UE and shall not process any further requests (other than exception reporting and a response to paging) for Data Transport via a Control Plane Service Request from that UE while the Control Plane data back-off timer is still running. + +NOTE 1: The Control Plane data back-off timer does not affect any other mobility management or session management procedure. + +NOTE 2: The Control Plane data back-off timer does not apply to user plane data communication. + +If the UE is allowed to send exception reporting, the UE may send an initial NAS Message for exception reporting even if Control Plane data back-off timer is running. + +The UE may respond to paging with an initial NAS Message without uplink data even if the Control Plane data back-off timer is running. + +If the AMF receives an initial NAS Message in response to a paging, and the AMF has a Control Plane data back-off timer running for the UE, and the AMF is not overloaded, and AMF decides to accept the Control Plane Service Request, then the AMF shall respond with Service Accept without the Control Plane data back-off timer and stop the Control Plane data back-off timer. If the UE receives a Service Accept without the Control Plane data back-off timer from the AMF while the Control Plane data back-off timer is running, the UE shall stop the Control Plane data back-off timer. The Control Plane data back-off timer in the UE and the AMF is stopped at PLMN change. + +If the AMF receives a Control Plane Service Request with uplink data, and decides to send the UE a Control Plane data back-off timer, the AMF may decide to process the Control Plane Service Request with uplink data, i.e. decrypt and forward the data payload, or not based on the following: + +- If the UE has indicated Release Assistance Information that no further Uplink and Downlink Data transmissions are expected, then the AMF may process (integrity check/decipher/forward) the received Control Plane data packet, and send a Service Accept to the UE with Control Plane data back-off timer. The UE interprets this as successful transmission of the Control Plane data packet starts the Control Plane data back-off timer. +- For all other cases, the AMF may decide to not process the received Control Plane data packet and send a Service Reject to the UE with Control Plane data back-off timer. The UE interprets this indication as unsuccessful delivery of the control plane data packet and starts the Control Plane data back-off timer. The AMF may take into consideration whether the PDU Session is set to Control Plane only to make the decision whether to reject the packet and send Service Reject or move the PDU Session to user plane and process the data packet as described in next bullet. +- Alternatively, if UE has not provided Release Assistance Information, and the PDU Session not set to Control Plane only, and UE supports N3 data transfer, then the AMF may initiate establishment of N3 bearer according to the procedure defined in clause 4.2.3 of TS 23.502 [3]. In this case the AMF may also return a Control Plane data back-off timer within the Service Accept. + +The AMF only includes the Control Plane data back-off timer if the UE has indicated support for Control Plane CIoT 5GS optimizations in the Registration Request. + +## 5.20 External Exposure of Network Capability + +The Network Exposure Function (NEF) supports external exposure of capabilities of network functions. External exposure can be categorized as Monitoring capability, Provisioning capability, Policy/Charging capability, Analytics reporting capability and Member UE selection capability. The Monitoring capability is for monitoring of specific event for UE in 5G System and making such monitoring events information available for external exposure via the NEF. The Provisioning capability is for allowing external party to provision of information which can be used for the UE in 5G System. The Policy/Charging capability is for handling access and mobility management, QoS and charging policies for the UE based on the request from external party. The Analytics reporting capability is for allowing an external party to fetch or subscribe/unsubscribe to analytics information generated by 5G System (this is further defined in TS 23.288 [86]). The Member UE selection capability is for allowing an external party to acquire one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information that is based on the assistance information generated by 5G System based on some defined filtering criteria, the details are explained in clause 4.15.13 in TS 23.502 [3]. + +Monitoring capability is comprised of means that allow the identification of the 5G network function suitable for configuring the specific monitoring events, detect the monitoring event, and report the monitoring event to the authorised external party. Monitoring capability can be used for exposing UE's mobility management context such as UE location, reachability, roaming status, and loss of connectivity. Monitoring capability can also be used for exposing QoS monitoring result. AMF stores URRP-AMF information in the MM context to determine the NFs that are authorised to receive direct notifications from the AMF. UDM stores URRP-AMF information locally to determine authorised monitoring requests when forwarding indirect notifications. The Monitoring capability also allows AF to subscribe to the group status changes for a group, either a 5G VN group as described in clause 5.29.2, as well as a group configured by OA&M. In this case the AF is notified if the group member list is updated or a group member is no longer subscribed to the group. + +Provisioning capability allows an external party to provision the Expected UE Behaviour or the 5G-VN group information or DNN and S-NSSAI specific Group Parameters or ECS Address Configuration Information or service specific information to 5G NF via the NEF. The provisioning comprises of the authorisation of the provisioning external third party, receiving the provisioned external information via the NEF, storing the information, and distributing that information among those NFs that use it. The externally provisioned data can be consumed by different NFs, depending on the data. In the case of provisioning the Expected UE Behaviour, the externally provisioned information which is defined as the Expected UE Behaviour parameters in clause 4.15.6.3 of TS 23.502 [3] or Network Control parameter in clause 4.15.6.3a of TS 23.502 [3] consists of information on expected UE movement, Expected UE Behaviour parameters or expected Network Configuration parameter. The provisioned Expected UE Behaviour parameters may be used for the setting of mobility management or session management parameters of the UE. In the case of provisioning the 5G-VN group information the externally provisioned information is defined as the 5G-VN group parameters in clause 4.15.6.7 of TS 23.502 [3] and it consists of some information on the 5G-VN group. In the + +case of the provisioning the DNN and S-NSSAI specific Group Parameters, the externally provisioned information is defined in clause 4.15.6.14 of TS 23.502 [3] and clause 5.20b. In the case of provisioning ECS address, the externally provisioned information is defined as the ECS Address Configuration Information in clause 4.15.6.3d of TS 23.502 [3]. The affected NFs are informed via the subscriber data update as specified in clause 4.15.6.2 of TS 23.502 [3]. The externally provisioned information which is defined as the Service Parameters in clause 4.15.6.7 of TS 23.502 [3] consists of service specific information used for supporting the specific service in 5G system. The provisioned Service Parameters may be delivered to the UEs. The affected NFs are informed of the data update. + +Policy/Charging capability is comprised of means that allow the request for session and charging policy, enforce QoS policy, apply accounting functionality and requests to influence access and mobility management policies. It can be used for specific QoS/priority handling for the session of the UE, and for setting applicable charging party or charging rate. + +Analytics reporting capability is comprised of means that allow discovery of type of analytics that can be consumed by external party, the request for consumption of analytics information generated by NWDAF. + +Member UE selection capability is comprised of means that allows filtering and providing one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information that can be consumed by external party, the request for consumption of UE list generated by external party. + +An NEF may support CAPIF functions for external exposure as specified in clause 6.2.5.1. + +An NEF may support exposure of NWDAF analytics as specified in TS 23.288 [86]. + +The NEF may support exposure of 5GS and/or UE availability and capabilities for time synchronization service as specified in clause 5.27.1.8. + +An NEF may support exposure of event based notifications and reports for NSACF as specified in clause 5.15.11. + +An AF may only be able to identify the target UE of an AF request for external exposure of 5GC capabilities (e.g. Data Provisioning or for Event Exposure for a specific UE) by providing the UE's address information. In this case the NEF first needs to retrieve the Permanent identifier of the UE before trying to fulfil the AF request. The NEF may determine the Permanent identifier of the UE, as described in clause 4.15.3.2.13 of TS 23.502 [3], based on: + +- the address of the UE as provided by the AF; this may be an IP address or a MAC address; +- the corresponding DNN and/or S-NSSAI information: this may have been provided by the AF or determined by the NEF based on the requesting AF; this is needed if the UE address is an IP address. + +The NEF may provide an AF specific UE Identifier to the AF: + +- that has explicitly requested a translation from the address of the UE to a unique UE identifier (via Nnef\_UEId service); or +- that has implicitly requested a translation from the address of the UE to a AF specific UE Identifier by requesting external exposure about an individual UE identified by its address. + +The AF may have its own means to maintain the AF specific UE Identifier through, e.g. an AF session. After the retrieval of an AF specific UE Identifier the AF shall not keep maintaining a mapping between this identifier and the UE IP address as this mapping may change. + +The AF specific UE Identifier shall not correspond to a MSISDN; it is represented as a GPSI in the form of an External Identifier. When used as an AF specific UE identifier, the External Identifier provided by the 5GCN shall be different for different AF. + +NOTE 1: This is to protect user privacy. + +NOTE 2: The AF specific UE identifier is ensured to be unique across different AFs as defined in TS 23.003 [19] by configuration. Such configuration is assumed to be coordinated between the different involved entities (e.g. NEF(s) and UDM/UDR). + +NOTE 3: Based on policies, the NEF can be configured to enforce restriction on the usage of AF specific UE identifier (e.g. rejection of a service request from AF not authorized to use the UE identifier). + +## 5.20a Data Collection from an AF + +An NF that needs to collect data from an AF may subscribe/unsubscribe to notifications regarding data collected from an AF, either directly from the AF or via NEF. + +The data collected from an AF is used as input for analytics by the NWDAF. + +The details for the data collected from an AF as well as interactions between NEF, AF and NWDAF are described in TS 23.288 [86]. + +## 5.20b Support exposure of DNN and S-NSSAI specific Group Parameters + +#### 5.20b.1 Group attribute provisioning + +A group may be a 5G VN group managed as defined in clause 5.29.2, as well as a group configured by OA&M. + +An AF may provision DNN and S-NSSAI specific attributes for a group of UEs: + +- LADN Service area, which consists of Tracking Area identities or geographical information, it is applicable to each UE member within the group and for a specific DNN and S-NSSAI. +- Default QoS, the QoS refers to 5QI, ARP and 5QI Priority Level as defined in clause 5.7.2.7 and it is applicable to each UE member within the group and for a specific DNN and S-NSSAI. + +### 5.20b.2 Support LADN service area for a group + +The procedure as defined in clause 4.15.6.2 of TS 23.502 [3] is applicable for provisioning of LADN service area for a group with the following clarifications and enhancements: + +- The AF request additionally contains the LADN service area as part of DNN and S-NSSAI specific Group Parameters, and the LADN service area is stored in UDR as subscription data and delivered to AMF. If the AMF receives the LADN service area for a group, the AMF configures the DNN of the group as LADN DNN. +- If the AF provides the LADN service area in the form of geographical information, the NEF maps the geographical information to a list of TAs before sending the service area to the UDM. + +LADN per DNN and S-NSSAI as defined in clause 5.6.5a is applicable for enforcement of LADN service area. + +### 5.20b.3 Support QoS for a group + +The procedure as defined in clause 4.15.6.2 of TS 23.502 [3] is applicable for provisioning of default QoS for a DNN and S-NSSAI for a group of UEs with the following clarifications and enhancements: + +- The AF request contains the Default QoS for the group, and the UDM stores such QoS in the UDR and uses such QoS to set 5GS Subscribed QoS profile in Session Management Subscription data for each UE within the group. + +NOTE: When a UE belongs to multiple groups simultaneously, and AF(s) provision different Default QoS for the same DNN and S-NSSAI but different groups, UDM selects a QoS profile among the groups the UE belongs to for a DNN and S-NSSAI to set the 5GS subscribed QoS profile. How the UDM selects a QoS profile is based on implementation and configuration. The UDM can e.g. select a QoS profile with a higher 5QI Priority Level or higher ARP priority level. + +Mechanisms as defined in clause 5.7.2.7 are used to enforce the 5GS Subscribed QoS profile for a DNN and S-NSSAI for each UE within a group. + +### 5.20b.4 Void + +#### 5.20b.5 Void + +## 5.20c Provisioning of traffic characteristics and monitoring of performance characteristics for a group + +NEF provisioning capability as defined in clause 5.20 allows an AF to perform provisioning of traffic characteristics and monitoring of performance characteristics for a group of UEs as specified in clause 4.15.6.14 of TS 23.502 [3] and clause 6.1.3.28 of TS 23.503 [45]. + +NOTE : The AF may use application layer functionalities to handle requests for UE-to-UE traffic as defined by SA WG6. + +The NEF determines whether or not to invoke the TSCTSF in the same way as for AF session with required QoS procedure, as described in step 2 of clause 4.15.6.6 in TS 23.502 [3]. In the case that the TSCTSF is used, the TSCTSF receives the AF requested QoS information from the NEF. In the case that TSCTSF is not used, the AF request is handled as described in clause 4.15.6.14 of TS 23.502 [3] and clause 6.1.3.28 of TS 23.503 [45]. + +When the TSCTSF receives the AF requested QoS information from NEF or the PCF(s) receive the AF requested QoS information from UDR, the TSCTSF or PCF (s) manage the AF requested QoS information for each UE group member within the group as follows: + +- Translate the External Group ID into a list of SUPIs by invoking Nudm\_SDM\_Get service. +- Determine which of these UE group members have active PDU Sessions matching the DNN and S-NSSAI and determine the relevant UE address. +- Manage the request status (activated, de-activated, failed) for each UE group member within the group: + - Apply the AF requested QoS information if the UE group member is registered or has active PDU Session matching the DNN and S-NSSAI. Set the status to activated if the QoS resources are assigned for the UE group member, otherwise, failed. + - Set the status to de-activated if the UE group member is not registered or has no active PDU Session matching the DNN and S-NSSAI. + - Delete the request status for the UE group member if the UE group member is removed from the group, and further revokes AF request QoS information if the request status is activated. + - Check whether to apply the AF requested QoS information and update the request status for the UE group member if the UE group member is newly added to the group. +- When the AF requested QoS information contains temporal invalidity condition: + - Revoke AF requested QoS information for each UE group member which is marked as active, so to e.g. to remove or modify PCC rules as defined in clause 4.16.5.2 of TS 23.502 [3] if the start-time is reached. + - Apply AF requested QoS information for each UE group member that has active PDU Sessions matching the DNN and S-NSSAI, e.g. to add or modify PCC rules as defined in clause 4.16.5.2 of TS 23.502 [3]. + +## 5.20d User Plane Direct 5GS Information Exposure + +#### 5.20d.1 General + +In order to expose network information, the user plane direct 5GS information exposure function may be applied. The user plane direct 5GS information exposure function allows the UPF to report the network information directly to consumer based on the instructions provided by SMF. + +NOTE: In the scenario of Edge Computing as described in TS 23.548 [130], the consumer can be the L-NEF or local AF when the local AF is trusted. + +When the exposed network information is provided by the UPF, the PSA UPF may be instructed to report network information via Nupf\_EventExposure service (e.g. directly to an AF, i.e. bypassing the SMF and the PCF); or the UPF may be instructed to report the information to the consumer via SMF/PCF/NEF, as described in clause 5.8.2.18. + +When the exposed network information is provided by the NG-RAN, the NG-RAN may be instructed by the SMF to report the information via the GTP-U tunnel(s) between the NG RAN and PSA UPF, as defined in clause 5.45. + +The User Plane Direct 5GS Information Exposure may be used for exposing the following information: + +- QoS Monitoring information (see clause 5.45). +- TSC Management Information (see clause 5.28.3). + +## 5.21 Architectural support for virtualized deployments + +### 5.21.0 General + +5GC supports different virtualized deployment scenarios, including but not limited to the options below: + +- A Network Function instance can be deployed as distributed, redundant, stateless, and scalable NF instance that provides the services from several locations and several execution instances in each location. + - This type of deployments would typically not require support for addition or removal of NF instances for redundancy and scalability. In the case of an AMF this deployment option may use enablers like, addition of TNLA, removal of TNLA, TNLA release and rebinding of NGAP UE association to a new TNLA to the same AMF. +- A Network Function instance can also be deployed such that several network function instances are present within a NF set provide distributed, redundant, stateless and scalability together as a set of NF instances. + - This type of deployments may support for addition or removal of NF instances for redundancy and scalability. In the case of an AMF this deployment option may use enablers like, addition of AMFs and TNLAs, removal of AMFs and TNLAs, TNLA release and rebinding of NGAP UE associations to a new TNLA to different AMFs in the same AMF set. +- The SEPP, although not a Network Function instance, can also be deployed distributed, redundant, stateless, and scalable. +- The SCP, although not a Network Function instance, can also be deployed distributed, redundant, and scalable. + +Also, deployments taking advantage of only some or any combination of concepts from each of the above options is possible. + +### 5.21.1 Architectural support for N2 + +#### 5.21.1.1 TNL associations + +5G-AN node shall have the capability to support multiple TNL associations per AMF, i.e. AMF name. + +An AMF shall provide the 5G-AN node with the weight factors for each TNL association of the AMF. + +The AMF shall be able to request the 5G-AN node to add or remove TNL associations to the AMF. + +The AMF shall be able to indicate to the 5G-AN node the set of TNL associations used for UE-associated signalling and the set of TNL associations used for non-UE associated signalling. + +NOTE: The TNL association(s) indicated for UE-associated and non-UE associated signalling can either be overlap or be different. + +#### 5.21.1.2 NGAP UE-TNLA-binding + +While a UE is in CM-Connected state the 5G-AN node shall maintain the same NGAP UE-TNLA-binding (i.e. use the same TNL association and same NGAP association for the UE) unless explicitly changed or released by the AMF. + +An AMF shall be able to update the NGAP UE-TNLA-binding (i.e. change the TNL association for the UE) in CM-CONNECTED state at any time. The NGAP UE-TNLA-binding can also be updated when a UE-specific NGAP message initiated by AMF is received via a new TNL association. + +An AMF shall be able to update the NGAP UE-TNLA-binding (i.e. change the TNL association for the UE) in response to an N2 message received from the 5G-AN by triangular redirection (e.g. by responding to the 5G-AN node using a different TNL association). + +An AMF shall be able to command the 5G-AN node to release the NGAP UE-TNLA-binding for a UE in CM-CONNECTED state while maintaining N3 (user-plane connectivity) for the UE at any time. + +#### 5.21.1.3 N2 TNL association selection + +The 5G-AN node shall consider the following factors for selecting a TNL association for the AMF for the initial N2 message e.g. N2 INITIAL UE MESSAGE: + +- Availability of candidate TNL associations. +- Weight factors of candidate TNL associations. + +The AMF may use any TNL association intended for non-UE associated signalling for initiation of the N2 Paging procedure. + +### 5.21.2 AMF Management + +#### 5.21.2.1 AMF Addition/Update + +The 5G System should support establishment of association between AMF and 5G-AN node. + +A new AMF can be added to an AMF set and association between AMF and GUAMI can be created and/or updated as follows: + +- AMF shall be able to dynamically update the NRF with the new or updated GUAMI(s) to provide mapping between GUAMI(s) and AMF information. Association between GUAMI(s) and AMF is published to NRF. In addition, to deal with planned maintenance and failure, an AMF may optionally provide backup AMF information, i.e. it act as a backup AMF if the indicated GUAMI associated AMF is unavailable. It is assumed that the backup AMF and the original AMF are in the same AMF set as they have access to the same UE context. Based on that information one GUAMI is associated with an AMF, optionally with a backup AMF used for planned removal and/or another (same or different) backup AMF used for failure. +- Upon successful update, the NRF considers the new and/or updated GUAMI(s) for providing AMF discovery results to the requester. Requester can be other CP network functions. +- The new AMF provides its GUAMI to 5G-AN and 5G-AN store this association. If the association between the same GUAMI and another AMF exists in the 5G-AN (e.g. due to AMF planned removal), the previously stored AMF is replaced by the new AMF for the corresponding GUAMI association. + +Information about new AMF should be published and available in the DNS system. It should allow 5G-AN to discover AMF and setup associations with the AMF required. N2 setup procedure should allow the possibility of AMFs within the AMF Set to advertise the same AMF Pointer and/or distinct AMF Pointer value(s) to the 5G-AN node. + +To support the legacy EPC core network entity (i.e. MME) to discover and communicate with the AMF, the information about the AMF should be published and available in the DNS system. Furthermore, GUMMEI and GUAMI encoding space should be partitioned to avoid overlapping values in order to enable MME discover an AMF without ambiguity. + +#### 5.21.2.2 AMF planned removal procedure + +##### 5.21.2.2.1 AMF planned removal procedure with UDSF deployed + +An AMF can be taken gracefully out of service as follows: + +- If an UDSF is deployed in the network, then the AMF stores the context for registered UE(s) in the UDSF. The UE context includes the AMF UE NGAP ID that is unique per AMF set. In order for the AMF planned removal procedure to work gracefully, 5G-S-TMSI shall be unique per AMF Set. If there are ongoing transactions (e.g. N1 procedure) for certain UE(s), AMF stores the UE context(s) in the UDSF upon completion of an ongoing transaction. +- The AMF deregister itself from NRF indicating due to AMF planned removal. + +NOTE 1: It is assumed that the UE contexts from the old AMF include all event subscriptions with peer CP NFs. + +NOTE 2: Before removal of AMF the overload control mechanism can be used to reduce the amount of ongoing transaction. + +An AMF identified by GUAMI(s) shall be able to notify the 5G-AN that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF. Upon receipt of the indication that an AMF(identified by GUAMI(s)) is unavailable, 5G-AN shall take the following action: + +- 5G-AN should mark this AMF as unavailable and not consider the AMF for selection for subsequent N2 transactions until 5G-AN learns that it is available (e.g. as part of discovery results or by configuration). +- During NGAP Setup procedure, the AMF may include an additional indicator that the AMF will rebind or release the NGAP UE-TNLA-binding on a per UE-basis for UE(s) in CM-CONNECTED state. If that indicator is included and the 5G-AN supports timer mechanism, the 5G-AN starts a timer to control the release of NGAP UE-TNLA-binding. For the duration of the timer or until the AMF releases or re-binds the NGAP UE-TNLA-binding the AN does not select a new AMF for subsequent UE transactions. Upon timer expiry, the 5G-AN releases the NGAP UE UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s), for subsequent N2 message, the 5G-AN should select a different AMF from the same AMF set when the subsequent N2 message needs to be sent. + +NOTE 3: For UE(s) in CM-CONNECTED state, after indicating that the AMF is unavailable for processing UE transactions and including an indicator that the AMF releases the NGAP UE-TNLA-binding(s) on a per UE-basis, the AMF can either trigger a re-binding of the NGAP UE associations to an available TNLA on a different AMF in the same AMF set or use the NGAP UE-TNLA-binding per UE release procedure defined in TS 23.502 [3] to release the NGAP UE-TNLA-binding on a per UE-basis while requesting the AN to maintain N3 (user plane connectivity) and UE context information. + +NOTE 4: The support and the use of timer mechanism in 5G-AN is up to implementation. + +- If the instruction does not include the indicator, for UE(s) in CM-CONNECTED state, 5G-AN considers this as a request to release the NGAP UE-TNLA-binding with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and UE context information. For subsequent N2 message, the 5G-AN should select a different AMF from the same AMF set when the subsequent N2 message needs to be sent. +- For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI pointing to an AMF that is marked unavailable, the 5G-AN should select a different AMF from the same AMF set and forward the initial NAS message. If the 5G-AN can't select an AMF from the same AMF set, the 5G-AN selects another new AMF as described in clause 6.3.5. + +An AMF identified by GUAMI(s) shall be able to instruct other peer CP NFs, subscribed to receive such a notification, that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF. If the CP NFs register with NRF for AMF unavailable notification, then the NRF shall be able to notify the subscribed NFs to receive such a notification that AMF identified by GUAMI(s) will be unavailable for processing transactions. Upon receipt of the notification that an AMF (GUAMI(s)) is unavailable, the other CP NFs shall take the following actions: + +- CP NF should mark this AMF (identified by GUAMI(s)) as unavailable and not consider the AMF for selection for subsequent MT transactions until the CP NF learns that it is available (e.g. as part of NF discovery results or via NF status notification from NRF). + +- Mark this AMF as unavailable while not changing the status of UE(s) associated to this AMF (UE(s) previously served by the corresponding AMF still remain registered in the network), and AMF Set information. +- For the UE(s) that were associated to the corresponding AMF, when the peer CP NF needs to initiate a transaction towards the AMF that is marked unavailable, CP NF should select another AMF from the same AMF set (as in clause 6.3.5) and forward the transaction together with the old GUAMI. The new AMF retrieves UE context from the UDSF. If CP NF needs to send a notification to new AMF which is associated with a subscription from the old AMF, the CP NF shall exchange the old AMF information embedded in the Notification Address with the new AMF information, and use that Notification Address for subsequent communication. + +NOTE 5: If the CP NF does not subscribe to receive AMF unavailable notification (either directly from the AMF or via NRF), the CP NF may attempt forwarding the transaction towards the old AMF and detect that the AMF is unavailable after certain number of attempts. When it detects unavailable, it marks the AMF and its associated GUAMI(s) as unavailable. CP NF should select another AMF from the same AMF set (as in clause 6.3.5) and forward the transaction together with the old GUAMI. The new AMF retrieves UE context from the UDSF and process the transaction. + +Following actions should be performed by the newly selected AMF: + +- When there is a transaction with the UE the newly selected AMF retrieves the UE context from the UDSF based on SUPI, 5G-GUTI or AMF UE NGAP ID and processes the UE message accordingly and updates the 5G-GUTI towards the UE, if necessary. For UE(s) in CM-CONNECTED state, it may also update the NGAP UE association with a new AMF UE NGAP ID towards the 5G-AN and replace the GUAMI in the UE context stored at the 5G-AN with the new GUAMI associated with the newly selected AMF if the 5G-GUTI has been updated. The AMF also informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI). +- When there is a transaction with the UE, the new selected AMF updates the peer NFs (that subscribed to receive AMF unavailability notification from old AMF), with the new selected AMF information. +- If the new AMF is aware of a different AMF serving the UE (by implementation specific means) it forwards the uplink N2 signalling of the UE to that AMF directly if necessary, the 5G-AN shall be able to receive the message from a different AMF, or it rejects the transaction from the peer CP NFs with a cause to indicate that new AMF has been selected, the peer CP NFs resend the transaction to the new AMF. + +NOTE 6: This bullet above addresses situations where 5G-AN node selects an AMF and CP NFs select another AMF for the UE concurrently. It also addresses the situation where CP NFs select an AMF for the UE concurrently + +- If the UE is in CM-IDLE state and the new AMF does not have access to the UE context, the new AMF selects one available AMF from the old AMF set as described in clause 6.3.5. The selected AMF retrieves the UE context from the UDSF and provides the UE context to the new AMF. If the new AMF doesn't receive the UE context then the AMF may force the UE to perform Initial Registration. + +##### 5.21.2.2.2 AMF planned removal procedure without UDSF + +An AMF can be taken graciously out of service as follows: + +- The AMF can forward registered UE contexts, UE contexts grouped by the same GUAMI value, to target AMF(s) within the same AMF set, including the source AMF name used for redirecting UE's MT transaction. The UE context includes the per AMF Set unique AMF UE NGAP ID. In order for the AMF planned removal procedure to work graciously, 5G-S-TMSI shall be unique per AMF set. If there are ongoing transactions (e.g. N1 procedure) for certain UE(s), AMF forwards the UE context(s) to the target AMF upon completion of an ongoing transaction. +- The AMF deregister itself from NRF indicating due to AMF planned removal. + +NOTE 1: It is assumed that the UE contexts from the old AMF include all event subscriptions with peer CP NFs. + +NOTE 2: Before removal of AMF the overload control mechanism can be used to reduce the amount of ongoing transaction. + +An AMF shall be able to instruct the 5G-AN that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF and its corresponding target AMF(s). The target AMF shall be able to update the 5G-AN that the UE(s) served by the old GUAMI(s) are now served by target AMF. The target AMF provides the old GUAMI value that the 5G-AN can use to locate UE contexts served by the old AMF. Upon receipt of the indication that an old AMF is unavailable, 5G-AN shall take the following action: + +- 5G-AN should mark this AMF as unavailable and not consider the AMF for selection for subsequent N2 transactions until 5G-AN learns that it is available (e.g. as part of discovery results or by configuration). The associated GUAMIs are marked as unavailable. +- During NGAP Setup, the AMF may include an additional indicator that the AMF will rebind or release the NGAP UE-TNLA-binding on per UE-basis. If that indicator is included and the 5G-AN supports timer mechanism, the 5G-AN starts a timer to control the release of NGAP UE-TNLA-binding(s). For the duration of the timer or until the AMF releases or re-binds the NGAP UE-TNLA-binding, the AN does not select a new AMF for subsequent transactions. Upon timer expiry, the 5G-AN releases the NGAP UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s), for subsequent N2 message, the 5G-AN uses GUAMI which points to the target AMF that replaced the old unavailable AMF, to forward the N2 message to the corresponding target AMF(s). + +NOTE 3: For UE(s) in CM-CONNECTED state, after indicating that the AMF is unavailable for processing UE transactions and including an indicator that the AMF releases the NGAP UE-TNLA-binding on a per UE-basis, the AMF can either trigger a re-binding of the NGAP UE associations to an available TNLA on a different AMF within the same AMF set or use the NGAP UE-TNLA-binding per UE release procedure defined in TS 23.502 [3] to release the NGAP UE-TNLA-binding on a per UE-basis while requesting the AN to maintain N3 (user plane connectivity) and UE context information. + +NOTE 4: The support and the use of timer mechanism in 5G-AN is up to implementation. + +If the instruction does not include the indicator, for UE(s) in CM-CONNECTED state, 5G-AN considers this as a request to release the NGAP UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and UE context information. For subsequent N2 message, the 5G-AN uses GUAMI based resolution which points to the target AMF that replaced the old unavailable AMF, to forward the N2 message to the corresponding target AMF(s). + +- For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI, based resolution the 5G-AN uses 5G S-TMSI or GUAMI which points to the target AMF that has replaced the old unavailable AMF and, the 5G-AN forwards N2 message. + +An AMF shall be able to instruct other peer CP NFs, subscribed to receive such a notification, that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF and its corresponding target AMF(s). The target AMF shall update the CP NF that the old GUAMI(s) is now served by target AMF. The old AMF provides the old GUAMI value to target AMF and the target AMF can use to locate UE contexts served by the old AMF. If the CP NFs register with NRF for AMF unavailable notification, then the NRF shall be able to notify the subscribed NFs to receive such a notification (along with the corresponding target AMF(s)) that AMF identified by GUAMI(s) will be unavailable for processing transactions. Upon receipt of the notification that an AMF is unavailable, the other CP NFs shall take the following action: + +- Mark this AMF and its associated GUAMI(s) as unavailable while not changing the status of UE(s) associated to this AMF (UE(s) previously served by the corresponding AMF still remain registered in the network), and AMF Set information. +- For the UE(s) that were associated to the corresponding AMF, when the peer CP NF needs to initiate a transaction towards the AMF that is marked unavailable and the old unavailable AMF was replaced by the target AMF, CP NF should forward the transaction together with the old GUAMI to the target AMF(s). If CP NF needs to send a notification to new AMF which is associated with a subscription from the old AMF, the CP NF shall exchange the old AMF information embedded in the Notification Address with the new AMF information, and use that Notification Address for subsequent communication. + +NOTE 5: If the CP NF does not subscribe to receive AMF unavailable notification (either directly with the AMF or via NRF), the CP NF may attempt forwarding the transaction towards the old AMF and detect that the AMF is unavailable after certain number of attempts. When it detects unavailable, it marks the AMF and its associated GUAMI(s) as unavailable. + +The following actions should be performed by the target AMF: + +- To allow AMF process ongoing transactions for some UE(s) even after it notifies unavailable status to the target AMF, the target AMF keeps the association of the old GUAMI(s) and the old AMF for a configured time. During that configured period, if target AMF receives the transaction from the peer CP NFs and cannot locate UE context, it rejects the transaction with old AMF name based on that association, and the indicated AMF is only used for the ongoing transaction. The peer CP NFs resend the transaction to the indicated AMF only for the ongoing transaction. For subsequent transactions, peer CP NFs should use the target AMF. When the timer is expired, the target AMF deletes that association information. +- When there is a transaction with the UE the target AMF uses SUPI, 5G-GUTI or AMF UE NGAP ID to locate UE contexts and processes the UE transactions accordingly and updates the 5G-GUTI towards the UE, if necessary. For UE(s) in CM-CONNECTED state, it may also update the NGAP UE association with a new AMF UE NGAP ID towards the 5G-AN and replace the GUAMI in the UE context stored at the 5G-AN with the new GUAMI associated with the newly selected AMF if the 5G-GUTI has been updated. The AMF also informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI). +- Target AMF shall not use old GUAMI to allocate 5G-GUTI for UE(s) that are being served by Target AMF. + +#### 5.21.2.3 Procedure for AMF Auto-recovery + +In order to try and handle AMF failure in a graceful manner (i.e. without impacting the UE), AMF can either back up the UE contexts in UDSF, or per GUAMI granularity in other AMFs (serving as backup AMF for the indicated GUAMI). + +NOTE 1: Frequency of backup is left to implementation. + +For deployments without UDSF, for each GUAMI the backup AMF information (in association to the GUAMI) is configured in the AMF. The AMF sends this information to 5G-AN and other CP NFs during the N2 setup procedure or the first (per NF) interaction with other CP NFs. + +In the case that an AMF fails and the 5G-AN/peer CP NFs detect that the AMF has failed, or the 5G-AN/peer CP NFs receives notification from another AMF in the same AMF set that this AMF has failed, following actions are taken: + +- The OAM deregister the AMF from NRF indicating due to AMF failure. +- 5G-AN marks this AMF as failed and not consider the AMF for selection until explicitly notified. +- For UE(s) in CM-CONNECTED state, 5G-AN considers failure detection or failure notification as a trigger to release the NGAP UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and other UE context information. For subsequent N2 message, if the backup AMF information of the corresponding failed AMF is not available the 5G-AN should select a different AMF (as in clause 6.3.5) from the same AMF set when the subsequent N2 message needs to be sent for the UE(s). If no other AMF from the AMF set is available, then it can select an AMF (implementation dependent) from the same AMF Region as in clause 6.3.5. If backup AMF information of the corresponding failed AMF is available, the 5G-AN forwards the N2 message to the backup AMF. + +NOTE 2: One AMF in the AMF set may be configured to send this failure notification message. + +- For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a S-TMSI or GUAMI pointing to an AMF that is marked failed, if the backup AMF information of the corresponding failed AMF is not available the 5G-AN should select a different AMF from the same AMF set and forward the initial NAS message. If no other AMF from the AMF set is available, then it can select an AMF (implementation dependent) from the same AMF Region as in clause 6.3.5. If backup AMF information of the corresponding failed AMF is available, the 5G-AN forwards the N2 message to the backup AMF. +- Peer CP NFs consider this AMF as unavailable while retaining the UE context. +- For the UE(s) that were associated to the corresponding AMF, when the peer CP NF needs to initiate a transaction towards the AMF, if backup AMF information of the corresponding failed AMF is not available, CP NF should select another AMF from the same AMF set and forward the transaction together with the old GUAMI. If neither the backup AMF nor any other AMF from the AMF set is available, then CP NF can select an AMF from the same AMF Region as in clause 6.3.5. If backup AMF information of the corresponding failed + +AMF is available, the CP NF forwards transaction to the backup AMF. If CP NF needs to send a notification to new AMF which is associated with a subscription from the old AMF, the CP NF shall exchange the old AMF information embedded in the Notification Address with the new AMF information, and use that Notification Address for subsequent communication. + +- When the 5G-AN or CP NFs need to select a different AMF from the same AMF set, + - For deployments with UDSF, any AMF from the same AMF set can be selected. + - For deployments without UDSF, the backup AMF is determined based on the GUAMI of the failed AMF. + +Following actions should be taken by the newly selected AMF: + +- For deployments with UDSF, when there is a transaction with the UE the newly selected AMF retrieves the UE context from the UDSF using SUPI, 5G-GUTI or AMF UE NGAP ID and it processes the UE message accordingly and updates the 5G-GUTI towards the UE, if necessary. +- For deployments without UDSF, backup AMF (the newly selected AMF), based on the failure detection of the old AMF, instructs peer CP NFs and 5G-AN that the UE contexts corresponding to the GUAMI of the failed AMF is now served by this newly selected AMF. The backup AMF shall not use old GUAMI to allocate 5G-GUTI for UE(s) that are being served by Target AMF. The backup AMF uses the GUAMI to locate the respective UE Context(s). +- When there is a transaction with the UE, the new AMF updates the peer NFs (that subscribed to receive AMF unavailability notification from old AMF) with the new AMF information. +- If the new AMF is aware of a different AMF serving the UE (by implementation specific means) it redirects the uplink N2 signalling to that AMF, or reject the transaction from the peer CP NFs with a cause to indicate that new AMF has been selected. The peer CP NFs may wait for the update from the new AMF and resend the transaction to the new AMF. + +NOTE 3: This bullet above addresses situations where 5G-AN node selects an AMF and other CP NFs select an AMF for the UE concurrently. It also addresses the situation where CP NFs select an AMF for the UE concurrently. + +NOTE 4: It is assumed that the UE contexts from the old AMF include all event subscriptions with peer CP NFs. + +- If the UE is in CM-IDLE state and the new AMF does not have access to the UE context, the new AMF selects one available AMF from the old AMF set as described in clause 6.3.5. The selected AMF retrieves the UE context from the UDSF and provides the UE context to the new AMF. If the new AMF doesn't receive the UE context then the AMF may force the UE to perform Initial Registration. +- If the UE is in CM-CONNECTED state, the new AMF may also update the NGAP UE association with a new AMF UE NGAP ID towards the 5G-AN and replace the GUAMI in the UE context stored at the 5G-AN with the new GUAMI associated with the newly selected AMF if the 5G-GUTI has been updated. + +NOTE 5: The above N2 TNL association selection and AMF management is applied to the selected PLMN. + +### 5.21.3 Network Reliability support with Sets + +#### 5.21.3.1 General + +A Network Function instance can be deployed such that several network function instances are present within an NF Set to provide distribution, redundancy and scalability together as a Set of NF instances. The same is also supported for NF Services. This can be achieved when the equivalent NFs and NF Services share the same context data or by Network Function/NF Service Context Transfer procedures as specified in clause 4.26 of TS 23.502 [3]. + +NOTE: A NF can be replaced by an alternative NF within the same NF Set in the case of scenarios such as failure, load balancing, load re-balancing. + +Such a network reliability design shall work in both communication modes, i.e. Direct Communication and Indirect Communication. In the Direct Communication mode, the NF Service consumer is involved in the reliability related procedures. In Indirect Communication mode, the SCP is involved in the reliability related procedures. + +#### 5.21.3.2 NF Set and NF Service Set + +Equivalent Control Plane NFs may be grouped into NF Sets, e.g. several SMF instances are grouped into an SMF Set. NFs within a NF Set are interchangeable because they share the same context data, and may be deployed in different locations, e.g. different data centres. + +In the case of SMF, multiple instances of SMFs within an SMF Set need to be connected to the same UPF: + +- If the N4 association is established between a SMF instance and an UPF, each N4 association is only managed by the related SMF instance. +- If only one N4 association is established between a SMF Set and an UPF, any SMF in the SMF Set should be able to manage the N4 association with the UPF. + +Furthermore, for a given UE and PDU Session any SMF in the SMF Set should be able to control the N4 session with the UPF (however, at any given time, only one SMF in the SMF Set will control the UPF for a given UE's PDU Session). + +A Control Plane NF is composed of one or multiple NF Services. Within a NF a NF service may have multiple instances. These multiple NF Service instances can be grouped into NF Service Set if they are interchangeable with each other because they share the same context data. + +NOTE: The actual mapping of instances to a given Set is up to deployment. + +#### 5.21.3.3 Reliability of NF instances within the same NF Set + +The NF producer instance is the NF instance which host the NF Service Producer. When the NF producer instance is not available, another NF producer instance within the same NF Set is selected. + +For Direct Communication mode, the NF Service consumer may subscribe to status change notifications of NF instance from the NRF. If the NF Service consumer is notified by the NRF or detects by itself (e.g. request is not responded) that the NF producer instance is not available anymore, another available NF producer instance within the same NF Set is selected by the NF Service consumer. + +For Indirect Communication mode, the SCP or NF Service consumer may subscribe to status change notifications of NF instance from the NRF and selects another NF producer instance within the same NF Set if the original NF producer instance serving the UE is not available anymore. + +NOTE: It is up to the implementation on how the SCP knows a NF producer instance is not available anymore. + +#### 5.21.3.4 Reliability of NF Services + +When multiple NF Service instances within a NF Service Set are exposed to the NF Service consumer or SCP and the failure of NF Service instance is detected or notified by the NRF, i.e. it is not available anymore, the NF Service consumer or SCP selects another NF Service instance of the same NF Service Set within the NF instance, if available. Otherwise the NF Service consumer or SCP selects a different NF instance within the same NF Set. + +NOTE: The NF Producer instance can change the NF Service instance in the response to the service request. + +When multiple NF Service instances within a NF Service Set are exposed to the NF Service consumer or SCP as a single NF Service, the reliability, i.e. the selection of an alternative NF Service instance is handled within the NF instance. + +### 5.21.4 Network Function/NF Service Context Transfer + +#### 5.21.4.1 General + +Network Function/NF Service Context Transfer Procedures allow transfer of Service Context of a NF/NF Service from a Source NF/NF Service Instance to the Target NF/NF Service Instance e.g. before the Source NF/NF Service can gracefully close its NF/NF Service. Service Context Transfer procedures are supported as specified in clause 4.26 of TS 23.502 [3]. + +Source NF / OA&M system determines when Source NF needs to transfer UE contexts to an NF in another NF set. Source NF should initiate this only for UE(s) that are not active in order to limit and avoid impacting services offered to corresponding UE(s). + +## 5.22 System Enablers for priority mechanism + +### 5.22.1 General + +The 5GS and the 5G QoS model allow classification and differentiation of specific services such as listed in clause 5.16, based on subscription-related and invocation-related priority mechanisms. These mechanisms provide abilities such as invoking, modifying, maintaining, and releasing QoS Flows with priority, and delivering QoS Flow packets according to the QoS characteristics under network congestion conditions. + +Subscription-related Priority Mechanisms include the ability to prioritize flows based on subscription information, including the prioritization of RRC Connection Establishment based on Unified Access Control mechanisms and the establishment of prioritized QoS Flows. + +Invocation-related Priority Mechanisms include the ability for the service layer to request/invoke the activation of prioritized QoS Flows through an interaction over Rx/N5 and packet detection in the UPF. + +QoS Mechanisms applied to established QoS Flows include the ability to fulfil the QoS characteristics of QoS Flows through preservation of differentiated treatment for prioritized QoS Flow and resource distribution prioritization. + +Messages associated with priority services that are exchanged over service-based interfaces may include a Message Priority header to indicate priority information, as specified in TS 23.502 [3] and TS 29.500 [49]. + +In addition, the separation of concerns between the service classification provided by the core network through the association of Service Data Flows to QoS, and the enforcing of QoS differentiation in (R)AN through the association of QoS Flows to Data Radio bearers, supports the prioritization of QoS Flows when a limitation of the available data radio bearers occurs. + +In addition, it also includes the ability for the service layer to provide instructions on how to perform pre-emption of media flows with the same priority assigned through an interaction over Rx as defined in TS 23.503 [45]. + +### 5.22.2 Subscription-related Priority Mechanisms + +Subscription-related mechanisms which are always applied: + +- **(R)AN:** During initial Access Network Connection Establishment, the Establishment Cause is set to indicate that special treatment is to be applied by the (R)AN in the radio resource allocation as specified in clause 5.2 for 3GPP access. +- **UDM:** As defined in clause 5.2.3 of TS 23.502 [3], the UE subscription data in the UDM contains an MPS subscription indication (i.e. MPS priority) and an MCX subscription indication (i.e. MCX priority) for the UE that has subscription to MPS and MCX, respectively. The MPS priority and the MCX priority, if available, are provided to the AMF via the Registration or the UE Configuration Update procedure as defined in clause 4.2 of TS 23.502 [3]. +- **AMF:** Following Access Network Connection Establishment, the receipt of the designated Establishment Cause (i.e. high priority access) by the AMF will result in priority handling of the "Initial UE Message" received as part of the Registration procedures of clause 4.2.2 of TS 23.502 [3]. If the AMF did not receive a designated Establishment Cause (i.e. high priority access), but when the AMF determines that there is a MPS priority (or MCX priority) in the UDM for that UE, the AMF shall provide priority handling for that UE at that time and shall provide the MPS priority (or MCX priority) to the UE via the Registration or the UE Configuration Update procedure, as defined in clause 4.2 of TS 23.502 [3]. In addition, certain exemptions to Control Plane Congestion and Overload Control are provided as specified in clause 5.19. + +Subscription-related mechanisms which are conditionally applied: + +- **UE:** When barring control parameters are broadcast by the RAN, access barring based on Access Identity(es) configured in the USIM and/or an Access Category is applied prior to an initial upstream transmission for the UE which provides a mechanism to limit transmissions from UEs categorized as non-prioritized, while allowing + +transmissions from UEs categorized as prioritized (such as MPS subscribed UEs), during the RRC Connection Establishment procedure as specified in clause 5.2. + +- **UDM:** One or more ARP priority levels are assigned for prioritized or critical services. The ARP of the prioritized QoS Flows for each DN is set to an appropriate ARP priority level. The 5QI is from the standard value range as specified in clause 5.7.2.7. In addition, Priority Level may be configured for the standardized 5QIs, and if configured, it overwrites the default value specified in the QoS characteristics Table 5.7.4-1. +- **PCF:** The "IMS Signalling Priority" information is set for the subscriber in the UDM, and the PCF modifies the ARP of the QoS Flow used for IMS signalling, for each DN which supports prioritized services leveraging on IMS signalling, to an appropriate ARP priority level assigned for that service. + +### 5.22.3 Invocation-related Priority Mechanisms + +The generic mechanisms used based on invocation-related Priority Mechanisms for prioritised services are based an interaction with an Application Function and between the Application Function and the PCF over Rx/N5 interface. + +These mechanisms apply to mobile originated as well as mobile terminated SIP call/sessions (clause 5.21 of TS 23.228 [15]) and Priority PDU connectivity services including MPS for Data Transport Service. + +NOTE 1: Clause 5.21 of TS 23.228 [15] is applicable to 5GS, with the understanding that the term PCRF corresponds to PCF in the 5GS. + +Invocation-related mechanisms for Mobile Originations e.g. via SIP/IMS: + +- PCF: When an indication for a session arrives over the Rx/N5 Interface and the UE does not have priority for the signalling QoS Flow, the PCF derives the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, of the QoS Flow for Signalling as per Service Provider policy as specified in clause 6.1.3.11 of TS 23.503 [45]. +- PCF: For sessions such as MPS, when establishing or modifying a QoS Flow for media as part of the session origination procedure, the PCF selects the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, to provide priority treatment to the QoS Flow(s). +- PCF: When all active sessions to a particular DN are released, and the UE is not configured for priority treatment to that particular PDU Session for a DN, the PCF will downgrade the IMS Signalling QoS Flows from appropriate settings of the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, to those entitled by the UE based on subscription. + +Invocation-related mechanisms for Mobile Terminations e.g. via SIP/IMS: + +- PCF: When an indication for a session arrives over the Rx/N5 Interface, mechanisms as described above for Mobile Originations are applied. +- UPF: If an IP packet arrives at the UPF for a UE that is CM-IDLE, the UPF sends a "Data Notification" including the information to identify the QoS Flow for the DL data packet to the SMF, as specified in clause 4.2.3.3 of TS 23.502 [3]. +- SMF: If a "Data Notification" message arrives at the SMF for a QoS Flow associated with an ARP priority level value that is entitled for priority use, delivery of priority indication during the Paging procedure is provided by inclusion of the ARP in the N11 interface "N1N2MessageTransfer" message, as specified in clause 4.2.3.3 of TS 23.502 [3]. +- AMF: If an "N1N2MessageTransfer" message arrives at the AMF containing an ARP priority level value that is entitled for priority use, the AMF handles the request with priority and includes the "Paging Priority" IE in the N2 "Paging" message set to a value assigned to indicate that there is an IP packet at the UPF entitled to priority treatment, as specified in clause 4.2.3.3 of TS 23.502 [3]. +- SMF: For a UE that is not configured for priority treatment, upon receiving the "N7 Session Management Policy Modification" message from the PCF with an ARP priority level that is entitled for priority use, the SMF sends an "N1N2MessageTransfer" to update the ARP for the Signalling QoS Flows, as specified in clause 4.3.3.2 of TS 23.502 [3]. + +- AMF: Upon receiving the "N1N2MessageTransfer" message from the SMF with an ARP priority level that is entitled for priority use, the AMF updates the ARP for the Signalling QoS Flows, as specified in clause 4.3.3.2 of TS 23.502 [3]. +- (R)AN: Inclusion of the "Paging Priority" in the N2 "Paging" message triggers priority handling of paging in times of congestion at the (R)AN as specified in clause 4.2.3.3 of TS 23.502 [3]. + +Invocation-related mechanisms for the Priority PDU connectivity services: + +- PCF: If the state of the Priority PDU connectivity services is modified from disabled to enabled, the QoS Flow(s) controlled by the Priority PDU connectivity services are established/modified to have the service appropriate settings of the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, using the PDU Session Modification procedure as specified in clause 4.3.3 of TS 23.502 [3]. +- PCF: If the state of Priority PDU connectivity services is modified from enabled to disabled, the QoS Flow(s) controlled by the Priority PDU connectivity services are modified from Priority PDU connectivity service appropriate settings of the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, to those entitled by the UE as per subscription, using the PDU Session Modification procedure as specified in clause 4.3.3 of TS 23.502 [3]. + +Invocation-related mechanisms for MPS for Data Transport Service: + +- MPS for Data Transport Service follows the same steps as those for Priority PDU connectivity services. The QoS Flows that will be subject to MPS for Data Transport Service are based on operator policy and regulations by means of local PCF configuration. + +NOTE 2: If no configuration is provided, MPS for Data Transport Service applies to the QoS Flow associated with the default QoS rule. + +### 5.22.4 QoS Mechanisms applied to established QoS Flows + +Mechanisms applied to established QoS Flows: + +- (R)AN: QoS Flows requested in the Xn "Handover Request" or N2 "Handover Request" which are marked as entitled to priority by virtue of inclusion of an ARP value from the set allocated by the Service Provider for prioritised services are given priority over requests for QoS Flows which do not include an ARP from the set as specified in clause 4.9 of TS 23.502 [3]. +- SMF: Congestion management procedures in the SMF will provide priority to QoS Flows established for sessions during periods of extreme overload. Prioritised services are exempt from any session management congestion controls. See clause 5.19. +- AMF: Congestion management procedures in the AMF will provide priority to any Mobility Management procedures required for the prioritised services during periods of extreme overload. Prioritised services are exempt from any Mobility Management congestion controls. See clause 5.19.5. +- QoS Flows whose ARP parameter is from the set allocated by the Service Provider for prioritised services' use shall be exempt from release during QoS Flow load rebalancing. +- (R)AN, UPF: IMS Signalling Packets associated with prioritised services' use are handled with priority. Specifically, during times of severe congestion when it is necessary to drop packets on the IMS Signalling QoS Flow, or QoS Flow supporting MPS for Data Transport Service signalling, to ensure network stability, these FEs shall drop packets not associated with priority signalling such as MPS or Mission Critical services before packets associated with priority signalling. See clauses 5.16.5 and 5.16.6. +- (R)AN, UPF: During times of severe congestion when it is necessary to drop packets on a media QoS Flow to ensure network stability, these FEs shall drop packets not associated with priority sessions such as MPS or Mission Critical services before packets associated with priority sessions. See clauses 5.16.5 and 5.16.6. + +## 5.23 Supporting for Asynchronous Type Communication + +Asynchronous type communication (ATC) enables 5GC to delay synchronizing UE context with the UE, so as to achieve an efficient signalling overhead and increase system capacity. The support of ATC is optional for the AMF. + +5GC supports asynchronous type communication with the following functionality: + +- Capability to store the UE context based on the received message, and synchronize the UE context with the involved network functions or UE later; + +For network function (e.g. PCF, UDM, etc.) triggered signalling procedure (e.g. network triggered Service Request procedure, network triggered PDU Session Modification procedure, etc.), if the UE CM state in the AMF is CM-IDLE state and the requesting network function indicates to the AMF the ATC is allowed for the signalling, if the AMF supports the ATC feature, the AMF may update and store the UE context based on the received message without paging UE immediately. When the UE CM state in the AMF enters CM-CONNECTED state, the AMF forwards N1 and N2 message to synchronize the UE context with the (R)AN and/or the UE. + +If the originating NF does not require immediate delivery, it may indicate that the AMF is allowed to use ATC. + +NOTE: Pre-Rel-17 AMF implementation cannot decode the indication that ATC is allowed. + +## 5.24 3GPP PS Data Off + +This feature, when activated by the user, prevents traffic via 3GPP access of all IP packets, Unstructured and Ethernet data except for those related to 3GPP PS Data Off Exempt Services. The 3GPP PS Data Off Exempt Services are a set of operator services, defined in TS 22.011 [25] and TS 23.221 [23], that are the only allowed services when the 3GPP PS Data Off feature has been activated by the user. The 5GC shall support 3GPP PS Data Off operation in both non-roaming and roaming scenarios. + +UEs may be configured with up to two lists of 3GPP PS Data Off Exempt Services and the list(s) are provided to the UEs by HPLMN via Device Management or UICC provisioning. When the UE is configured with two lists, one list is valid for the UEs camping in the home PLMN and the other list is valid for any VPLMN the UE is roaming in. When the UE is configured with a single list, without an indication to which PLMNs the list is applicable, then this list is valid for the home PLMN and any PLMN the UE is roaming in. + +NOTE 1: The operator needs to ensure coordinated list(s) of 3GPP Data Off Exempt Services provisioned in the UE and configured in the network. + +The UE reports its 3GPP PS Data Off status in PCO (Protocol Configuration Option) to (H-)SMF during UE requested PDU Session Establishment procedure for establishment of a PDU Session associated with 3GPP access and/or non-3GPP access. The UE does not need to report PS Data Off status during the PDU Session Establishment procedure for handover of the PDU Session between 3GPP access and non 3GPP access if 3GPP PS Data Off status is not changed since the last report. The PS Data Off status for a PDU Session does not affect data transfer over non-3GPP access. + +If 3GPP PS Data Off is activated, the UE prevents the sending of uplink IP packets, Unstructured and Ethernet data except for those related to 3GPP PS Data Off Exempt Services, based on the pre-configured list(s) of Data Off Exempt Services. + +If 3GPP PS Data Off is activated for a UE with MA PDU Sessions established through the ATSSS feature (see clause 5.32), the data transferred over the non-3GPP access of the MA PDU sessions are unaffected, which is ensured by the policy for ATSSS Control as specified in clause 5.32.3. + +The UE shall immediately report a change of its 3GPP PS Data Off status in PCO by using UE requested PDU Session Modification procedure. This also applies to the scenario of inter-RAT mobility to NG-RAN and to scenarios where the 3GPP PS Data Off status is changed when the session management back-off timer is running as specified in clause 5.19.7.3 and clause 5.19.7.4. For UEs in Non-Allowed Area (or not in Allowed Area) as specified in clause 5.3.4.1, the UE shall also immediately report a change of its 3GPP PS Data Off status for the PDU Session. For UEs moving out of LADN area and the PDU Session is still maintained as specified in clause 5.6.5, the UE shall also immediately report a change of its 3GPP PS Data Off status for the PDU Session. + +The additional behaviour of the SMF for 3GPP PS Data Off is controlled by local configuration or policy from the PCF as defined in TS 23.503 [45]. + +NOTE 2: For the PDU Session used for IMS services, the 3GPP Data Off Exempt Services are enforced in the IMS domain as specified TS 23.228 [15]. Policies configured in the (H-)SMF/PCF need to ensure those services are always allowed when the 3GPP Data Off status of the UE is set to "activated". + +## 5.25 Support of OAM Features + +### 5.25.1 Support of Tracing: Signalling Based Activation/Deactivation of Tracing + +5GS supports tracing as described in TS 32.421 [66]. 5GS support may include subscriber tracing (tracing targeting a SUPI) or equipment tracing (tracing targeting a PEI) but also other forms of tracing further described in TS 32.421 [66]. + +NOTE 1: TS 23.501 / TS 23.502 [3] / TS 23.503 [45] only describe how 5GS signalling supports delivery of Trace Requirements about a UE (Signalling Based Activation/Deactivation of Tracing). OAM delivery of tracing requirements as well as the transfer of tracing results to one or more Operations Systems are out of scope of these documents. + +The content of Trace Requirements about a UE (e.g. trace reference, address of the Trace Collection Entity, etc.) is defined in TS 32.421 [66]. + +Trace Requirements about a UE may be configured in subscription data of the UE and delivered together with other subscription data by the UDM towards the AMF, the SMF and/or the SMSF. + +The AMF propagates Trace Requirements about a UE received from the UDM to network entities not retrieving subscription information from UDM, i.e. to the 5G-AN, to the AUSF and to the PCF. The AMF also propagates Trace Requirements to the SMF and to the SMSF. If the I-SMF or V-SMF is needed for the PDU session, the AMF propagates Trace Requirements to the I-SMF or V-SMF. The I-SMF or V-SMF also propagates Trace Requirements received from the AMF to the I-UPF or V-UPF (over N4). + +Trace Requirements about a UE may be sent by the AMF to the 5G-AN as part of: + +- the N2 procedures used to move the UE from CM-IDLE to CM-CONNECTED or, +- the N2 procedures to request a Hand-over from a target NG-RAN or, +- a stand-alone dedicated N2 procedure when tracing is activated while the UE is CM-CONNECTED. + +Trace Requirements about a UE sent to a 5G-AN shall not contain information on the SUPI or on the PEI of the UE. Trace Requirements are directly sent from Source to Target NG-RAN in the case of Xn Hand-Over. + +The SMF propagates Trace Requirements about a UE received from the UDM to the UPF (over N4) and to the PCF. The SMF provides Trace Requirements to the PCF when it has selected a different PCF than the one received from the AMF. + +Once the SMF or the SMSF has received subscription data, Trace Requirements received from UDM supersede Trace requirements received from the AMF. Trace Requirements are exchanged on N26 between the AMF and the MME. + +### 5.25.2 Support of OAM-based 5G VN group management + +5GS supports 5G LAN-type service as defined in clause 5.29. 5G LAN-type service includes the 5G VN group management that can be configured by a network administrator. + +The parameters for 5G VN group is defined in clause 5.29. + +The 5G VN group parameters about a UE may be configured in subscription data of the UE and delivered together with other subscription data by the UDM towards the AMF and SMF. + +## 5.26 Configuration Transfer Procedure + +The purpose of the Configuration Transfer is to enable the transfer of information between two RAN nodes at any time via NG interface and the Core Network. An example of application is to exchange the RAN node's IP addresses in order to be able to use Xn interface between the NG-RAN node for Self-Optimised Networks (SON), as specified in TS 38.413 [34]. + +### 5.26.1 Architecture Principles for Configuration Transfer + +Configuration Transfer between two RAN node provides a generic mechanism for the exchange of information between applications belonging to the RAN nodes. + +In order to make the information transparent for the Core Network, the information is included in a transparent container that includes source and target RAN node addresses, which allows the Core Network nodes to route the messages. The mechanism is depicted in figure 5.26 1. + +![Figure 5.26-1: inter NG-RAN Configuration Transfer basic network architecture diagram showing signaling between NG-RAN and AMF nodes.](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +``` + +graph TD + subgraph "Source Side" + RAN1[NG-RAN] + AMF1[AMF] + end + + subgraph "Destination Side" + RAN2[NG-RAN] + AMF2[AMF] + end + + RAN1 -- "N2" --> AMF1 + AMF1 -. "Configuration Transfer Signaling" .-> RAN1 + + AMF1 -- "N14" --> AMF2 + AMF1 -. "Relaying Configuration Transfer Signaling" .-> AMF2 + + RAN2 -- "N2" --> AMF2 + RAN2 -. "Configuration Transfer Signaling" .-> AMF2 + +``` + +The diagram illustrates the signaling flow for configuration transfer. It is divided by a thick horizontal line. Above the line, an NG-RAN node is connected to an AMF via an N2 interface; a dashed arrow labeled "Configuration Transfer Signaling" points from the AMF to the NG-RAN. Below the line, another NG-RAN node is connected to another AMF via an N2 interface; a dashed arrow labeled "Configuration Transfer Signaling" points from the NG-RAN to the AMF. The two AMFs are connected vertically by an N14 interface, with a dashed arrow labeled "Relaying Configuration Transfer Signaling" pointing from the top AMF to the bottom AMF. Labels "NG-RAN" appear to the left of the horizontal divider. + +Figure 5.26-1: inter NG-RAN Configuration Transfer basic network architecture diagram showing signaling between NG-RAN and AMF nodes. + +**Figure 5.26-1: inter NG-RAN Configuration Transfer basic network architecture** + +The NG-RAN transparent containers are transferred from the source NG-RAN node to the destination NG-RAN node by use of Configuration Transfer messages. + +A Configuration Transfer message is used from the NG-RAN node to the AMF over N2 interface, a AMF Configuration Transfer message is used from the AMF to the NG-RAN over N2 interface, and a Configuration Transfer Tunnel message is used to tunnel the transparent container from a source AMF to a target AMF over the N14 interface. + +Each Configuration Transfer message carrying the transparent container is routed and relayed independently by the core network node(s). + +### 5.26.2 Addressing, routing and relaying + +#### 5.26.2.1 Addressing + +All the Configuration Transfer messages contain the addresses of the source and destination RAN nodes. An NG-RAN node is addressed by the Target NG-RAN node identifier. + +#### 5.26.2.2      Routing + +The following description applies to all the Configuration Transfer messages used for the exchange of the transparent container. + +The source RAN node sends a message to its core network node including the source and destination addresses. The AMF uses the destination address to route the message to the correct AMF via the N14 interface. + +The AMF connected to the destination RAN node decides which RAN node to send the message to, based on the destination address. + +#### 5.26.2.3 Relaying + +The AMF performs relaying between N2 and N14 messages as described in TS 38.413 [34], TS 29.518 [71]. + +## 5.27 Enablers for Time Sensitive Communications, Time Synchronization and Deterministic Networking + +### 5.27.0 General + +This clause describes 5G System features that can be used independently or in combination to enable time-sensitive communication, time synchronization and deterministic networking: + +- Delay-critical GBR; +- A hold and forward mechanism to schedule traffic as defined in IEEE Std 802.1Q [98] for Ethernet PDU Sessions in DS-TT and NW-TT (see clause 5.27.4) to de-jitter flows that have traversed the 5G System if the 5G System is to participate transparently as a bridge in a TSN network; +- TSC Assistance Information: describes TSC flow traffic characteristics as described in clause 5.27.2 that may be provided optionally for use by the gNB, to allow more efficiently schedule radio resources for periodic traffic and applies to PDU Session type Ethernet and IP. +- Time Synchronization: describes how 5GS can operate as a PTP Relay (IEEE Std 802.1AS [104]), as a Boundary Clock or as Transparent Clock (IEEE Std 1588 [126]) for PDU Session type Ethernet and IP and how 5GS can detect and report the status of the time synchronization. +- RAN feedback for BAT offset and adjusted periodicity describes a mechanism supported by NG-RAN and 5G CN that enables AF to adapt to received BAT offset and adjusted periodicity from NG-RAN for a given traffic flow. + +The 5G System integration as a bridge in an IEEE 802.1 TSN network as described in clause 5.28 can make use of all features listed above. + +To support any of the above features to enable time-sensitive communication, time synchronization and deterministic networking, during the PDU Session establishment, the UE shall request to establish a PDU Session as an always-on PDU Session, and the PDU Sessions are established as Always-on PDU session as described in clause 5.6.13. In this release of the specification, to use any of the above features to enable time-sensitive communication, time synchronization and deterministic networking: + +- Home Routed PDU Sessions are not supported; +- PDU Sessions are supported only for SSC mode 1; +- Service continuity is not supported when the UE moves from 5GS to EPS .i.e. interworking with EPS is not supported for a PDU Session for time synchronization or TSC or deterministic networking. + +### 5.27.1 Time Synchronization + +#### 5.27.1.1 General + +For supporting time synchronization service, the 5GS is configured to operate in one or multiple PTP instances and to operate in one of the following modes (if supported) for each PTP instance: + +- 1) as time-aware system as described in IEEE Std 802.1AS [104], +- 2) as Boundary Clock as described in IEEE Std 1588 [126], provisioned by the profiles supported by this 3GPP specification including SMPTE Profile for Use of IEEE Std 1588 [126] Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]; + +NOTE 1: Via proper configuration of the IEEE Std 1588 [126] data set members, the 5G internal system clock can become the time source for the PTP grandmaster function for the connected networks in the case of mode 1 and mode 2. + +NOTE 2: In some cases where the 5G internal system clock is the time source for the PTP grandmaster function for the connected networks, it might not be required for the UE to receive gPTP or PTP messages over user plane. The UE and DS-TT uses the 5G timing information and generates the necessary gPTP or PTP message for the end station, if needed (this is implementation specific). + +3) as peer-to-peer Transparent Clock as described in IEEE Std 1588 [126], provisioned by the profiles supported by this 3GPP specification including SMPTE Profile for Use of IEEE Std 1588 Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]; or + +4) as end-to-end Transparent Clock as described in IEEE Std 1588 [126], provisioned by the profiles supported by this 3GPP specification including SMPTE Profile for Use of IEEE Std 1588 Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]. + +NOTE 3: When the GM is external, the operation of 5GS as Boundary Clock assumes that profiles that are supported by the 5GS allows the exemption specified in clauses 9.5.9 and 9.5.10 of IEEE Std 1588 [126] where the originTimestamp (or preciseOriginTimestamp in case of two-step operation) is not required to be updated with the syncEventEgressTimestamp (and a Local PTP Clock locked to the external GM). As described in clause 5.27.1.2.2, only correctionField is updated with the 5GS residence time and link delay, in a similar operation as specified by IEEE Std 802.1AS [104]. + +The configuration of the time synchronization service in 5GS for option 1 by TSN AF and CNC is described in clause 5.28.3, and for options 1-4 by AF/NEF and TSCTSF in clause 5.27.1.8 and clause 5.28.3. + +The 5GS shall be modelled as an IEEE Std 802.1AS [104] or IEEE Std 1588 [126] compliant entity based on the above configuration. + +NOTE 4: This release of the specification does not support the PTP management mechanism or PTP management messages as described in clause 15 in IEEE Std 1588 [126]. + +The DS-TT and NW-TT at the edge of the 5G system may support the IEEE Std 802.1AS [104] or other IEEE Std 1588 [126] profiles' operations respective to the configured mode of operation. The UE, gNB, UPF, NW-TT and DS-TTs are synchronized with the 5G GM (i.e. the 5G internal system clock) which shall serve to keep these network elements synchronized. The TTs located at the edge of 5G system fulfil some functions related to IEEE Std 802.1AS [104] and may fulfil some functions related to IEEE Std 1588 [126], e.g. (g)PTP support and timestamping. Figure 5.27.1-1 illustrates the 5G and PTP grandmaster (GM) clock distribution model via 5GS. + +![Diagram illustrating the 5G system modelled as a PTP instance for supporting time synchronization. The diagram shows the flow of 5GS and (g)PTP timing directions through various network elements including End Station, DS-TT, UE, gNB, PTP compatible 5G transport, UPF, NW-TT, Bridge, and External network. A legend indicates that solid arrows represent 5GS timing direction, dashed arrows represent (g)PTP timing direction, and clock icons represent 5GS and (g)PTP time synchronization. A note at the bottom states that the 5G system can be considered as an 802.1AS time-aware system or IEEE 1588 Boundary or Transparent Clock.](981668c6be5792b778cccb1af38477e2_img.jpg) + +The diagram illustrates the 5G system modelled as a PTP instance for supporting time synchronization. It shows the flow of 5GS and (g)PTP timing directions through various network elements. A legend indicates that solid arrows represent 5GS timing direction, dashed arrows represent (g)PTP timing direction, and clock icons represent 5GS and (g)PTP time synchronization. A note at the bottom states that the 5G system can be considered as an 802.1AS time-aware system or IEEE 1588 Boundary or Transparent Clock. + +Diagram illustrating the 5G system modelled as a PTP instance for supporting time synchronization. The diagram shows the flow of 5GS and (g)PTP timing directions through various network elements including End Station, DS-TT, UE, gNB, PTP compatible 5G transport, UPF, NW-TT, Bridge, and External network. A legend indicates that solid arrows represent 5GS timing direction, dashed arrows represent (g)PTP timing direction, and clock icons represent 5GS and (g)PTP time synchronization. A note at the bottom states that the 5G system can be considered as an 802.1AS time-aware system or IEEE 1588 Boundary or Transparent Clock. + +**Figure 5.27.1-1: 5G system is modelled as PTP instance for supporting time synchronization** + +Figure 5.27.1-1 depicts the two synchronizations systems considered: the 5G Clock synchronization and the (g)PTP domain synchronization. + +- 5G Access Stratum-based Time Distribution: Used for NG RAN synchronization and also distributed to the UE. The 5G Access Stratum-based Time Distribution over the radio interface towards the UE is specified in TS 38.331 [28]. This method may be used to either further distribute the 5G timing to devices connected to a UE (using implementation-specific means) or to support the operation of the (g)PTP-based time distribution method. + +- (g)PTP-based Time Distribution: Provides timing among entities in a (g)PTP domain. This process follows the applicable profiles of IEEE Std 802.1AS [104] or IEEE Std 1588 [126]. This method relies on the 5G access stratum-based time distribution method to synchronize the UE/DS-TT and on the 5GS time synchronization to synchronize the gNB (which, in turn, may synchronize the DS-TT) and the NW-TT. + +The gNB needs to be synchronized to the 5G GM clock. + +The 5GS supports two methods for determining the grandmaster PTP Instance and the time-synchronization spanning tree. + +- Method a), BMCA procedure. +- Method b), local configuration. + +This is further described in clause 5.27.1.6. + +#### 5.27.1.2 Distribution of timing information + +##### 5.27.1.2.1 Distribution of 5G internal system clock + +The 5G internal system clock shall be made available to all user plane nodes in the 5G system. The UPF and NW-TT may get the 5G internal system clock via the underlying PTP compatible transport network with mechanisms outside the scope of 3GPP. The 5G internal system clock shall be made available to UE with signalling of time information related to absolute timing of radio frames as described in TS 38.331 [28]. The 5G internal system clock shall be made available to DS-TT by the UE. + +##### 5.27.1.2.2 Distribution of grandmaster clock and time-stamping + +###### 5.27.1.2.2.1 Distribution of gPTP Sync and Follow\_Up messages + +The mechanisms for distribution of TSN GM clock and time-stamping described in this clause are according to IEEE Std 802.1AS [104]. + +NOTE 1: It means Externally-observable behaviour of the 5GS bridge needs to comply with IEEE Std 802.1AS [104]. + +For downlink Time Synchronization, upon reception of a downlink gPTP message from NW-TT port in Follower state, the NW-TT makes an ingress timestamping (TSi) for each gPTP event (Sync) message and uses the cumulative rateRatio received inside the gPTP message payload (carried within Sync message for one-step operation or Follow\_up message for two-step operation) to calculate the link delay from the upstream TSN node (gPTP entity connected to NW-TT) expressed in TSN GM time as specified in IEEE Std 802.1AS [104]. NW-TT then calculates the new cumulative rateRatio (i.e. the cumulative rateRatio of the 5GS) as specified in IEEE Std 802.1AS [104] and modifies the gPTP message payload (carried within Sync message for one-step operation or Follow\_up message for two-step operation) as follows: + +- Adds the link delay from the upstream TSN node in TSN GM time to the correction field. +- Replaces the cumulative rateRatio received from the upstream TSN node with the new cumulative rateRatio. +- Adds TSi in the Suffix field of the gPTP packet as described in clause H.2. + +The UPF/NW-TT uses the ingress port number of the NW-TT, and domainNumber and sdoId in the received gPTP message to assign the gPTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then forwards the gPTP message from TSN network to the PTP ports in DS-TT(s) in Leader state within this PTP instance via PDU sessions terminating in this UPF that the UEs have established to the TSN network. The UPF/NW-TT also forwards the gPTP message to the PTP ports in NW-TT in Leader state within this PTP instance. All gPTP messages are transmitted on a QoS Flow that complies with the residence time upper bound requirement specified in IEEE Std 802.1AS [104]. + +NOTE 2: Leader and Follower terms in this specification maps to Master and Slave terms respectively for (g)PTP time synchronization as specified in IEEE Std 802.1AS [104] and IEEE Std 1588 [126]. This terminology can require update depending on the IEEE 1588 WG response to SA WG2. + +NOTE 3: The sum of the UE-DS-TT residence time and the PDB of the QoS Flow needs to be lower than the residence time upper bound requirement for a time-aware system specified in IEEE Std 802.1AS [104] in the following cases: + +- a) If the PTP port in DS-TT is in Follower state and a PTP port in the NW-TT is in Leader state; or +- b) a PTP port in DS-TT is in Leader state and a PTP port in NW-TT is in Follower state. + +NOTE 4: If the PTP port in DS-TT is in a Follower state, and a PTP port in another DS-TT is in Leader state, then the sum of the residence time for these two DS-TT ports and the PDB of the QoS flow of the two PDU Sessions needs to be lower than the residence time upper bound requirement for a time-aware system specified in IEEE Std 802.1AS [104]. + +A UE receives the gPTP messages and forwards them to the DS-TT. The DS-TT then creates egress timestamping (TSe) for the gPTP event (Sync) messages for external TSN working domains. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this gPTP message expressed in 5GS time. The DS-TT then uses the rateRatio contained inside the gPTP message payload (carried within Sync message for one-step operation or Follow\_up message for two-step operation) to convert the residence time spent within the 5GS in TSN GM time and modifies the payload of the gPTP message that it sends towards the downstream TSN node (gPTP entity connected to DS-TT) as follows: + +- Adds the calculated residence time expressed in TSN GM time to the correction field. +- Removes Suffix field that contains TSi. + +If the ingress DS-TT has indicated support of the IEEE Std 802.1AS [104] PTP profile as described in clause K.2.1 and the network has configured a PTP instance with the IEEE Std 802.1AS [104] PTP profile for the ingress DS-TT, the ingress DS-TT performs the following operations for received UL gPTP messages for the PTP instance: + +- Adds the link delay from the upstream TSN node (gPTP entity connected to DS-TT) in TSN GM time to the correction field. +- Replaces the cumulative rateRatio received from the upstream TSN node (gPTP entity connected to DS-TT) with the new cumulative rateRatio. +- Adds TSi in the Suffix field of the gPTP packet. + +The UE transparently forwards the gPTP message from DS-TT to the UPF/NW-TT. If the ingress DS-TT port is in Passive state, the UPF/NW-TT discards the gPTP messages. If the ingress DS-TT port is in Follower state, the UPF/NW-TT forwards the gPTP messages as follows: + +- In the case of synchronizing end stations behind NW-TT, the egress port is in UPF/NW-TT. For the received UL gPTP messages, the egress UPF/NW-TT performs the following actions: + - Adds the calculated residence time expressed in TSN GM to the correction field. + - Removes Suffix field that contains TSi. +- In the case of synchronizing TSN end stations behind DS-TT, the egress TT is DS-TT of the other UE, and the UPF/NW-TT uses the port number of the ingress DS-TT, and domainNumber and sdoId in the received gPTP message to assign the gPTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then forwards the received UL gPTP message to the PTP ports in DS-TT(s) in Leader state within this PTP instance. The egress DS-TT performs same actions as egress UPF/NW-TT in previous case. + +###### 5.27.1.2.2.2 Distribution of PTP Sync and Follow\_Up messages + +This clause applies if DS-TT and NW-TT support distribution of PTP Sync and Follow\_Up messages. PTP support by DS-TT and NW-TT may be determined as described in clause K.2.1. + +The mechanisms for distribution of PTP GM clock and time-stamping described in this clause are according to IEEE Std 1588 [126] for Transparent clock and for the case of Boundary clock when the GM is external, where the originTimestamp (or preciseOriginTimestamp) is not updated by the 5GS as described by the exemption in clause 5.27.1.1. If the 5GS acts as the GM with a PTP instance type Boundary clock, then the 5GS updates the + +originTimestamp (or preciseOriginTimestamp in case of two-step operation) with the 5GS internal clock, as described in clause 5.27.1.7. + +NOTE 1: This means externally-observable behaviour of the PTP instance in 5GS needs to comply with IEEE Std 1588 [126]. + +Upon reception of a PTP event message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for each PTP event (i.e. Sync) message. + +The PTP port in the ingress TT measures the link delay from the upstream PTP instance as described in clause H.4. + +The PTP port in the ingress TT modifies the PTP message payload (carried within Sync message for one-step operation or Follow\_Up message for two-step operation) as follows: + +- (if the PTP port in the ingress TT has measured the link delay) Adds the measured link delay from the upstream PTP instance in PTP GM time to the correction field. +- (if the PTP port in the ingress TT has measured the link delay and rateRatio is used) Replaces the cumulative rateRatio received from the upstream PTP instance with the new cumulative rateRatio. +- Adds TSi in the Suffix field of the PTP message as described in clause H.2. + +NOTE 2: If the 5GS is configured to use the Cumulative frequency transfer method for synchronizing clocks as described in clause 16.10 in IEEE Std 1588 [126], i.e. when the cumulative rateRatio is measured, then the PTP port in the ingress TT uses the cumulative rateRatio received inside the PTP message payload (carried within Sync message for one-step operation or Follow\_Up message for two-step operation) to correct the measured link delay to be expressed in PTP GM time as specified in IEEE Std 1588 [126]. The PTP port in the ingress TT then calculates the new cumulative rateRatio (i.e. the cumulative rateRatio of the 5GS) as specified in IEEE Std 1588 [126]. + +NOTE 3: If 5GS acts as an end-to-end Transparent Clock, since the end-to-end Transparent Clock does not support peer-to-peer delay mechanism, the residence time can be calculated with the residence time spent within the 5GS in 5G GM time and if needed, with a correction factor, for instance, as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126], this gives a residence time expressed in PTP GM time that is used to update the correction field of the received PTP Sync or Follow\_Up message. + +The PTP port in the ingress TT then forwards the PTP message to the UPF/NW-TT. The UPF/NW-TT further distributes the PTP message as follows: + +- If the 5GS is configured to operate as Boundary Clock as described in IEEE Std 1588 [126], the UPF/NW-TT uses the port number of the ingress DS-TT and domainNumber and sdoId in the received PTP message to assign the PTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then regenerates the Sync and Follow\_Up (for two-step operation) messages based on the received Sync and Follow\_Up messages for the PTP ports in Leader state in NW-TT and DS-TT(s) within this PTP instance. The NW-TT/UPF forwards the regenerated Sync and Follow\_Up (for two-step operation) messages to the Leader ports in NW-TT and the PDU session(s) related to the Leader ports in the DS-TT(s) within this PTP instance. +- If the 5GS is configured to operate as a Transparent Clock as described in IEEE Std 1588 [126], the UPF/NW-TT uses the port number of the ingress TT and domainNumber and sdoId in the received PTP message to assign the PTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then forwards the received Sync messages to PTP ports in DS-TT(s) within this PTP instance via corresponding PDU Sessions terminating to this UPF, and to NW-TT ports within this PTP instance, except toward the ingress PTP port in the ingress TT. + +NOTE 4: If 5GS acts as a Transparent Clock, the 5GS does not maintain the PTP port states; the ingress PTP messages received on a PTP Port are retransmitted on all other PTP Ports of the Transparent Clock subject to the rules of the underlying transport protocol. + +NOTE 5: Due to the exemption described in clause 5.27.1.1, when the PTP instance in 5GS is configured to operate as a Boundary Clock, the 5GS does not need to synchronize its Local PTP Clock to the external PTP grandmaster. The PTP instance in 5GS measures the link delay and residence time and communicates these in a correction field. The externally observable behaviour of 5GS still conforms to the specifications for a Boundary Clock as described in IEEE Std 1588 [126]. + +The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP event (i.e. Sync) messages for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. + +The PTP port in the egress TT then uses the rateRatio contained inside the PTP message payload (if available, carried within Sync message for one-step operation or Follow\_Up message for two-step operation) to convert the residence time spent within the 5GS in PTP GM time. + +The PTP port in the egress TT modifies the payload of the PTP message (Sync message for one-step operation or Follow\_Up message for two-step operation) that it sends towards the downstream PTP instance as follows: + +- Adds the calculated residence time to the correction field. +- Removes Suffix field of the PTP message that contains TSi. + +NOTE 6: If 5GS acts as an end-to-end Transparent Clock, since the end-to-end Transparent Clock does not support peer-to-peer delay mechanism, the residence time is calculated with the residence time spent within the 5GS in 5G GM time and, if needed, corrected for instance with the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126] to get it expressed in PTP GM time. The residence time is used to update the correction field of the received PTP event (e.g. Sync or Follow\_Up) message. + +#### 5.27.1.3 Support for multiple (g)PTP domains + +This clause describes support for multiple domains for gPTP and PTP and for GM clocks connected to DS-TT and NW-TT and only applies if DS-TT and NW-TT support the related functionality. PTP support and support of gPTP for GM clocks connected to DS-TT by DS-TT and NW-TT may be determined as described in clause K.2.1. + +Each (g)PTP domain sends its own (g)PTP messages. The (g)PTP message carries a specific PTP "domainNumber" that indicates the time domain they are referring to. The PTP port in ingress TT makes ingress timestamping (TSi) for the (g)PTP event messages of all domains and forwards the (g)PTP messages of all domains to the UPF/NW-TT that further distributes the (g)PTP messages to the egress TTs as specified in clause 5.27.1.2.2. + +The PTP port in the egress TT receives the original PTP GM clock timing information and the corresponding TSi via (g)PTP messages for one or more (g)PTP domains. The PTP port in the egress TT then makes egress timestamping (TSe) for the (g)PTP event messages for every (g)PTP domain. Ingress and egress time stamping are based on the 5G system clock at NW-TT and DS-TT. + +NOTE 1: An end-station can select PTP timing information of interest based on the "domainNumber" in the (g)PTP message. + +The process described in clause 5.27.1.2.2 is thus repeated for each (g)PTP domain between a DS-TT and the NW-TT it is connected to. + +NOTE 2: If all (g)PTP domains can be made synchronous and the synchronization can be provided by the 5G clock, the NW-TT or DS-TT(s) generates the (g)PTP event messages of all domains using 5G clock as described in clause 5.27.1.7. + +NOTE 3: This Release of the specification supports multiple gPTP domains as defined in IEEE Std 802.1AS [104]. If a 5GS TSN bridge supports stream gates and/or transmission gates as defined in IEEE Std 802.1Q [98], then they operate based on a single given gPTP domain. + +#### 5.27.1.4 DS-TT and NW-TT Time Synchronization functionality + +This clause describes the support of Time Synchronization functionality supported by the 5G System. Synchronization between UPF/NW-TT and NG-RAN is outside scope of 3GPP. + +DS-TT and NW-TT may support the following PTP instance types: + +- Boundary Clock as defined in IEEE Std 1588 [126] as described in clause 5.27.1.1; +- End-to-End Transparent Clock as defined in IEEE Std 1588 [126] as described in clause 5.27.1.1; +- Peer-to-Peer Transparent Clock as defined in IEEE Std 1588 [126] as described in clause 5.27.1.1; +- PTP Relay instance as defined in IEEE Std 802.1AS [104]. + +**Editor's note:** Support for external networks operating with IEEE Std 1588-2008 [107] is for further study. + +DS-TT and NW-TT may support the following transports for PTP: + +- IPv4 as defined in IEEE Std 1588 [126] Annex C; +- IPv6 as defined in IEEE Std 1588 [126] Annex D; + +IEEE Std 802.3 [131] (Ethernet) as defined in IEEE Std 1588 [126] Annex E. + +For operation as a Boundary clock or as a Transparent Clock, DS-TT and NW-TT may support the following path and link delay measurement methods: + +- Delay request-response mechanism as described in clause 11.3 of IEEE Std 1588 [126]; +- Peer-to-peer delay mechanism as defined in clause 11.4 of IEEE Std 1588 [126]. + +DS-TT and NW-TT may support acting as a PTP grandmaster, i.e. may support generating (g)PTP Announce, Sync and Follow\_Up messages. DS-TT and NW-TT supporting (g)PTP shall support one or more PTP profiles as described in clause 20.3 of IEEE Std 1588 [126], i.e.: + +- Default PTP Profiles in IEEE Std 1588 [126], Annex I; +- IEEE Std 802.1AS [104] PTP profile for transport of timing as defined in IEEE Std 802.1AS [104] Annex F; +- SMPTE Profile for Use of IEEE Std 1588 [126] Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]. + +TSN AF and TSCTSF may determine the PTP functionalities supported by DS-TT and NW-TT and may configure PTP instances in DS-TT and NW-TT using port and user plane node management information exchange as described in Annex K, clause K.2. + +**NOTE:** How the TSN AF or TSCTSF assigns NW-TT port(s) of one NW-TT to different PTP instances is up to implementation. + +#### 5.27.1.5 Detection of (g)PTP Sync and Announce timeouts + +The procedure described in this clause is applicable when the PTP instance in 5GS is configured to operate as a time-aware system or as a Boundary Clock, and the PTP grandmaster is external to the 5GS, and the BMCA procedure (Method a) is used as described in clause 5.27.1.6. + +The NW-TT processes Announce messages according to IEEE Std 1588 [126]. + +In particular, the NW-TT shall compute and maintain the time when the Announce and Sync timeout events occur for the PTP port in a Follower state. When the 5GS is configured to operate as a time-aware system, the NW-TT shall determine the Sync and Announce message interval for the PTP Port at the other end of the link to which the Follower PTP Port in 5GS is attached, as described in IEEE Std 802.1AS [104]. When the 5GS is configured to operate as a Boundary Clock, the NW-TT shall determine Announce interval based on the configuration of the Follower port in 5GS, as described in IEEE Std 1588 [126]. + +The configuration of PTP instances in DS-TT and NW-TT for Sync and Announce timeouts is described in clause K.2. Upon detection of the Sync or Announce timeout event, the NW-TT shall re-evaluate the DS-TT and NW-TT port states as described in clause 5.27.1.6. + +#### 5.27.1.6 Distribution of Announce messages and best master clock selection + +The procedure described in this clause is applicable if DS-TT and NW-TT support operating as a Boundary Clock described in IEEE Std 1588 [126] or as a time-aware system (support of the IEEE 802.1AS [104] PTP profile) and when the PTP instance in 5GS is configured to operate as a time-aware system or as a Boundary Clock. Whether DS-TT/NW-TT support operating as a Boundary Clock or as a time-aware system may be determined as described in clause K.2.1. + +The externally-observable behaviour of the Announce message handling by 5GS needs to comply with IEEE Std 802.1AS [104] or IEEE Std 1588 [126], respective to the configured mode of operation. + +The DS-TT forwards the received Announce messages to NW-TT over User plane. The NW-TT port forwards the received Announce messages from N6 interface to NW-TT. + +The NW-TT maintains the PTP port state for each DS-TT port and NW-TT port. The PTP port states may be determined by NW-TT either via: + +- Method a), BMCA procedure. +- Method b), local configuration. + +When Method b) is used, the following applies: + +- When the PTP GM is external to the 5GS, for one of the NW-TT or DS-TT ports (per each PTP domain) the PTP port state is Follower and for all other NW-TT and DS-TT ports of the same PTP domain the PTP port state is set either to Passive or Leader (depending on implementation). +- When the 5GS is configured as a grandmaster for a (g)PTP domain for the connected networks, all NW-TT ports and DS-TT ports are set to Leader state for that (g)PTP domain. + +The local configuration of PTP port states in DS-TT and NW-TT for Method b is described in clause K.2. + +When the Method a) is used (PTP port states are determined by BMCA procedure), the NW-TT needs to process the received Announce messages (from NW-TT port(s) and over user plane from the DS-TT(s)) for BMCA procedure, determine port states within the 5GS, and maintain the Leader-Follower hierarchy. + +The DS-TT maintains the Disabled, Initializing and Faulty (if applicable) state for the PTP ports in DS-TT. While in Disabled, Initializing or Faulty state, the port in the DS-TT discards any (g)PTP messages it may receive from the upstream PTP instance or from the NW-TT via user plane. + +When the 5GS Clock is determined as a grandmaster for a (g)PTP domain, the Announce messages are distributed as described in clause 5.27.1.7. + +When the grandmaster is external to the 5GS, the NW-TT regenerates the Announce messages based on the Announce messages received from Follower port in NW-TT or DS-TT for the Leader ports in NW-TT and DS-TT(s). The NW-TT/UPF forwards the regenerated Announce messages to the PDU session(s) related to the Leader ports in the DS-TT(s). + +NOTE 1: The TSN AF or TSCTSF can use the portDS.portState in the "Time synchronization information for each DS-TT port" element in UMIC to read and get notified for the port state changes for the PTP ports in DS-TT(s), and the portDS.portState in PMIC to read and get notified for the port state changes for the PTP ports in NW-TT. Based on the change of the port states, TSN AF or TSCTSF can determine that an external Grandmaster PTP Instance is found to be used instead of the GM in 5GS, or the GM in 5GS is selected as the Grandmaster PTP Instance, and TSN AF or TSCTSF can disable or enable the (g)PTP grandmaster functionality in DS-TT(s), respectively. + +NOTE 2: The TSN AF or TSCTSF can use the portDS.portState in PMIC to read and get notified for the port state changes for the PTP ports in DS-TT for the port state Disabled, Initializing or Faulty (if applicable). The TSCTSF or TSN AF can use the portDS.portEnable to indicate to the NW-TT that the DS-TT port is disabled. This avoids unnecessary (g)PTP traffic over User Plane to a DS-TT port in Disabled, Initializing or Faulty state. + +#### 5.27.1.7 Support for PTP grandmaster function in 5GS + +The 5GS that is configured to operate as a time-aware system or Boundary Clock may support acting as a PTP grandmaster for a (g)PTP domain. + +The configuration of PTP instances in DS-TT and NW-TT for PTP grandmaster function is described in clause K.2. + +The following options may be supported (per DS-TT) for the 5GS to generate the Sync, Follow\_Up and Announce messages for the Leader ports on the DS-TT: + +- a) NW-TT generates the Sync, Follow\_Up and Announce messages on behalf of DS-TT (e.g. if DS-TT does not support this). + +The NW-TT/UPF forwards the generated Sync, Follow\_Up and Announce messages to the PDU session(s) related to the Leader ports on the DS-TT(s). The NW-TT timestamps the (g)PTP event message when the event message is sent to the PDU Session, and adds TSi corresponding to the timestamp to the Sync message and the OriginTimestamp corresponding to the timestamp to Sync message (if one-step operation is used) or PreciseOriginTimestamp corresponding to the timestamp to Follow\_Up message (if two-step operation is used), and sets the cumulative rateRatio value with 1. The OriginTimestamp or PreciseOriginTimestamp shall be set by NW-TT/UPF to the 5GS internal clock. + +When DS-TT(s) receive the Sync, Follow\_Up messages, it modifies the payload of the Sync, Follow\_Up message as described for the PTP port in the egress TT in clause 5.27.1.2.2.2. + +- b) DS-TT generates the Sync, Follow\_Up and Announce messages in this DS-TT. The OriginTimestamp or PreciseOriginTimestamp shall be set by DS-TT to the 5GS internal clock. + +In both options, the NW-TT generates the Sync, Follow\_Up and Announce messages for the Leader ports on the NW-TT. + +#### 5.27.1.8 Exposure of Time Synchronization + +5G System supports time synchronization service that can be activated and deactivated by AF. Exposure of time synchronization comprises the following capabilities: + +- The AF may learn 5GS and/or UE availability and capabilities for time synchronization service. +- The AF controls activation and deactivation of the time synchronization service for the target UE(s). +- The AF may subscribe to time synchronization service status for the target UE(s). + +The AF may use the service-specific parameters to control the time synchronization service for targeted UE(s). These parameters are specified in clause 4.15.9.3 and 4.15.9.4 of TS 23.502 [3] for (g)PTP-based and 5G access stratum-based time synchronization services, respectively. + +The AF may subscribe for 5GS and/or UE availability and capabilities for time synchronization service. The AF indicates in the request the DNN, S-NSSAI, and in addition the AF may indicate a list of UE identities or group identity to limit the subscription only to corresponding UEs. If the AF does not indicate DNN, S-NSSAI, the NEF determines the DNN, S-NSSAI based on the AF Identifier. + +The TSCTSF (directly or via NEF) exposes the 5GS and/or UE availability and capabilities for synchronization service to the AF as described in clause 4.15.9.2 of TS 23.502 [3]. The exposed information includes the list of user plane node identities, the list of UE identities and may include the supported capabilities for (g)PTP time synchronization service per user plane node and UE. + +The AF request to control the (g)PTP time synchronization service is sent to the TSCTSF (directly or via NEF). The request is targeted to a set of AF-sessions that are associated with the exposure of UE availability and capabilities for synchronization service. + +The AF may request to use a specific PTP instance type when requesting the (g)PTP-based time synchronization distribution method (IEEE Std 1588 [126] or IEEE Std 802.1AS [104] operation (i.e. as a Boundary Clock, peer-to-peer Transparent Clock, or end-to-end Transparent Clock or as a PTP relay instance)). The request to control the (g)PTP time synchronization service may contain other service parameters as specified in Table 4.15.9.3-1 in clause 4.15.9.3 of TS 23.502 [3]. + +The AF may request to use the 5G access stratum as a time synchronization distribution method. In this case, the time source is provided by the 5GS. 5G-AN provides the 5GS time to the UE via 3GPP radio access; UE/DS-TT may provide 5G access stratum timing information to end stations using implementation specific means. The request to control the 5G access stratum time distribution (including the parameters such AF requests may contain) is described in clause 4.15.9.4 of TS 23.502 [3]. + +The AF or NEF selects the TSCTSF as specified in clause 6.3.24. + +The AF request may include a time synchronization error budget (see also clause 5.27.1.9). The time synchronization error budget defines an upper bound for time synchronization errors introduced by 5GS. + +The AF uses the procedure for configuring the (g)PTP instance in 5GS as described in clause 4.15.9.3 of TS 23.502 [3] and uses the procedure for providing the 5G access stratum time distribution as described in clause 4.15.9.4 of TS 23.502 [3] for the UEs. + +The TSCTSF uses the Time Synchronization parameters (Table 4.15.9.3-1 in TS 23.502 [3]) as received from the AF (directly or via NEF) to control the (g)PTP time synchronization service. When IEEE Std 1588 [126] or IEEE Std 802.1AS [104] operation have been selected, the TSCTSF determines the necessary (g)PTP parameters to activate and control the service in DS-TT(s) and NW-TTs. For this purpose, the TSCTSF uses the PMIC or UMIC to manage the IEEE Std 1588 [126] or IEEE Std 802.1AS [104] operation in the DS-TT(s) or NW-TTs, respectively (see clause 5.27.1.4). + +The TSCTSF may indicate whether it can support the service or not as per the requested acceptance criteria (e.g. based on the known timing synchronization status attribute thresholds also pre-configured at gNB) and provide notification when there is a service status update if the AF subscribes to service status updates (see also clause 5.27.1.12). + +The TSCTSF uses the Time Synchronization parameters (Table 4.15.9.4-1 of TS 23.502 [3]) as received from the AF (directly or via NEF) to control the 5G access stratum time synchronization distribution as described in clause 4.15.9.4 of TS 23.502 [3]. + +For handling (g)PTP traffic, the PCF, according to PCC rule authorization, chooses a 5QI and dynamically set the PDB and/or MDBV according to requirements for (g)PTP protocol. The PCF provides the SMF with a PCC rule generated based on the AF request to control the (g)PTP time synchronization service. The SMF may take the information in the PCC rule to modify a PDU Session to create or modify or release a QoS Flow for transmitting the (g)PTP messages. The PCF acknowledges the policy request to the TSCTSF. The TSCTSF may report the result of the time synchronization request to the AF (directly or via NEF). + +The AF may provide a temporal validity condition to the TSCTSF (directly or via NEF) when the AF activates or modifies the time synchronization service. Temporal validity condition contains the start-time and stop-time (in absolute time value) attributes that describe the time period when the time synchronization service is active for the targeted AF sessions. The TSCTSF manages the temporal validity condition as described in clauses 4.15.9.3 and 4.15.9.4 of TS 23.502 [3]. + +The AF may provide clock quality detail level and clock quality acceptance criteria to the TSCTSF (directly or via NEF) when the AF activates or modifies the time synchronization service. For ASTI based time synchronization services, the TSCTSF provides the clock quality reporting control information to AMF (see also clause 5.27.1.12). + +The AF may provide a requested coverage area for the time synchronization service to the TSCTSF (directly or via NEF) when the AF activates or modifies the time synchronization service. The requested coverage area defines a spatial validity condition for the service using a geographical area (e.g. a civic address or shapes), or a list of Tracking Area Identities (TAIs). + +#### 5.27.1.9 Support for derivation of Uu time synchronization error budget + +The AF may request a specific time synchronization error budget when requesting a time synchronization service employing the (g)PTP-based or 5G access stratum-based time distribution method. If the AF includes a time synchronization error budget in its request, the TSCTSF uses it to derive an error budget available for the NG-RAN to provide the 5G access stratum time via the Uu interface to each targeted UE (referred to as Uu time synchronization error budget hereafter). + +The Time Synchronization Subscription data may optionally contain the authorized Uu time synchronization error budget. When the TSCTSF receives an AF request with a specific time synchronization error budget for the time synchronization service, the TSCTSF validates the Uu time synchronization error budget as described in clause 5.27.1.11. + +To derive the Uu time synchronization error budget for each targeted UE, the TSCTSF takes the following into account: + +- selected time synchronization distribution method (i.e. 5G access stratum-based time distribution or (g)PTP-based time distribution); +- Uu time synchronization error budget in the Time Synchronization Subscription data defined in clause 5.27.1.11; +- in the case of the (g)PTP-based time distribution: + - whether 5GS operates as a boundary clock and acts as a GM; + +- whether a clock connected to the DS-TT/NW-TT acts as a GM; +- PTP port states; +- a CN part and a Device part of the time synchronization error budget (both parts may be predefined at the TSCTSF, or calculated by the 5GS using the implementation-specific means). + +If the AF does not include a time synchronization error budget, the TSCTSF uses a preconfigured time synchronization error budget to derive the Uu time synchronization error budget. The TSCTSF provides a 5G access stratum time distribution indication and the derived Uu time synchronization error budget to NG-RAN as described in clause 4.15.9.4 of TS 23.502 [3]. Based on this, NG-RAN provides the 5G access stratum time to the UE according to the Uu interface time synchronization error budget as provided by the TSCTSF (if supported by UE and NG-RAN). During Handover, Service Request, mobility registration and AM policy modification procedure, the AMF may provide the 5G access stratum time distribution indication and the Uu time synchronization error budget to NG-RAN as described in clause 4.15.9.4 of TS 23.502 [3], if needed. + +NOTE: This release of the specification assumes that deployments ensure that the targeted UEs and the NG-RAN nodes serving those UEs support Rel-17 propagation delay compensation as defined in TS 38.300 [27]. + +#### 5.27.1.10 Support for coverage area filters for time synchronization service + +This feature enables the AF to request time synchronization service for a UE or a group of UEs in a specific geographical area (so called coverage area). The requested coverage area contains a list of Tracking Area (TA) or a geographical area (e.g. a civic address or shapes that the NEF transforms to list of TAs based on pre-configuration). + +TSCTSF checks with the UDM if the UE is allowed to receive the time synchronization service requested by AF. + +The coverage area defines a spatial validity condition for the targeted UE(s) that is resolved at the TSCTSF. In order to do that, the TSCTSF may either: + +- discover the AMF(s) serving the list of TA(s) that comprise the spatial validity using Nnrf\_NFDiscovery\_Request service from the NRF and subsequently, the TSCTSF subscribes to the discovered AMF(s) to receive notifications about presence of the UE in an Area of Interest events (as described in clause 5.3.4.4). The subscription is targeted to Any UE. To reduce the number of Area of Interest reports (based on presence of UE) for the discovered AMFs, the TSCTSF may provide additional filtering information (e.g. List of UE IDs, DNN(s)/S-NNSAI(s)) to limit the subscription to the indicated UE identities, or UEs having a PDU Session with the given DNN/S-NSSAI as specified in clause 5.3.4.4. +- determine the serving AMF for each of the targeted UE(s) using the UDM and subscribe to the serving AMF to receive notification about presence of the UE in an Area of Interest (as described in clause 5.3.4.4). + +An Area of Interest (AoI) for each AMF is represented by a list of TA(s), wherein the Area of Interest is identical to the requested coverage area. + +Based on the outcome provided by the AMF about the UE's presence in the AoI, the TSCTSF determines if the time synchronization service is activated or deactivated. + +For access stratum distribution activation/deactivation, the TSCTSF will enable/disable access stratum time distribution to the UE at the serving NG-RAN node reusing the procedures in clause 4.15.9.4 of TS 23.502 [3]. For (g)PTP distribution activation/deactivation, the TSCTSF will modify the PTP instance configuration by means of sending a PMIC to the impacted UE/DS-TTs and UMIC to the impacted UPF/NW-TT, as described in clause K.2.2. + +If the time synchronization service is modified based on the reports of UE presence in the Area of Interest, the TSCTSF informs the AF for the impacted UE(s) by indicating the PTP port state for the related DS-TT PTP port (in the case of (g)PTP based time distribution) or notifying the AF with the indication of 5G access status time distribution status (enabled or disabled, for ASTI based time distribution). + +If the Time Synchronization Coverage Area requested by the AF includes at least one TA that is a part of UE's Registration Area (RA), the 5GS may provide the AF-requested time synchronization service to the targeted UE within its RA, i.e. all TAs of the RA shall be treated as a Time Synchronization Coverage Area even if some of the TAs were not requested by the AF. + +NOTE 1: This ensures that (1) there is no impact on the Registration Area (RA) of UE if/when the AMF receives a time synchronization service request with a spatial validity condition (i.e. for specific geographical area); and (2) the UE can continue receiving the time synchronization service when it moves within the RA in the RRC\_IDLE state. + +NOTE 2: Since the RA can be specific to the UE, the result can be different Time Synchronization Coverage Area for different DS-TT ports of different UEs within a PTP instance. + +#### 5.27.1.11 Controlling time synchronization service based on the Subscription + +The distribution of timing information, 5G access stratum-based time distribution and (g)PTP-based time distribution, for a UE may be controlled based on subscription data stored in the UDM. The (g)PTP-based or 5G access stratum-based time synchronization service may be provided to a UE based on the UE's subscription which is specified in the TS 23.502 [3] clause 5.2.3.3.1. + +The Access and Mobility Subscription data include for the control of 5G access stratum-based time distribution the following information: + +- the Access Stratum Time Synchronization Service Authorization, which indicates whether the UE should be provisioned with 5G system internal clock timing information over access stratum as specified in TS 38.331 [28]. +- optionally, the Uu time synchronization error budget. +- optionally, one or more periods of start and stop times defining the times when the UE should be provisioned with 5G system internal clock timing information. +- optionally, a Time Synchronization Coverage Area comprising a list of TAs where the UE shall be provisioned with 5G system internal clock timing information. +- optionally, a clock quality detail level indicating whether and which clock quality information to provide to the UE. It comprises one of the following values: clock quality metrics or acceptable/not acceptable indication. +- optionally, the clock quality acceptance criteria for the UE. It may be defined based on one or more attributes listed in Table 5.27.1.12-1. + +During the Registration procedure, the AMF retrieves the subscription from UDM. If the AMF receives 5G access stratum-based time synchronization service subscription for the given UE, the AMF controls the 5G access stratum-based time distribution: + +- If the 5G access stratum-based time synchronization service is allowed for the UE, the AMF provides the 5G access stratum time distribution indication to the NG-RAN so that it can provide 5G timing information to the UE. +- The AMF may provide a Uu time synchronization error budget to the NG-RAN (as described in clause 5.27.1.9). If the UE's subscription contains a Uu time synchronization error budget, then AMF sends it to NG-RAN. Otherwise, the AMF uses the pre-configured Uu time synchronization error budget and sends it to NG-RAN. +- If the UE's subscription contains Coverage Area (defined as a list of TAs), the AMF configures the NG-RAN to provide the 5G timing information to UE only when the UE is in the Coverage Area as described in clause 5.27.1.10. +- If the AMF receives the start and stop times, then the AMF enables and disables the 5G access stratum time distribution indication to the NG-RAN according to the expiry of start and stop times if the UE is in CM-CONNECTED state. If the UE is in CM-IDLE state when a Start time condition is met, the AMF pages the UE and provides the 5G access stratum time distribution indication to NG-RAN as part of the subsequent service request procedure initiated by the UE in the response to the paging. +- If the AMF receives the clock quality detail level, then the AMF configures the NG-RAN to provide clock quality detail information reporting to UE as described in clause 5.27.1.12. The AMF may instruct the UE to reconnect to the network when the UE detects that the RAN timing synchronization status has changed while the UE is in RRC\_INACTIVE or RRC\_IDLE, as described in clause 5.27.1.12. +- If the AMF receives the same parameters both in the Access and Mobility Subscription data from UDM and in the AM Policy from PCF, the AMF shall use the value received from the AM policy. + +The Time Synchronization Subscription data is the subscription data for the control of (g)PTP-based time distribution and 5G access stratum-based time distribution and includes the following information: + +- the "AF request Authorization", indicating whether the UE is authorized for an AF-requested 5G access stratum-based time distribution and (g)PTP-based time distribution services. The indication is provided separately for each service: + - "allowed" or "not allowed" for (g)PTP based time synchronization service (per DNN/S-NSSAI and UE identity), + - "allowed" or "not allowed" for ASTI based time synchronization services (per UE identity). +- If the "AF request Authorization" is set to "allowed", the Time Synchronization Subscription data may contain additional information for (g)PTP/ASTI based time synchronization services authorized by: + - optionally, a list of TA(s) which specifies an area (a so-called Authorized Time Synchronization Coverage Area) in which an AF may request time synchronization services; + - optionally, one or more periods of authorized start and stop times, which indicates the allowed time period during which an AF may request time synchronization services; + - optionally, authorized Uu time synchronization error budget, which indicates the limit the AF may request. +- one or more Subscribed time synchronization service ID(s), each containing the DNN/S-NSSAI and a reference to a PTP instance configuration pre-configured at the TSCTSF (e.g. PTP profile, PTP domain, etc.): + - optionally, for each PTP instance configuration, one or more periods of start and stop times defining active times of time synchronization service for the PTP instance. + - optionally, for each PTP instance configuration, a Time Synchronization Coverage Area defining a list of TAs where the (g)PTP-based time synchronization is available for the UEs in the PTP instance. + - optionally, for each PTP instance configuration, Uu time synchronization error budget. + +The TSCTSF retrieves the Time Synchronization Subscription data from UDM. If the TSCTSF receives the Time Synchronization Subscription data for a UE, the TSCTSF controls the Time Synchronization Service including (g)PTP-based time distribution and 5G access stratum-based time distribution: + +- The TSCTSF retrieves the Time Synchronization Subscription data from the UDM when the TSCTSF receives an AF request for the time synchronization service (either ASTI or (g)PTP). According to the "AF request Authorization" in the UE's Time Synchronization Subscription data, the TSCTSF determines whether the UE is authorized for an AF-requested time synchronization service: + - If the UE's Time Synchronization Subscription data contains an Authorized Time Synchronization Coverage Area (i.e. a list of TA(s) defining the restricted area for AF request), TSCTSF checks whether the AF requested Coverage Area satisfies the authorized area: If the requested Coverage Area (see clause 5.27.1.10) is within the Authorized Time Synchronization Coverage Area, the TSCTSF uses the requested Coverage Area. If the Authorized Time Synchronization Coverage Area is inside of the requested Coverage Area, the TSCTSF uses the Authorized Time Synchronization Coverage Area. If the requested Coverage Area partly overlaps with the Authorized Time Synchronization Coverage Area, the TSCTSF uses the intersection of them. If there is no overlap between them, the TSCTSF shall reject the AF request. +- If the AF requested Coverage Area satisfies the authorized area totally or partly, TSCTSF notifies to AF with the Time Synchronization Service information based on the Authorized Time Synchronization Coverage Area. TSCTSF subscribes to UE's presence in the Area of Interest at the discovered AMF(s), if the UE(s) moves out of the AF requested coverage area, the TSCTSF shall disable Time Synchronization Service and notifies to AF. +- If the UE's Time Synchronization Subscription data contains authorized Uu time synchronization error budget, the TSCTSF checks whether the Uu time synchronization error budget derived from AF request satisfies (i.e. equal or larger than) the authorized Uu time synchronization error budget. +- If the UE's Time Synchronization Subscription data contains periods of authorized start and stop times, the TSCTSF checks whether the AF requested temporal validity condition satisfies (i.e. within) any of the + +periods of authorized start and stop times. If such period is found, the TSCTSF uses the start and stop times of the AF request. + +- If the AF request is authorized, the TSCTSF proceeds as specified in clause 5.27.1.8 and in TS 23.502 [3]. Otherwise, the TSCTSF rejects the AF request. +- The TSCTSF retrieves the Time Synchronization Subscription data from the UDM when it receives notification from the PCF that a UE has established a PDU Session that is potentially impacted by (g)PTP-based time synchronization service: + - The TSCTSF retrieves the PTP instance configurations referenced from the "Subscribed time synchronization service ID(s)". The PTP instance configurations are stored locally in the TSCTSF. The TSCTSF determines if one or more of the PTP instance configurations match with the DNN/S-NSSAI of the given PDU Session. If no PTP instance exists for the given PTP instance configuration, the TSCTSF initializes the PTP instance in 5GS as described in clause K.2.2. +- The TSCTSF configures a PTP port in DS-TT and adds it to the corresponding PTP instance in NW-TT as described in clause K.2.2. +- If the PTP instance configuration referenced by UE's Time Synchronization Subscription data contains an Uu time synchronization error budget, then the TSCTSF uses it to derive an Uu time synchronization error budget available for the NG-RAN to provide the 5G access stratum time for the UE as specified in clause 5.27.1.9. +- If the PTP instance configuration referenced by the Time Synchronization Subscription data for the UE contains start and stop times, the TSCTSF, upon expiry of start time, creates the PTP instance and adds the PTP port in DS-TT to the PTP instance. Upon expiry of stop time, if this is the last period of start and stop times in the PTP instance configuration, the TSCTSF deletes the PTP instance, otherwise the TSCTSF temporarily disables the PTP instance. +- If the PTP instance configuration referenced by the Time Synchronization Subscription data for the UE contains a Time Synchronization Coverage Area, the TSCTSF subscribes to UE's Presence in Area(s) of Interest corresponding to the Time Synchronization Coverage Area at the discovered AMF(s). When the TSCTSF determines that the UE has moved inside or outside of the Time Synchronization Coverage Area, the TSCTSF adds or temporarily removes the PTP port in DS-TT from the corresponding PTP instance. + +#### 5.27.1.12 Support for network timing synchronization status monitoring + +While the time synchronization service is offered by the 5GS, based on 5G access stratum-based time distribution or (g)PTP-based time distribution, the network timing synchronization status of the nodes involved in the operation (e.g. gNBs and/or UPF/NW-TTs) may change. gNBs and UPF/NW-TT can detect timing synchronization degradation or improvement locally. The support for network timing synchronization status monitoring enables the 5GS to modify time synchronization service for a UE or a group of UEs depending on the current synchronization status and notify service updates. There may be three consumers of this information: + +- TSCTSF may receive node-level information about timing synchronization status from gNB and/or UPF/NW-TT directly from OAM or alternatively, if supported by a node, using control plane signalling at node level. Node level signalling uses UMIC for UPF/NW-TT case and an AMF service to report N2 node level information for the gNB case. In the latter case, the AMF controls the gNB node level reporting and subscription using NGAP messages (see TS 38.413 [34]). +- AF may subscribe to time synchronization status notifications for a UE or group of UEs for which the AF requests or has requested time synchronization service (for 5G access stratum time distribution or (g)PTP services). +- For 5G access stratum time synchronization service, the UE may receive clock quality information from the gNB based on UE subscription data stored in the UDM (see clause 5.27.1.11) or AF request for clock quality reporting to the UE. + +When activating time synchronization for a UE, TSCTSF forwards the clock quality detail level (if available) to the AMF (via PCF using AM policy). The AMF instructs the UE to transition to the RRC\_CONNECTED state in the case when the UE later detects that the gNB timing synchronization status has changed while the UE is in the RRC\_INACTIVE or RRC\_IDLE state. When the UE wants to access the 5GS, the UE shall perform Unified Access Control as defined in TS 38.331 [28]. + +gNBs may be pre-configured with thresholds for each Timing Synchronization Status (TSS) attribute, if supported, that is described in Table 5.27.1.12-1. + +gNBs may include a reference report ID in SIB information, if supported. A reference report ID consists of a scope of the TSS and an Event ID. A scope of the TSS supports providing TSS information for all cells or a group of cells within a single gNB. Event ID is an integer indicating that the gNB's clock quality has changed, resulting in at least one TSS attribute exceeding or meeting again the pre-configured threshold. Uniqueness of Event ID value is ensured by combining it with a gNB ID as specified in TS 38.300 [27]. When the network TSS attribute exceeds the thresholds (i.e. status degradation), or the network TSS attribute meets the thresholds again (i.e. status improvement), the gNB notifies the TSCTSF (either using N2 node level signalling via AMF, or via OAM) with the scope of the timing synchronization status (i.e. gNB ID or a list of Cell IDs within a single gNB) and the corresponding network timing synchronization status attributes as described in Table 5.27.1.12-1. The gNB indicates the status change to the UEs via the reference report ID change in SIB information: + +- When the network timing synchronization status exceeds any of the pre-configured thresholds (i.e. status degradation) or meets the threshold again (i.e. status improvement), the gNB changes the reference report ID in SIB information. Either event serves as a notification for the UEs reading the SIB information that there is new TSS information available. + +NOTE 1: NG-RAN is assumed not to provide clock quality metrics better than the pre-configured threshold, i.e. if a clock quality metric is better than the corresponding threshold, the NG-RAN reports the threshold value to the UE in an RRC message instead. + +NOTE 2: It is assumed the pre-configured thresholds in the gNB(s) are sufficient to meet UE time sync performance requirement which are configured by the operator. + +- If supported, the UE in the RRC\_INACTIVE or RRC\_IDLE state compares the reference report ID in SIB information with its locally stored reference report ID to determine whether it has the latest available clock quality information already or it needs to transit to the RRC\_CONNECTED state to retrieve it. +- If the UE is instructed by AMF (via the Registration procedure, or the UE Configuration Update procedure) to reconnect to the network in the case when the UE determines that the reference report ID has changed, the UE in the RRC\_INACTIVE or RRC\_IDLE state, if supported by the UE, reconnects to the network. RAN may delay or prioritize UE's transition to the RRC\_CONNECTED state using the UAC framework [28], i.e. UEs are not expected to transition to the RRC\_CONNECTED state immediately after determining that the clock quality information has changed and receiving instructions from the AMF. After the UE has reconnected to the network, the gNB uses unicast RRC signalling to provision the clock quality information to the UEs. + +The network timing synchronization status information from gNB or UPF/NW-TT to the TSCTSF may contain the following information as described in the Table 5.27.1.12-1. The details for gNB timing synchronization status information are specified in TS 38.413 [34]. However, it is up to gNB to determine whether to provide its timing synchronization status reporting and which of the information elements to include in the TSS report to the TSCTSF, i.e. based on the implementation gNB may report all, some, or none of the information elements from Table 5.27.1.12-1. + +**Table 5.27.1.12-1: Information elements that gNB or UPF/NW-TT timing synchronization status information may contain (all optional)** + +| Information Name | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Synchronization state | Indicates the state of the node synchronization, represented by the values "Locked", "Holdover", or "Freerun" (NOTE 1). | +| Clock quality | | +| >> Traceable to GNSS | Indicates whether the current time source is traceable to the GNSS and represented by values "Yes" or "No". | +| >> Traceable to UTC | Indicates whether the current time source is traceable to the UTC and represented by values "Yes" or "No". | +| >> Frequency stability | Describes the estimate of the variation of the local clock when it is not synchronized to another source (NOTE 2). | +| >> Clock Accuracy | Describes the mean in ns over an ensemble of measurements of the time between the clock under test and a reference clock (NOTE 3). | +| Parent time source | Describes the primary source the node is currently using, represented by the values "SyncE", "PTP", "GNSS", "atomic clock", "terrestrial radio", "serial time code", "NTP", "hand_set", "other". | +| NOTE 1: Clock is in the "Locked", "Holdover", or "Freerun" mode, as defined in ITU-T G.810 [164]. | | +| NOTE 2: Frequency stability is estimated in a similar manner as for offsetScaledLogVariance attribute defined in clause 7.6.3.5 of IEEE Std 1588 [126]. | | +| NOTE 3: Clock accuracy measurement considers accuracy up to gNB antenna and RAN internal process. | | + +The TSCTSF determines the UEs impacted by gNB's timing synchronization status change (i.e. degradation, failure or improvement) or UPF timing synchronization status change (only for the case when UPF/NW-TT is involved in providing time information to DS-TT). + +- For the gNB case, when the TSCTSF receives information about timing synchronization status change, the TSCTSF uses the NRF to discover the AMFs serving the impacted gNBs and subscribes to receive notifications for UE's presence in Area of Interest information from AMF as described in clause 5.3.4.4. The Area of Interest is set to the scope of the timing synchronization status (i.e. gNB ID or a group of cells within the gNB specified with a list of Cell IDs that has reported status degradation (i.e. the pre-configured thresholds are exceeded in the gNB). The subscription is targeted to any UE in the AMF, the TSCTSF may provide additional filtering information as specified in clause 5.3.4.4 (e.g., List of UE IDs, DNN(s)/S-NSSAI(s)) to limit the subscription to the indicated UE identities, UEs having a PDU Session with the given DNN(s)/S-NSSAI(s). The TSCTSF correlates information about impacted gNBs and the UE location information received from the AMF. If the gNB notifies the TSCTSF for the status improvement (i.e. the pre-configured thresholds are met in the gNB), the TSCTSF modifies the subscription to remove the corresponding Area of Interest from the subscription. +- For UPF case, the TSCTSF determines the UEs for which the impacted UPF/NW-TT is configured to send (g)PTP messages on behalf of DS-TT (see clause 5.27.1.7). + +If the gNB's or UPF's timing synchronization status change, the TSCTSF may perform the following: + +- For AFs that subscribe for 5G access stratum time synchronization service or (g)PTP time synchronization service status update (i.e. change in support status of the clock quality acceptance criteria provided by the AF and specified using TSS attributes from Table 5.27.1.12-1), the TSCTSF may provide notification towards the AF when there is a change in support status for a UE or group of UEs. +- Deactivating/reactivating/updating time synchronization services: + - (g)PTP time synchronization service case: For UEs that are part of a PTP instance and which are impacted by NG-RAN or UPF time synchronization status degradation or improvement: + - If TSCTSF determines that the clock quality acceptance criteria provided by AF can still be met, then TSCTSF may update the clock quality information sent in Announce messages (see clause 7.6.2 of IEEE 1588 [8]) for the PTP instance using existing procedures and existing PMIC/UMIC information. The handling of Announce messages follows existing procedures as described in clause 5.27.1.6. + - If TSCTSF determines that the clock quality acceptance criteria provided by AF cannot be met, then TSCTSF informs the AF for the corresponding PTP ports being inactive due to the result of fulfilling the clock quality acceptance criteria; and the TSCTSF temporarily removes the UE/DS-TT from the PTP instance using the procedure in clause K.2.2.1 and clause K.2.2.4. The AF may send a service update or delete request (see clause 4.15.9.3 of TS 23.502 [3]). + +- If TSCTSF determines that the clock quality acceptance criteria provided by AF can be met again then TSCTSF informs the AF about the result, adds the DS-TT PTP port to the PTP instance again and re-activates the Grandmaster functionality. + +For 5G access stratum time synchronization service, clock quality reporting control information manages the gNBs timing synchronization status reporting to the UE. When AMF provides the 5G access stratum time distribution indication and the Uu time synchronization error budget to gNB, the AMF also includes the clock quality reporting control information (CQRCI) provided by the TSCTSF or retrieved from UDM. CQRCI may be a part of Access and Mobility Subscription data at the UDM, or AF may include CQRCI in its request. CQRCI contains the following fields: + +- Clock quality detail level. It indicates whether and which clock quality information to provide to the UE and can take one of the following values: "clock quality metrics" or "acceptable/not acceptable indication". +- If the clock quality detail level equals "clock quality metrics", the NG-RAN provides clock quality metrics to the UE that reflect its current timing synchronization status. i.e. one or more of the following information elements: clock accuracy, traceability to UTC, traceability to GNSS, frequency stability, parent time source, synchronization state as defined in Table 5.27.1.12-1. NG-RAN is locally configured which of the clock quality metrics supported by NG-RAN are provided to UE(s). +- If the clock quality detail level equals "acceptable/not acceptable indication", NG-RAN provides clock quality acceptance criteria for the UE. The gNB provides an acceptable indication to the UE if the gNB's timing synchronization status matches the acceptance criteria received from the AMF; otherwise, the gNB indicates "not acceptable" to the UE. Clock quality acceptance criteria can be defined based on one or more information elements listed in Table 5.27.1.12-1. If AF includes clock quality acceptance criteria in its request towards TSCTSF, the AF shall be notified about the result once TSCTSF determines whether the clock quality acceptance criteria can be met or not. Based on the notification, the AF may decide to modify the service if preferred (e.g., disable the service upon status degradation or enable it again upon status improvement). + +When determining the clock quality metrics for a UE and when determining whether clock quality is acceptable or not acceptable for a UE, the gNB considers whether propagation delay compensation is performed. + +NOTE 3: In this Release, UE capabilities and internal inaccuracies are assumed to be budgeted by the client network operator when agreeing the required clock accuracy with the 5G network operator. + +To provision clock quality information to the UEs, a gNB uses unicast RRC signalling: + +- For UEs in the RRC\_CONNECTED state, the gNB uses unicast RRC signalling. +- UEs that are not in the RRC\_CONNECTED state first need to establish or resume the RRC connection to receive the clock quality information from the gNB via unicast RRC signalling. + +During N2 Handover and Xn handover, Service Request, mobility registration and AM policy modification procedure, the AMF may provide the CQRCI to NG-RAN. + +### 5.27.1a Periodic deterministic communication + +This clause describes 5G System features that allow support of periodic deterministic communication where the traffic characteristics are known a-priori, and a schedule for transmission from the UE to a downstream node, or from the UPF to an upstream node is provided via external protocols outside the scope of 3GPP (e.g. IEEE 802.1 TSN). + +The features include the following: + +- Providing TSC Assistance Information (TSCAI) that describe TSC flow traffic characteristics (as described in clause 5.27.2) at the gNB ingress and the egress of the UE for traffic in downlink and uplink direction, respectively; +- Support for hold & forward buffering mechanism (see clause 5.27.4) in DS-TT and NW-TT to de-jitter flows that have traversed the 5G System. + +### 5.27.2 TSC Assistance Information (TSCAI) and TSC Assistance Container (TSCAC) + +#### 5.27.2.1 General + +TSC Assistance Information (TSCAI) is defined in Table 5.27.2-1 and describes TSC traffic characteristics for use in the 5G System. TSCAI may be used by the 5G-AN, if provided by SMF. The knowledge of TSC traffic pattern is useful for 5G-AN as it allows more efficiently scheduling of QoS Flows that have a periodic, deterministic traffic characteristics either via Configured Grants, Semi-Persistent Scheduling or with Dynamic Grants. TSCAI can be provided for both GBR and non-GBR QoS flows. + +The TSCTSF determines the TSC Assistance Container (defined in Table 5.27.2-2) based on information provided by an AF/NEF or a DetNet controller as described in clause 5.27.2.3 and provides it to the PCF for IP type and Ethernet type PDU Sessions. In the case of integration with IEEE TSN network, the TSN AF determines TSC Assistance Container as described in clause 5.27.2.2 and provides it to the PCF for Ethernet PDU Sessions. The PCF receives the TSC Assistance Container from the TSCTSF or the TSN AF and forwards it to the SMF as part of PCC rule as described in clause 6.1.3.23a of TS 23.503 [45]. + +The SMF binds a PCC rule with a TSC Assistance Container to a QoS Flow as described in clause 6.1.3.2.4 of TS 23.503 [45]. The SMF uses the TSC Assistance Container to derive the TSCAI for that QoS Flow and sends the derived TSCAI to the NG-RAN. The Periodicity, Periodicity Range, Burst Arrival Time (BAT), BAT Window and Survival Time components of the TSCAI are specified by the SMF with respect to the 5G clock. The SMF is responsible for mapping the Burst Arrival Time, BAT Window, Periodicity and Periodicity Range from an external clock (when available) to the 5G clock based on the time offset and cumulative rateRatio (when available) between the external clock time and 5GS time as measured and reported by the UPF. The SMF determines the TSCAI as described in clause 5.27.2.4. + +A Survival Time, which indicates the time period an application can survive without any data burst, may be provided by TSN AF/AF or by the TSCTSF either in terms of maximum number of messages (message is equivalent to all packets of a data burst) or in terms of time units. Only a single data burst is expected within a single time period referred to as the periodicity. + +The SMF may send an update of the TSCAI to the NG-RAN as defined in clauses 4.3.3.2, 4.9.1.2.2 and 4.9.1.3.2 of TS 23.502 [3] or as defined in clause 5.37.8.2. + +**Table 5.27.2-1: TSC Assistance Information (TSCAI)** + +| Assistance Information | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Flow Direction | The direction of the TSC flow (uplink or downlink). | +| Periodicity | It refers to the time period between start of two data bursts. | +| Burst Arrival Time (optional) | The latest possible time when the first packet of the data burst arrives at either the ingress of the RAN (downlink flow direction) or the egress of the UE (uplink flow direction). | +| Survival Time (optional) | Survival Time, as defined in TS 22.261 [2], refers to the time period an application can survive without any data burst. | +| Burst Arrival Time Window (BAT Window) (optional) (NOTE 1) (NOTE 2) | Indicates the acceptable earliest and latest arrival time of the first packet of the data burst at either the ingress of the RAN (downlink flow direction) or the egress of the UE (uplink flow direction). | +| Capability for BAT adaptation (optional) (NOTE 1) | Indicates that the AF will adjust the burst sending time according to the network provided Burst Arrival Time offset (see clause 5.27.2.5). | +| N6 Jitter Information (optional) (NOTE 3) | Jitter information associated with the Periodicity in downlink (see clause 5.378.1). | +| Periodicity Range (optional) (NOTE 4) | It indicates that the AF will adjust the periodicity and provides the acceptable range (which is formulated as lower bound and upper bound of the Periodicity) or acceptable Periodicity value(s) (which is formulated as a list of values for the Periodicity). | +| NOTE 1: Only one of the parameters (BAT Window or Capability for BAT adaptation) can be provided. | | +| NOTE 2: The parameter can only be provided together with Burst Arrival Time. | | +| NOTE 3: Only one of the parameters Burst Arrival Time or N6 Jitter Information may be provided for a given Traffic Flow. | | +| NOTE 4: The Periodicity Range can only be provided together with Periodicity when Burst Arrival Time and Burst Arrival Time Window are present. | | + +**Table 5.27.2-2: TSC Assistance Container (TSCAC)** + +| Assistance Information | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Flow Direction | The direction of the TSC flow (uplink or downlink). | +| Periodicity | It refers to the time period between start of two data bursts. | +| Burst Arrival Time (optional) | The time when the first packet of the data burst arrives at the ingress port of 5GS for a given flow direction (DS-TT for uplink, NW-TT for downlink). | +| Survival Time (optional) | It refers to the time period an application can survive without any data burst, as defined in TS 22.261 [2]. | +| Time Domain (optional) | The (g)PTP domain of the TSC flow. | +| Burst Arrival Time Window (BAT Window) (optional) (NOTE 1) (NOTE 2) | Indicates the acceptable earliest and latest arrival time of the first packet of the data burst at the ingress port of 5GS for a given flow direction (DS-TT for uplink, NW-TT for downlink). | +| Capability for BAT adaptation (optional) (NOTE 1) | It indicates that the AF will adjust the burst sending time according to the network provided Burst Arrival Time offset (see clause 5.27.2.5). | +| Periodicity Range (optional) (NOTE 3) | It indicates that the AF will adjust the periodicity and provides the acceptable range (which is formulated as lower bound and upper bound of the Periodicity) or acceptable Periodicity value(s) (which is formulated as a list of values for the Periodicity). | +| NOTE 1: Only one of the parameters (BAT Window or Capability for BAT adaptation) can be provided. | | +| NOTE 2: The parameter can only be provided together with Burst Arrival Time. | | +| NOTE 3: The Periodicity Range can only be provided together with Periodicity when Burst Arrival Time and Burst Arrival Time Window are present. | | + +#### 5.27.2.2 TSC Assistance Container determination based on PSFP + +In the case of integration with IEEE TSN network, the TSN AF determines a TSC Assistance Container (defined in Table 5.27.2-2) and provides it to the PCF. The determination of TSC Assistance Container based on Per-Stream Filtering and Policing (PSFP) information applies only to Ethernet type PDU Sessions. + +NOTE 1: This clause assumes that PSFP information as defined in IEEE Std 802.1Q [98] and Table K.3.1-1 is provided by CNC. PSFP information may be provided by CNC if TSN AF has declared PSFP support to CNC. TSN AF indicates the support for PSFP to CNC only if all the DS-TT and NW-TT ports of the 5GS Bridge have indicated support of PSFP. Means to derive the TSC Assistance Container if PSFP is not supported by 5GS and/or the CNC are beyond the scope of this specification. + +The TSN AF may be able to identify the ingress port and thereby the PDU Session as described in clause 5.28.2. + +The TSN AF interfaces towards the CNC for the PSFP (IEEE Std 802.1Q [98]) managed objects that correspond to the PSFP functionality implemented by the DS-TT and the NW-TT. Thus, when PSFP information is provided by the CNC, the TSN AF may extract relevant parameters from the PSFP configuration. The TSN AF calculates traffic pattern parameters (such as burst arrival time with reference to the ingress port and periodicity). TSN AF also obtains the flow direction as specified in clause 5.28.2. Survival Time may be pre-configured in TSN AF. + +TSN AF may enable aggregation of TSN streams if the TSN streams belong to the same traffic class, terminate in the same egress port and have the same periodicity and compatible Burst arrival time. When Survival Time information is provided for a TSN stream, then it should not be aggregated with other TSN streams into a single QoS Flow, or if they are aggregated, then the Survival Time parameter shall not be provided. One set of parameters and one TSC Assistance Container are created by the TSN AF for multiple TSN streams to enable aggregation of TSN streams to the same QoS Flow. + +Annex I describe how the traffic pattern information is determined. + +NOTE 2: Further details of aggregation of TSN streams (including determination of burst arrival times that are compatible so that TSN streams can be aggregated) are left for implementation. + +NOTE 3: In order for the TSN AF to get Burst Arrival Time, Periodicity on a per TSN stream basis, support for IEEE Std 802.1Q [98] (as stated in clause 4.4.8.2) Per-Stream Filtering and Policing (PSFP) with stream gate operation is a prerequisite. + +For a UE-UE TSC stream, the (TSN) AF divides the stream into one uplink stream and one or more downlink streams as defined in clause 5.28.2. The TSN AF binds the uplink and downlink streams to the PDU Sessions, and provides the streams on AF Session basis to the PCF(s). The TSN AF calculates traffic pattern parameters for the UL and the DL stream using the PSFP configuration (if provided) respectively: + +- For the uplink stream, the Flow Direction is set to uplink and traffic pattern parameters (such as burst arrival time with reference to the ingress port and periodicity) is determined as described in Annex I. +- For downlink stream, the Flow Direction is set to downlink, the burst arrival time is set to sum of burst arrival time of the UL stream and 5GS Bridge delay of PDU Session carrying the UL stream, and the periodicity is determined as described in Annex I. + +#### 5.27.2.3 TSC Assistance Container determination by TSCTSF + +The TSCTSF constructs TSC Assistance Container (defined in Table 5.27.2-2) based on information provided (directly or via NEF) by the AF for IP or Ethernet type PDU Sessions, or by the DetNet controller for IP type PDU Sessions. + +In the case of an AF request, the AF may provide Flow Direction, Burst Arrival Time (optional) at the UE/DS-TT (uplink) or UPF/NW-TT (downlink), Maximum Burst Size, Periodicity, Survival Time (optional), and a Time Domain (optional) to the TSCTSF. If the AF is able to adjust the burst sending time, the AF may in addition provide a BAT Window or the Capability for BAT adaptation to the TSCTSF. Additionally if the AF is able to adjust the periodicity, the AF may also provide the Periodicity Range along with the Periodicity to the TSCTSF. Based on these parameters, the TSCTSF constructs a TSC Assistance Container and provides it to PCF. If the AF provides to the TSCTSF a Burst Arrival Time or Periodicity without corresponding Time Domain, the TSCTSF sets the Time Domain = "5GS" in the TSC Assistance Container. + +If the AF is able to adjust the transmission time and periodicity then in addition to above parameters, it may provide a BAT Window (optional) or the capability for BAT adaptation (optional), or Periodicity Range (optional), to the TSCTSF. + +NOTE: The Maximum Burst Size is signalled separately, i.e. it is not part of the TSC Assistance Container. + +The AF provides these parameters to the NEF and the NEF forwards these parameters to the TSCTSF. The AF trusted by the operator provides these parameters to the TSCTSF directly. + +In the case of Deterministic Networking, the TSCTSF constructs the TSC Assistance Container based on information provided by the DetNet controller as defined in clause 6.1.3.23b of TS 23.503 [45]. + +The TSCTSF sends the TSC Assistance Container to the PCF as follows: + +- The TSCTSF uses the UE IP address/DS-TT port MAC address to identify the PCF and N5 association related to the PDU Session of a UE/DS-TT. + +#### 5.27.2.4 TSCAI determination based on TSC Assistance Container + +The SMF determines the TSCAI (defined in Table 5.27.2-1) for the QoS Flow based on the TSC Assistance Container of the PCC rule bound to the QoS Flow. This clause is applicable irrespective of whether the TSC Assistance Container is determined by the TSN AF or by the TSCTSF. + +The Burst Arrival Time and Periodicity component of the TSCAI that the SMF sends to the 5G-AN are specified with respect to the 5G clock. The SMF is responsible for mapping the Burst Arrival Time and Periodicity in the TSC Assistance Container from an external clock to the 5G clock based on the time offset and cumulative rateRatio (when available) between external time and 5GS time as measured and reported by the UPF. The SMF may correct the TSCAI based on the UPF report for time offset and cumulative rateRatio between external PTP time and 5GS time as measured and reported by the UPF. + +The TSCAI parameter determination in SMF is done as follows: + +- For traffic in downlink direction, the SMF corrects the Burst Arrival Time in the TSC Assistance Container based on the latest received time offset measurement from the UPF and sets the TSCAI Burst Arrival Time as the sum of the corrected value and CN PDB as described in clause 5.7.3.4, representing the latest possible time when the first packet of the data burst arrives at the AN. +- For traffic in uplink direction, the SMF corrects the Burst Arrival Time in the TSC Assistance Container based on the latest received time offset measurement from the UPF and sets the TSCAI Burst Arrival Time as the sum of the corrected value and UE-DS-TT Residence Time, representing the latest possible time when the first packet of the data burst arrives at the egress of the UE. How the SMF corrects the Burst Arrival Time if the UE-DS-TT Residence Time has not been provided by the UE is up to SMF implementation. +- The SMF corrects the Periodicity in the TSC Assistance Container using the cumulative rateRatio if the cumulative rateRatio was previously received from the UPF and sets the TSCAI Periodicity as the corrected value. Otherwise, the SMF sets the received Periodicity in the TSCAI without any correction. +- The SMF sets the TSCAI Flow Direction as the Flow Direction in the TSC Assistance Container. +- If Survival Time is provided in terms of maximum number of messages, the SMF converts maximum number of messages into time units by multiplying its value by the TSCAI Periodicity, and sets the TSCAI Survival Time to the calculated value. If Survival Time is provided in time units, the SMF corrects the Survival Time using the cumulative rateRatio if the cumulative rateRatio was previously received from the UPF and sets the TSCAI Survival Time to the corrected value. Otherwise, SMF sets the TSCAI Survival Time without correction. +- If the TSC Assistance Container contains a BAT Window, the SMF sets and corrects the indicated earliest and latest possible arrival time of the first packet in the same way it is described for the correction of the Burst Arrival Time above. +- If the TSC Assistance Container contains a Capability for BAT adaptation, the SMF sets the Capability for BAT adaptation in the TSCAI. When the SMF determines that the TSCAI contains the Capability for BAT adaptation without a BAT, the SMF enables notification control for the QoS Flow in order to receive the BAT offset along with the "GFBR can no longer be guaranteed" notification described in clause 5.7.2.4. +- If the TSC Assistance Container contains a Periodicity Range, the SMF sets and corrects the Periodicity Range in the same way it is described for the correction of the Periodicity above. + +Depending on whether the Time Domain is provided in the TSC Assistance container, SMF may perform the following: + +- the SMF provisions the UPF/NW-TT to report the clock drifting between 5G clock and the external GM clock for the (g)PTP time domain number that is configured to the NW-TT. +- the SMF provisions the UPF/NW-TT to report the clock drifting between 5G clock and the external GM clock for the given Time Domain number. + +The SMF uses the N4 Association Setup or Update procedures as described in clause 4.4.3 of TS 23.502 [3] to provision the UPF to report the clock drifting. + +If the SMF has clock drift information for a Time Domain and if the Time Domain matches with the Time Domain in the TSC Assistance Container (i.e. clock drift between 5G timing and AF supplied Time Domain determined based on UPF reporting), or Time Domain information is not provided in the TSC Assistance Container, then the SMF may adjust the TSCAI information so that it reflects the 5GS Clock as described in clause 5.27.2.1. + +If the SMF does not have synchronization information for a requested Time Domain in the TSC Assistance Container, or the Time Domain in the TSC Assistance Container is set to a value = "5GS", then the TSCAI information will be used without adjustment. + +In the case of drift between external GM clock and 5G clock, the UPF updates the offset to SMF using the N4 Report Procedure as defined in clause 4.4.3.4 of TS 23.502 [3]. If the cumulative rateRatio is available and in the case of change of cumulative rateRatio between external PTP time and 5G time, the UPF updates the cumulative rateRatio to SMF using the N4 Report Procedure as defined in clause 4.4.3.4 of TS 23.502 [3]. The SMF may then trigger a PDU Session Modification as defined in clause 4.3.3 of TS 23.502 [3] in order to update the TSCAI to the NG-RAN without requiring AN or N1 specific signalling exchange with the UE. + +NOTE 4: In order to prevent frequent updates from the UPF, the UPF sends the offset or the cumulative rateRatio only when the difference between the current measurement and the previously reported measurement is larger than a threshold as described in clause 4.4.3.4 of TS 23.502 [3]. + +#### 5.27.2.5 RAN feedback for Burst Arrival Time offset and adjusted Periodicity + +##### 5.27.2.5.1 Overview + +If the NG-RAN receives a TSCAI containing a BAT Window or the Capability for BAT adaptation for a QoS Flow, the NG-RAN can determine a BAT offset in order to align the arrival of the traffic bursts with the next expected transmission opportunity over the air interface in each direction (i.e. DL or UL). The BAT offset can take a positive or a negative values. + +If the NG-RAN receives a TSCAI containing a Periodicity Range for a QoS Flow, the NG-RAN can determine an adjusted Periodicity along with above specified BAT offset, in order to align the periodicity of the traffic bursts with the expected time interval between subsequent transmission opportunities over the air interface in each direction (i.e. DL or UL). If the TSCAI contained a value range, the adjusted Periodicity should be any value between the lower bound and upper bound. If the TSCAI contained a list of Periodicity value(s), the adjusted Periodicity should be one of these values. + +NG-RAN may support the following feedback mechanisms: + +- Proactive RAN feedback for adaptation of Burst Arrival Time and Periodicity: NG-RAN may provide a Burst Arrival Time offset and an adjusted Periodicity as part of QoS flow establishment or modification as illustrated in clause 5.27.2.5.2; +- Reactive RAN feedback for Burst Arrival Time adaptation: NG-RAN may provide a Burst Arrival Time offset after QoS flow establishment as illustrated in clause 5.27.2.5.3. + +##### 5.27.2.5.2 Proactive RAN feedback for adaptation of Burst Arrival Time and Periodicity + +If the NG-RAN receives a Burst Arrival Time and Burst Arrival Time Window in the TSCAI for a QoS Flow, the 5GS will perform the following actions: + +- The NG-RAN can determine a BAT offset in order to align the expected arrival of the traffic bursts (as indicated in the BAT) with the time when the next transmission over the air interface in each direction (i.e. DL or UL) is expected. The BAT offset shall always be provided by NG-RAN and it shall be within the BAT Window. The BAT offset is calculated with reference to the BAT. +- If the BAT offset is provided from NG-RAN to the SMF in the response to the QoS Flow establishment or modification request, the SMF provides the BAT offset to the PCF and the PCF notifies the AF as described in clause 6.1.3.23a of TS 23.503 [45]. +- The SMF may adjust the BAT offset received from NG-RAN based on the clock drifting report from UPF as specified in clause 4.4.3.4 of TS 23.502 [3]. + +NOTE: The feedback from RAN implies that the RAN accepts the BAT offset. If the AF requested BAT is acceptable for NG-RAN, the NG-RAN provides a BAT offset of zero. + +- If the RAN also receives a Periodicity Range along with the Periodicity in the TSCAI for a QoS flow, the 5GS will further perform the following actions: + - The RAN may determine an adjusted periodicity in order to align the periodicity of the traffic bursts with the expected time interval between subsequent transmission opportunities over the air interface in each direction (i.e. DL or UL). If the RAN determines an adjusted periodicity, the RAN provides it together with a BAT + +offset mentioned above. The adjusted periodicity shall be within the Periodicity Range and the BAT offset is based on the adjusted periodicity. + +- The adjusted periodicity is forwarded to the AF via the SMF and the PCF together with a BAT offset in the same way it is described above. +- If interworking with a TSN network deployed in the transport network is supported, the SMF/CUC uses the adjusted periodicity (if provided) and BAT offset accepted by the RAN to adjust the EarliestTransmitOffset and LatestTransmitOffset in the Talker/Listener Group in IEEE Std 801.Q [98] as described in Annex M, clause M.1. + +##### 5.27.2.5.3 Reactive RAN feedback for Burst Arrival Time adaptation + +If the RAN receives the capability for BAT adaptation without a Burst Arrival Time in the TSCAI and notification control is enabled for this QoS Flow, the 5GS will perform the following actions: + +- If NG-RAN determines that the PDB of the QoS flow cannot be fulfilled in DL and UL direction, then if supported, NG-RAN shall determine a BAT offset value which reduces the time between the arrival of the traffic bursts and the time of the next possible transmission over the air interface for DL and UL, respectively. NG-RAN shall not provide a BAT offset with the same value until the PDB of the QoS Flow can be fulfilled again. + +NOTE: NG-RAN determines BAT offset value in reference to the current arrival time of the bursts experienced by RAN in DL and by UE in UL. Further details on BAT offset determination for DL and UL will be defined by RAN WG2. + +- The BAT offset is provided from NG-RAN to the SMF when sending the notification towards the SMF that the "GBFR can no longer be guaranteed" described in clause 5.7.2.4. The SMF provides the BAT offset to the PCF and the PCF provides the BAT offset to the AF as part of notifying the AF as described in clause 6.1.3.23a of TS 23.503 [45] + +### 5.27.3 Support for TSC QoS Flows + +TSC QoS Flows use a Delay-critical GBR resource type and TSC Assistance Information. TSC QoS Flows may use standardized 5QIs, pre-configured 5QIs or dynamically assigned 5QI values (which requires signalling of QoS characteristics as part of the QoS profile) as specified in clause 5.7.2. For each instance of Periodicity, within each Period (defined by periodicity value), TSC QoS Flows are required to transmit only one burst of maximum size MDBV within the 5G-AN PDB. Known QoS Flow traffic characteristics provided in the TSCAI may be used to optimize scheduling in the 5GS. + +The following is applicable for the QoS profile defined for TSC QoS Flows: + +1. The TSC Burst Size may be used to set the MDBV as follows: + +The maximum TSC Burst Size is considered as the largest amount of data within a time period that is equal to the value of 5G-AN PDB of the 5QI. The maximum value of TSC Burst Size should be mapped to a 5QI with MDBV that is equal or higher. When integration with IEEE TSN applies, this 5QI also shall have a PDB value that satisfies the bridge delay capabilities (see clause 5.27.5 for more details) reported for the corresponding traffic class. For TSC QoS Flows, the Maximum Burst Size of the aggregated TSC streams to be allocated to this QoS Flow can be similarly mapped to a 5QI with MDBV value that is equal or higher. If interworking with a TSN network deployed in the transport network is supported, the maximum value of TSC Burst Size should be mapped to a 5QI with MDBV that is equal. + +2. The PDB is explicitly divided into 5G-AN PDB and CN PDB as described in clause 5.7.3.4. Separate delay budgets are necessary for calculation of expected packet transmit times on 5G System interfaces. For the TSC QoS Flow, the 5G-AN PDB is set to value of 5QI PDB minus the CN PDB as described in clause 5.7.3.4. The CN PDB may be static value or dynamic value and is up to the implementation of 5GS bridge. +3. When integration with IEEE TSN applies, the Maximum Flow Bitrate calculated by the TSN AF as per Annex I.1 may be used to set GBR. In this case, MBR is set equal to GBR. +4. ARP is set to a pre-configured value. +5. 5QI value is derived using QoS mapping tables and TSN QoS information as described in clause 5.28.4 in the case of integration with IEEE TSN network, or using QoS Reference parameters and Requested PDB, Burst + +Size, Priority parameters as described in clause 4.15.6.6 or clause 4.15.6.6a of TS 23.502 [3] in the case of AF requested Time Sensitive Communication. + +### 5.27.4 Hold and Forward Buffering mechanism + +DS-TT ports and NW-TT ports support a hold and forward mechanism to schedule traffic as defined in IEEE Std 802.1Q [98] if 5GS is to participate transparently as a bridge in a TSN network. That is, the hold and forward buffering mechanism in this release of the specification provides externally observable behaviour identical to scheduled traffic with up to eight queues (clause 8.6.8.4 in IEEE Std 802.1Q [98]) and with protected windows (Annex Q.2 in IEEE Std 802.1Q [98]). Frames are only transmitted from a given buffer according to the open time interval of the corresponding transmission gate; otherwise, frames are hold back (which corresponds to a closed transmission gate). The protected windows scheme implies that only a single transmission gate is open at any single time. Thus, the Hold and Forward buffering mechanism allows PDB based 5GS QoS to be used for TSC traffic. + +For Ethernet frames that contain a VLAN tag, DS-TT and NW-TT determine the priority based on the PCP value contained in the VLAN tag. For Ethernet frames that do not contain a VLAN tag, DS-TT and NW-TT apply a priority value of 0. + +To achieve externally observable behaviour according to the protected windows scheme, 5GS provides AdminControlList, AdminBaseTime, AdminCycleTime and TickGranularity as defined in IEEE Std 802.1Q [98] on a per Ethernet port basis to DS-TT and NW-TT for the hold and forward buffering mechanism as described in clause 5.28.3. + +NOTE: The details of how Hold and Forward buffering mechanism is provided by the DS-TT and NW-TT is up to implementation. + +### 5.27.5 5G System Bridge delay + +This clause applies if 5GS is integrated as a bridge into an IEEE TSN network. + +In order for the 5G System to participate as a TSN bridge according to transmission gate schedules specified, the 5GS Bridge is required to provide Bridge Delays as defined in IEEE Std 802.1Q [98] for each port pair and traffic class of the 5GS bridge to an IEEE 802.1 TSN system. In order to determine 5GS Bridge Delays, the following components are needed: + +1. UE-DS-TT Residence Time. +2. Per traffic class minimum and maximum delays between the UE and the UPF/NW-TT that terminates the N6 interface (including UPF and NW-TT residence times), independent of frame length that a given 5GS deployment supports. The per-traffic class delays between the UE and the UPF/NW-TT are pre-configured in the TSN AF (see clause 5.28.4). + +The TSN AF calculates the 5GS independentDelayMin and independentDelayMax values for each port pair and for each traffic class using the above components. If the UE-DS-TT Residence Time has not been provided by the UE, then the TSN AF uses a locally configured minimum UE-DS-TT Residence Time for the calculation of independentDelayMin and a locally configured maximum UE-DS-TT Residence Time for the calculation of independentDelayMax. + +The dependentDelayMin and dependentDelayMax for 5GS Bridge specify the time range for a single octet of an Ethernet frame to transfer from ingress to egress and include the time to receive and store each octet of the frame, which depends on the link speed of the ingress Port as per IEEE Std 802.1Q [98]. + +NOTE: Further details how TSN AF determines dependentDelayMin and dependentDelayMax are up to implementation. + +Since residence times may vary among UEs and per traffic class delay between the UE and the UPF/NW-TT may vary among UPFs, the 5GS Bridge Delay is determined after the PDU Session Establishment for the corresponding UPF and the UE by the TSN AF. The TSN AF deduces the related port pair(s) from the port number of the DS-TT Ethernet port and port number of the NW-TT Ethernet port(s) of the same 5GS Bridge when the TSN AF receives the 5GS Bridge information for a newly established PDU Session and calculates the bridge delays per port pair. Additionally, TSN AF deduces the port pair(s) consisting of two DS-TT ports connecting to the same 5GS bridge and determines the 5GS bridge delay as sum of bridge delays related to PDU Sessions of two DS-TT ports. + +## 5.28 Support of integration with TSN, Time Sensitive Communications, Time Synchronization and Deterministic Networking + +### 5.28.0 General + +Clause 5.28 defines the 5GS integration in TSN DN as a 5GS bridge. + +In this scenario, 5GS is deployed in a TSN DN to provide wireless connectivity. From the perspective of the TSN DN, the 5GS is modelled as a Layer 2 Ethernet Bridge of the TSN DN. + +In addition to supporting interoperation with TSN, 5GS also supports Time Sensitive Communication, Time Synchronization and integration with Deterministic Networking. + +### 5.28.1 5GS bridge management for TSN + +5GS acts as a Layer 2 Ethernet Bridge. When integrated with IEEE TSN network, 5GS functions acts as one or more TSN Bridges of the TSN network. The 5GS Bridge is composed of the ports on a single UPF (i.e. PSA) side, the user plane tunnel between the UE and UPF, and the ports on the DS-TT side. For each 5GS Bridge of a TSN network, the port on NW-TT support the connectivity to the TSN network, the ports on DS-TT side are associated to the PDU Session providing connectivity to the TSN network. + +The granularity of the 5GS TSN bridge is per UPF for each network instance or DNN/S-NSSAI. The bridge ID of the 5GS TSN bridge is bound to the UPF ID of the UPF as identified in TS 23.502 [3]. The TSN AF stores the binding relationship between a port on UE/DS-TT side and a PDU Session during reporting of 5GS TSN bridge information. The TSN AF also stores the information about ports on the UPF/NW-TT side. The UPF/NW-TT forwards traffic to the appropriate egress port based on the traffic forwarding information. From the TSN AF point of view, a 5GS TSN bridge has a single NW-TT entity within UPF and the NW-TT may have multiple ports that are used for traffic forwarding. + +NOTE 1: How to realize single NW-TT entity within UPF is up to implementation. + +NOTE 2: Ethernet PDU Session type in this release of the specification may be subject to the constraint that it supports a single N6 interface in a UPF associated with the N6 Network Instance. + +There is only one PDU Session per DS-TT port for a given UPF. All PDU Sessions which connect to the same TSN network via a specific UPF are grouped into a single 5GS bridge. The capabilities of each port on UE/DS-TT side and UPF/NW-TT side are integrated as part of the configuration of the 5GS Bridge and are notified to TSN AF and delivered to CNC for TSN bridge registration and modification. + +NOTE 3: It is assumed that all PDU Sessions which connect to the same TSN network via a specific UPF are handled by the same TSN AF. + +![Diagram illustrating the Per UPF based 5GS bridge architecture. The diagram shows two TSN Bridge / End Stations on the left. The top station connects to a 'DS_TT' block, which is part of 'Bridge A'. This 'DS_TT' connects to 'UE1', which is connected via 'PDU Session 1A' to 'UPF - A'. 'UPF - A' connects to 'NW-TT', which is connected to a cloud labeled 'TSN System'. The bottom station connects to another 'DS_TT' block, which is part of 'Bridge B'. This 'DS_TT' connects to 'UE2', which is connected via 'PDU Session 2B' to 'UPF - B'. 'UPF - B' connects to 'NW-TT', which is also connected to the 'TSN System' cloud. Both 'UPF - A' and 'UPF - B' are shown as separate entities, each with their own 'NW-TT' block connected to the TSN System.](5bcaa554999322056447df1b81256bfc_img.jpg) + +Diagram illustrating the Per UPF based 5GS bridge architecture. The diagram shows two TSN Bridge / End Stations on the left. The top station connects to a 'DS\_TT' block, which is part of 'Bridge A'. This 'DS\_TT' connects to 'UE1', which is connected via 'PDU Session 1A' to 'UPF - A'. 'UPF - A' connects to 'NW-TT', which is connected to a cloud labeled 'TSN System'. The bottom station connects to another 'DS\_TT' block, which is part of 'Bridge B'. This 'DS\_TT' connects to 'UE2', which is connected via 'PDU Session 2B' to 'UPF - B'. 'UPF - B' connects to 'NW-TT', which is also connected to the 'TSN System' cloud. Both 'UPF - A' and 'UPF - B' are shown as separate entities, each with their own 'NW-TT' block connected to the TSN System. + +Figure 5.28.1-1: Per UPF based 5GS bridge + +NOTE 4: If a UE establishes multiple PDU Sessions terminating in different UPFs, then the UE is represented by multiple 5GS TSN bridges. + +In order to support IEEE 802.1Q features related to TSN, including TSN scheduled traffic (clause 8.6.8.4 in IEEE Std 802.1Q [98]) over 5GS Bridge, the 5GS supports the following functions: + +- Configure the bridge information in 5GS. +- Report the bridge information of 5GS Bridge to TSN network after PDU Session establishment. +- Receiving the configuration from TSN network as defined in clause 5.28.2. +- Map the configuration information obtained from TSN network into 5GS QoS information (e.g. 5QI, TSC Assistance Information) of a QoS Flow in corresponding PDU Session for efficient time-aware scheduling, as defined at clause 5.28.2. + +The bridge information of 5GS Bridge is used by the TSN network to make appropriate management configuration for the 5GS Bridge. The bridge information of 5GS Bridge includes at least the following: + +- Information for 5GS Bridge: + - Bridge ID + +Bridge ID is to distinguish between bridge instances within 5GS. The Bridge ID can be derived from the unique bridge MAC address as described in IEEE Std 802.1Q [98], or set by implementation specific means ensuring that unique values are used within 5GS; + - Number of Ports; + - list of port numbers. +- Capabilities of 5GS Bridge as defined in IEEE Std 802.1Q [98]: + - 5GS Bridge delay per port pair per traffic class, including 5GS Bridge delay (dependent and independent of frame size, and their maximum and minimum values: independentDelayMax, independentDelayMin, dependentDelayMax, dependentDelayMin), ingress port number, egress port number and traffic class. + - Propagation delay per port (txPropagationDelay), including transmission propagation delay, egress port number. + - VLAN Configuration Information. + +NOTE 5: This Release of the specification does not support the modification of VLAN Configuration Information at the TSN AF. + +- Topology of 5GS Bridge as defined in IEEE Std 802.1AB [97]: + - LLDP Configuration Information. + - Chassis ID subtype and Chassis ID of the 5GS Bridge. + - LLDP Discovery Information for each discovered neighbor of each NW-TT port and DS-TT port. +- Traffic classes and their priorities per port as defined in IEEE Std 802.1Q [98]. +- Stream Parameters as defined in clause 12.31.1 in IEEE Std 802.1Q [98], in order to support PSFP: + - MaxStreamFilterInstances: The maximum number of Stream Filter instances supported by the bridge; + - MaxStreamGateInstances: The maximum number of Stream Gate instances supported by the bridge; + - MaxFlowMeterInstances: The maximum number of Flow Meter instances supported by the bridge (optional); + - SupportedListMax: The maximum value supported by the bridge of the AdminControlListLength and OperControlListLength parameters. + +The following parameters: independentDelayMax and independentDelayMin, how to calculate them is left to implementation and not defined in this specification. + +DS-TT and NW-TT report txPropagationDelay to the TSN AF relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC). If the TSN AF has subscribed for notifications on txPropagationDelay and if the difference to the previously reported txPropagationDelay is larger than the txPropagationDelayDeltaThreshold received in PMIC, the corresponding DS-TT or NW-TT informs the TSN AF about the updated txPropagationDelay using PMIC signalling. + +NOTE 6: Configuration of TSN time domain number and txPropagationDelayDeltaThreshold via PMIC is optional for NW-TT. NW-TT can instead be pre-configured with the threshold and the single time domain that is used by the CNC for bridge configuration and reporting. + +Bridge ID of the 5GS Bridge, port number(s) of the Ethernet port(s) in NW-TT could be preconfigured on the UPF. The UPF is selected for a PDU Session serving TSC as described in clause 6.3.3.3. + +This release of the specification requires that each DS-TT port is assigned with a globally unique MAC address. + +NOTE 7: The MAC address of the DS-TT port must not be used in user data traffic; it is used for identification of the PDU Session and the associated bridge port within the 3GPP system. + +When there are multiple network instances within a UPF, each network instance is considered logically separate. The network instance for the N6 interface (clause 5.6.12) may be indicated by the SMF to the UPF for a given PDU Session during PDU Session establishment. UPF allocates resources based on the Network Instance and S-NSSAI and it is supported according to TS 29.244 [65]. DNN/S-NSSAI may be indicated by the SMF together with the network instance to the UPF for a given PDU Session during PDU Session establishment procedure. + +The TSN AF is responsible to receive the bridge information of 5GS Bridge from 5GS, as well as register or update this information to the CNC. + +### 5.28.2 5GS Bridge configuration for TSN + +The configuration information of 5GS Bridge as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98], includes the following: + +- Bridge ID of 5GS Bridge. +- Configuration information of scheduled traffic on ports of DS-TT and NW-TT: + - Egress ports of 5GS Bridge, e.g. ports on DS-TT and NW-TT; + - Traffic classes and their priorities. + +NOTE 1: In this Release of the specification, scheduled traffic (clause 8.6.8.4 in IEEE Std 802.1Q [98]) is only supported with protected windows, (see clause Q.2 in IEEE Std 802.1Q [98]), therefore, it is enough to support AdminControlList, AdminBaseTime, AdminCycleTime and TickGranularity for the configuration of the 5GS. + +The configuration information of 5GS Bridge as defined in IEEE Std 802.1Q [98], includes the following: + +- Chassis ID of 5GS Bridge; +- Traffic forwarding information as defined in clause 8.8.1 of IEEE Std 802.1Q [98]: + - Destination MAC address and VLAN ID of TSN stream; + - Port number in the Port MAP as defined in clause 8.8.1 of IEEE Std 802.1Q [98]. +- Configuration information per stream according to clause 8.6.5.1 of IEEE Std 802.1Q [98] including: + - Stream filters. + - Stream gates. + +NOTE 2: In order to support clause 8.6.5.2.1 of IEEE Std 802.1Q [98], it is required to support the Stream Identification function as specified by IEEE Std 802.1CB [83]. + +The SMF report the MAC address of the DS-TT port of the related PDU Session to TSN AF via PCF. The association between the DS-TT MAC address, 5GS Bridge ID and port number on DS-TT is maintained at TSN AF and further used to assist to bind the TSN traffic with the UE's PDU session. + +Two models are supported to configure 5GS QoS for TSN traffic: + +- Based on the assumption that PSFP information is always provided by CNC: In this case the QoS Flows are setup based on the PSFP information provided by CNC; + +NOTE 3: PSFP information may be provided by CNC if TSN AF has declared PSFP support to CNC. TSN AF indicates the support for PSFP to CNC only if each DS-TT and NW-TT of the 5GS bridge has indicated support of PSFP. + +- Without requiring PSFP information provided by the CNC.: In this case, pre-configured QoS Flows are used and configured e.g. during PDU session establishment as described in clause 5.28.4. Additional QoS Flows are setup as necessary based on the PSFP, if available, as described in this clause. + +When PSFP information is available, TSN AF identifies the ingress and egress port for the TSN stream as described in Annex I and determines the DS-TT port MAC address(es) identifying the corresponding PDU session(s) carrying the TSN stream. Flow direction of a TSN stream is determined as follows: if the ingress port is a DS-TT port, then the Flow direction is UL; otherwise if the ingress port(s) is (are) NW-TT port, the Flow direction is DL. Flow direction is part of the TSCAI as defined in clause 5.27.2. + +The TSN AF uses the stream filter instances of PSFP information to derive the service data flow for TSN streams. The TSN AF uses the Priority values in the stream filter instances in PSFP information (if available) as defined in clause 8.6.5.2.1 of IEEE Std 802.1Q [98], the 5GS bridge delay information (see clause 5.27.5) and may additionally use scheduled traffic information as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98], to derive the TSN QoS information (i.e. priority and delay) for a given TSN stream or flow of aggregated TSN streams as specified in clause 5.28.4. + +The TSN AF identifies the egress port(s) for the TSN stream using local configuration or static filtering entry that matches the TSN stream. If the TSN AF determines that the TSN stream is for UE-UE communication (i.e. ingress and egress ports are in DS-TTs), the TSN AF divides the stream into one uplink stream and one or more downlink streams and provides the streams on AF Session basis to the PCF(s). The SMF applies local switching as specified in clause 5.8.2.13 or clause 5.8.2.5.3 in order to enable UPF locally forward uplink stream from one PDU session as downlink stream in another PDU session. + +When CNC configures the PSFP information to the TSN AF, TSN AF determines the TSC Assistance Container as described in clause 5.27.2. The TSN AF associates the TSN QoS information and TSC Assistance Container (if available) with the corresponding service data flow description and provides to the PCF and the SMF as defined in clause 6.1.3.23 of TS 23.503 [45]. + +- NOTE 4: When the TSN stream priority information from PSFP is not available (priority value in stream filters is set to wild card), in certain configurations it can be possible to use the scheduled traffic information as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98] to derive the Priority of the TSN stream. For example, when there is a single downlink stream for a given DS-TT port, it can be possible to determine the affected DS-TT port in the downlink and the associated TSN stream priority based on the scheduled traffic information of the affected egress port, and to derive an estimated MDBV based on the gate open interval and the assumed ingress port bitrate. + +If TSN AF provides PSFP and/or scheduled traffic information to DS-TT and NW-TT then DS-TT and NW-TT execute on this information relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC). + +- NOTE 5: Configuration of TSN time domain number via PMIC is optional for NW-TT. NW-TT can instead be pre-configured with the single time domain that is used by the CNC for bridge configuration and reporting. + +### 5.28.3 Port and user plane node management information exchange in 5GS + +#### 5.28.3.1 General + +Port number for the PDU Session is assigned by the UPF during PDU session establishment. The port number for a PDU Session shall be reported to the SMF from the UPF and further stored at the SMF. The SMF provides the port number via PCF to the TSN AF or TSCTSF. TSN AF or TSCTSF maintains an association between the port number for the PDU Session and the DS-TT port MAC address (with Ethernet type PDU session) or IP address (applicable for TSCTSF only, with IP type PDU Session) of the UE. If a PDU session for which SMF has reported a port number to TSN AF or TSCTSF is released, then SMF informs TSN AF or TSCTSF accordingly. The port number for the PDU Session corresponds to the device side port of the 5GS bridge/router. When the device supports the DS-TT functionality, the port number represents the DS-TT port number corresponding to the given PDU Session. + +NOTE 1: Port number can refer either to Ethernet port or PTP port. In Ethernet type PDU Sessions, it is assumed that the PTP port number is the same as the associated Ethernet port number. + +When the DS-TT or the NW-TT functions are used, the 5GS shall support transfer of standardized and deployment-specific port management information transparently between TSN AF or TSCTSF and DS-TT or NW-TT, respectively inside a Port Management Information Container. NW-TT may support one or more ports. In this case, each port uses separate Port Management Information Container. 5GS shall also support transfer of standardized and deployment-specific user plane node management information transparently between TSN AF or TSCTSF and NW-TT, respectively inside a User Plane Node Management Information Container. Clause K.1 lists standardized port management information and user plane node management information, respectively. + +If TSN AF is deployed, i.e. if 5GS is integrated with an IEEE TSN network, the port and user plane node management information is exchanged between CNC and TSN AF. The port management information is related to ports located in DS-TT or NW-TT. The user plane node management information container is related to 5GS bridge management. + +If TSN AF is not deployed, the port and user plane node management information is exchanged between TSCTSF and DS-TT/NW-TT. + +NOTE 2: The time synchronization parameters used in Port Management Information Container and User Plane Node Management Information Container are from IEEE Std 1588 [126], Edition 2019, and from IEEE Std 802.1AS [104]. Since the IEEE time synchronization data sets are not exposed, care needs to be taken when interoperating with devices supporting Edition 2008, IEEE Std 1588-2008 [107] (which can be the case when operating under the SMPTE profile, ST 2059-2:2015 [127]) and using a common management. + +Exchange of port and user plane node management information between TSN AF or TSCTSF and NW-TT or between TSN AF or TSCTSF and DS-TT allows TSN AF or TSCTSF to: + +- 1) retrieve port management information for a DS-TT or NW-TT port or user plane node management information; +- 2) send port management information for a DS-TT or NW-TT port or user plane node management information; +- 3) subscribe to and receive notifications if specific port management information for a DS-TT or NW-TT port changes or user plane node management information changes. +- 4) delete selected entries in the following data structures: + - "DS-TT port neighbour discovery configuration for DS-TT port" in UMIC using the DS-TT port number to reference the selected entry. + - "Stream Filter Instance Table" in PMIC using the Stream Filter Instance ID to reference the selected entry. + - "Stream Gate Instance Table" in PMIC using the Stream Gate Instance ID to reference the selected entry. + - "Static Filtering Entries table" in UMIC using the (MAC address, VLAN ID) pair to reference the selected entry. +- 5) delete PTP Instances in a DS-TT port or NW-TT port using the PTP Instance ID to reference the selected entry as described in clause K.2.2.1. + +Exchange of port management information between TSN AF or TSCTSF and NW-TT or DS-TT is initiated by DS-TT or NW-TT to: + +- notify TSN AF or TSCTSF if port management information has changed that TSN AF or TSCTSF has subscribed for. + +Exchange of user plane node management information between TSN AF or TSCTSF and NW-TT is initiated by NW-TT to: + +- notify TSN AF or TSCTSF if user plane node management information has changed that TSN AF or TSCTSF has subscribed for. +- notify TSCTSF if time synchronization status information of UPF has changed that the TSCTSF has subscribed for. + +Exchange of port management information is initiated by DS-TT to: + +- provide port management capabilities, i.e. provide information indicating which standardized and deployment-specific port management information is supported by DS-TT. + +TSN AF or TSCTSF indicates inside the Port Management Information Container or user plane node Management Information Container whether it wants to retrieve or send port or user plane node management information or intends to (un-)subscribe for notifications. If the TSN AF or TSCTSF has requested to receive notification of TSC management information and both SMF and UPF support direct reporting, the UPF may directly report TSC management information to the TSN AF or TSCTSF using Nupf\_EventExposure\_Notify. + +#### 5.28.3.2 Transfer of port or user plane node management information + +Port management information is transferred transparently via 5GS between TSN AF or TSCTSF and DS-TT or NW-TT, respectively, inside a Port Management Information Container (PMIC). User plane node management information is transferred transparently via 5GS between TSN AF or TSCTSF and NW-TT inside a user plane node Management Information Container (UMIC). The transfer of port or user plane node management information is as follows: + +- To convey port management information from DS-TT or NW-TT to TSN AF or TSCTSF: + - DS-TT provides a PMIC and the DS-TT port MAC address (if available) to the UE, which includes the PMIC as an optional Information Element of an N1 SM container and triggers the UE requested PDU Session Establishment procedure or PDU Session Modification procedure to forward the PMIC to the SMF. SMF forwards the PMIC and the port number of the related DS-TT port to TSN AF or TSCTSF as described in clauses 4.3.2.2 and 4.3.3.2 of TS 23.502 [3]; + - NW-TT provides PMIC(s) and/or UMIC to the UPF, which may trigger the N4 Session Level Reporting Procedure to forward the PMIC(s) and/or UMIC to SMF. UPF selects an N4 session corresponding to any of the N4 sessions for this NW-TT. SMF in turn forwards the PMIC(s) and the port number(s) of the related NW-TT port(s), or the UMIC, to TSN AF or TSCTSF as described in clause 4.16.5.1 of TS 23.502 [3]. + - NW-TT may provide PMIC(s) and/or UMIC to the UPF, which may trigger UPF Event Exposure Notification to forward the PMIC(s) and/or UMIC to TSN AF or TSCTSF. UPF directly reports TSC management information event via Nupf\_EventExposure\_Notify service operation as described in clause 5.2.26.2 of TS 23.502 [3]. + +NOTE 1: There has to be at least one established PDU session for DS-TT port before the UPF can report PMIC/UMIC information towards the TSN AF or TSCTSF. + +- To convey port management information from TSN AF or TSCTSF to DS-TT: + - TSN AF or TSCTSF provides a PMIC, DS-TT port MAC address or UE IP address (applicable for TSCTSF only) reported for a PDU Session (i.e. MAC address of the DS-TT port or IP address related to the PDU session) and the port number of the DS-TT port to manage to the PCF by using the AF Session level Procedure, which forwards the information to SMF based on the MAC or IP address using the PCF initiated SM Policy Association Modification procedure as described in clause 4.16.5.2 of TS 23.502 [3]. SMF determines that the port number relates to a DS-TT port and based on this forwards the PMIC to DS-TT using the network requested PDU Session Modification procedure as described in clause 4.3.3.2 of TS 23.502 [3]. + +- To convey port or user plane node management information from TSN AF or TSCTSF to NW-TT: + - TSN AF or TSCTSF selects a PCF-AF session corresponding to any of the DS-TT MAC or IP addresses (applicable for TSCTSF only) for the related PDU sessions of this bridge or router and provides a PMIC(s) and the related NW-TT port number(s) and/or UMIC to the PCF. The PCF uses the PCF initiated SM Policy Association Modification procedure to forward the information received from TSN AF or TSCTSF to SMF as described in clause 4.16.5.2 of TS 23.502 [3]. SMF determines that the included information needs to be delivered to the NW-TT either by determining that the port number(s) relate(s) to a NW-TT port(s) or based on the presence of UMIC, and forwards the container(s) and/or related port number(s) to NW-TT using the N4 Session Modification procedure described in clause 4.4.1.3 of TS 23.502 [3]. + +#### 5.28.3.3 VLAN Configuration Information for TSN + +The CNC obtains the 5GS bridge VLAN configuration from TSN AF according to clause 12.10.1.1 of IEEE Std 802.1Q [98]. The TSN AF and UPF/NW-TT are pre-configured with same 5GS bridge VLAN configuration. + +NOTE: In this Release, the VLAN Configuration Information are pre-configured at the TSN AF and the NW-TT and is not exchanged between the TSN AF and the UPF/NW-TT. + +### 5.28.4 QoS mapping tables for TSN + +The mapping tables between the traffic class and 5GS QoS Profile is provisioned and further used to find suitable 5GS QoS profile to transfer TSN traffic over the PDU Session. QoS mapping procedures are performed in two phases: (1) QoS capability report phase as described in clause 5.28.1, and (2) QoS configuration phase as in clause 5.28.2 + +- (1) The TSN AF shall be pre-configured (e.g. via OAM) with a mapping table. The mapping table contains TSN traffic classes, pre-configured bridge delays (i.e. the preconfigured delay between UE and UPF/NW-TT) and priority levels. Once the PDU session has been setup and after retrieving the information related to UE-DS-TT residence time, the TSN AF deduces the port pair(s) in the 5GS bridge and determines the bridge delay per port pair per traffic class based on the pre-configured bridge delay and the UE-DS-TT residence time as described in clause 5.27.5. The TSN AF updates bridge delays per port pair and traffic class and reports the bridge delays and other relevant TSN information such as the Traffic Class Table (clause 12.6.3 in IEEE Std 802.1Q [98]) for every port, according to the IEEE Std 802.1Q [98] to the CNC. +- (2) CNC may distribute PSFP information and transmission gate scheduling parameters to 5GS Bridge via TSN AF, which can be mapped to TSN QoS requirements by the TSN AF. + +The PCF mapping table provides a mapping from TSN QoS information (see clauses 6.2.1.2 and 6.1.3.23 of TS 23.503 [45]) to 5GS QoS profile. Based on trigger from TSN AF, the PCF may trigger PDU session modification procedure to establish a new 5G QoS Flow or use the pre-configured 5QI for 5G QoS Flow for the requested traffic class according to the selected QoS policies and the TSN AF traffic requirements. + +Figure 5.28.4-1 illustrates the functional distribution of the mapping tables. + +![Diagram illustrating the functional distribution of mapping tables between PCF and TSN AF. The PCF is connected to the TSN AF via the N5 interface. The TSN AF is connected to the TSN System via the C-Plane interface. Below the PCF, a box indicates the '5QI mapping table at PCF based on TSN mapped information from TSN AF'. Below the TSN AF, a box indicates the 'QoS mapping table pre-configured at the TSN AF via OAM'.](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg) + +``` + +graph LR + PCF[PCF] --- N5((N5)) + N5 --- TSN_AF[TSN AF] + TSN_AF --- CPlane((C-Plane)) + CPlane --- TSN_System((TSN System)) + PCF --> PCF_Table[5QI mapping table at PCF based on TSN mapped information from TSN AF] + TSN_AF --> TSN_AF_Table[QoS mapping table pre-configured at the TSN AF via OAM] + +``` + +Diagram illustrating the functional distribution of mapping tables between PCF and TSN AF. The PCF is connected to the TSN AF via the N5 interface. The TSN AF is connected to the TSN System via the C-Plane interface. Below the PCF, a box indicates the '5QI mapping table at PCF based on TSN mapped information from TSN AF'. Below the TSN AF, a box indicates the 'QoS mapping table pre-configured at the TSN AF via OAM'. + +Figure 5.28.4-1: QoS Mapping Function distribution between PCF and TSN AF + +The minimum set of TSN QoS-related parameters that are relevant for mapping the TSN QoS requirements are used by the TSN AF: traffic classes and their priorities per port, TSC Burst Size of TSN streams, 5GS bridge delays per port pair and traffic class (independentDelayMax, independentDelayMin, dependentDelayMax, dependentDelayMin), propagation delay per port (txPropagationDelay) and UE-DS-TT residence time. + +Once the CNC retrieves the necessary information, it proceeds to calculate scheduling and paths. The configuration information is then set in the bridge as described in clauses 5.28.2 and 5.28.3. The most relevant information received is the PSFP information and the schedule of transmission gates for every traffic class and port of the bridge. At this point, it is possible to retrieve the TSN QoS requirements by identifying the traffic class of the TSN stream. The traffic class to TSN QoS and delay requirement (excluding the UE-DS-TT residence time) mapping can be performed using the QoS mapping table in the TSN AF as specified in TS 23.503 [45]. Subsequently in the PCF, the 5G QoS Flow can be configured by selecting a 5QI as specified in TS 23.503 [45]. This feedback approach uses the reported information to the CNC and the feedback of the configuration information coming from the CNC to perform the mapping and configuration in the 5GS. + +If the Maximum Burst Size of the aggregated TSC streams in the traffic class is provided by CNC via TSN AF to PCF, PCF can derive the required MDBV taking the Maximum Burst Size as input. If the default MDBV associated with a standardized 5QI or a pre-configured 5QI in the QoS mapping table cannot satisfy the aggregated TSC Burst Size, the PCF provides the derived MDBV in the PCC rule and then the SMF performs QoS Flow binding as specified in clause 6.1.3.2.4 of TS 23.503 [45]. + +Maximum Flow Bit Rate is calculated over StreamGateAdminCycleTime as described in Annex I and provided by the TSN AF to the PCF. The PCF sets the GBR and MBR values to the Maximum Flow Bitrate value. + +The Maximum Flow Bit Rate is adjusted according to Averaging Window associated with a pre-configured 5QI in the QoS mapping table or another selected 5QI (as specified in TS 23.503 [45]) to obtain GBR of the 5GS QoS profile. GBR is then used by SMF to calculate the GFBR per QoS Flow. QoS mapping table in the PCF between TSN parameters and 5GS parameters should match the delay, aggregated TSC burst size and priority, while preserving the priorities in the 5GS. An operator enabling TSN services via 5GS can choose up to eight traffic classes to be mapped to 5GS QoS profiles. + +Once the 5QIs to be used for TSN streams are identified by the PCF as specified in TS 23.503 [45], then it is possible to enumerate as many bridge port traffic classes as the number of selected 5QIs. + +When PSFP information is not available to the TSN AF for a given TSN stream (e.g. because of lack of PSFP support in the DS-TTs or the NW-TTs, or exceeding the number of supported table entries for PSFP functions, or because CNC does not provide PSFP information), the 5GS can support the TSN streams using pre-configured mapping from stream priority (i.e. PCP as defined in IEEE Std 802.1Q [98]) to QoS Flows. + +### 5.28.5 Support of integration with IETF Deterministic Networking + +#### 5.28.5.1 General + +5GS acts as a DetNet Router according to the architecture defined in clause 4.4.8.4. When integrated with an IETF Deterministic Network, 5GS acts as one or more routers. A 5GS router is composed of the ports on a single UPF (i.e. PSA) network side, the user plane tunnel between the UE and UPF, and the ports on the device side. For each 5GS router of a deterministic network, the ports on the network side and the ports on device side that are associated to the PDU Sessions support connectivity to the deterministic network. + +The granularity of the 5GS DetNet node is per UPF for each network instance or DNN/S-NSSAI. The TSCTSF stores the binding relationship between a device side port and a PDU Session identified by the UE address. The TSCTSF also stores information about ports on the UPF/NW-TT side. + +The integration with IETF Deterministic Networking assumes the following. + +- The existing 3GPP routing mechanisms are re-used for DetNet. +- The existing multicast capabilities can be re-used for DetNet communications. +- The 5GS integration to IETF DetNet is based on DetNet for IP; DetNet for MPLS is not supported. +- IPbased DetNet traffic is carried in Iptype PDU Sessions. + +- 5GS functions realize the DetNet forwarding sub-layer. For the IP case, according to clause 1 of IETF RFC 8939 [157], no service sub-layer function needs to be defined. The 5GS DetNet Router acts as a DetNet transit node as defined in IETF RFC 8655 [150]. + +The interface between the TSCTSF and the DetNet controller uses protocols defined in IETF. The DetNet configuration is carried in the YANG model [154] over Netconf [155] or Restconf [156]. + +#### 5.28.5.2 5GS DetNet node reporting + +The TSCTSF may provide exposure information to the DetNet controller using information collected from the 5GS entities. The exposure information can be used by the DetNet controller to build up the network topology information. The exposure may be based on IETF RFC 8343 [151] and IETF RFC 8344 [152]. + +The TSCTSF may collect the information from the UPF/NW-TT via parameters in PMIC as defined in clause 5.28.3.1. For the device side ports, the TSCTSF collects information using parameters provided from SMF to TSCTSF via PCF as described in clause 6.1.3.23b of TS 23.503 [45]. + +When the MTU size for IPv4 or IPv6 is not provided to TSCTSF for a port, the TSCTSF may use a pre-configured default value for IPv4 or IPv6. + +In the case of network side ports, the TSCTSF may collect information on the type of the interface (defined in IETF RFC 8343 [151], with values defined in IETF RFC 7224 [153]) associated with the port. In the case of device side ports, which correspond to the PDU Sessions that are reported to the TSCTSF, the default value of "3GPP WWAN" (wwanPP) for the interface type is assumed. The TSCTSF can differentiate network side ports as they are reported from the NW-TT within UMIC/PMIC, while device side ports correspond to the PDU Sessions, reported to the TSCTSF in the associated AF sessions. + +For device side ports also information on IP addresses or IP prefixes not directly assigned to the port but reachable via the port may be provided. On the device side ports, these are related to Framed Routes, i.e. a range of IPv4 addresses or IPv6 prefixes reachable over a single PDU Session, as defined in clause 5.6.14, or prefixes delegated by IPv6 prefix delegation as defined in clause 5.8.2.2. This additional information helps both the TSCTSF and the DetNet controller to map flows to the correct UE address as described in clause 5.28.5.3. For the network side ports, the TSCTSF may also collect information on the link layer address and neighbor IP nodes. + +The ports are identified by the port number within the 3GPP system. The port number may also be used to generate interface identifiers towards the DetNet controller that are unique within the 5GS node. + +NOTE 1: One possibility to generate unique interface identifiers towards the DetNet controller is to use the port number as the if-Index as defined in IETF RFC 8343 [151]. Based on the if-Index, an interface name is generated, e.g. by using the if-Index as a string, possibly adding a substring prefix or postfix based on configuration. The if-Index and the name of the interface contain essentially the same information, but both can be provided, since the name is used as the key in the YANG model, while if-Index is usually considered as the basis for interface management of IP nodes. + +The TSCTSF may use the user-plane node ID provided by the UPF to generate an identifier of the 5GS node that is provided to the DetNet controller. + +NOTE 2: The 5GS node identification can be realized by providing an identifier of the 5GS node to the DetNet controller, or the TSCTSF can use different termination points (addresses) for the signalling between the DetNet controller and the TSCTSF. + +For network side ports, the information is transferred in PMIC between the NW-TT and the TSCTSF. For device side ports, the information is transferred without relying on PMIC, using parameters from the SMF via the PCF to the TSCTSF. + +#### 5.28.5.3 DetNet node configuration mapping in 5GS + +The TSCTSF maps the parameters in the DetNet YANG configuration to 5GS parameters as defined in clause 6.1.3.23b of TS 23.503 [45]. + +The TSCTSF determines the UE address to bind the DetNet configuration as follows: + +- When available, the TSCTSF uses the identity of the incoming and outgoing interface to determine the affected UE address and whether the flow is uplink or downlink or UE-to-UE. + +- If there is no incoming interface for UL traffic, the TSCTSF may determine the UE address based on the source IP address of the UL traffic in the DetNet configuration, or using local configuration to map the DetNet flow information to the UE address. If there is no incoming interface for traffic with an outgoing interface on the device side, the TSCTSF may determine whether the flow is UE-to-UE based on the source IP address of the traffic in the DetNet configuration, or using local configuration. + +NOTE 1: The incoming interface is optional in the DetNet YANG configuration. It is assumed that any IP prefix on the device side is reachable via, at most, a single device side interface. Thus if the flow source IP address is available and belongs to a prefix associated with a device side interface, that interface can be uniquely determined as the incoming interface for the flow. + +NOTE 2: If there is no incoming interface for the UL traffic or no incoming interface for traffic with outgoing interface on the device side, the details on how the TSCTSF uses local configuration are not specified. + +- When the information on IP addresses or IP prefixes not directly assigned to the port but reachable via the port is available as described in clause 5.28.5.2, the TSCTSF also takes such info into account. +- If the flow is UE-to-UE, two PDU Sessions will be affected for the flow, and the TSCTSF breaks up the requirements to individual requirements for the PDU Sessions. + +The TSCTSF provides a response to the DetNet controller regarding the success of the configuration setup. When both the TSCTSF and the DetNet controller support 3GPP extensions to the IETF draft-ietf-detnet-yang [154], the TSCTSF may provide 5GS specific status code information on the result of the configuration to the DetNet controller. + +NOTE 3: The 3GPP extension to the IETF draft-ietf-detnet-yang [154] is defined in 3GPP as a YANG model which imports draft-ietf-detnet-yang [154] and adds the 3GPP specific parameters. The 3GPP defined YANG model uses the 3GPP namespace as defined in IETF RFC 5279 [158]. + +If the status of the flow changes later on for any reason, the TSCTSF notifies the DetNet controller. Upon release of a PDU Session that is part of the existing DetNet configuration, the PCF notifies the TSCTSF of the PDU Session release, and TSCTSF notifies the DetNet controller on the status of the flow. + +The 5GS routing is not modified by the configuration received from the DetNet controller. Still the TSCTSF may verify whether the explicit routing information provided by the DetNet controller is in line with the 5GS mapping of IP addresses and prefixes to PDU sessions. The verification may be based on whether the source or destination IP address in the DetNet flow on the given port corresponds to the IP address or prefix associated with the given PDU Session. Based on operator configuration, the TSCTSF may use other criteria (not routing related) to determine whether to accept or reject a given DetNet configuration. + +5GS DetNet Node can forward via its device side interface IP packets destined not only to the UE's IP address or prefix but also to a range of IPv4 addresses or IPv6 IP prefixes according to one or more Framed Routes or prefixes delegated to the UE by IPv6 prefix delegation. To facilitate this, the additional IP addresses used for framed routes and IPv6 prefix delegation are exposed by the SMF to the TSCTSF via the PCF and the TSCTSF may expose them to the DetNet controller, as defined in clause 5.28.5.2. + +## 5.28a Support for TSN enabled Transport Network + +### 5.28a.1 General + +When the 5GS supports interworking with IEEE TSN deployed in the transport network, the CUC that is collocated with SMF interworks with the CNC in the transport network (TN CNC) as specified in clause 46.2 of IEEE Std 802.1Q [98]. The SMF/CUC provides the stream requirements on QoS Flow basis (i.e. translated Talker group and Listener group information) via the User/Network-Interface (UNI) to the TN CNC. The TN CNC uses the stream requirements as input to configure respective path(s) and schedules in TN. Based on the results, the TN CNC provides a Status group that contains the end station communication-configuration back to the SMF/CUC. + +When interworking with TSN deployed in the transport network is applied, the dynamic value for the CN PDB of a Delay-critical GBR 5QI shall be configured in the SMF as described in clause 5.7.3.4. When the SMF setups a new QoS Flow, the SMF signals the dynamic value for the CN PDB and TSCAI for the QoS Flow to NG-RAN on QoS Flow basis. Upon receiving the TSCAI for a QoS Flow from the SMF, if the TSCAI includes a BAT in UL direction, the RAN may determine a dynamic value of 5G-AN PDB in UL direction for the QoS Flow. The NG-RAN provides the + +dynamic value of 5G-AN PDB to the SMF in a response to the QoS Flow request. The dynamic value of 5G-AN PDB is used to generate EarliestTransmitOffset as described in Annex M. + +The details of providing End Station related information to generate the stream requirements for the QoS Flow by the SMF/CUC are described in Annex M. + +If the NG-RAN and UPF support the TSN Talker and Listener functionality (i.e. implement the AN-TL and CN-TL, respectively), the SMF/CUC can communicate with the AN-TL and CN-TL via TL-Container. The TL-Container conveys the data sets defined in IEEE P802.1Qdj [146] between the SMF/CUC and AN-TL and CN-TL. + +The AN-TL and CN-TL enable the following functions: + +- a) hold and buffer functionality in a case when the TSCAI contains a BAT in UL and/or DL direction. +- b) support of stream transformation functionality with respective information exchange with SMF/CUC. +- c) for SMF/CUC to retrieve the InterfaceCapabilities and/or EndStationInterfaces from the AN-TL or CN-TL. +- d) topology information exchange functionality via LLDP in the TN as described in clause 5.28a.3. + +NOTE 1: How to realize AN-TL in the base station and CN-TL in UPF is up to implementation. + +NOTE 2: In this Release of the specification, it is assumed that connected mode mobility is not used in deployments with a TSN enabled TN. + +### 5.28a.2 Transfer of TL-Container between SMF/CUC and AN-TL and CN-TL + +If NG-RAN and UPF support AN-TL and CN-TL, the SMF/CUC may use the TL-Container to send a: + +- 1) get-request. +- 2) set-request: submits the following information elements to the AN-TL or CN-TL: + - InterfaceConfiguration as described in Annex M, clause M.1 (one InterfaceConfiguration is associated with each QFI in the N3 tunnel) + - Interface ID Group. + - TN Stream Identification Information for DataFrameSpecification. + - TN Stream Identification Information for mask-and-match. + - Interval (only provided together with TimeAwareOffset). + - MaxFrameSize (only provided together with TimeAwareOffset). + +The AN-TL or CN-TL may use the TL-Container to send a: + +- 1) get-response: indicates the following elements of the Talker or Listener group from the AN-TL or CN-TL: + - EndStationInterfaces: list of InterfaceIDs. + - InterfaceCapabilities. + - Buffer capability: maximum possible buffer duration for a packet of a stream with the maximum size of an Ethernet packet (1522 Bytes) that is supported by the AN-TL / CN-TL when acting as a Talker. +- 2) set-response: reports the processing results for the corresponding set-request to the SMF/CUC. + +Details on the TL-Container information are provided in Table M.2-1 of clause M.2. + +The SMF/CUC may request the NG-RAN/UPF to report AN-TL or CN-TL information by including a TL-Container with a get-request to the AN-TL or CN-TL, respectively. The get-request is sent to AN-TL in the N2 SM information and to CN-TL in the N4 Session Establishment as described in clause 4.3.2.2 of TS 23.502 [3]. + +If the NG-RAN/UPF supports AN-TL/CN-TL, the NG-RAN/AN-TL and UPF/CN-TL responds with a TL-Container including the elements defined for the get-response. + +The SMF/CUC may submit TL-Container including a set-request the elements defined for the set-request to NG-RAN/AN-TL and UPF/CN-TL. The set-request is sent to AN-TL in the N2 SM information and to CN-TL in the N4 Session Modification request as described in clause 4.3.3.2 of TS 23.502 [3]. The SMF/CUC shall initiate to the CN-TL/AN-TL the deletion of TN stream configurations as described in 4.3.4.2 of TS 23.502 [3]. + +The InterfaceConfiguration is associated with the corresponding QFI in the N3 tunnel in the NG-RAN or UPF, respectively. The AN-TL/CN-TL uses the provided configuration for the traffic in the QoS Flow of the given QFI as described in Annex M. + +### 5.28a.3 Topology Information for TSN TN + +NG-RAN and UPF may support u-plane LLDP functionality to provide topology information to the TN. When LLDP is supported, AN-TL and CN-TL shall perform the LLDP functionality at the u-plane without the need to interact with the c-plane. Further there is no need for 5GS interaction with TN CNC directly. This is achieved with following measures: + +- AN-TL and CN-TL implement the Transmit Only operation mode as defined in clause 9.1 of IEEE Std 802.1AB [97]. +- The TSN End Station is pre-configured with parameter set for Transmit Only operating mode as defined in clause 9.2 of IEEE Std 802.1AB [97]. +- The System Capabilities TLV may also be set to Station Only as defined in clause 8.5.8 of IEEE Std 802.1AB [97]. + +## 5.29 Support for 5G LAN-type service + +### 5.29.1 General + +The service requirements for 5G LAN-type service are specified in TS 22.261 [2]. + +A 5G Virtual Network (VN) group consists of a set of UEs using private communication for 5G LAN-type services. + +### 5.29.2 5G VN group management + +5G System supports management of 5G VN Group identification and membership (i.e. definition of 5G VN group identifiers and membership) and 5G VN Group data (i.e. definition of 5G VN group data). The 5G VN Group management can be configured by a network administrator or can be managed dynamically by AF. + +A 5G VN group is characterized by the following: + +- 5G VN group identities: External Group ID and Internal Group ID are used to identify the 5G VN group. +- 5G VN group membership: The 5G VN group members are uniquely identified by GPSI. The group as described in clause 5.2.3.3.1 of TS 23.502 [3] is applicable to 5G LAN-type services. +- 5G VN group data. The 5G VN group data may include the following parameters: PDU session type, DNN, S-NSSAI and Application descriptor, the indication that the 5G VN group is associated with 5G VN group communication, Information related with secondary authentication / authorization (e.g. to enable IP address assignment by the DN-AAA, Maximum Group Data Rate). + +The Information related with secondary authentication / authorization corresponds to the procedures described in clause 5.6.6; it allows e.g. the AF to provide DN-AAA server addressing information and possibly to request the SMF to get the UE IP address from the DN-AAA server. + +In order to support dynamic management of 5G VN Group identification and membership, the NEF exposes a set of services to manage (e.g. add/delete/modify) 5G VN groups and 5G VN members. The NEF also exposes services to dynamically manage 5G VN group data. + +An AF can request provisioning of traffic characteristics, QoS parameters and monitoring of QoS parameters for a 5G VN group as described in clause 6.1.3.28 of TS 23.503 [45]. + +A 5G VN group is identified by the AF using External Group ID. The NEF provides the External Group ID to UDM. The UDM maps the External Group ID to Internal Group ID. For a newly created 5G VN Group, an Internal Group ID is determined by the UDM based on implementation specific means. + +NOTE 1: The Internal Group ID determined by UDM has to comply with the format defined in TS 23.003 [19]. + +The NEF can retrieve the Internal Group ID from UDM via Nudm\_SDM\_Get service operation (External Group ID, Group Identifier translation). + +An External Group ID for a 5G VN group corresponds to a unique set of 5G VN group data parameters. + +The 5G VN group configuration is either provided by OA&M or provided by an AF to the NEF. + +When configuration is provided by an AF, the procedures described in clause 4.15.6.2 of TS 23.502 [3] apply for storing the 5G VN group identifiers, group membership information and group data in the UDR, as follows: + +- The NEF provides the External Group ID, 5G VN group membership information and 5G VN group data to the UDM. +- The UDM updates the Internal Group ID-list of the corresponding UE's subscription data in UDR, if needed. +- The UDM updates the Group Identifier translation in the Group Subscription data with the Internal Group ID, External Group ID and list of group members, if needed. +- The UDM stores/updates the 5G VN group data (PDU session type, DNN and S-NSSAI, Application descriptor, the indication that the 5G VN group is associated with 5G VN group communication, Information related with secondary authentication / authorization, Maximum Group Data Rate) in UDR. + +NOTE 2: It is assumed that all members of a 5G VN group belong to the same UDM Group ID. The NEF can select a UDM instance supporting the UDM Group ID of any of the member GPSIs of the 5G VN group. + +NOTE 3: Shared data mechanisms as defined in TS 29.503 [122] can be used to support large 5G VN groups. + +An AF may also configure and update the service area, QoS for the 5G VN group as described in clause 5.20b as well as other parameters (e.g. Expected UE Behaviour parameters, Network Configuration parameters, ECS Address Configuration Information, etc.) for a 5G VN group as described in clause 4.15.6 of TS 23.502 [3]. + +If a UE is member of a 5G VN Group, UDM retrieves UE subscription data and corresponding 5G VN group data from UDR, and provides the AMF and SMF with UE subscription data with 5G VN group data included. If the 5G VN group data contains the indication that the 5G VN group is associated with 5G VN group communication, the SMF may apply the 5G VN group communication as defined in clauses 5.29.3 and 5.29.4 for the PDU Sessions accessing to the 5G VN group. + +The PCF generates URSP rules based on 5G VN group data. The PCF retrieves 5G VN group data from UDR. The PCF(s) that have subscribed to modifications of 5G VN group data receive(s) a Nudr\_DM\_Notify notification of 5G VN group data change from the UDR as defined in TS 29.505 [145]. The PCF receives from the AMF at the UE Policy association establishment the Internal Group ID(s) corresponding to a UE, so that PCF identifies the 5G VN group data that needs to be used to generate URSP rules to the UE. If the PCF is made aware of a change of UE Internal Group Identifier(s) as defined in TS 29.525 [144] or change of 5G VN group membership as defined in TS 29.505 [145], or both, the PCF then may update the URSP rules for the impacted 5G VN group members. + +NOTE 4: The proper way to obtain the 5G VN group membership changes of a specific UE, e.g. if the UE is added to a new 5G VN group, is via the notification of change of UE Internal Group Identifier(s) from the AMF as specified in TS 29.525 [144]. The subscription in the UDR is for being notified about changes in the 5G VN group data and in the 5G VN group membership of a specific 5G VN group. + +If the PCF receives the Maximum Group Data Rate as part of the 5G VN group data, it performs the group related policy control as described in clauses 6.1.5 and 6.2.1.11 of TS 23.503 [45]. + +An AF may update the UE Identities of the 5G VN group at any time after the initial provisioning. + +An AF may subscribe to notification of the group status changes for the 5G VN group as described in clause 5.20. + +The DNN, S-NSSAI provided within 5G VN group data cannot be modified after the initial provisioning. + +In this Release of the specification, the home network of the 5G VN group members is same. + +In this Release of the specification, only a 1:1 mapping between (DNN, S-NSSAI) combination and 5G VN group is supported. + +The PCF delivers 5G VN group configuration information (DNN, S-NSSAI, PDU session type) to the UE for each GPSI that belongs to a 5G VN group. The 5G VN group configuration information is delivered in the URSP from the PCF to the UE using the UE Configuration Update procedure for transparent UE Policy delivery as described in clause 4.2.4.3 of TS 23.502 [3] and clause 6.1.2.2 of TS 23.503 [45]. + +### 5.29.3 PDU Session management + +Session management as defined for 5GS in clause 5.6 is applicable to 5G-VN-type services with the following clarification and enhancement: + +- A UE gets access to 5G LAN-type services via a PDU Session of IP PDU Session type or Ethernet PDU Session type. +- A PDU Session provides access to one and only one 5G VN group. The PDU Sessions accessing to a certain 5G VN group should all anchor at the same network, i.e. the common home network of 5G VN group members. +- A DNN and S-NSSAI is associated with a 5G VN group. +- A dedicated SMF, a dedicated SMF Set or multiple SMF (Sets) can be responsible for all the PDU Sessions for communication of a certain 5G VN group. Multiple SMF (Sets) may apply for a 5G VN group extended over a large area, bigger than the service area of any SMF Set serving the DNN/S-NSSAI of the 5G VN group. SMF selection is described in clause 6.3.2. + +NOTE 1: If a dedicated SMF (Set) is used to serve a 5G VN, the network is configured so that the same SMF (Set) is always selected for a certain 5G VN group, e.g. only one SMF, or SMFs in one SMF Set, registers on the NRF with the DNN/S-NSSAI used for a given 5G VN group. + +NOTE 2: Having a dedicated SMF serving a 5G VN does not contradict that redundancy solutions can be used to achieve high availability. If SMF Set(s) serve the 5G VN group, high availability is achieved by the set functionality. + +- In the case that more than one SMF sets or SMF instances in a SMF Set are responsible for all the PDU Sessions for communication of a certain 5G VN group to enable SMF redundancy for reliability of the 5G VN group communication: + - The associations between one or more SMF Sets and the DNN, S-NSSAI of the associated 5G VN group is registered and discovered in NRF. + - The SMFs that registered to associate with the DNN, S-NSSAI of the 5G VN group should be available in the LADN service area of the 5G VN group. +- The UE provides the DNN and S-NSSAI associated with the 5G VN group to access the 5G LAN-type services for that 5G VN, using the PDU Session Establishment procedure described in clause 4.3.2 of TS 23.502 [3]. +- During establishment of the PDU Session, secondary authentication as described in clause 5.6.6 and in clause 4.3.2.3 of TS 23.502 [3], may be performed in order to authenticate and authorize the UE for accessing the DNN and S-NSSAI associated with the 5G VN group. Authentication and authorization for a DNN and S-NSSAI using secondary authentication implies authentication and authorization for the associated 5G VN group. There is no 5G VN group specific authentication or authorization defined. +- The SM level subscription data for a DNN and S-NSSAI available in UDM, as described in clause 5.6.1, applies to the DNN and S-NSSAI associated to a 5G VN group. +- Session management related policy control for a DNN and S-NSSAI as described in TS 23.502 [3], is applicable to the DNN and S-NSSAI associated to a 5G VN group. This includes also usage of URSP, for the UE to determine how to route outgoing traffic to a PDU Session for the DNN and S-NSSAI associated to a 5G VN group. +- Session and service continuity SSC mode 1, SSC mode 2, and SSC mode 3 as described in clause 5.6.9 are applicable to N6-based traffic forwarding of 5G VN communication within the associated 5G VN group. + +- A PDU Session provides unicast, broadcast and multicast communication for the DNN and S-NSSAI associated to a 5G VN group. The PSA UPF determines whether the communication is for unicast, broadcast or multicast based on the destination address of the received data, and performs unicast, broadcast or multicast communication handling. +- During the PDU Session Establishment procedure, the SMF retrieves SM subscription data related to 5G-VN type service from the UDM as part of the UE subscription data for the DNN and S-NSSAI. +- In order to realize N19 traffic routing in the case that a single SMF (or single SMF Set) is serving the 5G VN, the SMF (or SMF Set) correlates PDU sessions established to the same 5G VN group and uses this to configure the UPF with the group level N4-session including packet detection and forwarding rules for N19 tunnelling forwarding. + +NOTE 3: In the case of a SMF Set serving a 5G VN, implementation dependent mechanism can be used between SMF(s) that are part of a SMF Set to control the N19 configuration. + +- In order to realize N6/N19 traffic routing between PSA UPFs in case multiple SMF Sets are serving the 5G VN, traffic forwarding between UPFs belonging to different SMF (Set)s can be realized via User Plane tunnels that are configured using OAM between UPFs served by different SMF (Set)s. How to implement the user plane tunnels and traffic forwarding configured between these UPFs is up to network implementation and deployment and is out of scope of this specification. + +### 5.29.4 User Plane handling + +User Plane management as defined for 5GS in clause 5.8 is applicable to 5G LAN-type services with the following clarifications: + +- There are three types of traffic forwarding methods allowed for 5G VN communication: + - N6-based, where the UL/DL traffic for the 5G VN communication is forwarded to/from the DN; + +NOTE 1: Optionally a L2TP tunnel can be established over N6 as described in clause 5.8.2.16. + +- N19-based, where the UL/DL traffic for the 5G VN group communication is forwarded between PSA UPFs of different PDU sessions via N19. N19 is based on a shared User Plane tunnel connecting PSA UPFs of a single 5G VN group. +- Local switch, where traffic is locally forwarded by a single UPF if this UPF is the common PSA UPF of different PDU Sessions for the same 5G VN group. +- For UPFs served by a single SMF Set, the SMF instance(s) in the SMF set handles the user plane paths of the 5G VN group, including: + - The SMF instance(s) may prefer to select a single PSA UPF for as many PDU sessions (targeting the same 5G VN group) as possible, in order to implement local switch on the UPF. + - (if needed) Establishing N19 tunnels between PSA UPFs served by the same SMF set to support N19-based traffic forwarding. +- If multiple SMF (Set)s are serving a 5G VN, user plane forwarding between UPFs served by different SMF (Set)s can be achieved via the DN (i.e. N6) or via user plane tunnels on N6/N19 as described in clause 5.29.3. + +NOTE 2: The above user plane tunnels may be using GTP-U or IETF VPN. For example, for IP-type traffic, the traffic routing can be based on routing protocols or pre-configured IP address ranges/prefixes corresponding different SMF sets; for ethernet-type traffic, the traffic routing can be based on the learned MAC address over the user plane tunnels between UPFs controlled by different SMF sets, etc. How to implement such user plane tunnels configured between these UPFs is up to network implementation and deployment. + +- For Ethernet PDU Session, the SMF may instruct the UPF(s) to classify frames based on VLAN tags, and to add and remove VLAN tags, on frames received and sent on N6 or N19 or internal interface ("5G VN internal"), as described in clause 5.6.10.2. + +NOTE 3: For handling VLAN tags for traffic on N6, TSP ID could also be used as described in clause 6.2.2.6 of TS 23.503 [45]. + +Further description on User Plane management for 5G VN groups is available in clause 5.8.2.13. + +When N6-based traffic forwarding is expected, after creation of a 5G VN group the AF can influence the traffic routing for all the members of the 5G VN group, by providing information identifying the traffic, DNAI(s) suitable for selection and an optional indication of traffic correlation together with a 5G VN External Group ID identifying the 5G VN group in an AF request sent to the PCF, as described in clause 5.6.7. If the optional indication of traffic correlation is provided, it means the PDU sessions of the 5G VN group member UEs should be correlated by a common DNAI in the user plane for the traffic. The PCF transforms the AF request into policies that apply to PDU Sessions of the 5G VN group and sends the policies to the SMF. According to the policies, the SMF (re)selects DNAI(s) for the PDU Sessions and configures their UP paths to route the traffic to the selected DNAI(s). If the policies include the traffic correlation indication, the SMF (re)selects a common DNAI for the PDU Sessions so that the traffic of the 5G VN group is routed to the common DNAI. + +NOTE 4: When receiving a new PDU session establishment request for a 5G VN group, to avoid unnecessary N19 tunnels between UPFs, SMF can check previously selected UPFs for the same 5G VN group, and decide whether a previously selected UPF could serve the requested PDU session. + +NOTE 5: N19 tunnel(s) can be established between a new UPF and other UPF(s) that belongs to a 5G VN group when the new UPF is selected for the 5G VN group during PDU session establishment. The N19 tunnel(s) to a UPF can be released during or after PDU session release when there is no more PDU sessions for a 5G VN group in that UPF. Establishment or release of the N19 tunnels at the UPF is performed within a group-level N4 Session. + +## 5.30 Support for non-public networks + +### 5.30.1 General + +A Non-Public Network (NPN) is a 5GS deployed for non-public use, see TS 22.261 [2]. An NPN is either: + +- a Stand-alone Non-Public Network (SNPN), i.e. operated by an NPN operator and not relying on network functions provided by a PLMN, or +- a Public Network Integrated NPN (PNI-NPN), i.e. a non-public network deployed with the support of a PLMN. + +NOTE: An NPN and a PLMN can share NG-RAN as described in clause 5.18. + +Stand-alone NPN are described in clause 5.30.2 and Public Network Integrated NPNs are described in clause 5.30.3. + +### 5.30.2 Stand-alone Non-Public Networks + +#### 5.30.2.0 General + +SNPN 5GS deployments are based on: + +- the architecture depicted in clause 4.2.3; +- the architecture for 5GC with Untrusted non-3GPP access (Figure 4.2.8.2.1-1) for either access to SNPN services via a PLMN (and vice versa) or for direct access to SNPN via non-3GPP access; +- the architecture for 5GC with Trusted non-3GPP access (Figure 4.2.8.2.1-2); and +- the additional functionality covered in clause 5.30.2. + +Alternatively, a Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the Credentials Holder based on the architecture specified in clause 5.30.2.9. Idle and connected mode mobility is supported as defined in clause 5.30.2.11. + +Clauses 5.30.2.1 to 5.30.2.11 specify the common SNPN aspects applicable to both 3GPP and non-3GPP access, except where stated differently. + +Aspects specific to Untrusted non-3GPP access for SNPN are specified in clause 5.30.2.12. + +Aspects specific to Trusted non-3GPP access for SNPN are specified in clause 5.30.2.13. + +Aspects specific to N5CW devices accessing SNPN services are specified in clause 5.30.2.15. + +The following 5GS features and functionalities are not supported for SNPNs: + +- Interworking with EPS; +- Emergency services when the UE accesses the SNPN over NWu via a PLMN; +- Roaming, e.g. roaming between SNPNs. However, it is possible for a UE to access an SNPN with credentials from a CH as described in clause 5.30.2.9 and to move between equivalent SNPNs; +- Handover between SNPN and PLMN or PNI-NPN; +- CIoT 5GS Optimizations; +- CAG; and +- Proximity based Services (ProSe) as defined in TS 23.304 [128]. + +A UE with two or more network subscriptions, where one or more network subscriptions may be for a subscribed SNPN, can apply procedures specified for Multi-USIM UEs as described in clause 5.38. The UE shall use a separate PEI for each network subscription when it registers to the network. + +NOTE: The number of preconfigured PEIs for a UE is limited. If the number of network subscriptions for a UE is greater than the preconfigured number of PEIs, the number of network subscriptions that can be registered with the network simultaneously is restricted by the number of pre-configured number of PEIs. + +#### 5.30.2.1 Identifiers + +The combination of a PLMN ID and a Network identifier (NID) identifies an SNPN. + +NOTE 1: The PLMN ID used for SNPNs is not required to be unique. PLMN IDs reserved for use by private networks can be used for non-public networks, e.g. based on mobile country code (MCC) 999 as assigned by ITU [78]). Alternatively, a PLMN operator can use its own PLMN IDs for SNPN(s) along with NID(s), but registration in a PLMN and mobility between a PLMN and an SNPN are not supported using an SNPN subscription given that the SNPNs are not relying on network functions provided by the PLMN. + +The NID shall support two assignment models: + +- Self-assignment: NIDs are chosen individually by SNPNs at deployment time (and may therefore not be unique) but use a different numbering space than the coordinated assignment NIDs as defined in TS 23.003 [19]. +- Coordinated assignment: NIDs are assigned using one of the following two options: + 1. The NID is assigned such that it is globally unique independent of the PLMN ID used; or + 2. The NID is assigned such that the combination of the NID and the PLMN ID is globally unique. + +NOTE 2: Which legal entities manage the number space is beyond the scope of this specification. + +NOTE 3: The use of SNPN with self-assignment model NID such that the combination of PLMN ID and NID is not globally unique is not assumed for the architecture described in Figure 5.30.2.9.3-1, Figure 5.30.2.9.2-1 and for SNPN - SNPN Mobility as described in clause 5.30.2.11. + +The GIN shall support two assignment models: + +- Self-assignment: GINs are chosen individually and may therefore not be unique. It is defined as in TS 23.003 [19]; or +- Coordinated assignment: GIN uses a combination of PLMN ID and NID and is assigned using one of the following two options as defined in TS 23.003 [19]: + 1. The GIN is assigned such that the NID is globally unique (e.g. using IANA Private Enterprise Numbers) independent of the PLMN ID used; or + +2. The GIN is assigned such that the combination of the NID and the PLMN ID is globally unique. + +NOTE 4: Which legal entities manage the number space for GIN is beyond the scope of this specification. + +An optional human-readable network name helps to identify an SNPN during manual SNPN selection. The human-readable network name and how it is used for SNPN manual selection is specified in TS 22.261 [2] and TS 23.122 [17]. + +#### 5.30.2.2 Broadcast system information + +NG-RAN nodes or Trusted non-3GPP access networks which provide access to SNPNs broadcast the following information: + +- One or multiple PLMN IDs; +- List of NIDs per PLMN ID identifying the non-public networks NG-RAN provides access to; and + +NOTE 1: It is assumed that an NG-RAN node supports broadcasting a total of twelve NIDs. Further details are defined in TS 38.331 [28]. + +NOTE 2: The presence of a list of NIDs for a PLMN ID indicates that the related PLMN ID and NIDs identify SNPNs. + +- Optionally: + - A human-readable network name per SNPN; + +NOTE 3: The human-readable network name per SNPN is only used for manual SNPN selection. If the SNPN supports Localized Service, the human-readable network name of the SNPN can be information related to the Localized Service. The mechanism how human-readable network name is provided (i.e. whether it is broadcasted or unicasted) to the UE is specified in TS 38.331 [28]. + +- Information, as described in TS 38.300 [27], TS 38.331 [28] and in TS 38.304 [50], to prevent UEs not supporting SNPNs from accessing the cell, e.g. if the cell only provides access to non-public networks; +- An indication per SNPN of whether access using credentials from a Credentials Holder is supported; +- List of supported Group IDs for Network Selection (GINs) per SNPN; and +- An indication per SNPN of whether the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. UEs that do not have any PLMN ID and NID nor GIN broadcast by the SNPN in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs. + +NOTE 4: Further details (including number of supported GINs per SNPN) are defined in TS 38.331 [28]. + +#### 5.30.2.3 UE configuration and subscription aspects + +An SNPN-enabled UE is configured with the following information for each subscribed SNPN: + +- PLMN ID and NID of the subscribed SNPN; +- Subscription identifier (SUPI) and credentials for the subscribed SNPN; +- Optionally, an N3IWF FQDN and the MCC of the country where the configured N3IWF is located; +- Optionally, if the UE supports access to an SNPN using credentials from a Credentials Holder: + - User controlled prioritized list of preferred SNPNs; + - Credentials Holder controlled prioritized list of preferred SNPNs; + - Credentials Holder controlled prioritized list of GINs; +- Optionally, if the UE supports access to an SNPN using credentials from a Credentials Holder and access to an SNPN providing access for Localized Services: + - User controlled prioritized list of preferred SNPNs; + +- Credentials Holder controlled prioritized list of preferred SNPNs for accessing Localized Services, each entry of the list includes: + - an SNPN identifier; + - validity information; and + - optionally, location assistance information; +- Credentials Holder controlled prioritized list of GINs for accessing Localized Services, each entry of the list includes: + - a GIN; + - validity information; and + - optionally, location assistance information; +- Protection scheme for concealing the SUPI as defined in TS 33.501 [29]. + +NOTE 1: Additionally the UE can be configured with indication to use anonymous SUCI as defined in TS 24.501 [47]. + +Validity information consists of: + +- Time validity information, i.e. time periods (defined by start and end times) when access to the SNPN for accessing Localized Services is allowed; and/or + +Location assistance information consisting of: + +- Geolocation information, and/or, +- Tracking Area information of serving networks, i.e. lists of TACs per PLMN ID or per PLMN ID and NID. + +The UE may use the location assistance information to determine where to search for the SNPNs in the Credentials Holder controlled prioritized list of SNPNs and GINs for accessing Localized Services, i.e. the location assistance information is not used for any area restriction enforcement. + +For an SNPN-enabled UE with SNPN subscription, the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services may be updated by the Credentials Holder using the Steering of Roaming (SoR) procedure as defined in Annex C of TS 23.122 [17]. Updating Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services via the Steering of Roaming (SoR) procedure is not applicable for Credentials Holder with AAA Server. + +A subscription of an SNPN is either: + +- identified by a SUPI containing a network-specific identifier that takes the form of a Network Access Identifier (NAI) using the NAI RFC 7542 [20] based user identification as defined in clause 28.7.2 of TS 23.003 [19]. The realm part of the NAI may include the NID of the SNPN; or +- identified by a SUPI containing an IMSI. + +NOTE 2: As to route network signalling to AUSF and UDM instances serving the SNPN-enabled UE, the UE can be configured with Routing Indicator locally or updated with Routing Indicator using the UE Parameters Update via UDM Control Plane procedure defined in clause 4.20 of TS 23.502 [3]. When the SNPN credential is stored in the USIM, the Routing Indicator is provisioned in the USIM, when the SNPN credential is stored in the ME, the Routing Indicator is provisioned in the ME. + +In the case of access to an SNPN using credentials owned by a Credentials Holder as specified in clause 5.30.2.9.2 and clause 5.30.2.9.3, the SUPI shall also contain identification for the Credentials Holder (i.e. the realm in the case of Network Specific Identifier based SUPI or the MCC and MNC in the case of an IMSI based SUPI). In the case of access to an SNPN using credentials owned by a Credentials Holder using AAA-S as specified in clause 5.30.2.9.2, only Network Specific Identifier based SUPI is supported. + +NOTE 3: When Credentials Holder is an SNPN, and the MCC and MNC of the SNPN is not unique (e.g. MCC =999 is used and MNC is not coordinated amongst the SNPNs), then IMSI based SUPI is not supported as the MCC and MNC need not be globally unique always; instead USIM credentials are supported using Network Specific Identifier based SUPI. + +NOTE 4: Network Specific Identifier are not supported for the case the Credentials Holder is provided by a PLMN. + +NOTE 5: It is assumed that normally the SNPN and the Credentials Holder use different PLMN ID. If the SNPN and CHs (where CH can be another SNPN or a PLMN) share PLMN ID, and IMSI based SUPI is used, then the Routing Indicator can be used for AUSF/UDM discovery and selection as long as the Routing Indicator values are coordinated among the involved SNPN and CHs. When the PLMN ID is not shared between SNPNs and CHs (where CH can be another SNPN or a PLMN) and IMSI based SUPI is used, then PLMN ID is sufficient to be used for AUSF/UDM discovery & selection unless the CHs deploys multiple AUSF/UDM in which case also the Routing Indicator can be used as long as the Routing Indicator values are coordinated within the CH. + +An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription may additionally be configured with the following information for SNPN selection and registration using the PLMN subscription in SNPN access mode: + +- User controlled prioritized list of preferred SNPNs; +- Credentials Holder controlled prioritized list of preferred SNPNs; +- Credentials Holder controlled prioritized list of preferred GINs. +- Optionally if the UE supports access to an SNPN providing access for Localized Services: + - Credentials Holder controlled prioritized list of preferred SNPNs for accessing Localized Services, each entry of the list includes: + - an SNPN identifier; + - validity information; and + - optionally, location assistance information; + - Credentials Holder controlled prioritized list of preferred GINs for accessing Localized Services, each entry of the list includes: + - a GIN; + - validity information; and + - optionally, location assistance information. + +Validity information consists of: + +- Time validity information, i.e. time periods (defined by start and end times) when access to the SNPN for accessing Localized Services is allowed; and/or, + +Location assistance information consisting of: + +- Geolocation information, and/or, +- Tracking Area information of serving networks, i.e. lists of TACs per PLMN ID or per PLMN ID and NID. + +The UE may use the location assistance information to determine where to search for the SNPNs in the Credentials Holder controlled prioritized list of SNPNs and GINs for accessing Localized Services, i.e. the location assistance information is not used for any area restriction enforcement. + +For an SNPN-enabled UE with PLMN subscription, the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, or the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services may be updated by the Credentials Holder using the Steering of Roaming (SoR) procedure as defined in Annex C of TS 23.122 [17]. + +When the Credentials Holder updates a UE with the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, and/or the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services, the UE may perform SNPN selection again, e.g. to potentially select a higher prioritized SNPN or to potentially select an SNPN that provides access for Localized Services. + +#### 5.30.2.4 Network selection in SNPN access mode + +##### 5.30.2.4.1 General + +An SNPN-enabled UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode the UE selects and registers with SNPNs over Uu as described in clause 5.30.2.4. Network selection in SNPN access mode for access to SNPN services via Untrusted non-3GPP access, Trusted non-3GPP access and Wireline access is specified in clause 5.30.2.12, clause 5.30.2.13 and clause 5.30.2.14 respectively. Access network selection in SNPN access mode for 5G NSWO is specified in clause 6.3.12b. + +Emergency services are supported in SNPN access mode over Uu as defined in clause 5.16.4.1. Support for Emergency in SNPN access mode via Untrusted non-3GPP access is specified in clause 5.30.2.12. + +If a UE is not set to operate in SNPN access mode, even if it is SNPN-enabled, the UE does not select and register with SNPNs. A UE not set to operate in SNPN access mode performs PLMN selection procedures as defined in clause 4.4 of TS 23.122 [17]. For a UE capable of simultaneously connecting to an SNPN and a PLMN, the setting for operation in SNPN access mode is applied to each of the Uu/Yt/NWu interfaces independently. Clause D.4 provides more details. + +An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription needs to first enter SNPN access mode to be able to select SNPNs. Once the UE has entered SNPN access mode, SNPN selection is performed as described in clause 5.30.2.4. Once an SNPN has been selected the UE attempts registration in the SNPN using the PLMN credentials. + +NOTE 1: Details of activation and deactivation of SNPN access mode are up to UE implementation. + +When a UE is set to operate in SNPN access mode the UE does not perform normal PLMN selection procedures as defined in clause 4.4 of TS 23.122 [17]. + +UEs operating in SNPN access mode read the information described in clause 5.30.2.2 from the broadcast system information and take them into account during network selection. Furthermore, if the UE supports access to an SNPN providing access for Localized Services, and the end user enables to access the Localized Services the UE may select an SNPN providing access for Localized Services. + +NOTE 2: Details of how the user enables/disables access to Localized Services are up to UE implementation. + +##### 5.30.2.4.2 Automatic network selection + +NOTE 1: If the UE has multiple subscriptions (SNPN and/or PLMN) it is assumed that the subscription to use for automatic selection is determined by implementation specific means prior to network selection. + +If the UE supports accessing an SNPN providing access for Localized Services and the end user enables to access Localized Services, for automatic network selection, the UE shall select and attempts registration on available SNPN in the following order: + +- (a) if the UE supports access to an SNPN using Credentials from a Credentials Holder then the UE continues by selecting and attempting registration on available and allowable SNPNs which broadcasts the indication that access using credentials from a Credentials Holder is supported in the following order: + - i the SNPN with the validity information the UE was last registered with (if the validity information is met) or the SNPN's equivalent SNPN(s) (if available and the validity information of the SNPN that the UE was last registered with is met); + +NOTE 2: The equivalent SNPN(s) are assumed to provide access to the same Localized Services as the SNPN the UE was last registered with. + +- ii SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs for accessing Localized Services (in priority order) if the validity information is met; + +- iii SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs for accessing Localized Services (in priority order) if validity information is met; +- (b) the SNPN without validity information the UE was last registered with (if available) or the equivalent SNPN (if available); +- (c) the subscribed SNPN, which is identified by the PLMN ID and NID for which the UE has SUPI and credentials; +- (d) the available and allowable SNPNs which broadcast the indication that access using credentials from a Credentials Holder is supported in the following order: + - i SNPNs in the user controlled prioritized list of preferred SNPNs (in priority order); + - ii SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs (in priority order); + - iii SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs (in priority order); + - iv- SNPNs, which additionally broadcast an indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. the broadcasted NID or GIN is not present in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs, nor in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services in the UE. + +If the UE supports accessing an SNPN providing access for Localized Services and the end user enables to access Localized Services, the UE shall periodically attempt reselection and registration on a higher priority SNPN 1) based on the order of the above sub-bullets (i) to (iii) of bullet (a), bullet (c), sub-bullets (i) to (iii) of bullet (d) if the UE is not registered to the sub-bullet (i) of bullet (a) or 2) based on the order of the above sub-bullets (ii) to (iii) of bullet (a), bullet (c), sub-bullets (i) to (iii) of bullet (d) if the UE is registered to the sub-bullet (i) of bullet (a) if any of the below conditions is met: + +- if there are one or more SNPNs with validity information which is met, and the UE is not registered to an SNPN which has highest priority among the one or more SNPNs; or +- if there is no SNPN with validity information which is met, and there are one or more GINs with the validity information which is met, and the UE is not registered to an SNPN broadcasting a GIN which has highest priority among the one or more GINs; or +- if there is no SNPN with validity information which is met and there is no GIN with validity information which is met, and the UE is not registered to the subscribed SNPN + +Otherwise, the UE does not trigger periodic reselection and does not attempt registration on a higher priority SNPN + +NOTE 3: Details of network selection (e.g. validity information handling, periodicity determination) specified in TS 23.122 [17]. + +If a validity condition in Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services changes from met to not met (and vice versa), the UE shall attempt selection and registration on an SNPN based on the above bullets (a) to (d). + +If the UE does not support to access an SNPN providing access for Localized Services or the end user does not enable to access the Localized Services, for automatic network selection the UE shall select and attempts registration on available and allowable SNPNs in the following order: + +- the SNPN without validity information the UE was last registered with (if available) or the equivalent SNPN (if available); +- the subscribed SNPN, which is identified by the PLMN ID and NID for which the UE has SUPI and credentials.; +- If the UEs supports access to an SNPN using credentials from a Credentials Holder then the UE continues by selecting and attempting registration on available and allowable SNPNs which broadcast the indication that access using credentials from a Credentials Holder is supported in the following order: + - SNPNs in the user controlled prioritized list of preferred SNPNs (in priority order); + - SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs (in priority order); + +- SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs (in priority order); + +NOTE 4: If multiple SNPNs are available that broadcast the same GIN, the order in which the UE selects and attempts a registration with those SNPNs is implementation specific. + +- SNPNs, which additionally broadcast an indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. the broadcasted NID or GIN is not present in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs in the UE. + +NOTE 5: If multiple SNPNs are available that broadcast the indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, the order in which the UE selects and attempts a registration with those SNPNs is implementation specific. + +When a UE performs Registration or Service Request to an SNPN, the UE shall indicate the PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID. + +##### 5.30.2.4.3 Manual network selection + +For manual network selection UEs operating in SNPN access mode provide to the user the list of SNPNs (each is identified by a PLMN ID and NID) and related human-readable names (if available) of the available SNPNs the UE has respective SUPI and credentials for. If the UE supports access to an SNPN using credentials from a Credentials Holder, the UE also presents available SNPNs which broadcast the "access using credentials from a Credentials Holder is supported" indication and the human-readable names related to the SNPNs (if available). + +NOTE: The details of manual SNPN selection are defined in TS 23.122 [17]. + +When a UE performs Initial Registration to an SNPN, the UE shall indicate the selected PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID. + +#### 5.30.2.5 Network access control + +If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a self-assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to temporarily prevent the UE from automatically selecting and registering with the same SNPN. + +If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a coordinated assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to permanently prevent the UE from automatically selecting and registering with the same SNPN. + +NOTE: The details of rejection and cause codes is defined in TS 24.501 [47]. + +If a UE performs the registration in an SNPN using credentials from a Credentials Holder (i.e. the CH is the PLMN/SNPN that owns the UE subscription and controls the access) and the Credentials Holder does not authorize the UE to access that specific SNPN due to access authorization based on subscription data or invalid time for accessing an SNPN that provides access to Localized Services, then the UDM, in the Credentials Holder, can reject the UE which results in AMF rejecting the registration request from the UE with an appropriate cause code to prevent the UE from automatically selecting and registering with the same SNPN using credentials from the Credentials Holder as described in TS 24.501 [47]. + +In order to prevent access to SNPNs for authorized UE(s) in the case of network congestion/overload, Unified Access Control information is configured per SNPN (i.e. as part of the subscription information that the UE has for a given SNPN) and provided to the UE as described in TS 24.501 [47]. + +#### 5.30.2.6 Cell (re-)selection in SNPN access mode + +UEs operating in SNPN access mode only select cells and networks broadcasting both PLMN ID and NID of the selected SNPN or its equivalent SNPN. + +NOTE: Further details on the NR idle and inactive mode procedures for SNPN cell selection is defined in TS 38.331 [28] and in TS 38.304 [50]. + +#### 5.30.2.7 Access to PLMN services via stand-alone non-public networks + +To access PLMN services, a UE in SNPN access mode that has successfully registered with an SNPN may perform another registration via the SNPN User Plane with a PLMN (using the credentials of that PLMN) following the same architectural principles as specified in clause 4.2.8 (including the optional support for PDU Session continuity between PLMN and SNPN using the Handover of a PDU Session procedures in clauses 4.9.2.1 and 4.9.2.2 of TS 23.502 [3]) and the SNPN taking the role of "Untrusted non-3GPP access". Annex D, clause D.3 provides additional details. + +**NOTE:** QoS differentiation in the SNPN can be provided on per-IPsec Child Security Association basis by using the UE or network requested PDU Session Modification procedure described in clause 4.3.3.2 of TS 23.502 [3]. In the PLMN, N3IWF determines the IPsec child SAs as defined in clause 4.12 of TS 23.502 [3]. The N3IWF is preconfigured by PLMN to allocate different IPsec child SAs for QoS Flows with different QoS profiles. + +To support QoS differentiation in the SNPN with network-initiated QoS, the mapping rules between the SNPN and the PLMN are assumed to be governed by an SLA including: 1) mapping between the DSCP markings for the IPsec child SAs on NWu and the corresponding QoS, which is the QoS requirement of the PLMN and is expected to be provided by the SNPN, and 2) N3IWF IP address(es) in the PLMN. The non-alteration of the DSCP field on NWu is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters in the SNPN can be based on the N3IWF IP address and the DSCP markings on NWu. + +To support QoS differentiation in the SNPN with UE-requested QoS, the UE can request for an IPsec SA the same 5QI from the SNPN as the 5QI provided by the PLMN. It is assumed that UE-requested QoS is used only when the 5QIs used by the PLMN are from the range of standardized 5QIs. The packet filters in the requested QoS rule can be based on the N3IWF IP address and the SPI associated with the IPsec SA. + +Refer to clause D.7 for details on how to support QoS differentiation. + +When the UE accesses the PLMN over NWu via a SNPN, the AMF in the serving PLMN shall send an indication toward the UE during the Registration procedure to indicate whether an IMS voice over PS session is supported or not. + +#### 5.30.2.8 Access to stand-alone non-public network services via PLMN + +To access SNPN services, a UE that has successfully registered with a PLMN over 3GPP access may perform another registration via the PLMN User Plane with an SNPN (using the credentials of that SNPN) following the same architectural principles as specified in clause 4.2.8 (including the optional support for PDU Session continuity between PLMN and SNPN using the Handover of a PDU Session procedures in clauses 4.9.2.1 and 4.9.2.2 of TS 23.502 [3]) and the PLMN taking the role of "Untrusted non-3GPP access" of the SNPN, i.e. using the procedures for Untrusted non-3GPP access in clause 4.12.2 of TS 23.502 [3]. Annex D, clause D.3 provides additional details. The case where UE that has successfully registered with a PLMN over non-3GPP access to access SNPN services is not specified in this Release. + +**NOTE:** QoS differentiation in the PLMN can be provided on per-IPsec Child Security Association basis by using the UE or network requested PDU Session Modification procedure described in clause 4.3.3.2 of TS 23.502 [3]. In the SNPN, N3IWF determines the IPsec child SAs as defined in clause 4.12 of TS 23.502 [3]. The N3IWF is preconfigured by SNPN to allocate different IPsec child SAs for QoS Flows with different QoS profiles. + +To support QoS differentiation in the PLMN with network-initiated QoS, the mapping rules between the PLMN and the SNPN are assumed to be governed by an SLA including: 1) mapping between the DSCP markings for the IPsec child SAs on NWu and the corresponding QoS, which is the QoS requirement of the SNPN and is expected to be provided by the PLMN, and 2) N3IWF IP address(es) in the SNPN. The non-alteration of the DSCP field on NWu is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters in the PLMN can be based on the N3IWF IP address and the DSCP markings on NWu. + +To support QoS differentiation in the PLMN with UE-requested QoS, the UE can request for an IPsec SA the same 5QI from the PLMN as the 5QI provided by the SNPN. It is assumed that UE-requested QoS is used only when the 5QIs used by the SNPN are from the range of standardized 5QIs. The packet filters in the requested QoS rule can be based on the N3IWF IP address and the SPI associated with the IPsec SA. + +Refer to clause D.7 for details on how to support QoS differentiation. + +When the UE accesses the SNPN over NWu via a PLMN, the AMF in the SNPN shall send an indication toward the UE during the Registration procedure to indicate whether an IMS voice over PS session is supported or not. + +#### 5.30.2.9 SNPN connectivity for UEs with credentials owned by Credentials Holder + +##### 5.30.2.9.1 General + +SNPNs may support UE access using credentials owned by a Credentials Holder separate from the SNPN. In this case the Session Management procedures (i.e. PDU Sessions) terminate in an SMF in the SNPN. + +When an SNPN supports UE access using credentials assigned by a Credentials Holder separate from the SNPN, it is assumed that is supported homogeneously within the whole SNPN. + +Credentials Holder using AAA Server for primary authentication and authorization is described in clause 5.30.2.9.2 and Credentials Holder using AUSF and UDM for primary authentication and authorization is described in clause 5.30.2.9.3. + +##### 5.30.2.9.2 Credentials Holder using AAA Server for primary authentication and authorization + +The AUSF and the UDM in SNPN may support primary authentication and authorization of UEs using credentials from a AAA Server in a Credentials Holder (CH). + +- Only NSI based SUPI is supported and the SUPI is used to identify the UE during primary authentication and authorization towards the AAA Server. SUPI privacy is achieved according to methods in clause I.5 of TS 33.501 [29]. +- The AMF discovers and selects the AUSF as described in clause 6.3.4 using the Home Network Identifier (realm part) and Routing Indicator present in the SUCI provided by a UE configured as described in clause 5.30.2.3. +- The AMF selects the UDM in the same SNPN, based on local configuration (e.g. using the realm part of the SUCI), or using the NRF procedure defined in clause 4.17.4a of TS 23.502 [3]. +- If the UDM decides that the primary authentication is performed by AAA Server in CH based on the UE's SUPI and subscription data. The Home Network Identifier, is derived by UDM from the SUCI received from AUSF. If the SUCI was generated using a privacy protection scheme that requires de-concealment, UDM de-conceal the SUCI as defined in TS 33.501 [29]. The UDM then instructs the AUSF that primary authentication by a AAA Server in a CH is required, the AUSF shall discover and select the NSSAAF, and then forward EAP messages to the NSSAAF. The NSSAAF selects AAA Server based on the domain name corresponds to the realm part of the SUPI, relays EAP messages between AUSF and AAA Server (or AAA proxy) and performs related protocol conversion. The AAA Server acts as the EAP Server for the purpose of primary authentication. + +NOTE 1: The UDM in SNPN, based on SLA between Credentials Holder and SNPN, is pre-configured with information indicating whether the UE needs primary authentication from AAA Server. + +NOTE 2: It is assumed that the SNPN is configured on per Home Network Identifier basis to determine whether to perform primary authentication with AUSF/UDM or AAA server. + +- The AMF and SMF shall retrieve the UE subscription data from UDM using SUPI. + +Figure 5.30.2.9.2-1 depicts the 5G System architecture for SNPN with Credentials Holder using AAA Server for primary authentication and authorization. + +NOTE 3: The SNPN in Figure 5.30.2.9.2-1 can be the subscribed SNPN for the UE (i.e. NG-RAN broadcasts SNPN ID of the subscribed SNPN). As a deployment option, the SNPN in Figure 5.30.2.9.2-1 can also be another SNPN than the subscribed SNPN for the UE (i.e. none of the SNPN IDs broadcast by NG-RAN matches the SNPN ID corresponding to the subscribed SNPN). In both cases, the AUSF, UDM and NSSAAF are configured to support the HNI of the UE's SUPI/SUCI, SUPI privacy settings (when using privacy protection scheme other than the 'null-scheme' to generate the SUCI as defined in TS 33.501 [29]), subscription data of the UE and authentication settings to allow UE authentication with AAA-S in CH. + +![Figure 5.30.2.9.2-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AAA Server. The diagram shows a Credentials Holder at the top connected to an AAA Server. Below the AAA Server is the NSSAAF. A dashed line separates the Credentials Holder/AAA Server from the SNPN. The SNPN contains NSACF, NSSF, UDM, NEF, NRF, PCF, AF, AUSF, and NSSAAF. Below these are the AMF and SMF. The UE is connected to the (R)AN, which is connected to the AMF (N1, N2), the SMF (N4), and the UPF (N3). The UPF is connected to the DN (N6) and has an N9 interface. The AMF is connected to the NSACF (Nnsacf), NSSF (Nnsf), UDM (Nudm), NEF (Nnef), NRF (Nnrf), PCF (Npcf), AF (Naf), AUSF (Nausf), and NSSAAF (Nnssaaf).](dd5771673aececa53d42ece89218299d_img.jpg) + +Figure 5.30.2.9.2-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AAA Server. The diagram shows a Credentials Holder at the top connected to an AAA Server. Below the AAA Server is the NSSAAF. A dashed line separates the Credentials Holder/AAA Server from the SNPN. The SNPN contains NSACF, NSSF, UDM, NEF, NRF, PCF, AF, AUSF, and NSSAAF. Below these are the AMF and SMF. The UE is connected to the (R)AN, which is connected to the AMF (N1, N2), the SMF (N4), and the UPF (N3). The UPF is connected to the DN (N6) and has an N9 interface. The AMF is connected to the NSACF (Nnsacf), NSSF (Nnsf), UDM (Nudm), NEF (Nnef), NRF (Nnrf), PCF (Npcf), AF (Naf), AUSF (Nausf), and NSSAAF (Nnssaaf). + +**Figure 5.30.2.9.2-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AAA Server** + +NOTE 4: The NSSAAF deployed in the SNPN can support primary authentication in the SNPN using credentials from Credentials Holder using a AAA Server (as depicted) and/or the NSSAAF can support Network Slice-Specific Authentication and Authorization with a Network Slice-Specific AAA Server (not depicted). + +##### 5.30.2.9.3 Credentials Holder using AUSF and UDM for primary authentication and authorization + +An SNPN may support primary authentication and authorization of UEs that use credentials from a Credentials Holder using AUSF and UDM. The Credentials Holder may be an SNPN or a PLMN. The Credentials Holder UDM provides to SNPN the subscription data. + +NOTE 1: A list of functionalities not supported in SNPN is provided in clause 5.30.2.0. + +Optionally, an SNPN may support network slicing (including Network Slice-Specific Authentication and Authorization, Network Slice Access Control and subscription-based restrictions to simultaneous registration of network slices) for UEs that use credentials from a Credentials Holder using AUSF and UDM. The SNPN retrieves NSSAA and NSSRG information from the UDM of the Credentials Holder. + +Figure 5.30.2.9.3-1 depicts the 5G System architecture for SNPN with Credentials Holder using AUSF and UDM for primary authentication and authorization and network slicing. + +NOTE 2: The architecture for SNPN and Credentials Holder using AUSF and UDM is depicted as a non-roaming reference architecture as the UE is not considered to be roaming, even though some of the roaming architecture reference points are also used, e.g. for AMF and SMF in SNPN to register with and retrieve subscription data from UDM of the Credentials Holder. + +![Figure 5.30.2.9.3-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AUSF and UDM. The diagram shows a Credentials Holder (top) and an SNPN (bottom) separated by a dashed line. The Credentials Holder contains NSSAAF (NnssAAF), UDM (Nudm), NRF (Nnrf), and AUSF (Nausf). The SNPN contains NSACF (NnsacF), NSSF (NnssF), NEF (Nnef), NRF (Nnrf), PCF (Npcf), and AF (Naf). A SEPP is shown between the two domains. Below the SNPN, the AMF (Namf) and SMF (Nsmf) are connected to the NSACF, NSSF, NEF, NRF, PCF, and AF. The AMF is connected to the UE (N1) and (R)AN (N2). The (R)AN is connected to the UPF (N3). The UPF is connected to the DN (N6) and has a connection to the SMF (N4). The UE is also connected to the (R)AN (N3).](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Figure 5.30.2.9.3-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AUSF and UDM. The diagram shows a Credentials Holder (top) and an SNPN (bottom) separated by a dashed line. The Credentials Holder contains NSSAAF (NnssAAF), UDM (Nudm), NRF (Nnrf), and AUSF (Nausf). The SNPN contains NSACF (NnsacF), NSSF (NnssF), NEF (Nnef), NRF (Nnrf), PCF (Npcf), and AF (Naf). A SEPP is shown between the two domains. Below the SNPN, the AMF (Namf) and SMF (Nsmf) are connected to the NSACF, NSSF, NEF, NRF, PCF, and AF. The AMF is connected to the UE (N1) and (R)AN (N2). The (R)AN is connected to the UPF (N3). The UPF is connected to the DN (N6) and has a connection to the SMF (N4). The UE is also connected to the (R)AN (N3). + +**Figure 5.30.2.9.3-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AUSF and UDM** + +#### 5.30.2.10 Onboarding of UEs for SNPNs + +##### 5.30.2.10.1 General + +Onboarding of UEs for SNPNs allows the UE to access an Onboarding Network (ONN) for the purpose of provisioning the UE with SNPN credentials for primary authentication and other information to enable access to a desired SNPN, i.e. (re-)select and (re-)register with SNPN. + +To provision SNPN credentials in a UE that is configured with Default UE credentials (see clause 5.30.2.10.2.4), the UE selects an SNPN as ONN and establishes a secure connection with that SNPN referred to as Onboarding SNPN (ON-SNPN), see more details in clause 5.30.2.10.2. + +**NOTE:** If the UE is already provisioned with a set of SNPN credentials or credentials owned by a Credentials Holder and needs to be provisioned with an additional set of SNPN credentials, the UE can access an SNPN using the network selection in SNPN access mode as described in clause 5.30.2.4, normal registration (i.e. not registration for onboarding) and normal PDU Session (i.e. not a restricted PDU Session used for onboarding) and then leverage the SNPN's User Plane connection to get access to a PVS. The PVS address can be provided in the same way as when the Onboarding Network is a PLMN. + +To provision SNPN credentials in a UE that is equipped with a USIM configured with PLMN credentials, the UE selects a PLMN as ONN and establishes a secure connection with that PLMN, see more details in clause 5.30.2.10.3. + +After the secure connection is established, the UE is provisioned with SNPN credentials and possibly other data to enable discovery, (re-)selection and (re-)registration for a desired SNPN, see more details in clause 5.30.2.10.4. + +ON-SNPN and SO-SNPN can be roles taken by either an SNPN or different SNPNs. It is possible for the same network to be in both roles with respect to a specific UE. + +##### 5.30.2.10.2 Onboarding Network is an SNPN + +###### 5.30.2.10.2.1 General + +A UE configured with Default UE credentials may register with an ON-SNPN for the provisioning of SO-SNPN credentials. + +###### 5.30.2.10.2.2 Architecture + +Figures 5.30.2.10.2.2-1, 5.30.2.10.2.2-2 and 5.30.2.10.2.2-3 depict the architecture for Onboarding of UEs in an ON-SNPN. + +![Architecture diagram for UE Onboarding in ON-SNPN when the DCS includes an AUSF and a UDM.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +This diagram illustrates the network architecture for UE onboarding in an ON-SNPN. On the left, a UE is connected to an (R)AN, which in turn connects to an AMF via the N1 interface. The AMF is connected to an NSSF via the N22 interface and to an SMF via the N11 interface. The SMF is connected to a PCF via the N7 interface and to a UPF via the N4 interface. The UPF is connected to a DN via the N6 interface. A Provisioning Server is located within the DN. A vertical dashed line separates the ON-SNPN (left) from the DCS (right). The AMF is connected to an AUSF in the DCS via the N12 interface. The AUSF is connected to a UDM via the N13 interface. The label 'DCS with AUSF and UDM' is placed near the AUSF and UDM. + +Architecture diagram for UE Onboarding in ON-SNPN when the DCS includes an AUSF and a UDM. + +Figure 5.30.2.10.2.2-1: Architecture for UE Onboarding in ON-SNPN when the DCS includes an AUSF and a UDM + +![Architecture diagram for UE Onboarding in ON-SNPN when the DCS includes a AAA Server used for primary authentication.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +This diagram illustrates the network architecture for UE onboarding in an ON-SNPN when a AAA server is used for primary authentication. The UE, (R)AN, AMF, NSSF, SMF, PCF, UPF, DN, and Provisioning Server components and their interconnections are identical to Figure 5.30.2.10.2.2-1. The AMF is connected to an AUSF via the N12 interface. The AUSF is connected to an NSSAAF via the N83 interface. The NSSAAF is connected to a AAA Server via an 'AAA protocol' interface. The label 'DCS with AAA server' is placed near the AAA Server. + +Architecture diagram for UE Onboarding in ON-SNPN when the DCS includes a AAA Server used for primary authentication. + +Figure 5.30.2.10.2.2-2: Architecture for UE Onboarding in ON-SNPN when the DCS includes a AAA Server used for primary authentication + +![Figure 5.30.2.10.2.2-3: Architecture for UE Onboarding in ON-SNPN when the DCS is not involved during primary authentication. The diagram shows the network architecture for UE onboarding. On the left, the UE connects to (R)AN via N1, which connects to AMF via N2. AMF connects to AUSF via N12, NSSF via N22, SMF via N11, and UPF via N3. AUSF connects to UDM via N13. SMF connects to PCF via N7 and UPF via N15. UPF connects to DN via N6 and N9. A 'Secondary Authentication' path is shown from UPF to a 'DCS with AAA server' inside the DN. The DN contains an AAA Server and a Provisioning Server. The ON-SNPN and DN are separated by a dashed line.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Figure 5.30.2.10.2.2-3: Architecture for UE Onboarding in ON-SNPN when the DCS is not involved during primary authentication. The diagram shows the network architecture for UE onboarding. On the left, the UE connects to (R)AN via N1, which connects to AMF via N2. AMF connects to AUSF via N12, NSSF via N22, SMF via N11, and UPF via N3. AUSF connects to UDM via N13. SMF connects to PCF via N7 and UPF via N15. UPF connects to DN via N6 and N9. A 'Secondary Authentication' path is shown from UPF to a 'DCS with AAA server' inside the DN. The DN contains an AAA Server and a Provisioning Server. The ON-SNPN and DN are separated by a dashed line. + +**Figure 5.30.2.10.2.2-3: Architecture for UE Onboarding in ON-SNPN when the DCS is not involved during primary authentication** + +NOTE 1: AUSF in the ON-SNPN interfaces with the DCS via NSSAAF as shown in Figure 5.30.2.10.2.2-2 owned by an entity that is internal or external to the ON-SNPN. + +NOTE 2: The functionality with respect to exchange information between PVS and SO-SNPN to provision SNPN credentials and other data from the SO-SNPN in the UE is out of 3GPP scope. + +NOTE 3: The dotted lines in Figure 5.30.2.10.2.2-1, Figure 5.30.2.10.2.2-2 and Figure 5.30.2.10.2.2-3 indicate that whether domains (e.g. DCS domain, PVS domain, and SO-SNPN) are separated depends on the deployment scenario. + +NOTE 4: See TS 33.501 [29] for the functionality beyond AUSF, and other interfaces required for security. + +NOTE 5: When secondary authentication is used in the context of the UE onboarding architecture in Figure 5.30.2.10.2.2-3, the same S-NSSAI/DNN or different S-NSSAI/DNNs can be used for the onboarding PDU Sessions of different UEs even though the DN-AAA servers that authenticate the UEs can reside in different administrative domains. + +When the DCS is involved during mutual primary authentication during the Onboarding procedure (as in Figure 5.30.10.2.2-1 and Figure 5.30.10.2.2-2), the following applies: + +- When the DCS includes an AUSF and a UDM functionality, then the AMF selects AUSF in the DCS domain. The ON-SNPN and DCS domain are connected via N32 and SEPP which are not shown in the Figure 5.30.2.10.2.2-1. +- When the DCS includes a AAA Server functionality, only NSI based SUPI is supported and the AMF selects AUSF in the ON-SNPN. Based on local configuration (e.g. using the realm part of the Onboarding SUCI), the AUSF skips the UDM selection and directly performs primary authentication towards DCS with AAA Server functionality using Default UE credentials for primary authentication. The AUSF uses an NSSAAF (and the NSSAAF may use a AAA-P which is not shown in the figure 5.30.2.10.2.2-2) to relay EAP messages towards the DCS including a AAA Server. The NSSAAF selects AAA Server based on the domain name corresponding to the realm part of the SUPI. + +NOTE 5: The AMF in ON-SNPN uses the Home Network Identifier of the Onboarding SUCI to select the DCS. It is assumed that the ON-SNPN is configured on per Home Network Identifier basis to determine whether to perform primary authentication with AUSF/UDM or AAA server. + +- Upon establishment of the PDU Session used for User Plane Remote Provisioning the ON-SNPN may trigger secondary authentication procedure, as described in clause 4.3.2.3 of TS 23.502 [3], with a DN-AAA using Default UE credentials for secondary authentication as described in clause I.9.2.4 of TS 33.501 [29]. + +When the DCS is not involved during primary authentication (as in Figure 5.30.10.2.2-3), the following applies: + +- The AMF selects a local AUSF as described in clause 5.30.2.10.2.6 and performs primary authentication towards the local AUSF using Default UE credentials for primary authentication as described in TS 33.501 [29]. +- Upon establishment of the PDU Session used for User Plane Remote Provisioning the ON-SNPN may trigger secondary authentication procedure, as described in clause 4.3.2.3 of TS 23.502 [3], with the DCS or with a DN-AAA server using Default UE credentials for secondary authentication, as described in clause I.9.2.4 of TS 33.501 [29]. When secondary authentication is used, the SMF identifies the DCS or the DN-AAA server as defined in clause 4.3.2.3 of TS 23.502 [3]. + +NOTE 6: If the secondary authentication fails, the SMF rejects the PDU Session used for User Plane Remote Provisioning. Based on local policy the AMF can deregister the UE as described in clause 5.30.2.10.2.7. + +NOTE 7: The DCS and PVS can be owned by an administrative entity that can be different from either the ON-SNPN or SO-SNPN. The ownership of DCS and PVS is outside the scope of 3GPP. + +###### 5.30.2.10.2.3 Broadcast system information + +When the SNPN supports Onboarding of UEs for SNPNs (i.e. the SNPN can be used as ON-SNPN), the NG-RAN node or the Trusted non-3GPP access network providing access to SNPN additionally broadcasts the following information: + +- An onboarding enabled indication that indicates whether onboarding is currently enabled for the SNPN. For access to SNPN via NG-RAN the onboarding enabled indication is broadcasted per cell e.g. to allow start of the onboarding procedure only in parts of the SNPN. + +NOTE: Onboarding enabled indication per cell does not affect mobility management functions, i.e. once the UE selects the ON-SNPN as described in clause 5.30.2.10.2.5 and successfully registers within ON-SNPN as described in clause 5.30.2.10.2.6, the UE can move to a cell of the ON-SNPN not indicating onboarding support and continue with the remote provisioning as described in clause 5.30.2.10.4. + +###### 5.30.2.10.2.4 UE Configuration Aspects + +A UE enabled to support UE Onboarding, shall be pre-configured with Default UE credentials, and the UE may be pre-configured with ON-SNPN selection information. The Default UE credentials consist of credentials for primary authentication and optionally credentials for secondary authentication, as described in clause I.9 of TS 33.501 [29]. + +NOTE 1: The content of the ON-SNPN network selection information depends on UE implementation and can include SNPN network identifiers and/or GIN(s). + +The UE uses the ON-SNPN selection information for selection of ON-SNPN (see clause 5.30.2.10.2.5). + +The UE Configuration Data for UP Remote Provisioning is described in the clause 5.30.2.10.4.2. + +NOTE 2: It is assumed that the UE is not pre-configured with a S-NSSAI and DNN for the purpose of UE onboarding in the ON-SNPN. + +NOTE 3: The Default UE credentials for primary authentication are used to derive a SUPI. When the UE derives the SUPI from the Default UE credentials for primary authentication, the UE performs specific onboarding procedure as described in clauses 5.30.2.10.2.5, 5.30.2.10.2.6 and 5.30.2.10.2.7. + +###### 5.30.2.10.2.5 Network selection + +This clause applies only when the UE is in SNPN access mode. + +When the UE wants to perform UE onboarding via an SNPN, the UE shall perform ON-SNPN selection as described below. An ON-SNPN is an SNPN providing onboarding access and enabling remote provisioning for a UE registered for onboarding as specified in clause 4.2.2.2.4 of TS 23.502 [3]. + +NOTE: The trigger for the UE to initiate the UE Onboarding procedure is UE implementation dependent (e.g. the trigger can be a power-on event in the UE, or an input by the user). + +For automatic or manual selection, the UE may select and attempt to register to an ON-SNPN which broadcast the Onboarding enabled indication described in clause 5.30.2.10.2.3 and matches the pre-configured ON-SNPN selection information such as SNPN network identifier and/or GIN(s) (if available) described in clause 5.30.2.10.2.4 according to the UE implementation-specific logic. If the registration fails, the UE may select and attempt to register to a different ON-SNPN as defined in clause 4.9.3.1.3 or clause 4.9.3.1.4 of TS 23.122 [17]. + +###### 5.30.2.10.2.6 Registration for UE onboarding + +When the user or UE has selected an ON-SNPN according to clause 5.30.2.10.2.5, the UE establishes an RRC connection towards the NG-RAN node of the ON-SNPN. The UE provides an indication in RRC Connection Establishment that the RRC connection is for onboarding as defined in TS 38.331 [28]. This indication allows the NG-RAN node to select an appropriate AMF that supports the UE onboarding procedures. The UE indicates the ON-SNPN as the selected network, and the NG-RAN node shall indicate the selected PLMN ID and NID of the ON-SNPN to the AMF. + +NOTE 1: As the configuration information in the UE does not include any S-NSSAI and DNN used for onboarding, the UE does not include S-NSSAI and DNN in RRC when it registers for UE onboarding purposes to the ONN. + +The UE shall initiate the NAS registration procedure by sending a NAS Registration Request message with the following characteristics: + +- The UE shall set the 5GS Registration Type to the value "SNPN Onboarding" indicating that the registration request is for onboarding. +- The UE shall provide a SUCI derived from a SUPI as specified in TS 23.003 [19] and TS 33.501 [29]. The SUPI shall uniquely identify the UE and shall be derived from the Default UE credentials for primary authentication. The SUPI used for onboarding may contain an IMSI or a network-specific identifier. The ON-SNPN may determine the corresponding DCS identity or address/domain, based on the SUCI (i.e. based on the Home Network Identifier of the SUCI). + +The UE does not include a Requested NSSAI in NAS signalling when it registers for UE onboarding purposes to the ON-SNPN. + +The AMF supporting UE onboarding is configured with AMF Onboarding Configuration Data that includes e.g.: + +- S-NSSAI and DNN to be used for onboarding or a configured SMF for the S-NSSAI and DNN used for onboarding. +- Information to use a local AUSF(s) within the ON-SNPN for onboarding of UEs with a SUCI for a DCS with AAA Server or for onboarding of UEs in the case where the DCS is not involved during primary authentication. + +NOTE 2: The S-NSSAI used for onboarding is assumed to be configured in both the AMF (i.e. in the AMF Onboarding Configuration Data) and the NG-RAN nodes for the corresponding Tracking Areas where onboarding is enabled. + +When the AMF receives a NAS Registration Request with a 5GS Registration Type set to "SNPN Onboarding", the AMF: + +- starts an authentication procedure towards the AUSF, the authentication procedure is specified in TS 33.501 [29]. The AMF may be provided with PVS IP address(es) or PVS FQDN(s) from the DCS during authentication procedure. The AMF selects an appropriate AUSF as described in clause 6.3.4 based on the Home Network Identifier of the SUCI used during onboarding or based on local configuration in the AMF. +- applies the AMF Onboarding Configuration Data e.g. used to restrict UE network usage to only onboarding for User Plane Remote Provisioning of UE as described in clause 5.30.2.10.4.3. +- stores in the UE context in AMF an indication that the UE is registered for SNPN onboarding. + +- shall handle the list of equivalent SNPNs as described in TS 24.501 [47]. + +Upon successful authentication from AUSF, the AMF informs the UE about the result of the registration. If the UE is not successfully authenticated, the AMF shall reject the registration procedure for onboarding, and the UE may select a different ON-SNPN to attempt to register. + +NOTE 3: The AMF does not interact with the UDM of the ON-SNPN or DCS (i.e. for registration or subscription management purposes) when it receives a NAS Registration Request with a 5GS Registration Type set to "SNPN Onboarding" (see clause 4.2.2.2.4 of TS 23.502 [3]). + +###### 5.30.2.10.2.7 Deregistration from the ON-SNPN for onboarding registered UE + +Once remote provisioning of SO-SNPN credentials is completed, the UE should initiate deregistration from the ON-SNPN. + +Based on ON-SNPN policies, the AMF may start an implementation specific timer once the UE has registered to the ON-SNPN for the purpose of onboarding. Expiry of this timer triggers the AMF to deregister the onboarding registered UE from the ON-SNPN. + +The AMF may also deregister the UE when it determines that the PDU Session used for User Plane Remote Provisioning has been released by the SMF. + +When AMF re-allocation occurs for a UE registered for SNPN onboarding during mobility registration update procedure as described in TS 23.502 [3] in clause 4.2.2.2.4 or during N2 based handover as described in TS 23.502 [3] clause 4.9.1.3, the new AMF supporting SNPN Onboarding should be selected as described in clause 6.3.5. If the new AMF receives in UE context the indication that the UE is registered for SNPN onboarding, the new AMF may start an implementation specific timer for when to deregister the UE when the new AMF completes the Registration procedure (i.e. sends Registration Accept to the UE) or completes the N2 based handover procedure. + +NOTE: This specific timer is used to prevent onboarding registered UEs from staying at the ON-SNPN indefinitely. + +##### 5.30.2.10.3 Onboarding Network is a PLMN + +###### 5.30.2.10.3.1 General + +A UE configured with PLMN credentials in USIM for primary authentication may register with a PLMN for the provisioning of SO-SNPN credentials. + +###### 5.30.2.10.3.2 Network selection and Registration + +This clause applies only when the UE is not in SNPN access mode. + +When the UE is using PLMN credentials for accessing a PLMN as the Onboarding Network (ONN), then regular network selection, as per TS 23.122 [17] and regular initial registration procedures apply, as per TS 23.502 [3]. After successfully registering to the ON-PLMN, the UE is provisioned with the SO-SNPN credentials via User Plane as in clause 5.30.2.10.4.4. + +NOTE: When Onboarding network is a PLMN and the UE's subscription only allows for Remote Provisioning, then based on PLMN policies, the AMF can start an implementation specific timer once the UE has registered to the PLMN. Expiry of this timer triggers the AMF to deregister the UE from the PLMN. This specific timer is used to prevent registered UEs that are only allowed for Remote Provisioning from staying at the PLMN indefinitely. + +##### 5.30.2.10.4 Remote Provisioning of UEs in Onboarding Network + +###### 5.30.2.10.4.1 General + +Remote Provisioning of UEs that registered with an Onboarding Network enables provisioning the UE with SNPN credentials for primary authentication and other information to enable access to the desired SNPN. + +Onboarding Services are provided using a PDU Session for DNN and S-NSSAI used for onboarding allowing remote provisioning of UEs via User Plane. The PDU Session may be restricted only to be used for Remote Provisioning of the UE. + +###### 5.30.2.10.4.2 Onboarding configuration for the UE + +In order to enable UP Remote Provisioning of SNPN credentials for a UE, UE Configuration Data for User Plane Remote Provisioning are either pre-configured on the UE or provided by the ONN. UE Configuration Data for User Plane Remote Provisioning provided by the ONN take precedence over corresponding configuration data stored in the UE. + +UE Configuration Data for User Plane Remote Provisioning consist of PVS IP address(es) and/or PVS FQDN(s). + +If the UE does not have any PVS IP address or PVS FQDN after the establishment of the PDU Session used for User Plane Remote Provisioning, the UE may construct an FQDN for PVS discovery as defined in TS 23.003 [19]. + +The UE Configuration Data for User Plane Remote Provisioning may be stored in the ME. + +The UE Configuration Data for User Plane Remote Provisioning (i.e. PVS IP address(es) or PVS FQDN(s), or both) may be: + +- locally configured in the SMF of ONN; and/or +- provided by the DCS to the AMF of ON-SNPN as part of the authentication procedure as specified in TS 33.501 [29] and sent by the AMF in the Nsmf\_PDUSession\_CreateSMContext Request message to the SMF + +If the SNPN acting as ON-SNPN is not capable to provide access to Localized Services, the PVS IP address(es) and/or PVS FQDN(s) provided by the DCS take precedence over the locally configured PVS IP address(es) and/or PVS FQDN(s) in the ON-SNPN. If the SNPN acting as ON-SNPN is capable to provides access to Localized Services, the SMF should include both DCS provided and the locally configured PVS IP address(es) and/or PVS FQDN(s), in the UE Configuration Data for User Plane Remote Provisioning. + +If the PCF is used for User Plane Remote Provisioning, the SMF provides the UE Configuration Data to the PCF as described in clause 5.30.2.10.4.3. + +The UE Configuration Data for User Plane Remote Provisioning may be provided to the UE during the establishment of the PDU Session used for User Plane Remote Provisioning as part of Protocol Configuration Options (PCO) in the PDU Session Establishment Response. + +NOTE: If there are multiple PVS IP addresses and/or PVS FQDNs in the UE, how the UE selects PVS from this information is up to UE implementation. + +###### 5.30.2.10.4.3 User Plane Remote Provisioning of UEs when Onboarding Network is an ON-SNPN + +The AMF selects an SMF used for User Plane Remote Provisioning using the SMF discovery and selection functionality as described in clause 6.3.2. The S-NSSAI and DNN of the AMF Onboarding Configuration Data may be used to discover and select an SMF for User Plane Remote Provisioning. Alternatively, for SMF selection, the AMF Onboarding Configuration Data may contain a configured SMF for the S-NSSAI and DNN used for onboarding. The AMF provides Onboarding Indication to SMF via Nsmf\_PDUSession\_CreateSMContext request message when a PDU Session used for User Plane Remote Provisioning is established. During PDU Session establishment for remote provisioning, the AMF may provide the PVS IP address(es) and/or PVS FQDN(s) to the SMF. + +When a UPF is selected for User Plane Remote Provisioning, the UPF selection function described in clause 6.3.3 for normal services is applied considering the S-NSSAI and DNN used for onboarding. + +The SMF or the PCF may store S-NSSAI and DNN information used for onboarding. Onboarding Configuration Data available to PCF (for details see TS 23.503 [45]) and/or SMF may include PVS FQDN(s) and/or PVS IP address(es). The SMF and the PCF may use Onboarding Indication and DNN and S-NSSAI used for onboarding to access the Onboarding Configuration Data. + +NOTE: The SMF is aware about the PVS IP address(es) and/or PVS FQDN(s) in one of the following ways: either received from the AMF or retrieved locally from the Onboarding Configuration Data. + +When the UE registered for Onboarding (i.e. 5GS Registration Type is set to the value "SNPN Onboarding") successfully completes the User Plane Remote Provisioning of SNPN credentials via the Onboarding Network, then the UE should deregister from the Onboarding Network. + +Initial QoS parameters used for User Plane Remote Provisioning are configured in the SMF when dynamic PCC is not used. + +Dynamic PCC may be used for a PDU Session used for User Plane Remote Provisioning as described in TS 23.503 [45]. If a PCF is used and the AMF provided an Onboarding Indication, the SMF provides Onboarding Indication to the PCF when requesting an SM Policy Association. The SMF may provide the UE Configuration Data (i.e. PVS IP address(es) and/or PVS FQDN(s)) to the PCF when requesting an SM Policy Association. + +The QoS Flows of a restricted PDU Session, which is associated with the S-NSSAI/DNN used for Onboarding, shall be dedicated to Onboarding Services. The SMF may configure in the UPF PDR(s) and FAR(s) including PVS and DNS server IP addresses to block any traffic that is not from or to PVS and DNS server addresses. + +If the UE is registered for Onboarding (i.e. 5GS Registration Type is set to the value "SNPN Onboarding"), the network should apply S-NSSAI and DNN in the Onboarding Configuration Data for the PDU Session Establishment request from the UE. + +###### 5.30.2.10.4.4 User Plane Remote Provisioning of UEs when Onboarding Network is a PLMN + +Subscription data of such a UE shall contain the DNN and S-NSSAI used for onboarding. + +The AMF selects an SMF used for User Plane Remote Provisioning using the SMF discovery and selection functionality as described in clause 6.3.2, considering the DNN and S-NSSAI used for onboarding provided by the UE or the default DNN and S-NSSAI provided by UDM. + +The UPF selection function described in clause 6.3.3 is applied, considering the DNN and S-NSSAI used for onboarding. + +The SMF may be configured with one or more PVS FQDN(s) and/or PVS IP address(es) per DNN and S-NSSAI used for onboarding. When the UE requests a PDU Session used for User Plane Remote Provisioning by using DNN and S-NSSAI used for onboarding, the SMF sends the PVS FQDN(s) and/or PVS IP address(es) associated to the DNN and S-NSSAI of the PDU Session to the UE as part of Protocol Configuration Options (PCO) in the PDU Session Establishment Response if the following conditions are met: + +- the UE subscription data contains the DNN and S-NSSAI used for onboarding; and +- the SMF has obtained the PVS FQDN(s) and/or PVS IP address(es) associated to the DNN and S-NSSAI of the PDU Session from local configuration; and +- the UE has requested PVS information via PCO in PDU Session Establishment Request. + +NOTE 1: Local PCC or dynamic PCC can be used as described for PLMNs in TS 23.503 [45] and based on operator policy, PDR(s) and FAR(s) can be configured to restrict traffic other than provisioning traffic between PVS/DNS server(s) and UE(s). + +NOTE 2: If the UE receives multiple PVS IP addresses and/or PVS FQDNs, how the UE uses this information is up to UE implementation. + +#### 5.30.2.11 UE Mobility support for SNPN + +If the UE moves its 3GPP access between SNPN and PLMN, the network selection is performed as specified in TS 23.122 [17] and UE performs initial registration as specified in clause 4.2.2.2.2 of TS 23.502 [3]. + +NOTE 1: When the UE moves its 3GPP access between SNPN and PLMN, it is up to UE implementation to activate/deactivate SNPN access mode. + +If the UE moves its 3GPP access between SNPNs, the network selection is performed as specified in TS 23.122 [17], then the UE performs initial or mobility registration as specified in clause 4.2.2.2.2 of TS 23.502 [3]. + +NOTE 2: When the UE moves its 3GPP access between SNPNs, it is up to UE implementation whether and when to establish again PDU Sessions using existing mechanism. + +If the UE and network supports equivalent SNPNs, the AMF may provide list of equivalent SNPNs to the UE and NG-RAN. The UE may move its 3GPP access to the SNPN in the list of equivalent SNPNs without performing network selection. A UE supporting equivalent SNPNs gets a new registered SNPN ID during the Registration procedure if serving SNPN is changed. + +#### 5.30.2.12 Access to SNPN services via Untrusted non-3GPP access + +Access to SNPN services via Untrusted non-3GPP access network follows the specification in the previous 5.30.2 clauses with the differences as specified in this clause. + +N3IWF selection is supported as follows: + +- When UE registers to SNPN with credentials owned by the SNPN, UE uses the same N3IWF selection procedure as specified for access to stand-alone non-public network services via PLMN in clause 6.3.6.2a. + +Emergency services are supported as follows: + +- UE initiates N3IWF selection for emergency services when the UE detects a user request for emergency session and determines that Untrusted non-3GPP access is to be used for the emergency access. The UE in SNPN access mode the following: +- If the UE determines that it is located in the same country as the configured N3IWF of the subscribed SNPN, the UE uses the configured N3IWF FQDN for N3IWF selection. +- Otherwise, the UE performs a DNS query using the Visited Country Emergency SNPN FQDN, as specified in clause 28.3.2.2.6.3 of TS 23.003 [19] to determine which SNPNs in the visited country support emergency services in untrusted non-3GPP access via N3IWF; and: +- If the DNS response contains one or more records, the UE selects an SNPN that supports emergency services in untrusted non-3GPP access via N3IWF based on UE implementation specific methods. Each record in the DNS response shall contain the identity of an SNPN (i.e. SNPN ID) in the visited country supporting emergency services in untrusted non-3GPP access via N3IWF. + +NOTE 1: Self-assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same self-assigned NID (i.e. in collision scenarios). + +- Once the UE has selected an SNPN, the UE selects an N3IWF for Emergency for the selected SNPN, as specified in TS 23.003 [19]. + +When an N3IWF has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall select another SNPN supporting emergency services in untrusted non-3GPP access. + +If the DNS response of the Visited Country Emergency SNPN FQDN does not contain any record, or if the DNS response contains one or more records but the UE fails to select an SNPN that supports emergency services in untrusted non-3GPP access, or if the Emergency Registration procedure has failed for all SNPNs supporting emergency services in untrusted non-3GPP access, the UE deactivates the SNPN access mode over NWu and attempts emergency services via PLMN untrusted non-3GPP access, by following the N3IWF selection procedure as defined in clause 6.3.6.4.2. + +NOTE 2: If the UE determines that it is located in a different country as the configured N3IWF of the subscribed SNPN, the UE can deactivate the SNPN access mode over NWu and attempts emergency services via PLMN untrusted non-3GPP access, by following the N3IWF selection procedure defined in clause 6.3.6.4.2, without performing a DNS query using the Visited Country Emergency SNPN FQDN. + +UE onboarding is supported as follows: + +- When UE registers to SNPN over Untrusted non-3GPP access for UE Onboarding, if the UE determines that it is located in the country where the configured N3IWF for onboarding is located, the UE may select the N3IWF in the SNPN which supports UE Onboarding by using the configured N3IWF FQDN used for Onboarding. +- If the UE determines that it is located in a country different from the country where the configured N3IWF for onboarding is located (called the visited country), then in order to determine which SNPNs in the visited country support Untrusted non-3GPP access for UE Onboarding via N3IWF performs a DNS query using the Visited Country FQDN for SNPN N3IWF supporting Onboarding, as specified in clause 28.3.2.2.6.2 of TS 23.003 [19]; and: + +- If no DNS response is received, the UE shall stop the N3IWF selection. +- If the DNS response contains one or more records, the UE selects an SNPN that supports Untrusted non-3GPP access for UE Onboarding via N3IWF. Each record in the DNS response shall contain the identity of an SNPN in the visited country supporting Untrusted non-3GPP access for UE Onboarding via N3IWF. In this case: + - The UE shall select an SNPN based on its own implementation means. + +If the UE cannot select any N3IWF included in the DNS response, then the UE shall stop the N3IWF selection. +- If the DNS response contains no records, then the UE determines that the visited country does not mandate the selection of an N3IWF that supports Untrusted non-3GPP access for UE Onboarding via N3IWF in this country. In this case the UE uses the configured N3IWF for onboarding. +- If the UE has selected an SNPN for onboarding, the UE constructs the Operator Identifier based Onboarding FQDN for SNPN N3IWF as specified in clause 28.3.2.2.7.2 of TS 23.003 [19], based on the SNPN ID of the selected SNPN and performs a DNS query: + - The DNS response contains the identifier of the N3IWF supporting the onboarding in the SNPN identified by the SNPN ID. +- If the PVS is reachable from the local Untrusted non-3GPP access network (e.g. via the Internet) using the local IP connectivity, UE may connect directly (i.e. without being connected to an N3WIF) with a PVS to obtain the SNPN credentials. +- As part of UE registration via Untrusted non-3GPP access, in Figure 4.12.2.2-1, step 5 of TS 23.502 [3], the UE provides an onboarding indication inside the AN-Parameters. + +#### 5.30.2.13 Access to SNPN services via Trusted non-3GPP access + +Access to SNPN services via Trusted non-3GPP access network follows the specification in the previous (sub)clauses of clause 5.30.2 with the differences as specified in this clause. + +To access SNPN services via a Trusted non-3GPP access network, the UE follows the procedure for accessing a PLMN via a Trusted non-3GPP access network defined in clause 6.3.12.2 with the following clarifications and additions: + +- A non-3GPP access network may advertise (e.g. with ANQP), not only the PLMNs with which 5G connectivity is supported (as specified in clause 6.3.12.2), but also the SNPNs with which 5G connectivity is supported and the related parameters and indications defined in clause 5.30.2.2 (i.e. human-readable network name(s), GIN(s), indication whether access using credentials from a Credentials Holder is supported, indication whether SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, etc.). +- The UE initiates the access network selection procedure specified in clause 6.3.12.2 and constructs a list of available SNPNs. This list contains the SNPNs advertised by all discovered non-3GPP access networks. +- The UE selects an SNPN that is included in the list of available SNPNs following the procedure in clause 5.30.2.4. +- The UE selects a non-3GPP access network that supports 5G connectivity to the selected SNPN and initiates the registration procedure via Trusted non-3GPP access specified in clause 4.12a.2.2 of TS 23.502 [3] in order to register with the selected SNPN via the selected non-3GPP access network. During the EAP authentication procedure the NAI provided by the UE indicates that 5G connectivity to a specific SNPN is required (e.g. NAI = "@nai.5gc.nid.mnc.mcc.3gppnetwork.org"). + +NOTE: In the case of SNPN ID with self-assigned NID, if the UE, when trying to register with an SNPN ID via TNAN X, is rejected by the AMF with a cause code that temporarily prevents the UE from registering with this SNPN ID, the UE does temporarily not attempt to register with the same SNPN ID, even if the same SNPN ID is advertised via another TNAN. + +- If there are multiple non-3GPP access networks that support 5G connectivity to the selected SNPN, then the UE places these non-3GPP access networks in a prioritized list and selects the highest priority non-3GPP access network from this list. To determine the priority of a non-3GPP access network, the UE shall apply the WLANSP rules (if provided), and the procedure specified in clause 6.6.1.3 of TS 23.503 [45], "UE procedure for + +selecting a WLAN access based on WLANSP rules". If the UE is not provided with WLANSP rules, the UE determines the priority of a non-3GPP access network by using implementation means. + +UE onboarding via Trusted non-3GPP access is supported as follows: + +- The non-3GPP access network advertises (e.g. via ANQP) an Onboarding enabled indication, as specified in clause 5.30.2.10.2.3. +- The UE selects an SNPN advertising the Onboarding enabled indication following the network selection procedure specified in clause 5.30.2.10.2.5. +- As part of UE registration via Trusted non-3GPP access, in Figure 4.12a.2.2-1, step 5 of TS 23.502 [3] the UE provides an onboarding indication inside the AN-Parameters. + +#### 5.30.2.14 Access to SNPN services via wireline access network + +Access to SNPN services via a wireline access network is specified in TS 23.316 [84]. + +#### 5.30.2.15 Access to SNPN services for N5CW devices + +Devices that do not support 5GC NAS signalling over WLAN access (referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short), may access 5GC in an SNPN via a trusted WLAN access network that supports a TWIF function. To access SNPN services the N5CW device performs the following procedure: + +- A WLAN access network may advertise (e.g. with ANQP), not only the PLMNs with which "5G connectivity-without-NAS" is supported (as specified in clause 6.3.12a.1), but also the SNPNs with which "5G connectivity-without-NAS" is supported, as well as the related parameters and indications defined in clause 5.30.2.2 (i.e. human-readable network name(s), GIN(s), indication whether access using credentials from a Credentials Holder is supported, indication whether SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN). +- The N5CW device initiates the access network selection procedure by sending an ANQP query to each discovered WLAN access network and constructs a list of available SNPNs with which "5G connectivity-without-NAS" is supported. This list contains the SNPNs with which "5G connectivity-without-NAS" is supported as advertised by all the discovered WLAN access networks. +- The N5CW device selects an SNPN that is included in the list of available SNPNs with which "5G connectivity-without-NAS" is supported following the procedure in clause 5.30.2.4. +- The N5CW device selects a WLAN access network (e.g. an SSID) that supports "5G connectivity-without-NAS" to the selected SNPN and initiates the "Initial Registration and PDU Session Establishment" procedure specified in clause 4.12b.2 of TS 23.502 [3]. If there are multiple WLAN access networks that support "5G connectivity-without-NAS" to the selected SNPN, then the N5CW device selects the highest priority WLAN access network from this list. To determine the priority of a WLAN access network, the N5CW device shall apply the WLANSP rules (if provided), and the procedure specified in clause 6.6.1.3 of TS 23.503 [45], "UE procedure for selecting a WLAN access based on WLANSP rules". If the N5CW device is not provided with WLANSP rules, the N5CW device determines the priority of a WLAN access network by using implementation means. + +NOTE: How the N5CW device selects credentials to use for SNPN access is implementation specific. + +### 5.30.3 Public Network Integrated NPN + +#### 5.30.3.1 General + +Public Network Integrated NPNs are NPNs made available via PLMNs e.g. by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN. The existing network slicing functionalities apply as described in clause 5.15. When a PNI-NPN is made available via a PLMN, then the UE shall have a subscription for the PLMN in order to access PNI-NPN. + +NOTE 1: Annex D provides additional consideration to consider when supporting Non-Public Network as a Network Slice of a PLMN. + +As network slicing does not enable the possibility to prevent UEs from trying to access the network in areas where the UE is not allowed to use the Network Slice allocated for the NPN, Closed Access Groups may optionally be used to apply access control. + +A Closed Access Group identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. + +CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). + +NOTE 2: CAG is used for access control e.g. authorization at cell selection and configured in the subscription as part of the Mobility Restrictions i.e. independent from any S-NSSAI. CAG is not used as input to AMF selection nor Network Slice selection. If NPN isolation is desired, operator can better support NPN isolation by deploying network slicing for PNI-NPN, configuring dedicated S-NSSAI(s) for the given NPN as specified in Annex D, clause D.2 and restricting NPN's UE subscriptions to these dedicated S-NSSAI(s). + +The UE and PNI-NPN may support remote provisioning of credentials for NSSAA or credentials for secondary authentication/authorization to the UE, as specified in clause 5.39. + +NOTE 3: After successful provisioning of the credentials to the UE, specific service subscription data (e.g. to enable the use of PNI-NPN) can be activated in the UE Subscription data in the UDR/UDM. This can result in a change of the UE Subscription Data to include new S-NSSAI, DNN or CAG information, which can trigger update of the UE configurations, e.g. described in clause 5.15.5.2.2. + +NOTE 4: The UE always has subscription to the HPLMN providing the PNI-NPN and has a USIM that contains primary authentication credentials. + +Support for Proximity based Services (ProSe) as defined in TS 23.304 [128] in conjunction with CAG is not specified in this Release of the specification. + +#### 5.30.3.2 Identifiers + +The following is required for identification: + +- A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID; +- A CAG cell broadcasts one or multiple CAG Identifiers per PLMN; + +NOTE 1: It is assumed that a cell supports broadcasting a total of twelve CAG Identifiers. Further details are defined in TS 38.331 [28]. + +- A CAG cell may in addition broadcast a human-readable network name per CAG Identifier: + +NOTE 2: The human-readable network name per CAG Identifier is only used for presentation to user when user requests a manual CAG selection. + +#### 5.30.3.3 UE configuration, subscription aspects and storage + +To use CAG, the UE, that supports CAG as indicated as part of the UE 5GMM Core Network Capability, may be pre-configured or (re)configured with the following CAG information, included in the subscription as part of the Mobility Restrictions: + +- an Allowed CAG list i.e. a list of CAG Identifiers the UE is allowed to access; and +- each entry of the Allowed CAG list may be associated with time validity information; and +- optionally, a CAG-only indication whether the UE is only allowed to access 5GS via CAG cells (see TS 38.304 [50] for how the UE identifies whether a cell is a CAG cell); + +The HPLMN may configure or re-configure a UE with the above CAG information using the UE Configuration Update procedure for access and mobility management related parameters described in clause 4.2.4.2 of TS 23.502 [3]. + +The above CAG information is provided by the HPLMN on a per PLMN basis. In a PLMN the UE shall only consider the CAG information provided for this PLMN. The entries of the Allowed CAG list with validity condition are provided to the UE only if the UE indicates support of CAG with validity information. + +NOTE 1: If the UE supports CAG but not CAG with validity information and there are entries of the Allowed CAG list that are associated with validity information in the subscription data, the CAG Identifier of the corresponding entry in subscription data can be provided to the UE without validity information when the validity condition is evaluated as true and removed when the evaluation changes to false. It is up to AMF local policy whether to provide such CAG Identifier to the UE. In case the AMF does not support CAG with validity information e.g. in the case of roaming, the UDM provides CAG information to the AMF without entries including validity information. + +When the subscribed CAG information changes, UDM sets a CAG information Subscription Change Indication and sends it to the AMF. The AMF shall provide the UE with the CAG information when the UDM indicates that the CAG information within the Access and Mobility Subscription data has been changed. When AMF receives the indication from the UDM that the CAG information within the Access and Mobility Subscription has changed, the AMF uses the CAG information received from the UDM to update the UE. Once the AMF updates the UE and obtains an acknowledgment from the UE, the AMF informs the UDM that the update was successful and the UDM clears the CAG information Subscription Change Indication flag. + +The AMF may update the UE using either the UE Configuration Update procedure after registration procedure is completed, or by including the new CAG information in the Registration Accept or in the Registration Reject or in the Deregistration Request or in the Service Reject. + +When the UE is roaming and the Serving PLMN provides CAG information, the UE shall update only the CAG information provided for the Serving PLMN while the stored CAG information for other PLMNs are not updated. When the UE is not roaming and the HPLMN provides CAG information, the UE shall update the CAG information stored in the UE with the received CAG information for all the PLMNs. + +The UE shall store the latest available CAG information for every PLMN for which it is provided and keep it stored when the UE is de-registered or switched off, as described in TS 24.501 [47]. + +The CAG information is only applicable with 5GS. + +NOTE 2: CAG information has no implication on whether and how the UE accesses 5GS over non-3GPP access. + +#### 5.30.3.4 Network and cell (re-)selection, and access control + +The following is assumed for network and cell selection, and access control: + +- The CAG cell shall broadcast information such that only UEs supporting CAG are accessing the cell (see TS 38.300 [27], TS 38.304 [50]); + +NOTE 1: The above also implies that cells are either CAG cells or normal PLMN cells. For network sharing scenario between SNPN, PNI-NPN and PLMNs, please see clause 5.18. + +- In order to prevent access to NPNs for authorized UE(s) in the case of network congestion/overload, existing mechanisms defined for Control Plane load control, congestion and overload control in clause 5.19 can be used, as well as the access control and barring functionality described in clause 5.2.5, or Unified Access Control using the access categories as defined in TS 24.501 [47] can be used. +- For aspects of automatic and manual network selection in relation to CAG, see TS 23.122 [17]; +- For aspects related to cell (re-)selection, see TS 38.304 [50]; +- If the UE is accessing a CAG cell and the corresponding entry of the Allowed CAG list configured on the UE is associated with validity information, the UE may trigger cell reselection and/or network selection procedure if the evaluation of the validity condition changes. +- The Mobility Restrictions shall be able to restrict the UE's mobility according to the Allowed CAG list (if configured in the subscription) and include an indication whether the UE is only allowed to access 5GS via CAG cells (if configured in the subscription) as described in clause 5.30.3.3; +- The AMF shall update the Allowed CAG list in the Mobility Restrictions towards NG-RAN if the evaluation of the validity condition of an entry in the Allowed CAG list changes between true and false, unless the AMF + +releases the NAS signalling connection to the UE based on operator's policy if the evaluation of the validity condition changes from true to false. + +- During transition from CM-IDLE to CM-CONNECTED and during Registration after connected mode mobility from E-UTRAN to NG-RAN as described in clause 4.11.1.2.2 of TS 23.502 [3]: +- The AMF shall verify whether UE access is allowed by Mobility Restrictions: + +NOTE 2: It is assumed that the AMF is made aware of the supported CAG Identifier(s) of the CAG cell by the NG-RAN. + +- If the UE is accessing the 5GS via a CAG cell and if at least one of the CAG Identifier(s) received from the NG-RAN is part of the UE's Allowed CAG list (for entries with validity information if any, the evaluation of the condition is true), then the AMF accepts the NAS request; + - If the UE is accessing the 5GS via a CAG cell and if none of the CAG Identifier(s) received from the NG-RAN are part of the UE's Allowed CAG list (for entries with validity information if any, the evaluation of the condition is true), then the AMF rejects the NAS request and the AMF should include CAG information in the NAS reject message. The AMF shall then release the NAS signalling connection for the UE by triggering the AN release procedure; and + - If the UE is accessing the 5GS via a non-CAG cell and the UE's subscription contains an indication that the UE is only allowed to access CAG cells, then the AMF rejects the NAS request and the AMF should include CAG information in the NAS reject message. The AMF shall then release the NAS signalling connection for the UE by triggering the AN release procedure. +- During transition from RRC\_INACTIVE to RRC\_CONNECTED state: + - When the UE initiates the RRC Resume procedure for RRC\_INACTIVE to RRC\_CONNECTED state transition in a CAG cell, NG-RAN shall reject the RRC Resume request from the UE if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list according to the Mobility Restrictions received from the AMF or if no Allowed CAG list has been received from the AMF. + - When the UE initiates the RRC Resume procedure for RRC\_INACTIVE to RRC\_CONNECTED state transition in a non-CAG cell, NG-RAN shall reject the UE's Resume request if the UE is only allowed to access CAG cells according to the Mobility Restrictions received from the AMF. + - During connected mode mobility procedures within NG-RAN, i.e. handover procedures as described in clause 4.9.1 of TS 23.502 [3]: + - Source NG-RAN shall not handover the UE to a target NG-RAN node if the target is a CAG cell and none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list in the Mobility Restriction List or if no Allowed CAG list has been received from the AMF; + - Source NG-RAN shall not handover the UE to a non-CAG cell if the UE is only allowed to access CAG cells based on the Mobility Restriction List; + - If the target cell is a CAG cell, target NG-RAN shall reject the N2 based handover procedure if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list in the Mobility Restriction List or if no Allowed CAG list has been received from the AMF; + - If the target cell is a non-CAG cell, target NG-RAN shall reject the N2 based handover procedure if the UE is only allowed to access CAG cells based on the Mobility Restriction List. + - Update of Mobility Restrictions: + - When the AMF receives the Nudm\_SDM\_Notification from the UDM and the AMF determines that the Allowed CAG list or the indication whether the UE is only allowed to access CAG cells have changed; + - The AMF shall update the Mobility Restrictions in the UE and NG-RAN accordingly under the conditions as described in clause 4.2.4.2 of TS 23.502 [3]. + +NOTE 3: When the UE is accessing the network for emergency services the conditions for AMF in clause 5.16.4.3 apply. + +#### 5.30.3.5 Support of emergency services in CAG cells + +Emergency Services are supported in CAG cells, for UEs supporting CAG, whether normally registered or emergency registered as described in clause 5.16.4 and in clause 4.13.4 of TS 23.502 [3]. + +A UE may camp on an acceptable CAG cell in limited service state as specified in TS 23.122 [17] and TS 38.304 [50], based on operator policy defined in TS 38.300 [27]. + +NOTE: Support for Emergency services requires each cell with a Cell Identity associated with PLMNs or PNI-NPNs to only be connected to AMFs that supports emergency services. + +The UE shall select a PLMN (of a CAG cell or non-CAG cell), as described in TS 23.122 [17] and TS 23.167 [18], when initiating emergency services from limited service state. + +During handover to a CAG cell, if the UE is not authorized to access the target CAG cell as described in clause 5.30.3.4 and has emergency services, the target NG-RAN node only accepts the emergency PDU Session and the target AMF releases the non-emergency PDU Sessions that were not accepted by the NG-RAN node. Upon completion of handover the UE behave as emergency registered. + +## 5.31 Support for Cellular IoT + +### 5.31.1 General + +This clause provides an overview about 5GS optimisations and functionality for support of Cellular Internet-of-Things (Cellular IoT, or CIoT) according to service requirements described in TS 22.261 [2]. Cellular IoT is in earlier 3GPP releases also referred to as Machine Type Communication (MTC) (see clause 4.3.17 of TS 23.401 [26]). The specific functionality is described in the affected procedures and features of this specification, in TS 23.502 [3], TS 23.503 [45] and other specifications. + +In this Release Control Plane CIoT 5GS Optimisations (clause 5.31.4) and User Plane CIoT 5GS Optimisations (clause 5.31.18) are only supported over E-UTRA and these CIoT 5GS optimisations are not supported over Non-3GPP RAT type accesses. + +CIoT functionality is provided by the visited and home networks when the networks are configured to support CIoT. It applies to both the non-roaming case and the roaming case and some functionality may be dependent upon the existence of appropriate roaming agreements between the operators. + +Some of the CIoT functions are controlled by subscriber data. Other CIoT functions are based on indicators sent by the UE to the network. CIoT functionality is performed by UEs that are configured to support different options as described in clause 5.31.2 + +Though motivated by scenarios and use cases defined in TS 22.261 [2], the functions added to support CIoT have general applicability and are in no way constrained to any specific scenario, use case or UE types, except where explicitly stated. + +In the context of CIoT the term AF denotes an SCS/AS as defined TS 23.682 [36]. + +### 5.31.2 Preferred and Supported Network Behaviour + +At registration, a UE includes its 5G Preferred Network Behaviour indicating the network behaviour the UE can support and what it would prefer to use. + +NOTE: If the UE supports S1-mode then the UE will indicate the supported EPS Network Behaviour Information in the S1 UE network capability IE. + +The 5G Preferred Network Behaviour signalled by the UE includes the following information in the 5GMM Capability IE: + +- Whether Control Plane CIoT 5GS Optimisation is supported. +- Whether User Plane CIoT 5GS Optimisation is supported. +- Whether N3 data transfer is supported. + +- Whether header compression for Control Plane CIoT 5GS Optimisation is supported. + +And the following 5G Preferred Network Behaviour in other IEs: + +- Whether Control Plane CIoT 5GS Optimisation or User Plane CIoT 5GS Optimisation is preferred. + +If N3 data transfer is supported is indicated by the UE, the UE supports data transfer that is not subject to CIoT 5GS Optimisations. If the UE indicates support of User Plane CIoT 5GS Optimisation then it shall also indicate support of N3 data transfer. + +The AMF indicates the network behaviour the network accepts in the 5G Supported Network Behaviour information. This indication is per Registered Area. The AMF may indicate one or more of the following: + +- Whether Control Plane CIoT 5GS Optimisation is supported. +- Whether User Plane CIoT 5GS Optimisation is supported. +- Whether N3 data transfer is supported. +- Whether header compression for Control Plane CIoT 5GS Optimisation is supported. + +If the AMF indicates support of User Plane CIoT 5GS Optimisation then it shall also indicate support of N3 data transfer. If the UE and AMF indicate support for User Plane CIoT 5GS Optimisation, the AMF indicates support of User Plane CIoT 5GS Optimisation support for the UE to NG-RAN. + +For NB-IoT UEs that only support Control Plane CIoT 5GS Optimisation, the AMF shall include support for Control Plane CIoT 5GS Optimisation in the Registration Accept message. + +A UE that supports the NB-IoT shall always indicate support for Control Plane CIoT 5GS Optimisation. + +A UE that supports WB-E-UTRA shall always indicate support for N3 data transfer. + +The 5G Preferred Network Behaviour indication from the UE may be used to influence policy decisions that can cause rerouting of the Registration Request from an AMF to another AMF. + +### 5.31.3 Selection, steering and redirection between EPS and 5GS + +The UE selects the core network type (EPC or 5GC) based on the broadcast indications for both EPC and 5GC, and the UE's EPC and 5GC Preferred Network Behaviour. Networks that support NB-IoT shall broadcast an indication whether N3 data transfer is supported or not in system information. + +When the UE performs the registration procedure it includes its Preferred Network Behaviour (for 5G and EPC) in the Registration Request message and the AMF replies with the 5G Supported Network Behaviour in the Registration Accept message. + +If the UE supports any of the CIoT 5GS Optimisations included in 5GC Preferred Network Behaviour, then when the UE performs an Attach or TAU procedure and the UE includes its EPC Preferred Network Behaviour then the UE shall also include its 5GC Preferred Network Behaviour. + +In networks that support CIoT features in both EPC and 5GC, the operator may steer UEs from a specific CN type due to operator policy, e.g. due to roaming agreements, Preferred and Supported Network Behaviour, load redistribution, etc. Operator policies in EPC and 5GC are assumed to avoid steering UEs back and forth between EPC and 5GC. + +To redirect a UE from 5GC to EPC, when the UE sends a Registration Request or Service Request, the AMF sends a Registration Reject or Service Reject with an EMM cause value indicating that the UE should not use 5GC. The UE disables N1 mode and re-enables S1 mode, if it was disabled. The UE then performs either an Attach or TAU in EPC as described in clause 5.17.2. + +To redirect a UE from EPC to 5GC, when the UE requests an Attach or TAU procedure or Service Reject, the MME sends a reject message with an EMM cause indicating the UE should not use EPC. The UE disables S1 mode and re-enables N1 mode, if it was disabled. The UE then registers with 5GC as described in clause 5.17.2. + +When determining whether to redirect the UE, the AMF/MME takes into account the UE support of S1/N1 mode, respectively, and the UE's Preferred Network Behaviour and the Supported Network Behaviour of the network the UE is being redirected towards. + +When determining to redirect the UE in 5GMM-CONNECTED mode to EPC, the AMF shall initiate the UE Configuration Update procedure to indicate registration requested and release of the N1 NAS signalling connection not requested, then the AMF redirects the UE to EPC by rejecting the subsequent Registration Request, see TS 24.501 [47]. + +If after redirection the UE cannot find a cell supporting connectivity, the UE may re-enable the disabled N1/S1 mode and then perform Registration, Attach or TAU. + +### 5.31.4 Control Plane CIoT 5GS Optimisation + +#### 5.31.4.1 General + +The Control Plane CIoT 5GS Optimisation is used to exchange user data between the UE and the SMF as payload of a NAS message in both uplink and downlink directions, avoiding the establishment of a user plane connection for the PDU Session. The UE and the AMF perform integrity protection and ciphering for the user data by using NAS PDU integrity protection and ciphering. For IP and Ethernet data, the UE and the SMF may negotiate and perform header compression. + +NOTE: In the context of Control Plane CIoT 5GS Optimisation, established or activated user plane resources/connection refers to radio user plane resources/connection i.e Data Radio Bearer and N3 tunnel. + +UE and AMF negotiate support and use of Control Plane CIoT 5GS Optimisation as defined in clause 5.31.2. When the Control Plane CIoT 5GS Optimisation feature is used and the PDU Session Type is unstructured, the SMF selects either NEF or UPF based on information in the UE's subscription. + +If UE and network have negotiated support and use of Control Plane CIoT 5GS Optimisation then the following paragraphs of this clause apply. + +During the PDU Session Establishment procedure the AMF indicates to the SMF that Control Plane CIoT 5GS Optimisation is available for data transmission. + +During the PDU Session Establishment procedure the AMF also determines based on Preferred and Supported Network Behaviour (see clause 5.31.2), subscription data, other already established PDU Sessions and local policy whether a new PDU Session shall only use the Control Plane CIoT 5GS Optimisation (i.e. that a user-plane connection shall never be established for the new PDU Session). If a PDU Session shall only use Control Plane CIoT 5GS Optimisation, the AMF provides a Control Plane Only Indicator to the SMF during the PDU Session Establishment. The SMF provides the Control Plane Only Indicator in the Session Management Request to the UE. A UE and SMF receiving the Control Plane Only Indicator for a PDU Session shall always use the Control Plane CIoT 5GS Optimisation for this PDU Session. + +The following rules apply for the use of the Control Plane Only Indicator during PDU Session Establishment: + +- If N3 data transfer was not successfully negotiated, all PDU Sessions shall include Control Plane Only Indicator. +- If N3 data transfer was successfully negotiated then: + - For a new PDU Session for a DNN/S-NSSAI for which the subscription data for SMF Selection includes an Invoke NEF indication (i.e. for a PDU Session which will be anchored in NEF), the AMF shall always include the Control Plane Only Indicator. + - For a new PDU Session for a DNN/S-NSSAI for which the subscription data for SMF Selection does not include an Invoke NEF indication (i.e. for a PDU Session which will be anchored in UPF) and that supports interworking with EPS based on the subscription data defined in TS 23.502 [3]: + - for the first PDU Session the AMF determines based on local policy whether to include the Control Plane Only Indicator or not; + - if the AMF previously included a Control Plane Only Indicator for PDU Sessions that support interworking with EPS based on the subscription data defined in TS 23.502 [3] and that are anchored in UPF, the AMF shall include it also for the new PDU Session; + - if the AMF previously did not include a Control Plane Only Indicator for any of the PDU Sessions that support interworking with EPS based on the subscription data defined in TS 23.502 [3] and that are anchored in UPF, the AMF shall not include it for the new PDU Session. + +- For a new PDU Session for a DNN/S-NSSAI for which the subscription data for SMF Selection does not include an Invoke NEF indication (i.e. for a PDU Session which will be anchored in UPF) and that does not support interworking with EPS based on the subscription data defined in TS 23.502 [3], AMF determines individually per PDU Session whether to include the Control Plane Only Indicator or not. + +As described in clause 5.31.4.2, if UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation, the UE or SMF may request to establish N3 data transfer for one or more PDU Sessions for which Control Plane Only Indicator was not received. In CM-CONNECTED, the UE and the network use N3 delivery for PDU Sessions for which user plane resources are established, and uses NAS for data transmission for PDU Sessions for which user plane resources are not established. + +If the AMF determines that Control Plane Only indication associated with PDU Session is not applicable any longer due to e.g. change of Preferred and Supported Network Behaviour, subscription data, and local policy, the AMF should request the SMF to release the PDU Session as specified in clause 4.3.4.2 or clause 4.3.4.3 of TS 23.502 [3]. + +Early Data Transmission may be initiated by the UE for mobile originated Control Plane CIoT 5GS Optimisation when the RAT Type is E-UTRA. + +The QoS model as defined in clause 5.7 is not supported for PDU Sessions using Control Plane CIoT 5GS Optimisation as user plane resources are not established for those PDU Sessions. + +#### 5.31.4.2 Establishment of N3 data transfer during Data Transport in Control Plane CIoT 5GS Optimisation + +If UE and AMF have successfully negotiated N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the SMF may decide to establish N3 data transfer for any PDU session for which Control Plane Only Indicator was not included based on local SMF decision e.g. based on the amount of data transferred in UL or DL using Control Plane CIoT 5GS Optimisation. In that case, the SMF initiates the SMF-triggered N3 data transfer establishment procedure as described in clause 4.2.10.2 of TS 23.502 [3]. + +If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the UE may decide to establish N3 data transfer for any PDU session for which Control Plane Only Indicator was not included based on local decision, e.g. based on the amount of data to be transferred. In that case, the UE performs the UE triggered N3 data transfer establishment procedure as described in clause 4.2.10.1 of TS 23.502 [3]. + +#### 5.31.4.3 Control Plane Relocation Indication procedure + +For intra-NB-IoT mobility when UE and AMF are using Control Plane CIoT 5GS Optimisation, the CP Relocation Indication procedures may be used. The purpose of the CP Relocation Indication procedure is to request the AMF to authenticate the UE's re-establishment request (see TS 33.501 [29]), and initiate the establishment of the UE's N2 connection after the UE has initiated an RRC Re-Establishment procedure in a new NG-RAN node (see TS 38.300 [27]). + +The RRC Re-Establishment procedure uses the Truncated 5G-S-TMSI as the UE identifier. The NG-RAN is configured with the sizes of the components of the Truncated 5G-S-TMSI and it is configured with how to recreate the AMF Set ID, the AMF Pointer and 5G-TMSI from the equivalent truncated parameters (see TS 23.003 [19]). + +The AMF configures the UE with the Truncated 5G-S-TMSI Configuration that provides the sizes of the components of the Truncated 5G-S-TMSI as described in TS 24.501 [47] during the Registration. The configuration of these parameters are specific to each PLMN. + +NOTE: Network sharing default configuration of the sizes of the truncated components is described in TS 23.003 [19]. + +### 5.31.5 Non-IP Data Delivery (NIDD) + +Functions for NIDD may be used to handle Mobile Originated (MO) and Mobile Terminated (MT) communication for unstructured data (also referred to as Non-IP). Such delivery to the AF is accomplished by one of the following two mechanisms: + +- Delivery using the NIDD API; +- Delivery using UPF via a Point-to-Point (PtP) N6 tunnel. + +NIDD is handled using an Unstructured PDU session to the NEF. The UE may obtain an Unstructured PDU session to the NEF during the PDU Session Establishment procedure. Whether or not the NIDD API shall be invoked for a PDU session is determined by the presence of a "NEF Identity for NIDD" for the DNN/S-NSSAI combination in the subscription. If the subscription includes a "NEF Identity for NIDD" corresponding with the DNN and S-NSSAI information, then the SMF selects that NEF and uses the NIDD API for that PDU session. + +The NEF exposes the NIDD APIs described in TS 23.502 [3] on the N33/Nnef reference point. + +The NEF uses the provisioned policies to map an AF Identifier and UE Identity to a DNN/S-NSSAI combination if the Reliable Data Service (RDS) is not enabled. If RDS is enabled, the NEF determines the association based on RDS port numbers and the provisioned policies that may be used to map AF Identifier and User identity to a DNN. + +The NEF also supports distribution of Mobile Terminated messages to a group of UEs based on the NIDD API. If an External Group Identifier is included in the MT NIDD request, the NEF uses the UDM to resolve the External Group Identifier to a list of SUPIs and sends the message to each UE in the group with an established PDU Session. + +The Protocol Configuration Options (PCO) may be used to transfer NIDD parameters to and from the UE (e.g. maximum packet size). The PCO is sent in the 5GSM signalling between UE and SMF. NIDD parameters are sent to and from the NEF via the N29 interface. + +### 5.31.6 Reliable Data Service + +The Reliable Data Service (RDS) may be used between the UE and NEF or UPF when using a PDU Session of PDU Type 'Unstructured'. The service provides a mechanism for the NEF or UPF to determine if the data was successfully delivered to the UE and for the UE to determine if the data was successfully delivered to the NEF or UPF. When a requested acknowledgement is not received, the Reliable Data Service retransmits the packet. The service is enabled or disabled based on DNN and NSSAI Configuration per SLA. + +When the service is enabled, a protocol is used between the end-points of the unstructured PDU Session. The protocol uses a packet header to identify if the packet requires no acknowledgement, requires an acknowledgement, or is an acknowledgment and to allow detection and elimination of duplicate PDUs at the receiving endpoint. RDS supports both single and multiple applications within the UE. Port Numbers in the header are used to identify the application on the originator and to identify the application on the receiver. The UE, NEF and the UPF may support reservation of the source and destination port numbers for their use and subsequent release of the reserved port numbers. Reliable Data Service protocol (as defined in TS 24.250 [80]) also enables applications to query their peer entities to determine which port numbers are reserved and which are available for use at any given time. The header is configured based on Reliable Data Service Configuration information which is obtained in the NIDD configuration, MT NIDD, and MO NIDD procedures with the AF as specified in TS 23.502 [3]. + +During NIDD Configuration, the AF may indicate which serialization formats it supports for mobile originated and mobile terminated traffic in the Reliable Data Server Configuration. When port numbers are reserved by the UE, the serialization format that will be used by the application may be indicated to the NEF. When port numbers are reserved by the NEF, the serialization format that will be used by the application may be indicated to the UE. If the receiver does not support the indicated serialization format, it rejects the port number reservation request and the sender may re-attempt to reserve the port number with a different serialization format. If, during NIDD Configuration, the AF indicated that it supports multiple serialization formats, the NEF determines the serialization format that it will indicate to the UE based on local policies and previous negotiations with the UE (e.g. the NEF may indicate the same serialization format that was indicated by the UE or avoid indicating a serialization format that was previously rejected by the UE). When serialization formats are configured for reserved port numbers, the NEF stores the serialization formats as part of the Reliable Data Service Configuration and provides the updated Reliable Data Service Configuration to the AF. + +NOTE: Whether the UE Application or AF supports a given serialization format is outside the scope of 3GPP specifications. + +The UE indicates its capability of supporting RDS in the Protocol Configuration Options (PCO) and the SMF negotiates RDS support with the NEF or UPF. If the NEF or UPF supports and accepts RDS then the SMF indicates to the UE, in the PCO, that the RDS shall be used if enabled in the DNN and NSSAI configuration. + +In order to prevent situations where an RDS instance needs to interface to both the user and control plane, RDS may only be used with PDU Sessions for which the "Control Plane CIoT 5GS Optimisation" indication is set or with PDU sessions using the Control Plane CIoT 5GS Optimisation when the AMF does not move the PDU session to the user plane. + +Reliable Data Service protocol is defined in TS 24.250 [80]. + +### 5.31.7 Power Saving Enhancements + +#### 5.31.7.1 General + +To enable UE power saving and to enhance MT reachability while using MICO mode, e.g. for CIoT, the following features are specified in the following clauses: + +- Extended Discontinuous Reception (DRX) for CM-IDLE and CM-CONNECTED with RRC\_INACTIVE; +- MICO mode with Extended Connected Time; +- MICO mode with Active Time; +- MICO mode and Periodic Registration Timer Control. + +If a UE requests via NAS to enable both MICO mode with Active Time and extended idle mode DRX, e.g. based on local configuration, Expected UE Behaviour, if available, UE requested Active Time value, UE subscription information and network policies etc, the AMF may decide to enable MICO mode with or without Active Time, extended idle mode DRX or both. + +The functions and procedures to enable a UE using power saving functions to receive MBS service are defined in TS 23.247 [129]. + +#### 5.31.7.2 Extended Discontinuous Reception (DRX) for CM-IDLE and CM-CONNECTED with RRC-INACTIVE + +##### 5.31.7.2.1 Overview + +The UE and the network may negotiate over non-access stratum signalling the use of extended idle mode DRX for reducing its power consumption, while being available for mobile terminating data and/or network originated procedures within a certain delay dependent on the DRX cycle value. Extended DRX in CM-IDLE is supported for E-UTRA and NR connected to 5GC. Extended DRX in CM-CONNECTED with RRC\_INACTIVE mode is supported for WB-E-UTRA, LTE-M and NR connected to 5GC. RRC\_INACTIVE is not supported by NB-IoT connected to 5GC. + +The negotiation of the eDRX parameters for NR, WB-E-UTRA and LTE-M is supported over any RAT. + +Applications that want to use extended idle mode DRX need to consider specific handling of mobile terminating services or data transfers, and in particular they need to consider the delay tolerance of mobile terminated data. A network side application may send mobile terminated data, an SMS, or a device trigger, and needs to be aware that extended idle mode DRX may be in place. A UE should request for extended idle mode DRX only when all expected mobile terminating communication is tolerant to delay. + +NOTE 1: The extended idle mode DRX cycle length requested by UE takes into account requirements of applications running on the UE. Subscription based determination of eDRX cycle length can be used in those rare scenarios when applications on UE cannot be modified to request appropriate extended idle mode DRX cycle length. The network accepting extended DRX while providing an extended idle mode DRX cycle length value longer than the one requested by the UE, can adversely impact reachability requirements of applications running on the UE. + +UE and NW negotiate the use of extended idle mode DRX as follows: + +If the UE decides to request for extended idle mode DRX, the UE includes an extended idle mode DRX parameters information element in the Registration Request message. The UE may also include the UE specific DRX parameters information element for regular idle mode DRX according to clause 5.4.5. The extended DRX parameters information element includes the extended idle mode DRX cycle length. + +The AMF decides whether to accept or reject the UE request for enabling extended idle mode DRX. If the AMF accepts the extended idle mode DRX, the AMF based on operator policies and, if available, the extended idle mode DRX cycle length value in the subscription data from the UDM, may also provide different values of the extended idle mode DRX parameters than what was requested by the UE. The AMF taking into account the RAT specific Subscribed Paging Time Window, the UE's current RAT and local policy also assigns a Paging Time Window length to be used, and provides this value to the UE during Registration Update procedures together with the extended idle mode DRX cycle length in the extended DRX parameter information element. If the AMF accepts the use of extended idle mode DRX, the UE shall apply extended idle mode DRX based on the received extended idle mode DRX length, the UE's current RAT (NR, NB-IoT, WB-E-UTRA or LTE-M) and RAT specific Paging Time Window length. If the UE does not receive the extended DRX parameters information element in the relevant accept message because the AMF rejected its request or because the request was received by AMF not supporting extended idle mode DRX, the UE shall apply its regular discontinuous reception as defined in clause 5.4.5. For NR, Paging Time Window applies for extended DRX lengths greater than 10.24s as defined in TS 38.304 [50]. For WB-E-UTRA, Paging Time Window applies for extended DRX lengths of 10.24s and greater as defined in TS 36.304 [52]. + +When the UE is accessing NR, if the AMF provides an extended idle mode DRX cycle length value of 10.24s, and the registration area of the UE contains only NR cells, the AMF does not include a Paging Time Window. If the AMF provides an extended idle mode DRX cycle length value of 10.24s, and the registration area of the UE contains E-UTRA cells and NR cells if the UE supports both E-UTRA and NR, the AMF includes a Paging Time Window. + +For WB-E-UTRA and LTE-M the eNB broadcasts an indicator for support of extended idle mode DRX in 5GC in addition to the existing indicator for support of extended idle mode DRX in EPC as defined in TS 36.331 [51]. For NR the gNB broadcasts an indicator for support of extended idle mode DRX as defined in TS 38.331 [28]. This indicator is used by the UE in CM-IDLE state. + +NOTE 2: A broadcast indicator for support of extended idle mode DRX is not needed for NB-IoT as it is always supported in NB-IoT. + +The specific negotiation procedure handling is described in TS 23.502 [3]. + +NOTE 3: If the Periodic Registration Update timer assigned to the UE is not longer than the extended idle mode DRX cycle the power savings are not maximised. + +For RAT types that support extended DRX for CM-CONNECTED with RRC\_INACTIVE state, the AMF passes the UE's accepted idle mode eDRX values to NG-RAN. If the UE supports eDRX in RRC\_INACTIVE, based on its UE radio capabilities, NG-RAN configures the UE with an eDRX cycle in RRC\_INACTIVE as specified in TS 38.300 [27] up to the value for the UE's idle mode eDRX cycle as provided by the AMF in "RRC Inactive Assistance Information" as defined in clause 5.3.3.2.5. + +If an eDRX cycle is applied in RRC\_INACTIVE, the RAN can buffer DL packets up to the duration of the eDRX cycle chosen by NG-RAN if the eDRX cycle does not last more than 10.24 seconds. If the CN based MT communication handling support indication is received in RRC Inactive Assistance Information, the NG-RAN may select an eDRX cycle that lasts more than 10.24s. In this case, based on implementation the NG-RAN may send an indication in N2 message that the UE is transitioning to RRC\_INACTIVE state and the NG-RAN determined eDRX values (i.e. the eDRX cycle length and the Paging Time Window length) for RRC\_INACTIVE to the AMF. The CN takes the indication in the N2 message into account, then handles mobile terminated (MT) communication as specified in clause 5.31.7.2.4 and it can apply high latency communication as specified in clause 5.31.8. The AMF replies to NG-RAN that the indication in the N2 message has been taken into account and the MT signalling or data may be buffered by the Core Network based on high latency communication. If and when the NG-RAN chooses to send the indication is up to NG-RAN implementation. If the NG-RAN delays sending the indication and it receives a DL NAS message for the UE, the NG-RAN proceeds as described in clause 4.8.1.1a of TS 23.502 [3]. + +NOTE 4: If the indication that the UE is transitioning to RRC\_INACTIVE state is not sent (or sent after UE has entered RRC\_INACTIVE state) by the NG-RAN then until CN receives it the CN cannot apply the high latency communication functionality, other NFs will not be aware of the UE reachability, certain high latency communication related services provided to the AF via NEF would not be available, NAS message delivery might fail and downlink data in RAN might be lost. + +NOTE 5: The CN based MT communication handling support indication in RRC Inactive Assistance Information is provided when all entities (e.g. AMF, SMF and UPF) involved in the CN support corresponding functionalities (including the support providing buffered downlink data size) based on deployment and configuration. + +When the UE has PDU Session associated with emergency services, the UE and AMF follow regular discontinuous reception as defined in clause 5.4.5 and shall not use the extended idle mode DRX. Extended idle mode DRX parameters may be negotiated while the UE has PDU Session associated with emergency services. When the PDU Session associated with emergency services is released, the UE and AMF shall reuse the negotiated extended idle mode DRX parameters in the last Registration Update procedure. + +The UE shall include the extended DRX parameters information element in each Registration Request message if it still wants to use extended idle mode DRX. At AMF to AMF, AMF to MME and MME to AMF mobility, the extended idle mode DRX parameters are not sent from the old CN node to the new CN node as part of the MM context information. + +##### 5.31.7.2.2 Paging for extended idle mode DRX in E-UTRA and NR connected to 5GC + +###### 5.31.7.2.2.0 General + +For WB-E-UTRA and LTE-M connected to 5GC, the extended idle mode DRX value range will consist of values starting from 5.12s (i.e. 5.12s, 10.24s, 20.48s, etc.) up to a maximum of 2621.44s (almost 44 min). For NB-IoT, the extended idle mode DRX value range will start from 20.48s (i.e. 20.48s, 40.96s, 81.92, etc.) up to a maximum of 10485.76s (almost 3 hours) (see TS 36.304 [52]). For NR, the extended idle mode DRX value range will consist of values starting from 2.56s (i.e. 2.56s, 5.12s, 10.24s, 20.48s, etc.) up to a maximum of 10485.76s (almost 3 hours) (see TS 38.304 [50]). The extended idle mode DRX cycle length is negotiated via NAS signalling. The AMF includes the extended idle mode DRX cycle length for NR, WB-E-UTRA, LTE-M or NB-IoT in paging message to assist the NG-RAN node in paging the UE. For NR, Paging Time Window applies for extended DRX lengths longer than 10.24s as defined in TS 38.304 [50]. For WB-E-UTRA, LTE-M and NB-IoT, Paging Time Window applies for extended DRX lengths of 10.24s and longer as defined in TS 36.304 [52]. + +The network follows the regular paging strategy as defined in clause 5.4.5 when the extended idle mode DRX cycle length is 5.12s or less for WB-E-UTRA, LTE-M and NB-IoT, or 10.24s or less for NR. + +Clauses 5.31.7.2.2.1, 5.31.7.2.2.2 and 5.31.7.2.2.3 apply when the extended idle mode DRX cycle length is 10.24s or longer for WB-E-UTRA, LTE-M and NB-IoT, or longer than 10.24s for NR. + +###### 5.31.7.2.2.1 Hyper SFN, Paging Hyperframe and Paging Time Window length + +A Hyper-SFN (H-SFN) frame structure is defined on top of the SFN used for regular idle mode DRX. Each H-SFN value corresponds to a cycle of the legacy SFN of 1024 radio frames, i.e. 10.24s. When extended idle mode DRX is enabled for a UE, the UE is reachable for paging in specific Paging Hyperframes (PH), which is a specific set of H-SFN values. The PH computation is a formula that is function of the extended idle mode DRX cycle, and a UE specific identifier, as described in TS 36.304 [52] and TS 38.304 [50]. This value can be computed at all UEs and AMFs without need for signalling. The AMF includes the extended idle mode DRX cycle length and the PTW length in paging message to assist the NG-RAN nodes in paging the UE. + +The AMF also assigns a Paging Time Window length, and provides this value to the UE during Registration Update procedures together with the extended idle mode DRX cycle length. The UE first paging occasion is within the Paging Hyperframe as described in TS 36.304 [52] and TS 38.304 [50]. The UE is assumed reachable for paging within the Paging Time Window. The start and end of the Paging Time Window is described in TS 36.304 [52] and TS 38.304 [50]. After the Paging Time Window length, the AMF considers the UE unreachable for paging until the next Paging Hyperframe. + +###### 5.31.7.2.2.2 Loose Hyper SFN synchronization + +NOTE: This clause applies when the extended DRX cycle length is 10.24s or longer for WB-E-UTRA, LTE-M and NB-IoT, and longer than 10.24s for NR. + +In order for the UE to be paged at roughly similar time, the H-SFN of all NG-RAN nodes and AMFs should be loosely synchronized. + +Each NG-RAN node and AMF synchronizes internally the H-SFN counter so that the start of H-SFN=0 coincides with the same a preconfigured time epoch. If NG-RAN nodes and AMFs use different epochs, e.g. due to the use of different time references, the GPS time should be set as the baseline, and the NG-RAN nodes and AMFs synchronize the H-SFN counter based on the GPS epoch considering the time offset between GPS epoch and other time-reference epoch a preconfigured time. It is assumed that NG-RAN nodes and AMFs are able to use the same H-SFN value with accuracy in the order of legacy DRX cycle lengths, e.g. 1 to 2 seconds. There is no need for synchronization at SFN level. + +There is no signalling between network nodes required to achieve this level of loose H-SFN synchronization. + +###### 5.31.7.2.2.3 AMF paging and paging retransmission strategy + +NOTE: This clause applies when the extended DRX cycle length is 10.24s or longer for WB-E-UTRA, LTE-M and NB-IoT, and longer than 10.24s for NR. + +When the AMF receives trigger for paging and the UE is reachable for paging, the AMF sends the paging request. If the UE is not reachable for paging, then the AMF pages the UE just before the next paging occasion. + +The AMF determines the Paging Time Window length and a paging retransmission strategy, and executes the retransmission scheme. + +For extended DRX length of 10.24s, in the paging request message the AMF sends the Paging Time Window to the ng-eNB but does not send the Paging Time Window to the gNB. + +##### 5.31.7.2.3 Paging for a UE registered in a tracking area with heterogeneous support of extended idle mode DRX + +When the UE is registered in a registration area with heterogeneous support of extended idle mode DRX (e.g. comprising WB-E-UTRA and NR cells) and has negotiated eDRX, the AMF shall, for any paging procedure, perform at least one paging attempt during a PTW. + +NOTE: Heterogeneous support of extended idle mode DRX in tracking areas assigned by AMF in a TAI list can result in significant battery life reduction in the UE as compared to homogeneous support by NG-RAN nodes of extended idle mode DRX. + +##### 5.31.7.2.4 Paging for extended DRX for RRC\_INACTIVE in NR connected to 5GC + +For NR, the NG-RAN may request the CN to handle mobile terminated (MT) communication for the UE configured with eDRX for RRC\_INACTIVE state by means of the Connection Inactive procedure with CN based MT communication handling Procedure (see clause 4.8.1.1a of TS 23.502 [3]). This allows the CN to apply high latency communication functions as specified in clause 5.31.8. The NG-RAN provides the determined eDRX values (i.e. the eDRX cycle length and the Paging Time Window length) for RRC\_INACTIVE to AMF (i.e. >10.24s). Based on the request from NG-RAN, the AMF responds to NG-RAN and informs other NFs (e.g. SMF and UPF) involved in downlink data or signalling handling and trigger the data buffering as specified in clause 4.8.1.1a of TS 23.502 [3]. + +When MT data or signalling arrives for a UE in RRC\_INACTIVE state, the other NFs communicate with the AMF for delivery of MT data or signalling. The AMF calculates the UE reachability based on the eDRX values for RRC\_INACTIVE state provided by NG-RAN and triggers NG-RAN paging via an N2 RAN Paging Request message if the UE is considered reachable as specified in clause 4.8.2.2b of TS 23.502 [3]. Otherwise, the AMF stores the information received in the NF request and replies to the requesting NF to apply high latency communication functions as specified in clause 5.31.8 based on eDRX values for RRC\_INACTIVE (e.g. an Estimated Maximum Wait Time is calculated based on eDRX values for RRC\_INACTIVE). When the AMF determines that the UE has become reachable for paging, the AMF uses the stored information to send an N2 RAN Paging Request message. If UPF/SMF provides the downlink data size information, the AMF provides the information to NG-RAN as described in clause 4.8.2.2b of TS 23.502 [3]. + +When the UE resumes the RRC connection as specified in TS 38.300 [27] (e.g. including mobile originated small data transmission procedure), if the NG-RAN had sent the indication for the CN to handle mobile terminated (MT) communication, NG-RAN proceeds as specified in clause 4.8.2.2 of TS 23.502 [3], which indicates to the AMF that the UE is now reachable for downlink data and/or signalling. The AMF then informs other NFs that the UE is now reachable using the high latency communication functions as specified in clause 5.31.8 and MT data and signalling can be delivered to the UE. + +#### 5.31.7.3 MICO mode with Extended Connected Time + +When a UE, using MICO mode, initiates MO signalling or MO data and the AMF is aware of pending or expected MT traffic, the AMF may keep the UE in CM-CONNECTED state and the RAN may keep the UE in RRC\_CONNECTED state for an Extended Connected Time period in order to ensure the downlink data and/or signalling is delivered to the UE. The Extended Connected Time is determined by the AMF and is based on local configuration and/or the Maximum Response Time, if provided by the UDM. + +The AMF maintains the N2 connection for at least the Extended Connected Time and provides the Extended Connected Time value to the RAN. The Extended Connected Time value indicates the minimum time the RAN should keep the UE in RRC\_CONNECTED state regardless of inactivity. The Extended Connected Time value is provided to the RAN together with the + +- NAS Registration Accept message; or +- NAS Service Accept message. + +At inter-RAN node handovers, if some signalling or data are still pending, the target AMF may send the Extended Connected Time value to the target RAN node. + +#### 5.31.7.4 MICO mode with Active Time + +During a Registration procedure the UE may optionally request an Active Time value from the AMF as part of MICO Mode negotiation. In response, if the AMF receives an Active Time value from the UE and determines that the MICO mode is allowed for the UE, the AMF may assign an Active Time value for the UE, e.g. based on local configuration, Expected UE Behaviour if available, UE requested Active Time value, UE subscription information and network policies, and indicates it to the UE during Registration procedure. When an Active Time value is assigned to the UE the AMF shall consider the UE reachable for paging after the transition from CM-CONNECTED to CM-IDLE for the duration of the Active Time. Together with the Active Time value, the UE may request a periodic registration time value as specified in clause 5.31.7.45. + +When the AMF indicates MICO mode with an Active Time to a UE, the registration area may be constrained by paging area size. To avoid paging in the entire PLMN, when the AMF allocates the Active Time the AMF should not allocate "all PLMN" registration area to the UE. + +The UE and AMF shall set a timer corresponding to the Active Time value negotiated during the most recent Registration procedure. The UE and AMF shall start the timer upon entering CM-IDLE state from CM-CONNECTED. When the timer expires (i.e. reaches the Active Time) the UE enters MICO mode and the AMF can deduce that the UE has entered MICO mode and is not available for paging. If the UE enters CM-CONNECTED state before the timer expires, the UE and AMF shall stop and reset the timer. + +If no Active Time value was negotiated during the most recent Registration procedure the UE shall not start the timer and it shall instead enter MICO mode directly upon entering CM-IDLE state. + +Active Time is not transferred between AMF and MME. + +#### 5.31.7.5 MICO mode and Periodic Registration Timer Control + +If the Expected UE Behaviour indicates the absence of DL communication, the AMF may allow MICO mode for the UE and allocate a large periodic registration timer value based on e.g. Network Configuration parameters to the UE so that the UE can maximise power saving between Periodic Registration Updates. + +If the Expected UE Behaviour indicates scheduled DL communication the AMF should allow MICO mode for the UE and allocate a periodic registration timer value such that the UE performs Periodic Registration Update to renegotiate MICO mode before or at the scheduled DL communication time, if the AMF decides to allow MICO mode for the UE. When UE requests the MICO mode with active time, the UE may also request a periodic registration timer value suitable for the latency/responsiveness of the DL communication service known to UE. If the UE wants to change the periodic registration timer value, e.g. when the conditions are changed in the UE, the UE consequently requests the value it wants in the registration procedure. The AMF takes the UE requested periodic registration time value into consideration when providing the periodic registration timer to UE during Registration procedure as specified in clause 4.2.2.2.2 of TS 23.502 [3]. + +If the UE supports 'Strictly Periodic Registration Timer Indication', the UE indicates its capability of supporting 'Strictly Periodic Registration Timer Indication' in the Registration Request message. If the UE indicates its support of 'Strictly Periodic Registration Timer Indication' in the Registration Request message, the AMF may provide a Strictly Periodic Registration Timer Indication to the UE together with the periodic registration timer value, e.g. based on Expected UE Behaviour. If the indication is provided by the AMF, the UE and the AMF shall start the periodic registration timer after completion of the Registration procedure. The UE and the AMF shall neither stop nor restart the periodic registration timer when the UE enters CM-CONNECTED, and shall keep it running while in CM-CONNECTED state and after returning to CM-IDLE state. If and only when the timer expires and the UE is in CM-IDLE, the UE shall perform a Periodic Registration Update. If the timer expires and the UE is in CM-CONNECTED state, the AMF and the UE + +restart the periodic registration timer while still applying 'Strictly Periodic Registration Timer Indication'. The AMF may use the UE Configuration Update procedure to trigger the UE to perform Registration procedure, in which the periodic registration timer value and 'Strictly Periodic Registration Timer Indication' can be renegotiated. + +When the UE and the AMF locally disable MICO mode (e.g. when an emergency service is initiated), the UE and the AMF shall not apply 'Strictly Periodic Registration Timer Indication'. + +If the periodic registration timer is renegotiated during a Registration procedure, e.g. triggered by UE Configuration Update, and if the periodic registration timer is running, then the periodic registration timer is stopped and restarted using the renegotiated value even when the Strictly Periodic Registration Timer Indication was provided to the UE. + +### 5.31.8 High latency communication + +Functions for High latency communication may be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions as specified in clause 5.31.7 or due to discontinuous coverage as described in clause 5.4.13. "High latency" refers to the initial response time before normal exchange of packets is established. That is, the time it takes before a UE has woken up from its power saving state and responded to an initial downlink packet or signal. + +When a NR RedCap UE requests to use the power saving functions as specified in clause 5.31.7, then the AMF may, based on local policy, reroute the Registration Request to another AMF that supports High latency communication as specified in clause 6.3.5. + +High latency communication is supported by extended buffering of downlink data in the UPF, SMF or NEF when a UE is using power saving functions in CM-IDLE state or in RRC\_INACTIVE state, or when the UE is using a satellite access with discontinuous coverage and the UE is not reachable. For UPF anchored PDU sessions the SMF configures during AN release or when NG-RAN indicates via the AMF the UE is in extended DRX for RRC\_INACTIVE, the UPF with user data Forwarding Action Rule and user data Buffering Action Rule according to TS 29.244 [65]. The rules include instructions whether UPF buffering applies or the user data shall be forwarded to the SMF for buffering in the SMF. For NEF anchored PDU sessions only extended buffering in the NEF is supported in this release of the specification. During the Network Triggered Service Request procedure or Mobile Terminated Data Transport procedures when using Control Plane CIoT 5GS Optimisation, the AMF provides an Estimated Maximum Wait Time to the SMF if the SMF indicates the support of extended buffering. The SMF determines the Extended Buffering Time based on the received Estimated Maximum Wait Time or local configuration. The handling is e.g. specified in the Network Triggered Service Request procedure, clauses 4.2.3.3, 4.2.6, 4.24.2 and 4.25.5 of TS 23.502 [3]. + +High latency communication is also supported through notification procedures. The following procedures are available based on different monitoring events: + +- UE Reachability; +- Availability after DDN failure; +- Downlink Data Delivery Status. + +An AF may request a one-time "UE Reachability" notification when it wants to send data to a UE which is using a power saving function (see event subscription procedure in clause 4.15.3.2 of TS 23.502 [3]). The SCS/AS/AF then waits with sending the data until it gets a notification that the UE is reachable (see notification procedures in TS 23.502 [3]). + +An AF may request repeated "Availability after DDN failure" notifications where each UE reachability notification is triggered by a preceding DDN failure, i.e. the AF sends a downlink packet to request a UE reachability notification when the UE becomes reachable. That downlink packet is discarded by the UPF or SMF or NEF (see notification procedures in TS 23.502 [3]). + +An AF may request repeated "Downlink Data Delivery Status" notifications when it wants indications that DL data has been buffered or when buffered DL data has been delivered to the UE. + +If MICO mode or extended idle mode DRX is enabled, Idle Status Indication allows the AF to determine when the UE transitions into idle mode. When requesting to be informed of either "UE Reachability" or "Availability after DDN failure" notification, the AF may also request Idle Status Indication. If the UDM and the AMF support Idle Status Indication, then when the UE for which MICO mode or extended idle mode DRX is enabled transitions into idle mode, the AMF includes in the notification towards the NEF the time at which the UE transitioned into idle mode, the active + +time and the periodic registration update timer granted to the UE by the AMF, the eDRX cycle length and the Suggested number of downlink packets if a value was provided to the SMF. + +An AF may provide parameters related to High latency communication for different methods to UDM, via NEF, as part of provisioning capability as specified in clause 5.20. The UDM can further deliver the parameters to other NFs (e.g. AMF or SMF) as specified in clause 4.15.6 of TS 23.502 [3]. + +If the AMF is aware that some signalling or data is pending in the network for an UE that is known as being unreachable for a long duration, e.g. for UE's having extended idle mode DRX, extended DRX for RRC\_INACTIVE or MICO enabled, the AMF maintains the N2 connection for at least the Extended Connected Time and provides the Extended Connected Time value in a NG-AP message to the RAN. The Extended Connected Time value indicates the minimum time the RAN should keep the UE in RRC\_CONNECTED state regardless of inactivity. At inter-RAN node handovers, if some signalling or data are still pending, the target AMF may send the Extended Connected Time value to the target RAN node. + +### 5.31.9 Support for Monitoring Events + +The Monitoring Events feature is intended for monitoring of specific events in the 3GPP system and reporting such Monitoring Events via the NEF. The feature allows NFs in 5GS to be configured to detect specific events and report the events to the requested party. Clause 5.20 further discusses the Monitoring capabilities of the NEF. + +For CIoT, the list of supported monitoring events is specified in Table 4.15.3.1-1 of TS 23.502 [3]. + +Support for Monitoring Events can be offered via AMF, UDM, NSACF and SMF, and can be reported via the NEF, as specified in clause 4.15.3 of TS 23.502 [3]. + +### 5.31.10 NB-IoT UE Radio Capability Handling + +NB-IoT Radio Capabilities are handled in the network independently from other RATs' Radio Capabilities, see clause 5.4.4.1. + +### 5.31.11 Inter-RAT idle mode mobility to and from NB-IoT + +Tracking Areas are configured so that they do not contain both NB-IoT and other RATs' cells, so when the UE is changing RAT type to or from NB-IoT while remaining registered with 5GC, the UE will perform the Mobility Registration Update procedure, see clause 5.3.2.3. When the UE is changing RAT type to or from NB-IoT and moving between 5GC and EPC, during the Registration, Attach or TAU procedure the RAT type change is determined. + +The specification in this clause does not apply to RAT type corresponding to Non-3GPP Access type. + +PDU session handling is controlled by "PDU Session continuity at inter RAT mobility" in the UE's subscription data, which indicates per DNN/S-NSSAI whether to; + +- maintain the PDU session, +- disconnect the PDU session with a reactivation request, +- disconnect the PDU session without reactivation request, or +- leave it up to local VPLMN policy + +when the UE moves between a "broadband" RAT (e.g. NR or WB-E-UTRA) and a "narrowband" RAT (NB-IoT). + +During PDU session establishment the SMF retrieves the "PDU Session continuity at inter RAT mobility" subscription information (if available) from the UDM. Local SMF configuration is used if "PDU Session continuity at inter RAT mobility" is not available for a PDU Session. + +The AMF informs the SMF at an inter-RAT idle mobility event, e.g. to or from NB-IoT connected to 5GC about the RAT type change in the Nsmf\_PDUSession\_UpdateSMContext message during the Registration procedure. Based on this (H-)SMF handles the PDU session according to "PDU session continuity at inter RAT mobility information" subscription data or based on local policy. + +NOTE: The "PDU Session continuity at inter RAT mobility" and "PDN continuity at inter-RAT mobility" subscription should be the same so that the PDU sessions/PDN connections are handled the same by both CN types. + +During inter-RAT idle mode mobility to NB-IoT, if a PDU session has more than one QoS rule, the SMF shall initiate a PDU session modification procedure as described in TS 23.502 [3] to remove any non-default QoS rule, and maintain only the default QoS rule. + +### 5.31.12 Restriction of use of Enhanced Coverage + +Support of UEs in E-UTRA Enhanced Coverage is specified in TS 36.300 [30]. + +The usage of Enhanced Coverage requires use of extensive resources (e.g. radio and signalling resources). Specific subscribers can be restricted to use the Enhanced Coverage feature through Enhanced Coverage Restricted information that is stored in the UDM as part of subscription data and specifies per PLMN whether the Enhanced Coverage functionality is restricted or not for the UE. For eMTC, the Enhanced Coverage Restricted information indicates whether CE mode B is restricted for the UE, or both CE mode A and CE mode B are restricted for the UE, or both CE mode A and CE mode B are not restricted for the UE. For NB-IoT, the NB-IoT Enhanced Coverage Restricted information indicates whether the Enhanced Coverage is restricted or not for the UE. + +The AMF receives Enhanced Coverage Restricted information from the UDM during the Registration procedure. If the UE includes the support for restriction of use of Enhanced Coverage in the Registration Request message, the AMF based on local configuration, UE Usage setting, UE subscription information and network policies, or any combination of them, determines whether Enhanced Coverage is restricted for the UE and stores updated Enhanced Coverage Restriction information in the UE context in the AMF. If the UE usage setting indicated that UE is "voice centric", then the AMF shall set CE mode B restricted for the UE in Enhanced Coverage Restriction information. + +The AMF sends Enhanced Coverage Restricted information to the UE in the Registration Accept message. The UE shall use the value of Enhanced Coverage Restricted information to determine if enhanced coverage feature is restricted or not. The AMF provides an Enhanced Coverage Restricted information to the RAN via N2 signalling whenever the UE context is established in the RAN, e.g. during N2 Paging procedure, Service Request procedure, Initial Registration and Periodic Registration procedure. + +For roaming UEs, if the UDM doesn't provide any Enhanced Coverage Restricted information or the provided Enhanced Coverage Restricted information is in conflict with the roaming agreement, the AMF uses default Enhanced Coverage Restricted information locally configured in the VPLMN based on the roaming agreement with the subscriber's HPLMN. + +The UE indicates its capability of support for restriction of use of Enhanced Coverage to the AMF in the Registration procedure for the RAT it is camping on. A UE that supports Enhanced Coverage shall also support restriction of the Enhanced Coverage. + +The UE shall assume that restriction for use of Enhanced Coverage indicated by Enhanced Coverage Restricted information is the same in the equivalent PLMNs. NB-IoT cells also broadcast the support of restriction of use of Enhanced Coverage as defined in TS 36.331 [51]. + +If the UE supports CE mode B and use of CE mode B is not restricted according to the Enhanced Coverage Restriction information in the UE context in the AMF, then the AMF shall use the extended NAS-MM timer setting for the UE as specified in TS 24.501 [47] and shall send the extended NAS-SM timer indication during PDU session establishment to the SMF. + +If the UE supports CE mode B and use of CE mode B changes from restricted to unrestricted or vice versa in the Enhanced Coverage Restriction information in the UE context in the AMF (e.g. due to a subscription change) then: + +- The AMF determines when to enforce the change of restriction of use of Enhanced Coverage. +- When the UE is in CM-CONNECTED mode, the AMF can use the UE Configuration Update procedure, as specified in step 3a of clause 4.2.4.2 of TS 23.502 [3], to trigger a mobility registration update procedure in CM-CONNECTED mode for the AMF to inform the change of restriction of Enhanced Coverage towards the UE. +- If the UE has already established PDU sessions, then the AMF shall trigger a PDU session modification to the SMFs serving the UE's PDU sessions to update the use of the extended NAS-SM timer setting as described in step 1f of clause 4.3.3.2 of TS 23.502 [3] when the AMF determines that NAS-SM timer shall be updated due to the change of Enhanced Coverage Restriction. + +- The UE and network applies the new Enhanced Coverage Restriction information after mobility registration procedure is completed. + +Based on the extended NAS-SM timer indication, the SMF shall use the extended NAS-SM timer setting for the UE as specified in TS 24.501 [47]. + +The support for Enhanced Coverage Restriction Control via NEF enables AF to query status of Enhanced Coverage Restriction or enable/disable Enhanced Coverage Restriction per individual UEs. The procedure for Enhanced Coverage Restriction Control via NEF is described in clause 4.27 of TS 23.502 [3]. + +### 5.31.13 Paging for Enhanced Coverage + +Support of UEs in E-UTRA Enhanced Coverage is specified in TS 36.300 [30]. + +Whenever N2 is released and Paging Assistance Data for CE capable UE is available for the UE, the NG-RAN sends it to the AMF as described in clause 4.2.6 of TS 23.502 [3]. + +The AMF stores the received Paging Assistance Data for CE capable UE and then the AMF includes it in every subsequent Paging message for all NG-RAN nodes selected by the AMF for paging. + +If Enhanced Coverage is restricted for the UE as described in clause 5.31.12, the AMF sends the Enhanced Coverage Restriction parameter as defined in TS 38.413 [34]. + +NOTE: Only the NG-RAN node which cell ID is included in the Paging Assistance Data considers the assistance data. + +### 5.31.14 Support of rate control of user data + +#### 5.31.14.1 General + +The rate of user data sent to and from a UE (e.g. a UE using CIoT 5GS Optimisations) can be controlled in two different ways: + +- Serving PLMN Rate Control; +- Small Data Rate Control. + +Serving PLMN Rate Control is intended to allow the Serving PLMN to protect its AMF and the Signalling Radio Bearers in the NG-RAN from the load generated by NAS Data PDUs. + +Small Data Rate Control is intended to allow HPLMN operators to offer customer services such as "maximum of Y messages per day". + +NOTE: Existing Session-AMBR mechanisms are not suitable for such a service since, for radio efficiency and UE battery life reasons, an AMBR of e.g. > 100kbit/s is desirable and such an AMBR translates to a potentially large daily data volume. + +The SMF in the Serving PLMN may send the Small Data rate control parameter for an emergency PDU session. + +#### 5.31.14.2 Serving PLMN Rate Control + +The Serving PLMN Rate Control value is configured in the (V-)SMF. + +NOTE 1: Homogeneous support of Serving PLMN Rate Control in a network is assumed. + +At PDU Session establishment and PDU Session modification, the (V-)SMF may inform the UE and UPF/NEF of any per PDU Session local Serving PLMN Rate Control that the Serving PLMN intends to enforce for NAS Data PDUs. The (V-)SMF shall only indicate a Serving PLMN Rate Control command to the UPF if the PDU Session is using N4 and is set to Control Plane only. The (V-)SMF shall only indicate a Serving PLMN Rate Control command to the NEF if that PDN connection is using NEF. + +Serving PLMN rate control is operator configurable and expressed as "X NAS Data PDUs per deci hour" where X is an integer that shall not be less than 10. There are separate limits for uplink and downlink NAS Data PDUs: + +- The UE shall limit the rate at which it generates uplink NAS Data PDUs to comply with the Serving PLMN policy. In the UE the indicated rate control applies only on the PDU Session where it was received, and therefore the UE shall limit the rate of its uplink NAS Data PDUs to comply with the rate that is indicated for the PDU Session. The indicated rate is valid until the PDU Session is released. +- The UPF/NEF shall limit the rate at which it generates downlink Data PDUs. In the UPF/NEF the indicated rate control applies only on the PDU Session where it was received, and therefore the UPF/NEF shall limit the rate of its downlink Data PDUs to comply with the rate that is indicated for the PDU Session. +- The (V-)SMF may enforce these limits per PDU Session by discarding or delaying packets that exceed these limits. The Serving PLMN Rate does not include SMS using NAS Transport PDUs. The (V-)SMF starts the Serving PLMN Rate Control when the first NAS Data PDU is received. + +NOTE 2: If the UE/UPF/NEF start the Serving PLMN rate control at a different time than the (V-)SMF, PDUs sent within the limit enforced at the UE/UPF/NEF can still exceed the limit enforced by the (V-)SMF. + +NOTE 3 It is assumed that the Serving PLMN Rate is sufficiently high to not interfere with the Small Data Rate Control as the Small Data Rate Control, if used, is assumed to allow fewer messages. NAS PDUs related to exception reports are not subject to the Serving PLMN Rate Control. + +#### 5.31.14.3 Small Data Rate Control + +The (H-)SMF may consider, e.g. based on operator policy, subscription, DNN, S-NSSAI, RAT type etc. to determine whether to apply Small Data Rate Control or not. The (H-)SMF can send a Small Data Uplink Rate Control command to the UE using the PCO information element. The (H-)SMF informs the UPF or NEF of any Small Data Rate Control that shall be enforced. + +The Small Data Rate Control applies to data PDUs sent on that PDU Session by either Data Radio Bearers or Signalling Radio Bearers (NAS Data PDUs). + +The rate control information is separate for uplink and downlink and in the form of: + +- an integer 'number of packets per time unit', and +- an integer 'number of additional allowed exception report packets per time unit' once the rate control limit has been reached. + +The UE shall comply with this uplink rate control instruction. If the UE exceeds the uplink 'number of packets per time unit', the UE may still send uplink exception reports if allowed and the 'number of additional allowed exception reports per time unit' has not been exceeded. The UE shall consider this rate control instruction as valid until it receives a new one from (H-)SMF. + +When a PDU Session is first established, the (H-)SMF may provide the configured Small Data Rate Control parameters to the UE and UPF or NEF. + +When the PDU Session is released, the Small Data Rate Control Status (including the number of packets still allowed in the given time unit, the number of additional exception reports still allowed in the given time unit and the termination time of the current Small Data Rate Control validity period) may be stored in the AMF so that it can be retrieved for a subsequent re-establishment of a new PDU Session. + +At subsequent establishment of a new PDU Session, the (H-)SMF may receive the previously stored Small Data Rate Control Status and if the validity period has not expired, it provides the parameters to the UE in the PCO and to the UPF/NEF as the initially applied parameters, in addition to the configured Small Data Rate Control parameters. If the initially applied parameters are provided, the UE and UPF or NEF shall apply them and shall use the SMF provided configured Small Data Rate Control parameters once the initially applied Small Data Rate Control validity period expires. + +NOTE 1: Storage of Small Data Rate Control Status information for very long time intervals can be implementation specific. + +For the UPF and NEF, Small Data Rate Control is based on a 'maximum allowed rate' per direction. If (H-)SMF provided the 'number of additional allowed exception report packets per time unit', then the 'maximum allowed rate' is equal to the 'number of packets per time unit' plus the 'number of additional allowed exception report packets per time unit', otherwise the 'maximum allowed rate' is equal to the 'number of packets per time unit'. + +The UPF or NEF may enforce the uplink rate by discarding or delaying packets that exceed the 'maximum allowed rate'. The UPF or NEF shall enforce the downlink rate by discarding or delaying packets that exceed the downlink part of the 'maximum allowed rate'. + +NOTE 2: It is assumed that the Serving PLMN Rate is sufficiently high to not interfere with the Small Data Rate Control as the Small Data Rate Control, if used, is assumed to allow fewer messages. NAS PDUs related to exception reports are not subject to the Serving PLMN Rate Control. + +For NB-IoT the AMF maintains an "MO Exception Data Counter" which is incremented when the RRC establishment cause "MO exception data" is received from NG-RAN. The AMF reports whether the UE accessed using "MO exception data" RRC establishment cause, to all (H-)SMFs which have PDU Sessions that are subject to Small Data Rate Control and if the UE is accessing using "MO exception data" then the "MO Exception Data Counter" is also provided by the AMF. The SMF indicates each use of the RRC establishment cause "MO Exception Data" by including the related counter on the charging information. + +NOTE 3: Since Exception Data PDUs and normal priority PDUs cannot be distinguished within an RRC connection, the AMF is only counting the number of RRC Connection establishments with "MO Exception data" priority. + +If the UE moves to EPC then the UE and the PGW-U+UPF store the current Small Data Rate Control Status for all PDU Sessions that are not released. If the UE moves back to 5GC the stored Small Data Rate Control Status is restored and continues to apply to PDU Session(s) that are moved from EPC to 5GC, taking into account remaining validity period of the stored Small Data Rate Control Status. When the UE moves to EPC the Small Data Rate Control Status for all PDU Session(s) may also be stored in the AMF if the PDU Session is released while the UE is connected to EPC and re-established when the UE moves to 5GC. The time to store the Small Data Rate Control Status information is implementation specific. + +### 5.31.15 Control Plane Data Transfer Congestion Control + +NAS level congestion control may be applied in general for all NAS messages. To enable congestion control for control plane data transfer, a Control Plane data back-off timer is used, see clause 5.19.7.6. + +### 5.31.16 Service Gap Control + +Service Gap Control is an optional feature intended for CIoT UEs to control the frequency at which these UEs can access the network. That is, to ensure a minimum time gap between consecutive Mobile Originated data communications initiated by the UE. This helps reducing peak load situations when there are a large number of these UEs in an operator network. Service Gap Control is intended to be used for "small data allowance plans" for MTC/CIoT UEs where the applications are tolerant to service latency. + +NOTE 1: Time critical applications, such as regulatory prioritized services like Emergency services can suffer from the latency caused by the Service Gap Control feature. Therefore Service Gap Control feature is not recommended for subscriptions with such applications and services. + +Service Gap Time is a subscription parameter used to set the Service Gap timer and is enforced in the UE and in the AMF on a per UE level (i.e. the same Service Gap Timer applies for all PDU Sessions that the UE has). The UE indicates its capability of support for Service Gap Control in the Registration Request message to the AMF. The AMF passes the Service Gap Time to the UE in the Registration Accept message for a UE that has indicated its support of the Service Gap Control. The Service Gap Control shall be applied in a UE when a Service Gap Time is stored in the UE context and applied in the AMF when the Service Gap Time is stored in the UE Context in the AMF. + +Service Gap Control requires the UE to stay in CM-IDLE mode for at least the whole duration of the Service Gap timer before triggering Mobile Originated user data transmission, except for procedures that are exempted (see TS 24.501 [47]). The Service Gap timer shall be started each time a UE moves from CM-CONNECTED to CM-IDLE, unless the connection request was initiated by the paging of a Mobile Terminated event, or after a Mobility or Periodic Registration procedure without Follow-on Request indication and without Uplink data status, which shall not trigger a new or extended Service Gap interval. When a Service Gap timer expires, the UE is allowed to send a connection request again. If the UE does so, the Service Gap timer will be restarted at the next CM-CONNECTED to CM-IDLE transition. + +The Service Gap control is applied in CM-IDLE state only and does not impact UE Mobile Originated user data transmission or Mobile Originated signalling in CM-CONNECTED state. The Service Gap timer is not stopped upon + +CM-IDLE state to CM-CONNECTED state transition. The UE shall not initiate connection requests for MO user plane data, MO control plane data, or MO SMS when a Service Gap timer is running. The UE shall not initiate PDU Session Establishment Requests when a Service Gap timer is running, unless it is for Emergency services which are allowed. CM-CONNECTED with RRC\_INACTIVE is not used for UEs that have a Service Gap Time configured. + +NOTE 2: As a consequence of allowing Initial Registration Request procedure, the UE with a running Service Gap timer does not initiate further MO signalling, except for Mobility Registration procedure, until the UE receives MT signalling or after the UE has moved to CM-IDLE state and the Service Gap Timer is not running. + +NOTE 3: Implementations need to make sure that latest and up-to-date data are always sent when a Service Gap timer expires. + +The AMF may enforce the Service Gap timer by rejecting connection requests for MO user plane data, MO control plane data, or MO SMS when a Service Gap timer is running. The AMF may enforce the Service Gap timer by not allowing MO signalling after Initial Registration requests when a Service Gap timer is running except for Mobility Registration procedure, Periodic Registration procedure or access to the network for regulatory prioritized services like Emergency services, which are allowed. When rejecting the connection requests and the SM signalling after Initial Registration Requests while the Service Gap timer is running, the AMF may include a Mobility Management back-off timer corresponding to the time left of the current Service Gap timer. For UEs that do not support Service Gap Control (e.g. pre-release-16 UEs), Service Gap Control may be enforced using "General NAS level congestion control" as defined in clause 5.19.7.2. + +NOTE 4: After MT signalling in CM-CONNECTED state the AMF does not further restrict MO signalling when a Service Gap timer is running as this case is considered equal to a connectivity request in response to paging. + +When the AMF starts the Service Gap timer, the AMF should invoke the Service Gap timer with a value that is slightly shorter than the Service Gap Time value provided to the UE based on the subscription information received from the UDM. + +NOTE 5: This ensures that the AMF does not reject any UE requests just before the Service Gap timer expires e.g. because of slightly unsynchronized timers between UE and AMF. + +A UE which transitions from a MICO mode or eDRX power saving state shall apply Service Gap Control when it wakes up if the Service Gap timer is still running. + +Additional aspects of Service Gap Control: + +- Service Gap Control applies in all PLMNs. +- When the Service Gap timer is running and the UE receives paging, the UE shall respond as normal. +- Service Gap Control does not apply to exception reporting for NB-IoT. +- Access to the network for regulatory prioritized services like Emergency services are allowed when a Service Gap timer is running. +- Service Gap Control shall be effective also for UEs performing de-registration and re-registration unless access to the network for regulatory prioritized services like Emergency services is required. +- If the Service Gap timer is running, the Service Gap is applied at PLMN selection as follows: + - a) Re-registration to the registered PLMN: The remaining Service Gap timer value survives. + - b) Registration to a different PLMN: The remaining Service Gap timer value survives. + - c) USIM swap: The Service Gap timer is no longer running and the Service Gap feature does not apply, unless re-instantiated by the serving PLMN. +- Multiple uplink packets and downlink packets are allowed during one RRC connection for UE operating within its Rate Control limits. + +The following procedures are impacted by Service Gap Control: + +- Registration Procedure, see clause 4.2.2.2 of TS 23.502 [3]; + +- UE Triggered Service Request, see clause 4.2.3.2 of TS 23.502 [3]; + +NOTE 6: Since UE triggered Service Request is prevented by Service Gap timer, this implicitly prevents the UE from initiating UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation (see clause 4.24.1 of TS 23.502 [3]), NEF Anchored Mobile Originated Data Transport (see clause 4.25.4 of TS 23.502 [3]) and MO SMS over NAS in CM-IDLE (see clause 4.13.3.3 of TS 23.502 [3]). + +### 5.31.17 Inter-UE QoS for NB-IoT + +To allow NG-RAN to prioritise resource allocation between different UEs accessing via NB-IoT when some of the UEs are using Control Plane CIoT 5GS Optimisation, NG-RAN may, based on configuration, retrieve from the AMF the subscribed NB-IoT UE Priority for any UE accessing via NB-IoT by using the UE's 5G-S-TMSI as the identifier. + +In order to reduce signalling load on the AMF, NG-RAN may be configured to request the NB-IoT UE Priority from the AMF e.g. only when the NG-RAN's NB-IoT load exceeds certain threshold(s) or when the NG-RAN needs to cache the QoS profile. + +### 5.31.18 User Plane CIoT 5GS Optimisation + +User Plane CIoT 5GS Optimisation enables transfer of user plane data from CM-IDLE without the need for using the Service Request procedure to establish Access Stratum (AS) context in NG-RAN and UE. + +If the following preconditions are met: + +- UE and AMF negotiated support User Plane CIoT 5GS Optimisation (see clause 5.31.2) over NAS, +- the UE has indicated support of User Plane CIoT 5GS Optimisation in the UE radio capabilities as defined in TS 36.331 [51], +- AMF has indicated User Plane CIoT 5GS Optimisation support for the UE to NG-RAN, +- the UE has established at least one PDU session with active UP connection, i.e. AS context is established in NG-RAN and the UE, + +then the RRC connection can be suspended by means of the Connection Suspend Procedure (see clause 4.8.1.2 of TS 23.502 [3]). + +Based on a trigger from the NAS layer when a UE is in CM-IDLE with Suspend, the UE should attempt the Connection Resume in CM-IDLE with Suspend procedure (clause 4.8.2.3 of TS 23.502 [3]). If the Connection Resume in CM-IDLE with Suspend procedure fails, the UE initiates the pending NAS procedure. To maintain support for User Plane CIoT 5GS Optimisation for UE mobility across different NG-RAN nodes, the AS Context should be transferred between the NG-RAN nodes, see TS 38.300 [27] and TS 38.423 [99]. + +For MT data or signalling when the UE is in CM-IDLE with Suspend, Network Triggered Service Request procedure (clause 4.2.3.3 of TS 23.502 [3]) applies. + +By using the Connection Suspend Procedure: + +- the UE at transition into CM-IDLE stores the AS information; +- NG-RAN stores the AS information, the NGAP UE association and the PDU session context for that UE; +- AMF stores the NGAP UE association and other information necessary to later resume the UE, interacts with the SMF(s) to deactivate the user plane resources for the UE's PDU Sessions and enters CM-IDLE. + +NG-RAN may decide based on implementation to delete the stored UE context and NGAP association. In that case, the RAN shall initiate the AN Release procedure as described in clause 4.2.6 of TS 23.502 [3]. NG-RAN does not initiate any RRC procedure to notify the UE of the UE context release. + +By using the Connection Resume in CM-IDLE with Suspend procedure: + +- the UE resumes the connection from CM-IDLE with the network using the AS information stored during the Connection Suspend procedure; +- NG-RAN notifies the AMF that the connection with the UE has been resumed; + +- AMF enters CM-CONNECTED and interacts with the SMF to activate the user plane resources for the UE's PDU Sessions. + +Early Data Transmission may be initiated by the UE for mobile originated User Plane CIoT 5GS Optimisation during Connection Resume. + +If the AMF establishes an NGAP UE association with a new NG-RAN node different from the stored NGAP UE association, e.g. the UE initiates service request or registration procedure from a different NG-RAN node, the AMF initiates UE N2 release command towards the old NG-RAN node. + +NG-RAN maintains the N3 tunnel endpoint information while a UE is in CM-IDLE with Suspend. UPF is instructed to remove DL N3 Tunnel Info of AN during Connection Suspend procedure, while UPF keeps UL N3 Tunnel Info (i.e. UPF accepts and forwards UL data). If a UE sends MO data with resume procedure, the NG-RAN can send the MO data to the UPF which is addressed by the N3 tunnel endpoint information. In the case of change of serving NG-RAN node due to UE mobility, if NG-RAN determines that it is not able to connect to the UPF which is addressed by the N3 tunnel endpoint information, NG-RAN performs Path Switch procedure before sending the MO data received from the UE. + +Early Data Transmission may be initiated by the UE for mobile originated User Plane CIoT 5GS Optimisation when the RAT Type is E-UTRA. + +### 5.31.19 QoS model for NB-IoT + +5GC QoS model described in clause 5.7 applies to NB-IoT with the following requirements: + +- The default QoS rule shall be the only QoS rule of a PDU Session for a UE connected to 5GC via NB-IoT. There is only one QoS Flow (corresponding to the default QoS rule) per PDU session. +- Reflective QoS is not supported over NB-IoT. +- For NB-IoT, there is a 1:1 mapping between the QoS Flow corresponding to the default QoS of a PDU session and a Data Radio Bearer when user plane resources are active for that PDU session. +- A maximum of two Data Radio Bearers are supported over NB-IoT. Therefore, at most two PDU sessions can have active user plane resources at the same time. +- The capability of multiple UP resource support for NB-IoT UEs is indicated in the UE 5GMM Core Network Capability (see TS 24.501 [47]). During PDU Session Establishment or UP resource activation, the AMF checks if the UE can support the establishment of user plane resources (See clause 4.2.3.2 and clause 4.3.2.2.1 of TS 23.502 [3]). + +### 5.31.20 Category M UEs differentiation + +This functionality is used by the network to identify traffic to/from Category M UEs, e.g. for charging differentiation. + +A Category M UE using E-UTRA shall provide a Category M indication to the NG-RAN during RRC Connection Establishment procedure as defined in TS 36.331 [51]. + +When the UE has provided a Category M indication to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an LTE-M Indication to the AMF in the Initial UE Message (see clause 4.2.2.2.1 of TS 23.502 [3] and TS 38.413 [34]). + +When the AMF receives an LTE-M Indication from NG-RAN in an Initial UE Message or from an MME during EPS to 5GS handover, the AMF shall store the LTE-M Indication in the UE context, consider that the RAT type is LTE-M and signal it accordingly to the SMSF during registration procedure for SMS over NAS, to the SMF during PDU Session Establishment or PDU Session Modification procedure. The PCF will also receive the RAT Type as LTE-M, when applicable, from the SMF during SM Policy Association Establishment or SM Policy Association Modification procedure. + +The NFs generating CDRs shall include the LTE-M RAT type in their CDRs. + +Upon AMF change or inter-system mobility from 5GS to EPS, the source AMF shall provide the "LTE-M Indication" to the target AMF or MME as part of the UE context. + +During EPS to 5GS Mobility Registration Procedure, the AMF shall disregard any "LTE-M Indication" received from the MME in the UE context (see TS 23.401 [26]), and take into account the "LTE-M Indication" received from NG-RAN, as specified above. + +## 5.32 Support for ATSSS + +### 5.32.1 General + +The ATSSS feature is an optional feature that may be supported by the UE and the 5GC network. + +The ATSSS feature enables a multi-access PDU Connectivity Service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network and two independent N3/N9 tunnels between the PSA and RAN/AN. The multi-access PDU Connectivity Service is realized by establishing a Multi-Access PDU (MA PDU) Session, i.e. a PDU Session that may have user-plane resources on two access networks. This assumes both 3GPP access and non-3GPP access are allowed for the S-NSSAI of the PDU Session. + +The UE may request a MA PDU Session when the UE is registered via both 3GPP and non-3GPP accesses, or when the UE is registered via one access only. + +After the establishment of a MA PDU Session, and when there are user-plane resources on both access networks, the UE applies network-provided policy (i.e. ATSSS rules) and considers local conditions (such as network interface availability, signal loss conditions, user preferences, etc.) for deciding how to distribute the uplink traffic across the two access networks. Similarly, the UPF anchor of the MA PDU Session applies network-provided policy (i.e. N4 rules) and feedback information received from the UE via the user-plane (such as access network Unavailability or Availability) for deciding how to distribute the downlink traffic across the two N3/N9 tunnels and the two access networks. When there are user-plane resources on only one access network, the UE applies the ATSSS rules and considers local conditions for triggering the establishment or activation of the user plane resources over another access. + +The type of a MA PDU Session may be one of the following types defined in clause 5.6.1: IPv4, IPv6, IPv4v6, and Ethernet. In this release of the specification, the Unstructured type is not supported. The clause 5.32.6.2.1, the clause 5.32.6.2.2 and the clause 5.32.6.3.1 below define what Steering Functionalities can be used for each supported type of a MA PDU Session. + +The handling of 3GPP PS Data Off feature for MA PDU Session is specified in clause 5.24. + +The ATSSS feature can be supported over any type of access network, including untrusted and trusted non-3GPP access networks (see clauses 4.2.8 and 5.5), wireline 5G access networks (see clause 4.2.8), etc. as long as a MA PDU Session can be established over this type of access network. + +In this Release of the specification, a MA PDU Session using IPv6 multi-homing (see clause 5.6.4.3) or UL Classifier (see clause 5.6.4.2) is not specified. + +In this Release of the specification, support for ATSSS assumes SMF Service Areas covering the whole PLMN or that a MA PDU Session is released over both accesses when the UE moves out of the SMF Service Area. + +A MA PDU Session does not support LADN. If the AMF receives a request to establish a MA PDU Session for a LADN DNN, the AMF shall reject the request. If the AMF receives a request to establish a PDU Session for a LADN DNN with "MA PDU Network-Upgrade Allowed" indication, the AMF shall not forward "MA PDU Network-Upgrade Allowed" indication to the SMF. + +If the UE, due to mobility, moves from being served by a source AMF supporting ATSSS to a target AMF not supporting ATSSS, the MA PDU Session is released as described in TS 23.502 [3]. + +NOTE 1: Deployment of ATSSS that is homogeneous per PLMN, or network slice enables consistent behaviour. In the case of non-homogenous support of ATSSS in a PLMN/slice (i.e. some NFs in a PLMN/slice may not support ATSSS), MA PDU Sessions can be released due to UE mobility. + +A Multi-Access PDU Session may, for the 3GPP access and/or non-3GPP access, use user-plane resources of an associated PDN Connection in EPC (e.g. one 3GPP access path via EPC and one non-3GPP access path via 5GC or one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC). Such use of ATSSS with EPS interworking may apply to Ethernet and IP-based PDU Session and PDN Connection types. + +NOTE 2: Co-existence with NBIFOM is not defined. It is assumed that NBIFOM and the multi-access connectivity described in this clause are not deployed in the same network. + +NOTE 3: To the MME and SGW this is a regular PDN Connection and the support for ATSSS is transparent to MME and SGW. + +For a MA PDU Session established for the Ethernet PDU Session type, if the UE has not indicated support for Ethernet PDN connection type or if the network does not support Ethernet PDN connection type, when the 3GPP access use user-plane resources of an associated PDN Connection, the following takes place: + +- The SMF+PGW-C considers that the Multi-Access PDU Session is still using the Ethernet PDU Session / PDN Connection type but in a restricted mode where EPS signalling can only refer to non-IP PDN Connection type. +- MAR rules in the UPF are still used for distributing DL traffic between 3GPP access and non-3GPP access. +- For traffic on 3GPP access, the SMF may update N4 rules and QoS rules/EPS bearer contexts on the UE to take into account that no QoS differentiation is possible over 3GPP access. + +Support of Multi-Access PDU Sessions using one leg associated with PDN Connection in EPC and one leg associated with PDU Session in 5GC is further defined in TS 23.502 [3]. + +The following clauses specify the functionality that enables ATSSS. + +### 5.32.2 Multi Access PDU Sessions + +A Multi-Access PDU (MA PDU) Session is managed by using the session management functionality specified in clause 5.6, with the following additions and modifications: + +- When the UE wants to request a new MA PDU Session: + - If the UE is registered to the same PLMN over 3GPP and non-3GPP accesses, then the UE shall send a PDU Session Establishment Request over any of the two accesses. The UE also provides Request Type as "MA PDU Request" in the UL NAS Transport message. The AMF informs the SMF that the UE is registered over both accesses and this triggers the establishment of user-plane resources on both accesses and two N3/N9 tunnels between PSA and the RAN/AN. + - If the UE is registered to different PLMNs over 3GPP and non-3GPP accesses, then the UE shall send a PDU Session Establishment Request over one access. The UE also provides Request Type as "MA PDU Request" in the UL NAS Transport message. After this PDU Session is established with one N3/N9 tunnel between the PSA and (R)AN established, the UE shall send another PDU Session Establishment Request over the other access. The UE also provides the same PDU Session ID and Request Type as "MA PDU Request" in the UL NAS Transport message. Two N3/N9 tunnels and User-plane resources on both accesses are established. + +- If the UE is registered over one access only, then the UE shall send a PDU Session Establishment Request over this access. The UE also provides Request Type as "MA PDU Request" in the UL NAS Transport message. One N3/N9 tunnel between the PSA and (R)AN and User-plane resources on this access only are established. After the UE is registered over the second access, the UE shall establish user-plane resources on the second access. +- In the PDU Session Establishment Request that is sent to request a new MA PDU Session, the UE shall provide also its ATSSS capabilities, which indicate the steering functionalities and the steering modes supported in the UE. These functionalities are defined in clause 5.32.6. +- If the UE indicates it is capable of supporting: + - the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); + +and the network accepts to activate this functionality, then the network may provide to UE Measurement Assistance Information (see details in clause 5.32.5) and shall provide to UE one or more ATSSS rules. + +NOTE 1: As specified in Table 5.32.8-1 and in Table 5.8.5.8-1, the ATSSS-LL functionality cannot be used together with the Redundant steering mode. When the UE indicates it is capable of supporting the ATSSS-LL functionality with any steering mode, it is implied that the UE can support the ATSSS-LL functionality with any steering mode except the Redundant steering mode. + +- If the UE indicates it is capable of supporting: + - the MPTCP functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or + - the MPTCP functionality with any steering mode and the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); + +and the network accepts to activate these functionalities, then the network provides MPTCP proxy information to UE, and allocates to UE (a) one IP address/prefix for the MA PDU session (as defined in clause 5.8.2.2) and (b) two additional IP addresses/prefixes, called "MPTCP link-specific multipath" addresses. Further details are provided in clause 5.32.6.2.1. In addition, the network may provide to UE Measurement Assistance Information and shall provide to UE one or more ATSSS rules. If the UE supports the ATSSS-LL functionality with only the Active-Standby steering mode, the network shall provide to UE an ATSSS rule for non-MPTCP traffic. The ATSSS rule for non-MPTCP traffic shall use the ATSSS-LL functionality and the Active-Standby Steering Mode to indicate how the non-MPTCP traffic shall be transferred across the 3GPP access and the non-3GPP access in the uplink direction. + +- If the UE indicates it is capable of supporting + - the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or + - the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); + +and the network accepts to activate these functionalities, then the network provides MPQUIC proxy information to UE, and allocates to UE (a) one IP address/prefix for the MA PDU session (as defined in clause 5.8.2.2) and (b) two additional IP addresses/prefixes, called "MPQUIC link-specific multipath" addresses. Further details are provided in clause 5.32.6.2.2. In addition, the network may provide to UE Measurement Assistance Information and shall provide to UE one or more ATSSS rules. If the UE supports the ATSSS-LL functionality with only the Active-Standby steering mode, the network shall provide to UE an ATSSS rule for non-MPQUIC traffic. The ATSSS rule for non-MPQUIC traffic shall use the ATSSS-LL functionality and the Active-Standby Steering Mode to indicate how the non-MPQUIC traffic shall be transferred across the 3GPP access and the non-3GPP access in the uplink direction. + +- If the UE indicates it is capable of supporting + - the MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or + +- the MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); + +and the network accepts to activate these functionalities, then the network provides MPTCP proxy information and MPQUIC proxy information to UE and allocates to UE (a) one IP address/prefix for the MA PDU session (as defined in clause 5.8.2.2), (b) two additional IP addresses/prefixes, called "MPTCP link-specific multipath" addresses, and (c) two additional IP addresses/prefixes, called "MPQUIC link-specific multipath" addresses. Further details are provided in clause 5.32.6.2.1 and in clause 5.32.6.2.2. In addition, the network may provide to UE Measurement Assistance Information and shall provide to UE one or more ATSSS rules. If the UE supports the ATSSS-LL functionality with only the Active-Standby steering mode, the network shall provide to UE an ATSSS rule for non-MPTCP and non-MPQUIC traffic (i.e. the traffic for which neither the MPTCP nor the MPQUIC functionalities are applied). The ATSSS rule for non-MPTCP and non-MPQUIC traffic shall use the ATSSS-LL functionality and the Active-Standby Steering Mode to indicate how the non-MPTCP and non-MPQUIC traffic shall be transferred across the 3GPP access and the non-3GPP access in the uplink direction. + +NOTE 2: The "MPTCP link-specific multipath" addresses and the "MPQUIC link-specific multipath" addresses can be the same. + +- If the UE requests an S-NSSAI, this S-NSSAI should be allowed on both accesses. Otherwise, the MA PDU Session shall not be established. +- The SMF determines the ATSSS capabilities supported for the MA PDU Session based on the ATSSS capabilities provided by the UE and per DNN configuration on SMF, as follows: + - a) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode" (as specified in clause 5.32.6.1), then: + - i) If the DNN configuration allows MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), including RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (2) MPTCP and ATSSS-LL with Active-Standby mode in the uplink. + +NOTE 3: In this case, it is assumed that ATSSS-LL with "Smallest Delay" steering mode is selected for the downlink only when the UPF can measure RTT without using the PMF protocol, e.g. by using other means not defined by 3GPP such as using the RTT measurements of MPTCP. + +- ii) If the DNN configuration allows MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), but not RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP in the downlink (2) ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (3) MPTCP and ATSSS-LL with Active-Standby mode in the uplink. + - iii) If the DNN configuration allows MPTCP with any steering mode and ATSSS-LL with only Active-Standby steering mode, the MA PDU Session is capable of MPTCP and ATSSS-LL with Active-Standby mode in the uplink and in the downlink. +- b) If the UE includes in its ATSSS capabilities "MPQUIC functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode" (as specified in clause 5.32.6.1), then: + - i) If the DNN configuration allows MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), including RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (2) MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. + +NOTE 4: In this case, it is assumed that ATSSS-LL with "Smallest Delay" steering mode is selected for the downlink only when the UPF can measure RTT without using the PMF protocol, e.g. by using other means not defined by 3GPP such as using the RTT measurements of MPQUIC. + +- ii) If the DNN configuration allows MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), but not RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPQUIC in the downlink (2) ATSSS-LL with any steering mode (i.e. any + +Steering Mode allowed for ATSSS-LL) in the downlink, and (3) MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. + +- iii) If the DNN configuration allows MPQUIC with any steering mode and ATSSS-LL with only Active-Standby steering mode, the MA PDU Session is capable of MPQUIC and ATSSS-LL with Active-Standby mode in the uplink and in the downlink. +- c) If the UE includes in its ATSSS capabilities "MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1), and the DNN configuration allows MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), the MA PDU Session is capable of MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the uplink and in the downlink. +- d) If the UE includes in its ATSSS capabilities "ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1) and the DNN configuration allows ATSSS-LL with any steering mode allowed for ATSSS-LL, the MA PDU Session is capable of ATSSS-LL with any steering mode allowed for ATSSS-LL in the uplink and in the downlink. +- e) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1), and the DNN configuration allows MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), the MA PDU Session is capable of MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the uplink and in the downlink. +- f) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1), and the DNN configuration allows MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), the MA PDU Session is capable of MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the uplink and in the downlink. +- g) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with only the Active-Standby steering mode" (as specified in clause 5.32.6.1), then: + - i) If the DNN configuration allows MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), including RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (2) MPTCP and MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. + +NOTE 5: In this case, it is assumed that ATSSS-LL with "Smallest Delay" steering mode is selected for the downlink only when the UPF can measure RTT without using the PMF protocol, e.g. by using other means not defined by 3GPP such as using the RTT measurements of MPTCP or MPQUIC. + +- ii) If the DNN configuration allows MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), but not RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP and MPQUIC in the downlink (2) ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (3) MPTCP and MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. +- iii) If the DNN configuration allows MPTCP and MPQUIC with any steering mode and ATSSS-LL with only Active-Standby steering mode, the MA PDU Session is capable of MPTCP and MPQUIC and ATSSS-LL with Active-Standby mode in the uplink and in the downlink. + +The SMF provides the ATSSS capabilities of the MA PDU Session to the PCF during PDU Session Establishment. + +- The PCC rules provided by PCF include MA PDU Session Control information (see TS 23.503 [45]). They are used by SMF to derive ATSSS rules for the UE and N4 rules for the UPF. When dynamic PCC is not used for the MA PDU Session, the SMF shall provide ATSSS rules and N4 rules based on local configuration (e.g. based on DNN or S-NSSAI). + +- The UE receives ATSSS rules from SMF, which indicate how the uplink traffic should be routed across 3GPP access and non-3GPP access. Similarly, the UPF receives N4 rules from SMF, which indicate how the downlink traffic should be routed across 3GPP access and non-3GPP access. +- When the SMF receives a PDU Session Establishment Request and a "MA PDU Request" indication and determines that UP security protection (see clause 5.10.3) is required for the PDU Session, the SMF shall only confirm the establishment of the MA PDU session if the 3GPP access network can enforce the required UP security protection. The SMF needs not confirm whether the non-3GPP access can enforce the required UP security protection. +- The UE indicates during MA PDU Session Establishment to the AMF whether it supports non-3GPP access path switching, i.e. whether the UE can transfer the non-3GPP access path of the MA PDU Session from a source non-3GPP access (N3IWF/TNGF) to a target non-3GPP access (a different N3IWF/TNGF). If the UE has indicated support for non-3GPP access path switching and the AMF supports non-3GPP access path switching, the AMF selects an SMF that supports non-3GPP access path switching, if such an SMF is available. If the AMF supports to maintain two N2 connections for non-3GPP access during the Registration procedure and the selected SMF supports non-3GPP path switching, the AMF indicates whether the UE supports non-3GPP path switching to the SMF. The SMF indicates support for non-3GPP path switching to the UE in the PDU Session Establishment Accept message. + +NOTE 6: If the AMF selects an SMF not supporting non-3GPP access path switching, the non-3GPP access path switching can still be performed with the AMF triggering release of the old user plane resources before new user plane resources are established. + +- After the MA PDU Session establishment: + - At any given time, the MA PDU session may have user-plane resources on both 3GPP and non-3GPP accesses, or on one access only, or may have no user-plane resources on any access. + - The AMF, SMF, PCF and UPF maintain their MA PDU Session contexts, even when the UE deregisters from one access (but remains registered on the other access). + - When the UE deregisters from one access (but remains registered on the other access), the AMF informs the SMF to release the resource of this access type in the UPF for the MA PDU Session. Subsequently, the SMF notifies the UPF that the access type has become unavailable and the N3/N9 tunnel for the access type are released. + - If the UE wants to add user-plane resources on one access of the MA PDU Session, e.g. based on access network performance measurement and/or ATSSS rules, then the UE shall send a PDU Session Establishment Request over this access containing PDU Session ID of the MA PDU Session. The UE also provides Request Type as "MA PDU Request" and the same PDU Session ID in the UL NAS Transport message. If there is no N3/N9 tunnel for this access, the N3/N9 tunnel for this access is established. + - If the UE wants to re-activate user-plane resources on one access of the MA PDU Session, e.g. based on access network performance measurement and/or ATSSS rules, then the UE shall initiate the UE Triggered Service Request procedure over this access. + - If the network wants to re-activate the user-plane resources over 3GPP access or non-3GPP access of the MA PDU Session, the network shall initiate the Network Triggered Service Request procedure, as specified in clause 4.22.7 of TS 23.502 [3]. + - If the UE wants to move the non-3GPP user-plane resources of the MA PDU Session from a source non-3GPP access (e.g. source N3IWF or TNGF) to a target non-3GPP access (e.g. target N3IWF or TNGF), the UE initiates a Mobility Registration Update via the target non-3GPP access as described in TS 23.502 [3], clause 4.22.9.5. This procedure may also be used to move the non-3GPP user-plane resources of single access PDU Session(s). + +NOTE 7: The UE can request activation of single access PDU Session(s) over the target non-3GPP access while performing Mobility Registration Update procedure according to the existing procedure. + +- The SMF may add, remove or update one or more individual ATSSS rules of the UE by sending new or updated ATSSS rules with the corresponding Rule IDs to the UE. + +A MA PDU Session may be established either: + +- a) when it is explicitly requested by an ATSSS-capable UE; or +- b) when an ATSSS-capable UE requests a single-access PDU Session but the network decides to establish a MA PDU Session instead. This is an optional scenario specified in clause 4.22.3 of TS 23.502 [3], which may occur when the UE requests a single-access PDU Session but no policy (e.g. no URSP rule) and no local restrictions in the UE mandate a single access for the PDU Session. + +A MA PDU Session may be established during a PDU Session modification procedure when the UE moves from EPS to 5GS, as specified in clause 4.22.6.3 of TS 23.502 [3]. + +The AMF indicates as part of the Registration procedure whether ATSSS is supported or not. When ATSSS is not supported, the UE shall not + +- request establishment of a MA PDU Session (as described in clause 4.22.2 of TS 23.502 [3]); or +- request addition of User Plane resources for an existing MA PDU Session (as described in clause 4.22.7 of TS 23.502 [3]); or +- request establishment of a PDU Session with "MA PDU Network-Upgrade Allowed" indication (as described in clause 4.22.3 of TS 23.502 [3]); or +- request PDU Session Modification with Request Type of "MA PDU request" or with "MA PDU Network-Upgrade Allowed" indication after moving from EPC to 5GC (as described in clause 4.22.6.3 of TS 23.502 [3]). + +The AMF indicates as part of the Registration procedure whether it supports non-3GPP access path switching. When the AMF does not indicate support of non-3GPP access path switching, the UE shall not perform the Mobility Registration Update procedure for non-3GPP access path switching, i.e. to switch traffic from a source non-3GPP access to a target non-3GPP access. The SMF indicates as part of the PDU Session Establishment procedure whether it supports non-3GPP access path switching. If the UE has more than one PDU session and at least one serving SMF for the PDU Sessions supports non-3GPP access path switching, the UE may include ("Non-3GPP path switching while using old AN resources") indication when the UE performs the Mobility Registration Update procedure for non-3GPP access path switching. If the UE is registered to different PLMNs over 3GPP and non-3GPP accesses, the UE shall use the capability received over non-3GPP access to determine whether to perform the Mobility Registration Update procedure for non-3GPP path switching and whether to include ("Non-3GPP access path switching while using old AN resources") indication. + +NOTE 8: If the AMF receives ("Non-3GPP path switching while using old AN resources") indication from Mobility Registration Update procedure, and the serving SMF(s) for PDU Session(s) is not supporting non-3GPP access path switching, the non-3GPP access path switching can still be performed with the AMF triggering for each PDU Session the release of the old user plane resources before new user plane resources are established. + +An ATSSS-capable UE may decide to request a MA PDU Session based on the provisioned URSP rules. In particular, the UE should request a MA PDU Session when the UE applies a URSP rule, which triggers the UE to establish a new PDU Session and the Access Type Preference component of the URSP rule indicates "Multi-Access" (see TS 23.503 [45]). + +### 5.32.3 Policy for ATSSS Control + +If dynamic PCC is to be used for the MA PDU Session, the PCF may take ATSSS policy decisions and create PCC rules that contain MA PDU Session Control information, (as specified in TS 23.503 [45]), which determines how the uplink and the downlink traffic of the MA PDU Session should be distributed across the 3GPP and non-3GPP accesses. If dynamic PCC is not deployed, local policy in SMF is used. + +The SMF receives the PCC rules with MA PDU Session Control information and maps these rules into (a) ATSSS rules, which are sent to the UE, and (b) N4 rules, which are sent to the UPF. The ATSSS rules are provided as a prioritized list of rules (see clause 5.32.8), which are applied by the UE to enforce the ATSSS policy in the uplink direction and the N4 Rules are applied by the UPF to enforce the ATSSS policy in the downlink direction. + +The ATSSS rules are sent to UE with a NAS message when the MA PDU Session is created or updated by the SMF, e.g. after receiving updated/new PCC rules from the PCF. Similarly, the N4 rules are sent to UPF when the MA PDU Session is created or updated by the SMF. + +The details of the policy control related to ATSSS are specified in TS 23.503 [45]. + +### 5.32.4 QoS Support + +The 5G QoS model for the Single-Access PDU Session is also applied to the MA PDU Session, i.e. the QoS Flow is the finest granularity of QoS differentiation in the MA PDU Session. One difference compared to the Single-Access PDU Session is that in a MA PDU Session there can be separate user-plane tunnels between the AN and the PSA, each one associated with a different access. However, the QoS Flow is not associated with specific access, i.e. it is access agnostic, so the same QoS is supported when the traffic is distributed over 3GPP and non-3GPP accesses. The SMF shall provide the same QFI in 3GPP and non-3GPP accesses so that the same QoS is supported in both accesses. + +A QoS Flow of the MA PDU Session may be either Non-GBR or GBR depending on its QoS profile. + +For a Non-GBR QoS Flow, the SMF provides a QoS profile to both 5G-ANs during MA PDU Session Establishment or MA PDU Session Modification procedure: + +- During MA PDU Session Establishment procedure, the QoS profile to both ANs if the UE is registered over both accesses. +- During MA PDU Session Modification procedure, the QoS profile is provided to the 5G-AN(s) over which the user plane resources are activated. + +For a GBR QoS Flow, the SMF shall provide a QoS profile to 5G-AN(s) as follows: + +- If the PCC rule allows a GBR QoS Flow in a single access, the SMF provides the QoS profile for the GBR QoS Flow to the access network allowed by the PCC rule. +- If the PCC rule allows a GBR QoS Flow in both accesses and the Steering Mode is different from Redundant, the SMF decides to which access network to provide the QoS profile for the GBR QoS Flow based on its local policy (e.g. the access where the traffic is ongoing according to the Multi Access Routing rule). +- If the PCC rule allows a GBR QoS Flow in both accesses and the Steering Mode is Redundant, the SMF provides the QoS profile for the GBR QoS Flow to both access networks. Whenever the SMF recognizes that resources are not allocated in one access network, the SMF shall notify the PCF about the resource allocation failure and indicate the respective Access Type. Whenever the SMF recognizes that resources are not allocated in both access networks, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. + +NOTE 1: The SMF knows about the allocation of resources in an access network from the interaction with the access network during GBR QoS Flow establishment/modification as well as during the release of resources by the access network. + +For a GBR QoS Flow, traffic splitting is not supported. If the UPF determines that it cannot send GBR traffic over the current ongoing access e.g. based on the N4 rules and access availability and unavailability report from the UE as described in clause 5.32.5.3, the UPF shall send an Access Availability report to the SMF. + +Based on the Access Availability report and if the Steering Mode is different from Redundant, the SMF decides whether to move GBR QoS Flows to the other access when one access is not available: + +- if the PCC rule allows the GBR QoS Flows only on this access, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. +- if the corresponding PCC rule allows the GBR QoS Flow on both accesses and the other access is not available, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. +- if the PCC rule allows the GBR QoS Flow on both accesses and the other access is available, the SMF shall try to move the GBR QoS Flow to the other access. The SMF may trigger a PDU session modification procedure to provide the QoS profile to the other access and release the resources for the GBR QoS Flow in the current access. +- if Notification Control parameter is not included in the PCC rule for the GBR QoS Flow and the other access does not accept the QoS profile, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. +- if the Notification Control parameter is included in the PCC rule, the SMF shall notify the PCF that GBR can no longer be guaranteed. After the other access accepts the QoS profile, the SMF shall notify the PCF + +that GFBR can again be guaranteed. If the other access does not accept the QoS profile, the SMF shall delete the GBR QoS Flow and report to the PCF about the removal of the PCC rule. + +NOTE 2: The ATSSS rule for GBR QoS Flow only allows the UE to steer traffic over a single access so that the network knows in which access the UE sends GBR traffic. If the network wants to move GBR QoS Flow to the other access, the network needs to update ATSSS rule of the UE. + +Based on the Access Availability report and if the Steering Mode is Redundant, the SMF behaves as follows: + +- if both accesses are not available, the SMF shall release the resources for the GBR QoS Flow and report to the PCF about the removal of the PCC rule. + +NOTE 3: The UPF can detect that both accesses are not available based on implementation specific means. + +- when one of the accesses becomes unavailable while the other access is still available, the SMF shall neither release the resources for the GBR QoS Flow nor notify the PCF that GFBR can no longer be guaranteed (if the Notification Control parameter is included in the PCC rule). + +NOTE 4: The access network will typically release the resources for a GBR QoS Flow if there is no traffic transferred for a certain amount of time and this will then trigger the SMF notification to PCF described above. + +When the MA PDU Session is established or when the MA PDU Session is modified, the SMF may provide QoS rule(s) to the UE via one access, which are applied by the UE as specified in clause 5.7.1.4. The QoS rule(s) provided by SMF via one access are commonly used for both 3GPP access and non-3GPP access, so the QoS classification is independent of ATSSS rules. + +The derived QoS rule generated by Reflective QoS is applied independently of the access on which the RQI was received. When the MPTCP functionality and/or the MPQUIC functionality is used in the UE, the UE shall use the IP address/prefix of the MA PDU Session and the final destination address to generate the derived QoS rule. + +When the MPTCP functionality and/or MPQUIC functionality is enabled for the MA PDU Session: + +- any QoS rules or PDRs that apply to the MA PDU Session IP address/prefix and port also apply (a) to the MPTCP "link-specific multipath" addresses/prefixes and ports used by the UE to establish MPTCP subflows over 3GPP and non-3GPP accesses , and (b) to the "MPQUIC link-specific multipath" addresses and ports used by the UE to transmit UDP flows over 3GPP and non-3GPP accesses; and +- any QoS rules or PDRs that apply to the IP address/prefix and port of the final destination server in DN also apply (a) to the IP address and port of the MPTCP proxy for corresponding MPTCP subflows that are terminated at the proxy and (b) to the IP address and port of the MPQUIC proxy for corresponding UDP flows that are terminated at the proxy. + +NOTE 5: How these associations are made is left up to the UE and UPF implementations. + +### 5.32.5 Access Network Performance Measurements + +#### 5.32.5.1 General principles + +When an MA PDU Session is established, the network may provide the UE with Measurement Assistance Information. This information assists the UE in determining which measurements shall be performed over both accesses, as well as whether measurement reports need to be sent to the network. + +Measurement Assistance Information shall include the addressing information of a Performance Measurement Function (PMF) in the UPF, the UE can send PMF protocol messages to: + +- For a PDU Session of IP type, Measurement Assistance Information contains one IP address for the PMF, one UDP port associated with 3GPP access and another UDP port associated with non-3GPP access. PMF messages sent by UE to one of these UDP ports, shall be transmitted to UPF via the QoS Flow associated with the default QoS rule. +- For a PDU Session of Ethernet type, Measurement Assistance Information contains one MAC address associated with 3GPP access and another MAC address associated with non-3GPP access. PMF messages sent by UE to one of these MAC addresses, shall be transmitted to UPF via the QoS Flow associated with the default QoS rule. + +NOTE 1: To protect the PMF in the UPF (e.g. to block DDOS to the PMF), the IP addresses of the PMF are only accessible from the UE IP address via the N3/N9 interface. + +NOTE 2: After the MA PDU Session is released, the same UE IP address/prefix is not allocated to another UE for MA PDU Session in a short time. + +If the SMF determines that access performance measurements per QoS Flow shall be applied for the MA PDU Session, then the Measurement Assistance Information shall also include a list of QoS Flows on which access performance measurements may be performed. For each QoS Flow in this list, the following information is included: + +- The QFI of the associated QoS Flow. +- For a PDU Session of IP type, one UDP port associated with 3GPP access and another UDP port associated with non-3GPP access. PMF messages sent by UE to one of these UDP ports, shall be transmitted to UPF via the associated QoS Flow. +- For a PDU Session of Ethernet type, one MAC address associated with 3GPP access and another MAC address associated with non-3GPP access. PMF messages sent by UE to one of these MAC addresses, shall be transmitted to UPF via the associated QoS Flow. + +The QoS rules and the N4 rules provided by SMF to UE and to UPF respectively shall include information (e.g. packet filters containing the UDP port or the MAC address associated with a QoS Flow), which enables the UE and UPF to route a PMF message to a specific QoS Flow. + +The UE and the UPF may need to perform access performance measurements in order to estimate the Round-Trip Time (RTT) and/or the Packet Loss Rate (PLR) that an SDF is expected to experience when transmitted on a certain access type. Based on these measurements and the provisioned ATSSS rules in the UE and MAR rules in the UPF, the UE and the UPF decide how to distribute the traffic of an SDF across the two accesses. + +If the UE and the UPF decide to initiate access performance measurements to estimate the RTT and/or the PLR for an SDF, the access performance measurements shall be performed either + +- (a) using the QoS Flow associated with the default QoS rule; or +- (b) using the target QoS Flow, which is the QoS Flow that the SDF traffic is transmitted on. + +When the access performance measurements are using the target QoS Flow, it is termed that "access performance measurements per QoS Flow" are applied for the MA PDU Session. + +The UE shall indicate in its ATSSS capabilities that it supports access performance measurements per QoS Flow. Based on this UE capability and other information (such as local policy), the SMF determines whether access performance measurements per QoS Flow shall be applied for the MA PDU Session or not. If the SMF determines that access performance measurements per QoS Flow shall be applied for the MA PDU Session, then: + +- The SMF determines a list of QoS Flows over which access performance measurements may be performed and provides this list to the UE (within the Measurement Assistance Information) and to the UPF. +- The UE and the UPF may initiate access performance measurements on one or more of the QoS Flows included in this list. The UE and the UPF shall be able to receive and respond to PMF messages sent on any QoS Flow included in this list. +- The SMF may update the list of QoS Flows over which access performance measurements may be performed during the lifetime of a MA PDU Session, e.g. when a new PCC rule that could benefit from PMF access performance measurements is bound to a QoS Flow. + +NOTE 3: The SMF can e.g. add a QoS Flow into the list when at least one PCC Rule is bound to that QoS Flow that is using one of the Steering Modes where performance measurements via PMF are applicable, such as Lowest Delay Steering Mode or a Steering Mode where threshold values have been provided. + +The UE shall perform access performance measurements per QoS Flow only when this is explicitly indicated in the Measurement Assistance Information, i.e. only when the UE receives the list of QoS Flows over which access performance measurements may be performed. Otherwise, the UE shall perform access performance measurements based on the QoS Flow associated with the default QoS rule. The UPF shall perform access performance measurements per QoS Flow only when this is explicitly indicated by SMF, i.e. only when the UPF receives the list of QoS Flows over which access performance measurements may be performed. Otherwise, the UPF shall perform access performance + +measurements based on the QoS Flow associated with the default QoS rule. In this case the UPF learns what QoS Flow to use as described in TS 29.244 [65]. + +The UE and the UPF may decide not to initiate access performance measurements using PMF over a certain target QoS Flow, when they already have access performance measurements for another target QoS Flow which they determine can be reused. + +NOTE 4: How the UE and UPF determine that the performance measurements using a certain target QoS Flow apply to another target QoS Flow is based on implementation, e.g. AN resource to QoS Flow mapping in the UE or getting similar access measurements results with other QoS Flow. + +When access performance measurements for an SDF are performed based on the target QoS Flow, the UE needs to be able to determine the QoS Flow a downlink packet arrives on. In order to enable this, the SMF shall include downlink Packet Filter information in the QoS rule provided to UE matching this SDF, unless Reflective QoS is used for the SDF. + +NOTE 5: For example, if a QoS Flow requires to activate Reflective QoS, the SMF does not need to provide downlink QoS Flow information for the QoS Flow to minimize usage of packet filters. When a data packet is received over a QoS Flow, the UE can decide whether to check the downlink QoS Flow information based on the existence of SDAP header for the QoS Flow. + +The addressing information of the PMF in the UPF is retrieved by the SMF from the UPF during N4 session establishment. If the UPF receives from the SMF, during N4 session establishment or modification procedure, a list of QoS Flows over which access performance measurements may be performed, the UPF allocates different UDP ports per QoS Flow per access for IP PDU sessions, or allocates different MAC addresses per QoS Flow per access for Ethernet PDU sessions. For IP PDU sessions, the UPF sends the PMF IP addressing information and the UDP ports with the QFI of the associated QoS Flow to the SMF. For Ethernet PDU sessions, the UPF sends the MAC addresses with the QFI of the associated QoS Flow to the SMF. + +The following PMF protocol messages can be exchanged between the UE and the UPF: + +- Messages to allow for Round Trip Time (RTT) measurements, i.e. when the "Smallest Delay" steering mode is used or when either "Priority-based", "Load-Balancing" or "Redundant" steering mode is used with RTT threshold value being applied; +- Messages to allow for Packet Loss Rate (PLR) measurements, i.e. when steering mode is used either "Priority-based", "Load-Balancing" or "Redundant" steering mode is used with PLR threshold value being applied; +- Messages for reporting Access availability/unavailability by the UE to the UPF. +- Messages for sending UE-assistance data to UPF. Such messages may be sent from the UE to UPF only when the UE receives the UE-assistance indicator in an ATSSS rule, as specified in clause 5.32.8. Further details are provided in clause 5.32.5.5. +- Messages for sending Suspend Traffic Duplication and Resume Traffic Duplication from UPF to UE to suspend or resume traffic duplication as defined in clause 5.32.5.6. + +Since steering modes can be different in up-link and down-link, the UE needs to be able to handle PMF protocol messages for RTT and PLR measurements received from UPF even if it is not using one of the steering modes associated with the RTT and PLR measurements (and vice versa). + +The PMF protocol is specified in TS 24.193 [109]. + +The PMF protocol messages used for access availability/unavailability reports shall be sent on the QoS Flow associated with the default QoS rule. The PMF protocol messages used for access performance measurements shall be sent either on the QoS Flow associated with the default QoS rule, or on the target QoS Flow, as specified above. + +The QoS Flow associated with the default QoS rule for MA PDU Session is Non-GBR QoS Flow. + +The UE shall not apply the ATSSS rules and the UPF shall not apply the MAR rules for the PMF protocol messages. + +When the UE requests a MA PDU session and indicates it is capable to support: + +- the MPTCP functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or + +- the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or +- the MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); + +the network may send Measurement Assistance Information for the UE to send Access availability/unavailability reports to the UPF. In this case, the UE and UPF shall not perform RTT and PLR measurements using PMF as the UE and UPF can use measurements available at the MPTCP layer and/or at the MPQUIC layer. + +##### 5.32.5.1a Address of PMF messages + +As described in clause 5.32.5.2, 5.32.5.2a and 5.32.5.3, a UE and UPF may exchange PMF messages to measure access performance and report access availability/unavailability. When the UE and UPF exchanges PMF message, source and destination address of the PMF messages shall be assigned as follows: + +###### 1. In the case of a MA PDU Session of IP type: + +- If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the PMF in the UE sends PMF messages to the PMF in the UPF over UDP/IP. The destination IP address is the IP address contained in the Measurement Assistance Information and the destination UDP port is one of the two UDP ports contained in the Measurement Assistance Information. One UDP port is used for sending PMF messages to UPF over 3GPP access and the other UDP port is used for sending PMF messages to UPF over non-3GPP access. The source IP address is the IP address assigned to UE for the MA PDU Session and the source UDP port is a UDP port that is dynamically allocated by the UE for PMF communication. This source UDP port in the UE remains the same for the entire lifetime of the MA PDU Session. + +If access performance measurements per QoS Flow is performed, the Measurement Assistance Information contains UDP ports, one for each QoS Flow and access combination. When the UE sends PMF message over a QoS Flow of an access, the UE shall set the destination UDP port as the UDP port for the QoS Flow and the access in Measurement Assistance information. + +- If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the PMF in the UPF sends PMF messages to the PMF in the UE over UDP/IP. The source IP address is the same IP address as the one provided in the Measurement Assistance Information and the source UDP port is one of the two UDP ports as provided in the Measurement Assistance Information. One UDP port is used for sending PMF messages to UE over 3GPP access and the other UDP port is used for sending PMF messages to UE over the non-3GPP access. The destination IPv4 address is the IPv4 address assigned to UE for the MA PDU Session (if any) and the destination IPv6 address is an IPv6 address selected by the UE from the IPv6 prefix assigned for the MA PDU Session (if any). The destination UDP port is the dynamically allocated UDP port in the UE, which is contained in all PMF messages received from the UE. + +If access performance measurements per QoS Flow is performed, when the UPF sends PMF message over a QoS Flow of an access, the UPF shall set the source UDP port with the UDP port for the QoS Flow and the access as the one for the QoS Flow and the access provided in Measurement Assistance information. + +- If the UE receives Measurement Assistance Information, the UE shall inform the network via the user plane about the UE's dynamically allocated UDP port, and the IPv6 address if IPv6 is used for PMF messages, so that it is possible for the UPF to know the UE's IPv6 address (if applicable) and dynamically allocated UDP port as soon as the MA PDU Session has been established. + +NOTE 1: Regardless of whether access performance measurements per QoS Flow is applied or not, the UE only allocates a single UDP port for PMF messages. + +###### 2. In the case of a MA PDU Session of Ethernet type: + +- The PMF in the UE sends PMF messages to the PMF in the UPF over Ethernet. The Ethertype is the Ethertype contained in the Measurement Assistance Information. If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the destination MAC address is one of the two MAC addresses contained in the Measurement Assistance Information. One MAC address is used for sending PMF messages to UPF over 3GPP access and the other MAC address is used for sending PMF messages to UPF over non-3GPP access. The source MAC address is a MAC address of the UE, which remains the same for the entire lifetime of the MA PDU Session. + +If access performance measurements per QoS Flow is performed, Measurement Assistance Information contains MAC addresses for each QoS Flow and each access. When the UE sends PMF message over a QoS Flow of an access, the UE shall set the destination MAC address as the MAC address for the QoS Flow and the access in Measurement Assistance information. + +- The PMF in the UPF sends PMF messages to the PMF in the UE over Ethernet. The Ethertype is the same Ethertype as the one provided in the Measurement Assistance Information. If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the source MAC address is one of the two MAC addresses as provided in the Measurement Assistance Information. One MAC address is used for sending PMF messages to UE over 3GPP access and the other MAC address is used for sending PMF messages to UE over non-3GPP access. The destination MAC address is the MAC address of the UE, which is contained in all PMF messages received from the UE. + +If access performance measurements per QoS Flow is performed, when the UPF sends PMF message over a QoS Flow of an access, the UPF shall set the source MAC address with the MAC address for the QoS Flow and the access as the one for the QoS Flow and the access provided in Measurement Assistance information. + +- If the UE receives Measurement Assistance Information, the UE shall inform the network via the user plane about the UE's MAC address so that it is possible for the UPF to know the UE's MAC address as soon as the MA PDU Session has been established. + +NOTE 2: Regardless of whether access performance measurements per QoS Flow is applied or not, the UE only use a single MAC address. + +#### 5.32.5.2 Round Trip Time Measurements + +RTT measurements can be conducted by the UE and UPF independently. There is no measurement reporting from one side to the other. RTT measurements are defined to support the "Smallest Delay", "Priority-based", "Load Balancing" or "Redundant" steering mode (i.e. when RTT threshold value is applied). + +The estimation of the RTT by the UE and by the UPF is based on the following mechanism: + +1. The PMF in the UE sends over the user plane PMF-Echo Request messages to the PMF in the UPF, and the PMF in the UPF responds to each one with a PMF-Echo Response message. Similarly, the PMF in the UPF sends over the user plane PMF-Echo Request messages to the PMF in the UE, and the PMF in the UE responds to each one with a PMF-Echo Response message. +2. When the UP connection of the MA PDU session is deactivated on an access, no PMF-Echo Request messages are sent on this access. The PMF in the UPF shall not send PMF-Echo Request on this access if the UP connection is not available or after it receives notification from the (H-)SMF to stop sending the PMF-Echo Request on this access. +3. The UE and the UPF derive an estimation of the average RTT over an access type and QoS Flow by averaging the RTT measurements obtained over this access type and QoS Flow. + +##### 5.32.5.2a Packet Loss Rate Measurements + +The UE and the UPF may decide to estimate the Packet Loss Rate (PLR) for an SDF over both accesses. For example, the UE may take this decision when an ATSSS rule in the UE requires the traffic of an SDF to be steered in accordance with a PLR-based threshold condition (e.g. $PLR < 2\%$ ). + +The UE and the UPF calculate the PLR for an SDF by exchanging PMF-PLR Report messages, as specified below. A PMF-PLR Report message is sent over 3GPP access or over non-3GPP access, using either the QoS Flow associated with the default QoS rule or a "target" QoS Flow, as specified in clause 5.32.5.1. + +The calculation of the PLR by the UE and by the UPF is based on the following mechanism. It is assumed that the PLR should be calculated for a target QoS Flow, however, the same mechanism applies when the PLR should be calculated for the QoS Flow associated with the default QoS rule. + +- The UE requests from UPF to start counting the number of received UL packets by sending a PMF-PLR Count Request message over the target QoS Flow. The UPF starts counting of the received UL packets over the target QoS Flow and over the access network which the PMF-PLR Count Request message was received from. The UE + +starts counting the transmitted UL packets over the target QoS Flow and access network when it sends a PMF-PLR Count Request message to UPF. + +- The UE stops the counting and requests from UPF to report the number of counted UL packets by sending a PMF-PLR Report Request message over the target QoS Flow. The UPF stops the counting and sends a PMF-PLR Report Response message over the QoS Flow including the number of UL packets counted since it received the last PMF-PLR Count Request message. + +NOTE 1: A PMF-PLR Report Request message can also indicate to UPF to start counting packets if the UE wants to measure the Packet Loss Rate again. + +- The UE calculates the UL packet loss ratio based on the local counting result of the number of transmitted UL packets and reported number of received UL packets in the UPF. +- The UPF applies the same procedure for calculating the DL PLR, i.e. it sends to UE a PMF-PLR Count Request message on a target QoS Flow to request from UE to start counting the number of DL packets received on this target QoS Flow. As defined in clause 5.32.5.1, the UE determines which DL packets are received on the target QoS Flow by checking the QFI included in the header of DL packets (e.g. in the SDAP header). If no QFI is included in the header of a DL packet, the UE determines the QFI for this DL packet by applying the Packet Filters for downlink in the QoS Rules received from SMF. +- When the UP connection of the MA PDU session is deactivated on an access, no PMF-PLR messages are sent on this access. The PMF in the UPF shall not send PMF-PLR message on this access if the UP connection is not available or after it receives notification from the (H-)SMF to stop sending the PMF-PLR message on this access. +- The UE and the UPF derive an estimation of the average PLR per QoS Flow over an access type by averaging the PLR measurements obtained over this access. + +NOTE 2: The details of the packet loss measurements, including error cases and mechanisms for improving the measurement accuracy, are considered in the Stage 3 specifications. + +#### 5.32.5.3 Access Availability/Unavailability Report + +If required by the network in the Measurement Assistance Information, the UE shall provide access availability/unavailability reports to the network. How the UE detects the unavailability and the availability of an access is based on implementation. The CM state of a UE is not a factor when determining whether the 3GPP access is available. When the UE detects the unavailability/availability of an access, it shall: + +- build a PMF-Access Report containing the access type and an indication of availability/unavailability of this access; +- send the PMF-Access Report to the UPF via the user plane. + +The UPF shall acknowledge the PMF-Access Report received from the UE. + +#### 5.32.5.4 Protocol stack for user plane measurements and measurement reports + +![Figure 5.32.5.4-1: UE/UPF measurements related protocol stack for 3GPP access and for an MA PDU Session with type IP. The diagram shows the protocol stack across UE, RAN, UPF, and UPF (PSA) connected via N3 and N9 interfaces. The stack includes PMF protocol, UDP, IP, 5G-AN protocol layers, GTP-u, UDP/IP, L2, and L1.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +The diagram illustrates the protocol stack for user plane measurements and measurement reports over 3GPP access. It shows the following components and layers: + +- UE (User Equipment):** PMF protocol, UDP, IP, 5G-AN protocol layers. +- RAN (Radio Access Network):** 5G-AN protocol layers, GTP-u, UDP/IP, L2, L1. +- N3 Interface:** Connects RAN and UPF. +- UPF (PDN Gateway):** GTP-u, UDP/IP, L2, L1. +- N9 Interface:** Connects UPF and UPF (PSA). +- UPF (PSA):** PMF protocol, UDP, IP, GTP-u, UDP/IP, L2, L1. + +Figure 5.32.5.4-1: UE/UPF measurements related protocol stack for 3GPP access and for an MA PDU Session with type IP. The diagram shows the protocol stack across UE, RAN, UPF, and UPF (PSA) connected via N3 and N9 interfaces. The stack includes PMF protocol, UDP, IP, 5G-AN protocol layers, GTP-u, UDP/IP, L2, and L1. + +**Figure 5.32.5.4-1: UE/UPF measurements related protocol stack for 3GPP access and for an MA PDU Session with type IP** + +In the case of an MA PDU Session with type Ethernet, the protocol stack over 3GPP access is that same as the one in the above figure, but the PMF protocol operates on top of Ethernet, instead of UDP/IP. + +![Figure 5.32.5.4-2: UE/UPF measurements related protocol stack for Untrusted non-3GPP access and for an MA PDU Session with type IP. The diagram shows the protocol stack across UE, Untrusted N3GPP Access Network, N3IWF, UPF, and UPF (PSA) connected via Nwu, N3, and N9 interfaces. The stack includes PMF protocol, UDP, IP, GRE, Inner IP, IPsec, IP, Non-3GPP, IP, Lower Layers, N3 stack, and N9 stack.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +The diagram illustrates the protocol stack for user plane measurements and measurement reports over Untrusted non-3GPP access. It shows the following components and layers: + +- UE (User Equipment):** PMF protocol, UDP, IP, GRE, Inner IP, IPsec, IP, Non-3GPP. +- Untrusted N3GPP Access Network:** IP, Non-3GPP, Lower Layers. +- Nwu Interface:** Connects UE and N3IWF. +- N3IWF (N3 Interface Function):** GRE, Inner IP, IPsec, IP, Lower Layers, N3 stack. +- N3 Interface:** Connects N3IWF and UPF. +- UPF (PDN Gateway):** N3 stack, N9 stack. +- N9 Interface:** Connects UPF and UPF (PSA). +- UPF (PSA):** PMF protocol, UDP, IP, N9 stack. + +Figure 5.32.5.4-2: UE/UPF measurements related protocol stack for Untrusted non-3GPP access and for an MA PDU Session with type IP. The diagram shows the protocol stack across UE, Untrusted N3GPP Access Network, N3IWF, UPF, and UPF (PSA) connected via Nwu, N3, and N9 interfaces. The stack includes PMF protocol, UDP, IP, GRE, Inner IP, IPsec, IP, Non-3GPP, IP, Lower Layers, N3 stack, and N9 stack. + +**Figure 5.32.5.4-2: UE/UPF measurements related protocol stack for Untrusted non-3GPP access and for an MA PDU Session with type IP** + +In the case of an MA PDU Session with type Ethernet, the protocol stack over Untrusted non-3GPP access is the same as the one in the above figure, but the PMF protocol operates on top of Ethernet, instead of UDP/IP. + +![Figure 5.32.5.4-3: UE/UPF measurements related protocol stack for Trusted non-3GPP access and for an MA PDU Session with type IP. The diagram shows the protocol stack across UE, TNAP, N3IWF, UPF, and UPF (PSA) connected via NWt, N3, and N9 interfaces. The stack includes PMF protocol, UDP, IP, GRE, Inner IP, IPsec, IP, Non-3GPP, IP, Lower Layers, N3 stack, and N9 stack.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) + +The diagram illustrates the protocol stack for user plane measurements and measurement reports over Trusted non-3GPP access. It shows the following components and layers: + +- UE (User Equipment):** PMF protocol, UDP, IP, GRE, Inner IP, IPsec, IP, Non-3GPP. +- TNAP (Trusted N3GPP Access Network):** IP, Non-3GPP, Lower Layers. +- NWt Interface:** Connects UE and N3IWF. +- N3IWF (N3 Interface Function):** GRE, Inner IP, IPsec, IP, Lower Layers, N3 stack. +- N3 Interface:** Connects N3IWF and UPF. +- UPF (PDN Gateway):** N3 stack, N9 stack. +- N9 Interface:** Connects UPF and UPF (PSA). +- UPF (PSA):** PMF protocol, UDP, IP, N9 stack. + +Figure 5.32.5.4-3: UE/UPF measurements related protocol stack for Trusted non-3GPP access and for an MA PDU Session with type IP. The diagram shows the protocol stack across UE, TNAP, N3IWF, UPF, and UPF (PSA) connected via NWt, N3, and N9 interfaces. The stack includes PMF protocol, UDP, IP, GRE, Inner IP, IPsec, IP, Non-3GPP, IP, Lower Layers, N3 stack, and N9 stack. + +**Figure 5.32.5.4-3: UE/UPF measurements related protocol stack for Trusted non-3GPP access and for an MA PDU Session with type IP** + +In the case of an MA PDU Session with type Ethernet, the protocol stack over Trusted non-3GPP access is the same as the one in the above figure, but the PMF protocol operates on top of Ethernet, instead of UDP/IP. + +#### 5.32.5.5 UE Assistance Operation + +When UE-assistance operation is authorized by the PCF in the PCC Rule, the SMF provides an indication for UE-assistance in the ATSSS Rule to the UE, as described in clause 5.32.8, and in the MAR to the UPF, as described in clause 5.8.5.8. + +If the UE receives the UE-assistance indicator in an ATSSS rule (as specified in clause 5.32.8) and the UE decides to apply a different UL traffic distribution for an SDF than the default UL traffic distribution indicated in the Steering Mode component of the ATSSS rule (e.g. because the UE is running out of battery), then the following applies: + +- The UE may apply any split percentages for the UL traffic distribution of an SDF, based on implementation specific criteria. +- The UE may send a PMF-UAD (UE Assistance Data) message to UPF that contains the split percentages that may be used by UPF for all DL traffic that the UE-assistance operation applies. The UPF acknowledges the reception of the PMF-UAD message by sending a PMF-UAD complete message to the UE. + +NOTE: If the UE has multiple ATSSS rules that allow UE-assistance operation, and the UE decides to use different UL split percentages for their respective SDFs, then the split percentages included in the PMF-UAD message are selected by the UE based on implementation specific criteria. + +- The UPF may apply the information in a received PMF-UAD message to align the DL traffic distribution for traffic that is allowed to use UE-assistance operation, i.e. traffic where the MAR contains a Steering Mode Indicator set to UE-assistance operation. +- If the UE decides to terminate the UE assistance operation, the UE may send a PMF-UAT (UE Assistance Termination) message to the UPF indicating that the UE assistance operation is terminated and the UE performs the UL traffic distribution according to the split percentages in the ATSSS rule received from the network. If the UPF receives the PMF-UAT message, the UPF acknowledges the reception by sending a PMF-UAT complete message and performs DL traffic distribution by applying the split percentages included in the MAR. + +#### 5.32.5.6 Suspend and Resume Traffic Duplication + +As part of the Redundant Steering Mode, a UPF can decide to suspend traffic duplication for a UE by sending PMF-Suspend Duplication Request message to the UE. How the UPF determines to suspend traffic duplication is implementation specific. + +NOTE 1: The Suspension of traffic duplication can be caused by e.g. the locally detected UPF congestion. In that way the UPF can stop receiving duplicated traffic via 3GPP and non-3GPP access network simultaneously. + +The UPF may indicate in the PMF-Suspend Duplication Request message the type of traffic (i.e. GBR or non-GBR) for which traffic duplication is being suspended. The PMF-Suspend Duplication Request message is sent over the user plane of any available access network of the MA PDU Session. Once the UE receives the PMF-Suspend Duplication Request message from the UPF, the UE shall stop duplicating the type of traffic for which traffic duplication is suspended. + +If the UPF does not provide the type of traffic (GBR or non-GBR) in the PMF-Suspend Duplication Request message, traffic duplication is suspended for all traffic for which traffic duplication is being performed. Once UPF suspended traffic duplication and if no Primary Access is configured, both the UE and the UPF decide, based on their own implementation, which access network to use for sending UL and DL traffic. If the Primary Access is configured, both the UE and the UPF use the Primary Access for sending UL and DL traffic. + +The UPF may decide to resume traffic duplication for a UE by sending the PMF-Resume Duplication Request message. How the UPF determines to resume traffic duplication is implementation specific. + +NOTE 2: Traffic duplication can be resumed e.g. when the UPF has detected that local congestion has diminished. + +Once the UE receives the PMF-Resume Duplication Request message from the UPF, the UE may restart to duplicate the type of traffic for which traffic duplication is resumed based on the provided Redundant steering mode policies and UE implementation. + +### 5.32.6 Support of Steering Functionalities + +#### 5.32.6.1 General + +The functionality in an ATSSS-capable UE that can steer, switch and split the MA PDU Session traffic across 3GPP access and non-3GPP access, is called a "steering functionality". An ATSSS-capable UE may support one or more of the following types of steering functionalities: + +- High-layer steering functionalities, which operate above the IP layer: + - In this release of the specification, two high-layer steering functionalities are specified: + - The first applies the MPTCP protocol (IETF RFC 8684 [81]) and is called "MPTCP functionality" (see clause 5.32.6.2.1). This steering functionality can be applied to steer, switch and split the TCP traffic flows identified in the ATSSS/N4 rules. The MPTCP functionality in the UE may communicate with an associated MPTCP Proxy functionality in the UPF, by using the MPTCP protocol over the 3GPP and/or the non-3GPP user plane. + - The second applies the QUIC protocol (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]) and its multipath extensions (draft-ietf-quic-multipath [174]), and it is called "MPQUIC functionality" (see clause 5.32.6.2.2). This steering functionality can be applied to steer, switch and split the UDP traffic flows identified in the ATSSS/N4 rules. The MPQUIC functionality in the UE may communicate with an associated MPQUIC Proxy functionality in the UPF, by using the QUIC protocol and its multipath extensions over the 3GPP and/or the non-3GPP user plane. +- Low-layer steering functionalities, which operate below the IP layer: + - One type of low-layer steering functionality defined in the present document is called "ATSSS Low-Layer functionality", or ATSSS-LL functionality (see clause 5.32.6.3.1). This steering functionality can be applied to steer, switch and split all types of traffic, including TCP traffic, UDP traffic, Ethernet traffic, etc. ATSSS-LL functionality is mandatory for MA PDU Session of type Ethernet. In the network, there shall be in the data path of the MA PDU session one UPF supporting ATSSS-LL. + +NOTE: Filters used in ATSSS rules related with a MA PDU Session of type Ethernet can refer to IP level parameters such as IP addresses and TCP/UDP ports. + +The UE indicates to the network its supported steering functionalities and steering modes by including in the UE ATSSS Capability one of the following: + +##### 1) ATSSS-LL functionality with any steering mode. + +In this case, the UE indicates that it is capable to steer, switch and split all traffic of the MA PDU Session by using the ATSSS-LL functionality with any steering mode allowed for ATSSS-LL, as specified in clause 5.32.8. + +##### 2) MPTCP functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode. + +In this case, the UE indicates that: + +- a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; and +- b) it is capable to steer and switch all other traffic (i.e. the non-MPTCP traffic) of the MA PDU Session by using the ATSSS-LL functionality with the Active-Standby steering mode specified in clause 5.32.8. + +##### 3) MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode. + +In this case, the UE indicates that: + +- a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; and +- b) it is capable to steer, switch and split all other traffic (i.e. the non-MPTCP traffic) of the MA PDU Session by using the ATSSS-LL functionality with any steering mode, as specified in clause 5.32.8. + +- 4) MPQUIC functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode. + +In this case, the UE indicates that: + +- a) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and +- b) it is capable to steer and switch all other traffic (i.e. the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with the Active-Standby steering mode specified in clause 5.32.8. + +- 5) MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode. + +In this case, the UE indicates that: + +- a) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and +- b) it is capable to steer, switch and split all other traffic (i.e. the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with any steering mode that can be used with ATSSS-LL, as specified in clause 5.32.8. + +- 6) MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode, and ATSSS-LL functionality with only Active-Standby steering mode. + +In this case, the UE indicates that: + +- a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; +- b) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and +- c) it is capable to steer and switch all other traffic (i.e. the non-MPTCP traffic and the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with the Active-Standby steering mode specified in clause 5.32.8. + +- 7) MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode, and ATSSS-LL functionality with any steering mode. + +In this case, the UE indicates that: + +- a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; +- b) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and +- c) it is capable to steer, switch and split all other traffic (i.e. the non-MPTCP traffic and the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with any steering mode that can be used with ATSSS-LL, as specified in clause 5.32.8. + +The above steering functionalities are schematically illustrated in the Figure 5.32.6.1-1, which shows an example model for an ATSSS-capable UE supporting the MPTCP functionality, the MPQUIC functionality and the ATSSS-LL functionality. The MPTCP flows and the MPQUIC flows in this figure represent the traffic of the applications for which MPTCP can be applied and for which MPQUIC can be applied respectively. The five different IP addresses illustrated in the UE are further described in clause 5.32.6.2.1 and in clause 5.32.6.2.2. When the MPTCP functionality and the MPQUIC functionality are both applied, the addresses (IP@1, IP@2) used for MPTCP may be the same as the addresses (IP@4, IP@5) used for MPQUIC. The "Low-Layer" in this figure contains functionality that operates below the IP layer (e.g. different network interfaces in the UE), while the "High-Layer" contains functionality that operates above the IP layer. + +![Diagram illustrating steering functionalities in an example UE model. The diagram shows traffic flows from applications being steered through various functionalities (MPTCP, MPQUIC, ATSSS-LL) and then distributed across Non-3GPP and 3GPP access paths. A central 'ATSSS Rules' block influences all steering decisions.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the flow of data from applications through various steering functionalities in a User Equipment (UE) model. At the top, three types of flows are shown: + +- Non MPTCP & Non MPQUIC flows** (e.g. UDP, TCP, Ethernet flows) which pass through the **ATSSS-LL functionality**. +- MPTCP flows** (TCP flows from apps allowed to use MPTCP) which pass through the **MPTCP functionality**. This functionality splits flows into subflows bound to IP@1 and IP@2. +- MPQUIC flows** (UDP flows from apps allowed to use MPQUIC) which pass through the **MPQUIC functionality**. This functionality splits flows into subflows bound to IP@4 and IP@5. + +All three functionalities (ATSSS-LL, MPTCP, and MPQUIC) have a bidirectional connection to a central **ATSSS Rules** block. Below the functionalities, a central horizontal bar represents the aggregation of flows. From this bar, arrows point down to five IP addresses: IP@3 (from ATSSS-LL), IP@1 and IP@2 (from MPTCP), and IP@4 and IP@5 (from MPQUIC). These IP addresses are then distributed to two access paths at the bottom: + +- Non-3GPP access**: Receives IP@3, IP@1, and IP@2. +- 3GPP access**: Receives IP@2, IP@3, IP@4, and IP@5. + +Diagram illustrating steering functionalities in an example UE model. The diagram shows traffic flows from applications being steered through various functionalities (MPTCP, MPQUIC, ATSSS-LL) and then distributed across Non-3GPP and 3GPP access paths. A central 'ATSSS Rules' block influences all steering decisions. + +**Figure 5.32.6.1-1: Steering functionalities in an example UE model** + +Within the same MA PDU Session in the UE, it is possible to steer the MPTCP flows by using the MPTCP functionality, to steer the MPQUIC flows by using the MPQUIC functionality and, simultaneously, to steer all other flows by using the ATSSS-LL functionality. For the same packet flow, only one steering functionality shall be used. + +All steering functionalities in the UE shall take ATSSS decisions (i.e. decide how to steer, switch and split the traffic) by using the same set of ATSSS rules. Similarly, all ATSSS decisions in the UPF shall be taken by applying the same set of N4 rules, which support ATSSS. The ATSSS rules and the N4 rules supporting ATSSS are provisioned in the UE and in the UPF respectively, when the MA PDU Session is established. + +If the UE supports multiple steering functionalities, e.g. both the MPTCP functionality and the ATSSS-LL functionality, or the MPTCP functionality, the MPQUIC functionality and the ATSSS-LL functionality, it shall use the provisioned ATSSS rules (see TS 23.503 [45]) to decide which steering functionality to apply for a specific packet flow. + +#### 5.32.6.2 High-Layer Steering Functionalities + +##### 5.32.6.2.1 MPTCP Functionality + +As mentioned in clause 5.32.6.1, the MPTCP functionality in the UE applies the MPTCP protocol (IETF RFC 8684 [81]) and the provisioned ATSSS rules for performing access traffic steering, switching and splitting. The MPTCP functionality in the UE may communicate with the MPTCP Proxy functionality in the UPF using the user plane of the 3GPP access, or the non-3GPP access, or both. + +The MPTCP functionality may be enabled in the UE when the UE provides an "MPTCP capability" during PDU Session Establishment procedure. + +The network shall not enable the MPTCP functionality when the type of the MA PDU Session is Ethernet. + +If the UE indicates it is capable of supporting the MPTCP functionality, as described in clause 5.32.2, and the network agrees to enable the MPTCP functionality for the MA PDU Session then: + +- i) An associated MPTCP Proxy functionality is enabled in the UPF for the MA PDU Session by MPTCP functionality indication received in the Multi-Access Rules (MAR). +- ii) The network allocates to UE one IP address/prefix for the MA PDU Session and two additional IP addresses/prefixes, called "MPTCP link-specific multipath" addresses/prefixes; one associated with 3GPP access and another associated with the non-3GPP access. In the UE, these two IP addresses/prefixes are used only by the MPTCP functionality. Each "MPTCP link-specific multipath" address/prefix assigned to UE may not be routable via N6. The MPTCP functionality in the UE and the MPTCP Proxy functionality in the UPF shall use the "MPTCP link-specific multipath" addresses/prefixes for subflows over non-3GPP access and over 3GPP access and MPTCP Proxy functionality shall use the IP address/prefix of the MA PDU session for the communication with the final destination. In Figure 5.32.6.1-1, the IP@3 corresponds to the IP address of the MA PDU Session and the IP@1 and IP@2 correspond to the "MPTCP link-specific multipath" IP addresses. The following UE IP address management applies: + - The MA PDU IP address/prefix shall be provided to the UE via mechanisms defined in clause 5.8.2.2. + - The "MPTCP link-specific multipath" IP addresses/prefixes shall be allocated by the UPF and shall be provided to the UE via SM NAS signalling. + +NOTE 1: After the MA PDU Session is released, the same UE IP addresses/prefixes are not allocated to another UE for MA PDU Session in a short time. + +NOTE 2: The act of the UPF performing translation on traffic associated with the "MPTCP link-specific multipath" addresses to/from the MA PDU session IP address can lead to TCP port collision and exhaustion. The port collision can potentially occur because the UE also uses the MA PDU session IP address for non-MPTCP traffic, and this causes the port namespace of such address to be owned simultaneously by the UE and UPF. In addition, the port exhaustion can potentially occur when the UE creates a large number of flows, because multiple IP addresses used by the UE are mapped to a single MA PDU session IP address on the UPF. The UPF needs to consider these problems based on the UPF implementation, and avoid them by, for example, using additional N6-routable IP addresses for traffic associated to the link-specific multipath addresses/prefixes. How this is done is left to the implementation. + +- iii) The network shall send MPTCP proxy information to UE, i.e. the IP address, a port number and the type of the MPTCP proxy. The following type of MPTCP proxy shall be supported in this release: + - Type 1: Transport Converter, as defined in IETF RFC 8803 [82]. + +The MPTCP proxy information is retrieved by the SMF from the UPF during N4 session establishment. + +The UE shall support the client extensions specified in IETF RFC 8803 [82]. + +- iv) The network may indicate to UE the list of applications for which the MPTCP functionality should be applied. This is achieved by using the Steering Functionality component of an ATSSS rule (see clause 5.32.8). + +NOTE 3: To protect the MPTCP proxy function (e.g. to block DDOS to the MPTCP proxy function), the IP addresses of the MPTCP Proxy Function are only accessible from the two "MPTCP link-specific multipath" IP addresses of the UE via the N3/N9 interface. + +- v) When the UE indicates it is capable of supporting the MPTCP functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1) and these functionalities are enabled for the MA PDU Session, then the UE shall route via the MA PDU Session the TCP traffic of applications for which the MPTCP functionality should be applied (i.e. the MPTCP traffic), as defined in bullet iv. The UE may route all other traffic (i.e. the non-MPTCP traffic) via the MA PDU Session, but this type of traffic shall be routed on one of 3GPP access or non-3GPP access, based on the received ATSSS rule for non-MPTCP traffic (see clause 5.32.2). The UPF shall route all other traffic (i.e. non-MPTCP traffic) based on the N4 rules provided by the SMF. This may include N4 rules for ATSSS-LL, using any steering mode as instructed by the N4 rules. + +##### 5.32.6.2.2 MPQUIC Functionality + +The MPQUIC functionality enables steering, switching, and splitting of UDP traffic between the UE and UPF, in accordance with the ATSSS policy created by the network. The operation of the MPQUIC functionality is based on RFC 9298 [170] "proxying UDP in HTTP", which specifies how UDP traffic can be transferred between a client (UE) and a proxy (UPF) using the RFC 9114 [171] HTTP/3 protocol. The HTTP/3 protocol operates on top of the QUIC + +protocol (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]), which supports simultaneous communication over multiple paths, as defined in draft-ietf-quic-multipath [174]. + +The MPQUIC functionality in the UE communicates with the MPQUIC Proxy functionality in the UPF (see Figure 4.2.10-1) using the user plane of the 3GPP access, or the non-3GPP access, or both. + +The MPQUIC functionality may be enabled for an MA PDU Session with type IPv4, IPv6 or IPv4v6, when both the UE and the network support this functionality. The MPQUIC functionality shall not be enabled when the type of the MA PDU Session is Ethernet. + +The MPQUIC functionality is composed of three components: + +- 1) QoS flow selection & Steering mode selection: This component in the UE initiates the establishment of one or more multipath QUIC connections, after the establishment of the MA PDU Session and, for each uplink UDP flow, it selects a QoS flow (based on the QoS rules), a steering mode and a transport mode (based on the ATSSS rules). This component in the UPF selects, for each downlink UDP flow, a QoS flow (based on the N4 rules), a steering mode and a transport mode (based on the N4 rules). The supported transport modes are defined below. + +In the UE, this component is only used in the uplink direction, while, in the UPF, this component is only used in the downlink direction. + +- 2) HTTP/3 layer: Supports the HTTP/3 protocol defined in RFC 9114 [171] and the extensions defined in: + +- RFC 9298 [170] for supporting UDP proxying over HTTP; +- RFC 9297 [172] for supporting HTTP datagrams; and +- RFC 9220 [173] for supporting Extended CONNECT. + +The HTTP/3 layer selects a multipath QUIC connection to be used for each UDP flow and allocates a new QUIC stream on this connection that is associated with the UDP flow. It also configures this QUIC stream to apply a specific steering mode. + +In the UE, the HTTP/3 layer implements an HTTP/3 client, while, in the UPF, it implements an HTTP/3 proxy. + +- 3) QUIC layer: Supports the QUIC protocol as defined in the applicable IETF specifications (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]) and the extensions defined in: + +- RFC 9221 [169] for supporting unreliable datagram transport with QUIC; and +- draft-ietf-quic-multipath [174] for supporting QUIC connections using multiple paths simultaneously. + +When the MPQUIC functionality is applied, the protocol stack of the user plane is depicted in figure below. + +![Figure 5.32.6.2.2-1: UP protocol stack when the MPQUIC functionality is applied. The diagram shows the protocol stack across four entities: UE, 5G-AN, UPF, and Remote Host, separated by interfaces N3, N9, and N6. The UE stack includes PDU, HTTP/3 (connect-udp), MPQUIC, TLS, UDP, IP, and 5G-AN Protocol Layers. The 5G-AN stack includes Relay, GTP-U, UDP/IP, L2, and L1. The UPF stack includes Relay, GTP-U, UDP/IP, L2, L1, IP, UDP, TLS, MPQUIC, and HTTP/3 (connect-udp). The Remote Host stack includes PDU and N6 protocol layers. The UPF is labeled as the PDU Session Anchor.](492256bb98eb10f95553a7b1983c4b96_img.jpg) + +Figure 5.32.6.2.2-1: UP protocol stack when the MPQUIC functionality is applied. The diagram shows the protocol stack across four entities: UE, 5G-AN, UPF, and Remote Host, separated by interfaces N3, N9, and N6. The UE stack includes PDU, HTTP/3 (connect-udp), MPQUIC, TLS, UDP, IP, and 5G-AN Protocol Layers. The 5G-AN stack includes Relay, GTP-U, UDP/IP, L2, and L1. The UPF stack includes Relay, GTP-U, UDP/IP, L2, L1, IP, UDP, TLS, MPQUIC, and HTTP/3 (connect-udp). The Remote Host stack includes PDU and N6 protocol layers. The UPF is labeled as the PDU Session Anchor. + +Figure 5.32.6.2.2-1: UP protocol stack when the MPQUIC functionality is applied + +**Editor's note:** The above figure might need changes (e.g. related with the mandatory use of TLS) based on the security work in SA WG3. + +If the UE indicates that it is capable of supporting the MPQUIC functionality, as described in clause 5.32.2, and the network agrees to enable the MPQUIC functionality for the MA PDU Session then: + +- i) An associated MPQUIC Proxy functionality is enabled in the UPF for the MA PDU Session. +- ii) The network allocates to UE one IP address/prefix for the MA PDU Session and two additional IP addresses/prefixes, called "MPQUIC link-specific multipath " addresses/prefixes; one associated with 3GPP access and another associated with the non-3GPP access. In the UE, these two IP addresses/prefixes are used only by the MPQUIC functionality. Each "MPQUIC link-specific multipath" address/prefix assigned to UE may not be routable via N6. The MPQUIC functionality in the UE and the MPQUIC Proxy functionality in the UPF shall use the "MPQUIC link-specific multipath" addresses/prefixes for transmitting UDP flows over non-3GPP access and over 3GPP access. The MPQUIC Proxy functionality shall use the IP address/prefix of the MA PDU session for the communication with the final destination. In Figure 5.32.6.1-1, the IP@3 corresponds to the IP address of the MA PDU Session and the IP@4 and IP@5 correspond to the "MPQUIC link-specific multipath" addresses. The following UE IP address management applies: + - The MA PDU IP address/prefix shall be provided to the UE via mechanisms defined in clause 5.8.2.2. + - The "MPQUIC link-specific multipath" IP addresses/prefixes shall be allocated by the UPF and shall be provided to the UE via SM NAS signalling. + +NOTE 1: After the MA PDU Session is released, the same UE IP addresses/prefixes are not allocated to another UE for MA PDU Session in a short time. + +- iii) The network shall send MPQUIC proxy information to UE, i.e. one IP address of UPF, one UDP port number and the proxy type (e.g. "connect-udp"). This information is used by the UE for establishing multipath QUIC connections with the UPF, which implements the MPQUIC Proxy functionality. + - iv) After the MA PDU Session is established, the UE determines the number of multipath QUIC connections to be established with the UPF. The UE determines to establish at least as many multipath QUIC connections as the number of QoS flows of the MA PDU Session, i.e. one multipath QUIC connection per QoS flow. Each multipath QUIC connection carries the UDP traffic mapped to a single QoS flow. +- For the downlink traffic to which the MPQUIC functionality is to be applied, the QoS rules provided to UE include downlink QoS information and the UE applies the downlink QoS information to establish multipath QUIC connections for the QoS flows used for the downlink traffic only. +- v) During a QUIC connection establishment, the UE and UPF negotiate QUIC transport parameters and indicate (a) support of QUIC Datagram frames and (b) support of multipath. They indicate support of QUIC Datagram frames by providing the "max\_datagram\_frame\_size" transport parameter with a non-zero value (see RFC 9221 [169]) and they indicate support of multipath by providing the "enable\_multipath" transport parameter (see draft-ietf-quic-multipath [174]). + +In addition, during a QUIC connection establishment the QoS flow associated with this connection is determined. The UE sends all traffic of a QUIC connection over the QoS flow associated with this QUIC connection. This enables the UPF to determine the QoS flow associated with a QUIC connection and to select a QUIC connection for sending the downlink traffic of a QoS flow. + +- vi) After a QUIC connection establishment, the HTTP/3 client in the UE and the HTTP/3 proxy in the UPF negotiate HTTP settings and indicate support of HTTP Datagrams (see RFC 9297 [172]) and support of Extended CONNECT (see RFC 9220 [173]). To use MPQUIC proxying for a UDP traffic flow, the UE then sends a HTTP/3 CONNECT request (see RFC 9298 [170]) to the HTTP/3 proxy in the UPF. +- vii) The network may indicate to UE the list of applications for which the MPQUIC functionality should be applied. This is achieved by using the Steering Functionality component of an ATSSS rule (see clause 5.32.8). + +###### 5.32.6.2.2.1 Supported Transport Modes + +The MPQUIC functionality supports the following transport modes for transmitting a UDP flow between UE and UPF. The PCF selects which of these transport modes shall be applied for a UDP flow (SDF). The selected transport mode is provided to UE and UPF within the ATSSS rules and N4/MAR rules respectively. + +- Datagram mode 2: This transport mode is the mode defined in RFC 9298 [170]. It encapsulates UDP packets within QUIC Datagram frames and provides unreliable transport with no sequence numbering and no packet reordering / deduplication. +- Datagram mode 1: This transport mode is an extension of the mode defined in RFC 9298 [170]. It encapsulates UDP packets within QUIC Datagram frames and provides unreliable transport but with sequence numbering and with packet reordering / deduplication. It can be applied for any UDP flow. The details of the datagram mode 1, including the potential use of a Context ID (see RFC 9298 [170]), are considered in stage-3 specifications. + +**Editor's note:** A reference to the applicable stage-3 specification needs to be added to the above paragraph, to point to the stage-3 details of Datagram mode 1. + +- Stream mode: This transport mode is readily supported by the QUIC protocol. It encapsulates UDP packets within QUIC Stream frames and provides reliable transport with sequence numbering and with packet reordering / deduplication. It can be applied for UDP flows where it is known that the application does not perform retransmissions. + +NOTE 1: The Stream mode provides strict reliability and in-order delivery with re-transmissions and therefore can lead to melt down phenomena when reliable traffic (e.g. QUIC) is carried, or counteracts application decisions when UDP is selected to avoid reliability and/or in-order delivery. Therefore, it can be avoided for applications which perform their own reliability mechanisms. + +NOTE 2: When a steering mode is supported by ATSSS-LL for a UDP flow (e.g. Active-Standby), the MPQUIC steering functionality can be selected if additional features, which are not supported by the ATSSS-LL steering functionality and PMF, are required for the traffic steering/switching/splitting of the UDP flow. + +#### 5.32.6.3 Low-Layer Steering Functionalities + +##### 5.32.6.3.1 ATSSS-LL Functionality + +The ATSSS-LL functionality in the UE does not apply a specific protocol. It is a data switching function, which decides how to steer, switch and split the uplink traffic across 3GPP and non-3GPP accesses, based on the provisioned ATSSS rules and local conditions (e.g. signal loss conditions). The ATSSS-LL functionality in the UE may be applied to steer, switch and split all types of traffic, including TCP traffic, UDP traffic, Ethernet traffic, etc. The ATSSS-LL functionality does not support the Redundant Steering Mode. + +The ATSSS-LL functionality may be enabled in the UE when the UE provides an "ATSSS-LL capability" during the PDU Session Establishment procedure. + +The ATSSS-LL functionality is mandatory in the UE for MA PDU Session of type Ethernet. In addition: + +- When the UE neither supports the MPTCP functionality nor the MPQUIC functionality, the ATSSS-LL functionality is mandatory in the UE for an MA PDU Session of type IP. +- When the UE supports the MPTCP functionality and does not support the MPQUIC functionality, the ATSSS-LL functionality with Active-Standby Steering Mode is mandatory in the UE for an MA PDU Session of type IP to support non-MPTCP traffic. +- When the UE supports the MPQUIC functionality and does not support the MPTCP functionality, the ATSSS-LL functionality with Active-Standby Steering Mode is mandatory in the UE for an MA PDU Session of type IP to support non-MPQUIC traffic. +- When the UE supports both the MPTCP functionality and the MPQUIC functionality, the ATSSS-LL functionality with Active-Standby Steering Mode is mandatory in the UE for an MA PDU Session of type IP to support non-MPTCP and non-MPQUIC traffic. + +The network shall also support the ATSSS-LL functionality as defined for the UE. The ATSSS-LL functionality in the UPF is enabled for a MA PDU Session by ATSSS-LL functionality indication received in the Multi-Access Rules (MAR). + +### 5.32.7 Interworking with EPS + +#### 5.32.7.1 General + +Multi-access connectivity using ATSSS via EPC only is not supported. + +Interworking for MA PDU Session, if allowed by the network, is based on the interworking functionality specified in clause 5.17.2, with the differences and clarifications described in the following clauses. + +A PDN Connection in EPS may be modified into a MA PDU Session when transferred to 5GS if the UE and the SMF+PGW-C support the ATSSS feature. + +#### 5.32.7.2 Interworking with N26 Interface + +Interworking with N26 interface is based on clause 5.17.2.2, with the following differences and clarifications: + +- When the UE is registered to the same PLMN over 3GPP and non-3GPP accesses, and the UE request a new MA PDU Session via non-3GPP access, the AMF also includes the indication of interworking with N26 to SMF. +- The SMF does not request EBI allocation when MA PDU Session is established only over non-3GPP access. If MA PDU Session is released over 3GPP access, the allocated EBI(s) for the MA PDU Session is revoked by the SMF as described in clause 4.11.1.4.3 of TS 23.502 [3]. +- The SMF does not request EBI allocation for GBR QoS Flow if the GBR QoS Flow is only allowed over non-3GPP access. +- If the UE and the network support MA PDU Sessions with 3GPP access connected to EPC, the MA PDU Session may be simultaneously associated with user-plane resources on 3GPP access network connected to EPC and with non-3GPP access network connected to 5GC. This case is further described in clause 5.32.1 and in clause 4.22.2.3 of TS 23.502 [3]. +- If the UE or the network does not support MA PDU Session with 3GPP access connected to EPC, the MA PDU Session is handled as follows: + - When UE moves from 5GS to EPS, for both idle mode and connected mode mobility, if the MA PDU Session is moved to EPS as a PDN connection, the SMF triggers PDU Session Release procedure to release the MA PDU Session over Non-3GPP access in 5GS. UE and SMF remove ATSSS related contexts e.g. ATSSS rules, Measurement Assistance Information. + - When UE moves from 5GS to EPS, for both idle mode and connected mode mobility, if the MA PDU Session is not moved to EPS as a PDN connection, the 3GPP access of this MA PDU session becomes unavailable and the AMF notifies the SMF. In turn, the SMF may decide to move the traffic to Non-3GPP access of the MA PDU session, if it is available. When UE moves back from EPS to 5GS, after the UE is registered over the 3GPP, the UE may add user-plane resources over the 3GPP access to the MA PDU session by triggering PDU Session Establishment procedure as specified in clause 5.32.2. + - After UE moves from EPS to 5GS, for both idle mode and connected mode mobility, if the UE requires MA PDU session, or if no policy in the UE (e.g. no URSP rule) and no local restrictions mandate a single access for the PDU Session, UE triggers the PDU Session Modification procedure as described in clause 4.22.6.3 of TS 23.502 [3] to provide the ATSSS Capability to SMF+PGW-C. The SMF+PGW-C may determine whether to modify this PDU Session to a MA PDU Session in 5GS, e.g. based on SMF+PGW-C and UE's ATSSS Capability, subscription data and local policy. If dynamic PCC is to be used for the MA PDU Session, the PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. If the MA PDU Session is allowed, the SMF provides ATSSS rule(s) and Measurement Assistance Information to the UE. If the UE receives ATSSS rules and is not registered to non-3GPP access, the UE establishes the second user-plane over non-3GPP access after the UE is registered to non-3GPP access. If UE was registered to non-3GPP access in 5GS, the UP resources over non-3GPP access are also established by the SMF using the PDU Session Modification procedure. + +#### 5.32.7.3 Interworking without N26 Interface + +Interworking without N26 interface is based on clause 5.17.2.3, with the following differences and clarifications: + +- After UE moves from 5GS to EPS, UE may send a PDN Connectivity Request with "handover" indication to transfer the MA PDU Session to EPS. Then, if the UE or the network does not support MA PDU Session with 3GPP access connected to EPC, the SMF+PGW-C triggers to release MA PDU in 5GS. If UE does not transfer the MA PDU Session to EPS, UE keeps the MA PDU Session in 5GS. If the UE and the network support MA PDU Session with 3GPP access connected to EPC, the UE includes a "handover" indication and a "MA PDU Request" indication as well as the PDU Session ID in the PCO and the SMF+PGW-C keeps the user-plane resources over non-3GPP access in 5GC as described in clause 4.22.6.2.5 of TS 23.502 [3]. In this case, UE may report to UPF that 3GPP access is unavailable, all MA PDU Session traffic is transported over N3GPP access. Later, if UE returns to 5GS, UE may report the 3GPP access availability to UPF. +- After UE moves from EPS to 5GS, UE may trigger PDU Session Establishment procedure to transfer the PDN Connection to 5GS. During the PDU Session Establishment procedure, if the PDN Connection was not used as the 3GPP access leg of the MA PDU Session, the UE may request to establish a MA PDU Session by including "MA PDU Request" or, if no policy in the UE (e.g. no URSP rule) and no local restrictions mandate a single access for the PDU Session, the UE may include the "MA PDU Network-Upgrade Allowed" indication. + +### 5.32.8 ATSSS Rules + +As specified in clause 5.32.3, after the establishment of a MA PDU Session, the UE receives a prioritized list of ATSSS rules from the SMF. The structure of an ATSSS rule is specified in Table 5.32.8-1. + +**Table 5.32.8-1: Structure of ATSSS Rule** + +| Information name | Description | Category | SMF permitted to modify in a PDU context | Scope | +|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|------------------------------------------|-------------| +| Rule identifier | Unique identifier to identify the ATSSS Rule | Mandatory | No | PDU context | +| Rule Precedence | Determines the order in which the ATSSS rule is evaluated in the UE. | Mandatory (NOTE 1) | Yes | PDU context | +| Traffic Descriptor | This part defines the Traffic descriptor components for the ATSSS rule. | Mandatory (NOTE 2) | | | +| Application descriptors | One or more application identities that identify the application(s) generating the traffic (NOTE 3). | Optional | Yes | PDU context | +| IP descriptors (NOTE 4) | One or more 5-tuples that identify the destination of IP traffic. | Optional | Yes | PDU context | +| Non-IP descriptors (NOTE 4) | One or more descriptors that identify the destination of non-IP traffic, i.e. of Ethernet traffic. | Optional | Yes | PDU context | +| Access Selection Descriptor | This part defines the Access Selection Descriptor components for the ATSSS rule. | Mandatory | | | +| Steering Mode | Identifies the steering mode that should be applied for the matching traffic and associated parameters. | Mandatory (NOTE 8) | Yes | PDU context | +| Steering Mode Indicator | Indicates either autonomous load-balance operation or UE-assistance operation if steering mode is set to "Load Balancing". | Optional (NOTE 6) | Yes | PDU context | +| Threshold Values (NOTE 9) | A Maximum RTT and/or a Maximum Packet Loss Rate. | Optional (NOTE 6) | Yes | PDU context | +| Steering Functionality | Identifies whether the MPTCP functionality, the MPQUIC functionality, or the ATSSS-LL functionality should be applied for the matching traffic. | Optional (NOTE 5) (NOTE 8) | Yes | PDU context | +| Transport Mode | Identifies the transport mode (see clause 5.32.6.2.2.1) that should be used for the matching traffic, when the Steering Functionality is the MPQUIC functionality. | Optional (NOTE 7) | Yes | PDU context | + +NOTE 1: Each ATSSS rule has a different precedence value from the other ATSSS rules. +NOTE 2: At least one of the Traffic Descriptor components is present. +NOTE 3: An application identity consists of an OSId and an OSAppId. +NOTE 4: An ATSSS rule cannot contain both IP descriptors and Non-IP descriptors. +NOTE 5: If the UE supports only one Steering Functionality, this component is omitted. +NOTE 6: The Steering Mode Indicator and the Threshold Values shall not be provided together. +NOTE 7: The Transport Mode shall be included when the Steering Functionality is the MPQUIC functionality. In all other cases, the Transport Mode shall not be included. +NOTE 8: The Steering functionality "ATSSS-LL functionality" shall not be provided together with Steering Mode "Redundant". +NOTE 9: If the Steering Mode is "Redundant", either a Maximum RTT or a Maximum Packet Loss Rate may be provided, but not both. + +The UE evaluates the ATSSS rules in priority order. + +Each ATSSS rule contains a Traffic Descriptor (containing one or more components described in Table 5.32.8-1) that determines when the rule is applicable. An ATSSS rule is determined to be applicable when every component in the Traffic Descriptor matches the considered service data flow (SDF). + +Depending on the type of the MA PDU Session, the Traffic Descriptor may contain the following components (the details of the Traffic Descriptor generation are described in clause 5.32.3): + +- For IPv4, or IPv6, or IPv4v6 type: Application descriptors and/or IP descriptors. +- For Ethernet type: Application descriptors and/or Non-IP descriptors. + +One ATSSS rule with a "match all" Traffic Descriptor may be provided, which matches all SDFs. When provided, it shall have the least Rule Precedence value, so it shall be the last one evaluated by the UE. + +NOTE 1: The format of the "match all" Traffic descriptor of an ATSSS rule is defined in stage-3. + +Each ATSSS rule contains an Access Selection Descriptor that contains the following components: + +- A Steering Mode, which determines how the traffic of the matching SDF should be distributed across 3GPP and non-3GPP accesses. The following Steering Modes are supported: + - Active-Standby: It is used to steer a SDF on one access (the Active access), when this access is available, and to switch the SDF to the available other access (the Standby access), when Active access becomes unavailable. When the Active access becomes available again, the SDF is switched back to this access. If the Standby access is not defined, then the SDF is only allowed on the Active access and cannot be transferred on another access. + - Smallest Delay: It is used to steer a SDF to the access that is determined to have the smallest Round-Trip Time (RTT). As defined in clause 5.32.5, measurements may be obtained by the UE and UPF to determine the RTT over 3GPP access and over non-3GPP access. In addition, if one access becomes unavailable, all SDF traffic is switched to the other available access. It can only be used for the Non-GBR SDF. + - Load-Balancing: It is used to split a SDF across both accesses if both accesses are available. It contains the percentage of the SDF traffic that should be sent over 3GPP access and over non-3GPP access. Load-Balancing is only applicable to Non-GBR SDF. In addition, if one access becomes unavailable, all SDF traffic is switched to the other available access, as if the percentage of the SDF traffic transported via the available access was 100%. + - Priority-based: It is used to steer all the traffic of an SDF to the high priority access, until this access is determined to be congested. In this case, the traffic of the SDF is sent also to the low priority access, i.e. the SDF traffic is split over the two accesses. In addition, when the high priority access becomes unavailable, all SDF traffic is switched to the low priority access. How UE and UPF determine when a congestion occurs on an access is implementation dependent. It can only be used for the Non-GBR SDF. + - Redundant (without Threshold Values): It is used to duplicate traffic of an SDF on both accesses if both accesses are available. A Primary Access (either 3GPP access or Non-3GPP access) may be provided to the UE in the ATSSS rules and to the UPF in the N4 rules. If a Primary Access is provided, UE and UPF shall send all data packets of the SDF on the Primary Access and may duplicate data packets of the SDF on the other access. How many and which data packets are duplicated by UE and UPF on the other access is based on implementation. If the Primary Access is not provided to UE and UPF, the UE and UPF shall send all data packets of the SDF on both accesses. It can be used for GBR and Non-GBR SDF. +- A Steering Mode Indicator, which indicates that the UE may change the default steering parameters provided in the Steering Mode component and may adjust the traffic steering based on its own decisions. Only one of the following Steering Mode Indicators may be provided: + - Autonomous load-balance indicator: This indicator may be provided only when the Steering Mode is Load-Balancing. When provided, the UE may ignore the percentages in the Steering Mode component (i.e. the default percentages provided by the network) and may autonomously determine its own percentages for traffic splitting, in a way that maximizes the aggregated bandwidth in the uplink direction. The UE is expected to determine its own percentages for traffic splitting by performing measurements across the two accesses. The UPF may apply a similar behaviour when the autonomous load-balance indicator is included in an N4 rule. + - UE-assistance indicator: This indicator may be provided only when the Steering Mode is Load-Balancing. When provided by the network, it indicates that (a) the UE may decide how to distribute the UL traffic of the matching SDF based on the UE's internal state (e.g. when the UE is in the special internal state, e.g. lower battery level), and that (b) the UE may inform the UPF how it decided to distribute the UL traffic of the + +matching SDF. In the normal cases, although with this indicator provided, the UE shall distribute the UL traffic as indicated by the network. + +NOTE 2: Typically, the UE-assistance indicator can be provided for SDFs for which the network has no strong steering requirements. For example, when the network has no strong steering requirements for the default traffic of an MA PDU Session, the network can indicate (i) that this traffic must be steered with Load-Balancing steering mode using 50% - 50% split percentages, and (ii) that the UE is allowed to use other split percentages, such as 0% - 100%, if this is needed by the UE to optimize its operation (e.g. to minimize its battery consumption). + +- Threshold Values: One or more threshold values may be provided when the Steering Mode is Priority-based or when the Steering Mode is Load-Balancing with fixed split percentages (i.e. without the Autonomous load-balance indicator or UE assistance indicator). One threshold value may be provided when the Steering Mode is Redundant. A threshold value may be either a value for RTT or a value for Packet Loss Rate. The threshold values are applicable to both accesses and are applied by the UE and UPF as follows: + - Load-Balancing Steering Mode with fixed split percentages (i.e. without the Autonomous load-balance indicator or UE assistance indicator): When at least one measured parameter (i.e. RTT or Packet Loss Rate) on one access exceeds the provided threshold value, the UE and UPF may stop sending traffic on this access, or may continue sending traffic on this access but should reduce the traffic on this access by an implementation specific amount and shall send the amount of reduced traffic on the other access. When all measured parameters (i.e. RTT and Packet Loss Rate) for both accesses do not exceed the provided threshold values, the UE and UPF shall apply the fixed split percentages. + - Priority-based Steering Mode: When one or more threshold values are provided for the Priority-based Steering Mode, these threshold values should be considered by UE and UPF to determine when an access becomes congested. For example, when a measured parameter (i.e. RTT or Packet Loss Rate) on one access exceeds the provided threshold value, the UE and UPF may consider this access as congested and send the traffic also to the low priority access. + - Redundant Steering Mode: When the measured Packet Loss Rate exceeds the provided threshold value on both accesses, the UE and UPF shall duplicate the traffic of the SDF on both accesses. When the measured RTT exceeds the provided threshold value on both accesses, the UE and UPF may duplicate the traffic of the SDF on both accesses based on implementation. When the measured parameter (i.e. either RTT or Packet Loss Rate) exceeds the provided threshold value on one access only, the UE and UPF shall send the traffic of the SDF only over the other access. When the measured parameter (i.e. either RTT or Packet Loss Rate) does not exceed the provided threshold value on any access, the UE and UPF shall send the traffic of the SDF only over the Primary Access. The Primary Access (either 3GPP access or Non-3GPP access) may be provided to the UE in the ATSSS rules and to the UPF in the N4 rules. If the Primary Access is not provided to the UE and UPF, UE and UPF shall select a Primary Access based on their own implementation (e.g. using the lowest RTT access or the lowest Packet Loss Rate access). If measurement results on an access are not available for a parameter, it is considered that the measured parameter for this access has not exceeded the provided threshold value. If a threshold value is provided when the Steering Mode is Redundant, the Steering Mode can only be used for Non-GBR SDF. +- A Steering Functionality, which identifies whether the MPTCP functionality, or the MPQUIC functionality, or the ATSSS-LL functionality should be used to steer the traffic of the matching SDF. This is used when the UE supports multiple functionalities for ATSSS, as specified in clause 5.32.6 ("Support of Steering Functions"). +- A Transport Mode, which identifies the transport mode that should be applied by the MPQUIC functionality for the matching traffic. The transport modes supported by the MPQUIC functionality are defined in clause 5.32.6.2.2.1. + +NOTE 3: There is no need to update the ATSSS rules when one access becomes unavailable or available. + +As an example, the following ATSSS rules could be provided to UE: + +- a) "Traffic Descriptor: UDP, DestAddr 1.2.3.4", "Steering Mode: Active-Standby, Active=3GPP, Standby=non-3GPP": + - This rule means "steer UDP traffic with destination IP address 1.2.3.4 to the active access (3GPP), if available. If the active access is not available, use the standby access (non-3GPP)". +- b) "Traffic Descriptor: TCP, DestPort 8080", "Steering Mode: Smallest Delay": + +- This rule means "steer TCP traffic with destination port 8080 to the access with the smallest delay". The UE needs to measure the RTT over both accesses, in order to determine which access has the smallest delay. +- c) "Traffic Descriptor: TCP traffic of Application-1", "Steering Mode: Load-Balancing, 3GPP=20%, non-3GPP=80%", "Steering Functionality: MPTCP": + - This rule means "send 20% of the TCP traffic of Application-1 to 3GPP access and 80% to non-3GPP access by using the MPTCP functionality". +- d) "Traffic Descriptor: TCP traffic of Application-1", "Steering Mode: Load-Balancing, 3GPP=20%, non-3GPP=80%", "Threshold Value for Packet Loss Rate: 1%", "Steering Functionality: MPTCP": + - This rule means "send 20% of the TCP traffic of Application-1 to 3GPP access and 80% to non-3GPP access as long as the Packet Loss Rate does not exceed 1% on both accesses, by using the MPTCP functionality. If the measured Packet Loss Rate of an access exceeds 1%, then the TCP traffic of Application-1 may be reduced on this access and sent via the other access". +- e) "Traffic Descriptor: UDP traffic of Application-1", "Steering Mode: Load-Balancing, 3GPP=30%, non-3GPP=70%", "Steering Functionality: MPQUIC", "Transport Mode: Datagram mode 1": + - This rule means "send 30% of the UDP traffic of Application-1 to 3GPP access and 70% to non-3GPP access by using the MPQUIC functionality with the Datagram mode 1". +- f) "Traffic Descriptor: com.example.app0, TCP", "Steering Mode: Redundant", "Steering Functionality: MPTCP": + - This rule means "traffic duplication is applied by the MPTCP steering functionality to the TCP traffic of application com.example.app0 and 100% of the traffic is duplicated over both accesses". +- g) "Traffic Descriptor: com.example.app1, TCP", "Steering Mode: Redundant, Primary Access=3GPP, Threshold Value for Packet Loss Rate: 0.1%", "Steering Functionality: MPTCP": + - This rule means "traffic duplication is applied to the TCP traffic of application com.example.app1. If the measured PLR exceeds 0.1% on both accesses, all matched traffic is duplicated on both accesses. If the measured PLR exceeds 0.1% on one access only (either 3GPP or non-3GPP access), all matched traffic is sent over the other access only. If the measured PLR does not exceed 0.1% on any access, all matched traffic is sent over 3GPP access only as this is the Primary Access". +- h) "Traffic Descriptor: com.example.app2, TCP", "Steering Mode: Redundant, Threshold Value for Packet Loss Rate: 0.1%", "Steering Functionality: MPTCP": + - This rule means "traffic duplication is applied to the TCP traffic of application com.example.app2. If the measured PLR exceeds 0.1% on both accesses, all matched traffic is duplicated and transmitted on both accesses. If the measured PLR exceeds 0.1% on one access only (either 3GPP or non-3GPP access), all matched traffic is sent over the other access only. If the measured PLR does not exceed 0.1% on any access, the UE or UPF selects the access based on their own implementation, e.g. the access with lower Packet Loss Rate to transmit all matched traffic". + +## 5.33 Support for Ultra Reliable Low Latency Communication + +### 5.33.1 General + +The following features described in 5.33 may be used to enhance 5GS to support Ultra Reliable Low Latency Communication (URLLC): + +- Redundant transmission for high reliability communication. + +In this Release, URLLC applies to 3GPP access only. + +When a PDU Session is to serve URLLC QoS Flow, the UE and SMF should establish the PDU Session as always-on PDU Session as described in clause 5.6.13. + +NOTE 1: How the UE knows whether a PDU Session is to serve a URLLC QoS Flow when triggering PDU Session establishment is up to UE implementation. + +NOTE 2: No additional functionality is specified for URLLC in order to support Home Routed roaming scenario in this Release. + +### 5.33.2 Redundant transmission for high reliability communication + +#### 5.33.2.1 Dual Connectivity based end to end Redundant User Plane Paths + +In order to support highly reliable URLLC services, a UE may set up two redundant PDU Sessions over the 5G network, such that the 5GS sets up the user plane paths of the two redundant PDU Sessions to be disjoint. The user's subscription indicates if user is allowed to have redundant PDU Sessions and this indication is provided to SMF from UDM. + +NOTE 1: It is out of scope of 3GPP how to make use of the duplicate paths for redundant traffic delivery end-to-end. It is possible to rely on upper layer protocols, such as the IEEE 802.1 TSN (Time Sensitive Networking) FRER (Frame Replication and Elimination for Reliability) [83], to manage the replication and elimination of redundant packets/frames over the duplicate paths which can span both the 3GPP segments and possibly fixed network segments as well. + +NOTE 2: The following redundant network deployment aspects are within the responsibility of the operator and are not subject to 3GPP standardization: + +- RAN supports dual connectivity, and there is sufficient RAN coverage for dual connectivity in the target area. +- UEs support dual connectivity. +- The core network UPF deployment is aligned with RAN deployment and supports redundant user plane paths. +- The underlying transport topology is aligned with the RAN and UPF deployment and supports redundant user plane paths. +- The physical network topology and geographical distribution of functions also supports the redundant user plane paths to the extent deemed necessary by the operator. +- The operation of the redundant user plane paths is made sufficiently independent, to the extent deemed necessary by the operator, e.g. independent power supplies. + +Figure 5.33.2.1-1 illustrates an example user plane resource configuration of dual PDU Sessions when redundancy is applied. One PDU Session spans from the UE via Master RAN node to UPF1 acting as the PDU Session Anchor, and the other PDU Session spans from the UE via Secondary RAN node to UPF2 acting as the PDU Session Anchor. As described in TS 37.340 [31], NG-RAN may realize redundant user plane resources for the two PDU Sessions with two NG-RAN nodes (i.e. Master RAN node and Secondary RAN node as shown in Figure 5.33.2.1-1) or a single NG-RAN node. In both cases, there is a single N1 interface towards AMF. + +Based on these two PDU Sessions, two independent user plane paths are set up. UPF1 and UPF2 connect to the same Data Network (DN), even though the traffic via UPF1 and UPF2 may be routed via different user plane nodes within the DN. + +In order to establish two redundant PDU Sessions and associate the duplicated traffic coming from the same application to these PDU Sessions, URSP as specified in TS 23.503 [45] may be used, or alternatively the UE may perform this task independently from URSP. + +When URSP is used to establish two redundant PDU Sessions, duplicated traffic from the application, associated to the redundant PDU Sessions, is differentiated by two distinct traffic descriptors, each in a distinct URSP rule. These traffic descriptors need to have different DNNs, IP descriptors or non-IP descriptors (e.g. MAC address, VLAN ID), so that the two redundant PDU Sessions are matched to the Route Selection Descriptors of distinct URSP rules. These Route Selection Descriptors of distinct URSP rules may include corresponding RSNs and PDU Session Pair IDs. The Route Selection Descriptors share same PDU Session Pair ID, if included, to denote the two traffic are redundant with each other. How does UE determines the PDU Session Pair ID and/or RSN from the matched URSP rules is described in clause 6.6.2 of TS 23.503 [45]. + +When the UE performs the establishment of two redundant PDU Sessions and the duplication of traffic independently from URSP, the UE may establish two redundant PDU Sessions even when the application does not duplicate the traffic and the application does not provide two distinct traffic descriptors. In this case the UE may set the RSN and PDU Session Pair ID in the PDU Session Establishment Request message based on UE implementation. + +NOTE 3: As an example, the UE may use the implementation of FRER (Frame Replication and Elimination for Reliability), IEEE Std 802.1CB-2017 [83], in the UE's operating system. + +If the operator decides to allow UE to use its own mechanisms to determine PDU Session Pair ID and RSN (where such UE capability is known based on local PCF configuration based on e.g. deployment, terminal implementation or policies per group of UE(s)), then the PCF shall not include PDU Session Pair ID and RSN in URSP rule. + +The redundant user plane set up applies to both IP and Ethernet PDU Sessions. + +![Diagram illustrating the example scenario for end to end redundant User Plane paths using Dual Connectivity. The diagram shows a UE connected to two NG-RANs: Master NG-RAN and Secondary NG-RAN, which are interconnected via an Xn interface. The Master NG-RAN is connected to an AMF via an N2 interface. The AMF is connected to two SMFs, SMF1 and SMF2, via N4 interfaces. Both SMF1 and SMF2 are connected to a UPF (UPF1 and UPF2) via N3 interfaces. The UPFs are connected to a DN (Data Network) via N6 interfaces. The UE is connected to both NG-RANs, and the Master NG-RAN is connected to the AMF via an N2 interface. The AMF is connected to SMF1 and SMF2 via N4 interfaces. SMF1 and SMF2 are connected to UPF1 and UPF2 via N3 interfaces. UPF1 and UPF2 are connected to the DN via N6 interfaces.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +``` + +graph TD + UE[UE] --- MasterNGRAN[Master NG-RAN] + UE --- SecondaryNGRAN[Secondary NG-RAN] + MasterNGRAN --- Xn[Xn] + SecondaryNGRAN --- Xn + MasterNGRAN --- N2[N2] + N2 --- AMF[AMF] + AMF --- N4_1[N4] + N4_1 --- SMF1[SMF1] + AMF --- N4_2[N4] + N4_2 --- SMF2[SMF2] + SMF1 --- N3_1[N3] + N3_1 --- UPF1[UPF1] + SMF2 --- N3_2[N3] + N3_2 --- UPF2[UPF2] + UPF1 --- N6_1[N6] + N6_1 --- DN[DN] + UPF2 --- N6_2[N6] + N6_2 --- DN + +``` + +Diagram illustrating the example scenario for end to end redundant User Plane paths using Dual Connectivity. The diagram shows a UE connected to two NG-RANs: Master NG-RAN and Secondary NG-RAN, which are interconnected via an Xn interface. The Master NG-RAN is connected to an AMF via an N2 interface. The AMF is connected to two SMFs, SMF1 and SMF2, via N4 interfaces. Both SMF1 and SMF2 are connected to a UPF (UPF1 and UPF2) via N3 interfaces. The UPFs are connected to a DN (Data Network) via N6 interfaces. The UE is connected to both NG-RANs, and the Master NG-RAN is connected to the AMF via an N2 interface. The AMF is connected to SMF1 and SMF2 via N4 interfaces. SMF1 and SMF2 are connected to UPF1 and UPF2 via N3 interfaces. UPF1 and UPF2 are connected to the DN via N6 interfaces. + +**Figure 5.33.2.1-1: Example scenario for end to end redundant User Plane paths using Dual Connectivity** + +Support of redundant PDU Sessions include: + +- UE initiates two redundant PDU Sessions and may provide PDU Session Pair ID (optional) and the RSN (optional). Different combinations of RSN, DNN and S-NSSAI are used for each PDU Session within a given pair of redundant PDU Sessions. Different combinations of PDU Session Pair ID, DNN and S-NSSAI are used between the different pairs of redundant PDU Session. +- The UE may include a PDU Session Pair ID and/or RSN in each of the PDU Session establishment Request when it establishes redundant PDU Sessions. UE determines the PDU Session Pair ID and/or RSN based on UE local mechanism or the matched URSP rules. +- The SMF determines whether the PDU Session is to be handled redundantly. The determination is based on the presence of the PDU Session Pair ID and/or RSN in the PDU Session Establishment Request or the determination is based on an indication that redundant PDU Session is required provided by PCF for the PDU Session, if dynamic PCC applies for the PDU Session or the combination of the S-NSSAI, DNN, user subscription and local policy configuration in the SMF if dynamic PCC is not used for the PDU Session. If the PDU session is to be handled redundantly and the PDU Session Pair ID was not included in the PDU Session Establishment request, the SMF uses S-NSSAI, DNN and local configuration to determine the PDU Session Pair ID. If the PDU session is to be handled redundantly and RSN was not included in the PDU Session Establishment request, the SMF uses S-NSSAI, DNN to determine the RSN value. The RSN differentiates the PDU Sessions that are handled redundantly and indicates redundant user plane requirements for the PDU Sessions in NG-RAN. +- The SMF shall provide the RSN and PDU Session Pair ID to the NG-RAN for a redundant PDU Session. +- Operator configuration of UPF selection ensures the appropriate UPF selection for disjoint paths. +- At establishment of the PDU Sessions or at transitions to CM-CONNECTED state, the RSN parameter indicates to NG-RAN that redundant user plane resources shall be provided for the given PDU Sessions by means of dual connectivity. The PDU Session Pair ID identifies the two redundant PDU Sessions that belong together. The + +value of the RSN parameter and the PDU Session Pair ID indicates redundant user plane requirements for the PDU Sessions. This request for redundant handling is made by indicating the RSN to the NG-RAN node on a per PDU Session granularity. PDU Sessions associated with different RSN values shall be realized by different, redundant UP resources. Based on the RSN, the PDU Session Pair ID and RAN configuration, the NG-RAN sets up dual connectivity as defined in TS 37.340 [31] so that the sessions have end to end redundant paths. When there are multiple PDU Sessions with the RSN parameter set, of different values of RSN and the same PDU Session Pair ID, this indicates to NG-RAN that CN is requesting dual connectivity to be set up and the user plane shall be handled as indicated by the RSN parameter, the PDU Session Pair ID and the associated RAN configuration. If the RSN value and PDU Session Pair ID are provided to the NG-RAN, NG-RAN shall consider the RSN value and PDU Session Pair ID when it associates the PDU Sessions with NG-RAN UP. + +NOTE 4: The decision to set up dual connectivity remains in NG-RAN as defined today. NG-RAN takes into account the additional request for the dual connectivity setup provided by the CN. + +- Using NG-RAN local configuration, NG-RAN determines whether the request to establish RAN resources for a PDU Session is fulfilled or not considering user plane requirements indicated by the RSN parameter and the PDU Session Pair ID by means of dual connectivity. If the request to establish RAN resources for PDU Session can be fulfilled by the RAN, the PDU Session is established even if the user plane requirements indicated by RSN cannot be satisfied. The decision for each PDU Session is taken independently (i.e. rejection of a PDU Session request shall not release the previously established PDU Session). The RAN shall determine whether to notify the SMF if the RAN resources indicated by the RSN parameter and the PDU Session Pair ID can no longer be maintained and SMF can use that to determine if the PDU Session should be released. +- In the case of Ethernet PDU Sessions, the SMF has the possibility to change the UPF (acting as the PSA) and select a new UPF based on the identity of the Secondary RAN node for the second PDU Session if the Secondary RAN node is modified (or added/released), using the Ethernet PDU Session Anchor Relocation procedure described in clause 4.3.5.8 of TS 23.502 [3]. +- The SMF's charging record may reflect the RSN information. +- The RSN parameter and the PDU Session Pair ID, if available, is transferred from Source NG-RAN to Target NG-RAN in the case of handover. + +#### 5.33.2.2 Support of redundant transmission on N3/N9 interfaces + +If the reliability of NG-RAN node, UPF and CP NFs are high enough to fulfil the reliability requirement of URLLC services served by these NFs, but the reliability of single N3 tunnel is considered not high enough, e.g. due to the deployment environment of backhaul network, the redundant transmission may be deployed between PSA UPF and NG-RAN via two independent N3 tunnels, which are associated with a single PDU Session, over different transport layer path to enhance the reliability. SMF may make use of Redundant Transmission Experience analytics provided by NWDAF, as described in clause 6.13 of TS 23.288 [86], to determine whether redundant transmission for the PDU session of the URLLC shall be performed or (if activated) shall be stopped. + +To ensure the two N3 tunnels are transferred via disjointed transport layer paths, the SMF or PSA UPF should provide different routing information in the tunnel information (e.g. different IP addresses or different Network Instances), and these routing information should be mapped to disjoint transport layer paths according to network deployment configuration. The SMF indicates NG-RAN and PSA UPF that one of the two CN/AN Tunnel Info is used as the redundancy tunnel of the PDU Session accordingly. The redundant transmission using the two N3/N9 tunnels are performed at QoS Flow granularity and are sharing the same QoS Flow ID. + +During or after a URLLC QoS Flow establishment, if the SMF decided that redundant transmission shall be performed based on authorized 5QI, NG-RAN node capability, operator configuration and/or Redundant Transmission Experience analytics, the SMF informs the PSA UPF and NG-RAN to perform redundant transmission via N4 interface and N2 information accordingly. In this case, NG-RAN should also provide different routing information in the tunnel information (e.g. different IP addresses), and these routing information should be mapped to disjoint transport layer paths according to network deployment configuration. + +NOTE 1: The NG-RAN node capability to support the redundant transmission on N3/N9 can be configured in the SMF per network slice or per SMF service area. + +If duplication transmission is performed on N3/N9 interface, for each downlink packet of the QoS Flow the PSA UPF received from DN, the PSA UPF replicates the packet and assigns the same GTP-U sequence number to them for the + +redundant transmission. The NG-RAN eliminates the duplicated packets based on the GTP-U sequence number and then forwards the PDU to the UE. + +For each uplink packet of the QoS Flow the NG-RAN received from UE, the NG-RAN replicates the packet and assigns the same GTP-U sequence number to them for redundant transmission. These packets are transmitted to the PSA UPF via two N3 Tunnels separately. The PSA UPF eliminates the duplicated packet based on the GTP-U sequence number accordingly. + +NOTE 2: How to realize the sequence number for support of GTP-U duplication over N3/N9 is up to stage 3. + +NOTE 3: For redundant transmission on N3/N9 interfaces, reordering is not required on the receiver side. + +The PSA UPF and NG-RAN may transmit packets via one or both of the tunnels per QoS Flow based on SMF instruction. + +NOTE 4: The AMF selects an SMF supporting redundant transmission based on the requested S-NSSAI and/or DNN. + +During UE mobility, when the UE moves from NG-RAN supporting redundant transmission to NG-RAN not supporting redundant transmission, the SMF may release the QoS Flow which are subject to redundant transmission. + +Figure 5.33.2.2-1 illustrates the case that the redundant transmission is performed only on N3 interface. These packets are transmitted to the NG-RAN via two N3 Tunnels separately. The RAN node and PSA UPF shall support the packet replication and elimination function as described above. + +![Figure 5.33.2.2-1: Redundant transmission with two N3 tunnels between the PSA UPF and a single NG-RAN node. The diagram shows a UE connected to an NG-RAN. The NG-RAN is connected to an AMF via an N2 interface. The AMF is connected to an SMF via an N11 interface. The SMF is connected to a PCF via an N7 interface. The SMF is also connected to a UPF via an N4 interface. The NG-RAN is connected to the UPF via two N3 tunnels, labeled 'N3 Tunnel 1' and 'N3 Tunnel 2'. The UPF is connected to a DN (Data Network) via an N6 interface.](04c7ffb4a475a374f52b88704ecd295f_img.jpg) + +Figure 5.33.2.2-1: Redundant transmission with two N3 tunnels between the PSA UPF and a single NG-RAN node. The diagram shows a UE connected to an NG-RAN. The NG-RAN is connected to an AMF via an N2 interface. The AMF is connected to an SMF via an N11 interface. The SMF is connected to a PCF via an N7 interface. The SMF is also connected to a UPF via an N4 interface. The NG-RAN is connected to the UPF via two N3 tunnels, labeled 'N3 Tunnel 1' and 'N3 Tunnel 2'. The UPF is connected to a DN (Data Network) via an N6 interface. + +**Figure 5.33.2.2-1: Redundant transmission with two N3 tunnels between the PSA UPF and a single NG-RAN node** + +Two Intermediate UPFs (I-UPFs) between the PSA UPF and the NG-RAN may be used to support the redundant transmission based on two N3 and N9 tunnels between a single NG-RAN node and the PSA UPF. The NG-RAN node and PSA UPF shall support the packet replication and elimination function as described above. + +![Figure 5.33.2.2-2: Two N3 and N9 tunnels between NG-RAN and PSA UPF for redundant transmission. The diagram shows a UE connected to an NG-RAN. The NG-RAN is connected to an AMF via an N2 interface. The AMF is connected to an SMF via an N11 interface. The SMF is connected to a PCF via an N7 interface. The SMF is also connected to two Intermediate UPFs (I-UPF1 and I-UPF2) via an N4 interface. The NG-RAN is connected to I-UPF1 via an N3 Tunnel 1 and to I-UPF2 via an N3 Tunnel 2. I-UPF1 is connected to a UPF via an N9 Tunnel 1, and I-UPF2 is connected to the UPF via an N9 Tunnel 2. The UPF is connected to a DN (Data Network) via an N6 interface.](e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg) + +Figure 5.33.2.2-2: Two N3 and N9 tunnels between NG-RAN and PSA UPF for redundant transmission. The diagram shows a UE connected to an NG-RAN. The NG-RAN is connected to an AMF via an N2 interface. The AMF is connected to an SMF via an N11 interface. The SMF is connected to a PCF via an N7 interface. The SMF is also connected to two Intermediate UPFs (I-UPF1 and I-UPF2) via an N4 interface. The NG-RAN is connected to I-UPF1 via an N3 Tunnel 1 and to I-UPF2 via an N3 Tunnel 2. I-UPF1 is connected to a UPF via an N9 Tunnel 1, and I-UPF2 is connected to the UPF via an N9 Tunnel 2. The UPF is connected to a DN (Data Network) via an N6 interface. + +**Figure 5.33.2.2-2: Two N3 and N9 tunnels between NG-RAN and PSA UPF for redundant transmission** + +In figure 5.33.2.2-2, there are two N3 and N9 tunnels between NG-RAN and PSA UPF for the URLLC QoS Flow(s) of the same PDU Session for redundant transmission established during or after a URLLC QoS Flow establishment. In the case of downlink traffic, the PSA UPF duplicates the downlink packet of the QoS Flow from the DN and assigns the same GTP-U sequence number to them. These duplicated packets are transmitted to I-UPF1 and I-UPF2 via N9 Tunnel 1 and N9 Tunnel 2 separately. Each I-UPF forwards the packet with the same GTP-U sequence number which receives from the PSA UPF to NG-RAN via N3 Tunnel 1 and N3 Tunnel 2 respectively. The NG-RAN eliminates the duplicated packet based on the GTP-U sequence number. In the case of uplink traffic, the NG-RAN duplicates the packet of the QoS Flow from the UE and assigns the same GTP-U sequence number to them. These duplicated packets are transmitted to I-UPF1 and I-UPF2 via N3 Tunnel 1 and N3 Tunnel 2 separately. Each I-UPF forwards the packet with + +the same GTP-U sequence number which receives from the NG-RAN to PSA UPF via N9 Tunnel 1 and N9 Tunnel 2 respectively. The PSA UPF eliminates the duplicated packets based on the GTP-U sequence number. + +The I-UPFs inserted on one leg of the redundant paths shall not behave in an UL CL or Branching Point role. + +#### 5.33.2.3 Support for redundant transmission at transport layer + +Redundant transmission can be supported within the 5G System without making any assumption on support for protocols such as IEEE FRER in the application layer (DN only) at the same time it can be supported without requiring redundant GTP-U tunnel over N3. The backhaul provides two disjoint transport paths between UPF and NG-RAN. The redundancy functionality within NG-RAN and UPF make use of the independent paths at transport layer. Support of redundant transmission at transport layer requires no 3GPP protocol impact. + +Following are the required steps: + +- UE establishes the PDU session for URLLC services. Based on DNN, S-NSSAI, knowledge of supporting redundant transmission at transport layer and other factors as described in clause 6.3.3, SMF selects a UPF that supports redundant transmission at transport layer for the PDU session. One N3 GTP-U tunnel is established between UPF and NG-RAN. + +The knowledge of supporting redundant transmission at transport layer can be configured in the SMF, or be configured in UPF and then obtained by the SMF via N4 capability negotiation during N4 Association setup procedure. + +- For DL data transmission, UPF sends the DL packets on N3 GTP-U tunnel. Redundant functionality in the UPF duplicates the DL data on the transport layer. Redundant functionality in the NG-RAN eliminates the received duplicated DL data and sends to NG-RAN. +- For UL data transmission, NG-RAN sends the received UL packets on N3 GTP-U tunnel, the Redundant functionality in the NG-RAN performs the redundant handling on the backhaul transport layer. The Redundant functionality in the UPF eliminates the received duplicated UL data and sends to UPF. + +### 5.33.3 QoS Monitoring for packet delay + +#### 5.33.3.1 General + +QoS Monitoring for packet delay can be applied based on 3rd party application request or PCF policy control or both, e.g. to assist URLLC services. The packet delay between UE and PSA UPF is a combination of the RAN part of UL/DL packet delay as defined in TS 38.314 [120] and UL/DL packet delay between NG-RAN and PSA UPF. The NG-RAN is required to provide the QoS monitoring results on the RAN part of UL/DL packet delay measurement. The measurement of the UL/DL packet delay between NG-RAN and PSA UPF can be performed on different levels of granularities, i.e. per QoS Flow per UE level, or per GTP-U path level, subject to the operators' configuration. + +The PCF generates the authorized QoS Monitoring policy for a service data flow based on the QoS Monitoring request received from the AF (as described in clause 6.1.3.21 of TS 23.503 [45]). The PCF includes the authorized QoS Monitoring policy in the PCC rule and provides it to the SMF. + +When SMF receives the authorized QoS Monitoring policy for packet delay in a PCC rule from the PCF (as described in clause 6.1.3.21 of TS 23.503 [45]), SMF configures the UPF(s) and NG-RAN to perform delay measurements according to the method selected: per QoS Flow per UE QoS measurement (as described in clause 5.33.3.2) or per GTP-U Path measurement (as described in clause 5.33.3.3). The SMF configure the UPF to report the QoS monitoring results for the QoS Flow as described in clause 5.8.2.18 with parameters determined by the SMF based on the authorized QoS Monitoring policy received from the PCF and/or local configuration. + +The UPF reporting behaviour for QoS Monitoring for packet delay of a QoS Flow is the same when per QoS Flow per UE level measurement (described further in clause 5.33.3.2) or when per GTP-U path level measurement (described further in clause 5.33.3.3) is used. + +#### 5.33.3.2 Per QoS Flow per UE QoS Measurement + +SMF may activate the end to end UL/DL packet delay measurement between UE and PSA UPF for a QoS Flow during the PDU Session Establishment or Modification procedure. + +The SMF sends a QoS Monitoring request to the PSA UPF via N4 and NG-RAN via N2 signalling to request the QoS monitoring between PSA UPF and NG-RAN. The QoS Monitoring request may contain monitoring parameters determined by SMF based on the authorized QoS Monitoring policy received from the PCF and/or local configuration. + +The NG-RAN initiates the RAN part of UL/DL packet delay measurement based on the QoS Monitoring request from SMF. NG-RAN reports the RAN part of UL/DL packet delay result to the PSA UPF in the UL data packet or dummy UL packet. + +If the NG-RAN and PSA UPF are time synchronised, the one way packet delay monitoring between NG-RAN and PSA UPF is supported. + +If the NG-RAN and PSA UPF are not time synchronised, it is assumed that the UL packet delay and the DL packet delay between NG-RAN and PSA UPF are the same. + +For both time synchronised and not time synchronised between NG-RAN and PSA UPF, the PSA UPF creates and sends the monitoring packets to the RAN in a measurement frequency, decided by the PSA UPF, taking the Reporting frequency for QoS Monitoring received from the SMF into account: + +- The PSA UPF encapsulates in the GTP-U header with QFI, QoS Monitoring Packet (QMP) indicator (which indicates the packet is used for UL/DL packet delay measurement) and the local time T1 when the PSA UPF sends out the DL monitoring packets. +- The NG-RAN records the local time T1 received in the GTP-U header and the local time T2 at the reception of the DL monitoring packets. +- When receiving an UL packet from UE for that QFI or when the NG-RAN sends a dummy UL packet as monitoring response (in case there is no UL service packet for UL packet delay monitoring), the NG-RAN encapsulates QMP indicator, the RAN part of UL/DL packet delay result, the time T1 received in the GTP-U header, the local time T2 at the reception of the DL monitoring packet and the local time T3 when NG-RAN sends out this monitoring response packet to the UPF via N3 interface, in the GTP-U header of the monitoring response packet. + +NOTE 1: When the NG-RAN sends the dummy UL packet as monitoring response to PSA UPF depends on NG-RAN's implementation. + +- The PSA UPF records the local time T4 when receiving the monitoring response packets and calculates the round trip (if not time synchronized) or UL/DL packet delay (if time synchronized) between NG-RAN and anchor PSA UPF based on the time information contained in the GTP-U header of the received monitoring response packet. If the NG-RAN and PSA UPF are not time synchronised, the PSA UPF calculates the UL/DL packet delay between the NG-RAN and the PSA UPF based on the $(T2-T1+T4-T3)/2$ . If the NG-RAN and PSA UPF are time synchronised, the PSA UPF calculates the UL packet delay and DL packet delay between the NG-RAN and the PSA UPF based on $(T4-T3)$ and $(T2-T1)$ , respectively. The PSA UPF calculates the UL/DL packet delay between UE and PSA UPF based on the received RAN part of UL/DL packet delay result and the calculated UL/DL packet delay between RAN and PSA UPF. + +NOTE 2: If the NG-RAN and PSA UPF are not time synchronised, it can cause inaccurate result of UL/DL packet delay. + +- The PSA UPF reports the QoS Monitoring results as described in clause 5.8.2.18. + +If the redundant transmission on N3/N9 interfaces is activated, the UPF and NG-RAN performs QoS monitoring for both UP paths. The UPF reports the packet delays of the two UP paths independently to the SMF. + +#### 5.33.3.3 GTP-U Path Measurement + +The SMF can request to activate QoS monitoring for the GTP-U path(s) between all UPF(s) and the (R)AN based on locally configured policies. Alternatively, when a QoS monitoring policy is received in a PCC rule and the QoS monitoring is not yet active for the DSCP corresponding to the 5QI in the PCC rule, the SMF activates QoS Monitoring for all UPFs currently in use for this PDU Session and the (R)AN. In this case, the SMF performs the QoS Flow Binding without taking the QoS Monitoring Policy within the PCC rule into account. The SMF sends the QoS monitoring policy to each involved UPF and the (R)AN via N4 interface and via N2 interface respectively. + +NOTE 1: The PCC rule containing a QoS monitoring policy is just a trigger for the SMF to instruct the UPFs to initiate the GTP-U based QoS Monitoring. + +A GTP-U sender performs an estimation of RTT to a GTP-U receiver on a GTP-U path by sending Echo messages and measuring time that elapses between the transmission of Request message and the reception of Response message. A GTP-U sender computes an accumulated packet delay by adding RTT/2, the processing time and, if available, an accumulated packet delay from an upstream GTP-U sender (i.e. an immediately preceding GTP-U sender in user plane path) thus the measured accumulated packet delay represents an estimated elapsed time since a user plane packet entered 3GPP domain. + +It is expected that a GTP-U sender determines RTT periodically in order to detect changes in transport delays. QoS monitoring is performed by a GTP-U end-point (UP function) that receives, stores and executes the QoS monitoring policy as described below for a QoS Flow. QoS monitoring is performed by comparing a measured accumulated packet delay with the stored parameters. If the GTP-U end-point (the PSA UPF, in the case of accumulated packet delay reporting) determines that the packet delay exceeds the value of a stored parameter, then the node triggers QoS monitoring alert signalling to the relevant SMF or to the OA&M function as further described in TS 29.244 [65]. + +NOTE 2: Echo Request message and Echo Response message are sent outside GTP-U tunnels (the messages are using TEID set to 0). If underlying transport is using QoS differentiation (e.g. IP DiffServ) then it is up to the implementation to ensure that the Echo messages are classified correctly and receive similar treatment by the underlying transport as GTP-U GTP-PDUs carrying QoS Flows (user data). + +When QoS Monitoring is used to measure the packet delay for a QoS Flow, the following applies: + +- Packet delay measurement is performed by using GTP-U Echo Request/Response as defined in the TS 28.552 [108], in the corresponding user plane transport path(s), independent of the corresponding PDU Session and the 5QI for a given QoS Flow. +- RAN measures and provides the RAN part of UL/DL packet delay towards UPF (in the GTP-U header of the respective QoS Flow via N3). +- The UPF calculates the UL/DL packet delay by combining the received measurements of RAN part with the measurements of N3/N9 interface (N9 is applicable when I-UPF exists). +- The UPF reports the QoS Monitoring results as described in clause 5.8.2.18. + +QoS Monitoring can also be used to measure the packet delay for transport paths to influence the mapping of QoS Flows to appropriate network instances, DSCP values as follows: + +- SMF activates QoS monitoring for the GTP-U path(s) between all UPF(s) and all (R)AN nodes based on locally configured policies. +- UPF does measurement of network hop delay per transport resources that it will use towards a peer network node identified by an IP destination address (the hop between these two nodes) and port. The network hop measured delay is computed by sending an Echo Request over such transport resource (Ti) and measuring RTT/2 when Echo Response is received. +- UPF maps {network instance, DSCP} into Transport Resource and measures delay per IP destination address and port. Thus, for each IP destination address, the measured delay per (network instance, DSCP) entry is determined. +- The UPF performing the QoS monitoring can provide the corresponding {Network instance, DSCP} along with the measured accumulated packet delay for the corresponding transport path to the SMF. The UPF reports the measurement results to the SMF based on some specific conditions e.g. first time, periodic, event triggered, when thresholds for reporting towards SMF (via N4) are reached. +- Based on this, SMF can determine QoS Flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for the given QoS Flow. + +## 5.34 Support of deployments topologies with specific SMF Service Areas + +### 5.34.1 General + +When the UE is outside of the SMF Service Area, or current SMF cannot serve the target DNAI for the traffic routing for local access to the DN, an I-SMF is inserted between the SMF and the AMF. The I-SMF has a N11 interface with the AMF and a N16a interface with the SMF and is responsible of controlling the UPF(s) that the SMF cannot directly control. The exchange of the SM context and forwarding of tunnel information if needed are done between two SMFs directly without involvement of AMF. + +Depending on scenario, a PDU Session in non-roaming case or local breakout is either served by a single SMF or served by an SMF and an I-SMF. When a PDU Session is served by both an SMF and an I-SMF, the SMF is the NF instance that has the interfaces towards the PCF and CHF. + +In this Release of the specification, deployments topologies with specific SMF Service Areas apply only for 3GPP access. + +The SMF shall release or reject the PDU Session if the DNN of the PDU Session corresponds to a LADN and the I-SMF is inserted to the PDU Session. + +NOTE 1: This implies that operators need to plan the LADN deployment in such a way that the LADN Service area needs to be within the SMF Service Area, but not across SMFs' Service Areas. + +NOTE 2: This is to cover the case where the UE is not in or moves out of SMF Service Area and an I-SMF is inserted to the PDU Session e.g. during PDU Session Establishment, Service Request. If the PDU Session is maintained with I-SMF, the SMF is not able to enforce the LADN Service control, e.g. SMF is not notified in the case of Service Request. + +Independent of whether deployments topologies with specific SMF Service Areas apply, the SMF may trigger the PDU Session re-establishment to the same DN, if the PDU Session is associated with the SSC mode 2 or SSC mode 3. + +NOTE 3: SSC mode 2 or SSC mode 3 can be used to optimize SMF location for a PDU Session and/or, depending on deployment, ensure that the UE is always within the service area of the SMF controlling the PDU Session. In this case (when PDU Session continuity over the PLMN is not required) procedures described in this clause are not needed. + +In this Release, how TSC (as defined in clauses 5.27 and 5.28) is supported for PDU Sessions involving an I-SMF is not specified. + +In this Release, Redundant User Plane Paths as defined in clause 5.33.2.2 is not supported for PDU Sessions involving an I-SMF. + +Redundant PDU sessions support as defined in clause 5.33.2.1 is supported for PDU Sessions involving an I-SMF, when different S-NSSAIs are used for the redundant PDU sessions. + +Redundant User Plane Paths as defined in clause 5.33.2.3 is supported for PDU Sessions involving an I-SMF only if this PDU session is established for a S-NSSAI referring to network instances requiring redundant transmission at transport layer. + +QoS monitoring (as defined in clause 5.33.3) is supported as long as SMF and not I-SMF initiates the QoS monitoring function. + +Dynamic CN PDB provisioning (as defined in clause 5.7.3.4) is supported for PDU Sessions involving an I-SMF. + +In this Release, no dedicated functionality is specified for I-SMF and N16a in order to support NPN. + +### 5.34.2 Architecture + +#### 5.34.2.1 SBA architecture + +In non-roaming case the SBA architecture described in Figure 4.2.3-1 shall apply. In local breakout scenarios the SBA architecture described in Figure 4.2.4-1 shall apply. In Home Routed scenarios the SBA architecture described in Figure 4.2.4-3 shall apply. + +#### 5.34.2.2 Non-roaming architecture + +Figure 5.34.2.2-1 depicts the non-roaming architecture with an I-SMF insertion to the PDU Session without UL-CL/BP, using reference point representation. + +![Diagram of non-roaming architecture with I-SMF insertion to the PDU Session without UL-CL/BP.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +The diagram illustrates the non-roaming architecture with an I-SMF insertion. At the top, the Network Slice Selection Function (NSSF) and the AUSF are connected to the AMF via N22 and N12 interfaces respectively. The AUSF is also connected to the UDM via the N13 interface. The UDM is connected to the AMF via the N8 interface and to the SMF via the N10 interface. The CHF is connected to the SMF via the N40 interface. The AMF is connected to the UE via the N1 interface and to the (R)AN via the N2 interface. The AMF is also connected to the I-SMF via the N11 interface and to the UPF via the N14 interface. The I-SMF is connected to the SMF via the N16a interface and to the UPF via the N4 interface. The SMF is connected to the PCF via the N7 interface and to the UPF via the N4 interface. The PCF is connected to the AF via the N5 interface. The (R)AN is connected to the UPF via the N3 interface. The UPF is connected to the DN via the N6 interface. The UPF is also connected to the I-SMF via the N15 interface. The I-SMF is connected to the SMF via the N38 interface. The UPF is connected to the DN via the N9 interface. + +Diagram of non-roaming architecture with I-SMF insertion to the PDU Session without UL-CL/BP. + +NOTE 1: N16a is the interface between SMF and I-SMF. + +NOTE 2: N38 is the interface between I-SMFs. + +**Figure 5.34.2.2-1: Non-roaming architecture with I-SMF insertion to the PDU Session in reference point representation, with no UL-CL/BP** + +Figure 5.34.2.2-2 depicts the non-roaming architecture for an I-SMF insertion to the PDU Session with UL-CL/BP, using reference point representation. + +![Figure 5.34.2.2-2: Non-roaming architecture with I-SMF insertion to the PDU Session in reference point representation, with UL-CL/BP. The diagram shows network functions and their interfaces. Key components include UE, (R)AN, AMF, I-SMF, SMF, UPF, PCF, AF, DN, NSSF, AUSF, UDM, and CHF. Interfaces are labeled N1 through N40. Specifically, AMF connects to (R)AN via N2, to I-SMF via N11, and to NSSF via N22. I-SMF connects to SMF via N16a and N38. SMF connects to PCF via N7. UPFs are interconnected via N9 and connect to DN via N6. AMF also has connections to AUSF (N12), UDM (N8), and CHF (N15).](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Figure 5.34.2.2-2: Non-roaming architecture with I-SMF insertion to the PDU Session in reference point representation, with UL-CL/BP. The diagram shows network functions and their interfaces. Key components include UE, (R)AN, AMF, I-SMF, SMF, UPF, PCF, AF, DN, NSSF, AUSF, UDM, and CHF. Interfaces are labeled N1 through N40. Specifically, AMF connects to (R)AN via N2, to I-SMF via N11, and to NSSF via N22. I-SMF connects to SMF via N16a and N38. SMF connects to PCF via N7. UPFs are interconnected via N9 and connect to DN via N6. AMF also has connections to AUSF (N12), UDM (N8), and CHF (N15). + +**Figure 5.34.2.2-2: Non-roaming architecture with I-SMF insertion to the PDU Session in reference point representation, with UL-CL/BP** + +#### 5.34.2.3 Roaming architecture + +Figure 5.34.2.3-1 depicts 5G System roaming architecture in the case of local break out scenario where the SMF controlling the UPF connecting to NG-(R)AN is separated from the SMF controlling PDU Session anchor, using the reference point representation. + +![Figure 5.34.2.3-1: Roaming 5G System architecture with SMF/I-SMF - local breakout scenario in reference point representation. The diagram is divided by a dashed line into VPLMN (left) and HPLMN (right). In VPLMN: UE, (R)AN, AMF, NSSF, I-SMF, SMF, vPCF, AF, UPF, and DN. In HPLMN: AUSF, UDM, and hPCF. Key cross-border interfaces include N12 (AMF to AUSF), N8/N10 (AMF/SMF to UDM), N24 (vPCF to hPCF), and N13 (AUSF to UDM). Internal VPLMN interfaces include N1, N2, N3, N4, N6, N7, N9, N11, N15, N16a, N22, and N38.](896e86ed12aff206d302c64f2e3091fa_img.jpg) + +Figure 5.34.2.3-1: Roaming 5G System architecture with SMF/I-SMF - local breakout scenario in reference point representation. The diagram is divided by a dashed line into VPLMN (left) and HPLMN (right). In VPLMN: UE, (R)AN, AMF, NSSF, I-SMF, SMF, vPCF, AF, UPF, and DN. In HPLMN: AUSF, UDM, and hPCF. Key cross-border interfaces include N12 (AMF to AUSF), N8/N10 (AMF/SMF to UDM), N24 (vPCF to hPCF), and N13 (AUSF to UDM). Internal VPLMN interfaces include N1, N2, N3, N4, N6, N7, N9, N11, N15, N16a, N22, and N38. + +**Figure 5.34.2.3-1: Roaming 5G System architecture with SMF/I-SMF - local breakout scenario in reference point representation** + +For the case of home routed scenario, Figure 4.2.4-6 applies. + +### 5.34.3 I-SMF selection, V-SMF reselection + +The AMF is responsible of detecting when to add or to remove an I-SMF or a V-SMF for a PDU Session. For this purpose, the AMF gets from NRF information about the Service Area and supported DNAI(s) of SMF(s). + +During mobility events such as Hand-Over or AMF change, if the service area of the SMF does not include the new UE location, then the AMF selects and inserts an I-SMF which can serve the UE location and the S-NSSAI. Conversely if the AMF detects that an I-SMF is no more needed (as the service area of the SMF includes the new UE location) it removes the I-SMF and interfaces directly with the SMF of the PDU Session. If the AMF detects that the SMF cannot serve the UE location (e.g. due to mobility), then the AMF selects a new I-SMF serving the UE location. If the existing I-SMF (or V-SMF) cannot serve the UE location (e.g. due to mobility) and the service area of the SMF does not include the new UE location (or the PDU Session is Home Routed), then the AMF initiates an I-SMF (or V-SMF) change. A V-SMF change may take place either at intra-PLMN or inter-PLMN mobility. + +According to the PCC rules related with AF influence traffic mechanism regarding DNAI(s), the SMF determines the target DNAI which is applicable to the current UE location and which can be based on the common DNAI (if applicable) as described in TS 23.548 [130]. If current (I-)SMF cannot serve the target DNAI or if the SMF can serve the target DNAI and existing I-SMF is not needed, the SMF may send the target DNAI information to the AMF for triggering I-SMF (re)selection or removal, e.g. the AMF performs I-SMF (re)selection or removal based on the target DNAI and supported DNAI(s) of (I-)SMF. If the SMF determines that target DNAI currently served by I-SMF should not be used for the PDU Session hence the existing I-SMF is not needed (e.g. due to the updated PCC rules removes DNAI(s) that was provided in the previous PCC rules), the SMF sends the target DNAI information without including target DNAI to AMF, which may trigger the I-SMF removal. + +At PDU Session Establishment in non-roaming and roaming with LBO scenarios, if the AMF or SCP cannot select an SMF with a Service Area supporting the current UE location for the selected (DNN, S-NSSAI) and required SMF capabilities, the AMF selects an SMF for the selected (DNN, S-NSSAI) and required capabilities and in addition selects an I-SMF serving the UE location and the S-NSSAI. + +Compared to the SMF selection function defined in clause 6.3.2, the following parameters are not applicable for I-SMF/V-SMF selection: + +- Data Network Name (DNN). +- Subscription information from UDM. + +NOTE 1: All SMF(s) and I-SMF are assumed to be able to control the UPF mapping between EPC bearers and 5GC QoS Flows. + +If HR-SBO roaming is allowed for a PDU Session, the DNN is also considered for V-SMF selection. + +If delegated SMF discovery is used at PDU Session establishment: + +1. The AMF sends Nsmf\_PDUSession\_CreateSMContext Request to SCP and includes the parameters as defined in clause 6.3.2 (e.g. the DNN, required SMF capabilities, UE location) as discovery and selection parameters. If the SCP successfully selects an SMF matching all discovery and selection parameters, the SCP forwards the Nsmf\_PDUSessionCreateSMContext Request to the selected SMF. +2. If the SCP cannot select an SMF matching all discovery and selection parameters, the SCP returns a dedicated error to AMF. In this case the I-SMF also need be discovered. +3. Upon reception of the error from the SCP that an SMF matching all discovery and selection parameters cannot be found, the AMF performs the discovery and selection of the SMF from NRF (thus not providing the UE location as a discovery parameter). The AMF may indicate the maximum number of SMF instances to be returned from NRF, i.e. SMF selection at NRF. +4. The AMF sends Nsmf\_PDUSession\_CreateSMContext Request to SCP, which includes the endpoint (e.g. URI) of the selected SMF and the discovery and selection parameters as defined in clause 6.3.2 except the DNN and the required SMF capabilities, i.e. parameter for I-SMF selection. The SCP performs discovery and selection of the I-SMF and forwards the Nsmf\_PDUSession\_CreateSMContext Request to the selected I-SMF. +5. The I-SMF sends the Nsmf\_PDUSession\_Create Request towards the SMF via the SCP; the I-SMF uses the received endpoint (e.g. URI) of the selected SMF to construct the target destination to be addressed. The SCP forwards the Nsmf\_PDUSession\_Create Request to the SMF. + +6. The SMF answers to the I-SMF that answers to the AMF; in this answer the AMF receives the I-SMF ID. +7. Upon reception of a response from I-SMF, based on the received I-SMF ID, the AMF may obtain the SMF Service Area of the I-SMF from NRF. The AMF uses the SMF Service Area of the I-SMF to determine the need for I-SMF relocation upon subsequent UE mobility. + +If delegated I-SMF discovery is used once the PDU Session establishment has been established, the procedure starts at step 4 above and is further detailed in the messages flows in clause 23 of TS 23.502 [3]. + +If delegated V-SMF discovery is used for V-SMF reselection, clause 6.3.2 applies, but there is no need for discovery and selection of the H-SMF. This is further detailed in the messages flows in clause 23 of TS 23.502 [3]. + +### 5.34.4 Usage of an UL Classifier for a PDU Session controlled by I-SMF + +This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/BP in VPLMN is not supported in HR case. + +When I-SMF is involved for a PDU Session, it is possible that the UL CL controlled by I-SMF is inserted into the data path of the PDU Session. The usage of an ULCL controlled by I-SMF in the data path of a PDU Session is depicted in Figure 5.34.4-1. + +![Figure 5.34.4-1: User plane Architecture for the Uplink Classifier controlled by I-SMF. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an I-SMF via N11. The I-SMF is connected to an SMF via N16a. The SMF is connected to a UPF (PDU session anchor 1) via N4. The UPF (PDU session anchor 1) is connected to a DN via N6. The AN is also connected to a UPF (Uplink Classifier) via N3. The UPF (Uplink Classifier) is connected to the I-SMF via N4. The UPF (Uplink Classifier) is also connected to a UPF (PDU session anchor 2) via N9. The UPF (PDU session anchor 2) is connected to a DN via N6. A dashed line labeled 'Local access to the same DN' connects the two DN blocks.](ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg) + +``` + +graph LR + UE[UE] --- AN[AN] + AN -- N1 --> AMF[AMF] + AN -- N2 --> AMF + AN -- N3 --> UPF_UC[UPF Uplink Classifier] + AMF -- N11 --> ISMF[I-SMF] + ISMF -- N16a --> SMF[SMF] + SMF -- N4 --> UPF_A1[UPF PDU session anchor 1] + UPF_A1 -- N6 --> DN1[DN] + UPF_UC -- N4 --> ISMF + UPF_UC -- N9 --> UPF_A2[UPF PDU session anchor 2] + UPF_A2 -- N6 --> DN2[DN] + DN1 -.-> DN2 + subgraph Local_access [Local access to the same DN] + DN1 + DN2 + end + +``` + +Figure 5.34.4-1: User plane Architecture for the Uplink Classifier controlled by I-SMF. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an I-SMF via N11. The I-SMF is connected to an SMF via N16a. The SMF is connected to a UPF (PDU session anchor 1) via N4. The UPF (PDU session anchor 1) is connected to a DN via N6. The AN is also connected to a UPF (Uplink Classifier) via N3. The UPF (Uplink Classifier) is connected to the I-SMF via N4. The UPF (Uplink Classifier) is also connected to a UPF (PDU session anchor 2) via N9. The UPF (PDU session anchor 2) is connected to a DN via N6. A dashed line labeled 'Local access to the same DN' connects the two DN blocks. + +**Figure 5.34.4-1: User plane Architecture for the Uplink Classifier controlled by I-SMF** + +The I-SMF determines whether UL CL will be inserted based on information received from SMF, and the I-SMF selects the UPFs acting as UL CL and/or PDU Session Anchor providing local access to the Data Network. + +### 5.34.5 Usage of IPv6 multi-homing for a PDU Session controlled by I-SMF + +This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/BP in VPLMN is not supported in HR case. + +When I-SMF is involved for a PDU Session, it is possible that the BP controlled by I-SMF is inserted into the data path of the PDU Session. The usage of a BP controlled by I-SMF in the data path of a PDU Session is depicted in Figure 5.34.5-1. + +![Figure 5.34.5-1: Multi-homed PDU Session: Branching Point controlled by I-SMF. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an I-SMF via N11. The I-SMF is connected to an SMF via N16a. The SMF is connected to a UPF (PDU session anchor 1) via N4. The UPF (PDU session anchor 1) is connected to a DN via N6. The I-SMF is also connected to a UPF (Branching Point) via N4. The UPF (Branching Point) is connected to the AN via N3 and to a UPF (PDU session anchor 2) via N9. The UPF (PDU session anchor 2) is connected to a DN via N6. The UE is also connected to the UPF (Branching Point) via N1. The AN is also connected to the UPF (Branching Point) via N2. The I-SMF is also connected to the UPF (PDU session anchor 2) via N9. A dashed line labeled 'Local access to the same DN' connects the two DN blocks.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +graph LR + UE[UE] -- N1 --> AMF[AMF] + AN[AN] -- N2 --> AMF + AN -- N3 --> UPF_BP[UPF Branching Point] + AMF -- N11 --> ISMF[I-SMF] + ISMF -- N4 --> UPF_BP + ISMF -- N16a --> SMF[SMF] + SMF -- N4 --> UPF_A1[UPF PDU session anchor 1] + UPF_A1 -- N6 --> DN1[DN] + UPF_BP -- N9 --> UPF_A2[UPF PDU session anchor 2] + UPF_A2 -- N6 --> DN2[DN] + UPF_A2 -- N9 --> UPF_BP + UE -.-> UPF_BP + AN -.-> UPF_BP + ISMF -.-> UPF_A2 + DN1 -.-> DN2 + subgraph Local access to the same DN + DN1 + DN2 + end + +``` + +Figure 5.34.5-1: Multi-homed PDU Session: Branching Point controlled by I-SMF. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an I-SMF via N11. The I-SMF is connected to an SMF via N16a. The SMF is connected to a UPF (PDU session anchor 1) via N4. The UPF (PDU session anchor 1) is connected to a DN via N6. The I-SMF is also connected to a UPF (Branching Point) via N4. The UPF (Branching Point) is connected to the AN via N3 and to a UPF (PDU session anchor 2) via N9. The UPF (PDU session anchor 2) is connected to a DN via N6. The UE is also connected to the UPF (Branching Point) via N1. The AN is also connected to the UPF (Branching Point) via N2. The I-SMF is also connected to the UPF (PDU session anchor 2) via N9. A dashed line labeled 'Local access to the same DN' connects the two DN blocks. + +**Figure 5.34.5-1: Multi-homed PDU Session: Branching Point controlled by I-SMF** + +The I-SMF determines whether BP will be inserted based on information received from SMF, and the I-SMF selects the UPFs acting as BP and/or PDU Session Anchor providing local access to the Data Network. + +### 5.34.6 Interaction between I-SMF and SMF for the support of traffic offload by UPF controlled by the I-SMF + +#### 5.34.6.1 General + +This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/Branching Point in VPLMN is not supported in HR case. It applies for the architectures described in clauses 5.34.4 and 5.34.5 + +When the I-SMF is inserted into a PDU Session, e.g. during PDU Session establishment or due to UE mobility, the I-SMF may provide the DNAI list it supports to the SMF. Based on the DNAI list information received from I-SMF, the SMF may provide the DNAI(s) of interest for this PDU Session for local traffic steering to the I-SMF e.g. immediately or when a new or updated or removed PCC rule(s) is/are received. The DNAI(s) of interest is derived from PCC rules. + +The I-SMF is responsible for the insertion, modification and removal of UPF(s) to ensure local traffic steering. The SMF does not need to have access to local configuration or NRF output related with UPF(s) controlled by I-SMF. Based on the DNAI(s) of interest for this PDU Session for local traffic steering and UE location the I-SMF determines which DNAI(s) are to be selected, selects UPF(s) acting as UL CL/BP and/or PDU Session Anchor based on selected DNAI, and insert these UPF(s) into the data path of the PDU Session. + +When a UL CL/BP has been inserted, changed or removed, the I-SMF indicates to the SMF that traffic offload have been inserted, updated or removed for a DNAI, providing also the IPv6 prefix that has been allocated if a new IPv6 prefix has been allocated for the PDU Session. + +From now on the SMF and I-SMF interactions entail: + +- Notifying the SMF with the new Prefix (multi-Homing case): the SMF is responsible of issuing Router Advertisement message. The SMF constructs a link-local address as the source IP address. The Router Advertisement message includes the IPv6 multi-homed routing rules provided to the UE to select the source IPv6 prefix among the prefixes related with the PDU Session according to RFC 4191 [8]. The SMF sends the Router Advertisement message to the UE via the PSA UPF controlled by the SMF. +- N4 interactions related with traffic offloading. The SMF provide N4 information to the I-SMF for how the traffic shall be detected, enforced, monitored in UPF(s) controlled by the I-SMF: the SMF issues requests to the I-SMF containing N4 information to be used for creating / updating /removing PDR, FAR, QER, URR, etc. The N4 information for local traffic offload provided by the SMF to the I-SMF are described in clause 5.34.6.2. +- Receiving N4 notifications related with traffic usage reporting: the I-SMF forwards to the SMF N4 information corresponding to UPF notifications related with traffic usage reporting; the SMF aggregates and constructs usage reports towards PCF/CHF. + +NOTE: How the SMF decides what traffic steering and enforcement actions are enforced in UPF(s) controlled by I-SMF is left for implementation. + +The I-SMF is responsible of the N4 interface towards the local UPF(s) including: + +- the usage of AN Tunnel Info received from the 5G AN via the AMF in order to build PDR and FAR; +- requesting the allocation of the CN Tunnel Info between local UPFs (if needed); +- to control UPF actions when the UP of the PDU Session becomes INACTIVE. +- provide Trace Requirements on the N4 interface towards the UPF(s) it is controlling, using Trace Requirements received from AMF. + +#### 5.34.6.2 N4 information sent from SMF to I-SMF for local traffic offload + +The SMF generates N4 information for local traffic offload based on the available DNAI(s) indicated by the I-SMF, PCC rules associated with these DNAI(s) and charging requirement. This N4 information is sent from the SMF to the I-SMF after UL CL/Branching Point insertion/update/removal, and the I-SMF uses this N4 information to derive rules installed in the UPFs controlled by the I-SMF. + +The N4 information for local traffic offload corresponds to rules and parameters defined in clause 5.8.5, i.e. PDR, FAR, URR and QER. It contains identifiers allowing the SMF to later modify or delete these rules. + +N4 information for local traffic offload is generated by the SMF without knowledge of how many local UPF(s) are actually used by the I-SMF. The SMF indicates whether a rule within N4 information is enforced in UL CL/ Branching Point or local PSA. If the rule is applied to the local PSA, the N4 information includes the associated DNAI. The I-SMF generates suitable rules for the UPF(s) based on the N4 information received from SMF. + +NOTE: The SMF is not aware of whether there is a single PSA or multiple PSA controlled by I-SMF. + +The following parameters are managed by the I-SMF: + +- The 5G AN Tunnel Info. +- CN tunnel info between local UPFs. +- Network instance (if needed). + +The N4 information exchanged between I-SMF and SMF are not associated with a N4 Session ID but are associated with an N16a association allowing the SMF to modify or delete the N4 information at a later stage. + +The I-SMF generates an N4 Session ID and for each rule a Rule ID (unless the ones received from the SMF can be used) and maintains a mapping between the locally generated identifiers and the ones received from the SMF. The I-SMF replaces those IDs in the PDR(s), QER(s), URR(s) and FAR(s) received from the SMF. When the I-SMF receives the N4 information, the Network instance (if needed) included in the rules sent to the UPF is generated by I-SMF. + +### 5.34.7 Event Management + +#### 5.34.7.1 UE's Mobility Event Management + +When an I-SMF is involved in a PDU Session, the SMF and I-SMF independently subscribe to "UE mobility event notification" service provided by AMF. The AMF treats the SMF's and I-SMF's subscription separately and notifies the event directly to the SMF or I-SMF. If the SMF does not know the serving AMF address, the SMF gets the serving AMF address from the UDM as described in clause 5.2.3.2.4, TS 23.502 [3] and subscribes directly with the serving AMF. + +In the case of AMF change (e.g. Inter NG-RAN node N2 based handover), the target AMF receives mobility event subscription information from the source AMF and updates the mobility event subscription information with the SMF and I-SMF independently (i.e. target AMF allocates the Subscription Correlation ID for each event and notifies the respective SMFs and I-SMF as described in clause 5.3.4.4). + +In the case of I-SMF change or I-SMF insertion (e.g. at Inter NG-RAN node N2 based handover), the subscription of mobility event (from AMF) is not transferred from the old I-SMF or SMF to the new I-SMF, the new I-SMF triggers a + +new subscription event if the new I-SMF wants to receive the corresponding mobility event. In the case of I-SMF removal, the subscription of mobility event at the AMF is not transferred from the old I-SMF to the SMF, the SMF triggers a new subscription event if the SMF wants to receive the corresponding mobility event. + +The subscription from the old SMF entity (old I-SMF, SMF) is removed via an explicitly request from this old SMF entity. + +#### 5.34.7.2 SMF event exposure service + +Consumers of SMF events do not need to be aware of the insertion / removal / change of an I-SMF as they always subscribe to the SMF of the PDU Session. + +Except for the events documented in the present clause, the I-SMF does not need to support the events defined in clause 5.2.8.3.1 of TS 23.502 [3]. + +For Events "First downlink packet per source of the downlink IP traffic (buffered / discarded / transmitted)", when an I-SMF is involved in the PDU Session, the SMF subscribes / unsubscribes onto I-SMF for the PDU Session ID on behalf of the event consumer (e.g. at I-SMF insertion or when a consumer subscribes or un subscribes while an I-SMF serves the PDU Session) and the I-SMF directly notifies the event consumer. At I-SMF change, the related SMF event subscriptions are not transferred from source I-SMF to the target I-SMF. The SMF may trigger new subscription event to the target I-SMF if the SMF wants to receive the corresponding SMF event. At I-SMF change or removal the corresponding subscription is removed in the source I-SMF when it removes the context associated with the PDU Session Id. + +#### 5.34.7.3 AMF implicit subscription about events related with the PDU Session + +When creating an association with a SMF or I-SMF for a PDU Session, the AMF implicitly subscribes to SMF / I-SMF about events related with the PDU Session (the AMF provides the relevant notification information to the SMF or the I-SMF respectively). This implicit subscription is implicitly released when the corresponding association with the SMF / I-SMF is removed (e.g. as no more needed due to a I-SMF insertion / change / removal). + +### 5.34.8 Support for Cellular IoT + +This clause defines the specific impacts of deployments topologies with specific SMF Service Areas on how 5GS supports Cellular IoT as defined in clause 5.31. + +For a PDU Session supporting Control Plane CIoT 5GS Optimisation as defined in clause 5.31.4: + +- For a PDU session towards a DNN/S-NSSAI for which the subscription includes a NEF Identity for NIDD (i.e. for a PDU session which will be anchored in NEF), the AMF never inserts an I-SMF. + +When an I-SMF is inserted to serve a PDU Session, the I-SMF supports the features that, as specified in clause 5.31, apply to the V-SMF in the case of Home Routed. + +NOTE: This can require the SMF to subscribe onto I-SMF about RAT type change for a PDU Session as described in clause 4.23 of TS 23.502 [3]. + +### 5.34.9 Support of the Deployment Topologies with specific SMF Service Areas feature within and between PLMN(s) + +When Deployments Topologies with specific SMF Service Areas need to be used in a PLMN for a S-NSSAI, all AMF serving this S-NSSAI are configured to support Deployments Topologies with specific SMF Service Areas. + +NOTE 1: The specifications do not support AMF selection related with Deployment Topologies with specific SMF Service Areas. + +For HR roaming, the AMF discovers at PDU Session establishment whether a H-SMF supports V-SMF change based on feature support indication received from the NRF, possibly via the SCP. When the V-PLMN requires Deployments Topologies with specific SMF Service Areas but no H-SMF can be selected that supports V-SMF change, a H-SMF not supporting V-SMF change may be selected by the VPLMN. In that case, and if a V-SMF serving the full VPLMN is available, AMF should prefer to select such V-SMF. + +In this release of the specifications, when an AMF detects the need to change the V-SMF while the H-SMF does not support V-SMF change, the AMF shall not trigger V-SMF change but shall trigger the release of the PDU Session. + +NOTE 2: The AMF can determine whether the H-SMF supports V-SMF change based on NRF look up. + +### 5.34.10 Support for 5G LAN-type service + +This clause defines how 5GS supports 5G LAN-type service as defined in clause 5.29 in the case of deployments topologies with specific SMF Service Areas. + +The UE may be connected with the PSA via an I-UPF which is controlled by the I-SMF. In this case, traffic switching (e.g. UPF local traffic switching) is controlled by the SMF as described in clause 5.29.4 without any specific knowledge or involvement of the I-SMF to support the 5G LAN-type service. + +## 5.35 Support for Integrated access and backhaul (IAB) + +### 5.35.1 IAB architecture and functional entities + +Integrated access and backhaul (IAB) enables wireless in-band and out-of-band relaying of NR Uu access traffic via NR Uu backhaul links. In this Release of the specification, NR satellite access is not applicable. The serving PLMN may provide the mobility restriction for NR satellite access as specified in clause 5.3.4.1 + +The Uu backhaul links can exist between the IAB-node and: + +- a gNB referred to as IAB-donor; or +- another IAB-node. + +The part of the IAB node that supports the Uu interface towards the IAB-donor or another parent IAB-node (and thus manages the backhaul connectivity with either PLMN or SNPN it is registered with) is referred to as an IAB-UE. + +In this Release of the specification, the IAB-UE function does not apply to the NR RedCap UE. + +At high level, IAB has the following characteristics: + +- IAB uses the CU/DU architecture defined in TS 38.401 [42], and the IAB operation via F1 (between IAB-donor and IAB-node) is invisible to the 5GC; +- IAB performs relaying at layer-2, and therefore does not require a local UPF; +- IAB supports multi-hop backhauling; +- IAB supports dynamic topology update, i.e. the IAB-node can change the parent node, e.g. another IAB-node, or the IAB-donor, during operation, for example in response to backhaul link failure or blockage. + +Figure 5.35.1-1 shows the IAB reference architecture with two backhaul hops, when connected to 5GC. + +![Diagram of IAB architecture for 5GS. At the top is the 5GC. Below it, an NG-RAN contains a gNB and an IAB-donor gNB. The gNB is connected to the 5GC via an NG (N2, N3) interface and to the IAB-donor gNB via an Xn interface. The IAB-donor gNB contains an IAB-donor-CU and an IAB-donor-DU, connected by an F1 interface. The IAB-donor-CU is connected to the 5GC via another NG (N2, N3) interface. The IAB-donor-DU is connected to an IAB-node via an NR Uu interface, which is also an F1 interface. This IAB-node contains an IAB-UE and a gNB-DU. The IAB-UE is connected to the IAB-donor-CU via an F1 interface. The gNB-DU is connected to another IAB-node via an NR Uu interface, which is also an F1 interface. This second IAB-node also contains an IAB-UE and a gNB-DU. The IAB-UE is connected to the IAB-donor-CU via an F1 interface. The gNB-DU is connected to three UEs via NR Uu interfaces. The IAB-UEs are connected to the 5GC via the IAB-donor gNB.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Diagram of IAB architecture for 5GS. At the top is the 5GC. Below it, an NG-RAN contains a gNB and an IAB-donor gNB. The gNB is connected to the 5GC via an NG (N2, N3) interface and to the IAB-donor gNB via an Xn interface. The IAB-donor gNB contains an IAB-donor-CU and an IAB-donor-DU, connected by an F1 interface. The IAB-donor-CU is connected to the 5GC via another NG (N2, N3) interface. The IAB-donor-DU is connected to an IAB-node via an NR Uu interface, which is also an F1 interface. This IAB-node contains an IAB-UE and a gNB-DU. The IAB-UE is connected to the IAB-donor-CU via an F1 interface. The gNB-DU is connected to another IAB-node via an NR Uu interface, which is also an F1 interface. This second IAB-node also contains an IAB-UE and a gNB-DU. The IAB-UE is connected to the IAB-donor-CU via an F1 interface. The gNB-DU is connected to three UEs via NR Uu interfaces. The IAB-UEs are connected to the 5GC via the IAB-donor gNB. + +**Figure 5.35.1-1: IAB architecture for 5GS** + +The gNB-DU in the IAB-node is responsible for providing NR Uu access to UEs and child IAB-nodes. The corresponding gNB-CU function resides on the IAB-donor gNB, which controls IAB-node gNB-DU via the F1 interface. IAB-node appears as a normal gNB to UEs and other IAB-nodes and allows them to connect to the 5GC. + +The IAB-UE function behaves as a UE, and reuses UE procedures to connect to: + +- the gNB-DU on a parent IAB-node or IAB-donor for access and backhauling; +- the gNB-CU on the IAB-donor via RRC for control of the access and backhaul link; +- 5GC, e.g. AMF, via NAS; +- OAM system via a PDU session or PDN connection (based on implementation). + +**NOTE:** The 5GC, e.g. SMF, may detect that a PDU session for the IAB-UE is for the OAM system access, e.g. by checking the DNN and/or configuration. It is up to the operator configuration to choose whether to use 1 or multiple QoS Flows for OAM traffic and the appropriate QoS parameters, e.g. using 5QI=6 for software downloading, and 5QI=80 with signalled higher priority or a pre-configured 5QI for alarm or control traffic. + +The IAB-UE can connect to 5GC over NR (SA mode) or connect to EPC (EN-DC mode). The UE served by the IAB-node can operate in the same or different modes than the IAB-node as defined in TS 38.401 [42]. The operation mode with both UE and IAB-node connected to EPC is covered in TS 23.401 [26]. Operation modes with UE and IAB-node connected to different core networks are described in clause 5.35.6. + +### 5.35.2 5G System enhancements to support IAB + +In IAB operation, the IAB-UE interacts with the 5GC using procedures defined for UE. The IAB-node gNB-DU only interacts with the IAB-donor-CU and follows the CU/DU design defined in TS 38.401 [42]. + +For the IAB-UE operation, the existing UE authentication methods as defined in TS 33.501 [29] applies. Both USIM based methods and EAP based methods are allowed, and NAI based SUPIs can be used. + +The following aspects are enhanced to support the IAB operation in the Registration procedure as defined in clause 4.2.2.2 of TS 23.502 [3]: + +- The IAB-node provides an IAB-indication to the IAB-donor-CU when the RRC connection is established as defined in TS 38.331 [28]. When the IAB-indication is received, the IAB-donor-CU selects an AMF that supports IAB and includes the IAB-indication in the N2 INITIAL UE MESSAGE as defined in TS 38.413 [34] so that the AMF can perform IAB authorization; +- the UE Subscription data as defined in clause 5.2.3 of TS 23.502 [3] is enhanced to include the authorization information for the IAB operation; +- Authorization procedure during the UE Registration procedure is enhanced to perform verification of IAB subscription information; +- If the IAB operation is not authorized and IAB-UE is not allowed to be registered, the AMF rejects the IAB-UE's registration or de-register the IAB-UE. The AMF initiates UE Context setup/modification procedure by providing IAB authorized indication with the value set to "not authorized" to the NG-RAN, if the IAB-UE is still allowed to be registered; +- If the IAB operation is authorized, UE Context setup/modification procedure is enhanced to provide IAB authorized indication with the value set to "authorized" to NG-RAN. + +After registered to the 5G system, the IAB-node remains in CM-CONNECTED state if the IAB operation is authorized. In the case of radio link failure, the IAB-UE uses existing UE procedure to restore the connection with the network. The IAB-UE uses Deregistration Procedure as defined in clause 4.2.2.3 of TS 23.502 [3] to disconnect from the network. In the case of controlled IAB-node release as specified in clause 8.9.10 of TS 38.401 [42] (including the case when authorization state of the IAB-node is changed from authorized to non-authorized), after UE Context Modification message to NG-RAN with authorization indication as not authorized and after a certain period (e.g. based on the expiration of a timer configured on the AMF), the AMF may trigger the IAB-UE Deregistration. + +### 5.35.3 Data handling and QoS support with IAB + +Control plane and user plane protocol stacks for IAB operation are defined in TS 38.300 [27]. + +QoS management for IAB can remain transparent to the 5GC. If NG-RAN cannot meet a QoS requirement for a QoS Flow to IAB-related resource constraints, the NG-RAN can reject the request using procedures defined in TS 23.502 [3]. + +The IAB-UE function can establish a PDU session or PDN connection, e.g. for OAM purpose (protocol stack not shown here). In that case, the IAB-UE obtains an IP address/prefix from the core network using normal UE procedures. The IAB-UE's IP address is different from that of the IAB-node's gNB DU IP address. + +NOTE: For OAM traffic, based on their specific requirements, operators can select QoS characteristics and reference them by operator specific 5QI(s) or using signalled QoS characteristics within the operator's network. + +### 5.35.4 Mobility support with IAB + +For UEs, all existing NR intra-RAT mobility and dual-connectivity procedures are supported when the UE is served by an IAB-node except for the cases of NR satellite access. For a UE served by an IAB-node when the serving IAB-node changes its IAB-donor-CU due to mobility, the mobility support is specified in clause 5.35A.1 and clause 5.35A.3. + +### 5.35.5 Charging support with IAB + +IAB-donor has all the information regarding the UE and the IAB-node and corresponding mapping of the bearers. The PDU sessions for the UE and IAB-node are separate from IAB-node onwards to the core network. Therefore, the existing charging mechanism as defined in clause 5.12 can be used to support IAB. + +### 5.35.6 IAB operation involving EPC + +When the IAB-donor gNB has connection to both EPC and 5GC, based on PLMN configuration, there are two possible operation modes: + +- the IAB-node connects to a 5GC via the IAB-donor gNB, while the UEs served by the IAB-node connect to EPC with Dual Connectivity as defined in TS 37.340 [31]. In this operation mode, the IAB-donor gNB has connection to an eNB, and the 5GC is restricted for IAB-node access only; and +- the IAB-node connects to an EPC via the IAB-donor gNB with Dual Connectivity as defined in TS 37.340 [31], while the UEs served by the IAB-node connect to the 5GC. In this operation mode, the EPC is restricted for IAB-node access only. + +To support the above operation modes, the IAB-UE shall be configured to select only a specific PLMN (as defined in TS 23.122 [17]) and whether it needs to connect to 5GC or EPC. + +NOTE: For a particular PLMN, it is expected that only one of the modes would be deployed in a known region. + +## 5.35A Support for Mobile Base Station Relay (MBSR) + +### 5.35A.1 General + +The MBSR uses the IAB architecture as defined in clause 5.35, and operates as an IAB node (with an IAB-UE and gNB-DU) with mobility when integrated with the serving PLMN. The architecture described in clause 5.35 applies unless specific handling is specified in clause 5.35A. Additionally, the following limitations apply to the MBSR: + +- the MBSR has a single hop to the IAB-donor node; +- NR Uu is used for the radio link between a MBSR and served UEs, and between MBSR and IAB-donor node. + +Regulatory requirements (e.g. emergency services, priority services) are supported when UEs access 5GS via a MBSR. LCS framework as defined in TS 23.273 [87] is used for providing the location service to the served UEs, with additional enhancements described in clause 5.35A.5. + +Roaming of the MBSR is supported, i.e. a MBSR can integrated with a VPLMN's IAB-donor node. The corresponding enhancements to support MBSR roaming are described in clause 5.35A.4. + +CAG mechanism as defined in clause 5.30 can be used for the control of UE's access to the MBSR. Optional enhancements to the CAG mechanism for MBSR use are described in clause 5.35A.6. + +For a MBSR node to operate as a MBSR, it provides a mobile IAB-indication to the IAB-donor-CU when the RRC connection is established as defined in TS 38.331 [28]. When the mobile IAB-indication is received, the IAB-donor-CU selects an AMF that supports mobile IAB-node and includes the mobile IAB-indication in the N2 INITIAL UE MESSAGE as defined in TS 38.413 [34] so that the AMF can perform MBSR authorization as described in clause 5.35A.4. If the MBSR node is not authorized, e.g. due to the MBSR authorization indication from AMF, it also provides the mobile IAB-indication when establishing new RRC connection so that the AMF supporting mobile IAB-node will be selected by the IAB-donor-CU, to ensure that the operation related to MBSR authorization status change for a registered MBSR node can be performed as described in clause 5.35A.4. If the MBSR receives MBSR authorized indication from AMF, it provides the information about the authorization result to its IAB-DU component based on non-standardized interface as described in clause 5.35A.4. + +After the IAB-UE performs registration procedure in 5GS, further mobility procedure can be performed to change the IAB-donor-DU, the IAB-donor-CU as specified in TS 38.401 [42]. The mobility support of UEs served by the MBSR is specified in clause 5.35A.3 + +### 5.35A.2 Configuration of the MBSR + +In order for an MBSR to operate as a mobile IAB node, it receives configuration from the OAM system of the serving PLMN as specified in TS 38.401 [42]. The MBSR IAB-UE establishes a secure and trusted connection to the OAM server only if it is authorized to operate as MBSR in the serving PLMN as defined in TS 38.401 [42]. + +In addition, the MBSR(IAB-UE) is assumed to be configured with preferred PLMN lists and forbidden PLMNs by the HPLMN to perform PLMN selection as specified in TS 23.122 [17]. + +When a PDU session is used for the MBSR to access the OAM server, the MBSR establishes a dedicated PDU session for the OAM traffic. The serving PLMN provides an Allowed NSSAI and establishes the PDU session for the OAM server access, considering the S-NSSAI and DNN requested by MBSR and/or the default values in subscription data. + +The MBSR can be (pre-)configured with UE policy or provisioned using existing UE Policy mechanism as defined in TS 23.503 [45] including the OAM access PDU session parameters for the authorized PLMNs. + +### 5.35A.3 Mobility support of UEs served by MBSR + +#### 5.35A.3.1 UE mobility between a fixed cell and MBSR cell + +The procedure of Inter-gNB-DU Mobility as defined in TS 38.401 [42] or the handover procedure using the Xn/N2 reference points as defined in TS 23.502 [3] can be used. + +For UEs in RRC\_IDLE and RRC\_INACTIVE state when a MBSR goes out-of-service, procedure for cell (re-)selection as specified in TS 38.304 [50] for RRC\_IDLE and RRC\_INACTIVE is used. + +For UEs in RRC\_CONNECTED state, if the MBSR goes out-of-service due to e.g. MBSR moves to an area where the MBSR is not allowed to provide the relay service, the procedure for IAB node release as specified in TS 38.401 [42] is used. + +The IAB-donor-CU triggers handover procedure when it is possible for the UEs accessing emergency service and being served by the MBSR, if MBSR is about to become unavailable to provide the services. + +#### 5.35A.3.2 UE mobility between MBSR cells + +Similar to the behaviours described in clause 5.35A.3.1, UEs use existing procedures defined in TS 38.401 [42], TS 23.502 [3], or TS 38.304 [50] to handle the mobility between MBSR cells. + +#### 5.35A.3.3 UE mobility when moving together with a MBSR cell + +The TAC broadcasted by the MBSR cell(s) can be configured by the OAM or donor-CU. When MBSR moves to a serving cell with a different TAC, the TAC to be broadcasted by the MBSR may also change. + +For a UE served by a MBSR cell, it may observe change of TAC and/or cell IDs, even if it is still connected to the same MBSR. This can trigger mobility registrations, as defined in TS 23.502 [3], if the new TAC is not in the TAI list in the RA. + +### 5.35A.4 MBSR authorization + +For a MBSR, the subscription information stored in the HPLMN indicates whether it is authorized to operate as MBSR, and the corresponding location and time information as specified in TS 23.502 [3]. + +NOTE 1: For non-roaming MBSRs, the operator local policy can be taken into consideration for MBSR authorization, e.g. based on the network status, or a limit on the number of MBSRs operating in a certain area. + +When the MBSR (IAB-UE) performs initial registration with the serving PLMN, it indicates the request to operate as a MBSR as described in clause 5.35A.1. The AMF authorizes the MBSR based on the subscription information, and provides MBSR authorized indication to the MBSR node over NAS and NG-RAN over NGAP as described in the registration procedure in TS 23.502 [3]. The MBSR establishes the connection to OAM system using the configuration information for MBSR operation upon the reception of MBSR authorization indication (authorized). The MBSR provides the information about the authorization result (authorized) to its IAB-DU component. When the AMF formulates the registration area for an authorized MBSR, the TAs included in the registration area are authorized for MBSR operation homogeneously, taking any MBSR Operation allowed information in subscription data and operator local policy into account. + +NOTE 2: The MBSR support can be deployed in certain Network Slices based on operator configuration and Network slicing functionalities (e.g. the function specified in clause 5.15.18) can be applied when suitable. + +When MBSR roaming is supported, a roaming agreement between VPLMN and HPLMN regarding MBSR operation is in place. The AMF can make use of the subscription data for authorization of the MBSR in the V-PLMN. + +MBSR (IAB-DU) can use IAB-node integration procedure or inter-IAB-donor gNB mobility procedure to integrate into the serving PLMN to provide service. + +NOTE 3: How the MBSR obtains the configuration information for MBSR operation is described in clause 5.35A.2. + +If the MBSR operation is not authorized (e.g. due to location or time limitation), the AMF of the MBSR can indicate to the MBSR IAB-UE that it is not allowed to act as an MBSR, i.e. the MBSR authorization indication (not authorized), as part of registration procedure. The AMF may provide the indication in a Registration Accept (if the PLMN allows the MBSR IAB-UE to be registered in the PLMN). In this case, the AMF includes the MBSR authorization indication (not authorized) to donor-gNB. The MBSR provides the information about the authorization result (not authorized) to its IAB-DU component. The AMF may reject the Registration (if the PLMN does not allow the MBSR IAB-UE to be registered in the PLMN). + +**Editor's note: The details of the additional information and corresponding MBSR behaviour will be added.** + +When the MBSR authorization state changes for a registered MBSR node (either authorized, or not authorized), the AMF updates the MBSR and the NG-RAN accordingly. Based on the operator configuration, the AMF may use either Deregistration (with re-registration required indication) or the UE Configuration Update procedure to inform the MBSR regarding the updated authorization status: + +- When Deregistration (with re-registration required indication) procedure is used, AMF provides the new authorization indication to MBSR (IAB-UE) as described above, when the MBSR performs initial Registration procedure after the deregistration. +- When UE Configuration Update procedure is used, the AMF provides the new authorization indication and additional information to the MBSR in the UE Configuration Update Command. The MBSR provides the information about the new authorization status to its IAB-DU component. + +The AMF informs the NG-RAN of the new authorization status using UE Context Modification, Initial Context Setup procedure or the DOWNLINK NAS TRANSPORT message, with the following principles: + +- If the authorization state changes from authorized to not authorized and AMF uses the UE Configuration Update procedure to update the MBSR, the AMF updates the NG-RAN with the new authorization indication (not authorized) by including this information in the DOWNLINK NAS TRANSPORT message. The NG-RAN completes handover of the UEs served by the MBSR before releasing the F1 connection to the MBSR IAB-DU. +- If the authorization state changes from authorized to not authorized and the AMF uses the Deregistration procedure to update the MBSR, the AMF sends the UE Context Modification message to NG-RAN and after a certain period (e.g. based on the expiration of a timer configured on the AMF) the AMF executes the deregistration procedure with MBSR and releases the NAS signalling connection. + +If the Network-initiated Deregistration procedure is triggered for MBSR IAB-UE that is registered with authorization to act as MBSR, the AMF sends the UE Context Modification message to NG-RAN and updates the NG-RAN with the authorization indication as not authorized and after a certain period (e.g. based on the expiration of a timer configured on the AMF) the AMF executes the deregistration procedure with MBSR and releases the NAS signalling connection. + +NOTE 4: The AMF delays the MBSR de-registration to allow the IAB-donor gNB to move all connected UEs via MBSR to other cells as specified in clause 8.9.10 of TS 38.401 [42]. + +If a PDU session is used to provide OAM access for MBSR when it is not authorized but remains registered, the AMF may notify the SMF serving the PDU session for O&M access to trigger the release of the PDU Session. + +NOTE 5: The mechanism applies to both roaming and non-roaming MBSR operations. + +### 5.35A.5 Location Service Support of UEs served by MBSR + +When a UE accesses 5GS via a MBSR, it can use the location service as defined in TS 23.273 [87]. However, in order to provide accurate estimation of the UE location, LMF needs to take the location of the MBSR into account. Enhancements to the LCS framework for MBSR support is described in clause 5.9 of TS 23.273 [87]. + +### 5.35A.6 Providing cell ID/TAC of MBSR for services + +The TAC and cell ID broadcasted by the MBSR cell(s) are configured as specified in TS 38.470 [165]. + +After the MBSR is authorized as defined in 5.35A.4, when a UE is served by a cell of this MBSR, the IAB-donor-CU may provide 'Additional ULI' in addition to User Location Information, in N2 messages. The 'Additional ULI' is the ULI of the IAB-UE. The AMF may consider the 'Additional ULI' when it determines UE location and manages the UE location related functions (e.g. Mobility Restrictions). + +When the AMF provides user location information to other NFs (e.g. LMF as specified in clause 5.9 of TS 23.273 [87]) for a UE connected via MBSR, the AMF may also send the Additional ULI received via N2 messages. + +### 5.35A.7 Control of UE access to MBSR + +CAG Identifier is used to control the access of UE via MBSR (i.e. mobile IAB-node) and existing CAG mechanism defined in clause 5.30.3 can be used for managing UE's access to MBSR, with the following additional considerations: + +- When the MBSR is allowed to operate as an IAB node for a PLMN, the MBSR is configured, either during the communication with the serving PLMN OAM or (pre-)configuration mechanism, with a CAG identifier which is unique within the scope of this PLMN. If the MBSR is (pre-)configured with the PLMN list in which the MBSR is allowed to operate as MBSR, the corresponding CAG Identifier per PLMN is also configured in the MBSR. + +NOTE 1: The CAG for MBSR is supported as part of the PNI-NPN concept described in clause 5.30.3. + +- NG-RAN and 5GC support the UE access control based on the CAG identifier associated with the MBSR cell and the allowed CAG identifiers for the UE that supports CAG functionality. +- For the UE that does not support CAG functionality, NG-RAN and 5GC are allowed to use not only CAG mechanism but also the other existing mechanism e.g. forbidden Tracking Area, to manage its access to MBSR. +- Time duration restriction may be provided together with the CAG Identifier(s) for the MBSR(s) that the UE can access. The enhanced Allowed CAG list will be provided to UE and AMF for enforcement, to make sure that UE not accessing the MBSR cell outside of the time duration. For example, if the time when a certain CAG is allowed for a UE is up, the CAG for the UE is revoked from the network. + +NOTE 2: Control of the MBSR access to the serving network is based on normal mobility restriction management based on subscription data form MBSR (i.e. IAB-UE). + +## 5.36 RIM Information Transfer + +The purpose of RIM Information Transfer is to enable the transfer of RIM information between two RAN nodes via 5GC. The RIM Information Transfer is specified in TS 38.413 [34]. + +When the source AMF receives RIM information from source NG-RAN towards target NG-RAN, the source AMF forwards the RIM information to the target AMF, as described in TS 38.413 [34] and TS 29.518 [71]. The AMF does not interpret the transferred RIM information. + +## 5.37 Support for high data rate low latency services, eXtended Reality (XR) and interactive media services + +### 5.37.1 General + +This clause provides an overview of 5GS functionalities for support of XR services (AR/VR applications) and interactive media services that require high data rate and low latency communication, e.g. cloud gaming and tactile/multi-modal communication services according to service requirements documented in TS 22.261 [2]. The standardized 5QI characteristics for such interactive services are provided in Table 5.7.4-1 and TSCAI is used to describe the related traffic characteristics as defined in clause 5.27.2. Further enhancements for these interactive media services are as follows: + +- The 5GS may support QoS policy control for multi-modal traffic, see clause 5.37.2. +- The 5GS may support network information exposure which can be based on ECN markings for L4S, see clause 5.37.3 or 5GS exposure API, see clause 5.37.4. + +- The 5GS may support PDU Set based QoS handling including PDU Set identification and marking, see clause 5.37.5. +- The 5GS may ensure that the UL and DL packets together meet the requested round trip delay and also update the delay for UL and DL considering QoS monitoring results, see clause 5.37.6. +- The 5GS may perform per-flow Packet Delay Variation (PDV) monitoring and policy control according to AF provided requirements, see clause 5.37.7. +- The 5GC may provide traffic assistance information to the NG-RAN to enable Connected mode DRX power saving, see clause 5.37.8. + +### 5.37.2 Policy control enhancements to support multi-modal services + +A multi-modal service is a communication service that consists of several data flows that relate to each other and that are subject to application coordination. The data flows can transfer different types of data (for example audio, video, positioning, haptic data) and may come from different sources (e.g. a single UE, a single device or multiple devices connected to the single UE, or multiple UEs). + +For the single UE case, it is expected that those data flows are closely related and require strong application coordination for the proper execution of the multi-modal application and therefore, all those data flows are transmitted in a single PDU session. + +The Nnef\_AFsessionWithQoS service allows the AF to provide, at the same time, for each data flow that belongs to the multi-modal service, a Multi-modal Service ID, the service requirements and the QoS monitoring requirements: + +- The Multi-modal Service ID is an explicit indication that data flows are related to a multi-modal service. The PCF may use this information to derive the correct PCC rules and to apply appropriate QoS policies for the data flows that are part of a specific multi-modal application. +- The AF may provide QoS monitoring requirements for data flows associated to a multi-modal service to the PCF. The PCF generates the authorized QoS Monitoring policy for each data flow. + +NOTE: In order to start the QoS monitoring for the data flows associated to a multi-modal service within a certain period of time, the PCF needs to receive the QoS monitoring requirements for those data flows from AF within a single request or, in case of multiple requests, within a short period of time. + +In addition to the features that are provided for the case that the data flows are associated with a single UE, the following features are provided for the case where the data flows are associated with more than one UE: + +- The same DNN/S-NSSAI combination for the multi-modal service should be selected by each of the involved UEs. The URSP Rule evaluation framework is used to ensure that the same DNN/S-NSSAI is selected. +- The AF should use the same Multi-modal Service ID in the interactions with the PCF(s) for all the involved UEs that relate to a multi-modal service. The PCF may take this information into account (e.g. to apply a specific QoS policy) when processing each AF request independently. The data flows contribute to the service experience, but are still valid stand-alone, as they are transmitted over separate PDU Sessions to/from the involved UEs. +- If multiple PCFs are involved, the PCFs take policy decisions according to the input provided by the AF. There is no support for policy coordination among the multiple PCFs in this Release of the specification. Policy decisions are taken by each PCF separately on a per PDU Session basis. + +### 5.37.3 Support of ECN marking for L4S to expose the congestion information + +#### 5.37.3.1 General + +L4S (Low Latency, Low Loss and Scalable Throughput) is described in IETF RFC 9330 [159], IETF RFC 9331 [160] and IETF RFC 9332 [161]. It exposes congestion information by marking ECN bits in the IP header of the user IP packets between the UE and the application server to trigger application layer rate adaptation. + +In 5G System, ECN marking for L4S may be supported. ECN marking for L4S is enabled on a per QoS Flow basis in the uplink and/or downlink direction and may be used for GBR and non-GBR QoS Flows. ECN marking for the L4S in the IP header is supported in either the NG-RAN (see clause 5.37.3.2 and TS 38.300 [27]), or in the PSA UPF (see clause 5.37.3.3). + +NOTE 1: Based on operator's network configuration and policies, SMF decides whether NG-RAN or PSA UPF based ECN marking for L4S is used. + +In the case of ECN marking for L4S by PSA UPF, the NG-RAN is instructed to perform congestion information monitoring and report to the PSA UPF the congestion information (i.e. a percentage of packets that UPF uses for ECN marking for L4S) of the QoS Flow on UL and/or DL directions via GTP-U header extension to PSA UPF. + +NOTE 2: As for any QoS Flow, QoS rules in the UE and PDRs in the PSA UPF control which packets are bound to the L4S enabled QoS flow. The Packet Filter Set in the QoS rule or PDR can use packet filter(s) in clause 5.7.6.2 (e.g. match packets with ECT(1) or CE (See RFC 9331 [160]) together with IP 5 tuple) to steer traffic to an L4S enabled QoS Flow. + +NOTE 3: A QoS Flow may be enabled with ECN marking for L4S requirement e.g. statically when a PDU session is established based on configuration in SMF or PCF, or dynamically based on detection of the L4S traffic (e.g. match packets with ECT(1) or CE (See RFC 9331 [160]) together with IP 5 tuple) in the IP header whereby SMF or PCF triggers a setup of a QoS Flow enabled for L4S, or by requests by an AF. + +NOTE 4: To support this functionality, the UE needs to support L4S feedback as described in IETF RFC 9330 [159], which is not in the scope of 3GPP. + +When serving PSA UPF or NG-RAN is changed e.g. due to inter-NG-RAN handover or PSA UPF relocation, target NG-RAN and target PSA UPF, if supported, should continue to perform ECN marking for L4S for the QoS Flow. However, if not available (i.e. ECN marking for L4S is not supported in both, target NG-RAN and target PSA UPF), AF should be notified when ECN marking for L4S had been enabled for the QoS Flow based on AF request. + +#### 5.37.3.2 Support of ECN marking for L4S in NG-RAN + +ECN marking for L4S may be supported in NG-RAN as specified in TS 38.300 [27]. + +To enable ECN marking for L4S in NG-RAN, dedicated QoS Flow(s) are used for carrying L4S enabled IP traffic. The SMF may be instructed, based on either dynamic or predefined PCC rule, to provide an indication for ECN marking for L4S to NG-RAN for a corresponding QoS Flow(s) in UL and/or DL directions. In the absence of such PCC rule, the use of ECN marking for L4S in NG-RAN on a QoS Flow is controlled by a coordinated configuration in NG-RAN and 5GC. + +The criteria based on which NG-RAN decides to mark ECN bits for L4S is NG-RAN implementation specific. + +In the case of inter NG-RAN UE mobility, if the ECN marking for L4S has been enabled on source NG-RAN, but the target NG-RAN does not support ECN marking for L4S, then the SMF may, if supported, enable ECN marking for L4S in PSA UPF as defined in clause 5.37.3.3. + +#### 5.37.3.3 Support of ECN marking for L4S in PSA UPF + +To enable ECN marking for L4S by a PSA UPF, a QoS Flow level ECN marking for L4S indicator may be sent by SMF to PSA UPF over N4. SMF also indicates to NG-RAN to report the congestion information (i.e. a percentage of packets that UPF uses for ECN marking for L4S) of the QoS Flow on UL and/or DL directions via GTP-U header extension to PSA UPF. If there is no UL packet when report for DL and/or UL needs to be provided, NG-RAN may generate an UL Dummy GTP-U Packet for such a reporting. + +The SMF may be instructed, based on either dynamic or predefined PCC rule, to provide an indication for ECN marking for L4S to PSA UPF for a corresponding QoS Flow(s) in UL and/or DL directions. + +Upon successful activation of congestion information reporting for UL and/or DL directions, PSA UPF uses information sent by NG-RAN in GTP-U header extension (see TS 38.415 [116] and TS 38.300 [27]) to perform ECN bits marking for L4S for the corresponding direction. + +NOTE: How the congestion information is converted to ECN markings is UPF implementation specific. + +The criteria based on which NG-RAN decides to provide the congestion information is up to NG-RAN implementation. + +In the case of PSA UPF relocation, if the ECN marking for L4S has been enabled on source PSA UPF, SMF should select a target PSA UPF supporting ECN marking for L4S. If the target PSA UPF does not support ECN marking for L4S, then SMF may, if supported, switch to ECN marking for L4S in target NG-RAN by following clause 5.37.3.2. In such case, the target NG-RAN stops sending congestion information to the target PSA UPF. + +In the case of inter NG-RAN UE mobility, if the congestion information reporting has been enabled on source NG-RAN while the target NG-RAN does not support congestion information reporting, then the SMF shall inform PSA UPF to stop ECN marking for L4S. If ECN marking for L4S is supported by the target NG-RAN, the SMF may instruct the target NG-RAN to perform ECN marking for L4S in NG-RAN by following clause 5.37.3.2. For a given QoS Flow, if the target NG-RAN supports congestion information reporting, the target NG-RAN shall report congestion information to UPF once it is available. + +### 5.37.4 Network Exposure of 5GS information + +5GS and XR/media services cooperate to provide a better user experience using External Network Exposure. + +Based on the AF request, the 5GS can expose the following information based on the QoS Monitoring as defined in clause 5.33.3 and/or clause 5.45: + +- The UL and/or DL congestion information monitoring (see clause 5.45.3). + +Based on the PCC rule from PCF, the SMF requests the NG-RAN to report the information via GTP-U header to PSA UPF. This NG-RAN reported information is common to support congestion information exposure and to support ECN marking for L4S in PSA UPF as described in clause 5.37.3.3. In the case of congestion information exposure, the PSA UPF exposes the UL and/or DL congestion information via Nupf\_EventExposure service or via SMF/PCF/NEF as described in clause 5.8.2.18. It can be applied to a Non-GBR or GBR QoS Flow. + +- The UL and/or DL Data rate information (see clause 5.45.4). + +Based on the PCC rule from PCF, the SMF requests the PSA UPF to measure and report the information. They may be exposed to the AF directly by PSA UPF via Nupf\_EventExposure service or via SMF/PCF/NEF as described in clause 5.8.2.18. + +- The round trip delay for two service data flows considering the UL direction of a service data flow and the DL direction of another service data flow. in the same PDU Session. + +It is determined based on the QoS Monitoring for packet delay of individual QoS Flows as described in clause 5.33.3. The PCF derives the separate QoS monitoring policies for each direction packet delay (see clause 5.33.3) based on AF request and local policy. The PCF provides the two QoS Monitoring policies in the PCC rules for the service data flows. The PSA UPF reports the delay information per QoS Flow to the SMF. The SMF reports to PCF. The PCF derives round trip delay information based on the two direction's packet delay result for the service data flows and exposes the information to the AF directly or via NEF. + +- The round trip delay for one service data flow. + +If the service data flow is mapped to two QoS Flows (i.e. the UL traffic and DL traffic of the service data flow are separated into two QoS flows respectively) in the same PDU Session, similarly to the round trip delay for two service data flows over two QoS flows, the PCF triggers QoS Monitoring for each direction packet delay of individual QoS flows respectively and derives round trip delay based on the two direction QoS flows' packet delay monitored result. + +NOTE: How PCF calculates the requested round trip delay for multiple QoS Flows from delays of individual QoS Flows is not specified in this specification. + +The AF may provide the Alternative QoS parameter set requirements and Averaging Window to the NEF/PCF for the GBR QoS Flow as specified in clause 4.15.6.6 of TS 23.502 [3]. + +### 5.37.5 PDU Set based Handling + +#### 5.37.5.1 General + +A PDU Set is comprised of one or more PDUs carrying an application layer payload such as a video frame or video slice. The PDU Set based QoS handling by the NG-RAN is determined by PDU Set QoS Parameters in the QoS profile + +of the QoS Flow (specified in clause 5.7.7) and PDU Set information provided by the PSA UPF via N3/N9 interface as described in clause 5.37.5.2. The PDU Set based QoS Handling can be applied for GBR and non-GBR QoS Flows. + +The AF should provide PDU Set related assistance information for dynamic PCC control. One or more of the following PDU Set related assistance information may be provided to the NEF/PCF using the AF session with required QoS procedures in clauses 4.15.6.6 and 4.15.6.6a of TS 23.502 [3]. + +- PDU Set QoS Parameters as described in clause 5.7.7 +- Protocol Description: Indicates the transport protocol used by the service data flow (e.g. RTP, SRTP) and information, e.g. the following: + - RTP [185] or SRTP [186]; + - RTP or SRTP with RTP Header Extensions, including: + - RTP Header Extensions for PDU Set Marking as defined in TS 26.522 [179]; + - Other RTP Header Extensions as defined RFC 8285 [189]; + - RTP or SRTP without RTP Header Extensions, but together with RTP Payload Format (e.g. H.264 [187] or H.265 [188]); + - RTP or SRTP with RTP Header Extensions for PDU Set Marking as defined in TS 26.522 [179], and together with RTP Payload Format (e.g. H.264 [187] or H.265 [188]); + - RTP or SRTP with other RTP Header Extensions following RFC 8285 [189], and together with RTP Payload Format (e.g. H.264 [187] or H.265 [188]). + +When RTP Header Extensions for PDU Set Marking (as defined in TS 26.522 [179]) or other RTP header extensions as defined in RFC 8285 [189] is included, the differentiation between different RTP Header Extension Types should be supported. + +When RTP Payload Format is included, the differentiation between different RTP Payload Formats should be supported. + +NOTE 1: Multiplexing of different transport protocols and different media traffic for differentiated PDU Set QoS handling is not supported in the current Release. + +AF provided PDU Set QoS Parameters and Protocol Description may be used in determining the PCC Rule by the PCF as defined in clause 6.1.3.27.4 of TS 23.503 [45] and the Protocol Description may be used for identifying the PDU Set information by the PSA UPF. + +When the SMF receives the PCC rule, the SMF performs binding of the PCC rule to one QoS Flow as described in clause 6.1.3.2.4 of TS 23.503 [45]. If the PCC rule contains one or more PDU Set QoS Parameters (PSER, PSDB and PSIHI), the SMF adds these PDU Set QoS parameters to the QoS Profile of the QoS Flow as described in clause 6.2.2.4 of TS 23.503 [45]. Alternatively, the SMF may be configured to support PDU Set based QoS Handling without receiving PCC rules from a PCF. + +For the downlink direction, the PSA UPF identifies PDUs that belong to PDU Sets and marks them accordingly as described in clause 5.37.5.2. If the PSA UPF receives a PDU that does not belong to a PDU Set based on Protocol Description for PDU Set identification, then the PSA UPF still maps it to a PDU Set and determines the PDU Set Information as described in clause 5.37.5.2. + +NOTE 2: If the PSA UPF receives a PDU that does not belong to a PDU Set, then it is assumed that the UPF determines the PDU Set Importance value based on pre-configuration. + +For the uplink direction, the UE may identify PDU Sets, and how this is done is left up to UE implementation. The SMF may send Protocol Description associated with the QoS rule to UE. + +NOTE 3: Using the Protocol Description or not is left to UE implementation. The use of Protocol Description does not impact QoS Flow Mapping in the UE. + +In this Release, the PDU Set based QoS handling is supported in 5GS for UE registered in 3GPP access for single access PDU Session with IP PDU Session Type. + +#### 5.37.5.2 PDU Set Information and Identification + +To support PDU Set based QoS handling, the PSA UPF identifies PDUs that belong to PDU Sets and determines the below PDU Set Information which it sends to the NG-RAN in the GTP-U header. The PDU Set information is used by the NG-RAN for PDU Set based QoS handling as described above. + +The PDU Set Information comprises: + +- PDU Set Sequence Number. +- Indication of End PDU of the PDU Set. +- PDU Sequence Number within a PDU Set. +- PDU Set Size in bytes. +- PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow. + +The NG-RAN may use the Priority Level (see clause 5.7.3.3) across QoS Flows and PDU Set Importance within a QoS Flow for PDU Set level packet discarding in presence of congestion. + +NOTE 1: In addition to considering the PDU Set Importance within a QoS Flow, NG-RAN could also consider the relative PDU Set Importance across QoS Flows of the same Priority Level when determining which PDU Set needs to be discarded, which is up to implementation and configuration of operator. + +NOTE 2: The PDU Set Information can be different for different PDU Sets within a QoS Flow. + +The SMF instructs PSA UPF to perform PDU Set marking and may provide the PSA UPF the Protocol Description used by the service data flow. The Protocol Description may be received in the PCC rule, based on information provided by the AF or by PCF local policies as described in clause 5.37.5.1. + +PSA UPF can identify the PDU Set Information using the Protocol Description and the received transport protocol headers and payload or using implementation specific means. The details of the RTP/SRTP headers, header extensions and/or payloads used to identify PDU Set Information are defined in TS 26.522 [179]. + +For each DL PDU received on N6 for which PDU Set based QoS handling is indicated from the SMF, the PSA UPF applies the rules for PDU Set identification and provides the available PDU Set Information to the RAN in the GTP-U header. + +NOTE 3: The PSA UPF is expected to assign a unique PDU Set Sequence Number in the GTP-U header to each PDU Set of the QoS Flow. + +#### 5.37.5.3 Non-homogenous support of PDU set based handling in NG-RAN + +By sending at least one PDU Set QoS parameter to the NG-RAN, the SMF requests the NG-RAN to activate PDU Set QoS handling for a given QoS flow and the NG-RAN provides the SMF with an indication of whether the PDU Set based handling is supported. Based on this indication, SMF may activate the PDU Set identification and marking in the PSA UPF. + +For the mobility procedures that may result in the change of NG-RAN for PDU Set based handling support, the target NG-RAN provides to the SMF with an indication of whether the target NG-RAN node supports PDU Set based handling, as specified in TS 38.413 [34]. Based on the target NG-RAN indication, the SMF may, upon completion of the mobility procedure, initiate the PDU Session modification procedure to provide PDU Set QoS parameters to NG-RAN and may configure the PSA UPF to activate/deactivate the PDU Set identification and marking. + +In the case where the PSA UPF identifies and marks PDUs with PDU Set information in GTP-U header, it shall start doing so from a complete PDU Set. + +### 5.37.6 UL/DL policy control based on round-trip latency requirement + +For XR and other interactive media services that require very low Round-Trip (RT) latency, Uplink-Downlink policy control may be supported to meet the RT latency requirement. RT latency requirement is the upper bound for the sum of UL delay and DL delay of a single data flow or two different data flows between UE and N6 termination point at the + +UPF. PCF may support Uplink-Downlink policy control based on RT latency requirement based on an RT latency indication from AF (as defined in clause 6.1.3.27.2 of TS 23.503 [45]) during the AF session with the required QoS procedure as defined in clause 4.15.6.6 of TS 23.502 [3]. + +The AF can provide an RT latency indication with a single direction delay requirement between the UE and the PSA UPF expressed as the QoS Reference parameter or individual QoS parameters (as defined in clause 6.1.3.22 of TS 23.503 [45]). The RT latency indication indicates the need to meet the RT latency requirement for data flow, i.e. doubling of the single direction delay requirement between the UE and the PSA UPF expressed by the QoS Reference parameter or individual QoS parameter. + +PCF determines the data flow's UL PDB and DL PDB based on the RT latency requirement. The UL PDB and DL PDB can be unequal, but their sum shall not exceed the RT latency requirement. The PCF shall generate two PCC rules, one for UL QoS flow for UL traffic of the data flow and one for DL QoS flow for DL traffic of the data flow, respectively. PCF shall assign the 5QIs for each of these two PCC rules according to the derived UL PDB and DL PDB. + +To support UL and DL delay tracking, the QoS monitoring for UL packet delay and the DL packet delay (as defined in clause 6.1.3.21 of TS 23.503 [45]) shall be triggered respectively to request tracking the UL packet delay of the QoS flow used in UL and DL packet delay of the QoS flow used in DL independently. Based on the QoS monitoring results, the PCF may readjust the UL PDB and/or DL PDB under the consideration of the RT latency requirement to better fit the new situation. + +The Uplink-Downlink policy control based on round-trip latency requirement for two unidirectional service data flows is described in clause 6.1.3.27.2 of TS 23.503 [45]. + +NOTE: How the PCF derives the round-trip latency and takes policy decisions is up to the implementation. + +### 5.37.7 5GS Packet Delay Variation monitoring and reporting + +#### 5.37.7.1 General + +The 5GS Packet Delay Variation is the variation of packet delay measured between UE and PSA UPF. The AF may send the requirement for Packet Delay Variation monitoring to 5GS together with the requirement for packet delay measurement, as described in clause 6.1.3.21 of TS 23.503 [45]. + +Upon AF request for Packet Delay Variation monitoring together with packet delay monitoring, the PCF triggers the QoS monitoring procedure, and gets the UL, DL or RT QoS Monitoring result from the SMF. The PCF derives the 5GS Packet Delay Variation based on the QoS Monitoring result and then reports to the AF/NEF both packet delay measurements and Packet Delay Variation. + +NOTE: The derivation of 5GS Packet Delay Variation by PCF, based on QoS Monitoring, is implementation dependent. The Packet Delay Variation calculation method needs to be the same within the PLMN, based on operator policy. + +QoS Monitoring is used to obtain measurement of QoS parameters of individual QoS Flows. PCF determines the measurements required based on input from AF and enables the measurements by generating an authorized QoS Monitoring Policy for the PCC Rule as specified in clause 6.1.3.21 of TS 23.503 [45]. + +### 5.37.8 UE power saving management + +#### 5.37.8.1 General + +The following traffic assistance information may be provided by the CN to NG-RAN in order to configure UE power saving management scheme for connected mode DRX: + +- UL and/or DL Periodicity; +- N6 Jitter Information associated with the DL Periodicity; +- Indication of End of Data Burst. + +The UL and/or DL Periodicity and N6 Jitter Information associated with the DL Periodicity are provided by the CN to NG RAN via TSCAI. + +#### 5.37.8.2 Periodicity and N6 Jitter Information associated with Periodicity + +In the procedures for setting up or updating an AF session with QoS, the 5G System may be provided with UL/DL Periodicity information for NG-RAN to configure UE power management for connected mode DRX. The UL/DL Periodicity information is provided by the AF to the PCF via NEF or directly to the PCF when the AF is trusted. + +If UL/DL Periodicity information is available at the PCF, the PCF sends the Periodicity information received from the AF/NEF to the SMF. In accordance with the operator's local policies, the PCF may include an indication for SMF to request the UPF to perform N6 Traffic Parameter(s) measurement (i.e. N6 Jitter Information associated with the DL Periodicity and if not provided by the AF, UL/DL periodicity) within the PCC Rules. + +Upon reception of a PCC rule with Periodicity information, the SMF determines the TSCAI and forwards it to the NG-RAN. If the PCC rule indicates to perform N6 Traffic Parameter measurements, the SMF shall request the UPF to monitor and periodically report the N6 Traffic Parameters (i.e. the N6 Jitter Information associated with the DL Periodicity and, if not provided by the AF, UL/DL periodicity) using the N4 Session Modification procedure, see clause 5.8.5.11. If the measurement of N6 Jitter Information associated with the DL Periodicity is required and the DL Periodicity is available at the SMF, the SMF also sends the DL Periodicity to the UPF. The UPF reports the measured N6 Traffic Parameters to SMF via N4 interface. + +NOTE 1: How the UPF derives the N6 jitter and periodicity (i.e. when periodicity is not provided by the AF) is implementation dependent. + +At reception of measured N6 Traffic Parameter(s) from the UPF in the N4 Session Level Report, the SMF includes the N6 Jitter Information associated with the DL Periodicity together with the DL periodicity and the UL periodicity if not provided by the AF in the TSCAI and forwards it to the NG-RAN in an NGAP message, see clause 5.27.2. + +NOTE 2: In order to prevent frequent updates from the UPF, the UPF sends the N6 Jitter Measurement Report periodically or only when the N6 jitter is larger than a threshold. + +The N6 Jitter Information associated with the DL Periodicity indicates the range of the positive or negative deviation of the arrival time of first arrived packet of a Data Burst compared to the ideal Data Burst start time which is determined based on the DL periodicity. + +#### 5.37.8.3 End of Data Burst Indication + +An indication of End of Data Burst may be provided to the NG-RAN by the UPF, e.g. to configure UE power management schemes like connected mode DRX. + +Based on the End of Data Burst Marking Indication in a PCC rule and/or on local operator policies, SMF should request the UPF to detect the last PDU of the data burst and mark the End of Data burst in the GTP-U header of the last PDU in downlink. The SMF may provide the PSA UPF the End of Data Burst Marking Indication and Protocol Description used by the service data flow. The Protocol Description may be received in the PCC rule, based on information provided by the AF or by PCF local policies as described in clause 5.37.5.1. + +According to the request and information from the SMF, the UPF identifies the last PDU of a Data burst in the DL traffic based on the End indication according to the Protocol Description or UPF implementation and provides an End of Data Burst indication to the NG-RAN over GTP-U of the last PDU of a Data burst. + +NOTE: There can be some packets from the Data Burst received by NG-RAN after the PDU with End of Data Burst Indication if packets are received out of sequence. + +## 5.38 Support for Multi-USIM UE + +### 5.38.1 General + +A network and a Multi-USIM UE may support one or more of the following features for Multi-USIM UE operation: + +- Connection Release as described in clause 5.38.2; +- Paging Cause Indication for Voice Service, as described in clause 5.38.3; +- Reject Paging Request, as described in clause 5.38.4; + +- Paging Restriction, as described in clause 5.38.5; +- Paging Timing Collision Control, as described in clause 5.38.6. + +In the Registration procedure (as specified in clause 4.2.2.2.2), when a Multi-USIM UE has more than one USIM active, supports and intends to use one or more Multi-USIM specific features, it indicates to the AMF the corresponding Multi-USIM feature(s) are supported (except for the Paging Timing Collision Control feature). Based on the received indication of the supported Multi-USIM features from the UE, the AMF shall indicate to the UE the support of the Multi-USIM features based on the Multi-USIM features supported by network and any preference policy by the network, if available. When a UE returns to having only one USIM active from a Multi-USIM UE that previously indicated to the network it supported Multi-USIM feature(s), the UE shall indicate all the Multi-USIM features are not supported to the network for that USIM. The AMF shall only indicate the support of Paging Restriction feature together with the support of either Connection Release feature or Reject Paging Request feature. + +The Multi-USIM UE includes the support of individual features for Connection Release, Paging Cause Indication for Voice Service, Reject Paging Request and Paging Restriction as specified in clause 5.4.4a. + +NOTE: The Paging Timing Collision Control feature being based on the Mobility Registration Update, and it doesn't require capability exchange between the UE and network. + +The network shall not indicate support for any Multi-USIM feature to the UE as part of the Emergency Registration procedure. + +A Multi-USIM UE shall use a separate PEI for each USIM when it registers with the network. + +### 5.38.2 Connection Release + +A Multi-USIM UE may request the network to release the UE from RRC\_CONNECTED state in 3GPP access for a USIM due to activity on another USIM in 3GPP access, if both UE and network indicate the Connection Release feature is supported to each other. + +In the case of NAS connection release procedure, the UE indicates that it requests to be released from RRC\_CONNECTED state, by initiating either a Service Request procedure over 3GPP access or a Registration procedure over 3GPP access (if case the UE needs to perform Registration Update at the same time with this network, including the case where the Registration Request is sent due to mobility outside the Registration Area, i.e. before detecting whether the network supports the feature in the new Tracking Area, provided that the network has already indicated support for Connection Release feature in the current stored Registration Area), by including a Release Request Indication. If supported by the UE and network, the UE may also provide, only together with the Release Request Indication, Paging Restriction Information, as specified in clause 5.38.5, which requests the network to restrict paging. If the UE is performing an Emergency Registration then it shall not include a Release Request Indication. + +For NR/5G access, an AS method for the UE to request the network to release the UE from RRC\_CONNECTED state is specified in TS 38.300 [27]. This mechanism does not allow the UE to indicate Paging Restrictions. + +NOTE 1: When both the access stratum and NAS based approaches for requesting the connection release are supported by the UE and the network, it depends on the UE implementation which of the two to use (for example: based on the preferred end state (RRC\_INACTIVE or RRC\_IDLE) and whether Paging Restriction Information is to be provided). + +NOTE 2: When there is no PLMN-wide support for the Connection Release feature, it can occur that upon Mobility Registration Update with Release Request indication the UE is not released by the network. The UE behaviour, when it detects that the network does not support the feature in a new RA, is outside the scope of this specification. + +### 5.38.3 Paging Cause Indication for Voice Service + +A Multi-USIM UE and the network may support Paging Cause Indication for Voice Service feature. + +The network that supports Paging Cause Indication for Voice Service feature shall provide a Voice Service Indication for IMS voice service in the Paging message, only if the UE indicates the Paging Cause Indication for Voice Service feature is supported to the network. The network determines the IMS voice service based on the Paging Policy Indicator as specified in clause 5.4.3.2. + +Upon reception of the Voice Service Indication in NGAP Paging Message from AMF, the NG-RAN supporting Paging Cause Indication for Voice Service should include the Voice Service Indication in the Uu Paging message to the UE. + +When the UE context in the AMF indicates Paging Cause Indication for Voice Service feature is supported, in order to require NG RAN to deliver the Voice Service Indication in RAN paging for the UE in RRC\_INACTIVE state, the AMF provides an indication indicating the Paging Cause Indication for Voice Service feature is supported to the NG-RAN. Upon reception of the indication, the NG-RAN that supports the feature stores a Paging Cause Indication for Voice Service indication in its the UE context. For a UE in RRC\_INACTIVE, the NG-RAN should provide the Voice Service Indication in the RAN Paging message only when there is Paging Cause Indication for Voice Service indication in the UE context and detects the downlink data which triggers the RAN Paging message is related to voice service based on the Paging Policy Indicator, in the header of the received downlink data, as specified in clause 5.4.3.2. + +UE that supports the Paging Cause Indication for Voice Service feature is capable of differentiation between Paging from a network that does not support the Paging Cause Indication for Voice Service feature and Paging without the Voice Service Indication. How the UE distinguishes the Paging from a RAN that does not support the Paging Cause Indication for Voice Service feature and Paging without the Voice Service Indication is defined in TS 38.331 [28]. The UE determines whether the Paging Cause Indication for Voice Service feature is supported in the current Registration Area by 5GC based on the MUSIM capability exchange with the AMF, see clause 5.38.1. The UE determines that the Paging Cause Indication for Voice Service feature is supported if it is supported by both the RAN, as indicated in the received Uu Paging message, and by 5GC, as indicated in the MUSIM capability exchange with the AMF. + +The UE uses the Paging Cause Indication for Voice Service as described in TS 24.501 [47] and TS 38.331 [28]. + +### 5.38.4 Reject Paging Request + +A Multi-USIM UE may set up a connection to respond to a page with a Reject Paging Indication to the network indicating that the UE does not accept the paging and requests to return to CM-IDLE state after sending this response, if both UE and network indicate the Reject Paging Request feature is supported to each other. + +Upon being paged by the network, the Multi-USIM UE in CM-IDLE state attempts to send a Service Request message to the paging network including the Reject Paging Indication as the response to the paging, unless it is unable to do so, e.g. due to UE implementation constraints. In addition to the Reject Paging Indication, the UE may include Paging Restriction Information as specified in clause 5.38.5 in the Service Request message, if supported by UE and network. + +NOTE: A Multi-USIM UE in RRC\_INACTIVE state can decide to not initiate the RRC connection resumption procedure, e.g. when it decides not to respond to the paging message due to UE implementation constraints as specified in TS 24.501 [47] and TS 38.331 [28]. + +### 5.38.5 Paging Restriction + +A Multi-USIM UE and the network may support Paging Restriction. A Multi-USIM UE, if the AMF indicates that the network supports Paging Restriction feature, may indicate Paging Restriction Information in the Service Request or Registration Request message (including the case where the Registration Request is sent due to mobility outside the Registration Area, i.e. before detecting whether the network supports the feature in the new Tracking Area, provided that the network has already indicated support for Paging Restriction feature in the current stored Registration Area) as specified in clauses 5.38.2 and 5.38.4. + +Based on operator policy the AMF may accept or reject the Paging Restriction Information requested by the UE. If the AMF accepts the Paging Restriction Information from the UE, the AMF stores the Paging Restriction Information from the UE in the UE context. If the AMF rejects the Paging Restriction Information, the AMF removes any stored Paging Restriction Information from the UE context and discards the UEs requested Paging Restriction Information. The AMF informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the Registration Accept or Service Accept message. + +If the UE does not provide any Paging Restriction Information in the Service Request over 3GPP access or the Registration Request over 3GPP access, the AMF removes any stored Paging Restriction Information from the UE context. + +The Paging Restriction Information may indicate any of the following: + +- a) all paging is restricted; or +- b) all paging is restricted, except paging for voice service (IMS voice); or + +- c) all paging is restricted, except for certain PDU Session(s); or +- d) all paging is restricted, except paging for voice service (IMS voice) and certain PDU session(s). + +NOTE 1: The UE expects not to be paged for any purpose in case a). The UE expects to be paged only for voice service in case b). The UE expects to be paged only for certain PDU Session(s) in case c). The UE expects to be paged for voice service and certain PDU session(s) in case d). The AMF can page the UE for mobile terminated signalling based on local policy considering the stored Paging Restriction Information, except for case a). In this case, to comply with the UE provided Paging Restriction Information, the AMF can trigger AN release procedure as soon as possible after the mobile terminated signalling procedure is executed. + +NOTE 2: In the case of roaming, the Paging Restrictions for voice service implied by bullet b) and d) depends on the existence of an agreement with the HPLMN to support voice service via IMS. Hence the support of Paging Restrictions in bullets b) and d) takes the IMS voice service agreement into consideration. + +NOTE 3: When there is no PLMN-wide support for the Paging Restriction feature, it can occur that upon Mobility Registration Update with Paging Restriction Information the UE detects the network does not support the feature. If so, the UE assumes that no Paging Restriction Information is applied. + +### 5.38.6 Paging Timing Collision Control + +To avoid possible paging occasion collision and to enhance the likelihood that paging is received successfully for different USIMs, a Multi-USIM UE may need a new 5G-GUTI to modify the timing of the Paging Occasions (POs) for a USIM when the USIM's registration is not emergency registration. When a Multi-USIM UE needs a 5G-GUTI assignment, it performs a Mobility Registration Update without any specific indication (i.e. it is using a normal Registration procedure). This triggers the AMF to allocate a new 5G-GUTI and provide it to the Multi-USIM UE in the Registration Accept message. + +NOTE: It is recommended to avoid excessive signalling load from UE due to this procedure. + +## 5.39 Remote provisioning of credentials for NSSAA or secondary authentication/authorization + +### 5.39.1 General + +The UE's subscribed network (i.e. HPLMN, or subscribed SNPN) may provide functionalities to provision or update the credentials used for NSSAA or credentials used for secondary authentication/authorization to the UE. The provisioning procedure is supported via User Plane. + +For User Plane Remote Provisioning, the UE establishes a PDU Session that is used for remote provisioning, e.g. by using DNN(s)/S-NSSAI(s) which can access the PVS. The AMF selects an SMF used for remote provisioning using the SMF discovery and selection functionality as described in clause 6.3.2. If the SMF is configured with the PVS address(es) and/or PVS FQDN(s), the SMF shall send the PVS address(es) and/or PVS FQDN(s) per DNN/S-NSSAI to the UE via PCO during PDU Session Establishment procedure, based on the UE's subscribed DNN(s)/S-NSSAI(s) and the UE's request of PVS information from the network. Alternatively, the UE may be configured with an address of a PVS or the PVS may subscribe for UE Reachability Notification and may use the Application Triggering procedure as specified in TS 23.502 [3] to trigger the UE to initiate the setup of a connection for remote provisioning. + +### 5.39.2 Configuration for the UE + +In order to enable UP Remote Provisioning of credentials for NSSAA or secondary authentication/authorization, UE Configuration Data for UP Remote Provisioning are either pre-configured on the UE or provided by the network to the UE. UE Configuration Data for UP Remote Provisioning provided by the network take precedence over corresponding configuration data stored in the UE. + +UE Configuration Data for UP Remote Provisioning consist of PVS IP address(es) and/or PVS FQDN(s). The PVS IP address or PVS FQDN may be associated with dedicated DNN(s) and/or S-NSSAI(s). + +If the UE does not have any PVS IP address or PVS FQDN after the establishment of a PDU Session used for UP remote provisioning, the UE may construct an FQDN for PVS discovery as defined in TS 23.003 [19]. + +The UE Configuration Data for UP Remote Provisioning may be stored in the ME. + +The UE Configuration Data for UP Remote Provisioning (i.e. PVS IP address(es) or PVS FQDN(s)) associated with dedicated DNN(s) and/or S-NSSAI(s) may be locally configured in the SMF. The UE Configuration Data for UP Remote Provisioning, if available, shall be provided to the UE during the establishment of any PDU Session used for UP Remote Provisioning as part of Protocol Configuration Options (PCO) in the PDU Session Establishment Response, if the UE has requested the PVS information via PCO in the PDU Session Establishment Request. + +## 5.40 Support of Disaster Roaming with Minimization of Service Interruption + +### 5.40.1 General + +Subject to operator policy and national/regional regulations, 5GS provides Disaster Roaming service (e.g. voice call and data service) for the UEs from PLMN(s) with Disaster Condition. The UE shall attempt Disaster Roaming only if: + +- there is no available PLMN which is allowable (see TS 23.122 [17]); +- the UE is not in RM-REGISTERED and CM-CONNECTED state over non-3GPP access connected to 5GCN; +- the UE cannot get service over non-3GPP access through ePDG; +- the UE supports Disaster Roaming service; +- the UE has been configured by the HPLMN with an indication of whether Disaster roaming is enabled in the UE set to "disaster roaming is enabled in the UE" as specified in clause 5.40.2; and +- a PLMN without Disaster Condition is able to accept Disaster Inbound Roamers from the PLMN with Disaster Condition. + +In this Release of the specification, the Disaster Condition only applies to NG-RAN nodes, which means the rest of the network functions except one or more NG-RAN nodes of the PLMN with Disaster Condition can be assumed to be operational. + +### 5.40.2 UE configuration and provisioning for Disaster Roaming + +A UE supporting Disaster Roaming is configured with the following information: + +- Optionally, indication of whether disaster roaming is enabled in the UE; +- Optionally, indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN'; +- Optionally, list of PLMN(s) to be used in Disaster Condition. + +The Activation of Disaster Roaming is performed by the HPLMN by setting the indication of whether Disaster roaming is enabled in the UE to "disaster roaming is enabled in the UE" using the UE Parameters Update Procedure as defined in TS 23.502 [3]. The UE shall only perform disaster roaming if the HPLMN has configured the UE with the indication of whether disaster roaming is enabled in the UE and set the indication to "disaster roaming is enabled in the UE". The UE, registered for Disaster Roaming service, shall deregister from the PLMN providing Disaster Roaming service if the received indication of whether disaster roaming is enabled in the UE is set to "disaster roaming is disabled in the UE". + +The optional 'list of PLMN(s) to be used in Disaster Condition' may be pre-configured in USIM or provided by the HPLMN during and after a successful registration procedure over 3GPP access or non-3GPP access via Registration Request procedure or UE Configuration Update procedure as defined in TS 23.502 [3]. The 'list of PLMN(s) to be used in Disaster Condition' may be configured over non-3GPP access before disaster condition has occurred. + +While roaming (i.e. not in HPLMN), the Registered PLMN may provide the 'list of PLMN(s) to be used in Disaster Condition' during and after a successful registration procedure to the UE via Registration Request procedure or UE + +Configuration Update procedure as specified in TS 23.502 [3]. This list shall not alter any list provided by the HPLMN and shall only be used if the UE is configured by the HPLMN using the UE Parameters Update Procedure as defined in TS 23.502 [3] with the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' set to "True". + +The details of the UE behaviour regarding the usage of this list are described in TS 23.122 [17] and TS 24.501 [47]. If the UE is not configured with 'list of PLMN(s) to be used in Disaster Condition', the UE follows the procedure described in TS 23.122 [17] to select PLMN to be used in Disaster Condition. + +The HPLMN may use UE Parameters Update Procedure as defined in TS 23.502 [3] to update the Disaster Roaming information configuration in UE, if the UDM has received MINT support indication as indicated in 5GMM capability from the AMF. The UE indicates the support of MINT in 5GMM capability as specified in clause 5.4.4a, during registration procedure as defined in TS 23.502 [3]. + +### 5.40.3 Disaster Condition Notification and Determination + +The NG-RAN in the PLMN that provides Disaster Roaming service, broadcasts an indication of accessibility for Disaster Roaming service, and optionally, a 'list of one or more PLMN(s) with Disaster Condition for which Disaster Roaming service is offered by the available PLMN' in the impacted area as described in TS 38.304 [50] and TS 38.331 [28]. + +A UE determines the Disaster Condition based on the information broadcasted from the NG-RAN providing Disaster Roaming service, and performs the network selection and the access control for the Disaster Roaming as described in TS 23.122 [17] and TS 24.501 [47]. + +NOTE 1: How a PLMN is notified that another PLMN is a PLMN with Disaster Condition and how a PLMN is notified of the area where the associated Disaster Condition applies is managed by the government agencies or the authorities, and is out of scope of 3GPP. + +NOTE 2: The broadcast for Disaster Roaming service from the NG-RAN occurs only during the Disaster Condition. + +### 5.40.4 Registration for Disaster Roaming service + +For a UE to receive Disaster Roaming service from a PLMN providing Disaster Roaming service, the UE sends a NAS Registration Request message with Registration Type value "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update": + +- When the AMF in the PLMN providing Disaster Roaming service receives a NAS Registration Request with Registration Type set to "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update"; +- the AMF controls if the UE is allowed to access Disaster Roaming service in the area with Disaster Condition as specified in clause 4.2.2.2.2 of TS 23.502 [3]; +- the AMF may provide the Disaster Roaming service indication to AUSF and UDM as specified in clause 4.2.2.2.2 of TS 23.502 [3] and TS 33.501 [29]. The AMF may provide the Disaster Roaming service indication to SMF as specified in clause 4.3.2 of TS 23.502 [3]. + +NOTE 1: The AUSF and the UDM are configured with Disaster Condition via OAM based on operator policy and the request by the government agencies. Based on this local configuration and/or the Disaster Roaming service indication, the AUSF can execute authentication of the UE, and the UDM can provides the subscription data for a Disaster Roaming service to the AMF and/or the SMF. + +To support the Disaster Roaming service, the PLMN providing Disaster Roaming service is configured to support communication with the network entities in the HPLMN of the UE, i.e. configurations related to roaming interfaces for communication between serving PLMN and HPLMN shall be deployed in the affected entities. This communication between the PLMNs need only be enabled during the Disaster Condition. + +The Disaster Roaming service is limited to the impacted geographic area with Disaster Condition. The NG-RAN nodes and AMF in the PLMN providing Disaster Roaming service are configured with the area information, i.e. a list of TAIs which can be formulated by the PLMN providing the Disaster Roaming service based on the geographic area with Disaster Condition in the other PLMN(s). + +The AMF in the PLMN providing Disaster Roaming service provides the mobility restriction list to the NG-RAN as specified in clause 5.3.4.1.1 considering the area with Disaster Condition, and also indicating that EPC is not an allowed core network. + +NOTE 2: From the perspective of emergency services, a UE is following procedures as described in clause 4.24 of TS 24.501 [47] when registered for Disaster Roaming service. + +### 5.40.5 Handling when a Disaster Condition is no longer applicable + +When a UE detects a Disaster Condition is no longer applicable, the UE performs PLMN selection as described in TS 23.122 [17] and TS 24.501 [47] and may return to the PLMN previously with Disaster Condition. + +A PLMN providing Disaster Roaming: + +- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition when the Disaster Inbound Roamers attempt to transit to 5GMM-CONNECTED mode. +- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by triggering Deregistration procedure. +- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by rejecting Registration Request message. +- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by rejecting Service Request message. +- Shall organise the return of the Disaster Roaming UEs in a manner that does not cause overload (e.g. of signalling) in the PLMN that previously had the Disaster Condition. +- Stop broadcasting of providing Disaster Roaming service as specified in clause 5.40.3. +- May determine that the disaster condition has ended and the UE which is registered for disaster roaming services has an emergency PDU session, the AMF initiates the UE configuration update procedure to indicate that the UE is registered for emergency services as described in TS 24.501 [47]. +- May determine that the disaster condition has ended and inform the UE by initiating the UE configuration update procedure indicating re-registration from UE is required as specified in clause 5.4.4 of TS 24.501 [47] if the UE is in CM-CONNECTED mode. + +NOTE: Whether and how long the PLMN waits before paging the Disaster Inbound Roamers upon being notified that a Disaster Condition no longer applies is up to operator's policy. + +The HPLMN i.e. the UDM may trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by triggering Deregistration procedure. + +### 5.40.6 Prevention of signalling overload related to Disaster Condition and Disaster Roaming service + +The load control, congestion and overload control mechanism specified in clause 5.19 and access control and barring specified in clause 5.2.5 can be used to mitigate the load caused by UE requesting the Disaster Roaming service in the PLMN providing Disaster Roaming service and returning of UE to allowable PLMN when Disaster Condition is no longer applicable. + +To prevent signalling overload in PLMN providing Disaster Roaming, the HPLMN or registered PLMN: + +- may provide the UE in a prioritized manner with the list of PLMNs described in clause 5.40.2 for Disaster Roaming; +- may provide disaster roaming wait range information to control when the UE can initiate the registration for Disaster Roaming service upon arriving in the PLMN providing Disaster Roaming service as specified in TS 23.122 [17] and TS 24.501 [47]; and +- applies Access Identity 3 for Disaster Roaming service request as specified in TS 24.501 [47]. + +NOTE: The mechanisms available at the AMF and the SMF for mitigation of overload and congestion are used for 5GSM congestion mitigation during the Disaster Roaming. + +To prevent signalling overload by returning UEs in PLMN previously with Disaster Condition which is no long applicable, the HPLMN or registered PLMN: + +- may provide disaster return wait range information to control when the UE can initiate the registration upon returning to the PLMN previously with Disaster Condition as specified in TS 23.122 [17] and TS 24.501 [47]. + +## 5.41 NR RedCap UEs differentiation + +This functionality is used by the network to identify traffic to/from UEs accessing over NR RedCap, e.g. for charging differentiation. + +An NR RedCap UE using NR shall provide an NR RedCap indication to the NG-RAN during RRC Connection Establishment procedure as defined in TS 38.300 [27]. + +When the UE has provided an NR RedCap indication to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an NR RedCap Indication to the AMF in the Initial UE Message (see clause 4.2.2.2.1 of TS 23.502 [3] and TS 38.413 [34]). + +When the AMF receives an NR RedCap Indication from NG-RAN in an Initial UE Message, the AMF shall store the NR RedCap Indication in the UE context, consider that the RAT type is NR RedCap and signal it accordingly to the SMSF during registration procedure for SMS over NAS, to the SMF during PDU Session Establishment or PDU Session Modification procedure. The PCF will also receive the NR RedCap RAT type indication when applicable, from the SMF during SM Policy Association Establishment or SM Policy Association Modification procedure. + +During handover from E-UTRA to NR, the target NG-RAN (i.e. gNB) provides the NR RedCap indication to AMF in NGAP Path Switch Request message during Xn handover, or NGAP Handover Request Acknowledge message during N2 handover (including intra 5GS N2 handover and EPS to 5GS handover) based on the UE capability information provided by the source RAN to the target RAN as specified in TS 38.300 [27]. + +The NFs interacting with CHF shall include the NR RedCap as RAT type. + +Upon AMF change, the source AMF shall provide the "NR RedCap Indication" to the target AMF. + +## 5.42 Support of Non-seamless WLAN offload + +Non-seamless WLAN offload is an optional capability of a UE supporting WLAN radio access. + +The architecture to support authentication for Non-seamless WLAN offload in 5GS is defined in clause 4.2.15. + +A UE supporting Non-seamless WLAN offload may, while connected to WLAN access, route specific data flows via the WLAN access without traversing the 5GC. These UE data flows are identified using URSP configuration for Non-Seamless Offload, or UE Local Configurations as defined in TS 23.503 [45]. For these data flows, the UE uses the local IP address allocated by the WLAN access network and no IP address preservation is provided between WLAN and NG-RAN. + +For performing the Non-seamless WLAN offload, the UE needs to acquire a local IP address from the WLAN access network and it is not required to connect to an N3IWF, ePDG or TNGF. If the WLAN access network is configured to require the 5GS based access authentication of the UE for connecting to the WLAN, the UE performs the authentication procedure for Non-seamless WLAN offload in 5GS defined in clause 4.2.15 and in Annex S of TS 33.501 [29]. After successful authentication, the UE is not considered to be entered in 5GS Registered state. The UE can send and receive traffic not traversing the 5GC and which is not under the control of the 5GC. + +A non-3GPP access network may be connected via SWa' to multiple PLMNs for 5G NSWO. In a roaming scenario the HPLMN may be reached by the UE via a WLAN access connected to more than one VPLMN. Therefore, a UE when roaming shall be able to indicate a specific selected VPLMN (e.g. using decorated NAI for 5G NSWO) through which the NSWO request should be sent towards the HPLMN. + +A non-3GPP access network may be connected to multiple SNPNS different from the Credentials Holder for 5G NSWO. When using the credentials owned by CH, the UE shall be able to indicate a specific selected SNPN (e.g. using + +decorated NAI for 5G NSWO) through which the NSWO request should be sent towards the CH in the following scenarios: + +- The CH hosts AUSF/UDM and the CH is reached by the UE via a WLAN access connected to a SNPN different from the CH as defined in Figure 4.2.15-3a. +- The CH hosts AAA server and the CH is reached by the UE via a WLAN access connected to the AAA proxy in specific SNPN as defined in Figure 4.2.15-3b. + +A UE connected to a WLAN access network using 5GS credentials (as shown in Figure 4.2.15-1), may also be connected to the 5GC, for example to establish a PDU session. For example, the UE may connect to the 5GC either via another access type (such as NG-RAN), or via the same WLAN access network by performing the 5GS registration via Untrusted non-3GPP access procedure (using N3IWF) or interworking between ePDG connected to EPC and 5GS (using ePDG) defined in TS 23.502 [3]. + +When a UE is connected to a WLAN access network (e.g. using 5GS credentials) and using an Untrusted non-3GPP access, the UE can perform Non-Seamless Offload of some or all data traffic to this WLAN access network sending the traffic outside the IPSec tunnel encapsulation as defined in URSP rules with Non-Seamless Offload indication. + +A UE may use the Registration procedure for Trusted non-3GPP access defined in clause 4.12a.2.2 of TS 23.502 [3] and then determine to send some traffic (to be subject to Non-seamless WLAN offload) outside of the IPSec tunnel established with the TNGF. + +**NOTE:** A UE cannot first connect to a WLAN access network using 5GS credentials and without performing 5GS registration, and then later, on this WLAN access network, perform 5GS registration using the Trusted non-3GPP access procedure without first having to release the WLAN and then to establish a new WLAN association per the Registration procedure for Trusted non-3GPP access as defined in clause 4.12a.2.2 of TS 23.502 [3]. + +When the UE decides to use 5G NSWO to connect to the WLAN access network using its 5GS credentials but without registration to 5GS, the NAI format for 5G NSWO is used whose realm is different than the realm defined for usage of Trusted non-3GPP access to the 5GC (defined in clauses 28.7.6 and 28.7.7 of TS 23.003 [19]). + +The NAI format for 5G NSWO is defined in TS 23.003 [19]. + +## 5.43 Support for 5G Satellite Backhaul + +### 5.43.1 General + +Satellite may be used as part of the backhaul between (R)AN and 5GC. The 5G System supports to report of usage of satellite backhaul as described in clause 5.43.2. + +For some deployments, UPF may be deployed on the satellite. In these cases, edge computing or local switch via UPF deployed on the satellite may be performed as described in clauses 5.43.2 and 5.43.3. Deployments with satellite backhaul and edge computing with UPF on the ground is supported as described in clause 5.13, i.e. without satellite backhaul specific requirements. + +### 5.43.2 Edge Computing via UPF deployed on satellite + +This clause only applies to the case where Edge Computing is deployed with UPF and Edge Computing services on-board the satellite. The UPF deployed on satellite can act as UL CL/BP/local PSA UPF or act as PSA UPF. + +**NOTE 1:** In this Release, Edge Computing via UPF deployed on satellite only applies to GEO satellite backhaul. + +To select the UPF deployed on satellite as PSA, the following enhancements apply: + +- If the UE is accessing gNB with satellite backhaul, and AMF is aware of the satellite backhaul category, the AMF sends the satellite backhaul category to the PCF. If GEO satellite backhaul category is indicated, the PCF may take it into account to generate or update the URSP rule as defined in clause 6.1.2.2 of TS 23.503 [45] to including an appropriate Route Selection Descriptor for services deployed on GEO satellite, which further enable PDU Session Establishment with PSA UPF on the satellite. + +Based on GEO satellite ID provided by the AMF, the SMF performs PSA UPF selection or UL CL/BP/local PSA selection and insertion during the PDU Session Establishment procedure as described in clause 4.3.2 of TS 23.502 [3] or PDU Session Modification procedure as described in clause 4.3.3 of TS 23.502 [3] to select the UPF deployed on the GEO satellite if available, which includes: + +- Based on configuration, the AMF may determine the GEO Satellite ID serving the UE and send it to the SMF. If GEO satellite ID changes, e.g. due to UE handover to an gNB using different GEO satellite as part of backhaul, the AMF may update the latest GEO Satellite ID to the SMF. + +NOTE 2: It is assumed that AMF determines the GEO Satellite ID based on local configuration, e.g. based on Global RAN Node IDs associated with satellite backhaul. + +- The SMF determines DNAI based on local configuration, DNN or S-NSSAI or both and the GEO Satellite ID received from AMF. + +NOTE 3: It is assumed that one or more DNAI values are assigned for each GEO Satellite ID by the operator. SMF is locally configured with mapping relationship between DNAI and GEO Satellite ID. + +- If the UE is allowed to access the service(s) according to the EAS Deployment Information as described in clause 6.2.3.4 of TS 23.548 [130], the SMF selects the PSA UPF or UL CL/BP/local PSA based on the DNAI corresponding to the GEO Satellite ID and other factors as described in clause 6.2.3.2 of TS 23.548 [130]. + +NOTE 4: EASDF may be deployed on satellite based on local configuration. + +### 5.43.3 Local switch for UE-to-UE communications via UPF deployed on GEO satellite + +#### 5.43.3.1 General + +The UE to UE traffic may be locally routed by UPF(s) deployed on satellite (i.e. through local switch) to the target UE without traversing back to the satellite gateway on the ground. + +Local switching via UPF(s) deployed on satellite in this clause only applies on GEO satellite backhaul case and considers only DNNs and slices for 5G VN. + +N19 tunnel may be established between two UPFs deployed on different satellites for traffic between UEs. Also, N6 may be used for carrying traffic between UPFs deployed on different satellites. + +Only a single SMF is supported for local switching and N19 forwarding, i.e. both UEs are served by the same SMF. + +- NOTE: The latency optimisation that can be gained by inter-satellite link between UPFs on different GEO satellites depends on the distance between the satellites that can be substantial, depending on the number of deployed satellites. + +Clause 5.43.3.2 describes the case of PSA UPF deployed on satellite, clause 5.43.3.3 describes the case of UL CL/BP and local PSA deployed on satellite (PSA UPF is on the ground). Selection of PSA UPF or UL CL/BP/local PSA on satellite is described in clause 6.3.3 and determination of DNAI to select the UPF deployed on the corresponding GEO satellite reuses the mechanism described in clause 5.43.2. + +A combination of DNN/S-NSSAI is assigned by the operator for the communications between UEs where backhaul with UPF is deployed on GEO satellite, the URSP is described in TS 23.503 [45] and its configuration to enable the selection PSA UPF on the GEO satellite reuses the mechanism described in clause 5.43.2. + +#### 5.43.3.2 Local switch with PSA UPF deployed on satellite + +If SMF selects the UPF deployed on satellite as PSA of UE's PDU Session, the SMF configures the UE's N4 session to forward/detect packet to/from the internal interface as specified for the configuration for the 5GVN group member's N4 Session in clause 5.8.2.13.1 (Support for unicast traffic forwarding of a 5G VN). + +SMF may reuse the mechanism described in clause 5.8.2.13.1 to configure group-level N4 session rules for each N19 tunnel. + +For establishing N19 tunnel between the PSA UPFs onboard the satellite, the PSA UPFs are controlled by the same SMF. + +- To process packets between UE and servers residing in DN, SMF configures rules to route traffic via N6 as described in clause 5.8.2.13.1. + +The group-level N4 session is per DNN and S-NSSAI. The SMF can create, update or delete the group-level N4 Session, i.e. add or delete N4 rules, allocate or release the N19 tunnel resources based on operator deployment, e.g. based on GEO satellite's planned obsolescence or new GEO satellite setup. + +N6 may be used for carrying traffic between PSA UPFs deployed on different satellites. If N6 is used, SMF configures corresponding N4 rules for processing traffic to/from N6. + +#### 5.43.3.3 Local switching with UL CL/BP and local PSA UPF deployed on satellite + +If the UEs using GEO satellite backhaul are served by the same SMF and the GEO satellite(s) serving the UEs has UPF deployed, the SMF may determine to activate local switching and N19 forwarding for the UEs, based on: + +- 1) AF request including of UE identifiers which require communication between UEs as described in clause 5.29.2; and/or +- 2) Destination IP address(es) reported by on-ground PSA UPF as current reporting mechanism in clause 5.8.5.7. To enable the destination IP address(es) reporting, SMF configures the on-ground PSA UPF to detect UL packets with destination IP addresses which belong to the current UPF address pool. + +If the SMF determines that the UEs (i.e. corresponding to AF request in bullet 1) and/or the Destination IP address(es) reported in bullet 2)) are under the same GEO satellite (or multiple connectable GEO satellites) based on GEO Satellite ID(s) reported by AMF and the UEs are allowed to access the DNAIs corresponding to the GEO satellite IDs, for each UE communicating with target UE(s) in the communication group, the SMF may select and insert the UPF deployed on GEO satellite according to the DNAI as UL CL/BP and L-PSA, and configures UL CL/BP with the following rule: + +- Route the data traffic received from the UE and destined to IP address(es) of the target UE(s) to the L-PSA. +- Route other data traffic received from the UE to the PSA UPF of the UE's PDU Session. + +NOTE 1: The SMF determines the GEO satellites are connectable based on configuration. + +The SMF configures the Local PSA with local forwarding rules to forward the data traffic to the target UEs directly. If the selected L-PSAs are different for the UEs in the communication group, N19 tunnel is established between the L-PSAs. For establishing N19 tunnel between the UPFs onboard the satellite, the UPFs are controlled by the same SMF. If UEs are members of the same 5G VN group, the SMF may configure the local data forwarding rules on L-PSA(s) using 5GVN user plane handing mechanism in clause 5.8.2.13.1 (Support for unicast traffic forwarding of a 5G VN). + +NOTE 2: The selected UPF deployed on satellite can be inserted as UL CL/BP/L-PSA reusing existing UL CL/BP insertion procedures defined in TS 23.502 [3] or TS 23.548 [130]. + +N6 may be used for carrying traffic between L-PSA UPFs deployed on different satellites. If N6 is used, SMF configures corresponding N4 rules for processing traffic to/from N6. + +### 5.43.4 Reporting of satellite backhaul to SMF + +If the AMF is aware that a satellite backhaul is used towards 5G AN, the AMF may report this to SMF as part of the PDU Session establishment procedure as described in clause 4.3.2 of TS 23.502 [3]. If AMF is aware that satellite backhaul category changes (e.g. at handover), the AMF reports the current satellite backhaul category and indicates the satellite backhaul category change to SMF. + +Satellite backhaul category refers to the type of the satellite (i.e. GEO, MEO, LEO or OTHERSAT, DYNAMIC\_GEO, DYNAMIC\_MEO, DYNAMIC\_LEO, DYNAMIC\_OTHERSAT) used in the backhaul as specified in clause 5.4.3.39 of TS 29.571 [183]. Only a single backhaul category can be indicated. + +If dynamic satellite backhaul is used by the NG-RAN, i.e. capabilities (latency and/or bandwidth) of the satellite backhaul change over time due to e.g. use of varying inter-satellite links as part of backhaul, the AMF notifies the SMF of the corresponding dynamic satellite backhaul category to serve the PDU Session and the SMF can notify it to other NFs as described in clause 5.2.8.3 of TS 23.502 [3]. + +NOTE: It is assumed that the AMF can determine the Satellite backhaul category for the notification to the SMF based on local configuration, e.g. based on Global RAN Node IDs associated with satellite backhaul. + +### 5.43.5 QoS monitoring when dynamic Satellite Backhaul is used + +If dynamic satellite backhaul is used, QoS monitoring can be used to measure packet delay as specified in clause 5.45.2. + +If the Satellite backhaul category received from SMF indicates dynamic satellite backhaul is used, the PCF may, based on PCF local policy or configuration, request QoS monitoring for the packet delay between UE and PSA UPF as specified in clause 5.45.2. The AF can also trigger QoS monitoring by requesting QoS monitoring report from the PCF e.g. when the AF has received dynamic satellite backhaul indication. + +NOTE: PCF handling of satellite backhaul category indication and possible QoS monitoring is specified in TS 23.503 [45]. + +## 5.44 Support of Personal IoT network service + +### 5.44.1 General + +Personal IoT Network (PIN) provides local connectivity between PIN elements i.e. UEs and/or non-3GPP devices. PIN elements communicate using PIN direct communication, PIN indirect communication and the PIN-DN communication. The management of the PIN direct communication is out of the scope of this specification. For the PIN indirect communication and PIN-DN communication, the data traffic and management traffic pass via a UE acting as PIN element with Gateway Capability (PEGC). With the support of the PEGC registered to 5G network, the PIN Elements have access to the 5G network services and may communicate with other PIN Elements within the PIN or with the DN via 5GC. A PEGC may support multiple PINs. For each PIN, a dedicated DNN/S-NSSAI shall be configured. + +PIN and PIN elements are managed by specific PIN element with Management Capability (PEMC) with support of an AF, if AF (Application Server and PIN server as specified in TS 23.542 [181]) is deployed. A PIN includes at least one PEGC and at least one PEMC. The management of the PIN network (i.e. the management of PIN network creation, deletion and update) and PIN Element (including the management role distribution between PEMC and AF) is out of the scope of this specification. + +The PEGC is a UE with subscription data related to PIN within the 5GS (i.e. (DNN, S-NSSAI) combination(s) for PIN) and shall register to 5GS as UE in order to support PIN indirect communication and PIN-DN communication via dedicated PDU session. The UE acting as PEMC does not have subscription data related to PIN within the 5GS and behaves as normal UE if it is registered in 5GS. + +An AF for PIN may be deployed to support the PIN service. The AF for PIN may communicate with PIN elements, including PEMC and PEGC, via application layer for management of the PIN which is transported as user plane data transparently to 5GS and with the 5GC via NEF. + +The PEMC can manage the PIN via PIN direction communication or PIN indirect communication with the other elements of PIN or via PIN-DN communication with PIN AF which enables the exchange of information with 5GC. + +The 5GC is enhanced to support the delivery of UE policy related to PIN service for UE acting as PEGC (as specified in clause 5.44.2) and to support the PDU session management for PIN service (as specified in clause 5.44.3). + +See information in Annex P for the relation between PIN and 5GS. The PINE, PEMC and PEGC application layer functionalities are defined in TS 23.542 [181] and are transparent in 5GS. + +The support of PIN by 5G-RG and FN-RG is not specified. + +Redundant PDU session for URLLC is not supported in conjunction with PIN. + +### 5.44.2 UE policy delivery for PIN + +For a PEGC registered in the 5GS, the 5GS supports the provisioning of URSP rules that include a PIN ID as Traffic Descriptor. URSP rules with a PIN ID in the Traffic Descriptor are sent to the UE based on the information provided from an AF for PIN as specified in TS 23.502 [3] and TS 23.503 [45] for policy delivery. + +### 5.44.3 Session management enhancement for PIN service support + +#### 5.44.3.1 PDU Session Establishment for PIN + +When a PDU Session associated with a PIN is established by PEGC, an SMF is selected according to clause 4.3.2.2.3 of TS 23.502 [3] based on S-NSSAI/DNN. The PEGC may use IP address allocation methods as specified in clause 5.8.2 (e.g. IPv6 Prefix Delegation feature). + +One PEGC may serve more than one PIN. The PEGC may use a single or multiple PDU sessions to serve multiple PINs. One PDU Session may be shared by more than one PIN served by the PEGC, if differentiation or isolation for the traffics to/from different PINs via PEGC is not required in 5GS. Otherwise, different DNNs and S-NSSAIs shall be applied to distinguish the PINs by different PDU sessions of the PEGC. + +One PIN can be served by only one PDU session in the PEGC. If there are multiple PDU sessions for a PIN from different PEGCs connecting to the same UPF, the same mechanism for local switching in the UPF as defined for 5G VN group communication, as described in clause 5.8.2.13, may be applied. + +#### 5.44.3.2 Session management related policy control + +For PIN indirect communication and PIN-DN communication via PEGC and 5GC with PDU session, the 5GC supports the session policy control. The policy control is based on session management procedures as specified in TS 23.502 [3] and TS 23.503 [45]. + +An AF may provide QoS parameters for PIN traffic to 5GC as specified in clauses 4.15.6.6, 4.15.6.6a, and 4.15.6.14 of TS 23.502 [3]. + +An AF may influence traffic routing for PDU sessions for PIN-DN communication as specified in clause 5.6.7 and in clause 4.3.6 of TS 23.502 [3]. + +#### 5.44.3.3 Non-3GPP QoS Assistance Information + +QoS experienced by PINs connected behind a PEGC depends on the end-to-end path between a PINE and the application server, i.e. depends on the QoS differentiation in both the 3GPP network and the non-3GPP network attached to the PEGC. Non-3GPP QoS Assistance Information (N3QAI) enables the PEGC to perform QoS differentiation for the PINs in the non-3GPP network behind the PEGC. + +During PDU session establishment and PDU session modification, if the SMF provides the PEGC with QoS flow descriptions, the SMF may additionally signal N3QAI for each QoS flow to the PEGC based on the (DNN, S-NSSAI) combination of the PDU Session. Based on the N3QAI together with QoS rule information, the PEGC may reserve resources in the non-3GPP network. N3QAI consists of the following QoS information: QoS characteristics, GFBR/MFBR, Maximum Packet Loss Rate, Notification Control. + +How to enforce QoS based on the N3QAI in the non-3GPP network is considered outside the scope of 3GPP. + +#### 5.44.3.4 Non-3GPP delay budget between PINE and PEGC + +For PIN indirect communication and PIN-DN communication via PEGC and 5GC, non-3GPP delay is the delay between the PEGC and the PINE. 5GC may need to be aware of the non-3GPP delay and compensate for this delay in 5GS. The compensation is achieved by adjusting the dynamic CN PDB for the 3GPP network by the non-3GPP delay (i.e. the network determined original PDB value is unchanged, but it needs to cover non-3GPP delay, besides the AN PDB and CN PDB). + +If the PEGC supports providing of the non-3GPP delay budget for a specific QoS flow of the PIN traffic, the PEGC may provide a non-3GPP delay budget to SMF by using the UE requested PDU Session Modification procedure. Based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may, according to operator policy and implementation, consider the non-3GPP delay budget when signalling the dynamic CN PDB to NG-RAN. The dynamic CN PDB signalled to the NG-RAN may be calculated as the sum of the value of dynamic CN PDB for the related GBR QoS flow and the requested non-3GPP delay budget. If the dynamic CN PDB changes in the SMF (e.g., when an I-UPF is inserted by the SMF), based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may apply the non-3GPP delay budget again before signalling the dynamic CN PDB to NG-RAN. The non-3GPP delay budget does not impact the QoS flow binding in SMF. + +NOTE 1: For deployments that support a PEGC to request a non-3GPP delay budget it is assumed that RAN is locally configured to give precedence to the CN PDB value received via N2 signalling as specified in clause 5.7.3.4. + +It is assumed that the PEGC will limit the frequency of triggering the UE-initiated PDU Session Modification request to provide the non-3GPP delay budget to the network to avoid unnecessary signalling. + +NOTE 2: It is up to CT WG1 to discuss to potentially introduce a timer to limit how often a PEGC is allowed to request a delay budget. + +### 5.44.4 Identifiers for PIN + +A PIN is managed at the PIN application layer. A unique PIN ID in a PLMN is designated to a PIN, e.g. by PIN application layer as specified in TS 23.542 [181]. In 5GS the PIN ID is only used in the traffic descriptor of URSP rules, for routing traffic of specific PIN towards a dedicated (DNN, S-NSSAI) combination as specified in clause 6.6.2 of TS 23.503 [45]. + +If a PIN contains more than one PEGCs, the list of PEGCs may be grouped together following the 5G VN group management principles as specified in clause 5.29.2. Then the PEGCs of a PIN can be identified by an External Group ID by the AF for PIN. The AF for PIN may use the External Group ID to manage the list of PEGCs that are part of a PIN and for providing URSP guidance (as specified in clause 5.44.2) and/or QoS requests applicable to all the PEGCs (as specified in clause 5.44.3). + +NOTE: The PEMCs can also be grouped together with the PEGCs using the 5G VN group management functionality for enabling the PEMCs to communicate with PEGCs via UPF local switch in order to manage the PIN. + +## 5.45 QoS Monitoring + +### 5.45.1 General + +QoS monitoring comprises of measurements of QoS monitoring parameters and reports of the measurement result for a QoS Flow and can be enabled based on 3rd party application requests and/or operator policies configured in the PCF. Event Reporting from PCF is specified in clause 6.1.3.18 of TS 23.503 [45] and User Plane QoS Flow related QoS monitoring and reporting in clause 5.8.2.18. + +The AF may request measurements for one or more of the following QoS monitoring parameters, which may trigger QoS monitoring for service data flow(s): + +- UL packet delay, DL packet delay, round trip packet delay for a service data flow, see clause 5.45.2. +- Congestion, see clause 5.45.3. +- Data Rate, see clause 5.45.4. +- Packet Delay Variation, see clause 5.37.7. +- Round trip packet delay considering UL on a service data flow and DL of another service data flow, see clause 5.37.4. + +The following AF requested QoS requirements may trigger QoS monitoring for service data flow(s): + +- Round-trip latency requirement, see clause 5.37.6. + +The PCF may generate the authorized QoS Monitoring policy for a service data flow based on the QoS Monitoring request received from the AF (as described in clause 6.1.3.21 of TS 23.503 [45]) or based on PCF local policy or configuration reasons, such as PCF awareness of dynamic satellite backhaul connection. The PCF includes the authorized QoS Monitoring policy in the PCC rule and provides it to the SMF. + +The QoS monitoring parameter(s) that can be measured by means of QoS monitoring are listed below. The QoS monitoring policy in PCC rule (described in clause 6.3.1 of TS 23.503 [45]) may include the following: + +- UL packet delay, DL packet delay, round trip packet delay, see clause 5.45.2. + +- Congestion, see clause 5.45.3. +- Data Rate, see clause 5.45.4. + +The SMF configures the UPF to perform QoS monitoring for the QoS Flow and to report the monitoring results as described in clause 5.8.2.18 with parameters determined by the SMF based on the authorized QoS Monitoring policy received from the PCF or local configuration or both. + +The SMF may also configure RAN to measure the QoS monitoring parameters by sending QoS monitoring request based on the authorized QoS Monitoring policy received from the PCF and/or local configuration. The QoS monitoring request to the NG RAN for different parameters is as defined in clause 5.45.2 and 5.45.3. + +The following clauses describe the QoS monitoring parameters which can be measured and any specific actions or constraints for their measurement. + +NOTE: The QoS monitoring parameter which can be measured are parameters which describe the QoS experienced in the 5GS by the application, i.e. they are not restricted to the 5G QoS Parameters defined in clause 5.7.2. + +### 5.45.2 Packet delay monitoring + +QoS Monitoring for packet delay allows for the measurement of UL packet delay, DL packet delay or round trip packet delay between UE and PSA UPF. The details of the QoS Monitoring for packet delay are described in clause 5.33.3. + +The PCF may calculate Packet Delay Variation (clause 5.37.7) and the round trip packet delay when UL and DL are on different QoS flows (clause 5.37.4) based on packet delay monitoring results of QoS flows. + +### 5.45.3 Congestion information monitoring + +The NG-RAN may be required to provide the UL and/or DL QoS Flow congestion information to UPF (i.e. a percentage of congestion level for exposure). The UPF may be required to monitor and expose the UL and/or DL QoS Flow congestion information reported from the NG-RAN. + +QoS monitoring request for congestion information provided by the SMF to the NG-RAN is to trigger the NG-RAN to measure and report UL and/or DL QoS Flow congestion information to PSA UPF as defined in 5.37.3. + +NOTE 1: How the RAN measures and reports the congestion information is up to RAN implementation. + +NOTE 2: It is assumed that the RAN reports whenever there is a change in the percentage of packets to be marked with ECN for L4S marking and/or congestion information. The granularity of change in percentage determination is up to RAN implementation. + +For the reporting of the congestion information from PSA UPF, the periodical reporting is not applied and only the *Reporting frequency 'event triggered'* applies, see clause 5.8.2.18. The PSA UPF shall send a report when the measurement result crosses the indicated *Reporting threshold*. Subsequent reports shall not be sent by the PSA UPF during the *Minimum waiting time*. + +The PSA UPF reports the received UL and/or DL QoS Flow congestion information to the target NF as instructed by the QoS Monitoring request (see clause 5.8.2.18) from the SMF. + +Only one of ECN marking for L4S (in the case of ECN marking for L4S in RAN as described in clause 5.37.3) or QoS monitoring of congestion information may be requested to NG-RAN for a QoS Flow. They are mutually exclusive, therefore, measurements of Congestion information on a QoS Flow are not provided in QoS Monitoring reports if SMF enables ECN marking for L4S in RAN (see clause 5.37.3). + +### 5.45.4 Data rate monitoring + +The QoS Monitoring for data rate allows the measurement of the UL and/or DL data rate per QoS flow at the PSA UPF and it can be applied to a Non-GBR or GBR QoS flow. The data rate is measured over a monitoring averaging window with a standardized value. + +The SMF may configure the UPF to perform and report QoS monitoring for data rates as described in clause 5.8.2.18. According to the QoS Monitoring request for UL and/or DL data rate from the SMF, the UPF is required to initiate data rate measurement for a QoS Flow and to report the measured data rate as instructed. + +### 5.45.5 Void + +## 5.46 Assistance to AI/ML Operations in the Application Layer + +### 5.46.1 General + +This clause describes the list of 5GC enablers to support the following AI/ML operations in the Application layer over the 5G System: + +- AI/ML operation splitting between AI/ML endpoints; +- AI/ML model/data distribution and sharing; +- Distributed/Federated Learning. + +NOTE 1: Requirements on 5G System assistance to AI/ML operations in the Application layer are specified in clause 6.40 of TS 22.261 [2]. + +The AF may subscribe to NEF monitoring events as described in clause 4.15.3.2.3 of TS 23.502 [3] in order to assist its application AI/ML operations. For example, the AF may subscribe to session inactivity time monitoring event in order to assist the AI/ML application server in scheduling available UE(s) to participate in the AI/ML operation (e.g. + +Federated Learning). In addition, the AF may subscribe to NEF to be notified on the traffic volume exchanged between the UE and the AI/ML application server in order to assist the AF with the transfer of AI/ML data. + +The AF that aims to provide an AI/ML operation may request assistance from the 5GC as described in clause 5.46.2. The AF initially provides a list of target member UE(s) and at least one filtering criterion, when subscribing to the NEF to be notified about a subset list of UE(s) (i.e. list of candidate UE(s)) that fulfil certain filtering criteria. Details of the procedures are described in clause 4.15.13 of TS 23.502 [3]. This subset list of UE(s) may become the member UE(s) used in the AI/ML operation depending on the AF's final decision, considering its internal logic. Alternatively, the AF may select the list of UEs for the AI/ML operation without NEF involvement as described in Annex I of TS 23.502 [3]: in this case, the AF determines a list of UEs without any assistance from the NEF and may use, for example, NWDAF analytics to assist with the AI/ML operation over 5G System. + +The AF may request the network to provide a recommended time window for the AI/ML operation using the Planned Data Transfer with QoS (PDTQ) requirements and procedures as described in clause 6.1.2.7 of TS 23.503 [45] and in clause 4.16.15 of TS 23.502 [3]. + +At the time or during the AI/ML operation, the AF may request the serving NEF to provide QoS for a list of UEs. Each UE is identified by its UE IP address. The AF may subscribe to QoS Monitoring which may include also Consolidated Data Rate monitoring as described in clause 5.45 and in clause 4.15.6.13 of TS 23.502 [3] for those AF requests for QoS that result in a successful resource allocation. The AF provides QoS parameters that are derived from the performance requirements listed in clause 7.10 of TS 22.261 [2]. + +As a result of the AF subscription to NEF to provide the subset list of UE(s) that fulfil certain filtering criteria, the AF may be notified about changes in the subset list of UE(s) and in such a case the AF may determine a updated list of UEs used in the AI/ML operation from the new subset list of UE(s) provided by NEF, and the AF may request a new recommended time window for the AI/ML operation using the Planned Data Transfer with QoS (PDTQ) requirements as described in clause 6.1.2.7 of TS 23.503 [45] and in clause 4.16.15 of TS 23.502 [3]. The AF may request the NEF to provide QoS for the updated list of UEs, each identified by UE IP address, that results in QoS resources previously allocated to some UEs to be released, while QoS resources for other UEs to be allocated and QoS monitoring to be initiated. + +The AF may also subscribe to, or request Network Data Analytics as defined in TS 23.288 [86], such as End-to-end data volume transfer time analytics, DN performance analytics, Network performance analytics, UE mobility analytics, WLAN performance analytics etc. in order to assist its AI/ML operations. + +The AF hosting an AI/ML based application may provision the Expected UE Behaviour parameters captured in Table 4.15.6.3-1 of TS 23.502 [3] and/or the Application-Specific Expected UE Behaviour parameter(s) captured in Table 4.15.6.3f-1 of TS 23.502 [3] to the 5GC. The parameters may be provisioned with corresponding confidence and/or accuracy levels, and a threshold may also be provided to the UDM by the NF (e.g. AMF or SMF) subscribing to such externally provisioned parameters as described in clause 4.15.6.2 of TS 23.502 [3]. + +In addition, the following principles apply when 5GS assists the AI/ML operation at the application layer: + +- AF requesting 5GS assistance to AI/ML operations in the application layer shall be authorized by the 5GC using the existing mechanisms. + +NOTE 2: In this Release, assistance to AI/ML operations in the application layer is not supported for roaming UEs. + +NOTE 3: Policy and charging control as defined in TS 23.503 [45] can be used for traffic related to AI/ML operations as described in clause 6.40.1 of TS 22.261 [2]. Capabilities based on Flow Based Charging can be used together with an appropriate PCF configuration for charging differentiation between AI/ML traffic and other type of traffic from the same application. As long as the AF can provide different filter information as described in TS 23.503 [45] for the AI/ML traffic and the other type of traffic from the same application in the procedures utilized for the resource request, the PCF can assign different rating groups (i.e. charging key) or rating group + service-ids based on an appropriate PCF configuration. The UPF will then handle such traffic accordingly. This enables charging of AI/ML traffic according to operator's policies. + +- Application AI/ML decisions and their internal operation logic reside at the AF and UE application client and is out of scope of 3GPP. +- Based on application logic, it is the application decision whether to request assistance from 5GC, e.g. for the purpose of selection of Member UEs that participate in certain AI/ML operation. + +- In this Release, 5GS assistance to AI/ML operations in the application layer is conducted within a single slice. + +### 5.46.2 Member UE selection assistance functionality for application operation + +5G System may support Member UE selection assistance functionality to assist the AF to select member UE(s) that can be used in application operations such as AI/ML based applications (e.g. Federated Learning) as specified in clause 5.46.1 according to the AF's inputs. + +The Member UE selection assistance functionality shall be hosted by NEF, and the features of the Member UE selection assistance functionality hosted by the NEF include (see clause 4.15.13 of TS 23.502 [3] for details of Member UE selection procedures): + +- Receiving a request from the AF that shall include a list of target member UE(s) (which may not necessarily be a part of the subsequent updated request), optionally (a) time window(s), and one or more filtering criteria as specified in Table 4.15.13.2-1 of TS 23.502 [3] (e.g. UE current location, UE historical location, UE direction, UE separation distance, QoS requirements, DNN, preferred access/RAT type, Desired end-to-end data volume transfer time performance, or Service Experience). +- Referring to the filtering criteria provided by the AF and then interacting with 5GC NFs using existing services in order to have the corresponding data for all the UEs in the list of target member UE from relevant 5GC NFs (e.g. PCF, NWDAF, AMF, SMF) to derive the list(s) of candidate UE(s) (i.e. UE(s) among the list of target member UE(s) provided by the AF) which fulfil the filtering criteria. +- Providing the AF with the Member UE selection assistance information, including one or more lists of candidate UE(s), and optionally other additional information (e.g. one or more recommended time window(s) for performing the application operation, QoS of each target UE, UE(s) location, Access/RAT type, or Service Experience). NEF may also provide the number of UEs per each filtering criterion that do not fulfil the corresponding filtering criterion. + +The Member UE selection assistance information provided by the NEF may be used by the AF to select member UE(s) used in application AI/ML operation. (See clause 5.2.6.32 of TS 23.502 [3] for details of parameters). + +NOTE: The AF can decide whether to use the Member UE selection assistance functionality provided by NEF. + +Without using the Member UE selection assistance functionality, AF in either trusted or untrusted domain can select the Member UE(s) for e.g. participating in federating learning operation, by collecting the corresponding data using network exposure information as described in clause 4.15 of TS 23.502 [3], e.g. UE location reporting from the AMF, user plane information from the UPF and network data analytics from NWDAF. + +# --- 6 Network Functions + +## 6.1 General + +Clause 6 provides the functional description of the Network Functions and network entities and the principles for Network Function and Network Function Service discovery and selection. + +NG-RAN functions and entities are described in TS 38.300 [27] and TS 38.401 [42]. + +Security functions and entities are described in TS 33.501 [29] and TS 33.535 [124]. + +5G Media streaming functions are described in TS 26.501 [135]. + +## 6.2 Network Function Functional description + +### 6.2.1 AMF + +The Access and Mobility Management function (AMF) includes the following functionality. Some or all of the AMF functionalities may be supported in a single instance of an AMF: + +- Termination of RAN CP interface (N2). +- Termination of NAS (N1), NAS ciphering and integrity protection. +- Registration management. +- Connection management. +- Reachability management. +- Mobility Management. +- Lawful intercept (for AMF events and interface to LI System). +- Provide transport for SM messages between UE and SMF. +- Transparent proxy for routing SM messages. +- Access Authentication. +- Access Authorization. +- Provide transport for SMS messages between UE and SMSF. +- Security Anchor Functionality (SEAF) as specified in TS 33.501 [29]. +- Location Services management for regulatory services. +- Provide transport for Location Services messages between UE and LMF as well as between RAN and LMF. +- EPS Bearer ID allocation for interworking with EPS. +- UE mobility event notification. +- S-NSSAIs per TA mapping notification. +- Support for Control Plane CIoT 5GS Optimisation. +- Support for User Plane CIoT 5GS Optimisation. +- Support for restriction of use of Enhanced Coverage. +- Provisioning of external parameters (Expected UE Behaviour parameters or Network Configuration parameters). +- Support for Network Slice-Specific Authentication and Authorization. +- Support for charging. +- Controlling the 5G access stratum-based time distribution based on UE's subscription data. +- Controlling the gNB's time synchronization status reporting and subscription. + +NOTE 1: Regardless of the number of Network functions, there is only one NAS interface instance per access network between the UE and the CN, terminated at one of the Network functions that implements at least NAS security and Mobility Management. + +In addition to the functionalities of the AMF described above, the AMF may include the following functionality to support non-3GPP access networks: + +- Support of N2 interface with N3IWF/TNGF. Over this interface, some information (e.g. 3GPP Cell Identification) and procedures (e.g. Handover related) defined over 3GPP access may not apply, and non-3GPP access specific information may be applied that do not apply to 3GPP accesses. +- Support of NAS signalling with a UE over N3IWF/TNGF. Some procedures supported by NAS signalling over 3GPP access may be not applicable to untrusted non-3GPP (e.g. Paging) access. +- Support of authentication of UEs connected over N3IWF/TNGF. +- Management of mobility, authentication, and separate security context state(s) of a UE connected via a non-3GPP access or connected via a 3GPP access and a non-3GPP access simultaneously. +- Support as described in clause 5.3.2.3 a co-ordinated RM management context valid over a 3GPP access and a Non 3GPP access. +- Support as described in clause 5.3.3.4 dedicated CM management contexts for the UE for connectivity over non-3GPP access. +- Determine whether the serving N3IWF/TNGF is appropriate based on the slices supported by the N3IWFs/TNGFs as specified in clause 6.3.6 and clause 6.3.12 respectively. + +NOTE 2: Not all of the functionalities are required to be supported in an instance of a Network Slice. + +In addition to the functionalities of the AMF described above, the AMF may include policy related functionalities as described in clause 6.2.8 of TS 23.503 [45]. + +The AMF uses the N14 interface for AMF re-allocation and AMF to AMF information transfer. This interface may be either intra-PLMN or inter-PLMN (e.g. in the case of inter-PLMN mobility). + +In addition to the functionality of the AMF described above, the AMF may include the following functionality to support monitoring in roaming scenarios: + +- Normalization of reports according to roaming agreements between VPLMN and HPLMN (e.g. change the location granularity in a report from cell level to a level that is appropriate for the HPLMN); and +- Generation of charging/accounting information for Monitoring Event Reports that are sent to the HPLMN. + +In addition to the functionality of the AMF described above, the AMF may provide support for Network Slice restriction and Network Slice instance restriction based on NWDAF analytics. + +In addition to the functionalities of the AMF described above, the AMF may provide support for the Disaster Roaming as described in clause 5.40. + +In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support Network Slice Admission Control: + +- Support of NSAC for maximum number of UEs as defined in clauses 5.15.11.1 and 5.15.11.3. + +In addition to the functionality of the AMF described above, the AMF may include the following functionality to support SNPNs: + +- Support for Onboarding of UEs for SNPNs. + +In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support satellite backhaul: + +- Support for reporting satellite backhaul category and its modification based on AMF local configuration to SMF as defined in clause 5.43.4. + +In addition to the functionalities of the AMF described above, the AMF may provide support for Network Slice instance change for PDU sessions as defined in clause 5.15.5.3. + +In addition to the functionalities of the AMF described above, the AMF may also support functionalities for Partial Network Slice support in a Registration Area as described in clause 5.15.17. + +In addition to the functionalities of the AMF described above, the AMF may also include functionalities to support NS-AoS not matching deployed Tracking Areas as described in clause 5.15.18. + +In addition to the functionalities of the AMF described above, the AMF may also include functionalities to support Network Slice Replacement as described in clause 5.15.19. + +In addition to the functionalities of the AMF described above, the AMF may also include functionalities to enforce the LADN Service Area per LADN DNN and S-NSSAI for a UE as described in clause 5.6.5a, as well as to enforce the LADN Service Area per LADN DNN for a UE in clause 5.6.5. + +### 6.2.2 SMF + +The Session Management function (SMF) includes the following functionality. Some or all of the SMF functionalities may be supported in a single instance of a SMF: + +- Session Management e.g. Session Establishment, modify and release, including tunnel maintain between UPF and AN node. +- UE IP address allocation & management (including optional Authorization). The UE IP address may be received from a UPF or from an external data network. +- DHCPv4 (server and client) and DHCPv6 (server and client) functions. +- Functionality to respond to Address Resolution Protocol (ARP) requests and / or IPv6 Neighbour Solicitation requests based on local cache information for the Ethernet PDUs. The SMF responds to the ARP and / or the IPv6 Neighbour Solicitation Request by providing the MAC address corresponding to the IP address sent in the request. +- Selection and control of UP function, including controlling the UPF to proxy ARP or IPv6 Neighbour Discovery, or to forward all ARP/IPv6 Neighbour Solicitation traffic to the SMF, for Ethernet PDU Sessions. +- Configures traffic steering at UPF to route traffic to proper destination. +- 5G VN group management, e.g. maintain the topology of the involved PSA UPFs, establish and release the N19 tunnels between PSA UPFs, configure traffic forwarding at UPF to apply local switching, N6-based forwarding or N19-based forwarding, manage traffic forwarding in the case that a SMF Set or multiple SMF Sets are serving a 5G VN. +- Termination of interfaces towards Policy control functions. +- Lawful intercept (for SM events and interface to LI System). +- Support for charging. +- Control and coordination of charging data collection at UPF. +- Termination of SM parts of NAS messages. +- Downlink Data Notification. +- Initiator of AN specific SM information, sent via AMF over N2 to AN. +- Determine SSC mode of a session. +- Support for Control Plane CIoT 5GS Optimisation. +- Support of header compression. +- Act as I-SMF in deployments where I-SMF can be inserted, removed and relocated. +- Provisioning of external parameters (Expected UE Behaviour parameters or Network Configuration parameters). +- Support P-CSCF discovery for IMS services. +- Act as V-SMF with following roaming functionalities: + - Handle local enforcement to apply QoS SLAs (VPLMN). + - Charging (VPLMN). + +- Lawful intercept (in VPLMN for SM events and interface to LI System). +- Support for interaction with external DN for transport of signalling for PDU Session authentication/authorization by external DN. +- Instructs UPF and NG-RAN to perform redundant transmission on N3/N9 interfaces. +- Generation of the TSC Assistance Information based on the TSC Assistance Container received from the PCF. +- Support for RAN feedback for BAT offset and adjusted periodicity as defined in clause 5.27.2.5. + +NOTE: Not all of the functionalities are required to be supported in an instance of a Network Slice. + +In addition to the functionalities of the SMF described above, the SMF may include policy related functionalities as described in clause 6.2.2 of TS 23.503 [45]. + +In addition to the functionality of the SMF described above, the SMF may include the following functionality to support monitoring in roaming scenarios: + +- Normalization of reports according to roaming agreements between VPLMN and HPLMN; and +- Generation of charging information for Monitoring Event Reports that are sent to the HPLMN. + +The SMF may also include following functionalities to support Edge Computing enhancements (further defined in TS 23.548 [130]): + +- Selection of EASDF and provision of its address to the UE as the DNS Server for the PDU session; +- Usage of EASDF services as defined in TS 23.548 [130]; +- For supporting the Application Layer Architecture defined in TS 23.558 [134]: Provision and updates of ECS Address Configuration Information to the UE. + +The SMF and SMF+ PGW-C may also include following functionalities to support Network Slice Admission Control: + +- Support of NSAC for maximum number of PDU sessions as defined in clauses 5.15.11.2, 5.15.11.3 and 5.15.11.5. +- Support of NSAC for maximum number of UEs as defined in clauses 5.15.11.3 and 5.15.11.5. +- Support of PDU Set based QoS handling as described in clause 5.37.5. + +The SMF may also include following functionalities: + +- Providing per-QoS flow Non-3GPP QoS assistance information to the UE (e.g. PEGC) and formulation of the CN PDB based on non-3GPP delay budget from UE (e.g. PEGC) as described in clause 5.44.3.4. + +In addition to the functionalities of the SMF described above, the SMF may also include functionalities to support Network Slice Replacement as described in clause 5.15.19. + +The SMF may also include functionalities to support indirect UPF event exposure service subscription on behalf of the consumer NF(s) as described in clause 4.15.4.5 of TS 23.502 [3]. + +### 6.2.3 UPF + +The User plane function (UPF) includes the following functionality. Some or all of the UPF functionalities may be supported in a single instance of a UPF: + +- Anchor point for Intra-/Inter-RAT mobility (when applicable). +- Allocation of UE IP address/prefix (if supported) in response to SMF request. +- External PDU Session point of interconnect to Data Network. +- Packet routing & forwarding (e.g. support of Uplink classifier to route traffic flows to an instance of a data network, support of Branching point to support multi-homed PDU Session, support of traffic forwarding within a 5G VN group (UPF local switching, via N6, via N19)). + +- Packet inspection (e.g. Application detection based on service data flow template and the optional PFDs received from the SMF in addition). +- User Plane part of policy rule enforcement, e.g. Gating, Redirection, Traffic steering). +- Lawful intercept (UP collection). +- Traffic usage reporting. +- QoS handling for user plane, e.g. UL/DL rate enforcement, Reflective QoS marking in DL. +- Uplink Traffic verification (SDF to QoS Flow mapping). +- Transport level packet marking in the uplink and downlink. +- Downlink packet buffering and downlink data notification triggering. +- Sending and forwarding of one or more "end marker" to the source NG-RAN node. +- Functionality to respond to Address Resolution Protocol (ARP) requests and / or IPv6 Neighbour Solicitation requests based on local cache information for the Ethernet PDUs. The UPF responds to the ARP and / or the IPv6 Neighbour Solicitation Request by providing the MAC address corresponding to the IP address sent in the request. +- Packet duplication in downlink direction and elimination in uplink direction in GTP-U layer. +- NW-TT functionality. +- High latency communication, see clause 5.31.8. +- ATSSS Steering functionality to steer the MA PDU Session traffic, refer to clause 5.32.6. + +NOTE: Not all of the UPF functionalities are required to be supported in an instance of user plane function of a Network Slice. + +- Inter PLMN UP Security (IPUPS) functionality, specified in clause 5.8.2.14. +- Event exposure, including exposure of network information, i.e. the QoS monitoring information, as specified in clause 5.8.2.18, events as specified in clause 5.2.26.2 of TS 23.502 [3], exposure of data collected for analytics, as specified in clause 5.2.26.2 of TS 23.502 [3] and exposure of the TSC management information as specified in clause 5.8.5.14. +- Exposure of the UE information, e.g. UE IP address translation information as specified in clause 5.2.26.3 of TS 23.502 [3] and clause 4.15.10 of TS 23.502 [3] if Network address translation (i.e. NAT) functionality of the UE IP address is deployed within UPF. +- Support PDU Set Handling as defined in clause 5.37.5. + +### 6.2.4 PCF + +The Policy Control Function (PCF) includes the following functionality: + +- Supports unified policy framework to govern network behaviour. +- Provides policy rules to Control Plane function(s) to enforce them. +- Accesses subscription information relevant for policy decisions in a Unified Data Repository (UDR). +- Support PDU Set Handling as defined in clause 5.37.5. + +NOTE: The PCF accesses the UDR located in the same PLMN as the PCF. + +The details of the PCF functionality are defined in clause 6.2.1 of TS 23.503 [45]. + +### 6.2.5 NEF + +#### 6.2.5.0 NEF functionality + +The Network Exposure Function (NEF) supports the following independent functionality: + +- Exposure of capabilities and events: + - NF capabilities and events may be securely exposed by NEF for e.g. 3rd party, Application Functions, Edge Computing as described in clause 5.13. + - NEF stores/retrieves information as structured data using a standardized interface (Nudr) to the Unified Data Repository (UDR). +- Secure provision of information from external application to 3GPP network: + - It provides a means for the Application Functions to securely provide information to 3GPP network, e.g. Expected UE Behaviour, 5G-VN group information, time synchronization service information and PDU Set handling service specific information. In that case the NEF may authenticate and authorize and assist in throttling the Application Functions. +- Translation of internal-external information: + - It translates between information exchanged with the AF and information exchanged with the internal network function. For example, it translates between an AF-Service-Identifier and internal 5G Core information such as DNN, S-NSSAI, as described in clause 5.6.7. + - In particular, NEF handles masking of network and user sensitive information to external AF's according to the network policy. +- Redirecting the AF to a more suitable NEF/L-NEF e.g. when serving an AF request for local information exposure and detecting there is a more appropriate NEF instance to serve the AF's request. +- The Network Exposure Function receives information from other network functions (based on exposed capabilities of other network functions). NEF stores the received information as structured data using a standardized interface to a Unified Data Repository (UDR). The stored information can be accessed and "re-exposed" by the NEF to other network functions and Application Functions, and used for other purposes such as analytics. +- A NEF may also support a PFD Function: The PFD Function in the NEF may store and retrieve PFD(s) in the UDR and shall provide PFD(s) to the SMF on the request of SMF (pull mode) or on the request of PFD management from NEF (push mode), as described in TS 23.503 [45]. +- A NEF may also support a 5G-VN Group Management Function: The 5G-VN Group Management Function in the NEF may store the 5G-VN group information in the UDR via UDM as described in TS 23.502 [3]. +- Support management of ECS Address Information. +- Support management of relationship between DNAI and EAS Address Information. +- Exposure of analytics: + - NWDAF analytics may be securely exposed by NEF for external party, as specified in TS 23.288 [86]. +- Retrieval of data from external party by NWDAF: + - Data provided by the external party may be collected by NWDAF via NEF for analytics generation purpose. NEF handles and forwards requests and notifications between NWDAF and AF, as specified in TS 23.288 [86]. +- Support of Non-IP Data Delivery: + - NEF provides a means for management of NIDD configuration and delivery of MO/MT unstructured data by exposing the NIDD APIs as described in TS 23.502 [3] on the N33/Nnef reference point. See clause 5.31.5. +- Charging data collection and support of charging interfaces. + +- Support of Member UE selection assistance functionality: + - NEF may provide one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information to the AF based on the parameters contained in the request from the AF as described in clause 5.46.2. NEF supports the translation of the member UE selection filtering criteria parameters received from the AF to the corresponding event or analytics filters that can be understood by the 5GC NFs for events or analytics related data collection. NEF interacts with 5GC NFs using existing services in order to collect the corresponding data and then derive the list(s) of candidate UE(s) and other assistance information as described in clause 4.15.13 of TS 23.502 [3]. +- Support of Multi-member AF session with required QoS for a set of UEs identified by a list of UE addresses: + - Details are specified in clause 4.15.6.13 of TS 23.502 [3]. +- Support of UAS NF functionality: + +Details are defined in TS 23.256 [136]. +- Support of EAS deployment functionality: + +Details are defined in TS 23.548 [130]. +- Support of SBI-based MO SM transmit for MSISDN-less MO SMS: + +Details are defined in TS 23.540 [142]. +- Support PDU Set Handling as defined in clause 5.37.5. +- Support management of common EAS and common DNAI: + +Details are defined in TS 23.548 [130]. + +A specific NEF instance may support one or more of the functionalities described above and consequently an individual NEF may support a subset of the APIs specified for capability exposure. + +NOTE: The NEF can access the UDR located in the same PLMN as the NEF. + +The services provided by the NEF are specified in clause 7.2.8. + +For external exposure of services related to specific UE(s), the NEF resides in the HPLMN. Depending on operator agreements, the NEF in the HPLMN may have interface(s) with NF(s) in the VPLMN. + +When a UE is capable of switching between EPC and 5GC, an SCEF+NEF is used for service exposure. See clause 5.17.5 for a description of the SCEF+NEF. + +#### 6.2.5.1 Support for CAPIF + +When an NEF is used for external exposure, the CAPIF may be supported. When CAPIF is supported, an NEF that is used for external exposure supports the CAPIF API provider domain functions. The CAPIF and associated API provider domain functions are specified in TS 23.222 [64]. + +### 6.2.5a Void + +### 6.2.6 NRF + +#### 6.2.6.1 General + +The Network Repository Function (NRF) supports the following functionality: + +- Supports service discovery of NRF services and their endpoint addresses by the NRF bootstrapping service. + +- Supports service discovery function. Receive NF Discovery Request from NF instance or SCP, and provides the information of the discovered NF instances (be discovered) to the NF instance or SCP. +- Supports P-CSCF discovery (specialized case of AF discovery by SMF). +- Maintains the NF profile of available NF instances and their supported services. +- Maintains SCP profile of available SCP instances. +- Supports SCP discovery by SCP instances. +- Notifies about newly registered/updated/ deregistered NF and SCP instances along with its potential NF services to the subscribed NF service consumer or SCP. +- Maintains the health status of NFs and SCP. + +In the context of Network Slicing, based on network implementation, multiple NRFs can be deployed at different levels (see clause 5.15.5): + +- PLMN level (the NRF is configured with information for the whole PLMN), +- shared-slice level (the NRF is configured with information belonging to a set of Network Slices), +- slice-specific level (the NRF is configured with information belonging to an S-NSSAI). + +In the context of roaming, multiple NRFs may be deployed in the different networks (see clause 4.2.4): + +- the NRF(s) in the Visited PLMN (known as the vNRF) configured with information for the visited PLMN. +- the NRF(s) in the Home PLMN (known as the hNRF) configured with information for the home PLMN, referenced by the vNRF via the N27 interface. + +#### 6.2.6.2 NF profile + +NF profile of NF instance maintained in an NRF includes the following information: + +- NF instance ID. +- NF type. +- PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. +- Network Slice related Identifier(s) e.g. S-NSSAI, NSI ID. +- FQDN or IP address of NF. +- NF capacity information. +- NF priority information. + +NOTE 1: This parameter is used for AMF selection, if applicable, as specified in clause 6.3.5. See clause 6.1.6.2.2 of TS 29.510 [58] for its detailed use. + +- NF Set ID. +- NF Service Set ID of the NF service instance. +- NF Specific Service authorization information. +- if applicable, Names of supported services. +- Endpoint Address(es) of instance(s) of each supported service. +- Identification of stored data/information. + +NOTE 2: This is only applicable for a UDR profile. See applicable input parameters for Nnrf\_NFManagement\_NFRegister service operation in clause 5.2.7.2.2 of TS 23.502 [3]. This information applicability to other NF profiles is implementation specific. + +- Other service parameter, e.g. DNN or DNN list, notification endpoint for each type of notification that the NF service is interested in receiving. +- Location information for the NF instance. + +NOTE 3: This information is operator specific. Examples of such information can be geographical location, data centre. + +- TAI(s). +- NF load information. +- Routing Indicator, Home Network Public Key identifier, for UDM and AUSF. +- For UDM, AUSF and NSSAAF in the case of access to an SNPN using credentials owned by a Credentials Holder with AAA Server, identification of Credentials Holder (i.e. the realm of the Network Specific Identifier based SUPI). +- For UDM and AUSF, and if UDM/AUSF is used for access to an SNPN using credentials owned by a Credentials Holder, identification of Credentials Holder (i.e. the realm if Network Specific Identifier based SUPI is used or the MCC and MNC if IMSI based SUPI is used); see clause 5.30.2.1. +- For AUSF and NSSAAF in the case of SNPN Onboarding using a DCS with AAA server, identification of DCS (i.e. the realm of the Network Specific Identifier based SUPI). +- For UDM and AUSF, and if UDM/AUSF is used as DCS in the case of SNPN Onboarding, identification of DCS (i.e. the realm if Network Specific Identifier based SUPI, or the MCC and MNC if IMSI based SUPI). +- One or more GUAMI(s), in the case of AMF. +- For the UPF, see clause 5.2.7.2.2 of TS 23.502 [3]. +- UDM Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of internal group identifiers, range(s) of external group identifiers for UDM. +- UDR Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers for UDR. +- AUSF Group ID, range(s) of SUPIs for AUSF. +- PCF Group ID, range(s) of SUPIs for PCF. +- HSS Group ID, set(s) of IMPIs, set(s) of IMPU, set(s) of IMSIs, set(s) of PSIs, set(s) of MSISDN for HSS. +- For NWDAF, the following information are supported: + - Analytics ID(s) (possibly per service). + - NWDAF Serving Area information (i.e. list of TAIs for which the NWDAF can provide services and/or data). + - Supported Analytics Delay per Analytics ID (if available). + - NF types of the NF data sources, NF Set IDs of the NF data sources, if available. + - Analytics aggregation capability (if available). + - Analytics metadata provisioning capability (if available). + - ML model Filter information parameters include S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s). + - ML Model Interoperability indicator (if available) per Analytics ID(s). + +- FL capability information per analytics ID including FL capability type (i.e. FL server NWDAF or FL client NWDAF, if available). +- Time interval supporting FL (if available). +- Accuracy checking capability for ML model accuracy monitoring or Analytics Accuracy Monitoring (if available). +- Roaming exchange capability (if available). + +NOTE 4: The NWDAF's Serving Area information is common to all its supported Analytics IDs. + +NOTE 5: The Analytics IDs supported by the NWDAF may be associated with a Supported Analytics Delay i.e. the Analytics report can be generated with a time (including data collection delay and inference delay) in less than or equal to the Supported Analytics Delay. + +NOTE 6: The determination of Supported Analytics Delay, and how the NWDAF avoid updating its Supported Analytics Delay in NRF frequently is NWDAF implementation specific. + +- Event ID(s) supported by AFs, in the case of NEF. +- Event Exposure service supported event ID(s) by UPF. +- Application Identifier(s) supported by AFs, in the case of NEF. +- Range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF, in the case of NEF. + +NOTE 7: This is applicable when NEF exposes AF information for analytics purpose as detailed in TS 23.288 [86]. + +NOTE 8: It is expected service authorization information is usually provided by OA&M system, and it can also be included in the NF profile in the case that e.g. an NF instance has an exceptional service authorization information. + +NOTE 9: The NRF may store a mapping between UDM Group ID and SUPI(s), UDR Group ID and SUPI(s), AUSF Group ID and SUPI(s) and PCF Group ID and SUPI(s), to enable discovery of UDM, UDR, AUSF and PCF using SUPI, SUPI ranges as specified in clause 6.3 or interact with UDR to resolve the UDM Group ID/UDR Group ID/AUSF Group ID/PCF Group ID based on UE identity, e.g. SUPI (see clause 6.3.1 for details). + +- IP domain list as described in clause 6.1.6.2.21 of TS 29.510 [58], Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs or Range(s) of GPSIs or a BSF Group ID, in the case of BSF. +- SCP Domain the NF belongs to. +- DCCF Serving Area information, NF types of the data sources, NF Set IDs of the data sources, if available, in the case of DCCF. +- Supported DNAI list, in the case of SMF. +- For SNPN, capability to support SNPN Onboarding in the case of AMF and capability to support User Plane Remote Provisioning in the case of SMF. +- IP address range, DNAI for UPF. +- Additional V2X related NF profile parameters are defined in TS 23.287 [121]. +- Additional ProSe related NF profile parameters are defined in TS 23.304 [128]. +- Additional MBS related NF profile parameters are defined in TS 23.247 [129]. +- Additional UAS related NF profile parameters are defined in TS 23.256 [136]. +- Additional Ranging based services and Sidelink Positioning related NF profile parameters are defined in TS 23.586 [180]. +- For additional information in PCF profile, see clause 5.2.7.2.2 of TS 23.502 [3]. + +#### 6.2.6.3 SCP profile + +SCP profile maintained in an NRF includes the following information: + +- SCP ID. +- FQDN or IP address of SCP. +- Indication that the profile is of an SCP (e.g. NF type parameter set to type SCP). +- SCP capacity information. +- SCP load information. +- SCP priority. +- Location information for the SCP (see locality in clause 6.1.6.2.2 of TS 29.510 [58]). +- Served Location(s) (see servingScope in clause 6.1.6.2.2 of TS 29.510 [58]). +- Network Slice related Identifier(s) e.g. S-NSSAI, NSI ID. +- Remote PLMNs reachable through SCP. +- Endpoint addresses accessible via the SCP. +- NF sets of NFs served by the SCP. +- SCP Domain the SCP belongs to. If an SCP belongs to more than one SCP Domain, the SCP will be able bridge these domains, i.e. sending messages between these domains. + +NOTE: Service definition defines optional and mandatory parameters, see TS 23.502 [3]. + +### 6.2.7 UDM + +The Unified Data Management (UDM) includes support for the following functionality: + +- Generation of 3GPP AKA Authentication Credentials. +- User Identification Handling (e.g. storage and management of SUPI for each subscriber in the 5G system). +- Support of de-concealment of privacy-protected subscription identifier (SUCI). +- Access authorization based on subscription data (e.g. roaming restrictions). +- UE's Serving NF Registration Management (e.g. storing serving AMF for UE, storing serving SMF for UE's PDU Session). +- Support to service/session continuity e.g. by keeping SMF/DNN assignment of ongoing sessions. +- MT-SMS delivery support. +- Lawful Intercept Functionality (especially in outbound roaming case where UDM is the only point of contact for LI). +- Subscription management. +- SMS management. +- 5G-VN group management handling. +- Support of external parameter provisioning (Expected UE Behaviour parameters or Network Configuration parameters). +- Support for the Disaster Roaming as described in clause 5.40. + +- Support for the control of time synchronization service based on subscription data as described in clause 5.27.1.11. + +To provide this functionality, the UDM uses subscription data (including authentication data) that may be stored in UDR, in which case a UDM implements the application logic and does not require an internal user data storage and then several different UDMs may serve the same user in different transactions. + +NOTE 1: The interaction between UDM and HSS, when they are deployed as separate network functions, is defined in TS 23.632 [102] and TS 29.563 [103] or it is implementation specific. + +NOTE 2: The UDM is located in the HPLMN of the subscribers it serves, and access the information of the UDR located in the same PLMN. + +### 6.2.8 AUSF + +The Authentication Server Function (AUSF) supports the following functionality: + +- Supports authentication for 3GPP access and untrusted non-3GPP access as specified in TS 33.501 [29]. +- Supports authentication of UE for a Disaster Roaming service as specified in TS 33.501 [29]. + +### 6.2.9 N3IWF + +The functionality of N3IWF in the case of untrusted non-3GPP access includes the following: + +- Support of IPsec tunnel establishment with the UE: The N3IWF terminates the IKEv2/IPsec protocols with the UE over NWu and relays over N2 the information needed to authenticate the UE and authorize its access to the 5G Core Network. +- Termination of N2 and N3 interfaces to 5G Core Network for control - plane and user-plane respectively. +- Relaying uplink and downlink control-plane NAS (N1) signalling between the UE and AMF. +- Handling of N2 signalling from SMF (relayed by AMF) related to PDU Sessions and QoS. +- Establishment of IPsec Security Association (IPsec SA) to support PDU Session traffic. +- Relaying uplink and downlink user-plane packets between the UE and UPF. This involves: + - De-capsulation/ encapsulation of packets for IPsec and N3 tunnelling. +- Enforcing QoS corresponding to N3 packet marking (e.g. DSCP), taking into account QoS requirements associated to such marking received over N2. QoS includes 5QI, the Priority Level (if explicitly signalled) and optionally, the ARP priority level. + +NOTE: Based on operator policy and/or regional/national regulations, the N3IWF can apply a different DSCP value to the outer ESP tunnel packet than the DSCP value of the inner IP packet. + +- Packet marking, e.g. setting the DSCP value based on the Establishment cause on N2, and based on 5QI, the Priority Level (if explicitly signalled) and optionally, the ARP priority level on N3. +- Local mobility anchor within untrusted non-3GPP access networks using MOBIKE per IETF RFC 4555 [57]. +- Supporting AMF selection. + +### 6.2.9A TNGF + +The functionality of TNGF in the case of trusted non-3GPP access includes the following: + +- Terminates the N2 and N3 interfaces. +- Terminates the EAP-5G signalling and behaves as authenticator when the UE attempts to register to 5GC via the TNAN. +- Implements the AMF selection procedure. + +- Transparently relays NAS messages between the UE and the AMF, via NWt. +- Handles N2 signalling with SMF (relayed by AMF) for supporting PDU sessions and QoS. +- Transparently relays PDU data units between the UE and UPF(s). +- Implements a local mobility anchor within the TNAN. +- Packet marking in the downlink, and the uplink on N2 and N3, as for the N3IWF (clause 6.2.9). + +### 6.2.10 AF + +The Application Function (AF) interacts with the 3GPP Core Network in order to provide services, for example to support the following: + +- Application Function influence on traffic routing (see clause 5.6.7); +- Application Function influence on Service Function Chaining (see clause 5.6.16.2); +- Accessing Network Exposure Function (see clause 5.20); +- Interacting with the Policy and charging control framework (see clause 5.14); +- Time synchronization service (see clause 5.27.1.8); +- IMS interactions with 5GC (see clause 5.16). +- Support PDU Set Handling as defined in clause 5.37.5. + +Based on operator deployment, Application Functions considered to be trusted by the operator can be allowed to interact directly with relevant Network Functions. + +Application Functions not allowed by the operator to access directly the Network Functions shall use the external exposure framework (see clause 7.3) via the NEF to interact with relevant Network Functions. + +The functionality and purpose of Application Functions are only defined in this specification with respect to their interaction with the 3GPP Core Network. + +### 6.2.11 UDR + +The Unified Data Repository (UDR) supports the following functionality: + +- Storage and retrieval of subscription data by the UDM. +- Storage and retrieval of policy data by the PCF. +- Storage and retrieval of structured data for exposure. +- Application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs, 5G-VN group information for 5G-VN management). +- Storage and retrieval of NF Group ID corresponding to subscriber identifier (e.g. IMPI, IMPU, SUPI). + +The Unified Data Repository is located in the same PLMN as the NF service consumers storing in and retrieving data from it using Nudr. Nudr is an intra-PLMN interface. + +NOTE 1: Deployments can choose to collocate UDR with UDSF. + +### 6.2.12 UDSF + +The UDSF is an optional function that supports the following functionality: + +- Storage and retrieval of information as unstructured data by any NF. Notify a NF consumer if information validity has expired. + +- Timer service to any NF. + +NOTE 1: Structured data in this specification refers to data for which the structure is defined in 3GPP specifications. Unstructured data refers to data for which the structure is not defined in 3GPP specifications. + +NOTE 2: Deployments can choose to collocate UDSF with UDR. + +### 6.2.13 SMSF + +The SMSF supports the following functionality to support SMS over NAS: + +- SMS management subscription data checking and conducting SMS delivery accordingly. +- SM-RP/SM-CP with the UE (see TS 24.011 [6]). +- Relay the SM from UE toward SMS-GMSC/IWMSC/SMS-Router. +- Relay the SM from SMS-GMSC/IWMSC/SMS-Router toward the UE. +- SMS charging. +- Lawful Interception. +- Interaction with AMF and SMS-GMSC for notification procedure that the UE is unavailable for SMS transfer (i.e, notifies SMS-GMSC to inform UDM when UE is unavailable for SMS). + +### 6.2.14 NSSF + +The Network Slice Selection Function (NSSF) supports the following functionality: + +- Selecting the set of Network Slice instances serving the UE; +- Determining the Allowed NSSAI and, if needed, the mapping to the Subscribed S-NSSAIs; +- Determining the Configured NSSAI and, if needed, the mapping to the Subscribed S-NSSAIs; +- Determining the AMF Set to be used to serve the UE, or, based on configuration, a list of candidate AMF(s), possibly by querying the NRF; +- The NSSF may provide support for Network Slice restriction and Network Slice instance restriction based on NWDAF analytics. +- Determining whether an S-NSSAI has to be replaced and providing to the AMF the indication that the S-NSSAI is unavailable and a corresponding Alternative S-NSSAI, e.g. based on received NWDAF analytics (e.g. for Service Experience for a Network Slice or Slice load level), or local trigger from the OAM system. + +### 6.2.15 5G-EIR + +The 5G-EIR is an optional network function that supports the following functionality: + +- Check the status of PEI (e.g. to check that it has not been prohibited). + +### 6.2.16 LMF + +The functionality of LMF is defined in clause 4.3.8 of TS 23.273 [87]. + +### 6.2.16A GMLC + +The functionality of GMLC is defined in clause 4.3.8 of TS 23.273 [87]. + +### 6.2.17 SEPP + +The Security Edge Protection Proxy (SEPP) is a non-transparent proxy and supports the following functionality: + +- Message filtering and policing on inter-PLMN control plane interfaces. + +NOTE: The SEPP protects the connection between Service Consumers and Service Producers from a security perspective, i.e. the SEPP does not duplicate the Service Authorization applied by the Service Producers as specified in clause 7.1.4. + +- Topology hiding. + +Detailed functionality of SEPP, related flows and the N32 reference point, are specified in TS 33.501 [29]. + +The SEPP applies the above functionality to every Control Plane message in inter-PLMN signalling, acting as a service relay between the actual Service Producer and the actual Service Consumer. For both Service Producer and Consumer, the result of the service relaying is equivalent to a direct service interaction. Every Control Plane message in inter-PLMN signalling between the SEPPs may pass via IPX entities. More details on SEPPs and the IPX entities are described in TS 29.500 [49] and TS 33.501 [29]. + +### 6.2.18 Network Data Analytics Function (NWDAF) + +The Network Data Analytics Function (NWDAF) includes one or more of the following functionalities: + +- Support data collection from NFs and AFs; +- Support data collection from OAM; +- Support retrieval of information from data repositories (e.g. UDR via UDM for subscriber-related information or via NEF(PFDF) for PFD information); +- Support data collection of location information from LCS system; +- NWDAF service registration and metadata exposure to NFs and AFs; +- Support analytics information provisioning to NFs and AFs; +- Support Machine Learning (ML) model training and provisioning to NWDAFs (containing Analytics logical function); +- Support bulked data related to Analytics ID(s) provisioning for NFs; +- Support accuracy information about Analytics IDs provisioning for NFs; +- Support accuracy information or accuracy degradation about ML model provisioning for NFs; +- Support roaming exchange capability to exchange data and analytics between PLMNs; +- Support Federated Learning (FL) to train an ML model among multiple NWDAFs (containing MTLF). + +The details of the NWDAF functionality are defined in TS 23.288 [86]. + +NOTE 1: Some or all of the NWDAF functionalities can be supported in a single instance of an NWDAF. + +NOTE 2: NWDAF functionality beyond its support for Nnwdaf is out of scope of 3GPP. + +### 6.2.19 SCP + +The Service Communication Proxy (SCP) includes one or more of the following functionalities. Some or all of the SCP functionalities may be supported in a single instance of an SCP: + +- Indirect Communication (see clause 7.1.1 for details). +- Delegated Discovery (see clauses 7.1.1 and 6.3.1 for details). + +- Message forwarding and routing to destination NF/NF service. +- Message forwarding and routing to a next hop SCP. +- Communication security (e.g. authorization of the NF Service Consumer to access the NF Service Producer API), load balancing, monitoring, overload control, etc. +- Optionally interact with UDR, to resolve the UDM Group ID/UDR Group ID/AUSF Group ID/PCF Group ID/CHF Group ID/HSS Group ID based on UE identity, e.g. SUPI or IMPI/IMPU (see clause 6.3.1 for details). + +NOTE 1: Communication security, e.g. authorization of the NF Service Consumer to access the NF Service Producer's API is specified in TS 33.501 [29]. + +NOTE 2: Load balancing, monitoring, overload control functionality provided by the SCP is left up to implementation. + +The SCP may be deployed in a distributed manner. + +NOTE 3: More than one SCP can be present in the communication path between NF Services. + +SCPs can be deployed at PLMN level, shared-slice level and slice-specific level. It is left to operator deployment to ensure that SCPs can communicate with relevant NRFs. + +In order to enable SCPs to route messages through several SCPs (i.e. next SCP hop discovery, see clause 6.3.16), an SCP may register its profile in the NRF. Alternatively, local configuration may be used. + +### 6.2.20 W-AGF + +The functionality of W-AGF is specified in TS 23.316 [84]. + +### 6.2.21 UE radio Capability Management Function (UCMF) + +The UCMF is used for storage of dictionary entries corresponding to either PLMN-assigned or Manufacturer-assigned UE Radio Capability IDs. An AMF may subscribe with the UCMF to obtain from the UCMF new values of UE Radio Capability ID that the UCMF assigns for the purpose of caching them locally. + +Provisioning of Manufacturer-assigned UE Radio Capability ID entries in the UCMF is performed from an AF that interacts with the UCMF either directly or via the NEF (or via Network Management) using a procedure defined in TS 23.502 [3]. A UCMF that serves both EPS and 5GS shall require provisioning the UE Radio Capability ID with the TS 36.331 [51] format or TS 38.331 [28] format or both the formats of the UE radio capabilities. + +The UCMF also assigns the PLMN-assigned UE Radio Capability ID values. + +Each PLMN-assigned UE Radio Capability ID is also associated to the TAC of the UE model(s) that it is related to. When an AMF requests the UCMF to assign a UE Radio Capability ID for a set of UE radio capabilities, it indicates the TAC of the UE that the UE Radio Capability information is related to. + +The UCMF stores a Version ID value for the PLMN assigned UE Radio Capability IDs so it is included in the PLMN assigned UE Radio Capability IDs it assigns. This shall be configured in the UCMF. + +The UCMF may be provisioned with a dictionary of Manufacturer-assigned UE Radio Capability IDs which include a "Vendor ID" that applies to the Manufacturers of these UE, and a list of TACs for which the PLMN has obtained-Manufacturer-assigned UE Radio Capability IDs. + +A PLMN-assigned UE Radio Capability IDs is kept in the UCMF storage as long as it is associated with at least a TAC value. When a TAC value is related to a UE model that is earmarked for operation based on Manufacturer assigned UE Radio Capability IDs, this TAC value is disassociated in the UCMF from any PLMN assigned UE Radio Capability IDs. + +For the case that the PLMN is configured to store PLMN assigned IDs in the Manufacturer Assigned operation requested list defined in clause 4.4.1a, the UCMF does not remove from storage any PLMN assigned UE Radio Capability ID no longer used, and rather quarantines it to avoid any future reassignment. + +A UCMF dictionary entry shall include also the related UE Radio Capability for Paging for each RAT. + +### 6.2.22 TWIF + +The functionality of Trusted WLAN Interworking Function (TWIF) is specified in clause 4.2.8.5.3. + +### 6.2.23 NSSAAF + +The Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF) supports the following functionality: + +- Support for Network Slice-Specific Authentication and Authorization as specified in TS 23.502 [3] with a AAA Server (AAA-S). If the AAA-S belongs to a third party, the NSSAAF may contact the AAA-S via a AAA proxy (AAA-P). +- Support for access to SNPN using credentials from Credentials Holder using AAA server (AAA-S) as specified in clause 5.30.2.9.2 or using credentials from Default Credentials Server using AAA server (AAA-S) as specified in clause 5.30.2.10.2. If the Credentials Holder or Default Credentials Server belongs to a third party, the NSSAAF may contact the AAA server via a AAA proxy (AAA-P). + +NOTE: When the NSSAAF is deployed in a PLMN, the NSSAAF supports Network Slice-Specific Authentication and Authorization, while when the NSSAAF is deployed in a SNPN the NSSAAF can support Network Slice-Specific Authentication and Authorization and/or the NSSAAF can support access to SNPN using credentials from Credentials Holder. + +### 6.2.24 DCCF + +The Data Collection Coordination Function (DCCF) supports the following functionality: + +- Determining Data Sources that can provide data for a received data request. +- Determining whether data is already being collected from a data source. +- Instructing a Messaging Framework to send data to consumers or notification endpoints. +- Instructing a Messaging Framework to do formatting and processing of the data sent via the Messaging Framework. +- Formatting and processing of data. +- Sending data to consumers or notification endpoints. +- Registering NWDAFs and ADRFs that are already receiving data from a Data Source. + +The DCCF functionality is specified in TS 23.288 [86]. + +### 6.2.25 MFAF + +The Messaging Framework Adaptor Function (MFAF) supports the following functionality: + +- Interfacing with a DCCF that controls how a messaging framework will process, format and send data to consumers or notification endpoints. +- Receiving data from Data Sources via services offered by those Data Sources. +- Sending data received from Data Sources to a messaging framework (outside the scope of 3GPP). +- Receiving data from a messaging framework (outside the scope of 3GPP). +- Processing, formatting and sending data to specified consumers or notification endpoints. + +NOTE: The internal logic of Messaging Framework is outside the scope of 3GPP, only MFAF and the interface between MFAF and other 3GPP defined NF is under 3GPP scope. + +The MFAF functionality is specified in TS 23.288 [86]. + +### 6.2.26 ADRF + +The Analytics Data Repository Function (ADRF) supports the following functionality: + +- Storage and retrieval of analytics generated by NWDAFs and collected data. +- Storage and retrieval of ML model files trained by NWDAFs containing MTLF. + +The Analytics Data Repository Function (ADRF) is specified in TS 23.288 [86]. + +### 6.2.27 MB-SMF + +The functionality of MB-SMF is specified in TS 23.247 [129]. + +#### 6.2.27a MB-UPF + +The functionality of MB-UPF is specified in TS 23.247 [129]. + +#### 6.2.27b MBSF + +The functionality of MBSF is specified in TS 23.247 [129]. + +### 6.2.27c MBSTF + +The functionality of MBSTF is specified in TS 23.247 [129]. + +### 6.2.28 NSACF + +The Network Slice Admission Control Function (NSACF) supports the following functionality: + +- Support of monitoring and controlling the number of registered UEs per network slice. +- Support of monitoring and controlling the number of UEs with at least one PDU Session/PDN Connection per network slice in case of EPC interworking. +- Support of monitoring and controlling the number of established PDU Sessions per network slice. +- Support of event based Network Slice status notification and reports to a consumer NF. +- Acting as a Centralized NSACF in PLMNs deploying a centralized architecture as described in clause 5.15.11.0. +- Support of different type of NSAC modes for roaming UEs for the number of UEs per network slice. +- Support of different type of NSAC modes for roaming UEs for the number of PDU Sessions per network slice. +- Acting as a Primary NSACF in PLMNs deploying a hierarchal architecture as described in clause 5.15.11.0. + +The details of the NSACF functionality are defined in clause 5.15.11. + +### 6.2.29 TSCTSF + +The Time Sensitive Communication and Time Synchronization Function (TSCTSF) supports the following functionality: + +- Associating the time synchronization service request (see clause 5.27.1.8) from the NF consumer to the AF sessions with the PCF (the session between the PCF and TSCTSF). +- Controlling time synchronization service request from the NF consumer, (g)PTP-based time distribution and ASTI-based time distribution based on subscription data. The TSCTSF may be pre-configured with one or several PTP instance configurations. For each PTP instance configuration, it may contain: + - a reference to the PTP instance configuration. + +- PTP profile. +- PTP domain. +- Detecting and reporting time synchronization service status based on NG-RAN and UPF/NW-TT timing synchronization status information and reporting status updates. +- Managing the DS-TT and NW-TT via exchange of PMIC and UMIC as described in Annex K. +- Detecting availability of 5GS Bridge/Router information (including user plane node ID that applies also for IP type PDU Sessions) as reported by PCF for both Ethernet and IP type PDU Sessions (including the need to (un)subscribe 5GS Bridge/Router information Notification from PCF). +- Creating the TSC Assistance Container based on individual traffic pattern parameters from the NEF/AF or DetNet controller and providing it to the PCF. +- Determining the Requested PDB by subtracting the UE-DS-TT Residence Time from the Requested 5GS Delay provided by the NEF/AF or DetNet controller and providing the determined Requested PDB to the PCF. +- Discovering the AMFs serving the list of TA(s) that comprise the spatial validity condition from the NRF or AMFs serving the UE(s) from the UDM and subscribing to the discovered AMF(s) to receive notifications about presence of the UE in an Area of Interest. +- Discovering the AMF(s) serving a UE or a list of TA(s) and subscribing to gNB's node-level timing synchronization status. +- Obtaining gNB's and UPF's node-level timing synchronization status information as defined in clause 5.27.1.12. +- Determining the spatial validity condition from the requested coverage area by the NEF/AF and enforcing time synchronization service for the requested coverage area. +- Support for RAN feedback for BAT offset and adjusted periodicity as defined in clause 5.27.2.5. +- In the case of support of integration with IETF Deterministic Networking (as depicted in clauses 4.4.8.4 and 5.28.5), acting as a stateful translator function between a DetNet controller and 5G System Network Functions and Procedures, including the NW-TT. This includes exposing the information about the 5GS router to the DetNet controller and mapping 5GS router configuration parameters provided by the DetNet controller to 5G System parameters. The details are defined in clause 5.28.5. + +### 6.2.30 5G DDNMF + +The functionality of 5G DDNMF is defined in TS 23.304 [128]. + +### 6.2.31 EASDF + +The functionality of EASDF is defined in TS 23.548 [130]. + +### 6.2.32 TSN AF + +The TSN AF supports control plane translator functionality for the integration of the 5GS with a TSN network, this involves e.g.: + +- 5GS Bridge management. +- Port and bridge management information exchange with DS-TT or NW-TT. +- Interactions with the CNC for 5GS Bridge configuration and reporting. +- determining the TSC Assistance Container and TSN QoS information by mapping TSN Stream(s) based on IEEE standards. The traffic pattern parameter determination may be based on PSFP (IEEE Std 802.1Q [98]) as specified in Annex I, clause I.1. + +### 6.2.33 NSWOF + +The NSWOF interfaces the WLAN access network using the SWa interface as defined in TS 23.402 [43] and interfaces the AUSF using the Nausf SBI performing protocol translation and AUSF discovery (see clause 6.3.4). + +## 6.3 Principles for Network Function and Network Function Service discovery and selection + +### 6.3.1 General + +The NF discovery and NF service discovery enable Core Network entities (NFs or Service Communication Proxy (SCP)) to discover a set of NF instance(s) and NF service instance(s) for a specific NF service or an NF type. NF service discovery is enabled via the NF discovery procedure, as specified in clauses 4.17.4, 4.17.5, 4.17.9 and 4.17.10 of TS 23.502 [3]. + +Unless the expected NF and NF service information is locally configured on the requester NF, e.g. when the expected NF service or NF is in the same PLMN as the requester NF, the NF and NF service discovery is implemented via the Network Repository Function (NRF). NRF is the logical function that is used to support the functionality of NF and NF service discovery and status notification as specified in clause 6.2.6. + +NOTE 1: NRF can be colocated together with SCP e.g. for communication option D, depicted in Annex E. + +In order for the requested NF type or NF service to be discovered via the NRF, the NF instance need to be registered in the NRF. This is done by sending a Nnrf\_NFManagement\_NFRegister containing the NF profile. The NF profile contains information related to the NF instance, such as NF instance ID, supported NF service instances (see clause 6.2.6 for more details regarding the NF profile). The registration may take place e.g. when the producer NF instance and its NF service instance(s) become operative for the first time. The NF service registration procedure is specified in clause 4.17.1 of TS 23.502 [3]. + +In order for the requester NF or SCP to obtain information about the NF and/or NF service(s) registered or configured in a PLMN/slice, based on local configuration the requester NF or SCP may initiate a discovery procedure with the NRF by providing the type of the NF and optionally a list of the specific service(s) it is attempting to discover. The requester NF or SCP may also provide other service parameters e.g. slicing related information. For the detailed service parameter(s) used for specific NF and NF service discovery refer to clause 5.2.7.3.2 of TS 23.502 [3]. The requester NF may also provide NF Set related information to enable reselection of NF instances within the NF set. The requester NF may also provide the required supported features of the NF. + +For some Network Functions which have access to the subscription data (e.g. HSS, UDM) the NRF may need to resolve the NF Group ID corresponding to a subscriber identifier. If the NRF has no stored configuration mapping identity sets/ranges to NF Group ID locally, the NRF may retrieve the NF Group ID corresponding to a specific subscriber identifier from the UDR using the Nudr\_GroupIDmap\_Query service operation. + +In the case of Indirect Communication, a NF Service Consumer employs an SCP which routes the request to the intended target of the request. + +If the requester NF is configured to delegate discovery, the requester NF may omit the discovery procedure with the NRF and instead delegate the discovery to the SCP; the SCP will then act on behalf of the requester NF. In this case, the requester NF adds any necessary discovery and selection parameters to the request in order for the SCP to be able to do discovery and associated selection. The SCP may interact with the NRF to perform discovery and obtain discovery result and it may interact with the NRF or UDR to obtain NF Group ID corresponding to subscriber identifier. + +NOTE 2: For delegated discovery of the HSS or the UDM, the SCP can rely on the NRF to discover the group of HSS/UDM instance(s) serving the provided user identity, or in some deployments the SCP can first query the UDR for the HSS/UDM Group ID for the provided user identity. It is expected that the stage 3 defines a single encoding for the user identity provided by the service consumer that can be used for both variants of delegated discovery to avoid that the service consumer needs to be aware of the SCP behaviour. + +The NRF provides a list of NF instances and NF service instances relevant for the discovery criteria. The NRF may provide the IP address or the FQDN of NF instance(s) and/or the Endpoint Address(es) of relevant NF service instance(s) to the NF Consumer or SCP. The NRF may also provide NF Set ID and/or NF Service Set ID to the NF Consumer or SCP. The response contains a validity period during which the discovery result is considered valid and can + +be cached. The result of the NF and NF service discovery procedure is applicable to any subscriber that fulfils the same discovery criteria. The entity that does the discovery may cache the NF profile(s) received from the NF/NF service discovery procedure. During the validity period, the cached NF profile(s) may be used for NF selection for any subscriber matching the discovery criteria. + +NOTE 3: Refer to TS 29.510 [58] for details on using the validity period. + +In the case of Direct Communication, the requester NF uses the discovery result to select NF instance and a NF service instance that is able to provide a requested NF Service (e.g. a service instance of the PCF that can provide Policy Authorization). + +In the case of Indirect Communication without Delegated Discovery, the requester NF uses the discovery result to select a NF instance while the associated NF service instance selection may be done by the requester NF and/or an SCP on behalf of the requester NF. + +In both the cases above, the requester NF may use the information from a valid cached discovery result for subsequent selections (i.e. the requester NF does not need to trigger a new NF discovery procedure to perform the selection). + +In the case of Indirect Communication with Delegated Discovery, the SCP will discover and select a suitable NF instance and NF service instance based on discovery and selection parameters provided by the requester NF and optional interaction with the NRF. The NRF to be used may be provided by the NF consumer as part of the discovery parameters, e.g. as a result of a NSSF query. The SCP may use the information from a valid cached discovery result for subsequent selections (i.e. the SCP does not need to trigger a new NF discovery procedure to perform the selection). + +NOTE 4: In a given PLMN, Direct Communication, Indirect Communication, or both may apply. + +The requester NF or SCP may subscribe to receive notifications from the NRF of a newly updated NF profile of an NF (e.g. NF service instances taken in or out of service), or newly registered de-registered NF instances. The NF/NF service status subscribe/notify procedure is defined in clauses 4.17.7 and 4.17.8 of TS 23.502 [3]. + +For NF and NF service discovery across PLMNs, the NRF in the local PLMN interacts with the NRF in the remote PLMN to retrieve the NF profile(s) of the NF instance(s) in the remote PLMN that matches the discovery criteria. The NRF in the local PLMN reaches the NRF in the remote PLMN by forming a target PLMN specific query using the PLMN ID provided by the requester NF. The NF/NF service discovery procedure across PLMNs is specified in clause 4.17.5 of TS 23.502 [3]. + +NOTE 5: See TS 29.510 [58] for details on using the target PLMN ID specific query to reach the NRF in the remote PLMN. + +For topology hiding, see clause 6.2.17. + +#### 6.3.1.0 Principles for Binding, Selection and Reselection + +Binding can be used to indicate suitable target NF producer instance(s) for NF service instance selection, reselection and routing of subsequent requests associated with a specific NF producer resource (context) and NF service. This allows the NF producer to indicate that the NF consumer, for a particular context, should be bound to an NF service instance, NF instance, NF service set or NF set depending on local policies and other criteria (e.g. at what point it is in the middle of a certain procedure, considering performance aspects etc). + +Binding can also be used by the NF consumer to indicate suitable NF consumer instance(s) for notification target instance reselection and routing of subsequent notification requests associated with a specific notification subscription and for providing Binding Indication for service(s) that the NF consumer produces for the same data context and the NF service producer is subsequently likely to invoke. + +The Binding Indication contains the information in Table 6.3.1.0-1. + +The Routing Binding Indication may be included in Request, Subscribe or Notification messages (see clause 7.1.2). It may be used in the case of indirect communication by the SCP to route the message. The Routing Binding Indication is a copy of the information in the Binding Indication and also contains the information in Table 6.3.1.0-1. + +NOTE 1: Subscription request messages can contain both a Binding Indication and a Routing Binding Indication. + +The NF service producer may provide a Binding Indication to the NF service consumer as part of the Direct or Indirect Communication procedures, to be used in subsequent related service requests. The level of Binding Indication provided by the NF service producer to the NF consumer indicates if the resource in the NF service producer is either bound to + +NF service instance, NF instance, NF Service Set or NF set as specified in Table 6.3.1.0-1. The Binding Indication may include NF Service Set ID, NF Set ID, NF instance ID, or NF service instance ID, for use by the NF consumer or SCP for NF Service Producer (re-)selection. If the resource is created in the NF Service Producer, the NF Service Producer provides resource information which includes the endpoint address of the NF service producer. For indirect communication, the NF service consumer copies the Binding Indication into the Routing Binding Indication in Request or Subscribe message, unless the NF service consumer performs a reselection for indirect communication without delegated discovery. + +During explicit or implicit notification subscription, a Binding Indication may be provided by the NF service consumer to NF service producer; the NF service consumer will also provide a Notification Endpoint. The NF service consumer may also provide a Binding Indication in response to notification requests. The level of Binding Indication provided by the NF service consumer to the NF service provider indicates if the Notification Endpoint is either bound to NF service instance, NF instance, NF Service Set or NF set as specified in Table 6.3.1.0-1. The Binding Indication shall include at least one of NF Set ID, NF instance ID, NF Service Set ID and/or NF service instance ID, and may also include the service name. The NF Service Set ID, NF service instance ID, and service name relate to the service of the NF service consumer that will handle the notification. + +NOTE 2: The NF service can either be a standardised service as per this specification or a custom service. The custom service can be used for the sole purpose of registering endpoint address(es) to receive notifications at the NRF. + +The Binding Indication is used by the NF service producer as notification sender to reselect an endpoint address and construct the Notification Endpoint, i.e. the URI where the notification is to be sent, e.g. if the provided Notification Endpoint of the NF service consumer included in the subscription cannot be reached, according to the following: + +- If the service name in the Binding Indication is omitted and the binding for notification is on NF Set or NF Instance level, the endpoint address registered in the NRF at NF Profile level of the NF(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. +- If the service name is included in the Binding Indication, an endpoint address registered in the NRF for that service in the NF profile(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. + +For indirect communication, the NF service producer copies the Binding Indication into the Routing Binding Indication that is included in the Notification request, to be used by the SCP to discover an alternative endpoint address and construct a Notification Endpoint e.g. if the Notification Endpoint that the request targets cannot be reached, according to the following: + +- If the service name in the Routing Binding Indication is omitted and the binding for notification is on NF Set or NF Instance level, the endpoint address registered in the NRF at NF Profile level of the NF(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. +- If the service name is included in the Routing Binding Indication, an endpoint address registered in the NRF for that service in the NF profile(s) selected according to the Binding Indication shall be used to construct a new Notification Endpoint. + +For subscription to notifications via another network function, a separate Binding Indication for subscription related events may be provided by the NF service consumer (see clause 4.17.12.4 of TS 23.502 [3]) and if provided shall be associated with an applicability indicating notification for subscription related events. + +If the NF as an NF consumer provides a Binding Indication for services that the NF produces in service requests, the Binding Indication shall be associated with an applicability indicating other service and may contain the related service name(s), in addition to the other parameters listed in Table 6.3.1.0-1. If no service name(s) are provided, the Binding Indication relates to all services that the NF produces. + +For NF Set or NF Instance level of binding, a Binding Indication for notifications and other services may be combined if it relates to the same service, and that combined Binding Indication shall then be associated with an applicability indicating all scenarios that the Binding Indication relates to (For this purpose, the applicability can indicate a combination of values). + +If no applicability is indicated in a request or subscribe messages, a Binding Indication in that messages is applicable for notification to all events except for the subscription related event (see clause 4.17.12.4 of TS 23.502 [3]). + +NOTE 3: Such a request message can be used for implicit subscription. + +NOTE 4: Request messages can contain both the Binding Indications for services and for notifications, and in addition, the Routing Binding Indication in the case of indirect communication. + +A Binding Indication may be shared by a group of resources (e.g. contexts) identified by a group identifier. This enables a NF Service consumer or producer to update the binding indication for this group of resources in a single request or notification towards a given peer NF service instance, e.g. when a group of resources need to be taken over by a different NF within an NF set. See clause 6.12.1 of TS 29.500 [49]. + +Table 6.3.1.0-1 defines the selection and reselection behaviour of NF services consumers and SCPs depending on the Binding Indication provided by an NF service producer. The detailed procedures refer to clause 4.17.11 and 4.17.12 of TS 23.502 [3]. + +**Table 6.3.1.0-1: Binding, selection and reselection** + +| Level of Binding Indication | The NF Consumer / Notification sender / SCP selects | The NF Consumer / Notification sender / SCP can reselect e.g. when selected producer is not available | Binding information for selection and reselection | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| +| NF Service Instance | The indicated NF Service Instance | An equivalent NF Service instance:
  • - within the NF Service Set (if applicable)
  • - within the NF instance
  • - within the NF Set (if applicable)
| NF Service Instance ID, NF Service Set ID, NF Instance ID, NF Set ID, Service name (NOTE 4) | +| NF Service Set | Any NF Service instance within the indicated NF Service Set | Any NF Service instance within an equivalent NF Service Set within the NF Set (if applicable) (Note 2) | NF Service Set ID, NF Instance ID, NF Set ID, Service name (NOTE 4) | +| NF Instance | Any equivalent NF Service instance within the NF instance. | Any equivalent NF Service instance within a different NF instance within the NF Set (if applicable) | NF Instance ID, NF Set ID, Service name (NOTE 4) | +| NF Set | Any equivalent NF Service instance within the indicated NF Set | Any equivalent NF Service instance within the NF Set | NF Set ID, Service name (NOTE 4) | +| NOTE 1: if the Binding Indication is not available, the NF Consumer routes the service request to the target based on routing information available. | | | | +| NOTE 2: NF Service Sets in different NFs are considered equivalent if they include same type and variant (e.g. identical NF Service Set ID) of NF Services. | | | | +| NOTE 3: If a Routing Binding Indication is not available, the SCP routes the service request to the target based on available routing information. | | | | +| NOTE 4: The service name is only applicable if the Binding Indication relates to a notification target or If the NF as a NF consumer provides a Binding Indication for services that the NF produces. | | | | + +#### 6.3.1.1 NF Discovery and Selection aspects relevant with indirect communication + +For indirect communication shown in Annex E, the SCP performs the following functionalities regarding Network Function and Network Function Service discovery and selection: + +- If the request includes a Routing Binding Indication, the SCP shall route the service request to the requested target as specified in Table 6.3.1.0-1. If the Routing Binding Indication does not exist, the SCP may get the NF Set ID from the NRF or local configuration (if available). +- If the request recipient had previously provided a Binding Indication, then the request sender shall include a Routing Binding Indication with the same contents in subsequent related requests. + +#### 6.3.1.2 Location information + +The location information describes the network location of the NF instance. It can consist of one or more levels. Each level describes one location aspect, such as geographic location, data centre, cluster, etc. An NF instance has only one location. + +The location information may be used to select the NF service instance or NF instance from a particular network location based on local configuration. + +NOTE: The location information in TS 29.510 [58] specifies the granularity of location information. It is up to each deployment to determine the granularity of location information to be used. + +### 6.3.2 SMF discovery and selection + +The SMF selection functionality is supported by the AMF and SCP and is used to allocate an SMF that shall manage the PDU Session. The SMF selection procedures are described in clause 4.3.2.2.3 of TS 23.502 [3]. + +The SMF discovery and selection functionality follows the principles stated in clause 6.3.1. + +If the AMF does discovery, the AMF shall utilize the NRF to discover SMF instance(s) unless SMF information is available by other means, e.g. locally configured on AMF. The AMF provides UE location information to the NRF when trying to discover SMF instance(s). The NRF provides NF profile(s) of SMF instance(s) to the AMF. In addition, the NRF also provides the SMF service area of SMF instance(s) to the AMF. The SMF selection functionality in the AMF selects an SMF instance and an SMF service instance based on the available SMF instances obtained from NRF or on the configured SMF information in the AMF. + +NOTE 1: Protocol aspects of the access to NRF are specified in TS 29.510 [58]. + +The SMF selection functionality is applicable to both 3GPP access and non-3GPP access. + +The SMF selection for Emergency services is described in clause 5.16.4.5. + +The following factors may be considered during the SMF selection: + +- Selected Data Network Name (DNN). In the case of the home routed roaming, the DNN is not applied for the V-SMF selection. +- S-NSSAI of the HPLMN (for non-roaming and home-routed roaming scenarios), and S-NSSAI of the VPLMN (for roaming with local breakout and home-routed roaming scenarios). +- NSI-ID. + +NOTE 2: The use of NSI -ID in the network is optional and depends on the deployment choices of the operator. If used, the NSI ID is associated with S-NSSAI. + +- Access technology being used by the UE. +- Support for Control Plane CIoT 5GS Optimisation. +- Subscription information from UDM, e.g. + - per DNN: whether LBO roaming is allowed. + - per DNN: whether HR-SBO roaming is allowed. + - per S-NSSAI: the subscribed DNN(s). + - per (S-NSSAI, subscribed DNN): whether LBO roaming is allowed. + - per (S-NSSAI, subscribed DNN): whether HR-SBO roaming is allowed. + - per (S-NSSAI, subscribed DNN): whether EPC interworking is supported. + - per (S-NSSAI, subscribed DNN): whether selecting the same SMF for all PDU sessions to the same S-NSSAI and DNN is required. + +- per (S-NSSAI, DNN) associated with 5G VN group: Service Area (LADN service area) for the 5G VN group. In the case of SMF selection for a PDU Session targeting 5G VN group, the AMF may prefer candidate SMF(s) that have an intersection with the LADN service area of the 5G VN group. + +g) Void. + +h) Local operator policies. + +NOTE 3: These policies can take into account whether the SMF to be selected is an I-SMF or a V-SMF or a SMF. + +i) Load conditions of the candidate SMFs. + +j) Analytics (i.e. statistics or predictions) for candidate SMFs' load as received from NWDAF (see TS 23.288 [86]), if NWDAF is deployed. + +k) UE location (i.e. TA). + +l) Service Area of the candidate SMFs. + +m) Capability of the SMF to support a MA PDU Session. + +n) If interworking with EPS is required. + +o) Preference of V-SMF support. This is applicable only for V-SMF selection in the case of home routed roaming. + +p) Target DNAI. + +q) Capability of the SMF to support User Plane Remote Provisioning (see clause 5.30.2.10.4.3). + +r) Supported DNAI list. + +s) HR-SBO support (according to clause 6.7 of TS 23.548 [130]). + +t) Capability of the SMF (V-SMF and H-SMF) to support non-3GPP access path switching. + +To support the allocation of a static IPv4 address and/or a static IPv6 prefix as specified in clause 5.8.2.2.1, a dedicated SMF may be deployed for the indicated combination of DNN and S-NSSAI and registered to the NRF, or provided by the UDM as part of the subscription data. + +In the case of delegated discovery, the AMF, shall send all the available factors a)-d), k) and n) to the SCP. + +In addition, the AMF may indicate to the SCP which NRF to use (in the case of NRF dedicated to the target slice). + +If there is an existing PDU Session and the UE requests to establish another PDU Session to the same DNN and S-NSSAI of the HPLMN, and the UE subscription data indicates the support for interworking with EPS for this DNN and S-NSSAI of the HPLMN or UE subscription data indicates the same SMF shall be selected for all PDU sessions to the same S-NSSAI, DNN, the same SMF in non roaming and LBO case or the same H-SMF in home routed roaming case, shall be selected. In addition, if the UE Context in the AMF provides a SMF ID for an existing PDU session to the same DNN, S-NSSAI, the AMF uses the stored SMF ID for the additional PDU Session. In any such a case where the AMF can determine which SMF should be selected, if delegated discovery is used, the AMF shall indicate a desired NF Instance ID so that the SCP is able to route the message to the relevant SMF. Otherwise, if UE subscription data does not indicate the support for interworking with EPS for this DNN and S-NSSAI, a different SMF in non roaming and LBO case or a different H-SMF in home routed roaming case, may be selected. For example, to support a SMF load balancing or to support a graceful SMF shutdown (e.g. a SMF starts to no more take new PDU Sessions). + +In the home-routed roaming case, the SMF selection functionality selects an SMF in VPLMN based on the S-NSSAI of the VPLMN, as well as an SMF in HPLMN based on the S-NSSAI of the HPLMN. This is specified in clause 4.3.2.2.3.3 of TS 23.502 [3]. + +If the HR-SBO roaming is allowed for the PDU Session, the DNN is also considered for V-SMF selection. + +When the UE requests to establish a PDU Session to a DNN and an S-NSSAI of the HPLMN, if the UE MM Core Network Capability indicates the UE supports EPC NAS and optionally, if the UE subscription indicates the support for interworking with EPS for this DNN and S-NSSAI of the HPLMN, the selection functionality (in AMF or SCP) selects a combined SMF+PGW-C. Otherwise, a standalone SMF may be selected. + +If the UDM provides a subscription context that allows for handling the PDU Session in the VPLMN (i.e. using LBO) for this DNN and S-NSSAI of the HPLMN and, optionally, the AMF is configured to know that the VPLMN has a suitable roaming agreement with the HPLMN of the UE, the following applies: + +- If the AMF does discovery, the SMF selection functionality in AMF selects an SMF from the VPLMN. +- If delegated discovery is used, the SCP selects an SMF from the VPLMN. + +If an SMF in the VPLMN cannot be derived for the DNN and S-NSSAI of the VPLMN, or if the subscription does not allow for handling the PDU Session in the VPLMN using LBO, then the following applies: + +- If the AMF does discovery, both an SMF in VPLMN and an SMF in HPLMN are selected, and the DNN and S-NSSAI of the HPLMN is used to derive an SMF identifier from the HPLMN. +- If delegated discovery is used: + - The AMF performs discovery and selection of H-SMF from NRF. The AMF may indicate the maximum number of H-SMF instances to be returned from NRF, i.e. SMF selection at NRF. + - The AMF sends Nsmf\_PDUSession\_CreateSMContext Request to SCP, which includes the endpoint (e.g. URI) of the selected H-SMF, and the discovery and selection parameters as defined in this clause, i.e. parameter for V-SMF selection. The SCP performs discovery and selection of the V-SMF and forwards the request to the selected V-SMF. + - The V-SMF sends the Nsmf\_PDUSession\_Create Request towards the H-SMF via the SCP; the V-SMF uses the received endpoint (e.g. URI) of the selected H-SMF to construct the target destination to be addressed. The SCP forwards the request to the H-SMF. + - Upon reception of a response from V-SMF, based on the received V-SMF ID the AMF obtains the Service Area of the V-SMF from NRF. The AMF uses the Service Area of the V-SMF to determine the need for V-SMF relocation upon subsequent UE mobility. + +If the initially selected SMF in VPLMN (for roaming with LBO) detects it does not understand information in the UE request, it may reject the N11 message (related with a PDU Session Establishment Request message) with a proper N11 cause triggering the AMF to select both a new SMF in the VPLMN and a SMF in the HPLMN (for home routed roaming). + +The AMF selects SMF(s) considering support for CIoT 5GS optimisations (e.g. Control Plane CIoT 5GS Optimisation). + +In the case of onboarding of UEs for SNPNs, when the UE is registered for SNPN onboarding the AMF selects SMF(s) of Onboarding Network considering the Capability of SMF to support User Plane Remote Provisioning. + +Additional details of AMF selection of an I-SMF are described in clause 5.34. + +In the case of home routed scenario, the AMF selects a new V-SMF if it determines that the current V-SMF cannot serve the UE location. The selection/relocation is same as an I-SMF selection/relocation as described in clause 5.34. + +### 6.3.3 User Plane Function Selection + +#### 6.3.3.1 Overview + +The selection and reselection of the UPF for PDU session establishment, UE mobility or UE traffic offloading are performed by the SMF by considering UPF deployment scenarios such as centrally located UPF and distributed UPF located close to or at the Access Network site. The selection of the UPF shall also enable deployment of UPF with different capabilities, e.g. UPFs supporting no or a subset of optional functionalities. + +The UPF selection for PDU session establishment in home routed roaming case, the UPF(s) in home PLMN is selected by SMF(s) in HPLMN, and the UPF(s) in the VPLMN is selected by SMF(s) in VPLMN. The exact set of parameters used for the selection mechanism is deployment specific and controlled by the operator configuration. + +The UPF selection for PDU session establishment, UE mobility or UE traffic offloading involves: + +- a step of SMF Provisioning of available UPF(s). This step may take place while there is no PDU Session to establish and may be followed by N4 Node Level procedures defined in clause 4.4.3 of TS 23.502 [3] where the UPF and the SMF may exchange information such as the support of optional functionalities and capabilities. +- A step of selection of an UPF for a particular PDU Session; it is followed by N4 session management procedures defined in clause 4.4.1 of TS 23.502 [3]. + +To collect the data from the UPF as defined in clause 5.8.2.17, the related dedicated UPF is discovered and selected as following: + +- When the NF consumer or SCP directly subscribes to the UPF, the NF consumer or SCP queries the NRF including the related discovery parameter. The NRF returns the UPF(s) which meet(s) the discovery request. +- When the NF consumer or SCP shall subscribe via the SMF, the NF consumer gets the serving SMF information from the UDM per SUPI, DNN and S-NSSAI. After that, the NF consumer sends a subscription to the indicated SMF and the SMF identifies the related UPF(s) using the parameters of the subscription (e.g. target flow description, AoI, etc.) and transfers the related event subscription information to the identified UPF(s). If the NF consumer does not know the SUPI but only the UE IP address, it may need to invoke the BSF to get the SUPI corresponding to the triplet (IP address, DNN and S-NSSAI). + +#### 6.3.3.2 SMF Provisioning of available UPF(s) + +SMF may be locally configured with the information about the available UPFs, e.g. by OA&M system when UPF is instantiated or removed. + +NOTE 1: UPF information can be updated e.g. by OA&M system any time after the initial provisioning, or UPF itself updates its information to the SMF any time after the node level interaction is established. + +The UPF selection functionality in the SMF may optionally utilize the NRF to discover UPF instance(s). In this case, the SMF issues a request to the NRF that may include following parameters: DNN, S-NSSAI, SMF Area Identity, the requested functionalities and capabilities (e.g. ATSSS steering capabilities, functionality associated with high data rate low latency service etc.). In its answer, the NRF provides the NF profile(s) that include(s) the IP address(es) or the FQDN of the N4 interface of corresponding UPF instance(s) to the SMF. + +UPFs may be associated with an SMF Area Identity in the NRF. This allows limiting the SMF provisioning of UPF(s) using NRF to those UPF(s) associated with a certain SMF Area Identity. This can e.g. be used in the case that an SMF is only allowed to control UPF(s) configured in NRF as belonging to a certain SMF Area Identity. + +The NRF may be configured by OAM with information on the available UPF(s) or the UPF instance(s) may register its/their NF profile(s) in the NRF. This is further defined in clause 4.17 of TS 23.502 [3]. + +#### 6.3.3.3 Selection of an UPF for a particular PDU Session + +If there is an existing PDU Session, and the SMF receives another PDU Session request to the same DNN and S-NSSAI, and if the SMF determines that interworking with EPC is supported for this PDU Session as specified in clause 4.11.5 of TS 23.502 [3], the SMF should select the same UPF, otherwise, if the SMF determines that interworking with EPC is not supported for the new PDU Session, a different UPF may be selected. + +For the same DNN and S-NSSAI if different UPF are selected at 5GC, when the UE is moved to EPC network, there is no requirement to enforce APN-AMBR. Whether and how to apply APN-AMBR for the PDN Connection associated with this DNN/APN is implementation dependent, e.g. possibly only AMBR enforcement per PDU Session applies. + +The following parameter(s) and information may be considered by the SMF for UPF selection and re-selection: + +- UPF's dynamic load. +- Analytics (i.e. statistics or predictions) for UPF load, Service Experience analytics and/or DN Performance analytics per UP path (including UPF and/or DNAI and/or AS instance) and UE related analytics (UE mobility, UE communication, and expected UE behavioural parameters) as received from NWDAF (see TS 23.288 [86]), if NWDAF is deployed. +- UPF's relative static capacity among UPFs supporting the same DNN. +- UPF location available at the SMF. + +- UE location information. +- Capability of the UPF and the functionality required for the particular UE session: An appropriate UPF can be selected by matching the functionality and features required for an UE. +- Data Network Name (DNN). +- PDU Session Type (i.e. IPv4, IPv6, IPv4v6, Ethernet Type or Unstructured Type) and if applicable, the static IP address/prefix. +- SSC mode selected for the PDU Session. +- UE subscription profile in UDM. +- DNAI as included in the PCC Rules and described in clause 5.6.7. +- Local operator policies. +- S-NSSAI. +- Access technology being used by the UE. +- Information related to user plane topology and user plane terminations, that may be deduced from: + - 5G-AN-provided identities (e.g. CellID, TAI), available UPF(s) and DNAI(s); +- Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations provided by a W-AGF or a TNGF or a TWIF; +- Information regarding the user plane interfaces of UPF(s). This information may be acquired by the SMF using N4; +- Information regarding the N3 User Plane termination(s) of the AN serving the UE. This may be deduced from 5G-AN-provided identities (e.g. CellID, TAI); +- Information regarding the N9 User Plane termination(s) of UPF(s) if needed; +- Information regarding the User plane termination(s) corresponding to DNAI(s). +- RSN, support for redundant GTP-U path or support for redundant transport path in the transport layer (as in clause 5.33.2) when redundant UP handling is applicable. +- Information regarding the ATSSS Steering Capability of the UE session (e.g. any combination of ATSSS-LL capability, MPTCP capability, MPQUIC capability) and information on the UPF support of RTT measurements without PMF. +- Support for UPF allocation of IP address/prefix. +- Support of the IPUPS functionality, specified in clause 5.8.2.14. +- Support for High latency communication (see clause 5.31.8). +- Support for functionality associated with high data rate low latency services, eXtended Reality (XR) and interactive media services, specified in clause 5.37 (for example, ECN marking for L4S, specified in clause 5.37.3, PDU Set Marking, specified in clause 5.37.5, UE power saving management, specified in clause 5.37.8). +- User Plane Latency Requirements within AF request (see clause 5.6.7.1 and clause 6.3.6 of TS 23.548 [130]). +- List of supported Event ID(s) for exposure of UPF-related information via service based interface (see clause 7.2.29 and clause 5.2.26.2 of TS 23.502 [3]). + +NOTE 1: How the SMF determines information about the user plane network topology from information listed above, and what information is considered by the SMF, is based on operator configuration. + +NOTE 2: In this release the SMF uses no additional parameters for UPF selection for a PDU Session serving TSC or Deterministic Networking. If a PDU Session needs to connect to a specific UPF hosting a specific TSN 5GS bridge or 5GS router, this can be achieved e.g. by using a dedicated DNN/S-NSSAI combination. + +A W-AGF or a TNGF may provide Identifiers of its N3 terminations when forwarding over N2 uplink NAS signalling to the 5GC. The AMF may relay this information to the SMF, as part of session management signalling for a new PDU Session. + +### 6.3.4 AUSF discovery and selection + +In the case of NF consumer based discovery and selection, the following applies: + +- The AMF and the NSWOF perform AUSF selection to allocate an AUSF Instance that performs authentication between the UE and 5G CN in the HPLMN. The AMF and the NSWOF shall utilize the NRF to discover the AUSF instance(s) unless AUSF information is available by other means, e.g. locally configured on AMF and on NSWOF. The AUSF selection function in the AMF and in the NSWOF selects an AUSF instance based on the available AUSF instances (obtained from the NRF or locally configured in the AMF). +- The UDM shall utilize the NRF to discover the AUSF instance(s) unless AUSF information is available by other means, e.g. locally configured on UDM. The UDM selects an AUSF instance based on the available AUSF instance(s) obtained from the NRF or based on locally configured information, and information stored (by the UDM) from a previously successful authentication. + +AUSF selection is applicable to both 3GPP access and non-3GPP access. + +The AUSF selection function in AUSF NF consumers or in SCP should consider one of the following factors when available: + +1. Home Network Identifier (e.g. MNC and MCC, realm) of SUCI/SUPI (by an NF consumer in the Serving network) along with the selected NID (provided by the NG-RAN) in the case of SNPN, Routing Indicator and optionally Home Network Public Key identifier (e.g. in the case that Routing Indicator is not enough to provide SUPI range granularity). + +NOTE 1: The UE provides the SUCI, which contains the Routing Indicator and Home Network Public Key identifier as defined in TS 23.003 [19], to the AMF during initial registration and to the NSWOF during NSWOF authentication. The AMF can provide the UE's Routing Indicator and optionally Home Network Public Key identifier to other AMFs as described in TS 23.502 [3]. + +NOTE 2: The usage of Home Network Public Key identifier for AUSF discovery is limited to the scenario where the AUSF NF consumers belong to the same PLMN as AUSF. + +NOTE 3: In the case of SNPN and if the UE provides an IMSI type SUCI to the AMF and the SUCI provided by UE or the SUPI derived from the SUCI is for an SNPN served by the AMF, the AMF uses the selected NID provided by the NG-RAN together with the selected PLMN ID (from IMSI) or the Routing Indicator provided by the UE within the SUCI for selection of AUSF. In the case of SNPN and the UE provides an NSI type SUCI to the AMF, the AMF uses the Home Network Identifier and Routing Indicator of SUCI/SUPI for selection of AUSF. + +When the UE's Routing Indicator is set to its default value as defined in TS 23.003 [19], the AUSF NF consumer can select any AUSF instance within the home network for the UE. + +2. AUSF Group ID the UE's SUPI belongs to. + +NOTE 4: The AMF can infer the AUSF Group ID the UE's SUPI belongs to, based on the results of AUSF discovery procedures with NRF. The AMF provides the AUSF Group ID the SUPI belongs to other AMFs as described in TS 23.502 [3]. + +3. SUPI; e.g. the AMF selects an AUSF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for AUSF discovery. + +NOTE 5: In the case of Onboarding via ON-SNPN, AUSF instances supporting UE onboarding can be registered in NRF or locally configured in the AMF. The AMF in ON-SNPN can discover and select AUSF instance(s) supporting UE onboarding based on the MCC and MNC or realm part in Home Network Identifier of the SUCI/SUPI provided by the onboarding UE. + +In the case of delegated discovery and selection in SCP, the AUSF NF consumer shall send all available factors to the SCP. + +### 6.3.5 AMF discovery and selection + +The AMF discovery and selection functionality is applicable to both 3GPP access and non-3GPP access. + +The AMF selection functionality can be supported by the 5G-AN (e.g. RAN, N3IWF) and is used to select an AMF instance for a given UE. An AMF supports the AMF selection functionality to select an AMF for relocation or because the initially selected AMF was not an appropriate AMF to serve the UE (e.g. due to change of Allowed NSSAI). Other CP NF(s), e.g. SMF, supports the AMF selection functionality to select an AMF from the AMF set when the original AMF serving a UE is unavailable. + +The TSCTSF shall use the AMF discovery functionality to determine the AMFs serving the TAs in the spatial validity condition provided by the AF. + +5G-AN selects an AMF Set and an AMF from the AMF Set under the following circumstances: + +- 1) When the UE provides no 5G-S-TMSI nor the GUAMI to the 5G-AN. +- 2) When the UE provides 5G-S-TMSI or GUAMI but the routing information (i.e. AMF identified based on AMF Set ID, AMF pointer) present in the 5G-S-TMSI or GUAMI is not sufficient and/or not usable (e.g. UE provides GUAMI with an AMF region ID from a different region). +- 3) AMF has instructed AN that the AMF (identified by GUAMI(s)) is unavailable and no target AMF is identified and/or AN has detected that the AMF has failed. +- 4) When the UE attempts to establish a signalling connection, and the following conditions are met: + - the 5G-AN knows in what country the UE is located; and + - the 5G-AN is connected to AMFs serving different PLMNs of different countries; and + - the UE provides a 5G-S-TMSI or GUAMI, which indicates an AMF serving a different country to where the UE is currently located; and + - the 5G-AN is configured to enforce selection of the AMF based on the country the UE is currently located. + +Then the 5G-AN shall select an AMF serving a PLMN corresponding to the UE's current location. How 5G-AN selects the AMF in this case is defined in TS 38.410 [125]. + +NOTE: AMF selection case 4) does not apply if 5G-AN nodes serves one country only. + +In the case of NF Service Consumer based discovery and selection, the CP NF selects an AMF from the AMF Set under the following circumstances: + +- When the AMF has instructed CP NF that a certain AMF identified by GUAMI(s) is unavailable and the CP NF was not notified of target AMF; and/or +- CP NF has detected that the AMF has failed; and/or +- When the selected AMF does not support the UE's Preferred Network Behaviour; and/or +- When the selected AMF does not support the High Latency communication for NR RedCap UE. + +In the case of delegated discovery and associated selection, the SCP selects an AMF from the corresponding AMF Set under the following circumstances: + +- The SCP gets an indication "select new AMF within SET" from the CP NF; and/or +- SCP has detected that the AMF has failed. + +The AMF selection functionality in the 5G-AN may consider the following factors for selecting the AMF Set: + +- AMF Region ID and AMF Set ID derived from GUAMI; +- Requested NSSAI; +- Local operator policies; + +- 5G CIoT features indicated in RRC signalling by the UE; +- IAB-indication; +- NB-IoT RAT Type; +- Category M Indication; +- NR RedCap Indication; +- SNPN Onboarding indication as indicated in 5G-AN signalling by the UE. + +AMF selection functionality in the 5G-AN or CP NFs or SCP considers the following factors for selecting an AMF from AMF Set: + +- Availability of candidate AMF(s). +- Load balancing across candidate AMF(s) (e.g. considering weight factors of candidate AMFs in the AMF Set). +- In 5G-AN, 5G CIoT features indicated in RRC signalling by the UE. +- In 5G-AN, SNPN Onboarding indication as indicated in 5G-AN signalling by the UE. + +When the UE accesses the 5G-AN with a 5G-S-TMSI or GUAMI that identifies more than one AMF (as configured during N2 setup procedure), the 5G-AN selects the AMF considering the weight factors. + +When 5G-S-TMSI or GUAMI provided by the UE to the 5G-AN contains an AMF Set ID that is usable, and the AMF identified by AMF pointer that is not usable (e.g. AN detects that the AMF has failed) or the corresponding AMF indicates it is unavailable (e.g. out of operation) then the 5G-AN uses the AMF Set ID for selecting another AMF from the AMF set considering the factors above. + +The discovery and selection of AMF in the CP NFs or SCP follows the principle in clause 6.3.1 + +In the case of NF Service Consumer based discovery and selection, the AMF or other CP NFs shall utilize the NRF to discover the AMF instance(s) unless AMF information is available by other means, e.g. locally configured on AMF or other CP NFs. The NRF provides the NF profile(s) of AMF instance(s) to the AMF or other CP NFs. The AMF selection function in the AMF or other CP NFs selects an AMF instance as described below: + +When NF Service Consumer performs discovery and selection the following applies: + +- In the case of AMF discovery and selection functionality in AMF or other CP NFs use GUAMI (in the SNPN case, along with NID of the SNPN that owns the AMF instances to be discovered and selected) or TAI to discover the AMF instance(s), the NRF provides the NF profile of the associated AMF instance(s). If an associated AMF is unavailable due to AMF planned removal, the NF profile of the backup AMF used for planned removal is provided by the NRF. If an associated AMF is unavailable due to AMF failure, the NF profile of the backup AMF used for failure is provided by the NRF. If AMF pointer value in the GUAMI is associated with more than one AMF, the NRF provides all the AMFs associated with this AMF pointer value. If no AMF instances related to the indicated GUAMI can be found, the NRF may provide a list of NF profiles of candidate AMF instances in the same AMF Set. The other CP NF or AMF may select any AMF instance from the list of candidate AMF instances. If no NF profiles of AMF is returned in the discovery result, the other CP NF or AMF may discover an AMF using the AMF Set as below. +- In the case of AMF discovery and selection functionality in AMF use AMF Set to discover AMF instance(s), the NRF provides a list of NF profiles of AMF instances in the same AMF Set. +- At intra-PLMN mobility, the AMF discovery and selection functionality in AMF may use AMF Set ID, AMF Region ID, the target location information, S-NSSAI(s) of Allowed NSSAI to discover target AMF instance(s). The NRF provides the target NF profiles matching the discovery. +- At intra-SNPN mobility, the AMF discovery and selection functionality in AMF may use AMF Set ID, AMF Region ID (along with NID of the SNPN that owns the AMF instances to be discovered and selected), the target location information, S-NSSAI(s) of Allowed NSSAI, AMF support of SNPN Onboarding (if the UE is registered for SNPN Onboarding) to discover target AMF instance(s). The NRF provides the target NF profiles matching the discovery. + +- At inter PLMN mobility, the source AMF selects an AMF instance(s) in the target PLMN by querying target PLMN level NRF via the source PLMN level NRF with target PLMN ID. The target PLMN level NRF returns an AMF instance address based on the target operator configuration. After the Handover procedure the AMF may select a different AMF instance as specified in clause 4.2.2.2.3 of TS 23.502 [3]. + +In the context of Network Slicing, the AMF selection is described in clause 5.15.5.2.1. + +When delegated discovery and associated selection is used, the following applies: + +- If the CP NF includes GUAMI or TAI in the request, the SCP selects an AMF instance associated with the GUAMI or TAI and sends the request to a selected AMF service instance if it is available. The following also applies: + - If none of the associated AMF service instances are available due to AMF planned removal, an AMF service instance from the backup AMF used for planned removal is selected by the SCP; + - If none of the associated AMF service instances are available due to AMF failure, an AMF service instance from the backup AMF used for failure is selected by the SCP; + - If no AMF service instances related to the indicated GUAMI (in the SNPN case, along with NID of the SNPN that owns the AMF instances to be discovered and selected) can be found the SCP selects an AMF instance from the AMF Set; or + - AMF Pointer value used by more than one AMF, SCP selects one of the AMF instances associated with the AMF Pointer. +- If the CP NF includes AMF Set ID in the request, the SCP selects AMF/AMF service instances in the provided AMF Set. +- At intra-PLMN mobility, if a target AMF instance needs to be selected, the AMF may provide AMF Set ID, AMF Region ID, and the target location information, S-NSSAI(s) of Allowed NSSAI in the request, optionally NRF to use. The SCP will select a target AMF instance matching the discovery. +- At intra-SNPN mobility, if a target AMF instance needs to be selected, the AMF may provide AMF Set ID, AMF Region ID along with NID of the SNPN that owns the AMF instances to be discovered and selected, and the target location information, S-NSSAI(s) of Allowed NSSAI, AMF support of SNPN Onboarding in the request (if the UE is registered for SNPN Onboarding), optionally NRF to use. The SCP will select a target AMF instance matching the discovery. +- At inter PLMN mobility, the source AMF selects indicates "roaming" to the SCP. The SCP interacts with the NRF in source PLMN so that the NRF in source PLMN can discover an AMF in the target PLMN via target PLMN NRF. + +### 6.3.6 N3IWF selection + +#### 6.3.6.1 General + +When the UE supports connectivity with N3IWF but does not support connectivity with ePDG, as specified in TS 23.402 [43], the UE shall perform the procedure in clause 6.3.6.2 for selecting an N3IWF. + +When the UE supports connectivity with N3IWF, as well as with ePDG, as specified in TS 23.402 [43], the UE shall perform the procedure in clause 6.3.6.3 for selecting either an N3IWF or an ePDG, i.e. for selecting a non-3GPP access node. + +In both cases above the UE can be configured by the HPLMN with the same information that includes: + +- 1) ePDG identifier configuration: It contains the FQDN or IP address of the ePDG in the HPLMN, as specified in clause 4.5.4.3 of TS 23.402 [43]. This is used only when the UE supports connectivity with ePDG and attempts to select an ePDG. It is ignored in all other cases. +- 2) N3IWF identifier configuration: It contains the FQDN or IP address of the N3IWF in the HPLMN. +- 3) Extended Home N3IWF identifier configuration: It contains one or multiple tuples of FQDN/IP address of the N3IWF in the HPLMN and the S-NSSAIs supported by this N3IWF. + +- 4) Non-3GPP access node selection information: It contains a prioritized list of PLMNs and for each PLMN it includes (i) a "Preference" parameter which indicates if ePDG or N3IWF is preferred in this PLMN and (ii) an FQDN parameter which indicates if the Tracking/Location Area Identity FQDN or the Operator Identifier FQDN (as specified in clause 4.5.4.4 of TS 23.402 [43]) should be used when discovering the address of an ePDG or N3IWF in this PLMN. The list of PLMNs shall include the HPLMN and shall include an "any PLMN" entry, which matches any PLMN the UE is connected to except the HPLMN. +- 5) Slice-specific N3IWF prefix configuration: It contains one or multiple tuples consisting of: + - List of supported S-NSSAIs; + - Prefix for the Prefixed N3IWF OI or TA FQDNs. + +NOTE 1: Extended Home N3IWF identifier configuration and Slice-specific N3IWF prefix configuration are assumed to be provided to the UE as part of ANDSP. + +The ePDG identifier configuration, the N3IWF identifier configuration, the Extended Home N3IWF identifier configuration and the Slice-specific N3IWF Prefix Configuration are optional parameters, while the Non-3GPP access node selection information is required and shall include at least the HPLMN and the "any PLMN" entry. + +If the ePDG identifier configuration is configured in the UE, then, when the UE decides to select an ePDG in the HPLMN (according to the procedure in clause 6.3.6.3), the UE shall use the ePDG identifier configuration to find the IP address of the ePDG in the HPLMN and shall ignore the FQDN parameter of the HPLMN in the Non-3GPP access node selection information. + +If the N3IWF identifier configuration or the Extended Home N3IWF identifier configuration is configured in the UE, then, when the UE decides to select an N3IWF in the HPLMN (according to the procedure in clause 6.3.6.3 for combined N3IWF/ePDG selection and the procedure in clause 6.3.6.2 for Stand-alone N3IWF selection), the UE shall use the Extended Home N3IWF identifier configuration, if available, and otherwise the N3IWF identifier configuration to find the IP address of the N3IWF in the HPLMN and shall ignore the FQDN parameter of the HPLMN in the Non-3GPP access node selection information. + +The HPLMN's PCF takes the UE's subscribed S-NSSAIs into account when providing Extended Home N3IWF identifier configuration and/or Slice-specific N3IWF Prefix Configuration to the UE. + +If a UE does not support the Extended Home N3IWF identifier configuration and the Slice-specific N3IWF Prefix Configuration, then the HPLMN provides to the UE the Non-3GPP access node selection information and the N3IWF identifier configuration by taking into account the UE's subscribed S-NSSAIs. + +NOTE 2: If the HPLMN deploys multiple N3IWFs with different TAs which support different S-NSSAIs, then the HPLMN can configure a UE with N3IWF identifier configuration so that the UE selects an N3IWF that supports the UE's subscribed S-NSSAIs. + +The UE can be configured by the VPLMN with the following information applicable for the V-PLMN: + +Slice-specific N3IWF prefix configuration: It contains one or multiple tuples consisting of: + +- List of supported S-NSSAIs; +- Prefix for the Prefixed N3IWF OI or TA FQDNs. + +To enable the V-PCF to provide the UE with Slice-specific N3IWF prefix configuration, the AMF provides the V-PCF with the Configured NSSAI for the serving PLMN during the UE Policy Association Establishment/Modification procedure. + +NOTE 3: In non-roaming cases, the UE PCF already receives the subscribed NSSAI from the UDR. Therefore, there is no need for the AMF to provide the Configured NSSAI to the PCF in the non-roaming case. + +NOTE 4: PCF (V-PCF in the roaming case) is assumed to be locally configured with information about the slices supported by the different N3IWFs in the serving PLMN. + +During the registration procedure the AMF may determine if the N3IWF selected by the UE is suitable for the S-NSSAI(s) requested by the UE considering the UE subscription. If the AMF determines that a different N3IWF should be selected as described in clause 4.12.2.2 of TS 23.502 [3], the AMF: + +- may, if the UE supports slice-based N3IWF selection, triggers the UE Policy Association Establishment or UE Policy Association Update procedure to provide the UE with updated N3IWF selection information as described in clause 6.15.2.1; when the AMF is informed by the PCF that the update of UE policy information on the UE is completed as described in clause 4.12.2.2.2 of TS 23.502 [3], the AMF releases UE Policy Association if the UE is not registered over 3GPP access before proceeding to the Registration Reject over untrusted non-3GPP access; +- shall send a Registration Reject message to the UE. The AMF may include target N3IWF information (FQDN and/or IP address) in the Registration Reject so that the UE can, if supported by the UE, use the target N3IWF information to select the N3IWF to register to 5GC if the UE wishes to send the same Requested NSSAI as during the previous Registration Request. The target N3IWF information only applies to the one N3IWF selection performed by the UE just after receiving the Registration Reject. + +The AMF may determine the N3IWF based on the list of supported TAs and the corresponding list of supported slices for each TA obtained as defined in clause 5.15.8. + +NOTE 5: The operator is assumed to ensure that UEs that do not support slice-based N3IWF selection always select an N3IWF that supports at least one slice requested by the UE. This is to avoid unnecessary and potentially repetitive rejections of those UEs. To ensure this, the operator is assumed to provide identifiers of N3IWFs that only support a subset of the slices configured in the network only to UEs that support slice-based N3IWF selection. + +#### 6.3.6.2 Stand-alone N3IWF selection + +The UE performs N3IWF selection based on the ePDG selection procedure as specified in clause 4.5.4 of TS 23.402 [43] except for the following differences: + +- The Tracking/Location Area Identifier FQDN shall be constructed by the UE based only on the Tracking Area wherein the UE is located. The N3IWF Tracking/Location Area Identifier FQDN may use the 5GS TAI when the UE is registered to the 5GS, or the EPS TAI when the UE is registered to EPS. The Location Area is not applicable on the 3GPP access. +- The ePDG Operator Identifier (OI) FQDN format is substituted by with N3IWF OI FQDN format as specified in TS 23.003 [19]. +- If the UE is configured with Slice-specific N3IWF prefix configuration, then the UE shall construct the Prefixed N3IWF OI FQDN or the Prefixed N3IWF TA FQDN as specified in TS 23.003 [19] instead of the N3IWF OI FQDN and the N3IWF TA FQDN, respectively. To determine the prefix, the UE selects the Slice-specific N3IWF prefix configuration for the selected PLMN that contains S-NSSAIs that match all (or most, in case there is no full match) of the S-NSSAIs that the UE is going to include in the Requested NSSAI in the subsequent Registration procedure. + +Editor's note: The Prefixed N3IWF OI FQDN is assumed to take the form: + +.tac-lb.tac-hb.tac.n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org. + +The Prefixed N3IWF TA FQDN is assumed to take the form + .n3iwf.5gc.mnc.mcc.pub.3gppnetwork.org. + +Once these FQDNs have been added to TS 23.003, this Editor's note will be removed. + +- The ePDG identifier configuration is substituted by the N3IWF identifier configuration and the Extended Home N3IWF identifier configuration. The Extended Home N3IWF identifier configuration takes precedence over the N3IWF identifier configuration. If the UE is located in the home country and the UE is configured with Extended Home N3IWF identifier configuration, then the UE uses the Extended Home N3IWF identifier configuration to select an N3IWF: + - The UE uses the FQDN or IP address from the Extended Home N3IWF identifier configuration that matches all (or most, if there is no full match) of the S-NSSAIs that the UE is going to request in the subsequent Registration. +- The ePDG selection information is substituted by the Non-3GPP access node selection information and slice-specific N3IWF prefix information. The UE shall give preference to the N3IWF in all PLMNs in the Non-3GPP access node selection information independent of the "Preference" parameter. + +- If the UE determines to be located in a country other than its home country (called the visited country), then instead of clause 4.5.4.4, bullet 3 of TS 23.402 [43], the following applies: + - a) If the UE is registered via 3GPP access to a PLMN and this PLMN is included in the Non-3GPP access node selection information, then the UE shall select an N3IWF in this PLMN. If the UE fails to connect to an N3IWF in this PLMN, the UE shall select an N3IWF by performing the DNS procedure specified in clause 4.5.4.5 of TS 23.402 [43]. + - b) In all other cases, (e.g. when the UE is not configured with the Non-3GPP access node selection information, or the UE is registered via 3GPP access to a PLMN but this PLMN is not included in the Non-3GPP access node selection information, or the UE is not registered via 3GPP access to any PLMN), the UE shall select an N3IWF by performing the DNS procedure specified in clause 4.5.4.5 of TS 23.402 [43] with the difference that the UE shall construct the Prefixed N3IWF OI FQDN if the UE is configured with Slice-specific N3IWF prefix configuration for the selected PLMN. + +If the UE is accessing PLMN services via SNPN, the UE uses the procedure defined in this clause to select an N3IWF deployed in the PLMN. If the UE is accessing standalone non-public network service via a PLMN (see supported cases in clause 5.30.2.0), the UE uses the procedure defined in clause 6.3.6.2a. + +##### 6.3.6.2a SNPN N3IWF selection + +This procedure applies when the UE is accessing the SNPN N3IWF in its subscribed SNPN via a PLMN or directly via untrusted non-3GPP access. + +The UE shall first determine the country in which it is located. If the UE cannot determine the country in which the UE is located, the UE shall stop N3IWF selection and abort the attempt to access the SNPN via PLMN. + +NOTE 1: It is up to UE implementation how to determine the country in which the UE is located. + +The UE is configured with one N3IWF address and the MCC of the country where the configured N3IWF is located as defined in TS 24.502 [48]. + +If the UE determines that it is located in the country where the configured N3IWF is located, then the UE uses the configured N3IWF FQDN to select an N3IWF deployed in the SNPN. + +If the UE determines that it is located in a country (called the visited country) different from the country where the configured N3IWF is located, then: + +- The UE shall construct an FQDN consisting of the SNPN ID of the subscribed SNPN and the Visited Country FQDN and indicating the query is for SNPN, as specified in TS 23.003 [19] and perform a DNS query for the resulting FQDN. +- If the DNS response contains no records, then the UE determines that the visited country does not mandate the selection of an N3IWF in this country for the SNPN identified by the SNPN ID provided by the UE. In this case the UE uses the configured N3IWF FQDN to select an N3IWF deployed in the SNPN. +- If no DNS response is received, the UE shall stop the N3IWF selection. + +NOTE 2: The DNS can be configured to return no records for the visited country regardless of the SNPN ID provided by the UE. This addresses the scenario that the visited country in general does not mandate selection of a local N3IWF. + +- If the DNS response contains one or more records, then the UE determines that the visited country mandates the selection of an N3IWF in this country. Each record in the DNS response shall contain the identity of an N3IWF of the UE's subscribed SNPN in the visited country which may be used for N3IWF selection. In this case: + - The UE shall select an N3IWF included in the DNS response based on its own implementation means. + - If the UE cannot select any N3IWF included in the DNS response, then the UE shall stop the N3IWF selection. + +NOTE 3: Visited countries which mandate the selection of an N3IWF in the country are assumed to configure the DNS as follows: + +- (i) For SNPNs that do not have any dedicated N3IWFs in the country and which are not exempt from the requirement to select an N3IWF in the visited country, the DNS response contains a record that cannot be resolved to an IP address; +- (ii) for SNPNs that have dedicated N3IWFs in the country, the DNS response contains the identities of the SNPN's N3IWFs in the visited country; +- (iii) for SNPNs that are exempt from the requirement to select an N3IWF in the visited country, the DNS response contains no records. + +NOTE 4: Self-assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same self-assigned NID (i.e. in collision scenarios). If the visited country mandates the selection of an N3IWF in the same country, the NAPTR record(s) associated to the Visited Country FQDN of SNPNs that use a self-assigned NID can be provisioned with the replacement field containing an FQDN that cannot be resolved to an IP address. + +NOTE 5: The identity of an SNPN's N3IWF in the visited country can be any FQDN, i.e. is not required to include the SNPN ID. + +NOTE 6: It is assumed that the AMF, SMF, UPF are located in the same country as the N3IWF and belong to the subscribed SNPN of the UE. + +#### 6.3.6.3 Combined N3IWF/ePDG Selection + +When the UE wants to select a non-3GPP access node (either an N3IWF or an ePDG), the UE shall perform the following procedure: + +- 1) The UE shall attempt to determine the country it is located in. This is determined by implementation-specific methods not defined in this specification. If the UE cannot determine the country it is located in, the UE shall stop the non-3GPP access node selection. +- 2) If the UE determines to be located in its home country, then: + - a) The UE shall select the HPLMN. If the UE fails to connect to an ePDG/N3IWF in the HPLMN, then the UE shall stop the non-3GPP access node selection. +- 3) If the UE determines to be located in a country other than its home country (called the visited country), then: + - a) If the UE is registered via 3GPP access to a PLMN and this PLMN is included in the Non-3GPP access node selection information, then the UE shall select this PLMN. If the UE fails to connect to an ePDG/N3IWF in this PLMN, the UE shall select another PLMN by performing the DNS procedure specified in bullet 3c) below. + - b) In all other cases, (e.g. when the UE is not configured with the Non-3GPP access node selection information, or the UE is registered via 3GPP access to a PLMN but this PLMN is not included in the Non-3GPP access node selection information, or the UE is not registered via 3GPP access to any PLMN), the UE shall select a PLMN by performing the DNS procedure specified in bullet 3c) below. + - c) The UE shall select a PLMN as follows: + - i) The UE shall determine if the non-3GPP access node selection is required for an IMS service or for a non-IMS service. The means of that determination are implementation specific. + - ii) If the UE determines that the non-3GPP access node selection is required for a non-IMS service, the UE shall select a PLMN as specified in clause 6.3.6.2. As defined below, if the UE fails to connect to an N3IWF in any PLMN, the UE may attempt to select an ePDG according to the procedure specified in clause 4.5.4.5 of TS 23.402 [43]. + - iii) If the UE determines that the non-3GPP access node selection is required for an IMS service, the UE shall select a PLMN as follows: + - First, the UE shall perform a DNS query using the Visited Country FQDN for N3IWF, as specified in TS 23.003 [19] to determine if the visited country mandates the selection of N3IWF in this country. The DNS response received by the UE may be empty or may contain the identities of one or more PLMNs in the visited country, which may be used for N3IWF selection, if the UE decides to select an + +N3IWF, as specified below. For example, the DNS response may contain the identity of PLMN-1 and the identity of PLMN-2. + +- Then, the UE shall perform a DNS query using the Visited Country FQDN for ePDG, as specified in TS 23.003 [19] to determine if the visited country mandates the selection of ePDG in this country. The DNS response received by the UE may be empty or may contain the identities of one or more PLMNs in the visited country, which may be used for ePDG selection, if the UE decides to select an ePDG, as specified below. For example, the DNS response may contain the identity of PLMN-1 and the identity of PLMN-3. +- If the UE does not receive a DNS response in none of the above two DNS queries, then the UE shall stop the non-3GPP access node selection. Otherwise, the next steps are executed. +- The UE shall consolidate the PLMN identities received in the above two DNS responses and shall construct a candidate list of PLMNs. For example, the candidate list of PLMNs may contain the identities of PLMN-1, PLMN-2, PLMN-3. +- If the candidate list of PLMNs is empty, then: + - If the Non-3GPP access node selection information contains one or more PLMNs in the visited country, the UE shall select one of these PLMNs based on their priorities in the Non-3GPP access node selection information. If the UE fails to connect to a non-3GPP access node in any of these PLMNs, the UE shall select the HPLMN. + - Otherwise, the UE shall select the HPLMN. +- If the candidate list of PLMNs is not empty, then: + - If the UE is registered via 3GPP access to a PLMN which is included in the candidate list of PLMNs, then the UE shall select this PLMN. If the UE fails to connect to a non-3GPP access node in this PLMN, then the UE shall select a different PLMN included in the candidate list of PLMNs as specified in the next bullet. + - If the UE is registered via 3GPP access to a PLMN which is not included in the candidate list of PLMNs, or the UE is not registered via 3GPP access to any PLMN, or the UE fails to connect to a non-3GPP access node according to the previous bullet, then the UE shall select one of the PLMNs included in the candidate list of PLMNs based on the prioritized list of PLMNs in the Non-3GPP access node selection information (i.e. the UE shall select first the highest priority PLMN in the Non-3GPP access node selection information that is contained in the candidate list of PLMNs). If the Non-3GPP access node selection information does not contain any of the PLMNs in the candidate list of PLMNs, or the UE is not configured with the Non-3GPP access node selection information, or the UE was not able to connect to a non-3GPP access node in any of the PLMNs included in the Non-3GPP access node selection information and in the candidate list of PLMN, then the UE shall select a PLMN included in the candidate list of PLMNs based on its own implementation means. + - If the UE cannot select a non-3GPP access node in any of the PLMNs included in the candidate list of PLMNs, then the UE shall stop the non-3GPP access node selection. + +In the selected PLMN the UE shall attempt to select a non-3GPP access node as follows: + +1. The UE shall determine if the non-3GPP access node selection is required for an IMS service or for a non-IMS service. The means of that determination are implementation-specific. +2. When the selection is required for an IMS service, the UE shall choose a non-3GPP access node type (i.e. ePDG or N3IWF) based on the "Preference" parameter specified in clause 6.3.6.1, unless the UE has its 5GS capability disabled in which case it shall choose an ePDG independent of the "Preference" parameter setting. + +If the "Preference" parameter for the selected PLMN indicates that ePDG is preferred, the UE shall attempt to select an ePDG. If the "Preference" parameter for the selected PLMN indicates that N3IWF is preferred, the UE shall attempt to select an N3IWF. + +If the selection fails, including the case when, during the registration performed over either 3GPP or non-3GPP access, the UE receives the IMS Voice over PS session Not Supported over Non-3GPP Access indication (specified in clause 5.16.3.2a), the UE shall attempt selecting the other non-3GPP access node type in the + +selected PLMN, if any. If that selection fails too, or it is not possible, then the UE shall select another PLMN, according to the procedure specified bullet 3c) above. + +3. When the selection is required for a non-IMS service, the UE shall perform the selection by giving preference to the N3IWF independent of the "Preference" parameter setting. If the N3IWF selection fails, or it is not possible, the UE should select another PLMN based on the procedure specified in clause 4.5.4.4 of TS 23.402 [43], and shall attempt to select an N3IWF in this PLMN. If the UE fails to select an N3IWF in any PLMN, the UE may attempt to select an ePDG according to the procedure specified in clause 4.5.4.5 of TS 23.402 [43]. + +In the above procedure, when the UE attempts to construct a Tracking/Location Area Identifier FQDN either for ePDG selection or for N3IWF selection, the UE shall use the Tracking Area wherein the UE is located and shall construct either: + +- an ePDG or N3IWF TAI FQDN based on the 5GS TAI, when the UE is registered to the 5GS; or +- an ePDG or N3IWF TAI FQDN based on the EPS TAI, when the UE is registered to EPS. + +NOTE: A UE performing both a selection for an IMS service and a selection for a non-IMS service could get simultaneously attached to a N3IWF and to an ePDG in the same PLMN or in different PLMNs. + +If the UE is configured with Slice-specific N3IWF prefix configuration, then the UE shall construct the Prefixed N3IWF OI FQDN or the Prefixed N3IWF TA FQDN as specified in TS 23.003 [19] instead of the N3IWF OI FQDN and the N3IWF TA FQDN, respectively. Further details on constructing the Prefixed N3IWF OI and TA FQDN are described in clause 6.3.6.2. + +#### 6.3.6.4 PLMN and non-3GPP access node Selection for emergency services + +##### 6.3.6.4.1 General + +UE initiates PLMN and non-3GPP access node selection for emergency services when it detects a user request for emergency session and determines that untrusted non-3GPP access shall be used for the emergency access. + +When the UE supports connectivity with N3IWF but does not support connectivity with ePDG, as specified in TS 23.402 [43], the UE shall perform the procedure in clause 6.3.6.4.2 for selecting an N3IWF. + +When the UE supports connectivity with N3IWF, as well as with ePDG, as specified in TS 23.402 [43], the UE shall perform the procedure in clause 6.3.6.4.3 for selecting either an N3IWF or an ePDG, i.e. for selecting a non-3GPP access node. + +##### 6.3.6.4.2 Stand-alone N3IWF selection + +If the UE is attached to 5GC via an N3IWF that is located in the same country as the country in which the UE is currently located and the AMF has previously indicated support for emergency services over non-3GPP access as defined in clause 5.16.4.1, the UE reuses the existing N3IWF connection for emergency services. Otherwise, the UE terminates any existing N3IWF connection and continues as follows: + +If the UE is equipped with a UICC: + +- The UE determines whether it is located in the home country or a visited country; +- If the UE is located in the home country, then the UE selects the Home PLMN for emergency services and selects an N3IWF based on the procedure defined in clause 6.3.6.2. +- If the UE is located in a visited country, the UE performs a DNS query using the Visited Country Emergency N3IWF FQDN, as specified in TS 23.003 [19] to determine which PLMNs in the visited country support emergency services in non-3GPP access via N3IWF; and: +- If the DNS response contains one or more records, the UE selects a PLMN that supports emergency services in non-3GPP access via N3IWF. Each record in the DNS response shall contain the identity of a PLMN in the visited country supporting emergency services in non-3GPP access via N3IWF. +- The UE shall consider these PLMNs based on their priorities in the Non-3GPP Access Node Selection Information (if available). If the UE cannot select a PLMN in the Non-3GPP Access Node Selection + +Information or if non-3GPP Access Node Selection Information is not available, the UE shall attempt to select any PLMN in the list of PLMNs returned in the DNS response. + +- Once the UE has selected a PLMN the UE shall select an N3IWF for the selected PLMN as follows: + - If non-3GPP Access Node Selection Information is available for the selected PLMN the UE constructs the Tracking Area Identity based N3IWF FQDN or the Operator Identifier based N3IWF FQDN as indicated in the non-3GPP Access Node Selection Information for the selected PLMN. + - If non-3GPP Access Node Selection Information is not available for the selected PLMN the UE constructs the Operator Identifier based N3IWF FQDN for the selected PLMN. +- If the DNS response does not contain any record, or if the DNS response contains one or more records but the UE fails to select a PLMN that supports emergency services in non-3GPP access, or if the Emergency Registration procedure has failed for all PLMNs supporting emergency services in non-3GPP access, the UE notifies the user that an emergency session cannot be established. + +If the UE is not equipped with a UICC, the UE shall perform the emergency N3IWF selection procedure above as if always in a visited country and without using the Non-3GPP Access Node Selection Information, i.e. the UE may construct the Operator Identifier based N3IWF FQDN format based on a PLMN ID obtained via implementation specific means. + +When an N3IWF has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall select another PLMN supporting emergency services in non-3GPP access. + +##### 6.3.6.3.3 Combined N3IWF/ePDG Selection + +If the UE is attached to 5GC via an N3IWF that is located in the same country as the country in which the UE is currently located and the AMF has previously indicated support for emergency services over non-3GPP access as defined in clause 5.16.4.1, the UE reuses the existing N3IWF connection for emergency services. Otherwise, the UE terminates any existing N3IWF connection and performs PLMN and N3IWF or ePDG selection for emergency services. + +If the UE is attached to EPC via an ePDG that has indicated support for the emergency services and is located in the same country as the country in which the UE is currently located, the UE reuses the existing ePDG connection for emergency services. Otherwise, the UE terminates the existing ePDG connection, if any, and performs PLMN and N3IWF or ePDG selection for emergency services. + +PLMN and N3IWF or ePDG selection for emergency services is performed as follows: + +If the UE is equipped with a UICC: + +- The UE determines whether it is located in the home country or a visited country; +- If the UE is located in the home country the UE selects the Home PLMN for emergency services and selects an N3IWF or ePDG as follows: + - If the Non-3GPP Access Node Selection Information for the HPLMN is available the UE selects first an N3IWF or ePDG based on the Non-3GPP Access Node type preference in the Non-3GPP Access Node Selection Information for the HPLMN. To select an N3IWF the UE uses the N3IWF identifier configuration (if available). If the N3IWF identifier configuration is not available, the UE constructs the FQDN format as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the HPLMN. To select an ePDG the UE selects the ePDG identified by the configured Emergency ePDG FQDN (if available). If the configured Emergency ePDG FQDN is not available, the UE constructs either the Tracking/Location Area Identity based Emergency ePDG FQDN or the Operator Identifier based Emergency ePDG FQDN as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the HPLMN. + - If the Non-3GPP Access Node Selection Information is not available, the UE shall first attempt to select an N3IWF following the procedure defined in clause 6.3.6.2 before attempting to select an ePDG. To select an ePDG the UE selects the ePDG identified by the configured Emergency ePDG FQDN (if available). If the configured Emergency ePDG FQDN is not available, the UE constructs the Operator Identifier based Emergency ePDG FQDN. + +- If the UE is located in a visited country, the UE performs a DNS query using the Visited Country Emergency FQDN for N3IWF and using the Visited Country Emergency FQDN for ePDG, as specified in TS 23.003 [19] to determine which PLMNs in the visited country support emergency services in non-3GPP access. +- If the DNS responses contain one or more records, the UE selects a PLMN that supports emergency services in non-3GPP access for the UE. Each record in the DNS responses shall contain the identity of a PLMN in the visited country supporting emergency services in non-3GPP access via ePDG or N3IWF. +- The UE shall consider these PLMNs based on their priorities in the Non-3GPP Access Node Selection Information. If the UE cannot select a PLMN in the Non-3GPP Access Node Selection Information or if non-3GPP Access Node Selection Information is not available, the UE shall attempt to select any PLMN in the list of PLMNs returned in the DNS response. +- Once the UE has selected a PLMN the UE shall select an N3IWF or ePDG for the selected PLMN as follows: + - If the Non-3GPP Access Node Selection Information for the PLMN is available the UE selects first an N3IWF or ePDG based on the Non-3GPP Access Node type preference in the Non-3GPP Access Node Selection Information for the PLMN. To select an N3IWF the UE constructs the FQDN format as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the PLMN. To select an ePDG the UE constructs either the Tracking/Location Area Identity based Emergency ePDG FQDN or the Operator Identifier based Emergency ePDG FQDN as indicated by the FQDN format in the Non-3GPP Access Node Selection Information for the PLMN. + - If the Non-3GPP Access Node Selection Information is not available, the UE shall first attempt to select an N3IWF following the procedure defined in clause 6.3.6.2 before attempting to select an ePDG. To select an ePDG the UE constructs the Operator Identifier based Emergency ePDG FQDN. + - If the DNS response does not contain any record, or if the DNS response contains one or more records but the UE fails to select a PLMN that supports emergency services in non-3GPP access, or if the Emergency Registration procedure has failed for all PLMNs supporting emergency services in non-3GPP access, the UE notifies the user that emergency session cannot be established. + +If the UE is not equipped with a UICC, the UE shall perform the emergency ePDG/N3IWF selection procedure above as if always in a visited country and without using the Non-3GPP Access Node Selection Information, i.e. the UE may construct the Operator Identifier FQDN for N3IWF or ePDG based on a PLMN ID obtained via implementation specific means. + +When a N3IWF has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall attempt to select an ePDG before selecting another PLMN supporting emergency services in non-3GPP access. When an ePDG has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall attempt to select a N3IWF before selecting another PLMN supporting emergency services in non-3GPP access. + +### 6.3.7 PCF discovery and selection + +#### 6.3.7.0 General principles + +Clause 6.3.7.0 describes the underlying principles for PCF selection and discovery: + +- There may be multiple and separately addressable PCFs in a PLMN. +- The PCF must be able to correlate the AF service session established over N5 or Rx with the associated PDU Session (Session binding) handled over N7. +- It shall be possible to deploy a network so that the PCF may serve only specific DN(s). For example, Policy Control may be enabled on a per DNN basis. +- Unique identification of a PDU Session in the PCF shall be possible based on the (UE ID, DNN)-tuple, the (UE (IP or MAC) Address(es), DNN)-tuple and the (UE ID, UE (IP or MAC) Address(es), DNN). + +#### 6.3.7.1 PCF discovery and selection for a UE or a PDU Session + +PCF discovery and selection functionality is implemented in AMF, SMF, SCP and PCF and follows the principles in clause 6.3.1. The AMF uses the PCF services for a UE and the SMF uses the PCF services for a PDU Session. PCF for a PDU Session uses the PCF services for a UE. + +When the NF service consumer performs discovery and selection for a UE, the following applies: + +- The AMF may utilize the NRF to discover the candidate PCF instance(s) for a UE. In addition, PCF information may also be locally configured in the AMF. The AMF selects a PCF instance based on the available PCF instances obtained from the NRF or locally configured information in the AMF, depending on operator's policies. + +In the non roaming case, the AMF selects a PCF instance for AM policy association and selects the same PCF instance for UE policy association. In the roaming case, the AMF selects a V-PCF instance for AM policy association and selects the same V-PCF instance for UE policy association. + +The PCF for a PDU Session selects a (V-)PCF instance for UE policy association. + +The following factors may be considered at PCF discovery and selection for Access and Mobility policies and UE policies: + +- SUPI; the AMF selects a PCF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for PCF discovery. +- S-NSSAI(s). In the roaming case, the AMF selects the V-PCF instance based on the S-NSSAI(s) of the VPLMN and selects the H-PCF instance based on the S-NSSAI(s) of the HPLMN. +- PCF Set ID. +- PCF Group ID of the UE's SUPI. + +NOTE 1: The AMF can infer the PCF Group ID the UE's SUPI belongs to, based on the results of PCF discovery procedures with NRF. The AMF provides the PCF Group ID the SUPI belongs to to other PCF NF consumers as described in TS 23.502 [3]. + +- DNN replacement capability of the PCF. +- Slice replacement capability of the PCF. +- PCF Selection Assistance Info and PCF ID(s) serving the established PDU Sessions/PDN Connections received from UDM. In case PCF Selection Assistance Info and PCF ID(s) are received from the UDM, the AMF selects the same PCF instance serving the combination of DNN and S-NSSAI as indicated by the PCF Selection Assistance Info, if multiple DNN, S-NSSAI combinations are provided, the AMF selects the DNN,S-NSSAI using local configuration. In case PCF ID(s) are not received, e.g. EPS interworking is not supported, the AMF selects the PCF instance by considering other above factors. +- URSP delivery in EPS capability of the PCF. + +When the NF service consumer performs discovery and selection for a PDU Session, the following applies: + +- The SMF may utilize the NRF to discover the candidate PCF instance(s) for a PDU Session. In addition, PCF information may also be locally configured in the SMF. The SMF selects a PCF instance based on the available PCF instances obtained from the NRF or locally configured information in the SMF, depending on operator's policies. + +The following factors may be considered at PCF discovery and selection for a PDU session: + +- a) Local operator policies. +- b) Selected Data Network Name (DNN). +- c) S-NSSAI of the PDU Session. In the LBO roaming case, the SMF selects the PCF instance based on the S-NSSAI of the VPLMN. In the home routed roaming case, the H-SMF selects the H-PCF instance based on the S-NSSAI of the HPLMN. + +- d) SUPI; the SMF selects a PCF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for PCF discovery. +- e) PCF selected by the AMF for the UE. +- f) MA PDU Session capability of the PCF, for an MA PDU session. +- g) The PCF Group ID provided by the AMF to the SMF. +- h) PCF Set ID. +- i) Same PCF Selection Indication. +- j) URSP delivery in EPS capability of the PCF. + +In the case of delegated discovery and selection in SCP, the SMF includes the factors b) - h), j), if available, in the first request. + +The selected PCF instance for serving the UE and the selected PCF instance for serving a PDU session of this UE may be the same or may be different. + +In the following scenarios, information about the PCF instance that has been selected (i.e. the PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available)) may be forwarded to another NF. If the NF service consumer performs discovery and selection, this NF may use this PCF instance. If the NF service consumer performs delegated discovery and selection, this NF may include PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) in the request and the SCP may use this information to select the PCF instance (discovery may still be needed depending on what level of information is sent by the AMF, e.g. the address of the PCF instance may not be present): + +When NF service consumer performs discovery and selection, the following applies: + +- During AMF relocation, the target AMF may receive a PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) from the source AMF to enable the usage of the same PCF by the target AMF, and the target AMF may decide based on operator policy either to use the same PCF or select a new PCF. +- The AMF may, based on operator policies, forward the selected PCF to SMF instance(s) during the PDU Session Establishment procedure(s) to enable the usage of the same PCF for the AMF and the SMF instance(s). The SMF may decide based on operator policy either to use the same PCF or select a new PCF. If combination of the DNN and S-NSSAI of the PDU session matches one of the combination of the DNN and S-NSSAI included in the PCF Selection Assistance info received from UDM, the AMF shall forward Same PCF Selection Indication together with the selected PCF to SMF instance during the PDU Session Establishment procedure. In case that the Same PCF Selection Indication is received together with the PCF ID, the SMF shall select the same PCF instance for SM Policy Control. +- In the roaming case, the AMF may, based on operator policies, e.g. roaming agreement, select the H-PCF in addition to the V-PCF for a UE by performing the PCF discovery and selection as described above. The AMF sends the H-PCF ID of the selected H-PCF instance to the V-PCF during the policy association establishment procedure. + +When the SMF receives a redirection indication with PCF ID from the PCF for the PDU session, the SMF shall terminate the current SM Policy Control association and reselects a PCF based on the received PCF ID. The SMF shall then establish an SM Policy Control association with the reselected PCF. + +In the case of delegated discovery and selection in the SCP, the following applies: + +- The selected PCF instance may include the PCF Id, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) in the response to the AMF. + +NOTE 2: The selected (V-)PCF instance can include the binding indication, including the (V-)PCF ID and possibly PCF Set ID in the response to the AMF as described in clause 6.3.1.0. + +- The AMF first establishes an AM policy association; when forwarding the related request message the SCP discovers and selects a PCF instance. Unless binding information is provided in the response to that request the SCP adds the NF function producer ID it selected, i.e. PCF ID, into the response and the AMF uses the received PCF ID and available binding information as discovery and selection parameters for the request to establish the + +UE policy association towards the SCP. The SCP selects the (V-)PCF instance for UE policy association based on the received discovery and selection parameters. + +- During AMF relocation, the AMF may receive a PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) from the source AMF to enable the usage of the same PCF instance by the AMF. The AMF may decide based on operator policy either to use the old PCF instance or select another PCF instance. If the AMF decides to use the old PCF, the AMF includes the PCF ID PCF Set Id, and if PCF Set Id is not available, the PCF Group ID (if available) as received from the source AMF in the AM policy update request to the SCP. +- The AMF may, based on operator policies, forward the selected PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) to the SMF during the PDU Session Establishment procedure to enable the usage of the same PCF for the AMF and the SMF. The SMF may include that information in the request in discovery and selection parameters to the SCP. The SCP may decide based on operator policy either to use the indicated PCF instance or select another PCF instance. +- In the roaming case, the AMF performs discovery and selection of the H-PCF from NRF as described in this clause. The AMF may indicate the maximum number of H-PCF instances to be returned from NRF, i.e. H-PCF selection at NRF. The AMF uses the received V-PCF ID and available binding information received during the AM policy association procedure to send the UE policy association establishment request, which also includes the H-PCF ID, to the SCP. The SCP discovers and selects the V-PCF. The V-PCF sends an UE policy association establishment request towards the HPLMN, which includes the H-PCF ID as a discovery and selection parameter to SCP. + +#### 6.3.7.2 Providing policy requirements that apply to multiple UE and hence to multiple PCF + +An authorized Application Function may, via the NEF, provide policy requirements that apply to multiple UE(s) (which, for example, belong to group of UE(s) defined by subscription or to any UE). Such policy requirements shall apply to any existing or future PDU Sessions that match the parameters in the AF request, and they may apply to multiple PCF instance(s). + +NOTE: Application Function influence on traffic routing described in clause 5.6.7 is an example of such requirement. + +After relevant validation of the AF request (and possible parameter mapping), the NEF stores this request received from the AF into the selected UDR instance as the Data Subset of the Application data. The possible parameter mapping includes mapping UE (group) identifiers provided by the AF to identifiers used within the 5GC, e.g. from GPSI to SUPI and/or from External Group Identifier to Internal-Group Identifier. Parameter mapping may also include mapping from the identifier of the Application Function towards internal identifiers such as the DNN and/or the S-NSSAI. + +PCF(s) that need to receive AF requests that targets a DNN (and slice), and/or a group of UEs subscribe to receive notifications from the UDR about such AF request information. The PCF(s) can be configured (e.g. by OAM) to subscribe to receive notification of such AF request information from the UDR(s). The PCF(s) take(s) the received AF request information into account when making policy decisions for existing and future relevant PDU Sessions. In the case of existing PDU Sessions, the policy decision of the PCF instance(s) may trigger a PCC rule(s) change from the PCF to the SMF. + +The PCF subscription to notifications of AF requests described above may take place during PDU Session Establishment or PDU Session Modification, when the PCF(s) receive request(s) from the SMF for policy information related to the DNN (and slice), and/or the Internal-Group Identifier of UEs. For the PCF(s) that have subscribed to such notifications, the UDR(s) notify the PCF(s) of any AF request update. + +The NEF associates the AF request with information allowing to later modify or delete the AF request in the UDR; it associates the AF request with: + +- When the AF request targets PDU Sessions established by "any UE": the DNN, the slicing information target of the AF request, +- When the request targets PDU Sessions established by UE(s) belonging to an Internal-Group: the DNN, the slicing information and the Internal-Group Identifier target of the application request. +- The AF transaction identifier in the AF request. + +#### 6.3.7.3 Binding an AF request targeting a UE address to the relevant PCF + +Binding an AF request to the relevant PCF instance is described in TS 23.503 [45]. + +#### 6.3.7.4 Binding an AF request targeting a UE to the relevant PCF + +Binding an AF request to the relevant PCF for a UE is described in TS 23.503 [45]. + +### 6.3.8 UDM discovery and selection + +The NF consumer or the SCP performs UDM discovery to discover a UDM instance that manages the user subscriptions. + +If the NF consumer performs discovery and selection, the NF consumers shall utilize the NRF to discover the UDM instance(s) unless UDM information is available by other means, e.g. locally configured on NF consumers. The UDM selection function in NF consumers selects a UDM instance based on the available UDM instances (obtained from the NRF or locally configured). + +The UDM selection functionality is applicable to both 3GPP access and non-3GPP access. + +The UDM selection functionality in NF consumer or in SCP should consider one of the following factors: + +1. Home Network Identifier (e.g. MNC and MCC, realm) of SUCI/SUPI, along with the selected NID (provided by the NG-RAN) in the case of SNPN, UE's Routing Indicator and optionally Home Network Public Key identifier (e.g. in the case that Routing Indicator is not enough to provide SUPI range granularity). + +NOTE 1: The UE provides the SUCI to the AMF, which contains the Routing Indicator and Home Network Public Key identifier as defined in TS 23.003 [19] during initial registration. The AMF provides the UE's Routing Indicator and optionally Home Network Public Key identifier to other NF consumers (of UDM) as described in TS 23.502 [3]. + +NOTE 2: The usage of Home Network Public Key identifier for UDM discovery is limited to the scenario where the NF consumers belong to the same PLMN as AUSF. + +NOTE 3: In the case of SNPN and the UE provides an IMSI type SUCI to the AMF and the SUCI provided by UE or the SUPI derived from the SUCI is for an SNPN served by the AMF, the AMF uses the selected NID provided by the NG-RAN together with the selected PLMN ID (from IMSI) or the Routing Indicator provided by the UE within the SUCI for UDM selection. In the case of SNPN and the UE provides an NSI type SUCI to the AMF, the AMF uses the Home Network Identifier and Routing Indicator of SUCI/SUPI for selection of UDM. + +When the UE's Routing Indicator is set to its default value as defined in TS 23.003 [19], the UDM NF consumer can select any UDM instance within the home network of the SUCI/SUPI. + +2. UDM Group ID of the UE's SUPI. + +NOTE 4: The AMF can infer the UDM Group ID the UE's SUPI belongs to, based on the results of UDM discovery procedures with NRF. The AMF provides the UDM Group ID the SUPI belongs to other UDM NF consumers as described in TS 23.502 [3]. + +3. SUPI or Internal Group ID; the UDM NF consumer selects a UDM instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI or Internal Group ID as input for UDM discovery. +4. GPSI or External Group ID; UDM NF consumers which manage network signalling not based on SUPI/SUCI (e.g. the NEF) select a UDM instance based on the GPSI or External Group ID range the UE's GPSI or External Group ID belongs to or based on the results of a discovery procedure with NRF using the UE's GPSI or External Group ID as input for UDM discovery. + +In the case of delegated discovery and selection in SCP, NF consumer shall include one of these factors in the request towards SCP. + +### 6.3.9 UDR discovery and selection + +Multiple instances of UDR may be deployed, each one storing specific data or providing service to a specific set of NF consumers as described in clause 4.2.5. In segmented UDR deployment, different instances of UDR store the data for different Data Sets and Data Subsets or for different users. A UDR instance can also store application data that applies on any UE, i.e. all subscribers of the PLMN. + +If the NF service consumer performs discovery and selection, the NF consumer shall utilize the NRF to discover the appropriate UDR instance(s) unless UDR instance information is available by other means, e.g. locally configured on NF consumer. The UDR selection function in NF consumers is applicable to both 3GPP access and non-3GPP access. The NF consumer or the SCP shall select a UDR instance that contains relevant information for the NF consumer, e.g. UDM/SCP selects a UDR instance that contains subscription data, while NEF/SCP (when used to access data for exposure) selects a UDR that contains data for exposure; or PCF/SCP selects a UDR that contains Policy Data and/or Application Data. + +The UDR selection function in UDR NF consumers considers the Data Set Identifier of the data to be managed in UDR (see UDR service definition in clause 5.2.12 of TS 23.502 [3]). Additionally, the UDR selection function in UDR NF consumers should consider one of the following factors when available to the UDR NF consumer when selecting a UDR that stores the required Data Set(s) and Data Subset(s): + +1. UDR Group ID the UE's SUPI belongs to. +2. SUPI; e.g. the UDR NF consumer selects a UDR instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for UDR discovery. +3. GPSI or External Group ID; e.g. UDR NF consumers select a UDR instance based on the GPSI or External Group ID range the UE's GPSI or External Group ID belongs to or based on the results of a discovery procedure with NRF using the UE's GPSI or External Group ID as input for UDR discovery. +4. UDR capability to store application data that is applicable on any UE (i.e. all subscribers of the PLMN). + +In the case of delegated discovery and selection, the NF consumer shall include the available factors in the request towards SCP. + +### 6.3.10 SMSF discovery and selection + +The SMSF selection function is supported by the AMF and is used to allocate an SMSF instance that shall manage the SMS. + +If the "SMS supported" indication is included in the Registration Request by the UE, the AMF checks SMS subscription from the UDM for the UE on whether the SMS is allowed for the UE. + +If the SMS is allowed and the UE Context stored in AMF includes an SMSF address, the AMF uses the SMSF address included in UE Context (according to Table 5.2.2.2.2-1 of TS 23.502 [3]). + +If the SMS is allowed and the UE Context stored in AMF does not include an SMSF address, the AMF discovers and selects an SMSF to serve the UE. + +The SMSF selection may be based on the following methods: + +- SMSF instance(s) address(es) preconfigured in the AMF (i.e. SMSF FQDN or IP addresses); or +- SMSF information available in the serving PLMN if received from an old AMF or the UDM; or +- The AMF invokes Nnrf\_NFDiscovery service operation from NRF to discover SMSF instance as described in clause 5.2.7.3.2 of TS 23.502 [3]. + +For roaming scenario, the AMF discovers and selects an SMSF in VPLMN. + +If the NF consumer performs discovery and selection via NRF, the SMSF selection function in the NF consumer selects a SMSF instance based on the available SMSF instances obtained from the NRF. + +In the case of delegated discovery and selection in SCP, the NF consumer shall include all available factors in the request towards SCP. + +### 6.3.11 CHF discovery and selection + +The CHF discovery and selection function is supported by the SMF, the AMF, the SMSF and the PCF. It is used by the SMF to select a CHF that manages the online charging or offline charging for a PDU Session of a subscriber. It is used by the AMF to select a CHF that manages the online charging or offline charging for 5G connection and mobility of a subscriber. It is used by the SMSF to select a CHF that manages the online charging or offline charging for the SMS over NAS transactions of a subscriber. It is used by the PCF to select a CHF that manages the spending limits for a subscriber and/or a PDU Session of a subscriber. + +For the PCF to select the CHF, the address(es) of the CHF, including the Primary CHF address and the Secondary CHF address, may be: + +- stored in the UDR as part of the PDU Session policy control subscription information as defined in clause 6.2.1.3 of TS 23.503 [45]. +- stored in the UDR as part of the UE context policy control subscription information as defined in clause 6.2.1.3 of TS 23.503 [45]. +- stored in the UDR as part of the Access and Mobility policy control subscription information as defined in clause 6.2.1.3 of TS 23.503 [45]. +- locally configured in the PCF based on operator policies. +- discovered using NRF as described in in clause 6.1 of TS 32.290 [67]. + +NOTE 1: The operator can perform the above UDR provisioning or local configuration in a consistent manner such that the same CHF address is used for SM policy, AM policy and UE policy. If NRF discovery is used, it is up to the PCF logic (or SCP logic when working in Delegated Discovery mode) and operator configuration to guarantee the CHF address consistency. + +The address(es) of the CHF shall be applicable for all services provided by the CHF. + +The CHF address(es) that a stored in the UDR or configured in the PCF may be complemented by the associated CHF instance ID(s) and CHF set ID(s) (see clause 6.3.1.0) stored or configured in the same location. + +The CHF address(es) retrieved from the UDR and possible associated CHF instance ID(s) and CHF set ID(s) take precedence over the locally configured CHF address(es) and possible associated CHF instance ID(s) and CHF set ID(s), and over the CHF address(es) discovered by the NRF. If no CHF address(es) is received from the UDR, the PCF selects, based on operator policies, either the CHF address(es) provided by NRF, or the locally configured CHF address(es) and possible associated CHF instance ID(s) and CHF set ID(s). + +If the PCF has a CHF set ID but no CHF instance ID associated to the CHF address(es) in the same location, the CHF instance within the CHF set may change. If the PCF is not able to reach the CHF address(es), it should query the NRF for other CHF instances within the CHF set. + +If the PCF received a CHF set ID and a CHF instance ID associated to the CHF address(es) in the same location, the CHF service instance within the CHF may change. If an PCF is not able to reach the CHF address(es), it should query the NRF for other CHF service instances within the CHF. + +To enable the SMF to select the same CHF that is selected by the PCF for a PDU Session, the PCF provides the selected CHF address(es) and, if available, the associated CHF instance ID(s) and/or CHF set ID(s) in the PDU Session related policy information to the SMF as described in Table 6.4-1 of TS 23.503 [45] and the SMF applies the CHF address and if available, the associated CHF instance ID(s) and/or CHF set ID(s) passed from the PCF as defined in clause 5.1.8 of TS 32.255 [68]. Otherwise, the SMF selection of the CHF as defined in clause 5.1.8 of TS 32.255 [68] applies. + +If operator policies indicates the AMF should select the same CHF that is selected by the PCF for a UE, the PCF provides the selected CHF address(es) and, if available, the associated CHF instance ID(s) and/or CHF set ID(s) in the Access and mobility related policy information to the AMF as described in Table 6.5-1 of TS 23.503 [45] and the AMF may apply the CHF address and, if available, the associated CHF instance ID(s) and/or CHF set ID(s) passed from the PCF as defined in clause 5.1.3 of TS 32.256 [114]. Otherwise, the AMF selection of the CHF as defined in clause 5.1.3 of TS 32.256 [114] applies. + +How the CHF is selected by the SMSF is defined in clause 5.4 of TS 32.274 [118]. + +If the NF consumer performs discovery and selection via NRF, the CHF selection function in NF consumers selects a CHF instance based on the available CHF instances obtained from the NRF. + +The CHF selection functionality in NF consumer or in SCP should consider one of the following factors: + +1. CHF Group ID of the UE's SUPI. + +NOTE 2: The NF Consumer can infer the CHF Group ID the UE's SUPI belongs to, based on the results of CHF discovery procedures with NRF. + +2. SUPI; the NF consumer selects a CHF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for CHF discovery. + +In the case of delegated discovery and selection in SCP, the NF consumer shall include all available factors in the request towards SCP. + +### 6.3.12 Trusted Non-3GPP Access Network selection + +#### 6.3.12.1 General + +Clause 6.3.12 specifies how a UE, which wants to establish connectivity via trusted non-3GPP access and is not operating in SNPN access mode, selects a PLMN and a trusted non-3GPP access network (TNAN) to connect to. + +NOTE: For UE operating in SNPN access mode refer to clause 5.30.2.13. + +How the UE decides to use trusted non-3GPP access is not specified in this document. As an example, a UE may decide to use trusted non-3GPP access for connecting to 5GC in a specific PLMN based on: + +- the UE implementation-specific criteria; or +- the UE configuration, e.g. the UE may be configured to try first the trusted non-3GPP access procedures; or +- the UE capabilities, e.g. the UE may support only the trusted non-3GPP access procedures; or +- the advertised capabilities of the discovered non-3GPP access networks, e.g. one or more available non-3GPP access networks advertise support of trusted connectivity to 5GC in a specific PLMN. + +An example deployment scenario is schematically illustrated in Figure 6.3.12.1-1 below. In this scenario, the UE has discovered five non-3GPP access networks, which are WLAN access networks. These WLANs advertise information about the PLMNs they interwork with, e.g. by using the ANQP protocol, as defined in the HS2.0 specification [85]. Each WLAN may support "S2a connectivity" and/or "5G connectivity" to one or more PLMNs. Before establishing connectivity via trusted non-3GPP access, the UE needs to select (a) a PLMN, (b) a non-3GPP access network that provide trusted connectivity this this PLMN, and (c) a connectivity type, i.e. either "5G connectivity" or "S2a connectivity". + +Each non-3GPP access network may advertise one or more of the following PLMN lists: + +- 1) A PLMN List-1, which includes PLMNs with which "AAA connectivity" is supported. A non-3GPP access network supports "AAA connectivity" with a PLMN when it deploys an AAA function that can connect with a 3GPP AAA Server/Proxy in this PLMN, via an STa interface (trusted WLAN to EPC), or via an SWa interface (untrusted WLAN to EPC); see TS 23.402 [43]. +- 2) A PLMN List-2, which includes PLMNs with which "S2a connectivity" is supported. A non-3GPP access network supports "S2a connectivity" with a PLMN when it deploys a TWAG function that can connect with a PGW in this PLMN, via an S2a interface; see clause 16 of TS 23.402 [43]. +- 3) A PLMN List-3, which includes PLMNs with which "5G connectivity" is supported. A non-3GPP access network supports "5G connectivity" with a PLMN when it deploys a TNGF function that can connect with an AMF function and an UPF function in this PLMN via N2 and N3 interfaces, respectively; see clause 4.2.8. + +When the UE wants to discover the PLMN List(s) supported by a non-3GPP access network and the non-3GPP access network supports ANQP, the UE shall send an ANQP query to the non-3GPP access network requesting "3GPP Cellular Network" information. If the non-3GPP access network supports interworking with one or more PLMNs, the response received by the UE includes a "3GPP Cellular Network" information element containing one or more of the + +above three PLMN Lists. The PLMN List-1 and the PLMN List-2 are specified in TS 23.402 [43] and indicate support of interworking with EPC in one or more PLMNs. The PLMN List-3 is a list used to indicate support of interworking with 5GC in one or more PLMNs. When the non-3GPP access network does not support ANQP, how the UE discovers the PLMN List(s) supported by the non-3GPP access network is not defined in the present specification. + +The UE determines if a non-3GPP access network supports "trusted connectivity" to a specific PLMN by receiving the PLMN List-2 and the PLMN List-3 advertised by this access network. If this PLMN is not included in any of these lists, then the non-3GPP access network can only support connectivity to an ePDG or N3IWF in the PLMN (i.e. "untrusted connectivity"). + +![Figure 6.3.12.1-1: Example deployment scenario for trusted Non-3GPP access network selection. The diagram shows a UE connected to an NG-RAN via an N1 interface. The NG-RAN is connected to a 5GC via an N2/N3 (5G) interface. The 5GC is connected to an EPC (PLMN-a) via an N2/N3 (5G) interface. The EPC (PLMN-a) is connected to a 5GC (PLMN-b) via an N2/N3 (5G) interface. The 5GC (PLMN-b) is connected to an EPC (PLMN-c) via an N2/N3 (5G) interface. The EPC (PLMN-c) is connected to a 5GC (PLMN-d) via an N2/N3 (5G) interface. The 5GC (PLMN-d) is connected to an EPC (PLMN-d) via an N2/N3 (5G) interface. The UE is also connected to five WLAN Access Networks (WLAN 1 to 5). WLAN 1 (SSID=x1) contains a TNGF and an AAA. It supports PLMN-c via PLMN List-1 (AAA) and PLMN-a, PLMN-b via PLMN List-3 (5G connectivity). WLAN 2 (SSID=x2) contains an AAA and a TWAG. It supports PLMN-a, PLMN-c via PLMN List-1 (AAA), PLMN-a, PLMN-c via PLMN List-2 (S2a connectivity), and PLMN-b via PLMN List-3 (5G connectivity). WLAN 3 (SSID=x3) contains a TWAG and an AAA. It supports PLMN-d via PLMN List-1 (AAA) and PLMN-d via PLMN List-2 (S2a connectivity). WLAN 4 (SSID=x4) contains a TNGF. It supports PLMN-c via PLMN List-3 (5G connectivity). WLAN 5 (SSID=x5) supports no PLMNs. Connections from the WLANs to the PLMNs are labeled S1a, S2a, and N2/N3 (5G).](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +Figure 6.3.12.1-1: Example deployment scenario for trusted Non-3GPP access network selection. The diagram shows a UE connected to an NG-RAN via an N1 interface. The NG-RAN is connected to a 5GC via an N2/N3 (5G) interface. The 5GC is connected to an EPC (PLMN-a) via an N2/N3 (5G) interface. The EPC (PLMN-a) is connected to a 5GC (PLMN-b) via an N2/N3 (5G) interface. The 5GC (PLMN-b) is connected to an EPC (PLMN-c) via an N2/N3 (5G) interface. The EPC (PLMN-c) is connected to a 5GC (PLMN-d) via an N2/N3 (5G) interface. The 5GC (PLMN-d) is connected to an EPC (PLMN-d) via an N2/N3 (5G) interface. The UE is also connected to five WLAN Access Networks (WLAN 1 to 5). WLAN 1 (SSID=x1) contains a TNGF and an AAA. It supports PLMN-c via PLMN List-1 (AAA) and PLMN-a, PLMN-b via PLMN List-3 (5G connectivity). WLAN 2 (SSID=x2) contains an AAA and a TWAG. It supports PLMN-a, PLMN-c via PLMN List-1 (AAA), PLMN-a, PLMN-c via PLMN List-2 (S2a connectivity), and PLMN-b via PLMN List-3 (5G connectivity). WLAN 3 (SSID=x3) contains a TWAG and an AAA. It supports PLMN-d via PLMN List-1 (AAA) and PLMN-d via PLMN List-2 (S2a connectivity). WLAN 4 (SSID=x4) contains a TNGF. It supports PLMN-c via PLMN List-3 (5G connectivity). WLAN 5 (SSID=x5) supports no PLMNs. Connections from the WLANs to the PLMNs are labeled S1a, S2a, and N2/N3 (5G). + +**Figure 6.3.12.1-1: Example deployment scenario for trusted Non-3GPP access network selection** + +#### 6.3.12.2 Access Network Selection Procedure + +The steps below specify the steps executed by the UE when the UE wants to select and connect to a PLMN over trusted non-3GPP access. Note that the UE executes these steps before connecting to a trusted non-3GPP access network. This is different from the untrusted non-3GPP access (see clause 6.3.6, "N3IWF selection"), where the UE first connects to a non-3GPP access network, it obtains IP configuration and then proceeds to PLMN selection and ePDG/N3IWF selection. In the case of trusted non-3GPP access, the UE uses 3GPP-based authentication for connecting to a non-3GPP access, so it must first select a PLMN and then attempt to connect to a non-3GPP access. + +Step 1: The UE constructs a list of available PLMNs, with which trusted connectivity is supported. This list contains the PLMNs included in the PLMN List-2 and PLMN List-3, advertised by all discovered non-3GPP access networks. For each PLMN the supported type(s) of trusted connectivity is also included. + +- a. In the example shown in Figure 6.3.12.1-1, the list of available PLMNs includes: + - PLMN-a: "S2a connectivity", "5G connectivity" + - PLMN-b: "5G connectivity" + - PLMN-c: "S2a connectivity", "5G connectivity" + - PLMN-d: "S2a connectivity" + +Step 2: The UE selects a PLMN that is included in the list of available PLMNs, as follows: + +- a. If the UE is connected to a PLMN via 3GPP access and this PLMN is included in the list of available PLMNs, the UE selects this PLMN. If this PLMN is not included in the list of available PLMNs, but it is included in the "Non-3GPP access node selection information" in the UE (see clause 6.3.6.1), the UE selects this PLMN and executes the combined ePDG/N3IWF selection procedure specified in clause 6.3.6.3. +- b. Otherwise (the UE is not connected to a PLMN via 3GPP access, or the UE is connected to a PLMN via 3GPP access but this PLMN is neither in the list of available PLMNs nor in the "Non-3GPP access node selection information"), the UE determines the country it is located in by using implementation specific means. + - i) If the UE determines to be located in its home country, then: + - The UE selects the HPLMN, if included in the list of available PLMNs. Otherwise, the UE selects an E-HPLMN (Equivalent HPLMN), if an E-HPLMN is included in the list of available PLMNs. If the list of available PLMNs does not include the HPLMN and does not include an E-HPLMN, the UE stops the procedure and may attempt to connect via untrusted non-3GPP access (i.e. it may execute the N3IWF selection procedure specified in clause 6.3.6). + - ii) If the UE determines to be located in a visited country, then: + - The UE determines if it is mandatory to select a PLMN in the visited country, as follows: + - If the UE has IP connectivity (e.g. the UE is connected via 3GPP access), the UE sends a DNS query and receives a DNS response that indicates if a PLMN must be selected in the visited country. The DNS response includes also a lifetime that denotes how long the DNS response can be cached for. The FQDN in the DNS query shall be different from the Visited Country FQDN (see TS 23.003 [19]) that is used for ePDG/N3IWF selection. The DNS response shall not include a list of PLMNs that support trusted connectivity in the visited country, but shall only include an indication of whether a PLMN must be selected in the visited country or not. + - If the UE has no IP connectivity (e.g. the UE is not connected via 3GPP access), then the UE may use a cached DNS response that was received in the past, or may use local configuration that indicates which visited countries mandate a PLMN selection in the visited country. + - If the UE determines that it is not mandatory to select a PLMN in the visited country, and the HPLMN or an E-HPLMN is included in the list of available PLMNs, then the UE selects the HPLMN or an E-HPLMN, whichever is included in the list of available PLMNs. + - Otherwise, the UE selects a PLMN in the visited country by considering, in priority order, the PLMNs, first, in the User Controlled PLMN Selector list and, next, in the Operator Controlled PLMN Selector list (see TS 23.122 [17]). The UE selects the highest priority PLMN in a PLMN Selector list that is also included in the list of available PLMNs; + - If the list of available PLMNs does not include a PLMN that is also included in a PLMN Selector list, the UE stops the procedure and may attempt to connect via untrusted non-3GPP access. +- c. In the example shown in Figure 6.3.12.1-1, the UE may select PLMN-c, for which "S2a connectivity" and "5G connectivity" is supported. + +Step 3: The UE selects the type of trusted connectivity ("S2a connectivity" or "5G connectivity") for connecting to the selected PLMN, as follows: + +- a. If the list of available PLMNs indicates that both "S2a connectivity" and "5G connectivity" is supported for the selected PLMN, then the UE shall select "5G connectivity" because it is the preferred type of trusted access. +- b. Otherwise, if the list of available PLMNs indicates that only one type of trusted connectivity (either "S2a connectivity" or "5G connectivity") is supported for the selected PLMN, the UE selects this type of trusted connectivity. +- c. In the example shown in Figure 6.3.12.1-1, the UE may select PLMN-c and "5G connectivity". There are two non-3GPP access networks that support "5G connectivity" to PLMN-c: the WLAN access network 2 and the WLAN access network 4. + +Step 4: Finally, the UE selects a non-3GPP access network to connect to, as follows: + +- a. The UE puts the available non-3GPP access networks in priority order. For WLAN access, the UE constructs a prioritized list of WLAN access networks by using the WLANSP rules (if provided) and the procedure specified in clause 6.6.1.3 of TS 23.503 [45]. When the UE supports the selection of Trusted access supporting the network slices it desires to use and has received extended WLANSP rule as specified in clause 6.6.1.1 of TS 23.503 [45], the UE selects the non-3GPP access network with the SSID(s) which can access to the TNGF supporting the S-NSSAI needed by the UE. If the UE is not provided with WLANSP rules, the UE constructs the prioritized list of WLAN access networks by using an implementation specific procedure. For other types of non-3GPP access, the UE may use access specific information to construct this prioritized list. +- b. From the prioritized list of non-3GPP access networks, the UE selects the highest priority non-3GPP access network that supports the selected type of trusted connectivity to the selected PLMN. +- c. In the example shown in Figure 6.3.12.1-1, the UE selects either the WLAN access network 2 or the WLAN access network 4, whichever has the highest priority in the prioritized list of non-3GPP access networks. +- d. Over the selected non-3GPP access network, the UE starts the 5GC registration procedure specified in clause 4.12a.2.2 of TS 23.502 [3]. +- e. If the AMF detects the UE is using a wrong TNGF, the AMF may trigger a UE policy update and reject the UE registration + +During the registration procedure the AMF may determine if the TNGF selected by the UE is suitable for the S-NSSAI(s) requested by the UE considering the UE subscription. If the AMF determines that a different TNGF should be selected as described in clause 4.12a.2.2 of TS 23.502 [3], the AMF: + +- may, if the UE supports slice-based TNGF selection, triggers the UE Policy Association Establishment or UE Policy Association Update procedure to provide the UE with updated TNGF selection information as described in clause 6.15.2.1; when the AMF is informed by the PCF that the update of UE policy information on the UE is completed as described in clause 4.12a.2.2 of TS 23.502 [3], the AMF releases UE Policy Association if the UE is not registered over 3GPP access before proceeding to the Registration Reject over trusted non-3GPP access; + +NOTE 1: To enable the V-PCF to provide the UE with Slice-specific TNGF selection information in the roaming case, the AMF provides the V-PCF with the Configured NSSAI for the serving PLMN during the UE Policy Association Establishment/Update procedure. + +- shall send a Registration Reject message to the UE. The AMF may include target TNAN information (SSID, TNGF ID) in the Registration Reject so that the UE can, if supported by the UE, use the target TNAN information to try again to register to 5GC if the UE wishes to send the same Requested NSSAI as during the previous Registration Request. The target TNAN information only applies to the one TNAN selection performed by the UE just after receiving the Registration Reject. + +The AMF may determine the target TNAN based on the list of supported TAs and the corresponding list of supported slices for each TA obtained as defined in clause 5.15.8, and considering UE location. + +NOTE 2: The operator is assumed to ensure that UEs that do not support slice-based TNGF selection always select a TNGF that supports at least one slice requested by the UE. This is to avoid unnecessary and potentially repetitive rejections of those UEs. To ensure this, the operator is assumed to provide identifiers of TNGFs that only support a subset of the slices configured in the network only to UEs that support slice-based TNGF selection. + +### 6.3.12a Access Network selection for devices that do not support 5GC NAS over WLAN + +#### 6.3.12a.1 General + +As specified in clause 4.2.8.5, devices that do not support 5GC NAS signalling over WLAN access (referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short), may access 5GC in a PLMN or an SNPN via a trusted WLAN access network that supports a TWIF function. The following clause specifies (a) how a N5CW device selects a PLMN and (b) how it selects a trusted WLAN access network that can provide "5G connectivity-without-NAS" to the selected PLMN. This selection procedure is called access network selection. + +NOTE: For N5CW device accessing an SNPN refer to clause 5.30.2.15. + +Each WLAN access network that provides "5G connectivity-without-NAS" advertises with ANQP a list of PLMNs with which "5G connectivity-without-NAS" is supported. This list is called PLMN List-4, and is different from the PLMN List-1, PLMN List-2 and PLMN List-3 defined in clause 6.3.12. A WLAN advertises the PLMN List-4, when the WLAN supports a TWIF function. + +#### 6.3.12a.2 Access Network Selection Procedure + +The steps executed by a N5CW device for access network selection are specified below and are very similar with the corresponding steps executed by a UE that supports NAS; see clause 6.3.12.2. + +Step 1: The N5CW device constructs a list of available PLMNs. This list contains the PLMNs included in the PLMN List-4 advertised by all discovered WLAN access networks. + +- a. The N5CW device discovers the PLMN List-4 advertised by all discovered WLAN access networks by sending an ANQP query to each discovered WLAN access network. The ANQP query shall request "3GPP Cellular Network" information. If a WLAN access network supports interworking with one or more PLMNs, the ANQP response received by the N5CW device includes a "3GPP Cellular Network" information element containing one or more of the following lists: PLMN List-1, PLMN List-2, PLMN List-3 and PLMN List-4. The PLMN List-1, PLMN List-2 and PLMN List-3 are defined in clause 6.3.12. The PLMN List-4 includes the PLMNs with which "5G connectivity-without-NAS" is supported. + +Step 2: The N5CW device selects a PLMN that is included in the list of available PLMNs as follows. + +- a. If the N5CW device is connected to a PLMN via 3GPP access and this PLMN is included in the list of available PLMNs, then the N5CW device selects this PLMN. +- b. Otherwise (the N5CW device is not connected to a PLMN via 3GPP access, or the N5CW device is connected to a PLMN via 3GPP access but this PLMN is not in the list of available PLMNs): + - i) If the N5CW device determines to be located in its home country, then: + - The N5CW device selects the HPLMN if the N5CW device has a USIM or is pre-configured with an HPLMN, if the HPLMN is included in the list of available PLMNs. Otherwise, the N5CW device selects an E-HPLMN (Equivalent HPLMN), if an E-HPLMN is included in the list of available PLMNs. If the list of available PLMNs does not include the HPLMN and does not include an E-HPLMN, the N5CW device stops the access network selection procedure. + - ii) If the N5CW device determines to be located in its visited country, then: + - The N5CW device determines if it is mandatory to select a PLMN in the visited country, as follows: + - If the N5CW device has IP connectivity (e.g. it is connected via 3GPP access), the N5CW device sends a DNS query and receives a DNS response that indicates if a PLMN must be selected in the + +visited country. The DNS response includes a lifetime that denotes how long the DNS response can be cached. + +- If the N5CW device has no IP connectivity (e.g. it is not connected via 3GPP access), then the N5CW device may use a cached DNS response that was received in the past, or may use local configuration that indicates which visited countries mandate a PLMN selection in the visited country. +- If the N5CW device determines that it is not mandatory to select a PLMN in the visited country, and the HPLMN or an E-HPLMN is included in the list of available PLMNs, then the N5CW device selects the HPLMN or an E-HPLMN, whichever is included in the list of available PLMNs. +- Otherwise, the N5CW device selects a PLMN in the visited country as follows: + - If the N5CW device has a USIM, the UE selects a PLMN in the visited country by considering, in priority order, the PLMNs, first, in the User Controlled PLMN Selector list and, next, in the Operator Controlled PLMN Selector list (see TS 23.122 [17]). + - If the N5CW device does not have a USIM, the N5CW device selects the highest priority PLMN in a pre-configured list, which is also included in the list of available PLMNs. + +- If the list of available PLMNs does not include a PLMN that is also included in the pre-configured list(s), the N5CW device either stops the access network selection procedure, or may select a PLMN based on its own implementation. + +Step 3: Finally, the N5CW device selects a WLAN access network (e.g. an SSID) to connect to, following the procedure specified in clause 6.6.1.3 of TS 23.503 [45], "UE procedure for selecting a WLAN access based on WLANSP rules", or any other implementation specific means. + +After the N5CW device completes the above access network selection procedure, the N5CW device initiates the "Initial Registration and PDU Session Establishment" procedure specified in clause 4.12b.2 of TS 23.502 [3]. + +### 6.3.12b Access Network selection for 5G NSWO + +In addition to the PLMN lists specified in clause 6.3.12 and in clause 6.3.12a, a WLAN access network may also advertise the following PLMN list: + +- A PLMN List-5, which includes candidate PLMNs with which "AAA connectivity to 5GC" is supported. A WLAN access network supports "AAA connectivity to 5GC" in a candidate PLMN when it deploys an AAA function that can connect with a NSWOF in this PLMN or can connect with a NSWOF in another PLMN (i.e. HPLMN in roaming case) via AAA proxy. The NSWOF supports "WLAN connection using 5G credentials without 5GS registration", as defined in clause 4.2.15. + +If the UE selects a PLMN that is neither UE's HPLMN nor EHPLMN through which the NSWO request should be sent towards the HPLMN, the UE shall use the decorated NAI format as specified in clause 4.2.15 and in TS 23.003 [19]. + +For access to SNPN or CH, a WLAN access network may also advertise the following SNPN list: + +- A SNPN List-5, which includes SNPNs with which "AAA connectivity to 5GC" is supported. The SNPNs are the candidate serving SNPNs that the WLAN access network can connect with. A WLAN access network supports "AAA connectivity to 5GC" in a SNPN when it deploys an AAA function that can connect with a NSWOF in this SNPN or can connect with a NSWOF or AAA server in a CH via AAA Proxy. The SNPN or CH supports "WLAN connection using 5G credentials without 5GS registration", as defined in clause 4.2.15. + +NOTE: The selected SNPN within the SNPN List-5 is interpreted as serving SNPN when the SNPN does not correspond to UE's subscribed SNPN. + +When the UE wants to connect to a WLAN access network using the 5G NSWO procedure defined in TS 33.501 [29], Annex S, the UE may retrieve the PLMN List-5 or SNPN List-5 advertised by each discovered WLAN access network and may consider this list for selecting the WLAN access network to connect to. For example, if the UE identifies that the HPLMN or CH is included in the PLMN List-5 or SNPN List-5 advertised by a WLAN access network, the UE may select this WLAN access network to connect to using the 5G NSWO procedure. + +When the UE is configured by HPLMN or CH to use 5G NSWO for connecting to WLAN access networks using its 5G credentials (as defined in TS 33.501 [29]), the UE shall attempt to select a WLAN that supports 5G NSWO and shall only use the 5G NSWO procedure for connecting to the selected WLAN. + +A WLAN access network may also advertise a list of SNPNs which includes SNPNs with which "AAA connectivity to 5GC" is supported. A WLAN access network supports "AAA connectivity to 5GC" in an SNPN when it deploys an AAA function that can connect with a SNPN or CH using any of the architectures defined in clause 4.2.15. When the UE operating in SNPN access mode wants to connect to a WLAN access network using the 5G NSWO procedure defined in Annex S of TS 33.501 [29], the UE may retrieve the SNPNs with which "AAA connectivity to 5GC" is supported that are advertised by each discovered WLAN access network and may consider this information for selecting the WLAN access network to which it attempts to connect. + +### 6.3.13 NWDAF discovery and selection + +Multiple instances of NWDAF may be deployed in a network. + +The NF consumers shall utilize the NRF to discover NWDAF instance(s) unless NWDAF information is available by other means, e.g. locally configured on NF consumers. NF consumers may make an additional query to UDM, when supported, as detailed below. The NWDAF selection function in NF consumers selects an NWDAF instance based on the available NWDAF instances. + +The NRF may return one or more candidate NWDAF instance(s) and each candidate NWDAF instance (based on its registered profile) supports the Analytics ID with a time that is less than or equal to the Supported Analytics Delay. + +The following factors may be considered by the NF consumer for NWDAF selection: + +- S-NSSAI. +- Analytics ID(s). +- Supported service(s), possibly with their associated Analytics IDs. +- NWDAF Serving Area information, i.e. list of TAIIs, for which the NWDAF can provide analytics, train ML models and provide trained ML models and/or data; for each item of this list, a weight may be defined in the NWDAF NF profile to indicate the priority of the NWDAF to cover the TA. + +NOTE 1: If all services provided by one NWDAF do not support the same Analytics ID, the NWDAF registers the Analytics IDs of the services at the service level. + +NOTE 2: Analytics ID(s) at service level take precedence over Analytics ID(s) at NF level. + +NOTE 3: For discovery of NWDAF supporting Nnwdaf\_AnalyticsSubscription or Nnwdaf\_AnalyticsInfo services, the Analytics IDs at the NWDAF NF profile are used. + +- (only when DCCF is hosted by NWDAF): + - NF type of the data source. + - NF Set ID of the data source. + +NOTE 4: Can be used when the NWDAF determines that it needs to discover another NWDAF which is responsible for co-ordinating the collection of required data. The NWDAF does a new discovery for a target NWDAF via NRF using NF Set ID of the data source. + +NOTE 5: For discovery of NWDAF supporting Nnwdaf\_DataManagement service, at least the NWDAF Serving Area information from the NWDAF profile are used. + +NOTE 6: The presence of NF type of data source or NF set ID of the data source denotes that the NWDAF can collect data from such NF Sets or NF Types. + +- Supported Analytics Delay of the requested Analytics ID(s) (see clause 6.2.6.2). + +In the case of multiple instances of NWDAFs deployment, following factors may also be considered: + +- NWDAF Capabilities: + - Analytics aggregation capability. + - Analytics metadata provisioning capability. + - Accuracy checking capability. + +Applicable when NF consumer cannot determine a suitable NWDAF instance based on NRF discovery response, and when NWDAF registration in UDM is supported, as defined in clause 5.2 of TS 23.288 [86]: NF consumers may query UDM (Nudm\_UECM\_Get service operation) for determining the ID of the NWDAF serving the UE. The following factors may be considered by NF consumers to select an NWDAF instance already serving a UE for an Analytics ID: + +- SUPI. +- Analytics ID(s). + +When selecting an NWDAF for ML model provisioning, the following additional factors may be considered by the NWDAF: + +- The ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest (see clause 5.2, TS 23.288 [86]) for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID, if available. + +When selecting an NWDAF that supports Federated Learning, the following additional factors may be considered by the NWDAF: + +- Time Period of Interest: time interval [start...end], during which the Federated Learning will be performed. +- when selecting FL client NWDAF: + +- FL capability type as FL client NWDAF per Analytics ID. +- NF type(s) of the data source(s) where data can be collected as input for local model training. +- NF Set ID(s) of the data source(s) where data can be collected as input for local model training. +- ML Model Interoperability indicator. +- when selecting FL server NWDAF: + - FL capability type as FL server NWDAF per Analytics ID. + - The ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest (see clause 5.2 of TS 23.288 [86]) for the trained ML model(s) per Analytics ID(s), if available. + +When selecting a NWDAF for roaming case, the detailed mechanism is defined in clause 5.2 of TS 23.288 [86]. + +### 6.3.14 NEF Discovery + +The NF consumers may utilize the NRF to discover NEF instance(s) unless NEF information is available by other means, e.g. locally configured in NF consumers. The NRF provides NF profile(s) of NEF instance(s) to the NF consumers. + +The IP address(es)/port(s) of the NEF or L-NEF may be locally configured in the AF, or the AF may discover the FQDN or IP address(es)/port(s) of the NEF/L-NEF by performing a DNS query using the External Identifier of an individual UE or using the External Group Identifier of a group of UEs or using EDNS Client Subnet, or, if the AF is trusted by the operator, the AF may utilize the NRF to discover the FQDN or IP address(es)/port(s) of the NEF or L-NEF. + +NOTE 1: When the AF discovers the FQDN or IP address(es)/port(s) of the NEF/L-NEF by performing a DNS query, the AF can add in its DNS request an EDNS Client Subnet option in order to help the DNS determine a local NEF directly. The use of a DNS query for the selection of a L-NEF is only supported for AF and not internal network functions. + +NOTE 2: The EDNS Client Subnet may be derived by the AF based on factors that are considered for NEF selection. Whether and which factors are considered for NEF/L-NEF selection may depend on whether the AF performs an initial NEF discovery or a NEF discovery due to L-PSA relocation. + +NOTE 3: The NEF discovery and selection procedures described in this clause are intended to be applied by NF consumers deployed within the operator's domain. + +NOTE 4: The NEF supporting the capabilities can be configured in the AF or discovered by AF with the assistance of NRF. + +The following factors may be considered for NEF selection: + +- S-NSSAI(s); +- S-NSSAI and DNN corresponding to an untrusted AF; +- Event ID(s) supported by an AF (see clause 6.2.6, clause 6.2.2.3 of TS 23.288 [86] and clause 5.2.19 of TS 23.502 [3]); +- AF Instance ID, Application Identifier; +- External Identifier, External Group Identifier, or domain name; +- A request for local NEF selection; +- Location (see locality in clause 6.1.6.2.2 of TS 29.510 [58]); +- (for local NEF selection) List of supported TAI; +- (for local NEF selection) List of supported DNAI; +- Capability of NEF to support UAS NF functionality for UUAA procedures; +- Capability of NEF to support Multi-member AF session with required QoS for a set of UEs identified by a list of UE addresses; +- Capability of NEF to support member UE selection assistance functionality. + +Local NEF instance(s) can be deployed close to UE access. For local NEF selection, the location of the local NEF instance (e.g. geographical location, data centre) may be used in conjunction with the location of L-PSA UPF or AF. + +### 6.3.15 UCMF Discovery and Selection + +The AMF, MME, NEF, AF, SCEF, SCS/AS may utilize the NRF to discover UCMF instance(s) unless UCMF information is available by other means, e.g. locally configured in UCMF services consumers. + +In the case of delegated discovery and selection in SCP, the NF consumer shall forward the request towards SCP. + +### 6.3.16 SCP discovery and selection + +An NF is configured with its serving SCP(s). + +In a deployment where several SCPs are deployed, a message may traverse several SCP instances until reaching its final destination. A SCP may discover and select a next hop SCP by querying the Nnrf\_NFDiscovery Service of the NRF or it may be configured with next SCP in the message path. + +An SCP may use the SCP profile parameters in clause 6.2.6.3 as discovery parameters in Nnrf\_NFDiscovery. The parameter(s) to be used depend(s) on network deployment. The NRF returns a list SCP Profiles as per the provided discovery parameters. + +If an SCP receives a Routing Binding Indication within a service or notification request and decides to forward that request to a next-hop SCP, it shall include the Routing Binding Indication in the forwarded request. + +NOTE: It is up to SCP implementation, deployment specific configuration and operator policies as to how the SCP will use information retrieved from the NRF to resolve the optimal route to a producer. + +Based on SCP configuration, an SCP deciding to address a next-hop SCP for a service request may then delegate the NF (instance) and/or service (instance) selection to subsequent SCPs and provide discovery and selection parameters to the next-hop SCP. + +### 6.3.17 NSSAAF discovery and selection + +In the case of NF consumer based discovery and selection, the following applies: + +- The NF consumer (e.g. AMF, AUSF) performs NSSAAF selection to select an NSSAAF Instance that supports authentication between the UE and the AAA-S associated with the HPLMN or in the Credentials Holder in the case of SNPN or in the DCS domain in the case of ON-SNPN. The NF consumer shall utilize the NRF to discover the NSSAAF instance(s) unless NSSAAF information is available by other means, e.g. locally configured on the NF consumer. The NSSAAF selection function in the NF consumer selects an NSSAAF instance based on the available NSSAAF instances (obtained from the NRF or locally configured in the NF consumer). + +In the case of SNPN, NSSAAF selection is only applicable to 3GPP access. Otherwise, NSSAAF selection is applicable to both 3GPP access and non-3GPP access. + +The NSSAAF selection function in NSSAAF NF consumers or in SCP should consider the following factor when it is available: + +1. Home Network Identifier (e.g. MNC and MCC, realm) of SUPI (by an NF consumer in the Serving network). +2. S-NSSAI of the HPLMN. +3. SUPI or Internal Group ID; the NSSAAF NF consumer selects a NSSAAF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI or Internal Group ID as input for NSSAAF discovery. + +An HPLMN deploying NSSAAF instances supporting specific S-NSSAIs and/or sets of SUPIs (according to factors 2-3) shall also deploy NSSAAF instance(s) that can be selected using factor 1 if they need to interoperate with VPLMNs using only factor 1 for NSSAAF selection. + +In the case of delegated discovery and selection in SCP, the NSSAAF NF consumer shall send all available factors to the SCP. + +### 6.3.18 5G-EIR discovery and selection + +A consumer NF of the 5G-EIR performs discovery of 5G-EIR using either configuration or NRF as specified in clause 6.3.1. The network is configured with the 5G-EIR to serve the PLMN of the NF consumer requesting the 5G-EIR service, i.e. no roaming interface is defined. + +The 5G-EIR selection function in NF consumers is independent of Access Type. + +### 6.3.19 DCCF discovery and selection + +Multiple instances of DCCF may be deployed in a network. + +The NF consumers shall utilize the NRF to discover DCCF instance(s) unless DCCF information is available by other means, e.g. locally configured on NF consumers. The DCCF selection function in NF consumers selects a DCCF instance based on the available DCCF instances. + +The following factors may be considered by the NF consumer for DCCF selection: + +- DCCF Serving Area information, i.e. list of TAIs for which the DCCF coordinates Data Sources. +- S-NSSAI. +- NF type of the data source. +- NF Set ID of the data source. + +NOTE: NF Set ID can be used when the NF consumer is a DCCF when the DCCF determines that it needs to discover another DCCF which is responsible for co-ordinating the collection of required data. The DCCF discovers a target DCCF via NRF using NF Set ID of the data source. + +- DCCF relocation capability: Support for relocating the data collection subscription among DCCFs. + +### 6.3.20 ADRF discovery and selection + +Multiple instances of ADRF may be deployed in a network. + +The NF consumers shall utilize the NRF to discover ADRF instance(s) unless ADRF information is available by other means, e.g. locally configured on NF consumers. The ADRF selection function in NF consumers selects an ADRF instance based on the available ADRF instances. + +NOTE: When NF consumer is DCCF, the DCCF can have information available already from previous registrations of ADRFs. In this case, NRF discovery is not needed. + +The following factors may be considered by the NF consumer for ADRF selection: + +- S-NSSAI. +- ML model storage capability. + +### 6.3.21 MFAF discovery and selection + +Multiple instances of MFAF may be deployed in a network. + +The MFAF selection function is supported by the DCCF. The DCCF shall utilize the NRF to discover MFAF instance(s) unless MFAF information is available by other means, e.g. locally configured on the DCCF. The MFAF selection function in the DCCF selects a MFAF instance based on the available MFAF instances. + +The following factors may be considered by the DCCF for MFAF selection: + +- S-NSSAI; +- NF Types of the Data Sources handled by the MFAF; +- NF Set IDs of the Data Sources handled by the MFAF; +- MFAF Serving Area information, i.e. list of TAIs for which the MFAF may receive data from Data Sources. + +### 6.3.22 NSACF discovery and selection + +The NF consumers shall utilise the NRF to discover NSACF instance(s), including the NSACF acting as Primary NSACF role, unless NSACF information is available by other means, e.g. locally configured in NF consumers. + +The NSACF selection function in the NSACF NF consumer selects an NSACF instance based on the available NSACF instances, which are obtained from the NRF or locally configured in the NSACF NF consumer. + +The following factors may be considered by the NF consumer for NSACF discovery and selection: + +- S-NSSAI(s). +- NSAC Service Area Identifier, or a reserved value "Entire PLMN" for discovering the NSACF acting as Primary NSACF or centralized NSAC role. The NSAC Service Area Identifier is configured at the consumer NF and NSACF (see clause 5.15.11.0). Each Service Area Identifier is a unique and unambiguous identifier and a NSACF registers with the NRF the NSAC Service Area Identifier(s) of the NSAC Service Area(s) it serves. "Entire PLMN" is indicated in roaming case to the NRF of HPLMN by the VPLMN NF consumer when the VPLMN NF consumer needs to discover the HPLMN NSACF, or in non roaming case to select a Primary NSACF. +- NSACF service capabilities: + - Support monitoring and controlling the number of registered UEs per network slice for the network slice that is subject to NSAC. + - Support, for network slices that are subject to NSAC and configured to support EPS counting, monitoring and controlling the number of registered UEs with at least one PDU session per network slice, as defined in clause 5.15.11.5a. + - Support monitoring and controlling the number of established PDU Sessions per network slice for the network slice that is subject to NSAC. +- PLMN ID information in the case of roaming to contact the HPLMN NSACF for inbound roamers. + +In the case of delegated discovery and selection in SCP, the NSACF NF consumer shall send all available and applicable factors to the SCP. + +### 6.3.23 EASDF discovery and selection + +Multiple instances of EASDF may be deployed in a network. NF consumers mentioned in this clause are SMF(s). + +The NF consumers shall utilize the NRF to discover EASDF instance(s) unless EASDF information is available by other means, e.g. locally configured on the NF consumer. The EASDF selection function in NF consumers or SCP selects an EASDF instance based on the available EASDF instances. + +The following factors may be considered by the NF consumer or SCP for EASDF selection: + +- S-NSSAI. +- DNN. +- the N6 IP address of the EASDF. + +NOTE: The IP address of the EASDF is not used for EASDF discovery. It can be used is to select an EASDF that is "IP near" to the PSA of the PDU Session. + +- The N6 IP address of the PSA UPF. +- Location as per NF profile. +- DNAI (if exist). + +### 6.3.24 TSCTSF Discovery + +The NFs (e.g. NEF, AF and PCF) may utilize the NRF to discover TSCTSF instance(s) unless TSCTSF information is available by other means, e.g. locally configured in the requested NF. + +The following factors may be considered for TSCTSF discovery and selection: + +- DNN and S-NSSAI. When the NF discovers the TSCTSF for a DNN/S-NSSAI, the NRF provides the NF with NF profile(s) of TSCTSF instance(s) belonging to single TSCTSF Set for a given DNN/S-NSSAI. For example, the same TSCTSF Set shall be selected by the PCF serving PDU Sessions for this DNN and S-NSSAI to notify the TSCTSF for a PDU Session that is potentially impacted by the (g)PTP time synchronization service. +- GPSI or External Group Identifier. TSCTSF NF consumers (which manage network signalling not based on SUPI/SUCI (e.g. the NEF)) select a TSCTSF instance based on the GPSI or External Group ID range the UE's GPSI or External Group ID belongs to or based on the results of a discovery procedure with NRF using the UE's GPSI or External Group ID as input for TSCTSF discovery. +- SUPI or Internal Group ID. TSCTSF NF consumers select a TSCTSF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI or Internal Group ID as input for TSCTSF discovery. + +If the TSCTSF is locally configured in NFs, it shall be ensured that the same TSCTSF Set is configured in all NFs (e.g. NEF, AF and PCF) for the given DNN and S-NSSAI. + +NOTE: Thus, it is assumed that there is only one TSCTSF Set for a given DNN/S-NSSAI in this Release of the specification. + +### 6.3.25 AF Discovery and Selection + +The NF consumers (e.g. NWDAF) may utilize the NRF to discover AF instance(s) in the MNO domain, i.e. trusted AF(s), unless AF information is available by other means, e.g. locally configured in NF consumers. The NRF provides NF profile(s) of AF instance(s) to the NF consumers. + +The following factors may be considered for AF discovery and selection: + +- One or multiple combination(s) of the S-NSSAI and DNN corresponding to an AF. +- Supported Application Id(s). +- Event ID(s) Supported by an AF. +- Internal-Group Identifier. + +The NF consumer (e.g. NWDAF) may select an AF instance, in the MNO domain, considering one or multiple combination(s) of the S-NSSAI and DNN corresponding to an AF and the EventID(s) supported by an AF to provide the input data required for generation of analytics. The NF consumer (e.g. NWDAF) may consider the supported Application Id(s), if the input data is required only for those applications. The NF consumer (e.g. NWDAF) may consider the Internal-Group Identifier supported by the AF if the input data is required for a particular group of UEs. + +### 6.3.26 NRF discovery and selection + +The following mechanisms may be used for discovery of NRF service instances and their endpoint addresses: + +- NF consumers or SCP may have all the NRF services instances and their endpoint addresses locally configured. +- NF consumers or SCP may have the endpoint address of a NRF discovery service locally configured and utilize it to discover the NRF(s) and get the NF profile(s) of the NRF(s). +- NF consumers (e.g. v-NRF) or SCP may have endpoint addresses of the NRF bootstrapping service and utilize it to discover the NRF service instances and their endpoint addresses. The NRF bootstrapping service is a version independent API, which may be especially useful over roaming interfaces. +- The NF consumer, e.g. AMF, may use the Nnsnf\_NSSelection service to get the endpoint address of a NRF discovery service for a certain slice. + +# 7 Network Function Services and descriptions + +## 7.1 Network Function Service Framework + +### 7.1.1 General + +Service Framework functionalities include e.g. service registration/de-registration, consumer authorization, service discovery, and inter service communication, which include selection and message passing. Four communication options are listed in Annex E and can all co-exist within one and the same network. + +An NF service is one type of capability exposed by an NF (NF Service Producer) to other authorized NF (NF Service Consumer) through a service-based interface. A Network Function may expose one or more NF services. Following are criteria for specifying NF services: + +- NF services are derived from the system procedures that describe end-to-end functionality, where applicable (see TS 23.502 [3], Annex B drafting rules). Services may also be defined based on information flows from other 3GPP specifications. +- System procedures can be described by a sequence of NF service invocations. + +NF services may communicate directly between NF Service consumers and NF Service Producers, or indirectly via an SCP. Direct and Indirect Communication are illustrated in Figure 7.1.1-1. For more information, see Annex E and clauses 6.3.1 and 7.1.2. Whether a NF Service Consumer (e.g. in the case of requests or subscriptions) or NF Service Producer (e.g. in the case of notifications) uses Direct Communication or Indirect Communication by using an SCP is based on the local configuration of the NF Service Consumer/NF Service Producer. An NF may not use SCP for all its communication based on the local configuration. + +NOTE: The SCP can be deployed in a distributed manner. + +In Direct Communication, the NF Service consumer performs discovery of the target NF Service producer by local configuration or via NRF. The NF Service consumer communicates with the target NF Service producer directly. + +In Indirect Communication, the NF Service consumer communicates with the target NF Service producer via a SCP. The NF Service consumer may be configured to perform discovery of the target NF Service producer directly, or delegate the discovery of the target NF Service Producer to the SCP used for Indirect Communication. In the latter case, the SCP uses the parameters provided by NF Service consumer to perform discovery and/or selection of the target NF Service producer. The SCP address may be locally configured in NF Service consumer. + +![Diagram illustrating NF/NF service inter communication. It is divided into two parts by a vertical line. The left part, labeled 'Direct communication', shows two boxes labeled 'NF A' and 'NF B' connected by a single horizontal line. The right part, labeled 'Indirect communication', shows three boxes: 'NF A', 'SCP', and 'NF B', connected in a sequence by horizontal lines (NF A to SCP, and SCP to NF B).](740442c999390734911677f01af0316d_img.jpg) + +Diagram illustrating NF/NF service inter communication. It is divided into two parts by a vertical line. The left part, labeled 'Direct communication', shows two boxes labeled 'NF A' and 'NF B' connected by a single horizontal line. The right part, labeled 'Indirect communication', shows three boxes: 'NF A', 'SCP', and 'NF B', connected in a sequence by horizontal lines (NF A to SCP, and SCP to NF B). + +Figure 7.1.1-1: NF/NF service inter communication + +### 7.1.2 NF Service Consumer - NF Service Producer interactions + +The end-to-end interaction between two Network Functions (Consumer and Producer) within this NF service framework follows two mechanisms, irrespective of whether Direct Communication or Indirect Communication is used: + +- "Request-response": A Control Plane NF\_B (NF Service Producer) is requested by another Control Plane NF\_A (NF Service Consumer) to provide a certain NF service, which either performs an action or provides information or both. NF\_B provides an NF service based on the request by NF\_A. In order to fulfil the request, NF\_B may in turn consume NF services from other NFs. In Request-response mechanism, communication is one to one + +between two NFs (consumer and producer) and a one-time response from the producer to a request from the consumer is expected within a certain timeframe. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0) in the Response, which may be used by the NF Service Consumer to select suitable NF service producer instance(s) for subsequent requests. For indirect communication, the NF Service Consumer copies the Binding Indication into the Routing Binding indication, that is included in subsequent requests, to be used by the SCP to discover a suitable NF service producer instance(s). + +![Figure 7.1.2-1: 'Request-response' NF Service illustration. A sequence diagram showing a Request message from NF_A (Consumer) to NF_B (Producer) and a Response message from NF_B (Producer) back to NF_A (Consumer).](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +``` + +sequenceDiagram + participant NF_A as NF_A (Consumer) + participant NF_B as NF_B (Producer) + Note right of NF_A: Request + NF_A->>NF_B: Request + Note left of NF_B: Response + NF_B-->>NF_A: Response + +``` + +Figure 7.1.2-1: 'Request-response' NF Service illustration. A sequence diagram showing a Request message from NF\_A (Consumer) to NF\_B (Producer) and a Response message from NF\_B (Producer) back to NF\_A (Consumer). + +**Figure 7.1.2-1: "Request-response" NF Service illustration** + +- "Subscribe-Notify": A Control Plane NF\_A (NF Service Consumer) subscribes to NF Service offered by another Control Plane NF\_B (NF Service Producer). Multiple Control Plane NFs may subscribe to the same Control Plane NF Service. NF\_B notifies the results of this NF service to the interested NF(s) that subscribed to this NF service. The subscription request shall include the notification endpoint, i.e. a Notification Target Address and a Notification Correlation ID (e.g. the callback URL) of the NF Service Consumer to which the event notification from the NF Service Producer should be sent to. + +NOTE 1: The notification endpoint can be a URL and contains both the Notification Target Address and the Notification Correlation ID. + +The NF Service Consumer may add a Binding Indication (see clause 6.3.1.0) in the subscribe request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding Indication, that is included in the response, to be used by the SCP to discover a suitable notification target. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0) in the subscribe response, which may be used by the NF Service Consumer (or SCP) to select suitable NF service producer instance(s) or NF producer service instance. In addition, the subscription request may include notification request for periodic updates or notification triggered through certain events (e.g. the information requested gets changed, reaches certain threshold etc.). The subscription for notification can be done through one of the following ways: + +- Explicit subscription: A separate request/response exchange between the NF Service Consumer and the NF Service Producer; or +- Implicit subscription: The subscription for notification is included as part of another NF service operation of the same NF Service; or +- Default notification endpoint: Registration of a notification endpoint for each type of notification the NF consumer is interested to receive, as a NF service parameter with the NRF during the NF and NF service Registration procedure as specified in clause 4.17.1 of TS 23.502 [3]. + +The NF Service Consumer may also add a Binding Indication (see clause 6.3.1.0) in the response to the notification request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding indication that is included in subsequent notification requests. The binding indication is then used by the SCP to discover a suitable notification target. + +![Figure 7.1.2-2: 'Subscribe-Notify' NF Service illustration 1. A sequence diagram showing a Subscribe message from NF_A (Consumer) to NF_B (Producer) and a Notify message from NF_B (Producer) back to NF_A (Consumer). The Subscribe message is a dashed line, and the Notify message is a solid line with a break in the middle.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) + +``` + +sequenceDiagram + participant NF_A as NF_A (Consumer) + participant NF_B as NF_B (Producer) + Note right of NF_A: Subscribe + NF_A-->>NF_B: Subscribe + Note left of NF_B: Notify + NF_B-->>NF_A: Notify + +``` + +Figure 7.1.2-2: 'Subscribe-Notify' NF Service illustration 1. A sequence diagram showing a Subscribe message from NF\_A (Consumer) to NF\_B (Producer) and a Notify message from NF\_B (Producer) back to NF\_A (Consumer). The Subscribe message is a dashed line, and the Notify message is a solid line with a break in the middle. + +**Figure 7.1.2-2: "Subscribe-Notify" NF Service illustration 1** + +A Control Plane NF\_A may also subscribe to NF Service offered by Control Plane NF\_B on behalf of Control Plane NF\_C, i.e. it requests the NF Service Producer to send the event notification to another consumer(s). In + +this case, NF\_A includes the notification endpoint, i.e. Notification Target Address) and a Notification Correlation ID, of the NF\_C in the subscription request. NF\_A may also additionally include the notification endpoint and a Notification Correlation ID of NF\_A associated with subscription change related Event ID(s), e.g. Subscription Correlation ID Change, in the subscription request, so that NF\_A can receive the notification of the subscription change related event. The NF\_A may add Binding Indication (see clause 6.3.1.0) in the subscribe request. + +![Figure 7.1.2-3: 'Subscribe-Notify' NF Service illustration 2. A sequence diagram showing three Network Functions: NF_A (Consumer), NF_B (Producer), and NF_C (Consumer). NF_A sends a 'Subscribe' message to NF_B. NF_B then sends a 'Notify' message to NF_C. Each lifeline has a break symbol.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` + +sequenceDiagram + participant NF_A as NF_A (Consumer) + participant NF_B as NF_B (Producer) + participant NF_C as NF_C (Consumer) + Note left of NF_A: [Break] + NF_A->>NF_B: Subscribe + Note right of NF_B: [Break] + NF_B->>NF_C: Notify + Note right of NF_C: [Break] + +``` + +Figure 7.1.2-3: 'Subscribe-Notify' NF Service illustration 2. A sequence diagram showing three Network Functions: NF\_A (Consumer), NF\_B (Producer), and NF\_C (Consumer). NF\_A sends a 'Subscribe' message to NF\_B. NF\_B then sends a 'Notify' message to NF\_C. Each lifeline has a break symbol. + +**Figure 7.1.2-3: "Subscribe-Notify" NF Service illustration 2** + +Routing of the messages for the NF interaction mechanisms above may be direct, as shown in the figures 7.1.2-1 to 7.1.2-3, or indirect. In the case of Indirect Communication, an SCP is employed by the NF service consumer. The SCP routes messages between NF service consumers and NF service producers based on the Routing Binding Indication if available, and may do discovery and associated selection of the NF service producer on behalf of a NF service consumer. Figure 7.1.2-4 shows the principle for a request-response interaction and figure 7.1.2-5 shows an example of a subscribe-notify interaction. + +![Figure 7.1.2-4: Request response using Indirect Communication. A sequence diagram showing three entities: NF_A (Consumer), SCP, and NF_B (Producer). NF_A sends a 'Request' to the SCP. The SCP forwards the 'Request' to NF_B. NF_B returns a 'Response' to the SCP, which then forwards the 'Response' back to NF_A.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +``` + +sequenceDiagram + participant NF_A as NF_A (Consumer) + participant SCP as SCP + participant NF_B as NF_B (Producer) + NF_A->>SCP: Request + SCP->>NF_B: Request + NF_B->>SCP: Response + SCP->>NF_A: Response + +``` + +Figure 7.1.2-4: Request response using Indirect Communication. A sequence diagram showing three entities: NF\_A (Consumer), SCP, and NF\_B (Producer). NF\_A sends a 'Request' to the SCP. The SCP forwards the 'Request' to NF\_B. NF\_B returns a 'Response' to the SCP, which then forwards the 'Response' back to NF\_A. + +**Figure 7.1.2-4: Request response using Indirect Communication** + +![Figure 7.1.2-5: Subscribe-Notify using Indirect Communication. A sequence diagram showing four entities: NF_A (Consumer), SCP, NF_B (Producer), and NF_C. NF_A sends a 'Subscribe' message to the SCP. The SCP forwards the 'Subscribe' message to NF_B. NF_B sends a 'Notify' message to the SCP. The SCP then forwards the 'Notify' message to NF_C. Each lifeline has a break symbol.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +``` + +sequenceDiagram + participant NF_A as NF_A (Consumer) + participant SCP as SCP + participant NF_B as NF_B (Producer) + participant NF_C as NF_C + Note left of NF_A: [Break] + NF_A->>SCP: Subscribe + Note right of SCP: [Break] + SCP->>NF_B: Subscribe + Note right of NF_B: [Break] + NF_B->>SCP: Notify + Note right of SCP: [Break] + SCP->>NF_C: Notify + Note right of NF_C: [Break] + +``` + +Figure 7.1.2-5: Subscribe-Notify using Indirect Communication. A sequence diagram showing four entities: NF\_A (Consumer), SCP, NF\_B (Producer), and NF\_C. NF\_A sends a 'Subscribe' message to the SCP. The SCP forwards the 'Subscribe' message to NF\_B. NF\_B sends a 'Notify' message to the SCP. The SCP then forwards the 'Notify' message to NF\_C. Each lifeline has a break symbol. + +**Figure 7.1.2-5: Subscribe-Notify using Indirect Communication** + +NOTE: The subscribe request and notify request can be routed by different SCPs. + +### 7.1.3 Network Function Service discovery + +A Control Plane Network function (NF) within the 5G Core network may expose its capabilities as services via its service based interface, which can be re-used by Control Plane CN NFs. + +The NF service discovery enables a CN NF or SCP to discover NF instance(s) that provide the expected NF service(s). The NF service discovery is implemented via the NF discovery functionality. + +For more detail NF discovery refer to clause 6.3.1. + +### 7.1.4 Network Function Service Authorization + +NF service authorization shall ensure the NF Service Consumer is authorized to access the NF service provided by the NF Service Provider, according to e.g. the policy of NF, the policy from the serving operator, the inter-operator agreement. + +Service authorization information shall be configured as one of the components in NF profile of the NF Service Producer. It shall include the NF type (s) and NF realms/origins allowed to consume NF Service(s) of NF Service Producer. + +Due to roaming agreements and operator policies, a NF Service Consumer shall be authorised based on UE/subscriber/roaming information and NF type, the Service authorization may entail two steps: + +- Check whether the NF Service Consumer is permitted to discover the requested NF Service Producer instance during the NF service discovery procedure. This is performed on a per NF granularity by NRF. + +NOTE 1: When NF discovery is performed based on local configuration, it is assumed that locally configured NFs are authorized. + +- Check whether the NF Service Consumer is permitted to access the requested NF Service Producer for consuming the NF service, with a request type granularity. This is performed on a per UE, subscription or roaming agreements granularity. This type of NF Service authorization shall be embedded in the related NF service logic. + +NOTE 2: The security of the connection between NF Service Consumer and NF Service Producer is specified in TS 33.501 [29]. + +NOTE 3: It is expected that an NF authorization framework exists in order to perform consumer NF authorization considering UE, subscription or roaming agreements granularity. This authorization is assumed to be performed without configuration of the NRF regarding UE, subscription or roaming information. + +### 7.1.5 Network Function and Network Function Service registration and de-registration + +For the NRF to properly maintain the information of available NF instances and their supported services, each NF instance informs the NRF of the list of NF services that it supports. + +NOTE: The NF informs the appropriate NRF based on configuration. + +The NF instance may make this information available to NRF when the NF instance becomes operative for the first time (registration operation) or upon individual NF service instance activation/de-activation within the NF instance (update operation) e.g. triggered after a scaling operation. The NF instance while registering the list of NF services it supports, for each NF service, may provide a notification endpoint information for each type of notification service that the NF service is prepared to consume, to the NRF during the NF instance registration. The NF instance may also update or delete the NF service related parameters (e.g. to delete the notification endpoint information). Alternatively, another authorised entity (such as an OA&M function) may inform the NRF on behalf of an NF instance triggered by an NF service instance lifecycle event (register or de-registration operation depending on instance instantiation, termination, activation, or de-activation). Registration with the NRF includes capacity and configuration information at time of instantiation. + +The NF instance may also de-registers from the NRF when it is about to gracefully shut down or disconnect from the network in a controlled way. If an NF instance become unavailable or unreachable due to unplanned errors (e.g. NF crashes or there are network issues), an authorised entity shall de-register the NF instance with the NRF. + +## 7.2 Network Function Services + +### 7.2.1 General + +In the context of this specification, an NF service is offering a capability to authorised consumers. + +Network Functions may offer different capabilities and thus, different NF services to distinct consumers. Each of the NF services offered by a Network Function shall be self-contained, reusable and use management schemes independently of other NF services offered by the same Network Function (e.g. for scaling, healing, etc). + +The discovery of the NF instance and NF service instance is specified in clause 6.3.1. + +NOTE 1: There can be dependencies between NF services within the same Network Function due to sharing some common resources, e.g. context data. This does not preclude that NF services offered by a single Network Function are managed independently of each other. + +![Diagram of a Network Function containing multiple NF Services.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +A diagram showing a large rounded rectangle labeled "NETWORK FUNCTION" in the top right corner. Inside this rectangle, there are three gray rounded rectangles arranged horizontally, labeled "NF SERVICE 1", "NF SERVICE 2", and "NF SERVICE n" from left to right. An ellipsis is placed between "NF SERVICE 2" and "NF SERVICE n". + +Diagram of a Network Function containing multiple NF Services. + +Figure 7.2.1-1: Network Function and NF Service + +Each NF service shall be accessible by means of an interface. An interface may consist of one or several operations. + +![Diagram of a Network Function containing multiple NF Services, each with associated operations.](5a95b187de0044da69b7322e04761b86_img.jpg) + +A diagram showing a large rounded rectangle labeled "NETWORK FUNCTION" in the bottom right corner. Inside this rectangle, there are three gray rounded rectangles arranged horizontally, labeled "NF SERVICE 1", "NF SERVICE 2", and "NF SERVICE n" from left to right. An ellipsis is placed between "NF SERVICE 2" and "NF SERVICE n". Above each service, there is a vertical arrow pointing upwards to a horizontal line that spans across the top of the services. The arrows are labeled with operation names: "Nnf\_nfservice1" for the first service, "Nnf\_nfservice2\_operation1" and "Nnf\_nfservice2\_operation2" for the second service, and "Nnf\_nfservicen" for the nth service. + +Diagram of a Network Function containing multiple NF Services, each with associated operations. + +Figure 7.2.1-2: Network Function, NF Service and NF Service Operation + +System procedures, as specified in TS 23.502 [3] can be built by invocation of a number of NF services. The following figure shows an illustrative example on how a procedure can be built; it is not expected that system procedures depict the details of the NF Services within each Network Function. + +![Figure 7.2.1-3: System Procedures and NF Services. A sequence diagram showing interactions between Network Function A, Network Function B, and Network Function C. Network Function A contains NF SERVICE A2 to NF SERVICE An. Network Function B contains NF SERVICE B1 to NF SERVICE Bn and CONSUMER An. Network Function C contains CONSUMER B1, CONSUMER A2, and CONSUMER Bn. Arrows indicate service requests: from NF SERVICE A2 to CONSUMER A2, from NF SERVICE B1 to CONSUMER B1, and from CONSUMER An to CONSUMER Bn.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 7.2.1-3: System Procedures and NF Services. A sequence diagram showing interactions between Network Function A, Network Function B, and Network Function C. Network Function A contains NF SERVICE A2 to NF SERVICE An. Network Function B contains NF SERVICE B1 to NF SERVICE Bn and CONSUMER An. Network Function C contains CONSUMER B1, CONSUMER A2, and CONSUMER Bn. Arrows indicate service requests: from NF SERVICE A2 to CONSUMER A2, from NF SERVICE B1 to CONSUMER B1, and from CONSUMER An to CONSUMER Bn. + +**Figure 7.2.1-3: System Procedures and NF Services** + +NOTE 2: The SCP can be used for indirect communication between NF/NF service instances. For simplicity the SCP is not shown in the procedure. + +The following clauses provide for each NF the NF services it exposes through its service based interfaces. + +### 7.2.2 AMF Services + +The following NF services are specified for AMF: + +**Table 7.2.2-1: NF Services provided by AMF** + +| Service Name | Description | Reference in TS 23.502 [3] or indicated other TS | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| Namf_Communication | Enables an NF consumer to communicate with the UE and/or the AN through the AMF. This service enables SMF to request EBI allocation to support interworking with EPS. This service also supports PWS functionality as described in TS 23.041 [46]. | 5.2.2.2 | +| Namf_EventExposure | Enables other NF consumers to subscribe or get notified of the mobility related events and statistics. | 5.2.2.3 | +| Namf_MT | Enables an NF consumer to make sure UE is reachable. | 5.2.2.4 | +| Namf_Location | Enables an NF consumer to request location information for a target UE. | 5.2.2.5 | +| Namf_MBSSroadcast | Enables the NF consumer to communicate with the NG-RAN for broadcast communication. | TS 23.247 [129] | +| Namf_MBSSCommunication | Enables NF consumer to communicate with the NG-RAN for multicast communication. | TS 23.247 [129] | + +### 7.2.3 SMF Services + +The following NF services are specified for SMF: + +**Table 7.2.3-1: NF Services provided by SMF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| Nsmf_PDUSession | This service manages the PDU Sessions and uses the policy and charging rules received from the PCF. The service operations exposed by this NF service allows the consumer NFs to handle the PDU Sessions. | 5.2.8.2 | +| Nsmf_EventExposure | This service exposes the events happening on the PDU Sessions to the consumer NFs. | 5.2.8.3 | +| Nsmf_NIDD | This service is used for NIDD transfer between SMF and another NF. | 5.2.8.4 | +| Nsmf_TrafficCorrelation | Used for SMF determined information related to the members of the set of UEs identified by traffic correlation ID as defined in clause 6.2.3.2.7 of TS 23.548 [130], | 5.2.8.5 | + +### 7.2.4 PCF Services + +The following NF services are specified for PCF: + +**Table 7.2.4-1: NF Services provided by PCF** + +| Service Name | Description | Reference in TS 23.502 [3] or indicated other TS | +|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| +| Npcf_AMPolicyControl | This PCF service provides Access Control, network selection and Mobility Management related policies, UE Route Selection Policies to the NF consumers. | 5.2.5.2 | +| Npcf_SMPolicyControl | This PCF service provides session related policies to the NF consumers. | 5.2.5.4 | +| Npcf_PolicyAuthorization | This PCF service authorises an AF request and creates policies as requested by the authorised AF for the PDU Session to which the AF session is bound to. This service allows the NF consumer to subscribe/unsubscribe to the notification of Access Type and RAT type, PLMN identifier, access network information, usage report etc. | 5.2.5.3 | +| Npcf_BDTPolicyControl | This PCF service provides background data transfer policy negotiation and optionally notification for the renegotiation to the NF consumers. | 5.2.5.5 | +| Npcf_UEPolicyControl | This PCF service provides the management of UE Policy Association to the NF consumers. | 5.2.5.6 | +| Npcf_EventExposure | This PCF service provide the support for event exposure. | 5.2.5.7 | +| Npcf_AMPolicyAuthorization | The PCF authorises an AF request and uses it as input for deciding access and mobility management related policies for a UE. | 5.2.5.8 | +| Npcf_MBSPolicyControl | The PCF service provides MBS session related policies towards the MB-SMF. | TS 23.247 [129] | +| Npcf_MBSPolicyAuthorization | This service authorizes an AF / NEF / MBSF request for an MBS service and creates policies as requested by the authorized AF for the MBS Service. | TS 23.247 [129] | +| Npcf_PDTQPolicyControl | This PCF service provides negotiation for Planned Data Transfer with QoS requirements policy and optionally notification for the renegotiation to the NF consumers. | 5.2.5.9 | + +### 7.2.5 UDM Services + +The following NF services are specified for UDM: + +**Table 7.2.5-1: NF Services provided by UDM** + +| Service Name | Description | Reference in TS 23.502 [3] or indicated other TS | +|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| +| Nudm_UECM |
  1. 1. Provide the NF consumer of the information related to UE's transaction information, e.g. UE's serving NF identifier, UE status, etc.
  2. 2. Allow the NF consumer to register and deregister its information for the serving UE in the UDM.
  3. 3. Allow the NF consumer to update some UE context information in the UDM.
| 5.2.3.2 | +| Nudm_SDM |
  1. 1. Allow NF consumer to retrieve user subscription data when necessary.
  2. 2. Provide updated user subscriber data to the subscribed NF consumer.
| 5.2.3.3 | +| Nudm_UEAuthentication |
  1. 1. Provide updated authentication related subscriber data to the subscribed NF consumer.
  2. 2. For AKA based authentication, this operation can be also used to recover from security context synchronization failure situations.
  3. 3. Used for being informed about the result of an authentication procedure with a UE.
| 5.2.3.4 | +| Nudm_EventExposure |
  1. 1. Allow NF consumer to subscribe to receive an event.
  2. 2. Provide monitoring indication of the event to the subscribed NF consumer.
| 5.2.3.5 | +| Nudm_ParameterProvision |
  1. 1. To provision information which can be used for the UE in 5GS.
| 5.2.3.6 | +| Nudm_NIDDAuthorisation |
  1. 1. To authorise an NIDD configuration request for the received External Group Identifier or GPSI.
| 5.2.3.7 | +| Nudm_ServiceSpecificAuthorisation |
  1. 1. To authorise for a specific service configuration.
| 5.2.3.8 | +| Nudm_ReportSMDelivery Status |
  1. 1. To report the SM-Delivery Status to UDM.
| 5.2.3.9 | +| Nudm_MT |
  1. 1. UE state and domain selection info for terminating services.
| TS 23.632 [102] | + +### 7.2.6 NRF Services + +The following NF services are specified for NRF: + +**Table 7.2.6-1: NF Services provided by NRF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| Nnrf_NFManagement | Provides support for register, deregister and update service to NF, NF services, SCP. Provide NF service consumers and SCP with notifications of newly registered/updated/deregistered NF along with its NF services. Also Provide SCP with notifications of newly registered/updated/deregistered SCP. | 5.2.7.2 | +| Nnrf_NFDiscovery | Enables one NF service consumer or SCP to discover a set of NF instances with specific NF service or a target NF type. Also enables one NF service consumer or SCP to discover a specific NF service. Also enables a SCP to discover a next hop SCP. | 5.2.7.3 | +| Nnrf_AccessToken | Provides OAuth2 2.0 Access Tokens for NF to NF authorization as defined in TS 33.501 [29]. | 5.2.7.4 | +| Nnrf_Bootstrapping | Lets NF Service Consumers of the NRF know about the services endpoints it supports, the NRF Instance ID and NRF Set ID if the NRF is part of an NRF set. | 5.2.7.5 | + +### 7.2.7 AUSF Services + +The following NF services are specified for AUSF: + +**Table 7.2.7-1: NF Services provided by AUSF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| Nausf_UEauthentication | The AUSF provides UE authentication service to requester NF. For AKA based authentication, this operation can also be used to recover from security context synchronization failure situations. | 5.2.10.2 | +| Nausf_SoRProtection | The AUSF provides protection of Steering of Roaming information service to the requester NF. | 5.2.10.3 | +| Nausf_UPUProtection | The AUSF provides the UE Parameters Update protection service to the requester NF. | 5.2.10.4 | + +### 7.2.8 NEF Services + +The following NF services are specified for NEF: + +**Table 7.2.8-1: NF Services provided by NEF** + +| Service Name | Description | Reference in TS 23.502 [3] or other TS | +|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| Nnef_EventExposure | Provides support for event exposure. | 5.2.6.2 | +| Nnef_PFDManagement | Provides support for PFDs management. | 5.2.6.3 | +| Nnef_ParameterProvision | Provides support to provision information which can be used for the UE in 5GS. | 5.2.6.4 | +| Nnef_Trigger | Provides support for device triggering. | 5.2.6.5 | +| Nnef_BDTPNegotiation | Provides support for background data transfer policy negotiation and optionally notification for the renegotiation. | 5.2.6.6 | +| Nnef_TrafficInfluence | Provide the ability to influence traffic routing. | 5.2.6.7 | +| Nnef_ChargeableParty | Requests to become the chargeable party for a data session for a UE. | 5.2.6.8 | +| Nnef_AFsessionWithQoS | Requests the network to provide a specific QoS for an AF session. | 5.2.6.9 | +| Nnef_MSISDN-less_MO_SMS | Used by the NEF to send MSISDN-less MO SM to the AF. | 5.2.6.10 | +| Nnef_ServiceParameter | Provides support to provision service specific information. | 5.2.6.11 | +| Nnef_APISupportCapability | Provides support for awareness on availability or expected level of a service API. | 5.2.6.12 | +| Nnef_NIDDConfiguration | Used for configuring necessary information for data delivery via the NIDD API. | 5.2.6.13 | +| Nnef_NIDD | Used for NEF anchored MO and MT unstructured data transport. | 5.2.6.14 | +| Nnef_SMContext | Provides the capability to create, update or release the SMF-NEF Connection. | 5.2.6.15 | +| Nnef_AnalyticsExposure | Provides support for exposure of network analytics. | 5.2.6.16 | +| Nnef_UCMFProvisioning | Provides the ability to configure the UCMF with dictionary entries consisting of UE manufacturer-assigned UE Radio Capability IDs, the corresponding UE radio capabilities, the corresponding UE Radio Capability for Paging and the (list of) associated IMEI/TAC value(s) via the NEF. The UE radio capabilities the NEF provides for a UE radio Capability ID can be in TS 36.331 [51] format, TS 38.331 [28] format or both formats. Also used for deletion (e.g. as no longer used) or update (e.g. to add or remove a (list of) IMEI/TAC value(s) associated to an entry) of dictionary entries in the UCMF. | 5.2.6.17 | +| Nnef_ECRestriction | Provides support for queuing status of enhanced coverage restriction, or enable/disable enhanced coverage restriction per individual UEs. | 5.2.6.18 | +| Nnef_ApplyPolicy | Provides the capability to apply a previously negotiated Background Data Transfer Policy to a UE or a group of UEs. | 5.2.6.19 | +| Nnef_Location | Provides the capability to deliver UE location to AF. | 5.2.6.21 | +| Nnef_AMInfluence | Provides the ability to influence access and mobility management related policies for one or multiple UEs. | 5.2.6.22 | +| Nnef_AMPolicyAuthorization | Provides the ability to provide inputs that can be used by the PCF for deciding access and mobility management related policies. | 5.2.6.23 | +| Nnef_AKMA | AKMA Application Key derivation service. | TS 33.535 [124] | +| Nnef_Authentication | This service enables the consumer to authenticate and authorize the Service Level Device Identity as described in TS 23.256 [136]. | TS 23.256 [136] | +| Nnef_TimeSynchronization | Provides the ability to support for (g)PTP or 5G access stratum based time synchronization service. | 5.2.6.25 | +| Nnef_EASDeployment | EAS deployment service. | 5.2.6.26 | + +| Service Name | Description | Reference in TS 23.502 [3] or other TS | +|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Nnef_UEId | UE Identifier service, which supports to retrieve AF specific UE Identifier based on UE address. | 5.2.6.27 | +| Nnef_MBSTMGI | Allows AF to request allocation/deallocation of TMGI(s) for MBS Session. | TS 23.247 [129] | +| Nnef_MBSSession | Allows AF to create, update and delete MBS Session. | TS 23.247 [129] | +| Nnef_MBSGroupMsgDelivery | Allows AF to request to create, update and delete resource for group message delivery via MBS Session. | TS 23.247 [129] | +| Nnef_ASTI | Provides the ability to influence 5G access stratum based time distribution configuration. | 5.2.6.28 | +| Nnef_SMService | Used for SBI-based MO SM transmit through NEF for MSISDN-less MO SMS. | 5.2.6.29 | +| Nnef_PDTQPolicyNegotiation | Provides support for negotiation for Planned Data Transfer with QoS requirements policy and optionally notification for the renegotiation. | 5.2.6.30 | +| Nnef_MemberUESelectionAssistance | Provides one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information based on the parameters contained in the request from the AF. | 5.2.6.31 | +| Nnef_DNAIMapping | Allows AF to obtain DNAI. | 5.2.6.34 | +| Nnef_TrafficInfluenceData | Used in HR SBO as defined in TS 23.548 [130] to get AF Traffic Influence configuration from the V-NEF. | 5.2.6.35 | +| Nnef_ECSAddress | This service is defined only for the support of HR-SBO. It allows AF to provide ECS Address Configuration Information for a group of UE or any UE to V-NEF. It allows V-SMF to subscribe and retrieve ECS Address Configuration Information. | 5.2.6.37 | + +### 7.2.8A Void + +### 7.2.9 SMSF Services + +The following NF services are specified for SMSF: + +**Table 7.2.9-1: NF Services provided by SMSF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| Nsmf_SMService | This service allows AMF to authorize SMS and activate SMS for the served user on SMSF. Additionally, this service allows downlink SMS message transmit from consumer NF to SMSF. | 5.2.9.2 | + +### 7.2.10 UDR Services + +The following NF services are specified for UDR: + +**Table 7.2.10-1: NF Services provided by UDR** + +| Service Name | Description | Reference in TS 23.502 [3] | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| Nudr_DM | Allows NF consumers to retrieve, create, update, subscribe for change notifications, unsubscribe for change notifications and delete data stored in the UDR, based on the set of data applicable to the consumer. This service may also be used to manage operator specific data. | 5.2.12.2 | +| Nudr_GroupIDmap | Allows NF consumers to retrieve a NF group ID corresponding to a subscriber identifier. | 5.2.12.9 | + +### 7.2.11 5G-EIR Services + +The following NF services are specified for 5G-EIR: + +**Table 7.2.11-1: NF Services provided by 5G-EIR** + +| Service Name | Description | Reference in TS 23.502 [3] | +|----------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------| +| N5g-eir_Equipment Identity Check | This service enables the 5G-EIR to check the PEI and check whether the PEI is in the prohibited list or not. | 5.2.4.2 | + +### 7.2.12 NWDAF Services + +The following NF services are specified for NWDAF: + +**Table 7.2.12-1: NF Services provided by NWDAF** + +| Service Name | Description | Reference in TS 23.288 [86] | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| Nnwdaf_AnalyticsSubscription | This service enables the NF service consumers to subscribe/unsubscribe for different type of analytics from NWDAF. | 7.2 | +| Nnwdaf_AnalyticsInfo | This service enables the NF service consumers to request and get different type of analytics information from NWDAF or enables NWDAF to request transfer of analytics context from another NWDAF. | 7.3 | +| Nnwdaf_DataManagement | This service enables the NF service consumer to subscribe/unsubscribe and fetch data from NWDAF. | 7.4 | +| Nnwdaf_ModelProvision | This service enables the consumer to receive a notification when an ML model matching the subscription parameters becomes available in NWDAF containing MTLF. | 7.5 | +| Nnwdaf_ModelInfo | This service enables the consumer to request and get ML Model Information from NWDAF containing MTLF. | 7.6 | +| Nnwdaf_ModelMonitor | This service enables the consumer to subscribe/unsubscribe for ML model accuracy information monitored by an NWDAF (i.e. NWDAF containing AnLF). The service also enables the NWDAF containing AnLF registers the use and monitoring capability for an ML model into the model provider NWDAF, i.e. NWDAF containing MTLF. | 7.9 | +| Nnwdaf_ModelTraining | This service enables ML model training. | 7.10 | +| Nnwdaf_ModelTrainingInfo | This service enables the consumer to request for the information about ML model training based on the ML Model input parameter provided by the consumer. | 7.11 | +| Nnwdaf_RoamingAnalytics | This service enables the consumer to request or to subscribe/unsubscribe for network data analytics related to roaming UE for NWDAF analytics. | 7.7 | +| Nnwdaf_RoamingData | This service enables the consumer to subscribe/unsubscribe for input data related to roaming UE for NWDAF analytics. | 7.8 | + +### 7.2.13 UDSF Services + +The following NF services are specified for UDSF: + +**Table 7.2.13-1: NF Services provided by UDSF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|----------------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| Nudsf_UnstructuredDataManagement | Allows NF consumers to retrieve, create, update, and delete data stored in the UDSF. | 5.2.14.2 | +| Nudsf_Timer | Allows NF consumers to start, stop, update, and search timers in UDSF. NF consumers may be notified about timer expiry. | 5.2.14.3 | + +### 7.2.14 NSSF Services + +The following NF services are specified for NSSF: + +**Table 7.2.14-1: NF Services provided by NSSF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|------------------------|-------------------------------------------------------------------------|----------------------------| +| Nnsf_NSSelection | Provides the requested Network Slice information to the Requester. | 5.2.16.2 | +| Nnsf_NSSAIAvailability | Provides NF consumer on the availability of S-NSSAIs on a per TA basis. | 5.2.16.3 | + +### 7.2.15 BSF Services + +The following NF services are specified for BSF as described in TS 23.503 [45]: + +**Table 7.2.15-1: NF Services provided by BSF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------| +| Nbsf_Management | Allows a PCF to register/deregister itself and to be discoverable by NF service consumers (NOTE 1). | 5.2.13.2 | +| NOTE 1: There may be both PCF for a PDU Session and PCF for a UE. Each of them may separately and independently register itself at the BSF. Each of them may separately and independently be discovered by a consumer of the BSF. | | | + +### 7.2.16 LMF Services + +The following NF services are specified for LMF: + +**Table 7.2.16-1: NF Services provided by LMF** + +| Service Name | Description | Reference in TS 23.273 [87] | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Nlmf_Location | This service enables an NF to request location determination for a target UE for the Immediate Location Request and to subscribe / get notified of the location determination for a Deferred Location Request. It allow NFs to request or subscribe the current geodetic and optionally civic location of a target UE. | 8.3.2 | +| Nlmf_Broadcast | This service enables an NF to receive information related to broadcast of location assistance by an LMF. | 8.3.3 | + +### 7.2.16A GMLC Services + +The following NF services are specified for GMLC: + +**Table 7.2.16A-1: NF Services provided by GMLC** + +| Service Name | Description | Reference in TS 23.273 [87] | +|----------------|-------------------------------------------------------------------------------|-----------------------------| +| Ngmlc_Location | This service enables an NF to request location determination for a target UE. | 8.4 | + +### 7.2.17 CHF Services + +The following NF services for spending limits and charging are specified for CHF. + +**Table 7.2.17-1: NF Services provided by CHF** + +| Service Name | Description | Reference in TS 23.502 [3] or other TS | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Nchf_SpendingLimitControl | This service enables transfer of policy counter status information relating to subscriber spending limits from CHF to NF consumer and described in TS 23.503 [45]. | 5.2.17 | +| Nchf_Converged_Charging | This service enables converged online and offline charging. | TS 32.290 [67] | +| Nchf_OfflineOnlyCharging | This service enables only offline charging. | TS 32.290 [67] | + +### 7.2.18 UCMF Services + +The following NF services are specified for UCMF: + +**Table 7.2.18-1: NF Services provided by UCMF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| Nucmf_Provisioning | Allows the NF consumer to provision a dictionary entry in the UCMF consisting of a Manufacturer-assigned UE Radio Capability ID, the corresponding UE Radio Capability for Paging and the corresponding UE radio capabilities and the (list of) associated IMEI/TAC value(s). The UE radio capabilities the NEF provides for a UE radio Capability ID can be in TS 36.331 [51] format, TS 38.331 [28] format or both formats. Also used for deletion (e.g. as no longer used) or update (e.g. to add or remove a (list of) IMEI/TAC value(s) associated to an entry) of dictionary entries in the UCMF. | 5.2.18.2 | +| Nucmf_UECapabilityManagement | Allows the NF consumer to resolve UE Radio Capability ID (either Manufacturer-assigned or PLMN-assigned) into the corresponding UE radio capabilities and the corresponding UE Radio Capability for Paging. The consumer shall indicate whether it requests a TS 36.331 [51] format or a TS 38.331 [28] format to be provided.
Allows the NF consumer to obtain a PLMN-assigned UE Radio Capability ID for a specific UE radio capabilities. The consumer shall indicate whether the UE radio capabilities sent to UCMF are in TS 36.331 [51] format, TS 38.331 [28], or both.
Allows the NF consumer to subscribe or unsubscribe for notifications of UCMF dictionary entries.
Allows the NF consumer to be notified about creation and deletion of UCMF dictionary entries. | 5.2.18.3 | + +### 7.2.19 AF Services + +The following NF services are specified for AF: + +**Table 7.2.19-1: NF Services provided by AF** + +| Service Name | Description | Reference in TS 23.502 [3] or other TS | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| +| Naf_EventExposure | This service enables consumer NF(s) to subscribe or get notified of the event as described in TS 23.288 [86]. | 5.2.19.2 | +| Naf_ProSe | This service is for ProSe services as described in TS 23.304 [128]. | TS 23.304 [128] | +| Naf_Authentication | This service enables the consumer to authenticate and authorize the Service Level Device Identity as described in TS 23.256 [136]. | TS 23.256 [136] | + +### 7.2.20 NSSAAF Services + +The following NF services are specified for NSSAAF: + +**Table 7.2.20 -1: NF Services provided by NSSAAF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| Nnssaaf_NSSAA | The NSSAAF provides NSSAA service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed. It also provides notification to the current AMF where the UE is of the need to re-authenticate and re-authorize the UE or to revoke the UE authorization. | 5.2.20.2 | +| Nnssaaf_AIW | The NSSAAF provides AIW (AAA interworking) service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed. | 5.2.20.3 | + +### 7.2.21 DCCF Services + +The following NF services are specified for DCCF: + +**Table 7.2.21-1: NF Services provided by DCCF** + +| Service Name | Description | Reference in TS 23.288 [86] | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Ndccf_DataManagement | This service enables a Data Consumer to request data, and have it delivered via a messaging framework or via the DCCF, while avoiding redundant requests to data sources. | 8.2 | +| Ndccf_ContextManagement | This service allows a network function to register/deregister the availability of data with the DCCF. | 8.3 | + +### 7.2.22 MFAF Services + +The following NF services are specified for MFAF: + +**Table 7.2.22-1: NF Services provided by MFAF** + +| Service Name | Description | Reference in TS 23.288 [86] | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Nmfaf_3daDataManagement | This service allows a DCCF to request a messaging framework to provide collected data to consumers or notification endpoints according to processing and formatting instructions. | 9.2 | +| Nmfaf_3caDataManagement | This service allows a messaging framework to provide data to consumers or notification endpoints according to instructions received via the Nmfaf_3da_DataManagement service. | 9.3 | + +### 7.2.23 ADRF Services + +The following NF services are specified for ADRF: + +**Table 7.2.23-1: NF Services provided by ADRF** + +| Service Name | Description | Reference in TS 23.288 [86] | +|-------------------------|-------------------------------------------------------------------------------------------|-----------------------------| +| Nadrf_DataManagement | This service allows consumers to store, retrieve and delete data or analytics in an ADRF. | 10.2 | +| Nadrf_MLModelManagement | This service allows consumers to store, retrieve and delete ML model(s) in an ADRF. | 10.3 | + +### 7.2.24 5G DDNMF Services + +The 5G DDNMF supports the N5g-ddnmf service defined in clause 7.1 of TS 23.304 [128]. + +### 7.2.25 EASDF Services + +The following NF services are specified for EASDF. + +**Table 7.2.25-1: NF Services provided by EASDF** + +| Service Name | Description | Reference in TS 23.548 [130] | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| +| Neasdf_DNSContext | This service enables the consumer to create, update and delete DNS context in EASDF, or subscribe to DNS message reporting from EASDF. DNS contexts in EASDF include rules on how EASDF is to handle DNS messages. | 7.1.2 | +| Neasdf_BaselineDNSPattern | This service enables the consumer to create, update and delete BaselineDNSPattern in EASDF. | 7.1.3 | + +### 7.2.26 TSCTSF Services + +The following NF services are specified for TSCTSF. + +**Table 7.2.26-1: NF Services provided by TSCTSF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| Ntsctsf_TimeSynchronization | Provides support for time synchronization service based on (g)PTP or 5G access stratum time distribution method as described in clause 5.27.1.8. Allows the NF consumer to subscribe for the UE and 5GC capabilities for (g)PTP or 5G access stratum based time synchronization service or time synchronization status information updates. Allows the NF consumer to configure the UEs and the 5GC for the (g)PTP based time synchronization service. | 5.2.27.2 | +| Ntsctsf_QoSandTSCAssistance | Allows the NF consumer to provide QoS parameters and information to create TSC Assistance Container. | 5.2.27.3 | +| Ntsctsf_ASTI | Provides support for time synchronization service based on 5G access stratum time distribution method as described in clause 5.27.1.8. Allows the NF consumer to configure the 5GC and RAN for 5G access stratum based time synchronization service for the UEs and subscribe to time synchronization status information updates. | 5.2.27.4 | + +### 7.2.27 NSACF Services + +The following NF services are specified for NSACF: + +**Table 7.2.27-1: NF Services provided by NSACF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| +| Nnsacf_NSAC | This service enables consumer NF to check the availability per network slice and update the number of UEs registered with a network slice, or the number of UEs with at least one PDU Session/PDN Connection established on a network slice in the case of EPC interworking, or the number of PDU Sessions established on a network slice. | 5.2.21.2 | +| Nnsacf_SliceEventExposure | This service enables consumer NF(s) to subscribe and get notified of the event as described in clause 5.15.11.4. | 5.2.21.4 | + +### 7.2.28 MB-SMF Services + +The following NF service is specified for MB-SMF. + +**Table 7.2.28-1: NF Services provided by MB-SMF** + +| Service Name | Description | Reference in TS 23.247 [129] | +|-------------------|---------------------------------------------------------------------------------------|------------------------------| +| Nmbsmf_TMGI | This service enables NF service consumer to allocate, refresh and deallocate TMGI(s). | 9.1.2 | +| Nmbsmf_MBSSession | This service enables the consumer to create, update and delete the MBS Session. | 9.1.3 | + +### 7.2.29 UPF Services + +The following NF service is specified for UPF. + +**Table 7.2.29-1: NF Services provided by UPF** + +| Service Name | Description | Reference in TS 23.502 [3] | +|---------------------------------------|---------------------------------------------------------------------------|----------------------------| +| Nupf_EventExposure | This service exposes UPF related information to the consumer NFs. | 5.2.26.2 | +| Nupf_GetUEPrivateIPAddrAndIdentifiers | This service exposes UPF information related to NAT information and SUPI. | 5.2.26.3 | + +## 7.3 Exposure + +Network exposure is described in clauses 5.20, 5.20d and in clause 4.15 of TS 23.502 [3]. + +# 8 Control and User Plane Protocol Stacks + +## 8.1 General + +Clause 8 specifies the overall protocol stacks between 5GS entities, e.g. between the UE and the 5GC Network Functions, between the 5G-AN and the 5GC Network Functions, or between the 5GC Network Functions. + +## 8.2 Control Plane Protocol Stacks + +### 8.2.1 Control Plane Protocol Stacks between the 5G-AN and the 5G Core: N2 + +#### 8.2.1.1 General + +NOTE 1: N2 maps to NG-C as defined in TS 38.413 [34]. + +Following procedures are defined over N2: + +- Procedures related with N2 Interface Management and that are not related to an individual UE, such as for Configuration or Reset of the N2 interface. These procedures are intended to be applicable to any access but may correspond to messages that carry some information only on some access (such as information on the default Paging DRX used only for 3GPP access). +- Procedures related with an individual UE: + - Procedures related with NAS Transport. These procedures are intended to be applicable to any access but may correspond to messages that for UL NAS transport carry some access dependent information such as + +User Location Information (e.g. Cell-Id over 3GPP access or other kind of User Location Information for Non-3GPP access). + +- Procedures related with UE context management. These procedures are intended to be applicable to any access. The corresponding messages may carry: + - some information only on some access (such as Mobility Restriction List used only for 3GPP access). + - some information (related e.g. with N3 addressing and with QoS requirements) that is to be transparently forwarded by AMF between the 5G-AN and the SMF. +- Procedures related with resources for PDU Sessions. These procedures are intended to be applicable to any access. They may correspond to messages that carry information (related e.g. with N3 addressing and with QoS requirements) that is to be transparently forwarded by AMF between the 5G-AN and the SMF. +- Procedures related with Hand-Over management. These procedures are intended for 3GPP access only. + +The Control Plane interface between the 5G-AN and the 5G Core supports: + +- The connection of multiple different kinds of 5G-AN (e.g. 3GPP RAN, N3IWF for Un-trusted access to 5GC) to the 5GC via a unique Control Plane protocol: A single NGAP protocol is used for both the 3GPP access and non-3GPP access; +- There is a unique N2 termination point in AMF per access for a given UE regardless of the number (possibly zero) of PDU Sessions of the UE; +- The decoupling between AMF and other functions such as SMF that may need to control the services supported by 5G-AN(s) (e.g. control of the UP resources in the 5G-AN for a PDU Session). For this purpose, NGAP may support information that the AMF is just responsible to relay between the 5G-AN and the SMF. The information can be referred as N2 SM information in TS 23.502 [3] and this specification. + +NOTE 2: The N2 SM information is exchanged between the SMF and the 5G-AN transparently to the AMF. + +#### 8.2.1.2 5G-AN - AMF + +![A large black rectangular box, likely a placeholder for a diagram showing the control plane between the 5G-AN and the AMF.](9d4bac4111fe96f0d6f746b95343cbd8_img.jpg) + +A large black rectangular box, likely a placeholder for a diagram showing the control plane between the 5G-AN and the AMF. + +##### Legend: + +- **NG Application Protocol (NG-AP):** Application Layer Protocol between the 5G-AN node and the AMF. NG-AP is defined in TS 38.413 [34]. +- **Stream Control Transmission Protocol (SCTP):** This protocol guarantees delivery of signalling messages between AMF and 5G-AN node (N2). SCTP is defined in RFC 4960 [44]. + +**Figure 8.2.1.2-1: Control Plane between the 5G-AN and the AMF** + +#### 8.2.1.3 5G-AN - SMF + +![Diagram showing the control plane between the 5G-AN and the SMF. The diagram is mostly black with a white rectangular area in the center. At the top of this white area, there are two lines forming a V-shape, pointing towards the center. To the right of the white area, there is a dashed rectangular box.](474a819357587e34949a3e110ff19b30_img.jpg) + +Diagram showing the control plane between the 5G-AN and the SMF. The diagram is mostly black with a white rectangular area in the center. At the top of this white area, there are two lines forming a V-shape, pointing towards the center. To the right of the white area, there is a dashed rectangular box. + +##### Legend: + +- **N2 SM information:** This is the subset of NG-AP information that the AMF transparently relays between the 5G-AN and the SMF, and is included in the NG-AP messages and the N11 related messages. + +**Figure 8.2.1.3-1: Control Plane between the 5G-AN and the SMF** + +NOTE 1: From the 5G-AN perspective, there is a single termination of N2 i.e. the AMF. + +NOTE 2: For the protocol stack between the AMF and the SMF, see clause 8.2.3. + +### 8.2.2 Control Plane Protocol Stacks between the UE and the 5GC + +#### 8.2.2.1 General + +A single N1 NAS signalling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signalling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE. + +The NAS protocol on N1 comprises a NAS-MM and a NAS-SM components. + +There are multiple cases of protocols between the UE and a core network function (excluding the AMF) that need to be transported over N1 via NAS-MM protocol. Such cases include: + +- Session Management Signalling. +- SMS. +- UE Policy. +- LCS. + +RM/CM NAS messages in NAS-MM and other types of NAS messages (e.g. SM), as well as the corresponding procedures, are decoupled. + +The NAS-MM supports generic capabilities: + +- NAS procedures that terminate at the AMF. This includes: + - Handles Registration Management and Connection Management state machines and procedures with the UE, including NAS transport; the AMF supports following capabilities: + - Decide whether to accept the RM/CM part of N1 signalling during the RM/CM procedures without considering possibly combined other non NAS-MM messages (e.g. SM) in the same NAS signalling contents; + - Know if one NAS message should be routed to another NF (e.g. SMF), or locally processed with the NAS routing capabilities inside during the RM/CM procedures; + - Provide a secure NAS signalling connection (integrity protection, ciphering) between the UE and the AMF, including for the transport of payload; + - Provide access control if it applies; + +- It is possible to transmit the other type of NAS message (e.g. NAS SM) together with an RM/CM NAS message by supporting NAS transport of different types of payload or messages that do not terminate at the AMF, i.e. NAS-SM, SMS, UE Policy and LCS between the UE and the AMF. This includes: + - Information about the Payload type; + - Additional Information for forwarding purposes + - The Payload (e.g. the SM message in the case of SM signalling); +- There is a Single NAS protocol that applies on both 3GPP and non-3GPP access. When an UE is served by a single AMF while the UE is connected over multiple (3GPP/Non 3GPP) accesses, there is a N1 NAS signalling connection per access. + +Security of the NAS messages is provided based on the security context established between the UE and the AMF. + +Figure 8.2.2.1-1 depicts NAS transport of SM signalling, SMS, UE Policy and LCS. + +![Diagram showing NAS transport for SM, SMS, UE Policy and LCS between UE, AMF, SMF, SMSF, PCF, and LMF.](6470d350326789d5306eabcb76533951_img.jpg) + +The diagram illustrates the NAS transport architecture for various services. On the left, the User Equipment (UE) contains a stack of NAS messages: NAS-SM, SMS, UE Policy, and LCS. These are encapsulated in NAS-MM, which is then transported via NAS Transport over a Lower Layer to the Access and Management Function (AMF). The AMF also contains NAS-MM and Lower Layer components. From the AMF, the NAS-MM is forwarded to the Session Management Function (SMF) via the N11 / -Nsmf interface. The SMF then routes the specific NAS messages to their respective destinations: NAS-SM is sent to the SMF itself, SMS is sent to the SMS Function (SMSF) via the N20 / -Nsmf interface, UE Policy is sent to the Policy Control Function (PCF) via the N15 / -Npcf interface, and LCS is sent to the Location Management Function (LMF) via the NL1 / -Nlmf interface. Arrows indicate the flow of these messages from the UE through the AMF and then to the appropriate network functions. + +Diagram showing NAS transport for SM, SMS, UE Policy and LCS between UE, AMF, SMF, SMSF, PCF, and LMF. + +Figure 8.2.2.1-1 NAS transport for SM, SMS, UE Policy and LCS + +#### 8.2.2.2 UE - AMF + +![Diagram illustrating the Control Plane between the UE and the AMF. The diagram shows a stack of protocol layers. On the left, a single box represents the UE. In the center, a box represents the NG-RAN (Radio Access Network). On the right, a stack of four boxes represents the AMF (Access and Management Function). The top layer of the AMF stack is highlighted with a black background and white text, representing the NAS-MM layer. The three layers below it represent the 5G-AN Protocol layer. Arrows indicate the flow of control plane signaling between the UE and the AMF, passing through the NG-RAN.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +Diagram illustrating the Control Plane between the UE and the AMF. The diagram shows a stack of protocol layers. On the left, a single box represents the UE. In the center, a box represents the NG-RAN (Radio Access Network). On the right, a stack of four boxes represents the AMF (Access and Management Function). The top layer of the AMF stack is highlighted with a black background and white text, representing the NAS-MM layer. The three layers below it represent the 5G-AN Protocol layer. Arrows indicate the flow of control plane signaling between the UE and the AMF, passing through the NG-RAN. + +##### Legend: + +- **NAS-MM:** The NAS protocol for MM functionality supports registration management functionality, connection management functionality and user plane connection activation and deactivation. It is also responsible of ciphering and integrity protection of NAS signalling. 5G NAS protocol is defined in TS 24.501 [47] +- **5G-AN Protocol layer:** This set of protocols/layers depends on the 5G-AN. In the case of NG-RAN, the radio protocol between the UE and the NG-RAN node (eNodeB or gNodeB) is specified in TS 36.300 [30] and TS 38.300 [27]. In the case of non-3GPP access, see clause 8.2.4. + +**Figure 8.2.2.2-1: Control Plane between the UE and the AMF** + +#### 8.2.2.3 UE – SMF + +The NAS-SM supports the handling of Session Management between the UE and the SMF. + +The SM signalling message is handled, i.e. created and processed, in the NAS-SM layer of UE and the SMF. The content of the SM signalling message is not interpreted by the AMF. + +The NAS-MM layer handles the SM signalling as follows: + +- For transmission of SM signalling: + - The NAS-MM layer creates a NAS-MM message, including security header, indicating NAS transport of SM signalling, additional information for the receiving NAS-MM to derive how and where to forward the SM signalling message. +- For reception of SM signalling: + - The receiving NAS-MM processes the NAS-MM part of the message, i.e. performs integrity check, and interprets the additional information to derive how and where to derive the SM signalling message. + +The SM message part shall include the PDU Session ID. + +![Control Plane protocol stack between the UE and the SMF diagram](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +This diagram illustrates the control plane protocol stack between a User Equipment (UE) and a Session Management Function (SMF). The stack is shown as a series of layers. At the top, a black bar represents the UE's NAS (Non-Access Stratum) layer, which contains a white box representing the NAS-SM (Session Management) protocol. Below this, a white box represents the RRC (Radio Resource Control) layer. The next layer is a black bar representing the AMF (Access and Management Function). Below the AMF, a white box represents the N11 interface. The final layer at the bottom is a white box representing the SMF. Arrows indicate the flow of signaling messages between the UE and the SMF, passing through the AMF. + +Control Plane protocol stack between the UE and the SMF diagram + +##### **Legend:** + +- **NAS-SM:** The NAS protocol for SM functionality supports user plane PDU Session Establishment, modification and release. It is transferred via the AMF, and transparent to the AMF. 5G NAS protocol is defined in TS 24.501 [47] + +**Figure 8.2.2.3-1: Control Plane protocol stack between the UE and the SMF** + +### 8.2.3 Control Plane Protocol Stacks between the network functions in 5GC + +#### 8.2.3.1 The Control Plane Protocol Stack for the service based interface + +The control plane protocol(s) for the service-based interfaces listed in clause 4.2.6 is defined in the TS 29.500 [49] + +#### 8.2.3.2 The Control Plane protocol stack for the N4 interface between SMF and UPF + +The control plane protocol for SMF-UPF (i.e. N4 reference point) is defined in TS 29.244 [65]. + +### 8.2.4 Control Plane for untrusted non 3GPP Access + +![Control Plane before the signalling IPsec SA is established between UE and N3IWF diagram](0977b81510f7649846289ee785d20e74_img.jpg) + +This diagram shows the control plane before the signaling IPsec SA is established between the UE and the N3IWF (Non-3GPP InterWorking Function). The stack consists of several layers. At the top is a black bar representing the UE. Below it is a white box representing the NAS layer. The next layer is a white box representing the RRC layer. Below the RRC layer is a white box representing the N3IWF. The bottom layer is a white box representing the AMF. Arrows indicate the signaling path from the UE, through the NAS and RRC layers, to the N3IWF, and then to the AMF. + +Control Plane before the signalling IPsec SA is established between UE and N3IWF diagram + +**Figure 8.2.4-1: Control Plane before the signalling IPsec SA is established between UE and N3IWF** + +![Diagram showing the control plane after the signalling IPsec SA is established between UE and N3IWF. It depicts a User Equipment (UE) on the left with multiple protocol layers, an N3IWF in the center with a tunnel icon, and a UPF on the right. Arrows show bidirectional traffic flow between the UE and N3IWF, and between the N3IWF and UPF.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Diagram showing the control plane after the signalling IPsec SA is established between UE and N3IWF. It depicts a User Equipment (UE) on the left with multiple protocol layers, an N3IWF in the center with a tunnel icon, and a UPF on the right. Arrows show bidirectional traffic flow between the UE and N3IWF, and between the N3IWF and UPF. + +Figure 8.2.4-2: Control Plane after the signalling IPsec SA is established between UE and N3IWF + +Large NAS messages may be fragmented by the "inner IP" layer or by TCP. + +![Diagram showing the control plane for establishment of user-plane via N3IWF. It shows the UE, N3IWF, and UPF. Arrows indicate the signaling path from the UE through the N3IWF to the UPF, and the return path.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +Diagram showing the control plane for establishment of user-plane via N3IWF. It shows the UE, N3IWF, and UPF. Arrows indicate the signaling path from the UE through the N3IWF to the UPF, and the return path. + +Figure 8.2.4-3: Control Plane for establishment of user-plane via N3IWF + +In the above figures 8.2.4-1, 8.2.4-2 and 8.2.4-3, the UDP protocol may be used between the UE and N3IWF to enable NAT traversal for IKEv2 and IPsec traffic. + +The "signalling IPsec SA" is defined in clause 4.12.2 of TS 23.502 [3]. + +### 8.2.5 Control Plane for trusted non-3GPP Access + +![Diagram showing the control plane before the NWt connection is established between UE and TNGF. The UE is shown at the top, with a TNGF below it. A large black bar at the bottom represents the 3GPP network. Arrows show traffic from the UE, through the TNGF, into the 3GPP network.](f324fbc5d5af1e4da9cd932389f0064c_img.jpg) + +Diagram showing the control plane before the NWt connection is established between UE and TNGF. The UE is shown at the top, with a TNGF below it. A large black bar at the bottom represents the 3GPP network. Arrows show traffic from the UE, through the TNGF, into the 3GPP network. + +Figure 8.2.5-1: Control Plane before the NWt connection is established between UE and TNGF + +![Diagram showing the control plane after the NWt connection is established between UE and TNGF. Similar to the previous diagram, but now there is a direct bidirectional arrow between the UE and the TNGF, indicating an established connection.](e4a14961bdc9882e296b25f7ae5f9760_img.jpg) + +Diagram showing the control plane after the NWt connection is established between UE and TNGF. Similar to the previous diagram, but now there is a direct bidirectional arrow between the UE and the TNGF, indicating an established connection. + +Figure 8.2.5-2: Control Plane after the NWt connection is established between UE and TNGF + +Large NAS messages may be fragmented by the "inner IP" layer or by TCP. + +![Figure 8.2.5-3: Control Plane for establishment of user-plane via TNGF. The diagram shows a protocol stack with a black base. Above it, there are two sets of boxes representing protocol layers. The left set has two boxes, with the top one having a double-headed arrow pointing to the right. The right set also has two boxes, with the top one having a double-headed arrow pointing to the left. A dashed vertical line separates the two sets of boxes.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +Figure 8.2.5-3: Control Plane for establishment of user-plane via TNGF. The diagram shows a protocol stack with a black base. Above it, there are two sets of boxes representing protocol layers. The left set has two boxes, with the top one having a double-headed arrow pointing to the right. The right set also has two boxes, with the top one having a double-headed arrow pointing to the left. A dashed vertical line separates the two sets of boxes. + +**Figure 8.2.5-3: Control Plane for establishment of user-plane via TNGF** + +In the above figures 8.2.5-2 and 8.2.5-3, the UDP protocol may be used between the UE and TNGF to enable NAT traversal for IKEv2 and IPsec traffic. + +The NWt connection is defined in clause 4.2.8.3 and in clause 4.12a.2.2 of TS 23.502 [3]. + +### 8.2.6 Control Plane for W-5GAN Access + +The control plane for W-5GAN is defined in clause 6 of TS 23.316 [84]. + +### 8.2.7 Control Plane for Trusted WLAN Access for N5CW Device + +![Figure 8.2.7-1: Control Plane for trusted WLAN access for N5CW device. The diagram shows a sequence of protocol stacks and interfaces. From left to right: 1. N5CW Device with EAP and Non-3GPP layers, connected via Yt' to 2. TWAP (Non-3GPP Relay, AAA, Lower layers). 3. Yw interface connects TWAP to 4. TWIF (AAA, NAS, N2, Stack). 5. N2 interface connects TWIF to 6. AMF (NAS, N2, Stack). 7. N12 interface connects AMF to 8. AUSF (EAP, N12, Stack).](b54ce9bffd341cd643e196d5f4538829_img.jpg) + +Figure 8.2.7-1: Control Plane for trusted WLAN access for N5CW device. The diagram shows a sequence of protocol stacks and interfaces. From left to right: 1. N5CW Device with EAP and Non-3GPP layers, connected via Yt' to 2. TWAP (Non-3GPP Relay, AAA, Lower layers). 3. Yw interface connects TWAP to 4. TWIF (AAA, NAS, N2, Stack). 5. N2 interface connects TWIF to 6. AMF (NAS, N2, Stack). 7. N12 interface connects AMF to 8. AUSF (EAP, N12, Stack). + +**Figure 8.2.7-1: Control Plane for trusted WLAN access for N5CW device** + +The EAP protocol applies only for performing EAP-based access authentication procedure to connect to a trusted WLAN access network. + +## 8.3 User Plane Protocol Stacks + +### 8.3.1 User Plane Protocol Stack for a PDU Session + +This clause illustrates the protocol stack for the User plane transport related with a PDU Session. + +![Figure 8.3.1-1: User Plane Protocol Stack. The diagram illustrates the protocol stack for user plane data across different network elements. On the left, the UE (User Equipment) stack consists of Application, PDU Layer, and 5G-AN Protocol Layers. The 5G-AN (5G Access Network) stack includes a Relay block, 5G-AN Protocol Layers, GTP-U, UDP/IP, L2, and L1. The UPF (User Plane Function) stack, shown with dashed lines, includes a Relay block, GTP-U, UDP/IP, L2, and L1. The UPF is further divided into a 'non PDU Session Anchor' UPF and a 'PDU Session Anchor' UPF. The interfaces N3, N9, and N6 are indicated by vertical dashed lines. The PDU Session Anchor UPF stack consists of PDU Layer, GTP-U, UDP/IP, L2, and L1.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Figure 8.3.1-1: User Plane Protocol Stack. The diagram illustrates the protocol stack for user plane data across different network elements. On the left, the UE (User Equipment) stack consists of Application, PDU Layer, and 5G-AN Protocol Layers. The 5G-AN (5G Access Network) stack includes a Relay block, 5G-AN Protocol Layers, GTP-U, UDP/IP, L2, and L1. The UPF (User Plane Function) stack, shown with dashed lines, includes a Relay block, GTP-U, UDP/IP, L2, and L1. The UPF is further divided into a 'non PDU Session Anchor' UPF and a 'PDU Session Anchor' UPF. The interfaces N3, N9, and N6 are indicated by vertical dashed lines. The PDU Session Anchor UPF stack consists of PDU Layer, GTP-U, UDP/IP, L2, and L1. + +##### Legend: + +- **PDU layer:** This layer corresponds to the PDU carried between the UE and the DN over the PDU Session. When the PDU Session Type is IPv4 or IPv6 or IPv4v6, it corresponds to IPv4 packets or IPv6 packets or both of them; When the PDU Session Type is Ethernet, it corresponds to Ethernet frames; etc. +- **GPRS Tunnelling Protocol for the user plane (GTP-U):** This protocol supports tunnelling user data over N3 (i.e. between the 5G-AN node and the UPF) and N9 (i.e. between different UPFs of the 5GC) in the backbone network, details see TS 29.281 [75]. GTP shall encapsulate all end user PDUs. It provides encapsulation on a per PDU Session level. This layer carries also the marking associated with a QoS Flow defined in clause 5.7. This protocol is also used on N4 interface as defined in TS 29.244 [65]. + +**Figure 8.3.1-1: User Plane Protocol Stack** + +- **5G-AN protocol stack:** This set of protocols/layers depends on the AN: + - When the 5G-AN is a 3GPP NG-RAN, these protocols/layers are defined in TS 38.401 [42]. The radio protocol between the UE and the 5G-AN node (eNodeB or gNodeB) is specified in TS 36.300 [30] and TS 38.300 [27]. + - When the AN is an Untrusted non 3GPP access to 5GC the 5G-AN interfaces with the 5GC at a N3IWF defined in clause 4.3.2 and the 5G-AN protocol stack is defined in clause 8.3.2. +- **UDP/IP:** These are the backbone network protocols. + +NOTE 1: The number of UPF in the data path is not constrained by 3GPP specifications: there may be in the data path of a PDU Session 0, 1 or multiple UPF that do not support a PDU Session Anchor functionality for this PDU Session. + +NOTE 2: The "non PDU Session Anchor" UPF depicted in the Figure 8.3.1-1 is optional. + +NOTE 3: The N9 interface may be intra-PLMN or inter PLMN (in the case of Home Routed deployment). + +If there is an UL CL (Uplink Classifier) or a Branching Point (both defined in clause 5.6.4) in the data path of a PDU Session, the UL CL or Branching Point acts as the non PDU Session Anchor UPF of Figure 8.3.1-1. In that case there are multiple N9 interfaces branching out of the UL CL / Branching Point each leading to different PDU Session anchors. + +NOTE 4: Co-location of the UL CL or Branching Point with a PDU Session Anchor is a deployment option. + +### 8.3.2 User Plane for untrusted non-3GPP Access + +![Diagram illustrating the User Plane for untrusted non-3GPP Access via N3IWF. It shows four main components: a UE (User Equipment) on the left, an N3IWF (N3 Interface Function) in the center-left, a UPF (UPF) in the center-right, and a DN (Data Network) on the far right. The UE is represented by two stacked rectangles. The N3IWF is represented by two stacked rectangles with a tall vertical rectangle to its right. The UPF is represented by two stacked rectangles. The DN is represented by a single tall vertical rectangle. Arrows indicate the flow of data from the UE, through the N3IWF, then through the UPF, and finally into the DN.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +Diagram illustrating the User Plane for untrusted non-3GPP Access via N3IWF. It shows four main components: a UE (User Equipment) on the left, an N3IWF (N3 Interface Function) in the center-left, a UPF (UPF) in the center-right, and a DN (Data Network) on the far right. The UE is represented by two stacked rectangles. The N3IWF is represented by two stacked rectangles with a tall vertical rectangle to its right. The UPF is represented by two stacked rectangles. The DN is represented by a single tall vertical rectangle. Arrows indicate the flow of data from the UE, through the N3IWF, then through the UPF, and finally into the DN. + +Figure 8.3.2-1: User Plane via N3IWF + +Large GRE packets may be fragmented by the "inner IP" layer. + +Details about the PDU Layer, the N3 stack and the N9 stack are included in clause 8.3.1. The UDP protocol may be used below the IPsec layer to enable NAT traversal. + +### 8.3.3 User Plane for trusted non-3GPP Access + +![Diagram illustrating the User Plane for trusted non-3GPP Access via TNGF. It shows four main components: a UE (User Equipment) on the left, a TNGF (Trusted Non-3GPP Gateway) in the center-left, a UPF (UPF) in the center-right, and a DN (Data Network) on the far right. The UE is represented by two stacked rectangles. The TNGF is represented by two stacked rectangles with a tall vertical rectangle to its right. The UPF is represented by two stacked rectangles. The DN is represented by a single tall vertical rectangle. Below the UE, TNGF, and UPF is a thick black horizontal bar representing the trusted non-3GPP access network. Arrows indicate the flow of data from the UE, through the TNGF, then through the UPF, and finally into the DN, with the data passing through the thick black bar.](c85b57b2414f341860dfc338e1cf2509_img.jpg) + +Diagram illustrating the User Plane for trusted non-3GPP Access via TNGF. It shows four main components: a UE (User Equipment) on the left, a TNGF (Trusted Non-3GPP Gateway) in the center-left, a UPF (UPF) in the center-right, and a DN (Data Network) on the far right. The UE is represented by two stacked rectangles. The TNGF is represented by two stacked rectangles with a tall vertical rectangle to its right. The UPF is represented by two stacked rectangles. The DN is represented by a single tall vertical rectangle. Below the UE, TNGF, and UPF is a thick black horizontal bar representing the trusted non-3GPP access network. Arrows indicate the flow of data from the UE, through the TNGF, then through the UPF, and finally into the DN, with the data passing through the thick black bar. + +Figure 8.3.2-1: User Plane via TNGF + +Large GRE packets may be fragmented by the "inner IP" layer. + +Details about the PDU Layer, the N3 stack and the N9 stack are included in clause 8.3.1. The UDP protocol may be used below the IPsec layer to enable NAT traversal. + +### 8.3.4 User Plane for W-5GAN Access + +The user plane for W-5GAN is defined in clause 6 of TS 23.316 [84]. + +### 8.3.5 User Plane for N19-based forwarding of a 5G VN group + +![Diagram of User Plane for N19-based forwarding of a 5G VN group. It shows two User Equipment (UE) units, UE 1 and UE 2, connected via a central network path. UE 1 is connected to UPF 1 (PDU Session Anchor) through 'PDU Session 1'. UE 2 is connected to UPF 2 (PDU Session Anchor) through 'PDU Session 2'. UPF 1 and UPF 2 are interconnected via the 'N19' interface. Each UE contains an 'Application' block and a 'PDU Session User Plane Protocol Stack'. The stacks in the UEs consist of PDU Session, User Plane, and Protocol layers. The UPFs contain 'Relay' blocks with their own protocol stacks: PDU Layer, GTP-U, UDP/IP, L2, and L1. Arrows indicate the flow of data from the applications in the UEs, through their respective stacks, into the UPFs, across the N19 interface, and back out to the applications in the other UE.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +Diagram of User Plane for N19-based forwarding of a 5G VN group. It shows two User Equipment (UE) units, UE 1 and UE 2, connected via a central network path. UE 1 is connected to UPF 1 (PDU Session Anchor) through 'PDU Session 1'. UE 2 is connected to UPF 2 (PDU Session Anchor) through 'PDU Session 2'. UPF 1 and UPF 2 are interconnected via the 'N19' interface. Each UE contains an 'Application' block and a 'PDU Session User Plane Protocol Stack'. The stacks in the UEs consist of PDU Session, User Plane, and Protocol layers. The UPFs contain 'Relay' blocks with their own protocol stacks: PDU Layer, GTP-U, UDP/IP, L2, and L1. Arrows indicate the flow of data from the applications in the UEs, through their respective stacks, into the UPFs, across the N19 interface, and back out to the applications in the other UE. + +Figure 8.3.5-1: User Plane for N19-based forwarding + +Details about the PDU Layer, PDU Session User Plane Protocol Stack are included in clause 8.3.1 and clause 8.3.2. The N19 is based on a shared User Plane tunnel connecting two PSA UPFs of a single 5G VN group. + +### 8.3.6 User Plane for Trusted WLAN Access for N5CW Device + +![Diagram of User Plane for Trusted WLAN Access for N5CW Device. It shows an N5CW Device on the left connected to a TWAP (Trusted WLAN Access Point). The TWAP is connected to a TWIF (Trusted WLAN Interconnect). The TWIF is connected to a UPF (PDG Session Anchor) via the N3 interface. The UPF is connected to the N6 interface. The diagram illustrates the protocol stacks at each entity. The N5CW Device has Application, PDU Layer, Transport, and Non-3GPP (WLAN) layers. The TWAP has Transport, Non-3GPP (WLAN), and Lower layers. The TWIF has Transport, Relay N3 Stack, and Lower layers. The UPF has N3 Stack, Relay N9 Stack, and PDU Layer. The N6 interface is shown as a continuation of the PDU Layer. Interfaces are labeled Yt', Yw, N3, N9, and N6.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +Diagram of User Plane for Trusted WLAN Access for N5CW Device. It shows an N5CW Device on the left connected to a TWAP (Trusted WLAN Access Point). The TWAP is connected to a TWIF (Trusted WLAN Interconnect). The TWIF is connected to a UPF (PDG Session Anchor) via the N3 interface. The UPF is connected to the N6 interface. The diagram illustrates the protocol stacks at each entity. The N5CW Device has Application, PDU Layer, Transport, and Non-3GPP (WLAN) layers. The TWAP has Transport, Non-3GPP (WLAN), and Lower layers. The TWIF has Transport, Relay N3 Stack, and Lower layers. The UPF has N3 Stack, Relay N9 Stack, and PDU Layer. The N6 interface is shown as a continuation of the PDU Layer. Interfaces are labeled Yt', Yw, N3, N9, and N6. + +##### **Legend:** + +- Transport: this layer refers to the transport of PDUs between the N5CW device and TWIF (see clause 4.2.8.5.4). +In this Release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type. + +Figure 8.2.8-1: User Plane for trusted WLAN access for N5CW device + +# Annex A (informative): Relationship between Service-Based Interfaces and Reference Points + +Service-Based Interfaces and Reference Points are two different ways to model interactions between architectural entities. A Reference Point is a conceptual point at the conjunction of two non-overlapping functional groups (see TR 21.905 [1]). In figure A-1 the functional groups are equivalent to Network Functions. + +A reference point can be replaced by one or more service-based interfaces which provide equivalent functionality. + +![Figure A-1: Example showing a Reference Point replaced by two Service based Interfaces. The diagram consists of two parts. The top part shows two boxes, NFA and NFB, connected by a line labeled RP1. The bottom part shows the same two boxes, NFA and NFB, connected by two lines: one labeled Nnfb from NFA to NFB, and another labeled Nnfa from NFB to NFA. A large bracket groups the two parts, indicating a replacement relationship.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +Figure A-1: Example showing a Reference Point replaced by two Service based Interfaces. The diagram consists of two parts. The top part shows two boxes, NFA and NFB, connected by a line labeled RP1. The bottom part shows the same two boxes, NFA and NFB, connected by two lines: one labeled Nnfb from NFA to NFB, and another labeled Nnfa from NFB to NFA. A large bracket groups the two parts, indicating a replacement relationship. + +**Figure A-1: Example show a Reference Point replaced by two Service based Interfaces** + +![Figure A-2: Example showing a Reference Point replaced by a single Service based Interface. The diagram consists of two parts. The top part shows two boxes, NFA and NFB, connected by a line labeled RP1. The bottom part shows the same two boxes, NFA and NFB, connected by a single line labeled Nnfb from NFA to NFB. A large bracket groups the two parts, indicating a replacement relationship.](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +Figure A-2: Example showing a Reference Point replaced by a single Service based Interface. The diagram consists of two parts. The top part shows two boxes, NFA and NFB, connected by a line labeled RP1. The bottom part shows the same two boxes, NFA and NFB, connected by a single line labeled Nnfb from NFA to NFB. A large bracket groups the two parts, indicating a replacement relationship. + +**Figure A-2: Example showing a Reference Point replaced by a single Service based Interface** + +Reference points exist between two specific Network Functions. Even if the functionality is equal on two reference points between different Network Functions there has to be a different reference point name. Using the service-based interface representation it is immediately visible that it is the same service-based interface and that the functionality is equal on each interface. + +![Figure A-3: Reference Points vs. Service-based Interfaces representation of equal functionality on the interfaces. The diagram consists of two parts. The top part shows a box NFA connected to two boxes, NFB and NFC, via lines labeled RP1 and RP2 respectively. The bottom part shows the same box NFA connected to the same two boxes, NFB and NFC, via lines labeled Nnfa. A large bracket groups the two parts, indicating that the different reference point names (RP1, RP2) correspond to the same service-based interface (Nnfa).](187bba66c887c745c512add37a577c5e_img.jpg) + +Figure A-3: Reference Points vs. Service-based Interfaces representation of equal functionality on the interfaces. The diagram consists of two parts. The top part shows a box NFA connected to two boxes, NFB and NFC, via lines labeled RP1 and RP2 respectively. The bottom part shows the same box NFA connected to the same two boxes, NFB and NFC, via lines labeled Nnfa. A large bracket groups the two parts, indicating that the different reference point names (RP1, RP2) correspond to the same service-based interface (Nnfa). + +**Figure A-3: Reference Points vs. Service-based Interfaces representation of equal functionality on the interfaces** + +A NF may expose one or more services through Service based interfaces. + +![Diagram showing NFA connected to NFB via four service interfaces: Nnfa_serv1, Nnfb_serv1, Nnfa_serv2, and Nnfb_serv2.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +The diagram illustrates a Network Function (NFA) on the left connected to another Network Function (NFB) on the right. Four horizontal lines represent service interfaces between them. From top to bottom, the labels are: Nnfa\_serv1, Nnfb\_serv1, Nnfa\_serv2, and Nnfb\_serv2. Each line has a small circle at its connection point to the NFA and another at its connection point to the NFB. + +Diagram showing NFA connected to NFB via four service interfaces: Nnfa\_serv1, Nnfb\_serv1, Nnfa\_serv2, and Nnfb\_serv2. + +Figure A-4: One or more Services exposed by one Network Function + +# --- Annex B (normative): Mapping between temporary identities + +When interworking procedures with N26 are used and the UE performs idle mode mobility from 5GC to EPC the following mapping from 5G GUTI to EPS GUTI applies: + +- 5G maps to EPS +- 5G maps to EPS +- 5G and 5G maps to EPS and part of EPS +- 5G map to part of EPS +- 5G <5G-TMSI> maps to EPS + +NOTE 1: The mapping described above does not necessarily imply the same size for the 5G GUTI and EPS GUTI fields that are mapped. The size of 5G GUTI fields and other mapping details will be defined in TS 23.003 [19]. + +NOTE 2: To support interworking with the legacy EPC core network entity (i.e. when MME is not updated to support interworking with 5GS), it is assumed that the 5G and EPS is partitioned to avoid overlapping values in order to enable discovery of source node (i.e. MME or AMF) without ambiguity. Once the EPS in the PLMN has been updated to support interworking with 5GS, the full address space of the AMF Region ID can be used for 5GS. + +# --- Annex C (informative): Guidelines and Principles for Compute-Storage Separation + +5G System Architecture allows any NF/NF Service to store and retrieve its unstructured data (e.g. UE contexts) into/from a Storage entity (e.g. UDSF) as stated in clause 4.2.5 in this release of the specification. This clause highlights some assumptions, principles regarding NF/NF services that use this Storage entity for storing unstructured data: + +1. It is up to the Network Function implementation to determine whether the Storage entity is used as a Primary Storage (in which case the corresponding context stored within the NF/NF Service is deleted after storage in the Storage entity) or the Storage entity is used as a Secondary Storage (in which case the corresponding context within the NF/NF Service is stored). +2. It is up to the NF/NF Service implementation to determine the trigger (e.g. at the end of Registration procedure, Service Request procedure etc) for storing unstructured data (e.g. UE contexts) in the Storage entity but it is a good practice for NF/NF service to store stable state in the Storage entity. +3. Multiple NF/NF service instances may require to access the same stored data in the Storage entity (e.g. UE context), around the same time, then the resolution the race condition is implementation specific. +4. All NFs within the same NF Set are assumed to have access to the same unstructured data stored within the Storage entity. +5. AMF planned removal with UDSF (clause 5.21.2.2.1) and AMF auto-recovery (with UDSF option in clause 5.21.2.3) assume that a storage entity/UDSF is used either as a primary storage or secondary storage by the AMF for storing UE contexts. +6. It is up to implementation of the Storage entity to make sure that only NFs that are authorized for a certain data record can access this data record. + +# --- Annex D (informative): 5GS support for Non-Public Network deployment options + +## D.1 Introduction + +This annex provides guidance on how 5GS features and capabilities can be used to support various Non-Public Network deployment options. + +**Overlay network:** When UE is accessing SNPN service via NWu using user plane established in PLMN, SNPN is the overlay network. When UE is accessing PLMN services via NWu using user plane established in SNPN, PLMN is the overlay network. + +**Underlay network:** When UE is accessing SNPN service via NWu using user plane established in PLMN, PLMN is the underlay network. When UE is accessing PLMN services via NWu using user plane established in SNPN, SNPN is the underlay network. + +## --- D.2 Support of Non-Public Network as a network slice of a PLMN + +The PLMN operator can provide access to an NPN by using network slicing mechanisms. + +NOTE: Access to PLMN services can be supported in addition to PNI-NPN services, e.g. based on different S-NSSAI/DNN for different services. + +The following are some considerations in such a PNI-NPN case: + +1. The UE has subscription and credentials for the PLMN; +2. The PLMN and NPN service provider have an agreement of where the NPN Network Slice is to be deployed (i.e. in which TAs of the PLMN and optionally including support for roaming PLMNs); +3. The PLMN subscription includes support for Subscribed S-NSSAI to be used for the NPN (see clause 5.15.3); +4. The PLMN operator can offer possibilities for the NPN service provider to manage the NPN Network Slice according to TS 28.533 [79]. +5. When the UE registers the first time to the PLMN, the PLMN can configure the UE with URSP including NSSP associating Applications to the NPN S-NSSAI (if the UE also is able to access other PLMN services); +6. The PLMN can configure the UE with Configured NSSAI for the Serving PLMN (see clause 5.15.4); +7. The PLMN and NPN can perform a Network Slice specific authentication and authorization using additional NPN credentials; +8. The UE follows the logic as defined for Network Slicing, see clause 5.15; +9. The network selection logic, access control etc are following the principles for PLMN selection; and +10. The PLMN may indicate to the UE that the NPN S-NSSAI is rejected for the RA when the UE moves out of the coverage of the NPN Network Slice. However, limiting the availability of the NPN S-NSSAI would imply that the NPN is not available outside of the area agreed for the NPN S-NSSAI, e.g. resulting in the NPN PDU Sessions being terminated when the UE moves out of the coverage of the NPN Network Slice. Similarly access to NPN DNNs would not be available via non-NPN cells. +11. In order to prevent access to NPNs for authorized UE(s) in the case of network congestion/overload and if a dedicated S-NSSAI has been allocated for an NPN, the Unified Access Control can be used using the operator-defined access categories with access category criteria type (as defined in TS 24.501 [47]) set to the S-NSSAI used for an NPN. +12. If NPN isolation is desired, it is assumed that a dedicated S-NSSAI is configured for the NPN and that the UE is configured to operate in Access Stratum Connection Establishment NSSAI Inclusion Mode a, b or c, see + +clause 5.15.9, such that NG-RAN receives Requested NSSAI from the UE and it can use the S-NSSAI for AMF selection. + +## D.3 Support for access to PLMN services via Stand-alone Non-Public Network and access to Stand-alone Non Public Network services via PLMN + +![Figure D.3-1: Access to PLMN services via Stand-alone Non-Public Network. The diagram shows a UE connected to an NPN 3GPP Access, which is part of an SNPN CN. The UE has an N1 for NPN connection to the AMF and an N2 connection to the NG-RAN. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to a DN via N6. The UE also has an N3 connection to the UPF and an NWu for PLMN connection to the N3IWF. The N3IWF is connected to the AMF via N1 for PLMN and to the UPF via N3. The AMF is connected to the SMF via N11. The SMF is connected to the UPF via N4. The UPF is connected to the DN via N6. The PLMN CN contains the AMF, SMF, UPF, and N3IWF. The SNPN CN contains the AMF, SMF, and UPF. The UE is connected to the NPN 3GPP Access, which is connected to the AMF in the SNPN CN. The UE also has a connection to the N3IWF in the PLMN CN via the NWu for PLMN interface. The N3IWF is connected to the AMF in the PLMN CN via the N1 for PLMN interface. The AMF in the PLMN CN is connected to the SMF via the N11 interface. The SMF is connected to the UPF via the N4 interface. The UPF is connected to the DN via the N6 interface. The AMF in the SNPN CN is connected to the SMF via the N11 interface. The SMF is connected to the UPF via the N4 interface. The UPF is connected to the DN via the N6 interface. The UE has an N1 for NPN connection to the AMF in the SNPN CN. The UE has an N2 connection to the NG-RAN in the SNPN CN. The UE has an N3 connection to the UPF in the SNPN CN. The UE has an NWu for PLMN connection to the N3IWF in the PLMN CN.](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +Figure D.3-1: Access to PLMN services via Stand-alone Non-Public Network. The diagram shows a UE connected to an NPN 3GPP Access, which is part of an SNPN CN. The UE has an N1 for NPN connection to the AMF and an N2 connection to the NG-RAN. The AMF is connected to an SMF via N11. The SMF is connected to a UPF via N4. The UPF is connected to a DN via N6. The UE also has an N3 connection to the UPF and an NWu for PLMN connection to the N3IWF. The N3IWF is connected to the AMF via N1 for PLMN and to the UPF via N3. The AMF is connected to the SMF via N11. The SMF is connected to the UPF via N4. The UPF is connected to the DN via N6. The PLMN CN contains the AMF, SMF, UPF, and N3IWF. The SNPN CN contains the AMF, SMF, and UPF. The UE is connected to the NPN 3GPP Access, which is connected to the AMF in the SNPN CN. The UE also has a connection to the N3IWF in the PLMN CN via the NWu for PLMN interface. The N3IWF is connected to the AMF in the PLMN CN via the N1 for PLMN interface. The AMF in the PLMN CN is connected to the SMF via the N11 interface. The SMF is connected to the UPF via the N4 interface. The UPF is connected to the DN via the N6 interface. The AMF in the SNPN CN is connected to the SMF via the N11 interface. The SMF is connected to the UPF via the N4 interface. The UPF is connected to the DN via the N6 interface. The UE has an N1 for NPN connection to the AMF in the SNPN CN. The UE has an N2 connection to the NG-RAN in the SNPN CN. The UE has an N3 connection to the UPF in the SNPN CN. The UE has an NWu for PLMN connection to the N3IWF in the PLMN CN. + +**Figure D.3-1: Access to PLMN services via Stand-alone Non-Public Network** + +NOTE 1: The reference architecture in Figure D.3-1 and Figure D.3-2 only shows the network functions directly connected to the UPF or N3IWF and other parts of the architecture are same as defined in clause 4.2. + +In order to obtain access to PLMN services when the UE is camping in NG-RAN of Stand-alone Non-Public Network, the UE obtains IP connectivity, discovers and establishes connectivity to an N3IWF in the PLMN. + +In the Figure D.3-1, the N1 (for NPN) represents the reference point between UE and the AMF in Stand-alone Non-Public Network. The NWu (for PLMN) represents the reference point between the UE and the N3IWF in the PLMN for establishing secure tunnel between UE and the N3IWF over the Stand-alone Non-Public Network. N1 (for PLMN) represents the reference point between UE and the AMF in PLMN. + +![Figure D.3-2: Access to Stand-alone Non-Public Network services via PLMN. The diagram shows a UE connected to a PLMN CN and an SNPN CN. The PLMN CN contains an AMF, SMF, and UPF. The SNPN CN contains an AMF, SMF, N3IWF, and UPF. The UE is connected to the PLMN CN via N1 (for PLMN) and N2. The UE is also connected to the SNPN CN via NWu (for NPN) and N1 (for NPN). The PLMN CN is connected to the SNPN CN via N3 and N6. The SNPN CN is connected to a DN (Data Network).](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram illustrates the network architecture for accessing Stand-alone Non-Public Network (SNPN) services via a Public Land Mobile Network (PLMN). On the left, a User Equipment (UE) is shown. It has a solid line connection labeled 'N1 for PLMN' to an AMF in the 'PLMN CN' (dashed oval) and a dashed line connection labeled 'NWu for NPN' to an N3IWF in the 'SNPN CN' (dashed oval). The UE also has a solid line connection labeled 'N2' to the AMF. The AMF in the PLMN CN is connected to an SMF via 'N11' and to the N3IWF via 'N3'. The SMF is connected to a UPF via 'N4'. The UPF is connected to a DN (Data Network) via 'N6'. The N3IWF in the SNPN CN is connected to an AMF in the SNPN CN via 'N1 for NPN' and to a UPF via 'N3'. The AMF in the SNPN CN is connected to an SMF via 'N11', which is connected to the UPF via 'N4'. The UPF in the SNPN CN is also connected to the DN via 'N6'. A circle labeled 'PLMN 3GPP Access' is shown between the UE and the PLMN CN. + +Figure D.3-2: Access to Stand-alone Non-Public Network services via PLMN. The diagram shows a UE connected to a PLMN CN and an SNPN CN. The PLMN CN contains an AMF, SMF, and UPF. The SNPN CN contains an AMF, SMF, N3IWF, and UPF. The UE is connected to the PLMN CN via N1 (for PLMN) and N2. The UE is also connected to the SNPN CN via NWu (for NPN) and N1 (for NPN). The PLMN CN is connected to the SNPN CN via N3 and N6. The SNPN CN is connected to a DN (Data Network). + +**Figure D.3-2: Access to Stand-alone Non-Public Network services via PLMN** + +In order to obtain access to Non-Public Network services when the UE is camping in NG-RAN of a PLMN, the UE obtains IP connectivity, discovers and establishes connectivity to an N3IWF in the Stand-alone Non-Public Network. + +In Figure D.3-2, the N1 (for PLMN) represents the reference point between UE and the AMF in the PLMN. The NWu (for NPN) represents the reference point between the UE and the N3IWF in the stand-alone Non-Public Network for establishing a secure tunnel between UE and the N3IWF over the PLMN. The N1 (for NPN) represents the reference point between UE and the AMF in NPN. + +When using the mechanism described above to access overlay network via underlay network, the overlay network can act as authorized 3rd party with AF to interact with NEF in the underlay network, to use the existing network exposure capabilities provided by the underlay network defined in clause 4.15 of TS 23.502 [3]. This interaction is subject of agreements between the overlay and the underlay network. + +## D.4 Support for UE capable of simultaneously connecting to an SNPN and a PLMN + +When a UE capable of simultaneously connecting to an SNPN and a PLMN and the UE is not set to operate in SNPN access mode for any of the Uu/Yt/NWu interfaces, the UE only performs PLMN selection procedures using the corresponding interface for connection to the PLMN. + +A UE supporting simultaneous connectivity to an SNPN and a PLMN applies the network selection as applicable for the access and network for SNPN and PLMN respectively. Whether the UE uses SNPN or PLMN for its services is implementation dependent. + +A UE supporting simultaneous connectivity to an SNPN and a PLMN applies the cell (re-)selection as applicable for the access and network for SNPN and PLMN respectively. Whether the UE uses SNPN or PLMN for its services is implementation dependent. + +## D.5 Support for keeping UE in CM-CONNECTED state in overlay network when accessing services via NWu + +When UE is accessing the overlay network via the underlay network as described in clause D.3, it is possible to keep the UE in CM-CONNECTED state in the overlay network: + +- UE maintains at least one PDU Session in underlay network, from where the N3IWF of the overlay network is reachable via the DN of the PDU Session in underlay network. In this case, the UE is considered as successfully connected to the non-3GPP access of the overlay network, thus UE always attempts to transit to CM-CONNECTED state from CM-IDLE, as described in NOTE 3 in clause 5.5.2. +- IKEv2 liveness check procedure initiated either by UE or N3IWF as defined in clause 7.8 and clause 7.9 of TS 24.502 [48] can be utilized to ensure the signalling connection between UE and N3IWF is still valid when UE stays in CM-CONNECTED state. Adjusting the time interval of the liveness check to avoid the deletion of the IKEv2 SA due to inactivity, on both endpoints of the SA. +- If NAT is used, so as to avoid a timeout of the NAT entries between the UPF in the underlay network and the N3IWF in the overlay network, NAT-Traversal mechanisms described in RFC 7296 [60] and NAT-Keepalive described in RFC 3948 [138] are recommended. +- AMF in overlay network keeps the UE in CM-CONNECTED state unless UE or N3IWF triggers the release. +- The NG-RAN node in the underlay network can use the existing information to decide an appropriate RRC state for the UE (e.g. whether release a UE to RRC\_INACTIVE). + +## --- D.6 Support for session/service continuity between SNPN and PLMN when using N3IWF + +Depending on the UE's radio capability and implementation, the following existing mechanisms can be used to allow session/service continuity between SNPN and PLMN: + +- For Single Radio UE which includes single Rx/Tx and dual Rx/single Tx UE, seamless service continuity is not supported in this release when the UE is moving between the 3GPP access networks of SNPN and PLMN because of the single radio limitation. But the PDU session continuity between SNPN and PLMN can be realized by utilizing the existing handover procedure between non-3GPP access and 3GPP access as defined in clause 4.9.2 of TS 23.502 [3], where one network is acting as non-3GPP access of the other network. +- For Dual Radio (Dual Rx/Dual Tx) UE, the service continuity can be achieved by utilizing the existing handover procedure between non-3GPP access and 3GPP access for PDU session on a single access and the existing user plane resource addition procedure for MA PDU session, where one network is acting as non-3GPP access of the other network +- For PDU session on a single access, UE can register to the same 5GC via both Uu and NWu interfaces from two networks when it is possible, by following the procedure defined in clause 4.2.2 of TS 23.502 [3] if the registration is via Uu, or in clause 4.12.2 of TS 23.502 [3] if the registration is via NWu. The registration via NWu utilizes the user plane which is established in another 5GC using another network's Uu interface. For example, if UE is moving out of its SNPN 3GPP access coverage and would like to continue its SNPN service in PLMN, UE can register to its SNPN 5GC via PLMN's 3GPP access network using NWu interface with SNPN's 5GC before moving out SNPN NG-RAN coverage. Upon mobility, the existing handover procedure between non-3GPP access and 3GPP access defined in clause 4.9.2 of TS 23.502 [3] can be utilized. +- For MA PDU session, if supported by UE and network, UE can register to the same 5GC via Uu and NWu interfaces and establish MA PDU session with ATSSS support to be anchored in the 5GC as defined in clause 4.22.2.2 of TS 23.502 [3], where one network is acting as non-3GPP access of the other network (Figure D.6-1 shows the example of UE with MA PDU session anchored in SNPN UPF when connected to SNPN via Uu and NWu interfaces). Upon mobility, UE can add/activate the user plane resource to the corresponding access type basing on the procedures defined in clause 4.22.7 of TS 23.502 [3]. + +![Diagram of MA PDU session with ATSSS support for dual radio UE accessing to Stand-alone Non-Public Network services via Uu and NWu interfaces. The diagram shows a UE connected to two 3GPP access networks (PLMN and SNPN). The PLMN access connects to a PLMN CN (AMF, SMF, UPF) which is connected to a DN via N6. The SNPN access connects to an SNPN CN (AMF, SMF, UPF) via an N3IWF. The SNPN CN is also connected to a DN via N6. The UE is connected to both the PLMN and SNPN 3GPP access networks. A legend indicates that a thick line represents an MA PDU session.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +The diagram illustrates a User Equipment (UE) connected to two separate 3GPP access networks: PLMN 3GPP access and SNPN 3GPP access. The UE is connected to the PLMN 3GPP access via the Uu interface and to the SNPN 3GPP access via the NWu interface. The PLMN 3GPP access is connected to a PLMN Core Network (CN) containing an AMF, SMF, and UPF. The UPF is connected to a Data Network (DN) via the N6 interface and to the UE via the N3 interface. The SNPN 3GPP access is connected to an SNPN Core Network (CN) containing an AMF, SMF, and UPF, with an N3IWF between the AMF and the UPF. The SNPN UPF is connected to a DN via the N6 interface and to the UE via the N3 interface. A thick line represents the MA PDU session, which is established between the UE and the PLMN UPF, and then between the PLMN UPF and the SNPN UPF via the N3IWF. + +Diagram of MA PDU session with ATSSS support for dual radio UE accessing to Stand-alone Non-Public Network services via Uu and NWu interfaces. The diagram shows a UE connected to two 3GPP access networks (PLMN and SNPN). The PLMN access connects to a PLMN CN (AMF, SMF, UPF) which is connected to a DN via N6. The SNPN access connects to an SNPN CN (AMF, SMF, UPF) via an N3IWF. The SNPN CN is also connected to a DN via N6. The UE is connected to both the PLMN and SNPN 3GPP access networks. A legend indicates that a thick line represents an MA PDU session. + +Figure D.6-1: MA PDU session with ATSSS support for dual radio UE accessing to Stand-alone Non-Public Network services via Uu and NWu interfaces + +## D.7 Guidance for underlay network to support QoS differentiation for User Plane IPsec Child SA + +### D.7.1 Network initiated QoS + +When UE is accessing an overlay network via an underlay network as described in clause D.3, in order to ensure the underlay network to support the QoS required by the overlay network User Plane IPsec Child SA, the QoS differentiation mechanism based on network-initiated QoS modification as described in clause 5.30.2.7 and clause 5.30.2.8 can be used with the following considerations: + +- An overlay network service can have specific QoS requirement that needs to be fulfilled by the underlay network, based on SLA between the two networks. +- The SLA covers selective services of the overlay network which require QoS support in underlay network. The rest of the overlay network traffic could be handled in best efforts basis by underlay network. +- The SLA between the overlay network and the underlay network includes a mapping between DSCP values of the User Plane IPsec Child SAs and the QoS requirement of the overlay network services. The QoS requirement includes the QoS parameters described in clause 5.7.2 that are necessary (e.g. 5QI, ARP, etc.) during the network-initiated QoS modification in underlay network. In order to facilitate the SLA, a guidance for details of the mapping between DSCP values of the User Plane IPSec Child SAs and QoS requirement of the overlay network services is described of TS 29.513 [133]. The SLA also includes the N3IWF IP address of the overlay network. +- The mapping agreed in SLA is configured at N3IWF of the overlay network and at the SMF/PCF of the underlay network. If a dedicated DNN/S-NSSAI is used in the underlay network for providing access to the N3IWF in the overlay network, the SMF/PCF in the underlay network can be configured to enable packet detection (based on N3IWF IP address and DSCP value) for PDU sessions associated with the dedicated DNN/S-NSSAI. + +- When UE establishes a PDU Session in underlay network, the PCF in the underlay network determines PCC rules based on UE subscription information and local configuration which takes into account the SLA described above and installs the PCC rules on the SMF which generates and installs PDR/URR on UPF. The PCC rules indicate N3IWF IP address and the DSCP values of the User Plane IPsec Child SAs of the overlay network which require QoS differentiation by the underlay network. So, the UPF in the underlay network can detect packets of the User Plane IPsec Child SAs corresponding to the overlay network services which require QoS support by the underlay network. +- UE registers and establishes PDU Session in the overlay network via the User Plane connectivity established in the underlay network. When UE is accessing a specific service of overlay network, a QoS Flow can be created by the overlay network, then N3IWF creates dedicated User Plane IPsec Child SA for each overlay network QoS Flow that requires underlay network QoS support. +- N3IWF uses the QoS profile and the Session-AMBR it receives from SMF in overlay network along with the mapping agreed in the SLA to derive a specific DSCP value for the User Plane IPsec Child SA. N3IWF assigns a specific DSCP value only to one User Plane IPsec Child SA for a UE at the same time. UE (for UL) and N3IWF (for DL) will set the DSCP marking in the outer IP header of the User Plane IPsec Child SA accordingly. +- The overlay network traffic between UE and N3IWF using the specific DSCP marking will be detected by the UPF in the underlay network, based on previous installed PDR/URR. The SMF/PCF in underlay network will be informed when the overlay network traffic is detected. Then the PCF installs new PCC rules on the SMF including the QoS parameters for handling of packets corresponding to the specific User Plane IPsec Child SA based on the N3IWF IP address and the DSCP value of the User Plane IPsec Child SA, and the SMF generates a QoS profile that triggers the PDU Session Modification procedure as described in clause 4.3.3 of TS 23.502 [3]. The QoS parameters are derived from the mapping agreed in SLA based on the detected DSCP value. + +### D.7.2 UE initiated QoS + +When UE is accessing an overlay network via an underlay network as described in clause D.3, if UE-initiated QoS modification in clause 5.30.2.7 and clause 5.30.2.8 is used, the following principles can be considered to enable consistent QoS for User Plane IPsec Child SAs between the two networks: + +- UE registers and establishes PDU Session in the overlay network via the User Plane connectivity established in the underlay network. When UE is accessing a specific service of overlay network, a QoS Flow in overlay network can be created according to clause 4.3.3 of TS 23.502 [3]. UE receives the QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR, as specified in TS 24.501 [47]) from SMF/PCF in overlay network for the QoS Flow which is created for the specific overlay network service. +- N3IWF in overlay network creates dedicated User Plane IPsec Child SA for each overlay network QoS Flow that requires underlay network QoS support. +- In order to ensure the traffic of the overlay network service is handled with the desired QoS in underlay network, UE can request new QoS Flow for the PDU session in the underlay network, by PDU Session Modification procedure described in clause 4.3.3 of TS 23.502 [3]. The requested QoS can be derived from the QoS Flow level QoS parameters which the UE has received from the overlay network. The Packet Filter in the QoS rule of the request includes overlay network N3IWF IP address and SPI associated with the User Plane IPsec Child SA. +- SMF in the underlay network notifies the PCF that the UE has initiated resource modification, after receiving the PDU Session Modification Request. PCF in the underlay network determines if the request can be authorized based on UE subscription and local policy which can take into account the SLA between overlay network and underlay network. If the request is authorized, PCF generates new PCC rule and installs on SMF in order to create new QoS Flow in underlay network using the QoS Flow level QoS parameters from the overlay network. The PDR/FAR generated refers to the N3IWF IP address and the SPI (provided by the UE in Traffic filter in PDU Session Modification request) to enable filtering and mapping of DL traffic towards the right PDU Session/QoS Flow within the underlay network. +- If SLA exists, it can include a mapping between the DSCP values of the User Plane IPsec Child SAs and the QoS requirement of the overlay network services. The SLA is configured at N3IWF in overlay network and at SMF/PCF in underlay network. N3IWF can provide DSCP value to UE for the User Plane IPsec Child SA at PDU Session Establishment (clause 4.12.5, step 4a and 4c of TS 23.502 [3]). UE can include the DSCP value as an addition in the Packet Filter by initiating the PDU Session Modification procedure in the underlay network. PCF in the underlay network performs QoS authorization of UE QoS request considering the UE subscription and local configuration which takes into account the mapping in the SLA. Details of the mapping between DSCP + +values of the User Plane IPSec Child SAs and QoS requirement of the overlay network services is described in TS 29.513 [133]. + +# Annex E (informative): Communication models for NF/NF services interaction + +## E.1 General + +This annex provides a high level description of the different communication models that NF and NF services can use to interact with each other. Table E.1-1 summarizes the communication models, their usage and how they relate to the usage of an SCP. + +**Table E.1-1: Communication models for NF/NF services interaction summary** + +| Communication between consumer and producer | Service discovery and request routing | Communication model | +|---------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|---------------------| +| Direct communication | No NRF or SCP; direct routing | A | +| | Discovery using NRF services; no SCP; direct routing | B | +| Indirect communication | Discovery using NRF services; selection for specific instance from the Set can be delegated to SCP. Routing via SCP | C | +| | Discovery and associated selection delegated to an SCP using discovery and selection parameters in service request; routing via SCP | D | + +**Model A - Direct communication without NRF interaction:** Neither NRF nor SCP are used. Consumers are configured with producers' "NF profiles" and directly communicate with a producer of their choice. + +**Model B - Direct communication with NRF interaction:** Consumers do discovery by querying the NRF. Based on the discovery result, the consumer does the selection. The consumer sends the request to the selected producer. + +**Model C - Indirect communication without delegated discovery:** Consumers do discovery by querying the NRF. Based on discovery result, the consumer does the selection of an NF Set or a specific NF instance of NF set. The consumer sends the request to the SCP containing the address of the selected service producer pointing to a NF service instance or a set of NF service instances. In the latter case, the SCP selects an NF Service instance. If possible, the SCP interacts with NRF to get selection parameters such as location, capacity, etc. The SCP routes the request to the selected NF service producer instance. + +**Model D - Indirect communication with delegated discovery:** Consumers do not do any discovery or selection. The consumer adds any necessary discovery and selection parameters required to find a suitable producer to the service request. The SCP uses the request address and the discovery and selection parameters in the request message to route the request to a suitable producer instance. The SCP can perform discovery with an NRF and obtain a discovery result. + +Figure E.1-1 depicts the different communication models. + +![Four communication models (A, B, C, D) for NF/NF services interaction. Model A shows direct communication between Consumer and Producer. Model B adds NRF discovery. Model C uses SCP for routing with NRF discovery. Model D uses SCP for routing with Service Request + parameters.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram illustrates four communication models for Network Function (NF) services interaction, labeled A, B, C, and D. Each model shows the interaction between a Consumer (C o n s u m e r) and a Producer (P r o d u c e r). + +- Model A:** The Consumer sends a Service Request to the Producer, which responds with a Service Response. Subsequent requests are also sent directly to the Producer. +- Model B:** The Consumer first sends a Discovery request to the NRF (Network Repository Function), which returns NF profile(s). Then, the Consumer sends a Service Request to the Producer, which responds with a Service Response. Subsequent requests are sent directly to the Producer. +- Model C:** The Consumer sends a Discovery request to the NRF, which returns NF profile(s). The Consumer then sends a Service Request to the SCP (Service Communication Proxy). The SCP forwards the Service Request to the Producer, which returns a Response. The SCP then returns the Service Response to the Consumer. Subsequent requests are sent to the SCP. +- Model D:** The Consumer sends a Service Request + parameters to the SCP. The SCP forwards the Service Request to the Producer, which returns a Response. The SCP then returns the Service Response to the Consumer. Subsequent requests are sent to the SCP. + +Four communication models (A, B, C, D) for NF/NF services interaction. Model A shows direct communication between Consumer and Producer. Model B adds NRF discovery. Model C uses SCP for routing with NRF discovery. Model D uses SCP for routing with Service Request + parameters. + +Figure E.1-1: Communication models for NF/NF services interaction + +# Annex F (informative): Redundant user plane paths based on multiple UEs per device + +This clause describes an approach to realize multiple user plane paths in the system based on a device having multiple UEs and specific network deployments. + +The approach assumes a RAN deployment where redundant coverage by multiple gNBs (in the case of NR) is generally available. Upper layer protocols, such as the IEEE 802.1 TSN (Time Sensitive Networking), can make use of the multiple user plane paths. + +The UEs belonging to the same terminal device request the establishment of PDU Sessions that use independent RAN and CN network resources using the mechanisms outlined below. + +This deployment option has a number of preconditions: + +- The redundancy framework uses separate gNBs to achieve user plane redundancy over the 3GPP system. It is however up to operator deployment and configuration whether separate gNBs are available and used. If separate gNBs are not available for a device, the redundancy framework may still be applied to provide user plane redundancy in the rest of the network as well as between the device and the gNB using multiple UEs. +- Terminal devices integrate multiple UEs which can connect to different gNBs independently. +- RAN coverage is redundant in the target area: it is possible to connect to multiple gNBs from the same location. To ensure that the two UEs connect to different gNBs, the gNBs need to operate such that the selection of gNBs can be distinct from each other (e.g. gNB frequency allocation allows the UE to connect to multiple gNBs). +- The core network UPF deployment is aligned with RAN deployment and supports redundant user plane paths. +- The underlying transport topology is aligned with the RAN and UPF deployment and supports redundant user plane paths. +- The physical network topology and geographical distribution of functions also supports the redundant user plane paths to the extent deemed necessary by the operator. +- The operation of the redundant user plane paths is made sufficiently independent, to the extent deemed necessary by the operator, e.g. independent power supplies. + +Figure F-1 illustrates the architecture view. UE1 and UE2 are connected to gNB1 and gNB2, respectively and UE1 sets up a PDU Session via gNB1 to UPF1, while UE2 sets up a PDU Session via gNB2 to UPF2. UPF1 and UPF2 connect to the same Data Network (DN), but the traffic via UPF1 and UPF2 might be routed via different user plane nodes within the DN. UPF1 and UPF2 are controlled by SMF1 and SMF2, respectively. + +![Figure F-1: Architecture with redundancy based on multiple UEs in the device. The diagram shows two User Equipment (UE) units, UE1 and UE2, enclosed in a dashed box labeled 'Device'. UE1 is connected to gNB1, and UE2 is connected to gNB2. gNB1 is connected to AMF1 via an N2 interface and to UPF1 via an N3 interface. gNB2 is connected to AMF2 via an N2 interface and to UPF2 via an N3 interface. AMF1 is connected to Nsmf and SMF1. SMF1 is connected to UPF1 via an N4 interface. AMF2 is connected to Nsmf and SMF2. SMF2 is connected to UPF2 via an N4 interface. UPF1 and UPF2 are both connected to a Data Network (DN) via N6 interfaces. Nsmf is connected to Namf.](6584b95e34ea1f0b67144aa841db0863_img.jpg) + +``` +graph TD + subgraph Device + UE1[UE1] + UE2[UE2] + end + UE1 --- gNB1[gNB1] + UE2 --- gNB2[gNB2] + gNB1 -- N2 --> AMF1[AMF1] + gNB1 -- N3 --> UPF1[UPF1] + gNB2 -- N2 --> AMF2[AMF2] + gNB2 -- N3 --> UPF2[UPF2] + AMF1 -- Nsmf --> SMF1[SMF1] + SMF1 -- N4 --> UPF1 + AMF2 -- Nsmf --> SMF2[SMF2] + SMF2 -- N4 --> UPF2 + UPF1 -- N6 --> DN[DN] + UPF2 -- N6 --> DN + Nsmf -- Namf --> AMF1 + Nsmf -- Namf --> AMF2 +``` + +Figure F-1: Architecture with redundancy based on multiple UEs in the device. The diagram shows two User Equipment (UE) units, UE1 and UE2, enclosed in a dashed box labeled 'Device'. UE1 is connected to gNB1, and UE2 is connected to gNB2. gNB1 is connected to AMF1 via an N2 interface and to UPF1 via an N3 interface. gNB2 is connected to AMF2 via an N2 interface and to UPF2 via an N3 interface. AMF1 is connected to Nsmf and SMF1. SMF1 is connected to UPF1 via an N4 interface. AMF2 is connected to Nsmf and SMF2. SMF2 is connected to UPF2 via an N4 interface. UPF1 and UPF2 are both connected to a Data Network (DN) via N6 interfaces. Nsmf is connected to Namf. + +Figure F-1: Architecture with redundancy based on multiple UEs in the device + +The approach comprises the following main components shown as example using NR in figure F-2. + +- **gNB selection:** The selection of different gNBs for the UEs in the same device is realized by the concept of UE Reliability Groups for the UEs and also for the cells of gNBs. By grouping the UEs in the device and cells of gNBs in the network into more than one reliability group and preferably selecting cells in the same reliability group as the UE, it is ensured that UEs in the same device can be assigned different gNBs for redundancy as illustrated in Figure F-2, where UE1 and the cells of gNB1 belong to reliability group A, and UE2 and the cells of gNB2 belong to reliability group B. + +![Figure F-2: Reliability group-based redundancy concept in RAN. The diagram shows a 'Device' containing two UEs (UE1 and UE2) connected to two different gNBs (gNB1 and gNB2) which belong to different reliability groups (Reliability Group A and Reliability Group B). UE1 is connected to gNB1 (Reliability Group A), which is connected to AMF1 via N2. AMF1 is connected to Namf and SMF1 via N1. SMF1 is connected to UPF1 via N4. UPF1 is connected to DN via N6. UE2 is connected to gNB2 (Reliability Group B), which is connected to AMF2 via N2. AMF2 is connected to Namf and SMF2 via N1. SMF2 is connected to UPF2 via N4. UPF2 is connected to DN via N6. The gNBs are also connected to the UPFs via N3 interfaces.](aeb2a26a07219661191294dba528067a_img.jpg) + +Figure F-2: Reliability group-based redundancy concept in RAN. The diagram shows a 'Device' containing two UEs (UE1 and UE2) connected to two different gNBs (gNB1 and gNB2) which belong to different reliability groups (Reliability Group A and Reliability Group B). UE1 is connected to gNB1 (Reliability Group A), which is connected to AMF1 via N2. AMF1 is connected to Namf and SMF1 via N1. SMF1 is connected to UPF1 via N4. UPF1 is connected to DN via N6. UE2 is connected to gNB2 (Reliability Group B), which is connected to AMF2 via N2. AMF2 is connected to Namf and SMF2 via N1. SMF2 is connected to UPF2 via N4. UPF2 is connected to DN via N6. The gNBs are also connected to the UPFs via N3 interfaces. + +**Figure F-2: Reliability group-based redundancy concept in RAN** + +For determining the reliability grouping of a UE, one of the following methods or a combination of them can be used: + +- It could be configured explicitly to the UE and sent in a Registration Request message to the network using an existing parameter (such as an S-NSSAI in the Requested NSSAI where the SST is URLLC; the Reliability Group can be decided by the SD part). +- It could also be derived from existing system parameters (e.g. SUPI, PEI, S-NSSAI, RFSP) based on operator configuration. + +The Reliability Group of each UE is represented via existing parameters and sent from the AMF to the RAN when the RAN context is established, so each gNB has knowledge about the reliability group of the connected UEs. + +**NOTE:** An example realisation can be as follows: the UE's Allowed NSSAI can be used as input to select the RFSP index value for the UE. The RAN node uses the RFSP for RRM purposes and can based on local configuration determine the UE's Reliability Group based on the S-NSSAI in Allowed NSSAI and/or S-NSSAI for the PDU Session(s). + +The reliability group of the RAN (cells of gNBs) entities are pre-configured by the O&M system in RAN. It is possible for gNBs to learn the reliability group neighbouring cells as the Xn connectivity is set up, or the reliability group of neighbouring cells are also configured into the gNBs. + +In the case of connected mode mobility, the serving gNB prioritizes candidate target cells that belong to different reliability group than the UE. It follows that normally the UE is handed over only to cells in the same reliability group. If cells in the same reliability group are not available (UE is out of the coverage of cells of its own reliability group or link quality is below a given threshold) the UE may be handed over to a cell in another reliability group as well. + +If the UE connects to a cell whose reliability group is different from the UE's reliability group, the gNB initiates a handover to a cell in the appropriate reliability group whenever such a suitable cell is available. + +In the case of an Idle UE, it is possible to use the existing cell (re-)selection priority mechanism, with a priori UE config using dedicated signalling (in the RRCConnectionRelease message during transition from connected to idle mode) to configure the UE to reselect the cells of the appropriate reliability group for camping in deployments where the cell reliability groups use different sets of frequencies. + +- **UPF selection.** UPF selection mechanisms as described in clause 6.3.3 can be used to select different UPFs for the UEs within the device. The selection may be based either on UE configuration or network configuration of different DNNs leading to the same DN, or different slices for the two UEs. It is possible to use the UE's Reliability Group, described above for gNB selection, as an input to the UPF selection. The proper operator configuration of the UPF selection can ensure that the path of the PDU Sessions of UE1 and UE2 are independent. +- **Control plane.** The approach can optionally apply different control plane entities for the individual UEs within the device. This may be achieved by using: + - different DNNs for the individual UEs within the device to select different SMFs, + - or applying different slices for the individual UEs within the device either based on UE configuration or network subscription, to select different AMFs and/or SMFs. + +# Annex G (informative): SCP Deployment Examples + +## G.1 General + +This Annex provides deployment examples for the SCP but is not meant to be an exhaustive list of deployment options for the SCP. The first example G.1 is based on an SCP implement using (network wide) service mesh technology, while the second example builds on SCP and 5GC functions as independent deployment units. + +## G.2 An SCP based on service mesh + +### G.2.1 Introduction + +This clause describes an SCP deployment based on a distributed model in which SCP endpoints are co-located with 5GC functionality (e.g. an NF, an NF Service, a subset thereof such as a microservice implementing part of an NF/NF service or a superset thereof such as a group of NFs, NF Services or microservices). This example makes no assumptions as to the internal composition of each 5GC functionality (e.g. whether they are internally composed of multiple elements or whether such internal elements communicate with means other than the service mesh depicted in this example). + +In this deployment example, Service Agent(s) implementing necessary peripheral tasks (e.g. an SCP endpoint) are co-located with 5GC functionality, as depicted in Figure G.2.1-1. In this example, Service Agents and 5GC functionality, although co-located, are separate components. + +![Diagram of a deployment unit for 5GC functionality and co-located Service Agent(s).](e3eebf9854831ba50eca8b26c468f65e_img.jpg) + +The diagram illustrates a 'Unit of deployment for a 5GC functionality' as a vertical stack of three components. From top to bottom, they are: 'Service Agent N: other functionality', 'Service Agent 1: SCP endpoint', and '5GC functionality'. A vertical ellipsis is shown between Service Agent N and Service Agent 1. To the right of the top component, a line points to a text box stating: 'Co-located Service Agents provide 5GC functionality with peripheral tasks such as: communications proxy (e.g. SCP endpoint), logging, configuration, ...'. To the right of the bottom component, a line points to a text box stating: '5GC functionality (e.g. Npcf\_AMPolicyControl)'. + +Diagram of a deployment unit for 5GC functionality and co-located Service Agent(s). + +**Figure G.2.1-1: Deployment unit: 5GC functionality and co-located Service Agent(s) implementing peripheral tasks** + +In this deployment example, an SCP Service Agent, i.e. a service communication proxy, is co-located in the same deployment unit with 5GC functionality and provides each deployed unit (e.g. a container-based VNFC) with indirect communication and delegated discovery. + +Figure G.2.1-2 shows an overview of this deployment scenario. For SBI-based interactions with other 5GC functionalities, a consumer (5GC functionality A) communicates through its Service Agent via SBI. Its Service Agent selects a target producer based on the request and routes the request to the producer's (5GC functionality B) Service Agent. What routing and selection policies a Service Agent applies for a given request is determined by routing and selection policies pushed by the service mesh controller. Information required by the service mesh controller is pushed by the Service Agents to the service mesh controller. + +In this deployment, the SCP manages registration and discovery for communication within the service mesh and it interacts with an external NRF for service exposure and communication across service mesh boundaries. Operator-defined policies are additionally employed to generate the routing and selection policies to be used by the Service Agents. + +This example depicts only SBI-based communication via a service mesh, but it does not preclude the simultaneous use of the service mesh for protocols other than SBI supported by the service mesh or that the depicted 5GC functionality additionally communicates via other means. + +![Figure G.2.1-2: SCP Service mesh co-location with 5GC functionality. The diagram shows a central SCP block containing a Service Mesh controller and Internal service registration/discovery. Above the SCP, NRF and Operator policies are connected via Nnrf. Two Deployment units are shown, each containing a 5GC functionality (A and B) connected to a Service Agent via SBI. The Service Agents are connected to the SCP's Service Mesh controller. A legend indicates that Non-SCP 5GC functionality is represented by a light gray box and Service Mesh components by a dark gray box.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +Figure G.2.1-2: SCP Service mesh co-location with 5GC functionality. The diagram shows a central SCP block containing a Service Mesh controller and Internal service registration/discovery. Above the SCP, NRF and Operator policies are connected via Nnrf. Two Deployment units are shown, each containing a 5GC functionality (A and B) connected to a Service Agent via SBI. The Service Agents are connected to the SCP's Service Mesh controller. A legend indicates that Non-SCP 5GC functionality is represented by a light gray box and Service Mesh components by a dark gray box. + +Figure G.2.1-2: SCP Service mesh co-location with 5GC functionality + +From a 3GPP perspective, in this deployment example a deployment unit thus contains NF functionality and SCP functionality. Figure G.2.1-3 depicts the boundary between both 3GPP entities. In the depicted example, two NF Services part of the same NF and each exposing an SBI interface are deployed each in a container-based VNFC. A co-located Service Agent provides each NF Service with indirect communication and delegated discovery. + +![Figure G.2.1-3: Detail of the NF-SCP boundary. The diagram shows the boundary between NF and SCP. On the NF side, there are NF Service A and NF Service B. On the SCP side, there are Service Agents. Each NF Service is connected to its corresponding Service Agent via SBI. Both NF Service and Service Agent are contained within a Container-based VNFC. Ellipses indicate additional services and containers.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +Figure G.2.1-3: Detail of the NF-SCP boundary. The diagram shows the boundary between NF and SCP. On the NF side, there are NF Service A and NF Service B. On the SCP side, there are Service Agents. Each NF Service is connected to its corresponding Service Agent via SBI. Both NF Service and Service Agent are contained within a Container-based VNFC. Ellipses indicate additional services and containers. + +Figure G.2.1-3: Detail of the NF-SCP boundary + +### G.2.2 Communication across service mesh boundaries + +It is a deployment where a single service mesh covers all functionality within a given deployment or not. In cases of communication across the boundaries of a service mesh, the service mesh routing the outbound message knows neither whether the selected producer is in a service mesh nor the internal topology of the potential service mesh where the producer resides. + +In such a deployment, as shown in Figure G.2.2.-1, after producer selection is performed, routing policies on the outgoing service mesh are only aware of the next hop. + +Given a request sent by A, A's Service Agent will perform producer selection based on the received request. If the selected producer endpoint (e.g. D) is determined to be outside of Service Mesh 1, A's Service Agent routes the request to the Egress Proxy. For a successful routing, the Egress Proxy needs to be able to determine the next hop of the request. In this case, this is the Ingress Proxy of Service Mesh 2. The Ingress Proxy of Service Mesh 2 is, based on the information in the received request and its routing policies, able to determine the route for the request. Subsequently, D receives the request. No topology information needs to be exchanged between Service Mesh 1 and Service Mesh 2 besides a general routing rule towards Service Mesh 2 (e.g. a FQDN prefix) and an Ingress Proxy destination for requests targeting endpoints in Service Mesh 2. + +![Figure G.2.2-1: Message routing across service mesh boundaries. The diagram shows two service meshes, Service Mesh 1 and Service Mesh 2, separated by a central SCP (Service Communication Proxy). Service Mesh 1 contains three endpoints (A, B, C) connected to their respective Service Agents (A's, B's, C's). These agents send traffic to an Egress Proxy. The Egress Proxy connects to the SCP. The SCP connects to an Ingress Proxy, which then routes traffic to Service Mesh 2. Service Mesh 2 contains three endpoints (D, E, F) connected to their respective Service Agents (D's, E's, F's).](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +Figure G.2.2-1: Message routing across service mesh boundaries. The diagram shows two service meshes, Service Mesh 1 and Service Mesh 2, separated by a central SCP (Service Communication Proxy). Service Mesh 1 contains three endpoints (A, B, C) connected to their respective Service Agents (A's, B's, C's). These agents send traffic to an Egress Proxy. The Egress Proxy connects to the SCP. The SCP connects to an Ingress Proxy, which then routes traffic to Service Mesh 2. Service Mesh 2 contains three endpoints (D, E, F) connected to their respective Service Agents (D's, E's, F's). + +Figure G.2.2-1: Message routing across service mesh boundaries + +## G.3 An SCP based on independent deployment units + +This clause shows an overview of SCP deployment based on the 5GC functionality and SCP being deployed in independent deployment units. + +![Figure G.3-1: Independent deployment units for SCP and 5GC functionality. The diagram shows two separate deployment units. The top unit, 'Deployment unit for 5GC functionality', contains three boxes labeled '5GC functionality', which are connected to a list of services: '5GC functionality 1 e.g. Nudm_UEContextManagement service', '5GC functionality 2 e.g. Nudm_SubscriberDataManagement service', and an ellipsis. The bottom unit, 'Deployment unit for SCP functionality', contains two boxes labeled 'SCP functionality', which are connected to a list of services: 'SCP functionality 1 e.g. Controller (vendor specific)' and 'SCP functionality 2 e.g. Agents for ingress, LB,... (vendor specific)'.](90df9788d66ecf65abf861caf76be5ca_img.jpg) + +Figure G.3-1: Independent deployment units for SCP and 5GC functionality. The diagram shows two separate deployment units. The top unit, 'Deployment unit for 5GC functionality', contains three boxes labeled '5GC functionality', which are connected to a list of services: '5GC functionality 1 e.g. Nudm\_UEContextManagement service', '5GC functionality 2 e.g. Nudm\_SubscriberDataManagement service', and an ellipsis. The bottom unit, 'Deployment unit for SCP functionality', contains two boxes labeled 'SCP functionality', which are connected to a list of services: 'SCP functionality 1 e.g. Controller (vendor specific)' and 'SCP functionality 2 e.g. Agents for ingress, LB,... (vendor specific)'. + +Figure G.3-1: Independent deployment units for SCP and 5GC functionality + +The SCP deployment unit can internally make use of microservices, however these microservices are up to vendors implementation and can be for example SCP agents and SCP controller as used in this example. The SCP agents implement the http intermediaries between service consumers and service producers. The SCP agents are controlled by the SCP controller. Communication between SCP controller and SCP agents is via SCP internal interface (4) and up to vendors implementation. + +In this model it is a deployment choice to co-locate SCP and other 5GC functions or not. The SCP interfaces (1), (2) and (3) are service based interfaces. SCP itself is not a service producer itself, however acting as http proxy it registers services on behalf of the producers in NRF. Interface (2) represents same services as (1) however using SCP proxy addresses. Interface (3) is interfacing NRF e.g. for service registration on behalf of the 5GC functions or service discovery. + +![Figure G.3-2: 5GC functionality and SCP co-location choices. This diagram shows a 'Datacenter' box containing four '5GC functionality (one or several)' blocks. To the right is an 'SCP' box containing an 'SCP Controller' and two 'SCP agent' blocks. Arrows labeled '1' connect each 5GC functionality to an SCP agent. An arrow labeled '2' connects the top SCP agent to the second SCP agent. An arrow labeled '3' points from the SCP Controller to the right. An arrow labeled '4' points from the SCP Controller to the top SCP agent. A long arrow labeled 'using direct communication mode' points from the bottom 5GC functionality to the right.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +Figure G.3-2: 5GC functionality and SCP co-location choices. This diagram shows a 'Datacenter' box containing four '5GC functionality (one or several)' blocks. To the right is an 'SCP' box containing an 'SCP Controller' and two 'SCP agent' blocks. Arrows labeled '1' connect each 5GC functionality to an SCP agent. An arrow labeled '2' connects the top SCP agent to the second SCP agent. An arrow labeled '3' points from the SCP Controller to the right. An arrow labeled '4' points from the SCP Controller to the top SCP agent. A long arrow labeled 'using direct communication mode' points from the bottom 5GC functionality to the right. + +**Figure G.3-2: 5GC functionality and SCP co-location choices** + +For SBI-based interactions with other 5GC functions, a consumer communicates through a SCP agent via SBI (1). SCP agent selects a target based on the request and routes the request to the target SCP agent (2). What routing and selection policies each SCP agent applies for a given request is determined by routing and selection policies determined by the SCP controller using for example information provided via NRF (3) or locally configured in the SCP controller. The routing and selection information is provided by the SCP controller to the SCP agents via SCP internal interface (4). Direct communication can coexist in the same deployment based on 3GPP specified mechanisms. + +![Figure G.3-3: Overview of SCP deployment. This diagram shows two 'Datacenter' boxes, each containing four '5GC functionality (one or several)' blocks and an 'SCP' box. The 'SCP' box in each datacenter contains an 'SCP Controller' and two 'SCP agent' blocks. Arrows labeled '1' connect each 5GC functionality to an SCP agent. An arrow labeled '2' connects the top SCP agent in the left datacenter to the top SCP agent in the right datacenter. An arrow labeled '3' points from the top SCP Controller in the left datacenter to an 'NRF' box at the top. An arrow labeled '4' points from the top SCP Controller to its top SCP agent. A long arrow labeled 'using direct communication mode' connects the bottom 5GC functionality in the left datacenter to the bottom 5GC functionality in the right datacenter.](ef5f5c6665b6ae13660ede412333ba45_img.jpg) + +Figure G.3-3: Overview of SCP deployment. This diagram shows two 'Datacenter' boxes, each containing four '5GC functionality (one or several)' blocks and an 'SCP' box. The 'SCP' box in each datacenter contains an 'SCP Controller' and two 'SCP agent' blocks. Arrows labeled '1' connect each 5GC functionality to an SCP agent. An arrow labeled '2' connects the top SCP agent in the left datacenter to the top SCP agent in the right datacenter. An arrow labeled '3' points from the top SCP Controller in the left datacenter to an 'NRF' box at the top. An arrow labeled '4' points from the top SCP Controller to its top SCP agent. A long arrow labeled 'using direct communication mode' connects the bottom 5GC functionality in the left datacenter to the bottom 5GC functionality in the right datacenter. + +**Figure G.3-3: Overview of SCP deployment** + +## G.4 An SCP deployment example based on name-based routing + +### G.4.0 General Information + +This clause provides a deployment example for the SCP which is based on a name-based routing mechanism that provides IP over ICN capabilities such as those described in Xylomenos, George, et al. [G1]. + +The scenario describes an SCP offering based on an SBA-platform to interconnect 5GC Services (or a subset of the respective services). The Name-based Routing mechanism, described in this deployment example, is realized through a Path Computation Element which is the core part of the SCP. The 5GC Services are running as microservices on cloud/deployment units (clusters). A Service Router is the communication node (access node/gateway) between the SCP and the 5GC Services and resides as a single unit within a Service Deployment Cluster. The Service Router acts as communication proxy and it is responsible for mapping IP based messages onto ICN publication and subscriptions. The Service Router serves multiple 5GC Service Endpoints within that cluster. For direct communication the Service Router is not used. + +5GC Functionalities communicate with the Service Router using standardized 3GPP SBIs. + +The Functionalities within the Service Deployment Cluster are containerized Service Functions. + +Depicted in Figure G.4-1, the Service Router act as SCP termination point and offer the SBI to the respective 5GC Service Functionalities. In this example, Service Routers and 5GC functionality, although co-located, are separate components within the Service Deployment Cluster. Multiple Functionalities can exist within the Service Deployment Cluster, all served by the respective Service Router when needed to communicate to other Service Functionalities within different clusters. + +![Diagram of a deployment unit showing 5GC functionalities (A and B) connected to a Service Router via SBI interfaces, all within a Service Deployment Cluster.](1033dc9fde75540d224c907681b1b7aa_img.jpg) + +The diagram illustrates a deployment unit. A large grey rectangle represents the 'Service Deployment Cluster'. Inside this cluster, at the bottom, is a component labeled 'SCP'. Above the SCP is a white box labeled 'Service Router'. To the left of the Service Router, within the cluster, are two white boxes labeled '5GC Functionality A' and '5GC Functionality B'. Each of these functionalities has a double-headed arrow labeled 'SBI' (Service Based Interface) connecting it to the 'Service Router'. Additionally, there is a vertical double-headed arrow labeled 'SBI' connecting '5GC Functionality A' and '5GC Functionality B' directly. The entire cluster is enclosed in a dashed rectangular border. + +Diagram of a deployment unit showing 5GC functionalities (A and B) connected to a Service Router via SBI interfaces, all within a Service Deployment Cluster. + +**Figure G.4-1: Deployment unit: 5GC functionality and co-located Service Agent(s) implementing peripheral tasks** + +In Figure G.4-1, the two depicted 5GC Service Functionalities (realized as Network Function Service Instances) may communicate in two ways. However, before the communication can be established between two 5GC Functionalities, Service Registration and Service Discovery need to take place, as described in Figure G.4.1-1. Service Registration and Service Discovery are provided in a standardized manner using 3GPP Service Based Interfaces. + +### G.4.1 Service Registration and Service Discovery + +Service registration can be done in several ways. One option is that ready 5GC Service Functions may register themselves with their service profile via the Nnrf interface. The registration request is forwarded to the internal Registry as well as forwarded to the operator's NRF. The internal registration is used to store the address to identifier relationship and the Service Deployment Cluster location. The external registration (NRF) is used to expose the Service Functionality to Services outside the depicted SCP. + +Service discovery entails Function A requesting a resolvable identifier for Functionality B. This resolve request is received by the Service Router which performs the task with the help of the SCP. After the resolve is done, the 5GC Functionalities may communicate either directly without any further interaction through the SCP, when the targeted address is resolved within the same Service Deployment Cluster; or via the Service Router when the Functionality resides outside of the originator's Service Deployment Cluster. The Service Router then acts as gateway towards the underlying SCP platform. + +![Diagram of Figure G.4.1-1: Registering 5GC Functionalities in the SCP. The diagram shows a Service Deployment Cluster (SDC) within an SCP. Inside the SDC, there are two 5GC functionalities, '5GC Functionality A' and '5GC Functionality B', which are connected to each other via an SBI interface. Both functionalities have SBI interfaces connecting them to a 'Service Router' inside the SDC. The Service Router has an Nnrf interface connecting it to an external 'NRF' (Network Repository Function). The NRF is connected to a 'Discovery' and 'Registration' block, which in turn has an Nnrf interface connecting it back to the Service Router.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Diagram of Figure G.4.1-1: Registering 5GC Functionalities in the SCP. The diagram shows a Service Deployment Cluster (SDC) within an SCP. Inside the SDC, there are two 5GC functionalities, '5GC Functionality A' and '5GC Functionality B', which are connected to each other via an SBI interface. Both functionalities have SBI interfaces connecting them to a 'Service Router' inside the SDC. The Service Router has an Nnrf interface connecting it to an external 'NRF' (Network Repository Function). The NRF is connected to a 'Discovery' and 'Registration' block, which in turn has an Nnrf interface connecting it back to the Service Router. + +Figure G.4.1-1: Registering 5GC Functionalities in the SCP + +### G.4.2 Overview of Deployment Scenario + +Figure G.4.2-1 shows an overview of this deployment scenario. For SBI-based interactions with other 5GC functionalities, a consumer entity (e.g. 5GC functionality B in the cluster on the left side) communicates through the cluster's Service Router with other entities in other clusters (e.g. 5GC Functionality D in the cluster on the right side). The target selection is performed through the platform's Discovery Service. From the client's perspective, the Service Router is the first and only contact point to the SCP. The platform resolves the requested Service identifier and aligns the results with the platform's policies. The Path Computation Element calculates a path between the consumer and the producer (e.g. the shortest path between the nodes). + +![Diagram of Figure G.4.2-1: (NbR-) SCP interconnects multiple deployment clusters with external NRF. The diagram shows two Service Deployment Clusters (SDCs) connected to a central SCP. The left SDC contains '5GC Functionality A' and '5GC Functionality B' connected via SBI, and a 'Service Router' connected to both via SBI. The right SDC contains '5GC Functionality A' and '5GC Functionality D' connected via SBI, and a 'Service Router' connected to both via SBI. Both Service Routers have Nnrf interfaces connecting them to a 'Discovery' and 'Registration' block within the SCP. This block has an Nnrf interface connecting it to an external 'NRF'. The 'Discovery' and 'Registration' block also has an interface connecting it to a 'Path Computation Element' within the SCP. The 'Path Computation Element' has an interface connecting it to 'Operator Policies'.](b774dfc5023e15e9c352b97ca25a56d4_img.jpg) + +Diagram of Figure G.4.2-1: (NbR-) SCP interconnects multiple deployment clusters with external NRF. The diagram shows two Service Deployment Clusters (SDCs) connected to a central SCP. The left SDC contains '5GC Functionality A' and '5GC Functionality B' connected via SBI, and a 'Service Router' connected to both via SBI. The right SDC contains '5GC Functionality A' and '5GC Functionality D' connected via SBI, and a 'Service Router' connected to both via SBI. Both Service Routers have Nnrf interfaces connecting them to a 'Discovery' and 'Registration' block within the SCP. This block has an Nnrf interface connecting it to an external 'NRF'. The 'Discovery' and 'Registration' block also has an interface connecting it to a 'Path Computation Element' within the SCP. The 'Path Computation Element' has an interface connecting it to 'Operator Policies'. + +Figure G.4.2-1: (NbR-) SCP interconnects multiple deployment clusters with external NRF + +### G.4.3 References + +- [G1] Xylomenos, George, et al.: "IP over ICN goes live", 2018 European Conference on Networks and Communications (EuCNC). IEEE, 2018. + +# --- Annex H (normative): PTP usage guidelines + +## H.1 General + +This Annex provides guidelines on the use of certain specific IEEE parameters and protocol messages in the case of TSN as described in clause 5.27. + +## --- H.2 Signalling of ingress time for time synchronization + +The ingress timestamp (TSi) of the PTP event (e.g. Sync) message is provided from the ingress TT (NW-TT/UPF or DS-TT/UE) to the egress TT, if supported in the PTP messages as described in clauses 5.27.1.2.2.1 and 5.27.1.2.2.2 using the Suffix field defined in clause 13.4 of IEEE Std 1588 [126]. The structure of the Suffix field follows the recommendation of clause 14.3 of IEEE Std 1588 [126], with an organizationId specific to 3GPP, an organizationSubType referring to an ingress timestamp, and data field that carries the ingress timestamp encoded as specified in clause 5.3.3 of IEEE Std 1588 [126]. TS 24.535 [117] specifies the coding of the ingress timestamp in the (g)PTP messages between a DS-TT and a NW-TT. + +## --- H.3 Void + +## --- H.4 Path and Link delay measurements + +The procedure described in this clause is applicable if DS-TT and NW-TT support operating as a boundary clock or as a time-aware system or as peer to peer Transparent Clock or end to end Transparent Clock, and when the PTP instance in 5GS is configured to operate as a time-aware system or as a Boundary Clock or as peer to peer Transparent Clock or as end to end Transparent Clock. Whether DS-TT/NW-TT support operating as a boundary clock or peer to peer Transparent Clock or end to end Transparent Clock or as a time-aware system (support of the IEEE Std 802.1AS [104] PTP profile) may be determined as described in clause K.2.1. + +PTP ports in DS-TT and NW-TT may support the following delay measurement mechanisms: + +- Delay request-response mechanism as described in clause 11.3 of IEEE Std 1588 [126]; +- Peer-to-peer delay mechanism as defined in clause 11.4 of IEEE Std 1588 [126]; +- Common Mean Link Delay Service. + +Depending on the measurement mechanisms supported by DS-TT and NW-TT as well as the configured clock mode of 5GS, the PTP ports in DS-TT and NW-TT are configured as follows: + +- PTP ports configured to operate as a time-aware system according to IEEE Std 802.1AS [104] may be configured to use the peer-to-peer delay mechanism or Common Mean Link Delay Service; +- PTP ports configured to operate as a Boundary Clock according to IEEE Std 1588 [126] may be configured to use the delay request-response mechanism, the peer-to-peer delay mechanism or Common Mean Link Delay Service. +- PTP ports in 5GS configured to operate as a peer-to-peer Transparent Clock according to IEEE Std 1588 [126] shall use the peer-to-peer delay mechanism. +- PTP ports in 5GS configured to operate as an end-to-end Transparent Clock according to IEEE Std 1588 [126] do not actively participate in path and link measurements mechanisms but shall calculate and add residence time and delay asymmetry information to PTP messages as defined in clause 10.2.2 of IEEE Std 1588 [126]. + +If DS-TT and NW-TT support operating as an end-to-end Transparent Clock, then the residence time for one-step operation as an end-to-end Transparent Clock for the path and link measurements is calculated as follows: + +- Upon reception of a PTP Delay\_Req/Pdelay\_Req/Pdelay\_Resp message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for the message. +- The ingress timestamp is conveyed to the egress TT via the PDU Session as described in clause H.2. +- The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP message for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. If needed, the PTP port in the egress TT convert the calculated resident time in 5GS into the residence time expressed in PTP GM time e.g. by means of the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126]. +- The PTP port in the egress TT modifies the payload of the PTP Delay\_Req/Pdelay\_Req/Pdelay\_Resp message that it sends towards the downstream PTP instance as follows: + - Adds the calculated residence time to the correction field. + - Removes Suffix field that contains TSi. + +If DS-TT and NW-TT support operating as an end-to-end Transparent Clock, then the residence time for two-step operation as an end-to-end Transparent Clock for the path and link measurements is calculated as follows: + +- Upon reception of a PTP Delay\_Req/Pdelay\_Req/Pdelay\_Resp message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for the message. +- If the ingress TT receives a Pdelay\_Resp message with the twoStepFlag set to FALSE, then the ingress TT modifies the twoStepFlag to TRUE and creates a PTP Pdelay\_Resp\_Follow\_Up message. +- The ingress timestamp is conveyed to the egress TT via the PDU Session as described in clause H.2. +- The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP message for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. If needed, the PTP port in the egress TT converts the calculated residence time in 5GS into the residence time expressed in PTP GM time, e.g. by means of the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126]. The egress TT then stores the calculated residence time expressed in PTP GM time and removes Suffix field that contains TSi before sending the PTP Delay\_Req/Pdelay\_Req/Pdelay\_Resp message towards the downstream PTP instance. +- Upon reception of the PTP Delay\_Resp message associated with the PTP Delay\_Req, the egress TT for the PTP Delay\_Req message (i.e. the ingress TT for the PTP Delay\_Resp message) modifies the payload of the PTP Delay\_Resp message that it sends towards the ingress TT of the PTP Delay\_Req message (i.e. egress TT for the PTP Delay\_Resp message) as follows: + - Adds the (previously stored) calculated residence time to the correction field. +- Upon reception (or local creation) of the PTP Pdelay\_Resp\_Follow\_Up message associated with the previously received PTP Pdelay\_Resp message, the ingress TT for the PTP Pdelay\_Resp\_Follow\_Up message modifies the payload of the PTP Pdelay\_Resp\_Follow\_Up message that it sends towards the egress TT for the PTP Pdelay\_Resp\_Follow\_Up message as follows: + - Adds the (previously stored) calculated residence time of the associated PTP Pdelay\_Req message to the correction field. +- Upon reception of the PTP Pdelay\_Resp\_Follow\_Up message associated with the PTP Pdelay\_Resp, the egress TT for PTP Pdelay\_Resp\_Follow\_Up message modifies the payload of the PTP Pdelay\_Resp\_Follow\_Up message that it sends towards the downstream PTP instance as follows: + - Adds the (previously stored) calculated residence time of the associated PTP Pdelay\_Resp messages to the correction field. + +# Annex I (normative): TSN usage guidelines + +## I.1 Determination of traffic pattern information + +As described in clause 5.27.2, the calculation of the TSCAI relies upon mapping of information for the TSN stream(s) based upon certain IEEE standard information. + +Additional traffic pattern parameters such as maximum burst size and maximum flow bitrate can be mapped to MDBV and GFBR. + +The traffic pattern parameter determination based on PSFP (IEEE Std 802.1Q [98]), when available, is as follows: + +- Periodicity of a TSN stream is set equal to StreamGateAdminCycleTime if there is only one StreamGateControlEntry with a StreamGateStatesValue set to Open in the StreamGateAdminControlList. If there is more than one StreamGateControlEntry with a StreamGateStatesValue set to Open in the StreamGateAdminControlList, then the Periodicity of the TSN Stream is set equal to sum of the timeIntervalValues from the first gate open instance to a next gate open instance in the StreamGateAdminControlList. For aggregated TSN streams with same periodicity and compatible Burst Arrival Times, the periodicity of the aggregated flow of these TSN Streams is set equal to StreamGateAdminCycleTime received from CNC for one of the TSN streams that are aggregated. + +NOTE 1: Given that only TSN streams that have the same periodicity and compatible Burst Arrival Time can be aggregated, the StreamGateAdminCycleTime for those TSN streams is assumed to be the same. + +- Burst Arrival time of a TSN stream at the ingress port is determined based on the following conditions: + - The Burst Arrival Time of a TSN Stream should be set to StreamGateAdminBaseTime plus the sum of the timeIntervalValues for which the StreamGateStatesValue is Closed in the StreamGateAdminControlList until the first gate open time (i.e. until StreamGateStatesValue set to Open is found). If the StreamGateStatesValue is Open for the first timeIntervalValue, then the Burst Arrival time is set to StreamGateAdminBaseTime. For aggregated TSN streams, the arrival time is calculated similarly, but using the time interval to the first StreamGateStatesValue that is Open from the aggregated TSN streams. +- Burst Size of a TSN stream at the ingress port (which is useful to map to MDBV) is determined based on the following conditions: + - The Burst Size may be determined from TSN Stream gate control operations in the StreamGateAdminControlList. If in the StreamGateAdminControlList, IntervalOctetMax is provided for a StreamGateControlEntry with an "open" StreamGateStatesValue, the Burst Size is set to the IntervalOctetMax for that control list entry. If IntervalOctetMax is not provided, the Burst Size is set to the timeIntervalValue (converted from ns to s) of the StreamGateControlEntry with an "open" StreamGateStatesValue multiplied by the port bitrate. + - When multiple compatible TSN Streams are aggregated, the Burst Size is set to the sum of the Burst Sizes for each TSN stream as determined above. +- Maximum Flow Bitrate of a TSN stream (which is useful to map to GBR) is determined as follows: + - The Maximum Flow Bitrate of a TSN Stream is equal to the summation of all timeIntervalValue (converted from ns to s) with StreamGateStatesValue = Open, multiplied by the bitrate of the corresponding port, and divided by StreamGateAdminCycleTime. For aggregated TSN streams, the same calculation is performed over the burst of aggregated streams (calculated using superposition, i.e. timeIntervalValue with StreamGateStatesValue = Open of every stream is summed up, as they are assumed to have same periodicity, compatible Burst arrival time, and same traffic class if they are to be aggregated). + +When CNC configures the PSFP information to the TSN AF, the TSN AF may use local information (e.g. local configuration) to map the PSFP information to an ingress port and/or egress port of the 5GS bridge. + +NOTE 2: As an example, for the local configuration, the PSFP can use either the destination MAC address and VLAN identifier, or the source MAC address and VLAN identifier for stream identification. The TSN AF is pre-configured with either the MAC address of Ethernet hosts behind a given DS-TT port (identified by the DS-TT port MAC address), or the VLAN identifier used over a given DS-TT port, or both. When the TSN AF determines that one of the known Ethernet host's MAC address appears as a source or destination MAC address, it can identify that the ingress or egress port is the associated DS-TT port. + +# Annex J (informative): Link MTU considerations + +According to clause 5.6.10.4 networks can provide link MTU size for UEs. A purpose of the link MTU size provisioning is to limit the size of the packets sent by the UE to avoid packet fragmentation in the backbone network between the UE and the UPF acting as PSA (and/or across the N6 reference point). Fragmentation within the backbone network creates a significant overhead. Therefore operators might desire to avoid it. This Annex presents an overhead calculation that can be used by operators to set the link MTU size provided by the network. A UE might not employ the provided link MTU size, e.g. when the MT and TE are separated, as discussed in clause 5.6.10.4. Therefore, providing an MTU size does not guarantee that there will be no packets larger than the provided value. However, if UEs follow the provided link MTU value operators will benefit from reduced transmission overhead within backbone networks. + +One of the worst-case scenarios is when GTP packets, e.g. between a NG-RAN node and the 5GC, are transferred over IPSec tunnel in an IPv6 deployment. In that case the user packet first encapsulated in a GTP tunnel which results in the following overhead: + +- IPv6 header, which is 40 octets; +- UDP overhead, which is 8 octets; +- Extended GTP-U header, which is 16 octets. + +NOTE 1: The sending of a Reflective QoS Indicator within a GTP-U header extension, or the use of Long PDCP PDU numbers at handover will further increase the GTP-U header size (see TS 29.281 [75] and TS 38.415 [116]). + +In this scenario the GTP packet then further encapsulated into an IPSec tunnel. The actual IPSec tunnel overhead depends on the used encryption and integrity protection algorithms. TS 33.210 [115] mandates the support of AES-GMAC with a key length of 128 bits and the use of HMAC\_SHA-1 for integrity protection. Therefore, the overhead with those algorithms is calculated as: + +- IPv6 header, which is 40 octets; +- IPSec Security Parameter Index and Sequence Number overhead, which is 4+4 octets; +- Initialization Vector for the encryption algorithm, which is 16 octets; +- Padding to make the size of the encrypted payload a multiple of 16; +- Padding Length and Next Header octets (2 octets); +- Integrity Check Value, which is 12 octets. + +In order to make the user packet size as large as possible a padding of 0 octet is assumed. With this zero padding assumption the total overhead is 142 octets, which results a maximum user packet size of transport MTU minus 142 octets. Note that in the case of transport MTU=1500, this user packet size will result in a 1424 octets payload length to be ciphered, which is a multiple of 16, thus the assumption that no padding is needed is correct (see Figure J.1). Similar calculations can be done for networks with transport that supports larger MTU sizes. + +![Diagram illustrating the overhead calculation for transport MTU=1500 octet. The diagram shows the structure of an IP packet in a backbone network, which contains a GTP packet, which in turn contains a UE MTU. The total MTU is 1500 octets. The overhead is calculated as 89 * 16 = 1424 octets.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +| | | | | | | | | | +|-------------------------------|--------------|-------------|-------------|------------|--------------|----------------|-------------|-----------| +| IP packet in backbone network | | | | | | | | | +| | | | GTP packet | | | | | | +| | | | | | | UE MTU | | | +| 40 | 4+4 | 16 | 40 | 8 | 16 | 1358 | 1+1 | 12 | +| IPv6 header | IPSec SPI+SN | Init vector | IPv6 header | UDP header | GTP-U header | User IP packet | IPSec PL+NH | IPSec ICV | +| | | | 89*16=1424 | | | | | | +| 1500 | | | | | | | | | + +Diagram illustrating the overhead calculation for transport MTU=1500 octet. The diagram shows the structure of an IP packet in a backbone network, which contains a GTP packet, which in turn contains a UE MTU. The total MTU is 1500 octets. The overhead is calculated as 89 \* 16 = 1424 octets. + +**Figure J-1: Overhead calculation for transport MTU=1500 octet** + +The link MTU value that can prevent fragmentation in the backbone network between the UE and the UPF acting as PSA depends on the actual deployment. Based on the above calculation a link MTU value of 1358 is small enough in most of the network deployments. However for network deployments where the transport uniformly supports for example ethernet jumbo frames, transport MTU <= 9216 octets can provide a much larger UE MTU and hence more efficient transfer of user data. One example of when it can be ensured that all links support larger packet sizes, is when the UE uses a specific Network Slice with a limited coverage area. + +Note that using a link MTU value smaller than necessary would decrease the efficiency in the network. Moreover, a UE might also apply some tunnelling (e.g. VPN). It is desirable to use a link MTU size that assures at least MTU minus 220 octets within the UE tunnel to avoid the fragmentation of the user packets within the tunnel applied in the UE. In the case transport MTU is 1500 octets, this results a link MTU of 1280 octets (for the transport), which is the minimum MTU size in the case of IPv6. + +The above methodology can be modified for calculation of the UE's link MTU when a UPF has MTU limits on the N6 reference point and is offering a PDU Session with Ethernet or Unstructured PDU Session type between the UPF and the UE. + +# --- Annex K (normative): Port and user plane node management information exchange + +## K.1 Standardized port and user plane node management information + +Table K.1-1 and Table K.1-2 list standardized port management information and user plane node management information, respectively. + +Table K.1-1: Standardized port management information + +| Port management information | Applicability (see NOTE 6) | | Supported operations by TSN AF (see NOTE 1) | Supported operations by TSCTSF (see NOTE 1) | Reference | +|----------------------------------------------------------|----------------------------|-------|---------------------------------------------|---------------------------------------------|------------------------------------------------------| +| | DS-TT | NW-TT | | | | +| General | | | | | | +| Port management capabilities (see NOTE 2) | X | X | R | R | | +| Bridge delay related information | | | | | | +| txPropagationDelay | X | X | R | - | IEEE Std 802.1Q [98] clause 12.32.2.1 | +| txPropagationDelayDeltaThreshold (see NOTE 23) | X | X | RW | | | +| Traffic class related information | | | | | | +| Traffic class table | X | X | RW | - | IEEE Std 802.1Q [98] clause 12.6.3 and clause 8.6.6. | +| Gate control information | | | | | | +| queueMaxSDUTable | | | | | IEEE Std 802.1Q [98], clause 12.29.1 | +| > queueMaxSDU | X | X | RW | | IEEE Std 802.1Q [98], clause 12.29.1 | +| > TransmissionOverrun (see NOTE 3) | X | X | R | | IEEE Std 802.1Q [98], clause 12.29.1 | +| GateEnabled | X | X | RW | - | IEEE Std 802.1Q [98] Table 12-32 | +| AdminGateStates | X | X | RW | | IEEE Std 802.1Q [98] Table 12-32 | +| AdminBaseTime | X | X | RW | - | IEEE Std 802.1Q [98] Table 12-32 | +| AdminControlList | X | X | RW | - | IEEE Std 802.1Q [98] Table 12-32 | +| AdminCycleTime (see NOTE 3) | X | X | RW | - | IEEE Std 802.1Q [98] Table 12-32 | +| AdminControlListLength (see NOTE 3) | X | X | RW | - | IEEE Std 802.1Q [98] Table 12-32 | +| AdminCycleTimeExtension | X | X | RW | - | IEEE Std 802.1Q [98] Table 12-32 | +| Tick granularity | X | X | R | - | IEEE Std 802.1Q [98] Table 12-32 | +| SupportedListMax | X | X | R | - | IEEE Std 802.1Q [98] Table 12-32 | +| General Neighbor discovery configuration (NOTE 4) | | | | | | +| adminStatus | D | X | RW | - | IEEE Std 802.1AB [97] clause 9.2.5.1 | +| lldpV2LocChassisIdSubtype | D | X | RW | - | IEEE Std 802.1AB [97] Table 11-2 | +| lldpV2LocChassisId | D | X | RW | - | IEEE Std 802.1AB [97] Table 11-2 | +| lldpV2MessageTxInterval | D | X | RW | - | IEEE Std 802.1AB [97] Table 11-2 | +| lldpV2MessageTxHoldMultiplier | D | X | RW | - | IEEE Std 802.1AB [97] Table 11-2 | +| NW-TT port neighbor discovery configuration | | | | | | +| lldpV2LocPortIdSubtype | | X | RW | - | IEEE Std 802.1AB [97] Table 11-2 | +| lldpV2LocPortId | | X | RW | - | IEEE Std 802.1AB [97] Table 11-2 | +| DS-TT port neighbor discovery configuration | | | | | | +| lldpV2LocPortIdSubtype | D | | RW | - | IEEE Std 802.1AB [97] Table 11-2 | +| lldpV2LocPortId | D | | RW | - | IEEE Std 802.1AB [97] Table 11-2 | + +| | | | | | | +|---------------------------------------------------------------------------------------|---|---|---|---|------------------------------------------| +| Neighbor discovery information for each discovered neighbor of NW-TT (NOTE 26) | | | | | | +| lldpV2RemChassisIdSubtype | | X | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2RemChassisId | | X | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2RemPortIdSubtype | | X | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2RemPortId | | X | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| TTL | | X | R | - | IEEE Std 802.1AB [97]
clause 8.5.4 | +| Neighbor discovery information for each discovered neighbor of DS-TT (NOTE 5) | | | | | | +| lldpV2RemChassisIdSubtype | D | | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2RemChassisId | D | | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2RemPortIdSubtype | D | | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2RemPortId | D | | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| TTL | D | | R | - | IEEE Std 802.1AB [97]
clause 8.5.4.1 | +| Information for deterministic networking for each NW-TT port (NOTE 27) | | | | | | +| Interface information | | | | | | +| Interface type | | X | | R | IETF RFC 8343 [151] | +| Interface enabled status | | X | | R | IETF RFC 8343 [151] | +| phys-address | | X | | R | IETF RFC 8343 [151] | +| IPv4 information | | | | | | +| IPv4 enabled status | | X | | R | IETF RFC 8344 [152] | +| IPv4 forwarding status | | X | | R | IETF RFC 8344 [152] | +| IPv4 MTU | | X | | R | IETF RFC 8344 [152] | +| Information for each IPv4 address | | | | | | +| IPv4 address | | X | | R | IETF RFC 8344 [152] | +| prefix-length | | X | | R | IETF RFC 8344 [152] | +| netmask | | X | | R | IETF RFC 8344 [152] | +| origin | | X | | R | IETF RFC 8344 [152] | +| Information for each IPv4 neighbor | | | | | | +| IPv4 address | | X | | R | IETF RFC 8344 [152] | +| link-layer-address | | X | | R | IETF RFC 8344 [152] | +| origin | | X | | R | IETF RFC 8344 [152] | +| IPv6 information | | | | | | +| IPv6 enabled status | | X | | R | IETF RFC 8344 [152] | +| IPv6 forwarding status | | X | | R | IETF RFC 8344 [152] | +| IPv6 MTU | | X | | R | IETF RFC 8344 [152] | +| Information for each IPv6 address | | | | | | +| IPv6 address | | X | | R | IETF RFC 8344 [152] | +| prefix-length | | X | | R | IETF RFC 8344 [152] | +| origin | | X | | R | IETF RFC 8344 [152] | +| status | | X | | R | IETF RFC 8344 [152] | +| Information for each IPv6 neighbor | | | | | | +| IPv6 address | | X | | R | IETF RFC 8344 [152] | +| link-layer-address | | X | | R | IETF RFC 8344 [152] | +| origin | | X | | R | IETF RFC 8344 [152] | +| is-router | | X | | R | IETF RFC 8344 [152] | +| state | | X | | R | IETF RFC 8344 [152] | +| Stream Parameters (NOTE 11) | | | | | | +| MaxStreamFilterInstances | X | | R | - | IEEE Std 802.1Q [98]
clause 12.31.1.1 | +| MaxStreamGateInstances | X | | R | - | IEEE Std 802.1Q [98]
clause 12.31.1.2 | + +| | | | | | | +|----------------------------------------------------------------|---|---|----|----|---------------------------------------------------------------| +| MaxFlowMeterInstances | X | | R | - | IEEE Std 802.1Q [98]
clause 12.31.1.3 | +| SupportedListMax | X | | R | - | IEEE Std 802.1Q [98]
clause 12.31.1.4 | +| Per-Stream Filtering and Policing information (NOTE 10) | | | | | | +| Stream Filter Instance Table (NOTE 8) | | | | - | IEEE Std 802.1Q [98]
Table 12-35 | +| > StreamFilterInstanceIndex | X | X | RW | - | IEEE Std 802.1Q [98]
Table 12-35 | +| > Stream Identification type | X | X | RW | - | IEEE 802.1CB [83]
clause 9.1.1.6 | +| > Stream Identification Controlling Parameters | X | X | RW | - | IEEE 802.1CB [83]
clauses 9.1.2, 9.1.3, 9.1.4
(NOTE 12) | +| > PrioritySpec | X | X | RW | - | IEEE Std 802.1Q [98]
Table 12-35 | +| > StreamGateInstanceID | X | X | RW | - | IEEE Std 802.1Q [98]
Table 12-35 | +| Stream Gate Instance Table (NOTE 9) | | | | | IEEE Std 802.1Q [98]
Table 12-33 | +| StreamGateInstanceIndex | X | X | RW | - | IEEE Std 802.1Q [98]
Table 12-36 | +| StreamGateAdminBaseTime | X | X | RW | - | IEEE Std 802.1Q [98]
Table 12-36 | +| StreamGateAdminControlList | X | X | RW | - | IEEE Std 802.1Q [98]
Table 12-36 | +| StreamGateAdminCycleTime | X | X | RW | - | IEEE Std 802.1Q [98]
Table 12-36 | +| StreamGateTickGranularity | X | X | R | - | IEEE Std 802.1Q [98]
Table 12-36 | +| StreamGateAdminCycleTimeExtension | X | X | R | - | IEEE Std 802.1Q [98]
Table 12-36 | +| Time Synchronization Information | | | | | | +| TSN Time domain number (NOTE 24) | X | X | RW | | | +| Supported PTP instance types (NOTE 13) | X | | R | R | IEEE Std 1588 [126]
clause 8.2.1.5.5 | +| Supported transport types (NOTE 14) | X | | R | R | | +| Supported delay mechanisms (NOTE 15) | X | | R | R | IEEE Std 1588 [126]
clause 8.2.15.4.4 | +| PTP grandmaster capable (NOTE 16) | X | | R | R | | +| gPTP grandmaster capable (NOTE 17) | X | | R | R | | +| Supported PTP profiles (NOTE 18) | X | | R | R | | +| Number of supported PTP instances | X | | R | R | | +| PTP instance specification | | | | | | +| PTP Instance ID (NOTE 25) | X | X | RW | RW | | +| > PTP profile (NOTE 19) | X | | RW | RW | | +| > Transport type (NOTE 20) | X | | RW | RW | | +| > Grandmaster enabled (NOTE 21) | X | | RW | RW | | +| IEEE Std 1588 [126] data sets (NOTE 22) | | | | | | +| > defaultDS.clockIdentity | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.2.2 | +| > defaultDS.clockQuality.clockClass | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.3.1.2 | +| > defaultDS.clockQuality.clockAccuracy | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.3.1.3 | +| > defaultDS.clockQuality.offsetScaledLogVariance | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.3.1.4 | +| > defaultDS.priority1 | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.1 | +| > defaultDS.priority2 | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.2 | +| > defaultDS.domainNumber | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.3 | + +| | | | | | | +|-------------------------------------------------------|---|---|----|----|----------------------------------------------| +| > defaultDS.sdold | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.5 | +| > defaultDS.instanceEnable | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.5.2 | +| > defaultDS.instanceType | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.5.5 | +| > portDS.portIdentity | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.2.1 | +| > portDS.portState | X | X | R | R | IEEE Std 1588 [126]
clause 8.2.15.3.1 | +| > portDS.logMinDelayReqlInterval | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.3.2 | +| > portDS.logAnnounceInterval | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.1 | +| > portDS.announceReceiptTimeout | | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.2 | +| > portDS.logSyncInterval | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.3 | +| > portDS.delayMechanism | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.4 | +| > portDS.logMinPdelayReqlInterval | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.5 | +| > portDS.versionNumber | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.6 | +| > portDS.minorVersionNumber | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.7 | +| > portDS.delayAsymmetry | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.8 | +| > portDS.portEnable | X | X | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.5.1 | +| > timePropertiesDS.currentTimeOffset | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.4.2 | +| > timePropertiesDS.timeSource | X | | RW | RW | IEEE Std 1588 [126]
clause 8.2.4.9 | +| > externalPortConfigurationPortDS.desiredState | | | RW | RW | IEEE Std 1588 [126]
clause 15.5.3.7.15.1 | +| IEEE Std 802.1AS [104] data sets
(NOTE 22) | | | | | | +| > defaultDS.clockIdentity | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.2 | +| > defaultDS.clockQuality.clockClass | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.2 | +| > defaultDS.clockQuality.clockAccuracy | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.3 | +| > defaultDS.clockQuality.offsetScaledLogVariance | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.4 | +| > defaultDS.priority1 | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.5 | +| > defaultDS.priority2 | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.6 | +| > defaultDS.timeSource | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.15 | +| > defaultDS.domainNumber | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.16 | +| > defaultDS.sdold | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.3 | + +| | | | | | | +|--------------------------------------------|---|---|----|----|---------------------------------------| +| > defaultDS.instanceEnable | X | | RW | RW | IEEE Std 802.1AS [104] clause 14.2.19 | +| > portDS.portIdentity | | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.2 | +| > portDS.portState | | X | R | R | IEEE Std 802.1AS [104] clause 14.8.3 | +| > portDS.ptpPortEnabled | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.4 | +| > portDS.delayMechanism | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.5 | +| > portDS.isMeasuringDelay | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.6 | +| > portDS.asCapable | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.7 | +| > portDS.meanLinkDelay | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.8 | +| > portDS.meanLinkDelayThresh | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.9 | +| > portDS.delayAsymmetry | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.10 | +| > portDS.neighborRateRatio | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.11 | +| > portDS.initialLogAnnounceInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.12 | +| > portDS.currentLogAnnounceInterval | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.13 | +| > portDS.useMgtSettableLogAnnounceInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.14 | +| > portDS.mgtSettableLogAnnounceInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.15 | +| > portDS.announceReceiptTimeout | | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.16 | +| > portDS.initialLogSyncInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.17 | +| > portDS.currentLogSyncInterval | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.18 | +| > portDS.useMgtSettableLogSyncInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.19 | +| > portDS.mgtSettableLogSyncInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.20 | +| > portDS.syncReceiptTimeout | | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.21 | +| > portDS.syncReceiptTimeoutTimeInterval | | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.22 | + +| | | | | | | +|------------------------------------------------------|---|---|----|----|---------------------------------------| +| > portDS.initialLogPdelayReqInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.23 | +| > portDS.currentLogPdelayReqInterval | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.24 | +| > portDS.useMgtSettableLogPdelayReqInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.25 | +| > portDS.mgtSettableLogPdelayReqInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.26 | +| > portDS.initialLogGptpCapableMessageInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.27 | +| > portDS.currentLogGptpCapableMessageInterval | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.28 | +| > portDS.useMgtSettableLogGptpCapableMessageInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.29 | +| > portDS.mgtSettableLogGptpCapableMessageInterval | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.30 | +| > portDS.initialComputeNeighborRateRatio | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.31 | +| > portDS.currentComputeNeighborRateRatio | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.32 | +| > portDS.useMgtSettableComputeNeighborRateRatio | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.33 | +| > portDS.mgtSettableComputeNeighborRateRatio | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.34 | +| > portDS.initialComputeMeanLinkDelay | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.35 | +| > portDS.currentComputeMeanLinkDelay | X | X | R | R | IEEE Std 802.1AS [104] clause 14.8.36 | +| > portDS.useMgtSettableComputeMeanLinkDelay | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.37 | +| > portDS.mgtSettableComputeMeanLinkDelay | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.38 | +| > portDS.allowedLostResponses | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.39 | +| > portDS.allowedFaults | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.40 | +| > portDS.gPtpCapableReceiptTimeout | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.41 | +| > portDS.versionNumber | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.42 | +| > portDS.nup | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.43 | +| > portDS.ndown | X | X | RW | RW | IEEE Std 802.1AS [104] clause 14.8.44 | + +| | | | | | | +|------------------------------------------------|---|---|----|----|---------------------------------------------| +| > portDS.oneStepTxOper | X | X | R | R | IEEE Std
802.1AS [104]
clause 14.8.45 | +| > portDS.oneStepReceive | X | X | R | R | IEEE Std
802.1AS [104]
clause 14.8.46 | +| > portDS.oneStepTransmit | X | X | R | R | IEEE Std
802.1AS [104]
clause 14.8.47 | +| > portDS.initialOneStepTxOper | X | X | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.48 | +| > portDS.currentOneStepTxOper | X | X | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.49 | +| > portDS.useMgtSettableOneStepTxOper | X | X | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.50 | +| > portDS.mgtSettableOneStepTxOper | X | X | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.51 | +| > portDS.syncLocked | X | X | R | R | IEEE Std
802.1AS [104]
clause 14.8.52 | +| > portDS.pdelayTruncatedTimestampsArray | X | X | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.53 | +| > portDS.minorVersionNumber | X | X | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.54 | +| > timePropertiesDS.currentUtcOffset | X | | RW | RW | IEEE Std
802.1AS [104]
clause 14.5.2 | +| > externalPortConfigurationPortDS.desiredState | | X | RW | RW | IEEE Std
802.1AS [104]
clause 14.12.2 | + +- NOTE 1: R = Read only access; RW = Read/Write access; — = not supported. +- NOTE 2: Indicates which standardized and deployment-specific port management information is supported by DS-TT or NW-TT. +- NOTE 3: AdminCycleTime, AdminControlListLength and TransmissionOverrun are optional for gate control information. +- NOTE 4: If DS-TT supports neighbor discovery, then TSN AF sends the general neighbor discovery configuration for DS-TT Ethernet ports to DS-TT. If DS-TT does not support neighbor discovery, then TSN AF sends the general neighbor discovery configuration for DS-TT Ethernet ports to NW-TT using the User Plane Node Management Information Container (refer to Table K.1-2) and NW-TT performs neighbor discovery on behalf of DS-TT. When a parameter in this group is changed, it is necessary to provide the change to every DS-TT and the NW-TT that belongs to the 5GS TSN bridge. It is mandatory that the general neighbor discovery configuration is identical for all DS-TTs and the NW-TTs that belongs to the bridge. +- NOTE 5: If DS-TT supports neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from DS-TT. TSN AF indicates the neighbor discovery information for each discovered neighbor of DS-TT port to CNC. If DS-TT does not support neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from NW-TT, using the User Plane Node Management Information Container (refer to Table K.1-2), the NW-TT performing neighbor discovery on behalf of DS-TT. +- NOTE 6: X = applicable; D = applicable when validation and generation of LLDP frames is processed at the DS-TT. +- NOTE 7: Void. +- NOTE 8: There is a Stream Filter Instance Table per Stream. +- NOTE 9: There is a Stream Gate Instance Table per Gate. +- NOTE 10: TSN AF indicates the support for PSFP to the CNC only if each DS-TT and NW-TT of the 5GS bridge has indicated support of PSFP. DS-TT indicates support of PSFP using port management capabilities, i.e. by indicating support for the Per-Stream Filtering and Policing information and by setting higher than zero values for MaxStreamFilterInstances, MaxStreamGateInstances, MaxFlowMeterInstances, SupportedListMax parameters. When available, TSN AF uses the PSFP information for determination of the traffic pattern information as described in Annex I. The PSFP information can be used at the DS-TT (if supported) and at the NW-TT (if supported) for the purpose of per-stream filtering and policing as defined in clause 8.6.5.2.1 of IEEE Std 802.1Q [98]. +- NOTE 11: TSN AF composes a Stream Parameter Table towards the CNC. It is up to TSN AF how it composes the Stream Parameter Table based on the numerical values as received from DS-TT and NW-TT port(s) and for the bridge for each individual parameter. +- NOTE 12: The set of Stream Identification Controlling Parameters depends on the Stream Identification type value as defined in IEEE Std 802.1CB [83] Table 9-1 and clauses 9.1.2, 9.1.3, 9.1.4. +- NOTE 13: Enumeration of supported PTP instance types. Allowed values as defined in clause 8.2.1.5.5 of IEEE Std 1588 [126]. +- NOTE 14: Enumeration of supported transport types. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). +- NOTE 15: Enumeration of supported PTP delay mechanisms. Allowed values as defined in clause 8.2.15.4.4 of IEEE Std 1588 [126]. +- NOTE 16: Indicates whether DS-TT supports acting as a PTP grandmaster. +- NOTE 17: Indicates whether DS-TT supports acting as a gPTP grandmaster. +- NOTE 18: Enumeration of supported PTP profiles, each identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. +- NOTE 19: PTP profile to apply, identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. +- NOTE 20: Transport type to use. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). +- NOTE 21: Indicates whether to act as grandmaster or not, i.e. whether to send Announce, Sync and optionally Follow\_Up messages. +- NOTE 22: The IEEE Std 802.1AS [104] data sets apply if the IEEE 802.1AS PTP profile is used; otherwise the IEEE Std 1588 [126] data sets apply. +- NOTE 23: Indicates how much the txPropagationDelay needs to change so that DS-TT/NW-TT report a change in txPropagationDelay to TSN AF. This is optional for NW-TT. +- NOTE 24: Indicates the gPTP domain (identified by a domain number) that is assumed by the CNC as the reference clock for time information in the scheduled traffic (gate control) information, PSFP information and bridge delay related information. This is optional for NW-TT. +- NOTE 25: PTP Instance ID uniquely identifies a PTP instance within the user plane node. +- NOTE 26: TSN AF indicates the neighbor discovery information for each discovered neighbor of NW-TT port to CNC. +- NOTE 27: Applicable in case of interworking with IETF Deterministic Networking. + +**Table K.1-2: Standardized user plane node management information** + +| User plane node management information | Supported operations by TSN AF (see NOTE 1) | Supported operations by TSCTSF (see NOTE 1) | Reference | +|-----------------------------------------------------------------------------|---------------------------------------------|---------------------------------------------|-----------------------------------------| +| Information for 5GS Bridge/Router | | | | +| User plane node Address | R | R | | +| User plane node ID | R | R | | +| NW-TT port numbers | R | R | | +| Traffic forwarding information | | | | +| Static Filtering Entry (NOTE 3) | RW | - | IEEE Std 802.1Q [98]
clause 8.8.1 | +| General Neighbor discovery configuration (NOTE 2) | | | | +| adminStatus | RW | - | IEEE Std 802.1AB [97]
clause 9.2.5.1 | +| lldpV2LocChassisIdSubtype | RW | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2LocChassisId | RW | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2MessageTxInterval | RW | - | IEEE Std 802.1AB [97]
Table 11-2 | +| lldpV2MessageTxHoldMultiplier | RW | - | IEEE Std 802.1AB [97]
Table 11-2 | +| DS-TT port neighbor discovery configuration for DS-TT ports (NOTE 4) | | | | +| >DS-TT port neighbor discovery configuration for each DS-TT port | | | | +| >> DS-TT port number | RW | - | | +| >> lldpV2LocPortIdSubtype | RW | - | IEEE Std 802.1AB [97]
Table 11-2 | +| >> lldpV2LocPortId | RW | - | IEEE Std 802.1AB [97]
Table 11-2 | +| Discovered neighbor information for DS-TT ports (NOTE 4) | | | | +| >Discovered neighbor information for each DS-TT port (NOTE 4) | | | | +| >> DS-TT port number | R | - | | +| >> lldpV2RemChassisIdSubtype | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| >> lldpV2RemChassisId | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| >> lldpV2RemPortIdSubtype | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| >> lldpV2RemPortId | R | - | IEEE Std 802.1AB [97]
Table 11-2 | +| >> TTL | R | - | IEEE Std 802.1AB [97]
clause 8.5.4.1 | +| Stream Parameters (NOTE 5) | | | | +| MaxStreamFilterInstances | R | - | IEEE Std 802.1Q [98]
Table 12-34 | +| MaxStreamGateInstances | R | - | IEEE Std 802.1Q [98]
Table 12-34 | +| MaxFlowMeterInstances | R | - | IEEE Std 802.1Q [98]
Table 12-34 | +| SupportedListMax | R | - | IEEE Std 802.1Q [98]
Table 12-34 | +| Time synchronization information | | | | +| Supported PTP instance types (NOTE 6) | R | R | | +| Supported transport types (NOTE 7) | R | R | | +| Supported delay mechanisms (NOTE 8) | R | R | | +| PTP grandmaster capable (NOTE 9) | R | R | | +| gPTP grandmaster capable (NOTE 10) | R | R | | +| Supported PTP profiles (NOTE 11) | R | R | | +| Number of supported PTP instances | R | R | | +| Time synchronization information for PTP instances (NOTE 16) | | | | +| > PTP instance specification | | | | + +| | | | | +|---------------------------------------------------|----|----|----------------------------------------------| +| >> PTP Instance ID (NOTE 17) | RW | RW | | +| >> PTP profile (NOTE 12) | RW | RW | | +| >> Transport type (NOTE 13) | RW | RW | | +| >> Grandmaster candidate enabled | RW | RW | | +| IEEE Std 1588 [126] data sets (NOTE 15) | | | | +| >> defaultDS.clockIdentity | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.2.2 | +| >> defaultDS.clockQuality.clockClass | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.3.1.2 | +| >> defaultDS.clockQuality.clockAccuracy | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.3.1.3 | +| >> defaultDS.clockQuality.offsetScaledLogVariance | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.3.1.4 | +| >> defaultDS.priority1 | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.1 | +| >> defaultDS.priority2 | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.2 | +| >> defaultDS.domainNumber | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.3 | +| >> defaultDS.sdoId | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.4.5 | +| >> defaultDS.instanceEnable | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.5.2 | +| >> defaultDS.externalPortConfigurationEnabled | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.5.3 | +| >> defaultDS.instanceType | RW | RW | IEEE Std 1588 [126]
clause 8.2.1.5.5 | +| >> timePropertiesDS.currentUtcOffset | RW | RW | IEEE Std 1588 [126]
clause 8.2.4.2 | +| >> timePropertiesDS.timeSource | RW | RW | IEEE Std 1588 [126]
clause 8.2.4.9 | +| IEEE Std 802.1AS [104] data sets (NOTE 15) | | | | +| >> defaultDS.clockIdentity | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.2 | +| >> defaultDS.clockQuality.clockClass | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.2 | +| >> defaultDS.clockQuality.clockAccuracy | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.3 | +| >> defaultDS.clockQuality.offsetScaledLogVariance | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.4 | +| >> defaultDS.priority1 | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.5 | +| >> defaultDS.priority2 | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.6 | +| >> defaultDS.timeSource | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.15 | +| >> defaultDS.domainNumber | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.16 | +| >> defaultDS.sdoId | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.18 | +| >> defaultDS.externalPortConfigurationEnabled | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.4.3 | +| >> defaultDS.instanceEnable | RW | RW | IEEE Std
802.1AS [104]
clause 14.2.19 | + +| | | | | +|------------------------------------------------------------------------|----|----|---------------------------------------------| +| >> timePropertiesDS.currentUtcOffset | RW | RW | IEEE Std 802.1AS [104]
clause 14.5.2 | +| Time synchronization information for DS-TT ports | | | | +| > Time synchronization information for each DS-TT port | | | | +| > DS-TT port number | RW | RW | | +| >> Time synchronization information for each PTP Instance | | | | +| >> PTP Instance ID (NOTE 17) | RW | RW | | +| >> Grandmaster on behalf of DS-TT enabled (NOTE 14) | RW | RW | | +| IEEE Std 1588 [126] data sets (NOTE 15) | | | | +| >> portDS.portIdentity | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.2.1 | +| >> portDS.portState | R | R | IEEE Std 1588 [126]
clause 8.2.15.3.1 | +| >> portDS.logMinDelayReqlInterval | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.3.2 | +| >> portDS.logAnnounceInterval | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.1 | +| >> portDS.announceReceiptTimeout | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.2 | +| >> portDS.logSyncInterval | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.3 | +| >> portDS.delayMechanism | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.4 | +| >> portDS.logMinPdelayReqlInterval | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.5 | +| >> portDS.versionNumber | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.6 | +| >> portDS.minorVersionNumber | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.7 | +| >> portDS.delayAsymmetry | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.4.8 | +| >> portDS.portEnable | RW | RW | IEEE Std 1588 [126]
clause 8.2.15.5.1 | +| >> externalPortConfigurationPortDS.desiredState | RW | RW | IEEE Std 1588 [126]
clause 15.5.3.7.15.1 | +| IEEE Std 802.1AS [104] data sets (NOTE 15) | | | | +| >> portDS.portIdentity | RW | RW | IEEE Std 802.1AS [104]
clause 14.8.2 | +| >> portDS.portState | R | R | IEEE Std 802.1AS [104]
clause 14.8.3 | +| >> portDS.ptpPortEnabled | RW | RW | IEEE Std 802.1AS [104]
clause 14.8.4 | +| >> portDS.delayMechanism | RW | RW | IEEE Std 802.1AS [104]
clause 14.8.5 | +| >> portDS.isMeasuringDelay | R | R | IEEE Std 802.1AS [104]
clause 14.8.6 | +| >> portDS.asCapable | R | R | IEEE Std 802.1AS [104]
clause 14.8.7 | +| >> portDS.meanLinkDelay | R | R | IEEE Std 802.1AS [104]
clause 14.8.8 | +| >> portDS.meanLinkDelayThresh | RW | RW | IEEE Std 802.1AS [104]
clause 14.8.9 | +| >> portDS.delayAsymmetry | RW | RW | IEEE Std 802.1AS [104]
clause 14.8.10 | + +| | | | | +|-------------------------------------------------------|----|----|---------------------------------------------| +| >> portDS.neighborRateRatio | R | R | IEEE Std
802.1AS [104]
clause 14.8.11 | +| >> portDS.initialLogAnnounceInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.12 | +| >> portDS.currentLogAnnounceInterval | R | R | IEEE Std
802.1AS [104]
clause 14.8.13 | +| >> portDS.useMgtSettableLogAnnounceInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.14 | +| >> portDS.mgtSettableLogAnnounceInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.15 | +| >> portDS.announceReceiptTimeout | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.16 | +| >> portDS.initialLogSyncInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.17 | +| >> portDS.currentLogSyncInterval | R | R | IEEE Std
802.1AS [104]
clause 14.8.18 | +| >> portDS.useMgtSettableLogSyncInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.19 | +| >> portDS.mgtSettableLogSyncInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.20 | +| >> portDS.syncReceiptTimeout | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.21 | +| >> portDS.syncReceiptTimeoutTimeInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.22 | +| >> portDS.initialLogPdelayReqInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.23 | +| >> portDS.currentLogPdelayReqInterval | R | R | IEEE Std
802.1AS [104]
clause 14.8.24 | +| >> portDS.useMgtSettableLogPdelayReqInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.25 | +| >> portDS.mgtSettableLogPdelayReqInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.26 | +| >> portDS.initialLogGptpCapableMessageInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.27 | +| >> portDS.currentLogGptpCapableMessageInterval | R | R | IEEE Std
802.1AS [104]
clause 14.8.28 | +| >> portDS.useMgtSettableLogGptpCapableMessageInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.29 | +| >> portDS.mgtSettableLogGptpCapableMessageInterval | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.30 | +| >> portDS.initialComputeNeighborRateRatio | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.31 | +| >> portDS.currentComputeNeighborRateRatio | R | R | IEEE Std
802.1AS [104]
clause 14.8.32 | + +| | | | | +|--------------------------------------------------|----|----|---------------------------------------------| +| >> portDS.useMgtSettableComputeNeighborRateRatio | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.33 | +| >> portDS.mgtSettableComputeNeighborRateRatio | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.34 | +| >> portDS.initialComputeMeanLinkDelay | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.35 | +| >> portDS.currentComputeMeanLinkDelay | R | R | IEEE Std
802.1AS [104]
clause 14.8.36 | +| >> portDS.useMgtSettableComputeMeanLinkDelay | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.37 | +| >> portDS.mgtSettableComputeMeanLinkDelay | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.38 | +| >> portDS.allowedLostResponses | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.39 | +| >> portDS.allowedFaults | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.40 | +| >> portDS.gPtpCapableReceiptTimeout | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.41 | +| >> portDS.versionNumber | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.42 | +| >> portDS.nup | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.43 | +| >> portDS.ndown | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.44 | +| >> portDS.oneStepTxOper | R | R | IEEE Std
802.1AS [104]
clause 14.8.45 | +| >> portDS.oneStepReceive | R | R | IEEE Std
802.1AS [104]
clause 14.8.46 | +| >> portDS.oneStepTransmit | R | R | IEEE Std
802.1AS [104]
clause 14.8.47 | +| >> portDS.initialOneStepTxOper | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.48 | +| >> portDS.currentOneStepTxOper | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.49 | +| >> portDS.useMgtSettableOneStepTxOper | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.50 | +| >> portDS.mgtSettableOneStepTxOper | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.51 | +| >> portDS.syncLocked | R | R | IEEE Std
802.1AS [104]
clause 14.8.52 | +| >> portDS.pdelayTruncatedTimestampsArray | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.53 | +| >> portDS.minorVersionNumber | RW | RW | IEEE Std
802.1AS [104]
clause 14.8.54 | + +| | | | | +|------------------------------------------------------|----|----|---------------------------------------| +| >> externalPortConfigurationPortDS.desiredState | RW | RW | IEEE Std 802.1AS [104] clause 14.12.2 | +| Time synchronization status (TSS) information | | | | +| > Synchronization state | - | R | Table 5.27.1.12-1 | +| > Clock quality | - | R | Table 5.27.1.12-1 | +| >> Traceable to UTC | - | R | Table 5.27.1.12-1 | +| >> Traceable to GNSS | - | R | Table 5.27.1.12-1 | +| >> Frequency stability | - | R | Table 5.27.1.12-1 | +| >> Clock accuracy | - | R | Table 5.27.1.12-1 | +| > Parent time source | - | R | Table 5.27.1.12-1 | + +NOTE 1: R = Read only access; RW = Read/Write access; — = not supported. + +NOTE 2: General neighbor discovery information is included only when NW-TT performs neighbor discovery on behalf of DS-TT. When a parameter in this group is changed, it is necessary to provide the change to every DS-TT and the NW-TT that belongs to the 5GS TSN bridge. + +NOTE 3: If the Static Filtering Entry information is present, UPF/NW-TT can use Static Filtering Entry information for forwarding TSC traffic, as specified in clause 5.8.2.5.3. + +NOTE 4: DS-TT discovery configuration and DS-TT discovery information are used only when DS-TT does not support LLDP and NW-TT performs neighbor discovery on behalf of DS-TT. TSN AF indicates the discovered neighbor information for each DS-TT port to CNC. + +NOTE 5: TSN AF indicates the support for PSFP to the CNC only if each DS-TT and NW-TT of the 5GS bridge have indicated support of PSFP. The support of PSFP at the NW-TT ports is expressed by setting higher than zero values for MaxStreamFilterInstances, MaxStreamGateInstances, MaxFlowMeterInstances, SupportedListMax parameters. + +NOTE 6: Enumeration of supported PTP instance types. Allowed values as defined in clause 8.2.1.5.5 of IEEE Std 1588 [126]. + +NOTE 7: Enumeration of supported transport types. Allowed values: IPv4 (as defined in IEEE Std 1588 [126] Annex C), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). + +NOTE 8: Enumeration of supported PTP delay mechanisms. Allowed values as defined in clause 8.2.15.4.4 of IEEE Std 1588 [126]. + +NOTE 9: Indicates whether NW-TT supports acting as a PTP grandmaster. + +NOTE 10: Indicates whether NW-TT supports acting as a gPTP grandmaster. + +NOTE 11: Enumeration of supported PTP profiles, each identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. + +NOTE 12: PTP profile to apply, identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. + +NOTE 13: Transport type to use. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). + +NOTE 14: Indicates whether to act as grandmaster on behalf of a DS-TT port or not if 5GS is determined to be the grandmaster clock, i.e. whether to send Announce, Sync and optionally Follow\_Up messages on behalf of DS-TT. + +NOTE 15: The IEEE Std 802.1AS [104] data sets apply if the IEEE 802.1AS PTP profile is used; otherwise, the IEEE Std 1588 [126] data sets apply. + +NOTE 16: Specifies the default data set for each PTP instance identified by PTP instance ID within the user plane node. + +NOTE 17: PTP Instance ID uniquely identifies a PTP instance within the user plane node. + +## K.2 Port and user plane node management information exchange for time synchronization + +### K.2.1 Capability exchange + +DS-TT and NW-TT indicate time synchronization information they support inside the Port management capabilities (see Table K.1-1). + +TSN AF and TSCTSF may determine the PTP functionalities supported by DS-TT and NW-TT by retrieving the following port management information or user plane node management information, respectively: + +- Supported PTP instance types; +- Supported transport types; +- Supported PTP delay mechanisms; + +- Grandmaster capability; +- Supported PTP profiles; +- Number of supported PTP instances. + +NOTE: IF NW-TT or DS-TT do not indicate support for any of the PTP profiles and PTP instance types, then TSN AF or TSCTSF assume that the NW-TT or DS-TT only support acting as a PTP Relay instance with the gPTP GM connected on N6. + +If DS-TT and NW-TT support the PTP Relay instance type as defined by IEEE 802.1AS [104] then DS-TT and NW-TT shall include the IEEE 802.1AS [104] PTP profile in the "Supported PTP profiles" in PMIC and UMIC, respectively. + +The TSN AF or TSCTSF may retrieve the "Number of supported PTP instances" from NW-TT via UMIC and from DS-TT via PMIC. + +### K.2.2 PTP Instance configuration + +#### K.2.2.1 General + +Based on input received from external applications (CNC in case of TSN AF or any AF in case of TSCTSF), TSN AF or TSCTSF may configure PTP instances (identified by PTP Instance ID) in a DS-TT or NW-TT by sending port management information (PMIC, see Table K.1-1) and user plane node management information (UMIC, see Table K.1-2) to DS-TT or NW-TT as described below: + +- use PMIC "PTP instance specification" for configuring DS-TT(s) for PTP instance data sets common for all PTP ports (i.e. defaultDS and TimePropertiesDS), and PTP instance data sets specific for each PTP port (i.e. portDS data set); +- use UMIC "PTP instance specification" for configuring NW-TT for PTP instance data sets common for all PTP ports; +- use PMIC "PTP instance specification" for configuring NW-TT for PTP instance data sets specific for each PTP port; +- use UMIC "Time synchronization information for DS-TT ports" for configuring NW-TT for PTP instance data sets specific for each PTP port for the PTP ports in DS-TT(s). + +TSN AF or TSCTSF may also configure PTP instances for DS-TT ports in NW-TT by sending UMIC (see Table K.1-2) to NW-TT to enable NW-TT to operate as a grandmaster on behalf of DS-TT (see clause K.2.2.4 for more details). + +For each PTP instance the TSN AF or TSCTSF may provide individual PTP configuration parameters or may provide a PTP profile ID to DS-TT or NW-TT. The DS-TT and NW-TT use the default values as defined in the corresponding PTP Profile, if individual PTP configuration parameters that are covered by the PTP profile are not provided. + +NOTE 1: Even if PTP profiles are used to configure DS-TT or NW-TT, individual PTP parameters can still be configured in addition, e.g. domain numbers, transport to use, etc. + +To configure DS-TT and NW-TT to operate as a PTP relay instance, TSN AF or TSCTSF shall set the PTP profile (see Table K.1-1) to IEEE Std 802.1AS [104]. + +DS-TT may operate as a PTP relay instance with the gPTP GM connected on N6 until the first PTP instance is configured in the DS-TT by TSN AF or TSCTSF. + +To initialize a PTP instance in 5GS, TSN AF or TSCTSF creates a new PTP instance in NW-TT by assigning a new PTP Instance ID and indicating it to the NW-TT in "PTP instance specification" in UMIC and PMIC(s) for each NW-TT port that is part of the PTP instance. TSN AF or TSCTSF then retrieves the "defaultDS.clockIdentity" of the PTP instance in NW-TT via UMIC. NW-TT ensures that the clockIdentity in defaultDS in UMIC matches with the clockIdentity in the portDS.portIdentity in PMIC(s) for a particular PTP Instance ID. + +To add a DS-TT port into an existent PTP instance in 5GS, the TSN AF or TSCTSF indicates the PTP Instance ID (to which the DS-TT port is being added) to the DS-TT in "PTP instance specification" in PMIC, and indicating the PTP Instance ID to the NW-TT in "Time synchronization information for DS-TT ports" in UMIC for the corresponding DS-TT port. + +For a particular PTP instance in NW-TT, the same PTP Instance ID shall be used in "PTP instance specification" in PMIC, in "PTP instance specification" in UMIC, and in "Time synchronization information for DS-TT ports" in UMIC. + +NOTE 2: The TSN AF or TSCTSF creates a PTP Instance in the NW-TT or DS-TT by using the "Set parameter" operation code as described in TS 24.539 [139]. The NW-TT or DS-TT determines that this "Set parameter" operation creates a new PTP Instance based on the PTP Instance ID that does not correspond to any of the configured PTP Instances in the "PTP instance specification" and "Time synchronization information for DS-TT ports" (for NW-TT) or in the "PTP instance specification" (for DS-TT). + +The TSN AF or TSCTSF then initializes the PTP instance in the DS-TT by setting the applicable PTP instance data sets common for all PTP ports (i.e. defaultDS and TimePropertiesDS), (including"defaultDS.clockIdentity") via "PTP instance specification" in PMIC to the same value as retrieved from the NW-TT via "PTP instance specification" in UMIC. The TSN AF or TSCTSF also enables the PTP instance by setting the defaultDS.instanceEnable = TRUE to DS-TT via PMIC and to NW-TT via UMIC (if applicable). The TSN AF or TSCTSF can initialize any number of PTP instances: + +- a) among the DS-TT(s) and NW-TT that are part of the same set of PTP instances in 5GS; up to the maximum number of supported PTP instances by the NW-TT or DS-TT that supports the lowest number of supported PTP instances; and +- b) in the NW-TT; up to the maximum number of supported PTP instances by the NW-TT. + +NOTE 3: How the TSN AF or TSCTSF assign NW-TT port(s) of one NW-TT to different PTP instances is up to implementation. + +To remove a DS-TT port from a PTP instance in 5GS, the TSN AF or TSCTSF deletes the PTP instance in DS-TT using PMIC and in NW-TT using UMIC as specified in TS 24.539 [139]. To remove a NW-TT port from a PTP instance in 5GS, the TSN AF or TSCTSF deletes the PTP instance in NW-TT using PMIC as specified in TS 24.539 [139]. If a PTP instance in 5GS is no more needed the TSN AF or TSCTSF may delete the PTP instance in NW-TT using UMIC as specified in TS 24.539 [139]. + +#### K.2.2.2 Configuration for Sync and Announce reception timeouts + +The NW-TT shall be able to determine the timeout of the reception of (g)PTP Announce (when the 5GS operates as a time-aware system or Boundary Clock) and gPTP Sync messages (when the 5GS operates as time-aware system). To enable this, the TSCTSF or TSN AF shall configure the NW-TT for the following information via PMIC for each PTP port in NW-TT and "Time synchronization information for each DS-TT port" element in UMIC for each PTP port in DS-TT: + +portDS.announceReceiptTimeout (for time-aware system and Boundary Clock); +portDS.syncReceiptTimeout (for time-aware system); +portDS.logAnnounceInterval (for Boundary Clock). +portDS.initialLogAnnounceInterval, portDS.useMgtSettableLogAnnounceInterval and +portDS.mgtSettableLogAnnounceInterval (for time-aware system). + +#### K.2.2.3 Configuration for PTP port states + +The PTP port states may be determined by NW-TT either via: + +- Method a), BMCA procedure. +- Method b), local configuration. + +When Method b) is used, the TSN AF or TSCTSF sets the defaultDS.externalPortConfigurationEnabled (per PTP instance) in UMIC to TRUE, and sets the value of externalPortConfigurationPortDS.desiredState (per PTP port) in UMIC for each DS-TT port and in PMIC for each NW-TT port for the (g)PTP domain. + +#### K.2.2.4 Configuration for PTP grandmaster function + +The following options may be supported (per DS-TT) for the 5GS to generate the Sync, Follow\_Up and Announce messages for the Leader ports on the DS-TT: + +- a) NW-TT generates the Sync, Follow\_Up and Announce messages on behalf of DS-TT (e.g. if DS-TT does not support this). +- b) DS-TT generates the Sync, Follow\_Up and Announce messages in this DS-TT. + +TSN AF and TSCTSF may use the elements in port and user plane node management information container to determine the PTP grandmaster functionality supported by DS-TT and NW-TT and may configure the DS-TT and NW-TT ports to operate as in option a) or b) as follows: + +- The "PTP grandmaster capable" element and the "gPTP grandmaster capable" element in PMIC are used to indicate the support for PTP or gPTP grandmaster capability, respectively, in each DS-TT. If the TSN AF or TSCTSF determines the DS-TT supports grandmaster capability (PTP or gPTP grandmaster capable is TRUE), then either option a) or b) can be used for the PTP instance(s) in the DS-TT. Otherwise, only option a) can be used for the PTP instance(s) in the DS-TT. +- To enable option a) for PTP ports in DS-TT, the TSN AF or TSCTSF sets the element "Grandmaster on behalf of DS-TT enabled" TRUE (per PTP instance per DS-TT) in UMIC for the respective DS-TT port, and the TSN AF or TSCTSF sets the element "Grandmaster enabled" FALSE (per PTP instance per DS-TT) in PMIC to the respective DS-TT port. +- To enable option b) for PTP ports in DS-TT, the TSN AF or TSCTSF sets the element "Grandmaster on behalf of DS-TT enabled" FALSE in UMIC (per PTP instance per DS-TT) for the respective port, and the TSN AF or TSCTSF sets the element "Grandmaster enabled" TRUE (per PTP instance per DS-TT) in PMIC to the respective DS-TT port. +- To enable either option a) or option b) for a PTP instance, the TSN AF or TSCTSF sets the element "Grandmaster candidate enabled" TRUE (per PTP instance) in UMIC. +- When option b) is used for one or more PTP ports in DS-TT(s), the TSN AF or TSCTSF shall use the elements in defaultDS in PMIC for the respective DS-TT(s) and in UMIC for NW-TT to ensure that all PTP ports in the DS-TT(s) and NW-TT in particular PTP instance are distributing the same values of grandmasterPriority1, grandmasterClockQuality, grandmasterPriority2, grandmasterIdentity, and timeSource message fields in Announce messages. + +#### K.2.2.5 Configuration for Sync and Announce intervals + +The TSN AF or TSCTSF uses the values in portDS.logSyncInterval (for Boundary Clock) or portDS.initialLogSyncInterval, portDS.useMgtSettableLogSyncInterval and portDS.mgtSettableLogSyncInterval (for time-aware system) to configure the interval for the Sync messages (per PTP port) as described in IEEE Std 1588 [126] or IEEE Std 802.1AS [104], respectively. The TSCTSF or TSN AF configures those values as follows: + +- TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in NW-TT. +- TSCTSF or TSN AF use the "Time synchronization information for each DS-TT port" element in UMIC to configure the values for PTP ports in DS-TT(s) if NW-TT acts as GM on behalf of those DS-TTs. +- TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in DS-TT if the DS-TT is capable of acting as a GM. + +When the NW-TT generates the (g)PTP Sync messages on behalf of the DS-TT, the NW-TT uses the values in the element "Time synchronization information for each DS-TT port" in UMIC to determine the Sync interval for the PTP ports the respective DS-TT. When DS-TT generates the (g)PTP Sync messages, the DS-TT uses the values in PMIC to determine the Sync interval for the PTP ports in this DS-TT. + +The TSN AF or TSCTSF uses the values in portDS.logAnnounceInterval (for Boundary Clock) or portDS.initialLogAnnounceInterval, portDS.useMgtSettableLogAnnounceInterval and portDS.mgtSettableLogAnnounceInterval (for time-aware system) to configure the interval for the Announce messages (per PTP port) as described in IEEE Std 1588 [126] and IEEE Std 802.1AS [104], respectively. The TSCTSF or TSN AF configures those values as follows: + +- TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in NW-TT. +- TSCTSF or TSN AF use the "Time synchronization information for each DS-TT port" element in UMIC to configure the values for PTP ports in DS-TT(s) if NW-TT acts as GM on behalf of those DS-TTs. + +- TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in DS-TT if the DS-TT is capable of acting as a GM. + +When the NW-TT generates the (g)PTP Announce messages on behalf of the DS-TT, the NW-TT uses the values in the element "Time synchronization information for each DS-TT port" in UMIC to determine the Announce interval for the PTP ports the respective DS-TT. When DS-TT generates the (g)PTP Announce messages, the DS-TT uses the values in PMIC to determine the Announce interval for the PTP ports in this DS-TT. + +##### K.2.2.6 Configuration for transport protocols + +The procedure described in this clause is applicable when the PTP Profile that is used for the PTP instance in 5GS defines multiple permitted transport protocols. + +TSN AF or TSCTSF may use the element "Supported transport types" in port management information container (per DS-TT) to determine the supported transport types in the DS-TT. TSN AF or TSCTSF may use the element "Supported transport types" in UMIC (per NW-TT) to determine the supported transport types in the NW-TT. + +The TSN AF or TSCTSF may use the element "Transport type" (per PTP instance) in PMIC to configure the transport protocol in use for the PTP instance in DS-TT. The TSN AF or TSCTSF may use the element "Transport type" (per PTP instance) in UMIC to configure the transport protocol in use for the PTP instance in NW-TT. + +The PTP instance shall be configured to use one of the following transport protocols: + +- 1) Ethernet as described in Annex E of IEEE Std 1588 [126]. The Ethertype as defined for PTP shall be used. The related Ethernet frames carry the PTP multicast Ethernet destination MAC address. +- 2) UDP over IPv4 as described in Annex C of IEEE Std 1588 [126], +- 3) UDP over IPv6 as described in Annex D of IEEE Std 1588 [126]. + +Option 1 applies to Ethernet PDU Session type. Options 2 and 3 apply to IP PDU Session type or Ethernet PDU Session type with IP payload. + +# --- Annex L (normative): Support of GERAN/UTRAN access + +This annex applies when the SMF+PGW-C is enhanced to support UE accessing the network via GERAN/UTRAN over Gn/Gp interface. For this scenario, the SMF+PGW-C uses N7 interface to interact with PCF and the N40 interface to interact with CHF. + +NOTE 1: For the interface with the serving node of the UE, the SMF+PGW-C is assumed to behave as the Control Plane of the PGW described in Annex D of TS 23.401 [26]. + +SMF+PGW-C selection by SGSN is specified in Annex G of TS 23.502 [3]. + +The SMF+PGW-C interacting with PCF for GERAN/UTRAN access is specified in Annex G of TS 23.502 [3]. + +The functional description for SMF+PGW-C interacting with PCF to support GERAN/UTRAN access is specified in TS 23.503 [45]. + +NOTE 2: Support for IP address preservation upon mobility between 5GS and GERAN/UTRAN for PDN sessions established in EPC is described in clause 5.17.2.4. IP address preservation is not supported for direct mobility between 5GS and GERAN/UTRAN, nor for indirect mobility cases when the PDN session is established in 5GS or in GERAN/UTRAN. + +The charging services on SMF+PGW-C interactions with CHF for GERAN/UTRAN access are specified in TS 32.255 [68]. + +# Annex M (normative): Interworking with TSN deployed in the Transport Network + +## M.1 Mapping of the parameters between 5GS and TSN UNI + +**Editor's note:** The information provided here is a guidance for better understanding of the function. Content of this Annex will be updated to a functional level detail once stage 3 work is stable. + +The details of the parameters in the TSN UNI are specified in IEEE Std 802.1Q [98] and IEEE P802.1Qdj [146]. Stream identification is further specified in IEEE Std 802.1CB [83] and IEEE Std 802.1CBdb [178]. + +The SMF/CUC derives the End Station related information for the stream requirements towards the TN CNC for the QoS Flow as follows: + +a) For the Talker group: + +- StreamID: can be generated by the SMF/CUC based on the End Station MAC address acting as Talker and a UniqueID. SUPI, PDU Session ID and QFI may be used to derive the UniqueID. The MAC address is either pre-configured at the SMF/CUC or provided by the AN-TL or CN-TL to the SMF/CUC (e.g. as part of the EndStationInterfaces information). +- StreamRank: set to zero for ARP priority values 1-8; set to one for other ARP values. +- EndStationInterfaces: If the AN-TL and CN-TL are supported, the SMF/CUC receives the EndStationInterfaces (MacAddress, InterfaceName) from the AN-TL and CN-TL via TL-Container. If the AN-TL and CN-TL are not supported the SMF/CUC sets the information based on pre-configuration. +- DataFrameSpecification (optional): When it is present it specifies how the TN can identify packets of the TN stream using Ethernet, IP and transport protocol header fields in order to apply the required TSN configuration. + +The SMF/CUC may derive the DataFrameSpecification based on: + +- N3 tunnel end point addresses that are used for the QoS Flow. The SMF/CUC may instruct the UPF and NG-RAN to assign a separate N3 tunnel end point address for each QoS Flow that may carry TSC streams so that the TN can distinguish the QoS Flows based on the N3 tunnel destination IP addresses. + +NOTE 1: IPv6 can be used in the N3 tunnel end point addresses to provide sufficient address space in case separate N3 tunnel end point addresses are used for each QoS flow that can carry time sensitive streams. + +- Mask-and-match stream identification parameters (IEEE 802.1CBdb [178] clause 9.1.6) (optional). The SMF/CUC may indicate mask-and-match configuration based on the TEID and QFI of the given QoS flow and the destination IP address to the TN CNC, when the deployment supports mask-and-match stream identification function as defined in clause 6.8 in IEEE Std 802.1CBdb [178]. This functionality can be used for example to check for the TEID and QFI in the GTP header and the destination IP address to distinguish the QoS Flows. This enables the TN CNC to configure the mask-and-match stream identification function in the transport network. This is an option that allows to use a single GTP-U tunnel as defined for non-TSN Transport networks. + +The DataFrameSpecification or mask-and-match stream identification parameters may be provided to the AN-TL and CN-TL to configure stream identification. In that case, the AN-TL and CN-TL can perform the stream identification without relying on additional information from the upper layers of the AN or CN node. When AN-TL and CN-TL are not supported the TN CNC configures the edge bridge to perform the stream transformation based on the provided the DataFrameSpecification or mask-and-match parameters when applicable. + +- TrafficSpecification elements: + +- Interval: derived from the Periodicity of the traffic as indicated in the TSCAI. +- MaxFramesPerInterval: specifies the maximum number of frames that the Talker transmits in one Interval. +- MaxFrameSize: derived from the MDBV of the QoS Flow. If the PCF determines interworking with a TSN network deployed in the transport network is supported based on the DNN/S-NSSAI of the PDU Session, the PCF generates MDBV based on the Burst Size as described in clause 5.27.3 and the PCF transfers the MDBV to the SMF/CUC. The SMF/CUC sets MaxFrameSize based on the following formula: MDBV of the QoS Flow - the framing bits which is not used for transferring in 5GS, (e.g. CRC + the GTP-U tunnel overhead). + +- TransmissionSelection: specifies the algorithm that the Talker uses to transmit the Stream's traffic class. If no algorithm is known, the value zero (strict priority) is used. + - TSpecTimeAware group (optional, present only if the traffic in the QoS Flow is time-synchronized): + - EarliestTransmitOffset: the earliest offset within the Interval. + + +For uplink, EarliestTransmitOffset should be set based on the following formula: + +Packet arrival time at the Talker (UL) - M x Interval, where M is the largest integer for which the relation: + +Packet arrival time at the Talker (UL) > M x Interval duration. + +would be true. + +Packet arrival time at the Talker (UL) should be: TSCAC BAT in UL direction (presented in TAI time and corrected for clock drifting as specified in the present specification) + UE-DS-TT Residence Time. + +For downlink, EarliestTransmitOffset should be set based on the following formula: + +Packet arrival time at the Talker (DL) - M x Interval, where M is the largest integer for which the relation: + +Packet arrival time at the Talker (DL) > M x Interval duration. + +would be true. + +Packet arrival time at the Talker (DL) should be TSCAC BAT in DL direction (presented in TAI time and corrected for clock drifting as specified in the present specification). + - LatestTransmitOffset: the last chance within an interval should leave enough time to transfer a packet with MaxFrameSize. Derived from the end of the interval, the time to transfer a packet with MaxFrameSize. The LatestTransmitOffset shall be set to the Buffer Capability when the value of LatestTransmitOffset subtracted by the packet arrival time at the Talker (either UL or DL respectively as described in EarliestTransmitOffset) exceeds the Buffer capability. The value of LatestTransmitOffset shall be larger or equal than EarliestTransmitOffset. + - Jitter: derived in SMF/CUC based on local information on Jitter in AN-TL and CN-TL and respective stream and traffic interference. Annex U, clauses U.1.1, U.1.2, and U.1.3 of IEEE Std 802.1Q [98] provide some examples. + - UserToNetworkRequirements: + - NumSeamlessTrees: set to one (no redundancy) or other value (if redundancy is required). + - MaxLatency: set to CN PDB subtracted by maximum possible buffer duration in Talker. Maximum possible buffer duration is set to LatestTransmitOffset subtracted by EarliestTransmitOffset. + - InterfaceCapabilities (optional): If the AN-TL and CN-TL are supported, the SMF/CUC collects InterfaceCapabilities from AN-TL and CN-TL via TL-Container. If the AN-TL and CN-TL are not supported, the SMF/CUC leaves the InterfaceCapabilities empty. +- b) For the Listener group: +- Stream ID and Stream Rank: that were generated for the Talker of the TN stream are also used by the SMF/CUC for the Listener. + - EndStationInterfaces: derived as with the corresponding information for the Talker group. + - UserToNetworkRequirements: + - NumSeamlessTrees: set to one. + - MaxLatency: derived as with the corresponding information for the Talker group. + - InterfaceCapabilities: derived as with the corresponding information for the Talker group. +- c) For the Status group: The Status group contains the end station communication-configuration provided by TN CNC to the SMF/CUC: +- Stream ID. + - StatusInfo. + - AccumulatedLatency: If the AccumulatedLatency is included from TN CNC to SMF/CUC for a stream in DL direction, the SMF/CUC may use the AccumulatedLatency to update the TSCAI BAT to the NG-RAN; the SMF sets the TSCAI Burst Arrival Time in downlink direction as the sum of the TSCAC BAT value in downlink direction and AccumulatedLatency and the buffer duration in Talker in CN-TL. The buffer duration in CN-TL is zero if TimeAwareOffset for the Talker group is not present, and TimeAwareOffset - EarliestTransmitOffset if the TimeAwareOffset is present for the Talker group. + - InterfaceConfiguration (optional): + - MAC Address (optional, present only if the respective InterfaceCapability contains a value for Active Destination MAC and VLAN Stream identification in CB-StreamIdTypeList, and stream transformation is performed in AN-TL and CN-TL). + - VLAN Tag (optional, present only if the respective InterfaceCapability contains that it is VlanTagCapable and a value for Active Destination MAC and VLAN Stream identification in CB-StreamIdTypeList, and the stream transformation is performed in AN-TL and CN-TL). + - IPv4/IPv6 Tuples (optional, but not supported in this release of the specification). + +- TimeAwareOffset (optional, present only if the traffic is time-synchronized, AN-TL and CN-TL is supported, and TSpecTimeAware elements were provided in the stream requirements). + +If the InterfaceConfiguration is included and if the AL-TL/CN-TL acting as Talker End Station support the Stream Transformation as described in IEEE Std 802.1Q [98], the SMF/CUC can instruct the UPF and NG-RAN to assign an individual TSN Transport address by providing the InterfaceConfiguration to the AN-TL/CN-TL via TL-Container. The Talker in AN-TL/CN-TL shall use the indicated InterfaceConfiguration, e.g. source MAC address, multicast destination MAC address, VLAN ID, as assigned by the TN CNC for the data stream in a QoS Flow. The TN can identify the streams based on the Stream Transformation that is applied in the AN-TL/CN-TL acting as Taker End Station. This allows to use a single GTP-U tunnel as defined for non-TSN Transport networks. + +If the TimeAwareOffset is included from TN CNC to SMF/CUC, the SMF/CUC should send the TimeAwareOffset to the AN-TL (for streams in UL direction) or the CN-TL port (for streams in the DL direction). The AL-TL/CN-TL derive Gate Control information (i.e. AdminBaseTime, AdminCycleTime, AdminControlListLength, and AdminControlList) based on the TimeAwareOffset as defined in IEEE Std 802.1Q [98] at the AN-TL (for streams in UL direction) and the CN-TL port (for streams in the DL direction). The AN-TL or CN-TL acting as Talker buffers the data burst until the time indicated in the TimeAwareOffset is reached. + +If the SMF/CUC receives a TimeAwareOffset from TN CNC for a downlink stream (i.e. for a Talker in the UPF/CN-TL), the SMF/CUC adds the received TimeAwareOffset value to the TSCAI BAT in the DL direction in the TSCAI and updates the NG-RAN for the new TSCAI. + +- FailedInterfaces (optional) provides a list of one or more physical ports of failed end stations or bridges to locate the interfaces in the physical topology that caused the failure. It is up to implementation how the SMF reacts when it receives FailedInterfaces. + +NOTE 2: It is assumed that the end station communication-configuration will contain at least the same information as defined for the status. + +NOTE 3: If Jitter value needs to be considered, EarliestTransmitOffset for UL and DL and LatestTransmitOffset shall be Jitter corrected. How Jitter correction is carried out is up to implementation. + +## --- M.2 TL-Container Information + +Table M.2-1: TL-Container Information + +| TL-Container information | Supported Operations - AN-TL/CN-TL (see NOTE 1) | | Reference | | +|-----------------------------------------------------------------------------------------------|-------------------------------------------------|----------|-----------------------------------------|--| +| | Talker | Listener | | | +| End Station Parameters of AN-TL/CN-TL | | | | | +| List of InterfaceID group(s) | | | | | +| >Mac Address | Get | Get | IEEE Std 802.1Q [98], Table 46-3 | | +| >InterfaceName (see NOTE 2) | Get | Get | IEEE Std 802.1Q [98], Table 46-3 | | +| InterfaceCapabilities (see NOTE 3) | | | | | +| >VlanTagCapable (see NOTE 4) | Get | Get | IEEE Std 802.1Q [98], Table 46-3 | | +| >BufferCapability (see NOTE 5) | Get | - | Annex M.1 | | +| TN Stream Parameters | | | | | +| TN Stream Identification Information for mask-and-match (see NOTE 7, NOTE 14) | | | | | +| >tsnCpeMmIdMsduMaskLength | Set | Set | IEEE Std 802.1CBdb [X], clause 9.1.6.5 | | +| >tsnCpeMmIdMsduMask | Set | Set | IEEE Std 802.1CBdb [X], clause 9.1.6.6 | | +| >tsnCpeMmIdMsduMatch | Set | Set | IEEE Std 802.1CBdb [X], clause 9.1.6.7 | | +| TN Stream Identification Information for DataFrameSpecification (See NOTE 13, NOTE 14) | | | | | +| >DataFrameSpecification | Set | Set | IEEE Std 802.1Q [98], Clause 46.2.3.4 | | +| Configuration of End Station Interface | | | | | +| >Interface ID group | | | | | +| >>InterfaceName (see NOTE 8) | Set | Set | IEEE Std 802.1Q [98], Table 46-3 | | +| >>Mac Address | Set | Set | IEEE Std 802.1Q [98], Table 46-3 | | +| >InterfaceConfiguration (See NOTE 9, NOTE 10, NOTE 12) | | | | | +| >>IEEE802-MacAddresses | Set | Set | IEEE Std 802.1Q [98], Clause 46.2.5.3.1 | | +| >>IEEE802-VlanTag | Set | Set | IEEE Std 802.1Q [98], Clause 46.2.5.3.2 | | +| >>IPv4-tuple | Set | Set | IEEE Std 802.1Q [98], Clause 46.2.5.3.3 | | +| >>IPv6-tuple | Set | Set | IEEE Std 802.1Q [98], Clause 46.2.5.3.4 | | +| >>TimeAwareOffset (see NOTE 12) | Set | - | IEEE Std 802.1Q [98], clause 46.2.5.3.5 | | +| >Other parameters to Calculate Gate Control Information (See NOTE 6) | | | | | +| >>Interval | Set | - | IEEE Std 802.1Q [98], Table 46-8 | | +| >>MaxFrameSize (see NOTE 11) | Set | - | IEEE Std 802.1Q [98], Table 46-8 | | + +NOTE 1: Get = Get Response; Set = Set Request; - = not supported. + +NOTE 2: This parameter is optional and only required if End Station has more than one Interface/Port. It identifies the Interface/Port at the End Station. + +NOTE 3: Interface Capabilities are identical for all Interfaces/Ports of the End Station. + +NOTE 4: Possible values are TRUE or FALSE. + +NOTE 5: Maximum possible buffer duration for a packet with the maximum size of an Ethernet packet (1522 Bytes). + +NOTE 6: SMF/CUC enables the TL to calculate Gate Control Information. Port(s) of the Talker TL may create jitter due to implementation of the TL. How the jitter behaviour is identified and the correction is carried out is up to implementation. + +NOTE 7: The parameters are provided if mask-and-match stream identification is supported. + +NOTE 8: The parameter is provided if End Station supports multiple Interfaces/Ports. SMF/CUC guarantees that the End Station MAC address + InterfaceName, which is provided from TN-CNC as InterfaceConfiguration is conveyed with respect to the LLDP information sent via each interface at the user plane. + +NOTE 9: IEEE802-MacAddresses and IEEE802-VlanTag are provided if Stream Transformation is performed at AN-TL/CN-TL and if Active Destination MAC and VLAN stream identification is signalled from SMF/CUC to TN CNC and if TN CNC provides it in the status group for the Interface/Port. + +NOTE 10: Vlanid in IEEE802-VlanTag is provided if Stream Transformation is performed at AN-TL/CN-TL and if Active Destination MAC and VLAN stream identification is signalled from SMF/CUC to TN CNC and if TN CNC provides it in the status group for the Interface/Port and End Station VlanTagCapable is TRUE. + +NOTE 11: Message Length of the Stream including the GTP-U header size. + +NOTE 12: TimeAwareOffset is provided if TN Stream is scheduled. + +NOTE 13: The TL indicates a respective FailureCode if it detects a mismatch between the DataFrameSpecification and the GTP-U information received outside of the TL-Container. + +NOTE 14: Mask-and-match and DataFrameSpecification shall not be supported at the same time. + + + +# --- Annex N (informative): Support for access to Localized Services + +## N.1 General + +A Localized Service is a service, which is provided at specific/limited area and/or can be bounded in time. The service can be realized via applications (e.g. live or on-demand audio/video stream, electric game, IMS, etc.), or connectivity (e.g. UE to UE, UE to Data Network, etc.). + +A Localized Service provider is an application provider or network operator who make their services localized and that are offered to the end user via a network. A network providing Localized Services can be an SNPN or a PNI-NPN. + +## --- N.2 Enabling access to Localized Services + +### N.2.1 General + +To enable a PNI-NPN or SNPN to provide access to Localized Services, the PNI-NPN or SNPN operator configures the network with information enabling the UEs to access the Localized Services using the PNI-NPN or SNPN according to any validity of the Localized Services, and the information is determined in agreement with the Localized Service Provider e.g.: + +- a. Identification of each Localized Service, e.g. to be used in URSP rules. +- b. validity restriction for each Localized Service, e.g. the validity of time and/or location. +- c. service parameters for each Localized Service, e.g. DNN, S-NSSAI and QoS requirements. +- d. service authorization methods, e.g. NSSAA or Secondary authentication/authorization during PDU Session establishment. + +To allow the UE to access the PNI-NPN providing access to Localized Services using credentials of the HPLMN, the PNI-NPN can be configured based on the Localized Service agreements between the PNI-NPN and the HPLMN, to allow primary authentication towards the HPLMN. + +To allow the UE to access the SNPN providing access to Localized Services using credentials of the Credentials Holder, the SNPN can be configured based on Localized Service agreements between the SNPN and the Credentials Holder, to allow primary authentication towards the Credentials Holder. + +To allow the UE to access the SNPN providing access to Localized Services when new credential is required, the SNPN can provide UE onboarding function as specified in clause 5.30.2.10 for the UE to obtain credential and necessary information to access the SNPN, or the UE can leverage existing credential and network connection to get access to a PVS via User Plane to obtain new credential. + +To allow the UE to access the PNI-NPN providing access to the Localized Services where NSSAA or secondary authentication/authorization during PDU session establishment is required, the UE can obtain new credential using remote provisioning functionality as defined in clause 5.39. + +To allow the UE to access the HPLMN or subscribed SNPN services while being registered in the PNI-NPN or SNPN, the PNI-NPN or SNPN can establish service agreements and configure inter-connect with the HPLMN or subscribed SNPN operator. If a PNI-NPN is providing access to the Localized Services, the existing roaming architecture with home-routed PDU Sessions are used. If an SNPN is providing access to the Localized Services, then the UE can access HPLMN or subscribed SNPN as described in Annex D, clauses D.3, D.6 and D.7. + +### N.2.2 Configuration of network to provide access to Localized Services + +For configuring the PNI-NPN or SNPN (e.g. creation of network slice/DNN for carrying Localized Service traffic), existing OAM mechanisms can be re-used as per TS 28.557 [148] clause 6.3.1, that provides a solution for NPN provisioning by a network slice of a PLMN and for exposure of management capability of PNI-NPN (clause 6.3.2). The attributes to support this management is further documented in TS 28.541 [149]. + +### N.2.3 Session Management aspects + +For session management level information and interactions such as monitoring the PNI-NPN or SNPN performance, and enabling suitable QoS for UE in the PNI-NPN or SNPN for Localized Service, the following non-exhaustive options can be used: + +- Covered by the SLA between the PNI-NPN or SNPN operator and the Localized Service Provider. +- Reuse the existing network exposure procedures as specified in TS 23.502 [3] clause 4.15, where the Localized Service Provider is taking the AF role and utilizing the exposure capability provided by the PNI-NPN or SNPN. +- Enable NEF/PCF in the PNI-NPN or SNPN providing access to the Localized Services (via AF of the Localized Service Provider) to receive and forward the validity conditions and QoS requirements of the Localized Services to the AMF/SMF by reusing the existing PCF initiated AM/SM policy association procedures described in TS 23.502 [3] clause 4.16. + +## --- N.3 Selection of network providing access to Localized Services + +The UE selects an SNPN providing access for Localized Services as described in clause 5.30.2.4.2, clause 5.30.2.4.3 and in TS 23.122 [17]. + +## --- N.4 Enabling the UE access to Localized Services + +The access to a Localized Service is made available in a specific area and/or a specific period of time. + +After the UE has successfully registered to a PNI-NPN/SNPN providing access to the Localized Service, the UE can be configured with URSP rules using existing principles (see clause 6.6.2.2 of TS 23.503 [45]). + +The URSP rules can include an association between the UE application and the DNN/S-NSSAI which is meant for a particular Localized Service. The URSP rules can also include "Route Selection Validation Criteria" as described in Table 6.6.2.1-3 of TS 23.503 [45], with the time/location defined for the particular Localized Service. + +The existing LADN feature described in clause 5.6.5 can also be used for enabling the UE access to Localized Service which is defined by a LADN DNN. The S-NSSAI used for a Localized Service can be restricted to a specific area and time as described in clause 5.15. + +## --- N.5 Support for leaving network that provides access to Localized Services + +When Localized Services in a network are completed, all UEs that are registered with the network are expected to be transferred to other network or to other network resources (e.g. other cells) within the same network, potentially within a relatively short timeframe. The other network can be HPLMN, VPLMN or another SNPN. + +UE can stop using the network resources for Localized Services for numerous reasons, e.g. when one or more of the following conditions apply: + +- Localized Services in a network are completed. +- Validity conditions of network selection information are no longer met. +- The user decides to stop using the Localized Services before they are completed. +- A policy decision is taken by the network, with the effect that the UE is deregistered before the Localized Services are completed. + +NOTE: The list is not an exhaustive list and UE can stop using the network resources for Localized Services due to other reasons e.g. UE loses coverage, power off. + +When large number of UEs move to other network (i.e. HPLMN, VPLMN or another SNPN) or other network resources within a relatively short timeframe, the total signalling involved can cause signalling overload in the target network. + +Existing mechanisms for Control Plane Load Control, Congestion and Overload Control described in clause 5.19 and access control and barring described in clause 5.2.5 can be used to mitigate the signalling overload caused by returning UEs. For further enhancement of mitigation of signalling overload, additional mechanisms can be implemented to ensure spreading of the load that returning UEs cause. Such mechanisms are implementation-specific, but some guidelines that can be considered are described below: + +- The time validity of the network selection information given to a UE can be set somewhat longer than the actual duration of the service, e.g. users will by themselves disable Localized Service and the UE then stops using the connectivity to access the Localized Service, thus causing the UE to be moved, e.g. by performing normal network selection. +- The time validity of the network selection information given to a UE can be different for each UE so that each UE performs network selection at a different time to distribute returning UEs. +- When the AMF after end of Localized Services triggers deregistration of UEs, the deregistration requests can be sent at a certain rate in an adaptive and distributed manner, with the effect that the signalling load on both the source network and the target network is limited. +- When the AMF after end of Localized Services triggers UE configuration update procedure, e.g. to remove S-NSSAI from the Allowed NSSAI (if dedicated S-NSSAI is used for the Localized Service), the requests can be sent at a certain rate, with the effect that the signalling load in the network is limited. + +When the NAS level congestion control is activated at AMF as specified in clause 5.19.7.2, to prevent a UE staying in an SNPN for accessing for Localized Services but not able to get services from the SNPN due to the congestion, additional mechanism can be implemented. Such mechanisms are implementation-specific but some guidelines that can be considered are described below: + +- the AMF can determine whether to reject the UE with a proper cause without Mobility Management back-off timer to allow the UE to reselect another SNPN for Localized Services. + +## --- N.6 Configuration of Credentials Holder for determining SNPN selection information + +To enable the HPLMN or the subscribed SNPN acting as Credentials Holder to generate and provision UEs with SNPN selection information for discovery and selection of SNPNs providing Localized Services, based on Localized Service agreements between the Localized Service Provider or the SNPN providing Localized Services and the HPLMN or the subscribed SNPN acting as Credentials Holder, the Localized Service Provider or the SNPN providing access to Localized Services can provide configuration information for SNPN selection to the HPLMN or the subscribed SNPN acting as Credentials Holder. The configuration information for SNPN selection may contain at least one of the following parameters: + +- a. SNPN ID or GIN of the SNPN providing access to one or more Localized Services; +- b. Identification of each Localized Service; +- c. validity information for each Localized Service, e.g. the validity time information or/and location assistance information; and/or + +- d. List of UE IDs (e.g. GPSIs or External Group ID) identifying the UEs subscribed with a Localized Service. + +NOTE: How HPLMN or subscribed SNPN obtains the information above as part of the Localized Service agreements is out of 3GPP scope. + +The operator of the HPLMN or the subscribed SNPN acting as Credentials Holder then may use the information received from the SNPN providing Localized Services and/or Localized Service Provider to create or update the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services and provision the UEs using the Steering of Roaming procedure as defined in TS 23.122 [17]. + +# --- Annex O (informative): Allowing UE to simultaneously send data to different groups with different QoS policy + +This Annex provides deployment examples allowing a UE to simultaneously send data to different groups (i.e. IP or Ethernet multicast groups) with different QoS policy as in clause 6.13.2 of TS 22.261 [2]. + +## --- O.1 A PDU Session with multiple QoS Flows for different groups + +In case the UE Application sends individual copies of data to different receivers, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: + +- If different groups (IP or Ethernet multicast groups) are associated to the same DNN and S-NSSAI combination used for a 5G VN group, then different QoS Flows of a single PDU Session may be used to transfer the data copy sent to different groups. + +Figure O.1-1 shows a PDU Session with multiple QoS Flows for different groups as an example. + +- Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with 5GVN.A group. The QoS for multicast address 1 is set to QoS1. For G1, its members, multicast address 1 and corresponding QoS1 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. +- Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with 5GVN.A group. The QoS for multicast address 2 is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. +- During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.A group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.A group to set up the QoS flow in respective member's PDU Session. As a result: + - There will have two QoS flows in UE1's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, one QoS flow (QoS Flow 1.1) is used to carry data destined to multicast address 1 with QoS1, the other one (QoS Flow 1.2) is used to carry data destined to multicast address 2 with QoS2. + - There will have one QoS flow (QoS Flow 2) in UE2's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, this QoS flow is used to carry data destined to multicast address 1 with QoS1. + - There will have one QoS flow (QoS Flow 3) in UE3's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, this QoS flow is used to carry data destined to multicast address 2 with QoS2. +- UE1 sends data with multicast address 1 (MA.1) to the UPF via QoS Flow 1.1 of UE1's PDU session for 5GVN.A group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address 1 via QoS Flow 2 of UE2's PDU Session for 5GVN.A group. +- UE1 also sends the same data with multicast address 2 (MA.2) to the UPF via QoS Flow 1.2 of the same PDU Session for 5GVN.A group. The UPF forwards the packet to UE3 as it is a member of multicast group represented by multicast address 2 via QoS Flow 3 of UE3's PDU Session for 5GVN.A group. + +![Diagram of a PDU Session with multiple QoS Flows for different groups. UE1 sends data for MA.1 (QoS1) and MA.2 (QoS2) to the UPF. UE2 receives data for MA.1 (QoS1) from the UPF. UE3 receives data for MA.2 (QoS2) from the UPF. The UPF is connected to 5GVN.A. The diagram shows the flow of data from UE1 through the UPF to UE2 and UE3, with specific QoS flows identified for each multicast address.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +Diagram of a PDU Session with multiple QoS Flows for different groups. UE1 sends data for MA.1 (QoS1) and MA.2 (QoS2) to the UPF. UE2 receives data for MA.1 (QoS1) from the UPF. UE3 receives data for MA.2 (QoS2) from the UPF. The UPF is connected to 5GVN.A. The diagram shows the flow of data from UE1 through the UPF to UE2 and UE3, with specific QoS flows identified for each multicast address. + +Figure O.1-1: A PDU Session with multiple QoS Flows for different groups + +## 0.2 Multiple PDU Sessions for different groups + +In the case that the UE Application sends individual copies of data to different receivers, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: + +- If different groups (IP or Ethernet multicast groups) are associated to different DNN and S-NSSAI combinations used for different 5G VN groups, then different PDU Sessions are used to transfer the data copy sent to different groups. As a result, the UE sends the same data to different groups using the QoS Flow of the respective PDU Sessions. + +Figure O.2-1 shows multiple PDU sessions used for different groups as an example. + +- Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with 5GVN.1 group. The QoS for multicast address 1 is set to QoS1. For G1, its members, multicast address 1 and corresponding QoS1 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. +- Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with 5GVN.2 group. The QoS for multicast address 2 is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. +- During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.1 group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.1 group to set up the QoS flow in respective member's PDU Session. During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.2 group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.2 group to set up the QoS flow in respective member's PDU Session. As a result: + - There will have two PDU Sessions for UE1: one PDU Session is targeting to DNN and S-NSSAI for 5GVN.1 group and there will have one QoS flow setup to carry data destined to multicast address 1 with QoS1; the other PDU Session is targeting to DNN and S-NSSAI for 5GVN.2 group and there will have one QoS flow setup to carry data destined to multicast address 2 with QoS2. + - There will have one PDU Session for UE2: this PDU Session is targeting to DNN and S-NSSAI for 5GVN.1 group and there will have one QoS flow setup to carry data destined to multicast address 1 with QoS1. + - There will have one PDU Session for UE3: this PDU Session is targeting to DNN and S-NSSAI for 5GVN.2 group and there will have one QoS flow setup to carry data destined to multicast address 2 with QoS2. +- UE1 sends data with multicast address 1 (MA.1) to a UPF via the QoS Flow of UE1's PDU session for 5GVN.1 group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address 1 via the QoS Flow of UE2's PDU Session for 5GVN.1 group. +- UE1 also sends the same data with multicast address 2 (MA.2) to the UPF via the QoS Flow of UE1's PDU Session for 5GVN.2 group. The UPF forwards the packet to UE3 as it is a member of multicast group represented by multicast address 2 via the QoS Flow of UE3's PDU Session for 5GVN.2 group. + +![Diagram illustrating Multiple PDU Sessions for different groups. Three User Equipment (UE) units, UE1, UE2, and UE3, are shown on the left. UE1 has two multicast addresses, MA.1 and MA.2. MA.1 is associated with a PDU session labeled 'QoS1 for MA.1 /5GVN1' which connects to a Packet Data Network (PDR) labeled 'PDR MA.1'. MA.2 is associated with a PDU session labeled 'QoS2 for MA.2 /5GVN2' which connects to a PDR labeled 'PDR MA.2'. UE2 has MA.1 associated with a PDU session labeled 'QoS1 for MA.1 /5GVN.1' which connects to the 'PDR MA.1'. UE3 has MA.2 associated with a PDU session labeled 'QoS2 for MA.2 /5GVN.2' which connects to the 'PDR MA.2'. All three PDU sessions converge at a central UPF (User Plane Function). From the UPF, two dashed lines lead to two separate 5G Virtual Network (5GVN) groups, labeled '5GVN.1' and '5GVN.2'.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +Diagram illustrating Multiple PDU Sessions for different groups. Three User Equipment (UE) units, UE1, UE2, and UE3, are shown on the left. UE1 has two multicast addresses, MA.1 and MA.2. MA.1 is associated with a PDU session labeled 'QoS1 for MA.1 /5GVN1' which connects to a Packet Data Network (PDR) labeled 'PDR MA.1'. MA.2 is associated with a PDU session labeled 'QoS2 for MA.2 /5GVN2' which connects to a PDR labeled 'PDR MA.2'. UE2 has MA.1 associated with a PDU session labeled 'QoS1 for MA.1 /5GVN.1' which connects to the 'PDR MA.1'. UE3 has MA.2 associated with a PDU session labeled 'QoS2 for MA.2 /5GVN.2' which connects to the 'PDR MA.2'. All three PDU sessions converge at a central UPF (User Plane Function). From the UPF, two dashed lines lead to two separate 5G Virtual Network (5GVN) groups, labeled '5GVN.1' and '5GVN.2'. + +Figure O.2-1: Multiple PDU Sessions for different groups + +## O.3 A PDU Session targeting a predefined group formed of multiple sub-groups + +In the case when the UE Application uses IP or Ethernet multicast, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: + +- UE establishes a PDU Session to a DNN and S-NSSAI, which can be a special DNN and S-NSSAI configured by the operator for e.g. an electrical system. The DNN and S-NSSAI is associated with a 5GVN group, which is defined as a combination of multiple sub-groups (IP or Ethernet multicast groups). +- The 5G VN group and each sub-group is associated with a separate multicast address and QoS, the QoS for a 5G VN group is set to refer to the QoS of the sub-group that has the strictest QoS requirements among all the sub-group groups. When a UE belongs to multiple groups, the QoS provisioning for the groups needs to be done in the order that enables the the strictest QoS profile to be selected for the UE. For each group, its members, multicast address, corresponding QoS information, associated DNN and S-NSSAI are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. +- The application sends traffic to a multicast address depending on which group(s) it wants to target. For example, an application sends traffic to the multicast address associated with the 5G VN group. This allows an application to send a single packet reaching multiple destinations and also multiple groups. + +Figure O.3-1 shows a PDU Session targeting a predefined group formed of multiple sub-groups as an example. + +- Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with / mapped to 5GVN.1 group. The QoS for the group is set to QoS1. For G1, its members, multicast address 1, corresponding QoS1, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.1 group as described in clause 6.1.3.28 of TS 23.503 [45]. +- Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with / mapped to 5GVN.2 group. The QoS for the group is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.2 group as described in clause 6.1.3.28 of TS 23.503 [45]. +- GroupA (GA): a group of multicast address A with members UE1, UE2 and UE3 is associated with 5GVN.A group. G1 and G2 are combined to form the GA. The QoS for the 5GVN.A group is indicated to refer to the strictest QoS among other groups the UE belongs to. For GA, its members, multicast address A and corresponding QoS indication, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.A group as described in clause 6.1.3.28 of TS 23.503 [45]. +- During establishment or modification procedure for PDU Sessions targeting to the DNN and S-NSSAI, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information to set up the QoS flow in respective member's PDU Session. As a result: + - There will have two QoS flows in UE1's PDU Session targeting to DNN and S-NSSAI, one QoS flow is used to carry data destined to multicast address 1 with QoS1, the other one is used to carry data destined to multicast address 2 with QoS2. With the QoS indication for GA, the higher QoS between QoS1 of G1 and + +QoS2 of G2 is selected for UE1 since the UE1 belongs to both the G1 and G2, then the QoS flow with higher QoS requirements (QoS Flow 1) is also used to carry data destined to multicast address A. + +- There will have one QoS flow in UE2's PDU Session targeting to DNN and S-NSSAI, this QoS flow (QoS Flow 2) is used to carry data destined to multicast address 1 with QoS1. With the QoS indication for GA, the QoS1 of G1 is selected for UE1 since the UE2 only belongs to G1, then the same QoS flow is also used to carry data destined to multicast address A. +- There will have one QoS flow in UE3's PDU Session targeting to DNN and S-NSSAI, this QoS flow (QoS Flow 3) is used to carry data destined to multicast address 2 with QoS2. With the QoS indication for GA, the QoS2 of G2 is selected for UE3 since the UE3 only belongs to G2, then the same QoS flow is also used to carry data destined to multicast address A. +- UE1 sends data with multicast address A (MA.A) to a UPF via QoS Flow 1 of UE1's PDU Session for 5GVN.A group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address A (MA.A) via the QoS Flow 2 of UE2's PDU Session and forwards the packet to UE3 as it is a member of the multicast group represented by multicast address A (MA.A) via the QoS Flow 3 of UE3's PDU Session. + +![Diagram illustrating a PDU Session targeting a predefined group formed of multiple sub-groups. The diagram shows three User Equipment (UE) blocks: UE1, UE2, and UE3 on the left, and a UPF block on the right. UE1 is connected to the UPF via a flow labeled 'Max(QoS1 for group1, QoS2 for group2)'. UE2 is connected to the UPF via a flow labeled 'QoS1 for group 1'. UE3 is connected to the UPF via a flow labeled 'QoS2 for group 2'. All three flows are labeled with 'MA.A' at their respective UE ends. The UPF has a 'PDR MA.A' entry. To the right of the UPF is an oval labeled '5GVN.A'. Dashed arrows indicate data flow from the UPF's PDR to UE2 and UE3.](e1ce114c43dcefce51eadcd12f2da6d2_img.jpg) + +Diagram illustrating a PDU Session targeting a predefined group formed of multiple sub-groups. The diagram shows three User Equipment (UE) blocks: UE1, UE2, and UE3 on the left, and a UPF block on the right. UE1 is connected to the UPF via a flow labeled 'Max(QoS1 for group1, QoS2 for group2)'. UE2 is connected to the UPF via a flow labeled 'QoS1 for group 1'. UE3 is connected to the UPF via a flow labeled 'QoS2 for group 2'. All three flows are labeled with 'MA.A' at their respective UE ends. The UPF has a 'PDR MA.A' entry. To the right of the UPF is an oval labeled '5GVN.A'. Dashed arrows indicate data flow from the UPF's PDR to UE2 and UE3. + +Figure O.3-1: A PDU Session targeting a predefined group formed of multiple sub-groups + +# Annex P (informative): Personal IoT Networks + +## P.1 PIN Reference Architecture + +Figure P.1-1 shows the logical PIN reference architecture. + +![Figure P.1-1: PIN reference architecture diagram. The diagram shows the logical PIN reference architecture. On the left, a dashed circle labeled 'PIN' contains three elements: 'PINE', 'PEGC (UE)', and 'PEMC'. 'PINE' is connected to 'PEGC (UE)' and 'PEMC'. 'PEGC (UE)' is connected to 'AMF' via 'N1' and to 'PEMC' via a dashed line. 'PEMC' is connected to '(R)AN' via 'N2'. '(R)AN' is connected to 'UPF' via 'N3'. 'UPF' is connected to 'DN' (Data Network) via 'N6' and 'N9'. 'DN' contains an 'AF for PIN'. 'AMF' is connected to 'AUSF' via 'N15' and to 'SMF' via 'N4'. 'AUSF' is connected to 'UDR' via 'N16'. 'SMF' is connected to 'UPF' via 'N4'. Above the 'AMF', 'AUSF', 'SMF', and 'UDR' are 'NEF', 'NRF', 'PCF', and 'UDM'. 'NEF' is connected to 'AMF' via 'N5'. 'NRF' is connected to 'AMF', 'AUSF', 'SMF', and 'UDM'. 'PCF' is connected to 'AMF', 'AUSF', 'SMF', and 'UDM'. 'UDM' is connected to 'AMF', 'AUSF', 'SMF', and 'UDR'. 'UDR' is connected to 'AMF', 'AUSF', 'SMF', and 'UDM'.](691626a7032a642bb74793336c37e274_img.jpg) + +Figure P.1-1: PIN reference architecture diagram. The diagram shows the logical PIN reference architecture. On the left, a dashed circle labeled 'PIN' contains three elements: 'PINE', 'PEGC (UE)', and 'PEMC'. 'PINE' is connected to 'PEGC (UE)' and 'PEMC'. 'PEGC (UE)' is connected to 'AMF' via 'N1' and to 'PEMC' via a dashed line. 'PEMC' is connected to '(R)AN' via 'N2'. '(R)AN' is connected to 'UPF' via 'N3'. 'UPF' is connected to 'DN' (Data Network) via 'N6' and 'N9'. 'DN' contains an 'AF for PIN'. 'AMF' is connected to 'AUSF' via 'N15' and to 'SMF' via 'N4'. 'AUSF' is connected to 'UDR' via 'N16'. 'SMF' is connected to 'UPF' via 'N4'. Above the 'AMF', 'AUSF', 'SMF', and 'UDR' are 'NEF', 'NRF', 'PCF', and 'UDM'. 'NEF' is connected to 'AMF' via 'N5'. 'NRF' is connected to 'AMF', 'AUSF', 'SMF', and 'UDM'. 'PCF' is connected to 'AMF', 'AUSF', 'SMF', and 'UDM'. 'UDM' is connected to 'AMF', 'AUSF', 'SMF', and 'UDR'. 'UDR' is connected to 'AMF', 'AUSF', 'SMF', and 'UDM'. + +Figure P.1-1: PIN reference architecture + +A Personal IoT Network (PIN) in 5GC consists of one or more devices providing gateway/routing functionality known as the PIN Element with Gateway Capability (PEGC), and one or more devices providing PIN management functionality known as the PIN Element with Management Capability (PEMC) to manage the Personal IoT Network; and device(s) called the PIN Elements (PINE). A PINE can be a non-3GPP device. + +The PIN service can also have an AF for PIN (see TS 23.542 [181]). The AF can be deployed by mobile operator or by an authorized third party. When the AF is deployed by third party, the interworking with 5GS is performed via the NEF. + +With PIN-DN communication, the PEMC and PEGC communicates with the PIN Application Server at the application layer over the user plane. The PEGC and PEMC can communicate with each other via PIN direct communication using 3GPP access (e.g. PC5) or non-3GPP access (e.g. WiFi, BT) or via PIN indirect communication using a PDU Session in the 5GS. + +## P.2 Session management and traffic routing for PIN + +The general session management principles as described in clause 5.6, the QoS model as defined in clause 5.7 and the User Plane management for 5GS as defined in clause 5.8 are applicable to PIN-DN communication and PIN-indirect communication. + +If a PIN has multiple PEGC UEs, 5G VN group communication mechanisms can be used for PIN indirect communication (i.e. communication between PIN Elements belonging to the same PIN but served by different PEGC UEs). In this case a dedicated SMF set is used for managing the PIN related PDU Sessions from all the PEGCs of that PIN and the PDU session management principles for 5G VN-LAN-type services as specified in clause 5.29.3 are applicable. The user plane handling for 5G LAN-type services as specified in 5.29.4 are applicable with following differences: + +- For PIN indirect communication N19-based traffic forwarding is not used i.e. the PIN traffic is forwarded using: + - N6-based traffic forwarding method, where the UL/DL traffic for the PIN communication is forwarded to/from the DN; + - local switching as depicted in Figure P.2-1 below, following the principles of local switching of traffic for 5G VN LAN-type service. + +![Diagram of local-switch based user plane architecture for PIN. A dashed box labeled 'PIN' contains two PEGC UEs. PEGC UE1 is connected to three circles labeled PINE1, PINE2, and PINE3. PEGC UE2 is connected to three circles labeled PINE4, PINE5, and PINE6. Both PEGC UEs are connected to a box labeled '(R)AN'. From each '(R)AN', an arrow labeled 'N3' points to a dashed box labeled 'I-UPF'. From each 'I-UPF', an arrow labeled 'N9' points to a box labeled 'PSA UPF (local switch)'.](c0ca823603794512478906b302176bca_img.jpg) + +Diagram of local-switch based user plane architecture for PIN. A dashed box labeled 'PIN' contains two PEGC UEs. PEGC UE1 is connected to three circles labeled PINE1, PINE2, and PINE3. PEGC UE2 is connected to three circles labeled PINE4, PINE5, and PINE6. Both PEGC UEs are connected to a box labeled '(R)AN'. From each '(R)AN', an arrow labeled 'N3' points to a dashed box labeled 'I-UPF'. From each 'I-UPF', an arrow labeled 'N9' points to a box labeled 'PSA UPF (local switch)'. + +**Figure P.2-1: Local-switch based user plane architecture for PIN** + +NOTE: Figure P.2-1 does not show traffic from a PEMC. + +The SMF configures the UPF(s) to apply N6-based traffic forwarding to route traffic between PDU Sessions of different PEGC UEs of a PIN as specified in clause 5.8.2.13. The SMF can apply local switching as specified in clause 5.8.2.13 in order to enable UPF locally forward uplink stream from one PDU session of one PEGC UE of a PIN as downlink stream of PDU session of one or more PEGC UE(s) of the same PIN. For local switching of PIN traffic between PIN related PDU sessions from different PEGC UEs of a single PIN, based on the DNN and S-NSSAI that is used for the PDU session related to PIN, the SMF provides a Network Instance to the UPF in FAR and/or PDR via N4 Session Establishment/Modification procedures. + +# Annex Q (informative): Satellite coverage availability information + +The protocol and format of satellite coverage availability information to be provisioned to the UE via PDU session or SMS is not defined in this release of the specification, but this annex provides some examples on the information that constitutes input to the source of satellite coverage availability information e.g. external server and the output it provides to the UE. Satellite coverage availability information can be indicated to the UE by indications corresponding to whether or not coverage is available for a specific satellite RAT Type for a particular location and time, where: + +- These indications can be Boolean "True" (e.g. coverage available) and "False" (coverage not available); +- locations can correspond to grid points in a fixed array (e.g. rectangular, hexagonal); +- Coverage availability times may occur at fixed periodic intervals; and +- Coverage availability information is per RAT Type. The information provisioned to the UE can include coverage information on only one PLMN or multiple PLMNs. + +If Satellite coverage availability information indicates coverage is available then additional information on whether PLMN is allowed to operate in that location can be provided to the UE. + +In order for the source of satellite coverage availability information to provide accurate information to the UE, a UE might indicate for example the following information to a source of satellite coverage availability information (e.g. an external server): + +- Serving PLMN ID (if not already known or implied). +- One or more satellite RAT Types (where satellite coverage availability information is then expected for these one or more RAT Types). +- List of supported satellite frequency bands (if not implied by the particular RAT Types). +- Present UE location (e.g. latitude and longitude) for a reference grid point (e.g. the most Southerly and then most Westerly grid point). +- Type of Array (e.g. rectangular or hexagonal). +- Minimum elevation angle. + +Based on the above information provided by the UE, satellite coverage availability information could be delivered to the UE as a sequence of time durations for each grid point where each time duration includes an indication of coverage availability or unavailability one example of many alternatives as illustrated below for a particular grid point with N different durations: + +Satellite coverage availability information at a given grid point = . . . + +The above would be concatenated for all of the grid points to produce the satellite coverage availability information. + +When SMS is used to deliver the satellite coverage availability information, the UE input and satellite coverage availability information output can be delivered in a series of concatenated SMS messages using possibly the same format. + +# Annex R (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 06-2017 | SP#76 | SP-170384 | - | - | - | MCC Editorial Update for presentation to TSG SA#76 for Information | 1.0.0 | +| 12-2017 | SP#78 | - | - | - | - | MCC Editorial Update | 2.0.0 | +| 12-2017 | SP#78 | SP-170931 | - | - | - | Correction of Annex A figure numbers for presentation to TSG SA#78 for Approval | 2.0.1 | +| 12-2017 | SP#78 | - | - | - | - | MCC Editorial Update after TSG SA#78 Approval | 15.0.0 | +| 03-2018 | SP#79 | SP-180090 | 0002 | 2 | F | Using NRF for UPF discovery | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0003 | 2 | F | Configuration information the UE may exchange with the SMF during the lifetime of a PDU Session | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0004 | - | F | Handling of MM back-off timer for N3GPP Access | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0005 | - | F | Correction of the definitions of Allowed NSSAI and Configured NSSAI | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0006 | 4 | F | Allowed NSSAI and Access Type | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0007 | 1 | F | Correction to rejected S-NSSAI | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0008 | 2 | F | Corrections to Emergency Services | 15.1.0 | +| 03-2018 | SP#79 | SP-180096 | 0009 | - | D | Clarification of SUCI | 15.1.0 | +| 03-2018 | SP#79 | SP-180096 | 0010 | - | D | Miscellaneous editorial corrections (capitalization, messages, procedures etc.) | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0011 | - | F | Corrections to RQoS logic when receiving DL packet with RQI | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0013 | - | F | Paging Policy Differentiation correction | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0014 | - | F | Clarification on UE specific DRX parameter from old AMF to new AMF | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0015 | - | F | Clarification on PCF selection | 15.1.0 | +| 03-2018 | SP#79 | SP-180093 | 0016 | - | F | Adding the new clause about SMSF selection | 15.1.0 | +| 03-2018 | SP#79 | SP-180090 | 0017 | - | F | Use of identifiers for mobility between GERAN/UTRAN and 5GS | 15.1.0 | +| 03-2018 | SP#79 | SP-180090 | 0018 | 1 | F | Remaining IP address/prefix lifetime with SSC mode 3 | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0020 | 1 | F | Correction to handling of S-NSSAI mapping information | 15.1.0 | +| 03-2018 | SP#79 | SP-180090 | 0021 | 3 | F | Wildcard DNN subscription | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0022 | 4 | F | Clarification in LADN clause 5.6.5 - TS 23.501 | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0023 | - | F | Clean up on the interworking without 26 indication | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0024 | - | F | TS 23.501 mobility from EPC to 5GC | 15.1.0 | +| 03-2018 | SP#79 | SP-18009 | 0025 | 2 | F | AMF Load Re-Balancing For CONNECTED mode UE | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0026 | - | F | Update on Traffic Detection Information | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0027 | - | F | Proposal of Specifying Packet Detection Rule | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0028 | 1 | F | Relation between the SSC mode 3 and the PDU type | 15.1.0 | +| 03-2018 | SP#79 | SP-180091 | 0031 | - | F | UE-specific DRX parameter negotiation between UE and AMF | 15.1.0 | +| 03-2018 | SP#79 | SP-180091 | 0033 | - | F | Control of the Messages triggering Paging at AMF | 15.1.0 | +| 03-2018 | SP#79 | SP-180091 | 0034 | 2 | F | Alignment with TS 23.502 on Service Request procedure | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0035 | - | F | Corrections and clarifications for the usage of Packet Filter Set | 15.1.0 | +| 03-2018 | SP#79 | SP-180091 | 0036 | - | F | Update Paging Policy Differentiation | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0037 | 1 | F | Correction to AF influence on traffic routing | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0038 | - | F | Clarifications to AF influence on traffic routing | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0039 | - | F | Clarify NSSF discovery | 15.1.0 | +| 03-2018 | SP#79 | SP-180090 | 0040 | 1 | F | Change subscribed S-NSSAI in UE to configured NSSAI of HPLMN | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0041 | 1 | F | UDM discovery clarifications | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0044 | - | F | Corrections to UPF selection and resolution of related Editor's Note | 15.1.0 | +| 03-2018 | SP#79 | SP-180097 | 0045 | 1 | F | Updates to the Security Edge Protection Proxy description | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0046 | - | F | Homogeneous support for IMS voice over PS Session supported indication | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0047 | 1 | F | Slice selection cleanup | 15.1.0 | +| 03-2018 | SP#79 | SP-180091 | 0048 | - | F | Resource reservation for services sharing priority | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0049 | - | F | Replace PUI with GPSI | 15.1.0 | +| 03-2018 | SP#79 | SP-180091 | 0050 | - | F | Idle and connected state terminology cleanup | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0051 | - | F | NAS congestion control update | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0052 | - | F | Complete of IMS Emergency support in 5G including slice and local numbers | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0053 | 1 | F | Traffic mapping information that disallows UL packets | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0054 | 1 | F | Clean-up of Characteristics signalling | 15.1.0 | +| 03-2018 | SP#79 | SP-180093 | 0055 | - | F | EPS Fallback for voice | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0056 | 1 | F | Network sharing prioritised PLMN handling | 15.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| 03-2018 | SP#79 | SP-180098 | 0057 | 2 | F | Corrections to Combined N3IWF/ePDG Selection | 15.1.0 | +| 03-2018 | SP#79 | SP-180091 | 0058 | 1 | F | Moving Network Analytics functionality into 23.501 | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0061 | 1 | F | Clarification on UDR | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0062 | - | F | QFI in N9 | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0063 | 1 | F | NF Service Discovery Corrections | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0064 | 3 | F | UE mobility event notification | 15.1.0 | +| 03-2018 | SP#79 | SP-180092 | 0066 | 4 | C | Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0068 | - | F | CN assistance information enhancement | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0070 | - | F | Inter-PLMN mobility when N26 is not used | 15.1.0 | +| 03-2018 | SP#79 | SP-180093 | 0071 | 3 | F | Interworking without N26 corrections | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0072 | 1 | F | Clarification for S-NSSAI based congestion Control | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0073 | - | F | Non-roaming Architecture for Network Exposure Function in reference point representation | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0074 | 1 | F | NSSF service update | 15.1.0 | +| 03-2018 | SP#79 | SP-180092 | 0075 | 1 | F | Correcting the support of charging Characteristics | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0076 | - | F | Non-Allowed Area as criterion for Cell Reselection or trigger for PLMN Selection | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0077 | 1 | F | Correction to the use of Redirection in EPS fallback for emergency services | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0078 | 2 | F | Network Provided Location for non-3GPP access | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0082 | 1 | F | Updates to TS 23.501 Scope | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0083 | 1 | F | Fixes for CP protocol stack | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0084 | 1 | F | EPC to 5GC Migration fixes for Option 7 | 15.1.0 | +| 03-2018 | SP#79 | SP-180098 | 0085 | 1 | F | EPS Interworking: 5G-S-TMSI derivation and context retrieval | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0086 | 1 | F | Fixes for Emergency Services and Emergency Services using Fallback | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0087 | 2 | F | 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0088 | 4 | F | QoS Notification control and Release | 15.1.0 | +| 03-2018 | SP#79 | SP-180095 | 0089 | 4 | C | GUTI unique across AMFs in an AMF SET | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0090 | 1 | F | Partitioning of Identifier space to ensure success of Context retrieval for EPS Interworking | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0091 | 1 | F | UDM Discovery with SUPI as input | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0095 | 5 | F | Clarifications of Subscribed and Configured S-NSSAI update | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0102 | 4 | F | Sending of congested S-NSSAI during AN signalling connection Establishment | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0104 | 3 | F | Clarification on modification of the set of network slices for a UE | 15.1.0 | +| 03-2018 | SP#79 | SP-180092 | 0105 | 1 | F | UE support for Multi-homed IPv6 PDU Session | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0106 | 1 | F | 5GS support for network slicing | 15.1.0 | +| 03-2018 | SP#79 | SP-180093 | 0107 | 2 | F | UE Core Network Capability handling | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0108 | - | F | eCall over IMS supported over E-UTRA only | 15.1.0 | +| 03-2018 | SP#79 | SP-180090 | 0109 | 2 | F | Domain selection for UE in Dual Registration mode | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0110 | 2 | F | MICO and interworking with EPC | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0115 | 2 | F | Correction of NSSAI handling | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0116 | 1 | F | Slice Availability update | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0122 | 2 | F | User Plane management to support interworking with EPS | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0124 | 3 | F | Supporting Common API framework for NEF | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0126 | 1 | F | Clarification on NAS recovery procedure in RRC Inactive | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0129 | 2 | F | Correction for congestion control | 15.1.0 | +| 03-2018 | SP#79 | SP-180096 | 0133 | - | D | Correction for the usage of RQI bit | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0134 | 5 | F | Clarifications for QoS Framework | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0135 | 2 | F | DL signalling handling for non-3GPP PDU Session | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0136 | 1 | F | Clarification on location reporting for LADN in RRC Inactive clause 5.3.3.2.5 - TS 23.501 | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0137 | 2 | F | Network Sharing and Interworking with EPS- TS 23.501 | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0138 | - | F | Edge Computing Clarification | 15.1.0 | +| 03-2018 | SP#79 | SP-180095 | 0141 | 1 | B | Supporting 3GPP PS Data Off in 5GS | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0144 | 2 | F | Management of service area restriction information | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0145 | 2 | F | Clarification on TAI list assignment for different 5G RATs | 15.1.0 | +| 03-2018 | SP#79 | SP-180099 | 0146 | - | F | Network sharing for supporting RRC redirection procedure | 15.1.0 | +| 03-2018 | SP#79 | SP-180095 | 0147 | 2 | C | Selection of NAS procedures for E-UTRA connected to both EPC and 5GC | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0149 | 1 | F | Clarification of SM congestion control | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0150 | 1 | F | Updates to AF influence on traffic routing | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0151 | 2 | F | Updates to description of CN Tunnel Info | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0152 | - | F | Clarification on RRM description | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0153 | 1 | F | Editorial corrections in clause 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0154 | 2 | F | Clarification on the association of an S-NSSAI to a given application | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0155 | 2 | F | Update of UE Network slicing configuration | 15.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| 03-2018 | SP#79 | SP-180100 | 0157 | 2 | F | SBA Scope Clarification | 15.1.0 | +| 03-2018 | SP#79 | SP-180092 | 0158 | 2 | F | Clean up for BSF | 15.1.0 | +| 03-2018 | SP#79 | SP-180092 | 0160 | 3 | F | Clarification on Area of Interest for Presence Area Reporting | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0161 | 3 | F | Correction to Providing AF request to multiple PCFs | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0165 | 1 | F | Usage of Unified access control in priority mechanisms | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0166 | - | F | Update Roaming reference architectures | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0168 | 5 | F | Clarification of UE Requested NSSAI | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0170 | 1 | F | Emergency Services Support indication per RAT | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0171 | 2 | F | N4 User Plane Path | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0173 | 1 | F | SSC Mode Selection | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0174 | 2 | F | Proposal of QER, URR and FAR | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0177 | 1 | F | UE specific DRX parameters for CM-CONNECTED with Inactive state | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0179 | 6 | F | Slicing configuration update | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0180 | 1 | F | Update of Mobility Restrictions | 15.1.0 | +| 03-2018 | SP#79 | SP-180125 | 0181 | 1 | B | Addition of PDU Session type IPv4v6 | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0183 | 1 | F | Mapping of Requested NSSAI clarification | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0184 | 2 | F | Clarification of the interworking between 5G and GERAN/UTRAN/E-UTRAN when UE is in RRC-inactive state | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0187 | 5 | F | Select the same SMF+UPF for PDU sessions of the same DNN within one slice | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0189 | 2 | F | Subscription Permanent Identifier | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0192 | 1 | F | Clarification of interworking procedures without N26 interface | 15.1.0 | +| 03-2018 | SP#79 | SP-180100 | 0194 | 1 | F | Clarification on the use of the indicator for the support of interworking without N26 | 15.1.0 | +| 06-2018 | SP#80 | SP-180482 | 0067 | 6 | F | Controlled support of (AF) session binding for Ethernet PDU Session Type | 15.2.0 | +| 06-2018 | SP#80 | SP-180491 | 0117 | 7 | F | Use of Priority parameters for scheduling | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0169 | 8 | F | Temporary restriction of Reflective QoS | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0196 | 1 | F | 5_16_6_Mission Critical Services - Reference Update | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0197 | 1 | F | 5_16_6_Mission Critical Services - Editorial Changes | 15.2.0 | +| 06-2018 | SP#80 | SP-180477 | 0198 | - | D | Fixing Incorrect References to the Service Request Procedures | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0199 | 2 | F | SUPI based paging | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0201 | 2 | F | Mobile Terminated SMS over NAS: 5GS Access Selection | 15.2.0 | +| 06-2018 | SP#80 | SP-180483 | 0203 | 1 | F | Discovery and Topology Hiding | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0206 | 3 | F | Changed length and mapping of 5GS Temporary Identifiers | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0207 | 5 | F | Slice configuration change | 15.2.0 | +| 06-2018 | SP#80 | SP-180483 | 0209 | 1 | F | Defining NWDAF in 23.501 | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0210 | 3 | F | Corrections to PFD management | 15.2.0 | +| 06-2018 | SP#80 | SP-180491 | 0212 | 2 | F | Update on UE mobility event notification | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0214 | 1 | F | Identification and update of UE derived QoS rule | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0216 | 2 | F | Clarification of traffic steering control in the case of interworking | 15.2.0 | +| 06-2018 | SP#80 | SP-180491 | 0217 | 2 | F | Updates to System Enablers for Priority Mechanism | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0219 | 2 | F | AMF Selection aspects | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0220 | 1 | F | AMF functionality clarification - to add SUCI | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0222 | 1 | F | EPS Interworking Principles - SR mode with N26 | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0224 | 1 | F | UDM services - addition to Nudm_UEAuthentication | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0225 | 0 | F | UDM functionality support for SUCI | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0226 | 3 | F | MFBR Enforcement for GBR QoS Flows | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0227 | 1 | F | NF Registration via the NRF | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0229 | - | F | Abbreviations supplement | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0231 | 1 | F | 3GPP PS Data Off Clarification | 15.2.0 | +| 06-2018 | SP#80 | SP-180477 | 0232 | - | D | Network Sharing and Interworking Clarification | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0237 | 3 | F | Clarification on MT SMS domain selection by SMSF | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0239 | 1 | F | TS 23.501: Clean-up for the RRC Inactive related procedure | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0240 | - | F | Correction on Control Plane protocol stacks | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0241 | 2 | F | Clarification on NSSAI related functionality in 5G RAN | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0242 | 2 | F | Clarification on Application data | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0244 | 3 | F | AMF UE area of interest reporting in RRC inactive state | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0245 | - | F | Clarification on RAT fallback | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0248 | 1 | F | Clarification on notification message | 15.2.0 | +| 06-2018 | SP#80 | SP-180477 | 0250 | - | D | Editorial correction in clause 5.9.2 Subscription Permanent Identifier | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0251 | 8 | F | Correction to DNN subscription | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0254 | 4 | F | Clarification on the support of Delay Critical resource type | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0255 | 7 | F | Network slicing clause cleanup | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0261 | 1 | F | UE and network shall override the Core Network type restriction for regulatory prioritized services | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0262 | 1 | F | Clarification to the usage of Internal-Group Identifier | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0264 | 5 | F | Different types of Ethernet services and N4 | 15.2.0 | +| 06-2018 | SP#80 | SP-180487 | 0265 | 3 | F | Providing AF with information on the N6 User Plane tunnelling information | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------------------------|--------| +| 06-2018 | SP#80 | SP-180488 | 0266 | 4 | F | SMF getting UE location from the AMF for NPLI when no QoS Flow to create/Update/modify | 15.2.0 | +| 06-2018 | SP#80 | SP-180487 | 0267 | - | F | Removal of network restriction for eight concurrent S-NSSAIs when serving a UE | 15.2.0 | +| 06-2018 | SP#80 | SP-180487 | 0268 | - | F | Removal of duplicated requirements for Allowed/Configured NSSAI | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0269 | 2 | F | Correction to AMF and S-NSSAI overload control | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0270 | - | F | AMF Name and AMF N2AP UE ID | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0271 | 2 | F | Correction for support of the Ethernet Type PDU Session | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0272 | 1 | F | Correction on aspects for LADN | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0273 | 1 | F | Subscription status notification for Event Exposure service | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0275 | 1 | F | Clarification on SMF selection | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0276 | 2 | F | Clarification on SMSF selection | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0280 | 1 | F | Update for providing policy requirements to multiple UEs | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0282 | 2 | F | Clarifying handling of reachability state | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0283 | 6 | F | Dual Registration mode of operation from E-UTRA cell connecting to both EPC and 5GC | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0284 | 2 | F | Consolidation of UE Network Capabilities | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0285 | 1 | F | NAS level congestion control for emergency and high priority access | 15.2.0 | +| 06-2018 | SP#80 | SP-180476 | 0286 | 1 | C | Coexistence of RRC Inactive and Dual Connectivity | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0287 | 3 | F | Mapped parameters in case of No N26 | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0289 | 2 | F | Clarification on the use of shared AMF Pointer value | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0290 | 1 | F | ReAuthentication by an external DN-AAA server | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0292 | 6 | F | LADN configuration of UE | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0295 | 1 | F | Clarification of S-NSSAI based congestion control | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0296 | 4 | F | Add indication of Notification Control to QoS rules sent to UE | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0297 | 1 | F | Local deactivate MICO for emergency service | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0298 | 4 | F | How the SMF validates UE location when requested for LADN PDU Session establishment | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0302 | 1 | F | AUSF clarification and alignment | 15.2.0 | +| 06-2018 | SP#80 | SP-180477 | 0303 | - | D | Correction to references | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0304 | 3 | F | Clarification on N3GPP TAI | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0305 | 6 | F | Correction on capability negotiation on "SMS over NAS" | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0306 | 1 | F | Alignment of the name of the network function | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0308 | 3 | F | Correction on NAS level congestion control | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0310 | 2 | F | Clarification on AMF management | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0311 | 4 | F | S-NSSAI check for activation of UP connection of PDU Session | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0313 | 3 | F | Clarifications required resulting from 6-bit QFI limit | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0314 | 1 | F | Missing "redirection" to E-UTRA connected to 5GC | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0319 | 1 | F | Clarification of high priority access | 15.2.0 | +| 06-2018 | SP#80 | SP-180476 | 0323 | 3 | F | Dual connectivity support for network slices | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0325 | - | F | Clarification to the NRF Roaming architecture | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0326 | 2 | F | Slicing information and RFSP | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0327 | - | F | TS 23.501: UE DL Signalling handling in RRC Inactive State | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0331 | 1 | F | Some TADs fix's | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0334 | 1 | F | Handling of maximum supported data rate per UE for integrity protection | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0335 | - | F | NF/NF service registration and status subscribe/notify description updates | 15.2.0 | +| 06-2018 | SP#80 | SP-180491 | 0336 | 1 | F | Use of results of NF/NF service discovery for NF/NF service selection | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0338 | 4 | F | Subscribed SMSF address | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0339 | - | F | SEPP fully redundant and next-hop IPX proxy | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0342 | 1 | F | SMF selection factor | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0344 | - | F | IPsec SAs in tunnel mode | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0345 | 1 | F | Determining interworking support for PDU sessions in case of interworking without N26 | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0346 | 1 | F | Fixing the definition of signalled QoS rule | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0349 | 2 | F | Clarify GUTI aspects for single-registration mode UEs for interworking without N26 | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0351 | - | F | N9 missing in some figures | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0352 | 2 | F | NF instance and NF service instance definitions | 15.2.0 | +| 06-2018 | SP#80 | SP-180483 | 0353 | 2 | F | Correction to UE Radio Capability handling | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0355 | 1 | F | Further QoS clean-up | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0356 | 1 | F | Coordination of reference point allocation | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0359 | 2 | F | Handling of Configured NSSAIs in Roaming Scenarios - 23.501 | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0363 | 1 | F | Update and correction of table for AMF, UDM, UDR, NSSF, UDSF and BSF services | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0365 | 1 | F | Update of FAR | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0367 | 1 | F | NEF Services | 15.2.0 | +| 06-2018 | SP#80 | SP-180477 | 0368 | 2 | D | Editor's note clean-up | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------------------------|--------| +| 06-2018 | SP#80 | SP-180482 | 0370 | 3 | F | Compute - Storage split principles | 15.2.0 | +| 06-2018 | SP#80 | SP-180484 | 0371 | - | F | Emergency Services Fallback Support indicator validity in the Registration Area | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0372 | - | F | LMF Services | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0375 | 2 | F | UDM-AUSF Discovery | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0383 | 2 | F | Clarification on usage of PLMN ID received via PCO during PDN connection establishment | 15.2.0 | +| 06-2018 | SP#80 | SP-180483 | 0385 | - | F | Correction to the mapping to the Subscribed S-NSSAI(s) | 15.2.0 | +| 06-2018 | SP#80 | SP-180487 | 0386 | 2 | F | Provisioning NSSP | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0389 | 1 | F | Tracking Area in 5GS | 15.2.0 | +| 06-2018 | SP#80 | SP-180483 | 0390 | 1 | F | Correction to S-NSSAI congestion | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0391 | 1 | F | Clarification to PDU Session Types: MTU | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0394 | 3 | F | Alignment of radio capabilities procedure | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0396 | 2 | F | CN type indicator in AS signalling | 15.2.0 | +| 06-2018 | SP#80 | SP-180483 | 0397 | 1 | F | Correction to eCall Support by NR | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0398 | 1 | F | Bit rate enforcement | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0399 | - | F | Clarification on TAC format at inter-system handover | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0401 | 1 | F | Add table of CHF Spending Limit Control service in 7.2.x | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0402 | 2 | F | S-NSSAI of VPLMN when HO from 4G to 5G | 15.2.0 | +| 06-2018 | SP#80 | SP-180489 | 0403 | - | F | SSC Mode Selection clarification | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0404 | 1 | F | How Peer CP NF sends notification to target/new AMF after AMF planned removal | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0405 | 1 | F | AF influence on traffic routing for Ethernet type PDU Session | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0406 | 2 | F | Avoid the case the one UE MAC shared by multiple Ethernet PDU Sessions | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0407 | 1 | F | How AMF provides LADN Information to UE | 15.2.0 | +| 06-2018 | SP#80 | SP-180477 | 0410 | - | D | Non-3GPP access node selection information | 15.2.0 | +| 06-2018 | SP#80 | SP-180496 | 0411 | - | F | Clarify RAT restrictions are not provided to the UE | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0414 | 1 | F | Including GUAMI in RRC message of related procedures | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0415 | 1 | F | Clarification on CN assistance information | 15.2.0 | +| 06-2018 | SP#80 | SP-180481 | 0416 | 2 | F | Clarify the relationship between GFBR and MDBV | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0417 | 2 | F | Clarification on support of MFBR greater than GFBR | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0418 | 1 | F | Clarification on requested NSSAI usage by RAN | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0422 | - | F | Clarification on SMSF checking subscription data | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0423 | - | F | S-NSSAI back off timer for UE requested PDU session release | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0424 | 2 | F | Clarification on AF influence on traffic routing | 15.2.0 | +| 06-2018 | SP#80 | SP-180482 | 0425 | 2 | F | Combined SMF+PGW-C Selection | 15.2.0 | +| 06-2018 | SP#80 | SP-180488 | 0430 | - | F | Resume procedure in the equivalent PLMN | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0433 | - | F | Alignment of selective activation of UP connection of existing PDU Session | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0435 | 1 | F | Alignment of PCF selection description | 15.2.0 | +| 06-2018 | SP#80 | SP-180487 | 0436 | 4 | F | QNC during Handover | 15.2.0 | +| 06-2018 | SP#80 | SP-180487 | 0437 | 3 | F | Reflective QoS in interworking | 15.2.0 | +| 06-2018 | SP#80 | SP-180491 | 0438 | 2 | F | Use of Network Instance | 15.2.0 | +| 06-2018 | SP#80 | SP-180490 | 0439 | 3 | F | Update of N4 Parameter Descriptions and Tables | 15.2.0 | +| 06-2018 | SP#80 | SP-180480 | 0441 | 3 | F | Clarification on LADN 5.6.5 | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0444 | 3 | F | Network slicing subscription change and update of UE configuration | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0446 | 2 | F | Clarification note on Network Slice limitation | 15.2.0 | +| 06-2018 | SP#80 | SP-180478 | 0447 | 1 | F | Adding default value for Averaging Window | 15.2.0 | +| 06-2018 | SP#80 | SP-180486 | 0448 | 1 | F | Mobility restrictions | 15.2.0 | +| 06-2018 | SP#80 | SP-180479 | 0451 | 2 | F | Capturing subsequent mobility to and from GERAN/UTRAN | 15.2.0 | +| 06-2018 | SP#80 | SP-180485 | 0453 | - | F | GFBR is applicable only for GBR QoS Flows | 15.2.0 | +| 06-2018 | SP#80 | SP-180556 | 0454 | 2 | F | NSSAI handling in PDU Session Establishment procedures in roaming | 15.2.0 | +| 06-2018 | SP#80 | SP-180483 | 0456 | 1 | F | Correction to identifiers in Registration procedure | 15.2.0 | +| 06-2018 | SP#80 | SP-180487 | 0459 | 1 | F | Radio capabilities after 5GS registration | 15.2.0 | +| 09-2018 | SP#81 | SP-180713 | 0455 | 3 | F | Storage of structured proprietary data in UDSF | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0460 | 3 | F | Missing TADs behaviour | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0463 | - | F | Correcting handling of RAT restriction and Forbidden Areas | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0464 | 3 | F | Clarification on LADN | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0465 | 3 | F | Clarification on a wildcard DNN | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0466 | 3 | F | Correcting use of identifiers during registration in equivalent PLMNs | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0470 | 1 | F | Clarification on UE context exchanged on N26 interface | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0471 | 1 | F | Correction to AF influence on traffic routing | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0472 | 2 | F | Clarification on UE Registration type with only PDU Session for Emergency Services | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0473 | 7 | F | The resource type of QoS Flow associated with the default QoS rule | 15.3.0 | +| 09-2018 | SP#81 | SP-180724 | 0474 | 5 | B | Support of tracing in 5GS signalling: overview | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0475 | - | F | MCC implementation correction of 23.501 CR0255R7 | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0480 | 3 | F | 5QI-QCI alignment | 15.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------|--------| +| 09-2018 | SP#81 | SP-180713 | 0481 | 2 | F | Number of packet filters supported by UE | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0482 | 2 | F | Paging policy differentiation for RRC inactive | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0485 | 4 | F | Application detection report when the PFDs are removed | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0487 | 5 | F | Correction to Configured NSSAI for the HPLMN | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0488 | 1 | F | Correction to TAI list generation | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0493 | 1 | F | Network Exposure in Roaming Situations | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0494 | 1 | F | Handling of UP Security Policy when IWK with EPS | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0497 | 2 | F | Clarification on handling of Ethernet frames at UPF | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0498 | 4 | F | Completion of description on Configured NSSAIs | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0499 | - | F | LADN Clarification | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0500 | 1 | F | DNN Usage Clarification | 15.3.0 | +| 09-2018 | SP#81 | SP-180713 | 0501 | 4 | F | Clarification for pre-configured QoS rule | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0502 | 1 | F | Clarification for QoS handling at UPF | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0504 | 3 | F | DL signalling handling for non-3GPP PDU Session | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0508 | 2 | F | Emergency call and eCall support when the ng-eNode is connected to EPC and 5GC | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0509 | 1 | F | Mobility Restriction List clean up | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0515 | 1 | F | Subscription of selecting the same SMF and UPF | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0516 | 3 | F | GUAMI Definition Correction | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0518 | 1 | F | Merging Network Slice with regular EPS Interworking | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0520 | 2 | F | Notification Control applicability | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0521 | 1 | F | 23.501: 5G AN Parameters sent during Service Request | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0524 | - | F | Null interworking with GERAN/UTRAN CS domain | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0525 | - | F | Correction on mobility management back-off timer | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0527 | - | F | 5G-TMSI should map to M-TMSI | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0529 | 1 | F | Clarification on Homogeneous Support of IMS Voice over PS Sessions indication | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0530 | 3 | F | Clarification on the non-IP PDU session type for EPS to 5GS interworking | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0531 | 2 | F | Clarification on the PDU session handling in EPS to 5GS handover with N26 | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0532 | 1 | F | Incorrect text implying slicing is optional | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0533 | - | F | Update of SMSF selection function | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0534 | 1 | F | Corrections to NF profile description | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0535 | 1 | F | Corrections to NF services names and references | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0536 | - | F | Update on AUSF service operation to support Steering of Roaming | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0538 | 3 | F | Correction to interworking with EPC with N3GPP PDU Sessions | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0539 | 3 | F | Emergency Services Support indicator for non-3GPP access | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0540 | 1 | F | Clarification of the AMF Set definition | 15.3.0 | +| 09-2018 | SP#81 | SP-180714 | 0542 | 1 | F | Clarification on priority service | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0543 | 1 | F | Unified Access Control for UE configured for EAB | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0544 | 2 | F | UE configuration of NSSAI and associated mapping | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0545 | - | F | Corrections to NEF functionalities description | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0546 | 2 | F | Update of N4 Parameter Descriptions and Tables/ Ethernet PDU Session Type | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0547 | 1 | F | Miscellaneous Corrections to SM specifications (SSC mode, PCFP reference, etc.) | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0548 | 2 | F | Specify AUSF selection by UDM | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0551 | - | F | Obsolete reference to Lawful Interception specifications | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0555 | 2 | F | Clearification on UE's configuration update | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0558 | 2 | F | Corrections to AF influence (5.6.7) based on CT WG3 LS on AF influence on traffic routing | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0559 | 2 | F | Alignment with CT WG1 on the QoS Flow Description | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0562 | - | F | UDM procedures in EPS-5GS interworking without N26 | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0563 | - | F | Update of NEF service table (7.2.8) for Chargeable party and AFsessionWithQoS | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0564 | 1 | F | Radio Capabilities for DRM in emergency services | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0565 | 3 | F | Selection of S-NSSAIs used in the Requested NSSAI | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0566 | 3 | F | Temporary identifier usage at interworking | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0567 | 1 | F | Temporary identifier coordination | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0569 | 1 | F | Updating radio capabilities from RRC_Inactive | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0573 | 1 | F | SMS support used in different meanings | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0575 | - | F | Exposure function reference correction | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0583 | 3 | F | Consistent Description of 5QI | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0584 | - | F | Corrections to N4 and UP tunnel protocol descriptions | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0585 | 1 | F | Handling of pending DL NAS signalling (related to LS In S2-187632) | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0586 | - | F | Alignment of Slice Selection logic in the AMF and NSSF | 15.3.0 | +| 09-2018 | SP#81 | SP-180715 | 0587 | 3 | F | Missing requirements to trigger Notification Control | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0588 | 2 | F | OAuth2 Authorization Service | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0589 | 2 | F | Clarification of the service area restriction and NSSAIs to EPLMNs | 15.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|-----------------------------------------------------------------------------------------------------|--------| +| 09-2018 | SP#81 | SP-180716 | 0591 | 1 | F | 23.501: Reference Point and Services correction | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0592 | 1 | F | 23.501: UDM Services | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0593 | 2 | F | 23.501: Subscription for EPS IWK | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0594 | - | F | 23.501: AUSF, UDM, UDR Discovery | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0595 | 2 | F | Voice centric UE behaviour in non-allowed area | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0597 | 5 | F | Update to PCF discovery and selection | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0598 | 3 | F | Clarification to IMS emergency procedure | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0604 | 1 | F | Clarification on reporting of PS Data Off status change | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0605 | 4 | F | TAI List provision to RAN by AMF for RRC Inactive UE | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0606 | 2 | F | Clarifications for signalled QoS characteristics | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0608 | 1 | F | IPv6 multi-homed routing rule | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0609 | 1 | F | Clarification on priority of URSP and configuration of association between application and LADN DNN | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0616 | 2 | F | Update N4 principles and parameters | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0617 | - | F | Clarification on NF profile parameters | 15.3.0 | +| 09-2018 | SP#81 | SP-180716 | 0618 | - | F | Update to service area restriction | 15.3.0 | +| 09-2018 | SP#81 | SP-180791 | 0611 | 3 | F | Clarification on the AMF store the DNN and PGW-C+SMF to UDM/HSS without N26. | 15.3.0 | +| 2018-12 | SP#82 | SP-181084 | 0576 | 6 | F | CHF discovery and selection | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0590 | 2 | F | Clarification to the slice based congestion control handling at NG-RAN | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0607 | 11 | F | Clarifications for 5QI priority level | 15.4.0 | +| 2018-12 | SP#82 | SP-181090 | 0621 | 2 | F | Using preconfigured 5QI for QoS Flow associated with the default QoS rule | 15.4.0 | +| 2018-12 | SP#82 | SP-181090 | 0622 | 3 | F | Update of Default Configured NSSAI | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0625 | 2 | F | Clarifying the boundaries of an NF instance | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0626 | - | F | Correcting discovery and selection | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0628 | 3 | F | Reporting PS Data Off status change when SM back off timer is running | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0629 | 1 | F | Correction of the indication of UE 5GSM capabilities after intersystem change | 15.4.0 | +| 2018-12 | SP#82 | SP-181090 | 0630 | 1 | F | UE unable to use N3IWF identifier configuration in stand-alone N3IWF selection | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0633 | 2 | F | Removal of Editor's Note re mandatoriness of RRC Inactive | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0634 | 3 | F | Avoiding mandatory MME impacts from 3-byte TAC | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0637 | 1 | F | Alignment of NF Profile with adding priority parameter | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0638 | 2 | F | Clarification on RQ Timer | 15.4.0 | +| 2018-12 | SP#82 | SP-181088 | 0639 | 2 | F | Interactions with PCF - Updates to reference architecture for interworking | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0641 | 1 | F | Registration Area and Service Restriction Area in relation to multiple PLMNs | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0645 | 1 | F | Correcting the interaction needed for the NSSF service | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0648 | - | F | Connections on Default Configured NSSAI | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0651 | 1 | F | Correction and clarification for CM-CONNECTED with RRC Inactive state | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0653 | 2 | F | SUPI definition and NAI format | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0655 | 1 | F | Addition of abbreviations | 15.4.0 | +| 2018-12 | SP#82 | SP-181088 | 0656 | 8 | F | Network controlled NSSAI for SR-related Access Stratum connection establishment | 15.4.0 | +| 2018-12 | SP#82 | SP-181195 | 0660 | 8 | F | Unified Access Control clarification and triggers | 15.4.0 | +| 2018-12 | SP#82 | SP-181087 | 0661 | 3 | B | Data Volume Reporting for Option 4/7 | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0662 | 4 | F | Configuration Transfer Procedure | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0666 | 3 | F | Avoiding overloading the target of AMF Load Re-Balancing | 15.4.0 | +| 2018-12 | SP#82 | SP-181090 | 0667 | 1 | F | UE storage of NSSAI and associated mapping | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0668 | 1 | F | Clarification of PS Voice Support for 3GPP and non-3GPP | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0669 | 1 | F | Secondary authentication update | 15.4.0 | +| 2018-12 | SP#82 | SP-181087 | 0671 | 1 | F | Emergency registration in a normally camped cell | 15.4.0 | +| 2018-12 | SP#82 | SP-181088 | 0672 | 1 | F | Priority indication over SBA interfaces via Message Priority header | 15.4.0 | +| 2018-12 | SP#82 | SP-181088 | 0675 | 3 | F | MME/AMF registration in HSS+UDM | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0676 | 1 | F | Completion of 5QI characteristics table | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0677 | - | F | Consistent usage of terminology in QoS notification control description | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0679 | 3 | F | Alignment for always-on PDU sessions | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0680 | 1 | C | PS Data Off supporting non-IP data packet | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0682 | 3 | F | Clarification on the PDU Session handover procedure with the User Plane Security Enforcement | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0683 | 1 | F | Clean up congestion control | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0685 | 3 | F | Correction on SSCMSP | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0686 | 4 | F | Clarification on the AMF store the DNN and PGW-C+SMF to UDM+HSS | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0687 | 1 | F | Clarification on NPLI for EPS Fallback | 15.4.0 | +| 2018-12 | SP#82 | SP-181087 | 0688 | 1 | F | Correction on UE inclusion of UE's usage setting | 15.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| 2018-12 | SP#82 | SP-181090 | 0690 | 3 | F | UE radio capability for paging information with NR and eLTE connected to the CN | 15.4.0 | +| 2018-12 | SP#82 | SP-181087 | 0691 | 2 | F | Correction to traffic steering control | 15.4.0 | +| 2018-12 | SP#82 | SP-181090 | 0692 | - | F | Using TCP for reliable NAS transport between UE and N3IWF | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0693 | 1 | C | 5GS Support for MCS Subscription | 15.4.0 | +| 2018-12 | SP#82 | SP-181091 | 0695 | 1 | F | UE sending UE Integrity Protection Data Rate capability over any access | 15.4.0 | +| 2018-12 | SP#82 | SP-181087 | 0696 | 1 | F | Correction on Subscribed 5QI | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0699 | - | F | Selective deactivation for always-on PDU sessions | 15.4.0 | +| 2018-12 | SP#82 | SP-181091 | 0701 | 1 | F | Use of emergency DNN when Emergency Registered | 15.4.0 | +| 2018-12 | SP#82 | SP-181090 | 0703 | 3 | F | Requirements on 5G-TMSI randomness | 15.4.0 | +| 2018-12 | SP#82 | SP-181087 | 0707 | 1 | F | Emergency registration over two accesses | 15.4.0 | +| 2018-12 | SP#82 | SP-181090 | 0708 | 1 | F | Registration procedure with different Registration types | 15.4.0 | +| 2018-12 | SP#82 | SP-181088 | 0709 | 2 | F | EPS to 5GS with network slices | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0710 | 2 | F | AUSF and UDM selection | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0712 | 2 | F | Providing a threshold to UPF while waiting for quota | 15.4.0 | +| 2018-12 | SP#82 | SP-181088 | 0713 | 1 | F | Corrections to usage of IP index | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0716 | 2 | F | Clarification on OVERLOAD behaviour for the EUTRA connected to 5GC | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0719 | 2 | F | Clarification on Registration with AMF re-allocation | 15.4.0 | +| 2018-12 | SP#82 | SP-181089 | 0720 | 1 | F | PDN Disconnection handling | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0721 | 3 | F | Always on Setting for the EBI allocated PDU Session | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0722 | 2 | F | Clarification on packet filter handling | 15.4.0 | +| 2018-12 | SP#82 | SP-181086 | 0723 | 4 | F | Clarify for PDB of dynamically assigned 5QI | 15.4.0 | +| 2018-12 | SP#82 | SP-181091 | 0724 | 2 | F | Update the UCU procedure with operator-defined access category definitions | 15.4.0 | +| 2018-12 | SP#82 | SP-181087 | 0725 | - | F | Correction of VLAN ID | 15.4.0 | +| 2018-12 | SP#82 | SP-181085 | 0726 | 1 | F | Clarification on DN authorization data between PCF and SMF | 15.4.0 | +| 2018-12 | SP#82 | SP-181084 | 0730 | 2 | F | Addition of URRP-AMF definition | 15.4.0 | +| 2019-03 | SP#83 | SP-190154 | 0700 | 3 | F | Use of S-NSSAI at interworking from EPS to 5GS | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0733 | 2 | F | Slice interworking HR mode update | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0741 | 1 | F | UDR selection | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0742 | 2 | F | Fixing text related to discovery and selection | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0743 | 1 | F | Change of the term confidence level | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0756 | 2 | F | Correction to NSSAI logic | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0758 | 2 | F | UL Session-AMBR enforcement in UPF | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0759 | 1 | F | Alignment with stage 3 for EPS interworking indications | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0762 | 2 | F | Clarification of user plane security enforcement between NG-RAN and SMF in Dual Connectivity scenario | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0767 | 2 | F | QoS Notification Control during handover | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0773 | 1 | F | Correction to traffic steering control | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0774 | 3 | F | Configurable time for subsequent notification that the GFBR cannot be fulfilled | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0775 | 1 | F | Clarification for default values | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0784 | 4 | F | 5GC emergency calls over non-3GPP | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0786 | 1 | F | Adding UE Local Configuration as an additional option to the URSP | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0789 | - | F | Update of network slicing text on NSSAI inclusion in RRC | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0791 | 3 | C | Supporting early trace in AUSF | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0792 | 1 | F | IMS voice over PS Session Supported Indication in roaming cases. | 15.5.0 | +| 2019-03 | SP#83 | SP-190154 | 0793 | 2 | F | Introduce Charging Function in overall architecture | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0797 | 2 | F | Update of configured NSSAI handling | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0806 | 3 | F | Corrections to AMF overlad control procedure | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0808 | - | F | TS 23.501 Update to Network Slice availability | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0818 | - | F | No services defined for Ngmlc | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0824 | 6 | F | Clarification on DN authorization data | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0833 | - | F | Clarification on Establishing a PDU Session in a Network Slice | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0834 | 8 | F | Clarification on NAS level congestion control | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0853 | 6 | F | PS Data Off status update when congestion control is applied in AMF | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0857 | 1 | F | Correction to Mobility Restrictions (for non-3GPP access) | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0860 | 3 | F | Clarification on the UE behaviours under NAS level congestion control | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0875 | - | F | Permanent identifier with IMEISV format | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0876 | 2 | F | Removing a superfluous NOTE about the need for ultra-low latency QCI/5QIs | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0877 | 7 | F | Allowed Area and Non-Allowed Area encoding | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0901 | 2 | F | Alignment of Emergency Registered definition with Stage 3 | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0904 | - | F | Addition of PCF services Npcf_UEPolicyControl and Npcf_EventExposure | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0910 | 3 | F | Clarification on ARP Proxy | 15.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|-------------------------------------------------------------------------------------------------|---------------| +| 2019-03 | SP#83 | SP-190155 | 0913 | 2 | F | PS Data Off status update when UE in non-allowed area or out of LADN area | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0915 | 2 | F | Non-roaming reference architecture correction | 15.5.0 | +| 2019-03 | SP#83 | SP-190155 | 0922 | 2 | F | TS 23.501: correction for enforcement of user plane integrity protection | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0932 | 2 | F | Clarification on the PDU Session parameter | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0942 | 2 | F | Transport Level Packet Marking | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0943 | 2 | F | Support of baseline Frame Routing feature | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0945 | 1 | F | Disabling E-UTRA connected to EPC radio capability | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0949 | 2 | F | Correction of slicing terminology | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0958 | 1 | F | Adding a new 5G-GUTI allocation condition | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0968 | 2 | F | Clarify on Network Slice availability change | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0969 | 2 | F | Correction the terms on Secondary authentication/authorization of the PDU Session Establishment | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0975 | 1 | F | Clarification on Core Network type Restriction | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0976 | 3 | F | Clarification on AMF planned removal | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0979 | 1 | F | Correction of UE 5GSM Core Network Capability | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0982 | 2 | F | Clarification on QoS Notification control | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0988 | 0 | F | Correction on reference | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0992 | 3 | F | Slice interworking HR mode update | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 0996 | 2 | F | Clarification on PCF selection | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 1006 | - | F | Corrections on routing rule | 15.5.0 | +| 2019-03 | SP#83 | SP-190156 | 1012 | 2 | F | Clarification on GTP-u protocol | 15.5.0 | +| 2019-03 | SP#83 | SP-190175 | 0704 | 4 | C | New 5QIs for Enhanced Framework for Uplink Streaming | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0734 | 8 | B | TS 23.501: Introducing Non-public network | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0747 | 12 | B | Support for 5G LAN | 16.0.0 | +| 2019-03 | SP#83 | SP-190194 | 0757 | 8 | B | Introducing support for Non-Public Networks | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0903 | 2 | B | Introduction of 5G LAN-type service | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 1007 | 2 | B | Introducing support TSC Deterministic QoS | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 1008 | 2 | B | Introducing support Hold and Forward Buffers for TSC Deterministic QoS | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 1002 | 3 | B | 5GS Logical TSN bridge management | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0748 | 3 | B | CloT High Level Description in 23.501 | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0751 | 3 | B | High Latency Overall Description | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0752 | 4 | B | Introducing Rate Control for 5G CloT | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0768 | 6 | B | Introduction of eDRX in 5GS | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0819 | 1 | B | CloT Monitoring Events | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0820 | 4 | B | Restriction of use of Enhanced Coverage in 5GC | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0825 | 2 | B | Introduction to Reliable Data Service | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0889 | 7 | B | Introduction of data transfer in Control Plane CloT 5GS Optimisation | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0890 | 6 | B | Introduction of NEF based infrequent small data transfer via NAS | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0893 | 7 | B | Introduction of Power Saving Functions for CloT | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0894 | 5 | B | CloT Introduction of Overload Control | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0895 | 2 | B | Introduction of Inter-RAT mobility support to and from NB-IoT | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0896 | 2 | B | CloT Introduction of CN Selection and Steering | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 1014 | 2 | B | Introduction of Service Gap Control | 16.0.0 | +| 2019-03 | SP#83 | SP-190173 | 0735 | 11 | B | Introduction of ATSSS Support | 16.0.0 | +| 2019-03 | SP#83 | SP-190173 | 0740 | 7 | B | Support of Steering Functions for ATSSS | 16.0.0 | +| 2019-03 | SP#83 | SP-190173 | 0770 | 4 | B | QoS for Multi-Access PDU Session | 16.0.0 | +| 2019-03 | SP#83 | SP-190173 | 0921 | 3 | B | Access Network Performance Measurements | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0810 | 2 | B | New clause for URLLC supporting | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0753 | 8 | B | General description of solution 1 in 23.725 for user plane redundancy | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0811 | 6 | B | Add description of solution 4 in 23.725 to 23.501 | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0872 | 3 | B | Description of solution 7 in 23.725 as replication framework | 16.0.0 | +| 2019-03 | SP#83 | SP-190164 | 0732 | 2 | B | ETSUN - Architecture conclusion | 16.0.0 | +| 2019-03 | SP#83 | SP-190164 | 0848 | 5 | B | UL CL/BP controlled by I-SMF | 16.0.0 | +| 2019-03 | SP#83 | SP-190175 | 0704 | 4 | C | New 5QIs for Enhanced Framework for Uplink Streaming | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0755 | 2 | B | Description of solution 11 in 23.725 for Ethernet anchor relocation | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0734 | 8 | B | Introducing Non-public network | 16.0.0 | +| 2019-03 | SP#83 | SP-190215 | 0736 | 10 | B | Introduction of indirect communication between NF services, and implicit discovery | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0744 | 4 | B | SUPI and SUCI for wireline access | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0745 | 6 | B | Mobility restrictions for wireline access | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0746 | 2 | B | IP addressing enhancements | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0747 | 12 | B | Support for 5G LAN | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0754 | 2 | B | Description of solution 2 in 23.725 for redundancy as an informational annex | 16.0.0 | +| 2019-03 | SP#83 | SP-190173 | 0761 | 1 | B | ATSSS-SMF and UPF selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0776 | 3 | B | CloT Introduction of extended DRX in CM-CONNECTED with RRC Inactive state | 16.0.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|-------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | SP#83 | SP-190167 | 0781 | 2 | B | Support of Trusted non-3GPP access | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0783 | 2 | B | Trusted non-3GPP Access Network Selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190173 | 0785 | 5 | B | Updating 5.8.2.11 for N4 Rules to support ATSSS | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0799 | 10 | B | eSBA communication schemas related to general discovery and selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0800 | 3 | B | eSBA communication schemas related to UDM and UDR discovery and selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0940 | 3 | B | Use of analytics for SMF selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0801 | 7 | B | eSBA communication schemas related to SMF discovery and selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0802 | 3 | B | eSBA communication schemas related to PCF discovery and selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0803 | 5 | B | eSBA communication schemas related to AUSF discovery and selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0804 | 4 | B | eSBA communication schemas related to AMF discovery and selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0826 | 2 | B | Introduction of the MSISDN-less MO SMS Service | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0828 | 1 | B | Introduction of the SCEF+NEF | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0831 | 6 | B | CR for TS 23.501 based on conclusion of eNA TR 23.791 | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0837 | 3 | B | Use of NWDAF analytics for decision of MICO mode parameters | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0841 | 2 | B | FQDN format of N3IWF in a standalone non-public network | 16.0.0 | +| 2019-03 | SP#83 | SP-190168 | 0843 | 2 | F | Update to LCS related definitions | 16.0.0 | +| 2019-03 | SP#83 | SP-190238 | 0844 | 8 | B | Network reliability support with Sets | 16.0.0 | +| 2019-03 | SP#83 | SP-190199 | 0850 | 1 | B | Enhancement on slice interworking-501 | 16.0.0 | +| 2019-03 | SP#83 | SP-190162 | 0859 | 2 | B | Adding 5G SRVCC description to 23.501 | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0862 | 7 | B | UPF Selection influenced by the indication of the identity/identities of 5G AN N3 User Plane capability | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0863 | 8 | B | Architecture and reference points for Wireline AN | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0866 | 8 | B | Clarification of RM and CM for 5G-RG | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0870 | 3 | B | TSC definitions | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0871 | 4 | B | TSC Architecture | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0873 | 8 | B | eSBA communication schema co-existence | 16.0.0 | +| 2019-03 | SP#83 | SP-190170 | 0878 | 2 | B | NEF service for service specific parameter provisioning | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0886 | 5 | B | Introduction for solution 14 to key issue 9 | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0897 | 7 | B | Sol#6 specific updates to 5.6.4.2 | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0898 | 6 | B | External parameters provisioning to the 5GS | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0899 | 1 | B | Use of analytics for user plane function selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0900 | 1 | B | Use of analytics for UE mobility procedures | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 0909 | 3 | B | Control of traffic forwarding in 5G-LAN | 16.0.0 | +| 2019-03 | SP#83 | SP-190165 | 0916 | 1 | B | User Plane Forwarding with Control Plane C IoT 5GS Optimisation | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0926 | 2 | B | Update the support of virtualized deployment with SCP distribution and the NF/NF service instance Set | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0927 | 1 | C | Update of NRF functionalities | 16.0.0 | +| 2019-03 | SP#83 | SP-190164 | 0931 | 2 | B | UE IP address Allocation by UPF: N4 impacts | 16.0.0 | +| 2019-03 | SP#83 | SP-190164 | 0933 | 1 | B | ETSUN - Conclusion alignment | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0934 | 2 | B | Support of full Frame Routing feature | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 0941 | 4 | B | Location information | 16.0.0 | +| 2019-03 | SP#83 | SP-190164 | 0954 | 2 | B | Addition of UE IP address Allocation by UPF | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0961 | 1 | B | Protocol stack for W-5GAN support | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0962 | 3 | C | Session Management of 5G-RG/FN-RG connection to 5GC in the Wireline ANs | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0964 | 2 | B | NEF service for NWDAF analytics | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0972 | 3 | B | Add description of solution 13 in 23.725 to TS 23.501 | 16.0.0 | +| 2019-03 | SP#83 | SP-190167 | 0981 | 2 | B | Extension of the QoS model for wireline access | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0983 | 2 | B | Update of TS 23.501 for Rel.16 BDT Notification | 16.0.0 | +| 2019-03 | SP#83 | SP-190168 | 0984 | 2 | F | Update the description and the reference of LMF service | 16.0.0 | +| 2019-03 | SP#83 | SP-190172 | 0987 | 3 | B | CR for TS 23.501 Clarifications NWDAF Discovery and Selection | 16.0.0 | +| 2019-03 | SP#83 | SP-190171 | 0989 | 2 | B | Introduction of E2E PDB Division | 16.0.0 | +| 2019-03 | SP#83 | SP-190169 | 1003 | 2 | B | QoS parameters mapping between TSN characters and 5G QoS | 16.0.0 | +| 2019-03 | SP#83 | SP-190174 | 1010 | 3 | B | Introducing NF Set and NF Service Set | 16.0.0 | +| 2019-03 | SP#83 | SP-190175 | 1022 | 2 | B | Introduction of Dedicated Bearer for Ethernet support in EPC | 16.0.0 | +| 2019-04 | - | - | - | - | - | MCC correction of clause 5.29.3 (to 5.30.3) and position of clause 5.31.7.2. Editorial style and formatting corrections | 16.0.1 | +| 2019-04 | - | - | - | - | - | MCC correction swapping clause 5.28 to 5.29 and clause 5.29 to 5.28 for readability purposes | 16.0.2 | +| 2019-06 | SP#84 | SP-190407 | 0892 | 4 | B | Introduction of inter-UE QoS differentiation for NB-IoT using NB-IoT UE Priority | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1019 | 3 | B | Support of EPC interworking for C IoT Monitoring Events | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1028 | 1 | D | Proper naming of the reference point between two UPFs for direct routing | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1033 | 2 | B | Clarification on MA PDU session | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1034 | 5 | B | Determination of access availability | 16.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-06 | SP#84 | SP-190419 | 1035 | 4 | B | NRF based P-CSCF discovery | 16.1.0 | +| 2019-06 | SP#84 | SP-190425 | 1037 | 3 | B | Introduction of RACS: UCMF services | 16.1.0 | +| 2019-06 | SP#84 | SP-190514 | 1042 | 6 | A | Correcting factors to consider for PCF selection | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1044 | 2 | A | QoS Notification Control | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1047 | 3 | F | MICO mode and Periodic Registration Timer Control | 16.1.0 | +| 2019-06 | SP#84 | SP-190422 | 1050 | 4 | B | Transfer of N4 information for local traffic switching from SMF to I-SMF | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1015 | 2 | B | Proposed update to 5G LAN terminology | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1052 | 8 | B | Further detailing of 5G LAN group management | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1055 | 2 | F | Correction of SMF selecting UPF for a particular PDU Session supporting EPS IWK | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1056 | 2 | F | Network Slicing and delegated discovery | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1059 | 1 | F | UE specific DRX parameter use for NB-IOT | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1062 | 1 | A | Congestion control exception for reporting 5GSM Core Network Capability and Always-on PDU Session Requested indication | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1064 | 1 | A | Data volume reporting granularity | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1066 | - | A | Removal of restriction of using UE requested PDU modification request for Emergency PDU | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1067 | 6 | F | Return to NR from EPS/RAT fallback | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1068 | 2 | F | Clarification on PRA | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1070 | 3 | F | Clarification to support associating URLLC traffic to redundant PDU sessions | 16.1.0 | +| 2019-06 | SP#84 | SP-190425 | 1071 | 5 | B | Introduction of Radio Capabilities Signalling Optimisation feature | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1073 | 4 | B | Support of emergency services in public network integrated NPNs | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1075 | 3 | F | Clarification on MICO and eDRX during CN node changes | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1078 | 1 | F | Correction and clarifications for QoS Flow in MA PDU Session | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1079 | 2 | F | Correction related to ATSSS Rule | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1080 | 2 | F | Clear ENs about Measurement Assistance Information for ATSSS | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1083 | 6 | B | Clarification of Inserting and Removing VLAN tags for 5G-VN | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1091 | 2 | F | Update of the NF/NF service discovery result | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1092 | 3 | C | Update of NRF function and services | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1093 | 2 | F | Update of network reliability support | 16.1.0 | +| 2019-06 | SP#84 | SP-190420 | 1094 | 1 | C | Back-off timers handling for scheduled communication | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1095 | 5 | C | Addressing Editor's notes on TSN | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1098 | 1 | F | Access Control for PLMN Integrated NPN | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1101 | 9 | B | Establishing UP connection during CP Data Transfer | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1103 | 1 | F | Corrections for SMF, UPF and PCF selection for an MA PDU session | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1104 | 1 | F | Corrections for N4 rules for ATSSS | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1109 | 2 | B | Service Gap corrections | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1116 | 2 | F | Local cache information for ARP proxy | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1118 | 1 | F | UE Requested PDU Session Establishment with Network Modification to MA PDU Session | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1119 | 2 | C | Granularity of TSN bridge | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1120 | 1 | C | Filtering own address for Ethernet PDU Sessions | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1123 | 3 | B | TSN QoS mapping and 802.1Qbv parameters | 16.1.0 | +| 2019-06 | SP#84 | SP-190415 | 1128 | 3 | B | Access to 5GC from UEs not supporting NAS over non-3GPP access | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1130 | 1 | A | Validity of LADN information and LADN discovery/storage in the UE per-PLMN | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1131 | 3 | A | Conclusions on applicability of Allowed NSSAI to E-PLMNs | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1132 | 1 | A | Correction to the provisioning of the UE Integrity Protection Data Rate capability | 16.1.0 | +| 2019-06 | SP#84 | SP-190419 | 1134 | 3 | B | Allowing IMS to use N5 interface to interact with PCF | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1135 | 3 | F | Correction regarding legacy UE and non-NPN UE | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1139 | 3 | F | AMF selection during inter PLMN mobility | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1142 | 6 | C | Update description for E2E PDB division | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1144 | 2 | C | Explicit indication of AF response to be expected for runtime coordination with AF | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1149 | 9 | B | Roaming support for service exposure | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1152 | 1 | A | Corrections for the activation of usage reporting in the UPF | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1159 | 2 | A | Clarification on NAS level congestion control | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1161 | 3 | A | Correction of UE 5GSM Core Network Capability | 16.1.0 | +| 2019-06 | SP#84 | SP-190423 | 1162 | 1 | B | Introduce a new standardized SST value dedicated for V2X services | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1163 | 1 | F | Clarification on the CN PDB configured in each NG-RAN node | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1164 | 2 | B | Clarification on GBR QoS Flow establishment | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1168 | 5 | C | RTT measurements with TCP | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1169 | 2 | F | MA PDU QoS Aspects On Link-Specific Multipath and MPTCP Proxy Addresses | 16.1.0 | +| 2019-06 | SP#84 | SP-190422 | 1170 | 1 | F | ETSUN Architecture Update | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1171 | 4 | F | SCP Function Update | 16.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|-------------------------------------------------------------------------------------------|--------| +| 2019-06 | SP#84 | SP-190412 | 1173 | 2 | F | Redundant PDU session handling | 16.1.0 | +| 2019-06 | SP#84 | SP-190421 | 1174 | 6 | B | Introduction of Slice-Specific Authentication and Authorisation | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1176 | 1 | A | Association between the GUAMI and AMF instance | 16.1.0 | +| 2019-06 | SP#84 | SP-190422 | 1177 | 5 | B | LADN handling in ETSUN scenario | 16.1.0 | +| 2019-06 | SP#84 | SP-190422 | 1179 | 7 | B | Traffic offload by UPF controlled by the I-SMF | 16.1.0 | +| 2019-06 | SP#84 | SP-190422 | 1180 | 1 | B | UE IP address Allocation by AAA/DHCP | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1183 | 3 | C | SNPN deployment scenarios | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1186 | 8 | B | Introducing 5GS UP optimization | 16.1.0 | +| 2019-06 | SP#84 | SP-190420 | 1187 | 1 | B | Adding NF load information inside NFprofile | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1190 | 2 | C | Resolving editor's note on eSBA | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1191 | 3 | F | ATSSS support for Unstructured Data | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1194 | 3 | F | Removing the EN on the DNN and 5G LAN group mapping | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1198 | 8 | C | Resolving the EN on traffic pattern to the TT | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1199 | 3 | F | Clarification on the CAG ID and slicing | 16.1.0 | +| 2019-06 | SP#84 | SP-190420 | 1201 | 2 | B | CR for adding Naf_EventExposure services | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1202 | 2 | F | Clarification on PDU Session management for 5G-LAN multicast | 16.1.0 | +| 2019-06 | SP#84 | SP-190409 | 1205 | - | B | Add new Reference points | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1207 | 3 | F | 5G-LAN Service continuity | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1212 | 1 | B | Update to Support TSAI for TSC Deterministic QoS | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1214 | 10 | B | Introducing support for UE and UPF Residence Time for TSC Deterministic QoS | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1217 | 4 | C | 5G URLLC: Optimizing Redundancy | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1218 | 2 | F | Standalone NPN - NID Management | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1219 | 1 | F | Standalone NPN - EPS Interworking support | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1222 | 12 | B | NF Set and NF Service Set - Open items resolution | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1226 | - | F | AMF Failure - Other CP NF Behaviour | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1228 | 1 | A | Correction on home-routed roaming architecture for EPC interworking | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1230 | 4 | C | Dedicated SMF selection for a 5G LAN group | 16.1.0 | +| 2019-06 | SP#84 | SP-190415 | 1233 | 4 | F | Requirements on the Ta interface | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1235 | 2 | A | Configuration transfer between NG-RAN and eNodeB | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1237 | 1 | A | Cleanup of NAS Congestion Control | 16.1.0 | +| 2019-06 | SP#84 | SP-190415 | 1239 | 4 | B | Removal of roaming support from Rel-16 for W-5GAN | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1243 | - | B | Update to NEF description by adding NIDD support | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1249 | 2 | A | Correction of SM congestion control override | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1250 | 2 | B | Corrections to MICO mode with Active Time | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1251 | 1 | B | Subscription Information Influence on PDU Session Rate Control | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1252 | 2 | B | Handling of Stored Small Data Rate Control Status at Subsequent PDU Session Establishment | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1256 | 4 | F | Corrections to CN assisted RAN parameters tuning | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1257 | 3 | F | Corrections to Network Slice Registration | 16.1.0 | +| 2019-06 | SP#84 | SP-190420 | 1258 | 2 | B | CR for TS 23.501 Clarifications NWDAF Discovery and Selection | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1262 | 1 | F | RRC Inactive information for eDRX | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1263 | 2 | F | AMF utilizes NRF to discover NSSF | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1264 | 3 | F | QoS differentiation for access to SNPN (PLMN) services via PLMN (SNPN) | 16.1.0 | +| 2019-06 | SP#84 | SP-190422 | 1265 | - | D | Fixing clause number reference | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1266 | 2 | F | Correction of description of the IMS voice over PS Session Supported Indication | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1271 | 13 | D | SCP: Service-mesh-based deployment options | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1274 | 2 | F | Clarification on the UE operates in SR mode in case the NW does not support IWK | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1275 | - | A | Removing unnecessary PDU release during inter-system handover | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1277 | 1 | A | Definition of LPP | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1278 | 2 | A | UE's usage setting indicating UE capability of supporting voice over E-UTRA | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1279 | - | A | Clarification for interface identifier allocation in IPv6 Multi-homing | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1283 | 3 | F | Interaction between MICO mode with active time and eDRX | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1287 | - | F | Update reference to TS 24.250 | 16.1.0 | +| 2019-06 | SP#84 | SP-190426 | 1291 | 1 | B | Introduction of UDICOM | 16.1.0 | +| 2019-06 | SP#84 | SP-190417 | 1296 | 2 | C | Adding Support for Indicating Serialization Format in RDS | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1297 | 2 | F | CAG and Network Slice Selection | 16.1.0 | +| 2019-06 | SP#84 | SP-190428 | 1298 | 3 | F | Unified Access Control with NPN | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1301 | 1 | A | Configuring Transport Level Marking values | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1303 | 1 | F | Alignment of Network Slice selection logic | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1305 | 2 | F | Enforcement of UP integrity protection | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1306 | 2 | F | Ethernet support clarification | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1307 | 2 | F | Generalized text for redundant user planes in RAN | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1308 | 3 | C | DNN replacement in 5GC | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1312 | 1 | B | Extending the significance of the locality parameter | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1315 | 2 | A | Correcting AMF selection | 16.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------|--------| +| 2019-06 | SP#84 | SP-190422 | 1316 | 1 | C | Clarify which parameters are (not) applicable for I-SMF selection. | 16.1.0 | +| 2019-06 | SP#84 | SP-190412 | 1320 | 3 | F | Clarification on redundant N3 tunnel solution | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1321 | - | F | Clarification on IWK without N26 | 16.1.0 | +| 2019-06 | SP#84 | SP-190418 | 1323 | 1 | C | S6b optional for ePDG connected to 5GS | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1328 | 2 | F | Data forwarding for 5G-LAN multicast | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1331 | 3 | B | Support of Service Context Transfer in TS23.501 | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1333 | 1 | B | Alignment of IMS Voice Service via EPS Fallback with RAN specifications | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1337 | 1 | B | Update to High Latency Overall Description | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1338 | 2 | F | NPN: Corrections to handling of Allowed CAG list and CAG-only indication | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1339 | 2 | F | NPN: Correction to CAG-only indication | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1341 | 2 | F | NPN: Update and enforcement of new Allowed CAG list and CAG-only indication | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1346 | 2 | F | CloT scope clarification | 16.1.0 | +| 2019-06 | SP#84 | SP-190404 | 1350 | 2 | A | Location Reporting of secondary cell | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1351 | 2 | B | Network request re-activation of user-plane resources | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1352 | 2 | B | Clarification on Access Network Performance Measurements | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1358 | 1 | A | Emergency Fallback from non-3GPP/ePDG | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1360 | 1 | F | NIDD related indications | 16.1.0 | +| 2019-06 | SP#84 | SP-190420 | 1362 | 2 | B | Description regarding NEF support of data retrieval from external party | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1366 | 3 | F | Subscription Segmentation in PCF and UDR | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1367 | 2 | C | Serving PLMN UE-AMBR control | 16.1.0 | +| 2019-06 | SP#84 | SP-190415 | 1372 | 1 | B | Access network selection for devices that do not support NAS over WLAN | 16.1.0 | +| 2019-06 | SP#84 | SP-190415 | 1374 | - | B | AMF overload control for trusted non-3GPP access | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1375 | 2 | B | 23.501 part of PCF selection for PDU sessions with same DNN and S-NSSAI | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1376 | 1 | B | Support for Enhanced Coverage Restriction Control via NEF | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1378 | 1 | F | Support for Dynamic Port Management in RDS | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1381 | 2 | B | Introduction of TSN Sync soln #28A | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1382 | 1 | F | Update to Survival time EN | 16.1.0 | +| 2019-06 | SP#84 | SP-190419 | 1384 | 3 | B | Adding UDR NF Group ID association functionality | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1390 | 2 | F | Correction of use of PEI/IMEI for non-3GPP only UEs | 16.1.0 | +| 2019-06 | SP#84 | SP-190416 | 1395 | 1 | F | Clarifications on Reflective QoS for MPTCP | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1396 | 1 | B | NW selection considering RAN sharing for SNPNS | 16.1.0 | +| 2019-06 | SP#84 | SP-190421 | 1404 | 1 | F | Target AMF Selection during mobility from EPS to 5GS | 16.1.0 | +| 2019-06 | SP#84 | SP-190420 | 1405 | - | F | Corrections to analytics used by AMF for MICO mode and SMF for UPF selection | 16.1.0 | +| 2019-06 | SP#84 | SP-190420 | 1406 | 1 | B | Update NRF descriptions to support AF Available Data Registration as described in TS23.288 | 16.1.0 | +| 2019-06 | SP#84 | SP-190427 | 1408 | 2 | F | Corrections and alignments for the 5QI characteristics table | 16.1.0 | +| 2019-06 | SP#84 | SP-190410 | 1413 | 2 | B | NF Set concept for SMF | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1417 | 2 | B | Stateless IPv6 Address Autoconfiguration for Control Plane CloT 5GS Optimisation | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1418 | 2 | B | Introduction of Small Data Rate Control Interworking with APN Rate Control | 16.1.0 | +| 2019-06 | SP#84 | SP-190415 | 1420 | 2 | B | Location information for trusted N3GPP | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1423 | 2 | B | TSC Burst Arrival Time usage and Clock Reference | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1424 | 2 | F | Correction on Location reporting procedure | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1425 | 3 | C | Address editor's notes for 5GS Bridge management and QoS mapping | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1426 | 4 | C | clarifications on SNPN | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1427 | 2 | C | Support for unicast traffic forwarding within a 5G VN group | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1430 | 2 | C | implementation of 5G-VN related interfaces | 16.1.0 | +| 2019-06 | SP#84 | SP-190407 | 1431 | 1 | B | Support of User Plane Optimisations in Preferred and Supported Network Behaviour | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1432 | 1 | B | Ingress timestamp signalling | 16.1.0 | +| 2019-06 | SP#84 | SP-190413 | 1436 | - | F | Align CHF service for offline only charging | 16.1.0 | +| 2019-06 | SP#84 | SP-190419 | 1438 | 2 | B | HSS discovery via NRF | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1443 | 1 | B | AF influence for traffic forwarding in 5G-VN | 16.1.0 | +| 2019-06 | SP#84 | SP-190431 | 1445 | 2 | B | Update of TS23.501 to finalize xBDT feature | 16.1.0 | +| 2019-06 | SP#84 | SP-190429 | 1448 | - | D | Vertical LAN - Editorial clean up | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1449 | 1 | A | Applicability of Allowed NSSAI to PLMNs whose TAs are in the RA TAI list | 16.1.0 | +| 2019-06 | SP#84 | SP-190399 | 1451 | - | A | Clarification on S-NSSAI for PDU session in Requested NSSAI | 16.1.0 | +| 2019-09 | SP#85 | SP-190608 | 0990 | 6 | B | Introduction of QoS Monitoring to assist URLLC Service | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1097 | 3 | F | Support of Standalone Non-Public Networks | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1240 | 5 | F | Clarification of support of dual radio UE | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1329 | 3 | F | IP Address Accessibility for MA PDU Session | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1330 | 2 | F | N3/N9 Tunnels for the MA-PDU Session | 16.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------------|--------| +| 2019-09 | SP#85 | SP-190605 | 1347 | 6 | F | Introducing of UP CIoT 5GS Optimisation capability | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1364 | 1 | F | NIDD Description Update for Maximum Packet Size | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1371 | 3 | F | Clarification for the related CAG identifier | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1379 | 2 | F | Support for access to PLMN services via SNPN and SNPN services via PLMN | 16.2.0 | +| 2019-09 | SP#85 | SP-190608 | 1414 | 3 | B | QoS monitoring based on GTP-U paths | 16.2.0 | +| 2019-09 | SP#85 | SP-190615 | 1440 | 8 | B | Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | 16.2.0 | +| 2019-09 | SP#85 | SP-190607 | 1453 | 4 | F | Completion of the PCF Group | 16.2.0 | +| 2019-09 | SP#85 | SP-190622 | 1454 | 2 | F | Inter Core Network Roaming | 16.2.0 | +| 2019-09 | SP#85 | SP-190609 | 1455 | 3 | F | Align PLMN selection with service requirements | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1457 | 2 | F | NAS RAI corrections | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1461 | 2 | F | Clarifications to QoS support for NB-IoT | 16.2.0 | +| 2019-09 | SP#85 | SP-190617 | 1463 | 3 | F | Correction on support of RACS | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1464 | 3 | C | Completing Ethernet port management | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1465 | 2 | F | Adding N4 Notification about buffered packets being dropped | 16.2.0 | +| 2019-09 | SP#85 | SP-190609 | 1466 | - | F | PEI for 5G-RG and FN-RG | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1467 | 1 | F | Corrections to general 5G LAN description | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1468 | 3 | F | 5G LAN user plane corrections | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1469 | 4 | F | Awareness of UE PMF port number and MAC address in UPF | 16.2.0 | +| 2019-09 | SP#85 | SP-190607 | 1470 | 4 | F | Clarification of the Locality of a NF Instance | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1476 | 2 | F | Replacement of VPLMN by serving PLMN where appropriate | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1477 | 1 | F | Clarification on the misalignment of service area restriction between UE and Network | 16.2.0 | +| 2019-09 | SP#85 | SP-190611 | 1478 | 1 | F | Correction of P-CSCF selection to consider proximity to UPF | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1479 | 1 | F | Aligning Terminology referring to the CIoT 5GS Optimisations | 16.2.0 | +| 2019-09 | SP#85 | SP-190617 | 1480 | 1 | F | Corrections of PLMN assigned Capability signalling | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1483 | 1 | F | Correction of Network Slice selection with NSSF | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1487 | 3 | C | DNN replacement in 5GC | 16.2.0 | +| 2019-09 | SP#85 | SP-190608 | 1489 | 1 | F | Failure handling for redundancy based on dual connectivity | 16.2.0 | +| 2019-09 | SP#85 | SP-190608 | 1490 | 1 | F | Clarification on reordering requirement with GTP-U redundancy | 16.2.0 | +| 2019-09 | SP#85 | SP-190601 | 1494 | 1 | A | Discrepancy with TS 33.501 with respect to Secondary Authentication | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1500 | 2 | F | Clarification of traffic switching for GBR QoS Flow in MA PDU session | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1501 | 3 | F | N19 Tunnel management | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1504 | 3 | C | TSN Time Synchronization Traffic Handling | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1507 | 3 | F | TSC Assistance Information update | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1509 | 1 | F | Handling of CIoT optimisations not supported over NR | 16.2.0 | +| 2019-09 | SP#85 | SP-190617 | 1517 | 2 | C | Handling of NB-IOT radio capabilities and RACS in 5GS | 16.2.0 | +| 2019-09 | SP#85 | SP-190601 | 1519 | 2 | A | Allowed NSSAI and TAI list from (previous) UE Configuration Update | 16.2.0 | +| 2019-09 | SP#85 | SP-190622 | 1521 | 1 | F | Use of the URSP rules when UE attaches to EPS | 16.2.0 | +| 2019-09 | SP#85 | SP-190624 | 1522 | 1 | B | Introduction of the IAB support in 5GS | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1540 | 2 | F | Clarification on the meaning of Emergency Services Support indicator | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1541 | 2 | F | Addition of missing CIoT services | 16.2.0 | +| 2019-09 | SP#85 | SP-190606 | 1543 | 1 | F | Addition of missing GMLC and its service | 16.2.0 | +| 2019-09 | SP#85 | SP-190614 | 1544 | 3 | F | Mobility event management | 16.2.0 | +| 2019-09 | SP#85 | SP-190608 | 1547 | - | F | Improvement for support of redundant transmission on N3/N9 interfaces | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1548 | 1 | F | Clarification on S-NSSAI(s) for PDU session | 16.2.0 | +| 2019-09 | SP#85 | SP-190622 | 1556 | 2 | D | Adding Policy Charging and Control related reference points | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1557 | 2 | F | Update to NEF related reference points | 16.2.0 | +| 2019-09 | SP#85 | SP-190611 | 1563 | 1 | F | NF Group resolution by SCP | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1570 | 1 | F | Corrections about default QoS rule | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1571 | 3 | B | Interworking for MA PDU Session | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1573 | 2 | F | Conditions to use CP or UP CIoT | 16.2.0 | +| 2019-09 | SP#85 | SP-190621 | 1578 | 1 | F | Correction of NAS transport for LCS | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1580 | 2 | F | Corrections to Control Plane CIoT 5GS Optimisation description | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1581 | - | F | Alignment of the term Early Data Transmission | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1586 | 3 | B | Network request re-activation of user-plane resources | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1587 | 1 | F | PMF message delivery | 16.2.0 | +| 2019-09 | SP#85 | SP-190613 | 1588 | 3 | F | AMF capability of Network Slice-Specific Authentication and Authorization | 16.2.0 | +| 2019-09 | SP#85 | SP-190622 | 1589 | 3 | F | Priority of CHF selection | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1596 | 1 | B | Clarify short DRX cycle length CM-CONNECTED with RRC inactive for eMTC | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1598 | 3 | F | Clarification on NEF discovery by an AF | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1604 | - | F | Exclusive Gating Mechanism | 16.2.0 | +| 2019-09 | SP#85 | SP-190611 | 1607 | 1 | F | Update P-CSCF Discovery using NRF | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1608 | 1 | F | GUAMI allocation for standalone non-public network | 16.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|----|---|---------------------------------------------------------------------------------------|--------| +| 2019-09 | SP#85 | SP-190607 | 1622 | - | F | Relation between Group and Set | 16.2.0 | +| 2019-09 | SP#85 | SP-190607 | 1624 | 3 | F | Network Function/NF Service Context | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1632 | 3 | F | Clarification on strictly periodic timer in relation to MICO mode. | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1636 | 2 | F | Mandatory support of ATSSS-LL for PDU Sessions of type Ethernet | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1637 | 3 | F | Update of 5G LAN-type service feature description | 16.2.0 | +| 2019-09 | SP#85 | SP-190608 | 1643 | 2 | C | Clarifications on URLLC support | 16.2.0 | +| 2019-09 | SP#85 | SP-190608 | 1644 | 1 | F | Clarification and correction to AF response | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1646 | 1 | F | MA PDU IP Address/Prefix Handling in UPF | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1647 | 1 | F | Use of NW instance for N19 interface | 16.2.0 | +| 2019-09 | SP#85 | SP-190609 | 1650 | 1 | F | Corrections for devices that do not support 5GC NAS over WLAN access | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1652 | - | F | Correction to protocol stacks for RTT measurements | 16.2.0 | +| 2019-09 | SP#85 | SP-190610 | 1653 | 3 | F | Clarification about an MA PDU Session using only MPTCP functionality | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1659 | 2 | C | Support of forwarding of broadcast and multicast packets | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1660 | 2 | C | Address editor's notes for TSN | 16.2.0 | +| 2019-09 | SP#85 | SP-190607 | 1664 | 4 | F | eSBA SMF and PCF selection-option 2 | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1665 | 1 | F | Clarification on Preferred Network Behaviour for CIoT 5GS Optimisations | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1669 | 1 | F | Removal of eDRX support with RRC_INACTIVE for NB-IoT | 16.2.0 | +| 2019-09 | SP#85 | SP-190605 | 1670 | 2 | F | UPF Service Area awareness for keeping UL N3 Tunnel available | 16.2.0 | +| 2019-09 | SP#85 | SP-190612 | 1671 | 3 | F | Correction on data collection from an AF | 16.2.0 | +| 2019-09 | SP#85 | SP-190618 | 1675 | 2 | C | Modification to the QoS parameters mapping for 5GS Bridge configuration | 16.2.0 | +| 2019-09 | SP#85 | SP-190612 | 1677 | 1 | F | Updating the stored information in NRF to support BSF discovery | 16.2.0 | +| 2019-09 | SP#85 | SP-190622 | 1678 | 5 | C | On the usage of rateRatio, one-step vs two-step sync operation and dedicated QoS Flow | 16.2.0 | +| 2019-12 | SP#86 | SP-191068 | 1363 | 3 | B | Identification of LTE-M (eMTC) traffic | 16.3.0 | +| 2019-12 | SP#86 | SP-191076 | 1373 | 2 | F | Corrections to Trusted Non-3GPP Access Network selection | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1459 | 3 | F | Correcting AMF selection | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1472 | 2 | F | Correcting behavior if binding indication is not provided | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1473 | 4 | F | Correcting delegated discovery and selection and the use of IDs in binding | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1485 | 3 | F | Service Gap Control at IWK | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1486 | 1 | F | Serving PLMN rate control parameters in modification procedure | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1527 | 3 | F | SMF Set and UPF | 16.3.0 | +| 2019-12 | SP#86 | SP-191076 | 1553 | 2 | F | Completing the introduction of TNGF in 23.501 | 16.3.0 | +| 2019-12 | SP#86 | SP-191088 | 1564 | 3 | F | Correction to deletion of PLMN-assigned UE Radio Capability ID | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1576 | 2 | F | Correction of UE Radio Capability Update IE encoding | 16.3.0 | +| 2019-12 | SP#86 | SP-191088 | 1592 | 10 | F | Resolution of Editor's Note on UCMF-AMF interaction | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1594 | 3 | F | I-NEF in Interworking Scenarios | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1623 | 2 | F | NRF use of UDR Group ID Mapping service | 16.3.0 | +| 2019-12 | SP#86 | SP-191080 | 1654 | 2 | F | UE related analytics for UPF selection | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1666 | 8 | F | Corrections to Small Data Rate Control and Exception Reporting | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1667 | 4 | B | Introduction of RRC Connection Re-Establishment for CP | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1679 | 2 | F | Clarification on target address in service request message | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1687 | 1 | A | Condition for the UE to provide a Requested NSSAI | 16.3.0 | +| 2019-12 | SP#86 | SP-191076 | 1688 | - | F | Network slicing impacts of Wireless and Wireline Convergence | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1689 | 2 | F | Support of TAs with heterogeneous support of eDRX | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1690 | 2 | F | Control Plane CIoT 5GS Optimisations restriction on NR | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1692 | 1 | F | Addition of I-NEF to Network Functions | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1693 | 1 | F | Service Exposure in Interworking Scenarios | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1695 | 2 | F | Correction to PPI setting control over N4 | 16.3.0 | +| 2019-12 | SP#86 | SP-191082 | 1697 | - | F | Interaction between ETSUN and CIoT. | 16.3.0 | +| 2019-12 | SP#86 | SP-191082 | 1698 | 1 | F | Clarifications to ETSUN specification | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1702 | 3 | F | Clarification on QoS Support for ATSSS | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1703 | 3 | F | Clarification on DNN replacement | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1710 | 4 | F | Clarification on N6 traffic routing information for Ethernet type PDU Session | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1711 | 1 | F | clarification on N6-based traffic forwarding of 5G-VN | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1714 | 2 | F | MA PDU Upgrade in modification procedure | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1715 | 1 | F | Delegated discovery and selection in SCP for CHF and SMSF | 16.3.0 | +| 2019-12 | SP#86 | SP-191073 | 1716 | 1 | C | Update N4 rules for QoS Monitoring | 16.3.0 | +| 2019-12 | SP#86 | SP-191088 | 1717 | 2 | F | Clarification on UE capability update | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1721 | 2 | F | Removal of ENs for control plane congestion control | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1722 | 2 | F | Multicast forwarding for Ethernet type PDU Session | 16.3.0 | +| 2019-12 | SP#86 | SP-191081 | 1723 | 2 | F | Alignments to support Network Slice-Specific Authentication and Authorization | 16.3.0 | +| 2019-12 | SP#86 | SP-191082 | 1726 | 2 | F | Clarification on IPv6 Router Advertisement message in ETSUN | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1728 | 1 | F | SMF selection clarification | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1729 | 4 | F | Group ID and Set ID | 16.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------|--------| +| 2019-12 | SP#86 | SP-191081 | 1730 | 1 | F | AMF redirection at handover from 4G to 5G | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1733 | 1 | F | Clarification of Access Availability report via N4 | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1734 | 1 | F | Clarification of terms in secondary authentication | 16.3.0 | +| 2019-12 | SP#86 | SP-191084 | 1735 | 1 | B | Extension of standardized 5QI to QoS characteristics mapping table to accommodate enhanced V2X requirements | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1736 | 2 | F | Determination of Emergency Services Fallback support in the AMF | 16.3.0 | +| 2019-12 | SP#86 | SP-191080 | 1737 | - | F | UDM Discovery by Internal Group ID | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1738 | 3 | F | UE may provide NSSAI in AS for initial registration | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1739 | 5 | F | No impact on IMS voice session by a change of the IMS voice over PS session indicator during fallback | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1740 | 1 | F | Clarification of Homogeneous Support of IMS Voice over PS Sessions | 16.3.0 | +| 2019-12 | SP#86 | SP-191073 | 1742 | 1 | F | Enhancement of UP path management based on the coordination with AFs | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1743 | 2 | F | PCF selection for multiple PDU Sessions to the same DNN and S-NSSAI | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1745 | - | F | Extended NAS timers for CE mode B | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1746 | 1 | F | Correcting AMF decision to set CP only indicator | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1747 | 7 | F | 5GS Bridge Management | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1750 | 3 | F | Completing QoS and TSCAI mapping | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1751 | 3 | F | Clarifying N3IWF access to SNPN | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1752 | 3 | F | Clarifying CAG handling during RRC resume procedure | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1754 | 1 | F | Update to Clause 4.2.7 Reference Points | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1755 | 3 | F | Corrections on Session-AMBR setting and enforcement | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1757 | 1 | A | Correction on PCF selection and discovery | 16.3.0 | +| 2019-12 | SP#86 | SP-191078 | 1759 | - | F | UDR service for mapping IMS Public Identity to HSS Group ID for HSS selection | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1765 | 3 | F | Notification receiver information in a subscription | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1766 | 3 | F | Correcting delegated discovery for PCF | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1767 | 2 | F | 23.501:PCF provides PCC rule to SMF based on Local routing indication in subscription information | 16.3.0 | +| 2019-12 | SP#86 | SP-191073 | 1768 | 2 | F | Delivery of SMF waiting time to AF for session continuity | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1769 | 3 | F | Corrections for performance measurements | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1770 | 2 | F | Correction on TNLA binding | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1771 | 3 | F | General corrections for MA PDU sessions | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1772 | 2 | F | Corrections to interworking with EPS for ATSSS | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1773 | 2 | F | N4 impacts due to ATSSS | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1774 | 3 | F | Corrections to steering functionalities description | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1775 | 2 | F | PCF selection for DNN replacement | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1778 | 2 | F | Remote Interference Management support | 16.3.0 | +| 2019-12 | SP#86 | SP-191084 | 1785 | 2 | F | Corrections to handling of Alternative QoS Profiles | 16.3.0 | +| 2019-12 | SP#86 | SP-191080 | 1787 | 7 | F | Consistency on Definitions related to NWDAF | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1792 | 2 | F | EDT support for UP CIoT Optimisation | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1797 | 3 | F | Support of PLMN managed NIDs | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1798 | 2 | F | Support of NG-RAN sharing options for NPN | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1801 | 2 | F | TS 23.501: PEI format for non-3GPP devices | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1802 | 2 | F | TSN 5QI clarification and static TSC QoS Flow establishment | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1804 | 3 | F | 5GS bridge model interpretation | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1806 | 5 | F | Revision on MDBV mapping | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1815 | 2 | F | clarification on the Qos parameters mapping and TSCAI creation | 16.3.0 | +| 2019-12 | SP#86 | SP-191073 | 1816 | - | F | Clarification on the Standardized or pre-configured 5QI parameters modification | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1817 | 1 | F | Expected UE behaviour data contents | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1818 | 2 | F | Correction of Small Data Rate Control interworking | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1819 | 1 | F | Network selection correction | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1821 | 3 | F | Clarification of SMF management of 5G-VN PDU sessions | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1822 | 3 | F | Clarification of UPF selection for 5G-VN communication | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1823 | 1 | F | Clarification of use of AF influence in 5G-VN | 16.3.0 | +| 2019-12 | SP#86 | SP-191088 | 1828 | 3 | F | Misleading RACS architecture pictures | 16.3.0 | +| 2019-12 | SP#86 | SP-191088 | 1829 | 6 | F | removing requirement that TAC+SV is used to identify UE model in manufacturer assigned ID | 16.3.0 | +| 2019-12 | SP#86 | SP-191086 | 1833 | 3 | F | changing IAB-MT to IAB-UE | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1837 | 2 | F | Correction on applicability of slicing to more than 3GPP access | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1839 | 2 | F | Incorrect reference to clause in specification | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1840 | 1 | F | Alignment with SA5 on Charging for 5G connection and mobility domain | 16.3.0 | +| 2019-12 | SP#86 | SP-191082 | 1842 | 3 | F | PDU Session with SSC mode 2/3 | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1845 | 3 | C | General description and data volume reporting for NR in unlicensed bands | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1847 | 2 | B | Access restrictions for primary and secondary RAT | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1849 | 1 | B | Introduction of UE specific DRX for NB-IOT | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1853 | 1 | A | Correction of QFI value in QER | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|-----------------------------------------------------------------------------------|--------| +| 2019-12 | SP#86 | SP-191073 | 1854 | 5 | F | Management of GBR QoS Flows at handover | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1857 | 5 | F | Updates to the 5G VN broadcast solution | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1859 | 4 | F | PDU session anchor terminology clarification | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1860 | 4 | F | Remove incorrect reasoning of default MDBV value setting | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1868 | 5 | F | ATSSS Link-Specific Multipath IP Address Configuration | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1869 | 10 | F | ATSSS Steering of non-MPTCP Traffic | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1870 | 3 | F | ATSSS PMF Protocol over UDP | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1875 | 2 | F | Interworking with EPS for the MA PDU Session | 16.3.0 | +| 2019-12 | SP#86 | SP-191073 | 1878 | 2 | F | 5G URLLC Handling PDU Session Failure | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1879 | 2 | F | UPF selection for 5G URLLC PDU Sessions | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1881 | 3 | F | UE identifier for SNPN | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1887 | 2 | F | N4 Impacts - Bridge Management | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1888 | 5 | F | Clarification for TSC QoS Mapping clause | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1889 | 2 | F | TSC PDU Session Restrictions | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1890 | 7 | F | TSCAI granularity | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1893 | 3 | F | UPF functional update for TSC | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1895 | - | F | Clarification on SMF identifier in HR roaming | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1899 | 2 | F | Clarifications on CN assistance information sent to the RAN | 16.3.0 | +| 2019-12 | SP#86 | SP-191086 | 1901 | 1 | B | Handling of IAB-indication to 5GC | 16.3.0 | +| 2019-12 | SP#86 | SP-191086 | 1902 | 1 | B | Handling of OAM traffic for IAB-node | 16.3.0 | +| 2019-12 | SP#86 | SP-191086 | 1903 | 1 | B | Support of IAB operation in EN-DC mode | 16.3.0 | +| 2019-12 | SP#86 | SP-191086 | 1905 | 1 | F | Mobility support limitation for IAB | 16.3.0 | +| 2019-12 | SP#86 | SP-191078 | 1912 | - | F | Including IMS related interfaces in list of 5G interfaces | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1918 | - | F | Clarification on UE mobility event notification | 16.3.0 | +| 2019-12 | SP#86 | SP-191076 | 1920 | 1 | F | Avoid specifying SUPI / SUCI and PEI used for FN RG both in 23.501 and 23.316 | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1923 | 2 | F | Corrections to ATSSS capabilities of a MA PDU Session | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1924 | 1 | F | Applicability of UP Security Policy to a MA PDU Session | 16.3.0 | +| 2019-12 | SP#86 | SP-191082 | 1929 | 3 | F | (I)SMF notifications: which SMF events need to be supported by ISMF | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1932 | 2 | F | Clarification on the PDU session management for VN | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1934 | 1 | F | Correction on SMSF change | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1935 | 2 | F | Correction on UE context handling during inter system mobility | 16.3.0 | +| 2019-12 | SP#86 | SP-191088 | 1936 | 2 | F | Inclusion of Version Identifier in PLMN assigned ID | 16.3.0 | +| 2019-12 | SP#86 | SP-191077 | 1937 | 1 | F | Corrections for link-specific multipath address/prefix and MPTCP proxy IP address | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1940 | 3 | F | Selecting SMF that support static IP address | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1941 | 4 | F | Number of EBIs | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1942 | 2 | F | Notification URI | 16.3.0 | +| 2019-12 | SP#86 | SP-191082 | 1943 | 2 | F | I-SMF handling of N4 Information | 16.3.0 | +| 2019-12 | SP#86 | SP-191090 | 1945 | - | F | Correction of implementation of CR #1321 | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1949 | 1 | F | Clarification on the PCF selection | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1956 | - | A | Removal of wrongly implemented Network Slicing CR #1031 and mirror CR #1131 | 16.3.0 | +| 2019-12 | SP#86 | SP-191073 | 1971 | - | F | Correction on support of redundant transmission on N3/N9 interfaces | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1972 | - | F | Clarification on Control Plane Only Indicator | 16.3.0 | +| 2019-12 | SP#86 | SP-191073 | 1973 | 1 | F | Correction and clarification to AF influence in URLLC | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1976 | 2 | F | ULCL/BP based on the local routing policy | 16.3.0 | +| 2019-12 | SP#86 | SP-191081 | 1979 | 2 | F | On NSSAA Services | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1981 | 5 | F | Applying Per-Stream Filtering and Policing | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1985 | 1 | A | S-NSSAI setting for emergency service | 16.3.0 | +| 2019-12 | SP#86 | SP-191074 | 1986 | 2 | B | Solution on support of NAT in 5GS | 16.3.0 | +| 2019-12 | SP#86 | SP-191080 | 1992 | 1 | F | Corrections to NWDAF discovery and selection | 16.3.0 | +| 2019-12 | SP#86 | SP-191068 | 1993 | - | F | UE support of CP optimization over NB-IoT | 16.3.0 | +| 2019-12 | SP#86 | SP-191071 | 1994 | 1 | F | Correction of CHF discovery to consider eSBA binding principles | 16.3.0 | +| 2019-12 | SP#86 | SP-191092 | 1997 | 3 | F | PNI-NPN - Reusing NSSAI for AMF selection when NPN isolation is needed | 16.3.0 | +| 2019-12 | SP#86 | SP-191084 | 2001 | - | F | Correction on the support of V2X in 5GS | 16.3.0 | +| 2019-12 | SP#86 | SP-191086 | 2003 | - | F | Remove protocol stack diagrams for IAB | 16.3.0 | +| 2019-12 | SP#86 | SP-191086 | 2004 | 1 | F | Remove Editor's Notes for IAB related clauses | 16.3.0 | +| 2019-12 | SP#86 | SP-191081 | 2005 | 1 | F | Correction on pending NSSAA indication to UE | 16.3.0 | +| 2019-12 | SP#86 | SP-191082 | 2006 | - | F | ETSUN: correction for I-SMF trace | 16.3.0 | +| 2020-03 | SP#87E | SP-200075 | 1482 | 7 | F | Alignments and corrections to Non-Public Network functionality | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 1520 | 4 | F | PLMN+CAG information - minimum, maximum storage and survival of power cycle | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 1595 | 2 | F | 23.501 Supporting for AF providing UE IP address(es) for 5G VN group PDU sessions | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 1668 | 4 | F | Clarification to MICO mode and Periodic Registration Timer Control | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 1691 | 3 | F | Alignment with TS 23.502 and clarification on Extended Buffering | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 1749 | 7 | F | Item#4: Apply StaticFilteringEntry information in 5GS | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|----------------------------------------------------------------------------------------------------------|--------| +| 2020-03 | SP#87E | SP-200069 | 1782 | 4 | F | Applicability of PS data off to ATSSS and MA PDU sessions | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 1783 | 6 | F | UE IDLE over N3GPP responding to indication of DL data when access is available | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 1799 | 7 | F | Support of CAG ID privacy | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 1848 | 14 | F | Introduction of the Inter PLMN UP functionality in the architecture | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 1882 | 4 | F | UDM - AUSF Discovery & Selection in an SNPN | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 1947 | 3 | F | Corrections to general MA PDU session handling | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 1951 | 4 | F | Clarifying gPTP message forwarding for multiple TSN PDU sessions | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 1957 | 2 | F | Adding ATSSS functionality into the UPF | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 1980 | 3 | F | MDBV mapping and configuration for TSC QoS Flow | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2007 | 1 | F | Correction on TSCAI: TSN open issue #1 | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2009 | 1 | F | Correct errors in Port Management information table | 16.4.0 | +| 2020-03 | SP#87E | SP-200071 | 2011 | 1 | F | Re-allowing UE for services after the NSSAA revocation | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2015 | 2 | F | CN component of the PDB is configured per UL and DL | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2017 | 1 | F | Correcting AMF selection | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2019 | 2 | F | Procedures for handover between SNPN and PLMN | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2020 | 3 | F | MTU size considerations | 16.4.0 | +| 2020-03 | SP#87E | SP-200065 | 2021 | 4 | F | Binding for notification reselection corrections | 16.4.0 | +| 2020-03 | SP#87E | SP-200065 | 2022 | 3 | F | Correcting delegated discovery for PCF | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2026 | 1 | F | Correction of current context and using 5GS bridge to refer to 5GS functions act as TSN bridge | 16.4.0 | +| 2020-03 | SP#87E | SP-200068 | 2027 | 2 | F | Support of Wireline access requires both N1 signalling and N2 signalling | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2028 | 3 | F | Clarification on the 5G VN usage of IP Multicast mechanisms from TS 23.316 | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2029 | 4 | F | Usage of Ethernet PDU Session Information to support 5G VN Group point to point Ethernet traffic | 16.4.0 | +| 2020-03 | SP#87E | SP-200072 | 2030 | 1 | F | Criteria for I-SMF (and V-SMF) selection and change including also ATSSS cases | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2031 | 1 | F | Support of TNAP identifier when the Trusted Access does not correspond to WLAN | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 2032 | 3 | F | ATSSS capabilities cooperation between the UE and UPF | 16.4.0 | +| 2020-03 | SP#87E | SP-200068 | 2033 | 4 | F | Access type and RAT type per Non-3GPP accesses | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2035 | - | F | Service Gap Control handling at UE side during IWK | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 2036 | 2 | F | Corrections for handling of serving networks not supporting ATSSS | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2038 | 2 | F | Requested NSSAI provided at the AS layer | 16.4.0 | +| 2020-03 | SP#87E | SP-200071 | 2040 | 1 | F | Clarification on pending NSSAI in Network Slice-Specific Authentication and Authorization | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2042 | 4 | F | Item #5 Support of emergency services for Rel-16 UE not supporting CAG in CAG cells | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 2044 | 1 | F | Clarification the deregistration in single access | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2046 | 2 | F | Clarification of N2 based handover considering CAG IDs supported by the target NG-RAN node | 16.4.0 | +| 2020-03 | SP#87E | SP-200068 | 2047 | 1 | F | TS23.501 - Correction on User Location Information | 16.4.0 | +| 2020-03 | SP#87E | SP-200072 | 2048 | - | F | Paging Policy Differentiation | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2050 | 2 | F | TSN CN PDB | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 2051 | - | F | Access availability report configuration in the UPF | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2053 | 3 | B | Assistance indication for WUS grouping | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2054 | 2 | F | Correction on MDBV and CN PDB | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2056 | 2 | F | Default ARP values for dedicated QoS Flows | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2057 | 1 | F | Correction of ARP description | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2060 | 4 | F | Clarification on the EBI context if target MME does not support EBI extension during 5GS to EPS mobility | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2064 | 3 | F | Item#4: Clarification on the PSFP and Qbv for TSC traffic | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2067 | 1 | F | Clarifying TSCAI based on TSN clock used by PSFP gate operation | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2069 | 5 | F | Clarifying UL configuration issue | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2070 | 2 | F | Traffic Forwarding issue at UPF side | 16.4.0 | +| 2020-03 | SP#87E | SP-200075 | 2073 | 2 | F | #1 Clarification for supporting 5G VN group communication | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2074 | 3 | F | #2_ clarification on N6-based traffic forwarding of 5G-VN | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 2079 | 1 | F | Clarification on multiple PDU Session anchors for a MA PDU Session | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2084 | 3 | F | Correction to Emergency services support by SNPN | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2085 | 4 | F | Correction to TSN stream aggregation and QoS parameter mapping guidelines | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2087 | 1 | F | Clarification on the use of reference points N14 and N26 | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2088 | 1 | F | NAS signalling of CP Relocation Indication Truncated 5G-S-TMSI Parameters | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2089 | 3 | F | Correction for MO Exception Data Rate and its inclusion in charging information | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2097 | 2 | F | Correction to Access SNPN via PLMN | 16.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------|--------| +| 2020-03 | SP#87E | SP-200060 | 2100 | 1 | A | Alignment with SA5 on Charging for SMS over NAS | 16.4.0 | +| 2020-03 | SP#87E | SP-200064 | 2102 | 1 | F | NEF service to support location transfer | 16.4.0 | +| 2020-03 | SP#87E | SP-200074 | 2106 | 2 | F | UCMF provisioning correction | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2108 | 3 | F | Clarification on the CN tunnel info allocation and release | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2109 | 2 | F | Clarification on internal group ID usage | 16.4.0 | +| 2020-03 | SP#87E | SP-200065 | 2111 | 2 | F | Update of the binding related descriptions | 16.4.0 | +| 2020-03 | SP#87E | SP-200074 | 2116 | 1 | F | On UCMF discovery | 16.4.0 | +| 2020-03 | SP#87E | SP-200074 | 2117 | - | F | RACS and NB-IoT corrections | 16.4.0 | +| 2020-03 | SP#87E | SP-200067 | 2122 | 2 | F | Correction for the wrongly implemented CR1785r8 | 16.4.0 | +| 2020-03 | SP#87E | SP-200067 | 2123 | 5 | F | Corrections of Alternative QoS Profiles - proper TS version | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2128 | 1 | F | Sending EPS APN rate control information during PDU session establishment | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2132 | - | F | Correction to Reference Points for Non-3GPP Access | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2133 | 1 | F | Clarification of TSN stream and traffic class | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2136 | 1 | F | Correction to UE configuration update procedure conditions for re-registration | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2137 | 1 | F | Selecting network for Emergency services | 16.4.0 | +| 2020-03 | SP#87E | SP-200070 | 2140 | 1 | F | Corrections to UE mobility event notification | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 2141 | - | F | QoS handling of MA PDU Session for interworking with N26 | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2143 | 1 | F | Correct the transfer and determination of the bridge delay related parameters | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2147 | 1 | F | PDU Session release when Control Plane Only indication becomes not applicable | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2148 | 1 | F | Correction on PTW determination | 16.4.0 | +| 2020-03 | SP#87E | SP-200069 | 2150 | - | F | Correction on MA PDU Session request indication | 16.4.0 | +| 2020-03 | SP#87E | SP-200067 | 2154 | 1 | F | Update N4 rules to support QoS Monitoring and ATSSS | 16.4.0 | +| 2020-03 | SP#87E | SP-200081 | 2157 | - | F | Subscription based access restriction for E-UTRA in unlicensed | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2158 | 1 | F | Subscription based access restriction for LTE-M | 16.4.0 | +| 2020-03 | SP#87E | SP-200070 | 2159 | 1 | F | Clarification on NWDAF information maintained in NRF | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2160 | 1 | F | Missing capabilities in 5GMM Capability IE | 16.4.0 | +| 2020-03 | SP#87E | SP-200074 | 2161 | - | D | Editorial updates in RACS clauses | 16.4.0 | +| 2020-03 | SP#87E | SP-200062 | 2163 | - | D | Mega CR on editorial corrections for 5G_CIoT | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2164 | 1 | F | Correction to network selection with multiple subscribed SNPNS | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2165 | 1 | F | Clarification for Support for multiple TSN working domains | 16.4.0 | +| 2020-03 | SP#87E | SP-200072 | 2169 | 1 | F | ETSUN related CR for non-FASMO corrections | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2171 | - | F | Adding reference points in the Architecture to support Time Sensitive Communication | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2172 | 1 | F | UPF selection based on traffic classes and VLAN | 16.4.0 | +| 2020-03 | SP#87E | SP-200060 | 2175 | 1 | A | UE capability match request during the registration procedure | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2178 | - | F | Replace IEEE802.1Qbv with IEEE802.1Q | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2183 | 1 | F | Correction on QoS Flow Binding about TSN | 16.4.0 | +| 2020-03 | SP#87E | SP-200068 | 2186 | - | F | Correction for support of N5CW devices to access 5GC via trusted WLAN access networks | 16.4.0 | +| 2020-03 | SP#87E | SP-200065 | 2190 | 1 | F | Endpoint Address correction | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2191 | 1 | F | Clarification on PS Data Off for non-3GPP access PDU Session | 16.4.0 | +| 2020-03 | SP#87E | SP-200071 | 2192 | 1 | F | Handling of NSSAA during N2 handover procedure | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2194 | 1 | F | Clear description of Access to an SNPNS | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2195 | 1 | F | AMF Management | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2197 | 1 | F | Vertical_LAN 5G-VN related CR for non-FASMO corrections | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2198 | 1 | F | Vertical_LAN TSN related CR for non-FASMO corrections | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2199 | - | F | Vertical_LAN NPN related CR for non-FASMO corrections | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2201 | 1 | F | Correction on area of interest used by SMF | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2202 | 1 | F | TSN working domain and aggregation | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2204 | 1 | F | Updates for Bridge Delay information reporting and QoS mapping | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2205 | - | F | Incorrect reference to IEEE 1588 Timestamp data type in normative Annex H.2 | 16.4.0 | +| 2020-03 | SP#87E | SP-200078 | 2209 | 1 | F | Clarification on network instance determination | 16.4.0 | +| 2020-03 | SP#87E | SP-200076 | 2212 | 1 | F | UPF selection based on TSN parameters and context correction | 16.4.0 | +| 2020-03 | SP#87E | SP-200068 | 2214 | 1 | F | Inclusion of Requested NSSAI in AN Parameters for non-3GPP access | 16.4.0 | +| 2020-03 | SP#87E | SP-200068 | 2216 | 1 | F | 5WWC related CR for non-FASMO corrections | 16.4.0 | +| 2020-03 | SP#87E | SP-200293 | 2179 | 3 | F | Change of the restriction of enhanced coverage | 16.4.0 | +| 2020-07 | SP#88E | SP-200433 | 2131 | 2 | F | Support of ETSUN and ATSSS | 16.5.0 | +| 2020-07 | SP#88E | SP-200424 | 2138 | 2 | F | Selection of direct vs indirect communication | 16.5.0 | +| 2020-07 | SP#88E | SP-200428 | 2153 | 1 | F | Steering modes for GBR traffic | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2170 | 2 | F | QoS container vs. TSCAI input container | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2217 | 1 | F | Fix terminology on maximum number of CAGs per cell instead of per NG-RAN node | 16.5.0 | +| 2020-07 | SP#88E | SP-200425 | 2222 | 1 | F | Update of QoS monitoring for URLLC based on RAN WG3 decision | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2223 | 1 | F | Clarification on the supported and non-supported features and services for SNPNS | 16.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------|--------| +| 2020-07 | SP#88E | SP-200438 | 2224 | 1 | F | SMF to request the UE IP address from the DN-AAA server based on subscription information | 16.5.0 | +| 2020-07 | SP#88E | SP-200433 | 2225 | 1 | F | Support of ETSUN within and between PLMN(s) | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2227 | 1 | F | TSN QoS information for DL traffic | 16.5.0 | +| 2020-07 | SP#88E | SP-200437 | 2232 | - | F | Common Network Exposure | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2234 | 1 | F | Alignment of traffic forwarding information | 16.5.0 | +| 2020-07 | SP#88E | SP-200436 | 2236 | 1 | F | Missing the Radio Capability Filtering linkage to the UE Radio Capability ID | 16.5.0 | +| 2020-07 | SP#88E | SP-200552 | 2238 | 1 | F | ARP values for additional QoS Flows | 16.5.0 | +| 2020-07 | SP#88E | SP-200428 | 2240 | - | F | Handling of mobility when target does not support ATSSS | 16.5.0 | +| 2020-07 | SP#88E | SP-200420 | 2242 | - | A | UE radio capability retrieval | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2246 | 1 | F | QoS parameters mapping: GFBR, ARP | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2247 | 1 | F | UPF selection criteria | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2248 | - | F | Missing change in Annex I | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2251 | 1 | F | Correction on the derived MDBV | 16.5.0 | +| 2020-07 | SP#88E | SP-200436 | 2254 | - | F | Correction on the interface N58 b/w NEF and AF | 16.5.0 | +| 2020-07 | SP#88E | SP-200436 | 2255 | 1 | F | Support of multiple radio capability formats | 16.5.0 | +| 2020-07 | SP#88E | SP-200436 | 2257 | 1 | F | Clarification on Version ID | 16.5.0 | +| 2020-07 | SP#88E | SP-200428 | 2258 | 1 | F | Corrections to steering modes | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2263 | 1 | F | NF selection in SNPN 5GC | 16.5.0 | +| 2020-07 | SP#88E | SP-200432 | 2268 | 1 | F | Handling of pending NSSAI | 16.5.0 | +| 2020-07 | SP#88E | SP-200424 | 2269 | 2 | F | Enablers for multiple SCPs (23.501) | 16.5.0 | +| 2020-07 | SP#88E | SP-200432 | 2270 | 1 | F | Removal of service area for UE registration with empty Allowed NSSAI due to pending NSSAA | 16.5.0 | +| 2020-07 | SP#88E | SP-200424 | 2271 | 1 | F | Corrections to Principles for Binding, Selection and Reselection | 16.5.0 | +| 2020-07 | SP#88E | SP-200432 | 2274 | 1 | F | Clarification for the NSSAI in NSSAA procedure of roaming scenario | 16.5.0 | +| 2020-07 | SP#88E | SP-200428 | 2276 | 1 | F | MA-PDU Session establishment in Non-allowed Area | 16.5.0 | +| 2020-07 | SP#88E | SP-200422 | 2277 | 1 | F | Small data rate control enforcement of normal and exception data | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2278 | 1 | F | Correcting 5GS TSN bridge delays | 16.5.0 | +| 2020-07 | SP#88E | SP-200430 | 2279 | 1 | F | Corrections to HSS Discovery | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2285 | - | F | Annex I Clarification | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2287 | 1 | F | Bridge Management Clarification | 16.5.0 | +| 2020-07 | SP#88E | SP-200428 | 2292 | 1 | F | Correction on ATSSS rule generation | 16.5.0 | +| 2020-07 | SP#88E | SP-200425 | 2293 | 1 | F | Correction of RAN part of packet delay for QoS monitoring | 16.5.0 | +| 2020-07 | SP#88E | SP-200420 | 2299 | 1 | A | Incorrect NOTE 14 for 5QI 3 | 16.5.0 | +| 2020-07 | SP#88E | SP-200422 | 2302 | 1 | F | Corrections to restriction of use of Enhanced Coverage | 16.5.0 | +| 2020-07 | SP#88E | SP-200428 | 2303 | 1 | F | Corrections related to UPF support of RTT measurements without PMF | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2305 | 1 | F | Correction on RAN sharing for NPN networks | 16.5.0 | +| 2020-07 | SP#88E | SP-200427 | 2308 | 1 | F | Correction on RAT type | 16.5.0 | +| 2020-07 | SP#88E | SP-200427 | 2309 | - | F | Correction on wireline access and reference point between N5CW device and TWAP | 16.5.0 | +| 2020-07 | SP#88E | SP-200552 | 2311 | 1 | C | Remove restriction for support of eCall over NR | 16.5.0 | +| 2020-07 | SP#88E | SP-200433 | 2315 | 1 | F | Pause of Charging | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2319 | 1 | F | Alignment on Identifying PDU session in TSN AF | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2321 | 1 | F | Clarification on the bridge delay | 16.5.0 | +| 2020-07 | SP#88E | SP-200428 | 2327 | - | F | Correction of reference to mptcp RFC8684 | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2334 | 1 | F | Clarify the 5GS Bridge ID | 16.5.0 | +| 2020-07 | SP#88E | SP-200432 | 2336 | - | F | Correction on the value of S-NSSAIs for NSSAA | 16.5.0 | +| 2020-07 | SP#88E | SP-200551 | 2338 | 1 | F | Correction on description about area of interest | 16.5.0 | +| 2020-07 | SP#88E | SP-200551 | 2339 | 1 | F | Reordering DL data during SR procedure | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2340 | 1 | F | Correction for TSCAI Calculation | 16.5.0 | +| 2020-07 | SP#88E | SP-200551 | 2341 | - | F | Correction on QoS handling for priority sessions | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2344 | 1 | F | Correction of the gPTP domain and the selection of UPF | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2346 | 1 | F | Update on 5G VN group subscription data retrieval | 16.5.0 | +| 2020-07 | SP#88E | SP-200551 | 2347 | 1 | F | Update on IPUPS functionality | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2348 | 1 | F | Support of 5G LAN-type service under ETSUN architecture | 16.5.0 | +| 2020-07 | SP#88E | SP-200551 | 2350 | - | F | Correction on AF influence on traffic routing | 16.5.0 | +| 2020-07 | SP#88E | SP-200551 | 2351 | 1 | F | Correction on Control and User Plane Protocol Stacks | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2352 | 1 | F | Support of emergency services for Rel-15 UE in CAG cells | 16.5.0 | +| 2020-07 | SP#88E | SP-200424 | 2353 | 1 | F | Update of NF profile | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2363 | 1 | F | VLAN Information configuration and information exchange | 16.5.0 | +| 2020-07 | SP#88E | SP-200433 | 2365 | 1 | F | MA PDU Session not supported in ETSUN case | 16.5.0 | +| 2020-07 | SP#88E | SP-200515 | 2230 | 2 | F | Splitting port management information into port- and bridge-specific information | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2135 | 5 | F | Updating the UE with new CAG information | 16.5.0 | +| 2020-07 | SP#88E | SP-200588 | 2370 | 2 | F | Alignment on Alternative QoS Profile
(This CR was noted, corrected to implement CR2730R1 in v16.5.1) | 16.5.0 | +| 2020-07 | SP#88E | SP-200420 | 1732 | 5 | A | Reflective QoS | 16.5.0 | +| 2020-07 | SP#88E | SP-200422 | 2243 | 3 | F | Service Area Restriction clarification | 16.5.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------|--------| +| 2020-07 | SP#88E | SP-200610 | 2361 | 3 | F | PDU Session release when Control Plane Only indication is not available | 16.5.0 | +| 2020-07 | SP#88E | SP-200432 | 2368 | 1 | F | PCO support for DNS over (D)TLS (avoiding attacks against DNS traffic) | 16.5.0 | +| 2020-07 | SP#88E | SP-200427 | 2369 | 1 | F | Clarification of the Support of the Frame Routing Feature | 16.5.0 | +| 2020-07 | SP#88E | SP-200433 | 2371 | 1 | F | URLLC - TSN interworking with ETSUN | 16.5.0 | +| 2020-07 | SP#88E | SP-200432 | 2372 | - | F | Replacing AUSF by NSSAAF to support NSSAA | 16.5.0 | +| 2020-07 | SP#88E | SP-200422 | 2374 | - | F | Removal of I-NEF | 16.5.0 | +| 2020-07 | SP#88E | SP-200422 | 2378 | 1 | F | UE specific DRX for NB-IoT RAN support clarification based on LS R2-2004057 | 16.5.0 | +| 2020-07 | SP#88E | SP-200434 | 2379 | 1 | F | Capability for HPLMN to understand whether or not the NG-RAN node supports Alternative QoS Profiles | 16.5.0 | +| 2020-07 | SP#88E | SP-200438 | 2380 | 2 | F | Handling manipulation of CAG by VPLMN -Sol 1 | 16.5.0 | +| 2020-07 | SP#88E | SP-200435 | 2382 | 1 | F | IAB support in NPN deployment | 16.5.0 | +| 2020-08 | SP#88E | SP-200434 | 2370 | 1 | F | Alignment on Alternative QoS Profile
(Correction to implementation of CR2730R2 from v16.5.0) | 16.5.1 | +| 2020-09 | SP#89E | SP-200688 | 2266 | 2 | F | Human readable name for SNPN | 16.6.0 | +| 2020-09 | SP#89E | SP-200685 | 2387 | - | F | Correction for URLLC GTP-U Path Monitoring | 16.6.0 | +| 2020-09 | SP#89E | SP-200687 | 2390 | - | F | HSS NF profile Update | 16.6.0 | +| 2020-09 | SP#89E | SP-200678 | 2391 | 1 | F | HSS Selection Update | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2392 | 1 | F | PSFP clarifications including IEEE LS response on TSN support | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2393 | 1 | F | Addressing technical comments from IEEE LS response on TSN support | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2394 | 1 | F | Addressing wording comments from IEEE LS response on TSN support | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2395 | 2 | F | Delay clarifications including IEEE LS input clarifications | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2396 | 1 | F | Solving Synchronization issues, addressing IEEE LS response | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2398 | 1 | F | Mapping GBR and Averaging Window | 16.6.0 | +| 2020-09 | SP#89E | SP-200686 | 2400 | 1 | C | UE user plane integrity protection mandatory at full rate | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2403 | 1 | F | Correction to TSN stream identification in PSFP information | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2404 | 1 | F | Correction and clarification related to the choice of PDU Session when exchanging BMIC or PMIC between TSN AF and NW-TT | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2405 | 1 | F | 5GS BMCA support and PTP port state configuration | 16.6.0 | +| 2020-09 | SP#89E | SP-200686 | 2407 | 1 | F | WUS system support for 5GC | 16.6.0 | +| 2020-09 | SP#89E | SP-200674 | 2409 | 1 | F | Routing Binding indication without delegated discovery | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2410 | 1 | F | Clarify the Announce message handling | 16.6.0 | +| 2020-09 | SP#89E | SP-200671 | 2420 | - | A | Clarification on concurrency of AS rekeying handling and Emergency Fallback procedure for R16 | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2421 | 1 | F | correction on the bridge model and NW-TT ports | 16.6.0 | +| 2020-09 | SP#89E | SP-200673 | 2424 | - | F | Overview Clarifications for multiple UP resource support for an NB-IoT UE | 16.6.0 | +| 2020-09 | SP#89E | SP-200673 | 2425 | - | F | Overview Clarifications about the CIoT optimisations during mobility to and from non-3GPP access | 16.6.0 | +| 2020-09 | SP#89E | SP-200673 | 2426 | - | F | Overview Clarifications for handling Control Plane CIoT optimisation during interworking between EPS and 5GS | 16.6.0 | +| 2020-09 | SP#89E | SP-200673 | 2427 | 1 | F | Drop downlink packets with notification of the discarded downlink packet | 16.6.0 | +| 2020-09 | SP#89E | SP-200673 | 2428 | - | F | Overview of redirecting UE via service reject to align with CT1 | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2430 | 1 | F | 23.501: Revision on PNI-NPN CAG Configuration Update | 16.6.0 | +| 2020-09 | SP#89E | SP-200674 | 2431 | 1 | F | Correction for NF instance set | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2435 | - | F | remove bridge name to align with CT3 | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2437 | 1 | F | Clarify Ethernet Frames handling for Ethernet PDU session | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2438 | 1 | F | dedicated SMF selection clarification | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2439 | 1 | F | 5G-VN clarifications | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2440 | 1 | F | Clarification on the 5G VN usage of IP Multicast mechanisms | 16.6.0 | +| 2020-09 | SP#89E | SP-200686 | 2442 | 1 | F | Support for DTLS | 16.6.0 | +| 2020-09 | SP#89E | SP-200673 | 2443 | 1 | F | Extended Connected Timer in mobility messages | 16.6.0 | +| 2020-09 | SP#89E | SP-200674 | 2444 | 1 | F | Clarifications on SCP registration and discovery procedures | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2446 | 1 | F | Resolution of open items related to IEEE LS | 16.6.0 | +| 2020-09 | SP#89E | SP-200674 | 2447 | 1 | F | Clarification on SCP selection to support multi-SCPs | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2449 | - | F | Change the Default QoS Flow to the QoS Flow with the default QoS rule | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2451 | 1 | F | Moving NW-TT ports from BMI into BMIC | 16.6.0 | +| 2020-09 | SP#89E | SP-200683 | 2452 | 1 | C | New 5QIs for OAM traffic over IAB | 16.6.0 | +| 2020-09 | SP#89E | SP-200677 | 2453 | - | F | RFC for draft-ietf-tcpm-converters | 16.6.0 | +| 2020-09 | SP#89E | SP-200688 | 2455 | 1 | F | Clarification of network sharing for NPN | 16.6.0 | +| 2020-09 | SP#89E | SP-200802 | 2383 | 2 | F | Signalling of UE Radio Capability ID in Registration procedure | 16.6.0 | +| 2020-12 | SP#90E | SP-200950 | 2228 | 4 | F | Correction of Alternative QoS Profile handling | 16.7.0 | +| 2020-12 | SP#90E | SP-200946 | 2389 | 1 | F | Handling of AAA-S address in NSSAA | 16.7.0 | +| 2020-12 | SP#90E | SP-200951 | 2408 | 2 | F | Indication of redundancy transmission | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2416 | 1 | F | TSCAI update during Handover procedure | 16.7.0 | +| 2020-12 | SP#90E | SP-200949 | 2456 | 1 | F | Correction on SMF change with eSBA | 16.7.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------|---------------| +| 2020-12 | SP#90E | SP-200953 | 2465 | 1 | F | Reject UE access to SNPN service via a PLMN to align with CT1 | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2466 | 1 | F | Clarification on gPTP handling at NW-TT acting as the GM | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2468 | 1 | F | 5G-VN clarifications | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2470 | - | F | Correction to inaccurate and misleading NOTE4 in the BMIC table | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2472 | - | F | Clarification of TSN AF role | 16.7.0 | +| 2020-12 | SP#90E | SP-200945 | 2474 | 1 | A | Correcting Xn handover at network sharing | 16.7.0 | +| 2020-12 | SP#90E | SP-200951 | 2475 | 1 | F | Correction to QoS monitoring for URLLC on GTP-U | 16.7.0 | +| 2020-12 | SP#90E | SP-200947 | 2476 | - | F | Exception data reporting and connected state | 16.7.0 | +| 2020-12 | SP#90E | SP-200959 | 2477 | - | F | V-SMF selection | 16.7.0 | +| 2020-12 | SP#90E | SP-200947 | 2481 | - | F | Correction on Enhanced Coverage Restriction | 16.7.0 | +| 2020-12 | SP#90E | SP-200947 | 2482 | - | F | Event Configuration Synchronization between 4G&5G | 16.7.0 | +| 2020-12 | SP#90E | SP-200949 | 2483 | 1 | F | Group Id from AMF to SMF removal when SCP is responsible for reselection | 16.7.0 | +| 2020-12 | SP#90E | SP-200959 | 2485 | 1 | F | Continuation of PDU sessions upon mobility to a target PLMN | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2486 | 1 | F | Clarification of CAG information | 16.7.0 | +| 2020-12 | SP#90E | SP-200958 | 2487 | - | F | Removal of NSSAA related statements | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2488 | 1 | F | Alignment with CT specification on updating the UE with new CAG information | 16.7.0 | +| 2020-12 | SP#90E | SP-200959 | 2490 | 1 | F | Correction on AMF discovery and selection | 16.7.0 | +| 2020-12 | SP#90E | SP-200959 | 2499 | 1 | F | S-NSSAI handling at the Inter PLMN mobility | 16.7.0 | +| 2020-12 | SP#90E | SP-200959 | 2500 | - | F | Correction on mobility restriction | 16.7.0 | +| 2020-12 | SP#90E | SP-200959 | 2502 | 1 | F | Correction of AF use of Internal Group Identifier | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2504 | 1 | F | Clarification on UPF report Bridge ID | 16.7.0 | +| 2020-12 | SP#90E | SP-200954 | 2510 | - | F | Clarification on the construction of prioritized list of WLAN access networks for trusted access network selection | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2511 | 1 | F | Updates to N4 for NW-TT port number reporting | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2512 | 1 | F | TSN QoS determination | 16.7.0 | +| 2020-12 | SP#90E | SP-200953 | 2521 | 1 | F | N3IWF selection procedure when accessing SNPN via PLMN | 16.7.0 | +| 2020-12 | SP#90E | SP-200959 | 2523 | 1 | F | Mega CR to clean up | 16.7.0 | +| 2021-03 | SP#91E | SP-210243 | 2463 | 2 | F | Correction on Ethernet Type PDU session and MAC address association | 16.8.0 | +| 2021-03 | SP#91E | SP-210245 | 2531 | 1 | F | Clarification on LADN support for an MA PDU Session | 16.8.0 | +| 2021-03 | SP#91E | SP-210242 | 2532 | 1 | F | Correction of packet delay calculation for QoS monitoring | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2534 | 1 | F | Correction on the determination of S-NSSAI for interworking | 16.8.0 | +| 2021-03 | SP#91E | SP-210055 | 2535 | - | F | Correction on UE Radio Capability Handling during suspend | 16.8.0 | +| 2021-03 | SP#91E | SP-210243 | 2540 | 2 | F | Correction on gap analysis on charging for 5G service based architecture | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2546 | 1 | F | Correction of UE radio capability handling | 16.8.0 | +| 2021-03 | SP#91E | SP-210243 | 2555 | 1 | F | 5G-EIR Discovery and Selection | 16.8.0 | +| 2021-03 | SP#91E | SP-210242 | 2557 | 1 | F | Removal of erroneous RAN requirements | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2559 | 1 | F | Correction to Mobility Restrictions and Access Restrictions | 16.8.0 | +| 2021-03 | SP#91E | SP-210054 | 2569 | 1 | F | Support for IMS emergency from CAG non-supporting UE | 16.8.0 | +| 2021-03 | SP#91E | SP-210080 | 2570 | 1 | F | Handling of UTRAN UE radio capabilities | 16.8.0 | +| 2021-03 | SP#91E | SP-210244 | 2589 | - | F | Correction on reference to BBF | 16.8.0 | +| 2021-03 | SP#91E | SP-210243 | 2600 | 1 | F | IMS voice over PS Session Supported Indication taking into account UE S1 mode status | 16.8.0 | +| 2021-03 | SP#91E | SP-210054 | 2603 | 1 | F | clarification on the determination of the egress port for DL traffic | 16.8.0 | +| 2021-03 | SP#91E | SP-210054 | 2604 | - | F | Correction for reporting of 5GS Bridge information | 16.8.0 | +| 2021-03 | SP#91E | SP-210054 | 2605 | - | F | Clarification for the stream filter instance | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2622 | 1 | F | S-NSSAI for emergency services | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2623 | 1 | F | Inter PLMN mobility for emergency services | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2632 | 1 | F | NGAP UE-TNLA-binding update | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2636 | 1 | F | AMF reallocation during EPS to 5GS handover using N26 | 16.8.0 | +| 2021-03 | SP#91E | SP-210055 | 2641 | - | F | Clarification on support of QoS for Control Plane CLoT 5GS Optimisation | 16.8.0 | +| 2021-03 | SP#91E | SP-210242 | 2655 | 1 | F | Correction on QoS monitoring for URLLC | 16.8.0 | +| 2021-03 | SP#91E | SP-210055 | 2657 | 1 | F | Downlink data report by UPF | 16.8.0 | +| 2021-03 | SP#91E | SP-210081 | 2664 | - | F | Provide recommended cells for paging information in NGAP UE CONTEXT RESUME REQUEST message | 16.8.0 | +| 2021-03 | SP#91E | SP-210078 | 2665 | - | F | Remove the remaining editor's note for IAB descriptions | 16.8.0 | +| 2021-03 | SP#91E | SP-210077 | 2683 | 1 | F | Alternative QoS Profiles and Handover to Congested Cells | 16.8.0 | +| 2021-03 | SP#91E | SP-210067 | 2457 | 1 | B | Introduction of AKMA into the reference architecture | 17.0.0 | +| 2021-03 | SP#91E | SP-210088 | 2525 | 1 | B | Support of different slices over different Non 3GPP access | 17.0.0 | +| 2021-03 | SP#91E | SP-210068 | 2527 | 1 | B | MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2530 | 1 | B | Enchantments for supporting Supported Analytics Delay mechanism | 17.0.0 | +| 2021-03 | SP#91E | SP-210085 | 2536 | 1 | B | Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service | 17.0.0 | +| 2021-03 | SP#91E | SP-210065 | 2537 | - | C | Selection of CN node by NG-RAN node providing satellite access across multiple countries | 17.0.0 | +| 2021-03 | SP#91E | SP-210065 | 2538 | 1 | C | Identification and mobility restrictions for satellite access | 17.0.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-03 | SP#91E | SP-210084 | 2542 | 1 | B | KI#2-1: Capturing the FS_IoT conclusions on static filtering entries | 17.0.0 | +| 2021-03 | SP#91E | SP-210088 | 2544 | 1 | C | IP index from UDM | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2549 | 1 | C | KI#1-4: Control of PTP functionality in DS-TT and NW-TT | 17.0.0 | +| 2021-03 | SP#91E | SP-210074 | 2550 | 1 | C | SNPN selection for access to SNPNs using credentials from an entity separate from the SNPN | 17.0.0 | +| 2021-03 | SP#91E | SP-210074 | 2551 | 1 | D | Informative guideline on how to keep the UE in CM-CONNECTED state in overlay network using existing release 16 mechanisms. | 17.0.0 | +| 2021-03 | SP#91E | SP-210088 | 2560 | 1 | B | 5G system architecture updates to support Dynamically Changing Policies in the 5GC | 17.0.0 | +| 2021-03 | SP#91E | SP-210088 | 2561 | - | B | DCAMP related update of BSF services (23.501) | 17.0.0 | +| 2021-03 | SP#91E | SP-210074 | 2563 | 1 | B | Informative guideline on supporting session/service continuity between SNPN and PLMN when using N3IWF | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2567 | 1 | B | Network Slice restriction based on NWDAF analytics | 17.0.0 | +| 2021-03 | SP#91E | SP-210087 | 2571 | 1 | C | New SST for High-Performance Machine-Type Communications (HMTC) | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2573 | 1 | B | Introduction of the architectures for Time Sensing Communication other than TSN. | 17.0.0 | +| 2021-03 | SP#91E | SP-210086 | 2574 | 1 | B | Introduction of Paging Cause feature | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2575 | 1 | B | NWDAF discovery and selection | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2576 | 1 | B | DCCF Discovery | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2577 | 1 | B | NWDAF Discovery | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2581 | 1 | B | Adding the usage of Redundant Transmission Experience analytics for URLLC service | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2582 | 1 | B | Adding the usage of extended UE Mobility analytics for LADN service | 17.0.0 | +| 2021-03 | SP#91E | SP-210068 | 2583 | 1 | B | PMF enhancements to support per QoS Flow measurements | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2584 | 1 | B | Extensions of NWDAF services | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2585 | 1 | B | NWDAF discovery and selection based on provided ML models | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2586 | 1 | B | UP path selection enhancement based on analytics info provided by NWDAF | 17.0.0 | +| 2021-03 | SP#91E | SP-210068 | 2587 | 1 | B | Packet Loss Rate measurements | 17.0.0 | +| 2021-03 | SP#91E | SP-210068 | 2590 | 1 | B | Applying thresholds to Load-Balancing steering mode in ATSSS | 17.0.0 | +| 2021-03 | SP#91E | SP-210064 | 2596 | 1 | B | AF Services for 5G ProSe | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2606 | 1 | B | KI#2 Supporting UE-UE TSC | 17.0.0 | +| 2021-03 | SP#91E | SP-210074 | 2611 | 1 | B | SNPN support AAA Server for primary authentication and authorization | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2614 | 1 | B | NWDAF discovery and selection for model sharing | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2615 | 1 | B | Triggers for network analytics | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2618 | 1 | B | KI#2 BMIC and PMIC for TSC without IEEE TSN network | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2619 | 1 | B | KI#3A - TSC Assistance container determined by NEF | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2620 | 1 | B | KI#1-3, UL Sync including New QoS Flow establishment for the gPTP | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2621 | 1 | C | KI#3 Updating AF functional description | 17.0.0 | +| 2021-03 | SP#91E | SP-210087 | 2624 | 1 | D | 23.501 Inclusive language review | 17.0.0 | +| 2021-03 | SP#91E | SP-210074 | 2625 | 1 | B | SNPN with separate entity hosting subscription | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2627 | 1 | C | Generalizing TSC clause 5.27 | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2628 | 1 | C | TSCAI applicability | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2629 | 1 | B | KI#3B-1: Exposure of Time synchronization as a service | 17.0.0 | +| 2021-03 | SP#91E | SP-210069 | 2634 | 1 | B | KI #1-1, I-SMF selection | 17.0.0 | +| 2021-03 | SP#91E | SP-210064 | 2637 | 1 | B | 5G Architecture reference model for ProSe | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2642 | 1 | B | Architectural changes to increasing efficiency of data collection | 17.0.0 | +| 2021-03 | SP#91E | SP-210088 | 2644 | 1 | B | Selecting the same PCF for AMF and SMF | 17.0.0 | +| 2021-03 | SP#91E | SP-210069 | 2646 | 1 | B | EC KI2 Target PSA buffering | 17.0.0 | +| 2021-03 | SP#91E | SP-210074 | 2648 | 1 | C | Support for normal IMS voice over SNPN | 17.0.0 | +| 2021-03 | SP#91E | SP-210065 | 2651 | 1 | C | 5QIs for satellite access | 17.0.0 | +| 2021-03 | SP#91E | SP-210089 | 2653 | 1 | B | Service Assistance Information for 3GPP Advanced Interactive Service | 17.0.0 | +| 2021-03 | SP#91E | SP-210068 | 2654 | 1 | B | Introduction of steering mode indicator | 17.0.0 | +| 2021-03 | SP#91E | SP-210069 | 2656 | 1 | B | Adding some parameters for local NEF selection | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2659 | 1 | B | Principle for logical decomposition of NWDAF | 17.0.0 | +| 2021-03 | SP#91E | SP-210088 | 2662 | 1 | B | Update to N3IWF selection for N3SLICE | 17.0.0 | +| 2021-03 | SP#91E | SP-210084 | 2668 | 1 | B | Support for PTP in time synchronization service and BMCA | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2670 | 1 | B | NWDAF new abbreviation | 17.0.0 | +| 2021-03 | SP#91E | SP-210069 | 2672 | 1 | B | AF Influence enhancement for EAS IP replacement | 17.0.0 | +| 2021-03 | SP#91E | SP-210064 | 2673 | - | B | Add general 5G ProSe support to 5GS | 17.0.0 | +| 2021-03 | SP#91E | SP-210065 | 2674 | 1 | C | Detection of satellite backhaul based on configuration information | 17.0.0 | +| 2021-03 | SP#91E | SP-210072 | 2677 | 1 | C | NWDAF discovery and selection for KI#2 NWDAF Reselection | 17.0.0 | +| 2021-03 | SP#91E | SP-210064 | 2678 | - | B | Introducing 5G DDNMF services for ProSe support | 17.0.0 | +| 2021-03 | SP#91E | SP-210083 | 2679 | 1 | B | TS23.501 KI#1 Network Slice Admission Control Function (NSACF) definition | 17.0.0 | +| 2021-03 | SP#91E | SP-210074 | 2684 | 1 | B | General introduction of Enhancements to Support SNPN along | 17.0.0 | + +| | | | | | | | | +|--|--|--|--|--|--|------------------------------------------------------------|--| +| | | | | | | with credentials owned by an entity separate from the SNPN | | +|--|--|--|--|--|--|------------------------------------------------------------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------|---------------| +| 2021-03 | SP#91E | SP-210271 | 0254 | 3 | B | Network selection for NR satellite access | 17.0.0 | +| 2021-06 | SP#92E | SP-210323 | 2553 | 5 | B | Function Description for Multi-SIM devices | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2562 | 7 | B | UE onboarding | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2635 | 2 | B | KI #1-1, Update for supporting UL time sync with gPTP message | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2647 | 2 | B | PMF extensions for sending UE-assistance data to UPF | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2649 | 3 | C | Support for IMS emergency services over SNPN | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2680 | 3 | B | TS23.501 KI#2 Network Slice Admission Control Function (NSACF) definition | 17.1.0 | +| 2021-06 | SP#92E | SP-210344 | 2689 | 2 | B | 5MBS architecture | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2690 | 3 | B | Support for IEEE 1588 Boundary Clocks in time synchronization service | 17.1.0 | +| 2021-06 | SP#92E | SP-210346 | 2691 | 1 | B | Support for L2TP on N6 | 17.1.0 | +| 2021-06 | SP#92E | SP-210342 | 2693 | 1 | C | UE location verification for NR satellite access | 17.1.0 | +| 2021-06 | SP#92E | SP-210344 | 2696 | 4 | B | N4 extensions for 5MBS | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2697 | 1 | C | Handling of Ethernet PDU Session type for MA PDU Session with a 3GPP EPC leg | 17.1.0 | +| 2021-06 | SP#92E | SP-210337 | 2701 | 2 | B | New 5QI values to support Advance Interactive Services (AIS) in 5G | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2702 | 2 | B | Discover NWDAF for UE related Analytics using UDM | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2705 | 1 | B | CR to update NWDAF discovery and selection for MTLF | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2706 | 3 | B | Support for UE-Slice-MBR | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2707 | 1 | B | EASDF discovery and selection, and update of edge computing description | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2708 | 1 | B | Adding the usage of Session Management Congestion Control Experience analytics | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2709 | 1 | B | Enabling restricted PDU Session for remote provisioning of UE via User Plane | 17.1.0 | +| 2021-06 | SP#92E | SP-210572 | 2714 | 4 | B | Remote provisioning of credentials for NSSAA or secondary authentication/authorisation | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2717 | 1 | B | Network access control by Credential Holder | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2718 | 4 | B | KI#2 T2: Informative guideline for mapping QoS parameters and DSCP marking | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2719 | 2 | B | Support of 5GC assisted cell selection to access network slice | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2720 | 1 | B | Decision to apply measurements per QoS Flow | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2721 | 5 | B | Send PMF messages to a target QoS Flow | 17.1.0 | +| 2021-06 | SP#92E | SP-210330 | 2723 | - | A | Correction to the N3IWF selection procedure | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2727 | 2 | B | NSACF functional descriptions | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2728 | 4 | B | Updates of NSACF discovery and selection | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2729 | 1 | B | NSAC support in roaming | 17.1.0 | +| 2021-06 | SP#92E | SP-210363 | 2736 | 4 | B | Clarification on UE provides PDU Session Pair ID based on URSP rules | 17.1.0 | +| 2021-06 | SP#92E | SP-210337 | 2740 | 2 | B | New standardized 5QI values for Advanced Interactive Services | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2743 | 3 | B | Introduction of UE-assistance operation | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2744 | 1 | B | Thresholds for Priority-based mode | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2746 | 3 | B | QoS Flow recognition for per QoS Flow measurements | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2755 | 3 | B | De-registration for onboarding registered UE | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2757 | 4 | B | AF Influence enhancement for EAS IP replacement | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2758 | 1 | B | Updating AMF exposed events in TS 23.501. | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2759 | 1 | B | Alignment of NWDAF discovery of data exposure capability in TS 23.501. | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2760 | 1 | F | Clarify the Supported Analytics Delay | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2761 | 4 | B | Update the NWDAF profile for ML Model | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2762 | 1 | B | SMF function update to support Edge computing enhancement | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2763 | 1 | B | Update of Edge Computing | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2765 | 1 | B | Adding EASDF services | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2768 | 1 | B | Update for support of TSC other than TSN | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2769 | 2 | B | Correction for Survival Time | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2773 | 3 | B | Update for PTP in time synchronization service and BMCA | 17.1.0 | +| 2021-06 | SP#92E | SP-210342 | 2781 | 1 | B | Support of new RATs in 5GS integrating satellite access | 17.1.0 | +| 2021-06 | SP#92E | SP-210363 | 2783 | 2 | F | (Mirror)Correct the NOTE for N6 | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2789 | 5 | B | Roaming support for NSAC | 17.1.0 | +| 2021-06 | SP#92E | SP-210363 | 2790 | 1 | B | Support GERAN/UTRAN access in SMF+PGW-C | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2791 | 1 | B | KI#3B, Resolving EN for Future PDU Session | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2795 | 1 | C | Add a use case for network slice load analytics | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2799 | 1 | B | Homogeneously support SNPN connectivity for UEs with credentials owned by Credentials Holder | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2801 | 2 | D | Correction to UE identifier sent to AMF by UE | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2802 | 1 | B | User Plane Remote Provisioning of UEs if PLMN as ON | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2804 | 3 | B | Edge relocation considering user plane latency requirement | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2805 | 1 | C | Use of TAI(s) for slice restriction based on analytics | 17.1.0 | +| 2021-06 | SP#92E | SP-210337 | 2806 | 1 | F | Packet size for PDB | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2807 | - | F | Corrections for ADRF services | 17.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------|--------| +| 2021-06 | SP#92E | SP-210351 | 2808 | - | F | Reference to DCCF and MFAF Services description clause | 17.1.0 | +| 2021-06 | SP#92E | SP-210337 | 2809 | 1 | F | TSC Assistance Container Determination by PCF | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2811 | 2 | C | Introducing threshold conditions for priority-based steering mode in TS 23.501 | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2813 | 4 | B | Introduction of support of NG.116 attribute Simultaneous Use of a Network Slice | 17.1.0 | +| 2021-06 | SP#92E | SP-210341 | 2814 | 3 | F | The impact of UE N1 mode change in EPS | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2815 | 3 | B | KI#1 - T5, Enable mobility between networks | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2817 | 1 | B | Terminology on the TSC MIC and Bridge ID | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2820 | - | B | Fix the description on the ethernet port | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2822 | 4 | B | Introduction of support of GSMA NG.116 attributes Maximum DL/UL throughput per slice/UE | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2826 | 1 | B | Mobility support between SNPNS and between SNPN and PLMN | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2832 | 1 | B | UE configuration for remote provisioning | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2833 | 2 | B | Introduction of architecture for AF requested support of Time Sensitive Communication and Time Synchronization | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2837 | 3 | B | Support of Emergency and Priority Services in Network Slice Admission Control | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2838 | 2 | B | TS23.501 KI#4 NSACF event notification definition | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2840 | 1 | F | Packet Loss Rate Measurements | 17.1.0 | +| 2021-06 | SP#92E | SP-210363 | 2848 | 1 | F | FQDNs for N3IWF selection for emergency services | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2856 | 3 | B | Newly added parameters for Local NEF discovery | 17.1.0 | +| 2021-06 | SP#92E | SP-210341 | 2858 | 1 | F | Consistent handling of NF documentation | 17.1.0 | +| 2021-06 | SP#92E | SP-210340 | 2861 | 1 | B | ProSe related functional description | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2862 | - | B | EASDF functional description | 17.1.0 | +| 2021-06 | SP#92E | SP-210330 | 2865 | 1 | A | UE radio capability clarification | 17.1.0 | +| 2021-06 | SP#92E | SP-210358 | 2870 | 1 | B | UAV support feature inclusion | 17.1.0 | +| 2021-06 | SP#92E | SP-210341 | 2874 | 1 | F | Correction to the reference document for charging related reference points | 17.1.0 | +| 2021-06 | SP#92E | SP-210344 | 2880 | 1 | B | PCF impacts of 5MBS | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2881 | 1 | B | KI#8 - AF discovery and selection | 17.1.0 | +| 2021-06 | SP#92E | SP-210345 | 2886 | 1 | B | Partial ATSSS rule update by using ATSSS rule ID | 17.1.0 | +| 2021-06 | SP#92E | SP-210330 | 2888 | 1 | A | Subscription data updates for EPS/5GS interworking | 17.1.0 | +| 2021-06 | SP#92E | SP-210329 | 2889 | - | A | Updates on PCC rule triggered GTP-U path monitoring | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2892 | 1 | F | SNPN UE configuration and subscription aspects | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2893 | 1 | B | SNPN - SNPN Mobility - AMF selection impacts | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2894 | 1 | F | SNPN GIN Encoding | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2896 | 1 | C | Exposure of Time synchronization as a service - description | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2899 | 1 | B | N4 interface enhancement for local notification | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2900 | 1 | B | UPF function update to support network information exposure | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2902 | 1 | F | Simultaneous data service from PNI-NPN and PLMN | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2903 | 1 | F | IMS voice over overlay network | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2904 | 1 | F | KI#3A Support QoS mapping based on priority for TSC exposure | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2905 | 1 | F | Clarification on support of PTP GM function in TT | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2908 | 1 | F | Resolving EN for Hold and Forward mechanism | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2909 | 1 | B | Support multiple NSACFs for one S-NSSAI during UE mobility | 17.1.0 | +| 2021-06 | SP#92E | SP-210340 | 2910 | 1 | B | Update of reference points for 5G ProSe | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2911 | 1 | B | KI#3B, Temporal Validity Condition Description | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2913 | 1 | B | Updates to AF requests to influence traffic routing | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2914 | - | F | Update on I-SMF selection per DNAI | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2918 | 1 | B | KI#2 T1: Informative guideline for QoS Notification between overlay network and underlay network | 17.1.0 | +| 2021-06 | SP#92E | SP-210545 | 2923 | 2 | F | Allowed NSSAI when NSSAA fails | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2924 | 1 | B | Network Slice Admission Control in EPC | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2926 | 1 | C | Interaction between AUSF and AAA Server | 17.1.0 | +| 2021-06 | SP#92E | SP-210362 | 2927 | 1 | B | Introduction of MUSIM capability exchange | 17.1.0 | +| 2021-06 | SP#92E | SP-210330 | 2931 | 1 | A | Support for UPIP for other than NR | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2934 | 1 | F | Update on uplink traffic buffering | 17.1.0 | +| 2021-06 | SP#92E | SP-210347 | 2935 | 1 | F | AF Influence enhancement for EAS Rediscovery at Edge Relocation | 17.1.0 | +| 2021-06 | SP#92E | SP-210355 | 2937 | 1 | B | NSAC with consideration of access type | 17.1.0 | +| 2021-06 | SP#92E | SP-210351 | 2938 | 1 | C | NWDAF assisted DNAI and UPF selection at SMF | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2939 | 1 | F | Correction to scenarios of external authentication | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2940 | 1 | B | Clarification on NID | 17.1.0 | +| 2021-06 | SP#92E | SP-210341 | 2945 | 1 | F | Clarification on the number of Subscribed S-NSSAIs | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2946 | - | C | Definition of the UE-DS-TT residence time | 17.1.0 | +| 2021-06 | SP#92E | SP-210327 | 2947 | 1 | A | NIDD configuration correction | 17.1.0 | +| 2021-06 | SP#92E | SP-210342 | 2948 | 1 | C | Removal of UPF indication of backhaul QoS to SMF | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2952 | 1 | B | HRNN in manual network selection for SNPNS | 17.1.0 | +| 2021-06 | SP#92E | SP-210341 | 2953 | 1 | F | Clarification on the Standardized SST values | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2955 | 1 | B | AMF selection to support UE onboarding SNPN | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2959 | - | F | Grandmaster candidate enabled management information per PTP | 17.1.0 | + +| | | | | | | | | +|--|--|--|--|--|--|----------|--| +| | | | | | | instance | | +|--|--|--|--|--|--|----------|--| + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-06 | SP#92E | SP-210359 | 2960 | 1 | C | Time Synchronization service exposure | 17.1.0 | +| 2021-06 | SP#92E | SP-210371 | 2962 | 2 | F | Clarification of applicability of port/bridge management information | 17.1.0 | +| 2021-06 | SP#92E | SP-210336 | 2963 | 1 | A | Clarification for Visited Country FQDN DNS query for SNPNs with locally assigned NIDs | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2965 | 1 | C | AUSF selection for an Onboarding UE | 17.1.0 | +| 2021-06 | SP#92E | SP-210353 | 2969 | 1 | B | Definition of SNPN-related terms | 17.1.0 | +| 2021-06 | SP#92E | SP-210341 | 2970 | 1 | B | 4G <-> 5GS mobility corrections to cope with areas of GERAN/UTRAN-only coverage | 17.1.0 | +| 2021-06 | SP#92E | SP-210361 | 2971 | 1 | B | Additional authorization functionality in support of MPS for Data Transport Service | 17.1.0 | +| 2021-06 | SP#92E | SP-210346 | 2973 | 1 | B | L2TP information provision | 17.1.0 | +| 2021-06 | SP#92E | SP-210359 | 2977 | 1 | B | Clarification on TSCAI for the non TSC service | 17.1.0 | +| 2021-06 | SP#92E | SP-210330 | 2982 | 1 | A | AMF to consider S1 mode capability into account when setting EMF and EMC | 17.1.0 | +| 2021-06 | SP#92E | SP-210335 | 2984 | 1 | A | Correction to trigger for UE Radio Capability Update procedure | 17.1.0 | +| 2021-06 | SP#92E | SP-210331 | 2990 | - | A | Correction on non-3GPP access type | 17.1.0 | +| 2021-06 | SP#92E | SP-210331 | 2991 | 1 | F | Adding PDU session limitation and protocol stacks for trusted WLAN access for N5CW device | 17.1.0 | +| 2021-06 | SP#92E | SP-210354 | 2992 | - | F | UE configuration for remote provisioning | 17.1.0 | +| 2021-06 | SP#92E | - | - | - | - | MCC Correction to move 5.15.11.14 to 5.15.11.5 | 17.1.1 | +| 2021-09 | SP#93E | SP-210916 | 2748 | 3 | C | Support of Mobility Registration Update for 5G Satellite Access | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 2919 | 2 | B | IMSI based SUPI support when access an SNPN using credentials owned by CH | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 2921 | 2 | B | UE onboarding architecture | 17.2.0 | +| 2021-09 | SP#93E | SP-210915 | 2993 | 1 | F | Clarifying that at least one default S-NSSAI is mandatory | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 2994 | 1 | F | correction to the re-configuration requirements for NSSRG non-supporting UEs | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 2995 | - | F | clarification on obtaining the Configured NSSAI from NSSF when NSSRG for UE changes | 17.2.0 | +| 2021-09 | SP#93E | SP-210911 | 2998 | 1 | A | Enforcing CAG restrictions during E-UTRAN to NG-RAN connected mode mobility | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 2999 | 1 | F | Update of Credentials Holder controlled prioritized lists of preferred SNPNs and GINs using SoR | 17.2.0 | +| 2021-09 | SP#93E | SP-210922 | 3001 | 1 | F | TS 23.288 reference update for ADRF services | 17.2.0 | +| 2021-09 | SP#93E | SP-210922 | 3002 | 1 | F | Resolving editor's note for ADRF discovery and selection | 17.2.0 | +| 2021-09 | SP#93E | SP-210910 | 3003 | 1 | A | Handling of UE Radio Capability for Paging | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3004 | 1 | F | Missing Definition of Target NSSAI | 17.2.0 | +| 2021-09 | SP#93E | SP-210935 | 3009 | 1 | B | EPS User Plane Integrity Protection using SMF+PGW-C | 17.2.0 | +| 2021-09 | SP#93E | SP-210919 | 3010 | 1 | C | Allowing usage of S-NSSAI and Network Instance for internal UPF resource allocation | 17.2.0 | +| 2021-09 | SP#93E | SP-210937 | 3011 | - | F | BSF related update of NRF services (23.501) | 17.2.0 | +| 2021-09 | SP#93E | SP-210928 | 3018 | 1 | F | NEF discovery and selection based on AF address | 17.2.0 | +| 2021-09 | SP#93E | SP-210931 | 3019 | 1 | B | Adding the functionality on MINT | 17.2.0 | +| 2021-09 | SP#93E | SP-210920 | 3025 | 1 | B | NEF service to support EAS deployment info | 17.2.0 | +| 2021-09 | SP#93E | SP-210920 | 3026 | - | F | AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation | 17.2.0 | +| 2021-09 | SP#93E | SP-210918 | 3027 | 1 | F | UE-assistance operation on traffic aggregate granularity | 17.2.0 | +| 2021-09 | SP#93E | SP-210916 | 3029 | 1 | C | PDB value for 5QI 10 | 17.2.0 | +| 2021-09 | SP#93E | SP-210906 | 3033 | 1 | F | ATSSS Rule ID | 17.2.0 | +| 2021-09 | SP#93E | SP-210914 | 3034 | 1 | F | Update the naming convention for the reference points for 5G ProSe | 17.2.0 | +| 2021-09 | SP#93E | SP-210937 | 3035 | 1 | F | 5G URLLC Redundant PDU Session correction for NGAP parameters | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3036 | 1 | F | GIN Encoding | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3038 | 1 | F | TSN AF functional description and reference point | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3039 | 1 | F | Updates for time synchronization text - description | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3040 | 1 | F | Architecture to enable Time Sensitive Communication and Time Synchronization | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3041 | 1 | F | Updates for TSCTSF text - description | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3042 | 1 | C | Exposure of Time synchronization as a service - description | 17.2.0 | +| 2021-09 | SP#93E | SP-210937 | 3043 | - | F | Correction on Redundant PDU Session | 17.2.0 | +| 2021-09 | SP#93E | SP-210915 | 3044 | 1 | F | Updates to enable mobility between GERAN/UTRAN and E-UTRAN in 5GS | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3045 | 1 | F | Handling of SUPI/SUCI format when accessing to a SNPN | 17.2.0 | +| 2021-09 | SP#93E | SP-210932 | 3048 | - | F | Update Paging Cause Feature in 5GS | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3049 | 1 | F | KI#4-SNPN UE Onboarding using existing DNN | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3051 | 1 | D | Correcting the usage of Survival Time | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3052 | 1 | B | Informative guidelines for usage of QoS related exposure capabilities to leverage between overlay network and underlay network | 17.2.0 | +| 2021-09 | SP#93E | SP-210915 | 3054 | 1 | F | Correction on Charging | 17.2.0 | +| 2021-09 | SP#93E | SP-210903 | 3057 | 1 | A | Derivation of UL Packet Filter from DL encapsulated IPsec protected packet | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------|--------| +| 2021-09 | SP#93E | SP-210936 | 3062 | 1 | C | Explicit indication for ATC | 17.2.0 | +| 2021-09 | SP#93E | SP-210936 | 3064 | - | F | Corrections on the AF related identifier | 17.2.0 | +| 2021-09 | SP#93E | SP-210937 | 3065 | 1 | F | Corrections on geographical area | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3066 | 1 | F | Addition of NSACF services | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3067 | 1 | F | Redirection to dedicated frequency band(s) at the end of NSSAA | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3072 | 1 | F | KI#5 UE-Slice-MBR enforcement in PCF | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3074 | 1 | B | Roaming support for NSAC in VPLMN | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3077 | 1 | F | Support of multiple NSACF instance | 17.2.0 | +| 2021-09 | SP#93E | SP-210922 | 3079 | - | F | Update to AF Discovery and Selection | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3084 | - | F | Interaction between PVS and SO-SNPN | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3085 | - | C | DCS providing PVS address to ONN | 17.2.0 | +| 2021-09 | SP#93E | SP-210932 | 3088 | 1 | B | 5GS Connection release support for 5GC/NR | 17.2.0 | +| 2021-09 | SP#93E | SP-210917 | 3091 | - | D | Update clause number for MB-UPF, MBSF and MBSTF in clause 6.2 | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3095 | - | B | Reference point AUSF - NSSAAF | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3097 | 1 | B | Format of SUCI/SUPI used for Onboarding | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3098 | - | C | SNPN support for emergency | 17.2.0 | +| 2021-09 | SP#93E | SP-210922 | 3101 | 1 | F | Resolve Editor's Note on analytics metadata provisioning capability | 17.2.0 | +| 2021-09 | SP#93E | SP-210937 | 3108 | - | F | Update BSF NF profile to support SUPI and GPSI | 17.2.0 | +| 2021-09 | SP#93E | SP-210918 | 3111 | 1 | F | Termination on UE assistance mode | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3112 | - | F | Classification of NEF or TSCTSF | 17.2.0 | +| 2021-09 | SP#93E | SP-210918 | 3114 | - | F | Removal of 5G-RG limitation on 3GPP access leg support in EPC | 17.2.0 | +| 2021-09 | SP#93E | SP-210918 | 3116 | 1 | F | Clarification on source and destination addresses setting for PMF messages | 17.2.0 | +| 2021-09 | SP#93E | SP-210916 | 3119 | 1 | F | Remove Editor's note in clause 5.4.11.1 in TS 23.501 | 17.2.0 | +| 2021-09 | SP#93E | SP-210920 | 3124 | 1 | F | Update of ECS address in External Exposure of Network Capability | 17.2.0 | +| 2021-09 | SP#93E | SP-211133 | 3126 | 3 | B | Resolve ENs in NSAC support for EPC interworking | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3136 | - | F | Terminology correction for UE onboarding | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3137 | 1 | F | AMF relocation for UE registered for onboarding | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3139 | - | F | selection of AUSF supporting primary authentication towards AAA server | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3142 | - | F | Clarify distribution of Announce message | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3143 | - | F | Clarify interworking with EPS is not supported for TSC or time synchronization | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3144 | 1 | F | Granularity of TSCTSF | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3146 | 1 | F | Correction on remote provisioning of credentials for NSSAA or secondary authentication/authorization | 17.2.0 | +| 2021-09 | SP#93E | SP-210920 | 3149 | 1 | F | Updates on edge computing | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3150 | 1 | F | Updates on PTP instance type | 17.2.0 | +| 2021-09 | SP#93E | SP-210933 | 3155 | 1 | B | Support RedCap UEs differentiation in 5GC | 17.2.0 | +| 2021-09 | SP#93E | SP-210911 | 3157 | 1 | A | Clarification on the Bridge delay calculating | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3160 | 1 | F | KI#3, clarification on the TSCTSF functionality and configuration for transport protocols | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3161 | 1 | B | KI#3, clarification on the exposure of time sync service | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3162 | 1 | F | Clean up on the BMIC and bridge Management Information Container | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3165 | - | F | Clarification of the AMF Onboarding Configuration Data | 17.2.0 | +| 2021-09 | SP#93E | SP-210904 | 3169 | - | A | 5GS Idle Status Indication | 17.2.0 | +| 2021-09 | SP#93E | SP-210915 | 3170 | 1 | B | AUSF/UDM discovery based SUCI information | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3173 | 1 | F | Clarification on NF profile in case of SNPN | 17.2.0 | +| 2021-09 | SP#93E | SP-210923 | 3175 | 1 | F | Clarification on functionality of NF in SNPN | 17.2.0 | +| 2021-09 | SP#93E | SP-210912 | 3178 | - | A | Emergency services for non-3GPP access | 17.2.0 | +| 2021-09 | SP#93E | SP-210918 | 3179 | 1 | F | Clarification on threshold values | 17.2.0 | +| 2021-09 | SP#93E | SP-210920 | 3186 | - | B | Use UPF to transfer DNS message between EASDF and DNS server | 17.2.0 | +| 2021-09 | SP#93E | SP-210920 | 3187 | - | F | Add Nudm_ServiceSpecificAuthorisation service | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3189 | 1 | F | Update for (g)PTP messages forwarding in UPF/NW-TT | 17.2.0 | +| 2021-09 | SP#93E | SP-210908 | 3190 | 2 | A | No empty allowed NSSAI at REGISTRATION ACCEPT | 17.2.0 | +| 2021-09 | SP#93E | SP-210932 | 3192 | 1 | F | MUSIM Terminology Alignment | 17.2.0 | +| 2021-09 | SP#93E | SP-210932 | 3196 | - | F | Terminology correction | 17.2.0 | +| 2021-09 | SP#93E | SP-210929 | 3198 | 1 | C | Correcting the residence time calculation for the delay measurements | 17.2.0 | +| 2021-09 | SP#93E | SP-210916 | 3199 | 1 | F | SMF subscribes Satellite backhaul category backhaul change from AMF | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3201 | 1 | B | Completion of NSAC per access type | 17.2.0 | +| 2021-09 | SP#93E | SP-210911 | 3204 | 2 | A | Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock | 17.2.0 | +| 2021-09 | SP#93E | SP-210903 | 3208 | - | A | Correction of N26 message relaying between S1 and N26 messages | 17.2.0 | +| 2021-09 | SP#93E | SP-210933 | 3209 | 1 | C | Extended DRX for NR (RedCap) | 17.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-09 | SP#93E | SP-210915 | 3213 | 1 | F | Update Reference architecture with UPF SBI | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3220 | 1 | F | NSAC procedure in EPS when APN maps to more than one S-NSSAI. | 17.2.0 | +| 2021-09 | SP#93E | SP-210915 | 3222 | - | F | Indicate the number of supported packet filters for signalled QoS rules only if the UE supports more than 16 packet filters for the PDU session | 17.2.0 | +| 2021-09 | SP#93E | SP-210932 | 3228 | - | F | Clarification related to access type | 17.2.0 | +| 2021-09 | SP#93E | SP-210915 | 3230 | 1 | F | Overlapping LADN Service area | 17.2.0 | +| 2021-09 | SP#93E | SP-210911 | 3231 | - | A | Clarification on support of CAG in SNPN | 17.2.0 | +| 2021-09 | SP#93E | SP-210925 | 3232 | - | F | clarification on S-NSSAI mapping | 17.2.0 | +| 2021-12 | SP#94E | SP-211289 | 2385 | 8 | C | Support of the mapping from IP addressing information provided to an AF to the user identity | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3030 | 4 | F | UE location verification handling | 17.3.0 | +| 2021-12 | SP#94E | SP-211286 | 3055 | 3 | F | MBS Packet detection and forwarding | 17.3.0 | +| 2021-12 | SP#94E | SP-211286 | 3092 | 3 | F | Add NF services for 5G MBS | 17.3.0 | +| 2021-12 | SP#94E | SP-211302 | 3094 | 2 | F | MUSIM support for SNPN access mode | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3107 | 4 | F | QoS parameter handling for TSC | 17.3.0 | +| 2021-12 | SP#94E | SP-211288 | 3110 | 2 | F | PMF information transported via N4 | 17.3.0 | +| 2021-12 | SP#94E | SP-211304 | 3172 | 5 | C | NSSAA Discovery and Selection based on S-NSSAI or UE ID Range | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3205 | 2 | F | Update to NSSRG procedure | 17.3.0 | +| 2021-12 | SP#94E | SP-211302 | 3229 | 2 | F | Deleting PRs in non allowed area | 17.3.0 | +| 2021-12 | SP#94E | SP-211302 | 3235 | 4 | F | Enabling of paging reception for 5GS | 17.3.0 | +| 2021-12 | SP#94E | SP-211550 | 3237 | 3 | F | MUSIM capabilities in Emergency Registration | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3240 | 2 | F | Network Slicing scope in relation to SNPNs | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3241 | 1 | F | Network slice admission control for SNPN onboarding | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3242 | 3 | F | Improved PTP instance configuration management | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3243 | - | F | Correction of the TSCTSF functionality description | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3244 | 1 | F | Revisions related Time Synchronization | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3245 | 1 | F | Clarifications on TSN AF and TSCTSF parameter handling | 17.3.0 | +| 2021-12 | SP#94E | SP-211304 | 3246 | - | C | Update of clause 6.3.1.0 related to binding | 17.3.0 | +| 2021-12 | SP#94E | SP-211288 | 3247 | 1 | F | Access performance measurements applicability to QoS Flows | 17.3.0 | +| 2021-12 | SP#94E | SP-211288 | 3248 | 1 | F | Corrections to UE assistance operation | 17.3.0 | +| 2021-12 | SP#94E | SP-211288 | 3250 | 1 | F | Clarification on threshold condition | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3251 | 1 | B | Authentication and Subscription information checking for Disaster Roaming service | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3252 | - | F | Clarification for Disaster Roaming service | 17.3.0 | +| 2021-12 | SP#94E | SP-211304 | 3253 | 1 | F | Reserving some reference point numbers | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3254 | 1 | F | Clarification on Remote provisioning of credentials - User Plane | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3255 | 1 | F | UE Configuration Data for UP Remote Provisioning provided by ONN | 17.3.0 | +| 2021-12 | SP#94E | SP-211627 | 3256 | 6 | F | UE onboarding architecture | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3257 | 3 | D | Rapporteur's editorial cleanup for eNPN | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3260 | 1 | F | Link delay measurement for the end-to-end Transparent Clock | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3261 | 2 | F | NSAC clarification | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3264 | 3 | F | MINT Updates | 17.3.0 | +| 2021-12 | SP#94E | SP-211287 | 3265 | - | C | NR RedCap Indication during IRAT handover procedure | 17.3.0 | +| 2021-12 | SP#94E | SP-211304 | 3267 | - | F | GBA Reference points | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3268 | 1 | D | Editorial Changes on eNS_Ph2 | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3269 | 2 | F | Clarification on Access Type for NSAC | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3274 | 3 | F | eNPN corrections to clarify use of DNN and S-NSSAI for onboarding, AUSF discovery | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3275 | 1 | F | Time synchronization - description review | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3276 | 1 | D | Rapporteur CR for editorial fixes | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3277 | 1 | F | Correction on remote provisioning of credentials for NSSAA or secondary authentication/authorization | 17.3.0 | +| 2021-12 | SP#94E | SP-211298 | 3280 | - | F | UAS NF selection based on the NEF capability | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3281 | 1 | F | KI#4- Restricted Onboarding PDU session when PLMN is ON | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3284 | 3 | F | Editorial correction in TS 23.501 | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3285 | 1 | F | Clarify the interaction between AF and TSCTSF | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3287 | 1 | F | Clarification on MINT | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3290 | 1 | D | Clarification on RTD and Terminology Alignment | 17.3.0 | +| 2021-12 | SP#94E | SP-211290 | 3293 | - | F | Corrections on DNAI based I-SMF selection and removal | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3294 | 1 | F | Applicability of states of non-3GPPA and clarifications. | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3295 | 1 | F | Update of the Early Admission Control (EAC) mode | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3296 | - | F | Update of the Functional Description Related to NSAC | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3297 | 1 | F | Clarification for UE onboarding and UE access with CH credentials | 17.3.0 | +| 2021-12 | SP#94E | SP-211290 | 3299 | 2 | F | 501 EASDF Service correction | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3300 | 1 | F | The decision of target NSSAI based on NSSRG | 17.3.0 | +| 2021-12 | SP#94E | SP-211624 | 3302 | 2 | A | Correction on PMF protocol stack for non-3GPP access | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3303 | 1 | F | 23.501 clarification on eNPN | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3311 | 1 | F | Deregistration for UE not eligible for disaster roaming service | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|----------|----------------------------------------------------------------------------------------------------------------------------------|--------| +| 2021-12 | SP#94E | SP-211299 | 3312 | 1 | F | Update for Time Synchronization Information in PMIC and UMIC | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3313 | 2 | F | Corrections on TSCTSF selection and residence time calculation | 17.3.0 | +| 2021-12 | SP#94E | SP-211592 | 3314 | 3 | F | Support for emergency calls in limited service state | 17.3.0 | +| 2021-12 | SP#94E | SP-211287 | 3316 | 2 | B | eDRX enhancement for 10.24s cycle for RedCap | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3318 | 2 | F | Limited service PLMN selection for emergency | 17.3.0 | +| 2021-12 | SP#94E | SP-211628 | 3319 | 6 | B | Support for Paging Early Indication | 17.3.0 | +| 2021-12 | SP#94E | SP-211293 | 3320 | 4 | F | Miscellaneous correction for eNA_Ph2 | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3321 | 1 | F | Multiple TSCTSFs associated with a single UPF | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3322 | 2 | F | Processing (g)PTP messages for domain numbers and while in Disabled state | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3323 | 2 | C | Support multiple TACs for satellite access | 17.3.0 | +| 2021-12 | SP#94E | SP-211287 | 3324 | 2 | B | Capabilities for NR RedCap UE | 17.3.0 | +| 2021-12 | SP#94E | SP-211303 | 3327 | - | F | EPS User Plane Integrity Protection corrections for Service Request and mixed eNB UPIP support; etc in TS 23.501. | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3328 | 1 | F | Clarification on the UE remote provisioning. | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3330 | 1 | F | Clarification on the time synchronization | 17.3.0 | +| 2021-12 | SP#94E | SP-211416 | 3331 | 2 | F | clarification on definition of NSSRG | 17.3.0 | +| 2021-12 | SP#94E | SP-211302 | 3334 | 1 | F | On Paging restrictions handling | 17.3.0 | +| 2021-12 | SP#94E | SP-211536 | 3335 | 3 | F | On Connection Release and Paging Restriction during a Mobility Registration Update in a TA outside the current Registration Area | 17.3.0 | +| 2021-12 | SP#94E | SP-211288 | 3338 | 1 | F | Change term default QoS Flow to the QoS Flow associated with default QoS rule in TS 23.501 | 17.3.0 | +| 2021-12 | SP#94E | SP-211293 | 3339 | - | F | Update to NEF Discovery and Selection | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3340 | 1 | F | Clarification on roaming description for SNPn | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3342 | 1 | Release: | Clarification on network selection for ON-SNPn | 17.3.0 | +| 2021-12 | SP#94E | SP-211626 | 3345 | 4 | F | Clarifications of NSAC and NSAC for roaming cases | 17.3.0 | +| 2021-12 | SP#94E | SP-211287 | 3346 | - | F | Correction on Paging for extended idle mode DRX in E-UTRA and NR connected to 5GC | 17.3.0 | +| 2021-12 | SP#94E | SP-211287 | 3349 | - | B | Support of Access Restriction for RedCap | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3351 | 1 | D | Rapporteur CR for editorial fixes - Inclusive terminology | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3352 | 1 | F | Addressing Rel-17 DS-TT backwards incompatibility for time synchronization | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3357 | 1 | F | Deletion of selected entries in UMIC/PMIC data structures | 17.3.0 | +| 2021-12 | SP#94E | SP-211300 | 3358 | 1 | F | Clarification on Static Filtering Entries | 17.3.0 | +| 2021-12 | SP#94E | SP-211305 | 3362 | - | F | Align BSF NF profile in NRF (23.501) with BSF related information in NRF services (23.502) | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3364 | 1 | F | TA handling for moving cells in satellite access | 17.3.0 | +| 2021-12 | SP#94E | SP-211276 | 3366 | - | A | V-SMF change at inter-PLMN mobility | 17.3.0 | +| 2021-12 | SP#94E | SP-211283 | 3367 | - | F | NG-RAN location report clarification in RRC Inactive | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3373 | 1 | F | Corrections for CH using AUSF/UDM | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3374 | 1 | F | Correction to AMF Onboarding Configuration Data | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3375 | 2 | F | 23.501: TSCTSF Discovery and Selection | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3376 | - | F | Clarification on IAB support for NR satellite access | 17.3.0 | +| 2021-12 | SP#94E | SP-211282 | 3378 | 1 | F | Fix reference for Naf ProSe | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3379 | - | B | Indicating a last visited TAI in a Registration for NR Satellite Access | 17.3.0 | +| 2021-12 | SP#94E | SP-211304 | 3382 | 1 | F | Supplementation of L2TP tunnel applicable scenario | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3386 | 1 | F | Update the correction field for the end-to-end Transparent Clock | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3389 | 1 | F | Handling of DC is no longer applicable | 17.3.0 | +| 2021-12 | SP#94E | SP-211278 | 3393 | 1 | A | correction for CAG restrictions with emergency services | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3394 | 1 | F | clarification for QoS differentiation for User Plane IPsec Child SA in underlay network | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3400 | - | F | Removal of Editor's Note on Configured NSSAI | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3401 | 1 | F | Clarification on Multiple NSACFs for S-NSSAI | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3405 | 1 | F | Relationship between Sync Exposure and Time Distribution | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3406 | 1 | F | Correction on 5G access stratum time distribution | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3407 | 1 | F | Alignment on system information extensions for minimization of service interruption | 17.3.0 | +| 2021-12 | SP#94E | SP-211301 | 3408 | 1 | F | Emergency Services for Disaster Inbound Roamers | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3410 | - | F | Corrections on Nnsacf_SliceStatus and Nnef_SliceStatus services | 17.3.0 | +| 2021-12 | SP#94E | SP-211284 | 3415 | 1 | C | Mobility Registration Update trigger clarification | 17.3.0 | +| 2021-12 | SP#94E | SP-211298 | 3416 | 1 | F | Correction on UAS NF discovery and update UAS related AF and NEF service | 17.3.0 | +| 2021-12 | SP#94E | SP-211290 | 3418 | 1 | F | I-SMF removal triggered by removal of target DNAI | 17.3.0 | +| 2021-12 | SP#94E | SP-211288 | 3421 | 1 | F | Clarification on threshold values | 17.3.0 | +| 2021-12 | SP#94E | SP-211305 | 3422 | 1 | F | Clarification on support of slicing in TWIF scenario | 17.3.0 | +| 2021-12 | SP#94E | SP-211295 | 3428 | - | F | Correction for External Exposure of Network Capability | 17.3.0 | +| 2021-12 | SP#94E | SP-211302 | 3430 | 1 | F | Adding Paging Cause Indication for Voice Service Supported in the RRC Inactive AI | 17.3.0 | +| 2021-12 | SP#94E | SP-211294 | 3431 | 1 | F | Correction for switching 3GPP access between SNPn and PLMN | 17.3.0 | +| 2021-12 | SP#94E | SP-211299 | 3438 | 1 | F | Multiple PTP instances supported in 5GS | 17.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------|--------| +| 2021-12 | SP#94E | SP-211300 | 3439 | - | F | Update on configuration for Sync and Announce reception timeouts | 17.3.0 | +| 2021-12 | SP#94E | SP-211305 | 3440 | 1 | F | Removal of a now obsolete sentence about non-3GPP Access being forbidden in a PLMN | 17.3.0 | +| 2021-12 | SP#94E | SP-211279 | 3442 | 1 | A | Layer below IPsec to enable NAT traversal for TNGF/N3IWF access | 17.3.0 | +| 2021-12 | SP#94E | SP-211278 | 3443 | - | A | Adding AdminCycleTimeExtension and PSFPAdminCycleTimeExtension to PMIC | 17.3.0 | +| 2021-12 | SP#94E | SP-211278 | 3447 | 1 | A | Bridge delay calculation and TSCAI calculation if UE-DS-TT residence time has not been provided | 17.3.0 | +| 2021-12 | SP#94E | SP-211302 | 3449 | 1 | F | Clarification on paging restrictions | 17.3.0 | +| 2021-12 | SP#94E | SP-211287 | 3454 | - | F | RAT type determination on AMF for NR Redcap | 17.3.0 | +| 2021-12 | SP#94E | SP-211305 | 3455 | 1 | F | Support of GERAN/UTRAN access: Annex L alignment to CR 2970r1 to TS 23.501 | 17.3.0 | +| 2021-12 | SP#94E | SP-211279 | 3462 | 1 | F | Clarifications on SEPP | 17.3.0 | +| 2022-03 | SP#95E | SP-220047 | 3414 | 2 | F | Mapping TSCAI between TSN GM clock and 5GS clock | 17.4.0 | +| 2022-03 | SP#95E | SP-220055 | 3464 | 1 | F | Aligning 23.501 and 23.548 wording about the DN accessed via a L-UPF | 17.4.0 | +| 2022-03 | SP#95E | SP-220065 | 3465 | 1 | F | Adding NSWO NF in the architecture | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3466 | 1 | F | Remove the CP based remote provisioning | 17.4.0 | +| 2022-03 | SP#95E | SP-220064 | 3467 | 1 | F | Correct the MUSIM Connection Release feature | 17.4.0 | +| 2022-03 | SP#95E | SP-220064 | 3468 | 1 | F | Correction on MUSIM Paging Cause feature | 17.4.0 | +| 2022-03 | SP#95E | SP-220064 | 3469 | 1 | F | Correct PEI used for MUSIM and network subscriptions | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3470 | 1 | F | DN-AAA server selection when the DCS is not involved during primary authentication | 17.4.0 | +| 2022-03 | SP#95E | SP-220056 | 3471 | - | F | Cleanup for NWDAF, DCCF, MFAF and ADRF services | 17.4.0 | +| 2022-03 | SP#95E | SP-220055 | 3472 | 1 | F | Clarify FQDN in Traffic Influence | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3473 | 1 | F | 5G-EIR clarification | 17.4.0 | +| 2022-03 | SP#95E | SP-220062 | 3474 | 1 | F | Clarification on Authentication and Subscription information checking | 17.4.0 | +| 2022-03 | SP#95E | SP-220062 | 3479 | - | F | Delete the EN on disaster roaming revoking | 17.4.0 | +| 2022-03 | SP#95E | SP-220060 | 3480 | 1 | F | Correction on 5G access stratum time distribution | 17.4.0 | +| 2022-03 | SP#95E | SP-220068 | 3481 | 1 | F | Correction on the MME handling for UPIP during interworking | 17.4.0 | +| 2022-03 | SP#95E | SP-220047 | 3487 | 1 | A | Scheduled Traffic not used for TSCAI | 17.4.0 | +| 2022-03 | SP#95E | SP-220282 | 3489 | 2 | F | Clarifications on NSAC for Emergency and Priority Services | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3491 | - | F | Number of CN paging subgroups | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3492 | - | F | Reference Architecture Editorial Correction | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3495 | 1 | F | Correction for Restriction of use of Enhanced Coverage | 17.4.0 | +| 2022-03 | SP#95E | SP-220051 | 3498 | 1 | F | NR NTN: Correction to TA Handling | 17.4.0 | +| 2022-03 | SP#95E | SP-220053 | 3501 | 1 | F | MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC | 17.4.0 | +| 2022-03 | SP#95E | SP-220042 | 3505 | 1 | A | SSC mode support by the UEs | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3507 | 1 | F | Handling of VPLMN QoS constraints during mobility | 17.4.0 | +| 2022-03 | SP#95E | SP-220058 | 3508 | 1 | F | Clarification on the Registration area when Target NSSAI is indicated | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3510 | 1 | F | Correction for remote provisioning | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3511 | 1 | F | CH architecture update | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3512 | 1 | F | Correction for UE onboarding | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3514 | 1 | F | Correction in AAA selection procedure | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3515 | - | F | Support for emergency calls when no PLMN acceptable cell is available | 17.4.0 | +| 2022-03 | SP#95E | SP-220056 | 3517 | 1 | F | Clarifications for NWDAF profile and NWDAF discovery | 17.4.0 | +| 2022-03 | SP#95E | SP-220067 | 3518 | - | F | Clarification on non-3gpp AN selection | 17.4.0 | +| 2022-03 | SP#95E | SP-220047 | 3522 | 1 | F | Clarification for Routing Indicator on SNPn-enabled UE | 17.4.0 | +| 2022-03 | SP#95E | SP-220060 | 3523 | 1 | F | Multiple NW-TTs associated with a single UPF | 17.4.0 | +| 2022-03 | SP#95E | SP-220060 | 3524 | 1 | F | Clarifications and clean-ups for TSC | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3525 | 1 | F | Clarifications for SNPn onboarding service | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3526 | 1 | F | Corrections for UE access with CH credentials | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3527 | 1 | D | terms alignments and clean-ups for eNPN | 17.4.0 | +| 2022-03 | SP#95E | SP-220062 | 3530 | 1 | F | Disaster roaming disable handling | 17.4.0 | +| 2022-03 | SP#95E | SP-220060 | 3534 | 1 | F | Time Synchronization of the 5GS as IEEE 1588 Boundary Clock | 17.4.0 | +| 2022-03 | SP#95E | SP-220060 | 3535 | 1 | F | Correction for the end-to-end Transparent Clock | 17.4.0 | +| 2022-03 | SP#95E | SP-220059 | 3537 | 1 | F | Correction on UAS NF discovery | 17.4.0 | +| 2022-03 | SP#95E | SP-220045 | 3538 | 1 | A | Corrections to combined N3IWF/ePDG Selection | 17.4.0 | +| 2022-03 | SP#95E | SP-220058 | 3540 | 1 | F | Registration with AMF re-allocation in connected state | 17.4.0 | +| 2022-03 | SP#95E | SP-220062 | 3543 | - | F | Disaster roaming registration type | 17.4.0 | +| 2022-03 | SP#95E | SP-220055 | 3548 | 1 | F | Add missing EASDF descriptions | 17.4.0 | +| 2022-03 | SP#95E | SP-220051 | 3549 | 1 | F | TAIs reporting corresponding to the Selected PLMN | 17.4.0 | +| 2022-03 | SP#95E | SP-220056 | 3552 | 1 | F | Removal of Nnssf_NSRestriction service | 17.4.0 | +| 2022-03 | SP#95E | SP-220281 | 3553 | 2 | F | Correction of Subscription-related Priority Mechanism | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3554 | 1 | F | Inter-system configuration transfer | 17.4.0 | +| 2022-03 | SP#95E | SP-220051 | 3555 | 1 | F | Correction of Mobility Restrictions handling for emergency calls | 17.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|------------------------------------------------------------------------------------------------------|--------| +| 2022-03 | SP#95E | SP-220067 | 3556 | 1 | F | Clarification on TAI configured for Non 3GPP access | 17.4.0 | +| 2022-03 | SP#95E | SP-220048 | 3558 | 1 | A | LLDP neighbour discovery information fixes | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3559 | 1 | F | Clarification of ProSe support in SNPN | 17.4.0 | +| 2022-03 | SP#95E | SP-220062 | 3563 | 1 | F | Alignment with use of Disaster Roaming Enabled Configuration | 17.4.0 | +| 2022-03 | SP#95E | SP-220057 | 3567 | 1 | F | Clean-up the clause on UP onboarding via ON-SNPN | 17.4.0 | +| 2022-03 | SP#95E | SP-220047 | 3568 | 1 | A | Handling of untagged frames in TSN scenarios | 17.4.0 | +| 2022-03 | SP#95E | SP-220047 | 3570 | 1 | A | Add missing SupportedListMax for gate control information in PMIC and UMIC | 17.4.0 | +| 2022-03 | SP#95E | SP-220058 | 3571 | 1 | F | Clarification on support of multiple NSACFs | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3577 | 1 | F | Completing description of NF profile | 17.4.0 | +| 2022-03 | SP#95E | SP-220066 | 3578 | 1 | F | Paging Early Indication: Removal of Editor's notes | 17.4.0 | +| 2022-06 | SP#96 | SP-220412 | 3317 | 7 | B | Enabling slice priority and slice groups for RRM purposes | 17.5.0 | +| 2022-06 | SP#96 | SP-220404 | 3485 | 2 | F | Correcting the 5G AS time distribution procedure | 17.5.0 | +| 2022-06 | SP#96 | SP-220412 | 3539 | 4 | B | Enabling configuration of Network Slice AS Groups | 17.5.0 | +| 2022-06 | SP#96 | SP-220406 | 3580 | 3 | F | Disaster Roaming service indication | 17.5.0 | +| 2022-06 | SP#96 | SP-220400 | 3581 | 1 | F | Role of Credential Holder | 17.5.0 | +| 2022-06 | SP#96 | SP-220401 | 3582 | 1 | F | Removal of NSACF from HPLMN in LBO Model | 17.5.0 | +| 2022-06 | SP#96 | SP-220401 | 3584 | 1 | F | Clarification on determination of Registration Area | 17.5.0 | +| 2022-06 | SP#96 | SP-220400 | 3589 | 1 | F | Network Slicing Support in SNPN | 17.5.0 | +| 2022-06 | SP#96 | SP-220411 | 3591 | 1 | F | Alignment to BBF LS 512 (Frame route, BBF references) | 17.5.0 | +| 2022-06 | SP#96 | SP-220411 | 3593 | 1 | F | Handling of ARP for IMS voice service in home routed roaming | 17.5.0 | +| 2022-06 | SP#96 | SP-220407 | 3596 | - | F | Correction of message name for paging restriction information | 17.5.0 | +| 2022-06 | SP#96 | SP-220406 | 3599 | 1 | F | Session related subscription information | 17.5.0 | +| 2022-06 | SP#96 | SP-220406 | 3600 | 2 | F | Clarification on UE 5GMM Capability | 17.5.0 | +| 2022-06 | SP#96 | SP-220406 | 3601 | - | F | Removing the editor's note related to CT1 | 17.5.0 | +| 2022-06 | SP#96 | SP-220394 | 3604 | 1 | F | Criterion of Verification of UE location for UE registering via 5G Satellite Access | 17.5.0 | +| 2022-06 | SP#96 | SP-220404 | 3605 | 1 | F | Corrections to Survival Time description | 17.5.0 | +| 2022-06 | SP#96 | SP-220404 | 3606 | 1 | F | Corrections to time synchronization description | 17.5.0 | +| 2022-06 | SP#96 | SP-220394 | 3607 | 1 | F | Clarification on AMF obtaining the satellite-related information | 17.5.0 | +| 2022-06 | SP#96 | SP-220400 | 3609 | 1 | F | SMF UP remote provisioning capability | 17.5.0 | +| 2022-06 | SP#96 | SP-220396 | 3612 | 2 | F | AMF selection to support HLcom feature for RedCap using power saving function | 17.5.0 | +| 2022-06 | SP#96 | SP-220400 | 3613 | - | F | DCS supporting AUSF/UDM and AAA server functionality | 17.5.0 | +| 2022-06 | SP#96 | SP-220408 | 3617 | 4 | F | 23.501: NSWO and N3GPP access support | 17.5.0 | +| 2022-06 | SP#96 | SP-220394 | 3621 | 1 | F | RAN Initiated UE Context Release for UE using NR satellite access | 17.5.0 | +| 2022-06 | SP#96 | SP-220400 | 3623 | 2 | F | Clarification on the FQDN(s) and IP address(es) of PVS for remote provisioning | 17.5.0 | +| 2022-06 | SP#96 | SP-220404 | 3624 | 1 | F | Clarification on how the TSFTSF assign the NW-TT port to PPT instance | 17.5.0 | +| 2022-06 | SP#96 | SP-220404 | 3625 | 2 | F | Clarification on 5G access stratum distribution in mobility | 17.5.0 | +| 2022-06 | SP#96 | SP-220406 | 3626 | - | F | End of disaster condition | 17.5.0 | +| 2022-06 | SP#96 | SP-220406 | 3628 | 1 | C | UE capabilities indication for UPU with Disaster Roaming information | 17.5.0 | +| 2022-06 | SP#96 | SP-220688 | 3633 | 3 | F | RFSP Index authorized by PCF and subscribed RFSP Index | 17.5.0 | +| 2022-06 | SP#96 | SP-220410 | 3635 | 1 | F | NRF discovery and selection | 17.5.0 | +| 2022-06 | SP#96 | SP-220391 | 3642 | 1 | A | clarifications for CAG access control for a UE without mobility restrictions | 17.5.0 | +| 2022-06 | SP#96 | SP-220410 | 3645 | 1 | F | Correction of UE behaviour upon mobility between GERAN/UTRAN and 5GS | 17.5.0 | +| 2022-06 | SP#96 | SP-220391 | 3649 | 1 | A | Correction of the Signalling Based Tracing support | 17.5.0 | +| 2022-06 | SP#96 | SP-220410 | 3650 | 1 | F | UDR storing of non-subscriber related data | 17.5.0 | +| 2022-06 | SP#96 | SP-220401 | 3652 | 1 | F | Clarification on roaming for NSAC procedure | 17.5.0 | +| 2022-06 | SP#96 | SP-220394 | 3653 | 1 | F | Remove country of UE location from clause 5.16.4.1 in TS23.501 | 17.5.0 | +| 2022-06 | SP#96 | SP-220411 | 3654 | 1 | F | Correction of NSSF involvement in Registration procedure when NSSAA is used | 17.5.0 | +| 2022-06 | SP#96 | SP-220410 | 3655 | 1 | F | Correction of UE Configuration Update procedure conditions for Registration Required and NAS Release | 17.5.0 | +| 2022-09 | SP#97E | SP-220783 | 3603 | 4 | F | Defining the time distribution methods | 17.6.0 | +| 2022-09 | SP#97E | SP-220780 | 3616 | 2 | F | Clarification on UE-Slice-MBR | 17.6.0 | +| 2022-09 | SP#97E | SP-220779 | 3629 | 2 | F | DN-AAA server selection during UE onboarding | 17.6.0 | +| 2022-09 | SP#97E | SP-220771 | 3647 | 2 | A | Clarification of UE egress terminology | 17.6.0 | +| 2022-09 | SP#97E | SP-220789 | 3659 | 1 | F | Handling of PDU Sessions for Emergency services | 17.6.0 | +| 2022-09 | SP#97E | SP-220788 | 3660 | 1 | B | Alignment of SBI-based SMS | 17.6.0 | +| 2022-09 | SP#97E | SP-220789 | 3661 | - | F | Correction on Reference Architecture | 17.6.0 | +| 2022-09 | SP#97E | SP-220785 | 3664 | 1 | F | UCU procedure for MINT update | 17.6.0 | +| 2022-09 | SP#97E | SP-220789 | 3665 | 1 | F | ULI provision with PScell information | 17.6.0 | +| 2022-09 | SP#97E | SP-220769 | 3666 | 1 | C | Periodic update time from UE | 17.6.0 | +| 2022-09 | SP#97E | SP-220789 | 3674 | 1 | F | Handover capability detection | 17.6.0 | +| 2022-09 | SP#97E | SP-220789 | 3676 | 1 | F | Closing open issues on RAN slicing | 17.6.0 | +| 2022-09 | SP#97E | SP-220789 | 3677 | 1 | F | Missing UDSF timer service | 17.6.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------|---------------| +| 2022-09 | SP#97E | SP-220776 | 3678 | 1 | F | PMF UAD and UAT message handling clarifications | 17.6.0 | +| 2022-09 | SP#97E | SP-220786 | 3683 | 1 | F | Clarifications on Priority Subscription | 17.6.0 | +| 2022-09 | SP#97E | SP-220783 | 3685 | - | F | Clarification on 5G access stratum distribution in mobility and AM policy modification | 17.6.0 | +| 2022-09 | SP#97E | SP-220774 | 3687 | 1 | F | AMF sends forbidden TAI(s) to UE | 17.6.0 | +| 2022-09 | SP#97E | SP-220771 | 3689 | 1 | A | Correction on 5G VN group management | 17.6.0 | +| 2022-09 | SP#97E | SP-220789 | 3697 | 1 | B | Access Network selection for 5G NSWO | 17.6.0 | +| 2022-09 | SP#97E | SP-220787 | 3698 | 1 | F | Clarification related to Inactive state | 17.6.0 | +| 2022-09 | SP#97E | SP-220785 | 3700 | 1 | F | Clarification related to emergency service | 17.6.0 | +| 2022-12 | SP#98E | - | - | - | - | MCC Correction to add missing N1 line to Figure 4.2.10-1 | 17.7.0 | +| 2022-12 | SP#98E | SP-221079 | 3583 | 4 | F | Clarification on Mapped NSSAI | 17.7.0 | +| 2022-12 | SP#98E | SP-221069 | 3634 | 2 | F | Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF | 17.7.0 | +| 2022-12 | SP#98E | SP-221080 | 3663 | 2 | F | Correction related to traffic correlation in PCC rule | 17.7.0 | +| 2022-12 | SP#98E | SP-221079 | 3673 | 2 | F | Mapped NSSAI alignment with stage-3 | 17.7.0 | +| 2022-12 | SP#98E | SP-221071 | 3675 | 2 | F | Alignment with SA3 agreement on usage of SUCI when CH is legacy AAA | 17.7.0 | +| 2022-12 | SP#98E | SP-221072 | 3693 | 2 | F | Pending NSSAI and NSSRG | 17.7.0 | +| 2022-12 | SP#98E | SP-221080 | 3704 | 1 | F | ULI with TAI for non-3GPP access | 17.7.0 | +| 2022-12 | SP#98E | SP-221062 | 3709 | - | A | R17 Correction on TNGF functionality | 17.7.0 | +| 2022-12 | SP#98E | SP-221079 | 3711 | 1 | F | Emergency PDU session transfer | 17.7.0 | +| 2022-12 | SP#98E | SP-221079 | 3712 | 1 | F | Monitoring event in 5GS to EPS mobility | 17.7.0 | +| 2022-12 | SP#98E | SP-221071 | 3731 | 1 | F | Clarification when access SNPN using CH with AAA-S | 17.7.0 | +| 2022-12 | SP#98E | SP-221080 | 3742 | 1 | F | Correction of reference for RedCap indication from UE | 17.7.0 | +| 2022-12 | SP#98E | SP-221079 | 3747 | 1 | F | Correction on conditions for using SPI for UE derived QoS rules | 17.7.0 | +| 2022-12 | SP#98E | SP-221066 | 3801 | 2 | F | NSAG Information validation in Equivalent PLMN | 17.7.0 | +| 2022-12 | SP#98E | SP-221094 | 3701 | 4 | B | Secondary DN authentication and authorization in EPS IWK case | 18.0.0 | +| 2022-12 | SP#98E | SP-221090 | 3705 | 1 | B | Support of RRC_INACTIVE with long eDRX | 18.0.0 | +| 2022-12 | SP#98E | SP-221084 | 3707 | 1 | B | N3IWF selection enhancement for support of S-NSSAI needed by UE | 18.0.0 | +| 2022-12 | SP#98E | SP-221085 | 3710 | 1 | C | RFSP index in use at 5GS to EPS mobility | 18.0.0 | +| 2022-12 | SP#98E | SP-221085 | 3713 | 1 | B | RFSP index during interworking | 18.0.0 | +| 2022-12 | SP#98E | SP-221087 | 3714 | 5 | B | Support of Non-3GPP access for SNPN | 18.0.0 | +| 2022-12 | SP#98E | SP-221089 | 3715 | 1 | B | TS 23.501 Enhancing External Exposure of Network Capability | 18.0.0 | +| 2022-12 | SP#98E | SP-221093 | 3723 | 1 | B | Update for UPF registration and event exposure related context concluded in FS_UPEAS | 18.0.0 | +| 2022-12 | SP#98E | SP-221087 | 3730 | - | B | Equivalent SNPN support | 18.0.0 | +| 2022-12 | SP#98E | SP-221094 | 3733 | - | F | De-activation timer for eCall only mode UE in RRC_INACTIVE | 18.0.0 | +| 2022-12 | SP#98E | SP-221092 | 3734 | 5 | B | RAN feedback for burst sending time adjustment | 18.0.0 | +| 2022-12 | SP#98E | SP-221093 | 3737 | 1 | B | Introduction of UPEAS | 18.0.0 | +| 2022-12 | SP#98E | SP-221091 | 3749 | 1 | B | Support of unavailability period | 18.0.0 | +| 2022-12 | SP#98E | SP-221094 | 3752 | 1 | B | Reference point numbers for charging | 18.0.0 | +| 2022-12 | SP#98E | SP-221092 | 3762 | 3 | B | Adding time synchronization service based on subscription | 18.0.0 | +| 2022-12 | SP#98E | SP-221092 | 3767 | 2 | B | Support for coverage area filters for time synchronization service | 18.0.0 | +| 2022-12 | SP#98E | SP-221139 | 3772 | 3 | B | Discovery and Selection of the NWDAF Supporting Federated Learning in 5GC | 18.0.0 | +| 2022-12 | SP#98E | SP-221139 | 3783 | 2 | B | NWDAF discovery principle enhancements for enhanced model sharing | 18.0.0 | +| 2022-12 | SP#98E | SP-221140 | 3785 | 2 | B | Multiple NSACF architecture enhancement | 18.0.0 | +| 2022-12 | SP#98E | SP-221086 | 3788 | 2 | B | KI#4 23.501 AF traffic influence for common EAS, DNAI selection | 18.0.0 | +| 2022-12 | SP#98E | SP-221081 | 3790 | 2 | B | Verification of UE location update in 23.501 | 18.0.0 | +| 2022-12 | SP#98E | SP-221083 | 3793 | 2 | B | Support of Satellite Edge Computing via UPF deployed on satellite | 18.0.0 | +| 2022-12 | SP#98E | SP-221083 | 3794 | 4 | B | Support of local switch via UPF deployed on satellite for GEO backhaul case | 18.0.0 | +| 2022-12 | SP#98E | SP-221096 | 3796 | 2 | B | Enhancements of PCF Services and NEF Services | 18.0.0 | +| 2022-12 | SP#98E | SP-221083 | 3803 | 2 | B | QoS Monitoring for Dynamic Satellite Backhaul | 18.0.0 | +| 2022-12 | SP#98E | SP-221092 | 3811 | 2 | B | Interworking with TSN network deployed in the transport network | 18.0.0 | +| 2022-12 | SP#98E | SP-221141 | 3813 | 3 | B | Introduction of Mobile Base Station Relay | 18.0.0 | +| 2023-03 | SP#99 | SP-230080 | 3594 | 1 | D | RRC state and CM state terminology alignment | 18.1.0 | +| 2023-03 | SP#99 | SP-230077 | 3720 | 2 | B | UPF event exposure service for TSC management | 18.1.0 | +| 2023-03 | SP#99 | SP-230070 | 3745 | 2 | B | MPS when access to 5GC is WLAN | 18.1.0 | +| 2023-03 | SP#99 | SP-230051 | 3755 | 1 | C | Group Message Delivery | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3759 | 7 | B | Support of XR and Media Services | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 3761 | 4 | C | Introducing selection of more granular set of UEs | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 3789 | 2 | B | Common EAS/DNAI selection by AF | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3792 | 7 | B | PCF support of 5GS Packet Delay Variation monitoring based on QoS monitoring mechanism and exposed to AF | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 3807 | 1 | B | Reporting the RAN timing synchronization status change from AMF to TSCTSF | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 3820 | 5 | B | Edge Relocation within the same hosting PLMN's EHEs | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3821 | 2 | B | N5CW device access to SNPN services | 18.1.0 | +| 2023-03 | SP#99 | SP-230169 | 3822 | 7 | B | KI#4: Support for Centralized NSACF in a PLMN with multi-service | 18.1.0 | + +| | | | | | | | | +|--|--|--|--|--|--|-------|--| +| | | | | | | areas | | +|--|--|--|--|--|--|-------|--| + +| | | | | | | | | +|---------|-------|-----------|------|----|---|--------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | SP#99 | SP-230064 | 3823 | 6 | B | KI#4: Support for HPLMN admission mode while Roaming | 18.1.0 | +| 2023-03 | SP#99 | SP-230077 | 3825 | 1 | B | Support of NAT exposure in 23.501 according to the conclusion in UPEAS | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 3830 | 1 | B | The support of Home Routed PDU Session supporting Session Breakout in VPLMN (HR-SBO) | 18.1.0 | +| 2023-03 | SP#99 | SP-230080 | 3831 | 1 | F | Impacts of CH architecture in N3IWF selection | 18.1.0 | +| 2023-03 | SP#99 | SP-230051 | 3834 | 1 | B | MBS service for UE using power saving functions | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3835 | 3 | C | Support for NSWO with CH | 18.1.0 | +| 2023-03 | SP#99 | SP-230055 | 3837 | 1 | F | Resolving EN on PCF's awareness of modified RFSP index indicating a change of priority from 5GC to EPC | 18.1.0 | +| 2023-03 | SP#99 | SP-230034 | 3840 | 1 | A | PDU Session Type Selection in the URSP Rule | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3841 | - | B | Clarification of SNPN access mode | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3842 | 3 | B | Introduction to Localized Services | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3992 | 3 | B | Enabling Access to Localized Services | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3843 | 1 | B | Support for leaving network that provides access to localized services | 18.1.0 | +| 2023-03 | SP#99 | SP-230057 | 3844 | 9 | B | Support of integration with IETF Deterministic Networking | 18.1.0 | +| 2023-03 | SP#99 | SP-230044 | 3848 | - | A | Emergency configuration data update | 18.1.0 | +| 2023-03 | SP#99 | SP-230078 | 3850 | - | F | Update for the support of mobile IAB | 18.1.0 | +| 2023-03 | SP#99 | SP-230073 | 3854 | 4 | B | PIN support in 5GC | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3855 | 11 | B | Introduction of support for L4S | 18.1.0 | +| 2023-03 | SP#99 | SP-230048 | 3858 | 1 | B | Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) | 18.1.0 | +| 2023-03 | SP#99 | SP-230081 | 3859 | 1 | B | IPv6 prefix delegation in 5GS | 18.1.0 | +| 2023-03 | SP#99 | SP-230075 | 3860 | 1 | B | SFC CR 23.501 | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3864 | 5 | B | Policy control enhancements to support multi-modal flows | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 3867 | 5 | B | Change of Network Slice instance for PDU sessions | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 3870 | 1 | B | Removing ENs for TSN TN integration | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 3871 | 1 | F | Clarification on for TSN TN integration | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 3872 | - | B | Removing EN on UL scenario of Reactive RAN feedback for burst sending time adjustment | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3875 | 14 | B | Introduction of support for Jitter Measurement and End of Data Burst reporting to the NG-RAN | 18.1.0 | +| 2023-03 | SP#99 | SP-230056 | 3878 | 1 | B | Support for non-3GPP access path switching | 18.1.0 | +| 2023-03 | SP#99 | SP-230081 | 3881 | 2 | B | 5QI for V2X message delivery via MBS | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3883 | 7 | B | UE discover, select and access to a Hosting network for Localized services | 18.1.0 | +| 2023-03 | SP#99 | SP-230081 | 3886 | - | B | 23.501 - Spending Limits for AM and UE Policies in the 5GC | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3887 | 6 | B | Introduction of 5GS Information Exposure | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 3892 | 6 | B | Support for network timing synchronization status and reporting KI1 - description | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 3895 | 4 | C | The support for Periodicity feedback in Enablers for Time Sensitive Communications and Time Synchronization feature KI6. | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3896 | 12 | B | Update TS23.501 to reflect conclusion of KI#4 for XRM in TR23.700-60 | 18.1.0 | +| 2023-03 | SP#99 | SP-230073 | 3897 | 12 | B | PIN communication configuration | 18.1.0 | +| 2023-03 | SP#99 | SP-230073 | 3898 | 3 | B | PIN policy configuration | 18.1.0 | +| 2023-03 | SP#99 | SP-230054 | 3910 | 5 | B | Assistance to Member Selection Functionality for Application Operation | 18.1.0 | +| 2023-03 | SP#99 | SP-230073 | 3912 | 1 | B | Non-3GPP QoS and delay budget - 23.501 | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 3914 | 1 | B | Service area provisioning and LADN aspects for enhanced group management | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3919 | 7 | B | Introduction of KI#6 conclusion: uplink-downlink transmission coordination | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 3923 | 10 | B | Network exposure support for XR services | 18.1.0 | +| 2023-03 | SP#99 | SP-230065 | 3924 | 1 | B | Support URSP provisioning in EPS | 18.1.0 | +| 2023-03 | SP#99 | SP-230062 | 3925 | 1 | B | TS 23.501 enhancements for federated learning. | 18.1.0 | +| 2023-03 | SP#99 | SP-230062 | 3926 | 1 | B | TS 23.501 enhancements for model sharing. | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 3927 | 6 | B | Clarifications on Onboarding in SNPN supporting localized services | 18.1.0 | +| 2023-03 | SP#99 | SP-230080 | 3928 | 1 | F | TS 23.501: Clarification of handling of the non-3GPP PDU session in Non-allowed service area | 18.1.0 | +| 2023-03 | SP#99 | SP-230062 | 3929 | 4 | B | Considering ML model management capability during ADRF discovery and selection | 18.1.0 | +| 2023-03 | SP#99 | SP-230078 | 3933 | 1 | B | Providing cell ID/TAC of MBSR for services | 18.1.0 | +| 2023-03 | SP#99 | SP-230040 | 3935 | 1 | A | Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access | 18.1.0 | +| 2023-03 | SP#99 | SP-230056 | 3937 | 1 | B | Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 3939 | 7 | B | Improved network control of the UE behaviour for a network slice | 18.1.0 | +| 2023-03 | SP#99 | SP-230043 | 3948 | 1 | A | 5G NSWO clarifications and corrections | 18.1.0 | +| 2023-03 | SP#99 | SP-230077 | 3949 | 1 | C | User Plane Function Selection for UPEAS | 18.1.0 | +| 2023-03 | SP#99 | SP-230053 | 3953 | 1 | B | TNGF selection enhancement for support of S-NSSAI needed by | 18.1.0 | + +| | | | | | | | | +|--|--|--|--|--|--|----|--| +| | | | | | | UE | | +|--|--|--|--|--|--|----|--| + +| | | | | | | | | +|---------|-------|-----------|------|----|---|--------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | SP#99 | SP-230387 | 3956 | 13 | B | Transfer of Satellite Coverage Data to a UE and AMF | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 3959 | 7 | B | Hierarchical NSAC architecture enhancement | 18.1.0 | +| 2023-03 | SP#99 | SP-230077 | 3962 | 1 | F | Direct Exposure from UPF and UPF selection | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 3964 | 1 | B | KI#3, NEF exposure for handling PDU Session Type change and managing temporal invalidity/validity condition for a group of UEs | 18.1.0 | +| 2023-03 | SP#99 | SP-230049 | 3966 | 3 | B | Paging enhancement during satellite discontinuous coverage | 18.1.0 | +| 2023-03 | SP#99 | SP-230054 | 3968 | 4 | B | 5GS Assistance for Application AI/ML operation: General clause | 18.1.0 | +| 2023-03 | SP#99 | SP-230056 | 3973 | 1 | B | Introduction of the MPQUIC Steering Functionality | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 3981 | 1 | F | Update for controlling time synchronization service based on Subscription | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 3982 | 1 | B | Group MBR | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 3984 | 1 | B | UE-to-UE QoS for a group | 18.1.0 | +| 2023-03 | SP#99 | SP-230050 | 3985 | - | B | Add description for PSA UPF selection | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 3986 | 1 | B | Allowing UE to simultaneously send data to different groups with different QoS policy | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 3987 | 5 | B | KI#4 AF traffic influence for common EAS, DNAI selection | 18.1.0 | +| 2023-03 | SP#99 | SP-230055 | 3991 | 1 | B | Clarification of AMF behaviour when it receives RFSP Index in Use Validity Time from MME during UE mobility from EPS to 5GS | 18.1.0 | +| 2023-03 | SP#99 | SP-230040 | 3998 | 1 | A | Pending NSSAI and AMF Relocation in Connected mode 23.501. | 18.1.0 | +| 2023-03 | SP#99 | SP-230050 | 3999 | 1 | B | Clarification of N19 forwarding for local switch via PSA UPF on GEO | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 4004 | 5 | B | Optimizations for the support of time validity policies for a network slice and graceful network slice PDU sessions release. | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 4010 | 1 | B | Add the default QoS parameters for 5G VN group data | 18.1.0 | +| 2023-03 | SP#99 | SP-230038 | 4018 | 1 | A | Correction of supported services in UPF | 18.1.0 | +| 2023-03 | SP#99 | SP-230056 | 4019 | 1 | B | Introducing Redundant Steering Mode | 18.1.0 | +| 2023-03 | SP#99 | SP-230049 | 4020 | 6 | B | Wait range during discontinuous coverage. | 18.1.0 | +| 2023-03 | SP#99 | SP-230073 | 4028 | 5 | B | Informative Annex on PIN Architecture | 18.1.0 | +| 2023-03 | SP#99 | SP-230386 | 4033 | 13 | B | Support of discontinuous coverage | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 4035 | 7 | B | Introduction of partially Allowed NSSAI and Partially Rejected S-NSSAI | 18.1.0 | +| 2023-03 | SP#99 | SP-230315 | 4036 | 4 | B | Introduction of Alternative S-NSSAI replacement determined by NSSF | 18.1.0 | +| 2023-03 | SP#99 | SP-230078 | 4039 | 1 | F | Resolving EN on emergency services. | 18.1.0 | +| 2023-03 | SP#99 | SP-230373 | 4040 | 3 | F | Not allowed to act as MBSR handling | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 4042 | 3 | B | Edge relocation with common DNAI | 18.1.0 | +| 2023-03 | SP#99 | SP-230247 | 4046 | 12 | B | Support of PDU Set based handling | 18.1.0 | +| 2023-03 | SP#99 | SP-230080 | 4049 | - | F | Corrections of Nudm service operations list | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 4054 | - | B | AF obtaining DNAI associated to EAS | 18.1.0 | +| 2023-03 | SP#99 | SP-230080 | 4056 | 1 | F | Generalization of QoS monitoring control description | 18.1.0 | +| 2023-03 | SP#99 | SP-230080 | 4057 | 1 | F | Clarifications for GTP-U Path Monitoring | 18.1.0 | +| 2023-03 | SP#99 | SP-230080 | 4058 | 1 | F | Restructuring of user plane management clause | 18.1.0 | +| 2023-03 | SP#99 | SP-230075 | 4069 | 1 | B | Support for Service Function Chaining in 5GS | 18.1.0 | +| 2023-03 | SP#99 | SP-230062 | 4070 | - | B | Discovery and selection of NWDAF with FL support - Resolve EN | 18.1.0 | +| 2023-03 | SP#99 | SP-230044 | 4076 | 1 | A | Mapped NSSAI when UE is roaming | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 4077 | 6 | B | Support of reduced network slice availability | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 4078 | 2 | B | Support of graceful/gradual termination of PDU sessions during network slice decommissioning | 18.1.0 | +| 2023-03 | SP#99 | SP-230062 | 4080 | 1 | B | Using network analytics for roaming scenarios | 18.1.0 | +| 2023-03 | SP#99 | SP-230115 | 4081 | 1 | B | CN based MT communication capability indication | 18.1.0 | +| 2023-03 | SP#99 | SP-230064 | 4083 | 10 | B | Support of network slice replacement | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 4086 | 1 | B | KI#1: Support the enhancement of group attribute management | 18.1.0 | +| 2023-03 | SP#99 | SP-230068 | 4087 | 1 | B | KI#3: provisioning of traffic characteristics and monitoring of performance characteristics | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 4088 | 4 | B | Clarify on periodicity adaption on Proactive feedback | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 4089 | 4 | F | Clarification for Controlling time synchronization service based on the Subscription | 18.1.0 | +| 2023-03 | SP#99 | SP-230073 | 4092 | 6 | B | PIN definition and architecture | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 4095 | 1 | B | SNPN broadcast system information and manual network selection for localized service | 18.1.0 | +| 2023-03 | SP#99 | SP-230044 | 4101 | 1 | A | UDM determination Internal Group ID values for 5G VN group management | 18.1.0 | +| 2023-03 | SP#99 | SP-230062 | 4105 | 1 | B | Update NEF to support NWDAF-assisted application detection | 18.1.0 | +| 2023-03 | SP#99 | SP-230078 | 4107 | 1 | C | UE mobility when moving together with a MBSR cell | 18.1.0 | +| 2023-03 | SP#99 | SP-230078 | 4108 | 1 | B | Configuration of the MBSR node | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 4118 | 3 | B | Support of non-3GPP access to SNPN | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 4119 | 3 | B | Support of allowed CAG list with validity condition | 18.1.0 | +| 2023-03 | SP#99 | SP-230063 | 4124 | 3 | B | Support of wireline access as access to SNPN | 18.1.0 | +| 2023-03 | SP#99 | SP-230054 | 4128 | 4 | B | Support of Group AF Sessions for QoS Resource Allocation and QoS monitoring operation | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 4133 | 2 | B | Ensuring that a geographical area requested for a time sync service coincides with a RA | 18.1.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | SP#99 | SP-230040 | 4137 | 1 | A | UE-Slice-MBR clarifications including for priority services | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 4144 | - | B | Common EAS re-discovery initiated by SMF | 18.1.0 | +| 2023-03 | SP#99 | SP-230170 | 4156 | 2 | B | Event exposure enhancement for enhanced NSAC architecture | 18.1.0 | +| 2023-03 | SP#99 | SP-230058 | 4160 | 2 | B | Delivery of Traffic Influence information for Home Routed-Session Breakout (HR-SBO) support | 18.1.0 | +| 2023-03 | SP#99 | SP-230052 | 4180 | 1 | C | Corrections for the description of coverage area support for time synchronization service KI2 | 18.1.0 | +| 2023-06 | SP#100 | SP-230490 | 3748 | 2 | F | Support for 5QI Priority Level in QoS constraints | 18.2.0 | +| 2023-06 | SP#100 | SP-230469 | 3764 | 6 | B | Extension of NWDAF registration information to reflect new accuracy checking capability | 18.2.0 | +| 2023-06 | SP#100 | SP-230495 | 3922 | 2 | F | Update for the description of the Nupf interface in 5G reference architecture | 18.2.0 | +| 2023-06 | SP#100 | SP-230490 | 4037 | 2 | F | NWDAF discovery with overlapping Serving Areas | 18.2.0 | +| 2023-06 | SP#100 | SP-230463 | 4155 | 5 | A | Rewording of NOTE on AF Specific UE identifier | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4183 | 3 | B | Support of extra traffic characteristics for alternative QoS profile | 18.2.0 | +| 2023-06 | SP#100 | SP-230491 | 4189 | - | B | Dynamically changing AM policies for inbound roamers using LBO | 18.2.0 | +| 2023-06 | SP#100 | SP-230476 | 4190 | - | F | KI#3 -5GS to EPS mobility | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4191 | 1 | F | Translation of Internal-External Information for Assisting Application Layer AI/ML Operations | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4192 | 6 | F | High level feature description for AIMLsys | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4196 | 1 | C | Resolving (Removing) ENs for TSN TN integration | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 4202 | 1 | C | Clarify the allowed CAG list with validity condition | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 4205 | 1 | C | SNPN selection for access to localized services | 18.2.0 | +| 2023-06 | SP#100 | SP-230459 | 4210 | 1 | C | Updates to non-3GPP access path switching | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4211 | 1 | C | Corrections to handling of LADN area per DNN and S-NSSAI | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4216 | 9 | C | Revision on the support of network timing synchronization status and reporting | 18.2.0 | +| 2023-06 | SP#100 | SP-230483 | 4218 | 1 | C | Co-existence of Small Data Transmission and CN based MT communication handling for UE in RRC_INACTIVE | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4219 | 6 | C | Resolution of EN for L4S | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4224 | 1 | F | PDU session sharing among PINs | 18.2.0 | +| 2023-06 | SP#100 | SP-230496 | 4228 | 6 | C | Additional User Location Information | 18.2.0 | +| 2023-06 | SP#100 | SP-230490 | 4229 | 1 | F | IAB node release handling | 18.2.0 | +| 2023-06 | SP#100 | SP-230483 | 4231 | 1 | F | N2 release handling for RRC_INACTIVE | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4234 | 1 | F | Resolving open issues related to Alternative S-NSSAI | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4235 | - | F | Resolving open issues for temporarily available network slices | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4236 | 1 | C | Resolving open issues for Network Slices with Network Slice Area of Service not matching deployed TAs | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 4238 | - | F | Additional requirements for N3IWF selection for onboarding | 18.2.0 | +| 2023-06 | SP#100 | SP-230451 | 4240 | 4 | C | Closing ENs for the procedures for discontinuous coverage reporting | 18.2.0 | +| 2023-06 | SP#100 | SP-230452 | 4246 | 1 | B | Optimization consideration for satellite backhaul QoS monitoring | 18.2.0 | +| 2023-06 | SP#100 | SP-230494 | 4249 | - | B | 5QI for A2X message delivery via MBS | 18.2.0 | +| 2023-06 | SP#100 | SP-230476 | 4253 | 1 | B | Support URSP provisioning in EPS | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4255 | 1 | F | R18 AIMLsys_General_23501_CR_EN on AIML traffic | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4257 | - | F | R18 AIMLsys_KI1_23501_CR_SingleSO_for_QoS | 18.2.0 | +| 2023-06 | SP#100 | SP-230472 | 4259 | 1 | A | Number of PDU session slice availability check during EPC IWK | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 4270 | 1 | B | Network access control when the UE accesses an SNPN that provides access for Localized Services | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4271 | 4 | F | Selection of Common DNAI | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4278 | 1 | F | KI#6 text alignment text | 18.2.0 | +| 2023-06 | SP#100 | SP-230460 | 4280 | 1 | F | Architectural diagram change for DetNet | 18.2.0 | +| 2023-06 | SP#100 | SP-230460 | 4281 | 1 | B | UPF discovery and Selection for DetNet | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4284 | 7 | C | Clarifying SMF behaviour for non-3GPP delay budget | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4287 | 6 | B | PIN identifiers | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 4288 | 1 | B | Configuration of Credentials Holder for determining SNPN selection information (Annex N.x) | 18.2.0 | +| 2023-06 | SP#100 | SP-230452 | 4293 | 1 | B | Update the descriptions for supporting Edge Computing on satellite | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4294 | 3 | C | QoS Monitoring and 5GS information exposure update | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 4300 | 1 | F | N3IWF selection for emergency services for UE not equipped with valid SNPN credentials | 18.2.0 | +| 2023-06 | SP#100 | SP-230451 | 4302 | 1 | B | Provisioning Satellite Coverage Availability to the AMF | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4306 | 1 | B | Support for 5G VN group with multiple SMF(Set)s | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4313 | 1 | B | KI#4 implementation of cross-SMF VN group communication | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4314 | 1 | F | KI#5 correction on the QoS support for UE with multiple groups | 18.2.0 | +| 2023-06 | SP#100 | SP-230469 | 4318 | 1 | B | DCCF Discovery principle enhancements for DCCF relocation in TS 23.501 | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4322 | 9 | B | EN resolving for KI#8 Except TSCAC and clarifications on AF inputs | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4326 | - | F | Solve the EN about handling of the PEMC in 5GC in relation with PIN | 18.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|----|---|-------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-06 | SP#100 | SP-230484 | 4327 | 1 | F | Solve the EN about PIN deletion, activation and deactivation | 18.2.0 | +| 2023-06 | SP#100 | SP-230459 | 4330 | 1 | F | Clarification on Redundant Steering Mode | 18.2.0 | +| 2023-06 | SP#100 | SP-230459 | 4342 | - | F | Clarification of RTT measurement for RSM | 18.2.0 | +| 2023-06 | SP#100 | SP-230456 | 4351 | 5 | F | Clarification on N3IWF/TNGF selection to support of S-NSSAI needed by UE | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4354 | 3 | C | Explicit subscription to NSSF for network slice instance replacement | 18.2.0 | +| 2023-06 | SP#100 | SP-230496 | 4367 | 1 | B | Open issue resolutions for MBSR support | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4370 | 1 | C | Support of provisioning periodicity set | 18.2.0 | +| 2023-06 | SP#100 | SP-230469 | 4372 | - | C | Updates for registration and discovery for FL entity | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4376 | 3 | B | Update supporting Edge Computing | 18.2.0 | +| 2023-06 | SP#100 | SP-230490 | 4377 | 1 | F | Add FQDN in Traffic Detection Information | 18.2.0 | +| 2023-06 | SP#100 | SP-230495 | 4378 | 1 | B | Considering capability of UPF event exposure during UPF discovery | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4381 | 1 | B | KI#1 V-SMF selection enhancement to support HR-SBO | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4383 | 11 | B | Resolve ENs for support of PDU Set handling | 18.2.0 | +| 2023-06 | SP#100 | SP-230479 | 4390 | 2 | A | Clarification on IAB Authorization | 18.2.0 | +| 2023-06 | SP#100 | SP-230496 | 4391 | 3 | B | Update of MBSR Configuration | 18.2.0 | +| 2023-06 | SP#100 | SP-230495 | 4404 | 1 | B | Updates on TSC management information | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4408 | 4 | B | NEF capability for the new AI/ML service | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4410 | 1 | B | KI#1: Other Group Attributes | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4411 | 1 | B | KI#1: QoS for a group | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4413 | 1 | B | KI#5: Reference Correction for Group QoS | 18.2.0 | +| 2023-06 | SP#100 | SP-230486 | 4415 | 1 | F | Corrections and alignments of SFC terminology | 18.2.0 | +| 2023-06 | SP#100 | SP-230452 | 4422 | - | F | Clarification of local switch via UPF on GEO satellites | 18.2.0 | +| 2023-06 | SP#100 | SP-230471 | 4424 | - | F | Clarification on the onboarding indication | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4427 | 3 | F | Clarifications on the UE member selection assistance functionality | 18.2.0 | +| 2023-06 | SP#100 | SP-230469 | 4428 | 1 | B | Add NWDAF services and Reference point between two NWDAFs for roaming case | 18.2.0 | +| 2023-06 | SP#100 | SP-230469 | 4430 | - | B | Update of ADRF services | 18.2.0 | +| 2023-06 | SP#100 | SP-230459 | 4431 | 1 | B | Clarifications the Redundant Steering Mode for GBR SDF | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4442 | 1 | B | Hierarchical NSAC Architecture for EPS counting | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4443 | 3 | B | Network control of the slice usage | 18.2.0 | +| 2023-06 | SP#100 | SP-230495 | 4445 | 1 | B | Support of NAT exposure aligned with TS 23.502 | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4447 | - | D | Support for Edge Computing DNAI mapping update | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4450 | 4 | B | Support QoS management for PIN | 18.2.0 | +| 2023-06 | SP#100 | SP-230459 | 4457 | 1 | B | Determining the ATSSS capabilities of a MA PDU Session when the UE supports MPQUIC | 18.2.0 | +| 2023-06 | SP#100 | SP-230459 | 4459 | 1 | B | Associating a QUIC connection with a QoS flow | 18.2.0 | +| 2023-06 | SP#100 | SP-230470 | 4461 | 1 | A | Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE | 18.2.0 | +| 2023-06 | SP#100 | SP-230476 | 4470 | 1 | B | UE Policy Association handling during EPS to 5GS mobility with N26 | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4473 | 4 | F | 5QI for AI/ML services | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4475 | 1 | B | Remove the EN on supporting TSN TN | 18.2.0 | +| 2023-06 | SP#100 | SP-230490 | 4476 | 1 | F | Clarification related to LADN PDU session. | 18.2.0 | +| 2023-06 | SP#100 | SP-230452 | 4478 | 1 | B | Remove ENs for QoS monitoring on dynamic satellite backhaul | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4486 | 1 | F | PDU Set Importance spanning across QoS Flows | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4487 | 1 | B | Updates on S-NSSAI Location Availability information | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4488 | 3 | B | Storage of S-NSSAI validity time information | 18.2.0 | +| 2023-06 | SP#100 | SP-230495 | 4490 | 3 | F | Update the description of reporting suggestion information | 18.2.0 | +| 2023-06 | SP#100 | SP-230481 | 4491 | 1 | F | MPS when access to 5GC is WLAN corrections | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4492 | 7 | F | PIN communication definition | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4493 | 3 | B | Introduction of a new standard SST for Extended Reality and Media Services | 18.2.0 | +| 2023-06 | SP#100 | SP-230483 | 4499 | 4 | F | CN based MT communication capability | 18.2.0 | +| 2023-06 | SP#100 | SP-230475 | 4500 | 7 | B | Introduction of the Support of Counting of UEs with at least one PDU sessions in the 5GS option 1 | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4503 | 1 | C | Update for network exposure for XR services | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4506 | 1 | B | Update about the Packet Delay Variation description and add PDV in QoS monitoring parameters | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4510 | 1 | F | Resolving the ENs on the Provisioning and monitoring for a group | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4511 | 1 | F | Clarification on the group-MBR | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4514 | 4 | F | Clarification on the TSCTSF handling when it receives the time sync request from AF and time sync subscription from UDM | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4516 | 1 | C | The update of Policy control enhancements to support multi-modal services | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4527 | 8 | B | Update TS23.501 for PDU Set and PDU Handling | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4529 | 4 | B | PCF provides the Periodicity to SMF via PCC rules for resolving the EN for KI#8 | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4530 | - | B | Service Experience filtering criteria in assistance to UE member selection | 18.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| 2023-06 | SP#100 | SP-230484 | 4535 | 1 | F | Editorial change for the PIN | 18.2.0 | +| 2023-06 | SP#100 | SP-230478 | 4541 | 1 | B | Update to Annex O to correct referenced clause number and add an optional condition for setup of the QoS flow | 18.2.0 | +| 2023-06 | SP#100 | SP-230719 | 4553 | 5 | C | Creating an RA when a Slice is Partially Supported in the RA | 18.2.0 | +| 2023-06 | SP#100 | SP-230485 | 4555 | - | B | Support of SL Positioning | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4565 | 1 | F | 23.501 - Member UE terminology update | 18.2.0 | +| 2023-06 | SP#100 | SP-230483 | 4569 | 2 | F | Correction for Asynchronous Type Communication for CN based MT communication handling | 18.2.0 | +| 2023-06 | SP#100 | SP-230476 | 4570 | 2 | B | Handling UE policy association when UE registered over both 3GPP and Non-3GPP access | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4571 | 2 | B | NEF function update | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4572 | 2 | B | PIN traffic routing support | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4573 | 3 | B | PIN general principles | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4580 | - | F | Clarifying the use of TSS information in UMIC | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4581 | 1 | F | Parameters for AF Request Authorization | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4584 | 2 | C | Resolving open issues for Network Slice Area of Service | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4585 | 2 | C | Target NSSAI configuration considering Partial Network Slice support in a Registration Area | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4586 | 2 | C | Number of S-NSSAIs in Partially Allowed NSSAI | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4587 | 2 | F | Clarification on the usage of TSCAI for XRM services | 18.2.0 | +| 2023-06 | SP#100 | SP-230469 | 4589 | 1 | C | Clarification for NWDAF in roaming architecture | 18.2.0 | +| 2023-06 | SP#100 | SP-230469 | 4590 | 2 | C | Clarification of RE-NWDAF discovery | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4591 | 2 | B | NEF capability for the new AIML service | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4592 | 2 | B | Definition of TL Containers | 18.2.0 | +| 2023-06 | SP#100 | SP-230497 | 4604 | 2 | B | QNC Direct Exposure by UPF | 18.2.0 | +| 2023-06 | SP#100 | SP-230498 | 4605 | 2 | B | Exposure of RAN measured data rates | 18.2.0 | +| 2023-06 | SP#100 | SP-230498 | 4611 | 3 | B | PDU Set QoS handling: non-homogenous support (Alternative 2) | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4614 | 1 | C | Resolve ENs on one PIN Served by multiple PDU Sessions | 18.2.0 | +| 2023-06 | SP#100 | SP-230484 | 4621 | 1 | B | Informative annex on PIN traffic routing | 18.2.0 | +| 2023-06 | SP#100 | SP-230457 | 4622 | - | B | Update to UE member selection assistance functionality for application operation | 18.2.0 | +| 2023-06 | SP#100 | SP-230493 | 4636 | 3 | C | Update on Periodicity Range | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4638 | 2 | F | Nnef service update on multiple SMF coordination | 18.2.0 | +| 2023-06 | SP#100 | SP-230473 | 4651 | 1 | B | Support of network slice replacement for handover | 18.2.0 | +| 2023-06 | SP#100 | SP-230451 | 4658 | 2 | B | Completion of Support discontinuous coverage | 18.2.0 | +| 2023-06 | SP#100 | SP-230490 | 4659 | 2 | F | Transfer of emergency PDU session from non-3GPP to 3GPP access | 18.2.0 | +| 2023-06 | SP#100 | SP-230492 | 4666 | 1 | B | 23.501 - Spending Limits for AM and UE Policies in the 5GC | 18.2.0 | +| 2023-06 | SP#100 | SP-230496 | 4669 | 1 | B | Open issue resolutions for MBSR support | 18.2.0 | +| 2023-06 | SP#100 | SP-230496 | 4670 | 3 | B | MBSR registration and authorization support | 18.2.0 | +| 2023-06 | SP#100 | SP-230451 | 4685 | 3 | B | Discontinuous coverage reporting | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4686 | 2 | B | Common EAS/DNAI determination for a set of UEs | 18.2.0 | +| 2023-06 | SP#100 | SP-230461 | 4688 | - | F | SMF determining target AF ID | 18.2.0 | +| 2023-06 | SP#100 | - | - | - | - | MCC correction to table 7.2.8-1 for reference to Nnef_TrafficCorrelation_Notify clause in 23.502 | 18.2.1 | +| 2023-07 | SP#100 | - | 4238 | - | F | MCC correction to add missing bullet and Editor's note in clause 5.30.2.12 | 18.2.2 | +| 2023-09 | SP#101 | SP-230849 | 4582 | 5 | F | NG-RAN resource usage for Alternative S-NSSAI | 18.3.0 | +| 2023-09 | SP#101 | SP-230859 | 4647 | 3 | F | Capability signalling limitation for Reflective QoS | 18.3.0 | +| 2023-09 | SP#101 | SP-230831 | 4695 | 1 | A | Update of subscribed NSSAI when UE is not registered in network | 18.3.0 | +| 2023-09 | SP#101 | SP-230844 | 4696 | 3 | D | Updates to application AI/ML assistance functionality descriptions related to Member UE selection | 18.3.0 | +| 2023-09 | SP#101 | SP-230847 | 4699 | 1 | F | Corrections on NEF(PFDF) support NWDAF-assisted application detection | 18.3.0 | +| 2023-09 | SP#101 | SP-230858 | 4700 | 2 | F | Add support for UPF selection criteria in context of XRM | 18.3.0 | +| 2023-09 | SP#101 | SP-230838 | 4702 | - | A | Replacing obsoleted RFC related to DHCPv6 with RFC 8415 | 18.3.0 | +| 2023-09 | SP#101 | SP-230859 | 4709 | 1 | F | Relaxation of 5QI delay requirements for first packets should also apply for RRC-INACTIVE mode. | 18.3.0 | +| 2023-09 | SP#101 | SP-230849 | 4717 | 4 | F | Resolving open issues related to RAN resources handling in KI#1 | 18.3.0 | +| 2023-09 | SP#101 | SP-230850 | 4719 | 3 | F | Clarification of the discovery and selection of NSACF | 18.3.0 | +| 2023-09 | SP#101 | SP-230836 | 4721 | - | F | Move PMIC and UMIC into Annex | 18.3.0 | +| 2023-09 | SP#101 | SP-230858 | 4723 | 3 | F | PCC support for ECN marking for L4S | 18.3.0 | +| 2023-09 | SP#101 | SP-230856 | 4727 | 2 | F | Clarification on the support for TSCTSF subscribing to AMF notifications for TRS | 18.3.0 | +| 2023-09 | SP#101 | SP-230854 | 4733 | 2 | F | Correction on description about PEGC | 18.3.0 | +| 2023-09 | SP#101 | SP-230849 | 4741 | 2 | F | UP resource deactivation when the UE moves outside the area of slice availability | 18.3.0 | +| 2023-09 | SP#101 | SP-230858 | 4747 | 3 | F | Clarification for GBR and non-GBR support of PDU set QoS Parameters | 18.3.0 | +| 2023-09 | SP#101 | SP-230859 | 4748 | 1 | F | General corrections and alignment for TS23.501 | 18.3.0 | +| 2023-09 | SP#101 | SP-230848 | 4750 | 2 | F | Alt. 1 for the equivalent SNPN used by the UE for Localized Services | 18.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-09 | SP#101 | SP-230854 | 4755 | 3 | F | PIN direct and indirect communication definition correction | 18.3.0 | +| 2023-09 | SP#101 | SP-230854 | 4761 | 2 | F | Make PIN ID unique in PLMN | 18.3.0 | +| 2023-09 | SP#101 | SP-230845 | 4767 | 3 | F | Meaning of availability for 3GPP access | 18.3.0 | +| 2023-09 | SP#101 | SP-230846 | 4769 | 1 | F | Service correction related to traffic correlation | 18.3.0 | +| 2023-09 | SP#101 | SP-230853 | 4770 | 1 | F | Provision of eDRX for RRC_INACTIVE with PTW | 18.3.0 | +| 2023-09 | SP#101 | SP-230857 | 4772 | 2 | F | CAG application for MBSR | 18.3.0 | +| 2023-09 | SP#101 | SP-230854 | 4773 | 3 | F | PIN description correction | 18.3.0 | +| 2023-09 | SP#101 | SP-230833 | 4775 | - | A | Removal of Editor's note for NTN tracking area handling | 18.3.0 | +| 2023-09 | SP#101 | SP-230845 | 4777 | 2 | F | ATSSS_Ph3 Enhanced Considerations of MPQUIC Multi-layer Stack Parameter Settings & Logics | 18.3.0 | +| 2023-09 | SP#101 | SP-230848 | 4784 | 1 | F | Method for exchange info to determine SNPN selection | 18.3.0 | +| 2023-09 | SP#101 | SP-230845 | 4791 | - | F | Clarification on non-3GPP path switching capability when a UE is registered to different PLMNs over 3GPP and non-3GPP accesses | 18.3.0 | +| 2023-09 | SP#101 | SP-230847 | 4798 | 2 | F | Interoperability Indicator for NWDAF discovery and selection | 18.3.0 | +| 2023-09 | SP#101 | SP-230837 | 4817 | 1 | A | PLMN list for NSWO in roaming scenario | 18.3.0 | +| 2023-09 | SP#101 | SP-230846 | 4819 | - | F | clarification on Subscriber category in AF request | 18.3.0 | +| 2023-09 | SP#101 | SP-230859 | 4829 | 3 | F | Update to Network Triggered Service Request for UE in CM_IDLE with Connection Suspend | 18.3.0 | +| 2023-09 | SP#101 | SP-230854 | 4832 | 3 | F | Terminology and specification of functionalities not applicable to PIN. | 18.3.0 | +| 2023-09 | SP#101 | SP-230856 | 4836 | - | F | Adjust AoI | 18.3.0 | +| 2023-09 | SP#101 | SP-230850 | 4839 | 2 | F | Clarifications on NSAC for maximum number of UEs with at least one PDU SessionPDN Connection | 18.3.0 | +| 2023-09 | SP#101 | SP-230858 | 4844 | 3 | F | Corrections on Protocol Description | 18.3.0 | +| 2023-09 | SP#101 | SP-230859 | 4848 | 1 | F | UE Mobility Reference | 18.3.0 | +| 2023-09 | SP#101 | SP-230846 | 4849 | 1 | F | Selection of Common DNAI | 18.3.0 | +| 2023-09 | SP#101 | SP-230835 | 4852 | 1 | A | Clarification on eDRX support for power saving enhancement | 18.3.0 | +| 2023-09 | SP#101 | SP-230841 | 4854 | 4 | F | Clarify on Discontinuous Coverage Support negotiation | 18.3.0 | +| 2023-09 | SP#101 | SP-230845 | 4856 | 1 | F | Editorial correction on ATSSS architecture | 18.3.0 | +| 2023-09 | SP#101 | SP-230849 | 4857 | 4 | F | Downlink packet handling for UE when outside of slice support area | 18.3.0 | +| 2023-09 | SP#101 | SP-230846 | 4858 | - | F | Update on NEF functionality | 18.3.0 | +| 2023-09 | SP#101 | SP-230856 | 4859 | 2 | F | Updates on timing synchronization status reporting | 18.3.0 | +| 2023-09 | SP#101 | SP-230842 | 4861 | 1 | F | QoS monitoring | 18.3.0 | +| 2023-09 | SP#101 | SP-230846 | 4862 | 3 | F | Clarification and editorial on the AF request influence on traffic routing for set of UEs | 18.3.0 | +| 2023-09 | SP#101 | SP-230845 | 4864 | - | F | Clarifications to the Redundant Steering Mode | 18.3.0 | +| 2023-09 | SP#101 | SP-230858 | 4869 | 2 | F | Update on support of PDU Set handling | 18.3.0 | +| 2023-09 | SP#101 | SP-230847 | 4876 | 2 | F | Clarification on NWDAF functionalities and NF profile in TS 23.501 | 18.3.0 | +| 2023-09 | SP#101 | SP-230856 | 4887 | 2 | F | Clarification for time synchronization service monitoring | 18.3.0 | +| 2023-09 | SP#101 | SP-230859 | 4891 | 2 | F | Further clarification on transfer of emergency PDU session from non-3GPP to 3GPP access | 18.3.0 | +| 2023-09 | SP#101 | SP-230838 | 4893 | 2 | A | Aligning secure DNS with SA3 specifications | 18.3.0 | +| 2023-09 | SP#101 | SP-230858 | 4907 | 4 | F | PDU Set QoS handling: Race conditions at mobility from supporting to non-supporting gNB | 18.3.0 | +| 2023-09 | SP#101 | SP-230859 | 4920 | 1 | F | NSAC back-off timer correction | 18.3.0 | +| 2023-12 | SP#102 | SP-231260 | 4350 | 4 | F | Clarification on the list of TAs associated with S-NSSAI partially rejected in the RA | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 4480 | 5 | F | PDU session inactivity timer for MAPDU session | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 4631 | 8 | F | Handling of rejected S-NSSAI from the NSSF by AMF:KI#5 | 18.4.0 | +| 2023-12 | SP#102 | SP-231362 | 4649 | 6 | F | Clean Up of Hierarchical NSAC Architecture | 18.4.0 | +| 2023-12 | SP#102 | SP-231249 | 4689 | 3 | F | Unavailability period EPC interworking aspects | 18.4.0 | +| 2023-12 | SP#102 | SP-231263 | 4724 | 3 | F | Adding 'URSP delivery over EPS' capability in PCF profile in NRF (23.501) | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 4740 | 4 | F | PDU Session management when the UE is outside the area of slice support or availability | 18.4.0 | +| 2023-12 | SP#102 | SP-231234 | 4744 | 7 | B | PDU Set based QoS Handling for uplink transmission | 18.4.0 | +| 2023-12 | SP#102 | SP-231769 | 4749 | 8 | F | Network Slice usage control clarification | 18.4.0 | +| 2023-12 | SP#102 | SP-231269 | 4760 | 4 | F | Enabling PEMC manage PIN via UPF local switch | 18.4.0 | +| 2023-12 | SP#102 | SP-231269 | 4762 | 3 | F | Correction to SMF behaviour for non-3GPP delay budget | 18.4.0 | +| 2023-12 | SP#102 | SP-231267 | 4771 | 4 | B | Support of RRC_INACTIVE with MT-SDT | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 4781 | 4 | F | Handling of EPS interworking due to NS-AoS | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 4783 | 2 | F | Partially Allowed NSSAI and S-NSSAIs used to determine RFSP | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4785 | 2 | D | eNPN_Ph2 general clean up | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4786 | 3 | F | SNPN N3WIF FQDN terminology alignment with stage 3 | 18.4.0 | +| 2023-12 | SP#102 | SP-231258 | 4788 | 3 | F | Add FL capability and ML model training related services | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4803 | 2 | F | Clarification on NAI format in NSWO scenario | 18.4.0 | +| 2023-12 | SP#102 | SP-231277 | 4807 | 3 | F | RT latency control and RT delay exposure for XR data flow | 18.4.0 | +| 2023-12 | SP#102 | SP-231254 | 4813 | 3 | F | Clarifications on redundant steering mode for GBR QoS Flow | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4818 | 1 | F | Clarification on SNPN list for NSWO in CH scenario | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 4850 | 4 | F | Clarification for temporary slices having validity time information | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4865 | 2 | F | Correction to AMF selection for SNPN onboarding | 18.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-12 | SP#102 | SP-231277 | 4871 | 3 | F | Clarifications of policy control enhancements for multi-modal services | 18.4.0 | +| 2023-12 | SP#102 | SP-231238 | 4910 | 2 | A | Add missing gate control information | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 4921 | 1 | F | QoS Monitoring Report clarification | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 4922 | 1 | F | Dual Connectivity terminology fixes and removal of obsolete Editor's Note | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4933 | 2 | D | Clarification on Stand-alone Non-Public Networks | 18.4.0 | +| 2023-12 | SP#102 | SP-231275 | 4935 | 2 | F | Clarification on Data exposure via SBI | 18.4.0 | +| 2023-12 | SP#102 | SP-231275 | 4937 | 3 | F | Update Architecture for UPF SBI interface | 18.4.0 | +| 2023-12 | SP#102 | SP-231275 | 4942 | 4 | F | Clarification on SMF and UPF functional description for UPF event exposure services | 18.4.0 | +| 2023-12 | SP#102 | SP-231277 | 4943 | 1 | F | Correction on network exposure of estimated bandwidth | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4947 | 2 | F | Clarifications for Enabling Access to Localized Services | 18.4.0 | +| 2023-12 | SP#102 | SP-231616 | 4949 | 5 | F | Removing the Editor's Note about the interaction between NAS and AS | 18.4.0 | +| 2023-12 | SP#102 | SP-231276 | 4950 | 1 | F | Providing both ULI and Additional ULI to other NFs | 18.4.0 | +| 2023-12 | SP#102 | SP-231273 | 4955 | 4 | F | Correction on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN) | 18.4.0 | +| 2023-12 | SP#102 | SP-231277 | 4957 | 3 | F | Correcting the Description of the N6 Traffic Parameter Measurement Report | 18.4.0 | +| 2023-12 | SP#102 | SP-231267 | 4960 | 1 | F | NGAP DL Data Notification Message update | 18.4.0 | +| 2023-12 | SP#102 | SP-231269 | 4961 | 3 | F | PIN ID clarification | 18.4.0 | +| 2023-12 | SP#102 | SP-231276 | 4962 | 2 | F | MBSR authorization handling update | 18.4.0 | +| 2023-12 | SP#102 | SP-231265 | 4964 | 2 | F | IAB authorization handling correction | 18.4.0 | +| 2023-12 | SP#102 | SP-231264 | 4965 | 2 | F | Corrections to QoS provisioning for a group | 18.4.0 | +| 2023-12 | SP#102 | SP-231250 | 4969 | 2 | F | Updates of functional description for 5G Satellite Backhaul | 18.4.0 | +| 2023-12 | SP#102 | SP-231264 | 4970 | 1 | F | Updates of functional description for LADN per DNN and S-NSSAI | 18.4.0 | +| 2023-12 | SP#102 | SP-231250 | 4975 | 1 | F | Clarifications to local switching via UPF deployed on satellite | 18.4.0 | +| 2023-12 | SP#102 | SP-231250 | 4976 | 2 | F | Correction to Edge Computing via UPF deployed on satellite | 18.4.0 | +| 2023-12 | SP#102 | SP-231258 | 4980 | 1 | F | Updates for registration and discovery for FL entity | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4981 | 3 | F | Congestion handling when a UE accesses an SNPN for Localized Services | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4987 | 3 | F | Adding architectures on supporting authentication for NSWO using CH with AAA Server via 5GC | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 4988 | - | F | Correction the interface in the NSWO architecture for SNPN | 18.4.0 | +| 2023-12 | SP#102 | SP-231264 | 4989 | 1 | F | LADN (DNN+S-NSSAI) provisioning for individual subscriber and SMF behaviour | 18.4.0 | +| 2023-12 | SP#102 | SP-231264 | 4993 | 2 | F | Change of PDU Session Type correction | 18.4.0 | +| 2023-12 | SP#102 | SP-231275 | 5001 | 3 | F | Corrections to UPF Services | 18.4.0 | +| 2023-12 | SP#102 | SP-231275 | 5002 | 3 | F | UPF Data Collection with QoS Monitoring event | 18.4.0 | +| 2023-12 | SP#102 | SP-231277 | 5012 | 5 | F | Clarification on scenarios for enabling/disabling downlink PDU Set based Handling | 18.4.0 | +| 2023-12 | SP#102 | SP-231255 | 5016 | 1 | F | UPF behaviour alignment for DetNet | 18.4.0 | +| 2023-12 | SP#102 | SP-231273 | 5024 | 7 | F | Clarification on the support for AMF discovery at the TSCTSF | 18.4.0 | +| 2023-12 | SP#102 | SP-231277 | 5026 | 2 | F | Corrections of XRM-specific clauses | 18.4.0 | +| 2023-12 | SP#102 | SP-231264 | 5034 | 2 | F | Provisioning of LADN information | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 5036 | 5 | F | Addressing EN on Downlink packet handling for UE with CM-IDLE mode when outside of slice support area | 18.4.0 | +| 2023-12 | SP#102 | SP-231273 | 5039 | 4 | F | Clarifications of Event ID broadcast in SIB9 | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 5041 | 3 | F | Support of NR coverage enhancements | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 5043 | 2 | F | Relaxation of 5QI delay requirements for first packets should also apply for RRC-INACTIVE mode and for other best effort 5QIs | 18.4.0 | +| 2023-12 | SP#102 | SP-231239 | 5054 | 1 | A | Addressing packet loss and first packet delay for public safety UEs | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 5062 | 1 | F | Move text on providing a back-off timer to the UE during NSAC for maximum number of PDU Sessions | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 5063 | 2 | F | ESNPN during registration for onboarding | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 5064 | 2 | F | Correction on automatic SNPN selection for localized service | 18.4.0 | +| 2023-12 | SP#102 | SP-231259 | 5065 | - | F | Clarification on LADN support in SNPN | 18.4.0 | +| 2023-12 | SP#102 | SP-231276 | 5067 | 1 | F | Clarification on delay in deregistration procedure | 18.4.0 | +| 2023-12 | SP#102 | SP-231263 | 5070 | 3 | F | URSP delivery via EPS | 18.4.0 | +| 2023-12 | SP#102 | SP-231253 | 5073 | 2 | F | Removal of Editor's Note on charging of AI/ML traffic | 18.4.0 | +| 2023-12 | SP#102 | SP-231277 | 5080 | 4 | F | Support of PDU Set handling on a per direction basis | 18.4.0 | +| 2023-12 | SP#102 | SP-231269 | 5083 | 1 | F | AF for PIN description update | 18.4.0 | +| 2023-12 | SP#102 | SP-231269 | 5084 | - | F | Non-3GPP Delay clarification | 18.4.0 | +| 2023-12 | SP#102 | SP-231276 | 5085 | 3 | F | MBSR authorization area restriction | 18.4.0 | +| 2023-12 | SP#102 | SP-231253 | 5087 | - | F | R18 AIMLsys_KI7_23501 CR for clarifying AF filtering criteria | 18.4.0 | +| 2023-12 | SP#102 | SP-231254 | 5091 | 1 | F | Clarification on Suspend and Resume Traffic Duplication | 18.4.0 | +| 2023-12 | SP#102 | SP-231263 | 5096 | - | F | Clarification on URSP delivery in EPS | 18.4.0 | +| 2023-12 | SP#102 | SP-231253 | 5103 | 1 | F | Clarification on the Member UE selection | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 5104 | 1 | F | Spending Limits for AM and UE Policies in the 5GC | 18.4.0 | +| 2023-12 | SP#102 | SP-231258 | 5105 | 2 | F | Correct NWDAF discovery principles | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 5109 | 3 | F | Further clarification of NSAC | 18.4.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------|--------| +| 2023-12 | SP#102 | SP-231263 | 5110 | 2 | F | Providing URSP support indication in EPS in PDN connectivity request | 18.4.0 | +| 2023-12 | SP#102 | SP-231263 | 5111 | 2 | F | Clarification on PCO support | 18.4.0 | +| 2023-12 | SP#102 | SP-231273 | 5115 | 3 | F | Alignment with RAN3 on the network timing synchronization status information | 18.4.0 | +| 2023-12 | SP#102 | SP-231237 | 5121 | 1 | A | Alignment of how Allowed NSSAI can be determined | 18.4.0 | +| 2023-12 | SP#102 | SP-231254 | 5123 | 3 | F | Clarify MRU handling for non-3GPP access path switching | 18.4.0 | +| 2023-12 | SP#102 | SP-231258 | 5125 | 2 | F | Correction for alignment with TS 23.288 regarding ML Model interoperability per Analytics ID | 18.4.0 | +| 2023-12 | SP#102 | SP-231512 | 5126 | 5 | F | Handling of Alternative S-NSSAI | 18.4.0 | +| 2023-12 | SP#102 | SP-231239 | 5128 | 1 | A | Requesting Configured NSSAI from NSSF | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 5137 | 1 | F | Clarification on slice replacement from Alternative S-NSSAI to original S-NSSAI | 18.4.0 | +| 2023-12 | SP#102 | SP-231249 | 5141 | 2 | F | Corrections to Support of Unavailability Period and Overload control | 18.4.0 | +| 2023-12 | SP#102 | SP-231253 | 5142 | 1 | F | Clarification on the Member UE selection assistance functionality for application operation | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 5156 | 4 | F | Clarification on Network Slice Replacement | 18.4.0 | +| 2023-12 | SP#102 | SP-231262 | 5162 | 3 | F | Clarification on eNSAC Option 1 | 18.4.0 | +| 2023-12 | SP#102 | SP-231249 | 5163 | 2 | F | Update on support of discontinuous coverage for satellite access | 18.4.0 | +| 2023-12 | SP#102 | SP-231249 | 5164 | - | F | Discontinuous coverage overload control priority users term alignment | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 5170 | 4 | F | Clarifications about the Alternative S-NSSAI subject to NSSAA | 18.4.0 | +| 2023-12 | SP#102 | SP-231260 | 5172 | 3 | F | Update of definition of NSAC Service area. | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 5185 | 1 | F | UE 5GSM capability indication for supporting secondary auth over EPC | 18.4.0 | +| 2023-12 | SP#102 | SP-231249 | 5187 | - | F | Satellite RAT Types in TS 23.501 | 18.4.0 | +| 2023-12 | SP#102 | SP-231239 | 5195 | 2 | A | Correction to Notification Endpoint | 18.4.0 | +| 2023-12 | SP#102 | SP-231256 | 5203 | 3 | F | KI#1 Alignment and correction on PLMN IDs in AF request | 18.4.0 | +| 2023-12 | SP#102 | SP-231248 | 5207 | 2 | F | Clarifying the ownership of data in UDSF | 18.4.0 | +| 2023-12 | SP#102 | SP-231276 | 5208 | 1 | F | Remove the editor's note for MBSR authorization indication | 18.4.0 | +| 2023-12 | SP#102 | SP-231767 | 4736 | 9 | F | Update for QoS monitoring and network exposure | 18.4.0 | +| 2023-12 | SP#102 | SP-231763 | 5008 | 7 | F | Correction and clarification of the Protocol Description definition | 18.4.0 | +| 2023-12 | SP#102 | SP-231765 | 5014 | 6 | F | Clarification on QoS flow mapping and service data flow | 18.4.0 | +| 2023-12 | SP#102 | SP-231766 | 5175 | 6 | F | Clarification of the Unmarked PDUs with SN Offset and PSI Value | 18.4.0 | +| 2023-12 | SP#102 | SP-231762 | 5186 | 3 | F | Incorrect reference in clause 5.15.17 for procedure for RAN initiated PDU session release | 18.4.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23540/raw.md b/raw/rel-18/23_series/23540/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f9374bf2356c5f6b4892f1a5bb9f0110d25535a7 --- /dev/null +++ b/raw/rel-18/23_series/23540/raw.md @@ -0,0 +1,1751 @@ + + +# 3GPP TS 23.540 V18.2.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System: Technical realization of Service Based Short Message Service; Stage 2 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis + +Valbonne - FRANCE + +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members + +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners + +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms and abbreviations ..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Architecture to support SBI-based SMS..... | 8 | +| 4.1 Architecture to support SBI-based SMS..... | 8 | +| 4.2 Reference point to support SBI-based SMS..... | 10 | +| 4.3 Service based interface to support SBI-based SMS..... | 10 | +| 5 Procedures for SBI-based SMS..... | 11 | +| 5.1 Procedure for SBI-based MT SMS ..... | 11 | +| 5.1.1 General ..... | 11 | +| 5.1.2 Successful Mobile Terminated short message transfer without SMS Router/ IP-SM-GW ..... | 12 | +| 5.1.3 Successful Mobile Terminated short message transfer via SMS Router ..... | 14 | +| 5.1.4 Successful Mobile Terminated short message transfer via IP-SM-GW..... | 16 | +| 5.1.5 Unsuccessful Mobile Terminated short message transfer without SMS Router/IP-SM-GW ..... | 18 | +| 5.1.6 Unsuccessful Mobile Terminated short message transfer via IP-SM-GW ..... | 20 | +| 5.1.7 GPSI-to-Subscription-Network resolution procedure ..... | 21 | +| 5.1.7.1 General..... | 21 | +| 5.1.7.2 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC ..... | 22 | +| 5.1.7.2.1 General ..... | 22 | +| 5.1.7.2.2 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Direct routing | 23 | +| 5.1.7.2.3 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Indirect routing | 24 | +| 5.1.7.3 SCP supports GPSI-to-Subscription-Network resolution procedure..... | 25 | +| 5.1.7.3.1 General ..... | 25 | +| 5.1.7.3.2 SCP supports GPSI-to-Subscription-Network resolution with MNPF ..... | 26 | +| 5.1.7.3.3 SCP supports GPSI-to-Subscription-Network resolution with NRF ..... | 27 | +| 5.1.7.3.4 SCP supports GPSI-to-Subscription-Network resolution with MNPF for Direct routing | 28 | +| 5.1.7.3.5 SCP supports GPSI-to-Subscription-Network resolution with MNPF for Indirect routing | 29 | +| 5.1.7.4 GPSI-to-Subscription-Network resolution using NRF ..... | 31 | +| 5.1.8 Alert..... | 33 | +| 5.1.9 Unsuccessful Mobile Terminated short message transfer via SMS Router ..... | 34 | +| 5.2 Procedure for SBI-based MO SMS..... | 36 | +| 5.2.1 General ..... | 36 | +| 5.2.2 Procedure for Successful Mobile Originated short message transfer..... | 36 | +| 5.2.3 Unsuccessful Mobile Originated short message transfer ..... | 37 | +| 5.2.4 MSISDN-less MO SMS message transfer ..... | 38 | +| 6 Services for SBI-based SMS..... | 39 | +| 6.1 General ..... | 39 | +| 6.2 UDM services for SBI-based SMS ..... | 39 | +| 6.2.1 General ..... | 39 | +| 6.2.2 Nudm_ReportSMDeliveryStatus service ..... | 39 | +| 6.2.2.1 General..... | 39 | +| 6.2.2.2 Nudm_ReportSMDeliveryStatus_Request service operation..... | 39 | +| 6.2.3 Nudm_EventExposure service ..... | 39 | + +| | | | +|-------------------------------|-------------------------------------------------------|-----------| +| 6.2.4 | Nudm_UECM service ..... | 39 | +| 6.3 | SMS-IWMSC services for SBI-based SMS..... | 40 | +| 6.3.1 | General ..... | 40 | +| 6.3.2 | Niwmsc_SMService service..... | 40 | +| 6.3.2.1 | General..... | 40 | +| 6.3.2.2 | Niwmsc_SMService_MoForwardSm service operation ..... | 40 | +| 6.4 | SMSF services for SBI-based SMS ..... | 40 | +| 6.4.1 | General ..... | 40 | +| 6.4.2 | Nsmmf_SMService service..... | 40 | +| 6.4.2.1 | General..... | 40 | +| 6.4.2.2 | Nsmmf_SMService_MtForwardSm service operation ..... | 41 | +| 6.5 | IP-SM-GW services for SBI-based SMS..... | 41 | +| 6.5.1 | General ..... | 41 | +| 6.5.2 | Nipsmgw_SMService service ..... | 41 | +| 6.5.2.1 | General..... | 41 | +| 6.5.2.2 | Nipsmgw_SMService_RoutingInfo service operation ..... | 41 | +| 6.5.2.3 | Nipsmgw_SMService_MtForwardSm service operation ..... | 41 | +| 6.6 | SMS Router services for SBI-based SMS..... | 42 | +| 6.6.1 | General ..... | 42 | +| 6.6.2 | Nrouter_SMService service..... | 42 | +| 6.6.2.1 | General..... | 42 | +| 6.6.2.2 | Nrouter_SMService_RoutingInfo service operation ..... | 42 | +| 6.6.2.3 | Nrouter_SMService_MtForwardSm service operation ..... | 42 | +| 6.7 | MNPF services for SBI-based SMS..... | 42 | +| 6.7.1 | General ..... | 42 | +| 6.7.2 | Nmnpf_NPStatus service..... | 43 | +| 6.7.2.1 | General..... | 43 | +| 6.7.2.2 | Nmnpf_NPStatus_Get service operation ..... | 43 | +| 6.8 | NEF services for SBI-based SMS ..... | 43 | +| 6.8.1 | General ..... | 43 | +| 6.8.2 | Nnef_SMService service..... | 43 | +| 6.8.2.1 | General..... | 43 | +| 6.8.2.2 | Nnef_SMService_MoForwardSm service operation..... | 43 | +| Annex A (informative): | Change history..... | 44 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document defines the Stage 2 architecture, procedures and services to support service based short message service (SMS) in 5G system (5GS). + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [3] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2". +- [4] 3GPP TS 23.502: "Procedures for the 5G System (5GS); Stage 2". +- [5] 3GPP TS 23.632: "User data interworking, coexistence and migration; Stage 2". +- [6] 3GPP TS 29.540: "5G System; SMS Services; Stage 3". +- [7] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3". +- [8] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". +- [9] 3GPP TS 29.573: "5G System; Public Land Mobile Network (PLMN) Interconnection; Stage 3". +- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". +- [11] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [12] IETF RFC 6116: "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM) ". +- [13] IETF RFC 4002: "IANA Registration for Enumservice 'web' and 'ft'". +- [14] IETF RFC 6118: "Update of Legacy IANA Registrations of Enumservices". +- [15] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2". + +# 3 Definitions of terms and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**alert-SC:** service element provided by a GSM/UMTS/EPS/5GS PLMN to inform an SC which has previously initiated unsuccessful short message delivery attempt(s) to a specific MS/UE, that the MS/UE is now recognized by the PLMN to have recovered operation. + +**Gateway MSC For Short Message Service (SMS-GMSC):** function of an MSC capable of receiving a short message from an SC, interrogating an HLR/HSS/UDM for routing information and SMS info, and delivering the short message to the VMSC/SGSN/MME/SMSF of the recipient MS/UE. + +**Interworking MSC For Short Message Service (SMS-IWMSC):** function of an MSC capable of receiving a short message from within the PLMN and submitting it to the recipient SC. + +**IP-Short-Message-Gateway (IP-SM-GW):** function responsible for protocol interworking between the IP-based UE and the SC. + +**Service Centre (SC):** function responsible for the relaying and store and forwarding of a short message between an SME and an MS/UE. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|---------|-----------------------------------------| +| GPSI | Generic Public Subscription Identifier | +| MNPF | Mobile Number Portability Function | +| MO SMS | Mobile Originated Short Message Service | +| MT SMS | Mobile Terminated Short Message Service | +| NAS | Non-Access-Stratum | +| NP | Number Portability | +| NRF | Network Repository Function | +| SBA | Service Based Architecture | +| SBI | Service Based Interface | +| SCP | Service Communication Proxy | +| SMS | Short Message Service | +| SM MO | Short Message Mobile Originated | +| SM MT | Short Message Mobile Terminated | +| SMSF | Short Message Service Function | +| SMSoNAS | SMS over NAS | +| UDM | Unified Data Management | + +# 4 Architecture to support SBI-based SMS + +## 4.1 Architecture to support SBI-based SMS + +Figure 4.1-1 shows the non-roaming architecture to support SBI-based SMS. + +![Figure 4.1-1: Non-roaming architecture to support SBI-based SMS. The diagram shows a Service Based Interface (SBI) with various Network Functions (NFs) connected to it. The NFs are SMS-IWMSC, SMS-GMSC, NRF, SMSF, IP-SM-GW, SMS Router, UDM, MNPF, and NEF. Below the SBI, the UE is connected to the AMF via an N1 interface. The AMF is connected to the SBI via a Namf interface.](740442c999390734911677f01af0316d_img.jpg) + +The diagram illustrates the non-roaming architecture for SBI-based SMS. At the top, a horizontal line represents the Service Based Interface (SBI). Above this line, nine boxes represent Network Functions (NFs): SMS-IWMSC, SMS-GMSC, NRF, SMSF, IP-SM-GW, SMS Router, UDM, MNPF, and NEF. Below the SBI line, corresponding reference points are labeled: Niwmsc, Ngmsc, Nnrf, Nsmmf, Nipsmgw, Nrouter, Nudm, Nmnpf, and Nnef. At the bottom, a box labeled 'UE' is connected to a box labeled 'AMF' via a line labeled 'N1'. The 'AMF' box is connected to the SBI line via a vertical line labeled 'Namf'. + +Figure 4.1-1: Non-roaming architecture to support SBI-based SMS. The diagram shows a Service Based Interface (SBI) with various Network Functions (NFs) connected to it. The NFs are SMS-IWMSC, SMS-GMSC, NRF, SMSF, IP-SM-GW, SMS Router, UDM, MNPF, and NEF. Below the SBI, the UE is connected to the AMF via an N1 interface. The AMF is connected to the SBI via a Namf interface. + +**Figure 4.1-2d: Architecture for NP Status Retrieval from MNPF in reference point representation** + +Figure 4.1-2a, Figure 4.1-2b, Figure 4.1-2c and Figure 4.1-2d depict the non-roaming architecture to support SBI-based SMS, using the reference point representation showing how various network functions interact with each other + +![Diagram of SM MT through SMS-GMSC. The flow is: SMS-SC -> SMS-GMSC (via SM1 to UDM) -> SM5 -> SMSF -> N20 -> AMF -> N1 -> UE.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +graph LR + SMS-SC[SMS-SC] --- SMS-GMSC[SMS-GMSC] + SMS-GMSC -- SM1 --> UDM[UDM] + SMS-GMSC -- SM5 --> SMSF[SMSF] + SMSF -- N20 --> AMF[AMF] + AMF -- N1 --> UE[UE] + +``` + +Diagram of SM MT through SMS-GMSC. The flow is: SMS-SC -> SMS-GMSC (via SM1 to UDM) -> SM5 -> SMSF -> N20 -> AMF -> N1 -> UE. + +SM MT through SMS-GMSC + +![Diagram of SM MT through SMS-GMSC and SMS Router. The flow is: SMS-SC -> SMS-GMSC (via SM1 to UDM) -> SM6 -> SMS Router -> SM7 -> SMSF -> N20 -> AMF -> N1 -> UE. The UDM is also connected to the SMS Router via SM4.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +``` + +graph LR + SMS-SC[SMS-SC] --- SMS-GMSC[SMS-GMSC] + SMS-GMSC -- SM1 --> UDM[UDM] + SMS-GMSC -- SM6 --> SMSRouter[SMS Router] + UDM -- SM4 --> SMSRouter + SMSRouter -- SM7 --> SMSF[SMSF] + SMSF -- N20 --> AMF[AMF] + AMF -- N1 --> UE[UE] + +``` + +Diagram of SM MT through SMS-GMSC and SMS Router. The flow is: SMS-SC -> SMS-GMSC (via SM1 to UDM) -> SM6 -> SMS Router -> SM7 -> SMSF -> N20 -> AMF -> N1 -> UE. The UDM is also connected to the SMS Router via SM4. + +SM MT through SMS-GMSC and SMS Router + +![Diagram of SM MT through SMS-GMSC and IP-SM-GW. The flow is: SMS-SC -> SMS-GMSC (via SM1 to UDM) -> SM8 -> IP-SM-GW -> SM9 -> SMSF -> N20 -> AMF -> N1 -> UE. The UDM is also connected to the IP-SM-GW via SM3.](0b87abe67b21a93777287649c33e755d_img.jpg) + +``` + +graph LR + SMS-SC[SMS-SC] --- SMS-GMSC[SMS-GMSC] + SMS-GMSC -- SM1 --> UDM[UDM] + SMS-GMSC -- SM8 --> IPSMGW[IP-SM-GW] + UDM -- SM3 --> IPSMGW + IPSMGW -- SM9 --> SMSF[SMSF] + SMSF -- N20 --> AMF[AMF] + AMF -- N1 --> UE[UE] + +``` + +Diagram of SM MT through SMS-GMSC and IP-SM-GW. The flow is: SMS-SC -> SMS-GMSC (via SM1 to UDM) -> SM8 -> IP-SM-GW -> SM9 -> SMSF -> N20 -> AMF -> N1 -> UE. The UDM is also connected to the IP-SM-GW via SM3. + +SM MT through SMS-GMSC and IP-SM-GW + +![Diagram of IM Interworking to SM MT through IP-SM-GW. The flow is: IM/CPM AS or S-CSCF -> ICS -> IP-SM-GW -> SM9 -> SMSF -> N20 -> AMF -> N1 -> UE. The IP-SM-GW is also connected to the UDM via SM3.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +``` + +graph LR + IMCPMAS[IM/CPM AS or S-CSCF] --- ICS[ICS] + ICS --> IPSMGW[IP-SM-GW] + IPSMGW -- SM3 --> UDM[UDM] + IPSMGW -- SM9 --> SMSF[SMSF] + SMSF -- N20 --> AMF[AMF] + AMF -- N1 --> UE[UE] + +``` + +Diagram of IM Interworking to SM MT through IP-SM-GW. The flow is: IM/CPM AS or S-CSCF -> ICS -> IP-SM-GW -> SM9 -> SMSF -> N20 -> AMF -> N1 -> UE. The IP-SM-GW is also connected to the UDM via SM3. + +IM Interworking to SM MT through IP-SM-GW + +Figure 4.1-2a: Non-roaming System Architecture for SBI-based MT SMS in reference point representation + +![Diagram of SBI-based MO SMS. The flow is: SMS-SC -> SMS-IWMSC -> SM10 -> SMSF -> N20 -> AMF -> N1 -> UE. The SMS-IWMSC is connected to the UDM via SM2. The UDM is connected to the SMSF via N21 and to the AMF via N8.](2ba086df3506f81bae3a9b53725dcfea_img.jpg) + +``` + +graph LR + SMS-SC[SMS-SC] --- SMSIWMSC[SMS-IWMSC] + SMS-IWMSC -- SM2 --> UDM[UDM] + SMS-IWMSC -- SM10 --> SMSF[SMSF] + UDM -- N21 --> SMSF + UDM -- N8 --> AMF[AMF] + AMF -- N1 --> UE[UE] + +``` + +Diagram of SBI-based MO SMS. The flow is: SMS-SC -> SMS-IWMSC -> SM10 -> SMSF -> N20 -> AMF -> N1 -> UE. The SMS-IWMSC is connected to the UDM via SM2. The UDM is connected to the SMSF via N21 and to the AMF via N8. + +Figure 4.1-2b: Non-roaming System Architecture for SBI-based MO SMS in reference point representation + +![Figure 4.1-2c: Architecture for SBI-based MSISDN-less MO SMS in reference point representation. The diagram shows a UDM at the top connected to an NEF via the N52 interface. The NEF is connected to an SMS-SC via the SM11 interface (highlighted in red) and to an AF via the N33 interface.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +graph TD + UDM[UDM] -- N52 --> NEF[NEF] + NEF -- SM11 --> SMS-SC[SMS-SC] + NEF -- N33 --> AF[AF] + +``` + +Figure 4.1-2c: Architecture for SBI-based MSISDN-less MO SMS in reference point representation. The diagram shows a UDM at the top connected to an NEF via the N52 interface. The NEF is connected to an SMS-SC via the SM11 interface (highlighted in red) and to an AF via the N33 interface. + +Figure 4.1-2c: Architecture for SBI-based MSISDN-less MO SMS in reference point representation + +![Figure 4.1-2d: Architecture for NP state Retrieval from MNPF in reference point representation. The diagram shows an NRF at the top connected to an SCP below it. The SCP is connected to an SMS-GMSC on the left and an MNPF on the right via the SM13 interface (highlighted in red). The SMS-GMSC is connected to the MNPF via the SM12 interface (highlighted in red). The NRF is also connected to the MNPF via the SM14 interface (highlighted in red).](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +``` + +graph TD + NRF[NRF] -- SM14 --> MNPF[MNPF] + NRF --> SCP[SCP] + SCP -- SM13 --> MNPF + SMS-GMSC[SMS-GMSC] -- SM12 --> MNPF + SMS-GMSC --> SCP + +``` + +Figure 4.1-2d: Architecture for NP state Retrieval from MNPF in reference point representation. The diagram shows an NRF at the top connected to an SCP below it. The SCP is connected to an SMS-GMSC on the left and an MNPF on the right via the SM13 interface (highlighted in red). The SMS-GMSC is connected to the MNPF via the SM12 interface (highlighted in red). The NRF is also connected to the MNPF via the SM14 interface (highlighted in red). + +Figure 4.1-2d: Architecture for NP state Retrieval from MNPF in reference point representation + +NOTE 1: The newly introduced reference points for SMS\_SBI are marked in red, and numbered from SM1 to SM14. + +## 4.2 Reference point to support SBI-based SMS + +Besides the reference point to support SMS over NAS described in clause 4.4.2.2 of TS 23.501 [3], the following reference points are needed to support SBI-based SMS: + +- Reference point SM1: Reference point for routing information between SMS-GMSC and UDM. +- Reference point SM2: Reference point between SMS-IWMSC and UDM. +- Reference point SM3: Reference point for routing information between IP-SM-GW and UDM. +- Reference point SM4: Reference point for routing information between SMS Router and UDM. +- Reference point SM5: Reference point for SMS message transfer between SMS-GMSC and SMSF. +- Reference point SM6: Reference point for SMS message transfer between SMS-GMSC and SMS Router. +- Reference point SM7: Reference point for SMS message transfer between SMSF and SMS Router. +- Reference point SM8: Reference point for SMS message transfer between SMS-GMSC and IP-SM-GW. +- Reference point SM9: Reference point for SMS message transfer between SMSF and IP-SM-GW +- Reference point SM10: Reference point for SMS message transfer between SMS-IWMSC and SMSF. +- Reference point SM11: Reference point for SMS message transfer between SMS-SC and NEF. +- Reference point SM12: Reference point for SMS message transfer between SMS-GMSC and MNPF. +- Reference point SM13: Reference point for SMS message transfer between SCP and MNPF. +- Reference point SM14: Reference point for SMS message transfer between NRF and MNPF. + +## 4.3 Service based interface to support SBI-based SMS + +Besides the service based interfaces to support SMS over NAS described in clause 4.4.2.3 of TS 23.501 [3], the following service based interfaces are needed to support SBI-based SMS. + +**Nudm:** Service-based interface exhibited by UDM + +**Nnrf:** Service-based interface exhibited by NRF + +**Ngmsc:** Service-based interface exhibited by SMS-GMSC + +**Niwmsc:** Service-based interface exhibited by SMS-IWMSC + +**Nipsmgw:** Service-based interface exhibited by IP-SM-GW + +**Nrouter:** Service-based interface exhibited by SMS Router + +**Nnef:** Service-based interface exhibited by NEF + +**Nmnpf:** Service-based interface exhibited by MNPF + +# --- 5 Procedures for SBI-based SMS + +## 5.1 Procedure for SBI-based MT SMS + +### 5.1.1 General + +The procedure is used to support the Mobile Terminated short message transfer for SBI-based interfaces as defined in clause 4.1, which is based on Short message mobile terminated procedure defined in clause 10.1 of 3GPP TS 23.040 [2] and clauses 4.13.3.6, 4.13.3.7 and 4.13.3.8 of 3GPP TS 23.502 [4]. + +This new services introduced in this procedure can be registered in NRF, and discovered by NF service consumers. + +SMSF/SMS Router/IP-SM-GW should indicate whether it supports SMS\_SBI or not. For the case of SMSF/IP-SM-GW, "SBI support indication" should be brought when SMSF/IP-SM-GW registers in UDM. For the case of SMS Router, "SBI support indication" should be configured locally in UDM, together with the SMS Router address. UDM stores the "SBI support indication" indication and provides it to the SMS-GMSC during Routing Info retrieval. SMS-GMSC selects legacy or SBI based protocol based on the indication received during Routing Info retrieval. + +### 5.1.2 Successful Mobile Terminated short message transfer without SMS Router/ IP-SM-GW + +![Sequence diagram for MT SMS over NAS without SMS Router/ IP-SM-GW. Lifelines: SMSF, NRF, UDM, SMS-GMSC, SC. The sequence starts with a Message Transfer from SC to SMS-GMSC. SMS-GMSC then sends an Nnrf_NFDiscovery_Request to NRF. NRF responds with Nnrf_NFDiscovery_Request Response. SMS-GMSC then sends a Nudm_UECM_SendRoutingInfoForSM to UDM. UDM responds with Nudm_UECM_SendRoutingInfoForSM Response. SMS-GMSC then sends an Nsmmf_SMService_MtForwardSm (SMS body) to SMSF. A callout box indicates steps 4a-6b from 3GPP TS 23.502 [4]. SMSF then sends an Nsmmf_SMService_MtForwardSm Response (Delivery Report) to SMS-GMSC. SMS-GMSC then sends a Nudm_SMReportStatus_Request to UDM. UDM responds with Nudm_SMReportStatus_Request Response. SMS-GMSC then sends a Delivery Report to SC. A callout box indicates steps 6c-6d from 3GPP TS 23.502 [4].](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant NRF + participant UDM + participant SMSF + + Note right of SC: 1. Message Transfer + SC->>SMS-GMSC: 1. Message Transfer + Note right of SMS-GMSC: 2a. Nnrf_NFDiscovery_Request + SMS-GMSC->>NRF: 2a. Nnrf_NFDiscovery_Request + Note right of NRF: 2b. Nnrf_NFDiscovery_Request Response + NRF->>SMS-GMSC: 2b. Nnrf_NFDiscovery_Request Response + Note right of SMS-GMSC: 3. Nudm_UECM_SendRoutingInfoForSM + SMS-GMSC->>UDM: 3. Nudm_UECM_SendRoutingInfoForSM + Note right of UDM: 4. Nudm_UECM_SendRoutingInfoForSM Response + UDM->>SMS-GMSC: 4. Nudm_UECM_SendRoutingInfoForSM Response + Note right of SMS-GMSC: 5. Nsmmf_SMService_MtForwardSm (SMS body) + SMS-GMSC->>SMSF: 5. Nsmmf_SMService_MtForwardSm (SMS body) + Note left of SMSF: 6. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + Note right of SMSF: 7. Nsmmf_SMService_MtForwardSm Response (Delivery Report) + SMSF->>SMS-GMSC: 7. Nsmmf_SMService_MtForwardSm Response (Delivery Report) + Note right of SMS-GMSC: 8. Nudm_SMReportStatus_Request + SMS-GMSC->>UDM: 8. Nudm_SMReportStatus_Request + Note right of UDM: 9. Nudm_SMReportStatus_Request Response + UDM->>SMS-GMSC: 9. Nudm_SMReportStatus_Request Response + Note right of SMS-GMSC: 10. Delivery Report + SMS-GMSC->>SC: 10. Delivery Report + Note left of SMSF: 11. step 6c -6d of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + +``` + +Sequence diagram for MT SMS over NAS without SMS Router/ IP-SM-GW. Lifelines: SMSF, NRF, UDM, SMS-GMSC, SC. The sequence starts with a Message Transfer from SC to SMS-GMSC. SMS-GMSC then sends an Nnrf\_NFDiscovery\_Request to NRF. NRF responds with Nnrf\_NFDiscovery\_Request Response. SMS-GMSC then sends a Nudm\_UECM\_SendRoutingInfoForSM to UDM. UDM responds with Nudm\_UECM\_SendRoutingInfoForSM Response. SMS-GMSC then sends an Nsmmf\_SMService\_MtForwardSm (SMS body) to SMSF. A callout box indicates steps 4a-6b from 3GPP TS 23.502 [4]. SMSF then sends an Nsmmf\_SMService\_MtForwardSm Response (Delivery Report) to SMS-GMSC. SMS-GMSC then sends a Nudm\_SMReportStatus\_Request to UDM. UDM responds with Nudm\_SMReportStatus\_Request Response. SMS-GMSC then sends a Delivery Report to SC. A callout box indicates steps 6c-6d from 3GPP TS 23.502 [4]. + +**Figure 5.1.2-1: MT SMS over NAS without SMS Router/ IP-SM-GW** + +1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. +- 2a. SMS-GMSC invokes the Nnrf\_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscriptions of the GPSI. The SMS-GMSC may need to retrieve the PLMN ID of the recipients GPSI before the discovery of the UDM instance based on the GPSI-to-Subscription-Network resolution procedure defined in clause 5.1.7. +- 2b. If no UDM supporting SMS SBI could be discovered, the NRF indicates so to SMS-GMSC (by not including any UDM instance in the discovery response), and SMS-GMSC shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2], +or if a UDM supporting SMS SBI is discovered and selected, NRF returns the IP addresses or FQDNs of the serving UDM to provide Nudm\_UECM\_SendRoutingInfoForSM service to SMS-GMSC. +3. SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the routing information of the nodes available for MT SMS delivery, in this case the registered serving SMSF instances for all access types for the UE. + +4. The UDM shall check the registration/reachability flags to determine the potential target nodes and responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response, in this procedure the SMSF instance Id and the indication for SMSF SMS\_SBI support are included in the response message. The UDM shall include the SMSF for 3GPP access and the SMSF for non-3GPP access separately, if both the SMSFs are currently known to be valid for the UE. +5. The SMS-GMSC forwards the SMS message to the SMSF. If the SMS-GMSC has more than one SMSF address to use for SMS transport towards the UE, then the SMS-GMSC chooses which SMSF address to use first, based on operator local policy. + +The SMS-GMSC selects protocol based on the indication for SMSF SMS\_SBI support. + +If SMSF indicates it supports SMS\_SBI, SMS-GMSC forwards the SMS message to the SMSF by invoking Nsmmf\_SMService\_MtForwardSm service operation. + +If SMSF indicates that it does not support SMS\_SBI, SMS-GMSC should forward SMS message to SMSF by legacy MAP/Diameter protocol. And the following steps follow the procedures for legacy MT SMS message transfer, as illustrated in Figure 15a of TS23.040 [2]. + +6. MT SMS over NAS procedure between SMSF, AMF and UE is same as the definition in step 4a to 6b of Figure 4.13.3.6-1 of 3GPP TS 23.502 [4]. +7. The SMSF delivers the delivery report to SMS-GMSC by sending the Nsmmf\_SMService\_MtForwardSm response to the SMS-GMSC. +8. The SMS-GMSC updates the SM-Delivery Report Status to UDM by invoking Nudm\_SMReportStatus\_Request. +9. UDM responses Nudm\_SMReportStatus\_Request response to SMS-GMSC. +10. The SMS-GMSC delivers the delivery report to SC as defined in TS 23.040 [2]. +11. MT SMS over NAS procedure between SMSF, AMF and UE is same as the definition in step 6c to 6d of Figure 4.13.3.6-1 of 3GPP TS 23.502 [4]. + +### 5.1.3 Successful Mobile Terminated short message transfer via SMS Router + +![Sequence diagram for MT SMS over NAS via SMS Router. Lifelines: SMSF, NRF, SMS Router, UDM, SMS-GMSC, SC. The sequence shows the flow of a short message from the SC through the SMS-GMSC, SMS Router, and finally to the SMSF, with various discovery and routing steps in between.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant UDM + participant NRF + participant SMS Router + participant SMSF + + Note left of SMSF: 9. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + + SC->>SMS-GMSC: 1. Message Transfer + SMS-GMSC->>NRF: 2a. Nnrf_NFDiscovery_Request + NRF-->>SMS-GMSC: 2b. Nnrf_NFDiscovery_Response + SMS-GMSC->>UDM: 3. Nudm_UECM_SendRoutingInfoForSM + UDM->>SMS Router: 4. Nrouter_SMService_RoutingInfo + SMS Router->>UDM: 5. Nrouter_SMService_RoutingInfo Response + UDM-->>SMS-GMSC: 6. Nudm_UECM_SendRoutingInfoForSM Response + SMS-GMSC->>SMS Router: 7. Nrouter_SMService_MtForwardSm (SMS body) + SMS Router->>SMSF: 8. Nsmmf_SMService_MtForwardSm (SMS body) + Note right of SMSF: 15. step 6c -6d of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + SMSF->>SMS Router: 10. Nsmmf_SMService_MtForwardSm Response (Delivery Report) + SMS Router->>SMS-GMSC: 11. Nrouter_SMService_MtForwardSm (Delivery Rpt) + SMS-GMSC-->>UDM: 12. Nudm_ReportSMDeliveryStatus_Request + UDM-->>SMS-GMSC: 13. Nudm_ReportSMDeliveryStatus_Request Response + SMS-GMSC->>SC: 14. Delivery Report + +``` + +Sequence diagram for MT SMS over NAS via SMS Router. Lifelines: SMSF, NRF, SMS Router, UDM, SMS-GMSC, SC. The sequence shows the flow of a short message from the SC through the SMS-GMSC, SMS Router, and finally to the SMSF, with various discovery and routing steps in between. + +Figure 5.1.3-1: MT SMS over NAS via SMS Router + +1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. +- 2a. SMS-GMSC invokes the Nnrf\_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscriptions of the GPSI. The SMS-GMSC may need to retrieve the PLMN ID of the recipients GPSI before the discovery of the UDM instance based on the GPSI-to-Subscription-Network resolution procedure defined in clause 5.1.7. +- 2b. If no UDM supporting SMS SBI could be discovered, the NRF indicates so to SMS-GMSC (by not including any UDM instance in the discovery response), and SMS-GMSC shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2], +or if a UDM supporting SMS SBI is discovered and selected, NRF returns the IP addresses or FQDNs of the serving UDM to provide Nudm\_UECM\_SendRoutingInfoForSM service to SMS-GMSC. +3. SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the serving node information for all access types for the UE. + +4. The UDM shall check the registration/reachability flags to determine the potential target nodes, e.g. SMSF. For MT SM transfer via SMS Router, the UDM shall invoke the Nrouter\_SMService\_RoutingInfo to provide the SMSF Instance Id to the SMS Router. The address of the SMS Router to be contacted by the UDM may be configured locally. +5. The SMS Router shall send Nrouter\_SMService\_RoutingInfo response to the UDM. +6. UDM responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response, including SMS Router address, the indication for SMSF SMS\_SBI support and the indication for SMS Router SMS\_SBI support. +- 7-8. The SMS-GMSC forwards the SMS message to the SMS Router, and then SMS Router forwards the SMS message to the SMSF. If the SMS Router has more than one SMSF address to use for SMS transport towards the UE, then the SMS Router chooses which SMSF address to use first, based on operator local policy. + +The SMS-GMSC selects protocol based on the indications for SMSF SMS\_SBI support and SMS Router SMS\_SBI support. + +If both SMSF and SMS Router indicate support for SMS\_SBI, SMS-GMSC forwards the SMS message to the SMS Router by invoking Nrouter\_SMService\_MtForwardSm service operation. And then the SMS Router forwards the SMS message to the SMSF by invoking Nsmmf\_SMService\_MtForwardSm service operation. + +If SMSF or SMS Router indicates that it does not support SMS\_SBI, SMS-GMSC should forward SMS message to SMS Router by legacy MAP/Diameter protocol. Then SMS Router forwards the SMS message to the SMSF by legacy MAP/Diameter protocol. The following steps follow the procedures for legacy MT SMS message transfer, as illustrated in Figure 15aa of TS23.040. + +9. MT SMS over NAS procedure between SMSF, AMF and UE is same as the definition in step 4a to 6b of Figure 4.13.3.6-1 in 3GPP TS 23.502 [4]. +10. The SMSF delivers the delivery report to SMS Router by sending the Nsmmf\_SMService\_MtForwardSm response to the SMS Router. +11. The SMS Router delivers the delivery report to SMS-GMSC by sending the Nrouter\_SMService\_MtForwardSm response to the SMS-GMSC. +- 12-13. The SMS-GMSC may report the SM-Delivery Status to the UDM by invoking Nudm\_ReportSMDeliveryStatus\_Request and UDM responses Nudm\_ReportSMDeliveryStatus\_Request response to SMS-GMSC. +14. The SMS-GMSC delivers the delivery report to SC as defined in 3GPP TS 23.040 [2]. +15. MT SMS over NAS procedure between SMSF, AMF and UE is same as the definition in step 6c to 6d of Figure 4.13.3.6-1 in 3GPP TS 23.502 [4]. + +### 5.1.4 Successful Mobile Terminated short message transfer via IP-SM-GW + +![Sequence diagram for MT SMS over NAS via IP-SM-GW. Lifelines: SMSF, NRF, IP-SM-GW, UDM, SMS-GMSC, SC. The sequence shows 16 steps: 1. Message Transfer (SC to SMS-GMSC); 2a. Nnrf_NFDiscovery_Request (SMS-GMSC to NRF); 2b. Nnrf_NFDiscovery_Response (NRF to SMS-GMSC); 3. Nudm_UECM_SendRoutingInfoForSM (SMS-GMSC to UDM); 4. Nipsmgw_SMService_RoutingInfo (UDM to IP-SM-GW); 5. Nipsmgw_SMService_RoutingInfo Response (IP-SM-GW to UDM); 6. Nudm_UECM_SendRoutingInfoForSM Response (UDM to SMS-GMSC); 7. Nipsmgw_SMService_MtForwardSm (SMS body) (UDM to IP-SM-GW); 8. Nsmmf_SMService_MtForwardSm (SMS body) (IP-SM-GW to SMSF); 9. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] (SMSF internal); 10. Nsmmf_SMService_MtForwardSm Response (Delivery Report) (SMSF to IP-SM-GW); 11. Nipsmgw_SMService_MtForwardSm (Delivery Rpt) (IP-SM-GW to SMS-GMSC); 12. Nudm_ReportSMDeliveryStatus_Request (SMS-GMSC to UDM); 13. Nudm_ReportSMDeliveryStatus_Request Response (UDM to SMS-GMSC); 14. Nudm_ReportSMDeliveryStatus_Request (SMS-GMSC to UDM); 15. Nudm_ReportSMDeliveryStatus_Request Response (UDM to SMS-GMSC); 16. Delivery Report (SMS-GMSC to SC).](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +Sequence diagram for MT SMS over NAS via IP-SM-GW. Lifelines: SMSF, NRF, IP-SM-GW, UDM, SMS-GMSC, SC. The sequence shows 16 steps: 1. Message Transfer (SC to SMS-GMSC); 2a. Nnrf\_NFDiscovery\_Request (SMS-GMSC to NRF); 2b. Nnrf\_NFDiscovery\_Response (NRF to SMS-GMSC); 3. Nudm\_UECM\_SendRoutingInfoForSM (SMS-GMSC to UDM); 4. Nipsmgw\_SMService\_RoutingInfo (UDM to IP-SM-GW); 5. Nipsmgw\_SMService\_RoutingInfo Response (IP-SM-GW to UDM); 6. Nudm\_UECM\_SendRoutingInfoForSM Response (UDM to SMS-GMSC); 7. Nipsmgw\_SMService\_MtForwardSm (SMS body) (UDM to IP-SM-GW); 8. Nsmmf\_SMService\_MtForwardSm (SMS body) (IP-SM-GW to SMSF); 9. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] (SMSF internal); 10. Nsmmf\_SMService\_MtForwardSm Response (Delivery Report) (SMSF to IP-SM-GW); 11. Nipsmgw\_SMService\_MtForwardSm (Delivery Rpt) (IP-SM-GW to SMS-GMSC); 12. Nudm\_ReportSMDeliveryStatus\_Request (SMS-GMSC to UDM); 13. Nudm\_ReportSMDeliveryStatus\_Request Response (UDM to SMS-GMSC); 14. Nudm\_ReportSMDeliveryStatus\_Request (SMS-GMSC to UDM); 15. Nudm\_ReportSMDeliveryStatus\_Request Response (UDM to SMS-GMSC); 16. Delivery Report (SMS-GMSC to SC). + +**Figure 5.1.4-1: MT SMS over NAS via IP-SM-GW** + +1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. +- 2a. SMS-GMSC invokes the Nnrf\_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscriptions of the GPSI. The SMS-GMSC may need to retrieve the PLMN ID of the recipients GPSI before the discovery of the UDM instance based on the GPSI-to-Subscription-Network resolution procedure defined in clause 5.1.7. +- 2b. If no UDM supporting SMS SBI could be discovered, the NRF indicates so to SMS-GMSC (by not including any UDM instance in the discovery response), and SMS-GMSC shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2], +or if a UDM supporting SMS SBI is discovered and selected, NRF returns the IP addresses or FQDNs of the serving UDM to provide Nudm\_UECM\_SendRoutingInfoForSM service to SMS-GMSC. + +3. The SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the serving node information for all access types for the UE. +4. The UDM shall check the registration/reachability flags to determine the potential target nodes, e.g. SMSF. For MT SM transfer via IP-SM-GW, the UDM shall invoke the Nipsmgw\_SMService\_RoutingInfo to provide the SMSF Instance Id to the IP-SM-GW. The address of the IP-SM-GW to be contacted by the UDM may be configured locally. +5. The IP-SM-GW shall send Nipsmgw\_SMService\_RoutingInfo response to the UDM. +6. The UDM responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response, including IP-SM-GW address, the indication for SMSF SMS\_SBI support and the indication for IP-SM-GW SMS\_SBI support. +- 7-8. The SMS-GMSC forwards the SMS message to the IP-SM-GW, and then IP-SM-GW performs service authorization and domain selection to determine the domain for delivery of the Short Message as defined in 3GPP TS 23.204 [15]. If the SMSF is selected, the IP-SM-GW forwards the SMS message to the SMSF. If the IP-SM-GW has more than one SMSF address to use for SMS transport towards the UE, then the IP-SM-GW chooses which SMSF address to use first based on operator local policy. + +The SMS-GMSC selects protocol based on the indication for SMSF SMS\_SBI support and IP-SM-GW SBI support: + +If both SMSF and IP-SM-GW indicate support for SMS\_SBI, SMS-GMSC forwards the SMS message to the IP-SM-GW by invoking Nipsmgw\_SMService\_MtForwardSm service operation. And then the IP-SM-GW forwards the SMS message to the SMSF by invoking Nsmsf\_SMService\_MtForwardSm service operation. + +If SMSF or IP-SM-GW indicates that it does not support SMS\_SBI, SMS-GMSC should forward SMS message to IP-SM-GW by legacy MAP/Diameter protocol. Then IP-SM-GW forwards the SMS message to the SMSF by legacy MAP/Diameter protocol. The following steps follow the procedures for legacy MT SMS message transfer, as illustrated in Figure 15aa of TS23.040 [2]. + +9. The MT SMS over NAS procedure between SMSF, AMF and UE is the same as in step 4a to 6b of Figure 4.13.3.6-1 of 3GPP TS 23.502 [4]. +10. The SMSF delivers the delivery report to the IP-SM-GW by sending the Nsmsf\_SMService\_MtForwardSm response to the IP-SM-GW. +11. The IP-SM-GW delivers the delivery report to the SMS-GMSC by sending the Nipsmgw\_SMService\_MtForwardSm response to the SMS-GMSC. +12. The IP-SM-GW may report the SM-Delivery Status to the UDM by invoking Nudm\_ReportSMDeliveryStatus\_Request. +13. The UDM responses with Nudm\_ReportSMDeliveryStatus\_Request response to the IP-SM-GW. +- 14-15. The SMS-GMSC may report the SM-Delivery Status to the UDM by invoking Nudm\_ReportSMDeliveryStatus\_Request and the UDM shall ignore the information provided in this report. +16. The SMS-GMSC delivers the delivery report to the SC as defined in 3GPP TS 23.040 [2]. +17. The MT SMS over NAS procedure between SMSF, AMF and UE is the same as in step 6c to 6d of Figure 4.13.3.6-1 of 3GPP TS 23.502 [4]. + +### 5.1.5 Unsuccessful Mobile Terminated short message transfer without SMS Router/IP-SM-GW + +![Sequence diagram for Unsuccessful MT SMS over NAS without SMS Router/ IP-SM-GW. The diagram shows interactions between SMSF, NRF, UDM, SMS-GMSC, and SC. The process starts with a Message Transfer from SC to SMS-GMSC. SMS-GMSC then sends an Nnrf_NFDiscovery_Request to NRF. NRF responds with Nnrf_NFDiscovery_Request Response. SMS-GMSC then sends a Nudm_UECM_SendRoutingInfoForSM to UDM. UDM responds with a Nudm_UECM_SendRoutingInfoForSM Response (error cause). SMS-GMSC then sends an Nsmmf_SMService_MtForwardSm (SMS body) to SMSF. A callout box indicates that step 4a-6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] is skipped. SMSF then sends an Nsmmf_SMService_MtForwardSm Response (error cause) to SMS-GMSC. SMS-GMSC then sends a Nudm_SMReportStatus_Request to UDM. UDM responds with a Nudm_SMReportStatus_Request Response. SMS-GMSC then sends a Failure Report to SC. Finally, SMS-GMSC sends a Nudm_EventExposure_Subscribe to UDM, which responds with a Nudm_EventExposure_Subscribe resp.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant NRF + participant UDM + participant SMSF + + Note left of SMSF: 6. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + + SC->>SMS-GMSC: 1. Message Transfer + SMS-GMSC->>NRF: 2a. Nnrf_NFDiscovery_Request + NRF-->>SMS-GMSC: 2b. Nnrf_NFDiscovery_Request Response + SMS-GMSC->>UDM: 3. Nudm_UECM_SendRoutingInfoForSM + UDM-->>SMS-GMSC: 4. Nudm_UECM_SendRoutingInfoForSM Response (error cause) + SMS-GMSC->>SMSF: 5. Nsmmf_SMService_MtForwardSm (SMS body) + Note left of SMSF: 6. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + SMSF-->>SMS-GMSC: 7. Nsmmf_SMService_MtForwardSm Response (error cause) + SMS-GMSC->>UDM: 8. Nudm_SMReportStatus_Request + UDM-->>SMS-GMSC: 9. Nudm_SMReportStatus_Request Response + SMS-GMSC->>SC: 10. Failure Report + SMS-GMSC->>UDM: 11. Nudm_EventExposure_Subscribe + UDM-->>SMS-GMSC: 12. Nudm_EventExposure_Subscribe resp + +``` + +Sequence diagram for Unsuccessful MT SMS over NAS without SMS Router/ IP-SM-GW. The diagram shows interactions between SMSF, NRF, UDM, SMS-GMSC, and SC. The process starts with a Message Transfer from SC to SMS-GMSC. SMS-GMSC then sends an Nnrf\_NFDiscovery\_Request to NRF. NRF responds with Nnrf\_NFDiscovery\_Request Response. SMS-GMSC then sends a Nudm\_UECM\_SendRoutingInfoForSM to UDM. UDM responds with a Nudm\_UECM\_SendRoutingInfoForSM Response (error cause). SMS-GMSC then sends an Nsmmf\_SMService\_MtForwardSm (SMS body) to SMSF. A callout box indicates that step 4a-6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] is skipped. SMSF then sends an Nsmmf\_SMService\_MtForwardSm Response (error cause) to SMS-GMSC. SMS-GMSC then sends a Nudm\_SMReportStatus\_Request to UDM. UDM responds with a Nudm\_SMReportStatus\_Request Response. SMS-GMSC then sends a Failure Report to SC. Finally, SMS-GMSC sends a Nudm\_EventExposure\_Subscribe to UDM, which responds with a Nudm\_EventExposure\_Subscribe resp. + +**Figure 5.1.5-1: Unsuccessful MT SMS over NAS without SMS Router/ IP-SM-GW** + +1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. +- 2a. SMS-GMSC invokes the Nnrf\_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscriptions of the GPSI. The SMS-GMSC may need to retrieve the PLMN ID of the recipients GPSI before the discovery of the UDM instance based on the GPSI-to-Subscription-Network resolution procedure defined in clause 5.1.7. +- 2b. If no UDM supporting SMS SBI could be discovered, the NRF indicates so to SMS-GMSC (by not including any UDM instance in the discovery response), and SMS-GMSC shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2], + +or if a UDM supporting SMS SBI is discovered and selected, NRF returns the IP addresses or FQDNs of the serving UDM to provide Nudm\_UECM\_SendRoutingInfoForSM service to SMS-GMSC. + +3. SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the routing information of the nodes available for MT SMS delivery, in this case the registered serving SMSF instance for all access types for UE. +4. The UDM shall check the registration/reachability flags to determine the potential target nodes. If the UDM is failed at this step, e.g. user not found in the UDM, the UDM shall respond to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response with error cause. If there is no target node address registered in the UDM, a response with error case indicating absent subscriber for SM is sent to the SMS-GMSC and the procedure continues in step 11. +5. If successful response is returned in step 4, the SMS-GMSC forwards the SMS message to the SMSF by invoking Nsmmf\_SMService\_MtForwardSm service operation. If the SMS-GMSC has more than one SMSF address to use for SMS transport towards the UE, then the SMS-GMSC chooses which SMSF address to use first based on operator local policy. +6. MT SMS over NAS procedure between SMSF, AMF and UE is same as the definition in step 4a to 6b of Figure 4.13.3.6-1 of 3GPP TS 23.502 [4]. +7. If the AMF informs the SMSF that it cannot deliver the MT-SMS to the UE in step 6, e.g. UE is not reachable, or the SMSF is failed at this step, e.g. memory capacity exceeded, the SMSF shall send the Nsmmf\_SMService\_MtForwardSm response with error cause to the SMS-GMSC. + +If the SMS-GMSC has more than one SMSF address to use for SMS transport towards the UE, then upon receiving MT-SMS failure report, the SMS-GMSC, based on operator local policy, may re-attempt the MT-SMS delivery via the other SMSF. If MT-SMS delivery also fails over the other SMSF, then the SMS-GMSC continues with step 8. + +8. The SMS-GMSC may report the SM-Delivery Status (e.g. UE is not reachable or memory capacity exceeded) to UDM by invoking Nudm\_ReportSMDeliveryStatus\_Request. +9. UDM responses Nudm\_ReportSMDeliveryStatus\_Request response to SMS-GMSC. +10. The SMS-GMSC sends the failure report to SC as defined in TS 23.040 [2]. +11. The SMS-GMSC subscribes in UDM to be notified when the UE becomes reachable for SMS (i.e. when the UE gets in radio contact with the AMF while an SMSF is actually registered, or when an SMSF gets registered) by using the Nudm\_EventExposure\_Subscribe service operation for Reachability for SMS event as defined in 3GPP TS 23.502 [4]. +12. If applicable, the UDM subscribes to UE reachability notification in the AMF(s) using the Namf\_EventExposure service and sets the relevant reachability flags. The UDM acknowledges the event subscription created by the SMS-GMSC. + +### 5.1.6 Unsuccessful Mobile Terminated short message transfer via IP-SM-GW + +![Sequence diagram for Unsuccessful MT SMS over NAS via IP-SM-GW. Lifelines: SMSF, NRF, IP-SM-GW, UDM, SMS-GMSC, SC. The sequence shows an unsuccessful transfer where the IP-SM-GW returns an error cause in step 5, which is propagated back through the chain to the SC in step 17.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant UDM + participant IP-SM-GW + participant NRF + participant SMSF + + Note left of SMSF: 9. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + + SC->>SMS-GMSC: 1. Message Transfer + SMS-GMSC->>NRF: 2a. Nnrf_NFDiscovery_Request + NRF-->>SMS-GMSC: 2b. Nnrf_NFDiscovery_Request Respone + SMS-GMSC->>UDM: 3. Nudm_UECM_SendRoutingInfoForSM + UDM->>IP-SM-GW: 4. Nipsmgw_SMService_RoutingInfo + IP-SM-GW-->>UDM: 5. Nipsmgw_SMService_RoutingInfo Response (error cause) + UDM-->>SMS-GMSC: 6. Nudm_UECM_SendRoutingInfoForSM Response (error cause) + SMS-GMSC->>IP-SM-GW: 7. Nipsmgw_SMService_MtForwardSm (SMS body) + IP-SM-GW->>SMSF: 8. Nsmmf_SMService_MtForwardSm (SMS body) + Note left of SMSF: 9. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + SMSF-->>IP-SM-GW: 10. Nsmmf_SMService_MtForwardSm Response (error cause) + IP-SM-GW-->>SMS-GMSC: 11. Nipsmgw_SMService_MtForwardSm Response (error cause) + IP-SM-GW-->>UDM: 12. Nudm_ReportSMDeliveryStatus_Request + UDM-->>IP-SM-GW: 13. Nudm_ReportSMDeliveryStatus_Request Response + Note right of IP-SM-GW: 14. IP-SM-GW performs subscription to UE reachability event as described in steps 9-13 of figure 5.5.6.3-1 in 3GPP TS 23.632 [5] + UDM-->>SMS-GMSC: 15. Nudm_ReportSMDeliveryStatus_Request + SMS-GMSC-->>UDM: 16. Nudm_ReportSMDeliveryStatus_Request Response + SMS-GMSC->>SC: 17. Failure Report + +``` + +Sequence diagram for Unsuccessful MT SMS over NAS via IP-SM-GW. Lifelines: SMSF, NRF, IP-SM-GW, UDM, SMS-GMSC, SC. The sequence shows an unsuccessful transfer where the IP-SM-GW returns an error cause in step 5, which is propagated back through the chain to the SC in step 17. + +**Figure 5.1.6-1: Unsuccessful MT SMS over NAS via IP-SM-GW** + +1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. +- 2a. SMS-GMSC invokes the Nnrf\_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscriptions of the GPSI. The SMS-GMSC may need to retrieve the PLMN ID of the recipients GPSI before the discovery of the UDM instance based on the GPSI-to-Subscription-Network resolution procedure defined in clause 5.1.7. + +- 2b. If no UDM supporting SMS SBI could be discovered, the NRF indicates so to SMS-GMSC (by not including any UDM instance in the discovery response), and SMS-GMSC shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2], +or if a UDM supporting SMS SBI is discovered and selected, NRF returns the IP addresses or FQDNs of the serving UDM to provide Nudm\_UECM\_SendRoutingInfoForSM service to SMS-GMSC. +3. SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the serving node information for UE. +4. The UDM shall check the registration/reachability flags to determine the potential target nodes, e.g. SMSF. For MT SM transfer via IP-SM-GW, the UDM shall invoke the Nipsmgw\_SMSService\_RoutingInfo to provide the SMSF Instance Id to the IP-SM-GW. The address of the IP-SM-GW to be contacted by the UDM may be configured locally. +5. If any failure at this step, the IP-SM-GW shall send Nipsmgw\_SMSService\_RoutingInfo response with error cause to the UDM. +6. If the UDM receives error response from IP-SM-GW in step 5 or UDM is failed after step 3, e.g. user not found in the UDM, the UDM shall respond to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response with error cause. If there is no target node address registered in the UDM, a response with error case indicating absent subscriber for SM is sent to the SMS-GMSC and the procedure continues in step 14. +7. If successful response is returned in step 6, the SMS-GMSC forwards the SMS message to the IP-SM-GW by invoking Nipsmgw\_SMSService\_MtForwardSm service operation. +8. The IP-SM-GW performs service authorization and domain selection to determine the domain for delivery of the Short Message as defined in 3GPP TS 23.204 [15]. If the SMSF is selected, the IP-SM-GW forwards the SMS message to the SMSF by invoking Nsmmf\_SMSService\_MtForwardSm service operation. If the IP-SM-GW has more than one SMSF address to use for SMS transport towards the UE, then the IP-SM-GW chooses which SMSF address to use first based on operator local policy. +9. MT SMS over NAS procedure between SMSF, AMF and UE is same as the definition in step 4a to 6b of Figure 4.13.3.6-1 of 3GPP TS 23.502 [4]. +10. If the AMF informs the SMSF that it cannot deliver the MT-SMS to the UE in step 9, e.g. UE is not reachable, or the SMSF is failed at this step, e.g. memory capacity exceeded, the SMSF shall send the Nsmmf\_SMSService\_MtForwardSm response with error cause to the IP-SM-GW. +11. If the IP-SM-GW receives error response from SMSF in step 10 and the IP-SM-GW has tried all selectable domains and accesses or the IP-SM-GW is failed after step 7, the IP-SM-GW shall send the Nipsmgw\_SMSService\_MtForwardSm response with error cause to the SMS-GMSC. +- 12-13. The IP-SM-GW may report the SM-Delivery Status (e.g. UE is not reachable or memory capacity exceeded) to UDM by invoking Nudm\_ReportSMDeliveryStatus\_Request. +14. The IP-SM-GW subscribes in HSS to be notified when the UE becomes reachable again, and subsequently the HSS subscribes in the UDM to UE reachability for SMS over IP event, as defined in clause 5.5.6 of 3GPP TS 23.632 [5]. If applicable, the UDM subscribes to UE reachability notification in the AMF(s) using the Namf\_EventExposure service and sets the relevant reachability flags. +- 15-16. The SMS-GMSC may report the SM-Delivery Status to UDM by invoking Nudm\_ReportSMDeliveryStatus\_Request and the UDM shall ignore the information provided in this report. +17. If the SMS-GMSC receives error response from IP-SM-GW in step 6 or step 11, the SMS-GMSC sends the failure report to SC as defined in TS 23.040 [2]. + +### 5.1.7 GPSI-to-Subscription-Network resolution procedure + +#### 5.1.7.1 General + +MT SMS delivery procedure requires routing based on the GPSI of the SMS recipient for interactions between the SMS-GMSC and the UDM, e.g., to retrieve the SMS routing information (e.g., the SMSF address) or report delivery status. In case that the SMS recipient belongs to a PLMN different from the PLMN of the SMS sender, the signaling takes place across PLMN borders. + +When using service-based interface between the SMS-GMSC and the UDM, if the GPSI is the only known SMS recipient's identifier, the SMS-GMSC needs to determine the target PLMN to be able to interact with the UDM in the home PLMN of the SMS recipient. The SMS-GMSC can determine the target PLMN using one of the following mechanisms: + +- GPSI-to-Subscription-Network resolution triggered by the NF consumer, described in clause 5.1.7.2. +- GPSI-to-Subscription-Network resolution using NRF, described in clause 5.1.7.4. +- GPSI-to-Subscription-Network resolution delegated by SCP, described in clause 5.1.7.3 + +It is assumed that the domain part in an External Identifier identifies the home PLMN and hence it is not required to determine the target PLMN when the GPSI is an External Identifier. The procedures described in the present clause 5.1.7 apply only when the GPSI is an MSISDN. + +NOTE: While these mechanisms are defined to determine the target PLMN for interactions between the SMS entities such as SMS-GMSC and the UDM requiring routing based on the GPSI of the SMS recipient, it can be applicable to any use case and procedure requiring selection of the target PLMN based on GPSI in 5GS. + +When the recipient GPSI belongs to the same country as the originating network and MNPF is not implemented in the country, the SMS-GMSC may skip the procedure and may directly discover UDM profile for invoking UDM service operation for routing information retrieval. In this case the SMS-GMSC determines the target PLMN ID from the recipient's GPSI Prefix (e.g. CC+NDC) while sending the discovery request to the NRF. + +#### 5.1.7.2 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC + +##### 5.1.7.2.1 General + +![Sequence diagram for GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC. The diagram shows four lifelines: NRF, MNPF, SMS-GMSC, and SC. The sequence of messages is: 1a. Nnrf_NFManagement_NFRegister from MNPF to NRF; 1b. Nnrf_NFManagement_NFRegister Response from NRF to MNPF; 2. Message Transfer from SC to SMS-GMSC; 3a. Nnrf_NFDiscovery_Request from SMS-GMSC to NRF; 3b. Nnrf_NFDiscovery_Request Response from NRF to SMS-GMSC; 4. Nmnpf_NPStatus_Get from SMS-GMSC to MNPF; 5. Nmnpf_NPStatus_Get Response from MNPF to SMS-GMSC.](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +``` + +sequenceDiagram + participant NRF + participant MNPF + participant SMS-GMSC + participant SC + Note left of MNPF: 1a. Nnrf_NFManagement_NFRegister + MNPF->>NRF: 1a. Nnrf_NFManagement_NFRegister + Note right of NRF: 1b. Nnrf_NFManagement_NFRegister Response + NRF-->>MNPF: 1b. Nnrf_NFManagement_NFRegister Response + Note left of SC: 2. Message Transfer + SC->>SMS-GMSC: 2. Message Transfer + Note left of SMS-GMSC: 3a. Nnrf_NFDiscovery_Request + SMS-GMSC->>NRF: 3a. Nnrf_NFDiscovery_Request + Note right of NRF: 3b. Nnrf_NFDiscovery_Request Response + NRF-->>SMS-GMSC: 3b. Nnrf_NFDiscovery_Request Response + Note left of SMS-GMSC: 4. Nmnpf_NPStatus_Get + SMS-GMSC->>MNPF: 4. Nmnpf_NPStatus_Get + Note right of MNPF: 5. Nmnpf_NPStatus_Get Response + MNPF-->>SMS-GMSC: 5. Nmnpf_NPStatus_Get Response + +``` + +Sequence diagram for GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC. The diagram shows four lifelines: NRF, MNPF, SMS-GMSC, and SC. The sequence of messages is: 1a. Nnrf\_NFManagement\_NFRegister from MNPF to NRF; 1b. Nnrf\_NFManagement\_NFRegister Response from NRF to MNPF; 2. Message Transfer from SC to SMS-GMSC; 3a. Nnrf\_NFDiscovery\_Request from SMS-GMSC to NRF; 3b. Nnrf\_NFDiscovery\_Request Response from NRF to SMS-GMSC; 4. Nmnpf\_NPStatus\_Get from SMS-GMSC to MNPF; 5. Nmnpf\_NPStatus\_Get Response from MNPF to SMS-GMSC. + +**Figure 5.1.7.2-1: GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC** + +1a-1b. The MNPF registers in the NRF with a new NF Type (e.g. MNPF). + +2. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. + +3a-3b. The SMS-GMSC should query the NRF to find the MNPF instance that manages the PLMN ID of the recipients GPSI's subscription network. The MNPF may belong to the same PLMN with SMS-GMSC or belong to the number range holder network which is different with the PLMN of SMS-GMSC. In latter case, the local NRF forwards the discovery request to the NRF of the number range holder PLMN. + +4. SMS-GMSC invokes Nmnpf\_NPStatus\_Get (GPSI) to the MNPF to get the target PLMN ID of the GPSI. + +5. MNPF checks the portability status of the recipient GPSI and responds back with the target PLMN ID. + +After step 5, the Mobile Terminated short message transfer procedures defined in clause 5.1 is performed from step 2a. The SMS-GMSC uses the target PLMN ID to discover the UDM NF profile via NRF for sending the routing information query to the UDM. If the target PLMN ID is not own network, the local NRF forwards the discovery request to the NRF of the target PLMN. + +##### 5.1.7.2.2 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Direct routing + +When MNP is implemented in a country or number portability domain with direct routing mechanism, the originating network first does the number portability query to identify the recipient GPSI's subscription PLMN before routing any messages based on GPSI. + +![Sequence diagram for GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Direct routing. The diagram shows interactions between the Originating Network (SMS-GMSC, NRF, MNPF, UDM), Number Range Holder N/W (NRF, UDM), and Subscription Network (NRF, UDM). It details the steps for MNPF registration, NRF discovery, MNPF status query, and subsequent UDM routing information requests based on whether the number is owned or ported.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +The sequence diagram illustrates the interaction for GPSI-to-Subscription-Network resolution. It is divided into three main lifelines: Originating Network (containing SMS-GMSC, NRF, MNPF, and UDM), Number Range Holder N/W (containing NRF and UDM), and Subscription Network (containing NRF and UDM). The process begins with the MNPF registering with the NRF (Step 1). The SMS-GMSC then discovers the MNPF instance (Steps 2-3) and queries its portability status (Steps 4-5). Based on the response, the SMS-GMSC discovers the UDM (Step 6a) and sends a routing information request (Step 8a). The UDM responds (Step 9a). If the number is ported (Case 2), the local NRF forwards the UDM discovery request to the Subscription Network's NRF (Step 6b), which returns the UDM instance (Step 7b). The SMS-GMSC then sends the routing information request to the Subscription Network's UDM (Step 8b), which responds (Step 9b). Case 1 indicates the number is owned (Own Not Ported or Ported In), while Case 2 indicates it is ported to another network (Own Ported Out, Foreign Ported to Foreign, or Foreign Not Ported). + +Sequence diagram for GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Direct routing. The diagram shows interactions between the Originating Network (SMS-GMSC, NRF, MNPF, UDM), Number Range Holder N/W (NRF, UDM), and Subscription Network (NRF, UDM). It details the steps for MNPF registration, NRF discovery, MNPF status query, and subsequent UDM routing information requests based on whether the number is owned or ported. + +Figure 5.1.7.2.2-1 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC (Direct Routing) + +1. If the MNPF is deployed, the MNPF registers in the NRF with a new NF Type (e.g. MNPF). +- 2-3. The SMS-GMSC should query the NRF to find the MNPF instance that manages the PLMN ID of the recipients GPSI's subscription network. +4. SMS-GMSC invokes Nnmf\_NPStatus\_Get (GPSI) to the MNPF to get the target PLMN ID of the GPSI. +5. MNPF checks the portability status of the recipient GPSI and responds back with the target PLMN ID. + +NOTE: When the recipient GPSI belongs to the same country as the originating network and MNPF is not implemented in the country, the steps 1-5 is skipped. In this case the SMS-GMSC determines the target PLMN ID from the recipient's GPSI Prefix (e.g. CC+NDC) based on local configuration. + +6-7. SMS-GMSC shall query the NRF to find the UDM instance serving the target PLMN based on target PLMN ID received in step 6. For step 7b-8b, if the target PLMN ID is not the originating network, the local NRF forwards the discovery request to the NRF of the target PLMN. + +8-9. SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM of the target PLMN to get the serving node instance for UE. The UDM shall check the registration/reachability flags to determine the potential target nodes and responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response, in this procedure the SMSF instance Id is included in the response message. + +##### **5.1.7.2.3 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Indirect routing** + +When MNP is implemented in a country or number portability domain with indirect routing mechanism, the signalling messages are always routed to the number range holder network, the number range holder then performs a number portability check and forwards the request to the subscription network if the number is ported out. For the case of international SMS termination also indirect routing is applied. In the case of international SMS termination, the originating network is outside the number portability domain and may not have any knowledge of whether number portability is implemented in the country of the recipient GPSI. + +![Sequence diagram showing GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Indirect routing. The diagram involves three main entities: Originating Network (SMS-GMSC, NRF), Number Range Holder Network (NRF, MNPF, UDM), and Subscription Network (NRF, UDM). The process starts with MNPF registering in the NRF of the Number Range Holder Network. The SMS-GMSC then queries the NRF for MNPF instances. It then checks the porting status using MNPF. Depending on whether the number is ported (Case 1) or not (Case 2), it either resolves the UDM in the Number Range Holder Network or queries the Subscription Network's NRF for the UDM instance.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` + +sequenceDiagram + participant SMS-GMSC + participant NRF as NRF + participant MNPF + participant UDM + Note right of Subscription Network: Case 1: +Number is Not ported + Note right of Subscription Network: Case 2: +Number is Ported out + + MNPF->>NRF: 1. Nnrf_NFManagement (NFType=MNPF, serviceName=Nmnpf_NPStatus) + SMS-GMSC->>NRF: 2. Nnrf_NFDiscovery (target-nf-type=MNPF, serviceName=Nmnpf_NPStatus, target PLMN ID=number range holder) + NRF-->>SMS-GMSC: 3. Nnrf_NFDiscovery_Response NF Instance(s) = MNPF Instances + SMS-GMSC->>MNPF: 4. Nmnpf_NPStatus_Get (GPSI) + MNPF-->>SMS-GMSC: 5. Nmnpf_NPStatus_Get response (Porting status, Target PLMN ID) + + Note left of Subscription Network: Case 1: Number is Not ported + SMS-GMSC->>NRF: 6a. Nnrf_NFDiscovery (NFType=UDM, serviceName=Nudm_routingInfo, PLMN ID= PLMN ID received in Step 6) + NRF-->>SMS-GMSC: 7a. Nnrf_NFDiscovery_Response (UDM instance) + SMS-GMSC->>UDM: 8a. Nudm_UECM_SendRoutingInfoForSM + UDM-->>SMS-GMSC: 9a. Nudm_UECM_SendRoutingInfoForSM Response + + Note left of Subscription Network: Case 2: Number is Ported out + SMS-GMSC->>NRF: 6b. Nnrf_NFDiscovery (NFType=UDM, serviceName=Nudm_routingInfo, PLMN ID= PLMN ID received in Step 6) + NRF-->>Subscription Network: 7b. Nnrf_NFDiscovery_Response (UDM Instance(s)) + SMS-GMSC->>UDM: 8b. Nudm_UECM_SendRoutingInfoForSM + UDM-->>SMS-GMSC: 9b. Nudm_UECM_SendRoutingInfoForSM Response + +``` + +Sequence diagram showing GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC for Indirect routing. The diagram involves three main entities: Originating Network (SMS-GMSC, NRF), Number Range Holder Network (NRF, MNPF, UDM), and Subscription Network (NRF, UDM). The process starts with MNPF registering in the NRF of the Number Range Holder Network. The SMS-GMSC then queries the NRF for MNPF instances. It then checks the porting status using MNPF. Depending on whether the number is ported (Case 1) or not (Case 2), it either resolves the UDM in the Number Range Holder Network or queries the Subscription Network's NRF for the UDM instance. + +**Figure 5.1.7.2.3-1 GPSI-to-Subscription-Network resolution triggered by the SMS-GMSC (Indirect Routing)** + +1. If the MNPF is deployed in the Number Range Holder PLMN, the MNPF registers in the NRF of the number range holder PLMN with a new NF Type (e.g. MNPF). + +2-3. The SMS-GMSC should query the local NRF to find the MNPF instance that manages the PLMN ID of the recipients GPSI's subscription network, the local NRF forwards the discovery request to the NRF of the number range holder PLMN. + +4. SMS-GMSC invokes Nmnpf\_NPStatus\_Get (GPSI) to the MNPF to get the target PLMN ID of the GPSI. + +5. MNPF checks the portability status of the recipient GPSI and responds back with the target PLMN ID. + +NOTE: When the recipient GPSI belongs to the same country as the number range holder network and MNPF is not implemented in the country, the steps 1-5 is skipped. In this case the SMS-GMSC determines the target PLMN ID from the recipient's GPSI Prefix (e.g. CC+NDC) based on local configuration. + +6-7. SMS-GMSC shall query the NRF to find the UDM instance serving the target PLMN based on target PLMN ID received in step 6. + +- For step 7a-8a, if the target PLMN ID belongs to the number range holder PLMN, the local NRF forwards the discovery request to the NRF of the number range holder PLMN. + +- For step 7b-8b, if the target PLMN ID belongs to the Subscription PLMN, the local NRF forwards the discovery request to the NRF of the Subscription PLMN. + +8-9. SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM of the target PLMN to get the serving node instance for UE. The UDM shall check the registration/reachability flags to determine the potential target nodes and responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response, in this procedure the SMSF instance Id is included in the response message. + +#### 5.1.7.3 SCP supports GPSI-to-Subscription-Network resolution procedure + +##### 5.1.7.3.1 General + +This procedure is used to retrieve the PLMN ID of the recipients GPSI for further discovery of UDM NF profiles for invoking UDM service operation for routing information retrieval. In indirect Communication with Delegated Discovery, the SCP is the service consumer of the GPSI-to-Subscription-Network resolution service in MNPF and routes an SBI message based on GPSI when MNPF is implemented. The SCP shall use the discovery factors (see 3GPP TS 29.500 [11], clause 6.10) provided by the SMS-GMSC to determine when to invoke the MNPF resolution, and to obtain the identity (GPSI) of the recipient. + +The SMS-GMSC sends routing information retrieval request to the SCP and the SCP uses the PLMN ID as the target PLMN ID in the discovery request towards NRF to discover the UDM NF profiles in the subscription network of the SMS recipient. + +##### 5.1.7.3.2 SCP supports GPSI-to-Subscription-Network resolution with MNPF + +![Sequence diagram showing the interaction between UDM, NRF, MNPF, SCP, SMS-GMSC, and SC for GPSI-to-Subscription-Network resolution. The diagram consists of 10 numbered steps: 1a-1b (MNPF registers with NRF), 2 (MT SMS interaction between SC and SMS-GMSC), 3 (SMS-GMSC sends Nudm_UECM_SendRoutingInfoForSM to SCP), 4a-4b (SCP queries NRF for MNPF instance), 5-6 (SCP invokes Nmmnf_NPStatus_Get on MNPF), 7a-7b (SCP queries NRF for MNPF instance), 8-9 (SCP sends Nudm_UECM_SendRoutingInfoForSM to UDM), and 10 (SCP sends Nudm_UECM_SendRoutingInfoForSM Response to SMS-GMSC).](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +``` + +sequenceDiagram + participant UDM + participant NRF + participant MNPF + participant SCP + participant SMS-GMSC + participant SC + + Note right of MNPF: 1a. Nnrf_NFManagement_NFRegister + MNPF->>NRF: 1a. Nnrf_NFManagement_NFRegister + Note right of NRF: 1b. Nnrf_NFManagement_NFRegister Response + NRF-->>MNPF: 1b. Nnrf_NFManagement_NFRegister Response + + Note right of SC: 2. Message Transfer + SC->>SMS-GMSC: 2. Message Transfer + + Note right of SMS-GMSC: 3. Nudm_UECM_SendRoutingInfoForSM + SMS-GMSC->>SCP: 3. Nudm_UECM_SendRoutingInfoForSM + + Note right of SCP: 4a. Nnrf_NFDiscovery_Request + SCP->>NRF: 4a. Nnrf_NFDiscovery_Request + Note right of NRF: 4b. Nnrf_NFDiscovery_Request Response + NRF-->>SCP: 4b. Nnrf_NFDiscovery_Request Response + + Note right of SCP: 5. Nmmnf_NPStatus_Get + SCP->>MNPF: 5. Nmmnf_NPStatus_Get + Note right of MNPF: 6. Nmmnf_NPStatus_Get Response + MNPF-->>SCP: 6. Nmmnf_NPStatus_Get Response + + Note right of SCP: 7a. Nnrf_NFDiscovery_Request + SCP->>NRF: 7a. Nnrf_NFDiscovery_Request + Note right of NRF: 7b. Nnrf_NFDiscovery_Request Response + NRF-->>SCP: 7b. Nnrf_NFDiscovery_Request Response + + Note right of SCP: 8. Nudm_UECM_SendRoutingInfoForSM + SCP->>UDM: 8. Nudm_UECM_SendRoutingInfoForSM + Note right of UDM: 9. Nudm_UECM_SendRoutingInfoForSM Response + UDM-->>SCP: 9. Nudm_UECM_SendRoutingInfoForSM Response + + Note right of SCP: 10. Nudm_UECM_SendRoutingInfoForSM Response + SCP->>SMS-GMSC: 10. Nudm_UECM_SendRoutingInfoForSM Response + +``` + +Sequence diagram showing the interaction between UDM, NRF, MNPF, SCP, SMS-GMSC, and SC for GPSI-to-Subscription-Network resolution. The diagram consists of 10 numbered steps: 1a-1b (MNPF registers with NRF), 2 (MT SMS interaction between SC and SMS-GMSC), 3 (SMS-GMSC sends Nudm\_UECM\_SendRoutingInfoForSM to SCP), 4a-4b (SCP queries NRF for MNPF instance), 5-6 (SCP invokes Nmmnf\_NPStatus\_Get on MNPF), 7a-7b (SCP queries NRF for MNPF instance), 8-9 (SCP sends Nudm\_UECM\_SendRoutingInfoForSM to UDM), and 10 (SCP sends Nudm\_UECM\_SendRoutingInfoForSM Response to SMS-GMSC). + +Figure 5.1.7.3.2-1: SCP supports GPSI-to-Subscription-Network resolution with MNPF + +1a-1b. If the MNPF is deployed, the MNPF registers in the NRF with a new NF Type (e.g. MNPF). + +2. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. + +3. The SMS-GMSC sends Nudm\_UECM\_SendRoutingInfoForSM to the SCP to get the serving node instance for UE from the UDM. As specified in the Indirect Communication with Delegated Discovery model, the Nudm\_UECM\_SendRoutingInfoForSM shall contain the discovery factors containing the GPSI (pointing to the Number Range Holder Network) and an indicator (i.e. "target-nw-resolution") that Subscription Network resolution is delegated to the SCP. The "target-nw-resolution" may also be sent by an SCP to the next hop SCP. The SCP receives the "target-nw-resolution" shall query the NF service consumer (MNPF) to obtain the PLMN ID of the recipient GPSI's subscription network. + +4a-4b. The SCP shall query the NRF to find the MNPF instance that manages the PLMN ID of the recipients GPSI's subscription network. The MNPF may belong to the same PLMN with SMS-GMSC or belong to the number range holder network which is different with the PLMN of SMS-GMSC. In latter case, the local NRF forwards the discovery request to the NRF of the number range holder PLMN. + +5. The SCP determines the target PLMN of the recipients GPSI's subscription network using the SBI service of the MNPF i.e. the SCP invokes Nmmnf\_NPStatus\_Get (GPSI) to the MNPF. + +6. MNPF checks the portability status of the recipient GPSI and responds back with the target PLMN ID. + +NOTE: If SCP is co-located with MNPF, steps between SCP and NRF to discover the MNPF, and steps between SCP and MNPF can be skipped. + +- 7a-7b. SCP shall query the NRF to find the UDM instance serving the target PLMN based on target PLMN ID received in step 6. +8. SCP invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the serving node instance for UE. +9. The UDM shall check the registration/reachability flags to determine the potential target nodes and responds to the SCP by sending Nudm\_UECM\_SendRoutingInfoForSM response, in this procedure the SMSF instance Id is included in the response message. +10. SCP forward the responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response (SMS Router address). + +##### 5.1.7.3.3 SCP supports GPSI-to-Subscription-Network resolution with NRF + +![Sequence diagram illustrating the interaction between UDM, NRF, MNPF, SCP, SMS-GMSC, and SC for GPSI-to-Subscription-Network resolution. The diagram shows 10 steps: 1a. MNPF registers with NRF; 1b. NRF responds; 2. SC sends Message Transfer to SMS-GMSC; 3. SMS-GMSC sends Nudm_UECM_SendRoutingInfoForSM to SCP; 4. SCP sends Nnrf_NFDiscovery_Request to NRF; 5. NRF sends Nmnpf_NPStatus_Get to MNPF; 6. MNPF responds; 7. NRF responds to SCP; 8. SCP sends Nudm_UECM_SendRoutingInfoForSM to UDM; 9. UDM responds; 10. SCP forwards response to SMS-GMSC.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +``` + +sequenceDiagram + participant MNPF + participant NRF + participant SCP + participant UDM + participant SMS-GMSC + participant SC + + Note left of MNPF: 1a. Nnrf_NFManagement_NFRegister + MNPF-->>NRF: 1a. Nnrf_NFManagement_NFRegister + Note right of NRF: 1b. Nnrf_NFManagement_NFRegister Response + NRF-->>MNPF: 1b. Nnrf_NFManagement_NFRegister Response + Note left of SC: 2. Message Transfer + SC->>SMS-GMSC: 2. Message Transfer + Note left of SMS-GMSC: 3. Nudm_UECM_SendRoutingInfoForSM + SMS-GMSC->>SCP: 3. Nudm_UECM_SendRoutingInfoForSM + Note left of SCP: 4. Nnrf_NFDiscovery_Request + SCP->>NRF: 4. Nnrf_NFDiscovery_Request + Note left of NRF: 5. Nmnpf_NPStatus_Get + NRF->>MNPF: 5. Nmnpf_NPStatus_Get + Note right of MNPF: 6. Nmnpf_NPStatus_Get Response + MNPF-->>NRF: 6. Nmnpf_NPStatus_Get Response + Note right of NRF: 7. Nnrf_NFDiscovery_Request Response + NRF-->>SCP: 7. Nnrf_NFDiscovery_Request Response + Note left of SCP: 8. Nudm_UECM_SendRoutingInfoForSM + SCP->>UDM: 8. Nudm_UECM_SendRoutingInfoForSM + Note right of UDM: 9. Nudm_UECM_SendRoutingInfoForSM Response + UDM-->>SCP: 9. Nudm_UECM_SendRoutingInfoForSM Response + Note left of SCP: 10. Nudm_UECM_SendRoutingInfoForSM Response + SCP->>SMS-GMSC: 10. Nudm_UECM_SendRoutingInfoForSM Response + +``` + +Sequence diagram illustrating the interaction between UDM, NRF, MNPF, SCP, SMS-GMSC, and SC for GPSI-to-Subscription-Network resolution. The diagram shows 10 steps: 1a. MNPF registers with NRF; 1b. NRF responds; 2. SC sends Message Transfer to SMS-GMSC; 3. SMS-GMSC sends Nudm\_UECM\_SendRoutingInfoForSM to SCP; 4. SCP sends Nnrf\_NFDiscovery\_Request to NRF; 5. NRF sends Nmnpf\_NPStatus\_Get to MNPF; 6. MNPF responds; 7. NRF responds to SCP; 8. SCP sends Nudm\_UECM\_SendRoutingInfoForSM to UDM; 9. UDM responds; 10. SCP forwards response to SMS-GMSC. + +Figure 5.1.7.3.3-1: SCP supports GPSI-to-Subscription-Network resolution with NRF + +- 1a-1b. If the MNPF is deployed, the MNPF registers in the NRF with a new NF Type (e.g. MNPF). +2. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. +3. The SMS-GMSC sends Nudm\_UECM\_SendRoutingInfoForSM to the SCP to get the serving node instance for UE from the UDM. The Nudm\_UECM\_SendRoutingInfoForSM contains the NF service discovery factors with the GPSI (pointing to the Number Range Holder Network) and an indicator (i.e. "target-nw-resolution") indicating that Subscription Network resolution is delegated to the SCP. The "target-nw-resolution" may also be sent by an SCP to the next hop SCP. +4. The SCP should query the NRF to find the UDM instance that manages the user subscriptions using the GPSI. The NRF receives the "target-nw-resolution" shall query the NF service consumer (MNPF) to obtain the PLMN ID of the recipient GPSI's subscription network. +5. The NRF determines the target PLMN of the recipients GPSI's subscription network using the SBI service of the MNPF i.e. the NRF invokes Nmnpf\_NPStatus\_Get (GPSI) to the MNPF. As an implementation choice the NRF may determine the target PLMN by other means, e.g. local configuration of ENUM query. + +6. MNPF checks the portability status of the recipient GPSI and responds back with the target PLMN ID. +7. NRF returns the UDM instance related to the GPSI and target PLMN Id to the SCP. For inter-PLMN discovery, the local NRF shall query the NRF in the target PLMN to find the UDM instance. If there are not NF instances available that can serve the request, the local NRF provides the discovery response indicating the consumer NF to use a legacy interface for the next operation request in the procedure. +8. SCP invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the serving node instance for UE. +9. The UDM shall check the registration/reachability flags to determine the potential target nodes and responds to the SCP by sending Nudm\_UECM\_SendRoutingInfoForSM response, in this procedure the SMSF instance Id is included in the response message. +10. SCP forward the responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response (SMS Router address). + +##### 5.1.7.3.4 SCP supports GPSI-to-Subscription-Network resolution with MNPF for Direct routing + +Figure 5.1.7.3.4-1 shows the procedure for Direct Communication with Delegated Discovery, the SCP is the service consumer of the GPSI-to-Subscription-Network resolution service in MNPF and routes an SBI message based on GPSI when direct routing of MNPF is implemented. + +![Sequence diagram illustrating the procedure for Direct Communication with Delegated Discovery for GPSI-to-Subscription-Network resolution. The diagram shows interactions between SMS-GMSC, SCP, NRF, MNPF, and UDM across three network domains: Originating Network, Number-Range Holder NW, and Subscription Network. The process involves MNPF registration, NRF discovery, MNPF status check, and subsequent UDM discovery and routing information requests.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +sequenceDiagram + participant SMS-GMSC + participant SCP + participant NRF as NRF + participant MNPF + participant UDM as UDM + Note right of UDM: Originating Network + Note right of UDM: Number-Range Holder NW + Note right of UDM: Subscription Network + + MNPF->>NRF: 1. Nrnf_NFManagement_Register (NFType=MNP) + SMS-GMSC->>SCP: 2. Nudm_UECM_SendRoutingInfoForSM (GPSI) + SCP->>NRF: 3. Nrnf_NFDiscovery_Request (target-nf-type=MNP) + NRF->>SCP: 4. Nrnf_NFDiscovery_Response (MNP instances) + SCP->>MNPF: 5. Nmmpf_NPStatus_Request (GPSI) + MNPF->>SCP: 6. Nmmpf_NPStatus_Response (Porting Status, Target PLMN Id) + + Note left of NRF: Number-Range Holder NW + SCP->>NRF: 7a. Nrnf_NFDiscovery_Request (target-nf-type=UDM, PLMNID=Target PLMN ID received in Step 6) + NRF->>SCP: 8a. Nrnf_NFDiscovery_Response (UDM Instances) + SCP->>UDM: 9a. Nudm_UECM_SendRoutingInfoForSM (GPSI) + UDM->>SCP: 10a. Nudm_UECM_SendRoutingInfoForSM Response + SCP->>SMS-GMSC: 11a. Nudm_UECM_SendRoutingInfoForSM Response + + Note left of NRF: Subscription Network + SCP->>NRF: 7b. Nrnf_NFDiscovery_Request (target-nf-type=UDM, PLMNID=Target PLMN ID received in Step 6) + NRF->>SCP: 8b. Nrnf_NFDiscovery_Response (UDM Instances) + SCP->>UDM: 9b. Nudm_UECM_SendRoutingInfoForSM (GPSI) + UDM->>SCP: 10b. Nudm_UECM_SendRoutingInfoForSM Response + SCP->>SMS-GMSC: 11b. Nudm_UECM_SendRoutingInfoForSM Response + + Note right of UDM: Case 1: B Number is OWN subscriber (Own Not Ported or Ported In) + Note right of UDM: Case 2: B Number is Ported/ other network subscriber (Own Ported Out, Foreign Ported to Foreign, Foreign Not Ported) + +``` + +Sequence diagram illustrating the procedure for Direct Communication with Delegated Discovery for GPSI-to-Subscription-Network resolution. The diagram shows interactions between SMS-GMSC, SCP, NRF, MNPF, and UDM across three network domains: Originating Network, Number-Range Holder NW, and Subscription Network. The process involves MNPF registration, NRF discovery, MNPF status check, and subsequent UDM discovery and routing information requests. + +**Figure 5.1.7.3.4-1 SCP supports the GPSI-to-Subscription-Network resolution with MNPF for Direct Routing** + +1. If the MNPF is deployed, the MNPF registers in the NRF with a new NF Type (e.g. MNPF). + +2. The SMS-GMSC sends Nudm\_UECM\_SendRoutingInfoForSM to the SCP to get the serving node instance for UE from the UDM. As specified in the Indirect Communication with Delegated Discovery model, the Nudm\_UECM\_SendRoutingInfoForSM shall contain the discovery factors containing the GPSI (pointing to the Number Range Holder Network) and an indicator that Subscription Network resolution is delegated to the SCP. +- 3-4. The SCP shall query the NRF to find the MNPF instance that manages the PLMN ID of the recipients GPSI's subscription network. +5. The SCP determines the target PLMN of the recipients GPSI's subscription network using the SBI service of the MNPF i.e. the SCP invokes Nmnpf\_NPStatus\_Get (GPSI) to the MNPF. +6. MNPF checks the portability status of the recipient GPSI and responds back with the target PLMN ID. + +NOTE 1: If SCP is co-located with MNPF, steps between SCP and NRF to discover the MNPF, and steps between SCP and MNPF can be skipped. + +NOTE 2: When the recipient GPSI belongs to the same country as the originating network and MNPF is not implemented in the country, steps between SCP and MNPF can be skipped. In this case the SMS-GMSC or SCP determines the target PLMN ID from the recipient's GPSI Prefix (e.g. CC+NDC) based on local configuration. + +- 7-8. SCP shall query the NRF to find the UDM instance serving the target PLMN based on target PLMN ID received in step 6. For step 7b-8b, if the target PLMN ID is not the originating network, the local NRF forwards the discovery request to the NRF of the target PLMN. +- 9-10. SCP invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM of the target PLMN to get the serving node instance for UE. The UDM shall check the registration/reachability flags to determine the potential target nodes and responds to the SCP by sending Nudm\_UECM\_SendRoutingInfoForSM response, in this procedure the SMSF instance Id is included in the response message. +11. SCP forward the responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response (SMS Router address). + +##### 5.1.7.3.5            SCP supports GPSI-to-Subscription-Network resolution with MNPF for Indirect routing + +Figure 5.1.7.3.5-1 shows the procedure for Indirect Communication with Delegated Discovery, the SCP is the service consumer of the GPSI-to-Subscription-Network resolution service in MNPF NF and routes an SBI message based on GPSI when indirect routing of MNPF is implemented. + +![Sequence diagram showing SCP supports GPSI-to-Subscription-Network resolution with MNPF for Indirect routing. The diagram is divided into three vertical dashed boxes: Originating Network, Number Range Holder NW, and Subscription Network. The Originating Network contains SMS-GMSC, SCP, and NRF. The Number Range Holder NW contains NRF, MNPF, and UDM. The Subscription Network contains NRF and UDM. The sequence starts with MNPF registering in the Number Range Holder NW NRF. Then, SMS-GMSC sends a Nudm_UECM_SendRoutingInfoForSM (GPSI) to SCP. SCP queries its local NRF for MNPF, which then queries the Number Range Holder NW NRF. The Number Range Holder NW NRF returns MNPF instances to SCP. SCP then sends Nmmnf_NPStatus_Request (GPSI) to MNPF, which returns Porting Status and Target PLMN ID. SCP then queries its local NRF for UDM instances. SCP sends Nudm_UECM_SendRoutingInfoForSM (GPSI) to UDM in the Number Range Holder NW. UDM returns a response. SCP then sends a response to SMS-GMSC. A dashed line separates Case 1 (B Number is Not Ported) and Case 2 (B Number is Ported Out). In Case 1, SCP sends Nudm_UECM_SendRoutingInfoForSM Response to SMS-GMSC. In Case 2, SCP queries the Subscription Network NRF for UDM instances, sends Nudm_UECM_SendRoutingInfoForSM (GPSI) to UDM in the Subscription Network, receives a response, and then sends Nudm_UECM_SendRoutingInfoForSM Response to SMS-GMSC.](dd5771673aececa53d42ece89218299d_img.jpg) + +Sequence diagram showing SCP supports GPSI-to-Subscription-Network resolution with MNPF for Indirect routing. The diagram is divided into three vertical dashed boxes: Originating Network, Number Range Holder NW, and Subscription Network. The Originating Network contains SMS-GMSC, SCP, and NRF. The Number Range Holder NW contains NRF, MNPF, and UDM. The Subscription Network contains NRF and UDM. The sequence starts with MNPF registering in the Number Range Holder NW NRF. Then, SMS-GMSC sends a Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to SCP. SCP queries its local NRF for MNPF, which then queries the Number Range Holder NW NRF. The Number Range Holder NW NRF returns MNPF instances to SCP. SCP then sends Nmmnf\_NPStatus\_Request (GPSI) to MNPF, which returns Porting Status and Target PLMN ID. SCP then queries its local NRF for UDM instances. SCP sends Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to UDM in the Number Range Holder NW. UDM returns a response. SCP then sends a response to SMS-GMSC. A dashed line separates Case 1 (B Number is Not Ported) and Case 2 (B Number is Ported Out). In Case 1, SCP sends Nudm\_UECM\_SendRoutingInfoForSM Response to SMS-GMSC. In Case 2, SCP queries the Subscription Network NRF for UDM instances, sends Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to UDM in the Subscription Network, receives a response, and then sends Nudm\_UECM\_SendRoutingInfoForSM Response to SMS-GMSC. + +**Figure 5.1.7.3.5-1 SCP supports GPSI-to-Subscription-Network resolution with MNPF for Indirect routing** + +1. If the MNPF is deployed in the Number Range Holder PLMN, the MNPF registers in the NRF of the number range holder PLMN with a new NF Type (e.g. MNPF). +2. The SMS-GMSC sends Nudm\_UECM\_SendRoutingInfoForSM to the SCP to get the serving node instance for UE from the UDM. As specified in the Indirect Communication with Delegated Discovery model, the Nudm\_UECM\_SendRoutingInfoForSM shall contain the discovery factors containing the GPSI (pointing to the Number Range Holder Network) and an indicator that Subscription Network resolution is delegated to the SCP. +- 3-4. The SCP shall query the local NRF to find the MNPF instance that manages the PLMN ID of the recipients GPSI's subscription network, the local NRF forwards the discovery request to the NRF of the number range holder PLMN. +5. The SCP determines the target PLMN of the recipients GPSI's subscription network using the SBI service of the MNPF i.e. the SCP invokes Nmmnf\_NPStatus\_Get (GPSI) to the MNPF. +6. MNPF checks the portability status of the recipient GPSI and responds back with the target PLMN ID. + +NOTE 1: If SCP is co-located with MNPF, steps between SCP and NRF to discover the MNPF, and steps between SCP and MNPF can be skipped. + +NOTE 2: When the recipient GPSI belongs to the same country as the number range holder network and MNPF is not implemented in the country, the steps between SCP and MNPF can be skipped. In this case the SMS-GMSC or SCP determines the target PLMN ID from the recipient's GPSI Prefix (e.g. CC+NDC) based on local configuration. + +- 7-8. SCP shall query the local NRF to find the UDM instance serving the target PLMN based on target PLMN ID received in step 6. +- For step 7a-8a, if the target PLMN ID belongs to the number range holder PLMN, the local NRF forwards the discovery request to the NRF of the number range holder PLMN. + - For step 7b-8b, if the target PLMN ID belongs to the Subscription PLMN, the local NRF forwards the discovery request to the NRF of the Subscription PLMN. +- 9-10. SCP invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM of the target PLMN to get the serving node instance for UE. The UDM shall check the registration/reachability flags to determine the potential target nodes and responds to the SCP by sending Nudm\_UECM\_SendRoutingInfoForSM response, in this procedure the SMSF instance Id is included in the response message. +11. SCP forwards the responds to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response (SMS Router address). + +#### 5.1.7.4 GPSI-to-Subscription-Network resolution using NRF + +Figure 5.1.7.4-1 shows the procedure to determine the target PLMN based on the GPSI using the discovery and selection framework via the NRF as defined in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4]. + +![Sequence diagram illustrating the determination of target PLMN based on GPSI using NRF across three network domains: Originating network, Number range holder network, and Subscription network.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +``` + +sequenceDiagram + participant SMS-GMSC as SMS-GMSC + participant NRF1 as NRF + participant MNPF1 as MNPF + participant NRF2 as NRF + participant MNPF2 as MNPF + participant NRF3 as NRF + participant UDM as UDM + participant HSS/HLR as HSS/HLR + + Note left of MNPF1: 2a/3a. Other alternatives +(e.g. local configuration, +DNS/ENUM query) + + Note right of NRF3: 5. Determination of target PLMN and +discovery of UDM instances in subscription +network as described in steps 2-4 + + SMS-GMSC->>NRF1: 1. Nnrf_NFDiscovery_Request + NRF1->>MNPF1: 2. MNPF query + MNPF1-->>NRF1: 3. MNPF response + Note left of MNPF1 + NRF1->>NRF3: 4. Nnrf_NFDiscovery_Request + NRF1-->>NRF2: 4a. Nnrf_NFDiscovery_Request + Note right of NRF3 + NRF3-->>NRF2: 6. Nnrf_NFDiscovery_Response + NRF2-->>NRF1: 6. Nnrf_NFDiscovery_Response + NRF1-->>SMS-GMSC: 7. Nnrf_NFDiscovery_Response + Note left of MNPF1 + NRF1->>UDM: 8a. Nudm_UECM_SendRoutingInfoForSM + UDM-->>HSS/HLR: 8b. MAP/Diameter SendRoutingInfoForShortMsg + +``` + +The sequence diagram illustrates the interaction between the SMS-GMSC, NRF, MNPF, UDM, and HSS/HLR across three network domains: Originating network, Number range holder network, and Subscription network. The process starts with the SMS-GMSC sending an Nnrf\_NFDiscovery\_Request to the local NRF. The NRF then sends an MNPF query to the MNPF, which responds. An alternative step (2a/3a) involving local configuration or DNS/ENUM query is shown in a dashed box. Next, the NRF sends an Nnrf\_NFDiscovery\_Request to the NRF in the Subscription network (step 4) and another to the NRF in the Number range holder network (step 4a). The NRF in the Subscription network performs the determination of target PLMN and discovery of UDM instances (step 5, shown in a dashed box) and returns an Nnrf\_NFDiscovery\_Response (step 6) to the NRF in the Number range holder network, which then forwards it to the local NRF. The local NRF then sends an Nnrf\_NFDiscovery\_Response to the SMS-GMSC (step 7). Finally, the local NRF sends an Nudm\_UECM\_SendRoutingInfoForSM request to the UDM (step 8a), which in turn sends a MAP/Diameter SendRoutingInfoForShortMsg to the HSS/HLR (step 8b). + +Sequence diagram illustrating the determination of target PLMN based on GPSI using NRF across three network domains: Originating network, Number range holder network, and Subscription network. + +Figure 5.1.7.4-1: Determination of target PLMN based on GPSI using NRF + +1. The SMS-GMSC located in the PLMN of the SMS sender contacts the NRF in the originating PLMN to perform NF/NF service discovery of the UDM instance(s). The discovery request is based on the GPSI of the SMS recipient and includes an indication for the NRF to determine the target PLMN and interface to be used (SBI or legacy interface). +2. Based on the indication to determine the target PLMN and interface to be used included in the discovery request, if direct routing mechanism is used the NRF in the originating PLMN retrieves the target PLMN ID from the MNPF in the originating PLMN by consuming the SBI services of the MNPF described in clause 6.7. The NRF performs an NP query to the MNPF using SBI for the GPSI of the SMS recipient. + +If indirect routing mechanism is used, steps 2-3 are skipped and the procedure continues in step 4a. + +3. The MNPF provides in the response the target PLMN information corresponding to the GPSI of the SMS recipient and the procedure continues in step 4. + +- 2a-3a. The NRF may, as an alternative implementation option to steps 2-3, obtain the target PLMN information by other means, e.g., using DNS/ENUM resolution, local configuration in the NRF or direct access to Number Portability (NP) databases via non-SBI, if applicable. + +NOTE 1: NP applies to GPSIs representing E.164 addresses (i.e., MSISDN). NP is subject to regional and regulatory requirements and is accomplished through the retrieval of ported data from NP databases. Support of ENUM or direct access to NP via non-SBI interfaces and the exact means to make the number portability data available to the NRF is subject to and configured per operator policy. + +The NRF may use the DNS/ENUM translation mechanism to resolve the GPSI of the SMS recipient in E.164 format to a URI as specified in IETF RFC 6116 [12]. The NRF performs an ENUM query for the GPSI of the SMS recipient in step 2a. The output of the lookup process in the DNS/ENUM server is a URI that is provided in the ENUM response and points to the originating PLMN or the NRF in the target PLMN with which the originating PLMN has an interconnection agreement using SBI, so that the NRF in the originating PLMN can send an inter-PLMN service discovery request to the NRF in the target PLMN. + +NOTE 2: The DNS/ENUM server searches for an ENUM record matching the GPSI of the SMS recipient. An ENUM record for the individual GPSI or number series provisioned in the DNS/ENUM server can be used to indicate whether the user belongs to the same PLMN or another PLMN in the same or different country. A URI as a result of the lookup process in the DNS/ENUM server can be provided by provisioning an ENUM service using the http or https scheme URI as defined in IETF RFC 4002 [13] and IETF RFC 6118 [14]. + +4. Based on the response from the MNPF, the NRF in the originating PLMN determines the target PLMN where to search for UDM instances. + +If the NRF has obtained the target PLMN information by other means in steps 2a-3a, the NRF determines the target PLMN based on the information from ENUM response, NP databases via non-SBI and/or local configuration. + +If the GPSI belongs to the originating PLMN (i.e. originating network is the same as subscription network), the NRF searches for UDM instances matching the discovery criteria that can serve the request in the originating PLMN using SBI services and provides the discovery response in step 7. + +If the GPSI belongs to a different PLMN, the NRF checks whether the originating PLMN has an interconnection agreement using SBI with the subscription PLMN and, in that case, sends an inter-PLMN discovery request including the GPSI to the NRF in the subscription PLMN to retrieve the UDM instances that can serve the SMS recipient, as defined in clause 4.17.5 of 3GPP TS 23.502 [4] and 3GPP TS 29.510 [10], and the procedure continues in step 6. + +- 4a. If indirect routing mechanism is used (i.e., no interaction as in steps 2-3 between NRF and MNPF in the originating PLMN), the NRF in the originating PLMN determines the PLMN ID of the number range holder network (e.g. from the recipient's GPSI prefix (CC+NDC) based on local configuration) and sends an inter-PLMN discovery request of UDM instances to the NRF in the number range holder network. In this case, the discovery request across PLMNs shall include the GPSI of the SMS recipient and the indication to determine the target PLMN and interface to be used. + +- Based on the indication to determine the target PLMN and interface to be used included in the discovery request from the NRF in the originating PLMN, the NRF in the number range holder PLMN applies the behaviour described for the NRF in steps 2-3 (or alternatively, steps 2a-3a) and step 4. + +The NRF in the number range holder network may perform a query to the MNPF using SBI if NP is required and NP information has not been retrieved previously (e.g., if originating and number range holder PLMNs belong to different countries or portability domains and NP is required in the country of the recipient GPSI). The NRF in the number range holder network obtains the PLMN ID of the subscription network in the response from the MNPF (or alternatively by other means such as ENUM/NP) and, if applicable, sends an inter-PLMN discovery request of UDM instances including the GPSI to the NRF in the subscription network. + +- The NRF in the subscription network provides the inter-PLMN discovery response including UDM instance(s) matching the discovery criteria or no UDM instance(s) found in the target PLMN, implying that SBI interactions should not be used. + +When using indirect routing, the NRF in the number range holder network forwards the discovery response from the NRF in the subscription network to the NRF in the originating network. + +- If the NRF in the originating network finds UDM instances matching the filter criteria in the originating PLMN or receives UDM instances in the response to a discovery request across PLMNs in step 6, the NRF provides the UDM instances in the discovery response to the SMS-GMSC. + +If no UDM instances can serve the request using SBI, the NRF provides the discovery response indicating the SMS-GMSC to use a non-SBI interface for the next operation request in the procedure. + +- If the discovery response includes UDM instances that can serve the SMS recipient, the SMS-GMSC sends the operation request using SBI to e.g., retrieve the SMS routing information from the UDM, and the SBI-based MT SMS procedure can be executed as described in clause 5.1. +- If no UDM instances are provided in the discovery response, the SMS-GMSC sends the operation request via legacy interface using MAP/Diameter to e.g., retrieve the SMS routing information from the HLR/HSS/UDM. + +### 5.1.8 Alert + +Figure 5.1.8-1 depicts procedure for alert. + +![Sequence diagram for the alert procedure. Lifelines: SC, SMS-GMSC/IWMSC, UDM, AMF/SMSF, UE. The diagram shows an 'Unsuccessful Mobile Terminated short message transfer procedure' followed by an alert sequence. The alert sequence involves: 1. AMF/SMSF sending a Nudm_EventExposure_Notify or Nudm_UECM_Registration or Nudm_UECM_Update to UDM. 2. UDM sending a Nudm_EventExposure_Notify Req to SMS-GMSC/IWMSC. 3. SMS-GMSC/IWMSC sending a Nudm_EventExposure_Notify Resp to UDM. 4. SMS-GMSC/IWMSC sending a ServiceCentreAlert to SC. A dashed box labeled 'Alert SC' encloses the SC and SMS-GMSC/IWMSC lifelines during the alert sequence.](6361dfaef83c9ffc3b147e1627ba76a1_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC/IWMSC + participant UDM + participant AMF/SMSF + participant UE + + Note over SC, SMS-GMSC/IWMSC, UDM, AMF/SMSF, UE: 1. Unsuccessful Mobile Terminated short message transfer procedure, as defined in steps 1-12 in Figure 5.1.5-1. + + Note left of SC: Alert SC + Note right of UE: Alert UE + + AMF/SMSF->>UDM: 2.Namf_EventExposure_Notify or Nudm_UECM_Registration or Nudm_UECM_Update + UDM->>SMS-GMSC/IWMSC: 3.Nudm_EventExposure_Notify Req + SMS-GMSC/IWMSC->>UDM: 4.Nudm_EventExposure_Notify Resp + SMS-GMSC/IWMSC->>SC: 5.ServiceCentreAlert + +``` + +Sequence diagram for the alert procedure. Lifelines: SC, SMS-GMSC/IWMSC, UDM, AMF/SMSF, UE. The diagram shows an 'Unsuccessful Mobile Terminated short message transfer procedure' followed by an alert sequence. The alert sequence involves: 1. AMF/SMSF sending a Nudm\_EventExposure\_Notify or Nudm\_UECM\_Registration or Nudm\_UECM\_Update to UDM. 2. UDM sending a Nudm\_EventExposure\_Notify Req to SMS-GMSC/IWMSC. 3. SMS-GMSC/IWMSC sending a Nudm\_EventExposure\_Notify Resp to UDM. 4. SMS-GMSC/IWMSC sending a ServiceCentreAlert to SC. A dashed box labeled 'Alert SC' encloses the SC and SMS-GMSC/IWMSC lifelines during the alert sequence. + +Figure 5.1.8-1: Procedure for alert + +- Unsuccessful Mobile Terminated short message transfer (without IP-SM-GW/SMS Router) procedure, as defined in steps 1-10 in Figure 5.1.5-1. + +- 2 UDM receives Namf\_EventExposure\_Notify or Nudm\_UECM\_Registration operation from AMF or SMSF indicating that the UE is reachable for SMS delivery; or UDM receives Nudm\_UECM\_Update operation from SMSF indicating that the UE has memory capacity available. +- 3-4 The UDM notifies the "UE\_MEMORY\_AVAILABLE\_FOR\_SMS" or "UE\_REACHABILITY\_FOR\_SMS" event to the SMS-GMSC/IWMSC accordingly. The UDM updates the corresponding reachability flags and deletes the subscription to UE reachability for SMS event created by the SMS-GMSC. +- 5 ServiceCentreAlert as defined in Operation 13 of Figure 20 in TS 23.040 [2]. + +### 5.1.9 Unsuccessful Mobile Terminated short message transfer via SMS Router + +![Sequence diagram for Unsuccessful MT SMS over NAS via SMS Router. Lifelines: SMSF, NRF, SMS Router, UDM, SMS-GMSC, SC. The sequence shows an unsuccessful transfer where the SMS Router returns an error cause at step 5, which propagates back through the chain. The diagram includes 16 numbered steps, with step 9 being a reference to another figure.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant UDM + participant SMS Router + participant NRF + participant SMSF + + Note left of SMSF: 9. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + + SC->>SMS-GMSC: 1. Message Transfer + SMS-GMSC->>NRF: 2a. Nnrf_NFDiscovery_Request + NRF-->>SMS-GMSC: 2b. Nnrf_NFDiscovery_Request Response + SMS-GMSC->>UDM: 3. Nudm_UECM_SendRoutingInfoForSM + UDM->>SMS Router: 4. Nrouter_SMService_RoutingInfo + SMS Router-->>UDM: 5. Nrouter_SMService_RoutingInfo Response (error cause) + UDM-->>SMS-GMSC: 6. Nudm_UECM_SendRoutingInfoForSM Response (error cause) + SMS-GMSC->>SMS Router: 7. Nrouter_SMService_MtForwardSm (SMS body) + SMS Router-->>SMSF: 8. Nsmmf_SMService_MtForwardSm (SMS body) + Note left of SMSF: 9. step 4a -6b of figure 4.13.3.6-1 in 3GPP TS 23.502 [4] + SMSF-->>SMS Router: 10. Nsmmf_SMService_MtForwardSm Response (error cause) + SMS Router-->>SMS-GMSC: 11. Nrouter_SMService_MtForwardSm Response (error cause) + SMS-GMSC->>UDM: 12. Nudm_ReportSMDeliveryStatus_Request + UDM-->>SMS-GMSC: 13. Nudm_ReportSMDeliveryStatus_Request Response + SMS-GMSC->>SC: 14. Failure Report + SMS-GMSC->>UDM: 15. Nudm_EventExposure_Subscribe + UDM-->>SMS-GMSC: 16. Nudm_EventExposure_Subscribe resp + +``` + +Sequence diagram for Unsuccessful MT SMS over NAS via SMS Router. Lifelines: SMSF, NRF, SMS Router, UDM, SMS-GMSC, SC. The sequence shows an unsuccessful transfer where the SMS Router returns an error cause at step 5, which propagates back through the chain. The diagram includes 16 numbered steps, with step 9 being a reference to another figure. + +Figure 5.1.9-1: Unsuccessful MT SMS over NAS via SMS Router + +1. MT SMS interaction between SC and SMS-GMSC follow the current procedure as defined in 3GPP TS 23.040 [2]. +- 2a. SMS-GMSC invokes the Nnrf\_NFDiscovery to discover and select the UDM instance(s), supporting SMS SBI interfaces, and managing the user subscriptions of the GPSI. The SMS-GMSC may need to retrieve the PLMN + +ID of the recipients GPSI before the discovery of the UDM instance based on the GPSI-to-Subscription-Network resolution procedure defined in clause 5.1.7. + +- 2b. If no UDM supporting SMS SBI could be discovered, the NRF indicates so to SMS-GMSC (by not including any UDM instance in the discovery response), and SMS-GMSC shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2], +or if a UDM supporting SMS SBI is discovered and selected, NRF returns the IP addresses or FQDNs of the serving UDM to provide Nudm\_UECM\_SendRoutingInfoForSM service to SMS-GMSC. +3. SMS-GMSC invokes Nudm\_UECM\_SendRoutingInfoForSM (GPSI) to the UDM to get the serving node information for all access types for the UE. +4. The UDM shall check the registration/reachability flags to determine the potential target nodes, e.g. SMSF. For MT SM transfer via SMS Router, the UDM shall invoke the Nrouter\_SMService\_RoutingInfo to provide the SMSF Instance Id to the SMS Router. The address of the SMS Router to be contacted by the UDM may be configured locally. +5. If any failure at this step, the SMS Router shall send Nrouter\_SMService\_RoutingInfo response with error cause to the UDM. +6. If the UDM receives error response from SMS Router in step 5 or UDM is failed after step 3, e.g. user not found in the UDM, the UDM shall respond to the SMS-GMSC by sending Nudm\_UECM\_SendRoutingInfoForSM response with error cause. If there is no target node address registered in the UDM, a response with error case indicating absent subscriber for SM is sent to the SMS-GMSC and the procedure continues in step 15. +7. If successful response is returned in step 6, the SMS-GMSC forwards the SMS message to the SMS Router by invoking Nrouter\_SMService\_MtForwardSm service operation. +8. The SMS Router forwards the SMS message to the SMSF by invoking Nsmmf\_SMService\_MtForwardSm service operation. +9. MT SMS over NAS procedure between SMSF, AMF and UE is same as the definition in step 4a to 6b of Figure 4.13.3.6-1 of 3GPP TS 23.502 [4]. +10. If the AMF informs the SMSF that it cannot deliver the MT-SMS to the UE in step 9, e.g. UE is not reachable, or the SMSF is failed at this step, e.g. memory capacity exceeded, the SMSF shall send the Nsmmf\_SMService\_MtForwardSm response with error cause to the SMS Router. +11. If the SMS Router receives error response from SMSF in step 10 or the SMS Router is failed after step 7, the SMS Router shall send the Nrouter\_SMService\_MtForwardSm response with error cause to the SMS-GMSC. +- 12-13. The SMS-GMSC may report the SM-Delivery Status (e.g. UE is not reachable or memory capacity exceeded) to UDM by invoking Nudm\_ReportSMDeliveryStatus\_Request. +14. If the SMS-GMSC receives error response from SMS Router in step 6 or step 11, the SMS-GMSC sends the failure report to SC as defined in TS 23.040 [2]. +15. The SMS-GMSC subscribes in UDM to be notified when the UE becomes reachable for SMS (i.e. when the UE gets in radio contact with the AMF while an SMSF is actually registered, or when an SMSF gets registered) by using the Nudm\_EventExposure\_Subscribe service operation for Reachability for SMS event as defined in 3GPP TS 23.502 [4]. +16. If applicable, the UDM subscribes to UE reachability notification in the AMF(s) using the Namf\_EventExposure service and sets the relevant reachability flags. The UDM acknowledges the event subscription created by the SMS-GMSC. + +## 5.2 Procedure for SBI-based MO SMS + +### 5.2.1 General + +The procedure for SBI-based MO SMS is showed in Figure 5.2.2-1, which is based on MO SMS procedures in 3GPP TS 23.040 [2] clause 10.2. Compared to procedures in 3GPP TS 23.040 [2], new services are introduced in, including: + +- Niwmsc\_SMService service provided by SMS-IWMSC. + +This new service is registered in NRF, and can be invoked by service consumers. + +### 5.2.2 Procedure for Successful Mobile Originated short message transfer + +![Sequence diagram for successful SBI-based SM MO message transfer. Lifelines: SC, SMS-IWMSC, NRF, SMSF, AMF, UE. The diagram shows the flow of messages from UE to SMSF (steps 1-2), then to NRF for discovery (steps 2a-2b), then to SMS-IWMSC for forwarding (steps 3-5), and finally to SC (step 4). A 'Delivery Report' is shown being sent from SMSF to UE.](c85b57b2414f341860dfc338e1cf2509_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMSF + participant NRF + participant SMS-IWMSC + participant SC + + Note right of SMSF: 1. step 1 -2b of figure 4.13.3.3-1 in 3GPP TS 23.502 [4] + UE->>SMSF: + Note right of SMSF: 2a.Nnrf_NFDiscovery Req + SMSF->>NRF: + Note right of NRF: 2b.Nnrf_NFDiscovery Resp + NRF->>SMSF: + Note right of SMSF: 3.Niwmsc_SMService_MoForwardSm (SMS body) Req + SMSF->>SMS-IWMSC: + Note right of SMS-IWMSC: 4.Msg xter/rpt + SMS-IWMSC->>SC: + Note right of SMS-IWMSC: 5.Niwmsc_SMService_MoForwardSm Resp + SMS-IWMSC->>SMSF: + Note right of SMSF: 6. step 6a -6d of figure 4.13.3.3-1 in 3GPP TS 23.502 [4] + SMSF->>UE: Delivery Report + +``` + +Sequence diagram for successful SBI-based SM MO message transfer. Lifelines: SC, SMS-IWMSC, NRF, SMSF, AMF, UE. The diagram shows the flow of messages from UE to SMSF (steps 1-2), then to NRF for discovery (steps 2a-2b), then to SMS-IWMSC for forwarding (steps 3-5), and finally to SC (step 4). A 'Delivery Report' is shown being sent from SMSF to UE. + +**Figure 5.2.2-1: Procedures for successful SBI-based SM MO message transfer** + +- 0 SMS-IWMSC registers Niwmsc\_SMService service in the NRF, during the NF registration procedure. + - 1 MO SM message transfer from UE to SMSF through AMF follows the current procedure as defined in 3GPP TS 23.040 [2] + - 2a If SMSF knows from local configuration that the target SMS-IWMSC does not support SBI, it shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2], or SMSF invokes the Nnrf\_NFDiscovery to discover and select serving SMS-IWMSC with the parameters of SUPI and/or GPSI and/or location (e.g. TAIs, CGIs, etc.) and/or E.164 address of the SC. + - 2b If no SMS-IWMSC could be discovered, the NRF indicates so to SMSF (by not including any SMS-IWMSC instance in the discovery response), and SMSF shall quit the SBI-based procedure and fallback to legacy (MAP/Diameter) protocol based procedures, as defined in TS 23.040 [2]. +- If a SMS-IWMSC is discovered and selected, NRF returns the IP addresses or FQDNs of the serving SMS-IWMSC to provide Niwmsc\_SMService service to SMSF. +- 3 SMSF sends a Niwmsc\_SMService\_MoForwardSm service request to the URI of serving SMS-IWMSC, which is obtained in step 2b. The payload body of the request shall contain the SM record to be sent, the Service Centre address, the callbackURI for MO SMS Delivery Report, the timer for waiting the MO SMS Delivery Report, and optionally contains the Access Type. + - 4 MO SMS delivery procedure between SMS-IWMSC and SC is the same as the definition in step 4 of Figure 4.13.3.3-1 of 3GPP TS 23.502 [4]. + - 5 SMS-IWMSC sends Niwmsc\_SMService\_MoForwardSm response to deliver the MO SMS delivery report to the URI of serving SMSF, which is obtained in step 3 + +6 MO SMS delivery report procedure between SMSF, AMF and UE is the same as the 3GPP TS 23.502 [4]. + +When no more SMS is to be sent, the procedure for CP-ack and SMS ack is the same as the 3GPP TS 23.502 [4]. + +These procedures are defined in step 6a to 6d of Figure 4.13.3.3-1 of 3GPP TS 23.502 [4]. + +### 5.2.3 Unsuccessful Mobile Originated short message transfer + +Figure 5.2.3-1 depicts procedure for unsuccessful SBI-based SM MO message transfer + +![Sequence diagram for unsuccessful SBI-based SM MO message transfer. Lifelines: SC, SMS-IWMSC, NRF, SMSF, AMF, UE. The process starts with SMS-IWMSC registering with NRF (0. Nnrf_NFManagement_NFRRegister). Then, a callout box indicates steps 1 to 2b from 3GPP TS 23.502 [4] involving SMSF, AMF, and UE. Next, NRF sends discovery requests (2a, 2b) to SMSF. SMSF sends a MoForwardSm request (3) to SMS-IWMSC. SMS-IWMSC responds with an error case response (4). Finally, SMSF sends a failure report (5) to UE. A dashed box labeled 'Failure Report' encloses steps 4 and 5.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant NRF + participant SMSF + participant AMF + participant UE + + Note right of SMSF: 1. step 1 -2b of figure 4.13.3.3-1 in 3GPP TS 23.502 [4] + + SMS-IWMSC->>NRF: 0. Nnrf_NFManagement_NFRRegister + Note right of SMSF: 1. step 1 -2b of figure 4.13.3.3-1 in 3GPP TS 23.502 [4] + NRF->>SMSF: 2a. Nnrf_NFDiscovery Req + SMSF-->>NRF: 2b. Nnrf_NFDiscovery Resp + SMSF->>SMS-IWMSC: 3. Niwmsc_SMService_MoForwardSm (SMS body) Req + Note right of UE: Failure Report + SMS-IWMSC-->>SMSF: 4. Niwmsc_SMService_MoForwardSm (error case) Resp + SMSF->>UE: 5. Failure Report + +``` + +Sequence diagram for unsuccessful SBI-based SM MO message transfer. Lifelines: SC, SMS-IWMSC, NRF, SMSF, AMF, UE. The process starts with SMS-IWMSC registering with NRF (0. Nnrf\_NFManagement\_NFRRegister). Then, a callout box indicates steps 1 to 2b from 3GPP TS 23.502 [4] involving SMSF, AMF, and UE. Next, NRF sends discovery requests (2a, 2b) to SMSF. SMSF sends a MoForwardSm request (3) to SMS-IWMSC. SMS-IWMSC responds with an error case response (4). Finally, SMSF sends a failure report (5) to UE. A dashed box labeled 'Failure Report' encloses steps 4 and 5. + +Figure 5.2.3-1: Procedures for unsuccessful SBI-based SM MO message transfer + +0-3 The same as the procedures in step 0-3 of Figure 5.2.2-1 in clause 5.2.2 + +4 SMS-IWMSC sends Niwmsc\_SMService\_MoForwardSm response with HTTP status code for application errors as defined in Table 5.3.2-1. + +5 Failure report from SMSF to UE, with the error cause code as defined in Table 5.3.2-2. + +SMS-IWMSC indicates the different errors for MO SM transfer in MoForwardSm response according to the different failure scenarios which happened during MO SM transfer. The Application Errors used in Niwmsc\_SMService\_MoForwardSm response are defined in Table 5.3.2-1 below + +Table 5.3.2-1: Application errors + +| Application Error | HTTP status code | Description | +|------------------------------------|---------------------|-----------------------------------------------------------------------------------------| +| SMS_PAYLOAD_MISSING | 400 Bad Request | The expected SMS payload content is missing | +| SMS_PAYLOAD_ERROR | 400 Bad Request | Error exists in the SMS payload content | +| UNKNOWN_SERVICE_CENTRE_ADDR
ESS | 403 Forbidden | The delivery of the MO short message failed because SMS-SC was unknown. | +| SERVICE_CENTRE_CONGESTION | 403 Forbidden | The delivery of the MO short message failed because SMS-SC was in congestion. | +| USER_NOT_SERVICE_CENTER | 403 Forbidden | The delivery of the short message failed because the user didn't belongs to the SMS-SC. | +| FACILITY_NOT_SUPPORTED | 403 Forbidden | The delivery of the MO short message failed because of facility not supported. | +| INVALID_SME_ADDRESS | 403 Forbidden | The delivery of the MO short message failed because the SME address is invalid. | +| UNREACHABLE_SMS_SC | 504 Gateway Timeout | The delivery of the MO short message failed because the response is timeout. | + +If errors are indicated by the SMS-IWMSC, the SMSF shall send a failure report (i.e. a RP-ERROR message) to the UE, with the error cause coded as following mapping between errors indicated by SMS-IWMSC and error cause code in RP-ERROR message: + +**Table 5.3.2-2: Mapping between Application errors and Cause value** + +| Return error from SMS-IWMSC | Cause value in the RP-ERROR message | +|--------------------------------------------------------------------------|--------------------------------------------------------| +| The Response from SMS-IWMSC is timeout
Unspecified 4xx/5xx error code | 38 Network out of order | +| 400 Bad Request with SMS_PAYLOAD_MISSING or
SMS_PAYLOAD_ERROR | 99 Information element non-existent or not implemented | +| 403 Forbidden with FACILITY_NOT_SUPPORTED | 69 Requested facility not implemented | +| 403 Forbidden with
UNKNOWN_SERVICE_CENTRE_ADDRESS | 1 Unassigned number | +| 403 Forbidden with SERVICE_CENTRE_CONGESTION | 42 Congestion | +| 403 Forbidden with USER_NOT_SERVICE_CENTER | 28 Unidentified subscriber | +| 403 Forbidden with INVALID_SME_ADDRESS | 21 Short message transfer rejected | + +NOTE: The coding and the use of the RP-ERROR message is specified in 3GPP TS 24.011 [8]. + +### 5.2.4 MSISDN-less MO SMS message transfer + +The procedure for SBI-based MSISDN-less MO SMS message transfer is depicted in Figure 5.2.4-1, + +![Sequence diagram for MSISDN-less MO SMS message transfer. Lifelines: NRF, UE, SMS-SC, UDM, NEF, AF. The sequence starts with UE registering with NEF (0. Nnrf_NFManagement_NFRegister). Then UE sends MO SMS to SMS-SC (1. MO SMS Delivery). SMS-SC sends discovery request to NRF (2a. Nnrf_NFDiscovery Req) and NRF responds (2b. Nnrf_NFDiscovery Resp). SMS-SC then sends MO Forward Sm request to NEF (3. Nnef_SMService_MoForwardSm (SMS body) Req). NEF sends Get request to UDM (4. Nudm_SDM_Get request (Identifier translation)) and UDM responds (5. Nudm_SDM_Get Response). NEF sends Notify to AF (6. Nnef_MSISDN-less_MO_SMS Notify). NEF sends status response to SMS-SC (7. Nnef_SMService_MoForwardSm (status) Resp). Finally, SMS-SC sends delivery or failure report to UE (8. SMS Delivery or Failure Report).](d8698aacaeead6dfed9a1e448670a2e4_img.jpg) + +Sequence diagram for MSISDN-less MO SMS message transfer. Lifelines: NRF, UE, SMS-SC, UDM, NEF, AF. The sequence starts with UE registering with NEF (0. Nnrf\_NFManagement\_NFRegister). Then UE sends MO SMS to SMS-SC (1. MO SMS Delivery). SMS-SC sends discovery request to NRF (2a. Nnrf\_NFDiscovery Req) and NRF responds (2b. Nnrf\_NFDiscovery Resp). SMS-SC then sends MO Forward Sm request to NEF (3. Nnef\_SMService\_MoForwardSm (SMS body) Req). NEF sends Get request to UDM (4. Nudm\_SDM\_Get request (Identifier translation)) and UDM responds (5. Nudm\_SDM\_Get Response). NEF sends Notify to AF (6. Nnef\_MSISDN-less\_MO\_SMS Notify). NEF sends status response to SMS-SC (7. Nnef\_SMService\_MoForwardSm (status) Resp). Finally, SMS-SC sends delivery or failure report to UE (8. SMS Delivery or Failure Report). + +**Figure 5.2.4-1: Procedures for MSISDN-less MO SMS message transfer** + +- 0 NEF registers Nnef\_SMService\_MoForwardSm service and supporting long/short code ranges in NRF, during the NF registration procedure. +- 1 MO SMS transmit from UE to SMS-SC, as already defined in clause 5.2.2. +- 2a-2b SMS-SC provides destination SME address (long/short code of the AF) to NRF for NEF selection, and chooses Nnef\_SMService\_MoForwardSm service for MSISDN-less MO SMS submit. +- 3 SMS-SC forwards MO SM to NEF, by invoking Nnef\_SMService\_MoForwardSm service. +- 4-5 Nudm\_SDM\_Get and response between NEF and UDM, which refers to Step 3-Step 4 of Figure 4.13.7.2-1 in TS 23.502 [4]. +- 6 The NEF provides a Nnef\_MSISDN-less\_MO\_SMS Notify, which refers to Step 5 of Figure 4.13.7.2-1 in TS 23.502 [4]. +- 7 NEF sends Nnef\_SMService\_MoForwardSm response to SMS-SC, carrying a success or failure delivery indication to SMS-SC. + +- 8 SMS-SC indicates success/failure back to UE using existing SBI-based SMS delivery report defined in clause 6.2.2. + +# 6 Services for SBI-based SMS + +## 6.1 General + +This clause introduces the services for SBI-based SMS. + +## 6.2 UDM services for SBI-based SMS + +### 6.2.1 General + +The following table illustrates the UDM services for SBI-based SMS. + +**Table 6.2.1-1: UDM Services for SBI-based SMS** + +| Service Name | Service Operations | Operation Semantics | Service Provider(s) | Service Consumer(s) | +|------------------------------|-----------------------|---------------------|---------------------|---------------------| +| UE Context Management (UECM) | SendRoutingInfoFor SM | request / response | UDM | SMS-GMSC | +| ReportSMDeliveryStatus | Request | request / response | UDM | SMS-GMSC, IP-SM-GW, | +| EventExposure | Subscribe | subscribe / notify | UDM | SMS-GMSC | + +### 6.2.2 Nudm\_ReportSMDeliveryStatus service + +#### 6.2.2.1 General + +For the Nudm\_ReportSMDeliveryStatus service the following service operations are defined: + +- Request + +#### 6.2.2.2 Nudm\_ReportSMDeliveryStatus\_Request service operation + +**Service operation name:** Nudm\_ReportSMDeliveryStatus\_Request + +**Description:** reports the SM-Delivery Status to UDM. + +**Inputs, Required:** GPSI, SM-Delivery status + +**Inputs, Optional:** None. + +**Outputs, Required:** report SM-Delivery status result. + +**Outputs, Optional:** None. + +### 6.2.3 Nudm\_EventExposure service + +**Service Description:** This service is defined in clause 5.2.3.5 of 3GPP TS 23.502 [4], in addition, this clause defines the enhancement of Nudm\_EventExposure for alert sc. + +Except the existing events that are exposed by UDM, events "UE\_MEMORY\_AVAILABLE\_FOR\_SMS" and "UE\_REACHABILITY\_FOR\_SMS" should be supported. + +### 6.2.4 Nudm\_UECM service + +**Service Description:** This service is defined in clause 5.2.3.2 of 3GPP TS 23.502 [4], in addition, this clause defines the enhancement of Nudm\_UECM service. + +The new service operation SendRoutingInfoForSM shall be supported to get the target valid node(s) serving the UE from the UDM, which will be used by the SMS-GMSC to deliver the MT SMS. + +## 6.3 SMS-IWMSC services for SBI-based SMS + +### 6.3.1 General + +The following table illustrates the SMS-IWMSC services for SBI-based SMS. + +**Table 6.3.1-1: SMS-IWMSC Services for SBI-based SMS** + +| Service Name | Service Operations | Operation Semantics | Service Provider(s) | Service Consumer(s) | +|--------------|--------------------|---------------------|---------------------|---------------------| +| SMService | MoForwardSm | request / response | SMS-IWMSC | SMSF | + +### 6.3.2 Niwmsc\_SMService service + +#### 6.3.2.1 General + +**Service Description:** This service can be used for SBI-based MO SM transfer and Delivery Report through SMS-IWMSC. + +#### 6.3.2.2 Niwmsc\_SMService\_MoForwardSm service operation + +**Service operation name:** Niwmsc\_SMService\_MoForwardSm. + +**Description:** Service request from consumer to SMS-IWMSC for MO SM transmit. + +**Inputs, Required:** the SM record to be sent, the Service Centre address, the callbackURI for MO SMS Delivery Report, the timer for waiting MO SMS Delivery Report. + +**Inputs, Optional:** Access Type. + +**Outputs, Required:** On success, Delivery Report should be returned. + +On failure or redirection, the appropriate HTTP status code (e.g. "403 Forbidden", "504 Gateway Timeout") indicating the error shall be returned. + +**Outputs, Optional:** None. + +## 6.4 SMSF services for SBI-based SMS + +### 6.4.1 General + +The following table illustrates the SMSF services for SBI-based SMS. + +**Table 6.4.1-1: SMSF Services for SBI-based SMS** + +| Service Name | Service Operations | Operation Semantics | Service Provider(s) | Service Consumer(s) | +|--------------|--------------------|---------------------|---------------------|--------------------------------------| +| SMService | MtForwardSm | request / response | SMSF | SMS-GMSC,
IP-SM-GW,
SMS Router | + +### 6.4.2 Nsmf\_SMService service + +#### 6.4.2.1 General + +**Service Description:** This service can be used for SBI-based MT SM transfer through SMSF. + +#### 6.4.2.2 Nsmmf\_SMService\_MtForwardSm service operation + +**Service operation name:** Nsmmf\_SMService\_MtForwardSm + +**Description:** transfer downlink SMS message from consumer NF to SMSF. + +**Inputs, Required:** GPSI, SMS payload + +**Inputs, Optional:** None. + +**Outputs, Required:** SMS message transmission result. + +**Outputs, Optional:** None. + +## 6.5 IP-SM-GW services for SBI-based SMS + +### 6.5.1 General + +The following table illustrates the IP-SM-GW services for SBI-based SMS. + +**Table 6.5.1-1: IP-SM-GW Services for SBI-based SMS** + +| Service Name | Service Operations | Operation Semantics | Service Provider(s) | Service Consumer(s) | +|--------------|--------------------|---------------------|---------------------|---------------------| +| SMService | RoutingInfo | request / response | IP-SM-GW | UDM | +| | MtForwardSm | request / response | IP-SM-GW | SMS-GMSC | + +### 6.5.2 Nipsmgw\_SMService service + +#### 6.5.2.1 General + +**Service Description:** This service can be used for SBI-based MT SM transfer through IP-SM-GW. + +#### 6.5.2.2 Nipsmgw\_SMService\_RoutingInfo service operation + +**Service operation name:** Nipsmgw\_SMService\_RoutingInfo + +**Description:** provides the SMSF Instance Id to the IP-SM-GW. + +**Inputs, Required:** GPSI, SMSF Instance Id. + +**Inputs, Optional:** None. + +**Outputs, Required:** Result. + +**Outputs, Optional:** None. + +#### 6.5.2.3 Nipsmgw\_SMService\_MtForwardSm service operation + +**Service operation name:** Nipsmgw\_SMService\_MtForwardSm + +**Description:** transfer downlink SMS message from consumer NF to IP-SM-GW and return the MT SMS Delivery Report to the consumer NF. + +**Inputs, Required:** GPSI, SMS payload + +**Inputs, Optional:** None. + +**Outputs, Required:** MT SMS Delivery Report. + +**Outputs, Optional:** None. + +## 6.6 SMS Router services for SBI-based SMS + +### 6.6.1 General + +The following table illustrates the SMS Router services for SBI-based SMS. + +**Table 6.6.1-1: SMS Router Services for SBI-based SMS** + +| Service Name | Service Operations | Operation Semantics | Service Provider(s) | Service Consumer(s) | +|--------------|--------------------|---------------------|---------------------|---------------------| +| SMService | RoutingInfo | request / response | SMS Router | UDM | +| | MtForwardSm | request / response | SMS Router | SMS-GMSC | + +### 6.6.2 Nrouter\_SMService service + +#### 6.6.2.1 General + +**Service Description:** This service can be used for SBI-based MT SM transfer through SMS Router. + +#### 6.6.2.2 Nrouter\_SMService\_RoutingInfo service operation + +**Service operation name:** Nrouter\_SMService\_RoutingInfo + +**Description:** provides the SMSF Instance Id to the SMS Router. + +**Inputs, Required:** GPSI, SMSF Instance Id. + +**Inputs, Optional:** None. + +**Outputs, Required:** Result. + +**Outputs, Optional:** None. + +#### 6.6.2.3 Nrouter\_SMService\_MtForwardSm service operation + +**Service operation name:** Nrouter\_SMService\_MtForwardSm + +**Description:** transfer downlink SMS message from consumer NF to SMS Router and return the MT SMS Delivery Report to the consumer NF. + +**Inputs, Required:** GPSI, SMS payload + +**Inputs, Optional:** None. + +**Outputs, Required:** MT SMS Delivery Report. + +**Outputs, Optional:** None. + +## 6.7 MNPF services for SBI-based SMS + +### 6.7.1 General + +The following table illustrates the MNPF services for SBI-based SMS. + +**Table 6.7.1-1: MNPF Services for SBI-based SMS** + +| Service Name | Service Operations | Operation Semantics | Service Provider(s) | Service Consumer(s) | +|--------------|--------------------|---------------------|---------------------|---------------------| +| NPStatus | Get | request / response | MNPF | SMS-GMSC, SCP | + +### 6.7.2 Nmnpf\_NPStatus service + +#### 6.7.2.1 General + +**Service Description:** This service can be used to retrieve the PLMN ID of the Subscription Network of a GPSI. + +#### 6.7.2.2 Nmnpf\_NPStatus\_Get service operation + +**Service operation name:** Nmnpf\_NPStatus\_Get + +**Description:** retrieve the PLMN ID of the Subscription Network of a GPSI. + +**Inputs, Required:** GPSI. + +**Inputs, Optional:** None. + +**Outputs, Required:** PLMN Id. + +**Outputs, Optional:** None. + +## 6.8 NEF services for SBI-based SMS + +### 6.8.1 General + +The following table illustrates the NEF services for SBI-based SMS. + +**Table 6.8.1-1: NEF Services for SBI-based SMS** + +| Service Name | Service Operations | Operation Semantics | Service Provider(s) | Service Consumer(s) | +|--------------|--------------------|---------------------|---------------------|---------------------| +| SMService | MoForwardSm | request / response | NEF | SMS-SC | + +### 6.8.2 Nnef\_SMService service + +#### 6.8.2.1 General + +This service can be used for SBI-based MO SM transfer through NEF for MSISDN-less MO SMS. + +#### 6.8.2.2 Nnef\_SMService\_MoForwardSm service operation + +**Service operation name:** Nnef\_SMService\_MoForwardSm + +**Description:** transmit MO SMS message from consumer NF to NEF. + +**Inputs, Required:** SMS payload, Application port ID, SUPI, destination SME address (long/short code of the AF). + +**Inputs, Optional:** None. + +**Outputs, Required:** SMS message transmission result. + +**Outputs, Optional:** None. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2021-10 | CT4#106e | C4-215046 | | | | C4-215046 as basis | | 0.1.0 | +| 2021-10 | CT4#106e | C4-215513 | | | | Implementation of C4-215417, C4-215418, C4-215453 and C4-215454 in CT4#106e | | 0.2.0 | +| 2021-12 | CT4#107e | C4-216466 | | | | Implementation of C4-216442, C4-216443, C4-216444 and C4-216546 in CT4#107e | | 0.3.0 | +| 2022-01 | CT4#107bis-e | C4-220540 | | | | Implementation of C4-220029, C4-220341, C4-220374, C4-220408 and C4-220409 in CT4#107bis-e | | 0.4.0 | +| 2022-02 | CT4#108e | C4-221588 | | | | Implementation of C4-221438, C4-221573, C4-221595 and C4-221692 in CT4#108e | | 0.5.0 | +| 2022-04 | CT4#109e | C4-222340 | | | | Implementation of C4-222229, C4-222271, C4-222301, C4-222329, C4-222330, C4-222394, C4-222395, C4-222396, C4-222397 and C4-222418 in CT4#109e | | 0.6.0 | +| 2022-05 | CT4#110e | C4-223449 | | | | Implementation of C4-223277, C4-223342 and C4-223358 in CT4#110e | | 0.7.0 | +| 2022-06 | CT#96 | CP-221077 | | | | TS for information and approval | | 1.0.0 | +| 2022-06 | CT#96 | CP-221077 | | | | TS approved in CT#96 | | 17.0.0 | +| 2022-09 | CT#97e | CP-222027 | 0001 | - | B | TS 23.540 Alignment of MNPF | | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0002 | - | B | Add NEF and MNPF in SBI-based SMS system architecture | | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0003 | - | F | Description of the Alert procedure | | 17.1.0 | +| 2022-09 | CT#97e | CP-222027 | 0004 | - | F | Correction on Operation Semantic of UDM service | | 17.1.0 | +| 2023-06 | CT#100 | CP-221072 | 0010 | - | F | Indication of Memory Available from SMSF as trigger for the Alert procedure | | 17.2.0 | +| 2023-06 | CT#100 | CP-221039 | 0008 | 1 | D | Editorial correction in TS 23.540 | | 18.0.0 | +| 2023-06 | CT#100 | CP-221039 | 0009 | 1 | B | MO SM delivery application error codes alignment | | 18.0.0 | +| 2023-09 | CT#101 | CP-232039 | 0013 | 1 | B | Compatibility of UDM not supporting SMS SBI | | 18.1.0 | +| 2023-09 | CT#101 | CP-232066 | 0012 | 1 | A | Alignment of MNPF in Rel-18 TS 23.540 | | 18.1.0 | +| 2023-09 | CT#101 | CP-232066 | 0015 | - | A | GPSI to subscription network resolution procedure using NRF | | 18.1.0 | +| 2023-12 | CT#102 | CP-233034 | 0016 | - | F | Modify of the description of MO SMS fallback to legacy way | | 18.2.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23548/raw.md b/raw/rel-18/23_series/23548/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0b6787c30c5d7733bf82594658b56f30a665faf7 --- /dev/null +++ b/raw/rel-18/23_series/23548/raw.md @@ -0,0 +1,3150 @@ + + +# 3GPP TS 23.548 V18.4.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G System Enhancements for Edge Computing; Stage 2 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized font with a red signal wave icon below the 'G', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Reference Architecture and Connectivity Models ..... | 8 | +| 4.1 General ..... | 8 | +| 4.2 Reference Architecture for Supporting Edge Computing ..... | 8 | +| 4.3 Connectivity Models ..... | 10 | +| 5 Functional Description for Supporting Edge Computing ..... | 11 | +| 5.1 EASDF ..... | 11 | +| 5.1.1 Functional Description ..... | 11 | +| 5.1.2 EASDF Discovery and Selection ..... | 12 | +| 5.2 Edge DNS Client (EDC) Functionality..... | 12 | +| 5.2.1 Functional Description ..... | 12 | +| 6 Procedures for Supporting Edge Computing ..... | 13 | +| 6.1 General ..... | 13 | +| 6.2 EAS Discovery and Re-discovery..... | 13 | +| 6.2.1 General ..... | 13 | +| 6.2.2 EAS (Re-)discovery over Distributed Anchor Connectivity Model ..... | 15 | +| 6.2.2.1 General..... | 15 | +| 6.2.2.2 EAS Discovery Procedure ..... | 15 | +| 6.2.2.3 EAS Re-discovery Procedure at Edge Relocation..... | 15 | +| 6.2.2.4 Procedure for EAS Discovery with Dynamic PSA Distribution ..... | 16 | +| 6.2.3 EAS (Re-)discovery over Session Breakout Connectivity Model..... | 18 | +| 6.2.3.1 General..... | 18 | +| 6.2.3.2 EAS Discovery Procedure ..... | 18 | +| 6.2.3.2.1 General ..... | 18 | +| 6.2.3.2.2 EAS Discovery Procedure with EASDF ..... | 18 | +| 6.2.3.2.3 EAS Discovery Procedure with Local DNS Server/Resolver..... | 25 | +| 6.2.3.2.4 Select common DNAI with Local DNS Server/Resolver for a set of UEs ..... | 27 | +| 6.2.3.2.5 Common EAS discovery for a set of UEs..... | 28 | +| 6.2.3.2.6 EAS discovery corresponding to Common DNAI for a set of UEs..... | 30 | +| 6.2.3.2.7 Coordination among SMFs for Common EAS/DNAI determination..... | 31 | +| 6.2.3.3 EAS Re-discovery Procedure at Edge Relocation..... | 32 | +| 6.2.3.4 EAS Deployment Information Management ..... | 33 | +| 6.2.3.4.1 General ..... | 33 | +| 6.2.3.4.2 EAS Deployment Information Provision from AF via NEF..... | 34 | +| 6.2.3.4.3 EAS Deployment Information Management in the SMF..... | 35 | +| 6.2.3.4.4 BaselineDNSPattern Management in the EASDF ..... | 36 | +| 6.2.4 EDC Functionality based DNS Query to reach EASDF/DNS Resolver/DNS Server indicated by the SMF ..... | 36 | +| 6.3 Edge Relocation ..... | 37 | +| 6.3.1 General ..... | 37 | +| 6.3.2 Edge Relocation Involving AF Change..... | 37 | +| 6.3.3 Edge Relocation Using EAS IP Replacement..... | 38 | +| 6.3.3.1 EAS IP Replacement Procedures..... | 38 | +| 6.3.3.1.1 Enabling EAS IP Replacement Procedure by AF ..... | 38 | +| 6.3.3.1.2 EAS IP Replacement Update upon DNAI and EAS IP Change ..... | 40 | +| 6.3.3.1.3 Disabling EAS IP Replacement Procedure ..... | 40 | +| 6.3.3.2 Enhancement to AF Influence ..... | 41 | +| 6.3.4 AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation..... | 41 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------|----| +| 6.3.5 | Packet Buffering for Low Packet Loss..... | 42 | +| 6.3.6 | Edge Relocation Considering User Plane Latency Requirement..... | 43 | +| 6.3.7 | Edge Relocation Triggered by AF..... | 44 | +| 6.4 | Network Exposure to Edge Application Server ..... | 44 | +| 6.4.1 | General ..... | 44 | +| 6.4.2 | Network Exposure to Edge Application Server ..... | 44 | +| 6.4.2.1 | Usage of Nupf_EventExposure to Report QoS Monitoring results..... | 44 | +| 6.4.2.2 | Local NEF Discovery ..... | 47 | +| 6.5 | Support of 3GPP Application Layer Architecture for Enabling Edge Computing ..... | 47 | +| 6.5.1 | General ..... | 47 | +| 6.5.2 | ECS Address Provisioning ..... | 48 | +| 6.5.2.1 | ECS Address Configuration Information ..... | 48 | +| 6.5.2.2 | ECS Address Configuration Information Provisioning to the UE..... | 48 | +| 6.5.2.3 | ECS Address Provisioning by a 3rd Party AF ..... | 49 | +| 6.5.2.4 | ECS Address Provisioning by MNO ..... | 49 | +| 6.5.2.5 | Interworking with EPC ..... | 49 | +| 6.5.2.6 | ECS Address Provisioning in Roaming..... | 49 | +| 6.5.2.6.1 | General ..... | 49 | +| 6.5.2.6.2 | ECS Address Configuration Information Provision from AF via NEF in VPLMN ..... | 50 | +| 6.5.2.6.3 | ECS Address Configuration Information Provision to the SMF in VPLMN ..... | 50 | +| 6.6 | Support of AF Guidance to PCF Determination of Proper URSP Rules ..... | 51 | +| 6.7 | Support of the local traffic routing in VPLMN for Home Routed PDU Session for roaming (HR-SBO) ..... | 52 | +| 6.7.1 | General ..... | 52 | +| 6.7.2 | Procedure..... | 52 | +| 6.7.2.1 | General..... | 52 | +| 6.7.2.2 | PDU Session establishment for supporting HR-SBO in VPLMN..... | 53 | +| 6.7.2.3 | EAS Discovery Procedure with V-EASDF for HR-SBO..... | 56 | +| 6.7.2.4 | EAS Discovery Procedure with Local DNS for HR-SBO..... | 57 | +| 6.7.2.5 | EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO..... | 58 | +| 6.7.2.6 | N2 Handover with V-SMF insertion/change/removal in HR-SBO case ..... | 60 | +| 6.7.2.7 | Inter V-SMF mobility registration update procedure in HR-SBO case..... | 64 | +| 6.7.2.8 | N2 Handover without V-SMF change in HR-SBO case ..... | 67 | +| 6.7.2.9 | Xn Handover with V-SMF change in HR-SBO case ..... | 67 | +| 6.7.2.10 | Xn Handover without V-SMF change in HR-SBO case ..... | 69 | +| 6.7.3 | EAS Re-discovery and Edge Relocation Procedure..... | 69 | +| 6.7.3.1 | General..... | 69 | +| 6.7.3.2 | Network triggered EAS change in HR-SBO context..... | 69 | +| 6.7.4 | AF request on PDU Sessions supporting HR-SBO ..... | 71 | +| 6.8 | Support for mapping between EAS address Information and DNAI..... | 71 | +| 6.8.1 | General ..... | 71 | +| 6.8.2 | AF request for DNAI Procedures ..... | 72 | +| 7 | Network Function Services and Descriptions..... | 73 | +| 7.1 | EASDF Services..... | 73 | +| 7.1.1 | General ..... | 73 | +| 7.1.2 | Neasdf_DNSContext Service ..... | 73 | +| 7.1.2.1 | General..... | 73 | +| 7.1.2.2 | Neasdf_DNSContext_Create Service Operation..... | 73 | +| 7.1.2.3 | Neasdf_DNSContext_Update Service Operation..... | 73 | +| 7.1.2.4 | Neasdf_DNSContext_Delete Service Operation..... | 74 | +| 7.1.2.5 | Neasdf_DNSContext_Notify Service Operation..... | 74 | +| 7.1.3 | Neasdf_BaselineDNSPattern Service..... | 74 | +| 7.1.3.1 | General..... | 74 | +| 7.1.3.2 | Neasdf_BaselineDNSPattern_Create Service Operation..... | 74 | +| 7.1.3.3 | Neasdf_BaselineDNSPattern_Update Service Operation ..... | 75 | +| 7.1.3.4 | Neasdf_BaselineDNSPattern_Delete Service Operation..... | 75 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------------|-----------| +| Annex A (Informative): | EAS Discovery Using 3rd Party Mechanisms..... | 76 | +| Annex B (Informative): | Application Layer based EAS (Re-)Direction ..... | 77 | +| Annex C (Informative): | Considerations for EAS (re)Discovery ..... | 78 | +| C.1 | General..... | 78 | +| C.2 | Impact of IP Addresses for DNS Resolver on UE ..... | 78 | +| C.3 | UE Considerations for EAS Re-discovery..... | 78 | +| C.4 | UE Procedures for Session Breakout..... | 79 | +| C.5 | Split-UE Considerations for EAS (Re-)discovery ..... | 79 | +| C.6 | Detection of UE not using 5GC provided DNS server ..... | 79 | +| Annex D (Informative): | Examples of AF Guidance to PCF for Determination of URSP Rules..... | 81 | +| Annex E (informative): | EPS Interworking Considerations..... | 82 | +| E.1 | General..... | 82 | +| E.2 | Distributed Anchor..... | 82 | +| E.3 | Multiple Sessions ..... | 82 | +| E.4 | Session Breakout..... | 82 | +| Annex F (Informative): | EAS Relocation on Simultaneous Connectivity over Source and Target PSA..... | 83 | +| Annex G (Informative): | Change history..... | 86 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document defines the Stage 2 specifications for enhancements of 5G System to support Edge Computing. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [5] 3GPP TS 23.558: "Architecture for enabling Edge Applications (EA)". +- [6] IETF RFC 7871: "Client Subnet in DNS Queries". +- [7] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [8] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3". +- [9] 3GPP TS 29.500: "Technical Realization of Service Based Architecture; Stage 3". +- [10] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [11] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [12] 3GPP TS 33.501: "Security architecture and procedures for 5G System". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1], TS 23.501 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] and TS 23.501 [2]. + +**Central DNS resolver/server:** A DNS resolver/server centrally deployed by the 5GC operator or 3rd party and is responsible for resolving the UE DNS Queries into suitable Edge Application Server (EAS) IP address(es). + +**Edge Application Server:** An Application Server resident in the Edge Hosting Environment. + +**Edge Hosting Environment:** An environment providing support required for Edge Application Server's execution. + +**Local part of DN:** The set of network entities of a DN that are deployed locally. The local access to the DN provides access to the local part of DN. + +**Local DNS resolver/server:** A DNS resolver/server that may be locally deployed by 5GC operator or 3rd parties within the Local DN, and is responsible for resolving UE DNS Queries into suitable EAS IP address(es) within the local DN. The L-DNS resolvers/servers may or may not have connectivity with C-DNS depending on the deployment. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1] and TS 23.501 [2]. + +| | | +|-----------|--------------------------------------------| +| C-DNS | Central DNS | +| C-NEF | Central NEF | +| C-PSA UPF | Central PSA UPF | +| EAS | Edge Application Server | +| EASDF | Edge Application Server Discovery Function | +| ECS | Edge Configuration Server | +| EDC | Edge DNS Client | +| EEC | Edge Enabler Client | +| EES | Edge Enabler Server | +| EHE | Edge Hosting Environment | +| L-DN | Local part of DN | +| L-DNS | Local DNS | +| L-NEF | Local NEF | +| L-PSA UPF | Local PSA UPF | +| HR-SBO | Home Routed Session BreakOut | + +# --- 4 Reference Architecture and Connectivity Models + +## 4.1 General + +Edge Computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. + +5GS supports Edge Hosting Environment (EHE) deployed in the DN beyond the PSA UPF. An EHE may be under the control of either the operator or 3rd parties. + +The Edge Computing features defined in this specification are applicable to PLMN(s) and to SNPN(s). + +The Local part of the DN in which EHE is deployed may have user plane connectivity with both a centrally deployed PSA and locally deployed PSA of same DNN. Edge Computing enablers as described in clause 5.13 of TS 23.501 [2], e.g. local routing and traffic steering, session and service continuity, AF influenced traffic routing, are leveraged in this specification. + +Edge Computing in the serving network (e.g. for Local Break Out roaming scenario in case of PLMN access) is supported, but for AF guidance to PCF determination of URSP rules, the Serving network (e.g. VPLMN or serving SNPN) has no control on URSP, so cannot influence UE in selecting a specific Edge Computing related DNN and S-NSSAI. + +## 4.2 Reference Architecture for Supporting Edge Computing + +The reference architectures for supporting Edge Computing are based on the reference architectures specified in clause 4.2 of TS 23.501 [2]. The following reference architectures for non-roaming, LBO roaming and HR with Session Breakout (HR-SBO) roaming scenarios further depict the relationship between the 5GS and a DN where Edge Application Servers (EASs) are deployed in an EHE. + +Figure 4.2-1 depicts 5GS architecture for non-roaming scenario supporting Edge Computing with UL CL/BP. + +![Figure 4.2-1: 5GS providing access to EAS with UL CL/BP for non-roaming scenario. This diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, PCF, AF, and UDM via the Service Based Interface (SBI). The AMF is also connected to a UPF (UL CL/BP) via the N3 interface. The UPF (UL CL/BP) is connected to another UPF (C-PSA) via the N9 interface. The UPF (C-PSA) is connected to a DN via the N6 interface. The UPF (UL CL/BP) is also connected to a UPF (L-PSA) via the N4 interface. The UPF (L-PSA) is connected to an EAS (Local part of DN) via the N6 interface. The SMF is connected to the AMF via the N4 interface and to the UPF (UL CL/BP) via the N4 interface. The SMF is also connected to the NRF, PCF, AF, and UDM via the SBI. The NEF and EASDF are connected to the SBI via the Nnef and Neasdf interfaces respectively.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +Figure 4.2-1: 5GS providing access to EAS with UL CL/BP for non-roaming scenario. This diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, PCF, AF, and UDM via the Service Based Interface (SBI). The AMF is also connected to a UPF (UL CL/BP) via the N3 interface. The UPF (UL CL/BP) is connected to another UPF (C-PSA) via the N9 interface. The UPF (C-PSA) is connected to a DN via the N6 interface. The UPF (UL CL/BP) is also connected to a UPF (L-PSA) via the N4 interface. The UPF (L-PSA) is connected to an EAS (Local part of DN) via the N6 interface. The SMF is connected to the AMF via the N4 interface and to the UPF (UL CL/BP) via the N4 interface. The SMF is also connected to the NRF, PCF, AF, and UDM via the SBI. The NEF and EASDF are connected to the SBI via the Nnef and Neasdf interfaces respectively. + +Figure 4.2-1: 5GS providing access to EAS with UL CL/BP for non-roaming scenario + +Figure 4.2-2 depicts 5GS architecture for non-roaming scenario supporting Edge Computing without UL CL/BP. + +![Figure 4.2-2: 5GS providing access to EAS without UL CL/BP for non-roaming scenario. This diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, PCF, AF, and UDM via the SBI. The AMF is also connected to a UPF (PSA) via the N3 interface. The UPF (PSA) is connected to an EAS (Local part of DN) via the N6 interface. The SMF is connected to the AMF via the N4 interface and to the UPF (PSA) via the N4 interface. The SMF is also connected to the NRF, PCF, AF, and UDM via the SBI. The NEF and EASDF are connected to the SBI via the Nnef and Neasdf interfaces respectively.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Figure 4.2-2: 5GS providing access to EAS without UL CL/BP for non-roaming scenario. This diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, PCF, AF, and UDM via the SBI. The AMF is also connected to a UPF (PSA) via the N3 interface. The UPF (PSA) is connected to an EAS (Local part of DN) via the N6 interface. The SMF is connected to the AMF via the N4 interface and to the UPF (PSA) via the N4 interface. The SMF is also connected to the NRF, PCF, AF, and UDM via the SBI. The NEF and EASDF are connected to the SBI via the Nnef and Neasdf interfaces respectively. + +Figure 4.2-2: 5GS providing access to EAS without UL CL/BP for non-roaming scenario + +Figure 4.2-3 depicts 5GS architecture for LBO roaming scenario supporting Edge Computing with UL CL/BP. + +![Figure 4.2-3: 5GS providing access to EAS with UL CL/BP for LBO roaming scenario. This diagram is split into two parts by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. In the VPLMN, a UE is connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, PCF, AF, and UDM via the SBI. The AMF is also connected to a UPF (UL CL/BP) via the N3 interface. The UPF (UL CL/BP) is connected to another UPF (C-PSA) via the N9 interface. The UPF (C-PSA) is connected to a DN via the N6 interface. The UPF (UL CL/BP) is also connected to a UPF (L-PSA) via the N4 interface. The UPF (L-PSA) is connected to an EAS (Local part of DN) via the N6 interface. The SMF is connected to the AMF via the N4 interface and to the UPF (UL CL/BP) via the N4 interface. The SMF is also connected to the NRF, PCF, AF, and UDM via the SBI. The NEF and EASDF are connected to the SBI via the Nnef and Neasdf interfaces respectively. In the HPLMN, there is a PCF and a UDM connected to each other. The UDM is connected to the SBI via the Nudm interface.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +Figure 4.2-3: 5GS providing access to EAS with UL CL/BP for LBO roaming scenario. This diagram is split into two parts by a vertical dashed line: VPLMN (Visited PLMN) on the left and HPLMN (Home PLMN) on the right. In the VPLMN, a UE is connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, PCF, AF, and UDM via the SBI. The AMF is also connected to a UPF (UL CL/BP) via the N3 interface. The UPF (UL CL/BP) is connected to another UPF (C-PSA) via the N9 interface. The UPF (C-PSA) is connected to a DN via the N6 interface. The UPF (UL CL/BP) is also connected to a UPF (L-PSA) via the N4 interface. The UPF (L-PSA) is connected to an EAS (Local part of DN) via the N6 interface. The SMF is connected to the AMF via the N4 interface and to the UPF (UL CL/BP) via the N4 interface. The SMF is also connected to the NRF, PCF, AF, and UDM via the SBI. The NEF and EASDF are connected to the SBI via the Nnef and Neasdf interfaces respectively. In the HPLMN, there is a PCF and a UDM connected to each other. The UDM is connected to the SBI via the Nudm interface. + +Figure 4.2-3: 5GS providing access to EAS with UL CL/BP for LBO roaming scenario + +Figure 4.2-4 depicts 5GS architecture for LBO roaming scenario supporting Edge Computing without UL CL/BP. + +![Figure 4.2-4: 5GS providing access to EAS without UL CL/BP for LBO roaming scenario. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, a PCF, and an AF. The AMF is also connected to an SMF, which is connected to a UPF (PSA). The UPF (PSA) is connected to an EAS (Local part of DN). The EAS is connected to an EASDF. The EASDF is connected to a PCF and a UDM. The diagram is split into VPLMN and HPLMN domains by a dashed line. The VPLMN domain contains the UE, AN, AMF, NRF, PCF, AF, SMF, UPF (PSA), and EAS (Local part of DN). The HPLMN domain contains the PCF and UDM.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +Figure 4.2-4: 5GS providing access to EAS without UL CL/BP for LBO roaming scenario. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, a PCF, and an AF. The AMF is also connected to an SMF, which is connected to a UPF (PSA). The UPF (PSA) is connected to an EAS (Local part of DN). The EAS is connected to an EASDF. The EASDF is connected to a PCF and a UDM. The diagram is split into VPLMN and HPLMN domains by a dashed line. The VPLMN domain contains the UE, AN, AMF, NRF, PCF, AF, SMF, UPF (PSA), and EAS (Local part of DN). The HPLMN domain contains the PCF and UDM. + +**Figure 4.2-4: 5GS providing access to EAS without UL CL/BP for LBO roaming scenario** + +Figure 4.2-5 depicts 5GS architecture for HR-SBO roaming scenario supporting Edge Computing with UL CL/BP. + +![Figure 4.2-5: 5GS providing access to EAS with UL CL/BP for HR-SBO roaming scenario. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, a PCF, and an AF. The AMF is also connected to an SMF, which is connected to a UPF (ULCL/BP). The UPF (ULCL/BP) is connected to an EAS (Local part of DN) via a UPF (L-PSA). The UPF (ULCL/BP) is also connected to a DN via a UPF. The diagram is split into VPLMN and HPLMN domains by a dashed line. The VPLMN domain contains the UE, AN, AMF, NRF, PCF, AF, SMF, UPF (ULCL/BP), UPF (L-PSA), and EAS (Local part of DN). The HPLMN domain contains the PCF, UDM, SMF, and UPF.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +Figure 4.2-5: 5GS providing access to EAS with UL CL/BP for HR-SBO roaming scenario. The diagram shows a UE connected to an AN, which is connected to an AMF. The AMF is connected to an NRF, a PCF, and an AF. The AMF is also connected to an SMF, which is connected to a UPF (ULCL/BP). The UPF (ULCL/BP) is connected to an EAS (Local part of DN) via a UPF (L-PSA). The UPF (ULCL/BP) is also connected to a DN via a UPF. The diagram is split into VPLMN and HPLMN domains by a dashed line. The VPLMN domain contains the UE, AN, AMF, NRF, PCF, AF, SMF, UPF (ULCL/BP), UPF (L-PSA), and EAS (Local part of DN). The HPLMN domain contains the PCF, UDM, SMF, and UPF. + +**Figure 4.2-5: 5GS providing access to EAS with UL CL/BP for HR-SBO roaming scenario** + +NOTE 1: Only some of the 5GS NFs are shown in the above reference architecture figures. In the above figures, the split between the UPF acting as UL CL/BP and the UPF acting as local PSA is illustrative. + +NOTE 2: Only the control plane of EASDF is depicted in the figure, the user plane between the EASDF and the UPF (i.e. over which the DNS messages are exchanged) is part of N6. Additionally, the EASDF may have direct connectivity with the local parts of one or more Data Networks. + +NOTE 3: For the HR-SBO roaming scenario, there can be other UPF(s) located in VPLMN between the UPF acting UL CL/BP and the UPF acting as remote PSA in HPLMN. + +## 4.3 Connectivity Models + +5GC supports the following connectivity models to enable Edge Computing: + +- Distributed Anchor Point: For a PDU Session, the PSA UPF is in a local site, i.e. close to the UE location. The PSA UPF may be changed e.g. due to UE mobility and using SSC mode 2 or 3. +- Session Breakout: A PDU Session has a PSA UPF in a central site (C-PSA UPF) and one or more PSA UPF in the local site (L-PSA UPF). The C-PSA UPF provides the IP Anchor Point when UL Classifier is used. The + +Edge Computing application traffic is selectively diverted to the L-PSA UPF using UL Classifier or multi-homing Branching Point mechanisms. The L-PSA UPF may be changed due to e.g. UE mobility. + +- Multiple PDU Sessions: Edge Computing applications use PDU Session(s) with a PSA UPF(s) in local site(s). The rest of applications use PDU Session(s) with PSA UPF(s) in the central site(s). Any PSA UPF may be changed due to e.g. UE mobility and using SSC mode 3 with multiple PDU Sessions. + +URSP rules, for steering the mapping between UE applications and PDU Sessions, can be used for any connectivity model and they are required for the Multiple PDU Sessions model. + +These three connectivity models are illustrated in Figure 4.3-1: + +![Figure 4.3-1: 5GC Connectivity Models for Edge Computing. The diagram shows three connectivity models: Distributed Anchor Point, Session Breakout, and Multiple PDU Sessions. Each model shows a UE connected to a Radio Site, which is connected to a Local Site (containing a UPF), which is connected to a Central Site (containing a UPF), which is connected to a DN. In the Distributed Anchor Point model, the UE is connected to the Local Site UPF. In the Session Breakout model, the UE is connected to the Local Site UPF, and the Local Site UPF is connected to the Central Site UPF. In the Multiple PDU Sessions model, the UE is connected to both the Local Site UPF and the Central Site UPF. A legend indicates that a solid line with a dot represents an IP Anchor Point, and a dashed line with a circle represents a UL CL/BP and Local PSA UPF.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +Figure 4.3-1: 5GC Connectivity Models for Edge Computing. The diagram shows three connectivity models: Distributed Anchor Point, Session Breakout, and Multiple PDU Sessions. Each model shows a UE connected to a Radio Site, which is connected to a Local Site (containing a UPF), which is connected to a Central Site (containing a UPF), which is connected to a DN. In the Distributed Anchor Point model, the UE is connected to the Local Site UPF. In the Session Breakout model, the UE is connected to the Local Site UPF, and the Local Site UPF is connected to the Central Site UPF. In the Multiple PDU Sessions model, the UE is connected to both the Local Site UPF and the Central Site UPF. A legend indicates that a solid line with a dot represents an IP Anchor Point, and a dashed line with a circle represents a UL CL/BP and Local PSA UPF. + +Figure 4.3-1: 5GC Connectivity Models for Edge Computing + +# 5 Functional Description for Supporting Edge Computing + +## 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. + - Providing a DNS response with a specific IP address to a DNS query. + +- 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. + +![Diagram of EDC functionality in the UE](426efb7efdc753a13f2fa16f7bff9429_img.jpg) + +The diagram shows a vertical rectangle representing the User Equipment (UE). Inside this rectangle, there are two smaller rectangles. The top rectangle is labeled 'EDC consumer' and the bottom rectangle is labeled 'EDC functionality'. A dashed vertical line connects the two rectangles, indicating a functional relationship or data flow between them within the UE context. + +Diagram of 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 Client with the DNS Server's configuration (IP address and, conditionally, DNS security information of the EASDF/DNS resolver; see TS 24.501 [11] and TS 33.501 [12]) received from the SMF in the ePCO according to TS 23.501 [2] clause 5.6.10.1. +- 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 configuration of the DNS Server (IP address and, conditionally, DNS security information of the EASDF/DNS resolver; see TS 24.501 [11] and TS 33.501 [12]) received from the SMF. The consumer in the UE can explicitly request the DNS Server's configuration and/or can subscribe/unsubscribe to receive updates of the DNS Server's configuration. + +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. + +# --- 6 Procedures for Supporting Edge Computing + +## 6.1 General + +Edge Computing enables operator and 3rd party services to be hosted in EAS close to the UE's point of attachment. The traffic to EAS can be routed based on the UE position and EAS availability "near to" that position. + +The subsequent clauses describe the procedures for supporting Edge Computing in 5G System considering different connectivity models, including: + +- EAS discovery and re-discovery. +- Edge relocation. +- Network exposure to Edge Application Server. +- Support of 3GPP application layer architecture defined in TS 23.558 [5]. +- Support of AF guidance to PCF determination of proper URSP rules. + +## 6.2 EAS Discovery and Re-discovery + +### 6.2.1 General + +In Edge Computing deployment, an application service may be served by multiple Edge Application Servers typically deployed in different sites. These multiple Edge Application Servers that host service may use a single IP address (anycast address) or different IP addresses. To start such a service, the UE needs to know the IP address(es) of the Application Server(s) serving the service. The UE may do a discovery to get the IP address(es) of a suitable Edge + +Application Server (e.g. the closest one), so that the traffic can be locally routed to the Edge Application Server and service latency, traffic routing path and user service experience can be optimized. + +EAS discovery is the procedure by which a UE discovers the IP address(es) of a suitable Edge Application Server(s) using Domain Name System (DNS). EAS Re-discovery is the EAS Discovery procedure that takes place when the previously discovered Edge Application Server cannot be used or may have become non-optimal (e.g. at edge relocation). + +The DNS server to be used for EAS (re-)discovery may be deployed in different locations in the network as Central DNS (C-DNS) server or as Local DNS (L-DNS) resolver/server. + +NOTE 1: The C-DNS servers and/or L-DNS resolvers/servers can use an anycast address. + +NOTE 2: The C-DNS servers or L-DNS resolvers/servers can contact any other DNS servers for recursive queries, which is out of scope of this specification. + +NOTE 3: This specification describes the discovery procedure based on 5GS NFs as to ensure the UE is served by the application service closest to the UE's point of attachment. However, this does not exclude other upper layer solution that can be adopted by operator or service provider, like the EAS Discovery procedure defined in TS 23.558 [5], or other alternatives shown in Annex A and Annex B. How those other solutions work, or whether they are able to guarantee the closest application service for the UE, is out of the scope of this specification. + +In order to provide a translation of the FQDN of an EAS into the address of an EAS as topologically close as possible to the UE, the Domain Name System may use following information: + +- The source IP address of the incoming DNS Query; and/or, +- an EDNS Client Subnet (ECS) option (as defined in RFC 7871 [6]). + +NOTE 4: UE IP address can be subject to privacy restrictions, which means that it is not to be sent to Authoritative DNS / DNS Resolvers outside the network operator within EDNS Client Subnet option or as Source IP address of the DNS Query. UE source IP address can be protected by using NAT mechanism. + +EAS (re-)discovery procedures described in this specification should use the top level domains (TLDs) in the public namespace by default. + +If a private namespace is used, an Edge Computing Service Provider (ECSP) can provision DNS information in the EAS Deployment information via AF request with its Application Identifier, or DNN and NSSAI. Since private namespaces do not have a common root server or naming, the DNS information for each ECSP should be stored individually to prevent any overwriting of resolution entries. + +NOTE 5: The DNS information provided by ECSP in the EAS Deployment Information can be used to select the DNS settings for a PDU Session mainly if the PDU Session is specific for the ECSP services. + +If the UE applications want to discover/access EAS by using the mechanisms defined in this TS, the UE shall support receiving DNS settings in PCO during PDU Session Establishment and PDU Session Modification, and the DNS Queries generated by the UE for these applications shall be sent to the DNS server/resolver (e.g. EASDF) indicated by the SMF. To ensure this, the application in the UE either requests the EDC functionality to send a DNS Query or, alternatively, uses the EDC functionality to get the configuration of the DNS Server (IP address and, conditionally, DNS security information of the EASDF/DNS resolver; see TS 24.501 [11] and TS 33.501 [12]) indicated by the SMF (see clauses 5.2.1 and 6.2.4) then resolves the FQDN by its own DNS mechanism. + +NOTE 6: It is the decision of the application in the UE whether to use the EDC functionality or not to resolve the FQDN. If it does not use the EDC functionality, the usage of the EAS (re-)discovery procedures defined in clause 6.2 cannot be ensured. + +The case of EAS (Re-)discovery over Distributed Anchor connectivity model is described in clause 6.2.2. For Multiple PDU Sessions connectivity model, the description in clause 6.2.2 also applies to the PDU Session(s) with Local PSA. The case of EAS (Re-)discovery over Session Breakout connectivity model is described in clause 6.2.3. + +### 6.2.2 EAS (Re-)discovery over Distributed Anchor Connectivity Model + +#### 6.2.2.1 General + +#### 6.2.2.2 EAS Discovery Procedure + +For the Distributed Anchor connectivity model, in PDU Session Establishment procedure, the SMF selects a DNS Server for the PDU Session. The DNS Server is configured to UE via PCO, and may also be configured via DHCP and/or IPv6 RA. The SMF determines the DNS server address for the PDU Session based on local configuration and EAS Deployment Information provided by AF when applicable. + +In order to provide a translation of the FQDN of an EAS into the address of an EAS as close as possible to the UE (where closeness relates to IP forwarding distance), the DNS system uses mechanisms described in clause 6.2.1. + +For Distributed Anchor Point connectivity model, in order to provide addressing information to the DNS system that is related to the UE topological location, when a DNS Query is sent via the Local PSA UPF, + +- either the DNS Query is resolved by a DNS resolver, which then adds a DNS EDNS Client Subnet option that may be built based on a locally pre-configured value or based on the source IP address of the DNS Query; then send the DNS Query to the Authoritative DNS server, which may take into account the DNS EDNS Client Subnet option as defined in RFC 7871 [6], or +- the DNS Query is resolved by a DNS server that is close to the PSA UPF: the Authoritative DNS server may take into account the source IP address of the DNS Query. + +#### 6.2.2.3 EAS Re-discovery Procedure at Edge Relocation + +In order to change the PDU Session Anchor serving a PDU Session of SSC mode 2/3 for a UE, SMF triggers session continuity, service continuity and UP path management procedures as indicated in clause 4.3.5.1, 4.3.5.2 and 4.3.5.3 of TS 23.502 [3]. During these procedures, for SSC mode 2/3, it is recommended that the UE applies the following behaviour: + +The UE DNS cache should be bound to the IP connection. When the UE detects the PDU Session release or new IP prefix is allocated within the PDU Session, the UE removes the old DNS cache related to old/removed IP address/prefix, for example, the old Edge Application Server address information. + +NOTE 1: UE DNS cache refers to cache at any level (OS and Application). Whether the DNS cache of Application is included or influenced depends on application's behaviour and UE implementation. + +With this behaviour, when the establishment of a new PDU Session triggers EAS rediscovery for an FQDN, the UE can reselect a new EAS for that FQDN. + +For SSC mode 2, the procedure in clause 4.3.5.1 of TS 23.502 [3] applies with following differences: + +- In step 3, when the new PDU Session has been established, UE can reselect a new EAS for the FQDN with an EAS Discovery procedure if the recommended UE behaviour has been followed. + +For SSC mode 3 with multiple PDU Sessions, the procedure in clause 4.3.5.2 of TS 23.502 [3] applies with following difference: + +- In step 5, the UE can reselect a new EAS for the FQDN with an EAS Discovery procedure if the recommended UE behaviour has been followed. + +For SSC mode 3 with IPv6 Multi-homed PDU Session that all new traffic going via new IPv6 prefix, the procedure in clause 4.3.5.3 of TS 23.502 [3] applies with following difference: + +- After steps 10-11 where SMF notifies the UE of the availability of the new IP prefix, the UE starts using it for all new traffic, including DNS Queries. The UE can reselect a new EAS for the FQDN with an EAS Discovery procedure if the recommended UE behaviour has been followed. + +Then UE can reselect a new EAS for the FQDN with an EAS discovery procedure as defined in clause 6.2.2.2. + +NOTE 2: For SSC mode 3 with Multi-homed PDU Sessions, an EAS re-discovery indication may as well be sent as described in clause 6.2.3.3. + +The SMF may also trigger EAS rediscovery as defined in clause 6.2.3.3 when new connection to EAS needs to be established in case the UE indicate support for this. This trigger may also be used by the SMF based on the AF triggered EAS relocation as described in clause 6.3.7. + +#### 6.2.2.4 Procedure for EAS Discovery with Dynamic PSA Distribution + +5GC supports an EAS discovery procedure that allows that at PDU Session Establishment the SMF selects a Central PSA, regardless if a Local PSA is available to the SMF and then, it allows to dynamically re-anchor the PDU Session and transition to a Distributed Anchor Point connectivity model when needed. This is applicable to PDU Sessions of both SSC mode 2 and SSC mode 3. + +This procedure relies on EASDF capability to influence the DNS Query of a FQDN so that the EAS Discovery considers a candidate UE topological location of a PSA further out in the network than current PSA. The PDU Session re-anchoring to the edge is performed as part of the EAS Discovery procedure. + +This procedure requires that the DNS settings provided to the UE for the PDU Session are respected. + +![Sequence diagram illustrating the procedure for EAS Discovery with Dynamic PSA distribution using EASDF. The diagram shows interactions between UE, EAS, UPF 1, UPF 2, SMF 1, SMF 2, EASDF 1, EASDF 2, and DNS server. The process is divided into four numbered steps: 1. PDU session establishment (UPF1) and EASDF context creation and update; 2. DNS EAS discovery and PSA Change from UPF1 (Central UPF) to UPF2 (L-PSA); 3. EAS (re)Discovery; 4. Application traffic.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +The diagram is a sequence diagram showing the interaction between various network functions for EAS discovery. The lifelines are: UE, EAS, UPF 1, UPF 2, SMF 1, SMF 2, EASDF 1, EASDF 2, and DNS server. The sequence of messages is as follows: + +- 1. PDU session establishment (UPF1) and EASDF context creation and update (Clause 6.2.3.2.2-1 Step 1 -6)**: This step involves the initial PDU session establishment with UPF 1 and the creation and update of the EASDF context. +- 2. DNS EAS discovery and PSA Change from UPF1 (Central UPF) to UPF2 (L-PSA) (TS 23.502 clause 4.3.5.1, clause 4.3.5.2 and clause 4.3.5.3)**: The new DNS settings are provided and new DNS context is established for the new UP path after UE starts using new UE IP address/prefix with the new PDU session. The DNS context in EASDF is removed after old PDU session released or old UP IP address not used. +- 3. EAS (re)Discovery (clause 6.2.2.2)**: This step involves the EAS (re)discovery process. +- 4. Application traffic**: This final step shows the application traffic flow. + +Sequence diagram illustrating the procedure for EAS Discovery with Dynamic PSA distribution using EASDF. The diagram shows interactions between UE, EAS, UPF 1, UPF 2, SMF 1, SMF 2, EASDF 1, EASDF 2, and DNS server. The process is divided into four numbered steps: 1. PDU session establishment (UPF1) and EASDF context creation and update; 2. DNS EAS discovery and PSA Change from UPF1 (Central UPF) to UPF2 (L-PSA); 3. EAS (re)Discovery; 4. Application traffic. + +**Figure 6.2.2.4-1 Application server discovery with Dynamic PSA distribution using EASDF** + +The EAS Discovery procedure with Dynamic PSA distribution for both SSC mode 2 and SSC mode 3 PDU Sessions using EASDF is described in Figure 6.2.2.4-1. + +The procedure is as follows: + +1. PDU Session Establishment, allocation of an EASDF and sending rules to the EASDF. Steps 1-6 in the procedure 6.2.3.2.2-1 for EAS Discovery Procedure with EASDF for Session Breakout connectivity model are applied. If Dynamic PSA distribution applies to the PDU Session based on SMF local configuration, the SMF may have selected a Central PSA at PDU Session Establishment, regardless of whether a Local PSA is available. +2. The UE sends a DNS Query message for an FQDN to the EASDF via Central PSA. Steps 7-12 in the procedure in figure 6.2.3.2.2-1 for EAS Discovery Procedure with EASDF for Session breakout Connectivity are applied. That is, the EASDF checks the DNS Query against the DNS Handling Rules in the DNS Context and reports to SMF and/or forwards to DNS for resolution as instructed by these rules. For resolution, it applies Option A or option B in the procedure 6.2.3.2.2-1 or sends the DNS Query to a pre-configured DNS server/resolver if none of them applies. + +When the DNS Response is received, EASDF checks it against the DNS context matching conditions for reporting. If applicable, it reports to SMF the selected EAS and handles the DNS Response as instructed by SMF DNS handling rules: when there is a change of PDU Session Anchor per SSC mode 2 or 3, the SMF indicates to EASDF to discard the DNS Response. + +When no DNS Response is sent to the UE, the UE is expected to restart the DNS Query over the new PDU Session). + +For further details see clause 6.2.3.2.2. + +SMF determines that the central UPF (PSA) needs to be changed to an Edge UPF (L-PSA) and it triggers one of the procedures to change the PSA of the PDU Session to a distributed anchor. Which procedure is triggered depends on the SSC mode of the PDU Session and also on SMF configuration: + +- Change of SSC mode 2 PDU Session Anchor with different PDU Sessions as in clause 4.3.5.1 of TS 23.502 [3]. The procedure applies with the following differences: + +In step 2, the DNS context for the session is removed from EASDF as part of the PDU Session Release procedure (in step 12 of the PDU Session release procedure in TS 23.502 [3] in 4.3.4.2). + +In step 3, SMF selects and provisions the DNS settings for the new PDU Session as required by the procedure for EAS Discovery on Distributed anchor as described in clause 6.2.2.2. + +- Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions as in clause 4.3.5.2 of TS 23.502 [3]. The procedure applies with the following differences: + +In step 4 in clause 4.3.5.2 of TS 23.502 [3], SMF selects and provisions the DNS settings for the new PDU Session as required by the procedure for EAS Discovery on Distributed anchor as described in clause 6.2.2. Step 3 in 6.2.2.4 could happen any time after this step. + +In step 6 in clause 4.3.5.2 of TS 23.502 [3], the old DNS context for the old session and old UE IP address/prefix of UE are removed from EASDF as part of the PDU Session Release procedure (in step 12 of the PDU Session Release procedure in TS 23.502 [3] in 4.3.4.2). + +- Change of SSC mode 3 PDU Session Anchor with IPv6 Multi-homed PDU Session as in clause 4.3.5.3 of TS 23.502 [3]. The procedure applies with the following differences: + +In steps 10-11 in clause 4.3.5.3 of TS 23.502 [3], SMF also manages the EASDF context and provides new DNS settings to the UE if needed: + +- If EASDF is not going to be used, SMF sends the UE the new DNS settings in a PDU Session Modification Command and removes the EASDF context. +- If EASDF is going to be used, SMF may update existing EASDF context or it may remove it and create a new one, for example, to select a new EASDF. If a new EASDF is selected, SMF sends the UE the new DNS settings in a PDU Session Modification Command and may also send them in Router Advertisement. + +After steps 10-11 in clause 4.3.5.3 of TS 23.502 [3], UE starts using IP@2 for all new traffic, including DNS messages, and SMF can already perform from step 3 in figure 6.2.2.4-1. + +The PDU Session establishment in this step includes the actions described above in step 1 in figure 6.2.2.4-1 if DNS Queries should be able to trigger re-anchoring of the session to a more distributed PSA. + +NOTE 1: When new DNS settings do not involve EASDF, new DNS Query will not trigger re-anchoring of the PDU Session to a L-PSA deployed even further out in the network. + +To remove the Session context in EASDF, SMF invokes Neasdf\_DNSContext\_Delete Request/Response. + +NOTE 2: Dynamic re-anchoring to an edge PSA implies that the UE IP address is changed from a UE IP address corresponding to the old (central) PSA to a UE IP address corresponding to the new (edge) PSA for all applications on the PDU Session. + +NOTE 3: Further re-anchoring (to a central UPF) can be triggered if activity is monitored e.g. if EC application traffic ceases. In that case, EASDF is provided again in the DNS settings for the PDU Session. New EAS Discovery will go to EASDF and be handled as described in step 1. + +3. A new discovery procedure is triggered for the application over the new PSA: the UE resends a DNS Query targeting the application. (Re)discovery follows the EAS (re)Discovery procedure for distributed anchor connectivity model as in clauses 6.2.2.2 and 6.2.2.3. + +NOTE 4: Clause 6.2.2.3 describes the UE behaviour that makes it possible to reselect a new EAS over the new PSA. With change of SSC mode 3 PDU Session Anchor with IPv6 Multi-homed PDU Session, an EAS rediscovery indication can as well be sent as described in clause 6.2.3.3. + +4. Application traffic starts via the PDU Session Edge PSA to the EAS selected in step 3. + +### 6.2.3 EAS (Re-)discovery over Session Breakout Connectivity Model + +#### 6.2.3.1 General + +This clause describes the EAS discovery and re-discovery procedures for PDU Session with Session Breakout connectivity model. + +The following Session breakout models are defined: + +- Dynamic Session Breakout: ULCL/BP/Local PSA (and their associated traffic filters and forwarding rules) are inserted based on DNS Response provided by the EASDF or based on the common EAS. The detail of the ULCL/BP/Local PSA insertion or relocation triggered by the DNS Response message received for the EAS (Re-)discovery is described in the procedure in clause 6.2.3.2.2. +- Pre-established Session Breakout: ULCL/BP/Local PSA (and their associated traffic filters and forwarding rules) are inserted without dependency on the DNS Response(s) for the EAS (Re-)discovery. They are typically inserted based on local configuration or per traffic routing information from AF request within AF influence on traffic routing procedure. For the ULCL/BP/Local PSA insertion or relocation triggered by traffic routing information from AF request, the traffic routing information from AF request is received by the SMF via the SM policy which is created during the procedure PDU Session establishment or is updated during the lifetime of the PDU Session (e.g. updating the SM policy with the traffic routing information based on the detected application identifier based on the received application traffic like DNS Query or service data for the application). The details are described in clauses 4.3.5 and 6.2.1.2 of TS 23.503 [4] and in clause 5.6.7.1 of TS 23.501 [2] and in clause 4.3.6.2 of TS 23.502 [3]. + +#### 6.2.3.2 EAS Discovery Procedure + +##### 6.2.3.2.1 General + +For PDU Session with Session Breakout connectivity model, based on UE subscription (e.g. DNN) and/or the operator's configuration, the DNS Query sent by UE may be handled by an EASDF (see clause 6.2.3.2.2), or by a local or central DNS resolver/server (see clause 6.2.3.2.3). + +NOTE 1: For the scenario where the TE and MT are separated, information provided by the SMF in the NAS message during the PDU Session Establishment or Modification may not be provided to the TE. Annex C documents mitigations for this scenario. + +NOTE 2: The DNS Query sent by UE may or may not carry EDNS Client Subnet option in the DNS message. + +##### 6.2.3.2.2 EAS Discovery Procedure with EASDF + +For the case that the UE DNS Query is to be handled by EASDF, the following applies. + +- The AF may provide EAS Deployment Information to NEF which may store it in UDR, as defined in clause 6.2.3.4. SMF may retrieve EAS Deployment Information from NEF as described in clause 6.2.3.4 or has locally preconfigured information. EAS Deployment Information is used for creating DNS message handling rule on EASDF and it is not dedicated to specific UE session(s). + +EAS Deployment Information may apply to all PDU Sessions with a certain DNN, S-NSSAI and/or specific Internal Group Identifier(s). + +- The SMF may provide BaselineDNSPattern to EASDF, the BaselineDNSPattern are derived from EAS Deployment Information provided by AF and are not dedicated to specific PDU Session; SMF configures EASDF with BaselineDNSPattern according to the procedures defined in clause 6.2.3.4. + +The Baseline DNS message detection template ID may be used by the EASDF to refer to Baseline DNS message detection template, and derive array of FQDN ranges and/or array of EAS IP address ranges. The Baseline DNS handling actions ID may be used by the EASDF to refer to Baseline DNS handling actions information, and derive actions related parameters. + +The Baseline DNS message detection template ID and the Baseline DNS handling actions ID are unique per SMF set when a SMF set controls an EASDF and shall be unique per SMF otherwise, within an EASDF Baseline + +BaselineDNSPattern may contain one or several items, where each item is either a Baseline DNS message detection template or a Baseline DNS handling actions information. Each BaselineDNSPattern item may be updated or deleted using Baseline DNS message detection template ID or Baseline DNS handling actions ID to identify the updated or deleted item + +- Baseline DNS message detection template + - Baseline DNS message detection template ID + - DNS message type = DNS Query or DNS Response: + - If DNS message type = DNS Query: + - Array of (FQDN ranges). + - If DNS message type = DNS Response: + - Array of FQDN ranges and/or array of EAS IP address ranges. +- Baseline DNS handling actions information: + - Baseline DNS handling actions ID: + - ECS option. + - Local DNS server IP address. + +NOTE 1: The FQDN can be set to wildcard to indicate the default DNS Server (e.g. the C-DNS), for the case in which the DNS message should be forwarded to the default DNS Server. + +NOTE 2: The BaselineDNSPattern can be configured for a specific application with the related FQDN set in the detection template. + +NOTE 3: The definition of structure of Baseline DNS handling actions ID and Detection template ID is left to stage 3. As an example, Baseline DNS handling action ID and Detection template ID could contain a concatenation of the SMF ID or SMF set Id and of SMF implementation selected information such as the DNAI or a sequence number. The EASDF is not meant to understand the structure of Baseline DNS handling actions ID and Detection template ID. + +- During the PDU Session establishment procedure, the SMF may obtain the EAS Deployment Information from the NEF if not already retrieved (by subscription of such information to the NEF as described in clause 6.2.3.4.3) or the SMF is preconfigure with the EAS Deployment Information and the SMF selects an EASDF and provides its address to the UE as the DNS Server to be used for the PDU Session. + +The SMF configures the EASDF with DNS message handling rules to handle DNS messages related to the UE(s). The DNS message handling rule has a unique identifier and includes information used for DNS message detection and associated action(s). The DNS handling rules is defined as following: + +- Precedence of the DNS message handling rule; +- DNS Handling Rule Identity; +- A Baseline DNS message detection template ID and/or a DNS message detection template (optional and includes at least one of the following, if existing): + - DNS message type = DNS Query or DNS Response: + - If DNS message type = DNS Query: + +- Source IP address (i.e. UE IP address). +- Array of (FQDN ranges) (optional). +- If DNS message type = DNS Response: + - Array of FQDN ranges and/or array of EAS IP address ranges (optional). +- DNS message Identifier (if received from EASDF); + +NOTE 4: For DNS message type = Query, the UE IP address provided at DNS context creation (Neasdf\_DNSContext\_Create Request) is considered if not provided explicitly as part of the DNS message detection template. + +NOTE 5: DNS message Identifier is used by EASDF for matching between the message reported in the Neasdf\_DNSContext\_Notify and the corresponding DNS message handling rule included in Neasdf\_DNSContext\_Update. + +- Action(s) (includes at least one action); the possible actions include: + - Reporting Action: Report DNS message content to SMF (i.e. target FQDN and if available: IP address information provided back by the DNS server). This reporting action may include reporting-once indication. If this indication is included, the EASDF reports the DNS message content to the SMF once if the DNS message detection template matches the first incoming DNS Query or DNS Response message. + +NOTE 6: With reporting-once indication, the DNS message detection template should contain the EAS IP address ranges corresponding to the same DNAI. Resetting the Reporting-once indication can be used by the SMF to allow reporting associated with a DNS handling rule when the SMF has removed the UL CL/BP e.g. when the UE has moved out of the area associated with the current DNAI and thus insertion of a new UPF offloading capability can be considered. + +- Forwarding Action: Send the DNS message(s) to a DNS server/resolver(s) as follows: + - A. Including the information to build optional EDNS Client Subnet option to be included in the DNS message, or to be used for replacing the EDNS Client Subnet option received in the DNS Query message from the UE. (The information for the EASDF to build the EDNS Client Subnet option is either included in the DNS handling rule, or Baseline DNS handling actions ID acts as a reference to the Baseline DNS handling actions Information. This corresponds to the option A defined below.) + - B. the information for the DNS message target address is either included as DNS Server Address indicated in the DNS handling rule, or the Baseline DNS handling actions ID included in the DNS handling rules refers to DNS message target address information; if no DNS Server Address is provided by the SMF in the rule, then the EASDF is to forward the DNS message to a locally preconfigured default DNS server/resolver. This corresponds to the option B defined below. + - C. Respond directly to the DNS request. In this case the EASDF is configured by the SMF not to forward the DNS Query to the DNS server, instead it creates a response based on EAS IP address provided by the SMF. + +NOTE 7: The forwarding action can include either A, B or C. + +- Control Action: Performs at least one of control actions on the DNS message(s) as follows: + - Build DNS response from DNS query with indicated IP address (e. g. common EAS). The EASDF is expected to handle the response it has built the same way as a response it has received from a remote DNS server. + - Buffer the DNS message(s). + - Send the buffered DNS Response(s) message to UE. + - Discard cached DNS Response message(s). + +When the EASDF forwards a DNS message (to the UE or towards a DNS server over N6), it uses its own address as the source address of the DNS message. When the EASDF forwards the DNS message to the UE the EASDF based on + +configuration either replace the received EDNS Client Subnet option with the one provided by the UE (i.e. if provided by the UE) or remove any received EDNS Client Subnet. + +The SMF may use following information to create DNS message handling rules associated with a PDU Session: + +- Local configuration associated with the (DNN, S-NSSAI, Internal Group Identifier) of the PDU Session; and/or +- EAS Deployment Information provided by the AF or preconfigured in the SMF; and/or +- Information derived from the UE location such as candidate L-PSA(s); and/or +- PDU Session information, like PDU Session L-PSA(s) and ULCL/BP; and/or +- Internal Group Identifier received in the Session Management Subscription data from the UDM; and/or +- IP address or DNAI (e.g. common EAS, common DNAI) cached locally or retrieve from UDR via PCF. + +NOTE 8: For example, the SMF can derive the IP address for ECS based on the N6 IP address(es) associated with serving L-PSA(s) locally configured or in the NRF. + +NOTE 9: Providing in DNS EDNS Client Subnet option an IP address associated with the L-PSA UPF protects the privacy of the (IP address of the) UE. + +- If the FQDN in a DNS Query matches the FQDN(s) provided by the SMF in a DNS message detection template, based on instructions by SMF, one of the following options is executed by the EASDF based on a corresponding DNS message handling rule: + - Option A: The EASDF includes or replaces an EDNS Client Subnet (ECS) option into the DNS Query message as defined in RFC 7871[6] and sends the DNS Query message to the DNS server for resolving the FQDN. The DNS server may resolve the EAS IP address considering the EDNS Client Subnet option and sends the DNS Response to the EASDF; + - Option B: The EASDF sends the DNS Query message to a Local DNS server which is responsible for resolving the FQDN within the corresponding L-DN. The EASDF receives the DNS Response message from the Local DNS server. + +NOTE 10: Option B does not support the scenario where the PSA UPF for transferring DNS Query between EASDF and DNS server, or the EASDF has no direct connectivity with the Local DNS servers. + +The SMF instructions for a matching FQDN may as well indicate EASDF to contact SMF. SMF then provides the EASDF with a DNS message handling rule; + +- If the DNS Query from the UE does not match a DNS message handling rules set by the SMF, then the EASDF may simply forward the DNS Query towards a preconfigured DNS server/resolver for DNS resolution; +- When the EASDF receives a DNS Response message, the EASDF notifies the EAS information (i.e. EAS IP address(es), the EAS FQDN and if available the corresponding IP address within the ECS DNS option) to the SMF if the DNS message reporting condition provided by the SMF is met (i.e. the EAS IP address or FQDN is within the IP/FQDN range). The SMF may then select the target DNAI based on the EAS information and trigger UL CL/BP and L-PSA insertion as specified in clause 6.3.3 in TS 23.501 [2] based on the Notification. + +NOTE 11: To avoid SMF overloading caused by massive reporting, the overload control mechanisms defined in clause 6.4 of TS 29.500 [9] can be used. + +The information to build the EDNS Client Subnet option or the Local DNS server address provided by the SMF to the EASDF are part of the DNS message handling rules to handle DNS Queries from the UE. This information is related to DNAI(s) for that FQDN(s) for the UE location, or in the case a common DNAI is used for the set of UEs, the information is determined based on the common DNAI of the set of UEs. The SMF may provide DNS message handling rules to handle DNS Queries from the UE to the EASDF when the SMF establishes the association with the EASDF for the UE and may update the rules at any time when the association exists. For the selection of the candidate DNAI for a FQDN for the UE, the SMF may consider the UE location, network topology, EAS Deployment Information and related policy information for the PDU Session provided as defined in clause 6.4 of TS 23.503 [4] or be preconfigured into the SMF. After the UE mobility, if the provided Information for EDNS Client Subnet option or the Local DNS server address needs to be updated, the SMF may send an update of DNS message handling rules to the EASDF. + +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 DNAI randomly, or based on selection weight factor if provided by AF, or select the DNAI closest to the UE location. + +NOTE 13: To protect the SMF (e.g. to block DOS from the EASDF), the EASDF IP address for DNS Query Request is only accessible from the UE IP address via UPF. + +Once the UL CL/BP and L-PSA have been inserted, the SMF may decide that the DNS messages for the FQDN are to be handled by Local DNS resolver/server from now on. This option is further described in clause 6.2.3.2.3. + +To avoid EASDF sending redundant DNS message reports triggering UL CL/BP insertion corresponding to the same DNAI, the SMF may send reporting-once control information (i.e. DNS message handling rule with DNS message detection template containing EAS IP address ranges with reporting-once indication set) to EASDF to instruct the EASDF to report only once for the DNS messages matching with the DNS message detection template of the reporting-once control information for the DNS message detection template. In addition, the SMF may instruct the EASDF not to report DNS Responses to SMF corresponding to some FQDN ranges and/or EAS IP address ranges e.g. once the UL CL/BP and L-PSA have been inserted for the corresponding EAS IP address ranges for Pre-established session breakout while there is configuration for the related EASDF reporting DNS Responses. After the removal or change of the L-PSA, the SMF may instruct the EASDF to restart the reports of the DNS messages. + +If the SMF, based on local configuration, decides that the interaction between EASDF and DNS Server in the DN shall go via an UPF, the SMF sends corresponding N4 rules to this UPF to instruct this UPF to forward DNS message between EASDF and the external DNS server. In this case, DNS messages between EASDF and DNS Server described in this clause are transferred via this UPF transparently. + +NOTE 14: Based network configuration, one UPF is used to transmit DNS signalling between EASDF and DNS servers. The N4 session between the SMF and this UPF is not related to a specific PDU Session but provides rules targeting Downlink traffic from DNS servers to the EASDF and associated with the traffic of multiple UE(s); the traffic forwarding between EASDF and this UPF is realized by IP in IP tunnelling. The EASDF provides the SMF with the source address it uses to contact DNS servers and with the destination address where it expects to receive the tunnelled traffic. + +![Sequence diagram of EAS discovery procedure with EASDF. Lifelines: UE, SMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, EASDF, DNS Server. The procedure includes DNSContext Creation (PDU Session Establishment, Select EASDF, Create Request/Response) and DNSContext Update (Update Request/Response). It also shows DNS Query handling, NOTIFY/UPDATE exchanges between SMF and EASDF, ULCL/BP insertion, and final DNS response delivery to the UE.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant UPF_ULCL_BP as UPF ULCL/BP + participant UPF_L_PSA as UPF L-PSA + participant UPF_PSA as UPF PSA + participant EASDF + participant DNS_Server as DNS Server + + Note left of UE: DNSContext Creation Procedure + Note left of UE: 1. PDU Session Establishment Procedure + UE->>SMF: 1. PDU Session Establishment Request + Note right of SMF: 2. Select EASDF + SMF->>EASDF: 3. Neasdf_DNSContext_Create Request + EASDF-->>SMF: 4. easdf_DNSContext_Create Response + Note left of UE: DNSContext Update Procedure + SMF->>EASDF: 5. Neasdf_DNSContext_Update Request + EASDF-->>SMF: 6. Neasdf_DNSContext_Update Response + SMF->>EASDF: 7. DNS Query + SMF->>EASDF: 8. Neasdf_DNSContext_Notify Request + EASDF-->>SMF: 9. Neasdf_DNSContext_Notify Response + SMF->>EASDF: 10. Neasdf_DNSContext_Update Request + EASDF-->>SMF: 11. Neasdf_DNSContext_Update Response + Note right of EASDF: 12. DNS query + EASDF->>DNS_Server: 12. DNS query + DNS_Server-->>EASDF: 13. DNS Response + SMF->>EASDF: 14. Neasdf_DNSContext_Notify Request + EASDF-->>SMF: 15. Neasdf_DNSContext_Notify Response + Note right of SMF: 16. ULCL/BP insertion + SMF->>EASDF: 17. Neasdf_DNSContext_Update Request + EASDF-->>SMF: 18. Neasdf_DNSContext_Update Response + SMF->>UPF_ULCL_BP: 19. DNS response + UPF_ULCL_BP-->>UE: 19. DNS response + +``` + +Sequence diagram of EAS discovery procedure with EASDF. Lifelines: UE, SMF, UPF ULCL/BP, UPF L-PSA, UPF PSA, EASDF, DNS Server. The procedure includes DNSContext Creation (PDU Session Establishment, Select EASDF, Create Request/Response) and DNSContext Update (Update Request/Response). It also shows DNS Query handling, NOTIFY/UPDATE exchanges between SMF and EASDF, ULCL/BP insertion, and final DNS response delivery to the UE. + +Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF + +1. UE sends PDU Session Establishment Request to the SMF as shown in step 1 of clause 4.3.2.2.1 of TS 23.502 [3]. The SMF retrieves the UE subscription information from the UDM (which may optionally include an indication on UE authorization for EAS discovery via EASDF) and checks if the UE is authorized to discover the EAS via EASDF. If not authorized, this procedure is terminated, and the subsequent steps are skipped. +2. During the PDU Session Establishment procedure, the SMF selects EASDF as described clause 6.3 of TS 23.501 [2]. The SMF may consider the UE subscription information to select an EASDF as the DNS server of the PDU Session. + +The SMF may indicate to the UE either that for the PDU Session the use of the EDC functionality is allowed or that for the PDU Session the use of the EDC functionality is required. + +If the SMF, based on local configuration, decides that the interaction between EASDF and DNS Server in the DN shall go via the PSA UPF, the SMF configures PSA UPF within N4 rules to forward the DNS message between EASDF and DN. + +3. The SMF invokes Neasdf\_DNSContext\_Create Request (UE IP address, SUPI, DNN, notification endpoint, (DNS message handling rules)) to the selected EASDF. + +This step is performed before step 11 of PDU Session Establishment procedure in clause 4.3.2.2.1 of TS 23.502 [3]. + +The EASDF creates a DNS context for the PDU Session and stores the UE IP address, SUPI, the notification endpoint and potentially provided DNS message handling rule(s) into the context. + +The EASDF is provisioned with the DNS message handling rule(s), before the DNS Query message is received at the EASDF or as a consequence of the DNS Query reporting. + +4. The EASDF invokes the service operation Neasdf\_DNSContext\_Create Response. + +After this step, the SMF includes the IP address of the EASDF as DNS server/resolver for the UE in the PDU Session Establishment Accept message as defined in step 11 of clause 4.3.2.2.1 of TS 23.502 [3]. The UE configures the EASDF as DNS server for that PDU Session. + +If the UE requested to obtain UE IP address via DHCP and the SMF supports DHCP based IP address configuration, the SMF responds to the UE via DHCP response with the allocated UE IP address and/or the DNS server address containing the IP address of the EASDF. + +5. The SMF may invoke Neasdf\_DNSContext\_Update Request (EASDF Context ID, (DNS message handling rules)) to EASDF. The update may be triggered by UE mobility, e.g. when UE moves to a new location, or by a reporting by EASDF of a DNS Query with certain FQDN, or, the update may be triggered by insertion/removal of Local PSA, e.g. to update rules to handle DNS messages from the UE or by new PCC rule information. + +6. The EASDF responds with Neasdf\_DNSContext\_Update Response. + +7. If required (see clause 5.2.1), the Application in the UE uses the EDC functionality as described in clause 6.2.4 to send the DNS Query to the EASDF. The UE sends a DNS Query message to the EASDF. + +8. If the DNS Query message matches a DNS message detection template of DNS message handling rule for reporting, the EASDF sends the DNS message report to SMF by invoking Neasdf\_DNSContext\_Notify Request (information from the DNS Query e.g. target FQDN of the DNS Query). The EASDF may add a DNS message identifier in the Neasdf\_DNSContext\_Notify. The DNS message identifier uniquely identifies the DNS message reported and is used to associate the corresponding DNS message handling rule included in Neasdf\_DNSContext\_Update Request with the identified DNS message. The DNS message identifier is generated by EASDF. + +9. The SMF responds with Neasdf\_DNSContext\_Notify Response. + +10. If DNS message handling rule for the FQDN received in the report need to be updated, e.g. provide updates to information to build/replace the EDNS Client Subnet option information, the SMF invokes Neasdf\_DNSContext\_Update Request (DNS message handling rules) to EASDF. If the EASDF provided a DNS message identifier, the SMF adds this DNS message identifier to the corresponding DNS message handling rule included in Neasdf\_DNSContext\_Update. If the EASDF did not provide a DNS message identifier, the SMF may use the DNS message type (Request) and the target FQDN to uniquely identify the DNS message. + +For Option A, the DNS handling rule includes corresponding IP address to be used to build/replace the EDNS Client Subnet option. For Option B, the DNS handling rule includes corresponding Local DNS Server IP address. The EASDF may as well be instructed by the DNS handling rule to simply forward the DNS Query to a pre-configured DNS server/resolver. + +11. If the SMF provided a DNS message handling rule with DNS message identifier, the EASDF only applies the DNS message handling rule to the corresponding DNS message. The EASDF responds with Neasdf\_DNSContext\_Update Response. + +12. The EASDF handles the DNS Query message received from the UE as the following: + +- For Option A, the EASDF adds/replaces the EDNS Client Subnet option into the DNS Query message as specified in RFC 7871[6] and sends it to C-DNS server; +- For Option B, the EASDF removes EDNS Client Subnet option if received in the DNS query and sends the DNS Query message to the Local DNS server. + +If no DNS message detection template within the DNS message handling rule provided by the SMF matches the requested FQDN in the DNS Query, the EASDF may simply send a DNS Query to a pre-configured DNS server/resolver. + +13. EASDF receives the DNS Response including EAS IP addresses which is determined by the DNS system and determines that the DNS Response can be sent to the UE. +14. The EASDF sends DNS message reporting to the SMF by invoking Neasdf\_DNSContext\_Notify request including EAS information if the EAS IP address or the FQDN in the DNS Response message matches the DNS message detection template provided by the SMF. The DNS message reporting may contain multiple EAS IP address if the EASDF has received multiple EAS IP address(es) from the DNS server it has contacted. The DNS message reporting may contain the FQDN and the EDNS Client Subnet option received in the DNS Response message. The EASDF may also add DNS message identifier to the reporting. The DNS message identifier uniquely identifies the DNS response reported, and the EASDF can associate the corresponding DNS message handling rule included in Neasdf\_DNSContext\_Update Request with the identified DNS response. The DNS message identifier is generated by EASDF. + +Per the received DNS message handling rule, the EASDF does not send the DNS Response message to the UE but waits for SMF instructions (in step 17), i.e. buffering the DNS Response message. + +If the DNS Response(s) is required to be buffered and reported to the SMF, when the reporting-once control information is set, EASDF only reports to SMF once by invoking Neasdf\_DNSContext\_Notify request for DNS Responses matching with the DNS message detection template. + +15. The SMF invokes Neasdf\_DNSContext\_Notify Response service operation. +16. The SMF may perform UL CL/BP and Local PSA selection and insert UL CL/BP and Local PSA. + +Based on EAS information received from the EASDF in Neasdf\_DNSContext\_Notify, other UPF selection criteria, as specified in clause 6.3.3 in TS 23.501 [2], and possibly Service Experience or DN performance analytics for an Edge Application as described in TS 23.288 [10], the SMF may determine the DNAI. The SMF may also determine the associated N6 traffic routing information for the DNAI according to N6 traffic routing information for the DNAI included in EAS Deployment Information and configure Local PSA UPF with forwarding actions derived from the N6 traffic routing information. The SMF may perform UL CL/BP and Local PSA selection and insertion as described in TS 23.502 [3]. In case of UL CL, the traffic detection rules and traffic routing rules are determined by the SMF based on IP address range(s) per DNAI included in the EAS Deployment Information or according to PCC rule received from PCF or according to preconfigured information. + +17. The SMF invokes Neasdf\_DNSContext\_Update Request (DNS message handling rules). If the EASDF provided a DNS message identifier, the SMF adds this to the corresponding DNS message handling rule included in Neasdf\_DNSContext\_Update Request. If the EASDF did not provide a DNS message identifier, the SMF may use the DNS message type (Response) and the FQDN to uniquely identify the DNS response message. + +The DNS message handling rule with the Control Action "Send the buffered DNS response(s) message to UE" indicates the EASDF to send DNS Response(s) buffered in step 14 to UE. Other DNS message handling rule may indicate the EASDF not to send further DNS Response message(s) corresponding to FQDN ranges and/or EAS IP address ranges. + +18. If the SMF provided a DNS message handling rule with DNS message identifier, the EASDF only applies the DNS message handling rule to the corresponding DNS response. The EASDF responds with Neasdf\_DNSContext\_Update Response. +19. If indicated to send the buffered DNS response(s) to UE in step 17, the EASDF sends the DNS Response(s) to the UE and handles the EDNS Client Subnet option as described above. + +During PDU Session Release procedure, the SMF removes the DNS context by invoking Neasdf\_DNSContext\_Delete service. + +##### 6.2.3.2.3 EAS Discovery Procedure with Local DNS Server/Resolver + +For the case that the DNS message is to be handled by Local DNS resolver/server, the DNS Query is routed to the Local DNS resolver/server corresponding to the DNAI where the L-PSA connects. The SMF selects the Local DNS server address based on the DNAI corresponding to the inserted local PSA, local configuration and based on EAS Deployment + +Information in AF request as specified in clause 6.2.3.4.2. Based on the operator's configuration, one of the following options may apply when UL CL/BP and Local PSA have been inserted (during or after PDU Session Establishment): + +- Option C: The SMF configures the local DNS server to the UE as new DNS server. The SMF may indicate to the UE either that for the PDU Session the use of the EDC functionality is allowed or that for the PDU Session the use of the EDC functionality is required. In addition, the SMF also configures traffic routing rule on the UL CL (including e.g. Local DNS server address) or the BP (e.g. the new IP prefix @ Local PSA) to route traffic destined to the L-DN including the DNS Query messages to the L-PSA. The L-DNS server resolves the DNS Query either locally or recursively by communicating with other DNS servers. +- 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 locally routed to a Local DNS server. + +NOTE 1: Option D assumes that ULCL steering is based on L4 information (i.e. DNS port number) and that ULCL has visibility of the DNS traffic (i.e. FQDN in the DNS Query message). The UPF may be instructed by the SMF to apply different forwarding of non-ciphered UL DNS traffic based on the target domain of the DNS Query. Option D requests modification of destination IP address of DNS messages. Whether this is allowed or not is subject to local regulations. Option D does not apply to DoH or DoT messages. + +![Sequence diagram for EAS discovery with Local DNS server/resolver. The diagram shows interactions between UE, SMF, ULCL/BP, L-PSA, PSA, Local DNS Resolver, Local DNS Server, and C-DNS. The process starts with PDU Session Establishment (step 0), followed by ULCL/BP insertion (step 1). Option C is shown with PDU Session Modification Command (step 2) and Ack (step 3). The UE then sends a DNS Query (step 4) to the ULCL/BP, which is forwarded to the L-PSA. The L-PSA then handles the DNS message forwarding and handling (step 5), resulting in a DNS response (step 6) being sent back to the UE.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant ULCL/BP + participant LPSA as L-PSA + participant PSA + participant LDR as Local DNS Resolver + participant LDS as Local DNS Server + participant CDNS as C-DNS + + rect rgb(255, 255, 255) + Note over UE, PSA: 0. PDU Session Establishment + end + + rect rgb(255, 255, 255) + Note over UE, PSA: 1. ULCL/BP insertion + end + + rect rgb(255, 255, 255) + Note over UE, SMF: Option C + SMF->>UE: 2. PDU Session Modification Command + UE->>SMF: 3. PDU Session Modification Command Ack + end + + UE->>ULCL/BP: 4. DNS Query + ULCL/BP->>LPSA: + + rect rgb(255, 255, 255) + Note over LPSA, CDNS: 5. DNS message forwarding and handling + end + + LPSA->>ULCL/BP: 6. DNS response + ULCL/BP->>UE: + +``` + +Sequence diagram for EAS discovery with Local DNS server/resolver. The diagram shows interactions between UE, SMF, ULCL/BP, L-PSA, PSA, Local DNS Resolver, Local DNS Server, and C-DNS. The process starts with PDU Session Establishment (step 0), followed by ULCL/BP insertion (step 1). Option C is shown with PDU Session Modification Command (step 2) and Ack (step 3). The UE then sends a DNS Query (step 4) to the ULCL/BP, which is forwarded to the L-PSA. The L-PSA then handles the DNS message forwarding and handling (step 5), resulting in a DNS response (step 6) being sent back to the UE. + +Figure 6.2.3.2.3-1: EAS discovery with Local DNS server/resolver + +0. UE sends a PDU Session Establishment Request to the SMF as shown in step 1 of clause 4.3.2.2.1 of TS 23.502 [3]. The SMF retrieves the UE subscription information from the UDM (which may optionally include an indication on UE authorization for EAS discovery via EASDF) and checks if the UE is authorized to discover the EAS via EASDF. If not authorized, the actions related to EASDF in this procedure are skipped. + +1. The SMF inserts UL CL/BP and Local PSA. + +UL CL/BP/Local PSA insertion can be triggered by DNS messages as described in clause 6.2.3.2.2. Or, the SMF may pre-establish the UL CL/BP and Local PSA before the UE sends out any DNS Query message (e.g. upon UE mobility). In this case, the SMF includes the IP address of Local DNS Server in PDU Session Establishment Accept message as in step 11 of clause 4.3.2.2.1 of TS 23.502 [3] or in a network initiated PDU Session Modification procedure. The UE configures the Local DNS Server as DNS server for that PDU Session. + +NOTE 2: If the new DNS server address is provided to the UE, the UE can refresh all EAS(s) information (e.g. DNS cache) bound to the PDU Session, based on UE implementation. + +The UL CL/BP and Local PSA are inserted or changed as described in TS 23.502 [3]. In the case of IPv6 multi-homing, the SMF may also send an IPv6 multi-homed routing rule along with the IPv6 prefix to the UE to influence the selection of the source Prefix for the subsequent DNS Queries as described in clause 5.8.2.2.2 of TS 23.501 [2]. + +When the UL CL/BP and Local PSA are inserted or simultaneously changed, the SMF configure the UL CL/BP for DNS Query handling: + +- For Option C, the SMF configures traffic routing rule on the UL CL (including e.g. Local DNS server address) or the BP (e.g. the new IP prefix @ Local PSA) to forward UE packets destined to the L-DN to the Local PSA. The packets destined to L-DN includes DNS Query messages destined to Local DNS Server. + +Steps 2 and 3 are performed for option C: + +2. If the UL CL/BP and Local PSA are inserted after PDU Session Establishment, the SMF sends PDU Session Modification Command (Local DNS Server Address) to UE. + +If, based on operator's policy or UE's mobility, the Local DNS Server IP address in the local Data Network needs to be notified or updated to UE, the SMF sends PDU Session Modification Command (Local DNS Server Address) to UE. + +3. The UE responds with PDU Session Modification Command Ack. + +The UE configures the Local DNS Server as the DNS server for the PDU Session. The UE sends the following DNS Queries to the indicated Local DNS Server. + +If EASDF was used as the DNS server for the PDU Session, the SMF may invoke Neasdf\_DNSContext\_Delete service to remove the DNS context in the EASDF. + +NOTE 3: The UE does not need to know that the new DNS server is "local". + +For the Split-UE in the option C case, the new address of Local DNS Server cannot be provided to the TE or the TE OS from the MT, Annex C documents mitigations for this scenario. + +4. If required (see clause 5.2.1), the application in the UE uses the EDC functionality as described in clause 6.2.4 to send the DNS Query to the DNS Resolver/DNS Server indicated by the SMF in Step 0. UE sends a DNS Query message. In the case of IPv6 multi-homing the UE selects the source IP prefix based on the IPv6 multi-homed routing rule provided by SMF. + +5. The DNS Query message is forwarded to the Local DNS Server and handled as described in following: + +- For Option C, the target address of the DNS Query is the IP address of the Local DNS Server. The DNS Query is forwarded to the Local DNS Server by UL CL/BP and Local PSA. The Local DNS Server resolves the FQDN of the DNS Query by itself or communicates with other DNS server to recursively resolve the EAS IP address. +- For Option D: The Local PSA sends the DNS traffic to the Local DNS Server that resolves the FQDN target of the DNS Query by itself or that communicates with a C-DNS server to recursively resolve the EAS IP address. + +NOTE 4: The Local PSA can send the DNS traffic to the Local DNS Server via tunnelling or via IP address replacement. If IP address replacement is used, the SMF sends the IP address of the Local DNS Server to the Local PSA and instructs the Local PSA to modify the packet's destination IP address (corresponding to EASDF) to that of the Local DNS Server. + +6. The Local PSA receives DNS Response message from Local DNS server, it forwards it to the UL CL/BP and the UL CL/BP forwards the DNS Response message to UE. + +NOTE 5: If IP address replacement has been enforced at step 5, the Local PSA replaces the source IP address to EASDF IP according to SMF instruction. + +If SMF decides to remove the UL CL/BP and Local PSA as defined in clause 4.3.5.5 of TS 23.502 [3], e.g. due to UE mobility, the SMF sends a PDU Session Modification Command to configure the new address of the DNS server on UE (e.g. to set it to the address of EASDF). + +##### 6.2.3.2.4 Select common DNAI with Local DNS Server/Resolver for a set of UEs + +The following procedure is for selecting common DNAI with Local DNS Server/Resolver for set of UEs. + +NOTE: In this Release, when an operator deploys the Local DNS server option defined in clause 6.2.3.2.3, the operator needs to be ensured that a UE cannot be involved in more than one UE set for a DNN and S-NSSAI. + +![Sequence diagram for Figure 6.2.3.2.4-1: Discovery Procedure for selecting the common DNAI for a set of UEs with Local DNS Server/Resolver. The diagram shows five lifelines: UE, SMF, UPF (UL CL/BP), UPF (PSA), and DNS Server. Step 1: UE sends a PDU Session Establishment Request to SMF. Step 2: SMF determines UE belongs to a set of UEs accessing an EAS corresponds to a common DNAI. Step 3: Step 5-6 of Figure 6.2.3.2.3-1 is performed to resolve EAS IP address via Local DNS Server and send it to UE.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant UPF1 as UPF (UL CL/BP) + participant UPF2 as UPF (PSA) + participant DNS as DNS Server + + Note right of SMF: 2. Based on step 1-4 of Figure 6.2.3.2.3-1, SMF determines UE belongs to a set of UEs accessing an EAS corresponds to a common DNAI + Note right of UPF1: 3. Step 5-6 of Figure 6.2.3.2.3-1 is performed to resolve EAS IP address via Local DNS Server and send it to UE + + UE->>SMF: 1. PDU Session Establishment Request + +``` + +Sequence diagram for Figure 6.2.3.2.4-1: Discovery Procedure for selecting the common DNAI for a set of UEs with Local DNS Server/Resolver. The diagram shows five lifelines: UE, SMF, UPF (UL CL/BP), UPF (PSA), and DNS Server. Step 1: UE sends a PDU Session Establishment Request to SMF. Step 2: SMF determines UE belongs to a set of UEs accessing an EAS corresponds to a common DNAI. Step 3: Step 5-6 of Figure 6.2.3.2.3-1 is performed to resolve EAS IP address via Local DNS Server and send it to UE. + +**Figure 6.2.3.2.4-1: Discovery Procedure for selecting the common DNAI for a set of UEs with Local DNS Server/Resolver** + +1. The UE sends a PDU Session establishment request to SMF as specified in step 0 of Figure 6.2.3.2.3-1. +2. The procedure in steps 1-4 of Figure 6.2.3.2.3-1 applies with following difference: + +In step 1, the SMF determines UE belongs to a set of UEs accessing an EAS corresponds to a common DNAI based on traffic correlation indication and Traffic correlation ID in the PCC rule. + +If the common DNAI is not available, the SMF notifies the NEF to determine the common DNAI as described in clause 6.2.3.2.7. + +Once the common DNAI is available, SMF inserts or changes a Local PSA serving the common DNAI and selects local PSA and local DNS server corresponding to the common DNAI. + +If the PDU session has been established and the PCC rule including updated common DNAI is provided to SMF, the SMF should reselect the local DNS server according to the common DNAI and configure the UE with new local DNS server in PCO using PDU session modification procedure. + +3. The EAS information (e.g. EAS IP address) is resolved by Local DNS Server and sent the UE as described in steps 5-6 of Figure 6.2.3.2.3-1. + +##### 6.2.3.2.5 Common EAS discovery for a set of UEs + +The following is the procedure for common EAS discovery for a set of UEs accessing the same application. Different UEs can be served by different SMFs. + +The common EAS IP address for the set of UEs may be provided by AF or determined by 5GC. AF may provide the common EAS IP via AF Traffic influence procedure as defined in clause 4.3.6.2 of TS 23.502 [3], for this purpose AF may determine the common EAS IP address based on candidate DNAI(s) reported by SMF as described in clause 4.3.6.3 of TS 23.502 [3]. Alternatively, the common EAS IP address may be determined by NEF as defined in clause 6.2.3.2.7 and is stored in UDR as part of AF traffic influence request information. + +![Sequence diagram for Figure 6.2.3.2.5-1: Common EAS discovery for a set of UEs. The diagram shows eight lifelines: UE, EASDF, DNS Server, SMF, PCF, UDR, NEF, and AF. Step 1: SMF sends an AF Request to influence traffic routing procedure to AF. Step 2: SMF performs the EAS discovery procedure with EASDF.](d5918cee231b536f20789a18d861fae3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EASDF + participant DNS as DNS Server + participant SMF + participant PCF + participant UDR + participant NEF + participant AF + + Note right of SMF: 1. Step 1~5 in AF Request to influence traffic routing procedure, Figure 4.3.6.2-1 TS23.502 + Note right of SMF: 2. Step 1~19 in Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF + + SMF->>AF: 1. Step 1~5 in AF Request to influence traffic routing procedure, Figure 4.3.6.2-1 TS23.502 + SMF->>EASDF: 2. Step 1~19 in Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF + +``` + +Sequence diagram for Figure 6.2.3.2.5-1: Common EAS discovery for a set of UEs. The diagram shows eight lifelines: UE, EASDF, DNS Server, SMF, PCF, UDR, NEF, and AF. Step 1: SMF sends an AF Request to influence traffic routing procedure to AF. Step 2: SMF performs the EAS discovery procedure with EASDF. + +**Figure 6.2.3.2.5-1: Common EAS discovery for a set of UEs** + +1. The AF request in step 1 of figure 4.3.6.2-1 in TS 23.502 [3] is used to request selecting the common EAS for a set of UEs accessing the application as identified in the AF Request. + +AF may use External/Internal Group ID(s) or a list of UEs or any UE as Target UE Identifier(s) and additionally Spatial Validity Condition to identify the set of UEs for correlated selection of common EAS. + +The following information may be included in AF request as defined in clause 5.6.7.1 of TS 23.501 [2]: + +- An EAS Correlation indication may be provided for indication of selecting the same EAS for the set of UEs accessing the same application. +- A Traffic Correlation ID may be provided for identification of the set of UEs accessing the application identified by the Traffic Description in AF request. +- A Common EAS to be accessed by the set of UEs may be included in AF request, if it is determined by AF. +- FQDN(s) may be included which is corresponding to the application traffic identified by Traffic Description in AF request. +- Spatial Validity Condition could be provided for limiting the location of the UEs, and also "any UE" or a UE list or group ID can be provided for defining the set of UEs accessing the same EAS. + +In step 3a of figure 4.3.6.2-1 of TS 23.502 [3], NEF updates the AF influence data related to the traffic correlation ID in the UDR with a Notification Endpoint to subscribe to be notified with information related to SMF's involvement for UE members of the set of UEs. + +In step 5 of figure 4.3.6.2-1 of TS 23.502 [3], PCF determines the UEs influenced by the AF Request and for each UE, based on AF request, PCF creates PCC rule with Traffic Correlation ID, EAS Correlation indication, Common EAS, FQDN(s) and NEF subscription to SMF due to step 3a and sends the PCC rule to the SMF. + +If an existing PDU Session is impacted by the above PCC rule for common EAS discovery and if the UE has indicated that it supports to refresh EAS information stored locally, the SMF shall send PDU Session Modification Command (EAS rediscovery indication, [impact field]) to UE to refresh the cached EAS information as described in step 2 of clause 6.2.3.3. + +2. Based on steps 1-19 in figure 6.2.3.2.2-1, with the following updates: + +In step 9: + +If FQDN in Neasdf\_DNSContext\_Notify Request is corresponding to the application indicated in PCC rule, e.g. the FQDN is included in the FQDN(s) in the PCC rule and if EAS Correlation indication is set, SMF determines the UE belongs to the set of UEs identified by Traffic Correlation ID and accessing the application and determines the UE connects to the common EAS for the set of UEs. If FQDN(s) is included in PCC rule, the SMF can use the FQDN(s) in PCC rule and the FQDN in Neasdf\_DNSContext\_Notify Request to match the FQDN with the PCC rule, i.e. the matched PCC rule includes the FQDN(s) containing the FQDN in Neasdf\_DNSContext\_Notify Request. + +If the common EAS is not present in PCC rule or SMF decides to trigger the EAS discovery procedure to select a new EAS for the set of UEs: + +Steps 10-15 are used for discovering of common EAS. After step 15, the procedure defined in clause 6.2.3.2.7 may be performed for common EAS IP coordination. + +Else, if the common EAS is available and to be used for the set of UEs: + +Steps 10-15 are skipped. + +In step 16: + +SMF may determine the DNAI based on the common EAS. + +In step 17: + +SMF sends DNS message handling rule including IP address for the common EAS and the Forwarding Action "Respond directly to the DNS request" for instructing EASDF to return the Common EAS IP address in a DNS response to UE directly. + +In step 19: + +If received IP address of the common EAS and instructed to respond directly in step 17, EASDF sends DNS response with the IP address of the common EAS to UE. + +##### 6.2.3.2.6 EAS discovery corresponding to Common DNAI for a set of UEs + +The common DNAI for the set of UEs can be provided either by AF or determined by 5GC. When the AF determines the common DNAI, the AF provides the common DNAI for the set of UEs via AF Traffic influence procedure as defined in clause 4.3.6.2 of TS 23.502 [3]. The AF may determine the common DNAI based on candidate DNAI(s) reported by SMF as described in clause 4.3.6.3 of TS 23.502 [3]. + +When the 5GC determines the common DNAI, the common DNAI is determined by NEF and the NEF stores the common DNAI in UDR as part of AF traffic influence request information, as described in clause 6.2.3.2.7. + +The following is the procedure for discovery EAS corresponding to a Common DNAI for set of UEs accessing the same application. + +![Sequence diagram for EAS discovery corresponding to Common DNAI for a set of UEs. The diagram shows interactions between UE, EASDF, DNS Server, SMF, PCF, UDR, NEF, and AF. Step 1 is an AF Request to influence traffic routing procedure (Figure 4.3.6.2-1 TS23.502) from AF to SMF. Step 2 is the EAS discovery procedure with EASDF (Figure 6.2.3.2.2-1) involving UE, EASDF, and DNS Server.](7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EASDF + participant DNS Server + participant SMF + participant PCF + participant UDR + participant NEF + participant AF + + Note right of SMF: 1. Step 1~5 in AF Request to influence traffic routing procedure, Figure 4.3.6.2-1 TS23.502 + AF->>SMF: AF Request + Note left of SMF: 2. Step 1~19 in Figure 6.2.3.2.2-1: EAS discovery procedure with EASDF + UE->>EASDF: DNS Query + EASDF->>DNS Server: DNS Query + DNS Server->>EASDF: DNS Response + EASDF->>UE: DNS Response + +``` + +Sequence diagram for EAS discovery corresponding to Common DNAI for a set of UEs. The diagram shows interactions between UE, EASDF, DNS Server, SMF, PCF, UDR, NEF, and AF. Step 1 is an AF Request to influence traffic routing procedure (Figure 4.3.6.2-1 TS23.502) from AF to SMF. Step 2 is the EAS discovery procedure with EASDF (Figure 6.2.3.2.2-1) involving UE, EASDF, and DNS Server. + +**Figure 6.2.3.2.6-1: EAS discovery corresponding to Common DNAI for a set of UEs** + +1. The AF request in step 1 of figure 4.3.6.2-1 in TS 23.502 [3] is used to request selecting the common DNAI for a set of UEs accessing the application as identified in the AF Request. + +AF may use External/Internal Group ID(s) or a list of UEs or any UE as Target UE Identifier(s) and additionally Spatial Validity Condition to identify the set of UEs for correlated selection of common DNAI. + +The following information may be included in AF request as defined in clause 5.6.7.1 in TS 23.501 [2]: + +- An indication of traffic correlation may be provided for indication of selecting the same DNAI (i.e. selecting EAS corresponding to the same DNAI) for the set of UEs accessing the same application. +- A Traffic Correlation ID may be provided for identification of the set of UEs accessing the application identified by the Traffic Description in AF request. +- A Common DNAI to be accessed by the set of UEs can be included in AF request, if it is determined by AF. +- FQDN(s) may be included which is corresponding to the application identified by Traffic Description in AF request. +- Spatial Validity Condition could be provided for limiting the location of the UEs, and also "any UE" or a UE list or group ID can be provided for defining set of UEs accessing the same DNAI. + +In step 3a of figure 4.3.6.2-1 of TS 23.502 [3], NEF updates the AF influence data related to the traffic correlation ID in the UDR with a Notification Endpoint to subscribe to be notified with information related to SMF's involvement for UE members of the set of UEs. + +In step 5 of figure 4.3.6.2-1 of TS 23.502 [3], PCF determines the UEs influenced by the AF Request, and for each UE, based on AF request, PCF creates PCC rule with Traffic Correlation ID and indication of traffic correlation, Common DNAI, FQDN(s) and Notification endpoint of NEF subscription received to step 3a and sends the PCC rule to the SMF. + +If an existing PDU Session is impacted by the above PCC rule for EAS discovery corresponding to Common DNAI and if the UE has indicated that it supports to refresh EAS information stored locally, the SMF shall send PDU Session Modification Command (EAS rediscovery indication, [impact field]) to UE to refresh the cached EAS information as described in step 2 of clause 6.2.3.3. + +- Based on steps 1~19 in figure 6.2.3.2.2-1, with the following changes: + +In step 10: + +If FQDN in Neasdf\_DNSContext\_Notify Request is corresponding to the application indicated in PCC rule, e.g. the FQDN is included in the FQDN(s) in the PCC rule and if indication of traffic correlation is set, SMF determines the UE belongs to set of UEs identified by Traffic Correlation ID and accessing the application and determines the UE connects to EAS corresponding to the common DNAI for the set of UEs. If FQDN(s) is included in PCC rule, the SMF can use the FQDN(s) in PCC rule and the FQDN in Neasdf\_DNSContext\_Notify Request to match the FQDN with the PCC rule, i.e. the matched PCC rule includes the FQDN(s) containing the FQDN. + +If the common DNAI is not available in the PCC Rule received in step 1, the SMF invokes the NEF to determine the common DNAI as described in clause 6.2.3.2.7. + +Once the common DNAI is available, for Option A, SMF provisions EASDF with the information to build EDNS Client Subnet option that refers to a location that is topologically close to the common DNAI; for Option B, SMF provisions EASDF with Local DNS server related to the common DNAI. + +##### 6.2.3.2.7 Coordination among SMFs for Common EAS/DNAI determination + +![Sequence diagram showing the interaction between SMF, PCF, UDR, and NEF for Common EAS/DNAI determination. The diagram consists of four numbered steps: 1. SMF sends Nsmf_TrafficCorrelation_notify to NEF; 2. NEF sends Store/Update common EAS, common DNAI together with AF influence data related to the traffic correlation ID to UDR; 3. NEF sends Nsmf_TrafficCorrelation_notify response to SMF; 4. UDR sends Notification to PCF(s), and associated PCC rule to those SMF(s) involved with PDU Session(s) associated with the Traffic Correlation ID.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant PCF + participant UDR + participant NEF + Note right of NEF: 2. Store/Update common EAS, common DNAI together with AF influence data related to the traffic correlation ID + Note right of UDR: 4. Notification to PCF(s), and associated PCC rule to those SMF(s) involved with PDU Session(s) associated with the Traffic Correlation ID + SMF->>NEF: 1. Nsmf_TrafficCorrelation_notify + NEF->>UDR: 2. Store/Update common EAS, common DNAI together with AF influence data related to the traffic correlation ID + NEF->>SMF: 3. Nsmf_TrafficCorrelation_notify response + UDR->>PCF: 4. Notification to PCF(s), and associated PCC rule to those SMF(s) involved with PDU Session(s) associated with the Traffic Correlation ID + +``` + +Sequence diagram showing the interaction between SMF, PCF, UDR, and NEF for Common EAS/DNAI determination. The diagram consists of four numbered steps: 1. SMF sends Nsmf\_TrafficCorrelation\_notify to NEF; 2. NEF sends Store/Update common EAS, common DNAI together with AF influence data related to the traffic correlation ID to UDR; 3. NEF sends Nsmf\_TrafficCorrelation\_notify response to SMF; 4. UDR sends Notification to PCF(s), and associated PCC rule to those SMF(s) involved with PDU Session(s) associated with the Traffic Correlation ID. + +Figure 6.2.3.2.7-1: Handling of Common EAS, Common/DNAI for set of UEs + +- SMF sends Nsmf\_TrafficCorrelation\_Notify to the NEF with Notification Endpoint received in the PCC rule as described in clauses 6.2.3.2.5 and 6.2.3.2.6 and provides: EAS IP address based on EASDF procedure, list of candidate DNAI(s), SMF ID, number of PDU sessions it is serving for the set of UEs, Traffic Correlation ID. +- If the NEF determines that there is currently no common EAS IP address and/or common DNAI available for the set of UEs identified by Traffic Correlation ID, it selects a common DNAI and/or common EAS using the list of DNAI(s), EAS IP address and number of PDU sessions each SMF is serving for the set of UEs received in step 1. Then the NEF updates traffic influence data with the 5GC determined common EAS/DNAI for the set of UEs. + +The update of traffic influence data triggers notifications to PCF(s) that in turn trigger associated PCC rule updates to the SMF(s), if any, with PDU Session(s) associated with the traffic correlation ID. + +The NEF maintains a list of SMFs serving the set of UEs and the associated data including common DNAI, common EAS, number of PDU sessions each SMF is serving for the set of UEs, Traffic Correlation ID. + +- NEF responds by acknowledging the notification to the SMF. +- The update in UDR triggers notification to the PCF(s) that have subscribed for notification. The PCF(s) sends PCC rule(s) with NEF information, Traffic correlation ID and common EAS IP address and/or Common DNAI, as part of traffic influence data to the SMF(s) with PDU Session(s) associated with the Traffic Correlation ID. + +SMF(s) may select other candidate DNAI(s) for the PDU session(s) or a candidate new EAS IP address via the EASDF procedure e.g. due to UE(s) mobility. In this case, the SMF notifies to the NEF as in the above step 1, with the list of candidate DNAI(s) and/or EAS IP address. This may trigger NEF to re-select common DNAI or common EAS. NEF determines common EAS and/or common DNAI based on received EAS IP, list of candidate DNAI(s), number of PDU sessions SMF(s) serving for the set of UEs. + +If another DNAI/EAS IP address is selected by the NEF, it updates the common DNAI or common EAS in the UDR in the Traffic Influence data. + +NOTE: How NEF determines a common EAS/DNAI is implementation. + +#### 6.2.3.3 EAS Re-discovery Procedure at Edge Relocation + +The support for EAS rediscovery indication procedure enables the UE to refresh stale EAS information stored locally so that the UE can trigger EAS discovery procedure to discover new EAS information. + +For PDU Session with Session Breakout connectivity, the UE may indicate its support for refreshing stale EAS information to the SMF during the PDU Session Establishment procedure or, when the UE moves from EPS to 5GS for the first time, by using the PDU Session Modification procedure. If the UE indicates such support, the SMF may send to the UE the EAS rediscovery indication, with an optional impact field, so that the UE may trigger to re-discover the EAS (see the step 2 of Figure 6.2.3.3-1) after the insertion/change/removal of an L-PSA based on AF influence or its local configuration using the PDU Session Modification procedure, or based on the AF triggered EAS relocation. + +This procedure is used by the SMF to trigger the EAS rediscovery procedure when a new connection to EAS need to be established. It applies to both Session Breakout using ULCL and Session Breakout using BP. + +![Sequence diagram of the EAS re-discovery procedure at Edge relocation. The diagram shows interactions between UE, SMF, L-PSA1, L-PSA2, PSA, PCF, and AF. Step 1a shows EAS rediscovery triggered by insertion/change/removal of L-PSA. Step 1b shows EAS rediscovery triggered by AF. Step 2 shows the UE sending a response based on Figure 4.3.3.2-1 of TS23.502.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant L-PSA1 + participant L-PSA2 + participant PSA + participant PCF + participant AF + + Note right of SMF: 1a. EAS rediscovery triggered by Insertion/change/removal of L-PSA + Note right of SMF: 1b. EAS rediscovery triggered by AF + Note left of SMF: 2. Step 3b-11b in Figure 4.3.3.2-1 of TS23.502 + +``` + +Sequence diagram of the EAS re-discovery procedure at Edge relocation. The diagram shows interactions between UE, SMF, L-PSA1, L-PSA2, PSA, PCF, and AF. Step 1a shows EAS rediscovery triggered by insertion/change/removal of L-PSA. Step 1b shows EAS rediscovery triggered by AF. Step 2 shows the UE sending a response based on Figure 4.3.3.2-1 of TS23.502. + +Figure 6.2.3.3-1: EAS re-discovery procedure at Edge relocation + +During a previous EAS Discovery procedure on this PDU Session the UE may have EAS information (i.e. EAS IP address corresponding to an EAS FQDN) locally stored, e.g. acquired during the previous connection with the EAS (for more information see Annex C UE considerations for EAS (re)discovery). + +- 1a. Due to the UE mobility the SMF triggers L-PSA insertion, change or removal for the PDU Session. The insertion, change or removal of L-PSA triggers EAS rediscovery. + +The L-PSA insertion, change or removal for the PDU Session may be triggered due to update of a common DNAI. + +- 1b. The AF triggers EAS relocation e.g. due to EAS load balance or maintenance, etc. and informs the SMF the related information indicating the EAS relocation, as described in clause 4.3.6 AF influence on traffic routing procedure in TS 23.502 [3]. + +AF may request to add/remove a UE to/from a set of UEs via AF influence on traffic routing procedure in TS 23.502 [3]. The PCF updates PCC rule to SMF (i.e. adding/removal of EAS Correlation indication/indication of traffic correlation and Traffic Correlation ID to/from the PCC rule). With the update of the PCC rule, the SMF detects that the UE is belonging to a set of UE(s) for a common EAS/DNAI, or the UE is not belonging to a set of UEs for common EAS/DNAI any longer and the common EAS/DNAI is not optimized for the UE, it may trigger EAS rediscovery. + +If UE is belonging to a set of UE(s) for a common EAS/DNAI as instructed by the PCC rule, the SMF interacts with NEF for common EAS/DNAI selection as described in clauses 6.2.3.2.5 and 6.2.3.2.6. + +2. This step may be performed as part of step 1a/1b. The SMF performs the network requested PDU Session Modification procedure from the step 3b-11b as defined in clause 4.3.3.2 TS 23.502 [3]. + +If the UE has indicated that it supports to refresh EAS information stored locally corresponding to the impact field per the EAS rediscovery indication from network, the SMF may send the impact field with the EAS rediscovery indication. SMF determines the impacted EAS(s) which need be rediscovered as the following: + +- If an L-PSA is inserted/relocated/removed, the SMF determines the impact field, which is associated with the L-DN to be inserted, relocated or removed and identified by FQDN(s) or IP address range(s) of the old EAS, based on the association between FQDN(s)/IP address range(s) and DNAI provided by AF or SMF local configuration on the L-DN. +- For AF triggered EAS rediscovery, the AF may indicate the EAS rediscovery for the impacted applications, which are identified by Application Identifier(s), to the SMF via the AF influence on traffic routing procedure. + +The SMF sends PDU Session Modification Command (EAS rediscovery indication, [impact field]) to UE. The EAS rediscovery indication indicates to refresh the cached EAS information. The impact field is used to identify which EAS(s) information need to be refreshed. The impact field includes the L-DN information corresponding to the impacted EAS(s), which are identified by FQDN(s) or IP address range(s) of the old EAS(s). If the impact field is not included, it means all EAS(s) information associated with this PDU Session need to be refreshed. + +The SMF may choose new DNS settings for the PDU Session and if so, it provides them to the UE as new DNS server (see Option C in clause 6.2.3.2.3). Otherwise the UE uses the existing DNS server for EAS rediscovery. + +For the following connection with the EAS(s) for which the EAS rediscovery needs to be executed per the received EAS rediscovery indication and impact field, the UE has been instructed not to use the old EAS information stored locally. Instead it should trigger EAS discovery procedure to get new EAS information as defined in clause 6.2.3.2. + +For the Split-UE, it is not possible to provide the NAS level EAS rediscovery indication and the impact field to the TE. Annex C documents mitigations for this scenario. + +NOTE 1: In case of EAS IP Replacement (see 6.3.3.1) the support for EAS rediscovery indication procedure is not required. + +NOTE 2: Depending on the UE implementation, the EAS rediscovery indication triggers an EAS Rediscovery procedure. If the EAS rediscovery indication is not sent to the UE Application Layer or to the UE OS, then the DNS Query to discover a new EAS is triggered only if the IP flows are terminated or via application/OS implementation means, e.g. based on application redirection, other application server information or DNS cache time-to-live. If DNS cache has not expired in the Application Layer or the OS, the triggered re-discovery can lead to the old EAS. For more information see Annex C. + +NOTE 3: The active connection(s) between the UE and the EAS(s) are not impacted. + +#### 6.2.3.4 EAS Deployment Information Management + +##### 6.2.3.4.1 General + +EAS Deployment Information management refers to the capability to create, update or remove EAS Deployment Information from AF and the distribution to the SMF. The NEF is in charge of the management of EAS Deployment Information which may be stored in UDR. + +The EAS Deployment Information indicates how edge services are deployed in each Local part of the DN, the description of EAS Deployment Information is shown in Table 6.2.3.4-1. + +**Table 6.2.3.4-1 Description of EAS Deployment Information** + +| Parameters | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AF ID | Addressing information of Application Function responsible for the DNAI in the record.
[Optional]. See NOTE 1. | +| DNN | DNN for the EAS Deployment Information.
[optional] | +| S-NSSAI | S-NSSAI for the EAS Deployment Information.
[optional] | +| External Group Identifier/Internal Group Identifier | Group ID for the EAS Deployment information.
[optional]. See NOTE 2. | +| Application ID | Identifies the application for which the EAS Deployment Information corresponds to.
[optional] | +| FQDN(s) | Supported FQDN(s) for application(s) deployed in the Local part of the DN. | +| DNAI(s) | DNAI(s) for the EAS Deployment information.
[optional] | +| DNS Server Information | list of DNS server identifier (consisting of IP address and port) for each DNAI.
[optional] | +| EAS IP address range Information | IP address(es) of the EASs in the Local part of the DN or the IP address ranges (IPv4 subnetwork(s) and/or IPv6 prefix(es) of the Local part of the DN where the EAS is deployed for each DNAI.
[optional] | +| N6 traffic routing information | Information about how to forward edge traffic in the local part of DN corresponding to DNAI.
[optional] | +| NOTE 1: When an AF ID is provided, all DNAI(s) correspond to the same EHE provider.
NOTE 2: The AF may provide External Group Identifier, and NEF can map the External Group Identifier into Internal Group Identifier according to information received from UDM. For HR-SBO roaming scenario, the NEF (V-NEF) determines the HPLMN of the External Group Identifier (e.g. based on the Realm in the identifier) and invokes Nnef_UEId_Get service to indicate NEF in HPLMN to retrieve Internal Group Identifier from UDM by invoking Nudm_SDM_Get service.
NOTE 3: AF ID can be used in case of AF(s) involving different EHE providers, and the source EHE is unaware of other/target EHE specific deployment details. | | + +The EAS Deployment Information management procedures are described in this clause, the procedures are independent of any PDU Session, including: + +- The procedure for EAS Deployment Information management from AF via the NEF. +- The procedure for EAS Deployment Information management in the SMF. +- The procedure for BaselineDNSPattern management in the EASDF. + +NOTE: In order to support EAS discovery when the Edge Hosting Environment is provided by a partner, an SLA is needed between current operator and the partner to provide e.g. the Address(es) and credentials for the DNS servers if the partner hosts the DNS server(s) for the related DNS resolution. + +##### 6.2.3.4.2 EAS Deployment Information Provision from AF via NEF + +The AF provides non-PDU Session specific EAS Deployment information to 5GC via the procedure defined in this clause. + +![Sequence diagram for EAS Deployment Information management in the AF procedure. Lifelines: UDR, NEF, AF. The sequence starts with the AF sending a 1.Nnef_EASDeployment_Create/Update/Delete Request to the NEF. The NEF performs 2.NEF Handling. Then, the NEF sends a 3.Nudr_DM_Create/Update/Delete Request to the UDR. The UDR responds with 4.Nudr_DM_Create/Update/Delete Response to the NEF. Finally, the NEF sends 5.Nnef_EASDeployment_Create/Update/Delete Response to the AF.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDR + Note right of NEF: 2.NEF Handling + AF->>NEF: 1.Nnef_EASDeployment_Create/Update/Delete Request + NEF->>UDR: 3.Nudr_DM_Create/Update/Delete Request + UDR-->>NEF: 4.Nudr_DM_Create/Update/Delete Response + NEF-->>AF: 5.Nnef_EASDeployment_Create/Update/Delete Response + +``` + +Sequence diagram for EAS Deployment Information management in the AF procedure. Lifelines: UDR, NEF, AF. The sequence starts with the AF sending a 1.Nnef\_EASDeployment\_Create/Update/Delete Request to the NEF. The NEF performs 2.NEF Handling. Then, the NEF sends a 3.Nudr\_DM\_Create/Update/Delete Request to the UDR. The UDR responds with 4.Nudr\_DM\_Create/Update/Delete Response to the NEF. Finally, the NEF sends 5.Nnef\_EASDeployment\_Create/Update/Delete Response to the AF. + +**Figure 6.2.3.4.2-1 EAS Deployment Information management in the AF procedure** + +1. The AF invokes the Nnef\_EASDeployment\_Create/Update/Delete service operation. +2. NEF checks whether the AF is authorized to perform the request, and authorised to provision the EAS Deployment Information based on the operator policies. The NEF derives DNN and S-NSSAI from the AF Service Identifier if not received explicitly and translates received External Application Identifier to Application Identifier known inside MNO domain. +3. The NEF invokes the Nudr\_DM\_Create/Update/Delete to the UDR if it is authorized. +4. The UDR stores/updates/removes the corresponding information (and responds a Nudr\_DM\_Create/Update/Delete Response to the NEF). +5. The NEF sends Nnef\_EASDeployment\_Create/Update/Delete Response to the AF. + +##### 6.2.3.4.3 EAS Deployment Information Management in the SMF + +The SMF may receive the EAS Deployment Information from NEF via Subscribe /Notify procedure defined in this clause. NEF may have stored the information in UDR. + +![Sequence diagram for EAS Deployment Information management in the SMF procedure. Lifelines: SMF, NEF. The sequence starts with the SMF sending a 1.Nnef_EASDeployment_Subscribe Request to the NEF. The NEF responds with 2.Nnef_EASDeployment_Subscribe Response to the SMF. Later, the NEF sends a 3.Nnef_EASDeployment_Notify Request to the SMF. The SMF responds with 4.Nnef_EASDeployment_Notify Response to the NEF.](446100c084b94817a19c319fa776b412_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant NEF + SMF->>NEF: 1.Nnef_EASDeployment_Subscribe Request + NEF-->>SMF: 2.Nnef_EASDeployment_Subscribe Response + Note right of NEF: 3.Nnef_EASDeployment_Notify Request + NEF->>SMF: 3.Nnef_EASDeployment_Notify Request + SMF-->>NEF: 4.Nnef_EASDeployment_Notify Response + +``` + +Sequence diagram for EAS Deployment Information management in the SMF procedure. Lifelines: SMF, NEF. The sequence starts with the SMF sending a 1.Nnef\_EASDeployment\_Subscribe Request to the NEF. The NEF responds with 2.Nnef\_EASDeployment\_Subscribe Response to the SMF. Later, the NEF sends a 3.Nnef\_EASDeployment\_Notify Request to the SMF. The SMF responds with 4.Nnef\_EASDeployment\_Notify Response to the NEF. + +**Figure 6.2.3.4.3-1: EAS Deployment Information management in the SMF procedure** + +- 1-2. As pre-requisite condition, the SMF subscribes to EAS Deployment Information Change Notification from the NEF by sending Nnef\_EASDeployment\_Subscribe message. The SMF may indicate that the current status of EAS Deployment Information shall be notified immediately (if available). The SMF may indicate for which (list of) DNN and/or S-NSSAI and/or application identifier and/or Internal Group Identifier (if available) it subscribes. + +- 3-4. The NEF invokes Nnef\_EASDeployment\_Notify (EAS Deployment Information) to the SMF(s) to which the EAS Deployment Information shall be provided. If there is EAS Deployment Information available and immediate report is required, the NEF notifies the SMF(s) with such information. + +##### 6.2.3.4.4 BaselineDNSPattern Management in the EASDF + +The SMF receives EAS Deployment Information as described in clause 6.2.3.4.1, and derives BaselineDNSPattern from the EAS Deployment Information. The BaselineDNSPattern is not dedicated to a specific PDU Session. + +SMF may create/update/delete the BaselineDNSPattern in the EASDF. + +![Sequence diagram showing BaselineDNSPattern management in the EASDF procedure between SMF and EASDF.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant EASDF + Note left of SMF: 1. Trigger to create or remove the BaselineDNSPattern + SMF->>EASDF: 2. Neasdf_BaselineDNSPattern_Create/Update/Delete Request + EASDF-->>SMF: 3. Neasdf_BaselineDNSPattern_Create/Update/Delete Response + +``` + +Sequence diagram showing BaselineDNSPattern management in the EASDF procedure between SMF and EASDF. + +**Figure 6.2.3.4.4-1: BaselineDNSPattern management in the EASDF procedure** + +1. The SMF may triggered to create/update/delete the BaselineDNSPattern. + - When new EAS Deployment Information is received by the SMF. + - When any update of the EAS Deployment Information is received by the SMF. + +The BaselineDNSPattern is deducted from the EAS Deployment Information. The BaselineDNSPattern has the form as per clause 6.2.3.2.2. + +2. The SMF invokes Neasdf\_BaselineDNSPattern\_Create/Update/Delete service operation of the EASDF to create/update/delete the BaselineDNSPattern. This interaction with the EASDF is a node level procedure, i.e. independent of any PDU Session. +3. The EASDF updates the BaselineDNSPattern and acknowledges the SMF. + +For EAS Deployment Information management in HR-SBO roaming scenario, the SMF and EASDF in clause 6.2.3.4.4 are replaced by V-SMF and V-EASDF. + +### 6.2.4 EDC Functionality based DNS Query to reach EASDF/DNS Resolver/DNS Server indicated by the SMF + +In order to guarantee that the FQDN requested by the Application that intends to use EAS is resolved by the DNS Server (e.g. EASDF/DNS resolver) indicated by the SMF, the consumer in the UE uses the related EDC functionality to either: + +- 1) Send a DNS Query to the DNS Server (e.g., EASDF/DNS resolver) indicated by the SMF. + - The consumer in the UE provides to the EDC functionality the Domain Name to be resolved, + - The EDC functionality shall send the DNS Query to the DNS Server (e.g., EASDF/DNS resolver) indicated by the SMF, + - Once received, the EDC functionality shall forward the result of the DNS response (i.e., the IP address provided by the DNS resolver) to the consumer. + +or: + +- 2) Obtain the IP address of the DNS Server (e.g., EASDF/DNS resolver) indicated by the SMF (Optional). + - The consumer in the UE requests the IP address of the DNS Server (e.g. EASDF/DNS resolver) indicated by the SMF. The EDC functionality shall send to the consumer in the UE the IP address of the DNS Server (e.g. EASDF/DNS resolver) or/and it shall notify the consumer in the UE of any update; + - The consumer in the UE then generates and sends a DNS Query to the DNS Server (e.g. EASDF/DNS resolver) indicated via EDC functionality by the SMF. + +## 6.3 Edge Relocation + +### 6.3.1 General + +Edge Relocation refers to the procedures supporting EAS changes and/or PSA UPF relocation. + +Edge Relocation may be triggered by an AF request (e.g. due to the load balance between EAS instances in the EHE) or by the network (e.g. due to the UE mobility). + +With Edge Relocation, the user plane path may be re-configured to keep it optimized. This may be done by PDU Session re-establishment using SSC mode 2/3 mechanisms or Local PSA UPF relocation using UL CL and BP mechanisms. The corresponding procedures are defined in TS 23.501 [2] and TS 23.502 [3]. + +Due to Edge Relocation, the UE may need to re-discover a new EAS and establish the connectivity to the new EAS to continue the service. The re-discovery of EAS is specified in clause 6.2. + +Edge Relocation may result in AF relocation, for example, as part of initial PDU Session Establishment, a central AF may be involved. However, due to Edge Relocation another AF serving the Edge Applications is selected. + +The trigger of Edge Relocation by the network is specified in clause 4.3.6.3 of TS 23.502 [3]. Some EAS (re-)Discovery procedures in clause 6.2 may also trigger Edge Relocation. + +This clause further describes the following procedures: + +- Edge Relocation involving AF change. +- Edge Relocation using EAS IP replacement. +- AF request for simultaneous connectivity for source and target PSA. +- Packet buffering for low Packet Loss. +- Edge Relocation considering User Plane Latency Requirements. +- Edge Relocation triggered by AF +- Edge Relocation for a set of UEs for common DNAI. + +Annex F describes example procedure for EAS Relocation on Release 16 capabilities. + +For non-roaming PDU Session, the 5GC functions in the following clauses are located in the HPLMN. + +For LBO roaming PDU Session, the 5GC functions in the following clauses are located in the serving VPLMN. + +For HR-SBO PDU Sessions specified in clause 6.7, the AF may send to V-NEF an AF request to influence traffic routing as described in clause 4.3.6 of TS 23.502 [3] for supporting Edge Relocation (e.g. for the purpose of subscription to UP path management events, especially for the change of local PSA UPF in VPLMN). In this case, the steps involving PCF in the following clauses are skipped. + +### 6.3.2 Edge Relocation Involving AF Change + +This clause is related to scenarios where distributed Edge Application Server (EAS) deployed in local part of a Data Network or a central AS are relocated, and where the (E)AS relocation also implies AF relocation i.e. AF instance change. + +Application Function influence on traffic routing mechanism as described in clause 5.6.7 of TS 23.501 [2] can be applied for a relocation of the AF. In the case that AF sends AF request via NEF, the target AF may invoke Nnef\_TrafficInfluence\_Create to deliver the relocation related information, including notification target address based on the procedure described in clause 4.3.6.2 of TS 23.502 [3]. Also, the source AF or target AF may invoke Nnef\_TrafficInfluence\_Update service operation to deliver the relocation information, including AF ID and notification target address based on the procedure described in clause 4.3.6.2 of TS 23.502 [3]. + +Also if the AF relocation occurs during the early/late notification procedure described in clause 4.3.6.3 of TS 23.502 [3], the target AF invokes Nnef\_TrafficInfluence\_Create/Update at step 4e-a or Npcf\_PolicyAuthorization\_Create at step 4g-a to deliver the notification target address of the AF. In the case that AF directly interacts with PCF, the target AF may invoke Npcf\_PolicyAuthorization\_Create, or the source AF/target AF may invoke Npcf\_PolicyAuthorization\_Update service operation to deliver relocation information including notification target address based on the procedure described in clause 4.3.6.4 of TS 23.502 [3]. + +In the case of Edge relocation between two DNAI(s), an AF relocation may be triggered by SMF, e.g. due to UE mobility. In such cases, the SMF provides as described in clause 4.3.6.3 of TS 23.502 [3] during early/late notification procedure the source AF with target AF ID as defined in Table 6.2.3.4-1. Target AF ID is used by source AF to communicate with the target AF. + +### 6.3.3 Edge Relocation Using EAS IP Replacement + +EAS IP replacement enables the Local PSA UPF to replace the source/old Target EAS IP address and port number with the target/new target EAS IP address and port number for the Destination IP address and Destination Port number field of the uplink traffic and replace the target/new target EAS IP address and port number with the source/old Target EAS IP address and port number for the Source IP address and Source Port number field of the downlink traffic based on the enhanced AF Influence information for EAS IP replacement (i.e. source EAS IP address and port number, target EAS IP address and port number). The source AS IP address and port number are the destination IP address and port number of the uplink traffic, generated by UE, for a service subject to Edge Computing. The source EAS IP address is the one discovered by UE for a service subject to Edge Computing. + +EAS IP replacement requires support of TCP/TLS/QUIC context transfer between EASs. + +NOTE: The feasibility of this requirement, i.e. TCP/TLS/QUIC context transfer between EASs, depends on whether third party platforms support an individual real time TCP/TLS/QUIC context transfer between EASs. + +#### 6.3.3.1 EAS IP Replacement Procedures + +##### 6.3.3.1.1 Enabling EAS IP Replacement Procedure by AF + +![Sequence diagram illustrating the Enabling EAS IP Replacement Procedure by AF. The diagram shows interactions between UE, UL CL UPF, Local PSA, Remote PSA, SMF, PCF, NEF, AF, Target EAS, and Source EAS. The procedure consists of four main steps: 1. Establish a PDU Session; 2. Discover EAS IP address (A Source EAS IP address is resolved by UE); 3. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP) and DL traffic (Src IP: Source EAS IP, Dst IP: UE IP); 4. AF or SGC triggered EAS IP replacement procedure. Step 4 leads to two sub-steps: 5a. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP) and DL traffic (Src IP: Source EAS IP, Dst IP: UE IP); 5b. UL traffic (Src IP: UE IP, Dst IP: Target EAS IP) and DL traffic (Src IP: Target EAS IP, Dst IP: UE IP).](1b2ad37940c441d410002c05ff71c7c5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UL_CL_UPF as UL CL UPF + participant Local_PSA as Local PSA + participant Remote_PSA as Remote PSA + participant SMF + participant PCF + participant NEF + participant AF + participant Target_EAS as Target EAS + participant Source_EAS as Source EAS + + Note over UE, SMF: 1. Establish a PDU Session + Note over UE, Remote_PSA: 2. Discover EAS IP address (A Source EAS IP address is resolved by UE) + Note over UE, Source_EAS: 3. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP) and DL traffic (Src IP: Source EAS IP, Dst IP: UE IP) + Note over AF, SMF: 4. AF or SGC triggered EAS IP replacement procedure + Note over UE, Source_EAS: 5a. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP) +DL traffic (Src IP: Source EAS IP, Dst IP: UE IP) + Note over UE, Target_EAS: 5b. UL traffic (Src IP: UE IP, Dst IP: Target EAS IP) +DL traffic (Src IP: Target EAS IP, Dst IP: UE IP) + +``` + +Sequence diagram illustrating the Enabling EAS IP Replacement Procedure by AF. The diagram shows interactions between UE, UL CL UPF, Local PSA, Remote PSA, SMF, PCF, NEF, AF, Target EAS, and Source EAS. The procedure consists of four main steps: 1. Establish a PDU Session; 2. Discover EAS IP address (A Source EAS IP address is resolved by UE); 3. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP) and DL traffic (Src IP: Source EAS IP, Dst IP: UE IP); 4. AF or SGC triggered EAS IP replacement procedure. Step 4 leads to two sub-steps: 5a. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP) and DL traffic (Src IP: Source EAS IP, Dst IP: UE IP); 5b. UL traffic (Src IP: UE IP, Dst IP: Target EAS IP) and DL traffic (Src IP: Target EAS IP, Dst IP: UE IP). + +Figure 6.3.3.1.1-1: Enabling EAS IP replacement procedure by AF + +NOTE 1: This procedure covers the scenarios that the UE moves from non-EC to EC or the AF decides to enable the EAS IP replacement in the middle of a session. + +1. UE requests to establish a PDU Session. +2. UE is preconfigured with the Source EAS IP address or discovers the IP address of the application server for the service subject to Edge Computing and the Source EAS IP address is returned to the UE via EAS Discovery procedure as described in clause 6.2. +3. UE communicates with the Source EAS. +- 4a. EAS Relocation may be triggered by AF (e.g. due to the load balance between EAS instances in the EHE). When AF detects that the EAS is capable of runtime context mirroring and an optimal EAS is found, then AF decides to influence the traffic routing in 5GC. For the common DNAI case, the AF may determine that there is an optimal common DNAI (i.e. target common DNAI). The AF may select Target EAS corresponding to the target common DNAI for each UE belonging to the set of UEs. The EAS IP replacement information (i.e. source EAS IP address and port number, target EAS IP address and port number) is sent to the SMF within the AF Influence information and the SMF reconfigures the UL CL UPF for local traffic routing and Local PSA with EAS IP replacement information. + +UL CL is configured by SMF to forward UL packet to Local PSA if the destination IP address is the Source EAS IP address. + +Local PSA is configured by SMF to enforce the "Outer Header Creation" and "Outer Header Removal" as described in step 5. FARs "Outer Header Creation" and "Outer Header Removal" are reused for such an instruction from SMF to UPF. + +Detailed enhancement to the AF Influence procedure is described in clause 6.3.3.2. + +If a new Local PSA is selected by SMF, the SMF may configure the new Local PSA to buffer the uplink traffic per clause 6.3.5 and enforce the "Outer Header Creation" and "Outer Header Removal" as described in step 5. + +If AF is not notified by 5GC that the 5GC supports EAS IP replacement mechanism, the AF does not include the target EAS identifier and does not initiate the AF triggered EAS IP replacement procedure. + +If the 5GC does not support EAS IP replacement capability, the SMF should reject the AF request and step 5 is skipped. + +- 4b. EAS Relocation may be also triggered by 5GC (e.g. due to UE Mobility). For the common DNAI case, a SMF may determine that there is an optimal common DNAI (i.e. target common DNAI). If target common DNAI is not available, the SMF determines Target Common DNAI. The SMF selects the common DNAI according to clause 6.2.3.2.4. When Early/Late Notification procedure with enhancement described in clause 6.3.3.2 is triggered, the SMF notifies AF about the target DNAI or target common DNAI and may provide the capability of supporting EAS IP replacement in 5GC. Based on the target DNAI or target common DNAI, the AF selects a proper target EAS, then the AF triggers to mirror the runtime context between Source EAS and Target EAS. Once the Target EAS is ready, AF responds to SMF about the EAS IP replacement information. During the addition or change of UL CL and Local PSA as described in clause 4.3.5.4, 4.3.5.6 or 4.3.5.7 of TS 23.502 [3], SMF may (re)configure Local PSA for EAS IP address replacement between Source EAS and Target EAS. +5. Local PSA starts to perform "Outer Header Creation" and "Outer Header Removal" FARs as instructed by SMF, which results in EAS IP address replacement: + - For UL traffic, the destination IP address and port number are replaced with the Target EAS IP address and port number; + - For DL traffic, the source IP address and port number are replaced back with the Source EAS IP address and port number. + +NOTE 2: In this solution, the PSA UPF need not to understand the logic of EAS IP replacement. + +Then all subsequent uplink traffic of this EC service for this UE is forwarded to the target EAS. + +NOTE 3: AF decides when and how to stop the Source EAS from serving the UE based on its local configuration. + +##### 6.3.3.1.2 EAS IP Replacement Update upon DNAI and EAS IP Change + +![Sequence diagram for EAS IP Replacement Update upon DNAI and EAS IP Change. The diagram shows the interaction between UE, Source UL CL, Local PSA1, Target UL CL, Local PSA2, SMF, PCF, AF, Old Target EAS, and New Target EAS. The process involves UL and DL traffic redirection and SMF reconfiguration.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +The diagram illustrates the sequence of operations for EAS IP Replacement Update upon DNAI and EAS IP Change. The participants are UE, Source UL CL, Local PSA1, Target UL CL, Local PSA2, SMF, PCF, AF, Old Target EAS, and New Target EAS. The sequence is as follows: + +- 1a. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP)** flows from UE to Source UL CL. +- 1b. UL traffic (Src IP: UE IP, Dst IP: Old Target EAS IP)** flows from Source UL CL to Old Target EAS. +- DL traffic (Src IP: Source EAS IP, Dst IP: UE IP)** flows from Old Target EAS back to Source UL CL. +- DL traffic (Src IP: Old Target EAS IP, Dst IP: UE IP)** flows from Old Target EAS to Source UL CL. +- 2. SMF reconfigures UL CL and Local PSA** (indicated by a message from SMF to Source UL CL and Local PSA1). +- Steps 3-4 are same as steps 5-6 described in clause 6.3.3.1.1** (indicated by a note spanning the bottom of the diagram). + +Sequence diagram for EAS IP Replacement Update upon DNAI and EAS IP Change. The diagram shows the interaction between UE, Source UL CL, Local PSA1, Target UL CL, Local PSA2, SMF, PCF, AF, Old Target EAS, and New Target EAS. The process involves UL and DL traffic redirection and SMF reconfiguration. + +Figure 6.3.3.1.2-1: EAS IP replacement update upon DNAI and EAS IP change + +1. For UL traffic, the destination IP address is replaced with the old Target EAS IP address at Local PSA; for DL traffic, the source IP address is replaced back with the Source EAS IP address at Local PSA. +2. SMF configures Target UL CL with forwarding rules and Local PSA2 with FARs, as described in step 4 of clause 6.3.3.1.1. + +Steps 3-4 are same as steps 5-6 described in clause 6.3.3.1.1 except that the UL CL, Local PSA and Target EAS in clause 6.3.3.1.1 are replaced by Target UL CL, Local PSA2 and new Target EAS respectively. + +##### 6.3.3.1.3 Disabling EAS IP Replacement Procedure + +![Sequence diagram for Disabling EAS IP Replacement Procedure. The diagram shows the interaction between UE, UL CL UPF, Local PSA, Remote PSA, SMF, PCF, NEF, AF, Old Target EAS, and Source EAS. The process involves UL and DL traffic redirection and a notification due to UE mobility.](ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg) + +The diagram illustrates the sequence of operations for Disabling EAS IP Replacement Procedure. The participants are UE, UL CL UPF, Local PSA, Remote PSA, SMF, PCF, NEF, AF, Old Target EAS, and Source EAS. The sequence is as follows: + +- 1a. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP)** flows from UE to UL CL UPF. +- 1b. UL traffic (Src IP: UE IP, Dst IP: Old Target EAS IP)** flows from UL CL UPF to Old Target EAS. +- DL traffic (Src IP: Source EAS IP, Dst IP: UE IP)** flows from Old Target EAS back to UL CL UPF. +- DL traffic (Src IP: Old Target EAS IP, Dst IP: UE IP)** flows from Old Target EAS to UL CL UPF. +- 2. Due to UE Mobility to a Non-EC environment, Early/Late Notification is triggered.** (indicated by a message from AF to SMF). +- 3. UL traffic (Src IP: UE IP, Dst IP: Source EAS IP) and DL traffic (Src IP: Source EAS IP, Dst IP: UE IP)** flow directly between UE and Source EAS. + +Sequence diagram for Disabling EAS IP Replacement Procedure. The diagram shows the interaction between UE, UL CL UPF, Local PSA, Remote PSA, SMF, PCF, NEF, AF, Old Target EAS, and Source EAS. The process involves UL and DL traffic redirection and a notification due to UE mobility. + +Figure 6.3.3.1.3-1: Disabling EAS IP replacement procedure + +1. Local PSA performs "Outer Header Creation" and "Outer Header Removal" FARs as instructed by SMF, which results in EAS IP address replacement: + - For UL traffic, the destination IP address and port number are replaced with the old Target EAS IP address and port number; + - For DL traffic, the source IP address and port number are replaced back with the Source EAS IP address and port number. +2. Due to UE Mobility to a Non-EC environment, when Early/Late Notification is triggered for the change from the UP path status where a DNAI applies to a status where no DNAI applies, AF knows the UE moves out of EC + +environment and mirrors the runtime session context from old Target EAS to Source EAS. Once ready, the AF indicates SMF without providing source/target EAS IP addresses and port numbers, so the SMF disables the local routing at UL CL and the EAS IP replacement at Local PSA for this PDU Session. + +3. UL and DL traffic goes through Remote PSA, no EAS IP address replacement happens at Remote PSA. + +NOTE 1: AF decides when and how to stop the old Target EAS from serving the UE based on its local configuration. In case of AF relocation, AF doesn't have to disable the EAS IP Replacement in 5GC. + +#### 6.3.3.2 Enhancement to AF Influence + +The AF may additionally include Source and Target EAS IP address(es) and Port number(s) in the Nnef\_TrafficInfluence\_Create/Update or Nnef\_TrafficInfluence\_AppRelocationInfo or Nsmf\_EventExposure\_AppRelocationInfo request. Based on the Source EAS IP address(es) and Port number(s), the SMF knows which service flow(s) is(are) subject to EAS IP Replacement. + +Using Early/Late Notification procedure, the SMF may notify the AF about the capability of supporting EAS IP replacement in 5GC, the AF sends an/a early/late notification response to the SMF when EAS relocation is completed. The SMF sends the "Outer Header Creation" and "Outer Header Removal" FARs to (target) Local PSA UPF and (target) Local PSA UPF starts the EAS IP address replacement as described in clause 6.3.3.1. + +For load balancing purpose, the AF may move some UE(s) from the old Target EAS to the New Target EAS in the same L-DN identified by the DNAI. For the abnormal condition of EAS, the AF may move all the UEs being served by the source EAS to a target EAS in the same L-DN. For those purposes, the AF needs to include List of UEs, the source/old Target EAS IP address and port number for the impacted DNAI, the (new) Target EAS IP address and port number for the impacted DNAI in the Nnef\_TrafficInfluence\_Create/Update request. If 5GC does not support EAS IP replacement capability, the SMF should reject this AF request. + +The additional parameters for enabling the EAS IP Replacement are defined in clause 5.6.7.1 of TS 23.501 [2] and clauses 4.3.6.3 and 4.3.6.4 of TS 23.502 [3]. + +### 6.3.4 AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation + +EAS relocation can make use of network capabilities that, at PSA change, provide simultaneous connectivity over the source and the target PSA during a transient period. This is described in Annex F. + +AF may issue a request to the network on whether to provide simultaneous connectivity over the source and the target PSA at edge relocation. This may trigger the SMF to use a re-anchoring procedure that provides simultaneous connectivity over the source and target PSA, as described in TS 23.502 [3]: + +- For Session Breakout, in clause 4.3.5.7 for Simultaneous change of Branching Point or UL CL and additional PSA for a PDU Session. This could involve the establishment of a temporary N9 forwarding tunnel between the source UL CL and target UL CL. + +The AF request may include the following information: + +- "Keep existing PSA" indication: If this indication is included, the SMF may decide to use a re-anchoring procedure that provides simultaneous connectivity over the source and target PSA, as described above. +- "Keep existing PSA timer": its value indicates the minimum time interval to be considered for inactivity for the traffic described. It may overwrite the SMF configurable period of time for how long the existing PSA is to be maintained after all active traffic ceases to flow on it. + +AF traffic influence request via NEF is described in clause 5.2.6.7 of TS 23.502 [3]. The request to PCF is described in clauses 5.2.5.3.2 and 5.2.5.3.3 of TS 23.502 [3]. The AF request for simultaneous connectivity over the source and the target PSA at relocation is authorized by PCF. The PCF checks whether the AF has an authority to make such a request. + +Once the simultaneous connectivity over the source and the target PSA at relocation requested by AF is authorized by the PCF, the AF request including the requirements is informed to the SMF via AF influenced Traffic Steering Enforcement Control (see clause 6.3.1 of TS 23.503 [4]) in PCC rules. + +### 6.3.5 Packet Buffering for Low Packet Loss + +This procedure aims at synchronizing between EAS relocation and UL traffic from the UE, ensuring that UL traffic from the UE is sent to the new EAS only when EAS context transfer has been carried out. + +This procedure may be applied at change of local PSA. It consists of buffering uplink packets in the target PSA in order to prevent there is packet loss if the application client sends UL packets to a new EAS before the new EAS is prepared to handle them. During the buffering, the old EAS may continue to serve the UE over the former PSA. + +Buffering starts upon request by AF and continues till AF indicates otherwise. The EAS relocation procedure (e.g. the migration of the service context) happens at the application layer. That is outside the scope of 3GPP. + +As an alternative to this procedure, upper layer solutions can provide the needed synchronization between EAS relocation and UL traffic from the UE. + +NOTE 1: Upper layer solutions may still be needed when there are other EAS relocation scenarios (e.g. EAS (re)selection upon DNS cache entry expiry) not related to PSA change. + +Buffering of uplink packets is not meant to apply to all traffic being offloaded at the new PSA. AF may request the buffering for the UL traffic of applications that require so. When the AF subscribes Early/Late Notification of UP path change for a specific application, Traffic Description for this application is provided as described in clause 5.6.7 of TS 23.501 [2]. When AF receives such an Early/Late Notification and indicates that uplink traffic buffering is needed in the response (step 2 in Figure 6.3.5-1), this uplink traffic buffering is then activated for the traffic described by Traffic Description provided in the subscription to Early/Late Notification. + +NOTE 2: To request uplink traffic buffering, the AF is expected to subscribe both Early and Late Notifications. + +![Sequence diagram illustrating Packet Buffering for Low Packet Loss. The diagram shows the interaction between UE, (R)AN, UPF (UL CL), UPF (PSA0), UPF (PSA1), UPF (PSA2), SMF, AF, EAS1, and EAS2. The process involves SMF determining PSA relocation, DNAT change notification, SMF configuring PSA2, N4 Session Modification, EAS Rediscovery, EAS relocation, and finally buffered UL data transfer to the new EAS.](4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant ULCL as UPF (UL CL) + participant PSA0 as UPF (PSA0) + participant PSA1 as UPF (PSA1) + participant PSA2 as UPF (PSA2) + participant SMF + participant AF + participant EAS1 + participant EAS2 + + Note left of UE: UL/DL Data + Note right of SMF: 1. SMF determines to perform PSA relocation + SMF->>AF: 2a. DNAT change notification + AF-->>SMF: 2b. Positive response + Note right of SMF: 3. SMF configures PSA2 + SMF->>ULCL: 4a. N4 Session Modification Request + ULCL-->>SMF: 4b. N4 Session Modification Response + SMF->>AF: 5. Late Notification + Note right of UE: 6a EAS Rediscovery (as in clause 6.2.3.3) with New EAS selection + Note right of RAN: UL Data (Dst: new EAS) + Note right of AF: 6b. EAS relocation + AF-->>SMF: 7. Response for Late Notification + Note right of SMF: 8a. SMF updates PSA2 and releases PSA1 + Note right of PSA2: 8b. Buffered UL Data + Note left of UE: UL/DL Data + +``` + +Sequence diagram illustrating Packet Buffering for Low Packet Loss. The diagram shows the interaction between UE, (R)AN, UPF (UL CL), UPF (PSA0), UPF (PSA1), UPF (PSA2), SMF, AF, EAS1, and EAS2. The process involves SMF determining PSA relocation, DNAT change notification, SMF configuring PSA2, N4 Session Modification, EAS Rediscovery, EAS relocation, and finally buffered UL data transfer to the new EAS. + +Figure 6.3.5-1: Packet buffering for low packet loss + +1. The SMF decides to change the local PSA of a PDU Session with UL CL or SSC mode 3. + +2. The SMF may send an early notification to the AF after target PSA (i.e. PSA2) is selected and waits for a notification response from the AF. The AF may reply in positive to the notification by indicating that buffering of uplink traffic to the target DNAI is needed as long as traffic to the target DNAI is not authorized by the AF. This is e.g. as defined in steps 1 and 2 of TS 23.502 [3] Figure 4.3.6.3-1. +3. For the procedures with ULCL/BP, the SMF configures the PSA2 as specified in step 2 in clause 4.3.5.6 and step 2 in clause 4.3.5.7 of TS 23.502 [3], which may request the PSA2 to buffer uplink traffic. The PSA1 (i.e. source PSA) keeps receiving downlink traffic from EAS1 and send it to the UE until it is released in step 7. + +For the procedures with SSC mode 3, the SMF configures the PSA2 as specified in step 4 in clause 4.3.5.2 and in step 5-6 in clause 4.3.5.4 of TS 23.502 [3], which may request the PSA2 to buffer uplink traffic. + +4. For the procedures with ULCL/BP, the SMF sends an N4 Session Modification Request to the UL CL to update the UL CL rules regarding to the traffic flows that the SMF tries to steer to PSA2. This is e.g. as defined in TS 23.502 [3] Figure 4.3.5.7-1 step 3. +5. The SMF sends a Late Notification to the AF. This corresponds e.g. to step 4a-c of TS 23.502 [3] Figure 4.3.6.3-1 and is e.g. also described in step 9 of TS 23.502 [3] Figure 4.3.5.7-1. +- 6a. A new EAS is selected by the application (e.g. at DNS cache entry expiry, the DNS Query is resolved and the response includes a new EAS that is near the new PSA (PSA2)). Any traffic sent to the new EAS is buffered at PSA2. +- 6b. The application layer completes the EAS relocation (This corresponds to step 4d of TS 23.502 [3] Figure 4.3.6.3-1). The UE context is completely relocated from the old EAS to new EAS. The old EAS stops to serve the UE + +NOTE 3: Steps 6a and 6b are related which implies there is some sort of coordination at application layer that is outside of 3GPP scope. + +7. When EAS relocation is completed, the AF sends a notification response to the SMF. This corresponds to step 4e-g of TS 23.502 [3] Figure 4.3.6.3-1 (and is e.g. also described in step 6 or 7 of TS 23.502 [3] Figure 4.3.5.7-1) and may indicate that buffering of uplink traffic to the target DNAI is no more needed as traffic to the target DNAI /EAS is now authorized by the AF. + +If the AF is changed during EAS relocation, see the details indicated in clause 6.3.2. + +8. (if AF has indicated that buffering of uplink traffic to the target DNAI is no more needed as traffic to the target DNAI /EAS is now authorized by the AF) The SMF updates the PSA2 by indicating the PSA2 to send the buffered uplink packets (step 8b) and to stop buffering. + +The SMF releases PSA1. + +### 6.3.6 Edge Relocation Considering User Plane Latency Requirement + +Edge relocation may be performed considering user plane latency requirements provided by the AF. + +In a network deployment where the estimated user plane latency between the UE and the potential PSA-UPF is known to the SMF, the 5GC provides the enhancement of AF influence to consider the user plane latency requirements requested by the AF so that the SMF decides to relocate the PSA-UPF based on AF requested requirements. + +The AF may provide user plane latency requirements to the network via AF traffic influence request as described in clause 5.2.6.7 of TS 23.502 [3]. The user plane latency requirements may include the following information: + +- Maximum allowed user plane latency: The value of this information is the target user plane latency. The SMF may use this value to decide whether edge relocation is needed to ensure that the user plane latency does not exceed the value. The SMF may decide whether to relocate the PSA UPF to satisfy the user plane latency. + +The AF request on the user plane latency requirements are authorized by PCF. The PCF checks whether the AF has an authority to make such a request. + +Once the user plane latency requirements requested by AF is authorized by the PCF, the AF request including the requirements is informed to the SMF via AF influenced Traffic Steering Enforcement Control (see clause 6.3.1 of TS 23.503 [4]) in PCC rules. After receiving the user plane latency requirements from AF via PCF, the SMF may take + +appropriate actions to meet the requirements e.g. by reconfiguring the user plane of the PDU Session as described in the step 6 of Figure 4.3.6.2-1 in TS 23.502 [3] with the following considerations: + +- In the case that the maximum allowed user plane latency is requested, the SMF decides not to perform PSA UPF relocation if the serving PSA satisfies the maximum allowed user plane latency. Otherwise, the SMF may decide to perform PSA UPF relocation if the target PSA UPF satisfies the maximum user plane latency. The SMF may select the PSA UPF with the shortest user plane latency among the PSA UPFs satisfying the maximum user plane latency requirements. + +### 6.3.7 Edge Relocation Triggered by AF + +The AF may invoke the AF request targeting an individual UE address procedure as described in clause 4.3.6.4 of TS 23.502 [3], due to EAS relocation. The EAS relocation may be due to AF internal triggers e.g. EAS load balance or maintenance, etc. or due to UP path change notification from SMF. The EAS relocation may include AF change or AF not change. The EAS relocation can happen with or without DNAI change. The AF may include the following information: Indication for EAS Relocation, target DNAI, traffic descriptor information and N6 routing information at target DNAI in the Nnef\_TrafficInfluence\_Create/Update Request to the NEF, or Npcf\_PolicyAuthorization\_Create/Update Request to the PCF. When the PCF receives an AF request for the same application, then the latest AF request message take precedence over any previous request if the traffic descriptor information is same. + +The AF may invoke the AF request targeting a set of UEs as described in clause 4.3.6.2 of TS 23.502 [3], due to change of common EAS/common DNAI used by the set of UEs. Similar as the Edge relocation triggered by AF with target DNAI, the common DNAI is included instead of the target DNAI. + +## 6.4 Network Exposure to Edge Application Server + +### 6.4.1 General + +Some real time network information, e.g. user path latency, are useful for application layer. In this release, in order to expose network information timely to local AF, the L-PSA UPF may expose i.e. QoS monitoring results as defined in clause 5.33.3 of TS 23.501 [2], to the local AF. + +NOTE 1: Local PSA UPF can expose the QoS monitoring results to local AF via N6. How to deliver the information on N6 is out of the scope of the present document. + +NOTE 2: Sending QoS monitoring information that has not been properly integrated over time, i.e. with over-high frequency, can increase risk that the application may over-react to instantaneous radio events/conditions e.g. leading to service instability. + +### 6.4.2 Network Exposure to Edge Application Server + +#### 6.4.2.1 Usage of Nupf\_EventExposure to Report QoS Monitoring results + +The UPF may be instructed to report information about a PDU Session directly i.e. bypassing the SMF and the PCF. This reporting may target an Edge Application Server (EAS) or a local AF that itself interfaces the EAS. + +Local NEF deployed at the edge may be used to support network exposure with low latency to local AF. The local NEF may support one or more of the functionalities described in clause 6.2.5.0 of TS 23.501 [2], and may support a subset of the APIs specified for capability exposure based on local policy. In order to support the network exposure locally, the local NEF shall support Nnef\_AFSessionWithQoS service operation for the local AF. The local NEF selection by AF is described in clauses 6.2.5.0 and 6.3.14 of TS 23.501 [2]. + +The local AF subscribes the direct notification of QoS Monitoring results from the PCF via a local NEF or NEF. If the NEF detects that it is not the most suitable NEF instance to serve the local AF request, it may redirect the AF to a local NEF instance. + +NOTE 1: If the notifications need to go via the local NEF, then the local NEF needs to be involved in order to be able to map these notifications to the URI where the AF expects to receive them. + +The local AF may also use the Npcf\_PolicyAuthorization\_Create or Update service of the PCF directly. In this case, reporting is done directly from the UPF to the local AF. + +Based on the indication of direct event notification and operator's policy, the PCF includes Direct event notification method and the Target of reporting (including target local NEF address or target AF address) within the PCC rule that it provides to the SMF as described in clause 6.1.3.21 of TS 23.503 [4]. + +The SMF sends the QoS monitoring request to the RAN and N4 rules to the L-PSA UPF. If the L-PSA UPF supports such reporting, N4 rules indicate that the QoS flow needs direct notification of QoS Monitoring. When QoS monitoring of GTP-U Path(s) is used, it is also activated if needed. This is as defined in clause 5.33.3 of TS 23.501 [2]. When N4 rules indicate that the QoS flow needs direct notification of QoS Monitoring results, upon the detection of the QoS monitoring event (e.g. when threshold for the packet delay of the QoS flow is reached as defined in clause 5.33.3 of TS 23.501 [2]), the L-PSA UPF notifies the QoS Monitoring event information to the AF (directly or via Local NEF). If the L-PSA UPF supports the Nupf\_EventExposure\_Notify service operation, as defined in clause 5.2.26 of TS 23.502 [3], the L-PSA UPF sends the Nupf\_EventExposure\_Notify to the Notification Target Address indicated by the Session Reporting Rule received from the SMF. The Notification Target Address may correspond to the AF or to a local NEF. When the Notification Target Address corresponds to a Local NEF, the local NEF reports the QoS Monitoring result to the AF. + +During UE mobility, the SMF may trigger the L-PSA UPF relocation/reselection and then send the N4 rules to the new L-PSA UPF to indicate the QoS flow needs direct notification of QoS Monitoring. The UE mobility may also trigger AF relocation or local NEF reselection, then the local AF should update the subscription for local exposure with QoS monitoring results possibly via local NEF, towards the PCF. This updated /new subscription is then propagated via SMF (via PCC rule updates) and then to the L-PSA UPF via N4 rules. + +NOTE 2: The new local AF can subscribe direct notification of QoS Monitoring if Edge Relocation Involving AF Change happens as described in clause 6.3.2. + +![Sequence diagram illustrating Network exposure to Edge Application Server. Lifelines: UE, RAN, AMF, L-PSA UPF, SMF, PCF, Local NEF/NEF, AF, new AF. The sequence shows: 0. PDU Session Establishment; 1a. Setting up an AF session with required QoS procedure; 1b. Npcf_PolicyAuthorization_Subscribe; 2. PCF-initiated PDU session modification; 3. QoS Monitoring; 4a. Nupf_EventExposure_Notify; 4b. Nupf_EventExposure_Notify; 5. Event Notification; 6. PSA relocation and EAS relocation; 7. The new AF session with required QoS and QoS Monitoring are established; 8. The old AF session with required QoS and QoS Monitoring are removed.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant L-PSA UPF + participant SMF + participant PCF + participant Local NEF/NEF + participant AF + participant new AF + + Note over UE, Local NEF/NEF: 0. PDU Session Establishment + Note over PCF, AF: 1a. Setting up an AF session with required QoS procedure + AF->>PCF: 1b.Npcf_PolicyAuthorization_Subscribe + Note over UE, Local NEF/NEF: 2. PCF-initiated PDU session modification + Note over RAN, L-PSA UPF: 3.QoS Monitoring + L-PSA UPF-->>AF: 4a.Nupf_EventExposure_Notify + L-PSA UPF-->>Local NEF/NEF: 4b.Nupf_EventExposure_Notify + Local NEF/NEF-->>AF: 5.Event Notification + Note over UE, Local NEF/NEF: 6. PSA relocation and EAS relocation + Note over new AF, AF: 7. The new AF session with required QoS and QoS Monitoring are established + Note over new AF, AF: 8. The old AF session with required QoS and QoS Monitoring are removed + +``` + +Sequence diagram illustrating Network exposure to Edge Application Server. Lifelines: UE, RAN, AMF, L-PSA UPF, SMF, PCF, Local NEF/NEF, AF, new AF. The sequence shows: 0. PDU Session Establishment; 1a. Setting up an AF session with required QoS procedure; 1b. Npcf\_PolicyAuthorization\_Subscribe; 2. PCF-initiated PDU session modification; 3. QoS Monitoring; 4a. Nupf\_EventExposure\_Notify; 4b. Nupf\_EventExposure\_Notify; 5. Event Notification; 6. PSA relocation and EAS relocation; 7. The new AF session with required QoS and QoS Monitoring are established; 8. The old AF session with required QoS and QoS Monitoring are removed. + +**Figure 6.4.2.1-1: Network exposure to Edge Application Server** + +0. The UE establishes a PDU Session as defined in clause 4.3.2.2.1 of TS 23.502 [3] A L-PSA UPF is assigned for this PDU Session. +1. The AF initiates setting up an AF session with required QoS procedure as defined in clause 4.15.6.6 of TS 23.502 [3]. + +In the request, the AF may subscribe to direct notification of QoS monitoring results for the service data flow to PCF possibly via Local NEF or NEF. If so, the AF shall include the corresponding QoS monitoring parameters as defined in clause 6.1.3.21 of TS 23.503 [4] and in TS 23.502 [3]. + +The AF may also first initiate an AF Session with PCF and later subscribe to direct notification of QoS monitoring to PCF by invoking Npcf\_PolicyAuthorization\_Update service operation. + +The local AF or NEF may discover a local NEF as specified in clause 6.2.5.0 of TS 23.501 [2] and using parameters as specified in clause 6.3.14. Alternatively, if the NEF detects that it is not the most suitable NEF instance to serve the local AF request, the NEF may redirect the AF to a (more) local NEF. The NEF may use information on the L-PSA UPF for this determination. + +2. The PCF makes the policy decision and initiates the PDU Session modification procedure as defined in clause 4.3.3.2 of TS 23.502 [3], steps 1b, 3b, 4-8b. + +If the direct notification of QoS monitoring results is subscribed, the PCF includes the Direct event notification method and the Target of reporting (including target local NEF or local AF address) in the PCC rule of the service data flow as described in clause 6.1.3.21 of TS 23.503 [4]. + +If the SMF receives the Direct event notification from the PCF and the SMF determines that the L-PSA UPF supports such reporting, the SMF determines the QoS monitoring parameters based on the information received from the PCF and/or local configuration and provides them to the L-PSA UPF via N4 rules as described in clause 5.33.3.1 of TS 23.501 [2]. Otherwise the SMF activates N4 reporting for the QoS monitoring results. The PCF may determine that the duplicated notification is required, i.e. both, direct notification to the AF (i.e. sent from UPF) and notification sent to the PCF/SMF is required and indicate it to the SMF using the Direct event notification method in the PCC rule as described in clause 6.1.3.21 of TS 23.503 [4]. In this case, the SMF shall activate the N4 reporting together with the direct reporting to the local NEF/AF. + +NOTE 2: The details of the parameters for the control of the QoS monitoring as well as the PCF and SMF behaviour are described in clause 6.1.3.21 of TS 23.503 [4] and in clause 5.33.3.1 of TS 23.501 [2], respectively. + +3. The L-PSA UPF obtains QoS monitoring information as defined in clause 5.33.3 of TS 23.501 [2]. +4. The L-PSA UPF sends the notification related with QoS monitoring information over Nupf\_EventExposure\_Notify service operation. The notification is sent to Notification Target Address that may correspond (4a) to the local AF or (4b) to the local NEF. +5. If Local NEF is used, it reports the real-time network information to local AF by invoking Nnef\_EventExposure\_Notify service operation. +6. Due to e.g. UE mobility, the PSA relocation and/or EAS relocation may happen as described in clause 6.3. During the PSA and/or EAS relocation (if the event was subscribed e.g. as in step 1), the SMF notifies the (local) NEF or the AF with the PSA and/or EAS relocation, and the AF may trigger a new L-NEF discovery as in step 1. During this step, the application mechanisms may involve a new AF for this session. +7. The new AF may initiate a new AF session to (re-)subscribe the direct notification of QoS monitoring as described in steps 1-4. +8. The old AF revokes the AF session. + +NOTE 3: Step 8 can take place before step 7. + +#### 6.4.2.2 Local NEF Discovery + +As specified in clause 6.2.5.0 of TS 23.501 [2], the NRF may be used by the AF to discover the L-NEF. To become discoverable, the L-NEF registers with an NRF deployed within the operator's domain where the AF resides. + +The AF uses existing procedures as described in clause 4.17.4 of TS 23.502 [3] to discover the L-NEF. If the AF only knows the NEF and it initiates a Nnef\_AFSessionWithQoS\_Create/Update\_request procedure with an indication of direct event notification as described in clause 6.4.2.1 and clause 6.1.3.21 of TS 23.503 [4], the NEF may decide that it is not suitable for local exposure, and re-direct the request to an L-NEF as described in TS 29.500 [9]. NEF may use NRF to find a suitable L-NEF for the re-direction. + +## 6.5 Support of 3GPP Application Layer Architecture for Enabling Edge Computing + +### 6.5.1 General + +The 3GPP application layer architecture for Enabling Edge Computing that is specified in TS 23.558 [5] includes the following functional entities: + +- Edge Enabler Client (EEC). +- Edge Configuration Server (ECS). +- Edge Enabler Server (EES). + +A UE may host EEC(s) as defined in TS 23.558 [5] and support the ability to receive ECS address(es) from the 5GC and to transfer the ECS address(es) to the EEC(s). In this case, the ECS address provisioning via 5GC is described in clause 6.5.2. + +NOTE: The features described in the other clauses of this specification do not require the UE and the network to support the 3GPP application layer architecture for Enabling Edge Computing that is specified in TS 23.558 [5]. + +### 6.5.2 ECS Address Provisioning + +#### 6.5.2.1 ECS Address Configuration Information + +The ECS Address Configuration Information consists of one or more ECS Configuration Information as defined in clause 8.3.2.1 of TS 23.558 [5]. The ECS Configuration Information may contain Spatial Validity Conditions, which includes one of the following alternatives: + +- a Geographical Service Area (see TS 23.558 [5]); +- a list of TA(s); or +- a list of countries (list of MCC); +- a list of PLMN IDs (see Table 4.15.6.3d-1 of TS 23.502 [3]). + +A UE may receive multiple instances of ECS Address Configuration Information e.g., corresponding to different ECSPs (e.g., the MNO or a 3rd party service provider). + +The ECS Address Configuration Information is sent to the UE on a per PDU Session basis. The same PDU session can be used by multiple ECS providers. + +The SMF does not need to be aware of the internal structure of the ECS Address Configuration Information. + +#### 6.5.2.2 ECS Address Configuration Information Provisioning to the UE + +If the UE hosts an EEC and supports transferring the ECS address received from the 5GC to the EEC, the UE indicates in the PCO at PDU Session establishment that it supports the ability to receive ECS address(es) via NAS and to transfer the ECS Address(es) to the EEC(s) (see TS 23.502 [3]). As described in TS 23.502 [3], if the UE supports the ability to receive ECS Address Configuration Information via NAS and to transfer the ECS address(es) to the EEC(s), the UE may receive ECS Address Configuration Information from the SMF via PCO during PDU Session Establishment and/or during PDU Session Modification procedures. If Spatial Validity Condition of ECS is provided, the UE uses the appropriate ECS as defined in TS 23.558 [5]. + +The SMF may receive ECS Address Configuration Information and associated spatial validity conditions from the UDM together with SM subscription information. The UDM in the HPLMN may provide the SMF (in HPLMN in HR case, in VPLMN in LBO case) with ECS address configuration information that depends on the serving PLMN of the UE. + +The SMF determines the ECS Address Configuration Information to be sent to the UE based on UE subscription information received from UDM (as described in clause 4.15.6.3d-2 of TS 23.502 [3]). + +The SMF may decide to send updated ECS Address Configuration Information to the UE based on locally configured policy or updated UE subscription information. The PDU Session Modification procedure is used to send updated ECS Address Configuration Information to the UE as described in clause 4.3.3 of TS 23.502 [3]. + +NOTE 1: In home routed sessions, the ECS Address Configuration Information comes from the H-SMF. The traffic to the indicated Edge Configuration Server(s) can be transmitted via a PDU Session with local breakout. + +NOTE 2: Although the Service Provisioning procedure with the ECS can take place over a HR session, if the HR-SBO PDU Session is not supported for the UE, an LBO PDU Session to access the EES(s) and EAS(s) in VPLMN needs to be established. As the UE is not aware of whether a PDU Session is working in LBO or in HR mode, in this case the PDU Session used to access the EES(s) would need to use another combination of (DNN, S-NSSAI) than the PDU Session working in HR mode. If the HR-SBO PDU Session is supported for the UE, the same combination of DNN and S-NSSAI working in HR mode can be also used to access the EES(s) and EAS(s) in VPLMN. + +NOTE 3: The Service Provisioning procedure is described in TS 23.558 [5]. + +#### 6.5.2.3 ECS Address Provisioning by a 3rd Party AF + +As described in TS 23.558 [5], the Edge Configuration Server can be deployed in a 3rd party domain by a service provider. An AF in the MNO domain or, if the Edge Configuration Server is deployed in a 3rd party domain by a service provider, a 3rd party AF can use Nnef\_ParameterProvision to provide, update, or delete AF provided ECS Address Configuration Information applying on a DNN and/or S-NSSAI for a group of UE, or any UE (See clause 4.15.6.2 of TS 23.502 [3]). + +When the AF uses Nnef\_ParameterProvision to send a new AF provided ECS Address Configuration Information to the UDM (e.g. because on Application layer activity, etc.), the UDM may notify the impacted SMF(s) of the updated Subscription provided ECS Address Configuration Information and the new ECS Address Configuration Information will be sent to the UE(s) in a PDU Session Modification procedure. + +NOTE 1: Mechanisms to avoid signalling overload when the AF uses Nnef\_ParameterProvision to send new ECS Address Information to many UEs are defined in TS 23.502 [3]. + +NOTE 2: The AF provides ECS Address Configuration Information to 5GC that target any UEs or a group of UE. + +#### 6.5.2.4 ECS Address Provisioning by MNO + +The ECS Address Configuration Information can be provisioned by the MNO subscription provisioning in UDM. + +#### 6.5.2.5 Interworking with EPC + +In interworking scenarios, if the UE hosts an EEC and supports transferring the ECS address received from the 5GC to the EEC, the UE indicates in the PCO at PDN Connection establishment that it supports the ability to receive ECS address(es) via NAS and to transfer the ECS Address(es) to the EEC(s) (see TS 23.502 [3]) and the bearer modification procedure without bearer QoS update procedure is used to send updated ECS Address Configuration Information to the UE as described in clause 4.11.0a.5 of TS 23.502 [3]. + +#### 6.5.2.6 ECS Address Provisioning in Roaming + +##### 6.5.2.6.1 General + +For both LBO and HR case, the subscription data of the ECS Address Configuration Information in UDM or UDR is stored per PLMN ID. + +For the LBO case, an AF in the visited PLMN may provide the EACI via External Parameter Provisioning procedure as described in clause 4.15.6.3d in TS 23.502 [3] to UDM via H-NEF. This ECS Address Configuration Information is further provided to SMF as part of subscription information. + +For the HR case when access to EHE in VPLMN is allowed: + +- The HPLMN has the knowledge of EACI in the VPLMN: For this scenario, the AF is able to interact with NEF in HPLMN. The AF may provide the VPLMN EACI to H-NEF via External Parameter Provisioning procedure as described in clause 4.15.6.3d in TS 23.502 [3], and further to the UDM. During the HR PDU session establishment procedure, the H-SMF sends the VPLMN EACI to V-SMF and then to UE. The V-SMF does not modify, but just delivers the EACI provided by the H-SMF. +- HPLMN does not have the knowledge of EACI in VPLMN: For this scenario, the AF can't interact with NEF in HPLMN. As defined in clauses 6.5.2.6.2 and 6.5.2.6.3, V-NEF stores the VPLMN EACI received from AF deployed in the VPLMN in V-UDR, and V-SMF subscribes from V-NEF to retrieve the VPLMN EACI. During the HR PDU Session establishment, the V-SMF sends the VPLMN EACI obtained from V-NEF to the H-SMF, and H-SMF decides the VPLMN ECS Address Configuration Information sent to V-SMF and then to UE according to the PLMN ID additionally. + +NOTE: It depends on the PLMN operation that the HPLMN can decide the EACI if both VPLMN and UDM provides the EACI. + +##### 6.5.2.6.2 ECS Address Configuration Information Provision from AF via NEF in VPLMN + +The AF provides non-PDU Session specific ECS Address Configuration Information via NEF in VPLMN to 5GC is defined in this clause. + +![Sequence diagram showing ECS Address Configuration Information provisioning to UDR via NEF in VPLMN. The diagram involves three lifelines: UDR, NEF, and AF. The sequence of messages is: 1. AF sends Nnef_ECSAddress_Create/Update/Delete Request to NEF; 2. NEF performs internal handling; 3. NEF sends Nudr_DM_Create/Update/Delete Request to UDR; 4. UDR sends Nudr_DM_Create/Update/Delete Response to NEF; 5. NEF sends Nnef_ECSAddress_Create/Update/Delete Response to AF.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +``` +sequenceDiagram + participant AF + participant NEF + participant UDR + Note right of NEF: 2.NEF Handling + AF->>NEF: 1.Nnef_ECSAddress_Create/Update/Delete Request + NEF->>UDR: 3.Nudr_DM_Create/Update/Delete Request + UDR-->>NEF: 4.Nudr_DM_Create/Update/Delete Response + NEF->>AF: 5.Nnef_ECSAddress_Create/Update/Delete Response +``` + +Sequence diagram showing ECS Address Configuration Information provisioning to UDR via NEF in VPLMN. The diagram involves three lifelines: UDR, NEF, and AF. The sequence of messages is: 1. AF sends Nnef\_ECSAddress\_Create/Update/Delete Request to NEF; 2. NEF performs internal handling; 3. NEF sends Nudr\_DM\_Create/Update/Delete Request to UDR; 4. UDR sends Nudr\_DM\_Create/Update/Delete Response to NEF; 5. NEF sends Nnef\_ECSAddress\_Create/Update/Delete Response to AF. + +**Figure 6.5.2.6.2-1** ECS Address Configuration Information provisioning to UDR via NEF in VPLMN + +1. The AF invokes the Nnef\_ECSAddress\_Create /Update/Delete service operation to provide ECS Address Configuration Information to the NEF in VPLMN. +2. NEF checks whether the AF is authorized to perform the request based on the operator policies. + +If External Group Identifier is provided, the NEF determines the HPLMN of the UE(s) (e.g. based on the Realm in the identifier) and invokes Nnef\_UEId\_Get service to indicate NEF in HPLMN to retrieve Internal Group Identifier from UDM by invoking Nudm\_SDM\_Get service. + +3. The NEF invokes the Nudr\_DM\_Create/Update/Delete to the UDR in VPLMN if it is authorized. +4. The UDR stores/updates/removes the corresponding information (and responds a Nudr\_DM\_Create/Update/Delete Response to the NEF). +5. The NEF sends Nnef\_ECSAddress\_Create/Update/Delete Response to the AF. + +##### 6.5.2.6.3 ECS Address Configuration Information Provision to the SMF in VPLMN + +V-SMF supporting HR-SBO may receive the ECS Address Configuration Information from NEF in VPLMN via Subscribe/Notify procedure is defined in this clause. + +![Sequence diagram showing ECS Address Configuration Information provisioning to SMF in VPLMN. The diagram involves two participants: SMF and NEF. The sequence of messages is: 1. Nnef_ECSAddress_Subscribe Request from SMF to NEF; 2. Nnef_ECSAddress_Subscribe Response from NEF to SMF; 3. Nnef_ECSAddress_Notify Request from NEF to SMF; 4. Nnef_ECSAddress_Notify Response from SMF to NEF.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant NEF + Note left of SMF: 1. Nnef_ECSAddress_Subscribe Request + SMF->>NEF: 1.Nnef_ECSAddress_Subscribe Request + Note right of NEF: 2. Nnef_ECSAddress_Subscribe Response + NEF-->>SMF: 2.Nnef_ECSAddress_Subscribe Response + Note right of NEF: 3. Nnef_ECSAddress_Notify Request + NEF-->>SMF: 3.Nnef_ECSAddress_Notify Request + Note left of SMF: 4. Nnef_ECSAddress_Notify Response + SMF-->>NEF: 4.Nnef_ECSAddress_Notify Response + +``` + +Sequence diagram showing ECS Address Configuration Information provisioning to SMF in VPLMN. The diagram involves two participants: SMF and NEF. The sequence of messages is: 1. Nnef\_ECSAddress\_Subscribe Request from SMF to NEF; 2. Nnef\_ECSAddress\_Subscribe Response from NEF to SMF; 3. Nnef\_ECSAddress\_Notify Request from NEF to SMF; 4. Nnef\_ECSAddress\_Notify Response from SMF to NEF. + +**Figure 6.5.2.6.3-1: ECS Address Configuration Information provisioning to SMF in VPLMN** + +- 1-2. As pre-requisite condition, the SMF subscribes to ECS Address Configuration Information Change Notification from the NEF by sending Nnef\_ECSAddress\_Subscribe message. The SMF may indicate that the current status of ECS Address Configuration Information shall be notified immediately (if available). The SMF may indicate for which (list of) DNN and/or S-NSSAI and/or Internal Group Identifier (if available) it subscribes. NEF may further subscribe to ECS Address Configuration Information Change Notification from the UDR using Nudr\_DM\_Subscribe. +- 3-4. The NEF invokes Nnef\_ECSAddress\_Notify (ECS Address Configuration Information) to the SMF if the ECS Address Configuration Information is updated. If there is ECS Address Configuration Information available and immediate report is required, the NEF notifies the SMF(s) with such information immediately. NEF may retrieve the ECS Address Configuration Information from UDR using Nudr\_DM\_Query/Notify. + +## 6.6 Support of AF Guidance to PCF Determination of Proper URSP Rules + +This clause describes how an Edge Computing related AF may send guidance to PCF determination of proper URSP rules to send to the UE. + +NOTE 1: This clause can apply in all deployment models. + +An AF related with Edge computing may need to guide PCF determination of proper URSP rules. The guidance sent by the AF may apply to any UE or to a set of UE(s) e.g. identified by a Group Id. The AF may belong to the operator or to a third party. + +NOTE 2: Some examples of the delivery of such AF guidance are shown in Annex D. + +An AF may deliver such guidance to the PCF via application guidance for URSP rules determination mechanisms defined in clause 4.15.6.10 of TS 23.502 [3]. This mechanism is defined only to deliver the guidance to a PCF of the HPLMN of the UE. + +The PCF may use the AF guidance received from different AFs, UE subscription data and local operator policy to determine the URSP rules to send to a UE. If received guidance information is not consistent with UE subscription data, or the local operator policy do not allow the specific S-NSSAI and DNN provided by the AF guidance, the corresponding AF guidance shall not be used to determine URSP rules. + +- Application traffic descriptor from the application guidance is used to set the URSP Traffic Descriptor (e.g. Destination FQDNs or a regular expression in the Domain descriptor), and the PCF determines the URSP rules precedence in the URSP rule (defined in TS 23.503 [4] Table 6.6.2.1-2); + +NOTE 3: When multiple Edge Computing specific parameters for the same application are received, the PCF decides the traffic matching priority Rule precedence value of the URSP rule (defined in TS 23.503 [4] Table 6.6.2.1-2). + +- Route selection parameter from the application guidance is used to set a Route Selection Descriptor as follows: + - DNN and S-NSSAI from the Route selection parameter from the application guidance are used to set the DNN selection, Network Slice selection components in the Route Selection Descriptor of the URSP rule, respectively (defined in TS 23.503 [4] Table 6.6.2.1-3) based on the UE subscription data; + - Route selection precedence from the application guidance is used to set the Route Selection Descriptor Precedence in the Route Selection Descriptor (defined in TS 23.503 [4] Table 6.6.2.1-3); + - The spatial validity condition for the Route selection precedence from the application guidance if any are used to set the Location Criteria in the Route Selection Descriptor of the URSP rule (defined in TS 23.503 [4] Table 6.6.2.1-3). + +NOTE 4: Since the Validation Criteria are not required to be checked during the lifetime of the PDU Session, it may be left to UE implementation (e.g. URSP re-evaluation at mobility change) how well spatial validity conditions in URSPs restrict the access to a specific (DNN, S-NSSAI) to certain locations. + +URSP rules based on AF guidance should not be set as the URSP rules with the "match all" traffic descriptor. + +## 6.7 Support of the local traffic routing in VPLMN for Home Routed PDU Session for roaming (HR-SBO) + +### 6.7.1 General + +When roaming, the UE establishes a Home Routed Session that is capable of supporting session breakout in V-PLMN based on the subscription. In this scenario, the Home PLMN and Visited PLMN have an agreement on the support of the local traffic routing (i.e. session breakout performed by V-SMF also called HR-SBO) in VPLMN for the home routed session. + +After establishing the HR-SBO PDU Session, the UE can access EAS deployed in EHE in VPLMN while the UE can also access the data network in the Home PLMN. + +The reference architecture supporting this scenario is depicted in Figure 4.2-5 in clause 4.2. + +### 6.7.2 Procedure + +#### 6.7.2.1 General + +This clause describes the authorization procedure of the local traffic offloading using HR PDU Session and EAS discovery procedure supporting HR-SBO. + +#### 6.7.2.2 PDU Session establishment for supporting HR-SBO in VPLMN + +![Sequence diagram illustrating the procedure for PDU Session establishment supporting HR-SBO in VPLMN. The diagram shows interactions between UE, (R)AN, AMF, UPF (Local PSA), UPF (ULCL/BP), V-UPF, V-SMF, V-EASDF, Visited DNS Server, H-UPF, H-SMF, UDM, H-PCF, and Home DNS Server. The procedure is divided into several steps: 1. Registration Procedure (AMF receives SMF Selection Subscription data including HR-SBO allowed indication); 2. PDU Session Establishment Procedure (H-SMF authorizes the request); 3. V-SMF creates DNSContext with V-EASDF; 4A. EAS Discovery procedure with V-EASDF for HR-SBO (6.7.2.3); 4B. EAS Discovery procedure with Local DNS For HR-SBO (6.7.2.4); 4C. EAS discovery procedure with V-EASDF using IP replacement mechanism (6.7.2.X).](bccc028d0e75bc30c41528056f581545_img.jpg) + +The sequence diagram illustrates the following steps: + +- 1. Registration Procedure as in TS 23.502 clause 4.2.2.2.2** +AMF receives the SMF Selection Subscription data including the HR-SBO allowed indication +- 2. PDU Session Establishment Procedure as in 23.502 clause 4.3.2.2.2** +H-SMF authorizes the PDU Session Establishment request for HR PDU Session based on the subscription data +- 3. V-SMF creates DNSContext with V-EASDF** +- 4A. EAS Discovery procedure with V-EASDF for HR-SBO (6.7.2.3)** +- 4B. EAS Discovery procedure with Local DNS For HR-SBO (6.7.2.4)** +- 4C. EAS discovery procedure with V-EASDF using IP replacement mechanism (6.7.2.X)** + +Sequence diagram illustrating the procedure for PDU Session establishment supporting HR-SBO in VPLMN. The diagram shows interactions between UE, (R)AN, AMF, UPF (Local PSA), UPF (ULCL/BP), V-UPF, V-SMF, V-EASDF, Visited DNS Server, H-UPF, H-SMF, UDM, H-PCF, and Home DNS Server. The procedure is divided into several steps: 1. Registration Procedure (AMF receives SMF Selection Subscription data including HR-SBO allowed indication); 2. PDU Session Establishment Procedure (H-SMF authorizes the request); 3. V-SMF creates DNSContext with V-EASDF; 4A. EAS Discovery procedure with V-EASDF for HR-SBO (6.7.2.3); 4B. EAS Discovery procedure with Local DNS For HR-SBO (6.7.2.4); 4C. EAS discovery procedure with V-EASDF using IP replacement mechanism (6.7.2.X). + +**Figure 6.7.2.2-1: Procedure for PDU Session establishment supporting HR-SBO in VPLMN** + +1. During the Registration procedure, the AMF receives the HR-SBO allowed indication per DNN/S-NSNAI from the UDM in the step 14b of the procedure in the clause 4.2.2.2.2 of TS 23.502 [3]. +2. During the PDU Session Establishment procedure for Home-routed roaming as in clause 4.3.2.2.2 of TS 23.502 [3], if the UE is roaming and if the AMF had received in SMF Selection Subscription data from UDM the HR-SBO allowed indication for the DNN/S-NSSAI in the step 1, the AMF selects a V-SMF supporting HR-SBO and sends an HR-SBO allowed indication to the V-SMF in the step 2 and the step3a of the procedure in figure 4.3.2.2.2-1 in clause 4.3.2.2.2 of TS 23.502 [3]. + +If the V-SMF supporting the HR-SBO receives the HR-SBO allowed indication from AMF, the V-SMF may: + +- select UL CL/BP UPF and L-PSA UPF based on UE location information and this indication in the step 4 of the Figure 4.3.2.2.2-1 of TS 23.502 [3]. + +NOTE 1: The UL CL/BP UPF and L-PSA UPF can be co-located in the single V-UPF. + +- select a V-EASDF; +- obtain the V-EASDF IP address based on local configuration, or invoke Neasdf\_DNSContext\_Create Request including the DNN, S-NSSAI, HPLMN ID and the UE IP address set to unspecified address or to a mapped address as specified in clause 7.1.2.2 to obtain the V-EASDF IP address; and + +NOTE 2: The network needs to ensure that EASDF can disambiguate the DNS traffic of different UEs that would be allocated with same private UE IP address. This can be done by implementation and/or deployment specific means, e.g. tunnelling on N6, network instance or UE source IP address mapping. To disambiguate the DNS traffic of different UEs allocated with same private UE IP address, the V-SMF can update the Local PSA-UPF with N4 PDR and FAR including either N6 traffic routing information or network instance (as described in clause 5.6.12 of 23.501 [2]) to forward the DNS traffic to the V-EASDF. When N6 traffic routing tunnel is used, the V-SMF can configure V-EASDF with the N6 traffic routing information towards the Local PSA-UPF. Alternatively, the V-SMF can update the local UPF to translate the UE source IP address with the replaced IP address in the IP pool of the Local PSA UPF. + +- send the request for the establishment of the PDU Session supporting HR-SBO in VPLMN and optionally send the V-EASDF IP address to the H-SMF in the Nsmf\_PDUSession\_Create Request in the step 6 of the procedure in figure 4.3.2.2.2-1 in clause 4.3.2.2.2 of TS 23.502 [3]. + +The H-SMF authorizes the request for HR-SBO based on SM subscription data (i.e. HR-SBO authorization indication) in the step 7 of the procedure in the clause 4.3.2.2.2-1 of TS 23.502 [3]. + +Once the HR-SBO is authorized, the H-SMF requests and retrieves the optional VPLMN Specific Offloading Policy from H-PCF. The H-SMF generates VPLMN Specific Offloading Information (i.e. IP range(s) and/or FQDN(s) allowed to be routed to the local part of DN in VPLMN, and/or Authorized DL Session AMBR for Offloading) based on the VPLMN Specific Offloading Policy. + +If HR-SBO is authorized for the PDU session, the H-SMF provides in the Nsmf\_PDUSession\_Create Response in the step 13 of the procedure in figure 4.3.2.2.2-1 in clause 4.3.2.2.2 of TS 23.502 [3] with the following information: + +- optionally, VPLMN Specific Offloading Information that may include FQDN range, IP range, session AMBR for the local part of DN and charging policy. + +The VPLMN specific Offloading Policy may refer to either allowed or not allowed traffic for HR-SBO (the latter is being used when the HPLMN would like to ensure that certain traffic are not allowed for HR-SBO). The VPLMN Specific Offloading Policy for the allowed and not allowed traffic should be mutually exclusive, i.e., either a list of allowed or a list of not allowed traffic descriptors should be sent, but not both. The VPLMN Specific Offloading Policy can be configured in the H-SMF and tagged with Offload Identifier(s), and which VPLMN Specific Offloading Information to be sent to V-SMF can be indicated by these Offload Identifier(s) received from UDM/H-PCF. + +Similarly, H-SMF may also sends the Offload Identifier(s) as labels of the VPLMN Specific Offloading Information together with the VPLMN Specific Offloading Information to be sent to V-SMF: + +- If the given V-SMF has already received the VPLMN Specific Offloading Information corresponding to certain Offload Identifier(s), this could be indicated to the H-SMF in any subsequent request to another HR-PDU Session from the same V-SMF, and the H-SMF will in this case send only the Offload Identifier(s) as a response; +- If the VPLMN Specific Offloading Information for a given Offload Identifier is changed, for each V-SMF using the Offload Identifier, the H-SMF chooses one existing HR-SBO PDU Session using the Offload Identifier to update VPLMN Specific Offloading Information and corresponding Offload Identifier to the V-SMF via PDU Session Modification procedure as described in clause 4.3.3.3 of TS 23.502 [3]; + +NOTE 3: An Offload identifier can include a version number. In this case, a VPLMN Specific Offloading Information provided by H-SMF with a higher version number will overwrite the one with lower version number. + +- During PDU Session Release procedure as described in clause 4.3.4.3 of TS 23.502 [3], if the PDU Session is the last HR-SBO PDU Session using a given Offload Identifier on the V-SMF, the V-SMF may remove the Offload Identifier and corresponding VPLMN Specific Offloading Information based on roaming agreements. + +NOTE 4: In this Release, the HPLMN allows HR-SBO for a PDU session only if the UE IP address of the PDU Session has not been allocated in a range that may overlap with other PDU sessions to the same DNN and S-NSSAI of that HPLMN. + +- the V-EASDF IP address (corresponding to clause 6.7.2.3) or DNS server IP address of HPLMN (corresponding to clause 6.7.2.5) as DNS server address to be sent to the UE via PCO; and +- optionally, the DNS server address provided by HPLMN to be used for DNS requests related with traffic not to be subject to HR-SBO, including to configure V-EASDF corresponding to clause 6.7.2.3, or configure the UPF in VPLMN to perform IP replacement as described in clause 6.7.2.5; + +NOTE 5: In this Release, only public IP address can be used as the DNS server address provided by HPLMN. + +- optionally, the HPLMN address information (e.g. H-UPF IP address on N6) to be used by V-EASDF to build EDNS Client Subnet option for target FQDN of the DNS query which is not authorized for HR-SBO as described in clause 6.7.2.3; +- the HR-SBO authorization result (i.e. whether HR-SBO request is authorized or not). + +The H-SMF may indicate to the UE either that for the PDU Session the use of the EDC functionality is allowed or that for the PDU Session the use of the EDC functionality is required. + +If the request for HR-SBO is not authorized and DNS context has been created, the V-SMF delete the DNS context from the selected V-EASDF, and the subsequent steps related to the EASDF in this procedure are skipped. + +The detailed information of VPLMN Specific Offloading Policy is described in clause 6.4 of TS 23.503 [4]. + +NOTE 6: The VPLMN Specific Offloading Policy can be prior configured in HPLMN based on the service level agreement between the VPLMN and HPLMN. + +3. The V-SMF configures the V-EASDF with the DNS handling rules using the VPLMN Specific Offloading Information received from H-SMF or corresponding to Offload Identifier(s) received from H-SMF. + +The V-SMF optionally configures the V-EASDF with the DNS server address provided by the HPLMN as default DNS server (corresponding to clause 6.7.2.3), after the step 13 of the procedure in figure 4.3.2.2.2-1 in clause 4.3.2.2.2 of TS 23.502 [3] if they are received from H-SMF in the step 2. If V-SMF has not received the DNS server address provided by HPLMN from H-SMF in step 2, a default DNS server may be configured to V-EASDF. + +If HPLMN address information is received, the V-SMF may also configure the V-EASDF to build EDNS Client Subnet option based on this HPLMN address information for target FQDN of DNS query which is not authorized for HR-SBO. + +If the V-SMF has interacted with the V-EASDF in step 2, then the V-SMF invokes Neasdf\_DNSContext\_Update Request including UE IP address to complete the configuration of the context in the V-EASDF. + +The V-SMF configures the UL CL UPF and PSA UPF selected in the step 2 to forward DNS messages to V-EASDF. + +At N4 session establishment for a PDU Session working in HR SBO mode, the SMF in VPLMN provides to any UPF in VPLMN acting as (local) PSA for that PDU Session and capable of enforcing NAT on N6 traffic: the HPLMN ID of UE, and the DNN/S-NSSAI of the PDU Session in HPLMN for the PDU Session. + +- 4A. EAS Discovery procedure with V-EASDF is performed as described in clause 6.7.2.3. +- 4B. EAS Discovery procedure with Local DNS Server/Resolver is performed as described in clause 6.7.2.4. +- 4C. EAS discovery procedure with V-EASDF using IP replacement mechanism as described in clause 6.7.2.5. + +#### 6.7.2.3 EAS Discovery Procedure with V-EASDF for HR-SBO + +![Sequence diagram for EAS Discovery Procedure with V-EASDF for HR-SBO roaming scenario. The diagram shows interactions between UE, V-SMF, UPF (ULCL/BP), UPF (L-PSA), V-UPF, V-EASDF, PSA, DNS Server, and H-SMF, divided into VPLMN and HPLMN domains.](c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SMF + participant UPF_ULCL as UPF (ULCL/BP) + participant UPF_LPSA as UPF (L-PSA) + participant V-UPF + participant V-EASDF + participant PSA + participant DNS_Server as DNS Server + participant H-SMF + + Note right of V-EASDF: VPLMN + Note right of PSA: HPLMN + + UE->>V-EASDF: 1. DNS Query + Note right of V-EASDF: 2. The step 8 to 15 of the procedure in the clause 6.2.3.2.2 by replacing SMF and EASDF with V-SMF and V-EASDF respectively + Note right of V-EASDF: 3. UL CL/BP insertion + Note right of V-EASDF: 4. The step 17 to 18 of the procedure in the clause 6.2.3.2.2 by replacing SMF and EASDF with V-SMF, V-EASDF respectively + V-EASDF-->>UE: 5. DNS Response + +``` + +Sequence diagram for EAS Discovery Procedure with V-EASDF for HR-SBO roaming scenario. The diagram shows interactions between UE, V-SMF, UPF (ULCL/BP), UPF (L-PSA), V-UPF, V-EASDF, PSA, DNS Server, and H-SMF, divided into VPLMN and HPLMN domains. + +**Figure 6.7.2.3-1: Procedure for EAS Discovery with V-EASDF for HR-SBO roaming scenario** + +1. The DNS query sent by the UE reaches the V-EASDF via the UL CL UPF and PSA UPF in VPLMN selected in step 2 of Figure 6.7.2.2-1. + +If the target FQDN of the DNS query is not part of the FQDN authorized by the H-SMF in step 2 of Figure 6.7.2.2-1, the following a) or b) may be performed: + +- a) The V-EASDF proceeds to step 12 of Figure 6.2.3.2.2-1 where it sends the DNS query which may include the HPLMN address information as the EDNS Client Subnet option. The DNS query is sent to the DNS server address according to the DNS message handling rules provided by the V-SMF or to the default DNS server configured in the V-EASDF. Upon receiving the DNS response, the procedure proceeds immediately to step 5. + +NOTE 1: If HPLMN DNS or the default DNS server does not support the ECS option, it cannot be ensured that an AS close to H-UPF will be resolved. + +- b) The UL CL/BP UPF sends the DNS query to the DNS server address provided by HPLMN via V-UPF (if exists) and H-UPF (through N9), by modifying the packet's destination IP address (corresponding to V-EASDF) to the DNS server address provided by HPLMN on UL CL or H-UPF. For the corresponding DNS response received by H-UPF, the H-UPF or UL CL modifies the packets' destination IP address to that of the V-EASDF. + +This assumes that the UL CL is able to detect FQDN(s) in traffic sent to the IP address of the EASDF. It is thus incompatible with usage of DoT (DNS over TLS) or DoH to protect the DNS traffic exchanged between the UE and the PLMN. + +The rest of the procedure assumes the target FQDN of the DNS query is part of the FQDN authorized by the H-SMF in step 2 of Figure 6.7.2.2-1. + +2. The steps 8 to 15 of the procedure in the Figure 6.2.3.2.2-1 by replacing SMF and EASDF with V-SMF and V-EASDF respectively. + +If VPLMN Specific Offloading Information does not include FQDN range and the EAS IP address of the DNS response is not part of the IP range(s) authorized in step 2 of Figure 6.7.2.2-1, the following may be performed: + +- If the V-EASDF is not configured with the DNS server address provided by the HPLMN as default DNS server, The V-SMF indicates the V-EASDF to construct and to send another DNS query with the same FQDN and the HPLMN address information as the EDNS Client Subnet option, to the DNS server address as described in step 1) bullet a). Otherwise V-SMF indicates the V-EASDF to construct and send another DNS query with the same FQDN to the DNS server provided by HPLMN. + +- The V-SMF selects UL CL/BP and local PSA in VPLMN based on the V-EASDF notification, EAS Deployment Information in the VPLMN, VPLMN Specific Offloading Information and UE location. The V-SMF may perform insertion or change of UL CL/BP and local PSA in VPLMN. + +The V-SMF configures the UL CL/BP and local PSA for the traffic to be offloaded to the local part of DN based on the VPLMN Specific Offloading Information received from H-SMF. + +In the case of UL CL, the V-SMF configures the traffic detection rules and traffic routing rules on the UL CL UPF based on the EAS Deployment Information and the EAS addresses included in VPLMN Specific Offloading Information. + +If there is no other V-UPF between the selected UL CL/BP in this step and H-UPF, the V-SMF sets up user plane between this UL CL/BP and H-UPF via the interaction with H-SMF. Otherwise, the V-SMF sets up user plane between this ULCL/BP and the existing V-UPF. + +The V-SMF sets up user plane between the selected UL CL/BP in this step and RAN (if no other V-UPF exists between RAN and this UL CL/BP) or the V-UPF (if exists between this UL CL/BP and RAN). + +NOTE 2: If the selected UL CL/BP and local PSA in this step is the UL CL/BP and PSA selected by V-SMF in the step 2 of Figure 6.7.2.2-1, the insertion of UL CL/BP and local PSA in VPLMN will not be performed in this step. + +NOTE 3: In the home routed roaming scenario, the V-UPF selected during PDU Session establishment procedure can be deployed at a central area within VPLMN. In this case, the V-UPF is located in the user plane path between UL CL/BP UPF in VPLMN and PSA-UPF in HPLMN. In some deployments, the UL CL/BP UPF can be collocated with the V-UPF. + +- The steps 17 to 18 of the procedure in clause 6.2.3.2.2 by replacing SMF and EASDF with V-SMF and V-EASDF respectively. + +- V-EASDF sends the DNS Response to the UE. + +#### 6.7.2.4 EAS Discovery Procedure with Local DNS for HR-SBO + +![Sequence diagram for EAS Discovery Procedure with Local DNS for HR-SBO. The diagram shows interactions between UE, (R)AN, AMF, UPF (ULCL/BP), UPF (L-PSA), V-SMF, Local DNS Resolver, Local DNS Server, UPF, H-SMF, and C-DNS. The process is divided into VPLMN and HPLMN. Steps include: 0. PDU Session for HR-SBO is established; 1. ULCL/BP insertion; 2. PDU Session Modification procedure; 3. DNS Query from UE to AMF; 4. DNS message forwarding and handling; 5. DNS Response from AMF to UE.](1fd70f9959ff1e73ef1e46218d9e9a84_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant UPF_ULCL as UPF (ULCL/BP) + participant UPF_LPSA as UPF (L-PSA) + participant V_SMF as V-SMF + participant DNS_Resolver as Local DNS Resolver + participant DNS_Server as Local DNS Server + participant UPF_HPLMN as UPF + participant H_SMF as H-SMF + participant C_DNS as C-DNS + + Note right of UPF_LPSA: VPLMN | HPLMN + + Note over UE, H_SMF: 0. PDU Session for HR-SBO is established + Note over UE, H_SMF: 1. ULCL/BP insertion + Note over UE, H_SMF: 2. PDU Session Modification procedure (PDU Session Modification as in TS 23.502 clause 4.3.3.3) + + UE->>AMF: 3. DNS Query + Note over UPF_ULCL, C_DNS: 4. DNS message forwarding and handling + AMF->>UE: 5. DNS Response + +``` + +Sequence diagram for EAS Discovery Procedure with Local DNS for HR-SBO. The diagram shows interactions between UE, (R)AN, AMF, UPF (ULCL/BP), UPF (L-PSA), V-SMF, Local DNS Resolver, Local DNS Server, UPF, H-SMF, and C-DNS. The process is divided into VPLMN and HPLMN. Steps include: 0. PDU Session for HR-SBO is established; 1. ULCL/BP insertion; 2. PDU Session Modification procedure; 3. DNS Query from UE to AMF; 4. DNS message forwarding and handling; 5. DNS Response from AMF to UE. + +Figure 6.7.2.4-1: Procedure for EAS Discovery with local DNS for HR-SBO roaming scenario + +The procedure in this clause assumes that the UL CL is able to detect FQDN(s) in traffic sent to the IP address of the local DNS Server. It is thus incompatible with usage of DoT (DNS over TLS) or DoH to protect the DNS traffic exchanged between the UE and the PLMN. + +If the target FQDN of the DNS query is not part of the FQDN authorized by the H-SMF in step 2 of Figure 6.7.2.2-1, the UL CL/BP UPF is instructed to send the DNS request to the DNS server address provided by HPLMN via V-UPF (if it exists) and H-UPF (through N9), by modifying the packet's destination IP address (corresponding to local DNS Server) to the DNS server address provided by HPLMN on UL CL or H-UPF. For the corresponding DNS response received by H-UPF, the H-UPF or UL CL modifies the packets' destination IP address to that of the local DNS Server. + +The steps 0 to 5 are the same as the steps 0 to 6 of Figure 6.2.3.2.3-1 with following differences: + +- SMF is replaced with V-SMF. + - UE, (R)AN, AMF, UL CL/BP UPF, L-PSA UPF, V-SMF, Local DNS Resolver/Server are located in VPLMN. + - UPF, H-SMF, C-DNS are located in HPLMN. +0. The HR-SBO PDU Session is established. See the procedure in clause 6.7.2.2. + 1. UL CL/BP insertion. See the step 1 of the procedure in Figure 6.2.3.2.3. + 2. After UL CL/BP insertion is performed, the V-SMF sends new local DNS server address to the UE by performing PDU Session Modification procedure as in clause 4.3.3.3 of TS 23.502 [3] with following additions: + - V-SMF sends Local DNS Server/Resolver to the H-SMF in the step 1a of the procedure as in clause 4.3.3.3 of TS 23.502 [3]. + - H-SMF sends the Local DNS Server/Resolver to be sent to the UE via PCO to the V-SMF in the step 3 of the procedure in clause 4.3.3.3 of TS 23.502 [3]. + - 3-5. See the steps 4-6 of the procedure in Figure 6.2.3.2.3. + +#### 6.7.2.5 EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO + +Based on the operator's configuration and local regulations, the IP replacement mechanism may be used for EAS discovery supporting HR-SBO: + +- For supporting HR-SBO, the H-SMF sends DNS server address provided by the HPLMN included in PCO to UE via V-SMF during PDU Session Establishment/Modification procedure. The DNS query related to the edge computing (corresponding to FQDNs) can be routed to V-EASDF/Local DNS server in the VPLMN using IP replacement mechanism. + +NOTE 1: This EAS discovery procedure requests modification of IP address of DNS messages. Whether this is allowed or not is subject to local regulations. As this procedure for EAS discovery requires an UPF to detect target FQDN in DNS message, it cannot apply when DNS security applies e.g. it does not apply to usage of DoH or DoT. + +![Sequence diagram illustrating the EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO. The diagram shows interactions between UE, AMF, V-SMF, ULCL/L-PSA of VPLMN, UPF in VPLMN, V-EASDF, DNS server of VPLMN, H-PSA, DNS server of HPLMN, H-SMF, and UDM. The procedure includes registration, HR PDU session establishment, V-SMF configuration of V-EASDF and UPF, DNS query transmission, EAS discovery procedure, and DNS response handling.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant V-SMF + participant ULCL/L-PSA of VPLMN + participant UPF in VPLMN + participant V-EASDF + participant DNS server of VPLMN + participant H-PSA + participant DNS server of HPLMN + participant H-SMF + participant UDM + + Note over all: 0. Registration procedure + Note over all: 1. HR PDU session establishment procedure + Note over V-SMF, V-EASDF, UPF in VPLMN: 2. V-SMF configures the V-EASDF and the UPF in VPLMN + Note over UE, V-SMF, UPF in VPLMN: 3. DNS query + Note over UPF in VPLMN, H-PSA, DNS server of HPLMN: 4a. DNS query transmission + Note over UPF in VPLMN, V-EASDF: 4b. DNS query transmission + Note over V-SMF, V-EASDF, UPF in VPLMN: 5. EAS discovery procedure with V-EASDF for HR-SBO + Note over UE, V-SMF, UPF in VPLMN: 6. DNS response handling and transmission + +``` + +Sequence diagram illustrating the EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO. The diagram shows interactions between UE, AMF, V-SMF, ULCL/L-PSA of VPLMN, UPF in VPLMN, V-EASDF, DNS server of VPLMN, H-PSA, DNS server of HPLMN, H-SMF, and UDM. The procedure includes registration, HR PDU session establishment, V-SMF configuration of V-EASDF and UPF, DNS query transmission, EAS discovery procedure, and DNS response handling. + +**Figure 6.7.2.5-1: EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO** + +NOTE 2: This clause assumes the V-SMF has received the HR-SBO allowed indication from the AMF and supports IP replacement mechanism for HR-SBO, it also assumes the HPLMN authorizes HR-SBO in the VPLMN. + +0. The Registration procedure is described in step 1 of clause 6.7.2.2. + +1. The HR-SBO PDU Session Establishment is described in the step 2 of clause 6.7.2.2 with the following differences: + +- After step 3 in clause 4.3.2.2.2 of TS 23.502 [3], the V-SMF selects a UPF in VPLMN supporting UL CL/BP and PSA functionalities based on UE location information. + +NOTE 3: Based on the deployment of VPLMN, the selected UPF in VPLMN can support both UL CL and PSA functionalities in case that the UL CL UPF and PSA UPF are co-located. This UPF in VPLMN can be the V-UPF selected in the step 4 of clause 4.3.2.2.2 of TS 23.502 [3]. + +- The V-SMF sends the request for establishment of the PDU session supporting HR-SBO in VPLMN without the V-EASDF IP address in the step 6 of clause 4.3.2.2.2 of TS 23.502 [3]. +- If the Nsmf\_PDUSession\_Create Request received by the H-SMF does not include the V-EASDF IP address, the H-SMF constructs PCO with DNS server address field set to DNS server address provided by the HPLMN and sends the PCO to UE via V-SMF in the step 13 of clause 4.3.2.2.2 of TS 23.502 [3]. + +NOTE 4: The V-SMF can select the V-EASDF and create the DNS context in the V-EASDF before sending Nsmf\_PDUSession\_Create Request or after having received Nsmf\_PDUSession\_Create response. + +2. The V-SMF configures the V-EASDF and the UPF in VPLMN as described in step 3 of clause 6.7.2.2 with the following differences: + +- Based on the FQDN(s) received from the VPLMN Specific Offloading Information, the V-SMF indicates the UPF in VPLMN to route DNS queries for the FQDN (range) query to V-EASDF. In the case of UL CL, the V-SMF configures the UPF in VPLMN with IP replacement information (i.e. DNS server IP address and port number of HPLMN, V-EASDF IP address and port number). In uplink direction, UPF in VPLMN replaces the destination address of the DNS query targeting an FQDN eligible for HR-SBO related offload from DNS server IP address of HPLMN to V-EASDF IP address; In downlink direction, UPF in VPLMN replaces the source address of the DNS response targeting an FQDN eligible for HR-SBO related offload from V-EASDF IP address to DNS server IP address of HPLMN. + +NOTE 5: For the DNS query requiring DNS resolution in the HPLMN, the DNS resolution path is same as the normal path in the HR PDU Session. + +3. UE sends DNS query to DNS server of HPLMN. + +- 4a. If the DNS query does not match the FQDN range eligible for HR-SBO related offload, UPF in VPLMN delivers the DNS query via H-PSA through N9 and H-PSA delivers the DNS query to the DNS server of HPLMN. +- 4b. If the DNS query matches the FQDN range eligible for HR-SBO related offload, the UPF in VPLMN delivers the DNS query to V-EASDF using IP replacement mechanism. The following EAS discovery procedure is based on step 4b. +5. The EAS discovery procedure described in steps 8-18 of clause 6.2.3.2.2 applies with the following differences: + - This EAS discovery procedure is implemented in the VPLMN. + - In step 16, the V-SMF may perform insertion or change of UL CL/BP and local PSA in VPLMN as described in the step 3 of clause 6.7.2.3. +6. The V-EASDF sends the DNS response including FQDN to the UPF in VPLMN. The UPF in VPLMN replaces the source address from V-EASDF to DNS server of HPLMN in the DNS response based on the V-SMF instructions and sends this DNS response to the UE directly or via UL CL/BP of VPLMN if existing in this PDU Session. + +#### 6.7.2.6 N2 Handover with V-SMF insertion/change/removal in HR-SBO case + +This clause defines the procedure for intra-VPLMN and inter-PLMN N2-based handover for HR-SBO PDU Sessions with V-SMF insertion/change/removal. This procedure is based on Inter NG-RAN node N2-based handover with I-SMF insertion/change/removal defined in TS 23.502 [3] clause 4.23.7.3. + +The procedure assumes the UE has an HR-SBO PDU Session established as described in clause 6.7.2.2 using a source serving PLMN (e.g. involving a source V-SMF) and there is a handover to a same or different serving PLMN (e.g. involving a target V-SMF) with V-SMF change. The procedure also applies to the scenario where source or target serving network (before or after an inter-PLMN handover) is the HPLMN thus V-SMF insertion or removal happens. + +![Sequence diagram for N2-based handover with V-SMF insertion/change/removal in HR-SBO case. The diagram shows interactions between UE, Target AMF, Target V-SMF, Source V-SMF, ULCL/BP/L-PSA, V-EASDF, H-SMF, and AF. The process starts with an N2 HO initiation (Step 1) and includes steps for SM context creation, V-SMF insertion/change, DNS context creation, PDU session modification, and SM context release. Key steps include: 0. AF subscribes to H-SMF; 1. N2 HO initiation; 2. Nsmf_PDUSessionCreateSMContext Request; 3a/3b. V-SMF insertion/change; 4. Neasdf_DNSContext_Create Request; 5. select and configure V-UPF; 6. Nsmf_PDUSessionCreateSMContext Response; 7. Nsmf_PDUSession_Update Request; 8. Authorize HR-SBO and get VPLMN Specific Offloading Policy; 9. Nsmf_PDUSession_Update Response; 10. Neasdf_DNSContext_Update Request / Response; 11. PDU Session Modification Command; 12. Nsmf_PDUSession_ReleaseSMContext Request; 12. Release old V-EASDF; 12. Release old EASDF; 13. Notify of change of serving PLMN; 14. EAS Discovery procedure.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target AMF + participant Target V-SMF + participant Source V-SMF + participant ULCL/BP/L-PSA + participant V-EASDF + participant H-SMF + participant AF + + Note right of AF: 0. Subscribe to change of serving PLMN + AF-->>H-SMF: 0. Subscribe to change of serving PLMN + Note left of UE: 1. N2 HO, see Step 1 of TS 23.502 Figure 4.23.7.3.2-1 + UE->>Target AMF: 1. N2 HO + Target AMF-->>Target V-SMF: 2. Nsmf_PDUSessionCreateSMContext Request + Target V-SMF-->>H-SMF: 3a. (V-SMF insertion) Nsmf_PDUSession_Context Request / Response + H-SMF-->>Target V-SMF: 3b. (V-SMF change) Nsmf_PDUSession_Context Request / Response + Target V-SMF-->>ULCL/BP/L-PSA: 4. Neasdf_DNSContext_Create Request / Response + Note right of Target AMF: 5. select and configure V-UPF + Target AMF-->>UE: 6. Nsmf_PDUSessionCreateSMContext Response + Target V-SMF-->>H-SMF: 7. Nsmf_PDUSession_Update Request + Note right of H-SMF: 8. Authorize HR-SBO and get VPLMN Specific Offloading Policy + H-SMF-->>Target V-SMF: 9. Nsmf_PDUSession_Update Response + Target V-SMF-->>ULCL/BP/L-PSA: 10. Neasdf_DNSContext_Update Request / Response + Target AMF-->>UE: 11. PDU Session Modification Command (new DNS information to UE) + Target AMF-->>Source V-SMF: 12. Nsmf_PDUSession_ReleaseSMContext Request + Note right of Source V-SMF: 12. Release old V-EASDF + Note right of H-SMF: 12. Release old EASDF + H-SMF-->>AF: 13. Notify of change of serving PLMN (local offload possible) + Note right of UE: 14 EAS Discovery procedure with V-EASDF for HR-SBO (§ 6.7.2.3) / with Local DNS for HR-SBO (§6.7.2.4) / with V-EASDF using IP replacement mechanism (§6.7.2.5) + +``` + +Sequence diagram for N2-based handover with V-SMF insertion/change/removal in HR-SBO case. The diagram shows interactions between UE, Target AMF, Target V-SMF, Source V-SMF, ULCL/BP/L-PSA, V-EASDF, H-SMF, and AF. The process starts with an N2 HO initiation (Step 1) and includes steps for SM context creation, V-SMF insertion/change, DNS context creation, PDU session modification, and SM context release. Key steps include: 0. AF subscribes to H-SMF; 1. N2 HO initiation; 2. Nsmf\_PDUSessionCreateSMContext Request; 3a/3b. V-SMF insertion/change; 4. Neasdf\_DNSContext\_Create Request; 5. select and configure V-UPF; 6. Nsmf\_PDUSessionCreateSMContext Response; 7. Nsmf\_PDUSession\_Update Request; 8. Authorize HR-SBO and get VPLMN Specific Offloading Policy; 9. Nsmf\_PDUSession\_Update Response; 10. Neasdf\_DNSContext\_Update Request / Response; 11. PDU Session Modification Command; 12. Nsmf\_PDUSession\_ReleaseSMContext Request; 12. Release old V-EASDF; 12. Release old EASDF; 13. Notify of change of serving PLMN; 14. EAS Discovery procedure. + +**Figure 6.7.2.6-1: N2-based handover with V-SMF insertion/change/removal in HR-SBO case** + +NOTE 1: The flow above does not show all steps in clause 4.23.7.3 of TS 23.502 [3] but only those that are impacted by the support of HR-SBO. + +The procedure described in clauses 4.23.17 and 4.23.7.3 of TS 23.502 [3] (N2-based handover with I-SMF insertion/change/removal) is performed by replacing I-SMF with V-SMF and SMF with H-SMF with following modifications: + +0. The AF may subscribe to H-SMF for the event related with a mobility of the PDU Session towards a serving PLMN where local traffic offload is possible, i.e. mobility of the PDU Session either towards HPLMN or towards a VPLMN where HR-SBO is possible i.e. supported and allowed. +1. Step 1 in Figure 4.23.7.3.2-1 of TS 23.502 [3] (initiation of the N2-based handover). + +For an intra PLMN HO, the source AMF provides the target AMF with whether HR-SBO is allowed for each PDU Session of the UE. + +For an inter PLMN HO, the target T-AMF uses local policies related to the SLA with the HPLMN of the UE to determine whether HR-SBO allowed indication is sent to the V-SMF(s) for the PDU Sessions of the UE. + +NOTE 2: This means that if HR-SBO is allowed only for some users of the HPLMN and is not allowed for the UE being handed over, this will only be detected at a later step of the procedure i.e. at step 8. + +2. Step 2 in Figure 4.23.7.3.2-1 of TS 23.502 [3] takes place. + +If the T-AMF considers that HR-SBO is possible, the T-AMF selects a V-SMF supporting HR-SBO. + +- 2a (V-SMF insertion or V-SMF change) step 2 in Figure 4.23.7.3.2-1 of TS 23.502 [3] takes place. + +For V-SMF insertion and inter VPLMN V-SMF change case, the T-AMF sends an HR-SBO allowed indication to the target V-SMF in Nsmf\_PDUSession\_CreateSMContext Request as part of the step 3 of the procedure in Figure 4.23.7.3.2 of TS 23.502 [3]. + +- 2b (V-SMF removal) steps 9 to 12b in Figure 4.23.7.3.2-1 of TS 23.502 [3] take place. + +The target AMF sends to H-SMF a Nsmf\_PDUSession\_CreateSMContext request as in step 9 in Figure 4.23.7.3.2-1 of TS 23.502 [3]. + +For EAS discovery with EASDF, the H-SMF selects an EASDF in HPLMN and configures the DNS context in this EASDF (Neasdf\_DNSContext\_Create) and may select and configure UPF(s) in HPLMN. + +For EAS discovery with Local DNS Server, the H-SMF selects a Local DNS Server. + +Steps 3 to 5 are skipped if the UE moves with V-SMF removal. + +3. (V-SMF insertion or V-SMF change) step 4 or step 5 in Figure 4.23.7.3.2-1 of TS 23.502 [3]. + +- 3a. (V-SMF insertion case) The (target) V-SMF retrieves SM context from H-SMF using Nsmf\_PDUSession\_Context Request, followed by the Nsmf\_PDUSession\_Context Response. + +- 3b. (V-SMF change case) The target V-SMF retrieves SM context from the source V-SMF using Nsmf\_PDUSession\_Context Request/Response. + +In step 3b, if source and target V-SMFs belong to same VPLMN, the SM context includes Authorization Result for HR-SBO, VPLMN Specific Offloading Information, the SM context also includes (if previously received by source V-SMF from H-SMF in the case of V-SMF change) the HPLMN address information, and the DNS Server address provided by the HPLMN. + +The SM context may also include EAS information to be refreshed for EAS re-discovery, i.e. FQDN(s) corresponding to the old target DNAI selected by the source V-SMF (V-SMF change case). + +4. (V-SMF insertion or V-SMF change) The (target) V-SMF selects a new V-EASDF e.g. based on the target UE location. The (target) V-SMF invokes Neasdf\_DNSContext\_Create including the DNN, S-NSSAI and HPLMN ID to obtain the new V-EASDF address. + +In the case of V-SMF insertion, the UE IP address is set to the unspecified address in Neasdf\_DNSContext\_Create as specified in clause 7.1.2.2. + +In the case of V-SMF change with inter PLMN mobility or intra PLMN mobility, the target V-SMF shall select a new V-EASDF if it is configured to use an EASDF for the PDU Session. + +To support EAS discovery with local DNS server as described in clause 6.7.2.4, the (target) V-SMF (re-)selects a local DNS server, e.g. based on the target UE location. + +5. (V-SMF insertion or V-SMF change) The (target) V-SMF may perform UL CL/BP and local PSA insertion/change/removal as described in step 2 of Figure 6.7.2.2-1. + +NOTE 3: When there are other V-UPF(s) between UL CL/BP and H-UPF, the (target) V-SMF sets up user plane between this ULCL/BP and the V-UPF. + +6. The H-SMF (V-SMF removal) or the target V-SMF (V-SMF insertion or V-SMF change) responses to the target AMF with a Nsmf\_PDUSession\_CreateSMContext Response as in step 8 (V-SMF insertion or V-SMF change) or step 13 in Figure 4.23.7.3.2-1 of TS 23.502 [3] (V-SMF removal). + +The handover procedure further continues as defined in steps 14 onwards of Figure 4.23.7.3.2-1 of TS 23.502 [3] and then per clause 4.23.7.3.3 of TS 23.502 [3], with clause 4.23.7.3.3 of TS 23.502 [3] modified as follows: + +- 7 (V-SMF insertion or V-SMF change) when the T-AMF sends to the Target V-SMF an indication of Handover Complete within Nsmf\_PDUSession\_UpdateSMContext Request (at step 2 in Figure 4.23.7.3.3-1 of TS 23.502 [3]) the target V-SMF invokes Nsmf\_PDUSession\_Update Request to the H-SMF. + +If a V-EASDF or a local DNS server has been selected in step 4, the selected V-EASDF or local DNS server address is provided in the request. The target V-SMF needs not provide the selected V-EASDF or local DNS server address if the target V-SMF is configured to use EAS discovery with V-EASDF using IP replacement mechanism corresponding to clause 6.7.2.5. + +If the UE indicated support of refreshing stale EAS information, the V-SMF may also provide an EAS rediscovery indication and EAS information to be refreshed for EAS re-discovery if received in step 3 to the H-SMF. + +This Nsmf\_PDUSession\_UpdateSMContext Request triggers steps 8 to 11. + +8. (V-SMF insertion or V-SMF change): If the UE has changed of serving VPLMN or has moved from HPLMN to a VPLMN, the H-SMF: + +- invokes Nudm\_SDM\_Get service to get subscription data from UDM by providing serving PLMN ID to get subscription data specific to the Serving PLMN; +- authorizes the request for HR-SBO based on the SM subscription data (i.e., HR-SBO authorization indication); and +- If the HR-SBO is authorized, retrieves the VPLMN Specific Offloading Policy from H-PCF. + +9. (V-SMF insertion or V-SMF change): As defined in step 8 in clause 4.23.7.3.3 of TS 23.502 [3], the H-SMF invokes Nsmf\_PDUSession\_Update Response, providing the same HR-SBO related information as sent by the H-SMF in step 2 of Figure 6.7.2.2-1. + +The H-SMF furthermore provides V-SMF with PCO including EAS rediscovery indication and impact field based on the EAS information to be refreshed for EAS re-discovery if received at step 7. + +The target V-SMF stores the PCO including the V-EASDF address/local DNS server address, EAS rediscovery, impact field for the UE until it receives an indication of HO completion as described in step 2 in Figure 4.23.7.3.3-1 of TS 23.502 [3] or in step 11. + +If the request for HR-SBO is not authorized and a V-EASDF context had been created, the V-SMF deletes the DNS context from the selected V-EASDF, and the subsequent steps related to the HR-SBO in this procedure are skipped. + +10. (V-SMF insertion or V-SMF change): The (target) V-SMF configures the V-EASDF with the DNS handling rules as defined in step 3 of Figure 6.7.2.2-1. + +If the (target) V-SMF has interacted with the V-EASDF in step 4, the V-SMF invokes Neasdf\_DNSContext\_Update Request including UE IP address to complete the configuration of the context in the V-EASDF. + +The (target) V-SMF may configure the ULCL/L-PSA selected in the step 5 to forward DNS messages to V-EASDF. + +When the V-SMF is configured to use EAS discovery with V-EASDF using IP replacement mechanism as described in clause 6.7.2.5, the (target) V-SMF configures the UL CL/L-PSA in the VPLMN with the IP replacement information (i.e. IP address of the DNS server provided by the HPLMN, the selected V-EASDF IP address and port number and DNS traffic filtering rules related with when IP replacement applies). + +11. (V-SMF insertion or V-SMF change): The target V-SMF sends the PCO for the UE (received at step 9) in a PDU Session Modification Command sent to the UE. + +(V-SMF removal): At step 10 in Figure 4.23.7.3.3-1 of TS 23.502 [3], when receiving Nsmf\_PDUSession\_UpdateSMContext Request (Handover Complete indication), the H-SMF sends the PCO including the V-EASDF or Local DNS Server address selected in step 2b in a PDU Session Modification Command sent to the UE. If the UE indicated support of refreshing stale EAS information, the PCO may include EAS rediscovery indication. + +12. (V-SMF change or removal): When the S-AMF invokes Nsmf\_PDUSession\_ReleaseSMContext Request to inform the Source V-SMF to release the SM context of the PDU Session, e.g. at step 3a or 11a in Figure 4.23.7.3.3-1 of TS 23.502 [3], the DNS context in the old (V-)EASDF is removed by the (source) V-SMF using Neasdf\_DNSContext\_Delete service. + +(V-SMF insertion): When the target V-SMF sends Nsmf\_PDUSession\_Update Request with a Handover Complete Indication at step 6 in Figure 4.23.7.3.3-1 of TS 23.502 [3], the DNS context in the old EASDF is removed by the H-SMF using Neasdf\_DNSContext\_Delete service. + +NOTE 4: Re-selecting the old V-EASDF to reuse the existing DNS context in the case of intra-PLMN inter V-SMF mobility is not supported in this release of the specification. + +13. If the AF had subscribed in step 0 and a serving PLMN change occurred towards a PLMN where local traffic offload is possible for the PDU Session, the H-SMF notifies the AF indicating the target serving PLMN ID and DNN, S-NSSAI of the HPLMN. This may take place as soon as the H-SMF has received an indication of Handover Complete. + +14. EAS discovery procedure by UE may take place: + +(V-SMF change or V-SMF insertion): EAS Discovery procedure with V-EASDF for HR-SBO (according to clause 6.7.2.3), with Local DNS for HR-SBO (according to clause 6.7.2.4), or with V-EASDF using IP replacement mechanism (according to clause 6.7.2.5); or + +(V-SMF removal): EAS Discovery procedure with EASDF or Local DNS Server (according to clause 6.2.3.2). + +#### 6.7.2.7 Inter V-SMF mobility registration update procedure in HR-SBO case + +This clause defines the procedure for inter V-SMF intra-VPLMN and inter-PLMN mobility registration update procedure for HR-SBO PDU Sessions. This procedure is based on I-SMF insertion/change/removal defined in clauses 4.23.3 and 4.23.4.3 of TS 23.502 [3]. + +![Sequence diagram for Inter V-SMF mobility registration update in HR-SBO. Lifelines: UE, Target AMF, Target V-SMF, Source V-SMF, ULCL/BP/L-PSA, V-EASDF, H-SMF, AF. The diagram shows steps 0 through 16, including session establishment, mobility registration, V-SMF insertion/change, DNS context updates, and EASDF release.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target AMF + participant Target V-SMF + participant Source V-SMF + participant ULCL/BP/L-PSA + participant V-EASDF + participant H-SMF + participant AF + + Note right of AF: 0. Subscribe to change of serving PLMN + Note left of UE: 1. HR-SBO PDU Session establishment as defined in clause 6.7.2.2 + Note left of UE: 2. mobility registration update as in clause 4.2.2.2.2 of TS 23.502 (step 1 to 16) + Note left of Target V-SMF: 3a. (V-SMF insertion or change) Nsmf_PDUSessionCreateSMContext + Note left of Target V-SMF: 3b-1. (V-SMF removal) Nsmf_PDUSessionCreateSMContext Request + Note right of H-SMF: 3b-2. configure H-EASDF + Note left of Target V-SMF: 4a. (V-SMF insertion) Nsmf_PDUSession_Context Request / Response + Note left of Target V-SMF: 4b. (V-SMF change) Nsmf_PDUSession_Context Request / Response + Note left of V-EASDF: 5. Neasdf_DNSContext_Create request / response + Note left of Target V-SMF: 6. select and configure V-UPF + Note left of Target V-SMF: 7. (V-SMF initiated) Nsmf_PDUSession_Update Request + Note right of H-SMF: 8. Authorize HR-SBO +Nudm_SDM_Get and get +VPLMN Specific Offloading +Policy from H-PCF + Note left of Target V-SMF: 9. Nsmf_PDUSession_Update Response (VPLMN Specific Authorization) + Note left of V-EASDF: 10. Neasdf_DNSContext_Update request / response + Note left of Target V-SMF: 10a. Update V-UPF + Note left of Target V-SMF: 11. Nsmf_PDUSessionCreateSMContext Response + Note left of UE: 12. the registration continues as defined in clause 4.2.2.2.2 of TS 23.502 [3] from step 18 on + Note left of Source V-SMF: 13. Release old V-EASDF + Note right of H-SMF: 13. Release old EASDF + Note left of UE: 14. PDU Session Modification Command (new DNS information to UE) + Note right of AF: 15. Notify of change of serving PL +(local offload possible) + Note left of UE: 16. EAS Discovery procedure with V-EASDF for HR-SBO (§ 6.7.2.3) / with Local DNS for HR-SBO (§6.7.2.4) / with V-EASDF using IP replacement mechanism (§6.7.2.5) + +``` + +Sequence diagram for Inter V-SMF mobility registration update in HR-SBO. Lifelines: UE, Target AMF, Target V-SMF, Source V-SMF, ULCL/BP/L-PSA, V-EASDF, H-SMF, AF. The diagram shows steps 0 through 16, including session establishment, mobility registration, V-SMF insertion/change, DNS context updates, and EASDF release. + +Figure 6.7.2.7-1: Inter V-SMF mobility registration update in HR-SBO + +1. The UE establishes a HR-SBO PDU Session as described in clause 6.7.2.2. +2. The UE initiates Mobility Registration Update procedure to the Target AMF as described in clauses 4.23.3 and 4.2.2.2.2 of TS 23.502 [3]. During the registration procedure, the target AMF (in roaming case) receives the SMF selection data including HR-SBO allowed indication per DNN/S-NSSAI from the UDM in the step 14b of the procedure in clause 4.2.2.2.2 of TS 23.502 [3]. +- 3a. (V-SMF insertion or V-SMF change): at step 17 of clause 4.2.2.2.2 of TS 23.502 [3], the Target AMF selects and inserts a V-SMF supporting HR-SBO and provides the received HR-SBO allowed indication for the established Session for DNN, S-NSSAI in the PDUSession\_CreateSMContext Request sent to the target V-SMF. + +3b. (V-SMF removal) in case the Target AMF is an AMF of HPLMN (the UE moves from a VPLMN to HPLMN), in step 3b-1, the Target AMF sends a PDUSession\_CreateSMContext Request sent to the H-SMF. The H-SMF may select an EASDF in HPLMN and configure the DNS context in this EASDF (Neasdf\_DNSContext\_Create) and may select and configure UPF(s) in HPLMN as in step 3b-2. For the V-SMF removal case, the steps 4 to 10 are skipped. + +4a. (V-SMF insertion case) The (target) V-SMF retrieves SM context from H-SMF using Nsmf\_PDUSession\_Context Request/Response, followed by the Nsmf\_PDUSession\_Context Request/Response. + +4b. (V-SMF change case) The target V-SMF retrieves SM context from the source V-SMF using Nsmf\_PDUSession\_Context Request/Response indicating HR-SBO support in the Request in the case of an intra-PLMN V-SMF case. + +In step 4b, if source and target V-SMFs belong to same VPLMN, the SM context from the source V-SMF includes Authorization Result for HR-SBO, VPLMN Specific Offloading Information, and (if previously received by source V-SMF from H-SMF) the HPLMN address information, and the DNS Server address provided by the HPLMN. + +NOTE 1: Step 4b in inter PLMN case (the target V-SMF retrieves SM context from the source V-SMF) assumes inter PLMN agreements on context exchange at both AMF and V-SMF levels. + +5. As in step 4 of Figure 6.7.2.6-1, the (target) V-SMF may invoke Neasdf\_DNSContext\_Create. + +6. As in step 5 of Figure 6.7.2.6-1, the (target) V-SMF may perform UL CL/BP and local PSA insertion/change/removal. + +7. The target V-SMF invokes Nsmf\_PDUSession\_Update Request to the H-SMF as in step 7 of Figure 6.7.2.6-1. + +8. As in step 8 of Figure 6.7.2.6-1, the H-SMF invokes Nudm\_SDM\_Get service, authorizes the request for HR-SBO based on the SM subscription data, and retrieves the VPLMN Specific Offloading Policy from H-PCF in case the HR-SBO is authorized. + +9. As in step 9 of Figure 6.7.2.6-1, once the HR-SBO is authorized, the H-SMF sends the VPLMN Specific Offloading Information in the Nsmf\_PDUSession\_Update Response message to the target V-SMF. + +NOTE 2: As the H-SMF sends VPLMN Specific Offloading Information related with the target PLMN for inter-PLMN case, this allows to support different VPLMN Specific Offloading Information between the source and the target VPLMN. + +10. As in step 9 of Figure 6.7.2.6-1, the (target) V-SMF may configure the V-EASDF based on the received VPLMN Specific Offloading Information. + +10a. The (target) V-SMF may also update the configuration of the V-UPF based on the received VPLMN Specific Offloading Information. + +11. As in step 6 of Figure 6.7.2.6-1, the target V-SMF (in the case of V-SMF removal, the H-SMF) answers to the target AMF with PDUSession\_CreateSMContext Response. + +12. The registration procedure continues as defined in clause 4.2.2.2.2 of TS 23.502 [3] from step 18 on. + +13. In the case of V-SMF removal or change, when, at step 17a of clause 4.23.4.3 of TS 23.502 [3], receiving Nsmf\_PDUSession\_ReleaseSMContext Request from the source AMF, the source V-SMF initiates a Neasdf\_DNSContext\_Delete if a V-EASDF was used for the PDU Session. + +In the case of V-SMF insertion, when at step 9 the H-SMF sends to the V-SMF VPLMN Specific Offloading Information in Nsmf\_PDUSession\_Update Response, the DNS context in the old EASDF may be removed by the H-SMF using Neasdf\_DNSContext\_Delete service. + +14. (V-SMF insertion or V-SMF change): The target V-SMF sends the DNS information for the UE (received at step 9) and EAS rediscovery indication via PCO in a PDU Session Modification Command sent to the UE. + +(In the case of V-SMF removal): the H-SMF sends the DNS information (received at step 3) for the UE and EAS rediscovery indication via PCO in a PDU Session Modification Command sent to the UE. + +15. As in step 13 of Figure 6.7.2.6 -1, notification from H-SMF to the AF. + +16. As in step 14 of Figure 6.7.2.6 -1: EAS discovery procedure by UE may take place. + +#### 6.7.2.8 N2 Handover without V-SMF change in HR-SBO case + +This clause defines the procedure for intra-VPLMN N2-based handover without V-SMF change for HR-SBO PDU Session. This procedure is based on Inter NG-RAN node N2-based handover without I-SMF change defined in TS 23.502 [3] clause 4.23.7.2. + +The procedure described in clauses 4.23.17, 4.23.7.2, 4.9.1.3.2 and 4.9.1.3.3 of TS 23.502 [3] is performed by replacing I-SMF with V-SMF and SMF with H-SMF with following modifications: + +- Preparation phase, step 3 of clause 4.9.1.3.2: the source AMF provides the target AMF with whether HR-SBO is allowed for each PDU Session of the UE. +- Preparation phase, after step 4 of clause 4.9.1.3.2: + +For EAS discovery with V-EASDF as described in clause 6.7.2.3, the V-SMF may (re-)select a new V-EASDF or reuse the existing V-EASDF based on the target UE location. The V-SMF may invoke Neasdf\_DNSContext\_Create including the DNN, S-NSSAI and HPLMN ID to obtain the new V-EASDF address. + +For EAS discovery with local DNS server as described in clause 6.7.2.4, the V-SMF may (re-)select a local DNS server, e.g. based on the target UE location. + +- Preparation phase, steps 5-6 of clause 4.9.1.3.2: + +The V-SMF may perform UL CL/BP and local PSA insertion/change/removal as described in step 2 of Figure 6.7.2.2-1. + +NOTE: When there are other V-UPF(s) between UL CL/BP and H-UPF, the V-SMF sets up user plane between this ULCL/BP and the V-UPF. + +- Execution phase, after step 7 of clause 4.9.1.3.3: + +The V-SMF removes the DNS Context in the old V-EASDF if a new V-EASDF is selected. + +- Execution phase, step 10a of clause 4.23.7.2.3 and 4.9.1.3.3: + +The V-SMF invokes Nsmf\_PDUSession\_Update Request toward the H-SMF. + +If a V-EASDF or a local DNS server has been selected, the selected V-EASDF or local DNS server address is provided in the request. The V-SMF needs not provide the selected V-EASDF or local DNS server address if the V-SMF is configured to use EAS discovery with V-EASDF using IP replacement mechanism corresponding to clause 6.7.2.5. + +If the UE indicated support of refreshing stale EAS information, the V-SMF may also provide an EAS rediscovery indication and EAS information to be refreshed for EAS re-discovery corresponding to the old target DNAI if it has been inserted by the V-SMF. + +The H-SMF invokes Nsmf\_PDUSession\_Update Response toward the V-SMF including the PCO for the UE. The PCO may include V-EASDF or local DNS Server address, EAS rediscovery indication and impact field which is generated based on EAS information to be refreshed for EAS re-discovery. + +- Execution phase, after step 10 of clause 4.9.1.3.3: + +The V-SMF sends the PCO in a PDU Session Modification Command sent to the UE. + +#### 6.7.2.9 Xn Handover with V-SMF change in HR-SBO case + +This clause defines the procedure for Xn handover with intra-PLMN V-SMF change for HR-SBO PDU Session. This procedure is based on Xn based handover with re-allocation of I-SMF defined in TS 23.502 [3] clause 4.23.11.3. + +The procedure described in clauses 4.23.17 and 4.23.11.3 of TS 23.502 [3] is performed by replacing I-SMF with V-SMF and SMF with H-SMF with following modifications: + +- step 4 of clause 4.23.11.3: + +The target V-SMF retrieves SM context from the source V-SMF. + +- The SM context includes Authorization Result for HR-SBO, VPLMN Specific Offloading Information. It may also include Offload Identifier(s). +- The SM context also includes (if previously received by source V-SMF from H-SMF) the HPLMN address information, and the DNS Server address provided by the HPLMN. +- The SM context also includes EAS information to be refreshed for EAS rediscovery, i.e. the FQDN(s) corresponding to the old target DNAI if it has been inserted by the source V-SMF. + +The V-SMF selects a new V-EASDF, e.g. based on the target UE location. The V-SMF may invoke `Neasdf_DNSContext_Create` including the DNN, S-NSSAI and HPLMN ID to obtain the new V-EASDF address. + +To support EAS discovery with local DNS server as described in clause 6.7.2.4, the V-SMF selects a local DNS server, e.g. based on the target UE location. + +The V-SMF may perform UL CL/BP and local PSA insertion as described in step 2 of Figure 6.7.2.2-1. + +NOTE: When there are other V-UPF(s) between UL CL/BP and H-UPF, the V-SMF sets up user plane between this ULCL/BP and the V-UPF. + +- step 6 of clause 4.23.11.3: + +If a V-EASDF or a local DNS server has been selected in step 4, the selected V-EASDF or local DNS server address is provided in the `Nsmf_PDUSession_Update` Request. + +The target V-SMF needs not provide the selected V-EASDF or local DNS server address if the target V-SMF is configured to use EAS discovery with V-EASDF using IP replacement mechanism corresponding to clause 6.7.2.5. + +If the UE indicated support of refreshing stale EAS information, the target V-SMF may also provide an EAS rediscovery indication and EAS information to be refreshed for EAS re-discovery if received in step 4 to the H-SMF. + +- step 9 of clause 4.23.11.3: the H-SMF includes the same HR-SBO related information as sent by the H-SMF in step 2 of Figure 6.7.2.2-1. + +The H-SMF furthermore provides the target V-SMF with EAS rediscovery indication to be sent to the UE and also impact field based on the EAS information to be refreshed for EAS re-discovery if received at step 6. + +The target V-SMF configures the V-EASDF with the DNS handling rules as defined in step 3 of Figure 6.7.2.2-1. + +If the target V-SMF has interacted with the V-EASDF in step 4, the target V-SMF invokes `Neasdf_DNSContext_Update` Request including UE IP address to complete the configuration of the context in the V-EASDF. + +The target V-SMF may configure the V-UPF selected in the step 4 to forward DNS messages to V-EASDF. + +When the target V-SMF is configured to use EAS discovery with V-EASDF using IP replacement mechanism as described in clause 6.7.2.5, the V-SMF configures the UPF in the VPLMN with the IP replacement information (i.e. IP address of the DNS server provided by the HPLMN, the selected V-EASDF IP address and port number and DNS traffic filtering rules related with when IP replacement applies). + +The target V-SMF sends the PCO including the V-EASDF address/local DNS server address, EAS rediscovery, impact field for the UE in a PDU Session Modification Command sent to the UE. + +- step 12a of clause 4.23.11.3: + +When the AMF invokes `Nsmf_PDUSession_ReleaseSMContext` Request to inform the Source V-SMF to release the SM context of the PDU Session, the DNS context in the old V-EASDF is removed by the source V-SMF using `Neasdf_DNSContext_Delete` service. + +#### 6.7.2.10 Xn Handover without V-SMF change in HR-SBO case + +This clause defines the procedure for Xn handover without V-SMF change for HR-SBO PDU Session. This procedure is based on Xn based handover without change of I-SMF defined in TS 23.502 [3] clause 4.23.11.5. + +The procedure described in clauses 4.23.17 and 4.23.11.5 of TS 23.502 [3] is performed by replacing I-SMF with V-SMF and SMF with H-SMF with following modifications: + +- step 2 of clause 4.23.11.5: + +When the V-SMF receives Nsmf\_PDUSession\_UpdateSMContext Request, the V-SMF may (re-)select a new V-EASDF or reuse the existing V-EASDF based on the target UE location. The V-SMF may invoke Neasdf\_DNSContext\_Create including the DNN, S-NSSAI and HPLMN ID to obtain the new V-EASDF address. + +For EAS discovery with local DNS server as described in clause 6.7.2.4, the V-SMF may (re-)select a local DNS server, e.g. based on the target UE location. + +The V-SMF may perform UL CL/BP and local PSA insertion/change/removal as described in step 2 of Figure 6.7.2.2-1. + +NOTE: When there are other V-UPF(s) between UL CL/BP and H-UPF, the V-SMF sets up user plane between this ULCL/BP and the V-UPF. + +The V-SMF invokes Nsmf\_PDUSession\_Update Request toward the H-SMF. + +If a V-EASDF or a local DNS server has been selected, the selected V-EASDF or local DNS server address is provided in the request. The V-SMF needs not provide the selected V-EASDF or local DNS server address if the V-SMF is configured to use EAS discovery with V-EASDF using IP replacement mechanism corresponding to clause 6.7.2.5. + +If the UE indicated support of refreshing stale EAS information, the V-SMF may also provide an EAS rediscovery indication and EAS information to be refreshed for EAS re-discovery corresponding to the old target DNAI if it has been inserted by the V-SMF. + +The V-SMF is responsible of when to remove the context in the old V-EASDF. + +- step 6 of clause 4.23.11.5: + +The Nsmf\_PDUSession\_Update Response sent by the H-SMF towards the V-SMF includes the PCO for the UE. The PCO may include V-EASDF or local DNS Server address, EAS rediscovery indication and impact field which is generated based on EAS information to be refreshed for EAS re-discovery. + +The V-SMF sends the PCO in a PDU Session Modification Command sent to the UE. + +### 6.7.3 EAS Re-discovery and Edge Relocation Procedure + +#### 6.7.3.1 General + +The EAS re-discovery and edge relocation in VPLMN can be triggered due to UE mobility, AF interacting with HPLMN, or AF interacting with VPLMN. + +#### 6.7.3.2 Network triggered EAS change in HR-SBO context + +Figure 6.7.3.2-1 shows the procedure of EAS re-discovery and edge relocation when HR-SBO is supported and allowed in the target serving PLMN. + +![Sequence diagram for Network triggered EAS rediscovery and edge relocation in HR-SBO context procedure. Lifelines: UE, V-SMF, V-NEF, H-SMF, H-NEF, AF. The diagram shows steps 0a, 0b, 1, 2a, 2b, 3a, 3b, 4, and 5. Steps 0a and 0b are grouped in a dashed box. Steps 1, 2a, 2b, and 3a are grouped in another dashed box. Step 5 is in a dashed box.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SMF + participant V-NEF + participant H-SMF + participant H-NEF + participant AF + + Note right of V-SMF: 0a. Inter V-SMF inter PLMN N2 handover or mobility registration update in HR-SBO case + Note right of V-SMF: 0b. Inter V-SMF intra PLMN N2/Xn handover or mobility registration update in HR-SBO case + Note right of H-SMF: 1. Step 13 at Figure 6.7.2.6 (Change of serving PLMN, local Offload possible) + Note right of AF: 2a. AF triggered EAS Re-discovery via H-NEF and H-SMF as described in clause 4.3.6 of TS 23.502 + Note right of V-NEF: 2b. AF triggered EAS Re-discovery via V-NEF and V-SMF as described in clause 4.3.6 of TS 23.502 + Note right of H-SMF: 3a. (H-SMF initiated) Nsmf_PDUSession_Update + Note right of V-SMF: 3b. (V-SMF initiated) Nsmf_PDUSession_Update + Note right of V-SMF: 4. PDU Session Modification Command (EAS rediscovery indication) + Note right of V-SMF: 5. Configure V-UPF + + Note left of UE: 0a. Inter V-SMF inter PLMN N2 handover or mobility registration update in HR-SBO case + Note left of UE: 0b. Inter V-SMF intra PLMN N2/Xn handover or mobility registration update in HR-SBO case + + Note right of H-SMF: 1. Step 13 at Figure 6.7.2.6 (Change of serving PLMN, local Offload possible) + Note right of AF: 2a. AF triggered EAS Re-discovery via H-NEF and H-SMF as described in clause 4.3.6 of TS 23.502 + Note right of V-NEF: 2b. AF triggered EAS Re-discovery via V-NEF and V-SMF as described in clause 4.3.6 of TS 23.502 + + Note right of H-SMF: 3a. (H-SMF initiated) Nsmf_PDUSession_Update + Note right of V-SMF: 3b. (V-SMF initiated) Nsmf_PDUSession_Update + + Note right of V-SMF: 4. PDU Session Modification Command (EAS rediscovery indication) + + Note right of V-SMF: 5. Configure V-UPF + +``` + +Sequence diagram for Network triggered EAS rediscovery and edge relocation in HR-SBO context procedure. Lifelines: UE, V-SMF, V-NEF, H-SMF, H-NEF, AF. The diagram shows steps 0a, 0b, 1, 2a, 2b, 3a, 3b, 4, and 5. Steps 0a and 0b are grouped in a dashed box. Steps 1, 2a, 2b, and 3a are grouped in another dashed box. Step 5 is in a dashed box. + +**Figure 6.7.3.2-1: Network triggered EAS rediscovery and edge relocation in HR-SBO context procedure** + +0. The procedures described in clauses 6.7.2.6, 6.7.2.7 and 6.7.2.9 are performed: inter V-SMF inter-PLMN N2 handover or mobility registration (0a) in the HR-SBO case; or inter V-SMF intra-PLMN N2 handover or Xn handover or mobility registration update (0b) in the HR-SBO case. +1. In the case of the procedures happened in step 0a, if the AF had subscribed to the corresponding event and a serving PLMN change occurred towards a PLMN where local traffic offload is possible for the PDU Session, the H-SMF notifies the AF, indicating the new serving PLMN ID as well as HPLMN DNN and S-NSSAI for HR-SBO session. This may take place as soon as the H-SMF has received an indication of Handover Complete (see step 13 of Figure 6.7.2.6-1). + +NOTE: Via this mechanism, the AF is aware of the PLMN to contact to issue traffic influence requests for HR-SBO sessions, if available, with HPLMN DNN and S-NSSAI information. The AF is assumed to check whether it has an SLA with the new serving PLMN. If the AF has no SLA with the new serving VPLMN, the AF interacts with H-NEF to issue traffic influence requests. + +This may trigger the AF triggered edge relocation / EAS rediscovery as defined in step 1b of Figure 6.2.3.3-1 and in step 4a of Figure 6.3.3.1.1-1. + +- 2a. For AF triggered EAS re-discovery and edge relocation via interacting with HPLMN, the AF may indicate the EAS rediscovery for the impacted applications, which are identified by Application Identifier(s), to the H-SMF via the H-PCF using the AF influence on traffic routing procedure as described in clause 4.3.6 of TS 23.502 [3]. The AF may also provide EAS IP replacement information and target DNAI together with an indication of the PLMN associated with this target DNAI, i.e. the serving PLMN ID. +- 2b. For AF triggered EAS re-discovery and edge relocation via interacting with serving VPLMN, the AF may indicate the EAS rediscovery for the impacted applications via the V-NEF using the procedure described in clause 4.3.6 of TS 23.502 [3]. + +This may trigger step 2 of Figure 6.2.3.3-1 where the SMF that initiates PDU Session modification is the V-SMF that initiates Nsmf\_PDUSession\_Update request with the requested PCO. + +The AF may also provide EAS IP replacement information and target DNAI to the VPLMN (i.e. V-SMF). In this case, steps 3-4 are skipped. + +- 3a. (For AF triggered EAS re-discovery and edge relocation via interacting with HPLMN case): The AF traffic influence request information is sent to H-SMF via PCC rule. This may trigger step 2 of Figure 6.2.3.3-1 where the SMF that initiates the PDU Session modification is the H-SMF. The H-SMF issues a Nsmf\_PDUSession\_Update request which may contain EAS IP replacement information and target DNAI provided by AF in step 2. If the V-SMF cannot serve the target DNAI, it invokes a Nsmf\_PDUSession\_SMContextStatusNotify service operation to send the target DNAI to AMF, and the AMF selects a target V-SMF based on the target DNAI as described in clause 4.23.5.4 of TS 23.502 [3] by replacing I-SMF with V-SMF. The target V-SMF retrieves SM context from the source V-SMF using Nsmf\_PDUSession\_Context Request/Response, containing Authorization Result for HR-SBO, EAS IP replacement information and target DNAI in the Request. The target V-SMF may select a new V-EASDF as described from steps 2 to 12 in Figure 6.7.2.6-1. +- 3b. (For AF triggered EAS re-discovery and edge relocation via interacting with VPLMN case): The V-SMF initiates Nsmf\_PDUSession\_Update request with the EAS rediscovery indication and the impact field to the H-SMF, and the H-SMF initiates Nsmf\_PDUSession\_Update Response towards the (target) V-SMF including the PCO information to be sent to the UE as described in step 2 of Figure 6.2.3.3-1. In intra-PLMN V-SMF change, the target V-SMF may use the source and target DNAI to determine the Impact field to be sent to the UE. In inter-PLMN mobility, the target V-SMF provides EAS rediscovery information without an Impact field. +4. The V-SMF may initiate PDU Session Modification command including the PCO to the UE. +The PCO may include EAS rediscovery indication (optional) and the impact field (optional). +- 5 The V-SMF may configure the V-UPF (UL CL and L-PSA) with EAS IP replacement information. + +### 6.7.4 AF request on PDU Sessions supporting HR-SBO + +For HR-SBO PDU Sessions, the AF in VPLMN may send to V-NEF an AF request to influence traffic routing (e.g. for the purpose of subscription to UP path management events on HR-SBO Sessions in VPLMN). The AF request for the HR-SBO PDU Session (which can be differentiated from the non-roaming and LBO PDU Session by the V-NEF as described in clauses 4.3.6.3 and 4.3.6.4 of TS 23.502 [3].) from the AF is stored as Application Data (Data Subset = AF traffic influence request information) in the UDR of VPLMN as described in clause 4.3.6 of TS 23.502 [3]. To obtain the AF traffic influence request information, the V-SMF managing the PDU Session supporting HR-SBO subscribes to the NEF in VPLMN for notification of Application Data modification as specified in clause 4.3.6 of TS 23.502 [3]. + +## 6.8 Support for mapping between EAS address Information and DNAI + +### 6.8.1 General + +In order to make sure the AF can query for DNAIs, the 5GS may help determine proper DNAI(s) and notify the information to AF based on AF request providing EAS address information (i.e. IP address(es), EAS IP range(s) or FQDN(s)). + +NEF/UDR is configured by OAM with the mapping information between EAS IP address information and DNAI. AF may subscribe the mapping information modification to NEF. AF may request immediate reporting. When the configuration information (relationship between DNAI and EAS address information) is changed, the UDR can notify the new mapping information to NEF. When the mapping information is stored in UDR, NEF may subscribe to mapping information in UDR, where NEF may request immediate reporting. If subscribed to information change, the UDR notifies the NEF with all the corresponding mapping information it has stored for the relevant DNN and/or S-NSSAI, and the NEF notifies the AF. + +The EAS address and DNAI Mapping Information record in UDR is shown Table 6.8.1-1. The information elements for the NEF service Nnef\_DNAIMapping\_Subscribe is specified in clause 5.2.6.8 of TS 23.502 [3]. + +Table 6.8.1-1: Description of EAS address and DNAI Mapping Information + +| Parameters | Description | +|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EAS address information | IP address(es) of the EASs or the IP address ranges (IPv4 subnetwork(s) and/or IPv6 prefix(es)) or FQDN(s) where the EAS is deployed for each DNAI.
[Mandatory] | +| DNAI(s) | DNAI(s) for the EAS Deployment information.
[Mandatory] | +| DNN | DNN for the EAS Deployment Information.
[Conditional] (NOTE 1) | +| S-NSSAI | S-NSSAI for the EAS Deployment Information.
[Conditional] (NOTE 1) | +| NOTE 1: At least one of DNN or S-NSSAI shall be present. | | + +### 6.8.2 AF request for DNAI Procedures + +![Sequence diagram showing the AF request for DNAI based on AF request. The diagram involves three entities: AF, NEF, and UDR. The sequence of messages is: 1. AF sends Nnef_DNAIMapping_Subscribe to NEF; 2. NEF sends Nudr_DM_Subscribe to UDR; 3. UDR sends Nudr_DM_Subscribe notify back to NEF; 4. NEF performs DNAI determination; 5. NEF sends Nnef_DNAIMapping_Subscribe notify back to AF.](4d5d6207a6d444ae745057ebc3ddcd86_img.jpg) + +``` + +sequenceDiagram + participant AF + participant NEF + participant UDR + Note right of NEF: 4.DNAI determination + AF->>NEF: 1. Nnef_DNAIMapping_Subscribe subscribe + NEF->>UDR: 2. Nudr_DM_Subscribe subscribe + UDR-->>NEF: 3. Nudr_DM_Subscribe notify + NEF->>AF: 5. Nnef_DNAIMapping_Subscribe notify + +``` + +Sequence diagram showing the AF request for DNAI based on AF request. The diagram involves three entities: AF, NEF, and UDR. The sequence of messages is: 1. AF sends Nnef\_DNAIMapping\_Subscribe to NEF; 2. NEF sends Nudr\_DM\_Subscribe to UDR; 3. UDR sends Nudr\_DM\_Subscribe notify back to NEF; 4. NEF performs DNAI determination; 5. NEF sends Nnef\_DNAIMapping\_Subscribe notify back to AF. + +Figure 6.8.2-1: AF request for DNAI based on AF request + +1. AF invokes Nnef\_DNAIMapping\_Subscribe service to request the DNAI information. The request includes EAS address information and optionally: DNN, S-NSSAI and AF Identifier. + +If mapping information is stored in NEF, skip step 2-3. + +2. If the mapping information is stored in UDR, the NEF determines the DNN and/or the S-NSSAI if not received from the AF, potentially using the AF identifier. If the NEF has not yet received the DNAI mapping information for this DNN and/or S-NSSAI, NEF invokes the Nudr\_DM\_Subscribe service to subscribe to DNAI mapping information for this DNN and/or S-NSSAI. +3. UDR notifies the NEF with all the DNAI mapping information for the requested DNN/S-NSSAI. +4. NEF determines the suitable DNAI(s) using the DNAI mapping information. +5. NEF notifies the DNAI(s) or the updated DNAI information to AF corresponding to the request in step 1. + +If DNAI information is stored in the UDR, whenever the DNAI mapping information change, steps 3 to 5 take place. + +# 7 Network Function Services and Descriptions + +## 7.1 EASDF Services + +### 7.1.1 General + +The following table illustrates the EASDF Services and Service Operations. + +**Table 7.1.1-1: NF services provided by the EASDF** + +| Service Name | Service Operations | Operation Semantics | Example Consumer(s) | +|---------------------------|--------------------|---------------------|---------------------| +| Neasdf_DNSContext | Create | Request/Response | SMF | +| | Update | Request/Response | SMF | +| | Delete | Request/Response | SMF | +| | Notify | Subscribe/Notify | SMF | +| Neasdf_BaselineDNSPattern | Create | Request/Response | SMF | +| | Update | Request/Response | SMF | +| | Delete | Request/Response | SMF | + +### 7.1.2 Neasdf\_DNSContext Service + +#### 7.1.2.1 General + +**Service description:** This service enables the consumer to create, update, or delete DNS context in EASDF and to Subscribe to DNS message related reporting from EASDF. + +DNS contexts in EASDF include rules on how EASDF is to handle DNS messages. + +This service also can be supported by V-EASDF in VPLMN for HR scenario supporting HR-SBO. + +#### 7.1.2.2 Neasdf\_DNSContext\_Create Service Operation + +**Service operation name:** Neasdf\_DNSContext\_Create + +**Description:** Create a DNS context in EASDF. + +**Input, Required:** UE IP address, DNN, S-NSSAI, Notification Endpoint. + +**Input, Optional:** HPLMN ID, DNS message handling rules, N6 traffic routing information (towards the Local PSA-UPF). + +NOTE 1: In HR-SBO scenario, the V-SMF can invoke Neasdf\_DNSContext\_Create service in order to obtain the IP address of the V-EASDF while the UE UP address has not yet been determined. If the V-SMF is not aware of the UE IP address when invoking this service operation, the V-SMF can set UE IP address as unspecified such as zero value. + +DNS message detection and Actions(s) are specified in clause 6.2.3.2.2. + +NOTE 2: N6 traffic routing information can contain the IP address the Local PSA-UPF. + +**Output, Required:** If successful, IP address of the EASDF, EASDF Context ID, Result Indication. + +**Output, Optional:** None. + +#### 7.1.2.3 Neasdf\_DNSContext\_Update Service Operation + +**Service operation name:** Neasdf\_DNSContext\_Update + +**Description:** Update the DNS context in EASDF, or indicate EASDF to forward the DNS Response to UE. + +**Input, Required:** EASDF Context ID, updated DNS message handling rules. + +**Input, Optional:** UE IP address, N6 traffic routing information (towards the Local PSA-UPF). + +NOTE: In HR-SBO scenario, the V-SMF can provide the UE IP address received from the H-SMF to update DNS Context of the V-EASDF via this Service Operation. + +**Output, Required:** Result Indication. + +**Output, Optional:** None. + +#### 7.1.2.4 Neasdf\_DNSContext\_Delete Service Operation + +**Service operation name:** Neasdf\_DNSContext\_Delete + +**Description:** Delete the DNS context in EASDF. + +**Input, Required:** EASDF Context ID. + +**Input, Optional:** None. + +**Output, Required:** Result Indication. + +**Output, Optional:** None. + +#### 7.1.2.5 Neasdf\_DNSContext\_Notify Service Operation + +**Service operation name:** Neasdf\_DNSContext\_Notify + +**Description:** EASDF reports DNS message related information to the consumer when receiving DNS Query or DNS Response. + +**Input, Required:** DNS message reporting information (DNS message content specified in clause 6.2.3.2.2 and corresponding DNS message type), Notification Endpoint. + +**Input, Optional:** DNS message identifier. + +**Output, Required:** Result Indication. + +**Output, Optional:** None. + +### 7.1.3 Neasdf\_BaselineDNSPattern Service + +#### 7.1.3.1 General + +This service provides the capability to create, update or remove BaselineDNSPattern in EASDF. See clause 6.2.3.4.4 for detailed procedure. + +#### 7.1.3.2 Neasdf\_BaselineDNSPattern\_Create Service Operation + +**Service operation name:** Neasdf\_BaselineDNSPattern\_Create + +**Description:** Create the BaselineDNSPattern in EASDF. + +**Input, Required:** BaselineDNSPattern. + +**Input, Optional:** None. + +**Output, Required:** Success or Failure. + +**Output, Optional:** + +#### 7.1.3.3 Neasdf\_BaselineDNSPattern\_Update Service Operation + +**Service operation name:** Neasdf\_BaselineDNSPattern\_Update + +**Description:** Update the BaselineDNSPattern in EASDF. + +**Input, Required:** Updated BaselineDNSPattern. + +**Input, Optional:** None. + +**Output, Required:** Success or Failure. + +**Output, Optional:** None. + +#### 7.1.3.4 Neasdf\_BaselineDNSPattern\_Delete Service Operation + +**Service operation name:** Neasdf\_BaselineDNSPattern\_Delete + +**Description:** Delete the BaselineDNSPattern in EASDF. + +**Input, Required:** Baseline DNS message detection template ID and/or Baseline DNS handling actions ID. + +**Input, Optional:** None. + +**Output, Required:** Result. + +**Output, Optional:** None. + +# Annex A (Informative): EAS Discovery Using 3rd Party Mechanisms + +There are different IP discovery mechanisms existing in the application layer. For example, the application client can generate the DNS Query outside of DNS libraries in the OS with DoT, DoH or other over the top mechanisms. + +The third party can also deploy a service scheduling server to determine the (E)AS IP address based on the UE's HTTP(S) request. In this case, the DNS firstly resolves the FQDN in the DNS Query of the UE into the IP address of the service scheduling server and then the UE contacts the service scheduling server that can provide the IP address of the EAS that the UE is then to contact. + +For the Distributed Anchor Point connectivity model, in order to enable EAS discovery by third party mechanisms, the DNS Server or service scheduling server in the third party could be pre-configured with mapping information between the IP address range which can correspond to the Central PSA UPF or other entities (e.g. a NAT server) on the N6 interface and EAS information. In this case, the DNS Server or service scheduling server in the third party can take the source IP address of the UE request as the location information of UE. The DNS and/or service scheduling server pre-configuration can be based on the agreement between the MNO and service provider. + +For the Session Breakout connectivity model, based on agreement with the operator, a possible solution for the service scheduling server is as follows: + +- The IP address of the service scheduling server can be set as a condition in the ULCL UPF to offload traffic. The IP address of service scheduling server can be pre-configured or resolved by the EASDF based on procedure defined in clause 6.2.2.2. +- NAT server can be deployed in the L- DN or local N6 interface, in order that the source IP address of the UE request sent to the service scheduling server can correspond to the UE location related information. + +NOTE: Otherwise, the source IP address of the UE request message sent to the third party DNS server / service scheduling server is bound with the central PSA UPF, so it's impossible for the third party DNS server / service scheduling server to know which local EAS address could be allocated to the UE. + +Based on the mapping relationship between the IP ranges of UE request and the EAS information, the EAS IP address can be allocated to the UE. The above example is briefly shown in Figure A-1. + +![Diagram illustrating the Service scheduling server mechanism for Session Breakout connectivity model. The diagram shows the flow of traffic and signaling between a UE, ULCL UPF, Central PSA UPF, Local PSA UPF, Local DN (containing EAS), Central DN, and a DNS Server. The sequence of messages is: 1. DNS request from UE to DNS Server; 2. DNS response (IP address of Service scheduling server) from DNS Server to UE; 3. HTTP request from UE to Central DN; 4. HTTP response (EAS address) from Central DN to UE; 5. HTTP request/response between UE and EAS via Local DN and Local PSA UPF.](b882c54d92390b4ca523f230e3e07617_img.jpg) + +``` +graph TD + UE[UE] -- "1.DNS request" --> DNS[DNS Server] + DNS -- "2.DNS response (IP address of Service scheduling server)" --> UE + UE -- "3.HTTP request" --> CentralDN((Central DN)) + CentralDN -- "4.HTTP response (EAS address)" --> UE + UE -- "5.HTTP request/response" --> LocalDN((Local DN)) + LocalDN --> LocalPSA[Local PSA UPF] + LocalPSA --> CentralPSA[Central PSA UPF] + CentralPSA --> ULCL[ULCL UPF] + ULCL --> UE +``` + +Diagram illustrating the Service scheduling server mechanism for Session Breakout connectivity model. The diagram shows the flow of traffic and signaling between a UE, ULCL UPF, Central PSA UPF, Local PSA UPF, Local DN (containing EAS), Central DN, and a DNS Server. The sequence of messages is: 1. DNS request from UE to DNS Server; 2. DNS response (IP address of Service scheduling server) from DNS Server to UE; 3. HTTP request from UE to Central DN; 4. HTTP response (EAS address) from Central DN to UE; 5. HTTP request/response between UE and EAS via Local DN and Local PSA UPF. + +**Figure A-1: Service scheduling server mechanism for Session Breakout connectivity model** + +# --- Annex B (Informative): Application Layer based EAS (Re-)Direction + +During the application relocation, the AF can reselect a new EAS for the UE. Reselection can be triggered by the AF when it receives a UP path change notification or by an internal trigger of the AF (e.g. load balancing, UE location change, etc.). When the new EAS is reselected, the UE is provided the new EAS address via application layer signalling. For example, the UE can receive the URL or FQDN of the new EAS once the application context relocation is complete and then use DNS to resolve the URL or FQDN. The UE can also obtain the new EAS address via HTTP redirection. + +NOTE: The Application layer signalling between the AF (or Old EAS) and UE is application specific and is outside the scope of this specification. + +# Annex C (Informative): Considerations for EAS (re)Discovery + +## C.1 General + +DNS records obtained from a DNS resolver in the network contains a time-to-live (TTL) value. This is a hint provided by the DNS resolver and can be used to determine the length of time that the record is to be cached. DNS records can be cached in the UE system wide (in OS) and/or applications. The application cache is managed on a per application basis while the system cache is common to applications. Name resolution caches in various applications also have different policies and behaviours. Some applications cache the DNS records for the length of the application session while others have a time limit. The recommendations in this TS will only work if the UE application (in case of DNS cache at the application layer) or the UE OS (in case of DNS cache shared by applications) consider indications from the UE modem layer with respect to DNS settings and DNS caching. Whether and how the UE (and application) considers the indication depends on implementation. + +## C.2 Impact of IP Addresses for DNS Resolver on UE + +The UE can be configured by the 5GC with an IP address for the DNS resolver using ePCO or IPv6 Router Advertisement (RA), DHCPv4 or DHCPv6 as described in clause 5.8.2 of TS 23.501 [2]. 5GC can reconfigure the DNS resolver IP address using NAS or IPv6 Router Advertisement (RA). In case of anycast IP address is used for the DNS resolver, the 5GC can use UL CL/BP to branch out the DNS messages and the DN is responsible to route them to the closest instance of the MNO DNS resolver without having to reconfigure the DNS resolver IP address in the UE. + +NOTE: 5GC is likely not to be able to reconfigure the DNS resolver IP address when DHCP is used to configure this information on the UE, e.g. in case of UE split. Applications in the UE can request the DNS resolver configured on the UE to resolve an FQDN. However, applications can also be configured with their own DNS resolver addresses and can use encrypted messaging based e.g. on DNS over HTTPS (DoH) or, DNS over TLS (DoT). Configuration of application DNS resolvers is out of scope of 5GC. DNS messages delivered over DoT, or DoH might be forwarded transparently to the destination addresses of the messages. The application DNS resolver can be operated by the 5GC operator or by a third party. + +A network interface change, or NAS SM EAS rediscovery indication (explicitly as described in clause 6.2.3.3) or reconfiguration of DNS server address in NAS SM message that implicitly indicating EAS rediscovery as described in 6.2.3.2.3 can and should result in the UE OS/application clearing name/IP address translations in its DNS cache. + +If a network interface change or NAS SM EAS rediscovery explicit indication or reconfiguration of DNS server address using NAS SM (i.e. implicit EAS rediscovery indication) does not result in the UE OS/application clearing name to IP address translations in its DNS cache, a subsequent DNS EAS address resolution request can result to address of old EAS. + +During EPC to 5GC mobility without N26 interface, the UE can receive a new DNS server address different from the one received from the SMF+PGW-C during the PDN connection initiated in EPC. This can result in the UE OS clearing name/IP address translations in its DNS cache. During 5GC to EPC mobility without N26 interface, the UE can perform the same if it receives a new DNS server address from the SMF+PGW-C. + +## C.3 UE Considerations for EAS Re-discovery + +A UE that complies with EAS (re-)discovery described in this specification is not recommended to override operator-provided DNS settings. This is necessary for the "closest" EAS server to be selected. Overriding the operator-provided DNS settings means that procedures requiring operator provided DNS server will not work. + +NOTE 1: If the user overrides the DNS configuration set by the network using ePCO, for example if the user configures a private DNS configuration via UI, the network DNS configuration configured using ePCO could remain inactive until the user configured DNS setting is revoked by the user. + +- NOTE 2: If an OS, user or applications override the operator-provided DNS settings, the DNS resolvers or servers in the third party can take the source IP address of the DNS Query as the location information of UE, which can correspond to the remote PSA UPF or other entities (e.g. a NAT server) on the remote/central N6 interface which can lead to a non-optimal choice of the EAS server address. +- NOTE 3: If the DNS server configuration in an OS overrides the operator provided DNS, the DNS Queries continue to be sent over the correct PDU Session for the application. +- NOTE 4: If the UE (OS or application) uses a DNS resolver that is different than the one provided by the 5GC, then the Session Breakout connectivity mode, option A and B in clause 6.2.3.2 will not work if the EASDF is not in the DNS resolver chain for recursive DNS resolution. + +## --- C.4 UE Procedures for Session Breakout + +In the session breakout connectivity model, the selection of a new session breakout path does not result in a new network interface indication at the UE. + +- NOTE: In the case of multiple sessions or distributed anchor point connectivity models, when there is a change of network interface, indication of network interface change can and should be used to flush the UE OS DNS cache. + +Session breakout results in a NAS SM message indicating the need to redo DNS lookup sent by the SMF to the UE modem. Thus, in order to support some solutions of this specification, it is necessary for the operating system to receive information of EAS rediscovery from the modem when such signalling has been received and clear the DNS cache in UE OS. + +## --- C.5 Split-UE Considerations for EAS (Re-)discovery + +For the split-UE (i.e. the TE and MT are separated), information provided by the SMF in the NAS message during the PDU Session Establishment, Modification and Command is provided to the MT and MTs cannot provide the NAS provided IP parameters to the TE, i.e. the TE cannot receive that information from the MT because of separation between the TE and MT. Example of information are the DNS configuration or Rediscovery indication. + +The TE gets LAN side IP parameters configuration from the MT, i.e. using DHCPv4 (for IPv4) or IPv6 Router Advertisement/DHCPv6 (for IPv6). MT hosts the DNS resolver for TE and its address can be obtained from MT using DHCP or IPv6 RA. When TE uses DNS resolver in MT, the MT in turn uses its configured network DNS resolver (e.g. EASDF, L-DNS) which is the expected DNS resolution chain and it results in the discovery of the correct EAS. An application in the TE that complies with EAS (re-)discovery described in this specification is not recommended to override operator-provided DNS settings as described in clause C.3. + +For the split-UE and MTs cannot provide the NAS information requesting UE to redo DNS lookup received from the SMF to the TE or the TE OS. In such cases, the closest EAS is still reachable, for example, if anycast EAS address is used. + +For the Split-UE in the option C case, if the new address of Local DNS Server cannot be provided to the TE or the TE OS from the MT, so the TE continues to use the old DNS Server to perform the EAS discovery and cannot receive the DNS Query/Response from the 5GC (e.g. the BP will route the DNS Query to the L-PSA). After no DNS Query response is received from the 5GC for several times or an information indicating the old DNS Server unreachable (e.g. ICMP message of Host Not Reachable), the TE initiates a new DNS Server Discovery via a DHCP message to the 5GC, and the SMF may send the same new DNS Server IP address to the UE in the DHCP response message than sent via PCO in the PDU Session Command. After the UE gets the new DNS Server IP address, the UE uses the new DNS Server IP address to perform the EAS (re-)discovery. + +## --- C.6 Detection of UE not using 5GC provided DNS server + +The UPF Traffic detection and traffic reporting capabilities specified in clause 5.8 in TS 23.501 [2] can be used to monitor if the UE uses a DNS resolver that is different than the one provided by the 5GC, e.g.: + +- the SMF can install Packet Detection Rule(s) in the UPF to report when the traffic matches certain well known public DNS service IP addresses; +- the UPF can have an Application Filter defined to detect DNS ports as well as if the DNS traffic not destined to operator provided DNS servers (e.g. EASDF). The SMF can refer to this filter using an application ID. + +# Annex D (Informative): Examples of AF Guidance to PCF for Determination of URSP Rules + +- a) The UE is to use a specific (DNN, S-NSSAI) (e.g. working in SSC mode 2 or 3 with the Distributed Anchor deployment) when trying to reach some domains while it should use another (DNN, S-NSSAI) (e.g. working in SSC mode 1) for other domains. In this example, the AF can indicate two FQDN filters, optionally with corresponding filtering rule priorities, if the FQDN filters overlap. For each FQDN filter, the AF can indicate a corresponding DNN, S-NSSAI. +- b) Corporate applications only reachable via a specific (DNN, S-NSSAI) negotiated with the operator; corresponding URSP rules (URSP rules referring to domains of these corporate applications) shall only point to this specific (DNN, S-NSSAI). In this example, the AF can indicate one FQDN filter for the corporate applications. Optionally, the AF can indicate also the corresponding DNN, S-NSSAI for the FQDN filter. If DNN, S-NSSAI is not provided by the AF, the NEF can determine it based on the AF identity. +- c) Corporate applications reachable via a (DNN, S-NSSAI) but only in some location; e.g. the corporate applications are only accessible when the UE is in some location corresponding to the corporate premises. In this example, the AF can provide information as in bullet b) and additionally provides where the corporate applications are accessible. URSP Rules will guide the UE select the (DNN, S-NSSAI) when the UE is in the geographical zone. +- d) Internet applications not reachable via a specific (DNN, S-NSSAI) negotiated with the operator but that should be only reachable via a general purpose (DNN, S-NSSAI); e.g. traffic of UE(s) of a third party targeting Internet applications is not to be sent to a specific (DNN, S-NSSAI) negotiated with the operator as this traffic is not expected to cross the Intranet of the corporate. In this example, the default operator rules are used generate a "match all" URSP rule with a low filtering rule priority and a corresponding generic purpose DNN, S-NSSAI. +- e) Internet applications reachable via both a specific (DNN, S-NSSAI) negotiated with the operator and via a general purpose (DNN, S-NSSAI) for which the third party may want to set preferences between these 2 kinds of connectivity. These preferences may depend on the UE location. In this example, the AF can indicate FQDN filters as in bullet b), but the FQDN filters are for Internet applications. In addition, the AF can indicate where the Internet applications are accessible via the specific DNN, S-NSSAI. In addition, the default operator rules are used generate a "match all" URSP rule with a low filtering rule priority and a generic purpose DNN, S-NSSAI. +- f) Combination of bullets c) and e). In this example, the AF can indicate one FQDN filter for corporate applications as in bullet c) and another FQDN filter for Internet applications as in bullet c), In addition, the AF can indicate filtering rule priorities for the FQDN filters, if the FQDN filters overlap. +- g) Corporate applications reachable via a (DNN, S-NSSAI) in some location and via another DNN, S-NSSAI in another location; e.g. the corporate applications are only accessible via a location specific corporate DNN, S-NSSAI. In this example, the AF can indicate an FQDN filter as in bullet c), but indicates two or more sets of location conditions for the FQDN filter and indicates different DNN, S-NSSAI for each. In addition, if the geographical zones overlap, the AF can indicate a Route Selection Descriptor Precedence for each of them. + +The examples b) to e) above can correspond to different AF(s) representing different corporate that have different policies. How the rule precedence between rules for different AFs are set in the URSP rules is up to the operator policy. + +In the examples above, when a location specific corporate DNN, S-NSSAI has been agreed, as an alternative, the location area where the DNN is accessible can also be set as part of the SLA agreement configured on the NEF. + +# --- Annex E (informative): EPS Interworking Considerations + +## E.1 General + +5GC is specified to support interworking with EPC. Edge Computing deployments that use interworking need to consider the aspects outlined in this Annex. + +## --- E.2 Distributed Anchor + +SSC mode 3 cannot be used when the UE is registered in EPC as 5G-NAS is not available. Re-establishing a PDN connection after releasing an old one can be done in EPS using the "reactivation requested" cause value in EPS bearer context deactivation (see clause 6.4.4.2 of TS 24.301 [7]), if the feature is supported by the EPS network. + +## --- E.3 Multiple Sessions + +The URSP rules provided by 5GC to the UE are defined to cover both 5GS as well as EPS when interworking is applied. In EPS there is no possibility to provide new URSP rules to the UE, instead according to clauses 5.15.5.3 and 5.17.1.2 of TS 23.501 [2], the URSP rules provided to the UE when it was registered in 5GC can also be used when the UE is registered in EPC if HPLMN uses URSP (see TS 24.526 [8]). + +AF guidance of URSPs may not take effect if the UE is in EPS and the UE does not use the URSP rules on EPS (see TS 24.526 [8] 4.4.2 for the use of URSP in EPS). Therefore, it is not deterministic when they will take effect, since PCF could have issued the URSP rules when the UE was on EPS (where URSP rules cannot be sent). + +## --- E.4 Session Breakout + +As traffic offload via UL CL/BP is not supported over EPC, when a PDN connection is initiated in EPS or a PDU Session is handed-over to EPS, the SMF+PGW-C can send to the EASDF DNS message handling rules requesting the EASDF to transparently forward any DNS traffic. The SMF+PGW-C can send to the EASDF new DNS message handling rules (with actual reporting and actions as defined in clause 6.2.3.2.2) when the PDU Session/PDN connection is handed-over (back) to 5GS. + +When a PDN connection is initiated in EPS, the SMF+PGW-C can also select a normal DNS Server (i.e. different from an EASDF) to serve the PDN Connection, and then indicate to the UE to use the EASDF as DNS Server when the PDU Session/PDN connection is moved to 5GS. + +# Annex F (Informative): EAS Relocation on Simultaneous Connectivity over Source and Target PSA + +This annex describes how EAS relocation can make use of network capabilities that, at PSA change, provide simultaneous connectivity over the source and the target PSA during a transient period. + +At PSA change, simultaneous connectivity to Application over former and new PSA allows the application to build its own EAS relocation solution and minimize the impact on latency: + +- If the decision for when to start using a target EAS is taken by the application, this decision can consider application specific aspects, like for example, the time interval between packets or end of a video frame to minimize impact on latency. +- When there are multiple applications on a PDU Session, if connectivity over the former PSA is maintained for some time, each application can schedule EAS relocation to suit the application specific needs without interfering with the other applications. + +The procedure is shown in below Figure F-1: + +![Sequence diagram of EAS relocation on simultaneous connectivity over source and target PSA. The diagram shows the interaction between UE, Source L-PSA, Source EAS (EAS#1), SMF, and DNS. The process involves PDU Session Edge reallocation, EAS Rediscovery, and Context migration between Source and Target EAS.](8a94796989f4fcba2688c4faa7991538_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source L-PSA + participant Source EAS as Source EAS (EAS#1) + participant SMF + participant DNS + + Note left of UE: IP#1 + UE->>Source EAS: Application Traffic (IP#1,EAS#1) + Note right of SMF: 1. PDU Session Edge reallocation at target L-PSA (source L-PSA is maintained) + Note left of UE: IP#1, IP#2 + UE->>Source EAS: 2. Application Traffic (IP#1,EAS#1) + Note right of SMF: 3. EAS Rediscovery (see clauses 6.2.2.3 and 6.2.3.3) + Note right of SMF: 4a. App signalling (IP#2 (or IP#1), EAS#2, Ctxt Id) + Note right of SMF: 4b. App traffic (IP#1, EAS#1, Ctxt Id) + Note right of SMF: 4c. App signalling (IP#2 (or IP#1), EAS#2, Ctxt Id) + Note right of SMF: 5. Release Source L-PSA + Note left of UE: IP#1 or IP#2 + UE->>Target EAS: 6. Application Traffic (IP#2 (or IP#1),EAS#2) + +``` + +The diagram illustrates the sequence of operations for EAS relocation. It begins with the UE sending application traffic to the Source EAS (EAS#1) via the Source L-PSA. Step 1 involves a PDU Session Edge reallocation at the target L-PSA while maintaining the source L-PSA. In step 2, the UE continues to send application traffic to the Source EAS. Step 3 is an EAS Rediscovery phase. Step 4 is a context migration phase, which includes app signalling (4a), app traffic (4b), and another app signalling (4c) between the UE and the Target EAS (EAS#2). Step 5 is the release of the Source L-PSA. Finally, in step 6, the UE sends application traffic to the Target EAS (EAS#2) via the Target L-PSA. A dashed box in the diagram encloses the context migration and signalling steps (4a, 4b, 4c). + +Sequence diagram of EAS relocation on simultaneous connectivity over source and target PSA. The diagram shows the interaction between UE, Source L-PSA, Source EAS (EAS#1), SMF, and DNS. The process involves PDU Session Edge reallocation, EAS Rediscovery, and Context migration between Source and Target EAS. + +Figure F-1: EAS relocation on simultaneous connectivity over source and target PSA + +The user has established a PDU Session. This PDU Session has a local PSA (source L-PSA), which could be the PSA of a PDU Session with Distributed Anchor connectivity or one additional local PSA of a PDU Session with Session Breakout. There has been an EAS Discovery procedure as described in clauses 6.2.2.2 and 6.2.3.2 (the procedure is conditioned to the connectivity model) for one or more applications. Application traffic is served by source EAS over the Local PSA. + +1. User mobility triggers SMF to select a new Local PSA (target L-PSA) that is closer to current user location. In this scenario, the re-anchoring procedures that provide Simultaneous Connectivity over Source and Target PSA are described in TS 23.502 [3]: + - For Distributed Anchor, in clause 4.3.5.2 for Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions and in clause 4.3.5.3 for Change of SSC mode 3 PDU Session Anchor with IPv6 Multi-homed PDU Session. + - For Session Breakout, in clause 4.3.5.7 for Simultaneous change of Branching Point or UL CL and additional PSA for a PDU Session. + +The SMF may notify an AF for the early and/or late notifications on the UP-path change event as described in clause 4.3.6.3 in TS 23.502 [3]. + +2. When the connectivity is available on target L-PSA, the connectivity via source L-PSA is still available during certain time (that is provisioned and controlled as described in these TS 23.502 [3] procedures). The application traffic can continue to run over the established UE-EAS connections. +3. The EAS Rediscovery Procedures described in clauses 6.2.2.3 and 6.2.3.3 allow the UE to discover a new EAS (i.e. target EAS) for the application that is closer to the UE over the new path (there could be multiple triggers as described in those respective clauses). If multiple applications are being served by this PDU Session, each of them performs rediscovery. This discovery procedure may lead to EAS reselection. +4. New L4 connections may now be established between the UE and the target EAS with the following considerations: + - For Distributed anchor or session breakout with MH, the UE uses the IP address /prefix associated with the target PSA (that is referred to as IP#2 in Figure F-1). + - For Session breakout with ULCL, there has not been connection/IP address change. Same IP address is still used by UE (that is referred to as IP#1 in Figure F-1). + +NOTE 1: If Session Breakout is used for connectivity and if the application wants to build service continuity on simultaneous connections, source EAS and target EAS cannot share the same IP address (e.g. by using anycast). + +EAS Relocation may involve EAS context migration in the case of stateful applications. The following examples are part of the application implementation details and fall out of 3GPP specification scope: + +- In case that SMF notifies an AF for the early and/or late notification in Step 1, based on the notifications, the AF can interact with the source Application server, which can recreate the context to the target EAS and then provide switching instructions to the Application client. +- The Application server can recreate the service context when first contacted by the client using a Context Id: when suitable, the application client sets up a connection to the target EAS including a Context Id. The target EAS uses this Context Id to retrieve the latest service context available and subsequent updates, if needed. +- The Application server can recreate the context when first contacted by the client using a Context Id: the application client sets up a connection to the target EAS but for some time it sends traffic to both source and target EAS. In this way it triggers the context migration before the actual EAS switch. +- The source Application server is able to provide the client with switching instructions when a new EAS is selected: upon UE request (if UE selected) or as an EAS initiative (if server selected), the source EAS provides the Application client with switching instructions while it continues to serve traffic and drives any context migration towards the selected target EAS. + +NOTE 2: This application procedure may be designed to solve EAS relocation in all scenarios, not only when triggered by Edge Relocation, which may simplify the application design. + +5. At some points all traffic for all applications in this session are sending traffic to their target EAS only and traffic ceases over the source L- PSA. The source L-PSA is then released. The timers should be set to allow EAS relocation. +6. UE only maintains connection(s) to target EAS(s). + +# --- Annex G (Informative): Change history + +| Change history | | | | | | | | +|----------------|-----------|------------|------|-----|-----|-----------------------------------------------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-03 | SA#2#143E | S2-2100114 | - | - | - | Proposed skeleton approved at S2#143E | 0.0.0 | +| 2021-06 | SA#92E | SP-210365 | - | - | - | MCC editorial update for presentation to TSG SA#92E for information | 1.0.0 | +| 2021-09 | SA#93E | SP-210942 | - | - | - | MCC editorial update for presentation to TSG SA#93E for approval | 2.0.0 | +| 2021-09 | SA#93E | - | - | - | - | MCC editorial update for publication after SA#93E approval | 17.0.0 | +| 2021-12 | SA#94E | SP-211290 | 0001 | 3 | F | Correction related to uniqueness of Update related to a buffered DNS message in EASDF | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0003 | - | F | Correction and removal of misleading Note | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0005 | 1 | F | Not all EC scenarios requires EASDF | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0014 | 1 | F | Clarify the local AF subscription for the QoS Monitoring during UE mobility | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0017 | 4 | F | Updates on EAS Discovery Procedure with EASDF | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0018 | 3 | F | Mega CR for minor fixes to TS 23.548 | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0024 | - | F | Update Neasdf_DNSContext services | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0030 | 4 | C | EAS rediscovery: Edge DNS Client based EAS (re-)discovery | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0031 | 3 | F | UE authorization for 5GC assisted EAS discovery | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0034 | 1 | F | Updating related to EAS Discovery Procedure | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0035 | 1 | F | Corrections on enabling EAS IP Replacement procedure by AF | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0036 | 1 | F | Improvements and correction to annex C | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0038 | 1 | F | Change of DNS server address during EPC IWK | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0039 | 1 | F | Alignment of EASDF functional description | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0040 | 1 | F | Added the situation of AF relocation to uplink Packet Buffer | 17.1.0 | +| 2021-12 | SA#94E | SP-211290 | 0042 | 1 | F | Local NEF selection | 17.1.0 | +| 2022-03 | SA#95E | SP-220055 | 0043 | 1 | F | Corrections on enabling EAS IP Replacement procedure by AF | 17.2.0 | +| 2022-03 | SA#95E | SP-220055 | 0046 | 1 | F | Correction related EHE in EC architecture | 17.2.0 | +| 2022-03 | SA#95E | SP-220055 | 0047 | 1 | F | Update of EAS discovery procedure and BaselineDNSPattern management in EASDF | 17.2.0 | +| 2022-03 | SA#95E | SP-220055 | 0048 | 1 | F | On NAT between PSA UPF and EASDF | 17.2.0 | +| 2022-03 | SA#95E | SP-220055 | 0050 | 1 | F | Removing inconsistency in the definition of ECS Address Configuration Information | 17.2.0 | +| 2022-03 | SA#95E | SP-220055 | 0051 | 1 | F | Corrections of EDC functionality description | 17.2.0 | +| 2022-06 | SA#96 | SP-220398 | 0052 | 1 | F | Correction related to EAS IP Address in EDI | 17.3.0 | +| 2022-06 | SA#96 | SP-220398 | 0053 | - | F | Corrections on enabling EAS IP Replacement procedure by AF | 17.3.0 | +| 2022-06 | SA#96 | SP-220398 | 0054 | 1 | F | Correction of EAS Deployment Information Management procedures and services | 17.3.0 | +| 2022-06 | SA#96 | SP-220398 | 0056 | 1 | F | Parameter supplement of EDI | 17.3.0 | +| 2022-06 | SA#96 | SP-220398 | 0061 | 1 | F | Alignment of ECS Address Configuration Information to SA6's definition | 17.3.0 | +| 2022-09 | SA#97E | SP-220777 | 0062 | 1 | F | EDNS Client Subnet option correction | 17.4.0 | +| 2022-12 | SA#98E | SP-221069 | 0063 | - | F | Clarifications for local event notification control | 17.5.0 | +| 2022-12 | SA#98E | SP-221086 | 0070 | 2 | B | Support of influencing UPF and EAS (re)location for collections of UEs | 18.0.0 | +| 2022-12 | SA#98E | SP-221086 | 0075 | 2 | B | KI#4 common EAS enforcement for set of UEs | 18.0.0 | +| 2022-12 | SA#98E | SP-221086 | 0079 | 3 | B | Procedure for PDU Session supporting HR-SBO in VPLMN | 18.0.0 | +| 2022-12 | SA#98E | SP-221086 | 0082 | 3 | B | Influencing UPF and EAS (re)location for collections of UEs | 18.0.0 | +| 2023-03 | SA#99 | SP-230059 | 0073 | 7 | B | EAS Re-discovery Procedure with EASDF in HR roaming scenario | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0083 | 4 | B | Edge Relocation within the same hosting PLMN's EHEs | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0084 | 13 | B | Home Routed-Session Breakout (HR-SBO) support | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0087 | 4 | B | KI#4: AF traffic influence for common EAS, DNAI selection | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0088 | 4 | B | The EAS discovery procedure with V-EASDF using IP replacement mechanism for supporting HR-SBO | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0089 | 4 | B | Handling AF traffic influence for HR-SBO PDU Sessions | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0092 | 9 | B | DNAI mapping based on conclusions in TR 23.700-48 | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0093 | 5 | B | KI#4 23.548 common EAS enforcement for set of UEs | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0094 | 1 | B | KI#5 EDI extension for EAS discovery for GSMA OPG scenario | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0095 | 1 | B | Common DNAI relocation | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0096 | 1 | B | ECS Address Configuration Information delivery in roaming | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0098 | 1 | B | Information sharing between PLMN to support GSMA OPG | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0101 | 1 | B | Select common DNAI/EAS for a set of UEs | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0105 | 1 | B | EASDF functional description update | 18.1.0 | +| 2023-03 | SA#99 | SP-230059 | 0109 | 1 | B | UL CL/BP insertion for common EAS Discovery | 18.1.0 | +| 2023-04 | SA#99 | - | - | - | - | MCC correction to implementation of CR0095R1 | 18.1.1 | +| 2023-06 | SA#100 | SP-230462 | 0112 | 4 | B | Home Routed-Session Breakout (HR-SBO) - offload policy structure | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0120 | 7 | B | KI#1 EAS Discovery: Resolve ENs | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0122 | 2 | B | KI#1 EACI provisioning from VPLMN | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0123 | 3 | B | KI#1 EDI provision for HR-SBO | 18.2.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|-------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-06 | SA#100 | SP-230462 | 0124 | 1 | B | KI#4 DNS cache refresh triggered by common EAS-DNAI requests | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0125 | 1 | C | Clarification on ECS Address Provisioning in roaming scenarios | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0137 | 4 | B | HR SBO and DNS security | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0140 | 1 | B | Clarification for geographic area in DNAI mapping | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0142 | 5 | C | Corrections on handling the AF traffic influencing request for HR-SBO PDU Sessions | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0146 | 2 | B | Common EAS/DNAI determination for a set of UEs | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0149 | 3 | F | Solving ENs on multiple SMF coordination | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0150 | - | F | Correction on UL CL/BP insertion | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0152 | 1 | B | Update to edge relocation for HR-SBO | 18.2.0 | +| 2023-06 | SA#100 | SP-230462 | 0155 | 3 | B | EAS Re-discovery in HR-SBO context | 18.2.0 | +| 2023-09 | SA#101 | SP-230846 | 0160 | 3 | F | how to route the DNS traffic between the UE and the V-EASDF where multiple DNN networks with the same IP address range are deployed | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0161 | 2 | F | Inter V-SMF mobility registration update procedure in HR-SBO case | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0162 | 2 | F | NEF determination of the HR-SBO condition when receiving an AF request targeting an individual UE address | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0163 | 3 | F | Clarification on common DNAI selection with local DNS server | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0165 | 1 | F | Enforcement of VPLMN specific offloading information for IP range(s) | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0167 | - | F | Service correction related to traffic correlation | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0169 | 1 | F | Clarification of SMF behaviour if no common EAS IP address present in PCC rule | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0171 | 1 | F | DNS server reselection based on common DNAI | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0172 | 2 | F | Clarification on procedure of Handling of Common EAS, CommonDNAI for set of UEs | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0173 | 2 | F | Updates on EAS change procedure | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0174 | 2 | F | Updates on common DNAI selection with Local DNS Server/Resolver | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0175 | 2 | F | Updates on coordination among SMFs for common EAS/DNAI determination | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0176 | 2 | F | Clarification and editorial regarding common EAS/DNAI | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0178 | 2 | F | Clarification on EAS discovery procedure | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0179 | 2 | F | Updates on EAS rediscovery procedure | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0180 | 2 | F | KI#4 DNS cache refresh triggered by UE quitting or joining UE set | 18.3.0 | +| 2023-09 | SA#101 | SP-230846 | 0181 | - | D | Editorial Fix in the Network triggered EAS change in HR-SBO context procedure | 18.3.0 | +| 2023-12 | SA#102 | SP-231256 | 0186 | 5 | F | Enhancement on offloading information enforcement | 18.4.0 | +| 2023-12 | SA#102 | SP-231256 | 0199 | 2 | F | Update on Network triggered EAS change procedure | 18.4.0 | +| 2023-12 | SA#102 | SP-231256 | 0206 | 2 | F | Remove EN on DNS traffic routing | 18.4.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23554/01832e59ebad7ada5e790de6f90cc9b6_img.jpg b/raw/rel-18/23_series/23554/01832e59ebad7ada5e790de6f90cc9b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeadaf338a502a47794be2ce1847f8b1a30e9924 --- /dev/null +++ b/raw/rel-18/23_series/23554/01832e59ebad7ada5e790de6f90cc9b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d3819cc412f36f8f86a315160c8c63aeb0cc4de5481ca13ef574c90193f26f1 +size 33146 diff --git a/raw/rel-18/23_series/23554/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/raw/rel-18/23_series/23554/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c90a3d405cbc8f718ea0eb97d301bded3bfea2dd --- /dev/null +++ b/raw/rel-18/23_series/23554/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1da50315e7d9f06c0007abbc0ca090514bf21b57127a4e700e09233a5b1ee9d +size 58840 diff --git a/raw/rel-18/23_series/23554/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/raw/rel-18/23_series/23554/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b9694e8c8a32aa1e3da643798ea4796f1b5bc77 --- /dev/null +++ b/raw/rel-18/23_series/23554/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:218fb25cafc43851cd32bcdeb413d6bd8eb7641ebf1b58534851c828eeccaec8 +size 33597 diff --git a/raw/rel-18/23_series/23554/070352b751dd0711b8ac6ddfa6df1d98_img.jpg b/raw/rel-18/23_series/23554/070352b751dd0711b8ac6ddfa6df1d98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdbeaa81c88a0f2b3817433a3d3494c3cc176112 --- /dev/null +++ b/raw/rel-18/23_series/23554/070352b751dd0711b8ac6ddfa6df1d98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b02b0135db1dc37f46e39605571a67b4f5c3d1050f43eb145fd1a2fda7ae2dfa +size 67511 diff --git a/raw/rel-18/23_series/23554/07b81106e8525814c458f262000c54a9_img.jpg b/raw/rel-18/23_series/23554/07b81106e8525814c458f262000c54a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6799155ad62f1821052e41a27c6f3d6240fbc8fc --- /dev/null +++ b/raw/rel-18/23_series/23554/07b81106e8525814c458f262000c54a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89e9fe1ccb635b9178a7b2f259078e9a99ece7f3f7bbfbf61986349dfcf64559 +size 24322 diff --git a/raw/rel-18/23_series/23554/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/raw/rel-18/23_series/23554/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e6c79044a93d6b1a41f7113311bfc0aff0dd4f9 --- /dev/null +++ b/raw/rel-18/23_series/23554/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdf1687b1ff30a2687188ff7f8c86b54ebca1c239682b435d1cfc9914a7b07e3 +size 152784 diff --git a/raw/rel-18/23_series/23554/0e252770f8f0573617e0112b36a93d2f_img.jpg b/raw/rel-18/23_series/23554/0e252770f8f0573617e0112b36a93d2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de2fd86e1873a6729ad9c05788dfda7d223979a1 --- /dev/null +++ b/raw/rel-18/23_series/23554/0e252770f8f0573617e0112b36a93d2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4804d9c99cbee0d7301d1f1c8f455573b9e2a050352faca682ee85ffce9644ee +size 94894 diff --git a/raw/rel-18/23_series/23554/1033dc9fde75540d224c907681b1b7aa_img.jpg b/raw/rel-18/23_series/23554/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f56798323baef24e0d992d402f7b98e848b4b17b --- /dev/null +++ b/raw/rel-18/23_series/23554/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c618001aa84cd95c1b57b80c7b53d820b89d530eaa04880eb823673df5116648 +size 31402 diff --git a/raw/rel-18/23_series/23554/107c8e1abcb7033ad244e30e7a910045_img.jpg b/raw/rel-18/23_series/23554/107c8e1abcb7033ad244e30e7a910045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..752665a9267d570a817b8079fad0ab7df38ee288 --- /dev/null +++ b/raw/rel-18/23_series/23554/107c8e1abcb7033ad244e30e7a910045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63b18a5afa1260949099c682a83c890e4d1bf9a645a049efde89e19f4b5f6752 +size 115155 diff --git a/raw/rel-18/23_series/23554/13dbd16a58861b335d8e10047ae8e524_img.jpg b/raw/rel-18/23_series/23554/13dbd16a58861b335d8e10047ae8e524_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57284927e94c835b9647b6142267c525a1ff8d6a --- /dev/null +++ b/raw/rel-18/23_series/23554/13dbd16a58861b335d8e10047ae8e524_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc86624c48c28c4ee428731f62cebf07c8303646d0c641cca68b5ebd1fc648d7 +size 72879 diff --git a/raw/rel-18/23_series/23554/18722c46c9e8475524e634dedd08bac2_img.jpg b/raw/rel-18/23_series/23554/18722c46c9e8475524e634dedd08bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..493933631fd7f609f8bd717fe39908ff0ab77d80 --- /dev/null +++ b/raw/rel-18/23_series/23554/18722c46c9e8475524e634dedd08bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3144877aca5ff79be21add92f4f5d7c5a98017e1aa89ac3eaadc3b5c26a98034 +size 33810 diff --git a/raw/rel-18/23_series/23554/19499072f755b22d0a231123f75fa477_img.jpg b/raw/rel-18/23_series/23554/19499072f755b22d0a231123f75fa477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcc9f91b423aa674fe66ab89dfa0024dba69901b --- /dev/null +++ b/raw/rel-18/23_series/23554/19499072f755b22d0a231123f75fa477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7703d66f865de1d5222bc93ca8c07dd9ac8723a00c26b67e76bb9ed9c60f0599 +size 31945 diff --git a/raw/rel-18/23_series/23554/1b2ad37940c441d410002c05ff71c7c5_img.jpg b/raw/rel-18/23_series/23554/1b2ad37940c441d410002c05ff71c7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a1ab06515f700a1968d984b22865006dcffade9 --- /dev/null +++ b/raw/rel-18/23_series/23554/1b2ad37940c441d410002c05ff71c7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fff1379e06ca9e6b101de765d1d88a9d814733ae84e08ae74baa3a17aca4f69 +size 34993 diff --git a/raw/rel-18/23_series/23554/1b34b4b9929df6a81e43e106be67c533_img.jpg b/raw/rel-18/23_series/23554/1b34b4b9929df6a81e43e106be67c533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dea07b8c6365308ca47381aaf8400489a7b821ab --- /dev/null +++ b/raw/rel-18/23_series/23554/1b34b4b9929df6a81e43e106be67c533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13b11fcd8a3c2310c74c364e30f7f57a305dca115bcc899fef4d7c5463bdd64b +size 43630 diff --git a/raw/rel-18/23_series/23554/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/raw/rel-18/23_series/23554/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..289a43231a901e1e8acd7b4d3180a0a6c8447de2 --- /dev/null +++ b/raw/rel-18/23_series/23554/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88ac16b45a22614fe131cbd9ef4247da0e8fd99f3655066d0514a8298c240f45 +size 35242 diff --git a/raw/rel-18/23_series/23554/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/raw/rel-18/23_series/23554/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9d884c8ba80fb821ed474980b354ea7617508a1 --- /dev/null +++ b/raw/rel-18/23_series/23554/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca8811f6a59fbe61390009e129bc3657242b588c069911eeeeeae73ae642dbe7 +size 45888 diff --git a/raw/rel-18/23_series/23554/205c14458d7f4e2d22c75354bb451e99_img.jpg b/raw/rel-18/23_series/23554/205c14458d7f4e2d22c75354bb451e99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..560691837c5fbbd2dc2e0d08af10494d78b196cc --- /dev/null +++ b/raw/rel-18/23_series/23554/205c14458d7f4e2d22c75354bb451e99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aab957c6411a208d828ab920d485bf2815a57e5460a4eaf93b8abe31be527b4e +size 50939 diff --git a/raw/rel-18/23_series/23554/235e996e83e7d5198cf9d909f5713cdd_img.jpg b/raw/rel-18/23_series/23554/235e996e83e7d5198cf9d909f5713cdd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..992bfa39815a3fa1be4979f2a6f3e5ff8733c30d --- /dev/null +++ b/raw/rel-18/23_series/23554/235e996e83e7d5198cf9d909f5713cdd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0a29478779c9fcf542097692b2376952f3c25419f418d47b56ee0f649eb23a5 +size 77115 diff --git a/raw/rel-18/23_series/23554/24ca460ee3381aee781887e9e586ec67_img.jpg b/raw/rel-18/23_series/23554/24ca460ee3381aee781887e9e586ec67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc0f5fcebd5ee3816e8c91dc9d20ad0c6d61cdca --- /dev/null +++ b/raw/rel-18/23_series/23554/24ca460ee3381aee781887e9e586ec67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:874f7446bebf97dcdc3a7f92647cd9aab7ed27b9aa1e8a235163dcf2d1d675dd +size 49397 diff --git a/raw/rel-18/23_series/23554/27788c2a26d9641e68232a4eff1299b9_img.jpg b/raw/rel-18/23_series/23554/27788c2a26d9641e68232a4eff1299b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a786f8935245098f7af9f9a4e85cfff85a0a56e --- /dev/null +++ b/raw/rel-18/23_series/23554/27788c2a26d9641e68232a4eff1299b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4768e2f7878ac9a4a1f2e68ddb14a5085de8a36706d324558f1aceffc38e049 +size 89429 diff --git a/raw/rel-18/23_series/23554/27f9c45d41672d72c3cc3c2ea386ebbb_img.jpg b/raw/rel-18/23_series/23554/27f9c45d41672d72c3cc3c2ea386ebbb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83a0eeb9a08627a902229b5414ddba6ef9131a22 --- /dev/null +++ b/raw/rel-18/23_series/23554/27f9c45d41672d72c3cc3c2ea386ebbb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7956329f69e490d93668567f62368f591510773d8c9859e36ad5d45da936b10a +size 36817 diff --git a/raw/rel-18/23_series/23554/2b00743506f6a3bbd17af764162dc76d_img.jpg b/raw/rel-18/23_series/23554/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72a919fab71dd3fe5a5fcfebe02c1e1177e59723 --- /dev/null +++ b/raw/rel-18/23_series/23554/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01d91d849b27d6c4261bcda73400c31cde2cfa32515613cd48e0320932fc4a70 +size 45987 diff --git a/raw/rel-18/23_series/23554/2d548db0b26b7bf33244320322d5ee2c_img.jpg b/raw/rel-18/23_series/23554/2d548db0b26b7bf33244320322d5ee2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46e236dd1bf7de41b10fb232f6931c3b4276d7ee --- /dev/null +++ b/raw/rel-18/23_series/23554/2d548db0b26b7bf33244320322d5ee2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0045b611e7bf4c173d8b92f75964cadaf7d3fe6fd746f779367b9df61a56172 +size 36716 diff --git a/raw/rel-18/23_series/23554/2eeee46b99394d7a37c46cd876e6cbc2_img.jpg b/raw/rel-18/23_series/23554/2eeee46b99394d7a37c46cd876e6cbc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..946e86231781bac1bff1e949df486269e3456ac7 --- /dev/null +++ b/raw/rel-18/23_series/23554/2eeee46b99394d7a37c46cd876e6cbc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9445285db497878952a9eb3fbf920a7a1990367ae4a5e48a3f87c424735646a0 +size 24885 diff --git a/raw/rel-18/23_series/23554/2fbb410da68e626ba5e994d872031f14_img.jpg b/raw/rel-18/23_series/23554/2fbb410da68e626ba5e994d872031f14_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a41fc0cdec90bd1e7fc17ed7d16d50c7c00bda4e --- /dev/null +++ b/raw/rel-18/23_series/23554/2fbb410da68e626ba5e994d872031f14_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d33bc0240460430c8672fa8ba21edbedc61b5ab978c3425209d51f77d2b4fa3 +size 150279 diff --git a/raw/rel-18/23_series/23554/32ff77da4286b58c4778033acaa10836_img.jpg b/raw/rel-18/23_series/23554/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e944de4b878f6db9bf85722d55715ca6d3a209de --- /dev/null +++ b/raw/rel-18/23_series/23554/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e97780774b60b4ab2456427db6ab4fb8d2885ee71e5a535b9968b4d6548d937a +size 31920 diff --git a/raw/rel-18/23_series/23554/364054adcd1b427fa259450e006c6b38_img.jpg b/raw/rel-18/23_series/23554/364054adcd1b427fa259450e006c6b38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e916725e2effd60780c10ecd5557d46c74e7d21 --- /dev/null +++ b/raw/rel-18/23_series/23554/364054adcd1b427fa259450e006c6b38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e0fb405b72002630432d0da45fa58a9ee4da2cbbb49567932978c2691ebdc6c +size 50322 diff --git a/raw/rel-18/23_series/23554/38a51baf4d5b8857d162e5d9a0645269_img.jpg b/raw/rel-18/23_series/23554/38a51baf4d5b8857d162e5d9a0645269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2209eb809f0765df1316bd8cdc7678ff6c0d7cc --- /dev/null +++ b/raw/rel-18/23_series/23554/38a51baf4d5b8857d162e5d9a0645269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddc4ecb9fa3027e0bd0c7b8d4a51e5a5a00e98e26fcf0234d251c4bc414e0225 +size 46023 diff --git a/raw/rel-18/23_series/23554/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg b/raw/rel-18/23_series/23554/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b60754d29e9cd84bef728f1dd429d289885b909 --- /dev/null +++ b/raw/rel-18/23_series/23554/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa1e82929845aa57ffc3ab345dc5e30f93a0ab86e424649d01d15d6fa45ba7ba +size 39523 diff --git a/raw/rel-18/23_series/23554/3c99312f83459559d9a301148555d7b9_img.jpg b/raw/rel-18/23_series/23554/3c99312f83459559d9a301148555d7b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a48478f3ad95c3141253265d83574eff23cd388b --- /dev/null +++ b/raw/rel-18/23_series/23554/3c99312f83459559d9a301148555d7b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:092be92521b85131c7351a62b69a1d938e66ef4b11b4cecff7f278d02aff9696 +size 38516 diff --git a/raw/rel-18/23_series/23554/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/raw/rel-18/23_series/23554/3ce04f1c7128814978c6b34d654a25cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4d26216d79b64f1cb763fa4f389c26583bf267a --- /dev/null +++ b/raw/rel-18/23_series/23554/3ce04f1c7128814978c6b34d654a25cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d08c0e9e45716945a80eb0a8d3a688bbe4f04a3bd1f419fd198df56cc001ef6 +size 91110 diff --git a/raw/rel-18/23_series/23554/40ebe9179df298f1b6d76822f28d90aa_img.jpg b/raw/rel-18/23_series/23554/40ebe9179df298f1b6d76822f28d90aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..003e58b2770462cb86caa8a91e4b00ab0bf2f03f --- /dev/null +++ b/raw/rel-18/23_series/23554/40ebe9179df298f1b6d76822f28d90aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e27a01f6fd0ba2a8d38332388f25ed7d28db75fb6442779c7c9a02ebf6379f66 +size 36617 diff --git a/raw/rel-18/23_series/23554/426a0ab9454f31706038a0ac0bc37b9c_img.jpg b/raw/rel-18/23_series/23554/426a0ab9454f31706038a0ac0bc37b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da09f1720986d9fe3f43510efec70c5c69a3a9c9 --- /dev/null +++ b/raw/rel-18/23_series/23554/426a0ab9454f31706038a0ac0bc37b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23f3fb84e5628d82906c237f68f7c27d72b555e7bfe973e6d8f87e4fdc56fe82 +size 52986 diff --git a/raw/rel-18/23_series/23554/43437211ce989e9da795fecc0d499c05_img.jpg b/raw/rel-18/23_series/23554/43437211ce989e9da795fecc0d499c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5756b1a1afedcc68239b5eabb4f47baa2598cd88 --- /dev/null +++ b/raw/rel-18/23_series/23554/43437211ce989e9da795fecc0d499c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8350d30a66a5e32c27a791c2df82c1aa7b61e7dab67f7e54c36d6420cb70f36 +size 32646 diff --git a/raw/rel-18/23_series/23554/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/raw/rel-18/23_series/23554/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b34bc6aa165acc65045a919b5e22b267aeade0c --- /dev/null +++ b/raw/rel-18/23_series/23554/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36955a42e51ba4a51e7fa3b0ee920b038e6806966760ec057c9e3fdb7caa2bda +size 45019 diff --git a/raw/rel-18/23_series/23554/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/raw/rel-18/23_series/23554/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..399e9217a1d8d52c428496f119844769bd95f89f --- /dev/null +++ b/raw/rel-18/23_series/23554/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0dfdeb74edb45b05b1b471c6b6a122e22bed8ae19483ec1d521922e58d2edb4 +size 96025 diff --git a/raw/rel-18/23_series/23554/5018822abcf9dc551579c7620b07701a_img.jpg b/raw/rel-18/23_series/23554/5018822abcf9dc551579c7620b07701a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa13f37c156635db2ba17cb82f4f5448fc456392 --- /dev/null +++ b/raw/rel-18/23_series/23554/5018822abcf9dc551579c7620b07701a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a45c051178787c516e74d45a2aa46a4c7a4d47063a6797764a70fa552f8eea7f +size 25391 diff --git a/raw/rel-18/23_series/23554/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg b/raw/rel-18/23_series/23554/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b47d500fdadff18c7ff5f7ac3211de322c6e5f2b --- /dev/null +++ b/raw/rel-18/23_series/23554/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:903417461e114832ddc3a325940a0029e2291553042d3545f49c037f457321a6 +size 46022 diff --git a/raw/rel-18/23_series/23554/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23554/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b47e9eab469e0789acb71685acdee9536fc4c7bd --- /dev/null +++ b/raw/rel-18/23_series/23554/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e05bcdedf45c0c74d26867c864ae1515d1a05b739250049aca3eab8218b0f64 +size 9465 diff --git a/raw/rel-18/23_series/23554/61a49f3179b455e4d35242fc3d187a29_img.jpg b/raw/rel-18/23_series/23554/61a49f3179b455e4d35242fc3d187a29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f035235515bf435003a8aec0f21f244e6574ef90 --- /dev/null +++ b/raw/rel-18/23_series/23554/61a49f3179b455e4d35242fc3d187a29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e089e5d29ecb574606fbc09d46d2816af5ed999885ece807ba5675b9d33eb460 +size 54979 diff --git a/raw/rel-18/23_series/23554/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23554/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d9e3a7abfac1c47911e19e1764852832a908c03 --- /dev/null +++ b/raw/rel-18/23_series/23554/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4db132b160bd34606d14f3211c42e194bd3b1c06dd70793efb6229d34bd425cb +size 5655 diff --git a/raw/rel-18/23_series/23554/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/raw/rel-18/23_series/23554/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbb7a04b8a82fe36c3d5801bea0c08f8f2fdc9e8 --- /dev/null +++ b/raw/rel-18/23_series/23554/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:470108beff0c4ef1ba89222dc2ffcfb5b6c5069f3eb74619fcf548326b16103f +size 19627 diff --git a/raw/rel-18/23_series/23554/66e89867f97592fd4bfab0e4f2b2054f_img.jpg b/raw/rel-18/23_series/23554/66e89867f97592fd4bfab0e4f2b2054f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de62c54d6caff21271c8126aed3b258ea65458a4 --- /dev/null +++ b/raw/rel-18/23_series/23554/66e89867f97592fd4bfab0e4f2b2054f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5942c44f3ef138e805ea87b996f660047cbd21d49c5b39d72fdc4b244f68039 +size 72985 diff --git a/raw/rel-18/23_series/23554/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/raw/rel-18/23_series/23554/675af5bb2357ce5b510e613d04f66bdc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9641666cdef65ca6a18137ad9ce4aad9688d95bf --- /dev/null +++ b/raw/rel-18/23_series/23554/675af5bb2357ce5b510e613d04f66bdc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:638b91fdabecf836b0493b1d50f1fbf1a7ae9fa2cd60d45fe762924ad0e57920 +size 29235 diff --git a/raw/rel-18/23_series/23554/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/raw/rel-18/23_series/23554/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e0729f689eadc89233aab8a2e46a3950688bc93 --- /dev/null +++ b/raw/rel-18/23_series/23554/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:830ba476b4cba5fa32ae97bfb1b76add6a00fe91e1b15e010b49a1a453a6711e +size 24588 diff --git a/raw/rel-18/23_series/23554/6929132b4964d52244da61d4614bc4d6_img.jpg b/raw/rel-18/23_series/23554/6929132b4964d52244da61d4614bc4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b404dbc311bf1922aa1c625758793a5e9571b07 --- /dev/null +++ b/raw/rel-18/23_series/23554/6929132b4964d52244da61d4614bc4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8d94966177cd76670175670e4bc9f3949745e5eb8096a342b3493bf11cdf26a +size 80924 diff --git a/raw/rel-18/23_series/23554/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg b/raw/rel-18/23_series/23554/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfc52e19155e386ebe016ff561cdd5e68ce1d8f4 --- /dev/null +++ b/raw/rel-18/23_series/23554/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69dda5fb2c24c14ad4848068d2da20cfc9ee14920ba12af610de635b81c3ddcd +size 52872 diff --git a/raw/rel-18/23_series/23554/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg b/raw/rel-18/23_series/23554/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaf8329b950f1f2a1ac555809ff990104aae1470 --- /dev/null +++ b/raw/rel-18/23_series/23554/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a010e31e50a849e1a1d5c9448c971fc9d30a4f5a59eb0cef112b2074d7f0172e +size 108228 diff --git a/raw/rel-18/23_series/23554/7b18671bc31881a5c474883bf6a300fd_img.jpg b/raw/rel-18/23_series/23554/7b18671bc31881a5c474883bf6a300fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fef3ab73d80a38557da4b634fa1dc55063ac0b4b --- /dev/null +++ b/raw/rel-18/23_series/23554/7b18671bc31881a5c474883bf6a300fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cc16f378903c130d1533b03bdbd0176941b868c41debce89798b90b4f6c0ca1 +size 79266 diff --git a/raw/rel-18/23_series/23554/7f7211748473542096717109ebe5a9d6_img.jpg b/raw/rel-18/23_series/23554/7f7211748473542096717109ebe5a9d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7792c0cf7aecec8bf2b83e26f4b8fea796d01463 --- /dev/null +++ b/raw/rel-18/23_series/23554/7f7211748473542096717109ebe5a9d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cc99e8e42cc7fa5c34b108195ccb31e667a16dfc77504e385ef5205711957bd +size 63195 diff --git a/raw/rel-18/23_series/23554/802707b774f2d2973b49cea2020e8453_img.jpg b/raw/rel-18/23_series/23554/802707b774f2d2973b49cea2020e8453_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fab4291852a4fde9c5f1297b071f2ce1d6fcef1 --- /dev/null +++ b/raw/rel-18/23_series/23554/802707b774f2d2973b49cea2020e8453_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83fe851e1fa9fe836284f6ea8a0836f150ab1b87b59c1a2782bdfa7e700c4f5a +size 40317 diff --git a/raw/rel-18/23_series/23554/81a0abf9a79b27cf9d765553216b173c_img.jpg b/raw/rel-18/23_series/23554/81a0abf9a79b27cf9d765553216b173c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7506c3b145e1865cedf8914c49bb6c9fa2ed9475 --- /dev/null +++ b/raw/rel-18/23_series/23554/81a0abf9a79b27cf9d765553216b173c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1b3edcea067cd846856f6c5bb44679651c43e6a70268e25fd42a172a074a282 +size 51018 diff --git a/raw/rel-18/23_series/23554/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/raw/rel-18/23_series/23554/834fb96b114b8fdc001625e1ae28e8b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a81c04eaa8ff40c47898fcadf4fccc38fd1e4426 --- /dev/null +++ b/raw/rel-18/23_series/23554/834fb96b114b8fdc001625e1ae28e8b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cca386fc1b2b8edf7444edabe09bb5dd3ae8aef7d551a5668512f5f6bfa7e88b +size 49661 diff --git a/raw/rel-18/23_series/23554/86bd357c573c9696393f5bde4d4cce4f_img.jpg b/raw/rel-18/23_series/23554/86bd357c573c9696393f5bde4d4cce4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fa0bd2afeda5dccc83f5a7e867fdaba9a5360c9 --- /dev/null +++ b/raw/rel-18/23_series/23554/86bd357c573c9696393f5bde4d4cce4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98d720ead5d073e95c683f7c2b7aca723af1c3eea3a147934b8fd50cf7ab7a0f +size 60936 diff --git a/raw/rel-18/23_series/23554/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/raw/rel-18/23_series/23554/8ab30dbff406204a68c59ae7c1b77413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebaa6dff8300a46d4f9503e381193f55d9b799ff --- /dev/null +++ b/raw/rel-18/23_series/23554/8ab30dbff406204a68c59ae7c1b77413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd607bd0d7b84cc4d6340407cbdcc18f7dc552aa9400f41deb26aac498a7eb08 +size 82933 diff --git a/raw/rel-18/23_series/23554/935075de5250cfe8aa0fb9d65d63dde5_img.jpg b/raw/rel-18/23_series/23554/935075de5250cfe8aa0fb9d65d63dde5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a07a91f22ece6c92507ee02635dda687a9211616 --- /dev/null +++ b/raw/rel-18/23_series/23554/935075de5250cfe8aa0fb9d65d63dde5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5591aa986fac9c15d7bc72cf88f24008cd3cf91407b7903ef711e6ff2c0bff +size 95133 diff --git a/raw/rel-18/23_series/23554/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg b/raw/rel-18/23_series/23554/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..138e001523d52f70b9c9ced5140c6153bb46f85e --- /dev/null +++ b/raw/rel-18/23_series/23554/987a8ea27d373fa66433e6b8cb2e98ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3613e000b3202c7e5440b8f8bbcf3dd58ceed0697bcd8bd7a2c1a42304e24beb +size 99848 diff --git a/raw/rel-18/23_series/23554/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/raw/rel-18/23_series/23554/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aefcadff1383203ed186b36515c9863c3849e54 --- /dev/null +++ b/raw/rel-18/23_series/23554/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:436690e0396c92ebf07493e11bfae10d5bd8ddfc74c6618dca844aece4f21ffd +size 10837 diff --git a/raw/rel-18/23_series/23554/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg b/raw/rel-18/23_series/23554/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17a078f5cda063b750f6e83fbf5ab3ed136db782 --- /dev/null +++ b/raw/rel-18/23_series/23554/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df443eeecf3c5f486b532e5603f4212b4f695e8ca1abcd0968ee0c6e38c68ba +size 96071 diff --git a/raw/rel-18/23_series/23554/b1e7bb95fa1587d870de03df02477df4_img.jpg b/raw/rel-18/23_series/23554/b1e7bb95fa1587d870de03df02477df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c15c6572c2849e7339eda78ac33cb72cb9acb5ab --- /dev/null +++ b/raw/rel-18/23_series/23554/b1e7bb95fa1587d870de03df02477df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b78ba17bb6b14bd6efd8bc20a427c09a8cdf8944db3143f0f824b04efae11287 +size 72372 diff --git a/raw/rel-18/23_series/23554/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/raw/rel-18/23_series/23554/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aea3fc4fb575ed3cee08c4966be6fd41ae8cce81 --- /dev/null +++ b/raw/rel-18/23_series/23554/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65b2bda1e81e550361b980cef7d3f537914bdc3e1875492d75792b12dc1a4e07 +size 52143 diff --git a/raw/rel-18/23_series/23554/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg b/raw/rel-18/23_series/23554/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5afe6ca6afc82e8a127e6e95eb2aee87f9ba1006 --- /dev/null +++ b/raw/rel-18/23_series/23554/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e123c5ab5cecc804f53b86005fc9e2412fbef9fb694779ec46e931fe6ca1132 +size 23419 diff --git a/raw/rel-18/23_series/23554/b560268ea8f6526970f23f0da225b099_img.jpg b/raw/rel-18/23_series/23554/b560268ea8f6526970f23f0da225b099_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61283ace991386eec1d0bb4c4d111bcbbef02f4b --- /dev/null +++ b/raw/rel-18/23_series/23554/b560268ea8f6526970f23f0da225b099_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a92b5f57e1b83ee821f381a4d94eece3a57cc2955592551b1e78e8227d3a90ff +size 40674 diff --git a/raw/rel-18/23_series/23554/bfc7918b689a38bc811276e0cc69477e_img.jpg b/raw/rel-18/23_series/23554/bfc7918b689a38bc811276e0cc69477e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..208cfb1a90f0c87cc352127855b156d939a5dc85 --- /dev/null +++ b/raw/rel-18/23_series/23554/bfc7918b689a38bc811276e0cc69477e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ca3a47efd3f131033bd2c7bcf695a8a2b6781e780ef1d71d0a64bdc9d7148c7 +size 79355 diff --git a/raw/rel-18/23_series/23554/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/raw/rel-18/23_series/23554/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0268ef0a3e9311294e7116f500ffe08b919e2812 --- /dev/null +++ b/raw/rel-18/23_series/23554/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26ef040abdfb3ea60a038dafdc51ea8ec139d09c2699e6d52fda58365b87e05c +size 80081 diff --git a/raw/rel-18/23_series/23554/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/raw/rel-18/23_series/23554/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89e1ec657ee09a0e929cb68dbc2da8f48d3fb787 --- /dev/null +++ b/raw/rel-18/23_series/23554/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9b8d782fbef19d6d0d15a10ce449ae882bdc9545ac7d437842a038fdf555b6d +size 25008 diff --git a/raw/rel-18/23_series/23554/c995e0bb4efc8c0f2994428aa1245709_img.jpg b/raw/rel-18/23_series/23554/c995e0bb4efc8c0f2994428aa1245709_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16c00fad06a54df66ddb1478989a77fc9cffad0c --- /dev/null +++ b/raw/rel-18/23_series/23554/c995e0bb4efc8c0f2994428aa1245709_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c78e7d6c5fc664c1c7402b9561f53002137a07d7d1624fd0e1fa8055393fb5c9 +size 27515 diff --git a/raw/rel-18/23_series/23554/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/raw/rel-18/23_series/23554/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89c90e9d95dbf3f68a970ac5fb08bfd75b306a2b --- /dev/null +++ b/raw/rel-18/23_series/23554/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b59f67ac087753f485c2f359e79a9431c3a362f93d50735dc6c5ea70e8dbdafb +size 8613 diff --git a/raw/rel-18/23_series/23554/cd3e29b6d40dce0580fa43b721157489_img.jpg b/raw/rel-18/23_series/23554/cd3e29b6d40dce0580fa43b721157489_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e875feccd0265ae967696efa77fe1f91eee18fd5 --- /dev/null +++ b/raw/rel-18/23_series/23554/cd3e29b6d40dce0580fa43b721157489_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3cf3731439da31d1ec7b9914eb2d67a3d323ec1bc2fcfd870abbe4b306fcd26 +size 92493 diff --git a/raw/rel-18/23_series/23554/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg b/raw/rel-18/23_series/23554/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32afeff7a8fe31353613b62fab6b47f944deda5c --- /dev/null +++ b/raw/rel-18/23_series/23554/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c68f68b0cf1c3e8a8d65e419ea93cdbd6071ec8d4c62656d7cf79f35b7bb097d +size 50723 diff --git a/raw/rel-18/23_series/23554/d734a6ea1b381280f043fcf70391b6db_img.jpg b/raw/rel-18/23_series/23554/d734a6ea1b381280f043fcf70391b6db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d991bf1023e16c053018d843885b1fc470b3d8 --- /dev/null +++ b/raw/rel-18/23_series/23554/d734a6ea1b381280f043fcf70391b6db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2527c0c360730b1e2ba329b736f4b8df974ee4c179862c396cb10c9ae0f95025 +size 37846 diff --git a/raw/rel-18/23_series/23554/d79de2dd022d74722a84f1b2ffce691c_img.jpg b/raw/rel-18/23_series/23554/d79de2dd022d74722a84f1b2ffce691c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2c53594e5b8a5f2e5e1725fbb5c99a575b68d38 --- /dev/null +++ b/raw/rel-18/23_series/23554/d79de2dd022d74722a84f1b2ffce691c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f5aa4dedb71cba39f02e9152041e5e31583f3aef759124d795cc32f9c939daa +size 74666 diff --git a/raw/rel-18/23_series/23554/da90447206621f137780272a2bf807a4_img.jpg b/raw/rel-18/23_series/23554/da90447206621f137780272a2bf807a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3a2022dcc5348fdece78091b34a0dc4f3013dc9 --- /dev/null +++ b/raw/rel-18/23_series/23554/da90447206621f137780272a2bf807a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6468cbfc640fda730f5d34abd088db953a987241025eb54beaef24e53f0b0242 +size 148481 diff --git a/raw/rel-18/23_series/23554/db6f6e9f69edb58bff0b65268e020fd6_img.jpg b/raw/rel-18/23_series/23554/db6f6e9f69edb58bff0b65268e020fd6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f04daa7c662fd3a44886e9ed1724191367b9ebd --- /dev/null +++ b/raw/rel-18/23_series/23554/db6f6e9f69edb58bff0b65268e020fd6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06e24c1a9146b23e9beb505e6e55741dbbe4488a6aaf718399bb12111fc3b3ff +size 67332 diff --git a/raw/rel-18/23_series/23554/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/raw/rel-18/23_series/23554/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b924cf780462d7641491fa125a76a7445d05f1f --- /dev/null +++ b/raw/rel-18/23_series/23554/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20c0f805731f028eb5505c92b894b62402f8f98554da96e6f94f309915e6898c +size 46085 diff --git a/raw/rel-18/23_series/23554/dde1a42ca58cd189901556a0cbfe7d57_img.jpg b/raw/rel-18/23_series/23554/dde1a42ca58cd189901556a0cbfe7d57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe0b3326e3f13d19f1d761a16f322f05a2a21570 --- /dev/null +++ b/raw/rel-18/23_series/23554/dde1a42ca58cd189901556a0cbfe7d57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58a172f8e337a25f2f9ff221cdd954842e5cad0267a10795421f2d38d8dcb0ef +size 67738 diff --git a/raw/rel-18/23_series/23554/e2b7490a3455c66c85db12872c78fcc3_img.jpg b/raw/rel-18/23_series/23554/e2b7490a3455c66c85db12872c78fcc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cfee3cf03f80fa8bf75bbf340d5aa5ec12060a2 --- /dev/null +++ b/raw/rel-18/23_series/23554/e2b7490a3455c66c85db12872c78fcc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa9da9333e06163351653f3eeb6eedfc64680d3f66a34bae798ccb495c67e6ae +size 86827 diff --git a/raw/rel-18/23_series/23554/e38206fcefa2045af01d494b2956775a_img.jpg b/raw/rel-18/23_series/23554/e38206fcefa2045af01d494b2956775a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e550f4256b8e0ffa0193936d4c9a1b36bf4def66 --- /dev/null +++ b/raw/rel-18/23_series/23554/e38206fcefa2045af01d494b2956775a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7413e467caba91a0efa64f40a7e7e8a582cc3dae21cef83577dca18d2f161e3 +size 44029 diff --git a/raw/rel-18/23_series/23554/e451a51157214e53bd9c64db914771cc_img.jpg b/raw/rel-18/23_series/23554/e451a51157214e53bd9c64db914771cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..444110024892269a70a765d5cc3b94b92b40981d --- /dev/null +++ b/raw/rel-18/23_series/23554/e451a51157214e53bd9c64db914771cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bce2894b809f71b39ab0dcbaca68d8f1c0b702ae4c874c15772e96eb64dd7f1 +size 28462 diff --git a/raw/rel-18/23_series/23554/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/raw/rel-18/23_series/23554/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c15e8520ba475c20240adbe4eb3b3fe21e2c9fe3 --- /dev/null +++ b/raw/rel-18/23_series/23554/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f0c4efac2025b9558b82f677c9c2507432393dca2660572f1d6d8af0629c35d +size 96863 diff --git a/raw/rel-18/23_series/23554/ec3647789b5c38fb686f2a0833324e79_img.jpg b/raw/rel-18/23_series/23554/ec3647789b5c38fb686f2a0833324e79_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..785a11bcf1958bdbabe1209947d5132fa54c3a2e --- /dev/null +++ b/raw/rel-18/23_series/23554/ec3647789b5c38fb686f2a0833324e79_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:573d2883d8d5fdf82005922090e00dcc3a1ee786b46fffc56c5e945fc6955016 +size 150175 diff --git a/raw/rel-18/23_series/23554/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/raw/rel-18/23_series/23554/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff2c651395891a8f1996ab38411d083fc3edd724 --- /dev/null +++ b/raw/rel-18/23_series/23554/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b96414632b323cf7e10909fdbcf467acd8076ead972996671bda8be9769fe5b +size 37200 diff --git a/raw/rel-18/23_series/23554/f8d508872d762c83336443cfd20c5412_img.jpg b/raw/rel-18/23_series/23554/f8d508872d762c83336443cfd20c5412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0a73a53be98ab7f42749afb7734309c787a1af8 --- /dev/null +++ b/raw/rel-18/23_series/23554/f8d508872d762c83336443cfd20c5412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a068e0dfd6729a655ec396e81ce4ce04ffff6bf6094d6c0a7032b70927c32814 +size 72179 diff --git a/raw/rel-18/23_series/23554/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/raw/rel-18/23_series/23554/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87b45dd6317a5605e31e110b0815759195a060d1 --- /dev/null +++ b/raw/rel-18/23_series/23554/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f44aa11f7266bcf3b056b683b4aa9543861f75baf5be545d5a31956f7325c477 +size 37127 diff --git a/raw/rel-18/23_series/23554/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/raw/rel-18/23_series/23554/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4812fb68a95bd26a46e694b3ae153e23cf3038e3 --- /dev/null +++ b/raw/rel-18/23_series/23554/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a408a43ebb2ad3079a0e1ecab71ed8dec01c5c6f0b44b2a2b6aa2071d5e4d5ec +size 76696 diff --git a/raw/rel-18/23_series/23554/ff87509cc2b267501d910a2d9f9054ac_img.jpg b/raw/rel-18/23_series/23554/ff87509cc2b267501d910a2d9f9054ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb979a5a79bb52f3b047a7d037b64e7a04c66b0a --- /dev/null +++ b/raw/rel-18/23_series/23554/ff87509cc2b267501d910a2d9f9054ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cdda145410464d3974696d9c598ee5ae3baa9b454c769c48ea5e73c5c9ae8bf +size 44004 diff --git a/raw/rel-18/23_series/23554/raw.md b/raw/rel-18/23_series/23554/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6b126f999ec5a154e84af737da0734cf8f50cfbf --- /dev/null +++ b/raw/rel-18/23_series/23554/raw.md @@ -0,0 +1,5589 @@ + + +# 3GPP TS 23.554 V18.6.0 (2023-12) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Application architecture for MSGin5G Service; Stage 2 (Release 18)** + +![5G ADVANCED logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black letters to the right. + +5G ADVANCED logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The logo for the 3rd Generation Partnership Project (3GPP), featuring the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon, and below the entire logo is the text 'A GLOBAL INITIATIVE' in small, black, uppercase letters. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------|----| +| Foreword ..... | 8 | +| Introduction ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Symbols..... | 11 | +| 3.3 Abbreviations ..... | 11 | +| 4 Architectural requirements..... | 12 | +| 4.1 General ..... | 12 | +| 4.1.1 Description ..... | 12 | +| 4.1.2 Requirements..... | 12 | +| 4.2 UE types ..... | 12 | +| 4.2.1 Description ..... | 12 | +| 4.2.2 Requirements..... | 12 | +| 4.3 Communication models..... | 12 | +| 4.3.1 Description ..... | 12 | +| 4.3.2 Requirements..... | 13 | +| 4.4 Charging..... | 13 | +| 4.4.1 Introduction ..... | 13 | +| 4.4.2 Requirements..... | 13 | +| 5 Application layer architecture..... | 13 | +| 5.1 General ..... | 13 | +| 5.2 Application Architecture..... | 13 | +| 5.3 Functional entities ..... | 16 | +| 5.3.1 General ..... | 16 | +| 5.3.2 MSGin5G Server ..... | 16 | +| 5.3.2.1 General functionalities ..... | 16 | +| 5.3.2.2 Target resolution ..... | 17 | +| 5.3.3 MSGin5G Client..... | 17 | +| 5.3.3.1 General functionalities of MSGin5G Client ..... | 17 | +| 5.3.3.2 MSGin5G Gateway Client..... | 18 | +| 5.3.4 Message Gateway..... | 18 | +| 5.3.4.1 General Description of Message Gateway..... | 18 | +| 5.3.4.2 Legacy 3GPP Message Gateway..... | 19 | +| 5.3.4.3 Non-3GPP Message Gateway..... | 19 | +| 5.3.4.4 Broadcast Message Gateway ..... | 19 | +| 5.3.5 Application Client ..... | 19 | +| 5.3.6 Application Server..... | 19 | +| 5.3.7 Legacy 3GPP Message Client ..... | 19 | +| 5.3.8 Non-3GPP Message Client..... | 20 | +| 5.3.9 SEAL Client ..... | 20 | +| 5.3.10 SEAL server ..... | 20 | +| 5.4 Reference Points..... | 20 | +| 5.4.1 General ..... | 20 | +| 5.4.2 MSGin5G-1 ..... | 20 | +| 5.4.3 MSGin5G-2 ..... | 20 | +| 5.4.4 MSGin5G-3 ..... | 20 | +| 5.4.5 MSGin5G-4 ..... | 21 | +| 5.4.6 MSGin5G-5 ..... | 21 | +| 5.4.7 MSGin5G-6 ..... | 21 | +| 5.4.8 SEAL-C ..... | 21 | +| 5.4.9 SEAL-S..... | 21 | + +| | | | +|--------|---------------------------------------------------------------------------|----| +| 5.4.10 | SEAL-UU ..... | 21 | +| 5.5 | Capability exposure for enabling MSGin5G Service..... | 22 | +| 5.5.1 | MSGin5G application enabler layer adaptation to CAPIF ..... | 22 | +| 5.6 | Service based interface representation for MSGin5G Service..... | 22 | +| 5.6.1 | General ..... | 22 | +| 5.6.2 | Service based architecture ..... | 22 | +| 5.6.3 | Service based interfaces ..... | 23 | +| 6 | Identities..... | 24 | +| 6.1 | Identities for MSGin5G Service endpoints ..... | 24 | +| 6.1.1 | General ..... | 24 | +| 6.1.2 | UE Service Identity (UE Service ID) ..... | 24 | +| 6.1.3 | Application Server Service Identity (AS Service ID) ..... | 24 | +| 6.1.4 | Message Gateway Service Identity (MGW Service ID) ..... | 24 | +| 6.2 | MSGin5G Group Service Identity (Group Service ID) ..... | 24 | +| 6.3 | Broadcast Area Service Identity (Broadcast Area ID)..... | 25 | +| 6.4 | MSGin5G UE Identity (MSGin5G UE ID)..... | 25 | +| 6.5 | Non-MSGin5G UE identity (Non-MSGin5G UE ID) ..... | 25 | +| 6.6 | Application Identity (Application ID)..... | 25 | +| 6.7 | MSGin5G Server address..... | 25 | +| 7 | Generic description of the MSGin5G Service (informative)..... | 25 | +| 7.1 | General ..... | 25 | +| 7.2 | Service flow..... | 26 | +| 7.3 | Message delivery flow at MSGin5G Server ..... | 27 | +| 8 | Procedures and information flows ..... | 28 | +| 8.1 | Configuration ..... | 28 | +| 8.1.1 | General ..... | 28 | +| 8.1.2 | MSGin5G UE Configuration..... | 28 | +| 8.1.3 | Message Gateway Configuration for support of Non-MSGin5G UE ..... | 29 | +| 8.1.4 | MSGin5G UE bulk configuration over MSGin5G-6 reference point ..... | 30 | +| 8.2 | Registration ..... | 31 | +| 8.2.0 | General ..... | 31 | +| 8.2.1 | MSGin5G UE Registration..... | 32 | +| 8.2.2 | MSGin5G UE De-Registration..... | 34 | +| 8.2.3 | Non-MSGin5G UE Registration ..... | 35 | +| 8.2.4 | Non-MSGin5G UE De-registration..... | 37 | +| 8.2.5 | Application Server Registration ..... | 38 | +| 8.2.6 | Application Server De-registration..... | 39 | +| 8.2.7 | MSGin5G UE bulk registration over MSGin5G-6 reference point..... | 39 | +| 8.2.8 | Constrained device with MSGin5G Client selecting MSGin5G Gateway UE ..... | 42 | +| 8.2.9 | Non-MSGin5G UE bulk registration..... | 45 | +| 8.2.10 | Non-MSGin5G UE bulk de-registration ..... | 46 | +| 8.2.11 | MSGin5G UE bulk de-registration over MSGin5G-6 reference point..... | 47 | +| 8.3 | Message delivery procedures ..... | 50 | +| 8.3.1 | General ..... | 50 | +| 8.3.2 | MSGin5G messages origination procedure..... | 50 | +| 8.3.3 | MSGin5G messages termination procedure..... | 55 | +| 8.3.4 | MSGin5G message delivery status report into the MSGin5G Server..... | 57 | +| 8.3.5 | MSGin5G message delivery status report from the MSGin5G Server ..... | 60 | +| 8.3.6 | MSGin5G Store and Forward..... | 62 | +| 8.4 | Message Aggregation..... | 64 | +| 8.4.1 | General ..... | 64 | +| 8.4.2 | Message Aggregation at MSGin5G Client..... | 64 | +| 8.4.3 | Message aggregation at MSGin5G Server ..... | 71 | +| 8.5 | MSGin5G Message Segmentation and Reassembly ..... | 74 | +| 8.5.1 | General ..... | 74 | +| 8.5.2 | Application-to-Point Segmentation and Reassembly ..... | 75 | +| 8.5.3 | Point-to-Application Message Segmentation and Reassembly ..... | 77 | +| 8.5.4 | Point-to-Point Message Segmentation and Reassembly ..... | 79 | +| 8.5.5 | Group Message Segmentation and Reassembly..... | 81 | +| 8.5.6 | MSGin5G Message Segment Recovery ..... | 81 | + +| | | | +|-----------|-------------------------------------------------------------------------------|-----| +| 8.6 | MSGin5G messaging procedure on Message Gateway ..... | 82 | +| 8.6.1 | General MSGin5G messaging procedure on Message Gateway ..... | 82 | +| 8.6.2 | Non-MSGin5G UE receives message from group ..... | 84 | +| 8.6.2.1 | Legacy 3GPP UE receives message from group ..... | 84 | +| 8.6.2.2 | Non-3GPP message client receives message from group ..... | 85 | +| 8.7 | E2E Message delivery procedures ..... | 86 | +| 8.7.1 | Point-to-Point Message delivery procedures ..... | 86 | +| 8.7.1.1 | From MSGin5G UE to MSGin5G UE ..... | 86 | +| 8.7.1.2 | From MSGin5G UE to Legacy 3GPP UE ..... | 87 | +| 8.7.1.3 | From MSGin5G UE to Non-3GPP UE ..... | 88 | +| 8.7.1.4 | From Legacy 3GPP UE to MSGin5G UE ..... | 89 | +| 8.7.1.5 | From Non-3GPP UE to MSGin5G UE ..... | 91 | +| 8.7.2 | Application-to-Point Message delivery procedures ..... | 92 | +| 8.7.2.1 | From Application Server to MSGin5G UE ..... | 92 | +| 8.7.2.2 | From Application Server to Legacy 3GPP UE ..... | 93 | +| 8.7.2.3 | From Application Server to Non-3GPP UE ..... | 94 | +| 8.7.3 | Point-to-Application Message delivery procedures ..... | 95 | +| 8.7.3.1 | From MSGin5G UE to Application Server ..... | 95 | +| 8.7.3.2 | From Legacy 3GPP UE to Application Server ..... | 96 | +| 8.7.3.3 | From Non-3GPP UE to Application Server ..... | 97 | +| 8.7.4 | MSGin5G Group messaging ..... | 98 | +| 8.7.4.1 | General ..... | 98 | +| 8.7.4.2 | Message delivery from UE to group ..... | 98 | +| 8.7.4.3 | Message delivery procedure from Application Server to group ..... | 99 | +| 8.7.5 | Message delivery between different PLMNs ..... | 100 | +| 8.7.5.1 | General ..... | 100 | +| 8.7.5.2 | Inter-PLMN message exchange procedure ..... | 100 | +| 8.7.5.3 | Inter-PLMN message exchange procedure based on Messaging Topic ..... | 101 | +| 8.7.6 | Broadcast message delivery ..... | 103 | +| 8.7.6.1 | General ..... | 103 | +| 8.7.6.2 | Broadcast message delivery procedure ..... | 103 | +| 8.8 | Other MSGin5G messaging related procedures ..... | 104 | +| 8.8.0 | General ..... | 104 | +| 8.8.1 | Messaging Topic Subscription ..... | 105 | +| 8.8.2 | Message delivery based on Messaging Topic ..... | 106 | +| 8.8.3 | Messaging Topic Unsubscription ..... | 107 | +| 8.8.4 | Messaging Topic Subscription handling between different MSGin5G Servers ..... | 108 | +| 8.8.4.1 | General ..... | 108 | +| 8.8.4.2 | Messaging Topic list subscription ..... | 108 | +| 8.8.4.2a | Messaging Topic list unsubscription ..... | 111 | +| 8.8.4.3 | Messaging Topic Subscription between different MSGin5G Servers ..... | 112 | +| 8.8.4.4 | Messaging Topic Unsubscription between different MSGin5G Servers ..... | 113 | +| 8.9.1 | General ..... | 113 | +| 8.9.2 | UE reachability status monitoring ..... | 113 | +| 8.9.2.1 | General ..... | 113 | +| 8.9.2.2 | Procedures ..... | 114 | +| 8.9.2.2.1 | Request-response ..... | 114 | +| 8.9.2.2.2 | Subscribe ..... | 115 | +| 8.9.2.2.3 | Notify ..... | 115 | +| 8.9.2.2.4 | Unsubscribe ..... | 116 | +| 8.9.2.3 | Flows ..... | 117 | +| 8.9.3 | MSGin5G device triggering ..... | 117 | +| 8.9.3.1 | General ..... | 117 | +| 8.9.3.2 | Procedure ..... | 118 | +| 8.9.3.3 | Flows ..... | 119 | +| 8.10.1 | General ..... | 119 | +| 8.10.2 | Configuration management service ..... | 120 | +| 8.10.2.1 | General ..... | 120 | +| 8.10.2.2 | Information flows ..... | 120 | +| 8.10.2.3 | Procedures ..... | 120 | +| 8.10.3 | Group management service ..... | 121 | +| 8.10.3.1 | General ..... | 121 | + +| | | | +|-----------|---------------------------------------------------------------------------------|-----| +| 8.10.3.2 | Information flows ..... | 121 | +| 8.10.3.3 | Procedures..... | 121 | +| 8.10.3.4 | APIs ..... | 121 | +| 8.11 | Application Client resides different UE in MSGin5G Service ..... | 122 | +| 8.11.1 | General ..... | 122 | +| 8.11.2 | Application Client registration using MSGin5G Client ..... | 122 | +| 8.11.3 | Application Client de-registration using MSGin5G Client ..... | 123 | +| 8.11.4 | Application Client sending a message using MSGin5G Client on another UE ..... | 124 | +| 8.11.5 | Application Client receiving message via MSGin5G Client on another UE ..... | 126 | +| 9 | APIs and related information flows ..... | 127 | +| 9.1 | APIs provided by MSGin5G Server..... | 127 | +| 9.1.1 | Mm5s APIs..... | 127 | +| 9.1.1.1 | M5S_AS_Originating_Message_Delivery API..... | 127 | +| 9.1.1.1.1 | General ..... | 127 | +| 9.1.1.1.2 | Send_MSGin5G_Message operation ..... | 127 | +| 9.1.1.2 | M5S_UE_Originating_Message_Delivery API ..... | 128 | +| 9.1.1.2.1 | General ..... | 128 | +| 9.1.1.2.2 | Send_MSGin5G_Message operation ..... | 128 | +| 9.1.1.3 | M5S_AS_Originating_Delivery_Status_Report API..... | 128 | +| 9.1.1.3.1 | General ..... | 128 | +| 9.1.1.3.2 | Report_Message_Delivery_Status operation ..... | 128 | +| 9.1.1.4 | M5S_Delivery_Status_Report API..... | 128 | +| 9.1.1.4.1 | General ..... | 128 | +| 9.1.1.4.2 | Report_Message_Delivery_Status operation ..... | 128 | +| 9.1.1.5 | M5S_AS_Registration API..... | 129 | +| 9.1.1.5.1 | General ..... | 129 | +| 9.1.1.5.2 | Registration operation ..... | 129 | +| 9.1.1.5.3 | Deregistration operation..... | 129 | +| 9.1.1.6 | M5S_Topiclist_Event API..... | 129 | +| 9.1.1.6.1 | General ..... | 129 | +| 9.1.1.6.2 | Subscribe Messaging Topiclist operation ..... | 129 | +| 9.1.1.6.3 | Notify Messaging Topiclist operation..... | 129 | +| 9.1.1.6.4 | Subscribe Messaging Topic operation ..... | 130 | +| 9.1.1.6.5 | Notify Messaging Topic operation..... | 130 | +| 9.1.1.6.6 | Unsubscribe Messaging Topiclist operation ..... | 130 | +| 9.1.1.6.7 | Unsubscribe Messaging Topic operation ..... | 130 | +| 9.1.2 | Mm5s Information flows ..... | 131 | +| 9.1.2.1 | M5S Application Server originating message send request ..... | 131 | +| 9.1.2.2 | M5S Application Server originating message delivery status report request ..... | 131 | +| 9.1.2.3 | M5S Application Server registration request..... | 131 | +| 9.1.2.4 | M5S Application Server registration response ..... | 131 | +| 9.1.2.5 | M5S Application Server de-registration request ..... | 132 | +| 9.1.2.6 | M5S Application Server de-registration response ..... | 132 | +| 9.2 | APIs provided by Message Gateway ..... | 132 | +| 9.2.1 | MI3g APIs ..... | 132 | +| 9.2.1.1 | L3G_Message_Delivery API..... | 132 | +| 9.2.1.1.1 | General ..... | 132 | +| 9.2.1.1.2 | Send_Message operation..... | 132 | +| 9.2.1.2 | L3G_Delivery_Status_Report API..... | 133 | +| 9.2.1.2.1 | General ..... | 133 | +| 9.2.1.2.2 | Report_Message_Delivery_Status operation ..... | 133 | +| 9.2.2 | Mn3g APIs..... | 133 | +| 9.2.2.1 | N3G_Message_Delivery API ..... | 133 | +| 9.2.2.1.1 | General ..... | 133 | +| 9.2.2.1.2 | Send_Message operation..... | 133 | +| 9.2.2.2 | N3G_Delivery_Status_Report API..... | 133 | +| 9.2.2.2.1 | General ..... | 133 | +| 9.2.2.2.2 | Report_Message_Delivery_Status operation ..... | 133 | +| 9.2.3 | Mbg APIs..... | 134 | +| 9.2.3.1 | Nbg_Message_Delivery API..... | 134 | +| 9.2.3.1.1 | General ..... | 134 | + +| | | | +|-------------------------------|---------------------------------------------------------|------------| +| 9.2.3.1.2 | Send_Message operation..... | 134 | +| 10 | Information Elements..... | 134 | +| 10.1 | Payload..... | 134 | +| 10.2 | Application ID..... | 134 | +| 10.3 | Messaging Topic..... | 134 | +| 10.4 | Broadcast Area ID..... | 135 | +| 10.5 | Message ID..... | 135 | +| 10.6 | Failure Cause..... | 135 | +| 11 | Deployment models ..... | 135 | +| 11.1 | General ..... | 135 | +| 11.2 | Deployment of MSGin5G server(s)..... | 135 | +| 11.3 | Deployment of Message Gateway(s)..... | 137 | +| 11.4 | Deployment of MSGin5G Server(s) and SEAL server(s)..... | 138 | +| Annex A (informative): | Change history..... | 139 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +# 1 Scope + +The present document specifies the functional architecture, procedures, information flows and APIs for MSGin5G Service. MSGin5G Service provides messaging communication capability in 5GS especially for Massive Internet of Things (MIoT). + +MSGin5G Service includes the following message communication models: + +- Point-to-Point message; +- Application-to-Point message/ Point-to-Application message; +- Group message; +- Broadcast message. + +The corresponding service requirements are defined in 3GPP TS 22.262 [2]. + +MSGin5G Service provides the following capabilities to enhance the message delivery for all message communication models: + +- MSGin5G Store and Forward; +- Message communication based on Messaging Topic; +- Message Aggregation; +- Message Segmentation and Reassembly; +- Message Gateway to interwork with non MSGin5G messaging services; +- Usage of Network Capabilities including UE reachability status monitoring and MSGin5G device triggering. + +The present specification also defines the usage and interactions of the MSGin5G Service with SEAL services and the utilizing of SEAL functionalities in MSGin5G service. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.262: "Message Service within the 5G System". +- [3] GSMA PRD RCC.07: "RCC.07 Rich Communication Suite 9.0 Advanced Communications Services and Client Specification". +- [4] OMA OMA-ERELD-LightweightM2M-V1\_1-20180612-C: "Enabler Release Definition for LightweightM2M". +- [5] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals". + +- [6] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2". +- [7] 3GPP TS 23.502: "Procedures for the 5G System". +- [8] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [9] 3GPP TS 29.122: "T8 reference point for northbound Application Programming Interfaces (APIs)". +- [10] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3". +- [11] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [12] 3GPP TS 23.501: "System Architecture for the 5G System (5GS); Stage 2". +- [13] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2". +- [14] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [15] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [16] 3GPP TS 33.501: "Security architecture and procedures for 5G System". +- [17] 3GPP TS 32.240: "Charging architecture and principles". +- [18] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)". +- [19] 3GPP TS 23.303: "Proximity-based services (ProSe)". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**AS-to-Point messaging:** an MSGin5G message delivery that is originated at an Application Server in the network and terminated at a UE. + +**Broadcast Area:** an area consisting of one or more cells where the broadcast message is delivered. + +**Broadcast messaging:** an MSGin5G message delivery that is delivered to UEs in a Broadcast Area. + +**Broadcast Message Gateway:** the entity in MSGin5G Service to support delivery Broadcast messages to Legacy 3GPP UEs, Non-3GPP UEs and MSGin5G UEs. + +**Constrained UE:** an MSGin5G UE which cannot connect to the 3GPP network directly for message exchange with MSGin5G Server. + +**Group messaging:** message delivery that is originated at a UE or an Application Server and is terminated at all members of the group (a group member can be of type UE, Legacy 3GPP UE or Non-3GPP UE). + +**Legacy 3GPP Message Gateway:** the entity in MSGin5G Service to support interworking with Legacy 3GPP UEs. + +**Legacy 3GPP UE:** the UE that supports legacy 3GPP message sending and receiving (e.g. SMS, NIDD, etc) in MSGin5G Service. + +**MSGin5G Client:** the client that enables MSGin5G message sending and receiving. + +**Message Gateway:** general terminology for Legacy 3GPP Message Gateway, Non-3GPP Message Gateway, or Broadcast Message Gateway. + +**MSGin5G Gateway UE:** an MSGin5G UE that can provide access to multiple constrained UEs to connect to the 3GPP network for MSGin5G services. + +**MSGin5G Group:** the group of UEs which members may be MSGin5G UE, Legacy 3GPP UE and Non-3GPP UE. + +**MSGin5G message:** the message defined in the present specification that is exchanged between the MSGin5G Service endpoints under the MSGin5G Service. + +**MSGin5G Server:** a server in MSGin5G Service that receives and delivers MSGin5G messages among MSGin5G Service endpoints. + +**MSGin5G Service:** an MNO message service using the 5G System that enables Point- to-Point, AS-to-Point, Point-to-AS, Group and Broadcast message delivery for thing-to-thing communication and person-to-thing communication. + +**Messaging Topic:** an identifier for a topic to which a UE or an Application Server can subscribe to in order to receive messages that are characterized by a Message Topic. + +**MSGin5G UE:** the UE that uses MSGin5G Client in MSGin5G Service. + +**Non-3GPP Message Gateway:** the entity in MSGin5G Service to support interworking with Non-3GPP UEs. + +**Non-3GPP UE:** the UE that supports non-3GPP message sending and receiving (e.g. RCS message as specified in GSMA PRD RCC.07 [3], OMA LWM2M message as specified in OMA OMA-ERELD-LightweightM2M [4]) in MSGin5G Service. + +NOTE: The MSGin5G UE utilizes MSGin5G Client in MSGin5G Service. The Legacy 3GPP UE and Non-3GPP UE does not utilize MSGin5G Client in MSGin5G Service. + +**Non-MSGin5G UE:** general terminology for Legacy 3GPP UE or Non-3GPP UE. + +**Point-to-AS messaging:** an MSGin5G message delivery that is originated at a UE and terminated at an Application Server. + +**Point-to-Point messaging:** an MSGin5G message delivery that originates at a UE and terminates at a UE, where at least one of the end points is an MSGin5G UE. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|--------------------------------------------------| +| 5GS | 5G System | +| AOMT | AS-Originated Mobile-Terminated | +| AS | Application Server | +| BMG | Broadcast Message Gateway | +| CAPIF | Common API Framework for northbound APIs | +| MOAT | Mobile-Originated AS-Terminated | +| MOMT | Mobile-Originated Mobile-Terminated | +| NIDD | Non IP Data Delivery | +| SCEF | Service Capability Exposure Function | +| SCS | Service Capability Server | +| SEAL | Service Enabler Architecture Layer for Verticals | + +| | | +|------|------------------------------| +| SMSC | Short Message Service Center | +| VAL | Vertical Application Layer | + +# --- 4 Architectural requirements + +## 4.1 General + +### 4.1.1 Description + +This subclause specifies the general architecture requirements for MSGin5G Service. + +### 4.1.2 Requirements + +[AR-4.1.2-a] The MSGin5G Client shall support one or more applications which need to use the MSGin5G message exchanging capabilities. + +[AR-4.1.2-b] The MSGin5G Server shall support one or more Applications Servers which support the MSGin5G message exchanging capabilities. + +[AR-4.1.2-c] The MSGin5G messaging related capabilities (e.g. registration, Point-to-Point messaging, Group messaging, message delivery status, etc.) should be exposed as APIs to the Applications Server(s). + +[AR-4.1.2-d] The application architecture shall enable the communication between the UEs in different PLMNs. The UEs support MSGin5G Service. + +[AR-4.1.2-e] The MSGin5G service should support different application priority levels for the MSGin5G messages including High, Normal and Low. + +## 4.2 UE types + +### 4.2.1 Description + +This subclause specifies the requirements for UE types supported by MSGin5G Service. + +### 4.2.2 Requirements + +[AR-4.2.2-a] The application architecture shall support the message exchanging between the following UE types: + +1. MSGin5G UE: + - 1) constrained devices (e.g. sensors, actuators) and + - 2) unconstrained devices with advanced capabilities (e.g. washing machine, micro-ovens) +2. Legacy 3GPP UE +3. Non-3GPP UE + +[AR-4.2.2-b] The application architecture shall enable the unconstrained devices to act as a MSGin5G Gateway UE to constrained devices to communicate with MSGin5G Server. + +## 4.3 Communication models + +### 4.3.1 Description + +This subclause specifies the requirements for MSGin5G communication models. + +### 4.3.2 Requirements + +[AR-4.3.2-a] The application architecture shall support the following message communication models: + +- 1 Point-to-Point message; +- 2 Application-to-Point message/ Point-to-Application message; +- 3 Group message; +- 4 Broadcast message. + +[AR-4.3.2-b] The application architecture shall support interconnecting between the MSGin5G Service and other different messaging delivery mechanisms, (e.g. SMS as specified in 3GPP TS23.040 [15], or RCS message as specified in GSMA PRD RCC.07 [3]). + +## 4.4 Charging + +### 4.4.1 Introduction + +This subclause specifies the charging related requirements for the MSGin5G Service. + +### 4.4.2 Requirements + +[AR-4.4.2] The MSGin5G Server shall support collecting charging information from MSGin5G message according to the operator's charging policy including charge per message, charge by amount of data, and flat rate (e.g., per month or per year). + +# --- 5 Application layer architecture + +## 5.1 General + +The following aspects of MSGin5G Service are described in this clause: + +- application architecture; +- functional entities; +- reference points; +- capability exposure for enabling MSGin5G Service; and +- service-based interface representation for MSGin5G Service. + +## 5.2 Application Architecture + +Figure 5.2-1 shows the application architecture of the MSGin5G service. The MSGin5G service shall fulfil the service requirements which are enumerated in 3GPP TS 22.262 [2] and the architecture requirements enumerated in clause 4. + +![Figure 5.2-1: Application Architecture of the MSGin5G Service. This block diagram illustrates the interactions between various network elements and user equipment (UE) for the MSGin5G service. On the left, a 'Non-3 GPP UE' (dashed box) contains a 'Non-3 GPP message client' connected to a 'Non-3 GPP Message Gateway'. Below it, 'UE-2' contains 'Application Client(s)' connected to 'MSGin5G UE-1' via the MSGin5G-5 interface. 'MSGin5G UE-1' contains an 'Application Client(s)', 'MSGin5G Client', and 'SEAL Client(s)'. The 'MSGin5G Client' connects to 'MSGin5G Server(s)' via MSGin5G-1 and to 'SEAL Client(s)' via SEAL-C. 'UE-2' also connects to 'MSGin5G Server(s)' via MSGin5G-5. 'Legacy3 GPP UE (e.g., SMS, NIDD)' (dashed box) connects to a 'Legacy 3 GPP Message Gateway', which in turn connects to 'MSGin5G Server(s)' via MSGin5G-2. The 'Non-3 GPP Message Gateway' connects to 'MSGin5G Server(s)' via MSGin5G-4. A 'Broadcast Message Gateway' connects to 'MSGin5G Server(s)' via MSGin5G-7. At the top right, 'Application Server(s)' connect to 'MSGin5G Server(s)' via MSGin5G-3. 'MSGin5G Server(s)' connects to 'SEAL Server(s)' via SEAL-S. 'SEAL Client(s)' in 'MSGin5G UE-1' connect to 'SEAL Server(s)' via Network Interfaces and SEAL-Uu. A '3 GPP Core Network(s)' block is shown in the center with dashed lines indicating out-of-scope interactions. A legend indicates that solid lines are 'In scope' and dashed lines are 'Out of scope non-3GPP'.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) + +Figure 5.2-1: Application Architecture of the MSGin5G Service. This block diagram illustrates the interactions between various network elements and user equipment (UE) for the MSGin5G service. On the left, a 'Non-3 GPP UE' (dashed box) contains a 'Non-3 GPP message client' connected to a 'Non-3 GPP Message Gateway'. Below it, 'UE-2' contains 'Application Client(s)' connected to 'MSGin5G UE-1' via the MSGin5G-5 interface. 'MSGin5G UE-1' contains an 'Application Client(s)', 'MSGin5G Client', and 'SEAL Client(s)'. The 'MSGin5G Client' connects to 'MSGin5G Server(s)' via MSGin5G-1 and to 'SEAL Client(s)' via SEAL-C. 'UE-2' also connects to 'MSGin5G Server(s)' via MSGin5G-5. 'Legacy3 GPP UE (e.g., SMS, NIDD)' (dashed box) connects to a 'Legacy 3 GPP Message Gateway', which in turn connects to 'MSGin5G Server(s)' via MSGin5G-2. The 'Non-3 GPP Message Gateway' connects to 'MSGin5G Server(s)' via MSGin5G-4. A 'Broadcast Message Gateway' connects to 'MSGin5G Server(s)' via MSGin5G-7. At the top right, 'Application Server(s)' connect to 'MSGin5G Server(s)' via MSGin5G-3. 'MSGin5G Server(s)' connects to 'SEAL Server(s)' via SEAL-S. 'SEAL Client(s)' in 'MSGin5G UE-1' connect to 'SEAL Server(s)' via Network Interfaces and SEAL-Uu. A '3 GPP Core Network(s)' block is shown in the center with dashed lines indicating out-of-scope interactions. A legend indicates that solid lines are 'In scope' and dashed lines are 'Out of scope non-3GPP'. + +**Figure 5.2-1: Application Architecture of the MSGin5G Service** + +The Application Client resides on the same UE with the MSGin5G Client as shown in MSGin5G UE-1, or resides on a different UE and interacts with the MSGin5G Client over the MSGin5G-5 reference point as shown in UE-2. + +The MSGin5G Client(s) interacts with SEAL Clients over the SEAL-C reference point specified for each SEAL service. The MSGin5G Server(s) interacts with SEAL Servers over the SEAL-S reference point specified for each SEAL service. The interaction between a SEAL Client and the corresponding SEAL Server is supported by SEAL-UU reference point specified for each SEAL service as specified in 3GPP TS 23.434 [5]. + +The MSGin5G UE-1 communicates with MSGin5G Server over MSGin5G-1 reference point. + +The Legacy 3GPP Message Gateway interacts with MSGin5G Server over MSGin5G-2 reference point on behalf of Legacy 3GPP UE (e.g., SMS, NIDD). + +The Non-3GPP Message Gateway interacts with MSGin5G Server over MSGin5G-4 reference point on behalf of Non-3GPP UE. + +The Broadcast Message Gateway interacts with MSGin5G Server over MSGin5G-7 reference point. + +NOTE 1: A SEAL Group Management Server and a SEAL Configuration Management Server (both specified in 3GPP TS 23.434 [5]) may be collocated in the MSGin5G Server. A SEAL Configuration Management Client specified in 3GPP TS 23.434 [5] may be collocated in the MSGin5G Client, Legacy 3GPP Message Gateway and Non-3GPP Message Gateway. The implementation of such deployment option is out of scope of the present specification. + +NOTE 2: Depending on the non-3GPP message service, the interaction between Non-3GPP message client and Non-3GPP Message Gateway may involve 3GPP Core Network. + +NOTE 3: 3GPP Core Network may not be involved for the interaction between the Non-3GPP Message Gateway and the MSGin5G Server. + +NOTE 4: If the Application Client on UE-2 communicates with the MSGin5G Client on UE-1 over the MSGin5G-5 reference point then the transport layer communication is based on the Unicast mode 5G ProSe Direct Communication specified in 3GPP TS 23.304 [18] or is implementation specific. + +The architecture shown in Figure 5.2-2 and Figure 5.2-3 illustrate architectural options for providing MSGin5G services for constrained devices. In these figures, the MSGin5G UE-2 is a constrained device which does not connect to the 3GPP network directly for message exchange with MSGin5G Server (e.g. UE-2 is out of 3GPP RAN coverage, with or without authorization to use UE-to-Network relay). If allowed by configuration, the MSGin5G UE-2 can use the options listed below to communicate with the MSGin5G Server: + +- the MSGin5G UE-2 uses an UE-1 as relay; +- the MSGin5G UE-2 interacts with an MSGin5G Gateway UE which supports MSGin5G Gateway Client. + +Figure 5.2-2 shows the application architecture of MSGin5G UE-2 using an UE-1 as a relay. The SEAL Client(s) residing on the UE-1 also acts as relay for the SEAL Client(s) residing on the MSGin5G UE-2 as specified in 3GPP TS 23.434 [5]. + +NOTE 5: In this option, MSGin5G UE-2 discovers the UE-1 and then uses the UE-1 as a ProSe UE-to-Network Relay by using the procedure specified in 3GPP TS 23.304 [18]. + +NOTE 6: The UE-1 can be any UE supporting ProSe UE-to-Network Relay capability and may not be an MSGin5G UE. + +![Figure 5.2-2: MSGin5G UE-2 using UE-1 as a relay. The diagram shows three main components: MSGin5G UE-2, UE-1, and MSGin5G Server. MSGin5G UE-2 contains an Application Client(s), MSGin5G Client, and SEAL Client(s). UE-1 contains MSGin5G-1 and SEAL-UU. MSGin5G Server is a separate entity. Connections: MSGin5G Client in UE-2 connects to MSGin5G-1 in UE-1 via MSGin5G-5; SEAL Client(s) in UE-2 connects to SEAL-UU in UE-1 via SEAL-C; MSGin5G-1 in UE-1 connects to MSGin5G Server; SEAL-UU in UE-1 connects to MSGin5G Server.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +Figure 5.2-2: MSGin5G UE-2 using UE-1 as a relay. The diagram shows three main components: MSGin5G UE-2, UE-1, and MSGin5G Server. MSGin5G UE-2 contains an Application Client(s), MSGin5G Client, and SEAL Client(s). UE-1 contains MSGin5G-1 and SEAL-UU. MSGin5G Server is a separate entity. Connections: MSGin5G Client in UE-2 connects to MSGin5G-1 in UE-1 via MSGin5G-5; SEAL Client(s) in UE-2 connects to SEAL-UU in UE-1 via SEAL-C; MSGin5G-1 in UE-1 connects to MSGin5G Server; SEAL-UU in UE-1 connects to MSGin5G Server. + +**Figure 5.2-2: MSGin5G UE-2 using UE-1 as a relay** + +Figure 5.2-3 shows the application architecture of MSGin5G UE-2 with MSGin5G Client interacts with an MSGin5G Gateway UE over the MSGin5G-6 reference point. + +NOTE 7: Both MSGin5G Client functionality and MSGin5G Gateway service functionality are internal functionalities of MSGin5G Gateway Client. The interaction between MSGin5G Client functionality in the MSGin5G Gateway Client and the MSGin5G Gateway service functionality is implementation specific. + +![Figure 5.2-3: MSGin5G UE-2 with MSGin5G Client interacts with an MSGin5G Gateway UE. The diagram shows three main components: MSGin5G UE-2, MSGin5G Gateway UE, and MSGin5G Server. MSGin5G UE-2 contains an Application Client(s) and MSGin5G Client. MSGin5G Gateway UE contains MSGin5G Gateway Client, which is further divided into MSGin5G Client functionality and MSGin5G Gateway service functionality. MSGin5G Server is a separate entity. Connections: MSGin5G Client in UE-2 connects to MSGin5G Gateway Client in Gateway UE via MSGin5G-6; MSGin5G Client functionality in Gateway UE connects to MSGin5G Server via MSGin5G-1; MSGin5G Gateway service functionality in Gateway UE connects to MSGin5G Server.](18722c46c9e8475524e634dedd08bac2_img.jpg) + +Figure 5.2-3: MSGin5G UE-2 with MSGin5G Client interacts with an MSGin5G Gateway UE. The diagram shows three main components: MSGin5G UE-2, MSGin5G Gateway UE, and MSGin5G Server. MSGin5G UE-2 contains an Application Client(s) and MSGin5G Client. MSGin5G Gateway UE contains MSGin5G Gateway Client, which is further divided into MSGin5G Client functionality and MSGin5G Gateway service functionality. MSGin5G Server is a separate entity. Connections: MSGin5G Client in UE-2 connects to MSGin5G Gateway Client in Gateway UE via MSGin5G-6; MSGin5G Client functionality in Gateway UE connects to MSGin5G Server via MSGin5G-1; MSGin5G Gateway service functionality in Gateway UE connects to MSGin5G Server. + +**Figure 5.2-3: MSGin5G UE-2 with MSGin5G Client interacts with an MSGin5G Gateway UE** + +NOTE 8: MSGin5G-6 reference point is based on the Unicast mode 5G ProSe Direct Communication specified in 3GPP TS 23.304 [18]. + +**Editor's note: How to handle SEAL Client functionality in a constrained MSGin5G UE is FFS.** + +Figure 5.2-4 illustrates the functional model for interconnection between MSGin5G servers. + +![Diagram showing the interconnection between two MSGin5G Servers. MSGin5G Server 1 is connected to MSGin5G Server 2 via a horizontal line labeled MSGin5G-8.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +graph LR + S1[MSGin5G Server 1] ---|MSGin5G-8| S2[MSGin5G Server 2] + +``` + +Diagram showing the interconnection between two MSGin5G Servers. MSGin5G Server 1 is connected to MSGin5G Server 2 via a horizontal line labeled MSGin5G-8. + +**Figure 5.2-4: Interconnection between MSGin5G Servers** + +To support distributed SEAL server deployment in one PLMN, and delivering MSGin5G messages between different PLMNs, the MSGin5G Server interacts with another MSGin5G Server over MSGin5G-8 reference point. + +## 5.3 Functional entities + +### 5.3.1 General + +The functional entities of the application architecture for the MSGin5G Service are described in this clause. + +### 5.3.2 MSGin5G Server + +#### 5.3.2.1 General functionalities + +An MSGin5G Server provides server-side functionality to assist MSGin5G Clients with the sending and receiving of messages via the MSGin5G Service to/from Application Servers and/or other MSGin5G Service endpoints on other UEs, and collect charging information from MSGin5G message. + +Functionalities of MSGin5G Server: + +- To manage MSGin5G UEs that are home to the MSGin5G Server and provides: + - handling the registration of these MSGin5G UEs + - handling the message initiation by these MSGin5G UEs + - handling the message delivery to these MSGin5G UEs +- To deliver messages to an MSGin5G Service endpoint based on the terminating MSGin5G Service ID. The terminating MSGin5G Service ID may be served by the same MSGin5G Server or served by another MSGin5G Server. If the MSGin5G Service ID is served by another MSGin5G Server, the MSGin5G Server forwards the messages to the next MSGin5G Server until it reaches to the MSGin5G Server that is the home of the terminating MSGin5G Service ID; +- To resolve the MSGin5G Group Service ID to determine the members of the Group as specified in 3GPP TS 23.434[5]; +- Interworking with non 3GPP messaging service through the Non-3GPP Message Gateway; +- Interworking with legacy 3GPP messaging service through the Legacy 3GPP Message Gateway; +- Interworking with a 3GPP broadcast service through the Broadcast Message Gateway; +- Exchanging MSGin5G messages with Application Servers, MSGin5G Clients, Legacy 3GPP Message Gateway, and Non-3GPP Message Gateway; + +- Supporting MSGin5G message segmentation according to service provider's policy; +- Supporting UE configuration procedures as specified in TS 23.434 [5] or communicating with the SEAL Configuration Management Server to provide MSGin5G configuration data on a UE to be ready for the MSGin5G Service; +- Managing information related to the MSGin5G Service, such as MSGin5G Client Triggering Information, MSGin5G Client availability and MSGin5G Client Supported Maximum MSGin5G segment size, and Broadcast Message Gateway; +- Support store and forward of messages based on the sender request and the availability and reachability of the service endpoints, and +- Interactions towards the CHF, as defined in TS 32.240 [17], to collect charging information from MSGin5G message according to the operator's charging policy and report charging information to CHF. + +NOTE: The details of charging function are out of scope of the present document. + +#### 5.3.2.2 Target resolution + +Upon receiving the MSGin5G message request to deliver the message to the recipient (which could be any of the MSGin5G UE, Legacy 3GPP UE, Non-3GPP UE or Application Server), the MSGin5G Server checks the recipient's registration status (created at the time of each MSGin5G UE/Application Server registration to MSGin5G Server, or the Message Gateway performs registration with the MSGin5G Server on behalf of the Non-MSGin5G UEs) for availability and reachability of MSGin5G service endpoints. The MSGin5G Server will attempt for delivery of the MSGin5G message request towards recipient based on the UE Service ID/AS Service ID, if the recipient is available and reachable. If the recipient is unavailable, the MSGin5G Server stores the message for deferred delivery unless the sender or the recipient opted out of store and forward services. + +NOTE: If reachability monitoring (see clause 8.9.2) is not used or the recipient is not an MSGin5G UE, the MSGin5G Server assumes the recipient is reachable. + +If the recipient is Non-MSGin5G UE, the Legacy 3GPP Message Gateway or the Non-3GPP Message Gateway that the Non-MSGin5G UE is registered with, will receive the MSGin5G message request on behalf of the Non-MSGin5G UE, and then delivers the message to the Non-MSGin5G UE by using the Non-MSGin5G message delivery mechanism. + +If the message is a Broadcast message, the Broadcast Message Gateway will receive the MSGin5G message request and will deliver the message to all UEs in the Broadcast Area via the Broadcast messaging delivery mechanism, based on the Broadcast Area ID. + +### 5.3.3 MSGin5G Client + +#### 5.3.3.1 General functionalities of MSGin5G Client + +An MSGin5G Client provides client-side functionality for UE Application Clients with the sending and receiving of messages via the MSGin5G Service to/from Application Servers and/or other MSGin5G Service endpoints; i.e. UEs. + +Functionalities of MSGin5G Client including: + +- may expose MSGin5G APIs to enable Application Clients to use an MSGin5G Service; +- supporting (de-)registration of an MSGin5G Client to an MSGin5G Server to use MSGin5G Service; +- supporting configuration of an MSGin5G Client required to use MSGin5G Service; +- construction of MSGin5G message when requested by a native application or Application Client; +- delivery of MSGin5G message payload to the targeted native application or Application Client; +- exchanging MSGin5G messages via an MSGin5G Server to/from Application Servers and/or other MSGin5G Service endpoints; i.e. UEs; + +- support MSGin5G message segmentation and re-assembly; +- support MSGin5G message aggregation and segregation + +NOTE 1: A native application on an MSGin5G UE is the application logic built within the MSGin5G Client. + +NOTE 2: An MSGin5G Client residing in a constrained device is the same as an MSGin5G Client residing in an unconstrained device. i.e. both of them use the same transport/data formats and have the same capabilities. + +#### 5.3.3.2 MSGin5G Gateway Client + +An MSGin5G Gateway Client is an MSGin5G Client which supports MSGin5G Gateway service functionality in addition to the MSGin5G Client functionalities specified in clause 5.3.3.1. It enables constrained devices to obtain services from the MSGin5G Server when communications via ProSe UE-to-Network Relay are not or cannot be supported. + +The MSGin5G Gateway service functionality in the MSGin5G Gateway Client supports: + +- supporting the bulk configuration and bulk (de-)registration for the MSGin5G Client residing on the Constrained UE, e.g. checking whether bulk configuration/bulk (de-)registration can be used, holding the (de-)registration request from MSGin5G Client residing on the constrained device, construction of the bulk (de-)registration request and splitting of the MSGin5G UE bulk (de-)registration response. + +NOTE: Whether other capabilities, e.g. detailing of the support for (de-)registration of constrained devices, are needed to be supported by MSGin5G Gateway service functionality is out of scope of the present document. + +### 5.3.4 Message Gateway + +#### 5.3.4.1 General Description of Message Gateway + +A Message Gateway in the MSGin5G application architecture provides functionality to deliver MSGin5G messages to Non-MSGin5G UEs. + +NOTE 1: It is an implementation option to deliver broadcast messages to Legacy 3GPP UEs and MSGin5G UEs (see Figure 5.2-1). + +A Message Gateway performs the role of interconnecting two different messaging delivery mechanisms and assures the message integrity between different message delivery mechanisms. A message delivery mechanism comprises the specific set of protocols, procedures and rules. + +Functionalities of Message Gateway: + +- Enables seamless delivery of an MSGin5G message between different message delivery mechanisms with integrity; +- Communicates with the MSGin5G Server using either an MSGin5G Client functionality or similar functions to enable sending and receiving MSGin5G messages; +- Delivers payload of an MSGin5G message to the Non-MSGin5G UE using the specific message delivery mechanism available to that Non-MSGin5G UE and vice versa; +- Performs message sender and receiver addresses conversion according to the two connected message delivery mechanisms and maintain the mapping of the address pair used for a response message delivery; +- Perform registration and de-registration with the MSGin5G Server on behalf of the Non-MSGin5G UEs; +- Act as a service endpoint to perform message segmentation and reassembly for the Non-MSGin5G UEs when needed; +- Act as a service endpoint to split the aggregated MSGin5G message into multiple individual MSGin5G message requests for the Non-MSGin5G UEs; and + +- Performs protocol conversion according to the service supported by the target UE; +- Supports the MSGin5G message delivery status report + 1. If application level message delivery status report is not supported by the Non-MSGin5G message delivery mechanisms, based on the information (e.g. response to the message delivery request, transport level information, etc) obtained from the Non-MSGin5G message delivery mechanisms, the Message Gateway fetches the delivery status from the above information and uses it to create an MSGin5G message delivery status report on behalf of Non-MSGin5G UE. If the delivery status is failure, also fetch the suitable failure reason from the above information and use it as reason of failure in the MSGin5G message delivery status report. + 2. If application level message delivery status report is supported by the Non-MSGin5G message delivery mechanisms (e.g. RCS specified in GSMA PRD RCC.07 [3]), translates the application level message delivery status report in the Non-MSGin5G message delivery mechanisms to MSGin5G message delivery status report. + +There are three types of Message Gateways used to deliver MSGin5G messages to different UE types: the Legacy 3GPP Message Gateway, the non-3GPP Message Gateway, and the Broadcast Message Gateway. + +NOTE 2: Implementation of the Message Gateway and the MSGin5G Server together is a deployment option that is out of scope the present specification. + +#### 5.3.4.2 Legacy 3GPP Message Gateway + +The Legacy 3GPP Message Gateway is used to deliver MSGin5G message to Legacy 3GPP UEs, using their 3GPP supported message delivery mechanisms. + +#### 5.3.4.3 Non-3GPP Message Gateway + +The Non-3GPP Message Gateway is used to deliver MSGin5G message to Non-MSGin5G UEs, using their (non-3GPP) supported message delivery mechanisms. + +#### 5.3.4.4 Broadcast Message Gateway + +The Broadcast Message Gateway is used to deliver MSGin5G message to MSGin5G UEs, Legacy 3GPP UEs or Non-MSGin5G UEs in a Broadcast Area. + +### 5.3.5 Application Client + +The Application Client is an entity in the application layer to implement and perform the application service logic for its own service. + +The Application Client interacts with MSGin5G Client for on the same or different UE sending and receiving MSGin5G messages. The Application Client provides needed information for the MSGin5G Client to perform MSGin5G Service with other endpoints. + +### 5.3.6 Application Server + +The Application Server is an entity in the application layer to implement and perform the application service logic. + +The Application Server supports sending and receiving messages with MSGin5G Service layer protocols and procedures. + +### 5.3.7 Legacy 3GPP Message Client + +The Legacy 3GPP Message Client provides client-side functionality for a Legacy 3GPP messaging service (e.g. SMS, NIDD). + +NOTE: The details of the Legacy 3GPP Message Client are out of scope of the present document. + +### 5.3.8 Non-3GPP Message Client + +The Non-3GPP Message Client provides client-side functionality for a Non-3GPP messaging service. + +NOTE: The details of the Non-3GPP message client are out of scope of the present document. + +### 5.3.9 SEAL Client + +The following SEAL Clients for MSGin5G Service are supported: + +- Group management client as specified in 3GPP TS 23.434 [5]; +- Configuration management client as specified in 3GPP TS 23.434 [5]. + +### 5.3.10 SEAL server + +The following SEAL servers for MSGin5G Service are supported: + +- Group management server as specified in 3GPP TS 23.434 [5]; +- Configuration management server as specified in 3GPP TS 23.434 [5]. + +NOTE: Usage of other SEAL services (e.g. location) from 3GPP TS 23.434 [5] for MSGin5G Service is not in scope of the present document. + +## 5.4 Reference Points + +### 5.4.1 General + +The reference points of the service architecture for the MSGin5G Service are described in this clause. + +### 5.4.2 MSGin5G-1 + +The interactions related to enabling MSGin5G message exchange between an MSGin5G Client and an MSGin5G Server are supported by the MSGin5G-1 reference point. This reference point supports: + +- Registration of an MSGin5G Client to an MSGin5G Server when not using IMS based solution; and +- The exchange of MSGin5G messages. + +### 5.4.3 MSGin5G-2 + +The interactions related to enabling MSGin5G message exchange between an MSGin5G Server and the Legacy 3GPP Message Gateway are supported by the MSGin5G-2 reference point. This reference point supports: + +- The exchange of MSGin5G messages between MSGin5G Server and the Legacy 3GPP Message Gateway; and +- Perform registration /de-registration on behalf of the Legacy 3GPP UEs that the Message Gateway connects with the MSGin5G Server. + +NOTE: Indicating the delivery mechanism on the MSGin5G-2 reference point is out of scope of current functionality. + +### 5.4.4 MSGin5G-3 + +The interactions related to enabling MSGin5G message exchange between an Application Server and an MSGin5G Server are supported by the MSGin5G-3 reference point. This reference point supports: + +- Access to MSGin5G Server and APIs to enable sending and receiving of MSGin5G messages; and + +- Adherence to CAPIF as specified in 3GPP TS 23.222 [6]. + +### 5.4.5 MSGin5G-4 + +The interactions related to enabling MSGin5G message exchange between a Non-3GPP Message Gateway and an MSGin5G Server are supported by the MSGin5G-4 reference point. This reference point supports: + +- The exchange of MSGin5G messages between MSGin5G Server and the Non-3GPP Message Gateway; and +- Perform registration/de-registration on behalf of the Non-3GPP UEs that the Message Gateway connects with the MSGin5G Server + +### 5.4.6 MSGin5G-5 + +The interactions related to enabling MSGin5G message related information exchange between an Application Client and an MSGin5G Client are supported by the MSGin5G-5 reference point. The Application Client can reside on the same UE with the MSGin5G Client or reside on a different UE. This reference point supports: + +- Providing information from Application Clients required to enable the MSGin5G Client to construct an MSGin5G message to be delivered to other MSGin5G Service endpoints. +- Configuring application clients with information required to enable the MSGin5G Client and MSGin5G Server to exchange and route MSGin5G messages to other MSGin5G Service endpoints. +- Sending notifications and information in the incoming MSGin5G messages received by the MSGin5G Client to the Application Clients from other MSGin5G Service endpoints. + +### 5.4.7 MSGin5G-6 + +The MSGin5G Client of MSGin5G UE-2 communicates with MSGin5G Gateway service functionality residing on an MSGin5G Gateway UE over MSGin5G-6 reference point. The interface is based on Unicast mode 5G ProSe Direct Communication specified in 3GPP TS 23.304 [18]. + +### 5.4.8 SEAL-C + +The following SEAL-C reference points for MSGin5G Service are supported: + +- GM-C reference point for group management as specified in 3GPP TS 23.434 [5]; +- CM-C reference point for configuration management as specified in 3GPP TS 23.434 [5]. + +### 5.4.9 SEAL-S + +The following SEAL-S reference points for MSGin5G Service are supported: + +- GM-S reference point for group management as specified in 3GPP TS 23.434 [5]; +- CM-S reference point for configuration management as specified in 3GPP TS 23.434 [5]. + +### 5.4.10 SEAL-UU + +The following SEAL-UU reference points for MSGin5G Service are supported: + +- GM-UU reference point for group management as specified in 3GPP TS 23.434 [5]; +- CM-UU reference point for configuration management as specified in 3GPP TS 23.434 [5]. + +### 5.4.11 MSGin5G-7 + +The MSGin5G-7 reference point is used by the MSGin5G Server to communicate with the Broadcast Message Gateway to deliver Broadcast messages. + +### 5.4.12 MSGin5G-8 + +The MSGin5G-8 reference point is used by the MSGin5G Server to communicate with another MSGin5G Server to deliver messages to the MSGin5G Service endpoint which is served by the other MSGin5G Server, and for message exchange related to Messaging Topic (un)subscriptions. + +## 5.5 Capability exposure for enabling MSGin5G Service + +### 5.5.1 MSGin5G application enabler layer adaptation to CAPIF + +The MSGin5G Server and Application Server may support CAPIF. When CAPIF is supported: + +- The MSGin5G Server shall support the CAPIF API provider domain functions (i.e. CAPIF-2/2e, CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e as specified in 3GPP TS 23.222 [6]) as shown in Figure 5.5.1-1; +- The Application Server shall act as API invoker and support the API invoker functions (i.e. CAPIF-1/1e and CAPIF-2/2e as specified in 3GPP TS 23.222 [6]) as shown in Figure 5.5.1-1. + +![Diagram illustrating MSGin5G adaptation to the CAPIF architecture. An Application Server (API invoker) is connected to CAPIF APIs via the CAPIF-1/1e reference point. The CAPIF APIs are part of the CAPIF core function. The CAPIF core function is connected to the MSGin5G SERVER via three reference points: CAPIF-3/3e, CAPIF-4/4e, and CAPIF-5/5e. The MSGin5G SERVER contains three functions: API exposing function, API publishing function, and API management function. The MSGin5G SERVER also connects to the Application Server via the MSGin5G-3 (CAPIF-2/2e) reference point.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +graph TD + AS[Application Server +(API invoker)] -- "CAPIF-1/1e" --> CAPIF_APIS((CAPIF APIs)) + CAPIF_APIS --- CCF[CAPIF core function] + CCF -- "CAPIF-3/3e" --> AE[API exposing function] + CCF -- "CAPIF-4/4e" --> AP[API publishing function] + CCF -- "CAPIF-5/5e" --> AM[API management function] + subgraph MSGin5G_SERVER [MSGin5G SERVER] + AE + AP + AM + end + MSGin5G_SERVER -- "MSGin5G-3 (CAPIF-2/2e)" --> AS + +``` + +Diagram illustrating MSGin5G adaptation to the CAPIF architecture. An Application Server (API invoker) is connected to CAPIF APIs via the CAPIF-1/1e reference point. The CAPIF APIs are part of the CAPIF core function. The CAPIF core function is connected to the MSGin5G SERVER via three reference points: CAPIF-3/3e, CAPIF-4/4e, and CAPIF-5/5e. The MSGin5G SERVER contains three functions: API exposing function, API publishing function, and API management function. The MSGin5G SERVER also connects to the Application Server via the MSGin5G-3 (CAPIF-2/2e) reference point. + +Figure 5.5.1-1: MSGin5G adaptation to the CAPIF architecture + +## 5.6 Service based interface representation for MSGin5G Service + +### 5.6.1 General + +The Service based architecture for MSGin5G Service is represented using functional entities and reference points between the functional entities as specified in clause 5. + +### 5.6.2 Service based architecture + +Figure 5.6.2-1 is the Service based Architecture for MSGin5G Service. + +![Figure 5.6.2-1: Service based MSGin5G Architecture diagram. The diagram shows a vertical dashed line separating the left side (AC and M5C) from the right side. On the left, AC is connected to M5C. On the right, a horizontal bus connects M5S, AS, SEAL Group management function, SEAL Configuration management function, BMG, L3G, and N3G. M5S is connected to the bus via the Mm5s interface. AS is connected to the bus via the M13g interface. The bus is connected to the SEAL Group management function via the Sgm interface, to the SEAL Configuration management function via the Scm interface, to BMG via the Mbg interface, to L3G via the Mn3g interface, and to N3G via the Mn3g interface.](d734a6ea1b381280f043fcf70391b6db_img.jpg) + +Figure 5.6.2-1: Service based MSGin5G Architecture diagram. The diagram shows a vertical dashed line separating the left side (AC and M5C) from the right side. On the left, AC is connected to M5C. On the right, a horizontal bus connects M5S, AS, SEAL Group management function, SEAL Configuration management function, BMG, L3G, and N3G. M5S is connected to the bus via the Mm5s interface. AS is connected to the bus via the M13g interface. The bus is connected to the SEAL Group management function via the Sgm interface, to the SEAL Configuration management function via the Scm interface, to BMG via the Mbg interface, to L3G via the Mn3g interface, and to N3G via the Mn3g interface. + +**Figure 5.6.2-1: Service based MSGin5G Architecture** + +NOTE: The AS, BMG, L3G and N3G in this Service based MSGin5G Architecture are in the same trust domain. + +The M5S function is a service based function exhibited by MSGin5G Server. + +The M5C function is the MSGin5G Client. + +The AC is the Application Client. + +The L3G function is a service based function exhibited by Legacy 3GPP Message Gateway. + +The N3G function is a service based function exhibited by Non-3GPP Message Gateway. + +The BMG function is a service based function exhibited by the Broadcast Message Gateway. + +The M5S manages the distribution of the messages it has received from MSGin5G UE, from Application Server, or from N3G (on behalf of Non-3GPP UE) or from L3G (on behalf of Legacy 3GPP UE). + +The M5S invokes services provided by L3G/N3G/BMG to send MSGin5G messages towards Legacy 3GPP UE, Non-3GPP UE, or the broadcast delivery mechanism. + +The AS/L3G/N3G invokes services provided by M5S to send MSGin5G messages to M5S on behalf of Legacy 3GPP UE or Non-3GPP UE. + +The M5S invokes services provided by SEAL Group management function to do MSGin5G Group management. + +The M5S/L3G/N3G invokes services provided by SEAL Configuration management function to do service configuration (including UE service ID provisioning). + +### 5.6.3 Service based interfaces + +Table 5.6.3-1 specifies the service based interfaces supported by MSGin5G Service. + +**Table 5.6.3-1: Service based interfaces supported by MSGin5G Service** + +| Service based interface | Application function entity | Mapping server entity | APIs offered | +|-------------------------|--------------------------------------|-----------------------------|--------------------| +| Mm5s | MSGin5G Server function | MSGin5G Server | Specified in 9.1 | +| Ml3g | Legacy 3GPP Message Gateway function | Legacy 3GPP Message Gateway | Specified in 9.2.1 | +| Mn3g | Non-3GPP Message Gateway function | Non-3GPP Message Gateway | Specified in 9.2.2 | +| Mbg | Broadcast Message Gateway function | Broadcast Message Gateway | Specified in 9.2.3 | + +# 6 Identities + +## 6.1 Identities for MSGin5G Service endpoints + +### 6.1.1 General + +MSGin5G Service endpoints shall be identified by unique identifiers within the MSGin5G Service domain. For each MSGin5G Service endpoint the identifier shall be a unique URI that can be used to identify the MSGin5G Service endpoint's home service domain. + +The following clauses describe different types of MSGin5G Service endpoint identifiers. + +### 6.1.2 UE Service Identity (UE Service ID) + +UE Service ID is the identifier of a UE (i.e. MSGin5G UE, Legacy 3GPP UE or Non-3GPP UE). + +For an MSGin5G UE, the assigned UE Service ID is used by the MSGin5G Client to register with the MSGin5G Server and to send and receive MSGin5G messages. It is used by the MSGin5G Server to authenticate and authorize the associated UE to the MSGin5G Service at the application layer. + +For a Legacy 3GPP UE or a Non-3GPP UE, the assigned UE Service ID is used by the Message Gateway to register with the MSGin5G Server on behalf of Legacy 3GPP UE or Non-3GPP UE, to map into the Service ID in their defined message delivery mechanisms for interworking, and to send/receive MSGin5G messages to/from MSGin5G Server on behalf of Legacy 3GPP UE or Non-3GPP UE. + +### 6.1.3 Application Server Service Identity (AS Service ID) + +AS Service ID is the identifier of an Application Server. It is used to perform mutual authentication with the MSGin5G Server for establishing a secured service connection, and it is used to send/receive message API request/response to/from other MSGin5G Service endpoints via MSGin5G Server. + +### 6.1.4 Message Gateway Service Identity (MGW Service ID) + +MGW Service ID is the identifier of Message Gateway. It is used to perform mutual authentication with the MSGin5G Server for establishing a secured service connection. + +## 6.2 MSGin5G Group Service Identity (Group Service ID) + +The Group Service ID is a unique identifier within the MSGin5G Service that represents a pre-defined MSGin5G Group. A pre-defined MSGin5G Group is established before the MSGin5G Group messages are sent to it, and is assigned a unique and permanent Group Service ID when it is established. This Group Service ID shall be communicated to all members of the group. A service endpoint (MSGin5G UE or Application Server) shall use this Group Service ID to send a message to all members of the group. + +The Group Service ID shall be a unique URI that can be used to identify where the group is hosted. + +## 6.3 Broadcast Area Service Identity (Broadcast Area ID) + +The Broadcast Area ID is the identity of the Service Area where the broadcast message is delivered. + +## 6.4 MSGin5G UE Identity (MSGin5G UE ID) + +The MSGin5G UE ID is a unique identifier that represents the MSGin5G UE (i.e. the device identifier of the MSGin5G UE). The MSGin5G UE ID may be pre-configured to the MSGin5G UE by its vendor. + +## 6.5 Non-MSGin5G UE identity (Non-MSGin5G UE ID) + +The Non-MSGin5G UE ID is a unique identifier that represents the Non-MSGin5G UE. A Non-MSGin5G UE ID is associated with a specific Non-MSGin5G UE. It is used by the Message Gateway in the MSGin5G Service to record the Non-MSGin5G UE. It is also used by the Message Gateway as a part of VAL UE ID when the Message Gateway executes the Non-MSGin5G UE configuration procedure on behalf of a Non-MSGin5G UE. The format of Non-MSGin5G UE ID may differ among different VALs. The non-MSGin5G ID may be pre-configured to the Non-MSGin5G UE by its vendor. + +## 6.6 Application Identity (Application ID) + +Application ID is an identifier that represents the application for which the payload of message is intended. The content of Application ID is outside the scope of this document. + +## 6.7 MSGin5G Server address + +MSGin5G Server address is the identifier of an MSGin5G Server within an MSGin5G service provider's domain. The MSGin5G Service endpoints in this MSGin5G service provider's domain can contact an MSGin5G Server by using the MSGin5G Server address of this MSGin5G Server. + +# --- 7 Generic description of the MSGin5G Service (informative) + +## 7.1 General + +Massive Internet of Things (MIoT) is one of key market segments of 5G. The typical IoT device communication is sending and receiving small data which can be delivered just in a message. The MSGin5G Service is designed and optimized for massive IoT device communication including thing-to-thing communication and person-to-thing communication. + +The MSGin5G Service is a message enabler for applications. An Application Client in a UE utilizes MSGin5G Service to send a message to another UE, to multiple UEs or to the Application Server, or the Application Server utilizes the MSGin5G Service to send a message to a UE or to multiple UEs. All messages will be routed via the MSGin5G Server in the 5G system. The MSGin5G Service flow is shown in figure 7.1-1. + +If the UE supports a legacy 3GPP message service (e.g. SMS, NIDD, or CB) and does not support the MSGin5G Service (i.e. UE has no MSGin5G Client), the message will be translated to the appropriate message delivery mechanism by the Legacy 3GPP Message Gateway. A UE that does not support any 3GPP message service can connect to the MSGin5G Service via Non-3GPP Message Gateway that facilitates the translation between the MSGin5G Service and non-3GPP message delivery mechanism. The connection between such UE and the gateway can be via 3GPP access or non 3GPP access (e.g. WLAN) and is out of scope of the present specification. + +An Application Server resides outside the 3GPP domain and connects to the MSGin5G Server via a CAPIF-aware reference point. + +The message communication models include: + +- Point-to-Point messaging: message that is originated at a UE (UE A) and terminated at another UE (UE B, a Legacy 3GPP UE or a Non-3GPP UE). +- AS-to-Point messaging: message that is originated at an Application Server and terminated at a UE. +- Point-to-AS messaging: message that is originated at a UE and terminated at an Application Server. +- Group Messaging: message that is originated at a UE or an Application Server and is terminated at a group of UEs (a group member can be of type UE A, Legacy 3GPP UE or Non-3GPP UE). +- Broadcast Messaging: message that is originated at an Application Server or an MSGin5G UE and broadcasted to all the UEs in a specific Broadcast Area within coverage of a cell or of multiple cells. An existing broadcast function (e.g. CB specified in 3GPP TS 23.041 [14]) may be reused in broadcast messaging of MSGin5G Service. +- Topic Messaging: message that is originated at an Application Server or a UE and is delivered to all UEs and Application Server(s) that have subscribed to the topic. + +![Figure 7.1-1: The MSGin5G Service overview diagram. The diagram shows two Application Servers (Application Server 1 and Application Server 2) connected to an MSGin5G Server. The MSGin5G Server is connected to a 5G Core / Access Network. Below the network, there are three message gateways: Broadcast Message Gateway, Legacy 3GPP Message Gateway, and Non-3GPP Message Gateway. These gateways are connected to four types of User Equipment (UE): MSGin5G UE A, MSGin5G UE B, Legacy 3GPP UE, and Non-3GPP UE. MSGin5G UE A and B contain MSGin5G Clients and Application Clients. Legacy 3GPP UE and Non-3GPP UE contain Legacy 3GPP and Non-3GPP Message Clients, respectively, along with Application Clients or person.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Figure 7.1-1: The MSGin5G Service overview diagram. The diagram shows two Application Servers (Application Server 1 and Application Server 2) connected to an MSGin5G Server. The MSGin5G Server is connected to a 5G Core / Access Network. Below the network, there are three message gateways: Broadcast Message Gateway, Legacy 3GPP Message Gateway, and Non-3GPP Message Gateway. These gateways are connected to four types of User Equipment (UE): MSGin5G UE A, MSGin5G UE B, Legacy 3GPP UE, and Non-3GPP UE. MSGin5G UE A and B contain MSGin5G Clients and Application Clients. Legacy 3GPP UE and Non-3GPP UE contain Legacy 3GPP and Non-3GPP Message Clients, respectively, along with Application Clients or person. + +Figure 7.1-1: The MSGin5G Service overview + +## 7.2 Service flow + +Before a UE or an Application Server can use the MSGin5G Service it needs to register with the MSGin5G Server. + +A UE registers with its identity, its security credentials, the capabilities that it supports, and its availability. The MSGin5G Server will use the availability registration and de-registration to determine if the UE is available for message delivery. If a UE is unavailable for message delivery, the MSGin5G Server will store the message and deliver it once the UE becomes available again. + +When a UE or an Application Server sends an MSGin5G message to a recipient UE then such message will be sent to the MSGin5G Server and this server will deliver the message to the UE based on the capabilities of the recipient UE (MSGin5G UE, Legacy 3GPP UE or Non-3GPP UE). If the recipient UE is a Legacy 3GPP UE then the MSGin5G Server will forward the message to the Legacy 3GPP Message Gateway and this gateway will convert the message to a message that is supported by the recipient UE (e.g. SMS, NIDD or CB). If the recipient UE is a Non-3GPP UE then the + +MSGin5G Server will forward the message to the Non-3GPP Message Gateway and this gateway will convert the message to a message that is supported by the recipient UE. + +A Legacy 3GPP UE sends the application payload to the Legacy 3GPP Message Gateway and this gateway will forward the application payload in an MSGin5G message to the MSGin5G Server, which will deliver the message to the recipient UE(s). A Non-3GPP UE sends the application payload to the Non-3GPP Message Gateway and this gateway will forward the application payload in an MSGin5G message to the MSGin5G Server, which will deliver the message to the recipient UE(s). + +NOTE: Conversion by a Message Gateway is out of scope of the present specification. + +If a UE or an Application Server sends an MSGin5G message to a group of UEs, the MSGin5G Server will deliver the message to all group members taking into account if such a UE is an MSGin5G UE, a Legacy 3GPP UE or a Non-MSGin5G UE and if such UE is available for delivery. + +If a UE or an Application Server sends an MSGin5G message containing a Messaging Topic to the MSGin5G Server, the MSGin5G Server will distribute the message to all UEs and Application Servers that have subscribed to that topic. + +If a UE or an Application Server sends a broadcast message to a Broadcast Area, the MSGin5G Server forwards the message to the Broadcast Message Gateway and this gateway will forward the message to the broadcast function. + +An originating UE or Application Server may request the recipient UE(s) to acknowledge reception of the message. If such a request is made, a message delivery status report shall be sent by the recipient MSGin5G UE or the Message Gateway (on behalf of the Non-MSGin5G UE) as a point-to-point message back to the originating UE or Application Server. The acknowledgement information is included in the payload and the format of this information is out of scope of the present specification. + +The Non-MSGin5G UE may respond to an incoming MSGin5G message; it is subject to the Message Gateway implementation to maintain the transaction of the incoming MSGin5G message and reply to it to the sender, with the response it receives from the Non-MSGin5G UE. + +## 7.3 Message delivery flow at MSGin5G Server + +Figure 7.3-1 shows the flow for message delivery by the MSGin5G Server. + +![Flowchart of message delivery flow at MSGin5G Server. The process starts with 'Message is available for delivery'. It checks 'UE registered?'. If 'no', it checks 'Device triggering supported?'. If 'yes', it 'Wake up the device for service' and loops back to 'UE registered?'. If 'no', it checks 'S/F requested?'. If 'yes', it 'Queue the message'. If 'no', it 'Drop the message OR local implementation and send report'. If 'UE registered?' is 'yes', it checks 'Client communication info available?'. If 'no', it 'Deliver the message'. If 'yes', it checks 'Delivery window?'. If 'no', it loops back to 'Client communication info available?'. If 'yes', it 'Deliver the message'. A note indicates that if delivery fails, a re-try will take place, and the number of failed re-tries before stopping is local implementation. Another note states that the MSGin5G Server may use network capabilities like device triggering or UE reachability status monitoring to check reachability, and this usage is implementation specific.](6929132b4964d52244da61d4614bc4d6_img.jpg) + +``` + +graph TD + Start([Message is available for delivery]) --> UE_Reg{UE registered?} + UE_Reg -- no --> Device_Trigger{Device triggering supported?} + Device_Trigger -- yes --> Wake_Up((Wake up the device for service)) + Wake_Up --> UE_Reg + Device_Trigger -- no --> S_F_Req{S/F requested?} + S_F_Req -- yes --> Queue[Queue the message] + S_F_Req -- no --> Drop[Drop the message OR local implementation and send report] + UE_Reg -- yes --> Client_Info{Client communication info available?} + Client_Info -- no --> Deliver((Deliver the message)) + Client_Info -- yes --> Delivery_Window{Delivery window?} + Delivery_Window -- no --> Client_Info + Delivery_Window -- yes --> Deliver + Deliver -- Failed --> A1((A)) + Queue --> A2((A)) + Deliver --> Note1[When message delivery failed, a re-try will take place. How many failed re-tries before stops delivery attempt is local implementation.] + Note2[* In this procedure, the MSGin5G Server may use the network capabilities, e.g. device triggering or UE reachability status monitoring, to check the reachability of the recipient. The usage of network capabilities in this procedure is implementation specific.] + +``` + +Flowchart of message delivery flow at MSGin5G Server. The process starts with 'Message is available for delivery'. It checks 'UE registered?'. If 'no', it checks 'Device triggering supported?'. If 'yes', it 'Wake up the device for service' and loops back to 'UE registered?'. If 'no', it checks 'S/F requested?'. If 'yes', it 'Queue the message'. If 'no', it 'Drop the message OR local implementation and send report'. If 'UE registered?' is 'yes', it checks 'Client communication info available?'. If 'no', it 'Deliver the message'. If 'yes', it checks 'Delivery window?'. If 'no', it loops back to 'Client communication info available?'. If 'yes', it 'Deliver the message'. A note indicates that if delivery fails, a re-try will take place, and the number of failed re-tries before stopping is local implementation. Another note states that the MSGin5G Server may use network capabilities like device triggering or UE reachability status monitoring to check reachability, and this usage is implementation specific. + +Figure 7.3-1: The message delivery flow at the MSGin5G Server + +# 8 Procedures and information flows + +## 8.1 Configuration + +### 8.1.1 General + +The configuration procedure is used to get the MSGin5G Service configuration information (e.g. UE Service ID). The configuration procedure is used by the MSGin5G UE or used by Message Gateway on behalf of the Non-MSGin5G UE. The MSGin5G Service configuration information is used in the future messaging communication. + +The VAL UE configuration data specified in TS 23.434 [5] is used in this configuration procedure. After the configuration procedure, the MSGin5G UE, or the Message Gateway on behalf of the Non-MSGin5G UE can register to MSGin5G Server. + +NOTE 1: The configuration on the Message Gateway to support the Non-MSGin5G UE for MSGin5G Service can also be done without using the SEAL configuration procedures and is implementation specific. + +NOTE 2: The MSGin5G Service configuration information can also be pre-configured to the MSGin5G UE/Non-MSGin5G UE and is implementation specific. + +### 8.1.2 MSGin5G UE Configuration + +In the MSGin5G UE configuration procedure, the MSGin5G UE acts as Configuration management client specified in 3GPP TS 23.434 [5]. + +The following steps of configuration management service apply for the MSGin5G UE: + +- Send the Get VAL UE configuration request specified in clause 11.3.2.1 of 3GPP TS 23.434 [5]; +- Receive the related Get VAL UE configuration response specified in clause 11.3.2.2 of 3GPP TS 23.434 [5]; + +The usage of the above information flows is clarified as below: + +- The MSGin5G UE ID works as VAL UE ID which is mandatory in the Get VAL UE configuration request; +- The UE Service ID works as VAL user ID; +- The service identifier of MSGin5G Service works as VAL service ID; + +Besides the IEs specified in clause 11.3.2.1 of 3GPP TS 23.434 [5], the information in table 8.1.2-1 is also included in the Get VAL UE configuration request. + +**Table 8.1.2-1: Additional Information in the Get VAL UE configuration request** + +| Information element | Status | Description | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| MSGin5G UE information | O | Other information needed by the configuration procedure. (see NOTE) | +| NOTE: | The information can be the device type, device vendor, etc. It is specified by application provider or MSGin5G Service provider and is out of scope of this document. The MSGin5G Service provider can configure the MSGin5G UE with different configuration data based on this IE. E.g. all sensors can be configured to a same MSGin5G Server. | | + +The information in table 8.1.2-2 is included in the Get VAL UE configuration response as a part of VAL UE configuration data. + +**Table 8.1.2-2: Information in the Get VAL UE configuration response** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------| +| UE Service ID | M | UE Service ID assigned to the requesting MSGin5G UE. | +| MSGin5G Server address | M | The MSGin5G Server which serves this MSGin5G UE. | +| MSGin5G Service specific information | O | The specific information of the MSGin5G Service specified by the MSGin5G Service provider. (see NOTE) | +| NOTE: E.g. the segment size of MSGin5G message in this service provider. The detailed definition is out of scope of this document. | | | + +Besides the functionalities of Configuration Management Server specified in 3GPP TS 23.434 [5], the MSGin5G Configuration Function should also check whether the MSGin5G UE ID (i.e. VAL UE ID) is included in a former Get VAL UE configuration request. + +- If so, the MSGin5G Configuration Function included the UE Service ID assigned to the MSGin5G UE in the former configuration procedure as a part of VAL UE configuration data, +- Otherwise, a new UE Service ID is assigned to the MSGin5G UE and included in the VAL UE configuration data. + +Then the MSGin5G Configuration Function processes the configuration request according to the service policy. + +### 8.1.3 Message Gateway Configuration for support of Non-MSGin5G UE + +The Message Gateway performs the configuration procedure on behalf of the Non-MSGin5G UE to get the MSGin5G Service configuration information (e.g. UE Service ID). + +NOTE 1: As an alternative to the configuration procedure all the necessary service information (including the UE Service ID) of a Non-MSGin5G UE can be pre-configured with the Message Gateway. + +If Configuration Management service in SEAL is used for the Message Gateway configuration, the Message Gateway acts as Configuration management client specified in 3GPP TS 23.434 [5] on behalf of each Non- MSGin5G UE. + +The following steps of configuration management service may apply for the Message Gateway: + +- Send the Get VAL UE configuration request specified in clause 11.3.2.1 of 3GPP TS 23.434 [5]; +- Receive the related Get VAL UE configuration response specified in clause 11.3.2.2 of 3GPP TS 23.434 [5]; + +The usage of the above information flows is clarified as below: + +- An Information Element contains both Non-MSGin5G UE ID and MGW Service ID works as VAL UE ID which is mandatory in the Get VAL UE configuration request; + +NOTE 2: The Non-MSGin5G UE ID may differ among different VALs and may not be unique among different Gateways. It is not enough to use only Non-MSGin5G UE ID as VAL UE ID. + +- The UE Service ID works as VAL user ID; +- The service identifier of MSGin5G Service works as VAL service ID; + +Besides the IEs specified in clause 11.3.2.1 of 3GPP TS 23.434 [5], the information in table 8.1.3-1 is also included in the Get VAL UE configuration request. + +**Table 8.1.3-1: Additional Information in the Get VAL UE configuration request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------| +| Non-MSGin5G UE information | O | Other information needed by the configuration procedure. (see NOTE) | +| NOTE: The information can be the device type, device Vendor, etc. It is specified by application provider or MSGin5G Service provider and is out of scope of this document. The MSGin5G Service provider can configure the Non-MSGin5G UE with different configuration data based on this IE. E.g. all sensors can be configured to a same MSGin5G Server. | | | + +The information in table 8.1.3-2 is included in the Get VAL UE configuration response as a part of VAL UE configuration data. The information is used by Message Gateway to support non-MSGin5G UEs that will be used to register with the MSGin5G Server for MSGin5G service. + +**Table 8.1.3-2: Information in the Get VAL UE configuration response** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------| +| UE Service ID | M | UE service ID assigned to the requesting Non-MSGin5G UE. | +| MSGin5G Server address | M | The MSGin5G Server which serves this MSGin5G UE. | +| MSGin5G Service specific information | O | The specific information of the MSGin5G Service specified by the MSGin5G Service provider. (see NOTE) | +| NOTE: The information (except UE Service IE) used by Message Gateway to support non-MSGin5G UEs that will be used to register with the MSGin5G Server for MSGin5G service is included in this IE. The detailed information is specified in Table 8.2.1-1. Other service specific information can also be included in this IE, the detailed definition of the other service specific information is out of scope of this document. | | | + +Besides the functionalities of Configuration Management Server specified in 3GPP TS 23.434 [5], the MSGin5G Configuration Function should also check whether the MSGin5G UE ID (i.e. VAL UE ID) is included in a former Get VAL UE configuration request. + +- If so, the MSGin5G Configuration Function included the UE Service ID assigned to the Non-MSGin5G UE in the former configuration procedure as a part of VAL UE configuration data. +- Otherwise, a new UE Service ID is assigned to the Non-MSGin5G UE and included in the VAL UE configuration data. + +Then the MSGin5G Configuration Function processes the configuration request according to the service policy. + +### 8.1.4 MSGin5G UE bulk configuration over MSGin5G-6 reference point + +When more than one MSGin5G UEs, which are constrained devices, which support an MSGin5G Client, get the MSGin5G Service configuration information via the MSGin5G Gateway UE, the MSGin5G Gateway UE may decide to use bulk configuration procedure specified in this clause based on service policy. + +Pre-conditions: + +1. The constrained MSGin5G UE has discovered and selected an MSGin5G Gateway UE as specified in clause 8.2.8 and connected to the serving network via the MSGin5G Gateway UE successfully. +2. The MSGin5G Gateway UE has been configured by using the procedure specified in clause 8.1.2 of the present document. + +The constrained MSGin5G UE sends the Get VAL UE configuration request as specified in clause 8.1.2 of the present document to MSGin5G Gateway UE. If the MSGin5G Gateway UE decides to use bulk configuration based on the service policy, the MSGin5G Gateway UE sends a Get VAL UE configuration response including the information elements as listed in table 8.1.4-1 as a part of VAL UE configuration data to the constrained MSGin5G UEs before bulk configuration is performed. This Get VAL UE configuration response is used to inform each constrained MSGin5G UE that their Get VAL UE configuration requests will be handled later. + +NOTE: How to decide that bulk configuration is used is implementation specific and out of scope. + +**Table 8.1.4-1: Information in the Get VAL UE configuration response to constrained device before bulk configuration is performed** + +| Information element | Status | Description | +|----------------------------|--------|--------------------------------------------------------------------------------------------| +| Maximum configuration time | M | The maximum wait time for the bulk configuration request to be sent to the MSGin5G Server. | + +In the MSGin5G UE bulk configuration procedure, the MSGin5G Gateway UE acts as Configuration management client specified in clause 8.1.2 of the present document. In addition to the information elements listed in table 8.1.2-1 of the present document and clause 11.3.2.1 of 3GPP TS 23.434 [5], the Get VAL UE configuration request used for bulk configuration also includes the information elements as listed in table 8.1.4-2. + +**Table 8.1.4-2: additional Information in the Get VAL UE configuration request** + +| Information element | Status | Description | +|-------------------------|--------|---------------------------------------------------------------------------------------------------------------| +| Bulk configuration flag | M | Indicates this request is an enhanced Get VAL UE configuration request used for MSGin5G UE bulk configuration | +| List of MSGin5G UE IDs | M | List of MSGin5G UE ID of MSGin5G UEs which needed to be configured in this bulk configuration request | + +In addition to the information elements listed in table 8.1.2-2 of the present document, the Get VAL UE configuration response used for bulk configuration also includes the information elements as listed in table 8.1.4-3 as a part of VAL UE configuration data as specified in clause 11.3.2.2 of 3GPP TS 23.434 [5]. + +**Table 8.1.4-3: additional Information in the Get VAL UE configuration response** + +| Information element | Status | Description | +|----------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| List of MSGin5G UE configuration information | M | Each element in this list contains information as specified in Table 8.1.2-2. The configuration information included in this IE is used to complete the configuration of the constrained MSGin5G UEs. | + +**Editor's note:** The enhancement of VAL UE configuration request and response are needed to be captured by eSEAL2 WID and are FFS. + +Upon receiving the Get VAL UE configuration response used for bulk configuration, the MSGin5G Gateway UE includes the MSGin5G UE configuration information in the List of MSGin5G UE configuration information into multiple individual Get VAL UE configuration responses and sends them to the corresponding constrained MSGin5G UEs. + +## 8.2 Registration + +### 8.2.0 General + +Before a UE or an Application Server can use the MSGin5G Service it needs to register with the MSGin5G Server. + +The procedures of MSGin5G UE registration/de-registration are specified in clause 8.2.1 and clause 8.8.2. The procedures also apply when the MSGin5G UE uses MSGin5G services by using another UE as relay. + +The procedures of Non-MSGin5G UE registration/de-registration are specified in clause 8.2.3 and clause 8.8.4. + +The procedures of Application Server registration/de-registration are specified in clause 8.2.5 and clause 8.8.6. + +The MSGin5G Gateway UE may use bulk registration to register more than one of MSGin5G UEs at one time if allowed by the service policy. The bulk registration procedure is specified in clause 8.2.7. Before using bulk registration, the MSGin5G UE should select a MSGin5G Gateway as specified in clause 8.2.8. If a MSGin5G Gateway + +UE is selected by an MSGin5G UE, the MSGin5G UE should use bulk registration over MSGin5G-6 reference point specified in clause 8.2.7 instead of the MSGin5G UE registration procedure specified in clause 8.2.1. The corresponding procedure of MSGin5G UE bulk de-registration over MSGin5G-6 reference point is specified in clause 8.2.11. + +The Message Gateway may also use bulk registration/de-registration to register more than one of Non-MSGin5G UE at one time with the MSGin5G Server. The procedures of Non-MSGin5G UE bulk registration and Non-MSGin5G UE bulk de-registration are specified in clause 8.2.9 and clause 8.2.10 respectively. + +### 8.2.1 MSGin5G UE Registration + +The signalling flow for MSGin5G UE registration is illustrated in figure 8.2.1-1. The procedure assumes that the MSGin5G UE is responsible for initiating registration to the MSGin5G Server in order to establish association with the MSGin5G Server to receive MSGin5G Services. + +Pre-conditions: + +1. The MSGin5G UE has connected to the serving network successfully. +2. The MSGin5G UE has successfully completed the Configuration procedure; alternatively, a UE Service ID and the MSGin5G Server address have been pre-configured on the MSGin5G UE. +3. Both the MSGin5G UE and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another. + +![Sequence diagram of MSGin5G Client registration](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +``` +sequenceDiagram + participant MSGin5G UE + participant MSGin5G Server + Note right of MSGin5G UE: MSGin5G Client + MSGin5G UE->>MSGin5G Server: 1. MSGin5G UE registration request + Note over MSGin5G UE, MSGin5G Server: 2. Authentication and authorization procedures + MSGin5G Server-->>MSGin5G UE: 3. MSGin5G UE registration response +``` + +The diagram illustrates the MSGin5G Client registration process. It features two main entities: the MSGin5G UE (which contains an internal MSGin5G Client) and the MSGin5G Server. The sequence of interactions is as follows: 1. The MSGin5G UE sends a 'MSGin5G UE registration request' to the MSGin5G Server. 2. Both entities engage in 'Authentication and authorization procedures', represented by a shared activation bar. 3. The MSGin5G Server returns a 'MSGin5G UE registration response' to the MSGin5G UE. + +Sequence diagram of MSGin5G Client registration + +**Figure 8.2.1-1: MSGin5G Client registration** + +1. The MSGin5G UE sends an MSGin5G UE registration request to the MSGin5G Server. The request includes the UE Service ID and may include the MSGin5G Client Profile and Requested expiration time as detailed in Table 8.2.1-1. + +Table 8.2.1-1: MSGin5G UE registration request + +| Information element | Status | Description | +|---------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE Service ID | M | UE service identifier assigned to the requesting MSGin5G UE. | +| MSGin5G Client Profile | O | Set of parameters describing the MSGin5G Client | +| >MSGin5G Client Triggering Information | O | UE Identifier (i.e., MSISDN, external ID), port number(s) and associated protocol (e.g., SMS, NIDD, etc.) for device triggering. See Table 8.2.1-2. The MSGin5G Server uses the information in step 5 of clause 8.9.3.2. | +| >MSGin5G Client Communication Availability | O | Communication availability information for the MSGin5G Client to receive MSGin5G messages. This IE informs the MSGin5G Server if the client has a specific application-level schedule/periodicity to its MSGin5G communications. See Table 8.2.1-3. | +| > MSGin5G Client Supported Maximum MSGin5G segment size | O | The Maximum MSGin5G segment size can be used by the MSGin5G Server to deliver message to the client served by it in its MSGin5G service domain. The MSGin5G message sent to the MSGin5G Client should be segmented by the MSGin5G Server serves the receiver if the message size is bigger than the MSGin5G Client Supported Maximum MSGin5G segment size as specified in clause 8.5. The value of this IE is decided by the MSGin5G Client, and is depended on the MSGin5G Client capabilities, e.g. supported transport, computing capability or application processing time limitation. If this IE is not included, the MSGin5G Server shall use the pre-configured global value within the MSGin5G service domain. | +| Requested expiration time | O | Requested expiration time for the registration. | + +Table 8.2.1-2: MSGin5G Client Triggering Information + +| Information element | Status | Description | +|----------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MSGin5G UE ID | M | Identity of the UE hosting the MSGin5G Client (e.g., the External Identifier defined in TS 23.682 [8], or an MSISDN) | +| MSGin5G Client Ports | M | List of port numbers that the MSGin5G Client listens on for device triggers from the MSGin5G Server. Also included with each port number is an associated protocol (e.g., SMS, NIDD, etc.). | + +Table 8.2.1-3: MSGin5G Client Communication Availability + +| Information element | Status | Description | +|----------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Scheduled communication time | M | Time when the UE becomes available for communication. | +| Communication duration time | M | Duration time of periodic communication. | +| Periodic communication indicator | O | Identifies whether the client communicates periodically or not, e.g., on demand. | +| Periodic communication interval | O | Interval Time of periodic communication. This IE is mandatory if the Periodic communication indicator indicates periodic communications. | +| Data size indication | O | Indicates the expected data size to be exchanged during the communication duration. | +| Store and forward option | O | Indicates opting out of store and forward services for incoming MSGin5G requests. The MSGin5G Server uses the information to determine whether Store and Forward procedure applies as specified in clause 8.3.6. | + +2. Upon receiving the request, the MSGin5G Server initiates authentication procedures with the MSGin5G Client and authorizes the MSGin5G Client. If the registration is successful, the MSGin5G Server stores the UE Service ID and associated MSGin5G Client Profile. The UE Service ID and associated MSGin5G Client Profile should be maintained on the MSGin5G Server until one of the following cases applies: + +- a) the MSGin5G UE de-registers from the MSGin5G Server as specified in clause 8.2.2; +- b) the MSGin5G UE re-registered successfully with a different MSGin5G Client Profile; In this case, the MSGin5G Server shall store the UE Service ID and associated new MSGin5G Client Profile; +- c) the MSGin5G UE registration is expired; or +- d) the MSGin5G Server deletes the MSGin5G UE registration as required by the service provider. + +NOTE: The authentication procedures in step 2 are built on top of the transport layer mechanism specified in Annex Y.2 of 3GPP TS 33.501 [16]. + +3. The MSGin5G Server sends an MSGin5G UE registration response to the MSGin5G UE. The response includes the information elements as detailed in Table 8.2.1-4. The registration expiration time may be returned either as provided by the MSGin5G client in the registration request or determined by the MSGin5G Server based on local policy. + +**Table 8.2.1-4: MSGin5G UE registration response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------|--------|------------------------------------------------------| +| UE Service ID | M | UE service identifier of the requesting MSGin5G UE. | +| Registration result | M | Indication if the registration is success or failure | +| Registration expiration time (see NOTE 1) | O | Indicates the expiration time of the registration. | +| Failure Cause (see NOTE 2) | O | The reason for failure | +| NOTE 1: This IE shall only be present when the Registration is Success. | | | +| NOTE 2: This IE shall only be present when the Registration result is Failure. | | | + +### 8.2.2 MSGin5G UE De-Registration + +By de-registering, the MSGin5G UE informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server. + +NOTE 1: De-registration implies that Client Triggering Information and the Client Communication Availability Information are no longer valid. + +The procedure assumes that the MSGin5G UE is responsible for initiating the de-registration from the MSGin5G Server. The signalling flow for MSGin5G UE de-registration is illustrated in figure 8.2.2-1. + +Pre-condition: + +1. The MSGin5G UE is registered to the MSGin5G Server. + +![Sequence diagram for MSGin5G UE de-registration. The diagram shows a MSGin5G UE (containing a MSGin5G Client) and a MSGin5G Server. The process consists of four steps: 1. Determine de-registration is required (internal to UE), 2. MSGin5G UE de-registration request (UE to Server), 3. Authentication and authorization procedures (Server side, indicated by a dashed box), and 4. MSGin5G UE de-registration response (Server to UE).](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) + +``` + +sequenceDiagram + participant UE as MSGin5G UE (MSGin5G Client) + participant Server as MSGin5G Server + Note left of UE: 1. Determine de-registration is required + UE->>Server: 2. MSGin5G UE de-registration request + Note right of Server: 3. Authentication and authorization procedures + Server-->>UE: 4. MSGin5G UE de-registration response + +``` + +Sequence diagram for MSGin5G UE de-registration. The diagram shows a MSGin5G UE (containing a MSGin5G Client) and a MSGin5G Server. The process consists of four steps: 1. Determine de-registration is required (internal to UE), 2. MSGin5G UE de-registration request (UE to Server), 3. Authentication and authorization procedures (Server side, indicated by a dashed box), and 4. MSGin5G UE de-registration response (Server to UE). + +**Figure 8.2.2-1: MSGin5G UE de-registration** + +1. The MSGin5G UE determines to de-register from the MSGin5G Server. +2. The MSGin5G UE sends an MSGin5G UE de-registration request to the MSGin5G Server that includes the UE Service ID, as detailed in Table 8.2.2-1. + +**Table 8.2.2-1: MSGin5G UE de-registration request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| UE Service ID | M | UE service identifier assigned to the MSGin5G UE. | + +3. The MSGin5G Server may initiate authentication procedures with the MSGin5G Client and authorizes the MSGin5G Client. If the MSGin5G Server has authorized the MSGin5G Client successfully it deletes any UE Service ID and associated MSGin5G Client Profile that it has stored. + +NOTE 2: The authentication procedures in step 3 are built on top of the transport layer mechanism specified in Annex Y.2 of 3GPP TS 33.501 [16]. + +4. The MSGin5G Server sends an MSGin5G UE de-registration response as detailed in Table 8.2.2-2 to the MSGin5G UE. + +**Table 8.2.2-2: MSGin5G UE de-registration response** + +| Information element | Status | Description | +|------------------------|--------|---------------------------------------------------------| +| UE Service ID | M | UE service identifier of the MSGin5G UE. | +| De-registration result | M | Indication if the de-registration is success or failure | +| Failure Cause | O | The reason for failure | + +### 8.2.3 Non-MSGin5G UE Registration + +Non-MSGin5G UEs (i.e., Legacy 3GPP UEs or Non-3GPP UEs) are connected to the MSGin5G Server through a Message Gateway. The Message Gateway performs registration with the MSGin5G Server on behalf of the Non MSGin5G UEs, based on pre-provisioned information when it receives a registration request from the Non MSGin5G UE, or gets the knowledge that the Non-MSGin5G UE is ready for the MSGin5G service. After the procedure is completed, the Message Gateway may communicate the result to the Non-MSGin5G UE to enable MSGin5G Services at the Non MSGin5G UE. + +NOTE: The communication procedure between Non-MSGin5G UE and Message Gateway is out of scope of this document. + +The signalling flow is illustrated in figure 8.2.3-1. + +Pre-conditions: + +1. The Message Gateway has been pre-configured with the MSGin5G Server address. +2. The Message Gateway has been configured with the necessary information as specified in clause 8.1.3. If the UE Service ID and Non-MSGin5G UE credentials have been configured and the Non-MSGin5G UE Profile is available, this pre-condition enables authentication and Non- MSGin5G UE registration at the Message Server. +3. A secured connection has been established between the Message Gateway and the MSGin5G Server. + +![Sequence diagram showing Non-MSGin5G UE registration. The Message Gateway sends a '1. Non-MSGin5G UE registration request' to the MSGin5G Server. The MSGin5G Server then performs '2. Authentication and authorization procedures'. Finally, the MSGin5G Server sends a '3. Non-MSGin5G UE registration response' back to the Message Gateway.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +``` + +sequenceDiagram + participant MG as Message Gateway + participant MS as MSGin5G Server + Note right of MG: 1. Non-MSGin5G UE registration request + MG->>MS: Request + Note right of MS: 2. Authentication and authorization procedures + Note right of MS: 3. Non-MSGin5G UE registration response + MS-->>MG: Response + +``` + +Sequence diagram showing Non-MSGin5G UE registration. The Message Gateway sends a '1. Non-MSGin5G UE registration request' to the MSGin5G Server. The MSGin5G Server then performs '2. Authentication and authorization procedures'. Finally, the MSGin5G Server sends a '3. Non-MSGin5G UE registration response' back to the Message Gateway. + +Figure 8.2.3-1: Non-MSGin5G UE registration + +1. The Message Gateway sends the Non-MSGin5G UE registration request to the MSGin5G Server. The request includes the information pre-configured to the Message Gateway or provided by the Non-MSGin5G UE (e.g. in non-MSGin5G registration or bootstrapping procedures which are out of scope of the present specification) and detailed in Table 8.2.3-1. + +Table 8.2.3-1: Non-MSGin5G UE registration request + +| Information element | Status | Description | +|--------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE Service ID | M | UE service identifier assigned to the requesting Non-MSGin5G UE. | +| MGW Service ID | M | The service identifier of the Message Gateway performing registration on behalf of a Non-MSGin5G UE | +| Non-MSGin5G UE Profile | O | Set of parameters describing the Non-MSGin5G UE | +| >Non-MSGin5G UE Communication Availability | O | Communication availability information for the Non-MSGin5G UE to receive messages. This IE informs the MSGin5G Server if the Non-MSGin5G UE has a specific application-level schedule/periodicity to its MSGin5G communications, which may be used to determine whether and when MSGin5G communications are attempted. See Table 8.2.1-3. | + +2. Upon receiving the request, the MSGin5G Server initiates authentication procedures with the Message Gateway on behalf of the Non-MSGin5G Client and authorises the Non-MSGin5G UE to receive the MSGin5G Service. If the registration is successful, the MSGin5G Server stores the UE Service ID and associated Non-MSGin5G UE Profile. The UE Service ID and associated Non-MSGin5G UE Profile should be maintained on the MSGin5G Server until one of the following cases applies: + - a) the Non-MSGin5G UE de-registers from the MSGin5G Server as specified in clause 8.2.4; + +- b) the Non-MSGin5G UE re-registered successfully with a different Non-MSGin5G UE Profile; In this case, the MSGin5G Server shall store the UE Service ID and associated new Non-MSGin5G UE Profile; +- c) the Non-MSGin5G UE registration is expired; or +- d) the MSGin5G Server deletes the Non-MSGin5G UE registration as required by the service provider. + +NOTE: The authentication procedures in step 2 are built on top of the transport layer mechanism specified in Annex Y.2 of 3GPP TS 33.501 [16]. + +- 3. The MSGin5G Server returns the result of the registration in the Non-MSGin5G UE registration response message with the information detailed in table 8.2.1-4, to the Message Gateway. + +### 8.2.4 Non-MSGin5G UE De-registration + +The Message Gateway performs de-registration with the MSGin5G Server on behalf of the Non-MSGin5G UEs, in order to terminate services from the MSGin5G Server. + +NOTE: After the procedure is completed, the Message Gateway may communicate the result to the requesting Non-MSGin5G UE and the procedure is out of scope of this document. + +The procedure assumes that the Message Gateway is responsible for initiating the de-registration from the MSGin5G Server on behalf of the Non-MSGin5G UE. The signaling flow for Non-MSGin5G UE de-registration is illustrated in figure 8.2.4-1. + +Pre-condition: + +- 1. The Message Gateway successfully performed registration with the MSGin5G Server on behalf of the Non-MSGin5G UE. + +![Sequence diagram showing the Non-MSGin5G UE de-registration process between a Message Gateway and an MSGin5G Server. The steps are: 1. Message Gateway determines to de-register the UE; 2. Message Gateway sends a de-registration request to the server; 3. Server performs authentication and authorization; 4. Server sends a de-registration response back to the gateway.](e38206fcefa2045af01d494b2956775a_img.jpg) + +``` + +sequenceDiagram + participant MG as Message Gateway + participant MS as MSGin5G Server + Note left of MG: 1. determines to de-register the Non-MSGin5G UE + MG->>MS: 2. Non-MSGin5G UE de-registration request + Note right of MS: 3. Authentication and authorization procedures + MS->>MG: 4. Non-MSGin5G UE de-registration response + +``` + +Sequence diagram showing the Non-MSGin5G UE de-registration process between a Message Gateway and an MSGin5G Server. The steps are: 1. Message Gateway determines to de-register the UE; 2. Message Gateway sends a de-registration request to the server; 3. Server performs authentication and authorization; 4. Server sends a de-registration response back to the gateway. + +**Figure 8.2.4-1: Non-MSGin5G UE de-registration** + +- 1. The Message Gateway determines to de-register the Non-MSGin5G UE with the MSGin5G Server. +- 2. The Message Gateway sends a Non-MSGin5G UE de-registration request to the MSGin5G Server that includes the UE Service ID associated with the Non-MSGin5G UE, as shown in Table 8.2.4-1. + +**Table 8.2.4-1: Non-MSGin5G UE de-registration request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| UE Service ID | M | UE service identifier assigned to the Non-MSGin5G UE. | + +- Upon receiving the request, the MSGin5G Server may initiate authentication procedures with the Message Gateway on behalf of the Non-MSGin5G Client and authorizes the Message Gateway. If the MSGin5G Server has authorized the Message Gateway successfully, it deletes any UE Service ID and associated Non-MSGin5G UE Profile that it has stored. + +NOTE: The authentication procedures in step 3 are built on top of the transport layer mechanism specified in Annex Y.2 of 3GPP TS 33.501 [16]. + +- The MSGin5G Server replies with a Non-MSGin5G UE de-registration response as shown in table 8.2.4-2. + +**Table 8.2.4-2: Non-MSGin5G UE De-registration response** + +| Information element | Status | Description | +|------------------------|--------|---------------------------------------------------------| +| UE Service ID | M | UE service identifier of the Non-MSGin5G UE. | +| De-registration result | M | Indication if the de-registration is success or failure | +| Failure Cause | O | The reason for failure | + +### 8.2.5 Application Server Registration + +The signalling flow for Application Server registration is illustrated in figure 8.2.5-1. Application Server may use the procedure in this clause to do registration. + +NOTE: If the Application Server does not use the Registration procedure, applicable Information Elements as listed in Table 9.1.2.3-1 need to be configured on the MSGin5G Server. + +Pre-conditions: + +- The Application Server has connected to the serving network successfully. +- An AS Service ID has been provisioned on the Application Server. +- The MSGin5G Server address has been provisioned on the Application Server. +- Both the Application Server and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another. + +![Sequence diagram for Application Server registration. The diagram shows two lifelines: Application Server and MSGin5G Server. Step 1: Application Server sends a registration request to MSGin5G Server. Step 2: MSGin5G Server performs authentication and authorization procedures. Step 3: MSGin5G Server sends a registration response back to Application Server.](1b2ad37940c441d410002c05ff71c7c5_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server + participant MSGin5G as MSGin5G Server + Note right of MSGin5G: 2. Authentication and authorization procedures + AS->>MSGin5G: 1. Application Server registration request + MSGin5G-->>AS: 3. Application Server registration response + +``` + +Sequence diagram for Application Server registration. The diagram shows two lifelines: Application Server and MSGin5G Server. Step 1: Application Server sends a registration request to MSGin5G Server. Step 2: MSGin5G Server performs authentication and authorization procedures. Step 3: MSGin5G Server sends a registration response back to Application Server. + +**Figure 8.2.5-1: Application Server registration** + +- The Application Server sends an Application Server registration request to the MSGin5G Server. The request may include authorization information for the Application Server to register to the MSGin5G Server. The request includes the AS Service ID and may include Application Profile information as detailed in Table 9.1.2.3-1. + +2. Upon receiving the request, the MSGin5G Server validates the Application Server registration request and may verify the security credentials. + +NOTE: The authentication procedures in step 2 are built on top of the transport layer mechanism specified in Annex Y.4 of 3GPP TS 33.501 [16]. + +3. The MSGin5G Server sends an Application Server registration response to the Application Server. The response includes the information elements as specified in Table 9.1.2.4-1. If the registration is successful, the MSGin5G Server stores the AS Profile information as detailed in Table 9.1.2.3-1. + +### 8.2.6 Application Server De-registration + +By de-registering, the Application Server informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server. + +The procedure assumes that the Application Server is responsible for triggering the de-registration from the MSGin5G Server. The signalling flow for Application Server de-registration is illustrated in figure 8.2.6-1. + +Pre-conditions: + +1. The Application Server is registered to the MSGin5G Server. + +![Sequence diagram illustrating the Application Server de-registration process. The diagram shows two lifelines: Application Server and MSGin5G Server. The process starts with the Application Server determining that de-registration is required. It then sends an 'Application Server de-registration request' to the MSGin5G Server. The MSGin5G Server performs 'Authentication and authorization procedures'. Finally, it sends an 'Application Server de-registration response' back to the Application Server.](b560268ea8f6526970f23f0da225b099_img.jpg) + +``` +sequenceDiagram + participant AS as Application Server + participant MSGin5G as MSGin5G Server + Note left of AS: 1. Determine de-registration is required + AS->>MSGin5G: 2. Application Server de-registration request + Note right of MSGin5G: 3. Authentication and authorization procedures + MSGin5G-->>AS: 4. Application Server de-registration response +``` + +Sequence diagram illustrating the Application Server de-registration process. The diagram shows two lifelines: Application Server and MSGin5G Server. The process starts with the Application Server determining that de-registration is required. It then sends an 'Application Server de-registration request' to the MSGin5G Server. The MSGin5G Server performs 'Authentication and authorization procedures'. Finally, it sends an 'Application Server de-registration response' back to the Application Server. + +**Figure 8.2.6-1: Application Server de-registration** + +1. The Application Server determines to de-register from the MSGin5G Server. +2. The Application Server sends an Application Server de-registration request to the MSGin5G Server that includes the AS Service ID, as detailed in Table 9.1.2.5-1. +3. The MSGin5G Server validates the Application Server de-registration request. If the MSGin5G Server has authorized the Application Server successfully, it deletes any AS Profile information that it has stored. + +NOTE: The authentication procedures in step 3 are built on top of the transport layer mechanism specified in Annex Y.4 of 3GPP TS 33.501 [16]. + +4. The MSGin5G Server replies with an Application Server de-registration response as detailed in Table 9.1.2.6-1. + +### 8.2.7 MSGin5G UE bulk registration over MSGin5G-6 reference point + +When MSGin5G UE-1 and UE-2, which support an MSGin5G Client, perform registration via MSGin5G Gateway UE to contact the MSGin5G Server, the MSGin5G Gateway service functionality in the MSGin5G Gateway UE may decide to use bulk registration procedure specified in this clause based on the registration request sent from MSGin5G Clients + +in MSGin5G UE-1 and MSGin5G UE-2, if allowed by service policy. The procedure for MSGin5G UE bulk registration is illustrated in figure 8.2.7-1. + +Pre-conditions: + +1. The MSGin5G Gateway UE has registered to the MSGin5G Server successfully. +2. MSGin5G UE-1 and MSGin5G UE-2 have discovered and selected an MSGin5G Gateway UE as specified in clause 8.2.8 and connected to the serving network via MSGin5G Gateway UE successfully. +3. UE Service IDs and the MSGin5G Server addresses have been configured on the MSGin5G Gateway UE, MSGin5G UE-1 and MSGin5G UE-2. All these MSGin5G UEs are served by a same MSGin5G Server. +4. Both the MSGin5G UEs and MSGin5G Server have been configured with the necessary credentials to enable authenticating one another. + +![Sequence diagram for MSGin5G Client bulk registration. Lifelines: MSGin5G UE 2 (MSGin5G Client 2), MSGin5G UE 1 (MSGin5G Client 1), MSGin5G Gateway UE (MSGin5G Gateway Client), and MSGin5G Server. The process starts with MSGin5G UE 1 sending a registration request to the Gateway UE. The Gateway UE checks if it can be bulked. If not, it forwards the request to the Server, which responds back through the Gateway UE to MSGin5G UE 1. If bulk registration is used, the Gateway UE sends a bulk registration notification to MSGin5G UE 1. Then, MSGin5G Client-2 sends its registration request, which is handed over to the Gateway UE. The Gateway UE checks if bulk registration conditions are met. If so, it sends a bulk registration request to the Server. The Server splits the request, authenticates/authorizes each client individually, and sends a bulk response back to the Gateway UE. The Gateway UE then splits the bulk response into individual responses for MSGin5G UE 1 and MSGin5G UE 2.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant UE2 as MSGin5G UE 2 +MSGin5G Client 2 + participant UE1 as MSGin5G UE 1 +MSGin5G Client 1 + participant GW as MSGin5G Gateway UE +MSGin5G Gateway Client + participant Server as MSGin5G Server + + Note right of UE1: 1. MSGin5G UE registration request + UE1->>GW: 1. MSGin5G UE registration request + Note right of GW: 2. checks whether the MSGin5G UE registration request can be bulked + alt i. bulk registration is not used + Note right of GW: 3a. MSGin5G UE registration request + GW->>Server: 3a. MSGin5G UE registration request + Note right of Server: 4. MSGin5G UE registration response + Server->>GW: 4. MSGin5G UE registration response + Note right of GW: 5. MSGin5G UE registration response + GW->>UE1: 5. MSGin5G UE registration response + else ii. Bulk registration is used + Note right of GW: 3b. Bulk registration notification + GW->>UE1: 3b. Bulk registration notification + end + Note right of UE2: 6. MSGin5G Client-2 sends a MSGin5G UE registration request and the MSGin5G UE registration request is handed as step 2-5. + UE2->>GW: 6. MSGin5G Client-2 sends a MSGin5G UE registration request and the MSGin5G UE registration request is handed as step 2-5. + Note right of GW: 7. The bulk registration conditions can be fulfilled + Note right of GW: 8. MSGin5G UE bulk registration request + GW->>Server: 8. MSGin5G UE bulk registration request + Note right of Server: 9. MSGin5G Server splits the MSGin5G UE bulk registration request, executes the authentication, authorization and registration procedures for each MSGin5G Client individually as specified in clause 8.2.1. + Note right of Server: 10. MSGin5G UE bulk registration response + Server->>GW: 10. MSGin5G UE bulk registration response + Note right of GW: 11. splits the MSGin5G UE bulk registration response into multiple individual MSGin5G UE registration response + Note right of GW: 12. MSGin5G UE registration Response 1 + GW->>UE1: 12. MSGin5G UE registration Response 1 + Note right of GW: 13. MSGin5G UE registration Response 2 + GW->>UE2: 13. MSGin5G UE registration Response 2 + +``` + +Sequence diagram for MSGin5G Client bulk registration. Lifelines: MSGin5G UE 2 (MSGin5G Client 2), MSGin5G UE 1 (MSGin5G Client 1), MSGin5G Gateway UE (MSGin5G Gateway Client), and MSGin5G Server. The process starts with MSGin5G UE 1 sending a registration request to the Gateway UE. The Gateway UE checks if it can be bulked. If not, it forwards the request to the Server, which responds back through the Gateway UE to MSGin5G UE 1. If bulk registration is used, the Gateway UE sends a bulk registration notification to MSGin5G UE 1. Then, MSGin5G Client-2 sends its registration request, which is handed over to the Gateway UE. The Gateway UE checks if bulk registration conditions are met. If so, it sends a bulk registration request to the Server. The Server splits the request, authenticates/authorizes each client individually, and sends a bulk response back to the Gateway UE. The Gateway UE then splits the bulk response into individual responses for MSGin5G UE 1 and MSGin5G UE 2. + +Figure 8.2.7-1: MSGin5G Client bulk registration + +1. The MSGin5G Client-1 sends an MSGin5G UE registration request to the MSGin5G Server as specified in clause 8.2.1. In addition to the Information Elements specified in table 8.2.1-1, the MSGin5G Client-1 may also add the Information Elements specified in table 8.2.7-1 in the MSGin5G UE registration request. + +**Table 8.2.7-1: MSGin5G UE registration request** + +| Information element | Status | Description | +|----------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Registration urgent degree | O | Indicates whether the registration request is urgent or not. | +| Wait time | O | Indicates the maximum wait time of the registration request allowed by the MSGin5G Client which sent the registration request before the bulk registration request is sent to the MSGin5G Server. | + +2. Upon receiving the MSGin5G UE registration request, the MSGin5G Gateway Client checks whether this request can be queued for bulk-handling based on the service policy and the information included in the MSGin5G UE registration request, e.g. whether the MSGin5G UE registration request is urgent. + +NOTE 1: Whether bulk registration is supported can be configured in the MSGin5G Gateway Client. + +NOTE 2: The bulk registration conditions are specified by the application provider or MSGin5G Service provider and are out of scope of this document. + +3. Based on step 2: + +- a) if the MSGin5G UE registration request is urgent, MSGin5G Gateway Client may also include other registration requests; or +- b) if the MSGin5G UE registration request can be bulk-handled, MSGin5G Gateway Client sends a bulk registration notification to MSGin5G Client-1 and caches/stores the MSGin5G UE registration request until the bulk registration conditions can be fulfilled. The Information Elements specified in table 8.2.7-2 are included in the bulk registration notification. The steps 4 and 5 are skipped. + +**Table 8.2.7-2: bulk registration notification** + +| Information element | Status | Description | +|----------------------------|--------|-----------------------------------------------------------------------------------------------------------------------| +| UE Service ID | M | UE service identifier assigned to the requesting MSGin5G UE. | +| Expected registration time | O | The expected time when the bulk registration can be handled and the MSGin5G UE registration Response can be received. | + +4. The MSGin5G Server handles the MSGin5G UE registration request as specified in clause 8.2.1 and sends the corresponding MSGin5G UE registration response to MSGin5G Gateway Client. +5. The MSGin5G Gateway Client sends the MSGin5G UE registration response to MSGin5G Client-1. The MSGin5G Client-1 handles the MSGin5G UE registration response as specified in clause 8.2.1 and skips all the remaining steps in the present clause. +6. MSGin5G Client-2 sends an MSGin5G UE registration request and the MSGin5G UE registration request is handed as in steps 2-5. +7. The MSGin5G Gateway Client finds that the conditions of sending a bulk registration request can be fulfilled, e.g. + - a) the registration request expiration time in the MSGin5G UE registration request sent from MSGin5G Client-1 or MSGin5G Client-2 is reached; or + - b) the periodic bulk registration interval is reached; or + - c) the maximum MSGin5G UE registration request number in a MSGin5G UE bulk registration request is reached. + +NOTE 3: The maximum registration time, periodic bulk registration interval and maximum MSGin5G UE registration request number are implementation specific and out of the scope of the current specification. + +- The MSGin5G Gateway Client includes all cached/stored MSGin5G UE registration requests in an MSGin5G UE bulk registration request and sends it to the MSGin5G Server. The Information Elements specified in table 8.2.7-3 are included in the MSGin5G UE bulk registration request. + +**Table 8.2.7-3: MSGin5G UE bulk registration request** + +| Information element | Status | Description | +|-------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------| +| Number of individual MSGin5G UE registration requests | M | Indicates total number of MSGin5G UE registration requests which are bulked in this MSGin5G UE bulk registration request | +| List of individual MSGin5G UE registration request | M | Each element in this list contains information as specified in Table 8.2.1-1. | + +- Upon receiving the MSGin5G UE bulk registration request, the MSGin5G Server splits the MSGin5G UE bulk registration request, executes the authentication, authorization and registration procedures for each MSGin5G Client individually as specified in clause 8.2.1. + +**Editor's note: Security aspects of bulk registration is the responsibility of SA3.** + +- The MSGin5G Server includes all corresponding MSGin5G UE registration responses in an MSGin5G UE bulk registration response and sends it to MSGin5G Gateway Client. The Information Elements specified in table 8.2.7-4 are included in the MSGin5G UE bulk registration response. + +**Table 8.2.7-4: MSGin5G UE bulk registration response** + +| Information element | Status | Description | +|--------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------| +| Number of individual MSGin5G UE registration responses | M | Indicates total number of MSGin5G UE registration responses which are bulked in this MSGin5G UE bulk registration response | +| List of individual MSGin5G UE registration response | M | Each element in this list contains information as specified in Table 8.2.1-4. | + +- Upon receiving the MSGin5G UE bulk registration response, the MSGin5G Gateway Client splits the MSGin5G UE bulk registration response into multiple individual MSGin5G UE registration responses. Each individual MSGin5G UE registration response contains information as specified in Table 8.2.1-4. +- MSGin5G Gateway Client sends the MSGin5G UE registration Response 1 to MSGin5G Client-1. +- MSGin5G Gateway Client sends the MSGin5G UE registration Response 2 to MSGin5G Client-2. + +### 8.2.8 Constrained device with MSGin5G Client selecting MSGin5G Gateway UE + +The signalling flow for MSGin5G Client-2 in the MSGin5G UE-2 (which is a constrained device) to request other MSGin5G UEs supporting MSGin5G Gateway service functionality to provide their configuration is illustrated in figure 8.2.8-1. + +Pre-conditions: + +- MSGin5G UE-2 is not able to communicate with MSGin5G Server directly; +- MSGin5G UE-2 has discovered nearby MSGin5G UEs using ProSe direct discovery procedure as specified in 3GPP TS 23.304 [18] and the 5G ProSe Direct Communication is established between MSGin5G UE-2 and nearby MSGin5G UE-1 and MSGin5G UE-3 as specified in 3GPP TS 23.304 [18]. +- An MSGin5G UE-3 supports MSGin5G Gateway service functionality (i.e. MSGin5G UE-3 is an MSGin5G Gateway UE) and an MSGin5G UE-1 does not support MSGin5G Gateway service functionality (i.e. MSGin5G UE-1 is not an MSGin5G Gateway UE). +- The UE service ID has been pre-configured on the MSGin5G UE-2. + +![Sequence diagram showing MSGin5G UE-2 (constrained UE) sending a gateway request to MSGin5G UE-3 (Gateway UE) and MSGin5G UE-1. The diagram includes three steps: 1. MSGin5G gateway request, 2. MSGin5G gateway response, and 3. Gateway UE selection.](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) + +``` + +sequenceDiagram + participant UE2 as MSGin5G UE-2 +MSGin5G Client-2 + participant UE3 as MSGin5G UE-3 (MSGin5G Gateway UE) +MSGin5G Gateway Client + participant UE1 as MSGin5G UE-1 +MSGin5G Client-1 + Note left of UE2: 3. Gateway UE selection + UE2->>UE3: 1. MSGin5G gateway request + UE3-->>UE1: 1. MSGin5G gateway request + UE3-->>UE2: 2. MSGin5G gateway response + +``` + +Sequence diagram showing MSGin5G UE-2 (constrained UE) sending a gateway request to MSGin5G UE-3 (Gateway UE) and MSGin5G UE-1. The diagram includes three steps: 1. MSGin5G gateway request, 2. MSGin5G gateway response, and 3. Gateway UE selection. + +**Figure 8.2.8-1: Constrained UE sending message to request configuration of the MSGin5G Gateway UE** + +- 1) The MSGin5G Client-2 in MSGin5G UE-2 (which is a constrained UE) sends messages to all surrounding MSGin5G UEs (using ProSe Direction communication as specified in 3GPP TS 23.304 [18]) to provide their gateway configuration if MSGin5G Gateway service functionality is supported by the MSGin5G UE, i.e. the MSGin5G UE is a MSGin5G Gateway UE. The request message includes information elements as specified in Table 8.2.8-1. + +**Table 8.2.8-1: Information elements for Request for gateway UE configuration** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------| +| Layer-2 ID | M | Layer-2 identity of UE-2 | +| UE service ID | M | UE service identifier of the UE-2 | +| MSGin5G UE ID | O | MSGin5G device identifier of the UE-2 | +| Required packet size | M | Maximum allowed packet size of the UE-2 | + +- 2) Upon receiving the request from the MSGin5G Client of MSGin5G UE-2, the MSGin5G UE-3 supporting the MSGin5G Gateway service functionality sends the response for the gateway configuration. The response message includes information elements as specified in Table 8.2.8-2. The MSGin5G UE-1 does not support the MSGin5G Gateway service functionality and ignores the request for gateway UE configuration, i.e. should not send a corresponding response. + +**Table 8.2.8-2: Information elements for Response for gateway UE configuration** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------| +| Layer-2 ID | M | Layer-2 identity of UE-1 | +| UE service ID | M | UE service identifier of the UE-1 | +| MSGin5G UE ID | O | MSGin5G device identifier of the UE-1 | +| Allowed packet size | M | Maximum allowed packet size of the UE-2 | + +- 3) If the MSGin5G UE-2 receives responses from multiple different MSGin5G Gateway UEs, then the MSGin5G Client of the MSGin5G UE-2 selects an MSGin5G Gateway UE whose value of the Allowed packet size is equal or more than the value of the Required packet size of the MSGin5G UE-2. If the value of the Allowed packet size is less than the value of the Required packet size for all MSGin5G Gateway UE, then the MSGin5G Client of the MSGin5G UE-2 selects the MSGin5G Gateway UE with the maximum value of the Allowed packet size among all MSGin5G Gateway UEs and further sets the maximum allowed packet size of the constrained UE to the value of the Allowed packet size of the selected MSGin5G Gateway UE. + +If the MSGin5G UE-2 receives responses from multiple MSGin5G Gateway UEs which serve different domains, the MSGin5G UE-2 shall select the MSGin5G Gateway UE that serves the same domain as the MSGin5G UE-2 does, based on the UE service ID. + +Once MSGin5G UE has selected the MSGin5G Gateway UE, the MSGin5G UE indicates the selected MSGin5G Gateway UE by registering to use the gateway service. The signalling flow for MSGin5G Client in the MSGin5G UE (which is a constrained device) to register itself to use Gateway service of the MSGin5G Gateway UE is illustrated in figure 8.2.8-2. + +![Sequence diagram showing the registration process between MSGin5G UE and MSGin5G Gateway UE. The MSGin5G UE contains an MSGin5G Client. The MSGin5G Gateway UE contains an MSGin5G Gateway Client. The sequence is: 1. Gateway register request from MSGin5G Client to MSGin5G Gateway Client; 2. Authorize the request from MSGin5G Gateway Client to MSGin5G Client; 3. Gateway register response from MSGin5G Gateway Client to MSGin5G Client.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G UE + participant MSGin5G Gateway UE + Note right of MSGin5G UE: MSGin5G Client + Note right of MSGin5G Gateway UE: MSGin5G Gateway Client + MSGin5G Client->>MSGin5G Gateway Client: 1. Gateway register request + MSGin5G Gateway Client->>MSGin5G Client: 2. Authorize the request + MSGin5G Gateway Client->>MSGin5G Client: 3. Gateway register response + +``` + +Sequence diagram showing the registration process between MSGin5G UE and MSGin5G Gateway UE. The MSGin5G UE contains an MSGin5G Client. The MSGin5G Gateway UE contains an MSGin5G Gateway Client. The sequence is: 1. Gateway register request from MSGin5G Client to MSGin5G Gateway Client; 2. Authorize the request from MSGin5G Gateway Client to MSGin5G Client; 3. Gateway register response from MSGin5G Gateway Client to MSGin5G Client. + +**Figure 8.2.8-2: Constrained UE registering to use MSGin5G Gateway UE** + +- 1) Upon selecting the MSGin5G Gateway UE, the MSGin5G Client of the MSGin5G UE sends a Gateway registration request to register with the selected MSGin5G Gateway UE to request the use of gateway service. The request message includes the UE service ID and may include the MSGin5G UE ID of the MSGin5G UE (i.e. constrained UE) and the time till when constrained device is intended to use the gateway service from the selected MSGin5G Gateway UE. The information elements are specified in Table 8.2.8-3. + +**Table 8.2.8-3: Information elements for Gateway registration request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------| +| UE service ID | M | UE service identifier of the MSGin5G UE | +| MSGin5G UE ID | O | Unique identifier that represents the MSGin5G UE (i.e. the device identifier of the MSGin5G UE) | +| Time till | O | The time when constrained device is intended to use the gateway service | + +- 2) Upon receiving the request from the MSGin5G Client of the MSGin5G UE, the MSGin5G Gateway Client in MSGin5G Gateway UE checks whether the MSGin5G UE is authorized to use the gateway service or not. +- 3) The MSGin5G Gateway Client in MSGin5G Gateway UE sends the response message with the status of the registration. If the registration is successful, the response message includes parameters like the Accepted time till when the constrained device is allowed to use the gateway service from the selected MSGin5G Gateway UE. The information elements are specified in Table 8.2.8-4. + +**Table 8.2.8-4: Gateway registration response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------| +| UE Service ID | M | UE service identifier of the requesting MSGin5G UE. | +| Registration result | M | Indication if the registration is success or failure | +| Accepted time till | O | Indicates the time when constrained device is allowed to use the gateway service if the constrained device was authorized successfully. | +| Failure Cause | O | The reason for failure. This IE should be included if the Registration result is failure. | + +### 8.2.9 Non-MSGin5G UE bulk registration + +Non-MSGin5G UEs (i.e., Legacy 3GPP UEs or Non-3GPP UEs) are connected to the MSGin5G Server through a Message Gateway. The Message Gateway may decide to use bulk registration procedure specified in this clause based on service policy. The procedure for Non-MSGin5G UE bulk registration is illustrated in figure 8.2.9-1. + +Pre-conditions: + +1. The Message Gateway has been pre-configured with the MSGin5G Server address. +2. The Message Gateway has been configured with the necessary information as specified in clause 8.1.3. If the UE Service ID and Non-MSGin5G UE credentials have been configured and the Non-MSGin5G UEs' Profile is available, this pre-condition enables authentication and Non- MSGin5G UEs registration at the Message Server. +3. A secured connection has been established between the Message Gateway and the MSGin5G Server. + +![Sequence diagram showing the Non-MSGin5G UE bulk registration process between a Message Gateway and an MSGin5G Server. The steps are: 1. checks whether the Non-MSGin5G UE registrations can be bulked; 2. Non-MSGin5G UE bulk registration request; 3. Authentication and authorization procedures; 4. Non-MSGin5G UE bulk registration response.](1e8c50ad4fca7f315a407347dd5091cc_img.jpg) + +``` + +sequenceDiagram + participant MG as Message Gateway + participant MS as MSGin5G Server + Note left of MG: 1. checks whether the Non-MSGin5G UE registrations can be bulked + MG->>MS: 2. Non-MSGin5G UE bulk registration request + Note right of MS: 3. Authentication and authorization procedures + MS->>MG: 4. Non-MSGin5G UE bulk registration response + +``` + +Sequence diagram showing the Non-MSGin5G UE bulk registration process between a Message Gateway and an MSGin5G Server. The steps are: 1. checks whether the Non-MSGin5G UE registrations can be bulked; 2. Non-MSGin5G UE bulk registration request; 3. Authentication and authorization procedures; 4. Non-MSGin5G UE bulk registration response. + +Figure 8.2.9-1: Non-MSGin5G UE bulk registration + +1. The Message Gateway determines to perform Non-MSGin5G UE bulk registration. + +NOTE: The conditions of whether the Non-MSGin5G UE bulk registration is used are implementation specific and out of the scope of the current specification. + +2. The Message Gateway sends a Non-MSGin5G UE bulk registration request to the MSGin5G Server. The Information Elements specified in table 8.2.9-1 are included in the Non-MSGin5G UE bulk registration request. + +Table 8.2.9-1: Non-MSGin5G UE bulk registration request + +| Information element | Status | Description | +|-------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------| +| Number of individual MSGin5G UE registration requests | M | Indicates total number of Non-MSGin5G UE registration requests which are bulked in this Non-MSGin5G UE bulk registration request | +| List of individual Non-MSGin5G UE information | M | Each element in this list contains information as specified in Table 8.2.3-1. | + +3. Upon receiving the Non-MSGin5G UE bulk registration request, the MSGin5G Server processes each of the UE registrations from the list individually as specified in clause 8.2.3. For each individual Non-MSGin5G UE registration that successful, the MSGin5G Server stores that UE Service ID and associated Non-MSGin5G UE Profile information. + +Editor's note: Security aspects of Non-MSGin5G UE bulk registration is the responsibility of SA3. + +4. The MSGin5G Server includes all corresponding MSGin5G UE registration responses in a Non-MSGin5G UE bulk registration response and sends it to the Message Gateway. The Information Elements specified in table 8.2.9-2 are included in the Non-MSGin5G UE bulk registration response. + +**Table 8.2.9-2: MSGin5G UE bulk registration response** + +| Information element | Status | Description | +|------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------| +| Number of individual Non-MSGin5G UE registration responses | M | Indicates total number of Non-MSGin5G UE registration responses which are bulked in this MSGin5G UE bulk registration response | +| List of individual Non-MSGin5G UE registration response | M | Each element in this list contains information as specified in Table 8.2.1-4. | + +### 8.2.10 Non-MSGin5G UE bulk de-registration + +The procedure assumes that the Message Gateway is responsible for initiating the bulk de-registration from the MSGin5G Server on behalf of the Non-MSGin5G UEs. The signaling flow for Non-MSGin5G UE bulk de-registration is illustrated in figure 8.2.10-1. + +Pre-conditions: + +1. The Message Gateway successfully performed registration with the MSGin5G Server on behalf of a set of Non-MSGin5G UEs. + +![Sequence diagram for Non-MSGin5G UE bulk de-registration. The diagram shows two lifelines: Message Gateway and MSGin5G Server. The process starts with the Message Gateway determining to de-register a set of Non-MSGin5G UEs. It then sends a 'Non-MSGin5G UE bulk de-registration request' to the MSGin5G Server. The MSGin5G Server performs 'Authentication and authorization procedures' and returns a 'Non-MSGin5G UE bulk de-registration response' to the Message Gateway.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +``` + +sequenceDiagram + participant MG as Message Gateway + participant MS as MSGin5G Server + Note left of MG: 1. determines to de-register a set of Non-MSGin5G UEs + MG->>MS: 2. Non-MSGin5G UE bulk de-registration request + Note right of MS: 3. Authentication and authorization procedures + MS-->>MG: 4. Non-MSGin5G UE bulk de-registration response + +``` + +Sequence diagram for Non-MSGin5G UE bulk de-registration. The diagram shows two lifelines: Message Gateway and MSGin5G Server. The process starts with the Message Gateway determining to de-register a set of Non-MSGin5G UEs. It then sends a 'Non-MSGin5G UE bulk de-registration request' to the MSGin5G Server. The MSGin5G Server performs 'Authentication and authorization procedures' and returns a 'Non-MSGin5G UE bulk de-registration response' to the Message Gateway. + +**Figure 8.2.10-1: Non-MSGin5G UE bulk de-registration** + +1. The Message Gateway determines to perform Non-MSGin5G UE bulk de-registration. + +NOTE: The conditions of whether the Non-MSGin5G UEs can be bulked de-registered are implementation specific and out of the scope of the current specification. + +2. The Message Gateway sends a Non-MSGin5G UE bulk de-registration request to the MSGin5G Server. The Information Elements specified in table 8.2.10-1 are included in the Non-MSGin5G UE bulk de-registration request. + +**Table 8.2.10-1: Non-MSGin5G UE bulk de-registration request** + +| Information element | Status | Description | +|----------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------| +| Number of individual MSGin5G UE de-registration requests | M | Indicates total number of Non-MSGin5G UE de-registration requests which are bulked in this Non-MSGin5G UE bulk de-registration request | +| List of individual UE Service ID | M | Each element in this list contains a UE service identifier assigned to the Non-MSGin5G UE. | + +3. Upon receiving the request, the MSGin5G Server processes each of the UE de-registration from the list individually as specified in clause 8.2.4. The MSGin5G Server deletes any applicable UE Service ID in the List of individual UE Service ID and associated MSGin5G Client Profile information that it has stored. + +Editor's note: Security aspects of Non-MSGin5G UE bulk de-registration is the responsibility of SA3. + +4. The MSGin5G Server replies with a Non-MSGin5G UE bulk de-registration response as shown in table 8.2.10-2. + +**Table 8.2.10-2: Non-MSGin5G UE bulk de-registration response** + +| Information element | Status | Description | +|---------------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------| +| Number of individual Non-MSGin5G UE de-registration responses | M | Indicates total number of Non-MSGin5G UE de-registration responses which are bulked in this Non-MSGin5G UE bulk de-registration response | +| List of individual Non-MSGin5G UE de-registration response | M | Each element in this list contains information as specified in Table 8.2.4-2. | + +### 8.2.11 MSGin5G UE bulk de-registration over MSGin5G-6 reference point + +The MSGin5G Gateway UE may decide to use bulk de-registration procedure specified in this clause based on the de-registration request sent from MSGin5G Clients in MSGin5G UEs or, if allowed by service policy. The procedure for MSGin5G UE bulk de-registration is illustrated in figure 8.2.11-1. + +Pre-conditions: + +1. The MSGin5G Gateway UE has registered to the MSGin5G Server successfully. +2. MSGin5G UE-1 and MSGin5G UE-2 have registered to the MSGin5G Server via MSGin5G Gateway UE successfully as specified in clause 8.2.8. + +![Sequence diagram for MSGin5G UE bulk de-registration. Lifelines: MSGin5G UE 2 (Client 2), MSGin5G UE 1 (Client 1), MSGin5G Gateway UE (Gateway Client), and MSGin5G Server. The process involves individual de-registration requests from Client 1 and Client 2, a check for bulk de-registration at the Gateway, and subsequent bulk de-registration handling by the Server.](ec3647789b5c38fb686f2a0833324e79_img.jpg) + +``` + +sequenceDiagram + participant UE2 as MSGin5G UE 2 +MSGin5G Client 2 + participant UE1 as MSGin5G UE 1 +MSGin5G Client 1 + participant GW as MSGin5G Gateway UE +MSGin5G Gateway Client + participant Server as MSGin5G Server + + Note right of UE1: 1. MSGin5G UE de-registration request + UE1->>GW: 1. MSGin5G UE de-registration request + Note right of GW: 2. checks whether the MSGin5G UE de-registration request can be bulked + alt i. bulk de-registration is not used + Note right of GW: 3a. MSGin5G UE de-registration request + GW->>Server: 3a. MSGin5G UE de-registration request + Note right of Server: 4. MSGin5G UE de-registration response + Server->>GW: 4. MSGin5G UE de-registration response + Note right of GW: 5. MSGin5G UE de-registration response + GW->>UE1: 5. MSGin5G UE de-registration response + else ii. Bulk de-registration is used + Note right of GW: 3b. Bulk de-registration notification + GW->>UE1: 3b. Bulk de-registration notification + end + Note right of UE2: 6. MSGin5G Client-2 sends a MSGin5G UE de-registration request and the MSGin5G UE de-registration request is handed as step 2-5. + UE2->>GW: 6. MSGin5G Client-2 sends a MSGin5G UE de-registration request and the MSGin5G UE de-registration request is handed as step 2-5. + Note right of GW: 7. The bulk de-registration conditions can be fulfilled + Note right of GW: 8. MSGin5G UE Bulk de-registration request + GW->>Server: 8. MSGin5G UE Bulk de-registration request + Note right of Server: 9. MSGin5G Server processes each of the MSGin5G UE de-registration from the list individually as specified in clause 8.2.2 + Note right of Server: 10. MSGin5G UE Bulk de-registration response + Server->>GW: 10. MSGin5G UE Bulk de-registration response + Note right of GW: 11. splits the MSGin5G UE bulk de-registration response into multiple individual MSGin5G UE de-registration response + Note right of GW: 12. MSGin5G UE de-registration Response 1 + GW->>UE1: 12. MSGin5G UE de-registration Response 1 + Note right of GW: 13. MSGin5G UE de-registration Response 2 + GW->>UE2: 13. MSGin5G UE de-registration Response 2 + +``` + +Sequence diagram for MSGin5G UE bulk de-registration. Lifelines: MSGin5G UE 2 (Client 2), MSGin5G UE 1 (Client 1), MSGin5G Gateway UE (Gateway Client), and MSGin5G Server. The process involves individual de-registration requests from Client 1 and Client 2, a check for bulk de-registration at the Gateway, and subsequent bulk de-registration handling by the Server. + +Figure 8.2.11-1: MSGin5G UE bulk de-registration + +1. The MSGin5G Client-1 sends an MSGin5G UE de-registration request to the MSGin5G Server as specified in clause 8.2.2, In addition to the Information Elements specified in table 8.2.2-1, the MSGin5G Client-1 may also add the Information Elements specified in table 8.2.11-1 in the MSGin5G UE de-registration request. + +Table 8.2.11-1: MSGin5G UE de-registration request + +| Information element | Status | Description | +|-------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| De-registration urgent degree | O | Indicates whether the de-registration request is urgent or not. | +| Wait time | O | Indicates the maximum wait time of the de-registration request allowed by the MSGin5G Client-2 before the bulk de-registration request is sent to the MSGin5G Server. | + +2. Upon receiving the MSGin5G UE de-registration request, the MSGin5G Gateway Client checks whether this request can be queued for bulk-handling based on the service policy and the information included in the MSGin5G UE registration request, e.g. whether the MSGin5G UE de-registration request is urgent. + +NOTE 1: Whether bulk de-registration is supported can be configured in the MSGin5G Gateway Client. + +NOTE 2: The bulk de-registration conditions are specified by the application provider or MSGin5G Service provider and are out of scope of this document. + +3. Based on step 2: + +- a) if the MSGin5G UE de-registration request is urgent, the MSGin5G Gateway Client may also include other registration requests; or +- b) if the MSGin5G UE de-registration request can be bulked, MSGin5G Client-1 sends a bulk de-registration notification to MSGin5G Client-1 and caches/stores the MSGin5G UE de-registration request until the bulk de-registration conditions can be fulfilled. The Information Elements specified in table 8.2.11-2 are included in the bulk de-registration notification. The steps 4 and 5 are skipped. + +**Table 8.2.11-2: bulk de-registration notification** + +| Information element | Status | Description | +|-------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------| +| UE Service ID | M | UE service identifier assigned to the requesting MSGin5G UE. | +| Expected de-registration time | O | The expected time when the bulk de-registration can be handled and the MSGin5G UE de-registration response can be received. | + +4. The MSGin5G Server handles the MSGin5G UE de-registration request as specified in clause 8.2.2 and sends the corresponding MSGin5G UE de-registration response to MSGin5G Gateway Client. +5. The MSGin5G Gateway Client sends the MSGin5G UE de-registration response to MSGin5G Client-1. The MSGin5G Client-1 handles the MSGin5G UE de-registration response as specified in clause 8.2.2 and skips all the remaining steps in the present clause. +6. MSGin5G Client-2 sends an MSGin5G UE de-registration request and the MSGin5G UE de-registration request is handled as in steps 2-5. +7. The MSGin5G Gateway Client finds that the conditions of sending a bulk de-registration request can be fulfilled, e.g. + - a) the de-registration request expiration time in the MSGin5G UE de-registration request sent from MSGin5G Client-1 or MSGin5G Client-2 is reached; or + - b) the periodic bulk de-registration interval is reached; or + - c) the maximum MSGin5G UE de-registration request number in a MSGin5G UE bulk de-registration request is reached. + +NOTE 3: The maximum de-registration time, periodic bulk de-registration interval and maximum MSGin5G UE de-registration request number are implementation specific and out of the scope of the current specification. + +8. The MSGin5G Gateway Client includes all cached/stored MSGin5G UE de-registration requests in an MSGin5G UE bulk de-registration request and sends it to the MSGin5G Server. The Information Elements specified in table 8.2.11-3 are included in the MSGin5G UE bulk de-registration request. + +**Table 8.2.11-3: MSGin5G UE bulk de-registration request** + +| Information element | Status | Description | +|----------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------| +| Number of individual MSGin5G UE de-registration requests | M | Indicates total number of MSGin5G UE de-registration requests which are bulked in this MSGin5G UE bulk de-registration request | +| List of individual MSGin5G UE de-registration request | M | Each element in this list contains information as specified in Table 8.2.2-1. | + +- Upon receiving the MSGin5G UE bulk de-registration request, the MSGin5G Server processes each of the MSGin5G UE de-registration from the list individually as specified in clause 8.2.2. + +**Editor's note:** Security aspects of MSGin5G UE bulk de-registration is the responsibility of SA3. + +- The MSGin5G Server includes all corresponding MSGin5G UE de-registration responses in an MSGin5G UE bulk de-registration response and sends it to MSGin5G Gateway Client. The Information Elements specified in table 8.2.11-4 are included in the MSGin5G UE bulk de-registration response. + +**Table 8.2.11-4: MSGin5G UE bulk de-registration response** + +| Information element | Status | Description | +|-----------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------| +| Number of individual MSGin5G UE de-registration responses | M | Indicates total number of MSGin5G UE de-registration responses which are bulked in this MSGin5G UE bulk de-registration response | +| List of individual MSGin5G UE de-registration response | M | Each element in this list contains information as specified in Table 8.2.2-2 | + +- Upon receiving the MSGin5G UE bulk de-registration response, the MSGin5G Gateway Client splits the MSGin5G UE bulk de-registration response into multiple individual MSGin5G UE de-registration responses. Each individual MSGin5G UE de-registration response contains information as specified in Table 8.2.2-2. +- MSGin5G Gateway Client sends the MSGin5G UE de-registration Response 1 to MSGin5G Client-1. +- MSGin5G Gateway Client sends the MSGin5G UE de-registration Response 2 to MSGin5G Client-2. + +## 8.3 Message delivery procedures + +### 8.3.1 General + +All MSGin5G message traffic is routed via the MSGin5G Server. The present clause specifies the MSGin5G message origination procedure when a MSGin5G service endpoint (i.e. MSGin5G UE, AS or Message Gateway) sending a message to its recipient(s) and the MSGin5G message termination procedure when a MSGin5G Server delivers a message to the MSGin5G service endpoint. + +### 8.3.2 MSGin5G messages origination procedure + +Figure 8.3.2-1 shows the procedure for an MSGin5G UE that initiates an MSGin5G message request. + +![Sequence diagram for Figure 8.3.2-1: New MSGin5G message request from UE](fe25bbee6685ab20f50ffc80c3feddd8_img.jpg) + +``` +sequenceDiagram + participant Application Client + participant MSGin5G Client + participant MSGin5G Server + Note left of Application Client: MSGin5G UE + Application Client->>MSGin5G Client: 1. request + MSGin5G Client->>MSGin5G Server: 2. MSGin5G message request + MSGin5G Server->>MSGin5G Client: 3. Authorization and message process + MSGin5G Server-->>MSGin5G Client: 4. Message response +``` + +This sequence diagram illustrates the interaction for a new MSGin5G message request from a User Equipment (UE). The UE contains an Application Client and an MSGin5G Client. The process starts with the Application Client sending a '1. request' to the MSGin5G Client. The MSGin5G Client then sends a '2. MSGin5G message request' to the MSGin5G Server. The server performs a '3. Authorization and message process' and returns a '4. Message response' to the client. + +Sequence diagram for Figure 8.3.2-1: New MSGin5G message request from UE + +**Figure 8.3.2-1: New MSGin5G message request from UE** + +Figure 8.3.2-2 shows the procedure for an Application Server that initiates an API request specified in clause 9.1.1.1 for sending an MSGin5G message to UE. + +![Sequence diagram for Figure 8.3.2-2: Application Server initiates a request for sending an MSGin5G message](036c200da9b64c3eb5aae2d67bb53e1f_img.jpg) + +``` +sequenceDiagram + participant Application Server + participant MSGin5G Server + Application Server->>MSGin5G Server: 2. API message request + MSGin5G Server->>MSGin5G Server: 3. Authorization and message process + MSGin5G Server-->>Application Server: 4. API message response +``` + +This sequence diagram shows the procedure for an Application Server to initiate a request for sending an MSGin5G message. The Application Server sends a '2. API message request' to the MSGin5G Server. The server then performs an internal '3. Authorization and message process' and sends back a '4. API message response' to the Application Server. + +Sequence diagram for Figure 8.3.2-2: Application Server initiates a request for sending an MSGin5G message + +**Figure 8.3.2-2: Application Server initiates a request for sending an MSGin5G message** + +Figure 8.3.2-3 shows the procedure for a Legacy 3GPP Message Gateway or a non-3GPP Message Gateway that sends a new MSGin5G message request to the MSGin5G Server on behalf of a Legacy 3GPP UE or Non-3GPP UE. + +![Sequence diagram showing the interaction between a Message Gateway and an MSGin5G Server. The Message Gateway sends a '2. MSGin5G message request' to the MSGin5G Server. The MSGin5G Server then performs an '3. Authorization and message process' and sends a '4. message response' back to the Message Gateway.](40ebe9179df298f1b6d76822f28d90aa_img.jpg) + +``` +sequenceDiagram + participant Message Gateway + participant MSGin5G Server + Note right of MSGin5G Server: 3. Authorization and message process + Message Gateway->>MSGin5G Server: 2. MSGin5G message request + MSGin5G Server-->>Message Gateway: 4. message response +``` + +Sequence diagram showing the interaction between a Message Gateway and an MSGin5G Server. The Message Gateway sends a '2. MSGin5G message request' to the MSGin5G Server. The MSGin5G Server then performs an '3. Authorization and message process' and sends a '4. message response' back to the Message Gateway. + +**Figure 8.3.2-3: New MSGin5G message request sending from Message Gateway** + +The following procedure applies to the above figures 8.3.2-1, 8.3.2-2 and 8.3.2-3 with the exception that step 1 only applies to figure 8.3.2-1. + +1. The Application Client in the UE sends a request to the MSGin5G Client for invoking the MSGin5G Client to send a new MSGin5G message to a recipient or to multiple recipients. + +**Editor's note:** Whether the APIs provided by the MSGin5G Client to the Application Client is to be specified in another clause of the TS is FFS. + +2. As shown in figure 8.3.2-1 or 8.3.2-3, the MSGin5G Client or Message Gateway sends the MSGin5G message request to the MSGin5G Server and includes the IEs as listed in table 8.3.2-1 in the request; or as shown in figure 8.3.2-2, the Application Server sends an API request to the MSGin5G Server for sending an MSGin5G message, the API request includes the IEs as listed in table 8.3.2-1. + +**NOTE:** If the value of the Store and forward flag IE in the MSGin5G message request indicates that store and forward services are requested by the sender, the procedure in 8.3.6 applies instead. + +**Table 8.3.2-1: Request to MSGin5G Server for sending MSGin5G message** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID | M | The service identity of the sending MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the sending Application Server. | +| Recipient UE Service ID/AS Service ID (see NOTE 1, NOTE 2) | O | The service identity of the receiving MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the receiving Application Server. This IE is mandatory for Point-to-Point messaging, AS-to-Point messaging, AOMT messaging and MOAT messaging and is not present in other message scenarios. | +| Group Service ID (see NOTE 1) | O | The service identifier of the target MSGin5G Group. This IE is mandatory for a Group Message and is not present in other message scenarios. | +| Broadcast Area ID (see NOTE 1) | O | The service identifier of the Broadcast Service Area where the message needs to be broadcast. This IE is mandatory in the Broadcast Message and is not present in other message scenarios. | +| Messaging Topic (see NOTE 1) | O | Indicates which Messaging Topic this message is related to. This IE is mandatory for a message distribution based on topic and is not present in other message scenarios. | +| Application ID | O | Identifies the application(s) for which the payload is intended. This list of Application IDs IE is required when the message is sent to one or multiple Application Clients served by same MSGin5G Client. This list of Application IDs IE may be included when the message is sent to an Application Server or to an Application Client. MSGin5G Server is unaware of the content. | +| Message ID | M | Unique identifier of this message. | +| Delivery status required | O | Indicates if delivery acknowledgement from the recipient is requested. | +| Payload | O | Payload of the message. MSGin5G Server/Client is unaware of the content. If the request is sent from MSGin5G Client or Message Gateway to the MSGin5G Server, the maximum size of this IE is a configurable value that shall not exceed 2048 octets. | +| Priority type (see NOTE 3) | O | Application priority level requested for this message. The application priority levels include High, Normal and Low. The default Priority type of an MSGin5G message is Normal. | +| Message is segmented | O | Indicates this message is part of a segmented message. | +| Segmentation set identifier | O | All segmented messages associated within the same set of segmented messages (i.e. associated with the same MSGin5G message) are assigned the same unique identifier. Mandatory IE to be present in every segmented message. | +| Total number of message segments | O | Indicates the total number of segments for the message. The Total Segments needs to be included only in the first segment of the message. | +| Message segment number | O | An incrementing message segment number that indicates segmented message number of each segmented message within a set of segmented messages | +| Last segment flag | O | An indicator of whether this segmented message is the last segment in the set of segmented messages or not. The Last Segment Flag needs to be included only in the last segment of the message. Message segment number of the segment with "Last Segment Flag" set can be considered as total segments. | +| Store and forward flag | M | An indicator of whether store and forward services are requested for this message. If the value indicates that store and forward services are requested by the sender, the store and forward procedure in clause 8.3.6 applies. | +| Store and forward parameters | O | Parameters used by MSGin5G Server for providing store and forward services, as detailed in table 8.3.2-2. This IE shall be included only if the value of the Store and forward flag IE indicates that store and forward services are requested. The MSGin5G store and forward procedure is detailed in clause 8.3.6. | +| NOTE 1: Only one of these IEs shall be included to represent the type of message request. The MSGin5G Client may construct the related IEs based on the information received from Application Client, e.g. adds the MSGin5G service domain. | | | +| NOTE 2: When the originator is an Application Server, (i.e. Originating AS Service ID is present), this IE shall be a UE Service ID. | | | +| NOTE 3: The MSGin5G message with high priority should not be aggregated. The other usages of the priority level of the message is implementation specific and is out of scope of this document. | | | + +**Table 8.3.2-2: Store and forward parameters** + +| Value | Status | Description | +|----------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message expiration time | O | Indicates message expiration time used for providing store and forward services if the destination is not available for communications. The MSGin5GServer attempts delivery at or before the message expiration time, or when the recipient becomes available. | +| Application specific store and forward information | O | Application specific information about store and forward handling, e.g. a delivery time/date. | + +- The MSGin5G Server verifies that the sender is authorized to send the message and checks the integrity of the message. + +If the received MSGin5G message request is for a Group Message, the MSGin5G Server shall generate an individual message to all group members (excluding the message originator) with additional Recipient UE Service ID to each individual message as shown in table 8.3.3-1. + +If the received MSGin5G message is a Message Topic message, the MSGin5G Server shall generate an individual message to all subscribers subscribing this message topic (excluding the message originator) with additional Recipient UE Service ID to each individual message as shown in table 8.3.3-1. + +- The MSGin5G Server may send a Message response to the originating entity if the message is rejected or stored and includes the IEs as listed in table 8.3.2-3 in the response. + +**Table 8.3.2-3: Message Response** + +| Information element | Status | Description | +|-----------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID | M | The identity of the MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the identity of the Application Server that initiated the previous Request. | +| Message ID | M | Identifier of the initiating Request. | +| Segment set identifier | O | Included in the message response if the originating message was a segmented message. | +| Delivery Status | O | Indicates if delivery is a failure, or if the message is stored for deferred delivery. | +| Failure Cause | O | The reason for failure | + +### 8.3.3 MSGin5G messages termination procedure + +Figure 8.3.3-1 shows the procedure for the MSGin5G Server that delivers an MSGin5G message. + +![Sequence diagram for MSGin5G message towards UE](675af5bb2357ce5b510e613d04f66bdc_img.jpg) + +``` +sequenceDiagram + participant MSGin5G Server + participant MSGin5G UE + Note right of MSGin5G UE: MSGin5G Client + Note right of MSGin5G UE: Application Client + MSGin5G Server->>MSGin5G Client: 1. MSGin5G message request + MSGin5G Client-->>Application Client: 2. Message delivery +``` + +The diagram illustrates a sequence of interactions for delivering an MSGin5G message to a User Equipment (UE). On the left, a box labeled 'MSGin5G Server' has a solid vertical lifeline. On the right, a larger box labeled 'MSGin5G UE' contains two sub-components: 'MSGin5G Client' and 'Application Client', each with its own solid vertical lifeline. A solid horizontal arrow labeled '1. MSGin5G message request' points from the server to the MSGin5G Client. A dashed horizontal arrow labeled '2. Message delivery' points from the MSGin5G Client to the Application Client. + +Sequence diagram for MSGin5G message towards UE + +**Figure 8.3.3-1: MSGin5G message towards UE** + +Figure 8.3.3-2 shows the same procedure (step 1 only), however for the MSGin5G Server that delivers the message to an Application Server by application request. + +![Sequence diagram for message towards an Application Server](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +``` +sequenceDiagram + participant MSGin5G Server + participant Application Server + MSGin5G Server->>Application Server: 1. MSGin5G Message +``` + +The diagram shows a single interaction between two servers. On the left is a box labeled 'MSGin5G Server' and on the right is a box labeled 'Application Server', both with solid vertical lifelines. A solid horizontal arrow labeled '1. MSGin5G Message' points from the MSGin5G Server to the Application Server. + +Sequence diagram for message towards an Application Server + +**Figure 8.3.3-2: Message towards an Application Server** + +Figure 8.3.3-3 shows the procedure for the MSGin5G Server that delivers an MSGin5G message to a Legacy 3GPP Message Gateway, a Non-3GPP Message Gateway, or a Broadcast Message Gateway. + +![Sequence diagram for MSGin5G message towards a Message Gateway](65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg) + +``` +sequenceDiagram + participant MSGin5G Server + participant Message Gateway + MSGin5G Server->>Message Gateway: 1. MSGin5G message request +``` + +The diagram depicts an interaction between a server and a gateway. On the left is a box labeled 'MSGin5G Server' and on the right is a box labeled 'Message Gateway', both with solid vertical lifelines. A solid horizontal arrow labeled '1. MSGin5G message request' points from the MSGin5G Server to the Message Gateway. + +Sequence diagram for MSGin5G message towards a Message Gateway + +**Figure 8.3.3-3: MSGin5G message towards a Message Gateway** + +The following procedure applies to the above figures 8.3.3-1, 8.3.3-2 and 8.3.3-3 with the exception that step 2 only applies to figure 8.3.3-1. + +1. The MSGin5G Server delivers the received MSGin5G message as listed in table 8.3.3-1. + +**Table 8.3.3-1: MSGin5G message request from MSGin5G Server** + +| Information element | Status | Description | +|-----------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID | M | The service identity of the originating MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the originating Application Server. | +| Recipient UE Service ID/AS Service ID | O | The service identity of the receiving entity.
For Group messaging, this IE can be a Recipient UE Service ID only.
This IE is fetched from the participant information of the recipient in the group profile.
For message delivery based on Messaging Topic subscription, this IE is the UE Service ID/AS Service ID of the Messaging Topic subscriber. | +| Broadcast Area ID | O | The identifier of the Service Area where the message needs to be broadcast. | +| Application ID | O | Identifies the application for which the payload is intended. | +| Message ID | M | Unique identifier of this message. | +| Delivery status required | O | Indicates if delivery acknowledgement from the recipient is requested. | +| Payload | O | Payload of the message. | +| Message is segmented | O | Indicates this message is part of a segmented message. | +| Group Service ID | O | The service identifier of a Group. | +| Messaging Topic | O | Indicates which Messaging Topic this message is related to. | +| Segmentation Set Identifier | O | All segmented messages associated within the same set of segmented messages (i.e. associated with the same MSGin5G message) are assigned the same unique identifier. | +| Total number of message segments | O | Indicates the total number of segments for the message.

The Total Segments needs to be included only in the first segment of the message. | +| Message segment number | O | An incrementing message segment number that indicates segmented message number of each segmented message within a set of segmented messages. | +| Last Segment Flag | O | An indicator of whether this segmented message is the last segment in the set of segmented messages or not.
The Last Segment Flag needs to be included only in the last segment of the message. Message segment number of the segment with "Last Segment Flag" set can be considered as total segments. | +| Priority type | O | Application priority level requested by the message originator for this message. | + +### 8.3.4 MSGin5G message delivery status report into the MSGin5G Server + +Figure 8.3.4-1 shows the procedure for an MSGin5G UE that initiates an MSGin5G message delivery status report. + +![Sequence diagram showing message delivery status report from MSGin5G UE](3c99312f83459559d9a301148555d7b9_img.jpg) + +``` +sequenceDiagram + participant Application Client + participant MSGin5G Client + participant MSGin5G Server + Note right of MSGin5G Server: 3. Authorization + Application Client->>MSGin5G Client: 1. request + MSGin5G Client->>MSGin5G Server: 2. MSGin5G message delivery status report + MSGin5G Server-->>MSGin5G Client: 4. response +``` + +The diagram illustrates the interaction for a message delivery status report from a MSGin5G UE. The UE contains an Application Client and an MSGin5G Client. The sequence is: 1. The Application Client sends a 'request' to the MSGin5G Client. 2. The MSGin5G Client sends a 'MSGin5G message delivery status report' to the MSGin5G Server. 3. The MSGin5G Server performs an 'Authorization' step. 4. The MSGin5G Server sends a 'response' back to the MSGin5G Client. + +Sequence diagram showing message delivery status report from MSGin5G UE + +**Figure 8.3.4-1: Message delivery status report from MSGin5G UE** + +Figure 8.3.4-2 shows the procedure for an Application Server that initiates an API request for MSGin5G message delivery status report specified in clause 9.1.1.4 to UE. + +![Sequence diagram showing message delivery status report from Application Server](1033dc9fde75540d224c907681b1b7aa_img.jpg) + +``` +sequenceDiagram + participant Application Server + participant MSGin5G Server + Note right of MSGin5G Server: 3. Authorization + Application Server->>MSGin5G Server: 2. API request for MSGin5G message delivery status report + MSGin5G Server-->>Application Server: 4. API response +``` + +The diagram illustrates the interaction for a message delivery status report initiated by an Application Server. The sequence is: 2. The Application Server sends an 'API request for MSGin5G message delivery status report' to the MSGin5G Server. 3. The MSGin5G Server performs an 'Authorization' step. 4. The MSGin5G Server sends an 'API response' back to the Application Server. + +Sequence diagram showing message delivery status report from Application Server + +**Figure 8.3.4-2: Message delivery status report from Application Server** + +Figure 8.3.2-3 shows the procedure for a Legacy 3GPP Message Gateway or a Non-3GPP Message Gateway that sends an MSGin5G message delivery status report to the MSGin5G Server on behalf of a Legacy 3GPP UE or Non-3GPP UE. + +![Sequence diagram showing the interaction between a Message Gateway and an MSGin5G Server. The Message Gateway sends a '2. MSGin5G message delivery status report' to the MSGin5G Server. The MSGin5G Server then performs '3. Authorization' and sends a '4. response' back to the Message Gateway.](01832e59ebad7ada5e790de6f90cc9b6_img.jpg) + +``` +sequenceDiagram + participant MG as Message Gateway + participant MS as MSGin5G Server + Note right of MS: 3. Authorization + MG->>MS: 2. MSGin5G message delivery status report + MS-->>MG: 4. response +``` + +Sequence diagram showing the interaction between a Message Gateway and an MSGin5G Server. The Message Gateway sends a '2. MSGin5G message delivery status report' to the MSGin5G Server. The MSGin5G Server then performs '3. Authorization' and sends a '4. response' back to the Message Gateway. + +**Figure 8.3.4-3: Message delivery status report from Message Gateway (on behalf of Non-MSGin5G UE)** + +Pre-conditions: + +1. The sender of an MSGin5G message has asked for a message delivery status report. + +Procedures: + +The following procedure applies to the above figures 8.3.4-1, 8.3.4-2 and 8.3.4-3 with the exception that step 1 only applies to figure 8.3.4-1. + +1. The Application Client in the MSGin5G UE sends a request to the MSGin5G Client for invoking the MSGin5G Client to send an MSGin5G message delivery status report to a recipient. + +**Editor's note: Whether the APIs provided by the MSGin5G Client to the Application Client is to be specified in another clause of the TS is FFS.** + +2. As shown in figure 8.3.4-1 or 8.3.4-3, the MSGin5G Client or Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server and includes the IEs as listed in table 8.3.4-1, or as shown in figure 8.3.4-2, the Application Server sends an API request to the MSGin5G Server for sending an MSGin5G message, the API request includes the IEs as listed in table 8.3.4-1. + +**Table 8.3.4-1: Message delivery status report to MSGin5G Server** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID | M | The service identity of the sending MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the sending Application Server. | +| Recipient UE Service ID/AS Service ID (NOTE) | M | The service identity of the receiving MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the receiving Application Server. This is the sender of the message that this message delivery status report is for. | +| Message ID | M | Unique identifier of message delivery status report. The message ID of the MSGin5G message that is being acknowledged is included in this IE. | +| Failure Cause | O | The Failure Cause indicates the failure reason, if applicable. | +| Delivery Status | M | The delivery status description, including success or failure in delivery | +| NOTE: When the originator is an Application Server, (i.e. Originating AS Service ID is present), this IE shall be a UE Service ID. | | | + +3. The MSGin5G Server verifies that the sender is authorized to send the message delivery status report. +4. The MSGin5G Server may send a response to the originating entity if the message delivery status report is rejected and includes the IEs as listed in table 8.3.2-3 in the response. + +### 8.3.5 MSGin5G message delivery status report from the MSGin5G Server + +Figure 8.3.5-1 shows the procedure for the MSGin5G Server that forwards an MSGin5G message delivery status report to an MSGin5G UE. + +![Sequence diagram showing the message delivery status report flow from MSGin5G Server to MSGin5G UE, then to Application Client.](802707b774f2d2973b49cea2020e8453_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G Server + participant MSGin5G UE + subgraph MSGin5G UE + participant MSGin5G Client + participant Application Client + end + MSGin5G Server->>MSGin5G Client: 1. MSGin5G message delivery status report + MSGin5G Client-->>Application Client: 2. message delivery status report + +``` + +Sequence diagram showing the message delivery status report flow from MSGin5G Server to MSGin5G UE, then to Application Client. + +**Figure 8.3.5-1: Message delivery status report towards an MSGin5G UE** + +Figure 8.3.5-2 shows the procedure for the MSGin5G Server that forwards an MSGin5G message delivery status report to an Application Server. + +![Sequence diagram showing a message delivery status report from MSGin5G Server to Application Server.](b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg) + +``` +sequenceDiagram + participant MSGin5G Server + participant Application Server + Note right of MSGin5G Server: 1. MSGin5G message delivery status report + MSGin5G Server->>Application Server: 1. MSGin5G message delivery status report +``` + +A sequence diagram illustrating the interaction between an MSGin5G Server and an Application Server. The MSGin5G Server sends a message labeled "1. MSGin5G message delivery status report" to the Application Server. + +Sequence diagram showing a message delivery status report from MSGin5G Server to Application Server. + +**Figure 8.3.5-2: Message delivery status report towards an Application Server** + +Figure 8.3.5-3 shows the procedure for the MSGin5G Server that forwards an MSGin5G message delivery status report to a Legacy 3GPP Message Gateway or a Non-3GPP Message Gateway. + +![Sequence diagram showing an API request for a message delivery status report from MSGin5G Server to a Message Gateway.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +``` +sequenceDiagram + participant MSGin5G Server + participant Message Gateway + Note right of MSGin5G Server: 1. API request for MSGin5G message delivery status report + MSGin5G Server->>Message Gateway: 1. API request for MSGin5G message delivery status report +``` + +A sequence diagram illustrating the interaction between an MSGin5G Server and a Message Gateway. The MSGin5G Server sends a message labeled "1. API request for MSGin5G message delivery status report" to the Message Gateway. + +Sequence diagram showing an API request for a message delivery status report from MSGin5G Server to a Message Gateway. + +**Figure 8.3.5-3: Message delivery status report towards a Message Gateway** + +The following procedure applies to the above figures 8.3.5-1, 8.3.5-2 and 8.3.5-3 with the exception that step 2 only applies to figure 8.3.5-1. + +1. the MSGin5G Server sends the MSGin5G message delivery status report to the MSGin5G UE or Message Gateway and includes the IEs as listed in table 8.3.5-1, or as shown in figure 8.3.5-2 and figure 8.3.5-3, the MSGin5G Server sends an API request to the Application Server for sending an MSGin5G message, the API request includes the IEs as listed in table 8.3.5-1. + +**Table 8.3.5-1: Message delivery status report to MSGin5G Server** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID | M | The service identity of the sending MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the sending Application Server. | +| Recipient UE Service ID/AS Service ID (see NOTE) | M | The service identity of the receiving MSGin5G Client, Legacy 3GPP UE, Non-3GPP UE or the receiving Application Server. This is the sender of the message that this message delivery status report is for. | +| Message ID | M | Unique identifier of message delivery status report. The message ID of the MSGin5G message that is being acknowledged is included in this IE. | +| Failure Cause | O | The Failure Cause indicates the failure reason, if applicable. | +| Delivery Status | M | The delivery status description, including success or failure in delivery. | +| NOTE: When the originator is an Application Server, (i.e. Originating AS Service ID is present), this IE shall be a UE Service ID. | | | + +2. The MSGin5G Client sends the MSGin5G message delivery status report to Application Client. + +### 8.3.6 MSGin5G Store and Forward + +Figure 8.3.6-1 shows the procedure for providing store and forward services for MSGin5G message requests. + +This procedure applies when an MSGin5G message is received at the MSGin5G Server for delivery and the message cannot be delivered to the recipient UE; otherwise, the procedure detailed in clause 8.3.2 applies. + +Pre-conditions: + +1. The MSGin5G Client or Application Server has registered to the MSGin5G Server. +2. The MSGin5G Server has determined that the recipient UE is not available. + +NOTE: In addition to UE registration status, the MSGin5G Server can use e.g, UE reachability status monitoring specified in clause 8.9.2 or the recipient's Communication Availability information specified in clause 8.2 to determine whether the recipient is available and reachable for message delivery. + +![Sequence diagram illustrating the Store and forward procedure for MSGin5G. The diagram is divided into two phases: Phase 1 (Recipient UE not available) and Phase 2 (Recipient UE available). The participants are MSGin5G Client/Application Server, MSGin5G Server, and Recipient UE. In Phase 1, the Client sends a message (1) to the Server, which stores and forwards it (2). The Server then triggers the UE (3), and the UE responds (4). In Phase 2, the UE becomes available (5), the Server terminates the message (6), and the UE responds (7).](107c8e1abcb7033ad244e30e7a910045_img.jpg) + +``` + +sequenceDiagram + participant Client as MSGin5G Client/Application Server + participant Server as MSGin5G Server + participant UE as Recipient UE + + Note left of Client: Phase 1: Recipient UE not available + Client->>Server: 1. MSGin5G message origination procedure + Note right of Server: 2. Store and forward processing: store or discard + Note right of Server: 3. Device triggering as specified in clause 8.9.3 + Server-->>UE: 3. Device triggering as specified in clause 8.9.3 + UE-->>Server: 4. Message response + Note left of Client: Phase 2: Recipient UE available + Note right of UE: 5. Recipient UE becomes available + Note right of Server: 6. MSGin5G message termination procedure + UE-->>Server: 6. MSGin5G message termination procedure + Server-->>Client: 7. Message response + +``` + +Sequence diagram illustrating the Store and forward procedure for MSGin5G. The diagram is divided into two phases: Phase 1 (Recipient UE not available) and Phase 2 (Recipient UE available). The participants are MSGin5G Client/Application Server, MSGin5G Server, and Recipient UE. In Phase 1, the Client sends a message (1) to the Server, which stores and forwards it (2). The Server then triggers the UE (3), and the UE responds (4). In Phase 2, the UE becomes available (5), the Server terminates the message (6), and the UE responds (7). + +**Figure 8.3.6-1: Store and forward procedure** + +1. MSGin5G message origination handling, see steps 1-3 in clause 8.3.2. The value of the Store and forward flag IE (see Table 8.3.2-1) in the MSGin5G message indicates that store and forward services are requested by the sender. +2. The MSGin5G Server checks the registration information of the recipient UE. If the Store and forward option IE (see Table 8.2.1-3) indicates that the recipient UE opts out of store and forward services, the message is discarded and the procedure proceeds with step 4 and ends with step 4. If the Store and forward flag IE (see Table 8.3.2-1) in the received message indicates that store and forward services are not requested by the sender, the message is discarded and the procedure proceeds with step 4 and ends with step 4. +If store and forward processing is required, the MSGin5G Server uses the Application specific store and forward information IE (see Table 8.3.2-2) to determine storage and forwarding. +3. Before the Message expiration time is expired, the MSGin5G Server may trigger the Recipient UE based on the MSGin5G device triggering procedure in clause 8.9.3. +4. The MSGin5G Server may send a message response as defined in table 8.3.2-3 which includes store and forward status information in the Delivery Status IE, e.g., that the delivery had been deferred, or has been discarded. + +5. The recipient UE becomes available. +6. When the recipient UE becomes available, the MSGin5G Server attempts delivery of the request using the procedure specified in clause 8.3.3. + +If the UE does not become available prior to the expiration time, the MSGin5G Server attempts delivery of the request at the message expiration time and the stored message is discarded or apply local implementation afterwards. + +7. The MSGin5G Server may send a message response as defined in table 8.3.2-3 which includes store and forward status information in the Delivery Status IE, e.g., that the message was discarded. + +## 8.4 Message Aggregation + +### 8.4.1 General + +Based on maximum segment size allowed to transmit over available transport, the MSGin5G Service can optimize communications by aggregating one or more messages towards the same target. The target may be an UE, an Application Server, a Broadcast Area, an MSGin5G Group or a Messaging Topic. + +The following pre-conditions apply for message aggregation: + +1. The recipient UE(s) support an MSGin5G Client or the (Legacy-3GPP and non-3GPP) Message Gateway supports the MSGin5G Client capability. +2. The MSGin5G Client 1 and MSGin5G Client 2 are registered with the MSGin5G Server, or an Application Server has established a secured communication with the MSGin5G Server. + +### 8.4.2 Message Aggregation at MSGin5G Client + +Figure 8.4.2-1 shows the procedure for an MSGin5G Client aggregating a set of Point-to-Point messages each carrying small amounts of data. All of the Point-to-Point messages to be aggregated are targeted to the same UE. + +NOTE 1: Aggregation of multiple messages can also be done with the Application Client; in this case it is implementation specific and out of the scope of the current specification. + +![Sequence diagram showing MSGin5G UE 1 aggregating messages towards target MSGin5G UE 2 via an MSGin5G Server.](3ce04f1c7128814978c6b34d654a25cc_img.jpg) + +``` +sequenceDiagram + participant AC1 as Application Client(s) + participant MC1 as MSGin5G Client(s) + participant Server as MSGin5G Server + participant MC2 as MSGin5G Client(s) + participant AC2 as Application Client(s) + + Note left of MC1: MSGin5G UE 1 + Note right of MC2: MSGin5G UE 2 + + AC1->>MC1: 1. request + Note over MC1: 2. Determines to aggregate messages + MC1->>Server: 3. Aggregated message request + Note over Server: 4. Authorization + Server-->>MC1: 5. Aggregated message response + Server->>MC2: 6. Aggregated message request + Note over MC2: 7a. Message delivery + Note over MC2: 8. Request to message delivery report + MC2-->>Server: 8. MSGin5G message delivery status report + Server-->>MC1: 8. MSGin5G message delivery status report + MC1-->>AC1: 8. Delivery status report +``` + +The sequence diagram illustrates the interaction for message aggregation. It starts with an Application Client(s) in MSGin5G UE 1 sending a 'request' to its MSGin5G Client(s). The client then 'Determines to aggregate messages' and sends an 'Aggregated message request' to the MSGin5G Server. The server performs 'Authorization' and returns an 'Aggregated message response'. Next, the server sends an 'Aggregated message request' to the MSGin5G Client(s) in MSGin5G UE 2. The client in UE 2 performs 'Message delivery' and sends a 'Request to message delivery report' to the server. The server returns an 'MSGin5G message delivery status report' to the client in UE 1, which then sends a 'Delivery status report' to its Application Client(s). + +Sequence diagram showing MSGin5G UE 1 aggregating messages towards target MSGin5G UE 2 via an MSGin5G Server. + +**Figure 8.4.2-1: MSGin5G UE aggregates messages towards target MSGin5G UE** + +Figure 8.4.2-2 shows the procedure for an MSGin5G Client aggregating a set of Point-to-AS messages each carrying small amounts of data. All of the Point-to-AS messages to be aggregated are sent to same Application Server. + +![Sequence diagram showing MSGin5G UE aggregating messages towards target Application Server.](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) + +``` +sequenceDiagram + participant Application Client(s) + participant MSGin5G Client(s) + participant MSGin5G Server + participant Application Server + + Note left of MSGin5G Client(s): MSGin5G UE 1 + + Application Client(s)->>MSGin5G Client(s): 1. request + MSGin5G Client(s)->>MSGin5G Server: 3. Aggregated message request + MSGin5G Server->>Application Server: 6. Aggregated message request + Application Server-->>MSGin5G Server: 8. Request to message delivery report + MSGin5G Server-->>MSGin5G Client(s): 8. MSGin5G message delivery status report + MSGin5G Client(s)->>Application Client(s): 8. Delivery status report +``` + +The sequence diagram illustrates the interaction for message aggregation. It begins with a 'request' (1.) from Application Client(s) to MSGin5G Client(s) within MSGin5G UE 1. The MSGin5G Client(s) then 'Determines to aggregate messages' (2.). Next, an 'Aggregated message request' (3.) is sent from MSGin5G Client(s) to MSGin5G Server. The server performs 'Authorization' (4.). A response (5.) is sent from MSGin5G Server back to MSGin5G Client(s). The MSGin5G Server then sends an 'Aggregated message request' (6.) to the Application Server. The Application Server sends a 'Request to message delivery report' (8.) back to the MSGin5G Server. The MSGin5G Server sends an 'MSGin5G message delivery status report' (8.) to the MSGin5G Client(s), which finally sends a 'Delivery status report' (8.) to the Application Client(s). + +Sequence diagram showing MSGin5G UE aggregating messages towards target Application Server. + +**Figure 8.4.2-2: MSGin5G UE aggregates messages towards target Application Server** + +Figure 8.4.2-3 shows the procedure for an MSGin5G Client aggregating a set of Point-to-Point messages each carrying small amounts of data. All of the Point-to-Point messages to be aggregated are sent to same recipient Non-MSGin5G UE. + +![Sequence diagram showing MSGin5G UE 1 aggregating messages towards a target Non-MSGin5G UE via a MSGin5G Server and a Message Gateway.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) + +``` +sequenceDiagram + participant AC as Application Client(s) + participant MC as MSGin5G Client(s) + participant MS as MSGin5G Server + participant MG as Message Gateway + participant NMUE as Non-MSGin5G UE + + Note left of AC: MSGin5G UE 1 + + AC->>MC: 1. request + Note right of MC: 2. Determines to aggregate messages + MC->>MS: 3. Aggregated message request + Note right of MS: 4. Authentication and authorization + MS-->>MC: 5. Aggregated message response + MS->>MG: 6. Aggregated message request + Note right of MG: 7b. Non-MSGin5G Message delivery + NMUE-->>MG: 8b. Request to message delivery report + MG-->>MS: 8. MSGin5G message delivery status report + MS-->>MC: 8. MSGin5G message delivery status report + MC-->>AC: 8. Delivery status report +``` + +The sequence diagram illustrates the interaction for aggregating messages. It starts with an Application Client(s) sending a request to the MSGin5G Client(s) within MSGin5G UE 1. The client then determines to aggregate messages and sends an aggregated message request to the MSGin5G Server. The server performs authentication and authorization, returning an aggregated message response. The server then sends an aggregated message request to the Message Gateway. The gateway performs non-MSGin5G message delivery to the Non-MSGin5G UE, which responds with a request to message delivery report. The gateway sends the MSGin5G message delivery status report back to the server, which in turn sends it to the client, which finally sends the delivery status report to the application client. + +Sequence diagram showing MSGin5G UE 1 aggregating messages towards a target Non-MSGin5G UE via a MSGin5G Server and a Message Gateway. + +**Figure 8.4.2-3: MSGin5G UE aggregates messages towards target Non-MSGin5G UE** + +Figure 8.4.2-4 shows the procedure for an MSGin5G Client sends aggregated message to a MSGin5G group. All of the messages to be aggregated are sent to same MSGin5G Group. + +![Sequence diagram for Figure 8.4.2-4 showing message aggregation from UE1 to multiple targets.](27788c2a26d9641e68232a4eff1299b9_img.jpg) + +This sequence diagram illustrates the procedure for an MSGin5G UE (UE1) to send aggregated messages towards a target MSGin5G Group. The participants involved are UE1 (containing Application Client 1 and MSGin5G Client 1), MSGin5G Server, Application Server, UE2 (containing MSGin5G Client 2 and Application Client 2), Message Gateway, and Non-MSGin5G UE. The process begins with steps 1-4 as specified in clause 8.4.2. UE1 then initiates a message exchange with the Application Server (step 4a). The Application Server returns an aggregated message response (step 5) to UE1. UE1 then sends an aggregated message request to the MSGin5G Server (step 6). The MSGin5G Server delivers the message to MSGin5G Client 2 within UE2 (step 7a) and also sends an aggregated message request to the Non-MSGin5G Client (step 6). The Message Gateway then delivers the message to the Non-MSGin5G UE (step 7b). Finally, a message delivery status report is sent (step 8). + +Sequence diagram for Figure 8.4.2-4 showing message aggregation from UE1 to multiple targets. + +**Figure 8.4.2-4: MSGin5G UE sends aggregated messages towards target MSGin5G Group** + +Figure 8.4.2-5 shows the procedure for an MSGin5G Client sends aggregated message based on Messaging Topic. All the messages to be aggregated have the same Messaging Topic. + +![Sequence diagram for Figure 8.4.2-5 showing message aggregation from UE1 based on a messaging topic.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +This sequence diagram illustrates the procedure for an MSGin5G Client (UE1) to send aggregated messages towards a target MSGin5G Group based on a messaging topic. The participants and steps are identical to Figure 8.4.2-4, but the initial aggregation logic is based on the messaging topic. The sequence starts with steps 1-4 (clause 8.4.2). UE1 sends an aggregated message response (step 5) to the Application Server. The MSGin5G Server then sends an aggregated message request to the MSGin5G Client (step 6). The MSGin5G Client 2 delivers the message to Application Client 2 (step 7a). The MSGin5G Server also sends an aggregated message request to the Non-MSGin5G Client (step 6), which is then delivered by the Message Gateway to the Non-MSGin5G UE (step 7b). A message delivery status report is sent (step 8). + +Sequence diagram for Figure 8.4.2-5 showing message aggregation from UE1 based on a messaging topic. + +**Figure 8.4.2-5: MSGin5G UE sends aggregated messages towards target MSGin5G Group** + +Figure 8.4.2-6 shows the procedure for an MSGin5G Client aggregating a set of Broadcast messages each carrying small amounts of data. All of the Broadcast messages to be aggregated are sent to same Broadcast Area. + +![Sequence diagram for MSGin5G UE aggregates messages towards target Broadcast Area. Lifelines: MSGin5G UE 1 (Application Client(s), MSGin5G Client(s)), MSGin5G Server, Broadcast Message Gateway, CBCF, UEs in Broadcast Area. The sequence shows a request from the Application Client to the MSGin5G Client, which then determines to aggregate messages and sends an aggregated message request to the MSGin5G Server. The server authenticates and authorizes, then sends an aggregated message response to the client. The client then sends an aggregated message request to the Broadcast Message Gateway, which delivers the message to the CBCF. The CBCF broadcasts the message to the UEs in the Broadcast Area. Finally, the Broadcast Message Gateway sends an MSGin5G message delivery status report to the MSGin5G Server, which in turn sends a delivery status report to the Application Client.](e2b7490a3455c66c85db12872c78fcc3_img.jpg) + +``` + +sequenceDiagram + participant UE1 as MSGin5G UE 1 + participant MSGin5G Server + participant BMG as Broadcast Message Gateway + participant CBCF + participant UEs as UEs in Broadcast Area + + Note left of UE1: Application Client(s) | MSGin5G Client(s) + UE1->>MSGin5G Server: 1. request + Note right of UE1: 2. Determines to aggregate messages + UE1->>MSGin5G Server: 3. Aggregated message request + Note right of MSGin5G Server: 4. Authentication and authorization + MSGin5G Server-->>UE1: 5. Aggregated message response + MSGin5G Server->>BMG: 6. Aggregated message request + Note right of BMG: 7c. Broadcast message Gateway delivers the message to the CBCF, and CBCF broadcasts the message as specified in 3GPP TS 23.041 [14] + BMG-->>MSGin5G Server: 8. MSGin5G message delivery status report + MSGin5G Server-->>UE1: 8. Delivery status report + +``` + +Sequence diagram for MSGin5G UE aggregates messages towards target Broadcast Area. Lifelines: MSGin5G UE 1 (Application Client(s), MSGin5G Client(s)), MSGin5G Server, Broadcast Message Gateway, CBCF, UEs in Broadcast Area. The sequence shows a request from the Application Client to the MSGin5G Client, which then determines to aggregate messages and sends an aggregated message request to the MSGin5G Server. The server authenticates and authorizes, then sends an aggregated message response to the client. The client then sends an aggregated message request to the Broadcast Message Gateway, which delivers the message to the CBCF. The CBCF broadcasts the message to the UEs in the Broadcast Area. Finally, the Broadcast Message Gateway sends an MSGin5G message delivery status report to the MSGin5G Server, which in turn sends a delivery status report to the Application Client. + +**Figure 8.4.2-6: MSGin5G UE aggregates messages towards target Broadcast Area** + +The following procedure applies to the above figures 8.4.2-1 to 8.4.2-6 with the exception that: + +- step 4a only applies to figure 8.4.2-4 + - step 7a only applies to figure 8.4.2-1 and figure 8.4.2-4; + - step 7b only applies to figure 8.4.2-3. and figure 8.4.2-4; and + - step 7c only applies to figure 8.4.2-6. +- Application Client(s) initiates a request to the MSGin5G Client 1 to send a message to another target. The target may be an MSGin5G UE, a Non-MSGin5G UE, an Application Server, a MSGin5G group, or a broadcast area. the Application Client(s) may also initiate a request to the MSGin5G Client 1 to send a message which is to be delivered based on Messaging Topic. + - The MSGin5G Client 1 checks if aggregation is allowed for this message as per the service configuration. The MSGin5G Client 1 also checks the message data size and the priority level to determine if the received message can be aggregated. For example, MSGin5G Client 1 finds that the message has a small payload size when compared to the maximum segment size that can be transmitted over available transport and is not high priority message (i.e. the value of Priority type included in the message is not "High"), the MSGin5G Client 1 may aggregate this message. The MSGin5G Client 1 may continue aggregating messages until an optimal segment size is reached before sending the aggregated message. When the aggregation is finished, e.g. the optimal segment size is reached or other conditions such as waiting time configured by service provider is fulfilled, the MSGin5G Client sends the aggregated message as per scheduling policy towards a selected target. + +NOTE 2: The condition(s) when the aggregation is needed to be finished is implementation specific. + +NOTE 3: The configuration of whether aggregation is allowed for MSGin5G messages and how the MSGin5G Client 1 uses information such as individual message priority, maximum time to wait, etc for aggregating and sending is out of scope of the present document. + +NOTE 4: The maximum segment size that can be transmitted over available transport is configured to the MSGin5G Client 1 in the MSGin5G Service specific information IE as specified in Table 8.1.2-2. + +- The MSGin5G Client 1 aggregates multiple MSGin5G message requests intended for a selected target and sends the Aggregated message request containing the information elements specified in Table 8.4.2-1 and Table 8.4.2-2 according to scheduling policy towards the MSGin5G Server. + +**Table 8.4.2-1: Aggregated message request (MSGin5G Client to MSGin5G Server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originator UE Service ID | M | The service identity of the sending MSGin5G Client. | +| Recipient UE Service ID/AS Service ID (see NOTE) | O | The service identity of the receiving MSGin5G Client or the receiving Application Server. | +| Group Service ID (see NOTE) | O | The service identifier of the target MSGin5G Group. | +| Messaging Topic (see NOTE) | O | Indicates which Messaging Topic this message is related to. | +| Broadcast Area ID (see NOTE) | O | The service identifier of the Broadcast Area where the message needs to be broadcast. | +| Message ID | M | Unique identifier of this aggregated message | +| Number of individual messages | M | Indicates total number of messages which are aggregated into this message | +| List of individual messages | M | Each element in this list contains information elements as specified in Table 8.4.2-2. | +| Store and forward flag | O | An indicator of whether store and forward services are requested for this aggregated message. The store and forward services can be applied to the aggregated message only if all messages in this aggregated message can be store and forwarded. | +| Store and forward parameters | O | Parameters used by MSGin5G Server for providing store and forward services, as detailed in table 8.3.2-2. This IE shall be included only if the value of the Store and forward flag IE indicates that store and forward services are requested. | +| NOTE Only one of these IEs shall be included to represent the type of message request. | | | + +**Table 8.4.2-2: Individual message data** + +| Information element | Status | Description | +|--------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------| +| Individual Message ID | M | Unique identifier of this individual message. | +| Application ID | O | Identifies the application for which the payload is intended. | +| Delivery status required | O | Indicates if delivery acknowledgement from the recipient is requested. | +| Payload | M | Payload of the message | +| Priority type | O | Application priority level requested for this message as specified in Table 8.3.2-1 except that the value of this IE should not be High. | + +NOTE 5: Total size of Aggregated message request is less than or equal to maximum segment size allowed to be transmitted over available transport. + +- MSGin5G Server checks whether the MSGin5G Client 1 is authorized to send the Aggregated message request. + - The MSGin5G Server performs the necessary message exchanging procedure with the Application Server as per clause 8.7.4.2. +- The MSGin5G Server sends the Aggregated message response to the MSGin5G Client 1 in the cases listed below. The information elements defined in Table 8.4.2-3 shall be included in the response.: + - MSGin5G Client 1 is not authorized to send Aggregated message request; or + - the Aggregated message request is not valid; or + - if MSGin5G Client 1 is authorized but the message is stored for deferred delivery. + +**Table 8.4.2-3: Aggregated message response (MSGin5G Server to MSGin5G Client)** + +| Information element | Status | Description | +|----------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Original MSGin5G Client ID | M | The identity of the MSGin5G Client sending the original message. | +| Message ID | M | Unique identifier of the original aggregated message | +| Delivery Status | O | Indicates if delivery is a failure, or if the message is stored for deferred delivery. | +| Failure Cause | O | This IE contains the failure reason, e.g. the originator is not authorized to send a message request or one of the multiple messages aggregated has an issue, may be included in this IE. | + +6. If MSGin5G Client 1 is authorized to send an Aggregated message request, the MSGin5G Server sends the Aggregated message request towards the selected target as specified in clause 8.3.3. If the aggregated message is sent to a recipient whose supported message segment size is smaller than the aggregated message, the MSGin5G Server should remove the last individual message in the List of individual messages element from the aggregated message until the aggregated message is smaller than the maximum segment size that can be transmitted over available transport. The MSGin5G messages removed from the aggregated message may be sent individually or aggregated again by the MSGin5G Server according to service configuration. + +7a. If the recipient of the aggregated message is MSGin5G UE 2, the MSGin5G Client 2 in the MSGin5G UE 2 splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the recipient Application Client(s). + +NOTE 6: The delivery between MSGin5G Client and Application Client is out of scope of the present document. + +7b. If the recipient of the aggregated message is a Message Gateway on behalf of Non-MSGin5G UE, the Message Gateway splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the Non-MSGin5G UE via Non-MSGin5G message delivery. + +NOTE 7: The Non-MSGin5G message delivery is out of scope of this document. + +7c. If the aggregated message needs to be delivered in the Broadcast Area, the Broadcast Message Gateway splits the received Aggregated message request into multiple individual MSGin5G message requests. The Broadcast Message Gateway broadcasts each individual MSGin5G message request to the MSGin5G UEs in the Broadcast Area, or broadcasts the content of each individual MSGin5G message request to the non-MSGin5G UEs in the Broadcast Area via CBCF. The procedures on CBCF are specified in 3GPP TS 23.041 [14]. + +8. The recipient MSGin5G Client/ Application Server/ Message Gateway may initiate sending a message delivery status report, if requested in the original message that is received as in Step 7a (for MSGin5G UE), step 7b (for Non-MSGin5G UE) or Step 6 (for Application Server). MSGin5G Client 2/ Application Server/ Message Gateway sends the message delivery status report towards the MSGin5G Client on MSGin5G UE 1 via MSGin5G Server. + +NOTE 8: The message delivery status reports can also be aggregated into a single message. + +### 8.4.3 Message aggregation at MSGin5G Server + +Figure 8.4.3-1 shows the procedure for the MSGin5G Server aggregating a set of Application-to-Point messages targeted to the same recipient UE, set of group messages for the same MSGin5G group, or a set of messages delivered based on Messaging Topic for the same Messaging Topic, or a set of messages broadcasted to the same Service Area, each carrying a small amount data targeted towards the same target MSGin5G UE(s). + +NOTE 1: Aggregation of multiple messages can also be done at the Application Server; in this case it is implementation specific and out of the scope of the current specification. + +![Sequence diagram for Figure 8.4.3-1: MSGin5G Server aggregates messages towards target MSGin5G UE. The diagram shows four lifelines: MSGin5G UE 1 (containing Application Client(s) and MSGin5G Client 1), MSGin5G Server, and Application Server. The sequence of messages is: 1. Request from Application Server to MSGin5G Server; 2. Internal processing in MSGin5G Server to determine aggregation; 3. Aggregated MSGin5G message request from MSGin5G Server to MSGin5G Client 1; 4a. Message delivery from MSGin5G Client 1 to Application Client(s).](24ca460ee3381aee781887e9e586ec67_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server + participant MS as MSGin5G Server + subgraph UE1 [MSGin5G UE 1] + direction TB + AC[Application Client(s)] + MC1[MSGin5G Client 1] + end + Note right of MS: 2. Determines to aggregate messages with small data that are of not high priority + AS->>MS: 1. Request + MS->>MC1: 3. Aggregated MSGin5G message request + MC1-->>AC: 4a. Message delivery + +``` + +Sequence diagram for Figure 8.4.3-1: MSGin5G Server aggregates messages towards target MSGin5G UE. The diagram shows four lifelines: MSGin5G UE 1 (containing Application Client(s) and MSGin5G Client 1), MSGin5G Server, and Application Server. The sequence of messages is: 1. Request from Application Server to MSGin5G Server; 2. Internal processing in MSGin5G Server to determine aggregation; 3. Aggregated MSGin5G message request from MSGin5G Server to MSGin5G Client 1; 4a. Message delivery from MSGin5G Client 1 to Application Client(s). + +**Figure 8.4.3-1: MSGin5G Server aggregates messages towards target MSGin5G UE** + +Figure 8.4.3-2 shows the procedure for MSGin5G Server aggregating a set of Application-to-Point messages targeted to the same recipient UE, or a set of group messages for the same MSGin5G group, or a set of messages delivered based on Messaging Topic for the same Messaging Topic, or a set of messages broadcasted to the same Service Area, each carrying a small amount data targeted towards the same target Non-MSGin5G UE(s). + +![Sequence diagram for Figure 8.4.3-2: MSGin5G Server aggregates messages towards target Non-MSGin5G UE. The diagram shows four lifelines: Non-MSGin5G UE, Message Gateway, MSGin5G Server, and Application Server. The sequence of messages is: 1. Request from Application Server to MSGin5G Server; 2. Internal processing in MSGin5G Server to determine aggregation; 3. Aggregated MSGin5G message request from MSGin5G Server to Message Gateway; 4b. Non-MSGin5G message delivery from Message Gateway to Non-MSGin5G UE.](38a51baf4d5b8857d162e5d9a0645269_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server + participant MS as MSGin5G Server + participant MG as Message Gateway + participant NMEU as Non-MSGin5G UE + Note right of MS: 2. Determines to aggregate messages with small data that are of not high priority + AS->>MS: 1. Request + MS->>MG: 3. Aggregated MSGin5G message request + MG-->>NMEU: 4b. Non-MSGin5G message delivery + +``` + +Sequence diagram for Figure 8.4.3-2: MSGin5G Server aggregates messages towards target Non-MSGin5G UE. The diagram shows four lifelines: Non-MSGin5G UE, Message Gateway, MSGin5G Server, and Application Server. The sequence of messages is: 1. Request from Application Server to MSGin5G Server; 2. Internal processing in MSGin5G Server to determine aggregation; 3. Aggregated MSGin5G message request from MSGin5G Server to Message Gateway; 4b. Non-MSGin5G message delivery from Message Gateway to Non-MSGin5G UE. + +**Figure 8.4.3-2: MSGin5G Server aggregates messages towards target Non-MSGin5G UE** + +Figure 8.4.3-3 shows the procedure for MSGin5G Server aggregating Broadcast messages, each carrying a small amount data targeted towards the target Broadcast Area. + +![Sequence diagram for Figure 8.4.3-3 showing the interaction between Non-MSGin5G UE, CBCF, Broadcast Message Gateway, MSGin5G Server, and Application Server. The sequence starts with a Request from the Application Server to the MSGin5G Server. The MSGin5G Server then determines to aggregate messages with small data that are of not high priority. It sends an Aggregated MSGin5G message request to the Broadcast Message Gateway. Finally, the Broadcast Message Gateway delivers the message to the CBCF, and the CBCF broadcasts the message as specified in 3GPP TS 23.041 [14] to the Non-MSGin5G UE.](7f7211748473542096717109ebe5a9d6_img.jpg) + +``` + +sequenceDiagram + participant Application Server + participant MSGin5G Server + participant Broadcast Message Gateway + participant CBCF + participant Non-MSGin5G UE + + Note right of MSGin5G Server: 2. Determines to aggregate messages with small data that are of not high priority + + Application Server->>MSGin5G Server: 1. Request + MSGin5G Server->>Broadcast Message Gateway: 3. Aggregated MSGin5G message request + Broadcast Message Gateway->>CBCF: 4c. Broadcast message Gateway delivers the message to the CBCF, and CBCF broadcasts the message as specified in 3GPP TS 23.041 [14] + +``` + +Sequence diagram for Figure 8.4.3-3 showing the interaction between Non-MSGin5G UE, CBCF, Broadcast Message Gateway, MSGin5G Server, and Application Server. The sequence starts with a Request from the Application Server to the MSGin5G Server. The MSGin5G Server then determines to aggregate messages with small data that are of not high priority. It sends an Aggregated MSGin5G message request to the Broadcast Message Gateway. Finally, the Broadcast Message Gateway delivers the message to the CBCF, and the CBCF broadcasts the message as specified in 3GPP TS 23.041 [14] to the Non-MSGin5G UE. + +**Figure 8.4.3-3: MSGin5G Server delivers aggregated message towards Non-MSGin5G UEs in the Broadcast Area** + +The following procedure applies to the above figures 8.4.3-1, 8.4.3-2 and 8.4.3-3 with the exception that step 4a only applies to figure 8.4.3-1, step 4b only applies to figure 8.4.3-2 and step 4c only applies to figure 8.4.3-3. + +1. The Application Server initiates to send a set of Application-to-Point messages targeted to the same recipient UE, or a set of group messages for the same MSGin5G group, or a set of messages delivered based on Messaging Topic for the same Messaging Topic, or a set of messages broadcasted to the same Service Area, and sends the request to MSGin5G Server. The MSGin5G Server executes the MSGin5G messages origination procedure for each message as specified in clause 8.3.2. +2. The MSGin5G Server checks the message data size and the priority level of each message to determine if these messages, targeted to the same service end-point and of the same message type (i.e., either a set of Application-to-Point messages targeted to the same recipient UE, a set of group messages for the same MSGin5G group, a set of messages delivered based on Messaging Topic for the same Messaging Topic or a set of messages broadcasted to the same Service Area,), can be aggregated. For example, the MSGin5G Server finds that the messages have small payload size when compared to the maximum segment size that can be transmitted over available transport and are not high priority messages (i.e. the value of Priority type included in the message is not "High"), which could be sent as per scheduling policy towards a selected target. + +NOTE 2: MSGin5G Server decides to continue aggregating messages until optimal use of segment size before sending message towards MSGin5G Client 1. + +3. The MSGin5G Server aggregates multiple MSGin5G message requests intended for the target UE. The Aggregated message request contain the information elements as defined in Table 8.4.3-1 and Table 8.4.2-2. The MSGin5G Server delivers the Aggregated message request by using the MSGin5G messages termination procedure specified in clause 8.3.3. + +**Table 8.4.3-1: Aggregated message request (MSGin5G Server to MSGin5G Client)** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating AS Service ID | M | The service identity of the sending Application Server. | +| Recipient UE Service ID | O | The service identity of the receiving MSGin5G Client. This IE is Mandatory for all type of message request except the broadcast message. | +| Group Service ID (see NOTE) | O | The service identifier of the target MSGin5G Group. This IE should be present if the aggregated message is a set of group messages for the same MSGin5G group. | +| Messaging Topic (see NOTE) | O | Indicates which Messaging Topic this message is related to. This IE should be present if the aggregated message is a set of message delivered based on Messaging Topic for the same Messaging Topic | +| Broadcast Area ID (see NOTE) | O | The identifier of the Service Area where the message needs to be broadcast. | +| Message ID | M | Unique identifier of this message | +| Number of individual messages | M | Indicates total number of messages which are aggregated into single message | +| List of Individual messages | M | Each element in this list contains information as specified in Table 8.3.3-1 | +| NOTE: Only one of these IEs shall be included to represent the type of message request. | | | + +NOTE 3: Total size of Aggregated message request is less than or equal to maximum segment size allowed to transmit over available transport. + +4a. If the recipient of the aggregated message is MSGin5G UE, the MSGin5G Client 1 residing on the MSGin5G UE splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the recipient Application Client(s). + +NOTE 4: The delivery between MSGin5G Client and Application Client is out of scope of the present document. + +4b. If the recipient of the aggregated message is the Message Gateway on behalf of Non-MSGin5G UE, the Message Gateway splits the received Aggregated message request into multiple individual MSGin5G message requests. The content of each MSGin5G message is delivered to the Non-MSGin5G UE via Non-MSGin5G message delivery. + +NOTE 5: The Non-MSGin5G message delivery is out of scope of this document. + +NOTE 6: The MSGin5G Server may aggregate messages towards the target UE if it receives messages from multiple MSGin5G UEs (instead of Application Server). + +4c. If the recipient of the aggregated message is a Broadcast Area, the Broadcast Message Gateway split the received aggregated message request into multiple individual MSGin5G message requests. The Broadcast Message Gateway may either broadcast each individual MSGin5G message request to the MSGin5G UEs in the Broadcast Area, or broadcast the content of each individual MSGin5G message request to the non-MSGin5G UEs in the Broadcast Area, via CBCF. The procedures on CBCF are specified in 3GPP TS 23.041 [14]. + +## 8.5 MSGin5G Message Segmentation and Reassembly + +### 8.5.1 General + +This clause introduces MSGin5G message segmentation and reassembly functionality to the MSGin5G Service. + +Segmentation and reassembly operations are performed by the MSGin5G Server, or by the MSGin5G Client, or by the Message Gateway, depending on the communication models. For Application-to-Point use case, the MSGin5G Server performs MSGin5G message segmentation while the MSGin5G Client performs MSGin5G message reassembly. For Point-to-Application use case, the MSGin5G Client performs MSGin5G message segmentation while the MSGin5G Server performs MSGin5G message reassembly. For the Point-to-Point use case the MSGin5G Client performs both the segmentation and the reassembly. + +The Message Gateway performs segmentation and reassembly if the sender or the recipient is a non-MSGin5G UE. + +The Aggregated message request should not be segmented. If aggregated message is sent to a recipient whose supported message segment size is smaller than the aggregated message, the MSGin5G Server should handle the Aggregated message as specified in clause 8.4.2. + +The maximum segmentation size of MSGin5G message is 2048 bytes and can be configurable. The supported maximum segment size for an MSGin5G UE may be provided in the MSGin5G UE registration request. + +#### 8.5.2 Application-to-Point Segmentation and Reassembly + +Figure 8.5.2-1 shows the MSGin5G message segmentation and reassembly procedure for Application-to-Point MSGin5G message use cases (e.g. AOMT). + +NOTE 1: Segmentation can also be done by the Application Server, in this case the Application Server will create a segmented message and send it as a regular MSGin5G message. In this case it is implementation specific and out of the scope of the current specification. + +Pre-conditions: + +1. A UE hosts an MSGin5G Client and an Application Client. +2. The MSGin5G Client has registered with the MSGin5G Server. +3. An Application Server needs to deliver application data to the Application Client on the UE and the size of the application data exceeds the maximum allowed packet size (e.g. due to limitation by the UE's access network transport). +4. Both the Application Server and the MSGin5G UE are hosted by the same MSGin5G Server. + +![Sequence diagram illustrating Application-to-Point MSGin5G Message Segmentation and Reassembly. The diagram shows the interaction between an Application Client(s) and MSGin5G Client (part of MSGin5G UE), an MSGin5G Server, and an Application Server(s). The process involves: 1. Application Server sending a large payload message to the MSGin5G Server; 2. MSGin5G message segmentation; 3. Segmented messages being delivered to the MSGin5G Client; 4. MSGin5G message reassembly; 5. Message received confirmation from the MSGin5G Client to the MSGin5G Server; 6. Message delivery from the MSGin5G Client to the Application Client(s).](8ab30dbff406204a68c59ae7c1b77413_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server(s) + participant MS as MSGin5G Server + participant UE as MSGin5G UE + Note right of AS: 1. Application Server sends message with large payload to MSGin5G Server as specified in clause 8.3.2 + Note right of MS: 2. MSGin5G message segmentation + Note right of MS: 3. Segmented messages delivered + Note right of UE: 4. MSGin5G message reassembly + UE->>MS: 5. Message received confirmation + Note left of UE: 6. Message delivery + +``` + +Sequence diagram illustrating Application-to-Point MSGin5G Message Segmentation and Reassembly. The diagram shows the interaction between an Application Client(s) and MSGin5G Client (part of MSGin5G UE), an MSGin5G Server, and an Application Server(s). The process involves: 1. Application Server sending a large payload message to the MSGin5G Server; 2. MSGin5G message segmentation; 3. Segmented messages being delivered to the MSGin5G Client; 4. MSGin5G message reassembly; 5. Message received confirmation from the MSGin5G Client to the MSGin5G Server; 6. Message delivery from the MSGin5G Client to the Application Client(s). + +**Figure 8.5.2-1: Application-to-Point MSGin5G Message Segmentation and Reassembly** + +1. An Application Server sends a message to an MSGin5G Server that targets an Application Client on a UE. +2. The MSGin5G Server compares the size of the received message to the maximum allowed packet size that is supported for message delivery to the targeted UE and detects that the size exceeds the limit. As a result, the MSGin5G Server segments the received message into a set of segmented messages. Within each segmented message, the information elements defined in Table 8.3.3-1 are included to enable the MSGin5G Client on the targeted UE to reassemble the segmented messages, with following clarifications. + - a) The MSGin5G message request includes following information elements from Table 8.3.3-1: + - i) Originating AS Service ID, Recipient UE Service ID, Message ID, Segmentation Set Identifier and Message segment number in each segmented message + - ii) Delivery status required and Total number of message segments, only if it is the first segment of the message + - iii) Last Segment Flag, only if it is the last segment of the message. +3. The MSGin5G Server sends each segmented message to the targeted UE. If any segment is not received within the expected time (based on configuration) then proceed to step 4. +4. If MSGin5G Client has received all segments (determined based on First segment and Last Segment), the MSGin5G Client reassembles all the segmented messages into a single MSGin5G message based on the information elements mentioned in step 2. If not all segments are received within expected time, then the MSGin5G Client recovers the segments as described in clause 8.5.6 MSGin5G message segment recovery procedure, before continuing with rest of the steps. + +NOTE 2: When no further segments are received within expected time and if both first segment and last segment are missing, recovery can be initiated as described in clause 8.5.6 MSGin5G message segment recovery procedure for recovering the first segment and then for remaining segments. + +- The MSGin5G Client sends Message received confirmation request to the MSGin5G Server. The information elements defined in Table 8.5.2-2 are included in the request. The result information element will contain "success" if the reassembly of the segments is success. Otherwise, the result information element will contain "failure". + +**Table 8.5.2-2: Message Received Confirmation Request Information Elements** + +| Information element | Status | Description | +|-----------------------------|--------|----------------------------------------------------------| +| Segmentation Set Identifier | M | The Segmentation Set Identifier as received in segments. | +| Result | M | Indicates the "success" or "failure" | + +- If reassembly of segments is successful, the MSGin5G Client delivers the contents of the MSGin5G message to the targeted Application Client. If MSGin5G Client has not received all messages (even after recovery procedure) or reassembly of segments failed for any reason (e.g. corrupt data) then the MSGin5G Client will notify receiving of a failed message to the Application Client. + +### 8.5.3 Point-to-Application Message Segmentation and Reassembly + +Figure 8.5.3-1 shows the MSGin5G message segmentation and reassembly procedure for Point-to-Application MSGin5G message use cases (e.g. MOAT). + +Pre-conditions: + +- A UE hosts an MSGin5G Client and an Application Client. +- The MSGin5G Client registered with the MSGin5G Server. +- An Application Client on the UE needs to deliver application data to an Application Server and the size of the application data exceeds the maximum allowed packet size (e.g. due to limitation by the UE's access network transport). +- Both the Application Server and the MSGin5G UE are hosted by the same MSGin5G Server. + +![Sequence diagram illustrating Point-to-Application MSGin5G Message Segmentation and Reassembly. The diagram shows four lifelines: MSGin5G UE (containing Application Client(s) and MSGin5G Client), MSGin5G Server, and Application Server. The process involves: 1. Request with large payload from Application Client(s) to MSGin5G Client; 2. MSGin5G message segmentation within the MSGin5G Client; 3. Segmented messages delivered from MSGin5G Client to MSGin5G Server; 4. MSGin5G message reassembly within the MSGin5G Server; 5. Message received confirmation from MSGin5G Server to MSGin5G Client; 6. Application request with large payload from MSGin5G Server to Application Server.](66e89867f97592fd4bfab0e4f2b2054f_img.jpg) + +``` + +sequenceDiagram + participant ApplicationClient as Application Client(s) + participant MSGin5GClient as MSGin5G Client + participant MSGin5GServer as MSGin5G Server + participant ApplicationServer as Application Server + + Note left of ApplicationClient: MSGin5G UE + ApplicationClient-->>MSGin5GClient: 1. Request with large payload + MSGin5GClient->>MSGin5GClient: 2. MSGin5G message segmentation + MSGin5GClient->>MSGin5GServer: 3. Segmented messages delivered + MSGin5GServer->>MSGin5GServer: 4. MSGin5G message reassembly + MSGin5GServer-->>MSGin5GClient: 5. Message received confirmation + MSGin5GServer->>ApplicationServer: 6. Application request with large payload + +``` + +Sequence diagram illustrating Point-to-Application MSGin5G Message Segmentation and Reassembly. The diagram shows four lifelines: MSGin5G UE (containing Application Client(s) and MSGin5G Client), MSGin5G Server, and Application Server. The process involves: 1. Request with large payload from Application Client(s) to MSGin5G Client; 2. MSGin5G message segmentation within the MSGin5G Client; 3. Segmented messages delivered from MSGin5G Client to MSGin5G Server; 4. MSGin5G message reassembly within the MSGin5G Server; 5. Message received confirmation from MSGin5G Server to MSGin5G Client; 6. Application request with large payload from MSGin5G Server to Application Server. + +**Figure 8.5.3-1: Point-to-Application MSGin5G Message Segmentation and Reassembly** + +1. An Application Client on a UE sends a message to an MSGin5G Client that targets an Application Server and that has a size that exceeds the maximum allowed packet size. +2. The MSGin5G Client compares the size of the received message to the maximum allowed packet size that is supported for message delivery to the MSGin5G Server and detects that the size exceeds the limit. As a result, the MSGin5G Client segments the received message into a set of segmented messages such that each segmented message can fit within the maximum allowed packet size. Within each segmented message, the information elements defined in Table 8.3.2-1 are included to enable the MSGin5G Server to reassemble the segmented messages, with following clarifications. + - a) The MSGin5G message request includes following information elements from Table 8.3.2-1: + - i) Originating UE Service ID, Recipient AS Service ID, Message ID, Segmentation set identifier and Message segment number in each segmented message + - ii) Delivery status required and Total number of message segments, only if it is the first segment of the message + - iii) Last segment flag, only if it is the last segment of the message. +3. The MSGin5G Client sends each segmented message to the MSGin5G Server. If any segment is not received within the expected time (based on configuration) then proceed to step 4. +4. If MSGin5G Server has received all segments (determined based on first segment and last Segment), the MSGin5G Server reassembles all the segmented messages into a single MSGin5G message based on the information elements mentioned in step 2. If not all segments are received within expected time, then the MSGin5G Server recovers the segments as described in clause 8.5.6 MSGin5G message segment recovery procedure, before continuing with rest of the steps. + +NOTE 1: When no further segments are received within expected time and if both first segment and last segment are missing, recovery can be initiated as described in clause 8.5.6 MSGin5G message segment recovery procedure for recovering the first segment and then for remaining segments. + +5. The MSGin5G Server sends a Message received confirmation to the MSGin5G Client. The information elements defined in Table 8.3.2-3 are included in the request. +6. If reassembly of segments is successful, the MSGin5G Server delivers the contents of the MSGin5G message to the targeted Application Server. If MSGin5G Server has not received all messages (even after recovery procedure) or reassembly of segments failed for any reason (e.g. corrupt data) then the MSGin5G Server will notify receiving of a failed message to the Application Server. + +## 8.5.4 Point-to-Point Message Segmentation and Reassembly + +Figure 8.5.4-1 shows the MSGin5G message segmentation and reassembly procedure for Point-to-Point MSGin5G message use cases (e.g. MOMT). + +If the recipient UE is a non-MSGin5G UE, the reassembly is performed by the Message Gateway. + +This procedure assumes that a UE is only aware of the maximum payload size of the delivery mechanism it is currently using, and it is not aware of the maximum payload size of the recipient UE. + +Pre-conditions: + +1. Both UEs host an MSGin5G Client and an Application Client. +2. The MSGin5G Clients registered with the MSGin5G Server. +3. An Application Client on the UE needs to deliver application data to an Application Client on another UE and the size of the application data exceeds the allowed maximum packet size (e.g. due to limitation by the UE's access network transport). +4. Both the sending and the receiving MSGin5G UE are hosted by the same MSGin5G Server. + +![Sequence diagram illustrating Point-to-Point MSGin5G Message Segmentation and Reassembly. The diagram shows three main entities: MSGin5G UE 1 (containing Application Client(s) and MSGin5G Client 1), MSGin5G Server, and MSGin5G UE 2 (containing MSGin5G Client 2 and Application Client(s)). The sequence of interactions is: 1. Application Client(s) on UE 1 sends a request with large payload to MSGin5G Client 1. 2. MSGin5G Client 1 performs message segmentation. 3. Segmented messages are delivered from Client 1 to the Server. 4. A dashed box indicates 'Possible MSGin5G message reassembly and segmentation' at the Server. 5. The Server sends a 'Message received confirmation' back to Client 1. 6. Segmented messages are delivered from the Server to MSGin5G Client 2. 7. MSGin5G Client 2 performs message reassembly. 8. Client 2 sends a 'Message received confirmation' to the Server. 9. The Server performs 'Message delivery with large payload' to the Application Client(s) on UE 2.](cd3e29b6d40dce0580fa43b721157489_img.jpg) + +Sequence diagram illustrating Point-to-Point MSGin5G Message Segmentation and Reassembly. The diagram shows three main entities: MSGin5G UE 1 (containing Application Client(s) and MSGin5G Client 1), MSGin5G Server, and MSGin5G UE 2 (containing MSGin5G Client 2 and Application Client(s)). The sequence of interactions is: 1. Application Client(s) on UE 1 sends a request with large payload to MSGin5G Client 1. 2. MSGin5G Client 1 performs message segmentation. 3. Segmented messages are delivered from Client 1 to the Server. 4. A dashed box indicates 'Possible MSGin5G message reassembly and segmentation' at the Server. 5. The Server sends a 'Message received confirmation' back to Client 1. 6. Segmented messages are delivered from the Server to MSGin5G Client 2. 7. MSGin5G Client 2 performs message reassembly. 8. Client 2 sends a 'Message received confirmation' to the Server. 9. The Server performs 'Message delivery with large payload' to the Application Client(s) on UE 2. + +**Figure 8.5.4-1: Point-to-Point MSGin5G Message Segmentation and Reassembly** + +1. An Application Client on UE 1 sends a message to MSGin5G Client 1 that targets Application Client on UE 2. +2. The MSGin5G Client 1 compares the size of the received message to the maximum allowed packet size that is supported for message delivery to the MSGin5G Server and detects that the size exceeds the limit of the originating UE. As a result, the MSGin5G Client segments the received message into a set of segmented messages such that each segmented message can fit within the maximum allowed packet size. + +The MSGin5G message request includes following information elements from Table 8.3.2-1: + +- i) Originating UE Service ID, Recipient UE Service ID, Message ID, Segmentation set identifier and Message segment number in each segmented message + - ii) Delivery status required and Total number of message segments, only if it is the first segment of the message + - iii) Last segment flag, only if it is the last segment of the message. +3. The MSGin5G Client 1 sends each segmented message to the MSGin5G Server. If any segment is not received within the expected time (based on configuration) then proceed to step 5. + 4. The MSGin5G Server checks if each segment does not exceed the configured maximum packet size of the targeted UE. If the maximum packet size is not exceeded, then the MSGin5G Server proceeds with step 6. + +If the maximum packet size is exceeded, the MSGin5G Server performs the following operations: + +- a) If all segments are received within expected time, then the MSGin5G Server reassembles subsequent segmented messages into a single MSGin5G message until the Last segment flag indication is received. The re-assembled message is then segmented such that each segment is smaller than the maximum allowed packet size of the targeted UE. Within each segmented message, the information elements as mentioned in step 2 are included to enable reassembly at the target, then proceed with step 6. + - b) If not all segments are received within expected time, then the MSGin5G Server acts as Message Receiver to recover the segments as described in clause 8.5.6 MSGin5G message segment recovery procedure, before continuing with rest of the steps. If all segments are received after recovery procedure, then the MSGin5G Server skips to step 4-a, otherwise proceed to step 5. +5. The MSGin5G Server sends Message received confirmation to the MSGin5G Client 1. The information elements defined in Table 8.3.2-3 are included in the request. If the Result information element is "failure" further steps are not executed. + 6. The MSGin5G Server sends each segmented message to the MSGin5G Client 2. If any segment as a separate message is not received within the expected time (based on configuration) then proceed to step 8. + 7. The MSGin5G Client 2 reassembles all the segmented messages into a single MSGin5G message based on the information elements defined mentioned in step 2. If not all segments are received within expected time, then the MSGin5G Client 2 acts as Message receiver to recover the segments as described in clause 8.5.6 MSGin5G message segment recovery procedure, before continuing with rest of the steps. +- NOTE 1: Steps 7, 8 and 9 can also be performed by the MSGin5G Client functionality in the Message Gateway in case the recipient UE is a non-MSGin5G UE. +8. The MSGin5G Client 2 sends Message received confirmation to the MSGin5G Server. The information elements defined in Table 8.5.2-2 are included in the request. The Result information element will contain "success" if the reassembly of the segments is successful. Otherwise, the Result information element will contain "failure". + 9. The MSGin5G Client 2 delivers the contents of the MSGin5G message to the targeted Application Client. If MSGin5G Client has not received all messages (even after recovery procedure) or reassembly of segments failed for any reason (e.g. corrupt data) then the MSGin5G Client will notify receiving of failed message to Application Client. + +## 8.5.5 Group Message Segmentation and Reassembly + +A Group Message is sent from the MSGin5G Server to a group of recipient UEs. The MSGin5G Server sends the message to each individual recipient taking into account the maximum packet size that is supported by the recipient and segments the message as described in clause 8.5.4. + +## 8.5.6 MSGin5G Message Segment Recovery + +Figure 8.5.6-1 illustrates an MSGin5G message segmentation recovery procedure. The procedure is applicable to Application-to-Point messages, Point-to-Application messages, Point-to-Point message and Group messages. + +Pre-conditions: + +1. The Message sender has delivered segmented messages to Message receiver. + +![Sequence diagram for MSGin5G Message Segmentation and Reassembly. The diagram shows three lifelines: Message Receiver, Access Network (e.g. 3GPP CN), and Message Sender. The sequence of steps is: 1. Message Receiver detects that recovery of segments required; 2. Message Receiver sends a Segment recovery request to Message Sender; 3. Message Sender sends a Segment recovery ack to Message Receiver; 4. Segmented messages are delivered using access network transport from Message Sender to Message Receiver; 5. Message Receiver performs Message reassembly.](364054adcd1b427fa259450e006c6b38_img.jpg) + +``` + +sequenceDiagram + participant MR as Message Receiver + participant AN as Access Network (e.g. 3GPP CN) + participant MS as Message Sender + Note left of MR: 1. Detects that recovery of segments required + MR->>MS: 2. Segment recovery request + MS-->>MR: 3. Segment recovery ack + Note right of MR: 4. Segmented messages delivered using access network transport + Note left of MR: 5. Message reassembly + +``` + +Sequence diagram for MSGin5G Message Segmentation and Reassembly. The diagram shows three lifelines: Message Receiver, Access Network (e.g. 3GPP CN), and Message Sender. The sequence of steps is: 1. Message Receiver detects that recovery of segments required; 2. Message Receiver sends a Segment recovery request to Message Sender; 3. Message Sender sends a Segment recovery ack to Message Receiver; 4. Segmented messages are delivered using access network transport from Message Sender to Message Receiver; 5. Message Receiver performs Message reassembly. + +**Figure 8.5.6-1: MSGin5G Message Segmentation and Reassembly** + +1. The Message Receiver detects that few segments are missing to reassemble complete message. +2. The Message receiver sends Segment recovery request to Message sender. The information elements defined in Table 8.5.6-1 are included in the request message. + +**Table 8.5.6-1: Segment Recovery Request Information Elements** + +| Information element | Status | Description | +|-----------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Segmentation Set Identifier | M | The Segmentation Set Identifier as received in segments. | +| List of Segment range | M | List of Segment range which the client wants to recover, each segment range consist of start and end sequence number of missing segments e.g. (5-7, 10-10, 15-19) | + +3. The Message sender sends Segment recovery acknowledgement to the MSGin5G Receiver. +4. The Message sender sends each segmented message to the Message receiver within an individual access network transport packet. If any segment is not received within the expected time (based on configuration) then the Message receiver may consider as recovery failed or may initiate the procedure again with updated list of segment range. + +NOTE: The MSGin5G message segment recovery procedure may repeat based on the configuration. + +5. If Message receiver has received all segments (determined based on First segment and Last Segment), the Message receiver reassembles all the segmented messages into a single MSGin5G message. + +## 8.6 MSGin5G messaging procedure on Message Gateway + +### 8.6.1 General MSGin5G messaging procedure on Message Gateway + +Figure 8.6.1-1 shows the MSGin5G message delivery procedure on Message Gateway for Non-MSGin5G UEs. + +![Sequence diagram illustrating the MSGin5G messaging procedure on a Message Gateway. The diagram shows three lifelines: MSGin5G Server, Message Gateway, and Non-MSGin5G UE. The sequence of messages is: 1. MSGin5G message request from MSGin5G Server to Message Gateway; 2. Non-MSGin5G information exchange between Message Gateway and Non-MSGin5G UE; 3. checks whether application level message delivery status report is supported by the Non-MSGin5G message delivery mechanisms (internal to Message Gateway); 4a. fetches delivery status (and failure reason If needed) from Non-MSGin5G message delivery mechanisms (internal to Message Gateway); 4b. Non-MSGin5G application level message delivery status report from Non-MSGin5G UE to Message Gateway; 5b. Translates the application level message delivery status report to MSGin5G message delivery status report (internal to Message Gateway); 6. MSGin5G message delivery status report from Message Gateway to MSGin5G Server. Steps 3, 4a, and 5b are grouped in a dashed box, and steps 4a and 4b are grouped in another dashed box.](b1784a5cbeeb3d9fb9e60b333019c721_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G Server + participant Message Gateway + participant Non-MSGin5G UE + + MSGin5G Server->>Message Gateway: 1. MSGin5G message request + Message Gateway-->>Non-MSGin5G UE: 2. Non-MSGin5G information exchange + Note right of Message Gateway: 3. checks whether application level message delivery status report is supported by the Non-MSGin5G message delivery mechanisms + Note right of Message Gateway: 4a. fetches delivery status (and failure reason If needed) from Non-MSGin5G message delivery mechanisms + Note right of Non-MSGin5G UE: 4b. Non-MSGin5G application level message delivery status report + Note right of Message Gateway: 5b. Translates the application level message delivery status report to MSGin5G message delivery status report + Message Gateway-->>MSGin5G Server: 6. MSGin5G message delivery status report + +``` + +Sequence diagram illustrating the MSGin5G messaging procedure on a Message Gateway. The diagram shows three lifelines: MSGin5G Server, Message Gateway, and Non-MSGin5G UE. The sequence of messages is: 1. MSGin5G message request from MSGin5G Server to Message Gateway; 2. Non-MSGin5G information exchange between Message Gateway and Non-MSGin5G UE; 3. checks whether application level message delivery status report is supported by the Non-MSGin5G message delivery mechanisms (internal to Message Gateway); 4a. fetches delivery status (and failure reason If needed) from Non-MSGin5G message delivery mechanisms (internal to Message Gateway); 4b. Non-MSGin5G application level message delivery status report from Non-MSGin5G UE to Message Gateway; 5b. Translates the application level message delivery status report to MSGin5G message delivery status report (internal to Message Gateway); 6. MSGin5G message delivery status report from Message Gateway to MSGin5G Server. Steps 3, 4a, and 5b are grouped in a dashed box, and steps 4a and 4b are grouped in another dashed box. + +**Figure 8.6.1-1: MSGin5G messaging procedure on Message Gateway.** + +1. The MSGin5G Server forwards the MSGin5G message request to recipient Non-MSGin5G UE based on the UE Service ID or to the Broadcast Message Gateway based on the Broadcast Area ID as specified in clause 8.3.3. A Delivery status required IE may be included in the MSGin5G message request. +2. The Message Gateway records if a message delivery status report is requested in the message. Then it translates the MSGin5G message to a Non-MSGin5G message (e.g. SMS, RCS message as specified in GSMA PRD RCC.07 [3]) with message delivery status report requested and finishes the information exchange procedure with Non-MSGin5G UE (e.g. sends the non-MSGin5G message to the Non-MSGin5G UE and receives the needed response). + +NOTE 1: The information exchange procedure between Message Gateway and Non-MSGin5G UE is out of scope of this specification. + +3. The Message Gateway checks if application level message delivery status report is supported by the Non-MSGin5G message delivery mechanism. If not supported, step 4a will be used and steps 4b and 5b will be skipped; otherwise step 4b-5b will be used and step 4a will be skipped. + +- 4a. Based on the information (e.g. response to the non-MSGin5G message delivery request, transport level information) obtained from the non-MSGin5G message delivery mechanism, the Message Gateway fetches the delivery status from the above information and uses it to create an MSGin5G message delivery status report. If the delivery status is a failure, the Message Gateway also fetches the suitable failure reason from the above information and uses it as reason of failure in the MSGin5G message delivery status report. The Information Elements listed in table 8.3.4-1 are included in the MSGin5G message delivery status report. + +- 4b. A non-MSGin5G application level message delivery status report is received by the Message Gateway. + +NOTE 2: The procedure of non-MSGin5G application level message delivery status report is out of scope of this specification. + +- 5b. The Message Gateway translates the non-MSGin5G application level message delivery status report to MSGin5G message delivery status report as specified in clause 8.3.4. The Information Elements listed in table 8.3.4-1 are also included in this MSGin5G message delivery status report, but the Delivery Status and Failure Cause IEs are fetched from the non-MSGin5G application level message delivery status report. +6. The Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server on behalf of the Non-MSGin5G UE or based on the delivery result of the broadcast delivery mechanism, as specified in clause 8.3.4. + +NOTE: The Broadcast Message Gateway could provide the delivery status report. If the recipient UE supports an MSGin5G Client, the MSGin5G UE can (also) send a delivery status report. + +## 8.6.2 Non-MSGin5G UE receives message from group + +### 8.6.2.1 Legacy 3GPP UE receives message from group + +Figure 8.6.2.1-1 shows the procedure for Legacy 3GPP UE to receive message from group. + +Pre-conditions: + +1. The MSGin5G Server has received the Group message to be sent to a target Legacy 3GPP UE. + +![Sequence diagram showing the procedure for a Legacy 3GPP UE to receive a message from a group. The diagram involves three main entities: Legacy 3GPP UE, Legacy 3GPP Message Gateway, and MSGin5G Server. The sequence of steps is: 1. MSGin5G Server sends a MSGin5G Group message to the Legacy 3GPP Message Gateway. 2. The Gateway translates the message to a legacy 3GPP message. 3. The Gateway delivers the legacy 3GPP message to the UE. 4. The UE performs the message payload delivery.](205c14458d7f4e2d22c75354bb451e99_img.jpg) + +``` + +sequenceDiagram + participant UE as Legacy 3GPP UE + participant GW as Legacy 3GPP Message Gateway + participant Server as MSGin5G Server + + Note over GW, Server: 1. Send MSGin5G Group message as per clause 8.3.3 + Note over GW: 2. Translate message to legacy 3GPP message + Note over UE, GW: 3. Deliver legacy 3GPP message + Note over UE: 4. Message payload delivery + +``` + +Sequence diagram showing the procedure for a Legacy 3GPP UE to receive a message from a group. The diagram involves three main entities: Legacy 3GPP UE, Legacy 3GPP Message Gateway, and MSGin5G Server. The sequence of steps is: 1. MSGin5G Server sends a MSGin5G Group message to the Legacy 3GPP Message Gateway. 2. The Gateway translates the message to a legacy 3GPP message. 3. The Gateway delivers the legacy 3GPP message to the UE. 4. The UE performs the message payload delivery. + +**Figure 8.6.2.1-1: Legacy 3GPP UE receives a message from a group** + +1. The MSGin5G Server sends the MSGin5G message request to the recipient based on the UE Service ID. The Legacy 3GPP Message Gateway receives the MSGin5G message request on behalf of the Legacy 3GPP UE as defined in clause 8.3.3 with following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient Group Service ID, Recipient UE Service ID, Message ID, Payload information elements from Table 8.3.3-1. The MSGin5G message request may include Delivery status required, Application ID and Priority type information elements from Table 8.3.3-1. +2. The Legacy 3GPP Message Gateway translates the MSGin5G message request to Legacy 3GPP message (e.g. SMS). +3. The Legacy 3GPP message gateway sends the Legacy 3GPP message (e.g. SMS) to Legacy 3GPP UE. +4. The Legacy 3GPP UE delivers the payload of the legacy 3GPP message (e.g. SMS) to the targeted Application Client on the Legacy 3GPP UE. + +### 8.6.2.2 Non-3GPP message client receives message from group + +Figure 8.6.2.2-1 shows the procedure for Non-3GPP message client to receive message from group. + +Pre-conditions: + +1. The MSGin5G Server has received the Group message to be sent to target Non-3GPP UE. + +![Sequence diagram showing the procedure for a Non-3GPP message client to receive a message from a group. The diagram has three vertical lifelines: Non-3GPP UE (left), Non-3GPP Message Gateway (center), and MSGin5G Server (right). Step 1: A box spanning from MSGin5G Server to Non-3GPP Message Gateway labeled '1. Send MSGin5G group message as per clause 8.3.3'. Step 2: A box on the Non-3GPP Message Gateway lifeline labeled '2. Translate message to Non-3GPP message'. Step 3: A box spanning from Non-3GPP Message Gateway to Non-3GPP UE labeled '3. Delivery Non-3GPP message'. Step 4: A box on the Non-3GPP UE lifeline labeled '4. Message payload delivery'.](86bd357c573c9696393f5bde4d4cce4f_img.jpg) + +``` + +sequenceDiagram + participant UE as Non-3GPP UE + participant GW as Non-3GPP Message Gateway + participant SRV as MSGin5G Server + SRV->>GW: 1. Send MSGin5G group message as per clause 8.3.3 + Note over GW: 2. Translate message to Non-3GPP message + GW->>UE: 3. Delivery Non-3GPP message + Note over UE: 4. Message payload delivery + +``` + +Sequence diagram showing the procedure for a Non-3GPP message client to receive a message from a group. The diagram has three vertical lifelines: Non-3GPP UE (left), Non-3GPP Message Gateway (center), and MSGin5G Server (right). Step 1: A box spanning from MSGin5G Server to Non-3GPP Message Gateway labeled '1. Send MSGin5G group message as per clause 8.3.3'. Step 2: A box on the Non-3GPP Message Gateway lifeline labeled '2. Translate message to Non-3GPP message'. Step 3: A box spanning from Non-3GPP Message Gateway to Non-3GPP UE labeled '3. Delivery Non-3GPP message'. Step 4: A box on the Non-3GPP UE lifeline labeled '4. Message payload delivery'. + +**Figure 8.6.2.2-1: Non-3GPP message client receives a message from a group** + +1. The MSGin5G Server sends the MSGin5G message request to the recipient based on the UE Service ID. The MSGin5G Gateway receives the MSGin5G message request on behalf of the Non-3GPP UE as defined in clause 8.3.3 with following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient Group Service ID, Recipient UE Service ID, Message ID, Payload information elements from Table 8.3.3-1. The MSGin5G message request may include Delivery status required, Application ID and Priority type information elements from Table 8.3.3-1. +2. The Non-3GPP Message Gateway translates the MSGin5G message to Non-3GPP message. +3. The Non-3GPP Message Gateway sends message to Non-3GPP Message Client. +- 4) The Non-3GPP UE delivers the payload of the non-3GPP message (e.g. RCS) to the targeted Application Client on the Non-3GPP UE. + +NOTE: The procedure to translate an MSGin5G message to a Non-3GPP message and to send a Non-3GPP message from the Non-3GPP Message Gateway to the Non-3GPP Message Client are out of scope of 3GPP. + +## 8.7 E2E Message delivery procedures + +Editor's note: It is also FFS how endpoints are provided with the Service IDs of the counterparts with which the E2E message delivery procedures are used. + +Editor's note: Generalizing MSISDN to Legacy 3GPP identifier in pre-conditions is FFS. + +### 8.7.1 Point-to-Point Message delivery procedures + +#### 8.7.1.1 From MSGin5G UE to MSGin5G UE + +Figure 8.7.1.1-1 shows the message delivery procedure from MSGin5G UE 1 to MSGin5G UE 2. + +Pre-condition: + +- Both MSGin5G Client 1 in MSGin5G UE 1 and MSGin5G Client 2 in MSGin5G UE 2 have registered with the MSGin5G Server. + +![Sequence diagram showing message delivery between MSGin5G UE-1 and MSGin5G UE-2 via an MSGin5G Server. The diagram shows three steps: 1. MSGin5G Client 1 sends a message to the server; 2. The server forwards the message to MSGin5G Client 2; 3. A delivery status report is sent from the server back to Client 1.](7b18671bc31881a5c474883bf6a300fd_img.jpg) + +``` + +sequenceDiagram + participant UE1 as MSGin5G UE-1 + participant Server as MSGin5G Server + participant UE2 as MSGin5G UE-2 + Note left of UE1: Application Client 1, MSGin5G Client 1 + Note right of UE2: MSGin5G Client 2, Application Client 2 + UE1->>Server: 1. MSGin5G Client 1 sends message to MSGin5G Server as per clause 8.3.2 + Server->>UE2: 2. MSGin5G Server forwards the message to MSGin5G Client 2 as per clause 8.3.3 + Server->>UE1: 3. MSGin5G message delivery status report as specified in clause 8.3.4 and 8.3.5 + +``` + +Sequence diagram showing message delivery between MSGin5G UE-1 and MSGin5G UE-2 via an MSGin5G Server. The diagram shows three steps: 1. MSGin5G Client 1 sends a message to the server; 2. The server forwards the message to MSGin5G Client 2; 3. A delivery status report is sent from the server back to Client 1. + +**Figure 8.7.1.1-1 Message delivery between MSGin5G UEs** + +- The MSGin5G Client 1 sends an MSGin5G message request to MSGin5G Server as specified in clause 8.3.2 with following clarifications: + - The MSGin5G message request includes Originating UE Service ID, Recipient UE Service ID and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. + - Upon receiving the MSGin5G message request, the MSGin5G Server determines if the MSGin5G Client 1 is authorized to send a message to MSGin5G Client 2. +- The MSGin5G Server forwards the MSGin5G message request to MSGin5G Client 2 as specified in clause 8.3.3. + +3. If Delivery status required is included in the MSGin5G message request, MSGin5G Client 2 sends MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4 and then the MSGin5G Server sends MSGin5G message delivery status report to MSGin5G Client 1 as specified in clause 8.3.5. + +### 8.7.1.2 From MSGin5G UE to Legacy 3GPP UE + +Figure 8.7.1.2-1 shows the message delivery procedure from MSGin5G UE to Legacy 3GPP UE. + +Pre-conditions: + +1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Message Gateway has registered with the MSGin5G Server on behalf of the Legacy 3GPP UE. +2. Legacy 3GPP Message Gateway is aware of the UE Service ID of Legacy 3GPP UE and maintains the mapping to IDs used in the legacy network. + +![Sequence diagram showing message delivery from MSGin5G UE to Legacy 3GPP UE. Lifelines: MSGin5G Client, MSGin5G Server, Legacy 3GPP Message Gateway, SMSC, MTC-IWF/SCEF/NEF, Legacy 3GPP UE. The process involves 8 steps: 1. MSGin5G Client sends message to MSGin5G Server; 2. MSGin5G Server authorizes; 3. MSGin5G Server sends to Legacy 3GPP Message Gateway; 4. Gateway determines delivery mechanism; i. Device Triggering (5a, 6a, 7a); ii. NIDD delivery (5b, 6b, 7b); iii. SMS delivery (5c, 6c, 7c); 8. MSGin5G message delivery status report.](da90447206621f137780272a2bf807a4_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G Client + participant MSGin5G Server + participant Legacy 3GPP Message Gateway + participant SMSC + participant MTC-IWF/SCEF/NEF + participant Legacy 3GPP UE + + Note left of MSGin5G Client: 1. MSGin5G Client sends message to MSGin5G Server as specified in 8.3.2 + MSGin5G Client->>MSGin5G Server: + Note left of MSGin5G Server: 2. Determine that the MSGin5G Client is authorized to send message to the recipient UE + MSGin5G Server->>Legacy 3GPP Message Gateway: 3. MSGin5G Server sends message to Legacy 3GPP Message Gateway as specified in 8.3.3 + Note left of Legacy 3GPP Message Gateway: 4. Determine delivery mechanism, do addressing and change the MSGin5G message request to Legacy 3GPP message request + + Note right of Legacy 3GPP Message Gateway: i. Device Triggering + Legacy 3GPP Message Gateway-->>MTC-IWF/SCEF/NEF: 5a. Device Trigger Request + Note right of MTC-IWF/SCEF/NEF: 6a. Device trigger delivery procedure + MTC-IWF/SCEF/NEF-->>Legacy 3GPP Message Gateway: 7a. Device Trigger Report + + Note right of Legacy 3GPP Message Gateway: ii. NIDD delivery + Legacy 3GPP Message Gateway-->>MTC-IWF/SCEF/NEF: 5b. NIDD Submit Request + Note right of MTC-IWF/SCEF/NEF: 6b. NIDD delivery procedure + MTC-IWF/SCEF/NEF-->>Legacy 3GPP Message Gateway: 7b. NIDD Submit Response + + Note right of Legacy 3GPP Message Gateway: iii. SMS delivery + Legacy 3GPP Message Gateway-->>SMSC: 5c. SMS Request + Note right of SMSC: 6c. SMS delivery procedure + SMSC-->>Legacy 3GPP Message Gateway: 7c. SMS Report + + Note left of MSGin5G Client: 8. MSGin5G message delivery status report as specified in clause 8.3.4 and 8.3.5 + MSGin5G Server->>MSGin5G Client: + +``` + +Sequence diagram showing message delivery from MSGin5G UE to Legacy 3GPP UE. Lifelines: MSGin5G Client, MSGin5G Server, Legacy 3GPP Message Gateway, SMSC, MTC-IWF/SCEF/NEF, Legacy 3GPP UE. The process involves 8 steps: 1. MSGin5G Client sends message to MSGin5G Server; 2. MSGin5G Server authorizes; 3. MSGin5G Server sends to Legacy 3GPP Message Gateway; 4. Gateway determines delivery mechanism; i. Device Triggering (5a, 6a, 7a); ii. NIDD delivery (5b, 6b, 7b); iii. SMS delivery (5c, 6c, 7c); 8. MSGin5G message delivery status report. + +Figure 8.7.1.2-1: Message delivery from MSGin5G UE to Legacy 3GPP UE + +1. The MSGin5G Client sends an MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient UE Service ID and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. +2. Upon receiving the MSGin5G message request, the MSGin5G Server determines if the MSGin5G Client is authorized to send a message to the recipient UE. +3. The MSGin5G Server forwards the MSGin5G message request to the recipient based on the UE Service ID. The Legacy 3GPP Gateway receives the MSGin5G message request on behalf of the Legacy 3GPP UE as specified in 8.3.3. +4. The Legacy 3GPP Message Gateway determines which legacy 3GPP message delivery mechanism (e.g. SMS, NIDD, Device triggering) will be used based on Legacy 3GPP UE capability, the UE communication status, and the MSGin5G Service configuration. When selected, the Legacy 3GPP Message Gateway maps the UE Service ID to the corresponding identifier. For example (not an exhaustive list): + - a) if the Legacy 3GPP Message Gateway selected the device triggering delivery mechanism, it maps the UE Service ID to MSISDN and Application port ID + - b) if the Legacy 3GPP Message Gateway selected the NIDD delivery mechanism, it maps the UE Service ID to External Identifier or MSISDN. + - c) if the Legacy 3GPP Message Gateway selected the SMS delivery mechanism, it maps the UE Service ID to MSISDN. +- 5-7. The Legacy 3GPP Message Gateway sends the payload of the MSGin5G message to the terminating Legacy 3GPP UE using the determined delivery mechanism. For example: + - a) For Device triggering delivery mechanism, the Legacy 3GPP Message Gateway interacts with the MTC-IWF/SCEF/NEF and maps the payload of the MSGin5G message to one or more Device Triggering requests. The MTC-IWF/SCEF/NEF interacts with SMS-SC for delivery to the UE and to receive the message delivery status report (see TS 23.682 [8] clause 5.2, TS 29.122 [9] clause 4.4.6 and TS 29.522 [10] clause 4.4.3) + - b) For NIDD delivery mechanism, the Legacy 3GPP Message Gateway may interact with the SCEF/NEF and maps the payload of the MSGin5G message to one or more NIDD submit request messages. The Reliable Data Service Configuration, Maximum Latency, Priority, PDN Connection Establishment Option settings are based on pre-configurations (see TS 23.682 [8] clause 5.13, TS 29.122 [9] clause 4.4.5.3 and TS 29.522 [10] clause 4.4.12.3). Alternatively, if tunnel parameters are provisioned in the Legacy 3GPP Message Gateway and UPF/P-GW the payload could be tunnelled via the UPF/P-GW (see TS 23.401 [11] (clause 4.3.17.8.3.3), TS 23.501[12] clause 5.6.10.3, TS 23.502 [7] clause 4.24); + - c) For SMS delivery mechanism, the Legacy 3GPP Message Gateway sends SMS to the Legacy 3GPP UE through the SMSC according to the procedure in TS 23.204 [13] or the procedure in clause 4.13.3 of TS 23.502 [7]. +8. If Delivery status required is included in the MSGin5G message request, the Legacy 3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4 and then the MSGin5G Server sends the message delivery status report to the MSGin5G Client as specified in clause 8.3.5. + +### 8.7.1.3 From MSGin5G UE to Non-3GPP UE + +Figure 8.7.1.3-1 shows the message delivery procedure from MSGin5G UE to Non-3GPP UE. + +Pre-conditions: + +1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the Non-3GPP UE. +2. Non-3GPP Message Gateway is aware of the non-3GPP message client in Non-3GPP UE and provides the mapping to UE Service ID. + +![Sequence diagram showing message delivery from MSGin5G UE to Non-3GPP UE. The diagram involves four main entities: MSGin5G UE (containing Application Client and MSGin5G Client), MSGin5G Server, Non-3GPP Message Gateway, and Non-3GPP UE (containing Non-3GPP Message Client). The sequence of messages is: 1. MSGin5G Client sends message to MSGin5G Server; 2. MSGin5G Server determines authorization; 3. MSGin5G Server forwards message to Non-3GPP Message Gateway; 4. Non-3GPP message delivery (dashed box); 5. MSGin5G message delivery status report back to MSGin5G Client.](778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G UE + participant MSGin5G Server + participant Non-3GPP Message Gateway + participant Non-3GPP UE + + Note left of MSGin5G UE: MSGin5G UE contains Application Client and MSGin5G Client + Note right of Non-3GPP UE: Non-3GPP UE contains Non-3GPP Message Client + + MSGin5G Client->>MSGin5G Server: 1.MSGin5G Client sends message to MSGin5G Server as specified in 8.3.2 + MSGin5G Server->>MSGin5G Server: 2. determines that the MSGin5G Client is authorized to send message to the recipient UE + MSGin5G Server->>Non-3GPP Message Gateway: 3.MSGin5G Server forwards MSGin5G Message to Non-3GPP Message Gateway as specified in 8.3.3 + Note right of Non-3GPP Message Gateway: 4. Non-3GPP message delivery (dashed box) + Non-3GPP Message Gateway->>MSGin5G Server: 5.MSGin5G message delivery status report as specified in clause 8.3.4 and 8.3.5 + MSGin5G Server->>MSGin5G Client: + +``` + +Sequence diagram showing message delivery from MSGin5G UE to Non-3GPP UE. The diagram involves four main entities: MSGin5G UE (containing Application Client and MSGin5G Client), MSGin5G Server, Non-3GPP Message Gateway, and Non-3GPP UE (containing Non-3GPP Message Client). The sequence of messages is: 1. MSGin5G Client sends message to MSGin5G Server; 2. MSGin5G Server determines authorization; 3. MSGin5G Server forwards message to Non-3GPP Message Gateway; 4. Non-3GPP message delivery (dashed box); 5. MSGin5G message delivery status report back to MSGin5G Client. + +**Figure 8.7.1.3-1 Message Delivery from MSGin5G UE to Non-3GPP UE** + +1. The Application Client in the MSGin5G UE triggers the MSGin5G Client to send an MSGin5G message request to the MSGin5G Server as specified in 8.3.2 with following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient UE Service ID and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. +2. The MSGin5G Server determines if the MSGin5G Client is authorized to send a message to the recipient UE. +3. The MSGin5G Server forwards the MSGin5G message request to the recipient based on the UE Service ID. The Non-3GPP Message Gateway receives the MSGin5G message request on behalf of the Non-3GPP UE as specified in clause 8.6.1. +4. The Non-3GPP Message Gateway translates the MSGin5G message to the Non-3GPP message with message delivery status report, if appropriate, requested and sends it to the Non-3GPP Message Client. This step is outside the scope of the present specification. +5. If message delivery status report is requested, the Non-3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server forwards the MSGin5G message delivery status report to the MSGin5G Client as specified in clause 8.3.5. + +#### 8.7.1.4 From Legacy 3GPP UE to MSGin5G UE + +This procedure is used for message reply from Legacy 3GPP UE (e.g. SMS UE) to MSGin5G UE. + +Figure 8.7.1.4-1 shows the response message delivery procedure from Legacy 3GPP UE (e.g. SMS UE) to MSGin5G UE. + +Pre-conditions: + +1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Legacy 3GPP Message Gateway has registered with the MSGin5G Server on behalf of the Legacy 3GPP UE. +2. The Legacy 3GPP UE received a message from the MSGin5G UE. +3. The Legacy 3GPP Message Gateway is aware of the Legacy 3GPP UE and provides the mapping to UE Service ID. +4. The Legacy 3GPP UE replies to the MSGin5G UE upon receiving the message from the MSGin5G UE. +5. The Legacy 3GPP Message Gateway implementation supports storing a messaging transaction, i.e. mapping the message originating MSGin5G Service ID and the message delivered to the Legacy 3GPP UE, for an operator configured time period to allow if the Legacy 3GPP UE will send a response to the incoming message. + +![Sequence diagram illustrating the response message delivery procedure from Legacy 3GPP UE to MSGin5G UE. The diagram shows six steps: 1. Legacy 3GPP message request from UE to Gateway; 2. Message Gateway sends message to MSGin5G Server; 3. MSGin5G Server sends message to MSGin5G Client; 4. MSGin5G message delivery status report from Client to Server; 5. API message delivery status report from Server to Gateway; 6. Legacy 3GPP message delivery status report from Gateway to UE.](070352b751dd0711b8ac6ddfa6df1d98_img.jpg) + +``` + +sequenceDiagram + participant L3GPP_UE as Legacy 3GPP UE (IMS or non-IMS) + participant L3GPP_GW as Legacy 3GPP Message Gateway + participant MSGin5G_S as MSGin5G Server + participant MSGin5G_C as MSGin5G Client + Note left of L3GPP_UE: Legacy 3GPP Message Client + L3GPP_UE->>L3GPP_GW: 1. Legacy 3GPP message request + L3GPP_GW->>MSGin5G_S: 2. Message Gateway sends message to MSGin5G Server as specified in 8.3.2 + MSGin5G_S->>MSGin5G_C: 3. MSGin5G Server sends message to MSGin5G Client as specified in 8.3.3 + MSGin5G_C->>MSGin5G_S: 4. MSGin5G message delivery status report as specified in 8.3.4 + MSGin5G_S->>L3GPP_GW: 5. API message delivery status report as specified in 8.3.5 + L3GPP_GW->>L3GPP_UE: 6. Legacy 3GPP message delivery status report + +``` + +Sequence diagram illustrating the response message delivery procedure from Legacy 3GPP UE to MSGin5G UE. The diagram shows six steps: 1. Legacy 3GPP message request from UE to Gateway; 2. Message Gateway sends message to MSGin5G Server; 3. MSGin5G Server sends message to MSGin5G Client; 4. MSGin5G message delivery status report from Client to Server; 5. API message delivery status report from Server to Gateway; 6. Legacy 3GPP message delivery status report from Gateway to UE. + +**Figure 8.7.1.4-1: Legacy 3GPPs UE replies to MSGin5G UE** + +1. The Legacy 3GPP UE sends a Legacy 3GPP message request to the Legacy 3GPP Message Gateway (e.g. through SMSC if SMS is used according the procedure in 3GPP TS 23.204 [13] or the procedure in clause 4.13.3 of TS 23.502 [7]). +2. The Legacy 3GPP Message Gateway translates the SMS message into MSGin5G message and sends an MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient UE Service ID, and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. + - b) Upon receiving the MSGin5G message request, the MSGin5G Server determines if the Legacy 3GPP UE with its UE Service ID is allowed to send a message to the MSGin5G UE. +3. The MSGin5G Server forwards the MSGin5G message request to the target MSGin5G Client as specified in clause 8.3.3. +- 4-6. If the message delivery status report is requested, the MSGin5G Client in MSGin5G UE sends an MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the MSGin5G message delivery status report to the Legacy 3GPP Message Gateway specified in clause 8.3.5, the Legacy 3GPP Message Gateway translates the MSGin5G message delivery status report to a Legacy 3GPP message delivery status report and sends it to the Legacy 3GPP UE. + +### 8.7.1.5 From Non-3GPP UE to MSGin5G UE + +This procedure is used for message reply from Non-3GPP UE to MSGin5G UE. + +Figure 8.7.1.5-1 shows the message delivery procedure from Non-3GPP UE to MSGin5G UE. + +Pre-conditions: + +1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the Non-3GPP UE. +2. The Non-3GPP UE received a message from the MSGin5G UE. +3. The Non-3GPP Message Gateway is aware of the Non-3GPP message client on the Non-3GPP UE and provides the mapping to UE Service ID. +4. The Non-3GPP UE replies to the MSGin5G UE upon receiving the message from the MSGin5G UE. +5. The Non-3GPP Message Gateway implementation supports storing a messaging transaction, i.e. mapping the message originating MSGin5G Service ID and the message delivered to the Non-3GPP UE, for an operator configured time period to allow if the Non-3GPP UE will send a response to the incoming message. + +![Sequence diagram showing the message delivery procedure from Non-3GPP UE to MSGin5G UE. The diagram involves four main entities: Non-3GPP UE (IMS or non-IMS) containing a Non-3GPP Message Client, Non-3GPP Message Gateway, MSGin5G Server, and MSGin5G UE containing a MSGin5G Client. The sequence of messages is: 1. Non-3GPP message request from Non-3GPP UE to Non-3GPP Message Gateway; 2. Message Gateway sends message to MSGin5G Server as specified in 8.3.2; 3. MSGin5G Server sends message to MSGin5G Client as specified in 8.3.3; 4. MSGin5G message delivery status report as specified in 8.3.4 from MSGin5G Client to MSGin5G Server; 5. API message delivery status report as specified in 8.3.5 from MSGin5G Server to Non-3GPP Message Gateway; 6. Non-3GPP message delivery status report from Non-3GPP Message Gateway to Non-3GPP UE.](b1e7bb95fa1587d870de03df02477df4_img.jpg) + +``` + +sequenceDiagram + participant Non-3GPP UE (IMS or non-IMS) + participant Non-3GPP Message Gateway + participant MSGin5G Server + participant MSGin5G UE + Note right of Non-3GPP UE: Non-3GPP Message Client + Note right of MSGin5G UE: MSGin5G Client + Non-3GPP UE->>Non-3GPP Message Gateway: 1. Non-3GPP message request + Non-3GPP Message Gateway->>MSGin5G Server: 2. Message Gateway sends message to MSGin5G Server as specified in 8.3.2 + MSGin5G Server->>MSGin5G Client: 3. MSGin5G Server sends message to MSGin5G Client as specified in 8.3.3 + MSGin5G Client->>MSGin5G Server: 4. MSGin5G message delivery status report as specified in 8.3.4 + MSGin5G Server->>Non-3GPP Message Gateway: 5. API message delivery status report as specified in 8.3.5 + Non-3GPP Message Gateway->>Non-3GPP UE: 6. Non-3GPP message delivery status report + +``` + +Sequence diagram showing the message delivery procedure from Non-3GPP UE to MSGin5G UE. The diagram involves four main entities: Non-3GPP UE (IMS or non-IMS) containing a Non-3GPP Message Client, Non-3GPP Message Gateway, MSGin5G Server, and MSGin5G UE containing a MSGin5G Client. The sequence of messages is: 1. Non-3GPP message request from Non-3GPP UE to Non-3GPP Message Gateway; 2. Message Gateway sends message to MSGin5G Server as specified in 8.3.2; 3. MSGin5G Server sends message to MSGin5G Client as specified in 8.3.3; 4. MSGin5G message delivery status report as specified in 8.3.4 from MSGin5G Client to MSGin5G Server; 5. API message delivery status report as specified in 8.3.5 from MSGin5G Server to Non-3GPP Message Gateway; 6. Non-3GPP message delivery status report from Non-3GPP Message Gateway to Non-3GPP UE. + +**Figure 8.7.1.5-1: Non-3GPP UE replies to MSGin5G UE** + +1. The Non-3GPP UE sends a Non-3GPP message request to the Non-3GPP Message Gateway. +2. The Non-3GPP Message Gateway translates the Non-3GPP message to MSGin5G message with message delivery status report requested and sends an MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient UE Service ID and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. + - b) Upon receiving the MSGin5G message request, the MSGin5G Server determines if the Non-3GPP UE with its UE Service ID is allowed to send a message to the MSGin5G UE. +3. The MSGin5G Server forwards the MSGin5G message request to the target MSGin5G Client as specified in clause 8.3.3. +4. If the message delivery status report is requested by the Non-3GPP UE, the MSGin5G Client in MSGin5G UE sends an MSGin5G message delivery status report to the MSGin5G Server specified in clause 8.3.4, the MSGin5G Server sends the MSGin5G message delivery status report to the Non-3GPP Message Gateway + +specified in clause 8.3.5, the Non-3GPP Message Gateway translates the MSGin5G message delivery status report to a Non-3GPP message delivery status report and sends it to the Non-3GPP UE. + +## 8.7.2 Application-to-Point Message delivery procedures + +### 8.7.2.1 From Application Server to MSGin5G UE + +Figure 8.7.2.1-1 shows the message delivery procedure from Application Server to MSGin5G UE. + +Pre-conditions: + +1. The MSGin5G Client is registered with the MSGin5G Server. +2. The Application Server has established secured communication with the MSGin5G Server. + +![Sequence diagram showing message delivery from Application Server to MSGin5G UE via MSGin5G server.](13dbd16a58861b335d8e10047ae8e524_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server + participant MS as MSGin5G server + participant UE as MSGin5G UE + Note right of AS: 1. Application Server sends message to MSGin5G Server as specified in 8.3.2 + AS->>MS: + Note right of MS: 2. MSGin5G Server sends MSGin5G Message Request to MSGin5G Client as specified in 8.3.3 + MS->>UE: + Note right of UE: 3. MSGin5G message delivery status Report As specified in 8.3.4 + UE->>MS: + Note right of MS: 4. API of message delivery status report as specified in 8.3.5 + MS->>AS: + +``` + +The diagram illustrates a four-step sequence of interactions between three entities: Application Server, MSGin5G server, and MSGin5G UE. + 1. The Application Server sends a message to the MSGin5G Server (specified in 8.3.2). + 2. The MSGin5G Server sends an MSGin5G Message Request to the MSGin5G Client (specified in 8.3.3). + 3. The MSGin5G Client sends a message delivery status Report back to the MSGin5G Server (specified in 8.3.4). + 4. The MSGin5G Server then provides an API of message delivery status report to the Application Server (specified in 8.3.5). + +Sequence diagram showing message delivery from Application Server to MSGin5G UE via MSGin5G server. + +**Figure 8.7.2.1-1: Message delivery from Application Server to MSGin5G UE** + +1. The Application Server sends an API Request to MSGin5G Server for sending MSGin5G message as specified in clause 8.3.2 with the following clarifications: + - a) The API request includes Originating AS Service ID, Recipient UE Service ID, and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. + - b) Upon receiving the API Request for MSGin5G message delivery, the MSGin5G Server determines if the Application Server is allowed to send a message to the MSGin5G UE. +2. The MSGin5G Server sends the MSGin5G message request to MSGin5G Client as specified in clause 8.3.3. +3. If Delivery status required is included in the MSGin5G message request, MSGin5G Client 2 sends the message delivery status report to the MSGin5G Server specified in clause 8.3.4. + +4. The MSGin5G Server sends the message delivery status report to the Application Server as specified in clause 8.3.5 + +### 8.7.2.2 From Application Server to Legacy 3GPP UE + +Figure 8.7.2.2-1 shows the message delivery procedure from Application Server to Legacy 3GPP UE. + +Pre-conditions: + +1. The Application Server has established secured communication with the MSGin5G Server. +2. The Legacy 3GPP Message Gateway has registered with the MSGin5G Server on behalf of the client in the Legacy 3GPP UE. +3. Legacy 3GPP Message Gateway is aware of the legacy 3GPP message client (i.e. SMS client) in Legacy 3GPP UE and provides the mapping to UE Service ID. + +![Sequence diagram showing the message delivery procedure from Application Server to Legacy 3GPP UE. The diagram involves six lifelines: Application Server, MSGin5G Server, Legacy 3GPP Message Gateway, SMSC (dashed), MTC-IWF/SCEF/NEF (dashed), and Legacy 3GPP UE. The process starts with the Application Server sending a message to the MSGin5G Server. The MSGin5G Server determines if the Application Server is allowed to send the message. It then sends the message to the Legacy 3GPP Message Gateway. The Gateway determines the delivery mechanism, addresses, and changes the MSGin5G message request to a Legacy 3GPP message request. The diagram then branches into three delivery options: i. Device Triggering, ii. NIDD delivery, and iii. SMS delivery. Each option involves a request from the Gateway to the MTC-IWF/SCEF/NEF, a delivery procedure, and a response back to the Gateway. Finally, the MSGin5G Server sends a message delivery status report to the Application Server.](2fbb410da68e626ba5e994d872031f14_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server + participant MSGin5G as MSGin5G Server + participant LGW as Legacy 3GPP Message Gateway + participant SMSC as SMSC + participant MTC as MTC-IWF/SCEF/NEF + participant UE as Legacy 3GPP UE + + Note left of AS: 1. Application Server sends message to MSGin5G Server as specified in 8.3.2 + AS->>MSGin5G: + Note left of MSGin5G: 2. Determine that the Application Server is allowed to send message to the recipient UE + MSGin5G->>LGW: 3. MSGin5G Server sends message to Legacy 3GPP Message Gateway as specified in 8.3.3 + Note left of LGW: 4. Determine delivery mechanism, do addressing and change the MSGin5G message request to Legacy 3GPP message request + + alt i. Device Triggering + Note right of LGW: i. Device Triggering + LGW-->>MTC: 5a. Device Trigger Request + Note right of MTC: 6a. Device trigger delivery procedure + MTC-->>LGW: 7a. Device Trigger Report + alt ii. NIDD delivery + Note right of LGW: ii. NIDD delivery + LGW-->>MTC: 5b. NIDD Submit Request + Note right of MTC: 6b. NIDD delivery procedure + MTC-->>LGW: 7b. NIDD Submit Response + alt iii. SMS delivery + Note right of LGW: iii. SMS delivery + LGW-->>MTC: 5c. SMS Request + Note right of MTC: 6c. SMS delivery procedure + MTC-->>LGW: 7c. SMS Report + end + + Note left of AS: 8. MSGin5G message delivery status report as specified in clause 8.3.4 and 8.3.5 + MSGin5G->>AS: + +``` + +Sequence diagram showing the message delivery procedure from Application Server to Legacy 3GPP UE. The diagram involves six lifelines: Application Server, MSGin5G Server, Legacy 3GPP Message Gateway, SMSC (dashed), MTC-IWF/SCEF/NEF (dashed), and Legacy 3GPP UE. The process starts with the Application Server sending a message to the MSGin5G Server. The MSGin5G Server determines if the Application Server is allowed to send the message. It then sends the message to the Legacy 3GPP Message Gateway. The Gateway determines the delivery mechanism, addresses, and changes the MSGin5G message request to a Legacy 3GPP message request. The diagram then branches into three delivery options: i. Device Triggering, ii. NIDD delivery, and iii. SMS delivery. Each option involves a request from the Gateway to the MTC-IWF/SCEF/NEF, a delivery procedure, and a response back to the Gateway. Finally, the MSGin5G Server sends a message delivery status report to the Application Server. + +Figure 8.7.2.2-1: Application Server to Legacy 3GPP UE messaging + +1. The Application Server sends an API Request to the MSGin5G Server for sending an MSGin5G message as specified in clause 8.3.2 with the following clarifications: + - a) The API Request includes Originating AS Service ID, Recipient UE Service ID, and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. +2. Upon receiving the API Request for MSGin5G message delivery, the MSGin5G Server determines if the Application Server is allowed to send a message to the recipient UE. +3. The MSGin5G Server sends the MSGin5G message request to the recipient based on the UE Service ID. The Legacy 3GPP Gateway receives the MSGin5G message request on behalf of the Legacy 3GPP UE as specified in clause 8.3.3. +- 4-7. Same with step 4-7 in clause 8.7.1.2. +8. The Legacy 3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4. + +### 8.7.2.3 From Application Server to Non-3GPP UE + +Figure 8.7.2.3-1 shows the message delivery procedure from Application Server to Non-3GPP UE. + +Pre-conditions: + +1. The Application Server has established a secured communication with the MSGin5G Server. +2. The Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the message client in the Non-3GPP UE. +3. Non-3GPP Message Gateway is aware of the non-3GPP message client in Non-3GPP UE and provides the mapping to UE Service ID. + +![Sequence diagram showing the message delivery procedure from Application Server to Non-3GPP UE. The diagram involves four lifelines: Application server, MSGin5G server, Non-3GPP Message Gateway, and Non-3GPP UE. The sequence of messages is: 1. Application Server sends message to MSGin5G Server as specified in 8.3.2; 2. MSGin5G Server determines that the Application Server is allowed to send message to the Non-3GPP UE; 3. MSGin5G Server sends message to Non-3GPP Message Gateway as specified in 8.3.3; 4. Non-3GPP Message Gateway sends non-3GPP message to Non-3GPP UE; 5. MSGin5G Gateway sends API of message delivery status report as specified in 8.3.4; 6. MSGin5G Server sends MSGin5G message delivery status as specified in 8.3.5.](0e252770f8f0573617e0112b36a93d2f_img.jpg) + +``` +sequenceDiagram + participant AS as Application server + participant MS as MSGin5G server + participant NGW as Non-3GPP Message Gateway + participant UE as Non-3GPP UE + + Note right of AS: 1. Application Server sends message to MSGin5G Server as specified in 8.3.2 + AS->>MS: + Note right of MS: 2. determines that the Application Server is allowed to send message to the Non-3GPP UE + MS->>NGW: 3. MSGin5G Server sends message to Non-3GPP Message Gateway as specified in 8.3.3 + Note right of NGW: 4. non-3GPP message + NGW->>UE: + Note right of NGW: 5. MSGin5G Gateway sends API of message delivery status report as specified in 8.3.4 + NGW->>MS: + Note right of MS: 6. MSGin5G Server sends MSGin5G message delivery status as specified in 8.3.5 + MS->>AS: +``` + +Sequence diagram showing the message delivery procedure from Application Server to Non-3GPP UE. The diagram involves four lifelines: Application server, MSGin5G server, Non-3GPP Message Gateway, and Non-3GPP UE. The sequence of messages is: 1. Application Server sends message to MSGin5G Server as specified in 8.3.2; 2. MSGin5G Server determines that the Application Server is allowed to send message to the Non-3GPP UE; 3. MSGin5G Server sends message to Non-3GPP Message Gateway as specified in 8.3.3; 4. Non-3GPP Message Gateway sends non-3GPP message to Non-3GPP UE; 5. MSGin5G Gateway sends API of message delivery status report as specified in 8.3.4; 6. MSGin5G Server sends MSGin5G message delivery status as specified in 8.3.5. + +Figure 8.7.2.3-1 Application Server to Non-3GPP UE messaging + +1. The Application Server sends an API Request to the MSGin5G Server for sending an MSGin5G message as specified in 8.3.2 with the following clarifications: + - a) The API Request includes Originating AS Service ID, Recipient UE Service ID, and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. +2. Upon receiving the API Request for MSGin5G message delivery, the MSGin5G Server determines if the Application Server is allowed to send a message to the Non-3GPP UE. +3. The MSGin5G Server sends the MSGin5G message request to the recipient based on the UE Service ID. The Non-3GPP Message Gateway receives the MSGin5G message request on behalf of the Non-3GPP UE as specified in clause 8.3.3. +4. The Non-3GPP Message Gateway translates the MSGin5G message to the Non-3GPP message and sends it to the Non-3GPP UE. This step is outside the scope of the present specification. +- 5-6. If message delivery status report is required, the Non-3GPP Message Gateway sends the MSGin5G message delivery status report to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the message delivery status report to the Application Server as specified in clause 8.3.5. + +### 8.7.3 Point-to-Application Message delivery procedures + +#### 8.7.3.1 From MSGin5G UE to Application Server + +Figure 8.7.3.1-1 shows the message delivery procedure from MSGin5G UE to Application Server. + +Pre-conditions: + +1. The Application Server and MSGin5G Client in MSGin5G UE have registered with the MSGin5G Server. + +![Sequence diagram showing message delivery from MSGin5G UE to Application Server. The diagram involves three lifelines: MSGin5G UE (containing MSGin5G Client), MSGin5G Server, and Application Server. The sequence of messages is: 1. MSGin5G Client sends message to MSGin5G Server as specified in 8.3.2; 2. MSGin5G Server sends message to Application Server as specified in 8.3.3; 3. API of message delivery status report as specified in 8.3.4; 4. MSGin5G message delivery status report as specified in 8.3.5.](61a49f3179b455e4d35242fc3d187a29_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G UE as MSGin5G UE +MSGin5G Client + participant MSGin5G Server + participant Application Server + Note right of MSGin5G UE: 1. MSGin5G Client sends message to MSGin5G Server as specified in 8.3.2 + MSGin5G UE->>MSGin5G Server: + Note right of MSGin5G Server: 2. MSGin5G Server sends message to Application Server as specified in 8.3.3 + MSGin5G Server->>Application Server: + Note right of Application Server: 3. API of message delivery status report as specified in 8.3.4 + Application Server->>MSGin5G Server: + Note right of MSGin5G Server: 4. MSGin5G message delivery status report as specified in 8.3.5 + MSGin5G Server->>MSGin5G UE: + +``` + +Sequence diagram showing message delivery from MSGin5G UE to Application Server. The diagram involves three lifelines: MSGin5G UE (containing MSGin5G Client), MSGin5G Server, and Application Server. The sequence of messages is: 1. MSGin5G Client sends message to MSGin5G Server as specified in 8.3.2; 2. MSGin5G Server sends message to Application Server as specified in 8.3.3; 3. API of message delivery status report as specified in 8.3.4; 4. MSGin5G message delivery status report as specified in 8.3.5. + +**Figure 8.7.3.1-1: Message delivery from MSGin5G UE to Application Server** + +1. The MSGin5G Client sends an MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient AS Service ID, and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. + - b) Upon receiving the MSGin5G message request, the MSGin5G Server determines if the MSGin5G Client is allowed to send message to Application Server. +2. The MSGin5G Server forwards the MSGin5G message request to the Application Server as specified in clause 8.3.3. + +- 3-4. If Delivery status required is included in the MSGin5G message request, the Application Server sends the message delivery status report to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the delivery status to MSGin5G Client as specified in clause 8.3.5. + +### 8.7.3.2 From Legacy 3GPP UE to Application Server + +This procedure is used for message reply from Non-3GPP UE to Application Server. + +Figure 8.7.3.2-1 shows the message delivery procedure from Legacy 3GPP UE to Application Server. + +Pre-conditions: + +1. The Application Server has established secured communication with the MSGin5G Server. +2. The Legacy 3GPP Message Gateway has registered with the MSGin5G Server on behalf of the message client in the Legacy 3GPP UE. +3. The Legacy 3GPP UE received a message from the Application Server. +4. The Legacy 3GPP Message Gateway is aware of the Legacy 3GPP Message client on the Legacy 3GPP UE and provides the mapping between its identifiers and UE Service ID. +5. The Legacy 3GPP Message Gateway implementation supports storing a messaging transaction, i.e. mapping the message originating MSGin5G Service ID and the message delivered to the Legacy 3GPP UE, for an operator configured time period to allow if the Legacy 3GPP UE will send a response to the incoming message. + +![Sequence diagram showing the message delivery procedure from Legacy 3GPP UE to Application Server. The diagram involves four main entities: Legacy 3GPP UE (IMS or non-IMS), Legacy 3GPP Message Client, Legacy 3GPP Message Gateway, MSGin5G Server, and Application Server. The sequence of messages is: 1. Legacy 3GPP message request from UE to Gateway; 2. Legacy 3GPP Message Gateway sends message to MSGin5G Server as specified in 8.3.2; 3. MSGin5G Server sends message to Application Server as specified in 8.3.3; 3. API of message delivery status report as specified in 8.3.4 from Application Server to MSGin5G Server; 5. MSGin5G Server sends delivery status to Legacy 3GPP Message Gateway as specified in 8.3.5; 6. Legacy 3GPP message delivery report from Gateway to UE.](dde1a42ca58cd189901556a0cbfe7d57_img.jpg) + +``` + +sequenceDiagram + participant UE as Legacy 3GPP UE (IMS or non-IMS) + participant Client as Legacy 3GPP Message Client + participant Gateway as Legacy 3GPP Message Gateway + participant MSGin5G as MSGin5G Server + participant AS as Application Server + + Note left of Client: Legacy 3GPP Message Client + UE->>Gateway: 1. Legacy 3GPP message request + Gateway->>MSGin5G: 2. Legacy 3GPP Message Gateway sends message to MSGin5G Server as specified in 8.3.2 + MSGin5G->>AS: 3. MSGin5G Server sends message to Application Server as specified in 8.3.3 + AS->>MSGin5G: 3. API of message delivery status report as specified in 8.3.4 + MSGin5G->>Gateway: 5. MSGin5G Server sends delivery status to Legacy 3GPP Message Gateway as specified in 8.3.5 + Gateway->>UE: 6. Legacy 3GPP message delivery report + +``` + +Sequence diagram showing the message delivery procedure from Legacy 3GPP UE to Application Server. The diagram involves four main entities: Legacy 3GPP UE (IMS or non-IMS), Legacy 3GPP Message Client, Legacy 3GPP Message Gateway, MSGin5G Server, and Application Server. The sequence of messages is: 1. Legacy 3GPP message request from UE to Gateway; 2. Legacy 3GPP Message Gateway sends message to MSGin5G Server as specified in 8.3.2; 3. MSGin5G Server sends message to Application Server as specified in 8.3.3; 3. API of message delivery status report as specified in 8.3.4 from Application Server to MSGin5G Server; 5. MSGin5G Server sends delivery status to Legacy 3GPP Message Gateway as specified in 8.3.5; 6. Legacy 3GPP message delivery report from Gateway to UE. + +**Figure 8.7.3.2-1: Legacy 3GPP UE replies to Application Server** + +1. The Legacy 3GPP UE sends a Legacy 3GPP message request to the Legacy 3GPP Message Gateway (e.g. through SMSC if SMS is used according the procedure in 3GPP TS 23.204 [13] or the procedure in clause 4.13.3 of TS 23.502 [7]). +2. The Legacy 3GPP Message Gateway translates the Legacy 3GPP message into an MSGin5G message and may include message delivery status report requested in the MSGin5G message. The Legacy 3GPP Message Gateway sends the MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient AS Service ID and Message ID information elements from Table 8.3.2-1, and may include Delivery status required, and may include Application ID, Payload and Priority type information elements from Table 8.3.2-1. + - b) Upon receiving the MSGin5G message request, the MSGin5G Server determines if the Legacy 3GPP UE with its UE Service ID is allowed to send a message to the Application Server. + +3. The MSGin5G Server forwards the MSGin5G message in API request to the Application Server as specified in clause 8.3.3. +- 4-6. If message delivery status report is requested, the Application Server sends the message delivery status report by API request to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server forwards the message delivery status report to the Legacy 3GPP Message Gateway as specified in clause 8.3.5, the Legacy 3GPP Message Gateway translates the MSGin5G message delivery status report into a Legacy 3GPP message delivery status report and sends it to the Legacy 3GPP UE. + +### 8.7.3.3 From Non-3GPP UE to Application Server + +This procedure is used for message reply from Legacy 3GPP UE to Application Server. + +Figure 8.7.3.3-1 shows the message delivery procedure from Non-3GPP UE to Application Server. + +Pre-conditions: + +1. The Application Server has established secured communication with the MSGin5G Server. +2. The Non-3GPP Message Client in Non-3GPP UE has registered with the MSGin5G Server via the Non-3GPP Message Gateway. +3. The Non-3GPP UE received a message from the Application Server. +4. The Non-3GPP Message Gateway is aware of the Non-3GPP message client on the Non-3GPP UE and provides the mapping between its identifiers and UE Service ID. +5. The Non-3GPP Message Gateway implementation supports storing a messaging transaction, i.e. mapping the message originating MSGin5G Service ID and the message delivered to the Non-3GPP UE, for an operator configured time period to allow if the Non-3GPP UE will send a response to the incoming message. + +![Sequence diagram showing the message delivery procedure from Non-3GPP UE to Application Server. The diagram involves four lifelines: Non-3GPP UE (Non-3GPP Message Client), Non-3GPP Message Gateway, MSGin5G Server, and Application Server. The sequence of messages is: 1. Non-3GPP message request from UE to Gateway; 2. Non-3GPP Message Gateway sends message to MSGin5G Server; 3. MSGin5G Server sends message to Application Server; 4. API of message delivery status report from Application Server to MSGin5G Server; 5. MSGin5G Server sends delivery status to Non-3GPP Message Gateway; 6. Non-3GPP message delivery report from Gateway to UE.](02dfdcd208dbdc8fa4f645885e59dd17_img.jpg) + +``` + +sequenceDiagram + participant UE as Non-3GPP UE +Non-3GPP Message Client + participant Gateway as Non-3GPP Message Gateway + participant MSGin5G_Server as MSGin5G Server + participant Application_Server as Application Server + + Note left of UE: Pre-conditions + UE->>Gateway: 1. Non-3GPP message request + Gateway->>MSGin5G_Server: 2. Non-3GPP Message Gateway sends message to MSGin5G Server as specified in 8.3.2 + MSGin5G_Server->>Application_Server: 3. MSGin5G Server sends message to Application Server as specified in 8.3.3 + Application_Server->>MSGin5G_Server: 4. API of message delivery status report as specified in 8.3.4 + MSGin5G_Server->>Gateway: 5. MSGin5G Server sends delivery status to Non-3GPP Message Gateway as specified in 8.3.5 + Gateway->>UE: 6. Non-3GPP message delivery report + +``` + +Sequence diagram showing the message delivery procedure from Non-3GPP UE to Application Server. The diagram involves four lifelines: Non-3GPP UE (Non-3GPP Message Client), Non-3GPP Message Gateway, MSGin5G Server, and Application Server. The sequence of messages is: 1. Non-3GPP message request from UE to Gateway; 2. Non-3GPP Message Gateway sends message to MSGin5G Server; 3. MSGin5G Server sends message to Application Server; 4. API of message delivery status report from Application Server to MSGin5G Server; 5. MSGin5G Server sends delivery status to Non-3GPP Message Gateway; 6. Non-3GPP message delivery report from Gateway to UE. + +**Figure 8.7.3.3-1: Non-3GPP UE replies to Application Server** + +1. The Non-3GPP UE sends a Non-3GPP message request to the Non-3GPP Message Gateway. +2. The Non-3GPP Message Gateway translates the Non-3GPP Message into an MSGin5G message and may include MSGin5G message delivery status report requested in the MSGin5G message. The Non-3GPP Message Gateway sends an MSGin5G message request to the MSGin5G Server as specified in clause 8.3.2 with the following clarifications: + - a) The MSGin5G message request includes Originating UE Service ID, Recipient AS Service ID, and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload, Priority type information elements from Table 8.3.2-1. + - b) Upon receiving the MSGin5G message request, the MSGin5G Server determines if the Non-3GPP UE with its UE Service ID is allowed to send a message to the Application Server. + +3. The MSGin5G Server forwards the MSGin5G message in an API request to the Application Server as specified in clause 8.3.3. +- 4-6. If the delivery status is required, the Application Server sends a message delivery status report by API request to the MSGin5G Server as specified in clause 8.3.4, the MSGin5G Server sends the message delivery status report to the Non-3GPP Message Gateway as specified in clause 8.3.5, the Non-3GPP Message Gateway translates the MSGin5G message delivery status report into a Non-3GPP message delivery status report and sends it to the Non-3GPP UE. + +## 8.7.4 MSGin5G Group messaging + +### 8.7.4.1 General + +This clause introduces a group messaging procedure for MSGin5G Client and MSGin5G Server to send and receive Group messages after a group is created. In this procedure, the group creation and membership management are handled by group management function specified in 3GPP TS 23.434 [5]. + +### 8.7.4.2 Message delivery from UE to group + +Figure 8.7.4.2-1 shows the MSGin5G Group messaging procedure in which MSGin5G Client (both IMS and non-IMS UE) sends a message to a group. + +Pre-conditions: + +1. An MSGin5G Group is created by following group management SEAL service procedures as specified in 3GPP TS 23.434 [5]. +2. All participants in the MSGin5G Group may get the Group information i.e. the Group Service ID. +3. The MSGin5G Server has a copy of the group profile with all the group members by using Group information query specified in 3GPP TS 23.434 [5]. + +![Sequence diagram of group messaging in MSGin5G Service. Lifelines: UE1 (MSGin5G UE1) with Application Client 1 and MSGin5G Client 1; MSGin5G Server; Application Server; UE2 (MSGin5G UE2) with Application Client 2 and MSGin5G Client 2; Legacy 3GPP Message Gateway; UE3 (Legacy 3GPP UE) e.g. SMS, NIDD; Non-3GPP Message Gateway; UE4 (Non-3GPP UE) with Non-3GPP Message Client. The sequence shows message flow from UE1 through the server and application server to other clients and gateways, ending with a delivery status report.](987a8ea27d373fa66433e6b8cb2e98ab_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE1 (MSGin5G UE1) +Application Client 1 +MSGin5G Client 1 + participant MSGin5G Server + participant Application Server + participant UE2 as UE2 (MSGin5G UE2) +Application Client 2 +MSGin5G Client 2 + participant Legacy 3GPP Message Gateway + participant UE3 as UE3 (Legacy 3GPP UE) +e.g. SMS, NIDD + participant Non-3GPP Message Gateway + participant UE4 as UE4 (Non-3GPP UE) +Non-3GPP Message Client + + Note left of MSGin5G Server: 1. MSGin5G Client sends message to group as per clause 8.3.2 + MSGin5G Server->>Application Server: 2. MSGin5G Server sends message to AS as per clause 8.3.3 + Application Server-->>MSGin5G Server: 2a. Application Server sends message response to MSGin5G Server + MSGin5G Server-->>UE1: 2b. MSGin5G Server sends the response to MSGin5G UE as per clause 8.3.2 + Application Server->>MSGin5G Server: 3. Application Server sends message to MSGin5G Server as per clause 8.3.2 + Note right of UE2: 4a. MSGin5G Client receives message from group as per clause 8.3.3 + Note right of UE3: 4b. Legacy 3GPP message client receives message from group as per clause 8.6.2.1 + Note right of UE4: 4c. Non-3GPP message client receives message from group as per clause 8.6.2.2 + Note right of UE4: 5. message delivery status report from MSGin5G Client or Legacy 3GPP Message Client or Non-3GPP Message Client. + +``` + +Sequence diagram of group messaging in MSGin5G Service. Lifelines: UE1 (MSGin5G UE1) with Application Client 1 and MSGin5G Client 1; MSGin5G Server; Application Server; UE2 (MSGin5G UE2) with Application Client 2 and MSGin5G Client 2; Legacy 3GPP Message Gateway; UE3 (Legacy 3GPP UE) e.g. SMS, NIDD; Non-3GPP Message Gateway; UE4 (Non-3GPP UE) with Non-3GPP Message Client. The sequence shows message flow from UE1 through the server and application server to other clients and gateways, ending with a delivery status report. + +Figure 8.7.4.2-1: Group messaging in MSGin5G Service + +1. The MSGin5G Client 1 sends a message to a group as specified in clause 8.3.2 with following clarifications: + +- a) The MSGin5G message request includes Originating UE Service ID, Recipient Group Service ID and Message ID information elements from Table 8.3.2-1. The MSGin5G message request may include Delivery status required, Application ID, Payload and Priority type information elements from Table 8.3.2-1. +2. Upon receiving the MSGin5G message request to send the group message, the MSGin5G Server may send the message to the Application Server based on service ID present in the received MSGin5G message request (e.g. to log application specific message or for analytics). Otherwise go to step 4. + - a) Upon receiving the MSGin5G message request, the Application Server validates the message and if the message is not valid, the Application Server sends MSGin5G message response with delivery status set as Reject to the MSGin5G Server. Otherwise, go to step 3. + - b) The MSGin5G Server sends the MSGin5G message response with delivery status set as reject to the MSGin5G Client 1. The information elements defined in Table 8.3.2-3 are included in the response. Following procedures will be skipped. + 3. The Application Server initiates to send message to all group members and sends the MSGin5G message request to the MSGin5G Server. + +**Editor's note: Whether to keep or correct step 2 or 3 is FFS.** + +4. Upon receiving the MSGin5G message request, if the MSGin5G Server determines the MSGin5G Client-1 is authorized to send the group message, the MSGin5G Server resolves the group ID to determine the members of that group, based on the information from the group management server as specified in 3GPP TS 23.434 [5]. + +**NOTE:** If the originating UE is member of the group, the originating UE is not included as recipient of the group message. + +5. The MSGin5G Server sends the message to all participants of the group by their UE Service ID. The MSGin5G message request includes Originating UE Service ID, Recipient Group ID, Recipient UE Service ID, Message ID, Payload information elements from Table 8.3.3-1. The MSGin5G message request may include Delivery status required, Application ID and Priority type information elements from Table 8.3.3-1. The MSGin5G Server routes, using the procedures in clause 8.3.3, the message to: + - a) a MSGin5G UE, + - b) a Legacy 3GPP UE, + - c) a Non-3GPP UE. + +**NOTE:** Steps 5 a), 5 b) and 5 c) can happen in parallel and in any order. + +5. Upon receiving the group message, if message delivery status report is requested and if supported by target message client, the MSGin5G Client or Legacy 3GPP UE or Non-3GPP message client sends the message delivery status report to originator MSGin5G Client 1 as specified in clause 8.2.4 and 8.3.5. + +#### 8.7.4.3 Message delivery procedure from Application Server to group + +Figure 8.6.4.3-1 shows the MSGin5G Group messaging procedure in which the Application Server sends a message to a group. + +**Pre-conditions:** + +1. An MSGin5G Group is created by following group management SEAL service procedures as specified in 3GPP TS 23.434 [5]. + +![Sequence diagram for Group messaging in MSGin5G Service. Lifelines: Application Server, MSGin5G Server, UE2 (MSGin5G UE2) containing Application Client 2 and MSGin5G Client 2, Legacy 3GPP Message Gateway, UE3 (Legacy 3GPP UE) e.g. SMS, NIDD, Non-3GPP Message Gateway, UE4 (Non-3GPP UE) containing Non-3GPP Message Client. The sequence shows: 1. Application Server sends message to group; 2. MSGin5G Client, Legacy 3GPP message client, and Non-3GPP message client receive the message; 3. A message delivery status report is sent back to the Application Server.](d79de2dd022d74722a84f1b2ffce691c_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server + participant MS as MSGin5G Server + participant UE2 as UE2 (MSGin5G UE2) +Application Client 2, MSGin5G Client 2 + participant LG as Legacy 3GPP Message Gateway + participant UE3 as UE3 (Legacy 3GPP UE) +e.g. SMS, NIDD + participant NG as Non-3GPP Message Gateway + participant UE4 as UE4 (Non-3GPP UE) +Non-3GPP Message Client + + Note over AS, MS: 1. Application Server sends message to group as per clause 8.3.2 + AS->>MS: + Note over MS, UE2: 2a. MSGin5G Client receives message from group as per clause 8.7.2.1 + MS->>UE2: + Note over MS, UE3: 2b. Legacy 3GPP message client receives message from group as per clause 8.7.2.2 + MS->>LG: + LG->>UE3: + Note over MS, UE4: 2c. Non-3GPP message client receives message from group as per clause 8.7.2.3 + MS->>NG: + NG->>UE4: + Note over AS, UE4: 3. message delivery status report from MSGin5G Client or Legacy 3GPP Message Client or Non-3GPP Message Client. + UE2->>AS: + UE3->>AS: + UE4->>AS: + +``` + +Sequence diagram for Group messaging in MSGin5G Service. Lifelines: Application Server, MSGin5G Server, UE2 (MSGin5G UE2) containing Application Client 2 and MSGin5G Client 2, Legacy 3GPP Message Gateway, UE3 (Legacy 3GPP UE) e.g. SMS, NIDD, Non-3GPP Message Gateway, UE4 (Non-3GPP UE) containing Non-3GPP Message Client. The sequence shows: 1. Application Server sends message to group; 2. MSGin5G Client, Legacy 3GPP message client, and Non-3GPP message client receive the message; 3. A message delivery status report is sent back to the Application Server. + +**Figure 8.7.4.3-1: Group messaging in MSGin5G Service** + +1. The Application Server sends a message to a group as specified in clause 8.3.2. + 2. Upon receiving the MSGin5G message request, if the AS is authorized to send the group message, the MSGin5G Server resolves the group ID to determine the members of that group, based on the information from the group management server specified in 3GPP TS 23.434 [5]. + 3. The MSGin5G Server sends the message to all participants of the group based on UE Service ID. The MSGin5G message Request includes Originating AS Service ID, Recipient Group ID, Recipient UE Service ID, Message ID, Payload information elements from Table 8.3.3-1. The MSGin5G message Request may include Delivery Status Required, Application ID and Priority Type information elements from Table 8.3.3-1. The MSGin5G Server routes, using the procedures in clause 8.7.2, the message to: + - a) a MSGin5G UE, + - b) a Legacy 3GPP UE, + - c) a Non-3GPP UE. +- NOTE: Steps 3 a), 3 b) and 3 c) can happen in parallel and in any order. +4. Upon receiving the group message, if message delivery status report is requested and if supported by the target message client, the MSGin5G Client or Legacy 3GPP UE or Non-3GPP message client sends the message delivery status report to originator Application Server as specified in clause 8.3.4 and 8.3.5. + +## 8.7.5 Message delivery between different PLMNs + +### 8.7.5.1 General + +MSGin5G messages may be delivered between different PLMNs. + +The procedure specified in clause 8.7.5.2 applies to Point-to-Point message, Group message, and may also apply to AS-to-Point message and Point-to-AS message delivery if agreed by the business agreement between the PLMN operators. The procedure specified in clause 8.7.5.3 applies to Message delivery based on Messaging Topic. + +### 8.7.5.2 Inter-PLMN message exchange procedure + +Pre-condition: + +1. The Message Sender (e.g. MSGin5G Client 1 in MSGin5G UE 1) is registered to the MSGin5G Server 1 in one PLMN. +2. The Message Receiver (e.g. MSGin5G Client 2 in MSGin5G UE 2) is registered to the MSGin5G Server 2 in another PLMN. +3. MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection. + +Editor's Note: TS 33.501 does not specify how the connection is secured. + +Figure 8.7.5.2-1 shows message delivery between MSGin5G endpoints in different PLMNs, where the Message Sender is registered in MSGin5G Server 1 and the Message Receiver is registered in MSGin5G Server 2. + +![Sequence diagram showing message delivery between MSGin5G endpoints in different PLMNs. The diagram shows four lifelines: Message Sender, MSGin5G Server 1 (PLMN 1), MSGin5G Server 2 (PLMN 2), and Message Receiver. The sequence of messages is: 1. MSGin5G message request from Message Sender to MSGin5G Server 1; 2. MSGin5G message request from MSGin5G Server 1 to MSGin5G Server 2; 3. MSGin5G message request from MSGin5G Server 2 to Message Receiver; 4. MSGin5G message delivery status report from Message Receiver to MSGin5G Server 2; 5. MSGin5G message delivery status report from MSGin5G Server 2 to MSGin5G Server 1; 6. MSGin5G message delivery status report from MSGin5G Server 1 to Message Sender.](ff87509cc2b267501d910a2d9f9054ac_img.jpg) + +``` + +sequenceDiagram + participant MS as Message Sender + participant S1 as MSGin5G Server 1 (PLMN 1) + participant S2 as MSGin5G Server 2 (PLMN 2) + participant MR as Message Receiver + Note right of S1: PLMN 1 + Note right of S2: PLMN 2 + MS->>S1: 1. MSGin5G message request + S1->>S2: 2. MSGin5G message request + S2->>MR: 3. MSGin5G message request + MR->>S2: 4. MSGin5G message delivery status report + S2->>S1: 5. MSGin5G message delivery status report + S1->>MS: 6. MSGin5G message delivery status report + +``` + +Sequence diagram showing message delivery between MSGin5G endpoints in different PLMNs. The diagram shows four lifelines: Message Sender, MSGin5G Server 1 (PLMN 1), MSGin5G Server 2 (PLMN 2), and Message Receiver. The sequence of messages is: 1. MSGin5G message request from Message Sender to MSGin5G Server 1; 2. MSGin5G message request from MSGin5G Server 1 to MSGin5G Server 2; 3. MSGin5G message request from MSGin5G Server 2 to Message Receiver; 4. MSGin5G message delivery status report from Message Receiver to MSGin5G Server 2; 5. MSGin5G message delivery status report from MSGin5G Server 2 to MSGin5G Server 1; 6. MSGin5G message delivery status report from MSGin5G Server 1 to Message Sender. + +**Figure 8.7.5.2-1: Message delivery between MSGin5G UEs in different PLMNs** + +1. The Message Sender sends an MSGin5G message request to MSGin5G Server 1 in PLMN 1 as specified in clause 8.3.2. +2. The MSGin5G Server 1 analyses the target UE Service ID and determines that the message is targeted to the Message Receiver in PLMN 2, authenticates that the Message Sender is allowed to send a message to the Message Receiver, and then the MSGin5G Server 1 forwards the MSGin5G message request to MSGin5G Server 2 in PLMN 2. The MSGin5G message request contains the Information Elements as specified in table 8.3.3-1. +3. MSGin5G Server 2 forwards the MSGin5G message request to the Message Receiver as specified in clause 8.3.3. +- 4-6. If the message delivery status report is requested, the Message Receiver sends a message delivery status report to Message Sender as per procedure specified in clause 8.3.4 and 8.3.5. + +### 8.7.5.3 Inter-PLMN message exchange procedure based on Messaging Topic + +Figure 8.7.5.3-1 shows the inter-PLMN Message delivery based on Messaging Topic when MSGin5G Server 2 forwards the Messaging Topic subscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 1 as specified in clause 8.8.4. + +Pre-condition: + +1. The Message Sender (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 1 in PLMN 1. +2. The Message Receiver (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 2 in PLMN 2. +3. MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection. +4. MSGin5G Client or Application Server served by MSGin5G Server 2 has subscribed to a Messaging Topic with the MSGin5G Server 1 as specified in clause 8.8.4 via MSGin5G Server 2. + +![Sequence diagram showing message delivery between MSGin5G UEs in different PLMNs. The diagram involves four lifelines: Message Sender, MSGin5G Server 1 (PLMN 1), MSGin5G Server 2 (PLMN 2), and Message Receiver 1. The sequence of messages is: 1. MSGin5G message request from Message Sender to MSGin5G Server 1; 2. MSGin5G message request from MSGin5G Server 1 to MSGin5G Server 2; 3a. MSGin5G message request from MSGin5G Server 2 to Message Receiver 1; 4. MSGin5G message delivery status report from Message Receiver 1 to MSGin5G Server 2; 5. MSGin5G message delivery status report from MSGin5G Server 2 to MSGin5G Server 1; 6. MSGin5G message delivery status report from MSGin5G Server 1 to Message Sender.](56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg) + +``` + +sequenceDiagram + participant MS as Message Sender + participant S1 as MSGin5G Server 1 (PLMN 1) + participant S2 as MSGin5G Server 2 (PLMN 2) + participant R1 as Message Receiver 1 + + Note right of S1: PLMN 1 + Note right of S2: PLMN 2 + + MS->>S1: 1. MSGin5G message request + S1->>S2: 2. MSGin5G message request + S2->>R1: 3a. MSGin5G message request + R1->>S2: 4. MSGin5G message delivery status report + S2->>S1: 5. MSGin5G message delivery status report + S1->>MS: 6. MSGin5G message delivery status report + +``` + +Sequence diagram showing message delivery between MSGin5G UEs in different PLMNs. The diagram involves four lifelines: Message Sender, MSGin5G Server 1 (PLMN 1), MSGin5G Server 2 (PLMN 2), and Message Receiver 1. The sequence of messages is: 1. MSGin5G message request from Message Sender to MSGin5G Server 1; 2. MSGin5G message request from MSGin5G Server 1 to MSGin5G Server 2; 3a. MSGin5G message request from MSGin5G Server 2 to Message Receiver 1; 4. MSGin5G message delivery status report from Message Receiver 1 to MSGin5G Server 2; 5. MSGin5G message delivery status report from MSGin5G Server 2 to MSGin5G Server 1; 6. MSGin5G message delivery status report from MSGin5G Server 1 to Message Sender. + +**Figure 8.7.5.3-1: Message delivery between MSGin5G UEs in different PLMNs** + +1. The Message Sender sends an MSGin5G message request (if the sender is an MSGin5G UE) or API request (if the sender is an Application Server or a Message Gateway on behalf of a Non-MSGin5G UE) to MSGin5G Server 1 in PLMN 1 as specified in clause 8.3.2. A Messaging Topic is included in this request. +2. The MSGin5G Server 1 checks the subscriptions of the Messaging Topic included in the request and obtains the UE Service ID/AS Service ID of the Message Receivers. The MSGin5G Server 1 determines that the message with this Messaging Topic is needed to be delivered to an MSGin5G UE/Application Server served by Message Server 2 in PLMN 2 based on the UE Service ID/AS Service ID of the Message Receiver. The MSGin5G Server 1 then sends the MSGin5G message to MSGin5G Server 2. The MSGin5G message request contains the Information Elements as specified in table 8.3.3-1. +3. The MSGin5G Server 2 delivers the MSGin5G message request to Messenger Receiver based on the UE Service ID/AS Service ID in the message as specified in clause 8.3.3. +- 4-6. If the message delivery status report is requested, the Message Receiver sends message delivery status report to Message Sender as per procedure specified in clause 8.3.4 and 8.3.5. + +Figure 8.7.5.3-2 shows the inter-PLMN Message delivery to subscribing service endpoints based on Messaging Topic when MSGin5G Server 2 subscribes the Messaging Topic on behalf of all MSGin5G UEs/Application Servers served by it as specified in clause 8.8.4. + +Pre-condition: + +1. The Message Sender (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 1 in PLMN 1. +2. The Message Receiver (e.g. an MSGin5G UE, a Message Gateway on behalf of a Non-MSGin5G UE or an Application Server) is registered to the MSGin5G Server 2 in PLMN 2. +3. MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection. +4. MSGin5G Server 2 subscribed to a Messaging Topic with the MSGin5G Server 1 as specified in clause 8.8.4. A Messaging Topic with the MSGin5G Server 2 address of the subscriber has been created on MSGin5G Server 1. +5. The MSGin5G Client or Application Server served by MSGin5G Server 2 subscribed to the Messaging Topic with the MSGin5G Server 2. A Messaging Topic with the UE Service ID/AS Service ID of the subscriber has been created on MSGin5G Server 2. + +![Sequence diagram showing message delivery between MSGin5G UEs in different PLMNs. The diagram involves five lifelines: Message Sender, PLMN 1 MSGin5G Server 1, PLMN 2 MSGin5G Server 2, Message Receiver 1, and Message Receiver 2. The sequence starts with the Message Sender sending a request to Server 1. Server 1 then forwards it to Server 2. Server 2 delivers it to both Message Receiver 1 and Message Receiver 2. Delivery status reports are sent back from the receivers to the sender via the servers.](cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg) + +``` + +sequenceDiagram + participant MS as Message Sender + participant S1 as PLMN 1 MSGin5G Server 1 + participant S2 as PLMN 2 MSGin5G Server 2 + participant R1 as Message Receiver 1 + participant R2 as Message Receiver 2 + + Note right of S1: PLMN 1 + Note right of S2: PLMN 2 + + MS->>S1: 1. MSGin5G message request + S1->>S2: 2. MSGin5G message request + S2->>R1: 3a. MSGin5G message request + S2->>R2: 3b. MSGin5G message request + R1->>S2: 4a. MSGin5G message delivery status report + R2->>S2: 4b. MSGin5G message delivery status report + S2->>S1: 5a. MSGin5G message delivery status report + S2->>S1: 5b. MSGin5G message delivery status report + S1->>MS: 6a. MSGin5G message delivery status report + S1->>MS: 6b. MSGin5G message delivery status report + +``` + +Sequence diagram showing message delivery between MSGin5G UEs in different PLMNs. The diagram involves five lifelines: Message Sender, PLMN 1 MSGin5G Server 1, PLMN 2 MSGin5G Server 2, Message Receiver 1, and Message Receiver 2. The sequence starts with the Message Sender sending a request to Server 1. Server 1 then forwards it to Server 2. Server 2 delivers it to both Message Receiver 1 and Message Receiver 2. Delivery status reports are sent back from the receivers to the sender via the servers. + +**Figure 8.7.5.3-2: Message delivery between MSGin5G UEs in different PLMNs** + +1. The Message Sender sends an MSGin5G message request (if the sender is an MSGin5G UE) or API request (if the sender is an Application Server or a Message Gateway) to MSGin5G Server 1 in PLMN 1 as specified in clause 8.3.2. A Messaging Topic is included in this request. +2. The MSGin5G Server 1 checks the subscription of the Messaging Topic included in the request. The MSGin5G Server 1 determines that the message with this Messaging Topic is needed to be delivered to the Message Server 2 in PLMN 2 and sends the MSGin5G message to MSGin5G Server 2. The MSGin5G message request contains the Information Elements as specified in table 8.3.2-1. +- 3a The MSGin5G Server 2 checks the subscription of the Messaging Topic included in the inbound request. The MSGin5G Server 2 delivers the MSGin5G message request to Messenger Receiver 1 based on its UE Service ID/AS Service ID as specified in clause 8.8.2. +- 3b The MSGin5G Server 2 also delivers the MSGin5G message request to Messenger Receiver 2 which subscribed to this Messaging Topic as specified in clause 8.8.2. +- 4a-6a. If the message delivery status report is requested, the Message Receiver 1 sends message delivery status report to Message Sender as per procedure specified in clause 8.3.4 and 8.3.5. +- 4b-6b. If the message delivery status report is requested, the Message Receiver 2 sends message delivery status report to Message Sender as per procedure specified in clause 8.3.4 and 8.3.5. + +## 8.7.6 Broadcast message delivery + +### 8.7.6.1 General + +This clause introduces a Broadcast message procedure for an Application Server and an MSGin5G UE to send a Broadcast message. In this procedure, an MSGin5G message is delivered via broadcast to MSGin5G UEs or non-MSGin5G UEs in a Broadcast Area. + +### 8.7.6.2 Broadcast message delivery procedure + +Figure 8.7.6.2-1 shows the Broadcast message delivery procedure from Application Server or MSGin5G UE to the UEs in Broadcast Area. + +Pre-condition: + +1. Application Server or MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server. + +![Sequence diagram showing Message Delivery in Broadcast Area. Lifelines: Application Server or MSGin5G UE, MSGin5G Server, Broadcast Message Gateway, CBCF (dashed box), and UEs in Broadcast Area. The sequence consists of four steps: 1. Application Server or MSGin5G Client sends message to MSGin5G Server; 2. MSGin5G Server determines authorization; 3. MSGin5G Server forwards message to CBCF via Broadcast Message Gateway; 4. Broadcast Message Gateway delivers message to CBCF, which then broadcasts to UEs.](235e996e83e7d5198cf9d909f5713cdd_img.jpg) + +``` + +sequenceDiagram + participant AS as Application Server or MSGin5G UE + participant MS as MSGin5G Server + participant BMG as Broadcast Message Gateway + participant CBCF as CBCF + participant UEs as UEs in Broadcast Area + + Note left of AS: 1. Application Server or MSGin5G Client sends message to MSGin5G Server as specified in 8.3.2 + AS->>MS: + Note right of MS: 2. Determine that the MSGin5G Client or Application Server is authorized to send broadcast message + MS->>MS: + Note right of MS: 3. MSGin5G Server forwards Broadcast message to CBCF via Broadcast message Gateway as specified in 8.3.3 + MS->>BMG: + Note right of BMG: 4. Broadcast message Gateway delivers the message to the CBCF, and CBCF broadcasts the message as specified in 3GPP TS 23.041 [14] + BMG-->>CBCF: + Note right of CBCF: + CBCF-->>UEs: + +``` + +Sequence diagram showing Message Delivery in Broadcast Area. Lifelines: Application Server or MSGin5G UE, MSGin5G Server, Broadcast Message Gateway, CBCF (dashed box), and UEs in Broadcast Area. The sequence consists of four steps: 1. Application Server or MSGin5G Client sends message to MSGin5G Server; 2. MSGin5G Server determines authorization; 3. MSGin5G Server forwards message to CBCF via Broadcast Message Gateway; 4. Broadcast Message Gateway delivers message to CBCF, which then broadcasts to UEs. + +**Figure 8.7.6.2-1: Message Delivery in Broadcast Area** + +1. An MSGin5G message request is sent by an Application Server or an MSGin5G UE to the MSGin5G Server as specified in clause 8.3.2 with following clarifications: + - a) The MSGin5G message includes Originating UE Service ID/AS service ID, Broadcast Area ID and Message ID information elements in Table 8.3.2-1, and may include Delivery status required, Application ID, Payload information elements from Table 8.3.2-1. +2. The MSGin5G Server determines if the Application Server or MSGin5G Client is authorized to send a Broadcast message. +3. The MSGin5G Server forwards the Broadcast message request to the CBCF (as specified in 3GPP TS 23.041 [14]) via the Broadcast Message Gateway based on the Broadcast Area ID as specified in 8.3.3. +4. The Broadcast Message Gateway delivers the message to the CBCF which broadcasts the message to the MSGin5G UEs in the Broadcast Area or to the non-MSGin5G UEs in the Broadcast Area. This step is out of scope of the present specification. + +If the Delivery status requested information element is included in the MSGin5G Broadcast message, a recipient MSGin5G UE sends the delivery report as specified in clause 8.3.4. + +## 8.8 Other MSGin5G messaging related procedures + +### 8.8.0 General + +In order to receive the message with a specific Messaging Topic, a UE or an Application Server subscribes to this Messaging Topic. The procedures of a MSGin5G Server creating a Messaging Topic and a UE or an Application Server subscribing/unsubscribing one or more Messaging Topic(s) from an MSGin5G Server are specified in clause 8.8.1 and clause 8.8.3. + +When a Messaging Topic(s) has already been created on a different MSGin5G server, an MSGin5G Server needs to learn the available Messaging Topics on the other MSGin5G Server. An MSGin5G Server may use the Messaging Topic list subscription procedure specified in clause 8.8.4.2 to learn the Messaging Topics available on the other MSGin5G Server. The corresponding Messaging Topic list unsubscription procedure is specified in clause 8.8.4.2a. + +An MSGin5G Server may subscribe one or more Messaging Topic(s) on the other MSGin5G Server on behalf of the UE(s) and/or Application Server(s) if the Messaging Topic list are not hosted locally. The procedure of MSGin5G Server subscribing one or more Messaging Topic(s) from the other MSGin5G Server is specified in clause 8.8.4.3 and the corresponding unsubscription procedure is specified in clause 8.8.4.4. + +A MSGin5G Server may also forward a subscription request to the MSGin5G Server that already handles the Messaging Topic. + +## 8.8.1 Messaging Topic Subscription + +An MSGin5G Client or an Application Server can subscribe one or more Messaging Topic(s) on the MSGin5G Server. The Messaging Topic IE will be populated by the Application Client or the Application Server and the content of this IE is out of scope. + +When an MSGin5G Client or an Application Server is subscribed to a Messaging Topic, then the MSGin5G Server will deliver messages that contain the same Messaging Topic to the subscribers. + +Figure 8.8.1-1 shows the MSGin5G Client/Application Server subscribing to Messaging Topic(s) on the MSGin5G Server. + +Pre-conditions: + +1. The MSGin5G Client or Application Server has registered to the MSGin5G Server. + +![Sequence diagram showing the subscription process between an MSGin5G Client/Application Server and an MSGin5G Server. The client sends a '1. Messaging Topic subscription request' to the server. The server then performs an internal step '2. Records the subscription' (indicated by a dashed box) and sends back a '3. Messaging Topic subscription response' to the client.](07b81106e8525814c458f262000c54a9_img.jpg) + +``` + +sequenceDiagram + participant Client as MSGin5G Client/Application Server + participant Server as MSGin5G Server + Note right of Server: 2. Records the subscription + Client->>Server: 1. Messaging Topic subscription request + Server-->>Client: 3. Messaging Topic subscription response + +``` + +Sequence diagram showing the subscription process between an MSGin5G Client/Application Server and an MSGin5G Server. The client sends a '1. Messaging Topic subscription request' to the server. The server then performs an internal step '2. Records the subscription' (indicated by a dashed box) and sends back a '3. Messaging Topic subscription response' to the client. + +**Figure 8.8.1-1: MSGin5G Service endpoint subscribes to Messaging topic(s)** + +1. The MSGin5G Client or Application Server sends a Messaging Topic subscription request to the MSGin5G Server. The request includes the information elements listed in Table 8.8.1-1. + +**Table 8.8.1-1: Messaging Topic subscription request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID | M | The service identity of the sending MSGin5G Client or the sending Application Server. | +| Messaging Topic | M | A list of Messaging Topic(s) that is to be subscribed. The number of Messaging Topic(s) included in this IE can be one or more. | +| Expiration | O | The date and time when the subscription expires. This date and time apply to all Messaging Topic(s) subscribed in this request.
If this IE is included, the value of it should be larger than 0.
If this IE is not included, the expiration time is subject to operator policy. | +| NOTE: The content of the Messaging Topic is out of scope of the present document. | | | + +2. The MSGin5G Server validates the Messaging Topic subscription request and checks the locally stored Messaging Topic(s). + +- a) If the subscribed Messaging Topic has already been created, the MSGin5G Server checks whether the UE Service ID/AS Service ID of the subscriber is already included in the subscribers list of this Messaging Topic. + 1. If not, the MSGin5G Server adds the UE Service ID/AS Service ID of the subscriber to the subscribers list of this Messaging Topic. The MSGin5G Server sets the validity time of this subscription to the value of the Expire IE or to a default value according to the service policy. + 2. Else, the MSGin5G Server updates the validity time of this subscription. +- b) If the subscribed Messaging Topic has not been already created, the MSGin5G Server creates this Messaging Topic, and adds the UE Service ID/AS Service ID of the subscriber to the subscribers list of this Messaging Topic. The MSGin5G Server sets the validity time of this subscription to the value of the Expire IE or to a default value according to the service policy. +3. The MSGin5G Server sends a Messaging Topic Subscription response to the originator of the request. The response includes the information listed in Table 8.8.1-2. + +**Table 8.8.1-2: Messaging Topic Subscription response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------| +| Subscription status | M | Indicates whether the subscription was successfully added or deleted on the MSGin5G Server. | +| Expiration | O | The validity date and time of this subscription set by the MSGin5G Server. | + +## 8.8.2 Message delivery based on Messaging Topic + +If an MSGin5G Client or an Application Server is in the subscribers list of a Messaging Topic, the MSGin5G Server delivers messages that contain this Messaging Topic to it. + +Figure 8.8.2-1 shows the Message delivery to a subscribing service endpoint based on Messaging Topic. + +Pre-conditions: + +1. The MSGin5G Client or Application Server subscribed to a Messaging Topic with the MSGin5G Server. A Messaging Topic with the UE Service ID/AS Service ID of the subscriber has been created. + +![Sequence diagram showing message delivery from MSGin5G Server to MSGin5G Client/Application Server. Step 1: MSGin5G Message or API Message received for the Messaging Topic (dashed box). Step 2: MSGin5G outbound messages from the MSGin5G Server as specified in clause 8.3.3.](e451a51157214e53bd9c64db914771cc_img.jpg) + +``` + +sequenceDiagram + participant Client as MSGin5G Client/ +Application Server + participant Server as MSGin5G Server + Note right of Server: 1. MSGin5G Message or API +Message received for the +Messaging Topic + Server->>Client: 2. MSGin5G outbound messages from the MSGin5G Server as +specified in clause 8.3.3 + +``` + +Sequence diagram showing message delivery from MSGin5G Server to MSGin5G Client/Application Server. Step 1: MSGin5G Message or API Message received for the Messaging Topic (dashed box). Step 2: MSGin5G outbound messages from the MSGin5G Server as specified in clause 8.3.3. + +**Figure 8.8.2-1: Message delivery to subscribing service endpoint based on Messaging Topic** + +1. The MSGin5G Server receives an MSGin5G message request or an API message request corresponding to step 2 in figures 8.3.2-1 or 8.3.2-2 which includes the IEs as listed in table 8.3.2-1. The MSGin5G message request or API message request contains a Messaging Topic IE corresponding to the Messaging Topic for which subscription(s) exist. +2. The MSGin5G Server uses the procedure described in clause 8.3.3 to deliver the message to all subscriber(s) of this Messaging Topic. In each message, the UE Service ID/AS Service ID of subscriber should be added as the Recipient UE Service ID/AS Service ID IE specified in table 8.3.3-1. + +### 8.8.3 Messaging Topic Unsubscription + +Corresponding to message topic subscription, an MSGin5G Client or an Application Server can unsubscribe from one or more Messaging Topic(s) on the MSGin5G Server. + +Figure 8.8.3-1 shows the MSGin5G Client/Application Server unsubscribing to Messaging Topic(s) on the MSGin5G Server. + +Pre-condition + +1. The MSGin5G Client or Application Server has subscribed one or more message topic(s) on the MSGin5G Server. + +![Sequence diagram showing the unsubscription process between MSGin5G Client/Application Server and MSGin5G Server.](c995e0bb4efc8c0f2994428aa1245709_img.jpg) + +``` + +sequenceDiagram + participant Client as MSGin5G Client/Application Server + participant Server as MSGin5G Server + Note right of Server: 2. Remove previous message topic subscription + Client->>Server: 1. Messaging Topic unsubscription request + Server-->>Client: 3. Messaging Topic unsubscription response + +``` + +Sequence diagram showing the unsubscription process between MSGin5G Client/Application Server and MSGin5G Server. + +**Figure 8.8.3-1: MSGin5G Service endpoint unsubscribes to Messaging topic(s)** + +1. The MSGin5G Client or Application Server sends a Messaging Topic unsubscription request to the MSGin5G Server. The request includes the information listed in Table 8.8.3-1. + +**Table 8.8.3-1: Messaging Topic unsubscription request** + +| Information element | Status | Description | +|-----------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID | M | The service identity of the sending MSGin5G Client or the sending Application Server. | +| Messaging Topic(s) | M | A list of Messaging Topic(s) that is to be unsubscribed. The number of Messaging Topic(s) included in this IE can be one or more. | + +2. The MSGin5G Server validates the Messaging Topic unsubscription request and checks the locally stored Messaging Topic(s). If the UE Service ID/AS Service ID is included in the subscribers list of this Messaging Topic, the MSGin5G Server removes the UE Service ID/AS Service ID from the subscribers list of this Messaging Topic. +3. The MSGin5G Server sends a Messaging Topic Unsubscription response to the originator of the request. The response includes the information listed in Table 8.8.3-2. + +**Table 8.8.3-2: Messaging Topic Unsubscription response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------| +| subscription status | M | Indicates whether the subscription was successfully deleted on the MSGin5G Server | + +NOTE: If the MSGin5G Server holds no more subscriptions for a Messaging Topic then how to handle the locally stored Messaging Topic is implementation specific. + +## 8.8.4 Messaging Topic Subscription handling between different MSGin5G Servers + +### 8.8.4.1 General + +When a Messaging Topic(s) is handled between different MSGin5G Servers, the MSGin5G Server 1 may work in the following models, when the subscription for the Messaging Topic exists on Server 2: + +- Mod.A: the MSGin5G UE/Application Server served by MSGin5G Server 1 subscribes to Messaging Topic(s) and the MSGin5G Server 1 forwards Messaging Topic subscription request from the MSGin5G UE/Application Server to MSGin5G Server 2 or +- Mod.B: the MSGin5G UE/Application Server served by MSGin5G Server 1 subscribes to Messaging Topic(s) and the MSGin5G Server 1 subscribes to the Messaging Topic(s) on Server 2 on behalf of all MSGin5G UE/Application Server served by it. + +If the subscription for the Messaging Topic already exists on Server 1, or if the subscription does not exist either on Server 1 or on Server 2, the procedure in clause 8.8.1 applies. + +The MSGin5G Server may work in one model based on the service policy. The MSGin5G Server 1 and MSGin5G Server 2 can be located in the same PLMN or different PLMNs. + +To enable the message delivery based on Messaging Topic between different MSGin5G Servers, an MSGin5G Server shall subscribe the Messaging Topic list from other MSGin5G Servers as specified in clause 8.8.4.2. If the Messaging Topic is created or deleted on an MSGin5G Server, and if there are Messaging Topic list subscriptions from other MSGin5G Server(s), the MSGin5G Server shall send a Messaging Topic list notification to the corresponding MSGin5G Server(s) as specified in clause 8.8.4.2. When an MSGin5G Server receives a Messaging Topic subscription or unsubscription from an MSGin5G Client, it shall handle the Messaging Topic subscription or unsubscription request as specified in clause 8.8.4.3 or clause 8.8.4.4. + +**Editor's note:** If a Messaging Topic creation procedure, where Messaging Topic subscription management is controlled by the MSGin5G Server, is required is FFS. + +### 8.8.4.2 Messaging Topic list subscription + +Before the subscribing of Messaging Topic(s), the MSGin5G Server 1 should obtain the available Messaging Topic list on the MSGin5G Server 2 to determine whether to forward the Messaging Topic subscription request to MSGin5G Server 2, to subscribe to the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it on MSGin5G Server 2, or to create the subscription on Server 1 as specified in clause 8.8.1 if the subscription does not exist on Server 2. + +Figure 8.8.4.2-1 shows the MSGin5G Server 1 subscribing to Messaging Topic list on the MSGin5G Server 2. + +NOTE 1: If the MSGin5G Server 1 and MSGin5G Server 2 are located in the same PLMN, the synchronization of Messaging Topic list between MSGin5G Servers may also be implementation specific. + +Pre-conditions: + +1. MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection. + +**Editor's Note:** How a secure connection between two MSGin5G Servers is to be established is FFS. + +![Sequence diagram showing MSGin5G Server 1 subscribing to the Messaging Topic list on MSGin5G Server 2. The steps are: 1. Subscription request from Server 1 to Server 2; 2. Authentication and Authorization (dashed box); 3. Records the subscription (dashed box); 4. Subscription response from Server 2 to Server 1; 5. Checks if notification is needed (dashed box); 6. Notification from Server 2 to Server 1; 7. Updates the Messaging Topic list (dashed box) on Server 1.](81a0abf9a79b27cf9d765553216b173c_img.jpg) + +``` + +sequenceDiagram + participant S1 as MSGin5G Server 1 + participant S2 as MSGin5G Server 2 + Note right of S2: 2. Authentication and Authorization + Note right of S2: 3. Records the subscription + S1->>S2: 1. Messaging Topic list subscription request + S2-->>S1: 4. Messaging Topic list subscription response + Note right of S2: 5. checks whether Messaging Topic list notification is needed + S2-->>S1: 6. Messaging Topic list notification + Note left of S1: 7. Updates the Messaging Topic list + +``` + +Sequence diagram showing MSGin5G Server 1 subscribing to the Messaging Topic list on MSGin5G Server 2. The steps are: 1. Subscription request from Server 1 to Server 2; 2. Authentication and Authorization (dashed box); 3. Records the subscription (dashed box); 4. Subscription response from Server 2 to Server 1; 5. Checks if notification is needed (dashed box); 6. Notification from Server 2 to Server 1; 7. Updates the Messaging Topic list (dashed box) on Server 1. + +**Figure 8.8.4.2-1: MSGin5G Server 1 subscribes to Messaging Topic list on the MSGin5G Server 2** + +1. The MSGin5G Server 1 sends a Messaging Topic list subscription request to the MSGin5G Server 2. The request includes the information elements listed in Table 8.8.4.2-1. + +**Table 8.8.4.2-1: Messaging Topic list subscription request** + +| Information element | Status | Description | +|-------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating MSGin5G Server ID | M | The MSGin5G Server which requests the Messaging Topic list. | +| Recipient MSGin5G Server ID | M | The MSGin5G Server which holds the Messaging Topic list. | +| Security credentials | O | Security information required by the MSGin5G Server 2 and is left for implementation. | +| Expiration | O | The date and time when the subscription expires. If this IE is included, the value of it should be larger than 0. If this IE is not included, the expiration time is subject to operator policy. | + +2. Upon receiving the Messaging Topic list subscription request, the MSGin5G Server 2 validates this request and may verify the security credentials. +3. The MSGin5G Server 2 checks the locally stored Messaging Topic list subscription(s). + - a) If the MSGin5G Server 1's subscription has already been created, the MSGin5G Server 2 updates the validity time of this subscription. + - b) If the MSGin5G Server 1's subscription has not been created, the MSGin5G Server 2 creates the subscription. +4. The MSGin5G Server 2 sends a Messaging Topic list Subscription response to MSGin5G Server 1. The response includes the information listed in Table 8.8.4.2-2. + +**Table 8.8.4.2-2: Messaging Topic list Subscription response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------------| +| Subscription status | M | Indicates whether the subscription was successfully added or deleted on the MSGin5G Server 2. | +| Expiration | O | The validity date and time of this Messaging Topic list subscription set by the MSGin5G Server 2. | + +5. The MSGin5G Server 2 checks whether Messaging Topic list notification is needed, e.g. whether the MSGin5G Server 1 subscribes the Messaging Topic list on MSGin5G Server 2 for the first time, or the local Messaging Topic(s) on the MSGin5G Server 2 are updated, e.g. new Messaging Topic(s) has been created or existing Messaging Topic(s) has been deleted. + +NOTE 2: If the MSGin5G Server 1 has previously unsubscribed the Messaging Topic list on MSGin5G Server 2, the MSGin5G Server 2 should consider that the MSGin5G Server 1 subscribes the Messaging Topic list on MSGin5G Server 2 for the first time when the MSGin5G Server 1 subscribes the Messaging Topic list again. + +6. If Messaging Topic list notification is needed, the MSGin5G Server 2 sends a Messaging Topic list notification to MSGin5G Server 1. The notification includes the information listed in Table 8.8.4.2-3. + +**Table 8.8.4.2-3: Messaging Topic list notification** + +| Information element | Status | Description | +|-----------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Expiration | O | The new validity date and time of this subscription set by the MSGin5G Server 2. | +| >Messaging Topic list | M | A list of Messaging Topic(s) that exists on the MSGin5G Server 2.
If the MSGin5G Server 1 subscribes the Messaging Topic list on MSGin5G Server 2 for the first time, the MSGin5G Server 2 should include all Messaging Topic(s) that exist on the MSGin5G Server 2 in this Messaging Topic list, else the MSGin5G Server 2 includes the deviation of Messaging Topic(s) since the last notification, Each element in this list contains information as specified in Table 8.8.4.2-4.
Based on service policy, the MSGin5G Server 2 may only include a part of Messaging Topic(s) in the notification which are allowed to be subscribed by MSGin5G Server 1. | + +**Table 8.8.4.2-4: Individual Messaging Topic** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------| +| Messaging Topic | M | Unique identifier of this Messaging Topic. | +| Update status | M | Identifies the Messaging Topic is newly created on the MSGin5G Server 2, or newly deleted on the MSGin5G Server 2 | + +7. Upon receiving the Messaging Topic list notification, the MSGin5G Server 1 updates the locally stored Messaging Topic list: +- if the Update status of a Messaging Topic is Created, the MSGin5G Server 1 adds the Messaging Topic to the locally stored Messaging Topic list; and + - if the Update status of a Messaging Topic is Deleted, + - if the Messaging Topic exists on MSGin5G Server 1, the MSGin5G Server 1 removes the Messaging Topic from the locally stored Messaging Topic list; and + +- ii) if the Messaging Topic does not exist on MSGin5G Server 1, the MSGin5G Server 1 ignores this Messaging Topic update. + +NOTE 3: The MSGin5G Server should not send Messaging Topic list notification to other MSGin5G Servers if its locally stored Messaging Topic list is updated by receiving a Messaging Topic list notification. + +### 8.8.4.2a Messaging Topic list unsubscription + +Corresponding to message topic list subscription, the MSGin5G Server 1 can unsubscribe the available Messaging Topic list on the MSGin5G Server 2 if it decides to stop to forward the Messaging Topic subscription request to MSGin5G Server 2, or to subscribe to the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it on MSGin5G Server 2, based on decision of service provider. + +Figure 8.8.4.2a-1 shows the MSGin5G Server 1 unsubscribing to Messaging Topic list on the MSGin5G Server 2. + +Pre-conditions: + +1. MSGin5G Server 1 and MSGin5G Server 2 have established a secured connection. +2. The MSGin5G Server 1 has subscribed Messaging Topic list on the MSGin5G Server 2. + +![Sequence diagram showing MSGin5G Server 1 sending an unsubscribe request to MSGin5G Server 2, which then performs internal steps (Authentication and Authorization, remove previous subscription) and returns a response.](19499072f755b22d0a231123f75fa477_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G Server 1 + participant MSGin5G Server 2 + Note right of MSGin5G Server 2: 2. Authentication and Authorization + Note right of MSGin5G Server 2: 3. remove previous Message Topic list subscription + MSGin5G Server 1->>MSGin5G Server 2: 1. Messaging Topic list unsubscribe request + MSGin5G Server 2-->>MSGin5G Server 1: 4. Messaging Topic list unsubscribe response + +``` + +Sequence diagram showing MSGin5G Server 1 sending an unsubscribe request to MSGin5G Server 2, which then performs internal steps (Authentication and Authorization, remove previous subscription) and returns a response. + +**Figure 8.8.4.2a-1: MSGin5G Server 1 unsubscribes to Messaging Topic list on the MSGin5G Server 2** + +1. The MSGin5G Server 1 sends a Messaging Topic list unsubscribe request to the MSGin5G Server 2. The request includes the information elements listed in Table 8.8.4.2a-1. + +**Table 8.8.4.2a-1: Messaging Topic list unsubscribe request** + +| Information element | Status | Description | +|------------------------------------|--------|---------------------------------------------------------------------------------------| +| Originating MSGin5G Server address | M | The MSGin5G Server which requests the unsubscription of the Messaging Topic list. | +| Recipient MSGin5G Server address | M | The MSGin5G Server which holds the Messaging Topic list. | +| Security credentials | O | Security information required by the MSGin5G Server 2 and is left for implementation. | + +2. Upon receiving the Messaging Topic list unsubscribe request, the MSGin5G Server 2 validates this request and may verify the security credentials. +3. The MSGin5G Server 2 checks the locally stored Messaging Topic list subscription(s) and removes previous Message Topic list subscription from MSGin5G Server 1. +4. The MSGin5G Server 2 sends a Messaging Topic list unsubscribe response to MSGin5G Server 1. The response includes the information listed in Table 8.8.4.2a-2. + +**Table 8.8.4.2a-2: Messaging Topic list Subscription response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------| +| Subscription status | M | Indicates whether the subscription was successfully deleted on the MSGin5G Server | + +### 8.8.4.3 Messaging Topic Subscription between different MSGin5G Servers + +If the MSGin5G Server 1 works in Mod.A (see clause 8.8.4.1), upon receiving a Messaging Topic subscription request from MSGin5G Client or Application Server, if the Messaging Topic is included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 forwards the Messaging Topic subscription request to MSGin5G Server 2. Otherwise, the MSGin5G Server 1 handles the Messaging Topic subscription request as specified in clause 8.8.3. + +If the MSGin5G Server 1 works in Mod.B (see clause 8.8.4.1), upon receiving a Messaging Topic subscription request from MSGin5G Client or Application Server, if the Messaging Topic is not included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 handles the Messaging Topic subscription request as specified in clause 8.8.1. Otherwise, it may subscribe one or more Messaging Topic(s) from the Messaging Topic list by using the procedure specified in clause 8.8.1 with the clarification listed below. + +The procedure for the Messaging Topic subscription for both Mod. A and Mod. B. between MSGin5G Servers is as follows: + +- The MSGin5G Server 1 includes the information elements listed in Table 8.8.4.3-1 instead of the information elements listed in Table 8.8.1-1. + +**Table 8.8.4.3-1: Messaging Topic subscription request** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID (see NOTE 1) | O | The service identity of the sending MSGin5G Client or the sending Application Server.
This IE shall be included if MSGin5G Server 1 forwards Messaging Topic subscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 2. | +| MSGin5G Server address (see NOTE 1) | O | The MSGin5G Server which subscribes the Messaging Topic(s).
This IE shall be included if MSGin5G Server 1 subscribe the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it. | +| Security credentials | O | Security information required by the MSGin5G Server 2 and is left for implementation. | +| Messaging Topic (see NOTE 2) | M | A list of Messaging Topic(s) that is to be subscribed. The number of Messaging Topic(s) included in this IE can be one or more. | +| Expiration | O | The date and time when the subscription expires. This date and time apply to all Messaging Topic(s) subscribed in this request.
If this IE is included, the value of it should be larger than 0.
If this IE is not included, the expiration time is subject to operator policy. | +| NOTE 1: Only one of these IEs shall be included.
NOTE 2: The content of the Messaging Topic is out of scope of 3GPP specifications. | | | + +- Upon receiving the Messaging Topic subscription request, the MSGin5G Server 2 validates this request and may verify the security credentials. +- The MSGin5G Server 2 handles the Originating UE Service ID/AS Service ID or MSGin5G Server address included in the Messaging Topic subscription request as the UE Service ID/AS Service ID included in Table 8.8.1-1. + +#### 8.8.4.4 Messaging Topic Unsubscription between different MSGin5G Servers + +If the MSGin5G Server 1 works in Mod.A (see clause 8.8.4.1), and upon receiving a Messaging Topic unsubscription request from MSGin5G Client or Application Server, and if the Messaging Topic is included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 forwards the Messaging Topic unsubscription request to MSGin5G Server 2. Otherwise, the MSGin5G Server 1 handles the Messaging Topic unsubscription request as specified in clause 8.8.1. + +If the MSGin5G Server 1 works in Mod.B (see clause 8.8.4.1), it may also unsubscribe one or more Messaging Topic(s) from the Messaging Topic list held on MSGin5G Server 2 by using the procedure specified in clause 8.8.3 with the clarification listed below. + +The procedure for the Messaging Topic unsubscription for both Mod. A and Mod. B. between MSGin5G Servers is as follows: + +1. The MSGin5G Server 1 includes the information elements listed in Table 8.8.4.4-1 instead of the information elements listed in Table 8.8.3-1. + +**Table 8.8.4.4-1: Messaging Topic unsubscription request** + +| Information element | Status | Description | +|------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Originating UE Service ID/AS Service ID (see NOTE 1) | O | The service identity of the sending MSGin5G Client or the sending Application Server.
This IE shall be included if MSGin5G Server 1 forwards Messaging Topic unsubscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 2. | +| MSGin5G Server address (see NOTE 1) | O | The MSGin5G Server which unsubscribes the Messaging Topic(s).
This IE shall be included if MSGin5G Server 1 subscribe the Messaging Topic on behalf of all MSGin5G UE/Application Server served by it. | +| Security credentials | O | Security information required by the MSGin5G Server 2 and is left for implementation. | +| Messaging Topic | M | A list of Messaging Topic(s) that is to be unsubscribed. The number of Messaging Topic(s) included in this IE can be one or more. | +| NOTE 1: Only one of these IEs shall be included. | | | + +2. Upon receiving the Messaging Topic unsubscription request, the MSGin5G Server 2 validates this request and may validate the security credentials. +3. The MSGin5G Server 2 handles the Originating UE Service ID/AS Service ID or MSGin5G Server address included in the Messaging Topic unsubscription request as the UE Service ID/AS Service ID included in Table 8.8.3-1. + +## 8.9 Usage of Network Capabilities + +### 8.9.1 General + +The present clause specifies the functionality leveraged by the MSGin5G Service via Core Network exposure. + +### 8.9.2 UE reachability status monitoring + +#### 8.9.2.1 General + +UE reachability status leverages the 3GPP network monitoring functionality exposed via T8/N33 reference point detailed in 3GPP TS 23.502 [7] and TS 29.522[10]. The MSGin5G Server may use the UE reachability status monitoring by using the 3GPP Network capabilities based on the information, i.e. whether UE reachability status monitoring is needed to be used for this message, received from the Application Server, i.e. based on Information Elements specified in clause 9.1.2.1 or based on the information received from the MSGin5G Client, i.e. based on + +Information Elements specified in clause 8.11.4. How (e.g., via request/response or subscription) to monitor the UE reachability using the 3GPP Network capabilities is implementation dependent. + +NOTE 1: Use of the UE reachability status monitoring procedure in the application layer has no impact to how the Core Network delivers the message to the UE. + +NOTE 2: MSGin5G Service provider policies may indicate whether the UE reachability status monitoring feature is enabled or not. + +## 8.9.2.2 Procedures + +### 8.9.2.2.1 Request-response + +Figure 8.9.2.2.1-1 shows the procedure which may be used by the MSGin5G Server to make a request for UE reachability status information. + +Pre-conditions: + +1. A UE hosts an MSGin5G Client. +2. The MSGin5G Client has registered with the MSGin5G Server and has shared UE contact information. +3. The MSGin5G Server has determined to subscribe for monitoring of UE reachability events in the Core Network, e.g., that the UE is a sleepy node. + +NOTE: How the MSGin5G Server subscribes for monitoring of UE reachability events in the Core Network is implementation dependent. + +![Sequence diagram showing the MSGin5G reachability status request-response procedure between the 3GPP Network and the MSGin5G Server.](43437211ce989e9da795fecc0d499c05_img.jpg) + +``` +sequenceDiagram + participant 3GPP Network + participant MSGin5G Server + Note right of MSGin5G Server: 1. Monitoring request via SCEF/NEF + MSGin5G Server->>3GPP Network: 1. Monitoring request via SCEF/NEF + Note left of 3GPP Network: 2. Determine UE Reachability status + 3GPP Network->>3GPP Network: 2. Determine UE Reachability status + Note right of 3GPP Network: 3. Monitoring response via SCEF/NEF + 3GPP Network->>MSGin5G Server: 3. Monitoring response via SCEF/NEF +``` + +Sequence diagram showing the MSGin5G reachability status request-response procedure between the 3GPP Network and the MSGin5G Server. + +Figure 8.9.2.2.1-1: MSGin5G reachability status request-response. + +1. The MSGin5G Server sends a one-time Monitoring Request to the 3GPP Network using SCEF/NEF capabilities. + +The one-time Monitoring Request includes monitoring type set to UE\_REACHABILITY, Maximum Number of Reports of 1 and does not include the Monitoring Duration IE. + +2. The 3GPP network processes the monitoring request and determines the reachability status of the UE(s), as described in 3GPP TS 29.122 [9]. + +3. If the Monitoring Request is successfully processed, a monitoring response providing the UE(s) reachability status is sent to the MSGin5G Server. The response may include idle mode information e.g., active time granted to the UE, eDRX cycle length, periodic RAU/TAU timer., depending on the parameters indicated in the request. + +#### 8.9.2.2.2 Subscribe + +Figure 8.9.2.2.2-1 shows the procedure which may be used by the MSGin5G Server to subscribe for monitoring of UE reachability. + +Pre-conditions: + +1. A UE hosts an MSGin5G Client. +2. The MSGin5G Client has registered with the MSGin5G Server and has shared UE contact information. +3. The MSGin5G Server subscribes for monitoring of UE reachability events in the Core Network, e.g., that the UE is a sleepy node, based on the information, i.e. whether UE reachability status monitoring is needed to be used for this message, received from the Application Server or MSGin5G Client. + +NOTE: How the MSGin5G Server subscribes for monitoring of UE reachability events in the Core Network is implementation dependent. + +![Sequence diagram for MSGin5G reachability status subscribe. The diagram shows two lifelines: 3GPP Network and MSGin5G Server. The MSGin5G Server sends a '1. Monitoring Event subscribe event via SCEF/NEF' to the 3GPP Network. The 3GPP Network then performs '3. Handling Monitoring Event Subscription' and sends a '3. Monitoring Event subscribe response via SCEF/NEF' back to the MSGin5G Server.](27f9c45d41672d72c3cc3c2ea386ebbb_img.jpg) + +``` + +sequenceDiagram + participant MSGin5G Server + participant 3GPP Network + Note right of MSGin5G Server: 1. Monitoring Event subscribe event via SCEF/NEF + MSGin5G Server->>3GPP Network: 1. Monitoring Event subscribe event via SCEF/NEF + Note left of 3GPP Network: 3. Handling Monitoring Event Subscription + 3GPP Network->>MSGin5G Server: 3. Monitoring Event subscribe response via SCEF/NEF + +``` + +Sequence diagram for MSGin5G reachability status subscribe. The diagram shows two lifelines: 3GPP Network and MSGin5G Server. The MSGin5G Server sends a '1. Monitoring Event subscribe event via SCEF/NEF' to the 3GPP Network. The 3GPP Network then performs '3. Handling Monitoring Event Subscription' and sends a '3. Monitoring Event subscribe response via SCEF/NEF' back to the MSGin5G Server. + +**Figure 8.9.2.2.2-1: MSGin5G reachability status subscribe.** + +1. The MSGin5G Server sends a Monitoring Event Subscribe request to the 3GPP Network using existing SCEF/NEF capabilities. + +The Monitoring Event Subscribe is a Monitoring Request with monitoring type set to UE\_REACHABILITY, and either the Maximum Number of Reports greater than 1 or the Monitoring Duration IE are included. + +3. The 3GPP network processes the Monitoring Event Subscribe request as described in 3GPP TS 29.122 [9]. +4. If the Monitoring Event Subscribe Request is successfully processed, a response indicating the request was accepted is sent to the MSGin5G Server. + +#### 8.9.2.2.3 Notify + +Figure 8.9.2.2.3-1 shows the procedure which may be for updating MSGin5G reachability status. + +Pre-conditions: + +1. The MSGin5G Server has subscribed for reachability status monitoring for a UE or group of UEs. +2. The monitored UE(s) has transitioned to Connected Mode, Idle Mode or eDRX paging occasion and the 3GPP Network Entities has detected the change in UE reachability status. + +![Sequence diagram showing MSGin5G reachability status notify. The diagram shows two lifelines: 3GPP Network and MSGin5G Server. The sequence of messages is: 1. Monitoring Event Notification Report from 3GPP Network via SCEF/NEF; 2. Monitoring Event Notification Report acknowledgement to 3GPP Network via SCEF/NEF; 3. Update availability info, provide service.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +``` + +sequenceDiagram + participant 3GPP Network + participant MSGin5G Server + Note right of 3GPP Network: 1. Monitoring Event Notification Report +from 3GPP Network via SCEF/NEF + Note left of MSGin5G Server: 2. Monitoring Event Notification Report acknowledgement +to 3GPP Network via SCEF/NEF + Note right of MSGin5G Server: 3. Update availability info, +provide service + +``` + +Sequence diagram showing MSGin5G reachability status notify. The diagram shows two lifelines: 3GPP Network and MSGin5G Server. The sequence of messages is: 1. Monitoring Event Notification Report from 3GPP Network via SCEF/NEF; 2. Monitoring Event Notification Report acknowledgement to 3GPP Network via SCEF/NEF; 3. Update availability info, provide service. + +**Figure 8.9.2.2.3-1: MSGin5G reachability status notify.** + +1. Based on the reachability status change of a monitored UE(s), the 3GPP Network sends a Monitoring Notification message for UE reachability to the MSGin5G Server as specified in 3GPP TS 29.122 [9]. + +The notification may include idle mode information e.g., active time granted to the UE, eDRX cycle length, periodic RAU/TAU timer, depending on the subscription. + +2. After receiving a UE Reachability monitoring notification, the MSGin5G Server responds with an acknowledgement of the notification via SCEF/NEF. +3. The MSGin5G Server uses the information provided in the UE reachability monitoring event report to update its information on the UE's availability, e.g., MSGin5G Client Availability information. The MSGin5G Server may provide additional services based on reachability information, e.g., forward a stored message. + +#### 8.9.2.2.4 Unsubscribe + +Figure 8.9.2.2.4-1 shows the procedure which may be used by the MSGin5G Server to unsubscribe from monitoring of UE reachability. + +Pre-conditions: + +1. The MSGin5G Server has subscribed for reachability status monitoring for a UE or group of UEs. +2. Later, the MSGin5G Server unsubscribes for monitoring of UE reachability events in the Core Network, based on the information received from the Application Server or MSGin5G Client. + +NOTE 1: How the MSGin5G Server subscribes or unsubscribes for monitoring of UE reachability events in the Core Network is implementation dependent. + +NOTE 2: If the initial MSGin5G Server subscription for reachability status monitoring reaches the Maximum Number of Reports or Monitoring Duration indicated in the request, the 3GPP Network automatically deletes the subscription and an explicit MSGin5G reachability status unsubscribe is not necessary. + +![Sequence diagram showing MSGin5G reachability status unsubscribe. The diagram involves two main entities: 3GPP Network and MSGin5G Server. The sequence of messages is: 1. Monitoring Event unsubscribe via SCEF/NEF (dashed box), 2. Delete Monitoring Event Subscription (solid box), 3. Monitoring Event unsubscribe response via SCEF/NEF (dashed box).](2d548db0b26b7bf33244320322d5ee2c_img.jpg) + +``` + +sequenceDiagram + participant 3GPP Network + participant MSGin5G Server + Note right of MSGin5G Server: 1. Monitoring Event unsubscribe via SCEF/NEF + MSGin5G Server->>3GPP Network: + Note left of 3GPP Network: 2. Delete Monitoring Event Subscription + 3GPP Network->>MSGin5G Server: + Note right of MSGin5G Server: 3. Monitoring Event unsubscribe response via SCEF/NEF + +``` + +Sequence diagram showing MSGin5G reachability status unsubscribe. The diagram involves two main entities: 3GPP Network and MSGin5G Server. The sequence of messages is: 1. Monitoring Event unsubscribe via SCEF/NEF (dashed box), 2. Delete Monitoring Event Subscription (solid box), 3. Monitoring Event unsubscribe response via SCEF/NEF (dashed box). + +**Figure 8.9.2.2.4-1: MSGin5G reachability status unsubscribe.** + +1. The MSGin5G Server sends a Monitoring event unsubscribe request to the 3GPP Network using existing SCEF/NEF capabilities. +2. The 3GPP network processes the Monitoring event unsubscribe request and deletes the subscription, as described in 3GPP TS 29.122 [9]. +3. If the Monitoring event unsubscribe request is successfully processed, a response indicating the subscription was deleted is sent to the MSGin5G Server via SCEF/NEF. + +### 8.9.2.3 Flows + +The following information flows are specified for UE reachability status monitoring: + +- UE Reachability monitoring request and response; +- UE Reachability monitoring subscribe and unsubscribe +- UE Reachability monitoring notify + +All UE reachability monitoring interactions from MSGin5G Server (acting as SCS/AS) to SCEF/NEF occur over T8/N33 reference points capabilities detailed in 3GPP TS 23.502 [7] and TS 29.522[10]. As specified in TS 29.522[10] clause 4.4.2, all UE Reachability monitoring procedures use APIs specified in TS 23.682 [8] clause 5.6.1.4 and 3GPP TS 29.122 [9] clause 4.4.2.2. + +## 8.9.3 MSGin5G device triggering + +### 8.9.3.1 General + +MSGin5G device triggering is the means by which an MSGin5G Server leverages the 3GPP network device triggering capabilities, exposed via T8 /N33 reference point, while attempting to deliver an MSGin5G message. For example, when an Application Server initiates an MSGin5G message request, but the target MSGin5G UE is not reachable, the + +MSGin5G Server may use the 3GPP network device triggering mechanism to wake up the device and then deliver the payload to the destination. + +### 8.9.3.2 Procedure + +Figure 8.9.3.2-1 shows the MSGin5G device triggering procedure. + +Pre-conditions: + +1. The target UE is an MSGin5G UE. +2. The target MSGin5G Client is registered with the MSGin5G Server. +3. At a later time, after the registration is completed, the MSGin5G UE has become unreachable by the MSGin5G Server. + +![Sequence diagram of MSGin5G Triggering Procedure](bfc7918b689a38bc811276e0cc69477e_img.jpg) + +``` +sequenceDiagram + participant MSGin5G UE + subgraph MSGin5G UE + direction TB + AC[Application Client(s)] + MCC[MSGin5G Client] + end + participant SCEF/NEF + participant MSGin5G Server + + Note right of MSGin5G Server: 1. Request as specified in 8.3.2 + MSGin5G Server->>MSGin5G Server: 2. Determine if trigger is required + MSGin5G Server->>SCEF/NEF: 3. Request for device triggering + SCEF/NEF->>MSGin5G Server: 4. Response to device triggering + Note left of SCEF/NEF: 5. Device Trigger Delivery + MSGin5G Server->>SCEF/NEF: 6. Device triggering delivery report + SCEF/NEF->>MSGin5G Server: 7. Device triggering delivery report response +``` + +The diagram illustrates the MSGin5G Triggering Procedure. It features four main entities: MSGin5G UE (containing Application Client(s) and MSGin5G Client), SCEF/NEF, and MSGin5G Server. The sequence of interactions is as follows: 1. An external request arrives at the MSGin5G Server. 2. The server internally determines if a trigger is required. 3. The server sends a request for device triggering to the SCEF/NEF. 4. The SCEF/NEF responds to the server. 5. A 'Device Trigger Delivery' phase occurs, indicated by a box spanning the UE and SCEF/NEF lifelines. 6. The server sends a device triggering delivery report to the SCEF/NEF. 7. The SCEF/NEF sends a device triggering delivery report response back to the server. + +Sequence diagram of MSGin5G Triggering Procedure + +**Figure 8.9.3.2-1: MSGin5G Triggering Procedure** + +1. The MSGin5G Server receives a request for sending an MSGin5G message, the request includes the IEs as detailed in clause 9.1.2.1. +2. If the MSGin5G Server determines that the recipient MSGin5G Client is not reachable, it initiates a device trigger request via the SCEF/NEF. + +To determine the reachability of the target MSGin5G UE, the MSGin5G Server may use the UE reachability status monitoring procedure in clause 8.9.2. The MSGin5G Server may also use availability information provided by the MSGin5G Client at registration in the MSGin5G Client Communication Availability IE, as detailed in Table 8.2.1-1. + +NOTE 1: How the MSGin5G Server uses the MSGin5G Client Communication Availability IE, the UE reachability status monitoring procedure, or a combination thereof to make this determination is implementation specific. + +NOTE 2: If the recipient MSGin5G Client is reachable then the trigger request is not required, the MSGin5G Server sends the MSGin5G message as detailed in clause 8.3.3 and the rest of the steps in this procedure are skipped. + +3. The MSGin5G Server sends a request for Device Triggering via SCEF/NEF and determines the flow as detailed in clause 8.9.3.2. The Device Triggering request uses the UE Identifier, port number(s) and associated protocol information provided by the MSGin5G Client at registration in the MSGin5G Client Triggering Information IE. + +The MSGin5G Server may use MSGin5G Client Communication Availability and/or pre-configured information to determine the timing of the Device Triggering request, e.g. the trigger may be sent to ensure that the target UE is reachable prior to resuming MSGin5G communications. + +4. The MSGin5G Server receives a response from SCEF/NEF indicating the success or failure status of the request, as detailed in clause 8.9.3.3. +5. The device trigger is delivered to the target via SCEF/NEF and the Core Network. The targeted MSGin5G Client or Application Client receives the device trigger request. The targeted MSGin5G Client or Application Client parses the payload of the trigger request and determines the device trigger purpose. The target UE becomes reachable, and the MSGin5G Client or Application Client becomes available for further MSGin5G communications. +6. The MSGin5G Server receives a Device Triggering delivery status report from SCEF/NEF indicating the success of the delivery, as detailed in clause 8.9.3.3. +7. The MSGin5G Server send a Device Triggering delivery status report response to SCEF/NEF to acknowledge the delivery status report, as detailed in clause 8.9.3.3. + +Based on the trigger purpose derived from the payload, the targeted MSGin5G Client performs the corresponding actions (e.g. establish access network connectivity, contact the Application Server). + +### 8.9.3.3 Flows + +The following information flows are specified for MSGin5G triggering: + +1. request for device triggering; +2. response to device triggering; +3. device triggering delivery report; and +4. device triggering delivery report response. + +All device triggering interactions from MSGin5G Server (acting as SCS/AS) to SCEF/NEF occur over T8/N33 reference points, using capabilities detailed in 3GPP TS 23.502 [7] and TS 29.522[10]. As specified in TS 29.522[10] clause 4.4.3, all device triggering flows use APIs specified in TS 23.682 [8] clause 5.17.1 and 3GPP TS 29.122 [9] clause 4.4.6. + +## 8.10 Usage of SEAL + +### 8.10.1 General + +The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize the SEAL services. All SEAL services specified in 3GPP TS 23.434 [5] are available to MSGin5G Service. In this clause, only the details of the information flows, procedures and APIs whose utilization by MSGin5G Service are well-known are described. + +## 8.10.2 Configuration management service + +### 8.10.2.1 General + +The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize configuration management service procedures of SEAL to support MSGin5G Service. + +### 8.10.2.2 Information flows + +The following information flows of Configuration Management service are applicable for the MSGin5G Service: + +- Get VAL UE configuration request specified in subclause 11.3.2.1 of 3GPP TS 23.434 [5]; +- Besides the IEs specified in subclause 11.3.2.1 of 3GPP TS 23.434 [5], the information in table 8.10.2.2-1 is also included in the Get VAL UE configuration request. + +**Table 8.10.2.2-1: Additional information in the Get VAL UE configuration request** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------| +| MSGin5G UE information | O | Other information needed by the configuration procedure. (NOTE) | +| NOTE: The information can be the device type, device Vendor, etc. It is specified by application provider or MSGin5G Service provider and is out of scope of this document. The MSGin5G Service provider can configure the MSGin5G UE with different configuration data based on this IE. E.g. all sensors can be configured to a same MSGin5G Server. | | | + +- Get VAL UE configuration response specified in subclause 11.3.2.2 of 3GPP TS 23.434 [5]; +- Besides the IEs specified in subclause 11.3.2.2 of 3GPP TS 23.434 [5], the information in table 8.10.2.2-2 is also included in the Get VAL UE configuration response. + +**Table 8.10.2.2-2: Additional information in the Get VAL UE configuration response** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------| +| UE service ID | M | MSGin5G Service ID assigned to the requesting MSGin5G UE. | +| MSGin5G Server address | M | The MSGin5G Server which serves this MSGin5G UE. | +| MSGin5G Service specified information | O | The specific information of the MSGin5G Service specified by the MSGin5G Service provider. (NOTE) | +| NOTE: E.g. the segment size of MSGin5G message in this service provider, the detailed definition is out of scope of this document. | | | + +The usage of the above information flows is clarified as below: + +- The VAL UE ID is the MSGin5G UE ID; +- VAL service ID is the service identifier of the MSGin5G Service; and +- VAL UE configuration data is the MSGin5G UE configuration data. + +### 8.10.2.3 Procedures + +The following procedures of configuration management service are applicable for the MSGin5G Service: + +- VAL UE configuration data specified in subclause 11.3.3 of 3GPP TS 23.434 [5]. + +## 8.10.3 Group management service + +### 8.10.3.1 General + +The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize SEAL Client and SEAL Server for the group management service (e.g. creation, join, leave) on the group configuration information (e.g. group join policy, group leader) provided by the MSGin5G Server. The decisions and corresponding triggers (e.g. group creation, join, leave and deletion) for group management are responsibility of the application leveraging MSGin5G Service. The group management service of SEAL provides support for creating group for MSGin5G Service for applications leveraging MSGin5G Service. + +### 8.10.3.2 Information flows + +The information flows of group management procedures are specified in 3GPP TS 23.434 [5]. + +### 8.10.3.3 Procedures + +The following procedures of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the MSGin5G Service: + +- Group creation specified in clause 10.3.3; + - Subsequent to Step 3, when the identity list with the list of VAL user IDs or VAL UE IDs that are part of the created group contain the list of VAL user IDs or VAL UE IDs which does not have group management client (e.g. Legacy 3GPP UEs, Non-3GPP UEs or Application Server), it is responsibility of the VAL server (MSGin5G Server) to initiate the group creation notification towards those UEs. +- Group membership update specified in clause 10.3.5.2; +- Group configuration management specified in clause 10.3.6; +- Location-based group creation specified in clause 10.3.7; +- Group announcement and join specified in clause 10.3.8; +- Group member leave specified in clause 10.3.9; +- Temporary groups specified in clause 10.3.10; +- Group deletion specified in clause 10.3.13. + +NOTE: If the UE that is involved the Group management procedures does not have group management client (e.g. Legacy 3GPP UEs, Non-3GPP UEs or Application Server), it is responsibility of the VAL server (MSGin5G Server) to initiate the necessary group management request/response towards SEAL Group Management server on behalf of those UE. And if applicable, send and receive the necessary group management request/response to/from those UEs. + +### 8.10.3.4 APIs + +The following APIs of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the MSGin5G Service: + +- SS\_GroupManagement API specified in clause 10.4.2; +- SS\_Group\_Management\_Event API specified in clause 10.4.5. + +## 8.11 Application Client resides different UE in MSGin5G Service + +### 8.11.1 General + +This clause specifies the procedures for an Application Client residing on a different UE-2 than the UE with the MSGin5G Client (resides on MSGin5G UE-1) to perform Application Client registration, to send messages and receive messages using MSGin5G Client. The communication between Application Client and MSGin5G Client is over MSGin5G-5 reference point. + +NOTE: The procedure in this clause is also applicable to UE-2 that is out of network coverage. + +Editor's note: The API definition for the procedures defined in this clause is FFS. + +Editor's note: Whether the procedures in this clause are applicable to Application Client within MSGin5G UE-1 is FFS. + +### 8.11.2 Application Client registration using MSGin5G Client + +The signalling flow for registration of Application Client on the UE-2 with MSGin5G Client on MSGin5G UE-1 to use MSGin5G service is illustrated in figure 8.11.2-1. + +Pre-conditions: + +1. The MSGin5G UE-1 is configured with information to recognize and authorize UE-2. +2. The Application Client on UE-2 has discovered or is configured that the MSGin5G Client resides on MSGin5G UE-1 and can provide the MSGin5G service capability to it. +3. The UE-2 is using NR-PC5 to communicate with MSGin5G UE-1. + +![Sequence diagram showing the registration process. UE 2 (containing Application Client) sends a '1. Registration to gateway UE request' to MSGin5G UE 1 (containing MSGin5G Client 1). MSGin5G UE 1 then performs '2. Authorize the request' internally and sends back a '3. Registration to gateway UE response' to UE 2.](2eeee46b99394d7a37c46cd876e6cbc2_img.jpg) + +``` + +sequenceDiagram + participant UE2 as UE 2 + subgraph UE2 + AC[Application Client] + end + participant MSGin5GUE1 as MSGin5G UE 1 + subgraph MSGin5GUE1 + MSGin5GClient1[MSGin5G Client 1] + end + Note right of MSGin5GClient1: 2. Authorize the request + AC->>MSGin5GClient1: 1. Registration to gateway UE request + MSGin5GClient1-->>AC: 3. Registration to gateway UE response + +``` + +Sequence diagram showing the registration process. UE 2 (containing Application Client) sends a '1. Registration to gateway UE request' to MSGin5G UE 1 (containing MSGin5G Client 1). MSGin5G UE 1 then performs '2. Authorize the request' internally and sends back a '3. Registration to gateway UE response' to UE 2. + +Figure 8.11.2-1: Registration of Application Client on UE-2 with MSGin5G Client on MSGin5G UE-1 + +- 1) An Application Client on the UE-2 registers with MSGin5G Client-1 in MSGin5G UE-1 to use MSGin5G service. The request message includes information elements as specified in Table 8.11.2-1. + +Table 8.11.2-1: Information elements for Registration to gateway UE request + +| Information element | Status | Description | +|------------------------|--------|--------------------------------------------------| +| Layer-2 ID | M | Layer-2 identity of UE-2 | +| Application ID | M | Application ID of the application client on UE-2 | +| Credential information | M | UE-2 credential information | + +Editor's note 1: The security parameters to include in the message between UE-2 and MSGin5G UE-1 are FFS. + +Editor's note 2: The alignment between the request/response name in clause 8.11.2/8.11.3 and the updated architecture is FFS. + +- 2) Upon receiving the request from the Application Client, the MSGin5G Client authorizes the Application Client on UE-2 to it for MSGin5G service. The MSGin5G Client assigns a Registration ID and stores the mapping of the Registration ID, Application ID and Layer-2 ID of the UE-2. + +NOTE 1: The MSGin5G Client may reject the request for registration to use it for MSGin5G service based on local condition (like available power or connectivity to access network or any other reason outside the scope of 3GPP). + +- 3) The MSGin5G Client sends a response to the Application Client. The response message includes information elements as specified in Table 8.11.2-2. + +**Table 8.11.2-2: Information elements for Registration to gateway UE response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| Result | M | Indicates success or failure of the request | +| Registration ID | O | Identifies registration. This IE is included only if Result IE is set to success. | +| Failure reason | O | Indicates failure reason. This IE is included only if Result IE is set to failure. | + +NOTE 2: If the MSGin5G Client decided to reject the request for registration or if authorization fails in step 2, the MSGin5G Client sends a failure response to the Application Client. Otherwise, the MSGin5G Client sends a success response to the Application Client. + +NOTE 3: The MSGin5G Client may provide MSGin5G service capabilities for multiple Application Clients, at the same time. + +### 8.11.3 Application Client de-registration using MSGin5G Client + +The signalling flow for deregistration of Application Client on the UE-2 with MSGin5G Client-1 on MSGin5G UE-1 is illustrated in figure 8.11.3-1. + +Pre-conditions: + +- 1. The Application Client on UE-2 is successfully registered with MSGin5G Client on MSGin5G UE-1. + +![Sequence diagram showing the deregistration process. UE 2 (Application Client) sends a '1. de-registration to gateway UE request' to MSGin5G UE 1 (MSGin5G Client 1). MSGin5G Client 1 performs '2. Authorize the request' and then sends a '3. de-registration to gateway UE response' back to the Application Client.](5018822abcf9dc551579c7620b07701a_img.jpg) + +``` + +sequenceDiagram + participant UE2 as UE 2 +Application Client + participant MSGin5GUE1 as MSGin5G UE 1 +MSGin5G Client 1 + Note right of MSGin5GUE1: 2. Authorize the request + UE2->>MSGin5GUE1: 1. de-registration to gateway UE request + MSGin5GUE1-->>UE2: 3. de-registration to gateway UE response + +``` + +Sequence diagram showing the deregistration process. UE 2 (Application Client) sends a '1. de-registration to gateway UE request' to MSGin5G UE 1 (MSGin5G Client 1). MSGin5G Client 1 performs '2. Authorize the request' and then sends a '3. de-registration to gateway UE response' back to the Application Client. + +**Figure 8.11.3-1: Deregistration of Application Client on UE-2 with MSGin5G Client on MSGin5G UE-1** + +- 1) An Application Client on the UE-2 deregisters with MSGin5G Client in MSGin5G UE-1 to discontinue usage of the MSGin5G Service. The request message includes information elements as specified in Table 8.11.3-1. + +**Table 8.11.3-1: Information elements for Deregistration to gateway UE request** + +| Information element | Status | Description | +|------------------------|--------|-----------------------------| +| Registration ID | M | Identifies the registration | +| Credential information | M | UE-2 credential information | + +- Upon receiving the request from the Application Client, the MSGin5G Client removes the mapping of Registration ID, Application ID and Layer-2 ID of the UE-2. The MSGin5G Client sends a response to the Application Client on UE-2. The response message includes the information elements as specified in Table 8.11.3-2. + +**Table 8.11.3-2: Information elements for Deregistration to gateway UE response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------| +| Result | M | Indicates success or failure of the request | +| Failure reason | O | Indicates failure reason. This IE is included only if the Result IE is set to failure. | + +### 8.11.4 Application Client sending a message using MSGin5G Client on another UE + +The signalling flow for the Application Client on the UE-2 to send a message using the MSGin5G Client on MSGin5G UE-1 is illustrated in figure 8.11.4-1. + +Pre-conditions: + +- The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server. +- The Application Client on UE-2 is successfully registered with MSGin5G UE-1 to use MSGin5G service. + +![Sequence diagram showing the interaction between UE-2 (Application Client), MSGin5G UE-1 (MSGin5G Client), and MSGin5G Server. The steps are: 1. Request to send MSGin5G message from UE-2 to MSGin5G UE-1; 2. MSGin5G message as specified in clause 8.4, 8.5 or 8.7 from MSGin5G UE-1 to MSGin5G Server; 3. Response to send MSGin5G message from MSGin5G UE-1 to UE-2; 4. MSGin5G message delivery status report as specified in clause 8.3.5 from MSGin5G Server to MSGin5G UE-1 (dashed box); 5. message delivery status report from MSGin5G UE-1 to UE-2 (dashed line).](f8d508872d762c83336443cfd20c5412_img.jpg) + +``` + +sequenceDiagram + participant UE-2 + subgraph UE-2 [UE-2] + AC[Application Client] + end + subgraph MSGin5G_UE-1 [MSGin5G UE-1] + MC[MSGin5G Client] + end + participant MSGin5G_Server [MSGin5G Server] + + Note right of MSGin5G_Server: 4. MSGin5G message delivery status report as specified in clause 8.3.5 + + AC->>MC: 1. Request to send MSGin5G message + MC->>MSGin5G_Server: 2. MSGin5G message as specified in clause 8.4, 8.5 or 8.7 + MC-->>AC: 3. Response to send MSGin5G message + MSGin5G_Server-->>MC: 4. MSGin5G message delivery status report as specified in clause 8.3.5 + MC-->>AC: 5. message delivery status report + +``` + +Sequence diagram showing the interaction between UE-2 (Application Client), MSGin5G UE-1 (MSGin5G Client), and MSGin5G Server. The steps are: 1. Request to send MSGin5G message from UE-2 to MSGin5G UE-1; 2. MSGin5G message as specified in clause 8.4, 8.5 or 8.7 from MSGin5G UE-1 to MSGin5G Server; 3. Response to send MSGin5G message from MSGin5G UE-1 to UE-2; 4. MSGin5G message delivery status report as specified in clause 8.3.5 from MSGin5G Server to MSGin5G UE-1 (dashed box); 5. message delivery status report from MSGin5G UE-1 to UE-2 (dashed line). + +**Figure 8.11.4-1: Application Client on UE-2 sends message using MSGin5G Client on MSGin5G UE-1** + +- An Application Client on the UE-2 sends a request to send MSGin5G message to the MSGin5G Client. The information elements defined in Table 8.11.4-1 are included in the message. + +**Table 8.11.4-1: Information elements for Request to send MSGin5G message** + +| Information element | Status | Description | +|-----------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| Recipient UE Service ID or AS Service ID (see NOTE) | O | The service identity of the recipient. This IE is mandatory to initiate Point-to-Point messaging and Point-to-AS messaging. | +| Group Service ID (see NOTE) | O | The service identifier of the target MSGin5G Group.
This IE is mandatory to initiate Group messaging. | +| Broadcast Area ID (see NOTE) | O | The service identifier of the Broadcast Service Area where the message needs to be broadcast.
This IE is mandatory in the Broadcast Message. | +| Messaging Topic (see NOTE) | O | Indicates which Messaging Topic this message is related to.
This IE is mandatory for a message distribution based on topic. | +| Application ID | O | Identifies the application(s) for which the payload is intended. | +| Payload | M | Payload of the message.
MSGin5G Server/Client is unaware of the content. | +| Delivery status required | O | Indicates whether delivery status is required or not. | +| Priority type | O | Application priority level requested for this message as specified in Table 8.3.2-1. | +| NOTE: Only one occurrence shall be present of any of these IEs. | | | + +Editor's note: If table 8.11.4-1 should be moved to separate clause to be applicable for communication between any Application Client and any MSGin5G Client is FFS. + +- 2) Upon receiving the request from the Application Client in UE-2, the MSGin5G Client constructs an MSGin5G message with the related IEs specified in table 8.3.2-1 and sends the MSGin5G message. +- if the size of the received message exceeds the maximum allowed packet size, the MSGin5G Client sends the message as specified in clause 8.5; or + - If the size of the received message does not exceed the maximum allowed packet size, the MSGin5G Client sends the message as specified in clause 8.7; or + - If the size of the received message does not exceed the maximum allowed packet size, the MSGin5G Client may apply message aggregation as specified in clause 8.4 before sending the message as specified in clause 8.7. +- NOTE 1: The MSGin5G Client may also reject the request to send the MSGin5G message based on local condition (like available power or connectivity to access network or any other reason outside the scope of 3GPP). +- 3) The MSGin5G Client sends a response to Application Client on UE-2. The response message includes the information elements as specified in Table 8.11.4-2. + +**Table 8.11.4-2: Information elements for Response to send MSGin5G message** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| UE Service ID or AS Service ID or Group Service ID or Broadcast Area ID or Message Topic | M | The service identifier that the message is sent | +| Result | M | Indicates success or failure of the request | +| Failure reason | O | Indicates failure reason. This IE is included only if Result IE is set to failure. | + +NOTE 2: If the MSGin5G Client has decided to reject the request to send the message or the MSGin5G Client received a reject response from the MSGin5G Server in step 2, the MSGin5G Client sends a failure response to the Application Client and stops performing further steps. + +- 4) If delivery status is requested in the message in step 1, the MSGin5G Client may receive MSGin5G message delivery status report from the MSGin5G Server. + +- 5) Upon receiving the MSGin5G message delivery status report, the MSGin5G Client sends the message delivery status report to the Application Client on UE-2. The message delivery status report includes information elements as specified in Table 8.11.4-3. + +**Table 8.11.4-3: Information elements for MSGin5G message delivery status** + +| Information element | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------| +| UE Service ID or AS Service ID | M | The service identifier that sends the message delivery status | +| Delivery status | M | Indicates delivery status | + +## 8.11.5 Application Client receiving message via MSGin5G Client on another UE + +The signalling flow for an Application Client on the UE-2 to receive a message using the MSGin5G Client on MSGin5G UE-1 is illustrated in figure 8.11.5-1. + +Pre-conditions: + +1. The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server. +2. The Application Client on UE-2 is successfully registered with MSGin5G UE-1 to use MSGin5G service. + +![Sequence diagram showing the signalling flow for an Application Client on UE-2 to receive a message using the MSGin5G Client on MSGin5G UE-1. The diagram involves three main entities: UE-2 (containing an Application Client), MSGin5G UE-1 (containing an MSGin5G Client), and the MSGin5G Server. The sequence of messages is: 1. MSGin5G Server to MSGin5G UE-1: 'Receives a MSGin5G message as specified in clause 8.3.3'; 2. MSGin5G UE-1 to UE-2: 'Message received request'; 3. UE-2 to MSGin5G UE-1: 'Message received response'; 4. MSGin5G UE-1 to UE-2: 'Message delivery status report'; 5. MSGin5G UE-1 to MSGin5G Server: 'MSGin5G message delivery status report as specified in clause 8.3.4' (indicated by a dashed box).](db6f6e9f69edb58bff0b65268e020fd6_img.jpg) + +``` + +sequenceDiagram + participant UE2 as UE-2 +Application Client + participant MSGin5G_UE1 as MSGin5G UE-1 +MSGin5G Client + participant MSGin5G_Server as MSGin5G Server + + Note right of MSGin5G_Server: 1. Receives a MSGin5G message as specified in clause 8.3.3 + MSGin5G_UE1->>UE2: 2. Message received request + UE2->>MSGin5G_UE1: 3. Message received response + MSGin5G_UE1->>UE2: 4. Message delivery status report + Note right of MSGin5G_UE1: 5. MSGin5G message delivery status report as specified in clause 8.3.4 + MSGin5G_UE1-->>MSGin5G_Server: 5. MSGin5G message delivery status report as specified in clause 8.3.4 + +``` + +Sequence diagram showing the signalling flow for an Application Client on UE-2 to receive a message using the MSGin5G Client on MSGin5G UE-1. The diagram involves three main entities: UE-2 (containing an Application Client), MSGin5G UE-1 (containing an MSGin5G Client), and the MSGin5G Server. The sequence of messages is: 1. MSGin5G Server to MSGin5G UE-1: 'Receives a MSGin5G message as specified in clause 8.3.3'; 2. MSGin5G UE-1 to UE-2: 'Message received request'; 3. UE-2 to MSGin5G UE-1: 'Message received response'; 4. MSGin5G UE-1 to UE-2: 'Message delivery status report'; 5. MSGin5G UE-1 to MSGin5G Server: 'MSGin5G message delivery status report as specified in clause 8.3.4' (indicated by a dashed box). + +**Figure 8.11.5-1: Application Client on UE-2 receives message using MSGin5G Client on MSGin5G UE-1** + +- 1) The MSGin5G Client receives an MSGin5G message as specified in clause 8.3.3 for the Application Client on UE-2. The MSGin5G Client performs reassembly if the received message is part of a segmented message and waits till the whole message is received. The MSGin5G Client may also perform the segment recovery procedure as specified in clause 8.5.4 to recover missing segments. +- 2) Upon successfully receiving a message for the Application Client on UE-2, the MSGin5G Client sends a message received request to the Application Client based on the Application ID in the received message. The message includes information elements as specified in Table 8.11.5-1. + +**Table 8.11.5-1: Information elements for Message received request** + +| Information element | Status | Description | +|-----------------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------| +| Recipient UE Service ID/AS Service ID (see NOTE) | O | The service identifier of the originator. This IE is mandatory for Point-to-Point messaging and AS-to-Point messaging. | +| Group Service ID (see NOTE) | O | The service identifier of the MSGin5G Group. This IE is mandatory for Group Message. | +| Messaging Topic (see NOTE) | O | Indicates the Topic for which the message is received. This IE is mandatory for a Topic Message. | +| Payload | M | Payload of the message. MSGin5G Server/Client is unaware of the content. | +| Delivery status required | O | Indicates whether delivery status is required or not | +| Priority type | O | Application priority level requested for this message as specified in Table 8.3.2-1. | +| NOTE: Only one occurrence shall be present of any of these IEs. | | | + +- 3) Upon successfully receiving the message, the Application Client on UE-2 sends the message received response to the MSGin5G Client. +- 4) If delivery status is requested in the received message, the Application Client on UE-2 sends the message delivery status to the MSGin5G Client. +- 5) Upon receiving the delivery status, the MSGin5G Client constructs the MSGin5G message delivery status report as specified in table 8.3.4-1 and sends it to the MSGin5G Server. + +## 9 APIs and related information flows + +### 9.1 APIs provided by MSGin5G Server + +#### 9.1.1 Mm5s APIs + +##### 9.1.1.1 M5S\_AS\_Originating\_Message\_Delivery API + +###### 9.1.1.1.1 General + +**API description:** This API enables the Application Server to send MSGin5G message to the MSGin5G Server. + +###### 9.1.1.1.2 Send\_MSGin5G\_Message operation + +**API operation name:** Send\_MSGin5G\_Message + +**Description:** Send an MSGin5G message to MSGin5G Server. + +**Known Consumers:** Application Server + +**Inputs:** Refer subclause 9.1.2.1 + +**Outputs:** Refer subclause 8.3.2 + +See subclause 8.3.2 for the details of usage of this API operation. + +### 9.1.1.2 M5S\_UE\_Originating\_Message\_Delivery API + +#### 9.1.1.2.1 General + +**API description:** This API enables the Message Gateway or other 5GS Function to deliver MSGin5G message to the MSGin5G Server. + +#### 9.1.1.2.2 Send\_MSGin5G\_Message operation + +**API operation name:** Send\_MSGin5G\_Message + +**Description:** Send an MSGin5G message to MSGin5G Server. + +**Known Consumers:** L3G, N3G. + +**Inputs:** Refer subclause 8.3.2 + +**Outputs:** Refer subclause 8.3.2 + +See subclause 8.3.2 for the details of usage of this API operation. + +### 9.1.1.3 M5S\_AS\_Originating\_Delivery\_Status\_Report API + +#### 9.1.1.3.1 General + +**API description:** This API enables the Application Server to deliver MSGin5G message delivery status report to the MSGin5G Server. + +#### 9.1.1.3.2 Report\_Message\_Delivery\_Status operation + +**API operation name:** Report\_Message\_Delivery\_Status + +**Description:** Send an MSGin5G message delivery status report to MSGin5G Server. + +**Known Consumers:** Application Server + +**Inputs:** Refer subclause 9.1.2.2 + +**Outputs:** Refer subclause 8.3.4 + +See subclause 8.3.4 for the details of usage of this API operation. + +### 9.1.1.4 M5S\_Delivery\_Status\_Report API + +#### 9.1.1.4.1 General + +**API description:** This API enables the Message Gateway to deliver MSGin5G message delivery status reports to the MSGin5G Server. + +#### 9.1.1.4.2 Report\_Message\_Delivery\_Status operation + +**API operation name:** Report\_Message\_Delivery\_Status + +**Description:** Send an MSGin5G message delivery status report to MSGin5G Server. + +**Known Consumers:** L3G, N3G, BMG. + +**Inputs:** Refer subclause 8.3.4 + +**Outputs:** Refer subclause 8.3.4 + +See subclause 8.3.4 for the details of usage of this API operation. + +### 9.1.1.5 M5S\_AS\_Registration API + +#### 9.1.1.5.1 General + +**API description:** This API enables the Application Server to register to MSGin5G Server. + +#### 9.1.1.5.2 Registration operation + +**API operation name:** Registration + +**Description:** Do registration or update registration to an MSGin5G Server, by using this API, the Application Server provides/updates its information, including the URL used for the message delivery from MSGin5G Server to Application Server. + +**Known Consumers:** Application Server + +**Inputs:** Refer subclause 9.1.2.3 + +**Outputs:** Refer subclause 9.1.2.4 + +#### 9.1.1.5.3 Deregistration operation + +**API operation name:** Send\_MSGin5G\_Message + +**Description:** Do deregistration with an MSGin5G Server. + +**Known Consumers:** Application Server + +**Inputs:** Refer subclause 9.1.2.5 + +**Outputs:** Refer subclause 9.1.2.6 + +### 9.1.1.6 M5S\_Topiclist\_Event API + +#### 9.1.1.6.1 General + +**API description:** This API enables another MSGin5G Server to communicate with the MSGin5G Server to subscribe and receive subsequent notification events of the Messaging Topic list and information of specific message topics on the MSGin5G Server. + +#### 9.1.1.6.2 Subscribe Messaging Topiclist operation + +**API operation name:** Subscribe\_Messaging\_Topiclist + +**Description:** Subscribing to changes to Messaging Topic list on the MSGin5G Server. + +**Known Consumers:** MSGin5G Server + +**Inputs:** Refer subclause 8.8.4.2 + +**Outputs:** Refer subclause 8.8.4.2 + +See subclause 8.8.4.2 for the details of usage of this API operation + +#### 9.1.1.6.3 Notify Messaging Topiclist operation + +**API operation name:** Notify\_Messaging\_Topiclist + +**Description:** Notification for changes to Messaging Topic list on the MSGin5G Server. + +**Known Consumers:** MSGin5G Server + +**Inputs:** Refer subclause 8.8.4.2 + +**Outputs:** Refer subclause 8.8.4.2 + +See subclause 8.8.4.2 for the details of usage of this API operation + +#### 9.1.1.6.4            Subscribe Messaging Topic operation + +**API operation name:** Subscribe\_Messaging\_Topic + +**Description:** Subscribing to changes to one or more specific Messaging Topic(s) on the MSGin5G Server. + +**Known Consumers:** MSGin5G Server + +**Inputs:** Refer subclause 8.8.4.3 + +**Outputs:** Refer subclause 8.8.4.3 + +See subclause 8.8.4.3 for the details of usage of this API operation + +#### 9.1.1.6.5            Notify Messaging Topic operation + +**API operation name:** Notify\_Messaging\_Topic + +**Description:** Notification for changes to one or more specific Messaging Topic(s) on the MSGin5G Server. + +**Known Consumers:** MSGin5G Server + +**Inputs:** Refer subclause 8.8.4.3 + +**Outputs:** Refer subclause 8.8.4.3 + +See subclause 8.8.4.3 for the details of usage of this API operation + +#### 9.1.1.6.6            Unsubscribe Messaging Topiclist operation + +**API operation name:** Unsubscribe\_Messaging\_Topiclist + +**Description:** Unsubscribing to changes to Messaging Topic list on the MSGin5G Server. + +**Known Consumers:** MSGin5G Server + +**Inputs:** Refer subclause 8.8.4.2a + +**Outputs:** Refer subclause 8.8.4.2a + +See subclause 8.8.4.2 for the details of usage of this API operation + +#### 9.1.1.6.7            Unsubscribe Messaging Topic operation + +**API operation name:** Unsubscribe\_Messaging\_Topic + +**Description:** Unsubscribing to changes to one or more specific Messaging Topic(s) on the MSGin5G Server. + +**Known Consumers:** MSGin5G Server + +**Inputs:** Refer subclause 8.8.4.4 + +**Outputs:** Refer subclause 8.8.4.4 + +See subclause 8.8.4.4 for the details of usage of this API operation + +## 9.1.2 Mm5s Information flows + +### 9.1.2.1 M5S Application Server originating message send request + +The information flows from the Application Server to the MSGin5G Server for message delivery includes the IEs in table 8.3.2-1. Additionally, the following information in table 9.1.2.1-2 elements needs to be included: + +**Table 9.1.2.1-2: M5S Northbound Message Delivery Send request** + +| Information element | Status | Description | +|---------------------------|--------|---------------------------------------------------------------------------------------------------------------| +| Latency | O | The latency requirement for the message. | +| Authorization Information | O | The authorization information used to determine whether the Application Server is allowed to send the message | + +### 9.1.2.2 M5S Application Server originating message delivery status report request + +The information flows from the Application Server to the MSGin5G Server for message delivery status report includes the IE in table 8.3.4-1, and the following information in table 9.1.2.2-1 elements needs to be included: + +**Table 9.1.2.2-1: M5S Northbound Message Delivery Send request** + +| Information element | Status | Description | +|---------------------------|--------|---------------------------------------------------------------------------------------------------------------| +| Authorization Information | O | The authorization information used to determine whether the Application Server is allowed to send the message | + +### 9.1.2.3 M5S Application Server registration request + +The information flows from the Application Server to the MSGin5G Server for registration request includes the information elements in Table 9.1.2.3-1. + +**Table 9.1.2.3-1: Application Server Registration request** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| AS service ID | M | The MSGin5G identifier of the Application Server. This ID is configured before registration. | +| Application ID | O | The identifier of the application specified by the application provider. | +| Authorization Information | O | The authorization information used to determine whether the Application Server is allowed to send the message | +| Notification target URI | O | The URL for receiving message, message delivery status report. The MSGin5G Server uses this URL to interact to Application Server. | +| Application Profile (NOTE) | O | The elements in Application Profile include the information of the Application Server, e.g. application name, application provider, application scenario description, application category. This IE is used by MSGin5G Server to compare with application client information. | +| NOTE: The detailed definition of Application Profile is out of scope of this document. | | | + +### 9.1.2.4 M5S Application Server registration response + +The information flows from the MSGin5G Server to the Application Server for registration response includes the information elements in Table 9.1.2.4-1. + +**Table 9.1.2.4-1: Application Server registration response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------| +| AS service ID | M | The MSGin5G identifier of the Application Server. | +| Registration result | M | Indication if the registration is success or failure | + +Editor's note: Whether other information may be included in the Application Server registration response is FFS. + +### 9.1.2.5 M5S Application Server de-registration request + +The information flows from the Application Server to the MSGin5G Server for de-registration request includes the information elements in Table 9.1.2.5-1. + +**Table 9.1.2.5-1: Application Server de-registration request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| AS service ID | M | The MSGin5G identifier of the Application Server. | + +### 9.1.2.6 M5S Application Server de-registration response + +The information flows from the MSGin5G Server to the Application Server for de-registration response includes the information elements in Table 9.1.2.6-1. + +**Table 9.1.2.6-1: Application Server de-registration response** + +| Information element | Status | Description | +|------------------------|--------|---------------------------------------------------------| +| AS service ID | M | The MSGin5G identifier of the Application Server. | +| De-registration result | M | Indication if the de-registration is success or failure | + +## 9.2 APIs provided by Message Gateway + +### 9.2.1 MI3g APIs + +#### 9.2.1.1 L3G\_Message\_Delivery API + +##### 9.2.1.1.1 General + +**API description:** This API enables the MSGin5G Server to deliver MSGin5G message to the Legacy 3GPP Message Gateway. + +##### 9.2.1.1.2 Send\_Message operation + +**API operation name:** Send\_MSGin5G\_Message + +**Description:** Send an MSGin5G message to Legacy 3GPP Message Gateway. + +**Known Consumers:** M5S. + +**Inputs:** Refer subclause 8.3.3 + +**Outputs:** Refer subclause 8.3.3 + +See subclause 8.3.3 for the details of usage of this API operation. + +### 9.2.1.2 L3G\_Delivery\_Status\_Report API + +#### 9.2.1.2.1 General + +**API description:** This API enables the MSGin5G Server to deliver a Delivery Status Report to the Legacy 3GPP Message Gateway. + +#### 9.2.1.2.2 Report\_Message\_Delivery\_Status operation + +**API operation name:** Report\_Message\_Delivery\_Status + +**Description:** Send an MSGin5G message delivery status report to Legacy 3GPP Message Gateway. + +**Known Consumers:** M5S. + +**Inputs:** Refer subclause 8.3.5 + +**Outputs:** Refer subclause 8.3.5 + +See subclause 8.3.5 for the details of usage of this API operation. + +### 9.2.2 Mn3g APIs + +#### 9.2.2.1 N3G\_Message\_Delivery API + +##### 9.2.2.1.1 General + +**API description:** This API enables the MSGin5G Server to deliver MSGin5G message to the Non-3GPP Message Gateway. + +##### 9.2.2.1.2 Send\_Message operation + +**API operation name:** Create\_MSGin5G\_Message + +**Description:** Send an MSGin5G message to Non-3GPP Message Gateway. + +**Known Consumers:** M5S. + +**Inputs:** Refer subclause 8.3.3 + +**Outputs:** Refer subclause 8.3.3 + +See subclause 8.3.3 for the details of usage of this API operation. + +#### 9.2.2.2 N3G\_Delivery\_Status\_Report API + +##### 9.2.2.2.1 General + +**API description:** This API enables the MSGin5G Server to deliver a Delivery Status Report to the Non-3GPP Message Gateway. + +##### 9.2.2.2.2 Report\_Message\_Delivery\_Status operation + +**API operation name:** Report\_Message\_Delivery\_Status + +**Description:** Send an MSGin5G message delivery status report to Non-3GPP Message Gateway. + +**Known Consumers:** M5S. + +**Inputs:** Refer subclause 8.3.5 + +**Outputs:** Refer subclause 8.3.5 + +See subclause 8.3.5 for the details of usage of this API operation. + +## 9.2.3 Mbg APIs + +### 9.2.3.1 Nbg\_Message\_Delivery API + +#### 9.2.3.1.1 General + +**API description:** This API enables the MSGin5G Server to deliver MSGin5G messages to the Broadcast Message Gateway. + +#### 9.2.3.1.2 Send\_Message operation + +**API operation name:** Create\_MSGin5G\_Message + +**Description:** Send an MSGin5G message to Broadcast Message Gateway. + +**Known Consumers:** M5S. + +**Inputs:** Refer subclause 8.3.3 + +**Outputs:** Refer subclause 8.3.3 + +See subclause 8.3.3 for the details of usage of this API operation. + +--- + +## 10 Information Elements + +### 10.1 Payload + +The *Payload* Information Element carries the application payload that is transferred by the MSGin5G Service, of which the content is transparent to the MSGin5G Service. + +If the message originates from an MSGin5G UE, the *Payload* IE is a string of maximum length that can be transported without segmentation but not more than 2048 octets. + +### 10.2 Application ID + +The *Application ID* Information Element identifies the Application Client on the UE or in the Application Server. + +The *Application ID* is a string, which shall allow identifying 65535 different Application Clients. The *Application ID* is configured or provisioned in the Application Client or the Application Server. + +### 10.3 Messaging Topic + +The *Messaging Topic* Information Element indicates the topic of the message, which an interested UE or Application Server can subscribe to. + +The *Messaging Topic* IE is a string, which shall allow identifying 65535 different Messaging Topics. Allocating and populating the *Messaging Topic* IE is done by the Application Client or the Application Server. + +## 10.4 Broadcast Area ID + +The *Broadcast Area ID* Information Element identifies the service area where the Broadcast Message will be delivered. + +The *Broadcast Area ID* IE is a string, which shall allow identifying 65535 different Broadcast Areas. The *Broadcast Area ID* is provisioned on the Application Client or the Application Server and is mapped by the Broadcast Message Gateway onto the Broadcast Area as used by the broadcast service in the 5GC. + +## 10.5 Message ID + +The Message ID Information Element uniquely identifies a specific MSGin5G message in the MSGin5G Service. If message delivery status report is requested by an MSGin5G message, the Message ID IE in this MSGin5G message is used by the sender of the MSGin5G message to match the message delivery status report with the original MSGin5G message. It is also used by the MSGin5G Server in aggregating the message delivery status report message delivery status reports. + +The Message ID shall be unique within the MSGin5G Service and shall be generated by the sender of a new message. + +## 10.6 Failure Cause + +The Failure Cause Information Element indicates the the failure reason of an MSGin5G message, if this MSGin5G message can not be delivered successfully. + +The Failure Cause IE is a string, which shall allow identifying 65535 different failure reasons. + +--- + +# 11 Deployment models + +## 11.1 General + +This clause describes deployments of the functional model specified in clause 5. + +## 11.2 Deployment of MSGin5G server(s) + +The MSGin5G server(s) should be deployed in the PLMN operator domain. The VAL service using MSGin5G service for the message delivery acts as Application Server and interacts with MSGin5G Server via MSGin5G-3 reference point. The MSGin5G server(s) connects with the 3GPP network system in one or more PLMN operator domain. The MSGin5G server(s) may be supporting multiple Application Servers. + +Figure 11.2-1 illustrates the deployment of multiple MSGin5G Servers in a single PLMN operator domain. Each MSGin5G Server serves a part of MSGin5G service subscribers (including the subscriber using the MSGin5G UE or Non-MSGin5G UE) in this PLMN operator domain. In this deployment, the MSGin5G Servers shall be connected with each other to provide the MSGin5G service to all MSGin5G service subscribers in the PLMN operator domain. The MSGin5G Servers provide MSGin5G service to the Application Server(s) deployed in the VAL service provider domain. The Application Server may be connected and registered to one MSGin5G Server. + +![Figure 11.2-1: MSGin5G Server(s) deployed in a single PLMN operator domain with interconnection between MSGin5G Server(s).](3c0be9369e1f99f7f820fda3f9d676e6_img.jpg) + +This diagram illustrates the deployment of MSGin5G servers within a single PLMN operator domain. At the top, an 'Application Server(s)' block is connected via an 'MSGin5G-3' interface to the 'Application service provider domain'. Below this, a dashed line separates it from the 'PLMN operator domain'. In the PLMN operator domain, 'MSGin5G Server 1' and 'MSGin5G Server 2' are interconnected via an 'MSGin5G-8' interface. Each server is connected to a central '3GPP network system' block via an 'MSGin5G-1/2/4/7' interface. Finally, each 3GPP network system is connected to a 'MSGin5G/Non-MSGin5G UE(s)' block. + +Figure 11.2-1: MSGin5G Server(s) deployed in a single PLMN operator domain with interconnection between MSGin5G Server(s). + +**Figure 11.2-1: MSGin5G Server(s) deployed in a single PLMN operator domain with interconnection between MSGin5G Server(s)** + +Figure 11.2-2 illustrates the deployment of MSGin5G Servers in multiple PLMN operator domains. Each MSGin5G Server serves the MSGin5G service subscribers in this PLMN operator domain. In this deployment, the MSGin5G Servers deployed in PLMN operator domain 1 may be connected with the MSGin5G deployed in PLMN operator domain 2 to provide the MSGin5G service interconnection based on the business agreement between PLMN operator 1 and PLMN operator 2. + +![Figure 11.2-2: MSGin5G Server(s) deployed in multiple PLMN operator domain with interconnection between MSGin5G Server(s).](1b34b4b9929df6a81e43e106be67c533_img.jpg) + +This diagram shows the deployment across two PLMN operator domains. An 'Application Server(s)' block at the top connects via 'MSGin5G-3' to the 'Application service provider domain'. A vertical dashed line separates 'PLMN operator domain 1' and 'PLMN operator domain 2'. In domain 1, 'MSGin5G Server 1' connects to a '3GPP network system' via 'MSGin5G-1/2/4/7' and to 'MSGin5G/Non-MSGin5G UE(s)'. In domain 2, 'MSGin5G Server 2' does the same. Crucially, 'MSGin5G Server 1' and 'MSGin5G Server 2' are interconnected across the domain boundary via an 'MSGin5G-8' interface. + +Figure 11.2-2: MSGin5G Server(s) deployed in multiple PLMN operator domain with interconnection between MSGin5G Server(s). + +**Figure 11.2-2: MSGin5G Server(s) deployed in multiple PLMN operator domain with interconnection between MSGin5G Server(s)** + +Editor's note: Whether MSGin5G Server can be deployed in EDN to fulfill the delay requirement specified in [R-5.1.2-001] of 3GPP TS 22.262 [2] is FFS. + +## 11.3 Deployment of Message Gateway(s) + +Figure 11.3-1 illustrates the deployment of Message Gateway in a single PLMN operator domain. If only one Message Gateway, i.e. Message Gateway 1 in Figure 11.3-1, is deployed, all MSGin5G Servers in this PLMN domain may connect to a single Message Gateway to provide the MSGin5G service for the Non-MSGin5G UEs. Multiple Message Gateways may also be deployed in a single PLMN operator domain. In this deployment, i.e. Message Gateway 1 and Message Gateway 2 in Figure 11.3-1 are deployed, each Message Gateway is used to provide MSGin5G service for a part of MSGin5G service subscribers in this PLMN operator domain. + +NOTE: The relationship between MSGin5G service subscribers served by the MSGin5G Server and Message Gateway, e.g. whether all MSGin5G service subscribers served by MSGin5G Server 1 use Message Gateway 1 or some of them use Message Gateway 1 and some of them use Message Gateway 2, is implementation specific. + +![Diagram illustrating the deployment of Message Gateways in a single PLMN operator domain. The diagram shows an Application Server(s) connected to MSGin5G Server 1 and MSGin5G Server 2 via MSGin5G-3. MSGin5G Server 1 and MSGin5G Server 2 are connected via MSGin5G-8. Both servers connect to a 3GPP network system via MSGin5G-2/4. The 3GPP network system connects to Message Gateway 1 and Message Gateway 2 via MSGin5G-2/4. The diagram is divided into an Application service provider domain and a PLMN operator domain by a dashed line.](6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg) + +``` + +graph TD + subgraph Application_service_provider_domain [Application service provider domain] + AS[Application Server(s)] + end + subgraph PLMN_operator_domain [PLMN operator domain] + MS1[MSGin5G Server 1] + MS2[MSGin5G Server 2] + NS[3GPP network system] + MG1[Message Gateway 1] + MG2[Message Gateway 2] + end + AS -- MSGin5G-3 --> MS1 + AS -- MSGin5G-3 --> MS2 + MS1 -- MSGin5G-8 --> MS2 + MS1 -- MSGin5G-2/4 --> NS + MS2 -- MSGin5G-2/4 --> NS + NS -- MSGin5G-2/4 --> MG1 + NS -- MSGin5G-2/4 --> MG2 + +``` + +Diagram illustrating the deployment of Message Gateways in a single PLMN operator domain. The diagram shows an Application Server(s) connected to MSGin5G Server 1 and MSGin5G Server 2 via MSGin5G-3. MSGin5G Server 1 and MSGin5G Server 2 are connected via MSGin5G-8. Both servers connect to a 3GPP network system via MSGin5G-2/4. The 3GPP network system connects to Message Gateway 1 and Message Gateway 2 via MSGin5G-2/4. The diagram is divided into an Application service provider domain and a PLMN operator domain by a dashed line. + +**Figure 11.3-1: deployment of Message Gateway in a single PLMN operator domain** + +Figure 11.3-2 illustrates the deployment of Message Gateway in multiple PLMN operator domains. The MSGin5G Server(s) in one PLMN domain are only connected to the Message Gateway(s) in the same PLMN operator domain to provide the MSGin5G service for the Non-MSGin5G UEs served by this PLMN operator. + +![Diagram showing the deployment of Message Gateways in multiple PLMN operator domains. The diagram is divided into three horizontal sections: Application service provider domain (top), PLMN operator domain 1 (left), and PLMN operator domain 2 (right). In the Application service provider domain, there is an 'Application Server(s)' block. A solid line labeled 'MSGin5G-3' connects it to 'MSGin5G Server 1' in PLMN operator domain 1. A dashed line labeled 'MSGin5G-8' connects 'MSGin5G Server 1' to 'MSGin5G Server 2' in PLMN operator domain 2. Below each MSGin5G server is a '3GPP network system' block, connected by a solid line labeled 'MSGin5G-2/4'. Below each 3GPP network system is a 'Message Gateway' block (labeled 'Message Gateway 1' and 'Message Gateway 2'), also connected by a solid line labeled 'MSGin5G-2/4'. A vertical dashed line separates the two PLMN operator domains.](426a0ab9454f31706038a0ac0bc37b9c_img.jpg) + +``` +graph TD; subgraph ASPD [Application service provider domain]; AS[Application Server(s)]; end; subgraph POD1 [PLMN operator domain 1]; MS1[MSGin5G Server 1]; NS1[3GPP network system]; MG1[Message Gateway 1]; end; subgraph POD2 [PLMN operator domain 2]; MS2[MSGin5G Server 2]; NS2[3GPP network system]; MG2[Message Gateway 2]; end; AS -- MSGin5G-3 --> MS1; MS1 -- MSGin5G-8 --> MS2; MS1 -- MSGin5G-2/4 --> NS1; NS1 -- MSGin5G-2/4 --> MG1; MS2 -- MSGin5G-2/4 --> NS2; NS2 -- MSGin5G-2/4 --> MG2; +``` + +Diagram showing the deployment of Message Gateways in multiple PLMN operator domains. The diagram is divided into three horizontal sections: Application service provider domain (top), PLMN operator domain 1 (left), and PLMN operator domain 2 (right). In the Application service provider domain, there is an 'Application Server(s)' block. A solid line labeled 'MSGin5G-3' connects it to 'MSGin5G Server 1' in PLMN operator domain 1. A dashed line labeled 'MSGin5G-8' connects 'MSGin5G Server 1' to 'MSGin5G Server 2' in PLMN operator domain 2. Below each MSGin5G server is a '3GPP network system' block, connected by a solid line labeled 'MSGin5G-2/4'. Below each 3GPP network system is a 'Message Gateway' block (labeled 'Message Gateway 1' and 'Message Gateway 2'), also connected by a solid line labeled 'MSGin5G-2/4'. A vertical dashed line separates the two PLMN operator domains. + +**Figure 11.3-2: deployment of Message Gateway in multipl PLMN operator domains** + +## 11.4 Deployment of MSGin5G Server(s) and SEAL server(s) + +If an MSGin5G Server interacts with SEAL Servers over the SEAL-S reference point specified for each SEAL service, i.e. the SEAL Server are not collocated in the MSGin5G Server, the application of functional model to deployments of SEAL servers specified in 3GPP TS 23.434 [5] applied. In the deployment, MSGin5G acts as the VAL servers specified in 3GPP TS 23.434 [5], but may be deployed in the PLMN operator domain. + +## Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2020-11 | SA6#40-e | | | | | TR skeleton agreed in SA6#40: S6-202295 | | 0.0.0 | +| 2021-01 | SA6#41-e | | | | | Implemented pCRs approved in SA6#41-e: S6-210363
Editorial changes by the rapporteur | | 0.1.0 | +| 2021-03 | SA6#42-e | | | | | Implemented pCRs approved in SA6#42-e: S6-210615, S6-210588, S6-210597, S6-210720
Editorial changes by the rapporteur | | 0.2.0 | +| 2021-04 | SA6#42 BIS-e | | | | | Implemented pCRs approved in SA6#42 BIS-e: S6-210827, S6-211087, S6-211088, S6-210989, S6-211089, S6-211090, S6-211091, S6-211092, S6-211093, S6-211094, S6-211095, S6-210988, S6-210969, S6-211071, S6-211096, S6-210822, S6-211042, S6-211043, S6-211097, S6-211098
Editorial changes by the rapporteur | | 0.3.0 | +| 2021-06 | SA6#43 -e | | | | | Implemented pCRs approved in SA6#43-e: S6-211135, S6-211136, S6-211367, S6-211337, S6-211232, S6-211338, S6-211230, S6-211342, S6-211339, S6-211340, S6-211341, S6-211399, S6-211400, S6-211349, S6-211490, S6-211169, S6-211343, S6-211344, S6-211430, S6-211355
Editorial changes by the rapporteur | | 0.4.0 | +| 2021-06 | SA#92 -e | SP-210474 | | | | Presentation for information at SA#92-e | | 1.0.0 | +| 2021-07 | SA6#44-e | | | | | Implemented pCRs approved in SA6#44-e: S6-211527, S6-211722, S6-211723, S6-211726, S6-211727, S6-211724, S6-211841, S6-211774, S6-211775, S6-211776, S6-211777, S6-211780, S6-211779, S6-211781, S6-211592, S6-211842, S6-211628, S6-211629, S6-211843, S6-211844, S6-211713
Editorial changes by the rapporteur | | 1.1.0 | +| 2021-09 | SA6#45-e | | | | | Implemented pCRs approved in SA6#45-e: S6-212164, S6-212153, S6-212084, S6-212089, S6-211944, S6-212154, S6-212105, S6-211954, S6-211955, S6-212155, S6-211957, S6-211959, S6-212156, S6-212177
Editorial changes by the rapporteur | | 1.2.0 | +| 2021-09 | SA#93-e | SP-210947 | | | | Presentation for approval at SA#93-e | | 2.0.0 | +| 2021-09 | SA#93-e | SP-210947 | | | | MCC Editorial update for publication after TSG SA approval (SA#93) | | 17.0.0 | +| 2021-09 | | | | | | Editorial corrections as agreed by SA6 | | 17.0.1 | +| 2021-12 | SA#94-e | SP-211521 | 0001 | 1 | F | Remove ENs with no actions in clause 5 | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0002 | 1 | F | Corrections in clause 7 | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0004 | 2 | F | Add definition of MSGin5G Server address | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0005 | 1 | F | Correction on clause 5.3.2.2 target resolution | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0006 | 1 | F | Correction on message delivery procedure to Message Gateway | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0007 | 1 | D | Editorial of MSGin5G | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0008 | 1 | F | Remove API Related EN and modify Figure 8.3.5-2 | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0010 | 1 | F | Correction on clause 8.3.3 | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0011 | 1 | F | Correction on clause 8.7.5 | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0012 | 2 | F | 5GMARCH store and forward | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0014 | 1 | B | Message topic unsubscription | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0015 | 1 | F | Editorial correction | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0016 | | F | Corrections on broadcast | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0017 | | F | Alignment on Message Gateway IE name | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0018 | 1 | F | Remove one IE from AS originating message send request | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0019 | 1 | F | Correction on Message Aggregation | | 17.1.0 | +| 2021-12 | SA#94-e | SP-211521 | 0020 | 1 | F | Security aspect of MSGin5G align with SA3 | | 17.1.0 | +| 2022-03 | SA#95-e | SP-220105 | 0021 | 2 | F | Correction on Message Segment Recovery | | 17.2.0 | +| 2022-03 | SA#95-e | SP-220105 | 0022 | 2 | F | Correction on Point-to-Point Message Segmentation and Reassembly | | 17.2.0 | +| 2022-03 | SA#95-e | SP-220105 | 0023 | 1 | F | Correction on Usage of Network Capabilities | | 17.2.0 | +| 2022-03 | SA#95-e | SP-220105 | 0024 | 1 | F | Editorial corrections | | 17.2.0 | +| 2022-03 | SA#95-e | SP-220105 | 0026 | 2 | F | Clarification on clause 5.3.3 functional entity of MSGin5G Client | | 17.2.0 | +| 2022-03 | SA#95-e | SP-220105 | 0027 | 2 | F | Clarification and correction on clause 8.8 Other MSGin5G messaging related procedures | | 17.2.0 | +| 2022-03 | SA#95-e | SP-220105 | 0028 | 2 | F | Clarification and correction on clause 8.11 Constrained devices | | 17.2.0 | +| 2022-03 | SA#95-e | SP-220105 | 0029 | 1 | F | Definitions of Gateway UE and Relay UE | | 17.2.0 | +| 2022-06 | SA#96 | SP-220481 | 0030 | 1 | B | Application architecture enhancement of broadcast aspect | | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0031 | 1 | B | Broadcast Message delivery procedure | | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0032 | 1 | B | Charging architectural requirements | | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0033 | 1 | F | Delete the example of the originator address in Table 8.11.5-1 | | 18.0.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-------------------------------------------------------------------------------------------|--------| +| 2022-06 | SA#96 | SP-220481 | 0034 | 1 | D | Editorial corrections | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0035 | 2 | B | Bulk registration for constrained device over MSGin5G-6 reference point | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0036 | 1 | C | Values and usage of Priority type | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0037 | 1 | C | MSGin5G message aggregation and segment | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0038 | 1 | B | Update of MSGin5G group management | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0039 | 1 | D | Update of abbreviations | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0040 | 1 | F | Clarify relationship between store forward and device triggering | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0041 | 1 | F | Remove the EN of broadcast in clause 10.4 | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0042 | | D | Removal of ENs with no action | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0043 | 1 | B | Messaging Topic handling between different MSGin5G Servers | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0044 | 1 | B | Message delivery based on Messaging Topic for different PLMNs | 18.0.0 | +| 2022-06 | SA#96 | SP-220481 | 0045 | 1 | D | Update of MSGin5G UE registration | 18.0.0 | +| 2022-09 | SA#97 | SP-220921 | 0046 | 4 | F | Update of Non-MSGin5G UE registration | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0047 | 2 | B | Relay selection procedure over MSGin5G-6 interface | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0048 | 2 | F | Correction on clause 8.1.3 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0049 | | F | Removal of EN in clause 10 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0050 | | F | Removal of EN in clause 5.3.2.1 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0051 | 1 | F | Aggregated message handling at the MSGin5G Server | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0052 | 1 | F | Typos, readability, and abbreviations | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0053 | 1 | C | Broadcast Message Gateway additions | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0054 | | C | Handling of Priority Type IE | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0055 | 1 | F | Corrections to clauses 4-6 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0056 | 3 | F | Correction to clause 8.1.3 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0057 | 3 | F | Correction to clause 8.2.1 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0058 | 1 | F | Corrections to clauses 8.2.7- 8.7.3.3 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0059 | 1 | F | Corrections to clauses 8.7.4.2 - 8.7.5.3 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0060 | 1 | F | Corrections for handling topic subscriptions between servers | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0061 | 1 | F | Corrections for constrained devices using gateway UE | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0062 | 1 | F | Corrected figure in chapter 8.7.1.5 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0063 | 1 | F | Security credentials IE in MSGin5G UE registration aligned with 33501 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0064 | 1 | F | Security credentials IE in Message Gateway registration aligned with 33501 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0065 | 1 | F | Security credentials IE in Application Server Registration aligned with 33501 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0066 | | F | Security credentials IE in messaging procedures aligned with 33501 | 18.1.0 | +| 2022-09 | SA#97 | SP-220921 | 0067 | | F | Security credentials IE in APIs provided by MSGin5G Server aligned with 33501 | 18.1.0 | +| 2022-12 | SA#98 | SP-221240 | 0068 | | F | Remove the EN about Application ID in clause 8.4.2 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0070 | 1 | B | Bulk registration of Non-MSGin5G UEs | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0071 | 1 | B | Bulk de-registration of Non-MSGin5G UEs | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0072 | 1 | B | MSGin5G UE bulk de-registration over MSGin5G-6 reference point | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0073 | 1 | F | Message Aggregation used in Group messaging and Message delivery based on Messaging Topic | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0075 | | F | Remove EN in clause 8.3.1 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0076 | | D | Terms alignment | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0078 | | F | Correction to clause 5.1 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0079 | 1 | F | Correction to clause 6.1.4 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0081 | 2 | F | Corrections to clause 9.1.1.4 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0082 | 1 | F | Corrections to clause 10 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0083 | 1 | F | Note on status reporting of broadcast message | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0086 | 3 | F | Resolution on EN about UE type | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0087 | | F | Resolution on Editor's Note on Priority IE for constrained devices | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0088 | 1 | F | Correction to clause 8.4.2 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0090 | | F | Rewording some steps in clause 8.4.2 | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0092 | 2 | B | MSGin5G UE bulk configuration over MSGin5G-6 reference point | 18.2.0 | +| 2022-12 | SA#98 | SP-221240 | 0094 | | F | Remove EN in clause 8.9.2 | 18.2.0 | +| 2023-03 | SA#99 | SP-230285 | 0095 | 2 | D | Corrections for clause 4.3.2 | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0096 | 2 | D | Editorial type corrections for clause 5.2 | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0097 | 1 | C | Add the element of Registration expiration time | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0098 | 1 | F | Update the scope | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0100 | 1 | F | The MSGin5G Client Profile handling on MSGin5G Server | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0101 | 1 | B | Adds new group management capabilities to MSGin5G service | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0102 | 1 | C | Separation of Availability and Reachability concepts | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0104 | 1 | F | AS registration is optional | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0105 | 2 | F | Various corrections on Topic handling | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0106 | 1 | C | Device Triggering should not be restricted to the AS | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0107 | 1 | F | Clarification when Store and forward applies | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0108 | 1 | D | Missing abbreviation | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0109 | 1 | F | Correction to UE-1 in Application Architecture | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0110 | 1 | F | Corrections on clause 8.11 | 18.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2023-03 | SA#99 | SP-230285 | 0114 | 1 | F | Architecture and reference point between MSGin5G Servers | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0115 | 1 | F | Deployment models | 18.3.0 | +| 2023-03 | SA#99 | SP-230285 | 0117 | 1 | B | Messaging Topic Event API | 18.3.0 | +| 2023-04 | | | | | | Editorial corrections; corrupt style of Figure 5.2-2 title and replacing in the requirement [AR-4.1.2-e] description "Including" with "including" | 18.3.1 | +| 2023-06 | SA#100 | SP-230697 | 0119 | 1 | F | MSGin5G-8 naming issue | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0121 | 1 | F | Modification of security credentials IE | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0123 | 3 | F | Update the architecture for constrained device | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0124 | 2 | F | Update the constrained device related definitions | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0125 | 1 | F | Update the Messaging Topic handling between different MSGin5G Servers | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0126 | | F | Resolution of EN in 8.4.2 | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0127 | 2 | C | Resolution of ENs in 8.5.x | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0128 | 1 | C | Some correction on identities | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0129 | | F | Update of 8.2.7 MSGin5G UE bulk registration based on constrained UE related architecture | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0130 | 2 | F | Update of clause 8.2.8 | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0131 | 1 | F | Update of clause 8.2.9 and 8.2.10 for Non-MSGin5G UE bulk (de)registration | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0132 | 1 | F | Update of clause 8.2.11 MSGin5G UE bulk de-registration | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0133 | 1 | F | Update of clause 8.11.1 | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0134 | 2 | F | Update of Application Client (de-)registration using MSGin5G Client | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0135 | 1 | F | Update of Application Client sending and receiving message using MSGin5G Client | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0136 | 1 | F | Clarify procedures in clause 8.3 with corrections | 18.4.0 | +| 2023-06 | SA#100 | SP-230697 | 0138 | 1 | F | New Message Delivery Flow | 18.4.0 | +| 2023-07 | SA#100 | | | | | Editorial corrections to the CR implementations like e.g. correcting the incorrect red text in the bullet in clause 5.3.3.2 | 18.4.1 | +| 2023-09 | SA#101 | SP-230995 | 0139 | 1 | F | Correction of grammatical errors | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0140 | 1 | F | Correction on NOTE 8 in clause 5.2 | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0141 | 1 | F | Message delivery flow | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0143 | 4 | F | Corrections to clause 8.1.4 | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0144 | 2 | F | Corrections to MSGin5G Registration | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0145 | 1 | F | Correction to MSGin5G UE De-registration | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0146 | 1 | F | Corrections to Non-MSGin5G UE Registration | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0147 | 2 | F | Corrections to AS (de-)registration | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0148 | 3 | F | Corrections to MSGin5G UE bulk (de-)registration | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0149 | 2 | F | Corrections to Constrained UE registration procedure | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0150 | 1 | F | Correction of profile storing | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0151 | 1 | F | No response message if message is discarded | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0153 | 1 | F | Corrections on message segmentation | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0155 | 1 | F | Corrections to Topic Unsubscription | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0156 | 2 | F | Correction for subscription management between 2 servers | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0157 | | F | Corrections in pre-conditions | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0159 | 1 | F | Correction to procedure for inter-PLMN message exchange | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0160 | 3 | F | Correction of reference | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0161 | 1 | F | Correction to empty clause 8.10.3.2 | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0162 | 1 | F | Legacy and non 3GPP Message Gateway interactions with SEAL services | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0163 | | F | Correction to clause 4.2.2 | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0167 | 1 | F | Correction on Message Aggregation at MSGin5G Client | 18.5.0 | +| 2023-09 | SA#101 | SP-230995 | 0168 | 3 | F | Update of the Message Aggregation at MSGin5G Server | 18.5.0 | +| 2023-12 | SA#102 | SP-231542 | 0170 | | F | Messaging Topic list unsubscription | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0171 | | F | Messaging Topic related unsubscription APIs | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0173 | 2 | F | UE reachability status monitoring is decided by application layer | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0176 | 1 | F | Resolution of EN | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0177 | 1 | F | Resolution of EN | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0178 | | F | Resolution of EN | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0179 | | F | Resolution of EN | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0182 | | F | Resolution of EN | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0183 | | F | Resolution of EN | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0186 | 1 | F | Removal of Topic | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0187 | 1 | F | Response message for segmented message is wrong | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0189 | 1 | F | Add general description in clause 8.2 | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0190 | 2 | F | Add general description in clause 8.8 | 18.6.0 | +| 2023-12 | SA#102 | SP-231542 | 0191 | 1 | F | Pre-conditions in clause 8.2.8 | 18.6.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23682/0931f3e098bd4539041de11c50cec2d2_img.jpg b/raw/rel-18/23_series/23682/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0c99473f08ed15ee1b8384b3f3d3948b1655686 --- /dev/null +++ b/raw/rel-18/23_series/23682/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5252bbffaeceff108e57f2ffe2c2b05fb4b3a9c7aae555004e5b02e4f2f7744b +size 38642 diff --git a/raw/rel-18/23_series/23682/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/raw/rel-18/23_series/23682/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1169bb7e0d72d060b2c6f7bb2cda6045a3fbace4 --- /dev/null +++ b/raw/rel-18/23_series/23682/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66c46c5ab63614e21fcc9dc50b6c8020386d844f01bf2a87c62cebf6aa35a2cf +size 80531 diff --git a/raw/rel-18/23_series/23682/142c0ec898fdb4803450dd39592136c5_img.jpg b/raw/rel-18/23_series/23682/142c0ec898fdb4803450dd39592136c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..267d95776f2f560f1883d0f4dc41ebc26174d6b5 --- /dev/null +++ b/raw/rel-18/23_series/23682/142c0ec898fdb4803450dd39592136c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4af0a7c111f3f3462e828264a0f6f41732ea99a09c112a7a591850b57667a98a +size 63585 diff --git a/raw/rel-18/23_series/23682/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/raw/rel-18/23_series/23682/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e51e33484e0aec373d856f5a30ea99faae1b3d5 --- /dev/null +++ b/raw/rel-18/23_series/23682/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20f29da59ed9f2b761646eca4159f5e992a5ee0df8bfa92a3a4c402ea2158f32 +size 67079 diff --git a/raw/rel-18/23_series/23682/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/raw/rel-18/23_series/23682/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0ded47e4ce17f41ecfe112a427e9a16ff78bb11 --- /dev/null +++ b/raw/rel-18/23_series/23682/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5ebd3e5091ad50261586b93b89631c63a5233d6dd890437b2ef13bf29ec09b6 +size 30417 diff --git a/raw/rel-18/23_series/23682/1ce027dfd26183da52137cf990213724_img.jpg b/raw/rel-18/23_series/23682/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fb16a713a4b1f055fa45c2b697954636e2d86a7 --- /dev/null +++ b/raw/rel-18/23_series/23682/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4c4a9e13285ce1c2c7861929d7a94db9b247aaf239d161f36a6dbb7c37c2d0e +size 108342 diff --git a/raw/rel-18/23_series/23682/23aceb0e7d3c1a644294899d9047df05_img.jpg b/raw/rel-18/23_series/23682/23aceb0e7d3c1a644294899d9047df05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e3f8c1bb9c59036cb5c55a920c074f2cdd5c13c --- /dev/null +++ b/raw/rel-18/23_series/23682/23aceb0e7d3c1a644294899d9047df05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ae9f0e8d6b47b61732b195d6b5de6afc2690eac9e5f6d6dfa8a6f4d1305d13e +size 99163 diff --git a/raw/rel-18/23_series/23682/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/23_series/23682/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9f76ea8832ea66677b869b0232dbffa72439fd9 --- /dev/null +++ b/raw/rel-18/23_series/23682/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b93c09e85a822d9e766b7d5e7b8f6eab86079383b7d9846646472773a977d93 +size 115247 diff --git a/raw/rel-18/23_series/23682/29997432244f81212ee1e6c94f308f1b_img.jpg b/raw/rel-18/23_series/23682/29997432244f81212ee1e6c94f308f1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e2da590628cef43fba26bec841e1674ef3b2837 --- /dev/null +++ b/raw/rel-18/23_series/23682/29997432244f81212ee1e6c94f308f1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:607e799df975f949014d4f06ab6db6f00c65bbc8589fbfe6de0e0c02353a2e9a +size 50739 diff --git a/raw/rel-18/23_series/23682/2f587210e4f97c32758c5972e2e83d20_img.jpg b/raw/rel-18/23_series/23682/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2247e009bf815279d75191cb6ca42ec7cd6200e4 --- /dev/null +++ b/raw/rel-18/23_series/23682/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc03c42a4b7ab331c4ca344731b85e526da6fa9b0452f956456d6ab5607893ec +size 61266 diff --git a/raw/rel-18/23_series/23682/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/raw/rel-18/23_series/23682/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce5a1a81abbc4677b6e2f946d16dfb963eee0336 --- /dev/null +++ b/raw/rel-18/23_series/23682/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dc65cd56e94815b0eecfe276e2f44bd58061049c2716bff3d5f0b61e77938a0 +size 72239 diff --git a/raw/rel-18/23_series/23682/38257e5215ad672f308f5235780034a2_img.jpg b/raw/rel-18/23_series/23682/38257e5215ad672f308f5235780034a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a260ac8bd33db5195f0c80acec10fe87b9458583 --- /dev/null +++ b/raw/rel-18/23_series/23682/38257e5215ad672f308f5235780034a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37cc44ca8dfe91877f4794ad6cbe696196b84fbc49eedb55668b063ecbd9ac35 +size 52535 diff --git a/raw/rel-18/23_series/23682/408c4798ea60469e0728a7cbbd598668_img.jpg b/raw/rel-18/23_series/23682/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93047eaea0d059a6e825586ec9169f9466badc29 --- /dev/null +++ b/raw/rel-18/23_series/23682/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0778afab929c0519f78b52f1a7087ac3aee1497f55a37a52ca1b4ee63029b740 +size 46409 diff --git a/raw/rel-18/23_series/23682/40b80ef077f6151a9fbb593b8ad4864d_img.jpg b/raw/rel-18/23_series/23682/40b80ef077f6151a9fbb593b8ad4864d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a45d452c21de9860bf850d1fe5da3fddc1f89b6b --- /dev/null +++ b/raw/rel-18/23_series/23682/40b80ef077f6151a9fbb593b8ad4864d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6d8701e98af3c1aa0f904906b85b815393f93646675eaa6e032851c7fb983cb +size 64459 diff --git a/raw/rel-18/23_series/23682/41af98c5f15e6022f8ddde55567cf56e_img.jpg b/raw/rel-18/23_series/23682/41af98c5f15e6022f8ddde55567cf56e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85b7748e0f8fa53c7aadd4f8338f1837b029afc4 --- /dev/null +++ b/raw/rel-18/23_series/23682/41af98c5f15e6022f8ddde55567cf56e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd9a6c1d59079c65f2f88a0ada8c16be7978fdf2f0dbe214a6b331901b516f3f +size 43348 diff --git a/raw/rel-18/23_series/23682/41fa90d03d7195caa162c74d289817a4_img.jpg b/raw/rel-18/23_series/23682/41fa90d03d7195caa162c74d289817a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a2f1b8b2ce3c5eceedfb97f46e8d7a4696fcf1a --- /dev/null +++ b/raw/rel-18/23_series/23682/41fa90d03d7195caa162c74d289817a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d598f8da1a67f68914032515d3705805d8f2b9b617361d2cc140c67b0ad924ad +size 34091 diff --git a/raw/rel-18/23_series/23682/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/raw/rel-18/23_series/23682/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a2b2a27ce29a5edf1cc3f2a9b0b49bf55d8df1e --- /dev/null +++ b/raw/rel-18/23_series/23682/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba6240cddc827f719445b2d8b375cb63984b7dd3e00630d2769a18360fea5c79 +size 37173 diff --git a/raw/rel-18/23_series/23682/550eaffa2d1e03391ac33ccb5ad16cd3_img.jpg b/raw/rel-18/23_series/23682/550eaffa2d1e03391ac33ccb5ad16cd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2787b4cdc9485ab8dc38d3483a919249a5474306 --- /dev/null +++ b/raw/rel-18/23_series/23682/550eaffa2d1e03391ac33ccb5ad16cd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47d213a1c95cb9670757f495002ea4180a55952d9861527e5ddd8c495ae0fcbb +size 77492 diff --git a/raw/rel-18/23_series/23682/5c834b7b0f3ad30428fe3d02926b225b_img.jpg b/raw/rel-18/23_series/23682/5c834b7b0f3ad30428fe3d02926b225b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..669a0c4b031d775f3f8dbebfaa4a8e3f0d83fee8 --- /dev/null +++ b/raw/rel-18/23_series/23682/5c834b7b0f3ad30428fe3d02926b225b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:853b377582d3b24c17f7233b543adce942da79143c91384c1a8a52e31679e67e +size 38266 diff --git a/raw/rel-18/23_series/23682/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23682/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74b784cd7199c6600864c12b55ca6bbcca8d3a9f --- /dev/null +++ b/raw/rel-18/23_series/23682/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca29cce50d223e96d3ff5ce0d3699780e1675bd9b671efa0390885efebb73e55 +size 9369 diff --git a/raw/rel-18/23_series/23682/6116b1a533010c170fc526ec513ba0b8_img.jpg b/raw/rel-18/23_series/23682/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..262f15959476da1bf15579849228add0c3b328ca --- /dev/null +++ b/raw/rel-18/23_series/23682/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ff796550bef4fbbfd80d9cb06bac0b8c53bf1f1d311d657bdb5835855adcd8d +size 54841 diff --git a/raw/rel-18/23_series/23682/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23682/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b6165ac0d998b28483936508d41bb3f1579c08d --- /dev/null +++ b/raw/rel-18/23_series/23682/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5c8ec852ae091fa94709d294a23706ac7d6526d73de17c9c7314f98e20bc2e2 +size 5686 diff --git a/raw/rel-18/23_series/23682/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/raw/rel-18/23_series/23682/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7153a7eaa415457cf2b4c11182c4ba1c85f6c8d5 --- /dev/null +++ b/raw/rel-18/23_series/23682/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c3489c5077f7a999baab38c69d03872ac51ac1f01112e4917ffe4980d1878a5 +size 40199 diff --git a/raw/rel-18/23_series/23682/691626a7032a642bb74793336c37e274_img.jpg b/raw/rel-18/23_series/23682/691626a7032a642bb74793336c37e274_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40cea39f57304ff654cc84960c989d91dc83a1d0 --- /dev/null +++ b/raw/rel-18/23_series/23682/691626a7032a642bb74793336c37e274_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f472597eb00ef281b9c9613968cc911578807537307170eef2b631c1f7f81d40 +size 38121 diff --git a/raw/rel-18/23_series/23682/6e9d059430baba0c363e33749f68b107_img.jpg b/raw/rel-18/23_series/23682/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58c433aad0f23e6035ac173d99b62ae00a19e345 --- /dev/null +++ b/raw/rel-18/23_series/23682/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04271c93beb3a1685732f8da4fa6f191a5d45b75e903b27653b5cc70320dfdd1 +size 29973 diff --git a/raw/rel-18/23_series/23682/6ee202d340236de98def8045f273fa38_img.jpg b/raw/rel-18/23_series/23682/6ee202d340236de98def8045f273fa38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0fd6a5c04f6f0b9c2f7b78282b91b9ddb070c69 --- /dev/null +++ b/raw/rel-18/23_series/23682/6ee202d340236de98def8045f273fa38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8acdc71b67badfd3968bfe0276eafc24afb1af7770a80f46af53298b758b8c9f +size 80003 diff --git a/raw/rel-18/23_series/23682/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg b/raw/rel-18/23_series/23682/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1f75cceeabae53b9d83aa4c818b5ed5fb3386b9 --- /dev/null +++ b/raw/rel-18/23_series/23682/7472c67897a35ed6b67fcb47ea4c6b6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d277357663adaf9d663eae748a450026734da5703880e376c9c346d11e8b77d +size 38473 diff --git a/raw/rel-18/23_series/23682/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/raw/rel-18/23_series/23682/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae5ab08784c5a3bde507cfac31c1bc46641ef07e --- /dev/null +++ b/raw/rel-18/23_series/23682/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:893b85728962497729173e86e5b1e265ea5992a4369c1c7811ca55635bfd5c04 +size 59535 diff --git a/raw/rel-18/23_series/23682/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/23_series/23682/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a71042c9c52912eb88314bd2e6b2f8986ac71750 --- /dev/null +++ b/raw/rel-18/23_series/23682/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e45a4fffe8f6feab4a0f484d654d86f4e15acbb50ed5a15a26522a63c4e50757 +size 54959 diff --git a/raw/rel-18/23_series/23682/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/raw/rel-18/23_series/23682/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5eeff0e646eb51ac7f3eee819b5cb690ca0c4487 --- /dev/null +++ b/raw/rel-18/23_series/23682/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab645a589825e1ed240b80fed9145970be7f520d63dd488879a4064adc7ae1a6 +size 109642 diff --git a/raw/rel-18/23_series/23682/8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg b/raw/rel-18/23_series/23682/8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dec00432284cb742243e703546c8243fc8552e34 --- /dev/null +++ b/raw/rel-18/23_series/23682/8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8a1b792d666f3ffe428341a1bda555ad6f3b83d1f57407d6a57a59f8443b33f +size 33238 diff --git a/raw/rel-18/23_series/23682/868ee7df1ec851f132ccf8c390de76a8_img.jpg b/raw/rel-18/23_series/23682/868ee7df1ec851f132ccf8c390de76a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c9c54699aaa67bd8947ddc3ee3a20b4bc0b84ed --- /dev/null +++ b/raw/rel-18/23_series/23682/868ee7df1ec851f132ccf8c390de76a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebb9a993aa88a3b7c4ecb0f561d0a2e3f6f6f6baf1b088e681ebafd7fdcaa394 +size 23454 diff --git a/raw/rel-18/23_series/23682/86e1f8551d4922ea8fa197f96fe4098b_img.jpg b/raw/rel-18/23_series/23682/86e1f8551d4922ea8fa197f96fe4098b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd2ac12bf0d90ecb85a242025eb769c9e4ff63e9 --- /dev/null +++ b/raw/rel-18/23_series/23682/86e1f8551d4922ea8fa197f96fe4098b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3871ba677d9289c2f8bb983b8ab673c73146c699b8e6d953017e6e0fd2c62ea5 +size 43762 diff --git a/raw/rel-18/23_series/23682/886af5e2ffd5d8f11079c547675cf882_img.jpg b/raw/rel-18/23_series/23682/886af5e2ffd5d8f11079c547675cf882_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e1791bae59b01832ec72699c4642b6627404930 --- /dev/null +++ b/raw/rel-18/23_series/23682/886af5e2ffd5d8f11079c547675cf882_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29c0180d937ed04d831715ac95c44c566e8a1be5615b4e152f88ce5e4fc1f2ea +size 67982 diff --git a/raw/rel-18/23_series/23682/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/raw/rel-18/23_series/23682/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fdbe9fb351e3b93273d0e37be84b244c174b7fe3 --- /dev/null +++ b/raw/rel-18/23_series/23682/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5962def697800b0cc59e24630920ae762c2f2b3b52751b0861a0497801d4628 +size 36292 diff --git a/raw/rel-18/23_series/23682/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/raw/rel-18/23_series/23682/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36dbfafe417bd6f31ba176d504f7ce20a0bd13f0 --- /dev/null +++ b/raw/rel-18/23_series/23682/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d21dab200fd695cee9940bf9d80781cbce4873b532b7f1f338c5654e6162986e +size 59580 diff --git a/raw/rel-18/23_series/23682/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/raw/rel-18/23_series/23682/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ade1983691ccca75c4748a7e95e0531249462d2d --- /dev/null +++ b/raw/rel-18/23_series/23682/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:459d03f5206e60e350495c23bf4db70e68a9208b9ac0cd17588d3c0c7fbbd921 +size 34464 diff --git a/raw/rel-18/23_series/23682/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/raw/rel-18/23_series/23682/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d82406cc2d3274ce648f4493725fce916ebef0 --- /dev/null +++ b/raw/rel-18/23_series/23682/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50a73e73c5dbdb63fff7a3be72117d38f539a3754abc01eebe51003a825be96f +size 53329 diff --git a/raw/rel-18/23_series/23682/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg b/raw/rel-18/23_series/23682/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eadb8684caace71aba4089da13d57e147d2ae158 --- /dev/null +++ b/raw/rel-18/23_series/23682/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fd7a9f1ca4c8e68987d9a84b14a7fcf318eec06dd5598260218c8d4ffbfc109 +size 23669 diff --git a/raw/rel-18/23_series/23682/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/23_series/23682/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88527de4549a6a888f1f36200bf60a540aa92890 --- /dev/null +++ b/raw/rel-18/23_series/23682/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:791fd922deb8f15ce85484c9bcb80092cba3242284ef1da44f68824b4022ccaf +size 89145 diff --git a/raw/rel-18/23_series/23682/a4b963a07cc368283154762c4b156fe7_img.jpg b/raw/rel-18/23_series/23682/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebe96764ae9315c5a02003f606aa72e181e0c3f3 --- /dev/null +++ b/raw/rel-18/23_series/23682/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f87562b2c47bfe52ac369782277a0ae8ff826324acd31f80882fe22d1687c335 +size 31492 diff --git a/raw/rel-18/23_series/23682/a66383962afcd0f0458f0d45c101fabf_img.jpg b/raw/rel-18/23_series/23682/a66383962afcd0f0458f0d45c101fabf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39651a88b3af58f52efab64e907a082d1c2861f5 --- /dev/null +++ b/raw/rel-18/23_series/23682/a66383962afcd0f0458f0d45c101fabf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f60f6ef7bb86888c7881caa2fcd15eed11c63e7844ac71a1b90574c89297a1c5 +size 47407 diff --git a/raw/rel-18/23_series/23682/aeb2a26a07219661191294dba528067a_img.jpg b/raw/rel-18/23_series/23682/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61ecd177f39b25f2b3f7fcb74a642041ead8b78f --- /dev/null +++ b/raw/rel-18/23_series/23682/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1be740d579147c68265abc51ad7df518434666b89eadd45daa653bbc4011d878 +size 142343 diff --git a/raw/rel-18/23_series/23682/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/raw/rel-18/23_series/23682/b06a4c871dfd0ce034cf801519d0039a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f418ac6e6e6afff729b7e2e3c811751a508e7526 --- /dev/null +++ b/raw/rel-18/23_series/23682/b06a4c871dfd0ce034cf801519d0039a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca0e53b9e429e19c24d5814c0baae2ae5057c2273c247298bcfd7ece7f51117b +size 69190 diff --git a/raw/rel-18/23_series/23682/c07e21a8d65991db04263322f859c94f_img.jpg b/raw/rel-18/23_series/23682/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5526c9246b5e6482d806133d12307fbe3015da6b --- /dev/null +++ b/raw/rel-18/23_series/23682/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:656bdae40598d323bd59e5125091adb14ed41279427b2c163ba78dcb34cc7975 +size 47578 diff --git a/raw/rel-18/23_series/23682/c14d36776b70c47a6bad152b3a8a5ec6_img.jpg b/raw/rel-18/23_series/23682/c14d36776b70c47a6bad152b3a8a5ec6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9110c520cfed93fc9840e74130a565a89c13b3cf --- /dev/null +++ b/raw/rel-18/23_series/23682/c14d36776b70c47a6bad152b3a8a5ec6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:baf7dd6e9065b3dfec81da4955cde30581f23c15e93d2ea73cd45cae57847818 +size 40381 diff --git a/raw/rel-18/23_series/23682/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg b/raw/rel-18/23_series/23682/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df553c8a76f264694ee5ae7183d8ec5ce6e4206a --- /dev/null +++ b/raw/rel-18/23_series/23682/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d026b8757447253dc3cd556ac2be3261a541398da9019a123a41b3f4dac30f7 +size 87330 diff --git a/raw/rel-18/23_series/23682/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/raw/rel-18/23_series/23682/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b913d2c48bd8e1474aaccfdd611c0a5a299e34b --- /dev/null +++ b/raw/rel-18/23_series/23682/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38ef48217601b6e6cf4ae3ad14dcc8d89e44402d1caeff956628541db1f9519b +size 52993 diff --git a/raw/rel-18/23_series/23682/dd8c4eb490876d1c18169c84d877ef32_img.jpg b/raw/rel-18/23_series/23682/dd8c4eb490876d1c18169c84d877ef32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c55122aec6a2b5d15e7f541c2c75cdd5516e839e --- /dev/null +++ b/raw/rel-18/23_series/23682/dd8c4eb490876d1c18169c84d877ef32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd5b9820f1bc38e1c2c207f11c83e494f606a67870da4849519c7001c90d9a48 +size 91949 diff --git a/raw/rel-18/23_series/23682/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/raw/rel-18/23_series/23682/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..057c78a6dc879c8348dedf1886d2cc122cd07964 --- /dev/null +++ b/raw/rel-18/23_series/23682/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0951523314edacf3d2597f90afce9dd8285c8a5fbb59f7efd39f1a188b0c25f9 +size 59825 diff --git a/raw/rel-18/23_series/23682/f2486d5031b55e42b300903a716b0a00_img.jpg b/raw/rel-18/23_series/23682/f2486d5031b55e42b300903a716b0a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f744b01654011a1d9721624f64a70ad194f2025a --- /dev/null +++ b/raw/rel-18/23_series/23682/f2486d5031b55e42b300903a716b0a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf6af6e66880e9dc6565432de55ee7ca49ddb08948275aa9fb369514548c0457 +size 35128 diff --git a/raw/rel-18/23_series/23682/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/raw/rel-18/23_series/23682/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70d35d82b49ce8f4fbcb1cb48e4f88e2805245a4 --- /dev/null +++ b/raw/rel-18/23_series/23682/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a715d9705656afac4b8b2f9ae5597a1347ea160de0816ada0e8bd3e58271f730 +size 108809 diff --git a/raw/rel-18/23_series/23682/f92e919c70b7adda2d0e778889f44fae_img.jpg b/raw/rel-18/23_series/23682/f92e919c70b7adda2d0e778889f44fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d96cda58036d22fa0cf3b5a642761f0b8b02be0 --- /dev/null +++ b/raw/rel-18/23_series/23682/f92e919c70b7adda2d0e778889f44fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6abf7bf737a14bbace8639e5d63958d9782e5a3a49b0c41f5dec4aa65b87c4cb +size 42786 diff --git a/raw/rel-18/23_series/23682/fae02fa1dac97fc5f19a7b85d20df290_img.jpg b/raw/rel-18/23_series/23682/fae02fa1dac97fc5f19a7b85d20df290_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30fe3688e0e86005824c4874b3f50ec0d3fbefc2 --- /dev/null +++ b/raw/rel-18/23_series/23682/fae02fa1dac97fc5f19a7b85d20df290_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1a6be4cd1dbe87d2197939cdaae4c68ffd95970f5b11bd495405538bff2e201 +size 51409 diff --git a/raw/rel-18/23_series/23682/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/23_series/23682/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7024a7d83272adb5dbe714fd286373f8c57ee96 --- /dev/null +++ b/raw/rel-18/23_series/23682/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02658468e6af605a4d3927c104ba42fd6d742f7f8c5b467d5d97b137f5b46439 +size 118626 diff --git a/raw/rel-18/23_series/23682/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/raw/rel-18/23_series/23682/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9b12ce0a6e3b148bac374132c55a368ac979b73 --- /dev/null +++ b/raw/rel-18/23_series/23682/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:835d51d73e969f2eabf8cce57c69800b36653e76793a87b09905c50e1143ca1c +size 69009 diff --git a/raw/rel-18/23_series/23682/ffb6acd27b8e3a54392840948a75869f_img.jpg b/raw/rel-18/23_series/23682/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92d8934fe7326ca0caf8650a03a5dfe1d03c5fcf --- /dev/null +++ b/raw/rel-18/23_series/23682/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4e89ca042d997b185a2f3215e64207137e92c77f0ee952ce05d974356e41742 +size 52326 diff --git a/raw/rel-18/23_series/23700-08/raw.md b/raw/rel-18/23_series/23700-08/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..b62a74457d1d5a138f652b559144c9b26d681226 --- /dev/null +++ b/raw/rel-18/23_series/23700-08/raw.md @@ -0,0 +1,6064 @@ + + +# 3GPP TR 23.700-08 V18.0.0 (2023-03) + +*Technical Report* + +**3rd Generation Partnership Project; +Technical Specification Group Services and System Aspects; +Study on enhanced support of Non-Public Networks; +Phase 2 +(Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. The 'G' has a red signal wave icon below it. + +3GPP logo + +A GLOBAL INITIATIVE + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 10 | +| 1 Scope..... | 12 | +| 2 References..... | 12 | +| 3 Definitions of terms, symbols and abbreviations..... | 13 | +| 3.1 Terms..... | 13 | +| 3.2 Void..... | 13 | +| 3.3 Abbreviations ..... | 13 | +| 4 Architectural Assumptions and Requirements..... | 14 | +| 5 Key Issues ..... | 14 | +| 5.1 Key Issue #1: Enabling support for idle and connected mode mobility between SNPNs without new network selection..... | 14 | +| 5.1.1 Description ..... | 14 | +| 5.2 Key Issue #2: Support of Non-3GPP access for SNPN ..... | 14 | +| 5.2.1 Description ..... | 14 | +| 5.3 Key Issue #3: Enabling NPN as hosting network for providing access to localized services ..... | 15 | +| 5.3.1 Description ..... | 15 | +| 5.4 Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services..... | 16 | +| 5.4.1 Description ..... | 16 | +| 5.5 Key Issue #5: Enabling access to localized services via a specific hosting network..... | 17 | +| 5.5.1 Description ..... | 17 | +| 5.6 Key Issue #6: Support for returning to home network..... | 18 | +| 5.6.1 Description ..... | 18 | +| 6 Solutions..... | 18 | +| 6.0 Mapping Solutions to Key Issues..... | 19 | +| 6.1 Solution #1: Enable efficient mobility via equivalent SNPNs..... | 19 | +| 6.1.1 Introduction ..... | 19 | +| 6.1.2 Functional Description ..... | 20 | +| 6.1.3 Procedures ..... | 20 | +| 6.1.4 Impacts on services, entities, and interfaces..... | 22 | +| 6.2 Solution #2: Access to SNPN services via Untrusted non-3GPP access network..... | 23 | +| 6.2.1 Introduction ..... | 23 | +| 6.2.2 Functional Description ..... | 23 | +| 6.2.3 Procedures ..... | 23 | +| 6.2.4 Impacts on services, entities, and interfaces..... | 24 | +| 6.3 Solution #3: Access to SNPN services via Trusted non-3GPP access network..... | 24 | +| 6.3.1 Introduction ..... | 24 | +| 6.3.2 Functional Description ..... | 24 | +| 6.3.3 Procedures ..... | 25 | +| 6.3.3.1 Access Network Selection procedure ..... | 25 | +| 6.3.3.2 Registration procedure ..... | 26 | +| 6.3.4 Impacts on services, entities, and interfaces..... | 26 | +| 6.4 Solution #4: Support of onboarding over untrusted non-3GPP access in SNPN..... | 26 | +| 6.4.1 Introduction ..... | 26 | +| 6.4.2 Functional Description ..... | 27 | +| 6.4.3 Procedures ..... | 27 | +| 6.4.4 Impacts on services, entities, and interfaces..... | 27 | +| 6.5 Solution #5: Support of Credentials Holder scenarios over untrusted non-3GPP access in SNPN..... | 28 | +| 6.5.1 Introduction ..... | 28 | +| 6.5.2 Functional Description ..... | 28 | +| 6.5.3 Procedures ..... | 28 | +| 6.5.4 Impacts on services, entities, and interfaces..... | 28 | +| 6.6 Solution #6: Access to SNPN services via wireline access network ..... | 29 | + +| | | | +|----------|----------------------------------------------------------------------------------------------------------------------------------|----| +| 6.6.1 | Introduction ..... | 29 | +| 6.6.2 | Functional Description ..... | 29 | +| 6.6.3 | Impacts on services, entities, and interfaces..... | 29 | +| 6.7 | Solution #7: High level flow for localized service support..... | 29 | +| 6.7.1 | Introduction ..... | 29 | +| 6.7.2 | Functional Description ..... | 30 | +| 6.7.3 | Procedures ..... | 30 | +| 6.7.4 | Impacts on services, entities, and interfaces..... | 32 | +| 6.8 | Solution #8: Reuse existing mechanisms for Control Plane Load Control, Congestion and Overload Control..... | 32 | +| 6.8.1 | Introduction ..... | 32 | +| 6.8.2 | Functional Description ..... | 32 | +| 6.8.3 | Procedures ..... | 32 | +| 6.8.4 | Impacts on services, entities, and interfaces..... | 32 | +| 6.9 | Solution #9: Prevention of overload build up at home network using AMF based congestion control when local service is over ..... | 33 | +| 6.9.1 | Introduction ..... | 33 | +| 6.9.2 | High-level Description ..... | 33 | +| 6.9.3 | Procedures ..... | 35 | +| 6.9.3.1 | UE in CM Idle-State and AMF configured to send "Network/service availability timer" ..... | 35 | +| 6.9.3.2 | UE in CM-Idle State and AMF not configured to send Network/service availability timer ..... | 37 | +| 6.9.3.2 | UE in CM-Connected State and AMF not configured to send Network/service availability timer ..... | 39 | +| 6.9.4 | Impacts on existing services and interfaces..... | 40 | +| 6.10 | Solution #10: Solution for discovery and selection of NPN hosting network and localized services ..... | 40 | +| 6.10.1 | Introduction ..... | 40 | +| 6.10.2 | Functional Description ..... | 41 | +| 6.10.2.1 | UE selection of SNPN hosting network for localized services ..... | 41 | +| 6.10.2.2 | UE selection of PNI-NPN hosting network for localized services ..... | 42 | +| 6.10.2.3 | Enabling access to SNPN Hosting Network for a localized service..... | 42 | +| 6.10.3 | Procedures ..... | 43 | +| 6.10.3.1 | Automatic discovery and selection of SNPNs for access to localized services..... | 43 | +| 6.10.3.2 | Leaving SNPN Localized services mode..... | 43 | +| 6.10.3.3 | Discovery and selection of PNI-NPNs with CAG for access to localized services ..... | 43 | +| 6.10.3.4 | Leaving the PNI-NPNs with CAG for access to localized services ..... | 44 | +| 6.10.3.5 | Manual discovery and selection of SNPNs for access to localized services ..... | 44 | +| 6.10.3.6 | Enabling access to localized services: Registration procedure..... | 44 | +| 6.10.4 | Impacts on services, entities, and interfaces..... | 45 | +| 6.11 | Solution #11: Access to localized service by using LADN and roaming architecture ..... | 45 | +| 6.11.1 | Introduction ..... | 45 | +| 6.11.2 | Functional Description ..... | 45 | +| 6.11.2.1 | Architecture ..... | 45 | +| 6.11.2.2 | Hosting network discovery and selection ..... | 46 | +| 6.11.2.3 | Registration to hosting network and access to Localized services ..... | 47 | +| 6.11.3 | Procedures ..... | 47 | +| 6.11.3.1 | Requesting Localized service information ..... | 47 | +| 6.11.3.2 | Connection to hosting network and access to Localized services ..... | 48 | +| 6.11.4 | Impacts on services, entities, and interfaces..... | 48 | +| 6.12 | Solution #12: Discovering services offered by SNPN/PNI-NPN while camping in a serving network..... | 49 | +| 6.12.1 | Introduction ..... | 49 | +| 6.12.2 | Functional Description ..... | 49 | +| 6.12.2.1 | PNI-NPN as hosting network ..... | 49 | +| 6.12.2.2 | SNPN as hosting network ..... | 49 | +| 6.12.3 | Procedures ..... | 52 | +| 6.12.3.1 | UE discovery, selection and access for hosting network using Registration procedure..... | 52 | +| 6.12.3.2 | UE discovery, selection and access for hosting network using UE Configuration Update procedure ..... | 53 | +| 6.12.3.3 | UE discovery, selection and access for hosting network using Steering of Roaming procedure ..... | 54 | +| 6.12.4 | Impacts on services, entities and interfaces..... | 54 | +| 6.13 | Solution #13: Exposure enhancements to support providing access to localized services ..... | 55 | +| 6.13.1 | Introduction ..... | 55 | +| 6.13.2 | Functional Description ..... | 56 | +| 6.13.3 | Procedures ..... | 60 | + +| | | | +|----------|---------------------------------------------------------------------------------------------------------------------------|----| +| 6.13.3.1 | Procedure for enabling hosting network to provide access to localized services ..... | 60 | +| 6.13.3.2 | Procedure for home network to update UE with the network selection information for the
subscribed Hosting Network..... | 62 | +| 6.13.3.3 | Procedure for hosting network to instruct the UE to return to the home network..... | 63 | +| 6.13.4 | Impacts on services, entities, and interfaces..... | 64 | +| 6.14 | Solution #14: Solution for hosting network selection..... | 64 | +| 6.14.1 | Introduction ..... | 64 | +| 6.14.2 | Functional Description ..... | 64 | +| 6.14.3 | Procedures ..... | 65 | +| 6.14.4 | Impacts on services, entities, and interfaces..... | 67 | +| 6.15 | Solution #15: Local service provisioning via PLMN..... | 67 | +| 6.15.1 | Introduction ..... | 67 | +| 6.15.2 | Functional Description ..... | 67 | +| 6.15.3 | Procedures ..... | 68 | +| 6.15.4 | Impacts on Services, Entities, and Interfaces ..... | 68 | +| 6.16 | Solution #16: Access to SNPN with NG-RAN and to WLAN Access Network using the same
credentials..... | 69 | +| 6.16.1 | Introduction ..... | 69 | +| 6.16.2 | Functional Description ..... | 69 | +| 6.16.3 | Procedures ..... | 70 | +| 6.16.3.1 | WLAN Authentication with AAA Server ..... | 70 | +| 6.16.3.2 | User plane aspects..... | 72 | +| 6.16.4 | Impacts on services, entities, and interfaces..... | 72 | +| 6.17 | Solution #17: UE Group specific NAS level congestion control..... | 72 | +| 6.17.1 | Introduction ..... | 72 | +| 6.17.2 | Functional Description ..... | 72 | +| 6.17.3 | Procedures ..... | 73 | +| 6.17.4 | Impacts on services, entities and interfaces..... | 73 | +| 6.18 | Solution #18: Steering of UE to select hosting network for obtaining localized services ..... | 74 | +| 6.18.1 | Introduction ..... | 74 | +| 6.18.2 | Functional Description ..... | 74 | +| 6.18.3 | Procedures ..... | 74 | +| 6.18.4 | Impacts on services, entities, and interfaces..... | 76 | +| 6.19 | Solution #19: Access to SNPN services via Untrusted non-3GPP access network with underlay/overlay
determination..... | 76 | +| 6.19.1 | Introduction ..... | 76 | +| 6.19.2 | Functional Description ..... | 76 | +| 6.19.3 | Procedures ..... | 77 | +| 6.19.4 | Impacts on services, entities, and interfaces..... | 77 | +| 6.20 | Solution #20: Access SNPN via 3GPP and N3GPP AN using same credentials and credential holder..... | 78 | +| 6.20.1 | Introduction ..... | 78 | +| 6.20.2 | Functional Description ..... | 78 | +| 6.20.3 | Procedures ..... | 79 | +| 6.20.4 | Impacts on services, entities, and interfaces..... | 79 | +| 6.21 | Solution #21: Support for NSWOF in SNPN..... | 80 | +| 6.21.1 | Introduction ..... | 80 | +| 6.21.2 | Functional Description ..... | 80 | +| 6.21.3 | Procedures ..... | 81 | +| 6.21.4 | Impacts on services, entities, and interfaces..... | 81 | +| 6.22 | Solution #22: Hosting network to provide localized service based on default credentials..... | 82 | +| 6.22.1 | Introduction ..... | 82 | +| 6.22.2 | Functional Description ..... | 82 | +| 6.22.3 | Procedures ..... | 83 | +| 6.22.4 | Impacts on services, entities, and interfaces..... | 83 | +| 6.23 | Solution #23: Solution for obtaining hosting network selection and access information - PNI-NPN..... | 84 | +| 6.23.1 | Introduction ..... | 84 | +| 6.23.2 | Functional Description ..... | 84 | +| 6.23.3 | Procedures ..... | 85 | +| 6.23.4 | Impacts on services, entities, and interfaces..... | 86 | +| 6.24 | Solution #24: Localized service data provisioning via UDR..... | 86 | +| 6.24.1 | Introduction ..... | 86 | +| 6.24.2 | Functional Description ..... | 86 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.24.3 | Procedures ..... | 87 | +| 6.24.3.1 | Provisioning of non-UE specific localized service data to networks ..... | 87 | +| 6.24.3.2 | Delivering localized service data to the UE via UE policy ..... | 88 | +| 6.24.4 | Impacts on services, entities, and interfaces..... | 89 | +| 6.25 | Solution #25: Temporary network reselection for localized service support..... | 89 | +| 6.25.1 | Introduction ..... | 89 | +| 6.25.2 | Functional Description ..... | 89 | +| 6.25.3 | Procedures ..... | 90 | +| 6.25.3.1 | Overview of Temporary Network Reselection (TNR) to enable localized services ..... | 90 | +| 6.25.3.2 | Home network authorization via Steering of Roaming (SOR) procedure..... | 92 | +| 6.25.4 | Impacts on services, entities, and interfaces..... | 93 | +| 6.26 | Solution #26: Enable UE to query localized services information from the hosting network for service discovery ..... | 94 | +| 6.26.1 | Introduction ..... | 94 | +| 6.26.2 | Functional Description ..... | 94 | +| 6.26.3 | Procedure ..... | 96 | +| 6.26.3.1 | UE query local service information without registering with the hosting network..... | 96 | +| 6.26.3.2 | UE local service discovery while registering with the hosting network..... | 97 | +| 6.26.4 | Impacts on services, entities and interfaces..... | 98 | +| 6.27 | Solution #27: Access to localized service by using LADN and N3IWF overlay architecture ..... | 98 | +| 6.27.1 | Introduction ..... | 98 | +| 6.27.2 | Functional Description ..... | 99 | +| 6.27.2.1 | Architecture ..... | 99 | +| 6.27.2.2 | Hosting network discovery and selection..... | 100 | +| 6.27.2.3 | Registration to hosting network and access to Localized services ..... | 100 | +| 6.27.3 | Procedures ..... | 101 | +| 6.27.3.1 | Requesting Localized service information ..... | 101 | +| 6.27.3.2 | Connection to hosting network and access to Localized services ..... | 101 | +| 6.27.4 | Impacts on services, entities, and interfaces..... | 102 | +| 6.28 | Solution #28: OTT solution for access to localized services ..... | 102 | +| 6.28.1 | Introduction ..... | 102 | +| 6.28.2 | Functional Description ..... | 102 | +| 6.28.3 | Procedures ..... | 104 | +| 6.28.4 | Impacts on services, entities, and interfaces..... | 105 | +| 6.29 | Solution #29: Solution for enabling UE to automatic discover and select a network for accessing local services on top of solution #10..... | 105 | +| 6.29.1 | Introduction ..... | 105 | +| 6.29.2 | Functional Description ..... | 105 | +| 6.29.3 | Procedures ..... | 106 | +| 6.29.4 | Impacts on services, entities and interfaces..... | 107 | +| 6.30 | Solution #30: Solution for steering a UE to a Hosting Network by Home Network..... | 107 | +| 6.30.1 | Introduction ..... | 107 | +| 6.30.2 | Steering a UE to an SNPn Hosting Network..... | 108 | +| 6.30.2.1 | The serving network is Home Network of the UE ..... | 108 | +| 6.30.2.2 | The serving network is not Home Network of the UE ..... | 108 | +| 6.30.2.3 | The selection of an SNPn Hosting Network without Home Network's steering ..... | 109 | +| 6.30.3 | Procedure ..... | 109 | +| 6.30.3.1 | Steer a UE to an SNPn Hosting Network when the serving network is UE's Home Network..... | 109 | +| 6.30.3.2 | Steer a UE to an SNPn Hosting Network when the serving network is not UE's Home Network.... | 111 | +| 6.30.4 | Impacts on services, entities, and interfaces..... | 112 | +| 6.31 | Solution #31: Discovery and selection of Hosting network based on broadcast information ..... | 112 | +| 6.31.1 | Introduction ..... | 112 | +| 6.31.2 | Functional Description ..... | 112 | +| 6.31.3 | Procedures ..... | 113 | +| 6.31.4 | Impacts on services, entities, and interfaces..... | 113 | +| 6.32 | Solution #32: Supporting PNI-NPN as hosting network ..... | 114 | +| 6.32.1 | Introduction ..... | 114 | +| 6.32.2 | Functional Description ..... | 114 | +| 6.32.3 | Procedures ..... | 115 | +| 6.32.4 | Impacts on services, entities, and interfaces..... | 116 | +| 6.33 | Solution #33: network selection for accessing to a hosting network ..... | 116 | +| 6.33.1 | Introduction ..... | 116 | + +| | | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.33.2 | Functional Description ..... | 117 | +| 6.33.3 | Procedures ..... | 117 | +| 6.33.4 | Impacts on services, entities, and interfaces..... | 117 | +| 6.34 | Solution #34: Providing Human Readable Localized Services Information for manual selection..... | 117 | +| 6.34.1 | Introduction ..... | 117 | +| 6.34.2 | Functional Description ..... | 118 | +| 6.34.2.1 | Human Readable Localized Service information in On-Demand SIB ..... | 118 | +| 6.34.2.2 | Construction of URL for webpage retrieval of Human Readable Localized service information. .... | 118 | +| 6.34.3 | Procedures ..... | 119 | +| 6.34.3.1 | Procedure for Human Readable Localized Service information in On-Demand SIB ..... | 119 | +| 6.34.3.2 | Procedure for retrieval of Localized service information from URL ..... | 120 | +| 6.34.4 | Impacts on services, entities, and interfaces..... | 120 | +| 6.35 | Solution #35: Access to localized service by network slicing and URSP ..... | 120 | +| 6.35.1 | Introduction ..... | 120 | +| 6.35.2 | Functional Description ..... | 121 | +| 6.35.3 | Procedures ..... | 121 | +| 6.35.4 | Impacts on services, entities, and interfaces..... | 122 | +| 6.36 | Solution #36: Steering of UEs by home network to a specific hosting network with consideration of location, times, and coverage for key issue #5..... | 122 | +| 6.36.1 | Introduction ..... | 122 | +| 6.36.2 | Functional Description ..... | 123 | +| 6.36.3 | Procedure ..... | 123 | +| 6.36.3.1 | UE-based procedure..... | 123 | +| 6.36.3.2 | UE-and-Network-coordination- based procedure..... | 124 | +| 6.36.4 | Impacts on services, entities and interfaces..... | 124 | +| 6.37 | Solution #37: Enabling access to localized services via a specific hosting network ..... | 125 | +| 6.37.1 | Introduction ..... | 125 | +| 6.37.2 | Functional Description ..... | 125 | +| 6.37.3 | Procedures ..... | 126 | +| 6.37.4 | Impacts on services, entities and interfaces..... | 126 | +| 6.38 | Solution #38: Sequential deregistration by hosting network ..... | 126 | +| 6.38.1 | Introduction ..... | 126 | +| 6.38.2 | Functional Description ..... | 126 | +| 6.38.3 | Procedures ..... | 127 | +| 6.38.4 | Impacts on services, entities, and interfaces..... | 128 | +| 6.39 | Solution #39: Local hosting network specific back-off timer..... | 128 | +| 6.39.1 | Introduction ..... | 128 | +| 6.39.2 | Functional Description ..... | 129 | +| 6.39.3 | Procedures ..... | 129 | +| 6.39.4 | Impacts on services, entities and interfaces..... | 130 | +| 6.40 | Solution #40: Credential provisioning for accessing hosting network ..... | 130 | +| 6.40.1 | Introduction ..... | 130 | +| 6.40.2 | Functional Description ..... | 130 | +| 6.40.3 | Procedures ..... | 131 | +| 6.40.4 | Impacts on services, entities, and interfaces..... | 132 | +| 6.41 | Solution #41: Provisioning of Credentials via Hosting Network PDU Session ..... | 133 | +| 6.41.1 | Introduction ..... | 133 | +| 6.41.2 | Functional Description ..... | 133 | +| 6.41.3 | Procedures ..... | 134 | +| 6.41.4 | Impacts on services, entities and interfaces..... | 135 | +| 6.42 | Solution #42: Solution of UE requesting for hosting network selection and access information via visiting network..... | 135 | +| 6.42.1 | Introduction ..... | 135 | +| 6.42.2 | Functional Description ..... | 135 | +| 6.42.3 | Procedures ..... | 136 | +| 6.42.4 | Impacts on services, entities, and interfaces..... | 137 | +| 6.43 | Solution #43: Solution for Transferring hosting network selection information from hosting network to UE's home network ..... | 137 | +| 6.43.1 | Introduction ..... | 137 | +| 6.43.2 | Functional Description ..... | 137 | +| 6.43.3 | Procedures ..... | 138 | +| 6.43.4 | Impacts on services, entities, and interfaces..... | 138 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------------------------------------------|-----| +| 6.44 | Solution #44: Solution on top of Solution #10 for Serving Network to assist in discovery of hosting networks ..... | 139 | +| 6.44.1 | Introduction ..... | 139 | +| 6.44.2 | Functional Description ..... | 139 | +| 6.44.2.1 | General ..... | 139 | +| 6.44.2.2 | Serving network assistance information in SIB ..... | 139 | +| 6.44.2.2 | Serving network assistance via dedicated signalling ..... | 140 | +| 6.44.3 | Procedures ..... | 140 | +| 6.44.3.1 | Procedure for Hosting network search assistance information in SIB ..... | 140 | +| 6.44.3.2 | Procedure for Hosting network search assistance information in SIB ..... | 141 | +| 6.44.4 | Impacts on services, entities and interfaces ..... | 142 | +| 6.45 | Solution #45: Ensuring UE access localized service in the service area/time ..... | 142 | +| 6.45.1 | Introduction ..... | 142 | +| 6.45.2 | Functional Description ..... | 142 | +| 6.45.3 | Procedures ..... | 143 | +| 6.45.4 | Impacts on services, entities, and interfaces ..... | 144 | +| 6.46 | Solution #46: Accesses Localized Services via URSP rules ..... | 144 | +| 6.46.1 | Introduction ..... | 144 | +| 6.46.2 | Functional Description ..... | 144 | +| 6.46.3 | Procedures ..... | 145 | +| 6.46.4 | Impacts on services, entities, and interfaces ..... | 145 | +| 6.47 | Solution #47: Solution for mitigating overload at home network ..... | 145 | +| 6.47.1 | Introduction ..... | 145 | +| 6.47.2 | Functional Description ..... | 146 | +| 6.47.3 | Procedures ..... | 147 | +| 6.47.3.1 | Adaptive deregistration procedure ..... | 147 | +| 6.47.4 | Impacts on services, entities, and interfaces ..... | 149 | +| 7 | Evaluation ..... | 149 | +| 7.1 | Key Issue #1: Enabling support for idle and connected mode mobility between SNPNS without new network selection ..... | 149 | +| 7.2 | Key Issue #2: Support of Non-3GPP access for SNPN ..... | 151 | +| 7.3 | Key Issue #3: Enabling NPN as hosting network for providing access to localized services ..... | 154 | +| 7.4 | Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services ..... | 154 | +| 7.4.1 | General ..... | 154 | +| 7.4.2 | Evaluation for the content of the localized service information ..... | 155 | +| 7.4.3 | Evaluation for from where and how UE obtains the localized service information ..... | 156 | +| 7.4.4 | Evaluation for how the localized service information is used by UE ..... | 158 | +| 7.4.5 | Evaluation for what credentials are used to access hosting network and how to obtain them ..... | 159 | +| 7.4.6 | Evaluation for how localized service is accessed in hosting network per agreed conditions ..... | 159 | +| 7.4.7 | Evaluation for the scenario where hosting network is a PNI-NPN ..... | 160 | +| 7.5 | Key Issue #5: Enabling access to localized services via a specific hosting network ..... | 162 | +| 7.6 | Key Issue #6: Support for returning to home network ..... | 164 | +| 8 | Conclusions ..... | 170 | +| 8.1 | Key Issue #1: Enabling support for idle and connected mode mobility between SNPNS without new network selection ..... | 170 | +| 8.2 | Key Issue #2: Support of Non-3GPP access for SNPN ..... | 170 | +| 8.3 | Key Issue #3: Enabling NPN as hosting network for providing access to localized services ..... | 172 | +| 8.4 | Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services ..... | 172 | +| 8.4.1 | General ..... | 172 | +| 8.4.2 | Conclusion for the content of the information for accessing localized services ..... | 173 | +| 8.4.3 | Conclusion for from where and how UE obtains the information for accessing localized service ..... | 173 | +| 8.4.4 | Conclusion for how the localized service information is used by UE ..... | 174 | +| 8.4.5 | Conclusion for what credentials are used to access hosting network and how to obtain them ..... | 174 | +| 8.4.6 | Conclusion for how localized service is accessed in hosting network per agreed conditions ..... | 175 | +| 8.5 | Key Issue #5: Enabling access to localized services via a specific hosting network ..... | 175 | +| 8.6 | Key Issue #6: Support for returning to home network ..... | 175 | +| Annex A: Change history ..... | | 177 | + + + +## Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +--- + +# 1 Scope + +The scope of this Technical Report is to study further enhancements of the 5GS to support Non-Public Networks including the following aspects: + +1. Support for enhanced mobility by enabling support for idle and connected mode mobility between SNPNS without new network selection. +2. Support for non-3GPP access for SNPN. +3. Address SA WG1 requirements in TS 22.261 [2] related to support for Providing Access to Localized Services. + +NOTE: The TS 22.261 [2] requirements for Providing Access to Local Services related to Multicast/Broadcast are not part of the scope. + +--- + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.261: "Service requirements for next generation new services and markets". +- [3] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [4] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [5] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System". +- [6] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode". +- [7] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3". +- [8] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)". +- [9] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [10] 3GPP TS 33.501: "Security architecture and procedures for 5G System". +- [11] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". +- [12] 3GPP TR 22.844: "Study on 5G Networks Providing Access to Localized Services". +- [13] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [14] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification". +- [15] 3GPP TS 38.300: "NR and NG-RAN Overall Description". +- [16] 3GPP TR 23.700-17: "Study on support for 5WWC; Phase 2". + +- [17] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [18] 3GPP TR 23.700-85: "Study on enhancement of 5G User Equipment (UE) policy". +- [19] 3GPP TS 24.526: "User Equipment (UE) policies for 5G System (5GS)". +- [20] 3GPP TS 28.557: "Management and orchestration; Management of Non-Public Networks (NPN)". +- [21] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM)". +- [22] 3GPP TR 33.857: "Study on enhanced security support for Non-Public Networks (NPN)". +- [23] 3GPP TR 23.700-05: "Study on architecture enhancements for vehicle-mounted relays". +- [24] 3GPP TR 23.700-41: "Study on enhancement of network slicing; Phase 3". + +--- + +## 3 Definitions of terms, symbols and abbreviations + +### 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1], TS 23.501 [3] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Local service, Localized service:** Service, which is localized (i.e. provided at specific/limited area) and/or can be bounded in time. The service can be realized via applications (e.g. live or on-demand audio/video stream, electric game, IMS, etc), or connectivity (e.g. UE to UE, UE to Data Network, etc.). + +**Localized service provider:** application provider or network operator who make their services localized and to be offered to end user via a hosting network. + +**Hosting network:** A network providing access to Local/Localized services. + +**Home network:** A network owning the current in use subscription/credential of the UE. Home network can be either PLMN or NPN. + +NOTE 1: For SNPN case, TS 23.501 [3] defines UE access using credentials owned by a Credentials Holder separate from the SNPN. + +**Home network service:** Service, which is offered to UE based on subscription agreed with home network operator. + +**Return to home network:** UE leaves the hosting network (e.g. when the Local/Localized service is terminated), and resumes to use subscription/credential of home network. It can involve a network selection (e.g. select HPLMN or VPLMN) as specified in TS 23.122 [6], and can involve deactivation/activation of SNPN access mode. + +NOTE 2: These are the definitions used in this TR, SA WG2 can consider if the definitions are used in the normative phase. + +### 3.2 Void + +### 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [3] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1], TS 23.501 [3]. + +#### *Abbreviation format (EW)* + + + +--- + +## 4 Architectural Assumptions and Requirements + +**Editor's note:** This clause will list general architectural assumptions and principles for this study. + +- Solutions shall build on the 5G System architectural principles as in TS 23.501 [3], including flexibility and modularity for newly introduced functionalities. +- Functionality to enable regulatory services like emergency services are assumed to re-use existing architecture mechanisms with no or limited impact. + +NOTE: Any impacts to PWS or LI would be handled by other responsible WGs i.e. CT1 and SA3-LI respectively. + +- Hosting network can be NPN, i.e. SNPN, or PNI-NPN. +- Home network can be NPN or PLMN. +- The term "home network" does not imply a roaming relationship. +- Only subscribers of a public network can roam into a PLMN. + +--- + +## 5 Key Issues + +### 5.1 Key Issue #1: Enabling support for idle and connected mode mobility between SNPNs without new network selection + +#### 5.1.1 Description + +The NPN Phase 2 study item contains following work task that assumes the UE is in SNPN access mode: Support for enhanced mobility by enabling support for idle and connected mode mobility between SNPNs without new network selection. This KI aims at studying impacts to the 5G System for scenarios where the UE has a subscription with each of the source and target SNPN or can access both the source and target SNPN using credentials from a Credentials Holder: + +- Study how to enable optimizations for idle mode mobility without new network selection in the inter-SNPN mobility case. +- Study how to enable optimizations for connected mode mobility without new network selection in the inter-SNPN mobility case. +- Whether and how session continuity can be supported in the case of idle mode and connected mode mobility between SNPNs. +- Whether and which additional information transfer between SNPNs on top of Rel-17 is required for the above mentioned mobility scenarios. + +## 5.2 Key Issue #2: Support of Non-3GPP access for SNPN + +### 5.2.1 Description + +Currently the 3GPP specifications do not support direct connection to SNPN via non-3GPP access networks. Indirect connection to SNPN via PLMN using untrusted non-3GPP access architecture is supported as shown in Annex D, clause D.3 of TS 23.501 [3] (PLMN as underlay network and SNPN as overlay network). + +There are already non-3GPP access technologies which are in use in enterprises and campuses, and it is foreseen that use of such non-3GPP access technologies will continue to evolve. The integration of these existing technologies in the SNPN would add flexibility to the SNPN operators. In general, the solutions of this key issue aim to address the support for non-3GPP access for SNPN. + +One objective of this key issue is to enable the 5GS to support direct connection of non-3GPP access networks to the SNPN's 5GC. + +NOTE 1: Co-ordination with BBF and CableLabs will take place as needed during the study for solutions related to Wireline 5G Access Network. + +NOTE 2: Roaming for SNPN is out of scope of this key issue. + +## 5.3 Key Issue #3: Enabling NPN as hosting network for providing access to localized services + +### 5.3.1 Description + +Providing access to local services refers to the capability to provide access to a hosting network and a set of services offered by the hosting network provider, and 3rd party service providers including other network operators and 3rd party application providers. The services may be localized (i.e. provided at specific/limited area) and may be bounded in time. The user may become aware of the available access to local services, and the process to gain and terminate access to the hosting network and local services. This process should be efficient, and convenient from a user experience standpoint. + +Providing access to local services creates new opportunities for users and service providers. For example, access can be provided in areas where there is no coverage provided by other networks (for example, on a cargo ship out at sea), or the access and local services can be established as needed (on a short-term basis), without the need for long term business relationships, permanently installed equipment, etc. + +The type of local services and access for localized services via a hosting network can be promoted and arranged through different channels. Principally the Localized service provider (e.g. brick and mortar businesses, construction contractors, first responder agencies, etc.) will provide information and proper incentive or instructions to potential users so that they will seek to access the local services via hosting networks. + +The 5G network as hosting network offering access to such localized services can be either a PNI-NPN or an SNPN. + +It is assumed that hosting network and the localized services can be operated by different entities. Localized services may provide more than just data connectivity to end users, e.g. additional information/incentive/instructions in order to seek access to the localized services in. + +This key issue aims at addressing how to enable a NPN (i.e. a SNPN or a PNI-NPN) as a hosting network for providing access to localized services with the following aspects: + +- Define hosting NPN and identify the difference(s) between hosting NPN and NPN defined in both Rel-16 and Rel-17. +- Define localized services and identify the difference(s) between localized services and regular services. +- Define where and when localized services are available based on localized service agreements (i.e. a service agreement for a localized service). + +NOTE 1: SA WG2 works under the assumption that the relationships and the localized service agreements are already available by means outside SA WG2 scope i.e. SA WG2 is to agree where the information is made available. + +- What is required to enable communication between a network operator deploying a hosting network and a localized services provider: + - Investigate which type of interaction (e.g. configuration of the hosting network, information reporting) is needed, in such relation to enable the localized services provider for making the best use of the hosting network; and + +NOTE 2: Collaboration with SA WG5 and SA WG3 may be needed. + +## 5.4 Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services + +### 5.4.1 Description + +For providing localized services to UE, the UE needs to be able to discover, select and access the hosting network for the localized services. The discovery mechanism can be based on provisioning the UE with appropriate information. TS 22.261 [2] has defined various requirements regarding discovery, selection and access of a hosting network in clauses 6.41.2.3, 6.41.2.4 and 6.41.2.5 of TS 22.261 [2]. + +NOTE: For the hosting network, only NPN (SNPN or PNI-NPN) is considered in this study. + +The corresponding solutions need to consider following assumptions: + +- The UE can, but not necessarily, have prior subscription with the hosting network and/or the localized services provider. +- The information for discovery of hosting network offering the localized services can be provided to the UE via either hosting network or UE's home network, or UE's serving network or localized services provider. This information allows the UE to discover, select and access the hosting network offering the localized services. +- Reception and usage of configuration provided by a localized services provider to discover and access a hosting network and localized services is subject to home network operator's policy and agreement between a localized services provider and hosting network operator, including the considerations of prior service agreement with a localized services provider and no prior subscription to hosting network. +- If the UE is able to obtain services from two networks simultaneously, it may additionally select the hosting network. +- The selection of a hosting network can be done on request by the user, i.e. using manual selection, unless the UE can, maintain the PDU Sessions established with the home network and retain the services provided by the home network on these PDU Sessions, while selecting the hosting network (see KI#5). +- Automatic selection of a hosting network needs to be allowed by the home network of the subscription/credentials used by the UE. +- A localized service agreement is established (see KI#3). + +This key issue aims at addressing the following aspects: + +- Investigate which type of information needs to be exchanged between hosting network and a localized services provider so that a UE can perform discovery, selection and connection of the hosting network and access the localized services provided via the hosting network. + +NOTE 1: The hosting network can also act as a service provider for localized services. + +- What is the provisioning mechanism and the information needed for the UE to discover, select and access suitable hosting network for localized services with possible validity conditions for accessing the hosting network offering the localized services, because of the nature of the localized service and hosting network (e.g. + +time and location constrains). This includes information enabling the UE to be aware of services that can be accessed via hosting NPN. + +- Discovery and selection procedures of hosting network and localized services provided via the hosting network for UE to obtain localized services. Both automatic and end user manual selection apply. +- How a UE already registered in a network (PLMN or NPN) can discover a suitable hosting network and the localized services provided via the hosting network when the hosting network and/or localized services become available. +- How to ensure the localized services are accessed by UE according to the conditions when and where the localized services are allowed to be accessed by the UE. +- How the UE is provisioned with credentials (if required) to access the selected localised services provided via the hosting network. +- Mechanisms to authorize UE to access the hosting network. + +NOTE 2: Security aspects (such as authentication of the UE and security aspects of provisioning) are addressed in SA WG3. The authentication architecture is addressed in both SA WG2 and SA WG3. + +## 5.5 Key Issue #5: Enabling access to localized services via a specific hosting network + +### 5.5.1 Description + +Hosting NPN provides access to localized services. But home network operator of a UE can also utilize the hosting network based on a relationship established between hosting network operator and UE's home operator, so that it is possible to enable the UE with a subscription from home network to access home network services via the hosting network, in addition to the localized services. TS 22.261 [2] has defined the following requirements: + +- *The 5G system shall be able to allow the home network to steer its UE(s) to a hosting network with the consideration of the location, times, coverage of the hosting network and services offered by the home network and hosting network.* +- *A localized service agreement is established (see KI#3).* +- *The 5G system shall enable the home network operator to indicate to the UE what services are preferred to be used from the home network when the UE connects to a hosting network and the requested services are available from both the hosting and the home network.* +- *Based on localized service agreements, the hosting network shall be able to provide required connectivity and QoS for a UE simultaneously connected to the hosting network for localized services and its home network for home network services.* +- *A UE shall be able to connect to its home network via the hosting network, if supported by the hosting network and the home network based on localized service agreements.* + +This key issue aims at addressing the following aspects: + +- How and whether the home network, determine the service availability of a hosting network, and interacts with hosting network to authorize home network's subscribers to access home network services via the hosting network, at certain time and location, coverage of the hosting network and services offered by the hosting network. +- How to enable UE to access both home network services and localized services via the hosting network, and seamless service continuity for home network services and localized services when UE moves between different networks providing the same services. This includes how to configure UE with information enabling the UE to be aware of services that can be accessed via a specific network (e.g. home network or hosting NPN). +- How home network determines the need to steer or instruct the UE, and how the home network steers or instructs the UE to select a hosting network for obtaining home network services or localized services or select a network for a specific service which is available from both hosting and home network. + +- How to collect charging information for the use of localized services at the hosting network and provide the charging records to UEs' home operators. + +NOTE 1: Charging aspects needs to be coordinated with SA WG5. + +NOTE 2: It is assumed that existing mechanisms can be used to support Regulatory Services, e.g. PWS and emergency services. + +## 5.6 Key Issue #6: Support for returning to home network + +### 5.6.1 Description + +According to SA WG1 TR 22.844 [12], when local service is over, large number of UEs would attempt registration back to their home network. This may lead to a signalling peak in the home network and result in user plane and control plane overload causing for example longer waiting for users to re-register to/re-select their home network. + +There are various load control mechanisms already defined e.g.: + +- Access control and barring as defined in clause 5.2.5 of TS 23.501 [3]; +- Control Plane Load Control, Congestion and Overload Control as defined in clause 5.19 of TS 23.501 [3]; +- Prevention of signalling overload related to Disaster Condition and Disaster Roaming service as defined in clause 5.40.6 of TS 23.501 [3]. + +This key issue aims to study whether the existing mechanisms for overload control in the network can support all the requirements in clause 6.41 of TS 22.261 [2] "Providing Access to Local Services" and whether any enhancements or additional mechanisms need to be defined. The following aspects will be considered: + +- How to mitigate user plane and control plane overload caused by a high number of UEs returning from a temporary local access of a hosting network to their home network in a very short period of time. +- How to minimize the impact on the UE's communication e.g. to prevent user plane and control plane outages when returning to a home network together with other high number of UEs in a very short period of time, after terminating their temporary local access to a hosting network. + +NOTE: The solution for this KI may need to consider mechanism developed for KI#5 "Enabling access to localized services via a specific hosting network". + +--- + +## 6 Solutions + +**Editor's note:** This clause is intended to document the agreed architecture solutions and a mapping of solutions to key issue(s) in clause 6.0. Each solution should clearly describe which of the key issues it covers and how. + +## 6.0 Mapping Solutions to Key Issues + +Table 6.0-1: Mapping Solutions to Key Issues + +| Solutions | Key Issues | | | | | | +|-----------|------------|---|---|---|---|---| +| | 1 | 2 | 3 | 4 | 5 | 6 | +| 1 | X | | | | | | +| 2 | | X | | | | | +| 3 | | X | | | | | +| 4 | | X | | | | | +| 5 | | X | | | | | +| 6 | | X | | | | | +| 7 | | | X | X | X | X | +| 8 | | | | | | X | +| 9 | | | | | | X | +| 10 | | | | X | | X | +| 11 | | | | X | X | | +| 12 | | | X | X | | | +| 13 | | | X | X | X | | +| 14 | | | | X | | | +| 15 | | | | X | X | | +| 16 | | X | | | | | +| 17 | | | | | | X | +| 18 | | | | | X | | +| 19 | | X | | | | | +| 20 | | X | | | | | +| 21 | | X | | | | | +| 22 | | | X | | | | +| 23 | | | | X | | | +| 24 | | | | X | | | +| 25 | | | | X | | X | +| 26 | | | | X | | | +| 27 | | | | X | X | | +| 28 | | | | X | X | | +| 29 | | | | X | X | | +| 30 | | | | X | | | +| 31 | | | | X | | | +| 32 | | | | X | | | +| 33 | | | | X | | | +| 34 | | | | X | | | +| 35 | | | | X | X | | +| 36 | | | | | X | | +| 37 | | | | | X | | +| 38 | | | | | | X | +| 39 | | | | | | X | +| 40 | | | | X | X | | +| 41 | | | X | X | | | +| 42 | | | | X | | | +| 43 | | | | X | | | +| 44 | | | | X | | | +| 45 | | | | X | X | | +| 46 | | | | | X | | +| 47 | | | | | | X | + +### 6.1 Solution #1: Enable efficient mobility via equivalent SNPNs + +#### 6.1.1 Introduction + +The solution addresses key issue #1 "Enhanced mobility between SNPNs without new network selection". + +The solution utilizes a list of SNPN identities (i.e. a list of combinations of PLMN ID and NID) to enable UE with one single SNPN subscription to efficiently access different SNPNs without performing new network selection. The list is implemented by the similar logic as the list of equivalent PLMNs, as specified in clause 5.18.2a of TS 23.501 [3]. + +The solution also re-use existing function as specified in clause 5.18.1 of TS 23.501 [3], where different combination of PLMN ID and NID can point to the same 5GC. + +## 6.1.2 Functional Description + +In existing specification, the UE can receive a list of equivalent PLMNs from core network. Such equivalent PLMN list will assist UE to select a cell from another PLMN during mobility without the need to perform new network selection. + +In this solution, a list of equivalent SNPNs is proposed to facilitate the idle and connected mobility between SNPNs, reusing similar functions which are defined for PLMN: + +- The core network can provide a list of SNPN identities to the UE that the UE consider as equivalent to the registered SNPN. +- The list of equivalent SNPNs can be prepared based on AMF local configuration. +- The UE stores the list of equivalent SNPNs, and update or delete the list at the end of each registration procedure in the same way as done with the list of equivalent PLMNs as described in TS 23.122 [6] and TS 24.501 [7]. +- The stored list consists of a list of equivalent SNPNs' identities as downloaded by the network plus the SNPN identity of the registered SNPN that downloaded the list. When the UE is switched off, the UE shall keep the stored list so that it can be used for SNPN selection after switch on. +- The lists of equivalent SNPNs are stored and used per SNPN subscription by the UE. +- These SNPNs in the list shall be regarded by the UE as equivalent to each other for SNPN selection and cell (re)selection. +- The list can also be provided from AMF to NG-RAN for the purpose of connected mode mobility. + +## 6.1.3 Procedures + +When UE accesses multiple SNPNs using the credentials holder function as depicted in Figure 6.1.3-1, the following applies: + +- SNPN-1 and SNPN-2 are identified by different SNPN identity, i.e. combination of PLMN ID and NID. +- SNPN-1 and SNPN-2 are the Credentials Holder(CH) for each other: + - UE of SNPN-1 can register in SNPN-2, where using SNPN-1 as the CH. + - UE of SNPN-2 can register in SNPN-1, where using SNPN-2 as the CH. +- NFs from one SNPN (e.g. SNPN-1) are only authorized to consume services from the other SNPN (e.g. SNPN-2) which is acting as CH, as depicted in Figure 5.30.2.9.3-1 of TS 23.501 [3]. +- UE from each SNPN has only the subscription/credential from the respective SNPN: + - UE of SNPN-1 has only subscription/credential from SNPN-1. + - UE of SNPN-2 has only subscription/credential from SNPN-2. +- When UE holds the list of equivalent SNPNs (SNPN-1 and SNPN-2), it efficiently makes cell (re)selection when doing idle mode mobility between the SNPN-1's NG-RAN and SNPN-2's NG-RAN, without the need to perform network selection. +- The Allowed NSSAI applies to the registered SNPN. If SNPNs support an RA with TAIs of equivalent SNPNs, then the same S-NSSAI values are required to be supported and used in those equivalent SNPNs. + +![Diagram showing a User Equipment (UE) connected to a central point, which is then connected to two separate SNPNs (SNPN-1 and SNPN-2). The connection between the central point and the SNPNs is labeled 'Reference points between CH and SNPN (TS 23.501 Figure 5.30.2.9.3-1)'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +The diagram illustrates a User Equipment (UE) represented by a rectangle on the left. A vertical line connects the UE to a central point. From this central point, two vertical lines extend to two separate ovals labeled 'SNPN-1' (top) and 'SNPN-2' (bottom). To the right of the central connection point, there is a text label: 'Reference points between CH and SNPN (TS 23.501 Figure 5.30.2.9.3-1)'. + +Diagram showing a User Equipment (UE) connected to a central point, which is then connected to two separate SNPNs (SNPN-1 and SNPN-2). The connection between the central point and the SNPNs is labeled 'Reference points between CH and SNPN (TS 23.501 Figure 5.30.2.9.3-1)'. + +**Figure 6.1.3-1: UE accesses multiple SNPNs using CH** + +When UE accesses multiple SNPNs belonging to the same administrative entity as depicted in Figure 6.1.3-2, the following applies: + +- SNPN-1 and SNPN-2 are identified by different SNPN identity, i.e. combination of PLMN ID and NID. +- SNPN-1 and SNPN-2 belong to the same administrative entity. A common 5GC is used and can be managed by the same administrative entity to support both SNPN identities of SNPN-1 and SNPN-2. +- NFs of one SNPN (e.g. SNPN-1) can be authorized to consume services from NFs of the other SNPN (e.g. SNPN-2). +- UE from each SNPN has only the subscription from the respective SNPN. +- When UE is provided with the list of equivalent SNPNs (SNPN-1 and SNPN-2), it efficiently makes cell (re)selection when doing idle mode mobility between the SNPN-1's NG-RAN and SNPN-2's NG-RAN, with all the mobility and session context transferred, but without the need to perform network selection. PDU session continuity is supported. +- UE selects and attempts registration on available and allowable SNPNs by taking the equivalent SNPNs (if available) into account. + +NOTE 1: CT WG1 will specify the details and final order of the network selection procedure. + +- When NG-RAN is provided with the list of equivalent SNPNs (SNPN-1 and SNPN-2) in the MRL, it makes use of such info to achieve connected mode mobility between SNPN-1 and SNPN-2. +- In the case of handover or network controlled release to a shared network: + - When multiple SNPN IDs are broadcasted in a cell selected by NG-RAN, NG-RAN selects a target SNPN, taking into account the list of SNPN IDs which are equivalent to the serving SNPN in the Mobility Restriction List (MRL) from the AMF. + - For Xn based HO procedure, source NG-RAN indicates the selected SNPN ID to the target NG-RAN. + - For N2 based HO procedure, the source NG-RAN indicates a selected SNPN ID to the AMF in the HO required message. Source AMF uses the selected SNPN ID and target tracking area information supplied by the source NG-RAN to select the target AMF. The source AMF should forward the selected SNPN ID to the target AMF. The target AMF indicates the selected SNPN ID to the target NG-RAN so that the target NG-RAN can select target cells for future handover appropriately. + +NOTE 2: It is up to RAN WG3 to decide how to add the selected SNPN ID in NGAP for connected mode mobility. + +Serving SNPN ID if changed is indicated to the UE as part of the UE registration procedure. + +![Diagram showing a User Equipment (UE) box on the left and a large oval labeled 'Enterprise-A' on the right. Inside the 'Enterprise-A' oval are two smaller ovals labeled 'SNPN-1' and 'SNPN-2'.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates a User Equipment (UE) represented by a rectangular box containing the letters 'U' and 'E' stacked vertically. To the right of the UE is a large vertical oval labeled 'Enterprise-A' at the top. Inside this oval are two smaller horizontal ovals, one above the other, labeled 'SNPN-1' and 'SNPN-2' respectively. This visualizes the UE accessing multiple SNPNs within a single administrative entity. + +Diagram showing a User Equipment (UE) box on the left and a large oval labeled 'Enterprise-A' on the right. Inside the 'Enterprise-A' oval are two smaller ovals labeled 'SNPN-1' and 'SNPN-2'. + +**Figure 6.1.3-2: UE accesses multiple SNPNs belonging to the same administrative entity** + +If equivalent SNPNs within an RA is to be supported, then NAS can be extended with a new Partial tracking area identity list – type of list that includes also the NID (together with the MCC and MNC), and NGAP can be extended allowing the TAI list to be associated to different SNPNs e.g. by adding a new TAI encoding for SNPNs. + +NOTE 3: For ensuring TAI list to work with Equivalent SNPNs, the NID must be defined to be unique, i.e. the UE will by default assume it is unique. The NID included in the new Partial tracking area must be configured such that NID is unique at least across the Registration Areas. + +#### 6.1.4 Impacts on services, entities, and interfaces + +UE and AMF support of equivalent SNPN list in NAS. + +NG-RAN and AMF support of equivalent SNPNs in NGAP. + +UE/NG-RAN/AMF take equivalent SNPN list into consideration, for supporting relevant functions, e.g.: + +- idle/connected network selection. +- cell (re)selection. + +AMF to inform UE the registered SNPN ID change during mobility in Registration Accept message. + +Minor impact on the following clauses in TS 23.501 [3]: + +- clause 5.18.1, NOTE 3. +- clause 5.18.2a. +- clause 5.18.4. + +NGAP impact for supporting connected mode mobility between SNPNs. + +NOTE: It is up to RAN WG3 to decide how to extend NGAP for connected mode mobility. + +If equivalent SNPNs within an RA is to be supported, then AMF and the UE needs to support a new Partial tracking area identity list – type of list that includes also the NID (together with the MCC and MNC), and NGAP is updated to support TAIs of different SNPNs (i.e. associated to MCC, MNC and NID). + +UE impact to apply Allowed NSSAI to an RA including one or more TAIs of equivalent SNPNs. + +## 6.2 Solution #2: Access to SNPN services via Untrusted non-3GPP access network + +### 6.2.1 Introduction + +Clause 5.30.2.8 and Annex D, clause D.3 of TS 23.501 [3] specify how the UE can access SNPN services via a PLMN. + +This solution defines how the UE can access SNPN services via Untrusted non-3GPP access network. + +### 6.2.2 Functional Description + +To access SNPN services, a UE that has successfully obtained IP connectivity via an Untrusted non-3GPP access network may select the N3IWF of an SNPN and register with that SNPN (using the credentials of that SNPN) following the same N3IWF selection procedure as specified for access to stand-alone non-public network services via PLMN in clause 6.3.6.2a of TS 23.501 [3]. + +UE initiates N3IWF selection for emergency services when the UE detects a user request for emergency session and determines that Untrusted non-3GPP access shall be used for the emergency access. The UE with SNPN subscription performs the following: + +- If the UE determines that it is located in the same country as the subscribed SNPN, the UE uses the configured N3IWF FQDN for N3IWF selection. +- Otherwise, the UE follows the N3IWF selection procedure for Emergency services for UE not equipped with UICC, as defined in clause 6.3.6.4.2 of TS 23.501 [3]. + +UE equipped with Default UE credentials only shall not attempt to register with an N3IWF. Instead, UE does one of the following: + +- connects directly (i.e. without connected to a N3WIF) with a PVS reachable from the local Untrusted non-3GPP access network (e.g. via the Internet) using the local IP connectivity (how the UE selects the PVS is out of 3GPP scope). +- performs the UE onboarding procedure via an ON-SNPN with 3GPP access and connects with a PVS using the IP connectivity provided by the ON-SNPN. +- In either case the PVS performs provisioning of the UE with SNPN credentials for primary authentication and other information to enable access to the desired SNPN, including N3IWF identifier configuration and Non-3GPP Access node selection information. + +NOTE: For UE equipped with Default UE credentials only (and in absence of an ON-SNPN with 3GPP access) this solution assumes that the PVS is reachable over the public Internet that the UE accesses via the untrusted non-3GPP access network. + +### 6.2.3 Procedures + +The procedure for selection of N3IWF of an SNPN for a UE connected to an untrusted non-3GPP access network is identical to the procedure for selection of N3IWF of an SNPN for a UE connected to a PLMN, the latter being described in clause 6.3.6.2a of TS 23.501 [3]. + +The [NGAP] INITIAL UE MESSAGE is extended to indicate the "selected NID" in addition to the existing "Selected PLMN identity". The encoding of this additional information is left to RAN WG3 to determine. + +NOTE: The lack of "selected NID" in [NGAP] INITIAL UE MESSAGE in Rel-17 for untrusted non-3GPP access was omitted due to the fact that SNPN support was limited to 3GPP access. + +## 6.2.4 Impacts on services, entities, and interfaces + +UE impact: + +- Ability to apply the existing procedures for selection of N3IWF of an SNPN for a UE connected to a PLMN (described in clause 6.3.6.2a of TS 23.501 [3]) when the UE is connected over Untrusted non-3GPP access. + +N3IWF impact: + +- Ability to select and to connect to the 5GC network of an SNPN and convey the "selected NID" to the AMF, in addition to the "Selected PLMN identity". + +NOTE: It is up to RAN WG3 to decide how NGAP is extended i.e. which IE is used for forwarding the selected NID. + +## 6.3 Solution #3: Access to SNPN services via Trusted non-3GPP access network + +### 6.3.1 Introduction + +This solution defines how the UE can access SNPN services via a Trusted non-3GPP access network. It is based on clause 6.3.12.2 of TS 23.501 [3], which defines the access network selection procedure for access to PLMN services via a Trusted non-3GPP access network. + +### 6.3.2 Functional Description + +To access SNPN services via a Trusted non-3GPP access network, the UE follows the same procedures used for accessing a PLMN via a Trusted non-3GPP access network defined in clause 6.3.12.2 of TS 23.501 [3] with the following clarifications and additions: + +- The UE initiates the access network selection procedure specified in clause 6.3.12.2 of TS 23.501 [3] and constructs a list of available SNPNs. This list contains the SNPNs advertised by all discovered non-3GPP access networks. A non-3GPP access network may advertise (e.g. with ANQP), not only the PLMNs with which 5G connectivity is supported (as specified in clause 6.3.12.2 of TS 23.501 [3]), but also the SNPNs with which 5G connectivity is supported. +- The UE selects an SNPN that is included in the list of available SNPNs. +- When the UE wants to perform UE onboarding via an SNPN, the UE may select an SNPN that is included in the pre-configured ON-SNPN selection information. + +NOTE 1: If the same SNPN identifier is included in the lists advertised by multiple non-3GPP access networks and the UE has determined to connect to this SNPN, the UE selects the underlying non-3GPP access network through which to establish the connection based on UE implementation. + +- The UE selects a non-3GPP access network that supports 5G connectivity to the selected SNPN and initiates the registration procedure via trusted non-3GPP access specified in clause 4.12a.2.2 of TS 23.502 [4] in order to register with the selected SNPN via the selected non-3GPP access network. During the EAP authentication procedure the NAI provided by the UE indicates that 5G connectivity to a specific SNPN is required, e.g. NAI = "@nai.5gc.nid.mnc.mcc.3gppnetwork.org". + +NOTE 2: In the case of SNPN ID with self-assigned NID, if the UE, when trying to register with an SNPN ID via TNAN X, is rejected by the AMF with a cause code that temporarily prevents the UE from registering with this SNPN ID, the UE does temporarily not attempt to register with the same SNPN ID, even if the same SNPN ID is advertised via another TNAN. + +- If there are multiple non-3GPP access networks that support 5G connectivity to the selected SNPN as described in clause 6.3.3, then the UE places these non-3GPP access networks in a prioritized list and selects the highest priority non-3GPP access network from this list. To determine the priority of a non-3GPP access network, the UE shall apply the WLANSP rules (if provided), and the procedure specified in clause 6.6.1.3 of TS 23.503 [5], + +"UE procedure for selecting a WLAN access based on WLANSP rules". If the UE is not provided with WLANSP rules, the UE determines the priority of a non-3GPP access network by using implementation means. + +- UE accessing the SNPN with credentials from CH is supported as described in clause 6.3.3.1. +- UE onboarding via Trusted non-3GPP access is supported as follows: + - The non-3GPP access network advertises (e.g. via ANQP) an Onboarding enabled indication, as defined in clause 5.30.2.10.2.3 of TS 23.501 [3] for the 3GPP access. + - As part of UE registration via Trusted non-3GPP access, in Figure 4.12a.2.2-1, step 5 of TS 23.502 [4] the UE provides an onboarding indication inside the AN-Parameters. +- Emergency services via Trusted non-3GPP access to an SNPN are supported as follows: + - UE shall attempt Emergency services over Trusted non-3GPP access only if there is no 3GPP coverage. + - In presence of Trusted non-3GPP access networks providing access to both SNPNs and PLMNs the UE initiates Emergency service with either an SNPN or a PLMN based on implementation. +- The non-3GPP access network advertises the support of Emergency service (e.g. via ANQP). + +### 6.3.3 Procedures + +#### 6.3.3.1 Access Network Selection procedure + +The UE follows the existing procedures for network selection in SNPN access mode defined in clause 5.30.2.4.2 (Automatic network selection) and clause 5.30.2.4.3 (Manual network selection) of TS 23.501 [3]. The prerequisite for these procedures is the following: + +UE is configured with one or more of the following lists as defined in clause 5.30.2.3 of TS 23.501 [3]: + +- User controlled prioritized list of preferred SNPNs; +- Credentials Holder controlled prioritized list of preferred SNPNs; +- Credentials Holder controlled prioritized list of GINs. + +A UE enabled to support UE Onboarding may be pre-configured with ON-SNPN selection information as described in clause 5.30.2.10.2.4 of TS 23.501 [3]. + +The non-3GPP access network advertises (e.g. via ANQP) the following information: + +- For SNPN supporting UE access using credentials from a CH, the indications defined in clause 5.30.2.2 of TS 23.501 [3] are used: + - An indication per SNPN of whether access using credentials from a Credentials Holder is supported; + - List of supported Group IDs for Network Selection (GINs) per SNPN; + - An indication per SNPN of whether the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. UEs that do not have any PLMN ID and NID nor GIN broadcast by the SNPN in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs. +- For SNPN supporting UE onboarding service, the Onboarding enabled indication as defined in clause 5.30.2.10.2.3 of TS 23.501 [3]: + - An onboarding enabled indication that indicates whether onboarding is currently enabled for the SNPN. +- For SNPN supporting Emergency service via Trusted non-3GPP access: + - an Emergency service indication. + +The [NGAP] INITIAL UE MESSAGE should be extended to indicate the "selected NID" in addition to the existing "Selected PLMN identity". The encoding of this additional information is left to RAN WG3 to determine. + +NOTE: The lack of "selected NID" in [NGAP] INITIAL UE MESSAGE in Rel-17 for Trusted non-3GPP access was omitted due to SNPN support was limited to 3GPP access. + +### 6.3.3.2 Registration procedure + +The UE registers with the selected SNPN via the trusted non-3GPP access network using the procedure described in clause 4.12a.2 of TS 23.502 [4] with the enhancements to the following steps: + +3. The UE requests "5G connectivity" to a specific SNPN, e.g. NAI = "@nai.5gc.nid.mnc.mcc.3gppnetwork.org". The TNAP selects a TNGF which is associated with the requested SNPN ID. + 5. In the Access Network parameters (AN parameters) container, the UE includes an Establishment cause set to a value corresponding to the service/functionality which the UE wants to use. For example, the Establishment cause may be set to 'UE onboarding'. +- 6a. The TNGF selects an AMF according to the included Establishment cause. + +## 6.3.4 Impacts on services, entities, and interfaces + +UE impact: + +- Ability to read SNPN identifiers in the list of available networks with which 5G connectivity is supported, as advertised by the non-3GPP access network. +- Ability to select an SNPN that is included in the list of available SNPNs as described in clause 6.3.3. +- Support for Emergency services as described in clause 6.3.2. +- Support for UE onboarding as described in clause 6.3.2, notably the use of an onboarding indication inside the AN-Params. +- Support of accessing SNPN using credentials from a CH as described in clause 6.3.3.1. + +Non-3GPP access network impact: + +- Ability to advertise (e.g. via ANQP) the SNPNs with which 5G connectivity is supported and related parameters as described in clause 6.3.3.1. +- Support for UE onboarding as described in clause 6.3.2, notably the advertisement (e.g. via ANQP) of an Onboarding enabled indication. + +TNGF impact: + +- Ability to select and to connect to the 5GC network of an SNPN. +- Ability to select and to connect to the 5GC network of an SNPN and convey the "selected NID" to the AMF, in addition to the "Selected PLMN identity". + +NOTE: It is up to RAN WG3 to decide how NGAP is extended i.e. which IE is used for forwarding the selected NID. + +## 6.4 Solution #4: Support of onboarding over untrusted non-3GPP access in SNPN + +### 6.4.1 Introduction + +**Editor's note:** This clause lists the key issue(s) addressed by this solution, and briefly the main principles of the solution. + +This solution aims at addressing key Issue #2 about support of Non-3GPP access for SNPN. In particular, this solution mainly focuses on how to support functionalities defined in R17 eNPN such as onboarding and remote provisioning + +over untrusted non-3GPP access. For UE accessing SNPN using credentials owned by the SNPN, Solution #2 specified in clause 6.2 can be applied. + +This solution can be applied to following scenarios: + +- access to PVS is restricted inside the ON-SNPN and the PVS is not accessible from the public internet directly over the "untrusted non-3GPP access network". +- UE accesses to SNPN via indirect non-3GPP access or direct non-3GPP access for Onboarding. + +## 6.4.2 Functional Description + +**Editor's note:** This clause further details the solution principles and any assumptions made. + +Before the UE registers to an SNPN over untrusted non-3GPP access for Onboarding, it shall select a N3IWF in the SNPN which supports Onboarding. Additionally, the SNPN shall support the Default Credentials Server belonging to a group identified by GINs. + +**Editor's note:** How the UE can select non-3GPP access network that supports access to the N3IWF in the SNPN which supports Onboarding is FFS. + +Therefore, clause 6.3.6.2a of TS 23.501 [3] can be applied with following clarifications and additions: + +- The configured N3IWF FQDN may consist of GIN that identifying a group the DCS belongs to. +- The FQDN constructed by the UE includes GIN that identifies a group the DCS belongs to, indicating the query is for SNPN Onboarding and performing a DNS query for the resulting FQDN. The example of N3IWF FQDN consisting of GIN is shown below: + +n3iwf.5gc.GIN999123456789ABCDE.pub.3gppnetwork.org + +- Alternatively, the FQDN constructed by the UE includes SNPN ID identifying the SNPN where the N3IWF locates and includes an Onboarding prefix, indicating the query is for SNPN Onboarding and performing a DNS query for the resulting FQDN. The UE may use the SNPN ID in the pre-configured ON-SNPN selection information to construct N3IWF FQDN. The example of N3IWF FQDN consisting of SNPN ID and Onboarding prefix is shown below: + +onboarding1.n3iwf.5gc.snpnid999123456789ABCDE.pub.3gppnetwork.org + +- After UE selects a N3IWF that supports Onboarding, it shall include an Onboarding indication in the AN parameters included in the EAP-Res/5G-NAS message which are sent to N3IWF during registration procedure as specified in clause 4.12.2.2 in TS 23.502 [4]. The selected N3IWF shall select an AMF that supports Onboarding based on the Onboarding indication included in the AN parameters. + +**Editor's note:** Whether GIN needs to be in the FQDN for N3IWF that supports onboarding is FFS. + +**Editor's note:** Which authority will respond to the DNS query for FQDN that contains GIN and support onboarding is FFS. + +## 6.4.3 Procedures + +**Editor's note:** This clause describes procedures and information flows for the solution. + +## 6.4.4 Impacts on services, entities, and interfaces + +**Editor's note:** This clause lists impacts to services, entities, and interfaces. + +UE impact: + +- Ability to construct an FQDN consist of GINs used for selecting a preferred SNPN that supports onboarding. +- Ability to include Onboarding indication in the AN parameter sent to the N3IWF during registration procedure. + +N3IWF impact: + +- Ability to select an AMF that supports Onboarding based on the Onboarding indication included in the AN parameters. + +## 6.5 Solution #5: Support of Credentials Holder scenarios over untrusted non-3GPP access in SNPN + +### 6.5.1 Introduction + +**Editor's note:** This clause lists the key issue(s) addressed by this solution, and briefly the main principles of the solution. + +This solution aims at addressing key Issue #2 about support of Non-3GPP access for SNPN. In particular, this solution mainly focuses on how to support functionalities defined in R17 eNPN such as accessing SNPN using credentials owned by Credentials Holder separate from the SNPN over untrusted non-3GPP access. For UE accessing SNPN using credentials owned by the SNPN, Solution #2 specified in clause 6.2 can be applied. + +### 6.5.2 Functional Description + +**Editor's note:** This clause further details the solution principles and any assumptions made. + +When UE accesses to a SNPN using credentials owned by Credentials Holder separate from the SNPN, if the UE is configured with GINs, it can select a N3IWF in the SNPN where UE accesses by using credentials owned by the Credentials Holder belonging to a group identified by GINs. + +**Editor's note:** It is FFS how GIN can help the UE select N3IWF of the serving SNPN it needs to receive service from. + +Therefore, clause 6.3.6.2a of TS 23.501 [3] can be applied with following clarifications and additions: + +- The UE is configured with a GIN that identifies a group the CH belongs to. +- The FQDN constructed by the UE consists of GIN that identifies a group the CH belongs to and the Visited Country FQDN, indicating the query is for SNPN and performing a DNS query for the resulting FQDN. + +The example of N3IWF FQDN consisting of GIN is shown below: + +n3iwf.5gc.GIN999123456789ABCDE..pub.3gppnetwork.org + +**Editor's note:** Which authority will resolve the DNS query for N3IWF FQDN using GIN is FFS. + +### 6.5.3 Procedures + +**Editor's note:** This clause describes procedures and information flows for the solution. + +### 6.5.4 Impacts on services, entities, and interfaces + +**Editor's note:** This clause lists impacts to services, entities, and interfaces. + +UE impact: + +- Ability to construct an FQDN consisting of GINs used for selecting a preferred SNPN that supports connecting with Credentials Holder. + +SNPN operator and/or GSMA: + +- Use SNPN FQDN consisting of GINs. + +## 6.6 Solution #6: Access to SNPN services via wireline access network + +### 6.6.1 Introduction + +This solution addresses KI#2. + +The solution defines how the 5G-RG, FN-RG, and devices behind the RG (UE or N5GC devices behind an FN-RG or 5G-RG) can access SNPN services via a wireline access network. It is based on clause 4.2.1 of TS 23.316 [8], where the SNPN is implicitly selected by wired physical connectivity between 5G-RG or FN-RG and W-AGF. The only additional requirement is that the NID is included as part of the registration procedure for wireline access system. + +### 6.6.2 Functional Description + +To access SNPN services via a wireline access network, the RG follows the similar procedures used for accessing a PLMN via a wireline access network defined in clause 4.2.1 of TS 23.316 [8]. The procedure is as follows: + +- SNPN is implicitly selected by wired physical connectivity. +- The 5G-RG, the W-AGF acting on behalf of the FN-RG and the W-AGF acting on behalf of the N5GC device shall consider both the PLMN ID and the SNPN Network Identifier (NID) configuration to access SNPN via the wireline access network. +- The 5G-RG that supports 5G connectivity to the SNPN initiates the registration procedure via a W-5GAN as specified in clause 7.2.1.1 of TS 23.316 [8] with the addition of SNPN NID. For example, the NAI format for a SUPI containing a GCI shall take the following form: + +"@5gc.nid.mnc.mcc.3gppnetwork.org" + +- The FN-RG that supports 5G connectivity to the SNPN initiates the registration procedure via a W-5GAN as specified in clause 7.2.1.3 of TS 23.316 [8] with the addition of SNPN NID. For example, the NAI format for a SUPI containing a GCI shall take the following form: + +"@5gc.nid.mnc.mcc.3gppnetwork.org" + +- The N5GC device behind RG (5G-RG or FN-RG) that supports 5G connectivity to the SNPN initiates the registration procedure via a W-5GAN as specified in clause 4.10a of TS 23.316 [8] with the addition of SNPN NID. + +### 6.6.3 Impacts on services, entities, and interfaces + +5G-RG impact: + +- Ability to formulate the SUCI that includes the SUPI type as "IMSI" and the home network domain which will include the SNPN identifier (NID) and the PLMN ID to access an SNPN network. + +W-AGF impact in the case of an FN-RG: + +- Ability to formulate the SUCI with NAI that includes the SNPN identifier (NID) and the PLMN ID in the realm portion of NAI to access an SNPN network. + +## 6.7 Solution #7: High level flow for localized service support + +### 6.7.1 Introduction + +This solution provides a high level and overall flow to enable localized service, and covers key issues KI#3/#4/#5/#6. + +## 6.7.2 Functional Description + +The steps shown in the Figure 6.7.3-1 describe a sequence of events among the involved entities. Such sequence is assumed to be applicable for enabling localized service in a typical scenario. The order of the steps and the occurrences of each step are not necessarily restricted. + +This solution is assumed to be an umbrella solution without further details on how each steps are implemented. + +## 6.7.3 Procedures + +![Sequence diagram showing high level procedures for providing access to local service between UE, Home Network, Hosting Network, and Service Provider.](fc0735d325f0ebd9214171975c68a888_img.jpg) + +``` +sequenceDiagram + participant UE + participant Home Network + participant Hosting Network + participant Service Provider + + Note right of Home Network: H1. Service agreements + Note right of Home Network: H2. Network configuration + Note right of Hosting Network: H2. Network configuration + Note left of UE: H3. End user is prompted with localized service and seek info to access localized service + Note right of UE: H4. Provide UE with information needed to discover/access hosting network and the localized service + Note left of UE: H5. UE discovers and selects the hosting network and the localized service + Note right of UE: H6. UE connects to hosting network + Note right of UE: H7. UE accesses the localized service, and optionally home network services + Note left of UE: H8. UE returns from hosting network + Note right of Home Network: H9. Charge the use of localized service + Note right of UE: H10. Roll back previous setup +``` + +The diagram illustrates a sequence of interactions between four entities: UE, Home Network, Hosting Network, and Service Provider. The sequence of steps is as follows: + +- H1. Service agreements**: An interaction between Home Network, Hosting Network, and Service Provider. +- H2. Network configuration**: Two separate interactions, one between Home Network and Hosting Network, and another between Hosting Network and Service Provider. +- H3. End user is prompted with localized service and seek info to access localized service**: An interaction between UE and Home Network. +- H4. Provide UE with information needed to discover/access hosting network and the localized service**: An interaction between UE and Service Provider. +- H5. UE discovers and selects the hosting network and the localized service**: An interaction between UE and Home Network. +- H6. UE connects to hosting network**: An interaction between UE and Service Provider. +- H7. UE accesses the localized service, and optionally home network services**: An interaction between UE and Service Provider. +- H8. UE returns from hosting network**: An interaction between UE and Home Network. +- H9. Charge the use of localized service**: An interaction between Home Network and Service Provider. +- H10. Roll back previous setup**: An interaction between UE and Service Provider. + +Sequence diagram showing high level procedures for providing access to local service between UE, Home Network, Hosting Network, and Service Provider. + +Figure 6.7.3-1: High level procedures for providing access to local service + +- H1. For a hosting network to provide access to localized service, the service provider of the localized service needs to establish localized service agreement with the operator of a hosting network. + +The service provider, according to clause 6.41.2.2 of TS 22.261 [2], can be network operators or 3rd party application providers. The services offered from service providers can be localized, and accessed via the hosting network based on the agreement between the different entities. + +A service agreement with UE's home network operator is needed to enable, e.g.: + +- UE to receive and use configuration provided by a 3rd party service provider to discover and access a hosting network and localized services. +- Charging for the use of localized service. +- The interworking scenarios described in Annex G, clause G.1 of TS 22.261 [2]. +- Service/session continuity between home network and hosting network. + +NOTE 1: The service level agreements established between different entities are work assumptions for SA WG2. + +- H2. The hosting network is configured based on the service agreements with localized service provider for the localized service, e.g. QoS, number of end users, time, location, network slicing, etc. + +The configuration of home network can include, e.g. whether a subscriber of the home network is authorized to use localized service, whether home network services can be accessed via hosting network, etc. + +NOTE 2: The configuration of hosting network based on agreement with localized service provider for localized service is out of SA WG2 study scope. Whether there is a gap that needs to be addressed in 3GPP is up to SA WG5. + +- H3. End user/UE is prompted with localized service (e.g. via ticket of an event, commercial etc), and starts to look for methods how to access the localized service. This could trigger activities on the application layer (e.g. login a web page, scan a QR code etc) and further triggers demand/request from the UE to obtain information related localized services. + +NOTE 3: The application layer activities are outside of 3GPP scope. + +- H4. The service provider / hosting network / home network can co-ordinately deliver to the UE information related to localized service(s). This step can also involve the serving network of the UE if UE is not currently served by home network. The information related to localized service(s) provided to UE in this step can also be unsolicited. In this case, step H3 can happen after, or during this step. +- H5. Based on the received information related to localized service(s), the end user/UE decides to accept and starts the process to discover/select the hosting network when the conditions of the localized service are about to be met (e.g. event time is approaching, end user enters the physical location etc). +- H6. UE connects to the hosting network, possibly with the authorization from home network, and prepares to access the localized service (e.g. User Plane setup, QoS negotiation, etc ). +- H7. UE temporarily stays in the hosting network to obtain the desired localized service and optionally home network services that are available via the hosting network. +- H8. When the temporary access to hosting network for localized service is about to be terminated due to for example event is over, end user has left the area, agreed quota is exhausted, etc, the UE returns from the hosting network. +- H9. Hosting network and/or the service provider collect and provide charging information to UEs' home network operator, depends on the localized service agreement. + +NOTE 4: Charging aspects is to be coordinated with SA WG5. + +- H10. When the localized service agreement is terminated, each entity shown in the figure may need to roll back the previous setup, in order to for example maintain the privacy of an end user against hosting network, prevent a UE to re-access hosting network, release network resources etc. The operation of roll back depends how the localized service is agreed between entities, e.g. if it is a time limited or a geographic limited service, whether it is an one-time service for a single event, etc. + +## 6.7.4 Impacts on services, entities, and interfaces + +Impacts are expected to be described in other solutions. + +NOTE: Security aspects has dependences on SA WG3 work. + +# 6.8 Solution #8: Reuse existing mechanisms for Control Plane Load Control, Congestion and Overload Control + +## 6.8.1 Introduction + +This solution addresses the scenario when UEs after having utilized localized services in a hosting network return to their home network. Due to the nature of localized services, this may involve large number of UEs in the same location at the same time. Large number of UEs that simultaneously attempt to re-register with their home network can cause a significant increase in signalling load, both in the Access Network (AN) and in the Core Network (CN). The proposed solution is to reuse existing mechanisms for Control Plane Load Control, Congestion and Overload Control, to mitigate signalling overload when large number of UEs return to their home network. + +## 6.8.2 Functional Description + +The solution assumes that the UEs have temporarily selected and registered with a hosting network for utilizing localized service, and that the UEs at some point leave the hosting network and return to their home network. The home network in this case can be a PLMN (HPLMN or VPLMN) or an SNPN. + +The mechanism for Control Plane Load Control is a comparatively slow mechanism. It does not adapt quickly to changes of signalling load. The purpose of the mechanism is to distribute the load in relation to the relative capacity of the involved Network Functions. The load distribution is based on Weight Factors in AMFs. + +AMF Control of Overload involves activation of NAS level congestion control, which is based on providing UEs with back-off time values. The UEs use the back-off time values to decide when to initiate NAS signalling. By providing different back-off time values to different UEs, the UE-initiated NAS-signalling is expected to be distributed over time, thereby reducing the peak signalling load. NAS level congestion control is described in clause 5.19.7 of TS 23.501 [3]. + +## 6.8.3 Procedures + +Control Plane Load Control, Congestion and Overload Control, are described in: + +- Clause 5.19 of TS 23.501 [3]. +- Clause 6.3 of TS 29.500 [11]: Load Control. +- Clause 6.4 of TS 29.500 [11]: Overload Control. + +## 6.8.4 Impacts on services, entities, and interfaces + +None. + +## 6.9 Solution #9: Prevention of overload build up at home network using AMF based congestion control when local service is over + +### 6.9.1 Introduction + +The solution addresses the KI#6: Support for returning to the home network, by controlling the build-up of load due to the large-scale migration of multiple UEs from the local hosting network to the home network when the local hosting network decides to end its services. + +The UEs that are registered to the local hosting network are deregistered in a staggered manner and completed before local hosting network goes out of service. The UEs are forced to enter into Network selection mode to choose the home network. In this manner the number of UE's triggering simultaneous de-registration (and consequently then registering back to its home) are in the range of manageable capacity by the home network without causing congestion or overload. + +This is achieved using either one of the two mechanisms + +- Usage of Network availability timers. +- Specific Cause code to trigger the controlled deregistration. + +### 6.9.2 High-level Description + +The solution addresses KI#6 and the following principles are used: + +- When a UE registers to the local hosting network, the AMF of the local hosting network, based on the valid duration of the local hosting services, will start a "Network/service availability timer" for the UE. The timer will have a random value and is based on the time at which the UE registers to the local hosting network and the duration for which such local hosting service will be available. +- There will be 2 separate timers for each UE started at the time of Registration - one to be applicable if the UE is in CM-Idle State when the timer expires and the other one if the UE is in CM-Connected State when the timer expires. The timer value for the CM-Connected State will be larger than the one for CM-Idle State. +- The "Network/service availability timer" will be restarted every time UE initiates Registration to the 5G Network. +- The "Network/service availability timer" for UE-Idle State will be applicable if the UE is in CM-Idle state at the expiry of this timer. +- The "Network/service availability timer" for UE-Connected State will be applicable if the UE is in CM-Connected state at the expiry of this timer. +- The "Network/service availability timer" is used to trigger the de-registration of UE from the local hosting network, before the local hosting services becomes unavailable. +- The timer values are chosen such that the de-registration procedures from the local hosting network are timed in a staggered manner and completed before the local hosting services terminates and the number of UE's triggered to initiate simultaneous de-registration (and consequently then registration back to its home network) are in the range of manageable capacity by the home network without causing overload build up at the home network +- The "Network/service availability timer" to be used in CM-Idle State could be send to the UE, during the Registration procedure to the local hosting network, in Registration accept message. +- Sending of "Network/service availability timer" is optional and based on configuration at the AMF. +- At the expiry of "Network/service availability timer"- Idle / Connected at AMF, RRC state of the UE will be checked, and appropriate actions will be taken based on the UE state (Idle or Connected) at that instant. +- When the "Network/service availability timer" for UE expires at the AMF and AMF is not configured to send the "Network/service availability timer" to the UE, AMF will initiate De-registration procedure for the UE with a specific cause code, that indicates the local hosting services are going to be unavailable. + +- When the "Network/service availability timer" for UE expires at the AMF, and AMF is configured to send the "Network/service availability timer" to the UE, AMF will initiate implicit De-registration procedure for the UE without any signalling. This is applicable only when the UE is in CM Idle State as the "Network/service availability timer" for CM-Connected State is never sent to the UE. +- If the UE becomes CM-Idle after the expiry of "Network/service availability timer" for CM-Idle State, but before the expiry of "Network/service availability timer" for CM-Connected State, then the AMF will immediately initiate De-registration procedure for the UE with a specific cause code, that indicates the local hosting services are going to be unavailable. +- When UE is provided with "Network/service availability timer" as part of the Registration Accept message, UE will move itself to RM-DEREGISTERED State without any signalling with the 5G Network, at the expiry of this timer. +- When the UE is de-registered from the local hosting services either due to the expiry of "Network/service availability timer" or due to the AMF initiated De-registration procedure for the UE, with a specific cause code, that indicates the local hosting services are going to be unavailable: + - a. The UE may put the hosting network in a temporary forbidden list or temporary unavailable list, so that it does not try to re-register to the same hosting network again after this timer expiry. + - b. UE would change the Network Selection mode to Automatic if it had connected to the hosting network through Manual selection mode and select network based on PLMN selection procedure as defined in clause 4.4 of TS 23.122 [6]. + - c. UE will initiate Registration to the Home Network as defined in clause 4.2.2.2.2 of TS 23.502 [4]. + +## 6.9.3 Procedures + +### 6.9.3.1 UE in CM Idle-State and AMF configured to send "Network/service availability timer" + +![Sequence diagram illustrating the procedure for UE in CM Idle-State and AMF configured to send 'Network/service availability timer'. The diagram shows interactions between UE, RAN, AMF, and UDM/AUSF within a Local hosting network. The process starts with OAM configuring the active network period, followed by registration, authentication, and subsequent timer expiration handling.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Local hosting network as Local hosting network + Note right of Local hosting network: OAM configures the active network period + Note right of Local hosting network: [RAN, AMF, UDM/AUSF] + UE->>RAN: 1. Registration request + RAN->>AMF: + AMF->>UDM/AUSF: + UDM/AUSF-->>AMF: + AMF-->>RAN: + RAN-->>UE: 2. Registration accept (Network/service availability timer) + Note right of AMF: 3. AMF maintains connected & Idle mode timers + Note right of UE: 4. UE enters into IDLE mode + Note left of UE: 5b. IDLE timer expires. + Note right of AMF: 5a. IDLE timer expires. Implicit Deregistration of the UE + Note left of UE: 6. Delete hosting network information and change state to deregistered + Note left of UE: 7. Move the local hosting network to the list of "temporarily forbidden SNPNS" or move the CAG identifiers of local hosting network out of the "CAG Information list" of PNI-NPN + Note left of UE: 8. Change network selection mode to "Automatic" PLMN selection. UE tries Home network selection & registration + +``` + +Sequence diagram illustrating the procedure for UE in CM Idle-State and AMF configured to send 'Network/service availability timer'. The diagram shows interactions between UE, RAN, AMF, and UDM/AUSF within a Local hosting network. The process starts with OAM configuring the active network period, followed by registration, authentication, and subsequent timer expiration handling. + +Figure 6.9.3.1-1: UE in CM-Idle State and AMF configured to send "Network/service availability timer" + +1. UE initiate registration with the local hosting network. +2. AMF assigns an appropriate "service availability timer" considering the service available timer (as configured by the OAM) and ensuring that all the UEs does not trigger de-registration at the same time. Thus, ensuring the UE also does not cause signalling overload at the home network when the UE connects back. AMF includes the "Network/service availability timer" in the Registration accept message as it is configured to send this timer in Registration accept message. + +As an example, one of the methods is illustrated below to show how the "Network/service availability timer" is derived by AMF + +- a. Network/service availability timer = (Time at which the Hosting Network ends service) – (Time of UE registration) + x where x is chosen a random value to avoid all UEs accessing the Home Network at the same time. +- 3. AMF starts the "Network/service availability timer" for both CM-Idle and CM-Connected States. + - 4. UE initiates RRC release procedure before the expiration of the "Network/service availability timer" for CM-Idle State. UE enters into CM-Idle State. + - 5. "Network/service availability timer" for CM-Idle State expires at AMF and UE. AMF initiates Implicit De-registration of the UE without any additional Signalling. + - 6. UE moves to RM-DEREGISTERED STATE. + - 7. UE moves hosting network identity to the list of "temporarily forbidden SNPNs" or temporary unavailable list, if the local hosting network is SNPN, or move the CAG Identifiers of local hosting network out of "CAG Information list", if the local hosting network is a PNI-NPN. + - 8. UE would change the Network Selection mode to Automatic PLMN selection if it had connected to the hosting network through Manual mode and select network based on PLMN selection procedure as defined in clause 4.4 of TS 23.122 [6]. UE will initiate Registration to the Home / Serving Network as defined in clause 4.2.2.2.2 of TS 23.502 [4]. Since the de-registration from the hosting network and Registration to the Home/Serving Network happens in a staggered manner, the Home/Serving Network does not get overloaded. + +### 6.9.3.2 UE in CM-Idle State and AMF not configured to send Network/service availability timer + +![Sequence diagram showing UE registration and deregistration in a Local hosting network when the AMF is not configured with a service availability timer.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Local_hosting_network as Local hosting network + participant RAN + participant AMF + participant UDM_AUSF as UDM/AUSF + + Note right of RAN: OAM configures the active network periodod + UE->>RAN: 1. Registration request + RAN->>AMF: + AMF->>UDM_AUSF: + UDM_AUSF-->>AMF: + AMF-->>RAN: + RAN-->>UE: 2. Registration accept + Note right of AMF: 3. AMF maintains connected & Idle mode timers + Note left of RAN: 4. UE enters into IDLE mode + Note right of AMF: 5. IDLE timer expires and UE is in IDLE state. Initiate Deregistration of the UE + AMF-->>RAN: 6. CN/RAN Paging + RAN-->>UE: 7. Service request + UE->>AMF: 8. Deregistration request (cause: 5GS service going out of service) + AMF-->>RAN: + RAN-->>UE: 9. Deregistration complete + Note left of UE: 10. Move the local hosting network to the list of "temporarily forbidden SNPNS" or move the CAG identifiers of local hosting network out of the "CAG Information list" of PNI-NPN + Note left of UE: 11. Change network selection mode to "Automatic" PLMN selection. UE tries Home network selection & registration + +``` + +The sequence diagram illustrates the interaction between a User Equipment (UE) and a Local hosting network (containing RAN, AMF, and UDM/AUSF). The process begins with the OAM configuring the active network periodod. The UE sends a registration request (1) to the RAN, which is processed by the AMF and UDM/AUSF through authentication and authorization. The AMF maintains connected and idle mode timers (3). The UE enters into IDLE mode (4). When the IDLE timer expires, the AMF initiates deregistration (5). The AMF sends CN/RAN paging (6), and the UE responds with a service request (7). The AMF then sends a deregistration request (8) to the UE, and the UE responds with a deregistration complete (9). The UE then moves the local hosting network to the list of "temporarily forbidden SNPNS" or moves the CAG identifiers out of the "CAG Information list" of PNI-NPN (10). Finally, the UE changes network selection mode to "Automatic" PLMN selection and tries home network selection and registration (11). + +Sequence diagram showing UE registration and deregistration in a Local hosting network when the AMF is not configured with a service availability timer. + +**Figure 6.9.3.2-1: UE in CM-Idle State and AMF not configured to send "Network/service availability timer"** + +- UE initiates registration with the local hosting network. +- AMF assigns an appropriate "service availability timer" considering the service available timer (as configured by the OAM) and ensuring that all the UEs does not trigger de-registration at the same time. Thus, ensuring the UE also does not cause signalling overload at the home network when the UE connects back. AMF does not include + +the "Network/service availability timer" in the Registration accept message as it is not configured to send this timer in Registration accept message. + +3. AMF starts the "Network/service availability timer" for both CM-Idle and CM-Connected States. +4. UE initiates RRC release procedure before the expiration of the "Network/service availability timer" for CM-Idle State. UE enters the CM-Idle State. +5. "Network/service availability timer" for CM-Idle State expires at AMF. AMF initiates explicit De-registration procedure with the UE. +6. AMF sends Paging Request to the UE. +7. UE initiates Service Request to come to CM-Connected Mode. +8. AMF sends De-registration Request to the UE with cause code (e.g.: 5G Services going out of Service) indicating that local services are going to be terminated soon. +9. UE sends De-registration complete to the AMF. +10. UE moves hosting network identity to the list of "temporarily forbidden SNPNs" or temporary unavailable list, if the local hosting network is SNPN, or move the CAG Identifiers of local hosting network out of "CAG Information list", if the local hosting network is a PNI-NPN. +11. UE would change the Network Selection mode to Automatic if it had connected to the hosting network through Manual mode and select network based on PLMN selection procedure as defined in clause 4.4 of TS 23.122 [6]. UE will initiate Registration to the Home / Serving Network as defined in clause 4.2.2.2.2 of TS 23.502 [4]. Since the de-registration from the hosting network and Registration to the Home/Serving Network happens in a staggered manner, the Home/Serving Network does not get overloaded. + +### 6.9.3.2 UE in CM-Connected State and AMF not configured to send Network/service availability timer + +![Sequence diagram showing UE registration and subsequent deregistration from a local hosting network when the AMF is not configured with a network/service availability timer.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LocalHostingNetwork as Local hosting network + Note right of LocalHostingNetwork: OAM configures the active network period + UE->>LocalHostingNetwork: 1. Registration request + LocalHostingNetwork->>UE: Authentication & Authorization + LocalHostingNetwork->>UE: 2. Registration accept + Note right of LocalHostingNetwork: 3. AMF maintains connected & Idle mode timers + Note right of LocalHostingNetwork: 4. IDLE mode timer expires. The UE is in Connected mode + Note right of LocalHostingNetwork: 5. connected mode timer expires. The UE is in Connected mode + LocalHostingNetwork->>UE: 6. Deregistration request (cause: 5GS service going out of service) + UE->>LocalHostingNetwork: 7. Deregistration complete + Note left of UE: 8. Move the local hosting network to the list of "temporarily forbidden SNPNS" or move the CAG identifiers of local hosting network out of the "CAG Information list" of PNI-NPN + Note left of UE: 9. Change network selection mode to "Automatic" PLMN selection. UE tries Home network selection & registration + +``` + +The sequence diagram illustrates the interaction between a User Equipment (UE) and a Local hosting network (containing RAN, AMF, and UDM/AUSF). The process begins with the UE sending a registration request (1) to the RAN, which is forwarded to the AMF. The AMF initiates authentication and authorization with the UDM/AUSF. Upon successful authentication, the AMF sends a registration accept (2) back to the UE via the RAN. The AMF then maintains connected and idle mode timers (3). When the idle mode timer expires (4), the UE remains in connected mode. Subsequently, when the connected mode timer expires (5), the UE is still in connected mode. The AMF then sends a deregistration request (6) to the UE with the cause "5GS service going out of service". The UE responds with a deregistration complete (7) message. Following this, the UE performs internal actions: moving the local hosting network to a list of temporarily forbidden SNPNS or removing its CAG identifiers from the CAG information list of PNI-NPN (8), and changing network selection mode to "Automatic" PLMN selection to try home network selection and registration (9). + +Sequence diagram showing UE registration and subsequent deregistration from a local hosting network when the AMF is not configured with a network/service availability timer. + +**Figure 6.9.3.2-1: UE in CM-Connected state and AMF not configured to send "Network / Service Availability" timer** + +1. UE initiates registration with the local hosting network. + +2. AMF assigns an appropriate "service availability timer" considering the service available timer (as configured by the OAM) and ensuring that all the UEs does not trigger de-registration at the same time. Thus, ensuring the UE also does not cause signalling overload at the home network when the UE connects back. AMF does not include the "Network/service availability timer" in the Registration accept message as it is not configured to send this timer in Registration accept message. +3. AMF starts the "Network/service availability timer" for both CM-Idle and CM-Connected States. +4. "Network/service availability timer" for CM-Idle State expires at AMF. The UE is in CM-CONNECTED state, so the AMF does not take any action. +5. "Network/service availability timer" for CM-Connected State expires at AMF. AMF initiates explicit De-registration procedure with the UE. +6. AMF sends De-registration Request to the UE with cause code (e.g.: 5G Services going out of Service) indicating that local services are going to be terminated soon. +7. UE sends De-registration complete to the AMF. +8. UE moves hosting network identity to the list of "temporarily forbidden SNPNs" or temporary unavailable list, if the local hosting network is SNPN, or move the CAG Identifiers of local hosting network out of "CAG Information list", if the local hosting network is a PNI-NPN. +9. UE would change the Network Selection mode to Automatic if it had connected to the hosting network through Manual mode and select network based on PLMN selection procedure as defined in clause 4.4 of TS 23.122 [6]. UE will initiate Registration to the Home / Serving Network as defined in clause 4.2.2.2.2 of TS 23.502 [4]. Since the de-registration from the hosting network and Registration to the Home/Serving Network happens in a staggered manner, the Home/Serving Network does not get overloaded. + +The same call flow is applicable for a UE in CM-Connected State, even if the AMF is configured to send "Network/service availability timer". + +## 6.9.4 Impacts on existing services and interfaces + +The solution has the following impacts: + +UE: + +- Handling of new cause codes, service availability timer and related implementation. + +AMF: + +- Handling of new timer for all the UEs accessing local services. Support for new cause code in network initiated UE deregistration request. + +## 6.10 Solution #10: Solution for discovery and selection of NPN hosting network and localized services + +### 6.10.1 Introduction + +This solution addresses the Key issue#4: Enabling UE to discover, select and access NPN as hosting network and receive localized services. + +It also provides a solution for Key Issue #6: Support for returning to home network + +It provides a different approach for discovery and selection for PNI-NPN case and for SNPN case. + +## 6.10.2 Functional Description + +### 6.10.2.1 UE selection of SNPN hosting network for localized services + +SNPN selection for localized services is performed by a UE that supports access to localized services in SNPNs and that has been configured to access localized services in SNPNs. We will call this UE an "*SNPN-localized services-enabled UE*". + +An "*SNPN-localized services-enabled UE*" can be configured with a specific prioritized list of SNPNs for localized services. The UE can be pre-configured or dynamically configured by the subscribed SNPN or Home PLMN (e.g. using the SoR procedure as defined in Annex C of TS 23.122 [6]). The dynamically configured mechanism by the subscribed SNPN or Home PLMN (e.g. using the SoR procedure as defined in Annex C of TS 23.122 [6]) is not used to steer the UE from one hosting network to another hosting network. If the UE which is registered to a hosting network received the updated prioritized list of SNPNs for localized services, then the UE only uses the updated prioritized list of SNPNs for localized services to perform SNPN hosting network selection for localized services after the UE leaves the current hosting network for localized services. + +NOTE: It assumes that how does the subscribed SNPN or Home PLMN construct the prioritized list of SNPNs for localized services is addressed by other solutions. + +The reason to have a separate list for localised services instead of a common one like the one is defined in clause 5.30.2.4 of TS 23.501 [3] is that there may be a case where the home SNPN or HPLMN or the UE is present in the same areas where localised services are provided and based on the existing selection procedures the UE will always prefer the home SNPN or HPLMN in this case. + +The prioritized list of SNPNs for localized services is stored in the context of a given subscription in the UE. If the UE has multiple subscriptions, then the UE may have one prioritized list of SNPNs for localized services for each subscription. + +Each entry in the prioritized list of SNPNs for localized services contains: + +1. An identification of the SNPN and the localized service to access. This identification can be done in a few different ways: + - Identification Mode 1: SNPN ID (PLMN ID + NID) or a Group ID for Network Selection (GIN) + - This mode if identification assumes that the localized service is enabled in the whole SNPN with the SNPN ID or in every cell where GIN is broadcasted. + - Note that an SNPN operator could potentially use multiple SNPN IDs in different areas. + - Identification Mode 2: SNPN ID or GIN, plus an additional Subnetwork ID. + - The subnetwork ID is used to assign a specific area where the localized service is provided, and it is broadcasted in SIB together with SNPN ID or GIN. + - The subnetwork ID may be a new ID or may be CAG (effectively extending CAG use to SNPN). + +NOTE: Whether to reuse CAG for subnetwork in SNPN or define a new ID is to be evaluated during evaluation/conclusions. + +- One or more localized services may be assigned the same subnetwork ID if they are offered in the same area. +2. Validity information: + - Validity time period. + - Additional location information (TAI list or geographical information). + +The UE uses this prioritized list and the validity information to perform discovery and selection and to leave the SNPN as described in the Procedures clause 6.10.3. + +### 6.10.2.2 UE selection of PNI-NPN hosting network for localized services + +For PNI-NPN case, Rel-17 automatic selection defined in TS 23.501 [3] applies with one additional enhancement: + +- Entries in the Allowed CAG list of the UE can additionally contain the following validity information: + - Validity time period (from/to date and time). + - Location (e.g. list of tracking areas where the CAG list is valid). + +NOTE: Location information for Allowed CAG list only needed if PNI-NPN as hosting network can be a subset of a CAG. + +In the case of PNI-NPN (CAG) selection for access to localized services, the UE only considers an entry in the Allowed CAG list valid if and while all conditions for that entry are met. + +For the case of time period, a UE will only attempt registration on a CAG cell if e.g. the current time lies within the time period of the related condition. + +### 6.10.2.3 Enabling access to SNPN Hosting Network for a localized service + +The principles of this solution for enabling access to the SNPN Hosting Network for localized services are as follows: + +- The hosting network maps a localized service to a subnetwork ID. Multiple localized services may be mapped to the same subnetwork ID if they are offered in the same service area. +- The Credentials Holder is aware of the subnetwork ID for the localized service in the SNPN hosting network. + +NOTE: The interaction between Hosting Network and Credentials Holder is not covered in this solution, but the inclusion of subnetwork ID may be included in other solutions in the TR. + +- The UE is configured by the credentials holder as described in clause 6.10.2.1. +- The RAN, via OAM, is configured to broadcast one or more subnetwork IDs. +- The UE performs Network selection as in clause 6.10.2.1 using the subnetwork ID if configured. The UE initiates UE registration procedure. +- The AMF receives from the UDM (at the Credentials Holder) the subscription information for UE access to a localized service in the Hosting Network. The AMF may receive also the subnetwork ID included in the NR access restriction information. +- If the AMF does not receive any subnetwork ID, i.e. the access for the localized service is enabled in the whole SNPN, regular registration procedure is executed. +- If the AMF receives a subnetwork ID, the AMF checks whether the UE is located in the subnetwork ID. This may be done: + - a. Via configuration in AMF. + - b. Via receiving from NG-RAN the subnetwork ID(s) in the cell the UE is camping on. +- The AMF accepts the registration request if the UE is in the subnetwork ID received from the UDM. +- The AMF rejects the registration request if the UE is outside the subnetwork ID received from the UDM. +- The AMF provides to the NG-RAN the access restriction to the subscribed subnetwork ID. The NG-RAN uses this information for handover decision. The NG-RAN does not initiate handover towards a cell that would be outside the subnetwork ID. +- If the UE moves outside the subnetwork ID the UE does not attempt to initiate any procedure towards the hosting network. The UE may initiate network selection as in clause 6.10.2.1. + +## 6.10.3 Procedures + +### 6.10.3.1 Automatic discovery and selection of SNPNS for access to localized services + +The UE performs the following steps: + +- Step 1. UE is configured with a "prioritized list of SNPNS for localized services" and at least one entry in the validity information is met (e.g. current time is within the time period). This configuration allows the UE to start operating in "SNPN Localized services mode" when the right validity conditions are met. The UE may continue at this point be in either SNPN access mode or PLMN access mode until the conditions of validity information. + - Step 2. When some validity information is met (e.g. time validity) in step 1, the UE scans for SNPNS in the background. +- NOTE: Details of how often to scan, etc. are out of scope of SA WG2. +- Step 3. If the UE finds at least one available and allowable SNPN which meets the validity conditions, then the UE switches to a new network selection mode "SNPN Localized services mode" and selects an available SNPN from the prioritized list of SNPNS for localized services. + - Step 4. The UE performs Initial registration in the SNPN and presents the SUPI of the currently active subscription (subscription that contains the prioritized list of SNPNS for localized services which the UE used to select the SNPN). + +### 6.10.3.2 Leaving SNPN Localized services mode + +The UE performs the following steps: + +- Step 1. If the validity information in the prioritized list of SNPNS for localized services for the currently registered SNPN are no longer met, then the UE disables "SNPN Localized services mode" and returns to the mode in which the UE was before activating SNPN Localized services mode (i.e. return to SNPN access mode or PLMN access mode). If the validity conditions that are no longer met is the Validity time period, this could occur to many devices at the same time and a large number of UEs may return to their HPLMN at the same time if measures are not taken. Therefore, two possible solutions to address this issue (key issue #6) can be taken: + - Option 1: The CH or HPLMN (depending on case) configures UEs with slightly different end time to the validity time period. + - Option 2: The UE applies a random delay before initiating step 2. +- Step 2. The UE performs SNPN selection or PLMN selection as defined in TS 23.122 [6] (depending on the mode). + +### 6.10.3.3 Discovery and selection of PNI-NPNs with CAG for access to localized services + +The UE performs the following steps: + +- Step 1. UE is configured with Allowed CAG list, and some of the entries in the Allowed CAG list are associated with validity information for localized services. +- Step 2. When the validity information is met in the Allowed CAG list, the UE starts to additionally consider the CAG cell during cell reselection and also consider the associated PLMN of the Allowed CAG list is valid if it was excluded during the previous network selection procedure due to CAG validation. +- Step 3. The UE selects the CAG cell and potentially a new PLMN. +- Step 4. The UE accesses the network via the CAG cell, and potentially a new registration if there is a PLMN change. + +### 6.10.3.4 Leaving the PNI-NPNs with CAG for access to localized services + +If the validity information of the Allowed CAG list is no longer met, UE re-evaluates the CAG related configuration and triggers cell reselection and/or network selection procedure. + +### 6.10.3.5 Manual discovery and selection of SNPNS for access to localized services + +The UE displays to the user a list of available SNPNS, marking first which SNPNS, if any, are in the "prioritized list of SNPNS for localized services" and at least one entry in the validity information is met. The user can select an SNPN for access to localized services. + +### 6.10.3.6 Enabling access to localized services: Registration procedure + +Figure 6.10.3.6-1 shows the call flow for the UE registration into an SNPN hosting network for localized service(s) access. + +![Sequence diagram of the registration procedure for access to localized service(s) in an SNPN Hosting Network. The diagram shows interactions between UE, NG-RAN, AMF, Other NFs, and UDM. The process starts with initial configuration (0.a) and UE selection (0.b), followed by a registration request (1) and AMF selection (2). The NG-RAN then sends a registration request with subnetwork ID(s) (3). The main registration procedure (steps 4-13) follows, including a step 14 interaction with the UDM for localized service information. An AMF check (14*) is performed, followed by steps 15-19. The registration accept (21) is sent to the UE, and the final steps (22-25) complete the procedure.](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant Other NFs + participant UDM + + Note over UE, UDM: 0.a. Credentials Holder aware of subnetwork ID if it applies, UE configured with Prioritized list of SNPNS for Localized Services (clause 6.10.2.1) + Note over UE, NG-RAN: 0.b. UE selects SNPN (6.10.3.1 or 6.10.3.5) + UE->>NG-RAN: 1. Registration request + NG-RAN->>AMF: 2. AMF selection + NG-RAN->>AMF: 3. Registration Request / Subnetwork ID(s) + Note over UE, UDM: Steps 4-13 Registration Procedure TS 23.502 clause 4.2.2.2.2 + AMF->>UDM: 14. Step 14 TS 23.502 clause 4.2.2.2.2 with UDM including Localized service information + subnetwork ID if applies + Note over AMF: 14*. AMF checks if UE in subnetwork ID + Note over UE, Other NFs: Steps 15-19 Registration Procedure TS 23.502 clause 4.2.2.2.2 + AMF->>UE: 21. Registration accept + Note over UE, AMF: 21. Registration Accept / Access Restriction: Subnetwork ID(s) + Note over UE, UDM: Steps 22-25 Registration Procedure TS 23.502 clause 4.2.2.2.2 + +``` + +Sequence diagram of the registration procedure for access to localized service(s) in an SNPN Hosting Network. The diagram shows interactions between UE, NG-RAN, AMF, Other NFs, and UDM. The process starts with initial configuration (0.a) and UE selection (0.b), followed by a registration request (1) and AMF selection (2). The NG-RAN then sends a registration request with subnetwork ID(s) (3). The main registration procedure (steps 4-13) follows, including a step 14 interaction with the UDM for localized service information. An AMF check (14\*) is performed, followed by steps 15-19. The registration accept (21) is sent to the UE, and the final steps (22-25) complete the procedure. + +**Figure 6.10.3.6-1: Registration procedure for access to localized service(s) in SNPN Hosting Network** + +0.a. It is assumed the Credentials Holder is aware of which subnetwork ID in an SNPN hosting network applies to a specific (set of) localized service(s). It is assumed the UE has been configured for selection of SNPN for localized services as in 6.10.3.1, and that NG-RAN is configured to broadcast subnetwork ID in cells that belong to a subnetwork. + +0.b. The UE performs selection of SNPN for localized services as in 6.10.3.1. + +The UE and SNPN perform registration procedure as in TS 23.502 [4] clause 4.2.2.2.2 with the following additions: + +- In step 3, the NG-RAN may include the (list of) subnetwork ID(s) that are available in the cell the UE is camping on, +- In step 14, the UDM provides the AMF with subscription information for access to localized service(s) the UE is authorized at the SNPN Hosting network. The UDM may also provide a subnetwork ID in the NR access restriction information, to indicate that the UE only is allowed access in the subnetwork ID. + +- Before step 15, if the AMF received a subnetwork ID from UDM, the AMF checks if the UE is camping in the subnetwork ID. If not, the AMF sends Registration Reject to UE with appropriate cause code, and terminates the procedure. If yes, the AMF proceeds with completing Registration Procedure. +- In step 21, the AMF includes the access restriction information including subnetwork ID. The NG-RAN uses this information to avoid handover to a cell not belonging to the subnetwork ID. + +## 6.10.4 Impacts on services, entities, and interfaces + +UE: + +- New configuration to incorporate localized services validity information and in the case of SNPN prioritization. +- New configuration to incorporate localized services validity information with Allowed CAG list. +- New SNPN for localized services selection mode. +- New triggers to enter/leave SNPN for localized selection mode. + +RAN: + +- In one of the options for SNPN for localized service identification, new Subnetwork ID broadcasted in SIB. + +UDM/SOR-AF: + +- Support prioritized list of SNPNs for localized service. + +RAN/AMF/UDM: + +- For PNI-NPN case, support validity information associated with Allowed CAG list for UE, and the access control function based on the validity information. +- For SNPN, support of subnetwork ID information and enforcing UE only accesses via a cell in the subnetwork ID. + +## 6.11 Solution #11: Access to localized service by using LADN and roaming architecture + +### 6.11.1 Introduction + +This solution addresses Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services and Key Issue #5: Enabling access to localized services via a specific hosting network. The basic principle of this solution is reusing existing roaming architecture and LADN mechanism. + +In this solution, it is assumed that a UE's home network is a PLMN and hosting network is a PNI-NPN. + +### 6.11.2 Functional Description + +#### 6.11.2.1 Architecture + +The following figure 6.11.2.1-1 and figure 6.11.2.1-2 depict the proposed architecture, which are reusing 5G System roaming architecture in the case of local breakout and home routed scenario. When a UE registers to the selected hosting network and receives localized services provided by the hosting network, architecture in figure 6.11.2.1-1 is used. If the UE also need to get services from the home network, the UE may establish home routed PDU session as shown in figure 6.11.2.1-2. Whether the UE receives a specific service from the hosting network or home network is determined based on subscription of the UE by establishing a local breakout session, or a home routed session. The UE just follows the existing PDU Session Establishment procedure based on URSP rule provided by the home network. + +NOTE: The following architecture figures do not apply when PNI-NPN is the HPLMN. + +![Figure 6.11.2.1-1: Architecture when a UE uses localized services provided by the hosting network. This diagram shows a UE connected to a (R)AN, which is connected to an AMF. The AMF is connected to an NSSF, SMF, and UPF. The SMF is connected to a vPCF, which is connected to an AF. The AF is connected to a DN. The UPF is connected to a DN. The AMF is also connected to the NSSF via N22, N58, N12, N8, and N10 interfaces. The NSSF is connected to the AUSF, UDM, and hPCF. The AUSF is connected to the UDM via N13. The UDM is connected to the hPCF via N59. The DN is connected to the UPF via N6 and N9 interfaces. The diagram is divided into two sections: Hosting Network (PNI-NPN) and Home Network (PLMN).](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +Figure 6.11.2.1-1: Architecture when a UE uses localized services provided by the hosting network. This diagram shows a UE connected to a (R)AN, which is connected to an AMF. The AMF is connected to an NSSF, SMF, and UPF. The SMF is connected to a vPCF, which is connected to an AF. The AF is connected to a DN. The UPF is connected to a DN. The AMF is also connected to the NSSF via N22, N58, N12, N8, and N10 interfaces. The NSSF is connected to the AUSF, UDM, and hPCF. The AUSF is connected to the UDM via N13. The UDM is connected to the hPCF via N59. The DN is connected to the UPF via N6 and N9 interfaces. The diagram is divided into two sections: Hosting Network (PNI-NPN) and Home Network (PLMN). + +Figure 6.11.2.1-1: Architecture when a UE uses localized services provided by the hosting network + +![Figure 6.11.2.1-2: Architecture when a UE uses services provided by the home network. This diagram shows a UE connected to a (R)AN, which is connected to an AMF. The AMF is connected to a V-NSSF, V-PCF, V-SMF, and UPF. The V-SMF is connected to an H-SMF, which is connected to an H-PCF, which is connected to an AF. The H-SMF is also connected to the UDM. The UDM is connected to the AUSF, NSSAAF, and H-NSSF. The AUSF is connected to the NSSAAF via N59. The H-NSSF is connected to the AMF via N31. The AMF is also connected to the V-NSSF via N22, N58, N12, N8, and N15 interfaces. The V-NSSF is connected to the AMF via N22. The V-PCF is connected to the AMF via N15. The V-SMF is connected to the AMF via N11. The UPF is connected to the AMF via N2. The (R)AN is connected to the AMF via N1. The UE is connected to the (R)AN via N1. The DN is connected to the UPF via N6 and N9 interfaces. The diagram is divided into two sections: Hosting Network (PNI-NPN) and Home Network (PLMN).](69e5f1993021af230d08c08aac97d9df_img.jpg) + +Figure 6.11.2.1-2: Architecture when a UE uses services provided by the home network. This diagram shows a UE connected to a (R)AN, which is connected to an AMF. The AMF is connected to a V-NSSF, V-PCF, V-SMF, and UPF. The V-SMF is connected to an H-SMF, which is connected to an H-PCF, which is connected to an AF. The H-SMF is also connected to the UDM. The UDM is connected to the AUSF, NSSAAF, and H-NSSF. The AUSF is connected to the NSSAAF via N59. The H-NSSF is connected to the AMF via N31. The AMF is also connected to the V-NSSF via N22, N58, N12, N8, and N15 interfaces. The V-NSSF is connected to the AMF via N22. The V-PCF is connected to the AMF via N15. The V-SMF is connected to the AMF via N11. The UPF is connected to the AMF via N2. The (R)AN is connected to the AMF via N1. The UE is connected to the (R)AN via N1. The DN is connected to the UPF via N6 and N9 interfaces. The diagram is divided into two sections: Hosting Network (PNI-NPN) and Home Network (PLMN). + +Figure 6.11.2.1-2: Architecture when a UE uses services provided by the home network + +## 6.11.2.2 Hosting network discovery and selection + +It is assumed that there is service level agreement between the home network and hosting network and based on the agreement the AMF in the home network is configured with Localized Service Information. The Localized Service Information contains following information: + +- Localized Service Name. +- Validity condition: + - Time and Spatial validity. +- Hosting network information: + - Precedence. + - Hosting network ID (PLMN ID) and RAT type (e.g. NR, E-UTRA). + +- LADN DNN. +- Allowed CAG information. + +NOTE 1: If the Localized service is provided in the home network (i.e. PNI-NPN is in the home network), hosting network information can be omitted. + +When a UE is registered in home network, the UE may request Localized Service Information to the AMF by sending NAS message (e.g. Registration). If subscription of the UE allows to use the Localized service, the AMF provides localized service information to the UE. The UE stores the received Localized Service Information until time validity condition is fulfilled. The spatial validity condition in the Localized Service Information can be represented by geographical area. The exact service area information of hosting network is provided to the UE as a part of LADN information during the registration to the hosting network. + +NOTE 2: In the case of roaming scenario, the AMF in the serving PLMN provides Localized Service Information to the UE. + +NOTE 3: The AMF can provide Localized Service Information to the UE without UE request if subscription of the UE allows to use the Localized service. For example, the AMF may provide Localized Service Information when a UE enters an area where the Localized service is available. + +Instead of providing Allowed CAG information to the UE in the Localized Service Information, the hosting network may provide Allowed CAG list to the UE by using existing procedure. However, in the case of roaming scenario, the serving PLMN cannot provision Allowed CAG list of hosting network to the inbound roamers as current specification only allows to update CAG information of the serving PLMN in the case of roaming. If the UE receives Allowed CAG information via Localized Service Information, the UE shall use the Allowed CAG information only when the UE access the hosting network for the Localized service. + +### 6.11.2.3 Registration to hosting network and access to Localized services + +Based on received Localized Service Information, the UE selects hosting network and registers to the network. When a UE registers to the hosting network and has the subscription to a specific LADN DNN for local service or a wild card DNN, the AMF provides LADN information (i.e. LADN DNN and LADN service area) to the UE according to the existing LADN mechanism. The UE uses the LADN information to access localized services provided by the hosting network. + +NOTE 1: When hosting network operator configures LADN information in the AMF, the operator can provide associated validity time of LADN DNN so that the AMF provides LADN information when the validity time is satisfied. + +NOTE 2: If the Localized service is provided in the home network (i.e. PNI-NPN is in the home network), the UE skips hosting network selection. If validity condition in Localized Service Information is fulfilled, the UE can requests LADN information to the AMF according to the existing LADN mechanism. + +## 6.11.3 Procedures + +### 6.11.3.1 Requesting Localized service information + +![Sequence diagram showing the request and response for localized service information between a UE and a Home Network AMF.](1b3c088f23921d4eeb45ffc05586e59b_img.jpg) + +``` +sequenceDiagram + participant UE + participant HN as Home Network AMF + Note left of UE: Requesting Localized Service Information + UE->>HN: 1. NAS Request message (Request of Localized Service Information) + HN-->>UE: 2. NAS Response message (Localized Service Information) +``` + +The diagram illustrates a sequence of two messages between a User Equipment (UE) and a Home Network AMF. The UE sends a 'NAS Request message (Request of Localized Service Information)' to the AMF, and the AMF responds with a 'NAS Response message (Localized Service Information)'. + +Sequence diagram showing the request and response for localized service information between a UE and a Home Network AMF. + +Figure 6.11.3.1-1: Requesting Localized service information + +The UE may request Localized Service Information to the AMF by sending NAS message (e.g. Registration request). The UE may indicate specific service the UE wants to receive by including Localized service name. The AMF provides Localized Service Information to the UE as described in clause 6.11.2.1. + +NOTE: How the UE gets Localized service name is out of 3GPP scope. The UE can get Localized service name via webpage, installing application, etc. + +### 6.11.3.2 Connection to hosting network and access to Localized services + +![Sequence diagram showing the registration process in the hosting network and access to Localized services. The diagram involves six entities: UE, Hosting Network AMF, Hosting Network V-PCF, Home Network AUSF, Home Network UDM, and Hosting Network SMF. The sequence of messages is: 1. Registration request (Registration type = local services) from UE to AMF; 2. Authentication from AMF to AUSF; 3. Nudm_UECM_Registration (Registering for local services) from AUSF to UDM; 4. Registration accept (LADN information) from AMF to UE; 5a. PDU Session Establishment Request (LADN DNN) from UE to SMF; 5b. PDU Session Establishment Accept from SMF to UE.](4346261cc730a1eb683f35e4ce9deacf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF as Hosting Network AMF + participant VPCF as Hosting Network V-PCF + participant AUSF as Home Network AUSF + participant UDM as Home Network UDM + participant SMF as Hosting Network SMF + + Note left of UE: 1. Registration request (Registration type = local services) + UE->>AMF: 1. Registration request (Registration type = local services) + Note left of AMF: 2. Authentication + AMF->>AUSF: 2. Authentication + Note left of AUSF: 3. Nudm_UECM_Registration (Registering for local services) + AUSF->>UDM: 3. Nudm_UECM_Registration (Registering for local services) + Note left of AMF: 4. Registration accept (LADN information) + AMF->>UE: 4. Registration accept (LADN information) + Note left of UE: 5a. PDU Session Establishment Request (LADN DNN) + UE->>SMF: 5a. PDU Session Establishment Request (LADN DNN) + Note left of SMF: 5b. PDU Session Establishment Accept + SMF->>UE: 5b. PDU Session Establishment Accept + +``` + +Sequence diagram showing the registration process in the hosting network and access to Localized services. The diagram involves six entities: UE, Hosting Network AMF, Hosting Network V-PCF, Home Network AUSF, Home Network UDM, and Hosting Network SMF. The sequence of messages is: 1. Registration request (Registration type = local services) from UE to AMF; 2. Authentication from AMF to AUSF; 3. Nudm\_UECM\_Registration (Registering for local services) from AUSF to UDM; 4. Registration accept (LADN information) from AMF to UE; 5a. PDU Session Establishment Request (LADN DNN) from UE to SMF; 5b. PDU Session Establishment Accept from SMF to UE. + +**Figure 6.11.3.2-1: Registration in the hosting network and access to Localized services** + +If the UE wants to receive Localized service, the UE requests Localized service information as specified in clause 6.11.3.1 and selects hosting network based on the received Localized Service Information. If selected hosting network is available, the UE performs registration with the selected hosting network. The Registration procedure in TS 23.502 [4] is used with following modifications: + +- When the UE performs initial Registration procedure, Registration type indicates that the UE is accessing the network for localized services. Based on this information the AMF determine to provide LADN information to the UE. +- The AMF indicates to the UDM that the UE is registering for localized services. The UDM use the indication whether to accept UE registration. + +After Registration is completed, the UE establishes PDU Session to the LADN DNN. + +### 6.11.4 Impacts on services, entities, and interfaces + +UE: + +- The UE indicates that the UE is accessing the network for localized services during the Registration procedure. +- The UE requests and receives Localized Service Information from the AMF and selects hosting network based on the received Localized Service Information. + +AMF: + +- The AMF indicates to the UDM that the UE is registering for localized services. +- The AMF provides Localized Service Information to the UE. + +UDM: + +- The UDM determines whether to accept registration taking into account the indication that UE is registering for localized services. + +## 6.12 Solution #12: Discovering services offered by SNPN/PNI-NPN while camping in a serving network + +### 6.12.1 Introduction + +The solution addresses key issue #4 "Enabling UE to discover, select and access NPN as hosting network and receive localized services" and proposes how UE becomes aware of hosting network for localized services. + +UE may not actively search for available networks such as hosting network for localized services when UE is camped in home network. + +This solution proposes that current serving network (PLMN or SNPN) may assist UE in discovering hosting network for localized services in specific conditions, such as when serving network determines that UE moves into area where localized services are available. For current serving network to be able to assist UE in discovery of hosting network for localized services some level of co-operation between current serving network and hosting network is needed. + +Once UE becomes aware of the hosting network with help of serving network, there can be several different alternatives for how the UE may connect to hosting network depending on the configuration of UE such as availability of credentials and configuration of hosting network. + +### 6.12.2 Functional Description + +#### 6.12.2.1 PNI-NPN as hosting network + +When PNI-NPN is made available via a PLMN, the UE has subscription for the PLMN in order to access PNI-NPN. For subscribers of other PLMNs this means there needs to be proper roaming/service agreements in place. + +In PNI-NPN a Closed Access Groups is used to apply access control for a group of subscribers i.e. to prevent UE(s) that are not allowed to access the NPN via the associated CAG cell(s). The CAG cell(s) are inherently associated with location or spatial validity condition(s) and hence additional spatial validity condition is not required to be provided with Allowed CAG list. + +Hosting network specific aspects can be addressed as additional considerations, if needed, for NPN as a network slice of a PLMN described in TS 23.501 [3] Annex D.2. Network Slice Selection Policy (NSSP) could be associated with hosting network specific time validation criteria. + +PNI-NPN slice may be only available in the TA(s) that span over the event location, i.e. S-NSSAI is only provided to the UE as allowed S-NSSAI in this TA by the AMF. UE may consider TAI list, Allowed NSSAI, Allowed CAG list as communicated by AMF in Registration Accept or UE Configuration Update to discover a specific hosting network configuration. + +UE can be pre-configured with S-NSSAI(s) that are used for localized services, i.e. PLMN can reserve few values for this purpose and pre-provision the UEs with these S-NSSAI(s). S-NSSAI/DNN for a particular hosting network can be provisioned in the PLMN via operator specific means or by the service provider via NEF using Nnef\_ParameterProvision service with NEF providing versatile external to internal parameter mapping capabilities related to, e.g. AF expressed location or service description and NEF translates these input data to special DNN/S-NSSAI and TA(s). + +The UE may become aware about hosting network related information via OTT. There can be UE implementation specific means how to map service specific information retrieved via OTT to hosting network information, such as S-NSSAI/DNN. The UE may then perform registration update to network with new slice information. + +#### 6.12.2.2 SNPN as hosting network + +This solution addresses KI#4 and the following principles are used: + +- UE is assumed to have only single radio capability. +- The home network UDM is assumed to have UE's subscribe localized services and corresponding hosting network information. + +- The home network UDM invokes Namf\_EventExposure\_Notify to receive UE location information event notification in order to be aware of the availability of hosting network. When the hosting network is available, the UDM can trigger SoR procedure to update information on available hosting network(s). +- The home network UDM may send location information to the AMF, enabling the AMF to assign the Registration Area according to the received location information. +- When the UE is camping in the home network, the home network AMF determines the location of the UE, for instance, based on AMF determining change of Tracking Area (TA), e.g. Tracking Area Code (TAC) or cell id, in Registration Request (Mobility Registration Update) received from UE as specified in clause 4.2.2.2 of TS 23.502 [4]. +- The AMF is aware of availability of hosting network(s) that corresponds to (allowed) areas (such as tracking area) which represent the current UE location as indicated in the Mobility Registration Update sent by the UE. The AMF may assign Registration Area to the UE in such a way that the UE performs Mobility Registration Update when UE moves to into the Tracking Area (TA) where the hosting network is present. The AMF may be aware of the availability and other information of the hosting network(s) in the registration area by local configuration or based on the location information received from UDM, or by service agreement with hosting network. +- Based on availability of the hosting network(s) in the location of the UE and considering other information such as subscription information, UE capability, roaming and local configuration/policies or other operator specific criteria, AMF may decide to assist UE in discovering hosting network(s). +- If the serving network decides to assist UE in discovering hosting network(s), the AMF may: + - the AMF may include information on available hosting network(s) as part of Registration Accept message sent to UE. + - the UDM may as part of registration procedure initiate Steering of Roaming (SoR), as specified in Annex C of TS 23.122 [6], to update information of available hosting network(s) to UE. + - the AMF may initiate UE Configuration Update procedure, as specified in clause 4.2.4.2 of TS 23.502 [4], to update information on available hosting network(s). + +**Editor's note:** It is FFS whether the existing information element in the SoR is sufficient to carry hosting network related information or what enhancements are needed. + +- The AMF may invoke the Namf\_EventExposure\_Notify to provide mobility related event to (authorized) SMF(s) that have subscribed for the events by invoking Namf\_EventExposure\_Subscribe as specified in clause 5.3.4.4 of TS 23.501 [3] and clause 4.15.4.2 of TS 23.502 [4]. Mobility event notification may include information of available hosting network(s) or could be mapped (e.g. PRA) to such information in SMF. SMF may use the information of available hosting network(s) received from AMF to initiate PDU Session Modification to inform UE, e.g. using PCO, about specific details of hosting network configuration such as URL that UE may use to access localized services captive portal for UE onboarding and remote provisioning purposes. SMF may be locally configured with configuration information for hosting network(s). +- UE could use the localized services captive portal, e.g. for UE onboarding to hosting network (to obtain credentials) while still connected in home network (or current serving network) and using existing PDU session. +- Information of available hosting network(s) may include: + - indication of availability of one or more hosting network(s); + - list of (PLMN ID, SNPN ID), GINs (as defined in clause 5.30 of TS 23.501 [3]) or localized services specific identifier of available hosting network(s); + - N3IWF address and necessary credentials to access hosting network(s); + - Specific details of hosting network such as URL or other data for UE to be able to connect to the localized services captive portal page. +- The serving network may also broadcast GIN that is localized services specific or localized services specific broadcast indicator to indicate localized services availability with which the hosting network has an agreement with. If GIN is used, the serving network also broadcasts GIN when requested by the UE. In the case of localized + +services, a new indicator is needed in the broadcast that a GIN can be used to select a hosting network. GIN, the localized services identifier and other information such as HRNN (Human readable network name) may also be displayed on the UE allowing for manual selection by the user. The GIN that is hosting network specific or the hosting network specific indicator broadcasted by the serving network could be cell specific. + +NOTE 1: In Rel-17 maximum number of GINs is 24 (see TS 38.331 [14]). + +NOTE 2: Broadcast details will be determined by RAN WG2. + +- Based on information of available hosting network(s) UE receives from current serving network (e.g. initiated by AMF or triggered by GIN broadcasted by the serving network), UE may: + - access hosting network using credentials owned by a Credentials Holder separate from the hosting network. Credentials Holder can be the home network (e.g. the PLMN or the SNPN). Hosting network identifier information may include indication that access using credentials from a Credentials Holder is supported or indication that hosting network allows registration attempts from UEs that are not explicitly configured in list of preferred SNPNs/GINs to select the hosting network. This follows the principles defined in Rel-17 for automatic network selection (TS 23.501 [3] clause 5.30.2.4.2) and manual network selection (clause 5.30.2.4.3 of TS 23.501 [3]). UE authorization for hosting network services is checked by the serving network. + - access hosting network by using UE onboarding and remote provisioning as specified in clause 5.30.2.10 of TS 23.501 [3] with onboarding SUCI/SUPI and other configuration information provisioned using UE Configuration Update (or SoR) procedure while connected to home network. + - access from the serving network to hosting network via NWu interface and N3IWF located in the hosting network using onboarding SUCI/SUPI in registration procedure. Onboarding SUCI/SUPI, N3IWF address, default credentials to establish connectivity via NWu to access hosting network and other data can be configured using UE Configuration Update procedure to the UE. The access credentials can be UE specific or usable by all UEs of a certain serving network. In this case hosting network acts as the overlay network, serving network acts as the underlay network. UE may use PDU session in (overlay) hosting network that is restricted to access only to the localized services portal page where the UE can be provisioned with service and network related data. + - access hosting network that offers free services for users in the area, e.g. using sponsored connectivity. + - access hosting network services for subscribers of the serving network (e.g. the PLMN or the SNPN) with which they have agreement. In this case, authorization to offer hosting network services is checked by the serving network. + +## 6.12.3 Procedures + +### 6.12.3.1 UE discovery, selection and access for hosting network using Registration procedure + +![Sequence diagram illustrating UE discovery, selection and access for hosting network using Registration procedure. The diagram shows interactions between UE, Serving Network, and Hosting Network. Steps include: 0. Initial Registration (from Hosting Network to Serving Network); 1. Registration Request (Mobility Update) (from UE to Serving Network); 2. AMF configured to be aware of localized service availability in area (TA, cell) (internal to Serving Network); 3. Registration Accept (from Serving Network to UE); 4. PDU Session Establishment or Update (from UE to Serving Network); 5. UE connects to the localized services portal (dashed arrow from UE to Hosting Network); 6. UE connects to hosting network directly or using Nwu connectivity (dashed arrow from UE to Hosting Network).](df1966d80c74bc127f159a48f38b13ee_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN as Serving Network + participant HN as Hosting Network + Note right of HN: 0. Initial Registration + UE->>SN: 1. Registration Request (Mobility Update) + Note right of SN: 2. AMF configured to be aware of localized service availability in area (TA, cell) + SN-->>UE: 3. Registration Accept + UE-->>SN: 4. PDU Session Establishment or Update + UE-->>HN: 5. UE connects to the localized services portal + UE-->>HN: 6. UE connects to hosting network directly or using Nwu connectivity + +``` + +Sequence diagram illustrating UE discovery, selection and access for hosting network using Registration procedure. The diagram shows interactions between UE, Serving Network, and Hosting Network. Steps include: 0. Initial Registration (from Hosting Network to Serving Network); 1. Registration Request (Mobility Update) (from UE to Serving Network); 2. AMF configured to be aware of localized service availability in area (TA, cell) (internal to Serving Network); 3. Registration Accept (from Serving Network to UE); 4. PDU Session Establishment or Update (from UE to Serving Network); 5. UE connects to the localized services portal (dashed arrow from UE to Hosting Network); 6. UE connects to hosting network directly or using Nwu connectivity (dashed arrow from UE to Hosting Network). + +**Figure 6.12.3.1-1: UE discovery, selection and access for hosting network** + +0. During Initial registration of the UE, the home network (UDM) may provide to serving network (AMF) as part subscription information with Nudm\_SDM\_Get service operation response, an indication whether the AMF is allowed to provide available hosting network information to UE to discover hosting networks (e.g. when the AMF belongs to home network) or an indication to the AMF to send the list of available hosting networks to the UDM first for authorization and then send the authorized list of hosting networks received from the UDM to the UE. +1. Registration Request (Mobility Update) update triggered due to TAC changes. +2. Serving Network detects that the UE moved to area (TA, cell id) where localized service is offered. The serving network's AMF may trigger Nudm\_SDM\_Get service operation to the UDM including a list of hosting network, if UDM had provided an indication at step 0 to send the list of hosting network information for authorization before sending them to the UE. The UDM then responds back with the list of hosting network that the AMF is authorized to provide to the UE. +3. In TAs where localized services is available, the serving network includes hosting network information as part of Registration procedure. The serving network may also include necessary information regarding hosting network (SNPN ID, GIN, DNN, S-NSSAI) for it to obtain limited connectivity to hosting network. +4. Alternative to step 3, the hosting network information can be provided by the SMF in a PCO during PDU session establishment or update. The AMF may provide an indication in Nsmf\_PDUSession\_CreateSMContext or Nsmf\_PDUSession\_UpdateSMContext to the SMF to provide hosting network related information to the UE. +5. UE may initiate PDU Session using DNN, S-NSSAI information received step 3 or 4 that the network redirects to the localized services portal (PCF policies installed using PDR/FAR rules to redirect to localized services portal). + +NOTE 1: UE can use internet PDU Session, reactivate UP and simply use the link provided by the network e.g. in the PCO to reach the hosting network. + +6. Depending on information, subscription and authorization obtained for hosting network, UE may connect to hosting network using NWu connectivity or select hosting network directly. + +NOTE 2: If UE should use hosting network as the underlay network later on and the PLMN as overlay, it might be necessary to provide N3IWF address of the PLMN as well. + +### 6.12.3.2 UE discovery, selection and access for hosting network using UE Configuration Update procedure + +![Sequence diagram illustrating the UE discovery, selection and access for hosting network using UE Configuration Update procedure. The diagram shows four steps: 0. Initial Registration (between Serving Network and Hosting Network), 1. Registration Procedure (Mobility Update) (between UE and Serving Network), 2. AMF configured to be aware of localized service availability in area (TA, cell) (internal to Serving Network), and 3. UE Configuration Update (between Serving Network and UE). Step 4 is a dashed line indicating UE connects to hosting network directly or using Nwu connectivity (between UE and Hosting Network).](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN as Serving Network + participant HN as Hosting Network + Note right of HN: 0. Initial Registration + UE->>SN: 1. Registration Procedure (Mobility Update) + Note right of SN: 2. AMF configured to be aware of localized service availability in area (TA, cell) + SN->>UE: 3. UE Configuration Update + UE-->>HN: 4. UE connects to hosting network directly or using Nwu connectivity + +``` + +Sequence diagram illustrating the UE discovery, selection and access for hosting network using UE Configuration Update procedure. The diagram shows four steps: 0. Initial Registration (between Serving Network and Hosting Network), 1. Registration Procedure (Mobility Update) (between UE and Serving Network), 2. AMF configured to be aware of localized service availability in area (TA, cell) (internal to Serving Network), and 3. UE Configuration Update (between Serving Network and UE). Step 4 is a dashed line indicating UE connects to hosting network directly or using Nwu connectivity (between UE and Hosting Network). + +**Figure 6.12.3.2-1: UE discovery, selection and access for hosting network using UE Configuration Update procedure** + +0. During initial registration of the UE, the home network (UDM) may provide to serving network (AMF) as part subscription information with Nudm\_SDM\_Get service operation response, an indication whether the AMF is allowed to provide available hosting network information to UE to discover hosting networks (e.g. when the AMF belongs to home network) or an indication to the AMF to send the list of available hosting networks to the UDM first for authorization and then send the authorized list of hosting networks received from the UDM to the UE. +1. UE triggers Registration Request (Mobility Update) to TAC change and Registration procedure completes. +2. Serving Network detects that the UE moved to area (TA, cell id) where localized service is offered. The serving network's AMF may trigger Nudm\_SDM\_Get service operation to the UDM including a list of hosting network, if UDM had provided an indication at step 0 to send the list of hosting network information for authorization before sending them to the UE. The UDM then responds back with the list of hosting network that the AMF is authorized to provide to the UE. +3. When localized services are available, the serving network AMF using UE Configuration Update for access and mobility management related parameters may provide UE with information of available hosting network(s) and other information as well as trigger the UE to perform scanning of hosting network(s) and if needed also provide the UE a trigger for the UE to determine whether to it needs to initiate change to SNPN selection mode. Depending on localized service information user has acquired by means out of scope of 3GPP, such as QR code in entrance ticket and information of available hosting network(s) received from serving network, a list of hosting network(s) and localized service information may be available in the UE to seek user consent, e.g. for manual selection. +4. Depending on information, received in step 3 the UE may select and connect to hosting network directly or using NWu. + +NOTE: If UE should use hosting network as the underlay network later on and the PLMN as overlay, it might be necessary to provide N3IWF address of the PLMN as well. + +### 6.12.3.3 UE discovery, selection and access for hosting network using Steering of Roaming procedure + +![Sequence diagram illustrating the UE discovery, selection and access for hosting network using SoR procedure. The diagram shows four lifelines: UE, Serving Network, Home Network, and Hosting Network. The sequence of messages is: 1. Registration Procedure (Mobility Update) from UE to Serving Network; 2. AMF configured to be aware of localized service availability in area (TA, cell) and triggers Update of SoR information (internal message within Serving Network); 3. Steering of Roaming information update from Serving Network to UE; 4. UE connects to hosting network directly (dashed arrow from UE to Hosting Network).](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN as Serving Network + participant HN as Home Network + participant HoN as Hosting Network + Note right of SN: 2. AMF configured to be aware of localized service availability in area (TA, cell) and triggers Update of SoR information + UE->>SN: 1. Registration Procedure (Mobility Update) + SN->>UE: 3. Steering of Roaming information update + UE-->>HoN: 4. UE connects to hosting network directly + +``` + +Sequence diagram illustrating the UE discovery, selection and access for hosting network using SoR procedure. The diagram shows four lifelines: UE, Serving Network, Home Network, and Hosting Network. The sequence of messages is: 1. Registration Procedure (Mobility Update) from UE to Serving Network; 2. AMF configured to be aware of localized service availability in area (TA, cell) and triggers Update of SoR information (internal message within Serving Network); 3. Steering of Roaming information update from Serving Network to UE; 4. UE connects to hosting network directly (dashed arrow from UE to Hosting Network). + +**Figure 6.12.3.3-1: UE discovery, selection and access for hosting network using SoR procedure** + +0. During initial registration of the UE, the home network (UDM) may provide to serving network (AMF) as part subscription information with Nudm\_SDM\_Get service operation response, an indication whether the AMF is allowed to provide available hosting network information to UE to discover hosting networks. Home network (UDM) may in addition provide as part of Nudm\_SDM\_Get service operation response, a new type of SoR Update Indicator for hosting network supporting access to localized services (enhancement to Annex C of TS 23.122 [6]). This allows home network to indicate to the AMF whether it supports and allows AMF triggering SoR for hosting networks that provide access to localized. + 1. Registration Request (Mobility Update) update triggered due to TAC changes. As part of Mobility Registration update, if allowed by the home network in step 0, the AMF may include list of available hosting network(s) to the UE as in clauses 6.12.3.1 or 6.12.3.2. + 2. Serving Network detects that the UE moved to area (TA, cell id) where localized service is offered. Based on SoR Update Indicator for hosting networks supporting access to localized services in UE context in the AMF and list of available hosting network(s), the AMF may include the list of available hosting network(s) as part of Nudm\_SDM\_Get service operation to UDM in home network. Home network (UDM) may determine preferences/priorities between hosting network(s) and subscribed SNPN/VPLMN/HPLMN and initiate SoR procedure to communicate changed preferences in Credentials Holder controlled list(s) to UE. +- NOTE: The H-UDM can be triggered for SoR procedure during Mobility Registration update as per the procedure in Sol#18. +3. Steering of Roaming procedure is used to update information of available hosting network(s) and other information to UE. + 4. Depending on the information, subscription and authorization obtained for home network in SoR, UE may select and connect to hosting network directly. + +### 6.12.4 Impacts on services, entities and interfaces + +UE: + +- support of information of hosting networks in NAS procedures. +- support ability to determine whether to automatically change to access mode used to access hosting network or display hosting network id, the localized services identifier and other information such as HRNN allowing for manual selection of SNPN access mode by the user; taking into account hosting network information UE receives from serving network and/or home network as part of registration procedure, UE Configuration Update procedure or SoR procedure. + +NG-RAN: + +- broadcast GIN(s) that is hosting network specific or hosting network specific broadcast indicator to indicate localized services availability. When GIN that is hosting network specific is broadcasted by the serving network, GIN is broadcasted together with indicator that informs GIN can be used to select a hosting network. + +## AMF: + +- support by local configuration of available of hosting network(s) in UE registration area. +- support assignment of registration area in such a way that the UE performs Mobility Registration Update when the UE moves to an area where hosting network(s) are available. +- provide information of available hosting networks to UE in NAS Registration procedure. +- provide information of available hosting networks and other information to UE in UE Configuration Update procedure. +- support capability to provide indication of UE presence in area of hosting network(s) and the list of hosting network(s) available in the area to UDM for initiation of SoR procedure. +- support capability to provide Onboarding SUCI/SUPI, N3IWF address, default credentials and other data in UE Configuration Update procedure to the UE for UE to be able to establish connectivity via NWu to access hosting network. + +## SMF: + +- may optionally support of ability to provide to UE information of URL and other information to access portal in order to perform remote provisioning to hosting network(s) in PCO when AMF notifies UE entering an area that co-locates with hosting network(s). + +## UDM: + +- provide information of allowed hosting networks, related preferences and other information to UE in SoR procedure. + +## 6.13 Solution #13: Exposure enhancements to support providing access to localized services + +### 6.13.1 Introduction + +This solution aims at address key Issue #3 (Enabling NPN as hosting network for providing access to localized services), Key Issue #4 (Enabling UE to discover, select and access NPN as hosting network and receive localized services) and Key Issue #5 (Enabling access to localized services via a specific hosting network), in particular: + +- How localized service agreements (i.e. a service agreement for a localized service) for a specific occasion (time and location) are automatically established and terminated. +- What is required to enable communication between a network operator deploying a hosting network and a localized services provider: Investigate which type of interaction (e.g. configuration of the hosting network, information reporting) is needed, in such relation to enable the localized services provider for making the best use of the hosting network. +- How and whether the home network, determine the service availability of a hosting network, and interacts with hosting network to authorize home network's subscribers to access home network services via the hosting network, at certain time and location, coverage of the hosting network and services offered by the hosting network. +- Investigate which type of information needs to be exchanged between hosting network and a localized services provider so that a UE can perform discovery, selection and connection of the hosting network and access the localized services provided via the hosting network. +- How to enable UE to access both home network services and localized services via the hosting network, and seamless service continuity for home network services and localized services when UE moves between different + +networks providing the same services. This includes how to configure UE with information enabling the UE to be aware of services that can be accessed via a specific network (e.g. home network or hosting NPN). + +- How home network determines the need to steer or instruct the UE, and how the home network steers or instructs the UE to select a hosting network for obtaining home network services or localized services or select a network for a specific service which is available from both hosting and home network. +- How to mitigate user plane and control plane overload when a high number of UEs return to home network from a temporary hosting network, especially ensure the service continuity for the UEs with single radio capability which are camping in the hosting network, and using hosting network as an underlay network to access the services provided by the home network. + +The main principles of this solution are that: + +- The localized service provider can act as the AF to manage the localized service agreements among Hosting Network operator, localized service provider, and Home Network or Credentials Holder via exposure interface. +- The localized service provider can act as the AF to manage the subscribed localized service information in subscription data within the Home Network or Credentials Holder or Hosting network via network exposure. This can be performed on a demand basis. +- The network selection information for the target Hosting Network is provisioned/signalled to the UE when the UE is registered in the Home Network; the network selection information is used for discovery and selection of the target Hosting Network; Optionally, the network selection information can be signalled to the UE under certain conditions e.g. when UE enters specific area and/or after certain time. +- When the UE registers in the Hosting Network, the Home Network or the Credentials Holder performs primary authentication and authorization for the UE. +- When the UE accesses to the localized service via Hosting Network, the Hosting Network initiates Network Slice-Specific Authentication and Authorization or PDU Session Secondary Authentication and Authorization to authorize the UE access to the localized service. +- When the UE accesses to the localized service via Hosting Network, the Hosting Network uses the time and location allowed for the UE to perform access control to the localized service. +- When the UEs return to Home Network from Hosting Network, the Hosting Network may group the registered UEs based on reported the Nwu status and the availability of the Home Network of the UE. Hosting Network may indicate every registered UE with a random back-off timer value from different range of values corresponding to different groups. UE should wait until the expiry of the back-off timer to initiate the registration and PDU session establishment request attempt to the home network if needed. + +## 6.13.2 Functional Description + +Providing access to localized services refers to the capability to provide access to a hosting network (PNI-NPN or SNPN) and a set of services offered by the hosting network provider, other mobile network operators (PLMN or SNPN) and 3rd party application providers. The services may be localized (i.e. provided at specific/limited area) and may be bounded in time. + +The UE's with or without prior subscription to the hosting network can access to the localized services via hosting network using access credentials from Home Network or Credentials Holder once the UE has subscribed successfully to the localized services of the hosting network. Then this solution is described as below: + +- The localized service provider acting as the application function manages the service agreements among Hosting Network operator, localized service provider, and Home Network or Credentials Holder via network exposure. The service agreements include: + - Availability of each of the localized service (service identification, service parameters [DNN, S-NSSAI, QoS], service authorization methods [NSSAA or PDU Session SAA], service access methods [LBO or HR], time and location); and + - List of Supported Home Networks or Credentials Holders for each localized service; and + - List of Supported Hosting Networks for each localized service. + +- The localized service provider may request the hosting network operator to configure or update its network rule (e.g. at the specific time and location) to provide the localized services. Based on the request from the localized service provider and the agreement between hosting network operator and localized service provider, the hosting network may configure or update its network rules in NFs to provide the localized services. The hosting network operator may respond the localized service provider with the result for providing the localized services. +- The hosting network may advertise the localized services to the UE according to the network rules. +- UE/User can subscribe to the localized service for a specific Hosting Network via out-of-3GPP means, e.g. online store, portal: + - The UE should be a subscriber of the supported Home Network or should have credentials from the supported Credentials Holder in the service agreement; and + - The target Hosting Network should be one in the list of supported Hosting Networks; and + - The localized service provider should know localized service information selected by the UE/User, e.g. subscribed DNN, S-NSSAI, QoS, service authorization method, service access method, time and location, this information selected by the UE/User should be covered by the Availability of the localized service in the service agreement. The localized service provider should also know the information of the UE's subscribed Hosting Network and Home Network or Credentials Holder; and + - The UE/User can obtain the service credentials assigned by the localized service, the service credentials can be used to authenticate and authorize the UE access to the localized service. +- The localized service provider acting as the application function, updates subscription data in the subscribed Home Network or Credentials Holder or Hosting network via network exposure, so the subscription data can contain the localized service information subscribed by a single UE or a group of UEs: + +**Editor's note:** It is FFS how network exposure is used by localized service provider to update the subscription data and what the subscription data for localized service contains. + +- If the UE will access the Hosting Network using credential from Credentials Holder with AAA Server, then the localized service provider updates the subscription data in the subscribed Hosting Network, so the subscription data contains the indication that primary AA by AAA-S is required as well as the subscribed localized service information e.g. subscribed DNN, S-NSSAI, QoS, service authorization method, service access method, time and location. +- If the UE will access the Hosting Network using credential from Credentials Holder with AUSF and UDM, then the localized service provider updates the subscription data in the subscribed Home Network, so the subscription data contains the subscribed Hosting Network information as well as the subscribed localized service information e.g. subscribed DNN, S-NSSAI, QoS, service authorization method, service access method, time and location. +- If the UE will access the Hosting Network using credentials from Home Network, then the localized service provider updates the subscription data in the subscribed Home Network, so the subscription data contains the subscribed Hosting Network information as well as the subscribed localized service information e.g. subscribed DNN, S-NSSAI, QoS, service authorization method, service access method, time and location. +- The Home Network updates UE with the network selection information for the subscribed Hosting Network (e.g. service identification, Hosting Network ID, temporal validity condition, spatial validity condition) when subscribed time starts and/or when UE enters specific area indicated by the subscribed location contained in the subscription data: + - The temporal validity condition is derived from the subscribed time for the localized service, this indicates the time period when the network selection information is valid. + - The spatial validity condition is derived from the subscribed location for the localized service, this indicates the area where the network selection information is valid. +- The Home Network can also provide UE with its N3IWF address to enable UE to access both home network services and localized services via the hosting network: + +- The N3IWF address of home network is used for UE to determine its way to access to hosting network based on its radio-capability.(e.g. access hosting network directly, or access home network via hosting network as an underlay network). +- The UE moves in the subscribed location for the localized service and the temporal validity condition is still valid, and starts discovery and selection of the Hosting Network. +- The UE registers in the Hosting Network with the access credentials and accesses to the localized services using the service credentials. +- The UE is authenticated and authorized by the Home Network or the Credentials Holder. +- The UE can be provisioned with information related with the subscribed localized service (Allowed NSSAI, service authorization method, URSP rules). +- The UE setups the connectivity to the localized service by establishing a PDU Session with the DNN, S-NSSAI associated with the localized service, the Hosting Network can allocate resources for the PDU Session according to the subscribed QoS or service access method. +- With the subscribed service authorization method, the Hosting Network performs the service authorization using the indicated authorization method. +- With the subscribed time and location, the Hosting Network performs access control to the localized service. +- When the UE moves out the subscribed location for the localized service or the temporal validity condition becomes out-dated: + - The UE de-registers from the Hosting Network, the UE may delete the network selection information for the subscribed Hosting Network and information related with the subscribed localized service. + - The Hosting Network de-registers the UE and releases network resources reserved for the UE. + - The localized service provider may delete the localized service information from subscription data in the Home Network or Credentials Holder or Hosting network. + +Figure 6.13.2-1 depicts the scenarios for support of providing access to localized services. + +![Diagram illustrating the support of providing access to localized services via exposure enhancements. The diagram shows four main entities: Service Providers/Operators (top), Hosting Network (PNH-NPN or SNPN) (right), Home Network/Credential Holder (left), and UE (bottom). Arrows indicate the flow of information: 1. Service Providers/Operators to Hosting Network (Service Credentials, Localized service); 2. Service Providers/Operators to Home Network/Credential Holder (Access Credentials); 3. UE to Home Network/Credential Holder (Move); 4. Home Network/Credential Holder to Hosting Network (Access Credentials). The Hosting Network contains an Exposure Framework, CN (Core Network), and AN (Access Network) layers.](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +The diagram illustrates the interaction between four main components for providing access to localized services: + +- Service Providers/Operators** (top): Can be hosting network provider, 3rd party service providers, other network operators. It contains "Service Credentials" and "Localized service". +- Hosting Network (PNH-NPN or SNPN)** (right): Contains an "Exposure Framework", "CN" (Core Network), and "AN" (Access Network) layers. +- Home Network/Credential Holder** (left): Can be PLMN or SNPN or 3rd Party AAA. It contains "Access Credentials". +- UE** (bottom): Indicated by a "Move" arrow. + +Interactions are shown by numbered arrows: + +- Arrow 1: From Service Providers/Operators to Hosting Network (Service Credentials, Localized service). +- Arrow 2: From Service Providers/Operators to Home Network/Credential Holder (Access Credentials). +- Arrow 3: From UE to Home Network/Credential Holder (Move). +- Arrow 4: From Home Network/Credential Holder to Hosting Network (Access Credentials). + +Diagram illustrating the support of providing access to localized services via exposure enhancements. The diagram shows four main entities: Service Providers/Operators (top), Hosting Network (PNH-NPN or SNPN) (right), Home Network/Credential Holder (left), and UE (bottom). Arrows indicate the flow of information: 1. Service Providers/Operators to Hosting Network (Service Credentials, Localized service); 2. Service Providers/Operators to Home Network/Credential Holder (Access Credentials); 3. UE to Home Network/Credential Holder (Move); 4. Home Network/Credential Holder to Hosting Network (Access Credentials). The Hosting Network contains an Exposure Framework, CN (Core Network), and AN (Access Network) layers. + +**Figure 6.13.2-1: Support of providing access to localized services via exposure enhancements** + +- When UE returns to Home Network from the Hosting Network, the AMF of Hosting Network may group the UEs based on the Nwu status and the availability of the Home Network of the UE. Hosting Network indicates the UE with a random back-off timer from different range of values corresponding to different groups to register to Home Network. + +- AMF of hosting network indicates UE the localized service(s) end. One or more localized services ID may be included in this indication. +- Upon receiving the end indication of the localized service(s) from the AMF, UE may: + - determine whether all the target localized services provided by the hosting network end. + - determine its current Nwu interface status for the specific home network. + - detect whether there is a coverage of the specific home network in a good signal condition(e.g. meet the requirement of the signal strength to access to) +- If UE determines all the target localized services provided by the hosting network end, UE reports the Nwu interface status and related home network identity(e.g. PLMN ID) that the Nwu interface connects to. UE reports the availability of the coverage of the home network. +- Based on the reports of the UEs, AMF groups the UE and indicate the UE with a random back-off timer from different range of values corresponding to different groups to register to home network in different groups. + +For every single home network, AMF may group the UEs into four groups: + +- Group1: Nwu interface for home network exists and coverage of the home network exists. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register and establish the PDU session in the home network immediately. +- Group2: Nwu interface for home network does not exist and coverage of the home network exists. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register to the home network immediately. The pre-defined range of back-off timer in Group2 should be longer than which of in Group1. +- Group3: Nwu interface for home network exists and coverage of the home network does not exist. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register and establish the PDU session in the home network when UE detects the availability of the home network. The pre-defined range of back-off timer in Group3 should be longer than which of in Group2. +- Group4: Nwu interface for home network does not exist and coverage of the home network does not exist. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register to home network when UE detects the availability of the home network. The pre-defined range of back-off timer in Group4 should be longer than which of in Group3. + +Figure 6.13.2-2 depicts an example to group the UEs by AMF based on the reports of the UEs. + +![Diagram of Home network A showing UE groups based on Nwu status and network availability.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The diagram illustrates the organization of User Equipment (UE) into groups within 'Home network A'. The network is represented by a large rectangle. Inside, there are two large circles. The left circle is labeled 'Home network is available' and contains two boxes: 'Group1:UE with Nwu' and 'Group2:UE without Nwu'. The right circle is labeled 'Home network is not available' and contains two boxes: 'Group3:UE with Nwu' and 'Group4:UE without Nwu'. + +Diagram of Home network A showing UE groups based on Nwu status and network availability. + +**Figure 6.13.2-2: AMF groups the UEs based on the reports of the Nwu status and the availability of the Home Network of the UE** + +- UE should wait until the expiry of the back-off timer to initiate the registration attempt and PDU session establishment request attempt to the home network if needed. + +### 6.13.3 Procedures + +#### 6.13.3.1 Procedure for enabling hosting network to provide access to localized services + +![Sequence diagram showing the interaction between a Hosting Network and an AF to enable localized services.](077f85b82901283b4657fd2b45fc0294_img.jpg) + +The sequence diagram shows the interaction between a 'Hosting Network' (containing UE, AMF, SMF, PCF, and NEF) and an 'AF (Localized Service Provider)'. The sequence of messages is as follows: + + +- The AF sends a '1. Request to provide localized services' to the NEF. +- The NEF sends a '2. Decision to provide localized service and related network rules' to the SMF. +- The SMF sends a '3. Response to provide localized services' to the AF. +- The SMF sends a '4. Enforce the network rules for localized services' message, which is received by both the AMF and the PCF. +- The AMF sends a '5. Advertise the localized services' message to the UE. + +Sequence diagram showing the interaction between a Hosting Network and an AF to enable localized services. + +**Figure 6.13.3.1-1: Procedure for the interaction between hosting network and localized service provider to enable UE to access the localized services via hosting network** + +The precondition for this procedure is the existence of a SLA between the Hosting network and the provider of localized service to enable the interaction between the AF and the Hosting Network as required. And there should be another precondition for this procedure that UE with target localized service has registered to the hosting AMF and setup a PDU session with the hosting SMF, and the related AM/SM policy association have been established between the hosting AMF/SMF with the hosting PCF. + +- Step 1: AF(localized service provider) may initiate or update the request to the NEF of the hosting network for providing access to localized services with the characteristics of the localized service, which including: + - list of the identification of the localized services; + - validity restriction for each localized service, e.g. the validity of time or location; + - QoS requirements for each localized service. +- Step 2: NEF/PCF of the hosting network determines its network rules for the localized services based on the request in Step1 and the agreement with the localized service provider. The network rules are used to reserve the network resources and meet the QoS requirement with the specific validity restriction for providing access to the localized services. +- Step 3: NEF/PCF of the hosting network responses the result for providing access to localized services to the AF (localized services provider), the result corresponds to the request in the Step1, which including: + - list of the identification of the localized services, which can be provided by the hosting network; + - validity restriction for each localized service provided by the hosting network, e.g. the validity of time or location; + - QoS requirements for each localized service provided by the hosting network. +- Step 4: PCF of hosting network updates the parameters of the AMF and SMF in order to enforce its network rules which are determined in step 3 to provide access to localized services. +- PCF will invoke Npcf\_AMPolicyControl\_UpdateNotify request to AMF as defined in clause 4.16.2.2 of TS 23.502 [4], which includes the list of the identification of the localized services, the modified service area restrictions (e.g. the validity of location), and the modified QoS (such as UE-AMBR, UE-Slice-MBR) parameters to notify AMF the access and mobility related policy for localized services has been updated. +- PCF will invoke Npcf\_SMPolicyControl\_UpdateNotify request to SMF as defined in clause 4.16.5.2 of TS 23.502 [4], which includes the modified QoS (e.g. Authorized MBR, Authorized session-AMBR), the Revalidation time limit, the Time Condition, etc. parameters to notify SMF the PDU session related policy information for localized services has been updated. +- Step 5: hosting network advertise the localized services to the UE according to the network rules (e.g. at the specific time and location). +- When AMF received the modified access and mobility related policy from PCF in step 4, AMF will deploy and store this updated policy information, then provisioning the Service Area Restrictions (e.g. the validity of location), the list of the identification of the localized services (such as DNN and/or S-NSSAIs) to the UE, and provisioning the UE-AMBR, Service Area Restrictions to the NG-RAN. + +### 6.13.3.2 Procedure for home network to update UE with the network selection information for the subscribed Hosting Network + +![Sequence diagram showing the procedure for home network to update UE with network selection information for the subscribed Hosting Network. The diagram involves four main entities: UE, RAN, AMF, and UDM/AUSF. The RAN, AMF, and UDM/AUSF are grouped under the label 'Home Network'. The sequence of messages is: 1. Registration Request (Target localized services) from UE to AMF; 2. Authorization for the target localized services from AMF to UDM/AUSF; 3. Registration Accept/UE configuration update (Information of the hosting network) from AMF to UE.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UDM/AUSF + Note right of AMF: Home Network + UE->>AMF: 1. Registration Request (Target localized services) + AMF->>UDM/AUSF: 2. Authorization for the target localized services + AMF->>UE: 3. Registration Accept/UE configuration update (Information of the hosting network) + +``` + +Sequence diagram showing the procedure for home network to update UE with network selection information for the subscribed Hosting Network. The diagram involves four main entities: UE, RAN, AMF, and UDM/AUSF. The RAN, AMF, and UDM/AUSF are grouped under the label 'Home Network'. The sequence of messages is: 1. Registration Request (Target localized services) from UE to AMF; 2. Authorization for the target localized services from AMF to UDM/AUSF; 3. Registration Accept/UE configuration update (Information of the hosting network) from AMF to UE. + +**Figure 6.13.3.2-1: Procedure for home network to update UE with network selection information for hosting network** + +- Step 1: UE indicates its target localized services (via a list of identification of the localized services) in the NAS message: Registration Request when UE registers to the AMF of the home network. +- Step 2: Home network may perform the authorization and authentication for the target localized services based on the local network policy and UE subscription. + +**Editor's note:** It is FFS how the authorization and authentication for the target localized service are performed in the home network, + +- Step 3: Based on the UE subscription of the target localized services provided by the hosting networks and the availability of the hosting network(s) in the location of the UE, the AMF of the home network may returns the information of the hosting network providing the target services to the UE in the NAS message: Registration Accept or UE configuration update, which includes: + - List of SNPIDs of the hosting network associated with the localized services. + - Special restriction for the localized services, including time and location restrictions. + - N3IWF address of the home network, which may be used for hosting network as an underlay network to access the home network. + +**Editor's note:** It is FFS whether ANDSP can be reused to provide N3IWF information to UE. + +- Credentials to access hosting network(s). + +**NOTE:** Whether and how credential can be sent to UE via NAS message is up to SA WG3. + +UE may store the information of the hosting network; it is up to UE to determine its way to access to hosting network when it is available, such as: + +- For a dual-radio capability UE, UE may access the hosting network directly on one radio link and retain the connection with the home network with the other radio link. + +- For a single-radio capability UE, UE access the home network via the hosting network as an underlay network, for both services from hosting network and the home network. + +### 6.13.3.3 Procedure for hosting network to instruct the UE to return to the home network + +![Sequence diagram showing the procedure for the hosting network to instruct the UE to return to the home network. The diagram involves three main entities: UE, RAN, and AMF (within the Hosting Network). The sequence of messages is: 1. Localized service end indication (AMF to RAN to UE), 2. Mobility status report (UE to RAN to AMF), 3. Group UE and assign back off timer value (AMF to RAN), 4. Mobility Command (back off timer) (RAN to UE), and 5. UE starts to register to home network at the expire of the back off timer (UE action).](977811d1c73b74f801be9f4c376694ca_img.jpg) + +``` +sequenceDiagram + participant UE + participant RAN + participant AMF + Note right of AMF: Hosting Network + + AMF->>RAN: 1.Localized service end indication + RAN->>UE: 1.Localized service end indication + UE->>RAN: 2.Mobility status report + RAN->>AMF: 2.Mobility status report + AMF->>RAN: 3.Group UE and assign back off timer value + RAN->>UE: 4.Mobility Command(back off timer) + Note left of UE: 5.UE starts to register to home network at the expire of the back off timer +``` + +Sequence diagram showing the procedure for the hosting network to instruct the UE to return to the home network. The diagram involves three main entities: UE, RAN, and AMF (within the Hosting Network). The sequence of messages is: 1. Localized service end indication (AMF to RAN to UE), 2. Mobility status report (UE to RAN to AMF), 3. Group UE and assign back off timer value (AMF to RAN), 4. Mobility Command (back off timer) (RAN to UE), and 5. UE starts to register to home network at the expire of the back off timer (UE action). + +**Figure 6.13.3-1: Procedure for hosting network to instruct UE to return to the home network** + +- Step 1: AMF sends the localized service end indication to the registered UE, which may include the list of the identity of the localized service that is about to end. +- Step 2: Upon receiving the end indication of the localized service from the AMF, If UE determines all the target localized services provided by the hosting network end, UE reports the Nwu interface status and related home network identity(e.g. PLMN ID) that the Nwu interface connects to. UE reports the availability of the coverage of the home network (e.g. the signal strength of the home network detected by the UE meets the requirement to access to). +- Step 3: For every single home network, AMF may group the UEs into four groups: + - Group1: Nwu interface for home network exists and coverage of the home network exists. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register and establish the PDU session in the home network immediately. + - Group2: Nwu interface for home network does not exist and coverage of the home network exists. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register to the home network immediately. The pre-defined range of back-off timer in Group2 should be longer than which of in Group1. + - Group3: Nwu interface for home network exists and coverage of the home network does not exist. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register and establish the PDU session in the home network when UE detects the availability of the home network. The pre-defined range of back-off timer in Group3 should be longer than which of in Group2. + - Group4: Nwu interface for home network does not exist and coverage of the home network does not exist. AMF may assign a random back-off timer value from a pre-defined range for each UE in order to trigger the UE to start to register to home network when UE detects the availability of the home network. The pre-defined range of back-off timer in Group4 should be longer than which of in Group3. + +NOTE: For each of the home network operator and the hosting network operator, there may be a SLA to configure the pre-defined range value corresponding to different groups. On the other hand, the hosting network may configure the pre-defined range value corresponding to different groups locally. + +- Step 4: AMF sends the mobility command to each of UE, which includes the assigned random back-off timer value from the predefined range corresponding to different groups. +- Step 5: Upon receiving the value of back-off timer from the AMF of the hosting network, UE should wait until the expiry of the back-off timer to initiate the registration attempt and PDU session establishment request attempt if needed to the home network. + +## 6.13.4 Impacts on services, entities, and interfaces + +UE: + +- Ability to indicate its target localized services in NAS message based on the received list of the identification of the localized services. + +PCF: + +- Support to receive and respond to Access Information from the NEF. +- Support to build network rules/policies to apply for localized server requests from the localized service provider and send to AMF and SMF respectively to perform. + +AMF: + +- Ability to receive and handle the list of the identification of the localized services, the modified service area restrictions, and the modified QoS (e.g. UE-AMBR, UE-Slice-MBR) parameters from the PCF. + +SMF: + +- Ability to receive and handle the list of the identification of the localized services, the modified QoS (e.g. Authorized MBR, Authorized session-AMBR), the Revalidation time limit, the Time Condition, etc. parameters from the PCF. + +NEF: + +- Ability to receive and respond to Access Information from the AF (localized service provider). + +## 6.14 Solution #14: Solution for hosting network selection + +### 6.14.1 Introduction + +This solution solves several requirements listed in Key Issue#4. + +This solution is used in the scenario when the hosting network is an SNPN. In this solution, two alternatives are provided for a UE to receive hosting network selection and access information from Localized service provider, after the UE establishes business relationship with the Localized service provider: + +- 1) UE receives hosting network selection and access information from Localized service provider using UP provisioning mechanism; +- 2) UE receives hosting network selection and access information from local SP using SoR procedure. + +In both alternatives, the Localized service provider obtains Hosting Network Selection and Access Information from the Hosting network. + +### 6.14.2 Functional Description + +In this solution, the hosting network sends Hosting Network Selection and Access Information to the local service provider, who provides service to UEs accessing the hosting network. + +The Hosting Network Selection and Access Information consists the following information: + +- Hosting Network Identifier, e.g. SNPN ID in the case of the hosting network is an SNPN. +- The time condition information when the hosting network provides access service. +- The location condition information where the hosting network provides access service. +- Optionally, credential used for the UE to access the hosting network. Credential may be only provided if hosting network is an SNPN. + +The UE receives the Hosting Network Selection and Access Information from the localized service provider. The UE selects a hosting network when the time and location condition information is satisfied. + +### 6.14.3 Procedures + +![Sequence diagram showing the interaction between UE, Localized service provider (LSP), and Hosting Network. The LSP contains an LSP App, and the Hosting Network contains a NEF and a UDR. The sequence is: 1. UDR to NEF (Hosting network selection and access information); 2. NEF to LSP App (Hosting network selection and access information); 3. UE to LSP App (UE establishes connection with LSP App); 4. LSP App to UE (Hosting network selection and access information); 5. UE internal procedure (hosting network selection procedure).](83c2ebae8819e9cdca7eb157a13ee26a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant LSP as Localized service provider(LSP) + participant HN as Hosting Network + Note right of LSP: LSP App + Note right of HN: NEF, UDR + UDR->>NEF: 1. Hosting network selection and access information + NEF->>LSP App: 2. Hosting network selection and access information + UE->>LSP App: 3. UE establishes connection with LSP App + LSP App->>UE: 4. Hosting network selection and access information + Note left of UE: 5. hosting network selection procedure + +``` + +Sequence diagram showing the interaction between UE, Localized service provider (LSP), and Hosting Network. The LSP contains an LSP App, and the Hosting Network contains a NEF and a UDR. The sequence is: 1. UDR to NEF (Hosting network selection and access information); 2. NEF to LSP App (Hosting network selection and access information); 3. UE to LSP App (UE establishes connection with LSP App); 4. LSP App to UE (Hosting network selection and access information); 5. UE internal procedure (hosting network selection procedure). + +**Figure 6.14.3-1: UE receives hosting network selection and access information from Localized service provider using UP provisioning mechanism** + +1. The hosting network server sends Hosting Network Selection and Access Information to the NEF. + +The hosting network (HN) server stores the Hosting Network Selection and Access Information and send it to the local service providers who provide services to the UEs accessing the hosting network. + +The HN server may be the UDR in the hosting network. The UDR sends Nudr\_DM\_Notify message to the NEF of hosting network, including LSP ID and the Hosting Network Selection and Access Information. + +The HN server may include the IDs of all the LSPs which provide localized services via the hosting network. + +2. The NEF sends the Hosting Network Selection and Access Information to the Local Service Provider (LSP) App. + +The NEF sends Nnef\_EventExposure\_Notify message to the LSP App, including the Hosting Network Selection and Access Information. + +3. The UE establishes connection with the local service provider App. + +The UE may establish a PDU Session via its home network and establishes connection via the PDU Session. + +NOTE 1: How the UE knows the address of the local service provider App is out of 3GPP scope, for example, from the ticket the user bought for a football match. + +4. The UE receives the Hosting Network Selection and Access Information from the local service provider App. + +5. For automatically network selection, when the corresponding time and location condition information is satisfied, the UE activates SNPN access mode. The UE selects a hosting network based on the Hosting Network Identifier in the Hosting Network Selection and Access Information when the corresponding time and location condition information is satisfied. + +For manual network selection, when the corresponding time and location condition information is satisfied, the UE provides to the user the list of hosting networks (each is identified by a PLMN ID and NID) and related human-readable names (if available) of the available hosting networks. The user selects manually one hosting network from the list. + +![Sequence diagram showing the UE receiving hosting network selection and access information from a local SP using the SoR procedure. The diagram involves three main entities: Home Network (containing AMF, UDM, NEF), Localized service provider (LSP) (containing LSP App), and Hosting Network (containing NEF, NSAI Server). The sequence of messages is: 1. NSAI Server to NEF (HN); 2. NEF (HN) to LSP App; 3. LSP App to NEF (HN); 4. NEF (HN) to UDM; 5. UDM to AMF; 6. AMF to UE; 7. UE internal procedure.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph Home Network + AMF + UDM + NEF_HN[NEF] + end + subgraph LSP + LSP_App[LSP App] + end + subgraph Hosting Network + NEF_HN + NSAI_Server[NSAI Server] + end + NSAI_Server->>NEF_HN: 1. Hosting network selection and access information + NEF_HN->>LSP_App: 2. Hosting network selection and access information + LSP_App->>NEF_HN: 3. Hosting network selection and access information + NEF_HN->>UDM: 4. Hosting network selection and access information + UDM->>AMF: 5. Hosting network selection and access information + AMF->>UE: 6. Hosting network selection and access information + Note left of UE: 7. hosting network selection procedure + +``` + +Sequence diagram showing the UE receiving hosting network selection and access information from a local SP using the SoR procedure. The diagram involves three main entities: Home Network (containing AMF, UDM, NEF), Localized service provider (LSP) (containing LSP App), and Hosting Network (containing NEF, NSAI Server). The sequence of messages is: 1. NSAI Server to NEF (HN); 2. NEF (HN) to LSP App; 3. LSP App to NEF (HN); 4. NEF (HN) to UDM; 5. UDM to AMF; 6. AMF to UE; 7. UE internal procedure. + +**Figure 6.14.3-2: UE receives hosting network selection and access information from local SP using SoR procedure** + +1. The hosting network server sends Hosting Network Selection and Access Information to the NEF. + +The hosting network (HN) server stores the Hosting Network Selection and Access Information and send it to the local service providers who provide services to the UEs accessing the hosting network. + +The HN server may be the UDR in the hosting network. The UDR sends Nudr\_DM\_Notify message to the NEF of hosting network, including LSP ID and the Hosting Network Selection and Access Information. + +The HN server may include the IDs of all the LSPs which provide localized services via the hosting network. + +2. The NEF sends the Hosting Network Selection and Access Information to the local service provider App. + +The NEF sends Nnef\_EventExposure\_Notify message to the LSP App, including the Hosting Network Selection and Access Information. + +3. The LSP App sends Nnef\_ParameterProvision\_Create message to the home network of the UE including the Hosting Network Selection and Access Information. + +NOTE 2: How the LSP App can obtain the home network of the UE is out of 3GPP scope, for example, from the UE's mobile phone number. + +4. The NEF of the home network of the UE sends Nudm\_ParameterProvision\_Create to the UDM of the home network of the UE, including the Hosting Network Selection and Access Information. + +5. The UDM notifies the AMF of the UE of the Hosting Network Selection and Access Information via Nudm\_SDM\_Notification Notify message. + +6. The AMF sends a DL NAS TRANSPORT message to the UE, including the Hosting Network Selection and Access Information. + +NOTE 3: Steps 5 and 6 can reuse the corresponding steps in SoR mechanism as described in Annex C of TS 23.122 [6] or user parameter update procedure as described in TS 23.502 [4]. + +7. For automatically network selection, when the corresponding time and location condition information is satisfied, the UE activates SNPN access mode. The UE selects a hosting network based on the Hosting Network Identifier in the Hosting Network Selection and Access Information when the corresponding time and location condition information is satisfied. + +For manual network selection, when the corresponding time and location condition information is satisfied, the UE provides to the user the list of hosting networks (each is identified by a PLMN ID and NID) and related human-readable names (if available) of the available hosting networks. The user selects manually one hosting network from the list. + +## 6.14.4 Impacts on services, entities, and interfaces + +UE impact: + +- Ability to receive Hosting Network Selection and Access Information from the local service provider App or via SoR procedure. +- Ability to perform hosting network selection based on the received Hosting Network Selection and Access Information. + +Hosting Network impact: + +- Ability to send Hosting Network Selection and Access Information to the local service provider. + +Home Network impact: + +- NEF: Ability to receive Hosting Network Selection and Access Information from the local service provider. +- UDM: Ability to receive Hosting Network Selection and Access Information from the NEF and sends Hosting Network Selection and Access Information to the UE using SoR procedure or user parameter update procedure. + +## 6.15 Solution #15: Local service provisioning via PLMN + +### 6.15.1 Introduction + +This solution mainly addresses Key Issue #4 and #5. The local service platform generates and provides the local service access information and provides it to the UE, through the UE's serving PLMN. + +### 6.15.2 Functional Description + +This solution assumes that the local service provider has a business agreement with the PLMN operator. Its service platform utilizes the PLMN's network exposure framework for providing the local service access information to the requesting UE. + +The local service platform monitors the Local Service Subscription events through the PLMN network exposure function. Such an event is triggered when a UE initiates subscription request (e.g. via NAS request) for a interested local service. The UE may have learned the desired local service information (e.g. local service name/identifier) via various channels that are out of 3GPP scope. + +When the local service platform receives the Local Service Subscription event, and if it is acceptable, it generates the local service access information for the requesting UE and provides it to the UE through the PLMN network exposure function. The local service access information may include the hosting network identifier, temporary credential for accessing the hosting network and local service, etc. + +With the local service information, the UE should be able to access the hosting network and may further obtain more configuration for accessing the local service from the hosting network. + +### 6.15.3 Procedures + +![Sequence diagram illustrating the local service provisioning via PLMN. The diagram shows interactions between UE, AMF, UDM/NEF, and AF (local service platform).](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) + +``` + +sequenceDiagram + participant AF as AF (local service platform) + participant UDM/NEF + participant AMF + participant UE + + Note right of AF: 1. Network event exposure subscription (Local Service Subscription event) + AF->>UDM/NEF: 1. Network event exposure subscription (Local Service Subscription event) + Note right of UDM/NEF: 2. Network event exposure subscription (Local Service Subscription Event) + UDM/NEF->>AMF: 2. Network event exposure subscription (Local Service Subscription Event) + Note left of UE: 3. Local service subscription request triggered + UE->>AMF: 4. NAS request for local service subscription (local service ID) + Note right of AMF: 5. Network event notification (Local Service Subscription event) + AMF->>UDM/NEF: 5. Network event notification (Local Service Subscription event) + Note right of UDM/NEF: 6. Generate local service access information + UDM/NEF->>AF: 6. Generate local service access information + Note right of AF: 7. UDM parameter provisioning procedure for delivering local service access information + AF->>UDM/NEF: 7. UDM parameter provisioning procedure for delivering local service access information + +``` + +Sequence diagram illustrating the local service provisioning via PLMN. The diagram shows interactions between UE, AMF, UDM/NEF, and AF (local service platform). + +**Figure 6.15.3-1: Local service provisioning via PLMN** + +1. The AF in the local service platform subscribes to the Local Service Subscription event notification from the 5GC. The AF indicates its local service identifier in the subscription request. +2. The NEF determines the AMFs that serve the areas where the local service is available and subscribes to the Local Service Subscription event notification from the AMF. +3. The UE has obtained the local service related information such as local service identifier through various channels that are out of 3GPP scope. The local service subscription request may be triggered, for example, by the user input or when entering the area where the local service is available. +4. The UE initiates local service subscription by sending a NAS request to the AMF. The UE indicates the desired local service identifier in the request. +5. The AMF detects the Local Service Subscription event and sends the event notification to the NEF. +6. The NEF forwards the event notification to the AF in the local service platform. +7. If the subscription request is acceptable, the local service platform generates the information necessary for accessing the local service, such as the initial credentials. +8. The local service platform uses the NEF/UDM 's external parameter provisioning procedure to deliver the local service access information to the UE that has requested the subscription. + +### 6.15.4 Impacts on Services, Entities, and Interfaces + +NEF, UDM and AMF need to support new Local Service Subscription event. + +AMF and UE need to support new NAS message or IE that indicates local service subscription request. + +## 6.16 Solution #16: Access to SNPN with NG-RAN and to WLAN Access Network using the same credentials + +### 6.16.1 Introduction + +The architecture defined for non-3GPP access in PLMNs for trusted and untrusted access relied on the assumption that the PLMN owns already a 3GPP based CN and therefore the 3GPP identities and credentials are used when the UE is also accessing over non-3GPP access e.g. WLAN. It is also assumed that the PLMN offers services e.g. IMS voice/SMS that the UE cannot access directly from the non-3GPP access and therefore it needs to connect to the 3GPP CN. This is achieved for example through connection to N3IWF in the case of untrusted non-3GPP access architecture or for Trusted Non-3GPP access using the network elements of TNAP and TNGF. + +These assumptions may though not hold true in "enterprise" environment that will possibly deploy 3GPP based "private cellular network"/SNPN while it already has a deployed WLAN infrastructure in place. For example in such enterprise environment the identities and credentials used for WLAN authentication could be already provisioned to the "enterprise" UEs before the SNPN is deployed. In such network environment also access to specific services can be restricted through using a VPN that runs on top of internet connection provided from WLAN or using application layer authentication and therefore there is possibly no need to have N3IWF in the "untrusted non-3GPP access" architecture and there is no need to upgrade the existing WLAN infrastructure to support what is required from TNAP and TNGF in the "trusted non-3GPP access" architecture. + +The other two aspects that need consideration is the access network selection and mobility. For access network selection mechanisms standardised by 3GPP e.g. using ANDSP need to be enhanced for Non-Seamless WLAN Offload or rely on local UE configuration. Seamless mobility is not in scope of this solution since many applications can also work with nomadic mobility. + +The solution describes how UE can access an SNPN with NG-RAN on one hand and a WLAN Access Network on the other hand using the same credentials. If the credentials use AKA and USIM authentication and are stored in UDM, the existing mechanisms for Non-Seamless WLAN Offload defined in TS 33.501 [10] and TS 23.501 [3] apply. + +If the credentials are stored in a AAA Server possibly new authentication procedures and Non-Seamless WLAN Offload (NSWO) architecture need to be defined. After being authenticated the UE does not have access to 5GC via WLAN and it performs only Non-seamless WLAN offload traffic. + +In summary this solution proposes the following enhancements: + +- (1) in the case of SNPN with non-3GPP credentials there has to be an association between the WiFi and cellular (non-3GPP) credentials that are stored in the cellular modem; and +- (2) WLANSPs support for SNPN ID, GIN to identify WLAN AN associated with the SNPN. + +The details are described in the following clauses. + +### 6.16.2 Functional Description + +The solution focuses on the case that the credentials are stored in a AAA Server and has the following properties: + +- The same AAA Server that is used for WLAN access authentication in a WLAN Access Network is also used for primary authentication in SNPN with NG-RAN by re-using the architecture defined for "Credentials Holder for primary authentication and authorization" in clause 5.30.2.9.2 of TS 23.501 [3]. +- SWa interface that is based on Radius/Diameter is assumed between WLAN Access Network and AAA-S +- The UE uses the same permanent identity and credentials for primary authentication in SNPN and for WLAN access authentication in WLAN Access Network +- For example the identity and credentials already used for WLAN access authentication are also used in SNPN as SUPI in NAI format. +- WLAN network selection can be based on enhanced WLAN Selection Policy (WLANSP) rules from ANSDP used for Non-Seamless WiFi Offload i.e. as defined in clause 4.8.2.1.6 of TS 23.402 [9] or local configuration in the UE. + +NOTE: The WLANSP rules in Rel-17 are only supported for PLMNs. + +- The SNPN can configure the UE to use a specific identity (SUCI) and credentials for specific WLAN networks, e.g. by associating the conditions from WLANSP rules with a specific identity (SUPI) and credentials to be used for the specific WLAN network e.g. based on the PreferredSSIDList or the HomeNetwork attribute containing the SNPN-id . +- The WLAN Access Network and the SNPN provide access to the same Data Network e.g. internet or enterprise network +- Optionally assignment of IP addresses in the WLAN Access Network and in the SNPN can happen from same IP address pool, if needed, based on local policy. + +Seamless mobility between the SNPN and the WLAN Access Network is not supported by this architecture. Seamless mobility can be provided if additionally N3IWF is deployed but this is out of scope of this specific solution. + +![Figure 6.16.2-1: Access to SNPN with NG-RAN and to WLAN Access Network using the same credentials. The diagram shows a UE connected to an (RAN) via N1 and to a WLAN Access Network via a WLAN interface. The (RAN) is connected to an AMF via N2 and N3. The AMF is connected to the SNPN Core Network (CN) via Namf. The SNPN CN includes UDM, NEF, NRF, PCF, AF, AUSF, and NSSAAF. The AMF is also connected to the SMF via Nsmf. The SMF is connected to the UPF via N4. The UPF is connected to the DN via N6 and N9. The AAA Server is connected to the WLAN Access Network via SWa. The Credential Holder is connected to the AAA Server. A dashed line indicates that the connection between the DN and the WLAN Access Network is out of scope.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +The diagram illustrates the network architecture for accessing an SNPN. At the top, a 'Credential Holder' and an 'AAA Server' are shown. The AAA Server is connected to a 'WLAN Access Network' via an 'SWa' interface. Below a horizontal dashed line, the SNPN Core Network (CN) is depicted, containing several Network Functions (NFs): NSSF, UDM, NEF, NRF, PCF, AF, AUSF, and NSSAAF. These NFs are connected to a central Service Interface (SBI) bus. Below the SBI, the AMF (Access and Management Function) and SMF (Session Management Function) are shown. The AMF connects to the SBI via 'Namf' and to the (RAN) via 'N2' and 'N3' interfaces. The SMF connects to the SBI via 'Nsmf' and to the UPF (User Plane Function) via an 'N4' interface. The UPF connects to the DN (Data Network) via 'N6' and 'N9' interfaces. A dashed line from the DN to the WLAN Access Network is labeled 'Out of scope'. At the bottom, the UE (User Equipment) is shown, connected to the (RAN) via 'N1' and to the WLAN Access Network via a 'WLAN i/f'. + +Figure 6.16.2-1: Access to SNPN with NG-RAN and to WLAN Access Network using the same credentials. The diagram shows a UE connected to an (RAN) via N1 and to a WLAN Access Network via a WLAN interface. The (RAN) is connected to an AMF via N2 and N3. The AMF is connected to the SNPN Core Network (CN) via Namf. The SNPN CN includes UDM, NEF, NRF, PCF, AF, AUSF, and NSSAAF. The AMF is also connected to the SMF via Nsmf. The SMF is connected to the UPF via N4. The UPF is connected to the DN via N6 and N9. The AAA Server is connected to the WLAN Access Network via SWa. The Credential Holder is connected to the AAA Server. A dashed line indicates that the connection between the DN and the WLAN Access Network is out of scope. + +Figure 6.16.2-1: Access to SNPN with NG-RAN and to WLAN Access Network using the same credentials + +## 6.16.3 Procedures + +### 6.16.3.1 WLAN Authentication with AAA Server + +The figure 6.16.3-1 describes the WLAN authentication using a AAA Server. + +![Sequence diagram for WLAN authentication sharing with AAA Server. The diagram shows four lifelines: UE, WLAN Access Network, AAA-P (optional), and AAA. The sequence starts with '0. WLAN network selection' in the UE. Step 1: 'WLAN Conn. Established' between UE and WLAN Access Network. Step 2: 'EAP-REQ/Identity' from WLAN Access Network to UE. Step 3: 'EAP-RSP/Identity (SUCI in NAI format)' from UE to WLAN Access Network. Step 4: 'AAA (EAP-RSP/Identity)' from WLAN Access Network to AAA-P. Step 5: 'AAA (EAP-RSP/Identity)' from AAA-P to AAA. Step 6: 'EAP Authentication' between UE and AAA. Step 7: 'AAA (EAP-Success)' from AAA to AAA-P. Step 8: 'AAA (EAP-Success)' from AAA-P to WLAN Access Network. Step 9: 'EAP-Success' from WLAN Access Network to UE.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant UE + participant WLAN as WLAN Access Network + participant AAA-P as AAA-P (optional) + participant AAA + Note left of UE: 0. WLAN network selection + UE->>WLAN: 1. WLAN Conn. Established + WLAN->>UE: 2. EAP-REQ/Identity + UE->>WLAN: 3. EAP-RSP/Identity (SUCI in NAI format) + WLAN->>AAA-P: 4. AAA (EAP-RSP/Identity) + AAA-P->>AAA: 5. AAA (EAP-RSP/Identity) + Note over UE, AAA: 6. EAP Authentication + AAA->>AAA-P: 7. AAA (EAP-Success) + AAA-P->>WLAN: 8. AAA (EAP-Success) + WLAN->>UE: 8. EAP-Success + +``` + +Sequence diagram for WLAN authentication sharing with AAA Server. The diagram shows four lifelines: UE, WLAN Access Network, AAA-P (optional), and AAA. The sequence starts with '0. WLAN network selection' in the UE. Step 1: 'WLAN Conn. Established' between UE and WLAN Access Network. Step 2: 'EAP-REQ/Identity' from WLAN Access Network to UE. Step 3: 'EAP-RSP/Identity (SUCI in NAI format)' from UE to WLAN Access Network. Step 4: 'AAA (EAP-RSP/Identity)' from WLAN Access Network to AAA-P. Step 5: 'AAA (EAP-RSP/Identity)' from AAA-P to AAA. Step 6: 'EAP Authentication' between UE and AAA. Step 7: 'AAA (EAP-Success)' from AAA to AAA-P. Step 8: 'AAA (EAP-Success)' from AAA-P to WLAN Access Network. Step 9: 'EAP-Success' from WLAN Access Network to UE. + +**Figure 6.16.3-1: WLAN authentication sharing with AAA Server as in Figure 6.16.2-1** + +- 0) If the SNPN supports the architecture as in Figure 6.16.2-1 and wants the UE to use the same credentials for access to a WLAN Access Network and to this SNPN, then the SNPN configures in the UE the same permanent identity and credentials for primary authentication with the SNPN and for WLAN access authentication with the WLAN Access Network. WLAN network selection can be based on enhanced WLAN Selection Policy (WLANS) rules from ANSDP used for Non-Seamless WiFi Offload i.e. as defined in clause 4.8.2.1.6 of TS 23.402 [9]. + +The SNPN can configure the UE to use a specific identity (SUCI) and credentials for specific WLAN networks, e.g. by associating the conditions from WLANS rules that in Rel-17 are only supported for PLMNs with a specific identity (SUCI) and credentials to be used for the specific WLAN network e.g. based on the PreferredSSIDList or the HomeNetwork attribute containing the SNPN-id. + +Steps 1-8 are out of scope of SA2 and are shown for information: + +1. A connection is established between the UE and the WLAN AP, using a specific procedure based on IEEE 802.11. +2. The WLAN AP sends an EAP Identity Request to the UE. +3. The UE always sends the SUCI in NAI format. +4. The WLAN AP sends a SWa protocol message (could be over RADIUS or Diameter interface) with EAP identity response, NAI containing the SUCI to AAA Proxy. +5. If AAA Proxy is used it forwards the SWa message to AAA Server based on the NAI of the SUCI. +6. EAP authentication is performed. Any EAP method can be used for WLAN authentication between the UE and the AAA Server. + +- 7, 8. AAA Server performs successful authentication. When AAA Proxy is used sends a SWa protocol message with EAP-success and possibly other security parameters to WLAN. EAP-success message is forwarded from WLAN AP to the UE. + +**Editor's note:** New authentication procedures and Non-Seamless WLAN Offload (NSWO) architecture need to be defined. Security aspects are in SA WG3 scope. + +### 6.16.3.2 User plane aspects + +The UE needs to acquire a local IP address on WLAN access that may optionally be from same IP address pool, if needed, based on local policy. + +Following same principles as in TS 23.501 [3] for UE supporting non-seamless WLAN offload, while connected to WLAN access and registered in the SNPN via NG-RAN, the UE can route specific data flows via the WLAN access without traversing the 5GC of SNPN. The UE data flows are identified using URSP configuration for Non-Seamless Offload, or UE Local Configurations as defined in TS 23.503 [5]. For these data flows, the UE uses the local IP address allocated by the WLAN access network and no IP address preservation is provided between WLAN and SNPN. + +### 6.16.4 Impacts on services, entities, and interfaces + +UE: + +- uses the same permanent identity (SUCI) and credentials for primary authentication in SNPN and for WLAN access authentication in a WLAN Access Network. +- UE is optionally configured to associate the conditions from WLANSP rules that in Rel-17 are only supported for PLMNs with specific identity (SUPI) and credentials to be used for the specific WLAN network e.g. based on the PreferredSSIDList or the HomeNetwork attribute containing the SNPN-id. Otherwise local configuration can be used. +- New authentication procedures and Non-Seamless WLAN Offload (NSWO) architecture need to be defined. Security aspects are in SA WG3 scope. WLAN AP (informative impact). +- Support compatible security mechanisms with 5GS. +- SWa interface that is based on Radius/Diameter is assumed between WLAN Access Network and AAA-S. + +No other impacts in the UE, NG-RAN, and 5GC are identified. + +## 6.17 Solution #17: UE Group specific NAS level congestion control + +### 6.17.1 Introduction + +One of the aspects of the Key Issue #6 is how to mitigate user plane and control plane overload caused by a high number of UEs returning from a temporary local access of a hosting network to their home network in a very short period of time. + +This solution describes how the existing mechanisms defined in clause 5.19.7.5 of TS 23.501 [3] can be enhanced to support NAS level congestion control for a specific group of UEs that has temporarily accessed to a local service(s) and has attempted to return their home network almost simultaneously. + +### 6.17.2 Functional Description + +The proposed solution focuses on using group specific NAS level congestion control mechanism to mitigate user plane and control plane overload caused by a higher number of UEs returning from a hosting network to their home network in a very short period of time. + +Group specific NAS level congestion control is performed at the 5GC only, and it is transparent to UE. The AMF or SMF or both may apply NAS level congestion control for a UE associated to an Internal-Group Identifier described in clause 5.9.7 of TS 23.501 [3]. + +The home network associates UEs temporarily accessing localized services to an Internal-Group Identifier, which can be specific to each local hosting network and/or service, and applies UE group-specific NAS level congestion control to mitigate user plane and control plane overload caused during the return of UEs. The home network removes the UE from the group after it has returned to the home network. If the UE did not return back to the home network after accessing the localized service(s) or the UE is switched off before moving back to the home network, the home network removes the UE from the group sometime after the duration of the localized service(s) that UE has accessed. This additional time to the localized service duration can be implementation specific. If the UE has accessed more than one localized service, the longest localized service duration will be considered. + +### 6.17.3 Procedures + +The home network (HPLMN) and/or local hosting network (LHN) may group the UEs based on the information: + +- when the UE-initiated de-registration request message sent from UE to its HPLMN in order to access to local services provided by a LHN, UE indicates in the de-registration message (i.e. "hosting network access" or "5GS local network access indication") that the de-registration request is to access to local services provided by a LHN; or +- when the network-initiated de-registration request message sent from network to the UE in order to enable the UE to register with a LHN to access to local services, the network indicates in the de-registration message (i.e. "hosting network access" or "5GS local network access indication") that the de-registration request is to enable UE to register with a LHN to access to local services. + +The home network (HPLMN) may utilize: + +- an application function (AF) residing in the local hosting network(s); or +- an exposure framework from local hosting network(s), + +to receive information on users who requested access or has accessed to the local service(s) in order to associate users to an Internal-Group Identifier specific to local hosting network(s) and/or local service(s). + +If the local hosting network does not support an AF and an exposure framework to the home network, the home network uses UE-/network-initiated de-registration request message approach along with any other selection and access mechanisms proposed as part of KI#4. If the local hosting network supports an AF and an exposure framework, the home network uses the information provided by the local hosting network to associate users to an Internal-Group Identifier specific to local hosting network(s) and/or local service(s). + +**Editor's note:** It is FFS whether and how new mechanism(s) developed for KI#5 is considered in this solution. + +Then, the network (AMF or SMF) applies UE group-specific NAS level congestion control to manage the return of UEs from the LHN to their home PLMN by spreading out the registration attempts over time and limiting the number of UEs attempting to register simultaneously when the UEs accessed to the local service(s) provided by the LHN(s) are returning back to their home network. + +### 6.17.4 Impacts on services, entities and interfaces + +UDM: + +- Support for local hosting network and/or local service information in the Internal-Group Identifier. + +UE: + +- Shall support configuration and handling of the localized service related de-registration information (i.e. "hosting network access" or "5GS local network access indication"). + +AMF: + +- Shall support localized service related de-registration information element (i.e. "hosting network access" or "5GS local network access indication"). + +AMF/SMF: + +- Shall apply Group Specific NAS level congestion control when UEs temporarily accessed to local service(s). + +NEF: + +- Shall support exposure from local hosting networks + +## 6.18 Solution #18: Steering of UE to select hosting network for obtaining localized services + +### 6.18.1 Introduction + +One of the aspects of the key issue #5 is how the network would determine the need to steer or instruct the UE to hosting network and other aspect is on how actually network would steer the UE toward the hosting network. + +The proposed solution focuses on the case when based on location and time, certain localized services are available, which are being provided by the hosting network and using "Steering of Roaming" mechanism to allow service provider (PLMN or 3rd Party service provider) to update the UE with required information on availability of hosting networks along with the services they are providing. This information will assist the UE to make the switch to appropriate hosting network for obtaining localized services. + +Steering of Roaming information container would carry the "operator defined hosting network selector list", which will assist the UE to switch to hosting network for obtaining localized services. + +### 6.18.2 Functional Description + +The proposed solution will be using similar concept and mechanism to "Steering of Roaming" as defined in TS 23.122 [6]. + +As per the service level agreement between the PLMN operator and hosting network operator/service provider, UE's HPLMN may create a "operator defined hosting network selector list" for the purpose of automatically steering the UE between PLMN and hosting networks. + +The "operator defined hosting network selector list" may consist of following information: + +- A prioritized list of hosting network identifiers (SNPN IDs). +- A validity time window may be associated with the hosting network identifier i.e. SNPN ID in the "operator defined hosting network selector list". +- A valid list of tracking areas (TAs) may be associated with the hosting network identifier i.e. SNPN ID in the "operator defined hosting network selector list". The total TAs in this list also indicates the service area of the local services that the UE is allowed to access. + +Also Home network (H-UDM) may decide to subscribe when a particular UE enters a specific area (Service area of a Hosting Network which may be hosting a particular event). This location information may be coordinated to the Home network during the service agreement of Hosting network and Home network and the Serving network, so that the NFs in the specific area of the serving network can reflect availability of hosting network which providing the localized services. + +### 6.18.3 Procedures + +Figure 6.18.3-1 shows the flow of steering of roaming information container with "operator defined hosting network selector list" to assist in UE with selection of hosting network. This procedure can be triggered during or after registration, UE's location, and time window are critical factors in deciding when this procedure is triggered by the UDM/SoR-AF/SP (Service Provider). + +![Sequence diagram titled 'Steering the UE with hosting network information'. The diagram shows interactions between UE, AMF, H-UDM, and SoR-AF/SP. The sequence starts with SoR-AF/SP sending Nudm_ParameterProvision to H-UDM. H-UDM sends Namf_EventExposure_Subscribe to AMF. UE moves to the area of interest (step 3). UE sends Mobility update to AMF (step 4). AMF sends Namf_EventExposure_Notify to H-UDM (step 5). H-UDM sends Sor_GetRequest to SoR-AF/SP (step 6a) and receives Sor_GetResponse (step 6b). H-UDM sends Nudm_SDM_Notification to AMF (step 7). AMF sends DL NAS transport to UE (step 8). UE performs steering of roaming information security check (step 9). UE sends UL NAS Transport to AMF (step 10). AMF sends Nudm_SDM_Info to H-UDM (step 11). H-UDM sends Nsoraf_SoR_info to SoR-AF/SP (step 12). UE performs hosting network selection (step 13).](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant H-UDM + participant SoR-AF/SP + + Note left of UE: 3. UE moves to the area of interest + SoR-AF/SP->>H-UDM: 1. Nudm_ParameterProvision + H-UDM-->>AMF: 2. Namf_EventExposure_Subscribe + UE->>AMF: 4. Mobility update + AMF-->>H-UDM: 5. Namf_EventExposure_Notify + H-UDM->>SoR-AF/SP: 6a. Sor_GetRequest + SoR-AF/SP-->>H-UDM: 6b. Sor_GetResponse + H-UDM-->>AMF: 7. Nudm_SDM_Notification + AMF->>UE: 8. DL NAS transport + Note left of UE: 9. Steering of roaming information security check + UE-->>AMF: 10. UL NAS Transport + AMF-->>H-UDM: 11. Nudm_SDM_Info + H-UDM-->>SoR-AF/SP: 12. Nsoraf_SoR_info + Note left of UE: 13. Hosting network Selection + +``` + +Sequence diagram titled 'Steering the UE with hosting network information'. The diagram shows interactions between UE, AMF, H-UDM, and SoR-AF/SP. The sequence starts with SoR-AF/SP sending Nudm\_ParameterProvision to H-UDM. H-UDM sends Namf\_EventExposure\_Subscribe to AMF. UE moves to the area of interest (step 3). UE sends Mobility update to AMF (step 4). AMF sends Namf\_EventExposure\_Notify to H-UDM (step 5). H-UDM sends Sor\_GetRequest to SoR-AF/SP (step 6a) and receives Sor\_GetResponse (step 6b). H-UDM sends Nudm\_SDM\_Notification to AMF (step 7). AMF sends DL NAS transport to UE (step 8). UE performs steering of roaming information security check (step 9). UE sends UL NAS Transport to AMF (step 10). AMF sends Nudm\_SDM\_Info to H-UDM (step 11). H-UDM sends Nsoraf\_SoR\_info to SoR-AF/SP (step 12). UE performs hosting network selection (step 13). + +**Figure 6.18.3-1: Steering the UE with hosting network information** + +Procedure: + +1. The SoR-AF/SP to HPLMN UDM: Nudm\_ParameterProvision is sent to the HPLMN UDM to trigger the update of the UE with new list of "operator defined hosting network selector list" or to trigger subscribing for Exposure services for interested location area. +2. Namf\_EventExposure\_Subscribe : H-UDM subscribes for notification for UE moving in or out of the subscribed "Area Of Interest" +3. UE moves to the area of interest +4. UE/NG-RAN does a mobility update/location reporting to the Serving Network AMF. +5. Namf\_EventExposure\_Notify: AMF reports the event specific parameters that were subscribed to the H-UDM. +- 6a-b. H-UDM may provide the info to the SoR-AF that may take decision to provide UE the Hosting Network information. +7. The HPLMN UDM to the AMF: The UDM notifies the changes of the user profile to the affected AMF by the means of invoking Nudm\_SDM\_Notification service operation. +8. The AMF to the UE: the AMF sends a DL NAS TRANSPORT message to the served UE. The AMF includes in the DL NAS TRANSPORT message the steering of roaming information received from the UDM. +9. UE: Upon receiving the SoR information, UE shall perform the security check on it. +10. The UE to AMF: If the UDM has requested an acknowledgement from the UE in the DL NAS TRANSPORT message, the UE sends an UL NAS TRANSPORT message to the serving AMF with an SOR transparent container including the UE acknowledgement. +11. The AMF to the HPLMN UDM: If the UL NAS TRANSPORT message with an SOR transparent container is received, the AMF uses the Nudm\_SDM\_Info service operation to provide the received SOR transparent container to the UDM. +12. The HPLMN UDM to the SOR-AF: HPLMN UDM informs the SoR-AF/Service Provider (SP) about the successful delivery of the SoR information (i.e. "operator defined hosting network selector list"). + +13. The UE will use the received steering of roaming information to assist in selection of the hosting network for obtaining localized services. The UE would select an SNPN if available and allowable (e.g. the time and location is within the validity time window and valid list of TA associated with the SNPN) for obtaining localized services, identified by an SNPN identity contained in the "operator defined hosting network selector list" in priority order. + +**Editor's note:** Switch between SNPN/PLMN access mode for network selection is FFS. + +## 6.18.4 Impacts on services, entities, and interfaces + +UDM: + +- Support for additional list (i.e. "operator defined hosting network selector list") in steering of roaming information. + +SoR-AF/SP: + +- Support for additional list (i.e. "operator defined hosting network selector list") in steering of roaming information. + +UE: + +- Shall support configuration and handling of the new list (i.e. "operator defined hosting network selector list"). +- Use the "operator defined hosting network selector list" for selection of hosting network. + +## 6.19 Solution #19: Access to SNPN services via Untrusted non-3GPP access network with underlay/overlay determination + +### 6.19.1 Introduction + +This solution is based on solution #2 for the UE can access SNPN services via Untrusted non-3GPP access network with the modifications described in this clause. + +Since Rel-15, the access restriction per access type can be performed based on per UE subscription and network policies configured by the operator, e.g. whether the UE is allowed to access 5GCN via 3GPP access or non-3GPP access, or both. If access via one access type is not allowed, the AMF rejects the UE request with an appropriate cause values as per specified in stage 3. For accessing the SNPN, in some cases, the SNPN may perform access control based on the exact access type of whether a UE accessing the SNPN via a PLMN or via non-3GPP access (e.g. WLAN). Consequently in order to enable different access control for the following scenarios: + +- To allow or forbidden the access to the SNPN via direct N3GPP access, e.g. a WLAN deployed in the SNPN. +- To allow or forbidden the access to the SNPN via indirect N3GPP access, e.g. via PLMN as defined in clause 5.30.2.8 and Annex D, clause D.3 of TS 23.501 [3] specify how the UE can access SNPN services via a PLMN. + +It is required to distinguish the scenarios otherwise the restriction "Non-3GPP access to 5GCN not allowed" or lack of restriction applies to both scenarios since from the point of view of SNPN they are both a N3GPP accesses. + +### 6.19.2 Functional Description + +The functional descriptions in clause 6.2.2 applies with the following modifications: + +- 1) The RAT type is extended adding the "Untrusted Non-3GPP over underlay 3GPP access" to indicate when the UE accesses to N3IWF via underlying network 3GPP network as defined in Clause 5.30.2.8 and Annex D, clause D.3 of TS 23.501 [3] in contrast the RAT-type "Untrusted N3GPP" indicates when the UE access via a N3GPP network, such as WLAN. +- 2) The N3IWF determines the access network information based on the local configuration (e.g. IP range for specific PLMN in service agreements) and the UE's local IP address used to reach the N3IWF. The N3IWF + +provides the access network information to AMF in addition to the UE's local IP address used to reach the N3IWF provided by N3IWF to AMF in "N3IWF user location information" IE in N2. + +**Editor's note:** It is FFS how N3IWF determines the access network information. + +- 3) The UE may include an access network information (e.g. access network = PLMN) in the NAS message Registration Request when performs the registration to N3IWF's SNPN. +- 4) The AMF of the SNPN uses the access network information provided by UE and the access network information provided by N3IWF to determine a more precise Untrusted Non-3GPP RAT type, i.e. "Untrusted Non-3GPP over underlay 3GPP access" or "Untrusted N3GPP". +- 5) The AMF of the SNPN authorizes UE's access network information and rejects UE with an appropriate cause code per UE subscription and network policies configured by the operator. +- 6) Based on the reject cause code received from SNPN, the UE disables the N1 mode capability for the "Untrusted Non-3GPP over underlay 3GPP access" of the SNPN; however, the UE can still attempt direct connection to SNPN via Untrusted non-3GPP access networks when needed. + +### 6.19.3 Procedures + +The functional descriptions in clause 6.2.3 applies with the following additions: + +- In step 5 of figure 4.12.2.2-1 of TS 23.502 [4] (for Registration procedure to Untrusted N3GPP) The UE may include an access network information (e.g. access network = PLMN or WLAN) in the NAS Registration Request when registering in SNPN over underlay PLMN. +- In step 6a of figure 4.12.2.2-1 of TS 23.502 [4] The N3IWF of SNPN determines the Access network type as described in clause 6.19.2, bullet 2). +- Step 6b of figure 4.12.2.2-1 of TS 23.502 [4] The N3IWF send the access network information to the AMF of SNPN. +- AMF determines the RAT type "Untrusted Non-3GPP over underlay PLMN" or "Untrusted N3GPP" as described in clause 6.19.2, bullet 4). +- The AMF performs access restriction based on the access information from both UE and N3IWF, and rejects the UE with proper cause code, e.g. access SNPN via PLMN is not allowed, so the UE disables the N1 mode capability for the underlay PLMN access based on such cause code; but the UE can still attempt direct connection to SNPN via Untrusted non-3GPP access networks when needed. + +### 6.19.4 Impacts on services, entities, and interfaces + +The impact descriptions in clause 6.2.4 applies with the following additions: + +UE impact: + +- Ability to determine it is accessing the SNPN via an underlay PLMN and include an access network information in the NAS message to the AMF of SNPN. +- Ability to disable the N1 mode capability for the underlay PLMN access with the appropriate cause code received from SNPN over underlay PLMN. + +SNPN's N3IWF impact: + +- Ability to determine it is receiving a NAS PDU from a specific IP address which is identified as a UPF of a PLMN, and include an access network information in the N2 message and send it to AMF of SNPN. + +SNPN's AMF impact: + +- The AMF uses the access network information to determine a more precise Untrusted Non-3GPP RAT type, i.e. Untrusted Non-3GPP over underlay PLMN, and rejects UE SNPN access over underlay PLMN with appropriate cause code. + +NOTE: It is up to RAN WG3 to decide how NGAP is extended. + +## 6.20 Solution #20: Access SNPN via 3GPP and N3GPP AN using same credentials and credential holder + +### 6.20.1 Introduction + +This solution addresses KI#2. + +The solution defines how the same credentials from a credential holder external to the SNPN can be leveraged for devices accessing SNPN via 3GPP and non-3GPP access network (both connected to 5GC). + +Many enterprise networks have existing deployments with non-3GPP network infrastructure (WLAN or Wireline access) using the AAA server to authenticate the end-devices. The addition of SNPN deployments could leverage the already provisioned identities and credentials to authenticate devices accessing SNPN via 3GPP and non-3GPP access networks both connecting to 5GC via a credential holder (AAA server) external to the SNPN. + +### 6.20.2 Functional Description + +- The same AAA Server (external credential holder) is used for primary authentication of a UE accessing the SNPN via a 3GPP or non-3GPP access network (e.g. WLAN or Wireline access network) re-using the architecture defined for "Credentials Holder for primary authentication and authorization" as defined in clause 5.30.2.9.2 of TS 23.501 [3]. A N3GPP device accessing the SNPN via non-3GPP access network (e.g. WLAN or Wireline access network) can also leverage the same external credential holder for authentication. +- The UE connecting via the 3GPP access or Trusted and Untrusted Non-3GPP access network, the 5G\_RG and FN-RG connected via Wireline access to the SNPN uses the same permanent identity and credentials. The existing identity and credentials used for WLAN and Wireline access authentication can be re-used for SNPN access using a SUPI in NAI format as defined in clause 28.7.2 of TS 23.503 [5]. +- The SNPN access via NG-RAN and the non-3GPP network (e.g. WLAN or Wireline access network) provides access to the same Data Network e.g. internet or enterprise network. +- Seamless mobility between the NG-RAN and the Trusted and Untrusted Non-3GPP access network, the 5G\_RG and FN-RG connected via Wireline access for accessing the SNPN is supported by this architecture. + +**Editor's note:** The scenario of UE and N3GPP device connected to 5GC via 5G-RG/FN-RG, is FFS. This scenario shall take into account the conclusion of 5WWC SID on the support of the device behind an RG. + +![Figure 6.20.2.1: Access to SNPN via 3GPP and non-3GPP access networks (both connected to 5GC) using the same credentials from an external credential holder. The diagram shows a 5G Core (5GC) connected to various access networks and external entities. At the top, an 'External Credential Holder' (AAA Server) is connected to the Network Slice Selection Function (NSSAF). Below it, a Service Based Interface (SBI) connects the NSSAF to the Network Slice Selection Function (NSSF), User Data Management (UDM), Network Exposure Function (NEF), Network Repository Function (NRF), Policy Control Function (PCF), Application Function (AF), AUSF, and NSSAF. The 5GC consists of the AMF (Access and Management Function) and SMF (Session Management Function). The AMF is connected to the (R)AN (Radio Access Network) via N2, to the W-AGF (Wireless Access Gateway Function) via N2, to the Wireline Access Network via N1, and to the 3GPP Device via Uu. The SMF is connected to the AMF via N11, to the UPF (UPF) via N4, to the N3IWF/TNGF (N3 Interworking Function/Trusted Non-3GPP Gateway Function) via N3, and to the DN (Data Network) via N6. The (R)AN is connected to the UPF via N3. The W-AGF is connected to the UPF via N3. The Wireline Access Network is connected to the UPF via N3. The Trusted/Untrusted Access Network is connected to the UPF via N9. The 3GPP Device is connected to the AMF via Uu. The N3IWF/TNGF is connected to the UPF via N3. The DN is connected to the UPF via N6.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +Figure 6.20.2.1: Access to SNPN via 3GPP and non-3GPP access networks (both connected to 5GC) using the same credentials from an external credential holder. The diagram shows a 5G Core (5GC) connected to various access networks and external entities. At the top, an 'External Credential Holder' (AAA Server) is connected to the Network Slice Selection Function (NSSAF). Below it, a Service Based Interface (SBI) connects the NSSAF to the Network Slice Selection Function (NSSF), User Data Management (UDM), Network Exposure Function (NEF), Network Repository Function (NRF), Policy Control Function (PCF), Application Function (AF), AUSF, and NSSAF. The 5GC consists of the AMF (Access and Management Function) and SMF (Session Management Function). The AMF is connected to the (R)AN (Radio Access Network) via N2, to the W-AGF (Wireless Access Gateway Function) via N2, to the Wireline Access Network via N1, and to the 3GPP Device via Uu. The SMF is connected to the AMF via N11, to the UPF (UPF) via N4, to the N3IWF/TNGF (N3 Interworking Function/Trusted Non-3GPP Gateway Function) via N3, and to the DN (Data Network) via N6. The (R)AN is connected to the UPF via N3. The W-AGF is connected to the UPF via N3. The Wireline Access Network is connected to the UPF via N3. The Trusted/Untrusted Access Network is connected to the UPF via N9. The 3GPP Device is connected to the AMF via Uu. The N3IWF/TNGF is connected to the UPF via N3. The DN is connected to the UPF via N6. + +**Figure 6.20.2.1: Access to SNPN via 3GPP and non-3GPP access networks (both connected to 5GC) using the same credentials from an external credential holder** + +## 6.20.3 Procedures + +- 0) If the SNPN supports the architecture as in Figure 6.20.2-1 and wants the UE to use the same credentials for accessing SNPN via 3GPP or Trusted and Untrusted Non-3GPP access network and wireline access network, then it is configured with the same permanent identity and credentials for primary authentication with the NG-RAN and the non-3GPP access network (Trusted and Untrusted Non-3GPP access network, and wireline access network). +- 1) A connection is established between a UE towards 5GC via the untrusted non-3GPP access using the procedures as defined in clause 4.12 of TS 23.502 [4] or a connection is established between a 3GPP capable device towards 5GC via the trusted non-3GPP access using the procedures as defined in clause 4.12a of TS 23.502 [4] or a connection is established between the UE behind 5G\_RG / FN\_RG towards 5GC via the wireline access using the procedures as defined in clause 4.10 of TS 23.316 [8]. +- 2) A connection is established between a UE and the SNPN network via NG-RAN and 5GC as defined in clause 5.30.2 of TS 23.501 [3]. + +The same credentials are used for authentication by an external credential holder (AAA server) for primary authentication of a device accessing the SNPN via 3GPP or the non-3GPP access network (e.g. WLAN or Wireline access network), re-uses the architecture defined for "Credentials Holder for primary authentication and authorization" as defined in clause 5.30.2.9.2 of TS 23.501 [3]. + +A UE may establish connection towards SNPN 5GC using either or both 3GPP and non-3GPP access network (Trusted and Untrusted Non-3GPP access network, and wireline access network) simultaneously. + +## 6.20.4 Impacts on services, entities, and interfaces + +UE: + +- Use the same permanent identity and credentials for primary authentication for accessing the SNPN via NG-RAN and the non-3GPP network (Trusted and Untrusted Non-3GPP access network, and wireline access network). + +No other impacts in the UE, NG-RAN, and 5GC are identified. + +## 6.21 Solution #21: Support for NSWOF in SNPN + +### 6.21.1 Introduction + +This solution addresses KI#2. + +The solution defines how the same credentials can be leveraged for devices accessing SNPN via NG-RAN and 5GC, and non-3GPP access network using Non-Seamless WLAN Offload Function (NSWOF). If a device is connected via WLAN for the non-3GPP access network, NSWOF interfaces to the WLAN access network using the SWa interface as defined in TS 23.402 [9], and interfaces to the AUSF using the Nausf Service Based Interface (SBI) performing the protocol translation and the AUSF discovery. + +If a device is connected via a residential gateway (e.g. FN-RG or 5G-RG), NSWOF support for wireline access that is being addressed in Rel-18 5WWC (e.g. Solution#22 in TR 23.700-17 [18]) is assumed and conclusion of TS 23.700-17 [18] will be taken into account and possible alignment will be considered. For example, NSWOF of wireline access interfaces to a 5G-RG using a SWa interface as referred in TR 23.700-17 [18]. Based on this solution, the device connecting to 5G-RG is authenticated and authorized by the HPLMN of this device. The authentication procedure does not require 5GS registration because it is based on the NSWO authentication procedure specified in Annex S of TS 33.501 [10]". + +### 6.21.2 Functional Description + +- The architecture to support authentication via NSWOF will be as defined in clause 4.2.15 of TS 23.501 [3]. +- The procedures for AUSF discovery and selection by NSWOF will be as defined in clause 6.3.4 of TS 23.501 [3]. +- The functionality of NSWOF and the procedures applied for supporting WLAN connection or wireline connection using 5GS credentials for Non-seamless WLAN offload may be as defined in TS 33.501 [10] (e.g. in Annex S). +- When the UE wishes to use 5G NSWO to connect to the non-3GPP network (e.g. WLAN or Wireline access network) using its 5GS credentials associated with the SNPN, the NAI format for 5G NSWO access used will be as defined in clauses 28.7.6 and 28.7.7 of TS 23.503 [5]. +- The SNPN and the non-3GPP network (e.g. WLAN or Wireline access network) provides access to the same Data Network e.g. internet or enterprise network +- Seamless mobility between the SNPN and the non-3GPP network (e.g. WLAN or Wireline access network) is not supported by this architecture. + +![Figure 6.21.2.1: Support for NSWOF for SNPn. This diagram illustrates the network architecture for a Single Network Slice Per Operator (SNPn) that supports Non-3GPP Wireless Offload (NSWOF). The architecture is divided into three main horizontal layers by dashed lines. The top layer contains Service Based Interfaces (SBIs) between various Network Functions (NFs): NSS (Nnssf), UDM (Nudm), NEF (Nnef), NRF (Nnrf), PCF (Npcf), AF (Naf), AUSF (Nausf), and NSSAAF (Nnssf). A dashed line labeled N60 is shown above this layer. The middle layer, labeled SNPn, contains the AMF (N1, N2, N11, Namf), SMF (N4, N11, Nsmf), (R)AN (N2, N3, Uu), UPF (N3, N4, N6, N9), and DN (N6). The bottom layer contains the 3GPP Device (Uu, N1) and two non-3GPP access networks: WLAN Access Network and Wireline Access Network. Both non-3GPP networks connect to the UPF via SWa interfaces and are managed by a 5G RG and FN RG. The 3GPP Device connects to the (R)AN via Uu and to the 5G RG via N1. The NSWO (Non-3GPP Wireless Offload) entity is shown at the top right, connected to the AUSF via N60 and to the 5G RG via SWa.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +Figure 6.21.2.1: Support for NSWOF for SNPn. This diagram illustrates the network architecture for a Single Network Slice Per Operator (SNPn) that supports Non-3GPP Wireless Offload (NSWOF). The architecture is divided into three main horizontal layers by dashed lines. The top layer contains Service Based Interfaces (SBIs) between various Network Functions (NFs): NSS (Nnssf), UDM (Nudm), NEF (Nnef), NRF (Nnrf), PCF (Npcf), AF (Naf), AUSF (Nausf), and NSSAAF (Nnssf). A dashed line labeled N60 is shown above this layer. The middle layer, labeled SNPn, contains the AMF (N1, N2, N11, Namf), SMF (N4, N11, Nsmf), (R)AN (N2, N3, Uu), UPF (N3, N4, N6, N9), and DN (N6). The bottom layer contains the 3GPP Device (Uu, N1) and two non-3GPP access networks: WLAN Access Network and Wireline Access Network. Both non-3GPP networks connect to the UPF via SWa interfaces and are managed by a 5G RG and FN RG. The 3GPP Device connects to the (R)AN via Uu and to the 5G RG via N1. The NSWO (Non-3GPP Wireless Offload) entity is shown at the top right, connected to the AUSF via N60 and to the 5G RG via SWa. + +Figure 6.21.2.1: Support for NSWOF for SNPn + +### 6.21.3 Procedures + +If the SNPn supports the architecture as in Figure 6.21.2-1, the UE can use the same permanent identity and credentials that are used for primary authentication with the SNPn to connect to the non-3GPP network (e.g. WLAN or Wireline access network) using the 5G NSWOF that interacts with AUSF within the 5GC of SNPn network to authenticate the UE. + +- 1) A connection is established between a UE and the SNPn network via NG-RAN and 5GC as defined in clause 5.30.2 of TS 23.501 [3]. +- 2) A connection is established between a UE and the non-3GPP network (e.g. WLAN or Wireline access network) that uses the same permanent identity and credentials that are used for primary authentication with the SNPn using the 5G NSWOF as defined in Annex S of TS 33.501 [10]. + +**Editor's note:** A procedure of NSWO for wireline and handling of N3GPP devices behind the RG will be dependent on the conclusion of TR 23.700-17 [18] and possible alignment will be considered. + +The UE may establish connection towards either or both the non-3GPP network (e.g. WLAN or Wireline access network) and SNPn via NG-RAN and 5GC simultaneously. + +### 6.21.4 Impacts on services, entities, and interfaces + +UE: + +- Shall be able to support NSWO authentication (as defined in Annex S of TS 33.501 [10]) using the same permanent identity and credentials for primary authentication in SNPN via NG-RAN and 5GC, and the non-3GPP network (e.g. WLAN or Wireline access network). + +RG: + +- Shall be able to support NSWO authentication (e.g. leveraging the NSWO architectures defined for wireline access in Rel-18 5WWC) using the same permanent identity and credentials for primary authentication in SNPN via NG-RAN and 5GC, and the non-3GPP network (e.g. WLAN or Wireline access network). + +No other impacts in the UE, NG-RAN, and 5GC are identified. + +## 6.22 Solution #22: Hosting network to provide localized service based on default credentials + +### 6.22.1 Introduction + +The solution addresses key issue #3 Enabling SNPN as hosting network for providing access to localized services. + +The solution aims to enable hosting network to provide the localized service for the UE. + +### 6.22.2 Functional Description + +In this solution, it is assumed that UE has default credentials that can be used in the hosting network. Hosting network broadcasts a dedicated Hosting networking service indication to show that this NPN can provide hosting networking for localized services. + +The localized services information are pre-configured in AMF of hosting network. + +For the network selection aspect, there are following assumptions: + +- 1) If there is some service agreement between hosting network and home network, so that the UE can be successfully authenticated by the hosting network by using credentials of home network. Automatic network selection is performed +- 2) If there is no service agreement between hosting network and home network, the hosting network performs authentication by using the UE's default credentials. After successful authentication, hosting network can allow the UE to initiate restricted PDU session to the localized service, and may perform secondary authentication during the PDU session establishment. Manual network selection is performed. + +**Editor's note:** Details of the restricted PDU session are FFS. + +**Editor's note:** the nature of the default credentials and how to perform the authentication by using the default credentials in the hosting network is FFS. How to pre-configure the default credentials is FFS. Where the subscription corresponding to the default credentials is stored is FFS. Whether further security is needed should depend on SA WG3. + +## 6.22.3 Procedures + +![Sequence diagram illustrating the procedure for a hosting network providing localized service. The diagram shows interactions between UE, gNB, AMF, UDM (grouped as 'Hosting network'), localized Service, and Home network. The steps are: 0. broadcasting hosting network service indication; 1. Network selection; 2. registration request [UE ID, hosting network Service indication]; 3. registration request [UE ID, hosting network Service indication]; 4. authentication & authorization; 5. determine to provide hosting network service; 6. registration accept [configuration for localized services]; 7. registration accept [configuration for localized services]; 8. UE triggers to initiate PDU session for certain Localized services.](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph Hosting network + participant gNB + participant AMF + participant UDM + end + participant LS as localized Service + participant HN as Home network + + Note left of UE: 0 broadcasting hosting network service indication + Note left of UE: 1, Network selection + UE->>gNB: 2, registration request [UE ID, hosting network Service indication] + gNB->>AMF: 3, registration request [UE ID, hosting network Service indication] + Note right of AMF: 4, authentication & authorization + Note right of AMF: 5, determine to provide hosting network service + AMF->>gNB: 6, registration accept [configuration for localized services] + gNB->>UE: 7, registration accept [configuration for localized services] + Note right of UE: 8, UE triggers to initiate PDU session for certain Localized services + +``` + +Sequence diagram illustrating the procedure for a hosting network providing localized service. The diagram shows interactions between UE, gNB, AMF, UDM (grouped as 'Hosting network'), localized Service, and Home network. The steps are: 0. broadcasting hosting network service indication; 1. Network selection; 2. registration request [UE ID, hosting network Service indication]; 3. registration request [UE ID, hosting network Service indication]; 4. authentication & authorization; 5. determine to provide hosting network service; 6. registration accept [configuration for localized services]; 7. registration accept [configuration for localized services]; 8. UE triggers to initiate PDU session for certain Localized services. + +**Figure 6.22.3-1: Hosting network providing localized service** + +0. SNPN network broadcasts a Hosting Network Service Indication, to say that the hosting network can support the UE to access to localized service. +1. UE performs network selection and selects the hosting network, based on the pre-configuration and broadcasting information from hosting network. + +If there is no service agreement between hosting network and home network, manual network selection is performed. + +2. UE initiates the registration request with UE's information and Hosting Network Service Indication to gNB. +3. gNB selects the AMF that supporting Hosting Network Service based on the indication in step 2. +4. AMF performs the authentication and authorization by using the credentials from home network if there is some service agreement between hosting network and home network. + +AMF performs authentication and authorization by using the default credentials pre-configured in the UE, when there is no service agreement between hosting network and home network. + +**Editor's note:** What exactly are the "hosting network default credentials", how they are used and who/how they are configured in the UE is FFS. + +5. AMF sends UE the localized services information that can be provided by the hosting network when AMF determines to accept UE's request. The localized information may include IP address/FQDN/DNN of the localized service. +- 6-7. AMF sends the registration accept to UE via gNB, including localized service information. +8. UE initiates the PDU Session to dedicated DNN that can provide expected localized service, if the expected localized service is in the received localized list if the list is available. + +## 6.22.4 Impacts on services, entities, and interfaces + +Network impact: + +- AMF configured with localized service information. + +- gNB broadcasts the Hosting Network Service Indication. + +Editor's note: Default credential aspects, restricted PDU session aspects are FFS. + +## 6.23 Solution #23: Solution for obtaining hosting network selection and access information - PNI-NPN + +### 6.23.1 Introduction + +This solution solves several requirements listed in Key Issue#4. + +This solution is used in the scenario when the hosting network is an PNI-NPN. + +When a UE accesses localized service, Network Slice-Specific Authentication and Authorization or Secondary authentication/authorization is performed between the UE and the Localized service provider. + +In this solution, a UE receives hosting network selection and access information from its home PLMN, after the UE subscribes the Localized service from the Localized service provider. + +The hosting network selection and access information extends the current CAG information (e.g. Allowed CAG ID list) by including validity condition information when and where the PNI-NPN provides service. + +### 6.23.2 Functional Description + +In this solution, the UE subscribed service from the Localized service provider (LSP). The UE is provisioned with credential which is used to access the Localized service using current mechanism defined in clause 5.39 of TS 23.501 [3]. The credential is used during Network Slice-Specific Authentication and Authorization or Secondary authentication/authorization when the UE accesses localized service. The UE may obtain the PVS address of the LSP with some out of 3GPP scope mechanisms, e.g. from the ticket the user bought for a football match. + +The LSP notifies the UE's home PLMN that the UE is already provisioned with the corresponding credential for accessing the Localized service. The UE's UDM updates UE's subscription with the CAG ID and optionally DNN or S-NSSAI corresponding to the Localized service provider. The UDM updates UE's configuration using UE Configuration Update procedure. + +In the scenario of hosting network is a PNI-NPN, the Hosting Network Selection and Access Information consists the following information: + +- Hosting Network Identifier, e.g. CAG ID and corresponding PLMN ID. +- The time condition information when the hosting network provides access service. +- The location condition information where the hosting network provides access service. + +The UE selects a hosting network when the time and location condition information is satisfied. + +### 6.23.3 Procedures + +![Sequence diagram illustrating the procedure for UE receiving hosting network selection and access information. The diagram shows interactions between the UE, AMF, UDM, and NEF within the Home Network, and the LSP App within the Localized service provider (LSP).](1c79f31a718d63814feb28ab46f64f19_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph Home Network + participant AMF + participant UDM + participant NEF + end + participant LSP as Localized service provider(LSP) + participant LSPApp as LSP App + + Note left of UE: 1. UE subscribed with LSP for its service and is provisioned with credentials for accessing the service + LSPApp->>NEF: 2. Successful provision notification + NEF->>UDM: 3. Successful provision notification + UDM->>AMF: 4. Allowed CAG ID list, with validity conditions + AMF->>UE: 5. Allowed CAG ID list, with validity conditions + Note left of UE: 6. PNI-NPN selection + +``` + +Sequence diagram illustrating the procedure for UE receiving hosting network selection and access information. The diagram shows interactions between the UE, AMF, UDM, and NEF within the Home Network, and the LSP App within the Localized service provider (LSP). + +**Figure 6.23.3-1: UE receives hosting network selection and access information** + +1. The UE subscribes a localized service from the Localized service provider (LSP). The UE is provisioned with credential which is used to access the Localized service using current mechanism defined in clause 5.39 of TS 23.501 [3]. + +NOTE 1: The UE may obtain the PVS address of the LSP with some out of 3GPP scope mechanisms, e.g. from the ticket the user bought for a football match. + +2. The LSP App sends Nnef\_ParameterProvision\_Create message to the NEF of the UE's home PLMN, including GPSI of the UE, Successful provision indication and validity condition of the Localized service. One of DNN, S-NSSAI, or CAG ID and PLMN ID corresponding to the Localized service is also included. The Successful provision notification indicates that the UE is provisioned with credential for accessing the Localized service. The validity condition of the Localized service includes time and location condition information of the Localized service. + +NOTE 2: How the LSP App can obtain the home network of the UE is out of 3GPP scope, for example, from the UE's mobile phone number. + +3. The NEF of the home network of the UE sends Nudm\_ParameterProvision\_Create to the UDM of the home network of the UE, including GPSI of the UE, the Successful provision indication, validity condition of the Localized service. One of DNN, S-NSSAI, or CAG ID and PLMN ID corresponding to the Localized service is also included if received in step 2. + +The UDM updates the UE's subscription by adding the DNN or the S-NSSAI corresponding to the Localized service. The UDM also updates the UE's Allowed CAG ID list by adding the CAG ID and PLMN ID corresponding to the Localized service with validity condition. + +4. The UDM sends the updated Allowed CAG ID list and optionally the updated DNN, S-NSSAI to the AMF. +5. The AMF sends the updated Allowed CAG ID list and optionally the updated DNN, S-NSSAI to the UE. + +Step 4-5 can use the UE Configuration Update procedure. + +6. For automatically network selection, and manual network selection, the UE performs the existing mechanism as defined in TS 23.122 [6] with the following difference: the hosting network ID (i.e. CAG ID) in the Allowed CAG ID list is taken into account when the corresponding time and location condition information is satisfied. + +## 6.23.4 Impacts on services, entities, and interfaces + +UE impact: + +- Ability to receive Allowed CAG ID list with validity condition corresponding to a CAG ID. +- Ability to perform CAG selection based on the received Hosting Network Selection and Access Information. + +Home Network impact: + +- NEF: Ability to receive Successful provision indication and one of DNN, S-NSSAI, or CAG ID and PLMN ID corresponding to the Localized service, validity condition of the Localized service from the local service provider. +- UDM: Ability to receive Successful provision indication and one of DNN, S-NSSAI, or CAG ID and PLMN ID corresponding to the Localized service, validity condition of the Localized service from the NEF and updates UE's subscription accordingly. + +## 6.24 Solution #24: Localized service data provisioning via UDR + +### 6.24.1 Introduction + +This solution addresses requirements listed in Key Issue #4. It proposes to use network exposure for provisioning network with information related to localized service and use UE policy for delivering the information to UE. + +This solution covers the function described in solution #7 step H4. + +### 6.24.2 Functional Description + +There are many characteristics to describe a localized service, e.g.: + +- the name and identifier of the localized service; +- time validity; +- location validity; +- a service provider group identifier for end users who will be offered with localized service; +- information related to hosting network(s), such as network identity, cost and quality of the localized service, S-NSSAI/DNN to be used for accessing the localized service, valid credential types, etc. + +It is assumed that UE is usually registered in a serving network prior to registering to hosting network for localized service. Localized service provider can have business relationship with multiple hosting network operators, so that there could be more than one hosting network providing access to the localized service. After the interactions between localized service provider and the hosting network operators (see solution #7 step H1 and H2), localized service provider has gathered all the characteristics of a localized service and is able to provision the data to the UE's serving network (e.g. HPLMN, VPLMN). + +When the serving network is provisioned with data related localized service, UE can obtain the data via UE policy and use the data to perform selection of hosting network and localized service. + +NOTE: How does the UE make use of the localized service data is not discussed in this solution. + +## 6.24.3 Procedures + +### 6.24.3.1 Provisioning of non-UE specific localized service data to networks + +![Sequence diagram showing the provisioning of non-UE specific localized service data to networks. The diagram involves three entities: UDR, NEF, and AF. The sequence of messages is: 1. Creation of the AF request (internal to AF), 2. Nnef_ServiceParameter_Create / Update / Delete Request (AF to NEF), 3. Nudr_DM_Create/Update/Delete Request (NEF to UDR), 4. Nudr_DM_Create/Update/Delete Response (UDR to NEF), 5. Nnef_ServiceParameter_Create / Update / Delete Response (NEF to AF).](e4bbddb050930c71ba62996a2e194549_img.jpg) + +``` +sequenceDiagram + participant AF + participant NEF + participant UDR + Note right of AF: 1. Creation of the AF request + AF->>NEF: 2. Nnef_ServiceParameter_Create / Update / Delete Request + NEF->>UDR: 3. Nudr_DM_Create/Update/Delete Request + UDR-->>NEF: 4. Nudr_DM_Create/Update/Delete Response + NEF-->>AF: 5. Nnef_ServiceParameter_Create / Update / Delete Response +``` + +Sequence diagram showing the provisioning of non-UE specific localized service data to networks. The diagram involves three entities: UDR, NEF, and AF. The sequence of messages is: 1. Creation of the AF request (internal to AF), 2. Nnef\_ServiceParameter\_Create / Update / Delete Request (AF to NEF), 3. Nudr\_DM\_Create/Update/Delete Request (NEF to UDR), 4. Nudr\_DM\_Create/Update/Delete Response (UDR to NEF), 5. Nnef\_ServiceParameter\_Create / Update / Delete Response (NEF to AF). + +**Figure 6.24.3.1-1: Provisioning of non-UE specific localized service data to networks** + +The above figure reuses the signalling flow defined in clause 4.15.6.7 of TS 23.502 [4], with the following considerations: + +- AF is an external party to the network, which has business agreement with the localized service provider. The AF represents the localized service provider who has gathered all the characteristics of a localized service as described in clause 6.24.2. +- The name/identifier of the localized service can be used as service description in the AF request to NEF. +- Time/location validity and information related to hosting network(s) are the localized service specific information which will be provisioned to serving network and delivered to UE. +- Nnef\_ServiceParameter\_Create service operation is not-UE specific and therefore does not include any specific UE Identity or External Group Identifier. +- Optionally, a service provider group identifier can be allocated by the AF for identifying a determined group of end users who will be offered with localized service, and thus be provided with the localized service data. +- AF can invoke this procedure with multiple networks that have business agreement with the localized service provider. +- The localized service data is stored in UDR as "Application Data". + +### 6.24.3.2 Delivering localized service data to the UE via UE policy + +![Sequence diagram showing the procedure for delivering localized service data to the UE via UE policy. The diagram involves six lifelines: UE, (R)AN, AMF, PCF, UDR, and UDM. The process starts with 0. UE registration. Step 1: End user triggers the demand of the localized service. Step 2: UL NAS Transport from UE to AMF containing a UE Policy container. Step 3a: Npcf_UEPolicyControl_Create Request from AMF to PCF. Step 3b: Namf_Communication_N1MessageNotify from AMF to PCF. Step 4: Nudr_DM_Query Request from PCF to UDR. Step 5: Nudr_DM_Query Response from UDR to PCF. Step 6a: Npcf_UEPolicyControl_Create Response from PCF to AMF, with a note that steps 3-5 are defined in clause 4.2.4.3 of 23.502. Step 6b: UE Policy delivery procedure from AMF to UE, with a note that this is defined in clause 4.2.4.3 of 23.502.](28f2f470a7b2446ae5f525123534383c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant AMF + participant PCF + participant UDR + participant UDM + + Note over UE, UDM: 0. UE registration + Note left of UE: 1. End user triggers the demand of the localized service + UE->>AMF: 2. UL NAS Transport, [UE Policy container(request UE Policy of localized service, and localized service identifier)] + AMF->>PCF: 3a. Npcf_UEPolicyControl_Create Request + AMF->>PCF: 3b. Namf_Communication_N1MessageNotify + PCF->>UDR: 4. Nudr_DM_Query Request + UDR-->>PCF: 5. Nudr_DM_Query Response + Note right of AMF: 6a. Npcf_UEPolicyControl_Create Response and step 3-5 in clause 4.2.4.3 of 23.502 + AMF-->>UE: 6b. UE Policy delivery procedure defined in clause 4.2.4.3 of 23.502 + +``` + +Sequence diagram showing the procedure for delivering localized service data to the UE via UE policy. The diagram involves six lifelines: UE, (R)AN, AMF, PCF, UDR, and UDM. The process starts with 0. UE registration. Step 1: End user triggers the demand of the localized service. Step 2: UL NAS Transport from UE to AMF containing a UE Policy container. Step 3a: Npcf\_UEPolicyControl\_Create Request from AMF to PCF. Step 3b: Namf\_Communication\_N1MessageNotify from AMF to PCF. Step 4: Nudr\_DM\_Query Request from PCF to UDR. Step 5: Nudr\_DM\_Query Response from UDR to PCF. Step 6a: Npcf\_UEPolicyControl\_Create Response from PCF to AMF, with a note that steps 3-5 are defined in clause 4.2.4.3 of 23.502. Step 6b: UE Policy delivery procedure from AMF to UE, with a note that this is defined in clause 4.2.4.3 of 23.502. + +**Figure 6.24.3.2-1: Delivering localized service data via UE policy** + +The procedure to deliver the localized service data towards UE is described as below: + +0. UE has registered in a network, and optionally UE policy association is established and PCF has subscribed to be notified of the reception of the UE Policy container (see step 0a in clause 4.2.4.3 of TS 23.502 [4]). + +During the registration procedure, AMF fetches the subscription data from UDM and verifies that UE is allowed to use localized services. Then, AMF indicates to the UE there is support of provisioning localized service data via successful registration. + +1. End user is motivated by service provider to seek for localized service, for example scan a QR code, or login a web page, etc. +2. Based on the knowledge that the current serving network supports localized service data provisioning, the UE requests such data from the serving network reusing the procedure defined in clause 6.2.4 of TS 23.287 [13]. + +The UE's request includes information for the network to determine what localized service information to provide to the UE e.g. service identifier associated with the localized service, and/or a "filter" e.g. free text name of localized service, location, time, service provider group identifier. + +NOTE 1: The information included in the UE request message is obtained via mechanisms outside of 3GPP scope. + +- 3a. If there is no UE policy association established, AMF sends Npcf\_UEPolicyControl\_Create request to establishes UE policy association with PCF, including the UE policy container. +- 3b. If there is UE policy association has been established and PCF has subscribed to be notified of the reception of the UE policy container, AMF sends the Namf\_Communication\_N1MessageNotify request to the PCF including the UE Policy Container received from UE. +4. PCF queries UDR for the data stored for localized service, based on the information provided by the UE (e.g. localized service identifier, a "filter", etc). + +NOTE 2: If the current serving network is different than the home network, in addition to localized service data received from the PCF in the home network, the PCF in the serving network can also provide the UE with localized service data based on information stored in the serving network UDR. + +5. PCF receives the localized service data from the UDR. The data is provisioned and stored in UDR as described in clause 6.24.3.1. + +PCF can use service provider group identifier to verify if UE belongs to the correct group of receiving the localized service. + +- 6a. If step 3a is executed, then PCF accepts the UE policy association establishment, and then steps 3-5 in clause 4.2.4.3 of TS 23.502 [4] are used to deliver the UE policy to UE. + +- 6b. If step 3b is executed, then PCF provisions the UE with the localized service data as part of new UE Policies for localized services, re-using procedure defined in clause 4.2.4.3 of TS 23.502 [4]. + +## 6.24.4 Impacts on services, entities, and interfaces + +AF/NEF/UDR: + +- Support provisioning and storing of localized service data. + +UE/PCF: + +Support UE triggered localized service data delivery via UE policy delivery procedure. + +AMF: + +- Indicate to the UE the network support provisioning of localized service data via NAS. + +UDM: + +- Indicate to AMF that UE is allowed to use localized services via subscription data. + +## 6.25 Solution #25: Temporary network reselection for localized service support + +### 6.25.1 Introduction + +This solution addresses the scenario of when the UE has subscribed to a localized service in a hosting network and a temporary network reselection procedure from a home/or other network to a hosting network is needed. It describes a temporary network reselection procedure that enables the UE to enjoy localized services and covers Key Issue #4 and #6. + +This solution details the step H5 and H8 in solution #7. + +### 6.25.2 Functional Description + +The solution assumes that the UE is aware of which hosting network to use for the desired localized service. This solution facilitates a temporary change in the network priorities for network selection or a temporary change of SNPN access mode. Additionally, it enables the home network (i.e. HPLMN, subscribed SNPN) to authorize the UE to use this reselection procedure. There are criteria associated with the temporary reselection procedure (e.g. the start times and end times), so that the temporary reselection procedure is only applicable when the criteria are met, otherwise the existing network selection procedures defined in TS 23.122 [6] apply. + +It would enable: + +- the UE to perform a network reselection to the hosting network from a network which was selected based on the existing network selection procedures as described in TS 23.122 [6] before the beginning of the localized service. + +- the UE to leave the hosting network and select a new network using existing network selection procedures as described in TS 23.122 [6] after the localized service is stopped. +- the UE to switch the SNPN access mode. + +## 6.25.3 Procedures + +### 6.25.3.1 Overview of Temporary Network Reselection (TNR) to enable localized services + +![Sequence diagram illustrating the Temporary Network Reselection (TNR) procedure between a UE and a Home Network.](a2bbc82e5c6132b0870bd70f6657f919_img.jpg) + +``` +sequenceDiagram + participant UE + participant Home Network + Note left of UE: 1. UE is registered in a network. + Note left of UE: 2. UE selects a localized service in the hosting network. + Note right of Home Network: 3. Enabling of temporary network reselection procedure. + Note left of UE: 4. UE activates temporary network reselection. + Note left of UE: 5. UE starts and stops using the localized service. + Note left of UE: 6. UE deactivates temporary network reselection. +``` + +The diagram is a sequence diagram with two lifelines: UE and Home Network. The sequence of events is as follows: + +- UE is registered in a network. +- UE selects a localized service in the hosting network. +- Enabling of temporary network reselection procedure (indicated by a message from Home Network to UE). +- UE activates temporary network reselection. +- UE starts and stops using the localized service. +- UE deactivates temporary network reselection. + +Sequence diagram illustrating the Temporary Network Reselection (TNR) procedure between a UE and a Home Network. + +**Figure 6.25.3.1-1: Temporary Network Reselection (TNR) procedure to enable localized services** + +The following steps describe how to use Temporary Network Reselection (TNR) procedure to enable localized services as shown in Figure 6.25.3.1-1: + +1. The UE is already registered in a network, which was selected based on existing network selection procedures defined in TS 23.122 [6]. +2. The UE selects a localized service (e.g. the user selects a Localized service, the application requests a Localized service) and is aware of which hosting network to use for this localized service. + +NOTE 1: How the UE gets aware of which hosting network to use for the localized service is assumed to be described in other solutions. + +3. The UE and the home network (i.e. HPLMN or subscribed SNPN) decides to enable TNR procedure. + +The home network can authorize its subscriber to use the TNR, e.g.: + +- i. via pre-authorization for the UE based on UE configuration; or +- ii. via UE request as described in clause 6.25.3.2. + +4. The UE stores the current registered network, and activates TNR when the criteria associated with the TNR are met. + +The TNR can be achieved, in one way, by reprioritizing (or reordering) the list of networks that are made available to the UE, with the hosting network as the top priority. + +Another way is to avoid the automatic network selection to the higher priority networks, e.g. by avoiding triggering of periodic checks for higher prioritized networks when the UE is in a VPLMN (e.g. hosting network is a PNI-NPN which is different than the serving PLMN and has a lower priority than the serving PLMN). + +The TNR can also trigger the UE to switch the SNPN access mode if it is needed (e.g. hosting network is an SNPN while the UE is currently registered in a PLMN). + +The criteria associated with the authorized TNR can include, e.g. start/stop time, location, availability of home network services, etc. + +5. The UE starts and stops using the localized service. +6. The UE deactivates the TNR when the criteria are no longer met, and selects a new network based on the existing network selection procedures defined in TS 23.122 [6]. + +NOTE 2: It is up to CT1 to determine whether and how the previous registered network stored in step 4 is used in the network selection after UE deactivates the TNR. + +### 6.25.3.2 Home network authorization via Steering of Roaming (SOR) procedure + +![Sequence diagram for Home network authorization via Steering of Roaming (SOR) procedure. The diagram shows interactions between UE, VPLMN or HPLMN AMF, HPLMN UDM/AUSF, and SOR-AF. The process starts with the UE already registered. The UE sends a REGISTRATION REQUEST with GUTI and TNR. The AMF sends a Nudm_UECM_Update to the UDM. The UDM makes a decision to send SoR info based on TNR, then sends an Nsoraf_SoR_Get_Request to the SOR-AF. The SOR-AF responds with Nsoraf_SoR_Get response and secures the information. The UDM then sends a Nudm_SDM_Notify to the AMF. The AMF sends a REGISTRATION ACCEPT to the UE. The UE performs a steering of roaming information security check. If the security check fails or the UE is configured to receive steering of roaming information but did not receive it, then perform PLMN selection procedure and end the procedure. Otherwise, the UE sends a REGISTRATION COMPLETE to the AMF. The AMF sends a Nudm_SDM_InfoRequest to the UDM. The UDM sends an Nsoraf_SoR_Info request to the SOR-AF. Finally, the UE may perform PLMN selection procedure if higher priority PLMN is available.](114902bbeea56bda01b64b43fad41920_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF as VPLMN or HPLMN AMF + participant UDM as HPLMN UDM/AUSF + participant SOR-AF + + Note over UE, AMF: 0. UE is already registered via AMF in VPLMN or HPLMN + UE->>AMF: 1. REGISTRATION REQUEST (GUTI, TNR) + AMF->>UDM: 2. Nudm_UECM_Update (SUPI, TNR) + Note right of UDM: 3a. Decision to send SoR info (based on TNR) + UDM->>SOR-AF: 3b. Nsoraf_SoR_Get Request (SUPI, TNR) + SOR-AF-->>UDM: 3c. Nsoraf_SoR_Get response + Note right of UDM: 3d. Securing information + UDM->>AMF: 4. Nudm_SDM_Notify (SUPI, SoRInfo) + AMF-->>UE: 6. REGISTRATION ACCEPT + Note left of UE: 7. Steering of roaming information security check + UE-->>AMF: REGISTRATION COMPLETE + Note left of UE: 8. If the security check fails or the UE is configured to receive steering of roaming information but did not receive it, then perform PLMN selection procedure and end the procedure + UE-->>AMF: REGISTRATION COMPLETE + UE-->>AMF: 9. REGISTRATION COMPLETE + AMF-->>UDM: 10. Nudm_SDM_InfoRequest + UDM-->>SOR-AF: 10a. Nsoraf_SoR_Info request + Note left of UE: 11. UE may perform PLMN selection procedure if higher priority PLMN is available + +``` + +Sequence diagram for Home network authorization via Steering of Roaming (SOR) procedure. The diagram shows interactions between UE, VPLMN or HPLMN AMF, HPLMN UDM/AUSF, and SOR-AF. The process starts with the UE already registered. The UE sends a REGISTRATION REQUEST with GUTI and TNR. The AMF sends a Nudm\_UECM\_Update to the UDM. The UDM makes a decision to send SoR info based on TNR, then sends an Nsoraf\_SoR\_Get\_Request to the SOR-AF. The SOR-AF responds with Nsoraf\_SoR\_Get response and secures the information. The UDM then sends a Nudm\_SDM\_Notify to the AMF. The AMF sends a REGISTRATION ACCEPT to the UE. The UE performs a steering of roaming information security check. If the security check fails or the UE is configured to receive steering of roaming information but did not receive it, then perform PLMN selection procedure and end the procedure. Otherwise, the UE sends a REGISTRATION COMPLETE to the AMF. The AMF sends a Nudm\_SDM\_InfoRequest to the UDM. The UDM sends an Nsoraf\_SoR\_Info request to the SOR-AF. Finally, the UE may perform PLMN selection procedure if higher priority PLMN is available. + +**Figure 6.25.3.2-1: Home network authorizes Temporary Network Reselection (TNR)** + +The temporary network reselection (TNR) can be requested by the UE and be authorized by the home network, reusing Steering of Roaming (SOR) procedure defined in TS 23.122 [6] with additions listed below. + +Figure 6.25.3.2-1 shows PLMN as an example of the home network. The same principle applies if home network is SNPN. + +0. The UE is already registered via an AMF in a VPLMN or in the HPLMN. This implies that the AMF has already registered in UDM, has obtained subscription data for the UE and subscribed to subscription data updates including possible updates of SOR information. +1. The UE requests an authorization of TNR procedure by including a TNR information within a NAS message, e.g. a Registration Request. The TNR information can be sent as a separate IE or in a new transparent container for the HPLMN UDM (i.e. all AMFs would simply forward the transparent container). + +NOTE: Whether and how the TNR information is protected by UE before sending to AMF is up to SA WG3. + +The TNR information in the UE request includes, e.g.: + +- i. Requested start and stop time for permission to use TNR procedure. + - ii. The selected localized service identity. + - iii. The selected hosting network identity. +2. Based on the TNR information received from the UE, the AMF decides to update its registration in UDM to provide the UE requested TNR information to UDM. +3. Based on the TNR information received from the AMF, the UDM decides to request the SOR-AF for authorizing the TNR requested by the UE (step 3a and 3b). The UDM does this even if the UE is registered in the HPLMN. + +The SOR-AF updates the SOR information for the UE if needed according to SOR-AF decision (step 3c) and protects the SOR info via AUSF (step 3d). The SOR information provided by the SOR-AF includes the TNR authorization in the SOR-AF. This can be in the form of, e.g. + +- i. An indication that the UE is authorized for TNR. Based on this indication, UE can temporarily suspend the automatic network selection mechanism which is according to the available SOR list stored in the UE, or temporarily switch SNPN access mode. +- ii. An updated or new list of prioritized PLMNs or SNPNs including the hosting network selected by the UE with the highest priority. +- iii. Conditions for UE to activate TNR, e.g. authorized start/stop time, location, indication of whether possible to access home network using N3IWF via the hosting network, indication of home routed architecture exists between home network and the hosting network, etc. + +UE determines whether automatic network selection is possible, based on the indications described above and the UE's own capabilities (e.g. dual radio capability, access home network using N3IWF via hosting network). + +In order to avoid overload of the home network when UE leaves the hosting network(Key Issue #6), the UDM/SOR-AF can apply an offset to the authorized start/stop time in the authorized TNR sent to UE. + +4. The UDM provides the authorization decision to the UE via the AMF after protection via AUSF. +- 6-10. As defined in clause C.2 of TS 23.122 [6]. +11. The UE applies the TNR as authorized by the SOR-AF when conditions are met. If the SOR-AF is used and the SOR-AF keeps track of the conditions associated with the authorized TNR, then SOR-AF can issue an update of the SOR information to the UE as described by Figure C.3.1 and Figure C.6.1 of TS 23.122 [6]. + +## 6.25.4 Impacts on services, entities, and interfaces + +UE: + +- Request temporary network reselection via NAS message. +- Temporarily apply temporary network reselection, using updated or new list of prioritized networks with hosting network as top priority. +- Temporarily avoid periodic check of higher prioritized networks. +- Temporarily switch SNPN access mode. + +UDM/SOR-AF: + +- Authorize the UE request for temporary network reselection. +- Update the authorized temporary network selection with UE. +- Pre-authorize the UE to use temporary network reselection, based on UE configuration. + +AMF: + +- Forward the UE request for temporary network reselection to UDM. + +## 6.26 Solution #26: Enable UE to query localized services information from the hosting network for service discovery + +### 6.26.1 Introduction + +As illustrated in the Key #4, UE need to be able to discover the hosting network and the localized service being hosted by this network. One aspect of KI #4 is to identify the mechanism to provisioning UE with appropriate localized service information. Considering we need to support the cases which the UE may or may not have prior subscription or information about the hosting network and the localized service, this solution is to propose an information query/response mechanism by enhancing the registration procedure to allow UE to query the localized service information from the hosting network which UE may or may have subscription with. + +The localized service information may include local service ID or name, service availability (e.g. time, duration and location), local service captive portal address, information about available local hosting networks associated with the local service as described in solution #12, so on. UE can use the information for selecting and accessing the localized service and hosting network by the user's request. + +NOTE: This solution does not intent to define the detail of the localized service information, but it focuses on how to deliver the information from network to UE by the user's request. + +### 6.26.2 Functional Description + +This solution proposes to allow UE to use registration procedure to query the localized service information from the AMF of the hosting network. The local hosting network may configure a designated AMF to handle the UE access for localized service and store the localized service information. The localized service information stored in the designated AMF can be configured locally or provisioned by the localized service provider's AF via NEF. A new localized service intention indicator or new Registration Type is carried in the registration request message sent by UE to the AMF, to indicates UE's intention of using the registration for the query of localized service information. The gNB of the hosting network can use this indicator to select the designated AMF and forward the registration to this AMF, if there is a designated AMF for localized services. Upon receiving this indication, the designated AMF can provide UE with the localized service information during or after the registration procedure by using the Registration Accept message or Configuration Update Command. The UE may not have the right subscription which allows UE to access the hosting network before UE queries the localized service information, e.g. the user may not buy a ticket which has the credentials information, therefore, UE may only use the registration procedure to query the localized service information instead of registering to the network. For the latter case, network will send registration reject to the UE but with cause value of localized information query response along with the localized service information shown to the user. And UE may use the queried localized service information to subscribe the localized services (e.g. User uses the service portal address to subscribe the services) and manually select the hosting network later. + +There can be some different registration intention indicators or registration type which can be carried in the registration request: + +- **Local service information Query only:** This indicates the UE only uses this registration request to query localized service information without actual camping and registering to the network. After the hosting network gNB receives the registration request message with this indicator, the gNB forwards the request message to the AMF which can provide the information, such as the designated AMF. The AMF skips the normal registration procedure and just responses UE with registration reject but with cause value of localized information query response along with the localized service information. In this case, if UE is still connected and registered with the home network, UE can be either manually initiated by user to deregister from the home network and conduct query with the hosting network, or UE conducts the localized service information query while UE enters the RRC\_IDLE or RRC\_INACTIVE state based on a stored localized service discovery policy which contains conditions under which service discovery with other hosting network(s) can be conducted. UE and the home network can use paging restriction as defined in clause 5.38.5 of TS 23.501 [3] while UE is conducting localized service query with the hosting network RRC\_IDLE or RRC\_INACTIVE state. +- **Registration with local service information query:** This indicates that the UE would like to collect local service information during service registration phase. After the hosting network gNB receives the registration request message with this indicator, the network forwards the request message to the AMF which can provide information, such as the designated AMF. The AMF can provide the localized service information by either adding the localized service information in the registration accept message or sending separate NAS message, such as UCU. + +- **Registration only:** This indicates that the UE only wants to conduct normal service registration without collecting the localized service information. When the local service intention indicator is absent in the registration request message, it's default to consider the intention indicator is registration only, in order to support backward compatibility or the network which doesn't support localized services. + +In addition, the AMF will indicate how the localized services can be accessed by either providing a specific slice and/or a PDU session The AMF may also provide the UE a list of Tracking Areas, e.g. called "Localized Services availability area", where the localized services are available. The UE will then use this information instead of periodical searches to discover localized services. + +If a certain localized service was not available when the UE asked for it during the registration and now has become available, the network can page the UE (if it happens to be in IDLE Mode), bring it to Connected Mode and then provide the needed information by means of UCU procedure. + +In order to enable UE to use registration message to query localized service information, the hosting network needs to broadcast its capability of supporting the localized service access (e.g. using SIB message). UE only send register request with localized service query to the hosting network which supports localized service access. + +If UE is connected to the home network and supported by the home network, UE can conduct localized service information query with the hosting network including receiving the SIB messages from the hosting network while UE is in the RRC\_IDLE or RRC\_INACTIVE state. UE and the home network can use paging restriction as defined in clause 5.38.5 of TS 23.501 [3] while UE is conducting localized service query with the hosting network. + +UE can initiate localized service query procedure either manually by the user or being triggered by a stored localized service discovery policy which contains conditions under which service discovery with other hosting network(s) can be conducted, such as time, Localized Services availability area, as well as allowed discovery window duration (this can be used to configure the paging restriction information) while UE is in RRC\_IDLE or RRC\_INACTIVE state. This policy can be provisioned by the home network, or localized service providers or User. The home network can also trigger UE to conduct the localized service discovery procedure while UE enters RRC\_IDLE or RRC\_INACTIVE state and certain conditions are met, such as time, Localized Services availability area, so on. In order to trigger UE to conduct localized service discovery, the home network includes a localized service discovery indication and a discovery window which the page restriction is applied in the AN release message sending to UE. + +## 6.26.3 Procedure + +### 6.26.3.1 UE query local service information without registering with the hosting network + +![Sequence diagram for Figure 6.26.3.1-1 showing the procedure for a UE to query local service information without registering.](796d2e601722450d6456085e0a801e1e_img.jpg) + +``` +sequenceDiagram + participant UE1 as UE 1 (Network A) + participant RAN as RAN (Hosting network C) + participant AMF1 as AMF 1 hosting network C + participant AMF2 as AMF 2 (Dedicated AMF for service discovery) (network C) + + Note right of RAN: 3. Select AMF2 Per local configuration + + RAN->>UE1: 1. Broadcast SIB ( support localized service) + UE1->>RAN: 2. Registration request ( local service information query only ) + RAN->>AMF2: 4. Registration request ( local service information query only ) + AMF2->>RAN: 5. Registration reject ( reason cause value: local service info response, local service info) + RAN->>UE1: 5. Registration reject ( reason cause value: local service info response, local service info) +``` + +The sequence diagram illustrates the interaction between four entities: UE 1 (Network A), RAN (Hosting network C), AMF 1 hosting network C, and AMF 2 (Dedicated AMF for service discovery) (network C). The process begins with the RAN broadcasting a System Information Block (SIB) to UE 1, indicating support for localized services. UE 1 responds with a registration request that includes a 'local service information query only' indicator. Upon receiving this request, the RAN performs an internal step, 'Select AMF2 Per local configuration', and then forwards the registration request to AMF 2. AMF 2 sends a registration reject message back to the RAN, which includes a specific cause value ('local service info response, local service info'). Finally, the RAN forwards this registration reject message to UE 1. + +Sequence diagram for Figure 6.26.3.1-1 showing the procedure for a UE to query local service information without registering. + +Figure 6.26.3.1-1 + +1. RAN of hosting Network C broadcasts SIB message which includes indication for supporting localized service. +2. UE1 of Network A is interested in the localized service provided by local network C. Although UE1 may not have a subscription which allow it to access the network C, UE1 may still like to know local services information before making a decision to register to network C to access the local services which the User is interested. UE1 sends registration request message with an indicator "Local service information Query only" for querying local service information. +3. After receiving this registration request message with "local service information query only" indicator, RAN selects the designated AMF2 per the local configuration. +4. RAN forwards the registration request message to AMF2. +5. AMF2 sends a registration reject to UE1 with cause code of local service information response as well as the addition local service information as queried by the UE. + +## 6.26.3.2 UE local service discovery while registering with the hosting network + +![Sequence diagram for UE local service discovery while registering with the hosting network. The diagram shows four lifelines: UE 1 (network A), RAN (hosting network C), AMF 1 (hosting network C), and AMF 2 (Dedicated AMF for service discovery) (network C). The process starts with the RAN broadcasting a SIB message. UE 1 then sends a registration request. The diagram is split into two options: Option a, where the RAN selects AMF2 and the UE receives local service information; and Option b, where the RAN forwards the request to AMF1 and the UE receives a standard registration accept without local service information.](da06747b80ea0d71593cbbd4c2ea89aa_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE 1 (network A) + participant RAN as RAN (hosting network C) + participant AMF1 as AMF 1 (hosting network C) + participant AMF2 as AMF 2 (Dedicated AMF for service discovery) (network C) + + Note left of UE1: 1. Broadcast SIB (support localized service) + RAN->>UE1: 1. Broadcast SIB (support localized service) + + Note right of AMF2: Option a + Note left of UE1: 2a. Registration request (registration with local service information query) + UE1->>RAN: 2a. Registration request (registration with local service information query) + Note right of RAN: 3a. Per local config, Select AMF2 + RAN->>AMF2: 4a. Registration request (local service query) + AMF2->>RAN: 5a. Registration accept (local service info) + RAN->>UE1: 5a. Registration accept (local service info) + Note left of UE1: 6a. Or Other NAS message e.g., UCU (local service information) + AMF2->>RAN: 6a. Or Other NAS message e.g., UCU (local service information) + RAN->>UE1: 6a. Or Other NAS message e.g., UCU (local service information) + + Note right of AMF2: Option b + Note left of UE1: 2b. Registration request (registration only or intention indication is absent) + UE1->>RAN: 2b. Registration request (registration only or intention indication is absent) + RAN->>AMF1: 3b. Registration request (registration only or intention indication is absent) + AMF1->>RAN: 4b. Registration accept + RAN->>UE1: 4b. Registration accept + +``` + +Sequence diagram for UE local service discovery while registering with the hosting network. The diagram shows four lifelines: UE 1 (network A), RAN (hosting network C), AMF 1 (hosting network C), and AMF 2 (Dedicated AMF for service discovery) (network C). The process starts with the RAN broadcasting a SIB message. UE 1 then sends a registration request. The diagram is split into two options: Option a, where the RAN selects AMF2 and the UE receives local service information; and Option b, where the RAN forwards the request to AMF1 and the UE receives a standard registration accept without local service information. + +Figure 6.26.3.2-1 + +1. RAN of hosting Network C broadcasts SIB message which includes indication for supporting localized service. + +- **Option a: If UE likes to receive local service information.** + +2a. UE1 of network A may have the subscription to allow it to access network C and decides to register to the Network C. UE1 sends a registration request message with an local service intention indicator "Registration with local service information query". + +3a. After receiving this registration request message with "Registration with local service information query" indicator, RAN selects the designated AMF2 per the local configuration. + +4a. RAN forwards the registration request message to AMF2. + +5a. AMF2 sends Registration Accept to UE1 with additional local service information as queried by the UE. + +**Or:** + +- 6a. After AMF2 sends registration accept to UE1, AMF2 may send additional NAS message to UE, such as UCU which contains the local service information as queried by UE. + - **Option b: UE already has the local service information, or UE is not interested to collect local service information at this moment.** +- 2b. UE1 sends registration request without any local service intention indicator or with "Registration only". +- 3b. RAN forwards the registration request to AMF1 which is not designated for handling local services. +- 4b. AMF1 sends registration accept to UE1. + +## 6.26.4 Impacts on services, entities and interfaces + +### RAN: + +- Broadcasts of localized information SIB in hosting network. +- Selects the proper AMF based on the registration type/intention indicators from UE. +- Sends indication to trigger UE to conduct localized services discovery while UE enters RRC\_IDLE or RRC\_INACTIVE state if the home network supports triggering UE to conduct localized service discovery. + +### UE: + +- Informs the AMF in hosting network that it is interested in localized services or localized service information. +- Uses the provided information about the availability of the localized services, received in UCU, Registration Reject or Registration Accept, to access the services. +- Initiates localized service query procedure either manually by the user or being triggered by a stored localized service discovery policy which can be provisioned by the home network, or localized service provider or the User. +- Conducts localized service discovery or receives SIB messages from the hosting network while in RRC\_INACTIVE or RRC\_IDLE state if UE is still connected with the home network. + +### AMF: + +- Provides the necessary information about the availability of the localized services to the UE in UCU or Registration Accept. +- Provides to the UE a list of Tracking Areas where certain services are available in the Registration Accept, Registration Reject or UCU message. +- Provides the UE a localized service discovery policy which contains conditions under which service discovery with other hosting network(s) can be conducted, such as time, Localized Services availability area, as well as allowed discovery window duration while UE is in RRC\_IDLE or RRC\_INACTIVE state. + +NOTE: It may require SA WG3 analysis on security and authentication impact for the case which UE query the localized service information without registering with the hosting network. + +## 6.27 Solution #27: Access to localized service by using LADN and N3IWF overlay architecture + +### 6.27.1 Introduction + +This solution addresses Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services and Key Issue #5: Enabling access to localized services via a specific hosting network. The basic principle of this solution is reusing N3IWF overlay architecture and LADN mechanism. + +This solution can be applied in the case of: + +- Home network is a PLMN and hosting network is a SNPN. +- Home network is a SNPN and hosting network is a SNPN. +- Home network is a SNPN and hosting network is a PNI-NPN. + +NOTE: In the case of home network is a PLMN and hosting network is a PNI-NPN is covered by Solution #11. + +## 6.27.2 Functional Description + +### 6.27.2.1 Architecture + +The following figure 6.27.2-1 and figure 6.27.2-2 depict the proposed architecture, which are reusing 5G System architecture with access to SNPN using credentials from Credentials Holder and 5G System architecture accessing overlay network (home network) via underlay network (hosting network). When a UE registers to the selected hosting network and receives localized services provided by the hosting network, architecture in figure 6.27.2-1 is used. If the UE also need to get services from the home network, the UE may establish PDU session as shown in figure 6.27.2-2. Whether the UE receives a specific service from the hosting network or home network is determined based on URSP rule of the UE. The UE just follows the existing PDU Session Establishment procedure based on URSP rule provided by the home network. + +![Figure 6.27.2-1: Architecture when a UE uses localized services provided by the hosting network. The diagram shows a UE connected to an (R)AN, which is connected to an AMF. The AMF is connected to an SMF, which is connected to a UPF, which is connected to a DN. The AMF is also connected to a SEPP, which is connected to another SEPP in the Home Network. The Home Network contains NSSAAF, UDM, NRF, and AUSF. The Hosting Network contains NSSF, NEF, NRF, PCF, and AF. The AMF is also connected to the NEF and the NRF in the Hosting Network. The UE is connected to the (R)AN via N1 and N2 interfaces. The (R)AN is connected to the AMF via N3 interface. The AMF is connected to the SMF via N4 interface. The SMF is connected to the UPF via N6 interface. The UPF is connected to the DN via N9 interface. The AMF is connected to the SEPP via N32 interface. The SEPP is connected to the SEPP in the Home Network via N32 interface. The SEPP in the Home Network is connected to the NSSAAF, UDM, NRF, and AUSF via NnssAAF, Nudm, Nnrf, and Nausf interfaces respectively. The AMF is connected to the NSSF, NEF, NRF, PCF, and AF via Nnssf, Nnef, Nnrf, Npcf, and Naf interfaces respectively. The AMF is also connected to the NEF and the NRF via Namf and Nsmf interfaces respectively.](ff3417b75213b8688e6504a21220b430_img.jpg) + +Figure 6.27.2-1: Architecture when a UE uses localized services provided by the hosting network. The diagram shows a UE connected to an (R)AN, which is connected to an AMF. The AMF is connected to an SMF, which is connected to a UPF, which is connected to a DN. The AMF is also connected to a SEPP, which is connected to another SEPP in the Home Network. The Home Network contains NSSAAF, UDM, NRF, and AUSF. The Hosting Network contains NSSF, NEF, NRF, PCF, and AF. The AMF is also connected to the NEF and the NRF in the Hosting Network. The UE is connected to the (R)AN via N1 and N2 interfaces. The (R)AN is connected to the AMF via N3 interface. The AMF is connected to the SMF via N4 interface. The SMF is connected to the UPF via N6 interface. The UPF is connected to the DN via N9 interface. The AMF is connected to the SEPP via N32 interface. The SEPP is connected to the SEPP in the Home Network via N32 interface. The SEPP in the Home Network is connected to the NSSAAF, UDM, NRF, and AUSF via NnssAAF, Nudm, Nnrf, and Nausf interfaces respectively. The AMF is connected to the NSSF, NEF, NRF, PCF, and AF via Nnssf, Nnef, Nnrf, Npcf, and Naf interfaces respectively. The AMF is also connected to the NEF and the NRF via Namf and Nsmf interfaces respectively. + +Figure 6.27.2-1: Architecture when a UE uses localized services provided by the hosting network + +![Figure 6.27.2-2: Architecture when a UE uses services provided by the home network. The diagram shows a UE connected to a Hosting Network 3GPP Access, which is connected to an AMF in the Hosting Network. The AMF is connected to an SMF in the Hosting Network, which is connected to a UPF in the Hosting Network, which is connected to a DN in the Hosting Network. The AMF in the Hosting Network is connected to an N3IWF in the Home Network via N11 for Home Network. The N3IWF is connected to an AMF in the Home Network, which is connected to an SMF in the Home Network, which is connected to a UPF in the Home Network, which is connected to a DN in the Home Network. The UE is connected to the Hosting Network 3GPP Access via N1 for Hosting Network and N2 interfaces. The Hosting Network 3GPP Access is connected to the AMF in the Hosting Network via Nwuu for Home Network interface. The AMF in the Hosting Network is connected to the SMF in the Hosting Network via N11 interface. The SMF in the Hosting Network is connected to the UPF in the Hosting Network via N4 interface. The UPF in the Hosting Network is connected to the DN in the Hosting Network via N6 interface. The AMF in the Hosting Network is connected to the N3IWF in the Home Network via N11 for Home Network interface. The N3IWF is connected to the AMF in the Home Network via N3 interface. The AMF in the Home Network is connected to the SMF in the Home Network via N11 interface. The SMF in the Home Network is connected to the UPF in the Home Network via N4 interface. The UPF in the Home Network is connected to the DN in the Home Network via N6 interface.](ffd8c2986aabedc8b6db2d8f2ed7a994_img.jpg) + +Figure 6.27.2-2: Architecture when a UE uses services provided by the home network. The diagram shows a UE connected to a Hosting Network 3GPP Access, which is connected to an AMF in the Hosting Network. The AMF is connected to an SMF in the Hosting Network, which is connected to a UPF in the Hosting Network, which is connected to a DN in the Hosting Network. The AMF in the Hosting Network is connected to an N3IWF in the Home Network via N11 for Home Network. The N3IWF is connected to an AMF in the Home Network, which is connected to an SMF in the Home Network, which is connected to a UPF in the Home Network, which is connected to a DN in the Home Network. The UE is connected to the Hosting Network 3GPP Access via N1 for Hosting Network and N2 interfaces. The Hosting Network 3GPP Access is connected to the AMF in the Hosting Network via Nwuu for Home Network interface. The AMF in the Hosting Network is connected to the SMF in the Hosting Network via N11 interface. The SMF in the Hosting Network is connected to the UPF in the Hosting Network via N4 interface. The UPF in the Hosting Network is connected to the DN in the Hosting Network via N6 interface. The AMF in the Hosting Network is connected to the N3IWF in the Home Network via N11 for Home Network interface. The N3IWF is connected to the AMF in the Home Network via N3 interface. The AMF in the Home Network is connected to the SMF in the Home Network via N11 interface. The SMF in the Home Network is connected to the UPF in the Home Network via N4 interface. The UPF in the Home Network is connected to the DN in the Home Network via N6 interface. + +Figure 6.27.2-2: Architecture when a UE uses services provided by the home network + +### 6.27.2.2 Hosting network discovery and selection + +It is assumed that there is service level agreement between the home network and hosting network and based on the agreement the AMF in the home network is configured with Localized Service Information. The Localized Service Information contains following information: + +- Localized Service Name. +- Validity condition: + - Time and Spatial validity. +- Hosting network information: + - Precedence. + - Hosting network ID (SNPN or PLMN ID) and RAT type (e.g. NR, E-UTRA). + - LADN DNN. + - Allowed CAG information. + +When a UE is registered in home network, the UE may request Localized Service Information to the AMF by sending NAS message (e.g. Registration). If subscription of the UE allows to use the Localized service, the AMF provides localized service information to the UE. The UE stores the received Localized Service Information until time validity condition is fulfilled. The spatial validity condition in the Localized Service Information can be represented by geographical area. The exact service area information of hosting network is provided to the UE as a part of LADN information during the registration to the hosting network. + +NOTE 1: In the case of roaming scenario, the AMF in the serving PLMN provides Localized Service Information to the UE. + +NOTE 2: The AMF can provide Localized Service Information to the UE without UE request if subscription of the UE allows to use the Localized service. For example, the AMF may provide Localized Service Information when a UE enters an area where the Localized service is available. + +If the hosting network uses CAG for Localized service (i.e. in the case of hosting network is PNI-NPN), the Allowed CAG information can be provided to the UE. If the UE receives Allowed CAG information via Localized Service Information, the UE shall use the Allowed CAG information only when the UE access the hosting network for the Localized service. + +### 6.27.2.3 Registration to hosting network and access to Localized services + +Based on received Localized Service Information, the UE selects the hosting network and registers to the network. When a UE registers to the hosting network and has the subscription to a specific LADN DNN for local service or a wild card DNN, the AMF provides LADN information (i.e. LADN DNN and LADN service area) to the UE according to the existing LADN mechanism. The UE uses the LADN information to access localized services provided by the hosting network. + +NOTE: When hosting network operator configures LADN information in the AMF, the operator can provide associated validity time of LADN DNN so that the AMF provides LADN information when the validity time is satisfied. + +## 6.27.3 Procedures + +### 6.27.3.1 Requesting Localized service information + +![Sequence diagram showing the request for localized service information between UE and Home Network AMF.](d66f6b708b0f0f8717f85872afec0089_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Home Network AMF + Note left of UE: Request of Localized Service Information + UE->>Home Network AMF: 1. NAS Request message (Request of Localized Service Information) + Home Network AMF-->>UE: 2. NAS Response message (Localized Service Information) + +``` + +Sequence diagram showing the request for localized service information between UE and Home Network AMF. + +**Figure 6.27.3.1-1: Requesting Localized service information** + +The UE may request Localized Service Information to the AMF by sending NAS message (e.g. Registration request). The UE may indicate specific service the UE wants to receive by including Localized service name. The AMF provides Localized Service Information to the UE as described in clause 6.27.2.1. + +NOTE: How the UE gets Localized service name is out of 3GPP scope. The UE can get Localized service name via webpage, by installing application, etc. + +### 6.27.3.2 Connection to hosting network and access to Localized services + +![Sequence diagram showing registration in the hosting network and access to Localized services.](c59200e0fd141cba63a0b0739c59c3d7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Hosting Network AMF + participant Hosting Network V-PCF + participant Home Network AUSF + participant Home Network UDM + participant Hosting Network SMF + participant Home Network N3IWF + participant Home Network AMF + + Note left of UE: Registration type = local services + UE->>Hosting Network AMF: 1. Registration request (Registration type = local services) + Hosting Network AMF->>Home Network UDM: 2. Authentication + Hosting Network AMF->>Home Network AUSF: 3. Nudm_UECM_Registration (Registering for local services) + Home Network UDM-->>Hosting Network AMF: 4. Registration accept (LADN information) + Hosting Network AMF-->>UE: 5a. PDU Session Establishment Request (LADN DNN) + UE-->>Hosting Network AMF: 5b. PDU Session Establishment Accept + Hosting Network AMF->>Home Network SMF: 6a. PDU Session Establishment Request (For Home Network access) + Home Network SMF-->>Hosting Network AMF: 6b. PDU Session Establishment Accept + Hosting Network AMF-->>UE: 7a. Registration request + UE-->>Home Network N3IWF: 7b. Registration accept + +``` + +Sequence diagram showing registration in the hosting network and access to Localized services. + +**Figure 6.27.3.2-1: Registration in the hosting network and access to Localized services** + +If the UE wants to receive Localized service, the UE requests Localized service information as specified in clause 6.27.3.1 and selects hosting network based on received Localized Service Information. If selected hosting network is available, the UE performs registration with the selected hosting network. The Registration procedure in TS 23.502 [4] is used with following modifications: + +- When the UE performs Registration procedure, Registration type indicates that the UE is accessing the network for localized services. Based on this information the AMF determine to provide LADN information to the UE. +- The AMF indicates to the UDM that the UE is registering for localized services. The UDM use the indication whether to accept UE registration. + +After Registration is completed, the UE establishes PDU Session to the LADN DNN. + +If the UE needs to get home network services, the UE may establishes PDU Session and registers to the home network via N3IWF. + +## 6.27.4 Impacts on services, entities, and interfaces + +UE: + +- The UE indicates that the UE is accessing the network for localized services during the Registration procedure. +- The UE requests and receives Localized Service Information from the AMF and selects hosting network based on the received Localized Service Information. + +AMF: + +- The AMF indicates to the UDM that the UE is registering for localized services. +- The AMF provides Localized Service Information to the UE. +- The PLMN AMF allows a SNPN subscribed UE to access PNI-NPN. +- The SNPN AMF provides Allowed CAG information used for hosting network to the UE. + +UDM: + +- The UDM determines whether to accept registration taking into account the indication that UE is registering for localized services. + +## 6.28 Solution #28: OTT solution for access to localized services + +### 6.28.1 Introduction + +This solution addresses Key Issues #4 (Enabling UE to discover, select and access NPN as hosting network and receive localized services) and #5 (Enabling access to localized services via a specific hosting network). + +The solution is an Over-The-Top (OTT) solution and is described in reference to the "umbrella" Solution #7. + +### 6.28.2 Functional Description + +Figure 6.28.2-1 illustrates the relationship between the Localized Service Provider (LSP), the Hosting Network and UE's Home Network. + +![Figure 6.28.2-1: OTT solution for access to localized services. The diagram shows the interaction between a UE, a Hosting Network, a Home Network (containing an N3IWF and a Home Network portal), and a Localized Service Provider (LSP) which acts as a Credential Holder (CH) with AAA. The sequence of steps is: 1. UE connects to the Home Network portal to request information for access to a localized service. 2. LSP issues time-restricted credentials for access to a Hosting Network and to a Localized service. 3. Home Network pushes the time-restricted credentials into UE. 4. UE connects to the Hosting network. 4a. UE is authenticated by LSP in the role of CH. 5. UE accesses the localized service via the Hosting Network. 5a. UE accesses Home Network services via the N3IWF.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HN as Home Network + subgraph HN [Home Network] + N3IWF + Portal as Home Network portal + end + participant LSP as LSP as CH with AAA + participant HostingNetwork as Hosting Network + + Note right of UE: 1. UE connects to the Home Network portal to request information for access to a localized service + Portal-->LSP: + Note right of LSP: 2. LSP issues time-restricted credentials for access to a Hosting Network and to a Localized service + LSP-->HN: + Note right of HN: 3. Home Network pushes the time-restricted credentials into UE + HN-->UE: + Note right of UE: 4. UE connects to the Hosting network + UE-->HostingNetwork: + Note right of UE: 4a. UE authenticated by LSP in the role of CH + UE-->LSP: + Note right of UE: 5. UE accesses the localized service via the Hosting Network + UE-->HostingNetwork: + Note right of UE: 5a. UE accesses Home Network services + UE-->N3IWF: + +``` + +Figure 6.28.2-1: OTT solution for access to localized services. The diagram shows the interaction between a UE, a Hosting Network, a Home Network (containing an N3IWF and a Home Network portal), and a Localized Service Provider (LSP) which acts as a Credential Holder (CH) with AAA. The sequence of steps is: 1. UE connects to the Home Network portal to request information for access to a localized service. 2. LSP issues time-restricted credentials for access to a Hosting Network and to a Localized service. 3. Home Network pushes the time-restricted credentials into UE. 4. UE connects to the Hosting network. 4a. UE is authenticated by LSP in the role of CH. 5. UE accesses the localized service via the Hosting Network. 5a. UE accesses Home Network services via the N3IWF. + +**Figure 6.28.2-1: OTT solution for access to localized services** + +The following are the salient features of this solution: + +- The Localized Service Provider (LSP) has a service agreement with UE's Home Network and with a Hosting Network. There is no direct agreement between UE's Home Network and the Hosting Network. +- The solution assumes that the Hosting Network is an SNPN, whereas UE's Home Network can be an SNPN or a PLMN. +- UE's user connects to a web portal of the Home Network operator to request information for access to a localized service. +- The Home Network obtains time-restricted credentials from the LSP providing this service. The time-restricted credentials include e.g. the following: + - SNPN ID and geographical coordinates of the Hosting Network. + - User id and security credential for access to the Home Network. + - User id and security credential for access to the LSP server providing the localized service. + - DNN/S-NSSAI for establishment of a PDU Session in the Hosting Network with optional credentials for secondary authentication. +- The Home Network pushes the time-restricted credentials into the UE (e.g. using SMS or via the web portal). +- When the UE arrives at the venue where the localized service is provided (e.g. stadium), the user performs manual selection of the Hosting Network. UE connects to the Hosting Network and is authenticated by the LSP in the role of Credential Holder (e.g. using a AAA server) based on the user id and security credential for access to the Home Network. +- UE requests a PDU Session to the provided DNN/S-NSSAI and accesses the localized service of the LSP via the Hosting Network based on the user id and security credential for access to the LSP server providing the localized service. +- In parallel the UE can access the services of the Home Network using an OTT (NWu) connection to an N3IWF node in the Home Network. + +## 6.28.3 Procedures + +Figure 6.28.3-1 (modelled on Figure 6.7.3-1) describes the procedure for access to localized services: + +![Sequence diagram illustrating the procedures for access to localized service. The diagram shows interactions between UE, Home Network, Hosting Network, and Service Provider. The steps are: H1. Service agreements between Home Network and Service Provider; H2. Network configuration from Service Provider to Hosting Network; H3. User is prompted by localized service add from UE; H4. UE requests via web portal the information needed to access A hosting network and the localized service from UE to Home Network and Service Provider; H5. Manual selection of the hosting network from UE; H6. UE connects to hosting network, authenticated by LSP in the role of CH from UE to Hosting Network; H7. UE accesses the localized service, and optionally home network services from UE to Service Provider; H8. UE returns from hosting network from UE; H9. Charge the use of localized service from Home Network to Service Provider; H10. Roll back previous setup from Hosting Network.](34d7353cac3d344f71ad82bd1eda40d1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Home Network + participant Hosting Network + participant Service Provider + + Note right of Home Network: H1. Service agreements + Home Network-->>Service Provider: H1. Service agreements + Note right of Service Provider: H2. Network configuration + Service Provider-->>Hosting Network: H2. Network configuration + Note left of UE: H3. User is prompted by localized service add + UE-->>UE: H3. User is prompted by localized service add + Note right of UE: H4. UE requests via web portal the information needed to access A hosting network and the localized service + UE-->>Home Network: H4. UE requests via web portal the information needed to access A hosting network and the localized service + UE-->>Service Provider: H4. UE requests via web portal the information needed to access A hosting network and the localized service + Note left of UE: H5. Manual selection of the hosting network + UE-->>UE: H5. Manual selection of the hosting network + Note right of UE: H6. UE connects to hosting network, authenticated by LSP in the role of CH + UE-->>Hosting Network: H6. UE connects to hosting network, authenticated by LSP in the role of CH + Note right of UE: H7. UE accesses the localized service, and optionally home network services + UE-->>Service Provider: H7. UE accesses the localized service, and optionally home network services + Note left of UE: H8. UE returns from hosting network + UE-->>UE: H8. UE returns from hosting network + Note right of Home Network: H9. Charge the use of localized service + Home Network-->>Service Provider: H9. Charge the use of localized service + Note right of Hosting Network: H10. Roll back previous setup + Hosting Network-->>Hosting Network: H10. Roll back previous setup + +``` + +Sequence diagram illustrating the procedures for access to localized service. The diagram shows interactions between UE, Home Network, Hosting Network, and Service Provider. The steps are: H1. Service agreements between Home Network and Service Provider; H2. Network configuration from Service Provider to Hosting Network; H3. User is prompted by localized service add from UE; H4. UE requests via web portal the information needed to access A hosting network and the localized service from UE to Home Network and Service Provider; H5. Manual selection of the hosting network from UE; H6. UE connects to hosting network, authenticated by LSP in the role of CH from UE to Hosting Network; H7. UE accesses the localized service, and optionally home network services from UE to Service Provider; H8. UE returns from hosting network from UE; H9. Charge the use of localized service from Home Network to Service Provider; H10. Roll back previous setup from Hosting Network. + +**Figure 6.28.3-1: Procedures for access to localized service** + +- H1. The Localized Service Provider (LSP) establishes service agreement with the operator of a Hosting Network. The LSP also establishes a service agreement with UE's Home Network operator to enable the UE to receive information needed to discover/access Hosting Network and the localized service. + +- H2. The hosting network is configured based on the service agreement e.g. DNN/S-NSSAI configuration for access to localized service, QoS, number of end users, time, location, whether home network services can be accessed via hosting network, etc. The configuration of the Hosting Network is performed by means that are outside of 3GPP scope. +- H3. UE's user is prompted by localized service advertisement. +- H4. UE's user connects to a web portal of the Home Network operator to request information for access to a localized service. The Home Network obtains time-restricted credentials from the LSP providing this service. The time-restricted credentials are described in clause 6.28.2. The Home Network pushes the time-restricted credentials into the UE (e.g. using SMS or via the web portal). +- NOTE: The solution assumes that the LSP has service agreement with the Home Network (as in Solution #7). If the UE has a direct service relationship with the LSP, the Home Network can be circumvented. +- H5. When the UE arrives at the venue where the localized service is provided (e.g. stadium), the user performs manual selection of the Hosting Network. +- H6. UE connects to the Hosting Network and is authenticated by the LSP in the role of Credential Holder (e.g. using a AAA server). +- H7. UE requests a PDU Session and accesses the localized service of the LSP via the Hosting Network. In parallel the UE can access the services of the Home Network using an OTT (NWu) connection to an N3IWF node in the Home Network. +- H8. Upon expiry of the time-restricted credentials, the LSP in the role of Credential Holder requests a release of the UE. +- H9. LSP collects and provides charging information to UEs' Home Network operator by means outside of 3GPP specification. +- H10. When the localized service agreement is terminated, the Hosting Network removes the configured information (configured in step H2) by means that are outside of 3GPP scope. + +## 6.28.4 Impacts on services, entities, and interfaces + +SA WG3 may need to check the security aspects e.g. related to the type of time-restricted credentials that can be used. + +The solution has no specification impact from SA WG2 perspective unless being identified by SA WG3. + +## 6.29 Solution #29: Solution for enabling UE to automatic discover and select a network for accessing local services on top of solution #10 + +### 6.29.1 Introduction + +The solution addresses Key Issue #4 (Enabling UE to discover, select and access NPN as hosting network and receive localized services) and builds on top of Solution #10. + +### 6.29.2 Functional Description + +This solution is based on Solution #10, clause 6.10.2.1 with the following considerations: + +- When one or more hosting network providing localised services is available in a particular location and time, the serving network will broadcast the availability of hosting network (i.e. indication of availability of one or more hosting network: YES/NO) to all the UEs in that area. This information will be broadcasted through SIB messages in all cells of the serving network that overlaps with the physical geographic area where the hosting network(s) is/are available. + +- Validity information of the "prioritized list of SNPNS for localized services" will contain the Cell Identifiers / Tracking area(s) (corresponding to serving network) where the local hosting network is expected to be present. +- When all the validity information is met and the UE detects the presence of local hosting network through the indication broadcasted in SIB message, the UE scans for SNPNS in the background. +- Service agreement exists between the Serving network of UE and the hosting network providing localized services. +- Serving Network is notified about the availability of hosting network. + +### 6.29.3 Procedures + +![Sequence diagram illustrating the discovery and selection of NPN as hosting network for localized services. The diagram shows four lifelines: UE, NG RAN, Serving Network, and Hosting Network. The process starts with an assumption that the UE is configured with a prioritized list of SNPNS for localized services. The Hosting Network indicates it is up and available to the Serving Network. The Serving Network then indicates the availability of the hosting network to the NG RAN. The NG RAN broadcasts a SIB message (hosting network available) to the UE. The UE checks if validity conditions are met and a matching entry is found in its prioritized list. Finally, the UE selects the hosting network and accesses localized services.](346324c08906e6d9320f632ab916f73e_img.jpg) + +``` +sequenceDiagram + participant UE + participant NG_RAN as NG RAN + participant Serving_Network as Serving Network + participant Hosting_Network as Hosting Network + + Note left of UE: Assumption: +UE is configured with +prioritized list of SNPNS +for localized services + Note right of Hosting_Network: Network is up and available +for providing localized services + Hosting_Network->>Serving_Network: + Serving_Network->>NG_RAN: Indicate availability of +hosting network + NG_RAN->>UE: SIB (hosting n/w +available) + Note left of UE: Validity conditions met and +a matching entry found in +"prioritized list of SNPNS for +localized services" + Note right of UE: UE selects hosting network and access localized services +``` + +Sequence diagram illustrating the discovery and selection of NPN as hosting network for localized services. The diagram shows four lifelines: UE, NG RAN, Serving Network, and Hosting Network. The process starts with an assumption that the UE is configured with a prioritized list of SNPNS for localized services. The Hosting Network indicates it is up and available to the Serving Network. The Serving Network then indicates the availability of the hosting network to the NG RAN. The NG RAN broadcasts a SIB message (hosting network available) to the UE. The UE checks if validity conditions are met and a matching entry is found in its prioritized list. Finally, the UE selects the hosting network and accesses localized services. + +**Figure 6.29.3-1: Discovery and selection of NPN as hosting network for localized services** + +1. UE is configured with a "prioritized list of SNPNS for localized services" as explained in Solution #10 +2. When the hosting network becomes active and ready for serving the UE(s), it indicates to the serving network about its availability. +3. Serving network broadcasts through SIB messages in all cells that are overlapping the physical geographic area where the hosting network is available, an indication regarding the presence of hosting network services. +4. SNPNS-localized services-enabled UE reaches a geographical area where a hosting network services are available. +5. Once the UE sees the presence of a local hosting network (through SIB message), the UE then checks the "prioritized list of SNPNS for localized services" for the SNPNS and their validity conditions. If the UE finds one or more valid SNPNS (e.g. the current time and Tracking area/Cell Identifier broadcasted by the serving network matches with at least one of the entries of "prioritized list of SNPNS for localized services"), then the UE starts looking for the SNPNS in the background. +6. If the UE finds at least one available and allowable SNPNS which meets the validity conditions, then the UE switches to a new network selection mode "SNPNS Localized services mode" and selects an available SNPNS from + +the list of SNPNs for localized services. Alternatively, the UE could provide the indication to the user for manual network selection process. + +NOTE 1: The "prioritized list of SNPNs for localized services" and "SNPN Localized services mode" are defined in Solution #10. + +In a variation to this method, the availability of hosting network indication could be indicated through on-demand SIB messages. The UE will request for the on-demand SIB messages once the validity information is met, and if presence of local hosting network is detected through such SIB messages, then the UE switches to a new network selection mode "SNPN Localized services mode" and selects an available SNPN from the list of SNPNs for localized services. + +NOTE 2: Availability of local hosting services could be indicated by a flag or by the presence of local hosting network identifiers. + +## 6.29.4 Impacts on services, entities and interfaces + +The solution has the following impacts in addition to the impacts mentioned in Solution #10: + +UE: + +- Handling of SIB message changes, prioritized list of SNPNs for localized services (that includes additional validity conditions as explained in clause 6.29.2) and SNPN Localized services mode. + +AMF: + +- Indication of presence of hosting network to NG-RANs. + +NG-RAN: + +- Broadcasting the indication of presence of hosting network to UEs. + +## 6.30 Solution #30: Solution for steering a UE to a Hosting Network by Home Network + +### 6.30.1 Introduction + +This solution addresses the Key issue#4: Enabling UE to discover, select and access NPN as Hosting Network and receive Localized Services. + +Clause 6.41.2.2 of TS 22.261 [2] specifies: + +- Subject to regulatory requirements and localized service agreements, the 5G system shall allow a Home Network operator to automatically negotiate policies with the Hosting Network for allowing the Home Network's subscribers to connect at a specific occasion, e.g. time and location, for their Home Network services. + +According to the above, the UE is **\*allowed\*** by Home Network to select a Hosting Network, i.e. the UE is **\*not enforced\*** to select a Hosting Network. Therefore, the UE can decide (e.g. UE implementation) whether it stays in current serving network or it selects a Hosting Network. + +To access Localized Services, when the Validity Information is met, the UE may initiate Hosting Network selection according to the configuration. + +This solution proposes a complementary approach where the Home Network may configure the UE only initiate Hosting Network selection when explicitly steered by the Home Network. The solution focuses on Home Network (PLMN or SNPN) steering to SNPN Hosting Networks. + +**Editor's note:** Steering to PNI-NPN is FFS. + +Based on the above, in this solution, the following general principles are proposed: + +- The UE is (pre)-configured or provisioned (signalled) by Home Network with a **List of SNPN Hosting Networks with Validity Information** (i.e. time and/or location) and an **Indication that the UE is only allowed to select a Hosting Network upon Steering by the Home Network**, except if Home Network is not available in which case + +the UE is allowed to select an SNPN Hosting Network without Home Network steering, when Validity Information is met. + +- When the Validity Information is about to be met, the UE starts searching for available and allowable SNPN Hosting Networks based on the *List of SNPN Hosting Networks with Validity Information* while the UE is served by a Serving Network. +- If the UE finds available and allowable SNPN Hosting Networks, the UE reports those SNPN Hosting Networks to the Home Network. The Home Network then determines the *Prioritized list of SNPN Hosting Networks* to which the UE can register for the Localized Services using Home Network's subscription/credentials. This list may contain a single SNPN Hosting Network. +- If the UE needs to register to Home Network using NWu interface, the N3IWF addresses of the Home Network are also configured in the UE. + +NOTE: If the UE's Serving Network is PLMN, and the UE's Home Network is PLMN. The existing Roaming mechanism is applied to allow the UE to reach the UE's Home Network + +- The UE selects and registers to a Hosting Network in the *Prioritized list of SNPN Hosting Networks* following the priority order in this list + +## 6.30.2 Steering a UE to an SNPN Hosting Network + +### 6.30.2.1 The serving network is Home Network of the UE + +When the Validity Information is about to be met and the UE is configured with an *Indication that the UE is only allowed to select a Hosting Network upon Steering by the Home Network*, the following steps are executed: + +- The UE starts searching for available and allowable Hosting Networks based on the *List of SNPN Hosting Networks with Validity Information* while the UE is served by a serving network (Home Network). +- If the UE finds any available and allowable SNPN Hosting Network(s), the UE initiates Service Request (SR) or Mobility Registration Update (MRU) procedure to report those available and allowable SNPN Hosting Network(s) to the serving network (Home Network). +- The serving network (Home Network) determines the *Prioritized list of SNPN Hosting Networks* and includes this list in the response message of SR or MRU procedure to the UE to instruct the UE to regard the *Prioritized list of SNPN Hosting Networks* as highest priority networks than any other network including Home Network when selecting an SNPN Hosting Network. +- When the UE receives the *Prioritized list of SNPN Hosting Networks*, the UE deregisters from the serving network (Home Network) and immediately selects and registers to an SNPN Hosting Network based on this list i.e. in prioritized order. + +When the Validity Information is no longer met or if UE no longer needs the SNPN Hosting Network for Localized Services, the UE deregisters from the SNPN Hosting Network, deletes the *Prioritized list of SNPN Hosting Networks*, and initiates normal network selection for returning to Home Network. + +### 6.30.2.2 The serving network is not Home Network of the UE + +When the Validity Information is about to be met and the UE is configured with an *Indication that the UE is only allowed to select a Hosting Network upon Steering by the Home Network*, the following steps are executed: + +- The UE starts searching for available and allowable SNPN Hosting Networks based on the *List of SNPN Hosting Networks with Validity Information* while the UE is served by a serving network (any other available and allowable network except Home Network). +- If the UE finds any available and allowable SNPN Hosting Network(s): + - Since the serving network is not Home Network, the UE needs to register to Home Network via NWu interface using the serving network as underlay network for connecting to the N3IWF of Home Network. + +- Then, the UE initiates SR procedure using the serving network (undelay network) to Home Network to report those available and allowable SNPN Hosting Network(s) to Home Network. +- The Home Network determines the *Prioritized list of SNPN Hosting Networks* and includes this list in the response message of SR to the UE to instruct the UE to regard the *Prioritized list of SNPN Hosting Networks* as highest priority networks than any other network including Home Network when selecting an SNPN Hosting Network. +- When the UE receives the *Prioritized list of SNPN Hosting Networks*, the UE deregisters from the serving network and immediately selects and registers to an SNPN Hosting Network based on the list in prioritized order. + +When the Validity Information is no longer met or if UE no longer needs the SNPN Hosting Network for Localized Services, the UE deregisters from the SNPN Hosting Network, deletes the *Prioritized list of SNPN Hosting Networks*, and initiates normal network selection for returning to Home Network. + +### 6.30.2.3 The selection of an SNPN Hosting Network without Home Network's steering + +When the Validity Information is met, and if the UE is not configured with an *Indication that the UE is only allowed to select a Hosting Network upon Steering by the Home Network*, the UE could decide whether it stays in the current serving network or the UE could select an SNPN Hosting Network for Localized Services based on the *List of SNPN Hosting Networks with Validity Information* e.g. up to the implementation. + +If Home Network is not available, i.e. the UE cannot find any available serving network, in which case the UE is allowed to select an SNPN Hosting Network without Home Network steering, when Validity Information is met. + +## 6.30.3 Procedure + +### 6.30.3.1 Steer a UE to an SNPN Hosting Network when the serving network is UE's Home Network + +In the case that the Home Network of the UE is SNPN and the serving network is the UE's subscribed SNPN. Based on the principles: + +- The UE is (pre)-configured or provisioned (signalled) by the UE's subscribed SNPN with the *List of SNPN Hosting Networks with Validity Information* and the UE is configured with the *Indication that the UE is only allowed to select a Hosting Network upon Steering by the Home Network*. +- The UE is also configured with the N3IWF addresses of the UE's subscribed SNPN. + +Then the following steps are performed (shown in Figure 6.30.3.1-1): + +- Step 0: the UE registers to the UE's subscribed SNPN. +- Step 1: When the Validity Information is about to be met, the UE starts searching any available and allowable SNPN Hosting Network(s) based on the *List of SNPN Hosting Networks with Validity Information* while the UE is served by the UE's subscribed SNPN. +- Step 2: If the UE finds any available and allowable SNPN Hosting Network(s), the UE initiates Service Request (SR) or Mobility Registration Update (MRU) procedure to report those available and allowable SNPN Hosting Network(s) to the UE's subscribed SNPN. +- Step 3: The UE's subscribed SNPN determines the *Prioritized list of SNPN Hosting Networks* and includes this list in the response message of SR or MRU procedure to instruct the UE to regard the *Prioritized list of SNPN Hosting Networks* as highest network than other network including Home Network when selecting an SNPN Hosting Network. +- Step 4: When the UE receives the *Prioritized list of SNPN Hosting Networks*, the UE deregisters from the UE's subscribed SNPN and immediately selects and registers to an SNPN Hosting Network based on the list in prioritized order. + +Step 5: When the Validity Information is no longer met or if UE no longer needs the SNPN Hosting Network for Localized Services, the UE deregisters from the SNPN Hosting Network, deletes the *Prioritized list of SNPN Hosting Networks*, and initiates SNPN network selection for returning to Home Network. + +![Sequence diagram showing the interaction between UE, Serving Network (HPLMN), and SNPN Hosting Network. The steps are: 0. UE registers to the UE's subscribed SNPN/HPLMN; 1. The Validity information is about to be met, the UE starts to search any available and allowable SNPN Hosting Network(s); 2. Initiates SR or MRU for reporting the search results of available and allowable SNPN Hosting Networks; 3. Determines the Prioritized list of SNPN Hosting Networks and includes the Prioritized list of SNPN Hosting Networks in response message of SR/MRU; 4. The UE selects and registers to an SNPN Hosting Network based on the Prioritized list of SNPN Hosting Networks; 5. When the Validity Information is no longer met, the UE deregisters from the SNPN Hosting Network, deletes the prioritized list of SNPN Hosting Networks, and initiates SNPN selection/PLMN selection for returning to Home Network.](a66383962afcd0f0458f0d45c101fabf_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN as Serving Network (the UE's subscribed SNPN/the UE's HPLMN) + participant SNHN as SNPN Hosting Network + + Note left of UE: 0. UE registers to the UE's subscribed SNPN/HPLMN + Note left of UE: 1. The Validity information is about to be met, the UE starts to search any available and allowable SNPN Hosting Network(s) + UE->>SN: 2. Initiates SR or MRU for reporting the search results of available and allowable SNPN Hosting Networks + Note right of SN: 3. Determines the Prioritized list of SNPN Hosting Networks and includes the Prioritized list of SNPN Hosting Networks in response message of SR/MRU + Note left of UE: 4. The UE selects and registers to an SNPN Hosting Network based on the Prioritized list of SNPN Hosting Networks + Note left of UE: 5. When the Validity Information is no longer met, the UE deregisters from the SNPN Hosting Network, deletes the prioritized list of SNPN Hosting Networks, and initiates SNPN selection/PLMN selection for returning to Home Network + +``` + +Sequence diagram showing the interaction between UE, Serving Network (HPLMN), and SNPN Hosting Network. The steps are: 0. UE registers to the UE's subscribed SNPN/HPLMN; 1. The Validity information is about to be met, the UE starts to search any available and allowable SNPN Hosting Network(s); 2. Initiates SR or MRU for reporting the search results of available and allowable SNPN Hosting Networks; 3. Determines the Prioritized list of SNPN Hosting Networks and includes the Prioritized list of SNPN Hosting Networks in response message of SR/MRU; 4. The UE selects and registers to an SNPN Hosting Network based on the Prioritized list of SNPN Hosting Networks; 5. When the Validity Information is no longer met, the UE deregisters from the SNPN Hosting Network, deletes the prioritized list of SNPN Hosting Networks, and initiates SNPN selection/PLMN selection for returning to Home Network. + +**Figure 6.30.3.1-1: the UE's subscribed SNPN/the UE's HPLMN as the serving network steers the UE to an SNPN Hosting Network** + +In the case that the Home Network of the UE is PLMN and the serving network is the UE's HPLMN. Based on the principles: + +- The UE is (pre)-configured or provisioned (signalled) by the UE's HPLMN with the *List of SNPN Hosting Networks with Validity Information* and the UE is configured with the *Indication that the UE is only allowed to select a Hosting Network upon Steering by the Home Network*. +- The UE is also configured with the N3IWF addresses of the UE's HPLMN + +Then the following steps are performed (shown in Figure 6.30.3.1-1): + +Step 0: The UE registers to the UE's HPLMN + +Step 1: When the Validity Information is about to be met, the UE in SNPN access mode starts searching any available and allowable SNPN Hosting Network based on the *List of SNPN Hosting Networks with Validity Information* while the UE is served by UE's HPLMN + +- Step 2: If the UE finds any available and allowable SNPN Hosting Network(s), the UE initiates Service Request (SR) or Mobility Registration Update (MRU) procedure to report those available and allowable SNPN Hosting Network(s) to the UE's HPLMN. +- Step 3: The UE's HPLMN determines the ***Prioritized list of SNPN Hosting Networks*** and includes this list in the response message of SR or MRU procedure to instruct the UE to regard the ***Prioritized list of SNPN Hosting Networks*** as highest network than other network including Home Network when selecting an SNPN Hosting Network +- Step 4: When the UE receives the ***Prioritized list of SNPN Hosting Networks***, the UE deregisters from the UE's HPLMN and immediately selects and registers to an SNPN Hosting Network based on the list in prioritized order. +- Step 5: When the Validity Information is no longer met or if UE no longer needs the SNPN Hosting Network for Localized Services, the UE deregisters from the SNPN Hosting Network, deletes the ***Prioritized list of SNPN Hosting Networks***, and initiates PLMN network selection for returning to Home Network. + +### 6.30.3.2 Steer a UE to an SNPN Hosting Network when the serving network is not UE's Home Network + +If the Home Network of the UE is SNPN or PLMN and the serving network is not the UE's subscribed SNPN or the UE's HPLMN, the steps are same as shown in Figure 6.30.3.1 with an additional step (i.e. step 2 shown in Figure 6.30.3.2-1): + +- Step 2: To report the search result of the available and allowable SNPN Hosting Networks in SR procedure, the UE needs to register to its Home Network using NWu and the N3IWF of the Home Network using the current serving network as underlay network. + +![Sequence diagram illustrating the steps to steer a UE to an SNPN Hosting Network when the serving network is not the UE's Home Network. The diagram shows interactions between the UE, Serving Network, Home Network, and SNPN Hosting Network.](521e2e9d53a2d9c4b3e22d151d46ee23_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SN as Serving Network (Not the UE's Home Network) + participant HN as Home Network (the UE's subscribed SNPN/the UE's HPLMN) + participant SNPN as SNPN Hosting Network + + Note left of UE: 0. UE registers to the serving network (not the UE's Home Network) + UE->>SN: + Note left of UE: 1. The Validity information is about to be met, the UE starts to search any available and allowable SNPN Hosting Network(s) + UE->>HN: 2. UE registers to the UE's subscribed SNPN/HPLMN using the serving network as underlay network + Note right of HN: 3. Initiates SR or MRU for reporting the search results of available and allowable SNPN Hosting Network(s) + HN->>UE: + Note left of UE: 4. Determines the Prioritized list of SNPN Hosting Networks and includes the Prioritized list of SNPN Hosting Networks in response message of SR/MRU + UE->>SNPN: 5. The UE selects and registers to a Hosting Network based on the Prioritized list of SNPN Hosting Networks + Note right of SNPN: 6. When the Validity Information is no longer met, the UE deregisters from the Hosting Network, deletes the prioritized list of SNPN Hosting Networks and initiates SNPN selection/PLMN selection for returning to Home Network + SNPN->>HN: + +``` + +Sequence diagram illustrating the steps to steer a UE to an SNPN Hosting Network when the serving network is not the UE's Home Network. The diagram shows interactions between the UE, Serving Network, Home Network, and SNPN Hosting Network. + +Figure 6.30.3.2-1: The UE's subscribed SNPN/the UE's HPLMN not as the serving network steers the UE to an SNPN Hosting Network + +## 6.30.4 Impacts on services, entities, and interfaces + +UE: + +- supports the *List of SNPN Hosting Networks with Validity Information*. +- supports the *Indication that the UE is only allowed to select a Hosting Network upon Steering by the Home Network*. + +Home Network: + +- determines the *Prioritized list of SNPN Hosting Network* per UE based on the search report from UE. + +## 6.31 Solution #31: Discovery and selection of Hosting network based on broadcast information + +### 6.31.1 Introduction + +This solution targets KI#4. + +It is assumed that the UE is a subscriber of a Localized service and the UE uses the service-level configuration to know when to trigger hosting network discover, i.e. whether the Localized service is available in a specific time period and/or specific location. However, the UE is not aware which networks (i.e. Hosting networks) supporting the Localized service. + +### 6.31.2 Functional Description + +In order to enable a UE to use a Localized service when the UE doesn't know the Hosting network IDs, the UE discovers/selections/accesses a Hosting network supporting the Localized service. It is proposed that the Hosting network supporting Localized service(s) broadcasts information indicating the supported Localized service(s). The broadcast information can be transmitted from NG-RAN or non-3GPP access network of the Hosting networks. + +Following are the characteristics of the solution: + +1. The UE is configured with Localized service information which includes the Localized service identification (e.g. Localized service ID) and information when and where a Localized service is available (i.e. availability conditions like time period and location). This configuration may be provided to the UE from the application layer (e.g. from Localized service provider, LSP): + - a. The LSP may have a service level agreement with Hosting network(s). During the SLA establishment the LSP and the Hosting network has agreed the Localized service ID and the service availability conditions (like time period and location), which the LSP can provide to the UE via the application layer. The LSP would act as CH when the UE accesses the Hosting network. + - b. In one alternative, it is possible that the Home network configures the UE with the Localized service ID and service availability conditions. Here the Home network and the Hosting network should have established SLAs. The Home network would act as CH when the UE accesses the Hosting network. +- 2.- The UE NAS layer requests the AS layer to discover available Hosting networks which broadcast support of the Localized service ID and the availability conditions are fulfilled. + - 2a. The broadcast information (e.g. the SIB of NG-RAN) from the access network includes at least the following parameters: (1) a Hosting NW indication which indicates that the network supports any Localized service; and (2) Localized service identifier and/or (3) Human Readable Service Name (HRSN) identifying the Localized service. + +**Editor's note:** Whether broadcasting the above parameters has potential security and privacy issues is FFS and the security impacts shall be evaluated by SA WG3. + +**NOTE:** The above broadcast information may take local regulations into account. + +3. The UE AS layer creates a list of discovered Hosting networks fulfilling the availability conditions; and reports to the NAS layer the list of discovered Hosting networks. If there are more than one discovered Hosting network broadcasting the Localized service ID, the AS layer may order the Hosting networks, e.g. by using the signal strength. +4. The UE selects a Hosting network from the list of discovered Hosting networks. If automatic network selection is performed and the multiple Hosting networks are discovered in point 3. the UE can select the network with the highest order. If manual network selection is performed, the list of discovered Hosting networks is displayed to the user. +5. The UE starts registration procedure with the selected Hosting network. + +### 6.31.3 Procedures + +The proposed solution reuses the existing functionalities with the following modifications: + +- The RAN System Information (SI) broadcast is specified in TS 38.331 [14]. In addition, the RAN broadcasts the following SI and the UE is able to receive and process this SI: + - Support of Hosting network (or Localized service) indication (e.g. broadcasted in Minimum SI, e.g. SIB1); + - List of supported Localized service IDs (e.g. broadcasted in "Other SI" which is transmitted seldom or on demand). + - List of associated Human-Readable Service Names (HRSN) associated with the Localized service IDs (e.g. broadcasted in "Other SI" which is transmitted seldom or on demand). + +NOTE: The above SI broadcast shall be coordinated and evaluated by RAN WG2. + +- The UE procedure for network selection is specified in TS 23.122 [6]. In addition, this solution requires the following changes: + - Configuration from higher layers about the Localized service ID (which is broadcasted in the SI) and the associated availability conditions. + - The UE can select a serving network by considering the broadcasted supported Localized service IDs and the availability conditions for the Localized service. + +### 6.31.4 Impacts on services, entities, and interfaces + +UE impacts: + +- The ability to be configured for Hosting network discovery including Localized service ID and associated availability conditions. +- Receiving SIB including the supported Localized service ID. +- Selecting a Hosting network based on the available networks supporting the Localized service ID and matching the availability conditions. + +RAN impacts: + +- Enhanced SIB information to announce the support of: + - Hosting network (or Localized service) indication. + - List of supported Localized service IDs. + - List of associated Human-Readable Service Names (HRSN) associated with the Localized service IDs. + +## 6.32 Solution #32: Supporting PNI-NPN as hosting network + +### 6.32.1 Introduction + +### 6.32.2 Functional Description + +If local services are provided via PNI-NPN in a PLMN, CAG cells may broadcast which local services are accessible via the cell. One CAG cell may support multiple local services. The service area of a local service consists of the CAG cells that support the service. The PLMN network is aware of the service area of the local services. + +A local service and CAG capable UE may discover available local services either from the CAG cell broadcast or NAS signalling, e.g. during Registration procedure. If the user is interested in a certain local service, it may request the authorization from the network to access the local service via NAS signalling. The network may determine the authorization based on whether the UE's subscription info allows it and may further interact with the local service provider. If the access to the local service is authorized, the network may provide the necessary configuration, e.g. the update of Allowed CAG list that contains the CAG cells serving the local service, to the UE. The UE may start searching for and accessing CAG cells for local services, e.g. based on the service validity time. + +## 6.32.3 Procedures + +![Sequence diagram showing the discovery and access of local service via PNI-NPN. The diagram involves three main entities: UE, AMF, and RAN (CAG cell). The sequence of messages is: 1. Registration from UE to AMF; 2. Registration Accept from AMF to UE; 3. Service Request from UE to AMF; 4. Check if the UE is authorized for the local service (internal AMF step); 5. Service Accept from AMF to UE; 6. UE Configuration Update from AMF to UE; 7. Triggers searching and selection of CAG cell for local service (internal UE step); 8. PDU Session Establishment for local service (involving UE, RAN, and AMF).](40b80ef077f6151a9fbb593b8ad4864d_img.jpg) + +``` +sequenceDiagram + participant UE + participant AMF + participant RAN as RAN (CAG cell) + + Note right of AMF: 4. Check if the UE is authorized for the local service + Note left of UE: 7. Triggers searching and selection of CAG cell for local service + + UE->>AMF: 1. Registration + AMF-->>UE: 2. Registration Accept (list of local service identifier, corresponding CAG identifiers, Validity time period, ...) + UE->>AMF: 3. Service Request (desired local service identifier) + AMF-->>UE: 5. Service Accept (local service access authorized) + AMF-->>UE: 6. UE Configuration Update (update of Allowed CAG list, ) + Note right of AMF: 8. PDU Session Establishment for local service +``` + +Sequence diagram showing the discovery and access of local service via PNI-NPN. The diagram involves three main entities: UE, AMF, and RAN (CAG cell). The sequence of messages is: 1. Registration from UE to AMF; 2. Registration Accept from AMF to UE; 3. Service Request from UE to AMF; 4. Check if the UE is authorized for the local service (internal AMF step); 5. Service Accept from AMF to UE; 6. UE Configuration Update from AMF to UE; 7. Triggers searching and selection of CAG cell for local service (internal UE step); 8. PDU Session Establishment for local service (involving UE, RAN, and AMF). + +**Figure 6.32.3-1: Discovery and access local service via PNI-NPN** + +1. UE initiates registration with the serving PLMN. The UE may indicate its capability of local service access to the network. + +2. The network provides a list of available local services to the UE. The list may be based on the area where the UE initiates the Registration. Other information such as the CAG identifiers and validity time period corresponding to the local services can also be provided. +3. The user may determine its desired local service and trigger the UE to send a NAS request (e.g. UL NAS Transport) to the network for the authorization to access the desired service. The UE indicates the desired local service identifier in the request. +4. The network checks if the UE is authorized to access the service based on UE's subscription information and may further interact with the local service provider for authorization determination (not shown in the figure). +5. The network returns the authorization result to the UE in a NAS response message (e.g. DL NAS Transport). +6. If the local service access is authorized, the network provides necessary configuration to the UE. The configuration may include the update of Allowed CAG list which contains the CAG IDs that supports the desired local service, DNN associated with the local service, etc. +7. The UE starts searching and accessing the CAG cell that supports the local service. This may be triggered by manual input or based on service available time. +8. The UE establishes PDU Sessions for accessing the local service. + +### 6.32.4 Impacts on services, entities, and interfaces + +#### UE: + +- Supports indication of local service access capabilities to the network. +- Receives local service-related information (service identifiers, validity time period, etc.) via NAS signalling and stores the information. +- Supports new NAS signalling for requesting authorization for access to a local service. + +#### AMF: + +- Determines available local services based on the UE's location. +- Provides local services related information (service identifiers, valid time period, etc.) via NAS signalling to the UE. +- Supports new NAS signalling for requesting authorization for access to a local service and checks authorization based on subscription information. + +#### UDM/UDR: + +- New subscription information on whether UE is allowed to access a local service. + +## 6.33 Solution #33: network selection for accessing to a hosting network + +### 6.33.1 Introduction + +The solution addresses key issue # 4 " Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services ". + +The solution aims to enhance existing network selection specified in TS 23.122 [6], by defining a new list of hosting network(s) that used for UE to perform automatic network selection to access the hosting network for the localized service. + +**Editor's note:** Manual network selection is FFS. + +## 6.33.2 Functional Description + +Based on existing network selection procedure, this solution defines a new list of hosting network that used for accessing to the target hosting network for the localized service when needed. + +A list of hosting network(s) includes at least NPN ID, optional valid time, or/and area information. This list has highest priority for the UE to select when it is used or activated. When the localized service in the hosting network is finished, the list of hosting network is deactivated so that UE can perform normal network selection. + +The following principle applies for the list of hosting network: + +- With highest priority when performing automatic network selection, even higher than HPLMN. Assumed that UE registered to one hosting network successfully for the expected localized service, when UE moves into the coverage of HPLMN, based on existing logic of network selection, UE has to select higher prioritized network(e.g. HPLMN), and then the localized service will be interrupted. So the list of hosting network has higher priority than any other network for UE to perform network selection, including even HPLMN. +- Can be activated or deactivated by UE or home network, e.g. when UE attempts to access the hosting network for the localized service, or when the localized service is finished, or home network sends the instruction to UE, etc. +- Can be pre-configured or dynamic delivered by home network +- Can be used for specific time, or/and, specific area, or/and specific localized service(s). + +**Editor's note:** How to obtain the list of hosting network(s) is FFS. + +## 6.33.3 Procedures + +**Editor's note:** It is FFS for the detailed procedure for discovery and selection for the hosting network based on the new defined list of hosting network. + +## 6.33.4 Impacts on services, entities, and interfaces + +UE impact: + +- A new hosting network list is needed. + +# 6.34 Solution #34: Providing Human Readable Localized Services Information for manual selection + +## 6.34.1 Introduction + +This solution is intended for KI#4, for the case of manual selection of localized services. For manual selection, there may be different scenarios: + +**Scenario 1: The user knows which NPN offers a specific localized service, time and location validity.** + +For example, the user has this information in the ticket of an event, which comes with instructions to access a specific NPN ID (PLMN+NID) or GIN, when entering the venue during the event. + +This scenario would need no further enhancements from what is already defined in Rel-17. + +If a human readable network name is needed, the NPN hosting network can include *SIB10* containing the Human-Readable Network Names (HRNN) of the NPNs listed in *SIB1* (as per Rel-17 specifications). + +**Scenario 2: The user does not know which localized services are available in the area.** + +For this scenario, the user needs to be displayed available localized services in human readable form. + +The localized service information to be displayed to the user may include a localized service name and some additional information regarding the localized service (e.g. pricing, time/location validity, etc.). + +For this scenario, currently defined SIB information for NPN is not enough. + +On the other hand, for NPN hosting networks offering multiple localized services, the amount of human readable information may become large, in which case including human readable information for localized services in regularly scheduled SIB information would be too costly in terms of utilized resources. + +This solution provides non-mutually exclusive alternatives to provide Human Readable Localized Services Information to UE for display to the user. + +## 6.34.2 Functional Description + +### 6.34.2.1 Human Readable Localized Service information in On-Demand SIB + +This alternative reuses on-demand system information acquisition procedure as defined in TS 38.300 [15] and TS 38.331 [14]. The hosting network, on top of already defined SIB information, broadcasts additional information as follows: + +- SIB1 includes information regarding the availability and scheduling (e.g. mapping of SIBs to SI message, periodicity, SI-window size) of the new SIB (SIBxx) with an indication whether this SIBxx is only provided on-demand and, in that case, the configuration needed by the UE to perform the SI request. +- If a UE intends to retrieve this information, the UE performs random access procedure to request the on-demand system information: + - The UE sets the raPurpose to requestForOtherSI or msg3RequestForOtherSI. + - The UE sets the intendedSIBs to indicate the UE wants to receive SIBxx as a result of the SI request. +- Upon request of one or more UEs, the NG-RAN schedules the on-demand SIBxx with Human Readable localized services information. The Human Readable localized services information contains information regarding the localized services that are available via the hosting network, e.g. a descriptive name of the localized service. + +**Editor's note:** Security considerations about broadcasting localized services information are FFS and this shall be evaluated by SA WG3. + +- This information is displayed to the user. + +### 6.34.2.2 Construction of URL for webpage retrieval of Human Readable Localized service information. + +In this alternative, the network broadcasts information, which enables a UE to construct an Internet address from where to retrieve more information about the hosting network and the localized services that can be accessed via the hosting network. This alternative assumes the UE has other means of data connectivity, e.g. the UE is currently connected to a (V/H-) PLMN or another SNPN/PNI-NPN. + +In order to make the broadcasted information efficient, the NG-RAN broadcasts in SIB a code. + +Based on this the UE creates a URL by embedding the key, e.g. as follows: .npn-service-information.com> + +The UE then retrieves localized services information from the webpage identified by the URL via a separate connection, i.e. via a V-PLMN/H-PLMN of another SNPN/PNNI-NPN the UE, and displays it to the user. + +**Editor's note:** The details of the retrieval from webpage are FFS. + +Note that the may include location information, e.g. it may contain .. + +**Editor's note:** Security considerations are FFS and this shall be evaluated by SA WG3. + +## 6.34.3 Procedures + +### 6.34.3.1 Procedure for Human Readable Localized Service information in On-Demand SIB + +![Sequence diagram illustrating the procedure for Human Readable Localized Service information in On-Demand SIB. The diagram shows interactions between a UE and an NG-RAN. Step 1: NG-RAN broadcasts SIB1 with an on-demand indication for SIBxx. Step 2: UE sends a PRACH on-demand SIB request for SIBxx. Step 3: NG-RAN indicates in SIB1 that SIBxx is scheduled. Step 4: NG-RAN broadcasts SIBxx. Step 5: UE displays the SIBxx content to the user.](c1b762c358fd423d6686563b3fde7750_img.jpg) + +``` +sequenceDiagram + participant UE + participant NG-RAN + Note left of UE: 5. Display SIBxx content to user + NG-RAN->>UE: 1. SIB1: SIBxx on-demand indication + UE->>NG-RAN: 2. PRACH: on-demand SIB request SIBxx + NG-RAN->>UE: 3. SIB1: SIBxx scheduled + NG-RAN->>UE: 4. SIBxx +``` + +Sequence diagram illustrating the procedure for Human Readable Localized Service information in On-Demand SIB. The diagram shows interactions between a UE and an NG-RAN. Step 1: NG-RAN broadcasts SIB1 with an on-demand indication for SIBxx. Step 2: UE sends a PRACH on-demand SIB request for SIBxx. Step 3: NG-RAN indicates in SIB1 that SIBxx is scheduled. Step 4: NG-RAN broadcasts SIBxx. Step 5: UE displays the SIBxx content to the user. + +**Figure 6.34.3.1-1: Procedure for Human Readable Localized Service information in On-Demand SIB** + +1. NG-RAN broadcasts SIB1 which includes information regarding the availability and scheduling (e.g. mapping of SIBs to SI message, periodicity, SI-window size) of the new SIB (SIBxx) with an indication whether this SIBxx is only provided on-demand and, in that case, the configuration needed by the UE to perform the SI request. +2. If a UE intends to retrieve this information, and SIB1 indicates SIBxx on demand only, the UE performs random access procedure to request the on-demand system information: + - The UE sets the raPurpose to requestForOtherSI or msg3RequestForOtherSI. + - The UE sets the intendedSIBs to indicate the UE wants to receive SIBxx as a result of the SI request; +3. Upon request of one or more UEs, the NG-RAN indicates in SIB1 the scheduling of SIBxx. +4. NG-RAN broadcasts SIBxx as scheduled in SIB1. +5. The UE that made the request in step 2, and any other UE also interested in SIBxx, receive SIBxx, and display the SIBxx content, i.e. the Human Readable Localized Services information, to the user. + +NOTE: The procedure described in this clause already exists in TS 38.300 [15] and TS 38.331 [14]. Only addition is the specific use a new SIBxx that contains human readable localized services information. The procedure shall be evaluated by RAN WG2. + +### 6.34.3.2 Procedure for retrieval of Localized service information from URL + +![Sequence diagram illustrating the procedure for retrieval of Localized service information from URL. The diagram shows interactions between UE, NG-RAN, and a Server (URL).](1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant Server as Server (URL) + Note left of UE: 0. Already connected to another network + Note right of NG-RAN: Network UE is connected to + NG-RAN->>UE: 1. SIB: + Note left of UE: 2. UE constructs URL with + Note right of Server: 3. Retrieve Localized services information from server (URL) + UE->>Server: + Note left of UE: 4. Display content to user + +``` + +Sequence diagram illustrating the procedure for retrieval of Localized service information from URL. The diagram shows interactions between UE, NG-RAN, and a Server (URL). + +**Figure 6.34.3.2: Procedure for retrieval of Localized service information from URL** + +0. UE has internet access via V-PLMN/H-PLMN, SNPN, PNI-NPN, WLAN or other means. + 1. NG-RAN broadcasts in SIB. The code may be included in SIB10, in new SIBxx (potentially on-demand as in clause 6.34.2.1) or both. + 2. Based on this the UE creates a URL by embedding the key, e.g. as follows: .npn-service-information.com> + 3. The UE then retrieves the webpage identified by the URL. +- Editor's note:** The details of the retrieval from webpage are FFS. +4. UE displays retrieved information to the user. + +### 6.34.4 Impacts on services, entities, and interfaces + +#### RAN: + +- For on-demand SIB alternative: new on-demand SIB support (no new procedure in RAN). +- For construction of URL based on code: transmit code for URL construction in SIB. + +#### UE: + +- For on-demand SIB alternative: new on-demand SIB support (no new SIB acquisition procedure in UE). +- For construction of URL based on code: construct URL based on code received in SIB. Retrieve information from URL. +- Retrieval of localized services information from URL. + +## 6.35 Solution #35: Access to localized service by network slicing and URSP + +### 6.35.1 Introduction + +This solution addresses Key Issue #5: Enabling access to localized services via a specific hosting network. + +More specifically the solution addresses step H6 of solution 7. + +The basic principles of this solution is reusing existing architectures and functionalities e.g. network slicing and URSP. + +## 6.35.2 Functional Description + +The following are the assumptions for this solution: + +1. Hosting network: + - can be a PNI-NPN (i.e. a PLMN) or an SNPN; + - uses dedicated network slice(s) for localized services: + - A dedicated network slice is defined to be available in the area of the served localized services, and available at least for the duration of the localized service. +2. Home network: + - can be a PNI-NPN (i.e. a PLMN) or an SNPN; + - The home network and hosting network can be the same network. +3. PCF is configured with information for localized services or retrieves the information from UDR. +4. Home network services can be accessed either using roaming architecture with N16/N9 or via N3IWF. +5. The UE uses the credentials of the home network to access the hosting network. + +## 6.35.3 Procedures + +![Sequence diagram for Registration in the hosting network. The diagram shows interactions between UE, Hosting Network AMF, Hosting Network PCF, Home Network AUSF, Home Network UDM, and Home Network H-PCF. The process includes registration request, authentication, Nudm_UECM_Registration, AM Policy Association Establishment/Modification, UE Policy Association Establishment, registration accept, UE Configuration Update Procedure, Registration, Change cell, and PDU Session Establishment.](9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HN_AMF as Hosting Network AMF + participant HN_PCF as Hosting Network PCF + participant HO_AUSF as Home Network AUSF + participant HO_UDM as Home Network UDM + participant HO_H_PCF as Home Network H-PCF + + Note left of UE: 8. Registration + Note left of UE: 9. Change cell + Note left of UE: 10. PDU Session Establishment + + UE->>HN_AMF: 1. Registration request (Requested NSSAI) + HN_AMF->>HO_AUSF: 2. Authentication + HO_AUSF->>HO_UDM: 3. Nudm_UECM_Registration, Nudm_SDM_Get, Nudm_SDM_Subscribe + HO_AUSF->>HN_AMF: 4. AM Policy Association Establishment/Modification + HN_AMF->>HN_PCF: 5. UE Policy Association Establishment + HN_AMF->>UE: 6. Registration accept + HN_AMF->>HN_PCF: 7. UE Configuration Update Procedure + +``` + +Sequence diagram for Registration in the hosting network. The diagram shows interactions between UE, Hosting Network AMF, Hosting Network PCF, Home Network AUSF, Home Network UDM, and Home Network H-PCF. The process includes registration request, authentication, Nudm\_UECM\_Registration, AM Policy Association Establishment/Modification, UE Policy Association Establishment, registration accept, UE Configuration Update Procedure, Registration, Change cell, and PDU Session Establishment. + +**Figure 6.35.3-1: Registration in the hosting network** + +The Registration procedure in TS 23.502 [4] is used with following modifications with the assumption that hosting network and home network is not the same network and that the UE therefore does not have e.g. S-NSSAI configured for the hosting network (if the hosting network and home network is the same network then UE can already have the S-NSSAI and the PCF can provide URSP rules to the UE): + +NOTE: The UE has previously performed step H5 of solution 7 i.e. UE discovers/selections the hosting network when the conditions of the localized service are about to be met. + +- 1.- The UE provides Requested NSSAI if available as per existing procedures. +2. Primary authentication is performed as per existing procedures. +3. AMF and UDM service operations as per existing procedures. + +4. AM Policy Association Establishment as per existing procedures. +5. UE Policy Association Establishment as per existing procedures. Potential enhancement introduced in study FS\_eUEPO can be utilized for URSP rule determination. This can involve H-PCF if the hosting network is a PNI-NPN and home network is a PLMN. +6. As per existing procedures i.e. the AMF provides the Configured NSSAI including the S-NSSAI of hosting network that is to be used for the localized service and the Mapped Configured NSSAI including the S-NSSAI of the home network. +7. PCF in hosting network provides the UE with URSP rules with RSD identifying the localized service and S-NSSAI and DNN in hosting network to be used. PCF in hosting network determines which localized services are granted to UE and the corresponding URSP rules based on SLA and the information stored in UDR in the hosting network. Optionally, the URSP rule includes validity conditions for the related URSP rule e.g. time window and a location where the localized service is valid. +8. The UE registers the network slice to be used for the localized service. +9. The existing mechanisms are used to change the NG-RAN resources for the UE e.g. to a dedicated cell/TA to be used for the localized services. Mechanism can be based on RFSP, Allowed NSSAI or Target NSSAI or other available mechanisms. This can happen after step 10. +10. The UE establishes a PDU Session to access the localized services as per the URSP rule for the localized service. + +### 6.35.4 Impacts on services, entities, and interfaces + +UE/PCF: + +- Support of traffic descriptor in the URSP rule to identify the localized services. + +PCF: + +- The PCF is able to provide the UE with UE policies (URSP) according to validity conditions for localized services, and remove the URSP rules after the end of the localized service. + +## 6.36 Solution #36: Steering of UEs by home network to a specific hosting network with consideration of location, times, and coverage for key issue #5 + +### 6.36.1 Introduction + +One of the aspects in Key issue #5 is about how home network determines the need to steer or instruct UE with the consideration of the location, times, and coverage of the hosting network, as required by TS 22.261 [2]. Because it's for local services, the coverage of the hosting network and the localized services normally are limited to certain area(s) (e.g. stadium, school campus, etc) within possible limited operation time. Therefore, it's important for home network to steer or instruct a UE to the specific hosting network while the UE is a location with good coverage of the hosting network and services. + +There can be two options to make sure UE being steered to a local network with satisfying those considerations: + +- Option 1:** UE-based: Home network provides hosting network selection policy to UE with the location and coverage validity conditions, so UE can use those policy to select the valid hosting network which match those conditions. This option fully relies on UE to make decision on whether the conditions are met and when to move to the local network after receiving the instruction from the home network, while the home network may lack knowledge of the UE's location and the coverage from the target hosting network in UE's location when the home makes steering decision. +- Option 2:** Network-and-UE-coordination based: Home network coordinates with UE to obtain UE location and the reception performance of the target hosting network in UE's location, before the home network makes steering decision to instruct UE to steer to the target hosting network. + +## 6.36.2 Functional Description + +For option 1 (UE-based), new selection conditions can be added into hosting network selection policy, such as location, time (includes start, end, or operation duration time of the network), and signal strength threshold. UE will only select and access the hosting network which meets those defined conditions. + +For option 2 (Network-and-UE-coordination based), for the home network to precisely steer the UE to the suitable hosting network based on UE's present location to avoid steering UE to a network which UE can't receive good coverage in that location, the home network may want to have the latest network performance status of the potential candidate hosting network in that area. Knowing the potential target network coverage for the UE(s) to be steered to may not be the reason for steering, instead it's used by the home network to check if the target network(s) are suitable for the UE with good coverage. + +There are 2 methods for option 2: + +- Method 1: The home network can use that UE location information to query the network performance information (e.g. performance analytics or Observed service experiences related network data analytics) from the target hosting SNPN in that UE location via target hosting SNPN's NEF. Based on the information from target network hosting SNPN, the home network decides if the hosting network is suitable for UE to be steered to or not. This method is from the network point of view with data being collected from the target network to determinate and predict if UE is in the good service coverage of target network or not. This method may not reflect the real UE experience in that location. +- Method 2: The home network can instruct UE to measure and report the signal reception status of the potential target hosting network(s). This can be realized via enhancing the UCU or UPU procedures. The signal reception status information from UE can be simple indication if those candidate network's signal strength is below or pass a defined signal strength threshold defined in UE's policy or the report instruction from home network, without requiring to UE to report detail information of the target network. + +## 6.36.3 Procedure + +### 6.36.3.1 UE-based procedure + +The procedure will use the same procedure as defined in clauses 5.30.2.4 and 5.30.3.4 of TS 23.501 [3] for NPN hosting network selection with the new added validity condition consideration, such as location, time, and coverage. + +### 6.36.3.2 UE-and-Network-coordination- based procedure + +![Sequence diagram illustrating the UE-and-Network-coordination-based procedure for steering UE to a target network. The diagram shows two methods for determining network coverage before sending a Steering of Roaming (SoR) instruction.](9874e3ac6f14360133f8e1674f79824f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Hosting SNPN B + participant Home network D + + Note left of UE: Method 1 + Note right of Home network D: 1a. Nnef_AnalyticsExposure_Fetch ( Network performance with UE1 location) + Note right of Home network D: 2a. Nnef_AnalyticsExposure_Fetch Response + + Note left of UE: Method 2 + Note right of Hosting SNPN B: 1b. UPU ( Update UE policy on measure for network B signal with a signal threshold) + Note right of Home network D: 2b. UPU ACK (indication that network B signal strength is higher than given threshold) + + Note right of Home network D: 3. Network B coverage in UE1 location is good enough + Note right of Home network D: 4. Sends SoR with target network B + +``` + +The diagram illustrates a sequence of interactions between a User Equipment (UE), a Hosting SNPN B, and a Home network D. It is divided into two methods for determining network coverage before sending a Steering of Roaming (SoR) instruction. + +**Method 1:** + +- 1a. Home network D sends a request (Nnef\_AnalyticsExposure\_Fetch) to Hosting SNPN B to get network performance information for UE1's location. +- 2a. Hosting SNPN B responds with the requested information (Nnef\_AnalyticsExposure\_Fetch Response). + +**Method 2:** + +- 1b. Home network D sends an Update UE policy (UPU) to the UE, instructing it to measure the signal strength of Hosting SNPN B with a specific threshold. +- 2b. The UE responds with a UPU ACK, indicating that the signal strength of Hosting SNPN B is higher than the given threshold. + +Based on the results from either Method 1 or Method 2, Home network D determines that the network B coverage in UE1's location is good enough. It then sends a SoR instruction (step 4) to the UE, steering it to the target network B. + +Sequence diagram illustrating the UE-and-Network-coordination-based procedure for steering UE to a target network. The diagram shows two methods for determining network coverage before sending a Steering of Roaming (SoR) instruction. + +Figure 6.36.3.2-1 + +In this example, UE1 is connecting with the home network before home network decides to steer UE to other hosting network. Home network D wants to steer UE1 to hosting SNPN B in that area because user or home network wants to use a specific local service which can't be accessed by home network or other business reasons. Before home network sending steer instruction to UE, home network needs to make sure UE1 is in the good coverage of SNPN B. + +#### For method 1: + +- 1a. Home network D queries network performance Analytics or observed Service Experience related network data analytic for the area of UE1 location as defined in clauses 6.6 and 6.4 of TS 23.288 [17], via NEF provided by SNPN B. +- 2a. SNPN B provides home network D with the network performance or service experience information of the queried area, which indicates UE1 may be in the good coverage area of SNPN B and expected to received good connection services. + +#### For method 2: + +- 1b: Home network D uses UPU to update a UE policy to trigger UE to measure the signal strength of hosting SNPN B with the defined threshold. +- 2b: UE1 responses home network D UPU ACK with reporting an indication that the signal threshold of SNPN B is higher than the threshold. +- 3: Based on the report from either method 1 or method 2, Home network D knows UE1 is in the good coverage of hosting network SNPN B. +4. Home network D sends SoR instruction to steer UE1 to hosting SNPN B. + +## 6.36.4 Impacts on services, entities and interfaces + +### Option 1 UE-based: + +UE: + +- Supports network selection considering the new validity conditions which are part of UE network selection policy provided by the home network. + +#### Option 2 Network-and-UE-coordination based (Method 2): + +UE: + +- Receives new hosting network measurement policy from home network. +- Reports if the hosting network signal strength is higher or lower than the signal threshold provided by the home network. + +UDM: + +- Provides UE the hosting network measurement policy including the signal threshold of hosting network which UE can compare with and report to the home network if the actual measurement is higher or lower than this threshold. +- Receives the report from UE on if the hosting network signal strength is higher or lower than the signal threshold provided by the home network. + +## 6.37 Solution #37: Enabling access to localized services via a specific hosting network + +### 6.37.1 Introduction + +This is a solution to Key Issue #5, "Key Issue #5: Enabling access to localized services via a specific hosting network". + +This key issue aims at addressing the following aspects: + +- How and whether the home network, determines the service availability of a hosting network, and interacts with hosting network to authorize home network's subscribers to access home network services via the hosting network, at certain time and location, coverage of the hosting network and services offered by the hosting network. +- How to enable UE to access both home network services and localized services via the hosting network, and seamless service continuity for home network services and localized services when UE moves between different networks providing the same services. This includes how to configure UE with information enabling the UE to be aware of services that can be accessed via a specific network (e.g. home network or hosting NPN). +- How home network determines the need to steer or instruct the UE, and how the home network steers or instructs the UE to select a hosting network for obtaining home network services or localized services or to select a network for a specific service which is available from both hosting and home network. + +### 6.37.2 Functional Description + +The solution defines a new network function LSF (Localized Service Function) in the home network and hosting network that specifically handles information related to localized services. The LSF in the hosting network maintains UE subscription information and the locations it has agreement with the home network to provide service. + +This new Network Function will provide information to AMF about all localised services that are available at the UE location. This information can be indicated to the UE during the registration procedure or after it is registered. The availability of the localized services will be indicated to the UE using NAS signalling message. + +Activation or deactivation of any new localized service in the location is handled by this new NF or updated in the new NF. + +3rd Party Application Server can contact the LSF to configure number of users allowed (dynamic load balancing) (e.g. AF) via the NEF (after NEF has verified the 3rd Party Application Server contacting it). + +Various localized services can be provided by the hosting network. The list of all such localized services at various locations is maintained by the LSF. The user will be informed of all such various localized services, provided by the same hosting network, using NAS signalling messages or over the user plane. This will help users to make an informed selection or activation of localized services on the local hosting network. + +**Editor's note:** How the LSF can communicate with the UE via user plane in FFS. + +The LSF would be accessible within the NPN Core Network and it keeps track of one or more location based services for different coverage locations in PLMN or NPN. + +The AMF can query the LSF in order to determine the presence of localised services for the UE location and the LSF provides the list of localised services to the AMF. + +Once the AMF determines that location services can be provided in a certain location, utilizing the Home Routed roaming architecture, the core network can then provide services offered by home network and simultaneously offload localized service traffic to the hosting network. + +**Editor's note:** How offloading of localized service traffic to the hosting network is realized is FFS. + +LSF provides "event based" reporting to NFs (e.g. AMF) to dynamically update the AMF about any services that are currently available based on load conditions. + +**Editor's note:** What the "load conditions" are is FFS. + +**Editor's note:** How subscriber data is considered is FFS. + +### 6.37.3 Procedures + +### 6.37.4 Impacts on services, entities and interfaces + +UE: + +- NAS support for LSF-related functionality. + +AMF: + +- New interface messages between LSF and AMF. +- NAS support for LSF-related functionality. + +LSF: + +- Maintains list of available localized services and provides it to UE via AMF. + +NEF: + +- Provides API for LSF-related functionality. + +## 6.38 Solution #38: Sequential deregistration by hosting network + +### 6.38.1 Introduction + +The solution addresses the KI#6: Support for returning to the home network. The congestion of home network is unavoidable if large number of UEs return to the home network as soon as Localized service is terminated. This solution proposes to control the number of returning UE based on service level agreement between the home network and hosting network. + +### 6.38.2 Functional Description + +This solution assumes that + +- There is service level agreement between the home network and hosting network. + +- The hosting network configures the AMF with maximum number of returning UEs for the given units of time for each of home network, e.g. 10 UEs per second for PLMN A. The home network operator can determine the maximum number of returning UEs e.g. considering the network processing capability and notifies it to the hosting network via service level agreement. +- The AMF of hosting network knows termination time of Localized services. + +When the Localized service is terminated, the AMF of hosting network triggers deregistration procedure. The AMF selects UEs from different home networks considering maximum number of returning UEs configured in the AMF. The AMF triggers deregistration for the selected UEs in sequence and ensures that number of returning UEs for each home network does not exceed the configured maximum number of returning UEs for the given units of time. + +NOTE 1: If many UEs trigger deregistration without waiting for network initiated deregistration, the AMF cannot control the number of returning UEs. In order to give some time to the AMF to trigger deregistration in a sequence manner, service termination time provided to the UE can be later than the actual service termination time. The time gap can be determined considering the expected number of returning UEs and maximum number of returning UEs for the given units of time for the home network. + +NOTE 2: How the AMF enforces maximum number of returning UE is not specified by 3GPP specification and it is up to implementation. + +### 6.38.3 Procedures + +![Sequence diagram showing the overall procedure for UE registration and service termination in a hosting network.](3dcf40a20068ca8624a8d8bbc79bdb87_img.jpg) + +``` +sequenceDiagram + participant UE + participant AMF as Hosting network AMF + Note right of AMF: 1. Configured with maximum number of returning UEs for the given units of time for each of home networks + UE->>AMF: 2a. Registration Request + Note right of AMF: 2b. Stores Home network of the UE + AMF-->>UE: 2c. Registration Accept + Note right of AMF: Service termination + AMF-->>UE: 3a. Deregistration Request (service terminated) + UE-->>AMF: 3b. Deregistration Accept +``` + +The diagram illustrates the interaction between a User Equipment (UE) and a Hosting network AMF. The sequence of events is as follows: 1. The AMF is pre-configured with the maximum number of returning UEs for each home network. 2. The UE sends a Registration Request (2a) to the AMF, which stores the home network information (2b) and responds with a Registration Accept (2c). 3. Upon service termination, the AMF sends a Deregistration Request (3a) to the UE, which responds with a Deregistration Accept (3b). + +Sequence diagram showing the overall procedure for UE registration and service termination in a hosting network. + +Figure 6.38.3-1: Overall procedure + +1. The AMF is configured with the maximum number of returning UEs for the given units of time for each of home network. +2. The UE registers to the hosting network for localized service. The AMF stores the home network of the UE. + +When the UE registers to the hosting network, the AMF needs to identify the home network of the UE in order to associate the configuration in step 1 with the UE. The Registration Request from the UE includes valid 5G-GUTI (and optionally NID in the case of SNPN assigned case) regardless of whether the 5G-GUTI is assigned by PLMN or SNPN (See NOTE). Based on the received 5G-GUTI (and optionally NID), the AMF in hosting network knows home network of the UE. + +NOTE 1: 5G-GUTI is assigned by PLMN or SNPN the UE last registered with. In the case of roaming, the UE provide 5G-GUTI assigned by roaming network. Then AMF applies the maximum number of returning UEs of the roaming network. + +3. After Localized service is terminated, the AMF triggers deregistration in a sequence manner so that the number of returning UEs does not exceed the configured maximum number of returning UEs. The AMF indicates that Localized service is terminated in the Deregistration Request message. The UE returns to the home network. The UE does not re-register to the hosting network again based on received indication from the AMF. + +NOTE 2: The AMF can also take into account UE-initiated deregistered UEs when the AMF enforces maximum number of returning UE. + +## 6.38.4 Impacts on services, entities, and interfaces + +UE: + +- If the AMF indicates that Localized service is terminated in the Deregistration Request message, the UE finishes deregistration procedure and returns to the home network. +- The UE includes valid 5G-GUTI (and optionally NID in the case of SNPN assigned case) regardless of whether the 5G-GUTI is assigned by PLMN or SNPN. + +AMF: + +- The AMF is configured with maximum number of returning UEs for the given units of time for each of home network. The AMF triggers deregistration in a sequence manner so that number of returning UEs does not exceed configured maximum number of returning UEs. +- The AMF indicates that Localized service is terminated in the Deregistration Request message. + +## 6.39 Solution #39: Local hosting network specific back-off timer + +### 6.39.1 Introduction + +This solution addresses the Key Issue #6. + +When a PLMN cannot accept a registration request due to congestion, the PLMN rejects the registration request with 5GMM cause value #22 (congestion) and assigns a value for back-off timer T3346 [7]: + +*If the initial registration request is rejected due to general NAS level mobility management congestion control, the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346.* + +*If the mobility and periodic registration update request is rejected due to general NAS level mobility management congestion control, the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346.* + +Assigning random back-off timer values from a pre-defined range that is the same for all different hosting networks may lead to unnecessary waiting time when the users return to their home network. As a local hosting network that provides localized services can be a temporary network, provide specific service(s) for a limited time (minutes to hours) and serve a variety of number of subscribers from different home networks (very low to very high number of users accessing the localized service), there can be a local hosting specific back-off timer range which can be used to spread out re-registration request from home network subscribers in a more effective way by means of waiting time. For example, if the number of users accessing to a hosting network is relatively small, a shorter range of backoff timer may be considered for these users. + +This solution proposes a local hosting network-specific flexible back-off timer range and back-off timer assignment to spread out the registration attempts over time and limit the number of users attempting to register back to their home network simultaneously in order to avoid signalling overload and unnecessary waiting times for the returning users. + +## 6.39.2 Functional Description + +The proposed solution focuses on hosting network-specific timer range that is used to trigger network re-selection process for the home network subscribers that have just terminated the local service. + +When a UE has connected to a hosting network for a localized service(s) and attempted to register back to its home network, the UE uses a new registration type or indicator to indicate that the UE was temporarily connected to a local hosting network and now is requesting a re-registration to its home network. In this new registration type or indicator, the UE also indicates the identifier of the hosting network to its home network. + +When a home network receives simultaneous registration requests with the hosting network re-registration information from a high number of its subscribers and cannot accept all the registration requests (congestion), the home network rejects the registration requests with a local hosting network-specific back-off timer. + +The home network uses the hosting network identifier information provided along with the new registration type or indicator sent by the UE, determines a local hosting network-specific back-off timer range that is specific to the identified local hosting network and assigns a value for a back-off timer to the UE from the local hosting network-specific back-off timer range. + +## 6.39.3 Procedures + +Figure 6.39.3-1 shows the flow of registration request with hosting network re-registration information and home network response to spread out any congestion by making use of local hosting network identifier and local hosting network specific timer range. It is worth to note that the given flow only considers the case when there is a congestion. In the case that there is no congestion, the home network can handle the registration request with the hosting network re-registration information conventionally and sends a registration accept message. + +![Sequence diagram illustrating the Application Function based network re-selection triggering procedure. The diagram shows three participants: UE, (R)AN, and Home Network AMF. The sequence of messages is: 1. UE sends a REGISTRATION REQUEST (5GS registration type indicates hosting network re-registration along with the local hosting network identifier) to the Home Network AMF via the (R)AN. 2a. The Home Network AMF determines the local hosting network-specific back-off timer range and chooses a back-off timer value from the range. 2b. The Home Network AMF sends a REGISTRATION REJECT (5GMM cause indicates that there is a congestion and provides a back-off timer chosen from the local hosting network-specific timer range) to the UE via the (R)AN. 3. The UE waits until the expiry of the back-off timer to attempt registration.](4c3cf5d00a9dfdf1705e49f7f3a3d93a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant Home Network AMF + Note right of UE: 1. REGISTRATION REQUEST (5GS registration type indicates hosting network re-registration along with the local hosting network identifier) + UE->>Home Network AMF: 1. REGISTRATION REQUEST + Note right of Home Network AMF: 2a. Determine the local hosting network-specific back-off timer range and choose a back-off timer value from the range. + Home Network AMF->>UE: 2b. REGISTRATION REJECT (5GMM cause indicates that there is a congestion and provides a back-off timer chosen from the local hosting network-specific timer range) + Note left of UE: 3. UE waits until the expiry of the back-off timer to attempt registration. + +``` + +Sequence diagram illustrating the Application Function based network re-selection triggering procedure. The diagram shows three participants: UE, (R)AN, and Home Network AMF. The sequence of messages is: 1. UE sends a REGISTRATION REQUEST (5GS registration type indicates hosting network re-registration along with the local hosting network identifier) to the Home Network AMF via the (R)AN. 2a. The Home Network AMF determines the local hosting network-specific back-off timer range and chooses a back-off timer value from the range. 2b. The Home Network AMF sends a REGISTRATION REJECT (5GMM cause indicates that there is a congestion and provides a back-off timer chosen from the local hosting network-specific timer range) to the UE via the (R)AN. 3. The UE waits until the expiry of the back-off timer to attempt registration. + +Figure 6.39.3-1: Application Function based network re-selection triggering procedure + +Procedure: + +1. UE sends REGISTRATION REQUEST message to its home network. In order to indicate that the UE has temporarily accessed to local service(s) provided by a local hosting network, UE includes an information in the REGISTRATION REQUEST message along with the local hosting network identifier. +2. In steps 2a and 2b, it is considered that there is a congestion due to having high number of users sending REGISTRATION REQUEST messages to their home network and the home network cannot handle that many simultaneous registration requests. Therefore, in step 2a, the home network AMF determines the range of the local hosting network-specific back-off timer and assigns a value to UE from that range. In step 2b, the 5GMM cause that indicates the congestion and home network AMF provides the chosen back-off timer in the REGISTRATION REJECT message to the UE. +3. If the UE received the REGISTRATION REJECT message along with the local hosting network related 5GMM congestion cause and the associated timer, the UE waits until the expiry of the allocated back-off timer value. + +Upon the expiry of the back-off timer, the UE repeats step 1 and sends another REGISTRATION REQUEST message. + +## 6.39.4 Impacts on services, entities and interfaces + +AMF: + +- Support a new registration request type/indicator related local hosting network re-registration (i.e. "re-registration from hosting network" or "local network access indication"). +- Support a local hosting network-specific back-off timer range assignment. + +UE: + +- Support sending of the new registration request (i.e. "re-registration from hosting network" or "local network access indication"). + +## 6.40 Solution #40: Credential provisioning for accessing hosting network + +### 6.40.1 Introduction + +This solution addresses the Key Issue #4 aspect regarding how UE is provisioned with credential to access hosting network, and the Key Issue #5 aspect regarding how home network to steer UE to the hosting network. + +This solution covers the function described in solution #7 step H4 and step H5. + +### 6.40.2 Functional Description + +Based on the principle of User Plane Remote Provisioning mechanisms specified in clause 5.30.2.10.4.4 of TS 23.501 [3], this solution enables the provisioning of hosting network credentials to UE. + +This solution assumes hosting network is SNPn. + +UE is assumed to have regular network credential(s) from a home network (e.g. a credential from a PLMN operator) and is currently registered in a serving network which can be the home network itself, or another network that UE is using home network credential to access. + +UE is also assumed to be provisioned with information related localized service, such as which hosting networks can provide access to the desired localized service. The solution for provisioning localized service information is addressed by other solutions. + +### 6.40.3 Procedures + +![Sequence diagram illustrating the credential provisioning procedure for accessing a hosting network. The diagram shows interactions between a UE, (R)AN, AMF, SMF, PCF, AUSF, UDM, and PVS across two networks: Serving Network and Home Network. The steps are: 0. Registration procedure; 1. UE is provisioned with information related to localized service; 2. End user/UE makes a selection of hosting network(s) or localized service(s); 3. PDU Session Establishment Request; 4. PDU Session Establishment Response; 5. User Plane Remote Provisioning of credential to access the selected hosting network; 6. Redirection of UE to hosting network, or; UE performs network selection to hosting network.](50a63fe40eaa16cb8745c689fe8f8264_img.jpg) + +``` + +sequenceDiagram + participant UE + participant (R)AN + participant AMF + participant SMF + participant PCF + participant AUSF + participant UDM + participant PVS + + Note over UE, (R)AN, AMF, SMF, PCF: Serving Network + Note over AUSF, UDM: Home Network + + Note over UE, (R)AN, AMF, SMF, PCF, AUSF, UDM: 0. Registration procedure + Note over UE, (R)AN, AMF, SMF, PCF, AUSF, UDM: 1. UE is provisioned with information related to localized service + + Note left of UE: 2. End user/UE makes a selection of hosting network(s) or localized service(s) + UE->>SMF: 3. PDU Session Establishment Request + SMF-->>UE: 4. PDU Session Establishment Response + + Note over UE, (R)AN, AMF, SMF, PCF, AUSF, UDM: 5. User Plane Remote Provisioning of credential to access the selected hosting network + + Note left of UE: 6. Redirection of UE to hosting network, or; UE performs network selection to hosting network + +``` + +Sequence diagram illustrating the credential provisioning procedure for accessing a hosting network. The diagram shows interactions between a UE, (R)AN, AMF, SMF, PCF, AUSF, UDM, and PVS across two networks: Serving Network and Home Network. The steps are: 0. Registration procedure; 1. UE is provisioned with information related to localized service; 2. End user/UE makes a selection of hosting network(s) or localized service(s); 3. PDU Session Establishment Request; 4. PDU Session Establishment Response; 5. User Plane Remote Provisioning of credential to access the selected hosting network; 6. Redirection of UE to hosting network, or; UE performs network selection to hosting network. + +**Figure 6.40.3-1: Credential provisioning for accessing hosting network** + +0. UE registers in a serving network using home network credential. +1. UE is provisioned with information related localized service, such as which hosting networks can provide access to the desired localized service (e.g. Solution #24), optionally credential related information (e.g. PVS address, etc) for accessing localized service, and at the same time provisioned with network capability to support User Plane Remote Provisioning of credential for accessing hosting network. +2. End user makes a selection of one or more specific hosting network(s) to access the desired localized service, or one or more specific localized service. + +If the UE is provisioned with Credentials Holder controlled priority list for SNPN selection (see TS 23.501 [3] clause 5.30.2.3) and the priority lists are used for hosting network selection, UE can determine whether its home network credential can be used to access the hosting network, by comparing the priority lists with the information received in step 1. If home network credential can be used to access the desired hosting network, step 3 to 5 are skipped. + +NOTE: Whether and how the Credential Holder controlled priority lists are extended for hosting network selection is discussed by other solutions. + +3. The UE initiates the PDU Session Establishment procedure for remote provisioning of credential related information (e.g. PVS address, etc). Along with a PDU Session Establishment procedure, UE can request for credential related information (e.g. PVS address, etc) of the hosting networks for accessing localized service if it is not already provisioned. + +The UE's request of credential related information includes one or more identifier(s) of the selected hosting network(s), and/or one or more identifier(s) of the selected localized service(s). + +The UE's request can be either as part of the UL NAS Transport message or inside the PDU Session Establishment Request message which is the payload container of the UL NAS Transport message. + +4. PDU Session Establishment is accepted by SMF. + +AMF or SMF has a locally configured mapping table between [Credential Information] and [Hosting network identifier] for a specific localized service. AMF or SMF can return the corresponding [Credential Information] to the UE, based on UE's request and the configured mapping table. + +Whether it is AMF or SMF to return the [Credential Information] to UE, depends on if the UE's request is part of UL NAS Transport message, or is inside the PDU Session Establishment Request message. + +The [Credential Information] associated with one hosting network in the mapping table consists of: + +- Indication of whether home network credential can be used as CH credential for the hosting network, if the serving network is the home network; +- FQDN or IP address of the PVS. + +UE can request network to return all available hosting network's credential information for the desired localized service, by specifying the localized service identifier in the request. + +5. UE connects to the PVS for remote provisioning of credential, and stores information associated with the newly obtained credential, e.g. the corresponding hosting network, the type of the credential (native or Default UE Credentials), etc. If home network credential can be used as CH credential to access the hosting network SNPN, this step can be omitted. + +If home network credential can be used as CH credential to access the hosting network SNPN, automatic network selection can be applied. + +6. The UE initiates the de-registration procedure. If the selected localized service(s) are about to start (or have started), the UE needs to select the hosting network. + +If the serving network is home network, the redirection to hosting network can be triggered as below: + +- The UE includes in the de-registration request the identifier of the selected hosting network for accessing a localized service; or +- The UE indicates in the de-registration request message with cause "redirection is requested", if in step 3 only single hosting network identifier is requested by UE and the request is handled by AMF. + +After de-registration accept, the AMF informs the NG-RAN via NGAP about the selected hosting network identifier, e.g. as new IE in the UE CONTEXT RELEASE COMMAND for that UE. If the NG-RAN is aware of neighbouring cells within the UE's selected hosting network identifier, the NG-RAN assists the UE in finding the hosting network by sending an RRC release with redirect message (frequency and optionally cell information) or RRC release with multiple frequencies to the UE. + +- If the UE does not receive any redirect information in the RRC release message, the UE performs cell/network search to find/select the hosting network. + +## 6.40.4 Impacts on services, entities, and interfaces + +UE: + +- Request Credential information by indicating the selected hosting network(s) or selected localized service(s). +- Use the obtained credential based on the associated type to access hosting network. +- Indicate to the network during de-registration a redirection to hosting network is preferred. + +AMF/SMF: + +- Configure the mapping of [Credential Information] and [Hosting network identifier] for specific localized service +- Respond to UE with proper [Credential Information] associated with a hosting network SNPN. + +AMF/RAN: + +- Redirect the UE to hosting network based on the input from UE. +- Extend the NG-AP message (UE CONTEXT RELEASE COMMAND) and RRC message (RRC Release) with hosting network redirection information. + +## 6.4.1 Solution #41: Provisioning of Credentials via Hosting Network PDU Session + +### 6.4.1.1 Introduction + +This solution takes ideas from Sol#22. + +This solution is mainly focuses on Key Issue#4 regarding how to provision UE with credentials for Localized service. It tries to solve the case of how to access Localized services when UE has neither any prior subscription with Hosting network nor with the Localised service provider (clause 5.7 of TR 22.844 [12]). The solution thus proposes how Hosting network can perform "on boarding" of UE for a particular localised service. + +It also provides ideas for Key Issue#3, focusing on what kind of information needs to be exchanged between Localized service provider and the Hosting network. + +The solution proposes to provision the credential to the UE via a restricted PDU Session. User may choose a particular Localized service based on information displayed on its mobile phone, and based on the chosen service and local configurations, AMF and SMF may create a session for the UE via which UE can connect to a captive portal pay for the services and then be provisioned the required credentials for accessing the Hosting network. + +During the service agreement between Localised service provider and the Hosting network, details of captive portal may be provided by the Localised service provider to the Hosting network. + +If the Hosting network is able to authenticate UE using its Home Network credentials, even then UE may require new credentials for accessing localised services (because UE's current subscription does not include Localised services usage). + +If the Hosting network is not able to authenticate the UE using its Home network credentials, then provisioning can be RLOS based. + +### 6.4.1.2 Functional Description + +Localized service provider may provide captive portal information, whether to create a restricted PDU Sessions for provisioning for the UE and/or DNAI, S-NSSAI information for the restricted PDU Session etc. during service agreement phase. + +As per the agreement between Localised service provider PCF may configure captive portal information/redirection information to SMF (SMF may provide it to UPF in form of FAR rules). + +User may manually select a particular Hosting Network. + +The User may then choose a particular Localised service based on the list of available Localized service provided by the Hosting network. This information may be available to the UE by some other solution (e.g. Sol#26 or Sol#34). A NAS request will be sent to UE requesting for further information regarding provisioning of Credentials for the particular Localized service. + +The AMF then decides to generate a PDU session which may be restricted in terms of time and the destination traffic, for the UE based on the chosen localised service. If the UE did not choose any service, based on local configuration UE's session may be established to a particular portal (e.g. a default Localized service configured locally). + +NOTE: It may be possible that the UE cannot be primarily authenticated. Then decision to generate the PDU Session is based on local policies. SA3 collaboration might be needed. + +Once the AMF finds (based on local policies) that Restricted PDU Session can be created for the UE's requested Localized Service, it may provide UE with the PVS address related to the particular Localized service and an indication that the UE can use this Hosting Network for Provisioning of Credentials for the particular Localized service. + +UE then proceeds to Request PDU Session establishment procedure with providing additionally the name of the requested Localized service so that the SMF may request the corresponding policy from PCF or use the local configuration based on the Localized Service name. + +The information related to Restricted PDU session may include the following: + +- Localized service name +- Max duration of PDU Session (time bound) +- Redirection information +- Max data through this PDU Session etc. + +### 6.41.3 Procedures + +![Sequence diagram illustrating the provisioning of localised service credentials via the Hosting network. The diagram shows interactions between UE, AMF, SMF, UPF, PCF, and LSP Server. The process starts with a service agreement between the LSP and the Hosting network. The UE sends a NAS Request for a selected Localized service to the AMF. The AMF decides to create a PDU Session for provisioning. The AMF sends a NAS Downlink to the UE. The UE sends a PDU Session establishment request to the AMF. The AMF sends an Nsmf_PDUSession_CreateSMContext request to the SMF. The SMF sends an SM policy request (Localized service name) to the PCF. The UE is redirected to the captive portal/LSP server. The LSP server provides the UE with new credentials for the Hosting network. Finally, the UE registers again with the new credentials.](61c77cded492bbcd03eff79c850d92c2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UPF + participant PCF + participant LSP Server + + Note over LSP Server, Hosting Network: 0. Service agreement between LSP and Hosting network + UE->>AMF: 1. NAS Request (selected Localized service) + Note right of AMF: 2. AMF decides to create a PDU Session for provisioning + AMF->>UE: 3. NAS Downlink + UE->>AMF: 4. PDU Session establishment request + AMF->>SMF: 5. Nsmf_PDUSession_CreateSMContext + SMF->>PCF: 6. SM policy request (Localized service name) + Note over UE, LSP Server: 7a. UE is redirected to the captive portal/LSP server + Note over UE, LSP Server: 7b. LSP server provides UE with new credential for the Hosting network + UE->>AMF: 8. UE registers again with the new credentials + +``` + +Sequence diagram illustrating the provisioning of localised service credentials via the Hosting network. The diagram shows interactions between UE, AMF, SMF, UPF, PCF, and LSP Server. The process starts with a service agreement between the LSP and the Hosting network. The UE sends a NAS Request for a selected Localized service to the AMF. The AMF decides to create a PDU Session for provisioning. The AMF sends a NAS Downlink to the UE. The UE sends a PDU Session establishment request to the AMF. The AMF sends an Nsmf\_PDUSession\_CreateSMContext request to the SMF. The SMF sends an SM policy request (Localized service name) to the PCF. The UE is redirected to the captive portal/LSP server. The LSP server provides the UE with new credentials for the Hosting network. Finally, the UE registers again with the new credentials. + +**Figure 6.41.3-1: Provisioning Localised service credentials via the Hosting network** + +High level details of the Procedure is described as follows: + +0. User may manually choose a particular Hosting network which provides a localized service. + +**Editor's note:** It is FFS how UE will register if it cannot be authenticated with the Home Network credentials. To decide whether RLOS-based provisioning of credentials can be used. + +1. NAS request: UE may include the selected localised service in the request. The details of how this information is available to UEs is assumed to be provided by other solutions. +2. AMF decides to create a PDU Session for provisioning purposes. + +AMF can be configured with the information, on a per Localized service, which may include LSP provisioning server address, whether Restricted PDU Session can be created or not etc. + +3. NAS Downlink Message (AMF to UE) which may include DNN, S-NSSAI, an indication to trigger PDU Session creation. + +AMF can send UE an indication related to "Provisioning for localised service"; which, based on UE implementation, may launch a particular application (e.g. web browser) that will initiate the PDU Session establishment. + +For example based on the indication sent by the AMF, UE may display a notification to the User informing about provisioning of credentials. User may click the notification and a particular application (UE implementation specific) may launch, thus starting the PDU Session establishment. + +**Editor's note:** Security implications of the AMF triggering the UE to a PDU session establishment need to be assessed by SA3. Potentially, any serving network may trigger the UE to establish a PDU session to any target DNN/S-NSSAI. + +4. PDU Session Establishment Request (UE to AMF): In addition UE includes the name of Localized Service in the request. + 5. AMF sends Nsmf\_PDUSession\_create to the SMF + 6. SMF creates a PDU session by providing appropriate information to UE and UPF. The session may be time bounded, and filtered for Destination addresses etc. +- 7a-7b. UE connects to the external portal and gets the credentials. Details of this step are out of 3GPP scope. +- NOTE:** UE's PDU Session may be redirected to the captive portal by using PDR/FAR rules installed by SMF based on PCF policies. +8. UE performs authentication/authorization with the new credentials. This may also involve sending UE a new Initial Registration to the Hosting network. + +#### 6.41.4 Impacts on services, entities and interfaces + +AMF/SMF capability to create a restricted PDU Session. Support for RLOS + +PCF capability update SMF/AMF regarding information of restricted portal, captive portal information etc. + +PCF capability to store and provide SMF policies for restricted PDU Session based on UE capability to initiate PDU Session based on AMF trigger/indication. + +**Editor's note:** The security impacts shall be evaluated by SA WG3. + +### 6.42 Solution #42: Solution of UE requesting for hosting network selection and access information via visiting network + +#### 6.42.1 Introduction + +This solution mainly addresses Key Issue #4 and focuses on this scenario: the UE's home network is not aware of the existence of hosting network or localised service. This scenario may exist when the UE's home network is in one country while the hosting network is in another country. It is not realistic for the hosting network to establish business relationship with all the UE's home networks all over the world. However, the hosting network can establish business relationship with the networks within the same country. + +#### 6.42.2 Functional Description + +In this solution, it is proposed that when the UE is roaming in a visiting network, the UE requests for hosting network selection and access information via the visiting network. The serving network sends the hosting network selection and access information to the UE's home network after obtaining it. The UE's home network then sends the hosting network + +selection and access information to the UE. A visiting network is a network which has roaming agreement with UE's home network. + +This solution is applicable to the scenario where the hosting network is an SNPN. + +The Hosting Network Selection and Access Information consists the following information: + +- Hosting Network Identifier, e.g. SNPN ID in the case of the hosting network is an SNPN. +- The time condition information when the hosting network provides access service. +- The location condition information where the hosting network provides access service. +- Optionally, credential used for the UE to access the hosting network. + +The UE receives the Hosting Network Selection and Access Information from the localized service provider. The UE selects a hosting network when the time and location condition information is satisfied. + +### 6.42.3 Procedures + +![Sequence diagram illustrating the procedure for UE requests for hosting network selection and access information via visiting network. The diagram shows interactions between UE, RAN, AMF, NEF, UDM, SoR-AF, and AF across Serving Network, Home Network, and LSP domains.](e1136c8a41c5a8081a8a554e513cd86e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant NEF + participant UDM + participant SoR-AF + participant AF + + Note left of RAN: Serving Network + Note right of SoR-AF: Home Network + Note right of AF: LSP + + UE->>AMF: 1. Registration Request + Note over RAN, AMF: 2. Steps 6-14 as per clause 4.2.2.2.2 + AMF->>NEF: 3a. Service Authorization Request + NEF->>AF: + AF-->>NEF: 3b. Service Authorization Response (hosting network selection and access information) + NEF-->>AMF: + AMF->>UDM: 4. hosting network selection and access information + AMF-->>UE: 5. Hosting network selection and access information + +``` + +Sequence diagram illustrating the procedure for UE requests for hosting network selection and access information via visiting network. The diagram shows interactions between UE, RAN, AMF, NEF, UDM, SoR-AF, and AF across Serving Network, Home Network, and LSP domains. + +**Figure 6.42.3-1: UE requests for hosting network selection and access information via visiting network** + +1. The UE sends Registration Request message to the AMF of the visiting network, including request of obtaining hosting network selection and access information. Localized service ID is included in Registration Request, indicating the localized service which the UE wants to access. How the UE knows about the Localized service ID may be out of 3GPP scope or addressed by other solutions. + +NOTE 1: The UE can perform the request of obtaining hosting network selection and access information during initial registration request or mobility registration request. + +2. Steps 6-14 in clause 4.2.2.2.2 of TS 23.502 [4] are performed. The AMF of the visiting network obtains UE ID (e.g. GPSI) from the UDM. + +- 3a. The AMF of the visiting network sends Service Authorization Request (UE ID) to the AF of the corresponding localized service provider via NEF. The Service Authorization Request is used to request the localized service provider to authorize the UE to use the localized service. 3b. The AF of the localized service provider authorizes the UE to use localized service and then sends Service Authorization Response to the AMF of the visiting network, including hosting network selection and access information. + +NOTE 2: How the AF of the localized service provider authorizes the UE to use localized service may be out of 3GPP scope, e.g. the user of the UE paid for the localized service offline. + +4. The AMF of the visiting network sends the hosting network selection and access information to the UDM of the UE's home network. +5. The UDM of the UE's home network sends the hosting network selection and access information to the UE using SoR or UPU procedure. + +## 6.42.4 Impacts on services, entities, and interfaces + +UE impact: + +- Ability to requests for Hosting Network Selection and Access Information from AMF of a visiting network. +- Ability to receive Hosting Network Selection and Access Information via SoR or user parameter update procedure. + +Visiting Network impact: + +- AMF: Ability to receive request for Hosting Network Selection and Access Information from the UE. Ability to send Service Authorization Request to the AF of the localized service provider via NEF and receive Hosting Network Selection and Access Information. Ability to send Hosting Network Selection and Access Information to the UDM of the home network. +- NEF: Ability to transfer Service Authorization and Hosting Network Selection and Access Information between the AMF and the AF of the local service provider. + +Home Network impact: + +- UDM: Ability to receive Hosting Network Selection and Access Information from the AMF of the visiting network and sends Hosting Network Selection and Access Information to the UE using SoR procedure or user parameter update procedure. + +## 6.43 Solution #43: Solution for Transferring hosting network selection information from hosting network to UE's home network + +### 6.43.1 Introduction + +This solution mainly addresses Key Issue #4 and focuses on this scenario: the UE's home network has business relationship with hosting network, but not with the Localized service provider. + +This solution is applicable to the scenario where the hosting network is an SNPN or a PNI-NPN. + +### 6.43.2 Functional Description + +In this solution, it is proposed that when the UE establishes business relationship with the Localized service provider, e.g. buying tickets, then the Localized service provider could notify the Hosting network and then trigger the Hosting network to send hosting network selection and access information to the UE via the UE's home network. + +The Hosting Network Selection and Access Information consists the following information: + +- Hosting Network Identifier, e.g. SNPN ID in the case of the hosting network is an SNPN, CAG ID in the case of the hosting network is a PNI-NPN. +- The time condition information when the hosting network provides access service. +- The location condition information where the hosting network provides access service. + +The UE receives the Hosting Network Selection and Access Information from the localized service provider. The UE selects a hosting network when the time and location condition information is satisfied. + +### 6.43.3 Procedures + +![Sequence diagram illustrating the procedure for hosting network selection and access information transfer. The diagram shows interactions between a UE, Home Network (UDM, NEF), Hosting Network (UDR, AF, NEF), and Localized service provider (AF).](8a9a4dc9f8f886d283f9a75e5b2287f4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Home Network + subgraph Home Network + UDM + NEF + end + subgraph Hosting Network + UDR + AF + NEF + end + participant LSP as Localized service provider + subgraph LSP + AF + end + + Note right of UE: 0. UE establishes business relationship with LSP + Note right of AF: 1. subscription of Localized service registration + Note right of AF: 2. Notification of Localized service registration (UE ID) + Note right of UDR: 3. Report of Localized service registration (UE ID) + Note right of AF: 4. Hosting network selection and access information (UE ID) + Note right of UDM: 5. Hosting network selection and access information + +``` + +Sequence diagram illustrating the procedure for hosting network selection and access information transfer. The diagram shows interactions between a UE, Home Network (UDM, NEF), Hosting Network (UDR, AF, NEF), and Localized service provider (AF). + +**Figure 6.43.3-1: Hosting network selection and access information transfer from hosting network to UE's home network** + +0. The UE establishes business relationship with the Localized service provider. + +NOTE 1: This step may be out of 3GPP scope, e.g. the user buys a ticket for a football match. + +1. The Hosting network AF may subscribe Localized service registration notification towards the UDR in the Hosting network. + +NOTE 2: This step is optionally performed. Otherwise, the UDR can be configured to report of localized service registration to the AF. + +2. The AF of Localized service provider sends Notification of Localized service registration to the UDR of Hosting network via NEF of Hosting network. Notification of Localized service registration describes the UE is successfully perform registration to the Localized service. Localized service ID and UE ID (e.g. UE's phone number) are included in this notification message. + +3. The UDR in the Hosting network sends Report of Localized service registration to the AF of the Hosting network. + +The UDR may also include DNN and S-NSSAI in Hosting network corresponding to the Localized service. + +4. The AF of the Hosting network sends Hosting network selection and access information to the UDM of the UE's home network via NEF of the home network. UE ID is also included in the message. + +DNN and S-NSSAI in Hosting network corresponding to the Localized service is also included in the message if received in step3. + +NOTE 3: The AF of the Hosting network can use the UE's phone number to determine UE's home network. + +**Editor's note:** whether message 4 is a message via NEF or BSS communication is FFS as intention is to make an update of the subscription. + +5. The UDM of the UE's home network sends the hosting network selection and access information to the UE using SoR or UPU procedure. + +The UDM may update the UE's subscription to allow the UE to use DNN and S-NSSAI in Hosting network when the UE wants to use the Localized service. + +### 6.43.4 Impacts on services, entities, and interfaces + +UE impact: + +- Ability to receive Hosting Network Selection and Access Information via SoR or user parameter update procedure. + +Home Network impact: + +- UDM: Ability to receive Hosting Network Selection and Access Information from the AF of the Hosting network and sends Hosting Network Selection and Access Information to the UE using SoR procedure or user parameter update procedure. +- NEF: Ability to transfer Hosting Network Selection and Access Information from the AF in the Hosting network to the UDM. + +Hosting Network impact: + +- AF: Ability to receive Hosting Network Selection and Access Information from the UDM of the hosting network and send the information to the UDM in Home network. Optionally, ability to subscribe report of Localized service registration for UEs. Hosting Network Selection and Access Information. +- UDR: Ability to send report of Localized service registration to AF of Hosting network and send Hosting Network Selection and Access Information to the AF of the Hosting network. + +Localized service provider Network impact: + +- AF: Ability to send notification of localized service registration to Hosting Network. + +## 6.44 Solution #44: Solution on top of Solution #10 for Serving Network to assist in discovery of hosting networks + +### 6.44.1 Introduction + +The solution addresses Key Issue #4 (Enabling UE to discover, select and access NPN as hosting network and receive localized services) and builds on top of Solution #10. + +### 6.44.2 Functional Description + +#### 6.44.2.1 General + +This solution is based on Solution #10, and builds on top assistance from the serving network for discovery of hosting networks. + +It assumes that: + +- The UE is configured for automatic selection of hosting networks for localized services as per Solution #10. +- The hosting network and serving network have a service level agreement, part of which is serving network assisting in search for hosting network. + - In such agreement, the serving network knows the frequency bands at which the hosting network operates, although it does not need to know any other information regarding localized services or any other information. + +In this solution, two options for Serving Network assistance in discovery of hosting networks are proposed. + +#### 6.44.2.2 Serving network assistance information in SIB + +In this option, the NG-RAN is configured, in the area where the agreement has been made, to broadcast in SIB the frequency bands where hosting networks are available. This option assumes that the serving network and hosting network(s) are willing to make the information available to any UE that is interested in this information. + +If a UE is configured with automatic selection of hosting networks for localized services as per Solution #10, the UE may use the information in SIB to narrow down the search of hosting networks to the broadcasted frequencies. All other + +triggers and conditions as described in Solution #10 are not altered by this frequency band assistance information received in SIB. + +NOTE: The frequency bands for hosting network information provided in SIB do not guarantee the actual presence of a specific hosting network in any of those bands at a specific time. This avoids the need for networks that are dynamically enabled and disabled for hosting network operation to update the serving network each time the hosting network is enabled/disabled. + +#### 6.44.2.2 Serving network assistance via dedicated signalling + +This option assumes that the serving network and hosting network agree that only authorized UEs are subject to receive hosting network search assistance information. + +In this option, the NG-RAN is configured with information on frequency bands where hosting network(s) may potentially be present. + +This information is provided by NG-RAN to authorized UEs in RRC signalling as follows: + +- The UDM contains as part of UE subscription information one bit indicating that the UE is enabled to receive assistance for hosting network discovery. +- During registration procedure, the UDM provides to the AMF in subscription information that the UE is enabled to receive assistance for hosting network discovery. +- The AMF provides to NG-RAN, in every N2 initial UE context establishment, an indication that UE is enabled to receive assistance for hosting network discovery. +- During RRC connection establishment, a UE that is interested in discovering hosting network(s) for localized services requests in RRC to receive assistance information. +- The NG-RAN, based on this indication from AMF, provides the UE with hosting network search assistance information, containing frequency band(s) with potential hosting network availability. + +### 6.44.3 Procedures + +#### 6.44.3.1 Procedure for Hosting network search assistance information in SIB + +Figure 6.44.3.1-1 shows the procedure for a serving network to assist the UE in searching for hosting networks in SIB. + +![Sequence diagram showing the procedure for hosting network search assistance information in SIB. The diagram involves two main entities: UE and Serving NW NG-RAN. The process starts with the UE being configured for automatic selection of hosting networks. The Serving NW NG-RAN then sends new SIB information containing frequency bands for hosting networks. Finally, the UE narrows or prioritizes its search based on this information.](36211a63b8012f6e261c769fd6bee979_img.jpg) + +``` +sequenceDiagram + participant UE + participant Serving NW NG-RAN + Note left of UE: 0. UE configured for Automatic selection of Hosting Network for localized services (Solution #10) + Note right of Serving NW NG-RAN: 1. New SIB information: Frequency bands for hosting networks + Note left of UE: 2. UE may narrow or prioritize search (as per Solution #10) to frequency bands in SIB +``` + +Sequence diagram showing the procedure for hosting network search assistance information in SIB. The diagram involves two main entities: UE and Serving NW NG-RAN. The process starts with the UE being configured for automatic selection of hosting networks. The Serving NW NG-RAN then sends new SIB information containing frequency bands for hosting networks. Finally, the UE narrows or prioritizes its search based on this information. + +Figure 6.44.3.1-1: Hosting network search assistance information in SIB + +0. The UE is assumed to have been configured for automatic selection of hosting networks for localized services as per Solution #10. +1. The NG-RAN in the serving network is configured (based on SLA with hosting network(s)) to broadcast in SIB hosting network search assistance information, containing frequency band(s) with potential hosting network availability. +2. If the hosting network search assistance information is present in SIB, the UE proceeds as per Solution #10, with the additional behaviour that the UE may narrow down or prioritize the frequency bands present in the hosting network search assistance information when searching for hosting networks. + +### 6.44.3.2 Procedure for Hosting network search assistance information in SIB + +Figure 6.44.3.2-1 shows the procedure for a serving network to assist the UE in searching for hosting networks via RRC signalling. + +![Sequence diagram showing the procedure for Hosting network search assistance information in RRC. The diagram involves five entities: UE, NG-RAN, AMF, Other NFs, and UDM. The sequence of messages is: 1. RRC connection establishment from UE to NG-RAN; 2. Registration Procedure TS 23.502 clause 4.2.2.2.2 from NG-RAN to AMF; 2.1. Step 14 TS 23.502 clause 4.2.2.2.2 with UDM including UE enabled for Hosting Network search assistance from AMF to UDM; 4. Any procedure requiring N2 Initial UE context / Path Switch from AMF to NG-RAN; 4.1. N2 Message: UE enabled for Hosting Network search assistance from AMF to NG-RAN; 4.2. RRC: Hosting Network search assistance information from NG-RAN to UE.](7fb56e3e9f8a134112eee90463cc9962_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant Other NFs + participant UDM + + Note left of UE: 1. RRC connection establishment + UE->>NG-RAN: + Note right of NG-RAN: 2. Registration Procedure TS 23.502 clause 4.2.2.2.2 + NG-RAN->>AMF: + Note right of AMF: Step 14 TS 23.502 clause 4.2.2.2.2 with UDM including UE enabled for Hosting Network search assistance + AMF->>UDM: + Note right of AMF: 4. Any procedure requiring N2 Initial UE context / Path Switch + AMF->>NG-RAN: + Note right of NG-RAN: N2 Message: UE enabled for Hosting Network search assistance + NG-RAN->>AMF: + Note left of UE: RRC: Hosting Network search assistance information + NG-RAN->>UE: + +``` + +Sequence diagram showing the procedure for Hosting network search assistance information in RRC. The diagram involves five entities: UE, NG-RAN, AMF, Other NFs, and UDM. The sequence of messages is: 1. RRC connection establishment from UE to NG-RAN; 2. Registration Procedure TS 23.502 clause 4.2.2.2.2 from NG-RAN to AMF; 2.1. Step 14 TS 23.502 clause 4.2.2.2.2 with UDM including UE enabled for Hosting Network search assistance from AMF to UDM; 4. Any procedure requiring N2 Initial UE context / Path Switch from AMF to NG-RAN; 4.1. N2 Message: UE enabled for Hosting Network search assistance from AMF to NG-RAN; 4.2. RRC: Hosting Network search assistance information from NG-RAN to UE. + +**Figure 6.44.3.2-1: Hosting network search assistance information in RRC** + +1. A UE that is interested in discovering hosting network(s) for localized services indicates this in RRC connection establishment. +2. During registration procedure, regular steps as defined in TS 23.502 [4] are executed with the following differences: + - In step 14, the UDM provides the AMF with an indication that the UE is enabled for Hosting Network search assistance. The AMF stores this indication in UE context. + - In step 21, the AMF provides the NG-RAN with an indication that the UE is enabled for Hosting Network search assistance. +3. If the UE indicated it is interested in discovering hosting networks, the NG-RAN received an indication from AMF that UE is enabled for Hosting Network search assistance, the NG-RAN based on configuration provides the UE with Hosting network search assistance information containing frequency band(s) with potential hosting network availability. The UE proceeds as per Solution #10, with the additional behaviour that the UE may narrow down or prioritize the frequency bands present in the hosting network search assistance information when searching for hosting networks. + +4. In any subsequent procedure where an N2 Initial UE context is established (e.g. subsequent registration procedure, service request procedure, etc), the procedure is unchanged except for the following additional flow of information: + - The AMF provides the NG-RAN with an indication that the UE is enabled for Hosting Network search assistance. + - If the UE indicated it is interested in discovering hosting networks, the NG-RAN received an indication from AMF that UE is enabled for Hosting Network search assistance, the NG-RAN based on configuration provides the UE with Hosting network search assistance information containing frequency band(s) with potential hosting network availability. The UE proceeds as per Solution #10, with the additional behaviour that the UE may narrow down or prioritize the frequency bands present in the hosting network search assistance information when searching for hosting networks. + +#### 6.44.4 Impacts on services, entities and interfaces + +The solution has the following impacts in addition to the impacts mentioned in Solution #10: + +UE: + +- For SIB option: Receive new Hosting Network search assistance information in SIB. +- For RRC option: Receive new Hosting Network search assistance information in RRC. +- Use that information to narrow down or prioritize search for hosting networks in the received frequency bands. + +NG-RAN: + +- For SIB option: Broadcasting in SIB the Hosting Network search assistance information. +- For RRC option: receive from AMF indication that UE is enabled for Hosting Network search assistance, and provide Hosting Network search assistance information for such UE via RRC signalling. + +AMF (for RRC option only): + +- Receive in subscription information an indication that UE is enabled for Hosting Network search assistance, and provide this indication NG-RAN over N2 signalling. + +UDM (for RRC option only): + +- Include in subscription information to be provided to UE that UE is enabled for Hosting Network search assistance. + +### 6.45 Solution #45: Ensuring UE access localized service in the service area/time + +#### 6.45.1 Introduction + +This solution is aimed at KI#4 and KI#5. In order to ensure that UE accesses the localized services within the location and/or time restriction based on the specific localized service conditions, AMF and SMF need to determine whether the UE meets the conditions that allows UE to obtain the localized services. If UE does not meet the conditions, UE should stop obtaining the localized services. + +#### 6.45.2 Functional Description + +The solution is similar to the LADN mechanism that the AMF will determine whether the UE meets the location condition of the localized service. In addition, considering the time condition of the localized service, SMF shall determine whether UE is allowed to obtain the localized service based on the time restriction. Therefore, the differences between this solution and the existing LADN mechanism are summarized as below: + +- If common DNN and/or S-NSSAI are used for localized services, a service identifier shall be provided by the UE to the AMF and SMF in order to determine the corresponding restriction. +- When there are location conditions, AMF may perform different procedures to determine the location of UE if different granularities of location conditions are applied. For example, if TAI list is used for location restriction, the existing mechanism defined in LADN can be reused. If cell Id list is used for location restriction, AMF shall perform location report control with RAN to obtain the cell Id where the UE is accessing to. +- When there are time conditions, SMF may need to monitor the service time after the UE starts obtaining the localized service. +- When the UE does not meet the service condition (e.g. when UE is out of the service area or when the service time is timeout), the SMF shall instruct the UPF to stop transmitting the localized services to the UE or deactivate the user plane if the PDU session is only used for the localized service. + +### 6.45.3 Procedures + +![Sequence diagram for PDU Session Establishment for Localized Service. The diagram shows interactions between UE, NG-RAN, AMF, SMF, and UPF within a Hosting Network. The process starts with UE and AMF obtaining localized service information. The UE sends a PDU Session Establishment Request to the AMF. The AMF performs SMF selection and sends a Nsmf_PDUSession_CreateSMContext Request to the SMF. A reference is made to steps 4 to 17 in Figure 4.3.2.2.1-1 of TS 23.502. The SMF triggers the procedure of determining whether the UE meets the localized service conditions. The AMF sends a Nsmf_EventExposure_Subscribe to the SMF. The SMF performs mobility management. The SMF sends a Nsmf_EventExposure_Notify to the AMF if the UE is out of the service area. Finally, the SMF instructs the UPF to stop forwarding the traffic flow of the service.](4c4d1f9c0946faff8f5432a60c4c3f94_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UPF + + Note left of UE: 0. UE obtain localized service information + Note right of AMF: 0. obtain localized service information + + UE->>AMF: 1. PDU Session Establishment Request (DNN, S-NSSAI) + AMF->>SMF: 2. SMF selection + AMF->>SMF: 3. Nsmf_PDUSession_CreateSMContext Request (service condition) + Note over AMF, SMF: 4. Step 4 to step 17 in Figure 4.3.2.2.1-1 of TS 23.502 + Note left of AMF: Trigger the procedure of determining whether UE meets the localized service conditions + SMF->>AMF: 5. Nsmf_EventExposure_Subscribe + Note over AMF, SMF: 6. mobility management + SMF->>AMF: 7. Nsmf_EventExposure_Notify (UE out of service area) + SMF->>UPF: 8. Instruct UPF to stop forwarding the traffic flow of the service + +``` + +Sequence diagram for PDU Session Establishment for Localized Service. The diagram shows interactions between UE, NG-RAN, AMF, SMF, and UPF within a Hosting Network. The process starts with UE and AMF obtaining localized service information. The UE sends a PDU Session Establishment Request to the AMF. The AMF performs SMF selection and sends a Nsmf\_PDUSession\_CreateSMContext Request to the SMF. A reference is made to steps 4 to 17 in Figure 4.3.2.2.1-1 of TS 23.502. The SMF triggers the procedure of determining whether the UE meets the localized service conditions. The AMF sends a Nsmf\_EventExposure\_Subscribe to the SMF. The SMF performs mobility management. The SMF sends a Nsmf\_EventExposure\_Notify to the AMF if the UE is out of the service area. Finally, the SMF instructs the UPF to stop forwarding the traffic flow of the service. + +**Figure 6.45.3-1: PDU Session Establishment for Localized Service** + +0. UE and AMF can obtain or be configured with localized service information. + +NOTE: The conclusion on how UE and AMF obtain or be configured with localized service information will be applied to this solution. + +1. UE sends the PDU Session Establishment Request to the AMF. The message includes DNN, S-NSSAI and optionally service ID(s). If common DNN and S-NSSAI are used for different localized services with different service conditions, the service ID(s) should be included in the request message in order to determine the corresponding service condition. +2. AMF determines the service conditions based on the DNN and/or S-NSSAI (or service ID). AMF performs SMF selection. +3. AMF sends Nsmf\_PDUSession\_CreateSMContext Request to the SMF including the DNN, S-NSSAI and optionally service ID(s). In addition, AMF sends the service condition to the SMF (e.g. service time). + +4. The PDU Session can be established as step 4 to step 17 in Figure 4.3.2.2.1-1 of TS 23.502 [4]. +5. When the PDU Session is established, the SMF should trigger the procedure to determine whether the UE meets the service condition(s). If the localized service has service area condition, the SMF should subscribe UE mobility event notification to AMF, triggering the AMF to determine the UE location. If the localized service has service time condition (e.g. the service duration time is 2 hours), the SMF shall monitor the duration time that the UE has obtained the localized service. +6. AMF determines the service conditions based on the DNN and/or S-NSSAI (or service ID). If the service conditions include service area and the service area is TAI list, the existing mechanism in LADN can be applied. If the service area is cell Id list, the AMF shall perform location report control with RAN to obtain the cell Id where the UE is accessing to. +7. If UE does not meet the service area conditions, the AMF should send a notification to the SMF. +8. When the SMF receives the notification from the AMF or when the SMF determines that UE does not meet the service time condition, the SMF instructs the UPF to stop forwarding the traffic flow of the service. + +#### 6.45.4 Impacts on services, entities, and interfaces + +UE impact: + +- Ability to include localized service identifier in PDU Session Establishment Request. + +AMF impact: + +- Ability to determine the localized service conditions based on service ID. +- Ability to determine whether UE is in the service area based on different granularity of service area. + +SMF impact: + +- Ability to perform session management based on service time conditions. + +### 6.46 Solution #46: Accesses Localized Services via URSP rules + +#### 6.46.1 Introduction + +In this solution, it addresses (KI#5) how the UE access the Localized Services in the registered Hosting Network. To support the UE accesses the Localized Services using URSP, the following preconditions should be fulfilled: + +- the Route Selection Validation Criteria (i.e. Time Window and Location Criteria) of the matched URSP rules should be fulfilled. + +To use the PDU Session for access the Localized Services in the Hosting Network, the UE should evaluate the URSP rules. When the UE finds the Traffic Descriptor (TD) of a URSP rule is matched, the UE starts to evaluate the Route Selection Descriptor (RSD). Only when the field(s) of the Route Selection Validation Criteria in the RSD is satisfied, the UE can access the Localized Services via: + +- using the existing PDU Session; or +- establishing the PDU Session based on the matched RSD. + +#### 6.46.2 Functional Description + +After the UE successfully registers to the selected Hosting Network, the UE may start to access the Localized Services. Before the UE initiates the PDU Session Establishment procedure, the UE should evaluate the URSP rules. + +The URSP rules could be: + +- provisioned (signalled) or pre-configured by the Home Network; or +- provisioned (signalled) by the Hosting Network. + +Furthermore, if the URSP rules are updated by Home Network or the Hosting Network at the time when the UE is registered to the Hosting Network, the UE can re-evaluate the URSP rules for the proper handlings for the corresponding PDU Session for the Localized Services as specified in TS 23.503 [5]. + +NOTE 1: If Home Network is PLMN and Hosting Network is a PNI-NPN, and the UE is accessing the Hosting Network using Home Network credentials, the URSP rules can be only provisioned by UE's Home Network as specified in clause 6.6.2.2.1 of TS 23.503 [5]. General principle is used as specified in the clause 6.6.2.2.1 of TS 23.503 [5]: + +- Only the URSP rules provisioned (signalled) by the PCF are used by the UE, if both URSP rules provisioned (signalled) by the PCF and pre-configured URSP rules are present. + +Furthermore, the following principles are applied in the UE when the UE evaluates the URSP rules for the Localized Services: + +- If the Home Network is PLMN and the Hosting Network is also PLMN, the UE can only use the URSP rules provisioned (signalled) by the HPLMN of the UE. +- If the Home Network is PLMN or SNPN and the Hosting Network is SNPN, the UE uses the URSP rules as specified in clause 6.6.2.2.2 of TS 23.503 [5] if the UE access the Hosting Network using the credentials from the Home Network as a Credentials Holder (CH). + +To Support the Localized Services, the Time Window and the Location Criteria should be configured according to the Validity Information of the Localized Services: + +- The Location Criteria can contain one or more types of location area as specified in Table 5.2.2 of TS 24.526 [19]. For the Localized Services, the Location Criteria could be TAI list which consists of the Hosting Network information. Furthermore, a new Partial tracking area list can be used to include NID information +- The Time Window can contain "Start Time" and "Stop Time" for the Localized Services as specified in Table 5.2.1 of TS 24.526 [19]. + +Only when the Route Selection Validation Criteria of the matched URSP rule are satisfied, the UE can establish the new PDU Session or re-use the existing PDU Session for the Localized Services. + +### 6.46.3 Procedures + +The solution reuses existing procedures. + +### 6.46.4 Impacts on services, entities, and interfaces + +UE: + +- To support new Partial tracking area list that includes NID. + +H-PCF/V-PCF: + +- Support to update the URSP rules in roaming scenario as proposed in TR 23.700-85 [16]. + +## 6.47 Solution #47: Solution for mitigating overload at home network + +### 6.47.1 Introduction + +The solution addresses the Key Issue #6: Support for returning to home network. Overload may happen when a high number of UEs attempt to re-register to their home network simultaneously after accessing a localized service from a temporary hosting network. This solution solves the problem of overloading at home network by deregistering UEs from the hosting network in an adaptive manner based on the input from the home network. + +## 6.47.2 Functional Description + +This solution makes the following assumptions: + +- There is a service level agreement between the hosting network and the home network. The hosting networks identities, locations, and the available localized services information are shared with the home network. +- Hosting network subscribes to the home network AMF to get notification of the allowed maximum number of returning UEs from the hosting network to the home network AMF per unit time. +- Based on the subscription, the home network AMF determines the hosting network and the localized service specific the allowed maximum number of returning UEs to the home network per unit time and notifies to the hosting network AMF. For example, if there are 2000 UEs registered to the hosting network for accessing the localized service, the home network notifies to the hosting network that maximum 500 UEs can return to the home network per unit time for 4 time units. +- UDM coordinates with AMFs for selection of the allowed maximum number of returning UEs in hosting network based on the notification from the home network AMF. After the localized service is over, the hosting network selects the allowed maximum number of returning UEs and deregisters them simultaneously. For example, the hosting network selects 500 UEs from the total 2000 UEs at first unit time and deregisters the selected 500 UEs simultaneously (which 500 UEs selected for deregistration is implementation specific). +- If there is a change in the allowed maximum number of returning UEs to the home network AMF per unit time from the hosting network due to less or high number of attempts from the home network and other hosting networks UEs, then the home network AMF notifies the new value (i.e. the new allowed maximum number of returning UEs per unit time) to the hosting network in a new notification. For example, the home network notifies to the hosting network in a new notification that 1000 UEs can return to the home network AMF at third unit time due to change in network condition. +- The deregistered UEs select their home network or another hosting network and initiate the registration procedure. + +## 6.47.3 Procedures + +### 6.47.3.1 Adaptive deregistration procedure + +![Sequence diagram of the Adaptive deregistration procedure. The diagram shows interactions between Home Network AMF, UE, and Hosting Network AMF/UDM. The steps are: 1. Pre-configuration (Home AMF to Hosting AMF/UDM); 2a. Registration Request (UE to Hosting AMF/UDM); 2b. Registration Accept (Hosting AMF/UDM to UE); 3a. Subscribe Configuration Service (Hosting AMF/UDM to Home AMF); 3b. AMF determines the hosting network and the localized service specific Max. No. of Returning UEs (Home AMF internal); 3c. Notify (Home AMF to Hosting AMF/UDM); 4. Localized service termination (Hosting AMF/UDM internal); 5a. Max. No. of Returning UEs are selected for deregistration (Hosting AMF/UDM internal); 5b. Deregistration Request for Max. No. of Returning UEs (Hosting AMF/UDM to UE); 5c. Deregistration Accept (UE to Hosting AMF/UDM); 6. Re-Register Max. No. of Returning UEs (UE internal); 7. Unsubscribe Configuration Service (UE to Home AMF).](16e2337d7302fa71012e69303a459c35_img.jpg) + +``` + +sequenceDiagram + participant Home Network AMF + participant UE + participant Hosting Network AMF/UDM + + Note over Home Network AMF, Hosting Network AMF/UDM: 1. Pre-configuration + UE->>Hosting Network AMF/UDM: 2a. Registration Request + Hosting Network AMF/UDM-->>UE: 2b. Registration Accept + Hosting Network AMF/UDM->>Home Network AMF: 3a. Subscribe Configuration Service (Hosting NW ID, No. of UEs, Localized Service Info) + Note left of Home Network AMF: 3b. AMF determines the hosting network and the localized service specific Max. No. of Returning UEs + Home Network AMF->>Hosting Network AMF/UDM: 3c. Notify (Home NW ID, Max. No. of Returning UEs, Valid Time, Localized Service Info) + Note right of Hosting Network AMF/UDM: 4. Localized service termination + Note right of Hosting Network AMF/UDM: 5a. Max. No. of Returning UEs are selected for deregistration + Hosting Network AMF/UDM->>UE: 5b. Deregistration Request for Max. No. of Returning UEs + UE-->>Hosting Network AMF/UDM: 5c. Deregistration Accept + Note left of UE: 6. Re-Register Max. No. of Returning UEs + UE->>Home Network AMF: 7. Unsubscribe Configuration Service (Hosting NW ID, Localized Service Info) + +``` + +Sequence diagram of the Adaptive deregistration procedure. The diagram shows interactions between Home Network AMF, UE, and Hosting Network AMF/UDM. The steps are: 1. Pre-configuration (Home AMF to Hosting AMF/UDM); 2a. Registration Request (UE to Hosting AMF/UDM); 2b. Registration Accept (Hosting AMF/UDM to UE); 3a. Subscribe Configuration Service (Hosting AMF/UDM to Home AMF); 3b. AMF determines the hosting network and the localized service specific Max. No. of Returning UEs (Home AMF internal); 3c. Notify (Home AMF to Hosting AMF/UDM); 4. Localized service termination (Hosting AMF/UDM internal); 5a. Max. No. of Returning UEs are selected for deregistration (Hosting AMF/UDM internal); 5b. Deregistration Request for Max. No. of Returning UEs (Hosting AMF/UDM to UE); 5c. Deregistration Accept (UE to Hosting AMF/UDM); 6. Re-Register Max. No. of Returning UEs (UE internal); 7. Unsubscribe Configuration Service (UE to Home AMF). + +**Figure 6.47.3-1: Adaptive deregistration procedure** + +1. There is a service level agreement between the hosting network and the home network. Based on the agreement, the hosting networks identities, locations, and the localized services information are shared with the home network. + +- 2a. UE initiates registration with the hosting network for accessing the localized service. + +NOTE 1: To identify the home network AMF of UEs, UEs share their home network given 5G-GUTI value while registering to the hosting network. In the case of roaming, UEs share 5G-GUTI of serving network that served last. Editor's note: It is FFS that how UE deregistered from hosting network would select the same serving network that served last in roaming scenarios. + +- 2b. The hosting network AMF accepts the registration of UE. + +- 3a. The hosting network subscribes for configuration service for deregistering UEs to the home network in an adaptive manner. The subscription request includes the hosting network ID, the localized service information, and the number of UEs registered for the localized service. + +NOTE 2: The interface between hosting network AMF and home network AMF can be direct or indirect. It is assumed that there is a bidirectional communication between hosting network AMF and home network AMF. + +- 3b. Upon receiving the subscription request from the hosting network, the home network AMF determines the hosting network and the localized service specific maximum allowed number of returning UEs to the home network per unit time, which is used for simultaneous deregistration at the hosting network. + +Based on the given number of UEs registered for the localized service in the hosting network, the localized service end time, and the number of UEs that can attempt to register from the home network and other hosting networks, the home network AMF determines the hosting network and the localized service specific the allowed + +maximum number of returning UEs per unit time to the home network. The home network AMF ensures that the total number of UEs attempting to register at a time from the home network and hosting networks do not exceed the maximum number of UEs that can be handled based on its processing capability in order to avoid congestion and overloading. + +- 3c. The home network AMF notifies to the hosting network the allowed maximum number of returning UEs to the home network AMF per unit time. The notification includes the hosting network ID, the allowed maximum number of returning UEs per unit time, valid time to follow this instruction, and the localized service information that UEs are accessing. + +If there is a change in the allowed maximum number of returning UEs from the hosting network to the home network AMF per unit time due to increase or decrease in the number of UEs that can attempt to register from the home network and other hosting networks, then the home network AMF notifies the new value (the updated allowed maximum number of returning UEs) to the hosting network in a new notification. In this case, the hosting network follows the instruction in the new notification and discards the old notification, i.e. the new notification always has higher precedence than the old notification. + +4. The temporary localized service time is over at the hosting network. + +- 5a. UDM coordinates with AMFs for selection of the allowed maximum number of returning UEs from hosting network based on the notification from the home network AMF. The selection is for simultaneous deregistration of UEs in an adaptive manner based on the notification from the home network AMF and ensures that the number of returning UEs from the hosting network do not exceed the maximum number of UEs the home network AMF can handle. + +There is a possibility that multiple AMFs in home network handle registration requests of UEs returning from hosting network and each home network AMF notified the allowed maximum number of returning UEs can be considered based on step 3 in that case. + +NOTE 3: The notified value of the allowed maximum number of returning UEs to the home network is valid until the valid time is expired. + +- 5b. The hosting network AMF initiates the simultaneous deregistration by sending Deregistration Request messages to the selected number of UEs in step 5a. + +NOTE 4: UEs may initiate deregistration procedure before the localized service is terminated. The hosting network AMF can handle UE-initiated deregistration requests as well. In order to allow the hosting network AMF to select the allowed maximum number of returning UEs to the home network, the service termination time of UEs can be set to slightly higher than the actual localized service termination time. + +- 5c. UEs deregister from the hosting network and the AMF accepts the deregistration. + +If UEs initiate Deregistration Request and the number UEs initiate the Deregistration Request procedure is higher than the allowed maximum number of returning UEs to the home network per unit time, then the hosting network AMF indicates the event with 'the allowed maximum number of returning UEs exceeded' parameter in a Deregistration Response message to that home network UEs. After deregistering from the hosting network, UEs which exceeded the allowed maximum number of returning UEs to that home network wait for a random amount of time before registering back to the home network or another hosting network. Otherwise, UEs initiate the registration procedure to their home network or another hosting network immediately after leaving the hosting network. + +NOTE 5: After deregistration, UEs place the hosting network NPN in a temporary forbidden list (a list of PLMN ID or SNPN ID which prohibits the UE to select the PLMN ID or SNPN IDs in this list for a certain period of time) and initiates automatic PLMN/SNPN network selection mode. + +6. Deregistered UEs leave the hosting network and initiate registration procedure to their home network or another hosting network. +7. Once all UEs registered for the localized service are deregistered, the hosting network unsubscribes the configuration service from the home network. The request to unsubscribe configuration service for a temporary localized service includes the hosting network ID and the localized service information. + +## 6.47.4 Impacts on services, entities, and interfaces + +### UE: + +- For the AMF-initiated Deregistration Request message, the UE completes the deregistration procedure. +- If the option with the new parameter 'the allowed maximum number of returning UEs exceeded' is used, the UE shall first run a random timer and wait until the random timer expires before initiating registration back to the home network or another hosting network. + +### AMF: + +- Supports to determine the hosting network and the localized service specific the allowed maximum number of returning UEs to the home network. +- Triggers network-initiated adaptive deregistration procedure. + +### UDM: + +- Supports to coordinate with AMFs for selection of the allowed maximum number of returning UEs from hosting network based on the notification from the home network AMF. + +--- + +## 7 Evaluation + +**Editor's note:** This clause provides an evaluation of the solutions. + +### 7.1 Key Issue #1: Enabling support for idle and connected mode mobility between SNPNS without new network selection + +The key issue #1 is addressed as follows: + +- For supporting the Equivalent SNPNS: + - Solution#1 considers the UE has either a subscription of source or target SNPNS while the subscription can be used to access both, or the UE has the credential from a Credentials Holder (CH) that can be used to access both source and target SNPNS (e.g. the UE has subscription of source SNPNS and access the target using the credentials from source SNPNS being a CH, or UE access source and target SNPNS using the credentials from another CH). +- Idle mode mobility: + - Solution#1 addresses this by: + - Providing the UE with a list of SNPNS identities to the UE that the UE consider as equivalent to the registered SNPNS during cell (re)selection avoiding the need to perform network selection at inter-SNPNS change. +- Connected mode mobility: + - Solution#1 addresses this by: + - Allowing equivalent SNPNS belonging to the same administrative entity being included in the MRL sent to NG-RAN. + - PDU session continuity is enabled for the case when the equivalent SNPNS belong to the same administrative entity. + +Solution #1 re-uses the principles of equivalent PLMNs functionality enabling the support of equivalent SNPNS and thereby provides enhancements to idle and connected mode mobility with minor impacts to the system. + +If equivalent SNPNs within an RA is to be supported, then NAS can be extended on top of the existing Partial tracking area identity lists (defined in Figure 9.11.3.9.2/3/4 of TS 24.501 [7]) with a new Partial tracking area identity list - type of list that includes also the NID (together with the MCC and MNC), and NGAP can be extended allowing the TAI list to be associated to different SNPNs e.g. by adding a new TAI encoding for SNPNs. The use case for supporting equivalent SNPNs within an RA would result into two or more SNPNs that are geographically overlapping or adjacent to each other and the UEs are moving between the two or more SNPNs such that the UEs would create frequent Mobility Registration Updates unless the two or more SNPNs are added to the same RA. + +The support of equivalent SNPNs impacts UE, AMF and NG-RAN. + +## 7.2 Key Issue #2: Support of Non-3GPP access for SNPN + +Table 7.2-1: Evaluation of solutions for Key Issue 2 + +| | | +|--------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #2
Access to SNPN services via Untrusted non-3GPP access network |

In this solution, UE that has successfully obtained IP connectivity via an Untrusted non-3GPP access network may select the N3IWF of an SNPN and register with that SNPN (using the credentials of that SNPN) following the same N3IWF selection procedure as specified for access to stand-alone non-public network services via PLMN.

For support of Emergency services the UE either relies on a configured N3IWF FQDN for N3IWF selection (when non-roaming) or follows the existing procedure for Emergency services for UE not equipped with UICC (when roaming).

The solution makes no special provisions for UE onboarding assuming that, either the PVS is reachable over the public Internet that the UE accesses via the untrusted non-3GPP access network, or the UE relies on an ON-SNPN with 3GPP access.

The solution has UE impact and N3IWF impact (inclusion of "selected NID" in the [NGAP] INITIAL UE MESSAGE, which is up to RAN3 to define).

| +| Solution #3
Access to SNPN services via Trusted non-3GPP access network |

The solution assumes that the non-3GPP access network advertises (e.g. with ANQP) the SNPNs with which 5G connectivity is supported, as well as the indications defined in clause 5.30.2.2 of TS 23.501 [3]. The UE is configured with one or more prioritized SNPN/GIN lists as defined in clause 5.30.2.3 of TS 23.501 [3].

For support of Emergency services the non-3GPP access network advertises the support of Emergency service (e.g. via ANQP).

For support of UE onboarding the non-3GPP access network advertises the Onboarding enabled indication (e.g. via ANQP).

The solution has UE impact, non-3GPP access network impact (additional parameters in ANQP messages) and TNGF impact (inclusion of "selected NID" in the [NGAP] INITIAL UE MESSAGE, which is up to RAN3 to define).

The solution has TS 23.402 [9] impacts if UE constructs a prioritized list of WLAN access networks by using the WLAN Selection Policy (WLANS) rules from ANSDP (currently supported only for PLMN in TS 23.402 [9]). Alternatively, the solution can rely on local configuration in the UE.

| +| Solution #4
Support of onboarding over untrusted non-3GPP access in SNPN |

This solution builds on top of Solution #2 and aims to add support for the following scenarios:

  • - access to PVS is restricted inside the ON-SNPN and the PVS is not accessible from the public internet directly over the "untrusted non-3GPP access network".
  • - UE accesses to SNPN via indirect non-3GPP access or direct non-3GPP access for Onboarding.

The additional UE impact (compared to Solution #2) includes the ability to construct a GIN-based FQDN for selection of the N3IWF/SNPN that will be used for UE onboarding, as well as inclusion of Onboarding indication in the AN parameter sent to the N3IWF during registration procedure.

The solution has several unresolved Editor's notes.

| +| Solution #5
Support of Credentials Holder scenarios over untrusted non-3GPP access in SNPN |

This solution builds on top of Solution #2 and aims to add support for accessing SNPN using credentials owned by Credentials Holder separate from the SNPN.

The additional UE impact (compared to Solution #2) includes the ability to construct a GIN-based FQDN for selection of the N3IWF/SNPN where UE accesses by using credentials owned by the Credentials Holder belonging to a group identified by the GIN.

The solution has several unresolved Editor's notes.

| +| Solution #6
Access to SNPN services via wireline access network |

The solution defines how the 5G-RG, FN-RG, and devices behind the RG (UE or N5GC devices behind an FN-RG or 5G-RG) can access SNPN services via a wireline access network. It is based on clause 4.2.1 of TS 23.316, where the SNPN is implicitly selected by wired physical connectivity between 5G-RG or FN-RG and W-AGF. The only additional requirement is that the NID is included as part of the registration procedure for wireline access system.

The solution has 5G-RG and W-AGF impact (ability to formulate the SUCI that includes the SUPI type as "IMSI" and the home network domain which includes a NID in addition to PLMN ID).

| +| Solution #16
Access to SNPN with NG-RAN and to WLAN Access Network using the same credentials |

The solution describes how UE can access an SNPN with NG-RAN on one hand and a WLAN Access Network on the other hand using the same credentials. UE uses the same permanent identity (SUCI) and credentials for primary authentication in SNPN and for WLAN access authentication in a WLAN Access Network.

For access network selection the solution assumes that either mechanisms standardised by 3GPP (e.g. using ANDSP) need to be enhanced for Non-Seamless WLAN Offload or rely on local UE configuration.

Seamless mobility is not in scope of this solution.

The solution has UE impacts. The solution has TS 23.402 [9] impacts if WLAN Selection Policy (WLANS) rules from ANDSP are used for Non-Seamless WiFi Offload (currently supported only for PLMN in TS 23.402 [9]). Alternatively, the solution can rely on local configuration in the UE.

The solution requires new authentication procedure and needs to be evaluated by SA3.

| + +| | | +|-------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #19
Access to SNPN services via Untrusted non-3GPP access network with underlay/overlay determination | This solution builds on top of Solution #2 and aims to add a new RAT Type to discriminate between direct access to SNPN services via N3GPP access (as in Solution #2) and indirect access to SNPN services via PLMN as defined in TS 23.501 [3] clause 5.30.2.8 and clause D.3. The RAT Type for these two cases would be set to "Untrusted N3GPP" or "Untrusted Non-3GPP over underlay PLMN", respectively.
The underlying assumption is that in some scenarios the access to the SNPN's 5GC may need to be restricted for one of the RAT Types, but not for the other.
The solution has UE, N3IWF and AMF impact related to the determination of the RAT Type.
The solution has an unresolved Editor's notes related to how the N3IWF determines the access network information. | +| Solution #20
Access SNPN via 3GPP and N3GPP AN using same credentials and credential holder | The solution defines how the same credentials from a credential holder external to the SNPN can be leveraged for devices accessing SNPN via 3GPP and non-3GPP access network (both connected to 5GC).
The solution has no normative impacts beyond the impact of Solution #5 (support of Credentials Holder over untrusted non-3GPP access in SNPN) and Solution #3 (support of Credentials Holder over trusted non-3GPP access in SNPN).
The scenario of UE and N3GPP device connected to 5GC via 5G-RG/FN-RG, is FFS. This scenario shall take into account the conclusion of the FS_5WWC_Ph2 study on the support of the device behind an RG. | +| Solution #21
Support for NSWOF in SNPN | The solution proposes to extend the NSWO authentication so that UE can access a non-3GPP network (e.g. WLAN or Wireline access network) using the same permanent identity and credentials as for primary authentication in SNPN via NG-RAN and 5GC.
The solution has UE and 5G-RG impacts for support of NSWO authentication using SNPN credentials i.e. credentials with user identity whose "realm" part enables routing of SWa requests from the WLAN AN to the NSWO in the SNPN's 5GC (applies both to SIM-based and non-SIM based credentials). The 5G-RG impacts have dependency on the FS_5WWC_Ph2 study (e.g. Solution #22 in TR 23.700-17 [18]). | + +## 7.3 Key Issue #3: Enabling NPN as hosting network for providing access to localized services + +Table 7.3-1: Evaluation of solutions for Key Issue 3 + +| | | +|--------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Solution#7
High level flow for localized service support

|

The service provider (can be network operators or 3rd party application providers) of the localized service needs to establish localized service agreement with the operator of a hosting network.
A service agreement between hosting network operator and UE's home network operator is needed to enable, e.g.: UE to receive and use configuration provided by a 3rd party service provider, etc.
This solution proposes to re-use traditional OAM mechanisms and existing SA5 specified mechanisms to handle the configuration aspect of hosting network.

| +|

Solution#12
Discovering services offered by SNPn while camping in a serving network

|

Current serving network (PLMN or SNPn) may assist UE in discovering hosting network for localized services in specific conditions, such as when serving network determines that UE moves into area where localized services are available.
Some level of co-operation between current serving network and hosting network is needed.
The service agreement between serving network and hosting network is assumed in place by means outside of 3GPP.

| +|

Solution#22
Hosting network to provide localized service based on default credentials

|

It is assumed that UE has default credentials that can be used in the hosting network. Hosting network broadcasts a dedicated Hosting networking service indication to show that this NPN can provide hosting networking for localized services.

  • - If there is some service agreement between hosting network and home network, the UE can be successfully authenticated by the hosting network by using credentials of home network
  • - If there is no service agreement between hosting network and home network, the hosting network performs authentication by using the UE's default credentials.

The localized services information are pre-configured in AMF of hosting network.
NOTE: Further impacts to address key issue#3 aspects are to be evaluated when additional details/clarifications are available.

| +|

Solution#41
Provisioning of Credentials via Hosting Network PDU Session

|

The solution mainly resolves how the Hosting network can perform "on boarding" of UE for a particular localized service. For KI#3, it only focuses on what kind of information needs to be exchanged between the Localized service provider and the Hosting network.
Localized service provider may provide captive portal information to hosting network during service agreement phase. How the localized service information is available to UE is assumed to be provided by others solutions. User may manually choose a particular hosting network. UE may include the selected localized service in the request. AMF responds the request which may include DNN, S-NSSAI, an indication to trigger PDU Session creation. A PDU Session could be established to connect UE and localized service provider. UE can get the credentials in the PDU Session.
NOTE: The security impacts shall be evaluated by SA WG3.

| + +## 7.4 Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services + +### 7.4.1 General + +The evaluation for KI #4 solutions is made for each component listed below: + +- The content of the localized service information that is used by UE to perform discovery/selection/access to the hosting NW for localized services. +- From where and how UE obtains such localized service information. + +- How the localized service information is used by UE. +- What credentials are used to access hosting network and how to obtain them if required. +- How localized service is accessed in hosting network per agreed conditions, e.g. time/location. + +Furthermore, since Hosting Network based on the architecture assumption and requirements in clause 4 as below + +- Hosting network can be NPN, i.e. SNPN, PNI-NPN +- Home network can be NPN or PLMN + +If the UE accesses the Hosting network using the subscription/credentials from the UE Home network, there are only two scenarios considered in such case: + +- If the Home network of the UE is PLMN, the Hosting network could be PNI-NPN or SNPN. +- If the Home network of the UE is SNPN, the Hosting network could be only SNPN. + +The case the Home network of the UE is SNPN and the Hosting network is PNI-NPN is not existed according to below SA1 requirement in clause 6.41.2 of TS 22.261 [2]: + +- Only subscribers of a public network can roam into a PLMN. + +Furthermore, if the UE has multiple hosting subscriptions/credentials, that which subscription/credential to use for automatic Hosting network selection is determined by implementation specific prior to network selection as same logic specified in clause 5.30.2.4 of TS 23.501 [3]. + +## 7.4.2 Evaluation for the content of the localized service information + +**Construct the information on localized service basis (Sol #11, #12, #13, #15, #24, #26, #27, #31, #32, #34, #42).** + +- The information includes an element to distinguish different localized service (e.g. identifier, name of the localized service), service availability (e.g. time, duration and location), validity conditions (time/location), local service captive portal address, associated hosting networks' information (e.g. hosting network identifier, temporary credential or credential type for accessing hosting network, CAG IDs, QoS, cost, information transmitted in the Hosting network's SIB, etc.). +- The localized service information may include either (a) a list of one or more Hosting Network Identifiers, or (2) information which is broadcasted by the Hosting Network (e.g. CAG IDs, localized service ID) used by the UE to select the Hosting network. + +NOTE: Credential provisioning mechanisms need to be evaluated by SA WG3. + +- The benefit of this principle is to provide UE/end user with relationship between localized services and hosting networks, so that it enables the possibility for UE/end user to make request on specific localized service and for network to inform UE what are the available localized services and over which hosting networks these localized services are provided. + +**Construct the information based on priority list for Hosting network selection (Sol #10, #14, #18, #25, #29, #30, #33, #36, #43).** + +- The information is a new priority list for Hosting network selection. Each entry on the list includes hosting network identifiers, validity conditions (time/location), etc. +- This principle requires other solution components (e.g. Sol #12, #13, #24, #30) to complement, since the information does not include reference to the localized services available over the different hosting networks included in the priority list and therefore it assumes that either UE or the network providing this information knows beforehand which localized service end user intends to access or what are the localized services supported by the hosting network on the priority list. + +The localized service information in Sol #22 and Sol #46 provided by hosting network to UE, is not used for selecting hosting networks (instead the UE has registered to a hosting network based on a prioritized list of Hosting network), but rather for UE to know how to access a service in the hosting network which can be addressed by existing functionality, such as URSP rules. + +According to existing mechanisms, network selection and traffic offload (to another access network) are two separated mechanisms and controlled by different rules/policies. + +Normally, a UE would request to use a specific application (for a specific Localized service) when the UE is in the coverage of the corresponding hosting network. After a UE selects and accesses into a hosting network, the UE would obtain Allowed S-NSSAI from the hosting network. The UE can use the URSP (received from the home network or hosting network) to determine which S-NSSAI/DNN is used for a localized service. + +To support a UE selecting and accessing into a hosting network, a hosting network list is needed. + +### 7.4.3 Evaluation for from where and how UE obtains the localized service information + +UE can obtain the localized service information from application server, serving network, home network, or hosting network. + +#### UE fetches the information from an application server (Sol #14, #28, #31, #40). + +- When a full set of new subscription/credential is provided to UE via application server, this principle has less system impact on 5GS. But on the other hand, home network subscription/credential is utilized for the UE to establish PDU connection with the application server and the UE needs to handle co-existence of multiple subscriptions/credentials on device. +- When the information includes a list of hosting networks and an indication that home network credential is to be used, there will be impact on network selection. Application server obtaining such information via network exposure is not necessary, since it is covered as part of the SLA between localized service provider and hosting network operator. + +#### UE fetches the information from home network (Sol #10, #13, #14, #15, #18, #23, #24, #29, #30, #31, #33, #36, #43). + +- This principle assumes that home network is capable of managing the localized service information data. +- The impact is about how home network is provisioned with the localized service information data, and how UE is provisioned by the home network. +- Most of the solutions following this principle propose that the home network provides the localized service information to UE via SoR procedure in combination with the principle that the localized service information is constructed based on a priority list for (hosting) network selection as described in clause 7.4.2. + - Some solutions assumed that the SoR-AF within the home network should be involved as the data source and the mechanism regarding how SoR-AF obtains such data should be out of 3GPP scope. Some solutions (Sol #14, #43) assumed the data source for SoR procedure is obtained from other NFs than SoR-AF. + +NOTE 1: In the current specifications, SoR-AF is the only entity that creates the SoR message if there is a need to dynamically change the content of the SoR information. + +- Since SoR procedure is mainly used for network discovery and selection, it is not suitable to be extended to provision UE with data more than required for the UE's actual network discovery and selection. + +NOTE 2: The current specifications provide the means for the serving network to provision the UE with information relevant for the serving network once the UE has registered to the hosting network e.g. network slicing information. + +- Sol #24 proposes another variant for UE to fetch the information from home network, that is via home network UDR and new UE policy. UE policy has the potential to include necessary data of the localized service, and possibility to be extended in the future. The new UE policy can be delivered to UE by PCF in home network, or PCF in serving network using N24. + +#### UE fetches the information from serving network (Sol #11, #12, #24, #27, #32, #42, #44). + +- This principle assumes serving network (either home network or another network which UE is accessing using home network credential) is capable of storing the localized service information data. This principle enables multiple information sources for UE to obtain localized service information. + +- If the current serving network is not the home network, this principle also provides mechanisms for home network to authorize or determine the final data that UE will receive, where the serving network either checks a subscription flag (Sol #12, #24, #32) or passes the localized service data to home network for authorization and delivery to UE (Sol #12, #42). +- The impact is about how serving network is provisioned with the localized service information data, and how UE is provisioned by the serving network. +- Some solutions following this principle proposes to use AMF/SMF in serving network to store the localized service information data. In this case, the provisioning to serving network is based on configuration which has less impact, but it requires the UE is served by the correct AMF/SMF configured with such information (e.g. UE is located in the overlapping area where the hosting network is available) or requires all the AMF/SMF in the serving network are configured with such information. The data is provisioned to UE via MM NAS or SM NAS message (it is TBD which procedures/messages are impacted). +- Other solutions following this principle, proposes to use UDR in the serving network to store the localized service information data as application data for any UE registered to the serving network. This enables the flexibility that if the serving network is not the home network, UE can obtain localized service information data from either the serving network, or from the home network, or from both. The impact is to extend service specific parameter provisioning for the serving network to receive the data (see clause 4.15.6.7 of TS 23.502 [4]) and new UE policy to provide the data to the UE. + +**UE fetches the information from hosting network (Sol #22, #26, #34, #41).** + +- This principle assumes a hosting network is selected prior to a localized service is selected, since the localized services information arrives later from the hosting network. It can happen that the fetched information is not interesting for the end user. +- The impact is to extend broadcast with capability for localized service, service discover policy that allows UE to query information from hosting network while in RRC-IDLE/INACTIVE with serving network, new on-demand SIB, or code for URL. Another impact is to deliver localized service information via registration reject/accept message. + +NOTE: Privacy aspect needs to be evaluated by SA WG3. + +- This principle implies that in some scenarios the UE needs to suspend the connection with or suppress the paging from the serving network when getting information from hosting network, which can cause service interruption. + +There are different triggers to provision the information to UE: + +- **UE request as trigger (Sol #11, #13, #15, #24, #27, #32, #34, #42).** +- **UE location as trigger (Sol #11, #12, #18, #27, #32).** +- **UE subscription data change via external parameter provisioning as trigger (Sol #14, #23, #43).** +- **UE Steering of Roaming information update (SoR based solutions).** + +UE request as trigger assumes UE/end user is aware of the desired localized services. UE location as trigger requires the serving network is aware of which hosting network is available in which serving network tracking areas, and the information sent to UE is unsolicited. UE subscription data change and SoR based solutions restrict the information source to home network only. + +There are different architectures/business relationships between home network and hosting network or Localized service provider. + +- Business relationship / roaming interface exists between home network and hosting network or Localized service provider. + - In this scenario, the home network knows about the hosting network or the Localized services. Therefore, it is reasonable for the home network to provision obtain hosting network information/localized service information to the UE. + - Moreover, UE can use its home network credentials to access hosting network. + +- To allow flexible deployment and use of Localized service, it would be benefit to allow update the above information to the UE timely, after the UE requesting for the Localized service. The UE can request via OTT, then LSP can notify the home network of the UE to send the above information to the UE. +- No business relationship / roaming interface between home network and hosting network. + +In this scenario, the home network does not know about the hosting network or the Localized services directly. There are two sub-scenarios regarding the business relationship between visiting network and hosting network or Localized service provider: + +- Business relationship / roaming interface exists between visiting network and hosting network or Localized service provider + - In this scenario, the visiting network knows about the hosting network or the Localized services. Therefore, UE can obtain hosting network information/localized service information from the visiting network. In order to enable control from home network, home network authorization is required before sending the information to the UE. + - In this scenario, UE cannot use credentials from home network to access hosting network. Therefore, other credentials e.g. default credentials can be used to access hosting network. +- No business relationship between visiting network and hosting network/ Localized service provider + +In this scenario, neither home network or visiting network know about the hosting network or the Localized service. The UE can only obtain hosting network information/ localized service information from hosting network or the Localized service provider. + +- UE obtains localized service information from hosting network + - in this scenario, manual network selection is used for hosting network discovery and selection; + - default credentials are used for the first time accessing to hosting network; + - credentials of hosting network can be provision to the UE. +- UE obtains hosting network information/ localized service information from Localized service provider + - In this scenario, the UE may also obtain the following information from the Localized service provider: + - default credentials to access hosting network; + - credentials to access localized service from the Localized service provider; + - configurations to access localized service from the hosting network; + - The above procedure is considered as OTT solution and would have no standard specifications. + +Although the first scenario (i.e. Business relationship / roaming interface exists between home network and hosting network or Localized service provider) is considered as the main scenario, it would be benefit to consider the other scenarios to support flexible deployments of hosting networks. + +#### 7.4.4 Evaluation for how the localized service information is used by UE + +New network selection mode is proposed (Sol #10, #25, #30, #33), where UE selects only hosting network when it intends for localized services and bypasses or temporary stops existing network selection procedure. This is needed if the UE is using home network credential to access hosting network, since home network and hosting network could be collocated in the same area and UE will always prioritize home network based on existing network selection mechanism. The new network selection mode can be requested by UE and authorized by home network (Sol #25). + +The time and location validity condition along with other localized service information as described in clause 7.4.2 provided to UE can be used as a criteria for the UE to determine when and where to enter the new network selection mode. + +Except the validity conditions, other methods for UE to determine whether to enter hosting network selection mode are also proposed, e.g. serving network to indicate to UE the presence of hosting network via either NAS or broadcast (Sol #12, #29, #30), which requires extra system impacts. + +#### 7.4.5 Evaluation for what credentials are used to access hosting network and how to obtain them + +If home network credentials are also used to access hosting network, existing mechanisms can be re-used for enabling access to hosting network, such as roaming architecture or Credentials Holder function. + +Minor enhancements are proposed to indicate to the UE that hosting network support CH function (Sol #12), or to indicate to the UE that home network credentials can be used as credential from CH to access specific hosting network (Sol #40). Whether hosting network support of CH function can be detected by UE via existing SIB broadcast. Whether home network can act as CH can be implicitly determined by whether there are priority lists for SNPN selection configured/provisioned on UE. But if hosting network selection does not use existing CH/User controlled priority lists for SNPN selection, there will be a gap for UE to know if home network credential can be used, or it needs to obtain a new set of credentials from somewhere else. When home network credential is used to access hosting network, it requires connection between home network and hosting network as described in clause 5.30.2.9 of TS 23.501 [3]. + +If separate credentials from the home network credentials are needed to access hosting network, the credentials can be obtained via: + +- application layer (Sol #12, #14, #28). +- NAS layer (Sol #12, #13, #14, #15, #42). +- enhanced onboarding procedure in SNPN type of hosting network (Sol #12, #22, #41). +- enhanced user plane remote provisioning procedure in serving network (Sol #40). + +Provisioning credentials via application layer is out of 3GPP scope. + +Provisioning credentials via NAS layer needs to be coordinated and agreed with WG SA3, since there is no existing NAS layer procedure suited for credential provisioning based on previous study conclusion in TR 33.857 [22] (Rel-17 FS\_eNPN\_SEC). + +Existing onboarding procedure in SNPN requires that the UE is pre-configured with Default UE credentials and other information, while Sol #12 proposes UE to obtain such onboarding related credentials/configuration via control plane signalling. + +Onboarding without primary authentication requires coordination with SA WG3. + +Minor enhancement for user plane remote provisioning enables UE to request specific hosting network related provisioning server (Sol #40), also enables the possibility for UE to obtain onboarding related credential/configuration via user plane. + +#### 7.4.6 Evaluation for how localized service is accessed in hosting network per agreed conditions + +The validity conditions of the localized service provided to UE can restrict the UE to access a hosting network per agreed conditions. + +For hosting network supporting large areas and multiple localized services, Sol #10 proposes to divide the hosting network SNPN to smaller sub-networks via a new identity (Subnetwork ID), and then UE in hosting network can be restricted to certain areas. The access restriction is on cell level, which prevents UE from selecting/camping on the cell. Such strict access control is more suited and needed in e.g. factory production environment. There are also many existing mechanisms to divide the network to smaller parts, e.g. network slicing, forbidden area restriction, service area restriction, etc. + +Sol #11, #27, #45 proposes to re-use existing LADN mechanism to restrict UE from accessing the DN when UE is out of the specific area (TAI). The access restriction is on PDU session level. Sol #45 also proposes to utilize the location report control if the granularity of localized service is not on TAI level, but on cell level. + +Sol #35, #46 proposes to re-use URSP rule to enable UE to access localized service when the RSD validity conditions are met. The access restriction is also on PDU session level. + +## 7.4.7 Evaluation for the scenario where hosting network is a PNI-NPN + +### - For credentials used for accessing hosting network: + +All the solutions propose to use home network credentials are used to access hosting network. Roaming interface between hosting network and home network is needed to support primary authentication procedure. + +### - For hosting network selection information provision to the UE: + +All the solutions propose to send Allowed CAG ID list to the UE. + +Solution #10, #12, #23, #32, #43 propose to reuse Allowed CAG ID list provided from the home network. + +Solution #11 and #27 proposes that the serving network provides Localized Service Information to the UE. The impact includes configurations in the AMFs in the serving network (home network and visiting networks) with Localized Service Information. + +### - Potential enhancement to Allowed CAG list: + +Solution #10 proposes to enhance the Allowed CAG list by including Validity time period and Location. It is also clarified that Location information for Allowed CAG list only needed if PNI-NPN as hosting network can be a subset of a CAG. + +Solution #12 clarify that the CAG cell(s) are inherently associated with location or spatial validity condition(s) and hence additional spatial validity condition is not required to be provided with Allowed CAG list. Network Slice Selection Policy (NSSP) could be associated with hosting network specific time validation criteria. + +### - For localized service information provision to the UE: + +Solution #11, #27 and #32 proposes to send Localized Service Information to the UE. + +They all proposes to include Localized Service Name and Validity condition. Solution #11, #27 also propose to include LADN DNN used in the hosting network. + +### - For triggers of sending hosting network selection information/localized service information to the UE: + +- UE request as trigger (Sol #11, #27, #32). +- UE location as trigger (Sol #12). +- UE subscription data change via external parameter provisioning as trigger (Sol #14, #23, #43). + +To allow flexible deployment and use of Localized service, it would be benefit to allow the UE to request for the Localized service then the home network can update the corresponding information to the UE (e.g. Allowed CAG ID list, S-NSSAI, DNN, potential URSPs, etc.) The UE can request via NAS, the network can authorize the request, optionally with confirmation with the LSP. The UE can also request via OTT, then LSP can notify the home network of the UE to send updated information to the UE. + +### - For how the UE uses the hosting network selection information/localized service information: + +- Solution #10 and #23 propose that when the validity information is met in the Allowed CAG list, the corresponding CAG ID is considered for selection. +- Solution #11 and #27 propose that the UE shall use the Allowed CAG information only when the UE access the hosting network for the Localized service. +- Solution #32 proposes that UE may start searching and accessing the CAG cell that supports the local service by manual input or based on service available time. + +### - For whether home network is a PLMN or SNPN: + +- Solution #27 includes a scenario where Home network is a SNPN and hosting network is a PNI-NPN. Therefore, a UE can access a PNI-NPN using SNPN credentials. + +According to the current specifications, when the visiting network is a PLMN, the home network shall be a PLMN. (Due to that a SNPN UE cannot access to a PLMN using SNPN credentials) + +If business relationship exists between the two PLMNs (supporting hosting network and home network), it is also reasonable to assume that the home network knows about the CAG ID of the hosting network. Therefore, the existing mechanism of providing Allowed CAG list from the home network can be reused for sending hosting network information to the UE. + +The proposed Localized service information includes Localized service ID. Existing identifies used to identify a service supported in a PNI-NPN include S-NSSAI, DNN. + +## 7.5 Key Issue #5: Enabling access to localized services via a specific hosting network + +**Table 7.5-1: Summary of solutions for KI#5** + +| | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #7 | The solution provides the high level entities and procedures for providing access to localized services, accessing localized/home services, and charging information for the home network operator. | +| Solution #11 | Solution is reusing existing roaming architecture and LADN mechanism.
The UE uses the local breakout session for accessing specific services from hosting network and home routed session for accessing services from the home network. Only PNI-NPN as Hosting Network is considered. | +| Solution #13 | The UE will be configured with the N3IWF address of the home network, wherein for accessing the home network services. The UE uses the hosting network as an underlay network. | +| Solution #15 | The solution focuses more on KI#4. | +| Solution #18 | Solution proposes to use the existing mechanism i.e. Steering of Roaming to allow the service provider (PLMN or 3rd Party service provider) to update the UE with required information on availability of hosting networks along with the localized services they are providing. Steering of Roaming information container would carry the "operator defined hosting network selector list", which will assist the UE to switch to hosting network for obtaining localized services. | +| Solution #27 | Solution is reusing N3IWF overlay architecture and LADN mechanism, i.e. 5G System architecture with access to SNPN using credentials from Credentials Holder and 5G System architecture accessing overlay network (home network) via underlay network (hosting network). The solution is built on top of solution #11. | +| Solution #28 | The UE (User) obtains the time restricted credentials from the LSP via the home network and uses that information for selection of hosting network as well as to access localized services. N3IWF node used to access home network services. | +| Solution #35 | The home network provides URSP which maps local services to its S-NSSAI and DNN. The registration of the S-NSSAI related to local services causes the cell/network reselection. | +| Solution #36 | There are two options are presented, one is using validity conditions provided by home network to UE to make sure UE only access the hosting network with satisfying those conditions. The other options presents that, home network and UE coordinate, wherein home network would either use the UE location to get information about target suitable hosting network performance information via target hosting network (e.g. SNPN) NEF or home network would instruct the UE to measure and report the signal reception status of the potential target hosting network(s). Based on the information received from the UE, the home network would send SoR (Steering of Roaming) instructions to steer the UE toward the target hosting network (e.g. SNPN). | +| Solution #37 | The solution defines a new network function LSF (Localized Service Function) in the home network and hosting network that specifically handles information related to localized services. The new network function will provide information to AMF about all available localized services at the UE location and this information about localized services will be shared with the UE via NAS signalling. | +| Solution #40 | The solution focuses more on KI#4 and for KI#5, it is regarding to how the home network steers UE to the hosting network. The solution proposes to use deregistration procedure to trigger the steering of UE to hosting network. The AMF/SMF supports configuring the mapping of [Credential Information] and [Hosting network identifier] for specific localized service and responds to UE with proper [Credential Information] associated with a hosting network SNPN. The home network AMF informs NG-RAN regarding the target hosting network identifier based on request from UE and let NG-RAN to perform release and redirect UE to the target network. It has impact on UE/NG-RAN/AMF. | +| Solution #45 |

The solution reuses the LADN mechanism with some enhancements. The enhancements are:

  • - UE shall support including localized service identifiers in PDU Session Establishment Request.
  • - AMF determines the location conditions of the UE to decide whether the UE meets the conditions that allow it to obtain the localized service.
  • - SMF determines whether the UE meets the validity information of the localized services. If the validity information is set to the location, the SMF subscribes UE mobility event notification to AMF. If the validity information is set to time, the SMF monitors the duration that the UE can access the localized services. If the UE does not meet the conditions, SMF receives a notification from the AMF, and instructs the UPF to stop forwarding traffic flow of the localized service. The solution has UE, AMF and SMF impacts.

For the above, the condition is assumed that UE has registered to a Hosting network and the UE wants to establish the PDU Session for access the localized services available in the currently registered Hosting network.

| + +| | | +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #46 |

The solution reuses existing URSP procedures, wherein the UE evaluates the URSP rules to use the PDU session for accessing the localized services in the hosting network. The time window and location criteria are configured according to the validity information of the localized services and only when the RSD criteria of the matched URSP rules are satisfied, the UE establishes a new PDU session or re-uses the existing PDU session for the localized services. There are UE and H-PCF/V-PCF impacts.

Furthermore, the solution also describes the order if the UE has multiple URSP rules from HPLMN or from the subscribed SNPN.

For the above, the condition is assumed that UE has registered to a Hosting network and the UE wants to establish the PDU Session for access the localized services available in the currently registered Hosting network.

| +|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +In several solutions (e.g. #18, #36, etc.), existing SoR mechanism with some enhancement is proposed to be used for the home network to steer the UE to the hosting network. This approach addresses the KI well and has limited impacts on the UE and network. + +In the solutions (e.g. #18, #36, etc.), the typical conditions for steering the UE to a specific hosting network are: + +- The time and location of UE has met the validity condition of a local service (e.g. #18). +- signal threshold which may be different for different localized services / hosting networks has met the validity condition of the hosting networks (e.g. #36). + +For the aspect of enabling access to both home network services and local services, several solutions propose to use existing overlay/underlay architecture to access the target network through N3IWF. This approach addresses the KI well and has limited impacts on the UE and network. + +- When a UE accesses both a hosting network and a home network using the overlay/underlay architecture, the underlay can support the localized service requirements e.g. high throughput, low latency and the ability to apply the location requirements in a suitable way and therefore the UE better access the localized services through the underlay network. +- According to the current specifications, when the visiting network is a PLMN, the home network shall be a PLMN. (Due to that a SNPN UE cannot access to a PLMN using SNPN credentials). When the UE is accessing a PNI-NPN hosting network, Home Routed PDU session can be established to access home network services. No need to use overlay/underlay architecture in this scenario. + +In several solutions (e.g. #35, #46), existing network slicing and URSP mechanism with some enhancements are proposed to be used for the UE to access the Localized Services in the registered Hosting Network. These approaches address the KI well and have limited impacts on the UE and network. + +For the aspect of enabling UE to access localized services based on the certain location and time condition of localized services, there are several methods as follows: + +- Reusing the existing LADN mechanism (e.g. #11, #27) to meet the location condition. For the time condition, it is realized by AMF/operator that combines LADN DNN with validity time. +- Using the enhanced LADN mechanism (e.g. #45) to meet the location condition. For the time condition, it is realized by SMF monitors the service time after the UE starts obtaining the localized service. + +Reusing the existing URSP mechanism (e.g. #35, #46) to meet the location and time condition. The Route Selection Validation Criteria (i.e. Time Window and Location Criteria) of the matched URSP rules should be fulfilled. Which is currently evaluated when establishing a PDU Session. + +## 7.6 Key Issue #6: Support for returning to home network + +The solutions for KI#6 are proposed to address the UEs returning from the Hosting Network to their Home Network (i.e. HPLMN/VPLMN, SNPN) when the Localized Services in the Hosting Network are completed. Under the condition, it may cause many UEs returning back to e.g. their Home Network and this may result in signalling overload in their Home Network. + +NOTE: Home Network is used, but the network selected by the UE depends on the UE's network selection and what networks are available e.g. UE can return to VPLMN different from the PLMN the UE was registered to before selecting the Hosting Network. + +When considering solution proposals for KI#6, there are two categories for handling signalling overload resulting from the UEs returning to their Home Network: + +1. The avoidance-based method: it mitigates or avoids overload at home network and it can be further classified into three subcategories based on the principles in the proposed solutions, + - a) the UEs is (pre)-configured with a timer/waiting time based on the Validity Information of the Localized Services and/or the NWu status and the availability of the home network of the UE e.g. by the Home Network or by the Hosting Network, + - b) the home network negotiates/communicates once with the hosting network as part of a service level agreement to configure the number of UEs can be deregistered from the hosting network to the home network per unit time, and + - c) the home network negotiates/communicates with the hosting network continuously by utilizing “subscribe-notify” communication service to configure the number of UEs which can be deregistered from the hosting network to the home network per unit time adaptively without causing an overload at the home network, and the hosting network instructs UEs which exceed the home network given maximum limit to wait for random amount of time before initiating re-registration to their home network if UEs initiate deregistration requests. +2. The runtime-based method: it handles overload at home network using the existing mechanisms and it can be further classified into three subcategories based on the principles in the proposed solutions, + - a) the UEs directly return to their Home network when the Localized Services terminate and the Home Network will use the existing mechanisms to handle the signalling overload if the congestion happens, + - b) the home network and/or local hosting network may group the UEs to create an Internal-Group Identifier specific to local hosting network(s) and/or local service(s), and then the home network AMF or SMF applies the existing UE group-specific NAS level congestion control mechanism to manage UEs returning from a local hosting network to their home network, and + - c) the UEs directly return to their home network when the Localized Services terminate and the home network uses localized hosting network specific back-off timer to adaptively reduce the overall waiting for UEs before re-register to their home network. + +For avoidance-based method (i.e. Solutions #9, 10, 13, 25, 38, 47), hosting network either determines the timer or maximum number of UEs on its own (e.g. Solution #9, #10,) or uses the home network input to determine it (e.g. Sol#47). + +For runtime-based method (i.e. Solutions #8, 17, 39), the Home Network applies the existing congestion control and overload control to the UEs for returning from the Hosting Network but cause congestion overload. The UEs registers to the Home Network by indicating they are back from the Hosting Network. If the Home Network is in a congestion condition, the Home Network can reject the UE with a cause and a back-off timer. + +To compare the avoidance-based and runtime-based methods, the differences are below: + +- The avoidance-based method can allow the UE to return to their Home Network in a distributed or staggered manner to prevent the congestion or overload conditions happen in their Home Network. +- The runtime-based method directly applies the existing mechanism optionally with some enhancement (e.g. hosting-network specific backoff timer). + +Category 1-a of the avoidance-based method potentially delays the UEs return to the Home Network also for the cases when the Home Network is not overloaded/congested. It is also expected that the user itself can decide to stop using the Localized Service i.e. in these cases the UE would return back to the Home Network disregarding the spreading applied for the UE's return. + +The runtime handling has allowed the UEs to initiate the Registration procedure as soon as wanted and then if the Home Network is congested rejected the UE with a back-off timer in which the Home Network has been through the signalling congestion from those returning UEs from the Hosting Networks (unless Home Network is so congested that e.g. UAC is used). + +**Table 7.6-1: Summary of solutions for KI#6** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #7
High level flow for localized service support (Category: Not applicable) |

The solution provides the high level entities and procedures for providing access to localized services.

This solution does not cover the impact on different entities, services, and interface, will be covered by other specific solutions.

| +| Solution #8
Reuse existing mechanisms for Control Plane Load Control, Congestion and Overload Control (Category: 2-a) |

The proposed solution is to reuse existing mechanisms for Control Plane Load Control, Congestion and Overload Control, to mitigate signalling overload when large number of UEs return to their home network.

As the solution proposes to reuse the existing mechanisms, it is noted that there is no impact on services, entities and interfaces.

The existing mechanisms do not mitigate overload at home network when large number of UEs return to their home network after accessing a localized service. Moreover, assigning random back-off time values to UEs to initiate the next re-registration attempt at different time to reduce the signalling load would increase the overall waiting for UEs before re-register to their home network.

| +| Solution #9
Prevention of overload build up at home network using AMF based congestion control when local service is over (Category: 1-a) |

This solution proposes to deregister UEs accessed to localized services in a staggered manner before the termination of local hosting network. In order to achieve this, two mechanisms, namely, usage of network availability timers and specific cause code to trigger a controlled deregistration are proposed.

The solution assumes that the hosting network is able to determine the exact timing when the local service stops and UEs need to leave, which may not be the case for most scenarios.

The solution has an impact on UE and AMF. For the UE, the impact is to support new cause codes, service availability timer and related implementation. For the AMF, the impact is to handle new timer for UEs accessing to local services and to support new cause code in network-initiated de-registration request.

The solution prevents any overload condition cause by simultaneous registration request coming from all the returning UEs. However, a local hosting network may not know the actual capacity of the home network to deregister UEs accordingly to utilize the home network's resources efficiently, and the overall waiting time of UEs would increase because each UE has to wait until the assigned random service availability timer expires.

| +| Solution #10
Solution for discovery and selection of NPN hosting network and localized services (Category: 1-a) |

Although this solution mainly addresses KI#4, it also provides a solution for KI#6.

It is proposed that either the UE applies a random delay before initiating a PLMN selection or HPLMN (or Credentials Holder) configures UEs with slightly different end time to the validity time period.

The end time of validity condition may not always be the same as the real end time of the service. It can't be assumed that UE's returning to the home network is triggered by the time validity condition. Moreover, it would increase the overall waiting time of UEs if a local hosting network alters the service end time of UEs without knowing the actual capacity of the home network which handles returning UEs.

| +| Solution #13
Exposure enhancements to support providing access to localized services (Category: 1-a) |

This solution proposes that the hosting network may group UEs based on the reported NWU status and the UEs home network availability when UEs return to their home network from the hosting network. The hosting network assigns a random back-off timer value to UEs based on which group the UEs belong to among four groups. Then, UEs should wait until the assigned back-off timer expires to initiate re-registration procedure to their home networks.

The solution has an impact on UE and AMF. The UE, when receiving the end indication of the localized service from the hosting network AMF, checks that all local services are ended, and reports Nwu interface status and related home network identity (e.g. PLMN ID) to the AMF. The hosting network AMF groups the UEs and send back-off-timer to the UEs. This solution would mitigate an overload at the home network. However, it may increase the overall waiting time for UEs before re-registering to their home network because the home network capacity and load condition are not considered by the hosting network.

| + +| | | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #17
UE Group specific NAS level congestion control
(Category: 2-b) |

The solution proposes to use group specific NAS level congestion control mechanism to mitigate user plane and control plane overload. The home network associates UEs temporarily accessing localized services to an Internal-Group Identifier, which can be specific to each local hosting network and/or service and applies UE group-specific NAS level congestion during the return of UEs.

The solution has an impact on UE/AMF to support localized service related de-registration information, NEF to support exposure from local hosting networks, UDM to support local hosting network/service information in Internal-Group identifier and AMF/SMF to apply Group Specific NAS level congestion control.

This solution requires UE to request registration in the home network and then the AMF of the home network applies UE group-specific NAS level congestion control. Naturally, this solution does not prevent an overload condition as the RAN and the AMF will get registration request from all the returning UE and this may lead to increased load in the system. Moreover, assigning random back-off time values to UEs to initiate the next re-registration attempt at different time to reduce the signalling load would increase the overall waiting for UEs before re-register to their home network.

| +| Solution #25
(Category: 1-a) |

Although this solution mainly addresses KI #4, it also provides a solution for KI #6.

This solution proposes that the home network UDM/SOR-AF can set an offset value to the authorized start/stop time for UEs as part of enabling Temporary Network Reselection procedure in order to avoid congestion/overload at the home network.

This solution potentially can mitigate the congestion/overload at the home network. However, setting offset value to the start/stop time for UEs in a pre-determined way would increase the overall waiting time for UEs before re-register to their Home Network.

| +| Solution #38
Sequential deregistration by hosting network
(Category: 1-b) |

This solution proposes to control the number of returning UE based on service level agreement between the home network and hosting network.

The solution relies on that the hosting network can group the UEs according to their home network, but it remains unclear how it is achieved. Moreover, it may not mitigate the congestion/overload at the home network because the congestion level at the home network may vary overtime based on the number of UEs returning from different hosting networks to their home network. Hence, a continuous communication/negotiation between the home network and the hosting networks are expected and not considered in the proposed solution.

The solution has an impact on UE and AMF. For the UE, the impact is to support finishing deregistration procedure where the termination of the localized service is indicated by AMF and to support return of the UE to its home network. For the AMF, the impact is to support indication of localized service termination as part of the Deregistration request message and to support triggering deregistration in a sequence manner in a way that the maximum number of returning UEs at a given units of time does not exceed the configured number at AMF.

| +| Solution #39
Local hosting network specific back-off timer
(Category: 2-c) |

This solution proposes a local hosting network-specific flexible back-off timer range and back-off timer assignment to spread out the registration attempts over time and limit the number of users attempting to register back to their home network simultaneously in order to avoid signalling overload and unnecessary waiting times for the returning users.

The solution effectively avoids using uniformed non-optimal back-off timers for all UEs.

The solution has an impact on UE and AMF. For the UE, the impact is to support sending the local network indication as part of the new registration request ("re-registration from hosting network" or "local network access indication"). For the AMF, the impact is to support new registration type/indicator related to local hosting network re-registration and assignment of a local hosting network-specific back-off timer range.

This solution requires UE to request registration in the home network and then the AMF of the home network provides a back-off timer. This solution does not prevent an overload condition as the RAN and AMF will get registration request from all the returning UE and this may lead to increased load in the system.

Though this solution may not mitigate an overload at the home network, it can reduce the overall waiting time for UEs before re-register to their home network by setting local hosting network specific back-off timer in an adaptive manner.

| + +| | | +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +|

Solution #47
(Category: 1-c)

|

This solution solves the problem of overloading at home network and reducing the unnecessary waiting time of UEs before re-register to their home network. The proposed solution deregisters UEs from the hosting network to the home network in an adaptive manner based on the input from the home network (i.e. the allowed maximum number of returning UEs from the hosting network to the home network AMF per unit time based on the network load condition at the home network). If network condition varies at the home network, then the home network AMF notifies a new value (i.e. the new allowed maximum number of returning UEs per unit time) to the hosting network in a new notification such that the number of UEs deregistered from the hosting network to the home network can be controlled adaptively to mitigate an overload/congestion at the home network.

This solution has an impact on UE, AMF, and UDM. For the UE, the impact is to support to wait for a random amount of time before initiating re-registration procedure to the Home Network if the number of UEs attempting to return to the Home Network exceeds the given maximum allowed value for the case of UEs initiate the Deregistration Request. For the AMF, the impact is to support to determine the hosting network and the localized service specific the maximum allowed number of returning UEs to the home network. For the UDM, the impact is to support to coordinate with the hosting network AMFs for selection of the allowed maximum number of returning UEs to the home network based on the notification from the home network AMF.

This solution effectively avoids an overload/congestion at the Home Network, efficiently utilizes the available resources in the home network AMF, and does not hold UEs to wait unnecessarily. This solution also supports to handle UE-initiated deregistration requests and instructs UEs to wait random amount of time before attempting re-registration to their home network if the number of UEs initiated deregistration requests exceeds the home network given maximum value to mitigate the overload at the home network.

| +|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +In the avoidance-based solutions (Category 1), there are three subcategories based on the principles used to address the requirements mentioned in the KI #6, which are summarized as follows: + +- Category 1-a based solutions are based on the principle of pre-configuring UEs service end time either by the home network or hosting network to spread out the registration attempts over time and limit the number of simultaneous attempts in a very short period of time in order to mitigate an overload/congestion at the home network. Though the category 1-a based solutions potentially mitigate the overload at home network, they would increase the overall waiting time for UEs before registering to their home network as all UEs are pre-configured to make re-registration attempt to their home network at different point in time without knowing the actual capacity of the home network AMF. +- Category 1-b based solutions are based on the principle of one-time negotiation/communication between the home network and the hosting network to deregister the number of UEs simultaneously per unit time from the hosting network to the home network without causing overload/congestion at the home network. Since it's a one-time negotiation/communication between the home network and the hosting network as part of a service level agreement and the actual load in the home network may vary over time, the constant/fixed number of deregistration of UEs from the hosting network to the home network may lead to congestion/overload. Also, if the home network is in a position to handle more of UEs that it was communicated/negotiated earlier, then UEs in the hosting network may have to wait unnecessarily. +- Category 1-c based solutions are based on the principle of negotiating/communicating the home network AMF capacity with the hosting network continuously to deregister the number of UEs simultaneously per unit time from the hosting network to the home network without causing overload/congestion at the home network. Since the home network and the hosting network are negotiating/communicating continuously using subscribe-notify communication service, the load variation in the home network due to less or high number of attempts from the home network and other hosting networks UEs is notified to the hosting network as a new maximum threshold value (i.e. the new allowed maximum number of returning UEs per unit time) in a new notification. Hence, the hosting network can deregister the number of UEs adaptively based on the current capacity of the home network AMF without causing overload/congestion at the home network. Also, it minimizes the overall waiting time for UEs before re-registering to their network and utilizes the available resources in the home network AMF efficiently. + +In the runtime-based solutions (Category 2), there are three subcategories based on the principles used to address the requirements mentioned in the KI #6, which are summarized as follows: + +- Category 2-a based solutions reuse the existing mechanisms without any additional enhancements. However, the existing mechanisms do not avoid an overload/congestion at the home network when a high number of UEs attempt to return from the hosting network to their home network in a short period of time. Moreover, the + +existing mechanisms would increase the overall waiting time of UEs as the existing mechanisms use the same pre-defined range for assigning random back-off timer value to all UEs irrespective of their size and service type they used. + +- Category 2-b based solutions are based on the principle of grouping UEs to create an Internal-Group Identifier specific to local hosting network(s) and/or local service(s) and then reusing the existing UE group-specific NAS level congestion control mechanism to manage UEs returning from a local hosting network to their home network. However, the existing mechanisms do not avoid overload and would increase the overall waiting time of users since the same pre-defined range is used for assigning random back-off timer value to all UEs irrespective of their size and service type they used. +- Category 2-c based solutions are based on the principle of assigning a local hosting network specific back-off timer value in order to reduce the overall waiting for UEs before re-register to their home network. + +A UE returning from a Hosting Network after using a Localized Service would normally not have higher priority than any other UEs, i.e. the prioritization among UEs would better follow existing mechanisms and therefore adding a separate indication that the UE is returning from the Hosting Network as an indication to the Home Network can be questioned. However, as the avoidance-based method potentially delays the UEs return to the Home Network also for the cases when the Home Network is not overloaded/congested, unless a frequent load check is introduced, it is better to allow the UE return as soon as the Localized Service ends or whenever the UE (e.g. user) decides to stop using the Localized Service and therefore leaves the Hosting Network before the end of the Localized Service. The end time of the Localized Service can be adapted on application layer by existing means i.e. without 3GPP impacts. + +--- + +## 8 Conclusions + +**Editor's note:** This clause will capture conclusions from the study. + +### 8.1 Key Issue #1: Enabling support for idle and connected mode mobility between SNPNS without new network selection + +Following the similar principles used in the Equivalent PLMNs, it is concluded that the following principles for the Equivalent SNPNS are to be used as basis for normative work: + +- Since UE may have either a subscription that can be used to access source and target SNPNS or has the credentials from a Credentials Holder (CH) to access both source and target SNPNS, the lists of equivalent SNPNS are stored and used per SNPN subscription by the UE. +- UE and AMF support of equivalent SNPN list in NAS. +- NG-RAN and AMF support of equivalent SNPNS in NGAP. +- UE/NG-RAN/AMF take equivalent SNPN list into consideration, for supporting relevant functions, e.g.: + - idle/connected network selection. + - cell (re)selection. +- AMF to inform UE the registered SNPN ID change during mobility in Registration Accept message, when there is a change of registered SNPN. +- NGAP impact for supporting connected mode mobility between SNPNS. + +NOTE: It is up to RAN WG3 to decide how to extend NGAP for connected mode mobility. + +- Equivalent SNPNS, with different SNPN IDs, within an RA is not supported for SNPNS. + +### 8.2 Key Issue #2: Support of Non-3GPP access for SNPN + +The following conclusions are agreed for normative work: + +- Access to SNPN services via Untrusted non-3GPP access network includes support for Credential Holder, UE Onboarding and Emergency services. Specifically: + - When UE registers to SNPN with credentials owned by the SNPN, UE uses the same N3IWF selection procedure as specified for access to stand-alone non-public network services via PLMN in clause 6.3.6.2a of TS 23.501 [3]. + - UE initiates N3IWF selection for emergency services when the UE detects a user request for emergency session and determines that Untrusted non-3GPP access is to be used for the emergency access. The UE with SNPN subscription performs the following: + - If the UE determines that it is located in the same country as the subscribed SNPN, the UE uses the configured N3IWF FQDN for N3IWF selection. + - Otherwise, the UE follows the N3IWF selection procedure for Emergency services for UE not equipped with UICC, as defined in clause 6.3.6.4.2 of TS 23.501 [3]. + - When the UE is registering to SNPN over Untrusted N3GPP access for UE Onboarding, UE may select a N3IWF in the SNPN which supports UE Onboarding by using the pre-configured N3IWF FQDN used for onboarding. + +NOTE 1: The GIN is not used to construct a N3IWF FQDN if a UE is registering to SNPN over Untrusted N3GPP access. + +NOTE 2: The format of FQDN will be specified by CT WG4. + +- If the PVS is reachable from the local Untrusted non-3GPP access network (e.g. via the Internet) using the local IP connectivity, UE may connect directly (i.e. without connected to a N3WIF) with a PVS to obtain the SNPN credentials. +- Access to SNPN services via Trusted non-3GPP access network is to be specified according to the principles described in Solution #3, including support for credential Holder, Emergency services and UE onboarding. Specifically: + - ANQP is to be extended to support advertising of: + - SNPN IDs and GINs corresponding to SNPNs with which 5G connectivity is supported and related parameters as described in clause 6.3.3.1. + - Support for Emergency services. + - Onboarding enabled indication. + +NOTE 3: The work on additional parameters in ANQP is to be kept internal to 3GPP. + +NOTE 4: If the UE tries to register with an SNPN via TNAN X in the case of SNPN ID with self-assigned NID, and the UE is rejected by the AMF with a cause code that temporarily prevents the UE from registering with this SNPN, the UE does temporarily not attempt to register with the same SNPN, even if the same SNPN ID is advertised via another TNAN Y. + +- When accessing SNPN services via Trusted or Untrusted non-3GPP access the UE needs to be able to construct a prioritized list of WLAN access networks by using enhanced WLAN Selection Policy (WLANS) rules from ANDSP (currently supported only for PLMN in TS 23.402 [9]) or based on local configuration. +- N3IWF and TNGF needs to be able to include the "selected NID" in the [NGAP] INITIAL UE MESSAGE, which is up to RAN WG3 to define. +- Access to SNPN services via wireline access network and use of Credential Holder is to be supported by defining a new GCI including a "NID". +- The NSWO procedure is to be extended to support UE authentication using SNPN credentials (applies both to SIM-based and non-SIM based credentials). It is expected that the impact is limited to the use of a SUCI format whose "realm" part enables routing of SWa requests from the WLAN AN to the NSWO in the SNPN's 5GC, which is already supported. + +- To support N5CW device access to SNPN services, the TWAP needs to be able to advertise a list of SNPNs with which "5G connectivity-without-NAS" is supported, equivalent to the PLMN list-4 defined in clause 6.3.12a.2 of TS 23.501 [3]. + +NOTE 3: Additional conclusions for wireline access related to UE behind 5G-RG depends on the progress on the FS\_5WWC\_Ph2 study. + +NOTE 4: Functionality related to the use of the same credentials for access to SNPN with NG-RAN and to WLAN Access Network as proposed in Solution #16 can be considered during normative work based on any feedback from SA WG3. + +## 8.3 Key Issue #3: Enabling NPN as hosting network for providing access to localized services + +When describing the feature description in the normative phase, the definitions for localized service and localized service provider in clause 3 can be used as basis. + +There are different types of interactions between hosting network operator and localized service provider. Depending on the types of the interactions, following principles are proposed to address this key issue: + +### **For interactions between localized service provider and hosting network operator:** + +The service agreements between hosting network operator and localized service provider can include: + +- list of the identification of the localized services; +- validity restriction for each localized service, e.g. the validity of time or location; +- service parameters for each localized service, e.g. DNN, S-NSSAI and QoS requirements; +- service authorization methods, e.g. NSSAA or PDU Session SAA. + +Depending on the types of the interactions, following principles are proposed: + +- If the purpose is to configure the hosting network (e.g. creation of network slice/DNN for carrying localized service traffic), existing OAM mechanisms can be re-used as per TS 28.557 [20] clause 6.3.1, that provides a solution for NPN provisioning by a network slice of a PLMN and for exposure of management capability of PNI-NPN (clause 6.3.2). The attributes to support this management is further documented in TS 28.541 [21]. +- For other types of Session Management level interactions (e.g. monitoring hosting network performance, enabling special QoS for UE in hosting network for localized service, etc.), the following options can be considered: + - Covered by the SLA. + - Reuse the existing network exposure procedures (see TS 23.502 [4] clause 4.15). + - Enable NEF/PCF in the hosting network (via AF of the localized service provider) to receive and forward the validity conditions and QoS requirements of the localized services to the AMF/SMF by reusing the existing PCF initiated AMF/SM policy association procedure. + +Conclusions in Key issue #4 and Key issue #5 are sufficient to cover all necessary interactions between home network and hosting network. + +It is suggested to re-use existing mechanisms that does not require SA2 normative work. + +## 8.4 Key Issue #4: Enabling UE to discover, select and access NPN as hosting network and receive localized services + +### 8.4.1 General + +The conclusion for KI #4 is made for each component that is evaluated in clause 7.4. + +When UE accesses the Hosting network using the subscription/credentials of its Home network, only two cases are considered: + +- If Home network is PLMN, the Hosting network can be PNI-NPN or SNPN. +- If Home network is SNPN, the Hosting network can be only SNPN + +If the UE accesses the Hosting network using the other credentials rather than the subscription/credentials from the UE Home network, the determination of the subscription used to access the Hosting network is by implementation specific prior to automatic network selection as described in NOTE 1 of clause 5.30.2.4.2 of TS 23.501 [3]. + +## 8.4.2 Conclusion for the content of the information for accessing localized services + +The following interim conclusions are reached. + +For manual selection existing SIB information e.g. HRNN and/or application layer information can be used without any normative impact. + +For automatic selection the following is concluded: + +- a. In the case of SNPN as hosting network, for automatic SNPN selection, the existing Credentials Holder controlled prioritized list of preferred SNPNs (and GINs) is extended with, for each entry in the list, time and location validity information. An entry may include time validity only, location validity only, or both. The location validity information can be in the form of geolocation and/or TAI of serving PLMN/SNPN. + +NOTE: The location validity information is used to aid the UE where to search for the SNPNs in the CH lists and is not used for any enforcement. + +- b. for automated cell re-selection: + +- In the case of PNI-NPN with CAG, the allowed CAG list can include time validity information as already agreed in TR 23.700-05 [23] (CR3813 to TS 23.501 [3] for VMR). +- In the case of PNI-NPN using S-NSSAI, the SOR can include S-NSSAI information as already concluded by TR 23.700-41 [24] (KI#2), or S-NSSAI validity information including time and location as concluded by KI#3 can be used. + +## 8.4.3 Conclusion for from where and how UE obtains the information for accessing localized service + +The information for localized service can be obtained by UE at the application layer from the home network or the localized service provider via means that are outside of 3GPP scope. + +The hosting network selection information is provisioned as below: + +1. The information for hosting network, selection and access can be preconfigured in the UE or dynamically provisioned by home network (via the VPLMN when roaming) using existing mechanisms. +2. In the case of SNPN as hosting network, the dynamic provisioning of prioritized list of hosting network information can be done via SoR: + +NOTE: How SOR-AF and/or UDM acquires hosting network information is outside the scope for 3GPP. + +- i. The home network UDM may determine to update UE with prioritized list of hosting network information using SoR procedure. Following triggers may apply: + - UE location as part of Registration procedure. + - UE subscription data change, e.g. via external parameter provisioning. +3. In the case of PNI-NPN as hosting network, the dynamic provisioning of allowed CAG ID list reuses existing procedure in clause 5.30.3.3 of TS 23.501 [3]. + +## 8.4.4 Conclusion for how the localized service information is used by UE + +The following principles based on the evaluation in clause 7.4.4 are recommended for the normative work: + +1. If UE uses home network credential to access a hosting network: + - a. When the end user intends to access localized service and the validity conditions of localized service are met, the UE initiates hosting network selection using the hosting network selection information. + - i. For SNPN as hosting network, the UE can switch between PLMN selection and hosting network selection following Rel-17 specification for SNPN selection with the following difference: + - If the UE is configured with Credential Holder controlled prioritized lists of preferred SNPNs and GINs and the lists contain entries with a validity condition and the validity condition is met for at least one of those entries, then the UE may select the related SNPNs even if the subscribed SNPN (if any) is available (i.e. the hosting network may have a higher priority than the subscribed SNPN). How the UE switches among the network selections is up to UE implementation. + - ii. For PNI-NPN as hosting network associated with CAG ID, the UE only considers an entry in the Allowed CAG list valid if and while all conditions (if there is any) for that entry are met. + +NOTE 1: Whether a new network selection mode is required for UE to initiate hosting network selection for an SNPN (i.e. to select an SNPN as hosting network) is to be determined by CT WG1. + +NOTE 2: Details regarding priority list for hosting network selection for an SNPN (i.e. to select an SNPN as hosting network), including if a new selection mode is required, is up to CT WG1 to decide. + +- b. Automatic hosting network selection is controlled by the home network, via SoR procedure with SoR information including certain authorized criteria e.g. time. Based on the SoR information, the UE performs automatic hosting network selection. + - i. For manual hosting network selection, the UE presents available localized service information it has received to the end user. +2. If the UE needs to obtain a new set of credentials/subscription to access the hosting network: + - a. It is up to UE implementation to decide how to switch to the new subscription profile for accessing hosting network. +3. The UE determines SNPN access mode is activated/de-activated using implementation specific means as specified in existing Release 17, or using received localized service/hosting network assistance information as input. + +## 8.4.5 Conclusion for what credentials are used to access hosting network and how to obtain them + +The following principles based on the evaluation in clause 7.4.5 are recommended for the normative work in the case of SNPN as hosting network: + +1. The UE checks whether it is possible to re-use the home network credentials to access the hosting network by performing the following: + - a. If the UE uses CH/User controlled priority lists part of the Home network subscription profile or if the UE uses hosting network related information from the Home network (part of the localized service information) which indicates support of CH credentials, the UE determines that home network credential can be used to register with the selected Hosting network. +2. If the UE has Default credentials and the UE determines that new credentials for accessing hosting network are needed, the UE uses the Default credentials for the onboarding mechanism with the ON-SNPN acting as hosting network as per Rel-17 with the following enhancements: + - a. In case that the UE is preconfigured with PVS address information and the UE receives PVS address information from the SMF during the PDU Session Establishment Accept message, the UE may determine based on local configuration whether to apply or ignore the PVS address information provided by the SMF. + +NOTE: Backwards compatibility with Rel-17 UE behaviour needs to be considered during normative phase. + +The following principles based on the evaluation in clause 7.4.5 are recommended for the normative work in the case of PNI-NPN as hosting network: + +3. Only UEs equipped with a USIM configured with PLMN credentials can access a hosting network which is a PNI-NPN. When the UE requests to access the hosting network, the home PLMN credential(s) are used during authentication procedure. + +## 8.4.6 Conclusion for how localized service is accessed in hosting network per agreed conditions + +The following principles based on the evaluation in clause 7.4.6 are recommended for the normative work: + +1. Validity conditions provided to the UE as part of the localized service information can be used to restrict the UE's access of the hosting network. +2. Existing methods, such as network slicing, forbidden area restriction, service area restriction, CAG, LADN, URSP rules can also be utilized to restrict UE's access, i.e. no need for additional normative work for access control in hosting network. +3. In order to restrict access to a hosting network to a specific area, a hosting network operator may deploy and broadcast multiple hosting network IDs, i.e. SNPN IDs for SNPN case and CAG IDs in the case of PNI-NPN, in different areas depending on localized service area validity. Each localized service is mapped to a specific hosting network ID. Multiple localized service areas can be mapped to the same hosting network ID if their allowed service areas are the same. Validity conditions are also used by hosting network to restrict access. + +## 8.5 Key Issue #5: Enabling access to localized services via a specific hosting network + +The following conclusions are agreed for normative work: + +- The existing SoR procedure is enhanced as follows: + - The SoR contains the Credentials Holder controlled prioritized list of preferred SNPNs (and GINs) which is extended with, for each entry in the list, validity condition information, for the scenario where the UE reuses Credential Holder credentials to access the hosting network. The list is determined by the home network and may be associated with validity conditions, including time and location conditions. +- When the hosting network is an SNPN which provides localized services and the home network is an HPLMN, the architecture specified in clause 5.30.2.7 of TS 23.501 [3] is reused for the UE to access both home network services (using the SNPN as underlay network) and localized services (via the SNPN). +- If the hosting network is a PNI-NPN, existing mechanisms (e.g. roaming architecture, network slicing, etc.) are reused for the UE to access home network services. +- The existing URSP rules or LADN feature can be re-used for a UE to access the Localized services after the UE has registered to a Hosting network. URSP rules are pre-configured in the UE, provisioned by the PCF of the home network or provisioned by the PCF of the hosting network according to existing principles. + +## 8.6 Key Issue #6: Support for returning to home network + +The following principles from the evaluation are recommended to be considered during the normative work: + +- The home/serving network can re-use existing mechanisms for Control Plane Load Control, Congestion and Overload Control described in clause 5.19 of TS 23.501 [3] when load level reaches a certain threshold and overload control mechanism are triggered. +- Additional mechanisms can be implemented to ensure spreading of return of the UEs to home network without any normative impacts to 3GPP specifications. + +NOTE: Means to describe how to spread returning UEs can be captured as informative description, during normative specification work. + +## Annex A: Change history + +| Change history | | | | | | | | +|----------------|----------------|------------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149e | S2-2200487 | - | - | - | Proposed skeleton agreed at SA2#149e | 0.0.0 | +| 2022-02 | SA2#149e | - | - | - | - | S2-2200488 (skeleton), S2-2200488, S2-2200489, S2-2201749, S2-2201750, S2-2201860, S2-2201752, S2-2201753, S2-2201850
Editorial changes by rapporteur. | 0.1.0 | +| 2022-04 | SA2#150e | - | - | - | - | S2-2203442, S2-2203443, S2-2203444, S2-2203445, S2-2203446, S2-2203447, S2-2203448, S2-2203449, S2-2203450, S2-2203451, S2-2203452, S2-2203453, S2-2202258, S2-2203454, S2-2203455, S2-2202457, S2-2203456, S2-2203457, S2-2203458, S2-2203459, S2-2202526, S2-2203460, S2-2203461, S2-2202931 | 0.2.0 | +| 2022-05 | SA2#151e | - | - | - | - | S2-2205129, S2-2205130, S2-2205131, S2-2205132, S2-2205133, S2-2205134, S2-2205135, S2-2205136, S2-2203728, S2-2205137, S2-2203729, S2-2205138, S2-2205139, S2-2205140, S2-2205141, S2-2205142, S2-2205143, S2-2205144, S2-2205145, S2-2205146, S2-2205147, S2-2205148, S2-2205149, S2-2205150, S2-2205151, S2-2205152, S2-2205153, S2-2205154, S2-2205155, S2-2203733, S2-2203966, S2-2205156, S2-2205157, S2-2205158, S2-2204521, S2-2204532 | 0.3.0 | +| 2022-05 | SP#96 | SP-220421 | - | - | - | MCC Update for presentation to TSG SA#96 for Information | 1.0.0 | +| 2022-08 | SA2#152e | - | - | - | - | S2-2207706, S2-2207707, S2-2207708, S2-2206281, S2-2207709, S2-2206838, S2-2207710, S2-2207711, S2-2206601, S2-2205801, S2-2205802, S2-2206698, S2-2207712, S2-2205803, S2-2207713, S2-2207714, S2-2207715, S2-2207716, S2-2206835, S2-2207717, S2-2206163, S2-2207718, S2-2207719, S2-2206555, S2-2207720, S2-2207721, S2-2207722
Editorial changes by rapporteur. | 1.1.0 | +| 2022-09 | SA2#152e | - | - | - | - | S2-2206693 | 1.2.0 | +| 2022-10 | SA2#153e | - | - | - | - | S2-2208770, S2-2208438, S2-2209861, S2-2209862, S2-2209863, S2-2209864, S2-2209865, S2-2208737, S2-2209168, S2-2209866, S2-2209867, S2-2209936, S2-2209868, S2-2209976 | 1.3.0 | +| 2022-11 | SA2#154 | - | - | - | - | S2-2210809, S2-2211096, S2-2211432, S2-2211433. | 1.4.0 | +| 2023-01 | SA2#154A
HE | - | - | - | - | S2-2301434, S2-2301435, S2-2301436 | 1.5.0 | +| 2023-03 | SP#99 | SP-230082 | - | - | - | MCC Update for presentation to TSG SA#99 for approval | 2.0.0 | +| 2023-03 | SP#99 | - | - | - | - | MCC Update for publication after TSG SA approval | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-25/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/raw/rel-18/23_series/23700-25/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b48e2ae886dfc8add39797a6ec1a53bbc4952e5 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:791253b0c5a34996c5f4a5d06438d7d8db5c53d0d7e98dfcceee2e5cc44335b1 +size 137162 diff --git a/raw/rel-18/23_series/23700-25/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/raw/rel-18/23_series/23700-25/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a01207cf27c67fb8e4510de9a687b901f150174 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f01468dc1d2058832862b8e30848ed94cc23227dbcd65fd13064a14ddd239a0 +size 82385 diff --git a/raw/rel-18/23_series/23700-25/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-25/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab1ec1f3a0ed1e06732d05a00de2936d811b935d --- /dev/null +++ b/raw/rel-18/23_series/23700-25/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6086a42c9681e87d8bef7bfa4a7af45889282ce649291e757a1ed68a25114abf +size 5716 diff --git a/raw/rel-18/23_series/23700-25/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/raw/rel-18/23_series/23700-25/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..caa79314a8042e3426d9a16fe5db5f73d9d1da88 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cec70e5ac93a0f7653918a5b7c32a9d9cf92043bc14daba1a8274c2bbadfc172 +size 90667 diff --git a/raw/rel-18/23_series/23700-25/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg b/raw/rel-18/23_series/23700-25/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0620b10f5139b93f6abc3b68c2aa4ad2f3f6156 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8895a07147bfa8056815f79cdb1a1e40d9518c6067258335246b6c055df08db +size 77396 diff --git a/raw/rel-18/23_series/23700-25/7e6522034f6ba31b1243b189d2e65ca2_img.jpg b/raw/rel-18/23_series/23700-25/7e6522034f6ba31b1243b189d2e65ca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53f36786049fe2c8db2695ce3b57d7114c39b80e --- /dev/null +++ b/raw/rel-18/23_series/23700-25/7e6522034f6ba31b1243b189d2e65ca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:919b8de542795678fdde270131cc9d2eedcfcf271706745f8503080ce1dc952d +size 55499 diff --git a/raw/rel-18/23_series/23700-25/90ddb84c323b956e2d50a54d3f870566_img.jpg b/raw/rel-18/23_series/23700-25/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b30bc5864d86b799981237a5ff36db099e6c126 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8c3696ebe7581a4f31b2e5de21c66b79c4533a57292db9470c989da3cc0ca0c +size 127612 diff --git a/raw/rel-18/23_series/23700-25/96c8d8b0159c47a7478ada46d781060b_img.jpg b/raw/rel-18/23_series/23700-25/96c8d8b0159c47a7478ada46d781060b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6153aa533756e7fa7aa78c037bc7825fd7ef96ef --- /dev/null +++ b/raw/rel-18/23_series/23700-25/96c8d8b0159c47a7478ada46d781060b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b981fed5b3ac1f880f83c00243d8a51ace4b43d00f2715322ea4b121ad02f305 +size 72638 diff --git a/raw/rel-18/23_series/23700-25/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/raw/rel-18/23_series/23700-25/9f51a76cae7309a296cbc6997941eb3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cd62a73c0bbacc28a6007c8bb0f90c4c421988e --- /dev/null +++ b/raw/rel-18/23_series/23700-25/9f51a76cae7309a296cbc6997941eb3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9f459ce14c2479d412ed782be002e897dd5bf481f60e82807d97a65fa034199 +size 25626 diff --git a/raw/rel-18/23_series/23700-25/b5335262987c819d7f71ce40f99cb71b_img.jpg b/raw/rel-18/23_series/23700-25/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4a8bbc536dd116c26c99ad2081a3ddcc0dec2b4 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5010c15bf8cbef83cb227453dcd8cc72d20c5acce4f6c2eb3510b934af3ddbf +size 74126 diff --git a/raw/rel-18/23_series/23700-25/b8efedb73292a798b3f2050f9335cae6_img.jpg b/raw/rel-18/23_series/23700-25/b8efedb73292a798b3f2050f9335cae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98dae57a7d74524c6d0747cab3a9b8a446f0e603 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/b8efedb73292a798b3f2050f9335cae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78b0470c3e420da5a161c413628fc9ef92a32e2c949b597d4102fb85a5131b73 +size 82756 diff --git a/raw/rel-18/23_series/23700-25/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/raw/rel-18/23_series/23700-25/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c3005163057927a7b29d3d99fe9afac9ea4ce35 --- /dev/null +++ b/raw/rel-18/23_series/23700-25/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9df40694dd91b777c73c6376b95a4d17f0af407d6e2473bee3303a85eb1900a2 +size 90664 diff --git a/raw/rel-18/23_series/23700-36/raw.md b/raw/rel-18/23_series/23700-36/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c3b9823953e046e6f45649fa94bbfd6d557c9edf --- /dev/null +++ b/raw/rel-18/23_series/23700-36/raw.md @@ -0,0 +1,1975 @@ + + +# 3GPP TR 23.700-36 V18.1.0 (2022-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Application Data Analytics Enablement Service; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 Key issues ..... | 8 | +| 4.1 Key issue #1: Support for application performance analytics..... | 8 | +| 4.2 Key issue #2: Support for edge analytics enablement..... | 8 | +| 4.3 Key issue #3: Support for data collection for application layer analytics..... | 9 | +| 4.4 Key issue #4: Key Issue on interactions with SEAL services..... | 9 | +| 4.5 Key issue #5: Support for slice-related application data analytics..... | 10 | +| 4.6 Key issue #6: Support for slice configuration recommendation enablement..... | 10 | +| 4.7 Key issue #7: Support for location accuracy analytics ..... | 10 | +| 4.8 Key issue #8: Support for service API capability analytics ..... | 11 | +| 5 Architecture aspects ..... | 12 | +| 5.1 Architecture related requirements ..... | 12 | +| 5.1.1 Description ..... | 12 | +| 5.1.2 General Requirements ..... | 12 | +| 5.1.3 ADAE internal architecture requirements ..... | 12 | +| 5.2 ADAE capability related requirements ..... | 12 | +| 5.2.1 Application performance analytics requirements..... | 12 | +| 5.2.1.1 Description..... | 12 | +| 5.2.1.2 Requirements ..... | 12 | +| 5.2.2 Edge load analytics requirements..... | 12 | +| 5.2.2.1 Description..... | 12 | +| 5.2.2.2 Requirements ..... | 13 | +| 5.2.3 Slice related application data analytics requirements..... | 13 | +| 5.2.3.1 Description..... | 13 | +| 5.2.3.2 Requirements ..... | 13 | +| 5.3 Functional Architecture..... | 13 | +| 5.3.1 General ..... | 13 | +| 5.3.2 On-network Functional Architecture..... | 13 | +| 5.3.3 Off-network Functional Architecture ..... | 15 | +| 5.3.4 ADAE internal architecture based on 3GPP data analytics framework ..... | 15 | +| 6 Solutions..... | 17 | +| 6.1 Mapping of solutions to key issues ..... | 17 | +| 6.2 Solution #1: Support for application performance analytics..... | 17 | +| 6.2.1 Solution description..... | 17 | +| 6.2.1.1 Procedure on VAL server performance analytics..... | 17 | +| 6.2.1.2 Procedure on VAL UE / session performance analytics..... | 19 | +| 6.2.2 Corresponding Analytics API..... | 21 | +| 6.2.3 Solution evaluation ..... | 22 | +| 6.3 Solution #2: Data Analytics Enablement ..... | 22 | +| 6.3.1 Solution description..... | 22 | +| 6.3.1.1 General ..... | 22 | +| 6.3.1.2 Procedures..... | 23 | +| 6.3.1.2.1 Generic server-side initiated data analytics..... | 23 | +| 6.3.1.2.2 Generic client-side initiated data analytics..... | 25 | +| 6.3.1.2.3 Generic data collection procedure..... | 27 | +| 6.3.1.3 Information Flows..... | 29 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------------|-----------| +| 6.3.2 | Evaluation ..... | 30 | +| 6.4 | Solution #3: Support for edge load analytics ..... | 31 | +| 6.4.1 | Solution description ..... | 31 | +| 6.4.2 | Corresponding Analytics API ..... | 33 | +| 6.4.3 | Solution evaluation ..... | 34 | +| 6.5 | Solution #4: Support for performance analytics for UE-to-UE sessions ..... | 34 | +| 6.5.1 | Solution description ..... | 34 | +| 6.5.2 | Corresponding Analytics API ..... | 36 | +| 6.5.3 | Solution evaluation ..... | 36 | +| 6.6 | Solution #5: Service experience to support application performance analytics ..... | 36 | +| 6.6.1 | Solution description ..... | 36 | +| 6.6.1.1 | Pull service experience information ..... | 37 | +| 6.6.1.2 | Push service experience information ..... | 38 | +| 6.6.1.3 | Service experience information based on triggers ..... | 39 | +| 6.6.2 | Solution evaluation ..... | 40 | +| 6.7 | Solution #6: Support for slice related application data analytics ..... | 40 | +| 6.7.1 | Solution description ..... | 40 | +| 6.7.2 | Corresponding Analytics API ..... | 42 | +| 6.7.3 | Solution evaluation ..... | 42 | +| 6.8 | Solution #7: Slice configuration recommendation ..... | 42 | +| 6.8.1 | Solution description ..... | 42 | +| 6.8.2 | Corresponding Analytics API ..... | 44 | +| 6.8.3 | Solution evaluation ..... | 44 | +| 6.9 | Solution #8: support for location accuracy analytics ..... | 44 | +| 6.9.1 | Solution description ..... | 44 | +| 6.9.2 | Corresponding Analytics API ..... | 46 | +| 6.9.3 | Solution evaluation ..... | 46 | +| 6.10 | Solution #9: support for service API analytics ..... | 46 | +| 6.10.1 | Solution description ..... | 46 | +| 6.10.2 | Corresponding Analytics API ..... | 49 | +| 6.10.3 | Solution evaluation ..... | 49 | +| 7 | Deployment scenarios ..... | 49 | +| 7.1 | General ..... | 49 | +| 7.2 | Deployment model #1: Cloud-deployed ADAES ..... | 49 | +| 7.3 | Deployment model #2 Edge-deployed ADAES ..... | 50 | +| 7.4 | Deployment model #3: Hierarchical ADAES deployment ..... | 51 | +| 8 | Overall evaluation ..... | 51 | +| 8.1 | General ..... | 51 | +| 8.2 | Solution evaluations ..... | 51 | +| 8.2.1 | General ..... | 51 | +| 8.2.2 | ADAE analytics services ..... | 53 | +| 9 | Conclusions ..... | 54 | +| 9.1 | General conclusions ..... | 54 | +| 9.2 | General conclusions for normative work ..... | 54 | +| 9.2 | Conclusions of solutions ..... | 55 | +| Annex A (informative): | Change history ..... | 56 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +Data analytics is a useful tool for the operator to help optimizing the service offering by predicting events related to the network or slice or UE conditions. 3GPP introduced data analytics function (NWDAF) [2] to support network data analytics services in 5G Core network, and management data analytics service (MDAS) [3] to provide data analytics at the OAM. + +Considering vertical-specific applications and edge applications as the major consumers of 3GPP-provided data analytics services, the application enablement layer can play role on the exposure of data analytics services from different 3GPP domains to the vertical/ASP in a unified manner; and on defining, at an overarching layer, value-add application data analytics services which cover stats/predictions for the end-to-end application service. + +This technical report identifies the key issues and corresponding application architecture and related solutions with recommendations for the normative work. + +# --- 1 Scope + +The present document is a technical report which identifies the application enabling layer platform architecture, capabilities, and services to support data analytics enablement at the application layer. + +The aspects of the study include the investigation of application data analytics services to optimize the application service operation, edge/cloud analytics enablement, data collection aspects per identified application data analytics service, coordination of data collection from multiple sources and unified exposure of data analytics to the vertical/ASP. This study will also identify potential enhancements to existing enablement layer entities (SEAL, eEDGEAPP, vertical specific enablers) to consume application data analytics enablement services. + +The study takes into consideration the work done for data analytics in 3GPP TS 23.288 [2] and 3GPP TS 28.104 [3] and other related work outside 3GPP. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [3] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics". +- [4] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [5] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [6] 3GPP TS 23.558: "Architecture for enabling Edge Applications". +- [7] 3GPP TS 26.531: "Data Collection and Reporting; General Description and Architecture" +- [8] 3GPP TR 23.700-96: "Study on 5G-enabled fused location service capability exposure" +- [9] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs" + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +            + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|---------------------------------------------------------------| +| ADAE | Application Data Analytics Enabler | +| A-ADRF | Application layer - Analytical Data Repository Function | +| A-DCCF | Application layer - Data Collection and Coordination Function | +| ADRF | Analytical Data Repository Function | +| ASP | Application Service Provider | +| DCCF | Data Collection and Coordination Function | +| MEP | Multi-access Edge Platform | +| MDAS | Management Domain Analytics Service | +| NWDAF | Network Data Analytics Function | +| OAM | Operation, Administration and Maintenance | +| RNIS | Radio Network Information Service | +| SEAL | Service Enabler Architecture Layer | +| SEALDD | Service Enabler Architecture Layer – Data Delivery | +| VAL | Vertical Application Layer | + +# --- 4 Key issues + +## 4.1 Key issue #1: Support for application performance analytics + +Data analytics related to the application end-to-end QoS and in particular statistics and predictions on the application server or application session performance and load can be useful for the application specific layer, so as to proactively identify potential adaptations of the application service and to trigger adaptations at the communication layer. One example is the utilization of analytics by the application specific layer e.g. for selecting the least loaded EAS for an application session, or for selecting the optimal PLMN for communicating the application service in a given area. + +This key issue will study: + +- whether and how the application data analytics enablement service provides application QoS related analytics for the application session /service? +- whether and how the application data analytics enablement service provides application QoS related analytics tailored for different communication means (e.g. different PLMNs, RATs, slices)? +- what data needs to be collected from 3GPP system and application specific layer for performing application QoS related analytics? +- how to enable the exposure of application QoS related analytics to the vertical / ASP in a unified manner? + +## 4.2 Key issue #2: Support for edge analytics enablement + +Edge deployments are vitally important for applications that require performance levels that cannot be met by existing cloud deployments. Edge data analytics may relate to stats/predictions on computational resources and expected/predicted load of the platform which hosts the edge applications and may be necessary to be exposed as a service to EAS (which can be either edge native applications or edge enhanced applications at a centralized cloud). + +Particularly, for edge native applications which need to be light designed and high portable, the use of edge analytics at the edge platform can help improving the application service operation. + +The support for edge analytics at the enablement layer (related to the edge performance, failure, service availability), would be useful for the edge applications to allow for dynamically deciding to scale-in, scale-out, migrate from the edge to the cloud in heavy load situations, or migrate from the cloud to the edge to improve the quality of experience for the end user. Also, the need for edge application relocation between edge platforms could be supported by using analytics which can be leveraged by the EDGEAPP layer and could be exposed as a service to the application developer for supporting the edge service operation optimization. + +Hence, in this key issue the following points shall be studied: + +- Whether and what edge data are needed to be collected by the application data analytics enablement server to allow for edge analytics enablement (related to the edge performance, failure, service availability)? +- Whether and how the application data analytics enablement server (deployed in an edge or centralized data network) can be utilized by the corresponding Edge Enabler layer architecture (as specified in 3GPP TS 23.558 [6]) to optimize edge services? +- Whether and how the analytics enablement layer needs to align with the EDGEAPP layer for allowing the edge services to utilize edge analytics enablement service to optimize their operation (e.g. triggering pro-active ACR based on edge analytics)? +- Whether and how the application data analytics enablement server needs to align with ETSI MEC system to utilize MEC services? + +## 4.3 Key issue #3: Support for data collection for application layer analytics + +For deriving application layer analytics, the data collection may be provided by different sources (e.g. vertical-specific server, application of the UE, EAS, 3rd party server, SEAL/SEALDD) and it needs to be identified how these data can be collected to allow for stats/predictions by the analytics enablement layer. + +The application data analytics enablement layer needs to be capable of receiving data from different data producers and prepare the data to be used for deriving analytics. Such data can be measurements or analytics from the 5GS (5GC, OAM), the applications of the VAL UEs, other application enablers etc. + +For example, for application QoS related analytics, such data can be potentially derived by the OAM, monitoring of network QoS by 5GC, subscribing and receiving QoS and network analytics from NWDAF, performance data from the application server, QoS data from enabler layer client-server sessions, etc. The consumer of the ADAE service may not be aware of the data that need to be collected from different sources, however the ADAE needs to be capable of selecting the optimal sources to collect data, subscribe to different data producers and also retrieve supplementary data samples based on the data producers' availability and load. + +Hence, this key issue will discuss the following open issues: + +- How to enable the collection and preparation of data at the application data analytics enablement service for data analytics derivation, when the data to be collected target the same performance metrics and are originated from different sources (UE, networking layer, application specific layer, non-3gpp domains)? +- Whether and how the application data analytics enablement layer needs to collect data from multiple sources, at the DN side or locally at the VAL UE side? +- Whether and how to leverage the UE data collection support provided by the SA4 EVEX study? + +## 4.4 Key issue #4: Key Issue on interactions with SEAL services + +SEAL is the service enabler architecture layer common to all vertical applications over 3GPP systems. It provides the functions like location management, group management, configuration management, identity management, key management, network resource management and network slice capability management as defined in 3GPP TS 23.434 [5]. + +This key issue will study: + +- the applicability of the usage of SEAL services for application data analytics enablement services considering different deployment and business models +- whether any enhancements are required at the SEAL services for exposing data to the application data analytics enablement service? +- whether and how application data analytics at the application data analytics enablement service can be used to optimize SEAL service operation? + +NOTE: This KI does not preclude the case where ADAE service is a SEAL service. + +## 4.5 Key issue #5: Support for slice-related application data analytics + +Data analytics related to slicing are provided by the 5GS, from NWDAF (e.g. slice load analytics) and MDAS (e.g. NSI/NSSI performance analytics). The slice capability enablement layer (based on NSCALE) discusses enhancements to NSCE SEAL service (as specified in TS 23.434 [5]). According to Solution #5 of TR 23.700-99, the NSCE server is expected to consume 5GS services related to analytics (from MDAS, NWDAF) and to re-expose them to the VAL server (slice customer). + +If further analytics is required on top of the consumed analytics services (MDAS/NWDAF), the ADAES can be utilized by NSCE service to perform further analytics related to applications for certain slice / NSI. Such analytics service is not overlapping with NWDAF/MDAS services since it will provide at application layer data analytics (per session or VAL server) which are bound to a given slice or NSI (e.g. per VAL session performance statistics when using slice #1). + +This key issue will investigate: + +- what is the possible interaction between NSCE service and ADAES, for providing application layer analytics bound to a slice or an NSI? +- whether and what data need to be collected by NSCE layer for supporting per slice or NSI app layer analytics? + +## 4.6 Key issue #6: Support for slice configuration recommendation enablement + +Slice data analysis can analyze the slice usage pattern based on the collected network slice performance and analytics, and provide analysis-based slice management suggestions, such as the slice scale in and scale out, which can be exposed to VAL or provided to NSCE as a service. One example is, to support the application layer automatic network slice lifecycle management, in which the NSCE server is supposed to send out some management recommendation based on the collected network slice performance analytics from the 5GC, OAM and the application layer. The recommendation is usually an empirical value given by experienced network operations, ADAES can help to output the recommendation according to the analysis based on historical network slice status and network performance. + +Hence, in this key issue the following points shall be studied: + +- How ADAES supports the slice configuration recommendation based on the slice related information from NSCE. + +## 4.7 Key issue #7: Support for location accuracy analytics + +According to SA1 TS 22.261 (6.27) and TS 22.104, positioning services aim to support verticals and applications with positioning accuracies better than 10 meters, thus more accurate than the ones of TS 22.071 for LCS. High accuracy positioning is characterized by ambitious system requirements for positioning accuracy in many verticals and applications, including regulatory needs. For example, on the factory floor, it is important to locate assets and moving objects such as forklifts, or parts to be assembled. Similar needs exist in transportation and logistics, for example rail, road and use of UAVs. In some road user cases, UE's supporting V2X application(s) are also applicable to such needs. In cases such as guided vehicles (e.g. industry, UAVs) and positioning of objects involved in safety-related functions, + +availability needs to be very high. In SA1, different service levels are mapped to different positioning performance attributes including vertical and horizontal accuracies. Such accuracies (e.g. cm-level, dm-level, meter-level) may depend on the positioning methods which are used, the LCS producers, as well as the UE mobility and the environment. + +When the VAL consumer requests a positioning service, the accuracy is calculated at the entity which produces a location estimate and whether the accuracy can be maintained along an application session (for a given time/area) is challenging to answer at the time of the request/subscription. In this scenario, there needs to be a translation of the per UE location report accuracy to an expected /predictive location accuracy derivation for the application requiring positioning services. Such location accuracy analytics and in particular the sustainability of vertical and horizontal accuracy per VAL application (e.g. group of field devices in industrial use cases) based on per UE reported location accuracies could be needed to make sure that LMS will meet the VAL customer location reporting requirements for a given time/area of location request validity. Such information will help deciding from application side whether for a particular service (e.g. process automation, AR in factories) adaptation of the application behavior if the accuracy cannot be maintained e.g. programs the IIOT devices to maintain a bigger distance etc. + +This key issue aims to investigate: + +- whether and how ADAES needs to be enhanced to perform analytics on vertical and horizontal accuracy for positioning services requested by a VAL customer? +- what criteria need to be considered (e.g. environment, UE mobility, service type, positioning method, fusion) and what data are needed to be collected from 5GS (e.g. NWDAF, LMF) and VAL side for performing location accuracy analytics for the VAL application? +- what enhancements are needed in SEAL LMS to support location accuracy analytics/data per VAL application? + +## 4.8 Key issue #8: Support for service API capability analytics + +The service APIs (assuming also EAS provided APIs, enablement service APIs and OAM API), cannot be assumed uniformly available and offering the same service level across the entire network. For CIoT service, 3GPP SA2 has already defined a NEF monitoring service to allow the AF to monitor the API availability and service level (e.g. via invoking a Nnef\_APISupportCapability API as part of the Monitoring Event in TS 23.522) for the target API. However, this doesn't provide analytics on NEF/SCEF APIs and doesn't support all ranges of service APIs (produced or offered at the platform) and focuses on the CIoT scenarios. Furthermore, CAPIF supports the monitoring of service API invocations and can provide API monitoring via the *Availability of service APIs event notification* or *Service Discover Response* as specified in TS 23.222. + +Service API analytics (such as the statistics on the successful/failed API invocation or predicted API availability for a given deployment) can be a tool to be used by the API provider (ASP, ECSP, MNO) to help optimizing the API usage by enabling him to trigger API related actions like API mashups, API rate limitations/throttling events, or pro-actively detecting API termination point changes which may affect service performance. Such service could be also useful for the API invoker to allow for early notification on expected API unavailabilities. + +One example for such API analytics can be the statistics or prediction of NEF API or SEAL API invocation request failure probability, or the predicted number of API invocations for a particular EDN area and time of day or even the number of unauthorized API invocation requests. Such analytics can be matched to different APIs and API operations and can be used as a service for example to help the service API invoker to identify what is the best time and means to perform a request e.g. so as to avoid possible failure due to high number of invocations expected for this service API. + +This key issue will investigate: + +- whether and how the application data analytics enablement service needs to provide data analytics for service APIs? +- what data / API logs and from which entities need to be collected for performing service API analytics? +- what enhancements are needed in CAPIF (CCF, API management function) for supporting service API analytics? + +NOTE: Data/analytics related to MNO provided APIs are only possible if ADAES is deployed by the MNO. For ADAES outside MNO domain, this key issue covers only non-MNO provided APIs. + +# 5 Architecture aspects + +## 5.1 Architecture related requirements + +### 5.1.1 Description + +This subclause specifies the general and ADAE internal requirements for application data analytics enablement layer functional architecture. + +### 5.1.2 General Requirements + +[AR-5.1.2-a] The ADAE client and the ADAE server shall support one or more VAL applications. + +[AR-5.1.2-b] Supported ADAE capabilities may be offered as APIs to the VAL applications. + +[AR-5.1.2-c] The ADAE shall support interaction with 3GPP network system to consume network data analytics services. + +[AR-5.1.2-d] The ADAE client shall be capable to communicate with one or more ADAE servers of the same ADAE service provider. + +### 5.1.3 ADAE internal architecture requirements + +[AR-5.1.3-a] The ADAE layer shall be able to provide a data collection coordination functionality to enable the collection from diverse data sources (OAM, 5GC, UE) per application data analytics event type. + +[AR-5.1.3-b] The ADAE layer shall include a data analytics repository function to store application data analytics. + +[AR-5.1.3-c] The data collection coordination and repository capabilities may be offered as APIs to ADAE server. + +## 5.2 ADAE capability related requirements + +### 5.2.1 Application performance analytics requirements + +#### 5.2.1.1 Description + +This subclause specifies the requirements for application performance analytics capability. + +#### 5.2.1.2 Requirements + +[AR-5.2.1.2-a] The ADAE server shall be capable of providing data analytics for the VAL server performance. + +[AR-5.2.1.2-b] The ADAE server shall be capable of providing data analytics for the VAL application sessions (for both Uu-based and PC5-based sessions). + +[AR-5.2.1.2-c] The ADAE server shall be able to collect application performance measurements and analytics from one or more ADAE clients. + +### 5.2.2 Edge load analytics requirements + +#### 5.2.2.1 Description + +This subclause specifies the requirements for edge load analytics capability. + +#### 5.2.2.2 Requirements + +[AR-5.2.2.2-a] The ADAE server shall be capable of collecting edge data from one or more edge platforms + +[AR-5.2.2.2-b] The ADAE server shall enable the exposure of edge data analytics to the VAL applications + +### 5.2.3 Slice related application data analytics requirements + +#### 5.2.3.1 Description + +This subclause specifies the requirements for slice related application data analytics capability. + +#### 5.2.3.2 Requirements + +[AR-5.2.3.2-a] The ADAE server shall be capable of providing data analytics for the VAL server or VAL session performance for a requested slice or slice instance. + +[AR-5.2.3.2-b] The ADAE server shall be able to collect slice related measurements and analytics from one or more 3GPP network system domains (OAM, 5GC). + +## 5.3 Functional Architecture + +### 5.3.1 General + +This clause provides the overall functional architecture description, which includes the on-network and off-network functional models. + +### 5.3.2 On-network Functional Architecture + +For the on-network functional architecture, both service-based representation and reference point representation are provided. + +Figure 5.3.2-1 depicts the application data analytics enablement architecture in the non-roaming case, using the reference point representation showing how various entities interact with each other. + +![Figure 5.3.2-1: Architecture for application data analytics enablement – reference points representation. The diagram shows three main components: VAL UE, 3GPP network system, and VAL server(s). The VAL UE contains VAL client(s) and an Application data analytics enablement client. The VAL server(s) contains an Application data analytics enablement server. Reference points are labeled: VAL-UU between VAL client(s) and 3GPP network system; ADAE-C between VAL client(s) and Application data analytics enablement client; ADAE-UU between Application data analytics enablement client and 3GPP network system; ADAE-S between VAL server(s) and Application data analytics enablement server. The 3GPP network system includes N33, N6, and ADAE-OAM interfaces.](b978ce2c39dbbcd4c4e087eb265a830b_img.jpg) + +The diagram illustrates the functional architecture for application data analytics enablement using reference points. It is divided into three main vertical sections: VAL UE (left), 3GPP network system (middle), and VAL server(s) (right). A dashed horizontal line separates the VAL section (top) from the SEAL section (bottom). In the VAL section, the VAL UE contains 'VAL client(s)', which connects to the 3GPP network system via the 'VAL-UU' reference point. In the SEAL section, the VAL UE contains 'Application data analytics enablement client', which connects to the 'VAL client(s)' via the 'ADAE-C' reference point and to the 3GPP network system via the 'ADAE-UU' reference point. The VAL server(s) contains 'Application data analytics enablement server', which connects to the 'VAL client(s)' via the 'ADAE-S' reference point. The 3GPP network system includes interfaces labeled 'N33', 'N6', and 'ADAE-OAM'. + +Figure 5.3.2-1: Architecture for application data analytics enablement – reference points representation. The diagram shows three main components: VAL UE, 3GPP network system, and VAL server(s). The VAL UE contains VAL client(s) and an Application data analytics enablement client. The VAL server(s) contains an Application data analytics enablement server. Reference points are labeled: VAL-UU between VAL client(s) and 3GPP network system; ADAE-C between VAL client(s) and Application data analytics enablement client; ADAE-UU between Application data analytics enablement client and 3GPP network system; ADAE-S between VAL server(s) and Application data analytics enablement server. The 3GPP network system includes N33, N6, and ADAE-OAM interfaces. + +**Figure 5.3.2-1: Architecture for application data analytics enablement – reference points representation** + +The application data analytics enablement client communicates with the application data analytics enablement server over the ADAE-UU reference point. The application data analytics enablement client provides the support for application data analytics enablement functions to the VAL client(s) over ADAE-C reference point. The VAL server(s) communicates with the application data analytics enablement server over the ADAE-S reference point. The application + +data analytics enablement server, acting as AF, may communicate with the 5G Core Network functions (over N33 reference point to NEF and N6 reference point to UPF) and OAM (over ADAE-OAM interface). + +Figure 5.3.2-2 exhibits the service-based interfaces for providing and consuming application data analytics enablement services. The application data analytics enablement server could provide service to VAL server and ADAE client through interface SAdae. + +![Figure 5.3.2-2: Architecture for application data analytics enablement – Service based representation. The diagram shows a User Equipment (UE) on the left containing a VAL client and an Application Data Analytics Enablement client connected via the ADAE-C interface. On the right, an Application function (AF) [VAL Server] connects to a central interface via Naf[SVal], and an Application function (AF) [Application Data Analytics Enablement server] connects via Naf[SAdae]. A dashed vertical line separates the UE from the network functions.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +Figure 5.3.2-2: Architecture for application data analytics enablement – Service based representation. The diagram shows a User Equipment (UE) on the left containing a VAL client and an Application Data Analytics Enablement client connected via the ADAE-C interface. On the right, an Application function (AF) [VAL Server] connects to a central interface via Naf[SVal], and an Application function (AF) [Application Data Analytics Enablement server] connects via Naf[SAdae]. A dashed vertical line separates the UE from the network functions. + +**Figure 5.3.2-2: Architecture for application data analytics enablement – Service based representation** + +Figure 5.3.2-3 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501 [4]. + +![Figure 5.3.2-3: Architecture for application data analytics enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation. The diagram shows two Application functions (AF) at the top: [Application Data Analytics Enablement server] and [VAL Server]. Both connect to a common horizontal interface line. Below this line, an Nnef interface connects to a box labeled SCEF+NEF/NEF.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +Figure 5.3.2-3: Architecture for application data analytics enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation. The diagram shows two Application functions (AF) at the top: [Application Data Analytics Enablement server] and [VAL Server]. Both connect to a common horizontal interface line. Below this line, an Nnef interface connects to a box labeled SCEF+NEF/NEF. + +**Figure 5.3.2-3: Architecture for application data analytics enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation** + +The application data analytics enablement server can be deployed as a SEAL server; hence enhancements to SEAL architecture (as specified in TS 23.434 [5]) are needed to incorporate the ADAE service. Figure 5.3.2-4 illustrates the service-based representation including ADAE server as part of the SEAL framework. + +![Figure 5.3.2-4: SEAL functional model representation using service-based interfaces and including ADAE function. The diagram shows a top row of four functions: ADAE function, VAL function, CAIF core function, and Network slice capability enablement function. These are connected via service-based interfaces (Sval, Cccf, Snsce) to a central horizontal bus. Below the bus, six functions are connected: Location management function (Slm), Group management function (Sgm), Configuration management function (Scm), Identity management function (Sim), Key management function (Skm), and Network resource management function (Snrm).](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Figure 5.3.2-4: SEAL functional model representation using service-based interfaces and including ADAE function. The diagram shows a top row of four functions: ADAE function, VAL function, CAIF core function, and Network slice capability enablement function. These are connected via service-based interfaces (Sval, Cccf, Snsce) to a central horizontal bus. Below the bus, six functions are connected: Location management function (Slm), Group management function (Sgm), Configuration management function (Scm), Identity management function (Sim), Key management function (Skm), and Network resource management function (Snrm). + +**Figure 5.3.2-4: SEAL functional model representation using service-based interfaces and including ADAE function** + +### 5.3.3 Off-network Functional Architecture + +Figure 5.3.3-1 illustrates the generic off-network functional model for ADAE. + +![Figure 5.3.3-1: Generic off-network functional model. The diagram shows two User Equipment (UE) blocks, UE1 and UE2, separated by a dashed line representing the network boundary. Inside UE1, there is a VAL client(s) and an Application data analytics client(s). Inside UE2, there is also a VAL client(s) and an Application data analytics client(s). The VAL client(s) in UE1 connects to the VAL client(s) in UE2 over the VAL-PC5 reference point. The Application data analytics client(s) in UE1 connects to the Application data analytics client(s) in UE2 over the ADAE-PC5 reference point. Both clients in UE1 are also connected to an ADAE-C component.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +Figure 5.3.3-1: Generic off-network functional model. The diagram shows two User Equipment (UE) blocks, UE1 and UE2, separated by a dashed line representing the network boundary. Inside UE1, there is a VAL client(s) and an Application data analytics client(s). Inside UE2, there is also a VAL client(s) and an Application data analytics client(s). The VAL client(s) in UE1 connects to the VAL client(s) in UE2 over the VAL-PC5 reference point. The Application data analytics client(s) in UE1 connects to the Application data analytics client(s) in UE2 over the ADAE-PC5 reference point. Both clients in UE1 are also connected to an ADAE-C component. + +**Figure 5.3.3-1: Generic off-network functional model** + +In the vertical application layer, the VAL client of UE1 communicates with VAL client of UE2 over VAL-PC5 reference point. An application data analytics enablement client of UE1 interacts with the corresponding application data analytics enablement client of UE2 over ADAE-PC5 reference points. The UE1, if connected to the network via Uu reference point, can also act as a UE-to-network relay, to enable UE2 to access the VAL server(s) over the VAL-UU reference point. + +If the ADAE server is deployed as SEAL server, the off network functional architecture is similar to SEAL off-network architecture (as specified in TS 23.434 [5]). + +### 5.3.4 ADAE internal architecture based on 3GPP data analytics framework + +In 3GPP SA2 (TS 23.288 [2]), the following entities have been defined as part of the data analytics framework: + +- NWDAF provides network data analytics services at the 5GC +- DCCF coordinates the collection and distribution of data requested by NF/AF consumers. Data Collection Coordination is supported by a DCCF. Data Consumers can send requests for data to the DCCF rather than directly to the NF/AF Data Source. + +- ADRF stores historical data and/or analytics, i.e., data and/or analytics related to past time period that has been obtained by the consumer. After the consumer obtains data and/or analytics, consumer may store historical data and/or analytics in an ADRF. Whether the consumer directly contacts the ADRF or goes via the DCCF or via the Messaging Framework is based on configuration. + +ADAE server can reuse the existing 3GPP data analytics framework for the data collection coordination, delivery and storage as provided by DCCF and ADRF functionalities. As illustrated in Figure 5.3.4-1, A-DCCF and A-ADRF can be defined as functionalities within the internal ADAE architecture and can offer similar functionality as proposed in 5GC but at application layer. + +Figure 5.3.4-1 illustrates the generic functional model for ADAE when re-using the existing data analytics model. + +![Figure 5.3.4-1: Generic functional model based on network data analytics model. The diagram shows a 'Data Network / Edge Data Network' containing 'A-ADRF' (Analytics and Collected Data) and 'A-DCCF'. Outside the network, 'VAL Server(s) / EAS(s)' connects to an 'ADAE server' via 'ADAE-S'. The 'ADAE server' connects to 'A-DCCF' via 'ADAE-X' and to 'Data Sources' via 'ADAE-Y'. 'A-DCCF' connects to 'A-ADRF' via 'AADRF-1' and to 'Data Sources' via 'ADCCF-1'.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +``` + +graph TD + subgraph Data_Network_Edge_Data_Network [Data Network / Edge Data Network] + A-ADRF["A-ADRF +Analytics and Collected Data"] + A-DCCF["A-DCCF"] + end + VAL["VAL Server(s) / EAS(s)"] + ADAE["ADAE server"] + DS["Data Sources"] + + VAL -- ADAE-S --> ADAE + ADAE -- ADAE-X --> A-DCCF + ADAE -- ADAE-Y --> DS + A-DCCF -- AADRF-1 --> A-ADRF + A-DCCF -- ADCCF-1 --> DS + +``` + +Figure 5.3.4-1: Generic functional model based on network data analytics model. The diagram shows a 'Data Network / Edge Data Network' containing 'A-ADRF' (Analytics and Collected Data) and 'A-DCCF'. Outside the network, 'VAL Server(s) / EAS(s)' connects to an 'ADAE server' via 'ADAE-S'. The 'ADAE server' connects to 'A-DCCF' via 'ADAE-X' and to 'Data Sources' via 'ADAE-Y'. 'A-DCCF' connects to 'A-ADRF' via 'AADRF-1' and to 'Data Sources' via 'ADCCF-1'. + +**Figure 5.3.4-1: Generic functional model based on network data analytics model** + +In this model, an Application layer - Data Collection and Coordination Function (A-DCCF) is used to fetch data or put data into an Application level entity (e.g. A-ADRF, Data Source). Such A-DCCF coordinates the collection and distribution of data requested by ADAE server (over ADCCF-1, ADAE-X). ADAE server can also directly interact with the Data Sources via ADAE-Y. + +Also, Application layer – Analytics and Data Repository Function (A-ADRF) can be used to store historical data and/or analytics, i.e. data and/or analytics related to past time period that has been obtained by the ADAE server (via AADRF-1) or other NFs/NWDAF. ADAE server can also fetch historical data from ADRF. Whether the ADAE server directly contacts the ADRF or goes via the A-DCCF is based on configuration. + +Data Sources can be 5GS data sources (5GC, OAM) or enablement layer data sources (SEAL, EEL) or external data sources at the DN side (VAL server/EAS) and VAL UEs. A-DCCF and A-ADRF can be used only for interacting with certain data sources (e.g. 5GC, OAM) based on configuration, and can be hidden from the VAL layer. + +NOTE: If the Data Source is the VAL UE, then the data collection mechanism shall reuse the SA4 mechanism based on EVEX study (TS 26.531 [7]). + +# 6 Solutions + +## 6.1 Mapping of solutions to key issues + +**Table 7.1-1: Mapping of solutions to key issues** + +| | KI #1 | KI #2 | KI #3 | KI #4 | KI #5 | KI #6 | KI #7 | KI #8 | +|--------|-------|-------|-------|-------|-------|-------|-------|-------| +| Sol #1 | X | | | | | | | | +| Sol #2 | X | X | X | X | | | | | +| Sol #3 | | X | | | | | | | +| Sol #4 | X | | | | | | | | +| Sol #5 | X | | | | | | | | +| Sol #6 | | | | X | X | | | | +| Sol #7 | | | | X | | X | | | +| Sol #8 | | | | X | | | X | | +| Sol #9 | | | | | | | | X | + +## 6.2 Solution #1: Support for application performance analytics + +### 6.2.1 Solution description + +This solution addresses Key Issue #1. + +This solution introduces application layer analytics to provide insight on the operation and performance of an application (VAL server or EAS, application session) and in particular statistics or prediction on parameters related to e.g. VAL server number of connections for a given time and area, VAL server rate of connection requests, connection probability failure rates, RTT and deviations for a VAL server or VAL UE session, packet loss rates etc. + +In this solution, two procedures are described in more detail: + +- one procedure for VAL server related analytics where an example is provided for VAL server performance, +- one procedure for VAL session/UE related analytics. + +#### 6.2.1.1 Procedure on VAL server performance analytics + +Figure 6.2.1.1-1 illustrates the procedure where the VAL server performance analytics are performed based on data collected from the ongoing VAL sessions as well as data from the DN (VAL server, DN database or networking stack at DN). + +Pre-conditions: + +1. ADAEC is connected to ADAES + +![Sequence diagram illustrating ADAES support for VAL server performance analytics. The diagram shows interactions between VAL UE (VAL Client, ADAE client), DN (Networking Stack, VAL server #1, Edge/Cloud DB), ADAES, and Consumer (App Server, NF, AF,...).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant Consumer as Consumer (App Server, NF, AF,...) + participant ADAES + participant DN as DN + participant VAL_UE as VAL UE + + Note right of Consumer: 1. App analytics subscription request +(analytics ID: "VAL perf prediction", VAL server #1, +area of interest, time of interest) + Consumer->>ADAES: 1. App analytics subscription request + ADAES-->>Consumer: 2. Subscription Response + Note right of ADAES: 3. Mapping of analytics ID to data +collection IDs, and data producer IDs, + ADAES->>DN: 4. Data Collection Subscription Request + DN-->>ADAES: 5. Data Collection Subscription Response + Note right of DN: 6. Historical data/stats +Notification +(data collection event ID, +analytics ID, VAL server ID) + DN-->>ADAES: 6. Historical data/stats Notification + Note left of DN: Start of first connection with VAL server #1 (e.g. TCP +connection) + Note right of DN: 7. Data Producer / Collector collects +real-time measurements (e.g. RTT) +about the first connection +from the networking stack + Note right of DN: 8a. Data Notification +(Session Id: '123', 'RTT': '67ms', 'RTT +deviation': '9.88ms') + DN-->>ADAES: 8a. Data Notification + Note left of VAL_UE: 8b. UE Data Notification +(Session Id: '123', 'RTT': '67ms', 'RTT +deviation': '9.88ms') + VAL_UE-->>ADAES: 8b. UE Data Notification + Note left of VAL_UE: End of first connection with VAL server #1 (e.g. TCP +connection) + Note right of VAL_UE: 9. Notification of VAL UE session data / completion of reporting + VAL_UE-->>ADAES: 9. Notification of VAL UE session data / completion of reporting + Note right of ADAES: 10. Correlate/ Combine Data from different Data +Producers for the analytics event, and for multiple +ongoing UE connections to VAL server #1 +(further data/analytics provided by 5GS are not +shown) + ADAES->>ADAES: 10. Correlate/ Combine Data + Note right of ADAES: 11. Derive app layer analytics for VAL serv #1 perf +prediction + ADAES->>ADAES: 11. Derive app layer analytics + Note right of ADAES: 12. Notify VAL #1 perf +analytics + ADAES-->>Consumer: 12. Notify VAL #1 perf analytics + +``` + +Sequence diagram illustrating ADAES support for VAL server performance analytics. The diagram shows interactions between VAL UE (VAL Client, ADAE client), DN (Networking Stack, VAL server #1, Edge/Cloud DB), ADAES, and Consumer (App Server, NF, AF,...). + +**Figure 6.2.1.1-1: ADAES support for VAL server performance analytics** + +1. The consumer of the ADAES analytics service sends a subscription request to ADAES and provides the analytics event ID e.g. "VAL perf prediction", the target VAL server ID, the time validity and area of the request, the required confidence level, whether offline and/or online analytics are needed etc. +2. The ADAES sends a subscription response as an ACK to the consumer. + +3. The ADAES maps the analytics event ID to a list of data collection event identifiers, and optionally a list of data producer IDs. Such mapping may be preconfigured by OAM or may be configured at ADAES based on the analytics event type / vertical type. +4. The ADAES sends a subscription request to the Data Producers (at the DN side or UE side) with the respective Data Collection Event ID and the requirement for data collection. This message includes the Data Collection event ID and/or the analytics event ID, the target VAL server ID, the ADAES ID, the time validity and area of interest, the required confidence level etc. +5. The Data Producer(s) sends a subscription response as an ACK to the ADAES. + +NOTE: The ADAES acting as AF may also subscribe to NEF/SMF/PCF/NWDAF to monitor network/UE situation or network data analytics required for the application data analytics event. + +6. The ADAES based on subscription, may receive offline stats/data on the VAL server performance based on the analytics/data collection event ID. Such offline data can be average/peak throughput, average/maximum e2e delay, jitter, av. PER, availability, VAL server load, number of failed transactions, and can be for a given area and time of the day (based on the time/area of the request). The edge / cloud DB depending on the deployment can be also part of ADRF (for MNO-deployed ADAES). + +A session starts between the VAL server #1 and a UE (this could happen for more than one UEs) + +7. The Data Producer starts collecting/listening to real-time networking or application data (from networking start at DN or VAL server itself). Such data can be the RTT, the PER, throughput etc. +- 8a. The Data Producer sends the real-time data to the ADAES, where the data correspond to the data collection ID or the analytics event ID for which the ADAES subscribed. +- 8b. The ADAES may receive also data (periodically or if a threshold is reached based on configuration) from the application of the UE within the ongoing session (via ADAEC). Such data can be about the RTT, average/peak throughput, jitter, QoE measurements (MOS, stalling events, stalling ratios, etc), QoS profile load, VAL server load, etc. +9. When the VAL UE session with VAL server finishes, the ADAEC notifies the ADAEC of the completion of the reporting. +10. The ADAES abstracts or correlates the data based on the analytics event and the data collection configuration. Such correlation can be filtering of data for the same metrics but with different granularities or be combining/aggregating the data of segments of the end-to-end path (end to end is between VAL client and server). The outcome is an abstracted/correlated/filtered set of data. +11. The ADAES derives application layer analytics on VAL server #1 performance, based on the analytics ID and type of request. Such analytics can be stats or prediction for a given area/time and based on the event type for a given network configuration. +12. The ADAES sends the analytics to the consumer, where these analytics include the VAL server 1 predicted or statistic performance for a given area and time horizon, including also the confidence level, whether offline/online analytics were used. + +#### 6.2.1.2 Procedure on VAL UE / session performance analytics + +Figure 6.2.1.2-1 illustrates the procedure where the VAL session performance analytics are performed based on data collected from the ongoing VAL sessions. + +Pre-conditions: + +1. ADAEC is connected to ADAES + +![Sequence diagram illustrating ADAES support for VAL session performance analytics. The diagram shows interactions between VAL UE 1 (VAL Client, ADAEC, PDU layer), VAL Server #1, ADAES, and Consumer (VAL server #x, NF, AF, ...).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant Consumer as Consumer (VAL server #x, NF, AF,...) + participant ADAES + participant VALServer as VAL Server #1 + participant VALUE1 as VAL UE 1 + Note right of VALUE1: VAL UE 1 contains VAL Client, ADAEC, PDU layer + + Consumer->>ADAES: 1. App analytics subscription request +(analytics ID: "VAL UE perf analytics", VAL server #1, area of interest, time of interest) + ADAES-->>Consumer: 2. Subscription Response + ADAES->>VALServer: 3. Select the ADAEC to assist in VAL UE perf analytics + VALServer->>ADAES: 4a. Data Analytics Subscription Request +('Event': 'VAL UE perf analytics', 'CallbackURI': 'https://...') + ADAES-->>VALServer: 4b. Subscription Response + VALServer->>VALUE1: 5. Mapping of analytics ID to data producer ID, data collection ID and data requirement + VALUE1->>VALServer: 6. ADAEC subscribes to receive local UE data from one or more VAL clients or networking stacks + Note over VALUE1: Start of first connection of VAL client #1 with VAL server + VALServer->>VALUE1: 7. Notification +('Event': 'VAL UE perf prediction', 'Session Id': '123', 'Server': 'VAL Server #1', 'UE_ip': '94.66.227.3', 'UE_port': '62208') + VALUE1->>VALServer: 8. Collect real-time measurements (e.g. RTT) about the first connection + VALUE1->>VALServer: 9. Correlate/Combine Data from different Data Producers for the analytics event + Note over VALUE1: End of first connection between VAL UE #1 and VAL server #1 + Note right of VALUE1: 10. Derive online app layer analytics for VAL UE/session perf prediction + VALUE1->>ADAES: 11. Notification of data / analytics on VAL UE #1 perf + Note right of ADAES: 12. Derive app layer analytics for VAL serv #1 perf prediction + ADAES->>Consumer: 13. Notification of analytics on VAL UE #1 perf + +``` + +Sequence diagram illustrating ADAES support for VAL session performance analytics. The diagram shows interactions between VAL UE 1 (VAL Client, ADAEC, PDU layer), VAL Server #1, ADAES, and Consumer (VAL server #x, NF, AF, ...). + +**Figure 6.2.1.2-1: ADAES support for VAL session performance analytics** + +1. The consumer of the ADAES analytics service sends a subscription request to ADAES and provides the analytics event ID e.g. "VAL UE perf prediction", the target VAL UE ID, VAL server ID/VAL application ID, the time validity and area of the request, the required confidence level, exposure level for providing UE + +analytics. If the consumer is the VAL server, the VAL server can provide to ADAEC application data related to the UE expected route/trajectory and VAL application traffic schedule / expected session time. + +2. The ADAES sends a subscription response as an ACK to the consumer. +3. The ADAES selects the corresponding ADAEC of the VAL UE for which the local analytics need to be performed. +- 4a. The ADAES sends a subscription request to the ADAEC with the analytics event ID and the configuration of the reporting required (e.g. periodic, based on threshold or event) +- 4b. The ADAEC sends a subscription response to ADAES +5. The ADAEC maps the analytics event ID to a list of data collection event identifiers or data collected IDs at the VAL UE or other UEs within the service and in proximity (in group-based communications) +6. The ADAEC subscribes to the VAL clients and/or requests UE local data based on the respective Data Collection Event ID (or the analytics event ID if they already know the mapping). This data may come from the PDU layer of the UE (via listening the traffic), or via VAL client of one or more UEs (if an application consists of a group of UEs). + +A session starts between the VAL UE #1 and a VAL server. + +7. The ADAEC (after being aware from the VAL client that the session started) sends a notification to ADAES that a session started, and it could be possible to provide real-time data analytics for VAL UE performance in the target area. +8. The ADAEC starts collecting data from the corresponding VAL UE(s) based on subscription. Such data can be about the RTT, throughput, jitter, QoE measurements, QoS profile load, etc. It can be also possible that VAL client provides to ADAEC application data related to the UE expected route/trajectory and VAL application traffic schedule / expected session time. +9. The ADAEC filters or correlates the data based on the analytics event and the data collection configuration. +10. When the VAL UE session finishes, the ADAEC (optionally) derives VAL session analytics to ADAES on VAL UE #1 performance, based on the analytics ID and type of request. Such analytics (if performed at the ADAEC can be stats or predictions on the RTT or RTT deviation, average/peak throughput, av. jitter, QoE measurements (MOS, stalling events, buffer related events), QoS profile load, VAL application traffic load etc. In case of prediction, a confidence level shall be also present and a time horizon for the predicted parameters. +11. The ADAEC sends the data of step 8 or the analytics of step 9 (if ADAEC performs analytics) to the ADAES. +12. The ADAES derives application layer analytics on VAL session performance (based on the data or analytics received by the ADAEC), based on the analytics ID and type of request. Such analytics can be stats or prediction for a given area/time and based on the event type for a given network configuration. Such analytics (if no analytics is performed at ADAEC) at ADAES can be stats or predictions on the RTT or RTT deviation, average/peak throughput, av. jitter, QoE measurements, QoS profile load, VAL application traffic load etc. In case of prediction, a confidence level shall be also present and a time horizon for the predicted parameters. +13. The ADAES sends the analytics to the consumer, where these analytics include the VAL UE 1 session predicted performance for a given area and time horizon, including also the confidence level, whether offline/online analytics were used. + +### 6.2.2 Corresponding Analytics API + +This subclause provides a summary on the corresponding Analytics API for solution #1. + +For VAL server performance analytics, this includes: + +- Inputs: per VAL server performance measurements (application QoS measurements such as latency, channel losses, data rate, jitter), historical data/stats for VAL server performance, network/KPI monitoring from 5GS +- List of Data Sources + +- Data Source #1 information: VAL UE #1 (or more VAL UEs having a session with VAL server #1), VAL Server #1 +- Data required from Data Source #1: application QoS measurements +- Data Source #2 information: OAM +- Data required from Data Source #1: PM data +- Data Source #3 information: 5GC +- Data required from Data Source #3: service experience analytics, network and QoS monitoring +- Output: Predicted application QoS metrics per VAL server, Statistics on VAL server application QoS/performance metrics + +For VAL session performance analytics, this includes: + +- Inputs: per VAL session performance measurements (application QoS measurements such as latency, channel losses, data rate, jitter) +- List of Data Sources: + - Data Source information: VAL UE #1, VAL Server #1 + - Data required from Data Source: application QoS measurements +- Output: Predicted application QoS metrics per VAL session + +### 6.2.3 Solution evaluation + +This solution addresses Key Issue #1 and introduces application layer analytics to predict the performance of a VAL server or an application session between a VAL UE and a VAL server. Such solution enables the VAL layer to get statistics or predictions for expected deviations of application performance metrics (e.g. RTT) based on data collected from the ADAE clients, as well as from 5GS. This solution is complementary to Solution #4 which covers only the VAL UE-to-UE sessions. Also, this Solution doesn't overlap with Solution #2 which provides a generic mechanism for data analytics enablement (and could be re-used). + +This solution is technically viable and doesn't introduce any impact on 5GS. + +## 6.3 Solution #2: Data Analytics Enablement + +### 6.3.1 Solution description + +#### 6.3.1.1 General + +The following solution corresponds to the key issue #1, 2, 3, 4 on support for application performance analytics, data collection, edge analytics enablement, and interaction with SEAL service. + +ADAE supporting application and service enablement layer analytics collects application or service enablement layer related information from the vertical application layer, service enablement layer, 5GC, and/or OAM to perform data analytics and to provide statistics or predictions. + +The solution addresses the following aspects: + +- Enablement of data analytics services by the ADAES layer, by addressing the types of interactions possible between ADAES and other service layer entities. +- Description of how higher-level data analytic requests can be provided to the ADAES layer, and on how analytics requests are translated into generic data collection tasks. + +- Description of the information flows for generic data analytics and data collection. + +A data source profile is proposed for a data source which describes capabilities related to data generation, data availability and pre-processing, as shown in table 6.3.1.3-1. + +A data analytics request from a requesting server/client to ADAE provides criteria for the data source profile elements to indicate the applicable data sources. The data analytics request also includes criteria for determining the information applicable for collection via the data collection procedure. The data analytics request also includes task processing requirements and operations used to determine the necessary level of processing by the ADAE, as shown in table 6.3.1.3-2 + +A data collection request from ADAE to a source provides information about the original data source and the data required, as shown in table 6.3.1.3-4. + +NOTE 1: Data collection tasks may be performed by ADAE using available dedicated functionality, e.g. Application Data Collection and Coordination Function deployed by MNO at the service layer. + +NOTE 2: Further definition of the data processing operations will be provided in the normative phase, including stage 3. + +Interaction between ADAE and the vertical application layer can be done over ADAE-S or ADAE-C reference points. + +If ADAE is implemented in the SEAL layer, then: + +- interaction between ADAE server and application enabler servers can be done over SEAL-S (e.g. for EES see TS 23.558 Figure A.4.1-1, for VAE Server see TS 23.286 Figure 6.2-2). Interactions between ADAE client and the corresponding application enabler client can be done over SEAL-C. +- interaction between ADAE server and SEAL server could be done over SEAL-X (TS 23.434 Figure 6.2-3), + +#### 6.3.1.2 Procedures + +##### 6.3.1.2.1 Generic server-side initiated data analytics + +Pre-conditions: + +1. ADAE is provisioned with data source profiles (Table 6.3.1.3-1) for data sources in the vertical application layer, application/service enablement layer (e.g., SEAL server/client, EES/EEC, CAPIF entities), core network (e.g., OAM, DCCF, NWDAF), etc. Alternatively, ADAE may perform a discovery for the data source profiles of data sources of interest. + +![Sequence diagram for Server-side initiated generic data analytics request. Lifelines: Requesting server, Data repository, ADAE server, VAL server(s), 5GC/OAM, ADAE client, VAL client(s). The process involves a request from the Requesting server to the ADAE server, followed by data source determination and conditional data collection from VAL server(s), ADAE client, or 5GC/OAM. Finally, the ADAE server performs optional analytics and returns a response.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant RS as Requesting server + participant DR as Data repository + participant AS as ADAE server + participant VS as VAL server(s) + participant GO as 5GC/OAM + participant AC as ADAE client + participant VC as VAL client(s) + + Note over DR: Data repository + RS->>AS: 1. Data analytics request + AS->>AS: 2. Determine input data and sources + alt Alt. a: 3a. Generic Data Collection procedure (clause 6.3.1.2.3) Data source = VAL server(s) + AS->>VS: 3a. Generic Data Collection procedure (clause 6.3.1.2.3) +Data source = VAL server(s) + else Alt. b: 3b. Generic Data Collection procedure (clause 6.3.1.2.3) Data source = ADAE client + AS->>AC: 3b. Generic Data Collection procedure (clause 6.3.1.2.3) +Data source = ADAE client + else Alt. c: 3c. Generic Data Collection procedure (clause 6.3.1.2.3) Data source = 5GC, OAM + AS->>GO: 3c. Generic Data Collection procedure (clause 6.3.1.2.3) +Data source = 5GC, OAM + end + AS->>RS: 4. (cond) Data analytics response (data collection) + Note over AS: 5. (cond) ADAE derives requested analytics, optional output data store + Note over AS: 6. (cond) Perform/trigger other analytics based on result + AS->>RS: 7. (cond) Data analytics response (data analytics) + +``` + +Sequence diagram for Server-side initiated generic data analytics request. Lifelines: Requesting server, Data repository, ADAE server, VAL server(s), 5GC/OAM, ADAE client, VAL client(s). The process involves a request from the Requesting server to the ADAE server, followed by data source determination and conditional data collection from VAL server(s), ADAE client, or 5GC/OAM. Finally, the ADAE server performs optional analytics and returns a response. + +**Figure 6.3.1.2.1-1: Server-side initiated generic data analytics request** + +1. The requesting server sends a data analytics request to the serving ADAE server to initiate data analytics, using either a one-time request or a subscription request. The request may specify the type of data analytics and the requirements/ preferences of the required analytics as defined in Table 6.3.1.3-2. +2. If the request is authorized, the ADAE server may determine which input data should be collected and the input data sources based on the request and local policies. +3. Based on the determination in step 2, the ADAE server may collect input data from various sources by performing data collection procedure, as described in clause 6.3.1.2.3. + +NOTE 1: A data repository may be assumed to be available to the ADAE server for corresponding data storage tasks, as described in clause 6.3.1.2.3. The repository functionality may be provided e.g. by a SEALDD storage server, or an Application – Analytics and Data Repository Function deployed by MNO at the service enablement layer. + +Depending on the type of data source, this step can be performed with several alternatives as follows: + +- (a) from other servers: + +- 3a. If the requested analytics requires server-side input data, the ADAE server may collect input data from the server-side entities such as vertical application servers (and EAS, if the target application is an edge application) via ADAE-S reference point. + +NOTE 2: In this alternative, the ADAE server may also collect input data from SEAL server(s) and application/service enabler server(s) (e.g. EES, VAE-S). + +(b) from ADAE clients: + +- 3b1. If the requested analytics requires client-side input data, the ADAE server performs the data collection procedure with the corresponding ADAE client as source. The request specifies what input data is required from the client-side. + +NOTE 3: In this alternative, the ADAE client may also collect input data from SEAL client and application/service enabler clients(s) (e.g. EEC, VAE-C), or other ADAE clients (via ADAE-PC5). + +(c) from other functions external to the service enablement layer (e.g. NWDAF, OAM): + +- 3c. The ADAE server performs the data collection procedure with other analytics functions in the system, such as NWDAF or OAM, as sources. For example, the ADAE server may collect input data from 5GC via monitoring events or via interactions with NWDAF, receive input data from OAM system, receive analytics result from NWDAF by subscription, etc. +4. If the step 1 request requires data collection without higher-level analytics, ADAE sends a data analytics response (collected data) to the requestor with the collected data or the location where the collected data is stored, as defined in Table 6.3.1.3-5. + 5. If the step 1 request includes analytics tasks to be performed, and based on the collected input data, the ADAE server derives the analytics result. The ADAE server performs the analytics operations provided in the data analytics request in step 1. The result of the analytics task on the collected data can be optionally stored in the repositories available, such as a SEALDD storage server, Application-ADRF, etc. + 6. Following an analytics task, the ADAE server may perform or trigger other analytics actions (using requests to the corresponding entities) based on the analytics result, before providing a final response to the requestor. + 7. The ADAE server provides the requested data analytics task outputs to the requestor, using either a response or a notification message, depending on the service used in step 1. + +##### 6.3.1.2.2 Generic client-side initiated data analytics + +Pre-conditions: + +1. ADAE is provisioned with data source profiles (Table 6.3.1.3-1) for data sources in the vertical application layer, service enablement layer (e.g., SEAL server/client, EES/EEC, CAPIF entities), core network (e.g., OAM, DCCF, NWDAF), etc. Alternatively, ADAE may perform a discovery for the data source profiles of data sources of interest. + +![Sequence diagram for Client-side initiated generic data analytics procedure. Lifelines: Requesting client, ADAE client, VAL client(s), 5GC/OAM, Data repository, ADAE server, VAL server(s). The process involves a request from the client, internal data determination and collection by the ADAE client, a request to the ADAE server, optional data source determination by the server, conditional data collection from VAL servers or 5GC, and finally the analytics response back to the client.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant Requesting client + participant ADAE client + participant VAL client(s) + participant 5GC/OAM + participant Data repository + participant ADAE server + participant VAL server(s) + + Note right of ADAE client: 2. Determining where to collect input data + Note right of ADAE client: 3. (cond) Generic Data Collection procedure (clause 6.3.1.2.3) +Data source = VAL client(s) + + Note right of ADAE server: 5. (Opt) Determine input data collection sources + Note right of ADAE server: Alt. a +6a. (cond) Generic Data Collection procedure (clause 6.3.1.2.3) +Data source = VAL Server(s) + Note right of ADAE server: Alt. b +6b. (cond) Generic Data Collection procedure (clause 6.3.1.2.3) +Data source = 5GC + + Note right of ADAE server: 8. (cond) ADAE derives requested analytics, optional data store + Note right of ADAE server: 10. (cond) Perform/trigger other analytics based on result + + Requesting client->>ADAE client: 1. Data analytics request + ADAE client->>ADAE client: 2. Determining where to collect input data + ADAE client->>ADAE client: 3. (cond) Generic Data Collection procedure (clause 6.3.1.2.3) +Data source = VAL client(s) + ADAE client->>ADAE server: 4. Data analytics request (with optional client-side input data) + ADAE server->>ADAE server: 5. (Opt) Determine input data collection sources + alt Alt. a: 6a. (cond) Generic Data Collection procedure (clause 6.3.1.2.3) Data source = VAL Server(s) + VAL server(s)->>ADAE server: + alt Alt. b: 6b. (cond) Generic Data Collection procedure (clause 6.3.1.2.3) Data source = 5GC + 5GC/OAM->>ADAE server: + ADAE server->>ADAE client: 7. (cond) Data analytics response (data collection) + ADAE server->>ADAE server: 8. (cond) ADAE derives requested analytics, optional data store + ADAE server->>ADAE client: 9. (cond) Data analytics response (data analytics) + ADAE server->>ADAE server: 10. (cond) Perform/trigger other analytics based on result + ADAE client->>Requesting client: 11. Data analytics response + +``` + +Sequence diagram for Client-side initiated generic data analytics procedure. Lifelines: Requesting client, ADAE client, VAL client(s), 5GC/OAM, Data repository, ADAE server, VAL server(s). The process involves a request from the client, internal data determination and collection by the ADAE client, a request to the ADAE server, optional data source determination by the server, conditional data collection from VAL servers or 5GC, and finally the analytics response back to the client. + +**Figure 6.3.1.2.2-1: Client-side initiated generic data analytics procedure** + +1. The requesting client sends a data analytics request to the serving ADAE client to initiate data analytics, using either a one-time request or a subscription request. The request may specify the type of data analytics and the requirements/ preferences of the required analytics, as defined in Table 6.3.1.3-2. +2. If the request is authorized, the ADAE client determines which input data should be collected and where to collect the input data based on the request. +3. Based on the determination in step 2, if client-side input data is required, the ADAE client may collect input data from the client-side entities such as vertical application clients (via ADAE-C) and other ADAE clients (via ADAE-PC5) by performing data collection procedure, as described in clause 6.3.1.2.3. + +NOTE 1: In this step, the ADAE client may also collect input data from SEAL client and application/service enabler clients(s) (e.g. EEC, VAE-C). + +4. The ADAE client sends the data analytics request to the ADAE server, as defined in Table 6.3.1.3-2. If client-side input data has been collected by the ADAE client, the collected client-side input data or the location of the data will also be sent to the ADAE server. + +5. The ADAE server may determine which input data should be collected and the input data sources, based on the request from the ADAE client and/or local policies +6. Based on the request in step 4 and/or the determination in step 5, the ADAE server may collect input data from various sources by performing data collection procedure, as described in clause 6.3.1.2.3. + +NOTE 2: A data repository may be assumed to be available to the ADAE server for corresponding data storage tasks, as described in clause 6.3.1.2.3. The repository functionality may be provided e.g. by a SEALDD storage server, or an Application – Analytics and Data Repository Function deployed by MNO at the service enablement layer. + +Depending on the type of data source, this step can be performed with several alternatives as follows: + +(a) from other servers: + +- 6a. The ADAE server collects input data from server-side entities such as vertical application servers (and EAS, if the target application is an edge application) via ADAE-S reference point. + +NOTE 3: In this alternative, the ADAE server may also collect input data from SEAL server(s) and application/service enabler server(s) (e.g. EES, VAE-S). + +(b) from other functions external to the service enablement layer (e.g. NWDAF, OAM): + +- 6b. The ADAE server may collect input data and/or request for analytics service from other analytics functions in the system. +7. If the step 1 request requires data collection without higher-level analytics, ADAE server sends a data analytics response (collected data) to the requester with the collected data or the location where the collected data is stored, as defined in Table 6.3.1.3-3. +8. If the step 1 request includes analytics tasks to be performed, and based on the collected input data, the ADAE server derives the analytics result. The ADAE server performs the analytics operations provided in the data analytics request in step 4. The result of the analytics task on the collected data can be optionally stored in the repositories available, such as a SEALDD storage server, Application-ADRF, etc. +9. Following an analytics task, the ADAE server sends a data analytics response (or a notification) to the ADAE client with the analytics result or the location where the resulting data is stored, as defined in Table 6.3.1.3-3. +10. Following an analytics task, the ADAE server or client may perform or trigger other analytics actions (using requests to the corresponding entities) based on the result, before providing a final response to the requestor. +11. The ADAE client provides the requested data analytics task outputs to the requestor, using either a response or a notification message, depending on the service used in step 1. + +##### 6.3.1.2.3 Generic data collection procedure + +Figure 6.3.1.2.3-1 describes a generic data collection procedure, i.e., using abstract data sources. + +Precondition: ADAE is provisioned with data source profiles (Table 6.3.1.3-1) for data sources in the vertical application layer, service enablement layer (e.g., SEAL server/client, EES/EEC, CAPIF entities), core network (e.g., OAM, DCCF, NWDAF), etc. Alternatively, ADAE may perform a discovery for the data source profiles of data sources of interest. + +![Sequence diagram illustrating the Generic data collection procedure. Lifelines: ADAE, Data Source(s), and Data Repository. Steps: 1. ADAE determines input data and source(s); 2. ADAE sends data collection request/response to Data Repository; 3. ADAE sends data collection request/response to Data Source(s); 4. ADAE (Pre-)Process collected data; 5. (Opt) Collected data store procedure (spanning all lifelines).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant ADAE + participant DS as Data Source(s) + participant DR as Data Repository + Note left of ADAE: 1. Determine input data and source(s) + ADAE->>DR: 2. Data collection request/response + ADAE->>DS: 3. Data collection request/response + Note left of ADAE: 4. (Pre-)Process collected data + Note over ADAE, DS, DR: 5. (Opt) Collected data store procedure + +``` + +Sequence diagram illustrating the Generic data collection procedure. Lifelines: ADAE, Data Source(s), and Data Repository. Steps: 1. ADAE determines input data and source(s); 2. ADAE sends data collection request/response to Data Repository; 3. ADAE sends data collection request/response to Data Source(s); 4. ADAE (Pre-)Process collected data; 5. (Opt) Collected data store procedure (spanning all lifelines). + +**Figure 6.3.1.2.3-1: Generic data collection procedure** + +1. ADAE determines data collection sources and processing operations based on the requirements in the data analytics request. For example, ADAE may determine whether data should be collected from the application layer, the service enablement layer, the core network, or whether a data processing task should be performed using data from multiple layers/sources. +2. ADAE may collect existing data that can meet or partially meet the requirements of the data analytics request from sources with the "Data source role" IE set as "repository" in the data source profile (e.g., SEALDD storage server, Application-ADRF). The request and response for data collection are defined in 6.3.1.3-4 and 6.3.1.3-5. + +NOTE 1: ADAE data collection requests/responses may be realized via subscriptions/notifications. + +3. ADAE collects data from other identified data sources. The request and response for data collection from a data source are defined in 6.3.1.3-4 and 6.3.1.3-5. +4. ADAE performs data processing operations as determined in step 1 and/or required by policies. For example, data samples that target the same performance metrics but originate from different sources may be normalized and validated. Such processing may remove samples that are inconsistent across different sources and keep samples that achieve consensus across all sources. +5. The collected (and optionally processed) data can be optionally stored in available repositories, such as a SEALDD storage server, Application-ADRF, etc. + +#### 6.3.1.3 Information Flows + +The data source profile includes information about the data generation/production capability of the data source to support data collection for data analytics service and the availability/accessibility of the generated/produced data, as defined in Table 6.3.1.3-1. + +**Table 6.3.1.3-1: Data source profile** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Source ID | M | ID of the source | +| Data source entity | M | Specifies the type of the entity, such as a vertical application server, a SEAL server/client, EES/EEC, EAS, etc.(NOTE 1) | +| Information type | M | Type of information can be provided by the data source, e.g., performance indicators, resource usage data, server load data, etc. The information types may also include those obtained from NWDAF or OAM events, or from service layer original sources such as application performance (solution #1), edge load (solution #3), (NOTE 2) | +| Data generation schedule | O | The schedule of data generation, e.g. when the data source is active to produce data. | +| Data source role | O | Role of the data source, e.g., original source, repository, logging server, etc. | +| Original source | O | If the data source role is not original source, specifies the original data source of the data provided by this data source. | +| Data freshness | O | If the data source role is not original source, length of time elapsed after the data is generated until is available at the data source. Alternatively, the data collection rate supported by the source is provided | +| Data storage capability | O | Indicates data storage capabilities, e.g. how long the data can be stored. | +| Anonymization capability | O | Indicates whether the data available at this data source can be anonymized before collection. | +| Pre-processing capabilities | O | Indicates capabilities of the data source to provide pre-processing functionality, such as aggregation, validation, etc. | +| Original source communication constraints | O | Constraints of the original source such as geographic constraints, access technology associated with the original data source, etc. | +| NOTE 1: The list of possible choices may be determined in the specification phase, based on ADAES capabilities to interact with other service layer entities | | | +| NOTE 2: The values available for "information type" may be determined in the specification phase. | | | + +Table 6.3.1.3-2 describes information elements in the data analytics task request from the requester to ADAE or from ADAE client to ADAE server. + +**Table 6.3.1.3-2: Data analytics request** + +| Information element | Status | Description | +|------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requester ID | M | ID of the requesting server/client making the request | +| Data source profile criteria | M | List of criteria for determining the data sources, based on the IEs present in the Data source profile table 6.3.1.3-1. | +| Information filter | O | Parameters and constraints of the information collected for the task. For example, the filter may specify a PLMN, a service provider, area of interest, time window of interest, reporting threshold (for NWDAF subscriptions), etc.... | +| Task processing operation | O | Specifies data processing operations that need to be performed on the collected data to produce the analytics results, such as normalization, rounding, clean-up, etc. to generate the task results. | + +| | | | +|---------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | When the task requires data to be collected from multiple sources, this parameter may specify operations to combine/merge the data from different sources such as aggregation, validation, data alignment, etc. | +| Task requirements | O | Specifies requirements on the data analytics task or the resulting data, e.g., when the task results are needed, where the resulting data should be stored, required data sampling/updating rate, required number of data samples, required amount (size) of collected data (dataset), required data granularity/accuracy, required level of confidence, etc. | +| Existing input data | O | Specifies input data that may already be available. | + +Table 6.3.1.3-3 describes information elements in the data analytics response from ADAE to the requester. + +**Table 6.3.1.3-3: Data analytics response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------| +| ADAES ID | M | ID of the ADAES | +| Task results | O | Output of the data analytics task. | + +Table 6.3.1.3-4 describes information elements in the data collection request from ADAE to a data source. + +**Table 6.3.1.3-4: Data collection request** + +| Information element | Status | Description | +|----------------------|--------|-------------------------------------------| +| ADAES ID | M | ID of the ADAES | +| Original data source | M | Identifies all the original data sources. | +| Data required | M | Identifies the data to be collected. | + +Table 6.3.1.3-5 describes information elements in the data collection response from the data source to ADAE. + +**Table 6.3.1.3-5: Data collection response** + +| Information element | Status | Description | +|------------------------|--------|----------------------------------------| +| ADAES ID | M | ID of the ADAES | +| Data collection output | O | Output of the data collection request. | + +### 6.3.2 Evaluation + +The solution addresses Key Issue #1, 2, 3, 4 on support for data collection for application and provides generic procedures and APIs to support different types of data analytics (e.g., application performance analytics, edge analytics, etc.). + +The solution defines generic procedures for application data analytics enablement service enablement, including interactions with other service enablement layer entities (e.g., SEAL, EEL) or the core network. The solution also enables ADAES to select data sources and to collect data for the analytics services provided. The solution specifies the API for requesting application data analytics enablement service and for enabling the collection and preparation of data that are originated from different sources. + +## 6.4 Solution #3: Support for edge load analytics + +### 6.4.1 Solution description + +This solution addresses Key Issue #2. + +This solution introduces edge load analytics to provide insight on the operation and performance of an EDN and in particular statistics or prediction on parameters related to: + +- the EAS / EES load for one or more EAS/EES +- edge platform load parameters, which include the aggregated load per EDN or per DNAI due to the edge support services and e.g., load level of edge computational resources. + +Such analytics can improve edge support services by allowing the pro-active edge service operation changes to deal with possible edge overload scenarios. For example, this can trigger EAS migration to a different EDN / central DN, or pro-active EAS reselection for a target UE or group of UEs. + +Figure 6.4.1-1 illustrates the procedure where the edge analytics are performed based on data collected from the EDN (EAS and/or EES, edge database or networking stack at EDN side). + +Pre-conditions: + +1. ADAES has discovered the APIs to access the edge services at EDN. + +![Sequence diagram illustrating ADAES support for edge analytics. The diagram shows interactions between 5GS (OAM, 5GC), EDN (Networking Stack / SEALDD / MEP, EAS #1), ADAES, and Consumer (App Server, AF, NF,...).](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant Consumer as Consumer (App Server, AF, NF,...) + participant ADAES + participant EDN + subgraph EDN + direction TB + EAS[EAS #1] + NS[Networking Stack / SEALDD / MEP] + end + participant 5GS as 5GS (OAM, 5GC) + + Note right of ADAES: 1. Analytics subscription request +(analytics ID: "EDN/EAS load prediction", area of interest, time of interest) + ADAES->>Consumer: 2. Subscription Response + Note right of ADAES: 3. Mapping of analytics ID to data collection IDs, and data producer IDs + ADAES->>EDN: 4. Edge Data Collection Subscription Request + EDN->>ADAES: 5. Data Collection Subscription Response + Note right of EDN: 6. Historical data/stats Notification +(data collection event ID, analytics ID, DNN/DNAI, edge offline stats) + EDN->>ADAES: 6. Historical data/stats Notification + Note left of EDN: 7. Collection of real-time measurements about the EDN or EES/EAS load / resource utilization (for the requested time) and analytics from 5GS + EDN->>ADAES: 8. Data Notification +(DNN, DNAI #x, cell #1,2, 'load': '50%', number of connections: '500',...) +... +Note right of ADAES: 9. Derive edge analytics for EDN/EAS load prediction + ADAES->>Consumer: 10. Notify edge perf analytics + +``` + +Sequence diagram illustrating ADAES support for edge analytics. The diagram shows interactions between 5GS (OAM, 5GC), EDN (Networking Stack / SEALDD / MEP, EAS #1), ADAES, and Consumer (App Server, AF, NF,...). + +Figure 6.4.1-1: ADAES support for edge analytics + +1. The consumer of the ADAES analytics service sends a subscription request to ADAES and provides the analytics event ID e.g. edge performance prediction or stats, the DNN / DNAI, the time validity and area of the request, the required confidence level, whether offline and/or online analytics are needed etc. +2. The ADAES sends a subscription response as an ACK to the consumer. +3. The ADAES maps the analytics event ID to a list of data collection event identifiers, and optionally a list of data producer IDs. Such mapping may be preconfigured by OAM or may be configured at ADAES based on the analytics event ID. Such Data Producers can be EASs onboarded to EDN, EESs, SEALDD server, MEP services (e.g. RNIS). +4. The ADAES sends a subscription request to the Data Producers (EASs onboarded to EDN, EESs, SEALDD server, RNIS, N6 endpoint at EDN, NWDAF, OAM) with the respective Data Collection Event ID and the + +requirement for data collection. This message includes the Data Collection event ID and/or the analytics event ID, the ADAES ID, the time validity and area of the request, the required confidence level etc. + +5. The Data Producer(s) sends a subscription response as an ACK to the ADAES. +6. The ADAES based on subscription, may receive offline stats/data on the edge DN load based on the analytics/data collection event ID from the data producer or from A-ADRF (see clause 5.3.4). Such offline data can be per EDN or per DNAI or per EAS/EES load statistics and edge computational resource utilization stats for a given time and area of interest. One example can be the load in terms of number of EAS or EES connections for a given area or time window, or the average edge computational resource usage or usage ratio based on the EDN total resource availability, EDN overload/high load indication events, probability of EAS/EES unavailability due to high load, etc. +7. The Data Producers at the edge start collecting data. Such data can be measurements or analytics based on the data source/producer, as follows: + - from OAM or EAS/ASP (for EAS load info): Per EAS/EES computational resource load, number of connections per EES/EAS + - from SEALDD server / N6 endpoint: N6 load / SEALDD server load + - from 5GC / NWDAF: DN performance analytics + - from OAM / MDAS: UPF load analytics (per DNAI) + - from MEC platform services (e.g., RNIS): per cell radio conditions / load for all cells within EDN coverage + +NOTE: How the ADAES obtains the EAS load information from EAS/ASP is up to implementation. + +8. The Data Producer send the data to the ADAES (based on step 7 measurements or analytics), where the data correspond to the data collection ID or the analytics event ID for which the ADAES subscribed. Such data can be provided one time or periodically or based on a threshold (e.g., load >X%). +9. The ADAES derives edge analytics on EDN / DNAI load or per EES/EAS load, based on the analytics ID and type of request. The analytics are derived based on the performance analytics received per DN or load analytics per DNAI/UPF; as well as considering measurements on the computational or RAN resource load or number of connections for the EES/EASs which are active at the EDN. Such analytics can be stats or prediction for a given area/time and based on the event type for a given network configuration. Such analytics can be for example a predicted load indication for the EDN or for an EES or EAS (e.g. 50% load or medium /high load), a predictive load in terms of number of EAS or EES connections for a given area or time window, or the predicted computational resource usage or usage ratio based on the EDN total resource availability, EDN overload/high load indication events, probability of EAS/EES unavailability due to high load. +10. The ADAES sends the edge analytics to the consumer, based on the request and the derived analytics in step 9. Such analytics indicate a prediction of the EDN load considering inputs from both 5GS as well as from edge platform services. Such prediction can also be in form of a recommendation for triggering an EAS relocation to a different platform. + +### 6.4.2 Corresponding Analytics API + +This subclause provides a summary on the corresponding Analytics API for solution #3. + +- Inputs: edge platform load data, EAS/EES load data, DN performance data, UPF load analytics. +- List of Data Sources + - Data Source #1 information: OAM / MDAS + - Data required from Data Source #1: UPF load analytics + - Data Source #2 information: 5GC / NWDAF + - Data required from Data Source #2: DN performance analytics + - Data Source #3 information: SEALDD server + +- Data required from Data Source #3: N6 load measurements, SEALDD computational resource load +- Data Source #4 information: EES +- Data required from Data Source #4: EES computational resource load or number of connections of EES +- Data Source #5 information: EAS +- Data required from Data Source #5: EAS computational resource load or number of connections of EAS +- Data Source #6 information: RNIS +- Data required from Data Source #6: per cell average radio conditions and resource utilization (for all cells within edge coverage) +- Output: stats or predictions on the EDN load conditions, EES or EAS load stats/predictions, recommendation for EAS relocation trigger (due to expected high load or edge resources). + +### 6.4.3 Solution evaluation + +This solution addresses Key Issue #2 and introduces edge data analytics to predict the load of an edge platform or an edge service. Such analytics can improve edge support services by allowing the pro-active edge service operation changes to deal with possible edge overload scenarios. + +This solution is feasible and doesn't introduce any dependency to 3GPP network systems. For the interaction to 5GC, ADAE server acts as AF, whereas for the interaction to OAM, ADAE server can be seen as a trusted 3rd party MDA service consumer (for consuming UPF load analytics). For the data collection related to ETSI MEC service like RNIS, this is only possible if the EDN has deployed such service, and any interaction between ADAE server and RNIS can be either up to ECSP implementation or by re-using EDGE-3 interface (RNIS acting as EAS). + +## 6.5 Solution #4: Support for performance analytics for UE-to-UE sessions + +### 6.5.1 Solution description + +This solution addresses Key Issue #1. + +This solution introduces application layer analytics to predict the performance of an application session among two or more VAL UEs within a service or group. Such prediction relates to application QoS attributes prediction for a given time horizon and area. This can be requested by the VAL server during the session, or the VAL server can subscribe to receive predicted application QoS downgrade indication for an ongoing session. Such analytics will help improving the application service experience and allow the VAL layer to pro-actively adapt to predicted application QoS changes. + +Figure 6.5.1-1 illustrates the procedure where the VAL session performance analytics are performed based on data collected from the ongoing VAL sessions. + +Pre-conditions: + +1. ADAECs are connected to ADAES + +![Sequence diagram illustrating ADAES support for VAL session performance analytics. The diagram shows interactions between VAL UE 2, VAL UE 1, ADAES, and VAL Server. The process involves subscription, connection start, data collection, and analytics notification.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant VAL_UE_2 as VAL UE 2 + participant VAL_UE_1 as VAL UE 1 + participant ADAES + participant VAL_Server as VAL Server + + Note left of VAL_UE_2: VAL Client, ADAEC #2 + Note left of VAL_UE_1: VAL Client, ADAEC #1 + + VAL_Server->>ADAES: 1. App analytics subscription request (analytics ID: "UE-to-UE session prediction") + ADAES-->>VAL_Server: 2. Subscription Response + Note right of ADAES: 3. Find the ADAEC to perform UE-to-UE session analytics + ADAES->>VAL_UE_1: 4a. Data Analytics Subscription Request ('Event': 'UE-to-UE session prediction', session iD, app QoS attributes) + VAL_UE_1-->>ADAES: 4b. Subscription Response + Note left of VAL_UE_1: Start of first connection of VAL UE #1 to VAL UE #2 (or more Ues) + VAL_UE_1->>ADAES: 5. Notification + Note left of VAL_UE_1: 6. Collect real-time application QoS measurements (e.g. latency, PER) about the first connection + Note right of VAL_UE_1: 7. Detect / Predict application QoS attribute change + VAL_UE_1->>ADAES: 8. Data / Analytics Notification + Note right of ADAES: 9. Predict application QoS attribute change + ADAES->>VAL_Server: 10. Notification of analytics for session #x + +``` + +Sequence diagram illustrating ADAES support for VAL session performance analytics. The diagram shows interactions between VAL UE 2, VAL UE 1, ADAES, and VAL Server. The process involves subscription, connection start, data collection, and analytics notification. + +**Figure 6.5.1-1: ADAES support for VAL session performance analytics** + +1. The consumer of the ADAES analytics service sends a subscription request to ADAES and provides the analytics event ID e.g. "VAL UE to UE session prediction", the target VAL UE ID or group of UE IDs, the VAL session / service ID, the time validity and area of the request, the required confidence level, exposure level for providing UE to UE analytics. Such request can also include whether the analytics notification shall be periodic or based on an expected application QoS change (in that case also the thresholds can be provided at the request) +2. The ADAES sends a subscription response as an ACK to the consumer. +3. The ADAES selects the corresponding ADAEC #1 of the VAL UE 1 where the session performance analytics need to be performed. Such UE can be for example a capable and authorized UE from the involved VAL UEs within the service or group, e.g. a group lead. + +4a. The ADAES sends a subscription request to the ADAEC #1 with the analytics event ID and the configuration of the reporting required (e.g., periodic, based on threshold or event). Such request also includes the application QoS attributes to be analyzed (latency, jitter, PER,...) + +4b. The ADAEC #1 sends a subscription response to ADAES + +A session starts between the VAL UE #1 and a VAL UE #2 (or more VAL UEs). + +5. The ADAEC #1 (after being aware from the VAL client that the session started) sends a notification to ADAES that a session started, and it could be possible to provide real-time data analytics for VAL UE to UE session performance in the target area. + +6. The ADAEC #1 starts collecting data from the corresponding VAL UE(s) based on subscription. Such data can be about the latency, throughput, jitter, QoE measurements, PQI load, etc. The data can be collected by ADAEC #1 from other ADAECs via ADAE-C interface, or from the VAL clients (VAL client to VAL client interaction is out of scope). + +7. The ADAEC either detects or predicts an application QoS change (depending on the authorization of ADAEC to perform analytics). Such change can be for example an application QoS downgrade related to the UE-to-UE session latency, or the PER/channel losses higher than a predefined threshold, for a given time horizon with a certain confidence level. + +8. The ADAEC sends the data or the analytics (depending on whether ADAEC provides a prediction) to the ADAES. + +9. The ADAES based on the received notification, confirms/verifies the analytics received or provides analytics (in case that data were reported) for the UE-to-UE session. Such analytics can be about predicting the application QoS change for the UE-to-UE session. + +13. The ADAES sends the analytics to the consumer. + +### 6.5.2 Corresponding Analytics API + +This subclause provides a summary on the corresponding Analytics API for solution #x + +- Inputs: per UE-to-UE session performance measurements (application QoS measurements such as latency, channel losses, data rate, jitter) +- List of Data Sources + - Data Source information: VAL UE #1, VAL UE #2 + - Data required from Data Source: application QoS measurements +- Output: Predicted application QoS metric change (downgrade or upgrade) + +### 6.5.3 Solution evaluation + +This solution addresses Key Issue #1 and introduces application layer analytics to predict the performance of an application session among two or more VAL UEs. Such solution enables the VAL layer to pro-actively adapt to predicted application QoS changes for VAL UE-to-UE sessions. + +This solution is technically viable and doesn't introduce any impact on 5GS. + +## 6.6 Solution #5: Service experience to support application performance analytics + +### 6.6.1 Solution description + +This solution addresses the open issues stated in Key Issue #1, specifically on what data to be collected. This solution supplements the existing solution #1 in clause 6.2 with service experience information. + +In some scenarios, where data from Application servers (like VAL server) is not available (overload or any other reasons) or doesn't show the quality of service experience at the UE side, the ADAE server may need to rely on alternate information sources like the application clients (like VAL clients) that provide the visibility on application service status. ADAE server can use this information from the clients alone, for the predictions and share with the consumer of the analytics. This solution supports a mechanism for the ADAE client to send service experience report to the ADAE server. ADAE server upon receiving the service experience information from the UE side entities can use it for predictions of application performance analytics. The service experience information from VAL client may include end-to-end response time, connection bandwidth, request rate, VAL server availability, etc. + +This solution describes three procedures in more detail: + +- Pull service experience information +- Push service experience information +- Service experience information based on triggers configured by ADAE server at ADAE client. + +#### 6.6.1.1 Pull service experience information + +Figure 6.6.1.1-1 illustrates the procedure where the ADAE server pulls the service experience information from the ADAE client. + +![Sequence diagram illustrating the 'Pull service experience information' procedure between an ADAE client and an ADAE server.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +``` +sequenceDiagram + participant ADAE client + participant ADAE server + Note left of ADAE client: 2. Take user consent to send report/feedback + ADAE server->>ADAE client: 1. Pull service experience information request + ADAE client->>ADAE server: 3. Push service experience information request response + Note right of ADAE server: 4. Use service experience information for deriving VAL server performance analytics and notify the analytics consumer +``` + +The diagram shows a sequence of interactions between an ADAE client and an ADAE server. The process begins with the ADAE server sending a '1. Pull service experience information request' to the ADAE client. The ADAE client then performs an internal step, '2. Take user consent to send report/feedback', indicated by a dashed box. Following this, the ADAE client sends a '3. Push service experience information request response' back to the ADAE server. Finally, the ADAE server performs an internal step, '4. Use service experience information for deriving VAL server performance analytics and notify the analytics consumer', also indicated by a dashed box. + +Sequence diagram illustrating the 'Pull service experience information' procedure between an ADAE client and an ADAE server. + +**Figure 6.6.1.1-1: Pull service experience information from UE** + +The procedure can be initiated by the ADAE server upon receiving a service experience from an ADAE client, to fetch service experience information other ADAE clients or upon receiving VAL server performance analytics request from application service provider (application server) or any other event that requires the ADAE server to determine the service experience data. + +1. The ADAE server sends Pull service experience request to the ADAE client. The request contains identity of the specific VAL server and VAL service ID, for which the service experience report is required, as mentioned in Table 6.6.1.1-1. + +**Table 6.6.1.1-1: Pull service experience information request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------| +| VAL server Identity | M | Identity of the VAL server for which the service experience information is requested. | +| VAL service ID | O | Identity of the VAL service. | + +- Upon receiving the Pull service experience request from the ADAE server, the ADAE client may take user consent to send the report if the user consent is not available already. +- The ADAE client sends the Pull service experience response to the ADAE server. The response contains service experience report, as specified in Table 6.6.1.1-2. The ADAE client receives the service experience related information from the VAL client. + +**Table 6.6.1.1-2: Pull service experience information request response** + +| Information element | Status | Description | +|-------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates whether the report is available or not | +| VAL UE ID | M | Identity of the VAL UE | +| VAL service ID (NOTE) | O | Identity of the VAL service. | +| VAL Server Id | M | Identify the VAL server for which the service experience report is sent | +| Timestamp (NOTE) | O | Time stamp of the collected report | +| VAL service experience report (NOTE) | O | Information related to VAL service experience. It may include end-to-end response time, connection bandwidth, request rate, VAL server availability, etc. | +| NOTE: These IEs are included only if the result is success. | | | + +- The ADAE server uses the service experience report for derivation of VAL server performance analytics. + +#### 6.6.1.2 Push service experience information + +Figure 6.6.1.2-1 illustrates the procedure where the ADAE client pushes the service experience information to the ADAE server. + +![Sequence diagram showing the push service experience information flow from ADAE client to ADAE server.](187bba66c887c745c512add37a577c5e_img.jpg) + +``` + +sequenceDiagram + participant ADAE client + participant ADAE server + Note right of ADAE server: 2. Use service experience information further for deriving VAL server performance analytics. + ADAE client->>ADAE server: 1. Push service experience information request + ADAE server-->>ADAE client: 3. Push service experience information response + +``` + +The diagram illustrates a sequence of interactions between an ADAE client and an ADAE server. + 1. The ADAE client sends a 'Push service experience information request' to the ADAE server. + 2. The ADAE server receives the request and performs an internal action: 'Use service experience information further for deriving VAL server performance analytics.' + 3. The ADAE server then sends a 'Push service experience information response' back to the ADAE client. + +Sequence diagram showing the push service experience information flow from ADAE client to ADAE server. + +**Figure 6.6.1.2-1: Push service experience information from UE** + +The ADAE client determines the service experience information based on information received from the VAL client. The service experience information includes application specific performance measurements like end-to-end response time, connection bandwidth, request rate, server availability time, etc. On request VAL client or any other trigger conditions, the ADAE client sends the service experience report about a VAL server to the ADAE server. + +1. The ADAE client sends Push service experience request to the ADAE server. The request contains service experience report about a VAL server and includes the information elements as specified in Table 6.6.1.2-1. + +**Table 6.6.1.2-1: Push service experience information request** + +| Information element | Status | Description | +|-------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL UE ID | M | Identity of the VAL UE | +| VAL service ID | O | Identity of the VAL service. | +| VAL Server Id | M | Identify the VAL server for which the service experience report is sent | +| Timestamp | O | Time stamp of the collected report | +| VAL service experience report | O | Information related to VAL service experience. It may include end-to-end response time, connection bandwidth, request rate, VAL server availability, etc. | + +2. Upon receiving the Push service experience request from the ADAE client, the ADAE server uses the service experience report for derivation of VAL server performance analytics. +3. The ADAE server sends Push service experience response to the ADAE client. + +The ADAE server may take further actions based on the analysis of the report as shared by the ADAE client. A service experience information from certain UEs, can trigger the ADAE server to fetch further service experience information other UEs. Use the service experience information report from other UEs, to determine/predict analytics. + +- If most of the UE side entities report a similar service experience, then it could be the application server problem across globally. +- If only some UEs report a bad service experience, the problem could be localized among a group of UEs. +- If the bad service experience from only a UE, the problem is localized to the UE. + +#### 6.6.1.3 Service experience information based on triggers + +Figure 6.6.1.3-1 illustrates procedure for the ADAE server to configure triggers to the ADAE client to send the service experience report. The procedure can be initiated by the ADAE server upon receiving VAL server performance analytics request from application service provider (application server). + +![Sequence diagram showing the interaction between ADAE client and ADAE server to configure service experience report triggers. The ADAE server sends a 'Configure service experience report trigger request' to the ADAE client. The ADAE client then performs an internal step 'Take user consent to send report/feedback' (indicated by a dashed box). Finally, the ADAE client sends a 'Configure service experience report trigger response' back to the ADAE server.](3b950edb26a62dde5f3c0f41d9983edc_img.jpg) + +``` + +sequenceDiagram + participant ADAE client + participant ADAE server + Note left of ADAE client: 2. Take user consent to send report/feedback + ADAE server->>ADAE client: 1. Configure service experience report trigger request + ADAE client-->>ADAE server: 3. Configure service experience report trigger response + +``` + +Sequence diagram showing the interaction between ADAE client and ADAE server to configure service experience report triggers. The ADAE server sends a 'Configure service experience report trigger request' to the ADAE client. The ADAE client then performs an internal step 'Take user consent to send report/feedback' (indicated by a dashed box). Finally, the ADAE client sends a 'Configure service experience report trigger response' back to the ADAE server. + +**Figure 6.6.1.3-1: Configure service experience report trigger** + +1. The ADAE server sends Configure service experience report trigger request to the ADAE client. The request contains identity of the specific VAL server(s) for which the service experience report is required. The request includes the information elements as specified in Table 6.6.1.3-1. + +**Table 6.6.1.3-1: Configure service experience report trigger request** + +| Information element | Status | Description | +|-------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| VAL Server specific criteria | M | Identify the list of VAL servers for which the service experience report is requested
List of VAL server specific criteria | +| > VAL Server Id | M | Identity of the VAL server | +| > Triggering Criteria | M | Information about the triggers on which the service experience is to be reported for the VAL server | +| Common Triggering criteria | O | Information about the triggers (applicable to all VAL servers) on which the service experience is fetched | +| Service experience measurement to monitor | O | Information about the service experience measurements which needs to be fetched and included in the report. If not present, by default end-to-end response time is measured. | +| Notification Target Address | O | The Notification target address (e.g. URL) where the notifications destined for the ASM Server should be sent to. | + +2. Upon receiving the Configure service experience report trigger request from the ADAE server, the ADAE client stores the triggering criteria for sending service experience report and may take user consent to send the report if the user consent is not available already. +3. The ADAE client sends the Configure service experience report trigger response to the ASM server, indicating the result of the request. + +### 6.6.2 Solution evaluation + +This solution addresses Key Issue #1 and the introduces a mechanism for the ADAE server to use the service experience information from the UE side entities via ADAE clients to determine the application performance analytics. The solution proposes three mechanisms, ADAE server pulls the service experience information from the ADAE, ADAE server pulls the service experience information from ADAE client based on certain triggers configured on the ADAE client by the ADAE server, and ADAE client pushes to ADAE server. + +## 6.7 Solution #6: Support for slice related application data analytics + +### 6.7.1 Solution description + +This solution addresses Key Issue #5. + +This solution introduces application layer analytics to provide insight on the performance of the VAL applications when using a given network slice (from a list of subscribed slices for the VAL customer). Such solution provides an analytics service to a consumer who can be either the VAL server (for helping to identify what slice it will use for its applications) or for other consumers such as SEAL NSCE to support on providing analytics (since NSCE doesn't contain an analytics engine for providing analytics on top of NWDAF/MDAS). + +Figure 6.7.1-1 illustrates the procedure where the VAL server performance analytics are performed based on data collected from the ongoing VAL sessions as well as data from the DN (VAL server, DN database or networking stack at DN). + +Pre-conditions: + +1. ADAEC is connected to ADAES + +![Sequence diagram illustrating ADAES support for slice-related performance analytics. The diagram shows interactions between NWDAF, OAM / NSCE, ADAES, and Consumer (VAL Server, NSCE server).](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant Consumer as Consumer (VAL Server, NSCE server) + participant ADAES + participant OAM_NSCE as OAM / NSCE + participant NWDAF + Note left of ADAES: 3. Subscribe to Data Sources to receive slice information (slice KPI monitoring, slice load analytics) + + Consumer->>ADAES: 1. App analytics subscription request (analytics ID: "slice perf prediction", DNN, target S-NSSAI(s) or NSI(s), area of interest, time of interest) + ADAES-->>Consumer: 2. Subscription Response + ADAES->>OAM_NSCE: 4. PM data (slice KPI monitoring) + ADAES->>NWDAF: 5. slice load analytics (for target S-NSSAI or NSI ID) + Note right of ADAES: 6. Perform VAL server / session performance analytics (based on 6.1.1) when on target slice + Note right of ADAES: 7. Correlate/ Combine Data from 4-6 and derive analytics on the predicted slice perf for VAL application + ADAES->>Consumer: 8. Notification of analytics on slice perf + +``` + +Sequence diagram illustrating ADAES support for slice-related performance analytics. The diagram shows interactions between NWDAF, OAM / NSCE, ADAES, and Consumer (VAL Server, NSCE server). + +**Figure 6.7.1-1: ADAES support for slice-related performance analytics** + +1. The consumer of the ADAES analytics service sends a subscription request to ADAES and provides the analytics event ID e.g. "slice perf prediction", the target S-NSSAI, DNN, NSI ID, the time validity and area of the request, the required confidence level, whether offline and/or online analytics are needed etc. +2. The ADAES sends a subscription response as an ACK to the consumer. +3. The ADAES subscribes to the Data Sources with the respective Data Collection Event ID and the requirement for data collection related to the request slice(s). Such requests can be towards: + - OAM for providing PM data related to the requested slice / NSI. Alternatively, if the interaction to OAM happens via NSCE layer, such subscription can be performed to NSCE (where ADAES is acting as VAL server). + - NWDAF for providing slice related analytics for the given area and time horizon (indicated in step 1). Such analytics can be the slice load level related network data analytics, or the service experience related network data analytics for a given slice +4. The ADAES based on subscription, receives PM data notification from OAM or from NSCE (via OAM APIs or NSCE-S APIs) +5. The ADAES based on subscription, receives the requested NWDAF analytics outputs. Such analytics can be: + +- network slice or NSI statistics or predictions (clause 6.3.3 of TS 23.288) + - per slice instance service experience stats or predictions (clause 6.4.3 of TS 23.288) +6. The ADAES can also provide analytics on the VAL session performance based on Solution #1 procedure 6.1.2 and filters the analytics only for the sessions which are connected to that requested slice for the area of interest. + 7. The ADAES abstracts or correlates the data/analytics from steps 4-6 and provides analytics on the slice or NSI performance for the the target VAL application/server. For example, such analytics can be about the min/average/max predicted RTT / end to end latency for the VAL application/server if this server uses a given slice/NSI (or for a list of given slices) within an area of interest. + 8. The ADAES sends the analytics to the consumer. + +### 6.7.2 Corresponding Analytics API + +This subclause provides a summary on the corresponding Analytics API for solution #x + +- Inputs: per slice measurements and analytics, application session performance analytics, historical data on slice information +- List of Data Sources: + - Data Source #1 information: OAM or NSCE + - Data required from Data Source #1: PM data for a given NSI + - Data Source #2 information: NWDAF + - Data required from Data Source #2: slice load analytics for NSI/S-NSSAI, service experience for NSI/S-NSSAI + - Data Source #3 information: VAL UEs (based on Solution #1) + - Data required from Data Source #3: application QoS measurements for an application session connected to requested slice +- Output: Statistics or prediction for the VAL application QoS for one or more requested S-NSSAIs/NSIs + +### 6.7.3 Solution evaluation + +This solution introduces application layer analytics to provide insight on the performance of the VAL applications when using a given network slice (from a list of subscribed slices for the VAL customer). This solution is technically viable and does not have any dependency to other slice related analytics since it targets the application performance for a target slice or NSI and not the network slice related performance. + +## 6.8 Solution #7: Slice configuration recommendation + +### 6.8.1 Solution description + +This solution addresses Key Issue #6. + +This solution provides a procedure for network slice configuration recommendation based on collected network slice performance and analytics and historical network slice status and network performance. The consumer can be either the VAL server or other consumers such as SEAL NSCE. + +Figure 6.8.1-1 illustrates the procedure for network slice configuration recommendation. + +Pre-conditions: + +1. The ADAES is registered and capable of interacting with 5GS to collect network slice data. + +2. The ADAES is registered and capable of interacting with NSCE to collect network slice performance and analytic. + +![Sequence diagram illustrating ADAES support for network slice configuration recommendation. The diagram shows interactions between NWDAF, OAM, NSCE, ADAES, Consumer, and Data repository. The ADAES sends a subscription request to the Consumer, receives a response, and then subscribes to data sources. It receives performance and analytics data from NSCE, PM data from OAM, and slice load analytics from NWDAF. The ADAES then combines/corrects data, performs storage and analysis, derives a recommendation, and sends a notification to the Consumer.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +``` + +sequenceDiagram + participant Consumer + participant ADAES + participant Data repository + participant NSCE + participant OAM + participant NWDAF + + Note right of ADAES: 1.Slice configuration recommendation Subscription request + ADAES->>Consumer: 1.Slice configuration recommendation Subscription request + Note right of Consumer: 2.Slice configuration recommendation Subscription response + Consumer-->>ADAES: 2.Slice configuration recommendation Subscription response + Note right of ADAES: 3.subscribes to the Data Sources + ADAES->>NSCE: 3.subscribes to the Data Sources + Note right of NSCE: 4. Performance and analytics of network slice + NSCE-->>ADAES: 4. Performance and analytics of network slice + Note right of OAM: 5. PM data + OAM-->>ADAES: 5. PM data + Note right of NWDAF: 6.slice load analytics + NWDAF-->>ADAES: 6.slice load analytics + Note right of ADAES: 7.Combine/Correction data from step 3-5 + ADAES->>Data repository: 7.Combine/Correction data from step 3-5 + Note right of ADAES: 8. Data storage and analysis + ADAES->>Data repository: 8. Data storage and analysis + Note right of ADAES: 9. Derive the recommendation + ADAES->>Data repository: 9. Derive the recommendation + Note right of ADAES: 10.Slice configuration recommendation notify + ADAES->>Consumer: 10.Slice configuration recommendation notify + +``` + +Sequence diagram illustrating ADAES support for network slice configuration recommendation. The diagram shows interactions between NWDAF, OAM, NSCE, ADAES, Consumer, and Data repository. The ADAES sends a subscription request to the Consumer, receives a response, and then subscribes to data sources. It receives performance and analytics data from NSCE, PM data from OAM, and slice load analytics from NWDAF. The ADAES then combines/corrects data, performs storage and analysis, derives a recommendation, and sends a notification to the Consumer. + +**Figure 6.8.1-1: ADAES support for network slice configuration recommendation** + +1. The consumer of the ADAES sends a subscription request to ADAES and provides the target S-NSSAI, DNN, slice requirement, area of the interest, interest time period of the historical data (e.g. last year), the required confidence level, whether offline and/or online analytic are needed etc. +2. The ADAES sends a subscription response to the consumer. +3. The ADAES subscribes to the Data Sources with the respective Data Collection Event ID and the requirement for data collection related to the request slice(s). Such requests can be sent to SEAL NSCE, OAM, NWDAF or the combination of them. +4. Based on subscription, the ADAES (acting as VAL server) may receive performance and analytics data from SEAL NSCE (e.g. QoE metrics, as defined in the TS 23.435 clause 9.4.2). +5. Based on subscription, the ADAES may receive Network slice / NSI related performance data from OAM as defined in TS 28.552 [12]. +6. Based on subscription, the ADAES may receive Network slice related Observed Service experience statistics, Load level information of a Network Slice defined from NWDAF as defined in TS 23.288[18] +7. If the data is collected from multiple sources, the ADAES combines or correlates the data/analytics from steps 3-5, and stores the data into data repository if needed. +8. Collect the historical data from data repository and analyze the network slice usage pattern. When the amount of stored historical data does not cover the required interest time period of the historical data, ADAES analyze the slice usage pattern based on the existing stored historical data. +9. The ADAES provides network slice configuration recommendation based on the slice requirement, slice performance and derived slice usage pattern from step 8. +10. The ADAES sends the network slice configuration recommendation to the consumer. The recommendation may be related to parameters in the slice serviceProfile if the consumer is the SEAL NSCE. Or the recommendation + +may be related to slice resource /functional configuration (e.g. slice capacity, coverage) if the consumer is the management system. + +### 6.8.2 Corresponding Analytics API + +This subclause provides a summary on the corresponding Analytics API for solution #7 + +- Inputs: per slice measurements and analytics, historical data on slice information +- List of Data Sources: + - Data Source #1 information: SEAL NSCE + - Data required from Data Source #1: performance and analytics data for a given S-NSSAI + - Data Source #2 information: OAM + - Data required from Data Source #2: PM data for a given S-NSSAI + - Data Source #3 information: NWDAF + - Data required from Data Source #3: slice load analytics for S-NSSAI, service experience for S-NSSAI + - Data Source #4 information: A-ADRF + - Data required from Data Source #4: historical slice load analytics and service experience for S-NSSAI. +- Output: Statistics for the network slice configuration recommendation for one or more requested S-NSSAIs. The recommendation may be related to parameters in the slice serviceProfile per S-NSSAI if the consumer is the SEAL NSCE. Or the recommendation may be related to slice resource /functional configuration per S-NSSAI / NSI (e.g. slice capacity, coverage) if the consumer is the management system. + +### 6.8.3 Solution evaluation + +This solution is technically viable and does not have any dependency to other slice related analytics since it targets the slice configuration recommendation for a target S-NSSAI. + +## 6.9 Solution #8: support for location accuracy analytics + +### 6.9.1 Solution description + +This solution addresses Key Issue #7. + +This solution introduces application layer analytics to allow a VAL server to be notified based on analytics whether the accuracy of a location can be met for a given application and optionally for a given UE/group route. For example, a VAL server may request the ADAE server to provide analytics whether the accuracy of a location for the UEs within a VAL application is predicted to be sustainable or is expected to downgrade in a specific area or for an expected route from location A to location B. + +Figure 6.9.1-1 illustrates the procedure for location accuracy analytics enablement solution. + +Pre-conditions: + +1. ADAES is connected to A-ADRF +2. ADAES has discovered SEAL LMS or FLS + +![Sequence diagram illustrating the Location accuracy analytics procedure. The diagram shows interactions between five entities: A-ADRF, NWDAF, SEAL LMS / FLS, ADAE server, and VAL server. The sequence starts with the VAL server sending an 'App analytics subscription request' to the ADAE server. The ADAE server responds with a 'Subscription Response'. Next, the ADAE server sends a 'Discover Data Sources' message to the SEAL LMS / FLS. The SEAL LMS / FLS then sends 'Subscribe for UE mobility related analytics' (4a) and 'UE mobility / location analytics notify' (4b) to the NWDAF. The NWDAF sends 'Request (fused) location reports' (5a) and '(fused) location reports and achieved accuracies' (5b) to the SEAL LMS / FLS. The SEAL LMS / FLS sends 'req/receive historical data/stats on location' (6) to the A-ADRF. Finally, the SEAL LMS / FLS sends a 'Derive vertical/horizontal location accuracy analytics' message (7) to the ADAE server, which then sends a 'Notification of analytics for location accuracy' (8) to the VAL server.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant ADAE server + participant SEAL LMS / FLS + participant NWDAF + participant A-ADRF + + Note right of VAL server: 1. App analytics subscription request +(analytics ID: "location accuracy analytics", VAL +service ID or VAL UE ID, area of interest or +waypoints, time of interest) + VAL server->>ADAE server: 1. App analytics subscription request + Note right of ADAE server: 2. Subscription Response + ADAE server->>VAL server: 2. Subscription Response + Note right of ADAE server: 3. Discover Data Sources (NWDAF and SEAL +LMS/FLS) for collecting location data/analytics +for the VAL UEs within the VAL service + ADAE server->>SEAL LMS / FLS: 3. Discover Data Sources + Note right of SEAL LMS / FLS: 4a. Subscribe for UE mobility related analytics +(for each VAL UE or for a set of waypoints) + SEAL LMS / FLS->>NWDAF: 4a. Subscribe for UE mobility related analytics + Note right of SEAL LMS / FLS: 4b. UE mobility / location analytics notify +(for each VAL UE or for a set of waypoints) + SEAL LMS / FLS->>NWDAF: 4b. UE mobility / location analytics notify + Note right of SEAL LMS / FLS: 5a. Request (fused) location reports for the +given area or list of VAL UEs + SEAL LMS / FLS->>NWDAF: 5a. Request (fused) location reports + Note right of SEAL LMS / FLS: 5b. (fused) location reports and achieved +accuracies for list of VAL UEs + SEAL LMS / FLS->>NWDAF: 5b. (fused) location reports + Note right of SEAL LMS / FLS: 6. req/receive historical data/stats on location +accuracy for the given area + SEAL LMS / FLS->>A-ADRF: 6. req/receive historical data/stats + Note right of SEAL LMS / FLS: 7. Derive vertical/horizontal +location accuracy analytics for VAL +service or for the given area or set +of waypoints + SEAL LMS / FLS->>ADAE server: 7. Derive vertical/horizontal + Note right of ADAE server: 8. Notification of analytics for +location accuracy + ADAE server->>VAL server: 8. Notification of analytics + +``` + +Sequence diagram illustrating the Location accuracy analytics procedure. The diagram shows interactions between five entities: A-ADRF, NWDAF, SEAL LMS / FLS, ADAE server, and VAL server. The sequence starts with the VAL server sending an 'App analytics subscription request' to the ADAE server. The ADAE server responds with a 'Subscription Response'. Next, the ADAE server sends a 'Discover Data Sources' message to the SEAL LMS / FLS. The SEAL LMS / FLS then sends 'Subscribe for UE mobility related analytics' (4a) and 'UE mobility / location analytics notify' (4b) to the NWDAF. The NWDAF sends 'Request (fused) location reports' (5a) and '(fused) location reports and achieved accuracies' (5b) to the SEAL LMS / FLS. The SEAL LMS / FLS sends 'req/receive historical data/stats on location' (6) to the A-ADRF. Finally, the SEAL LMS / FLS sends a 'Derive vertical/horizontal location accuracy analytics' message (7) to the ADAE server, which then sends a 'Notification of analytics for location accuracy' (8) to the VAL server. + +Figure 6.9.1 -1: Location accuracy analytics procedure + +1. The VAL server makes a request to ADAE server for location accuracy prediction/stats, including an analytics event ID (e.g. "location accuracy prediction" or "location accuracy sustainability"), an analytics request type (if not identified specifically at the event ID) which can be the location accuracy prediction for a given location X and/or for a given UE/app. The request may include also the target area, a target VAL application, or a VAL UE, group of UEs or the VAL service, time of day, accuracy threshold and requirements. If the VAL UEs are provided by the VAL server, this request may also include the expected route or a set of waypoints for the UEs of the VAL application. +2. The ADAE server sends a subscription response as an ACK to the VAL server. +3. The ADAE server discovers and maps the Data Sources with the respective analytics event ID for collecting location data for the corresponding VAL UEs or VAL service or area. +- 4a/4b. The ADAE server subscribes for NWDAF UE mobility analytics per VAL UE (for all the VAL UEs) and gets notification on the per UE location/mobility analytics based on TS 23.288 clause 6.7.2. Such analytics may be requested for a list of waypoints per UE route (if indicated at step 1). +- 5a/5b. The ADAE server requests and receives from SEAL LMS location reports for the respective VAL UEs or location reports from all VAL UEs within the requested area. Such request may also indicate the required location accuracy (requires enhancements to SEAL LMS procedures). In case where FLS is deployed, it can be also possible to request and receive fused location reports (combined location reports from 3gpp/n3gpp sources) if the ADAE server identifies that higher location accuracy is required. +6. The ADAE server may also request and receive location accuracy historical analytics /data from A-ADRF for the corresponding VAL UEs or VAL service area. +7. The ADAE server abstracts or correlates the data/analytics from steps 4-6 and provides analytics on the location accuracy for the the target VAL application. Depending on the event ID in step 1, the ADAE server can indicate + +whether the location accuracy is sustainable or is predicted to be downgraded or can be upgraded and become more granular (e.g. from meter to decimetre). + +8. The ADAE server sends the analytics to the consumer. + +### 6.9.2 Corresponding Analytics API + +This subclause provides a summary on the corresponding Analytics API for solution #8 + +- Inputs: per VAL UE or area location reports and UE mobility analytics +- List of Data Sources: + - Data Source #1 information: NWDAF (Nnwdaf\_AnalyticsInfo service via N33, as specified in TS 23.288 [2]) + - Data required from Data Source #1: UE mobility analytics + - Data Source #2 information: SEAL LMS (SS\_LocationMonitoring API, SS\_LocationAreaMonitoring API as specified in TS 23.434 [5]) + - Data required from Data Source #2: UE location reports and achieved accuracy, Location reports from all UEs within a given area + - Data Source #3 information: FLF + - Data required from Data Source #3: fused location reports per VAL UE (via FLS-2 as discussed in TR 23.700-96 [8]) + - Data Source #4 information: A-ADRF + - Data required from Data Source #4: historical location accuracy statistics for target VAL service area or VAL UE +- Output: a predictive location accuracy sustainability or change indication, a predictive location accuracy sustainability or change indication for a route of the UE with the application. + +### 6.9.3 Solution evaluation + +This solution addresses Key Issue #7 and introduces location accuracy analytics to predict possible downgrade of location accuracy for a given VAL application. Such solution enables the VAL layer to pro-actively adapt to predicted location accuracy changes for the VAL service (e.g. to change the distance between VAL UEs or trigger the change of VAL UE speed if location accuracy is changed). + +This solution is technically viable and doesn't introduce any impact on 5GS. This solution requires enhancements to SEAL LMS and to FLS for reporting the accuracy as part of the location reporting. + +## 6.10 Solution #9: support for service API analytics + +### 6.10.1 Solution description + +This solution addresses Key Issue #8. + +This solution introduces service API analytics to allow a VAL server or any other consumer (e.g. API provider) to be notified on the predicted /statistic availability and service level for the requested service API analytics. Such analytics may allow the API provider to perform actions to avoid service API invocation failures or other actions like throttling/rate limitations. Also, such analytics will support the VAL server to identify if/when to perform an API invocation request based on the API expected status at the given area and time horizon. + +Figure 6.10.1-1 illustrates the procedure for service API analytics enablement solution. + +Pre-conditions: + +1. ADAES is registered to CCF + +![Sequence diagram illustrating the Service API analytics procedure. The participants are A-ADRF, ADAE server, CAPIF / CCF, and Subscriber / API Invoker. The sequence of messages is: 1. Event subscription request from Subscriber to ADAE server; 2. Check authorization for subscription and store subscription info (internal ADAE server step); 3. Event subscription response from ADAE server to Subscriber; 4. request / subscribe for logs report for all service API invocations for target API(s) from ADAE server to CAPIF / CCF; 5. API invocation logs resp/report from CAPIF / CCF to ADAE server; 6. req/receive historical data/stats on service APIs from ADAE server to A-ADRF; 7. Authorize and anonymize invoker's info / derive service API analytics (internal ADAE server step); 8. service API event notification from ADAE server to Subscriber.](036ceaf207a7b289ca76e160892eb724_img.jpg) + +``` + +sequenceDiagram + participant A-ADRF + participant ADAE server + participant CAPIF / CCF + participant Subscriber / API Invoker + + Note right of ADAE server: 2. Check authorization for subscription and store subscription info + Note right of CAPIF / CCF: Fetch API logs + Note right of ADAE server: 7. Authorize and anonymize invoker's info / derive service API analytics + + Subscriber / API Invoker->>ADAE server: 1. Event subscription request (Event ID: Service API analytics on availability and service level) + ADAE server-->>ADAE server: 2. Check authorization for subscription and store subscription info + ADAE server-->>Subscriber / API Invoker: 3. Event subscription response + ADAE server->>CAPIF / CCF: 4. request / subscribe for logs report for all service API invocations for target API(s) + CAPIF / CCF-->>ADAE server: 5. API invocation logs resp/report + ADAE server->>A-ADRF: 6. req/receive historical data/stats on service APIs + ADAE server-->>ADAE server: 7. Authorize and anonymize invoker's info / derive service API analytics + ADAE server-->>Subscriber / API Invoker: 8. service API event notification (Event ID, Service API analytics, ..) + +``` + +Sequence diagram illustrating the Service API analytics procedure. The participants are A-ADRF, ADAE server, CAPIF / CCF, and Subscriber / API Invoker. The sequence of messages is: 1. Event subscription request from Subscriber to ADAE server; 2. Check authorization for subscription and store subscription info (internal ADAE server step); 3. Event subscription response from ADAE server to Subscriber; 4. request / subscribe for logs report for all service API invocations for target API(s) from ADAE server to CAPIF / CCF; 5. API invocation logs resp/report from CAPIF / CCF to ADAE server; 6. req/receive historical data/stats on service APIs from ADAE server to A-ADRF; 7. Authorize and anonymize invoker's info / derive service API analytics (internal ADAE server step); 8. service API event notification from ADAE server to Subscriber. + +Figure 6.10.1 -1: Service API analytics procedure + +1. The subscribing entity (CAPIF entity, VAL server / API invoker, API provider) sends an event subscription request to the ADAE server to receive analytics for one or more service APIs. The event subscription request includes the information elements as specified in Table 6.10.1-1 + +Table 6.10.1-1: Event subscription request + +| Information element | Status | Description | +|------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Identity information | M | The information to determine the identity of the subscribing entity | +| Service API information | M | The service API name or type | +| Analytics event ID and criteria | M | The event criteria include event type information relevant to the prediction or stats on the number of failure API invocations, API availability, frequency and occurrence of API version changes, API location changes for the target API, etc | +| Time Validity and horizon | O | Time validity of the request and time horizon for the predictions | +| Area of interest | O | Geographical or topological area for which the subscription applies | +| Notification reception information | O | The information of the subscribing entity for receiving the notifications for the event. | + +2. Upon receiving the event subscription request from the subscribing entity, the ADAE server checks for the relevant authorization for the event subscription. If the authorization is successful, the ADAE server stores the subscription information. +3. The ADAE server sends an event subscription response indicating successful subscription +4. Upon sending the subscription response, the ADAE server requests to collect API logs to be used to derive analytics and triggers API invocation log pull request towards the CAPIF core function. The API invocation log fetch request indicates the API (or list of APIs) for which logs are required. Based on the ADAE server + +deployment, this can be performed via CAPIF\_Logging\_API\_Invocation API as specified in 3GPP TS 23.222 [9]. The message may include the IEs as specified in Table 6.10.1-2. + +**Table 6.10.1-2: API invocation log fetch request** + +| Information element | Status | Description | +|--------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------| +| Service API log requestor information | M | Identity information of the originated application querying service API log request | +| ADAES ID / Security credentials | M | Identity information of the ADAES | +| Service ID or UE ID | M | Identity of the application service or UE for which the API invocations apply | +| Target API information / List of API information | M | Information on target API or list of target APIs | +| >Query information | O | List of query filters such as invoker's ID and IP address, service API name and version, input parameters, and invocation result | +| > API aggregation abstraction flag | O | What type of aggregation or abstraction/filtering needs to be applied | +| Reporting format configuration | O | The logs reporting configuration (frequency, periodicity etc) | +| Area of validity | O | The geographical area for which the request applies | +| Time or validity | O | The time of validity for the request | +| Exposure level requirement | O | The level of exposure requirement (e.g. permissions on the logs like read/write/delete..) for the logs to be exposed | + +- The CCF authorizes the request and fetches the API logs from the storage unit. CCF then sends the requested information to the ADAE server via a API invocation log fetch response message. The message may include the IEs as specified in Table 6.10.1-3. + +**Table 6.10.1-3: API invocation log fetch response** + +| Information element | Status | Description | +|--------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Identity information of the originated application querying service API log request | +| Service ID or UE ID | M | Identity of the application service or UE for which the API invocations apply | +| Target API information / List of API information | M | Information on target API or list of target APIs | +| >API Logs Collection Event | O | The API logs based on the subscription event. This includes for example the number of failure API invocations, API availability, frequency and occurrence of API version changes, API location changes for the target API, API throttling events, number of API invocations for a given area and time etc | +| > reporting info | O | The time and area for which the reporting applies | + +- The ADAES may also request and receive service API historical analytics /data from A-ADRF for the corresponding service APIs. +- The ADAE server authorizes and anonymizes the API logs (if not performed by CCF) and abstracts based on exposure level. The exposure level can be known based on pre-configuration by the OAM or based on the subscription and type of invoker. The ADAE server then derives analytics on the target service API(s) based on the logs received from the CCF. Such analytics are predictions/stats for the API status based on the analytics event. +- The ADAE server sends the analytics as event notifications to all the subscribing entities that have subscribed for the event matching the criteria. If a notification reception information is available as part of the subscribing entity event subscription, then the notification reception information is used by the ADAE server to send event notifications to the subscribing entity. + +The notification includes the following parameters: the analytics event ID, the service API name and/or type, stats or predictions based on abstracted or anonymized API logs (for example number of failure API invocations, API availability, frequency and occurrence of API version changes, API location changes for the target API, API throttling events, number of API invocations for a given area and time, API load statistics for a given edge network, etc), the time and area where the reporting occurs and is valid. + +### 6.10.2 Corresponding Analytics API + +This subclause provides a summary on the corresponding Analytics API for solution #9. + +- Inputs: service API logs +- List of Data Sources: + - Data Source #1 information: CAPIF CCF (via CAPIF\_Logging\_API\_Invocation API) + - Data required from Data Source #1: Service API logs for requested APIs + - Data Source #2 information: A-ADRF + - Data required from Data Source #2: historical data / statistics on service API availability and service level +- Output: stats or predictions for service API(s). For example, the failure rate of API invocations, API predicted availability, frequency and occurrence of API version changes, API location changes for the target API, API throttling events, number of API invocations for a given area and time, API load statistics for a given edge data network (for edge provided service APIs). + +### 6.10.3 Solution evaluation + +This solution addresses Key Issue #8 and introduces service API analytics to provide stats or predict possible downgrade of performance and availability of a service API. This solution is technically viable and doesn't introduce any impact on 5GS. + +# --- 7 Deployment scenarios + +## 7.1 General + +This clause provides the different deployment models for ADAE services. There could be three deployment options: + +- ADAES can be deployed at a centralized cloud platform, and collects data from multiple EDNs +- ADAES can be deployed at the edge platform +- Hierarchical ADAES deployment, where multiple ADAE services are deployed in edge or central clouds (e.g. in hierarchical arch). Such deployment allows for local-global analytics for system wide optimization + +## 7.2 Deployment model #1: Cloud-deployed ADAES + +In this deployment, as shown in Figure 7.2-1, the ADAES is centrally located and can provide analytics services to the application and edge services (EAS/EES, VAL server, SEAL services). + +The statistics/predictions that the ADAES provides are applicable to the ADAE server service area, which can be provided for the entire PLMN. + +![Figure 7.2-1: cloud deployed ADAES diagram](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +This diagram illustrates the cloud-deployed ADAES architecture. At the top, three vertical dashed boxes represent different network domains: EDN A1, EDN A2, and Centralized DN (DNN-B). EDN A1 and EDN A2 each contain a stack of 'EAS' (Edge Application Server) boxes and a single 'EES' (Edge Enriched Server) box. Centralized DN (DNN-B) contains a 'VAL server' and a 'SEAL services' box, which in turn contains a green 'ADAE server'. Below these domains is a horizontal bar representing the 'PLMN' (Packet Core Network). Within the PLMN, there are four DNAI (Data Network Access Identifier) labels: 'DNAI A1-m', 'DNAI A1-n', 'DNAI A2-n', and 'DNAI B'. Blue ovals connect the EES boxes in EDN A1 and EDN A2 to DNAI A1-m and DNAI A1-n respectively. Another blue oval connects the 'ADAE server' in Centralized DN (DNN-B) to DNAI B. + +Figure 7.2-1: cloud deployed ADAES diagram + +Figure 7.2-1 cloud deployed ADAES + +## 7.3 Deployment model #2 Edge-deployed ADAES + +In this deployment, as shown in Figure 7.3-1, the ADAES is located at the EDN and provides analytics services to the EAS or other edge native applications at the edge platform. ADAES can be deployed by the ECSP or the MNO to provide analytics for the application or edge parameters. + +The statistics/predictions that the edge deployed ADAES are applicable to the ADAE server service areas (as shown in the example in Fig 7.2-2), which are equivalent to the EDN service areas. Such analytics can be about the edge load or the EAS performance and can be provided to consumers within EDN. + +In this deployment the interaction between edge deployed ADAES is possible for exchanging edge/application analytics for application mobility scenarios or for cases when ADAES #1 and #2 service areas have overlapping coverage. + +![Figure 7.3-1: edge deployed ADAES diagram](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +This diagram illustrates the edge-deployed ADAES architecture. Similar to Figure 7.2-1, it shows three vertical dashed boxes for EDN A1, EDN A2, and Centralized DN (DNN-B) at the top, and a 'PLMN' bar at the bottom with DNAI labels 'DNAI A1-m', 'DNAI A1-n', 'DNAI A2-n', and 'DNAI B'. In this model, the 'ADAE server' is deployed directly within the edge domains: 'ADAE server #1' is in EDN A1 and 'ADAE server #2' is in EDN A2. Each EDN also contains 'EAS' and 'EES' boxes. Centralized DN (DNN-B) contains a 'VAL server' and 'SEAL services' box. Below the PLMN bar, two ovals represent service areas: 'ADAEs #1- service area' covering DNAI A1-m and DNAI A1-n, and 'ADAEs #2- service area' covering DNAI A2-n. Blue ovals connect the 'ADAE server #1' to the first service area and 'ADAE server #2' to the second service area. + +Figure 7.3-1: edge deployed ADAES diagram + +Figure 7.3-1 edge deployed ADAES + +## 7.4 Deployment model #3: Hierarchical ADAES deployment + +In this deployment, multiple ADAESs can be located at different EDNs/DNs and can be deployed by the same ADAE provider. Such hierarchical deployments allow the local – global analytics derivation (which may be needed for improving the analytics confidence level). The centrally deployed ADAES can also act as ADAE analytics aggregator entity and configures the edge deployed ADAES to derive analytics on different sub-areas. + +One example is the use of analytics for the EDN#1 or EDN#2 load which will help predicting the VAL server performance at a centrally located ADAES. Such deployment is also applicable for ML-based analytics methods, like supervised learning, where the centrally located ADAES acts as ML model training entity, and the edge located ADAESs can act as ML model inference entities (using edge data to improve the prediction accuracy). + +The statistics/predictions that the edge deployed ADAES correspond to the ADAE server service areas (as shown in the example in Fig 7.4-1), which is equivalent to the EDN service areas. The central ADAE server covers all PLMN area and is used to coordinate or jointly perform analytics with the distributed ADAES. Such analytics services can be provided to consumers at the central DN, like the VAL servers or SEAL services or even at the PLMN side (e.g. NWDAF consuming service experience analytics). + +![Diagram illustrating the hierarchical deployment of ADAES. It shows three main entities: EDN A1, EDN A2, and Centralized DN (DNN-B). EDN A1 and EDN A2 each contain an EAS (Edge Analytics Server), EES (Edge Enrichment Server), and an ADAE server (ADAE server #1.1 and ADAE server #1.2 respectively). Centralized DN (DNN-B) contains a VAL server, SEAL services, and an ADAE server (ADAE server #1). All three entities are connected to a common PLMN (Packet Core Network) via DNAIs (DNAI A1-m, DNAI A1-n, DNAI A2-n, and DNAI B). The ADAE servers are associated with service areas: ADAE 1.1- service area for EDN A1, ADAE 1.2- service area for EDN A2, and the PLMN area for the Centralized DN.](396197257cf9437b526bb6585b6a9c8a_img.jpg) + +Diagram illustrating the hierarchical deployment of ADAES. It shows three main entities: EDN A1, EDN A2, and Centralized DN (DNN-B). EDN A1 and EDN A2 each contain an EAS (Edge Analytics Server), EES (Edge Enrichment Server), and an ADAE server (ADAE server #1.1 and ADAE server #1.2 respectively). Centralized DN (DNN-B) contains a VAL server, SEAL services, and an ADAE server (ADAE server #1). All three entities are connected to a common PLMN (Packet Core Network) via DNAIs (DNAI A1-m, DNAI A1-n, DNAI A2-n, and DNAI B). The ADAE servers are associated with service areas: ADAE 1.1- service area for EDN A1, ADAE 1.2- service area for EDN A2, and the PLMN area for the Centralized DN. + +Figure 7.4-1 hierarchical deployment of ADAES + +# 8 Overall evaluation + +## 8.1 General + +The following clauses contain an overall evaluation of the solutions presented in this technical report, their applicability to the identified key issues and possible dependencies to other groups. This clause also includes a summary of the inputs/outputs and corresponding analytics APIs to be considered for the normative phase. + +## 8.2 Solution evaluations + +### 8.2.1 General + +All the key issues and solutions specified in this technical report are listed in Table 8.2.1-1. This table includes the mapping of the key issues to the solutions and corresponding solution evaluations. + +Table 8.2.1-1 Key issue and solutions + +| Key issues | Solution | Dependency on other working groups | +|---------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------| +| Key issue #1: Support for application performance analytics | Solution #1: Support for application performance analytics | | +| | Solution #2: Data Analytics Enablement | | +| | Solution #4: Support for performance analytics for UE-to-UE sessions | | +| | Solution #5: Service experience to support application performance analytics | | +| Key issue #2: Support for edge analytics enablement | Solution #2: Data Analytics Enablement | | +| | Solution #3: Support for edge load analytics | | +| Key issue #3: Support for data collection for application layer analytics | Solution #2: Data Analytics Enablement | | +| Key issue #4: Key Issue on interactions with SEAL services | Solution #2: Data Analytics Enablement | | +| | Solution #6: Support for slice related application data analytics | | +| | Solution #7: Slice configuration recommendation | | +| | Solution #8: Location accuracy analytics | | +| Key issue #5: Support for slice-related application data analytics | Solution #6: Support for slice related application data analytics | | +| Key issue #6: Support for slice configuration recommendation enablement | Solution #7: Slice configuration recommendation | | +| Key issue #7: support for location accuracy analytics | Solution #8: Location accuracy analytics | | +| Key issue #8: Support for service API capability analytics | Solution #9 : Service API analytics | | + +More specifically, + +- For Key issue #1 (Support for application performance analytics), Solution #1 and Solution #4 provide analytics capabilities for application performance targeting the UE-to-network and UE-to-UE sessions respectively. Solution #2 provides a generic mechanism which can be used for data analytics enablement and can be adopted by Solutions #1 and #4; whereas Solution #5 provides methods for collecting/notifying service experience data from the UE and can be seen as further elaboration of the collection/notification means based on Solution #1. There is no identified conflict among the solutions, and the solutions can complement each other. +- For Key issue #2 (Support for edge analytics enablement), Solution #3 provides analytics functionality for edge load, whereas Solution #2 provides a generic mechanism which can be used for edge load analytics enablement and can be adopted by Solution #3 (whereas it is not mandatory). Solution #2 may require enhancements in eEDGEAPP to allow the collection of the EES load information. +- For Key issue #3 (Support for data collection for application layer analytics), Solution #2 provides a generic mechanism for data collection enablement to be used for ADAE analytics derivation. +- For Key issue #4 (Key Issue on interactions with SEAL services), solutions #2, #6, #7, #8 have interactions with other SEAL services. Solution #2 provides a generic mechanism for data collection enablement to be used for ADAE analytics derivation. Additionally, Solution #6 and #7 interact with SEAL NSCE server for analytics derivation. Finally Solution #8 collects location reports from SEAL LMS and may require location enhancements of SEAL LMS. There is no identified conflict among the solutions, and the solutions can complement each other. +- For Key issue #5 (Support for slice-related application data analytics), Solution #6 provides slice-related application analytics and is optionally interacting with SEAL NSCE service (no enhancements are needed at SEAL NSCE). +- For Key issue #6 (Support for slice configuration recommendation enablement), Solution #7 provides a support capability for slice configuration recommendation and is interacting with SEAL NSCE service (no enhancements are needed at SEAL NSCE). + +- For Key issue #7 (support for location accuracy), Solution #8 provides location accuracy analytics functionality and is optionally interacting with SEAL LMS or FLF service (enhancements are needed at SEAL LMS if used as data source). +- For Key issue #8 (Support for service API capability analytics), Solution #9 provides a support capability for service API analytics. + +### 8.2.2 ADAE analytics services + +Table 8.2.2-1 provides an overview of the analytics services which are provided by ADAE layer, based on the individual solutions. + +**Table 8.2.2-1 ADAE analytics services** + +| Analytics Event | Solution | Inputs | Data Collection Sources | Analytics Outputs | Type of analytics | +|--------------------------------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|-----------------------------------------------------------------|--------------------------| +| VAL server performance analytics | Sol #1, Sol #5 | per VAL server performance measurements, historical data/stats for VAL server performance, network / KPI monitoring from 5GS | 1. VAL UE
2. VAL Server
3. OAM
4. 5GC (NWDAF, NEF) | Analytics on application QoS metrics per VAL server | Prediction, statistics | +| VAL UE/session performance analytics | Sol #1, Sol #5 | per VAL session performance measurements | 1. VAL UE
2. VAL Server | Analytics on application QoS metrics per VAL session | Prediction | +| VAL UE-to-UE session performance analytics | Sol #4 | per UE-to-UE session performance measurements | 1. VAL UEs | Analytics on application QoS metric change for UE-to-UE session | Prediction | + +| | | | | | | +|-------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| +| edge load analytics | Sol #3 | edge platform load data, EAS/EES load data, DN performance analytics, UPF load analytics | 1. OAM / MDAS
2. 5GC / NWDAF
3. SEALDD server
4. EES
5. EAS
5. MEP / RNIS | 1. stats / predictions on the EDN load conditions,
2. EES or EAS load stats/predictions, 3. recommendation for pro-active EAS relocation trigger | Prediction, statistics | +| Slice related performance analytics | Sol #6 | per slice measurements and analytics, application session performance analytics, historical data on slice information | 1. OAM or NSCE
2. 5GC / NWDAF
3. VAL UEs | Statistics / prediction for the VAL application QoS for one or more requested S-NSSAIs/NSIs | Prediction, statistics | +| Location accuracy analytics | Sol #8 | UE mobility analytics, UE location reports and achieved accuracy, historical location accuracy statistics for target VAL service area or VAL UE | 1. SEAL LMS / FLS
2. 5GC / NWDAF
3. A-ADRF | a predictive location accuracy sustainability or change indication | Prediction | +| Service API analytics | Sol #9 | Service API logs for requested APIs, historical data / statistics on service API availability and service level | 1. CCF
2. A-ADRF | stats / predictions for service API(s) | Prediction, statistics | +| Slice configuration recommendation | Sol #7 | per slice measurements and analytics, historical data on slice information | 1. SEAL NSCE
2. OAM
3. NWDAF
4. A-ADRF | Statistics for the network slice configuration recommendation for one or more requested S-NSSAIs | Statistics | + +# 9 Conclusions + +## 9.1 General conclusions + +This technical report fulfills the objectives of the study on application architecture for enabling application data analytics. The report includes the following: + +1. Definition of terms and abbreviations used in the study (clause 3); +2. Key issues identified by the study (clause 4); +3. Architectural requirements and detailed application architecture for enabling Application Data Analytics (clause 5); +4. Individual solutions addressing the key issues (clause 6); +5. Deployment scenarios (clause 7); and +6. Overall evaluations of all the solutions (clause 8); + +## 9.2 General conclusions for normative work + +For normative work in 3GPP Rel-18, it is recommended to define: + +1. Terms and abbreviations, the definition of terms and abbreviations captured in clause 3 will be reused. +2. Requirements on ADAE, the architectural requirements identified in clause 4 will be used as baseline architectural requirements; such requirements include also per functionality-imposed requirements as well as requirements for the internal ADAE architecture. +4. Application architecture for enabling Application Data Analytics Enablement, the architectures as specified in clause 5.3 will be used as baseline architecture. +5. Deployment scenarios will be considered as captured in clause. Additional deployment models and their implications on the solutions will be considered. +6. The definition of ADAE analytics services, data sources and corresponding APIs as captured in clause 8.2.2 based on the concluded solutions (see clause 9.3). + +## 9.2 Conclusions of solutions + +The study concludes with ADAE functionality, following solution considerations for the normative work: + +1. Following individual solutions, corresponding to the key issues, will be considered as candidate solutions: + - a. for Key issue #1 (Support for application performance analytics): + - i. Solution #1 (Support for application performance analytics) + - ii. Solution #2 (Data Analytics Enablement) + - iii. Solution #4 (Support for performance analytics for UE-to-UE sessions) + - iv. Solution #5 (Service experience to support application performance analytics) + - b. for Key issue #2 (Support for edge analytics enablement): + - i. Solution #2 (Data Analytics Enablement) + - ii. Solution #3 (Support for edge load analytics) + - c. for Key issue #3 (Support for data collection for application layer analytics): + - i. Solution #2 (Data Analytics Enablement) + - d. for Key issue #4 (Key Issue on interactions with SEAL services): + - i. Solution #2 (Data Analytics Enablement) + - e. for Key issue #5 (Support for slice-related application data analytics): + - i. Solution #6 (Support for slice related application data analytics) + - f. for Key issue #6 (Support for slice configuration recommendation enablement): + - i. Solution #7 (Slice configuration recommendation) + - g. for Key issue #7 (Support for location accuracy analytics): + - i. Solution #8 (Location accuracy analytics) + - h. for Key issue #8 (Support for service API capability analytics): + - i. Solution #9 (Service API analytics) + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA6#47-e | | | | | TR skeleton as approved by SA6 in S6-220082. | 0.0.0 | +| 2022-02 | SA6#47-e | | | | | Implementation of the following pCRs approved by SA6: S6-220083, S6-220355, S6-220356, S6-220357, S6-220359, S6-220360, S6-220474. | 0.1.0 | +| 2022-04 | SA6#48-e | | | | | Implementation of the following pCRs approved by SA6: S6-220925, S6-220644, S6-220819, S6-220972 | 0.2.0 | +| 2022-05 | SA6#49-e | | | | | Implementation of the following pCRs approved by SA6: S6-221154, S6-221349, S6-221301, S6-221350, S6-221351, S6-221204, S6-221161, S6-221474, S6-221352, S6-221156 | 0.3.0 | +| 2022-07 | SA6#49-bis-e | | | | | Implementation of the following pCRs approved by SA6: S6-221824, S6-221694, S6-221777, S6-221992, S6-221857, S6-221858, S6-221859, S6-221713, S6-221860, S6-221861 | 0.4.0 | +| 2022-09 | SA6#50-e | | | | | Implementation of the following pCRs approved by SA6: S6-222164, S6-222166, S6-222167, S6-222420, S6-222426 | 0.5.0 | +| 2022-09 | SA#97-e | SP-220909 | | | | Presentation for approval at SA#97-e | 1.0.0 | +| 2022-09 | SA#97-e | | | | | MCC editorial update for publication after TSG SA approval (SA#97) | 18.0.0 | +| 2022-12 | SA#98-e | SP-221245 | 0001 | 1 | B | Missing evaluations and EN resolution | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-41/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg b/raw/rel-18/23_series/23700-41/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b01407f56877016a25eeb28ee3353fac887cf6b9 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:234530fc26f310623dbd8611b28124d44f28f7ac02a1fa848840cb5f4c70fe6d +size 121091 diff --git a/raw/rel-18/23_series/23700-41/0d9b44054c70dcda35129f11b97a912f_img.jpg b/raw/rel-18/23_series/23700-41/0d9b44054c70dcda35129f11b97a912f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b13dfb5039bc4b1ee5a0c1875038536bbf898f14 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/0d9b44054c70dcda35129f11b97a912f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:246a119fe7127d579ab383089109e6f521dc70a87eec8ed2822a85e94ecc28b3 +size 48968 diff --git a/raw/rel-18/23_series/23700-41/1230eaa9d75a09d7e7b8509931e9190e_img.jpg b/raw/rel-18/23_series/23700-41/1230eaa9d75a09d7e7b8509931e9190e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e245c218596f3fdf8f2efcd89453e251dfa73818 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/1230eaa9d75a09d7e7b8509931e9190e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f5230fd08d6c6536ccd14b403735e5d40679131c72537efa75b0ae388edcdd1 +size 22234 diff --git a/raw/rel-18/23_series/23700-41/12de9b926df0384ec07702671827c9cd_img.jpg b/raw/rel-18/23_series/23700-41/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d77235286605ea76ac33e35fe3692e142808a06 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87da4c9c7e84476ac62cd5f9ba7db687e0e0a09e5c0ce324f844375a284d0cb4 +size 77711 diff --git a/raw/rel-18/23_series/23700-41/1c051a3d61003bc7d513e03015245317_img.jpg b/raw/rel-18/23_series/23700-41/1c051a3d61003bc7d513e03015245317_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71816e75432cbc1aa7cd22ccee8ffc2c85453f81 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/1c051a3d61003bc7d513e03015245317_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4d62cfa94816caf0e1e360004bd7458f472ea620c7ab97aa951f6a11bbdaa57 +size 110524 diff --git a/raw/rel-18/23_series/23700-41/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/raw/rel-18/23_series/23700-41/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..136aaaef96b63f36fcfa261aea7adddf6ff2a5ca --- /dev/null +++ b/raw/rel-18/23_series/23700-41/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13305190cc49212b750926c6197943e32190a122cfb1ef5c7a5657aa40325d28 +size 66873 diff --git a/raw/rel-18/23_series/23700-41/2914642fbfe4ae35924bdf4beb189c1f_img.jpg b/raw/rel-18/23_series/23700-41/2914642fbfe4ae35924bdf4beb189c1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c299930a61dd45fb2d5aac1576075f516acf8dd4 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/2914642fbfe4ae35924bdf4beb189c1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2bf726c63bdd5bed4b2eab89960080c7e38217e0d592bffd824088b673df5e5 +size 86242 diff --git a/raw/rel-18/23_series/23700-41/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg b/raw/rel-18/23_series/23700-41/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f046b71c613e47660018f151e0bf87b6f829dc2 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:caec7929a85c35413befc4c2fd9e4a632a41175dddd2e337ec293016408c7135 +size 82920 diff --git a/raw/rel-18/23_series/23700-41/3334fcca5dac808f4fd3840aba35bc2e_img.jpg b/raw/rel-18/23_series/23700-41/3334fcca5dac808f4fd3840aba35bc2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3176f8868731641b942885484ce084929c847d94 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/3334fcca5dac808f4fd3840aba35bc2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbe303a8255337a8f322891eb3bcfd09c3bdf0e2fbb3914296fad42d898c431c +size 55639 diff --git a/raw/rel-18/23_series/23700-41/37104233d1b6d7728427e833816594dc_img.jpg b/raw/rel-18/23_series/23700-41/37104233d1b6d7728427e833816594dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2fb22a7b593191f045b272d879fb1a63d068d17 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/37104233d1b6d7728427e833816594dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7c16fbe9aebbfb92d6f98d7e8b4bcdd16127656b020d1f44d94f7de39343360 +size 119760 diff --git a/raw/rel-18/23_series/23700-41/376f80eb8a41369e87da63a0210d173e_img.jpg b/raw/rel-18/23_series/23700-41/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9c47ef22ccebda06daa1ebb5025a3be375e1a98 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d46a57e5d6828bf18730cb20bc44fe1fe9c65101d20d8bf5a26dd8fba0f5613 +size 82482 diff --git a/raw/rel-18/23_series/23700-41/3e20f0289a1945c7c3894f51383d8e37_img.jpg b/raw/rel-18/23_series/23700-41/3e20f0289a1945c7c3894f51383d8e37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e735514123893a8029f7080c7103d9aa468aa6e --- /dev/null +++ b/raw/rel-18/23_series/23700-41/3e20f0289a1945c7c3894f51383d8e37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:964ed1890e5909b4aaa60404e250e5be78234ec86b93925bf84c0a3260c0ce92 +size 79898 diff --git a/raw/rel-18/23_series/23700-41/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg b/raw/rel-18/23_series/23700-41/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19adc2de4dbb04680a3c0a20d0aed72e0f8d9184 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:963563f73dea8a72ed4240e79782452acd70ac6de0aca19f6e191042b63fd972 +size 97300 diff --git a/raw/rel-18/23_series/23700-41/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/raw/rel-18/23_series/23700-41/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3c259caf81596d013501b27cfb9c2eb7796562a --- /dev/null +++ b/raw/rel-18/23_series/23700-41/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cd857a3dc7b25b0a457a8031f754de419b16b8404a6c1ec622d02916045b3a1 +size 198901 diff --git a/raw/rel-18/23_series/23700-41/4842f073775fb1e84d101c02fd74e59e_img.jpg b/raw/rel-18/23_series/23700-41/4842f073775fb1e84d101c02fd74e59e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..553f7859b50634aa0af7c91c0c868a7503d05f71 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/4842f073775fb1e84d101c02fd74e59e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac8b440eec951032b3249e905ec3058a7ba609ca6ec288c208494d2fe3a3f63e +size 34042 diff --git a/raw/rel-18/23_series/23700-41/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/raw/rel-18/23_series/23700-41/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fe24352fc7219994150cdb0ad8f402797f1672a --- /dev/null +++ b/raw/rel-18/23_series/23700-41/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4511bbb46a43fe9bac527e8b90581a89e3943ed57ed9eb08c1c7e93b944b1ef0 +size 148690 diff --git a/raw/rel-18/23_series/23700-41/51167ecef86d85cdc6dde05a3afb74b8_img.jpg b/raw/rel-18/23_series/23700-41/51167ecef86d85cdc6dde05a3afb74b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b63a57714ad59f338696cd99fdb9f926bbe6a6a4 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/51167ecef86d85cdc6dde05a3afb74b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f7a0d9c4dd8fecd0288bd3274b7fd74bcd8824233d84538fb93d3cc6fbbf56c +size 103711 diff --git a/raw/rel-18/23_series/23700-41/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/raw/rel-18/23_series/23700-41/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5168939c82f6ef9e6fe278c09e1972eb1782c61 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b108b74c73f15b9c874be553ab5e9493e340ba40efdcb7897483ba44fc62b123 +size 94858 diff --git a/raw/rel-18/23_series/23700-41/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/raw/rel-18/23_series/23700-41/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..213db4519cdb91aa83ce187d46ea4626d256ca66 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83f4e776add07cb5babfa7cce344dd12dea711d81a70490e064acc070cd2bb43 +size 56160 diff --git a/raw/rel-18/23_series/23700-41/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-41/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c109a843c86b34864af9ba58ffa9c0e32e02ef3 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:842d6172bf77588b8dd494ce8b875d6cf5638d032665c05ed8ddeb8c71063962 +size 9643 diff --git a/raw/rel-18/23_series/23700-41/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/raw/rel-18/23_series/23700-41/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d22bf02f1487d6b751fdfbd9050965b850ccb85 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9de2829df70db6f990d61f465a147e42b7b5508c642f133861f77a1389820f41 +size 97536 diff --git a/raw/rel-18/23_series/23700-41/6348f4fc8b3848158fcfbe85e26a731d_img.jpg b/raw/rel-18/23_series/23700-41/6348f4fc8b3848158fcfbe85e26a731d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a734c2832bc4d101aa9f2a57f3509b3453b431e4 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/6348f4fc8b3848158fcfbe85e26a731d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2959b6074da60a099089fb2f91d4e747c0eb23e2b9238e492e82a20def28e6d +size 112973 diff --git a/raw/rel-18/23_series/23700-41/63a2519518616620ef0e53d98b923c05_img.jpg b/raw/rel-18/23_series/23700-41/63a2519518616620ef0e53d98b923c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccef6e99d750be19d871d815ff829e11a94f0fcd --- /dev/null +++ b/raw/rel-18/23_series/23700-41/63a2519518616620ef0e53d98b923c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:522b1c14bf8f73cd20b7443faeed5f6d199ce57cf2b31b1cf5b670a2de1264e1 +size 21190 diff --git a/raw/rel-18/23_series/23700-41/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-41/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..129639df0b23b4a78ee948a880f71b491b4427ba --- /dev/null +++ b/raw/rel-18/23_series/23700-41/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e7a7be9d8135be3a66f27c8d125975d9327dce9a23d74760bab6d7620c912d5 +size 5629 diff --git a/raw/rel-18/23_series/23700-41/649f424fd35ea31f622163506a6148ed_img.jpg b/raw/rel-18/23_series/23700-41/649f424fd35ea31f622163506a6148ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8267587b032c650fecacfcfc5799bdda8a889431 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/649f424fd35ea31f622163506a6148ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8085850ab4d72abebc4927293b93f2c31e0723ae9265bbbe318f92d19074ea74 +size 57303 diff --git a/raw/rel-18/23_series/23700-41/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/raw/rel-18/23_series/23700-41/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba6bb96dccc055d9e52f3bca3b8327cd730df486 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:196ef44f1c95294e987c16d0b0a973c795612095d6082ac4df6ef2659e2842b1 +size 55869 diff --git a/raw/rel-18/23_series/23700-41/691626a7032a642bb74793336c37e274_img.jpg b/raw/rel-18/23_series/23700-41/691626a7032a642bb74793336c37e274_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39757f057af8c2a2b4b9a574b60a8a40f8cf1c41 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/691626a7032a642bb74793336c37e274_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0daa07154da262d687bb453777dd12e86648d8e5721efc69b4a552620718ded +size 143119 diff --git a/raw/rel-18/23_series/23700-41/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/raw/rel-18/23_series/23700-41/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b71908e9665be327e2eefd0e90683fdffb790e53 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:590a3b615ec3f8dec0bf5ce812111a4db20d1506eec430ff10c6ee2ca385b06d +size 70980 diff --git a/raw/rel-18/23_series/23700-41/6d67eee81b97a14e06a6fe57a95aff36_img.jpg b/raw/rel-18/23_series/23700-41/6d67eee81b97a14e06a6fe57a95aff36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24ff70d5a4325a619bb24a1297ca40221ec2ab25 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/6d67eee81b97a14e06a6fe57a95aff36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e449a94f127286a0511e51350d674f764b35a1795a69322a0610d3b02b41db8 +size 69174 diff --git a/raw/rel-18/23_series/23700-41/6e9d059430baba0c363e33749f68b107_img.jpg b/raw/rel-18/23_series/23700-41/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbdf7db9a6f63009a9d2354977743ff96d8128b4 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:affd5677dbdce6c92968900a4ff3d9b518573aa9f89df19c93f88fc05a784996 +size 40722 diff --git a/raw/rel-18/23_series/23700-41/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/raw/rel-18/23_series/23700-41/708e4c9a044ef61f586126676eb2eeb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17d8c239aefd1565b8e7cd575540984bc29fabff --- /dev/null +++ b/raw/rel-18/23_series/23700-41/708e4c9a044ef61f586126676eb2eeb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4767f2c82c077768197401dd30358a122ddb29dfb07a3900bbfb79d559569f97 +size 58703 diff --git a/raw/rel-18/23_series/23700-41/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/raw/rel-18/23_series/23700-41/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6586e17ada1e15abf5c844a78afa92f112919fb5 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa6a7382a6e361af79acddebe8e491dced13c8004a3e79ca88986ecbcbeb5670 +size 31676 diff --git a/raw/rel-18/23_series/23700-41/796d2e601722450d6456085e0a801e1e_img.jpg b/raw/rel-18/23_series/23700-41/796d2e601722450d6456085e0a801e1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4befdff2e6647c39335aeb466e9f62b210be74a4 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/796d2e601722450d6456085e0a801e1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a685a0db7cf7bd8f126d998ad4e22bdba27e51105988c9dc933104a39d3b4a5f +size 62009 diff --git a/raw/rel-18/23_series/23700-41/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/raw/rel-18/23_series/23700-41/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e95f4b50d2b39e2871f085981f9827961873d70b --- /dev/null +++ b/raw/rel-18/23_series/23700-41/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89fe2f7b997095928303a985fc5764d74e7075b273bcbe20e59afb174dacde13 +size 67829 diff --git a/raw/rel-18/23_series/23700-41/832a0ce332e784fe80289e9f00f56574_img.jpg b/raw/rel-18/23_series/23700-41/832a0ce332e784fe80289e9f00f56574_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4feb6680852ec85bb82ba60a535580f61453b5ed --- /dev/null +++ b/raw/rel-18/23_series/23700-41/832a0ce332e784fe80289e9f00f56574_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13ba8e8804301c3d38382b27c97338e70fca8385aa729287d4e3ae3406fd87f3 +size 50205 diff --git a/raw/rel-18/23_series/23700-41/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/raw/rel-18/23_series/23700-41/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c921dd2ed0a34980f61f65436cbec2a4619e7db --- /dev/null +++ b/raw/rel-18/23_series/23700-41/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d6632740a8ccc12be9d9acc06a3445f827acb6abb57ed75f3643f52ffa91018 +size 45354 diff --git a/raw/rel-18/23_series/23700-41/8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg b/raw/rel-18/23_series/23700-41/8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d572f37937c0145c74d92a3f1baca4bf60b81d8f --- /dev/null +++ b/raw/rel-18/23_series/23700-41/8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:662687ba2989e6af42bd3a30e08ec5eecca824d35e59205b77c26b47660ac1ab +size 63496 diff --git a/raw/rel-18/23_series/23700-41/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/raw/rel-18/23_series/23700-41/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a979442328ddf287d6ea9dbfa66da67f57364b6c --- /dev/null +++ b/raw/rel-18/23_series/23700-41/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11e137e3b9516c0cfff9e9965b07537e550b9ec4d28a157b06eb672aea059158 +size 63520 diff --git a/raw/rel-18/23_series/23700-41/9a159e2112eac7be06bdb97e84a0c49a_img.jpg b/raw/rel-18/23_series/23700-41/9a159e2112eac7be06bdb97e84a0c49a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb0b4e9bbc48fd641713ea86ca95ecc9e46bea4d --- /dev/null +++ b/raw/rel-18/23_series/23700-41/9a159e2112eac7be06bdb97e84a0c49a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b57b53a453093bb33135923b27c5154b71d327c0ab92346e5516367ff734d552 +size 109011 diff --git a/raw/rel-18/23_series/23700-41/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/raw/rel-18/23_series/23700-41/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fe792f442d52aba78c07113fe0e0acb9e0a8b73 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aaf59189dfe4f5f8bcaeaf1124e608b6969af6e8ae607a194a5b7368b392f06 +size 66658 diff --git a/raw/rel-18/23_series/23700-41/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/raw/rel-18/23_series/23700-41/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4b59d1dfe2c3fef0801040883e75c5285777590 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb802773f716a006dfa98d0216c798daa3f5ed3b88ba279fe2f811759d219ad5 +size 24485 diff --git a/raw/rel-18/23_series/23700-41/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/23_series/23700-41/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..457a5a8985678b8e9635a7d070a1a62dfa1b9c13 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9e2445e0b7cc3531a8212d014da25b648d51cc53ccf3a438d99dcc510fe0aae +size 66343 diff --git a/raw/rel-18/23_series/23700-41/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/raw/rel-18/23_series/23700-41/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..376dac98d91fd17481fa98235d893b793ec3ab84 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fde4db56d247f79d0423caf94a4749b474af9b1b79ea775a2f6afe0f0d6ec3c8 +size 96971 diff --git a/raw/rel-18/23_series/23700-41/a3f61f2e4a173b16257cd80e83d41d38_img.jpg b/raw/rel-18/23_series/23700-41/a3f61f2e4a173b16257cd80e83d41d38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa81d6248fa041bd03c60857c1dac95e7b07f2cc --- /dev/null +++ b/raw/rel-18/23_series/23700-41/a3f61f2e4a173b16257cd80e83d41d38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22b0409f9ab11b32bc1c82b95e23c2f4764ffc888baab8ca74f8851d3382e125 +size 119930 diff --git a/raw/rel-18/23_series/23700-41/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg b/raw/rel-18/23_series/23700-41/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8667956d2027e7187cd7a59b32936556eaa481a4 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/a4eb9fe011f0e6dc8405f777c5f3f766_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d4ef4b83fe8467d738f43d428124c65093401c275a2418e5c87a7ba722982e7 +size 76923 diff --git a/raw/rel-18/23_series/23700-41/a963ca41bde1669b18a4b783616f228b_img.jpg b/raw/rel-18/23_series/23700-41/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1714da70dc7154e07df773f75f31e5830fdac175 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912d5634602828f82439cd7083c837f721ef54ec15eaf69429374891523b0498 +size 122132 diff --git a/raw/rel-18/23_series/23700-41/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/raw/rel-18/23_series/23700-41/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd0b228b7d148d0e0449a96e1e006009e8f74cc1 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:060fd2fb1436bafeadab72a2872e69f6a84bc2360fb6b8381d53ee8e331ff03d +size 48162 diff --git a/raw/rel-18/23_series/23700-41/af90aabfe3c8c65617da060d82bf99c5_img.jpg b/raw/rel-18/23_series/23700-41/af90aabfe3c8c65617da060d82bf99c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08332168c0f626b0d4d6d81a2d8bdf28520a5cf2 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/af90aabfe3c8c65617da060d82bf99c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7f73a6b4ca78affb225da2fdc698f89c4ad3f303e99112a7b8fc6097d9f0a5a +size 131043 diff --git a/raw/rel-18/23_series/23700-41/b13465efdac63129aef9b6f1787d0d00_img.jpg b/raw/rel-18/23_series/23700-41/b13465efdac63129aef9b6f1787d0d00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8462457575b83fdefa8bdbc199f3fa1c78202755 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/b13465efdac63129aef9b6f1787d0d00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82274aab6253f5092d5fad85d9fb793932ce2eb923abca8da3607c6abc8ae6aa +size 56283 diff --git a/raw/rel-18/23_series/23700-41/b4415fea4ab6fd9f150a1347d4148525_img.jpg b/raw/rel-18/23_series/23700-41/b4415fea4ab6fd9f150a1347d4148525_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b03a70737678cb01e9031cfea9c64ba643ee514c --- /dev/null +++ b/raw/rel-18/23_series/23700-41/b4415fea4ab6fd9f150a1347d4148525_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b843ba6bbd12c33cb16fd95196fcbb65b9c84d2c08b67a83b9bdbaa50c2faa05 +size 90521 diff --git a/raw/rel-18/23_series/23700-41/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg b/raw/rel-18/23_series/23700-41/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2ab665d5ea8aedf5b588fbc11adfe8efbd2c248 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/c00d3fb4f9d9609639a6e7d7a356afd3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0457288594cfa95c80e96b2e9018117f538c63e419811345f7c432b67c541c33 +size 76760 diff --git a/raw/rel-18/23_series/23700-41/c0e369274e53b2e5364666be6f786c7a_img.jpg b/raw/rel-18/23_series/23700-41/c0e369274e53b2e5364666be6f786c7a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cdbd657d2c13e71f23b73449a293ca864ed14a4 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/c0e369274e53b2e5364666be6f786c7a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:097c910b7497f44fa306467d3f1becee9092c2b325f1a794c43268f8e5c8a76a +size 71544 diff --git a/raw/rel-18/23_series/23700-41/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/raw/rel-18/23_series/23700-41/cad89c017c9e7c1785bcd104fde4e737_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b9a9ee03f88d70010e16a182770b0c1fb7193ac --- /dev/null +++ b/raw/rel-18/23_series/23700-41/cad89c017c9e7c1785bcd104fde4e737_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93087ebc60cee33a3edb77be142ac935bbe9a6c4e5462de530c8666f8b4b27c1 +size 69357 diff --git a/raw/rel-18/23_series/23700-41/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/raw/rel-18/23_series/23700-41/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49f6fd3b73ec6f94c5b1fe315df38c5fdfab4f09 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63e5728d7fbe71953eb918ffb1f697743cc924db3c2a69aa7765203b366888f7 +size 80748 diff --git a/raw/rel-18/23_series/23700-41/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg b/raw/rel-18/23_series/23700-41/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b19282f04780d37b1d72339900156b5be076a9c --- /dev/null +++ b/raw/rel-18/23_series/23700-41/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fb84abf1dd342e6a031b891778e25fd77dc0f683832cf4a4a550d8fdbcc9663 +size 47825 diff --git a/raw/rel-18/23_series/23700-41/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg b/raw/rel-18/23_series/23700-41/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc9c48b8f47804d55a6c59ca28d905d5d4f04742 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f5887096536d4ce5e522c31e69b490ca553ab713976f4515125923ff93c1c1a +size 200089 diff --git a/raw/rel-18/23_series/23700-41/d3253d5db64378db6e72b66b41067a5b_img.jpg b/raw/rel-18/23_series/23700-41/d3253d5db64378db6e72b66b41067a5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a24b844013b58b46088c3439a3953e11c6b55bc --- /dev/null +++ b/raw/rel-18/23_series/23700-41/d3253d5db64378db6e72b66b41067a5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2c1796ac8cabeddbf35e88114c4099d8e3882ba6f822b91efc7466bfc0276e8 +size 98022 diff --git a/raw/rel-18/23_series/23700-41/d3a5878a2aeffba0c2c5e8b75ce5c37e_img.jpg b/raw/rel-18/23_series/23700-41/d3a5878a2aeffba0c2c5e8b75ce5c37e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faf35fb505380767b410cbb7408f130e28b021a0 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/d3a5878a2aeffba0c2c5e8b75ce5c37e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac642ec04391048013b880da467bc5864b627e615b5abd5a70c757d53643263 +size 45576 diff --git a/raw/rel-18/23_series/23700-41/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg b/raw/rel-18/23_series/23700-41/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85f6fbe5f7d6a7e9980f710d19534dbbecc83e6d --- /dev/null +++ b/raw/rel-18/23_series/23700-41/da06747b80ea0d71593cbbd4c2ea89aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f51aa4a424384cf8f2200ecf0aafbfb1b9e903f19619a50fd1706040c2ef6afd +size 160901 diff --git a/raw/rel-18/23_series/23700-41/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/raw/rel-18/23_series/23700-41/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4a2bc386653dae4bca8a99bd14d91cedfbff78d --- /dev/null +++ b/raw/rel-18/23_series/23700-41/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cae0f121b56ced1f45c7ad66fad575d8adfed5a2e47cdf792478792f42a13a99 +size 224235 diff --git a/raw/rel-18/23_series/23700-41/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg b/raw/rel-18/23_series/23700-41/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a72222e362280ebedabd9d89df9ed3ec1cfdb8bc --- /dev/null +++ b/raw/rel-18/23_series/23700-41/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:731f32a5e9a3e4f2724aefa9c01684a86d2082e1236a37af307b1e75c3f67c8a +size 65705 diff --git a/raw/rel-18/23_series/23700-41/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/raw/rel-18/23_series/23700-41/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4fbeb9e27815563d28fbf77752a8c743a37897c --- /dev/null +++ b/raw/rel-18/23_series/23700-41/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:830b5c0af37011ae5cbd9df0e5b3d5b0c760fdb7f608f393c295db256de4be29 +size 135919 diff --git a/raw/rel-18/23_series/23700-41/e05b36c0d46549e681ce6581422c66b2_img.jpg b/raw/rel-18/23_series/23700-41/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47e045027ed405363cee5567705c86f7752f67b1 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da4efc74c83c69012c97652d8a9c3fc5d0fbd443dcc23429149267c207a9a83b +size 75772 diff --git a/raw/rel-18/23_series/23700-41/e26bb66586e464339df27951d5c9355e_img.jpg b/raw/rel-18/23_series/23700-41/e26bb66586e464339df27951d5c9355e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9409397332f81db5664fa104804d364c54ff110b --- /dev/null +++ b/raw/rel-18/23_series/23700-41/e26bb66586e464339df27951d5c9355e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:996aee66db2f27dcb74a0823e5b4a561bdbf14eb3e1554c52f7bc2cc5ea372bc +size 65740 diff --git a/raw/rel-18/23_series/23700-41/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/raw/rel-18/23_series/23700-41/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b91e48a636b9c057fb702c5f2cf6b1999074a602 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:131527a0337a28f3b4a4946211da622550066267c72d6063c52dfe32d114d47f +size 55340 diff --git a/raw/rel-18/23_series/23700-41/e354b57563dae469c00b412b2abdf765_img.jpg b/raw/rel-18/23_series/23700-41/e354b57563dae469c00b412b2abdf765_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00e9cf3afed5549b21562a9584cf0a351b71030b --- /dev/null +++ b/raw/rel-18/23_series/23700-41/e354b57563dae469c00b412b2abdf765_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a89a9305c44dd6c5d50a276da6438bcfa31530a2cff6fff76c648fcf3d8f8ae5 +size 155802 diff --git a/raw/rel-18/23_series/23700-41/e417ae35ab07134888be901c201d54cd_img.jpg b/raw/rel-18/23_series/23700-41/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..723400ec7ad67b092797882166ffd351a85d6923 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bac27fda88a8fc87f7426f46342bd6929d20390b31dc90bd9be04f2dec06173 +size 76414 diff --git a/raw/rel-18/23_series/23700-41/e7010c66da16316c2935dfbbef5056b3_img.jpg b/raw/rel-18/23_series/23700-41/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e37121a74c5c27b5e1b2d4f4ac970d3fa983cabb --- /dev/null +++ b/raw/rel-18/23_series/23700-41/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f8890afa68b07d8d56dd799e72c85ca5cd1b2168e7dd1010deedfed7cc2870a +size 233966 diff --git a/raw/rel-18/23_series/23700-41/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg b/raw/rel-18/23_series/23700-41/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6bd47975aca8691dbc696532f2a0934a842632c --- /dev/null +++ b/raw/rel-18/23_series/23700-41/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e47436873838968e9274cd72b0a164da4b7c74992ec5793e0adfbb6aeb9b2a08 +size 72189 diff --git a/raw/rel-18/23_series/23700-41/efb282bed9f06eef1987a14fb27bc599_img.jpg b/raw/rel-18/23_series/23700-41/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d74698a297b7ecf3e62e18f2d64a6ba523aca81 --- /dev/null +++ b/raw/rel-18/23_series/23700-41/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19f6b47d20ad648e49ba272ea079be1f1aa4c9e4e3aae09384ebf5d6e238a25b +size 197692 diff --git a/raw/rel-18/23_series/23700-41/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg b/raw/rel-18/23_series/23700-41/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f7c20c4491415cda683297d88a361e08bafdc8b --- /dev/null +++ b/raw/rel-18/23_series/23700-41/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5901bff71f8e217e7b44b74e17359bd42309e70de4a2d86c58025bbefa2efcd +size 57423 diff --git a/raw/rel-18/23_series/23700-41/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/raw/rel-18/23_series/23700-41/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3472070ca24274adcc81054f85fda7aa605605dd --- /dev/null +++ b/raw/rel-18/23_series/23700-41/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eceb47511c5f631994abac9b31437769a9fa9f9e952881736ca078b7d00ed1bb +size 22388 diff --git a/raw/rel-18/23_series/23700-46/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/raw/rel-18/23_series/23700-46/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaa190ded6b20596a593ec747cac0c690769cdc3 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06826d7ec110c72d22f6495f0ee425def385ad0cf9dd6300574c6b767409313d +size 57726 diff --git a/raw/rel-18/23_series/23700-46/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/raw/rel-18/23_series/23700-46/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2125cf4ee68db676daadd5193408b421d8f9a769 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cacb697abe2561e778ecbaa7d2aed1b1ab1741bc6d02def3811398418383fbf2 +size 65545 diff --git a/raw/rel-18/23_series/23700-46/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/raw/rel-18/23_series/23700-46/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51d81ce2747f6f58478a2b60835cda0e17f45b4d --- /dev/null +++ b/raw/rel-18/23_series/23700-46/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4bd5de8a91a5abc23b25223ec187bb14363d695444e4bd649a45fa40c66a5df +size 47969 diff --git a/raw/rel-18/23_series/23700-46/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/23_series/23700-46/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b510db14f7f8eb78a4f8ea1aa00d4725ddcf203 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16656f4e7f1b092df306323ed97cc20204056c8fc9023156c82ba7f824801e8e +size 60060 diff --git a/raw/rel-18/23_series/23700-46/446100c084b94817a19c319fa776b412_img.jpg b/raw/rel-18/23_series/23700-46/446100c084b94817a19c319fa776b412_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e2756eb6d4f6ac11f10d32252168987b754e8b9 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/446100c084b94817a19c319fa776b412_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2d7310bd301d4340523412825ca1dcff96bca56619056294fcf293b5247d3bb +size 47423 diff --git a/raw/rel-18/23_series/23700-46/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/raw/rel-18/23_series/23700-46/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7324946df2dacd43e7a5370016007cb1f8f7172 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:050b9fd3c37444d4b03ac8d922237d2a8e06e21a1f9df04827e87fa9e790de25 +size 47995 diff --git a/raw/rel-18/23_series/23700-46/552ca016af3d6240648ab5a2cad97f60_img.jpg b/raw/rel-18/23_series/23700-46/552ca016af3d6240648ab5a2cad97f60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62afdab271552a448b664034272d35b856acdd15 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/552ca016af3d6240648ab5a2cad97f60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7a56dd0cb81d5abd5bcd341182d2a7a3275edacafa5b09a42920319de5b250e +size 35260 diff --git a/raw/rel-18/23_series/23700-46/5dfc130b129ace4df375839020a5700d_img.jpg b/raw/rel-18/23_series/23700-46/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9afacc9ea858b0cec009a429bf26f278e18c0c56 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90f2ea17455be6831dd5ae42bc326c79a7d27c997cd4f824511ba5b24fec211f +size 44914 diff --git a/raw/rel-18/23_series/23700-46/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-46/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f454e010b4d3fde2b22f0495af8122a2bce9a264 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a9269f78d9fbb1ae0482dde5ae2384fed586126242428b24a2cdac8ceb02213 +size 7339 diff --git a/raw/rel-18/23_series/23700-46/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-46/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b664ab0d3e551e419b0c71dc591bb8e8419b994 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09e0aec78af1f309244cf1fbb3a9d758fd4dbfa517e066b39bd8983f8194ef8d +size 5494 diff --git a/raw/rel-18/23_series/23700-46/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/raw/rel-18/23_series/23700-46/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60fccbc91c8cd40a48a797029e42656276290a56 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:067f989d0e024b3e9eb08e45396084c26bac909d5cc33715c5061e7a349fa033 +size 23103 diff --git a/raw/rel-18/23_series/23700-46/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/raw/rel-18/23_series/23700-46/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee093fdea0eed371a277739ffdf601cd3cb2ea55 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80995b44f675aae42e1bda56472a8be26574da79735aa9825023720033468778 +size 98298 diff --git a/raw/rel-18/23_series/23700-46/718be1eb075833deb7a3b80729a06264_img.jpg b/raw/rel-18/23_series/23700-46/718be1eb075833deb7a3b80729a06264_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea7ca22ebd27dae18108cb3b756de1f8f9c45f27 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/718be1eb075833deb7a3b80729a06264_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acc4746d6c3b714ab1e226300a992b1d3cac7ec7bc5b9b579a8ffa6351d52036 +size 40582 diff --git a/raw/rel-18/23_series/23700-46/7f17c430b9598e4d748a8041457810b3_img.jpg b/raw/rel-18/23_series/23700-46/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd43f5203c38526068c55bb3dd292c1f0b3bf226 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8807f3f5fe2e7839c275826a682fef49bdf5ce02839737b8ad65450389f7925f +size 26289 diff --git a/raw/rel-18/23_series/23700-46/9cd90f495b95ad2116ff780248c26d95_img.jpg b/raw/rel-18/23_series/23700-46/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00c001c1d772767861f88905e130e9a54544d53a --- /dev/null +++ b/raw/rel-18/23_series/23700-46/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65c59661ec9136090257acecea97f0877d8a373e1e5a15b71b6c0b99c52893aa +size 36497 diff --git a/raw/rel-18/23_series/23700-46/dd380ccd5aca1151074fede04826f1a4_img.jpg b/raw/rel-18/23_series/23700-46/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b01a248e98d637d7dc3228bf28098ccb45af7d15 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a3981f0bd21b8a47bc48899c6c805215204c62789d007706373d91a75623914 +size 41358 diff --git a/raw/rel-18/23_series/23700-46/dfaa8b98082261913dac00eae86b2889_img.jpg b/raw/rel-18/23_series/23700-46/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8195613410f2e08cf0c083b0d27858b129b9b4d8 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:850c459ece00e52557816675fdbbb1934f29bf52f2ae25537d37846bb89f2e1b +size 107158 diff --git a/raw/rel-18/23_series/23700-46/e6df2733626a85205c1db682e6259c46_img.jpg b/raw/rel-18/23_series/23700-46/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69ea32fe7ce035bf281f04ac9d853459ba4699fd --- /dev/null +++ b/raw/rel-18/23_series/23700-46/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa4fe6a184a5b8e9f13a1b83819901a46197f5bf0a5e7cbeb76dcf145d60c829 +size 48153 diff --git a/raw/rel-18/23_series/23700-46/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/raw/rel-18/23_series/23700-46/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92fdb78c2bf86fadf245b430b117d0cbcd60faea --- /dev/null +++ b/raw/rel-18/23_series/23700-46/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ee645efae227497dc067a6527b3df02f1e71e36c511a5835e03be922b3eac57 +size 60827 diff --git a/raw/rel-18/23_series/23700-46/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/raw/rel-18/23_series/23700-46/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c109f1468e2a9e2e5b5064dcef86ca89c31dc742 --- /dev/null +++ b/raw/rel-18/23_series/23700-46/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:caa6c4994e9fecc87edc313f8af69087aea2766b3c4146acf441564e88d7ae18 +size 27498 diff --git a/raw/rel-18/23_series/23700-46/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg b/raw/rel-18/23_series/23700-46/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae5feb7c67ca465063ee89a9adb5abc94fa9145b --- /dev/null +++ b/raw/rel-18/23_series/23700-46/ec98c4d2d93f28dfc8eb9d5e5730f62d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f24b817df1d52ae108bd0d6080150222fa0a117d77bdc0d61e0d845240b057c +size 28727 diff --git a/raw/rel-18/23_series/23700-47/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/raw/rel-18/23_series/23700-47/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bf51100d7f41fd014266c4051f9d16117cd0f7b --- /dev/null +++ b/raw/rel-18/23_series/23700-47/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01cd5c7d8029feec610cab8f9d6207fe22b9460f4b9f58f8761595adabc00972 +size 62628 diff --git a/raw/rel-18/23_series/23700-47/0d9b44054c70dcda35129f11b97a912f_img.jpg b/raw/rel-18/23_series/23700-47/0d9b44054c70dcda35129f11b97a912f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33c89b468418301bf545831b67459d4930a485db --- /dev/null +++ b/raw/rel-18/23_series/23700-47/0d9b44054c70dcda35129f11b97a912f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2de1105c8ed6b2af60efd62e5bfe84b0388679a448ecc095ce79ee816d9d278 +size 35973 diff --git a/raw/rel-18/23_series/23700-47/10781f43062bf3e9601a1e086710556c_img.jpg b/raw/rel-18/23_series/23700-47/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4ff63fcfa802eadf280472e8b96c29ea0e980e9 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d9d30d09559e095e9971a9bbd5b6d60f43fd34aaa1cd0c6b0208107a98c275e +size 156305 diff --git a/raw/rel-18/23_series/23700-47/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg b/raw/rel-18/23_series/23700-47/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f901e1ab58ebcf22246736e8d304c5b4783356a9 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5121fcf687af7b9cd59ca9cda45655745733c13646bdd7965d54058a232a0f93 +size 109041 diff --git a/raw/rel-18/23_series/23700-47/187bba66c887c745c512add37a577c5e_img.jpg b/raw/rel-18/23_series/23700-47/187bba66c887c745c512add37a577c5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62bb48df4b849da2e7dc9491224cd4d66e15f4c9 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/187bba66c887c745c512add37a577c5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49905ae19c903acb1bbd1660ff2f957141a12cc4d8d8316d46a38e32b2eb7244 +size 53174 diff --git a/raw/rel-18/23_series/23700-47/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/raw/rel-18/23_series/23700-47/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3de4730242ea4a8135e8c5a418b7c624eec09e63 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7e993e2b5f829fbf259cdb8779019706cd4336e0754b5eca45b66ed8abea038 +size 49700 diff --git a/raw/rel-18/23_series/23700-47/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/raw/rel-18/23_series/23700-47/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26a13d6ab20f57cb85db7d13dc007a2b04d3b14a --- /dev/null +++ b/raw/rel-18/23_series/23700-47/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:256e535d440e6d2a85f90e4d7dafbb747d244e3f8d20125869182521b58a1f84 +size 75368 diff --git a/raw/rel-18/23_series/23700-47/21c8a1f65b4718372aadf6a1cc10204d_img.jpg b/raw/rel-18/23_series/23700-47/21c8a1f65b4718372aadf6a1cc10204d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a6701f43837d3adf90feadeae9e2e7bab633973 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/21c8a1f65b4718372aadf6a1cc10204d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ffe855baa0e3ef35f406feaf919a70dbf7e5d22e5ff1ce151c3d9041053bc342 +size 47336 diff --git a/raw/rel-18/23_series/23700-47/468be155058fd5d2862919eb8ec35496_img.jpg b/raw/rel-18/23_series/23700-47/468be155058fd5d2862919eb8ec35496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a92a373c26d06b20f6738833b198afa0832f9e81 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/468be155058fd5d2862919eb8ec35496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47a9720219f955b89829a687a8b41efc1a3e31b74ea80432e55c90a83a09bed7 +size 35647 diff --git a/raw/rel-18/23_series/23700-47/4847c98185bc52e8786b78738bc52b45_img.jpg b/raw/rel-18/23_series/23700-47/4847c98185bc52e8786b78738bc52b45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab7152fe48a0f261233e4f10746d452ad65ca497 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/4847c98185bc52e8786b78738bc52b45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43df64f345e62f28f6365098845f607293d9d679fd82fe7e03b8a30fbef984dc +size 40914 diff --git a/raw/rel-18/23_series/23700-47/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/raw/rel-18/23_series/23700-47/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f915f1b97f847b68aa0fe0ea4fe91d3f9ffe2907 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73662d71549fc5b66913e0ddcb6e0f657d0fda3aa066b642a3b02f35f10cd865 +size 142274 diff --git a/raw/rel-18/23_series/23700-47/5801c19431e76330430e92a598cc7a16_img.jpg b/raw/rel-18/23_series/23700-47/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..912fed05402fb22e1a049265b77206f0ce3c9d55 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37ba7668e59cc4b8e49d3818da064e6a6735382c22044a068f68584ef792fd42 +size 68480 diff --git a/raw/rel-18/23_series/23700-47/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-47/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9af7a0219b871722751a8416d7574889a601a345 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c31a024782ee1fb89baff0c2ad00b151e25fc7e37f19226746e5dace921e85f3 +size 9576 diff --git a/raw/rel-18/23_series/23700-47/605625ddfc3363a6205ab0d43b184eaf_img.jpg b/raw/rel-18/23_series/23700-47/605625ddfc3363a6205ab0d43b184eaf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f493df9a42871dfaddd43f0deeaa37e92803286b --- /dev/null +++ b/raw/rel-18/23_series/23700-47/605625ddfc3363a6205ab0d43b184eaf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d60814e96a7eeed368c4d3fa7c5862e3cacf1054f0f720891c10d0f7de7905db +size 52298 diff --git a/raw/rel-18/23_series/23700-47/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-47/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..969b11260b221a9f7e179f07dae8525ec1dd8cbf --- /dev/null +++ b/raw/rel-18/23_series/23700-47/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4acdb92acc30922bb5e76a149abf0a19827768c583f80e86ed13605f9a318c74 +size 5643 diff --git a/raw/rel-18/23_series/23700-47/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg b/raw/rel-18/23_series/23700-47/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af730c4749af5f85d645d30b02a6d0c7b5b9e08b --- /dev/null +++ b/raw/rel-18/23_series/23700-47/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0a08407186bdbf76f9f11db246132a04949bc1af5a6ea7b53f0740bbbf3a520 +size 95795 diff --git a/raw/rel-18/23_series/23700-47/742a5484e7dd016256ab99921bbd635d_img.jpg b/raw/rel-18/23_series/23700-47/742a5484e7dd016256ab99921bbd635d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5aad36eb9ff03fadece2e322419e2e4f8c542528 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/742a5484e7dd016256ab99921bbd635d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23da10a012936064eac5bdcf8189511eb385a6b8cef746499740f760186a139e +size 151072 diff --git a/raw/rel-18/23_series/23700-47/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/raw/rel-18/23_series/23700-47/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2482e61b5f7fbc31aed077b0b2bb1b5f59a3726e --- /dev/null +++ b/raw/rel-18/23_series/23700-47/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d23856768cf29ecd123703a8aa737417423f695a1a4225c0a793935e1157f7a9 +size 82042 diff --git a/raw/rel-18/23_series/23700-47/8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg b/raw/rel-18/23_series/23700-47/8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd65adc8852f68da4edbb506685acbbc53a1a750 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/8198a1ee0b1f6ef1c5f1bf702dc74eca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42e35ad08a22de7eb61ed95d31ce593f6e5042f109509906ba7380c88b25fda7 +size 81964 diff --git a/raw/rel-18/23_series/23700-47/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/raw/rel-18/23_series/23700-47/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5b0a00f3124a0e7a17e3c109fdbdd902a8921cc --- /dev/null +++ b/raw/rel-18/23_series/23700-47/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b011e9683b6fea8470c6889b42788be7a32a183680025dec71b21ed57aba1fc +size 71659 diff --git a/raw/rel-18/23_series/23700-47/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/raw/rel-18/23_series/23700-47/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba066e1739cc2986d77f63ca8891d27099e0e454 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b15fb176936b769ad2cbf469f07169bc29d517e67dad542e94710f9b4d29d5cc +size 112358 diff --git a/raw/rel-18/23_series/23700-47/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/raw/rel-18/23_series/23700-47/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9ebdc9f9c9757e318044a1e33361267de6b7a63 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0df7a1f1cfa2e0f113e479eada4110be5f511e09e073fe6ceb0dfd6f82a223fe +size 152029 diff --git a/raw/rel-18/23_series/23700-47/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg b/raw/rel-18/23_series/23700-47/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cb2e0bfb16d702316504502e707764004adaf78 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5909e714fef12cd852198aeed0a301f8c3b9b2149c86663b77a06b31de105fe6 +size 63347 diff --git a/raw/rel-18/23_series/23700-47/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/raw/rel-18/23_series/23700-47/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea70e7246658ab51f401c31819f0c4327dd47c30 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:317648bc8715599915eaa1ffad651c726aebc3905db18e52b4c10a71dfce24c6 +size 115664 diff --git a/raw/rel-18/23_series/23700-47/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/raw/rel-18/23_series/23700-47/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8449e7cf9f734344459639a10344c1b453e389a8 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6358a50bebd32c0b621ad4d2754c39024bf9113147da179401cfeb118c8eed3 +size 130789 diff --git a/raw/rel-18/23_series/23700-47/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/raw/rel-18/23_series/23700-47/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a888e5b0b57b5a6fae8dddd605cf4e85027fb71 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74b2867795dfbb8538371c487428cd524acf355ef671df8807c5b44635afb810 +size 85689 diff --git a/raw/rel-18/23_series/23700-47/9f862801bce82634d3b5a1e0a195a799_img.jpg b/raw/rel-18/23_series/23700-47/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60afe913114957cbab6e1976110418385f756feb --- /dev/null +++ b/raw/rel-18/23_series/23700-47/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e280ab64016deb143fa6b6170fb630873bed03c839ecadfedbaf21eda22178e3 +size 169373 diff --git a/raw/rel-18/23_series/23700-47/a3472689858b068ef469213682965325_img.jpg b/raw/rel-18/23_series/23700-47/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaaedb4c8966160b0c69b3afd03b5efb3b711406 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f89e5c6a153bb8abd46fe5426e5cb2e85f1ceae00004ae101c36cdf7d91be60 +size 55686 diff --git a/raw/rel-18/23_series/23700-47/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/raw/rel-18/23_series/23700-47/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da56c62f9d9ea5979effea79fd7837b8071a1232 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:101b1aa3d121969d376e38d712fbf55b19679e7e855b2f82d8f3aa0d5a517f2d +size 110879 diff --git a/raw/rel-18/23_series/23700-47/a9159a006d67a834a7b1a771c18191cc_img.jpg b/raw/rel-18/23_series/23700-47/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c76bc9ef5bc3fc31104a446bf504e48e8bf7f482 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e08f9da6e34ec45d26d44ec71a5532c1bff7e5f61321a6baf340789f42fe5d78 +size 204476 diff --git a/raw/rel-18/23_series/23700-47/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg b/raw/rel-18/23_series/23700-47/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58052a79a4d8f4f70d1a38beda67a01372b9b8bc --- /dev/null +++ b/raw/rel-18/23_series/23700-47/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2b4fb064b214214bd5036fff29f38a52bb219a57d715488e7f56c6ee088b06a +size 150942 diff --git a/raw/rel-18/23_series/23700-47/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg b/raw/rel-18/23_series/23700-47/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5dfdaf7e37ca3096044cc7be537d2ca1359191a --- /dev/null +++ b/raw/rel-18/23_series/23700-47/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a6e87b5c40522a4f4cbc778e94c8bf5b7a4fecb43c6bbbf894fadffc85d19b9 +size 209337 diff --git a/raw/rel-18/23_series/23700-47/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/raw/rel-18/23_series/23700-47/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f27e842aea7c87444a39acb77b41a048384e035 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf1132f2daf6827d2c76b5d1d33d344479f3279ce5e1d1fc0fc109a74335e673 +size 168733 diff --git a/raw/rel-18/23_series/23700-47/bbddeb46a8bee133d49003273fcfc8dd_img.jpg b/raw/rel-18/23_series/23700-47/bbddeb46a8bee133d49003273fcfc8dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76ed15eb377c73bb182f7bfe52a160d367dc2b20 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/bbddeb46a8bee133d49003273fcfc8dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae804874a3eb9f8cf46ebbfb4904de1895317007aefa9ad0efbb026e490d36f7 +size 75557 diff --git a/raw/rel-18/23_series/23700-47/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/raw/rel-18/23_series/23700-47/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b9e9ab180b2cff2cd2c23010f1dd1220df4bcce --- /dev/null +++ b/raw/rel-18/23_series/23700-47/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f4fbf1a030a6e353cab364064c8515ced29e3dc4bcaa2c140035130933fe99d +size 98321 diff --git a/raw/rel-18/23_series/23700-47/bccc028d0e75bc30c41528056f581545_img.jpg b/raw/rel-18/23_series/23700-47/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c3324fe25dce1ff153fbd09d66b90b748c381ad --- /dev/null +++ b/raw/rel-18/23_series/23700-47/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78aac2c3589307f944cc2955c1f1a4b5a4e944e34ece338d12309db374e4bb45 +size 94484 diff --git a/raw/rel-18/23_series/23700-47/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/raw/rel-18/23_series/23700-47/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..305387cd0311a185e829350c1be41c016c280f01 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a10f03562eedc484c3698f28f7e31c8c9d84e9e689a1af2c15c8814dd5050cfd +size 141000 diff --git a/raw/rel-18/23_series/23700-47/c649cad02e45d7d9a16f3f5bdb332219_img.jpg b/raw/rel-18/23_series/23700-47/c649cad02e45d7d9a16f3f5bdb332219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7d4af2cbe23ca4b63ca5d99cbeba284577d5245 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/c649cad02e45d7d9a16f3f5bdb332219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:002d75c1f1ce673ef9e0cea89ad5756f6b4068d8d12a9a296f00df7683dd6ec6 +size 78132 diff --git a/raw/rel-18/23_series/23700-47/c7e27041e661260fd0c8e89c763bb32e_img.jpg b/raw/rel-18/23_series/23700-47/c7e27041e661260fd0c8e89c763bb32e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b35148da51321078d3ffa50efa84a957565a28f6 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/c7e27041e661260fd0c8e89c763bb32e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4d68bc252ed04c47781fc4f00f0b6ad3cc117a76bfadd64bf6e91eb0dd9779a +size 78284 diff --git a/raw/rel-18/23_series/23700-47/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/raw/rel-18/23_series/23700-47/cad89c017c9e7c1785bcd104fde4e737_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97ebfd936b06f6c26517909c83bc1f6fee5561ab --- /dev/null +++ b/raw/rel-18/23_series/23700-47/cad89c017c9e7c1785bcd104fde4e737_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df740575db3bbe6890c09747f0fb369829c1f6b58c2fc9e688dcfbc54ed0531f +size 44489 diff --git a/raw/rel-18/23_series/23700-47/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg b/raw/rel-18/23_series/23700-47/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15346f79f2f677b69520c5dcaa64b201ff986114 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54938e490be2cc8b28e94e3651742b829af8a43f53d26959340a79bd76461671 +size 85854 diff --git a/raw/rel-18/23_series/23700-47/d9d09655eb4282168769ac97178db50c_img.jpg b/raw/rel-18/23_series/23700-47/d9d09655eb4282168769ac97178db50c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d851ec6b214f2b5971a2a9d21f0cc3052bbbcf5 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/d9d09655eb4282168769ac97178db50c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71740dffe9f53d88ba0e672ade9323be684b9860e5761beac48547898284f213 +size 88203 diff --git a/raw/rel-18/23_series/23700-47/dde1a42ca58cd189901556a0cbfe7d57_img.jpg b/raw/rel-18/23_series/23700-47/dde1a42ca58cd189901556a0cbfe7d57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7868e3dd1b3580fcdf2ab11aff8893882531427f --- /dev/null +++ b/raw/rel-18/23_series/23700-47/dde1a42ca58cd189901556a0cbfe7d57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1a464e27ca860c5804c718d0d08e9d9ee242e38c21dc6b1191acb5e9bc3c9e5 +size 67760 diff --git a/raw/rel-18/23_series/23700-47/dec689324b075952626a86da862b9549_img.jpg b/raw/rel-18/23_series/23700-47/dec689324b075952626a86da862b9549_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd2ce8257d00acd78152488f8783c3243922948a --- /dev/null +++ b/raw/rel-18/23_series/23700-47/dec689324b075952626a86da862b9549_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66d71f6c485fc21f3589270cef1afa618a6bde70368ae105dfa4e6288ac397e5 +size 57561 diff --git a/raw/rel-18/23_series/23700-47/e05122559f56af5699789b7118d8fe87_img.jpg b/raw/rel-18/23_series/23700-47/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63a75a6735029f0b9706f810fe43640fca8fcc42 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a77a1a0da037a84f720aacc113e7d7409566560e80977e4bf7a70aea2bd93b7b +size 92198 diff --git a/raw/rel-18/23_series/23700-47/e20792fef9de6560b2d6c5441da7614a_img.jpg b/raw/rel-18/23_series/23700-47/e20792fef9de6560b2d6c5441da7614a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01d6d93606638a7c9420e15d029d86508277b80e --- /dev/null +++ b/raw/rel-18/23_series/23700-47/e20792fef9de6560b2d6c5441da7614a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1a4021499b90395f9ef59be80791d0cee2184a29587bc7af316a943058398e1 +size 114910 diff --git a/raw/rel-18/23_series/23700-47/e417ae35ab07134888be901c201d54cd_img.jpg b/raw/rel-18/23_series/23700-47/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..393599a80080042207fa88a0bfb310b528a83371 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5e54b11c90b8eddcfea600c2a96ae0ce4350f636e00abe0f383f45ece2e85a0 +size 196601 diff --git a/raw/rel-18/23_series/23700-47/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/23_series/23700-47/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85079f56209437eb4fdba872a0cf1bea8066b922 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e37820ec864f4e15323fa7b3dbdc17a704a326195d05d4d2b1fbcb685815523f +size 72103 diff --git a/raw/rel-18/23_series/23700-47/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/raw/rel-18/23_series/23700-47/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6853612e63bd8b732511dc8fa1d23a1d7209be9f --- /dev/null +++ b/raw/rel-18/23_series/23700-47/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65b731f221425d085de65cf031eb4aa7fde372926f5a463dae439d68631446e7 +size 89267 diff --git a/raw/rel-18/23_series/23700-47/fa3258abeaa067802e97eb4d1901572f_img.jpg b/raw/rel-18/23_series/23700-47/fa3258abeaa067802e97eb4d1901572f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..027480f782bad45fd2a79fc21e86fb25f94e2e57 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/fa3258abeaa067802e97eb4d1901572f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fcf027485a9e20562cff15893d256a55253dfc24178a1f37ff875a5d1b88497d +size 59952 diff --git a/raw/rel-18/23_series/23700-47/fc3e2b49a9f850951570e502393b697f_img.jpg b/raw/rel-18/23_series/23700-47/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8fde13565503e70c711b7ba904b2915842f92b2f --- /dev/null +++ b/raw/rel-18/23_series/23700-47/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df9c7f47232ad6e5434164c90c6b91454e948458cfd79eca04c7c42f61b1bbb9 +size 48418 diff --git a/raw/rel-18/23_series/23700-47/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/raw/rel-18/23_series/23700-47/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..617f3d6567c5c66ce433c00d788d517a8a149f96 --- /dev/null +++ b/raw/rel-18/23_series/23700-47/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db5af0ca74bb3f371983a89f9bc8a49c8188744f00418c33405a5cb74623489e +size 122231 diff --git a/raw/rel-18/23_series/23700-48/022d578ec5fd05303811e9e57975ab2e_img.jpg b/raw/rel-18/23_series/23700-48/022d578ec5fd05303811e9e57975ab2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a05cfa6a9abd270596ce11e6975ab9b7ad05da34 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/022d578ec5fd05303811e9e57975ab2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2255ce7539fa38e216f962d2dfcf7b8aebe3b24c57b55c03356f9f9cee512ddc +size 30994 diff --git a/raw/rel-18/23_series/23700-48/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg b/raw/rel-18/23_series/23700-48/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f257963b5feb8079c87164061d7addc99ad915b3 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3bebcb5a8ae38cc0392d6519a389805c71986b8649c2240ac8f2bec140f8e73 +size 67363 diff --git a/raw/rel-18/23_series/23700-48/05b0f658f02a1301691b547d089c485a_img.jpg b/raw/rel-18/23_series/23700-48/05b0f658f02a1301691b547d089c485a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60dd5ef5121e1950677fa202dd9bd5f06ce63a6a --- /dev/null +++ b/raw/rel-18/23_series/23700-48/05b0f658f02a1301691b547d089c485a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef71cd0d672056aaaf69b09d04b63780dc5562c1f9af28cde6b60f210d5c5750 +size 66983 diff --git a/raw/rel-18/23_series/23700-48/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/raw/rel-18/23_series/23700-48/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8d6101e7565b352b7f3407d8a497ee1507b2df8 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:702564d7ded9e07a24e5e03ced99f76a3b6058afab8a76b2975c5f8b64c1dd24 +size 141865 diff --git a/raw/rel-18/23_series/23700-48/088921fa3f5a44c8551815122517eefd_img.jpg b/raw/rel-18/23_series/23700-48/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a6a79281ea7ceb022c3ed8f35d2917726ddb2db --- /dev/null +++ b/raw/rel-18/23_series/23700-48/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73c7bdfc10950f24ffa29cef278f8e7c8fc1a6418eb69269530b7c5ff3ab76c9 +size 103243 diff --git a/raw/rel-18/23_series/23700-48/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/raw/rel-18/23_series/23700-48/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d6c1a3532f542dff02c3025fe8c104230aea132 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:393725beaa00c2704c0fa0cd3e16508473dbd14fd4e8f5a5d1f403dc56148f73 +size 48938 diff --git a/raw/rel-18/23_series/23700-48/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/raw/rel-18/23_series/23700-48/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b0dae5490fe8fb521f65ffa68e10ce29d56aa0e --- /dev/null +++ b/raw/rel-18/23_series/23700-48/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45efb040de01bc446af37fd507789a69b886e7464a2c3ef7ee8422e3797914e7 +size 80447 diff --git a/raw/rel-18/23_series/23700-48/0d9149a10167a487a93c349f5d848b7d_img.jpg b/raw/rel-18/23_series/23700-48/0d9149a10167a487a93c349f5d848b7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e715f965f824e105bbb5523be966f9821863dde5 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/0d9149a10167a487a93c349f5d848b7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53307a0f72dac751a79ca17e64194cf6f34100a0a0ba28786403fd6adb1662ee +size 28469 diff --git a/raw/rel-18/23_series/23700-48/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/raw/rel-18/23_series/23700-48/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98074cfae7a390f3b75e7bd9e5dc28b1f9567858 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2b12152563533f7e9c65ce68e94de320ddd101742c4e0f89c65c0192e8ec86e +size 123736 diff --git a/raw/rel-18/23_series/23700-48/10bf8762a8e8d9385609cc6fb11061fe_img.jpg b/raw/rel-18/23_series/23700-48/10bf8762a8e8d9385609cc6fb11061fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f9bdeddd07cf8490be3a52563fd0d9881c26a03 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/10bf8762a8e8d9385609cc6fb11061fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d684964f0da9186564fe5c738c3cef0cfa190ca69a7c50935ead621aa493713d +size 71820 diff --git a/raw/rel-18/23_series/23700-48/11f18bf0233d812ad2604f88f3385d60_img.jpg b/raw/rel-18/23_series/23700-48/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1ad3e1f52e86867481f4c96d08d77824f0ec25d --- /dev/null +++ b/raw/rel-18/23_series/23700-48/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b3306ea8dd68b76437b7053702d4b29b0c5eb61163858297dc413a8145a8387 +size 173743 diff --git a/raw/rel-18/23_series/23700-48/133d09b09892b9fa5e84cfaa627e11a2_img.jpg b/raw/rel-18/23_series/23700-48/133d09b09892b9fa5e84cfaa627e11a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0c96d0156cf52c035fe445fd242e3e2f5a77ddd --- /dev/null +++ b/raw/rel-18/23_series/23700-48/133d09b09892b9fa5e84cfaa627e11a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e2c118134343ba3dc7661c119ed9d46852eb6c3bbe9243ccc3760a404a2d70a +size 11830 diff --git a/raw/rel-18/23_series/23700-48/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/raw/rel-18/23_series/23700-48/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b03b3866003f77603ac49656e2aa79b427c1f2ee --- /dev/null +++ b/raw/rel-18/23_series/23700-48/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6950ce6e0af911062451380aeda41687d0a077b4925aa31ae1538f6ba2cf4bda +size 77376 diff --git a/raw/rel-18/23_series/23700-48/149826281804ec51b5cca5603c88b23b_img.jpg b/raw/rel-18/23_series/23700-48/149826281804ec51b5cca5603c88b23b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49c681a2a994057ddb02f1e1a6249feced661524 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/149826281804ec51b5cca5603c88b23b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d133f64549d34a07a9555d2f8054384a8fb9c5f6d3e308d77f0d00146969b9e +size 64428 diff --git a/raw/rel-18/23_series/23700-48/15b94d74577004248532b2f4fd64f535_img.jpg b/raw/rel-18/23_series/23700-48/15b94d74577004248532b2f4fd64f535_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7a3cd821343bde5fae511f974e9b01536f499af --- /dev/null +++ b/raw/rel-18/23_series/23700-48/15b94d74577004248532b2f4fd64f535_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6895076fcaca2a552cf5158a92a9af7f8663db2a671ea1b323fb8f429caadad +size 30929 diff --git a/raw/rel-18/23_series/23700-48/16d7062de0d42e048d1bb46d792d37b0_img.jpg b/raw/rel-18/23_series/23700-48/16d7062de0d42e048d1bb46d792d37b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df2f06e8276c6e8645cd34703de0a23e4105bbf3 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/16d7062de0d42e048d1bb46d792d37b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa3ed5b2c3f6c4606cdcb84655f12f3e9deb35c4e7ef2e27276d2341df969d01 +size 74208 diff --git a/raw/rel-18/23_series/23700-48/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg b/raw/rel-18/23_series/23700-48/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5452b83fc542a6387218c33a0a6ed217d9bb8670 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f0fcbeb24872d30a2130cb0670ea4ce946a5b957951913972199fe6bbd339ef +size 43132 diff --git a/raw/rel-18/23_series/23700-48/273610b2edda13f5c3de995f4e845396_img.jpg b/raw/rel-18/23_series/23700-48/273610b2edda13f5c3de995f4e845396_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf9da44931c3879975c8e1019e99189edb628813 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/273610b2edda13f5c3de995f4e845396_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8151ea0026a3e9fafdde14ac9e422cd364998897844e0caa18009e1a81538b82 +size 58838 diff --git a/raw/rel-18/23_series/23700-48/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/23_series/23700-48/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..823f0fa66c138673f8bcaa3fa406e2487cdeb42f --- /dev/null +++ b/raw/rel-18/23_series/23700-48/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da8c0a4dde0b0f7e76a0eb7a9f0f60df5ef18ee46e6492666c234cfdb3d19245 +size 53929 diff --git a/raw/rel-18/23_series/23700-48/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg b/raw/rel-18/23_series/23700-48/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..171b150c1e07983c7dc9e5df00d5ed99032f6c40 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:449697c75945de63582e008f57cd792a38d9f71eb4428f69a36aecae4dfc3f7d +size 89828 diff --git a/raw/rel-18/23_series/23700-48/34d7353cac3d344f71ad82bd1eda40d1_img.jpg b/raw/rel-18/23_series/23700-48/34d7353cac3d344f71ad82bd1eda40d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35789ab892d7ac7540b4d1f78c44e78ecd5846ea --- /dev/null +++ b/raw/rel-18/23_series/23700-48/34d7353cac3d344f71ad82bd1eda40d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d5d26760619cfc6f965d34d5594af3221437255e9986ac6af5b326cbeb7bbb9 +size 84852 diff --git a/raw/rel-18/23_series/23700-48/3750b0149a6380885998ab3ca6a8787c_img.jpg b/raw/rel-18/23_series/23700-48/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceaaffabdc7ec667dfa60de0f32772720254b7bb --- /dev/null +++ b/raw/rel-18/23_series/23700-48/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e013ffe071f30301301c540e2d0d4f2efaa1149e7d4ee5ea50c3d9223c5b7b07 +size 187291 diff --git a/raw/rel-18/23_series/23700-48/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/raw/rel-18/23_series/23700-48/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6407733830a17ac064fcff718f64d65c5595addb --- /dev/null +++ b/raw/rel-18/23_series/23700-48/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a46d82ed567d10be4b0f7dd32eff32a02af9544059c388728a36e603bbc15c3b +size 110172 diff --git a/raw/rel-18/23_series/23700-48/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/raw/rel-18/23_series/23700-48/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d6932013121871e4c140833b9d275b196b9d48c --- /dev/null +++ b/raw/rel-18/23_series/23700-48/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02a3746b5b0632c1c2a5b6ea652f62815077ef43eb02affa1c7836ff766b0021 +size 78296 diff --git a/raw/rel-18/23_series/23700-48/427095219f3706148e8c03f1013eaec8_img.jpg b/raw/rel-18/23_series/23700-48/427095219f3706148e8c03f1013eaec8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..715d8703e734fe3c215553cbb50c5a34ff8f9dd9 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/427095219f3706148e8c03f1013eaec8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ab3bd927503d18f2aed63374762b83984bb824f1523ac0bc7aac8bf60abee3c +size 67042 diff --git a/raw/rel-18/23_series/23700-48/48090d8f1db2e826aaa740035aa12ecb_img.jpg b/raw/rel-18/23_series/23700-48/48090d8f1db2e826aaa740035aa12ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..786cddcfd54e1ebfe1c63aa9297439208d3c5440 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/48090d8f1db2e826aaa740035aa12ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f9f33c24b0840e60349a5c99484911a75b681e4558c91c16a89e973bae02a35 +size 121883 diff --git a/raw/rel-18/23_series/23700-48/4b87467ad9642943235f48f7d4b59449_img.jpg b/raw/rel-18/23_series/23700-48/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a36ea2a8b097375dbbc685a29521af0b5b1815ef --- /dev/null +++ b/raw/rel-18/23_series/23700-48/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b6fffd43c3a666c3b53621582ee67d33f623b32c6aaa57eafbd07d4b8c34e8b +size 68414 diff --git a/raw/rel-18/23_series/23700-48/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/raw/rel-18/23_series/23700-48/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47b404ecca2bc31126221a3b59124caf9ae41d08 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6188d37c88257d1b9a3f34c5c0899c110699206ee9d0122e30ad899c1bddf7ab +size 65693 diff --git a/raw/rel-18/23_series/23700-48/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/raw/rel-18/23_series/23700-48/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fea1fbc205936623bdd2b822c2b360c35239d2f --- /dev/null +++ b/raw/rel-18/23_series/23700-48/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3938a7c96ab08f0ba5e06c8cb050ca6861ad2706507acc2d63f8dcaf603db600 +size 51446 diff --git a/raw/rel-18/23_series/23700-48/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/raw/rel-18/23_series/23700-48/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebdfa5979c61e20c2e48c3789fcd12f0d5eecad9 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1dc6bb34dcf33a72455238efc634b67c8d899c2f8a05ca6ad5f21c6cdb3f162 +size 63186 diff --git a/raw/rel-18/23_series/23700-48/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-48/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de75664b3f44976d6678cee0779d383b98003d13 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e1e8186a4748d32b76e5bbda3d429694804f4f56133335eef1b29d6e7b16fc9 +size 10101 diff --git a/raw/rel-18/23_series/23700-48/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-48/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..474088002f241fff2759ad877d40cef5e0d85323 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:749cfb547ae424a3470485259f8e1b911265b6b1d1408520050ee2cb59d9cceb +size 5700 diff --git a/raw/rel-18/23_series/23700-48/649426750a89fa0e5d7c1736d5cf72c6_img.jpg b/raw/rel-18/23_series/23700-48/649426750a89fa0e5d7c1736d5cf72c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e181b668ad1d5cd6d5260a8f61716db0d0111619 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/649426750a89fa0e5d7c1736d5cf72c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e65f49937902f8ab71d42b0237e835b83b917cfa36a416b33df014df29df52 +size 57498 diff --git a/raw/rel-18/23_series/23700-48/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg b/raw/rel-18/23_series/23700-48/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21c56b98df0f77e074ee26c5f3d5486dd52fc8cf --- /dev/null +++ b/raw/rel-18/23_series/23700-48/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8157d3e7f7d36c801821ee447b6531984410067ac404d298c7666c6b326892e9 +size 44979 diff --git a/raw/rel-18/23_series/23700-48/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/raw/rel-18/23_series/23700-48/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e44a7258a126ab819a498e3b06893832438a65b2 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f626786248d5279dd452ef3694c9f2989fbeb465f27f835602c7263f90e68c6c +size 188984 diff --git a/raw/rel-18/23_series/23700-48/6c03366230af7163bc0866430f8b20c2_img.jpg b/raw/rel-18/23_series/23700-48/6c03366230af7163bc0866430f8b20c2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf42c20428b9a870af9c60cf4dd04c3d85e7c82a --- /dev/null +++ b/raw/rel-18/23_series/23700-48/6c03366230af7163bc0866430f8b20c2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e37b1c1bbe411f3ece3767c9460b97cdfbb54f69f88f3d010d17aef7336ae851 +size 64592 diff --git a/raw/rel-18/23_series/23700-48/6d67eee81b97a14e06a6fe57a95aff36_img.jpg b/raw/rel-18/23_series/23700-48/6d67eee81b97a14e06a6fe57a95aff36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e73a6aa86e7111fc2112d23899a557efb299a43 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/6d67eee81b97a14e06a6fe57a95aff36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec8479e5896d5fa522305e21046e48bcf9466a6fa3ca87eac81cef00425d6ad6 +size 80138 diff --git a/raw/rel-18/23_series/23700-48/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/raw/rel-18/23_series/23700-48/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cd487fdf3880a607b59541aa18a0ea6e315af2e --- /dev/null +++ b/raw/rel-18/23_series/23700-48/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4f218db552b1eeb6f99a7ce26db778884f32a4b81a1a266e5898849d9289d57 +size 69365 diff --git a/raw/rel-18/23_series/23700-48/7dfe05137c554aca6bed20d67e52d739_img.jpg b/raw/rel-18/23_series/23700-48/7dfe05137c554aca6bed20d67e52d739_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e561b678a3461f46421d905e8bc5435e9bf4091d --- /dev/null +++ b/raw/rel-18/23_series/23700-48/7dfe05137c554aca6bed20d67e52d739_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1c1ff693fa9e45ad874e9ac18d864ab7aa8b28e0dfbeca460d2dff147592ee5 +size 44648 diff --git a/raw/rel-18/23_series/23700-48/86bd357c573c9696393f5bde4d4cce4f_img.jpg b/raw/rel-18/23_series/23700-48/86bd357c573c9696393f5bde4d4cce4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e12c89e0a8dbe47c61856c25ff326261c0d3f8ea --- /dev/null +++ b/raw/rel-18/23_series/23700-48/86bd357c573c9696393f5bde4d4cce4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7b7bea1c5bf9bbd112cad78b6de87abebec6c1f318320c80a6bc1c08d05c8a +size 90581 diff --git a/raw/rel-18/23_series/23700-48/879d68959f0c0ba370ef82447298ba17_img.jpg b/raw/rel-18/23_series/23700-48/879d68959f0c0ba370ef82447298ba17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c83cc4e6145317baa8fc6f8a8ab6feae5007880e --- /dev/null +++ b/raw/rel-18/23_series/23700-48/879d68959f0c0ba370ef82447298ba17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:049845faf3e9aa180146e5ddd8b8ceac8f80a6bb3e76069a04be041e5c69d915 +size 61832 diff --git a/raw/rel-18/23_series/23700-48/92724c769da9d46b730fde1a6dccb023_img.jpg b/raw/rel-18/23_series/23700-48/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b510651dd41f66044f582cc3eb43e9b34c739fd2 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc5ba90f26b09150d1e72a4f4b598f79167d66d50cc9ad279c08af5487c059c6 +size 162331 diff --git a/raw/rel-18/23_series/23700-48/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/raw/rel-18/23_series/23700-48/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14cd524cf46264dc4691702aef22c6429cd0d7f9 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be1097497776b2d492a354d4243915063885655d1b3971d0029a95c41b631f88 +size 54132 diff --git a/raw/rel-18/23_series/23700-48/9958beca8f65818eb0ff893647af94de_img.jpg b/raw/rel-18/23_series/23700-48/9958beca8f65818eb0ff893647af94de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..078edd7fa48483c86fd5ed150867ea92fef01529 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/9958beca8f65818eb0ff893647af94de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e7ad495dcc8805e157ff38869f282a41c6815f24ca14bbbfd79593077877ce0 +size 65039 diff --git a/raw/rel-18/23_series/23700-48/99781d878388c3e0f359b1d6ce14119c_img.jpg b/raw/rel-18/23_series/23700-48/99781d878388c3e0f359b1d6ce14119c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae6990f24ed23b3f62abd1fb246c4e28cd856f6e --- /dev/null +++ b/raw/rel-18/23_series/23700-48/99781d878388c3e0f359b1d6ce14119c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f56d24830aa826b072defdf0d98760bd8a4f6c77d61b911adf15959565527fec +size 45260 diff --git a/raw/rel-18/23_series/23700-48/99a0eddf16e836f411661acee6facd17_img.jpg b/raw/rel-18/23_series/23700-48/99a0eddf16e836f411661acee6facd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c1462b4fcec755758592ee5006e4230c2a9e043 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/99a0eddf16e836f411661acee6facd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac7292b800c7c589e0035a8f8270a6baf06d803a2a3d872a83ae9ce412e48495 +size 38130 diff --git a/raw/rel-18/23_series/23700-48/9b069184e680aac7a22df55de63370fa_img.jpg b/raw/rel-18/23_series/23700-48/9b069184e680aac7a22df55de63370fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c692b43f52f2c7e5acb55cb1f6386f700041f607 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/9b069184e680aac7a22df55de63370fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9c0f14430dd456c568cbd08764eb7ae1d6b0a1030cfcb18268f421cc532f6d9 +size 80422 diff --git a/raw/rel-18/23_series/23700-48/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/raw/rel-18/23_series/23700-48/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed87062f8642b458e375709785992a8b2594244d --- /dev/null +++ b/raw/rel-18/23_series/23700-48/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:699fc01b1bdef918eac158960641aebe89076b7004aaa3237b3fb331d3118759 +size 78974 diff --git a/raw/rel-18/23_series/23700-48/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/raw/rel-18/23_series/23700-48/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11d7a10bf58f74a3161a4d151f90cbbbadd4a1e1 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4925a9ef89d5224baaee5acb1b93458e3a1f577b499d81cdc4e89c73b41a445f +size 218025 diff --git a/raw/rel-18/23_series/23700-48/9d47fe89bc71acebde670ea760ee6ffb_img.jpg b/raw/rel-18/23_series/23700-48/9d47fe89bc71acebde670ea760ee6ffb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e564f0457fdacfef0004ea8e5e141ab71e59aef --- /dev/null +++ b/raw/rel-18/23_series/23700-48/9d47fe89bc71acebde670ea760ee6ffb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28172b19428c6d4b27bdfcd5559b466d771bd6589f2089f7d3ace1cb0411f502 +size 99076 diff --git a/raw/rel-18/23_series/23700-48/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/raw/rel-18/23_series/23700-48/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7831ee780b9e887a33c10cd893cc2e285ac2b645 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1668045c391cccc827bbea611bf67391ce0fc2a096134b2e6da0224a64e4cfcc +size 111444 diff --git a/raw/rel-18/23_series/23700-48/9f862801bce82634d3b5a1e0a195a799_img.jpg b/raw/rel-18/23_series/23700-48/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd505bcc695811159bbc055e2462bcdb0b4fa9c6 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a88d91bd1256b402b495a5b2816f4333530a0b6d1a6716f7f11ea19b0e25b34e +size 30308 diff --git a/raw/rel-18/23_series/23700-48/a04f61f63e7b6e8e7fbbe222f0534ce6_img.jpg b/raw/rel-18/23_series/23700-48/a04f61f63e7b6e8e7fbbe222f0534ce6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40e01066410cc40fc6d0bc45cd9edb6966edfcfd --- /dev/null +++ b/raw/rel-18/23_series/23700-48/a04f61f63e7b6e8e7fbbe222f0534ce6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9029d531207527484a665b62b59bce0e07e8a8d1b576257a8cdd726092b62aa +size 71526 diff --git a/raw/rel-18/23_series/23700-48/a0bd5927fc9594395881eedffd55129a_img.jpg b/raw/rel-18/23_series/23700-48/a0bd5927fc9594395881eedffd55129a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..945fe8f2f60a6fded0358022bc239541510ee719 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/a0bd5927fc9594395881eedffd55129a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a6d4fbf0cda6ba23b37c67b9c1a42623075e6d301ac2aff965a44adf679e125 +size 75599 diff --git a/raw/rel-18/23_series/23700-48/a47713c2491e6ce619259ed2f196fd24_img.jpg b/raw/rel-18/23_series/23700-48/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ee5661a9350760c783d3a7cc7aacabac0bb874f --- /dev/null +++ b/raw/rel-18/23_series/23700-48/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce2381f635347cc1ef14988ff00a73681d045bbfd9b93f5c61e4d7ed91b517ef +size 79680 diff --git a/raw/rel-18/23_series/23700-48/ad555483986d7170a46ce72d164b5bc8_img.jpg b/raw/rel-18/23_series/23700-48/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d787c11d0093be9327f7b441989398076ec3e32 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:724e5bad9ec92b3382fc3e78f2a1fbd2060412caf2a42838f88d9e0c130a3d68 +size 56122 diff --git a/raw/rel-18/23_series/23700-48/b0f7b7a99fad9dffaf1b3dc5e4d01c86_img.jpg b/raw/rel-18/23_series/23700-48/b0f7b7a99fad9dffaf1b3dc5e4d01c86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..caecb4b1cb1c43bf06b846aafed3761ef8ff6b7a --- /dev/null +++ b/raw/rel-18/23_series/23700-48/b0f7b7a99fad9dffaf1b3dc5e4d01c86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:017b2e31abb5c794ff3b4bd08b6347eeb0ecef4de9e465f1d7120badba241c06 +size 156399 diff --git a/raw/rel-18/23_series/23700-48/b49477e8f148b5ef044a2fd5a43528f6_img.jpg b/raw/rel-18/23_series/23700-48/b49477e8f148b5ef044a2fd5a43528f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8941d1d75da4da2ebd3e65735faea278df577ac --- /dev/null +++ b/raw/rel-18/23_series/23700-48/b49477e8f148b5ef044a2fd5a43528f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e629569b3b1e1d4dce7d842e52d1a696b47cd9b6be65cc9346c2a8dfa1b39a9 +size 68080 diff --git a/raw/rel-18/23_series/23700-48/b87818c8505328b198d035761bbc3f2d_img.jpg b/raw/rel-18/23_series/23700-48/b87818c8505328b198d035761bbc3f2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00ec400145f8d9087c87b1123849c56e96cc9e28 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/b87818c8505328b198d035761bbc3f2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d083d0deb18d6a094a3f49f50ac1f57471dafb477fa58bc956c85c8cfb4120d +size 50829 diff --git a/raw/rel-18/23_series/23700-48/bc92832923e394e43c69264e7c66d919_img.jpg b/raw/rel-18/23_series/23700-48/bc92832923e394e43c69264e7c66d919_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b66cd8f006023088b4eb8d9fa3e67b3181109825 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/bc92832923e394e43c69264e7c66d919_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a559226ac8f0a0bf665f1b75206006102ce9fb98df23a12aad713cd688afedd0 +size 26022 diff --git a/raw/rel-18/23_series/23700-48/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg b/raw/rel-18/23_series/23700-48/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b924ee4ce5b23c86ff1661e498c07d440c014a3 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b085adbf86614b53d55f228e3e2c86f423cc5100ae6788550e989c5a7360a38 +size 59756 diff --git a/raw/rel-18/23_series/23700-48/c0ca823603794512478906b302176bca_img.jpg b/raw/rel-18/23_series/23700-48/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c77b2359e193870d5e72cdd0363ea49796048d18 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:030b00a135dcd12e781a27f781899c785b64231ba5ea541c3a250a53cac0b5a8 +size 38559 diff --git a/raw/rel-18/23_series/23700-48/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg b/raw/rel-18/23_series/23700-48/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3bae2231f28623f71071d361f78d3fa377b69a4 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a975f79b0fff84046e2a2acd4e4a97665a036943277e128bbf3ebe60527963b6 +size 22370 diff --git a/raw/rel-18/23_series/23700-48/c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg b/raw/rel-18/23_series/23700-48/c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f2f132fb4e7d087cf833819ffd598cd6fd260c1 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/c36c9f3fd6dfe6c3116a5b86b6ab0877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df2b6a25341a8c8447e0bbd7495127ed247c3e270cfb29e91d808eb18023a8f6 +size 172209 diff --git a/raw/rel-18/23_series/23700-48/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg b/raw/rel-18/23_series/23700-48/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b1e7f42fd96a05a64961ed31669527a74d6e7f1 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/c5d9ee57705b6598bd43f9c075fec3c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51c4657dc3220f7e27d5a887a61244903874029e81f30bc25a45dc02380a8ff1 +size 50828 diff --git a/raw/rel-18/23_series/23700-48/c85b57b2414f341860dfc338e1cf2509_img.jpg b/raw/rel-18/23_series/23700-48/c85b57b2414f341860dfc338e1cf2509_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d4c952bc7fc3c37b903a2908076cad6b4616d52 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/c85b57b2414f341860dfc338e1cf2509_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5228671b11c916a97e86eaf3c44a27d4eaee2ca512a59d0d79efe1ccda494d2 +size 90602 diff --git a/raw/rel-18/23_series/23700-48/c973a830a03be42682a331ad3215d6c6_img.jpg b/raw/rel-18/23_series/23700-48/c973a830a03be42682a331ad3215d6c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86fc91f70ba45c2e0a541bc635b602acf5b19422 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/c973a830a03be42682a331ad3215d6c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7256276210d97b3aab087ea3afc0934fbf71f70d385d16d520974f4a2fd6b5bd +size 61416 diff --git a/raw/rel-18/23_series/23700-48/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/raw/rel-18/23_series/23700-48/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bccc5b6ce38896690be3939591ebe7200a6a72e2 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63db863491524b6ad95eaa142607e038708faaf647b545bde5416084f96d5746 +size 47419 diff --git a/raw/rel-18/23_series/23700-48/cdcbafff3cef7d54a001e3d0a4d9841e_img.jpg b/raw/rel-18/23_series/23700-48/cdcbafff3cef7d54a001e3d0a4d9841e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79ebea68e3eb0e630ea4e8053a079ecded22404a --- /dev/null +++ b/raw/rel-18/23_series/23700-48/cdcbafff3cef7d54a001e3d0a4d9841e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bcb08e48ec59d29ee36e61f2e62dc3294f937614b9ad687edba90dca9fb5207 +size 59471 diff --git a/raw/rel-18/23_series/23700-48/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/raw/rel-18/23_series/23700-48/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d41738fa1bab1d4e973846864a0deaa0f80e8997 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b65d77463a9a2ee691caec6afe36778020af1a7e97b1f198643d1e36256779b +size 44769 diff --git a/raw/rel-18/23_series/23700-48/d1be394c67ec994c0c8529d29ea3e9cc_img.jpg b/raw/rel-18/23_series/23700-48/d1be394c67ec994c0c8529d29ea3e9cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbfa6f1931eb3aa5600f4721e55e2eea457952e7 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/d1be394c67ec994c0c8529d29ea3e9cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7331e7e52558f834af39c458422e5d8a4135a5f29fc562bff73c532cc94ada38 +size 45870 diff --git a/raw/rel-18/23_series/23700-48/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg b/raw/rel-18/23_series/23700-48/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c88d18f7737b031ba86d30820a8fcf91c54d1ad2 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7322f636d6d9dd466f388852b038b19aca67d77fad1b3883e8d160dd7e76b500 +size 46849 diff --git a/raw/rel-18/23_series/23700-48/d5f4af137f0f2f002c86899367868c81_img.jpg b/raw/rel-18/23_series/23700-48/d5f4af137f0f2f002c86899367868c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25070fb061e85f42595c80507226316f0d667489 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/d5f4af137f0f2f002c86899367868c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b272b20d1193a715a7a1ecd9e753308397d57bde9766db36d079cc0483816353 +size 53477 diff --git a/raw/rel-18/23_series/23700-48/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/raw/rel-18/23_series/23700-48/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae5b4d35310af40a1d4e465534fce9529aeeb62b --- /dev/null +++ b/raw/rel-18/23_series/23700-48/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ff280620d1d5edbd1ba4ca1c28b44cf170419b1e5c4876c0333068df37416cc +size 47941 diff --git a/raw/rel-18/23_series/23700-48/dbe8bef1723acb3e03e8616be4faf939_img.jpg b/raw/rel-18/23_series/23700-48/dbe8bef1723acb3e03e8616be4faf939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f10bfb685100a80297a7eaf98af0ac70dc7b48f --- /dev/null +++ b/raw/rel-18/23_series/23700-48/dbe8bef1723acb3e03e8616be4faf939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32592c33779d6200866b8d028a668b8ee6f608508025006569a4b68eb012e94b +size 49544 diff --git a/raw/rel-18/23_series/23700-48/dd5771673aececa53d42ece89218299d_img.jpg b/raw/rel-18/23_series/23700-48/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ca914a3c0f5cdd1d4feb3545c04dfddd3922e24 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa934db8d977d1b0fe90da9429a640b360b712e469a0dff8eb037dd1bed93f28 +size 85216 diff --git a/raw/rel-18/23_series/23700-48/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg b/raw/rel-18/23_series/23700-48/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bca3e31dc924061dcc364eb4e04a1f44a462c4c --- /dev/null +++ b/raw/rel-18/23_series/23700-48/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ba3aec5e91ad263d57e13c74c2e2694fab34747921f6db484e416b856a0f2d0 +size 88282 diff --git a/raw/rel-18/23_series/23700-48/ddcdc1712375261ba1d89165fdf12aa6_img.jpg b/raw/rel-18/23_series/23700-48/ddcdc1712375261ba1d89165fdf12aa6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..636c1202edb6b5ad39ddbdd2cfc151a832603a81 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/ddcdc1712375261ba1d89165fdf12aa6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00b59dab95ed5fe122220acd598c637ca8b2288bccd936e5775bedd624a9590c +size 49702 diff --git a/raw/rel-18/23_series/23700-48/de18140c2e0030a43004b58338467655_img.jpg b/raw/rel-18/23_series/23700-48/de18140c2e0030a43004b58338467655_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f0186e3e0a5c03e6a3a1e5fcf324200ccb9922c --- /dev/null +++ b/raw/rel-18/23_series/23700-48/de18140c2e0030a43004b58338467655_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f4a334eb5dc5ff242733a8659630d2a08f9e6d7e50c9e2be45a50dc3fb25c36 +size 53313 diff --git a/raw/rel-18/23_series/23700-48/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/raw/rel-18/23_series/23700-48/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..591e2c8181d33f17a514a522ecc18c236c4c5877 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ef3f7484cdd0493bada5426085ca9121caba584d5c287237202721177fbfe61 +size 151998 diff --git a/raw/rel-18/23_series/23700-48/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg b/raw/rel-18/23_series/23700-48/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a76cd52b6a25fd193d5e8a2d0af4b12e647061e3 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/dfe74512a9c9fb620f72c9dbc22874aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f169e8ce560428ac078161e99f0bad9bb4b0d8585da4f568743f3b7e9fc5bc7 +size 84713 diff --git a/raw/rel-18/23_series/23700-48/efb282bed9f06eef1987a14fb27bc599_img.jpg b/raw/rel-18/23_series/23700-48/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44cb229bbc1b0cc94158c333d528754736101562 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b33f52c17248208572fb58718f5f825cb4bd8d659403b5b4968c4f6fec64109e +size 68927 diff --git a/raw/rel-18/23_series/23700-48/f1ba1e68228ebd4c3109371574a723e6_img.jpg b/raw/rel-18/23_series/23700-48/f1ba1e68228ebd4c3109371574a723e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95735a8a4a4ca8ba91ac110f4e306f101c0ab650 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/f1ba1e68228ebd4c3109371574a723e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e889d3356b6d6af9abd2786024006c03fc3a72ba38d95d3bab1f30551b16116f +size 67250 diff --git a/raw/rel-18/23_series/23700-48/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/raw/rel-18/23_series/23700-48/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2abb9661c50c17f0aa3340481c2993a776d5973 --- /dev/null +++ b/raw/rel-18/23_series/23700-48/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b309fb5c1e333b4cad3e9825c19ac3306bd13770ceff3fa9ce4c62f82b1248e6 +size 42072 diff --git a/raw/rel-18/23_series/23700-48/fcc757566216206ceddbd6c775e8db02_img.jpg b/raw/rel-18/23_series/23700-48/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac2f45c435958a23ce18c96d1afd05439ac4943a --- /dev/null +++ b/raw/rel-18/23_series/23700-48/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1370b60054318ff2b9c4c197fc4041a2dfc90205ef65c4a152cfdbc6c0a67a5e +size 74467 diff --git a/raw/rel-18/23_series/23700-48/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/raw/rel-18/23_series/23700-48/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbc75cbb156d36857c75002fb348108f7424593b --- /dev/null +++ b/raw/rel-18/23_series/23700-48/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f8ac17c7584c247348cda97026241d07b3d08e95800c9e0bd15f7d5c92c7522 +size 197263 diff --git a/raw/rel-18/23_series/23700-53/raw.md b/raw/rel-18/23_series/23700-53/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8154577116230698711be6a0e4f7dea3631e77d0 --- /dev/null +++ b/raw/rel-18/23_series/23700-53/raw.md @@ -0,0 +1,3324 @@ + + +# 3GPP TR 23.700-53 V18.0.0 (2022-12) + +Technical Report + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on access traffic steering, switching and splitting support in the 5G system architecture; Phase 3 (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a small red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions of terms and abbreviations ..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 10 | +| 3.2 Abbreviations ..... | 10 | +| 4 Architectural Assumptions and Requirements..... | 10 | +| 5 Key Issues ..... | 10 | +| 5.1 Key Issue #2: New steering functionalities for non-TCP traffic..... | 10 | +| 5.1.1 Description ..... | 10 | +| 5.2 Key Issue #3: Support of redundant traffic steering ..... | 11 | +| 5.2.1 Description ..... | 11 | +| 5.3 Key Issue #5: Switching traffic of an MA PDU Session between two non-3GPP access paths ..... | 12 | +| 5.3.1 Description ..... | 12 | +| 5.4 Key Issue #6: Supporting MA PDU Session with one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC..... | 13 | +| 5.4.1 Description ..... | 13 | +| 6 Solutions..... | 14 | +| 6.0 Mapping of Solutions to Key Issues ..... | 14 | +| 6.1 Solution #3.1: New steering mode - Redundancy steering mode with packet loss rate ..... | 14 | +| 6.1.1 Introduction ..... | 14 | +| 6.1.2 High-level Description ..... | 14 | +| 6.2 Solution #6.1: Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC ..... | 15 | +| 6.2.1 Introduction ..... | 15 | +| 6.2.2 High-level Description ..... | 15 | +| 6.2.3 Impacts on services, entities, interfaces and IETF protocols ..... | 17 | +| 6.3 Solution #2.1: MP-DCCP based Steering Functionality..... | 17 | +| 6.3.1 Introduction ..... | 17 | +| 6.3.2 Description ..... | 17 | +| 6.3.3 MA PDU Session Establishment procedure..... | 21 | +| 6.3.4 MA PDU Session Modification procedure..... | 23 | +| 6.3.5 Example of MP-DCCP-LL Operation..... | 23 | +| 6.3.6 Support of Steering Modes ..... | 26 | +| 6.3.7 Support of Re-Ordering ..... | 26 | +| 6.3.8 User-plane overhead..... | 27 | +| 6.3.9 Co-existence with MPTCP and ATSSS-LL ..... | 27 | +| 6.3.10 Impacts on services, entities, interfaces and IETF protocols ..... | 27 | +| 6.4 Solution #3.2: Redundant traffic steering triggered by AF ..... | 28 | +| 6.4.1 Introduction ..... | 28 | +| 6.4.2 High-level Description ..... | 28 | +| 6.4.3 Procedures ..... | 29 | +| 6.4.3.0 General..... | 29 | +| 6.4.3.1 Procedure of AF providing PLR threshold value via Nnef_TrafficInfluence_Create/Update operation service..... | 29 | +| 6.4.3.2 Procedure of AF providing PLR threshold value via Nnef_AFsessionWithQoS_Create/Update operation service..... | 30 | +| 6.4.4 Impacts on Existing Nodes and Functionality..... | 31 | +| 6.5 Solution #3.3: New traffic duplication steering mode ..... | 31 | +| 6.5.1 Introduction ..... | 31 | +| 6.5.2 High-level Description ..... | 31 | +| 6.5.3 Procedures ..... | 33 | +| 6.5.3.1 AF providing traffic duplication parameters ..... | 33 | + +| | | | +|---------|---------------------------------------------------------------------------------------------------------------|----| +| 6.5.3.2 | Procedure of AF providing traffic duplication parameters via Nnef_TrafficInfluence_Create/Update service..... | 34 | +| 6.5.4 | Impacts on Existing Nodes and Functionality..... | 34 | +| 6.6 | Solution #3.4: Redundant steering mode with duplication information and trigger mechanisms ..... | 35 | +| 6.6.1 | Introduction ..... | 35 | +| 6.6.2 | High-level Description ..... | 35 | +| 6.6.2.1 | Provision of RSM related parameters to UE and UPF ..... | 35 | +| 6.6.2.2 | Triggering the usage of a MA PDU Session with RSM ..... | 36 | +| 6.6.3 | Procedures ..... | 36 | +| 6.6.4 | Impacts on Existing Nodes and Functionality..... | 37 | +| 6.7 | Solution #5.1: Support traffic switching between two non-3GPP paths..... | 38 | +| 6.7.1 | Introduction ..... | 38 | +| 6.7.2 | High-level Description ..... | 38 | +| 6.7.3 | Procedures ..... | 38 | +| 6.7.4 | Impacts on Existing Nodes and Functionality..... | 40 | +| 6.8 | Solution #5.2: Delaying UDM Registration until non-3GPP access switching completes..... | 41 | +| 6.8.1 | Introduction ..... | 41 | +| 6.8.2 | High-level Description ..... | 41 | +| 6.8.3 | Procedures ..... | 41 | +| 6.8.4 | Impacts on Existing Nodes and Functionality..... | 43 | +| 6.9 | Solution #5.3: Path switching between non-3GPP accesses..... | 43 | +| 6.9.1 | Introduction ..... | 43 | +| 6.9.2 | High-level Description ..... | 43 | +| 6.9.3 | Procedures ..... | 44 | +| 6.9.4 | Impacts on Existing Nodes and Functionality..... | 46 | +| 6.10 | Solution #5.4: Non-3GPP access path switching in MA PDU Session ..... | 47 | +| 6.10.1 | Introduction ..... | 47 | +| 6.10.2 | High-level Description ..... | 47 | +| 6.10.3 | MA PDU Session Access Path Switching procedure..... | 48 | +| 6.10.4 | Impacts on Existing Nodes and Functionality..... | 49 | +| 6.11 | Solution #2.2: MPQUIC steering functionality using UDP proxying over HTTP ..... | 50 | +| 6.11.1 | Introduction ..... | 50 | +| 6.11.2 | High-level Description ..... | 51 | +| 6.11.3 | Procedures ..... | 54 | +| 6.11.4 | User-plane overhead..... | 58 | +| 6.11.5 | Co-existence with MPTCP and ATSSS-LL ..... | 60 | +| 6.11.6 | Handling of out-of-order delivery ..... | 61 | +| 6.11.7 | Handling of duplicated packets ..... | 61 | +| 6.11.8 | Impacts on Existing Nodes and Functionality..... | 62 | +| 6.12 | Solution #2.3: MPQUIC steering functionality using IP proxying over HTTP..... | 62 | +| 6.12.1 | Introduction ..... | 62 | +| 6.12.2 | High-level Description ..... | 63 | +| 6.12.3 | Procedures ..... | 66 | +| 6.12.4 | User-plane overhead..... | 70 | +| 6.12.5 | Co-existence with MPTCP and ATSSS-LL ..... | 70 | +| 6.12.6 | Handling of out-of-order delivery ..... | 70 | +| 6.12.7 | Handling of duplicated packets ..... | 71 | +| 6.12.8 | Impacts on Existing Nodes and Functionality..... | 72 | +| 6.13 | Solution #2.4: Limiting MA-PDU Per-Packet Overhead..... | 72 | +| 6.13.1 | Introduction ..... | 72 | +| 6.13.2 | High Level Description ..... | 73 | +| 6.13.3 | Procedures ..... | 73 | +| 6.13.4 | Impacts on Existing Nodes and Functionality..... | 74 | +| 6.14 | Solution #3.5: Redundant Traffic Steering Mode Activation/Deactivation..... | 74 | +| 6.14.1 | Introduction ..... | 74 | +| 6.14.2 | High Level Description ..... | 74 | +| 6.14.3 | Procedures ..... | 76 | +| 6.14.4 | Impacts on Existing Nodes and Functionality..... | 77 | +| 6.15 | Solution #3.6: Redundant steering mode ..... | 77 | +| 6.15.1 | Introduction ..... | 77 | +| 6.15.2 | High-level Description ..... | 77 | +| 6.15.3 | Procedures ..... | 78 | +| 6.15.4 | Impacts on Existing Nodes and Functionality..... | 78 | + +| | | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------|-----| +| 6.16 | Solution #5.5: Non-3GPP path switch during Registration in new non-3GPP access..... | 78 | +| 6.16.1 | Introduction ..... | 78 | +| 6.16.2 | High-level Description ..... | 78 | +| 6.16.3 | Procedures ..... | 78 | +| 6.16.4 | Impacts on Existing Nodes and Functionality..... | 80 | +| 6.17 | Solution #5.6: Consolidated solution for traffic switching between two non-3GPP access paths..... | 81 | +| 6.17.1 | Introduction ..... | 81 | +| 6.17.2 | High-level Description ..... | 81 | +| 6.17.3 | Procedures ..... | 81 | +| 6.17.4 | Impacts on Existing Nodes and Functionality..... | 83 | +| 6.18 | Solution #3.7: Suspending the Redundancy Steering Mode ..... | 84 | +| 6.18.1 | Introduction ..... | 84 | +| 6.18.2 | High-level Description ..... | 84 | +| 6.18.3 | Procedures ..... | 85 | +| 6.18.4 | Impacts on Existing Nodes and Functionality..... | 85 | +| 7 | Evaluation ..... | 85 | +| 7.1 | Evaluation for KI #2: New steering functionalities for non-TCP traffic ..... | 85 | +| 7.1.1 | User Plane Performance Aspect..... | 85 | +| 7.1.2 | Summary of proposed steering functionalities ..... | 86 | +| 7.1.2.1 | Co-existence with MPTCP and ATSSS-LL ..... | 86 | +| 7.1.3 | Evaluation of steering functionalities for UDP traffic flows..... | 86 | +| 7.1.3.1 | General..... | 86 | +| 7.1.3.2 | Allocation of UPF resources..... | 86 | +| 7.1.3.3 | Connections between UE and UPF..... | 87 | +| 7.1.3.4 | Application visibility ..... | 88 | +| 7.1.3.5 | User-plane overhead ..... | 88 | +| 7.1.3.6 | Data encryption aspects ..... | 89 | +| 7.1.3.7 | Packet reordering and deduplication..... | 90 | +| 7.1.3.8 | IETF Support ..... | 90 | +| 7.2 | Evaluation for KI #3: Support of redundant traffic steering ..... | 91 | +| 7.2.1 | Considerations on RSM with Duplication Criteria ..... | 91 | +| 7.2.2 | Considerations on RSM without Duplication Criteria ..... | 91 | +| 7.2.3 | Considerations on RSM suspension ..... | 91 | +| 7.3 | Evaluation for KI #5: Switching traffic of an MA PDU Session between two non-3GPP access paths.. | 91 | +| 7.4 | Evaluation for KI #6: Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC
..... | 96 | +| 8 | Conclusions..... | 97 | +| 8.1 | Conclusions for KI #2: New steering functionalities for non-TCP traffic ..... | 97 | +| 8.2 | Conclusions for KI #3: Support of redundant traffic steering..... | 97 | +| 8.3 | Conclusions for KI #5: Switching traffic of an MA PDU Session between two non-3GPP access paths | 99 | +| 8.4 | Conclusions for KI #6: Supporting MA PDU Session with one 3GPP access path via 5GC and one non-
3GPP access path via ePDG/EPC ..... | 101 | + +| | | +|--------------------------------------|------------| +| Annex A: Change history ..... | 102 | +|--------------------------------------|------------| + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, certain modal verbs have the following meanings: + +**shall** indicates a mandatory requirement to do something + +**shall not** indicates an interdiction (prohibition) to do something + +NOTE 1: The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +NOTE 2: The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +**should** indicates a recommendation to do something + +**should not** indicates a recommendation not to do something + +**may** indicates permission to do something + +**need not** indicates permission not to do something + +NOTE 3: The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +**can** indicates that something is possible + +**cannot** indicates that something is impossible + +NOTE 4: The constructions "can" and "cannot" shall not to be used as substitutes for "may" and "need not". + +**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +NOTE 5: The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The purpose of this Technical Report is to enhance the ATSSS feature by investigating solutions that can support the following capabilities: + +- 1) Support new steering functionalities that can steer/switch/split non-TCP traffic flows (e.g. UDP traffic flows and IP traffic flows). Two types of such steering functionalities are studied: (i) a steering functionality based on the QUIC protocol and its multipath extensions, and (ii) a steering functionality based on the DCCP protocol and its multipath extensions. +- 2) Support redundant traffic steering for both GBR and non-GBR traffic flows. With redundant traffic steering, a traffic flow (GBR or non-GBR) can be replicated on multiple access paths and, therefore, can improve transmission reliability and reduce packet latency. +- 3) Support traffic switching between one non-3GPP access path, from a UE to a N3IWF in a PLMN, and another non-3GPP access path, from the UE to a TNGF in the same PLMN. +- 4) Support the establishment of a MA PDU Session with one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC. This is to complement the existing ATSSS capability that supports the establishment of a MA PDU Session with one non-3GPP access path via 5GC and one 3GPP access path via EPC. + +For each of the above capabilities, the conclusions of the study identify whether a solution is required for the normative phase and, if required, which solution to consider in the normative phase. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G system, Stage 2". +- [4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System". +- [5] 3GPP TR 23.700-93: "Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture; Phase 2". +- [6] IETF RFC 9000: "QUIC: A UDP-Based Multiplexed and Secure Transport". +- [7] IETF RFC 9001: "Using TLS to Secure QUIC". +- [8] IETF RFC 9002: "QUIC Loss Detection and Congestion Control". +- [9] IETF RFC 9221: "An Unreliable Datagram Extension to QUIC". +- [10] draft-ietf-quic-multipath: "Multipath Extension for QUIC". +- Editor's note:** The above document cannot be formally referenced until it is published as an RFC. +- [11] IETF RFC 4340: "Datagram Congestion Control Protocol (DCCP)". + +- [12] draft-ietf-tsvwg-multipath-dccp: "DCCP Extensions for Multipath Operation with Multiple Addresses". + +**Editor's note:** The above document cannot be formally referenced until it is published as an RFC. + +- [13] 3GPP TS 24.193: "Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3". +- [14] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3". +- [15] IETF RFC 4336: " Problem Statement for the Datagram Congestion Control Protocol (DCCP)". +- [16] Void. +- [17] IEEE AINAW, "Out-of-Order Transmission for In-Order Arrival Scheduling for Multipath TCP", DOI:10.1109/WAINA.2014.122. +- [18] Void. +- [19] IETF RFC 4341: "Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control". +- [20] IETF RFC 4342: "Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)". +- [21] IETF RFC 5622: "Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP)". +- [22] Void. +- [23] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3". +- [24] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane nodes". +- [25] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [26] 3GPP TR 23.793: "Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture". +- [27] IETF RFC 9298: "Proxying UDP in HTTP". +- [28] IETF RFC 9114: "Hypertext Transfer Protocol Version 3 (HTTP/3)". +- [29] IETF RFC 9297: "HTTP Datagrams and the Capsule Protocol". +- [30] IETF RFC 9220: "Bootstrapping WebSockets with HTTP/3". +- [31] draft-ietf-masque-connect-ip: "IP Proxying Support for HTTP". + +**Editor's note:** The above document cannot be formally referenced until it is published as an RFC. + +- [32] IETF RFC 5225: "RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite". +- [33] IETF RFC 6846: "RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)". +- [34] 3GPP TS 38.323: "Packet Data Convergence Protocol (PDCP) specification". +- [35] IETF RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)". + +# 3 Definitions of terms and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1], in TS 23.501 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] or in TS 23.501 [2]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +            + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], in TS 23.501 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1] or in TS 23.501 [2]. + +# 4 Architectural Assumptions and Requirements + +The study in this technical report is based on the following architectural requirements and assumptions: + +- The study takes the Rel-17 ATSSS architecture (see TS 23.501 [2]) as a baseline. +- It is assumed that an MA PDU Session is required for supporting all ATSSS capabilities. Only ATSSS enhancements using an MA PDU Session are considered. +- The study may impact the core network (5GC and/or EPC) but it shall not impact the access network (e.g. NG-RAN, W-5GAN, etc.). +- All ATSSS steering functionalities (existing and new) shall reside in the UE and in an UPF. Steering functionalities outside either of the UE or the UPF are not considered. +- Any new steering functionality shall be based on the multipath extensions of the QUIC or DCCP protocols as defined in IETF. +- New ATSSS capabilities shall either be able to co-exist with the existing ATSSS capabilities or any dependencies between new and existing capabilities shall be explicitly defined. +- The study considers, not only ATSSS-capable UEs, but also ATSSS-capable 5G-RGs. The conclusions of the study identify which aspects / solutions are applicable only to ATSSS-capable UEs and which are applicable only to ATSSS-capable 5G-RGs. +- The solutions proposed to KI#5 will also be analysed whether addresses the scenario of UE simultaneously moving of both IPsec peers in the same RAT-type (i.e. UE local IP address and the anchor N3IWF/TNGF change), since according to RFC 4555 [35] MOBIKE is not best suited. + +NOTE: Co-ordination with BBF and CableLabs will take place as needed during the study. + +# 5 Key Issues + +NOTE: The numbering of the key issues below corresponds to the numbering of the Work Tasks in the approved ATSSS\_ph3 study item (see SP-211612). + +## 5.1 Key Issue #2: New steering functionalities for non-TCP traffic + +### 5.1.1 Description + +This key issue aims at studying new steering functionalities (in addition to the existing ATSSS-LL and MPTCP steering functionalities defined in TS 23.501 [2]), which can be used to support steering, switching and splitting of non-TCP traffic flows (e.g. UDP traffic flows and IP traffic flows). Presently, traffic splitting of non-TCP traffic flows is not fully supported with the ATSSS-LL because this steering functionality may introduce out of order delivery, which can severely impact the transport performance. + +**Editor's note:** Whether support of steering, switching and splitting of Ethernet traffic flows is required is FFS. + +More specifically, this key issue aims to: + +- 1) Continue the Rel-17 study of the QUIC-based steering functionality and its multipath extensions by considering some of the aspects that were left open (see clause 8.2 of TR 23.700-93 [5]). The resolution of these aspects may lead to new solutions, in addition to those specified in TR 23.700-93 [5], and any of them should support per-packet splitting. For example, it will be considered whether the QUIC-based steering functionality will apply other IETF protocols, such as the MASQUE protocol, and whether a single multipath QUIC connection can support one or multiple steering modes. + +The study of the QUIC-based steering functionality is based on the QUIC protocol [6], its multipath extensions (e.g. draft-ietf-quic-multipath [10]) and, possibly, on other relevant documents specified by IETF, such as RFC 9001 [7], RFC 9002 [8], draft-ietf-quic-datagram [9]. + +Any security aspects associated with the QUIC protocol mandating the usage of TLS 1.3 for key exchange, authentication, and negotiation of security and performance parameters (see RFC 9001 [7]), will be studied in conjunction with SA WG3. + +- 2) Study a new steering functionality based on the DCCP protocol RFC 4340 [11] and its multipath extensions draft-ietf-tsvwg-multipath-dccp [12] that provide support for per-packet splitting. + +The conclusions of the study will identify which one of the above two steering functionalities may be specified in the normative phase. + +This key issue shall also consider the following additional aspects: + +- How the new steering functionalities can co-exist with MPTCP and ATSSS-LL; +- What is the impact on the user plane performance (e.g. additional overhead) for each one of the new steering functionalities; +- Whether it is needed and how to negotiate the support of the new steering functionalities between the UE and the network; +- Whether it is needed and how to enhance PCC rules, ATSSS rules and N4 rules to support the new steering functionalities; +- UE impacts in order to support each one of the new steering functionalities; +- How to treat out-of-order delivery caused by per packet-splitting. + +## 5.2 Key Issue #3: Support of redundant traffic steering + +### 5.2.1 Description + +This key issue is to enable the transmitter (UE for UL traffic and UPF for DL traffic) to support redundant traffic steering with duplication criteria, in order to improve reliability and latency. + +The key issue also studies potential duplication criteria, i.e. how to activate or deactivate packet transmission redundancy on both accesses with additional mechanisms. The duplication criteria are known to UE and UPF, e.g. + +allowing to decide which DL and/or UL packets need to be duplicated on all access paths of a MA PDU session and which ones not. + +This key issue aims to study the following issues: + +- How to support redundant traffic steering mode for different steering functionalities. + +NOTE: The redundant traffic steering mode does not apply to the ATSSS-LL steering functionality. + +- Whether new measurements are needed to support redundant traffic steering mode. +- Whether and which criteria for traffic duplication should be introduced in order to allow the UE and UPF to decide, e.g. which packets must be duplicated on all access paths of a MA PDU session and which packets must be send over only one access path. +- If duplication criteria are introduced, how ATSSS and MA rules should be modified to allow to indicate the duplication criteria to UE and UPF. +- How the UE and UPF operate based on the modified ATSSS and MA rules for both GBR and non-GBR traffic. This includes the definition of UE and UPF behaviours for the case in which traffic is not duplicated on both access paths as it does not fulfil the configured duplication criteria. +- Whether and how to introduce mechanisms to activate and deactivate packet duplication in a dynamic manner, e.g. triggered by network entities or application functions. +- How the receiver (UPF for UL traffic and UE for DL traffic) will treat duplicated packets. + +## 5.3 Key Issue #5: Switching traffic of an MA PDU Session between two non-3GPP access paths + +### 5.3.1 Description + +This key issue aims to study how the data traffic of an MA PDU Session can be switched between one non-3GPP access path, from the UE to a N3IWF in a PLMN, and another non-3GPP access path, from the UE to a TNGF in the same PLMN. + +The following topics are considered: + +- How the UE can register to 5GC in order to enable switching the traffic from one non-3GPP access path to another non-3GPP access path. +- How to switch the traffic of an MA PDU Session between one non-3GPP access path from the UE to a N3IWF and another non-3GPP access path from the UE to a TNGF in the same PLMN. This includes how the UE and the network take decision to perform the switch of the traffic. +- Study how existing steering modes and steering functionalities, as well as new steering modes and steering functionalities (defined in this TR) can be reused, or, if needed, be modified to allow switching the traffic from one non-3GPP access path to another non-3GPP access path. + +The study of the above topics will be based on the following assumptions: + +- Both non-3GPP access paths traverse the same PLMN. +- One non-3GPP access path is using an N3IWF, while the other non-3GPP access path is using a TNGF. +- After switching the traffic, only one UE registration via non-3GPP access may exist. +- If the UE is able to access the same PLMN directly using 3GPP radio technology, then the UE may have an MA PDU Session with three access paths (two non-3GPP and one 3GPP) for the duration of switching the traffic from a source non-3GPP access path to a target non-3GPP access path. +- Impact to the UE and network should be minimized. + +NOTE 1: In conclusion if time permits, it can be considered whether the selected solution enables also the traffic switching between one non-3GPP access path (e.g. from the UE to a N3IWF), and another non-3GPP access path (e.g. from the UE to a TNGF) per single access PDU session. + +## 5.4 Key Issue #6: Supporting MA PDU Session with one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC + +### 5.4.1 Description + +This key issue considers how to support the establishment of a MA PDU Session with one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC. A solution for this key issue complements the existing ATSSS solution that supports the establishment of a MA PDU Session with one non-3GPP access path via 5GC and one 3GPP access path via EPC (see clause 4.22.2.3 of TS 23.501 [2]). + +The key issue addresses the following aspects: + +- How to establish a MA PDU session with a non-3GPP access path over ePDG/EPC and a 3GPP access path over 5GC. +- How to establish an PDN Connection in EPC using the S2b procedures with untrusted non-3GPP access and designate this PDN Connection as user-plane resource associated with a MA PDU Session. +- How to transfer a non-3GPP access path over ePDG/EPC (while keeping the 3GPP access path over 5GC) to a trusted non-3GPP access path over 5GC. + +NOTE: Handover between non-3GPP of EPC and non-3GPP access of 5GC will not be defined. + +- The impact on UE, ePDG, EPC and 5GC. +- Which steering functionalities and which steering modes can be applied to an MA PDU Session with a non-3GPP access path over ePDG/EPC and a 3GPP access path over 5GC. + +It is assumed that: + +- The UE can attach to EPC via an ePDG using the S2b procedures (see clause 7.2 of TS 23.402 [25]) and can simultaneously register with 5GC over 3GPP access. +- The study is restricted to EPC attach using the S2b procedures via untrusted non-3GPP access. EPC attach using S2c procedures via untrusted non-3GPP access are not considered. +- Solutions are preferred that re-use (as much as possible) the existing concepts and procedures for enabling an MA PDU Session with one non-3GPP access path via 5GC and one 3GPP access path via EPC, as defined in clause 4.22.2.3 of TS 23.501 [2]. + +# 6 Solutions + +## 6.0 Mapping of Solutions to Key Issues + +**Table 6.0-1: Mapping of Solutions to Key Issues** + +| Solution # | Solution Title | Key Issue(s) | +|------------|-------------------------------------------------------------------------------|--------------| +| #2.1 | MP-DCCP based Steering Functionality | #2 (DCCP) | +| #2.2 | MPQUIC steering functionality using UDP proxying over HTTP | #2 (QUIC) | +| #2.3 | MPQUIC steering functionality using IP proxying over HTTP | #2 (QUIC) | +| #2.4 | Limiting MA-PDU Per-Packet Overhead | #2 | +| #3.1 | New steering mode - Redundancy steering mode with packet loss rate | #3 | +| #3.2 | Redundant traffic steering triggered by AF | #3 | +| #3.3 | New traffic duplication operation | #3 | +| #3.4 | Redundant steering mode with duplication information | #3 | +| #3.5 | Redundant Traffic Steering Mode Activation/Deactivation | #3 | +| #3.6 | Redundant steering mode | #3 | +| #3.7 | Suspending the Redundancy Steering Mode | #3 | +| #5.1 | Support traffic switching between two non-3GPP paths | #5 | +| #5.2 | Delaying UDM Registration until non-3GPP access switching completes | #5 | +| #5.3 | Path switching between non-3GPP accesses | #5 | +| #5.4 | Non-3GPP access path switching in MA PDU Session | #5 | +| #5.5 | Non-3GPP path switch during Registration in new non-3GPP access | #5 | +| #5.6 | Consolidated solution for traffic switching between two non-3GPP access paths | #5 | +| #6.1 | Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC | #6 | + +## 6.1 Solution #3.1: New steering mode - Redundancy steering mode with packet loss rate + +### 6.1.1 Introduction + +This solution addresses KI#3 on support of redundant traffic steering. + +### 6.1.2 High-level Description + +The redundancy steering mode was discussed during both Rel-16 and Rel-17 ATSSS study phase, as described in clause 6.3.1.1, 6.4.1 of TR 23.793 [26] for the loss rate sensitive traffic, such as IMS signaling, video, and some TCP-based traffic, and the solution 4 in clause 6.4 of TR 23.700-93 [5]. It allows the traffic transmitted via 3GPP and non-3GPP accesses in a redundant way to achieve the lowest latency and to lower the loss rate. + +It is proposed to further enhance the redundancy steering mode as described in TR 23.793 [26], with which the traffic will always be transmitted over both accesses once applied, to make it possible that the traffic transmission goes via both accesses, if necessary, or via only one access to save the transport resource. In details, when the traffic is allowed on both accesses and the packet loss rate (PLR) is provided with the redundancy steering mode: + +- The UE and the UPF can select any one of the accesses (based on implementation) to transport the traffic, if both accesses can satisfy the PLR requirement. +- If only one access can satisfy the PLR value, this access is applied to transport the traffic. +- Otherwise, redundant transmission over both accesses is triggered, if the PLR is satisfied again over one access during the redundant transmission, the redundant transmission should be deactivated. This access is applied to transport the traffic. + +For example, if the loss rate on one access does not exceed the PLR threshold, then only this one access is applied, otherwise, redundant transmission is triggered. + +When the traffic is allowed on both accesses and the redundancy steering mode is provided without a PLR threshold value, both accesses are always applied for the redundant transmission. + +See below Figure 6.1.2-1 for details, where UL packet flow is taken as an example. The DL packet flow shares the same mechanism. + +This redundancy steering mode can be applied by the MPTCP functionality with new requirements to be derived from this study/solution. + +NOTE 1: The redundant transmission algorithm required by the redundancy steering mode with packet loss rate relies on the implementation of the MPTCP by the OS today. + +NOTE 2: The redundancy steering mode with packet loss rate does not apply to the ATSSS-LL steering functionality. + +Editor's note: How the receiver will treat duplicated packets in case of MP-QUIC or MP-DCCP is FFS. + +Editor's note: The redundant traffic steering mode for the GBR traffic is FFS. + +Editor's note: Whether threshold values other than packet loss rate, such as RTT, are applicable, or whether and how multiple threshold values can be used together, is FFS. + +NOTE: For the MA PDU session, when the UE performs traffic switching between the 3GPP and non-3GPP accesses in 5GS and the MPTCP functionality is applied for the traffic, the UE and the UPF may trigger the redundant transmission via the 3GPP and non-3GPP access. This redundant transmission can be applied to all the MPTCP traffic with any steering mode. + +Editor's note: How the UE and the UPF decide to trigger the redundant transmission via the 3GPP and non-3GPP access during the traffic switching is FFS. + +![Diagram illustrating Redundancy steering mode for an MA PDU session. The diagram shows two User Equipment (UE) blocks connected via a central network. Each UE has a 'Steering mode= Redundancy' block. Inside each UE, there are two access paths: 3GPP and Non3GPP. Packets are shown being transmitted simultaneously over both paths. On the left UE, packets 1, 2, 3 are shown entering the steering block, and packets 10, 9, 8 are shown on the Non3GPP path, while packets 7, 6, 5, 4 are on the 3GPP path. On the right UE, packets 1, 2, 3 are shown on the 3GPP path, and packets 7, 6, 5, 4 are on the Non3GPP path. The central network shows the MA PDU session with packets 7, 6, 5, 4 and 3, 2, 1 being transmitted.](e4c6fa93821e3546ee9fcae897ae2771_img.jpg) + +Diagram illustrating Redundancy steering mode for an MA PDU session. The diagram shows two User Equipment (UE) blocks connected via a central network. Each UE has a 'Steering mode= Redundancy' block. Inside each UE, there are two access paths: 3GPP and Non3GPP. Packets are shown being transmitted simultaneously over both paths. On the left UE, packets 1, 2, 3 are shown entering the steering block, and packets 10, 9, 8 are shown on the Non3GPP path, while packets 7, 6, 5, 4 are on the 3GPP path. On the right UE, packets 1, 2, 3 are shown on the 3GPP path, and packets 7, 6, 5, 4 are on the Non3GPP path. The central network shows the MA PDU session with packets 7, 6, 5, 4 and 3, 2, 1 being transmitted. + +Figure 6.1.2-1: Redundancy steering mode + +## 6.2 Solution #6.1: Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC + +### 6.2.1 Introduction + +This solution enables a UE and the network to create an MA PDU Session with the non-3GPP access leg of a normal PDU connection in EPC, while keeping the 3GPP access leg in 5GC. + +### 6.2.2 High-level Description + +In this solution, it is assumed that the UE is able to attach to the EPC via GTP-based S2b interface and simultaneously to register with the 5GC over 3GPP access. The architecture is shown in Figure 6.2.2-1. + +![Figure 6.2.2-1: Multi-access between EPC and 5GC. This diagram illustrates the network architecture for multi-access between EPC and 5GC. At the top, HSS + UDM, PCF, SMF + PGW-C, and UPF + PGW-U are shown. The SMF + PGW-C is connected to the AMF via N15 and N11 interfaces. The AMF is connected to the NG-RAN via N2 and N3 interfaces. The NG-RAN is connected to the UE via N1 and Uu interfaces. The UE is also connected to the ePDG via SWu. The ePDG is connected to the 3GPP AAA server via SWm and SWx. The 3GPP AAA server is connected to the SMF + PGW-C via S6b. The SMF + PGW-C is connected to the HSS + UDM via N10. The PCF is connected to the HSS + UDM via N7. The UPF + PGW-U is connected to the HSS + UDM via N8.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 6.2.2-1: Multi-access between EPC and 5GC. This diagram illustrates the network architecture for multi-access between EPC and 5GC. At the top, HSS + UDM, PCF, SMF + PGW-C, and UPF + PGW-U are shown. The SMF + PGW-C is connected to the AMF via N15 and N11 interfaces. The AMF is connected to the NG-RAN via N2 and N3 interfaces. The NG-RAN is connected to the UE via N1 and Uu interfaces. The UE is also connected to the ePDG via SWu. The ePDG is connected to the 3GPP AAA server via SWm and SWx. The 3GPP AAA server is connected to the SMF + PGW-C via S6b. The SMF + PGW-C is connected to the HSS + UDM via N10. The PCF is connected to the HSS + UDM via N7. The UPF + PGW-U is connected to the HSS + UDM via N8. + +**Figure 6.2.2-1: Multi-access between EPC and 5GC** + +The solution as defined in clause 4.22.2.3.2 of TS 23.502 [3] is reused, with the major difference: + +- Extend the ATSSS container and apply APCO IE to transport the ATSSS related parameters. + +The key points of the solution are as follows: + +When the UE firstly requests a new PDN connection to EPC via non-3GPP access and wants to use this PDN connection as user-plane resource associated with a MA PDU Session: + +- The UE requests establishment of a new PDN connection when the UE is registered via non-3GPP access in EPS using the IPsec tunnel establishment procedure. The UE provides the ATSSS container to ePDG via IKE\_AUTH request message. The ATSSS container is extended to include the ATSSS request PCO parameter as defined in clause 6.1.6.2 of TS 24.193 [13]. The ePDG forwards the ATSSS request PCO parameter in APCO IE to the PGW-C/SMF. +- PGW-C+SMF replies the Create Session Response message to ePDG including APCO. The APCO includes the ATSSS response with the length of two octets PCO parameter as defined in clause 6.1.6.3 of TS 24.193 [13] and additionally provides ATSSS rule. The ePDG obtains the ATSSS response parameter and ATSSS rule from APCO and forwards this information via ATSSS container to the UE via IKE\_AUTH response message. + +When the UE firstly requests a new MA PDU Session in 5GC/3GPP access and wants to add the user-plane resources on non-3GPP access over EPC, it applies the procedures as defined in clause 4.22.2.3.2 of TS 23.502 [3] and clause 7.2.2.1 of TS 24.302 [14] for the transferring an existing PDU session from 5GS: + +- The UE sends ATSSS container with the ATSSS request PCO parameter in the IKE\_AUTH request message to the ePDG including the IP address of the MA PDU Session in CFG\_REQUEST Configuration Payload, an "MA PDU Request" indication and the PDU Session ID of the existing MA PDU Session on non-3GPP access over 5GC. The ePDG forwards the ATSSS request PCO parameter in the APCO to the PGW-C/SMF via Create Session Request message. +- PGW-C+SMF replies the Create Session Response message to ePDG including APCO with ATSSS response with the length of two octets PCO parameter. The ePDG obtains the ATSSS response parameter from APCO and forwards this information via ATSSS container to the UE via IKE\_AUTH response message. + +For the 3GPP access, the mobility procedure from 5GS to EPS is to be performed as follows: + +- If the MA PDU Session is transferred to EPS in case of interworking support with N26, or if the UE sends a PDN Connectivity Request with "handover" indication to transfer the MA PDU Session to EPS in case of interworking without N26, the SMF+PGW-C can keep the MA PDU Session. +- In case of UE operating in dual registration, the UE may decide to keep the MA PDU Session in 5GS, in addition to the above behaviour. + +### 6.2.3 Impacts on services, entities, interfaces and IETF protocols + +ePDG: + +- Shall be able to support the ATSSS container and apply APCO IE to transport the ATSSS related parameters. + +PGW-C+SMF: + +- Shall be able to apply APCO IE to transport the ATSSS related parameters. + +UE: + +- Shall be able to provide MA PDU "MA PDU Request" indication and the PDU Session ID of the existing MA PDU Session in the IKE\_AUTH request message. +- Shall be able to receive ATSSS rule over EPC via IKE signalling. + +## 6.3 Solution #2.1: MP-DCCP based Steering Functionality + +### 6.3.1 Introduction + +This solution addresses Key Issue #2 "New steering functionalities for non-TCP traffic" proposing MP-DCCP-LL to enable Access Traffic Steering, Switching and Splitting for any type of traffic, e.g. UDP, etc. + +The ATSSS feature is to enable a UE the advantage that application traffic can use both access resources to raise the bandwidth or/and access reliability by simultaneously connecting over both 3GPP and non-3GPP accesses. Since release-16, the splitting mode is only available to TCP streams using the ATSSS-HL functionality based on MPTCP. For UDP and even plain IP traffic, it can only be supported by the ATSSS-LL functionality, thus an UDP or even an IP packet flow cannot be efficiently split over both accesses due to missing re-ordering support and to the lack of access path bandwidth capabilities, so actually the increase of bandwidth requirement is not achieved for those types of traffic. This solution is proposed to introduce a new steering method based on MP-DCCP to resolve this issue. + +The Datagram Congestion Control Protocol (DCCP) was specified in IETF in RFC 4340 [11] for the transport layer to complement TCP and UDP for traffic that does not require reliable transport and re-transmission (in contrast to TCP traffic), but needs session and congestion control (in contrast to UDP traffic). For an introduction to DCCP please refer to RFC 4336 [15]. DCCP RFC 4340 [11] and its multipath pendant MP-DCCP, draft-ietf-tsvwg-multipath-dccp [12] provide protocol inherent measurement of path characteristics like latency, packet loss and available bandwidth. In that regard MP-DCCP is similar to MPTCP and therefore can support the same steering modes. Different to MPTCP though, is the handling of missing packets. Re-transmission and resulting head-of-line blocking are not under the responsibility of (MP-)DCCP, which is therefore similar to the ATSSS-LL characteristics provided for any type of traffic. This makes it suitable to be applied to Ethernet, IP and higher layer traffic when it becomes integrated with an encapsulation framework, which tunnels these types of traffic over a MP-DCCP connection. Moreover MP-DCCP provides measures to facilitate the process of re-ordering at the termination points of ATSSS. For this purpose, timing and sequencing information are transmitted along with the encapsulated data to facilitate re-ordering or partial reordering of the data received from the 3GPP and non-3GPP access. Both access types provide different path characteristics that let the original data stream scramble during transport after it has been split. Re-ordering helps in the receiving ATSSS entity (UPF or UE) to reconstruct a certain degree order. + +For example, MP-DCCP supports similar functionality as provided by ATSSS-LL and ATSSS-HL (MPTCP) for all ATSSS steering modes, for any type of traffic, and provides re-ordering capabilities. MP-DCCP does not introduce encryption but relies on the security layer of 3GPP. + +This solution can be applied to any type of traffic, at least to the UDP based application traffic, with IP-based MA PDU Sessions for various IP versions (IPv4, IPv6, IPv4v6). + +### 6.3.2 Description + +This solution is largely based on Solution #6 "MPQUIC-LL Steering Functionality" defined in TR 23.700-93 [5] with the main difference of using MP-DCCP instead of MP-QUIC. + +The MP-DCCP-LL solution is applicable to applications relying on any type of traffic (plain IP, Ethernet, TCP/IP, UDP/IP), but at least provides ATSSS functionalities to non-TCP based traffic (e.g. UDP/IP, QUIC/UDP/IP). MP-DCCP-LL is able to co-exist with ATSSS-LL and MPTCP, even if it can take over their functionality. + +To support ATSSS using the MP-DCCP-LL steering functionality, the architecture reference model for ATSSS, as specified in TS 23.501 [2] clause 4.2.10, is enhanced as shown in Figure 6.3.2-1. The MP-DCCP-LL steering functionality is implemented in the UE and in the PSA UPF. The PMF functionality is not needed for an MA PDU Session that applies MP-DCCP-LL. + +![Figure 6.3.2-1: Reference Architecture for ATSSS using MP-DCCP. The diagram shows a User Equipment (UE) connected to an AMF via N1 and N2 interfaces. The AMF is connected to an SMF via N11. The SMF is connected to a PCF via N7 and to a UPF via N4. The UPF is connected to a Data Network via N6. The UE contains three functional blocks: MPTCP functionality, ATSSS-LL functionality, and MPDCCP-LL functionality. The AMF connects to the UE via 3GPP Access and Non-3GPP Access. The UPF contains four functional blocks: MPTCP Proxy functionality, UPF, PMF, and MPDCCP-LL functionality. The MPDCCP-LL functionality in the UE is connected to the MPDCCP-LL functionality in the UPF via N3 interfaces through the 3GPP Access and Non-3GPP Access.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +Figure 6.3.2-1: Reference Architecture for ATSSS using MP-DCCP. The diagram shows a User Equipment (UE) connected to an AMF via N1 and N2 interfaces. The AMF is connected to an SMF via N11. The SMF is connected to a PCF via N7 and to a UPF via N4. The UPF is connected to a Data Network via N6. The UE contains three functional blocks: MPTCP functionality, ATSSS-LL functionality, and MPDCCP-LL functionality. The AMF connects to the UE via 3GPP Access and Non-3GPP Access. The UPF contains four functional blocks: MPTCP Proxy functionality, UPF, PMF, and MPDCCP-LL functionality. The MPDCCP-LL functionality in the UE is connected to the MPDCCP-LL functionality in the UPF via N3 interfaces through the 3GPP Access and Non-3GPP Access. + +**Figure 6.3.2-1: Reference Architecture for ATSSS using MP-DCCP** + +The MP-DCCP protocol is specified in draft-ietf-tsvwg-multipath-dccp [12]: "DCCP Extensions for Multipath Operation with Multiple Addresses". It is designed to support the multipath scenario, and provides the means for access traffic steering, switching, and splitting. Depending on the traffic direction, the UE or PSA UPF acts as ATSSS sender or ATSSS receiver, respectively. The UE uses the MP-DCCP-LL functionality to establish multiple sub-flows as DCCP tunnels which are set up and operated towards the PSA UPF for bi-directional usage. Within each sub-flow inherent sequencing is given and DCCP congestion control provides real-time path characteristic information, which is required for splitting based steering modes (e.g. priority-based, smallest delay, load-balancing) and packet reordering measures. + +The MP-DCCP-LL provides an unreliable tunnelling service between the UE and the UPF that is based on: + +1. The DCCP protocol specified in RFC4340 [11] along with accompanying documents that describe congestion control (CCID2, RFC 4341 [19], CCID3, RFC 4342 [20], CCID4, RFC 5622 [21], CCID5); and +2. The DCCP extension specified in draft-ietf-tsvwg-multipath-dccp [12] for supporting multipath DCCP. + +The Figure 6.3.2-2 shows the model of an MA PDU Session that operates using the MP-DCCP-LL steering functionality. + +![Figure 6.3.2-2: Model of MA PDU Session using MP-DCCP-LL. The diagram shows two main components: the MP-DCCP Tunnel Client (MDTC) on the left and the MP-DCCP Tunnel Server (MDTS) on the right, both connected to an upper layer (e.g., IPv4, IPv6). The MDTC is composed of several functional blocks: QoS flow Selection, Steering Mode Selection, MP-DCCP Connection Selection, and DCCP protocol with multipath extensions. It also interacts with QoS Rules and ATSSS Rules. The MDTS is composed of similar functional blocks: QoS flow Selection, Steering Mode Selection, MP-DCCP Connection Selection, and DCCP protocol with multipath extensions, but it interacts with N4 Rules. Both components are connected to a central IP layer. Below the IP layer, there are two access paths: Non-3GPP Access and 3GPP Access. Each path contains multiple MP-DCCP connections (sub-flows) that carry traffic from the MDTC to the MDTS.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 6.3.2-2: Model of MA PDU Session using MP-DCCP-LL. The diagram shows two main components: the MP-DCCP Tunnel Client (MDTC) on the left and the MP-DCCP Tunnel Server (MDTS) on the right, both connected to an upper layer (e.g., IPv4, IPv6). The MDTC is composed of several functional blocks: QoS flow Selection, Steering Mode Selection, MP-DCCP Connection Selection, and DCCP protocol with multipath extensions. It also interacts with QoS Rules and ATSSS Rules. The MDTS is composed of similar functional blocks: QoS flow Selection, Steering Mode Selection, MP-DCCP Connection Selection, and DCCP protocol with multipath extensions, but it interacts with N4 Rules. Both components are connected to a central IP layer. Below the IP layer, there are two access paths: Non-3GPP Access and 3GPP Access. Each path contains multiple MP-DCCP connections (sub-flows) that carry traffic from the MDTC to the MDTS. + +**Figure 6.3.2-2: Model of MA PDU Session using MP-DCCP-LL** + +The MP-DCCP-LL is composed of the following components which can also be found in Figure 6.3.2-3: + +- **MP-DCCP Tunnel Client (MDTC)**: The MDTC operates in the UE as a MP-DCCP client application and provides the following functionality: + - It establishes N MP-DCCP connections with the MP-DCCP tunnel server (MDTS) in the UPF. The number N of MP-DCCP connections, as well as the destination IP address & port for each MP-DCCP connection, is determined from information contained in the PDU Session Establishment Accept message (see the "MP-DCCP Connection Setup Information" below). Each MP-DCCP connection is established immediately after the setup of the MA PDU Session. + +NOTE 1: As explained below, each MP-DCCP connection carries the traffic of one QoS flow only. By using a separate MP-DCCP connection for each QoS flow, we ensure that PDUs belonging to different QoS flows, which may require a different QoS treatment, are not multiplexed in the same MP-DCCP connection, hence, each MP-DCCP connection does not need to support QoS-aware scheduling. + +- It receives UL PDUs from the upper layer and, for each UL PDU: + - First, it selects a QoS flow based on the QoS rules in the UE. + - Then, it selects a steering mode to be applied for the UL PDU based on the ATSSS rules in the UE. + - If negotiated, it compresses the inner headers (e.g. IP, UDP, TCP, Ethernet) of the UL PDU. + - Finally, it selects a MP-DCCP connection to transmit the PDU based on the selected QoS flow and the selected steering mode. For each established MP-DCCP connection, the MDTC maintains an associated steering mode and QoS flow indicator. + +NOTE 2: It is assumed that the scheduler of a MP-DCCP connection can apply only one steering mode. Therefore, if different steering modes are needed for the traffic of a QoS flow, then different MP-DCCP connections are setup for this QoS flow, one per steering mode. + +- **MP-DCCP Tunnel Server (MDTS)**: The MDTS operates in the UPF as a MP-DCCP server application and provides the following functionality: + - It accepts the MP-DCCP connections requested by MDTC in the UE. + - It receives DL PDUs from the upper layer and, for each DL PDU, it selects (a) a QoS flow, (b) a MP-DCCP connection to transmit the PDU, and (c) a steering mode. The MP-DCCP connection is selected based on the N4 (e.g. MAR) rules. + - If negotiated, it compresses the inner headers (e.g. IP, UDP, TCP, Ethernet) of the DL PDU. + +- **MP-DCCP protocol:** The DCCP protocol as defined by IETF with the applicable multipath extensions, draft-ietf-tsvwg-multipath-dccp [12]. It receives PDUs from the MDTC in the UE (or the MDTS in the UPF) indicating the MP-DCCP connection to be sent on and, for each PDU, it selects an access type (i.e. a MP-DCCP sub-flow) to transmit the PDU. The access type selection is based on the steering mode associated with the MP-DCCP connection and the measurements provided by the MP-DCCP protocol (e.g. RTT, loss rate, congestion). + +The MP-DCCP-LL functionality tunnels PDUs (e.g. IP packets or Ethernet frames) over a multipath DCCP transport. The protocol stack in the UE and UPF is shown in Figure 6.3.2-3. The different IP addresses shown in this figure are explained in the next clause. + +![Figure 6.3.2-3: Protocol stack for MP-DCCP-LL. The diagram shows two protocol stacks side-by-side. The left stack is for the UE, starting with a PDU (IP@0) at the top, followed by a box containing the MP-DCCP Tunnel Client (MDTC) and the MP-DCCP-LL layer. Below this is the MP-DCCP layer, then a box with two IP addresses, IP@1 and IP@2. The bottom layer consists of two boxes: '3GPP access' and 'Non-3GPP access'. The right stack is for the UPF, starting with a PDU at the top, followed by a box containing the MP-DCCP Tunnel Server (MDTS) and the MP-DCCP-LL layer. Below this is the MP-DCCP layer, then a box with IP@3. The bottom layer consists of two boxes: 'GTP tunnel (Non-3GPP access)' and 'GTP tunnel (3GPP access)'. The labels 'UE' and 'UPF' are centered below their respective stacks.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +Figure 6.3.2-3: Protocol stack for MP-DCCP-LL. The diagram shows two protocol stacks side-by-side. The left stack is for the UE, starting with a PDU (IP@0) at the top, followed by a box containing the MP-DCCP Tunnel Client (MDTC) and the MP-DCCP-LL layer. Below this is the MP-DCCP layer, then a box with two IP addresses, IP@1 and IP@2. The bottom layer consists of two boxes: '3GPP access' and 'Non-3GPP access'. The right stack is for the UPF, starting with a PDU at the top, followed by a box containing the MP-DCCP Tunnel Server (MDTS) and the MP-DCCP-LL layer. Below this is the MP-DCCP layer, then a box with IP@3. The bottom layer consists of two boxes: 'GTP tunnel (Non-3GPP access)' and 'GTP tunnel (3GPP access)'. The labels 'UE' and 'UPF' are centered below their respective stacks. + +**Figure 6.3.2-3: Protocol stack for MP-DCCP-LL** + +In summary, the MP-DCCP-LL steering functionality: + +- Supports a multipath, unreliable, and transparent bi-directional tunnelling service between the UE and UPF. +- Does not support retransmission of lost DCCP datagrams but supports loss detection, according to RFC 4340 [11]. +- Provides mechanisms for reordering of out-of-order arrived DCCP datagrams as described in clause 6.3.7. +- Supports congestion control per DCCP sub-flow, based on standardized CC algorithms RFC 4341 [19], RFC 4342 [20], RFC 5622 [21]). As a result, the UE and the UPF may stop sending datagram frames on a DCCP sub-flow when congestion is detected by the MP-DCCP protocol on this sub-flow. +- Supports round-trip, packet loss measurements per DCCP sub-flow, as part of the CCID framework as specified in RFC 4340 [11] and provides available bandwidth estimation. +- Supports steering modes compatible with the ATSSS rules, the QoS rules and the N4 rules as defined in Rel-17. One steering mode is supported per MP-DCCP connection. +- Optionally, support compression of the inner headers (e.g. IP, UDP, TCP, Ethernet) of the UL and DL PDUs. + +### 6.3.3 MA PDU Session Establishment procedure + +![Sequence diagram of MA PDU Session Establishment procedure using MP-DCCP. Lifelines: UE, NG-RAN, AMF, SMF, UDM, PCF, UPF. The diagram shows the flow of messages for session establishment, including context creation, policy control, and N4 session setup. Red text highlights MP-DCCP-LL and IHC support and steering functionality.](a3472689858b068ef469213682965325_img.jpg) + +The sequence diagram illustrates the MA PDU Session Establishment procedure using MP-DCCP. The participants are UE, NG-RAN, AMF, SMF, UDM, PCF, and UPF. + +- 1a. UL NAS Transport:** UE to NG-RAN. PDU Session ID, [S-NSSAI], [DNN], Request Type = MA PDU Request, PDU Session Establishment Request (PDU Session ID, PDU type, SSC Mode, 5GSM capability). A note indicates: **MP-DCCP-LL supported, IHC supported, Compression profiles supported**. +- 1b. NGAP Uplink NAS Transport:** NG-RAN to AMF. +- 2. Create SM Context Req.:** AMF to SMF. SUPI, PDU Session ID, S-NSSAI, DNN, Request Type = MA PDU Request, Access Type, RAT Type, UE location, PDU Session Establishment Req.(...). +- 3a. Get SM subscription data:** SMF to UDM. +- 3b. UECM Registration:** SMF to UDM. +- 4. Create SM Context Res.:** SMF to AMF. 201 Created, URI of created SM ctx resource. +- 5a. SM Policy Control Create Req.:** SMF to PCF. MA PDU Request, ATSSS Capability (**MP-DCCP-LL**). A decision box indicates: 1) Decide that MA PDU Session is allowed. 2) Decide to apply **MP-DCCP-LL** steering functionality. +- 5b. SM Policy Control Create Res.:** PCF to SMF. PCC rules with MA PDU Session Control using **MP-DCCP-LL** steering functionality. +- 6a. Derive N4 rules for the UPF including MAR rules for MP-DCCP-LL:** SMF to UPF. Decides to use **IHC compression profile** to use. +- 6b. N4 Session Establishment Req.:** SMF to UPF. Provide ATSSS Control Information (**MP-DCCP-LL Control Information**), Create PDR(...), Create MAR (Steering functionality=**MP-DCCP-LL** Steering mode, **IHC configuration**). +- 6c. N4 Session Establishment Res.:** UPF to SMF. ATSSS Control Parameters (**MP-DCCP-LL Parameters**). +- 7. Derive "MP-DCCP Connection Setup Information" and ATSSS/QoS rules for the UE:** SMF to AMF. +- 8a. N1N2 Message Transfer Req.:** AMF to SMF. PDU Session Establishment Accept (PDU Session ID, PDU type, SSC Mode, QoS Rules, ATSSS Container). +- 8b. N1N2 Message Transfer Res.:** SMF to AMF. +- 9a. NGAP PDU Session Resource Setup Request:** AMF to NG-RAN. +- 9b. DL NAS Transport:** NG-RAN to UE. PDU Session ID, PDU Session Establishment Accept (PDU Session ID, PDU type, SSC Mode, QoS Rules, ATSSS Container). +- 9c. NGAP PDU Session Resource Setup Response:** NG-RAN to AMF. +- 10a. Update SM Context Req.:** AMF to SMF. +- 10b. N4 Session Modification Req.:** SMF to UPF. (DL TEID). +- 10c. N4 Session Modification Res.:** UPF to SMF. +- 10d. Update SM Context Res.:** SMF to AMF. +- 11a. The MDTC in the UE starts the establishment of N MP-DCCP connections with UPF over both 3GPP and non-3GPP access:** UE to UPF. + +Sequence diagram of MA PDU Session Establishment procedure using MP-DCCP. Lifelines: UE, NG-RAN, AMF, SMF, UDM, PCF, UPF. The diagram shows the flow of messages for session establishment, including context creation, policy control, and N4 session setup. Red text highlights MP-DCCP-LL and IHC support and steering functionality. + +Figure 6.3.3-1: MA PDU Session establishment using MP-DCCP + +The above Figure 6.3.3-1 shows how an MA PDU Session is established when (a) the UE indicates support for MP-DCCP-LL and (b) the network accepts to apply MP-DCCP-LL for one or more traffic flows. All steps are the same as the steps used to establish an MA PDU Session in Rel-17 specifications. The additions to support MP-DCCP-LL are further discussed below. + +- 1a. In the PDU Session Establishment Request the UE indicates (in the 5GSM capability) that it supports the MP-DCCP-LL steering functionality, inner header compression (IHC), supported compression profile, and, possibly, other steering functionalities such as MPTCP and ATSSS-LL. +- 1b. The AMF selects an SMF supporting ATSSS. + +- 5a. In the SM Policy Control Create Request, the SMF includes the ATSSS Capabilities of the MA PDU Session (see TS 23.502 [3] and TS 29.512 [23]), which contain the MP-DCCP-LL capability and, possibly, other capabilities already defined, such as "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode", etc. +- 5b. The PCF decides to allow the requested MA PDU Session and creates PCC rules containing MA PDU Session Control information (see TS 29.512 [23]), which specifies a steering functionality (e.g. MP-DCCP-LL, ATSSS-LL), a steering mode (e.g. Active/Standby), etc. +- 6a. Based on the received PCC rules, the SMF creates N4 rules for the UPF including MAR rules for MP-DCCP-LL and decides to use IHC and which compression profile. +- 6b. In the N4 Session Establishment Request, the SMF includes the N4 rules and indicates to UPF that MP-DCCP-LL Control Information should be provided (see next step). The MP-DCCP-LL Control Information indicates to UPF how many MP-DCCP connections are needed, which is determined from the received PCC rules which map to QoS Flows and steering modes. For example, if the SMF has two QoS Flows carrying traffic with steering functionality = MP-DCCP-LL and steering mode= smallest delay then the SMF indicates to UPF that two MP-DCCP connections are needed. It also includes IHC configuration information. +- 6c. Based on the requested MP-DCCP-LL Control Information, the UPF provides the following MP-DCCP-LL parameters: + - 1) Two "UE link-specific MP-DCCP-LL" IP addresses used only by the MP-DCCP-LL functionality in the UE, one associated with the 3GPP access and another associated with the non-3GPP access. It is possible that the UPF provides "UE link-specific MP-DCCP-LL" IP addresses that are not routable via N6 (e.g. IPv6 link-local addresses). For example, the "UE link-specific MP-DCCP-LL" IP addresses may be the following: + +UE link-specific MP-DCCP-LL IP address over 3GPP access = 10.10.1.1 + +UE link-specific MP-DCCP-LL IP address over non-3GPP access = 10.10.2.1 + +NOTE 1: The "UE link-specific MP-DCCP-LL" IP addresses are similar to the "UE link-specific multipath" IP addresses used for MPTCP, specified in TS 23.502 [3] and TS 29.244 [24]. + +NOTE 2: In case MP-DCCP-LL and MPTCP are enabled for the same MA PDU Session, the "UE link-specific MP-DCCP-LL" IP addresses and the "UE link-specific multipath" IP addresses can be the same. + +- 2) "MP-DCCP Address Information" which contains the "UPF link-specific MP-DCCP-LL" IP address for the UPF, and one UPF port number per MP-DCCP connection. + - 3) +7. Based on the received PCC rules and the MP-DCCP-LL parameters received from UPF, the SMF creates the following information, which will be sent to the UE: + - ATSSS rules; + - QoS rules; and + - "MP-DCCP Connection Setup Information" which contains + - a) information for the UE to setup the MP-DCCP connections with the UPF. For example, it indicates that a MP-DCCP Connection over 3GPP access should be established toward the UPF IP address 10.10.3.1 and UPF port 53671 for QFI-x and steering mode=smallest delay. + - b) IHC configuration information +- 8a. In the PDU Session Establishment Accept, the ATSSS Container (defined in TS 24.193 [13]) contains: + - 1) The ATSSS rules, which are applied by MDTC in the UE to route the traffic of the MA PDU Session across the DCCP connections; and + - 2) The "network steering functionalities information" (see TS 24.193 [13]), which contains: + - a. The two "UE link-specific MP-DCCP-LL" IP addresses provided by UPF in step 6c; and + - b. The "MP-DCCP Connection Setup information" created by SMF in step 7. + +11. Based on the received "MP-DCCP Connection Setup information" the MDTC in the UE establishes one or more MP-DCCP connections with the MDTS in the UPF. The UE establishes the MP-DCCP connections immediately after receiving the PDU Session Establishment Accept message. The application protocol negotiated during each MP-DCCP connection will be decided by stage-3 (for example, it could be "mp-dccp-ll"). + +When MP-DCCP-LL functionality is enabled for the MA PDU Session: + +- any QoS rules or PDRs that apply to the MA PDU Session IP address/prefix and port also apply to the "link-specific multipath" addresses/prefixes and ports used by the UE to establish MP-DCCP subflows over 3GPP and non-3GPP accesses; and +- any QoS rules or PDRs that apply to the IP address/prefix and port of the final destination server in DN also apply to the IP address and port of the MDTS for corresponding MP-DCCP subflows that are terminated at the UPF. + +NOTE 2: How these associations are made is left up to the UE and UPF implementations. + +The MP-DCCP connections established between the MDTC in UE and the MDTS in UPF include also MP-DCCP connections associated with downlink-only QoS flows. This is achieved by sending "MP-DCCP connection setup information" to UE that includes information for establishing a MP-DCCP connection associated with a downlink-only QoS flow. The UE does not send uplink PDUs to a MP-DCCP connection associated with a downlink-only QoS flow, because the UE has no associated QoS rule for this MP-DCCP connection. However, the UE sends DCCP packets (e.g. Data-ACK, etc.) over this MP-DCCP connection based on the normal MP-DCCP protocol operation. + +### 6.3.4 MA PDU Session Modification procedure + +The MA PDU Session Modification procedure (either network-requested or UE-requested) may be used to add or remove QoS flows from an established MA PDU Session, as specified since Rel-16. + +After the MA PDU Session Modification procedure is completed, then: + +- If a QoS flow is deleted and this QoS flow was used to transfer MP-DCCP-LL traffic, then the MP-DCCP connection associated with this QoS flow (one DCCP connection per access) is released. The UE receives updated "MP-DCCP Connection Setup Information" in order to determine which MP-DCCP connection to release. +- If a QoS flow is created and this QoS flow will be used to transfer MP-DCCP-LL traffic, then the MP-DCCP connection associated with this QoS flow (one DCCP connection per access) is established between the UE and UPF. The UE receives updated "MP-DCCP Connection Setup Information" in order to determine the UPF IP addresses and ports for the new MP-DCCP connections. + +### 6.3.5 Example of MP-DCCP-LL Operation + +To better explain the MP-DCCP-LL operation, we consider an example in this clause. In this example, it is assumed that the PCF creates two PCC rules which contain steering functionality = MP-DCCP-LL (see Figure 6.3.5-1 below) and the UPF provides the following MP-DCCP-LL parameters: + +- 1) "UE Link-specific MP-DCCP-LL" IP addresses: + +UE Link-specific MP-DCCP-LL IP address over 3GPP access = 10.10.1.1 + +UE Link-specific MP-DCCP-LL IP address over non-3GPP access = 10.10.2.1 + +- 2) MP-DCCP-LL Address Information: + +UPF Link-specific MP-DCCP-LL IP address for both 3GPP access and for non-3GPP access = 10.10.3.1 + +UPF Port for MP-DCCP Connection #1 = 53671 + +UPF Port for MP-DCCP Connection #2 = 53672 + +Based on the above MP-DCCP-LL Address Information, the SMF creates the following " MP-DCCP Connection Setup information", which is sent to UE. + +- MP-DCCP Connection #1: + +- UPF Link-specific MP-DCCP-LL IP address for 3GPP access: 10.10.3.1 +- UPF Port: 53671 +- Associated QFI: QFI-x +- Associated Steering Mode: Active/Standby +- MP-DCCP Connection #2: + - UPF Link-specific MP-DCCP-LL IP address for both 3GPP access and non-3GPP access: 10.10.3.1 + - UPF port: 53672 + - Associated QFI: QFI-y + - Associated Steering Mode: Smallest Delay + +The UE applies the received "UE link-specific MP-DCCP-LL" IP addresses and the "MP-DCCP Connection Setup information" and establishes two MP-DCCP connections with the UPF over both 3GPP access and non-3GPP access, as shown below. + +![Diagram illustrating the MP-DCCP-LL operation between a UE and a UPF. The UE contains a PDU (IP@0), an MP-DCCP Tunnel Client (MDTC), MP-DCCP-LL, and MP-DCCP layers. It has two link-specific IP addresses: IP@1 (10.10.1.1) for 3GPP access and IP@2 (10.10.2.1) for non-3GPP access. The UPF contains a PDU, an MP-DCCP Tunnel Server (MDTS), MP-DCCP-LL, and MP-DCCP layers. It has a link-specific IP address IP@3 (10.10.3.1) and two ports: 53671 and 53672. Four connections are shown: MP-DCCP Connection #1 over non-3GPP access, MP-DCCP Connection #2 over non-3GPP access, MP-DCCP Connection #1 over 3GPP access, and MP-DCCP Connection #2 over 3GPP access. The diagram also shows GTP tunnels for non-3GPP and 3GPP access within the UPF.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) + +Diagram illustrating the MP-DCCP-LL operation between a UE and a UPF. The UE contains a PDU (IP@0), an MP-DCCP Tunnel Client (MDTC), MP-DCCP-LL, and MP-DCCP layers. It has two link-specific IP addresses: IP@1 (10.10.1.1) for 3GPP access and IP@2 (10.10.2.1) for non-3GPP access. The UPF contains a PDU, an MP-DCCP Tunnel Server (MDTS), MP-DCCP-LL, and MP-DCCP layers. It has a link-specific IP address IP@3 (10.10.3.1) and two ports: 53671 and 53672. Four connections are shown: MP-DCCP Connection #1 over non-3GPP access, MP-DCCP Connection #2 over non-3GPP access, MP-DCCP Connection #1 over 3GPP access, and MP-DCCP Connection #2 over 3GPP access. The diagram also shows GTP tunnels for non-3GPP and 3GPP access within the UPF. + +**Figure 6.3.5-1: Example of MP-DCCP-LL Operation** + +After the two MP-DCCP connections are established between the UE and the UPF, the MP-DCCP-LL routes the PDUs received from the upper layers to one of the flows of a MP-DCCP connection, as illustrated in Figure 6.3.5-2 and Figure 6.3.5-3 below for up-link and down-link traffic, respectively. + +First, the QoS rules are applied on a received PDU (e.g. IP packet or Ethernet frame) to determine a QFI for this PDU. Subsequently, the MDTC finds a matching ATSSS rule for the PDU based on which it identifies the steering mode that should be applied for this PDU. Finally, the MDTC selects a MP-DCCP connection for the PDU based on the selected QFI and the steering mode. For each MP-DCCP Connection, the MDTC maintains an associated steering mode and QFI according on the received "MP-DCCP Connection Setup information". Finally, the PDU is encapsulated in a DCCP datagram and is added to a DCCP/IP packet destined to [UPF Link-specific MP-DCCP-LL IP address = 10.10.3.1, UPF Port = 53671]. + +NOTE 1: The QFI selected for a PDU is transferred down to the selected access (3GPP or non-3GPP) so that the selected access can transfer the PDU via the corresponding QoS flow. For a packet created by the MP-DCCP protocol itself (e.g. a Data ACK), the QFI delivered to the access is the QFI associated with the MP-DCCP connection over which this packet is transmitted. + +NOTE 2: The header compression, if performed by the MP-DCCP Tunnel Client and the MP-DCCP Tunnel Server (see clause 6.3.2) is not shown in the following two figures for simplicity. + +![Diagram illustrating the user-plane operation with MP-DCCP-LL in the UL direction, showing traffic flow from UE through MP-DCCP Tunnel Client to UPF via 3GPP and Non-3GPP accesses.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +The diagram illustrates the user-plane operation with MP-DCCP-LL in the UL direction, showing traffic flow from the UE through the MP-DCCP Tunnel Client to the UPF via 3GPP and Non-3GPP accesses. + +**UE (User Equipment):** Traffic from "app1.example.com" is processed through UDP/TCP and IP layers. Default traffic (match-all) is also processed. The IP packets are then passed to the MP-DCCP Tunnel Client. + +**MP-DCCP Tunnel Client:** This component performs QoS flow selection (based on QoS rules) and Steering Mode Selection (based on ATSSS rules). It uses QFI-1 and QFI-2 to select the MP-DCCP connection (Conn #1 or Conn #2) based on the selected steering mode and QFI. The selected IP packets are then processed by the MP-DCCP protocol with multipath extensions. + +**Accesses:** The MP-DCCP Tunnel Client sends traffic to two types of access: + +- 3GPP access:** Traffic is sent to lower layers (PDCP, RLC, ...) and then to the UPF via a GTP tunnel (3GPP). +- Non-3GPP access:** Traffic is sent to lower layers (IPsec, ...) and then to the UPF via a GTP tunnel (Non-3GPP). + +**UPF (User Plane Function):** The UPF receives traffic from both accesses. It performs further packet processing, e.g., MP-DCCP-LL Re-ordering, and then sends the IP packets to the upper layers (e.g., N6 interface). + +**Packet Flow Details:** The diagram shows the flow of IP packets through various components. In the UE, packets are colored blue, yellow, and green. In the MP-DCCP Tunnel Client, packets are processed based on QoS rules and steering modes. In the access, packets are encapsulated into GTP tunnels. In the UPF, packets are re-ordered and then sent to the upper layers. The MP-DCCP protocol with multipath extensions is shown at the bottom of the UE and UPF, indicating the encapsulation of IP packets into DCCP Payload, DCCP hdr, and IP hdr. + +Diagram illustrating the user-plane operation with MP-DCCP-LL in the UL direction, showing traffic flow from UE through MP-DCCP Tunnel Client to UPF via 3GPP and Non-3GPP accesses. + +Figure 6.3.5-2: Example of user-plane operation with MP-DCCP-LL (UL direction) + +![Figure 6.3.5-3: Example of user-plane operation with MPDCCP-LL (DL direction). The diagram illustrates the data flow from the UPF to the UE through various network layers and access paths. On the UE side, traffic from 'app1.example.com' and default traffic are processed through UDP/TCP and IP layers, then IP packets are handled by the MP-DCCP Tunnel Client. The client uses MP-DCCP connections #1 and #2 for further processing, such as re-ordering. On the UPF side, traffic from upper layers (e.g., N6 interface) goes through the IP layer and is processed by the MP-DCCP Tunnel Server. The server uses N4 rules for session identification, QoS flow selection, and steering mode selection. It then directs traffic through MP-DCCP connections #1 and #2 to GTP tunnels (Non-3GPP and 3GPP). The traffic is then sent to 3GPP and Non-3GPP access networks via lower layers (PDCP, RLC, etc.) and QoS flows. The diagram shows the encapsulation of IP packets into MP-DCCP sub-flows and their subsequent transmission over different access paths.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Figure 6.3.5-3: Example of user-plane operation with MPDCCP-LL (DL direction). The diagram illustrates the data flow from the UPF to the UE through various network layers and access paths. On the UE side, traffic from 'app1.example.com' and default traffic are processed through UDP/TCP and IP layers, then IP packets are handled by the MP-DCCP Tunnel Client. The client uses MP-DCCP connections #1 and #2 for further processing, such as re-ordering. On the UPF side, traffic from upper layers (e.g., N6 interface) goes through the IP layer and is processed by the MP-DCCP Tunnel Server. The server uses N4 rules for session identification, QoS flow selection, and steering mode selection. It then directs traffic through MP-DCCP connections #1 and #2 to GTP tunnels (Non-3GPP and 3GPP). The traffic is then sent to 3GPP and Non-3GPP access networks via lower layers (PDCP, RLC, etc.) and QoS flows. The diagram shows the encapsulation of IP packets into MP-DCCP sub-flows and their subsequent transmission over different access paths. + +Figure 6.3.5-3: Example of user-plane operation with MPDCCP-LL (DL direction) + +### 6.3.6 Support of Steering Modes + +MP-DCCP solution supports all specified steering modes in TS 23.501 [2]. In addition, MP-DCCP can support additional steering modes as listed in clause 6.3.1. + +MP-DCCP protocol may provide additional modes by new scheduling algorithms and by flexibly combining any of the existing steering modes. + +### 6.3.7 Support of Re-Ordering + +Traffic splitting over access paths with different characteristics causes scrambling of the original data stream. A reassembly of such data stream requires a re-ordering. + +MP-DCCP protocol itself does not specify re-ordering mechanisms but provides path sequencing (DCCP packet sequencing [11]), connection sequencing (MP\_SEQ option [12]) and has inherent latency (MP\_RTT option [12]) or timing (DCCP timestamp option [11]) information exchange, i.e. all properties that are necessary for the packet receiving side, i.e. UE or UPF, to be able to implement re-ordering properly. Different re-ordering strategies may be used which can be achieved by using implementation specific means. + +### 6.3.8 User-plane overhead + +This clause shows additional header sizes used by the MP-DCCP-LL solution to encapsulate and transport PDUs over the user-plane. + +Note: Outer IP header is not considered as not different between solutions. + +#### Data Packet + +``` +MP_RTT for Reordering +---DCCP----- + -----MP-DCCP--- + Payload +Generic Header + MP-SEQ + MP-RTT + IP + UDP +12 or 16 + 9 + 12 + 20 + 8 = 61/65 Bytes +``` + +``` +DCCP Timestamp for reordering +---DCCP----- + MP-DCCP + Payload +Generic Header + timestamp + MP-SEQ + IP + UDP +12 or 16 + 6 + 9 + 20 + 8 = 55/59 Bytes +``` + +Depending on which combination of short or long DCCP header and the type of delay information exchange (DCCP timestamp option or MP\_RTT option) is used for reordering the additional headers add 55 Byte to 65 Byte to the actual payload. It is recommended to use short DCCP header (12 Bytes) and timestamp option (6 Bytes) for implementations which results in additional 55 Byte only. + +Compression of IP/UDP or IP/TCP or Ethernet headers can significantly reduce overhead. + +### 6.3.9 Co-existence with MPTCP and ATSSS-LL + +The MP-DCCP and the MPTCP steering functionalities complement each other as the former supports multipath transport for UDP/IP/Ethernet traffic, while the latter supports multipath transport for TCP/IP traffic. + +Since the UE indicates if it supports the MP-DCCP steering functionality (in the PDU Establishment Request message), the network may configure the UE/UPF to apply MP-DCCP for UDP data flows, only if it is supported by the UE. Otherwise, the network may configure the UE/UPF to apply ATSSS-LL for UDP data flows. + +### 6.3.10 Impacts on services, entities, interfaces and IETF protocols + +The ATSSS rules and the N4 rules are enhanced to support values for the MP-DCCP-LL steering functionality and for potentially new steering modes. The UE and the UPF receive information ("MP-DCCP Connection Setup information" for UE respectively "MP-DCCP-LL Control Information" for UPF) which indicates how many MP-DCCP connections should be established between the UE and the UPF, and the QoS flow and steering mode associated with each MP-DCCP connection. + +IETF protocols: + +- The MP-DCCP-LL solution is based on the following draft specifications defined by IETF. The MP-DCCP-LL does not require any changes to these specifications. + +RFC 4340 [11], draft-ietf-tsvwg-multipath-dccp [12]. + +AMF: + +- No impact. It is assumed that if 5GC supports ATSSS / Rel-18, then all ATSSS-capable SMFs in 5GC are capable of supporting MP-DCCP-LL. + +SMF: + +- From the PCC rules, it shall determine the number of MP-DCCP connections needed. +- Shall indicate to UPF the number of MP-DCCP connections needed. +- Shall create and send to UE the "MP-DCCP Connection Setup Information" based on the "MP-DCCP-LL Address Information" received from UPF. +- From the received PCC rules, it shall create corresponding ATSSS rules and QoS rules for the UE. +- From the received PCC rules, it shall create corresponding N4 rules (PDRs, MAR, QER, etc.) for the UPF. + +- Decides whether to use IHC and forwards IHC configuration information to UE and UPF + +#### PCF: + +- Shall be able to create PCC rules using the MP-DCCP-LL steering functionality. + +#### UPF: + +- Shall be able to allocate the "UE Link-specific MP-DCCP-LL" IP addresses. +- Shall be able to allocate MP-DCCP-LL Address Information, i.e. one IP address used for MP-DCCP-LL and one DCCP port number for each MP-DCCP connection. +- Shall apply the N4 rules (e.g. PDRs and associated MARs) to select a MP-DCCP connection and an access (sub-flow) on this connection, for each DL PDU. Each MAR using the MP-DCCP-LL steering functionality shall identify a MP-DCCP Connection. +- Shall select a MP-DCCP connection for an DL PDU based on the steering mode and QoS flow selected with this PDU. +- Shall be able to support the DCCP protocol with multipath extensions. +- Shall apply the QoS Enforcement Rules (QERs) to map the traffic of each MP-DCCP connection to a QoS flow. +- Applies inner header compression based on the received when IHC configuration received in N4 rules + +#### UE: + +- Shall be able to indicate support of MP-DCCP-LL and whether IHC is supported and which compression profile it supports when requesting a MA PDU Session. +- Shall establish *N* MP-DCCP connections to UPF via each access, based on the received " MP-DCCP Connection Setup Information". +- Shall apply the ATSSS rules to select a steering mode for each UL PDU. +- Shall select a MP-DCCP connection for an UL PDU based on the steering mode and QoS flow selected with this PDU. +- Shall be able to support the DCCP protocol with multipath extensions. +- Shall apply the QoS rules to map the traffic of a SDF to a QoS flow. +- Shall apply IHC based on the received compression profile in the MP-DCCP Connection Setup Information + +## 6.4 Solution #3.2: Redundant traffic steering triggered by AF + +### 6.4.1 Introduction + +This solution aims at addressing key Issue #3 about support of redundant traffic steering. In particular, this solution mainly focuses on whether and how to introduce mechanisms to active and deactivate packet duplication in a dynamic manner, e.g. triggered by network entities or application functions. For how the UE and UPF apply the redundancy steering mode, Solution #3.1 specified in clause 6.1 can be applied. + +### 6.4.2 High-level Description + +This solution aims at addressing key Issue #3 about support of redundant traffic steering. In particular, this solution mainly focuses on whether and how to introduce mechanisms to activate and deactivate packet duplication in a dynamic manner, e.g. triggered by network entities or application functions. For how the UE and UPF apply the redundancy steering mode, Solution #3.1 specified in clause 6.1 can be applied. + +Application function (AF) can provide packet loss rate threshold value for specific traffic flows to the PCF via the NEF, triggering PCF to update the PCC rules related to the traffic flows, e.g. using redundant steering mode to transmit the + +traffic flows with applying the packet loss rate threshold value. When the SMF receives the updated PCC rules provided by the PCF, the SMF updates the N4 rules to UPF and ATSSS rules to UE via AMF respectively. The UE and the UPF transmit the traffic flows with redundancy steering mode as defined in Solution #3.1 based on the updated ATSSS rules and N4 rules. + +### 6.4.3 Procedures + +#### 6.4.3.0 General + +Application function (AF) can provide packet loss rate threshold value for specific traffic flows to PCF via the NEF as defined in the clauses 4.3.6.2, 4.15.6.6 or 4.15.6.6a of TS 23.502 [3]. When the parameter (i.e. the packet loss rate threshold value) is updated to PCF, the PCF may decide to trigger redundant traffic steering by updating PCC rules including the updated parameters to the SMF, enabling the SMF modifies the N4 rules and ATSSS rules to UPF and UE respectively. Clause 6.4.3.1 illustrates that the PLR threshold value is provided to PCF via the procedure of AF requesting to influence traffic routing for Sessions not identified by an UE address, while the clause 6.4.3.2 illustrates that the PLR threshold value is provided to PCF via the AF session with required QoS update procedure. + +**Editor's note:** It is FFS which one of the options is be selected. + +#### 6.4.3.1 Procedure of AF providing PLR threshold value via Nnef\_TrafficInfluence\_Create/Update operation service + +![Sequence diagram illustrating the procedure of AF providing PLR threshold value via Nnef_TrafficInfluence_Create/Update operation service. The diagram shows interactions between UE, RAN, AMF, UPF, SMF, PCF, UDR, NEF, and AF. Step 1: AF sends a request to PCF via NEF. Step 2: PCF sends N4 Session Modification to SMF. Step 3: SMF sends N4 Session Modification to UPF. Step 4: SMF sends NAS msg to AMF, which then sends it to UE.](e9b43ac020435f8121e8592f31afdc52_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UPF + participant SMF + participant PCF + participant UDR + participant NEF + participant AF + + Note right of AF: 1. step 1 to step 5 in Figure 4.3.6.2-1 of TS 23.502 including traffic filtering info, Routing profile ID, threshold value (PLR) + AF->>PCF: 1. Request (Nnef_TrafficInfluence_Create/Update) + PCF->>SMF: 2. N4 Session Modification (N4 rules [redundant steering mode, threshold value (PLR), traffic descriptor]) + SMF->>UPF: 3. N4 Session Modification (N4 rules [redundant steering mode, threshold value (PLR), traffic descriptor]) + SMF->>AMF: 4. NAS msg (ATSSS rule[redundant steering mode, threshold value (PLR), traffic descriptor]) + AMF->>UE: 4. NAS msg + +``` + +Sequence diagram illustrating the procedure of AF providing PLR threshold value via Nnef\_TrafficInfluence\_Create/Update operation service. The diagram shows interactions between UE, RAN, AMF, UPF, SMF, PCF, UDR, NEF, and AF. Step 1: AF sends a request to PCF via NEF. Step 2: PCF sends N4 Session Modification to SMF. Step 3: SMF sends N4 Session Modification to UPF. Step 4: SMF sends NAS msg to AMF, which then sends it to UE. + +**Figure 6.4.3.1-1: Procedure of AF providing PLR threshold value via Nnef\_TrafficInfluence\_Create/Update operation service** + +- Step 1 to step 5 in Figure 4.3.6.2-1 of TS 23.502 [3] are performed with following modification: + - The request message in step 1, step 2 and step 4 includes the maximum loss rate tolerated by the application corresponding to the traffic flow identified by the traffic filtering info. + - In step 5, the PCF determines to updates the SMF with corresponding new policy information about the MA PDU Session based on the maximum loss rate received in step 4. The MA PDU Session control information included in the PCC rules indicate that redundant steering mode with PLR threshold value is applied to traffic flows identified by the traffic filtering information. +- SMF derives the updated N4 rules and ATSSS rules based on the updated PCC rules. SMF sends the N4 rules to UPF via N4 Session modification procedure. Both N4 rules and ATSSS rules indicate that when transmitting the + +specific traffic flows identified by the traffic descriptor, the redundant steering mode shall be applied. The redundant steering mode can be triggered dynamically as specific in clause 6.1 in Solution #3.1. + +3. SMF sends Namf\_Communication\_N1N2MessageTransfer message to AMF, which include N1 SM container that consists of the ATSSS rules. +4. AMF sends the ATSSS rules to the UE via NAS message. + +When both UE and UPF obtain the ATSSS rules and N4 rules respectively, they transmit the specific traffic flows by using redundant steering mode as defined in Solution #3.1. + +#### 6.4.3.2 Procedure of AF providing PLR threshold value via Nnef\_AFsessionWithQoS\_Create/Update operation service + +![Sequence diagram showing the procedure of AF providing PLR threshold value via Nnef_AFsessionWithQoS_Create/Update operation service. The diagram involves eight lifelines: UE, RAN, AMF, UPF, SMF, PCF, NEF, and AF. The sequence starts with a block labeled '1. step 1 to step 5 in figure 4.15.6.6-1 or figure 4.15.6.6a-1 of TS 23.502'. This is followed by: 2. PCF sends Npcf_SMPolicyControl_UpdateNotify(PCC rules [traffic descriptor, redundant steering mode, threshold value (PLR)]) to SMF; 3. SMF sends N4 Session Modification (N4 rules [redundant steering mode, threshold value (PLR), traffic descriptor]) to UPF; 4. SMF sends Namf_Communication_N1N2MessageTransfer (ATSSS rule [redundant steering mode, threshold value (PLR), traffic descriptor]) to AMF; 5. AMF sends NAS msg (ATSSS rule [redundant steering mode, threshold value (PLR), traffic descriptor]) to UE.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +Sequence diagram showing the procedure of AF providing PLR threshold value via Nnef\_AFsessionWithQoS\_Create/Update operation service. The diagram involves eight lifelines: UE, RAN, AMF, UPF, SMF, PCF, NEF, and AF. The sequence starts with a block labeled '1. step 1 to step 5 in figure 4.15.6.6-1 or figure 4.15.6.6a-1 of TS 23.502'. This is followed by: 2. PCF sends Npcf\_SMPolicyControl\_UpdateNotify(PCC rules [traffic descriptor, redundant steering mode, threshold value (PLR)]) to SMF; 3. SMF sends N4 Session Modification (N4 rules [redundant steering mode, threshold value (PLR), traffic descriptor]) to UPF; 4. SMF sends Namf\_Communication\_N1N2MessageTransfer (ATSSS rule [redundant steering mode, threshold value (PLR), traffic descriptor]) to AMF; 5. AMF sends NAS msg (ATSSS rule [redundant steering mode, threshold value (PLR), traffic descriptor]) to UE. + +**Figure 6.4.3.2-1: Procedure of AF providing PLR threshold value via Nnef\_AFsessionWithQoS\_Create/Update operation service** + +1. Step 1 to step 5 in figure 4.15.6.6-1 or 4.15.6.6a-1 of TS 23.502 [3] are performed with following modifications: + - The request message in step 1 and 3 includes the QoS parameter of PLR corresponding to the traffic flow identified by the Flow descriptions. + - the TSCTSF is not involved in this procedure, so the steps 3a, 3b, 4b, 6a, 7a and 7b are not applicable. +2. The PCF determines to update the SMF with corresponding new policy information about the MA PDU Session based on the PLR threshold value received in step 1. The MA PDU Session control information included in the PCC rules indicate that redundant steering mode with PLR threshold value is applied to traffic flows identified by the traffic filtering information. +3. SMF derives the updated N4 rules and ATSSS rules based on the updated PCC rules. SMF sends the N4 rules to UPF via N4 Session modification procedure. Both N4 rules and ATSSS rules indicate that when transmitting the specific traffic flows identified by the traffic descriptor, the redundant steering mode shall be applied. The redundant steering mode can be triggered dynamically as specific in clause 6.1 in Solution #3.1. +4. SMF sends Namf\_Communication\_N1N2MessageTransfer message to AMF, which include N1 SM container that consists of the ATSSS rules. +5. AMF sends the ATSSS rules to the UE via NAS message. + +When both UE and UPF obtain the ATSSS rules and N4 rules respectively, they transmit the specific traffic flows by using redundant steering mode as defined in Solution #3.1. + +### 6.4.4 Impacts on Existing Nodes and Functionality + +PCF impact: + +- Ability to determine to apply redundant steering mode with PLR threshold value based on the parameters provided by AF. + +## 6.5 Solution #3.3: New traffic duplication steering mode + +### 6.5.1 Introduction + +This new solution addresses KI#3 on Support of redundant traffic steering. + +### 6.5.2 High-level Description + +With this solution redundant traffic steering is enabled as a new steering mode. The new steering mode enforces, based on certain criteria, that a Packet Data Unit (PDU) is duplicated and sent to the other access. Traffic duplication can be activated and de-activated by setting or re-setting the traffic duplication criteria. + +The UE indicates its capability for support of traffic duplication during the MA PDU session establishment procedure. + +Traffic duplication reduces end-to-end latency and packet loss rate, but at the cost of utilizing resources over both accesses. Thus, selective duplication is a necessity to avoid wasting unnecessarily network, and especially radio resources. The state of each access is dynamically changing over time, and hence a static selection of an access as primary access is suboptimal. + +The new steering mode operates on a per PDU basis in the following way: First, for each PDU the access to be used as primary access is determined either statically, or dynamically based on access conditions, e.g. smallest delay. Second, once the primary access for the PDU is selected and if the duplication criteria are met, the PDU is duplicated and sent over the other (the current secondary) access. + +As part of the ATSSS Rule and MA Rule at SDF level, the UE and the UPF respectively receive the necessary information to use the new steering mode. + +In certain cases, duplication of traffic may be desired only for a specific access, e.g. limited to the non-3GPP access to avoid excessive charging. For this purpose, an Access Constraint Indicator can be provided indicating the access to which duplication is not allowed, i.e. it can be set to 3GPP or non-3GPP. If not set, duplication can be applied for any access. + +1. Regarding the selection of the primary access, the following configuration parameter can be set: + - a. Static: One access is indicated and set as the primary access. The other access is the secondary access used for duplication. + - b. Dynamic: Based on measured performance criteria (e.g. PLR, RTT), the best-performing access is selected as primary access, and the other access is used as secondary access. +2. If none of the duplication criteria described below is provided and the Access Constraint Indicator is not set, all the traffic sent to the primary access is duplicated to the secondary access. If duplication criteria are provided, (part of the) traffic is duplicated to the other access whenever the duplication criteria are met, and the secondary access is available. + +The new steering mode is applicable to GBR and non-GBR traffic as it generally improves the user experience. For GBR traffic networks resources need to be reserved on both accesses. + +**Editor's note:** How the receiver will treat duplicated packets in case of MP-QUIC or MP-DCCP is FFS. + +If present, traffic duplication criteria are evaluated by the UE for the UL and by the UPF for the DL to decide which packets need to be duplicated. One or more of the following traffic duplication criteria can be applied to the traffic on the primary access: + +1. Link quality: Traffic duplication is started or stopped based on link quality measurements, e.g. considering Packet Loss Rate (PLR) or Round Trip Time (RTT) thresholds. The measurement result focuses only on the performance of a single link, i.e. the 3GPP or non-3GPP link in UL or DL. When the measured link performance + +violates the provisioned threshold, the next packets will be duplicated to the other path, otherwise the traffic will be sent on the currently selected primary access. This allows to limit duplication of traffic to the case where the link quality decreases, thus the probability to lose packets increases. These duplication threshold values can be specified in a similar way to existing Threshold values. + +The link quality criterion allows to specify the duplication conditions for the selected primary access. + +Duplication threshold values: One or more threshold values may be provided for a steering mode. A threshold value may be either a value for RTT or a value for PLR. The threshold values are applicable to currently selected primary access and are applied by the UE and UPF to decide whether a PDU shall be duplicated and sent on the other access. + +Applicability: This criterion keeps track of the status of the primary access path and enables the UE and the UPF to independently apply duplication when considered useful based on the measurements available. Thus, it can tackle temporary degradation of an access path in UL and/or DL. + +2. Percentage of duplicated traffic (Max or fixed percentage is possible): The max percentage variant, if indicated, allows to define a duplication budget as the max percentage (e.g. up to 20%) of traffic that can be duplicated over a certain time. It is up to implementation which traffic is duplicated. The fixed percentage variant, if indicated, mandates the exact percentage of traffic that should be duplicated to the secondary access. For example, fixed 20% duplication rate would mean that UE and UPF duplicate 20% of the packets, e.g. every 5th packet. A max of 20% duplication rate would mean that UE and UPF duplicate every 5th or less packet over a certain time period. + +Applicability: Unless fixed percentage is indicated, this criterion enables the UE and the UPF to select how much and which of the traffic to duplicate based for example on locally available information such as the battery state of the UE or other possible criteria, such as: + +- i. Important PDUs: Traffic duplication is applied based on header information indicating whether a PDU is important or not, i.e. only important PDUs are duplicated, and up to the maximum duplication budget. For example, duplicating only PDUs carrying I-frames, and not P-frames (which is indicated in a RTP header extension), in video streams, or duplicating only video and not audio in a video surveillance application. + +NOTE 1: The concrete information in the PDU header that is used for traffic duplication is not specified. + +- ii. Survival time: Survival Time, as defined in TS 23.501 [2], refers to the time period an application can survive without any data burst (with a certain burst size). As per TSC feature, Survival Time is part of TSCAI (see TS 23.501 [2]). The AF may provide the time an application can survive without any burst. It refers to the time that an application consuming a communication service may continue without an anticipated message and can be expressed as the maximum number of messages or in terms of time units. + +NOTE 2: The exact usage of the Survival Time in the TSCAI information is not specified, but the Survival Time has to be included as part of the ATSSS and MA rules to be used by the UE and the UPF respectively. + +Essentially the two criteria are easily combinable since: + +1. the first (Link quality) controls the dynamic activation of duplication of traffic +2. the second (Percentage), upon activation determines which PDUs should be duplicated based on the indicated budget. + +Access selection is based on relative performance of the two accesses, and by selecting always the best one it reduces the need for duplication. On the other hand, Link quality criterion for duplication captures the temporal evolution of access state and relies on absolute performance values. The combination of dynamic primary access selection and partial duplication significantly reduces the duplication overhead since the duplication is applied only when needed and to the extent it is needed. + +The duplication steering mode, together with duplication criteria, needs to be authorized by the PCF in the PCC Rules, and the SMF provides an indication for duplication and the duplication criteria in the ATSSS Rule to the UE, and in the Multi-Access Rule (MAR) to the UPF. After receiving the rules, UE and UPF determine when and how to duplicate traffic based on the provided duplication criteria and the measured performance of each access. + +The AF can also request to start and stop traffic duplication by including the corresponding duplication steering mode indication and traffic duplication criteria to be applied for the application traffic. The NEF provides an API allowing the AF to request start and stop of traffic duplication and providing traffic duplication criteria. + +The duplication steering mode requires that the Multi-Access Rule (MAR) and the ATSSS Rule, both generated by the SMF will need to be updated as follows: + +**Table 6.5.2-1: Updated structure of ATSSS Rule and MA Rule** + +| Information name | Description | Category | SMF permitted to modify in a PDU context | Scope | +|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------|------------------------------------------|-------------| +| Static primary access (1) | Identifies the static primary access (e.g. 3GPP access) | Optional | Yes | PDU context | +| Static secondary access (1) | Identifies the static secondary access (e.g. non-3GPP access) | Optional | Yes | PDU context | +| Dynamic primary access (2) | Identifies the performance criteria (PLR, RTT) to determine the primary access | Optional | Yes | PDU context | +| Access Constraint Indicator | Identifies the accesses to which duplication is not allowed.
If not set, duplication is allowed on all accesses. | Optional | Yes | PDU context | +| Duplication criterion | Identifies the duplication criterion that should be applied and associated parameters (see below) | Optional | Yes | PDU context | +| Duplication threshold values | A Maximum RTT and/or a Maximum Packet Loss Rate. | Optional | Yes | PDU context | +| Survival time | A Maximum duration that, as defined in TS 22.261, is synonymous with the time period an application can survive without any data burst. | Optional | Yes | PDU context | +| Percentage of duplicated traffic | A Maximum or fixed percentage of traffic that can be duplicated plus an indication whether max or fixed percentage is assumed. | Optional | Yes | PDU context | + +(1) Static primary and Static secondary access are configured together. + +(2) Dynamic primary access excludes configuration of Static primary and Static secondary access. + +### 6.5.3 Procedures + +#### 6.5.3.1 AF providing traffic duplication parameters + +Application Function (AF) can provide traffic duplication parameters for specific traffic flows to PCF via the NEF as defined in clauses 4.3.6.2, 4.15.6.6 and 4.15.6.6a of TS 23.502 [3]. When the AF influenced parameters (i.e. Duplication criterion, Duplication threshold values, Survival time or Percentage of duplicated traffic) are updated to PCF, the PCF may decide to trigger redundant traffic steering by updating PCC rules including the updated parameters at the SMF, enabling the SMF to modify the N4 rules and ATSSS rules at UPF and UE respectively. Clause 6.5.3.2 illustrates how the traffic duplication parameters are provided to PCF via the procedure of AF requesting to influence traffic routing for sessions not identified by a UE address, while clause 6.5.3.3 illustrates how the traffic duplication parameters are provided to PCF via the AF session with required QoS update procedure. + +#### 6.5.3.2 Procedure of AF providing traffic duplication parameters via Nnef\_TrafficInfluence\_Create/Update service + +![Sequence diagram showing the procedure of AF providing traffic duplication parameters via Nnef_TrafficInfluence_Create/Update service. The diagram involves nine nodes: UE, RAN, AMF, UPF, SMF, PCF, UDR, NEF, and AF. The sequence starts with a block labeled '1. step 1 to step 5 in Figure 4.3.6.2-1 of TS 23.502 including traffic filtering info, Routing profile ID, traffic duplication parameter'. This is followed by four numbered steps: 2. N4 Session Modification (N4 rules [redundant steering mode, traffic duplication parameter, traffic descriptor]) from SMF to UPF; 3. Namf_Communication_N1N2MessageTransfer (ATSSS rule [redundant steering mode, traffic duplication parameter, traffic descriptor]) from SMF to AMF; 4. NAS msg (ATSSS rule [redundant steering mode, traffic duplication parameter, traffic descriptor]) from AMF to UE.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +Sequence diagram showing the procedure of AF providing traffic duplication parameters via Nnef\_TrafficInfluence\_Create/Update service. The diagram involves nine nodes: UE, RAN, AMF, UPF, SMF, PCF, UDR, NEF, and AF. The sequence starts with a block labeled '1. step 1 to step 5 in Figure 4.3.6.2-1 of TS 23.502 including traffic filtering info, Routing profile ID, traffic duplication parameter'. This is followed by four numbered steps: 2. N4 Session Modification (N4 rules [redundant steering mode, traffic duplication parameter, traffic descriptor]) from SMF to UPF; 3. Namf\_Communication\_N1N2MessageTransfer (ATSSS rule [redundant steering mode, traffic duplication parameter, traffic descriptor]) from SMF to AMF; 4. NAS msg (ATSSS rule [redundant steering mode, traffic duplication parameter, traffic descriptor]) from AMF to UE. + +**Figure 6.5.3.2-1: Procedure of AF providing traffic duplication parameters via Nnef\_TrafficInfluence\_Create/Update operation service** + +1. Step 1 to step 5 in Figure 4.3.6.2-1 of TS 23.502 [3] are performed with following modifications: + - The request message in step 1, step 2 and step 4 includes the maximum loss rate tolerated by the application corresponding to the traffic flow identified by the traffic filtering info. + - In step 5, the PCF determines to update the SMF with corresponding new policy information about the MA PDU Session based on the exceeded threshold value received in step 4. The MA PDU Session control information included in the PCC rules indicate that redundant steering mode with duplication parameters is applied to traffic flows identified by the traffic filtering information. +2. SMF derives the updated N4 rules and ATSSS rules based on the updated PCC rules. SMF sends the N4 rules to UPF via N4 Session modification procedure. Both N4 rules and ATSSS rules indicate that when transmitting the specific traffic flows identified by the traffic descriptor, the redundant steering mode shall be applied. The redundant steering mode can be triggered dynamically as specific in clause 6.5.2. +3. SMF sends Namf\_Communication\_N1N2MessageTransfer message to AMF, which include N1 SM container with the ATSSS rules. +4. AMF sends the ATSSS rules to the UE via NAS message. + +### 6.5.4 Impacts on Existing Nodes and Functionality + +The ATSSS rules and the N4 rules are enhanced with a new steering mode definition and with new parameters. + +SMF: + +- Based on the PCC rules, create ATSSS rules and N4 rules with the new steering mode data including optional traffic duplication criteria. + +PCF: + +- Provide PCC rules considering new steering mode including optional traffic duplication criteria to the SMF. + +UPF: + +- Based on the traffic duplication steering mode and optionally available traffic duplication criteria decide when to duplicate traffic via the available access paths of a MA PDU session for the downlink traffic. + +UE: + +- Based on the traffic duplication steering mode and optionally available traffic duplication criteria decide when to duplicate traffic via the available access paths of a MA PDU session for the uplink traffic. + +AF: + +- AF can request start and stop of traffic duplication for an application session and optionally provide traffic duplication parameter which allow UPF and UE to decide when duplication of traffic is required. + +NEF: + +- NEF provides an API allowing the AF to request start and stop of traffic duplication and providing traffic duplication parameter. + +## 6.6 Solution #3.4: Redundant steering mode with duplication information and trigger mechanisms + +### 6.6.1 Introduction + +KI#3 indicates the need to study a new steering mode in order to enable the transmission of redundant traffic between UE and UPF. The solution proposed in this clause enables the CN to indicate to the UE and to the UPF what percentage of the traffic needs to be duplicated and over which access link. In addition, the solution defines mechanisms that allow the CN to trigger the establishment of a MA PDU Session with Redundant Steering Mode (RSM) to enable its usage in case some QoS requirements (e.g. PER/reliability) cannot be met with a regular (single access) PDU Session. + +NOTE: The working of RSM relies on the support of redundant packet transmission from the underlying protocol e.g. MPTCP, MPQUIC, or MPCCP. + +### 6.6.2 High-level Description + +#### 6.6.2.1 Provision of RSM related parameters to UE and UPF + +The provision of the redundant steering mode (RSM) parameters is based on the following principles: + +- The PCF, based on the QoS requirements from the AF, will generate PCC rules to be sent to the SMF indicating that the redundant steering mode (RSM) is to be used for a certain traffic and/or application. +- Based on the PCC rules, the SMF decides that the redundant steering mode (RSM) needs to be used for a certain traffic and/or application. The SMF also decides how much such traffic needs to be duplicated and over which access path it is to be duplicated. +- The SMF indicates to the UE and to the UPF via ATSSS rules and N4 rules, respectively, the details of the RSM: + - indication of which traffic and/or application is subject to RSM. + - how much of that traffic needs to be duplicated (duplication factor): this may vary between 0 to 100%. If 0% is indicated, it means that no duplication takes place and that all the traffic is sent only over the primary access link. If, e.g. 20, 50 or 100% is indicated, it means that only 20, 50 or 100% of the traffic sent over the primary access link is duplicated over the secondary access link. 100% means that all traffic is duplicated over the secondary access link. The indication can be different for UL and DL. For example, there could be a duplication factor of 50% in UL and of only 30% in DL. + - indication of which of the access paths is the secondary access. If secondary access = 'non-3GPP access', then 100% of the traffic is sent over the 3GPP access path and the X% duplicated PDUs (indicated by the duplication factor) will be sent over the non-3GPP access path. The indication can be different for UL and DL. + +NOTE 1: If the duplication factor is not indicated, it is implicitly assumed that all the traffic is duplicated. + +NOTE 2: How the receiver (i.e. the UPF in UL, the UE in DL) handles duplicated PDUs is up to implementation. For example, for each PDU sent by the sender (i.e. the UE in UL, the UPF in DL) over the primary access whose duplicate PDU is sent over the secondary access, the receiver retains the PDU that arrives at destination first and discards the one arriving later. + +#### 6.6.2.2 Triggering the usage of a MA PDU Session with RSM + +In addition, in scenarios in which the QoS requested for one or more QoS flows of a single access PDU Session cannot be met (e.g. a too high PER), the SMF may decide, based on information provided by the RAN and/or implementation dependent mechanisms, to use, instead use the regular single access PDU Session, a MA PDU Session with RSM to match the QoS requirements from the AF. + +In order to do this, two options are possible: + +- Option 1: UE proactively indicating the possible use of a MA PDU Session. + +If the UE can proactively indicate its willingness to upgrade to a MA PDU Session, then the UE Requested PDU Session Establishment with Network Modification to MA PDU Session procedure can be reused. The UE sends its ATSSS rules with the MA PDU Network-Upgrade Allowed indication and the SMF can trigger the switch to the MA PDU Session with RSM according to the indicated ATSSS rules. + +- Option 2: SMF asking UE to upgrade to a MA PDU Session. + +In that case, UE initially triggers the establishment of a regular single access PDU Session Establishment procedure without indicating ATSSS rules nor MA PDU Session Request. In the PDU Session Establishment Accept the SMF may indicate to the UE that if it establishes a MA PDU Session the provided QoS level will increase. The UE, after receiving such indication, may decide to upgrade to a MA PDU session by modifying the single access PDU Session and sending its ATSSS capabilities together with the MA PDU Request indication. + +### 6.6.3 Procedures + +#### Provision of rules to SMF, UE and UPF + +The solution is based on the reuse of the existing procedures for ATSSS to provision the necessary rules to SMF, UE and UPF: + +- the PCF provides the extended PCC rules (see clause 6.6.2.2) to the SMF at, e.g. UE triggered Service Request (see clause 4.2.3.2 of TS 23.502 [3]); +- the SMF provides the extended ATSSS and N4 rules to the UE and the UPF, respectively, by means of, the MA PDU Session Establishment procedure (see clause 4.22.2 of TS 23.502 [3]). + +#### Triggering of usage of RSM by the SMF + +In order to trigger the establishment of the MA PDU Session: + +- **Option 1: Re-usage of UE Requested PDU Session Establishment with Network Modification to MA PDU Session with a "MA PDU Network-Upgrade Allowed"** + +This option re-uses the UE Requested PDU Session Establishment with Network Modification to MA PDU Session (see clause 4.22.3 of TS 23.502 [3]) with a "MA PDU Network-Upgrade Allowed" indication. The SMF may decide to establish the MA PDU Session based on the fact that the QoS characteristics levels of a certain QoS flow of the PDU Session that is being established do not meet the QoS requirements from the AF. The SMF will then send the appropriate ATSSS rules and N4 rules to the UE and to the UPF, respectively, to initiate the usage of the RSM. + +- **Option 2: Modification of AF session setup and PDU Session Establishment procedures** + +This option is based on the extension of the following procedures. + +#### AF session setup + +The AF uses the procedure for setting up an AF session with the required QoS by sending an Nnnef\_AFsessionWithQoS\_Create message (see clause 4.15.6.6 of TS 23.502 [3]) to indicate the QoS + +requirements for a given UE. The PDU Session is identified by indicating the proper DNN/S-NSSAI combination. The following changes apply to the existing procedure: + +- Step 1: instead of using UE's IP address, the AF indicates that the UE's GPSI to the NEF when it provides the related QoS requirements. + +NOTE 2: It is assumed that the AF knows (e.g. based on application level subscription) when to provide the QoS requirements for the UE even the PDU Session is not yet established. + +- Step 3: + +The NEF temporarily stores the QoS requirements associated to the UE's GPSI and it triggers the storage of a 'retrieve QoS requirements' flag associated to the GPSI and of the NEF's endpoint address in the UDM. This flag is later used at PDU session establishment by the SMF to contact the NEF to retrieve the QoS requirements. + +#### PDU Session Establishment + +The UE Requested PDU Session Establishment (see clause 4.3.2.2.1 of TS 23.502 [3]) is extended with the following changes: + +- Step 4: If the Session Management Subscription data is not available, then, as per current Rel-17 behavior, the SMF retrieves the Session Management Subscription data from the UDM. The SMF identifies the 'retrieve QoS requirements' flag in the UDM and the NEF's endpoint address and retrieves the QoS requirements from the NEF. +- Step 11: the SMF is aware that the QoS requirements for a certain QoS flow of the PDU Session that is being established cannot be met. Because of that the QoS flow is established with lower QoS characteristics levels. +- After step 17: the SMF sends a PDU Session Modification Command message to the UE including an indication that, if the UE switches to MA PDU Session, then the QoS levels will be improved. + +After the UE receives the indication from the SMF and the single access PDU Session is established, the UE may decide to modify the PDU Session into a MA PDU Session by sending its ATSSS capabilities and a MA PDU Request indication. The SMF will then provide the appropriate ATSSS rules and N4 rules to the UE and the UPF, respectively, to initiate the usage of the RSM and improve the QoS provided to the UE (see clause 4.22.2.1 of TS 23.502 [3]). + +### 6.6.4 Impacts on Existing Nodes and Functionality + +#### PCF: + +- Extension of PCC rules to include RSM as a possible steering mode. + +#### NEF: + +- Optional: Receives from AF per-GPSI QoS Requirements and temporarily stores them. +- Optional: Stores in UDM flag to indicate to SMF to contact NEF at PDU session establishment and retrieve QoS requirements. + +#### SMF: + +- Extension of PCC rules/ATSSS rules/N4 rules to include RSM as a possible steering mode. +- Extension of ATSSS rules/N4 rules to include indication of how much traffic needs to be duplicated and over which access path. +- Decides to trigger the establishment of a MA PDU Session with RSM based on QoS conditions. +- Optional: check UDM for flag to retrieve QoS Requirements from NEF at PDU Session establishment. + +#### UE: + +- Extension of ATSSS rules to include indication of RSM, of how much traffic needs to be duplicated and over which access path. + +- Receives indication from SMF to switch to MA PDU Session to improve QoS level of QoS Flow. + +UPF: + +- Extension of N4 rules to include indication of RSM, of how much traffic needs to be duplicated and over which access path. + +UDM: + +- Optional: Stores flag to retrieve QoS Requirements from NEF at PDU Session establishment. + +AF: + +- Optional: Needs to provide per-GPSI QoS Requirements to 5GC before PDU Session Establishment (Nnef\_AFsessionWithQoS\_Create service operation). + +## 6.7 Solution #5.1: Support traffic switching between two non-3GPP paths + +### 6.7.1 Introduction + +This solution addresses KI#5 on support traffic switching between one non-3GPP access path from the UE to a N3IWF in a PLMN and another non-3GPP access path from the UE to a TNGF in the same PLMN. + +### 6.7.2 High-level Description + +In this solution, it is assumed that the two registrations via two non-3GPP access in the same PLMN are performed in order to enable switching the traffic from a source non-3GPP access path to a target non-3GPP access path and after switching the traffic, only one UE registration via non-3GPP access may exist. + +When UE decides to switch traffic of MA PDU Session from source non-3GPP access (e.g. trusted non-3GPP access) path to a target non-3GPP access (e.g. untrusted non-3GPP access) path in the same PLMN, UE shall perform registration procedure via the target non-3GPP access (untrusted non-3GPP access) path. + +The MOBIKE protocol may not be able to support handover procedure between trusted non-3GPP access and untrusted non-3GPP access and vice versa due to the simultaneous changes of the IP address of the two end point of IKEv2, i.e. the UE change of local IP address from source N3GPP access to target N3GPP access and the simultaneous change of GW endpoint from N3IWF to a TNGF. + +N3IWF/TNGF shall select the same AMF based on AN parameters provided by UE. + +AMF shall update UDM with the RAT type of target non-3GPP access after the registration procedure over the target non-3GPP access path is completed. + +When adding user-plane resources over the target non-3GPP access path, SMF may update ATSSS rules and N4 rules to the UE and the UPF respectively to indicate that the traffic have to be send on the target N3GPP access. + +### 6.7.3 Procedures + +This clause specifies how a UE can handover one leg of MA PDU Session from a source non-3GPP access to a target non-3GPP access path. Figure 6.7.3-1 illustrates the procedure of switching traffic of a MA PDU Session from trusted non-3GPP access path to untrusted non-3GPP access path. It can also be applied to the procedure of switching traffic of a MA PDU Session from untrusted non-3GPP access path to trusted non-3GPP access path by replacing the TNAP/TNGF with untrusted non-3GPP access network/N3IWF, and vice versa. + +![Sequence diagram illustrating the switching traffic of a MA PDU Session from trusted non-3GPP access path to untrusted non-3GPP access path. The diagram shows interactions between UE, TNAP, TNGF, AMF, AUSF, SMF, UPF, and UDM. The process starts with the UE registered on trusted non-3GPP access. It then initiates registration on untrusted non-3GPP access (steps 1-4). The N3IWF selects the AMF (3a). The AMF sends an N2 Registration Request (3b). The AMF sends a NAS Security Mode Command (4a) and the UE responds with a NAS Security Mode Complete (4b). The AMF sends an N2 Security Mode Complete (4c) and the UE responds with an IKE_AUTH Res (4d). The AMF sends an Initial Context Setup Req (5a) and the UE responds with an IKE_AUTH Res (5b). The UE completes registration on untrusted non-3GPP access (step 6). The AMF updates the UDM with the RAT type (7). The AMF adds user-plane resources over untrusted non-3GPP access (8). The AMF releases the MA PDU Session over trusted non-3GPP access (9). Finally, the UE performs deregistration on trusted non-3GPP access (10).](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Sequence diagram illustrating the switching traffic of a MA PDU Session from trusted non-3GPP access path to untrusted non-3GPP access path. The diagram shows interactions between UE, TNAP, TNGF, AMF, AUSF, SMF, UPF, and UDM. The process starts with the UE registered on trusted non-3GPP access. It then initiates registration on untrusted non-3GPP access (steps 1-4). The N3IWF selects the AMF (3a). The AMF sends an N2 Registration Request (3b). The AMF sends a NAS Security Mode Command (4a) and the UE responds with a NAS Security Mode Complete (4b). The AMF sends an N2 Security Mode Complete (4c) and the UE responds with an IKE\_AUTH Res (4d). The AMF sends an Initial Context Setup Req (5a) and the UE responds with an IKE\_AUTH Res (5b). The UE completes registration on untrusted non-3GPP access (step 6). The AMF updates the UDM with the RAT type (7). The AMF adds user-plane resources over untrusted non-3GPP access (8). The AMF releases the MA PDU Session over trusted non-3GPP access (9). Finally, the UE performs deregistration on trusted non-3GPP access (10). + +**Figure 6.7.3-1: Switching traffic of a MA PDU Session from trusted non-3GPP access path to untrusted non-3GPP access path** + +0. UE registers to 5GC via trusted non-3GPP access and has established a MA PDU session over trusted non-3GPP access. + 1. The UE shall initiate Registration procedure via untrusted non-3GPP access using step 1 to step 4 in clause 4.12.2.2-1 of TS 23.502 [3]. + 2. UE sends the IKE\_AUTH request which including an EAP-Response/5G-NAS packet that contains the Access Network parameters (AN parameters) and the Registration Request message. The AN parameters shall contain the same information used in the registration procedure over trusted non-3GPP access including the GUAMI, the Selected PLMN ID, the Requested NSSAI (if included) and the Establishment cause. The Registration Request message shall include the non-3GPP Path Switching indication, which indicate that the UE intends to switch traffic between non-3GPP accesses. + 3. The N3IWF shall select the same AMF that TNGF selected via trusted non-3GPP access based on the received AN parameters. The N3IWF shall then forward the Registration Request received from the UE to the selected AMF within an N2 message, which also contains N2 parameters that include the Selected PLMN ID and the Establishment cause. + 4. The AMF shall send a NAS Security Mode Command to UE in order to activate NAS security. The UE then replies the NAS Security Mode Complete message within an EAP/5G-NAS packet as specified in step 9 in clause 4.12.2.2-1 of TS 23.502 [3]. +- NOTE 1: It is assumed that there is no need to perform authentication over untrusted non-3GPP access since security context is available in the selected AMF. +5. The AMF shall send an NGAP Initial Context Setup Request message that includes the N3IWF key. + 6. UE perform registration procedure via untrusted non-3GPP access as specified in step 11 to step 13 in clause 4.12.2.2-1 of TS 23.502 [3]. + 7. When the registration is completed over trusted non-3GPP access, AMF shall update the RAT type of untrusted non-3GPP access with the UDM using Uudm\_UECM\_Update service. AMF shall also initiate a deregistration timer over the untrusted non-3GPP access. The usage of this deregistration timer is to deregister UE over untrusted non-3GPP access without releasing UE context of source (i.e. trusted) non-3GPP access when the deregistration timer is expired and the UE has not completed non-3GPP path switching. + 8. UE adds user-plane resources over untrusted non-3GPP access with the same PDU Session ID of the established MA PDU Session as specified in clause 4.22.7 of TS 23.502 [3] with following clarifications and additions: + +- AMF shall insert "non-3GPP Path Switching indication" in the Nsmf\_PDUSession\_Update SM Context Request to indicate SMF that UE is requested to perform path switching between non-3GPP accesses. + - When adding user-plane resources over untrusted non-3GPP access, SMF shall include additional indication (e.g. RAT type) in Namf\_Communication\_N1N2MessageTransfer to indicate AMF that N2 SM information included in this message should be sent over untrusted non-3GPP access. + - The N4 rules are updated to UPF to indicate that the traffic have to be send on the target N3GPP access. + - The MA PDU Session Establishment Accept message received by the UE may contain updated ATSSS rules which can be applied when there are two non-3GPP access paths available. The updated ATSSS rules shall indicate that the traffic shall be send on the target non-3GPP access path. +9. If the User Plane of the MA PDU Session is activated in untrusted non-3GPP access, the SMF releases of resources over trusted non-3GPP access as specified in clause 4.22.10 of TS 23.502 [3] with following clarifications and additions: +- When releasing user-plane resources over trusted non-3GPP access, SMF shall include additional indication (e.g. RAT Type) in Namf\_Communication\_N1N2MessageTransfer to indicate AMF that N2 SM information included in this message should be sent over trusted non-3GPP access. +- After the resources over trusted non-3GPP access are completely released, the user plane resources of single access PDU session over this access will also be deactivated. +10. If the deregistration timer over untrusted non-3GPP access is expired and AMF is not informed of the completion of non-3GPP access path switching of the UE (i.e. user plane resources over trusted non-3GPP access is released), AMF shall perform deregistration procedure via untrusted non-3GPP access as specified in clause 4.2.2.3.3 of TS 23.502 [3] + +### 6.7.4 Impacts on Existing Nodes and Functionality + +#### UE: + +- Performs Registration with non-3GPP Path Switching indication. +- Temporarily maintains simultaneous parallel user plane tunnel over trusted non-3GPP access and untrusted non-3GPP access. +- When the UE receives the N2 resources Registration Accept message for the target non-3GPP access, the UE shall add user plane resources over target non-3GPP access. + +#### AMF: + +- Initials deregistration timer over target non-3GPP access when registration with non-3GPP Path Switching indication is completed. +- Update the RAT type of target non-3GPP access with the UDM by using Nudm\_UECM\_Update service after registration is completed. +- Perform Deregistration when deregistration timer is expired and the AMF is not informed of the completion of non-3GPP access path switching of the UE. +- Insert non-3GPP Path Switching indication in the Nsmf\_PDUSession\_Update SM Context Request when UE adds user-plane resources over another non-3GPP access. + +#### SMF: + +- Indicates to AMF which access path should the N2 SM information be sent. +- Update N4 rules and ATSSS rules when UE requests to switch traffic between non-3GPP accesses. + +#### UPF: + +- Temporarily maintains simultaneous parallel user plane tunnel over trusted non-3GPP access and untrusted non-3GPP access. + +#### UDM: + +- Update the RAT type of target non-3GPP access by using Nudm\_UECM\_Update service. + +## 6.8 Solution #5.2: Delaying UDM Registration until non-3GPP access switching completes + +### 6.8.1 Introduction + +This solution addresses Key Issue #5 "Switching traffic of an MA PDU Session between two non-3GPP access paths" by allowing two simultaneous registrations over two non-3GPP accesses. In this solution, in order to minimize overall system impact, the AMF delays UDM Registration until access switching is completed. + +### 6.8.2 High-level Description + +When a UE establishes MA PDU Session, the SMF may indicate to the UE whether non-3GPP access switching is supported. Based on this indication, the UE may determine to change non-3GPP access leg. Whether and when to switch non-3GPP access is determined by the UE. If the UE determines to switch access, the UE performs registration over the new non-3GPP access with new registration type to indicate the registration is for switching non-3GPP access. + +The AMF follows normal registration procedure as described in TS 23.502 [3] but does not perform UDM registration. After the Registration procedure is completed, the UE sends PDU Session Establishment message to add new non-3GPP access leg to the existing MA PDU Session. After the access leg over the new non-3GPP access is established, the UE and UPF starts sending traffic over the new non-3GPP access leg and stops sending traffic over the old non-3GPP access leg. The AMF triggers AN release procedure over the old non-3GPP access and performs UDM Registration. + +### 6.8.3 Procedures + +This procedure assumes that the UE is registered over untrusted non-3GPP access first and then switches trusted non-3GPP access. + +![Sequence diagram of the overall non-3GPP access switching procedure. Lifelines: UE, NG-RAN, N3IWF, TNGF, AMF, SMF, UPF, UDM. The process starts with a pre-condition: '1. Registered over 3GPP and untrusted non-3GPP access and established MA PDU Session'. Step 2: UE sends 'Registration Request (Registration type = access switching, PDU Sessions To be Activated)' to AMF via NG-RAN and N3IWF. Step 3: AMF performs 'Authentication' with UDM. Step 4: AMF sends 'Initial Context Setup Request / Response' to TNGF. Step 5: AMF sends 'Nsmf_PDUSession_UpdateSMContext Request (Switching Notification)' to SMF. Step 6: SMF sends 'Nsmf_PDUSession_UpdateSMContext Response (N2 information)' to AMF. Step 7: SMF performs 'User plane establishment over trusted non-3GPP access' with UPF. Step 8a: AMF sends 'Nudm_UECM_Registration' to UDM. Step 8b: AMF sends 'Nudm_UECM_DeregistrationNotify' to UDM. A pre-condition box '9. AN Release over untrusted non-3GPP access' is shown. Step 10: AMF sends 'Registration Accept' to UE via TNGF and N3IWF.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +Sequence diagram of the overall non-3GPP access switching procedure. Lifelines: UE, NG-RAN, N3IWF, TNGF, AMF, SMF, UPF, UDM. The process starts with a pre-condition: '1. Registered over 3GPP and untrusted non-3GPP access and established MA PDU Session'. Step 2: UE sends 'Registration Request (Registration type = access switching, PDU Sessions To be Activated)' to AMF via NG-RAN and N3IWF. Step 3: AMF performs 'Authentication' with UDM. Step 4: AMF sends 'Initial Context Setup Request / Response' to TNGF. Step 5: AMF sends 'Nsmf\_PDUSession\_UpdateSMContext Request (Switching Notification)' to SMF. Step 6: SMF sends 'Nsmf\_PDUSession\_UpdateSMContext Response (N2 information)' to AMF. Step 7: SMF performs 'User plane establishment over trusted non-3GPP access' with UPF. Step 8a: AMF sends 'Nudm\_UECM\_Registration' to UDM. Step 8b: AMF sends 'Nudm\_UECM\_DeregistrationNotify' to UDM. A pre-condition box '9. AN Release over untrusted non-3GPP access' is shown. Step 10: AMF sends 'Registration Accept' to UE via TNGF and N3IWF. + +**Figure 6.8.2-1: Overall non-3GPP access switching procedure** + +1. The UE is registered over 3GPP access and untrusted non-3GPP access and established MA PDU Session. During the MA PDU Session Establishment, the UE indicates whether it supports non-3GPP access switching in the PDU Session Establishment Request message. The AMF also indicates whether it supports non-3GPP access switching to the SMF. Considering the received capabilities of the UE, AMF and SMF capability, the SMF indicates whether non-3GPP access switching is supported to the UE in the PDU Session Establishment Accept message. +2. The UE registers over trusted non-3GPP access with new Registration type = non-3GPP access switching. The UE includes in the List Of PDU Sessions To Be Activated the MA PDU Sessions that user plane resources are established over untrusted non-3GPP access. + +NOTE: It is assumed that the selected TNGF supports the S-NSSAI of the established MA PDU Session. This could be ensured by the UE or done by the network. In case the AMF needs to redirect the UE to the other TNGF, the AMF does not trigger non-3GPP access switching and wait until redirection procedure is finished (e.g. may be done between step 3 and step 4 or UE may need to trigger registration with new TNGF and then performs non-3GPP access switching depending solutions). The details of redirection is in the scope of 5WWC\_Ph2 study. + +3. The AMF may perform authentication procedure based on existing procedure. +4. The AMF sends Initial UE Context Setup Request message to the TNGF. +5. After the Initial UE Context Setup procedure is completed, the AMF notifies to the SMF that the UE requested non-3GPP access switching. +- 6-7. The SMF establishes user plane resources over the trusted non-3GPP access. At this point, there can be three user plane tunnels (i.e. 3GPP access, untrusted non-3GPP access, trusted non-3GPP access) in the UE and UPF. When the SMF establishes user plane resources over the trusted non-3GPP access, the SMF shall set the + +target access type to "trusted non-3GPP access" so that the AMF delivers the N2 information to the trusted non-3GPP access. + +8. The AMF performs UDM Registration by triggering Nudm\_UECM\_Registration service operation. The UDM triggers Nudm\_UECM\_DeregistrationNotify service according to the existing procedure. After this point, all signalling and Reachability procedures are performed over the trusted non-3GPP access. +9. The AMF performs AN release procedure over the untrusted non-3GPP access. As a result of this procedure, user plane resources over untrusted non-3GPP access of MA PDU is completely released. When the UE and UPF recognize that user plane resources over untrusted non-3GPP access are released, the UE and UPF starts to send traffic over trusted non-3GPP access. +10. The AMF sends Registration Accept message to the UE. When the UE receives Registration Accept message, the UE considers that the UE is deregistered from untrusted non-3GPP access and registered over trusted non-3GPP access. + +### 6.8.4 Impacts on Existing Nodes and Functionality + +UE: + +- Performs Registration with new registration type. +- Indicates to the SMF that the UE supports non-3GPP access switching during the MA PDU Session Establishment. +- Temporarily maintains simultaneous parallel user plane tunnel over untrusted 3GPP access and trusted non-3GPP access. +- When the UE receives the Registration Accept message for the target non-3GPP access, the UE considers that it is deregistered from the source non-3GPP access. + +AMF: + +- During the Registration procedure, delay UDM registration until non-3GPP access switching is completed. +- Indicates to the SMF that the AMF supports non-3GPP access switching during the MA PDU Session Establishment. +- Notifies to the SMF that the UE requested non-3GPP access switching during the Registration procedure. +- Performs AN release over old access during the Registration procedure + +SMF: + +- Indicates to the UE whether the MA PDU Session supports non-3GPP access switching during the MA PDU Session Establishment. + +UPF: + +- Temporarily maintains simultaneous parallel user plane tunnel over untrusted 3GPP access and trusted non-3GPP access. + +## 6.9 Solution #5.3: Path switching between non-3GPP accesses + +### 6.9.1 Introduction + +The solution in clause 6.9 addresses the objective of KI#5, i.e. it specifies how the data traffic of an MA PDU Session to be switched between two non-3GPP access paths, both of them using the same PLMN. + +### 6.9.2 High-level Description + +This solution uses the following principles to switch the data traffic of an MA PDU Session between two Non-3GPP access paths: + +- a. UE uses existing procedures to register to 5GC via a Non-3GPP access network (e.g. an untrusted Non-3GPP access network). Optionally, the UE may also register to 5GC via a 3GPP access network (e.g. via NG-RAN). +- b. MA PDU Session is established using the existing procedures specified in clause 4.22.2 of TS 23.502 [3] and data traffic is transferred over the paths of the MA PDU Session. +- c. UE discovers a new Non-3GPP access network (e.g. a trusted Non-3GPP access networks) and registers to 5GC via this access network by indicating "Non-3GPP path switch". This allows the AMF to maintain temporarily two registrations via two non-3GPP accesses until the path switch is completed. +- d. UE initiates the path switch by sending, via the new Non-3GPP access network, an MA PDU Session Establishment Request (using the same PDU session ID), which triggers the SMF to establish user-plane resources for the MA PDU Session over the new Non-3GPP access network. +- e. When the user-plane resources for the MA PDU Session over the new Non-3GPP access network are established, the SMF triggers the AMF to deregister the UE from the old Non-3GPP access network (e.g. the untrusted Non-3GPP access network). +- f. The UE can trigger the path switching procedure based on internal implementation Alternatively, the UE can decide to switch data traffic based on URSP policies (if available) received from the PCF indicating the priority of a non-3GPP access (priority of the trusted and untrusted non-3GPP accesses) which are part of a MA PDU session. + +### 6.9.3 Procedures + +Figure 6.9.3-1 below depicts the key steps of the solution, which enables the data traffic of an MA PDU Session to be switched from a non-3GPP access path using a N3IWF to a non-3GPP access path using a TNGF. The same steps can be used to switch the data traffic of an MA PDU Session between any non-3GPP access paths (using either N3IWF or TNGF). + +![Sequence diagram illustrating the procedure for enabling data traffic switching between two non-3GPP access paths. The diagram shows interactions between UE, NG-RAN, AMF, UDM, SMF, N3IWF, and TNGF. It details registration steps over 3GPP and non-3GPP accesses, NAS transport, SM context creation and updates, and the final traffic switching and deregistration process.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +The sequence diagram illustrates the procedure for enabling data traffic switching between two non-3GPP access paths. The participants involved are UE, NG-RAN, AMF, UDM, SMF, N3IWF, and TNGF. + +**Sequence of Events:** + +- 1. (Optional) UE registers via 3GPP access** +Registration type = Initial +AMF registers with UDM for 3GPP access and provides its GUAMI and RAT type=NR +- 2. UE registers via untrusted non-3GPP access** +Registration type = Initial +The AMF may indicate to UE that it supports registration for non-3GPP path switch +AMF registers with UDM for non-3GPP access and provides its GUAMI and RAT type (e.g., Virtual) +- 3a. UL NAS Transport** +Initiate MA PDU Session establishment +PDU Session Id=X, S-NSSAI, DNN, +Request type=MA PDU request +PDU Session Est. Request () +- 3b. Create SM Context Request** +SUPI, PDU Session Id=X, S-NSSAI, DNN, +MA Request Indication +AN Type=non-3GPP +Additional AN Type=3GPP +RAT type=Virtual +PDU Session Est. Request () +- 3c. UECM Registration Req.** +PDU Session Id=X, DNN, SUPI, +SMF UUID +- 3d. Additional steps to complete the MA PDU Session establishment** +User-plane resources established over both accesses +- 4. UE registers via trusted non-3GPP access (same AMF selected)** +Registration type = **Non-3GPP path switch** +AMF does not release the existing registration via untrusted non-3GPP access. +It maintains two registrations via non-3GPP access until the path switch is completed. +AMF starts a timer. +- 5a. UL NAS Transport** +Request UP resources via trusted non-3GPP access +PDU Session Id=X, S-NSSAI, DNN, +Request type=MA PDU request +PDU Session Est. Request () +- 5b. Update SM Context Request** +SUPI, PDU Session Id=X +Non-3GPP path switch indication +RAT type=Trusted\_WLAN +PDU Session Est. Request () +- 5c. Additional steps to complete the user-plane resources establishment over trusted non-3GPP access** +- 6a. UE switches all traffic from untrusted non-3GPP access to trusted non-3GPP access** +- 6b. The UPF switches all traffic from untrusted non-3GPP access to trusted non-3GPP access** +- 7. SM Context Status Notify** +Resource status: Non-3GPP path switch completed +- 8. The AMF initiates deregistration via untrusted non-3GPP access and updates the UDM with RAT type = Trusted\_WLAN for non-3GPP access.** +The AMF stops the timer. +- 9. When the timer in AMF expires, the AMF initiates deregistration via trusted non-3GPP access.** + +Sequence diagram illustrating the procedure for enabling data traffic switching between two non-3GPP access paths. The diagram shows interactions between UE, NG-RAN, AMF, UDM, SMF, N3IWF, and TNGF. It details registration steps over 3GPP and non-3GPP accesses, NAS transport, SM context creation and updates, and the final traffic switching and deregistration process. + +**Figure 6.9.3-1: Procedure for enabling data traffic switching between two non-3GPP access paths** + +- [Optionally] the UE performs an initial 5G registration over 3GPP access in a PLMN. The selected AMF registers with UDM for 3GPP access and provides its GUAMI and RAT type = NR. +- The UE selects an N3IWF and performs an initial 5G registration over untrusted non-3GPP access in the same PLMN using step 1 to step 13 in clause 4.22.9 of TS 23.502 [3] and with the following differences and clarifications: + - The UE indicates its support for "Non-3GPP path switch": + - "Non-3GPP path switch" indication indicates that this UE is capable of switching traffic of an MA PDU Session between two non-3GPP access paths. + - The same AMF is selected, as the one in the previous step. + - The AMF indicates to the UE its support for "Non-3GPP path switch". + +- iv) The AMF registers with UDM for non-3GPP access and provides its GUAMI and RAT type = Virtual or WLAN. + +NOTE: The above procedure may be performed at any time the UE initiates a registration request (i.e. to any AN). + +3. The UE requests an MA PDU Session, as specified in clause 4.22.2 of TS 23.502 [3]. User-plane resource are established over 3GPP access and over untrusted non-3GPP access. Data traffic over the MA PDU Session is exchanged between the UE and UPF using the two accesses. +4. The UE detects a trusted non-3GPP access network that supports 5G connectivity to the same PLMN. The UE decides to switch the data traffic transferred over the untrusted non-3GPP access of the MA PDU Session to the detected trusted non-3GPP access network as described in clause 6.9.2f. For this purpose, the UE initiates a 5G registration over trusted non-3GPP access using step 1 to step 15 in clause 4.12a.2.2 of TS 23.502 [3] with the following differences and clarifications: + - i) Indicates "Non-3GPP path switch". + - This indication indicates that the registration over trusted non-3GPP access is required for switching the data traffic of an MA PDU Session from one non-3GPP access path to another non-3GPP access path. + - ii) After the UE is registered via trusted non-3GPP access with the indication "Non-3GPP path switch", the AMF does not release the existing registration via untrusted non-3GPP access. + - iii) A timer value indicating how long the network will maintain two registrations via non-3GPP access is configured in the AMF. The AMF shall start a timer and maintain the two registrations via non-3GPP access until the path switch is completed or until this timer is equal to the configured timer value: + - As shown below (see step 9), when the timer expires, the AMF initiates deregistration via the TNGF. +5. The UE initiates the non-3GPP path switch by requesting user-plane resources via trusted non-3GPP access. To request these user-plane resources: + - i) The UE sends a PDU Session Establishment Request via the TNGF, which contains request type = MA PDU Request and the identity of the existing MA PDU Session. + - ii) The AMF sends an Update SM Context Request to SMF, which contains a "Non-3GPP path switch indication": + - This indication informs the SMF that the PDU Session Establishment Request is sent to enable path switching from the existing non-3GPP access of the MA PDU Session to a new non-3GPP access. + - iii) The AMF inserts the "Non-3GPP path switch indication" in the Update SM Context Request because the UE is registered with type "Non-3GPP path switch" (see step 4). + - iv) The SMF initiates the user-plane resources establishment over trusted non-3GPP access. +6. After user-plane resources over trusted non-3GPP access are established, the UE switches all uplink MA PDU Session traffic from untrusted non-3GPP access to trusted non-3GPP access. Similarly, the UPF switches all downlink MA PDU Session traffic from untrusted non-3GPP access to trusted non-3GPP access (for this the SMF modifies the existing N4 connection). +7. The SMF sends an SM Context Status Notify message to AMF to indicate that the non-3GPP path switch has been completed. +8. After receiving the SM Context Status Notify message, the AMF updates the UDM with RAT type = Trusted\_WLAN for non-3GPP access. The AMF initiates deregistration procedure for untrusted Non-3GPP access (see clause 4.12.3 of TS 23.502 [3]). Also, the AMF stops the timer that was started in step 4. After this step, the UE has only one 5G registration via non-3GPP access. +9. [Conditional] If AMF timer started in step 4 expires, the AMF deregisters the UE via trusted non-3GPP access. After this step, the UE has only one 5G registration via non-3GPP access. + +### 6.9.4 Impacts on Existing Nodes and Functionality + +UE: + +- Indicates to the AMF that the UE supports non-3GPP access switching during the Registration Request message. +- Trigger the switching from one N3GPP path to another N3GPP path is based on UE implementation. +- Use a new indication when performing the switching during the registration procedure via the other Non-3GPP path. + +AMF: + +- Indicate to SMF that Non-3GPP path switching is required for the MA PDU session. +- A configured timer value indicating how long the network will maintain two registrations via non-3GPP accesses. +- Configured timer value used to trigger a de-registration if a non-3GPP access path switch has not completed within the allotted provisioned time. + +SMF/UPF: + +- Perform the traffic switching from untrusted N3GPP access to trusted N3GPP access or vice versa. + +UDM: + +- UDM is only expected to be updated with the new RAT type information (e.g. from Virtual/WLAN to Trusted\_ WLAN) after the path switching has been performed successfully. + +## 6.10 Solution #5.4: Non-3GPP access path switching in MA PDU Session + +### 6.10.1 Introduction + +This solution addresses KI#5 on switching traffic of an MA PDU Session between two non-3GPP access paths. + +### 6.10.2 High-level Description + +In this solution, it is assumed that the UE is able to register to 5GC over two non-3GPP access paths for the duration of switching the non-3gpp access path of an established MA PDU Session, and the duration is decided by the network. Each non-3GPP access path is identified by the RAT Type of the non-3GPP access network (e.g. one non-3GPP access path is using an N3IWF, and the other non-3GPP access path is using an TNGF). + +It is assumed that the Non-3GPP access path switching feature is supported only for the MA PDU Session, therefore any UE which does not have ATSSS Capability cannot request to the network of two Non-3GPP access registrations for purpose of Non-3GPP access path switching of an MA PDU Session. + +The key points of the solution are as follows: + +- The UE triggers the non-3GPP access path switching of the established MA PDU Session. The AMF detects this by presence of ATSSS path switching indication, and List of PDU Sessions To Be Activated included in the Registration request. +- The AMF determines the RAT Type of the target non-3GPP access path which the Registration request is sent, and the RAT Type of the source non-3GPP access path which the UE is already registered over non-3GPP access. The AMF provides both source RAT Type and target RAT Type to the SMF, and requests to SMF the Access Path Switching Lifetime Value. The Access Path Switching Lifetime Value is used to decide the duration of switching. The AMF decides the value of Access Path Switching Timer based on its local configuration and the value received from the SMF, and provides to the UE. +- The UE requests MA PDU Session Establishment via target non-3GPP access network before the Access Path Switching Timer is expired. The AMF determines whether this request is for the second non-3GPP access path, and requests to the SMF to allocate N3 CN Tunnel Info for Target Access Network. The SMF distinguishes two non-3GPP access paths by Target RAT Type and Source RAT Type provided by the AMF. + +- The target non-3GPP access network also allocates the N3 AN Tunnel Info. If the AMF receives the successful result in N2 Session Response and the SMF receives the AN Tunnel Info of target non-3GPP access network, the access traffic switching is possible, and the traffic is transmitted via the target non-3GPP access network. +- The SMF initiates the MA PDU Session release over the source non-3GPP access. Any corresponding SM Context and UE Context is removed from the network. UP resources via source non-3GPP access are released. +- The AMF initiates the Deregistration of the UE over the source non-3GPP access. + +### 6.10.3 MA PDU Session Access Path Switching procedure + +![Sequence diagram of the Non-3GPP access path switching procedure for an MA PDU Session. The diagram shows interactions between UE, N3IWF, TNGF, AMF, SMF, and UPF. The process starts with a non-3GPP access path switching trigger at the UE. The UE sends a Registration Request to the AMF via N3IWF. The AMF sends an Nsmf_PDUSession_UpdateSMContext Request to the SMF. The SMF sends an N4 Session Modification to the UPF. The AMF sends a Registration Accept to the UE via N3IWF. The UE sends a PDU Session Establishment Request over trusted non-3GPP access to the AMF. The AMF sends an Nsmf_PDUSession_CreateSMContext Request to the SMF. The SMF sends an N4 Session Modification to the UPF. The AMF sends an N2 Session Request to the TNGF. The TNGF sends an AN-specific resource setup to the UE. The UE sends UL Data to the TNGF. The TNGF sends an N2 Session Response to the AMF. The AMF sends an Nsmf_PDUSession_UpdateSMContext Request to the SMF. The SMF sends an N4 Session Modification to the UPF. The UE receives DL Data from the TNGF. Finally, the network initiates MA PDU Session release over untrusted non-3GPP access and network initiated De-registration over untrusted non-3GPP access.](73b28b0f5e3be628bb5a3d6bd1d79d21_img.jpg) + +``` + +sequenceDiagram + participant UE + participant N3IWF + participant TNGF + participant AMF + participant SMF + participant UPF + + Note left of UE: 1. Non-3GPP access path switching of MA PDU Session is triggered + UE->>AMF: 2. Registration Request (ATSSS path switching indication, List Of PDU Session To Be Activated=PDU Session ID of MA PDU Session) + AMF->>SMF: 3. Nsmf_PDUSession_UpdateSMContext Request (ATSSS path switching indication, List Of PDU Sessions To Be Activated=PDU Session ID of MA PDU Session, Target RAT Type, Source RAT Type) + SMF->>AMF: 4. Nsmf_PDUSession_UpdateSMContext Response (Access Path Switching Lifetime Value) + AMF->>UE: 5. Registration Accept (Access Path Switching Timer) + UE->>AMF: 6. PDU Session Establishment Request over trusted non-3GPP access (MA PDU Request, PDU Session ID of MA PDU Session) + AMF->>SMF: 7. Nsmf_PDUSession_CreateSMContext Request (ATSSS path switching indication, PDU Session ID of MA PDU Session, Target RAT Type, Source RAT Type) + SMF->>UPF: 8. N4 Session Modification + SMF->>AMF: 9. Namf_Communication_N1N2MessageTransfer (CN Tunnel Info for trusted non-3GPP access) + AMF->>TNGF: 10. N2 Session Request (PDU Session Accept, CN Tunnel Info for Target Access Network) + TNGF->>UE: 11. AN-specific resource setup (PDU Session Accept) + UE->>TNGF: UL Data + TNGF->>AMF: 12. N2 Session Response (AN Tunnel Info for trusted non-3GPP access) + AMF->>SMF: 13. Nsmf_PDUSession_UpdateSMContext Request (AN Tunnel Info for trusted non-3GPP access, RAT Type) + SMF->>UPF: 14. N4 Session Modification + TNGF->>UE: DL Data + Note right of UE: 15. Network initiated MA PDU Session release over untrusted non-3GPP access + Note right of UE: 16. Network initiated De-registration over untrusted non-3GPP access + +``` + +Sequence diagram of the Non-3GPP access path switching procedure for an MA PDU Session. The diagram shows interactions between UE, N3IWF, TNGF, AMF, SMF, and UPF. The process starts with a non-3GPP access path switching trigger at the UE. The UE sends a Registration Request to the AMF via N3IWF. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext Request to the SMF. The SMF sends an N4 Session Modification to the UPF. The AMF sends a Registration Accept to the UE via N3IWF. The UE sends a PDU Session Establishment Request over trusted non-3GPP access to the AMF. The AMF sends an Nsmf\_PDUSession\_CreateSMContext Request to the SMF. The SMF sends an N4 Session Modification to the UPF. The AMF sends an N2 Session Request to the TNGF. The TNGF sends an AN-specific resource setup to the UE. The UE sends UL Data to the TNGF. The TNGF sends an N2 Session Response to the AMF. The AMF sends an Nsmf\_PDUSession\_UpdateSMContext Request to the SMF. The SMF sends an N4 Session Modification to the UPF. The UE receives DL Data from the TNGF. Finally, the network initiates MA PDU Session release over untrusted non-3GPP access and network initiated De-registration over untrusted non-3GPP access. + +Figure 6.10.3-1: Non-3GPP access path switching procedure for an MA PDU Session + +The above Figure 6.10.3-1 shows how the non-3GPP access path of an MA PDU Session is switched to another Non-3GPP access path. + +0. The UE is registered over untrusted non-3GPP access and established MA PDU Session. The UE may be registered over 3GPP access. During registration procedure over non-3GPP access, the UE includes its capability of non-3GPP path switching in the Registration Request message and the AMF informs to UE whether the network supports non-3GPP access path switching for MA PDU Session. +1. The UE determines that the existing non-3GPP access path of the MA PDU Session needs to be changed to trusted non-3GPP access. +2. In the Registration Request message, the UE includes ATSSS path switching indication and List Of PDU Sessions To Be Activated. ATSSS path switching indication indicates that this request is for the registration for the second non-3GPP access path via target non-3GPP access network (the trusted non-3GPP access in this case). List Of PDU Sessions To Be Activated includes the PDU Session ID of the MA PDU Session. + +The same AMF is selected using GUAMI provided by the UE. If the AMF supports non-3GPP access path switching for MA PDU Session, the AMF determines whether this request is for registration over the second non-3GPP access path of the established MA PDU Session. AMF determines RAT Type of trusted non-3GPP access (as defined in clause 5.3.2.3 of TS 23.501 [2]), and checks if it is different with that of the existing non-3GPP access path of the MA PDU Session. + +- 3 The AMF invokes the Nsmf\_PDUSession\_UpdateSMContext Request which includes the ATSSS path switching indication, PDU Session ID of the MA PDU Session, Target RAT Type (e.g. trusted W-LAN), and Source RAT Type (e.g. untrusted non-3GPP). +4. The SMF sends the Nsmf\_PDUSession\_UpdateSMContext Response which includes Access Path Switching Lifetime Value. The Access Path Switching Lifetime Value indicates how long the SMF will accept the MA PDU Session Establishment request over the second non-3GPP access path. The SMF starts a timer corresponding to the Access Path Switching Lifetime Value, and if the SMF does not receive any successful Nsmf\_PDUSession\_UpdateSMContext Request including AN Tunnel Info over the target non-3GPP access before expiry of this timer, the SMF maintains the source non-3GPP access path. +5. The AMF sends Registration Accept which includes Access Path Switching Timer. The AMF starts De-registration timer corresponding to the Access Path Switching Timer. The AMF can decide Access Path Switching Timer as longer value than Access Path Switching Lifetime Value received from the SMF in step 5, to avoid triggering the de-registration before the MA PDU Session Establishment over the second non-3GPP access path is finished. +6. The UE requests MA PDU Session Establishment over the trusted non-3GPP access before the expiry of the Access Path Switching Timer received in step 6. +7. The AMF invokes the Nsmf\_PDUSession\_CreateSMContext Request which includes ATSSS path switching indication, PDU Session ID of the MA PDU Session, Target RAT Type, and Source RAT Type. The SMF detects that this MA PDU Session request is related to the request of step 4. AMF updates its registration to UDM with Target RAT Type (e.g. untrusted non-3GPP) by invoking Nudm\_UECM\_Registration service operation. +8. The CN Tunnel Info for trusted non-3GPP access is allocated. +9. The SMF sends Namf\_Communication\_N1N2MessageTransfer which includes CN Tunnel Info for trusted non-3GPP access in N2 SM information. +10. The AMF sends N2 Session Request to the TNGF. +11. The TNGF issues AN specific resource setup with the UE, and the the AN Tunnel Info for the trusted non-3GPP access is allocated. The UE switches all uplink traffic from untrusted non-3GPP access to trusted non-3GPP access. +12. The Target Access Network sends N2 Session Response which includes the AN Tunnel Info corresponds to the TNGF address of the N3 tunnel for the MA PDU Session. +13. The AMF sends the N2 SM information received from TNGF and the RAT Type of trusted non-3GPP access to the SMF +14. The SMF initiates an N4 Session modification procedure with the UPF. The SMF provides the AN Tunnel Info to the UPF. The UPF provides an N4 Session Modification Response to the SMF. After this step, there can be three user plane tunnels (i.e. 3GPP access, untrusted non-3GPP access, and trusted non-3GPP access) in the UE and the UPF. The UPF switches all downlink traffic from untrusted non-3GPP access to trusted non-3GPP access. +15. The SMF initiates the MA PDU Session release over untrusted non-3GPP access. Any corresponding SM Context and UE Context is removed from the network. UP resources over untrusted non-3GPP access is deactivated. +16. The AMF initiates the Deregistration of the UE over untrusted non-3GPP access. + +### 6.10.4 Impacts on Existing Nodes and Functionality + +UE: + +- Triggers the non-3GPP access path switching of MA PDU Session. + +- Indicates UE's capability of non-3GPP access path switching in Registration request during non-3GPP access registration procedure. +- Indicates in Registration request that this request is for the registration for the second non-3GPP access path by using ATSSS path switching indication and the List Of PDU Session To Be Activated. + +#### AMF: + +- Informs to UE whether the network supports non-3GPP access path switching for MA PDU Session during registration procedure over non-3GPP access. +- Determines whether the Registration request from the UE is for registration over the second non-3GPP access path of the established MA PDU Session by using ATSSS path switching indication and the List Of PDU Session To Be Activated. +- Provides to SMF the RAT Type of the target non-3GPP access and the RAT Type of the source non-3GPP access. +- Decides the Access Path Switching Timer and provides to the UE to inform the duration of non-3GPP access path switching. +- Updates the UDM registration for the target non-3GPP access after user-plane resources of the target non-3GPP access are established. + +#### UDM: + +- Updates RAT Type for AMF registration with the RAT type of target non-3GPP access after user-plane resources of the target non-3GPP access are established. + +#### SMF: + +- Decides the Access Path Switching Lifetime Value and provides to the AMF to assist the AMF to finally decide the value of Access Path Switching Timer for the UE. + +#### UPF: + +- Allocates the N3 CN Tunnel Info for the second non-3GPP access path. + +## 6.11 Solution #2.2: MPQUIC steering functionality using UDP proxying over HTTP + +### 6.11.1 Introduction + +The solution in clause 6.11 specifies a new ATSSS steering functionality, called Multipath QUIC (MPQUIC) steering functionality, and addresses the objective of KI#2 for a QUIC-based steering functionality. It borrows several aspects from solutions studied in TR 23.700-93 [5], mainly from Solution #6 "MPQUIC-LL Steering Functionality" and from Solution #14 "Proxy based solution using MP-QUIC". + +The solution is primarily based on RFC 9298 "proxying UDP in HTTP" [27], which specifies how UDP traffic can be transferred between a client (UE) and a proxy (UPF) using the HTTP/3 protocol [28]. The HTTP/3 protocol operates on top of the QUIC protocol [6], which supports simultaneous communication over multiple paths, as defined in draft-ietf-quic-multipath [10]. + +The solution supports the following transport modes for transmitting a UDP flow between UE and UPF (see further details in clause 6.11.3, step 5): + +- Datagram mode 2: This transport mode is the mode already supported in RFC 9298 [27]. It encapsulates UDP packets within QUIC Datagram frames and provides unreliable transport with no sequence numbering and no packet reordering / deduplication. It can be applied for UDP flows where the application is robust against out-of-order delivery and jitter (e.g. because it can perform itself appropriate packet reordering / deduplication). +- Datagram mode 1: This transport mode is an extension of the mode supported in RFC 9298 [27]. It encapsulates UDP packets within QUIC Datagram frames and provides unreliable transport but with sequence numbering and with packet reordering / deduplication. It can be applied for any UDP flows, e.g. for applications that perform re- + +transmissions. The datagram mode 1 requires the definition of a new Context ID (see RFC 9298), which can be done in stage-3. Also, additional details (e.g. the algorithms for packet re-ordering) may also be considered in stage-3. + +- Stream mode: This transport mode is readily supported by the QUIC protocol. It encapsulates UDP packets within QUIC Stream frames and provides reliable transport with sequence numbering and with packet reordering / deduplication. It can be applied for UDP flows where it is known that the application does not perform retransmissions. + +The PCF selects which of the above transport modes shall be applied for a UDP flow (SDF). The selected transport mode is provided to UE and UPF within the ATSSS rules and N4/MAR rules respectively. + +NOTE 1: When the Datagram mode 2 is used with steering modes that use both accesses simultaneously, e.g. the Load-Balancing steering mode, traffic scheduling with per-packet splitting can result to excessive out-of-order delivery. + +NOTE 2: The Stream mode provides strict reliability and in-order delivery with re-transmissions and therefore can lead to melt down phenomena [see ] when reliable traffic (e.g. QUIC) is carried, or counteracts application decisions when UDP is selected to avoid reliability and/or in-order delivery. Therefore, it can be avoided for applications which perform their own reliability mechanisms. + +The Datagram mode 1 and the Stream mode can be used for supporting per-packet splitting, i.e. when the packets of a UDP flow are split across multiple accesses and may be received out-of-order. The Datagram mode 2 is a transport mode which can be applied for applications that can tolerate packet reordering or duplicated packets. The Datagram mode 2 is required (although it does not support re-ordering) because the MPQUIC steering functionality (as any other ATSSS steering functionality) must support all steering modes and not only steering modes that require packet reordering / deduplication. The Datagram mode 2 features benefits compared to ATSSS-LL as it supports congestion control, RTT/PLR measurements without the need to implement the PMF protocol, and it is implemented in high-layers so it can interact with applications. However, it also adds additional overhead and encryption. + +### 6.11.2 High-level Description + +The key principles of the solution are summarized below. + +- After the MA PDU Session establishment, the UE creates one or more multipath QUIC connections with the UPF. Each multipath QUIC connection is associated with a QoS flow, i.e. it carries the traffic mapped to a QoS flow. +- The UE operates as a connect-udp client and the UPF operates as a connect-udp proxy, both defined in RFC 9298 [27]. Therefore, the UE supports an HTTP/3 client and the UPF supports an HTTP/3 proxy, both of them operating over QUIC. +- When the UE wants to transmit the first uplink packet of a new UDP flow, the UE: + - Selects which QUIC connection will be used for the uplink traffic of the UDP flow based on the QoS flow associated with the UDP flow; + - Creates a new bidirectional QUIC stream on the selected QUIC connection; + - Configures the QUIC stream to apply a steering mode (i.e. the steering mode that should be used for the uplink traffic of the UDP flow based on the ATSSS rules); + - Sends to UPF, via the QUIC stream, an extended HTTP CONNECT request [27] containing 'path' information that identifies a destination address and port for the UDP flow (i.e. identifies the remote host where the UDP flow should be forwarded to); and + - Forwards to UPF the uplink packets of the UDP flow using multipath QUIC transport. +- When the UPF wants to transmit a downlink packet of a UDP flow, the UPF: + - Selects which QUIC connection will be used for the downlink traffic of the UDP flow based on the QoS flow associated with the UDP flow (this QUIC connection is the same as the one selected by UE for the UDP flow, assuming the QoS flow in UL and DL directions is the same); + +- Selects a bidirectional QUIC stream on the selected QUIC connection (this QUIC stream is the same as the one created by the UE for the UDP flow); +- Configures the QUIC stream to apply a steering mode (i.e. the steering mode that should be used for the downlink traffic of the UDP flow based on the N4 rules); and +- Forwards to UE the downlink packets of the UDP flow using multipath QUIC transport. + +The following figure illustrates how the traffic of a UDP flow is transferred between the UE and UPF using multipath QUIC transport. In this figure, it is assumed that the uplink traffic and the downlink traffic of the UDP flow are mapped to the same QoS flow (QFI-1). Therefore, both the uplink traffic and the downlink traffic of the UDP flow use the same multipath QUIC connection. + +![Diagram illustrating the use of multipath QUIC transport for a UDP flow between a UE and a UPF. The UE and UPF both have a UDP flow connected to a QFI-1 block. The QFI-1 block is connected to an HTTP/3 QUIC block. The UE's HTTP/3 QUIC block sends traffic on a bidirectional stream using an Uplink Steering mode, while the UPF's HTTP/3 QUIC block sends traffic on the same stream using a Downlink Steering mode. The traffic is transmitted in datagram mode, with each datagram containing a data packet. The diagram shows four datagrams (two blue, two red) being transmitted between the UE and UPF. The UPF is also connected to a Remote host.](aeb2a26a07219661191294dba528067a_img.jpg) + +The diagram shows the architecture for multipath QUIC transport of a UDP flow. On the UE side, a 'UDP flow' is processed through a 'QFI-1' block, which then splits into two parallel paths of 'Data packet' blocks (one red, one blue). These are then processed by an 'HTTP/3 QUIC' block. On the UPF side, a 'Remote host' sends a 'UDP flow' through a 'QFI-1' block, which similarly splits into two parallel paths of 'Data packet' blocks (one red, one blue), processed by an 'HTTP/3 QUIC' block. A central 'Multipath QUIC connection for QFI-1' connects the two 'HTTP/3 QUIC' blocks via a 'Bidirectional Stream'. Arrows indicate that the UE sends traffic on this stream using an 'Uplink Steering mode' and the UPF sends traffic using a 'Downlink Steering mode'. Below the connection, four datagrams are shown in a row: 'Datagram w/ Data packet' (blue), 'Datagram w/ Data packet' (red), 'Datagram w/ Data packet' (blue), and 'Datagram w/ Data packet' (red). + +Diagram illustrating the use of multipath QUIC transport for a UDP flow between a UE and a UPF. The UE and UPF both have a UDP flow connected to a QFI-1 block. The QFI-1 block is connected to an HTTP/3 QUIC block. The UE's HTTP/3 QUIC block sends traffic on a bidirectional stream using an Uplink Steering mode, while the UPF's HTTP/3 QUIC block sends traffic on the same stream using a Downlink Steering mode. The traffic is transmitted in datagram mode, with each datagram containing a data packet. The diagram shows four datagrams (two blue, two red) being transmitted between the UE and UPF. The UPF is also connected to a Remote host. + +**Figure 6.11.2-1: Using multipath QUIC transport for a UDP flow** + +The bidirectional QUIC stream is established by the UE to enable transmission of uplink data packets (blue) and downlink data packets (red) of the UDP flow. The UE configures this stream to send uplink traffic with a steering mode determined based on the ATSSS rules in the UE (uplink steering mode). The UPF configures this stream to send downlink traffic with a steering mode determined based on the N4 rules in the UPF (downlink steering mode). The data packets of the UDP flow shown in Figure 6.11.2-1 are transmitted in datagram mode (mode 1 or mode 2), i.e. they are encapsulated in HTTP datagrams and in QUIC DATAGRAM frames, each one carrying header information (see the Quarter Stream ID defined in RFC 9297 [29]) that associates it with the established bidirectional stream. As discussed below, the data packets of the UDP flow may be transmitted in stream mode (instead of datagram mode), i.e. transmitted directly over the bidirectional stream. In this case, the data packets of the UDP flow are encapsulated in DATAGRAM capsules (see [29]) and in QUIC STREAM frames. + +Figure 6.11.2-2 and Figure 6.11.2-3 illustrate the components of the MPQUIC steering functionality used to support data transmission in the uplink and downlink direction respectively. The MPQUIC steering functionality is composed of three components: + +- 1) QoS flow selection & Steering mode selection: This component in the UE initiates the establishment of one or more QUIC connections, after the establishment of the MA PDU Session and, for each uplink UDP flow, it selects a QoS flow (based on the QoS rules), and a steering mode and a transport mode (based on the ATSSS rules). This component in the UPF selects, for each downlink UDP flow, a QoS flow (based on the N4 rules), a steering mode and a transport mode (based on the N4 rules). + +In the UE, this component is only used in the uplink direction, while, in the UPF, this component is only used in the downlink direction. + +- 2) HTTP/3 layer: Supports the HTTP/3 protocol defined in RFC 9114 [28] and the extensions defined in: + +- RFC 9298 [27] for supporting UDP proxying over HTTP; +- RFC 9297 [29] for supporting HTTP datagrams; and +- RFC 9220 [30] for supporting Extended CONNECT. + +The HTTP/3 layer selects a QUIC connection to be used for each UDP flow and allocates a new QUIC stream on this connection that is associated with the UDP flow. It also configures this QUIC stream to apply a specific steering mode. + +In the UE, the HTTP/3 layer implements an HTTP/3 client, while, in the UPF, it implements an HTTP/3 proxy. + +- 3) QUIC layer: Supports the QUIC protocol as defined in the applicable IETF specifications (RFC 9000 [6], RFC 9001 [7], RFC 9002 [8]) and the extensions defined in: + - RFC 9221 [9] for supporting unreliable datagram transport with QUIC; and + - draft-ietf-quic-multipath [10] for supporting QUIC connections using multiple paths simultaneously. + +![Figure 6.11.2-2: Components of MPQUIC steering functionality used for UL data transmission](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +``` + + graph TD + subgraph UE + App_UE[App] + subgraph MPQUIC_Steering_UE [MPQUIC Steering Functionality] + QoS[QoS flow selection & Steering mode selection] + HTTP3_Client[HTTP/3 client connect-udp] + end + QUIC_UE[QUIC layer] + UDP_IP_UE[UDP/IP] + Non3GPP[Non-3GPP] + ThreeGPP[3GPP] + end + + subgraph UPF + subgraph MPQUIC_Steering_UPF [MPQUIC Steering Functionality] + HTTP3_Proxy[HTTP/3 proxy connect-udp] + QUIC_UPF[QUIC layer] + end + UDP_IP_UPF[UDP/IP] + GTP1[GTP tunnel] + GTP2[GTP tunnel] + Lower_UPF[Lower layers] + end + + subgraph Remote_Host + App_RH[App] + UDP_IP_RH[UDP/IP] + Lower_RH[Lower layers] + end + + GAN[5G-AN] + + App_UE --> QoS + QoS --> HTTP3_Client + HTTP3_Client --> QUIC_UE + QUIC_UE --> UDP_IP_UE + UDP_IP_UE --> Non3GPP + UDP_IP_UE --> ThreeGPP + Non3GPP --> GAN + ThreeGPP --> GAN + GAN --> GTP1 + GAN --> GTP2 + GTP1 --> UDP_IP_UPF + GTP2 --> UDP_IP_UPF + UDP_IP_UPF --> QUIC_UPF + QUIC_UPF --> HTTP3_Proxy + HTTP3_Proxy --> Lower_UPF + Lower_UPF --- Lower_RH + UDP_IP_RH --> App_RH + Lower_RH --> UDP_IP_RH + + QUIC_UE -- Multipath QUIC connection --- QUIC_UPF + QUIC_UE -- Multipath QUIC connection --- QUIC_UPF + App_UE --- App_RH + +``` + +The diagram shows the protocol stack and functional components for MPQUIC steering in the Uplink (UL) direction. + In the **UE**, the application data passes through QoS and steering selection, then an HTTP/3 client, and into the QUIC layer. The QUIC layer establishes multipath connections over UDP/IP, which are routed via 3GPP and Non-3GPP access through the 5G-AN. + In the **UPF**, the traffic is received via GTP tunnels and UDP/IP, processed by the QUIC layer and an HTTP/3 proxy, and then sent to the **Remote Host** via lower layers. The Remote Host receives the data through its own UDP/IP and application layers. Vertical red text labels 'MPQUIC Steering Functionality' indicate the specific functional blocks in the UE and UPF responsible for this feature. + +Figure 6.11.2-2: Components of MPQUIC steering functionality used for UL data transmission + +**Figure 6.11.2-2: Components of MPQUIC steering functionality used for UL data transmission** + +![Figure 6.11.2-3: Components of MPQUIC steering functionality used for DL data transmission. This diagram shows the interaction between a UE, a UPF, and a Remote Host. The UE contains an App, HTTP/3 client (connect-udp), QUIC layer, UDP/IP, and Non-3GPP/3GPP layers. The UPF contains QoS flow selection & Steering mode selection, HTTP/3 proxy (connect-udp), QUIC layer, UDP/IP, GTP tunnel, and Lower layers. The Remote Host contains an App, UDP/IP, and Lower layers. Connections are shown between the UE and UPF via 5G-AN, and between the UPF and Remote Host. Vertical labels 'MPQUIC Steering Functionality' are present on both the UE and UPF sides.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Figure 6.11.2-3: Components of MPQUIC steering functionality used for DL data transmission. This diagram shows the interaction between a UE, a UPF, and a Remote Host. The UE contains an App, HTTP/3 client (connect-udp), QUIC layer, UDP/IP, and Non-3GPP/3GPP layers. The UPF contains QoS flow selection & Steering mode selection, HTTP/3 proxy (connect-udp), QUIC layer, UDP/IP, GTP tunnel, and Lower layers. The Remote Host contains an App, UDP/IP, and Lower layers. Connections are shown between the UE and UPF via 5G-AN, and between the UPF and Remote Host. Vertical labels 'MPQUIC Steering Functionality' are present on both the UE and UPF sides. + +Figure 6.11.2-3: Components of MPQUIC steering functionality used for DL data transmission + +The protocol stack of the solution is depicted in Figure 6.11.2-4 below. + +![Figure 6.11.2-4: UP protocol stack of the solution. This diagram illustrates the protocol stacks across different network elements: UE, 5G-AN, UPF, and Remote Host. The UE stack includes PDU, HTTP3, MP-QUIC (with TLS), UDP, IP, and 5G-AN Protocol Layers. The 5G-AN stack includes Relay, GTP-U, UDP/IP, L2, and L1. The UPF stack includes PDU, HTTP3, TLS, MP-QUIC, UDP, IP, GTP-U, UDP/IP, L2, and L1. The Remote Host stack includes PDU and N6 protocol layers. Vertical dashed lines mark the N3, N9, and N6 interfaces.](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +Figure 6.11.2-4: UP protocol stack of the solution. This diagram illustrates the protocol stacks across different network elements: UE, 5G-AN, UPF, and Remote Host. The UE stack includes PDU, HTTP3, MP-QUIC (with TLS), UDP, IP, and 5G-AN Protocol Layers. The 5G-AN stack includes Relay, GTP-U, UDP/IP, L2, and L1. The UPF stack includes PDU, HTTP3, TLS, MP-QUIC, UDP, IP, GTP-U, UDP/IP, L2, and L1. The Remote Host stack includes PDU and N6 protocol layers. Vertical dashed lines mark the N3, N9, and N6 interfaces. + +Figure 6.11.2-4: UP protocol stack of the solution + +### 6.11.3 Procedures + +Figure 6.11.3-1 below depicts the key steps of the procedure that enables data traffic to be exchanged between the UE and UPF using the MPQUIC steering functionality. For simplicity, the components of the MPQUIC steering functionality at the UPF are not depicted. + +![Sequence diagram showing the procedure for enabling data traffic using the MPQUIC steering functionality between an App, UE, and UPF. The diagram includes steps for MA PDU Session establishment, QUIC connection setup, and subsequent data packet handling with steering mode selection.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The sequence diagram illustrates the interaction between an App, UE, and UPF for MPQUIC steering. The UE contains an 'MPQUIC Steering Functionality' block with 'QoS flow selection & Steering mode selection', 'HTTP/3 Client', and 'QUIC layer' components. The UPF also contains an 'MPQUIC Steering Functionality' block. + +**Sequence of Events:** + +1. An MA PDU Session is established. One or more ATSSS rules use the MPQUIC steering functionality. +2. Determine the number of QUIC connections to establish via the MA PDU Session. +- 3a. Establish QUIC connection #1 and enable multipath support. UE indicates that QUIC connection #1 is associated with a QoS flow #1 (QFI-1). HTTP Settings are negotiated between the HTTP/3 client in UE and the HTTP/3 proxy in UPF. +- 3b. Establish QUIC connection #2 and enable multipath support. UE indicates that QUIC connection #2 is associated with a QoS flow #2 (QFI-2). HTTP Settings are negotiated between the HTTP/3 client in UE and the HTTP/3 proxy in UPF. +4. Data packet #1 (Dst=144.23.1.47:556) is sent from the App. +- 5a. Data packet #1 initiates a new UDP flow. For this UDP flow, select a QoS flow, a steering mode and a transport mode. +- 5b. UDP flow id, Data packet #1, Dst, QFI, steering mode, transport mode are passed to the QUIC layer. +6. Select a QUIC connection for the UDP flow. Allocate a new QUIC stream for the UDP flow. Configure the QUIC stream to apply the steering mode. +6. Allocate new stream (steering\_mode) is sent to the QUIC layer. +6. stream\_id = 40 is returned. +7. Send stream data (stream\_id=40, HEADERS) is sent to the QUIC layer. +7. Select path based on the steering mode of the stream is performed. [Stream 40] HEADERS: :method = CONNECT, :protocol = connect-udp, :scheme = https, :path = /144.23.1.47/556/, :authority = upf.example.org is generated. +9. Send datagram (DATAGRAM (Context ID, [SeqNum], Data packet #1)) is sent to the QUIC layer. +9. Select path based on the steering mode of the stream is performed. 9. DATAGRAM Quarter Stream ID = 10, HTTP Datagram Payload = Context ID, [SeqNum], Data packet #1 is generated. +9. Data packet #1/ UDP/IP (to remote host) is sent from the UPF. +10. Stream data received (stream\_id=40, HEADERS) is received by the QUIC layer. +10. [Stream 40] HEADERS: :status = 200 is received from the UPF. +11. Datagram received (DATAGRAM (Context ID, [SeqNum], Data packet #2)) is received by the QUIC layer. +11. DATAGRAM Quarter Stream ID = 10, HTTP Datagram Payload = Context ID, [SeqNum], Data packet #2 is received from the UPF. +11. Data packet #2/ UDP/IP (from remote host) is received by the QUIC layer. +11. Data packet #2 (Src=144.23.1.47:556) is sent to the App. +12. Data packet #3 (Dst=144.23.1.47:556) is sent from the App. +12. UDP flow id, Data packet #3 is passed to the QUIC layer. +12. Send datagram (DATAGRAM (Context ID, [SeqNum], Data packet #3)) is sent to the QUIC layer. +12. Select path based on the steering mode of the stream is performed. 12. DATAGRAM Quarter Stream ID = 10, HTTP Datagram Payload = Context ID, [SeqNum], Data packet #3 is generated. +12. Data packet #3/ UDP/IP (to remote host) is sent from the UPF. + +Sequence diagram showing the procedure for enabling data traffic using the MPQUIC steering functionality between an App, UE, and UPF. The diagram includes steps for MA PDU Session establishment, QUIC connection setup, and subsequent data packet handling with steering mode selection. + +**Figure 6.11.3-1: Procedure for enabling data traffic using the MPQUIC steering functionality** + +1. The UE establishes a MA PDU Session with the 5G core (5GC) network. During the MA PDU Session establishment: + - In the PDU Establishment Request message, the UE indicates that it supports the MPQUIC steering functionality. This indication can be used by the network (a) to select a UPF that supports the MPQUIC steering functionality and (b) to decide whether the ATSSS/N4 rules for the MA PDU Session may use the MPQUIC steering functionality. + - The UE receives MPQUIC proxy information, i.e. one IP address of UPF, one UDP port number and the proxy type (e.g. "connect-udp"). This information is used by the UE for establishing QUIC connections with the UPF, which is also referred to as "MPQUIC proxy". + - The UE receives one IP address/prefix for the MA PDU Session and two additional IP addresses/prefixes, called "link-specific multipath QUIC" addresses; one associated with 3GPP access and another associated with non-3GPP access. These two addresses can be used by the UE to create two paths in a multipath QUIC connection. + +- The UE receives QoS rules and ATSSS rules to be applied for the MA PDU Session, for QoS enforcement and traffic steering enforcement respectively. Similar rules (N4 rules) are received by UPF. +2. After the MA PDU Session is established and the UE identifies that one or more ATSSS rules require traffic steering using the MPQUIC steering functionality, the UE determines the number of multipath QUIC connections to be established with the UPF (MPQUIC proxy). For example, the UE determines to establish as many multipath QUIC connections, as the number of QoS flows of the MA PDU Session, i.e. one multipath QUIC connection per QoS flow. This way, every QUIC packet can carry only traffic (e.g. one or more UDP payloads) that belongs to the same QoS flow, which facilitates QoS handling in the access layer. +- The QoS rules provided to UE include downlink QoS information and the UE applies the downlink QoS information to establish QUIC connections for the QoS flows used for downlink traffic only. +3. The UE establishes the number of multipath QUIC connection with the UPF (MPQUIC proxy) determined in the previous step. This results into several multipath QUIC connections between the UE and UPF, each one composed of multiple paths, e.g. one path over 3GPP access and another path over non-3GPP access. + +NOTE 1: Data transmitted over a multipath QUIC connection must be encrypted according to RFC 9001 [7]. However, encryption might not be necessary when the multipath QUIC connection is established between UE and UPF, because the underlying 5G security mechanisms can be applied. + +**Editor's note:** Whether and how encryption in the QUIC layer can be omitted is FFS and need to be studied by SA WG3. It could be studied, for example, whether RFC 9150 "TLS 1.3 Authentication and Integrity-Only Cipher Suites" can be applied to omit the data encryption. The impact due to encryption regarding overhead and performance is FFS in SA WG3. + +During a QUIC connection establishment, the UE and UPF negotiate QUIC transport parameters and indicate (a) support of QUIC Datagram frames and (b) support of multipath. They indicate support of QUIC Datagram frames by providing the "max\_datagram\_frame\_size" transport parameter with a non-zero value (see RFC 9221 [9]) and they indicate support of multipath by providing the "enable\_multipath" transport parameter (see draft-ietf-quic-multipath [10]). + +After a QUIC connection establishment, the HTTP/3 client and the HTTP/3 proxy negotiate HTTP settings and indicate support of HTTP Datagrams (see RFC 9297 [29]) and support of Extended CONNECT (see RFC 9220 [30]). + +The QoS flow associated with a QUIC connection is also negotiated between the UE and UPF. This is done by using a new QUIC transport parameter (defined by 3GPP) when the QUIC connection is established. + +NOTE 2: The new QUIC transport parameter needs to be registered in IANA (by stage 3). + +4. An app in the UE generates a new data packet (also referred to as "UDP payload") that should be sent via the MA PDU Session. This data packet initiates a new UDP flow, i.e. a sequence of data packets using the same 5-tuple. In the example shown in Figure 6.11.3-1, the data packet should be sent to IP address 144.23.1.47 and to UDP port 556. +5. For the new UDP flow (and for each new UDP flow): + - The UE selects a QoS flow (QFI) over which the UDP flow should be transmitted. This is selected by using the received QoS rules. + - The UE selects a steering mode that should be applied for the UDP flow. This is selected by using the received ATSSS rules. + - The UE selects a transport mode that should be applied for the UDP flow. This is selected by using the received ATSSS rules, i.e. each ATSSS rule which indicates that the MPQUIC steering functionality should be applied for the matching traffic, indicates also the transport mode that should be applied for this traffic. + +As specified in clause 6.11.1, three transport modes are supported (Datagram mode 1, Datagram mode 2 and Stream mode) and the transport mode that should be applied for a UDP flow is selected by PCF and is provided to UE and UPF within the ATSSS rules and the N4/MAR rules respectively. + +- The Datagram mode 2 is already specified in RFC 9298 [27] and does not require further specification in 3GPP. In this mode, the HTTP/3 proxy/client encapsulates each UDP data within an HTTP Datagram that contains a Context Id=0. Then, the HTTP Datagram is sent to the QUIC layer for multipath transmission. No sequence numbers are included in the HTTP Datagrams (see [27]). + +- The Datagram mode 1 is similar to the Datagram mode 2 but it also provides a sequence number for each UDP data. In this mode, the HTTP/3 proxy/client encapsulates each UDP data within an HTTP Datagram that contains a Context Id and a sequence number. Then, the HTTP Datagram is sent to the QUIC layer for multipath transmission. The value of this Context Id will be defined in stage-3 and indicates that a sequence number is also included. The sequence numbers are used by the receiving endpoint to re-order the UDP data and remove duplicated UDP data. Details of how packet reordering is supported (including the mechanisms for reordering) can be specified in stage-3. + +The Datagram mode 1 and Datagram mode 2 use two different (and pre-defined in 3GPP) Context IDs, e.g. Context ID=0 and Context ID=1, respectively. With Context ID=0, the HTTP Datagram Payload contains the UDP data, whereas, with Context ID=1, the HTTP Datagram Payload contains a sequence number followed by the UDP data. The format of QUIC DATAGRAMs used in both datagram modes is shown below. As specified in clause 6.11.6, the Datagram mode 1 supports reordering in the HTTP/3 layer (as described above). + +The following table shows how UDP data is encapsulated in a QUIC datagram using the Datagram mode 1 and the Datagram mode 2. It is assumed that the value of Context Id used in Datagram mode 1 is set to 1. + +| | | +|-----------------|--| +| Datagram mode 1 | | +| Datagram mode 2 | | + +6. The UE selects a multipath QUIC connection to be used for the new UDP flow (e.g. based on the selected QFI) and the UE allocates a new bidirectional QUIC stream (e.g. stream 40) in this multipath QUIC connection. This new stream is associated with the new UDP flow. The UE configures the new stream to transmit uplink data traffic using the selected steering mode for this UDP flow. + +- 7-9. The UE sends the data packet using the allocated new stream on the selected QUIC connection. + +When the datagram transport mode is selected (either mode 1 or mode 2), the UE encapsulates the data packet within an HTTP DATAGRAM frame [27], which is transferred inside a QUIC DATAGRAM frame [9]. The header of the HTTP DATAGRAM indicates that this datagram is associated with stream 40 (i.e. the Quarter Stream ID is set to 10). + +When the stream transport mode is selected, the UE encapsulates the data packet within an HTTP DATAGRAM frame [29] that is further encapsulated in a DATAGRAM capsule (see clause 3.5 in [29]), which is transferred inside a QUIC STREAM frame [6]. + +In the example procedure shown in Figure 6.11.3-1, the datagram transport mode (either mode 1 or mode 2) is selected. The UE sends an HTTP CONNECT request via the allocated stream 40, which indicates to UPF (MPQUIC proxy) that the UE wishes to create an HTTP tunnel to send UDP traffic to remote host 144.23.1.47 and port 556. The :protocol pseudo-header is set to "connect-udp" (as defined in [27]) to indicate that the protocol to be spoken on the tunnel is the capsule protocol defined in RFC 9297 [29]. Finally, the UE sends a QUIC DATAGRAM frame to UPF that encapsulates the data packet, which is forwarded to the remote host (144.23.1.47:556). Note that the QUIC DATAGRAM frame may contain a sequence number (as defined in step 5). + +If the stream transport mode were selected, the HTTP DATA frame in step 8 would contain a DATAGRAM capsule, which would include the data packet in the HTTP Datagram Payload field (see [29]). + +10. The UPF (MPQUIC proxy) responds with an HTTP 200 status, indicating that the request to proxy data packets to a remote host 144.23.1.47 and destination port 556 is accepted. + +11. When a data packet is received by UPF (MPQUIC proxy) from the remote host (data packet #2), this data packet is transferred to the UE using the established context information for the UDP flow, i.e. using the selected multipath QUIC connection, the selected stream on this connection, the selected steering mode, and the selected transport mode. Such context information is stored in the UPF and in the UE and is applied for all the data packets of the UDP flow. + +12. Similarly, when another data packet is generated by the UE app (data packet #3), this data packet is transferred to UPF (MPQUIC proxy) using again all the stored context information for the UDP flow. + +NOTE 2: The context information for a UDP flow in the UE and in the UPF is created when the first data packet (i.e. Data packet #1) of this UDP flow is transferred. All subsequent data packets of the same UDP flow are transferred between the UE and the UPF using this context information. + +When the UE identifies that the context information for a UDP flow is no longer needed (e.g. the app closes the associated UDP socket), the UE deletes this context information and releases the associated QUIC stream, which cause the UPF to delete the context information stored in UPF. + +The following figure 6.11.3-2 illustrates an example of how the uplink traffic of various UDP flows is transferred from the UE to UPF using QUIC multipath transport, and how the UPF relays this traffic to a final destination (remote host). Note that, for each UDP flow, there is an associated QUIC connection and an associated bidirectional QUIC stream, which is configured to apply a specific steering mode for the uplink traffic. For example, the red UDP flow is associated with the multipath QUIC connection #1 and with the red Stream Y, which is configured to apply the Smallest-delay steering mode in the uplink direction. + +All UDP flows shown in this figure, except the blue UDP flow, are transferred with the datagram transport mode (mode 1 or mode 2), so their data packets are transferred inside QUIC DATAGRAM frames. The blue UDP flow is transferred with the stream transport mode, so its data packets are transferred inside QUIC STREAM frames. + +The downlink traffic of UDP flows is transferred between the UE and UPF in a similar way. + +![Figure 6.11.3-2: Example of user-plane operation using the MPQUIC steering functionality (UL direction). The diagram shows data flows from various apps in the UE being processed through QoS flow selection and steering mode selection. It details two multipath QUIC connections (connection #1 and connection #2) with their respective streams (X, Y, Z and A, B) and steering modes (Active-Standby, Smallest delay, Load balancing). It also shows the encapsulation of data packets into QUIC frames (Stream frames or Datagram frames) and their transmission to the UPF, which then proxies them to various Remote Hosts. Headers for Stream frames and Datagram frames are shown, including QUIC, UDP, and IP headers.](85b53faf49a839f512153285c78fbbdb_img.jpg) + +The diagram illustrates the uplink traffic flow from the UE to the UPF and then to Remote Hosts. In the UE, data flows from different apps are processed through 'QoS Flow selection & Steering Mode selection'. This leads to two 'HTTP/3 client' instances. The first client uses 'QUIC (Multipath connection #1)' and contains three streams: Stream X (Steering\_mode = Active-Standby), Stream Y (Steering\_mode = Smallest delay), and Stream Z (Steering\_mode = Load balancing). Stream Y is shown as a 'Stream frame w/ data packet', while the others are 'Datagram frame w/ Data packet'. The second client uses 'QUIC (Multipath connection #2)' with Stream A (Steering\_mode = Smallest delay) and Stream B (Steering\_mode = Active-Standby), both using 'Datagram frame w/ Data packet'. Headers for 'Stream Frame' and 'Datagram Frame' are shown, including 'Data packet', 'QUIC hdr', 'UDP hdr', and 'IP hdr'. The UPF contains 'HTTP/3 proxy' units that receive these frames and forward them to 'Remote Host' units. Headers for the traffic between the UPF and Remote Hosts are also shown, including 'Data packet', 'UDP', and 'IP'. Text labels indicate the UE's link-specific multipath QUIC address, UPF's address, and port information. + +Figure 6.11.3-2: Example of user-plane operation using the MPQUIC steering functionality (UL direction). The diagram shows data flows from various apps in the UE being processed through QoS flow selection and steering mode selection. It details two multipath QUIC connections (connection #1 and connection #2) with their respective streams (X, Y, Z and A, B) and steering modes (Active-Standby, Smallest delay, Load balancing). It also shows the encapsulation of data packets into QUIC frames (Stream frames or Datagram frames) and their transmission to the UPF, which then proxies them to various Remote Hosts. Headers for Stream frames and Datagram frames are shown, including QUIC, UDP, and IP headers. + +Figure 6.11.3-2: Example of user-plane operation using the MPQUIC steering functionality (UL direction) + +### 6.11.4 User-plane overhead + +As shown in the figure 6.11.3-2 above and in the table below, the user-plane overhead of the MPQUIC steering functionality is given by the applied (a) proxying mechanism (instead of IP-in-IP tunneling), (b) the HTTP/3 encapsulation and (c) the QUIC protocol which can multiplex payload packets into a single QUIC packet as explained later in this clause. This proxying mechanism "allows an HTTP client to create a tunnel for UDP communications through an HTTP server that acts as a proxy" (see RFC 9298 [27]). + +The table below provides an estimate of the size of the additional headers for the various transport modes. Note that the exact estimation of the size of the additional headers depends on the QUIC implementation (e.g. how the + +implementation selects the size of the stream identity) and it is difficult to be calculated. Therefore, the table below provides approximate numbers based on some assumptions. + +**Table 6.11.4-1** + +| Transport mode | Size of additional headers [bytes] | +|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Datagram mode 1 | Size of additional headers = IP header (20) + UDP header (8) + QUIC short header (5) + QUIC Datagram header (6) = 39 bytes
The QUIC short header size depends on the length of the Destination Connection ID (0-160 bits) and the length of the Packet Number (8-32 bits). It is assumed that 16 bits are enough for each field.
The QUIC Datagram header contains:
Type: 1 byte
Length: Variable-length integer specifying the length of the Datagram Data field in bytes. It is assumed 2 bytes are enough.
Quarter Stream Id: Variable-length integer. It is assumed that 2 bytes are enough to support 65536 active streams on an MPQUIC connection.
Context Id: 1 byte
Sequence number: 2 bytes (assumed to be enough) | +| Datagram mode 2 | The same as Datagram mode 1 but without the sequence number (i.e. minus 2 bytes). | +| Stream mode | Size of additional headers = IP header (20) + UDP header (8) + QUIC short header (5) + QUIC Stream header (3) + Datagram Capsule (5) = 41 bytes
The QUIC Stream header contains:
Type: 1 byte
Stream Id: Assume 2 bytes are enough to contain all stream ids in each MPQUIC connection
Offset: Optional, variable length
Length: Optional, variable length
The Datagram Capsule contains:
Type: 1 byte
Length: Variable-length integer. It is assumed that 2 bytes are enough.
Quarter Stream Id: Variable-length integer. It is assumed that 2 bytes are enough to support 65536 active streams on an MPQUIC connection. | + +The figure 6.11.4-1 below shows that, when two app payloads are provided to the MPQUIC steering functionality they can be multiplexed in the same QUIC packet (this is a feature supported by QUIC), thus, reducing the user-plane overhead. In addition, a single UDP datagram can multiplex multiple QUIC packets, which can further reduce the overhead. + +NOTE: As a consequence of RFC9000 [6] the precondition for possible multiplexing of payload packets is that those payload packets fit completely inside a single QUIC packet, which is limited by the maximum MTU size. + +An overhead of the MPQUIC steering functionality, which is not evident from the figure below, is the HTTP CONNECT request plus the 200 OK response, sent at the beginning of every UDP flow (see steps 7 and 10 in Figure 6.11.3-1). + +![Diagram illustrating the multiplexing of QUIC datagram frames in one QUIC packet for MPQUIC steering functionality in the UL direction. The diagram shows data from Apps (App payload-1 and App payload-2) being processed through HTTP/3 and MPQUIC steering functionality to create two HTTP datagrams. These are then encapsulated into a single QUIC packet containing two Datagram Frm blocks (one for each payload) and a QUIC header. This packet is then processed through UDP and IP layers and finally split into 3GPP and Non-3GPP paths. A summary at the bottom shows the combined structure: Datagram Frm (App payload-2), Datagram Frm (App payload-1), QUIC, UDP, IP, and 3GPP/non-3GPP.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +Diagram illustrating the multiplexing of QUIC datagram frames in one QUIC packet for MPQUIC steering functionality in the UL direction. The diagram shows data from Apps (App payload-1 and App payload-2) being processed through HTTP/3 and MPQUIC steering functionality to create two HTTP datagrams. These are then encapsulated into a single QUIC packet containing two Datagram Frm blocks (one for each payload) and a QUIC header. This packet is then processed through UDP and IP layers and finally split into 3GPP and Non-3GPP paths. A summary at the bottom shows the combined structure: Datagram Frm (App payload-2), Datagram Frm (App payload-1), QUIC, UDP, IP, and 3GPP/non-3GPP. + +**Figure 6.11.4-1: Example of multiplexing QUIC datagram frames in one QUIC packet to reduce the user-plane overhead when using the MPQUIC steering functionality (UL direction)** + +### 6.11.5 Co-existence with MPTCP and ATSSS-LL + +The MPQUIC steering functionality can co-exist with the MPTCP and the ATSSS-LL steering functionalities and can complement the capabilities supported by these functionalities. As shown in the following figure, the MPQUIC steering functionality and the MPTCP steering functionality coexist and complement each other by applying the same principles for different types of flows (UDP/IP traffic flows and TCP/IP traffic flows respectively): + +- They both support a proxy functionality in the UPF. During the MA PDU Session establishment, the UE receives proxy information for MPQUIC (IP address, UDP port and type) and, in a similar way, it receives proxy information for MPTCP (IP address, TCP port and type). +- They are both high-layer functionalities that can interact with apps via multipath-aware APIs. +- The MPTCP establishes a new MP-TCP connection for every TCP data flow, while the MPQUIC establishes a new QUIC stream for every UDP data flow. +- The MPTCP applies a steering mode for every MP-TCP connection, while the MPQUIC applies a steering mode for every QUIC stream. + +Since the UE indicates if it supports the MPQUIC steering functionality (in the PDU Establishment Request message), the network may configure the UE/UPF to apply MPQUIC for UDP data flows, only if it is supported by the UE. Otherwise, the network may configure the UE/UPF to apply ATSSS-LL for UDP data flows. + +In case of an MA PDU Session with Ethernet type, only the ATSSS-LL is applied. + +![Diagram illustrating the co-existence of steering functionalities in UE and UPF. The UE contains Apps, Enhanced sockets API, MPQUIC Steering functionality, MPTCP Steering functionality, and ATSSS-LL Steering functionality. The UPF contains MPQUIC proxy (connect-udp), MPQUIC Steering functionality, MPTCP proxy (transport converter), MPTCP Steering functionality, and ATSSS-LL Steering functionality. Arrows show traffic paths: Apps to MPQUIC Steering for UDP/IP traffic; Enhanced sockets API to MPQUIC Steering for TCP/IP traffic; MPTCP Steering functionality to MPQUIC Steering for other IP traffic (ESP, GRE, etc.); ATSSS-LL Steering functionality to MPQUIC Steering for other IP traffic (ESP, GRE, etc.).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The diagram shows the internal architecture of a User Equipment (UE) and a User Plane Function (UPF) regarding traffic steering. In the UE, 'Apps' connect to 'Enhanced sockets API', which in turn connects to 'MPQUIC Steering functionality'. 'MPTCP Steering functionality' and 'ATSSS-LL Steering functionality' are also present. In the UPF, 'MPQUIC proxy (connect-udp)' connects to 'MPQUIC Steering functionality', which connects to 'MPTCP proxy (transport converter)' and 'MPTCP Steering functionality'. 'ATSSS-LL Steering functionality' is also present. Three main traffic paths are shown: + 1. 'Multipath transport for UDP/IP traffic' from UE Apps to UPF MPQUIC proxy. + 2. 'Multipath transport for TCP/IP traffic' from UE Enhanced sockets API to UPF MPQUIC proxy. + 3. 'Multipath transport for other IP traffic: ESP, GRE, etc. (and for Ethernet traffic)' from UE ATSSS-LL to UPF ATSSS-LL. + +Diagram illustrating the co-existence of steering functionalities in UE and UPF. The UE contains Apps, Enhanced sockets API, MPQUIC Steering functionality, MPTCP Steering functionality, and ATSSS-LL Steering functionality. The UPF contains MPQUIC proxy (connect-udp), MPQUIC Steering functionality, MPTCP proxy (transport converter), MPTCP Steering functionality, and ATSSS-LL Steering functionality. Arrows show traffic paths: Apps to MPQUIC Steering for UDP/IP traffic; Enhanced sockets API to MPQUIC Steering for TCP/IP traffic; MPTCP Steering functionality to MPQUIC Steering for other IP traffic (ESP, GRE, etc.); ATSSS-LL Steering functionality to MPQUIC Steering for other IP traffic (ESP, GRE, etc.). + +Figure 6.11.5-1: Co-existence of steering functionalities + +### 6.11.6 Handling of out-of-order delivery + +In some scenarios, e.g. when a UDP flow is simultaneously split across two accesses using the MPQUIC steering functionality, a percentage of received packets can be out-of-order. These packets need to be reassembled in the correct order (i.e. to be re-ordered) before they are consumed. This out-of-order delivery arises when: + +- The MPQUIC steering functionality applies a steering mode that simultaneously uses both accesses, such as the Load-Balancing steering mode, for an UDP flow and (a) the transmitted packets are scheduled across the two accesses on a per-packet decision (aka "per-packet splitting") and (b) there is a difference of RTTs across the two accesses. + +In other scenarios, e.g. when the MPQUIC steering functionality applies e.g. an Active/Standby steering mode, the out-of-order delivery caused by multipath transmission can be limited because, most of the time, the traffic of the UDP flow is transmitted on one access only. + +To enable scenarios where per-packet splitting is required and out-of-order delivery cannot be avoided otherwise, the MPQUIC steering functionality is able to: + +- Apply packet re-ordering by using the existing mechanisms provided by QUIC for stream transport, when the PCF indicates that the stream mode should be applied (head-of-line blocking can happen when delay due to re-transmissions is too high). +- Apply packet re-ordering by using the mechanisms provided by Datagram mode 1, when the PCF indicates that the Datagram mode 1 should be applied. As mentioned before, the Datagram mode 1 adds sequence numbers to the HTTP Datagrams that carry the UDP data packets (see details in clause 6.11.3, step 5) and requires the definition of a new Context Id. This Context Id, as well as the following aspects of Datagram mode 1 will be considered in stage-3. + - How to ensure re-ordering on the receiver side is implemented and activated, when needed. + - How the same reordering in both downlink and uplink can be provided. + - Which sequencing and reordering schemes can be supported and whether such schemes will be specified or will left to UE/UPF implementation. + +### 6.11.7 Handling of duplicated packets + +In some scenarios, the multipath transmission of a UDP flow using the MPQUIC steering functionality can lead to reception of double copies of the same packet. The duplicated copies of packets need to be discarded (i.e. to be deduplicated) before they are consumed. This duplicated delivery issue can arise when: + +- The MPQUIC steering functionality applies the redundant steering mode (RSM) for an UDP flow. + +The MPQUIC steering functionality can identify and remove the duplicated packets by using a transport mode that supports packet reordering / deduplication, such as the Datagram mode 1 or the Stream mode. + +### 6.11.8 Impacts on Existing Nodes and Functionality + +The 5GC network functions shall be able to support the following functionality in addition to the ATSSS functionality defined in Rel-17. + +#### AMF + +- No additional functionality is needed. It is assumed that when 5GC supports ATSSS / Rel-18, then all ATSSS-capable SMFs in 5GC are able to support MPQUIC. + +#### SMF + +- Shall be able to determine whether the UE supports the MPQUIC steering functionality and to indicate this to PCF. +- Shall be able to create ATSSS/N4 rules that apply the MPQUIC steering functionality, based on the PCC rules received from PCF. +- Shall be able to select a UPF that supports the MPQUIC steering functionality. + +#### PCF + +- If it is informed from SMF that the UE supports the MPQUIC steering functionality, then it shall be able to determine which UDP flows should be steered with the MPQUIC steering functionality. For each UDP flow, it shall be able to indicate a steering mode and a transport mode. + +#### UPF + +- Shall be able to support the MPQUIC steering functionality for steering the UDP flows indicated in the received N4 rules. For each UDP flow, it should apply the transport mode indicated in the received N4 rules. + +#### UE + +- Shall be able to indicate in the PDU Session Establishment Request that it supports the MPQUIC steering functionality. +- Shall be able to support the MPQUIC steering functionality for steering the UDP flows indicated by the received ATSSS rules. For each UDP flow, it should apply the transport mode indicated in the received ATSSS rules. + +The MPQUIC steering functionality is largely based on existing IETF specifications (see clause 6.11.2) but does not require any changes on these specifications. + +- A new QUIC transport parameter must be defined by 3GPP and registered with IANA. This transport parameter associates a QUIC connection with a QoS flow. + +## 6.12 Solution #2.3: MPQUIC steering functionality using IP proxying over HTTP + +### 6.12.1 Introduction + +The solution in clause 6.12 specifies a new ATSSS steering functionality, called Multipath QUIC-IP (MPQUIC-IP) steering functionality, and addresses the objective of KI#2 for a QUIC-based steering functionality. It borrows several aspects from solutions studied in TR 23.700-93 [5], mainly from Solution #6 "MPQUIC-LL Steering Functionality" and from Solution #14 "Proxy based solution using MP-QUIC". + +The solution is primarily based on the draft-ietf-masque-connect-ip [31], which specifies how IP traffic can be transferred between a client (UE) and a proxy (UPF) using the HTTP/3 protocol [28]. The HTTP/3 protocol operates on top of the QUIC protocol [6], which supports simultaneous communication over multiple paths, as defined in draft-ietf-quic-multipath [10]. + +The solution considers the following modes for transmitting an IP flow (see further details in clause 6.12.3, step 5): + +- Datagram mode 1: This mode encapsulates the IP packets into QUIC DATAGRAM frames. It provides unreliable transport and adds sequence numbers to the transmitted IP packets, so that the received IP packets can be re-ordered, and the duplicated IP packets can be removed. +- Datagram mode 2: This mode encapsulates the IP packets into QUIC DATAGRAM frames. It provides unreliable transport but does not add sequence numbers to the transmitted IP packets. Therefore, it may result in data delivery with out-of-order packets and/or with duplicated packets. +- Stream mode: This mode encapsulates the IP packets into QUIC STREAM frames. It provides reliable transport (based on the existing mechanisms supported by the QUIC protocol) and supports data delivery without out-of-order packets and without duplicated packets. + +NOTE: Stream mode provides strict reliability and in-order delivery with re-transmissions and therefore leads to melt down phenomena [see ] when reliable (e.g. QUIC) is carried, or counteracts application decisions when UDP is selected to avoid reliability and/or in-order delivery. + +The Datagram mode 1 and the Stream mode are particularly useful for supporting per-packet splitting, i.e. when the packets of an IP flow are split across multiple accesses and may be received out-of-order. The Datagram mode 2 is a simple transport mode which can be applied for applications that can tolerate packet reordering or duplicated packets. The Datagram mode 2 features benefits compared to ATSSS-LL, e.g. (a) it supports congestion control, (b) it supports RTT/PLR measurements without the need to implement the PMF protocol, etc. + +As clarified in clause 6.12.6, the MPQUIC-IP solution defines the mechanisms needed for packet re-ordering (Datagram mode 1 and Stream mode) and the conclusions should indicate which of those mechanisms should be defined in the normative specs. + +### 6.12.2 High-level Description + +The key principles of the solution are summarized below. + +- After the MA PDU Session establishment, the UE creates one or more multipath QUIC connections with the UPF. Each multipath QUIC connection is associated with a QoS flow, i.e. it carries the traffic mapped to a QoS flow. +- The UE operates as a connect-ip client and the UPF operates as a connect-ip proxy, both defined in draft-ietf-masque-connect-ip [31]. Therefore, the UE supports an HTTP/3 client and the UPF supports an HTTP/3 proxy, both of them operating over QUIC. +- On each of the established QUIC connections, the UE sends an extended HTTP CONNECT request to UPF (as defined in [31]) indicating that IP proxying over HTTP is needed. +- When the UE wants to transmit an uplink packet of an IP flow, the UE: + - Selects which QUIC connection will be used for the uplink traffic of the IP flow based on the QoS flow associated with the IP flow; + - Creates a new bidirectional QUIC stream on the selected QUIC connection; + - Configures the QUIC stream to apply a steering mode (i.e. the steering mode that should be used for the uplink traffic of the IP flow based on the ATSSS rules); and + - Forwards to UPF the uplink packets of the IP flow using multipath QUIC transport. +- When the UPF wants to transmit a downlink packet of an IP flow, the UPF: + - Selects which QUIC connection will be used for the downlink traffic of the IP flow (this QUIC connection is the same as the one selected by UE for the IP flow, assuming the QoS flow in UL and DL directions is the same); + - Selects a bidirectional QUIC stream on the selected QUIC connection (this QUIC stream is the same as the one created by the UE for the IP flow); + - Configures the QUIC stream to apply a steering mode (i.e. the steering mode that should be used for the downlink traffic of the IP flow based on the N4 rules); and + +- Forwards to UE the downlink packets of the IP flow using multipath QUIC transport. + +The following figure illustrates how the traffic of an IP flow is transferred between the UE and UPF using multipath QUIC transport [9]. In this figure, it is assumed that the uplink traffic and the downlink traffic of the IP flow are mapped to the same QoS flow (QFI-1). Therefore, both the uplink traffic and the downlink traffic of the IP flow use the same multipath QUIC connection. + +![Diagram illustrating the use of multipath QUIC transport for an IP flow between a UE and a UPF. The UE and UPF both have an IP flow connected to a QFI-1 block. The QFI-1 block is connected to a QUIC block. The QUIC blocks are connected by a bidirectional stream labeled 'Multipath QUIC connection for QFI-1'. The UE side shows uplink traffic (blue) being sent from the QUIC block to the QFI-1 block, and downlink traffic (red) being sent from the QFI-1 block to the QUIC block. The UPF side shows uplink traffic (blue) being sent from the QUIC block to the QFI-1 block, and downlink traffic (red) being sent from the QFI-1 block to the QUIC block. The diagram also shows the steering modes: 'UE sends traffic on this stream using an Uplink Steering mode' and 'UPF sends traffic on this stream using a Downlink Steering mode'. The data packets are shown as 'Datagram w/ IP packet'.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +Diagram illustrating the use of multipath QUIC transport for an IP flow between a UE and a UPF. The UE and UPF both have an IP flow connected to a QFI-1 block. The QFI-1 block is connected to a QUIC block. The QUIC blocks are connected by a bidirectional stream labeled 'Multipath QUIC connection for QFI-1'. The UE side shows uplink traffic (blue) being sent from the QUIC block to the QFI-1 block, and downlink traffic (red) being sent from the QFI-1 block to the QUIC block. The UPF side shows uplink traffic (blue) being sent from the QUIC block to the QFI-1 block, and downlink traffic (red) being sent from the QFI-1 block to the QUIC block. The diagram also shows the steering modes: 'UE sends traffic on this stream using an Uplink Steering mode' and 'UPF sends traffic on this stream using a Downlink Steering mode'. The data packets are shown as 'Datagram w/ IP packet'. + +**Figure 6.12.2-1: Using multipath QUIC transport for a IP flow** + +The bidirectional QUIC stream is established by the UE to enable transmission of uplink IP packets (blue) and downlink IP packets (red) of the IP flow. The UE configures this stream to send uplink traffic with a steering mode determined based on the ATSSS rules in the UE (uplink steering mode). The UPF configures this stream to send downlink traffic with a steering mode determined based on the N4 rules in the UPF (downlink steering mode). The data packets of the IP flow shown in Fig. 6.12.2-1 are transmitted in datagram mode (mode 1 or mode 2), i.e. they are encapsulated in HTTP datagrams and QUIC DATAGRAM frames, each one carrying header information (see the Quarter Stream ID defined in draft-ietf-masque-h3-datagram [29]) that associates it with the established bidirectional stream. As discussed below, the IP packets of the IP flow may be transmitted in stream mode (instead of datagram mode), i.e. transmitted directly over the bidirectional stream. In this case, the IP packets of the IP flow are encapsulated in DATAGRAM capsules (see [29]) and QUIC STREAM frames. + +Figure 6.12.2-2 and Figure 6.12.2-3 illustrate the components of the MPQUIC-IP steering functionality used to support data transmission in the uplink and downlink direction respectively. The MPQUIC-IP steering functionality is composed of three components: + +- 1) QoS flow selection & Steering mode selection: This component in the UE initiates the establishment of one or more QUIC connections, after the establishment of the MA PDU Session and, for each uplink IP flow, it selects a QoS flow (based on the QoS rules), a steering mode (based on the ATSSS rules) and a transport mode (see further details below). This component in the UPF selects, for each downlink IP flow, a QoS flow (based on the N4 rules), a steering mode (based on the N4 rules) and a transport mode (see further details below) + +In the UE, this component is only used in the uplink direction, while, in the UPF, this component is only used in the downlink direction. + +- 2) HTTP/3 layer: Supports the HTTP/3 protocol defined in draft-ietf-quic-http [28] and the extensions defined in: + - draft-ietf-masque-connect-ip [31] for supporting IP proxying over HTTP; and + - draft-ietf-masque-h3-datagram [29] for supporting HTTP datagrams. + +The HTTP/3 layer selects a QUIC connection to be used for each IP flow and allocates a new QUIC stream on this connection that is associated with the IP flow. It also configures this QUIC stream to apply a specific steering mode (further details are provided below). + +In the UE, the HTTP/3 layer implements an HTTP/3 client, while, in the UPF, it implements an HTTP/3 proxy. + +3) QUIC layer: Supports the QUIC protocol as defined in the applicable IETF specifications (RFC 9000 [6], RFC 9001 [7], RFC 9002 [8]) and the extensions defined in: + +- RFC 9221 [9] for supporting unreliable datagram transport with QUIC; and +- draft-ietf-quic-multipath [10] for supporting QUIC connections using multiple paths simultaneously. + +![Diagram illustrating the components of MPQUIC-IP steering functionality used for UL data transmission. The diagram shows three main entities: UE, UPF, and Remote Host. The UE contains an IP layer, a QoS flow selection & Steering mode selection block (part of MPQUIC-IP Steering Functionality), an HTTP/3 client, a QUIC layer, and a UDP/IP layer. The UDP/IP layer connects to Non-3GPP and 3GPP paths, which lead to a 5G-AN. The 5G-AN connects to the UPF. The UPF contains an HTTP/3 proxy, a QUIC layer, a UDP/IP layer (with GTP tunnels), and an IP layer (with Lower layers). The QUIC layer in the UPF is part of the MPQUIC-IP Steering Functionality. The Remote Host contains an IP layer and Lower layers. The diagram shows two 'Multipath QUIC connection' lines between the UE's QUIC layer and the UPF's QUIC layer. Arrows indicate the flow of data from the UE's IP layer, through the QoS selection, HTTP/3 client, and QUIC layer, then through the 5G-AN to the UPF's QUIC layer, then through the HTTP/3 proxy to the UPF's IP layer, and finally to the Remote Host's IP layer.](dd6c544ab685b25dd17f59456efcfbfc_img.jpg) + +Diagram illustrating the components of MPQUIC-IP steering functionality used for UL data transmission. The diagram shows three main entities: UE, UPF, and Remote Host. The UE contains an IP layer, a QoS flow selection & Steering mode selection block (part of MPQUIC-IP Steering Functionality), an HTTP/3 client, a QUIC layer, and a UDP/IP layer. The UDP/IP layer connects to Non-3GPP and 3GPP paths, which lead to a 5G-AN. The 5G-AN connects to the UPF. The UPF contains an HTTP/3 proxy, a QUIC layer, a UDP/IP layer (with GTP tunnels), and an IP layer (with Lower layers). The QUIC layer in the UPF is part of the MPQUIC-IP Steering Functionality. The Remote Host contains an IP layer and Lower layers. The diagram shows two 'Multipath QUIC connection' lines between the UE's QUIC layer and the UPF's QUIC layer. Arrows indicate the flow of data from the UE's IP layer, through the QoS selection, HTTP/3 client, and QUIC layer, then through the 5G-AN to the UPF's QUIC layer, then through the HTTP/3 proxy to the UPF's IP layer, and finally to the Remote Host's IP layer. + +Figure 6.12.2-2: Components of MPQUIC-IP steering functionality used for UL data transmission + +![Figure 6.12.2-3: Components of MPQUIC-IP steering functionality used for DL data transmission. The diagram shows three main entities: UE, UPF, and Remote Host. The UE contains an IP layer, an HTTP/3 client, a QUIC layer, and a UDP/IP layer (split into Non-3GPP and 3GPP). The UPF contains a QoS flow selection & Steering mode selection block, an HTTP/3 proxy, a QUIC layer, and a UDP/IP layer (split into two GTP tunnels and IP/Lower layers). The Remote Host contains an IP layer and Lower layers. Connections include 'Multipath QUIC connection' between UE and UPF, and a direct line between UE IP layer and Remote Host IP layer. Vertical labels 'MPQUIC-IP Steering Functionality' are present in both UE and UPF.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +Figure 6.12.2-3: Components of MPQUIC-IP steering functionality used for DL data transmission. The diagram shows three main entities: UE, UPF, and Remote Host. The UE contains an IP layer, an HTTP/3 client, a QUIC layer, and a UDP/IP layer (split into Non-3GPP and 3GPP). The UPF contains a QoS flow selection & Steering mode selection block, an HTTP/3 proxy, a QUIC layer, and a UDP/IP layer (split into two GTP tunnels and IP/Lower layers). The Remote Host contains an IP layer and Lower layers. Connections include 'Multipath QUIC connection' between UE and UPF, and a direct line between UE IP layer and Remote Host IP layer. Vertical labels 'MPQUIC-IP Steering Functionality' are present in both UE and UPF. + +Figure 6.12.2-3: Components of MPQUIC-IP steering functionality used for DL data transmission + +The protocol stack of the solution is depicted in Figure 6.12.2-4 below. + +![Figure 6.12.2-4: UP protocol stack of the solution. This is a detailed protocol stack diagram showing layers from PDU down to L1 across four entities: UE, 5G-AN, UPF, and Remote Host. The UE stack includes PDU, UDP, IP, HTTP3 (connect-ip), MP-QUIC (with TLS), UDP, IP, and 5G-AN Protocol Layers. The 5G-AN stack includes a Relay section with GTP-U, UDP/IP, L2, and L1 layers. The UPF stack includes a Relay section with GTP-U, UDP/IP, L2, and L1 layers, followed by N6 protocol layers: IP, HTTP3 (connect-ip), TLS, MP-QUIC, UDP, IP, GTP-U, UDP/IP, L2, and L1. The Remote Host stack includes PDU, UDP, IP, and N6 protocol layers. Interface markers N3, N9, and N6 are shown at the bottom.](677bcb564410628b8b966ad87b394888_img.jpg) + +Figure 6.12.2-4: UP protocol stack of the solution. This is a detailed protocol stack diagram showing layers from PDU down to L1 across four entities: UE, 5G-AN, UPF, and Remote Host. The UE stack includes PDU, UDP, IP, HTTP3 (connect-ip), MP-QUIC (with TLS), UDP, IP, and 5G-AN Protocol Layers. The 5G-AN stack includes a Relay section with GTP-U, UDP/IP, L2, and L1 layers. The UPF stack includes a Relay section with GTP-U, UDP/IP, L2, and L1 layers, followed by N6 protocol layers: IP, HTTP3 (connect-ip), TLS, MP-QUIC, UDP, IP, GTP-U, UDP/IP, L2, and L1. The Remote Host stack includes PDU, UDP, IP, and N6 protocol layers. Interface markers N3, N9, and N6 are shown at the bottom. + +Figure 6.12.2-4: UP protocol stack of the solution + +### 6.12.3 Procedures + +Figure 6.12.3-1 below depicts the key steps of the procedure that enables data traffic to be exchanged between the UE and UPF using the MPQUIC-IP steering functionality. + +![Sequence diagram illustrating the procedure for enabling data traffic using the MPQUIC-IP steering functionality between a UE and a UPF.](5801c19431e76330430e92a598cc7a16_img.jpg) + +The diagram shows the interaction between a User Equipment (UE) and a UPF for MPQUIC-IP steering. The UE contains an IP layer, MPQUIC-IP Steering Functionality (with QoS flow selection, HTTP/3 Client, and QUIC layer), and the UPF contains its own MPQUIC-IP Steering Functionality. + +- An MA PDU Session is established. One or more ATSSS rules use the MPQUIC steering functionality. +- Determine the number of QUIC connections to establish via the MA PDU Session. +- Establish QUIC connection #1 and enable multipath support. UE indicates that QUIC connection #1 is associated with a QoS flow #1 (QFI-1). HTTP Settings are negotiated between the HTTP/3 client in UE and the HTTP/3 proxy in UPF. +- Establish QUIC connection #2 and enable multipath support. UE indicates that QUIC connection #2 is associated with a QoS flow #2 (QFI-2). HTTP Settings are negotiated between the HTTP/3 client in UE and the HTTP/3 proxy in UPF. +- Send stream data (stream\_id=0, HEADERS) from UE to UPF. HEADERS include: method = CONNECT, protocol = connect-ip, scheme = https, path = /vpn, authority = upf.example.org. +- Stream data received (stream\_id=0, HEADERS) from UPF to UE. HEADERS include: status = 200. +- IP packet #1 arrives at the IP layer in the UE. +- IP packet #1 initiates a new IP flow. For this IP flow, select a QoS flow, a steering mode and a transport mode. +- Send IP flow id, IP packet #1, QFI, steering mode, transport mode from the IP layer to the MPQUIC-IP Steering Functionality in the UE. +- Select a QUIC connection for the IP flow. Allocate a new QUIC stream for the IP flow. Configure the QUIC stream to apply the steering mode. +- Allocate new stream (steering\_mode) from the MPQUIC-IP Steering Functionality to the QUIC layer in the UE. +- stream\_id = 40 from the QUIC layer to the MPQUIC-IP Steering Functionality. +- Send datagram (DATAGRAM (IP packet #1)) from the QUIC layer to the MPQUIC-IP Steering Functionality. +- Select path based on the steering mode of the stream from the MPQUIC-IP Steering Functionality to the QUIC layer. +- Send IP packet #1 using the allocated QUIC stream on the selected QUIC connection (internal UE process). +- DATAGRAM (Quarter Stream ID = 10, HTTP Datagram Payload = IP packet #1) from the QUIC layer to the UPF. +- IP packet #1 (to remote host) from the UPF. +- IP packet #2 (from remote host) from the UPF. +- DATAGRAM (Quarter Stream ID = 10, HTTP Datagram Payload = IP packet #2) from the UPF to the MPQUIC-IP Steering Functionality. +- Datagram received (DATAGRAM (IP packet #2)) from the MPQUIC-IP Steering Functionality to the QUIC layer. +- IP flow id, IP packet #2 from the QUIC layer to the MPQUIC-IP Steering Functionality. +- IP packet #2 from the MPQUIC-IP Steering Functionality to the IP layer. +- IP packet #3 arrives at the IP layer in the UE. +- IP flow id, IP packet #3 from the IP layer to the MPQUIC-IP Steering Functionality. +- Send datagram (DATAGRAM (IP packet #3)) from the MPQUIC-IP Steering Functionality to the QUIC layer. +- Select path based on the steering mode of the stream from the QUIC layer to the MPQUIC-IP Steering Functionality. +- DATAGRAM (Quarter Stream ID = 10, HTTP Datagram Payload = IP packet #3) from the QUIC layer to the UPF. +- IP packet #3 (to remote host) from the UPF. + +Sequence diagram illustrating the procedure for enabling data traffic using the MPQUIC-IP steering functionality between a UE and a UPF. + +Figure 6.12.3-1: Procedure for enabling data traffic using the MPQUIC-IP steering functionality + +- The UE establishes a MA PDU Session with the 5G core (5GC) network. During the MA PDU Session establishment: + - In the PDU Establishment Request message, the UE indicates that it supports the MPQUIC-IP steering functionality. This indication can be used by the network (a) to select a UPF that also supports the MPQUIC-IP steering functionality and (b) to decide whether the ATSSS/N4 rules for the MA PDU Session may use the MPQUIC-IP steering functionality. + - The UE receives MPQUIC-IP proxy information, i.e. one IP address of UPF, one UDP port number and the proxy type (e.g. "connect-ip"). This information is used by the UE for establishing QUIC connections with the UPF, which is also referred to as "MPQUIC-IP proxy". + - The UE receives one IP address/prefix for the MA PDU Session and two additional IP addresses/prefixes, called "link-specific multipath QUIC" addresses; one associated with 3GPP access and another associated with the non-3GPP access. These two addresses can be used by the UE to create two paths in a multipath QUIC connection. + - The UE receives QoS rules and ATSSS rules to be applied for the MA PDU Session, for QoS enforcement and traffic steering enforcement respectively. Similar rules (N4 rules) are received by UPF. + +2. After the MA PDU Session is established and the UE identifies that one or more ATSSS rules require traffic steering using the MPQUIC-IP steering functionality, the UE determines the number of multipath QUIC connections to be established with the UPF (MPQUIC-IP proxy). For example, the UE may determine to establish as many multipath QUIC connections, as the number of QoS flows of the MA PDU Session, i.e. one multipath QUIC connection per QoS flow. The QoS rules provided to UE include downlink QoS information and the UE applies the downlink QoS information to establish QUIC connections for the QoS flows used for downlink traffic only. +3. The UE establishes the number of multipath QUIC connection with the UPF (MPQUIC-IP proxy) determined in the previous step. This results into several multipath QUIC connections between the UE and UPF, each one composed of multiple paths, e.g. one path over 3GPP access and another path over non-3GPP access. + +NOTE 1: Data transmitted over a multipath QUIC connection must be encrypted according to RFC 9001 [7]. However, encryption might not be necessary when the multipath QUIC connection is established between UE and UPF, because the underlying 5G security mechanisms can be applied. + +**Editor's note:** Whether and how encryption in the QUIC layer can be omitted is FFS and need to be verified by SA3. The impact due to encryption regarding overhead and performance is FFS. + +During a QUIC connection establishment, the UE and UPF negotiate QUIC transport parameters and indicate (a) support of QUIC Datagram frames and (b) support of multipath. They indicate support of QUIC Datagram frames by providing the "max\_datagram\_frame\_size" transport parameter with a non-zero value (see RFC 9221 [9]) and they indicate support of multipath by providing the "enable\_multipath" transport parameter (see draft-ietf-quic-multipath [10]). + +After a QUIC connection establishment, the HTTP/3 client and the HTTP/3 proxy negotiate HTTP settings and indicate support of HTTP Datagrams (see draft-ietf-masque-h3-datagram [29]) and support of Extended CONNECT (see draft-ietf-httpbis-h3-websockets [30]). + +The QoS flow associated with a QUIC connection is also negotiated between the UE and UPF. This is done by using a new QUIC transport parameter (defined by 3GPP) when the QUIC connection is established. + +NOTE 2: QUIC transport parameter needs to be registered in IANA (by stage 3). + +4. On each of the established QUIC connections, the UE sends an extended HTTP CONNECT request to UPF (as defined in [31]) indicating that IP proxying over HTTP is needed. If this is accepted by UPF, it responds with a 200 status. +5. The UE generates a new IP packet (IP packet #1) that should be sent via the MA PDU Session. This IP packet initiates a new IP flow, i.e. a sequence of IP packets using the same 5-tuple. For this new IP flow (and for each new IP flow): + - The UE selects a QoS flow (QFI) over which the IP flow should be transmitted. This is selected by using the received QoS rules. + - The UE selects a steering mode that should be applied for the IP flow. This is selected by using the received ATSSS rules. + - The UE selects a transport mode, e.g. a datagram transport mode or the stream transport mode. This is selected by using the received ATSSS rules, i.e. each ATSSS rule which indicates that the MPQUIC-IP steering functionality should be applied for the matching traffic, indicates also the transport mode that should be applied for this traffic. + +The datagram transport mode supports the following two sub-modes of operation: + +- Datagram mode 1 (with sequence numbers): The HTTP/3 proxy/client or the "QoS flow selection and Steering mode selection" layer prefixes each UDP data with a sequence number before passing it to the QUIC layer for multipath transmission. The sequence numbers are applied by the receiving endpoint to re-order the UDP data and remove duplicated UDP data. Details of how packet reordering is supported with the MPQUIC-IP steering functionality are provided in clause 6.12.6. +- Datagram mode 2 (without sequence numbers): The HTTP/3 proxy/client does not prefix each IP packet with a sequence number before passing it to the QUIC layer for multipath transmission. This may result (depending on the applied steering mode) in data delivery with out-of-order packets and/or with duplicated packets. For some applications, however, such type of data delivery may be acceptable. + +The datagram mode 2 is needed (although it does not support re-ordering) because it features benefits compared to ATSSS-LL, e.g. (a) it supports congestion control, (b) it supports RTT/PLR measurements without the need to implement the PMF protocol, etc. + +In both datagram modes, every IP packet is encapsulated within an HTTP DATAGRAM, which if further encapsulated within an QUIC DATAGRAM frame [9]. The payload of the HTTP DATAGRAM is composed of a Context ID and a Payload (as defined in draft-ietf-masque-connect-ip [31]): HTTP DATAGRAM payload = {Context ID (i), Payload (..) }. + +The Datagram mode 1 and Datagram mode 2 use two different (and pre-defined in 3GPP) Context IDs, e.g. Context ID=0 and Context ID=1, respectively. With Context ID=0, the Payload contains the IP packet, whereas, with Context ID=1, the Payload contains a sequence number followed by the IP packet. The format of QUIC DATAGRAMs used in both datagram modes is shown below. As specified in clause 6.12.6, the Datagram mode 1 may support reordering either in the HTTP/3 layer (as described above) or in the layer above HTTP/3. In the latter case, the definition of a new Context ID is not needed as sequencing and reordering is performed outside the HTTP/3 layer. + +| | | +|-----------------|--| +| Datagram mode 1 | | +| Datagram mode 2 | | + +- The UE selects a multipath QUIC connection to be used for the new IP flow (e.g. based on the selected QFI) and the UE allocates a new QUIC stream (e.g. stream 40) in this multipath QUIC connection. This new stream is associated with the new IP flow. The UE configures the new stream to transmit data traffic using the selected steering mode for this IP flow. + +- The UE sends the IP packet using the allocated new stream on the selected QUIC connection. + +When the datagram transport mode is selected (mode 1 or mode 2), the UE encapsulates the IP packet within an HTTP DATAGRAM frame [29], which is transferred inside a QUIC DATAGRAM frame [9]. The header of the HTTP DATAGRAM indicates that this datagram is associated with stream 40 (i.e. the Quarter Stream ID is set to 10). + +When the stream transport mode is selected, the UE encapsulates the IP packet within an HTTP DATAGRAM frame [29] that is further encapsulated in a DATAGRAM capsule (see [29]), which is transferred inside a QUIC STREAM frame [6]. + +In the example procedure shown in Figure 6.12.3-1, the datagram transport mode (mode 1 or mode 2) is selected. The UE sends a QUIC DATAGRAM frame to UPF that encapsulates the IP packet, which is forwarded by UPF to the remote host. + +- When an IP packet is received by UPF (MPQUIC-IP proxy) from the remote host (IP packet #2), this IP packet is transferred to the UE using the established context information for the IP flow, i.e. using the selected multipath QUIC connection, the selected stream on this connection, the selected steering mode, and the selected transport mode. Such context information is stored in the UPF and in the UE and is applied for all the IP packets of the IP flow. + +- Similarly, when another IP packet is generated by the UE app (IP packet #3), this IP packet is transferred to UPF (MPQUIC-IP proxy) using again all the stored context information for the IP flow. + +NOTE 2: The context information for an IP flow in the UE and in the UPF is created when the initial IP packet (i.e. IP packet #1) of this IP flow is transferred. All subsequent IP packets of the same IP flow are transferred between the UE and the UPF using this context information. + +When the UE identifies that the context information for an IP flow is no longer needed, the UE deletes this context information and releases the associated QUIC stream, which cause the UPF to delete the context information stored in UPF. + +The following figure 6.12.3-2 illustrates an example of how the uplink traffic of various IP flows is transferred from the UE to UPF using QUIC multipath transport, and how the UPF relays this traffic to a final destination (remote host). Note that, for each IP flow there is an associated QUIC connection and an associated bidirectional QUIC stream, which + +is configured to apply a specific steering mode for the uplink traffic. For example, the red IP flow is associated with the multipath QUIC connection #1 and with the red Stream Y, which is configured to apply the Smallest delay steering mode in the uplink direction. + +All IP flows shown in this figure, except the blue IP flow, are transferred with the datagram transport mode (mode 1 or mode 2), i.e. their data packets are transferred inside QUIC DATAGRAM frames. The blue IP flow is transferred with the stream transport mode, so its data packets are transferred inside QUIC STREAM frames. + +The downlink traffic of IP flows is transferred between the UE and UPF in a similar way. + +![Diagram illustrating the user-plane operation using the MPQUIC-IP steering functionality in the uplink direction. The diagram shows traffic from the UE (User Equipment) to the UPF (UPF) and then to multiple Remote Hosts. In the UE, different IP flows (e.g., from the IP layer) are processed through QoS Flow selection & Steering Mode selection, resulting in QFI-2 and QFI-1. These are then handled by HTTP/3 client and QUIC (Multipath connection #1) and QUIC (Multipath connection #2) components. The MPQUIC-IP Steering Functionality directs traffic to different QUIC connections based on steering modes: Active-Standby, Smallest delay, and Load balancing. The UPF side shows HTTP/3 proxy and QUIC (Multipath connection #1) and QUIC (Multipath connection #2) components. The MPQUIC-IP Steering Functionality on the UPF side directs traffic to different Remote Hosts. The diagram also includes details of packet encapsulation: Stream Frame (Datagram capsule) with QUIC hdr, UDP hdr, and IP hdr, and Datagram frame w/ IP packet. The UE's link-specific multipath QUIC address is UPF's address, and the Dst. UDP port is UPF's port.](6707cae4df136f92a0c9f3a4676f91a6_img.jpg) + +Diagram illustrating the user-plane operation using the MPQUIC-IP steering functionality in the uplink direction. The diagram shows traffic from the UE (User Equipment) to the UPF (UPF) and then to multiple Remote Hosts. In the UE, different IP flows (e.g., from the IP layer) are processed through QoS Flow selection & Steering Mode selection, resulting in QFI-2 and QFI-1. These are then handled by HTTP/3 client and QUIC (Multipath connection #1) and QUIC (Multipath connection #2) components. The MPQUIC-IP Steering Functionality directs traffic to different QUIC connections based on steering modes: Active-Standby, Smallest delay, and Load balancing. The UPF side shows HTTP/3 proxy and QUIC (Multipath connection #1) and QUIC (Multipath connection #2) components. The MPQUIC-IP Steering Functionality on the UPF side directs traffic to different Remote Hosts. The diagram also includes details of packet encapsulation: Stream Frame (Datagram capsule) with QUIC hdr, UDP hdr, and IP hdr, and Datagram frame w/ IP packet. The UE's link-specific multipath QUIC address is UPF's address, and the Dst. UDP port is UPF's port. + +**Figure 6.12.3-2: Example of user-plane operation using the MPQUIC-IP steering functionality (UL direction)** + +### 6.12.4 User-plane overhead + +*Editor's note: This clause is FFS.* + +### 6.12.5 Co-existence with MPTCP and ATSSS-LL + +*Editor's note: This clause is FFS.* + +### 6.12.6 Handling of out-of-order delivery + +In some scenarios, the multipath transmission of an IP flow using the MPQUIC-IP steering functionality can lead to a large percentage of received packets being out-of-order. These packets need to be reassembled in the correct order (i.e. to be re-ordered) before they are consumed. This out-of-order delivery issue can be significant when: + +- The MPQUIC-IP steering functionality applies the Load-Balancing steering mode for an IP flow and (a) the transmitted packets are scheduled across the two accesses in a per-packet round-robin fashion (aka "per-packet splitting") and (b) the difference of RTTs across the two accesses is large. + +In other scenarios, e.g. when the MPQUIC-IP steering functionality applies a steering mode other than Load-Balancing, the out-of-order delivery caused by multipath transmission is very limited because, most of the time, the traffic of the IP flow is transmitted on one access only. + +Even in the scenarios where Load-Balancing is applied, the excessive out-of-order delivery can be mitigated by avoiding per-packet round-robin scheduling. Note that the ATSSS specifications mandate only the traffic to be split using certain percentages (e.g. 50% over 3GPP, 50% over non-3GPP) but do not specify a time window for achieving these percentages. For example, a UE may choose to perform splitting every 20 packets, e.g. send 10 packets over 3GPP and the next 10 packets over non-3GPP. This type of traffic scheduling can be very well applied by the UE/UPF for Load-Balancing, and it is compliant with the ATSSS specifications. UE/UPF implementations may also choose to adjust their traffic scheduling based on the difference of RTTs across the two accesses in order to minimize the percentage of out-of-order packets. + +Nevertheless, to enable scenarios where per-packet splitting is required and out-of-order delivery cannot be avoided otherwise, the MPQUIC-IP steering functionality is able to: + +- Offload the re-ordering procedure to the application, when the network indicates (via the "transport mode" parameter in the ATSSS/N4 rules) that Datagram mode 2 should be applied. In this case, the MPQUIC-IP does not perform packet re-ordering since the PCF indicates that packet re-ordering can be handled by the application. +- Apply packet re-ordering by using the existing mechanisms provided by QUIC for stream transport, when the PCF indicates that the stream mode should be applied. This may be indicated by PCF for applications that do not perform retransmissions themselves (e.g. do not embed QUIC streaming functionality in the application) hence the meltdown effect can be avoided. +- Apply packet re-ordering by using new mechanisms not provided by QUIC, when the PCF indicates that the Datagram mode 1 should be applied. This may be indicated by PCF for applications that perform retransmissions themselves (e.g. embed QUIC streaming functionality in the application). + +The new mechanisms that can be used for packet sequencing and re-ordering in Datagram mode 1 can be supported either in the HTTP/3 layer (as described in clause 6.12.3) or can be supported in the layer above HTTP/3. Whether the mechanisms for Datagram mode 1 are needed in Rel-18 or whether the Stream mode is sufficient is considered in the conclusions of KI#2 (in clause 8). + +**Editor's note:** It is FFS how to ensure re-ordering on the receiver side is implemented and activated, when needed. + +**Editor's note:** It is FFS how same re-ordering in both Down- and Uplink can be provided which is pre-requisite for a consistent and good user experience. + +**Editor's note:** http3 does not specify sequencing. It is FFS which IETF sequencing scheme can/will be used. + +**Editor's note:** It is FFS how the MPQUIC-IP steering functionality does re-ordering for the Datagram mode 1 (with sequence numbers). It is FFS whether and which parts of re-ordering mechanisms can be specified by IETF, should be specified by 3GPP and can be left for implementation. + +**Editor's note:** It is FFS whether Stream mode and/or Datagram mode 2 are needed. Both do not support required rel18 functionality for non-TCP traffic splitting of unreliable traffic, including the transport mode negotiation. + +### 6.12.7 Handling of duplicated packets + +In some scenarios, the multipath transmission of a IP flow using the MPQUIC-IP steering functionality can lead to reception of double copies of the same packet. The duplicated copies of packets need to be discarded (i.e. to be deduplicated) before they are consumed. This duplicated delivery issue can arise when: + +- The MPQUIC-IP steering functionality applies the redundant steering mode for an IP flow. + +The MPQUIC-IP steering functionality addresses this issue as follows: + +- An ATSSS/N4 rule which indicates that redundant steering mode should be applied, may include an additional parameter called "deduplication info". When the "deduplication info" parameter is false or is not included, the MPQUIC-IP steering functionality at the receiver shall not perform packet deduplication. In this case, it is assumed that packet deduplication is performed by the application itself. Otherwise, the MPQUIC-IP steering functionality shall number the transmitted packets and shall perform packet deduplication using an implementation specific mechanism. + +### 6.12.8 Impacts on Existing Nodes and Functionality + +The 5GC network functions shall be able to support the following functionality in addition to the ATSSS functionality defined in Rel-17. + +#### AMF + +- No additional functionality is needed. It is assumed that when 5GC supports ATSSS / Rel-18, then all ATSSS-capable SMFs in 5GC are able to support MPQUIC. + +#### SMF + +- Shall be able to determine whether the UE supports the MPQUIC-IP steering functionality and to indicate this to PCF. +- Shall be able to create ATSSS/N4 rules that apply the MPQUIC-IP steering functionality, based on the PCC rules received from PCF. +- Shall be able to select a UPF that supports the MPQUIC-IP steering functionality. + +#### PCF + +- If it is informed from SMF that the UE supports the MPQUIC-IP steering functionality, then it shall be able to determine which IP flows should be steered with the MPQUIC-IP steering functionality. For each IP flow, it shall be able to indicate a steering mode and a transport mode (e.g. stream mode or datagram mode 1/2). + +#### UPF + +- Shall be able to support the MPQUIC-IP steering functionality defined in clause 6.12 for steering the IP flows indicated in the received N4 rules. For each IP flow, it should apply the transport mode (e.g. stream mode or datagram mode 1/2) indicated in the received N4 rules. + +#### UE + +- Shall be able to indicate in the PDU Session Establishment Request that it supports the MPQUIC-IP steering functionality. +- Shall be able to support the MPQUIC-IP steering functionality defined in clause 6.12 for steering the IP flows indicated by the received ATSSS rules. For each IP flow, it should apply the transport mode (e.g. stream mode or datagram mode 1/2) indicated in the received ATSSS rules. + +The impact of the MPQUIC-IP steering functionality to IETF is the following: + +- The MPQUIC-IP steering functionality is based on: + - a) IETF RFCs specifying the QUIC protocol [6] – [9] and on draft-ietf-quic-multipath [10] defining QUIC extensions for multipath support; and + - b) IETF documents defining support for HTTP/3 including draft-ietf-quic-http [28], draft-ietf-masque-connect-ip [31] for supporting UDP proxying over HTTP, draft-ietf-masque-h3-datagram [29] for supporting HTTP datagrams and draft-ietf-httpbis-h3-websockets [30] for supporting Extended CONNECT. + +The MPQUIC-IP steering functionality does not require changes to any of the above documents. + +- A new QUIC transport parameter must be defined by 3GPP and registered with IANA. This transport parameter associates a QUIC connection with a QoS flow. + +## 6.13 Solution #2.4: Limiting MA-PDU Per-Packet Overhead + +### 6.13.1 Introduction + +This solution addresses aspects of Key Issue #2, especially, the impact on the user plane performance and UE impacts. + +When encapsulating IP and/or Ethernet traffic within a DCCP or QUIC tunnel, the headers of the encapsulated traffic need to be compressed to reduce the overhead per packet, using typically Ethernet Header Compression (EHC) [34, + +Annex A] and Robust Header Compression (ROHC) [32, 33] protocols. We can call this feature "inner header compression" (IHC). This solution describes how IHC can be established between the UE and UPF. IHC is optional and configured by the network based on network policy and UE/network capability. + +### 6.13.2 High Level Description + +Inner header compression can be performed by tunnel clients/servers, such as the MP-DCCP tunnel client/server defined in solution #2.1, or by the MP-DCCP or MP-QUIC layers. Using the tunnel clients/servers may be preferable since it enables using the same mechanism independently from the underlying transport protocol. Such a solution could therefore be used for any low-layer steering functionality, such as the MPDCCP-LL steering functionality defined in solution #2.1 and for the MPQUIC-IP steering functionality defined in solution #2.3. However, it is not required for high-layer steering functionalities, such as the MPQUIC steering functionality defined in solution #2.2, because no inner headers are used. + +Inner header compression should be configured on both ends, i.e. UE and UPF, prior to establishing a flow. NAS signalling can be used for this purpose, as described below. + +### 6.13.3 Procedures + +The following procedure describes how inner header compression can be configured when a new MA PDU session is created. + +![Sequence diagram illustrating the configuration of Inner Header Compression (IHC) in a MA-PDU Session. The diagram shows interactions between UE, AMF, SMF, UPF/Proxy, and AS. The process involves: 1. UE app decides to initiate communication with AS, determining to use a MA PDU session and IHC. 2. UE sends a PDU Session Establishment Request (IHC capabilities) to AMF. 3. AMF forwards this to SMF. 4. SMF determines IHC configuration and sends an N4 session establishment request to UPF/Proxy. 5. UPF/Proxy configures the tunnel server to use IHC. 6. UPF/Proxy sends an N4 session establishment response to SMF. 7. SMF sends a PDU Session Establishment Accept (IHC configuration) to AMF. 8. AMF forwards this to UE. 9. UE configures the tunnel client to use IHC. Finally, application traffic is steered/split over the MA PDU session between UE and UPF, with inner headers compressed between them, and then forwarded by UPF to/from AS.](a7721892ae499a78173ff3dfdc4e65a9_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UPF/Proxy + participant AS + + Note right of UE: 1. UE app decides to initiate communication with AS. UE determines to use a MA PDU session. UE determines to use IHC. + UE->>AMF: 2. PDU Session Establishment Request (IHC capabilities) + AMF->>SMF: 3. SMF determines IHC configuration + SMF->>UPF/Proxy: 4. N4 session establishment request (IHC configuration) + Note right of UPF/Proxy: 5. UPF configures tunnel server to use IHC for MA PDU session flows, using IHC configuration from SMF. + UPF/Proxy->>SMF: 6. N4 session establishment response + SMF->>AMF: 7. PDU Session Establishment Accept (IHC configuration) + AMF->>UE: 8. UE configures tunnel client to use IHC for appropriate MA PDU session flows, using IHC configuration from SMF. + Note right of UE: Application traffic is steered/split over MA PDU session between UE and UPF. Inner headers are compressed between UE and UPF. + Note right of UPF/Proxy: Application traffic is forwarded by UPF to/from AS + +``` + +Sequence diagram illustrating the configuration of Inner Header Compression (IHC) in a MA-PDU Session. The diagram shows interactions between UE, AMF, SMF, UPF/Proxy, and AS. The process involves: 1. UE app decides to initiate communication with AS, determining to use a MA PDU session and IHC. 2. UE sends a PDU Session Establishment Request (IHC capabilities) to AMF. 3. AMF forwards this to SMF. 4. SMF determines IHC configuration and sends an N4 session establishment request to UPF/Proxy. 5. UPF/Proxy configures the tunnel server to use IHC. 6. UPF/Proxy sends an N4 session establishment response to SMF. 7. SMF sends a PDU Session Establishment Accept (IHC configuration) to AMF. 8. AMF forwards this to UE. 9. UE configures the tunnel client to use IHC. Finally, application traffic is steered/split over the MA PDU session between UE and UPF, with inner headers compressed between them, and then forwarded by UPF to/from AS. + +**Figure 6.13.3-1: Configuration of Inner Header Compression in a MA-PDU Session** + +In step 1, a UE application decides to initiate communication with an Application Server (AS). UE determines to use a MA PDU session. UE determines to use IHC. + +In step 2, UE sends a PDU Session Establishment Request. The request includes the UE's supported IHC capabilities (e.g. the supported RoHC profiles). + +In step 3, SMF determines, based on the PCC rules, which traffic of the MA PDU Session should be steered with MP-DCCP/MP-QUIC based steering functionality. SMF determines the IHC configuration based on the IHC capabilities of the UE and the network. + +The same IHC configuration applies to all SDFs which are steered with a MP-DCCP/MP-QUIC based steering functionality. + +In step 4, SMF sends to UPF a N4 session establishment/modification request, including an IHC configuration. + +In step 5, UPF configures packet detection, enforcement and reporting rules, and configures the tunnel server to use the received IHC configuration for the appropriate MA PDU session flows. + +In step 6, UPF sends a N4 session establishment response to SMF. + +In step 7, SMF sends to UE, through AMF, a PDU Session Establishment Accept message including IHC configuration. + +In step 8, UE configures the tunnel client to use IHC for the appropriate MA PDU session flows, based on the IHC configuration in the PDU session establishment accept message. + +From this point on, the application traffic is switched/steered/split over a MA PDU session between UE and UPF. Inner headers are compressed between UE and UPF. The application traffic is forwarded by the UPF to/from the Application Server (AS). + +### 6.13.4 Impacts on Existing Nodes and Functionality + +IHC requires UE and UPF to implement header compression, e.g. using ROHC and/or EHC. This function may be in the tunnel client (on UE) and server (on UPF). UE indicates its IHC capabilities in the PDU session establishment request and obtains IHC configuration in PDU session establishment accept. + +The SMF determines IHC configuration based on the IHC capabilities of the UE and the network. The SMF transmits the IHC configuration to UPF (over N4 signalling) and to UE (over NAS signalling). + +## 6.14 Solution #3.5: Redundant Traffic Steering Mode Activation/Deactivation + +### 6.14.1 Introduction + +This solution addresses aspects of Key Issue #3 (Solutions for Redundant Traffic Steering Mode), especially related to the mechanism to support the activation and deactivation of traffic duplication, and the criteria needed for making this decision. In the following, we use existing solutions (MP-QUIC-LL as described in TR 23.700-93 [5], Solution #6, and MP-DCCP-LL as described in the present document, clause 6.3) as the framework to describe the solution. However, the solution is not tightly tied to these solutions, and can work for other solutions. + +### 6.14.2 High Level Description + +In both the MP-DCCP and MP-QUIC based solutions, the protocol stack at the UE and UPF is as shown in Figure 6.14.2.1. + +![Figure 6.14.2-1: Protocol Stack for MP-QUIC and MP_DCCP. The diagram shows two protocol stacks: UE (User Equipment) on the left and UPF (UPF) on the right. The UE stack consists of a PDU (IP@0) at the top, followed by a box containing the MP-QUIC/DCCP Tunnel Client (MxTC), the MP-QUIC/DCCP-LL layer, and the MP-QUIC/DCCP layer. Below this is a row with two boxes labeled IP@1 and IP@2. At the bottom are two boxes labeled 3GPP access and Non-3GPP access. The UPF stack consists of a PDU at the top, followed by a box containing the MP-QUIC/DCCP Tunnel Server (MxTS), the MP-QUIC/DCCP-LL layer, and the MP-QUIC/DCCP layer. Below this is a row with two boxes labeled IP@3 and IP@4. At the bottom are two boxes labeled GTP tunnel (Non-3GPP access) and GTP tunnel (3GPP access).](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +Figure 6.14.2-1: Protocol Stack for MP-QUIC and MP\_DCCP. The diagram shows two protocol stacks: UE (User Equipment) on the left and UPF (UPF) on the right. The UE stack consists of a PDU (IP@0) at the top, followed by a box containing the MP-QUIC/DCCP Tunnel Client (MxTC), the MP-QUIC/DCCP-LL layer, and the MP-QUIC/DCCP layer. Below this is a row with two boxes labeled IP@1 and IP@2. At the bottom are two boxes labeled 3GPP access and Non-3GPP access. The UPF stack consists of a PDU at the top, followed by a box containing the MP-QUIC/DCCP Tunnel Server (MxTS), the MP-QUIC/DCCP-LL layer, and the MP-QUIC/DCCP layer. Below this is a row with two boxes labeled IP@3 and IP@4. At the bottom are two boxes labeled GTP tunnel (Non-3GPP access) and GTP tunnel (3GPP access). + +**Figure 6.14.2-1: Protocol Stack for MP-QUIC and MP\_DCCP** + +The MP-QUIC/DCCP Tunnel Client (MxTC) at the UE, and the MP-QUIC/DCCP Tunnel Server (MxTS) at the UPF, rely on the underlying MP-QUIC or MP-DCCP protocol. These protocols support a number of traffic steering modes, including redundant traffic steering. + +In both cases, the MxTC establishes an MP-QUIC/DCCP connection with the MxTS in the UPF. An MP-QUIC/DCCP connection carries the traffic of only one QoS flow. In addition, it is assumed that an MP-QUIC/DCCP connection will be configured with a single steering mode. The MxTC receives UL PDUs from the upper layer and, for each UL PDU, the MxTC selects a steering mode to be applied for the UL PDU based on the ATSSS rules in the UE. The MxTC subsequently selects a MP-QUIC/DCCP connection to transmit the PDU based on the selected QoS flow and the selected steering mode. + +This mechanism works well for QoS flows which are known, a priori, to require redundant transmission. For such use cases, the choice of redundant transmission can be made at PDU session establishment, and traffic duplication should always be activated. In other use cases, traffic duplication should only be used when needed, as duplicating traffic over both accesses results in: + +- Power consumption at the UE: The UE is required to operate over both accesses. +- Core network load: The redundant transmissions will result in a certain load to the 5GC. +- Processing at UE and UPF: The UE and UPF both need to handle re-ordering and possible reception of duplicate PDUs. +- Radio resource usage: Radio resources are used over both accesses. + +For these use cases, traffic duplication should only be used when needed, and should be dynamically activated / deactivated on a per-packet basis. + +NOTE: The mechanism to duplicate the packet is FFS. It may be implemented at the MxTC or it may be implemented in the layers below the MxTC (for example in the MP-QUIC/DCCP layer). + +The Activation/Deactivation decision should be made at the MxTC for the UE and at the MxTS for the UPF, and should be based on selection criteria and measurements: + +- Packet Loss Rate (PLR): This measurement indicates the rate of PDU packet loss for each access network. The measurement is applicable to both uplink and downlink transmissions. +- Delay: This measurement indicates the PDU transmission delay for each access network. This is a one-way delay between UE and UPF for uplink transmissions, and between UPF and UE for downlink transmissions. + +- Variability of Delay: This measurement indicates the variability of PDU arrivals (jitter) over an access network. PDU arrivals at the UPF for uplink transmission and PDU arrivals at the UE for downlink transmissions. The variability of delay measurement is a reflection of transfer quality stability within certain time interval. It may be calculated using the mechanisms described in Solution #3 in TR 23.700-93 [5]. Variability of Delay measurements prevent wasteful transmissions over an access path. Some services, such as gaming and IMS voice, are sensitive to variability of delay. For these services, activating traffic duplication over a path that will not meet the variability of delay requirements, will not be useful. +- Load: This measurement indicates the load over an access network. + +The selection criteria should rely on these measurements and should allow the UE to activate traffic duplication only when **"needed and effective"**. For example, if the PLR is of critical importance of a data flow, the duplication should be activated when the measured PLR on the active access leg(s) is bigger than the threshold. For another example, the UE should not activate traffic duplication over a non-3GPP access, if the delay over the non-3GPP access will not meet the one-way delay requirement for the PDU. In such a case, the duplicate transmissions over the non-3GPP access would be useless. The selection criteria are included in the ATSSS rules provided to the UE and the N4 Rules provided to the UPF. The measurement configuration is included in the Measurement Assistance Information. + +When traffic duplication is deactivated, the UE and UPF should rely on a default steering mode (such as "Active-Standby" or "Smallest Delay") to select which access path to use. The default steering mode configuration could be chosen in a similar way how normal steering mode is configured (e.g. depending on UE/NW capabilities) and provided in the ATSSS rules to the UE and in the N4 rules to the UPF. The duplication criteria is configured in a way that the measurements in default steering mode can be used. For example, if Active-Standby is configured as the default steering mode, the PLR measurement on the active access, instead of both accesses, should be used in the criteria. + +**Editor's note: How to handle out-of-order reception due to latency difference between access paths is FFS.** + +### 6.14.3 Procedures + +The following procedure (Figure 6.14.3.1) describes how traffic duplication can be dynamically activated and/or deactivated. + +![Sequence diagram illustrating the activation/deactivation of traffic duplication in Redundant Steering Mode. The diagram shows interactions between UE, AMF, SMF, and UPF/Proxy. The process starts with the UE deciding to initiate communication and determining to use a MA-PDU session. The UE sends a PDU Session Establishment/Modification Request to the AMF. The AMF forwards this to the SMF. The SMF determines ATSSS rules, N4 rules, and Measurement Assistance Information. The SMF sends an N4 session establishment/modification request to the UPF/Proxy. The UPF/Proxy configures the tunnel server for MA-PDU session flows and sends an N4 session establishment/modification response to the SMF. The SMF sends a PDU Session Establishment/Modification Accept to the AMF. The AMF forwards this to the UE. The UE configures the tunnel client for MA-PDU session flows. If measurements are not available, the UE and UPF transmissions use traffic duplication, if initially activated. Finally, the UE and UPF monitor selection criteria and decide whether traffic duplication is activated or deactivated.](149826281804ec51b5cca5603c88b23b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UPF/Proxy + + Note left of UE: 1. UE app decides to initiate communication with AS. UE determines to use a MA-PDU session. + UE->>AMF: 2. PDU Session Establishment/Modification Request (support for redundant steering mode) + AMF->>SMF: + Note right of SMF: 3. SMF determines ATSSS rules, N4 rules, Measurement Assistance Information + SMF->>UPF/Proxy: 4. N4 session establishment/modification request (N4 rules (including selection criteria, initial activated/deactivated, default steering mode), Measurement Assistance Information) + Note right of UPF/Proxy: UPF configures tunnel server for MA-PDU session flows + UPF/Proxy->>SMF: N4 session establishment/modification response + SMF->>AMF: 5. PDU Session Establishment/Modification Accept (ATSSS rules (including selection criteria, initial activated/deactivated, default steering mode), Measurement Assistance Information) + AMF->>UE: + Note left of UE: 6. UE configures tunnel client for MA-PDU session flows + Note right of UPF/Proxy: 7. If measurements not available, UE and UPF transmissions use traffic duplication, if initially activated + Note right of UPF/Proxy: UE and UPF monitor selection criteria and decide whether traffic duplication is activated or deactivated + +``` + +Sequence diagram illustrating the activation/deactivation of traffic duplication in Redundant Steering Mode. The diagram shows interactions between UE, AMF, SMF, and UPF/Proxy. The process starts with the UE deciding to initiate communication and determining to use a MA-PDU session. The UE sends a PDU Session Establishment/Modification Request to the AMF. The AMF forwards this to the SMF. The SMF determines ATSSS rules, N4 rules, and Measurement Assistance Information. The SMF sends an N4 session establishment/modification request to the UPF/Proxy. The UPF/Proxy configures the tunnel server for MA-PDU session flows and sends an N4 session establishment/modification response to the SMF. The SMF sends a PDU Session Establishment/Modification Accept to the AMF. The AMF forwards this to the UE. The UE configures the tunnel client for MA-PDU session flows. If measurements are not available, the UE and UPF transmissions use traffic duplication, if initially activated. Finally, the UE and UPF monitor selection criteria and decide whether traffic duplication is activated or deactivated. + +**Figure 6.14.3-1: Redundant Steering Mode: Activation/Deactivation of Traffic Duplication** + +In step 1, UE application decides to initiate communication with AS. UE determines to use a MA-PDU session. + +In step 2, UE sends a PDU Session Establishment or Modification Request. The request includes capability support for redundant steering mode. + +In step 3, SMF determines to use MA-PDU session, e.g. based on configuration or PCC rules. SMF determines ATSSS rules for the UE and N4 rules for UPF. + +In step 4, SMF sends to UPF a N4 session establishment/modification request, including N4 rules and Measurement Assistance Information. The N4 rules include an indication whether the UPF should start with traffic duplication activated or deactivated, default steering mode configuration to use if duplication is deactivated, as well as the selection criteria to activate or deactivate traffic duplication. + +In step 5, SMF sends to UE, through AMF, a PDU Session Establishment/Modification Accept message including ATSSS rules for redundant steering mode and Measurement Assistance Information. The ATSSS rules include an indication whether the UE should start with traffic duplication activated or deactivated, default steering mode configuration to use if duplication is deactivated, as well as the selection criteria to activate or deactivate traffic duplication. + +In step 6, UE configures the MxTC. + +In step 7, before measurements for selection criteria are available, MxTC determines whether traffic duplication should be activated or deactivated based on the indication from the PDU Session Establishment/Modification Accept message. + +From this point on, the application traffic is sent over the MA-PDU session between UE and UPF. The MxTC monitors the selection criterion and based on ATSSS rules, decides whether traffic duplication should be activated or deactivated for the uplink application traffic. Similarly, the MxTS monitors the selection criterion and based on N4 rules, decides whether traffic duplication should be activated or deactivated for the downlink application traffic. + +### 6.14.4 Impacts on Existing Nodes and Functionality + +PCF: + +- Provide PCC rules to SMF, considering the selection criteria to activate or deactivate traffic duplication + +SMF: + +- Based on the PCC rules, create ATSSS rules and N4 rules including the selection criteria to activate or deactivate traffic duplication, and default steering mode configuration to use if duplication is deactivated. + +UPF: + +- Shall be able to determine whether traffic duplication is activated or deactivated. + +UE: + +- Shall be able to indicate support of redundant steering mode when requesting a MA PDU Session. +- Shall be able to determine whether traffic duplication is activated or deactivated. + +## 6.15 Solution #3.6: Redundant steering mode + +### 6.15.1 Introduction + +This solution addresses KI#3 on support of redundant traffic steering. + +### 6.15.2 High-level Description + +Redundant steering mode (RSM) allows traffic to be transmitted via 3GPP and non-3GPP accesses in a redundant way to achieve the lowest latency and to lower the loss rate. + +In this solution all packets are duplicated over both 3GPP and non-3GPP access when RSM applies for the traffic. This ensures that the application traffic always benefits from the increased robustness that comes with duplication of packets. + +RSM can be supported when MPTCP steering functionality is used. RSM does not apply to the ATSSS-LL steering functionality. + +**Editor's note:** RSM for MP-QUIC/MP-DCCP is FFS. + +In case RSM is applied for a GBR flow, the SMF provides the related GBR QoS profile to both 3GPP and non-3GPP accesses. This ensures that the corresponding GBR resources are reserved in both accesses. + +**Editor's note:** It is FFS if and how AF can influence the use of RSM. + +### 6.15.3 Procedures + +The existing procedures apply. Only a new Steering Mode is defined. + +### 6.15.4 Impacts on Existing Nodes and Functionality + +The PCC rules, ATSSS rules and the N4 rules are enhanced to support a new steering mode for Redundant Steering Mode. + +SMF: + +- Based on the PCC rules, create ATSSS rules and N4 rules with the new Steering Mode. + +PCF: + +- Provide PCC rules with the new Steering Mode. + +UPF: + +- If RSM is used for a traffic flow, duplicate traffic via the available access paths of a MA PDU session for the downlink traffic. Handle received duplicated uplink traffic. + +UE: + +- If RSM is used for a traffic flow, duplicate traffic via the available access paths of a MA PDU session for the uplink traffic. Handle received duplicated downlink traffic. + +**Editor's note:** It is FFS if and how AF can influence the use of RSM. + +## 6.16 Solution #5.5: Non-3GPP path switch during Registration in new non-3GPP access + +### 6.16.1 Introduction + +### 6.16.2 High-level Description + +This solution addresses Key Issue #5 "Switching traffic of an MA PDU Session between two non-3GPP access paths" by allowing a UE to Register in a new non-3GPP AN node while optionally keeping the UP connection in old non-3GPP AN node for a while, allowing the UE and UPF to switch the traffic to the new non-3GPP access before releasing the old access. The solution is based on UE triggering a Registration Request via the new non-3GPP AN node and requesting UP establishment using the "PDU Sessions to be activated" parameter. + +The solution allows both single access PDU Sessions and MA PDU Sessions to be "switched" using the Registration procedure. A reason for this is that the solution is basically describing how a mobility Registration Update is performed via non-3GPP access. If the UE initiates a mobility Registration Update via 3GPP access and indicates that it wants to activate UP connections using "PDU Sessions to be activated" parameter, it applies in the same way for single-access and MA PDU Sessions. It is proposed here that the same is assumed for mobility Registration via non-3GPP access. + +### 6.16.3 Procedures + +This procedure assumes that the UE is registered over untrusted non-3GPP access first and then switches to trusted non-3GPP access. A similar procedure is applicable if UE is registered over trusted non-3GPP access first and then switches to untrusted non-3GPP access. The UE may also be registered in 3GPP access. The solution re-uses some aspects of Solution#5.2, e.g. a new registration type. + +![Sequence diagram of Mobility Registration procedure to support non-3GPP access switching. The diagram shows interactions between UE, NG-RAN, N3IWF, TNGF, AMF, SMF, UPF, and UDM. It starts with two initial registration states: 1a. Registered over 3GPP and established MA PDU Session, and 1b. Registered over untrusted non-3GPP access and established MA PDU Session. The procedure involves registration request, authentication, N2 request/response, and final registration complete messages.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant N3IWF + participant TNGF + participant AMF + participant SMF + participant UPF + participant UDM + + Note over UE, UDM: 1a. Registered over 3GPP and established MA PDU Session + Note over UE, UDM: 1b. Registered over untrusted non-3GPP access and established MA PDU Session + + UE->>UPF: User data (red arrow) + UPF->>UE: User data (red arrow) + + UE->>AMF: 2. Registration Request (Dual non-3GPP switching indication, Registration type = mobility registration, PDU Session Status, PDU Sessions To Be Activated) + AMF->>UDM: 3. Authentication/Security + AMF->>N3IWF: 4. AN Release over untrusted non-3GPP access + AMF->>SMF: 5a. Nsmf_PDUSession_UpdateSMContext Request (Dual non-3GPP switching indication) + SMF->>UPF: 5b. N4 update + UPF->>SMF: 5c. Nsmf_PDUSession_UpdateSMContext Response (N2 information) + AMF->>TNGF: 6a. N2 Request (CN tunnel information, TNGF key) + TNGF->>UE: 6b. IKE AUTH to complete IPsec SA establishment + UE->>TNGF: 6c. IKE Create CHILD SA + TNGF->>AMF: 7. N2 Response (AN tunnel information) + AMF->>SMF: 8a. Nsmf_PDUSession_UpdateSMContext Update Request (AN tunnel information) + SMF->>UPF: 8b. N4 update + UPF->>SMF: 8c. Nsmf_PDUSession_UpdateSMContext Update Response + AMF->>N3IWF: 9. AN Release over untrusted non-3GPP access + + UE->>UPF: User data (red arrow) + UPF->>UE: User data (red arrow) + + AMF->>UE: 10. Registration Accept + AMF->>UDM: 11. Nudm_UECM_Update + UE->>AMF: 12. Registration Complete + +``` + +Sequence diagram of Mobility Registration procedure to support non-3GPP access switching. The diagram shows interactions between UE, NG-RAN, N3IWF, TNGF, AMF, SMF, UPF, and UDM. It starts with two initial registration states: 1a. Registered over 3GPP and established MA PDU Session, and 1b. Registered over untrusted non-3GPP access and established MA PDU Session. The procedure involves registration request, authentication, N2 request/response, and final registration complete messages. + +**Figure 6.16.2-1: Mobility Registration procedure to support non-3GPP access switching** + +1. The UE is registered over an untrusted non-3GPP access and may also be registered in 3GPP access. A MA PDU Session is established that has UP connections via untrusted non-3GPP access and possibly also via 3GPP access. The UE may also have single access (SA) PDU Sessions over 3GPP and/or untrusted non-3GPP access. + +During registration in non-3GPP, the AMF indicates to UE whether it supports non-3GPP access switching. + +2. The UE registers over trusted non-3GPP access with Registration type = mobility registration. The UE also indicates whether it is maintaining the old non-3GPP access connectivity by including a "dual non-3GPP access switching" indication. The UE includes in the List Of PDU Sessions To Be Activated the MA PDU Sessions that have user plane resources established over untrusted non-3GPP access. The UE may also include SA PDU Sessions active in untrusted non-3GPP access in the List Of PDU Sessions To Be Activated. The UE also indicates all SA and MA PDU Sessions that were active over the old non-3GPP access in the PDU Session status parameter. +3. The AMF may perform authentication based on existing procedures. The AMF may send an Initial Context Setup Request to TNGF and include AS security information. Alternatively, the AMF sends the Initial Context Setup Request to TNGF in step 6, after contacting the SMF(s). +4. The AMF releases the old N2 connection if the UE did not provide a "dual non-3GPP access switching" indication in step 2 or if the AMF only supports a single N2 connection via non-3GPP access. +5. The AMF notifies to the SMF(s) that the UE requested UP connection activation. For MA PDU Sessions, the AMF also includes the "dual non-3GPP access switching" indication, if received from the UE. The AMF repeats this step for all SA and MA PDU Sessions indicated in step 2. + +The SMF contacts UPF to allocate CN tunnel information, if needed. If the "dual non-3GPP switch" indication is received, the SMF does not trigger a release of UP connection (if any) to old non-3GPP access. + +The SMF replies to AMF including the CN tunnel information. + +6. The AMF sends an N2 message to TNGF and includes the CN tunnel information received from the SMF(s). The N2 message is an Initial Context Setup Request (if not sent in step 3) or a PDU Session Resource Setup request. The AMF knows that the N2 information is targeting TNGF since the UP connection setup is part of the registration in trusted non-3GPP access. + +The TNGF completes the IPSec SA establishment as described in clause 4.12a.2.2 of TS 23.502 [3] and triggers establishment of UP resources towards the UE, e.g. to create a first Child SA for the PDU Session. + +After this step, the UE may start to send UL traffic via the new non-3GPP access. + +7. The TNGF replies with Initial Context Setup Response, including AN tunnel information. +8. The AMF forwards the information to the SMF(s) and the SMF(s) provides the tunnel information to the UPF(s). For MA PDU Sessions, the UPF starts to use the trusted non-3GPP access as the non-3GPP access for the MA PDU Session, i.e. untrusted non-3GPP access is not used for downlink traffic anymore. For SA PDU Sessions, the downlink tunnel is switched to the trusted non-3GPP access. The UPF still accepts uplink packets from the untrusted non-3GPP access. +9. The AMF triggers a AN release of the untrusted non-3GPP access if not done in step 4. As a result of this procedure, user plane resources over untrusted non-3GPP access of MA PDU is completely released. Also user plane resources of SA PDU Session(s) are deactivated. The N3IWF does not need to signal to the UE since the UE may not be reachable over the old non-3GPP access. Latest when the UE recognize that user plane resources over untrusted non-3GPP access are released, the UE starts to send traffic over trusted non-3GPP access. +10. The AMF sends a NAS Registration Accept message to the UE, via the TNGF. +11. The AMF may update the registration for non-3GPP access in UDM, by providing the new RAT type. +12. The UE may send a NAS Registration Complete message, as described in TS 23.502 [3]. + +### 6.16.4 Impacts on Existing Nodes and Functionality + +UE: + +- Performs Registration with new indication for non-3GPP access switching. +- Indicates to the SMF that the UE supports non-3GPP access switching during the MA PDU Session Establishment. +- May be able to temporarily maintain simultaneous parallel user plane tunnel over untrusted 3GPP access and trusted non-3GPP access. +- When the UE receives the Registration Accept message for the target non-3GPP access, the UE considers that it is deregistered from the source non-3GPP access. + +AMF: + +- During the Registration procedure, indicate capability for non-3GPP access switching to UE. +- Update UDM with new RAT type when non-3GPP access switching is completed. +- Notifies to the SMF in Nsmf\_PDUSession\_UpdateSMContext that the UE requested non-3GPP access switching. +- May be able to temporarily maintain two N2 connections for non-3GPP access during the Registration procedure. + +SMF: + +- Not trigger release of old UP/N3 if receiving an Update from AMF to activate a new UP connection. + +UPF: + +- None. + +UDM: + +- Support for updating RAT type using Nudm\_UECM Update. + +## 6.17 Solution #5.6: Consolidated solution for traffic switching between two non-3GPP access paths + +### 6.17.1 Introduction + +The solution in clause 6.17 addresses the objective of KI#5, i.e. it specifies how the data traffic of an MA PDU Session can be switched between two non-3GPP access paths, both of them using the same PLMN. The solution borrows several aspects from solutions #5.2, #5.3 and #5.4. + +### 6.17.2 High-level Description + +The key principles of the solutions are listed below and are further detailed in the next clause. + +- The UE applies the existing procedures to register to 5GC via a non-3GPP access network. Optionally, the UE may also register to 5GC via a 3GPP access network (e.g. via NG-RAN). +- An MA PDU Session is established based on the existing procedures specified in clause 4.22.2 of TS 23.502 [3]. In addition, during the MA PDU Session establishment, the UE and the network indicate whether they support "Non-3GPP path switch", i.e. whether they can switch the traffic of an MA PDU Session from one Non-3GPP access path to another Non-3GPP access path. +- If both the UE and the network support "Non-3GPP path switch", then the following steps apply: + - When the UE wants to switch the traffic of the MA PDU Session from the existing non-3GPP access path to the new non-3GPP access path, the UE initiates registration over the new non-3GPP access path and indicates that the registration is for "Non-3GPP path switch". Also, the UE includes in the "List Of PDU Sessions To Be Activated" the identity of the existing MA PDU Session. + - A registration procedure (based on clause 4.2.2.2 of TS 23.502 [3]) takes place over the new non-3GPP access path and the SMF triggers establishment of user-plane resources for the MA PDU Session over the new non-3GPP access path. At this point, the MA PDU Session has user-plane resources over the old non-3GPP access path and over the new non-3GPP access path. + - The AMF updates its registration with the UDM for non-3GPP access and initiates deregistration over the old non-3GPP access path. The deregistration releases the user-plane resources over the old non-3GPP access and the UE and UPF start using the new non-3GPP access for the MA PDU Session. + +In order to support "Non-3GPP path switch" in a PLMN, it is assumed that all AMFs supporting ATSSS in the PLMN are enhanced to support "Non-3GPP path switch". This ensures that, if the UE establishes an MA PDU Session when connected to one AMF and receives an indication that "Non-3GPP path switch" is supported, the UE can assume the "Non-3GPP path switch" is still supported after moving into the serving area of another AMF in the same PLMN. + +### 6.17.3 Procedures + +Figure 6.17.3-1 below depicts the key steps of the solution, which enables the data traffic of an MA PDU Session to be switched from a non-3GPP access path using a N3IWF to a non-3GPP access path using a TNGF. The same steps can be used to switch the data traffic of an MA PDU Session between any non-3GPP access paths (using either N3IWF or TNGF). + +![Sequence diagram illustrating the procedure for enabling traffic switching between two non-3GPP access paths. The diagram shows interactions between UE, NG-RAN, AMF, UDM, SMF, UPF, and TNGF. The process involves optional 3GPP registration, untrusted non-3GPP registration, MA PDU Session establishment with Non-3GPP path switch support, traffic switching to a trusted non-3GPP access, and final AN release over the untrusted access.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +The sequence diagram illustrates the procedure for enabling traffic switching between two non-3GPP access paths. The participants involved are UE, NG-RAN, AMF, UDM, SMF, UPF, and TNGF. + +**Sequence of Events:** + +- 1. (Optional) UE registers via 3GPP access:** The UE registers via 3GPP access with Registration type = Initial. The AMF registers with UDM for 3GPP access and provides its GUAMI and RAT type=NR. +- 2. UE registers via untrusted non-3GPP access:** The UE registers via untrusted non-3GPP access with Registration type = Initial. The AMF registers with UDM for non-3GPP access and provides its GUAMI and RAT type (e.g., Untrusted WLAN). +- 3. Initiate MA PDU Session establishment:** + - 3a. UL NAS Transport:** The UE sends a UL NAS Transport message to the AMF with PDU Session Id=X, S-NSSAI, DNN, Request type=MA PDU request, and **Non-3GPP Path Switch supported**. The AMF sends a PDU Session Est. Request () to the SMF. + - 3b. Create SM Context Request:** The SMF sends a Create SM Context Request to the UDM with SUPI, PDU Session Id=X, S-NSSAI, DNN, MA Request Indication, **Non-3GPP Path Switch supported**, AN Type=non-3GPP, Additional AN Type=3GPP, RAT type=Virtual, and PDU Session Est. Request (). + - 3c. UECM Registration Req.:** The UDM sends a UECM Registration Req. to the SMF with PDU Session Id=X, DNN, SUPI, and SMF UUID. + - 3d. Additional steps to complete the MA PDU Session establishment:** User-plane resources are established over both accesses. + - 3e. N1N2 Message Transfer Request:** The SMF sends an N1N2 Message Transfer Request to the AMF. + - 3f. DL NAS Transport:** The AMF sends a DL NAS Transport message to the UE with PDU Session Est. Accept (**Non-3GPP Path Switch supported**). +- 4. UE discovers a trusted non-3GPP access:** The UE discovers a trusted non-3GPP access and decides to switch the MA PDU Session traffic from the existing (old) untrusted non-3GPP access to the new trusted non-3GPP access. +- 5. Registration Request:** The UE sends a Registration Request to the AMF with **Non-3GPP Path Switch indication** and List of PDU Sessions to be Activated: PDU Session Id=X. +- 6. Authentication (optional):** An optional authentication procedure occurs between the UE and the AMF. +- 7. SMC Request / Complete:** The AMF sends an SMC Request / Complete message to the UE. +- 8. Initial Context Setup:** + - 8a. Initial Context Setup Request (TNGF key):** The AMF sends an Initial Context Setup Request (TNGF key) to the TNGF. + - 8b. NWt connection establishment:** The UE and TNGF establish an NWt connection. + - 8c. Initial Context Setup Response:** The TNGF sends an Initial Context Setup Response to the AMF. +- 9. Update SM Context Request:** The AMF sends an Update SM Context Request to the SMF with SUPI, PDU Session Id=X and **Non-3GPP Path Switch indication**. +- 9b. Update SM Context Response:** The SMF sends an Update SM Context Response to the AMF with N2 info Container. +- 10. PDU Session Resource Setup Request:** The AMF sends a PDU Session Resource Setup Request to the TNGF. +- 10b. Additional steps to establish user-plane resources over the trusted non-3GPP access:** Additional steps are executed to establish user-plane resources over the trusted non-3GPP access. +- 10c. UE switches all UL traffic:** The UE switches all UL traffic from untrusted non-3GPP access to trusted non-3GPP access. +- 11. UECM Registration Request / Response:** The AMF sends a UECM Registration Request / Response to the UDM. +- 12. UECM Deregistration Notify:** The UDM sends a UECM Deregistration Notify to the AMF. +- 13. UE Context Release Command:** The AMF sends a UE Context Release Command to the TNGF. +- 13b. Additional steps to complete the AN release procedure over untrusted non-3GPP access:** Additional steps are executed to complete the AN release procedure over the untrusted non-3GPP access. +- 14. Registration Accept:** The AMF sends a Registration Accept message to the UE. +- 10d. UPF switches all DL traffic:** The UPF switches all DL traffic from untrusted non-3GPP access to trusted non-3GPP access. + +Sequence diagram illustrating the procedure for enabling traffic switching between two non-3GPP access paths. The diagram shows interactions between UE, NG-RAN, AMF, UDM, SMF, UPF, and TNGF. The process involves optional 3GPP registration, untrusted non-3GPP registration, MA PDU Session establishment with Non-3GPP path switch support, traffic switching to a trusted non-3GPP access, and final AN release over the untrusted access. + +Figure 6.17.3-1: Procedure for enabling traffic switching between two non-3GPP access paths + +- Optionally, the UE performs an initial 5G registration over 3GPP access in a PLMN. The selected AMF registers with UDM for 3GPP access and provides its GUAMI and RAT type = NR. +- The UE selects an N3IWF and performs an initial 5G registration over untrusted non-3GPP access in the same PLMN. The same AMF is selected, as the one in the previous step. The AMF registers with UDM for non-3GPP access and provides its GUAMI and RAT type = Untrusted WLAN. +- The UE requests an MA PDU Session, as specified in clause 4.22.2 of TS 23.502 [3]. Since the UE supports Non-3GPP path switch, the UE includes in the UL NAS Transport message a Non-3GPP path switch supported indication. Based on this indication, the AMF selects an SMF that supports Non-3GPP path switch and sends a Create SM Context Request to SMF including a Non-3GPP path switch indication which indicates that the AMF and the UE support Non-3GPP path switch. The SMF registers with the UDM and additional steps are executed + +to complete the MA PDU Session establishment including the establishment of user-plane resource over 3GPP access and over untrusted non-3GPP access. + +The PDU Session Establishment Accept message sent to UE indicates that Non-3GPP path switch is supported for the MA PDU Session. + +4. The UE detects a trusted non-3GPP access network that supports 5G connectivity to the same PLMN. The UE decides to switch the data traffic transferred over the untrusted non-3GPP access of the MA PDU Session to the detected trusted non-3GPP access network. +5. For this purpose, the UE initiates a 5G registration over trusted non-3GPP access and sends a Registration Request to the same AMF. The Registration Request contains a Non-3GPP path switch indication (e.g. either a new registration type = "Non-3GPP path switch" or a registration type = "Initial" plus a new IE), which indicates that the registration over trusted non-3GPP access is required for switching the data traffic of an MA PDU Session to another non-3GPP access path. The Non-3GPP path switch indication indicates to AMF that the existing registration via untrusted non-3GPP access should not be released until the path switch is completed. + +In the "List of PDU Sessions To Be Activated" the UE includes the identity of the established MA PDU Session in order to trigger the establishment of user-plane resources over the trusted non-3GPP access. + +6. Optionally, an authentication procedure may be executed. +7. The normal SMC Request / Response messages are exchanged to setup NAS security between the UE and the AMF over the trusted non-3GPP access. +8. The AMF sends an Initial Context Setup Request to TNGF including the TNGF key, which triggers the establishment of the NWt connection between the UE and the TNGF. +9. Since the UE provided a "List of PDU Sessions To Be Activated" including the identity of the established MA PDU Session, the AMF sends an Update SM Context Request to SMF to initiate the establishment of user-plane resources over the trusted non-3GPP access for this MA PDU Session. The Update SM Context Request contains a Non-3GPP path switch indication which indicates that the requested update is for switching the data traffic of an MA PDU Session to the trusted non-3GPP access and that the SMF shall not release the existing user-plane resources over the untrusted non-3GPP access. These resources are released later, in step 13. +10. The user-plane resources over the trusted non-3GPP access are established. At this point, the MA PDU Session has user-plane resources over the untrusted non-3GPP access path, over the trusted non-3GPP access path, and (optionally) over the 3GPP access path. The SMF initiates an N4 Session Modification procedure with the selected UPF. The UPF may switch the downlink traffic of the MA PDU Session from the untrusted non-3GPP access path to the trusted non-3GPP access path upon receiving updated N4 rules with new AN tunnel info from the SMF. The updated N4 rules indicate the target non-3GPP access to switch traffic. The UE may switch the uplink traffic of the MA PDU Session from the untrusted non-3GPP access path to the trusted non-3GPP access path upon all IPsec Child SAs for the MA PDU Session over trusted non-3GPP access path are established. +11. The AMF updates its UDM registration for non-3GPP access by sending a UECM Registration Request to UDM including RAT type = Trusted WLAN. +12. Based on the current procedures, the UDM accepts the new registration for non-3GPP access and notifies the AMF that the previous registration for non-3GPP access (performed in step 2) is now deregistered. +13. After updating the UDM, the AMF triggers an AN release procedure towards the N3IWF to release the N2 connection and the user-plane resources over the untrusted non-3GPP access. +14. Finally, the registration procedure is completed by sending a Registration Accept message to the UE. When the UE receives the Registration Accept message, it considers that it is deregistered from the untrusted non-3GPP access, and it is registered over the trusted non-3GPP access. + +### 6.17.4 Impacts on Existing Nodes and Functionality + +UE: + +- During the MA PDU Session Establishment, the UE indicates that it supports non-3GPP path switch. +- Performs registration by providing a Non-3GPP path switch indication. This indication can be provided either as a new registration type or as a new IE. + +- Temporarily maintains simultaneous user-plane resources over the untrusted 3GPP access and over the trusted non-3GPP access. +- When the UE receives the Registration Accept message for the new non-3GPP access, the UE considers that it is deregistered from the old non-3GPP access. + +#### AMF: + +- During the Registration procedure, the AMF updates the UDM registration for non-3GPP access after the user-plane resources over the new non-3GPP access are established. +- Indicates to the SMF that the AMF and the UE support non-3GPP path switch during the MA PDU Session Establishment. +- Indicates to SMF that the UE requested non-3GPP path switch during the Registration procedure. +- Performs AN release over old access during the Registration procedure + +#### SMF: + +- Indicates to UE whether the MA PDU Session supports non-3GPP path switch during the MA PDU Session Establishment. + +#### UPF: + +- Temporarily maintains simultaneous user-plane tunnels over untrusted non-3GPP access and over trusted non-3GPP access. + +## 6.18 Solution #3.7: Suspending the Redundancy Steering Mode + +### 6.18.1 Introduction + +Full traffic duplication can be expected to be used as one of the basic configurations of Redundancy Steering Mode (RSM), since it is the easiest one to implement and is applicable to all types of flows. However, full duplication has the highest cost in terms of network resource utilization, and inevitably increases network congestion. When the user plane is becoming congested, blindly using traffic duplication can further increase network congestion. Thus, though an individual UE would expect improved performance, the collective impact of RSM on the overall network performance can be negative. The network should support to enable suspend/reduce the duplication for some time and to some extent. + +### 6.18.2 High-level Description + +The UPF is at the best position to identify the impact of duplication on the system. Thus, when the UPF detects congestion, or when it considers that duplication is not efficient (e.g. since the same packets are being lost on both accesses due to UPF overload, the same performance would be achievable even without duplication), it may override the RSM configuration and can suspend for certain UEs or certain types of SDFs (e.g. for all Non-GBR SDFs) by indicating the access that is suspended for traffic transport. Especially for cases of full duplication, such an adjustment can rapidly address the congestion issue. This adjustment is referred to as Duplication Adjustment operation. + +**Editor's note:** How the UPF decides when to apply Duplication adjustment besides using implementation specific means is FFS. + +When Duplication Adjustment operation is authorized by the PCF in the PCC Rule, the SMF provides an indication for Duplication Adjustment in the ATSSS Rule to the UE, and in the MAR to the UPF. + +Once the need for duplication adjustment is identified, UPF can easily adapt to such a situation by changing itself the duplication in the downlink. Regarding the uplink though, the UE needs to be informed about this necessary adjustment. This information can be provided by the UPF via user plane by extending PMF Protocol with a new message. The new message can be implemented similarly to the UE assistance provided by the UE to the network in UE-assistance operation, with the difference that the network provides the guidance to the UE and that the UE is obliged to follow the provided guidance. + +**Editor's note:** Whether the UPF can only fully suspend duplication or could also indicate the desired percentage of partial duplication as the necessary adjustment is FFS. + +Once the UPF decides to terminate the Duplication Adjustment operation, e.g. when the congestion issue is resolved, the UPF sends a PMF protocol termination message to the UE. + +Remark: Duplication Adjustment can be achieved by updating the ATSSS/N4 rules, but such a solution cannot adapt fast enough to dynamically changing user-plane conditions + +### 6.18.3 Procedures + +Notice that all proposed solutions of KI#3 support full traffic duplication, and hence suspending it temporarily is independent of the exact solution finally adopted for normative work. + +No impact to existing ATSSS procedures has been identified, other than the Access Network Performance Measurements being extended with 2 new messages for suspending and reactivating duplication. + +### 6.18.4 Impacts on Existing Nodes and Functionality + +The ATSSS rules and the N4 rules are enhanced with a new steering mode definition and with new parameters, including the support of traffic duplication suspension. + +#### SMF + +- Based on the PCC rules, create ATSSS rules and N4 rules with the new RSM data including an indication that the UE/UPF is allowed to suspend duplication. + +#### PCF + +- Provide PCC rules considering new RSM including an indication that the UE/UPF is allowed to suspend duplication. + +#### UPF: + +- If an indication that the UPF is allowed to suspend traffic duplication has been received, UPF can adjust traffic duplication and indicate these changes to a UE to apply the same for the uplink. + +#### UE: + +- If an indication that the UPF is allowed to suspend traffic duplication has been received in ATSSS rules, and upon receipt from the UPF duplication updates, the UE applies UPF duplication guidance for the uplink, e.g. suspending duplication on a certain access path. + +# --- 7 Evaluation + +**Editor's note:** This clause provides the evaluation of different solutions. It may contain an evaluation for each Key Issue. + +## 7.1 Evaluation for KI #2: New steering functionalities for non-TCP traffic + +The main classes of solutions related to KI#2 are DCCP-based (#2.1) and QUIC-based (#2.2 and #2.3). Additionally, solution #2.4 complements some of those main solutions with methods to reduce header overhead. + +Both classes of solutions support a "Low-Layer" mode, where the payload of the MA-PDU session is an IP packet or an Ethernet frame. The QUIC-based class of solutions also supports "UDP proxying", where the payload of the MA-PDU session is a UDP payload (#2.2). Solution #2.4 details an aspect of "Low-Layer" solutions, which enables bringing their user plane performance up to par with the "UDP proxying" solution. + +### 7.1.1 User Plane Performance Aspect + +While the main solutions differ from per-packet overhead standpoint, solution #2.4 describes how inner header compression can be used in the tunnel between UE and UPF to limit overhead in some cases (#2.1 and #2.3). The + +estimated per-packet overhead of all 3 solutions (#2.1, #2.2, and #2.3) becomes equivalent to each other if header compression is used with #2.1 and #2.3. + +Solution #2.2 does not require header compression to achieve its low per-packet overhead. RoHC (or EHC) can be implemented with Solutions #2.1 and #2.3 to perform inner header compression in MA-PDU session endpoints (UE and UPF). + +### 7.1.2 Summary of proposed steering functionalities + +For KI#2, three solutions have been proposed: + +- 1) Solution #2.1 (MP-DCCP-LL); +- 2) Solution #2.2 (MPQUIC); and +- 3) Solution #2.3 (MPQUIC-IP). + +Solution #2.1 is based on the DCCP protocol and its multipath extension (draft-ietf-tsvwg-multipath-dccp). This solution supports the transport of UDP flows, IP flows and even Ethernet flows, over DCCP. + +Solutions #2.2 and #2.3 are both based on the QUIC protocol, its multipath extensions (draft-ietf-quic-multipath) and additional extensions defined in IETF for supporting "UDP proxying over HTTP" and "IP proxying over HTTP" respectively (see RFC 9298 and draft-ietf-masque-connect-ip). These solutions support the transport of UDP flows and IP flows respectively, encapsulated in HTTP/3. + +Solution #2.2 supports UDP traffic only, while solution #2.3 supports IP and UDP traffic. Solution #2.1 support IP, UDP and Ethernet traffic. + +#### 7.1.2.1 Co-existence with MPTCP and ATSSS-LL + +All three solutions #2.1, #2.2 and #2.3 are in principle capable to co-exist with MPTCP and ATSSS-LL and can be chosen using the solutions defined N4 and ATSSS rules. + +Solutions #2.1 does not necessarily need any additional steering functionality as it can handle all kinds of traffic. + +### 7.1.3 Evaluation of steering functionalities for UDP traffic flows + +#### 7.1.3.1 General + +For supporting UDP traffic flows, two alternative solutions can be used: Solution #2.1 (MP-DCCP-LL) and Solution #2.2 (MPQUIC). The following sub-clauses discuss different aspects of these solutions. + +The solution #2.3 may also be used for UDP traffic flows but this solution is more suitable when IP traffic flows (other than UDP) should be supported, thus, it should be considered separately. + +#### 7.1.3.2 Allocation of UPF resources + +As specified in clause 6.3.5, the MP-DCCP-LL solution requires the UPF to allocate: one IP address and two ports (one per access type) per MP-DCCP connection, as shown in the figure below. The UPF allocates the IP addresses and ports for each MP-DCCP connection based on information received from SMF (MP-DCCP-LL Control Information), which indicates how many MP-DCCP connections are required. The SMF derives this information based on the PCC rules received from PCF. If additional MP-DCCP connections are required during the lifetime of the MA PDU Session, the SMF should ask UPF to allocate more resources for these additional connections and then send a PDU Session Modification message to UE including the allocated UPF resources. + +![Figure 7.1.3.2-1 (a) shows the architecture for MP-DCCP. On the left, the UE contains an MP-DCCP Tunnel Client, an MP-DCCP layer, and an IP layer. It has two link-specific addresses: one for 3GPP and one for non-3GPP. On the right, the UPF contains an MP-DCCP Tunnel Server, an MP-DCCP layer, and an IP layer, with a link-specific address for 3GPP. Four arrows represent MP-DCCP connections: #1 (path over 3GPP), #1 (path over non-3GPP), #2 (path over 3GPP), and #2 (path over non-3GPP). A note indicates 'One port per MP-DCCP connection and per access' for both client and server.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Figure 7.1.3.2-1 (a) shows the architecture for MP-DCCP. On the left, the UE contains an MP-DCCP Tunnel Client, an MP-DCCP layer, and an IP layer. It has two link-specific addresses: one for 3GPP and one for non-3GPP. On the right, the UPF contains an MP-DCCP Tunnel Server, an MP-DCCP layer, and an IP layer, with a link-specific address for 3GPP. Four arrows represent MP-DCCP connections: #1 (path over 3GPP), #1 (path over non-3GPP), #2 (path over 3GPP), and #2 (path over non-3GPP). A note indicates 'One port per MP-DCCP connection and per access' for both client and server. + +Figure 7.1.3.2-1 (a) + +On the contrary, the MPQUIC solution requires the allocation of one IP address and one UDP port at the UPF, which are used for *all* MPQUIC connections of a UE. This is possible because the QUIC protocol can multiplex many connections on the same UDP port (using the "connection ID" parameter). The UE receives the IP address and UDP port at the UPF as part of the "proxy information" in the PDU Session Establishment Accept (exactly the same as in MP-TCP). When the UE needs to establish a new MPQUIC connection to UPF, the UE applies the received "proxy information" and does not require additional resources to be allocated at the UPF. + +![Figure 7.1.3.2-1 (b) shows the architecture for MP-QUIC. On the left, the UE contains an MP-QUIC layer, a UDP layer, and an IP layer. It has two link-specific addresses: one for 3GPP and one for non-3GPP. It also has two UDP ports: port #1 for MP-QUIC connection #1 and port #2 for MP-QUIC connection #2. On the right, the UPF contains an MP-QUIC layer, a UDP layer, and an IP layer. It has a single IP address and a single UDP port for all MP-QUIC connections. Four arrows represent MP-QUIC connections: #1 (path over 3GPP), #1 (path over non-3GPP), #2 (path over 3GPP), and #2 (path over non-3GPP).](2fc2e531b3b3c695cca497516ec79f20_img.jpg) + +Figure 7.1.3.2-1 (b) shows the architecture for MP-QUIC. On the left, the UE contains an MP-QUIC layer, a UDP layer, and an IP layer. It has two link-specific addresses: one for 3GPP and one for non-3GPP. It also has two UDP ports: port #1 for MP-QUIC connection #1 and port #2 for MP-QUIC connection #2. On the right, the UPF contains an MP-QUIC layer, a UDP layer, and an IP layer. It has a single IP address and a single UDP port for all MP-QUIC connections. Four arrows represent MP-QUIC connections: #1 (path over 3GPP), #1 (path over non-3GPP), #2 (path over 3GPP), and #2 (path over non-3GPP). + +Figure 7.1.3.2-1 (b) + +#### 7.1.3.3 Connections between UE and UPF + +The MPQUIC solution requires one MPQUIC connection per QoS flow (see clause 6.11.2). Each UDP flow transferred via an MPQUIC connection is associated with a unique QUIC stream on the connection and each QUIC stream is configured to apply a steering mode. Thus, different steering modes can be applied per MPQUIC connection. + +The MP-DCCP-LL requires one connection per QoS flow and per Steering Mode (see clause 6.3.2), so it needs much more connections than MPQUIC. The MP-DCCP-LL connection management (adding / removing connections) is cumbersome: Every time a new UDP flow should be transmitted using a steering mode for which no MP-DCCP connection supports, a new MP-DCCP connection should be established and the SMF should send a PDU Session Modification message with the parameters (UPF address/ports) for this MP-DCCP connection. + +The MP-DCCP-LL solution specifies that the UE receives "MP-DCCP Connection Setup Information", which indicates the QoS flow and the steering mode associated with each MP-DCCP connection. However, it does not specify how the UPF knows the QoS flow and the steering mode associated with each MP-DCCP connection. Without such information, the UPF cannot determine the MP-DCCP connection that should be used for each DL packet. In the MPQUIC solution, the QoS flow associated with an MPQUIC connection is indicated (as a new transport parameter) during the connection setup. + +When the UE creates a "derived" QoS rule (see TS 23.501 [2]), the MP-DCCP-LL solution does not specify how an MP-DCCP connection can be created to carry the traffic that matches this QoS rule. In case of the MPQUIC solution, when a "derived" QoS rule is created, the UE establishes a new MPQUIC connection and indicates to UPF the QFI associated with this connection (using a new QUIC transport parameter). + +#### 7.1.3.4 Application visibility + +In some cases, it is beneficial that an application can provide information to the underlying steering functionality, e.g. via an enhanced sockets API, such as, when an application implements itself the QUIC protocol and use it for reliable transport (using QUIC Streams). In this case, it could inform the underlying steering functionality that it should apply unreliable transport (e.g. using QUIC Datagrams) to avoid meltdown effects. + +The MPQUIC steering functionality is a high-layer functionality implemented higher in the protocol stack and can support interactions with the apps, e.g. via an enhanced sockets API (which is outside the scope of this study). + +#### 7.1.3.5 User-plane overhead + +Both the MP-DCCP-LL and the MPQUIC send Ack packets to acknowledge successful reception. + +As shown in figure below, when two (or more) app payloads are provided to the MPQUIC steering functionality, these payloads can be multiplexed in the same QUIC packet, thus, reducing the user-plane overhead (this is a feature supported by QUIC). In addition, a single UDP datagram can multiplex multiple QUIC packets, which can further reduce the overhead. + +NOTE: As a consequence of RFC 9000 [6] the precondition for possible multiplexing of payload packets is that those payload packets fit completely inside a single QUIC packet, which is limited by the maximum MTU size. + +In case of MP-DCCP-LL, each app payload will be encapsulated into two IP (inner) packets and will be transmitted with two DCCP-Data packets. However, inner header compression (IHC) can be applied by MP-DCCP-LL to reduce the overhead. + +![Diagram comparing MP-DCCP-LL and MPQUIC protocol stacks. The left side shows MP-DCCP-LL where app payloads are encapsulated in separate inner IP packets, then DCCP packets, then outer IP packets, and finally UDP. The right side shows MPQUIC where app payloads are multiplexed into a single QUIC packet, which is then encapsulated in a UDP datagram. The diagram includes layers for Apps, UDP, IP (inner/outer), MP-DCCP-LL steering functionality, and MPQUIC steering functionality, leading to 3GPP and Non-3GPP networks.](7cf88df393f1fd5cfac780bf07368c58_img.jpg) + +The diagram illustrates two protocol stack configurations for handling multiple application payloads (App payload-1 and App payload-2). + +**Left Stack (MP-DCCP-LL):** At the top, two boxes represent 'Apps' providing 'App payload-2' and 'App payload-1'. These are encapsulated into separate 'IP (inner)' packets. Each 'IP (inner)' packet is then encapsulated into an 'MP-DCCP-LL steering functionality' block (highlighted in yellow). This is followed by an 'IP (outer)' packet, then a 'UDP' layer, and finally the traffic is split into '3GPP' and 'Non-3GPP' network paths. Below the stack, two rows show the packet structure: [App payload-1 | UDP | IP (inner) | MP-DCCP | IP (outer) | 3GPP/ non-3GPP] and [App payload-2 | UDP | IP (inner) | MP-DCCP | IP (outer) | 3GPP/ non-3GPP]. + +**Right Stack (MPQUIC):** At the top, two boxes represent 'Apps' providing 'App payload-2' and 'App payload-1'. These are encapsulated into a single 'MPQUIC steering functionality' block (highlighted in yellow), which is part of a 'Higher-layer'. Below this is a 'UDP' layer, then an 'IP' layer, and finally the traffic is split into '3GPP' and 'Non-3GPP' network paths. Below the stack, a single row shows the packet structure: [Datagram Frame containing HTTP Datagram with App payload-2 | Datagram Frame containing HTTP Datagram with App payload-1 | QUIC | UDP | IP | 3GPP/ non-3GPP]. + +Diagram comparing MP-DCCP-LL and MPQUIC protocol stacks. The left side shows MP-DCCP-LL where app payloads are encapsulated in separate inner IP packets, then DCCP packets, then outer IP packets, and finally UDP. The right side shows MPQUIC where app payloads are multiplexed into a single QUIC packet, which is then encapsulated in a UDP datagram. The diagram includes layers for Apps, UDP, IP (inner/outer), MP-DCCP-LL steering functionality, and MPQUIC steering functionality, leading to 3GPP and Non-3GPP networks. + +Figure 7.1.3.5-1 + +The table below provides an estimate of the size of the additional headers for the solutions #2.1 and #2.2. Note that the exact estimation of the size of the additional headers depends on the implementation (e.g. how a QUIC implementation selects the size of the stream identity) and it is difficult to be calculated. Therefore, the table below provides + +approximate numbers based on some assumptions. One assumption is that the link-specific multipath IP addresses in the UE and UPF are IPv4. + +**Table 7.1.3.5-1** + +| Solution | Size of additional headers [Bytes] | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Solution #2.2 / Datagram mode 1 |

Size of additional headers = IPv4 header (20) + UDP header (8) + QUIC short header (5) + QUIC Datagram header (6) = 39 bytes

The QUIC short header size depends on the length of the Destination Connection ID (0-160 bits) and the length of the Packet Number (8-32 bits). It is assumed that 16 bits are enough for each field.

The QUIC Datagram header contains:
Type: 1 byte
Length: Variable-length integer specifying the length of the Datagram Data field in bytes. It is assumed 2 bytes are enough.
Quarter Stream Id: Variable-length integer. It is assumed that 2 bytes are enough to support 65536 active streams on an MPQUIC connection.
Context Id: 1 byte
Sequence number: 2 bytes (assumed to be enough)

| +| Solution #2.2 / Datagram mode 2 | As Datagram mode 1 but without the sequence number (i.e. minus 2 bytes). | +| Solution #2.2 / Stream mode |

Size of additional headers = IPv4 header (20) + UDP header (8) + QUIC short header (5) + QUIC Stream header (3) + Datagram Capsule (5) = 41 bytes

The QUIC Stream header contains:
Type: 1 byte
Stream Id: Assume 2 bytes are enough to contain all stream ids in each MPQUIC connection
Offset: Optional, variable length
Length: Optional, variable length

The Datagram Capsule contains:
Type: 1 byte
Length: Variable-length integer. It is assumed that 2 bytes are enough.
Quarter Stream Id: Variable-length integer. It is assumed that 2 bytes are enough to support 65536 active streams on an MPQUIC connection.

| +| Solution #2.1 / Inner IP = IPv4 (i.e. PDU session type = IPv4) |

Depending on short/long DCCP header and the type of delay information exchange for reordering:
55 bytes + 20 bytes for the outer IPv4 header for short header and DCCP timestamp option.
65 bytes + 20 bytes for the outer IPv4 header for long header and MP_RTT option.

| +| Solution #2.1 / Inner IP = IPv6 (i.e. PDU session type = IPv6) |

Depending on short/long DCCP header and the type of delay information exchange for reordering:
75 bytes + 20 bytes for the outer IPv4 header, for short header and DCCP timestamp option.
85 bytes + 20 bytes for the outer IPv4 header, for long header and MP_RTT option.

| + +#### 7.1.3.6 Data encryption aspects + +As specified in RFC 9001 (Using TLS to Secure QUIC), each QUIC connection is established using TLS v1.3 handshake and all QUIC packets are encrypted, and integrity protected using the negotiated TLS keys and algorithms. However, in case of ATSSS\_ph3, where QUIC is applied between the UE and UPF and where access-level security mechanisms are used to protect the user-plane traffic, the additional security mechanism in the QUIC layer is unnecessary. The MPQUIC solution contains the following EN, so this issue is expected to be addressed by SA WG3. + +**Editor's note:** Whether and how encryption in the QUIC layer can be omitted is FFS and need to be verified by SA WG3. The impact due to encryption regarding overhead and performance is FFS. + +It is noted that RFC 9150 "TLS 1.3 Authentication and Integrity-Only Cipher Suites" defines cipher suites which "provide server authentication and data authenticity, but not data confidentiality." + +The double-layer encryption is not an issue for MP-DCCP-LL, which relies on existing access-level security mechanisms to protect the user-plane traffic. However, the security aspects of MP-DCCP-LL will also have to be studied in SA WG3 (as needed for every solution). + +![Figure 7.1.3.6-1: Protocol stack diagram showing the flow of data between UE and UPF. The diagram illustrates the layers involved in MP-QUIC steering, transport level security (TLS v1.3), and access level security across 3GPP and Non-3GPP interfaces.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +The diagram illustrates the protocol stack for data transmission between a User Equipment (UE) and a User Plane Function (UPF). At the top, the UE contains 'Apps' which connect to an 'MP-QUIC steering functionality' block. This block is part of a 'Transport level security (TLS v1.3)' layer. Below this is a 'UDP' layer, followed by an 'IP' layer. The IP layer connects to two interface options: '3GPP' and 'Non-3GPP'. These interfaces are part of an 'Access Level security' layer. The same protocol stack (MP-QUIC steering functionality, UDP, IP) is shown on the UPF side, also connected to '3GPP' and 'Non-3GPP' interfaces within an 'Access Level security' layer. + +Figure 7.1.3.6-1: Protocol stack diagram showing the flow of data between UE and UPF. The diagram illustrates the layers involved in MP-QUIC steering, transport level security (TLS v1.3), and access level security across 3GPP and Non-3GPP interfaces. + +Figure 7.1.3.6-1 + +#### 7.1.3.7 Packet reordering and deduplication + +Both MP-DCCP-LL and MPQUIC solutions provide the means to support packet reordering and deduplication. + +The MP-DCCP-LL solution mentions that "MP-DCCP protocol itself does not specify re-ordering mechanisms but provides path sequencing (DCCP packet sequencing [11]), connection sequencing (MP\_SEQ option [12]), and has inherent latency (MP\_RTT option [12]) or timing (DCCP timestamp option[11]) information exchange, i.e. all properties that are necessary for the packet receiving side, i.e. UE or UPF, to be able to implement re-ordering properly." Although the MP-DCCP draft [12] states that "The details of the transmission scheduling mechanism and optional reordering mechanism are up to the sender and receiver, respectively, and are outside the scope of the MP-DCCP protocol," it is understood that such mechanisms can be considered and possibly defined in stage 3. + +The MPQUIC solution can readily support reordering and deduplication by leveraging the existing QUIC stream mechanisms, which are applied in the Stream transport mode. So, when the UDP traffic can be transferred in Stream transport mode, no additional mechanisms need to be specified for supporting packet reordering and deduplication. + +In addition, the MPQUIC solution support Datagram mode 1 (see clause 6.11.3), which supports unreliable transport and inserts sequence numbers in every UDP data packet. In Datagram mode 1, every UDP packet is encapsulated into a QUIC Datagram frame, which also carries a Context ID and a sequence number. The definition of this Context ID, as well as other aspects of Datagram mode 1 (e.g. reordering mechanisms), will be considered in stage 3. + +#### 7.1.3.8 IETF Support + +The QUIC multipath draft is planned to be published as a Standards Track RFC, while the DCCP multipath draft is planned to be published as an Experimental RFC. + +As specified in RFC 2026: + +"Specifications that are not on the standards track are labelled with one of three "off-track" maturity levels: "Experimental", "Informational", or "Historic". The documents bearing these labels are not Internet Standards in any sense." + +NOTE: The TCP converter used by the MPTCP proxy is based on the Experimental RFC 8803. + +## 7.2 Evaluation for KI #3: Support of redundant traffic steering + +### 7.2.1 Considerations on RSM with Duplication Criteria + +In order to support redundant traffic steering, there are solution #3.1, 3.2, 3.3, 3.4, 3.5 and 3.6 proposed to define the Redundant Steering Mode (RSM). If this new steering mode is applied by UE and UPF, the traffic is transmitted via 3GPP and non-3GPP accesses in a redundant way. + +Considering redundant transmission is costly, which consumes at maximum double resources compared with normal transmission without duplication, duplication criteria may be defined to indicate when RSM should be initiated. In other words, predefined conditions or criteria, as proposed by quite a few solutions, such as solution 3.1, 3.2, 3.3 and 3.4, can be defined as trigger points for initiating redundant transmission. The duplication criteria may not always be needed as, in some cases, applications may always require redundant transmission without criteria for activation / deactivation. + +One of the major benefits of redundant transmission is to reduce packet loss rate, therefore Packet loss rate should be taken as one of the criteria. Except packet loss rate, other criteria proposed by solution 3.3 and / or solution 3.4 to trigger redundant transmission, include Round Trip Time (RTT), jitter, percentage of duplicated traffic and load on an access network. + +Another benefit of redundant transmission is to reduce the RTT. If the RTT via both accesses cannot satisfy the traffic requirement, the redundant transmission can reduce the RTT because the receiver always selects the packet that arrives faster. Note that if the RTT over 3GPP access is smaller than the RTT over non-3GPP access, this does not mean that all packets arrive faster via 3GPP access. Some percentage of packets will arrive faster via non-3GPP and since the receiver always selects the packet that arrives first, this means that the RTT due to redundant transmission will be smaller than the RTT over 3GPP access and than the RTT over non-3GPP access. However, if both accesses exceed the threshold, but the RTT differs a lot between the two accesses, duplication will not help much. A few packets may arrive earlier via the slow access (depending on the jitter) but the max delay may not decrease in any significant way. Redundant steering based on RTT threshold may thus not be better than using Lowest-Delay steering mode but consumes more resources. + +**Editor's note:** Evaluation of the duplication factor is FFS. + +### 7.2.2 Considerations on RSM without Duplication Criteria + +Some of the solutions (#3.3 and #3.4) propose that the core network can decide how much of the traffic is duplicated on either of the accesses and provides this information in ATSSS rules to the UE and in the MAR rules to the UPF without indicating any duplication criteria. The amount of traffic that is duplicated on the secondary access is defined by a duplication factor between 0% and 100%. This can be used to limit the number of duplicated packets to the ones seen as important for UE and UPF. + +**Editor's note:** Evaluation of the duplication factor is FFS. + +### 7.2.3 Considerations on RSM suspension + +Whereas Duplication Criteria control the activation of duplication based on the state of each of the available accesses, the overall network situation is not considered by any of the traffic duplication solutions. Thus, it can happen that the network is congested and activating traffic duplication even worsens this situation. This issue would be amplified if only full duplication is applied. Solution #3.7 proposes to temporarily suspend the use of duplication, whenever it is beneficial for the overall network performance, e.g. due to UPF congestion. Although this can be performed by updating ATSSS and N4 rules, such a pure control-plane solution would be slow and not flexible enough, as it requires the coordination of several network entities. Instead, the UPF can react immediately, and user-plane suspension can be implemented by extensions of the PMF protocol as per solution #3.7. + +## 7.3 Evaluation for KI #5: Switching traffic of an MA PDU Session between two non-3GPP access paths + +There are two categories of solutions for KI#5, called Option 1 and Option 2: + +- Option 1: Switching the data traffic after the Registration procedure (Solution #5.1, #5.3 and #5.4): + +- These solutions propose to perform the Registration procedure over the new non-3GPP access first and after the procedure is finished, the UE adds a new leg to the existing MA PDU Session by re-using existing access addition procedure. After the access addition is completed, the network performs access release / deregistration over the old non-3GPP access. + +The main impact of these solutions is maintaining two simultaneous registrations over two non-3GPP accesses. There may exist undisclosed impacts to the system as the overall solution describes only access switching aspects and other procedures are not investigated in detail. + +In solution #5.1, #5.3 there is impact to the UE, AMF, SMF, UPF and UDM. In solution #5.4, there is no clear description that there is impact to the UDM. However, it seems that the UDM needs to maintain two simultaneous registration states so there is impact to the UDM. + +- Option 2: Switching the data traffic during the Registration procedure (Solution #5.2, #5.5 and #5.6): + - These solutions propose to perform access switching during the Registration procedure over the new non-3GPP access, i.e. there is no need to trigger additional procedure for access switching after the Registration procedure. + +In these solutions, there is no need to maintain simultaneous registration over two non-3GPP accesses. This enables to perform access switching by registering over the new non-3GPP access without need to trigger another session related procedure to add additional access to the existing MA PDU Session. + +In solution #5.2 and #5.6, there is impact to the UE, AMF, SMF, UPF while in solution #5.5 there is additional impact to the UDM. + +Several aspects of Option 1 and Option 2 are considered below. + +### **Path switching (PS) capability indication:** + +For option 1: + +- UE capability indication - since the traffic switching is initiated by UE, the UE shall be able to support traffic switching. Limiting UE's path switching capability by include indication in its subscription is not necessary since there is no capability indication in subscription for path switching within 3GPP accesses. +- Network capability indication - an indication is sent to the UE before switching traffic in order to prevent the UE from initiating the path switching when the AMF/SMF does not support it. + +### **Path switching (PS) indication:** + +For option 1: + +- AMF needs to be informed that this registration via target non-3GPP access is intended for switching the traffic between two non-3GPP access paths. It is used by the AMF to maintain temporary dual-registration via two non-3GPP accesses during the PS procedure. This indication is necessary to allow the AMF to distinguish the scenario where the registration shall be immediately replaced, or temporary registration is maintained for 2 N3GPP accesses. +- SMF needs to be informed that this PDU session establishment request via non-3GPP access is intended for switching the traffic between two non-3GPP access paths. in order to allow the SMF to establish new UP resources on the target access while existing UP resources in source non-3GPP access are preserved. +- Considering that these two indicators are both necessary and they are only applicable for non-3GPP traffic switching, it is preferable to define only 1 indicator (information element) which is used by both AMF and SMF. + +For option 2: + +- In this option the UE register for the purpose of traffic switching. When the AMF receives the path switching indication from UE, it shall update the SM context of UE in order to trigger the user-plane resources establishment. The registration results would also indicate whether the path switching between two non-3GPP accesses is success or not. Therefore, from the point of view of the whole procedure, the definition of a new registration type is preferred for option 2. + +### **List of PDU session indication:** + +For option 1: + +- Since UE performs PDU session establishment after the end of registration procedure, the UE can indicate the list of PDU session that wants to move in PDU session establishment and therefore it is not necessary to include list of PDU session in Registration Request procedures. + +For option 2: + +- List of PDU session is already supported in the Registration message. It can be used for SMF to distinguish which PDU session the UE is requesting to move, thus it is necessary. + +### **Deregistration timer:** + +For option 1: + +- The AMF needs to determine the maximum time for maintaining the UE registered via two non-3GPP access in order to allow the UE to perform the establishment of PDU session on target non-3GPP access, but to avoid also to keep for a long time the two registrations, for example when the UE does not establish PDU session on target access for some unexpected reason. The usage of a timer is not necessary for SMF. + +For option 2: + +- It is not required since PS is completed during registration. + +### **Maintenance of N2 sessions** + +For option 1: + +- The UE registers in new non-3GPP access while the UE is still registered in the old non-3GPP access. The AMF maintains two non-3GPP access registrations (and possibly a 3GPP access registration) while a PDU Session Establishment procedure is performed. The AMF thus needs to maintain two non-3GPP N2 sessions across several procedures. + +For option 2: + +- The path switch takes place during a single procedure (Registration). In order to allow the old user plane to be available while the new user plane is being established, the AMF can establish a N2 session in new non-3GPP access before releasing the N2 session in old non-3GPP access. The AMF thus needs to maintain two non-3GPP N2 sessions within the Registration procedure. Alternatively, the AMF can release the old N2 session before establishing the new N2 session, and in that case, AMF always has only a single N2 session for non-3GPP access. + +### **ATSSS rules update:** + +- When UE completes user-plane resources establishment on target non-3GPP access, two non-3GPP access paths can be available before that the user-plane resource of source non-3GPP access would be released. If UE has UL traffic to be transmitted, the UE may select either the target or the source non-3GPP access. + +For option 1: + +- If source non-3GPP access is selected, the service over non-3GPP access would be interrupted when user-plane resource of source non-3GPP access is released afterward. Enhancements on ATSSS rule with indication of the RAT type (Trusted or Untrusted N3GPP) to be used would solve the issue and improve the service continuity. Thus, updated ATSSS rule with the indication of RAT-type to be used is required. + +For option 2: + +- The UE switches the UL to the new non-3GPP access when the new non-3GPP access user plane connectivity is available. There is no need to modify the ATSSS rules due to the path switch. + +#### **N4 rules update:** + +- Since the AN tunnel info changes after switching which is allocated by the target N3GPP access node (e.g. N3IWF or TNGF), the N4 rules including the target AN tunnel info need to be updated to UPF. + +#### **PS for SA PDU session:** + +For option 1 & 2: + +- All existing solutions can support PS for single access PDU session between Trusted and Untrusted network, i.e. with change of RAT type. + +#### PS for same RAT type: + +For option 1 & 2: + +- The Trusted and Untrusted N3GPP access mandates the support of MOBIKE (RFC 4555 [35]) which enables the mobility of one peer end points (but not of both end point at the same time). For example, in TS 23502 [3] for Trusted N3GPP is defined the following: +- *"In step 13c, the TNGF provides to UE (a) an "inner" IP address, (b) a NAS IP\_ADDRESS and a TCP port number and (c) a DSCP value. After this step, an IPsec SA is established between the UE and TNGF. This is referred to as the "signalling IPsec SA" and operates in Tunnel mode. Operation in Tunnel mode enables the use of MOBIKE [40] for re-establishing the IPsec SAs when the IP address of the UE changes during mobility events. All IP packets exchanged between the UE and TNGF via the "signalling IPsec SA" shall be marked with the above DSCP value. The UE and the TNAP may map the DSCP value to a QoS level (e.g. to an EDCA Access Class [48]) supported by the underlying non-3GPP Access Network. The mapping of a DSCP value to a QoS level of the non-3GPP Access Network is outside the scope of 3GPP* +- Therefore, mobility of UE between different access network without changing of anchor Access node, as shown in figure 1, is currently supported. +- The mobility of UE between the same access network type (RAT-type) with changing of anchor Access node, as shown in figure 2, is not supported by MOBIKE (see RFC 4555 [35]) hence it would be good if the solution selected for support PS for SA PDU session between Trusted and Untrusted N3GPP access supports to the scenario of PS for SA PDU session without changing of RAT type. + +![Figure 7.3-1: Mobility of UE between 2 N3GPP access networks without changing of access node. The diagram shows a UE moving from IP1 to IP2 within the N3GPP2 Untrusted network. The UE is connected to a TNGF (N3IWF) which is the source. The UE's IP address changes from IP1 to IP2, but the TNGF remains the same.](0e252770f8f0573617e0112b36a93d2f_img.jpg) + +The diagram illustrates the mobility of a User Equipment (UE) between two N3GPP access networks without changing the access node. At the top, a UE with IP1 is connected to a TNGF (N3IWF) via a dashed red line labeled 'source'. Below, the UE is shown with IP2, labeled 'Target', within an oval representing the 'N3GPP2 Untrusted' network. A green curved arrow indicates the movement of the UE from IP1 to IP2, while the TNGF remains the same. + +Figure 7.3-1: Mobility of UE between 2 N3GPP access networks without changing of access node. The diagram shows a UE moving from IP1 to IP2 within the N3GPP2 Untrusted network. The UE is connected to a TNGF (N3IWF) which is the source. The UE's IP address changes from IP1 to IP2, but the TNGF remains the same. + +Figure 7.3-1: Mobility of UE between 2 N3GPP access networks without changing of access node + +![Figure 7.3-2: Mobility of UE between 2 N3GPP access networks with changing of AN node (e.g. N3IWF). The diagram shows a UE moving from N3GPP1 Untrusted (connected to N3IWF#1) to N3GPP2 Untrusted (connected to N3IWF#2) over time. The UE's IP address changes from IP1 to IP2, and the access node (N3IWF) also changes.](88066268366ca160709e20f13ed8f356_img.jpg) + +The diagram illustrates the mobility of a UE between two N3GPP access networks with a change of access node (AN). At Time=T0, the UE is in the 'N3GPP1 Untrusted' network, connected to 'N3IWF#1' (source). At Time=T1, after a time interval Δt, the UE has moved to the 'N3GPP2 Untrusted' network and is connected to 'N3IWF#2' (Target). The UE's IP address changes from IP1 to IP2, and the access node changes from N3IWF#1 to N3IWF#2. + +Figure 7.3-2: Mobility of UE between 2 N3GPP access networks with changing of AN node (e.g. N3IWF). The diagram shows a UE moving from N3GPP1 Untrusted (connected to N3IWF#1) to N3GPP2 Untrusted (connected to N3IWF#2) over time. The UE's IP address changes from IP1 to IP2, and the access node (N3IWF) also changes. + +Figure 7.3-2: Mobility of UE between 2 N3GPP access networks with changing of AN node (e.g. N3IWF) + +The following table lists evaluation aspects of existing proposed solutions. + +Table 7.3-1: Evaluation aspects of solutions + +| Sol | Handover Procedure | Capability Indication | Handover Indicator | List of PDU Session | ATSSS Rules Update | SA PDU Session Support | Deregistration Timer | +|------|--------------------|---------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------------------------|------------------------|-------------------------| +| #5.1 | Separate, option 1 | Not mentioned | IE Indicator for both AMF and SMF | Included in PDU session establishment procedure | Required to indicate target N3GPP access | Yes | Applied for AMF | +| #5.2 | Combined, option 2 | Include both UE and network capability indication | New Registration Type for AMF and IE indicator for SMF | Included in Registration Request procedure | Not mentioned | Yes | Not needed | +| #5.3 | Separate, option 1 | Include only AMF capability indication | New Registration Type for AMF and IE indicator for SMF | Included in PDU session establishment procedure | Not mentioned | Yes | Applied for AMF | +| #5.4 | Separate, option 1 | Include only UE capability indication | IE Indicator for both AMF and SMF | Included in both Registration Request procedure and PDU session establishment procedure | Not mentioned | Yes | Applied for AMF and SMF | +| #5.5 | Combined, option 2 | Include both UE and network capability indication | New Registration Type for AMF and IE indicator for SMF | Included in Registration Request procedure | Not mentioned | Yes | Not needed | +| #5.6 | Combined, option 2 | Include both UE and network capability indication | IE Indicator for both AMF and SMF | Included in Registration Request procedure | Not Mention | Yes | Not needed | + +Additional evaluation aspects for the KI#5 solutions are considered below. In particular, the following key aspects are considered: + +- New registration type = "non-3GPP path switch" or registration type = "initial" + new IE or registration type = "mobility" + new IE. +- Capability exchange between UE and network: + - 5G Session Management (5GSM) capability exchange. + - 5G Mobility Management (5GMM) capability exchange. +- PDU Session Establishment in the new non-3GPP access without requiring UE initiated PDU Session Establishment/Modification signalling. +- AMF update of RAT Type in UDM after user plane resources establishment in the new non-3GPP access. +- Timer related to de-registration of new non-3GPP access. +- Impacts on existing Nodes and Functionality. + +Tables 7.3-2 & 7.3-3 compare several key aspects where they differ or are align. + +Table 7.3-2: Comparison of Solutions to Evaluation Items + +| Solution # & Title | New Registration Type or New IE for Path Switch Indication | Capability exchange between UE & network (5GSM or 5GMM layer) | PDU Session Establishment in the new N3GPP access without requiring UE initiated PDU Session Establishment/Modification signalling | UDM subscription needed for ATSSS path switching | AMF update of RAT Type in UDM after User Plane Resources establishment in the new N3GPP Access | Timer for de-registration of new N3GPP Access | +|-------------------------------------------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|------------------------------------------------------------------------------------------------|-----------------------------------------------| +| #5.1: Support traffic switching between two non-3GPP paths | New Registration Type | No | No | No | No | Yes (AMF) | +| #5.2: Delaying UDM Registration until non-3GPP access switching completes | New Registration Type | Yes (5GSM) | Yes | No | Yes | No | +| #5.3: Path switching between non-3GPP accesses | Either | Yes (5GMM) | No | No | Yes | Yes (AMF) | +| #5.4: Non-3GPP access path switching in MA PDU Session | New IE | Yes (5GMM) | No | No | Yes | Yes (AMF & SMF) | +| #5.5: Non-3GPP path switch during Registration in new non-3GPP access | Either (Editor's Note) | Yes (5GSM) (Editor's Note) | Yes | No | Yes | No | +| #5.6: Consolidated solution for traffic switching between two non-3GPP access paths | Either | Yes (5GSM) | Yes | No | Yes | No | + +Table 7.3-3: Comparison of Solutions to Impacts on existing Nodes and Functionality + +| Solution # & Title | Impacts on Existing Nodes & Functionality | | | | | +|-------------------------------------------------------------------------------------|-------------------------------------------|-----|-----|-----|-----| +| | UE | AMF | SMF | UPF | UDM | +| #5.1: Support traffic switching between two non-3GPP paths | Yes | Yes | Yes | Yes | Yes | +| #5.2: Delaying UDM Registration until non-3GPP access switching completes | Yes | Yes | Yes | Yes | No | +| #5.3: Path switching between non-3GPP accesses | Yes | Yes | Yes | Yes | Yes | +| #5.4: Non-3GPP access path switching in MA PDU Session | Yes | Yes | Yes | Yes | Yes | +| #5.5: Non-3GPP path switch during Registration in new non-3GPP access | Yes | Yes | Yes | Yes | Yes | +| #5.6: Consolidated solution for traffic switching between two non-3GPP access paths | Yes | Yes | Yes | Yes | No | + +## 7.4 Evaluation for KI #6: Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC + +Solution #6.1 addresses KI#6 to support the non-3GPP access leg of MA-PDU Session with PDN connection in EPC. This solution also supports the mobility procedure from 5GS to EPS. It applies the similar mechanism as the solution + +for MA-PDU session with one leg via non-3GPP access to 5GC and one leg via 3GPP access to EPC, as defined in Rel-17, with a bit impact on the ePDG and PGW-C+SMF to support APCO IE to transport the ATSSS related parameters. + +# 8 Conclusions + +**Editor's note:** This clause enlists the conclusions of the study, including agreements for work to be done in the normative phase. + +## 8.1 Conclusions for KI #2: New steering functionalities for non-TCP traffic + +It is concluded that: + +- a) For supporting multipath transport of UDP flows between the UE and UPF, a high-layer steering functionality will be specified during the normative phase, which will be based on solution #2.2: "MPQUIC steering functionality using UDP proxying over HTTP". + - The specified high-layer steering functionality shall be able to support all ATSSS steering modes (i.e. the redundant steering mode and all other steering modes defined in Rel-17). + +NOTE 1: When the PCF selects a steering mode for a UDP flow and this steering mode is supported by ATSSS-LL (e.g. Active-Standby), the PCF can select to use the MPQUIC steering functionality if additional features, which are not supported by the ATSSS-LL steering functionality and PMF, are required for the traffic steering/switching/splitting of the UDP flow. + +NOTE 2: SA WG3 can study security optimizations that can improve the user-plane performance, such as whether the encryption in the QUIC layer can be omitted. + +## 8.2 Conclusions for KI #3: Support of redundant traffic steering + +A Redundant Steering Mode (RSM) shall be defined in the normative phase, which supports the following features: + +- 1) The PCF decides the SDF(s) for which RSM should be applied based on its own criteria and/or based on information received from AFs. +- 2) Duplication criteria may be provided by PCF for an SDF using a non-GBR QoS flow. Duplication criteria shall not be provided for SDFs using GBR QoS flows. +- 3) When duplication criteria are not provided for an SDF, then RSM operates in static mode. In this mode: + - The network may provide a Primary Access to instruct the UE/UPF that the UE/UPF shall send all data packets of the SDF on the Primary Access and may duplicate data packets of the SDF on the other, secondary access. How many and what data packets are duplicated on the secondary access is chosen by the UE and UPF based on their implementation. The primary access is selected by the PCF. + - If the network does not provide Primary Access to UE/UPF, the UE/UPF shall send all data packets of the SDF on both accesses. + +An example of ATSSS rule using RSM is static mode is shown below: + +- Traffic descriptor + - Application identity: com.example.app0 + - Protocol: TCP +- Access Selection descriptor + - Steering functionality: MPTCP + - Steering mode: Redundant + +This means that: + +- Redundant traffic steering is applied by the MPTCP steering functionality to the TCP traffic of application "com.example.app0". +- 100% of the traffic is duplicated over both accesses. + +4) When duplication criteria are provided for an SDF, then RSM operates in dynamic mode. In this mode: + +- When the duplication criteria are fulfilled on both accesses, the UE/UPF shall duplicate the traffic of the SDF on both accesses. +- When the duplication criteria are fulfilled on one access only, the UE/UPF shall send the traffic of the SDF over the other access only. +- When the duplication criteria are not fulfilled on both accesses, the UE/UPF shall send the traffic of the SDF over the "primary" access. The "primary" access may be selected by PCF and indicated to UE and UPF in ATSSS and N4 rules or may be selected by UE/UPF based on their own implementation (e.g. using the best performing access). If the measurements are not available to evaluate the duplication criteria for an access, it is assumed that the duplication criteria are not fulfilled on this access. If the duplication criteria are fulfilled again over one access the UE/UPF should deactivate the RSM. The UE/UPF sends the traffic of the SDF over the access only. + +NOTE 1: For example, the duplication criterion "Max PLR = 0.1%" is fulfilled on one access when the measured PLR on this access exceeds the 0.1% threshold. + +5) The duplication criteria contain either threshold values for Packet Loss Rate (PLR) or threshold values for Round Trip Time (RTT). + +- When only a PLR threshold is provided for an SDF and the measured PLR exceeds this threshold on both accesses, the UE/UPF shall duplicate the traffic of the SDF on both accesses. +- When only a RTT threshold is provided for an SDF and the measured RTT exceeds this threshold on both accesses, the UE and UPF decide independently to initiate packet duplication or not based on their own implementation. + +NOTE 2: For example, the UE/UPF can decide to initiate packet duplication only when the values of jitter on each access and the difference of values of RTT indicate that the packet duplication is expected to reduce the overall RTT for the SDF. + +6) The existing structure of ATSSS/N4 rules shall be re-used with enhancements for supporting RSM. An example of an ATSSS rule using dynamic RSM is shown below. + +- Traffic descriptor + - Application identity: com.example.app1 + - Protocol: TCP +- Access Selection descriptor + - Steering functionality: MPTCP + - Steering mode: Redundant + - Steering Mode Information: Primary access=3GPP + - Threshold Values: Max PLR = 0.1% + +This ATSSS rule indicates that: + +- Redundant traffic steering shall apply to the TCP traffic of application "com.example.app1". +- If the measured PLR exceeds 0.1% on both accesses (duplication criteria fulfilled on both accesses), then all matched traffic shall be duplicated on both accesses. +- If the measured PLR does not exceed 0.1% on both accesses, then all matched traffic shall be sent over 3GPP access only (as the primary access). + +- If the measured PLR does not exceed 0.1% on one access only (either 3GPP or non-3GPP), then all matched traffic shall be sent over this access. +- 7) The redundant traffic steering shall be applicable to both GBR and non-GBR traffic. For GBR traffic, the SMF shall provide the GBR QoS profile to both accesses. +- 8) The Nnef\_AFsessionWithQoS API can be used by an AF to indicate the desired packet delay and/or packet loss rate for a data flow. This information can be considered by PCF when deciding the steering mode for this data flow and may influence when traffic duplication is activated or deactivated. +- 9) The RSM does not apply to the ATSSS-LL steering functionality. +- 10) UPF can suspend traffic duplication for a UE, e.g. in case of locally detected UPF congestion, via an extension of the PMF protocol. How UPF determines to suspend traffic duplication or reactivate duplication is implementation specific. It is up to UPF to decide for which UEs and/or types of SDFs (e.g. all non-GBR SDFs) traffic duplication is suspended. UPF can at any time decide to terminate duplication suspension for one or several UEs via the PMF protocol. + +**Editor's note:** Additional bullets may be added before the completion of this study. It should also be defined how the steering functionality handles the duplicated packets. + +## 8.3 Conclusions for KI #5: Switching traffic of an MA PDU Session between two non-3GPP access paths + +The solution to be specified in the normative phase shall support the following principles: + +- 1) The path switching between non-3GPP accesses is performed during the Registration procedure. The UE sends a Registration Request message with the Registration type value set to "Mobility Registration Update" and optionally a new parameter indicating "Non-3GPP path switching" via the target non-3GPP access network and also requests user-plane establishment using the "PDU Sessions to be activated" parameter. There are two options for non-3GPP path switching as follows: + - Non-3GPP path switching without releasing AN resources over old non-3GPP access during switching procedure. In this option, user plane resources of old non-3GPP access is kept until user plane resources are established over the new non-3GPP access. The details are described in bullet 6.A. + - Non-3GPP path switching with releasing AN resources over old non-3GPP access during switching procedure. In this option, user plane resources of the old non-3GPP access is released first and then user plane resources are established over the new non-3GPP access. The details are described in bullet 6.B. + - The UE does not perform non-3GPP path switching if the PLMN of the selected target non-3GPP AN is different from the PLMN of the source non-3GPP AN. +- 2) The AMF updates the registration for non-3GPP access in UDM after the data traffic is switched to the new access via Nudm\_UECM\_Registration. +- 3) Path switching between any two non-3GPP accesses except wireline shall be supported, (i.e. trusted to trusted, trusted to untrusted, untrusted to trusted, or untrusted to untrusted). +- 4) Capability exchange between UE and network shall be performed. + - If the AMF supports non-3GPP path switching, the AMF indicates whether the AMF supports non-3GPP switching to the UE during the Registration procedure. + - During the MA PDU Session establishment, the UE indicates whether the UE supports non-3GPP path switching to the AMF. + - If the AMF supports non-3GPP path switching, the AMF selects the SMF that supports non-3GPP path switching and indicates whether the UE supports non-3GPP path switching to the SMF when the AMF sends PDU Session Establishment Request message. + - If the AMF and SMF support non-3GPP path switching, the SMF indicates whether the network supports non-3GPP path switching in the PDU Session Establishment Accept message. + +- 5) When the UE performs non-3GPP path switching, the UE includes the identity of the established MA PDU Session in the "List of PDU Sessions To Be Activated". + +NOTE 1: Whether the UE can also indicate SA PDU Session in the "List of PDU Sessions To Be Activated" will be determined during the normative phase. This enables SA PDU Sessions to be moved between non-3GPP accesses. + +- 6) When non-3GPP path switching is performed: + +- The UE can perform non-3GPP path switching when it receives capability indication during the Registration procedure. +- A. For non-3GPP path switching without releasing AN resources over old non-3GPP access during switching procedure + - The UE performs mobility registration procedure including "Non-3GPP path switching" indication in case the UE supports to maintain the old non-3GPP access while performing Registration over the new non-3GPP access. + - If the UE cannot maintain connection over old non-3GPP access while performing Registration over the new non-3GPP access, the UE does not provide the Non-3GPP path switching" indication. This case is described in bullet 6.B. + - If the AMF receives Registration Request message with "Non-3GPP path switching" indication, and the AMF supports to maintain the old non-3GPP N2 connection while establishing the new non-3GPP N2 connection, the AMF does not trigger AN release procedure over old non-3GPP access and includes "Non-3GPP path switching" indication in Nsmf\_PDUSession\_UpdateSMContext request. If the SMF receives this indication, the SMF does not release the existing user-plane resources of old non-3GPP access. + - The UE and UPF start to send traffic over the new non-3GPP access when user plane resources are established over new non-3GPP access. No need to enhance ATSSS rule and N4 rule to support non-3GPP path switching. + - The AMF updates UDM and triggers AN release procedure over the old non-3GPP access. + - The AMF provides Registration Accept to the UE. +- B. For non-3GPP path switching with releasing AN resources over old non-3GPP access during switching procedure + - The UE performs mobility registration procedure without including "Non-3GPP path switching" indication. + - If the AMF receives Registration Request message without "Non-3GPP path switching" indication, the AMF triggers AN release procedure over old non-3GPP access before notifying SMF about the user plane activation in new non-3GPP access. + - The UE and UPF start to send traffic over the new non-3GPP access when user plane resources are established over new non-3GPP access. No need to enhance ATSSS rule and N4 rule to support non-3GPP path switching. + - The AMF updates UDM and provides Registration Accept to the UE. + - If the AMF receives Registration Request message with "Non-3GPP path switching" indication, and the AMF does not support to maintain the old non-3GPP N2 connection while establishing the new non-3GPP N2 connection, the AMF triggers the AN release procedure, before triggering activation of the new N2 connection. During the AN release procedure, the AMF may notify SMF before sending the N2 release request to old non-3GPP AN. + +NOTE 2: The non-3GPP access switching is intended to be the switch between two different RAT-types, i.e. from Trusted N3GPP access to untrusted N3GPP access and vice versa, or the scenario of UE simultaneously moving of both IPsec peers in the same RAT-type (i.e. UE local IP address and the anchor N3IWF/TNGF change) or the scenario of changing to different N3IWF/TNGF without changing UE local IP address, since the scenario of UE moving without changing the N3GPP access node anchor is supported based on RFC 4555 MOBIKE support by IKEv2 from Rel-15. + +## 8.4 Conclusions for KI #6: Supporting MA PDU Session with one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC + +Solution #6.1 is concluded as baseline for normative work. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|----------|----------------------------|----|-----|-----|---------------------------------------------------------------------------------|------------------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149E | S2-2200755 | - | - | - | Skeleton | 0.0.0 | +| 2022-09 | SA#97-e | SP-220824 | - | - | - | MCC editorial update for presentation to TSG SA for information | 1.0.0 | +| 2022-11 | SA#98-e | SP-221113 | - | - | - | MCC editorial update for presentation to TSG SA for approval | 2.0.0 | +| 2022-12 | SA#98-e | - | - | - | - | MCC editorial update for publication after approval at TSG SA#98-e (Release 18) | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-55/raw.md b/raw/rel-18/23_series/23700-55/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7e29b4ccebabd9e71ae9875e7ed51531a97e8ad9 --- /dev/null +++ b/raw/rel-18/23_series/23700-55/raw.md @@ -0,0 +1,1384 @@ + + +# 3GPP TR 23.700-55 V18.0.0 (2022-12) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced Application Architecture for UAS applications; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' in black with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller black text to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps, black font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles – Sophia Antipolis +Valbonne – FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 +Intpp.org + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 8 | +| 4 Key issues ..... | 8 | +| 4.1 Key issue #1: Direct communication between UAVs..... | 8 | +| 4.2 Key issue #2: Support for multi-USS deployments ..... | 8 | +| 4.3 Key issue #3: Coordination between Uu and PC5 for direct UAV-to-UAV or UAV-to-UAV-C communication ..... | 9 | +| 4.4 Key issue #4: Support for detect and avoid services and applications..... | 9 | +| 5 Architecture requirements..... | 9 | +| 5.1 General ..... | 9 | +| 5.2 Support for multi-USS deployments ..... | 9 | +| 5.2.1 Description ..... | 9 | +| 5.2.2 Requirements..... | 9 | +| 5.3 Support for C2 direct mode feasibility reporting ..... | 10 | +| 5.3.1 Description ..... | 10 | +| 5.3.2 Requirements..... | 10 | +| 5.4 Support for detect and avoid services and applications ..... | 10 | +| 5.4.1 Description ..... | 10 | +| 5.4.2 Requirements..... | 10 | +| 6 Architecture..... | 10 | +| 6.1 General ..... | 10 | +| 6.2 Architecture enhancement..... | 11 | +| 7 Solutions..... | 11 | +| 7.1 General ..... | 11 | +| 7.2 Mapping of solutions to key issues ..... | 11 | +| 7.3 Solution #1: Change of USS during flight ..... | 11 | +| 7.3.1 Architecture enhancements..... | 11 | +| 7.3.2 Solution description..... | 12 | +| 7.3.2.1 General..... | 12 | +| 7.3.2.2 Registration of multi-USS capabilities ..... | 12 | +| 7.3.2.3 Provision of multi-USS capabilities ..... | 12 | +| 7.3.2.3.1 Multi-USS management..... | 12 | +| 7.3.2.3.2 Multi-USS configuration..... | 13 | +| 7.3.2.4 UAE layer assisted change of USS..... | 14 | +| 7.3.3 Solution evaluation ..... | 15 | +| 7.4 Solution #2: Support for USS re-mapping for a UAS..... | 15 | +| 7.4.1 Architecture enhancements..... | 15 | +| 7.4.2 Solution description..... | 15 | +| 7.4.2.1 General..... | 15 | +| 7.4.2.2 Procedure ..... | 16 | +| 7.4.3 Solution evaluation ..... | 18 | +| 7.5 Solution #3: Support for C2 direct mode feasibility reporting..... | 18 | +| 7.5.1 Architecture enhancements..... | 18 | +| 7.5.2 Solution description..... | 18 | +| 7.5.2.1 General..... | 18 | +| 7.5.2.2 Procedure ..... | 19 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------|-----------| +| 7.5.3 | Solution evaluation ..... | 19 | +| 7.6 | Solution #4: UAE layer support for DAA ..... | 20 | +| 7.6.1 | Architecture enhancements..... | 20 | +| 7.6.2 | Solution description..... | 20 | +| 7.6.2.1 | General ..... | 20 | +| 7.6.2.2 | Registration of DAA capability ..... | 20 | +| 7.6.2.3 | Provision of DAA policies..... | 21 | +| 7.6.2.3.1 | DAA support management procedure..... | 21 | +| 7.6.2.3.2 | DAA support configuration procedure..... | 22 | +| 7.6.2.4 | UAE layer support for DAA applications..... | 22 | +| 7.6.2.4.1 | Client initiated DAA support ..... | 22 | +| 7.6.2.4.2 | Server initiated DAA support..... | 23 | +| 7.6.3 | Solution evaluation ..... | 24 | +| 7.7 | Solution #5: Support for DAA applications ..... | 24 | +| 7.7.1 | Architecture enhancements..... | 24 | +| 7.7.2 | Solution description..... | 24 | +| 7.7.2.1 | General ..... | 24 | +| 7.7.2.2 | Enhanced real-time tracking of location information of UAVs to USS ..... | 24 | +| 7.7.2.3 | Tracking dynamic UAVs in an application defined area relative to a host UAV ..... | 25 | +| 7.7.2.3.1 | General ..... | 25 | +| 7.7.2.3.2 | Subscription for host UAV dynamic information ..... | 25 | +| 7.7.2.3.3 | Management of dynamic UE location based group ..... | 26 | +| 7.7.2.3.4 | Obtaining dynamic information of the UEs in proximity range ..... | 27 | +| 7.7.2.3.4.1 | Subscription procedure within UAS operator ..... | 27 | +| 7.7.2.3.4.2 | Subscription procedure across UAS operators ..... | 27 | +| 7.7.2.3.5 | Notification procedure..... | 28 | +| 7.7.2.3.6 | Notification of host UAV dynamic information ..... | 29 | +| 7.7.3 | Solution evaluation ..... | 29 | +| 8 | Deployment scenarios ..... | 29 | +| 8.1 | General ..... | 29 | +| 9 | Overall evaluation ..... | 29 | +| 9.1 | Architecture enhancements ..... | 29 | +| 9.2 | Key issue evaluations ..... | 29 | +| 9.2.1 | General ..... | 29 | +| 9.2.2 | Evaluation of key issue #1: Direct communication between UAVs ..... | 30 | +| 9.2.3 | Evaluation of key issue #2: Support for multi-USS deployments..... | 30 | +| 9.2.4 | Evaluation of key issue #3: Coordination between Uu and PC5 for direct UAV-to-UAV or UAV-to-UAV-C communication..... | 31 | +| 9.2.5 | Evaluation of key issue #4: Support for detect and avoid services and applications ..... | 32 | +| 10 | Conclusions ..... | 32 | +| 10.1 | Architecture enhancements ..... | 32 | +| 10.2 | Solutions..... | 33 | +| Annex A (informative): | Change history..... | 34 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions “shall” and “shall not” are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions “must” and “must not” are not used as substitutes for “shall” and “shall not”. Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- Should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction “may not” is ambiguous and is not used in normative elements. The unambiguous constructions “might not” or “shall not” are used instead, depending upon the meaning intended. + +- Can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions “can” and “cannot” are not substitutes for “may” and “need Not”. + +- Will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions “is” and “is not” do not indicate requirements. + +# --- Introduction + +As part of Rel-17, 3GPP TS 23.255 [3] specified the overall application layer architecture to enable application support for UAS applications over 3GPP networks, generic support for UAS applications were specified in the SEAL layer as outlined in 3GPP TS 22.434 [5], while general UAS-related aspects for the 3GPP-architecture were specified in 3GPP TS 23.256 [4]. + +In Rel-18, the UAS application layer architecture requires enhancements to further improve and enhance functionality in 3GPP for improved support assisting the aviation industry. + +# --- 1 Scope + +The present document analyze requirements and identify key issues and develop potential enhancements to the UAS application architecture. The study includes identification of potential enhancements to the UAS architecture, potential enhancements to the Service Enabler Architecture Layer (SEAL) and corresponding application requirements. + +The study bases its work on the existing stage 1 work within 3GPP related to UAS as specified in 3GPP TS 22.125 [2]. + +The conclusions of the study will be aligned with 3GPP TR 23.700-58 [6]. The recommendations from the study include solutions for the UAS architecture and SEAL that will be considered for normative work. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”. +- [2] 3GPP TS 22.125: “Uncrewed Aerial System (UAS) support in 3GPP”. +- [3] 3GPP TS 23.255: “Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows”. +- [4] 3GPP TS 23.256: “Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2”. +- [5] 3GPP TS 23.434: “Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows”. +- [6] 3GPP TR 23.700-58: “Study of further architecture enhancements for uncrewed aerial systems and urban air mobility”. +- [7] 3GPP TS 23.304: “Proximity based Services (ProSe) in the 5G System (5GS)”. +- [8] 3GPP TS 23.502: “Procedures for the 5G System (5GS)”. +- [9] 3GPP TS 23.303: “Proximity-based services (ProSe); Stage 2”. + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Symbols + +No symbols are introduced in this Technical Report. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|------------------------------------| +| DAA | Detect And Avoid | +| DN | Data Network | +| EDN | Edge Data Network | +| LUN | Local USS Network | +| SEAL | Service Enabler Architecture Layer | +| UAE | UAS Application Enabler | +| UAS | Uncrewed Aerial System | +| UAV | Uncrewed Aerial Vehicle | +| UAV-C | Uncrewed Aerial Vehicle-Controller | +| USS | UAS Service Supplier | +| UTM | UAS Traffic Management | + +# --- 4 Key issues + +## 4.1 Key issue #1: Direct communication between UAVs + +In the current version of 3GPP TS 23.255 [3], the UAVs (UAV – UAV and UAV – UAV-C) communicate over Unicast Uu. Communication over a direct link between the UAVs can improve performance and connectivity. Enhanced PC5 is the expected solution for direct communication between UAVs. + +Solutions for direct communication between UAVs is based on and must be coordinated with the work outlined by 3GPP TR 23.700-58 [6]. + +It is required to study the following: + +- How the UAE layer can be enhanced to support usage of direct communication between UAVs. +- Whether and how the UAE layer functionality related to C2 communication support can be enhanced if PC5 is used for direct communication. + +## 4.2 Key issue #2: Support for multi-USS deployments + +In the current version of 3GPP TS 23.255 [3], it is assumed that the UE communicate with a single USS/UTM during a flight. However, it is not unlikely that a single flight can span the service area of more than one USS/UTM. + +In some scenarios, a UAS can be served by more than one USS, or by more USSs in a USS network. A USS network can be considered a set of connected USSs for exchanging information and sharing relevant details to ensure shared situational awareness for UTM participants. USSs could have several geographic areas and times for which they are providing services. + +It must be secured that change of USS/UTM during an ongoing session (flight) is supported by the UAE layer. In multi-USS scenarios, each USS can also be located in different clouds and potentially deployed at the edge. + +Solutions for UAE layer support for UAS operation in multi-USS deployments must be coordinated with the work outlined by 3GPP TR 23.700-58 [6]. + +The key issue will investigate: + +- Whether and how the UAE layer can be enhanced to support change of USS/UTM during flight. +- Whether and how the UAE layer needs to be enhanced to assist the traffic steering of UAS application traffic to different DN/EDN to avoid application service disruption while in-flight. + +NOTE: Liability/legal responsibility for UAV operation stays with UTM/UAS operator. + +## 4.3 Key issue #3: Coordination between Uu and PC5 for direct UAV-to-UAV or UAV-to-UAV-C communication + +In the current version of 3GPP TS 23.255 [3], the UAVs (UAV – UAV and UAV – UAV-C) can communicate over Unicast Uu interface. Besides this, ProSe/PC5 Communication over a direct link mentioned in 3GPP TS 23.304 [7] can also be a solution for communications between UAVs. Communication over Uu and PC5 can be used in parallel between UAVs for redundancy or for different kinds of service scenarios. In some cases, the UAV needs to distinguish which traffic use which kind of interface. In addition, the mechanisms for communications between UAVs using multicast/broadcast Uu and ProSe/PC5 scenarios need further study. + +Solutions for coordination between Uu and PC5 is based on and must be coordinated with the work outlined by 3GPP TR 23.700-58 [6]. + +Therefore, it is required to study the following: + +- How the UAE layer can be enhanced to make coordination between network based communication (Uu) and direct communication (PC5) for communications between UAVs or between UAV and UAV-C. + +## 4.4 Key issue #4: Support for detect and avoid services and applications + +Development of the Support for Detect and Avoid Mechanism in 3GPP system is being studied in 3GPP TR 23.700-58 [6]. The 5GC enhancement work for DAA includes services for network assisted DAA and direct DAA via PC5. + +Considering the stage 1 requirements and also 5GC enhancements for DAA, it is required to study the aspects that UAE layer and SEAL can be supported for DAA. + +Further study is also required for UAE layer to support DAA scenarios where UAVs belong to multiple PLMNs. + +It is required to study the following: + +- Whether and how the UAE layer and/or SEAL services can be enhanced to support DAA services and applications for collision avoidance considering the Stage 1 requirements. +- How the UAE layer can support DAA scenarios where UAVs belong to multiple PLMNs. + +NOTE: Solutions for DAA will be coordinated with the conclusions of the work outlined by 3GPP TR 23.700-58 [6] and based on requirements for DAA specified in 3GPP TS 22.125 [2]. + +# --- 5 Architecture requirements + +## 5.1 General + +This clause specifies all requirements related to enhanced application architecture for UAS applications. + +## 5.2 Support for multi-USS deployments + +### 5.2.1 Description + +This clause specifies the requirements related to support for multi-USS deployments. + +### 5.2.2 Requirements + +[AR-5.2.2-a] The UAE Server shall provide a mechanism for configuring of multi-USS capabilities from the USS. + +[AR-5.2.2-b] The UAE Server shall provide a mechanism for configuring the multi-USS capabilities at the UAE Client (UAV). + +[AR-5.2.2-c] The UAV Server shall provide a mechanism to support change of USS during UAS operations. + +[AR-5.2.2-d] The UAE Client (UAV) shall provide a mechanism to support change of USS based on the multi-USS capabilities when an immediate change of USS is needed. + +NOTE: The details of multi-USS capabilities will be specified during the normative work. + +## 5.3 Support for C2 direct mode feasibility reporting + +### 5.3.1 Description + +This clause specifies the requirements related to support for C2 direct mode feasibility reporting. + +### 5.3.2 Requirements + +[AR-5.3.2-a] The UAE Server shall provide a mechanism for monitoring the feasibility of ProSe/PC5 link for C2 communications. + +[AR-5.3.2-b] The UAE Client shall be capable of reporting the feasibility of ProSe/PC5 link for C2 communications. + +## 5.4 Support for detect and avoid services and applications + +### 5.4.1 Description + +This clause specifies the requirements related to support for detect and avoid services and applications. + +### 5.4.2 Requirements + +[AR-5.4.2-a] The UAE Server shall provide a mechanism for configuring of DAA capabilities from the USS. + +[AR-5.4.2-b] The UAE Server shall provide a mechanism for configuring the DAA capabilities at the UAE Client (UAV). + +[AR-5.4.2-c] The UAS application enabler layer shall provide a mechanism for a UAS application specific server to obtain events for a UAV that can be relevant for DAA. + +[AR-5.4.2-d] The UAS application enabler layer shall provide a mechanism for a UAS application specific client to obtain events for a UAV that can be relevant for DAA. + +# --- 6 Architecture + +## 6.1 General + +Figure 6.1-1 illustrates the detailed UAS application layer functional model as outlined in 3GPP TS 23.255 [2]. + +![Figure 6.1-1: UAS application layer functional model. This diagram illustrates the functional architecture of the UAS application layer, organized into three horizontal layers: UAS application specific layer, UAE layer, and SEAL. On the left, two UAS UE (UAV-C or UAV) blocks are shown, each containing a 'UAS application specific client' and a 'UAE client'. These clients connect to 'SEAL clients'. On the right, a 'UAS application server' contains a 'UAS application specific server' and a 'UAE server', which in turn connects to 'SEAL servers'. A central '3GPP network system' block contains interfaces Nnef, T8, MB2-U, xMB-U, MB2-C/xMB-C, Rx, and T8. Various interfaces are labeled: U2-APP, U1-APP, U2-AE, U1-AE, U5, Uc, SEAL-C, SEAL-PCS, SEAL-UU, SEAL-S, and UAE-E. Dashed lines separate the functional layers and the UAS UE blocks.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 6.1-1: UAS application layer functional model. This diagram illustrates the functional architecture of the UAS application layer, organized into three horizontal layers: UAS application specific layer, UAE layer, and SEAL. On the left, two UAS UE (UAV-C or UAV) blocks are shown, each containing a 'UAS application specific client' and a 'UAE client'. These clients connect to 'SEAL clients'. On the right, a 'UAS application server' contains a 'UAS application specific server' and a 'UAE server', which in turn connects to 'SEAL servers'. A central '3GPP network system' block contains interfaces Nnef, T8, MB2-U, xMB-U, MB2-C/xMB-C, Rx, and T8. Various interfaces are labeled: U2-APP, U1-APP, U2-AE, U1-AE, U5, Uc, SEAL-C, SEAL-PCS, SEAL-UU, SEAL-S, and UAE-E. Dashed lines separate the functional layers and the UAS UE blocks. + +Figure 6.1-1: UAS application layer functional model + +## 6.2 Architecture enhancement + +No enhancement to the Release 17 architecture is identified. + +# 7 Solutions + +## 7.1 General + +The proposed solutions in this clause attempt to resolve all, or part of one or more Key Issues provided in clause 4. As part of the proposed solution, the proposed solution is also evaluated against the key issue(s) it attempts to resolve. + +## 7.2 Mapping of solutions to key issues + +Table 7.2-1 Mapping of solutions to key issues + +| | KI #1 | KI #2 | KI #3 | KI #4 | +|--------|-------|-------|-------|-------| +| Sol #1 | | X | | | +| Sol #2 | | X | | | +| Sol #3 | X | | X | | +| Sol #4 | | | | X | +| Sol #5 | | | | X | + +## 7.3 Solution #1: Change of USS during flight + +### 7.3.1 Architecture enhancements + +None. + +### 7.3.2 Solution description + +#### 7.3.2.1 General + +This solution aims to address the gaps identified in Key Issue #2 “Support for multi-USS deployments”. + +The solution covers registration of the UAE clients and the UAE servers multi-USS capabilities to the USS, provision of the capabilities and policies of the USS to the UAE client and the UAE server, and assistance by the UAE layer at change of USS. + +The functions of the USS are out of scope of the solution. + +#### 7.3.2.2 Registration of multi-USS capabilities + +Pre-conditions: + +- The UAE client has discovered the UAE server and is aware of the address of the UAE server (e.g., FQDN). + +NOTE: How the UAE client is provisioned with the UAE server information is outside the scope of the current document. + +- The UAV has already been assigned with the UAV ID. + +![Sequence diagram showing the registration of multi-USS capabilities between a UAE client and a UAE server.](0019f09403376d6444ee323591fa2e98_img.jpg) + +``` +sequenceDiagram + participant UAE client + participant UAE server + Note right of UAE server: 2. Authentication and authorization check + UAE client->>UAE server: 1. Registration request + UAE server-->>UAE client: 3. Registration response +``` + +The diagram illustrates a sequence of three messages between a UAE client and a UAE server. The UAE client sends a '1. Registration request' to the UAE server. The UAE server then performs an '2. Authentication and authorization check', indicated by a box on its lifeline. Finally, the UAE server sends a '3. Registration response' back to the UAE client. + +Sequence diagram showing the registration of multi-USS capabilities between a UAE client and a UAE server. + +**Figure 7.3.2.2-1: Registration of multi-USS capabilities of UAE client and UAE server** + +1. The UAE client sends a registration request to the UAE server. The UAE client includes its Multi-USS capabilities. +2. The UAE server performs authentication and authorization check (e.g., based on pre-provisioned security information or by interacting with UAS application specific server (e.g., USS/UTM)). +3. The UAE server sends a registration response to the UAE client indicating success or failure of the registration. + +#### 7.3.2.3 Provision of multi-USS capabilities + +##### 7.3.2.3.1 Multi-USS management + +Figure 7.3.2.3.1-1 illustrates the procedure where the UAE server receives an application request for managing the multi-USS capabilities from the UAS application specific server. + +Pre-condition: + +- The UAV has received its UAS ID from the UAS application specific server. +- The UAV has performed the UAS UE registration procedure. + +![Sequence diagram illustrating the Multi-USS management procedure. The diagram shows four steps: 1. Multi-USS management request from UAS application specific server to UAE server; 2. Multi-USS management response from UAE server to UAS application specific server; 3. Multi-USS configuration (internal step for UAE server); 4. Multi-USS management complete from UAE server to UAS application specific server.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant UAS_app_server as UAS application specific server + participant UAE_server as UAE server + Note left of UAE_server: 3. Multi-USS configuration + UAS_app_server->>UAE_server: 1. Multi-USS management request + UAE_server-->>UAS_app_server: 2. Multi-USS management response + Note right of UAE_server: 4. Multi-USS management complete + +``` + +Sequence diagram illustrating the Multi-USS management procedure. The diagram shows four steps: 1. Multi-USS management request from UAS application specific server to UAE server; 2. Multi-USS management response from UAE server to UAS application specific server; 3. Multi-USS configuration (internal step for UAE server); 4. Multi-USS management complete from UAE server to UAS application specific server. + +**Figure 7.3.2.3.1-1: Multi-USS management procedure** + +1. The UAS application specific server sends to the UAE server a Multi-USS management request with the USS policies. The UAE server receives a Multi-USS management request from a serving USS for managing the support for multi-USS. The request includes the UAV (UAE client) identification information and Multi-USS configuration parameters. The configuration includes: list of allowed USSes information (e.g. FQDN), current serving USS information, USS-change-initiation information (whether the UAE layer can initiate change of USS), a Multi-USS support policy (when/how to initiate a change of USS). The UAE server stores the Multi-USS support configuration parameters in the UAE client context. In the case of removal of Multi-USS configuration parameters for a USS from the UAE server, then the request shall include the UAV identifier and a USS identifier (e.g. FQDN) for the USS that will be removed. +2. The UAE server sends to the UAS application specific server a Multi-USS management response with a positive or negative acknowledgement of the request. +3. UAE server executes the multi-USS configuration according to clause 7.3.2.3.2. +4. After successful execution of USS management configuration, the UAE server notifies the UAS application specific server with a Multi-USS management complete based on the configured capabilities of the UAE client and the UAE server. + +##### 7.3.2.3.2 Multi-USS configuration + +This procedure enables the configuration of the UAE client, based on a request from UAS application specific server (which can be the USS/UTM) to configure multi-USS capabilities to the UAE client. + +Figure 7.3.2.3.2-1 illustrates the USS management configuration procedure. + +Pre-conditions: + +1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4]. +2. UAE server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server. +3. UAE server has performed the initiation of USS management capabilities as in clause 7.3.2.2.2. + +![Sequence diagram for Multi-USS configuration procedure. Lifelines: UAE client (UAV), 5GC, and UAE server. The sequence is: 1. Multi-USS Configuration request from UAE server to UAE client; 2. Store or remove Multi-USS configuration parameters (internal to UAE client); 3. Multi-USS Configuration response from UAE client to UAE server.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant UAE server + participant 5GC + participant UAV as UAE client (UAV) + Note left of UAV: 2. Store or remove Multi-USS configuration parameters + UAE server->>UAV: 1. Multi-USS Configuration request + UAV-->>UAE server: 3. Multi-USS Configuration response + +``` + +Sequence diagram for Multi-USS configuration procedure. Lifelines: UAE client (UAV), 5GC, and UAE server. The sequence is: 1. Multi-USS Configuration request from UAE server to UAE client; 2. Store or remove Multi-USS configuration parameters (internal to UAE client); 3. Multi-USS Configuration response from UAE client to UAE server. + +**Figure 7.3.2.3.2-1: Multi-USS configuration procedure** + +1. The UAE server sends a Multi-USS configuration request to the UAE client. The UAE client receives a Multi-USS configuration request from the UAE server that includes the Multi-USS configuration parameters. In the case of removal of Multi-USS configuration parameters for a USS from the UAE client, then the request shall only include a USS identifier (e.g. FQDN) for the USS that will be removed. + +NOTE: Further details on the elements and other procedures of multi-USS configuration will be specified during the normative work in stage 2 and stage 3. + +2. The UAE client stores or removes the Multi-USS configuration parameters as per the information received in step 1. +3. The UAE client sends a Multi-USS configuration response to the UAE server. + +#### 7.3.2.4 UAE layer assisted change of USS + +Figure 7.3.2.4-1 illustrates the procedure where the UAE server initiates change of USS. + +Change of DN/EDN to avoid disruption while in flight due to change of USS is not covered by this solution. + +Pre-conditions: + +1. UAE client and UAE server have indicated Multi-USS support. +2. UAS application specific server has provided Multi-USS capabilities and policies to the UAE client and the UAE server. + +![Sequence diagram for UAE layer assisted change of USS. Lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence is: 1. USS change request from UAS application specific server to UAE server; 2. USS change request from UAE server to UAE client; 3. Perform change of USS (internal to UAE client); 4. USS change response/notification from UAE client to UAE server; 5. USS change response/notification from UAE server to UAS application specific server.](e190b6ddb7c2e64b940749a1c5612256_img.jpg) + +``` + +sequenceDiagram + participant UAS application specific server + participant UAE server + participant UAV as UAE client (UAV) + Note left of UAV: 3. Perform change of USS + UAS application specific server-->>UAE server: 1. USS change request + UAE server->>UAV: 2. USS change request + UAV-->>UAE server: 4. USS change response/notification + UAE server-->>UAS application specific server: 5. USS change response/notification + +``` + +Sequence diagram for UAE layer assisted change of USS. Lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence is: 1. USS change request from UAS application specific server to UAE server; 2. USS change request from UAE server to UAE client; 3. Perform change of USS (internal to UAE client); 4. USS change response/notification from UAE client to UAE server; 5. USS change response/notification from UAE server to UAS application specific server. + +**Figure 7.3.2.4-1: UAE layer assisted change of USS** + +1. The UAE server receives a USS change request from a UAS application specific server. The request includes the UAV (UAE client) identification information, a new serving USS information and USS change authorization + +information (e.g. authorization token), USS change constraints parameters (e.g. delay or geo location/area threshold for change). The UAE server verifies that the request is authorized (e.g., Multi-USS capability is enabled, new USS part of the allowed USS list). + +Alternatively, the UAE server initiates the change of USS (i.e. on behalf of the USS) based on USS provided Multi-USS configuration parameters (e.g. USS-change-initiation parameter, Multi-USS support policy). If the UAE server is allowed to initiate a change of USS according to the Multi-USS configuration, the UAE server may select a new USS from the allowed USS list for the UAE client to connect to without reception of an USS change request from the UAS application specific server. + +2. The UAE server sends a USS change request to the UAE client including the new serving USS information. The UAE client initiates the communication with the new serving USS based on the USS change request and Multi-USS configuration parameters. + +3. Perform change of USS. + +If an emergency change of USS is deemed necessary by the UAE Client (e.g. sudden loss of contact with the serving USS), the UAE client initiates the change of USS (i.e. on behalf of the USS) based on USS provided Multi-USS configuration parameters. In this case, the steps 1-2 are not performed. + +4. The UAE client sends a USS change response/notification message indicating that a change of USS has been performed. + +5. The UAE server sends a USS change response/notification to the UAS application specific server indicating that a change of USS has been performed. + +### 7.3.3 Solution evaluation + +Key Issue #2 outlines the following to be investigated further with respect to the impact on the application layer functional model for UAS: + +- a) Whether and how the UAE layer can be enhanced to support change of USS/UTM during flight. +- b) Whether and how the UAE layer needs to be enhanced to assist the traffic steering of UAS application traffic to different DN/EDN to avoid application service disruption while in-flight. + +This solution fully addresses the bullet a) in Key Issue #2: + +A summary of the UAE layer capabilities are: + +- 1) UAE server and UAE client provide support for application specific layer message exchanges related to change of USS/UTM during flight. +- 2) UAE client change USS/UTM during flight as per Multi-USS configuration parameters. + +NOTE: Change of DN/EDN to avoid disruption while in flight due to change of USS is not covered by this solution. + +The solution enables the USS/UTM to take or give back control of the change of USS/UTM from/to the UAE server and/or the UAE client at any time. + +## 7.4 Solution #2: Support for USS re-mapping for a UAS + +### 7.4.1 Architecture enhancements + +None. + +### 7.4.2 Solution description + +#### 7.4.2.1 General + +This solution aims to address one of the gaps identified in Key Issue #2 “Support for multi-USS deployments”. + +The solution covers the assistance by the UAE layer at change of USS based on partially overlapping multi-USS deployments, based on UAV location tracking. UAE layer assists on the mapping and traffic steering of UAS traffic to different DNAI based on the deployment of the USSs in different edge/cloud networks. + +In multi-USS scenarios, each USS can be physically located in different clouds, and it is also possible that a USS is deployed at the edge. In such multi-USS/LUN scenarios, the interaction with the communication network for supporting a UAS session which requires the interaction to more than one USS e.g. due to UAV mobility to different geographical area covered by different edge cloud, needs to be specified. + +One example is shown below, where USSs are deployed in different edges/clouds and are clustered in different LUNs. In these cases, the interaction with 5GS can be via different DNAIs, and the UAV/UAV-C can be travelling to any location which is allowed to be based on the UAV route and the UAS operator wishes/restrictions. + +![Diagram illustrating an example multi-USS deployment. It shows two Local USS Networks (LUNs) connected to a PLMN. LUN 1 contains USS #1, USS #1.1, and USS #1.2, which are connected to DNAI #x, DNAI #y, and DNAI #z respectively. LUN 2 contains USS #2, USS #2.1, and USS #2.2, which are also connected to DNAI #x, DNAI #y, and DNAI #z respectively. The PLMN is shown as a horizontal bar at the bottom.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) + +The diagram illustrates a multi-USS deployment architecture. At the bottom, a horizontal bar represents the PLMN. Above it, two dashed ovals represent Local USS Networks (LUNs). The left LUN contains three cloud icons: USS #1 (top), USS #1.1 (bottom left), and USS #1.2 (bottom right). USS #1 is connected to both USS #1.1 and USS #1.2. USS #1.1 is connected to DNAI #x, USS #1.2 is connected to DNAI #z, and there is a DNAI #y between them. The right LUN contains three cloud icons: USS #2 (top), USS #2.1 (bottom left), and USS #2.2 (bottom right). USS #2 is connected to both USS #2.1 and USS #2.2. USS #2.1 is connected to DNAI #x, USS #2.2 is connected to DNAI #z, and there is a DNAI #y between them. All DNAIs (#x, #y, #z) are connected to the PLMN bar. + +Diagram illustrating an example multi-USS deployment. It shows two Local USS Networks (LUNs) connected to a PLMN. LUN 1 contains USS #1, USS #1.1, and USS #1.2, which are connected to DNAI #x, DNAI #y, and DNAI #z respectively. LUN 2 contains USS #2, USS #2.1, and USS #2.2, which are also connected to DNAI #x, DNAI #y, and DNAI #z respectively. The PLMN is shown as a horizontal bar at the bottom. + +Figure 7.4.2.1-1: Example multi-USS deployment + +#### 7.4.2.2 Procedure + +Figure 7.4.2.2-1 illustrates the procedure where the UAE server supports the change of USS. + +Pre-conditions: + +- The UAV has performed the UAS UE registration procedure. +- UAE client and UAE server have indicated Multi-USS support. + +![Sequence diagram illustrating the UAE layer assisted change of USS. The diagram shows interactions between four entities: UAE client (UAV), SEAL LMS, UAE server, and UAS application specific server. The sequence of messages is: 1. Multi-USS management procedure (including USS service areas, LUN info) from UAS application specific server to UAE server; 2. Mapping of UAS to list of allowable USSs & USS service areas to list of cells from UAE server to SEAL LMS; 3. Subscribe for UAV Location tracking from SEAL LMS to UAE server; 4. Detect UAV mobility to target USS area from UAE server to SEAL LMS; 5. USS change trigger from UAE server to UAS application specific server; 6. Decide change of USS for UAS from UAS application specific server to UAE server; 7. USS change command from UAE server to SEAL LMS; 8. Translation of USS change to UP path change (DNAI change) via AF traffic influence from SEAL LMS to UAE server; 9. USS change command from UAE server to UAE client (UAV); 10. ACK from UAE client (UAV) to UAE server; 11. USS change notification from UAE server to UAS application specific server.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant UAV as UAE client (UAV) + participant SEAL LMS + participant UAE server + participant UAS app specific server as UAS application specific server + + Note right of UAS app specific server: 1. Multi-USS management procedure (including USS service areas, LUN info) + UAS app specific server->>UAE server: 1. Multi-USS management procedure (including USS service areas, LUN info) + Note right of UAE server: 2. Mapping of UAS to list of allowable USSs & USS service areas to list of cells + UAE server->>SEAL LMS: 2. Mapping of UAS to list of allowable USSs & USS service areas to list of cells + Note right of SEAL LMS: 3. Subscribe for UAV Location tracking + SEAL LMS->>UAE server: 3. Subscribe for UAV Location tracking + Note right of UAE server: 4. Detect UAV mobility to target USS area + UAE server->>SEAL LMS: 4. Detect UAV mobility to target USS area + Note right of UAE server: 5. USS change trigger + UAE server->>UAS app specific server: 5. USS change trigger + Note right of UAS app specific server: 6. Decide change of USS for UAS + UAS app specific server->>UAE server: 6. Decide change of USS for UAS + Note right of UAE server: 7. USS change command + UAE server->>SEAL LMS: 7. USS change command + Note right of SEAL LMS: 8. Translation of USS change to UP path change (DNAI change) via AF traffic influence + SEAL LMS->>UAE server: 8. Translation of USS change to UP path change (DNAI change) via AF traffic influence + Note right of UAE server: 9. USS change command + UAE server->>UAV: 9. USS change command + Note right of UAV: 10. ACK + UAV->>UAE server: 10. ACK + Note right of UAE server: 11. USS change notification + UAE server->>UAS app specific server: 11. USS change notification + +``` + +Sequence diagram illustrating the UAE layer assisted change of USS. The diagram shows interactions between four entities: UAE client (UAV), SEAL LMS, UAE server, and UAS application specific server. The sequence of messages is: 1. Multi-USS management procedure (including USS service areas, LUN info) from UAS application specific server to UAE server; 2. Mapping of UAS to list of allowable USSs & USS service areas to list of cells from UAE server to SEAL LMS; 3. Subscribe for UAV Location tracking from SEAL LMS to UAE server; 4. Detect UAV mobility to target USS area from UAE server to SEAL LMS; 5. USS change trigger from UAE server to UAS application specific server; 6. Decide change of USS for UAS from UAS application specific server to UAE server; 7. USS change command from UAE server to SEAL LMS; 8. Translation of USS change to UP path change (DNAI change) via AF traffic influence from SEAL LMS to UAE server; 9. USS change command from UAE server to UAE client (UAV); 10. ACK from UAE client (UAV) to UAE server; 11. USS change notification from UAE server to UAS application specific server. + +**Figure 7.4.2.2-1: UAE layer assisted change of USS** + +1. The UAE server has performed the USS management procedure of clause 7.3.2.3.1; however at the Multi-USS management request, UAE server also receives from UAS application specific server the USS service areas (geographical) for all allowed USSs, and optionally the USS to DNAI mapping and a USS list per given Local USS network (LUN). + +NOTE: If USS to DNAI mapping is not provided in step 1, it is assumed that such mapping is available / pre-configured at UAE server (e.g. mapping of geographical area to DNAI). + +2. The UAE server maps each USS with different topological areas based on the USS to DNAI mapping (based on step 1), for all USSs which are allowed for a target area where the UAV is allowed to fly (this for example can be within the LUN). Then it also maps and stores all pairs of per LUN or for the areas of interest for the UAV (e.g. based on the allowable routes). +3. The UAE server tracks the location of the UAV, by requesting on-demand location monitoring from SEAL LMS (acting as VAL server in procedure of clause 9.3.4 or clause 9.3.5 of 3GPP TS 23.434 [5]) or via subscribing for monitoring the UAV location deviation (discussed in clause 9.3.11 of 3GPP TS 23.434 [5]). +4. The UAE server if detects an expected UAV location change to an area covered by a different USS (based on SEAL LMS monitoring subscription/request as in step 3), it generates a trigger event indicating that the UE moves to an area where the USS is overlapping with other USS or another overlapping USS within LUN area is not available. + +If it is an overlap, the UAE server checks whether the performance of serving USS is expected to get impacted (e.g. by requesting DN performance analytics for the target area) or if the serving USS is not supported at target area, checks what is the best available USS and whether this can provide the same services. The criteria for the best available USS are mainly the location of the UAV, but it can be also the priorities of the USS (based on the policies received) at the target area and the capabilities (services) provided by the target USS to be equivalent. + +5. The UAE server sends to the UAS application specific server a trigger message indicating the recommendation for a USS change for the UAS and provides the target USS ID or just a need for changing USS. Alternatively, the trigger message indicates a UAV mobility event, based on steps 3/4. + +- 6/7. The UAS application specific server, based on the trigger and after coordinating with source and target USSs (coordination is out of scope) sends to the UAS application specific server a USS change command message indicating the new USS information for the UAS. +8. The UAE server translates this to a UP path change and interacts with NEF as AF for influence UP path (switching to target DNAI). In particular UAE server (acting as AF) checks whether it can serve the target DNAI corresponding to the target USS based on the mapping of USS to DNAI which was performed in step 3. Interaction with 5GC is performed according to functionality for application function influence on traffic routing, see 3GPP TS 23.502 [8] clause 4.3.6.3. +9. The UAE server sends a USS change command to the UAV, indicating the UAV (UAE client) ID, a new serving USS information and optionally USS change authorization information. +10. The UAE server receives a positive or negative acknowledgement for the USS change. +11. The UAE server sends a USS change notification to the UAS application specific server upon successful USS change. + +### 7.4.3 Solution evaluation + +Key Issue #2 outlines the following to be investigated further with respect to the impact on the application layer functional model for UAS: + +- a) Whether and how the UAE layer can be enhanced to support change of USS/UTM during flight. +- b) Whether and how the UAE layer needs to be enhanced to assist the traffic steering of UAS application traffic to different DN/EDN to avoid application service disruption while in-flight. + +This solution addresses bullet a) and bullet b) in Key Issue #2. Management aspects based on solution #1 are provided by the USS and used by the UAE server to provide additional information for multi-USS configuration, like service areas of the USSes, etc. + +A summary of the UAE layer capabilities are: + +- 1) UAE server handles USS service area mapping to DNAI configuration to support application function influence on traffic routing as defined in 3GPP TS 23.502 [8] clause 4.3.6. +- 2) UAE server provides assistance at change of USS for partially overlapping multi-USS deployments based on UAV location tracking support related to change of USS/UTM during flight. +- 3) UAE server forwards the commands for change of USS from the USS/UTM. + +The solution enables the USS/UTM to be in control of the USS changes and utilizes the UAE layer's assistance to track the UAV and trigger change of USS. + +## 7.5 Solution #3: Support for C2 direct mode feasibility reporting + +### 7.5.1 Architecture enhancements + +None. + +### 7.5.2 Solution description + +#### 7.5.2.1 General + +This solution aims to address Key Issue #1 “Direct communication between UAVs” and in particular enhancements related to C2 communication monitoring over PC5. This solution addresses also Key Issue #3 since the outcome of such solution can trigger some coordination between PC5 and Uu for C2 mode switching. + +The network-assisted mode (in-direct) is used to facilitate the C2 communication in BLOS; however when the PC5 is feasible/available UAVs needs to switch to direct fast and without any loss of data. The feasibility/availability of PC5 + +can be e.g. when the UAV returns towards the UAV-C or when the expected QoS over PC5 is better than Uu (due to possible congestions/QoS degradation/resource starvation in one or both Uu links). + +The PC5 availability/feasibility indication for a C2 communication, will provide the awareness to the UAE server to switch to direct C2 communication if it is possible. The PC5 availability/feasibility can be captured at the UAV/UAV-C, e.g. the UAV-C can periodically broadcast signals in different frequencies, and upon reception of an ACK from the UAV to understand (based on the received signal) whether direct C2 is possible. The UAE server based on this indication can perform the procedure specified in 3GPP TS 23.255 [3] for C2 mode switching if possible. + +NOTE: This solution will not be considered for normative work unless SA2 provides the required functionality that aligns with this solution. + +#### 7.5.2.2 Procedure + +Figure 7.5.2.2-1 illustrates the procedure where the UAE server supports C2 direct mode feasibility checking. + +Pre-conditions: + +- The UAV has performed the UAS UE registration procedure. +- The UAV and UAV-C are both connected to 3GPP network and operate in network-based C2 mode. +- UAE Server has performed the C2 mode switching/selection capability initiation as in clause 7.4.2.1 of 3GPP TS 23.255 [3]. + +![Sequence diagram illustrating the support for C2 direct mode feasibility reporting. The diagram shows interactions between UAV-C, UAV, UAE server, and UAS application specific server. The process starts with '0. C2 communication over network'. The UAE server sends a '1. C2 direct mode feasibility request' to the UAV. The UAV responds with '2. C2 direct mode feasibility response'. The UAV then performs '3. PC5 Discovery'. The UAV sends a '4. C2 direct mode feasibility report' to the UAE server. Finally, the UAE server triggers '5. Dynamic UAE assisted C2 mode switching (based on 7.4.2.4 of TS 23.255)'.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +``` + +sequenceDiagram + participant UAV-C + participant UAV + participant UAE_server as UAE server + participant UAS_app_server as UAS application specific server + + Note over UAV-C, UAV: 0. C2 communication over network + Note over UAV-C, UAV: [UAS application specific client, UAE client] + + UAV->>UAE_server: 1. C2 direct mode feasibility request + UAE_server-->>UAV: 2. C2 direct mode feasibility response + Note over UAV-C, UAV: 3. PC5 Discovery + UAV->>UAE_server: 4. C2 direct mode feasibility report + Note over UAV-C, UAV: 5. Dynamic UAE assisted C2 mode switching (based on 7.4.2.4 of TS 23.255) + +``` + +Sequence diagram illustrating the support for C2 direct mode feasibility reporting. The diagram shows interactions between UAV-C, UAV, UAE server, and UAS application specific server. The process starts with '0. C2 communication over network'. The UAE server sends a '1. C2 direct mode feasibility request' to the UAV. The UAV responds with '2. C2 direct mode feasibility response'. The UAV then performs '3. PC5 Discovery'. The UAV sends a '4. C2 direct mode feasibility report' to the UAE server. Finally, the UAE server triggers '5. Dynamic UAE assisted C2 mode switching (based on 7.4.2.4 of TS 23.255)'. + +**Figure 7.5.2.2-1: Support for C2 direct mode feasibility reporting** + +1. The UAE server sends a C2 direct mode feasibility request including the ProSe codes for direct C2 operation, the UAV and UAV-C IDs and addresses, and the time and area for which the monitoring of feasibility will apply. Also, the request can include configuration of the expected reporting and periodicity/frequency of reporting required. +2. The UAE client of the UAV sends a feasibility response for the C2 communication. +3. The UAE client performs PC5 discovery between UAV and UAV-C UEs, as specified in ProSe Direct Discovery Models A, B defined in clause 5.3 of 3GPP TS 23.303 [9]. The PC5 discovery information can be exchanged between UAE clients, based on the configured ProSe announcements (e.g., based on codes received in step 1). +4. When the UAE clients are aware of the PC5 discovery, one or more clients sends a PC5 feasibility report to the UAE server, to notify on the PC5 possibility. This PC5 feasibility report message can include the UE identifiers, the UAS identification, a PC5 availability/feasibility notification indication, PC5 capabilities/configuration. The PC5 feasibility report can also include a preference/priority of the C2 operation mode, e.g., based on application requirements at the UAV-C and/or UAV. +5. The UAE server triggers a dynamic C2 mode switching operation as in clause 7.4.2.4 of 3GPP TS 23.255 [3]. + +### 7.5.3 Solution evaluation + +This solution addresses Key Issue #1 and Key Issue #3 and provides an enhancement of C2 related functionality specified in Release 17, by allowing the PC5 feasibility monitoring. This solution is dependent on SA2 Release 18 support for ProSe/PC5 for C2 communication (3GPP TR 23.700-58 [6]). + +NOTE 1: This solution will be considered feasible only if the SA2 provided concluded solution (as in 3GPP TR 23.700-58 [6]) works in the same manner as required by this solution. + +NOTE 2: The enhancements to procedures in clause 7.4.2 of 3GPP TS 23.255 [3] to fulfill the objectives of this solution will be considered during normative work (if concluded). + +## 7.6 Solution #4: UAE layer support for DAA + +### 7.6.1 Architecture enhancements + +None. + +### 7.6.2 Solution description + +#### 7.6.2.1 General + +This solution aims to address the gaps identified in Key Issue #4 “Support for detect and avoid services and applications”. + +The solution covers registration of the UAE clients’ DAA capability to the UAE server, provisioning of the DAA policies from the UAS application specific server to the UAE server and the UAE client and support for DAA from the UAE layer to the UAS application layer. + +The DAA capability of the UAE client is provided to the network to inform the network that the UAE client support reception of DAA-policies from the network and has functionality in the UAE layer to assist and coordinate support for DAA in the UE + +A DAA policy has two components: + +- The DAA application policy. This policy is used by the application and transparently provided from the UAS application specific server to the UAS client. The DAA application policy is timestamped and may be stored at the UAE server, to let the operator know when and optionally what information was provided to the UAS application. +- The DAA support policy. This policy is used by the UAE layer, and contains information pertaining to the UAE layer. This is parameters/rules for the UAE layer to provide support for DAA applications. + +NOTE: The complete list of parameters for the DAA support policy will be specified during the normative work. + +The Detect and Avoid operations performed by the UAS application layer is out of scope of the solution. + +#### 7.6.2.2 Registration of DAA capability + +Pre-conditions: + +- The UAE client has discovered the UAE server and is aware of the address of the UAE server (e.g., FQDN). + +NOTE: How the UAE client is provisioned with the UAE server information is outside the scope of the current document. + +- The UAV has already been assigned with the UAV ID. + +![Sequence diagram for Figure 7.6.2.2-1: Registration of DAA capability of the UAE client. The diagram shows three steps: 1. Registration request from UAE client to UAE server; 2. Authentication and authorization check performed by UAE server; 3. Registration response from UAE server to UAE client.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant UAE client + participant UAE server + Note right of UAE server: 2. Authentication and authorization check + UAE client->>UAE server: 1. Registration request + UAE server-->>UAE client: 3. Registration response + +``` + +Sequence diagram for Figure 7.6.2.2-1: Registration of DAA capability of the UAE client. The diagram shows three steps: 1. Registration request from UAE client to UAE server; 2. Authentication and authorization check performed by UAE server; 3. Registration response from UAE server to UAE client. + +**Figure 7.6.2.2-1: Registration of DAA capability of the UAE client** + +1. The UAE client sends a registration request to the UAE server. The UAE client includes an indication of its DAA capability. +2. The UAE server performs authentication and authorization check (e.g., based on pre-provisioned security information or by interacting with UAS application specific server). +3. The UAE server sends a registration response to the UAE client indicating success or failure of the registration for DAA support. + +#### 7.6.2.3 Provision of DAA policies + +##### 7.6.2.3.1 DAA support management procedure + +Figure 7.6.2.3.1-1 illustrates the DAA support management procedure where the UAE server receives an application request for managing the DAA configuration parameters from the UAS application specific server. + +Pre-condition: + +- The UAV has received its UAS ID from the UAS application specific server. +- The UAV has performed the UAS UE registration procedure. + +![Sequence diagram for Figure 7.6.2.3.1-1: DAA support management procedure. The diagram shows four steps: 1. DAA Support management request from UAS application specific server to UAE server; 2. DAA Support management response from UAE server to UAS application specific server; 3. DAA configuration performed by UAE server; 4. DAA Support management complete notification from UAE server to UAS application specific server.](5fbb4f0de01736f1293333e599410c99_img.jpg) + +``` + +sequenceDiagram + participant UAE server + participant UAS application specific server + Note left of UAE server: 3. DAA configuration + UAS application specific server->>UAE server: 1. DAA Support management request + UAE server-->>UAS application specific server: 2. DAA Support management response + UAE server->>UAS application specific server: 4. DAA Support management complete + +``` + +Sequence diagram for Figure 7.6.2.3.1-1: DAA support management procedure. The diagram shows four steps: 1. DAA Support management request from UAS application specific server to UAE server; 2. DAA Support management response from UAE server to UAS application specific server; 3. DAA configuration performed by UAE server; 4. DAA Support management complete notification from UAE server to UAS application specific server. + +**Figure 7.6.2.3.1-1: DAA support management procedure** + +1. The UAS application specific server sends to the UAE server a DAA support management request. The request includes the UAV (UAE client) identifier and the DAA policies. +2. The UAE server sends to the UAS application specific server a DAA support management response with a positive or negative acknowledgement of the request. +3. The UAE server executes the DAA configuration according to clause 7.6.2.3.2. +4. After successful execution of DAA configuration, the UAE server notifies the UAS application specific server with DAA support management complete. + +##### 7.6.2.3.2 DAA support configuration procedure + +Figure 7.6.2.3.2-1 illustrates the DAA support configuration procedure. This procedure enables the configuration of the UAE client, based on a request from UAS application specific server to configure DAA policies to the UAE client. + +Pre-conditions: + +1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4]. +2. UAE server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server. +3. UAE server has performed the DAA support management procedure according to clause 7.6.2.2.2. + +![Sequence diagram for DAA support configuration procedure](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` +sequenceDiagram + participant UAE client (UAV) + participant 5GC + participant UAE server + Note left of UAE client: 2. Store or remove DAA configuration parameters + UAE server->>UAE client: 1. DAA Support configuration request + UAE client->>UAE server: 3. DAA Support configuration response +``` + +The diagram shows a sequence of three messages between a UAE client (UAV), a 5GC, and a UAE server. The UAE server sends a '1. DAA Support configuration request' to the UAE client. The UAE client performs an internal action '2. Store or remove DAA configuration parameters' and then sends a '3. DAA Support configuration response' back to the UAE server. + +Sequence diagram for DAA support configuration procedure + +Figure 7.6.2.3.2-1: DAA support configuration procedure + +1. The UAE server sends a DAA support configuration request to the UAE client. The UAE client receives a DAA support configuration request from the UAE server that includes the DAA configuration parameters. + +NOTE: Details in case of e.g. removal of DAA policies will be specified during the normative work. + +2. The UAE client stores or removes the DAA configuration parameters as per the information received in step 1. +3. The UAE client sends a DAA support configuration response to the UAE server. + +#### 7.6.2.4 UAE layer support for DAA applications + +##### 7.6.2.4.1 Client initiated DAA support + +Figure 7.6.2.4.1-1 illustrates the procedure with client initiated DAA support. + +Pre-conditions: + +1. UAE server has provided DAA policies to the UAE client. + +![Sequence diagram for client initiated DAA support](6efcea66501271e9ea36cf33982f08d5_img.jpg) + +``` +sequenceDiagram + participant UAE client (UAV) + participant UAE server + participant UAS application specific server + Note left of UAE client: 1. + UAE client->>UAE server: 2. DAA support information + UAE server->>UAS application specific server: 3. DAA support information + UAS application specific server->>UAE server: 4. DAA support information acknowledge + UAE server->>UAE client: 5. DAA support information acknowledge +``` + +The diagram shows a sequence of five messages between a UAE client (UAV), a UAE server, and a UAS application specific server. The UAE client sends a '2. DAA support information' message to the UAE server. The UAE server then sends a '3. DAA support information' message to the UAS application specific server. The UAS application specific server responds with a '4. DAA support information acknowledge' message to the UAE server. Finally, the UAE server sends a '5. DAA support information acknowledge' message back to the UAE client. A small box with the number '1.' is shown below the UAE client lifeline, indicating the start of the procedure. + +Sequence diagram for client initiated DAA support + +Figure 7.6.2.4.1-1: Client initiated DAA support + +1. The UAE layer has, e.g. based on the DAA support policy and/or information provided by the U2X layer (see 3GPP TR 23.700-58 [6]) detected UAVs in proximity. +2. The UAE client sends a DAA support information (i.e. U2X layer detected information) to the UAE server indicating a detected flight path conflict with one or more UAVs in proximity. + +If the UAE client considers an emergency situation (e.g., due to lack of response from the UAE server and/or UAS application specific server), the UAE client shall inform the application layer (i.e. UAS Client) based on the DAA support policy. + +3. The UAE server records the DAA support event with current timestamp. UAE server requests UAE client location information from the SEAL location services. The UAE server records the received location information with current timestamp. The UAE server sends the DAA support information to the UAS application specific server. + +NOTE: The UAE server needs to provide trusted and timely network based location information to the USS which can be used as critical input for USS to handle or record DAA situations. The USS can provide deconflicting instructions to the UAV based on provided location information or handle properly potential flight path deviation due to DAA that is deconflicted locally. + +4. The UAS application specific server provides a DAA support information acknowledgement to the UAE server. The UAS application specific server may include more information in the acknowledgement (e.g. other UAVs detected information by network). +5. The UAE server provides a DAA support information acknowledgement to the UAE client, and the UAE client provides the application layer (i.e. UAS Client) with the consolidated information from the UAS application specific server. + +##### 7.6.2.4.2 Server initiated DAA support + +Figure 7.6.2.4.2-1 illustrates the procedure with UAS application server initiated DAA support. + +Pre-conditions: + +1. UAS application specific server has provided DAA configuration parameters to the UAE client. + +![Sequence diagram for Server initiated DAA support. The diagram shows three lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence starts with a box labeled '1.' on the UAS application specific server lifeline. An arrow labeled '2. DAA support information' points from the UAS application specific server to the UAE server. An arrow labeled '3. DAA support information' points from the UAE server to the UAE client (UAV). An arrow labeled '4. DAA support information acknowledge' points from the UAE client (UAV) to the UAE server. An arrow labeled '5. DAA support information acknowledge' points from the UAE server to the UAS application specific server.](2119293733c74fc64de88aefd597f4bb_img.jpg) + +``` + +sequenceDiagram + participant UAV as UAE client (UAV) + participant US as UAS application specific server + participant USer as UAE server + Note right of US: 1. + US->>USer: 2. DAA support information + USer->>UAV: 3. DAA support information + UAV->>USer: 4. DAA support information acknowledge + USer->>US: 5. DAA support information acknowledge + +``` + +Sequence diagram for Server initiated DAA support. The diagram shows three lifelines: UAE client (UAV), UAE server, and UAS application specific server. The sequence starts with a box labeled '1.' on the UAS application specific server lifeline. An arrow labeled '2. DAA support information' points from the UAS application specific server to the UAE server. An arrow labeled '3. DAA support information' points from the UAE server to the UAE client (UAV). An arrow labeled '4. DAA support information acknowledge' points from the UAE client (UAV) to the UAE server. An arrow labeled '5. DAA support information acknowledge' points from the UAE server to the UAS application specific server. + +**Figure 7.6.2.4.2-1: Server initiated DAA support** + +1. The UAS application specific server has discovered a conflict related to DAA (e.g. presence of other UAVs in proximity of the UAV), and will provide the UAE client with relevant information. + +NOTE: An example of such a conflict is that an UAV with U2X capabilities, see clause 7.6.2.4.1 step 0, provides information about objects in proximity to the UAS application specific server. The UAS application specific server can, based on this, e.g. provide information to one or more surrounding UAVs that does not have U2X capability. + +2. The UAS application specific server sends a DAA support information to the UAE server which includes information of other UAVs in the proximity of the UAV. The UAE server verifies that the request is authorized as described above before sending the DAA support information to the UAE client. + +3. The UAE server sends a DAA support information from the UAS application specific server to the UAE client. Coordination with Real-Time UAV connection status monitoring and location reporting is performed by the UAE server, see 3GPP TS 23.255 [3] clause 7.5 and 3GPP TS 23.434 [5], clause 9.3. + +Further, UAE client provides the application layer with the consolidated information from the UAS application specific server. + +4. The UAE client sends to the UAE server a DAA support information acknowledge. +5. The UAE server sends the DAA support information acknowledge to the UAS application specific server. + +### 7.6.3 Solution evaluation + +Key Issue #4 outlines the following to be investigated further with respect to the impact on the application layer functional model for UAS: + +- a) Whether and how the UAE layer and/or SEAL services can be enhanced to support DAA services and applications for collision avoidance considering the Stage 1 requirements. +- b) How the UAE layer can support DAA scenarios where UAVs belong to multiple PLMNs. + +This solution addresses the bullet a) and bullet b) in Key Issue #4: + +A summary of the UAE layer capabilities are: + +- 1) Management for provision of DAA-policies from the UAS application specific server the UAS application client is provided by the UAE layer. +- 2) UAE layer provides support for handling of DAA support information. +- 3) Provision of support for DAA is PLMN-agnostic. + +## 7.7 Solution #5: Support for DAA applications + +### 7.7.1 Architecture enhancements + +None. + +### 7.7.2 Solution description + +#### 7.7.2.1 General + +This solution aims to address the gaps identified in Key Issue #4 “Support for detect and avoid services and applications”. The solution proposes two aspects for the UAE layer support for DAA applications: + +- Providing real-time location update about UAVs to UASS (UTM/USS). +- Providing dynamic information of UAVs in an application defined area to the host UAV and/or UASS (UTM/USS). + +It is considered that the DAA application logic which mainly includes decision making for collision avoidance and its related signalling between the UAV and UASS (USS) is out of scope of 3GPP. + +#### 7.7.2.2 Enhanced real-time tracking of location information of UAVs to USS + +This procedure enables the USS to subscribe for real-time location information of UAVs from UAE server. + +1. UASS (UTM/USS) performs the subscription with UAE server to obtain real-time location information from UAE server as specified in clause 7.5.2.2 of 3GPP TS 23.255 [3] with the following modifications: + +- a. In step 1, the subscription request can be enhanced such that the UASS can subscribe for a list of UAV IDs instead of a single UAV ID. +2. Upon successful step 1 operation, the UAE server provides the notifications to UASS (USS) as per the subscription request as specified in clause 7.5.2.3 of 3GPP TS 23.255 [3] with the following modifications: + - a. The notification message from UAE server to UASS (USS) can be enhanced to contain one or more location information of the UAVs instead of the location information of a single UAV. + +#### 7.7.2.3 Tracking dynamic UAVs in an application defined area relative to a host UAV + +##### 7.7.2.3.1 General + +The UAE server can be responsible for tracking a host UAV's dynamic information (i.e., information of other dynamic UAVs in an application defined area relative to a host UAV). As per a proximity range set by the application layer, the UAE layer supports providing the dynamic information (i.e. other UAVs' location information) to the UASS (UTM/USS) and/or to the host UAV. + +This feature utilizes the following procedures: + +- UASS or the host UAV subscription for host UAV's dynamic information with UAE server. +- UAE server tracking host UAV's UE location with support from SEAL's location management server. +- UAE server management of dynamic UE location based group. +- UAE server obtaining dynamic information from the UAVs in proximity range of the host UAV. +- UAE server notification of host UAV's dynamic information to the UASS and/or to the host UAV. + +NOTE: The details of the usage of dynamic information of host UAV by UASS or by the host UAV is out of scope of this specification. + +##### 7.7.2.3.2 Subscription for host UAV dynamic information + +Figure 7.7.2.3.2-1 describes the procedure for subscription for host UAV's dynamic information. + +Pre-condition: + +- UASS has registered with UAE server 1 which is responsible for the host UAV. +- The UAV ID and application defined proximity range information are configured on the host UAV. + +![Sequence diagram for subscription for host UAV dynamic information. The diagram shows four steps: 1. UASS or UAE client of the Host UAV sends a 'Subscribe host UAV dynamic information request' to UAE server 1. 2. UAE server 1 sends a 'Store subscription' message to the Location management server 1. 3. UAE server 1 sends a 'Subscription response' back to the UASS or UAE client. 4. UAE server 1 sends an 'Obtain and track dynamic UE location for the UAV ID' message to the Location management server 1.](f7d969388c4f7e30cd04a061314bfa0e_img.jpg) + +``` + +sequenceDiagram + participant UASS as UASS or UAE client of the Host UAV + participant UAE as UAE server 1 (responsible for the host UAV) + participant LMS as Location management server 1 + Note right of UAE: 2. Store subscription + Note right of LMS: 4. Obtain and track dynamic UE location for the UAV ID + UASS->>UAE: 1. Subscribe host UAV dynamic information request + UAE->>LMS: 2. Store subscription + UAE->>UASS: 3. Subscription response + UAE->>LMS: 4. Obtain and track dynamic UE location for the UAV ID + +``` + +Sequence diagram for subscription for host UAV dynamic information. The diagram shows four steps: 1. UASS or UAE client of the Host UAV sends a 'Subscribe host UAV dynamic information request' to UAE server 1. 2. UAE server 1 sends a 'Store subscription' message to the Location management server 1. 3. UAE server 1 sends a 'Subscription response' back to the UASS or UAE client. 4. UAE server 1 sends an 'Obtain and track dynamic UE location for the UAV ID' message to the Location management server 1. + +Figure 7.7.2.3.2-1: Subscription for host UAV dynamic information + +1. The UASS or UAE client of host UAV sends a subscribe host UAV dynamic information request to the UAE server 1. The request includes the UAV ID of the host UAV, application defined proximity range information. +2. The UAE server 1 stores the subscription information. + +3. The UAE server 1 sends subscription response to the UASS. +4. The UAE server 1 obtains and initiates tracking the host UAV location from the location management server 1 as specified in 3GPP TS 23.434 [5]. + +##### 7.7.2.3.3 Management of dynamic UE location based group + +Figure 7.7.2.3.3-1 describes the procedure for management of dynamic UE location based group. + +Pre-condition: + +- UAE server 1 has received an updated location of the host UAV as per procedure specified in 3GPP TS 23.434 [5]. +- UAE server 1 is configured with UAE server 2..N information of other UAS operator and their supported region of operation. + +![Sequence diagram illustrating the management of dynamic UE location group. The diagram shows four lifelines: UAE server 1 (responsible for host UAV), Location management server 1, UAE server 2..N (Other UAS operators in the UE location), and Location Management Server 2..N. The sequence of steps is: 1. Trigger for dynamic UE location group creation/update (from UAE server 1 to Location management server 1); 2. Get Dynamic UEs information at the UE location (from Location management server 1 to UAE server 1); 3. Determine the UAE server(s) of other UAS operators operating in the UE location and Range (internal to UAE server 1); 4. Get Dynamic UEs information at the UE location from UAE server 2..N (from UAE server 1 to UAE server 2..N); 5. Get Dynamic UEs information at the UE location (from UAE server 2..N to Location Management Server 2..N); 6. As per agreement between UAS operators, the UAV IDs is replaced with temporary UAV IDs (internal to Location Management Server 2..N); 7. Get response with UE list (from Location Management Server 2..N to UAE server 2..N); 8. Create/update the Dynamic UE location-based group (internal to UAE server 1).](9b686adccf125267a013fa25721231a3_img.jpg) + +Sequence diagram illustrating the management of dynamic UE location group. The diagram shows four lifelines: UAE server 1 (responsible for host UAV), Location management server 1, UAE server 2..N (Other UAS operators in the UE location), and Location Management Server 2..N. The sequence of steps is: 1. Trigger for dynamic UE location group creation/update (from UAE server 1 to Location management server 1); 2. Get Dynamic UEs information at the UE location (from Location management server 1 to UAE server 1); 3. Determine the UAE server(s) of other UAS operators operating in the UE location and Range (internal to UAE server 1); 4. Get Dynamic UEs information at the UE location from UAE server 2..N (from UAE server 1 to UAE server 2..N); 5. Get Dynamic UEs information at the UE location (from UAE server 2..N to Location Management Server 2..N); 6. As per agreement between UAS operators, the UAV IDs is replaced with temporary UAV IDs (internal to Location Management Server 2..N); 7. Get response with UE list (from Location Management Server 2..N to UAE server 2..N); 8. Create/update the Dynamic UE location-based group (internal to UAE server 1). + +**Figure 7.7.2.3.3-1: Management of dynamic UE location group** + +1. Dynamic UE location based group creation or update is triggered (e.g. notified of the UE location of host UAV) via the step 4 in clause 7.7.2.3.2 for the UAV ID of the host UAV. +2. UAE server 1 uses its associated LMS 1 to obtain the dynamic UE list and the corresponding location information in the proximity area of the host UAV by providing the application defined proximity range and the UE location of the host UAV as specified in clause 9.3.10 of 3GPP TS 23.434 [5]. +3. UAE server 1 determines the list of other UAE servers 2..N operating in the same location. +4. For each UAE server determined in step 3, UAE server 1 requests the dynamic UE list and its corresponding location information for the application defined proximity range by providing the UE location of the host UAV. +5. The UAE server(s) 2..N obtain UE information corresponding to the UE location and application defined proximity range from its corresponding LMS 2..N as specified in 3GPP TS 23.434 [5]. + +6. As per the agreement between the UAS operators, if the UAV IDs are not shareable, then UAE server(s) 2..N may replace the UAV IDs with temporary UAV IDs. +7. The UAE server(s) 2..N sends get response with UE list in the UE location and application defined proximity range to UAE server 1. +8. If UAE server 1 has no dynamic UE location group for the UAV ID, the UAE server 1 creates a dynamic UE location based group with the UE list received from its LMS and other UAE server(s) 2..N. Further UAE server 1 stores the dynamic UE location based group. Otherwise, the UAE server 1 updates the dynamic UE location group with the latest UE information. The UAVs whose locations are no more within the application defined proximity range are removed from the dynamic UE location group. + +##### 7.7.2.3.4 Obtaining dynamic information of the UEs in proximity range + +###### 7.7.2.3.4.1 Subscription procedure within UAS operator + +Figure 7.7.2.3.4.1-1 describes the subscription procedure within UAS operator to obtain dynamic information from the UEs in application defined proximity range. + +Pre-condition: + +- UAE server 1 is tracking the host UAV and has created the dynamic UE location based group as per procedure in clause 7.7.2.3.3. + +![Sequence diagram for Figure 7.7.2.3.4.1-1: Subscription procedure within UAS operator. The diagram shows three steps: 1. UAE server 1 sends a 'Subscribe dynamic information request' to UAE client(s). 2. UAE client(s) perform 'Store subscription'. 3. UAE client(s) send a 'Subscription response' back to UAE server 1.](15e4a144a88176b71ea3eff2722253b0_img.jpg) + +``` +sequenceDiagram + participant UAE server 1 + participant UAE client(s) + Note right of UAE client(s): 2. Store subscription + UAE server 1->>UAE client(s): 1. Subscribe dynamic information request + UAE client(s)-->>UAE server 1: 3. Subscription response +``` + +Sequence diagram for Figure 7.7.2.3.4.1-1: Subscription procedure within UAS operator. The diagram shows three steps: 1. UAE server 1 sends a 'Subscribe dynamic information request' to UAE client(s). 2. UAE client(s) perform 'Store subscription'. 3. UAE client(s) send a 'Subscription response' back to UAE server 1. + +**Figure 7.7.2.3.4.1-1: Subscription procedure within UAS operator** + +1. The UAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the UAE clients who are part of the dynamic UE location group. These UAE clients (UAVs) belong to the same UAS operator as the host UAV. The request consists of reporting configuration (e.g. frequency of reporting, event based). +2. The UAE client(s) store the subscription information. +3. The UAE client(s) send a subscription response to the UAE server 1. + +###### 7.7.2.3.4.2 Subscription procedure across UAS operators + +Figure 7.7.2.3.4.2-1 describes the subscription procedure across UAS operators to obtain dynamic information from the UEs in application defined proximity range. + +Pre-condition: + +- UAE server 1 has created the dynamic UE location based group as per procedure in clause 7.7.2.3.3. + +![Sequence diagram for Subscription procedure across UAS operators. Lifelines: UAE server 1, UAE server 2, UAE client(s). Step 1: UAE server 1 sends '1. Subscribe dynamic information request' to UAE server 2. Step 2: UAE server 2 sends '2. Determine the UAV ID(s)' to UAE client(s). Step 3: UAE client(s) sends '3. Perform subscription' to UAE server 2. Step 4: UAE server 2 sends '4. Subscription response' to UAE server 1.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant UAE server 1 + participant UAE server 2 + participant UAE client(s) + Note right of UAE server 2: 2. Determine the UAV ID(s) + Note right of UAE server 2: 3. Perform subscription + UAE server 1->>UAE server 2: 1. Subscribe dynamic information request + UAE server 2->>UAE client(s): 2. Determine the UAV ID(s) + UAE client(s)->>UAE server 2: 3. Perform subscription + UAE server 2->>UAE server 1: 4. Subscription response + +``` + +Sequence diagram for Subscription procedure across UAS operators. Lifelines: UAE server 1, UAE server 2, UAE client(s). Step 1: UAE server 1 sends '1. Subscribe dynamic information request' to UAE server 2. Step 2: UAE server 2 sends '2. Determine the UAV ID(s)' to UAE client(s). Step 3: UAE client(s) sends '3. Perform subscription' to UAE server 2. Step 4: UAE server 2 sends '4. Subscription response' to UAE server 1. + +**Figure 7.7.2.3.4.2-1: Subscription procedure across UAS operators** + +1. The UAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the UAE server(s) who's UAVs are part of the dynamic UE location group. The request consists of temporary UAV IDs, reporting configuration (e.g. frequency of reporting, event based). +2. As per the agreement between UAS operators, if UAV IDs are not shareable, then UAE server 2 determines the UAV IDs corresponding to the temporary UAV IDs provided in step 1. +3. The UAE server 2 performs subscription procedure as specified in clause 7.7.2.3.4.1 with the UAE client(s). +4. The UAE server 2 sends a subscription response to the UAE server 1. + +NOTE: UAE server 1 initiates this procedure with other UAE servers operating in the area. + +##### 7.7.2.3.5 Notification procedure + +Figure 7.7.2.3.5-1 describes the notification procedure of dynamic information from the UEs in application defined proximity range. + +Pre-condition: + +- UAE server 2 has received the notification of dynamic information from its subscribed UAE client(s). + +![Sequence diagram for Notification procedure. Lifelines: UAE Server 2, UAE Client 2, UAE Client 1, UAE Server 1. Step 1: UAE Client 1 and UAE Client 2 send '1. Notification of dynamic information' to UAE Server 1. Step 2: UAE Server 1 sends '2. Prepare host UAV dynamic information including all the aggregate information from different UAE clients' to UAE Server 2.](68ea9310fb829dd6007635a6cd4ea2ad_img.jpg) + +``` + +sequenceDiagram + participant UAE Server 2 + participant UAE Client 2 + participant UAE Client 1 + participant UAE Server 1 + Note right of UAE Server 1: 2. Prepare host UAV dynamic information including all the aggregate information from different UAE clients + UAE Client 1->>UAE Server 1: 1. Notification of dynamic information + UAE Client 2->>UAE Server 1: 1. Notification of dynamic information + UAE Server 1->>UAE Server 2: 2. Prepare host UAV dynamic information including all the aggregate information from different UAE clients + +``` + +Sequence diagram for Notification procedure. Lifelines: UAE Server 2, UAE Client 2, UAE Client 1, UAE Server 1. Step 1: UAE Client 1 and UAE Client 2 send '1. Notification of dynamic information' to UAE Server 1. Step 2: UAE Server 1 sends '2. Prepare host UAV dynamic information including all the aggregate information from different UAE clients' to UAE Server 2. + +**Figure 7.7.2.3.5-1: Notification procedure** + +1. As per subscription procedure in clause 7.7.2.3.4.1 and clause 7.7.2.3.4.2, the UAE client(s) and UAE server 2 (of another UAS operator) send notification of dynamic information to the UAE server 1. The notification includes the nearby UE information (e.g. UAVs), distance with nearby UEs, UEs location information. As per agreement between UAS operators, if UAV IDs are not shareable, then UAE server 2 includes the temporary UAV IDs in the notification. +2. The UAE server 1 aggregates information from different UAE clients to create the host UAV dynamic information. + +##### 7.7.2.3.6 Notification of host UAV dynamic information + +Pre-conditions: + +- UASS has performed subscription as per procedure in clause 7.7.2.3.2 with UAE server 1. +- UAE server 1 has prepared the host UAV dynamic information as per procedure in clause 7.7.2.3.5. + +![Sequence diagram for host UAV dynamic information notification](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +``` +sequenceDiagram + participant UAE server 1 (responsible for host UAV) + participant UASS or UAE client of Host UAV + Note right of UASS or UAE client of Host UAV: 2. Update the host UAV dynamic information + UAE server 1->>UASS or UAE client of Host UAV: 1. Notify host UAV dynamic information + Note right of UASS or UAE client of Host UAV: 2. Update the host UAV dynamic information +``` + +The diagram is a sequence diagram showing the interaction between 'UAE server 1 (responsible for host UAV)' and 'UASS or UAE client of Host UAV'. The process consists of two steps: 1. 'Notify host UAV dynamic information' from the server to the client, and 2. 'Update the host UAV dynamic information' which occurs at the client side. + +Sequence diagram for host UAV dynamic information notification + +**Figure 7.7.2.3.6: Notification for host UAV dynamic information** + +1. The UAE server 1 sends notification of host UAV dynamic information to the subscribed entity (i.e. UASS and/or to the subscribed UAE client of the host UAV). The notification includes the aggregated information of all the UEs in the application defined proximity range of the host UAV and the location of the host UAV. +2. The UASS or the UAE client of the host UAV updates the host UAV dynamic information with the host UAV dynamic information received in step 1. The UAE client provides the host UAV dynamic information to the UAS Client. + +### 7.7.3 Solution evaluation + +This solution addresses Key Issue #4 by defining UAV(s) tracking capabilities at UAE layer. It is a viable solution for the UASS (UTM/USS) or host UAV to manage DAA scenarios by utilizing the UAE layer capabilities of real time UAV location tracking and availing host UAV dynamic information in an application defined area. + +# --- 8 Deployment scenarios + +## 8.1 General + +There is no deployment scenario described in this Technical Report. + +# --- 9 Overall evaluation + +There is no architecture enhancement described in this Technical Report. + +## 9.1 Architecture enhancements + +## 9.2 Key issue evaluations + +### 9.2.1 General + +This clause compares and evaluates all proposed solutions against each of the key issues listed in clause 4. + +All the key issues, solutions and architecture enhancements specified in this technical report are listed in Table 9.2.1-1. + +Table 9.2.1-1 provides a mapping of the key issues to the related solutions. It also indicates whether the solution requires enhancement to the Release-17 architecture and lists the dependencies on other working groups. + +**Table 9.2.1-1 Key issue and solutions** + +| Key issues
(evaluation clause reference) | Solution | Architectural enhancement
(clause reference) | Enhancements required | Dependency on other working groups | +|------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------------------------------------|-----------------------|------------------------------------| +| KI #1 Direct communication between UAVs | Solution #3:
Support for C2 direct mode feasibility reporting | 7.5 | None | SA2 | +| KI #2: Support for multi-USS deployments | Solution #1:
Change of USS during flight
NOTE | 7.3 | None | None | +| | Solution #2:
Support for USS re-mapping for a UAS | 7.4 | None | None | +| KI #3: Coordination between Uu and PC5 for direct UAV-to-UAV or UAV-to-UAV-C communication | Solution #3:
Support for C2 direct mode feasibility reporting | 7.5 | None | SA2 | +| KI #4: Support for detect and avoid services and applications | Solution #4: UAE layer support for DAA | 7.6 | None | None | +| | Solution #5:
Support for DAA applications | 7.7 | None | None | +| NOTE: Change of DN/EDN to avoid disruption while in flight due to change of USS is not covered by this solution. | | | | | + +### 9.2.2 Evaluation of key issue #1: Direct communication between UAVs + +Key Issue #1 outlines the following to be investigated: + +- How the UAE layer can be enhanced to support usage of direct communication between UAVs. +- Whether and how the UAE layer functionality related to C2 communication support can be enhanced if PC5 is used for direct communication. + +Solution #3 is selected as the basis for normative work, based on the following principles and with the following constraints: + +- Provision of enhancement of C2 related functionality. +- Allowance of PC5 feasibility monitoring. + +This solution is dependent on the support for ProSe/PC5 for C2 communication, see 3GPP TR 23.700-58 [6]. + +This solution will be considered feasible only if the concluded solution in 3GPP TR 23.700-58 [6] works in the same manner as required by the solution specified in clause 7.5. + +Enhancements to the procedures in of 3GPP TS 23.255 [3] clause 7.4.2 to fulfill the objectives of this solution will be considered during normative work (if concluded). + +### 9.2.3 Evaluation of key issue #2: Support for multi-USS deployments + +Key Issue #2 outlines the following to be investigated: + +- a) Whether and how the UAE layer can be enhanced to support change of USS/UTM during flight. +- b) Whether and how the UAE layer needs to be enhanced to assist the traffic steering of UAS application traffic to different DN/EDN to avoid application service disruption while in-flight. + +Solution #1 focuses on bullet a) including handling of management and policy for multi-USS deployments. By the policy for multi-USS configuration parameters, the USS will decide the level of control the UAE layer can take on behalf of the USS. + +Solution #2 re-use the management and policy-framework from solution #1, with additions for mapping between USS service areas and 3GPP infrastructure information (i.e., DNAI). + +Solution #1 and solution #2 complements each other to address both bullet a) and bullet b) using a common policy framework. + +A policy-based approach with the execution as requested by the USS via the UAE Client / UAE server in solution #1 and a UAE Server centric approach in solution #2 are compatible with each other and can be combined into a “UAE layer assisted / USS controlled” based solution covering all possible scenarios and requirements of key issue #2. This approach is in line with the principles and functionality specified in 3GPP TS 23.255 [3] for C2 communication mode selection/switching. + +Solution #1 and solution #2 are selected as the basis for normative work, based on the following combined UAE layer assisted / USS controlled principles: + +- 1) The Multi-USS capabilities of the UAE client and the UAE server are provided to the USS. +- 2) The UAE server and the UAE client are provided with policies from the USS for multi-USS deployments. +- 3) The USS is always in control of the decision for USS change during flight. The solutions enable the USS to explicitly make the decision to change the USS or provide/revoke permissions to the UAE client to make the decision on behalf of the USS based upon configuration provided by the USS when communication with the USS is lost. + +NOTE: Possible actions by the UAE server due to loss of contact with the USS will be discussed during the normative phase. + +- 4) The UAE server uses information provided by the USS in the policies for multi-USS deployment and the UAV location from the 3GPP network when providing a notification to the USS about a possible change of USS. This is based on the policy from the USS. The USS can initiate change of USS if this is required. +- 5) The UAE client notifies the UAE server when, based on policy from the USS, it detects condition for change of USS. The UAE server provides an indication to the USS to enable the USS to make the decision of change of USS. + +The UAE client may also trigger an immediate/autonomous change of USS, but only in emergency situations. + +- 6) The UAE server can, based on UAV tracking information from SEAL LMS and detection of UAV mobility to the DNAI associated with the USS, inform the USS about possible change of USS. Based on this, the USS can initiate a change of USS. +- 7) For cases where UAE server cannot determine the conditions for change of USS, the UAE server relies on UAE client assistance as above. +- 8) The UAE server performs traffic influence for the change of USS. + +### 9.2.4 Evaluation of key issue #3: Coordination between Uu and PC5 for direct UAV-to-UAV or UAV-to-UAV-C communication + +Key Issue #3 outlines the following to be investigated: + +- 1) How the UAE layer can be enhanced to make coordination between network based communication (Uu) and direct communication (PC5) for communications between UAVs or between UAV and UAV-C. + +Due to the overlap between Key Issue #1 and Key Issue #3, a common solution for both Kis are provided. + +Solution #3 is selected as the basis for normative work, based on the following principles and with the following constraints: + +- 1) Provision of enhancement of C2 related functionality. +- 2) Allowance of PC5 feasibility monitoring. + +This solution is dependent on the support for ProSe/PC5 for C2 communication, see 3GPP TR 23.700-58 [6]. + +This solution will be considered feasible only if the concluded solution in 3GPP TR 23.700-58 [6] works in the same manner as required by the solution specified in clause 7.5. + +Enhancements to the procedures in of 3GPP TS 23.255 [3] clause 7.4.2 to fulfill the objectives of this solution will be considered during normative work (if concluded). + +### 9.2.5 Evaluation of key issue #4: Support for detect and avoid services and applications + +Key Issue #4 outlines the following to be investigated: + +- a) Whether and how the UAE layer and/or SEAL services can be enhanced to support DAA services and applications for collision avoidance considering the Stage 1 requirements. +- b) How the UAE layer can support DAA scenarios where UAVs belong to multiple PLMNs. + +Solution #4 addresses bullet a) by including provisioning of the policy for DAA from the UAS server via the UAE layer to the UAS application and support from the UAE layer to the DAA decision making process in the UAS client. + +Bullet b) is also supported by Solution #4 by the fact that both the UAS application layer and the UAE layer are PLMN-agnostic. + +Solution #5 addresses bullet a) where UAE server provides capabilities for real-time UAV(s) tracking by the UAS application specific server or UAV. The UAS application specific server can provide an application defined area or proximity range with respect to a host UAV to obtain host UAV dynamic information which includes the information of other UAVs in the proximity range which can be a potential collision object for the host UAV. This information is utilized by UASS or the UAV to manage the DAA scenario. The application process of DAA is up to the UAV client and the UASS (UTM/USS) and how they use the UAE layer provided information is out of scope of the specification. + +Solution#5 addresses bullet b) where UAE server supports capabilities of UAV tracking for the UAVs which belong to any UAS operator or connected via any PLMN operator. + +Solution #4 and Solution 5 are selected as the basis for normative work, based on the following UAE layer assisted / USS controlled principles: + +- 1) The DAA capability of the UAE client is provided to the server. +- 2) The UAS client, the UAE client and the UAE server are provided with DAA policies from the USS. +- 3) UAE layer will support providing information for the DAA decision making process. +- 4) The UAS application specific server can provide application defined area or proximity range and detects potential collision object for a host UAV in flight. + +The UAS application layer is always in control of the decision for DAA. + +# --- 10 Conclusions + +## 10.1 Architecture enhancements + +There is no architecture enhancement described in this Technical Report, see subclause 9.1. + +## 10.2 Solutions + +The overall evaluation of Key Issue #1, is described in clause 9.2.2. This refer to selection of Solution #3 as the basis for normative work. + +The overall evaluation of Key Issue #2 is described in clause 9.2.3. This refer to selection of Solution #1 and solution #2 as the basis for normative work. + +The overall evaluation of Key Issue #3 is described in clause 9.2.4. This refer to selection of Solution #3 as the basis for normative work. + +The overall evaluation of Key Issue #4 is described in clause 9.2.5. This refer to selection of Solution #4 and Solution 5 as the basis for normative work. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2021-10 | SA6#45-bis-e | | | | | TS skeleton (version 0.0.0) approved in S6-212198
Implementation of the following pCRs approved by SA6:
S6-212199, S6-212200 | | 0.1.0 | +| 2021-11 | SA6#46-e | | | | | Implementation of the following pCRs approved by SA6:
S6-212717, S6-212833 | | 0.2.0 | +| 2022-02 | SA6#47-e | | | | | Implementation of the following pCRs approved by SA6:
S6-220286, S6-220287, S6-220471 | | 0.3.0 | +| 2022-04 | SA6#48-e | | | | | Implementation of the following pCRs approved by SA6:
S6-220814, S6-220821, S6-220964 | | 0.4.0 | +| 2022-05 | SA6#49-e | | | | | Implementation of the following pCRs approved by SA6:
S6-221321, S6-221323, S6-221325, S6-221326, S6-221471 | | 0.5.0 | +| 2022-07 | SA6#49-bis-e | | | | | Implementation of the following pCR approved by SA6:
S6-221868 | | 0.6.0 | +| 2022-09 | SA6#50-e | | | | | Implementation of the following pCRs approved by SA6:
S6-222151, S6-222365, S6-222366, S6-222424, S6-222587, S6-222603 | | 0.7.0 | +| 2022-09 | SA#97-e | SP-220910 | | | | Presentation for information at SA#97-e | | 1.0.0 | +| 2022-10 | SA6#51-e | | | | | Implementation of the following pCR approved by SA6:
S6-222773 | | 1.1.0 | +| 2022-11 | SA6#52 | | | | | Implementation of the following pCRs approved by SA6:
S6-223100, S6-223221, S6-223580, S1-223590, S6-223615, S6-223620 | | 1.2.0 | +| 2022-11 | SA6#52 | | | | | Update of ToC | | 1.2.1 | +| 2022-12 | SA#98-e | SP-221221 | | | | Submitted for Approval at SA#98-e | | 2.0.0 | +| 2022-12 | SA#98-e | SP-221221 | | | | MCC Editorial update for publication after TSG SA approval
(SA#98-e) | | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-62/raw.md b/raw/rel-18/23_series/23700-62/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0c84f08bd7dee29bc0fdd16f1354df859c793fc9 --- /dev/null +++ b/raw/rel-18/23_series/23700-62/raw.md @@ -0,0 +1,3319 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on UPF enhancement for Exposure and SBA (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font. The 'G' has a red signal wave icon below it. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions of terms, symbols and abbreviations..... | 10 | +| 3.1 Terms..... | 10 | +| 3.2 Symbols..... | 10 | +| 3.3 Abbreviations ..... | 10 | +| 4 Architectural Assumptions and Requirements..... | 10 | +| 4.1 Architectural Assumptions..... | 10 | +| 4.2 Architectural Requirements..... | 10 | +| 5 Key Issues ..... | 11 | +| 5.1 Key Issue #1: Study UPF event exposure service registration and discovery ..... | 11 | +| 5.1.1 Description ..... | 11 | +| 5.2 Key Issue #2: Support UPF expose information to other NFs..... | 11 | +| 5.2.1 General description..... | 11 | +| 6 Solutions..... | 12 | +| 6.0 Mapping of Solutions to Key Issues ..... | 12 | +| 6.1 Solution #1: UPF event exposure service framework enhancements to support registration, deregistration and discovery via NRF..... | 12 | +| 6.1.1 Description ..... | 12 | +| 6.1.2 Procedures ..... | 13 | +| 6.1.2.1 UPF Event Exposure service Registration..... | 13 | +| 6.1.2.2 UPF Event Exposure service Update..... | 14 | +| 6.1.2.3 UPF Event Exposure service Deregistration ..... | 15 | +| 6.1.2.4 UPF Event Exposure service Discovery..... | 15 | +| 6.1.2.5 UPF Selection for a UPF Event Exposure Service Request..... | 16 | +| 6.1.2.5.1 Procedure of UPF selection by the NF targeting PDU session or UE with information of IP address..... | 16 | +| 6.1.2.5.2 Procedure of UPF selection by the NF targeting PDU session or UE with information of SUPI, S-NSSAI and DNN..... | 18 | +| 6.1.2.5.3 Procedure of UPF selection by the NF with information of S-NSSAI, DNN and/or DNAI ..... | 20 | +| 6.1.2.5.4 Procedure of UPF selection by the NF targeting specific PDU sessions and UEs with information of Group Identifier..... | 21 | +| 6.1.3 Impacts on services, entities and interfaces..... | 21 | +| 6.2 Solution #2: ..... | 22 | +| 6.2.1 Key Issue mapping ..... | 22 | +| 6.2.2 Description ..... | 22 | +| 6.2.3 Procedures ..... | 22 | +| 6.2.3.1 TSN AF/TSCTSF based UPF event subscription..... | 23 | +| 6.2.3.2 SMF based UPF event subscription..... | 23 | +| 6.2.3.3 Bridge information reporting ..... | 24 | +| 6.2.3.4 Analysis of directly reporting TSC management information..... | 25 | +| 6.2.4 Impacts on services, entities and interfaces..... | 26 | +| 6.3 Solution #3: using the proper subscription mechanism depending on the event targeted by the UPF event consumer..... | 27 | +| 6.3.1 Key Issue mapping ..... | 27 | +| 6.3.2 Description ..... | 27 | +| 6.3.3 Procedures ..... | 29 | +| 6.3.4 selection of the proper UPF within the UPF(s) that serve a PDU Session..... | 29 | +| 6.3.5 Impacts on services, entities and interfaces..... | 29 | +| 6.4 Solution #4: upgrading N4 to pass necessary event filtering information to the UPF ..... | 30 | +| 6.4.1 Key Issue mapping ..... | 30 | +| 6.4.2 Description ..... | 30 | + +| | | | +|----------|----------------------------------------------------------------------------------------------------------|----| +| 6.4.3 | Procedures ..... | 30 | +| 6.4.4 | Impacts on services, entities and interfaces..... | 31 | +| 6.5 | Solution #5: registering UPF(s) serving a PDU session at UDM ..... | 31 | +| 6.5.1 | Key Issue mapping ..... | 31 | +| 6.5.2 | Description ..... | 31 | +| 6.5.3 | Procedures ..... | 32 | +| 6.5.4 | Impacts on services, entities and interfaces..... | 33 | +| 6.6 | Solution #6: Determining the UPF(s) that serve a UE address ..... | 33 | +| 6.6.1 | Key Issue mapping ..... | 33 | +| 6.6.2 | Description ..... | 33 | +| 6.6.3 | Procedures ..... | 34 | +| 6.6.4 | Impacts on services, entities and interfaces..... | 34 | +| 6.7 | Solution #7: Support to existing (Rel-16-Rel-17) data analytics with PDU Session Data Usage Events ..... | 35 | +| 6.7.1 | Key Issue mapping ..... | 35 | +| 6.7.2 | Description ..... | 35 | +| 6.7.3 | Procedures ..... | 36 | +| 6.7.3.1 | Subscription to UPF for Data Collection for "Any UE" ..... | 36 | +| 6.7.3.2 | Subscription to UPF for Data Collection for certain PDU Sessions..... | 37 | +| 6.7.4 | Impacts on services, entities and interfaces..... | 39 | +| 6.8 | Solution #8: Support to existing (Rel-16-Rel-17) data analytics with QoS Flow level measurements ..... | 40 | +| 6.8.1 | Key Issue mapping ..... | 40 | +| 6.8.2 | Description ..... | 40 | +| 6.8.3 | Procedures ..... | 41 | +| 6.8.4 | Impacts on services, entities and interfaces..... | 43 | +| 6.9 | Solution #9 to Key Issue 2: NWDAF collects information from UPF by event exposure ..... | 44 | +| 6.9.1 | Mapping table between Analytics ID and the related information collection in UPF ..... | 44 | +| 6.9.2 | Service based UPF event exposure..... | 45 | +| 6.9.3 | Procedure ..... | 47 | +| 6.9.3.1 | UPF data collection for single UE ..... | 47 | +| 6.9.3.2 | UPF data collection for any UE ..... | 48 | +| 6.9.4 | Impacts on services, entities and interfaces..... | 50 | +| 6.10 | Solution #10: UPF event exposure service to NWDAF..... | 51 | +| 6.10.1 | Key Issue mapping ..... | 51 | +| 6.10.2 | Description ..... | 51 | +| 6.10.3 | Procedures ..... | 51 | +| 6.10.4 | Impacts on services, entities and interfaces..... | 53 | +| 6.11 | Solution #11: UPF event exposure service to NWDAF subscribed directly from UPF ..... | 53 | +| 6.11.1 | Key Issue mapping ..... | 53 | +| 6.11.2 | Description ..... | 53 | +| 6.11.3 | Procedures ..... | 53 | +| 6.11.4 | Impacts on services, entities and interfaces..... | 54 | +| 6.12 | Solution #12: UPF registration to the NRF and NWDAF collecting data from UPF ..... | 55 | +| 6.12.1 | Key Issue mapping ..... | 55 | +| 6.12.2 | Description ..... | 55 | +| 6.12.3 | Procedures ..... | 55 | +| 6.12.3.1 | Procedure for UPF Registration to NRF ..... | 55 | +| 6.12.3.2 | Procedure for NWDAF collecting data from UPF ..... | 56 | +| 6.12.4 | Impacts on services, entities and interfaces..... | 56 | +| 6.13 | Solution #13: Subscription to UPF Event Exposure Services in the event of UP Path change ..... | 57 | +| 6.13.1 | Key Issue mapping ..... | 57 | +| 6.13.2 | Description ..... | 57 | +| 6.13.3 | Procedures ..... | 57 | +| 6.13.4 | Impacts on services, entities and interfaces..... | 58 | +| 6.14 | Solution #14: Reduce the UPF performance impacts due to data reporting to NF consumer ..... | 58 | +| 6.14.1 | Key Issue mapping ..... | 58 | +| 6.14.2 | Description ..... | 58 | +| 6.14.3 | Procedures ..... | 59 | +| 6.14.4 | Impacts on services, entities and interfaces..... | 59 | +| 6.15 | Solution #15: Subscription of UPF Event Exposure Service ..... | 59 | +| 6.15.1 | Key Issue mapping ..... | 59 | +| 6.15.2 | Description ..... | 60 | +| 6.15.3 | Procedures ..... | 60 | + +| | | | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| 6.15.3.1 | UPF Event Exposure using NEF ..... | 60 | +| 6.15.3.1.1 | Procedure of UPF service operations information flow ..... | 60 | +| 6.15.3.1.2 | Procedure of UPF information in BSF ..... | 60 | +| 6.15.4 | Impacts on services, entities and interfaces ..... | 61 | +| 6.16 | Solution #16: Direct/indirect subscription of the UPF event exposure service ..... | 61 | +| 6.16.1 | Key Issue mapping ..... | 61 | +| 6.16.2 | Description ..... | 61 | +| 6.16.3 | Procedures ..... | 62 | +| 6.16.3.1 | UPF event exposure service subscription directly from the UPF ..... | 62 | +| 6.16.3.2 | UPF event exposure service subscription via an SMF ..... | 63 | +| 6.16.4 | Impacts on services, entities and interfaces ..... | 64 | +| 6.17 | Solution #17: Update/Release subscription of the UPF event exposure service ..... | 64 | +| 6.17.1 | Key Issue mapping ..... | 64 | +| 6.17.2 | Description ..... | 64 | +| 6.17.3 | Procedures ..... | 64 | +| 6.17.3.1 | Update/release UPF event exposure service subscription directly by UPF ..... | 64 | +| 6.17.3.2 | Update/release UPF event exposure service subscription via an SMF ..... | 65 | +| 6.17.4 | Impacts on services, entities and interfaces ..... | 66 | +| 6.18 | Solution #18: QoS parameters exposure by UPF ..... | 67 | +| 6.18.1 | Key Issue mapping ..... | 67 | +| 6.18.2 | Description ..... | 67 | +| 6.18.3 | Procedures ..... | 67 | +| 6.18.4 | Impacts on services, entities and interfaces ..... | 68 | +| 6.19 | Solution #19: QoS Monitoring results exposure by UPF ..... | 68 | +| 6.19.1 | Key Issue mapping ..... | 68 | +| 6.19.2 | Description ..... | 68 | +| 6.19.3 | Procedures ..... | 68 | +| 6.19.3.1 | QoS Monitoring results subscription directly from the UPF under the same PCF policy ..... | 68 | +| 6.19.3.2 | QoS Monitoring results subscription directly from the UPF without PCF policy control ..... | 69 | +| 6.19.4 | Impacts on services, entities and interfaces ..... | 70 | +| 6.20 | Solution #20: UE IP address mapping information exposure by UPF ..... | 70 | +| 6.20.1 | Key Issue mapping ..... | 70 | +| 6.20.2 | Description ..... | 70 | +| 6.20.3 | Procedures ..... | 71 | +| 6.20.3.1 | UPF registration in NRF with NATed IP pools ..... | 71 | +| 6.20.3.2 | UE IP address mapping information exposure by UPF ..... | 71 | +| 6.20.4 | Impacts on services, entities and interfaces ..... | 72 | +| 6.21 | Solution #21: UPF Event Exposure with consideration on UPF performance ..... | 72 | +| 6.21.1 | Key Issue mapping ..... | 72 | +| 6.21.2 | Description ..... | 72 | +| 6.21.3 | Procedures ..... | 73 | +| 6.21.4 | Impacts on services, entities and interfaces ..... | 73 | +| 6.22 | Solution #22: Support UPF event exposure service subscription update in case of UPF/SMF change ..... | 73 | +| 6.22.1 | Key Issue mapping ..... | 73 | +| 6.22.2 | Description ..... | 73 | +| 6.22.3 | Procedures ..... | 74 | +| 6.22.3.1 | The consumer NF subscribes SMF/UPF change notification from the SMF ..... | 74 | +| 6.22.3.2 | The consumer NF subscribes UPF change notification from the BSF by storing UPF ID and UE IP address in the BSF in PDU Session Establishment procedure ..... | 75 | +| 6.22.4 | Impacts on services, entities and interfaces ..... | 76 | +| 7 | Overall Evaluation ..... | 76 | +| 7.1 | Overall Evaluation of solutions for Key Issue #1 ..... | 76 | +| 7.2 | Evaluation for KI#2 ..... | 77 | +| 8 | Conclusions ..... | 80 | +| 8.1 | Conclusions for Key Issue #1 ..... | 80 | +| 8.2 | Conclusions for KI#2 ..... | 80 | +| Annex A: | Analysis on the NWDAF requirements of UPF event exposure service(s) ..... | 83 | +| Annex B: | Change history ..... | 87 | + + + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The Technical Report studies on key issue description, solution and conclusion on the support of better integration of UPF into the 5GC SBA. The objectives include: + +- Study UPF event exposure service(s) registration/deregistration, and discovery via the NRF. +- Study UPF event exposure service(s) that would support, e.g.: + - Consumption of UPF exposure services by the PCF, NWDAF, CHF, NEF, Trusted AF and other NFs (if needed). + - (To support the UPF exposure service, if needed) Use of SMF services, PCF services, NWDAF services, CHF services, NEF services, Trusted AF services by the UPF. + +NOTE 1: This will not define solutions where UPF exposes information that it is not originator of, i.e. not re-expose information owned and exposed by other NFs. + +- Relevant Event IDs. +- Evaluate usage of UPF event exposure service(s) as defined in WT#2 also considering the architectural impacts. + +NOTE 2: SMF is responsible for controlling UPF packet processing. + +NOTE 3: The performance of UP traffic handling shall not be degraded due to mechanisms defined in this study. + +NOTE 4: The study shall address generic UPF data exposure mechanisms via SBA based mechanisms, and the coordination with other SIDs for this aspect may be needed in study phase. + +This study shall maintain the Rel-17 backward compatibility on the N3, N6, N9, N4 interfaces. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System (5GS); Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2". +- [5] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [6] 3GPP TS 29.510: "Network Function Repository Services; Stage 3". +- [7] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [8] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane nodes". +- [9] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3". + +- [10] 3GPP TR 23.700-48: "5G System Enhancements for Edge Computing". +- [11] 3GPP TS 24.519: " Time-Sensitive Networking (TSN) Application Function (AF) to Device-Side TSN Translator (DS-TT) and Network-Side TSN Translator (NW-TT) protocol aspects, Stage 3". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +            + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +    + +# --- 4 Architectural Assumptions and Requirements + +## 4.1 Architectural Assumptions + +The architecture and framework as specified in TS 23.501 [2], TS 23.502 [3], and TS 23.503 [4] are regarded as the baseline for the present study: + +- The SMF is responsible for controlling UPF packet processing. +- The UPF can only expose 5GC information which is originated in the UPF. + +## 4.2 Architectural Requirements + +Solutions shall build on the 5G System architectural principles as in TS 23.501 [2], including flexibility and modularity for newly introduced functionalities: + +- The performance of UPF user plane traffic handling shall not be degraded due to mechanisms defined in this study. +- The Rel-18 N6, N4 interface shall be based on the existing interface design and backward compatible. No impact is introduced on N3, N9 interfaces from this study. + +NOTE: This study is limited to event exposure, and thus interfaces can only be impacted due to this study. + +- The usage of direct UPF event exposure for exposure of some data when these data are already available via usage of SMF + N4 needs to be justified. + +- Some aspects as following should be considered when the solution evaluation is proposed: + - The co-existence for the UPF supporting UPEAS feature and UPF supporting Rel-17 (i.e. not supporting the feature) should be considered. + +# --- 5 Key Issues + +## 5.1 Key Issue #1: Study UPF event exposure service registration and discovery + +### 5.1.1 Description + +This KI maps to the WT1 of the SID. + +The KI will study the registration and discovery of UPF event exposure service(s). The following aspects should be studied: + +- How to support UPF event exposure service(s) registration/deregistration on NRF, and what parameters to be registered in the NF profile of UPF. +- How to support UPF service discovery via the NRF, and what parameters that can be used for discovery. +- How to support UPF selection for a UPF event exposure service request targeting a specific UE or a specific PDU session. + +This key issue is not meant to define for which UPF event / exposed information a direct consumer subscription to the UPF would take place (if any). + +NOTE: The information to be registered to the NRF is related to the UPF event exposure service requirement. + +## 5.2 Key Issue #2: Support UPF expose information to other NFs + +### 5.2.1 General description + +To enable flexible communication between UPF and other 5GC NFs, the UPF can expose network information to NFs through UPF event exposure service. + +In Release 17, TS 23.548 [7] has supported that UPF can expose QoS monitoring results to local NEF. In Release 18, we need further study whether UPF can also expose other useful information to other NFs to optimize the network performance. + +The key issue is to identify use cases for UPF event exposure (including the related Event Id) and for each use case determine whether the consumer directly contacts the UPF for its subscription or whether the consumer goes via an intermediate function like the SMF. + +The following aspects should be studied to support UPF event exposure service(s): + +- How and what specific information the UPF can expose to NWDAF so NWDAF can provide existing (Rel-16, Rel-17) data analytics as specified in TS 23.288 [5]. Support of New Rel-18 data analytics per the Rel-18 FS\_eNA\_Ph3 may also be considered in alignment with that study +- How and what specific information the UPF can expose to NEF/Local NEF/trusted AF, e.g. the information which can be exposed in Rel-18 SA WG2 studies such as FS\_EDGE\_Ph2 and FS\_XRM, or information which has been justified for exposure. + +NOTE: The Relevant Event IDs of the UPF event exposure services above can be introduced. + +- Whether PCF, CHF, and other NFs need to invoke UPF event exposure service. If yes, how and what specific information the UPF can expose to these NFs. +- Whether the consumer NF directly subscribes the UPF or not. If yes, how to authorize the consumer NF for subscribing to UPF event exposure services via Nupf, and how to update/release the subscription. + +# 6 Solutions + +## 6.0 Mapping of Solutions to Key Issues + +**Table 6.0-1: Mapping of Solutions to Key Issues** + +| Solutions | | | +|---------------------------------------------------------------------------------------------------------------------|----------------|----------------| +| | | | +| #1: UPF event exposure service framework enhancements to support registration, deregistration and discovery via NRF | X | | +| #2: UPF event exposure service for TSC management | | X | +| #3: using the proper subscription mechanism depending on the event targeted by the UPF event consumer | | X | +| #4: upgrading N4 to pass necessary event filtering information to the UPF | | X | +| #5: registering UPF(s) serving a PDU session at UDM | | X | +| #6: Determining the UPF(s) that serve a UE address | | X | +| #7: Support to existing (Rel-16-Rel-17) data analytics with PDU Session Data Usage Events | | X | +| #8: Support to existing (Rel-16-Rel-17) data analytics with QoS Flow level measurements | | X | +| #9: NWDAF collects information from UPF by event exposure | | X | +| #10: UPF event exposure service to NWDAF | | X | +| #11: UPF event exposure service to NWDAF subscribed directly from UPF | | X | +| #12: UPF registration and NWDAF collecting data from UPF | X | X | +| #13: Subscription to UPF Event Exposure Services in the event of UP Path change | | X | +| #14: Reduce the UPF performance impacts due to data reporting to NF consumer | | X | +| #15: Subscription of UPF Event Exposure Service | | X | +| #16: Direct/indirect subscription of the UPF event exposure service | | X | +| #17: Update/Release subscription of the UPF event exposure service | | X | +| #18: QoS parameters exposure by UPF | | X | +| #19: QoS Monitoring results exposure by UPF | | X | +| #20: UE IP address mapping information exposure by UPF | | X | +| #21: UPF Event Exposure with consideration on UPF performance | | X | +| #22: Support UPF event exposure service subscription update in case of UPF/SMF change | | X | + +## 6.1 Solution #1: UPF event exposure service framework enhancements to support registration, deregistration and discovery via NRF + +### 6.1.1 Description + +The solution introduces the service based UPF event exposure framework to support registration, deregistration and discovery via NRF. The following Figure 6.1.2-1 depicts the service-based interface Nupf introduced in the 5G system architecture. + +The solution for registering UPF in NRF is based on the option in the existing solution described in clause 6.3.3.2 of TS 23.501 [2] and clause 4.17 of TS 23.502 [3], whereby the UPF registers directly with the NRF and hence does not use N4 for registering to NRF. + +NOTE 1: As described in TS 23.501 [2], the NRF can alternatively be configured by OAM with information on the available UPF(s) or the UPF instance(s) may register its/their NF profile(s) in the NRF. + +![Figure 6.1.1-1: 5G system architecture with service based UPF. The diagram shows a 5G system architecture with a Service Based Interface (SBI) represented by a horizontal bus. Above the bus are Network Functions (NFs): NSSF, NEF, NRF, PCF, UDM, AF, and NWDAF, connected via their respective service interfaces (Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnwdaf). Below the bus are other NFs: NSSAAF, AUSF, AMF, SMF, SCP, and NSACF, connected via NnssAAF, Nausf, Nanf, Nsmf, and Nnsacf. The User Equipment (UE) connects to the (R)AN, which connects to the AMF via N1 and N2 interfaces. The AMF connects to the UPF via the N3 interface. The UPF connects to the DN via the N6 interface and has an additional N9 interface. A red line labeled 'Nupf' indicates a service-based interface between the UPF and the NRF.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +Figure 6.1.1-1: 5G system architecture with service based UPF. The diagram shows a 5G system architecture with a Service Based Interface (SBI) represented by a horizontal bus. Above the bus are Network Functions (NFs): NSSF, NEF, NRF, PCF, UDM, AF, and NWDAF, connected via their respective service interfaces (Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnwdaf). Below the bus are other NFs: NSSAAF, AUSF, AMF, SMF, SCP, and NSACF, connected via NnssAAF, Nausf, Nanf, Nsmf, and Nnsacf. The User Equipment (UE) connects to the (R)AN, which connects to the AMF via N1 and N2 interfaces. The AMF connects to the UPF via the N3 interface. The UPF connects to the DN via the N6 interface and has an additional N9 interface. A red line labeled 'Nupf' indicates a service-based interface between the UPF and the NRF. + +**Figure 6.1.1-1: 5G system architecture with service based UPF** + +NOTE 2: Figure 6.1.1-1 shows an example of UPF with Nupf service. In the context of this solution the UPF is in the role of consumer of NRF services, i.e. this solution is about how UPF can register its NF profile in NRF with related Nupf service information and does not describe services provided by the UPF itself. + +The solution also addresses UPF selection for a UPF event exposure service request targeting specific UEs and specific PDU sessions. + +### 6.1.2 Procedures + +#### 6.1.2.1 UPF Event Exposure service Registration + +The following Figure 6.1.2.1-1 depicts the UPF Event Exposure service Registration procedure. + +![Sequence diagram for UPF Event Exposure service Registration procedure](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` +sequenceDiagram + participant UPF + participant NRF + Note right of NRF: 2. Store UPF profile + UPF->>NRF: 1. Nnrf_NFManagement_NFRegister_request + NRF-->>UPF: 3. Nnrf_NFManagement_NFRegister_response +``` + +The diagram illustrates the registration procedure between a UPF and an NRF. The UPF sends a registration request to the NRF. The NRF then stores the UPF profile, indicated by a self-call message. Finally, the NRF sends a registration response back to the UPF. + +Sequence diagram for UPF Event Exposure service Registration procedure + +**Figure 6.1.2.1-1: UPF Event Exposure service Registration procedure** + +1. The UPF sends the Nnrf\_NFManagement\_NFRegister Request message to NRF to inform the NRF of its NF profile when the NF service consumer becomes operative for the first time. The existing UPF NF profile parameters include e.g. S-NSSAI(s) and the associated NSI ID(s), DNN(s), IP range, information about the location of the UPF (operator specific information, e.g. geographical location, data centre), UPF Service Area (TAI List), DNAI, as described in TS 29.510 [6]. In addition, to support UPF Event Exposure Service, also Event Exposure Service Name, Supported Event ID(s) are provided with the UPF NF profile. +2. The NRF stores the UPF profile and marks the UPF Event Exposure service as available. +3. The NRF acknowledge UPF Registration is accepted via Nnrf\_NFManagement\_NFRegister response. + +#### 6.1.2.2 UPF Event Exposure service Update + +The following Figure 6.1.2.2-1 depicts the UPF Event Exposure service Update procedure. + +![Sequence diagram for UPF Event Exposure service Update procedure](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` +sequenceDiagram + participant UPF + participant NRF + Note right of NRF: 2. Update UPF profile + UPF->>NRF: 1. Nnrf_NFManagement_NFUpdate_request + NRF-->>UPF: 3. Nnrf_NFManagement_NFUpdate_response +``` + +The diagram illustrates the update procedure between a UPF and an NRF. The UPF sends an update request to the NRF. The NRF then updates the UPF profile, indicated by a self-call message. Finally, the NRF sends an update response back to the UPF. + +Sequence diagram for UPF Event Exposure service Update procedure + +**Figure 6.1.2.2-1: UPF Event Exposure service Update procedure** + +1. UPF sends Nnrf\_NFManagement\_NFUpdate Request message (the updated NF profile of NF service consumer) to NRF to inform the NRF of its updated UPF profile. +2. The NRF updates the NF profile of UPF instance. +3. The NRF acknowledge UPF Update is accepted via Nnrf\_NFManagement\_NFUpdate response. + +#### 6.1.2.3 UPF Event Exposure service Deregistration + +The following Figure 6.1.2.3-1 depicts the UPF Event Exposure service Deregistration procedure. + +![Sequence diagram of UPF Event Exposure service Deregistration procedure](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +``` +sequenceDiagram + participant UPF + participant NRF + Note right of NRF: 2. Mark UPF as unavailable/Remove NF profile + UPF->>NRF: 1. Nnrf_NFManagement_NFDeregister_request + NRF-->>UPF: 3. Nnrf_NFManagement_NFDeregister_response +``` + +The diagram illustrates the interaction between the UPF and the NRF for service deregistration. It consists of three steps: 1. The UPF sends a 'Nnrf\_NFManagement\_NFDeregister\_request' message to the NRF. 2. The NRF performs an internal action to 'Mark UPF as unavailable/Remove NF profile', shown in a box. 3. The NRF sends a 'Nnrf\_NFManagement\_NFDeregister\_response' message back to the UPF. + +Sequence diagram of UPF Event Exposure service Deregistration procedure + +**Figure 6.1.2.3-1: UPF Event Exposure service Deregistration procedure** + +1. UPF sends Nnrf\_NFManagement\_NFDeregister Request message to NRF to inform the NRF of its unavailability. +2. The NRF marks the UPF unavailable. NRF may remove the NF profile of UPF according to NF management policy. +3. The NRF acknowledge NF Deregistration is accepted via Nnrf\_NFManagement\_NFDeregister response. + +#### 6.1.2.4 UPF Event Exposure service Discovery + +The following Figure 6.1.2.4-1 depicts the UPF Event Exposure service Discovery procedure. + +![Sequence diagram of UPF Event Exposure service Discovery procedure](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` +sequenceDiagram + participant Consumer of UPF Event Exposure Service + participant NRF + Note right of NRF: 2. Authorize UPF Event Exposure Service Discovery + Consumer of UPF Event Exposure Service->>NRF: 1. Nnrf_NFDiscovery_request + NRF-->>Consumer of UPF Event Exposure Service: 3. Nnrf_NFDiscovery_response +``` + +The diagram illustrates the interaction between a 'Consumer of UPF Event Exposure Service' and an 'NRF'. The sequence of messages is as follows: 1. The consumer sends an 'Nnrf\_NFDiscovery\_request' to the NRF. 2. The NRF performs an internal authorization step labeled 'Authorize UPF Event Exposure Service Discovery'. 3. The NRF then sends an 'Nnrf\_NFDiscovery\_response' back to the consumer. + +Sequence diagram of UPF Event Exposure service Discovery procedure + +**Figure 6.1.2.4-1: UPF Event Exposure service Discovery procedure** + +1. Service consumer NF that requires UPF services invokes Nnrf\_NFDiscovery\_Request message to NRF with the intent to discover UPF. The input may include e.g. UPF service name, Event ID(s), TAI, NF type (i.e. UPF), S-NSSAI, DNN, DNAI, as described in TS 29.510 [6]. +2. The NRF authorizes the Nnrf\_NFDiscovery\_Request and based on the UPF profile the NRF determines if the service consumer of the UPF is allowed to discover the UPF. +3. If allowed, the NRF determines a set of UPFs matching the input parameters included in the Nnrf\_NFDiscovery\_Request to the service consumer of the UPF via Nnrf\_NFDiscovery\_Request\_Response. The output includes one or more UPF instances, and for each UPF instance it includes UPF NF profile. + +#### 6.1.2.5 UPF Selection for a UPF Event Exposure Service Request + +##### 6.1.2.5.1 Procedure of UPF selection by the NF targeting PDU session or UE with information of IP address + +There are different alternatives to find UPF when the consumer NF targets a specific PDU session or UE with information of IP address. + +This solution is applied to discover PSA UPF where only the IP address provided to the UE can be used, i.e. the UE IP address stored in BSF. + +Figure 6.1.2.5.1-1 shows one first alternative: + +![Sequence diagram for Figure 6.1.2.5.1-1 showing the procedure of UPF selection by the NF targeting PDU session or UE with information of IP address. The diagram involves three participants: AF/NEF, PCF, and SMF. Step 1: AF/NEF sends a message to PCF: '1. Find out the address of the relevant PCF, the PCF response the SMF list'. Step 2: AF/NEF sends a message to SMF: '2. Nsmf_EventExposure subscribe'. Step 3: SMF sends a message to AF/NEF: '3. Nsmf_EventExposure Notify'.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` + +sequenceDiagram + participant AF/NEF + participant PCF + participant SMF + Note over AF/NEF, PCF: 1. Find out the address of the relevant PCF, the PCF response the SMF list + AF/NEF->>SMF: 2. Nsmf_EventExposure subscribe + SMF-->>AF/NEF: 3. Nsmf_EventExposure Notify + +``` + +Sequence diagram for Figure 6.1.2.5.1-1 showing the procedure of UPF selection by the NF targeting PDU session or UE with information of IP address. The diagram involves three participants: AF/NEF, PCF, and SMF. Step 1: AF/NEF sends a message to PCF: '1. Find out the address of the relevant PCF, the PCF response the SMF list'. Step 2: AF/NEF sends a message to SMF: '2. Nsmf\_EventExposure subscribe'. Step 3: SMF sends a message to AF/NEF: '3. Nsmf\_EventExposure Notify'. + +**Figure 6.1.2.5.1-1: Procedure of UPF selection by the NF targeting PDU session or UE with information of IP address** + +1. If the consumer NF is an AF/NEF, it can use the UE IP address to discover the PCF from the BSF. Then the PCF can send response with the SMF for the PDU session to the AF/NEF. +2. The AF/NEF interacts with the SMF that responded by the PCF in step 1 to obtain the appropriate UPF information for PDU Session over the Nsmf\_EventExposure\_Subscribe service operation providing UE IP address and if available IP domain. + +NOTE 1: The solution assumes there is no NAT between the EAS/AF and the UPF. + +NOTE 2: The SMF Event Exposure service may be extended with new event (e.g. UPF ID). + +3. The SMF responds Nsmf\_EventExposure\_Notify with the list of UPFs for the User PDU Session. + +Figure 6.1.2.5.1-2 below shows second alternative: + +![Sequence diagram for Figure 6.1.2.5.1-2 showing the procedure of UPF selection by the NF targeting PDU session or UE through UPF registration information in NRF. The diagram involves three participants: AF/NEF, NRF, and UPF. Step 0: UPF sends a message to NRF: '0. UPF Event Exposure service Registration'. Step 1: AF/NEF sends a message to NRF: '1. Nnrf_NFDiscovery_Request request'. Step 2: NRF sends a message to AF/NEF: '2. Nnrf_NFDiscovery_Request response'.](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) + +``` + +sequenceDiagram + participant AF/NEF + participant NRF + participant UPF + Note over NRF, UPF: 0. UPF Event Exposure service Registration + AF/NEF->>NRF: 1. Nnrf_NFDiscovery_Request request + NRF-->>AF/NEF: 2. Nnrf_NFDiscovery_Request response + +``` + +Sequence diagram for Figure 6.1.2.5.1-2 showing the procedure of UPF selection by the NF targeting PDU session or UE through UPF registration information in NRF. The diagram involves three participants: AF/NEF, NRF, and UPF. Step 0: UPF sends a message to NRF: '0. UPF Event Exposure service Registration'. Step 1: AF/NEF sends a message to NRF: '1. Nnrf\_NFDiscovery\_Request request'. Step 2: NRF sends a message to AF/NEF: '2. Nnrf\_NFDiscovery\_Request response'. + +**Figure 6.1.2.5.1-2: Procedure of UPF selection by the NF targeting PDU session or UE through UPF registration information in NRF** + +0. The UPF sends its supported IP range (and IP domain if needed) in the NF profile provided to the NRF during the NF registration. The NF profile also contains the address of the UPF Event Exposure service. + +1. If the consumer NF is an AF/NEF, the AF/NEF issues an Nnrf\_NFDiscovery\_Request service operation to find the appropriate UPF providing NF type (i.e. UPF) and UE IP address and if needed IP domain. +2. The NRF responds Nnrf\_NFDiscovery\_Request with the NF profiles of all UPFs that currently meet the AF/NEF discovery request. + +In a third alternative: + +![Sequence diagram showing the procedure of UPF selection by the NF targeting PDU session or UE with information of IP address using BSF. The diagram shows five network functions: BSF, AF/NEF, NRF, UDM, and SMF. The AF/NEF sends a message '1. Find out SUPI for the IP Address' to the BSF. The BSF then sends a message 'Apply for SUPI 6.1.2.5.2-1' to the AF/NEF, NRF, UDM, and SMF.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` +sequenceDiagram + participant BSF + participant AF/NEF + participant NRF + participant UDM + participant SMF + Note right of AF/NEF: 1. Find out SUPI for the IP Address + AF/NEF->>BSF: + BSF->>AF/NEF: + BSF->>NRF: + BSF->>UDM: + BSF->>SMF: + Note right of AF/NEF: Apply for SUPI 6.1.2.5.2-1 +``` + +Sequence diagram showing the procedure of UPF selection by the NF targeting PDU session or UE with information of IP address using BSF. The diagram shows five network functions: BSF, AF/NEF, NRF, UDM, and SMF. The AF/NEF sends a message '1. Find out SUPI for the IP Address' to the BSF. The BSF then sends a message 'Apply for SUPI 6.1.2.5.2-1' to the AF/NEF, NRF, UDM, and SMF. + +**Figure 6.1.2.5.1-3: Procedure of UPF selection by the NF targeting PDU session or UE with information of IP address using BSF** + +1. If the consumer NF is an AF/NEF, the AF/NEF uses UE IP address (and if needed IP domain) to obtain the SUPI from the BSF. +2. Procedure of UPF selection by the NF targeting PDU sessions of a certain UE with information of SUPI in 6.1.2.5.2-1 is applied. + +##### 6.1.2.5.2 Procedure of UPF selection by the NF targeting PDU session or UE with information of SUPI, S-NSSAI and DNN + +This solution is applied to discover central PSA UPF, local PSA UPF and distributed PSA UPF. + +![Sequence diagram illustrating the procedure of UPF selection by the NF targeting PDU sessions of a certain UE with information of SUPI, S-NSSAI and DNN. The diagram shows interactions between cNF, NRF, UDM, and SMF.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant cNF + participant NRF + participant UDM + participant SMF + + Note right of UDM: 4. Determines SMF + + cNF->>NRF: 1. Nnrf_NFDiscovery_Request request + NRF-->>cNF: 2. Nnrf_NFDiscovery_Request response + cNF->>UDM: 3. Nudm_UECM_Get request + UDM->>SMF: 4. Determines SMF + UDM-->>cNF: 5. Nudm_UECM_Get service + cNF-->>NRF: 6. Nnrf_NFDiscovery_Request request + NRF-->>cNF: 7. Nnrf_NFDiscovery_Request response + cNF->>SMF: 8. Nsmf_EventExposure_Subscribe + SMF-->>cNF: 9. Nsmf_EventExposure_Notify + +``` + +Sequence diagram illustrating the procedure of UPF selection by the NF targeting PDU sessions of a certain UE with information of SUPI, S-NSSAI and DNN. The diagram shows interactions between cNF, NRF, UDM, and SMF. + +**Figure 6.1.2.5.2-1: Procedure of UPF selection by the NF targeting PDU sessions of a certain UE with information of SUPI, S-NSSAI and DNN** + +1. The consumer NF (e.g. an NWDAF), issues an Nnrf\_NFDiscovery\_Request service operation to find the UDM providing the NF type, UE ID (SUPI). +2. The NRF responds Nnrf\_NFDiscovery\_Request with the NF profile of the UDM that currently meet the consumer NF discovery request. +3. The consumer NF issues an Nudm\_UECM\_Get request to find the SMF from UDM providing NF type, UE ID (SUPI), S-NSSAI, DNN. +4. The UDM finds the serving SMF for the UE providing SUPI, S-NSSAI, and DNN, as described in TS 23.502 [3]. +5. The UDM responds the SMF ID over Nudm\_UECM\_Get service response to the consumer NF. +- 6-7 The consumer NF contacts NRF to get the SMF exposure service contact information for SMF ID unless it has it already. +8. The consumer NF obtains UPF information from the SMF provided by the UDM over the Nsmf\_EventExposure\_Subscribe service operation providing SUPI, S-NSSAI, and DNN. + +If for a PDU session, the consumer NF needs to subscribe only to PSA UPFs on a given DNAI, it may provide DNAI in the request to SMF as input filter. If the consumer NF needs to subscribe only to the UPFs that will steer traffic of an App id or application flow, it may provide them in the request to SMF as input filter. SMF will return information of UPFs that may see that traffic according to its knowledge. + +NOTE: Some rules may have been predefined in UPF, and SMF may only be aware of the rules that it has provisioned in UPF itself. + +9. The SMF responds Nsmf\_EventExposure\_Notify with the requested UPF ID and the type of UPF. + +If the User PDU Session UP path changes, SMF may send a notification to consumer NF according to the subscription. Consumer NF can then create, update or remove the subscription to UPF event exposure service according to the impact on the UPF selection. + +##### 6.1.2.5.3 Procedure of UPF selection by the NF with information of S-NSSAI, DNN and/or DNAI + +![Sequence diagram showing the procedure of UPF selection by the NF with information of S-NSSAI, DNN and/or DNAI. The diagram involves three lifelines: NF, NRF, and UPF. The sequence starts with step 0: UPF sends a message to NRF labeled '0. UPF Event Exposure service Registration'. Then, step 1: NF sends a message to NRF labeled '1. Nnrf_NFDiscovery_Request request'. Finally, step 2: NRF sends a response back to NF labeled '2. Nnrf_NFDiscovery_Request response'.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` +sequenceDiagram + participant NF + participant NRF + participant UPF + Note right of NRF: 0. UPF Event Exposure service Registration + NF->>NRF: 1. Nnrf_NFDiscovery_Request request + NRF-->>NF: 2. Nnrf_NFDiscovery_Request response +``` + +Sequence diagram showing the procedure of UPF selection by the NF with information of S-NSSAI, DNN and/or DNAI. The diagram involves three lifelines: NF, NRF, and UPF. The sequence starts with step 0: UPF sends a message to NRF labeled '0. UPF Event Exposure service Registration'. Then, step 1: NF sends a message to NRF labeled '1. Nnrf\_NFDiscovery\_Request request'. Finally, step 2: NRF sends a response back to NF labeled '2. Nnrf\_NFDiscovery\_Request response'. + +**Figure 6.1.2.5.3-1: Procedure of UPF selection by the NF with information of S-NSSAI, DNN and/or DNAI** + +0. The UPF sends its S-NSSAI, DNN, DNAI, UPF Service Area, Supported Event ID(s) to the NRF during the UPF Event Exposure service registration procedure as described in clause 6.1.2.1. +1. The consumer NF (for example, NWDAF) issues an Nnrf\_NFDiscovery\_Request service operation to find the appropriate UPF providing NF type (i.e. UPF), S-NSSAI, DNN, DNAI and Event ID(s). +2. The NRF responds Nnrf\_NFDiscovery\_Request with the list of all UPFs that currently meet the request. + +##### 6.1.2.5.4 Procedure of UPF selection by the NF targeting specific PDU sessions and UEs with information of Group Identifier + +Two procedures are possible: + +![Sequence diagram showing the procedure of UPF selection by the NF with information of Group Identifier. The diagram involves four lifelines: NWDAF, NRF, UDM, and SMF. The sequence of messages is: 1. Nnrf_NFDiscovery_Request request from NWDAF to NRF; 2. Nnrf_NFDiscovery_Request response from NRF to NWDAF; 3. Nudm_SDM_Get request from NWDAF to UDM; 4. Nudm_SDM_Get response from UDM to NWDAF. A large box below the UDM response indicates that steps 3-7 of the procedure in Figure 6.1.2.5.2-1 are performed for each SUPI.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +``` + +sequenceDiagram + participant NWDAF + participant NRF + participant UDM + participant SMF + Note right of SMF: 4. Steps 3-7 of procedure with Figure 6.1.2.5.2-1 are performed for each SUPI + +``` + +Sequence diagram showing the procedure of UPF selection by the NF with information of Group Identifier. The diagram involves four lifelines: NWDAF, NRF, UDM, and SMF. The sequence of messages is: 1. Nnrf\_NFDiscovery\_Request request from NWDAF to NRF; 2. Nnrf\_NFDiscovery\_Request response from NRF to NWDAF; 3. Nudm\_SDM\_Get request from NWDAF to UDM; 4. Nudm\_SDM\_Get response from UDM to NWDAF. A large box below the UDM response indicates that steps 3-7 of the procedure in Figure 6.1.2.5.2-1 are performed for each SUPI. + +**Figure 6.1.2.5.4-1: Procedure of UPF selection by the NF with information of Group Identifier** + +1. If the consumer NF is an NWDAF, the NWDAF issues an Nnrf\_NFDiscovery\_Request service operation to find the UDM providing the NF type and Group ID. +2. The NRF responds Nnrf\_NFDiscovery\_Request with the NF profile of the UDM that currently meets the NWDAF discovery request. + +NOTE: It is assumed that all members of a Group ID belong to the same UDM. + +3. NWDAF requests the list of SUPIs that correspond to the Group ID using Nudm\_SDM\_Get. +4. UDM returns the list of SUPIs. +5. For each SUPI, NWDAF triggers from step 3 of procedure in clause 6.1.2.5.2. + +As an alternative, UPF(s) can be selected as described in clause 6.1.2.5.3. with procedure of UPF selection by the NF with information of S-NSSAI, DNN and/or DNAI. The Group ID is included as target in the subscription request to the UPFs that determine the specific target PDU Sessions, if any, in that UPF. + +### 6.1.3 Impacts on services, entities and interfaces + +SMF: + +- Determine the UPF that serves the target UEs in the scope of any UE according to parameters of NWDAF IP address, DNN, S-NSSAI. +- Nsmf Event Exposure Subscription needs to be enhanced to support exposing the information of UPF(s) that matches a PDU session and notify any changes according to subscription. + +NRF: + +- Discovery of several UPFs that accords with the UE IP address or IP range/domain. + +AF/NEF: + +- Invoke the BSF using the UE address (i.e. IP address or MAC address), DNN, S-NSSAI as discovery criteria. + +UDM: + +- Newly introduce UDM event consumers (e.g. NWDAF). + +PCF: + +- Update Npcf\_SMPolicyControl service so that PCF receives and can store the SMF ID for the policy association. +- Update the Npcf\_EventExposure service for PCF to send the SMF ID for the PDU session to the AF/NEF. + +## 6.2 Solution #2: + +### 6.2.1 Key Issue mapping + +This solution addresses KI 2. + +### 6.2.2 Description + +The SMF and UPF may exchange TSC management information container, such as the user plane node Management Information Container (UMIC) and Port Management Information Container (PMIC) over an N4 session. However, Port management information is transferred transparently via 5GS between TSN AF or TSCTSF and DS-TT in UE or NW-TT in UPF, respectively, inside a PMIC. User plane node management information is transferred transparently via 5GS between TSN AF or TSCTSF and NW-TT in UPF inside a UMIC. As a result, in order for TSC management information to be directly provided to TSN AF or TSCTSF by NW-TT in UPF, the UPF event exposure service should be invoked. TSC management information can thus be exposed to TSN AF or TSCTSF via the UPF. + +NOTE: Transferring TSC management information from TSN AF/TSCTSF to NW-TT/UPF is outside the scope of this solution. + +**Table 6.2.2-1: NF Services provided by UPF** + +| Service Name | Description | Example Consumer(s) | +|--------------------|----------------------------------------------------------|---------------------| +| Nupf_EventExposure | This UPF service provide the support for event exposure. | TSN AF, TSCTSF | + +Nupf\_EventExposure service enables an NF (e.g. TSN AF or TSCTSF) to subscribe and get notified about UPF events for TSC management information. The following service operations are defined for the Nupf\_EventExposure service: + +- Nupf\_EventExposure\_Subscribe. +- Nupf\_EventExposure\_UnSubscribe. +- Nupf\_EventExposure\_Notify. + +The TSC management information event can be notified to TSN AF or TSCTSF. This UPF event notification may contain PMIC(s) and/or UMIC along with the associated NW-TT port number as described in clauses 5.8.2.11.14 and 5.28.3 of TS 23.501 [2]. TSN AF or TSCTSF subscribes and receives event notifications if specific port management information for a NW-TT port changes or user plane node management information changes. In other words, the UPF notifies TSN AF or TSCTSF if port management information or user plane node management information has changed that TSN AF or TSCTSF has subscribed for. + +### 6.2.3 Procedures + +In this solution, procedures are proposed to (un)subscribe/notify the UPF event for TSC management information. The UPF is selected for a PDU Session serving TSC as described in clause 6.3.3.3 of TS 23.501 [2]. TSN AF or TSCTSF + +can identify the PDU session during the PDU session establishment procedure. Then, UPF/NW-TT triggers the N4 Session Level Reporting Procedure to forward the PMIC(s) and/or UMIC to SMF. + +Two methods are proposed for subscribing UPF event exposure service as follows: + +- TSN AF or TSCTSF subscribes the UPF event (Figure 6.2.3.1-1). +- Instead of TSN AF or TSCTSF, SMF subscribes the UPF event (Figure 6.2.3.2-1). + +#### 6.2.3.1 TSN AF/TSCTSF based UPF event subscription + +This clause describes the procedure for TSN AF or TSCTSF to (un)subscribe the UPF event and receive the event notification for TSC management information. TSN AF or TSCTSF can apply the procedure of UPF selection by the NF targeting PDU session specified in clause 6.1.2.5.1 in solution #1 to discover the UPF with the PDU session. + +![Sequence diagram illustrating UPF event exposure based on TSN AF/TSCTSF subscription. The diagram shows three main entities: TSN AF, TSCTSF, and UPF. The sequence starts with a common procedure for UPF selection. Then, TSN AF sends a NUpf_EventExposure_(Un)Subscribe message to the UPF. TSCTSF also sends a similar message. The UPF then triggers an event notification. Finally, the UPF sends NUpf_EventExposure_Notify messages to both TSN AF and TSCTSF.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +``` + +sequenceDiagram + participant TSN_AF as TSN AF + participant TSCTSF + participant UPF + Note over TSN_AF, TSCTSF, UPF: 0. Procedure of UPF selection by the NF targeting PDU session in Figure 6.1.2.5.1-1 or 6.1.2.5.1-2 of Solution #1 + TSN_AF->>UPF: 1a. NUpf_EventExposure_(Un)Subscribe (TSC management information) + TSCTSF->>UPF: 1b. NUpf_EventExposure_(Un)Subscribe (TSC management information) + Note right of UPF: 2. Trigger to report TSC management information event + UPF->>TSN_AF: 3a. NUpf_EventExposure_Notify (TSC management information) + UPF->>TSCTSF: 3b. NUpf_EventExposure_Notify (TSC management information) + +``` + +Sequence diagram illustrating UPF event exposure based on TSN AF/TSCTSF subscription. The diagram shows three main entities: TSN AF, TSCTSF, and UPF. The sequence starts with a common procedure for UPF selection. Then, TSN AF sends a NUpf\_EventExposure\_(Un)Subscribe message to the UPF. TSCTSF also sends a similar message. The UPF then triggers an event notification. Finally, the UPF sends NUpf\_EventExposure\_Notify messages to both TSN AF and TSCTSF. + +**Figure 6.2.3.1-1: UPF event exposure based on TSN AF/TSCTSF subscription** + +0. Procedure of UPF selection by the NF targeting PDU session in Solution #1 is performed. +1. TSN AF or TSCTSF sends Nupf\_EventExposure\_(Un)scribe service operation for TSC management information event to the UPF. +2. The event notification is triggered if there are changes in UMIC/PMIC from the UPF/NW-TT or the PDU session is released. +3. UPF sends the event notification for TSC management information over Nupf\_EventExposure\_Notify service operation to TSN AF or TSCTSF. + +#### 6.2.3.2 SMF based UPF event subscription + +This clause describes how SMF can (un)subscribe the UPF event so that TSN AF or TSCTSF receives the event notification for TSC management information. The PDU Session Establishment as defined clause 4.3.2.2.1-1 of TS 23.502 [3] is used to establish a PDU Session serving for TSC. During this procedure, the SMF selects a UPF for the PDU Session that supports functions as defined in clause 5.28.1 of TS 23.501 [2]. As a result, the SMF may subscribe to the UPF event as a result of the PCF initiated SM Policy Association Modification as described in Figure 4.16.5.2-1 of TS 23.502 [3], rather TSN AF or TSCTSF. + +![Sequence diagram illustrating UPF event exposure based on SMF subscription. The diagram shows interactions between TSN AF, TSCTSF, PCF, SMF, and UPF. Steps include: 1a. Npcf_PolicyAuthorization_Subscribe (TSN events) from TSN AF to PCF; 1b. Npcf_PolicyAuthorization_Subscribe (TSC events) from TSCTSF to PCF; 2. Npcf_SMPolicyControl_UpdateNotify from PCF to SMF; 3a. Nupf_EventExposure_(Un)Subscribe (TSC management information event) from SMF to UPF; 3b. N4 Session Modification (TSC management information, Direct reporting information) from SMF to UPF; 4. Trigger TSC management information event (internal to UPF); 5a. NUpf_EventExposure_Notify (TSC management information) from UPF to TSN AF; 5b. NUpf_EventExposure_Notify (TSC management information) from UPF to TSCTSF.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant TSN AF + participant TSCTSF + participant PCF + participant SMF + participant UPF + + Note left of TSN AF: 1a. Npcf_PolicyAuthorization_Subscribe (TSN events) + TSN AF->>PCF: 1a. Npcf_PolicyAuthorization_Subscribe (TSN events) + Note left of TSCTSF: 1b. Npcf_PolicyAuthorization_Subscribe (TSC events) + TSCTSF->>PCF: 1b. Npcf_PolicyAuthorization_Subscribe (TSC events) + Note right of PCF: 2. Npcf_SMPolicyControl_UpdateNotify + PCF->>SMF: 2. Npcf_SMPolicyControl_UpdateNotify + SMF->>UPF: 3a. Nupf_EventExposure_(Un)Subscribe (TSC management information event) + SMF->>UPF: 3b. N4 Session Modification (TSC management information, Direct reporting information) + Note right of UPF: 4. Trigger TSC management information event + UPF->>TSN AF: 5a. NUpf_EventExposure_Notify (TSC management information) + UPF->>TSCTSF: 5b. NUpf_EventExposure_Notify (TSC management information) + +``` + +Sequence diagram illustrating UPF event exposure based on SMF subscription. The diagram shows interactions between TSN AF, TSCTSF, PCF, SMF, and UPF. Steps include: 1a. Npcf\_PolicyAuthorization\_Subscribe (TSN events) from TSN AF to PCF; 1b. Npcf\_PolicyAuthorization\_Subscribe (TSC events) from TSCTSF to PCF; 2. Npcf\_SMPolicyControl\_UpdateNotify from PCF to SMF; 3a. Nupf\_EventExposure\_(Un)Subscribe (TSC management information event) from SMF to UPF; 3b. N4 Session Modification (TSC management information, Direct reporting information) from SMF to UPF; 4. Trigger TSC management information event (internal to UPF); 5a. NUpf\_EventExposure\_Notify (TSC management information) from UPF to TSN AF; 5b. NUpf\_EventExposure\_Notify (TSC management information) from UPF to TSCTSF. + +**Figure 6.2.3.2-1: UPF event exposure based on SMF subscription** + +1. TSN AF or TSCTSF subscribes for TSN/TSC events using the `Npcf_PolicyAuthorization_Subscribe` operation. Subscription indicates that UPF direct report of TSC management information is preferred. +2. If the PCF has received indication that UPF direct report is preferred or a Port Management Information Container for the PDU Session and related port number from the TSN AF or TSCTSF, the PCF issues a `Npcf_SMPolicyControl_UpdateNotify` request with possibly updated policy information about the PDU Session and/or target address for the notification when UPF direct report is preferred. Then, the SMF acknowledges the PCF request with a `Npcf_SMPolicyControl_UpdateNotify` response. +3. SMF sends `Nupf_EventExposure_(Un)scribe` service operation for TSC management information event to the UPF. As an alternative, the SMF may configure direct reporting information (refer to the clause 7.5.2.9 of TS 29.244 [8]) on the UPF using N4 Session Modification procedure. + +NOTE: If the SMF does not configure direct reporting information during N4 Session Modification procedure (i.e. the UPF does not support direct reporting to TSN AF or TSCTSF), the UPF reports TSC management information to the SMF via the N4 interface. + +4. The event notification is triggered if there are changes in UMIC/PMIC from the UPF/NW-TT or the PDU session is released. +5. UPF sends the event notification for TSC management information over `Nupf_EventExposure_Notify` service operation to TSN AF or TSCTSF. + +#### 6.2.3.3 Bridge information reporting + +During the SM Policy Association Establishment procedure, if the PCF detects the request relates to SM Policy Association enabling integration with TSN or TSC, the PCF may provide policy control request trigger for 5GS Bridge Information. TSN AF can (un)subscribe TSC management information events to the UPF using the methods given above in this scenario. + +![Sequence diagram illustrating UPF event exposure during 5GS Bridge information reporting. The diagram shows interactions between UE/DS-TT, (R)AN, AMF, SMF, UPF/NW-TT, PCF, and AF. Step 1 is the PDU Session Establishment procedure. Step 2a is SMF initiated SM Policy Association Modification. Step 2b is Npcf_PolicyAuthorization_Notify. Step 2c is Npcf_PolicyAuthorization_Create. Step 2d is Npcf_PolicyAuthorization_Subscribe. Step 3a is UPF event exposure based on TSN AF/TSCTSF subscription procedure. Step 3b is UPF event exposure based on SMF subscription procedure.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant UE/DS-TT + participant (R)AN + participant AMF + participant SMF + participant UPF/NW-TT + participant PCF + participant AF + + Note over all: 1. PDU Session Establishment procedure in Figure 4.3.2.2.1-1 + SMF->>PCF: 2a. SMF initiated SM Policy Association Modification + PCF->>AF: 2b. Npcf_PolicyAuthorization_Notify + PCF->>AF: 2c. Npcf_PolicyAuthorization_Create + PCF->>AF: 2d. Npcf_PolicyAuthorization_Subscribe + Note over AF: 3a. UPF event exposure based on TSN AF/TSCTSF subscription procedure in Figure 6.2.3.1 -1 + Note over AF: 3b. UPF event exposure based on SMF subscription procedure in Figure 6.2.3.2 -1 steps from 2 to 5 + +``` + +Sequence diagram illustrating UPF event exposure during 5GS Bridge information reporting. The diagram shows interactions between UE/DS-TT, (R)AN, AMF, SMF, UPF/NW-TT, PCF, and AF. Step 1 is the PDU Session Establishment procedure. Step 2a is SMF initiated SM Policy Association Modification. Step 2b is Npcf\_PolicyAuthorization\_Notify. Step 2c is Npcf\_PolicyAuthorization\_Create. Step 2d is Npcf\_PolicyAuthorization\_Subscribe. Step 3a is UPF event exposure based on TSN AF/TSCTSF subscription procedure. Step 3b is UPF event exposure based on SMF subscription procedure. + +**Figure 6.2.3.3-1: UPF event exposure during 5GS Bridge information reporting** + +The procedure of 5GS Bridge information reporting in Figure F.1-1 of TS 23.502 [3] is performed with the following differences and clarifications: + +1. PDU Session Establishment as defined clause 4.3.2.2.1-1 of TS 23.502 [3] is used to establish a PDU Session serving for TSC. +2. The SMF sends the information received in step 1 to the TSN AF or TSCTSF via PCF to establish/modify the 5GS Bridge. The TSN AF or TSCTSF subscribes for TSN events over the newly created AF session using the Npcf\_PolicyAuthorization\_Subscribe operation (step 2d). + +The TSN AF can use any PDU Session to subscribe with the NW-TT for bridge or port management information notifications. Similarly, the UPF can use any PDU Session to send bridge or port management information notifications. + +3. The procedure of UPF event exposure in Figure 6.2.3.1-1 or steps from 2 to 5 of Figure 6.2.3.2-1 is performed to use UPF exposure service for TSC management information between the UPF and TSN AF. + +The TSN AF or TSCTSF may additionally provide an indication of event notification which contains a Notification Target Address when subscribing for TSN/TSC events to the PCF. The QoS Monitoring information may include an indication of local event notification which contains a Notification Target Address in a similar manner. According to clause 5.8.2.11.11 of TS 23.501 [2], the UPF reports the QoS Monitoring information via Nupf\_EventExposure\_Notify service operation, as indicated by the indication of local event notification. Therefore, the TSN AF or TSCTSF requests the UPF to directly report TSC management information event via Nupf\_EventExposure\_Notify service operation by either adding the indication of event notification in TSC management information or subscribing to the event notification via Nupf\_EventExposure\_Subscribe. + +#### 6.2.3.4 Analysis of directly reporting TSC management information + +UPF/NW-TT reports TSC management information event using the N4 Session Level Reporting procedure as specified in clause 4.4.2.2 of TS 23.502 [3]. The UPF shall give the TSC management information, as defined in clause 6.2.2, to the SMF when it detects the TSC management information event that needs to be reported. The SMF then initiates the SM Policy Association Modification procedure as described in clause 4.16.5.1 of TS 23.502 [3]. If the SMF has reported TSC management information, such as PMIC with port number or UMIC, then the PCF transparently transports the received PMIC and the related port number or UMIC to the TSN AF or TSCTSF as described in clauses 6.1.3.23 and 6.1.3.23a of TS 23.503 [4]. + +The definition of 5GS Bridge information is included in Table 6.1.3.5-1 of TS 23.503 [4], which may contain user-plane Node ID, UE-DS-TT residence time and Ethernet port or IP address for the PDU Session and/or PMIC and/or UMIC. Two procedures are introduced to handle 5GS Bridge information: 5GS Bridge information reporting in Figure F.1-1 of TS 23.502 [3] and 5GS Bridge configuration in Figure F.2-1 of TS 23.502 [3]. TSC management information is delivered by TSN AF or TSCTSF to configure TSC management information in UPF/NW-TT in a 5GS Bridge + +configuration. The 5G Bridge information reporting is connected to the reporting of TSC management information from UPF/NW-TT to TSN AF or TSCTSF from the perspective of the UPF event exposure service. + +![Sequence diagram for 5GS Bridge information reporting [3]. The diagram shows interactions between UE/DS-TT, (R)AN, AMF, SMF, UPF/NW-TT, PCF, and AF. The sequence starts with a PDU Session Establishment procedure. Step 2a shows SMF initiating an SM Policy Association Modification to UPF/NW-TT. Step 2b shows UPF/NW-TT sending Npcf_PolicyAuthorization_Notify to AF. Step 2c shows UPF/NW-TT sending Npcf_PolicyAuthorization_Create to AF. Step 2d shows UPF/NW-TT sending Npcf_PolicyAuthorization_Subscribe to AF. Step 3 shows TSN AF providing TSN Time domain number to DS-TT and optionally to NW-TT. Step 4 shows TSN AF retrieving txPropagationDelay from DS-TT and NW-TT. Step 5 shows TSN AF sending NW-TT port neighbor discovery configuration and DS-TT port neighbor discovery configuration to NW-TT and optionally DS-TT, and subscribing for receiving neighbor discovery information for each discovered neighbor of NW-TT and DS-TT. Step 6 shows TSN AF receiving notifications about neighbors of NW-TT and DS-TT. Step 7 shows AF registering or updating 5GS Bridge to TSN CP.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +``` + +sequenceDiagram + participant UE/DS-TT + participant (R)AN + participant AMF + participant SMF + participant UPF/NW-TT + participant PCF + participant AF + + Note over UE/DS-TT, AF: 1. PDU Session Establishment procedure in Figure 4.3.2.2.1-1 + Note over SMF, UPF/NW-TT: 2a. SMF initiated SM Policy Association Modification + Note over UPF/NW-TT, AF: 2b. Npcf_PolicyAuthorization_Notify + Note over UPF/NW-TT, AF: 2c. Npcf_PolicyAuthorization_Create + Note over UPF/NW-TT, AF: 2d. Npcf_PolicyAuthorization_Subscribe + Note over TSN AF, DS-TT: 3. TSN AF provides TSN Time domain number to DS-TT and optionally to NW-TT + Note over TSN AF, DS-TT: 4. TSN AF retrieves txPropagationDelay from DS-TT and NW-TT + Note over TSN AF, NW-TT: 5. TSN AF sends NW-TT port neighbor discovery configuration and DS-TT port neighbor discovery configuration to NW-TT and optionally DS-TT and subscribes for receiving neighbor discovery information for each discovered neighbor of NW-TT and DS-TT + Note over TSN AF, NW-TT: 6. TSN AF receives notifications about neighbors of NW-TT and DS-TT + Note over AF, TSN CP: 7. Register or update 5GS Bridge to TSN CP + +``` + +Sequence diagram for 5GS Bridge information reporting [3]. The diagram shows interactions between UE/DS-TT, (R)AN, AMF, SMF, UPF/NW-TT, PCF, and AF. The sequence starts with a PDU Session Establishment procedure. Step 2a shows SMF initiating an SM Policy Association Modification to UPF/NW-TT. Step 2b shows UPF/NW-TT sending Npcf\_PolicyAuthorization\_Notify to AF. Step 2c shows UPF/NW-TT sending Npcf\_PolicyAuthorization\_Create to AF. Step 2d shows UPF/NW-TT sending Npcf\_PolicyAuthorization\_Subscribe to AF. Step 3 shows TSN AF providing TSN Time domain number to DS-TT and optionally to NW-TT. Step 4 shows TSN AF retrieving txPropagationDelay from DS-TT and NW-TT. Step 5 shows TSN AF sending NW-TT port neighbor discovery configuration and DS-TT port neighbor discovery configuration to NW-TT and optionally DS-TT, and subscribing for receiving neighbor discovery information for each discovered neighbor of NW-TT and DS-TT. Step 6 shows TSN AF receiving notifications about neighbors of NW-TT and DS-TT. Step 7 shows AF registering or updating 5GS Bridge to TSN CP. + +**Figure 6.2.3.4-1: 5GS Bridge information reporting [3]** + +Step 2a of Figure 6.2.3.4-1 involves the SMF initiating SM Policy Association modification, and step 2b shows the PCF delivering the Npcf\_PolicyAuthorization\_Notify message to the TSN AF or TSCTSF. The PCF transmits 5GS Bridge information to the TSN AF or TSCTSF when it has the 5GS Bridge information received from SMF and has a subscription for the 5GS Bridge information Notification from the TSN AF or TSCTSF. The parameters in PMIC or UMIC are not handled by SMF/PCF during 5GS Bridge information reporting. With reference to steps 1 and 2 of Figure 6.2.3.4-1, the UPF/NW-TT can therefore provide event exposure services to directly report TSC management information events. + +### 6.2.4 Impacts on services, entities and interfaces + +#### UPF: + +- Needs to support UPF event exposure service operations for TSC management information. +- New event id for TSC management information is available to UPF. + +#### SMF: + +- (Optional) May support UPF event exposure service operations for TSC management information. + +#### PCF: + +- (Optional) May support UPF event exposure service operations for TSC management information by providing UPF direct reporting information to SMF. + +#### TSF AF / TSCTSF: + +- Needs to support UPF event exposure service operations for TSC management information. + +## 6.3 Solution #3: using the proper subscription mechanism depending on the event targeted by the UPF event consumer + +### 6.3.1 Key Issue mapping + +This solution addresses KI 2. + +### 6.3.2 Description + +The solution strives to ensure usage of the proper subscription mechanism depending on the event targeted by the UPF event consumer, assuming that in any case discussed in this clause the notifications are sent by the UPF using Nupf\_EventExposure Service. The UPF event consumer is the NF that will receive Nupf\_EventExposure\_Notify service operation; it may sometimes differ from the NF that provides the subscription request to the UPF. + +The analysis and technical mechanisms defined in solution 3, 4, 5 and 6 consider the R18 requirements that the UPF event consumer may be a NWDAF (per requirements expressed in TS 23.288 [5]), or an AF / a NEF requesting QoS related exposure (as being studied as part of R18: FS\_EDGE\_Ph2 or FS\_XRM). (future) Application of these solutions for other usage of UPF event exposure by NEF/ AF or for other UPF event consumers is not precluded. + +To determine the proper method to be used by the UPF event consumer to subscribe to UPF event notification, it is needed to take into account the target of the monitoring (one UE, ... any UE) as well as the filtering to apply to the events being reported (as recalled in Annex A): + +- A set of UPF(s) possibly for a Network Slice and / or DNN. +- A UE or a group of UEs or any UE in a Network Slice and / or DNN. +- An application, a set of IP flows. +- An Area of Interest (i.e. set of TAIs), as defined in TS 23.501 [2]. +- A RAT Type or Frequency or both. + +**NOTE:** The determination the proper method to be used by the UPF event consumer to subscribe to UPF event notification needs to take into account different aspects: on one hand direct subscription from the UPF event consumer to UPF can in some cases reduce the signalling load within the 5GC but on the other hand the SMF is aware of more information about a PDU Session than the UPF and such information may be required by event filtering; Requiring the SMF to keep UPF(s) up to date about information such as the TAI / Cell / RAT type / satellite backhaul serving a PDU Session would induce MUCH more signalling than the signalling gained by a direct subscription from final UPF event consumer. Making UPF aware of information such as the TAI / RAT type / satellite backhaul serving a PDU Session goes against the SDN principle that a simpler and efficient User plane entity should focus on packet switching, and should not be bothered by information only relevant for the Control Plane. + +For all mechanisms described below (except the mechanism in item 1) UPF(s) need to register their event exposure service onto NRF using Nnrf\_NFManagement as described in solution 1. + +Following mechanisms are considered with descending order of priority (if the UPF reporting does not meet conditions of item 1, then conditions of item 2 are evaluated, etc.) + +1. If the UPF event retrieval requires some action from the 5G AN / 5G RAN, as for NEF/ AF requesting QoS related exposure defined in Rel-17 for QoS monitoring, the UPF event consumer subscribes via the SMF. This ensures that the SMF can request 5G (R)AN action (such as reporting QoS information to the UPF) at N2 PDU session resource creation / modification e.g. after PDU Session UP (re)-establishment or after mobility (e.g. HandOver or mobility between 3GPP and Non 3GPP access). + - Potential Outputs from the Rel-18 Edge Computing Study requiring getting information from NG RAN are potential examples where such mechanism is needed. +2. If the event retrieval is associated with a UE location dependant filter (e.g. an Area of interest corresponding to a set of Tracking Areas or a RAT Type / an Access Type and/or a SSID/BSSID), the UPF event consumer + +subscribes via the SMF; This ensures that the SMF being already aware of ULI (User Location Information such Tracking Areas/ SSID/BSSID) and of RAT Type / Access Type can control whether UPF needs to report. + +NOTE: an alternative mechanism could have been envisaged: in order to ensure that the UPF can apply event subscription filters set by a direct NF consumer subscription to UPF events, the 5G AN would provide via GTP-u the UPF with following information associated with a GTP-u tunnel PDU Session: the associated ULI (TAI, cell id, etc.) RAT type, etc. Then the UPF would use this information to check whether some UPF event subscription filters match; if yes the UPF would start considering the corresponding traffic for the notifications related with the UPF event subscription. This kind of solution would impact the 5G AN which is forbidden by the FS\_UPEAS SID SP-211652. + +Examples where such mechanism is needed are: + +- Requirements within clause 6.11.1 of TS 23.288 [5] on "WLAN performance analytics requests" and recalled in item 5 of Annex A of this TR. + - The following Requirements when Analytics Filter Information includes a location (e.g. ECGI, TA) / an AoI: + - Requirements within Table 6.8.2-2 of TS 23.288 [5]: "Data Collected from the UPF or from the AF related to User Data Congestion Analytics requests" and recalled in item 3 of Annex A of this TR. + - Requirements within Table 6.10.2-5 of TS 23.288 [5]: "UE data volume dispersion collected from serving UPF" and recalled in item 4 of Annex A of this TR. + - Requirements within clause 6.14.1 of TS 23.288 [5] "User plane performance analytics" and recalled in item 7 of Annex A of this TR. +3. When the target of UPF event subscription is a UPF itself (possibly for a set of DNN and / or slice) the final NF consumer uses Nnrf\_NFDiscovery to discover the UPF (TS 29.510 [6] already supports discovering UPF(s) based on the DNN and or S-NSSAI they serve or based on UPF locality). N4 nevertheless needs to be upgraded as described in solution 4 in order for the UPF to be able to apply UPF event subscription filters on parameters such as the DNN: +- this mechanism applies e.g. to Table 6.5.2-2 of TS 23.288 [5]: "Data collected by NWDAF for UPF load analytics" recalled in item 2 of Annex A of this TR; + - for this kind of event the functionality of the UPF for a PDU Session (PSA, UL CL, simple forwarder) needs does not need to be considered. +4. When the Target of Analytics Reporting = a UE identified by a SUPI or by its address (and for IP a DNN + a S-NSSAI) it is needed to identify which UPF(s) serve the relevant PDU Sessions of the UE. + +This applies to following TS 23.288 [5] Requirements when the UE target is an Individual UE AND Analytics Filter Information does NOT include a location (e.g. ECGI, TA) / an AoI. For example: + +- Requirements within Table 6.8.2-2 of TS 23.288 [5]: "Data Collected from the UPF or from the AF related to User Data Congestion Analytics requests" and recalled in item 3 of Annex A of this TR. +- Requirements within Table 6.10.2-5 of TS 23.288 [5]: "UE data volume dispersion collected from serving UPF" and recalled in item 4 of Annex A of this TR. +- Requirements within TS 23.288 [5] clause 6.14.1 "User plane performance analytics" and recalled in item 7 of Annex A of this TR. +- TS 23.288 [5] Table 6.5.2-2: Data collected by NWDAF for UPF load analytics recalled in item 2 of Annex A of this TR. + +When the consumer of UPF event exposure can, within the UPF(s) that serve a target PDU Session, determine the proper UPF where to subscribe for event exposure (see clause 6.3.4): + +- The mechanism described in solution 6 is used when the target UE is identified by its SUPI. +- The mechanism described in solution 5 is used when the target UE is identified by its (IP or MAC) address. + +Otherwise the consumer of UPF event exposure requests the SMF controlling the target PDU session to subscribe to the proper UPF(s) on its behalf. + +5. When the Target of Analytics Reporting = Internal-Group Identifier (for a DNN + a S-NSSAI) it is needed to identify which UPF(s) serve the relevant PDU Sessions of the group. + +The final NF consumer uses Nnrf\_NFDiscovery to discover the UPF(s) serving a DNN + S-NSSAI. N4 nevertheless needs to be upgraded as described in solution 4 in order for the UPF to be able to apply UPF event subscription filters on Internal-Group Identifier. + +This applies for example to the same TS 23.288 [5] Requirements as defined in item 4 above when Analytics Filter Information does NOT include a location (e.g. ECGI, TA) / an AoI and the UE target is an Internal-Group Identifier. + +**Editor's note:** Subscribing onto all the UPF(s) that can serve a DNN + S-NSSAI for groups that involve very few users (hence a limited number of UPF(s)) is not efficient. It is FFS whether a more optimised solution is possible. + +### 6.3.3 Procedures + +The procedure of solution 1, solution 4, solution 5 and solution 6 may apply according to the analysis of clause 6.3.2. + +### 6.3.4 selection of the proper UPF within the UPF(s) that serve a PDU Session + +Some UPF (event) reporting target the UPF itself so any UPF that meets some criteria (e.g. UPF supporting a slice, in a locality) should be considered. + +Some UPF reporting relate to a target (application) flow so relate to the UPF(s) that supports this (application) traffic flow. For a PDU Session, only one UPF that handle such a traffic flow should be involved for the reporting, for example in following case: + +- (Annex A, item 1) The Observed Service Experience analytics may provide Service Experience for an Edge Application over a UP path: Service experience in an Application or a set of Applications over a specific UP path (UPF, DNAI and EC server). UPF needs to report observed bit rate, delay, number of packet transmission / retransmission. + +If no care is taken, then there is the risk of double counting: if UPF reporting is triggered at both the UL CL UPF and the PSA UPF that serve the target application flow within a PDU Session we incur following risks: + +- Counting twice where the UPF event consumer (NWDAF) would receive twice the information on the number of packet transmission and may assume twice the traffic. +- Doubling the signalling where the report about the observed bit rate, delay etc...would be sent by multiple (at least 2) UPF(s) for the same traffic. + +(This assumes deployments where the UL CL UPF and the PSA UPF are different UPF(s)). + +Furthermore, if the traffic handling of the target (application) flow is moved from old UPF(s) to new UPF(s) (UL CL and PSA relocation due e.g. to UE mobility) then if direct subscription to UPF reporting is done by the consumer (NWDAF) of UPF reporting, then this consumer becomes responsible of requesting the event reporting to the new UPF(s) in case of change of serving UPF. + +**NOTE:** Usage of solution 1, 5 or solution 6 depends on the type of analytics / exposure that the final UPF event consumer requires. Whether a PDU Session uses multiple UPF(s) (I-UPF, UL CL, different PSA) depends on SMF policies related with DNN+s-NSSAI as well as on UE mobility. Both aspects (the type of analytics / exposure versus usage of multiple UPF(s) for a PDU Session) are not related with each other, thus the issue of contacting the right UPF may take place when each of solution 1, solution 5 and solution 6 applies. + +### 6.3.5 Impacts on services, entities and interfaces + +Impacts depend on which of solution 1, solution 4, solution 5 and solution 6 applies. + +## 6.4 Solution #4: upgrading N4 to pass necessary event filtering information to the UPF + +### 6.4.1 Key Issue mapping + +This solution addresses KI 2. + +### 6.4.2 Description + +The UPF event consumer may, as defined in solution 3, be a NWDAF, an AF or a NEF. + +The solution runs as follows: + +- in order to ensure that the UPF can apply event subscription filters set in a subscription to UPF events, the SMF provides UPF with following information associated with an N4 Session: the associated DNN, S-NSSAI (already existing information), list of Internal-Group Identifiers (the UE subscription and hence the PDU /N4 Session may be associated with more than one Internal-Group Identifier). +- the UPF uses this information to check whether some UPF event subscription filters match; if yes the UPF starts considering the N4 session for the notifications related with this UPF event subscription. + +### 6.4.3 Procedures + +![Sequence diagram of N4 Session Establishment procedure between UPF and SMF.](a7585024ebe2bba8ac0757150a12759a_img.jpg) + +``` +sequenceDiagram + participant UPF + participant SMF + Note left of UPF: 0. Subscription to an UPF event with filters (e.g. Internal-Group Identifier) + UPF-->>SMF: + Note right of SMF: 1. Trigger to establish / modify PDU session or relocate UPF + SMF->>UPF: 2. N4 Session Establishment (or modification) Request with associated (e.g. Internal-Group Identifier) + UPF->>SMF: 3. N4 Session Establishment (or modification) Response + Note left of UPF: 4. Subscription to an UPF event with filters (e.g. Internal-Group Identifier) + UPF-->>SMF: + Note left of UPF: 5. Nupf_EventExposure_Notify + UPF->>UPF: +``` + +The diagram illustrates the N4 Session Establishment procedure between the UPF and the SMF. It consists of five steps: 0. Subscription to an UPF event with filters (e.g. Internal-Group Identifier) from an external source to the UPF; 1. Trigger to establish / modify PDU session or relocate UPF from the SMF; 2. N4 Session Establishment (or modification) Request with associated (e.g. Internal-Group Identifier) from the SMF to the UPF; 3. N4 Session Establishment (or modification) Response from the UPF to the SMF; 4. Subscription to an UPF event with filters (e.g. Internal-Group Identifier) from an external source to the UPF; 5. Nupf\_EventExposure\_Notify from the UPF to the external source. + +Sequence diagram of N4 Session Establishment procedure between UPF and SMF. + +Figure 6.4.3-1: N4 Session Establishment procedure + +0. The UPF may receive a subscription to event reporting with a filter criteria that may contain a DNN, a S-NSSAI, a User group identifier (this is the case where the UPF receives a subscription before the N4 session establishment). + +When UPF receives step 0 it needs to check whether there are already on-going N4 sessions that match the subscription filters. For these N4 sessions step 0 may immediately trigger step 5. + +1. SMF receives the trigger to establish a new PDU Session or change the UPF for an established PDU Session as in step 1 of TS 23.502 [3] Figure 4.4.1.2-1. + +2. The SMF sends an N4 session establishment request message to the UPF. The SMF provides UPF with following information associated with an N4 Session: the associated DNN, S-NSSAI, list of Internal-Group Identifiers; This step may also correspond to a N4 Session modification. +3. The UPF responds with an N4 session establishment (or modification) response Session as in step 3 of TS 23.502 [3] Figure 4.4.1.2-1. + +If the UPF (by configuration or other means) utilizes an NWDAF, UPF may provide the received information to its NWDAF. + +4. The UPF may receive a subscription to UPF event reporting with a filter criteria that may contain a DNN, a S-NSSAI, a User group identifier (this is the case where the UPF receives a subscription after the N4 session establishment). +5. Based on the received information in step 2, the UPF determines whether the N4 session matches the filter criteria of the subscription to UPF event reporting and if this is the case starts taking into account the PDU Session for such reporting. + +### 6.4.4 Impacts on services, entities and interfaces + +The solution impacts N4 (delivery of extra information such as DNN or Internal-Group Identifier) thus the SMF and the UPF. + +## 6.5 Solution #5: registering UPF(s) serving a PDU session at UDM + +### 6.5.1 Key Issue mapping + +This solution addresses KI 2. It addresses the case where the UPF event consumer desires to subscribe to UPF(s) event exposure and targets PDU Sessions involving a UE identified by its UE ID. + +### 6.5.2 Description + +The UPF event consumer may, as defined in solution 3, be a NWDAF, an AF or a NEF. + +The solution runs as follows: + +- The SMF updates the UDM/UDR with the list of UPF(s) serving a PDU Session via Nudm\_UECM service (Nudm\_UECM\_Registration and Nudm\_UECM\_Update when the UPF information changes). The information provided to the UDM may contain: + - The SUPI, DNN, S-NSSAI (already provided as part of Nudm\_UECM\_Registration). + - The set of address(es) used by the user equipment on the PDU Session; this needs to be refreshed when new UE MAC addresses are notified to the SMF or when the SMF allocates new prefixes in a multi-homed PDU session. + - The UPF instance Id of each UPF involved in the PDU Session. This information needs to allow the UPF event consumer to contact the NRF to discover the parameters needed to subscribe onto the UPF event exposure. + - the Type of UPF (UL CL, PSA, traffic forwarder, IPUPS) and the DNAI this UPF serves (for the PSA UPF). + +NOTE: The functionality of the UPF for the PDU Session (PSA, UL CL, simple forwarder, etc..) needs to be considered. Failure to do so may induce that the NWDAF considers multiple time the same traffic (e.g. at UL CL and at PSA) or does not request (delay, packet loss) statistics at the right place (which should be the PSA); see also clause 6.3.4. + +Editor's note: Whether the UPF information can be stored in the UDM is FFS. + +- The UPF event consumer invokes Nudm\_UECM\_Get to get the list of UPF serving a PDU session identified by the SUPI/GPSI, a DNN, a S-NSSAI and possibly an UE address (IP address or MAC address). +- The UDM provides the UPF instance Id of each UPF that matches the Nudm\_UECM\_Get. +- The UPF event consumer uses this information to get information on the UPF exposure service from NRF. +- The UPF event consumer subscribes to the UPF event exposure. +- The UPF notifies the UPF event consumer. + +### 6.5.3 Procedures + +![Sequence diagram illustrating the procedure for registering UPF(s) serving a PDU session at UDM. The diagram shows interactions between Final UPF event consumer, UDM, NRF, SMF, UPF, and UE. The sequence starts with UPF registering with NRF (0). Then, a PDU session establishment or mobility or new PCC rule occurs between UE and SMF (1). The SMF selects UPF(s) (2). The SMF registers or updates the PDU session on the UDM (2). The Final UPF event consumer invokes Nudm_UECM_Get (3). The UDM provides a response (4). The Final UPF event consumer invokes Nnrf_NFDiscovery_Request (5). The NRF provides a response (6). The Final UPF event consumer subscribes to the UPF event exposure (7). The UPF notifies the Final UPF event consumer (8).](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UPF + participant SMF + participant NRF + participant UDM + participant FUEC as Final UPF event consumer + + Note right of UPF: 0. Nnrf_NFManagement_NFRegister (UPF, UPF ID, exposure service, ...) + UPF->>NRF: 0. Nnrf_NFManagement_NFRegister (UPF, UPF ID, exposure service, ...) + Note right of UE: 1. PDU session establishment or mobility or new PCC rule + UE->>SMF: 1. PDU session establishment or mobility or new PCC rule + Note right of SMF: Select UPF(s) + SMF->>UPF: 1 N4 session establishment + Note right of SMF: 2. Nudm_UECM_Register or Nudm_UECM_Update (SMF ID, DNN, S-NSSAI, UE address, list of UPF information) + SMF->>UDM: 2. Nudm_UECM_Register or Nudm_UECM_Update (SMF ID, DNN, S-NSSAI, UE address, list of UPF information) + Note right of FUEC: 3. Nudm_UECM_Get (UE ID or UE address) + FUEC->>UDM: 3. Nudm_UECM_Get (UE ID or UE address) + Note right of UDM: 4. Nudm_UECM_Get Response (list of UPF information) + UDM->>FUEC: 4. Nudm_UECM_Get Response (list of UPF information) + Note right of FUEC: 5. Nnrf_NFDiscovery_Request (UPF, UPF ID) + FUEC->>NRF: 5. Nnrf_NFDiscovery_Request (UPF, UPF ID) + Note right of NRF: 6. Nnrf_NFDiscovery_Response (address, exposure service, ...) + NRF->>FUEC: 6. Nnrf_NFDiscovery_Response (address, exposure service, ...) + Note right of FUEC: 7. Nupf_EventExposure_Subscribe (UE ID, event ID(s)) + FUEC->>UPF: 7. Nupf_EventExposure_Subscribe (UE ID, event ID(s)) + Note right of UPF: 8. Nupf_EventExposure_Notify (UE ID, event information) + UPF->>FUEC: 8. Nupf_EventExposure_Notify (UE ID, event information) + +``` + +Sequence diagram illustrating the procedure for registering UPF(s) serving a PDU session at UDM. The diagram shows interactions between Final UPF event consumer, UDM, NRF, SMF, UPF, and UE. The sequence starts with UPF registering with NRF (0). Then, a PDU session establishment or mobility or new PCC rule occurs between UE and SMF (1). The SMF selects UPF(s) (2). The SMF registers or updates the PDU session on the UDM (2). The Final UPF event consumer invokes Nudm\_UECM\_Get (3). The UDM provides a response (4). The Final UPF event consumer invokes Nnrf\_NFDiscovery\_Request (5). The NRF provides a response (6). The Final UPF event consumer subscribes to the UPF event exposure (7). The UPF notifies the Final UPF event consumer (8). + +**Figure 6.5.3-1: Registering UPF(s) serving a PDU session at UDM** + +0. UPF(s) need to register their event exposure service onto NRF using Nnrf\_NFManagement as described in solution 1. +1. A PDU Session is established or modified and the modification requires a change of UPF to serve the PDU Session (e.g. due to UE mobility or to new PCC rule or to EASDF induced UL CL insertion). + +The SMF selects new UPF(s) and establishes N4 session with these UPF(s). This may imply usage of solution 4. + +2. The SMF registers the PDU Session on UDM or updates the PDU Session registration on UDM. Nudm\_UECM\_Registration and Nudm\_UECM\_Update when the UPF information changes. The information provided to UDM is described in clause 6.5.2. +3. the UPF event consumer invokes Nudm\_UECM\_Get to get the list of UPF serving a PDU session identified by the SUPI/GPSI, a DNN, a S-NSSAI and possibly an UE address (IP address or MAC address). +4. the UDM provides the UPF instance Id of each UPF that matches the Nudm\_UECM\_Get. + +5. the UPF event consumer uses this information to get information on the UPF exposure service via Nnrf\_NFDiscovery\_Request. +6. the NRF provides the requested information. +7. the UPF event consumer issues Nupf\_EventExposure\_Subscribe. +8. when the conditions set in Nupf\_EventExposure\_Subscribe match, UPF issues Nupf\_EventExposure\_Notify. + +### 6.5.4 Impacts on services, entities and interfaces + +The solution impacts SMF, UDM and the UPF event consumers (NWDAF, NEF, AF). + +## 6.6 Solution #6: Determining the UPF(s) that serve a UE address + +### 6.6.1 Key Issue mapping + +This solution addresses KI 2. It addresses the case where the UPF event consumer desires to subscribe to UPF(s) event exposure and targets PDU Sessions involving a UE identified by its UE address. + +### 6.6.2 Description + +The UPF event consumer may, as defined in solution 3, be a NWDAF, an AF or a NEF. + +The solution runs as follows: + +- Per Rel-17 specifications, the SM PCF issues Nbsf\_Management\_Register to Register the tuple (UE address(es), SUPI, GPSI, DNN, S-NSSAI, PCF address(es), PCF instance id, PCF Set ID) for a PDU Session. The SM PCF issues Nbsf\_Management\_Update to update the information. +- The UPF event consumer invokes the BSF (Nbsf\_Management\_Discovery) using the UE address (i.e. IP address or MAC address), DNN, S-NSSAI as discovery criteria to get the SUPI of the UE. +- Then the UPF event consumer can invoke solution 5. + +### 6.6.3 Procedures + +![Sequence diagram illustrating the procedure for determining the UPF(s) that serve a UE address. The diagram shows interactions between UE, SMF, PCF, BSF, and UPF Event consumer. The steps are: 1. UE sends PDU session establishment to SMF; 2. SMF sends Npcf_SMPolicyControl_Create to PCF; 3. PCF sends Nbsf_Management_Register to BSF; 4. UPF Event consumer sends Nbsf_Management_Discovery to BSF; 5. BSF sends Nbsf_Management_Discovery Response to UPF Event consumer; 6. UPF Event consumer applies solution 5.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SMF + participant PCF + participant BSF + participant UPF_Event_consumer as UPF Event consumer + + Note left of UE: 1 PDU session establishment + UE->>SMF: + Note right of SMF: 2. Npcf_SMPolicyControl_Create + SMF->>PCF: + Note right of PCF: 3. Nbsf_Management_Register (IP address, DNN, S-NSSAI, SUPI, ...) + PCF->>BSF: + Note right of UPF_Event_consumer: 4. Nbsf_Management_Discovery (IP address, DNN, S-NSSAI, SUPI, ...) + UPF_Event_consumer->>BSF: + Note right of BSF: 5. Nbsf_Management_Discovery Response ( SUPI) + BSF->>UPF_Event_consumer: + Note right of UPF_Event_consumer: 6. Apply solution 5 + UPF_Event_consumer->>UPF_Event_consumer: + +``` + +Sequence diagram illustrating the procedure for determining the UPF(s) that serve a UE address. The diagram shows interactions between UE, SMF, PCF, BSF, and UPF Event consumer. The steps are: 1. UE sends PDU session establishment to SMF; 2. SMF sends Npcf\_SMPolicyControl\_Create to PCF; 3. PCF sends Nbsf\_Management\_Register to BSF; 4. UPF Event consumer sends Nbsf\_Management\_Discovery to BSF; 5. BSF sends Nbsf\_Management\_Discovery Response to UPF Event consumer; 6. UPF Event consumer applies solution 5. + +Figure 6.6.3-1: Determining the UPF(s) that serve a UE address + +1. A PDU Session is established or modified as described in Rel-17, clauses 4.3.2 and 4.3.3 of TS 23.502 [3]. +2. SM Policy Association Establishment / Modification using Npcf\_SMPolicyControl\_Create / Npcf\_SMPolicyControl\_Update as described in Rel-17, clause 4.16.4 / clause 4.16.5 of TS 23.502 [3]. +3. At SM Policy Association Establishment, the SM PCF issues Nbsf\_Management\_Register to Register the tuple (UE address(es), SUPI, GPSI, DNN, S-NSSAI, PCF address(es), PCF instance id, PCF Set ID) for a PDU Session. At SM Policy Association modification, the SM PCF issues Nbsf\_Management\_Update to update the information (new set of UE address associated with a PDU session). All these interactions are per Rel-17 specifications. +4. The UPF event consumer invokes the BSF (Nbsf\_Management\_Discovery Request) using the UE address (i.e. IP address or MAC address), DNN, S-NSSAI as discovery criteria. +5. The BSF answers (Nbsf\_Management\_Discovery Response) with the SUPI of the UE. +6. Then the UPF event consumer can invoke solution 5. + +### 6.6.4 Impacts on services, entities and interfaces + +- The UPF event consumer needs to invoke the BSF using the UE address (i.e. IP address or MAC address), DNN, S-NSSAI as discovery criteria. +- Nbsf\_Management\_Discovery Response needs to provide as output the SUPI of the UE. +- Impacts of solution 5. + +## 6.7 Solution #7: Support to existing (Rel-16-Rel-17) data analytics with PDU Session Data Usage Events + +### 6.7.1 Key Issue mapping + +This Solution addresses KI#2. + +### 6.7.2 Description + +This solution extends the Rel-17 UPF Event Exposure service with two new events for the collection of information of user data usage of the User PDU Session: + +- One event provides measurements, and it will be referred to as UserDataUsageMeasures along the solution and can include following information: + - Volume Measurement: measures of data volume exchanged (UL, DL and/or overall) and/or number of packets exchanged (UL, DL and/or overall) with or without application granularity. This measurement can also include number of packets transmitted for applications where that is possible to differentiate. + - Throughput Measurement: measures of data throughput (UL and DL) measures aggregated for the PDU Session or per application. +- The other event provides statistical measurements, and it will be referred to as UserDataUsageTrends along the solution and can include following information: + - Throughput Statistic Measurement (average and/or peak throughput) over the measurement period for the PDU Session or per application. + +Both events provide measurement context (for example, the measurement period) and information of the PDU Session. When the information refers only to certain traffic, an identifier e.g. Application Id may also be included. + +This solution defines a UPF Event Exposure Subscription operation that consumers can use to subscribe to UPF Event Exposure service for the two new events, UserDataUsageMeasures and UserDataUsageTrends. Subscription can be for a UE, "Any\_UE", or a specific PDU Session. The Event Subscription includes filters for the data collection, and measurement, event reporting and notification control information like which data that is requested and with which granularity (for the PDU Session or for an Application within the PDU Session). + +In this solution, the subscription to UPF does not have any impact on UPF packet matching procedure and it does not degrade the performance of UPF user plane traffic handling. When for exposure the UPF traffic differentiation in the User PDU Session is according to the packet detection rules that have been installed for each PFCP session by SMF, when measurements are requested for an/per application, UPF considers for the measurements of a User PDU Session and App Id only the traffic that is matching a PDR which has that App Id. + +The event notifications are sent to the consumer according to the notification control information received in the subscription to the event. + +This solution satisfies following Rel-16-Rel-17 NWDAF Analytics UPD Data Collection needs as follows: + +- NF Load: UserDataUsageMeasures event with Volume Measurement (see NOTE 1) accumulated for the PDU Session. +- User data Congestion: UserDataUsageTrends event with Throughput Statistic Measurement with per application or IP Packet Filter Set measures over a measurement period. +- UE Communications: UserDataUsageMeasures event with Volume Measurement and Throughput Measurement with per Application or IP Packet Filter Set measures or with PDU Session aggregated measures for a UE\_communication (see NOTE 2). +- WLAN Performance analytics: UserDataUsageMeasures event with Volume Measurement and Throughput Measurement measured for a PDU Session. +- Dispersion: UserDataUsageMeasures event with Volume measurement and per application or IP Packet Filter Set measures (they are exclusive) or with PDU Session aggregated measures. + +NOTE 1: The solution defines the Volume Measurements with similar definition as in the Traffic Usage Report. + +NOTE 2: UE Communication definition may imply measuring periods are defined, for example, in relation to application activity/inactivity. + +UPF reporting related with Delay measurements, and in general measurements related to QoS Flows is not addressed by this solution. + +### 6.7.3 Procedures + +#### 6.7.3.1 Subscription to UPF for Data Collection for "Any UE" + +Figure 6.7.3.1-1 below shows the procedure for UPF Event Exposure subscription and notification for the UserDataUsageMeasures and UserDataUsageTrends events that can be used in scenarios targeting data collection from UPF for "Any UE". + +Example UCs are NWDAF data collection for NF Load NWDAF analytic (clause 6.5 of TS 23.288 [5]), or for User Data Congestion Analytic (clause 6.8 of TS 23.288 [5]). + +![Sequence diagram for Data Collection from UPF for Any_UE](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +``` +sequenceDiagram + participant UPF + participant NRF + participant cNF + participant NWDAF + Note right of NWDAF: 3. Select Data contributors & start Data collection TS 23.288 + Note left of UPF: 6. UPF Selects PDU Sessions and starts measurement + Note right of NWDAF: 8. NWDAF derives Requested Analytic + + UPF->>NRF: 1. Nnrf_NF_Management:NFRegister_request + cNF->>NWDAF: 2. Nnwdaf_AnalyticsInfo_Request + NWDAF->>NRF: 4. Nnrf_NFDiscovery_request + NWDAF->>cNF: 5. Nupf_EventExposure Subscribe + cNF->>UPF: 7. Nupf_EventExposure Notify + NWDAF->>cNF: 9. Nnwdaf_AnalyticsInfo_Request response +``` + +The sequence diagram illustrates the interaction between four network functions: UPF, NRF, cNF, and NWDAF. The process begins with the UPF sending an 'Nnrf\_NF\_Management:NFRegister\_request' to the NRF. Simultaneously, the cNF sends an 'Nnwdaf\_AnalyticsInfo\_Request' to the NWDAF. The NWDAF then performs internal steps to 'Select Data contributors & start Data collection' as per TS 23.288. Next, the NWDAF sends an 'Nnrf\_NFDiscovery\_request' to the NRF. The NRF responds with a 'Nupf\_EventExposure Subscribe' message to the cNF. The cNF then sends a 'Nupf\_EventExposure Notify' message to the UPF. During this notification, the UPF performs internal steps to 'Select PDU Sessions and starts measurement'. Finally, the NWDAF sends an 'Nnwdaf\_AnalyticsInfo\_Request response' to the cNF, after which it performs internal steps to 'derive Requested Analytic'. + +Sequence diagram for Data Collection from UPF for Any\_UE + +Figure 6.7.3.1-1, Data Collection from UPF for Any\_UE + +A description of the procedure in Figure 6.7.3.1-1 follows: + +1. In a first step, UPF registers its profile in NRF. +2. NWDAF receives a request from a consumer. + +If type of Analytic is for example "NF Load" and NFs type=UPF, it may be for UPFs only within an Area of Interest (AoI) and specific S-NSSAI, or it may be for a given UPF Id. If for example Type of Analytic is "User Data Congestion", if "Any UE", it always includes AoI, and if the request includes a SUPI, the user location determines the AoI but UPF data collection is still for "Any UE" within AOI. In this case, the consumer may also request N top consuming Applications. + +3. NWDAF identifies the Data required for this analytic and starts data collection as in TS 23.288 [5]. In this case, data from UPF is required. +4. NWDAF selects the relevant UPFs with assistance from NRF. It can take into account information received in the request (for example, S-NSSAI and/or AoI). + +NOTE 1: When a PDU Session user plane consists of more than one UPF, only some of them may have service area overlapping the AoI and be selected. Their role may be ULCL/BP and/or PSA. Depending on the deployment, NWDAF may be configured to use procedure in Figure 6.7.3.1-2 instead for a given Analytic. + +5. NWDAF sends Nupf\_EventExposure Subscribe for Event= UserDataUsageMeasures / UserDataUsageTrends to relevant UPF(s) for "Any UE" and it may include filters like S-NSSAI or AoI (list of TAs). NWDAF provides Event Reporting Info including the DataSubset requested. +6. UPF Selects the PDU Sessions that match the filters and for that, it may perform sampling according to input received or local configuration. It starts to produce measurements for those sessions as requested. + +NOTE 2: When application traffic differentiation for exposure is conditioned by the PFCP session packet detection rules, the application differentiation that may be needed by exposure is considered in the definition of the rules to apply to the PDU Sessions, so that SMF installs packet detection rules in the PFCP sessions in UCL/BP and/or PSA (see NOTE 1) accordingly. + +The selection of PDU Sessions may change during the lifetime of the subscription e.g. at termination or establishment of PDU Sessions that meet the criteria, or UEs entering/leaving the AoI according to user location information (ULI) received over N4. + +NOTE 3: NWDAF subscription to AMF/SMF events for the AoI widens the mobility events where UPF gets ULI updates, improving accuracy of UPF PDU Session selection for the AoI. + +If Subscription has included AoI, and the PDU Session selection in UPF does not support this filter condition, UPF rejects the request from NWDAF. + +NOTE 4: Upon reject, NWDAF identifies that it needs to create the mapping of PDU sessions per TA. NWDAF can subscribe to UE mobility event notifications of AMF to retrieve the list of SUPIs in the AoI (not needed if this information is already known). It can then apply instead the procedure in clause 6.7.3.2 on the retrieved list of SUPIs or subscribe to UPF without AoI filter condition using the retrieved list of SUPIs to filter the UPF events (step 8). + +7. UPF sends Nupf\_EventExposure Notify for Event= UserDataUsageMeasures / UserDataUsageTrends for the selected PDU Sessions. The notifications include SUPI, DNN and S-NSSAI as available and conveys measurements and context according to the subscription. + +8. NWDAF derives the Requested Analytic. + +NOTE 5: NWDAF may at this stage use AMF/SMF information to filter the UPF events for the AoI. + +9. NWDAF provides the Analytic requested. + +#### 6.7.3.2 Subscription to UPF for Data Collection for certain PDU Sessions + +Figure 6.7.3.1-2 below shows the procedure for UPF Event Exposure subscription and notification for the UserDataUsageMeasures and UserDataUsageTrends events that can be used in scenarios targeting data collection from UPF for certain UEs or PDU Sessions. + +If Analytic is targeting "Any UE", this procedure can still be preferred or even needed for a preselection of the PDU Sessions (for example, when UPF lacks information to evaluate some filters), or as a way to perform the PDU Session sampling in SMF only when SMF also contributes to the analytic. + +Example for UCs are NWDAF data collection for WLAN Performance analytics (clause 6.11 of TS 23.288 [5]), Dispersion analytics (clause 6.10 of TS 23.288 [5]), and for UE Communication analytics (clause 6.7 of TS 23.288 [5]). + +![Sequence diagram showing data collection from UPF for certain PDU Sessions. The diagram involves four lifelines: UPF, SMF, CNF, and NWDAF. The sequence of messages is: 1. Nnwdaf_AnalyticsInfo_Request from CNF to NWDAF; 2. Select Data contributors (UPF/SMF Data needed) & start Data collection (TS 23.288) from NWDAF; 3. Nsmf_EventExposure Subscribe from NWDAF to SMF; 4. Nupf_EventExposure Subscribe from SMF to UPF; 5. UPF starts measurement for selected PDU Sessions (internal UPF action); 6. Nupf_EventExposure Notify from UPF to NWDAF; 7. NWDAF derives Requested Analytic (internal NWDAF action); 8. Nnwdaf_AnalyticsInfo_Request response from NWDAF to CNF.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +``` +sequenceDiagram + participant CNF + participant NWDAF + participant SMF + participant UPF + + Note right of NWDAF: 2. Select Data contributors (UPF/SMF Data needed) & start Data collection (TS 23.288) + + Note left of UPF: 5. UPF starts measurement for selected PDU Sessions + + Note right of NWDAF: 7. NWDAF derives Requested Analytic + + CNF->>NWDAF: 1. Nnwdaf_AnalyticsInfo_Request + NWDAF-->>SMF: 3. Nsmf_EventExposure Subscribe + SMF-->>UPF: 4. Nupf_EventExposure Subscribe + UPF->>NWDAF: 6. Nupf_EventExposure Notify + NWDAF-->>CNF: 8. Nnwdaf_AnalyticsInfo_Request response +``` + +Sequence diagram showing data collection from UPF for certain PDU Sessions. The diagram involves four lifelines: UPF, SMF, CNF, and NWDAF. The sequence of messages is: 1. Nnwdaf\_AnalyticsInfo\_Request from CNF to NWDAF; 2. Select Data contributors (UPF/SMF Data needed) & start Data collection (TS 23.288) from NWDAF; 3. Nsmf\_EventExposure Subscribe from NWDAF to SMF; 4. Nupf\_EventExposure Subscribe from SMF to UPF; 5. UPF starts measurement for selected PDU Sessions (internal UPF action); 6. Nupf\_EventExposure Notify from UPF to NWDAF; 7. NWDAF derives Requested Analytic (internal NWDAF action); 8. Nnwdaf\_AnalyticsInfo\_Request response from NWDAF to CNF. + +**Figure 6.7.3.1-2: Data Collection from UPF for certain PDU Sessions** + +A description of the procedure in Figure 6.7.3.1-2 follows: + +Prerequisite: When application traffic differentiation for exposure is conditioned by the PFCP session packet detection rules, SMF has installed packet detection rules in the PFCP sessions with rules for the applications for which differentiated measurements may be needed. + +1. NWDAF receives a request from a consumer. + +As an example, type of Analytic may be "UE Dispersion" requesting a Data Volume Dispersion Analytic (DVDA) for "Any UE", a UE or a UE\_Group including filters like S-NSSAI, AoI and/or App Ids for applications of interest. Another example would be a request with type of Analytic "WLAN performance" for "Any UE", a UE or a UE\_Group in an AoI and for certain SSID/BSSID. In another example, Analytic type could be "UE Communication" targeting a UE or UE Group and specific Applications. + +2. NWDAF identifies the Data required for this analytic and starts data collection as in TS 23.288 [5]. This analytic requires Data Collection from UPF and for that, the UPF PDU Session identifiers and UPF service contact information needs to be collected from SMF. SMF may contribute to this analytic with other data. + +Clause 6.2.2 of TS 23.288 [5] specifies some options for how to select SMF: + +- If Target is a UE or a UE Group, NWDAF can select the SMF(s) with UDM assistance as specified in clause 6.2.2 of TS 23.288 [5]. +- If Target is "Any UE", NWDAF selects SMF with assistance of NRF taking into account filter conditions if any received in the request. If AoI is also provided, NWDAF can first determine the users within AoI with AMF assistance and proceed as when Target is a UE. + +3. NWDAF sends Nsmf\_EventExposure Subscribe to SMF including the target and any conditions that need be considered for filtering or sampling the PDU Sessions. The SMF response/notification includes UPF identifiers of the User PDU Sessions matching the request and the information of the UPFs to be contacted. If needed, information of whether UPF is acting as PSA and DNAI could also be provided. This information may have been retrieved already during SMF data collection for the analytic in step 2. + +NOTE 1: SMF event notifications of already specified exposure events can be enhanced for this purpose, for example UPF Info, PDU session establishment or Information on PDU Session for WLAN (see clause 5.2.8.3 of TS 23.502 [3]). + +4. NWDAF takes SMF information as input for the data collection from UPF. It sends Nupf\_EventExposure Subscribe for Event= UserDataUsageMeasures / UserDataUsageTrends to the UPF handling the PDU Session. The subscription targets a PDU Session. The request includes Event Reporting Info, including the DataSubset requested. + +If Subscription has included AoI and UPF supports this condition, UPF takes into account whether UE is entering/leaving the AoI according to user location information (ULI) received over N4. If UPF does not support this filter condition UPF rejects the request from NWDAF. + +NOTE 2: Upon reject, NWDAF identifies that it needs to create the mapping of PDU session and TA itself. When there are many UE(s) in an AoI and many mobility in and out of the AoI, it may be convenient for the NWDAF to filter the events rather than performing many subscription/unsubscription to UPF to avoid high signalling load. + +NOTE 3: The signalling impacts of Providing user location information (ULI) received over N4 and on NWDAF receiving UPF notifications for UE(s) that are not in the AoI needs to be assessed. + +5. UPF starts the measurement for the PDU Session as requested. +6. UPF sends Nupf\_EventExposure Notify for Event= UserDataUsageMeasures / UserDataUsageTrends for the PDU Session. The notification includes SUPI, DNN and S-NSSAI as available and conveys measurement information according to the subscription. +7. NWDAF derives the Requested Analytic. +8. NWDAF provides the Analytic requested. + +### 6.7.4 Impacts on services, entities and interfaces + +This solution impacts the System as follows: + +- Nupf Event Exposure Service is enhanced with two new events and a subscription operation for those events: + - The target of the subscription to these events may be "any UE", a SUPI, or a given User PDU Session (identified by UE IP address and DNN or N4 Session ID). DNN and S-NSSAI and AoI can be included as filter conditions. + +- The subscription request also includes Event Reporting Information (including required DataSubset (Volume Measurement and/or Throughput Measurements or Throughput Statistic Measurement), Control Information for the measurements (like granularity) and Reporting and Notification Control Information for the event. +- Nupf Event Exposure service Notification provides information for a user PDU Session identified by UE IP address and DNN (and/or N4 Session ID) and includes SUPI and S-NSSAI when available. +- Nsmf Event Exposure service subscription notification includes UPF PDU Session identifier and UPF Event Exposure service contact information. If needed, information of whether UPF is acting as PSA and DNAI could also be provided. + +NOTE: Decision is left for stage 3 for whether enhancing notifications of already specified events or defining a new SMF event. + +For new UserDataUsageMeasures event, it includes: + +- Volume Measurement: measures of data volume exchanged (UL, DL and/or overall) and/or number of packets exchanged (UL, DL and/or overall) with or without application granularity. This measurement can also include number of packets transmitted and retransmitted for applications where that is possible to differentiate. +- Throughput Measurement: measures of data throughput (UL and DL) aggregated for the PDU Session or per application. + +For new UserDataUsageTrend event, it includes: + +- Throughput Statistic Measurement (average and/or peak throughput) over the measurement period for the PDU Session or per application. + +And for both events, it includes measurement context (for example, time stamps for the packets and the measures) and when the information refers to an application, the corresponding Application Id or Packet Filter Set. + +- UPF is enhanced to produce measurements according to UserDataUsageMeasures event and UserDataUsageTrends event and to send notifications as instructed in the subscription. +- SMF is enhanced to provide ULI (TA) to UPF over N4. UPF is enhanced to map PDU sessions to an AoI with TA granularity based on N4 ULI and to determine which PDU Sessions are for users with an AoI. +- NWDAF is enhanced to collect Data Usage measurements from UPF with UPF Event Exposure Service Subscription using UserDataUsageMeasures / UserDataUsageTrends event. It receives Nupf Event Exposure notifications for UserDataUsageMeasures / UserDataUsageTrends event with information as requested, and correlates information from different sources to produce Analytics. + +## 6.8 Solution #8: Support to existing (Rel-16-Rel-17) data analytics with QoS Flow level measurements + +### 6.8.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.8.2 Description + +This solution extends Rel-17 UPF Exposure Service QoS Monitoring event, with additional measurements of QoS Flow level performance information for a User PDU Session and QoS Flow. Besides, the QoS Monitoring measurement, this event can provide: + +- QoS Flow Bandwidth measurements: It provides bitrate measurements (UL, DL and/or overall) for a PDU Session and QoS Flow. + +NOTE 1: This event can be extended with other QoS Flow performance measurements in the future when available and required. + +With this extension, the NWDAF requirements on UPF event exposure service(s) to collect performance data of PDU Session QoS Flows are satisfied as follows: + +- Observed Service Experience: using the QoS monitoring event and from that, QoS Monitoring Measurement and/or QoS Flow Bandwidth measurements for the PDU Session and QFI as requested. See NOTE 2. + +NOTE 2: UPF awareness of Packet transmission and retransmission depends on the specific application transport protocol. Number of Packet transmission and retransmission can't be measured for a QoS Flow in UPF due to this limited visibility. The observed number of packets transmitted/retransmitted or a retransmission rate measurement can be considered in UPF event exposure for User PDU Session service data usage for applications with transport protocols that allow so. This has been considered in Solution 7. + +In this solution, the subscription to QoS monitoring event goes via SMF which simplifies the procedure and guarantees aligned selection decisions for data collection from UPF and SMF. + +SMF determines the PDU Sessions and UPFs impacted by this request and determines the QFI of QoS Flows to be monitored (for example the QFI for the PDU Session and Application). + +When packet delay for QoS Flows measurement is requested, SMF can decide whether this subscription influences QoS Monitoring activation and how. SMF may activate QoS Monitoring. SMF may only update activation towards UPF with direct reporting information. SMF sends Session Reporting Rules to UPF with Control Information for the measurements and with Direct Reporting information accordingly. + +UPF notifies the QoS Monitoring event directly to NWDAF as instructed. It provides Measurements as requested (QoS Monitoring Measurement and/or QoS Flow Bandwidth measurements) including for which QFI they have been performed. + +### 6.8.3 Procedures + +This procedure provides NWDAF with QoS Flow level Measurements for a User PDU Session. + +![Sequence diagram showing the procedure for data collection of QoS Flow Performance measurements from UPF. Lifelines: UE/AN, UPF, SMF, AMF, cNF, AF, NWDAF. The process involves an analytics request from cNF to NWDAF, determination of data needs by NWDAF, subscription by AMF to SMF, selection of PDU session by SMF, activation of QoS monitoring by SMF, notification by UPF to NWDAF, derivation of analytic by NWDAF, and a response back to cNF.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant cNF + participant NWDAF + participant AMF + participant SMF + participant UPF + participant UE/AN + + Note right of cNF: 1. Nnwdaf_AnalyticsInfoRequest (Analytics ID = Service Experience) + cNF->>NWDAF: 1. Nnwdaf_AnalyticsInfoRequest (Analytics ID = Service Experience) + Note right of NWDAF: 2. NWDAF determines data collection needs for the Analytic +QoS Flow performance data for this analytic is subscribed to via SMF +It selects the Network data provider NFs and AF and starts data Collection. + Note left of AMF: 3. Nsmf_EventExposure Subscribe (EVENT=QoSMonitoring) + AMF->>SMF: 3. Nsmf_EventExposure Subscribe (EVENT=QoSMonitoring) + Note right of SMF: 4. SMF selects User PDU Session, +it identifies UPF and QFI + Note right of SMF: SMF activates/updates session QoS Flow Measurements (QoS Monitoring activation involves UPF and AN) +SMF provides UPF with Direct Reporting information + SMF->>AMF: 5. Namf_Communication_N1N2MessageTransfer + SMF->>UPF: 6. N4_Session Modification (PFCPSession) + Note right of UPF: 7. AN/UPF perform QoS Flow performance measurements as instructed + Note left of NWDAF: 8. Nupf_EventExposure_Notify (EVENT=QoSMonitoring) + UPF->>NWDAF: 8. Nupf_EventExposure_Notify (EVENT=QoSMonitoring) + Note right of NWDAF: 9. NWDAF derives the requested Analytic + Note right of NWDAF: 10. Nnwdaf_AnalyticsInfoRequest Response (Estimated Experience.) + NWDAF->>cNF: 10. Nnwdaf_AnalyticsInfoRequest Response (Estimated Experience.) + +``` + +Sequence diagram showing the procedure for data collection of QoS Flow Performance measurements from UPF. Lifelines: UE/AN, UPF, SMF, AMF, cNF, AF, NWDAF. The process involves an analytics request from cNF to NWDAF, determination of data needs by NWDAF, subscription by AMF to SMF, selection of PDU session by SMF, activation of QoS monitoring by SMF, notification by UPF to NWDAF, derivation of analytic by NWDAF, and a response back to cNF. + +**Figure 6.8.3-1: Procedure for Data Collection of QoS Flow Performance measurements from UPF. +Example Use case for Observed Service Experience Analytic (clause 6.4 of TS 23.288 [5])** + +The procedure is as follows: + +1. NWDAF receives an Analytics Info Request that requires UPF Data collection, in this example, for Service Experience (OSE) for an Application Id. For example, that could be for a UP Path (DNAI) for a specific UE and for certain DNN and S-NSSAI. +2. NWDAF determines the data collection needed, in this case, QoS Flow Performance Data and other data network information from NF providers and from AF, as specific in clause 6.4 of TS 23.288 [5]. NWDAF selects the entities that provide input data, including the SMF for the Subscription to UPF QoS Flow performance Data. + +NOTE 1: How NWDAF selects SMF is specified in clause 6.2.2 of TS 23.288 [5], including how any filter for Area of Interest (AOI) is considered for SMF selection (and by SMF for PDU Session Selection). If NWDAF subscription to SMF is for a UE or UE Group, NWDAF may subscribe indirectly via UDM. If it is for "Any UE", it subscribes directly to SMF. + +NOTE 2: An operator should use "any UE" with caution, since per flow monitoring of a large amount of flows could have impact on UPF performance. + +3. NWDAF sends a Nsmf\_Event Exposure Subscribe Operation to SMF for QoS Monitoring Event. The request includes the event filters (target (for example SUPI) and other like DNN, S-NSSAI, DNAI and AppId) and event Reporting Information (required DataSubset (QoS Monitoring Measurement and/or QoS Flow Bandwidth Measurements), Control Information for the measurements and Reporting and Notification Control Information). +4. SMF Selects the target PDU Session. SMF also determines the UPF that has to perform the measurements (DNAI if provided is considered at this stage) and the QFI of QoS Flows to be monitored (e.g. QFI allocated to the Application in the PDU Session). +- 5-6. SMF can decide whether this subscription influences QoS Monitoring activation and how. SMF may activate QoS Monitoring. SMF may only update previous activation providing UPF with direct reporting information. SMF sends a Session Modification update towards UPF with Session Reporting Rules including Control Information for QoS Monitoring Measurements and/or QoS Flow Bandwidth Measurements and Direct Reporting information. +7. UPF performs the QoS Flow measurements as required with AN assistance when needed. +8. QoS Flow Level measurements trigger a Nupf Event Exposure Notification towards NWDAF according to the Control Information received. The Notification is for a PDU Session and QoS Flow and includes among other QoS Monitoring Measurement and/or QoS Flow Bandwidth Measurements with corresponding QFI. +9. NWDAF derives the requested Analytics for the data that it has collected. +10. NWDAF sends a Response to the Analytics Info Request with the Estimated Experience for the User and Application on the UP Path. + +### 6.8.4 Impacts on services, entities and interfaces + +This solution impacts the System as follows: + +- Nsmf Event Exposure Subscription needs to be enhanced: + - It is enhanced to support subscription to QoS Monitoring event, so NWDAF as consumer can collect data of QoS Flow performance. The target of the subscription to this event may correspond to a UE ID (SUPI), an Internal Group Identifier, or may include a "Any UE" indication. Event Filters are used to specify the conditions for notifying the events. Example parameters for this event are DNN, S-NSSAI, DNAI, Application Identifier. + - The subscription includes also additional Event Reporting Information, including the required DataSubset (QoS Monitoring Measurement and/or QoS Flow Bandwidth Measurements), Control Information for the measurements and Reporting and Notification Control Information). +- PFCP Session Establishment/Modification is enhanced as follows: + +- Session Reporting Rules (SRR) are enhanced to support new type of session data to report for Direct Reporting. Rules are enhanced to provide new Control for QoS Monitoring per QoS Flow for the QoS Flow Bandwidth Measurements. Direct Reporting is always provided. + - Control for QoS Flow Bandwidth Measurements includes QFI, requested measurements (UL, DL and/or overall bitrate), Reporting Frequency (for example, by event or periodic) and complementary information as needed, like thresholds to trigger reporting, or measurement period (periodic reporting). + - SMF is enhanced as follows: + - To support the described Subscription to QoS Monitoring event, select the relevant PDU Session, and determine the Session Reporting Rules, including the described enhancements. SMF sends these Rules to UPF in PFCP Session Establishment/Modification message to activate monitoring and reporting towards NWDAF. + - UPF is enhanced as follows: + - To support the new information in Session Reporting Rule, perform the requested measurements and trigger notifications according to these rules. It sends the notification as instructed by Direct Reporting Information. It supports the enhancements in Nupf Event Exposure Notification for QoS Monitoring event including for QoS Flow Bandwidth Measurements (see below). + - Nupf Event Exposure Notification for QoS Monitoring event is enhanced as follows: + - It is extended to convey QoS Flow Bandwidth measurements (UL, DL and/or overall bitrate) including the QFI for which the measurement has been performed. +- NOTE: Additional measurements may be provided in the future (as an example, with QoS Flow retransmission rate measurements) and services/interfaces should allow such extensions. +- NWDAF is enhanced as follows: + - To collect QoS Flow level performance measurements from UPF subscribing to SMF Event Exposure Service Subscription for QoS Monitoring event. It receives Nupf Event Exposure notifications for QoS Monitoring event with the Measurements for QFIs, and correlates information from different sources to produce Analytics. + +## 6.9 Solution #9 to Key Issue 2: NWDAF collects information from UPF by event exposure + +### 6.9.1 Mapping table between Analytics ID and the related information collection in UPF + +According to TS 23.288 [5], some of the Analytics ID in NWDAF needs the information from UPF. + +The details of the information are listed in Table 6.9.1. + +Table 6.9.1: Analytics ID and the related information collection from UPF + +| Information | Source | Analytics ID | Description | +|-----------------------------|-----------|----------------------|------------------------------------------------------------------------------------------------------------| +| QoS flow Bit Rate | UPF | Service Experience | The observed bit rate for UL direction; and
The observed bit rate for DL direction. | +| QoS flow Packet Delay | UPF | | The observed Packet delay for UL direction; and
The observed Packet delay for the DL direction. | +| Packet transmission | UPF | | The observed number of packet transmission. | +| Packet retransmission | UPF | | The observed number of packet retransmission. | +| Traffic usage report | UPF | NF load | Report of user plane traffic in the UPF for the accumulated usage of network resources (see TS 29.244 [8]) | +| UE communication (1..max) | UPF, AF | UE communication | Communication description per application | +| >Communication start | | | The time stamp that this communication starts | +| >Communication stop | | | The time stamp that this communication stops | +| >UL data rate | | | UL data rate of this communication | +| >DL data rate | | | DL data rate of this communication | +| >Traffic volume | | | Traffic volume of this communication | +| PDU Session ID (1..max) | SMF | | Identification of PDU Session. | +| > N4 Session ID | SMF, UPF | | Identification of N4 Session. | +| > Inactivity detection time | SMF, UPF | | Value of session inactivity timer. | +| Application ID | UPF or AF | User Data Congestion | Application identifier as defined in TS 23.501 [2] clause 5.8.2 (see NOTE 1). | +| IP Packet Filter Set | UPF or AF | | IP Packet Filter set as defined in TS 23.501 [2] clause 5.8.2 (see NOTE 1). | +| Measurement period | UPF or AF | | Measurement period. | +| Throughput UL/DL | UPF or AF | | Average Throughput UL/DL over the measurement period. | +| Throughput UL/DL (peak) | UPF or AF | | Peak Throughput UL/DL over the measurement period. | +| Timestamp | UPF or AF | | Time when measurements are taken. | +| Achieved sampling ratio | UPF | | Sampling ratio achieved by UPF (see NOTE 2). | +| UE IP address | UPF | | UE IP address. | +| Timestamp | UPF | UE Dispersion | A timestamp of the collected information. | +| Application ID | UPF | | Identify the application at the UPF. | +| IP 5-tuple | UPF | | IP 5-tuple. | +| Location of Application | UPF | | List of Internet applications represented by DNAI(s). | +| Data Volume UL/DL | UPF | | Sum of UE data volume exchanged per application during the period. | +| Application duration | UPF | | Duration for the application (e.g. Voice talk time). | +| UE communications (1..max) | UPF | WLAN Performance | List of communication time slots | +| > Communication start | | | The time stamp that PDU session(s) for WLAN starts. | +| > Communication stop | | | The time stamp that PDU session(s) for WLAN ends. | +| > UL data rate | | | UL data rate of PDU session(s) for WLAN. | +| > DL data rate | | | DL data rate of PDU session(s) for WLAN. | +| > Traffic volume | | | Traffic volume of PDU session(s) for WLAN. | + +### 6.9.2 Service based UPF event exposure + +**Service description:** This service provides events related to PDU Sessions towards consumer NF. The service operations exposed by this service allow other NFs to subscribe and get notified of events happening on UPFs. The following are the key functionalities of this NF service. + +NOTE 1: In Rel-18, the only consumers of UPF event exposure is SMF and NWDAF when collecting data for network data analytics from NWDAF. + +- Allow consumer NFs to directly subscribe and unsubscribe for an Event ID on UPF; +- Allow the NWDAF to collect data indirectly for network data analytics; + +- Notifying events on the UPF to the subscribed NFs; and +- Allow consumer NFs to acknowledge or respond to an event notification. + +The following events can be subscribed by a NF consumer (Event ID is defined in clause 4.15.1): + +- QoS flow Bit Rate. +- QoS flow Packet Delay. +- Packet transmission. +- Packet retransmission. +- Traffic usage report. +- Communication start and stop (3GPP access or WLAN access). +- UL/DL data rate (3GPP access or WLAN access). +- Traffic volume (3GPP access or WLAN access). +- Throughput UL/DL. +- Throughput UL/DL (peak). +- Timestamp. +- Achieved sampling ratio. + +According to the Analytic ID from consumer, the NWDAF can decide which kind of information should be collect from UPF in the form of event ID. And then, the NWDAF triggers subscription request towards SMF which controls of the dedicated UPF that data generation, and the SMF determines the UPF and sends data collection request to UPF. According to the event ID, the UPF collects the data and exposes the related information to NWDAF directly. + +### 6.9.3 Procedure + +#### 6.9.3.1 UPF data collection for single UE + +![Sequence diagram illustrating the procedure for UPF data collection for a single UE. The diagram shows interactions between NF (consumer), NWDAF, UDM, SMF, and UPF (data provider).](69e5f1993021af230d08c08aac97d9df_img.jpg) + +``` + +sequenceDiagram + participant NF as NF (consumer) + participant NWDAF + participant UDM + participant SMF + participant UPF as UPF (data provider) + + Note right of UPF: 0. N4 procedure: event ID registered to SMF + Note left of NF: 1. Nnwdaf_AnalyticsInfo_Request/Nnwdaf_AnalyticsInfo (Analytics ID, SUPI) + Note right of NWDAF: 2. NWDAF determines the event ID for data collection + Note right of SMF: 7. SMF determines the UPF ID, UPF IP address + Note right of NWDAF: 11. NWDAF derives requested Analytics + + NF->>NWDAF: 1. Nnwdaf_AnalyticsInfo_Request/Nnwdaf_AnalyticsInfo (Analytics ID, SUPI) + NWDAF->>UDM: 3. Nudm_UECM_Get Request + UDM-->>NWDAF: 4. Nudm_UECM_Get Response + NWDAF->>SMF: 5. Nsmf_EventExposure_Subscribe + SMF-->>NWDAF: 6. Nsmf_EventExposure_Subscribe Response + SMF->>UPF: 8. Nupf_EventExposure_Subscribe + UPF-->>SMF: 9. Nupf_EventExposure_Subscribe Response + SMF->>NWDAF: 10. Nupf_EventExposure_Subscribe Notify + NWDAF->>NF: 12. Nnwdaf_AnalyticsSubscription_Notify/Nnwdaf_AnalyticsInfo_Notify/ + +``` + +Sequence diagram illustrating the procedure for UPF data collection for a single UE. The diagram shows interactions between NF (consumer), NWDAF, UDM, SMF, and UPF (data provider). + +**Figure 6.9.3.1-1: Data collection for single UE from service based UPF** + +0. The UPF registers to SMF with the supported event exposure which represented by event ID(s) via N4 Association Setup procedure. +1. The analytics consumer sends a request to the NWDAF for analytics on a specific UE, using either the Nnwdaf\_AnalyticsInfo or Nnwdaf\_AnalyticsSubscription service. The NF can request statistics or predictions or both. The type of analytics is set to either of the Analytics ID defined in TS 23.288 [5]. The NF provides the UE id in the Target of Analytics Reporting. Analytics Filter Information optionally contains DNN, S-NSSAI, Area of Interest, etc. +2. The NWDAF determines the event ID of UPF event exposure according to Analytics ID. Each event ID represents the data needed to be collected from UPF. For example, if consumer requests for the service experience analytic, the NWDAF can decide event ID is Service Experience, and the data needed to be collected from UPF are: QoS flow Bit Rate, QoS flow Packet Delay, Packet transmission, Packet retransmission. +3. The NWDAF sends Nudm\_UECM\_Get\_Request(SUPI, type of requested information set to SMF Registration Info and the S-NSSAI and DNN) to UDM to get the SMF ID that serving the target UE. +4. The UDM provides the SMF id and the corresponding PDU Session id, S-NSSAI, DNN using Nudm\_UECM\_Get\_Response to the NWDAF. +5. The NWDAF sends Nsmf\_EventExposure\_Subscribe to the SMF, including the Event ID of UPF event exposure determined by NWDAF in step 2 and additional Direct Reporting indicating that the UPF should send the event notifications directly to NWDAF. The NWDAF requests SMF to represent NWDAF to perform data collection from UPF. +6. The SMF responses to NWDAF for subscription. +7. The SMF determines the UPF that serves the UE, according to PDU session id, UE id, and possibly S-NSSAI and DNN. + +8. The SMF performs Nupf\_EventExposure\_Subscribe request to the UPF that determined in step 7 for data collection from UPF. In the request, the following parameters are included: PDU session id, Event ID that represents the kind of data needs to be collect, NWDAF IP address, DNN, S-NSSAI, UE id. Each of the data is represented by Event ID, for example, Event ID = QoS flow Packet Delay. The UPF receives several Event ID, and collects the corresponding data. All of the Event ID and corresponding data constructs the analytics in NWDAF. + +If the UPF doesn't support some of the event ID(s) according to the step 0 or Direct Reporting is not enabled from the NWDAF in the step 5, the related data will be collected via N4 procedure between SMF and UPF. Then, the SMF may notify NWDAF of the event report using Nsmf\_EventExposure\_Notify. + +9. The UPF responds with subscription request. +10. The UPF sends the notification related with Event ID data collection information over Nupf\_EventExposure\_Notify service operation. The notification is sent to Notification Target Address that may correspond to the NWDAF. +11. The NWDAF derives requested analytics, in the form of statistics or predictions or both. +12. NWDAF to NF: Nnwdaf\_AnalyticsInfo\_Request response or Nnwdaf\_AnalyticsSubscription\_Notify. + +The NWDAF provides requested analytics to the NF consumer, using either Nnwdaf\_AnalyticsInfo\_Request response or Nnwdaf\_AnalyticsSubscription\_Notify, depending on the service used in step 1. + +#### 6.9.3.2 UPF data collection for any UE + +Different from the data collection for single UE, for the any UE situation, the UPF which the UEs are served for is not the single one. But for a specific Analytics ID, the destination IP address, DNN, DNAI, S-NSSAI etc. can be used to determine the potential UPFs that serves the UE that meets the requirements, for example, the UEs that in the same slice or access the same DNN or IP address. + +![Diagram illustrating data collection for a single UE from a service-based UPF. The diagram shows three User Equipment (UE) units (UE 1, UE 2, UE 3) connected to two Packet Session Anchors (PSA - 1 and PSA - 2). PSA - 1 is connected to an Application Server (AS - 1) within a Data Network (DN). PSA - 2 is connected to another PSA (PSA - n) within the DN, which is further connected to UE n. The DN is represented by an oval containing AS - 1, PSA - n, and UE n.](94d3fdcc244924326f02533aeb2d93fc_img.jpg) + +``` + +graph LR + UE1[UE 1] --- PSA1[PSA - 1] + UE2[UE 2] --- PSA1 + UE3[UE 3] --- PSA2[PSA - 2] + PSA1 --- AS1[AS - 1] + PSA2 --- PSAn[PSA - n] + subgraph DN [DN] + AS1 --- PSAn + PSAn --- UEn[UE n] + end + +``` + +Diagram illustrating data collection for a single UE from a service-based UPF. The diagram shows three User Equipment (UE) units (UE 1, UE 2, UE 3) connected to two Packet Session Anchors (PSA - 1 and PSA - 2). PSA - 1 is connected to an Application Server (AS - 1) within a Data Network (DN). PSA - 2 is connected to another PSA (PSA - n) within the DN, which is further connected to UE n. The DN is represented by an oval containing AS - 1, PSA - n, and UE n. + +**Figure 6.9.3.2-1: Data collection for single UE from service based UPF** + +For example in Figure 6.9.3.2-1, the NF consumers request the service experience towards the application server 1 for any UE. In the whole PLMN, the NWDAF should select out the UEs which has connection to AS-1 and determines the related UPF to collect data. But unlike in the single UE scenarios, the related SMF can be discovered in UDM by subscription data, for the any UE situation, the SMF which is responsible for the session management for the UEs to access DNN or application server IP address should be discovered by other means. + +![Sequence diagram for Figure 6.9.3.2-2: Data collection for any UE from service based UPF. The diagram shows interactions between NF (consumer), NWDAF, NRF, NEF, UDR, SMF 1-n, and UPF 1-n (data provider).](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant NF as NF (consumer) + participant NWDAF + participant NRF + participant NEF + participant UDR + participant SMF as SMF 1 - n + participant UPF as UPF 1 - n (data provider) + + Note right of UPF: 0. N4 procedure: event ID registered to SMF + Note left of NF: 1. Nnwdaf_AnalyticsInfo_Request (Analytics ID, EAS/AS IP address, DNN, DNAI, APP ID) + Note right of NWDAF: 2. NWDAF determines the event ID for data collection + Note right of NWDAF: 2a. DNAI obtain from NEF/UDR by application server address + Note right of NWDAF: 3. Nnrf_NFDiscovery_Request + Note left of NRF: 4. Nnrf_NFDiscovery_Request Response + Note right of NWDAF: 5. Nsmf_EventExposure_Subscribe (DNN, S-NSSAI, target AS IP address, DNAI) + Note right of SMF: 6. SMF determines the UPF that coordinated with the DNN, S-NSSAI, AS IP address, APP ID. + Note right of SMF: 7. Nupf_EventExposure_Subscribe request + Note left of UPF: 8. Nupf_EventExposure_Subscribe Response + Note right of SMF: 9. Nupf_EventExposure_Subscribe Notify + Note right of NWDAF: 10. NWDAF derives requested Analytics + Note left of NF: 11. Nnwdaf_AnalyticsSubscription_Notify/ Nnwdaf_AnalyticsInfo_Notify/ + +``` + +Sequence diagram for Figure 6.9.3.2-2: Data collection for any UE from service based UPF. The diagram shows interactions between NF (consumer), NWDAF, NRF, NEF, UDR, SMF 1-n, and UPF 1-n (data provider). + +**Figure 6.9.3.2-2: Data collection for any UE from service based UPF** + +0. The UPF registers to SMF with the supported event exposure which represented by event ID(s) via N4 Association Setup procedure. This procedure may be repeated between different UPF and SMF. +1. The analytics consumer sends a request to the NWDAF for analytics on any UE, using either the Nnwdaf\_AnalyticsInfo or Nnwdaf\_AnalyticsSubscription service. The NF can request statistics or predictions or both. The type of analytics is set to either of the Analytics ID defined in TS 23.288 [5]. The NF provides the any UE in the Target of Analytics Reporting. Analytics Filter Information optionally contains DNN, S-NSSAI, Area of Interest, Application IP address, APP ID, DNAI and etc. +2. The NWDAF determines the event ID of UPF event exposure according to Analytics ID. Each event ID represents the data needed to be collected from UPF. For example, if consumer requests for the service experience analytic, the NWDAF can decide event ID is Service Experience, and the data needed to be collected from UPF are: QoS flow Bit Rate, QoS flow Packet Delay, Packet transmission, Packet retransmission. +- 2a. If the information provided by NF consumer only includes application server address and it can't be directly used for SMF discovery in NRF, the NWDAF should recover the DNAI first from NEF/UDR. If the DNAI does not exist in the Nnwdaf\_AnalyticsInfo request or Nnwdaf\_AnalyticsSubscription request in step 1 and only the Application Server Address(es) exists in request, the NWDAF decides that Application Server Address(es) can't be directly used in SMF discovery in NRF and obtain the target DNAI from 5GC by the mapping table between Application IP range/address and DNAI based on the conclusion of TR 23.700-48 [10]. So, the NWDAF sends request to NEF to obtain DNAI by providing EAS IP/IP range and/or FQDN. NEF responds to the NWDAF directly if DNAI is stored in NEF locally or the NEF recovers the DNAI from UDR. After obtaining the DNAI from NEF, the NWDAF triggers the SMF discovery in NRF using the DNAI in any UE situation. The details services between NWDAF and NEF, and the details between NEF and UDR should be coordinated with R18 EGDE item. +3. Due to the analytic is for any UE, the related SMF should be discovered first. In the scope of any UE, the potential UEs that related to the analytics ID has the same features below: + - Connect to the same application server IP address. + - Connect to the same S-NSSAI. + - Connect to the same DN. + +The NWDAF discovers a set of SMF instances by Nnrf\_NFDiscovery request towards NRF according to the common features of UEs that the analytics ID refers to, including DNN, S-NSSAI, Area of Interest, Application IP address, APP ID, DNAI. This request is responsible for discovery all of the SMFs that controls the UE which coordinates with the conditions in analytics requests to NWDAF. + +If the area of interest is existing in the Nnwdaf\_AnalyticsInfo request or Nnwdaf\_AnalyticsSubscription request in step 1, this information can be transformed to the Service Area of SMF for SMF discovery to NRF. + +NOTE: The mechanism of mapping table between application IP address/range and target DNAI needs to be coordinated with R18 eEDGE phase 2 item. + +4. The NRF responses with several SMF ID, SMF IP address that controls the UE which coordinates with the conditions in analytics requests to NWDAF. +5. The NWDAF sends several Nsmf\_EventExposure\_Subscribe requests to the several of SMFs discovered by NRF, including the Event ID of UPF event exposure set to in step 2 and additional Direct Reporting indicating that the UPF should send the event notifications directly to NWDAF, and other parameters used to determine UPF including DNN, S-NSSAI, Area of Interest, Application IP address, APP ID, DNAI. The NWDAF requests these SMFs to represent NWDAF to perform data collection from UPF. +6. All these SMFs should determine the UPF which serves the UEs accord with the condition of DNN, S-NSSAI, Area of Interest, Application IP address, APP ID, DNAI. +7. The several SMFs performs Nupf\_EventExposure\_Subscribe request to each UPFs individually that determined in step 6 for data collection from UPF. In the request, the following parameters are included: PDU session id, Event ID that represents the kind of data needs to be collect, NWDAF IP address, DNN, S-NSSAI, Area of Interest, Application IP address, APP ID, DNAI. + +If the UPF doesn't support some of the event ID(s) according to the step 0 or Direct Reporting is not enabled from the NWDAF in the step 5, the related data will be collected via N4 procedure between SMF and UPF. Then, the SMF may notify NWDAF of the event report using Nsmf\_EventExposure\_Notify. + +**Editor's note:** For the any UE scenarios, how to reduce the multiple notification message of data collections from UPF is FFS. + +8. The UPF responses with subscription request. +9. The each of UPF sends the notification related with Event ID data collection information over Nupf\_EventExposure\_Notify service operation. The notification is sent to Notification Target Address that may correspond to the NWDAF. +10. The NWDAF derives requested analytics, in the form of statistics or predictions or both. +11. NWDAF to NF: Nnwdaf\_AnalyticsInfo\_Request response or Nnwdaf\_AnalyticsSubscription\_Notify. + +The NWDAF provides requested analytics to the NF consumer, using either Nnwdaf\_AnalyticsInfo\_Request response or Nnwdaf\_AnalyticsSubscription\_Notify, depending on the service used in step 1. + +### 6.9.4 Impacts on services, entities and interfaces + +UPF: + +- Newly introduced UPF Services and UPF Service Operations to support SMF or NWDAF to collect data. +- Newly defined Event ID to the available data in UPF. +- Expose UPF related data collection information to NWDAF directly. + +SMF: + +- Represent NWDAF to request UPF to collect dedicated data. +- Consumer of UPF services for data collection. +- Determine the UPF that serves the target UEs in the scope of any UE according to parameters of NWDAF IP address, DNN, S-NSSAI, Area of Interest, Application IP address, APP ID, DNAI. + +NRF: + +- Discovery of several SMFs that accords with the parameters that related to the UEs. + +NWDAF: + +- Sends the AS IP/IP range and/or FQDN to NEF to retrieve the corresponding DNAI. +- Responsible to transfer the area of interests from NF consumer to SMF service area for SMF discovery in NRF. + +NEF: + +- NEF responds to the NWDAF directly if DNAI is stored in NEF locally or the NEF recovers the DNAI from UDR. + +## 6.10 Solution #10: UPF event exposure service to NWDAF + +### 6.10.1 Key Issue mapping + +This solution addresses KI 2. + +### 6.10.2 Description + +Annex A of this TR has analysed the NWDAF requirements of UPF event exposure, which contains seven aspects of information. In this solution, the NWDAF subscribes to the UPF data via the SMF, and the UPF directly sends the collected UPF data to NWDAF. + +### 6.10.3 Procedures + +![Sequence diagram showing UPF Information Exposure to NWDAF. The diagram illustrates the interaction between NWDAF, UDM, NRF, SMF, UPF, and AMF. It is divided into Case 1 and Case 2. Case 1 involves Nudm_UECM_Get and Nupf_EventExposure_Notify. Case 2 involves Nnrf_NFDiscovery_Request, Namf_EventExposure_Subscribe, and N4 Session Establishment/Modification. The UPF sends data to the NWDAF via the SMF.](fdc47b9a20953c3611add6122f6831bf_img.jpg) + +``` + +sequenceDiagram + participant NWDAF + participant UDM + participant NRF + participant SMF + participant UPF + participant AMF + + Note left of NWDAF: Case1 + NWDAF->>UDM: 1. Nudm_UECM_Get + UDM-->>NWDAF: 2. Nudm_UECM_Get Response + + Note left of NWDAF: Case2 + NWDAF->>NRF: 1. Nnrf_NFDiscovery_Request with "UPF Event Exposure capabilities" + NRF-->>NWDAF: 2. Nnrf_NFDiscovery_Request Response + + NWDAF->>SMF: 3. UPF Data Subscription Request with "UPF Event Exposure capabilities" + + Note right of SMF: Case2 + SMF->>NRF: 4a. Nnrf_NFDiscovery_Request/Response with "UPF Event Exposure capabilities" + NRF-->>SMF: + SMF->>AMF: 4b. Namf_EventExposure_Subscribe using "Number of UEs present in a geographical area" + AMF-->>SMF: + Note right of SMF: 4c. Determine the UE list for data reporting + SMF->>UPF: 4.N4 Session Establishment Request/Response + UPF-->>SMF: + SMF->>NWDAF: 5. Nupf_EventExposure_Notify + + Note right of SMF: Case2 + SMF->>AMF: 6a. Namf_EventExposure_Subscribe using "UE moving in or out of Area of Interest" + AMF-->>SMF: + Note right of SMF: 6b. Determine the UE list for data reporting + SMF->>UPF: 6c.N4 Session Modification Request/Response with UE list + UPF-->>SMF: + +``` + +Sequence diagram showing UPF Information Exposure to NWDAF. The diagram illustrates the interaction between NWDAF, UDM, NRF, SMF, UPF, and AMF. It is divided into Case 1 and Case 2. Case 1 involves Nudm\_UECM\_Get and Nupf\_EventExposure\_Notify. Case 2 involves Nnrf\_NFDiscovery\_Request, Namf\_EventExposure\_Subscribe, and N4 Session Establishment/Modification. The UPF sends data to the NWDAF via the SMF. + +Figure 6.10.3-1: UPF Information Exposure to NWDAF + +For case 1, where the NWDAF requests UPF information Exposure for a certain UE or a group of UEs, step 1 and 2 are as follows: + +1. The NWDAF invokes Nudm\_UECM\_Get service operation to retrieve the appropriate SMF by providing UE ID and NF type. + +2. The UDM provides a Nudm\_UECM\_Get response to the NWDAF with the corresponding SMF. + +For case 2, where the NWDAF requests UPF information Exposure for a certain AOI, steps 1 and 2 are as below: + +1. The NWDAF discovers the SMF instances by invoking Nnrf\_NFDiscovery request with UPF Event Exposure Service towards NRF, including Area of Interest, to get the SMF which has the capability to subscribe to UPF on behalf of NWDAF for UPF information reporting. + +NOTE: For UPF, "UPF Event Exposure Service" indicates that the UPF supports information reporting. For SMF, "UPF Event Exposure Service" indicates that the SMF supports to subscribe to UPF on behalf of NWDAF for UPF information reporting. + +2. The NRF responses with SMF ID and SMF IP address to NWDAF. +3. The NWDAF sends the request to the SMF to subscribe UPF data, including the following information: + - Notification Target Address (NWDAF address). + - Indication of UPF Event Exposure Service. + - Event Filter Information: S-NSSAI, Application Id, Area of Interest. + - Target of Event Reporting: a UE or a group of UEs or any UE. + - Subscription Information: + - UL/DL Throughput, UL/DL packets or number of connections. + - N3 delay, N6 delay, E2E delay, UL/DL packet loss, or UL/DL packet retransmission. + - UL/DL Data Volume. +- 4a. For case 2, the SMF discovers the UPF instance by invoking Nnrf\_NFDiscovery request with UPF Event Exposure Service towards NRF, including Area of Interest, to get the UPF which supports user plane data reporting. And the NRF responses with UPF IP address to the SMF. +- 4b. For case 2, the SMF subscribes to AMF by invoking Namf\_EventExposure\_Subscribe with Event "Number of UEs present in a geographical area" to get the UE list 1 in the AOI. +- 4c. SMF locally determines the UE list 2 for user plane data reporting which is included in the Target of Event Reporting sending to UPF. + +If the Target of Event Reporting from NWDAF is a UE or a group of UEs, the SMF determines UE list 2 for user plane data reporting which locate(s) in the AOI by matching the UE or group of UEs from Target of Event Reporting with the UE list 1 from AMF in step 4b. + +If the Target of Event Reporting from NWDAF is any UE, the UE list 2 is the UE list 1 from AMF in step 4b. + +4. The SMF sends the request to the UPF over N4 Session Establishment Request/Response message including the NWDAF address, Event Filter Information, Target of Event Reporting, and Target Subscription Information. For case 1, Target of Event Reporting is the certain UE or the group of UEs same as step 1, For case 2, Target of Event Reporting is the UE list 2 from step 4c. +5. The UPF responds with the locally collected UPF data by invoking Nupf\_EventExposure\_Notify service operation to the NWDAF. +- 6a. For case 2, the SMF keeps monitoring to update UE list 1 by invoking Namf\_EventExposure\_Subscribe with Event "UE moving in or out of Area of Interest". +- 6b. The SMF determines the updated UE list 2 for user plane data reporting same as step 4c with the result from AMF from step 6a. +- 6c. The SMF sends the request to the UPF over N4 Session Modification Request/Response message including the Target of Event Reporting which is the updated UE list from step 6b. And the UPF responds to SMF same as step 5. + +### 6.10.4 Impacts on services, entities and interfaces + +#### UPF: + +- Support newly defined UPF Service to collect UPF data. +- Expose UPF related data collection information to NWDAF. +- Support new indication "UPF Event Exposure Service" and registration to NRF. + +#### SMF: + +- Represent NWDAF to request UPF to collect UPF data. +- Consume UPF service for data collection. +- Support new indication "UPF Event Exposure Service" and registration to NRF. + +#### NRF: + +- Support new indication "UPF Event Exposure Service" registration from SMF and UPF. + +## 6.11 Solution #11: UPF event exposure service to NWDAF subscribed directly from UPF + +### 6.11.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.11.2 Description + +Annex A of this TR has analysed the NWDAF requirements of UPF event exposure service, which contains the following seven aspects of information: + +1. QoS flow level Network Data from 5GC NF related to the QoS profile assigned for a particular service (identified by an Application Id or IP filter information), including QoS flow Bit Rate, QoS flow Packet Delay, Packet transmission, and Packet retransmission. +2. Data collected by NWDAF for UPF load analytics (i.e. Traffic usage report), and service data from 5GC related to UE communication (e.g. UE communications, N4 Session ID, and Inactivity detection time). +3. Data Collected from the UPF or from the AF related to User Data Congestion Analytics, e.g. Application ID, IP Packet Filter Set, Measurement period, Throughput UL/DL, Throughput UL/DL (peak), Timestamp, and Achieved sampling ratio. +4. UE data volume dispersion collected from serving UPF, e.g. UE UP address, Timestamp, Data Volume UL/DL, Application ID, IP 5-tuple, Location of Application, and Application duration. +5. User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific serving anchor UPF/DNAI/Edge Application Server Instance. +6. Data collected by NWDAF for WLAN performance analytics, e.g. UE communications. + +### 6.11.3 Procedures + +For the analytics targeting PDU session related information of a specific UE, e.g. QoS flow level Network Data, UE data volume dispersion, User plane performance analytics for a specific Edge Computing application, the NWDAF can find the UPF by using SUPI, S-NSSAI, and DNN via UDM and SMF, as described in Solution 1. + +For the analytics targeting "any UE" (possibly for specific DNN and or slices), e.g. Data collected by NWDAF for UPF load analytics, User Data Congestion Analytics, Data Volume dispersion analytics, WLAN performance analytics, the + +NWDAF can find the UPF by using S-NSSAI, DNN, or DNAI from NRF that has the UPF registration information, as described in Solution 1. + +![Sequence diagram showing UPF Information Exposure to NWDAF. The diagram involves two entities: NWDAF and UPF. The sequence of messages is: 1. Find the appropriate UPF (internal to NWDAF), 2. Nupf_EventExposure_Subscribe (NWDAF to UPF), and 3. Nupf_EventExposure_Notify (UPF to NWDAF).](195611c20b2dc7ed0fa3033392e22908_img.jpg) + +``` + +sequenceDiagram + participant NWDAF + participant UPF + Note left of NWDAF: 1. Find the appropriate UPF + NWDAF->>UPF: 2. Nupf_EventExposure_Subscribe + UPF-->>NWDAF: 3. Nupf_EventExposure_Notify + +``` + +Sequence diagram showing UPF Information Exposure to NWDAF. The diagram involves two entities: NWDAF and UPF. The sequence of messages is: 1. Find the appropriate UPF (internal to NWDAF), 2. Nupf\_EventExposure\_Subscribe (NWDAF to UPF), and 3. Nupf\_EventExposure\_Notify (UPF to NWDAF). + +**Figure 6.11.3-1: UPF Information Exposure to NWDAF** + +1. The NWDAF find the UPF(s) according to the specific use case. + +For the analytics targeting PDU session related information of a specific UE, e.g. QoS flow level Network Data, UE data volume dispersion, User plane performance analytics for a specific Edge Computing application, the NWDAF can find the UPF by using SUPI, S-NSSAI, and DNN via UDM and SMF, as described in Solution 1. + +For the analytics targeting "any UE" (possibly for specific DNN and or slices), e.g. Data collected by NWDAF for UPF load analytics, User Data Congestion Analytics, WLAN performance analytics, the NWDAF can find the UPF(s) by using AoI, S-NSSAI, DNN, or DNAI from NRF that has the UPF registration information, as described in Solution 1. + +2. The NWDAF sends the request for requesting the collected data over Nupf\_EventExposure\_Subscribe service operation to the UPF(s). For the "Any UE" scenarios, the request is sent to the relevant UPF(s) including filters like S-NSSAI, DNN, or AoI. + +**NOTE:** For the any UE scenarios, different UEs may be served by different UPFs. For the subscription to the same UPF, the UPF will concatenate the collected data of its serving UE into one notification reply message. Therefore, only one notification message of data collections will be sent for "any UE" filtered by specific DNN and/or slices which served by the same UPF. + +If the subscription has included AoI, the UPF need to determine which UEs are in the AoI and whether the UEs are entering/leaving the AoI according to user location information (ULI) received from SMF over N4. + +3. The UPF selects the PDU Sessions that match the filters and responds the requested collected data for the selected PDU Sessions over Nupf\_EventExposure\_Notify service operation to the NWDAF. + +### 6.11.4 Impacts on services, entities and interfaces + +UPF: + +- Newly introduced UPF Service Operations to support NWDAF to subscribe the UPF event exposure service directly. +- Expose UPF related data collection information to NWDAF directly. + +SMF: + +- ULI (User location Information) is provided by SMF to UPF over N4. + +## 6.12 Solution #12: UPF registration to the NRF and NWDAF collecting data from UPF + +### 6.12.1 Key Issue mapping + +This Solution addresses KI#1 and KI#2. + +### 6.12.2 Description + +Regarding to UPF event exposure service, the UPF may support different mechanism of data collection and data reporting per UPF data type, which can be identified with UPF Event IDs. Some of these Event IDs are suitable for direct subscriptions from the NF consumer to the UPF, but some of them are more suitable for indirect subscriptions to the UPF via SMF. For example: + +- Some UPF event IDs such as UPF measurement or detection data per UE controlled by N4 session, it is more appropriate for them to be subscribed by the consumer to the UPF via SMF. +- On the other hand, some UPF event IDs such as UPF load, Traffic usage report UPF measurement or detection data for any UE or some aggregated data for any UE, they are more appropriate to be subscribed by the consumer to the UPF directly without disturbing the SMF. + +In this solution, UPF registration to NRF procedure can be enhanced: + +- The UPF registers to the NRF with information including Supported Event ID(s), direct subscription indication and/or indirect subscription indication. +- The direct subscription indication indicates the UPF supports NF consumer subscribe data directly from it, and the indirect subscription indication indicates the UPF supports NF consumer subscribe data from it via the SMF. +- For direct or indirect subscription, the NF profile can also include the corresponding event ID (s). + +When the NF consumer (e.g. NWDAF) discovers the UPF from the NRF, the NRF determines appropriate UPF(s) matching the input parameters from the NF consumer (e.g. NWDAF), and feedbacks the NF consumer + +- the UPF instance ID + Direct Subscription indication within corresponding UPF NF profile; +- or Indirect Subscription indication within corresponding UPF NF profile. + +Then, the NWDAF subscribes to the UPF directly or indirectly based on the NF discovery outputs from NRF, which are specified in the procedure in clause 6.12.3.2. + +### 6.12.3 Procedures + +#### 6.12.3.1 Procedure for UPF Registration to NRF + +Regarding UPF Registration to NRF, the procedure is same with clause 6.1.2.1: UPF Event Exposure service Registration, except the following change in step 1: + +The UPF NF profile parameters in addition include direct subscription indication and/or indirect subscription indication: + +- The direct subscription indication indicates the UPF supports NF consumer subscribe data directly from it, and the indirect subscription indication indicates the UPF supports NF consumer subscribe data from it via the SMF. +- For direct or indirect subscription, the NF profile can also include the corresponding event ID (s), and for the indirect subscription. + +#### 6.12.3.2 Procedure for NWDAF collecting data from UPF + +![Sequence diagram illustrating the procedure for NWDAF collecting data from UPF. The diagram shows four lifelines: NRF, NWDAF, UPF, and SMF. The sequence of messages is: 1. Nnrf_NFDiscovery_Request from NWDAF to NRF; 2. Nnrf_NFDiscovery_Response from NRF to NWDAF; 3. Direct subscription to UPF from NWDAF to UPF; 4. Indirect subscription to UPF via SMF from NWDAF to SMF.](c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg) + +``` + +sequenceDiagram + participant NRF + participant NWDAF + participant UPF + participant SMF + Note left of NWDAF: 1. Nnrf_NFDiscovery_Request + NWDAF->>NRF: 1. Nnrf_NFDiscovery_Request + Note right of NRF: 2. Nnrf_NFDiscovery_Response + NRF-->>NWDAF: 2. Nnrf_NFDiscovery_Response + Note left of NWDAF: 3. Direct subscription to UPF + NWDAF->>UPF: 3. Direct subscription to UPF + Note left of NWDAF: 4. Indirect subscription to UPF via SMF + NWDAF->>SMF: 4. Indirect subscription to UPF via SMF + +``` + +Sequence diagram illustrating the procedure for NWDAF collecting data from UPF. The diagram shows four lifelines: NRF, NWDAF, UPF, and SMF. The sequence of messages is: 1. Nnrf\_NFDiscovery\_Request from NWDAF to NRF; 2. Nnrf\_NFDiscovery\_Response from NRF to NWDAF; 3. Direct subscription to UPF from NWDAF to UPF; 4. Indirect subscription to UPF via SMF from NWDAF to SMF. + +**Figure 6.12.3.2-1: NWDAF collects data from UPF procedure** + +1. NWDAF that requires UPF data invokes Nnrf\_NFDiscovery\_Request message to NRF to find appropriate UPF(s), including target NF service Name (i.e. UPF Event Exposure Service), AOI, target NF type (i.e. UPF), Event ID, S-NSSAI, DNN, DNAI. +2. The NRF determines one or more appropriate UPF(s) matching the input parameters included in the Nnrf\_NFDiscovery\_Request. The NRF sends the NF discovery outputs to the NWDAF. + +The output includes one or more UPF instances, and for each UPF instance it includes UPF NF profile: + +- If a UPF supports NF consumer subscribes the event ID directly from it, the feedback UPF NF profile includes Direct Subscription indication in it. +- If a UPF supports NF consumer subscribes the event ID from it via SMF, the feedback UPF NF profile includes Indirect Subscription indication. + +The NWDAF subscribes to the UPF directly or indirectly based on the NF discovery outputs from NRF. + +3. For the discovered UPF instance with Direct Subscription indication in the UPF NF profile, the NWDAF subscribes to the UPF for the event ID by invoking Nupf\_EventExposure Subscribe. +4. For the discovered UPF instance with Indirect Subscription indication in the UPF NF profile, the NWDAF discovers the SMF as described in solution 10 for a certain UE scenario or a certain AOI scenario, and then the NWDAF subscribes to the SMF by invoking Nsmf\_EventExposure Subscribe for the event ID of UPF. Then the SMF on behalf of the NWDAF performs data collection from UPF with N4 procedure. + +The UPF responds the requested collected data over Nupf\_EventExposure\_Notify service operation to the NWDAF. + +### 6.12.4 Impacts on services, entities and interfaces + +#### UPF: + +- Registers to the NRF with information including direct subscription indication and/or indirect subscription indication. + +#### NRF: + +- The NRF registers for the UPF with information including direct subscription indication and/or indirect subscription indication. +- The NRF discovers appropriate UPF(s) matching the input parameters from the NF consumer (e.g. NWDAF), and feedbacks the NF consumer the UPF instance ID with corresponding UPF NF profile, which includes Direct Subscription indication or Indirect Subscription indication. + +#### UPF data consumer (e.g. NWDAF): + +- Subscribes to the UPF directly or indirectly based on the NF discovery outputs from NRF. + +## 6.13 Solution #13: Subscription to UPF Event Exposure Services in the event of UP Path change + +### 6.13.1 Key Issue mapping + +This solution addresses KI#2. + +### 6.13.2 Description + +This solution aims to provide a mechanism of subscribing to the Target UPF in the perspective of the Consumer NF when either a UPF is relocated or an I-UPF is inserted. + +While subscribing to UPF's Event Exposure Service, consumer NF can indicate to the subscribed UPF (source UPF) the following: + +1. An indication of notifying the information of new UPF (in case UPF is relocated, or a additional UPF is added for the PDU Session path), or, +2. An indication to subscribe to the new UPF on behalf of it. + +The Source UPF may then subscribe to the relevant SMF for notification of UP path change. The SMF then informs the Target UPF instance ID and other relevant information to the Source UPF. + +The rest of the solution is described in the next section. + +**Editor's note:** Although the proposed solution utilizes SMF event Exposure service for getting the target UPF information; we can discuss solutions which leverages N4 for the required task. + +### 6.13.3 Procedures + +![Sequence diagram illustrating the procedure for UPF Event Exposure Services. The diagram shows interactions between Source UPF, Target UPF, SMF, and NEF/NWDAF. The sequence starts with the Source UPF sending a Nupf_EventExposure_Subscribe message to the SMF. The SMF then decides on UPF relocation and sends an Nsmf_EventExposure_Notify message to the Source UPF. The Source UPF then sends a Nupf_EventExposure_Notify message to the Target UPF. The Target UPF then sends a Nupf_EventExposure_Subscribe message to the SMF. The SMF then sends an Nupf_EventExposure_Notify message to the Target UPF. The Target UPF then sends a Nupf_EventExposure_Subscribe message to the Source UPF. The Source UPF then sends a Nupf_EventExposure_Notify message to the Target UPF.](a97a427b0f8a6387479a88cd85b2a1a6_img.jpg) + +``` + +sequenceDiagram + participant Consumer NF + participant Source UPF + participant Target UPF + participant SMF + participant NEF/NWDAF + + Note left of Consumer NF: 0. Nupf_EventExposure_Subscribe + Consumer NF->>Source UPF: 1. Nsmf_EventExposure_Subscribe + Source UPF->>SMF: 2. SMF decides UPF relocation + SMF-->>Source UPF: 3. Nsmf_EventExposure_Notify + Source UPF-->>NEF/NWDAF: 4. Nupf_EventExposure_Notify + Source UPF-->>Consumer NF: 5. Nupf_EventExposure_Subscribe/Unsubscribe + Target UPF-->>SMF: 6. Nupf_EventExposure_Subscribe + SMF-->>Target UPF: 7. Nupf_EventExposure_Notify + Target UPF-->>Source UPF: 8. Nupf_EventExposure_Subscribe + Source UPF-->>NEF/NWDAF: 9. Nupf_EventExposure_Notify + +``` + +Sequence diagram illustrating the procedure for UPF Event Exposure Services. The diagram shows interactions between Source UPF, Target UPF, SMF, and NEF/NWDAF. The sequence starts with the Source UPF sending a Nupf\_EventExposure\_Subscribe message to the SMF. The SMF then decides on UPF relocation and sends an Nsmf\_EventExposure\_Notify message to the Source UPF. The Source UPF then sends a Nupf\_EventExposure\_Notify message to the Target UPF. The Target UPF then sends a Nupf\_EventExposure\_Subscribe message to the SMF. The SMF then sends an Nupf\_EventExposure\_Notify message to the Target UPF. The Target UPF then sends a Nupf\_EventExposure\_Subscribe message to the Source UPF. The Source UPF then sends a Nupf\_EventExposure\_Notify message to the Target UPF. + +**Figure 6.13.3.1: Overview of procedure** + +A description of the procedure in Figure 6.13.3.1 is as follows: + +0. The consumer NF subscribes to Source UPF for event exposure services. In the request it provides indication for: + - A. Indication for getting Target UPF info in case of UPF relocation. + +- B. Indication of subscribing to target UPF on behalf of the consumer NF in case UPF relocation happens. +- 1. UPF subscribes for event notification for UPF relocation for the relevant PDU Session. +- 2. SMF decides for UPF relocation for the relevant PDU Session. +- 3. SMF notifies the Source UPF regarding UPF ID of target UPF, and other relevant information related to Event Exposure service endpoint. +- 4. Based on the subscription request in Step. 0, Source UPF notifies the NF with the information received from the SMF. + +**Editor's note:** It is FFS whether the solution is in the scope as per the architectural assumption. The UPF can only expose 5GC information which is originated in the UPF. + +- 5. Consumer NF may decide to unsubscribe or modify the Event Exposure Subscription. +- 6. If the Consumer NF chose option A in step 0, it may subscribe to Target UPF for event exposure service for the relevant PDU Session. +- 7. Target UPF notifies regarding the subscribed events. +- 8. If the consumer NF chose option B in step 0, the Source UPF subscribes to the relocated UPF on behalf of it. (Notification target is that of Consumer NF). +- 9. Target UPF notifies regarding the subscribed events. + +**Editor's note:** For any UE scenarios, how to reduce the multiple notification message of target UPF(s) from UPF is FFS. + +### 6.13.4 Impacts on services, entities and interfaces + +Changes in Nsmf\_EventExposure service (or N4 signalling in the case we utilize N4). + +Changes in Nupf\_Event\_Exposure service. + +## 6.14 Solution #14: Reduce the UPF performance impacts due to data reporting to NF consumer + +### 6.14.1 Key Issue mapping + +This solution is for the "Key Issue#2: Support UPF expose information to other NFs" especially focus on how to reduce the UPF performance impacts due to data reporting to NWDAF. + +The performance issue is also indicated in the Architectural Requirements i.e. clause 4.2: + +- *The performance of UPF user plane traffic handling shall not be degraded due to mechanisms defined in this study.* + +### 6.14.2 Description + +As defined in Annex A, multiple UPF information per Analytics ID are expected to be collected to help data analytics in NWDAF. However, it should be avoided the UPF's user plane traffic handling performance degradation due to UPF data reporting to NWDAF. + +For example, the scope of the UPF data collection by NWDAF may be per AoI or per S-NSSAI (e.g. for the Service Experience as defined in clause 6.4 of TS 23.288 [5] and Abnormal Behaviour analytics as defined in clause 6.7.5 of TS 23.288 [5]), which means UE level UPF data in the UPFs, which is for all the UE associated the indicated the AoI or S-NSSAI, need be reported to NWDAF. If the UE number is quite a big, the reporting impact to the UPF performance cannot be neglected. + +There are following mechanisms can be considered on how to alleviate this event reporting impact to UPF performance: + +1. Reuse the SMF based subscription/ notification mechanism: If different NWDAF subscribes the same UPF data to the UPF via the SMF, the SMF may combine the different subscriptions from different NWDAFs into one configuration/instruction to the UPF. The UPF will be instructed by SMF to report either directly to each NWDAF, or to the SMF via existing N4 interface. The SMF per different subscription information received before, it notify/distribute the UPF reports to different NWDAFs according to the subscriptions from the NWDAFs. + +NOTE: If DCCF is deployed, it may be possible to consolidate subscriptions towards SMF. + +2. Enhance the existing event subscription mechanism: UPF data for data analysis is not always time sensitive (especially for the training dataset collection). It is preferred not to immediately send those event notifications to the NWDAF when the event is detected but the UPF is at peak hour. Hence the event subscription can be enhanced as follows: + +- Add a new IE, i.e. Reporting suggestion information, in the Event Reporting Information. The Reporting suggestion information includes Report urgency and Reporting window two information. Reporting urgency information represents whether this event report can be delay tolerant, i.e. the event report can be delayed. When the related event is detected, the Reporting window defines the last reporting valid time. For example if the event can be reported within two hours of the event detection, the reporting windows is two hours. + +NOTE: Trade off between report sending and report storage needs to be evaluated at deployment. + +3. Aggregating the event subscription/Notification: For the UE level UPF data reporting normally the granularity of event subscription and reporting is per UE level, i.e. each UE have a separated event subscription and event reporting. To reduce the number of event notification, when the UE level UPF event is subscribed, the subscription and notification can be per node level. + +This mechanism can be combined with bullet 2. If the event which can be delay tolerant, the event subscription is per node level. When the event is detected, the UPF can aggregate the event notification. Within the event notification, the UE ID or other identifier is added to differentiate different UE related UPF event. Hence it can reduce the event notification sent to the NF consumer. + +The above mechanism can be generalized to be applied for any NF consumer of UPF event exposure service. + +### 6.14.3 Procedures + +The enhancement on existing UPF event exposure subscription and notification service procedure is described as in clause 6.14.2. + +### 6.14.4 Impacts on services, entities and interfaces + +NF consumer of UPF event exposure service: + +- Event Reporting Information: + - Add a new IE, i.e. Reporting suggestion information. It includes reporting urgency and reporting window information. +- Support UE level different UPF event subscription/notification can be aggregated as per Node level. + +UPF: + +- Per received Reporting suggestion information in the event subscription, the UPF can delay the event reporting. +- Support UE level different UPF event subscription/notification can be aggregated as per Node level. + +## 6.15 Solution #15: Subscription of UPF Event Exposure Service + +### 6.15.1 Key Issue mapping + +This solution is for KI#2. + +### 6.15.2 Description + +The solution introduces for the AF to subscribe to UPF Event Exposure served by the UPF handling a specific IP Flow over the PDU session. In this solution, we provide how to discover the specific UPF with UE IP address. + +### 6.15.3 Procedures + +#### 6.15.3.1 UPF Event Exposure using NEF + +##### 6.15.3.1.1 Procedure of UPF service operations information flow + +The procedure is used by the AF/NEF to subscribe event notification to the UPF handling a specific PDU session. Cancelling is done by Nupf\_EventExposure\_Unsubscribe request identifying the subscription to cancel. + +![Sequence diagram showing the procedure of UPF service operations information flow between AF, NEF, BSF, and UPF.](b5987d63203a5fa601921039922ac520_img.jpg) + +``` +sequenceDiagram + participant AF + participant NEF + participant BSF + participant UPF + Note left of AF: 1. Nnef_EventExposure_Subscribe / Unsubscribe Request + AF->>NEF: 1. Nnef_EventExposure_Subscribe / Unsubscribe Request + Note left of NEF: 2. Nbsf_EventExposure_Subscribe / Unsubscribe Request + NEF->>BSF: 2. Nbsf_EventExposure_Subscribe / Unsubscribe Request + Note left of BSF: 3. Nupf_EventExposure_Subscribe / Unsubscribe Request + BSF->>UPF: 3. Nupf_EventExposure_Subscribe / Unsubscribe Request + Note left of UPF: 4. Nupf_EventExposure_Subscribe / Unsubscribe Response + UPF->>BSF: 4. Nupf_EventExposure_Subscribe / Unsubscribe Response + Note left of BSF: 5. Nbsf_EventExposure_Subscribe / Unsubscribe Response + BSF->>NEF: 5. Nbsf_EventExposure_Subscribe / Unsubscribe Response + Note left of NEF: 6. Nnef_EventExposure_Subscribe / Unsubscribe Response + NEF->>AF: 6. Nnef_EventExposure_Subscribe / Unsubscribe Response +``` + +Sequence diagram showing the procedure of UPF service operations information flow between AF, NEF, BSF, and UPF. + +**Figure 6.15.3.1.1: Procedure of UPF service operations information flow** + +1. In order to subscribe to Event Exposure service on a specific PDU session, the AF sends a request to the NEF with UE IP address. +2. The NEF sends the request to the BSF. +3. Based on UE IP address, the BSF can identify the specific UPF and sends the request to it. +- 4-6. Acknowledgements for each request. + +##### 6.15.3.1.2 Procedure of UPF information in BSF + +The procedure is used for storing UPF information in BSF. + +![Sequence diagram showing the procedure of UPF information in BSF. The diagram involves three entities: SMF, PCF, and BSF. A box labeled '0. PDU Session Establishment Procedure' spans across the top. Below it, the SMF sends a '1.Npcf_SMPolicyControl_Update Request (UE IP address,..., UPF ID)' to the PCF. The PCF then sends a '2.Nbsf_Management_Register Request (GPSI, UE IP address,..., UPF ID)' to the BSF.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant PCF + participant BSF + Note over SMF, PCF, BSF: 0. PDU Session Establishment Procedure + SMF->>PCF: 1.Npcf_SMPolicyControl_Update Request (UE IP address,..., UPF ID) + PCF->>BSF: 2.Nbsf_Management_Register Request (GPSI, UE IP address,..., UPF ID) + +``` + +Sequence diagram showing the procedure of UPF information in BSF. The diagram involves three entities: SMF, PCF, and BSF. A box labeled '0. PDU Session Establishment Procedure' spans across the top. Below it, the SMF sends a '1.Npcf\_SMPolicyControl\_Update Request (UE IP address,..., UPF ID)' to the PCF. The PCF then sends a '2.Nbsf\_Management\_Register Request (GPSI, UE IP address,..., UPF ID)' to the BSF. + +**Figure 6.15.3.1.1: Procedure of UPF information in BSF** + +0. The UE requests PDU session establishment. +1. During the PDU session establishment, the SMF sends Npcf\_SMPolicyControl\_Update Request message to the PCF with UE IP address and UPF ID information. +2. The PCF sends Nbsf\_Management\_Register Request message to the BSF with UE IP address and UPF ID information. + +### 6.15.4 Impacts on services, entities and interfaces + +*Editor's note: This clause captures impacts on existing 3GPP nodes and functional elements.* + +## 6.16 Solution #16: Direct/indirect subscription of the UPF event exposure service + +### 6.16.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.16.2 Description + +The UPF event exposure service needs to be permitted when a consumer NF wants to subscribe this service. This includes two scenarios: + +- When the consumer NF subscribes the UPF event exposure service from UPF directly. +- When the consumer NF subscribes the UPF event exposure service via an SMF. + +The solution introduces the subscription methods for both of the scenarios, including subscribing the UPF event service via user plane and via control plane. The consumer NFs may be AF/NEF, NWDAF. The UPF may support Nupf\_EventExposure\_Subscribe service operation. The SMF may support Nsmf\_UPFAccessAuthorization service operation. + +### 6.16.3 Procedures + +#### 6.16.3.1 UPF event exposure service subscription directly from the UPF + +![Sequence diagram for UPF event exposure service subscription directly from the UPF. The diagram shows three lifelines: Consumer NF, UPF, and SMF. The sequence of messages is: 0. Find the appropriate UPF (a self-call on the Consumer NF), 1. Nupf_EventExposure_Subscribe request (from Consumer NF to UPF), 2. Report the subscription request or indication (from UPF to SMF), 3. Nupf_EventExposure_Subscribe response (from SMF to Consumer NF via a dashed line), and 4. Nupf_EventExposure_Notify (from UPF to Consumer NF).](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +``` + +sequenceDiagram + participant Consumer NF + participant UPF + participant SMF + Note over Consumer NF: 0. Find the appropriate UPF + Consumer NF->>UPF: 1. Nupf_EventExposure_Subscribe request + UPF->>SMF: 2. Report the subscription request or indication + SMF-->>Consumer NF: 3. Nupf_EventExposure_Subscribe response + UPF->>Consumer NF: 4. Nupf_EventExposure_Notify + +``` + +Sequence diagram for UPF event exposure service subscription directly from the UPF. The diagram shows three lifelines: Consumer NF, UPF, and SMF. The sequence of messages is: 0. Find the appropriate UPF (a self-call on the Consumer NF), 1. Nupf\_EventExposure\_Subscribe request (from Consumer NF to UPF), 2. Report the subscription request or indication (from UPF to SMF), 3. Nupf\_EventExposure\_Subscribe response (from SMF to Consumer NF via a dashed line), and 4. Nupf\_EventExposure\_Notify (from UPF to Consumer NF). + +**Figure 6.16.3.1-1: UPF event exposure service subscription directly from the UPF** + +0. The consumer NF finds the appropriate UPF(s) by using the UPF selection method as described in clause 6.1.2.5. +1. The consumer NF sends an Nupf\_EventExposure\_Subscribe request to the UPF for information exposure. The request includes the NF identity information of the consumer NF (e.g. NF name, NF type, IP address, FQDN), UPF event exposure mode (e.g. event-triggered, and periodically-triggered with a timer), exposure duration and the information expected to be exposed. + +The consumer may request the UPF to expose UE-level information or NF-level information. If the request information is UE-level, the request may include UE IP address, UE ID (i.e. SUCI, GPSI), PDU session ID, and QFI. The information expected to be exposed may be UE related, e.g. UE location and PDU session rate. If the request information is NF-level, the information expected to be exposed may be UPF related, e.g. UPF load. + +2. If consumer NF requests for provision information, i.e. UPF load and QoS parameters, skip step 2. If consumer NF requests for other information (e.g. measurement information), the UPF report the subscription request to the SMF (or to the PCF via the SMF) to decide whether, what information and how the UPF can expose to the consumer NF. The report includes the information received by UPF in step 1. + +The SMF/PCF determines whether, what information and how the request is permitted based on the local strategy together with the received information (e.g. NF type of the consumer NF, the information expected to be exposed), and responds to the UPF (directly or via the SMF). + +Alternatively, the UPF may decide whether, what information and how the UPF can expose to the consumer NF by itself, and reports an indication to the SMF/PCF. + +3. (Optional) The UPF sends an Nupf\_EventExposure\_Subscribe response message to the consumer NF. The response includes an indication to whether the request in step 1 is successful or not. + +If the subscription request is successful, the response may include the UPF event exposure mode (e.g. event-triggered, and periodically-triggered with a timer), exposure duration, whether the exposed information is NF-level or UE-level, and the information exposed to the consumer NF. If the subscription request is not successful, the response includes a Cause value indicating that the subscription failed. + +4. The UPF exposes the information determined in step 2 directly to the consumer NF over Nupf\_EventExposure\_Notify service operation. + +#### 6.16.3.2 UPF event exposure service subscription via an SMF + +![Sequence diagram illustrating UPF event exposure service subscription via an SMF. The diagram shows three lifelines: Consumer NF, SMF, and UPF. The sequence of messages is: 0. Find the appropriate SMF (internal to Consumer NF), 1. Subscription request (Consumer NF to SMF), 2. Subscription decision (internal to SMF), 3a. Subscription event notification via N4 interface (SMF to UPF), 3b. Subscription response (SMF to Consumer NF), and 4. Nupf_EventExposure_Notify (UPF to Consumer NF).](4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg) + +``` + +sequenceDiagram + participant Consumer NF + participant SMF + participant UPF + Note left of Consumer NF: 0. Find the appropriate SMF + Consumer NF->>SMF: 1. Subscription request + Note right of SMF: 2. Subscription decision + SMF->>UPF: 3a. Subscription event notification via N4 interface + SMF->>Consumer NF: 3b. Subscription response + UPF->>Consumer NF: 4. Nupf_EventExposure_Notify + +``` + +Sequence diagram illustrating UPF event exposure service subscription via an SMF. The diagram shows three lifelines: Consumer NF, SMF, and UPF. The sequence of messages is: 0. Find the appropriate SMF (internal to Consumer NF), 1. Subscription request (Consumer NF to SMF), 2. Subscription decision (internal to SMF), 3a. Subscription event notification via N4 interface (SMF to UPF), 3b. Subscription response (SMF to Consumer NF), and 4. Nupf\_EventExposure\_Notify (UPF to Consumer NF). + +**Figure 6.16.3.2-1: UPF event exposure service subscription via an SMF** + +0. The consumer NF finds the appropriate SMF as described in other solutions. +1. The consumer NF sends a subscription request to the SMF to subscribe to direct notification of UPF Event Exposure. + +NOTE: The request may be over the Nsmf\_UPFAccessAuthorization\_Create/Subscribe service operation. + +The request includes the NF identity information of the consumer NF (e.g. NF name, NF type, IP address, FQDN), UPF event exposure mode (e.g. event-triggered, and periodically-triggered with a timer), the exposure duration, and the information expected to be exposed. + +The consumer NF may request the UPF to expose UE-level information or NF-level information. If the request information is UE-level, the request includes UE IP address, UE ID (i.e. SUCI, GPSI), PDU session ID, and QFI. The information expected to be exposed may be UE related, e.g. UE location and PDU session rate. If the request information is NF-level, the information expected to be exposed may be UPF related, e.g. UPF load. + +2. The SMF determines whether, what information and how the UPF can expose to the consumer NF based on the local strategy together with the received information (e.g. NF type of the consumer NF, the information expected to be exposed). Optionally, the SMF may make the decision by considering the subscription information of this UE (if the request information is UE-level) from UDM. +3. If the subscription request is successful, the SMF sends a notification of direct event exposure to the UPF via the N4 interface. The notification may include the UPF event exposure mode (e.g. event-triggered, and periodically-triggered with a timer), the exposure duration, whether the exposed information is NF-level or UE-level, and the information exposed to the consumer NF. + +The SMF may send a subscription response to the consumer NF including an indication that the request in step 1 is successful. + +If the subscription request is not successful, the response includes a Cause value indicating that the subscription failed. + +4. The UPF exposes the information determined in step 2 directly to the consumer NF over Nupf\_EventExposure\_Notify service operation. + +### 6.16.4 Impacts on services, entities and interfaces + +UPF: + +- Newly introduced UPF Service Operations to support other NFs to subscribe the UPF event exposure service directly. + +SMF: + +- Newly introduced SMF Service and Service Operations to represent other NFs to subscribe the UPF event exposure service indirectly. + +## 6.17 Solution #17: Update/Release subscription of the UPF event exposure service + +### 6.17.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.17.2 Description + +The UPF event exposure service subscription may need to be updated or released based on the consumer NF's requirement. This includes two scenarios: + +- Update/release UPF event exposure service subscription directly by UPF. +- Update/release UPF event exposure service subscription via an SMF. + +The solution introduces the updating/releasing subscription methods for both of the scenarios. The UPF may support Nupf\_EventExposure\_Unsubscribe and Nupf\_EventExposure\_ModifySubscription service operation. The SMF may support Nsmf\_UPFAccessAuthorization service operation. + +### 6.17.3 Procedures + +#### 6.17.3.1 Update/release UPF event exposure service subscription directly by UPF + +If the subscription of the UPF event exposure service by the consumer NF is sent directly to UPF, the updating/releasing procedure is as follow. + +![Sequence diagram showing the update/release UPF event exposure service subscription directly by UPF. The diagram involves three participants: Consumer NF, UPF, and SMF. The sequence of messages is: 1. Consumer NF sends a Nupf_EventExposure_ModifySubscription/Unsubscribe request to the UPF. 2. The UPF sends a 'Report the update/release request or indication' to the SMF. 3. The UPF sends a Nupf_EventExposure_ModifySubscription/Unsubscribe response to the Consumer NF. 4. The UPF sends a Nupf_EventExposure_Notify to the Consumer NF.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` +sequenceDiagram + participant Consumer NF + participant UPF + participant SMF + Note left of Consumer NF: 1. Nupf_EventExposure_ModifySubscription/Unsubscribe request + Consumer NF->>UPF: Request + Note right of UPF: 2. Report the update/release request or indication + UPF->>SMF: Request + Note right of SMF: + SMF-->>UPF: Response + Note right of UPF: 3. Nupf_EventExposure_ModifySubscription/Unsubscribe response + UPF-->>Consumer NF: Response + Note right of UPF: 2. Nupf_EventExposure_Notify + UPF-->>Consumer NF: Notify +``` + +Sequence diagram showing the update/release UPF event exposure service subscription directly by UPF. The diagram involves three participants: Consumer NF, UPF, and SMF. The sequence of messages is: 1. Consumer NF sends a Nupf\_EventExposure\_ModifySubscription/Unsubscribe request to the UPF. 2. The UPF sends a 'Report the update/release request or indication' to the SMF. 3. The UPF sends a Nupf\_EventExposure\_ModifySubscription/Unsubscribe response to the Consumer NF. 4. The UPF sends a Nupf\_EventExposure\_Notify to the Consumer NF. + +**Figure 6.17.3.1-1: Update/release UPF event exposure service subscription directly by UPF** + +1. The consumer NF sends an Nupf\_EventExposure\_ModifySubscription (or Nupf\_EventExposure\_Unsubscribe) request to the UPF to update the subscription of (or unsubscribe) the UPF event exposure service. The request includes the consumer NF's Subscription Correlation ID. +2. Optionally, the UPF may report the update/release request to the SMF (or to the PCF via the SMF) to decide whether and what information to update/release. The request includes the information received by UPF in step 1. + +The SMF/PCF determines whether and what information to update based on the local strategy together with the received information (e.g. NF type of the consumer NF, the information expected to be updated), and responds to the UPF (directly or via the SMF). + +Alternatively, the UPF may decide whether and what information to update or whether to release the subscription by itself, and reports an indication to the SMF/PCF. + +3. The UPF sends a response message to the consumer NF including an indication to whether the ModifySubscription/Unsubscribe request is successful or not. If the request is not successful, the response includes a Cause value indicating that the update/release failed. +4. The UPF sends the updating/releasing notification related with the updated information (if the notification is updating the exposed information) to the consumer NF over Nupf\_EventExposure\_Notify service operation. + +#### 6.17.3.2 Update/release UPF event exposure service subscription via an SMF + +If the subscription of the UPF event exposure service by the consumer NF is via an SMF, the subscription updating procedure is as follows. + +![Sequence diagram showing the update UPF event exposure service subscription via an SMF. The diagram involves three participants: Consumer NF, SMF, and UPF. The sequence of messages is: 1. Subscription Updating request from Consumer NF to SMF; 2. Update decision from SMF to UPF; 3a. N4 Session Modification from SMF to UPF; 3b. Subscription Updating response from SMF to Consumer NF; 4. Nupf_EventExposure_Notify from UPF to Consumer NF.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant Consumer NF + participant SMF + participant UPF + Note right of SMF: 2. Update decision + Note right of SMF: 3a. N4 Session Modification + Consumer NF->>SMF: 1. Subscription Updating request + SMF->>UPF: 2. Update decision + SMF->>UPF: 3a. N4 Session Modification + SMF->>Consumer NF: 3b. Subscription Updating response + UPF->>Consumer NF: 4. Nupf_EventExposure_Notify + +``` + +Sequence diagram showing the update UPF event exposure service subscription via an SMF. The diagram involves three participants: Consumer NF, SMF, and UPF. The sequence of messages is: 1. Subscription Updating request from Consumer NF to SMF; 2. Update decision from SMF to UPF; 3a. N4 Session Modification from SMF to UPF; 3b. Subscription Updating response from SMF to Consumer NF; 4. Nupf\_EventExposure\_Notify from UPF to Consumer NF. + +**Figure 6.17.3.2-1: Update UPF event exposure service subscription via an SMF** + +1. The consumer NF sends an updating subscription request to the SMF to update the information exposed from the UPF. + +NOTE: The request may be over the Nsmf\_UPFAccessAuthorization\_Update service operation. + +The request includes the consumer NF's Subscription Correlation ID, the UPF identity information (e.g. UPF IP address and FQDN), NF identity information of the consumer NF (e.g. NF name, NF type, IP address, FQDN), and the information expected to be updated. + +2. The SMF determines whether to update the information exposure from the UPF to the consumer NF according to the local strategy together with the received information (e.g. NF type of the consumer NF, the information expected to be updated/released). +3. If the SMF permits the request in step 1, the SMF sends a notification for updating the information exposed to the consumer NF directly to the UPF via the N4 Session modification procedure. The notification includes the information to be updated. The SMF may send the response to the consumer NF including the decision result. + +If the request in step 1 is not permitted, the SMF sends the response to the consumer NF including the Cause value of refusal cause. + +4. The UPF sends the updating notification to the consumer NF about the exposed information to the consumer NF over the Nupf\_EventExposure\_Notify service operation. The notification includes the updated information to be exposed. + +In this case, the subscription releasing procedure is the same with the steps in clause 6.17.3.1. + +### 6.17.4 Impacts on services, entities and interfaces + +UPF: + +- Newly introduced UPF Service Operations to support other NFs to modify subscription of (or unsubscribe) the UPF event exposure service directly. + +SMF: + +- Newly introduced SMF Service and Service Operations to represent other NFs to update/release subscription of the UPF event exposure service indirectly. + +## 6.18 Solution #18: QoS parameters exposure by UPF + +### 6.18.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.18.2 Description + +In order to obtain QoS parameters with low latency, the AF may request to expose QoS parameters from UPF directly. The AF may want to know the QoS parameters for two reasons: + +- If UPF receives a dynamic PCC rule from PCF, the AF may want to verify whether the UPF uses the QoS parameters as configured in the PCC rule. +- If UPF does not receive a dynamic PCC rule from PCF and use the default configuration, the AF may want to know the default configuration used by UPF. + +The UPF may be instructed to report information about a QoS flow directly to the NEF, i.e. by passing the SMF and the PCF. This reporting may target a third-party AF that wants to know the QoS parameters (e.g. 5QI Value, Resource type, flow bit rates (GFBR, MFBR), packet rate, Usage report) used by UPF to guarantee the QoS flow. By exposing this information directly from UPF to NEF, the AF can know the QoS parameters with flexibility and low latency. + +NOTE: Exposing the QoS parameters from UPF to AF directly is to find a way with lower latency and higher flexibility. + +### 6.18.3 Procedures + +![Sequence diagram illustrating the QoS parameters exposure by UPF. The diagram shows three lifelines: AF, L-NEF, and UPF. The sequence of messages is: 1. AF sends Nnef_EventExposure_Subscribe request to L-NEF; 2. L-NEF finds the appropriate UPF (internal step); 3. L-NEF sends Nupf_EventExposure_Subscribe to UPF; 4. UPF sends Nupf_EventExposure_Notify to L-NEF; 5. L-NEF sends Nnef_EventExposure_Subscribe response to AF.](a02b188a5fd52c99f84255322873bf29_img.jpg) + +``` +sequenceDiagram + participant AF + participant L-NEF + participant UPF + Note right of L-NEF: 2. Find the appropriate UPF + AF->>L-NEF: 1. Nnef_EventExposure_Subscribe request + L-NEF->>UPF: 3. Nupf_EventExposure_Subscribe + UPF->>L-NEF: 4. Nupf_EventExposure_Notify + L-NEF->>AF: 5. Nnef_EventExposure_Subscribe response +``` + +Sequence diagram illustrating the QoS parameters exposure by UPF. The diagram shows three lifelines: AF, L-NEF, and UPF. The sequence of messages is: 1. AF sends Nnef\_EventExposure\_Subscribe request to L-NEF; 2. L-NEF finds the appropriate UPF (internal step); 3. L-NEF sends Nupf\_EventExposure\_Subscribe to UPF; 4. UPF sends Nupf\_EventExposure\_Notify to L-NEF; 5. L-NEF sends Nnef\_EventExposure\_Subscribe response to AF. + +Figure 6.18.3-1: QoS parameters exposure by UPF + +1. The AF issues an Nnef\_EventExposure\_Subscribe (Application ID, GPSI, IP address) service operation to request QoS parameters from the L-NEF. +2. The L-NEF finds the appropriate UPF(s) by using the UPF selection method targeting the PDU sessions of a certain UE with information of IP address, as described in clause 6.1.2.5.1. +3. The L-NEF sends the Nupf\_EventExposure\_Subscribe request to the UPF to request QoS parameters. + +NOTE: The QoS parameters requested to be exposed by UPF are configured in the UPF by 5GC which is QoS information used for packet processing. These QoS parameters are associated with PDU sessions and service flows which can be identified by AF, and are originated from the UPF without other operations by the UPF or any additional action from SMF, PCF, 5G AN. + +4. The UPF responds the QoS parameters to L-NEF over the Nupf\_EventExposure\_Notify service operation. +5. The L-NEF responds the QoS parameters to the AF over the Nnef\_EventExposure\_Subscribe service operation. + +### 6.18.4 Impacts on services, entities and interfaces + +UPF: + +- Newly introduced UPF Service Operations to support AF/Local NEF/NEF to subscribe the UPF event exposure service directly. +- Expose QoS parameter related information to AF/Local NEF/NEF directly. + +## 6.19 Solution #19: QoS Monitoring results exposure by UPF + +### 6.19.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.19.2 Description + +Some real time network information, e.g. user path latency, is useful for application layer. In R17, in order to expose network information timely to local AF, the L-PSA UPF may expose network information i.e. QoS monitoring results as defined in TS 23.501 [2], clause 5.33.3, to the local AF. + +The UPF may be instructed to report information about a PDU Session directly to the local NEF/NEF/AF i.e. by passing the SMF and the PCF. The PSA UPF may support Nupf\_EventExposure\_Subscribe service operation. + +### 6.19.3 Procedures + +#### 6.19.3.1 QoS Monitoring results subscription directly from the UPF under the same PCF policy + +![Sequence diagram illustrating the QoS Monitoring results subscription directly from the UPF under the same PCF policy. The diagram shows the interaction between UE, RAN, AMF, L-PSA UPF, SMF, PCF, Local NEF/NEF, and AF. Step 0 involves PDU Session Establishment and UPF information notify to Local NEF/NEF/AF. Step 1 shows the L-PSA UPF sending a Nupf_EventExposure_Subscribe/Notify message to the Local NEF/NEF and AF.](b4415fea4ab6fd9f150a1347d4148525_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant L-PSA UPF + participant SMF + participant PCF + participant Local NEF/NEF + participant AF + + Note over UE, AF: 0. PDU Session Establishment and UPF information notify to Local NEF/NEF/AF + L-PSA UPF-->>Local NEF/NEF: 1. Nupf_EventExposure_Subscribe/Notify + L-PSA UPF-->>AF: 1. Nupf_EventExposure_Subscribe/Notify + +``` + +Sequence diagram illustrating the QoS Monitoring results subscription directly from the UPF under the same PCF policy. The diagram shows the interaction between UE, RAN, AMF, L-PSA UPF, SMF, PCF, Local NEF/NEF, and AF. Step 0 involves PDU Session Establishment and UPF information notify to Local NEF/NEF/AF. Step 1 shows the L-PSA UPF sending a Nupf\_EventExposure\_Subscribe/Notify message to the Local NEF/NEF and AF. + +**Figure 6.19.3.1-1: QoS Monitoring results subscription directly from the UPF under the same PCF policy** + +0. The UE establishes a PDU Session and UPF notifies the QoS monitoring information to Local NEF/NEF/AF as described in step 0-5 in clause 6.4.2.1 of TS 23.548 [7]. The L-PSA UPF sends the direct subscription + +notification to the local AF or the local NEF together with the notification related with QoS monitoring information over Nupf\_EventExposure\_Notify service operation. + +1. (when the reporting goes via local NEF) For the subsequent requests to subscribe direct notification of QoS monitoring from this AF for the same service data flow via Local NEF, the local NEF may directly invoke the Nupf\_EventExposure\_Subscribe service operation. + +During the QoS monitoring initial request, AF allocated Transaction Reference ID to identify service data flow. Subsequent request is used for updating current subscription (e.g. update frequency of QoS monitoring report). AF invokes Nnef\_AFsessionWithQoS\_Update to update subscription for this service data flow with the same Transaction Reference ID. Local NEF can identify the request is for the same service data. + +The L-UPF sends the notification related with QoS monitoring information over Nupf\_EventExposure\_Notify service operation to the local NEF, and local NEF reports to AF. + +#### 6.19.3.2 QoS Monitoring results subscription directly from the UPF without PCF policy control + +This solution is applied for the scenario that AF request to expose QoS monitoring results via a Local NEF. + +![Sequence diagram for QoS Monitoring results subscription directly from the UPF without PCF policy control. The diagram shows five lifelines: AF, Local NEF, UPF, SMF, and PCF. The sequence of messages is: 0. Find the appropriate UPF (AF to UPF), 1. Nupf_EventExposure_Subscribe request (AF to UPF via Local NEF), 2. Report the subscription request of direct event notification and request for Policy update (UPF to SMF), 3. Nupf_EventExposure_Subscribe response (UPF to AF via Local NEF), and 4. Nupf_EventExposure_Notify (UPF to AF via Local NEF).](314da473d582c4327e1e3d56fcba19dd_img.jpg) + +``` + +sequenceDiagram + participant AF + participant Local NEF + participant UPF + participant SMF + participant PCF + + Note over AF, UPF: 0. Find the appropriate UPF + AF->>Local NEF: 1. Nupf_EventExposure_Subscribe request + Local NEF->>UPF: 1. Nupf_EventExposure_Subscribe request + Note over UPF, SMF: 2. Report the subscription request of direct event notification and request for Policy update + UPF->>SMF: 2. Report the subscription request of direct event notification and request for Policy update + Note over UPF, Local NEF: 3. Nupf_EventExposure_Subscribe response + UPF-->>Local NEF: 3. Nupf_EventExposure_Subscribe response + Local NEF-->>AF: 3. Nupf_EventExposure_Subscribe response + Note over UPF, Local NEF: 4. Nupf_EventExposure_Notify + UPF->>Local NEF: 4. Nupf_EventExposure_Notify + Local NEF->>AF: 4. Nupf_EventExposure_Notify + +``` + +Sequence diagram for QoS Monitoring results subscription directly from the UPF without PCF policy control. The diagram shows five lifelines: AF, Local NEF, UPF, SMF, and PCF. The sequence of messages is: 0. Find the appropriate UPF (AF to UPF), 1. Nupf\_EventExposure\_Subscribe request (AF to UPF via Local NEF), 2. Report the subscription request of direct event notification and request for Policy update (UPF to SMF), 3. Nupf\_EventExposure\_Subscribe response (UPF to AF via Local NEF), and 4. Nupf\_EventExposure\_Notify (UPF to AF via Local NEF). + +**Figure 6.19.3.2-1: QoS Monitoring results subscription directly from the UPF without PCF policy control** + +0. The AF finds the appropriate UPF(s) by using the UPF selection method as described in clause 6.1.2.5. +1. The AF requests to subscribe direct notification of QoS monitoring via Local NEF, the local NEF may directly invoke the Nupf\_EventExposure\_Subscribe service operation to the UPF for QoS monitoring results exposure. The request includes the AF identity information (e.g. IP address, FQDN). +2. The UPF reports the subscription request of direct event notification to the SMF. + +SMF sends request to PCF to update rules of QoS monitoring. The PCF makes the policy decision and initiates the PDU Session modification procedure. The PCF includes the indication of direct event notification (including target local NEF or local AF address) for the service data flow within the PCC rule. + +The SMF may activate the end to end UL/DL packet delay measurement between UE and PSA UPF for a QoS Flow to make the UPF obtain the QoS monitoring information, as described in clause 5.33.3 of TS 23.501 [2]. + +3. (Optional) The UPF sends an Nupf\_EventExposure\_Subscribe response message to the Local NEF, and the Local NEF replies to the AF. The response includes an indication to whether the request in step 1 is successful or not. If the subscription request is not successful, the response includes a Cause value indicating that the subscription failed. +4. The UPF sends the notification related with QoS monitoring information over Nupf\_EventExposure\_Notify service operation to the Local NEF, and the Local NEF reports to the AF by invoking Nnef\_EventExposure\_Notify service operation. + +### 6.19.4 Impacts on services, entities and interfaces + +UPF: + +- Newly introduced UPF Service Operations to support AF/Local NEF/NEF to subscribe the UPF event exposure service directly. +- Expose QoS monitoring information to AF/Local NEF/NEF directly. + +SMF: + +- Activate the end to end packet delay measurement based on the UPF's indication. + +## 6.20 Solution #20: UE IP address mapping information exposure by UPF + +### 6.20.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.20.2 Description + +If UPF(s) employs a NAT functionality, the packets behind of the UPF (N6 interface) will use a public IP address (possibly shared by multiple UE(s) when Network Address and Port Translation applies) and the AF may not know the UE private IP address of the UE. + +An AF, in the N6 interface, may detect abnormal events for those packets associated with a UE based on the public IP address and port number (public UE addressing information). The AF does not know the UE private IP address which is internally used in 5GC. Accordingly, the AF may fail to request proper action for the UE (e.g. policy change for the UE) brought the abnormal events, since the AF are not aware of the UE private IP address corresponding to the public UE addressing information. + +In Rel-17, AF specific UE ID retrieval has specified that AF requests corresponding GPSI for an IP address of a UE. However, an IP address that has been NATed is not supported. + +To get the mapped UE private IP address from UE public IP addressing information, the AF may request an UE IP address mapping information exposure to the UPF for a UE. This solution is applicable for the case the UPF supports the NAT, i.e. the NAT function deployed outside the UPF is not supported. + +- NOTE: The case where multiple UEs are allocated with the same private IP address can be addressed as follows: +- When this same private IP address is allocated to different UE(s) for different DNN and S-NSSAI(s) by associating the AF with a DNN and S-NSSAI. + - Otherwise and furthermore, the "ipDomain" attribute as defined in clause 4.2.2.2, Note 3, of TS 29.514 [9] may be leveraged. + +**Editor's note:** Whether these information can be exposed outside to 3rd AS is FFS. + +### 6.20.3 Procedures + +#### 6.20.3.1 UPF registration in NRF with NATed IP pools + +![Sequence diagram for UPF registration in NRF for NATed IP pools](f468e577645d646f5157ce3eefb4ed96_img.jpg) + +``` +sequenceDiagram + participant UPF + participant NRF + Note right of NRF: 2. Store UPF profile + UPF->>NRF: 1. Nnrf_NFManagement_NFRegister_request + NRF-->>UPF: 3. Nnrf_NFManagement_NFRegister_response +``` + +The diagram illustrates the sequence of messages for UPF registration in the NRF. It starts with the UPF sending a '1. Nnrf\_NFManagement\_NFRegister\_request' to the NRF. The NRF then performs an internal action '2. Store UPF profile' and responds with '3. Nnrf\_NFManagement\_NFRegister\_response' back to the UPF. + +Sequence diagram for UPF registration in NRF for NATed IP pools + +**Figure 6.20.3.1-1: UPF registration in NRF for NATed IP pools** + +As illustrated in clause 6.1.2.2, an UPF, supporting the NAT functionality, may register in NRF providing UPF Provision information. The UPF Provision information may include Public IP address pool information (i.e. Public IP address range, additionally ports number range)) for NAT. The Public IP address pool information may be on per DNN and S-NSSAI basis. + +#### 6.20.3.2 UE IP address mapping information exposure by UPF + +![Sequence diagram for UE IP address mapping information exposure by UPF](879d68959f0c0ba370ef82447298ba17_img.jpg) + +``` +sequenceDiagram + participant AF + participant NEF + participant NRF + participant UPF + Note right of NEF: 2. Find the appropriate UPF + AF->>NEF: 1 Nnef_EventExposure_Subscribe Request (UE IP mapping) + NEF->>NRF: 3 Nupf_EventExposure_Subscribe Request (UE IP mapping) + NRF-->>UPF: 4. Nupf_EventExposure_Notify + UPF-->>NEF: 5. Nnef_EventExposure_Notify +``` + +The diagram illustrates the sequence of messages for UE IP address mapping information exposure. It starts with the AF sending a '1 Nnef\_EventExposure\_Subscribe Request (UE IP mapping)' to the NEF. The NEF then performs an internal action '2. Find the appropriate UPF' and sends a '3 Nupf\_EventExposure\_Subscribe Request (UE IP mapping)' to the NRF. The NRF then sends a '4. Nupf\_EventExposure\_Notify' to the UPF. Finally, the UPF sends a '5. Nnef\_EventExposure\_Notify' back to the NEF. + +Sequence diagram for UE IP address mapping information exposure by UPF + +**Figure 6.20.3.2-1: UE IP address mapping information exposure by UPF** + +1. The AF issues Nnef\_EventExposure\_Subscribe (NATed addressing information, AF ID ) service operation to request UE IP address mapping information for a UE. The NATed addressing information comprise a Public IP address and a port number. + +The AF request may be for one-time notification. + +2. The NEF finds the appropriate UPF by using the UPF selection method targeting the NATed addressing information for a UE and the DNN=S-NSSAI associated with the AF ID. This may use NRF discovery (see clause 6.20.3.1). The NEF may also use the NATed addressing information to determine the "ipDomain" attribute as defined in clause 4.2.2.2, Note 3, of TS 29.514 [9]. +3. The NEF sends the Nupf\_EventExposure\_Subscribe request (public UE addressing information, DNN,S-NSSAI associated with the AF ID) to the UPF to request UE IP address mapping information. +4. The UPF responds with the 5GC UE IP address mapping information to NEF over the Nupf\_EventExposure\_Notify service operation. The 5GC UE IP address mapping information comprises a private IP address of the UE. +5. The NEF responds to the AF over the Nnef\_EventExposure\_Notify service operation. The Nnef\_EventExposure\_Notify operation may provide 5GC UE IP addressing mapping information and may additionally include address assistance information which can help to uniquely identify the related IP address. + +**Editor's note:** Whether the DNN/S-NSSAI, ipDomain information is the address assistance information and can be exposed outside to 3rd AS is FFS. + +**Editor's note:** It is FFS how long the binding information can be kept at the AF. + +### 6.20.4 Impacts on services, entities and interfaces + +UPF: + +- Support newly introduced UPF exposure Service Operations for the UE IP address mapping information. +- NAT support in UPF (how to perform NATing is out of 3GPP scope). +- Registration of NATed IP pools per IP Domain in UPF NFprofile. + +NEF: + +- Support newly introduced event exposure for the UE IP address mapping information by UPF. + +NRF: + +- Support UPF registration with UPF NAT information per IP Domain. +- Support UPF discovery with a NATed UE IP address as input. + +## 6.21 Solution #21: UPF Event Exposure with consideration on UPF performance + +### 6.21.1 Key Issue mapping + +This solution addresses "Key Issue#2: Support UPF expose information to other NFs". Especially, it focuses on the following architecture requirements: + +*The performance of UPF user plane traffic handling shall not be degraded due to mechanisms defined in this study.* + +### 6.21.2 Description + +The following mechanism decides whether the UPF event exposure is used or not at any time by taking a consideration on the UPF performance. The operator may want to keep UPF performance rather than to report the information to other NFs according to the threshold on UPF performance. By muting and resuming the UPF reporting based on the threshold of UPF performance configured from operator policy, it would be helpful to manage efficiently the UPF event exposure, and give the operator the flexibility of network deployments and managements. + +To achieve it, a consumer NF (e.g. NEF, AF) may provide in its subscription request the consideration on UPF performance during EventExposure Service subscription for event notification, (e.g. as the reporting suggestion information of Solution#14 or as a new IE in the Event Reporting Information). + +It is assumed that UPF is monitoring its performance by itself and such monitoring depends on the implementation. + +For example, the request is to: + +- indicate to the Event provider NF (i.e. UPF) that the notification of the available events shall be muted if the NF performance exceeds the threshold, providing a subscription to the automatic notification of reporting start/stop due to UPF overload, i.e. the event reporting can be started/stopped per UPF overload. + +NOTE 1: The above notification control implies to the Event provider NF (i.e. UPF) to resume the notification to the Event consumer NF if NF performance does not exceed the threshold. + +NOTE 2: The threshold of NF performance is pre-configured in UPF and may be updated via OAM. + +NOTE 3: This solution is similar to delay reporting of Solution#14, but the event report of this solution is dynamically muted and resumed. + +### 6.21.3 Procedures + +The enhancement on existing UPF event exposure subscription and notification service procedure is described as in clause 6.21.2. + +### 6.21.4 Impacts on services, entities and interfaces + +NF consumer of UPF event exposure service: + +- in the subscription request include the information for the event report notification with the consideration on NF performance. + +UPF: + +- Based on Reporting request information in the event subscription, the UPF can mute/resume the event reporting. + +## 6.22 Solution #22: Support UPF event exposure service subscription update in case of UPF/SMF change + +### 6.22.1 Key Issue mapping + +This is a solution for KI#2. + +### 6.22.2 Description + +In the scenario that a consumer NF requests a single UE related information from the target UPF(s) via UPF event exposure service, a subscription update may be needed when the target PDU Session related UPF changes. + +This solution aims to support the updating of target UPF for UPF event exposure service subscription in the perspective of consumer NF in case of UPF change during the life time of the PDU Session. Two mechanisms are proposed: + +- The consumer NF subscribes SMF/UPF change notification from the SMF. An indication of notifying the consumer NF to subscribe information from new SMF/UPF is triggered once the SMF/UPF for serving the PDU Session changes and detected by the SMF. +- Add UE ID (SUPI, GPSI) and PDU Session ID list with the corresponding UPF ID in the BSF. Then the consumer NF can subscribe the UPF information from the BSF directly. + +The details of these three solutions are described in the next clause. + +### 6.22.3 Procedures + +#### 6.22.3.1 The consumer NF subscribes SMF/UPF change notification from the SMF + +![Sequence diagram illustrating the procedure for a Consumer NF to subscribe to SMF/UPF change notifications. The diagram shows interactions between Consumer NF, Source SMF, Source UPF, Target SMF, and Target UPF. It includes steps for subscription, finding the source SMF, subscription to the source SMF, SMF decision, notification, and then handling two cases: SMF change (steps 5-7) and UPF change (steps 8-10).](a634891d16b60b21df90a35c2af72c67_img.jpg) + +``` + +sequenceDiagram + participant Consumer NF + participant Source SMF + participant Source UPF + participant Target SMF + participant Target UPF + + Note left of Consumer NF: 0. Nupf_EventExposure_Subscribe + Consumer NF->>Source SMF: 0. Nupf_EventExposure_Subscribe + Note left of Source SMF: 1. Find the Source SMF + Consumer NF->>Source SMF: 2. Nsmf_EventExposure_Subscribe + Note left of Source SMF: 3. SMF decides UPF relocation + Source SMF->>Consumer NF: 4. Nsmf_EventExposure_Notify + Note left of Consumer NF: 5. Nsmf_EventExposure_Unsubscribe + Consumer NF-->>Source SMF: 5. Nsmf_EventExposure_Unsubscribe + Note left of Source SMF: Case 1: in case of SMF change + Note left of Consumer NF: 6. Find the Target SMF + Consumer NF-->>Target SMF: 7. Nsmf_EventExposure_Subscribe + Note left of Consumer NF: 8. Nupf_EventExposure_Unsubscribe + Consumer NF-->>Source SMF: 8. Nupf_EventExposure_Unsubscribe + Note left of Source SMF: Case 2: in case of UPF change + Consumer NF-->>Target UPF: 9. Nupf_EventExposure_Subscribe + Consumer NF-->>Target UPF: 10. Nupf_EventExposure_Notify + +``` + +Sequence diagram illustrating the procedure for a Consumer NF to subscribe to SMF/UPF change notifications. The diagram shows interactions between Consumer NF, Source SMF, Source UPF, Target SMF, and Target UPF. It includes steps for subscription, finding the source SMF, subscription to the source SMF, SMF decision, notification, and then handling two cases: SMF change (steps 5-7) and UPF change (steps 8-10). + +**Figure 6.22.3.1-1: Consumer NF subscribes UPF/SMF relocation notification from the SMF** + +0. The consumer NF subscribes to Source UPF for event exposure service. +1. The consumer NF issues an Nudm\_UECM\_Get request to find the Source SMF from UDM providing NF type, UE ID, S-NSSAI, DNN. The UDM finds the serving SMF for the UE as described in TS 23.502 [3], and responds the SMF ID over Nudm\_UECM\_Get service response to the consumer NF. +2. The consumer NF subscribes for event notification for UPF/SMF relocation for the relevant PDU Session from the Source SMF via Nsmf\_EventExposure\_Subscribe service operation. +3. The Source SMF decides for UPF relocation for the relevant PDU Session. +4. The Source SMF notifies the consumer NF regarding UPF ID of the Target UPF. +If the PDU Session is released, the SMF notifies the consumer NF that implicitly indicates the release of the consumer subscription onto the SMF. +In Case 1: in case of SMF change, step 5-7 are executed. +In Case 2: in case of SMF change, step 8-10 are executed. +5. The consumer NF unsubscribe for event notification for UPF/SMF relocation for the relevant PDU Session from the Source SMF. +6. The consumer NF finds the Target SMF for the UE providing UE ID. There are two ways. The consumer NF may find the Target SMF by using the same way as described in step 1. Alternatively, the consumer NF may find + +the BSF by using the IP address, and then issues Nbsf\_Management\_Discovery to find the PCF(s) selected for the PDU Session identified by the tuple (UE IP address, SUPI, GPSI, DNN, S-NSSAI). + +7. The consumer NF subscribes for event notification for UPF/SMF relocation for the relevant PDU Session from the Target SMF via Nsmf\_EventExposure\_Subscribe service operation. +8. The consumer NF unsubscribe the event exposure subscription from the Source UPF. +9. The consumer NF subscribe to Target UPF for event exposure service. +10. The target UPF notifies regarding the subscribed events. + +#### 6.22.3.2 The consumer NF subscribes UPF change notification from the BSF by storing UPF ID and UE IP address in the BSF in PDU Session Establishment procedure + +![Sequence diagram showing the interaction between SMF, PCF, and BSF during PDU Session Establishment. The SMF sends an Npcf_SMPolicyControl_Update message to the PCF, which then sends an Nbsf_Management_Register message to the BSF.](64544fbada794f3cdf4f78f5d83613e4_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant PCF + participant BSF + Note over SMF, PCF, BSF: 0. PDU Session Establishment + SMF->>PCF: 1. Npcf_SMPolicyControl_Update (UE IP address, UPF ID) + PCF->>BSF: 2. Nbsf_Management_Register (UE IP address, UPF ID) + +``` + +Sequence diagram showing the interaction between SMF, PCF, and BSF during PDU Session Establishment. The SMF sends an Npcf\_SMPolicyControl\_Update message to the PCF, which then sends an Nbsf\_Management\_Register message to the BSF. + +Figure 6.22.3.2-1: Store UPF ID and UE IP address in BSF + +0. The UE establishes a PDU Session as defined in clause 4.3.2.2.1 of TS 23.502 [3]. +1. During the PDU Session establishment procedure, the SMF sends Npcf\_SMPolicyControl\_Update Request message (with the list of UE IP address and UPF ID) to PCF. +2. The PCF sends Nbsf\_Management\_Register Request message to the BSF to store the list of UE IP address and UPF ID in the BSF. + +![Sequence diagram showing the interaction between Consumer NF, BSF, and UPF. The Consumer NF sends an Nbsf_Management_Subscribe_Request to the BSF, which responds with Nbsf_Management_Notify_Response. The Consumer NF then sends a Nupf_EventExposure_Subscribe to the UPF, which responds with Nupf_EventExposure_Notify.](f4b570ddd089f54943d46e9f8776f9f9_img.jpg) + +``` + +sequenceDiagram + participant Consumer NF + participant BSF + participant UPF + Consumer NF->>BSF: 1. Nbsf_Management_Subscribe_Request + BSF->>Consumer NF: 2. Nbsf_Management_Notify_Response + Consumer NF->>UPF: 3. Nupf_EventExposure_Subscribe + UPF->>Consumer NF: 4. Nupf_EventExposure_Notify + +``` + +Sequence diagram showing the interaction between Consumer NF, BSF, and UPF. The Consumer NF sends an Nbsf\_Management\_Subscribe\_Request to the BSF, which responds with Nbsf\_Management\_Notify\_Response. The Consumer NF then sends a Nupf\_EventExposure\_Subscribe to the UPF, which responds with Nupf\_EventExposure\_Notify. + +Figure 6.22.3.2-2: Consumer NF subscribes UPF information notification from the BSF + +1. The consumer NF (e.g. AF/NEF) invokes Nbsf\_Management\_Subscribe Request to obtain the UPF ID providing the UE IP address, S-NSSAI, DNN. +2. The BSF responds the UPF ID(s) to consumer NF via the Nbsf\_Management\_Notify Response message. + +3. The consumer NF sends Nupf\_EventExposure\_Subscribe to relevant UPF(s) received in step 2 for event exposure service. +4. The UPF notifies regarding the subscribed events. + +### 6.22.4 Impacts on services, entities and interfaces + +SMF: + +- Nsmf Event Exposure Subscription needs to be enhanced to support exposing the UPF ID that matches a PDU session. + +BSF: + +- Discovery of several UPFs that accords with the parameters that related to the UEs. +- Expose UPF ID to the consumer NF. + +# --- 7 Overall Evaluation + +## 7.1 Overall Evaluation of solutions for Key Issue #1 + +For KI#1: + +- How to support UPF event exposure service(s) registration/deregistration on NRF, and what parameters to be registered in the NF profile of UPF. +- How to support UPF service discovery via the NRF, and what parameters that can be used for discovery. + +Solution #1 (clauses 6.1.2.1-6.1.2.4) can be seen as the basis to solve these aspects of KI#1. It is also considered and enhanced by Solution #12, Solution #20 and Solution #1 (clause 6.1.2.5.3) further. + +Solution #12 proposes direct subscription and indirect subscription for NWDAF collecting data from UPF. The impact of Solution #12 on KI #1 is that it proposes to include direct indication and/or indirect indication in UPF NF profile when UPF registers to NRF. + +Solution #20 proposes that an UPF supporting NAT functionality may register Public IP address pool information per IP Domain in NRF. The Public IP address pool information may be on per DNN and S-NSSAI basis. + +For KI#1: + +- How to support UPF selection for a UPF event exposure service request targeting a specific UE or a specific PDU session. + +Solution #1 (clauses 6.1.2.5.1 and 6.1.2.5.2) can also be considered to solve that aspect of KI#1: + +- It can be used for UPF selection with information of UE IP address, as described in clause 6.1.2.5.1. +- It can be used for UPF selection with information of SUPI, S-NSSAI and DNN, as in clause 6.1.2.5.2. +- It can be used also for UPF selection with information of UE IP address, by first applying existing functionality for IP address translation into SUPI using BSF service. +- It can be used for UPF selection with information of Group Identifier by first applying existing functionality for Group Identifier translation into SUPI list using UDM service. + +By specifying in normative phase the enhancements proposed in clause 6.1.2.1-6.1.2.5 from solution #1, clause 6.12.3.2 from solution #12, and clause 6.20.3.1 from solution #20, the following issues from KI#1 are covered: + +- How to support UPF event exposure service(s) registration/deregistration on NRF, and what parameters to be registered in the NF profile of UPF. +- How to support UPF service discovery via the NRF, and what parameters that can be used for discovery. + +The following issue from KI#1 is not covered: + +- How to support UPF selection for a UPF event exposure service request targeting a specific UE or a specific PDU session. + +### **UPF discovery for data collection** + +For UPF event exposure the UPF discovery is the necessary step to be considered. The UPF discovery can be categorized as following option: + +- Option 1: NRF based discovery (sol#1). The UPF registered its NF profile to the NRF. The NF consumer query the NRF, per the related query information, the NRF return the related UPF meet the query request. +- Option 2: SMF based discovery. There are further two option: + - Option 2.1: Only SMF is discovered (Sol#8/9/10). NF consumer get the serving SMF of the UE from the UDM per SUPI, which may require getting SUPI from IP address first (via BSF) or using IP address (via BSF) (Sol#1, 6.1.2.5.1-1). After that, the data collection from NF consumer is subscribed to the SMF only and SMF help to identify the related UPF. + - Option 2.2: the UPF is discovered via the assistance from SMF (Sol#1/2/7/11). NF consumer get the serving SMF for the UE from the UDM. Then it obtains the UPF information from the serving SMF. This option requires the SMF event exposure function enhancement to return a list of the UPF ID. +- Option 3: UDM/BSF based discovery (Sol#5/15). NF directly obtains the UPF information of the UE from the UDM (or BSF) if the serving SMF has registered the UPF information for the UE into the UDM (or BSF via the PCF). This option requires the SMF/UDM (or SMF/PCF/BSF) enhancement to register the UPF ID to the UDM (or BSF) and UDM (or BSF) send the required UPF ID to the NF consumer. + +Option 2 and Option 3 target for the same case, i.e. the data collection is related to a specific UE or QoS flow. + +For option 1, the NF profile of UPF can be used for discovery directly. This is suitable for the UPF direct subscription, e.g. UPF load analytics. + +For option 2, option 2.2 need enhancement on the SMF. The SMF need not only expose the UPF ID but also the UPF role. In case of the UPF change, the SMF also need notify the UPF change to the NF consumer, i.e. the SMF need maintain an additional UPF information subscription context. Option 2.1 only the SMF is to be discovered. The data collection can be subscribed via the SMF. If there are UPF role change or UPF reallocation, it can be handled by the SMF directly and not need notify the NF consumer. + +For option 3, it needs SMF register the related information to the UDM or BSF (via PCF). Also for each UPF role, e.g. PSA, I-UPF, the information need be registered to the UDM or BSF. Hence if the UPF role change or reallocation, the SMF also need update the related information at the UDM or BSF. + +Option 2.1 is suitable for UPF event exposure service indirect subscription as it does not require the SMF enhancement. And also the UPF role exposure and change notification can be avoided. + +## **7.2 Evaluation for KI#2** + +There are 21 candidate solutions proposed to address key issue#2, i.e. except solution#1, from solution#2 to #22. These 21 solutions can be group as follows: + +- Group 1: How the UPF expose the data to the TSN AF/TSCTSF. The related solution is sol#2. +- Group 2: How the UPF expose the data to NWDAF. The related solution is sol#7, 8, 9,10,11,12. +- Group 3: How the UPF expose the data to NEF/AF. The related solution is sol#15, 18, 19, 20. +- Group 4: Generic issue related to UPF data collection. The related solution is sol#3,4,5,6,13,14,16,17, 21, 22. + +### **UPF Data collection to TSN AF/TSCTSF** + +Solution#2 describes how TSN AF or TSCTSF collect the UPF/NW-TT PMIC/UMIC information via the UPF event exposure service. Currently this bridge information is encapsulated within containers and sent by UPF to SMF over N4. And only NW-TT in UPF, TSN AF and TSCTSF are requested to understand the information in those containers. + +With this proposal, the additional 'indication of UPF Direct Report' is introduced for the UPF event exposure service in the case that the operation code is 'subscribe-notify for parameter' or 'unsubscribe for parameter'. The NW-TT/UPF notification is unrelated to the other operation code defined in the container as described in TS 24.519 [11]. If enhanced with the addition of the indication of event notification, N7 and N4 can convey to UPF notification target information for direct report by UPF. + +Solution#2 optimizes only part of the information reported by the NW-TT/UPF depending on the request from TSN AF or TSCTSF. Optimizing notifications is more important than optimizing subscriptions due to the frequent UPF notifications. UPEAS enables a reduction in the signalling path for UPF reporting in the case of (un)subscribe operation code from TSN AF or TSCTSF and UPEAS does not cover the exchange of TSC information between DS-TT in UE and TSN AF or TSCTSF. + +**Proposal 1:** The UPF directly reports for transferring TSC management Information depending on the request from TSN AF/TSCTSF. + +### UPF Data collection to NWDAF + +For Group 2 solution, the data collection can be categorized into two types: + +- Direct subscription from UPF (sol#7, 11, 12), i.e. NWDAF directly subscribes the UPF data from the UPF. +- Indirect subscription via SMF (sol#8, 9, 10, 12), i.e. NWDAF firstly subscribes the UPF data from the SMF, then SMF transfer the subscription information to the UPF. There one different on which message should be used between the SMF and UPF, N4 procedure? Or Nupf\_EventExposure\_Subscribe service operation? + +Solution 9 propose SMF use Nupf\_EventExposure\_Subscribe for event subscription. Solution 8/10/12 propose SMF use the N4 procedure for event subscription. Using the SBA based API for subscription allows to benefit from SBA advantages / features (defined now and in the future) and avoids un-necessary protocol translations. Using PFCP for some events allows reusing N4 IEs defined for the purpose. + +For the data collection for single UE case, as it always need search the related SMF first. If we want to terminate the subscription at the UPF, a new UPF discovery mechanism is to be defined, e.g. enhance the SMF event exposure service. However if the subscription is terminated at the SMF, no enhancement is expected. Hence in this case the UPF data collection subscription is more suitable to be terminated at the SMF. + +**Proposal 2:** For the data collection related to single UE case, the UPF data collection subscription is preferred to be terminated at the SMF. + +**Proposal 3:** void. + +### UPF Data collection to the NEF/AF + +For Group 3 solution, all solution is related to the data collection related to one flow within one PDU session. The solution can be summarized as below: + +- Solution#15 describes how the direct subscription can be done via the BSF. It is unclear how the related flow information which need measurement is triggered? +- Solution#18 describes how the QoS parameter information at the UPF can be exposed to the AF to find a way with lower latency and higher flexibility. The QoS parameters requested to be exposed by UPF are provision information that are configured in the UPF by 5GC for packet processing and can be identified by AF. This information is provisioned by the UPF without other operations by the SMF or AN. +- Solution#19 describes how NEF do the subsequent subscription to the same QoS flow and how to use the direct UPF subscription to do the data collection from QoS Monitoring. + +For the AF do the subscription to the same QoS flow, AF is allocated Transaction Reference ID during the QoS monitoring initial request to identify service data flow. Subsequent request is used for updating current subscription with the same Transaction Reference ID. Local NEF can identify the request is for the same service data and invoke Nupf\_EventExposure\_Subscribe service operation directly. + +For the direct subscription to the UPF and UPF trigger the SMF action, it is unsuitable to trigger the UPF subscription directly. Normally this monitoring subscription is combined with the PCC rule and notified to the SMF. By doing that, the SMF can trigger the related action, e.g. PDU session modification. The input for the + +activate measurement also need consider the policy control from the PCF. So why not do the subscription via the SMF considering the UPF discovery may also need go via the SMF? + +- Solution #20 describes how the UE IP address mapping information can be exposed by UPF so that the AF can know the UE private IP address which is internally used in 5GC. This is for the case that the UPF supports the NAT. + +**Proposal 3:** For the data collection which need some action besides UPF, e.g. QoS flow characteristics measurement, the subscription should be terminated at the SMF. + +### Generic issue related to UPF data collection + +For Group 4 solution, the solution is not bound to one specific type NF consumer. It can be considered in all UPF data collection case. The solution can be summarized as follows: + +- Solution#3 give some generic guidance on whether the UPF data collection should be the direct subscription or indirect subscription. It can be considered when the NF consumer do the UPF event subscription and not need be concluded individually. +- Solution#4 describe that N4 interface need be enhanced to pass the related event filtering information to the UPF. It can be part of the data collection procedure. +- Solution#5/#6 describe how to find the related UPF via the SUPI or IP address. It is more related to KI#1. +- Solution#13 describe how the UPF event subscription can be updated if the UPF is changed. It may be more suitable to consider this procedure in the related context. For example if the UL-CL is released, no target UPF, how to consider this UPF subscription change case? +- Solution#14 describe how to avoid performance impact due to the UPF data collection. Similar consideration is also considered at the Solution#11 and Solution#21. There are at least two mechanisms can be considered, i.e. the NF consumer indicates the Reporting suggestion information in the Event subscription procedure and per Reporting suggestion information UPF can concatenate several notification message to the same notification endpoint in one notification message. + +By doing so it can greatly reduce number of the event reporting message and avoid the impact at the peak time especially avoiding event exposure impact to the normal UPF data packet transfer handling. This also give some flexibility to the UPF on when to report the collected data to NF consumer. + +- Solution#16 describe that when the UPF receives the event subscription it may notify to the SMF to verify whether the subscription is allowed or not. If the intention of this procedure is for service operation authorization, it can be done as part of the service operation discovery, which is defined by SA3 WG. +- Solution 17 describe two case, i.e. the update/release directly to UPF or update/release indirectly via the SMF. For the update/release directly, similar issue about the authorization process via SMF/PCF. +- Solution#21 describes whether the UPF event exposure is used or not at any time by taking a consideration on the UPF performance. By muting and resuming the UPF reporting based on the threshold of UPF performance configured from operator policy, it may be helpful to manage efficiently the UPF event exposure, and give the operator the flexibility of network deployments and managements. However due to the reporting is uncertain, it is unclear on its benefit of this type of reporting. +- Solution #22 describes how to support the updating of target UPF for UPF event exposure service subscription in case of UPF change during the life time of the PDU Session. + +**Proposal 4:** To reduce the event exposure impact to the UPF, it is suggested to introduce the Reporting suggestion information in the Event subscription procedure and per Reporting suggestion information UPF can concatenate several notification message to the same notification endpoint in one notification message. + +# 8 Conclusions + +## 8.1 Conclusions for Key Issue #1 + +UPF(s) register their Event Exposure service(s), supported event ID(s) onto NRF. Procedures defined in the present TR, clauses 6.1.2.1 to 6.1.2.4 are endorsed as a baseline for normative specifications. + +The conclusion for the not covered issue in KI#1 will be concluded as part of KI#2. + +To collect the data from the related UPF, the related UPF(s) need be discovered. It is done as following: + +- Option 1: NRF based discovery. The UPF registered its NF profile to the NRF. The NF consumer query the NRF, per the related query information, the NRF return the UPF meet the query request. +- Option 2: SMF based discovery. The NF consumer gets the serving SMF of the UE from the UDM per SUPI. If UE IP address is known the NF consumer may need to first get the SUPI (via BSF). After that, the data collection from NF consumer is subscribed to the SMF only and SMF help to identify the related UPF. + +## 8.2 Conclusions for KI#2 + +The following interim conclusions are proposed for KI#2: + +1. Subscription to UPF events via SMF is the rule except for the cases listed in bullet 2; Subscription via SMF means the final consumer of UPF event notifications sends the subscription request to the SMF and then the SMF is doing a third-party subscription onto UPF on behalf of this final consumer. Conversely the notifications are directly sent by the UPF to the final consumer of UPF notifications. + +NOTE 1: Optimizing notifications is more important than optimizing subscriptions. + +NOTE 2: Subscriptions related with AoI are handled by SMF that subscribe/unsubscribe to the relevant UPF(s) on behalf of the final consumer based on whether the UE is in the target AoI (for example, the SMF can first get the UE list within the AoI and keep being updated about the UE list by subscribing to AMF, and then subscribe/unsubscribe to the relevant UPF(s) on behalf of the final consumer). This allows the UPF not having to determine the AMF where to subscribe for UE presence in the AoI. + +NOTE 3: For event subscriptions requiring interactions with 5G AN, a solution where the UPF event consumer would directly subscribe to UPF and then UPF would ask SMF to send N2 SM signalling to 5G AN would be more complex and not bring advantage. + +2. Direct subscription to UPF (i.e. not requiring third party subscription to UPF via SMF) shall be possible for data collection where UPF is the source as defined in TS 23.288 [5], i.e. the following cases: + +A. TS 23.288 [5] Table 6.5.2-2: Data collected by NWDAF for UPF load analytics recalled in item 2 of Annex A of the TR. + +B. For analytics targeting "any UE" (possibly for specific DNN and or slices) and not related with an AoI or BSSID/SSID or with a specific data flow. + +NOTE 4: This can relate to use cases such as Data collected by NWDAF for UPF load analytics, User Data Congestion Analytics, Data Volume dispersion analytics, WLAN performance analytics. + +C. The case described in solution 20 (UE IP address mapping information exposure by UPF) where the 5GC NF (e.g., NEF, BSF) can directly discover the UPF that performs NAT (based on the NATed IP address) and then invoke directly the NAT related API at the UPF. This is an optional feature. + +Normative work will be based on NEF contacting NRF and UPF before invoking BSF. + +NOTE 5: Which 5GC NF can directly discover the UPF and invoke the NAT related API will be confirmed during normative phase. + +3. In Rel18: + +- A. the only defined consumers of UPF event SUBSCRIBE are SMF, and NWDAF. + - B. the only defined consumers of UPF event notifications are AF/NEF, TSNAF/TSCTSF and NWDAF. +4. UPF event exposure Service description: This service provides events related to PDU Sessions towards consumer NF. The service operations exposed by this service allow other NFs to subscribe and get notified of events happening on UPFs. + +The following events may be subscribed by a NF consumer: + +- Event: QoS monitoring. This event provides QoS Flow level performance information (information listed in Solution #8, clause 6.8.2). +- Event: UserDataUsageMeasures. This event provides information of user data usage of the User PDU Session (information listed in Solution #7, clause 6.7.2). +- Event: UserDataUsageTrends. This event provides statistical measurements (information listed in Solution #7, clause 6.7.2). + +When the UPF provides notifications related to UserDataUsageMeasures or UserDataUsageTrends events the notifications may indicate the time stamps for the measures and also refer to the Application Id or Packet Filter Set indicated in the consumer subscription. + +5. The subscription mechanisms for the defined UPF event exposure events are as follows: +- Event: QoS monitoring. Subscription is always indirect via SMF. UPF and SMF interact using PFCP. + - Event: UserDataUsageMeasures. SBI based subscription operation shall be used by SMF and other allowed direct consumers. + - Event: UserDataUsageTrends. SBI based subscription operation shall be used by SMF and other allowed direct consumers. +6. To determine which SMF to contact the final consumer of UPF events proceeds as follows: +- If the event targets any UE, the final consumer of UPF events looks up the NRF to discover all suitable SMF(s) (e.g. SMF(s) that serve the target combination of DNN and S-NSSAI). + - If the event targets a unique UE identified by its SUPI, the final consumer of UPF events sends Nudm\_UECM\_Get\_Request (SUPI, type of requested information set to SMF Registration Info and the S-NSSAI and DNN) to UDM to get the SMF ID serving the target UE. + - If the event target are UEs identified by a Group Identifier, the final consumer of UPF events sends Nudm\_SDM\_Get\_Request to UDM and requests the list of SUPIs that correspond to the Group ID. Final consumer then proceeds with these SUPIs as described above to get SMF ID serving each UE identified by one of received SUPIs. + +If the consumer of NWDAF service doesn't provide the target DNN, S-NSSAI (these parameters are optional for NWDAF service defined in TS 23.288 [5]), and the event targets a unique UE identified by its SUPI, the NWDAF gets the list of all PDU Session for that SUPI via Nudm\_UECM\_Get\_Request and then determine which (DNN, S-NSSAI) it will consider. + +If the consumer of NWDAF service doesn't provide the target DNN, S-NSSAI (these parameters are optional for NWDAF service defined in TS 23.288 [5]), but provides the application server IP address/FQDN, and the event targets a unique UE identified by its SUPI or any UE, the NWDAF may: + +- The NWDAF uses application server IP address/FQDN to obtain the corresponding DNAI from NEF/UDR. The NEF/UDR uses a mapping table between application server IP address/FQDN and DNAI. The procedure is described in clause 8.7 conclusion of TR 23.700-48 [10]. The DNAI is used to reduce the scope of related SMF/UPF and focus on the UE that access the application server IP address/FQDN locally via the indicated DNAI. +- (when the NWDAF request targets a single UE) get from UDM related all SMF(s) that serve the target UE by providing the SUPI, then check which of these SMF(s) supports the target DNAI and then send to each of these SMF the request to subscribe to the UPF event related with the application server IP address/FQDN and DNAI. + +- (when the NWDAF request targets Any UE) use the DNAI to query the NRF on discovery of all SMF(s) that support this DNAI and then send to each of them the request to subscribe to the UPF event related with the application server IP address/FQDN. +7. For the UPF data collection, the event subscription includes Reporting suggestion information as described in Sol#14, which is used to assist the UPF event notification. Per Reporting suggestion information UPF can concatenate several notification messages to the same notification endpoint in one notification message. + +# Annex A: Analysis on the NWDAF requirements of UPF event exposure service(s) + +This Annex aims at listing and analysing the NWDAF requirements of UPF event exposure service(s). + +NOTE 1: This clause recalls for information the main known usage of UPF information exposure in 5GC as defined in other 3GPP documents. If this clause and the quoted other 3GPP documents are not aligned, the quoted other 3GPP documents prevails. + +NWDAF requirements as defined in TS 23.288 [5], for instance (the list is not exhaustive), contain: + +1. Observed Service Experience: TS 23.288 [5] of Table 6.4.2-2 of: QoS flow level Network Data from 5GC NF related to the QoS profile assigned for a particular service (identified by an Application Id or IP filter information). + +The Observed Service Experience analytics may provide Service Experience for an Edge Application over a UP path: Service experience for a UE or a group UEs or any UE in an Application or a set of Applications over a specific UP path (UPF, DNAI and EC server). + +The Observed Service Experience analytics may also provide "Service experience for a UE or a group of UEs in an Application or a set of Applications over a RAT Type or over a Frequency or both" as defined in Table 6.4.1-1 of TS 23.288 [5]. + +**Table 6.4.2-2 (TS 23.288 [5]): QoS flow level Network Data from 5GC NF related to the QoS profile assigned for a particular service (identified by an Application Id or IP filter information)** + +| | | | +|-----------------------|-----|----------------------------------------------------------------------------------------------------| +| QoS flow Bit Rate | UPF | The observed bit rate for UL direction; and
The observed bit rate for DL direction. | +| QoS flow Packet Delay | UPF | The observed Packet delay for UL direction; and
The observed Packet delay for the DL direction. | +| Packet transmission | UPF | The observed number of packet transmission. | + +For NWDAF to provide Service Experience for an Application: Consumer NF sends an Analytics request/subscribe (Analytics ID = Service Experience, Target of Analytics Reporting = any UE or a UE identified by a SUPI or a group of UEs identified by a Group Id, Analytics Filter Information = (Application ID, S-NSSAI, DNN, Application Server Address(es), Area of Interest), Analytics Reporting Information=Analytics target period) to NWDAF. + +2. Table 6.5.2-2 of TS 23.288 [5]: Data collected by NWDAF for UPF load analytics. + +**Table 6.5.2-2 (TS 23.288 [5]): Data collected by NWDAF for UPF load analytics** + +| Information | Source | Description | +|----------------------|--------|-----------------------------------------| +| Traffic usage report | UPF | Report of user plane traffic in the UPF | + +UPF should report all traffic for all N4 (PDU) sessions that meet some criteria (S-NSSAI, Area of interest) -> SMF involvement may be considered when it is needed to determine which UPF(s) serve a UE in the area of interest. + +- Table 6.7.3.2-1 of TS 23.288 [5]: Service Data from 5GC related to UE communication. + +**Table 6.7.3.2-1 (TS 23.288 [5]): Service Data from 5GC related to UE communication** + +| UE communication (1..max) | UPF, AF | Communication description per application | +|-----------------------------|----------|-----------------------------------------------| +| >Communication start | | The time stamp that this communication starts | +| >Communication stop | | The time stamp that this communication stops | +| >UL data rate | | UL data rate of this communication | +| >DL data rate | | DL data rate of this communication | +| >Traffic volume | | Traffic volume of this communication | +| > N4 Session ID | SMF, UPF | Identification of N4 Session. | +| > Inactivity detection time | SMF, UPF | Value of session inactivity timer. | + +5GC Consumer NF sends a request to the NWDAF for analytics on UE(s), where the analytics type indicated by "Analytics ID" is set to "UE communication". The Target of Analytics Reporting is set to SUPI or an Internal Group Identifier and Analytics Filter may include Application ID and Area of Interest. + +3. Table 6.8.2-2 of TS 23.288 [5]: Data Collected from the UPF or from the AF related to User Data Congestion Analytics. + +**Table 6.8.2-2 (TS 23.288 [5]): Data Collected from the UPF or from the AF related to User Data Congestion Analytics** + +| Information | Source | Description | +|-------------------------|-----------|-------------------------------------------------------------------------------| +| Application ID | UPF or AF | Application identifier as defined in TS 23.501 [2] clause 5.8.2 (see NOTE 1). | +| IP Packet Filter Set | UPF or AF | IP Packet Filter set as defined in TS 23.501 [2] clause 5.8.2 (see NOTE 1). | +| Measurement period | UPF or AF | Measurement period. | +| Throughput UL/DL | UPF or AF | Average Throughput UL/DL over the measurement period. | +| Throughput UL/DL (peak) | UPF or AF | Peak Throughput UL/DL over the measurement period. | +| Timestamp | UPF or AF | Time when measurements are taken. | +| Achieved sampling ratio | UPF | Sampling ratio achieved by UPF (see NOTE 2). | + +NOTE 1: Application Id and IP Packet Filter Set are mutually exclusive. +NOTE 2: UPF may apply data sampling to reduce the load on the UPF. This parameter is provided when no sampling ratio is configured at the UPF or the UPF could not fulfil the configured sampling ratio. +NOTE 3: Multiple outputs are provided by the UPF when multiple Service Data Flows are running at the UPF for the same UE and measurement period. +NOTE 4: How NWDAF collects information from UPF is not defined in this Release of the specification. + +The Consumer NF indicates a request for analytics for congestion in a specific location. The Analytics ID is set to "User Data Congestion" for transfer over user plane, control plane, or both, the Target of Analytics Reporting is set to "any UE" and Analytics Filter Information set to include a location (e.g. ECGI, TA) and an indication to provide the list of applications that contribute the most to the traffic. + +4. Table 6.10.2-5 of TS 23.288 [5]: UE data volume dispersion collected from serving UPF. + +**Table 6.10.2-5 (TS 23.288 [5]): UE data volume dispersion collected from serving UPF** + +| Information | Source | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------| +| UE IP address | UPF | UE IP address. | +| Timestamp | UPF | Time stamp of the collected information. | +| Data Volume UL/DL | UPF | Sum of UE data volume exchanged per UE across all applications. | +| NOTE: The Data volume can be reported either as total volume of the PDU session or periodically. It refers to the Data volume exchanged between the start and stop of the PDU session. When reported periodically, the period can be specified in the requested analytic target period or configured as a default value in the UPF. | | | + +**Table 6.10.2-6: UE data volume dispersion collected from serving UPF** + +| Information | Source | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------| +| UE IP address | UPF | UE IP address. | +| Timestamp | UPF | A timestamp of the collected information. | +| Application ID | UPF | Identify the application at the UPF | +| IP 5-tuple | UPF | IP 5-tuple. | +| Location of Application | UPF | List of Internet applications represented by DNAI(s). | +| Data Volume UL/DL | UPF | Sum of UE data volume exchanged per application during the period. | +| Application duration | UPF | Duration for the application (e.g. Voice talk time). | +| NOTE 1: Application ID and IP 5-tuple are mutually exclusive.
NOTE 2: Multiple outputs are provided by the UPF when multiple applications are running at the UPF for the same UE and time period.
NOTE 3: The Data volume can be reported either as total volume of the PDU session or periodically. It refers to the Data volume exchanged between the start and stop of the PDU session. When reported periodically, the period can be specified in the requested analytic target period or configured as a default value in the UPF. | | | + +In table 6.10.2-5, the data volume is collected per UE from the UPF. The collected UE information is applicable across all applications used by the UE between start and stop of the PDU session. The UPF reports volume per UE IP address across all applications. + +In table 6.10.2-6, the UPF reports data volume per UE for specific application(s) in relation to the start and stop of the application as indicated by the application duration. + +The Consumer NF sends a request to the NWDAF for dispersion analytics on a specific UE, any UE, or a group of UEs, using either the Nnwdaf\_AnalyticsInfo or Nnwdaf\_AnalyticsSubscription service. The Analytics ID is set to "UE Dispersion Analytics", the Dispersion Analytic (DA) type is set to "Data Volume Dispersion Analytics" (DVDA) or "Transactions Dispersion Analytics" (TDA) and Analytic Filter Information = (Area of Interest, slice, target period, optional UE class: Top-Heavy, Fixed, or Camper UEs). The NF or AF provides the UE ID or Internal Group ID in the Target of Analytics Reporting. + +## 5. Clause 6.11.1 of TS 23.288 [5] on "WLAN performance analytics" requests: + +Target of Analytics Reporting: a single UE (SUPI), a group of UEs (an Internal Group ID), or any UE. + +Analytics Filter Information: + +- Area of Interest (list of TA or Cells); + +NOTE 2: Even though the Area of Interest may have been meant to indicate a UE location, it is questionable to use this information considering UE(s) that are IDLE over 3GPP access and thus whose 3GPP location cannot be determined. UPEAS is not meant to have UE impact. + +- SSID(s); +- BSSID(s); and + +The reporting should only apply for traffic exchanged on a target SSID and BSSID thus the UPF reporting should only be reported for target UE(s) exchanging traffic on a target SSID and BSSID or the UPF should be aware of the target SSID/BSSID. + +| | | | +|----------------------------|-----|-----------------------------------------------------| +| UE communications (1..max) | UPF | List of communication time slots | +| > Communication start | | The time stamp that PDU session(s) for WLAN starts. | +| > Communication stop | | The time stamp that PDU session(s) for WLAN ends. | +| > UL data rate | | UL data rate of PDU session(s) for WLAN. | +| > DL data rate | | DL data rate of PDU session(s) for WLAN. | +| > Traffic volume | | Traffic volume of PDU session(s) for WLAN. | + +## 6. Clause 6.14.1 of TS 23.288 [5] "User plane performance analytics" requests: + +- User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific serving anchor UPF. +- User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific DNAI. +- User plane performance analytics for a specific Edge Computing application for a UE, group of UEs, or any UE over a specific Edge Application Server Instance. + +Analytics consumer sends an Analytics request/subscribe (Analytics ID = DN Performance Target of Analytics Reporting, Analytics Filter Information = (Application ID, S-NSSAI, DNN, Area of Interest, UPF anchor ID, DNAI, Application Server Address(es)), Analytics Reporting Information = Analytics target period) to NWDAF by invoking a Nnwdaf\_AnalyticsInfo\_Request or a Nnwdaf\_AnalyticsSubscription\_Subscribe service. + +Some of these analytics target Any UE (possibly for specific DNN and or slices) and the NWDAF acting as a consumer of UPF exposure may target any UPF that serves the corresponding specific DNN and or slices. + +Some of these analytics target a specific UE and it is thus needed for the NWDAF subscription to be forwarded to the UPF(s) that serve the target PDU sessions of this UE. + +# Annex B: Change history + +| Change history | | | | | | | | +|----------------|------------|------------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2022-02 | SA2#149E | S2-2200094 | - | - | - | Proposed skeleton agreed at S2#149E | 0.0.0 | +| 2022-02 | SA2#149E | - | - | - | - | Documents approved p-CR at S2#149E, including S2-2200095, S2-2201822, S2-2201823, S2-2201824, S2-2201825, S2-2201826 | 0.1.0 | +| 2022-04 | SA2#150E | - | - | - | - | Documents approved p-CR at S2#150E, including S2-2202758, S2-2203581, S2-2203582, S2-2203583, S2-2202652, S2-2203584, S2-2203585, S2-2203586, S2-2203587, S2-2203588 | 0.2.0 | +| 2022-05 | SA2#151E | - | - | - | - | Documents approved p-CR at S2#151E, including S2-2204311, S2-2204515, S2-2205320, S2-2204880, S2-2204881, S2-2204882, S2-2204883, S2-2204884, S2-2204885, S2-2204886, S2-2204887, S2-2204888, S2-2204520, S2-2204889, S2-2204890, S2-2204891, S2-2203748, S2-2204892, S2-2204893, S2-2204894 | 0.3.0 | +| 2022-08 | SA2#152E | - | - | - | - | Documents approved p-CR at S2#152E, including S2-2205868, S2-2205885, S2-2206149, S2-2206309, S2-2206324, S2-2206731, S2-2207188, S2-2207189, S2-2207190, S2-2207191, S2-2207192, S2-2207193, S2-2207194, S2-2207195, S2-2207196, S2-2207197 | 0.4.0 | +| 2022-09 | SA#97-e | SP-220827 | - | - | - | MCC editorial update for presentation to TSG SA for information | 1.0.0 | +| 2022-10 | SA2#153E | | | | | Documents approved p-CR at S2#153E, including S2-2208635, S2-2209928, S2-2209929, S2-2209930, S2-2209942, S2-2209954 | 1.1.0 | +| 2022-11 | SA#98-e | SP-221112 | - | - | - | MCC editorial update for presentation to TSG SA for approval | 2.0.0 | +| 2023-01 | SA2#154AHE | - | - | - | - | Documents approved p-CR at S2#154AHE, including S2-2301386 | 2.1.0 | +| 2023-03 | SA#99 | SP-230084 | - | - | - | MCC editorial update for presentation to TSG SA for approval (second submission) | 2.2.0 | +| 2023-03 | SP#99 | - | - | - | - | MCC Update for publication after TSG SA approval | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-64/raw.md b/raw/rel-18/23_series/23700-64/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..aae6df1c10e68e287320ff0688023b4870c8782a --- /dev/null +++ b/raw/rel-18/23_series/23700-64/raw.md @@ -0,0 +1,715 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancements to application layer support for V2X services; Phase 2; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'G' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +## --- **Keywords** + + + +## **3GPP** + +## --- **Postal address** + +### --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +## Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Key issues ..... | 7 | +| 4.1 Key issue #1 – Support for high risk VRU zones ..... | 7 | +| 4.2 Key issue #2 – Support for V2P communications ..... | 7 | +| 4.3 Key issue #3 – V2X service deployment in edge data network..... | 8 | +| 4.4 Key issue #4 – Enhancement to support non-simultaneous multiple service providers control for advanced V2X services ..... | 8 | +| 4.5 Key issue #5 – Usage of network analytics..... | 9 | +| 4.6 Key issue #6 – Enhanced network monitoring to support advanced V2X services..... | 9 | +| 5 Architectural requirements..... | 9 | +| 5.1 General requirements ..... | 9 | +| 5.2 VRU zone configuration requirements ..... | 9 | +| 5.2.1 Description ..... | 9 | +| 5.2.2 Requirements..... | 9 | +| 5.3 V2P communications requirements ..... | 10 | +| 5.3.1 Description ..... | 10 | +| 5.3.2 Requirements..... | 10 | +| 6 Solutions..... | 10 | +| 6.1 Solution #1 - VAE support for Energy Efficient V2P communications ..... | 10 | +| 6.1.1 Solution description..... | 10 | +| 6.1.1.1 General..... | 10 | +| 6.1.1.2 Procedures..... | 10 | +| 6.1.1.2.1 Procedure for VAE client enabled V2P communication schedule configuration ..... | 11 | +| 6.1.1.2.2 Procedure for VAE server enabled V2P communication schedule configuration ..... | 12 | +| 6.1.2 Solution evaluation..... | 13 | +| 6.2 Solution #2 - Support for VRU zone configuration and operation ..... | 13 | +| 6.2.1 Solution description..... | 13 | +| 6.2.1.1 Procedure on VAL server - triggered VRU zone creation..... | 13 | +| 6.2.2 Solution evaluation ..... | 15 | +| 6.3 Solution #3 - Deployment of V2X application layer with Edge Enabler Layer ..... | 15 | +| 6.3.1 Solution description..... | 15 | +| 6.3.2 Solution evaluation..... | 16 | +| 6.4 Solution #4 - UE initiated request for VRU zones..... | 16 | +| 6.4.1 Solution description..... | 16 | +| 6.4.1.1 General..... | 16 | +| 6.4.1.2 Procedure ..... | 17 | +| 6.5 Solution #5 - Enhanced network monitoring ..... | 18 | +| 6.5.1 Solution description..... | 18 | +| 6.5.1.1 General..... | 18 | +| 6.5.1.2 Enhancements to subscription procedure in clause 9.7.3 ..... | 19 | +| 6.5.1.3 Enhancements to notification procedure in clause 9.7.4 ..... | 19 | +| 6.5.2 Solution evaluation ..... | 19 | +| 6.6 Solution #6 – Network situation enhanced with analytics ..... | 19 | +| 6.6.1 Solution description..... | 19 | +| 6.6.1.1 General..... | 19 | +| 6.6.1.2 Enhancements to network monitoring by V2X UE ..... | 19 | +| 6.6.1.3 Enhancements to monitoring and control of QoS for eV2X communications ..... | 19 | +| 6.6.2 Solution evaluation..... | 19 | + +7 Overall evaluation..... 20 +7.1 General ..... 20 +7.2 Key issue and solution evaluation..... 20 +7.3 Overall evaluation of key issue#1 ..... 20 +7.4 Overall evaluation of key issue#2 ..... 21 +7.5 Overall evaluation of key issue#3 ..... 21 +7.6 Overall evaluation of key issue#4 ..... 21 +7.7 Overall evaluation of key issue#5 ..... 21 +7.8 Overall evaluation of key issue#6..... 21 +8 Conclusions..... 22 +**Annex A: Change history ..... 23** + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# 1 Scope + +The present document is a technical report which identifies the enhancements to the application architecture to support V2X services specified in 3GPP TS 23.286 [6] considering advanced V2X services like V2P, ToD, etc and edge computing deployments for V2X services. + +The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to advanced V2X services and edge computing in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3], 3GPP TS 23.285 [5], 3GPP TS 23.287 [7], 3GPP TS 23.548 [10] and 3GPP TS 23.558 [11]. + +The study also takes into consideration the V2X application specific services and recommendations specified by automotive industry bodies (5GAA, ETSI ITS and AECC) related to advanced V2X services for VRU, Haptics/ToD and edge deployments for V2X services. + +This document will provide recommendations for normative work. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.185: "Service requirements for V2X services; Stage 1". +- [3] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1". +- [4] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs". +- [5] 3GPP TS 23.285: "Architecture enhancements for V2X services". +- [6] 3GPP TS 23.286: "Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows". +- [7] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [8] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [9] 3GPP TS 23.436: "Procedures for Application Data Analytics Enablement Service". +- [10] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [11] 3GPP TS 23.558: "Architecture for enabling Edge Applications". +- [12] 3GPP TR 23.700-36: "Study on Application Data Analytics Enablement Service". +- [13] ETSI TS 103 300-2: "Intelligent Transport Systems (ITS); Vulnerable Road Users (VRU) awareness; Part 2: Functional Architecture and Requirements definition; Release 2". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +The terms and definitions as specified in 3GPP TS 23.286 [6] apply. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------|--------------------------------------------------| +| BSM | Basic Safety Message | +| CAM | Cooperative Awareness Message | +| CPM | Collective Perception Message | +| DENM | Decentralized Environmental Notification Message | +| V2P | Vehicle-to-Pedestrian | +| V2X | Vehicle-to-Everything | +| VAE | V2X Application Enabler | +| VAM | VRU awareness message | +| VASS | V2X Application Specific Server | +| VRU | Vulnerable Road Users | +| VRUP | Vulnerable Road User Protection | + +# 4 Key issues + +## 4.1 Key issue #1 – Support for high risk VRU zones + +In VRU high risk zones, drivers (or automated vehicles) are delivered warnings when they enter a high risk area where there is a likely presence of many VRUs. The high-risk area can be static (e.g. a school during arrival and leaving times), or dynamic (e.g. a school bus or mobile ice-cream vendor). Dedicated roadside infrastructure could play a vital role in disseminating warning messages to VRUs and vehicles as well. + +One issue at the scenario of the VRU high risk zone areas is how to configure the communication for the zones (which can include different types of interfaces and transmission modes) and how to translate the zone configurations (which are application driven) to network requirements and zone specific provisioning parameters considering both static and dynamic zones. Furthermore, another issue is how to assist the provisioning of zone specific parameters to the devices which can be potential VRUs and V2X-UEs and are expected to enter the zone. So, the key issue will study: + +- Whether and how to enhance VAE layer capabilities to support configuring the communication parameters for the zones. +- Whether and how to enhance VAE layer capabilities to translate the zone configurations to network requirements and zone specific provisioning parameters. +- Whether and how to assist the provisioning of zone specific parameters to the devices which can be potential VRUs and V2X-UEs. + +## 4.2 Key issue #2 – Support for V2P communications + +Vehicle to Pedestrian (V2P) is one of the V2X scenarios, which enables communication between vehicles and pedestrians for both safety and traffic efficiency related applications. One of the key V2P applications is the Vulnerable + +Road User Protection (VRUP) as specified in ETSI TS 103 300-2 [13]. VRUP provides warning to vehicles of the presence of vulnerable road users, e.g. pedestrian or cyclist, in case of dangerous situation. In VRUP, multiple V2X messages need to be exchanged between the pedestrian and the vehicular UEs, originating by one or more applications. Such messages can be standard VRU messages (e.g. VAM) and other V2X messages (CAM, DENM, BSM, CPM) and can be exchanged via different transmission modes (unicast, groupcast, broadcast). + +In such scenario, one challenge is that a pedestrian UE might have a lower battery capacity and limited radio capability, and therefore may have to work in a low power consumption mode, e.g. not being able to send/receive V2X messages with the same periodicity as a Vehicular UE. Continuous sending/receiving V2X messages by the pedestrian UE would affect UE power efficiency. A further challenge is that multiple applications related to VRU may be deployed, which may have differentiated traffic/QoS requirements as well as transmission/reception schedules. + +The VAE layer may provide support functionality for enabling V2P applications, by consolidating the V2P application requirements and aligning the communication traffic pattern with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles). + +So, the key issue will study: + +- Whether and how the VAE layer can support the V2P communications considering the UE situation (e.g. low battery power, weak radio signals)? +- Whether and how the VAE layer can coordinate the alignment of the communication traffic patterns with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles)? + +## 4.3 Key issue #3 – V2X service deployment in edge data network + +The distributed deployment models for VAE layer are specified in clause 7.2.2 of 3GPP TS 23.286 [6]. It is possible that both VAE server and V2X application specific servers are deployed in the edge data network. Several industry bodies like 5GAA and AECC have studied the deployments of V2X services in edge computing domain. + +The edge enabler architecture is specified in 3GPP TS 23.558 [11] which supports Edge Application Servers (EAS) deployed at EDN with enabler capabilities like Application Context Relocation. + +It is required to investigate the impact of edge deployments of V2X application architecture considering the Edge enabler architecture. The following open issues can be studied: + +- a. Whether and how V2X application architecture supports the edge enabler architecture specified in 3GPP TS 23.558 [11]. +- b. Investigate the the impact on V2X enabler services for edge deployments. + +## 4.4 Key issue #4 – Enhancement to support non-simultaneous multiple service providers control for advanced V2X services + +Some capabilities (e.g. session oriented services) are specified in 3GPP TS 23.286 [6] which supports advanced V2X services (e.g. ToD service) controlled by a V2X application specific server operated by a V2X service provider. It is possible that a host vehicle can be controlled by multiple V2X service providers in different regions. Example: A host vehicle may be controlled by V2X service provider X in normal driving zone region and by V2X service provider Y in remote parking zone region. The multiple service providers may be utilizing the VAE services to support their ToD services. It can be investigated whether and how VAE services (e.g. Session oriented services) can support non-simultaneous multiple V2X service provider control for advanced V2X services (e.g. ToD). + +The following open issues can be studied: + +- a. Whether and how V2X enabler services (e.g. session oriented services) can support non-simultaneous multiple V2X service provider control for advanced V2X services. + +## 4.5 Key issue #5 – Usage of network analytics + +Exposure capabilities for various network analytics information (e.g. DN performance analytics) is specified in 3GPP TS 23.288 [8] via NWDAF (at network layer) and 3GPP TR 23.700-36 [12] via SEAL ADAE service (at application layer). + +Some capabilities (e.g. session oriented services) are specified in 3GPP TS 23.286 [5] which supports ToD service controlled by a V2X application specific server operated by a V2X service provider. These services require very good and stable network performance for successful service operation. It is hence required to study how network analytics (e.g. performance information or performance predictions) can be used to enhance the VAE capabilities which support advanced V2X services. + +The following open issue can be studied: + +- a. Whether and how V2X enabler services (e.g. session oriented services, V2X message delivery) can be enhanced to utilize the network analytics services specified in 3GPP TS 23.288 [8] and 3GPP TS 23.436 [9]. + +## 4.6 Key issue #6 – Enhanced network monitoring to support advanced V2X services + +For advanced V2X scenarios the communication service situation is very important. The V2X UE should be able to choose the communication services (e.g. Uu or PC5) with another V2X UE or a group of V2X UEs considering the network situation towards the V2X UE(s) and/or the proximity of the V2X UEs within which the V2X UEs can communicate. + +In 3GPP TS 23.286 [6] clause 9.7, a V2X UE can subscribe for the network situation monitoring events in an area of interest. Once the V2X UE receives notification, it can further decide to switch between different modes of operations for V2X communications. However, it does not support network situation monitoring events for a specific V2X UE or a group of V2X UEs as required for advanced V2X applications (e.g. ToD, platooning). + +The open issue for the study is: + +- a. How to enhance the network monitoring procedures considering specific V2X UE information or group of V2X UE(s) information? + +# --- 5 Architectural requirements + +## 5.1 General requirements + +[AR-5.1-a] The V2X application architecture shall be able to support the V2X applications and V2X enabler services deployments in edge data network. + +## 5.2 VRU zone configuration requirements + +### 5.2.1 Description + +This subclause specifies the VRU zone configuration related requirements. + +### 5.2.2 Requirements + +[AR-5.2.2-a] The VAE capabilities shall support VRU zone configurations (e.g. distribution of VRU zone related configuration information) to the relevant V2X UEs. + +## 5.3 V2P communications requirements + +### 5.3.1 Description + +This subclause specifies the V2P communications related requirements. + +### 5.3.2 Requirements + +[AR-5.3.2-a] The VAE capabilities shall provide mechanisms (e.g. configurations) to support V2P communications. + +# --- 6 Solutions + +## 6.1 Solution #1 - VAE support for Energy Efficient V2P communications + +### 6.1.1 Solution description + +#### 6.1.1.1 General + +Vehicle to Pedestrian (V2P) is one of the V2X scenarios, which enables communication between vehicles and pedestrians for both safety and traffic efficiency related applications. One of the key V2P applications is the Vulnerable Road User Protection (VRUP) as specified in ETSI TS 103 300-2 [13]. VRUP provides warning to vehicles of the presence of vulnerable road users, e.g. pedestrian or cyclist, in case of dangerous situation. In VRUP, multiple V2X messages need to be exchanged between the pedestrian and the vehicular UEs, originating by one or more applications. Such messages can be standard VRU messages (e.g. VAM) and other V2X messages (CAM, DENM, BSM, CPM) and can be exchanged via different transmission modes (unicast, groupcast, broadcast). + +In such scenario, one challenge is that a pedestrian UE might have a lower battery capacity and limited radio capability, and therefore may have to work in a low power consumption mode, e.g. not being able to send/receive V2X messages with the same periodicity as a Vehicular UE. Continuous sending/receiving V2X messages by the pedestrian UE would affect UE power efficiency. A further challenge is that multiple applications related to VRU may be deployed, which may have differentiated traffic/QoS requirements as well as transmission/reception schedules. + +The VAE layer may provide support functionality for enabling V2P applications, by consolidating the V2P application requirements and aligning the communication traffic pattern with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles). Such alignment may be in the form of triggering the update of QoS / AS layer configuration based on application requirement (procedure is shown in clause 6.1.1.2.1 for client-triggered alignment and in clause 6.1.1.2.2 for VAE-server triggered alignment). + +The different procedures correspond to different solution variants to address different use cases. + +Clause 6.1.1.2.1 provides a VAE-client enabled V2P communication schedule configuration which could be applicable to off-network deployments and could be triggered by the application of the V2X UE (e.g. if UE battery drops while the V2P session is ongoing) based on prior configuration from the VAE server. + +On the other hand, clause 6.1.1.2.2 provides a VAE server enabled V2P communication schedule configuration, which could be applicable to use cases where the VAE server after receiving the VASS requirement, it configures/aligns the schedules for the V2X UEs (e.g. can be used within VRU zones to avoid flooding/interference by continuous sending/receiving V2X messages). + +#### 6.1.1.2 Procedures + +This subclause describes the procedures for V2P communication schedule configuration and update support by the VAE layer. This includes an off-network (VAE client enabled) and on-network (VAE server enabled) procedures for V2P communication schedule configuration. + +##### 6.1.1.2.1.1 Procedure for VAE client enabled V2P communication schedule configuration + +Figure 6.1.1.2.1-1 illustrates the procedure where the VAE client configures the traffic schedule for V2P communications based on application requirement; and triggers the translation to an AS layer/ QoS configurations update. + +Pre-conditions: + +1. VASS or VASC has subscribed to VAE layer to provide support for V2P communication. +2. VAE client 1 has been configured by the VAE server to configure the communication schedule for V2P communications. +3. V2X UE #1 and V2X UE#2 have discovered each other based upon V2P service and established a unicast connection using the V2X Service oriented Layer-2 link establishment procedure as specified in 3GPP TS 23.287 [7] clause 6.3.3.1 + +![Sequence diagram illustrating the VAE client-enabled V2P communication schedule configuration procedure between V2X UE #1 and V2X UE #2.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +The diagram shows the interaction between two User Equipment (UE) entities, V2X UE #1 (Pedestrian or Vehicle) and V2X UE #2 (Vehicle or Pedestrian). Each UE contains four internal components: V2X app specific client #2, V2X app specific client #1, VAE client, and V2X / AS layer. + +The sequence of messages is as follows: + +- 1. V2X application requirements:** Both V2X app specific client #1 and #2 in UE #1 send requirements to their respective VAE client. +- 2. Generate communication schedule for UE#1:** The VAE client in UE #1 consolidates the requirements from both clients and generates a UE-level transmission schedule. +- 3. V2P Communication schedule update:** The VAE client in UE #1 sends this update message to the VAE client in UE #2. +- 4. Generate / Update communication schedule for UE#2:** The VAE client in UE #2 generates or updates its own schedule based on the received update. +- 5. V2P Communication schedule update:** The VAE client in UE #2 sends a response or further update back to the VAE client in UE #1. +- 6. Trigger AS layer / QoS adaptation:** Both VAE clients trigger adaptations in their respective V2X / AS layers. +- 7. V2P communication schedule notification:** The V2X / AS layers in both UEs send notifications to their respective V2X app specific clients. + +The final state is labeled "V2P communication". + +Sequence diagram illustrating the VAE client-enabled V2P communication schedule configuration procedure between V2X UE #1 and V2X UE #2. + +**Figure 6.1.1.2.1-1: VAE client - enabled V2P communication schedule configuration** + +1. On V2X UE #1, the V2X application specific client 1 and 2 provide the V2X application requirements to the VAE client, including delay requirements, etc., for the PC5 communication. Here, this V2X Application specific client 1 may be requesting a groupcast communication and V2X Application specific client 2 may be requesting a unicast communication. +2. V2X UE #1's VAE client consolidates requirements from both applications and generates a UE level transmission schedule, so that the off-duration is maximized. The determination of the transmission schedule can be determined based on the configuration on the UE (energy efficiency target) and the service KPIs. +3. V2X UE #1's VAE client sends a V2P communication schedule update message which includes the generated UE level transmission schedule to other VAE client 2 (in vicinity, or in service-based group), in order to negotiate the optimal transmission pattern or inform on the expected reception pattern. +4. V2X UE #2's VAE client either accepts or provides its transmission cycle or negotiates the traffic pattern. +5. VAE clients of V2X UE #2 may optionally send a V2P communication schedule update message indicating the expected/generated UE #2 transmission pattern. +6. V2X UE #1's and V2X UE #2's VAE clients (VAE clients are deployed at V2X application layer), provide the updated traffic pattern as V2X Application Requirements to V2X layer, also including QoS requirements such as delay requirements, priority, etc., for the PC5 communication for both applications, as specified in 3GPP TS 23.287 [7] clause 5.4.1.1. VAE client may also indicate the transmission mode (unicast, groupcast) per application. The V2X/AS layer of UE #1 and #2 applies/configures the DRX schedule for the corresponding + +V2X communication, based on the updated traffic pattern per cast type and/or destination Layer ID (as specified in 3GPP TS 23.287 [7] clause 5.9). + +**Editor's Note:** It is FFS to identify possible dependencies to RAN2/SA2 for the consideration of the Tx Profile which may impact the details of step 6. + +- VAE clients of V2X UEs #1 and #2 may send a notification to the V2X application specific client(s) to inform on the communication traffic pattern. + +##### 6.1.1.2.2 Procedure for VAE server enabled V2P communication schedule configuration + +Figure 6.1.1.2.2-1 illustrates the procedure where the VAE server configures the traffic schedule for V2P communications based on application requirement; and communicates with the VAE clients to trigger the translation to an AS layer/ QoS configurations update. + +Pre-conditions: + +- VASS has subscribed to VAE server to provide support for V2P communication. +- VAE client of V2X UE #1 and V2X UE #2 are registered with VAE server. + +![Sequence diagram illustrating the VAE server-enabled V2P communication schedule configuration procedure. The diagram shows interactions between V2X UE #2, V2X UE #1 (containing V2X app specific client, VAE client, and V2X/AS layer), VAE server, and V2X app specific server. The steps are: 1. V2X application requirement from V2X app specific server to VAE server; 2. Generate communication schedule for V2X UE #1 and UE #2 from VAE server; 3. V2P Communication schedule configuration from VAE server to V2X UE #1; 4. Trigger AS layer / QoS adaptation from VAE client to V2X/AS layer; 5. Acknowledgement from V2X/AS layer to VAE server; 6. V2P communication schedule notification from VAE client to V2X app specific client. The process concludes with V2P communication.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +``` + +sequenceDiagram + participant V2X_UE_2 as V2X UE #2 + subgraph V2X_UE_1 [V2X UE #1 (Pedestrian or Vehicle)] + V2X_app_client[V2X app specific client] + VAE_client[VAE client] + V2X_AS_layer[V2X / AS layer] + end + participant VAE_server as VAE server + participant V2X_app_server as V2X app specific server + + Note right of V2X_app_server: 1. V2X application requirement + V2X_app_server->>VAE_server: 1. V2X application requirement + Note right of VAE_server: 2. Generate communication schedule for V2X UE #1 and UE #2 + VAE_server->>VAE_client: 3. V2P Communication schedule configuration + Note right of VAE_client: 4. Trigger AS layer / QoS adaptation + VAE_client->>V2X_AS_layer: 4. Trigger AS layer / QoS adaptation + Note right of V2X_AS_layer: 5. Acknowledgement + V2X_AS_layer->>VAE_server: 5. Acknowledgement + Note right of VAE_client: 6. V2P communication schedule notification + VAE_client->>V2X_app_client: 6. V2P communication schedule notification + Note bottom of V2X_UE_1: V2P communication + V2X_UE_2->>V2X_UE_1: V2P communication + +``` + +Sequence diagram illustrating the VAE server-enabled V2P communication schedule configuration procedure. The diagram shows interactions between V2X UE #2, V2X UE #1 (containing V2X app specific client, VAE client, and V2X/AS layer), VAE server, and V2X app specific server. The steps are: 1. V2X application requirement from V2X app specific server to VAE server; 2. Generate communication schedule for V2X UE #1 and UE #2 from VAE server; 3. V2P Communication schedule configuration from VAE server to V2X UE #1; 4. Trigger AS layer / QoS adaptation from VAE client to V2X/AS layer; 5. Acknowledgement from V2X/AS layer to VAE server; 6. V2P communication schedule notification from VAE client to V2X app specific client. The process concludes with V2P communication. + +**Figure 6.1.1.2.2-1: VAE server - enabled V2P communication schedule configuration** + +- One or more V2X application specific servers provide the V2X application requirements to the VAE server, including application QoS requirements for the V2P applications and provisioning policies and parameters for the PC5 communication. +- The VAE server generates a communication schedule for one or more involved V2X UEs, so that the off duration is maximized. The determination of the transmission schedule can be determined based on the V2P service KPIs. Such communication schedule may include the transmission/reception schedule for the application messages and may also include the DRX cycle configuration for out of coverage and groupcast/broadcast communications. +- The VAE server sends a V2P communication schedule configuration message to the involved VAE clients. This includes the generated UE level transmission schedules and may also include the DRX cycle configuration for PC5 communication in out of coverage and groupcast/broadcast modes. +- V2X UE #1's and V2X UE #2's VAE clients provide the updated traffic pattern as V2X Application Requirements to V2X layer, also including QoS requirements such as delay requirements, priority, etc., for the PC5 communication for both applications, as specified in 3GPP TS 23.287 [7] clause 5.4.1.1. VAE client may also indicate the transmission mode (unicast, groupcast) per application. The V2X layer of UEs #1 and #2 + +process the requirements from VAE client and generates a UE level DRX schedule. The AS layer of UE #1 and #2 applies/configures the DRX schedule for the corresponding V2X communication. + +5. VAE clients of V2X UEs #1 and #2 may send an acknowledgement to the VAE server. +6. VAE clients of V2X UEs #1 and #2 may send a notification to the V2X application specific client(s) to inform on the communication traffic pattern. + +### 6.1.2 Solution evaluation + +In this solution, the VAE layer provides a support functionality for enabling V2P applications, by consolidating the V2P application requirements and aligning the communication traffic pattern with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles). Such alignment may be in the form of triggering the update of QoS/AS layer configuration based on application requirement. + +There are two solution variants captured in this solution: + +- Client-triggered alignment in clause 6.1.1.2.1, has possible dependency on the SA2 work (for the consideration of the Tx Profile which may impact the details of step 6). Also, for this variant the relationship of service KPIs and energy efficiency target (as discussed in step 2) requires further consideration during the normative phase. +- VAE-server triggered alignment in clause 6.1.1.2.2) has no dependencies to SA2 and is a viable technical solution to address key issue#2. + +## 6.2 Solution #2 - Support for VRU zone configuration and operation + +### 6.2.1 Solution description + +#### 6.2.1.1 Procedure on VAL server - triggered VRU zone creation + +This procedure supports the configuration and provisioning of the VRU high risk zone at the VAE layer based on a request from the VASS / VAL server. + +Figure 6.2.1.1-1 illustrates the procedure where the VAE client configures the VRU zone based on application requirement; and supports the run-time operation based on an expected UE entrance to the zone. + +Pre-conditions: + +1. VASS or VASC has subscribed to VAE layer to provide support for V2P communication. + +![Sequence diagram illustrating VAL server - triggered VRU zone creation. The diagram shows interactions between V2X UEs (at high risk area), UE #1 (Pedestrian or Vehicle candidate VRU) containing V2X/VRU app #1, VAE client, and V2X/ AS layer, SEAL LMS, VAE server, and VASS. The sequence of messages is: 1. VRU zone management subscription req from V2X/VRU app #1 to VAE server; 2. Processing subscription req and store subscription from VAE server; 3. VRU zone management subscription resp from VAE server to VASS; 4. Initiate Location tracking to detect UEs approaching VRU zone and UEs within zone from SEAL LMS to VAE server; 5. Notification of VRU zone information to the UEs (within the zone) from VAE server to V2X UEs; 6. SEAL LMS event notifications for VRU zone from SEAL LMS to VAE server; 7. Notification of UE1 approaching / leaving zone from VAE server to VASS; 8. Notification of UE1 approaching / leaving zone from VAE server to V2X UEs (dashed line).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Sequence diagram illustrating VAL server - triggered VRU zone creation. The diagram shows interactions between V2X UEs (at high risk area), UE #1 (Pedestrian or Vehicle candidate VRU) containing V2X/VRU app #1, VAE client, and V2X/ AS layer, SEAL LMS, VAE server, and VASS. The sequence of messages is: 1. VRU zone management subscription req from V2X/VRU app #1 to VAE server; 2. Processing subscription req and store subscription from VAE server; 3. VRU zone management subscription resp from VAE server to VASS; 4. Initiate Location tracking to detect UEs approaching VRU zone and UEs within zone from SEAL LMS to VAE server; 5. Notification of VRU zone information to the UEs (within the zone) from VAE server to V2X UEs; 6. SEAL LMS event notifications for VRU zone from SEAL LMS to VAE server; 7. Notification of UE1 approaching / leaving zone from VAE server to VASS; 8. Notification of UE1 approaching / leaving zone from VAE server to V2X UEs (dashed line). + +**Figure 6.2.1.1-1: VAL server - triggered VRU zone creation** + +1. The V2X application specific server sends a subscription request to manage the creation and configuration of a new high-risk area zone, and requires the VAE server support to translate it to a network-related zone configuration and provisioning to the UEs within the requested area. The subscription request consists of the Requestor ID (VASS ID or App ID), the VRU zone type (based on the scenario, which type of UEs are to be considered), geographical area, time validity and initiation trigger, types of supported messages and requirements (e.g. requirements for VAM messages), application QoS requirement dedicated for the VRU zone (e.g. URLLC like), whether it is a dynamic or static zone, etc. + +NOTE: If the zone is dynamically changing based on an event (e.g. school bus mobility / route), such mobility/route information will be provided to the VAE server, or the VASS needs to provide new configuration every time the configuration changes. + +2. The VAE server processes the request and stores the subscription. The processing includes the translation of the zone requirement of step 1 and determines a set of network-related zone parameters which indicates the configuration parameters for example: the topological area for the zone (cell IDs, TAs), the QoS requirements within the zone, the exposure requirements within the zone, the value added services required within the zone (e.g. location tracking, V2X message bundling), the transmission modes (unicast, groupcast, broadcast) within the applications within the zone, the interface selection within the zone (Uu, PC5), the use of application relaying or not, whether the zone is dynamic or not, and if it is dynamic to take into account the configuration adaptation every time the configuration changes or to provide the planning (e.g. based on a school bus route) to allow the network to adapt the configuration. +3. The VAE server sends a VRU zone creation subscription response to VASS. +4. The VAE server initiates the SEAL LMS service for location tracking both for static location and dynamically changing location for all UEs within the VRU zone area. VAE server obtains and initiates tracking the V2X UEs location from the location management server 1 as specified in 3GPP TS 23.434 (clause 9.3.12). +5. The VAE server sends a notification message including the VRU zone configuration parameters. Parameters can be based on the parameters provided in step 2. This configuration will be provided to the V2X-UEs (and pedestrians) within the area that will be covered by the VRU zone, and will also indicate when the zone will be activated, for how much time and if the zone configuration will be dynamically changing (e.g. where a school bus moves) and parameters related to the dynamicity (as discussed in steps 1, 2). +6. The VAE server keeps monitoring the VRU zone area based on monitoring SEAL LMS events. This includes events on whether a UE (e.g. UE1) is moving in or out a target area of interest. + +The VAE server translates the UE1 mobility event to an expected entrance to a VRU high risk zone, and based on the configuration of the zone, it identifies when an action needs to be taken and when to communicate this with the involved application entities. + +7. The VAE server alerts the VASS that the UE1 is expected to move to the VRU zone area in X time and provides also information on its mobility as well as the UE1 capabilities (e.g. VRU capable). The notification / alert message may include the UE ID (GPSI, or external ID), the group ID (if it is a group of UEs), an expected start time of VRUP, an expected duration, expected mobility/speed/direction, etc. Alternatively, when UE is leaving the zone, a message can be sent to VASS to notify that the UE1 is expected to leave this area and the VRUP is no longer needed. +8. The VAE server may also alert the VAE client (if deployed at the UE1) that it is expected to enter the VRU zone and requests the confirmation for allowing the push of VRU messages within the zone. Such notification / request will include zone area information and configuration parameters. Alternatively, when UE is leaving the zone, a message can be sent to VAE client to notify that the UE1 is expected to leave this area and the VRUP is no longer needed. + +### 6.2.2 Solution evaluation + +This solution addresses KI #1 on zone configuration and provisioning for VRUP applications. The solution supports the configuration and provisioning of the VRU high risk zone at the VAE layer based on a request from the VASS / VAL server. This solution enables distribution of zones and notifications related to those zones, but any usage of this information is up to the application as this information is not directly used by the VAE layer. This solution is technically viable. + +## 6.3 Solution #3 - Deployment of V2X application layer with Edge Enabler Layer + +### 6.3.1 Solution description + +This solution corresponds to key issue#3. The architecture for edge enabler layer is specified in 3GPP TS 23.558 [11]. This clause describes the deployment of V2X application layer services at Edge Data Network by utilizing the Edge Enabler Layer services. + +Figure 6.3.1-1 illustrates the edge deployment example for the V2X application layer. For simplicity, the reference points between enabler server and 5GS are omitted, and the reference points for inter-enabler server communication in the same enabler layer are also omitted. At UE side, V2X Application Specific client(s) and VAE client interact with the Edge Enabler Client (EEC) via EDGE-5 reference point. In an Edge Data Network (EDN), V2X Application Specific Server and VAE server assume the role of EAS (Edge Application Server) and interacts with the Edge Enabler Server (EES) via EDGE-3 reference point, for instance, to register its profile into the EES. Upon service provisioning, the EEC interacts with the EES via EDGE-1 reference point, for instance, to discover V2X Application Specific Server(s) and VAE Server and further the EEC provides the discovered V2X Application Specific Server(s) and VAE server to the V2X Application Specific client and VAE client respectively. + +![Figure 6.3.1-1: Deployment of V2X application layer with Edge Enabler Layer. The diagram shows a V2X UE on the left and an EDN on the right, connected via a 5GS. The V2X UE contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. The EDN contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. Various interfaces (V1, Vc, Vs, V1-AE, SEAL-C, SEAL-S, SEAL-UU, EDGE-1, EDGE-3, EDGE-4, EDGE-5, EDGE-6) are shown between components.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the deployment of the V2X application layer with the Edge Enabler Layer. It is divided into two main entities: V2X UE (User Equipment) on the left and EDN (Edge Data Network) on the right, connected via a 5GS (5G System) in the center. The V2X UE contains several layers: V2X application specific layer (with V2X Application Specific Client(s)), VAE layer (with VAE client), SEAL layer (with SEAL clients), and EDGE Enabler layer (with Edge Enabler Client). The EDN contains corresponding layers: V2X application specific layer (with V2X Application Specific Server(s)), VAE layer (with VAE server), SEAL layer (with SEAL servers), and EDGE Enabler layer (with Edge Enabler Server and Edge Configuration Server). Interfaces are labeled as follows: V1 between V2X Application Specific Client(s) and V2X Application Specific Server(s); Vc and Vs between V2X Application Specific Client(s)/Server(s) and VAE client/server; V1-AE between VAE client and VAE server; SEAL-C and SEAL-S between VAE client/server and SEAL clients/servers; SEAL-UU between SEAL clients and SEAL servers; EDGE-1 between Edge Enabler Client and Edge Enabler Server; EDGE-3 between SEAL servers and Edge Enabler Server; EDGE-4 between Edge Enabler Client and Edge Configuration Server; EDGE-5 between Edge Enabler Client and SEAL clients; EDGE-6 between Edge Enabler Server and Edge Configuration Server. + +Figure 6.3.1-1: Deployment of V2X application layer with Edge Enabler Layer. The diagram shows a V2X UE on the left and an EDN on the right, connected via a 5GS. The V2X UE contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. The EDN contains layers for V2X application specific, VAE, SEAL, and EDGE Enabler. Various interfaces (V1, Vc, Vs, V1-AE, SEAL-C, SEAL-S, SEAL-UU, EDGE-1, EDGE-3, EDGE-4, EDGE-5, EDGE-6) are shown between components. + +**Figure 6.3.1-1: Deployment of V2X application layer with Edge Enabler Layer** + +In an EDN, there could be several EES(s) provided by the same or different ECSP. The V2X application specific server(s) and VAE server shall be able to discover and register into an appropriate EES. If CAPIF is used, this can be done by utilizing the AEF serving area and/or the AEF location as described in 3GPP TS 23.222 [4]; otherwise, local configuration of the EES endpoint may be used. + +Note that the services provided by EES over EDGE-3 are not re-exposed by the VAE server or SEAL servers to the V2X application specific server but are directly consumed by the SEAL servers, VAE server and V2X application specific server(s). + +### 6.3.2 Solution evaluation + +This solution addresses key issue#3 for "Whether and how V2X application architecture supports the edge enabler architecture specified in 3GPP TS 23.558 [11]" and provides a solution for the deployment of V2X application layer with Edge Enabler Layer. + +## 6.4 Solution #4 - UE initiated request for VRU zones + +### 6.4.1 Solution description + +#### 6.4.1.1 General + +A cyclist training for long-distance competitions is vulnerable to road collisions during the entire training route. The cyclist would like to create a protection zone that tracks their route for use as part of the services provided by the V2X service provider. The V2X infrastructure, including edge enabler servers, receives a request to create a protection zone and dynamically update the protection zone to follow the route of the cyclist. When an incoming vehicle is detected, the infrastructure can alert the vehicle and provision V2P communication configurations to enable the vehicle to communicate with the cyclist. + +The following solution is provided for key issues #1 and 2 and complements solution #1. This solution also enhances solution #2 by providing an option to employ the VAE layer to receive protection zone configuration requests from the UE and notify VASS. The two solutions can coexist in any deployment, with the VRU application determining whether solution#4 may be used based on a policy specifying whether: + +- Use of VAE service for protection zone notification is allowed; and +- Protection zone requests initiated by UEs are allowed. + +#### 6.4.1.2 Procedure + +Pre-conditions: + +- VASS has subscribed to VAE server to provide support for V2P communication. +- VAE clients of V2X cyclist UE and vehicular UE are registered with VAE server. +- The VRU application (at VASS and Application client at the cyclist UE) are pre-configured so that: + - Use of VAE service for protection zone notification is allowed; and + - Protection zone requests be initiated by UEs are allowed. + +NOTE 1: Pre-condition 3 allows VAE server to determine that use of solution#4 mechanism is allowed. + +![Sequence diagram illustrating the UE request for protection zone procedure. The diagram shows interactions between Vehicular UE (VAE client), Pedestrian UE (App client and VAE client), 5GS, SEAL LMS, VAE Server, and VASS. The sequence starts with the Pedestrian UE sending a protection zone request to the VAE client, which then sends a request to the VAE server. The VAE server requests authorization from the VASS, which creates the protection zone and responds. The VAE server then configures subscriptions and sends a protection zone response to the Pedestrian UE. Finally, the VAE server sends UE mobility information and application context information to the 5GS, which updates the protection zone and notifies UEs, sending a notification alert to the Pedestrian UE.](29f586959675cafdf81cf934954908eb_img.jpg) + +``` + +sequenceDiagram + participant VUE as Vehicular UE +VAE client + participant PUE as Pedestrian UE +App client | VAE client + participant 5GS + participant SEAL as SEAL LMS + participant VAE as VAE Server + participant VASS + + Note right of PUE: 1. Protection zone request + PUE->>VAE: 2. Protection zone request + VAE->>VASS: 3. Request authorization + VASS->>VAE: 4. Create protection zone + VASS->>VAE: 5. Authorization response + VAE->>5GS: 6. Configure subscriptions + VAE->>PUE: 7. Protection zone response + Note right of 5GS: 8. Protection zone response + Note right of 5GS: 9a. UE mobility information + Note right of 5GS: 9b. UE application context information + Note right of 5GS: 10. Update protection zone and notify UEs in the protectionzone + Note right of 5GS: 11. Notification alert + 5GS->>PUE: 11. Notification alert + +``` + +Sequence diagram illustrating the UE request for protection zone procedure. The diagram shows interactions between Vehicular UE (VAE client), Pedestrian UE (App client and VAE client), 5GS, SEAL LMS, VAE Server, and VASS. The sequence starts with the Pedestrian UE sending a protection zone request to the VAE client, which then sends a request to the VAE server. The VAE server requests authorization from the VASS, which creates the protection zone and responds. The VAE server then configures subscriptions and sends a protection zone response to the Pedestrian UE. Finally, the VAE server sends UE mobility information and application context information to the 5GS, which updates the protection zone and notifies UEs, sending a notification alert to the Pedestrian UE. + +Figure 6.4.1.2-1: UE request for protection zone + +- Optionally, an application client on a cyclist UE makes a request to the VAE client to create a protection zone. +- A VAE client sends a request to a VAE server to create a protection zone. The request may include V2X Service ID, UE ID, application ID, UE location and location reporting configuration, destination location, request for dynamic protection zone, V2P communication configuration, user consent for using user application context information, user activity, active applications, etc. +- The VAE server sends a request to a VASS to authorize the creation of the protection zone for the cyclist UE and includes the information provided by the cyclist UE. + +4. The VASS authorizes the request and creates a protection zone based on information received from the VAE server. The VASS provides the VAE server with the protection zone and V2P communication configuration. +5. The VASS responds with an authorization response to the VAE server. The response includes the status of the authorization, the protection zone type, geographical area, time validity and initiation trigger, types of supported messages and requirements (e.g. requirements for VAM messages), application QoS requirement dedicated for the protection zone (e.g. URLLC like), whether it is a dynamic or static zone, an expiration for the protection zone, V2P communication configuration information, etc. +6. The VAE server configures subscriptions to obtain UE location from the 5G system. Sources of UE mobility information may come from SEAL LMS servers, EES, an analytics function (e.g. from ADAES or NWDAF), and the 5G core network. For V2X UEs location obtained from the location management server, the procedures specified in 3GPP TS 23.434 (clause 9.3.12) apply. +7. The VAE server sends a response message to the cyclist UE with a status for the request, the information of the protection zone, and updated V2P communication configuration. The VAE server may also subscribe to receive notifications from the VAE client about application context events such as user activity, active applications, application notifications, navigation information, etc. +8. Optionally, the VAE client returns a response to the application client. +9. The VAE server receives UE mobility information from the 5G network and/or from the UEs. The cyclist UE and vehicular UE may also provide application context information to the VAE server, such as battery level, user activity, active applications, and routing information from a navigation app. The battery level of the UE may help the VAE server determine the V2P communication configuration to provide to UEs in the protection zone. For example, if the battery level of a cyclist UE is low, the VAE server may provide V2P communication configurations to vehicular UEs to align with when the cyclist UE is able to receive V2P communication. Alternatively, the VAE server can provide V2P communication parameters to vehicular UEs to communicate with nearby UEs instead. +10. The VAE server updates the protection zone based on information the VAE server has obtained about the cyclist UE. For example, the protection zone may be updated due to a change in UE location. In addition, the VAE server may broadcast the new protection zone information to all the UEs in the protection zone. +11. The VAE server detects that a vehicular UE is now in the updated protection zone and sends a notification alert to the vehicular UE and includes the V2P communication configuration for use by the vehicular UE to communicate directly with the cyclist UE. + +### 6.4.2 Solution evaluation + +This solution addresses KI #1 and aspects of KI #2 and provides a procedure for a VAL client on a cyclist UE to request the creation of a dynamic protection zone via the VAE client. The VAE server checks with a VASS to authorize the request and if authorized, the VASS creates a protection zone based on the information provided by the VAE client. After the creation of the protection zone, the VAE server monitors the UE's mobility information and updates the protection zone accordingly. If the VAE server detects the presence of other vehicular UEs in the updated protection zone, the VAE server sends a notification alert to the vehicular UE and includes V2P communication configuration information. + +Further agreement is needed for the scenario of this solution where UEs can initiate VRU protection zone creation. + +## 6.5 Solution #5 - Enhanced network monitoring + +### 6.5.1 Solution description + +#### 6.5.1.1 General + +This solution corresponds to key issue#6. The network monitoring subscription and notification procedures specified in clause 9.7 of 3GPP TS 23.286 [6] are enhanced to allow a V2X UE for subscription and notification of network situation monitoring events considering a single V2X UE or a group of V2X UE(s) in addition to area information. + +#### 6.5.1.2 Enhancements to subscription procedure in clause 9.7.3 + +In step 1, the network monitoring information subscription request from VAE client to VAE server can include target V2X UE ID(s) in addition to area information. + +In step 2, the VAE server is enhanced to initiate network monitoring considering the requested information in step 1. + +#### 6.5.1.3 Enhancements to notification procedure in clause 9.7.4 + +In step 1, the network monitoring of VAE server with 5GC is enhanced to include configuring and receiving network monitoring events for V2X UE ID(s) also as per the subscription. + +### 6.5.2 Solution evaluation + +This is a viable technical solution to address key issue#6. + +## 6.6 Solution #6 – Network situation enhanced with analytics + +### 6.6.1 Solution description + +#### 6.6.1.1 General + +This solution corresponds to key issue#5. The network situation monitoring procedures specified in clause 9.7 and clause 9.20 of 3GPP TS 23.286 [6] are enhanced to utilize the SEAL's ADAE services for application performance analytics and prediction. + +#### 6.6.1.2 Enhancements to network monitoring by V2X UE + +In clause 9.7.3, step 2 of 3GPP TS 23.286 [6], the VAE server is enhanced to utilize the SEAL's ADAE service for application performance analytics and prediction. + +In clause 9.7.4, step 1 of 3GPP TS 23.286 [6], the network monitoring also includes the SEAL's ADAE service. In step 2, the VAE server processes the information obtained from SEAL's ADAE service corresponding to the application session. In step 3, the VAE server provides the notification to the V2X UE about both network situation and the predicted network situation. + +#### 6.6.1.3 Enhancements to monitoring and control of QoS for eV2X communications + +In clause 9.20.3, step 2 of 3GPP TS 23.286 [6], the VAE server is enhanced to utilize the SEAL's ADAE service for application performance analytics and prediction. + +In clause 9.20.4, step 1 of 3GPP TS 23.286 [6], the monitoring reports also includes the SEAL's ADAE service. In step 2, the VAE server processes the information obtained from SEAL's ADAE service corresponding to the application session. In step 3, the VAE server provides the service requirement adaptation notification request to V2X application specific server about both network situation and the predicted network situation to initiate any application session adaptation (e.g. session oriented service update or terminate). + +### 6.6.2 Solution evaluation + +This is a viable technical solution to address key issue#5 for supporting utilization of improved analytics. + +# 7 Overall evaluation + +## 7.1 General + +The following subclauses contain an overall evaluation of the solutions presented in this technical report, and their applicability to the identified key issues. + +- Clause 7.2 lists the solutions for the key issues including impact on other working groups that will need consideration. + +## 7.2 Key issue and solution evaluation + +All the key issues and solutions specified in this technical report are listed in table 7.2-1. It includes the mapping of the key issues (clause 4) to the solutions and corresponding solution evaluations. Also it lists the impact on other working groups that will need consideration during the Release 18 normative phase. + +**Table 7.2-1: Key issue and solution evaluation** + +| Key issues | Solution | Evaluation (subclause reference) | Dependency on other working groups | +|---------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|----------------------------------|------------------------------------| +| Key issue #1 – Support for high risk VRU zones | Solution #2 - Support for VRU zone configuration and operation | Clause 6.2.2 | SA2, RAN2 | +| | Solution #4 - UE initiated request for VRU zones | Clause 6.4.2 | - | +| Key issue #2 – Support for V2P communications | Solution #1 - VAE support for Energy Efficient V2P communications | Clause 6.1.2 | - | +| | Solution #4 - UE initiated request for VRU zones | Clause 6.4.2 | - | +| Key issue #3 – V2X service deployment in edge data network | Solution #3 - Deployment of V2X application layer with Edge Enabler Layer | Clause 6.3.2 | - | +| Key issue #4 – Enhancement to support non-simultaneous multiple service providers control for advanced V2X services | - | - | - | +| Key issue #5 – Usage of network analytics | Solution #6 – Network situation enhanced with analytics | Clause 6.6.2 | - | +| Key issue #6 – Enhanced network monitoring to support advanced V2X services | Solution #5: Enhanced network monitoring | Clause 6.5.2 | - | + +## 7.3 Overall evaluation of key issue#1 + +Key issue#1 on support for high risk VRU zones discussed the following open issues: + +- Whether and how to enhance VAE layer capabilities to support configuring the communication parameters for the zones. +- Whether and how to enhance VAE layer capabilities to translate the zone configurations to network requirements and zone specific provisioning parameters. +- Whether and how to assist the provisioning of zone specific parameters to the devices which can be potential VRUs and V2X-UEs. + +Solution#2 provides a solution for network initiated VRU zone configuration and operation. It addresses the open issues in a, b and c. + +Solution#4 provides a solution for UE initiated configuration and operation of protection zones. + +## 7.4 Overall evaluation of key issue#2 + +Key issue#2 on support for V2P communications discussed the following open issues: + +- a. Whether and how the VAE layer can support the V2P communications considering the UE situation (e.g. low battery power, weak radio signals)? +- b. Whether and how the VAE layer can coordinate the alignment of the communication traffic patterns with the PC5 QoS setting and the AS layer configurations (e.g. DRX cycles)? + +Solution#1 provides a solution for VAE support for energy efficient V2P communications. It addresses the open issues in a and b. The solution#1 is dependent on SA2 and RAN2. + +## 7.5 Overall evaluation of key issue#3 + +Key issue#3 on V2X service deployment on edge data network discussed the following open issues: + +- a. Whether and how V2X application architecture supports the edge enabler architecture specified in 3GPP TS 23.558 [11]. +- b. Investigate the the impact on V2X enabler services for edge deployments. + +Solution#3 addresses the open issue a of key issue#3 which further enables the V2X service deployments to utilize edge enabler layer for V2X service deployments. No impact on V2X enabler services for edge deployments were identified as per open issue b. + +## 7.6 Overall evaluation of key issue#4 + +Key issue#4 on enhancement to support non-simultaneous multiple service providers control for advanced V2X services discussed the following open issues: + +- a. Whether and how V2X enabler services (e.g. session oriented services) can support non-simultaneous multiple V2X service provider control for advanced V2X services. + +No solutions were proposed to address this key issue. + +## 7.7 Overall evaluation of key issue#5 + +Key issue#5 on usage of network analytics discussed the following open issues: + +- a. Whether and how V2X enabler services (e.g. session oriented services, V2X message delivery) can be enhanced to utilize the network analytics services specified in 3GPP TS 23.288 [8] and 3GPP TS 23.436 [9]. + +Solution#6 provides a solution for usage of network analytics offered by ADAE. It addresses the open issue a. + +## 7.8 Overall evaluation of key issue#6 + +Key issue#6 on enhanced network monitoring to support advanced V2X services discussed the following open issues: + +- a. How to enhance the network monitoring procedures considering specific V2X UE information or group of V2X UE(s) information? + +Solution#5 provides a solution for enhanced network monitoring. It addresses the open issue a. + +# 8 Conclusions + +This technical report fulfills the objectives of the study on enhancements to application layer to support advanced V2X services like V2P, ToD, etc and edge computing deployments for V2X services. The study includes the following: + +- 1) Identification of key issues (clause 4) and corresponding architecture requirements (clause 5) for enhanced V2X application enabler capabilities. +- 2) Individual solutions (clause 5) addressing the key issues. +- 3) Overall evaluation (clause 7) of all the key issues and solutions. + +The results from the study will be considered for follow-up normative work in Release 18 as follows: + +- 1) The architecture requirements (in clause 5) will be considered as the basis for technical specification with necessary enhancements and additions; +- 2) The following key issues (clause 4) and individual solutions (clause 6) are considered to be the candidate solutions with necessary enhancements as appropriate, according to the overall evaluation (clause 7): + - For key issue#1, solution#2 is considered and solution#4 can be considered based on the agreement on the use of protection zones. + - For key issue#2, solution#1 is considered subjected to capabilities enabled by SA2 and RAN2. + - For key issue#3, solution#3 is considered. + - For key issue#4, there is no solution proposed. + - For key issue#5, solution#6 is considered. + - For key issue#6, solution#5 is considered. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-10 | SA6#45-bis-e | | | | | TR skeleton as approved by SA6 in S6-212349 | 0.0.0 | +| 2021-10 | SA6#45-bis-e | | | | | Implementation of the following pCRs approved by SA6: S6-212397, S6-212398, S6-212435 | 0.1.0 | +| 2021-11 | SA6#46-e | | | | | Implementation of the following pCRs approved by SA6: S6-212661, S6-212758, S6-212800 | 0.2.0 | +| 2022-02 | SA6#47-e | | | | | Implementation of the following pCRs approved by SA6: S6-220103 | 0.3.0 | +| 2022-04 | SA6#48-e | | | | | Implementation of the following pCRs approved by SA6: S6-220904, S6-220971 | 0.4.0 | +| 2022-05 | SA6#49-e | | | | | Implementation of the following pCRs approved by SA6: S6-221439, S6-221495 | 0.5.0 | +| 2022-06 | SA#96 | SP-220461 | | | | Presentation for information at SA#96 | 1.0.0 | +| 2022-07 | SA6#49-bis-e | | | | | Implementation of the following pCRs approved by SA6: S6-221757, S6-221758, S6-221928 | 1.1.0 | +| 2022-08 | SA6#50-e | | | | | Implementation of the following pCRs approved by SA6: S6-222428, S6-222429, S6-222537, S6-222538 | 1.2.0 | +| 2022-10 | SA6#51-e | | | | | Implementation of the following pCRs approved by SA6: S6-222650, S6-222839, S6-222840, S6-223021, S6-223022 | 1.3.0 | +| 2022-11 | SA6#52 | | | | | Implementation of the following pCRs approved by SA6: S6-223390, S6-223633 | 1.4.0 | +| 2022-12 | SA#98-e | SP-221222 | | | | Submitted for Approval at SA#98-e | 2.0.0 | +| 2022-12 | SA#98-e | SP-221222 | | | | MCC Editorial update for publication after TSG SA approval (SA#98-e) | 18.0.0 | +| 2023-03 | SA#99 | SP-230299 | 0001 | 1 | 2 | FS eV2XAPP2 solution #4 naming correction | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-71/0726a03ffb4e106eb90cd4f9283a6347_img.jpg b/raw/rel-18/23_series/23700-71/0726a03ffb4e106eb90cd4f9283a6347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afea9b8a626ad17b55cbc99bfedd61724e39cc25 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/0726a03ffb4e106eb90cd4f9283a6347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8115060f4fd4b0fe7efc0e449bb9e7ec23be7b6332617a5f4a58c6b4f7688435 +size 108858 diff --git a/raw/rel-18/23_series/23700-71/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/raw/rel-18/23_series/23700-71/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..140898bcf9e54ef722a2b8ccbc3ee81f2b4696f0 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72504bcedd4b972c31fe42905f5db634749a1494bdeff76c14166f48d03fa172 +size 87744 diff --git a/raw/rel-18/23_series/23700-71/11f18bf0233d812ad2604f88f3385d60_img.jpg b/raw/rel-18/23_series/23700-71/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7083c64137cb7542045e7635531ed205efad8645 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32885482ea0737e0422bd7048178be841dfb8a2ca685d9772c3d176751b012a7 +size 44416 diff --git a/raw/rel-18/23_series/23700-71/1ad662a678c4f002de911d403f00de8e_img.jpg b/raw/rel-18/23_series/23700-71/1ad662a678c4f002de911d403f00de8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ad1cc9d73d799e8f296e02be09fe6a8a02dc1b4 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/1ad662a678c4f002de911d403f00de8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:634d84e4fa1b06b926b180e62a6cafcfa147f1e127081e7c1d5196b6c7dc1acb +size 122460 diff --git a/raw/rel-18/23_series/23700-71/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/raw/rel-18/23_series/23700-71/1bc1746388cb64bf23b356ce2365dfc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa3224b0ab1fbe18f793b2c68e31c553bab37ced --- /dev/null +++ b/raw/rel-18/23_series/23700-71/1bc1746388cb64bf23b356ce2365dfc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58c7ce5950afd5b1549f91991832995b96521be7e7fd1108025da8db7ad9e4ef +size 196372 diff --git a/raw/rel-18/23_series/23700-71/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg b/raw/rel-18/23_series/23700-71/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0254ee4fd27af29fbc410fc318e1fde2d00b17b0 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/1f3389a0b9ef108721bdc3b3a6e364b7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce52999c6884a92b65f2bcc41ac0e70ae30871d9b2f020a875d8f2af3579aa3a +size 127821 diff --git a/raw/rel-18/23_series/23700-71/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/23_series/23700-71/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a24d89635d64a3b0dad56b301dd687349cf024d5 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68c00c0be7830b8b11e7a03e314ee73718143f92bbcac32447d98480d38347bf +size 6654 diff --git a/raw/rel-18/23_series/23700-71/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/raw/rel-18/23_series/23700-71/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67d7e0ae81682270a6480ffe08c1b56c08f548bc --- /dev/null +++ b/raw/rel-18/23_series/23700-71/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ff47bd2f5a3e155b4973e8f9586dcbf19b78e275f86c7ad6bafd146b61ef526 +size 99207 diff --git a/raw/rel-18/23_series/23700-71/2876be3592c7b4878400b85f209b2b6a_img.jpg b/raw/rel-18/23_series/23700-71/2876be3592c7b4878400b85f209b2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94a70f5b9977ea086b5f56837834013bdefcba65 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/2876be3592c7b4878400b85f209b2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:068f441f93452ad7d1d7c3bf4b3d6ff893c5d7c5f80ac4a88d8b47ff1acdc852 +size 50420 diff --git a/raw/rel-18/23_series/23700-71/32ff77da4286b58c4778033acaa10836_img.jpg b/raw/rel-18/23_series/23700-71/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fce3dfb583dc65561c916d49db0b1a21d2b772d --- /dev/null +++ b/raw/rel-18/23_series/23700-71/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e7091fd626b0558321d6f329f1d48d333fd447f70cc3c372ad9cfe3ac91a5f5 +size 44264 diff --git a/raw/rel-18/23_series/23700-71/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg b/raw/rel-18/23_series/23700-71/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62bcb49d13bace730ba28c22b6b26edee0c3d843 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaf9c5df0e80d0f5dc1a8cd374655b7b257cd7e889977f467d78d78a626fceb7 +size 96875 diff --git a/raw/rel-18/23_series/23700-71/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/raw/rel-18/23_series/23700-71/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4c5fa79878277a455e756bdbbe3a75cb396d807 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14baa0e26bf19b7e851a1d67c5522b6fa26d79e2755be1404329fc36488818e7 +size 91101 diff --git a/raw/rel-18/23_series/23700-71/34b047489058d6400b412cd0ae2334ba_img.jpg b/raw/rel-18/23_series/23700-71/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99e02c968f7e2b98c9f33432b1824ecdd4ebe72d --- /dev/null +++ b/raw/rel-18/23_series/23700-71/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d69cf31f8a396ac3cffe20dd60d15305278fd3db6469ad9b504f761683f4538 +size 47829 diff --git a/raw/rel-18/23_series/23700-71/356eb99ab9489bbd647223390a913903_img.jpg b/raw/rel-18/23_series/23700-71/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2066074e699ac05881be650be91c760051a33fc --- /dev/null +++ b/raw/rel-18/23_series/23700-71/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5483901c6d6afbe328f67523e533a26facbb30ae9f0d7b1f8c01d9a6e24a7469 +size 95864 diff --git a/raw/rel-18/23_series/23700-71/4540c7355b250cb891be0b54b0ba25c7_img.jpg b/raw/rel-18/23_series/23700-71/4540c7355b250cb891be0b54b0ba25c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e55d41b68d6fb0a52c727db272146311db09d5f8 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/4540c7355b250cb891be0b54b0ba25c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:955574b47440a62cc652cd8d50bdc1e1b716962e12dd6f771d592c2e4d3b2a7e +size 64769 diff --git a/raw/rel-18/23_series/23700-71/474a819357587e34949a3e110ff19b30_img.jpg b/raw/rel-18/23_series/23700-71/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69369dfbc6287308e177a434731a45caf9ef5a01 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:266a2be96902d88232589a28a1f40d8c6ebc266bc43cbfb17f8326686675ff82 +size 135575 diff --git a/raw/rel-18/23_series/23700-71/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/raw/rel-18/23_series/23700-71/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a66c9a889c1464805dd2d476ba3122251a1234d --- /dev/null +++ b/raw/rel-18/23_series/23700-71/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9564f3632cd43559d3b3f1a4042aacf5b570d16c13889949172b8a7217f067b +size 116531 diff --git a/raw/rel-18/23_series/23700-71/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/raw/rel-18/23_series/23700-71/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d5b44ca8cc7fb5c1600df5909d3a71a4bc2637a --- /dev/null +++ b/raw/rel-18/23_series/23700-71/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16ee5753898447d0f72b64a6ae961dc31aedb293f21ac8f74f62c803374e26f6 +size 109140 diff --git a/raw/rel-18/23_series/23700-71/4b8c5ecb492fd759c766fe8950fafe67_img.jpg b/raw/rel-18/23_series/23700-71/4b8c5ecb492fd759c766fe8950fafe67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c53f5348600d57ff621bf9cec71d280c5f749472 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/4b8c5ecb492fd759c766fe8950fafe67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74fe2f185e674ff4b8cae2155a2b86cce886dac9b75038d67c701d38c0879157 +size 76350 diff --git a/raw/rel-18/23_series/23700-71/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg b/raw/rel-18/23_series/23700-71/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8617dd1e5e18e8a7d969fbaa7ada854ad823ab3f --- /dev/null +++ b/raw/rel-18/23_series/23700-71/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dd9ccfbe5f244f3763d318081a28da906ea1241823f7da27f7f303d087c14b7 +size 77325 diff --git a/raw/rel-18/23_series/23700-71/50214d232017279410e9c9db8eb75119_img.jpg b/raw/rel-18/23_series/23700-71/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5824d02d7be90a035cbf708dc79a9f74666ad6e8 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4694678c4374e3036f7baa5c5802a466dd277ca53935e5f9d685a5439ec27c69 +size 27532 diff --git a/raw/rel-18/23_series/23700-71/508bc574df81fa8d3027a374f6d155fc_img.jpg b/raw/rel-18/23_series/23700-71/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..505b8829bdf1f8abf1930850b068b1b8fa7ea2ca --- /dev/null +++ b/raw/rel-18/23_series/23700-71/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68a5538a02340e918efd8481062e035621747af9cca626667d868aa934831476 +size 62491 diff --git a/raw/rel-18/23_series/23700-71/536768a30136cd5c2d57f46c25d1d804_img.jpg b/raw/rel-18/23_series/23700-71/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f030979102c36eb124ef7c2bfebddc21482a191 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbccc1d372c6534db9ac040ed874b186bf6a3b6a368ad5b83cbd35f30b5194e3 +size 150113 diff --git a/raw/rel-18/23_series/23700-71/54159e6d8f5ecc73ad262758e3a60677_img.jpg b/raw/rel-18/23_series/23700-71/54159e6d8f5ecc73ad262758e3a60677_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..542643dd20461224380bcc0cda7a28a076340540 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/54159e6d8f5ecc73ad262758e3a60677_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8281c359459ede5323d6c3ca7a48d84e03c79fc19fbd0180650a9a5d2dfe2729 +size 90458 diff --git a/raw/rel-18/23_series/23700-71/5432eacbc055292cc3b3da108863b835_img.jpg b/raw/rel-18/23_series/23700-71/5432eacbc055292cc3b3da108863b835_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58888e5b6f7ab1394c8b78370a39902d0a221105 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/5432eacbc055292cc3b3da108863b835_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d6b062d1e2fc8e2350b423395c42041a50d60d4d45a30ab9ad2a50987c95d64 +size 25665 diff --git a/raw/rel-18/23_series/23700-71/57134800ac3a97b6212b27b93aa196ac_img.jpg b/raw/rel-18/23_series/23700-71/57134800ac3a97b6212b27b93aa196ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f09d5a565de50f34df84f90cdf5be0111a351207 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/57134800ac3a97b6212b27b93aa196ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84ecc2f59aabdf96d7fff1abf787c56a3e287bb8590ec71130de867e88075036 +size 55778 diff --git a/raw/rel-18/23_series/23700-71/5801c19431e76330430e92a598cc7a16_img.jpg b/raw/rel-18/23_series/23700-71/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7bfee21f2908648a313d18c91f5d791d6df73c1 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2e3f1a179003256f95bcd2f91426437d04553575126b42ba9401de2dcb91d81 +size 115182 diff --git a/raw/rel-18/23_series/23700-71/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg b/raw/rel-18/23_series/23700-71/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8b74abd3f922dd82c7efb05ab2da9fa4c112bd2 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7e2e326af09ae7ccc2e0882ad965daac837f2f4ab2c644e8005e050dc788e7a +size 198612 diff --git a/raw/rel-18/23_series/23700-71/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-71/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f771bd2b0daeaace7f230c75315dd5c97b508e46 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45615afc9f40105b11e44bf142e36065506e01130fb17b1df10c30eda513b7b5 +size 9439 diff --git a/raw/rel-18/23_series/23700-71/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/raw/rel-18/23_series/23700-71/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6afe553846230da79dc1857143aa9a76567b0ee0 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22d6de8be620d6c8400f65f9eea44d61326321fa813fa170b3335e0967ed53ad +size 40344 diff --git a/raw/rel-18/23_series/23700-71/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg b/raw/rel-18/23_series/23700-71/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39bd03004a215202f962c41cfd7e3ff7fa432d3d --- /dev/null +++ b/raw/rel-18/23_series/23700-71/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84b8f4f1b6b49db7aa567bf27dd0106092041e2bf0f4b2ed409ee0882b1a07b0 +size 56017 diff --git a/raw/rel-18/23_series/23700-71/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/raw/rel-18/23_series/23700-71/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a53dfdcaccaa280947bbbd38ed79b7b7619e0834 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c0e849b3390245473519aa401f7bbca6b81ff8cf17d20caa3bc9236b47ccaba +size 47721 diff --git a/raw/rel-18/23_series/23700-71/6322885569221ec51d70560d7dba1339_img.jpg b/raw/rel-18/23_series/23700-71/6322885569221ec51d70560d7dba1339_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66c644376ed4ed6f752851fcfa070d414dfb103d --- /dev/null +++ b/raw/rel-18/23_series/23700-71/6322885569221ec51d70560d7dba1339_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:392c52b063f1e88efd2af4e87550dbf50070193b36e5924267faba8a1425eb0a +size 50691 diff --git a/raw/rel-18/23_series/23700-71/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-71/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09f1d0411696a86e352f9c4de874177cf2812a94 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d93fca23fd44c978fa1dc2194ad519c1c24769bae8b5324a1f63fab82869eb06 +size 5658 diff --git a/raw/rel-18/23_series/23700-71/64bec4cd45e47e1976245711f702aca2_img.jpg b/raw/rel-18/23_series/23700-71/64bec4cd45e47e1976245711f702aca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fef94b0a29e2301ce7e3e1c5b9e228fd61c6358 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/64bec4cd45e47e1976245711f702aca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2febed3799735ff02e4ba4103c8eb52736113601ca7798552f3601dc8fc25293 +size 42369 diff --git a/raw/rel-18/23_series/23700-71/67a1dd734d3de6e31754caf85d6fe77f_img.jpg b/raw/rel-18/23_series/23700-71/67a1dd734d3de6e31754caf85d6fe77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35ffe8a5405701f645ef9641b099663866490db5 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/67a1dd734d3de6e31754caf85d6fe77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc1f1c66e1fbf290630126144ee5ef85adf5675c7046b716ca61ce4c207bdc85 +size 198521 diff --git a/raw/rel-18/23_series/23700-71/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/raw/rel-18/23_series/23700-71/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e8043c0bf9eadcbfc9fcc33c687715753b8b38e --- /dev/null +++ b/raw/rel-18/23_series/23700-71/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28133c7ed1c7c229b55c281f5b1b52164f8011ad950a1803bb83d1653c8f26a9 +size 183109 diff --git a/raw/rel-18/23_series/23700-71/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/raw/rel-18/23_series/23700-71/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d66b8a9dfd5c0d34888d80035e78f678d1bb68dd --- /dev/null +++ b/raw/rel-18/23_series/23700-71/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ca206cb3ed3a713ce73479f59452fa3b2649981fd45d562b3c8380fbacc106c +size 34614 diff --git a/raw/rel-18/23_series/23700-71/6a555cff11e140861ce08db72b01a6a2_img.jpg b/raw/rel-18/23_series/23700-71/6a555cff11e140861ce08db72b01a6a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c99c5abb09d99b713eff2009625e51c879ad9562 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/6a555cff11e140861ce08db72b01a6a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc52e94b9d0d1e41062f8df9bf9084758fccf3e396cc402ab066a1332053cb75 +size 50835 diff --git a/raw/rel-18/23_series/23700-71/6bbd36c86c0876e31b1bc2c4e63b029d_img.jpg b/raw/rel-18/23_series/23700-71/6bbd36c86c0876e31b1bc2c4e63b029d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb096e102f37e3112f64cbf85151e101be17fe95 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/6bbd36c86c0876e31b1bc2c4e63b029d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98dff6731a4750e5ac161ca2a810d11f8ac657fe392185f0206a4cd140402f89 +size 76562 diff --git a/raw/rel-18/23_series/23700-71/7c4726a694799239785f7869a6947472_img.jpg b/raw/rel-18/23_series/23700-71/7c4726a694799239785f7869a6947472_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c06227840a3fcb801c6c991cfe8e7378a57d6056 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/7c4726a694799239785f7869a6947472_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dba314cc43d0f863f2630dc4831d99dd6e06d523f7a6cc6dd103dfce129d6061 +size 111842 diff --git a/raw/rel-18/23_series/23700-71/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/raw/rel-18/23_series/23700-71/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4a701fc230aca0ace723ac49ae45fddbf047142 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8231ae666debb9fe8e30e4eef35735dc712a65e78c7a2c0e21ed50a749640f57 +size 89414 diff --git a/raw/rel-18/23_series/23700-71/879d68959f0c0ba370ef82447298ba17_img.jpg b/raw/rel-18/23_series/23700-71/879d68959f0c0ba370ef82447298ba17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db02513933866a5971e459a99429fd9bd3f120eb --- /dev/null +++ b/raw/rel-18/23_series/23700-71/879d68959f0c0ba370ef82447298ba17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13a469c75b6e1ee487bd29be354ed5d80537679d3457cd6cbc51624be9c84581 +size 72205 diff --git a/raw/rel-18/23_series/23700-71/8942c590307508b28df9c207bad75740_img.jpg b/raw/rel-18/23_series/23700-71/8942c590307508b28df9c207bad75740_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..263a836f3c3c623b73012cdc8003f669c0f2020a --- /dev/null +++ b/raw/rel-18/23_series/23700-71/8942c590307508b28df9c207bad75740_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6468f25b36fa414fa492521fb090544e3de19a2e84b8642bf49f273ab8002e2 +size 65550 diff --git a/raw/rel-18/23_series/23700-71/8a94796989f4fcba2688c4faa7991538_img.jpg b/raw/rel-18/23_series/23700-71/8a94796989f4fcba2688c4faa7991538_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93822688580fe054ce7a8f49d8705cea82248cc1 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/8a94796989f4fcba2688c4faa7991538_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0edd0ad82f4803c51a08d6a9aa542d867fec12f67e2d01db85e70af38fb24b14 +size 95540 diff --git a/raw/rel-18/23_series/23700-71/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/raw/rel-18/23_series/23700-71/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57ebe78c9541086041723977b24d57028ab6ec65 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b2b543ce58a8353f8339991dde1964c6cb4efb8ed4a9a5c78df061a5769b1ef +size 107051 diff --git a/raw/rel-18/23_series/23700-71/91aa06b0972f24b4889588fa0e3a331a_img.jpg b/raw/rel-18/23_series/23700-71/91aa06b0972f24b4889588fa0e3a331a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3970443973a539e6918a43ae6ab837ed5a7eb8f3 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/91aa06b0972f24b4889588fa0e3a331a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10f3fa9c73c84ebc9e79b28a2cb73465eef8579ab3ded92acabb7763f379bd66 +size 87501 diff --git a/raw/rel-18/23_series/23700-71/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/raw/rel-18/23_series/23700-71/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e41592f85b2bfcf2bbe71b3517d434c1b09ab881 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f42c44c1ffbed5d044d0d75275f1ca7d96bdb815883c6ec3f76122365ce9ae6e +size 63224 diff --git a/raw/rel-18/23_series/23700-71/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/raw/rel-18/23_series/23700-71/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9970bc168d665e0c86f019fbc1c02da0b5d4ec06 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c97c9c9cc27c986dd5f94574c14592112dc2728163ca6b33a69e1ab2a2db4e88 +size 93782 diff --git a/raw/rel-18/23_series/23700-71/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/raw/rel-18/23_series/23700-71/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94fc7d711db84eb1210a73dbf7e32a8e63b7f057 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04415c7fa3ea800b8a7e998b82a9e828fd06fbbe9decd7f133d3045485b87c69 +size 38221 diff --git a/raw/rel-18/23_series/23700-71/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg b/raw/rel-18/23_series/23700-71/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29969555178fbf3c5492fdc131e0415ca25d6fdf --- /dev/null +++ b/raw/rel-18/23_series/23700-71/9e5d66cdb5112ad5cab89552b126e4b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4180360fbbe3b9950a634f7436b2105d0475deafecf8de25c4f37e3ef057574 +size 50678 diff --git a/raw/rel-18/23_series/23700-71/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/23_series/23700-71/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38a12a4c874e30d598cffc76ba390c9664b071e8 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6100db2514c9d1eda15f0984922399f70d4747cc65eb4cab39bf3e405bb7da37 +size 34213 diff --git a/raw/rel-18/23_series/23700-71/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/raw/rel-18/23_series/23700-71/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6d81f6f0f7a9a5ee2d06bca38671d45db313c8b --- /dev/null +++ b/raw/rel-18/23_series/23700-71/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48239f6d75770e4a762f7632db3e372c7705b5f949dceb3a100fb4bd8000b1a2 +size 122255 diff --git a/raw/rel-18/23_series/23700-71/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/raw/rel-18/23_series/23700-71/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9824ab480d1248d23d9b0ea46c9bb4e1c3f4531a --- /dev/null +++ b/raw/rel-18/23_series/23700-71/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f06ce7595aa5aa5d9e7c26ae08d746bfdc7fcfa3a5079855f077db9b4bd06fe +size 201718 diff --git a/raw/rel-18/23_series/23700-71/a9159a006d67a834a7b1a771c18191cc_img.jpg b/raw/rel-18/23_series/23700-71/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6732317ec223c321f6a39d237baf77d135ccfd86 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1988aaac57be59c7520477896ba8216bf440b833409794209abf0e42253607a0 +size 95283 diff --git a/raw/rel-18/23_series/23700-71/aa22da43c463563d3d0035722bd79449_img.jpg b/raw/rel-18/23_series/23700-71/aa22da43c463563d3d0035722bd79449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04761237684789085aaaaf6d0f4aa8d031798c53 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/aa22da43c463563d3d0035722bd79449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e7fecfa224b1aecd19fb56341e5d579fe23a1f1eed90a7453256760638836c2 +size 73012 diff --git a/raw/rel-18/23_series/23700-71/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/raw/rel-18/23_series/23700-71/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a9f611c184aba81b6bb9eb228c2d219bffe0dd4 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f3c2ec8fd11cbbf57b071da3e1620b67df47182f2b42a1fda6ca3e497472ad1 +size 26435 diff --git a/raw/rel-18/23_series/23700-71/af90aabfe3c8c65617da060d82bf99c5_img.jpg b/raw/rel-18/23_series/23700-71/af90aabfe3c8c65617da060d82bf99c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..823645866c622ceeee0bbeb48e6375ac5bd42ccb --- /dev/null +++ b/raw/rel-18/23_series/23700-71/af90aabfe3c8c65617da060d82bf99c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8708a2de511847f167a7d9538d796179c33155436a11e44862eafb79ac3b17b5 +size 69358 diff --git a/raw/rel-18/23_series/23700-71/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/raw/rel-18/23_series/23700-71/b06a4c871dfd0ce034cf801519d0039a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db350ec9a88283b671814443ea18f61a7b2fd9c7 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/b06a4c871dfd0ce034cf801519d0039a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ca84f4e8e08926a2988579e1fe1c1996077c1f306cb8139face3609fe9c50b8 +size 60928 diff --git a/raw/rel-18/23_series/23700-71/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/raw/rel-18/23_series/23700-71/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39fda35ebca46e0f47afded00ab9da742b0a6bd7 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f916eed98daabf591438f16f9e7a4969c7805b236b655ba0d0bee4c8f10a023 +size 101107 diff --git a/raw/rel-18/23_series/23700-71/b49477e8f148b5ef044a2fd5a43528f6_img.jpg b/raw/rel-18/23_series/23700-71/b49477e8f148b5ef044a2fd5a43528f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2131db509c148cc85348b27c2bd81960a2ccbf1 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/b49477e8f148b5ef044a2fd5a43528f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:014cacf913bbe62919dfbe81a23485943e2e9d74ec5d5e553cd7f7becefe1e28 +size 70161 diff --git a/raw/rel-18/23_series/23700-71/b50f38be091844d58b11e3d47bc71e73_img.jpg b/raw/rel-18/23_series/23700-71/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e926603a397632ef320b55d6df2dae4c42f0edc1 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53bb1e8d7323a8ea274d2b69f8e3f6c48b2c660aa97dbe499cf34d608046b33f +size 49243 diff --git a/raw/rel-18/23_series/23700-71/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/raw/rel-18/23_series/23700-71/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c5d28272abb8e3042a62935b48596cdbb26040c --- /dev/null +++ b/raw/rel-18/23_series/23700-71/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3157993ceb692eae35fdf0757e8a91b6910d83da4d46ae74462854217b2072f +size 156780 diff --git a/raw/rel-18/23_series/23700-71/b9d5785720b6edd0917019f211469dde_img.jpg b/raw/rel-18/23_series/23700-71/b9d5785720b6edd0917019f211469dde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13f4f46b822b1ccf0ff2c611df42dd5940740085 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/b9d5785720b6edd0917019f211469dde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10e228278bc0f94cf2f4ad5f703deebf381ad05bbe417a6ff8fe0f6675f62ebc +size 188604 diff --git a/raw/rel-18/23_series/23700-71/bc6f20871b4f01c61470306c304fc9fe_img.jpg b/raw/rel-18/23_series/23700-71/bc6f20871b4f01c61470306c304fc9fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7891b80ec1767a2cc37ce40f16c4e2500192d846 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/bc6f20871b4f01c61470306c304fc9fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9592ee8b60f37c5fee0f20926a222b2a9ba4848a58419f8ff2ac8115f3cf504 +size 95577 diff --git a/raw/rel-18/23_series/23700-71/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/raw/rel-18/23_series/23700-71/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..816c23395029c28f3e5f5c9cc7a780302ac44f96 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe8b7c4aef50f5ea4151480c58f9979a1916aae5efc59740c23f399536bd8d6a +size 52370 diff --git a/raw/rel-18/23_series/23700-71/c07e21a8d65991db04263322f859c94f_img.jpg b/raw/rel-18/23_series/23700-71/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0297aabe8e812dd48d148a73a16250b9129f3635 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95bd1a16c49a54f4ed703d2d97eaf991444dbd2c5ca294d7d0282d09eab3c1cc +size 91002 diff --git a/raw/rel-18/23_series/23700-71/c85b57b2414f341860dfc338e1cf2509_img.jpg b/raw/rel-18/23_series/23700-71/c85b57b2414f341860dfc338e1cf2509_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..facfdf514c8240e4decc8c3c5a918a1bf7fcbf51 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/c85b57b2414f341860dfc338e1cf2509_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b525117e9a9728e2f33b2b71e41ae87059bb7c3dc25505a6a509f45ee7a8ca5 +size 47625 diff --git a/raw/rel-18/23_series/23700-71/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/raw/rel-18/23_series/23700-71/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1f2d285fe79b41f9953126372933cc33aaa269d --- /dev/null +++ b/raw/rel-18/23_series/23700-71/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b0f99a8060c7c04d646a8ba3b1752af9608365f01837d8368ba2e76dd97cd8e +size 45299 diff --git a/raw/rel-18/23_series/23700-71/cdd0f1dd36631f2c4b17d7ca0f174d80_img.jpg b/raw/rel-18/23_series/23700-71/cdd0f1dd36631f2c4b17d7ca0f174d80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e36f1441c8856a1e7089a6b57e00b0d3d301e60a --- /dev/null +++ b/raw/rel-18/23_series/23700-71/cdd0f1dd36631f2c4b17d7ca0f174d80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56c40c4e43c8c5bfd51e74394cdba0f7ed9ca614b580491d02c04f1f96ca76da +size 41777 diff --git a/raw/rel-18/23_series/23700-71/ceb9a4217df4b6e301712b3b88b09c69_img.jpg b/raw/rel-18/23_series/23700-71/ceb9a4217df4b6e301712b3b88b09c69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87e5be431683dfa50b28a59085e1fee64286846f --- /dev/null +++ b/raw/rel-18/23_series/23700-71/ceb9a4217df4b6e301712b3b88b09c69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:973bc880df0cd8182619a655c283729a829557935bfc5a08c1f4055fefd98c81 +size 218499 diff --git a/raw/rel-18/23_series/23700-71/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg b/raw/rel-18/23_series/23700-71/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39fda35ebca46e0f47afded00ab9da742b0a6bd7 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f916eed98daabf591438f16f9e7a4969c7805b236b655ba0d0bee4c8f10a023 +size 101107 diff --git a/raw/rel-18/23_series/23700-71/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/raw/rel-18/23_series/23700-71/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..675f01393941ba269e7c7f5f4b6e9af7ac05c58c --- /dev/null +++ b/raw/rel-18/23_series/23700-71/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:664753ac4c4cee0f3ea85f0ca602f9ef12a3bd7d93b54b611c45a2766a47ec0c +size 59715 diff --git a/raw/rel-18/23_series/23700-71/e26bb66586e464339df27951d5c9355e_img.jpg b/raw/rel-18/23_series/23700-71/e26bb66586e464339df27951d5c9355e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0136ee1106b3f27f8465c8357baf43ac29201a3 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/e26bb66586e464339df27951d5c9355e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51e248be81570bdc3d5820c5411b0757857657fe42ebc13db14bd1fdec9ebdfb +size 66647 diff --git a/raw/rel-18/23_series/23700-71/e417ae35ab07134888be901c201d54cd_img.jpg b/raw/rel-18/23_series/23700-71/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..269272c7f186b977d06c16f9a0a56ccd9830d2c9 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c5f4d3a84104e1ce8175e4410219374ee988702e76496e636d841446862a21b +size 24547 diff --git a/raw/rel-18/23_series/23700-71/f142b022cfc716cd967297f027efe647_img.jpg b/raw/rel-18/23_series/23700-71/f142b022cfc716cd967297f027efe647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73caadf13f5f51da2a4d406c03ac729e22e598af --- /dev/null +++ b/raw/rel-18/23_series/23700-71/f142b022cfc716cd967297f027efe647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95e28ab35131a4235578a8e2b409430dc1c7fd31527f9152c983b3c46c3fd6d0 +size 81667 diff --git a/raw/rel-18/23_series/23700-71/f5698523df298c80a0c6b5d4ca657993_img.jpg b/raw/rel-18/23_series/23700-71/f5698523df298c80a0c6b5d4ca657993_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78d9fd4fd01b69c11585da97d9a66b1257eb53e3 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/f5698523df298c80a0c6b5d4ca657993_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7c0ccf088e9be412e97d945170deb5c4fd5290b520b9b4ffb17ce46c298223f +size 133648 diff --git a/raw/rel-18/23_series/23700-71/f97535cdaa4fe017f4659512f4f78028_img.jpg b/raw/rel-18/23_series/23700-71/f97535cdaa4fe017f4659512f4f78028_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb07a18f09e56ffbcda43394e3f266e77870596d --- /dev/null +++ b/raw/rel-18/23_series/23700-71/f97535cdaa4fe017f4659512f4f78028_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9331db1126c14254b8bbe44f8a167fdcbea6fda989413bf1abe18a04da330b4 +size 103714 diff --git a/raw/rel-18/23_series/23700-71/fcc757566216206ceddbd6c775e8db02_img.jpg b/raw/rel-18/23_series/23700-71/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac0530f18a86cf9f48956cb6abc57a9468d7cf4a --- /dev/null +++ b/raw/rel-18/23_series/23700-71/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1ef43811ac5b3e8380d00b5d07f1f9fe8630a353855b49b9da9960ef6466b0f +size 38775 diff --git a/raw/rel-18/23_series/23700-71/ff87509cc2b267501d910a2d9f9054ac_img.jpg b/raw/rel-18/23_series/23700-71/ff87509cc2b267501d910a2d9f9054ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1ace046d93895799feb54f6e75ad6cf9f593db7 --- /dev/null +++ b/raw/rel-18/23_series/23700-71/ff87509cc2b267501d910a2d9f9054ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db2993f310ea91fa55292f568c746082765715e251a53e1dcdf90c64fdc5dfa9 +size 28333 diff --git a/raw/rel-18/23_series/23700-76/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/raw/rel-18/23_series/23700-76/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2a406e944cf6e1aae3540f96a54a74c5f179440 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ebaf16245ad4f4d4c1625d181d8a7e5bf19a9af42436bd22c6ece65a77cc9a5 +size 92348 diff --git a/raw/rel-18/23_series/23700-76/26d664119ad25250780f554633444e54_img.jpg b/raw/rel-18/23_series/23700-76/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c80da76acba0bfa56fd0c287be786964caeaa81 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cbca9c654d3d81d87a986880b82cbdf4617f9beb21e39b0ee1f8b98dd67af7c +size 124768 diff --git a/raw/rel-18/23_series/23700-76/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/raw/rel-18/23_series/23700-76/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..993833cecba0348d1a1f1d9b05bdc8d3d3e0f9b9 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11b69da3c9708dbfd5a1e97b233570aea563ae3c541c3cb9f69b871daf097021 +size 94719 diff --git a/raw/rel-18/23_series/23700-76/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-76/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de42fb67ec097cbcdd9c62c859a7e98395f2c0c6 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:227d42b071c444e8931ca906dc636428103614a0871a1e8195065d9facdf5517 +size 9569 diff --git a/raw/rel-18/23_series/23700-76/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-76/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462c222da54d9dbbec7cdc4e21c34c9df3967047 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6a44cef4530e30d221f63982b4437b8835871f9cdccae6f0e1a94e76217752c +size 5657 diff --git a/raw/rel-18/23_series/23700-76/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/raw/rel-18/23_series/23700-76/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1833764a7a23f31de81c9ea736e00cdd915c488 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abd9ea82a90ea52053233e3e23db81b2ca4351fd50ed427ae823421451630d61 +size 120616 diff --git a/raw/rel-18/23_series/23700-76/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/raw/rel-18/23_series/23700-76/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7db64250e97cddb2dd5737e48f3e3f3f749e0a9 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dac9eacc1f4766ec21e1635ac34deed0c6c10fd78167909953d9b1da38c01f06 +size 119114 diff --git a/raw/rel-18/23_series/23700-76/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/raw/rel-18/23_series/23700-76/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f78c98b972da82d8bc466afdeb0ec81ac8c37528 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50cc55ae4d04fe8a32c2abc77c774c9ef27538acdb7d5a24b7cc7ee16fe173ca +size 118816 diff --git a/raw/rel-18/23_series/23700-76/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/23_series/23700-76/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c96ae9cc03679cca977fb71f0de65b0d3821bdbf --- /dev/null +++ b/raw/rel-18/23_series/23700-76/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b345fe7a14a83cd846cf5c37815885eab15f4eaa706a80b00ce0b0b22a367e29 +size 105191 diff --git a/raw/rel-18/23_series/23700-76/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/23_series/23700-76/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a89ec2a8f01277fb39af2dc7b6c1c55849a9bc9 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a65c3dc36e0af270f262cc1aaa09d2228b24a6c336625fd956f567deacb989b5 +size 86673 diff --git a/raw/rel-18/23_series/23700-76/e90987faabad6a6665cd8ed1151dc474_img.jpg b/raw/rel-18/23_series/23700-76/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8094b3f0567d88400fa793e467e92f45ffdf2b4 --- /dev/null +++ b/raw/rel-18/23_series/23700-76/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44a7384b67936299dfd275d68bb915ec31adb522c0d77b25b937a3f9f804cde5 +size 61801 diff --git a/raw/rel-18/23_series/23700-78/0b452c5334567cbdc22ee9817e1246f5_img.jpg b/raw/rel-18/23_series/23700-78/0b452c5334567cbdc22ee9817e1246f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d311fa7518e5224151bd2df987628d48a7e4ce6a --- /dev/null +++ b/raw/rel-18/23_series/23700-78/0b452c5334567cbdc22ee9817e1246f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c644319f89d85ad3208ba403259d65d570d6eee175e44f4f0c5f9d741cc83022 +size 20634 diff --git a/raw/rel-18/23_series/23700-78/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg b/raw/rel-18/23_series/23700-78/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5fa4ceeeb2f253475b2dd1682c52a42fd5c658f --- /dev/null +++ b/raw/rel-18/23_series/23700-78/0c88b98a59dd5d549fed7b13c0ca6536_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a4207d6567e6ede7bf93439a12e25a2346141c1e6070c8277ddbcb062955cc0 +size 51923 diff --git a/raw/rel-18/23_series/23700-78/187d05bf7ead21e1394b61320d8b3632_img.jpg b/raw/rel-18/23_series/23700-78/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58718337dc1f9f930e0b78883c332b816195de51 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f79ee0d27c09313dbf442a8b76ddaba78563fcb5ad0b2e939b7567d56d41c599 +size 88477 diff --git a/raw/rel-18/23_series/23700-78/1ad662a678c4f002de911d403f00de8e_img.jpg b/raw/rel-18/23_series/23700-78/1ad662a678c4f002de911d403f00de8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9cc414d54ce78fbd6d7c5d3fc98438cd8159b27 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/1ad662a678c4f002de911d403f00de8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:938bd1c65c3a26404246eacd88c584ce9e97ad9160b845fb1e587a0ae7592e63 +size 40916 diff --git a/raw/rel-18/23_series/23700-78/1ca688982d625c3b8a8e382b675de466_img.jpg b/raw/rel-18/23_series/23700-78/1ca688982d625c3b8a8e382b675de466_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b0e1185884c4720dd13a8b9b27a309865bbb8e8 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/1ca688982d625c3b8a8e382b675de466_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06c0721b5710797db37bda5faecb61e6155e7ed9207edddbe9bbabbe292a846b +size 55157 diff --git a/raw/rel-18/23_series/23700-78/1e56c223f51992d193febf7a161af7be_img.jpg b/raw/rel-18/23_series/23700-78/1e56c223f51992d193febf7a161af7be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcc9b7b30d2ba40b5b980561a226736092cab492 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/1e56c223f51992d193febf7a161af7be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0294d940c769249e036b2467cd8f1c62b67ed2b2b8b28035005e91ef481f07d +size 33318 diff --git a/raw/rel-18/23_series/23700-78/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/raw/rel-18/23_series/23700-78/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c879207292a288eebd27b5461f06dbe72565d9d --- /dev/null +++ b/raw/rel-18/23_series/23700-78/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd877dd20eac15f0811bc5c9d56a2641f61a1aedd3de2b682c2d84a366751784 +size 30218 diff --git a/raw/rel-18/23_series/23700-78/38a51baf4d5b8857d162e5d9a0645269_img.jpg b/raw/rel-18/23_series/23700-78/38a51baf4d5b8857d162e5d9a0645269_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3b2732b9bbc00533b94588c3b52121198780185 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/38a51baf4d5b8857d162e5d9a0645269_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:837ba373c31c489ac51808a2fc9012a8981f1afb72b08b3bf7b294cce7cef9fb +size 128286 diff --git a/raw/rel-18/23_series/23700-78/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/raw/rel-18/23_series/23700-78/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..268d2726e2e2caab145ac0754cdae716ac4f243e --- /dev/null +++ b/raw/rel-18/23_series/23700-78/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d1fd0c5ceaf6019b3c6f47ae31e965e4f41e07b00a1271b0d70994d1886d211 +size 39614 diff --git a/raw/rel-18/23_series/23700-78/45578bd3ed11d45af63ce00e28bab2f8_img.jpg b/raw/rel-18/23_series/23700-78/45578bd3ed11d45af63ce00e28bab2f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..587617e0fdb394473f0bb5b278278bb3176a956b --- /dev/null +++ b/raw/rel-18/23_series/23700-78/45578bd3ed11d45af63ce00e28bab2f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e28d76aabe761ffc2baf652550d66047917352971965eb1f49109aa576fd708 +size 82396 diff --git a/raw/rel-18/23_series/23700-78/474a819357587e34949a3e110ff19b30_img.jpg b/raw/rel-18/23_series/23700-78/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f46f077cff6c9a0d619ba58acffc58042e32aada --- /dev/null +++ b/raw/rel-18/23_series/23700-78/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c86e40b31727e5cc7c8b7f9c7aadd7eb6dcb4a7859179612d9fe8c5c0e39d97 +size 76234 diff --git a/raw/rel-18/23_series/23700-78/5801c19431e76330430e92a598cc7a16_img.jpg b/raw/rel-18/23_series/23700-78/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d8c733006c93a0a4c5fe2d091c6f55301307da6 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:448ef8bd4fc115c8726170f580be2c115dc074f756f58c2b603947f271d945b9 +size 77407 diff --git a/raw/rel-18/23_series/23700-78/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-78/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0384b52849c0b8bdf9ab09c34bbac6c933420758 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b188f95f6516c6d1b8fd12682bd9831c73daeed1330fad3564886d68ebcd2bca +size 9593 diff --git a/raw/rel-18/23_series/23700-78/6031b46d356ee24f96bfe37ee2cb7616_img.jpg b/raw/rel-18/23_series/23700-78/6031b46d356ee24f96bfe37ee2cb7616_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffc070d489394706899876c003582c30aef872c6 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/6031b46d356ee24f96bfe37ee2cb7616_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3dd21be80df18d096aa08d818b89998ca8c6d3936f164c7cbd25fd1e7169222 +size 77863 diff --git a/raw/rel-18/23_series/23700-78/63a2519518616620ef0e53d98b923c05_img.jpg b/raw/rel-18/23_series/23700-78/63a2519518616620ef0e53d98b923c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bb9a574fa0cbb0269e1c5827b22bbe91272066a --- /dev/null +++ b/raw/rel-18/23_series/23700-78/63a2519518616620ef0e53d98b923c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4b18086099a19e97e3b253bdc94ec5e76d490fdca62835c45d5ea23f4f6a8fb +size 31450 diff --git a/raw/rel-18/23_series/23700-78/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-78/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462c222da54d9dbbec7cdc4e21c34c9df3967047 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6a44cef4530e30d221f63982b4437b8835871f9cdccae6f0e1a94e76217752c +size 5657 diff --git a/raw/rel-18/23_series/23700-78/71b0a68b4dd64961465d2b0e790538de_img.jpg b/raw/rel-18/23_series/23700-78/71b0a68b4dd64961465d2b0e790538de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1513b9ec645dcaf629fce67a626f304ded37303a --- /dev/null +++ b/raw/rel-18/23_series/23700-78/71b0a68b4dd64961465d2b0e790538de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22c86639f739038f03ecb6b5d0dc0e3e0452ecbe049189417d2768e2ffcb72cc +size 66526 diff --git a/raw/rel-18/23_series/23700-78/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/raw/rel-18/23_series/23700-78/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cdc275453ffa204e7b47198e96d4e9400950f24 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0374c04893aed0d18b31d13e3b17896ee2b1df566c136925c1a6f3a0ea74a121 +size 68163 diff --git a/raw/rel-18/23_series/23700-78/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/23_series/23700-78/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e75f3e7508d3cb12cf855555d74794f717812946 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a2876ef3c6646a123b5204ef64eb63cae68debce2264c128fa56f2c9bd8742a +size 66358 diff --git a/raw/rel-18/23_series/23700-78/86692d82da6655813b5acf58a767a38c_img.jpg b/raw/rel-18/23_series/23700-78/86692d82da6655813b5acf58a767a38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..813362a4d0b5d8296e25005c019c60053537179b --- /dev/null +++ b/raw/rel-18/23_series/23700-78/86692d82da6655813b5acf58a767a38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:801efafcd6016b21a58fab0e95340a82dc39c35531a4f53a852eabb3282b5920 +size 25032 diff --git a/raw/rel-18/23_series/23700-78/8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg b/raw/rel-18/23_series/23700-78/8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..481312a5414c01868dbd406e7400bb34d3b63594 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16cf88bdd72e491972891303141ea8049ae6046c07f35ce7cda623b302c81d3a +size 51986 diff --git a/raw/rel-18/23_series/23700-78/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/raw/rel-18/23_series/23700-78/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..376fc850b5a69f7efc12c98256d2fbc9e3480088 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7adef37e16fb65514ab0fd804d61e554a609b23815e5e91db919d7d0573e6fb0 +size 39569 diff --git a/raw/rel-18/23_series/23700-78/9b62a616c7a1097c5da57f001ab6dd64_img.jpg b/raw/rel-18/23_series/23700-78/9b62a616c7a1097c5da57f001ab6dd64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..979eaa0c527a7c4190078a44ddca6b0423655d2f --- /dev/null +++ b/raw/rel-18/23_series/23700-78/9b62a616c7a1097c5da57f001ab6dd64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:572e932d345585af87fe4def0af0e27bfcbb345cf7efe091273d8fe452a79677 +size 63469 diff --git a/raw/rel-18/23_series/23700-78/9b686adccf125267a013fa25721231a3_img.jpg b/raw/rel-18/23_series/23700-78/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18b16fb13f3a8e9648bddd47d097b33f2fbfa333 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfbd9fe4b79436e460cb49a7141b0de37fbfb98353fb3bc31ffd291fe7a743a7 +size 36286 diff --git a/raw/rel-18/23_series/23700-78/9cd7ec4a653f07d02def283cb6f2309e_img.jpg b/raw/rel-18/23_series/23700-78/9cd7ec4a653f07d02def283cb6f2309e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c0d7c1bafa379bdfc4e658d9784c11c8b8eb7d3 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/9cd7ec4a653f07d02def283cb6f2309e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8949f6a7760fbf09cc3226f50b5b12af331703d4a580aef363b67df75aa27bcf +size 64724 diff --git a/raw/rel-18/23_series/23700-78/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/raw/rel-18/23_series/23700-78/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a62ffb7846caffa832699499bc95bcae94332641 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe06ca9f45bd0d81fdb7a90de6a15861d9002cf22026a0815afcd4dd01fd6b72 +size 33298 diff --git a/raw/rel-18/23_series/23700-78/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/raw/rel-18/23_series/23700-78/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ce8cba84c76898882fdbe0792549ec85ff11732 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec35e8bbcc8712a730e5ac7ecc2fa8b9a274becd5b1065189ef853a185877116 +size 62002 diff --git a/raw/rel-18/23_series/23700-78/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/raw/rel-18/23_series/23700-78/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a9a900d1bf3982f933c26f31f9a73c3fafc7667 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d734cd3187a470b11284a9df13046e890be0b7026749f1a6a7f591a0fd9cc86 +size 31995 diff --git a/raw/rel-18/23_series/23700-78/a78db21022e0687c18d97ed547dd7ecb_img.jpg b/raw/rel-18/23_series/23700-78/a78db21022e0687c18d97ed547dd7ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88e29c73dda1d0fccea1b3bb3a585e2416529b89 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/a78db21022e0687c18d97ed547dd7ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b4176cdc5265d0c232ba0541ce25d825a439fe792a5cf0966a9c0eab0f06586 +size 77458 diff --git a/raw/rel-18/23_series/23700-78/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg b/raw/rel-18/23_series/23700-78/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38c45a7ba7c9926a3dc5f788258741941eef5da8 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/ae0dd5533e0b7fd2db452b5e2fdf8e5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:269e3967c3b96667eae8f53a6c488e0ac760ead02ad33a0c46c5383f95bbf587 +size 56670 diff --git a/raw/rel-18/23_series/23700-78/b2ddf2a678bd20b1b491023eb1db6458_img.jpg b/raw/rel-18/23_series/23700-78/b2ddf2a678bd20b1b491023eb1db6458_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8549452ceabf38e165d753ba26b566fa7f03cd4f --- /dev/null +++ b/raw/rel-18/23_series/23700-78/b2ddf2a678bd20b1b491023eb1db6458_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:356f4d5bd4996e966157e69e31794889fe462c305819749a4a4b55bf759e7ddc +size 42547 diff --git a/raw/rel-18/23_series/23700-78/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/raw/rel-18/23_series/23700-78/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfd0c302214b8f174dc7b3be66cb9db349be8748 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d7eecaadfadcc0a3da2aa642f034727f4d6a5fa829e025bcf2e1e91450bfaf9 +size 32322 diff --git a/raw/rel-18/23_series/23700-78/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/raw/rel-18/23_series/23700-78/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9d2bce1cc157ca30f9c1a2c026c9ea3e2b5c856 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1675cbfb5a6a5665116875939752318c4f77bd6be22be20bcaec6505762685c0 +size 13909 diff --git a/raw/rel-18/23_series/23700-78/b5335262987c819d7f71ce40f99cb71b_img.jpg b/raw/rel-18/23_series/23700-78/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47b45fbb9e3ab66daf5e6a25cf5c1d3495d9d9c8 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:457f297434c65aa3d9d8d168c17cc967b8f61311c587c00bf20aca7a3f51b12a +size 58494 diff --git a/raw/rel-18/23_series/23700-78/b5987d63203a5fa601921039922ac520_img.jpg b/raw/rel-18/23_series/23700-78/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81173efc833ce28f66ba64690f041bc250ea6a85 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fab245eac7d73957abfdde2ea2ac938985a28b31975a91df9bb2ed75c7b63e7 +size 75719 diff --git a/raw/rel-18/23_series/23700-78/b774dfc5023e15e9c352b97ca25a56d4_img.jpg b/raw/rel-18/23_series/23700-78/b774dfc5023e15e9c352b97ca25a56d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3e73413f149ceafd0a61db00ddfb2249fb25009 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/b774dfc5023e15e9c352b97ca25a56d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6045796a383ed8da85c2197bb427115f74e16773f50ba66ecd03e6ef9bc242aa +size 26426 diff --git a/raw/rel-18/23_series/23700-78/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/raw/rel-18/23_series/23700-78/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8afdfa91b42aa78b42196fd088aa596d76fd2219 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27502648738a4fcf55455bd23a2d93078ff89116eea1a4603d826fe887877246 +size 58036 diff --git a/raw/rel-18/23_series/23700-78/d3b5eac55166fc428a223bba5c46961b_img.jpg b/raw/rel-18/23_series/23700-78/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76df628bcada972b1cd90211784bdbc2567b264a --- /dev/null +++ b/raw/rel-18/23_series/23700-78/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff37347d56d38973603da3bd52df44ffa7c3d34fca66636b1d7451d4ea7dad30 +size 20000 diff --git a/raw/rel-18/23_series/23700-78/d5d5c87be8e612be9d06d406bc894fd5_img.jpg b/raw/rel-18/23_series/23700-78/d5d5c87be8e612be9d06d406bc894fd5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..593fdbe95c41f6745949f76c0183e737c5a9897c --- /dev/null +++ b/raw/rel-18/23_series/23700-78/d5d5c87be8e612be9d06d406bc894fd5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:311e127abc3df4c45a6245fcd88266b763afa1e552792acd18fc94d710760e6f +size 52043 diff --git a/raw/rel-18/23_series/23700-78/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg b/raw/rel-18/23_series/23700-78/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08b2867d7bcc2f3ece42a2e9eaacb36e52102a4c --- /dev/null +++ b/raw/rel-18/23_series/23700-78/ddd86d7df6cf14d68c0faf111c1e8fae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e290be804775996241384130a5ed5ca9e03e6f90a1630a63cfd6bcd241ca18f1 +size 28344 diff --git a/raw/rel-18/23_series/23700-78/e90987faabad6a6665cd8ed1151dc474_img.jpg b/raw/rel-18/23_series/23700-78/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..996315f6fee0e42a8324ee614e209c5ec076af50 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ee302a74b448c79c9d1f00c73baa6cb152768be555e0a1645d9d3bbbed7b60d +size 69375 diff --git a/raw/rel-18/23_series/23700-78/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/raw/rel-18/23_series/23700-78/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d418afde74828b5ef59ece1d0e2b518df2f23977 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a7c3cd69da3cb14dc3427b137ba0102b4d388bf3f8a3f6caf645d5a3d9b1f7f +size 67980 diff --git a/raw/rel-18/23_series/23700-78/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/raw/rel-18/23_series/23700-78/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..867fb575fab1c235665fb3c33eb1f4008b4c0649 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12f3d4afda19f258dfdff2d2389bcee67d0090025973432442f2d5b7aa610bef +size 75722 diff --git a/raw/rel-18/23_series/23700-78/fc0735d325f0ebd9214171975c68a888_img.jpg b/raw/rel-18/23_series/23700-78/fc0735d325f0ebd9214171975c68a888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f0e5501c7ebfc72feb26a0337c71ae82e65a303 --- /dev/null +++ b/raw/rel-18/23_series/23700-78/fc0735d325f0ebd9214171975c68a888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0923ff19afba0e87f4078041ff72684419b68d8f49ec27448a13e244d61f8096 +size 48583 diff --git a/raw/rel-18/23_series/23700-79/14515d82ffeec9475b9add3036ff26ab_img.jpg b/raw/rel-18/23_series/23700-79/14515d82ffeec9475b9add3036ff26ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0aa93b53797ae7a0c0703ea5735075229ba47b7 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/14515d82ffeec9475b9add3036ff26ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfe6ad9663fca1e868451949d46197568d074a4ee28d5c6bdb4f29a846491da3 +size 20346 diff --git a/raw/rel-18/23_series/23700-79/24c9e038a791677ed33100667b64f7e6_img.jpg b/raw/rel-18/23_series/23700-79/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6af90bf9801cbef3e004b7f03f65fe2babe39c4 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f5678dc188fd1ae8c34f62442417143457ba16689b35c0e3f544da23da54f61 +size 40502 diff --git a/raw/rel-18/23_series/23700-79/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/raw/rel-18/23_series/23700-79/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ab9dcd8aa60fb207569b8104f379bc8cea73245 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f58e8b3334654f1deefcb1ccac97057c0f8b887a9596f20ef665ef63ee58e7f +size 43415 diff --git a/raw/rel-18/23_series/23700-79/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/raw/rel-18/23_series/23700-79/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14255c56a39397abbe09cff3f3ab2b41baa88b02 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ffb9c664170fa13c812fde9f58a2d0119be37a821bf30f2a996cb6f2536341f +size 21292 diff --git a/raw/rel-18/23_series/23700-79/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/raw/rel-18/23_series/23700-79/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2be7b24d4ee18b3fc60bdda4ee0c39e3e54f4a5 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ee28d3ede146be2c6c33d3a689541b150951a42cd09635fb61046c5eab4dc37 +size 81621 diff --git a/raw/rel-18/23_series/23700-79/3621e1493d508bd789fec58ba8be9a40_img.jpg b/raw/rel-18/23_series/23700-79/3621e1493d508bd789fec58ba8be9a40_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a4c146485fd590e58b0c5c4e078057050139e19 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/3621e1493d508bd789fec58ba8be9a40_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1556f32a323d927976af26d96974df43cb55ffb4a870a1585c920b62d59c9ad0 +size 47504 diff --git a/raw/rel-18/23_series/23700-79/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-79/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2594cfea1b226b2814c5f030c97219873f0e2c6e --- /dev/null +++ b/raw/rel-18/23_series/23700-79/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:589102486e768558a62dbcb2f794a8baa3a3823a4f33189f6d5c223cc00da503 +size 10067 diff --git a/raw/rel-18/23_series/23700-79/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-79/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c1e52773f68eb6a5d21fc984bf8ff3ab3caeaf1 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a30c52c25bf0670307751237984e3d9ec03014f883813af6649075852613ede6 +size 5603 diff --git a/raw/rel-18/23_series/23700-79/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/raw/rel-18/23_series/23700-79/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18ddb8612d4b5ea930a1c7b2019fae564ed3dfa4 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa27aec028976373e55e1da24e2594dc1e4fb0510b31bfd171fb08137c51da2 +size 94245 diff --git a/raw/rel-18/23_series/23700-79/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/raw/rel-18/23_series/23700-79/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..937dfc29dc9c18911cb657f4521ca7e824f44982 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb00feba932a7add4004c057c0af9e7324d6eb51d3553daabaaebdfae6d566a9 +size 38322 diff --git a/raw/rel-18/23_series/23700-79/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/raw/rel-18/23_series/23700-79/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..659a317af0d6b182c404a4d71f6e840757241daf --- /dev/null +++ b/raw/rel-18/23_series/23700-79/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1755e1771fdc47877d4a430ad6571c28c0cdd9acd4c82eefb0fbd0368b7af560 +size 57025 diff --git a/raw/rel-18/23_series/23700-79/96b0240f56d14453b5da05ec30fd5c6e_img.jpg b/raw/rel-18/23_series/23700-79/96b0240f56d14453b5da05ec30fd5c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43d57bb63a7228a66b05e9b3df52481fa2e05132 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/96b0240f56d14453b5da05ec30fd5c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96cfaaf9cd2d89359bccae942bfd2a5099286e174396d67264aae51fdc8fca5e +size 18600 diff --git a/raw/rel-18/23_series/23700-79/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/raw/rel-18/23_series/23700-79/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..106ffc40ed4cbd15c3b1281ec333c5a211931dc9 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3cd75d000bff28d410fe51f544ca396c2985cacea65ddb9f1e006c55633049b +size 75143 diff --git a/raw/rel-18/23_series/23700-79/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/raw/rel-18/23_series/23700-79/ac31fdfebb9751f7f10416dfe33bc872_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eaccc7e5a43b6f0f41f20a3b9449c499c3cc457b --- /dev/null +++ b/raw/rel-18/23_series/23700-79/ac31fdfebb9751f7f10416dfe33bc872_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85b13617d3fd3b8e32d6cc93da345131619f1d22463f675eefeb0b965a695e2c +size 58627 diff --git a/raw/rel-18/23_series/23700-79/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/raw/rel-18/23_series/23700-79/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52d0ff178cf1d437f52e710927a0c62f92664967 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42895674d5dd6188ee3d9bdc1a426b409feeb5bfe05bd22317c25e81291a05ed +size 61894 diff --git a/raw/rel-18/23_series/23700-79/cdd4dfacab004e9979caed3fffea69e5_img.jpg b/raw/rel-18/23_series/23700-79/cdd4dfacab004e9979caed3fffea69e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85dd126689fdc409643020061bf5372ce2d954a1 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/cdd4dfacab004e9979caed3fffea69e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:814ab9efb09ededd93fdf15c80a8bf8ce581bb57fa4ad88c047eb765606e8cc9 +size 37341 diff --git a/raw/rel-18/23_series/23700-79/d26959f4514c26ca19c3d6f00da85956_img.jpg b/raw/rel-18/23_series/23700-79/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..296423462852cb13722cfb92daac67a638ee79a1 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59f4697d5099beb16a535f32079a3c968a250fc1c87967998272799eb47dc3df +size 47709 diff --git a/raw/rel-18/23_series/23700-79/dd5771673aececa53d42ece89218299d_img.jpg b/raw/rel-18/23_series/23700-79/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cb755f6dc2cda852013e6b28b4071ea7b85d1dc --- /dev/null +++ b/raw/rel-18/23_series/23700-79/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3370530cd17ba1d7f95bd7cd419c4116e8e646582cb8bab5a99f833f0341819f +size 35235 diff --git a/raw/rel-18/23_series/23700-79/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/raw/rel-18/23_series/23700-79/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e4a249772f0ed27b6f9b4bf1fffbb166dda8499 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14d83abd3d96a8f36f119ae42b903147e2f354bb8efd3e983dd96fecbe96572d +size 31246 diff --git a/raw/rel-18/23_series/23700-79/e4a14961bdc9882e296b25f7ae5f9760_img.jpg b/raw/rel-18/23_series/23700-79/e4a14961bdc9882e296b25f7ae5f9760_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86ef9073ccc75e07b32e440e50a60459718b4397 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/e4a14961bdc9882e296b25f7ae5f9760_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de830e326d38b2bc55df91521091afd47c4063cff2cc4dc1da844c56c9edcc6f +size 80898 diff --git a/raw/rel-18/23_series/23700-79/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/raw/rel-18/23_series/23700-79/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f288638d960f8101a18d9e9870c12f0f26555300 --- /dev/null +++ b/raw/rel-18/23_series/23700-79/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ded4908809f9d5a363b998fd954d09aa1e84f2afc1b525873a04dd286a2a638 +size 94661 diff --git a/raw/rel-18/23_series/23700-85/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg b/raw/rel-18/23_series/23700-85/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7be10b4be7270d6c36352b120a4b7c85994b76d2 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/034b4b6b963a7f9c9db99ad61b0e25e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d181285e2497bf34190e38a5972a71e4b257ab141f342289582737fdc9b658c2 +size 52606 diff --git a/raw/rel-18/23_series/23700-85/036ceaf207a7b289ca76e160892eb724_img.jpg b/raw/rel-18/23_series/23700-85/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cbf174608d48d9853eb127719cabb6628858b09 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f49b761322da6ede492638ae14f48fb6e3125de9320c926a83f329f1b5f60a8 +size 62983 diff --git a/raw/rel-18/23_series/23700-85/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/raw/rel-18/23_series/23700-85/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7736b747088c00a7278f08686b81f736eb1b03e8 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ac03e41fd44d8d4d559af83089bdd7cbe8861a69e89676e1c183ca7042822ee +size 46980 diff --git a/raw/rel-18/23_series/23700-85/10781f43062bf3e9601a1e086710556c_img.jpg b/raw/rel-18/23_series/23700-85/10781f43062bf3e9601a1e086710556c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0e90e2f2b0181a034b7b53e79f6f50f0ebc4ea9 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/10781f43062bf3e9601a1e086710556c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f6427f72f0cde8392c654ad9c89c3dc0d5c795c0cefce657c11b8db94ee5e49 +size 85886 diff --git a/raw/rel-18/23_series/23700-85/1593d118ca6d8c78c91eec7f2b8adf47_img.jpg b/raw/rel-18/23_series/23700-85/1593d118ca6d8c78c91eec7f2b8adf47_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0dd421499f499beddbc30213aedc4709fa6836d --- /dev/null +++ b/raw/rel-18/23_series/23700-85/1593d118ca6d8c78c91eec7f2b8adf47_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c04ad1774e0e0c434f4b126874df7ffda68cdb22753156a8a487680dfe0e60d +size 27714 diff --git a/raw/rel-18/23_series/23700-85/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/raw/rel-18/23_series/23700-85/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81b24145ce4ba27fe4a8269fc4b9374b84cfcfc9 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3eb70b8a19a8a4dc4145609541b6229c00b7ca9faada1d38f56f1008c42e4dc +size 97293 diff --git a/raw/rel-18/23_series/23700-85/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/raw/rel-18/23_series/23700-85/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d59dff1089a9db500b90cb202f86711d0c0c4f9 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a823db1efa3209a696e2b6b5eac055b6717b10408e41521aac5969dff442d1cf +size 92804 diff --git a/raw/rel-18/23_series/23700-85/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg b/raw/rel-18/23_series/23700-85/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c73d126660205ffdb6db55a1624ea61196248ca9 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73f98b4c766cfa85df332cfd79cdcd073c40665f09654c59322b41f7dc4ad60d +size 58859 diff --git a/raw/rel-18/23_series/23700-85/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/raw/rel-18/23_series/23700-85/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a850e2c6587c636b55918a0880c7929a7cbd70f --- /dev/null +++ b/raw/rel-18/23_series/23700-85/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c7825cba3e82416fa3af45e01b395c766e8a22fe760d9af6ac171c775a32713 +size 55709 diff --git a/raw/rel-18/23_series/23700-85/2914642fbfe4ae35924bdf4beb189c1f_img.jpg b/raw/rel-18/23_series/23700-85/2914642fbfe4ae35924bdf4beb189c1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc6b9cdce451f095ca9a8bc60c2dff9289f3d500 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/2914642fbfe4ae35924bdf4beb189c1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47940629867080a3cbe8b6e78d92d937bd1cdd4f2cd80b15f449543a31c559a4 +size 59416 diff --git a/raw/rel-18/23_series/23700-85/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg b/raw/rel-18/23_series/23700-85/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1b0be562376aca8307e753eb70411691ae246e2 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6826770373676ac11c9e20ab40a6681e758d7001a272241e3d8598d243bca2a +size 61890 diff --git a/raw/rel-18/23_series/23700-85/3d93290f9e6e9083f27ba5c914fe1e62_img.jpg b/raw/rel-18/23_series/23700-85/3d93290f9e6e9083f27ba5c914fe1e62_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf0d0fe8904725af946f380ca3b737bc8ad75821 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/3d93290f9e6e9083f27ba5c914fe1e62_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbb3637166185f3594ff60f926e9703246602fbddffc91063249efd99058ac2d +size 89715 diff --git a/raw/rel-18/23_series/23700-85/408c4798ea60469e0728a7cbbd598668_img.jpg b/raw/rel-18/23_series/23700-85/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9529328794cade5d39761dd0776783fdf6ae33f --- /dev/null +++ b/raw/rel-18/23_series/23700-85/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b48bdba1099aeec8033c17b6daa1c7f3dbbcdb4d3d1da9449a55dff4dbbd129 +size 40433 diff --git a/raw/rel-18/23_series/23700-85/4390b89fdb95cba102ee1f88e218b07b_img.jpg b/raw/rel-18/23_series/23700-85/4390b89fdb95cba102ee1f88e218b07b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..404ca59ce2be180bb79248684dc3a671c8215fda --- /dev/null +++ b/raw/rel-18/23_series/23700-85/4390b89fdb95cba102ee1f88e218b07b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6bb0477fac2b894604edff887b47fd85dad4f31e8dd3d8072301347c907e42c +size 47011 diff --git a/raw/rel-18/23_series/23700-85/43979979715bb3304389a0cb18f34444_img.jpg b/raw/rel-18/23_series/23700-85/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49627826a772c4767ab4f9a22cc4b0359ecf8c28 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fde4385d94d7f45c3e8e91d85921b3e65dd532e21f729133e54b4fee1b312534 +size 136325 diff --git a/raw/rel-18/23_series/23700-85/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/raw/rel-18/23_series/23700-85/4537891530c9f6f139a2e1ebf544edc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3c83e996fe24158df4fa778bdc8aa9c6deaef01 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/4537891530c9f6f139a2e1ebf544edc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08a73eba565bb402dd271629f886a34800fdbedb18ec44d52d4de2249bec0ac2 +size 54070 diff --git a/raw/rel-18/23_series/23700-85/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/raw/rel-18/23_series/23700-85/458fdbcb4015a4ee90bd84809afc4aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..208d7751efa369191e61fcb20b184c415f675920 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/458fdbcb4015a4ee90bd84809afc4aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2342aa49beaad8505268f3e549473ebb9b0beec44815bfffcceeb370c9eea83 +size 24311 diff --git a/raw/rel-18/23_series/23700-85/4a5c6fefcac9340ea7f9df373873cae9_img.jpg b/raw/rel-18/23_series/23700-85/4a5c6fefcac9340ea7f9df373873cae9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ef302d190918e510d5de345e1c5335bd1ba704b --- /dev/null +++ b/raw/rel-18/23_series/23700-85/4a5c6fefcac9340ea7f9df373873cae9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f7eaee3cc5c7858c15cd0250d191f9f50408862c95470c72ee442c579d666f0 +size 54570 diff --git a/raw/rel-18/23_series/23700-85/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/raw/rel-18/23_series/23700-85/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c58ab2b8a1f27829ab5d4a24689b27f986491d92 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7e3bbc2530a7ddfca4e77ffe8c8aacbd25d156ed32f74bf78780e6c03d3be05 +size 62435 diff --git a/raw/rel-18/23_series/23700-85/523ab7b925beb555f88b2e1e1336974f_img.jpg b/raw/rel-18/23_series/23700-85/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b6bedc7455353ae9f08e9243f12b582bca17b51 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1eda0655d6943c3e0e6752b11659a62b608fd47cdea79bd54044b0ad9ee1239 +size 57749 diff --git a/raw/rel-18/23_series/23700-85/55048d730ad7a041082df5cc76d53219_img.jpg b/raw/rel-18/23_series/23700-85/55048d730ad7a041082df5cc76d53219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f79e893e56ce28f7d82deddf31d2ea84b663ddd --- /dev/null +++ b/raw/rel-18/23_series/23700-85/55048d730ad7a041082df5cc76d53219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d297b8aff376973b84816a0744609ed9c3d7785d4cb501c49e78f3061c915cd7 +size 57744 diff --git a/raw/rel-18/23_series/23700-85/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg b/raw/rel-18/23_series/23700-85/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45738e1d4e24fc642160dcddf899af25d17df0c9 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a09c08543a9296658d93bb5ed616c5fc8b9fe157da0327a59d88d31fbf78cec6 +size 106120 diff --git a/raw/rel-18/23_series/23700-85/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg b/raw/rel-18/23_series/23700-85/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc67d19bc76b9df86c25685497914f1c14d92c53 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e62f03d5d0d175a91305b16aba4e1d6187517802bb1d2b08311103ec5cfc7038 +size 162568 diff --git a/raw/rel-18/23_series/23700-85/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23700-85/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83c38ef7124c1e4838fd3ddadb87637db73f7480 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea3fba0a92435b2a44052ac1285f5649596e5ce91653b71ffd008eab14a5df2b +size 9459 diff --git a/raw/rel-18/23_series/23700-85/6348f4fc8b3848158fcfbe85e26a731d_img.jpg b/raw/rel-18/23_series/23700-85/6348f4fc8b3848158fcfbe85e26a731d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..910bbeb7430eb7b7a77fe6895877d1dd8a7392f3 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/6348f4fc8b3848158fcfbe85e26a731d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b08d7ae87cda1591dee5419cea9e54dbc2a004b158b1fbf14ec3f50e1f37d8c +size 44750 diff --git a/raw/rel-18/23_series/23700-85/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23700-85/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59fca8d0861871c766f44461427ad0bd61be290e --- /dev/null +++ b/raw/rel-18/23_series/23700-85/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95cbf3e34e12c2498563709c995cd4b80420c31caa8c2ab0477755935bce3654 +size 5668 diff --git a/raw/rel-18/23_series/23700-85/64bec4cd45e47e1976245711f702aca2_img.jpg b/raw/rel-18/23_series/23700-85/64bec4cd45e47e1976245711f702aca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0756a272b28150ecda005b1e82470776a1ec2b7d --- /dev/null +++ b/raw/rel-18/23_series/23700-85/64bec4cd45e47e1976245711f702aca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cd49a9fbee2ada5a179f5a78d50e9652738335d68be440eb8c6d8d74c0f3a09 +size 38774 diff --git a/raw/rel-18/23_series/23700-85/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/raw/rel-18/23_series/23700-85/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec5c1775ea8598b2336556c286767fcd61d7e9df --- /dev/null +++ b/raw/rel-18/23_series/23700-85/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:395b7aa023191aa37eeb349539584eb5bfd49f5104d81f8e6ef94267d968f1a7 +size 77603 diff --git a/raw/rel-18/23_series/23700-85/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg b/raw/rel-18/23_series/23700-85/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d66871313d5752e268c67c0cf5ea88a3725e4cd2 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/68ea9310fb829dd6007635a6cd4ea2ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd7c7e5ad1a4dd00ade2cb8caf9f8d9a6db7ce670e47c9ecdb3b4a3ad195add8 +size 51851 diff --git a/raw/rel-18/23_series/23700-85/6984a27b2b89e0995d5216ec29b41d1c_img.jpg b/raw/rel-18/23_series/23700-85/6984a27b2b89e0995d5216ec29b41d1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e109ddf1c00a26e0352cc20f497a03a6b49167e1 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/6984a27b2b89e0995d5216ec29b41d1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c668f43be32d9eac01bc0df9c88a57531315cef1718f99d655bd4921b924bf5 +size 68862 diff --git a/raw/rel-18/23_series/23700-85/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/raw/rel-18/23_series/23700-85/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebf5bb97eb2b1c2ec9bdc7eb3e5a6398d54419dd --- /dev/null +++ b/raw/rel-18/23_series/23700-85/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66d46bb39fd1804976ad90ea95ce32bd24b09161598e32bbf269974bd2031349 +size 80847 diff --git a/raw/rel-18/23_series/23700-85/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/raw/rel-18/23_series/23700-85/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beda27f803eb2e34c6587614be2a808dabccc5ac --- /dev/null +++ b/raw/rel-18/23_series/23700-85/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96a0ae169b9d6576271e1bf14aa7ee7f3fba3ca8252e2d87069537fd277dc2f5 +size 43098 diff --git a/raw/rel-18/23_series/23700-85/6e9d059430baba0c363e33749f68b107_img.jpg b/raw/rel-18/23_series/23700-85/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe5dd830d692a469f955c35d31c9c5f96e3bc446 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aac8645eb084d0926f8d89374bcbe4b4663f80f3b94036b53c0cf1bb699c2d37 +size 31987 diff --git a/raw/rel-18/23_series/23700-85/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/raw/rel-18/23_series/23700-85/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6467cd7fe1f267353d949cafc0f44cb74bbb9cc2 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84bc27a334dde77d30c14e46ff866a2e2bc71e8507b8302b299c62c51228efce +size 104655 diff --git a/raw/rel-18/23_series/23700-85/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/raw/rel-18/23_series/23700-85/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f06746eac6848d4c110f7d3374ade890c377ffd --- /dev/null +++ b/raw/rel-18/23_series/23700-85/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e91e6f30dc4b3c4b7798556be88c1c1ca69854979dcba3bccb68a65d37f73514 +size 96268 diff --git a/raw/rel-18/23_series/23700-85/8307f6b04df072c9332f9987e034272c_img.jpg b/raw/rel-18/23_series/23700-85/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c13bbd8f84e675742e4dba1c6585159fd06c2d5 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a3a7432762d2eb0c113654b3239589685ab70ab579c6c78d00b0c3c668a23e8 +size 91447 diff --git a/raw/rel-18/23_series/23700-85/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg b/raw/rel-18/23_series/23700-85/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9385008b4b00b138d90862e523f2e8440507cad --- /dev/null +++ b/raw/rel-18/23_series/23700-85/8adc21ec44b6c7debe36fed5b1bb044f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d4711fa882a2551cfd55a97199060e57f7a3f5d0d2aa37e62332e2c650c3072 +size 74229 diff --git a/raw/rel-18/23_series/23700-85/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/raw/rel-18/23_series/23700-85/91b12db3c85bbf466ad27eb3665a1b06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61418f6af1d50d0924718d10603fb26b1516a37a --- /dev/null +++ b/raw/rel-18/23_series/23700-85/91b12db3c85bbf466ad27eb3665a1b06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:843f8370667f0efbf0e0bf84c01f5f29c179109af7df1aae161dd7be3e82c990 +size 60901 diff --git a/raw/rel-18/23_series/23700-85/9874e3ac6f14360133f8e1674f79824f_img.jpg b/raw/rel-18/23_series/23700-85/9874e3ac6f14360133f8e1674f79824f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9b84aa04c71bba66fe7ed09cf6555666eba0b93 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/9874e3ac6f14360133f8e1674f79824f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73e542ea3d8bbadeff5ef4e25d0b4088d50ea62fe4fc5b524a5bbbb1e0767270 +size 100455 diff --git a/raw/rel-18/23_series/23700-85/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/raw/rel-18/23_series/23700-85/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29006d32d97ad9bca1e22f32e320b1c6092ee5a8 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba32a8a57aa3c3d3143b7c6819a2b0e5418d8454f2d6c86778330e09d42d24ec +size 60256 diff --git a/raw/rel-18/23_series/23700-85/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/raw/rel-18/23_series/23700-85/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..457aee2e302a96a61fadc38458841d1f426a3459 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:273e7f03d9a3f9c7d432055394fc75bb0b58f4eb05ae62ac8060f6a43b22f259 +size 95684 diff --git a/raw/rel-18/23_series/23700-85/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg b/raw/rel-18/23_series/23700-85/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ecfecf3c2704c0fd4536e379e6faf9be61b4d26 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2feb8acb47d8f7537b5c39bc956ebb550cd4c171968d03c06d41b758274119e +size 75013 diff --git a/raw/rel-18/23_series/23700-85/9eba62b255ea4757497c72582d0fa54e_img.jpg b/raw/rel-18/23_series/23700-85/9eba62b255ea4757497c72582d0fa54e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f7d75adaca2f3f82a5d74d4563c600ffb86928f --- /dev/null +++ b/raw/rel-18/23_series/23700-85/9eba62b255ea4757497c72582d0fa54e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:594df542ff6855f9f7cc98fa20b299424588f6f6453c322e09ce9f21ce4ed61c +size 34628 diff --git a/raw/rel-18/23_series/23700-85/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/raw/rel-18/23_series/23700-85/9f50279046b74a4e66a1a0144c3b1d11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc010c3ce46784bd2b95d90c6fe0aba8f7a6480d --- /dev/null +++ b/raw/rel-18/23_series/23700-85/9f50279046b74a4e66a1a0144c3b1d11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbc9f23c2ec0a7e1b72d04ac23408c06d0e6a9f9f13a08dc76b9b5d40a14cf0b +size 164470 diff --git a/raw/rel-18/23_series/23700-85/9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg b/raw/rel-18/23_series/23700-85/9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f61092b14c1a59d06ef70781b8ad537998ebbcca --- /dev/null +++ b/raw/rel-18/23_series/23700-85/9f9fdebeade37ad92fdd68d6ea9f58ce_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78402f2aa2ffef85f7ab6d4697eaec415d46fbddb73b9564677030bf82f93dc9 +size 39829 diff --git a/raw/rel-18/23_series/23700-85/a166566092dd84196c2ec048ca175290_img.jpg b/raw/rel-18/23_series/23700-85/a166566092dd84196c2ec048ca175290_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eda17554ce266df9cb32c485afc219e24a8d7114 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/a166566092dd84196c2ec048ca175290_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db09964d22b3b997d0e64b1308748deb4d38e6e98effef7f625d46308af998b4 +size 70028 diff --git a/raw/rel-18/23_series/23700-85/a5404b7275b06497eecf9b5883604753_img.jpg b/raw/rel-18/23_series/23700-85/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc72ab2527e4ea86d034d32510575fc454401e65 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bb3dfc99d3e2d8b9bf504baaabc3d7014d9042fe84ad00adce2be6106817308 +size 61440 diff --git a/raw/rel-18/23_series/23700-85/a634891d16b60b21df90a35c2af72c67_img.jpg b/raw/rel-18/23_series/23700-85/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faddbd25c75949e9bfa4ce20110397f1704b6a24 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd1b7ec6a32e6ba14ee0d6a6e2f0b1cee5efce85246165afcc0a4ce4178ada58 +size 84746 diff --git a/raw/rel-18/23_series/23700-85/a70e0adcabc973b01b413b6a141884f3_img.jpg b/raw/rel-18/23_series/23700-85/a70e0adcabc973b01b413b6a141884f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15f669957aefd55d138910481c4a1bda086bae9c --- /dev/null +++ b/raw/rel-18/23_series/23700-85/a70e0adcabc973b01b413b6a141884f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4428d4c2a33c89742049e6620c9d27540c7490ad610ee02eabf1882a043a16f4 +size 55300 diff --git a/raw/rel-18/23_series/23700-85/a9159a006d67a834a7b1a771c18191cc_img.jpg b/raw/rel-18/23_series/23700-85/a9159a006d67a834a7b1a771c18191cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74992caeff1ec50b403feeb624046e9a633ea8d1 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/a9159a006d67a834a7b1a771c18191cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd8c31b48f09a8c11d910f02bc6265a085251a527635e59d405ca254d760e1fa +size 86783 diff --git a/raw/rel-18/23_series/23700-85/a963ca41bde1669b18a4b783616f228b_img.jpg b/raw/rel-18/23_series/23700-85/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f162ee144d81aa676c666519cd82033ab2c000e --- /dev/null +++ b/raw/rel-18/23_series/23700-85/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1e0b1b8c393e815d537f2200f02ced525ed69dbb80f2b93da3e328ba5df0939 +size 132278 diff --git a/raw/rel-18/23_series/23700-85/a97518a839da75f8379c578562b01bc2_img.jpg b/raw/rel-18/23_series/23700-85/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8918ccd803557abd291db5c7555c7e440a28ed86 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fea52ae19c01df5f902790b344999c1cf7d18c82d629c60a4ac152fdc2a18c4 +size 69325 diff --git a/raw/rel-18/23_series/23700-85/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/raw/rel-18/23_series/23700-85/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c804b9834b1bc833ae682c4661af2e7b5d64f1a1 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/aa6e28822419dba9f22129fee66c9c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2445ea67a4234bc1647771fbe61473118fe415a5d809f38490b22167033dc6c9 +size 95392 diff --git a/raw/rel-18/23_series/23700-85/ad555483986d7170a46ce72d164b5bc8_img.jpg b/raw/rel-18/23_series/23700-85/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ef7b2fed1656b5e6af3d52631586ed635794861 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe8a9a9b48bc775f41956d4672e5d695f30f9cab042e68a1fdd67bfc2a1ea17f +size 77378 diff --git a/raw/rel-18/23_series/23700-85/b5335262987c819d7f71ce40f99cb71b_img.jpg b/raw/rel-18/23_series/23700-85/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77610dcf15266a3db266717758533035fb5732c4 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1581758430141dfabb48879cf185f73bf3a7a7f023e28193461682dc4aeb2c1c +size 73981 diff --git a/raw/rel-18/23_series/23700-85/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/raw/rel-18/23_series/23700-85/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a61e97c3b6497bc35a188b1d9c99c78e01c1c99b --- /dev/null +++ b/raw/rel-18/23_series/23700-85/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee1338fdfccbaca33aaafb4d6883378a64c7acfb913391451af2cd74989fc1d2 +size 73800 diff --git a/raw/rel-18/23_series/23700-85/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/raw/rel-18/23_series/23700-85/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0fbadd199a75dedadadd87aecf911d097a8caa6 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50191dcec0f39ae1313792963740843c975647d840e80902856185fd8b0e9589 +size 83007 diff --git a/raw/rel-18/23_series/23700-85/d2417b04116c354deccb25d98a84a0fb_img.jpg b/raw/rel-18/23_series/23700-85/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9600261d57a2a7fe5bb4c2afac58506ffb29e46 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb10206768d0685e1b47448437f8408c1d6fbabc99ec8be31001f368ef2aebad +size 69906 diff --git a/raw/rel-18/23_series/23700-85/dd5771673aececa53d42ece89218299d_img.jpg b/raw/rel-18/23_series/23700-85/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de8bc7f5275082b118470b3ec895e3161b5df082 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f01ff947fb3c99679d3cf4ac2e2ff679162c250f0756ed98ed31d54c1162cf94 +size 38148 diff --git a/raw/rel-18/23_series/23700-85/e05b36c0d46549e681ce6581422c66b2_img.jpg b/raw/rel-18/23_series/23700-85/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b345863df2b02e9a07874908b417bbcee3a4000 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2991aa837c353901aa802e2375920faf81cf4c8273aeb055f3e9cb338511a8e7 +size 66360 diff --git a/raw/rel-18/23_series/23700-85/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/raw/rel-18/23_series/23700-85/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d65061d101efdb1571abc5c9368f914bbf0a7aef --- /dev/null +++ b/raw/rel-18/23_series/23700-85/e90b25c8d90cadc3f76c376701cf27ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0916fe3c4caee4f26bd22c0e70cd6288ffa87f34772e6cc1d142669724a4f51 +size 64710 diff --git a/raw/rel-18/23_series/23700-85/e9b43ac020435f8121e8592f31afdc52_img.jpg b/raw/rel-18/23_series/23700-85/e9b43ac020435f8121e8592f31afdc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07cea0239d7c1a3983f2dccab8ea35c64ed8bc26 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/e9b43ac020435f8121e8592f31afdc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a75d3baaa94dd99a577ac6b6366e7465de89c8ad70091fdd098852a0fc5fbd2 +size 43892 diff --git a/raw/rel-18/23_series/23700-85/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/raw/rel-18/23_series/23700-85/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..705ffa50c4cd29977e7cc11cb282dfed80dfd4db --- /dev/null +++ b/raw/rel-18/23_series/23700-85/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18e58798732ebda765dba9d56d64f744d5b03e36f704959b43b9c286c4b1672c +size 56769 diff --git a/raw/rel-18/23_series/23700-85/f5698523df298c80a0c6b5d4ca657993_img.jpg b/raw/rel-18/23_series/23700-85/f5698523df298c80a0c6b5d4ca657993_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..366c9f413a71d730b40b79dfcbc0390373714a8d --- /dev/null +++ b/raw/rel-18/23_series/23700-85/f5698523df298c80a0c6b5d4ca657993_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c92ec464d7450d8b84feac070511b1e9cf772328134f128c28547c00d422f42 +size 30948 diff --git a/raw/rel-18/23_series/23700-85/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/raw/rel-18/23_series/23700-85/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c8ef1e274297441101df7fe153b1cf32f1b2e3d --- /dev/null +++ b/raw/rel-18/23_series/23700-85/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e31eb61be68f6b88df977421bd90468309892d36957622db9958085b1928ae6d +size 91262 diff --git a/raw/rel-18/23_series/23700-85/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/raw/rel-18/23_series/23700-85/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d7aefea7cf94fa6ebd8b006a4633e3faa4b70b5 --- /dev/null +++ b/raw/rel-18/23_series/23700-85/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f94f2a2ba247fadf88b218918deec13e7a9cedf3503c354a79c2a7c24101436 +size 127882 diff --git a/raw/rel-18/23_series/23700-90/raw.md b/raw/rel-18/23_series/23700-90/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c364ce9972797fd3a77dd9915472d75859ff28b9 --- /dev/null +++ b/raw/rel-18/23_series/23700-90/raw.md @@ -0,0 +1,1740 @@ + + +# 3GPP TR 23.700-90 V18.0.0 (2022-03) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Interconnection and Migration Aspects for Railways; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 +Intpp.org + +## --- ***Copyright Notification*** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# --- Contents + +| | | +|-------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations ..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 8 | +| 4 Scenarios..... | 8 | +| 5 Key issues ..... | 8 | +| 5.1 Key issue 1 - Optimize the connectivity between MC systems ..... | 8 | +| 5.2 Key issue 2 - Functional alias handling ..... | 8 | +| 5.3 Key issue 3 - Group communication between MC systems..... | 8 | +| 5.4 Key issue 4 - Location information with multiple MC systems ..... | 9 | +| 5.5 Key issue 5 - Quick migration towards another MC system..... | 9 | +| 5.6 Key issue 6 - Call forwarding/transfer between MC systems..... | 9 | +| 5.7 Key issue 7 - IP connectivity between MC systems ..... | 9 | +| 5.8 Key issue 8 – Offline-Migration ..... | 10 | +| 6 Architectural requirements..... | 10 | +| 7 Solutions..... | 10 | +| 7.1 Solution on functional architecture enhancements to support location information..... | 10 | +| 7.1.1 General ..... | 10 | +| 7.1.2 Solution description..... | 10 | +| 7.1.2.1 Functional architecture ..... | 10 | +| 7.1.2.2 Reference points ..... | 10 | +| 7.1.3 Solution evaluation ..... | 11 | +| 7.2 Solutions on providing location information ..... | 11 | +| 7.2.1 General ..... | 11 | +| 7.2.2 Solution description..... | 11 | +| 7.2.2.1 Immediate location information requests and reports..... | 11 | +| 7.2.2.2 History location information requests and reports..... | 11 | +| 7.2.2.3 Event triggered location information reports based on subscriptions..... | 11 | +| 7.2.2.4 Configuration of event triggered location information reports..... | 11 | +| 7.2.2.5 Handling of location information subscriptions ..... | 11 | +| 7.2.3 Solution evaluation ..... | 12 | +| 7.3 Private call using functional alias towards a partner MC system ..... | 12 | +| 7.3.1 General ..... | 12 | +| 7.3.2 Solution description..... | 12 | +| 7.3.2.1 Principle ..... | 12 | +| 7.3.2.2 Configuration..... | 12 | +| 7.3.2.3 Messages..... | 13 | +| 7.3.2.4 Procedure ..... | 13 | +| 7.3.3 Solution evaluation ..... | 14 | +| 7.4 Functional alias support for migrated users ..... | 15 | +| 7.4.1 General ..... | 15 | +| 7.4.2 Solution description..... | 15 | +| 7.4.2.1 Principle ..... | 15 | +| 7.4.2.2 Procedure ..... | 15 | +| 7.4.2.3 Configuration..... | 16 | +| 7.4.3 Solution evaluation ..... | 16 | +| 7.5 Migration during an ongoing group communication ..... | 16 | +| 7.5.1 General ..... | 16 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------------------|----| +| 7.5.2 | Solution description..... | 17 | +| 7.5.2.1 | Procedure ..... | 17 | +| 7.5.3 | Solution evaluation ..... | 18 | +| 7.6 | Migration during an ongoing private communication..... | 18 | +| 7.6.1 | General ..... | 18 | +| 7.6.2 | Solution description..... | 18 | +| 7.6.2.1 | Procedure ..... | 18 | +| 7.6.2.2 | Information flows ..... | 19 | +| 7.6.2.2.1 | MCPTT private call suspend request ..... | 19 | +| 7.6.2.2.2 | MCPTT private call suspend response..... | 19 | +| 7.6.2.2.3 | MCPTT private call resume request (MCPTT client to MCPTT server) ..... | 19 | +| 7.6.2.2.3a | MCPTT private call resume request (MCPTT server to MCPTT server)..... | 20 | +| 7.6.2.2.3b | MCPTT private call resume request (MCPTT server to MCPTT client) ..... | 21 | +| 7.6.2.2.4 | MCPTT private call resume response (MCPTT client to MCPTT server)..... | 21 | +| 7.6.2.2.4a | MCPTT private call resume response ..... | 21 | +| 7.6.3 | Solution evaluation ..... | 22 | +| 7.7 | Optimize the connectivity between MC systems ..... | 22 | +| 7.7.1 | General ..... | 22 | +| 7.7.2 | Solution description..... | 22 | +| 7.7.2.1 | Principle ..... | 22 | +| 7.7.2.2 | Procedure ..... | 22 | +| 7.7.2.3 | Configuration ..... | 24 | +| 7.7.2.4 | Information flows ..... | 24 | +| 7.7.2.4.1 | General ..... | 24 | +| 7.7.2.4.2 | Request MC user info..... | 24 | +| 7.7.2.4.3 | Response MC user info ..... | 24 | +| 7.7.3 | Solution evaluation ..... | 24 | +| 7.8 | Private call using functional alias towards a partner MC system ..... | 25 | +| 7.8.1 | General ..... | 25 | +| 7.8.2 | Solution description..... | 25 | +| 7.8.2.1 | Principle ..... | 25 | +| 7.8.2.2 | Functional alias clarification..... | 25 | +| 7.8.2.3 | Functional alias resolution ..... | 26 | +| 7.8.2.3.1 | MCPTT functional alias resolution response ..... | 26 | +| 7.8.2.3.2 | MCPTT functional alias resolution request ..... | 26 | +| 7.8.2.4 | Procedure ..... | 26 | +| 7.8.3 | Solution evaluation ..... | 28 | +| 7.9 | Solution on IP connectivity between MC systems..... | 28 | +| 7.9.1 | General ..... | 28 | +| 7.9.2 | Solution description..... | 28 | +| 7.9.2.1 | Functional model ..... | 28 | +| 7.9.2.2 | Reference points ..... | 29 | +| 7.9.2.3 | Procedures and flows ..... | 29 | +| 7.9.3 | Solution evaluation ..... | 29 | +| 7.10 | Solution on migration without interconnection between two MC systems ..... | 29 | +| 7.10.1 | General ..... | 29 | +| 7.10.2 | Solution description..... | 29 | +| 7.10.3 | Solution evaluation ..... | 30 | +| 7.11 | Private call forwarding between MCPTT systems..... | 30 | +| 7.11.1 | General ..... | 30 | +| 7.11.2 | Solution description..... | 30 | +| 7.11.2.1 | Principle ..... | 30 | +| 7.11.2.2 | Messages ..... | 30 | +| 7.11.2.3 | Procedure ..... | 32 | +| 7.11.2.3.1 | MCPTT private call forwarding with target of the MCPTT private call forwarding in partner MCPTT system ..... | 32 | +| 7.11.2.3.2 | MCPTT private call forwarding with MCPTT private call forwarding occurring in the partner MCPTT system ..... | 34 | +| 7.11.3 | Solution evaluation ..... | 36 | +| 7.12 | Private call transfer between MCPTT systems ..... | 36 | +| 7.12.1 | General ..... | 36 | +| 7.12.2 | Solution description..... | 36 | + +| | | | +|---------------------------------------------------|-------------------------------------------------------------------------------------------------|-----------| +| 7.12.2.1 | Principle ..... | 36 | +| 7.12.2.2 | Impact on information flows..... | 36 | +| 7.12.3.2 | Procedures..... | 37 | +| 7.12.3.2.1 | MCPTT private call announced transfer with target in partner MCPTT system ..... | 37 | +| 7.12.3.2.2 | MCPTT private call announced transfer with transferring MCPTT user in partner MCPTT system..... | 40 | +| 8 | Overall evaluation ..... | 43 | +| 8.1 | Key issue and solution evaluation..... | 43 | +| 8.1.1 | Introduction ..... | 43 | +| 8.1.2 | Results ..... | 43 | +| 9 | Conclusions ..... | 44 | +| Annex A (informative): Change history..... | | 46 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- Introduction + +The work done for interconnection and migration did not fully address the needs for railways, additional work is required. Before starting additional normative stage 2 work on certain aspects, a study is initiated to identify gaps in existing mechanisms on interconnection and on migration and to develop solutions for those gaps. The technical report provides recommendations for solutions which are candidates for normative work. + +# --- 1 Scope + +The present document studies solutions to satisfy interconnection and migration needs for railways. It identifies enhancements to be included in the technical specifications for MCPTT (3GPP TS 23.379 [2]), MCVideo (3GPP TS 23.281 [3]), MCData (3GPP TS 23.282 [4]) and in the common functional architecture (3GPP TS 23.280 [5]) to support mission critical communications. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [3] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2". +- [4] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2". +- [5] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [6] 3GPP TR 23.744: "Study on location enhancements for mission critical services". +- [7] 3GPP TS 33.180: "Security of the Mission Critical (MC) service". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + + + +# --- 4 Scenarios + +NOTE: No scenarios were identified. + +# --- 5 Key issues + +## 5.1 Key issue 1 - Optimize the connectivity between MC systems + +The operation between multiple MC systems becomes for important and so the path of media and signalling needs to be re-considered. Optimisations on media and signalling routing may save transmission resources and may improve the quality of service. + +List of key issues: + +- Study and describe the existing mechanism of routing of media and signalling between MC systems. +- Investigate optimizations and develop solutions to improve media and signalling routing between MC service systems. + +## 5.2 Key issue 2 - Functional alias handling + +The use of functional aliases outside the own home MC system has not been considered by current specifications. Same applies for the use of a functional alias between interconnected MC systems, i.e. between a partner MC system and the home MC system as well as between two partner MC systems. Considerations on functional alias management procedures (activation, deactivation or group binding etc.), which are applied outside the own home MC system, are also missing in current specifications. + +List of key issues: + +- Describe the related procedures and elaborate the configuration needs for the use of functional alias in a partner MC system which was allocated by the home MC system. +- Describe the use of functional alias (allocated by the home MC system) used in multiple partner MC systems. +- Describe functional alias activation and deactivation procedures and configuration needs when the MC service user is migrated into a partner MC system. +- Elaborate how the transfer and the retrieval of functional alias binding with MC service groups is done when using a functional alias over multiple MC systems. + +## 5.3 Key issue 3 - Group communication between MC systems + +Group communications require further considerations when MC service users are spread to multiple MC systems or when MC service users re-locate to another MC system during an ongoing group communication. + +List of key issues: + +- Develop solutions which enable group communications that are spread to multiple MC systems. +- Develop solutions which allow migration to another MC system during an ongoing group communication. +- Elaborate security implications when MC service users are involved that belong to different MC systems. + +## 5.4 Key issue 4 - Location information with multiple MC systems + +The use of location related procedures when involving users of multiple MC service systems are not covered by current specifications. + +List of key issues: + +- Study current location information procedures and configuration data and elaborate its applicability when MC service users operating in multiple MC systems are involved. +- Develop solutions (incl. required configuration data) to support location information management procedures for operation in multiple MC systems. +- Elaborate any security related aspects when location information is exchanged and managed between multiple MC systems. + +## 5.5 Key issue 5 - Quick migration towards another MC system + +For railways there is a need to migrate from one MC system to another MC system (organization) at high speed with no loss of service (regular border crossing scenario). + +List of key issues: + +- Study current migration solutions and investigate possible improvements. +- If required, develop new solutions to support quick migration from one MC system to another MC system. +- Elaborate which configuration data is required to support quick migration. +- Elaborate if there are any security implications to support quick migration. + +## 5.6 Key issue 6 - Call forwarding/transfer between MC systems + +The use of supplementary services between interconnected MC systems, i.e. between a partner MC system and the home MC system as well as between two partner MC systems, has not been specified. + +Solutions are needed to enable call forwarding and call transfer procedures between interconnected MC systems. + +List of key issues: + +- Develop solutions which enable call forwarding to MC service users in a different MC system. +- Develop solutions which enable call transfer involving MC service users in a different MC system. + +## 5.7 Key issue 7 - IP connectivity between MC systems + +IP connectivity related aspects that involve two MC systems needs further investigations. Point-to-point and group standalone transmissions are to be considered as well as scenarios when the MC service user is abroad and uses home breakout or local breakout. + +List of key issues: + +- Investigate and develop solutions for IP connectivity point-to-point transmissions that involves two MC systems (support home and local breakout). + +- Investigate and develop solutions for IP connectivity group standalone transmissions that involves two MC systems (support home and local breakout). + +## 5.8 Key issue 8 – Offline-Migration + +Migration aspects in case there is no interconnection between two MC systems have not been considered by current specifications. Reasons for no interconnection between the MC systems may be, due to regulatory constraints, the use of tactical networks in e.g., remote areas and in the case of connection loss. Where cooperation is wanted, an authorized MC service user still needs to be enabled to obtain service from another MC system, where the primary and the partner MC systems are not interconnected. + +List of key issues: + +- Develop solutions which enable an MC service user to obtain service from another MC system, where there is no interconnection between primary and the partner MC systems. +- Elaborate if there are any security implications, to enable an MC service user to obtain MC services from another MC system, where there is no interconnection between the MC systems. + +# --- 6 Architectural requirements + +NOTE: No architectural requirements were identified. + +# --- 7 Solutions + +## 7.1 Solution on functional architecture enhancements to support location information + +### 7.1.1 General + +This solution addresses the key issue 4 described in clause 5.4 on defining a functional architecture when using multiple interconnected MC systems. + +### 7.1.2 Solution description + +#### 7.1.2.1 Functional architecture + +The in 3GPP TR 23.744 [6] clause 6.14 described functional architecture of interconnected MC systems for the exchange of location information is used to support the following scenarios: + +- a. immediate location information requests and reports; +- b. history location information requests and reports; +- c. event triggered location information reports based on subscriptions; +- d. configuration of event triggered location information reports; and +- e. handling of location information subscriptions, e.g. subscription requests, cancellation of subscriptions. + +#### 7.1.2.2 Reference points + +The in 3GPP TR 23.744 [6] clause 6.14 described reference points between entities of interconnected MC systems for the exchange of location information are used to support following scenarios: + +- a. utilizing the connection of the MC gateway servers; and +- b. utilizing the connection of the Location management servers. + +### 7.1.3 Solution evaluation + +The enhancements of the functional architecture described in 3GPP TR 23.744 [6] clause 6.14 fulfil the need for the exchange of location information in case of interconnection. + +## 7.2 Solutions on providing location information + +### 7.2.1 General + +This solution addresses the key issue 4 described in clause 5.4 on defining the usage of the functional architecture when using multiple interconnected MC systems. + +### 7.2.2 Solution description + +#### 7.2.2.1 Immediate location information requests and reports + +Building on 3GPP TR 23.744 [6] clause 6.15.2.7 as well as clause 6.15.2.8 the functional alias(es) may be included to the described information flows. + +The on-demand request of location information procedure described in 3GPP TR 23.744 [6] clause 6.15.2.9 is utilized. + +#### 7.2.2.2 History location information requests and reports + +Building on 3GPP TS 23.280 [5] clauses 10.9.2.11, 10.9.2.12, 10.9.2.13, 10.9.2.14, 10.9.2.15 as well as clause 10.9.1.16 the functional alias(es) may be included to the described information flows. + +Building on 3GPP TS 23.280 [5] clauses 10.9.3.9.2.2, 10.9.3.9.3.3 as well as clause 10.9.3.9.4.3 additional procedures are needed to cover cases of the interconnected MC systems. + +#### 7.2.2.3 Event triggered location information reports based on subscriptions + +Building on 3GPP TR 23.744 [6] clause 6.15.2.4 the functional alias(es) may be included to the described information flow. + +The event-triggered location information notification procedure described in 3GPP TR 23.744 [6] clause 6.15.2.6 is utilized. + +#### 7.2.2.4 Configuration of event triggered location information reports + +Building on 3GPP TR 23.744 [6] clause 6.15.2.14 as well as clause 6.15.2.15 the functional alias(es) may be included to the described information flows. + +The location reporting temporary configuration procedure described in 3GPP TR 23.744 [6] clause 6.15.2.16 is utilized. + +#### 7.2.2.5 Handling of location information subscriptions + +Building on 3GPP TR 23.744 [6] clauses 6.15.2.2, 6.15.2.3, 6.15.2.11 as well as clause 6.15.2.12 the functional alias(es) may be included to the described information flows. + +The Location information subscription procedure described in 3GPP TR 23.744 [6] clause 6.15.2.5 is utilized. + +The Location information cancel subscription procedure described in 3GPP TR 23.744 [6] clause 6.15.2.13 is utilized. + +### 7.2.3 Solution evaluation + +The following aspects of the key issue 4 - Location information with multiple MC systems is addressed with the above solution: + +- The current available information flows and procedures in 3GPP TR 23.744 [6] and 3GPP TS 23.280 [5] are analysed for interconnected MC systems. Especially 3GPP TR 23.744 [6] is addressing a wide range of information flows and procedures required for the interconnected MC system use case. +- Missing procedures for the exchange of history location information are identified and require further investigation for the explicit need with the interconnected MC system use case. +- The analysed information flows and procedures in 3GPP TR 23.744 [6] and 3GPP TS 23.280 [5] do not show additional security implications for the interconnected MC system use case. + +## 7.3 Private call using functional alias towards a partner MC system + +### 7.3.1 General + +This solution addresses the key issue 2 described in clause 5.2 on functional alias handling. + +The solution provides the possibility for an MCPTT user to initiate a private MCPTT call using a functional alias as target address towards an MCPTT user in a partner MCPTT system. + +### 7.3.2 Solution description + +#### 7.3.2.1 Principle + +Allow the MCPTT server in the primary MC system, to send an MCPTT private call request to an MCPTT server in the partner MC system using a functional alias without incorporating the MCPTT ID of the called party. + +Extend the MCPTT service configuration data so that the MC server in the primary MC system can identify that the functional alias belongs to a partner MC system. This is done by using certain formats for functional aliases belonging to the partner MC system towards the private call request is to be forwarded. + +#### 7.3.2.2 Configuration + +The MCPTT service configuration data is extended to contain the list of MC system identities and corresponding functional alias mask (e.g. \*.sbb.ch) information for all partner MCPTT systems. Based on the functional alias mask configured for all the partner MCPTT systems, the primary MCPTT server can route the request to the proper partner MCPTT system. + +Proposed modifications in 3GPP TS 23.379 [2] Table A.5-2 MCPTT service configuration data (on-network): + +**Table 7.3.2.2-1: MCPTT service configuration data (on network)** + +| | | | | | +|--|-----------------------------------------------------------------------------------------------|---|---|---| +| | List of partner MCPTT systems where system specific configuration applies for interconnection | | | | +| | > MC system identity of partner MCPTT system | N | Y | Y | +| | > Functional alias mask | N | Y | Y | + +NOTE: The use of the same functional alias in multiple MC systems is not supported. + +#### 7.3.2.3 Messages + +The MCPTT private call request between MCPTT servers is modified to allow only using the functional alias as called party address, i.e. the MCPTT ID address is not resolved and not contained by the primary MCPTT server. + +Proposed modifications in 3GPP TS 23.379 [2] Table 10.7.2.1.2-1: MCPTT private call request (MCPTT server to MCPTT server) information elements: + +**Table 7.3.2.3-1: MCPTT private call request (MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|----------------------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID (see NOTE) | O | The MCPTT ID of the called party | +| Functional alias (see NOTE) | O | The functional alias of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Requested priority | O | Priority level requested for the call. | +| Location information | O | Location of the calling party | +| NOTE: At least one identity must be present. | | | + +#### 7.3.2.4 Procedure + +The MCPTT private call setup procedure between MCPTT servers is modified to allow using the functional alias as called party address, i.e. the MCPTT ID address is not resolved by the primary MCPTT system, instead the primary MCPTT server uses the functional alias mask information configured in the MCPTT service configuration data to send the request towards the proper MCPTT system. + +Proposed changes against 3GPP TS 23.379 [2] clause 10.7.2.3.1: Private call setup in automatic commencement mode - MCPTT users in multiple MCPTT systems: + +NOTE: The changes are applicable when using manual commencement mode as well. + +![Sequence diagram illustrating Private call setup in automatic commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT clients and servers across two systems. Steps include registration, call initiation, request routing, authorization, progress indication, notification, response, and media plane establishment.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server 1 + participant MCPTT server 2 + participant MCPTT client 2 + + Note left of MCPTT client 1: MCPTT service provider 1 + Note right of MCPTT client 2: MCPTT service provider 2 + + MCPTT client 1->>MCPTT server 1: 1. MCPTT client 1 registered for MCPTT service + MCPTT client 2->>MCPTT server 2: 1. MCPTT client 2 registered for MCPTT service + MCPTT client 1->>MCPTT server 1: 2. initiate private call + MCPTT client 1->>MCPTT server 1: 3. MCPTT private call request + MCPTT server 1->>MCPTT server 2: 4. Authorize request + MCPTT server 1-->>MCPTT client 1: 5. MCPTT progress indication + MCPTT server 1->>MCPTT server 2: 6. MCPTT private call request + MCPTT server 2->>MCPTT client 2: 7. Authorize request + MCPTT server 2->>MCPTT client 2: 8. MCPTT private call request + MCPTT client 2->>MCPTT server 2: 9. Notify call + MCPTT client 2->>MCPTT server 2: 10. MCPTT private call response + MCPTT server 2->>MCPTT server 1: 10. MCPTT private call response + MCPTT server 1->>MCPTT client 1: 11. MCPTT private call response + Note right of MCPTT client 2: 12. Media plane established + +``` + +Sequence diagram illustrating Private call setup in automatic commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT clients and servers across two systems. Steps include registration, call initiation, request routing, authorization, progress indication, notification, response, and media plane establishment. + +**Figure 7.3.2.4-1: Private call setup in automatic commencement mode - users in multiple MCPTT systems** + +1./2. No change. + +3. The MCPTT private call request contains the MCPTT ID or functional alias of invited user. + +NOTE: End-to-end encryption requires the target MCPTT ID. + +4./5. No change. + +6. If the MCPTT private call request is initiated by using a functional alias as called party address, then the target MCPTT system is identified by help of configured functional alias mask in the MCPTT service configuration data. + +7. If the MCPTT server private call request contains a functional alias as called party address, the MCPTT server resolves the MCPTT ID of the called MCPTT user by using the functional alias address. + +8.-12. No change. + +### 7.3.3 Solution evaluation + +The solution describes a private MCPTT call setup using a functional alias as target address towards an MCPTT user in a partner MCPTT system. The solution relies on proper MCPTT service configuration data so that the MC server in the primary MC system can identify the partner MC system to which the call is to be routed. + +The solution principle can be re-used for private MCVideo call and point-to-point MCData call scenarios. + +## 7.4 Functional alias support for migrated users + +### 7.4.1 General + +This solution addresses the key issue 2 described in clause 5.2 on functional alias handling. + +The solution provides the possibility to configure proper functional aliases for MC service users migrating to a partner MC system. + +### 7.4.2 Solution description + +#### 7.4.2.1 Principle + +The solution relies on the existing procedure "MC service user receiving MC service from a partner MC system" described in 3GPP TS 23.280 [5] clause 10.1.4.3.2. The procedure can provide the list of functional aliases for use in the partner MC system as part of the migration MC service user profile. + +#### 7.4.2.2 Procedure + +A set of functional aliases for each primary MC system is configured in the partner MC system. After the MC user is migrated from the primary MC system into the partner MC system, the partner MC system provides the MC user profile for migration which includes a preconfigured set of functional aliases allowed to be used within the partner MC system. + +The MC configuration management server provides the functional alias management server functionality as described in subclause 7.4.2.2.13 of 3GPP TS 23.280 [5]. The configuration management server functionality is extended with the configuration function for functional alias sets for different partner MC system. + +NOTE: Different migrated MC users from different partner MC systems may need different functional alias sets; i.e. the configuration acts on MC partner system basis. + +The procedure is described in 3GPP TS 23.280 [5] clause 10.1.4.3.2: MC service user receiving MC service from a partner MC system: + +![Sequence diagram showing the retrieval of user profile in partner MC system. The diagram involves three main entities: MC service UE, Partner MC system of user (containing Configuration management server and MC service user database), and Primary MC system of user (containing Configuration management server and MC service user database). The sequence of messages is: 1. Get MC service user profile for migration request (UE to Partner CMS), 2. Get migrated MC service user profile request (Partner CMS to Primary CMS), 3. Retrieve user profile for migration (Primary CMS internal), 4. Get migrated MC service user profile response (Primary CMS to Partner CMS), 5. Modify user profile according to partner MC system policy and store (Partner CMS internal), 6. Validate modified MC service user profile request (Partner CMS to Primary CMS), 7. Validate modified user profile for migration (Primary CMS internal), 8. Validate modified MC service user profile response (Primary CMS to Partner CMS), 9. Get MC service user profile for migration response (Partner CMS to UE).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE as MC service UE + participant PartnerMC as Partner MC system of user + participant PrimaryMC as Primary MC system of user + + Note right of PartnerMC: Configuration management server + Note right of PartnerMC: MC service user database + Note right of PrimaryMC: Configuration management server + Note right of PrimaryMC: MC service user database + + UE->>PartnerMC: 1. Get MC service user profile for migration request + PartnerMC->>PrimaryMC: 2. Get migrated MC service user profile request + Note right of PrimaryMC: 3. Retrieve user profile for migration + PrimaryMC->>PartnerMC: 4. Get migrated MC service user profile response + Note right of PartnerMC: 5. Modify user profile according to partner MC system policy and store + PartnerMC->>PrimaryMC: 6. Validate modified MC service user profile request + Note right of PrimaryMC: 7. Validate modified user profile for migration + PrimaryMC->>PartnerMC: 8. Validate modified MC service user profile response + PartnerMC->>UE: 9. Get MC service user profile for migration response + +``` + +Sequence diagram showing the retrieval of user profile in partner MC system. The diagram involves three main entities: MC service UE, Partner MC system of user (containing Configuration management server and MC service user database), and Primary MC system of user (containing Configuration management server and MC service user database). The sequence of messages is: 1. Get MC service user profile for migration request (UE to Partner CMS), 2. Get migrated MC service user profile request (Partner CMS to Primary CMS), 3. Retrieve user profile for migration (Primary CMS internal), 4. Get migrated MC service user profile response (Primary CMS to Partner CMS), 5. Modify user profile according to partner MC system policy and store (Partner CMS internal), 6. Validate modified MC service user profile request (Partner CMS to Primary CMS), 7. Validate modified user profile for migration (Primary CMS internal), 8. Validate modified MC service user profile response (Primary CMS to Partner CMS), 9. Get MC service user profile for migration response (Partner CMS to UE). + +**Figure 7.4.2.2-1: Retrieval of user profile in partner MC system** + +Within step 5 above the partner MC system has the option of modifying the MC user profile for migrated users. Step 5 is enhanced to support functional alias sets for use in the partner MC system. + +After the MC service UE has received the MC service user profile in step 9, the MC service user is able to activate functional aliases within the partner MC system and use them for communication in the partner MC system. + +NOTE: The use of the same functional alias in multiple MC systems is not supported. + +#### 7.4.2.3 Configuration + +The configuration management server in the primary MC system of the MC service user stores the list of allowed functional aliases and related information as part of the MC service user profile which can be differently configured for each partner MC system. The current specified user profile configuration data set can be used for that purpose. The partner MC system may modify the list of allowed functional aliases according to local configuration information, e.g. remove, add or modify functional aliases. + +### 7.4.3 Solution evaluation + +The solution describes that the existing procedure called MC service user receiving MC service from a partner MC system described in 3GPP TS 23.280 [5] can be used to provide a list of functional aliases to be used in the partner MC system. The solution is applicable to all MC services and call scenarios. + +## 7.5 Migration during an ongoing group communication + +### 7.5.1 General + +This solution addresses the key issue 3 described in clause 5.3 on group communication between MC systems. + +The solution provides the capability for an MC service user to migrate to another MC system during an ongoing group communication and to continue the group communication in the other MC system. + +### 7.5.2 Solution description + +#### 7.5.2.1 Procedure + +The procedure is based on the following existing procedures: + +- MC service group de-affiliation procedure as described in TS 23.280 [5] clause 10.8.4.2, or +- De-affiliation from MC service group(s) defined in partner MC service system and is described in TS 23.280 [5] clause 10.8.4.3. +- MC service user receiving MC service from a partner MC system as described in TS 23.280 [5] clause 10.1.4.3.2. +- MC service group affiliation procedure as described in TS 23.280 [5] clause 10.8.3.1, or +- Affiliation to MC service group(s) defined in partner MC system as described in TS 23.280 [5] clause 10.8.3.2 or clause 10.8.3.2a. +- Late entry pre-arranged group call as described in TS 23.379 [2] clause 10.6.2.3.1.1.4. + +NOTE 1: The solution is about MCPTT group calls but is applicable for other services too. + +Pre-conditions: + +1. The MCPTT client is a receiving party in one or more ongoing group calls in the primary MC system. +2. The MCPTT UE detects the need to change the MC system. + +![Sequence diagram illustrating the migration to a partner MC system during an ongoing group call. The diagram shows interactions between an MCPTT UE (containing MCPTT client and Configuration management client), a Partner MC system (containing MCPTT server, Group management server, and Configuration management server), and a Primary MC system (containing MCPTT server, Group management server, and Configuration management server). The sequence of steps is: 1. MCPTT group de-affiliation, 2. Retrieval of user profile in partner MC system, 3. MCPTT group affiliation, and 4. Late entry pre-arranged group call.](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) + +``` + +sequenceDiagram + participant MCPTT_UE as MCPTT UE + participant Partner_MC_System as Partner MC system + participant Primary_MC_System as Primary MC system + + Note right of MCPTT_UE: MCPTT client + Note right of MCPTT_UE: Configuration management client + Note right of Partner_MC_System: MCPTT server + Note right of Partner_MC_System: Group management server + Note right of Partner_MC_System: Configuration management server + Note right of Primary_MC_System: MCPTT server + Note right of Primary_MC_System: Group management server + Note right of Primary_MC_System: Configuration management server + + MCPTT_UE->>Primary_MC_System: 1. MCPTT group de-affiliation + Primary_MC_System-->>MCPTT_UE: + MCPTT_UE->>Partner_MC_System: 2. Retrieval of user profile in partner MC system + Partner_MC_System-->>MCPTT_UE: + MCPTT_UE->>Primary_MC_System: 3. MCPTT group affiliation + Primary_MC_System-->>MCPTT_UE: + MCPTT_UE->>Partner_MC_System: 4. Late entry pre-arranged group call + +``` + +Sequence diagram illustrating the migration to a partner MC system during an ongoing group call. The diagram shows interactions between an MCPTT UE (containing MCPTT client and Configuration management client), a Partner MC system (containing MCPTT server, Group management server, and Configuration management server), and a Primary MC system (containing MCPTT server, Group management server, and Configuration management server). The sequence of steps is: 1. MCPTT group de-affiliation, 2. Retrieval of user profile in partner MC system, 3. MCPTT group affiliation, and 4. Late entry pre-arranged group call. + +**Figure 7.5.2.1-1: Migration to partner MC system during an ongoing group calls** + +1. The MCPTT client requests de-affiliation from MCPTT groups. The MCPTT groups are either defined in the primary MC system (TS 23.280 [5] clause 10.8.4.2) or the partner MC system (TS 23.280 [5] clause 10.8.4.3). The MCPTT client de-authorizes from the primary MC System. +2. After migration to the partner MC system, the configuration management client triggers retrieval of the MC service user profile used within the partner MC system (TS 23.280 [5] clause 10.1.4.3.2). + +NOTE 2: User authentication, service authorisation and signalling plane procedures are not shown. + +3. The MCPTT client requests affiliation to MCPTT groups. The MCPTT groups are either defined in the primary MC system (TS 23.280 [5] clause 10.8.3.1) or the partner MC system (TS 23.280 [5] clause 10.8.3.2 or clause 10.8.3.2a). + +4. If any of the received group calls are ongoing in the partner MC system, the partner MC system shall initiate a late-entry procedure towards the MCPTT client. If any of the received group calls are taken place in the primary MC system but not yet in the partner MC system, the affiliation by the migrated MCPTT UE triggers the late-entry procedure which then includes the MCPTT UE and the partner MC system into the group call. + +The MCPTT client may indicate the successful migration of group communications to the MCPTT user. + +### 7.5.3 Solution evaluation + +The solution provides the capability for an MCPTT user to migrate to another MCPTT system during an ongoing MCPTT group communication and to continue the group communication in the partner MC system. The solution relies on existing procedures on group affiliation and group de-affiliation, user profile retrieval in the partner MC system and late entry for pre-arranged group calls. + +The solution principle can be re-used for MCVideo and MCData group call scenarios, if needed. + +## 7.6 Migration during an ongoing private communication + +### 7.6.1 General + +This solution addresses the key issue 5 described in clause 5.5 on quick migration towards another MC system. + +The solution provides the capability for an MC service user to migrate to another MC system during an ongoing private communication and to continue the private communication in the other MC system without MC service user interaction. + +### 7.6.2 Solution description + +#### 7.6.2.1 Procedure + +NOTE 1: The solution is about MCPTT private calls but is applicable for other services too. + +Pre-conditions: + +1. The MCPTT client has one or more ongoing private calls in the primary MC system. +2. The MCPTT UE detects the need to change the MC system. + +![Sequence diagram showing the migration of a private call from the Primary MCPTT system to the Partner MCPTT system. The diagram involves three components in each system: MCPTT client, Configuration management client, and MCPTT server. The sequence of messages is: 1. Private call suspend initiated by MCPTT client 1; 2. Retrieval of user profile in partner MC system; 3. Private call resume initiated by MCPTT client 1.](9ddc2a6358c46a4717ceaed7183b6a46_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant Configuration management client 1 + participant MCPTT server 1 + participant MCPTT client 2 + participant Configuration management client 2 + participant MCPTT server 2 + + Note over MCPTT client 1, MCPTT server 1: Primary MCPTT system + Note over MCPTT client 2, MCPTT server 2: Partner MCPTT system + + MCPTT client 1->>MCPTT client 2: 1. Private call suspend initiated by MCPTT client 1 + MCPTT client 1->>Configuration management client 2: 2. Retrieval of user profile in partner MC system + MCPTT client 1->>MCPTT client 2: 3. Private call resume initiated by MCPTT client 1 + +``` + +Sequence diagram showing the migration of a private call from the Primary MCPTT system to the Partner MCPTT system. The diagram involves three components in each system: MCPTT client, Configuration management client, and MCPTT server. The sequence of messages is: 1. Private call suspend initiated by MCPTT client 1; 2. Retrieval of user profile in partner MC system; 3. Private call resume initiated by MCPTT client 1. + +**Figure 7.6.2.1-1: Migration to partner MC system during an ongoing private call** + +1. MCPTT client 1 requests private call suspend to put the call into suspended state in MCPTT client 2. The call is cleared between MCPTT server 1 and MCPTT server 2, and knowledge of the suspended call is held by MCPTT client 1 and MCPTT client 2. The MCPTT users of MCPTT client 1 and MCPTT client 2 get an indication that the private call has been suspended. MCPTT client 1 and MCPTT client 2 start a timer to allow the call suspended state to be cleared if the call is not resumed within a predetermined time interval. +2. After migration to the other MC system, the configuration management client 1 triggers retrieval of the MC service user profile used within the partner MC system (TS 23.280 [5] clause 10.1.4.3.2). + +NOTE 2: User authentication, service authorisation and signalling plane procedures are not shown. + +- MCPTT client 1 requests a new private call to MCPTT client 2, with the call resume indication to remove the call suspended state in MCPTT client 2. The MCPTT users of MCPTT client 1 and MCPTT client 2 get an indication that the private call has been resumed. + +NOTE 3: Any local call restrictions are considered. + +NOTE 4: If another private call request is sent to MCPTT client 1 or MCPTT client 2 before the call has resumed, the actions of the receiving MCPTT client are outside the scope of the present document and could include rejecting this new private call request. + +The MCPTT client may indicate the successful migration of private call communications to the MCPTT user. + +#### 7.6.2.2 Information flows + +##### 7.6.2.2.1 MCPTT private call suspend request + +Table 7.6.2.2.1-1 describes the information flow MCPTT private call suspend request from the MCPTT client to the MCPTT server, from the MCPTT server to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 7.6.2.2.1-1: MCPTT private call suspend request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | + +##### 7.6.2.2.2 MCPTT private call suspend response + +Table 7.6.2.2.2-1 describes the information flow MCPTT private call suspend response from the MCPTT client to the MCPTT server, from the MCPTT server to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 7.6.2.2.2-1: MCPTT private call suspend response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | In the direction MCPTT client to MCPTT server this shall be the MCPTT ID of the responding MCPTT client.
In the direction MCPTT server to MCPTT client this shall be the MCPTT ID of the destination MCPTT client. | + +##### 7.6.2.2.3 MCPTT private call resume request (MCPTT client to MCPTT server) + +Table 7.6.2.2.3-1 describes the information flow MCPTT private call resume request from the MCPTT client to the MCPTT server. + +**Table 7.6.2.2.3-1: MCPTT private call resume request (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|----------------------------------------------|--------|---------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID (see NOTE) | O | The MCPTT ID of the called party | +| Functional alias (see NOTE) | O | The functional alias of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | O | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication that is included if the user is requesting a particular commencement mode | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Location information | O | Location of the calling party | +| Requested priority | O | Application priority level requested for this call | +| Transfer indicator | O | Indicates that the MCPTT private call request is a result of a call transfer (true/false) | +| Forwarding indicator | O | Indicates that the MCPTT private call request is a result of a call forwarding (true/false) | +| NOTE: At least one identity must be present. | | | + +##### 7.6.2.2.3a MCPTT private call resume request (MCPTT server to MCPTT server) + +Table 7.6.2.2.3a-1 describes the information flow MCPTT private call resume request from the MCPTT server to the MCPTT server. + +**Table 7.6.2.2.3a-1: MCPTT private call resume request (MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Requested priority | O | Priority level requested for the call. | +| Location information | O | Location of the calling party | + +##### 7.6.2.2.3b MCPTT private call resume request (MCPTT server to MCPTT client) + +Table 7.6.2.2.3b describes the information flow MCPTT private call resume request from the MCPTT server to the MCPTT client. + +**Table 7.6.2.2.3b: MCPTT private call resume request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | + +##### 7.6.2.2.4 MCPTT private call resume response (MCPTT client to MCPTT server) + +Table 7.6.2.2.4-1 describes the information flow MCPTT private call resume response from the MCPTT client to the MCPTT server. + +**Table 7.6.2.2.4-1: MCPTT private call resume response (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|-----------------------------|--------|----------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| SDP answer | M | Media parameters selected | +| Requested commencement mode | O | An indication of the commencement mode to be used. | + +##### 7.6.2.2.4a MCPTT private call resume response + +Table 7.6.2.2.4a -1 describes the information flow MCPTT private call resume response from the MCPTT server to the MCPTT server and the MCPTT server to the MCPTT client. + +**Table 7.6.2.2.4a-1: MCPTT private call resume response information elements** + +| Information Element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| Acceptance confirmation | O | An indication whether the user has positively accepted the call. | +| SDP answer | M | Media parameters selected | + +### 7.6.3 Solution evaluation + +The solution provides the capability for an MCPTT user to migrate to another MCPTT system during an ongoing MCPTT private communication and to continue the private communication in the partner MC system. The solution relies on a new MCPTT private call suspend/resume procedure and an existing procedure for user profile retrieval in the partner MC system. + +The solution principle can be re-use for MCVideo and MCData group call scenarios, if needed. + +## 7.7 Optimize the connectivity between MC systems + +### 7.7.1 General + +This solution addresses the key issue 1 described in clause 5.1 on media and signalling routing. The aspect of the optimal routing of the media is of particular interest, so that delays especially in the media plane caused by the route involving the Home MC system can be eliminated. This is of elementary interest, especially used for data traffic in the process automation context. Also voice and video may benefit from the proposed approach in reducing latencies. + +The solution addresses the aspect how to obtain the information about the association between MC service user and the partner MC system when MC service user was migrated to another MC system. The proposed new procedural elements will determine target MC service user migration status before the media gets routed to the target MC system. + +### 7.7.2 Solution description + +#### 7.7.2.1 Principle + +The basic approaches with regard to migration, the necessary authentication and the migrated call handling have already been specified in 3GPP TS 23.280 [5]. For example, in the rail environment, more dynamic is anticipated because a train can use several partner organizations for its communication needs regardless of time during its mission (e.g., cargo trains commute between Rotterdam and Genoa). Terminating communication requirements are particularly affected and only the MC service server of the primary MC system has the current association with the respective partner MC system of its MC service client. Such information is decisive for the determination of the partner MC system to control the call routing accordingly. Accordingly, for each migrated MC service client call routing, a lookup to determine the currently visited partner organization need to be preceded. + +#### 7.7.2.2 Procedure + +The proposed MC system interrogation is a real time query to obtain current up-to-date status information of the corresponding MC service client. The resulting MC system interrogation status information of the MC service client will determine corresponding call routing, message delivery etc. towards the corresponding MC service user. In general, the MC system interrogation can be used for various purposes to obtain status information of a dedicated MC service client. + +Figure 7.7.2.2-1 shows the procedure where an MC service client in MC system 1 initiates a private call to an MC service client which is migrated to MC system 3. + +Preconditions: + +- The corresponding MC systems are interconnected. +- MC service client belonging to primary MC system 2 migrated to partner MC system 3. +- Interconnected MC systems can derive the corresponding primary MC system of the targeted/migrated MC service users. +- Functional alias resolution is executed prior call request forwarding starts. + +![Sequence diagram illustrating the interrogation to determine the MC system and MC service client association. The diagram shows interactions between MC system 1, MC system 2, and MC system 3 (which includes a migrated MC service client from MC system 2).](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +``` + +sequenceDiagram + participant MCSC1 as MC service client (MC system 1) + participant MS1 as MC system 1 + participant MS2 as MC system 2 + participant MS3 as MC system 3 + participant MCSC2 as MC service client belonging to MC system 2 + + Note right of MCSC2: MC system 3 +Partner MC system of migrated MC service client + + MCSC1->>MS1: 1. Call request + MS1->>MS2: 2. Request MC user info + MS2->>MCSC2: 3. MC service user lookup (MC client marked as migrated to MC system 3) + MS2->>MS1: 4. Response MC user info + MS1->>MS3: 5. Call request + MS3->>MS1: 6. Call response + MS1->>MS3: 7. Establish floor/transmission control and media paths + +``` + +Sequence diagram illustrating the interrogation to determine the MC system and MC service client association. The diagram shows interactions between MC system 1, MC system 2, and MC system 3 (which includes a migrated MC service client from MC system 2). + +**Figure 7.7.2.2-1: Interrogation to determine the MC system and MC service client association** + +1. MC service client associated with MC system 1 initiates a call request to a target MC service client belonging to MC system 2. MC system 1 need to figure out to which target MC system the call request needs to be forwarded. The called MC service ID is used to determine the primary MC system to request necessary MC user information to be able to route the communication/media. +2. Request MC user info is used to retrieve the current MC user migration status and to obtain relevant routing information of the corresponding MC system where the MC service client is currently located. +3. MC system 2 looks up MC service user information to figure out current MC service users to MC system association. In the illustrated case, the MC service user is migrated to MC system 3. +4. MC system 2 responds to the request with Response MC user info, which includes the MC service ID of MC service client 2, currently migrated to MC system 3 +5. MC system 1 uses the received MC user information to forward the communication/media to MC system 3 addressing MC service client belonging to MC system 2. +6. The call response acknowledges the communication request toward MC service client of MC system 1. +7. Necessary media, if necessary, floor control and transmission control is established between the corresponding MC service client. + +#### 7.7.2.3 Configuration + +The corresponding primary MC service server needs to keep track about the migration status of its associated MC service user. This information gets looked up to route communications/media to the corresponding MC system who the MC service user is located. The information necessary for routing calls/communications towards a MC service user need to contain unique MC system identifier e.g., organisation identifier. + +#### 7.7.2.4 Information flows + +##### 7.7.2.4.1 General + +The information flows address the aspect that various MC service communications may use the proposed flows to forward a communication directly to the target MC system without passing through the primary MC system of the migrated MC service user. + +##### 7.7.2.4.2 Request MC user info + +The MC system uses the flow to determine the primary MC system ID based on the targeted MC service user primary MC system association. + +**Table 7.7.2.4.2-1: Request MC user info - information elements** + +| Information Element | Status | Description | +|---------------------------------|--------|-------------------------------------------------------------------------------| +| MC node ID requesting MC system | M | MC service node identifier of the requesting MC system. | +| MC node ID queried MC system | M | MC service node identifier of the queried MC system ,e.g., MC gateway server. | +| MC service ID | M | MC service ID to be interrogated. | + +##### 7.7.2.4.3 Response MC user info + +The response MC user info is used to inform the requesting MC system about the migration status of the interrogated MC service user. + +**Table 7.7.2.4.3-1: Response MC user info - information elements** + +| Information Element | Status | Description | +|---------------------------------|--------|-------------------------------------------------------------------------------------------------| +| MC node ID queried MC system | M | MC service node identifier of the queried MC system ,e.g., MC gateway server. | +| MC node ID requesting MC system | M | MC service node identifier of the requesting MC system. | +| MC service ID | M | Interrogated MC service ID. | +| MC system ID | M | Unique identifier of the MC system the migrated MC service user is associated during the query. | +| MC node ID | M | MC node ID the migrated MC service user is associated. | + +### 7.7.3 Solution evaluation + +The solution proposes a new procedure to allow flexibility in communication/media routing for the use case when MC service users enter during their whole mission multiple MC systems and those MC systems are interconnected. The MC user information retrieval allows real time lookup of current MC service user migration status and corresponding necessary routing information to reach migrated MC service users. The communication and the corresponding media can be directly routed towards the MC system where the migrated MC service resides bypassing the Primary MC system of the migrated MC service user. + +This solution impacts current assumed call flow processing at the MC service server (MO side) where in the MC service server does not forward the call request to the home MC system of the addressed MC service user and the media routing is always directly between the originated MC system 1 (call originator) and the terminating MC system 3 (migrated MC service user). + +The proposed procedure and corresponding flows can be used independent from the MC service. + +## 7.8 Private call using functional alias towards a partner MC system + +### 7.8.1 General + +This solution addresses the key issue 2 described in clause 5.2 on functional alias handling. + +The solution provides the possibility for an MCPTT user to initiate a private MCPTT call using a functional alias, defined in the partner MC system, as target address towards an MCPTT user in a partner MC system. + +### 7.8.2 Solution description + +#### 7.8.2.1 Principle + +Allow the MCPTT functional alias controlling server in the primary MC system interworks with the MCPTT functional alias controlling server in the partner MC system to resolve the functional alias used for a private call towards a partner MC system using a functional alias. + +In TS 3GPP TS 23.280 [5], clause 8.1.5 defines the functional alias as a form of a URI. As a common form of an URI it is represented as `userinfo@host` where the user info part can be the functional alias and the host part can be the domain that hosts the functional alias controlling server. With this clarification in 3GPP TS 23.280 [5], the functional alias shall identify where its MC service functional alias controlling server locates. + +We have standardized how the functional alias is used in a private call in the same MC system in 3GPP TS 23.379 [2] clause 10.7.2.2 that includes end-to-end encryption security and the same mechanism is proposed to be used in a private call between 2 MC systems, i.e. the resolution of the called party functional alias (i.e. the MCPTT ID) shall be used by the originating party to setup the private call. Doing this the primary MCPTT FA controlling server shall query the partner MCPTT FA controlling server to resolve the called party functional alias for the private call. + +#### 7.8.2.2 Functional alias clarification + +To clarify the architectural requirement of the format of the functional alias, it is proposed to add clarification to the 3GPP TS 23.280 [5] clause 8.1.5 as: + +- Functional alias provides a complementary, role-based user identification scheme which can be used by MC service users for operational purposes in the form of meaningful elements such as the function, the order number or vehicle identifications that can be used within any form of MC service communication. Functional alias takes a form of a URI where the host part of the URI shall identify the home MC system functional alias controlling server. The application addressing remains in its form and forms the foundation for the association with the corresponding functional alias. An MC service user can simultaneously activate several functional aliases but only one can be associated to a certain communication. +- Each functional alias is subject to the uniqueness principle within an organization and can be shared simultaneously by several MC service users, depending on the assignment. In this case, all assigned MC service users sharing a functional alias can be included in a communication. +- An MC service user can simultaneously use different functional aliases from multiple service organizations to allow the MC service user to be reachable by different organizations. +- The use of a functional alias always requires an association with the MC service ID. The MC service ID needs to be used to provide the security context for a communication. + +#### 7.8.2.3 Functional alias resolution + +When the MCPTT FA controlling server receives a request to resolve a functional alias and if the requested functional alias belongs to a different MC system, the MCPTT FA controlling server sends a request to the partner MC system's MCPTT FA controlling server for resolution. The partner MC system's MCPTT FA controlling server will resolve the functional alias with a terminating MCPTT ID and returns it to the requesting MCPTT FA controlling server. + +The information flow in 3GPP TS 3GPP 23.379 [2] clause 10.7.2.1.8 is modified as: + +##### 7.8.2.3.1 MCPTT functional alias resolution response + +Table 7.8.2.3-1 describes the information flow MCPTT functional alias resolution response from the MCPTT functional alias controlling server to another MCPTT functional alias controlling server, the MCPTT functional alias controlling server to the MCPTT server and the MCPTT server to the MCPTT client. + +**Table 7.8.2.3-1: MCPTT functional alias resolution response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The corresponding MCPTT ID of the called functional alias. Return "NONE" if no one activates the targeted Functional Alias. | + +##### 7.8.2.3.2 MCPTT functional alias resolution request + +Table 7.8.2.3-2 describes the information flow MCPTT functional alias resolution request from the MCPTT server to the MCPTT functional alias controlling server and from the MCPTT functional alias controlling server to another MCPTT functional alias controlling server. + +**Table 7.8.2.3-2: MCPTT functional alias resolution request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| Functional alias | M | The functional alias of the called party | + +#### 7.8.2.4 Procedure + +The MCPTT private call setup procedure between MCPTT servers is modified to allow using the functional alias as called party address, i.e. the MCPTT ID address is resolved by the partner MC system through the primary MCPTT server and primary MCPTT functional alias controlling server. + +Proposed changes against 3GPP TS 23.379 [2] clause 10.7.2.3.1: Private call setup in automatic commencement mode - MCPTT users in multiple MC systems with additional functional alias resolution steps similar to the mechanism used in TS 3GPP 23.379 [2] clause 10.7.2.2.1: + +NOTE: The changes are applicable when using manual commencement mode as well. + +Additional new pre-condition: + +1. A secured connection has been established between the MCPTT functional alias controlling servers in different MC systems. + +![Sequence diagram for private call setup in automatic commencement mode between two MCPTT service providers.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT Server 1 + participant MCPTT FA Controlling Server 1 + participant MCPTT FA Controlling Server 2 + participant MCPTT Server 2 + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. MCPTT client 1 registered for MCPTT service + Note left of MCPTT client 1: 2. initiate private call + MCPTT client 1->>MCPTT Server 1: 3. MCPTT private call request + MCPTT Server 1->>MCPTT FA Controlling Server 1: 4. Authorize request + MCPTT Server 1->>MCPTT FA Controlling Server 1: 5. MCPTT functional alias resolution request + MCPTT FA Controlling Server 1->>MCPTT FA Controlling Server 2: 6. MCPTT functional alias resolution request + MCPTT FA Controlling Server 2->>MCPTT FA Controlling Server 1: 7. MCPTT functional alias resolution response + MCPTT FA Controlling Server 1->>MCPTT Server 1: 8. MCPTT functional alias resolution response + MCPTT Server 1->>MCPTT client 1: 9. MCPTT functional alias resolution response + MCPTT client 1->>MCPTT Server 1: 10. MCPTT private call request + MCPTT Server 1->>MCPTT Server 2: 11. MCPTT private call request + MCPTT client 2->>MCPTT Server 2: 1. MCPTT client 2 registered for MCPTT service + MCPTT Server 2->>MCPTT FA Controlling Server 2: 13. Authorize request + MCPTT FA Controlling Server 2->>MCPTT Server 2: 14. MCPTT private call request + MCPTT Server 2->>MCPTT client 2: 15. Notify call + MCPTT client 2->>MCPTT Server 2: 16. MCPTT private call response + MCPTT Server 2->>MCPTT Server 1: 17. MCPTT private call response + MCPTT Server 1->>MCPTT client 1: 18. MCPTT private call response + Note right of MCPTT client 2: 19. Media plane established + +``` + +Sequence diagram for private call setup in automatic commencement mode between two MCPTT service providers. + +**Figure 7.8.2.4-1: Private call setup in automatic commencement mode - users in multiple MC systems** + +1-2. same as step 1-2 in 3GPP TS 23.379 [2] clause 10.7.2.3.1, no change. + +3. The MCPTT private call request contains the MCPTT ID or functional alias of invited user. + +4. If the MCPTT private call request contains a functional alias instead of an MCPTT ID as called party, the MCPTT server 1 shall resolve the functional alias to the corresponding MCPTT ID for which the functional alias is active using steps 5-8 below. The MCPTT server shall also check whether MCPTT client 1 can use the functional alias to setup a private call. If authorized, proceed to step 5. + +Otherwise (using MCPTT ID for the MCPTT private call) the MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call to the MCPTT user at MCPTT client 2; if authorized proceed to step 11. + +5-10 new additional steps as: + +5. The MCPTT server 1 sends MCPTT functional alias resolution request message to the MCPTT FA controlling server 1 to resolve the functional alias of the called party. + +6. The MCPTT FA controlling server 1 determines that the function alias belongs to MCPTT service provider 2 and forwards the MCPTT functional alias resolution request message to MCPTT FA controlling server 2. + +7. The MCPTT FA controlling server 2 resolve the functional alias and determines the corresponding MCPTT ID shall be used to terminate the call and returns it to the MCPTT FA controlling server 1 in the MCPTT functional alias resolution response message. + +- NOTE: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the private call request is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria. The selection of an appropriate MCPTT ID is left to implementation. This selection criteria can include rejection of the call, if no suitable MCPTT ID is selected. +8. The MCPTT FA controlling server 1 returns the corresponding MCPTT ID to MCPTT server 1 in the MCPTT functional alias resolution response message. The MCPTT server 1 shall check if MCPTT user at MCPTT client 1 is authorized to initiate the private call to the MCPTT user at MCPTT client 2. If not authorized stop the procedure, otherwise continue with step 9. + 9. The MCPTT server 1 responds with a MCPTT functional alias resolution response message that contains the resolved MCPTT ID back to MCPTT client 1. + 10. The MCPTT client 1 sends a new MCPTT private call request towards the resolved MCPTT ID. + 11. same as step 6 in 3GPP TS 23.379 [2] clause 10.7.2.3.1, no change. + 12. same as step 5 in 3GPP TS 23.379 [2] clause 10.7.2.3.1, no change. + - 13-15. same as step 7-9 in 3GPP TS 23.379 [2] clause 10.7.2.3.1, no change. + 16. The receiving MCPTT client 2 accepts the private call automatically, and an acknowledgement is sent to the MCPTT server 2. + 17. The MCPTT server 2 forwards the MCPTT private call response message to MCPTT server 1. + - 18-19. same as steps 11-12 in 3GPP TS 23.379 [2] clause 10.7.2.3.1, no change. + +### 7.8.3 Solution evaluation + +The solution describes a private MCPTT call setup using a functional alias as target address towards an MCPTT user in a partner MC system with end-to-end encryption security. The solution relies on new communications between the MCPTT functional alias controlling server between interconnected MC systems with similar functional alias resolution mechanism described in 3GPP TS 23.379 [2] clause 10.7.2.2.1. + +The solution principle can be re-used for private MCVideo call and point-to-point MCData call scenarios. + +## 7.9 Solution on IP connectivity between MC systems + +### 7.9.1 General + +This solution addresses the key issue 7 described in clause 5.7 on IP connectivity between MC systems defining an alternative to the existing scheme in 3GPP TS 23.280 [5] applicable for IP communications to migrated MC services users bypassing primary MC system. The solution provides an alternative call processing approach bypassing the primary MC system of the migrated MC service user and can be used as a contribution to limited media plane delays. + +### 7.9.2 Solution description + +#### 7.9.2.1 Functional model + +The common functional model in 3GPP TS 23.280 [5] and the functional model that corresponds to MCData in 3GPP TS 23.282 [4] already provides the necessary means for interconnection either using topology hiding using an MC gateway server or without topology hiding not using an MC gateway server. + +#### 7.9.2.2 Reference points + +The necessary reference points applicable for interconnection and migration in 3GPP TS 23.280 [5] and 3GPP TS 23.282 [4] apply for direct communications between MC systems bypassing the primary MC system associated with a migrated MC service user. + +NOTE: MCPTT service and MCVideo service can also reuse defined reference points for interconnection. + +#### 7.9.2.3 Procedures and flows + +To determine the MC system of the migrated MC service user, the procedure and flow described in clause 7.7 is applied. For call processing applicable generic procedures for interconnection according to 3GPP TS 23.280 [5] applied. + +### 7.9.3 Solution evaluation + +The enhancements proposed in clause 7.7 allow the determination of the actual hosting MC system of the migrated MC service user. The response user data info contains necessary information about MC system identifier to route the call request directly towards target MC system without passing the primary MC system. + +This solution is applicable when communication recording in the primary MC system is not required. + +## 7.10 Solution on migration without interconnection between two MC systems + +### 7.10.1 General + +This solution addresses key issue 8 described in clause 5.8 on enabling an authorized MC service user to migrate to another MC system, where there is no interconnection between the primary and the partner MC systems. + +As stated in 3GPP TS 23.280 [5], clause 5.2.9.1, "MC service interconnection needs to be provided between MC systems that wish to provide migration of their MC service users.". However, there are scenarios where an MC service user may need to migrate to an MC partner system (e.g., tactical networks, MC systems without interconnection due to regulatory constraint), where there is no interconnection between the MC systems. + +### 7.10.2 Solution description + +#### Pre-conditions + +- The MC service user wishes to migrate to a partner MC system, even if there is no interconnection to the primary MC system. +- The primary and partner Identity Management Server have been provisioned with signing certificates using an out of band mechanism, as specified in 3GPP TS 33.180 [X], clause 5.1.4.2. +- MC service user authentication and authorization has taken place in the primary MC system, which has supplied necessary credentials to the MC service client to permit service authorization to take place in the partner system. +- The MC service client has been configured with an MC service user profile, by the primary MC system, that contains the necessary parameters needed for connectivity with the partner MC system, including authorization for migration. +- The partner MC system has been provisioned with a user profile for the migrating MC service user. + +![Sequence diagram showing service authorization for migration to a partner MC system. The diagram is titled 'Partner MC system of migrating MC service UE'. It features two main entities: 'MC service UE (of primary system)' and 'Partner MC system'. The sequence of events is: 1. Migration, where the UE migrates to the partner system; 2. Authorization check, where the partner system verifies the user's permission to migrate.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE as MC service UE (of primary system) + participant PartnerMC as Partner MC system + Note over UE, PartnerMC: Partner MC system of migrating MC service UE + Note right of UE: 1. Migration + Note right of PartnerMC: 2. Authorization check + +``` + +Sequence diagram showing service authorization for migration to a partner MC system. The diagram is titled 'Partner MC system of migrating MC service UE'. It features two main entities: 'MC service UE (of primary system)' and 'Partner MC system'. The sequence of events is: 1. Migration, where the UE migrates to the partner system; 2. Authorization check, where the partner system verifies the user's permission to migrate. + +**Figure 7.10.2-1 Service authorization for migration to partner MC system** + +1. The MC service UE migrates to the partner MC system by using the available access information and credentials provided by the primary MC system and after establishing the local PLMN connectivity. +2. The partner MC system performs an authorization check to verify that the MC service user is permitted to migrate, using the inter-domain MC user service authorization procedures, as specified in 3GPP TS 33.180 [7]. + +### 7.10.3 Solution evaluation + +The solution describes how an MC service user can migrate to another MC system, where there is no interconnection between the primary and partner MC systems. + +The solution is applicable for all MC services and uses present security mechanisms, as described in 3GPP TS 33.180[7], clause 5.1.4. + +## 7.11 Private call forwarding between MCPTT systems + +### 7.11.1 General + +This solution addresses the call forwarding related aspects of key issue 6 described in clause 5.6 on call forwarding/call transfer between MC systems. + +The solution provides the possibility of forwarding MCPTT private calls between MCPTT users in different MCPTT systems. + +### 7.11.2 Solution description + +#### 7.11.2.1 Principle + +Currently call forwarding for MCPTT private calls is defined within one MCPTT system. The following solution defines the necessary changes to allow call forwarding between MCPTT users in different MCPTT systems. + +#### 7.11.2.2 Messages + +The MCPTT private call forwarding related information flows are modified (and marked with highlighting) to cover necessary elements and messages between MCPTT servers to support MCPTT private call forwarding for users in different MCPTT systems. + +Proposed modifications in 3GPP TS 23.379 [2] Table 10.7.2.1.2-1: MCPTT private call request (MCPTT server to MCPTT server) information elements: + +NOTE 1: This information flow uses as a baseline Table 7.3.2.3-1. + +**Table 7.11.2.2-1: MCPTT private call request (MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|----------------------------------------------|--------|---------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID (see NOTE) | O | The MCPTT ID of the called party | +| Functional alias (see NOTE) | O | The functional alias of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Requested priority | O | Priority level requested for the call. | +| Transfer indicator | O | Indicates that the MCPTT private call request is a result of a call transfer (true/false) | +| Forwarding indicator | O | Indicates that the MCPTT private call request is a result of a call forwarding (true/false) | +| Location information | O | Location of the calling party | +| NOTE: At least one identity must be present. | | | + +Proposed modifications in 3GPP TS 23.379 [2] Table 10.7.5.1.2-1: MCPTT private call forwarding request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT server. + +**Table 7.11.2.2-2: MCPTT private call forwarding request (MCPTT client to MCPTT server and MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|--------------------------------------|--------|----------------------------------------------------| +| MCPTT ID | M | The MCPTT ID requesting the call forwarding | +| MCPTT ID | M | The MCPTT ID originating the MCPTT private call | +| MCPTT ID (see NOTE) | O | The target MCPTT ID of the call forwarding | +| Functional alias (see NOTE) | O | The target functional alias of the call forwarding | +| NOTE: One identity shall be present. | | | + +Proposed modifications in 3GPP TS 23.379 [2] Table 10.7.5.1.5-1: MCPTT private call forwarding request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT server. + +**Table 7.11.2.2-3: MCPTT private call forwarding response (MCPTT client to MCPTT server and MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the party to be forwarded | +| MCPTT ID | M | The MCPTT ID of the target of the forwarding | +| Result | M | Result of the call forwarding request – success or fail | + +#### 7.11.2.3 Procedure + +##### 7.11.2.3.1 MCPTT private call forwarding with target of the MCPTT private call forwarding in partner MCPTT system + +The procedure for MCPTT private call forwarding describes the case of an MCPTT users in a partner MCPTT system as target of the MCPTT private call forwarding. + +NOTE 1: The procedure shows manual commencement mode, but the changes are also applicable when using automatic commencement mode. + +NOTE 2: The procedure focusses on the interaction between the MCPTT servers, which is independent of the condition for the call forwarding. Therefore, the procedure is generically applicable for all types of call forwarding. + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call forwarding and has immediate call forwarding enabled with the destination MCPTT client 3. +2. MCPTT client 1 is authorized to make private calls to MCPTT client 2. +3. The redirection counter is below the limit. +4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end-to-end encryption is required for the private call. + +![Sequence diagram showing simplified private call setup with MCPTT private calls forwarding in manual commencement mode. The diagram involves two MCPTT systems. MCPTT system 1 contains MCPTT Client 1, MCPTT Server 1, and MCPTT Client 2. MCPTT system 2 contains MCPTT Server 2 and MCPTT Client 3. The sequence starts with Client 1 sending a request to Server 1. Server 1 detects forwarding from Client 2 and sends a forwarding request to Client 1. Client 1 notifies the user and sends a response. Server 1 then verifies authorization for Client 1 and sends a request to Server 2. Server 2 sends a request to Client 3. Client 3 responds, and Server 2 sends ringing and progress indications back to Server 1, which then pass them to Client 1. Finally, a media plane is established between Client 1 and Client 3.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Server 1 + participant MCPTT Client 2 + participant MCPTT Server 2 + participant MCPTT Client 3 + + Note right of MCPTT Server 1: MCPTT system 1 + Note right of MCPTT Server 2: MCPTT system 2 + + MCPTT Client 1->>MCPTT Server 1: 1. MCPTT private call request + Note right of MCPTT Server 1: 2. MCPTT server detects that MCPTT client 2 has call forwarding turned on and that the condition for the forwarding is meet. + MCPTT Server 1->>MCPTT Client 1: 3. MCPTT private call forwarding request + Note left of MCPTT Client 1: 4. Notify user + MCPTT Client 1->>MCPTT Server 1: 5. MCPTT private call forwarding response + MCPTT Client 1->>MCPTT Server 1: 6. MCPTT private call request + Note right of MCPTT Server 1: 7. MCPTT server verifies that client 1 has been authorized to complete the call forwarding + MCPTT Server 1->>MCPTT Server 2: 8. MCPTT private call request + MCPTT Server 2->>MCPTT Client 3: 9. MCPTT private call request + MCPTT Client 3-->>MCPTT Server 2: 11. MCPTT ringing + MCPTT Server 2-->>MCPTT Server 1: 12. MCPTT ringing + MCPTT Server 1-->>MCPTT Client 1: 13. MCPTT ringing + MCPTT Client 3->>MCPTT Server 2: 14. MCPTT private call response + MCPTT Server 2->>MCPTT Server 1: 15. MCPTT private call response + MCPTT Server 1->>MCPTT Client 1: 16. MCPTT private call response + Note bottom: 17. Media plane established between client 1 and 3 + +``` + +Sequence diagram showing simplified private call setup with MCPTT private calls forwarding in manual commencement mode. The diagram involves two MCPTT systems. MCPTT system 1 contains MCPTT Client 1, MCPTT Server 1, and MCPTT Client 2. MCPTT system 2 contains MCPTT Server 2 and MCPTT Client 3. The sequence starts with Client 1 sending a request to Server 1. Server 1 detects forwarding from Client 2 and sends a forwarding request to Client 1. Client 1 notifies the user and sends a response. Server 1 then verifies authorization for Client 1 and sends a request to Server 2. Server 2 sends a request to Client 3. Client 3 responds, and Server 2 sends ringing and progress indications back to Server 1, which then pass them to Client 1. Finally, a media plane is established between Client 1 and Client 3. + +**Figure 7.11.2.3.1-1: Simplified private call setup with MCPTT private calls forwarding in manual commencement mode with forwarding target in the partner MCPTT system** + +1. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1. + +NOTE 1: If the target of the MCPTT private call request is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details are not described. + +2. MCPTT server 1 detects that MCPTT client 2 has immediate call forwarding enabled to MCPTT client 3 which is registered in MCPTT system 2. + +3. MCPTT server 1 sends an MCPTT private call forwarding request towards MCPTT client 1. + +NOTE 2: If the target of the MCPTT private call forwarding is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details of the resolution are not described. + +4. The user at MCPTT client 1 is notified that a call forwarding is in process. + +5. MCPTT client 1 sends an MCPTT call private forwarding response back to MCPTT server. + +6. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 that includes a call forwarding indication set to true. + 7. MCPTT server 1 verifies that MCPTT client 1 is authorized to perform an MCPTT private call as a result of the MCPTT private call forwarding request. MCPTT server 1 verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 3, and the forwarding indication is set to true. + 8. MCPTT server 1 sends an MCPTT private call request towards MCPTT server 2. + 9. MCPTT server 2 sends an MCPTT private call request towards MCPTT client 3. +- NOTE 3: MCPTT server 2 detects that the private call request contains a forwarding indication is set to true and therefore skips the authorization checking. +10. Optionally MCPTT server 1 sends an MCPTT progress indication to MCPTT client 1. + 11. The user at MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to MCPTT server 2. This step is not required in case of automatic commencement mode. + 12. MCPTT server 2 sends an MCPTT ringing to MCPTT server 1. This step is not required in case of automatic commencement mode. + 13. MCPTT server 1 sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode. + 14. MCPTT client 3 sends an MCPTT private call response to MCPTT server 2. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call. + 15. MCPTT server 2 sends an MCPTT private call response to MCPTT server 1. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call. + 16. MCPTT server 1 sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call. + 17. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established. + +##### 7.11.2.3.2 MCPTT private call forwarding with MCPTT private call forwarding occurring in the partner MCPTT system + +The procedure for MCPTT private call forwarding describes the case of an MCPTT private call forwarding occurring in the partner MCPTT system. + +NOTE 1: The procedure shows manual commencement mode, but the changes are also applicable when using automatic commencement mode. + +NOTE 2: The procedure focusses on the interaction between the MCPTT servers, which is independent of the condition for the call forwarding. Therefore, the procedure is generically applicable for all types of call forwarding. + +Pre-conditions: + +1. MCPTT client 3 is authorized to use call forwarding and has immediate call forwarding enabled with the destination MCPTT client 2. +2. MCPTT client 1 is authorized to make private calls to MCPTT client 3. +3. The redirection counter is below the limit. +4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end-to-end encryption is required for the private call. + +![Sequence diagram showing simplified private call setup with MCPTT private calls forwarding in manual commencement mode with forwarding in the partner MCPTT systems. The diagram involves two systems: MCPTT system 1 (with Client 1, Server 1, and Client 2) and MCPTT system 2 (with Server 2 and Client 3). The process involves a call request from Client 1 to Server 1, which is forwarded to Server 2, then to Client 3. Server 2 detects forwarding is enabled for Client 3 to Client 2, so it forwards the request back to Server 1, which then notifies Client 1. Client 1 then sends another request to Server 1, which is forwarded to Server 2, then to Client 3. Server 2 verifies Client 1 is authorized, then sends a request to Client 2. Client 2 responds, and Server 1 forwards the response to Client 1. Finally, a media plane is established between Client 1 and Client 2.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Server 1 + participant MCPTT Client 2 + participant MCPTT Server 2 + participant MCPTT Client 3 + + Note right of MCPTT Server 2: 3. MCPTT server detects that MCPTT client 2 has call forwarding turned on and that the condition for the forwarding is meet. + + Note left of MCPTT Server 1: 10. MCPTT server verifies that client 1 has been authorized to complete the call forwarding + + Note right of MCPTT Client 2: 17. Media plane established between client 1 and 2 + + MCPTT Client 1->>MCPTT Server 1: 1. MCPTT private call request + MCPTT Server 1->>MCPTT Server 2: 2. MCPTT private call request + Note right of MCPTT Server 2: 3. MCPTT server detects that MCPTT client 2 has call forwarding turned on and that the condition for the forwarding is meet. + MCPTT Server 2->>MCPTT Server 1: 4. MCPTT private call forwarding request + MCPTT Server 1->>MCPTT Client 1: 5. MCPTT private call forwarding request + Note left of MCPTT Client 1: 6. Notify user + MCPTT Client 1->>MCPTT Server 1: 7. MCPTT private call forwarding response + MCPTT Server 1->>MCPTT Server 2: 8. MCPTT private call forwarding response + MCPTT Client 1->>MCPTT Server 1: 9. MCPTT private call request + Note left of MCPTT Server 1: 10. MCPTT server verifies that client 1 has been authorized to complete the call forwarding + MCPTT Server 1->>MCPTT Client 2: 11. MCPTT private call request + MCPTT Server 1-->>MCPTT Client 1: 12. MCPTT progress indication + MCPTT Server 1-->>MCPTT Client 2: 13. MCPTT ringing + MCPTT Client 2-->>MCPTT Client 1: 14. MCPTT ringing + MCPTT Server 1->>MCPTT Client 2: 15. MCPTT private call response + MCPTT Client 2-->>MCPTT Client 1: 16. MCPTT private call response + Note right of MCPTT Client 2: 17. Media plane established between client 1 and 2 + +``` + +Sequence diagram showing simplified private call setup with MCPTT private calls forwarding in manual commencement mode with forwarding in the partner MCPTT systems. The diagram involves two systems: MCPTT system 1 (with Client 1, Server 1, and Client 2) and MCPTT system 2 (with Server 2 and Client 3). The process involves a call request from Client 1 to Server 1, which is forwarded to Server 2, then to Client 3. Server 2 detects forwarding is enabled for Client 3 to Client 2, so it forwards the request back to Server 1, which then notifies Client 1. Client 1 then sends another request to Server 1, which is forwarded to Server 2, then to Client 3. Server 2 verifies Client 1 is authorized, then sends a request to Client 2. Client 2 responds, and Server 1 forwards the response to Client 1. Finally, a media plane is established between Client 1 and Client 2. + +**Figure 7.11.2.3.2-1: Simplified private call setup with MCPTT private calls forwarding in manual commencement mode with forwarding in the partner MCPTT systems** + +1. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 for establishing an MCPTT private call with MCPTT client 3 registered at MCPTT system 2. + +NOTE 1: If the target of the MCPTT private call request is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details are not described. + +2. MCPTT server 1 sends an MCPTT private call request towards MCPTT server 2 for establishing an MCPTT private call with MCPTT client 3 registered at MCPTT system 2. + +3. MCPTT server 2 detects that MCPTT client 3 has immediate call forwarding enabled to MCPTT client 2 registered at MCPTT system 1. + +NOTE 2: If the target of the MCPTT private call forwarding is a functional alias, the procedure resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. For simplicity details of the resolution are not described. + +4. MCPTT server 2 sends an MCPTT private call forwarding request towards MCPTT server 1. + +5. MCPTT server 1 sends an MCPTT private call forwarding request towards MCPTT client 1. + +6. The user at MCPTT client 1 is notified that a call forwarding is in process. +7. MCPTT client 1 sends an MCPTT call private forwarding response back to MCPTT server 1. +8. MCPTT server 1 sends an MCPTT call private forwarding response back to MCPTT server 2. +9. MCPTT client 1 sends an MCPTT private call request towards MCPTT server 1 that includes a call forwarding indication set to true. +10. MCPTT server 1 verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call forwarding request. MCPTT server 1 verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 5, and the forwarding indication is set to true. +11. MCPTT server 1 sends an MCPTT private call request towards MCPTT client 2. +12. Optionally MCPTT server 1 sends an MCPTT progress indication to MCPTT client 1. +13. The user at MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to MCPTT server 1. This step is not required in case of automatic commencement mode. +14. MCPTT server 1 sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode. +15. MCPTT client 2 sends an MCPTT private call response to MCPTT server 1. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call. +16. MCPTT server 1 sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call. +17. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established. + +### 7.11.3 Solution evaluation + +The solution describes MCPTT private call forwarding for MCPTT users in different MCPTT systems. The solution defines enhanced communication between the interconnected MCPTT systems by combining functionality as defined in 3GPP TS 3GPP 23.379 [2] clause 10.7.2.3 and clause 10.7.5. + +## 7.12 Private call transfer between MCPTT systems + +### 7.12.1 General + +This solution addresses the call transfer related aspects of key issue 6 described in clause 5.6 on call forwarding/call transfer between MC systems. The solution provides the possibility of transferring MCPTT private calls between MCPTT users in different MCPTT systems. + +NOTE: This solution describes the procedures for announced private call transfer. Unannounced private call transfer does not require any additional functionality regarding interconnect, so it is covered in this solution as well. + +### 7.12.2 Solution description + +#### 7.12.2.1 Principle + +Currently call transfer for MCPTT private calls is defined within one MCPTT system. The following solution defines the necessary changes to allow call transfer between MCPTT users in different MCPTT systems. + +#### 7.12.2.2 Impact on information flows + +The MCPTT private call transfer related information flows are modified (and marked with highlighting) to cover necessary elements and messages between MCPTT servers to support MCPTT private call transfer for users in different MCPTT systems. Below are the proposed modifications in 3GPP TS 23.379 [2] clause 10.7.6.1.1 and clause 10.7.6.1.3. + +##### 10.7.6.1.1 MCPTT private call transfer request (MCPTT client – MCPTT server) + +Table 10.7.6.1.1-1 describes the information flow MCPTT private call transfer request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT server. + +**Table 10.7.6.1.1-1: MCPTT private call transfer request (MCPTT client to MCPTT server and MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|--------------------------------------|--------|----------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the party requesting the transfer | +| MCPTT ID (see NOTE) | O | The MCPTT ID of the target of the transfer | +| Functional alias (see NOTE) | O | The functional alias of the target of the transfer | +| NOTE: One identity shall be present. | | | + +##### 10.7.6.1.3 MCPTT private call transfer response (MCPTT server – MCPTT client) + +Table 10.7.6.1.3-1 describes the information flow MCPTT private call transfer response from the MCPTT server to the MCPTT client and from the MCPTT server to the MCPTT server. + +**Table 10.7.6.1.3-1: MCPTT private call transfer response (MCPTT server to MCPTT client and MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the party requesting the transfer | +| MCPTT ID | M | The MCPTT ID of the target of the transfer | +| Result | M | Result of the transfer request – success or fail. | + +#### 7.12.3.2 Procedures + +##### 7.12.3.2.1 MCPTT private call announced transfer with target in partner MCPTT system + +The procedure for MCPTT private call announced transfer covers the case where an MCPTT client requests an ongoing MCPTT private call (with or without floor control) to be transferred to another MCPTT user with prior announcement. + +Figure 7.12.3.2.1-1 below illustrates the procedure for MCPTT private call announced transfer with target in partner MCPTT system. + +NOTE 1: The procedure for MCPTT private call unannounced transfer is very similar, the only difference is that steps 2 to 6 are skipped. + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call transfer. +2. MCPTT client 1 is authorized to make private calls to MCPTT client 2. +3. MCPTT client 2 is authorized to make private calls to MCPTT client 3. +4. MCPTT client 2 is authorized to transfer private calls to MCPTT client 3. +5. MCPTT client 2 supports simultaneous sessions for MCPTT private calls as described in 3GPP TS 23.379 [2] clause 10.8. +6. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3, and MCPTT client 2 has the necessary security information to initiate a private call with MCPTT client 3 if end2end encryption is required for the private call. + +![Sequence diagram illustrating MCPTT private call announced transfer with target in partner MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Server 1, MCPTT Client 2 in MCPTT system 1, and MCPTT Server 2, MCPTT Client 3 in MCPTT system 2. The process involves initiating a call, putting it on hold, initiating a new call to a third client, announcing transfer, releasing the new call, putting the first call off hold, and then completing the transfer authorization and media plane establishment.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Server 1 + participant MCPTT Client 2 + participant MCPTT Server 2 + participant MCPTT Client 3 + + Note left of MCPTT Client 1: MCPTT system 1 + Note right of MCPTT Client 3: MCPTT system 2 + + MCPTT Client 1->>MCPTT Client 2: 1. initiate MCPTT private call to MCPTT client 2 + MCPTT Client 1->>MCPTT Client 2: 2. Put call with MCPTT client 1 on hold + MCPTT Client 2->>MCPTT Client 3: 3. Initiate MCPTT private call to MCPTT client 3 + MCPTT Client 2->>MCPTT Client 3: 4. Announce call transfer + MCPTT Client 2->>MCPTT Client 3: 5. Release MCPTT private call with MCPTT client 3 + MCPTT Client 2->>MCPTT Client 1: 6. Put call with MCPTT client 1 off hold + MCPTT Client 2->>MCPTT Server 1: 7. MCPTT call transfer request + MCPTT Server 1->>MCPTT Client 2: 8. MCPTT server 1 verifies that MCPTT client 2 is authorized to perform the call transfer + MCPTT Server 1->>MCPTT Client 2: 9. If target is a functional alias MCPTT server 1 resolves it + MCPTT Server 1->>MCPTT Client 2: 10. MCPTT call transfer response + MCPTT Client 2->>MCPTT Server 1: 11. MCPTT call transfer request + MCPTT Server 1->>MCPTT Client 1: 12. Notify user + MCPTT Server 1->>MCPTT Client 1: 13. MCPTT private call request including transfer indication + MCPTT Server 1->>MCPTT Client 1: 14. MCPTT server 1 verifies that MCPTT Client 1 has been authorized to complete the call transfer + MCPTT Server 1->>MCPTT Server 2: 15. MCPTT private call request + MCPTT Server 2->>MCPTT Client 3: 16. MCPTT private call request + MCPTT Client 3->>MCPTT Server 2: 17. Notify user + MCPTT Server 2->>MCPTT Client 3: 18. MCPTT private call response + MCPTT Server 2->>MCPTT Server 1: 19. MCPTT private call response + MCPTT Server 1->>MCPTT Client 2: 20. MCPTT private call response + MCPTT Client 2->>MCPTT Server 1: 21. MCPTT call transfer response + MCPTT Server 1->>MCPTT Client 2: 22. MCPTT call transfer response + MCPTT Client 2->>MCPTT Client 1: 23. MCPTT client 2 releases the MCPTT private call with MCPTT client 1 + MCPTT Client 1->>MCPTT Client 3: 24. Media plane between MCPTT client1 and MCPTT client 3 is established + +``` + +Sequence diagram illustrating MCPTT private call announced transfer with target in partner MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Server 1, MCPTT Client 2 in MCPTT system 1, and MCPTT Server 2, MCPTT Client 3 in MCPTT system 2. The process involves initiating a call, putting it on hold, initiating a new call to a third client, announcing transfer, releasing the new call, putting the first call off hold, and then completing the transfer authorization and media plane establishment. + +**Figure 7.12.3.2.1-1: MCPTT private call announced transfer with target in partner MCPTT system** + +1. MCPTT client 1 initiates an MCPTT private call to MCPTT client 2 using the normal MCPTT call establishment as described in 3GPP TS 23.379 [2] clause 10.7.2.2. The user at MCPTT client 1 can talk with the user at MCPTT client 2. The user at MCPTT client 2 decides to transfer the call. + +2. The MCPTT user at MCPTT client 2 puts the call with MCPTT user at MCPTT client 1 on hold. + +3. MCPTT client 2 initiates an MCPTT private call to MCPTT client 3 using the normal MCPTT call establishment procedures as described in 3GPP TS 23.379 [2] clause 10.7.2.3. + +NOTE 2: The solution for private call using functional alias towards a partner MC system is defined in clause 7.8. + +4. The user at MCPTT client 2 can talk with the user at MCPTT client 3 and announces the call transfer. + +5. The MCPTT client 2 releases the MCPTT private call with MCPTT client 3 using the normal MCPTT call release procedure as described in 3GPP TS 23.379 [2] clause 10.7.2.3. This step can occur at any time after step 4. + +6. The MCPTT user at MCPTT client 2 puts the call with MCPTT client 1 off hold and confirms that the call will be transferred. + +7. The MCPTT client 2 sends an MCPTT call transfer request to the MCPTT server 1. + +8. The MCPTT server 1 verifies that MCPTT client 2 is authorized to transfer the MCPTT private call to MCPTT client 3. This check is based on entries in the user profile of the user at MCPTT client 2. First, the MCPTT server 1 checks the value of the "Allow private call transfer" entry. If it is false, the authorization check has failed, and the procedure continues with step 10. Otherwise, the MCPTT server 1 checks if the "Authorised to transfer private calls to any MCPTT user" entry is true. If this is the case the check has passed, and for target type of MCPTT ID the procedure continues with step 10 and for target ID type of functional alias the procedure continues with step 9. The subsequent checking depends on the type of target ID. If the target ID is a MCPTT ID, the MCPTT server 1 checks for a matching entry of the target MCPTT ID in the "List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, if no matching entry is found the check has failed, for any outcome the procedure continues with step 10. If the target ID is a functional alias, the MCPTT server 1 checks for a matching entry of the target functional alias in the "List of functional aliases that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, and the procedure continues with step 9. If no matching entry is found, the authorization check has failed, and the procedure continues with step 10. +9. If the target of the MCPTT private call transfer is a functional alias instead of an MCPTT ID the MCPTT server 1 resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. + +NOTE 3: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call transfer is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria. The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected. + +10. If the authorization check has failed, or the target of the transfer is a functional alias that is not active, or the target of the transfer is a functional alias that is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call transfer is cancelled, and the MCPTT server 1 sends an MCPTT private call transfer response with result "fail" back to MCPTT client 2. The MCPTT private call between MCPTT client 1 and MCPTT client 2 remains up, and the procedure stops. Otherwise, the procedure continues. + +11. The MCPTT server 1 sends an MCPTT call transfer request towards the MCPTT client 1. + +12. The user at MCPTT client 1 is notified that a call transfer is in progress. + +13. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server 1 that includes a call transfer indication set to true. + +14. The MCPTT server 1 verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call transfer request based on the fact that the transfer indication is present and set to true in the MCPTT private call request. + +NOTE 4: For call transfer the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 3. + +15. The MCPTT server 1 sends an MCPTT call request to MCPTT server 2. + +16. The MCPTT server 2 sends an MCPTT call request to MCPTT client 3. + +NOTE 5: MCPTT server 2 detects that the private call request contains a transfer indication set to true and therefore skips the authorization checking. + +17. The user at MCPTT client 3 is notified about the incoming call. + +18. MCPTT client 3 sends an MCPTT private call response back to the MCPTT server 2. + +19. MCPTT server 2 sends an MCPTT private call response back to the MCPTT server 1. + +20. The MCPTT server 1 forwards the MCPTT private call response towards MCPTT client 1. + +21. MCPTT client 1 sends an MCPTT call transfer response back to MCPTT server 1. + +22. The MCPTT server 1 forwards the MCPTT private transfer response towards MCPTT client 2. + +23. MCPTT client 2 initiates release of the private call between MCPTT client 1 and MCPTT client 2 as described in subclause 10.7.2.3. +24. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established. + +##### 7.12.3.2.2 MCPTT private call announced transfer with transferring MCPTT user in partner MCPTT system + +The procedure for MCPTT private call announced transfer covers the case where an MCPTT client requests an ongoing MCPTT private call (with or without floor control) to be transferred to another MCPTT user with prior announcement. + +Figure 7.12.3.2.2-1 below illustrates the procedure for MCPTT private call announced transfer with transferring MCPTT user in partner MCPTT system. + +NOTE 1: The procedure for MCPTT private call unannounced transfer is very similar, the only difference is that steps 2 to 6 are skipped. + +Pre-conditions: + +1. MCPTT client 3 is authorized to use call transfer. +2. MCPTT client 1 is authorized to make private calls to MCPTT client 3. +3. MCPTT client 3 is authorized to make private calls to MCPTT client 2. +4. MCPTT client 3 is authorized to transfer private calls to MCPTT client 2. +5. MCPTT client 3 supports simultaneous sessions for MCPTT private calls as described in 3GPP TS 23.379 [2] clause 10.8. +6. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3, and MCPTT client 3 has the necessary security information to initiate a private call with MCPTT client 2 if end2end encryption is required for the private call. + +![Sequence diagram illustrating the MCPTT private call announced transfer procedure between two MCPTT systems. The diagram shows the interaction between MCPTT Client 1, MCPTT Server 1, MCPTT Client 2 in MCPTT system 1, and MCPTT Server 2, MCPTT Client 3 in MCPTT system 2. The sequence starts with Client 1 initiating a call to Client 3, followed by putting the call on hold, initiating a new call to Client 2, announcing the transfer, and then completing the transfer of the call from Client 1 to Client 2 via Client 3's request.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Server 1 + participant MCPTT Client 2 + participant MCPTT Server 2 + participant MCPTT Client 3 + + Note over MCPTT Client 1, MCPTT Server 1, MCPTT Client 2: MCPTT system 1 + Note over MCPTT Server 2, MCPTT Client 3: MCPTT system 2 + + MCPTT Client 1->>MCPTT Client 3: 1. initiate MCPTT private call to MCPTT Client 3 + MCPTT Client 3->>MCPTT Client 1: 2. Put call with MCPTT client 1 on hold + MCPTT Client 3->>MCPTT Client 2: 3. Initiate MCPTT private call to MCPTT client 2 + MCPTT Client 2->>MCPTT Client 3: 4. Announce call transfer + MCPTT Client 3->>MCPTT Client 2: 5. Release MCPTT private call with MCPTT client 2 + MCPTT Client 3->>MCPTT Client 1: 6. Put call with MCPTT client 1 off hold + MCPTT Client 3->>MCPTT Server 2: 7. MCPTT call transfer request + Note right of MCPTT Server 2: 8. MCPTT server verifies that MCPTT Client 3 is authorized to perform the call transfer + Note right of MCPTT Server 2: 9. If target is a functional alias MCPTT server resolves it + MCPTT Server 2-->>MCPTT Client 3: 10. MCPTT call transfer Response (fail) + MCPTT Server 2->>MCPTT Server 1: 11. MCPTT call transfer request + MCPTT Server 1->>MCPTT Client 1: 12. MCPTT call transfer request + Note left of MCPTT Client 1: 13. Notify user + MCPTT Client 1->>MCPTT Server 1: 14. MCPTT private call request including transfer indication + Note right of MCPTT Server 1: 16. MCPTT server verifies that MCPTT Client 1 has been authorized to complete the call transfer + MCPTT Server 1->>MCPTT Client 2: 15. MCPTT private call request + Note left of MCPTT Client 2: 18. Notify user + MCPTT Client 2->>MCPTT Server 1: 19. MCPTT private call response + MCPTT Server 1->>MCPTT Client 1: 20. MCPTT private call response + MCPTT Client 1->>MCPTT Server 1: 21. MCPTT call transfer response + MCPTT Server 1->>MCPTT Server 2: 22. MCPTT call transfer response + MCPTT Server 2->>MCPTT Client 3: 23. MCPTT call transfer response + MCPTT Client 3->>MCPTT Client 1: 24. MCPTT client 3 releases the MCPTT private call with MCPTT client 1 + Note over MCPTT Client 1, MCPTT Client 2: 25. Media plane between MCPTT client 1 and MCPTT client 2 is established + +``` + +Sequence diagram illustrating the MCPTT private call announced transfer procedure between two MCPTT systems. The diagram shows the interaction between MCPTT Client 1, MCPTT Server 1, MCPTT Client 2 in MCPTT system 1, and MCPTT Server 2, MCPTT Client 3 in MCPTT system 2. The sequence starts with Client 1 initiating a call to Client 3, followed by putting the call on hold, initiating a new call to Client 2, announcing the transfer, and then completing the transfer of the call from Client 1 to Client 2 via Client 3's request. + +**Figure 7.12.3.2.2-1: MCPTT private call announced transfer transferring MCPTT user in partner MCPTT system** + +1. MCPTT client 1 initiates an MCPTT private call to MCPTT client 3 using the normal MCPTT call establishment as described in 3GPP TS 23.379 [2] clause 10.7.2.3. The user at MCPTT client 1 can talk with the user at MCPTT client 3. The user at MCPTT client 3 decides to transfer the call. + +NOTE 2: The solution for private call using functional alias towards a partner MC system is defined in clause 7.8. + +2. The MCPTT user at MCPTT client 3 puts the call with MCPTT user at MCPTT client 1 on hold. + +3. MCPTT client 3 initiates an MCPTT private call to MCPTT client 2 using the normal MCPTT call establishment procedures as described in 3GPP TS 23.379 [2] clause 10.7.2.3. + +NOTE 3: The solution for private call using functional alias towards a partner MC system is defined in clause 7.8. + +4. The user at MCPTT client 3 can talk with the user at MCPTT client 2 and announce the call transfer. + +5. The MCPTT client 3 releases the MCPTT private call with MCPTT client 2 using the normal MCPTT call release procedure as described in 3GPP TS 23.379 [2] clause 10.7.2.3. This step can occur at any time after step 4. +6. The MCPTT user at MCPTT client 3 puts the call with MCPTT client 1 off hold and confirms that the call will be transferred. +7. The MCPTT client 3 sends an MCPTT call transfer request to the MCPTT server 2. +8. The MCPTT server 2 verifies that MCPTT client 3 is authorized to transfer the MCPTT private call to MCPTT client 2. This check is based on entries in the user profile of the user at MCPTT client 3. First, the MCPTT server 2 checks the value of the "Allow private call transfer" entry. If it is false, the authorization check has failed, and the procedure continues with step 10. Otherwise, the MCPTT server 2 checks if the "Authorised to transfer private calls to any MCPTT user" entry is true. If this is the case the check has passed, and for target type of MCPTT ID the procedure continues with step 10 and for target ID type of functional alias the procedure continues with step 9. The subsequent checking depends on the type of target ID. If the target ID is an MCPTT ID, the MCPTT server 2 checks for a matching entry of the target MCPTT ID in the "List of MCPTT users that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, if no matching entry is found the check has failed, for any outcome the procedure continues with step 10. If the target ID is a functional alias, the MCPTT server 2 checks for a matching entry of the target functional alias in the "List of functional aliases that the MCPTT user is authorised to use as targets for call transfer" list. If a matching entry is found, the check has passed, and the procedure continues with step 9. If no matching entry is found, the authorization check has failed, and the procedure continues with step 10. +9. If the target of the MCPTT private call transfer is a functional alias instead of an MCPTT ID the MCPTT server 2 resolves the functional alias to the corresponding MCPTT ID for which the functional alias is active. + +NOTE 4: Depending on implementation the MCPTT server can apply additional call restrictions and decide whether the call is allowed to proceed with the resolved MCPTT ID(s) (e.g. whether the MCPTT ID is within the allowed area of the functional alias). If the MCPTT server detects that the functional alias used as the target of the MCPTT private call transfer is simultaneously active for multiple MCPTT users, then the MCPTT server can proceed by selecting an appropriate MCPTT ID based on some selection criteria. The selection of an appropriate MCPTT ID is left to implementation. The selection criteria can include rejection of the call, if no suitable MCPTT ID is selected. + +10. If the authorization check has failed, or the target of the transfer is a functional alias that is not active, or the target of the transfer is a functional alias that is simultaneously active by multiple users and the outcome of the selection is a rejection, the MCPTT private call transfer is cancelled, and the MCPTT server 2 sends an MCPTT private call transfer response with result "fail" back to MCPTT client 3. The MCPTT private call between MCPTT client 3 and MCPTT client 2 remains up, and the procedure stops. Otherwise, the procedure continues. + +11. The MCPTT server 2 sends an MCPTT call transfer request towards the MCPTT server 1. + +12. The MCPTT server 1 sends an MCPTT call transfer request towards the MCPTT client 1. + +13. The user at MCPTT client 1 is notified that a call transfer is in progress. + +14. MCPTT client 1 sends an MCPTT call transfer response back to the MCPTT server 1. + +15. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server 1 that includes a call transfer indication set to true. + +16. The MCPTT server 1 verifies that MCPTT client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call transfer request based on the fact that the transfer indication is present and set to true in the MCPTT private call request. + +NOTE 5: For call transfer the MCPTT server does not check if the initial originating MCPTT user at MCPTT client 1 is authorized to make an MCPTT private call to the final target MCPTT user at MCPTT client 2. + +17. The MCPTT server 1 sends an MCPTT call request to MCPTT client 3. + +18. The user at MCPTT client 2 is notified about the incoming call. + +19. MCPTT client 2 sends an MCPTT private call response back to the MCPTT server 1. + +20. The MCPTT server 1 forwards the MCPTT private call response towards MCPTT client 1. +21. MCPTT client 1 sends an MCPTT call transfer response back to the MCPTT server 1. +22. The MCPTT server 1 sends an MCPTT call transfer response back to the MCPTT server 2. +23. The MCPTT server 2 sends an MCPTT call transfer response back to the MCPTT client 3. +24. MCPTT client 3 initiates release of the private call between MCPTT client 3 and MCPTT client 1 as described in 3GPP TS 23.379 [2] clause 10.7.2.3. +25. The media plane for communication between MCPTT client 1 and MCPTT client 2 is established. + +### 7.12.3 Solution evaluation + +The solution describes private call transfer MCPTT for MCPTT users in different MCPTT systems. The solution defines enhanced communication between the interconnected MCPTT systems by combining functionality as defined in 3GPP TS 3GPP 23.379 [2] clauses 10.7.2.3 and 10.7.6. + +# --- 8 Overall evaluation + +## 8.1 Key issue and solution evaluation + +### 8.1.1 Introduction + +All the key issues and solutions specified in this technical report are listed in table 8.1.2-1. It includes the mapping of the key issues (clause 5) to the solutions (clause 7) and corresponding solution evaluations. + +In addition, table 8.1.2-1 lists the impacts to other working groups that will need consideration during the Rel-18 normative phase. + +### 8.1.2 Results + +**Table 8.1.2-1: Key issues, solutions, and solution evaluations** + +| Key issues | Solution | Evaluation (clause reference) | Dependency on other working groups | +|-------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------------|-------------------------------------------| +| Key issue 1 - Optimize the connectivity between MC systems | Clause 7.7 Optimize the connectivity between MC systems | Clause 7.7.3 | None | +| Key issue 2 - Functional alias handling | Clause 7.3 Private call using functional alias towards a partner MC system | Clause 7.3.3 | None | +| | Clause 7.4 Functional alias support for migrated users | Clause 7.4.3 | None | +| | Clause 7.8 Private call using functional alias towards a partner MC system | Clause 7.8.3 | None | +| Key issue 3 - Group communication between MC systems | Clause 7.5 Migration during an ongoing group communication | Clause 7.5.3 | None | +| Key issue 4 - Location information with multiple MC systems | Clause 7.1 Solution on functional architecture enhancements to support location information | Clause 7.1.3 | None | +| | Clause 7.2 Solution on location information | Clause 7.2.3 | None | +| Key issue 5 - Quick migration towards another MC system | Clause 7.6 Migration during an ongoing private communication | Clause 7.6.3 | None | +| Key issue 6 - Call forwarding/transfer between MC systems | Clause 7.11 Private call forwarding between MCPTT systems | Clause 7.11.3 | None | +| | Clause 7.12 Private call transfer between MCPTT systems | Clause 7.12.3 | None | +| Key issue 7 - IP connectivity between MC systems | Clause 7.9 Solution on IP connectivity between MC systems | Clause 7.9.3 | None | +| Key issue 8 – Offline-Migration | Clause 7.10 Solution on migration without interconnection between two MC systems | Clause 7.10.3 | None | + +# 9 Conclusions + +This technical report fulfills the objective to develop solutions for specific interconnection and migration needs for railways which were not satisfied yet. It identifies enhancements to be included in the technical specifications for MCPTT (3GPP TS 23.379 [2]), MCVideo (3GPP TS 23.281 [3]), MCData (3GPP TS 23.282 [4]) and in the common functional architecture (3GPP TS 23.280 [5]). + +The results from the study will be considered for follow-up normative work in Rel-18 as follows: + +- 1) The solution on functional architecture enhancements to support location information (clause 7.1) and the solution on providing location information (clause 7.2) may be used. +- 2) The solutions on private call using functional alias towards a partner MC system (clause 7.3 and clause 7.8) will be used as basis to define a proper mechanism. + +- 3) The solutions describing migration during an ongoing communication (clause 7.4 and clause 7.5) will be used as basis to define proper procedures. +- 4) The solutions on addressing the connectivity between MC systems to optimize media and signalling routing (clause 7.7) and on IP connectivity between MC systems (clause 7.9) provides the necessary guidance to cover rail communication use cases excluding the primary MC system for communication routing in the migration context. +- 5) The solution on migration without interconnection between two MC systems (clause 7.10) will be used to enable an authorized MC service user to migrate to another MC system, where there is no interconnection between the primary and the partner MC system. +- 6) The solution on private call forwarding between MCPTT systems (clause 7.11) will be used to forward MCPTT private calls towards an MCPTT user in a different MCPTT system. + +No dependencies to other 3GPP groups were identified in the overall evaluation (clause 8) which are required for fulfilling the solutions listed above. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2020-08 | SA6#39-e | | | | | S6-201345 (TR skeleton) | 0.0.0 | +| 2020-09 | SA6#39-e | | | | | S6-201346, S6-201347, S6-201351, S6-201352, S6-201353, S6-201355, S6-201356, S6-201357, S6-201565 | 0.1.0 | +| 2021-01 | SA6#41-e | | | | | S6-210092, S6-210093, S6-210204, S6-210205 | 0.2.0 | +| 2021-04 | SA6#42-bis-e | | | | | S6-210772, S6-210776, S6-210794, S6-210957, S6-210958, S6-210972 | 0.3.0 | +| 2021-07 | SA6#44-e | | | | | S6-211599, S6-211601, S6-211602, S6-211603, S6-211604, S6-211605, S6-211749 | 0.4.0 | +| 2021-07 | | | | | | Correction of the cover page | 0.4.1 | +| 2021-09 | SA6#45-e | | | | | S6-211886, S6-211887, S6-211889 | 0.5.0 | +| 2021-09 | SA#93-e | SP-210950 | | | | Presentation for information at SA#93-e | 1.0.0 | +| 2021-10 | SA6#45-bis-e | | | | | S6-212236, S6-212253, S6-212254, S6-212364, S6-212473 | 1.1.0 | +| 2021-11 | SA6#46-e | | | | | S6-212566, S6-212616, S6-212617, S6-212695, S6-212696, S6-212697 | 1.2.0 | +| 2022-02 | SA6#47-e | | | | | S6-220058, S6-220071, S6-220072, S6-220304 | 1.3.0 | +| 2022-03 | SA#95-e | SP-220092 | | | | Presentation for approval at SA#95-e | 2.0.0 | +| 2022-03 | SA#95-e | SP-220092 | | | | MCC Editorial update for publication after TSG SA approval (SA#95) | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-96/raw.md b/raw/rel-18/23_series/23700-96/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4853da68ff2146bc5d77d4a8bcd51d0868ef3f5e --- /dev/null +++ b/raw/rel-18/23_series/23700-96/raw.md @@ -0,0 +1,1219 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on 5G-enabled fused location service capability exposure; (Release 18)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +--- + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the bottom by a red, curved line. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Architectural assumptions and requirements ..... | 9 | +| 4.1 Architectural assumptions..... | 9 | +| 4.2 Architectural requirements..... | 9 | +| 5 Key issues ..... | 9 | +| 5.1 Key issue #1: Architecture enhancement of application enablement for location..... | 9 | +| 5.2 Key issue #2: Support of LCS QoS..... | 10 | +| 5.3 Key issue #3: Location service differentiation..... | 10 | +| 5.4 Key issue #4: Void..... | 10 | +| 5.5 Key issue #5: Initialization and configuration for fused location service..... | 10 | +| 6 Void..... | 11 | +| 7 Solutions..... | 12 | +| 7.0 Mapping of solutions to key issues ..... | 12 | +| 7.1 Solution #1: Standalone functional architecture for fused location service..... | 12 | +| 7.1.1 Solution description..... | 12 | +| 7.1.1.1 Functional architecture ..... | 12 | +| 7.1.1.2 Functional components and reference points..... | 13 | +| 7.1.1.3 Merged Architecture to support interaction between FLS and SEAL LMS..... | 14 | +| 7.1.2 Solution evaluation..... | 15 | +| 7.2 Solution #2: Support of both LCS and SUPL at Fused Location Function ..... | 15 | +| 7.2.1 Solution description..... | 15 | +| 7.2.1.1 Architectural models..... | 15 | +| 7.2.2 Solution evaluation..... | 16 | +| 7.3 Solution #3: Functional architecture for fused location service leveraging SEAL location management ..... | 16 | +| 7.3.1 Solution description..... | 16 | +| 7.3.1.1 Functional architecture ..... | 16 | +| 7.3.1.2 Functional components and reference points..... | 17 | +| 7.3.1.3 Deployment models ..... | 18 | +| 7.3.2 Solution evaluation..... | 19 | +| 7.4 Solution #4: Location service registration ..... | 19 | +| 7.4.1 Solution description..... | 19 | +| 7.4.2 Solution evaluation..... | 20 | +| 7.5 Solution #5: Location profiling for supporting fused location service enablement..... | 20 | +| 7.5.1 Solution description..... | 20 | +| 7.5.1.1 General..... | 20 | +| 7.5.1.2 Procedure ..... | 21 | +| 7.5.2 Solution evaluation..... | 23 | +| 7.6 Solution #6: Location service configuration ..... | 23 | +| 7.6.1 Solution description..... | 23 | +| 7.6.1.1 Service flow for fused location service configuration..... | 23 | +| 7.6.2 Solution evaluation..... | 25 | +| 7.7 Solution #7: Location QoS based location sources and positioning methods selection ..... | 25 | +| 7.7.1 Solution description..... | 25 | +| 7.7.1.1 Procedure of location QoS based location sources and positioning methods selection ..... | 26 | +| 7.7.2 Solution evaluation..... | 26 | +| 7.8 Solution #8: Architecture for fused location service..... | 27 | +| 7.8.1 Solution description..... | 27 | +| 7.8.1.1 Functional architecture ..... | 27 | + +| | | | +|-----------------|-------------------------------------------------|-----------| +| 7.8.1.2 | Functional components and reference points..... | 27 | +| 7.8.2 | Solution evaluation..... | 28 | +| 8 | Overall evaluation..... | 28 | +| 8.1 | General..... | 28 | +| 8.2 | Architecture enhancements..... | 29 | +| 8.3 | Solution evaluations..... | 29 | +| 8.3.1 | General..... | 29 | +| 8.3.2 | Overall evaluation of key issue#1..... | 29 | +| 8.3.3 | Overall evaluation of key issue#2..... | 30 | +| 8.3.4 | Overall evaluation of key issue#3..... | 30 | +| 8.3.5 | Overall evaluation of key issue#4..... | 30 | +| 8.3.6 | Overall evaluation of key issue#5..... | 31 | +| 8.3.7 | Overall evaluation of key issue#6..... | 31 | +| 9 | Conclusions..... | 31 | +| 9.1 | General conclusions..... | 31 | +| 9.2 | Conclusions for normative work..... | 31 | +| 9.2.1 | General conclusions..... | 31 | +| 9.2.2 | Architecture enhancement conclusions..... | 32 | +| 9.2.3 | Solution conclusions..... | 32 | +| Annex A: | Change history ..... | 34 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +*In drafting the TS/TR, pay particular attention to the use of modal auxiliary verbs! TRs shall not contain any normative provisions.* + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document + +**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +The present document studies and evaluates the application architecture aspects and solutions to address potential new and enhanced location capabilities for vertical application enabler, including the following aspects: + +- Enabling location performance (accuracy, availability and latency) enhancements through combined use and fusion of 3GPP and non-3GPP location technologies at the application layer; +- Identification and classification of location related requirements (including location QoS) for vertical application services; +- Architecture enhancement leveraging 5G positioning and location services; +- Enabling location sources and positioning methods selection based on the requested location QoS; +- Initialization and configuration for fused location service; +- Enabling value-added location service capabilities exposure to vertical applications; +- Enhancements on SEAL location management addressing the aspects above. + +NOTE: This study will not duplicate solutions already available in Core Network and RAN. + +# 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.261: "Service requirements for next generation new services and markets; Stage 1". +- [3] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)". +- [4] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". +- [5] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [6] 3GPP TS 38.305: "Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". +- [7] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains; Stage 1". +- [8] 3GPP TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP; Stage 1". +- [9] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1". +- [10] Open Mobile Alliance, OMA AD SUPL: "Secure User Plane Location Architecture", (). +- [11] Open Mobile Alliance, OMA AD MLS: "Mobile Location Service Architecture", (). +- [12] 3GPP TS 23.502: " Procedures for the 5G System (5GS); Stage 2". + +- [13] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [14] 3GPP TS 29.572: "Location Management Services; Stage 3". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +For the purposes of the present document, the following terms and definitions given in TS 22.261 [2] apply: + +**5G enhanced positioning area:** see TS 22.261 [2]. + +**5G positioning service area:** see TS 22.261 [2]. + +For the purposes of the present document, the following terms and definitions given in TS 23.271 [3] apply: + +**Current Location:** see TS 23.271 [3]. + +**LCS Server:** see TS 23.271 [3]. + +**Location Estimate:** see TS 23.271 [3]. + +**Velocity:** see TS 23.271 [3]. + +For the purposes of the present document, the following terms and definitions given in TS 23.273 [4] apply: + +**LCS Client:** see TS 23.273 [4]. + +For the purposes of the present document, the following terms and definitions given in TS 23.501 [5] apply: + +**5G Access Network:** see TS 23.501 [5]. + +**5G Core Network:** see TS 23.501 [5]. + +**5G System:** see TS 23.501 [5]. + +**NG-RAN:** see TS 23.501 [5]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|------------------------------------| +| GMLC | Gateway Mobile Location Centre | +| LCS | LoCation Services | +| LDR | Location Deferred Request | +| LMF | Location Management Function | +| LPP | LTE Positioning Protocol | +| MO-LR | Mobile Originated Location Request | +| MT-LR | Mobile Terminated Location Request | +| NI-LR | Network Induced Location Request | +| SLP | SUPL Location Platform | +| SUPL | Secure User Plane Location | +| TNAN | Trusted Non-3GPP Access Network | +| UNAN | Untrusted Non-3GPP Access Network | + +# --- 4 Architectural assumptions and requirements + +## 4.1 Architectural assumptions + +For discussions of architecture aspects of application enablement in this document, the following architectural assumptions apply: + +- The positioning methods include the standard positioning methods supported for NG-RAN access as specified in clause 4.3 in 3GPP TS 38.305 [6], and the positioning methods supported for non-3GPP access as specified in clause 5.3.1 in 3GPP TS 23.273 [4]. +- The source of location may include other standard location service (non-3GPP location service of e.g. OMA) from the third party. +- The PLMN operator must be able to protect user location data and privacy when the application enablement architecture is within the PLMN operator domain. + +## 4.2 Architectural requirements + +The following are the architectural requirements to support 5G-enabled fused location service. + +- The application layer architecture should take the baseline location management server specified in 3GPP TS 23.434[13] and the location resources and positioning methods should not conflict with the existing one in TS 23.501[5] and 23.502[12]. +- The application layer architecture shall provide mechanisms to enable location performance (accuracy, availability and latency) enhancements through combined use and fusion of 3GPP and non-3GPP location technologies; +- The application layer architecture shall enhance the SEAL location-related architecture to provide more accurate UE location report. And enhance the LM-UU interface to transfer the fused location information. + +# --- 5 Key issues + +## 5.1 Key issue #1: Architecture enhancement of application enablement for location + +The 3GPP TS 22.261 [2], 3GPP TS 22.104 [7], 3GPP TS 22.125 [8] have specified high accuracy positioning requirements of 5G for the support of various vertical applications. The major aspects of the study are the support of fusion or combination of different location technologies and the value added location capabilities at the application enabler, so that to enable the enhanced performance and meeting the vertical's needs. + +It should be studied whether and how the SEAL location-related architecture enhancement or new architecture model is needed based on evaluations of existing location management architectures, functional entities and capabilities with following aspects: + +- Functional entit(ies) supporting the combined use and fusion of different location technologies at the application layer; +- Architecture enhancement addressing the consideration of flexibility, scalability and reliability; +- Support for high-accuracy positioning based on LCS and 5G network exposure; +- Providing value-added location services to accommodate new service requirements and the evolving application enablement capabilities; +- Architecture aspects that make sure UE provided location is not spoofed; +- Architecture aspects that comply with local, national, and regional location privacy requirements; +- Architecture aspects exploiting edge computing capabilities including EDGEAPP and 5GC edge capabilities. + +The MNO may deploy both LCS and SUPL due to deployment and cost considerations while achieving consistent location performances. It is for further study: + +- The possible application layer architectural models to support both SUPL and LCS. +- The potential scenarios that LCS and SUPL location towards the same target UE are received by application layer at the same time. +- The architectural aspects to support selection or coordination between LCS and SUPL at the application layer when both location services are supported. + +## 5.2 Key issue #2: Support of LCS QoS + +According to 3GPP TS 23.273 [4] and 3GPP TS 22.071 [9], the LCS QoS which is characterised by LCS QoS Class, Accuracy and Response Time may be required by the application (LCS client) for location requests. For certain LCS services the LCS QoS Class is non-negotiable. + +To support the LCS QoS the following aspects need to be studied: + +- How to support invocation of LCS service (as defined by SA2) with a required LCS QoS, including how and when the LCS QoS attributes are specified in an application scenario, and how to potentially use the LCS QoS attributes differently for different vertical scenarios; +- How to support the identification of an appropriate LCS QoS requirement between all interested parties.; +- How to potentially retrieve the continuity and consistency of LCS QoS for the vertical applications; +- How to potentially support the negotiation of required LCS QoS that is application driven. + +## 5.3 Key issue #3: Location service differentiation + +Within the core network the LCS client has been categorized (as LCS client type) such that the privacy check, positioning methods schemes and other procedures can be differentiated. + +Within the application enabler layer there are also the dimensions to distinguish location services so that the service handling (e.g. priority information, service coverage, geographical area and other information used to invoke LCS service, the selection of location source, etc.) is differentiated. Also the location services distinguished based on use cases and regulation need to be considered. + +It is for further study: + +- The possible dimensions to distinguish location service in application enabler layer and how to enable the location service differentiation. + +## 5.4 Key issue #4: Void + +## 5.5 Key issue #5: Initialization and configuration for fused location service + +The application enabler needs to consider how the location service based on multiple or various location sources is initiated and configured. + +This key issue aims to study: + +- How to initiate and start the fused location service for a target UE in different scenarios, environment, network condition, type of service and etc. +- How to initiate and start the fused location service such that the location capabilities of target UE and the application layer location service can be coordinated. +- What configurations are needed for the initialization of fused location service and how. +- What application layer sessions are established for the fused location service and how. + +## 5.6 Key issue #6: Value-Added Location Services + +How does the FLS/SEAL LMS get the UE location from 3GPP and non-3GPP defined accesses are described in this TR, TS23.273 and TS23.434. A lot of value-added location services provide location enhanced functions to the upper layer consumer. Mobile internet and industrial application can use one or more value-added location services. Different value-added location services may require different architectures, interfaces, functions and procedures. + +The following aspects can be addressed in the study: + +- Identify which value-added service is to be studied and provide the functional description? + +The following value-added location services can be studied, and more value-added services can be further included and studied in the solution part (not exhausted): + +- Location format mapping +- Location Event Trigger provision, invoke, revoke +- Periodic and or event Triggered location reporting +- Real time location information Pushing +- Geofencing +- (Indoor) Map provision +- Location Alerting +- Real time Tracing request or playback (continuous locations in a map) +- History Trace request or playback +- Time information of the first entering and the last leaving an area (e.g. working campus) +- The length of time to stay in an area +- The times to re-enter and re-leave an area +- Location information analysis +- Heatmap +- Speed +- Heading Direction +- Identify whether the value-added service as listed above can be supported based on the procedures defined for the SEAL LMS and FLS. + +NOTE: Existing location service may be enhanced if not fully supported. + +# --- 6 Void + +# 7 Solutions + +## 7.0 Mapping of solutions to key issues + +**Table 7.0-1 Mapping of solutions to key issues** + +| | KI # 1 | KI # 2 | KI # 3 | KI # 4 | KI # 5 | KI # 6 | +|--------|--------|--------|--------|--------|--------|--------| +| Sol #1 | X | | | | | | +| Sol #2 | X | | | | | | +| Sol #3 | X | | | | | | +| Sol #4 | | | | | X | | +| Sol #5 | | | X | | | | +| Sol #6 | | | | | X | | +| Sol #7 | | X | | | | | +| Sol #8 | X | | | | | | + +## 7.1 Solution #1: Standalone functional architecture for fused location service + +### 7.1.1 Solution description + +This solution addresses key issue #1: Architecture enhancement of application enablement for location. + +#### 7.1.1.1 Functional architecture + +The figure 7.1.1.1-1 identifies the architecture of fused location service enabled by 5GS. + +![Figure 7.1.1.1-1: Functional architecture of fused location service. The diagram shows a Target UE on the left containing a Fused Location Client. The client connects via FLS-1 to a central Fused Location Function (FLF). Above the FLF is an Application Specific Server connected via FLS-2. To the right of the FLF is a Database connected via FLS-3. Below the FLF are four components: NEF (connected via Nnef), GMLC (connected via Le), SLP (connected via Le), and a 3rd Party Location Server (connected via FLS-4). Above the FLF, there are two boxes labeled 'Non-3GPP Defined Access' and '3GPP Access'.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 7.1.1.1-1: Functional architecture of fused location service. The diagram shows a Target UE on the left containing a Fused Location Client. The client connects via FLS-1 to a central Fused Location Function (FLF). Above the FLF is an Application Specific Server connected via FLS-2. To the right of the FLF is a Database connected via FLS-3. Below the FLF are four components: NEF (connected via Nnef), GMLC (connected via Le), SLP (connected via Le), and a 3rd Party Location Server (connected via FLS-4). Above the FLF, there are two boxes labeled 'Non-3GPP Defined Access' and '3GPP Access'. + +**Figure 7.1.1.1-1: Functional architecture of fused location service** + +The architecture is composed of logical function modules that are not necessarily physical entities and can reside in or co-locate with existing application layer entities as appropriate. + +In the architecture, the Fused Location Server (FLS) and Application Specific Server can be within the MNO domain or third party service provider domain. + +The FLS architecture supports multiple possible sources of location information including: + +- AMF location service exposed by NEF (as defined in 3GPP TS 23.502 [12]); +- LCS location retrieved from either NEF or GMLC (as defined in 3GPP TS 23.273 [4]); +- SUPL location retrieved from SLP (as defined in OMA AD SUPL [10]); + +NOTE: Whether and how the SUPL location service can be exposed by 5GC is within the remit of SA2. + +- Certain RAT-independent positioning retrieved from 3rd party location server or Fused Location Client. +- Retrieve the target UE Positioning via the FLS-1 interface. + +**Editor's Note:** It is FFS to show the relationship of Fused Location Function with SEAL-LM. + +#### 7.1.1.2 Functional components and reference points + +The Fused Location Server provides location information of the target UE based on positioning or location data retrieved from one or multiple location sources. The Fused Location Server can get the location information via the non-3GPP defined access from the Fused Location Client and additionally can get location information via the 3GPP access. The Fused Location Server selects one or more access types, one or more location methods, and Control Plane /User Plane (e.g. SUPL [10]) methods based on the requested location QoS. The Fused Location Server provides a normalized description of location data to the application-specific server (e.g. of ecosystem partners) through the northbound API. + +For the non-3GPP defined accesses, the FLS also needs to support the five types of interaction with the Fused Location Client to retrieve the location information via the non-3GPP defined accesses: + +- Get the UE location information; +- Provide location notification to the FLC in the target UE and get a guarantee to get location information from the target UE; +- Install location event triggers in the FLC in the target UE to support the target UE terminated deferred location information; + +The 3rd Party Location Server provides the location of a certain location technology (typically the network-based positioning) e.g. Bluetooth. + +The Fused Location Client represents the client of the target UE providing the UE-based positioning via the non-3GPP defined access and location-related information and provides the UE location information via the non-3GPP defined access to the Fused Location Server via an IP connection. + +NOTE 1: How does the Fused Location Client get the UE location information via the non-3GPP defined access is out of scope of 3GPP. + +The NEF (as defined in 3GPP TS 23.501 [5]) exposes location service of 5GC when Fused Location Server is external to MNO domain. + +The GMLC (as defined in 3GPP TS 23.273 [4]) provides LCS when Fused Location Server is within the MNO domain. + +The SLP (as defined in OMA AD SUPL [10]) provides location of SUPL network. + +The interfaces are described as followed: + +**FLS-1:** Reference point supporting location reporting, location determination, location management and exchange of location contextual information (e.g. UE ID, location capabilities of the non-3GPP defined access, the available non-3GPP defined accesses ) over application layer transactions between the Fused Location Server and the Fused Location Client of the target UE. The FLS-1 may support HTTP or WebSocket and the IP connection between the Fused Location Client and Fused Location Server + +NOTE 2: The IP connection between the Fused Location Client and Fused Location Server can be provided by the 5GS PDU Session. + +**FLS-2:** Service-based interface exposing fused location data to the applications (e.g. the vertical applications, the applications of ecosystem partners, etc.). The FLS-2 may support HTTP or WebSocket. + +**FLS-3:** Reference point between the FLS and a database for storing and retrieving location information for the target UE and user profile for the target UE. + +NOTE 3: The definition of FLS-3 is out of scope of this specification. + +**FLS-4:** The reference point is used for location retrieval of the target UE from that 3rd party location server. The FLS-X can be a service-based interface. The FLS-4 may support HTTP or WebSocket. + +NOTE 4: The definition of FLS-4 is out of scope of this specification. + +**Nnef:** Service-based interface as defined in 3GPP TS 23.501 [5]. + +**Le:** Reference point as defined in OMA AD MLS [11]. + +**LM-UU:** Reference point as defined in 3GPP TS 23.434 [13]. + +**LM-S:** Reference point as defined in 3GPP TS 23.434 [13]. + +NOTE 5: If the UE supports MUSIM, the FLS can get the UE location information from the PLMNs via the LM-S reference of each PLMN. + +#### 7.1.1.3 Merged Architecture to support interaction between FLS and SEAL LMS + +FLS fuses different location information from multiple resources and provides a better location service/information to the Application Server via its northbound API. And the SEAL LMS can be one of its location sources as described in figure 7.1.1.3-1. + +The SEAL LMS does not support getting location information from the non-3GPP defined access, the FLS needs to have the interface FLS-1 to get location information from the non-3GPP defined access. + +The FLS needs to get the location information from other PLMNs if the target UE is with multiple PLMN accesses, in such case, the FLS-1 and or the LM-S reference point is to provide such location information from different PLMNs. + +The FLS-3 reference point is defined for storing and retrieving location information for the target UE and user profile for the target UE. + +![Figure 7.1.1.3: Merged architecture with Interaction between Fused Location Server and SEAL LMS. The diagram shows the interaction between a UE, Non-3GPP Defined Access, 3GPP Network, Application Specific Server, Fused Location Server, SEAL LMS, DataBase, and 3rd Party Location Server. The UE contains a Fused Location Client and a SEAL LMC. The Fused Location Server is connected to the Application Specific Server via FLS-2, to the SEAL LMS via LM-S, to the DataBase via FLS-3, and to the 3rd Party Location Server via FLS-4. The SEAL LMS is connected to the 3GPP Network via LM-Uu, N33, and Le interfaces. The Fused Location Server is connected to the 3GPP Network via FLS-1.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +Figure 7.1.1.3: Merged architecture with Interaction between Fused Location Server and SEAL LMS. The diagram shows the interaction between a UE, Non-3GPP Defined Access, 3GPP Network, Application Specific Server, Fused Location Server, SEAL LMS, DataBase, and 3rd Party Location Server. The UE contains a Fused Location Client and a SEAL LMC. The Fused Location Server is connected to the Application Specific Server via FLS-2, to the SEAL LMS via LM-S, to the DataBase via FLS-3, and to the 3rd Party Location Server via FLS-4. The SEAL LMS is connected to the 3GPP Network via LM-Uu, N33, and Le interfaces. The Fused Location Server is connected to the 3GPP Network via FLS-1. + +**Figure 7.1.1.3: Merged architecture with Interaction between Fused Location Server and SEAL LMS** + +### 7.1.2 Solution evaluation + +The merged architecture defined in figure 7.1.1.3-1 is the architecture to merge the Fused Location Server. + +Based on the merged architecture, the SEAL LMS needs to upgrade to support Le interface. + +SEAL LMS only gets the location information for the target UE via the 3GPP defined accesses and provides the location information to the FLS via the LM-S interface, additionally, the FLS gets the location information via the non-3GPP defined accesses from the FLS-1 reference point. + +## 7.2 Solution #2: Support of both LCS and SUPL at Fused Location Function + +### 7.2.1 Solution description + +This solution addresses key issue #1 in respect of application layer support of both LCS and SUPL. + +#### 7.2.1.1 Architectural models + +According to OMA AD SUPL [10], Secure User Plane Location (SUPL) is an Enabler which utilizes existing standards where available and possible, to transfer assistance data and positioning data over a User Plane bearer, such as IP, to aid network and SUPL Enabled Terminal (SET) based positioning technologies in the calculation of a SET's position. + +When MNO deploys both LCS and SUPL, the 3GPP TS 23.271 [3] defines the operation of SUPL in EPC, in which the location of SUPL can be retrived from GMLC. The potential interworking of control plane LCS and OMA SUPL both deployed by an MNO is outside the scope of that specification. For 5G LCS the support for SUPL is not defined in 3GPP TS 23.273 [4]. The 3GPP TS 38.305 [6] Annex A (informative) provides an architecture for interworking + +between LCS and OMA SUPL, in which the location of SUPL is directly exposed from SLP without the involvement of core network entities. + +Considering the existing specifications regarding architecture aspects of SUPL, the potential architectural models of application layer consisting the location source of LCS and SUPL are shown in below figure . + +![Figure 7.2.1.1-1: Possible Fused Location Function architectural models consisting location source of LCS and SUPL. The figure shows three architectural models: a) Location Management Server in the same MNO domain with GMLC and SLP, LCS and SUPL location provided by GMLC; b) Location Management Server in the same MNO domain with the GMLC and SLP, LCS and SUPL location provided by GMLC and SLP separately; c) Location Management Server in 3rd party service provider domain, LCS and SUPL location provided by NEF and SLP separately.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +The diagram illustrates three architectural models for a Fused Location Function (FLF) within a Location Management Server (LMS): + +- Model a:** The LMS contains a Fused Location Function. It is connected via the Le interface to a GMLC (LCS) and an SLP (SUPL) within the same MNO domain. The caption states: "a) Location Management Server in the same MNO domain with GMLC and SLP, LCS and SUPL location provided by GMLC". +- Model b:** The LMS contains a Fused Location Function. It is connected via the Le interface to a GMLC (LCS) and an SLP (SUPL) within the same MNO domain. The caption states: "b) Location Management Server in the same MNO domain with the GMLC and SLP, LCS and SUPL location provided by GMLC and SLP separately". +- Model c:** The LMS contains a Fused Location Function. It is connected via the N33 interface to an NEF (LCS) and via the Le interface to an SLP (SUPL). The NEF and SLP are located in a 3rd party service provider domain, separate from the MNO domain. The caption states: "c) Location Management Server in 3rd party service provider domain, LCS and SUPL location provided by NEF and SLP separately". + +Figure 7.2.1.1-1: Possible Fused Location Function architectural models consisting location source of LCS and SUPL. The figure shows three architectural models: a) Location Management Server in the same MNO domain with GMLC and SLP, LCS and SUPL location provided by GMLC; b) Location Management Server in the same MNO domain with the GMLC and SLP, LCS and SUPL location provided by GMLC and SLP separately; c) Location Management Server in 3rd party service provider domain, LCS and SUPL location provided by NEF and SLP separately. + +**Figure 7.2.1.1-1: Possible Fused Location Function architectural models consisting location source of LCS and SUPL** + +The potential architectural models include: + +- LCS and SUPL locations are exposed by 5GC (from GMLC) through the same interface (Le) to the LCS client which is within the MNO domain. +- LCS and SUPL locations are exposed by 5GC (from GMLC) and OMA SLP separately, the LCS client and SUPL agent are within the MNO domain. + +NOTE: The SLP can belong to the operators' management and also can under the 3rd party location server's control. The LMS retrieves SUPL from SLP within the 3rd party location server via LM-3P reference point if the SLP belongs to the 3rd party location server. + +- LCS and SUPL locations are exposed by 5GC (from NEF) and OMA SLP separately to the AF and SUPL agent that are external to the MNO domain. + +### 7.2.2 Solution evaluation + +This solution is based on the architecture in solution 8 of KI#1 and defines how to fuse the location information from different sources via different interfaces and the possible architecture models. + +## 7.3 Solution #3: Functional architecture for fused location service leveraging SEAL location management + +### 7.3.1 Solution description + +This solution leverages SEAL to address key issue #1: Architecture enhancement of application enablement for location. + +#### 7.3.1.1 Functional architecture + +The figure 7.3.1.1-1 identifies the architecture of fused location service enabled by 5GS leveraging SEAL. + +![Figure 7.3.1.1-1: Functional architecture of fused location service leveraging SEAL location management. The diagram shows the interaction between a User Equipment (UE), a 3GPP network system, a VAL server(s), a Fused Location Function, a 3rd party Location Server, and a Location management server. The UE contains a VAL client(s) and a Fused location client. The VAL client(s) connects to the VAL server(s) via the VAL-UU interface. The Fused location client connects to the Fused Location Function via the FLS-X1 interface. The Fused Location Function connects to the 3rd party Location Server via the FLS-X2 interface and to the Location management server via the FLS-S interface. The Location management server connects to the 3GPP network system via the LM-UU, N33, and Le interfaces. The 3GPP network system connects to the VAL server(s) via the VAL-UU interface. The diagram is divided into two horizontal sections by a dashed line: VAL (top) and SEAL (bottom). The VAL section includes the VAL client(s), VAL server(s), Fused location client, Fused Location Function, and 3rd party Location Server. The SEAL section includes the Location management client, Location management server, and the 3GPP network system.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 7.3.1.1-1: Functional architecture of fused location service leveraging SEAL location management. The diagram shows the interaction between a User Equipment (UE), a 3GPP network system, a VAL server(s), a Fused Location Function, a 3rd party Location Server, and a Location management server. The UE contains a VAL client(s) and a Fused location client. The VAL client(s) connects to the VAL server(s) via the VAL-UU interface. The Fused location client connects to the Fused Location Function via the FLS-X1 interface. The Fused Location Function connects to the 3rd party Location Server via the FLS-X2 interface and to the Location management server via the FLS-S interface. The Location management server connects to the 3GPP network system via the LM-UU, N33, and Le interfaces. The 3GPP network system connects to the VAL server(s) via the VAL-UU interface. The diagram is divided into two horizontal sections by a dashed line: VAL (top) and SEAL (bottom). The VAL section includes the VAL client(s), VAL server(s), Fused location client, Fused Location Function, and 3rd party Location Server. The SEAL section includes the Location management client, Location management server, and the 3GPP network system. + +**Figure 7.3.1.1-1: Functional architecture of fused location service leveraging SEAL location management** + +Editor's note: Representing LMC offering service (e.g. clause 9.3.4 in 23.434) to LMS is FFS. + +Editor's note: How to prevent the loop communication between the FLF and LMS when Application Specific Server is consuming their services is FFS + +In the architecture, the SEAL Location management server (LMS) interacts with the Fused location function for fusion of different location technologies. + +The architecture supports multiple sources of location information including: + +- Location of AMF service exposed by NEF (as defined in 3GPP TS 23.502 [12]); +- LCS location retrieved from either NEF or GMLC (as defined in 3GPP TS 23.273 [4]); +- SUPL location retrieved from SLP (as defined in OMA AD SUPL [10]); +- Location retrieved from 3rd party location server or location management client. + +#### 7.3.1.2 Functional components and reference points + +The Location management server provides location information of the target UE based on positioning or location data retrieved from one or multiple location sources. + +Fused location function provides normalized description of location data to the Location management server through the API. + +The 3rd Party Location Server provides the location of a certain location technology (typically the network-based positioning) e.g. Bluetooth. + +The Location management client represents the client of the requestor/sender UE for location reporting as defined in 3GPP TS 23.434 [13]. + +The Fused location client represents the client of the sender UE for location reporting via non-3GPP access over FLS-X1 interface. + +The location management server is a functional entity that receives and stores user location information and provides user location information to the vertical application server as defined in 3GPP TS 23.434 [13]. The location management server acquires location information from one or more sources including: + +- the NEF (as defined in 3GPP TS 23.501 [5] and 3GPP TS 23.273 [4]) via N33 reference point; +- the GMLC (as defined in 3GPP TS 23.273 [4]) via Le reference point; +- the SLP (as defined in OMA AD SUPL [10]) of SUPL network; +- the Fused location function; and +- the location management client. + +The VAL client and VAL server (vertical application layer entities) are as defined in 3GPP TS 23.434 [13]. + +The interfaces are described as followed: + +**LM-UU:** Reference point as defined in 3GPP TS 23.434 [13]. + +**LM-S:** Reference point as defined in 3GPP TS 23.434 [13]. + +**FLS-X2:** The reference point is used for location retrieval of the target UE from 3rd party location server. + +**NOTE:** The definition of FLS-X2 is out of scope of this specification. + +**N33:** Service-based interface as defined in 3GPP TS 23.501 [5]. + +**Le:** Reference point as defined in OMA AD MLS [11]. + +**FLS-S:** Reference point used for fused location retrieval from Fused location function either by VAL Server or by Location management server. + +**Editor's note:** Impacts of architectural changes to existing SEAL LM procedures in 3GPP TS 23.434 [13] are FFS. + +**Editor's note:** The enhancements to location management client, LM-UU and LM-S providing fused location service are FFS. + +#### 7.3.1.3 Deployment models + +In deployments where Fused Location Function resides outside of SEAL LMS is shown by Figure 7.3.1.1-1. In another deployment the Fused Location Function can be collocated within SEAL LMS. Such function model is as shown in Figure 7.3.1.3-1. + +**NOTE:** This deployment option could be considered as the functional architecture diagram for 5GFLS during normative specification. + +![Functional architecture diagram of fused location service collected within SEAL location management. The diagram shows a UE containing VAL client(s) and LM-C. The VAL client(s) connects to VAL server(s) via VAL-UU. The LM-C connects to a Location management server via LM-UU. The Location management server contains a Fused Location Function and connects to a 3rd Party Location Server via FLS-X2. The Fused Location Function also connects to Non-3GPP access via FLS-X1. The 3GPP network system connects to the VAL server(s) via N33 and Le. The diagram is divided into VAL and SEAL layers by a dashed line.](0882d90c2036d3612040d0989282678a_img.jpg) + +``` + +graph TD + subgraph UE + VAL_client[VAL client(s)] + LM_C[LM-C] + end + VAL_client -- VAL-UU --> VAL_server[VAL server(s)] + LM_C -- LM-UU --> LMS[Location management server] + subgraph SEAL + LMS + FLF[Fused Location Function] + end + FLF -- FLS-X2 --> 3rd_party[3rd Party Location Server] + FLF -- FLS-X1 --> Non_3GPP[Non-3GPP access] + 3GPP_network[3GPP network system] -- N33 --> VAL_server + 3GPP_network -- Le --> LMS + VAL_server -- LM-S --> LMS + VAL_server -- VAL-UU --> VAL_client + LMS -- LM-UU --> LM_C + FLF -- FLS-X1 --> Non_3GPP + FLF -- FLS-X2 --> 3rd_party + FLF -- FLS-X1 --> LMS + FLF -- FLS-X2 --> LMS + +``` + +Functional architecture diagram of fused location service collected within SEAL location management. The diagram shows a UE containing VAL client(s) and LM-C. The VAL client(s) connects to VAL server(s) via VAL-UU. The LM-C connects to a Location management server via LM-UU. The Location management server contains a Fused Location Function and connects to a 3rd Party Location Server via FLS-X2. The Fused Location Function also connects to Non-3GPP access via FLS-X1. The 3GPP network system connects to the VAL server(s) via N33 and Le. The diagram is divided into VAL and SEAL layers by a dashed line. + +**Figure 7.3.1.3-1: Functional architecture of fused location service collected within SEAL location management** + +**Editor's note:** Moving deployment model to another clause is FFS + +### 7.3.2 Solution evaluation + +*Editor's Note: This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.* + +## 7.4 Solution #4: Location service registration + +### 7.4.1 Solution description + +This solution addresses key issue #5: Initialization and configuration for fused location service. + +The procedure for location service registration is illustrated in figure 7.4.1-1. This procedure is based on the fused location architecture of KI#1. The purpose of this procedure is for the Location Management Client (LMC) to register to the location services available at the Fused Location Function (FLF) which is part of Location Management Server (LMS) while ensuring the privacy of the user. + +If the Multi-USIM is supported by the LMC, the LMC performs the registration procedure for each PLMN of the Multi-USIM PLMNs. + +![Sequence diagram illustrating the Location service registration procedure. The diagram shows three steps: 1. Location Management Client sends a 'Location service registration request' to the Location Management Server (Fused Location Function). 2. The server performs an 'Authorization and privacy check'. 3. The server sends a 'Location service registration response' back to the client.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +``` + +sequenceDiagram + participant LMC as Location Management Client + participant LMS as Location Management Server (Fused Location Function) + Note right of LMS: 2. Authorization and privacy check + LMC->>LMS: 1. Location service registration request + LMS-->>LMC: 3. Location service registration response + +``` + +Sequence diagram illustrating the Location service registration procedure. The diagram shows three steps: 1. Location Management Client sends a 'Location service registration request' to the Location Management Server (Fused Location Function). 2. The server performs an 'Authorization and privacy check'. 3. The server sends a 'Location service registration response' back to the client. + +**Figure 7.4.1-1: Location service registration procedure** + +1. The LMC of a target UE sends location service registration request to the FLF which is part of LMS via the LM-UU interface over non-3GPP access, carrying the identifier of the UE (e.g. GPSI, UUID, etc.) and non-3GPP defined access location capabilities (e.g. the available non-3GPP defined access types, the location methods, the location accuracy and latency of the non-3GPP defined access types). + +**NOTE:** The LMC does not directly communicate with the FLF but communicate with LMS directly, and LMS will coordinate with FLF internally after receiving LMC requests. + +To access the FLF via the LM-UU interface over non-3GPP access, the LMC can use any available non-3GPP defined accesses to send the location service registration request. + +The LMS with FLF can be pre-configured in the UE or be discovered via the DNS query. + +2. The FLF checks authorization for the UE's request. If the FLF supports privacy checking it also performs or assists with e.g. 5GC on privacy check. +3. The FLF, upon successful authorization and privacy check (if any), responds to the LMC with registration result and stores the UE identifier information and non-3GPP defined access location capabilities into the UE location context. + +If the Multi-USIM is supported by the LMC, the LMC performs steps 1 to 3 to register its identifier (e.g. MSISDN) associated with each PLMN of the Multi-USIM PLMNs. + +### 7.4.2 Solution evaluation + +This solution is based on the new architecture proposed in KI#1. The location management client can provide its UE IDs and the location capabilities of the available non-3GPP defined accesses to the fused location function which is part of location management server through LM-UU interface over non-3GPP access, and the fused location function can generate and store this information as the UE location context, and also can use these UE location contexts in the subsequent location procedures. + +## 7.5 Solution #5: Location profiling for supporting fused location service enablement + +### 7.5.1 Solution description + +#### 7.5.1.1 General + +This solution addresses key issue #3 Location service differentiation. The solution discusses the creation of Location profiles at a fused location service at the application enablement layer; and the mapping of Location profiles to one or more vertical applications. Such profiling is based on a variety of factors which correspond to use-case / vertical driven hybrid positioning requirements and policies. This notion of profiling (which is different from the service profile) is based on the various factors which may affect the positioning methods and QoS, and fixes also the communication parameters per vertical requirement-use case, without providing any additional information at the 3rd party app. The attributes that can be used for the Location profile can be some of the following (however how the Location profiles are constructed can be up to implementation): + +- the vertical / application service type; +- the environment (indoor/outdoor, urban/suburban,); +- the QoS requirements, e.g. accuracy; +- the capabilities of the UEs involved; +- the energy constraints for the devices; +- preference on certain positioning methods, e.g. RAT-dependent or RAT-independent methods; +- LCS service level (in case of IIOT vertical); +- priorities of location methods; +- whether location augmentation is required; +- whether location prediction is required; +- whether sidelink positioning assistance is required; +- whether proximity-based location estimate is required; +- whether location verification is required. + +An example Location profile can be shown in Table 7.5.1.1-1 below. + +Table 7.5.1.1-1: Exemplary location profile attributes + +| Profile ID / name | Vertical / use case, environment | Positioning Service Level (for IIOT) / QoS / accuracy | Positioning Method(s) / Priorities | Involved 3GPP functionalities / Priorities | Involved non-3gpp access networks | Required APIs / API info | Other | +|---------------------|---------------------------------------------------|---------------------------------------------------------------|----------------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------|--------------------------|--------------------------------------| +| Location profile #1 | Industrial scenario, indoors, mobile robots/ AGVs | Service Level 6 / cm level accuracy / absolute/relative/ both | 1. DL-TDOA, 2. UL-TDOA, 3. Multi-RTT methods, 4. WLAN, 5. motion sensors, 6. Bluetooth | 1. LMF, 2. RAN-LMC, 3. SEAL LMS, .. | 1. WLAN ID,.... | NEF APIs, SEAL APIs, .. | Verification / augmentation required | +| Location profile #2 | V2X, outdoor, .. | Decimeter level accuracy / ... absolute/relative/both | 1. DL-TDOA, 2. Multi-RTT methods, 3. GNSS-RTK, 4. Sensor fusion, 5. A-GPS | 1. LMF, 2. SEAL LMS, 3. Other UEs | 2. GNSS #x, #y, 4. MEC #x | NEF APIs, MEC APIs, .. | Support for sidelink positioning | + +Without this solution, app server needs to consolidate all measurements and interact with different systems to get the required location. The profiling helps the optimization of the process based on the environment, UE context, etc., per profile checking/monitoring. Also, the configuration of combined positioning methods to meet the LCS requirements, done with minimum exposure to the 3rd party/customer. + +#### 7.5.1.2 Procedure + +The procedure includes the translation of the vertical request to a Location profile and the procedures with the involved entities to derive the requested location report. The fused location function/client may also fetch location reports in an iterative manner based on method priorities, to ensure that the vertical requirement is met, with the minimum signaling/complexity. + +Figure 7.5.1.2-1 illustrates a solution for the location profiling for supporting fused location exposure. + +Pre-conditions: + +1. The VAL server has registered to receive fused location function services. + +![Sequence diagram illustrating the location profiling process for fused location derivation and exposure. The diagram shows interactions between VAL Client, Location Management Client, 3rd Party location server, 5GC, Location Management Server (FLF), and VAL Server. The process involves configuration, request, mapping, and report delivery steps.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant VAL Client + participant LMC as Location Management Client + participant 3PLS as 3rd Party location server + participant 5GC + participant FLF as Location Management Server (FLF) + participant VS as VAL Server + + Note right of FLF: 1. Location profile configuration + FLF->>VS: 2. Fused Location Request + Note right of FLF: 3. VAL application to LCS profile mapping + FLF->>LMC: 4. LCS profile mapping and report configuration + Note right of 5GC: 5a. Fused location request + Note right of 5GC: 5b. Fused location report + Note right of 3PLS: 6. Retrieve location reports per location profile & VAL application + Note right of FLF: 7. Fused location estimate calculation/Check fulfillment of location profile req. + Note right of 3PLS: 8. Retrieve supplementary location reports per location profile & VAL application + Note right of FLF: 9. Fused location estimate calculation/Check fulfillment of location profile req. + FLF->>VS: 10. Fused Location Report + +``` + +Sequence diagram illustrating the location profiling process for fused location derivation and exposure. The diagram shows interactions between VAL Client, Location Management Client, 3rd Party location server, 5GC, Location Management Server (FLF), and VAL Server. The process involves configuration, request, mapping, and report delivery steps. + +**Figure 7.5.1.2-1: Location profiling for fused location derivation and exposure** + +1. The Fused Location Function(FLF) which is part of the Location Management Server(LMS) configures a set of location service profiles, where each location service profile includes metrics like the positioning method, QoS parameters, location service producers involved, environment/ area type, etc. + +NOTE 1: How the profiling attributes are selected/configured is up to implementation. + +2. The LMS receives a location request from a fused location service consumer (VAL server), where this request may include a VAL server ID, location QoS requirements (accuracy, response time,...), location granularity (coordinates, cell-level, civic addresses, topological location), vertical specific support information (planned route, road maps,...), time validity for the requirement, area of validity, event triggering criteria (under which criteria the location report needs to be sent), etc. +3. The fused location enabler function within the LMS determines a mapping of the fused location service consumer (VAL server) to a location service profile based on the location request and the information provided within the request. +4. The FLF within the LMS informs to the Location Management Client (LMC) optionally the involved 3gpp functions and the configuration of the mapping of the application to a Location profile. This may include the report configuration per Location profile (thresholds for event triggering, periodicity of reporting, format of reporting, minimum time between consecutive reports) as well as the priority of positioning methods and location report granularity (coordinates, cell-level, civic addresses, topological location). + +NOTE 2: The FLF does not directly communicate with the LMC but through the LMS, and the LMS will coordinate with FLF internally when received LMC requests + +- 5a. The FLF within the LMS requests from the LMC a local fused location estimate of the target VAL UE or for the UEs within the application in close vicinity. +- 5b. The LMC responds to the FLF a local fused location estimate based on the request. +6. The FLF within the LMS performs a location request to one or more of the following (based on the Location profile): + - to GMLC directly or via NEF (see TS 23.273), acting as AF. The LCS service request is sent to GMLC or AMF, via NEF using the service-based interface or CAPIF API; or directly to GMLC if allowed to (e.g. fused location function is within the MNO trust domain). + - to 3rd party location servers as described in KI#1. +7. The FLF within the LMS calculates the fused location estimated based on combining location reports from previous steps, and may also perform additional processing e.g. for location augmentation, and verification based on the Location profile. Then, it checks whether the estimate fulfills the Location profile requirement (based on QoS parameters such as accuracy, response time). +- 8-9. If the requirement is not fulfilled, the FLF within the LMS iteratively requests further location information and re-checks whether the requirement is met or not. +10. The LMS sends the fused location report to the VAL server. + +### 7.5.2 Solution evaluation + +This solution is based on the architecture proposed in solution 8 of KI#1 and discusses the creation of location profiles at FLF within the LMS, and the mapping of location profiles to one or more vertical applications. The Fused Location Function (FLF) which is part of the Location Management Server(LMS) could enable the translation/mapping of the vertical request to a location profile, derive the requested location report, and then fetch the aggregated/fused location data from more data sources (such as GMLC, 3rd party location servers, and etc.) in an iterative manner to ensure that the vertical requirement is met and send the final fused location report to the VAL server at last. + +## 7.6 Solution #6: Location service configuration + +### 7.6.1 Solution description + +This solution addresses key issue #5: Initialization and configuration for fused location service. + +#### 7.6.1.1 Service flow for fused location service configuration + +The high-level service flow for fused location service configuration is illustrated in figure 7.6.1.1-1. This service flow is based on the fused location architecture of KI#1. + +![Sequence diagram showing the service flow for fused location service configuration. Lifelines: Location Management Client, 3rd Party Location Server 1, 3rd Party Location Server 2(SUPL), NEF/GMLC(LCS), Location Management Server(FLF). The sequence starts with the FLF initiating a location service, followed by a capability query to the target UE. It then branches into two positioning options: LCS positioning (3a) and SUPL positioning (3b). Both lead to a location service configuration with the 3rd party location system (3c), which finally leads to a configuration with the target UE (3d).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant Client as Location Management Client + participant Server1 as 3rd Party Location Server 1 + participant Server2 as 3rd Party Location Server 2(SUPL) + participant NEF as NEF/GMLC(LCS) + participant FLF as Location Management Server(FLF) + + Note right of FLF: 1. Location service is initiated + Note over Client, FLF: 2. Location capability query with target UE + + Note right of NEF: LCS positioning + Note right of NEF: 3a. Location service request to LCS + + Note right of Server2: SUPL positioning + Note right of Server2: 3b. Location service request to SUPL + + Note over Server1, FLF: 3c. Location service configuration with 3rd Party Location system + Note over Client, FLF: 3d. Location service configuration with target UE + +``` + +Sequence diagram showing the service flow for fused location service configuration. Lifelines: Location Management Client, 3rd Party Location Server 1, 3rd Party Location Server 2(SUPL), NEF/GMLC(LCS), Location Management Server(FLF). The sequence starts with the FLF initiating a location service, followed by a capability query to the target UE. It then branches into two positioning options: LCS positioning (3a) and SUPL positioning (3b). Both lead to a location service configuration with the 3rd party location system (3c), which finally leads to a configuration with the target UE (3d). + +**Figure 7.6.1.1-1: Service flow for fused location service configuration** + +1. The location service is initiated at the Fused Location Function(FLF) within Location Management Server(LMS). This can be triggered by an application through e.g. a service request or triggered by an event, by which the location service requirements for a target UE are identified. +2. The LMS enhanced with FLF may query the location capability of the target UE, e.g. the location system or location service, or location methods supported by the UE. The FLF may need to decide the location source from which to receive location information based on the location service requirements as well as the target UE's location capability. + +The LMS enhanced with FLF may configure location report parameters (such as thresholds for event triggering, periodicity of reporting, format of reporting, minimum time between consecutive reports, etc.) and send to the location management client of the target UE. + +- 3a. The LMS enhanced with FLF may invoke the LCS service e.g. 5GC-MT-LR Procedure (as defined in 3GPP TS 23.273 [4]) including location report configuration by acting as AF or LCS client. +- 3b. The LMS enhanced with FLF may invoke the SUPL service from the 3rd party location server ,e.g. network initiated flows (as defined in OMA AD SUPL [10]) including location report configuration by acting as the SUPL agent. + +NOTE: The interaction between LMS and OMA is up to the implementation and out of 3GPP scope. + +- 3c. If the LMS enhanced with FLF decides to receive location from the 3rd party location system, the LMS enhanced with FLF configures the location service with the 3rd party location server to establish the secured data connection and session for location reports, and to support the location system configuration tailored for the location service requirements. +- 3d. The LMS enhanced with FLF interacts with the location management client of the target UE to provide the location service configurations including information about the fused location configuration. + +### 7.6.2 Solution evaluation + +This solution is based on the architecture proposed in solution 8 of KI#1. The Fused Location Function (FLF) which is part of Location Management Server (LMS) can acquire different location information from multiple resources. For example, from 3GPP access (LCS location retrieved from either NEF or GMLC, etc.), non-3GPP access (target UE location retrieved via LM-UU), or the 3rd party location server (SUPL location retrieved from SLP, etc.) to provide an accurate UE location. Besides, the FLF used as an additional source of the LMS can configure the location service with the 3rd party location server and communicate with the location management client of the target UE to provide the location service configurations. + +## 7.7 Solution #7: Location QoS based location sources and positioning methods selection + +### 7.7.1 Solution description + +This solution addresses key issue #2: Support of LCS QoS. + +The Fused Location Function firstly needs to produce the fused location data from multiple sources based on the requested location QoS (e.g. the requirements of the positioning accuracy, reliability and latency). Based on the requested location QoS, the FLF needs to select one or more access types, one or more location methods (as described in TS 29.572 [14] ) and related CP/UP(SUPL) methods based on the requested location QoS (not exhausted): + +- 2G/3G/4G/5G/NR satellite access +- Non-3GPP access connected to 5GC +- GNSS (e.g. GPS, Galileo, BeiDou etc.) +- Barometric Pressure +- WLAN +- Bluetooth +- Terrestrial Beacon System (TBS) positioning based on MBS signals +- Motion Sensor +- RFID +- Radio finger-print +- Cell ID +- ECID +- OTDOA +- DL\_TDOA +- DL\_AOD +- Multi-RTT +- NR\_ECID +- UL\_TDOA +- UL\_AOA +- Ultra Wide Band (UWB) +- Fingerprint + +#### 7.7.1.1 Procedure of location QoS based location sources and positioning methods selection + +![Sequence diagram illustrating the procedure of location QoS based location sources and positioning methods selection. The diagram shows interactions between Location Management Client, NG-RAN, WLAN, GNSS, Location Management Server(FLF), and Application-Specific Server. The steps are: 1. Location Request from Application-Specific Server to LMS; 2. Get the available access type and positioning methods based on the location QoS from LMS to LMC; 3. LMS selects an access type and a position method to get the UE location; 4. LMS fuses the location information from multiple location sources; 5. Location Response from LMS to Application-Specific Server.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +``` + +sequenceDiagram + participant LMC as Location Management Client + participant NG-RAN as NG-RAN + participant WLAN as WLAN + participant GNSS as GNSS + participant LMS as Location Management Server(FLF) + participant ASS as Application-Specific Server + + Note right of LMS: 2. Get the available access type and positioning methods based on the location QoS + Note right of LMC: 3. LMS selects an access type and a position method to get the UE location + Note right of LMS: 4. LMS fuses the location information from multiple location sources + + ASS->>LMS: 1. Location Request + LMS-->>LMC: 2. Get the available access type and positioning methods based on the location QoS + LMS-->>LMC: 3. LMS selects an access type and a position method to get the UE location + LMS-->>LMC: 4. LMS fuses the location information from multiple location sources + LMS-->>ASS: 5. Location Response + +``` + +Sequence diagram illustrating the procedure of location QoS based location sources and positioning methods selection. The diagram shows interactions between Location Management Client, NG-RAN, WLAN, GNSS, Location Management Server(FLF), and Application-Specific Server. The steps are: 1. Location Request from Application-Specific Server to LMS; 2. Get the available access type and positioning methods based on the location QoS from LMS to LMC; 3. LMS selects an access type and a position method to get the UE location; 4. LMS fuses the location information from multiple location sources; 5. Location Response from LMS to Application-Specific Server. + +Figure 7.7.1.1-1: location sources and positioning methods selection + +1. The application-specific server sends a location request to the Location Management Server(LMS) enhanced with Fused Location Function(FLF) to request the location information of the target Location Management Client(LMC) (e.g. UE Identity, location QoS, etc). The location QoS can include the location accuracy, reliability and latency,etc. as described in clause 4.1b of TS23.273[4]. +2. The LMS enhanced with FLF queries the UE location context (e.g. in the internal database) with the location QoS to retrieve the available access type, positioning methods as described in TS 29.572 [14] for the target LMC. +3. The LMS enhanced with FLF selects the available access type (i.e. different location sources) and positioning methods to get the UE location information from these available access types. + +NOTE: The FLF does not directly communicate with the LMC but through the LMS, and the LMS will coordinate with FLF internally when received LMC requests. + +4. The LMS enhanced with FLF fuses the UE location information from different sources to get a fused UE location that meets the location QoS requirements. +5. The LMS enhanced with FLF provides the fused UE location that meets the location QoS requirements to the application-specific server. + +### 7.7.2 Solution evaluation + +This solution is based on the architecture proposed in Solution 8 of KI#1. Compared to existing On-demand usage of location information in SEAL LM (TS 23.434[13], clause 9.3.9), the FLF which is part of LMS can aggregate/fuse location data from more data sources so that more accurate location can be reported. Different location source can provide location information with different location QoS, the FLF takes the different advantages of these different location sources and decides to select which location sources based on the required location QoS and fuses the location information from the selected location sources to produce the final location information to meet the location QoS. + +## 7.8 Solution #8: Architecture for fused location service + +### 7.8.1 Solution description + +This solution addresses key issue #1: Architecture enhancement of application enablement for location. + +#### 7.8.1.1 Functional architecture + +Figure 7.8.1.1-1 identifies the architecture of fused location service. + +![Figure 7.8.1.1-1: Functional architecture of fused location service. The diagram shows a UE containing a Location Management Client. The client connects via LM-UU interfaces (one over 3GPP access, one over non-3GPP access) to a central Location Management Server (LMS). The 3GPP access path includes a 3GPP Network with Le and N33 interfaces. The LMS contains a Fused Location Function (FLF) and connects to an Application Specific Server via an LM-S interface and to a 3rd Party Location Server via an LM-3P interface.](356eb99ab9489bbd647223390a913903_img.jpg) + +``` + +graph TD + subgraph UE + LMC[Location Management Client] + end + LMC -- "LM-UU (over 3GPP access)" --> 3GPN[3GPP Network] + LMC -- "LM-UU (over non-3GPP access)" --> N3GPA[Non-3GPP access] + 3GPN -- "Le, N33" --> LMS[Location Management Server] + N3GPA --> LMS + subgraph LMS + FLF[Fused Location Function] + end + LMS -- "LM-S" --> ASS[Application Specific Server] + LMS -- "LM-3P" --> 3PLS[3rd Party Location Server] + +``` + +Figure 7.8.1.1-1: Functional architecture of fused location service. The diagram shows a UE containing a Location Management Client. The client connects via LM-UU interfaces (one over 3GPP access, one over non-3GPP access) to a central Location Management Server (LMS). The 3GPP access path includes a 3GPP Network with Le and N33 interfaces. The LMS contains a Fused Location Function (FLF) and connects to an Application Specific Server via an LM-S interface and to a 3rd Party Location Server via an LM-3P interface. + +**Figure 7.8.1.1-1: Functional architecture of fused location service** + +The architecture is composed of logical function modules that are not necessarily physical entities and can reside in or co-locate with existing application layer entities as appropriate. + +In the architecture, the Fused Location Function (FLF) is part of the Location Management Server (LMS), and the LMS and Application Specific Server can be within the MNO domain or third-party service provider domain. + +The FLF fuses different location information from multiple resources and provides a better location service/information to the Application Specific Server via the LMS northbound API. + +The FLF supports multiple possible sources of location information including: + +- LCS location retrieved from SEAL LMS internally as defined in 3GPP TS 23.434 [13]; +- Retrieve the target UE positioning from 3rd party location server, e.g. the SLP (as defined in OMA AD SUPL [10]) of SUPL network; +- Retrieve the target UE Positioning via the LM-UU interface over non-3GPP access. +- Retrieve target UE location information via the LM-UU interface relating to a UE's other PLMN connection(s), if supported by the UE. + +#### 7.8.1.2 Functional components and reference points + +The FLF provides location information of the target UE based on positioning or location data retrieved from one or multiple location sources. The FLF can get the location information from the target UE, the SEAL LMS and the 3rd party location server. The FLF selects one or more location sources and one or more location methods based on the requested + +location QoS. The FLF provides a normalized description of location data to the application-specific server (e.g. of ecosystem partners) through the northbound API LM-S. + +The Location Management Client (LMC) is the SEAL Location Management Client as defined in 3GPP TS 23.434 [13] enhanced with new functions which could- represent the client of the target UE providing the UE-based positioning and location-related information (e.g. the WiFi SSID list for WiFi SSID fingerprint based UE positioning) and providing the UE location information to the FLF within the LMS via an IP connection through LM-UU interface over non-3GPP access. + +NOTE 1: How does the LMC get its UE location related information is out of the scope of 3GPP. + +The LMS is the SEAL Location Management Server enhanced with FLF. The SEAL Location Management Server is a functional entity that receives and stores user location information and provides user location information as defined in 3GPP TS 23.434 [13]. The LMS acquires location information from one or more sources including: + +- the NEF (as defined in 3GPP TS 23.501 [5] and 3GPP TS 23.273 [4]) via N33 reference point; +- the GMLC (as defined in 3GPP TS 23.273 [4]) via Le reference point which is not defined in 3GPP TS 23.434[13]; +- the SEAL location management client as defined in 3GPP TS 23.434[13]. + +The 3rd Party Location Server provides the location of certain location technology (typically the network-based positioning). + +The interfaces are described as following: + +**LM-UU:** Reference point as defined in 3GPP TS 23.434 [13]. The Reference point is enhanced to support location reporting, location determination, location management, and exchange of location contextual information (e.g. UE ID, location capabilities of the target UE, the available positioning methods supported by the target UE, such as the WiFi SSID list for WiFi SSID fingerprint based UE positioning) between the FLF of the LMS and the LMC of the target UE. + +**LM-3P:** The reference point is used for location retrieval of the target UE from that 3rd party location server. The LM-3P can be a service-based interface that may support HTTP or WebSocket. + +NOTE 2: The LM-3P is assumed to be based on the well defined protocols in location related services and the definition of LM-3P is out of scope of this specification. + +**Nnef/N33:** Service-based interface as defined in 3GPP TS 23.501 [5]. + +**Le:** Reference point as defined in 3GPP TS 23.271 [3]. + +**LM-S:** Reference point as defined in 3GPP TS 23.434 [13]. + +### 7.8.2 Solution evaluation + +With this architecture, the FLF can fuse additional UE location sources to determine a better UE location. The FLF can retrieve UE location from the LMC via LM-UU interface over non-3GPP access and the 3rd party server via LM-3P interface. However, how the FLF gets or retrieves the UE location from the 3rd party is out of scope of 3GPP. The FLF can be used as an additional source for location information to enhance the LMS. + +In this architecture, the SEAL LMS is enhanced with FLF and supports the enhanced LM-UU interface over non-3GPP access, and LM-3P interface. The LM-3P interface is out of scope of 3GPP. The LMC is enhanced to provide UE location information to FLF via LM-UU interface over non-3GPP access. + +# --- 8 Overall evaluation + +## 8.1 General + +The following clauses contain an overall evaluation of the solutions presented in this technical report, including their applicability to the identified key issues and possible dependencies to other groups. + +## 8.2 Architecture enhancements + +The solution #1 proposes a standalone functional architecture for fused location service, including the functional architecture, functional components, reference points and the merged architecture to support interaction between FLS and SEAL LMS. + +The solution #8 proposes an enhanced architecture for application enablement for location, including the fused functional architecture, functional components and reference points, etc. + +## 8.3 Solution evaluations + +### 8.3.1 General + +All the key issues and solutions specified in this technical report are listed in Table 8.3.1-1. This table includes the mapping of the key issues to the solutions, and possible dependencies to other groups. + +**Table 8.3.1-1 Key issues and solutions** + +| Key issues | Solution | Dependency on other working groups | +|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------------------| +| Key issue #1: Architecture enhancement of application enablement for location | Solution #1: Standalone functional architecture for fused location service | - | +| | Solution #2: Support of both LCS and SUPL at Fused Location Function | - | +| | Solution #3: Functional architecture for fused location service leveraging SEAL location management | - | +| | Solution #8: Architecture for fused location service | - | +| Key issue #2: Support of LCS QoS | Solution #7: Location QoS based location sources and positioning methods selection | - | +| Key issue #3: Location service differentiation | Solution #5: Location profiling for supporting fused location service enablement | - | +| Key issue #4: Void | | - | +| Key issue #5: Initialization and configuration for fused location service | Solution #4: Location service registration | - | +| | Solution #6: Location service configuration | - | +| Key issue #6: Value-Added Location Services | | - | + +### 8.3.2 Overall evaluation of key issue#1 + +The KI#1 mainly studies whether and how the SEAL location-related architecture enhancement or new architecture model is needed based on evaluations of existing location management architectures, functional entities, and capabilities with the following aspects: + +- Functional entity(ies) supporting the combined use and fusion of different location technologies at the application layer; +- Architecture enhancement addressing the consideration of flexibility, scalability, and reliability; +- Support for high-accuracy positioning based on LCS and 5G network exposure; +- Architecture aspects that make sure UE provided the location is not spoofed; +- Architecture aspects that comply with local, national, and regional location privacy requirements. + +To address the open issues aforementioned, there are four solutions proposed as follows: + +Solution #1 introduces a new Fused Location Server(FLS) which supports multiple possible sources of location information and proposes a merged architecture to support interaction between FLS and SEAL LMS. The solution indicated FLS is the primary contact for location information queries. The SEAL LMS only gets the location information for the target UE via the 3GPP defined accesses and provides the location information to the FLS. + +Additionally, the FLS gets the location information via the non-3GPP defined accesses. Based on the merged architecture, the SEAL LMS needs to upgrade to support Le interface. And this solution add the complexity for location information queries and has no benefit compared to Solution#8. + +Solution #2 defines in different deployment how to fuse the location information from different sources via different interfaces and the possible architecture models based on the same architecture in Solution#8. + +Solution #3 proposes a functional architecture of fused location service leveraging SEAL location management. In the architecture, the SEAL Location Management Server (LMS) interacts with the Fused Location Function (FLF) for a fusion of different location technologies. And the FLF can be deployed to reside outside of SEAL LMS or to be within SEAL LMS. However, this solution is incomplete(including 6 Editor's Notes) and does not clarify how loop communication between LMS and FLF can be prevented. + +Solution #8 proposes an enhanced architecture for SEAL LMS. In this architecture, the SEAL LMS is enhanced with FLF, which is part of the LMS, and supports the enhanced LM-UU interface over non-3GPP access, and the LM-3P interface to interact with 3rd party location server. The LM-3P interface is out of the scope of 3GPP. + +Based on the agreement, achitecture enhancements from solution #8 can be used for the baseline architecture in the normative phase, and the feature interaction between Location Management Client and Location Management Server will be addressed in normative work. And solution 2 will act as supplement for the the baseline architecture. + +### 8.3.3 Overall evaluation of key issue#2 + +The KI#2 mainly studies the following open issues: + +- How to support invocation of LCS service (as defined by SA2) with a required LCS QoS, including how and when the LCS QoS attributes are specified in an application scenario, and how to potentially use the LCS QoS attributes differently for different vertical scenarios; +- How to support the identification of an appropriate LCS QoS requirement between all interested parties.; +- How to potentially retrieve the continuity and consistency of LCS QoS for the vertical applications; +- How to potentially support the negotiation of required LCS QoS that is application driven. + +Solution #7 addresses KI#2 and is based on the architecture proposed in Solution#8. In Solution#7, as different location sources can provide different location information with different location QoS, the Fused Location Function (FLF) takes the advantages of these different location sources and decides to select which location sources based on the required location QoS and fuses the location information from the selected location sources to generate the final location information to meet the requested location QoS. + +Solution #7 can be considered in the normative work. The feature interaction between Location Management Server and VAL server, and detailed APIs and information flows can be discussed/addressed in the normative phase. + +### 8.3.4 Overall evaluation of key issue#3 + +The open issue for KI#3 includes: + +- The possible dimensions to distinguish location service in the application enabler layer and how to enable the location service differentiation. + +Solution #5 addresses KI#3 and introduces the creation of location profiles at a fused location service at the application enablement layer and the mapping of location profiles to one or more vertical applications. In Solution#5, the Fused Location Function (FLF) which is part of the Location Management Server(LMS) could enable the translation/mapping of the vertical request to a location profile, derive the requested location report, and then fetch the aggregated/fused location data from more data sources in an iterative manner to ensure that the vertical requirement is met and send the final fused location report to the VAL server at last. + +Solution #5 can be considered in the normative work, the detailed list of location profiles, APIs and information flows can be discussed in the normative phase. + +### 8.3.5 Overall evaluation of key issue#4 + +Void + +### 8.3.6 Overall evaluation of key issue#5 + +The open issue for KI#5 includes: + +- How to initiate and start the fused location service for a target UE in different scenarios, environments, network conditions, types of service, etc. +- How to initiate and start the fused location service such that the location capabilities of target UE and the application layer location service can be coordinated. +- What configurations are needed for the initialization of fused location service and how. +- What application layer sessions are established for the fused location service and how. + +There are two solutions that address the above open issues for KI#5. + +Solution #4 defines the procedure for fused location service registration from Location Management Client (LMC) to Location Management Server (LMS). The LMC can provide its UE IDs and the location capabilities of the available non-3GPP defined accesses to the Fused Location Function (FLF) which is part of LMS through the LM-UU interface over non-3GPP access, and the FLF can generate and store this information as the UE location context, and also can use these UE location contexts in the service flow (such as the one depicted in Figure 7.6.1.1-1) for fused location service. + +Solution #6 describes the high-level service flow for fused location service configuration. The location service is initiated at the LMS and triggered by an application. The FLF in the LMS may query the location management client of the target UE, and invoke the location service and/or SUPL service with 5GC, and/or the 3rd party location server, etc. + +Solution #4 covers open issues#1 and #2 of KI#3, and Solution#6 covers open issues#3 and #4 of KI#3. Both solutions can be considered in the normative work. The feature interaction between Location Management Client and Location Management Server for Sol#4 and the feature interaction between Location Management Server and VAL server for Sol#6, the detailed APIs and information flows can be discussed/addressed in the normative phase. + +### 8.3.7 Overall evaluation of key issue#6 + +There is no solution for KI#6. However, the importance and necessity of KI#6 have been recognized and documented. As the amount of addressed aspects/features for valued-added location service (such as Location Event Trigger provision, invoke, revoke; Real time location information Pushing; Location Alerting and so on) is huge, the study time for KI#6 in Rel18 is limited, and its realization is independent of the current architecture, the KI#6 is proposed to be investigated in future release. + +# --- 9 Conclusions + +## 9.1 General conclusions + +This technical report fulfils the objectives of the study on 5G-enabled fused location service capability exposure. + +The report includes the following: + +1. Definition of terms and abbreviations used in the study (clause 3); +2. Key issues identified by the study (clause 5); +3. Enhancements to Service Enabler Architecture Layer for Verticals (SEAL) specified in 3GPP TS 23.434, corresponding to the key issues and architectural assumptions and requirements (clause 4); +4. Individual solutions addressing the key issues (clause 7); +5. Overall evaluations of all the solutions (clause 8). + +## 9.2 Conclusions for normative work + +### 9.2.1 General conclusions + +The study concludes with the following general considerations for the normative work: + +1. Definition of terms and abbreviations captured in clause 3 will be reused; +2. Architectural requirements identified in clause 4 will be used for updated baseline architectural requirements. + +### 9.2.2 Architecture enhancement conclusions + +The study concludes with the following architectural enhancements considerations for the normative work: + +1. Architecture enhancements from solution #8 as specified in clause 7.8 will be used for updating the baseline location management server specified in 3GPP TS 23.434; + +### 9.2.3 Solution conclusions + +The study concludes with the following solution considerations for the normative work: + +1. Following individual solutions, corresponding to the key issues, will be considered as candidate solutions: + +- 1) For key issue#1 (Architecture enhancement of application enablement for location) + +The solution#8 will be considered in the normative phase and used as baseline enhanced architecture for 5G-enabled fused location service. The enhanced architecture for SEAL LMS will be specified in TS23.434 to support solution#8. + +The solution#2 will be considered in the normative phase and act as supplement for solution#8. + +The enhanced architecture for SEAL LMS will be specified in TS23.434 to support solution#2. + +- 2) For key issue #2 (Support of LCS QoS) + +The solution#7 will be considered in the normative phase. The function and procedure will be specified in TS23.434 to support solution#7. + +The detailed APIs and information flows can be discussed in the normative phase. + +- 3) For key issue#3 (Location service differentiation) + +The solution#5 will be considered in the normative phase. The function and procedure will be specified in TS23.434 to support solution#5. + +The detailed APIs and information flows can be discussed in the normative phase. + +- 4) For key issue#4(Void) + +Void + +- 5) For key issue#5(Initialization and configuration for fused location service) + +The solution#4 and solution#6 will be considered in the normative phase. The function and procedure will be specified in TS23.434 to support solution#4 and solution#6. + +The detailed APIs and information flows can be discussed in the normative phase. + +- 6) For key issue#6(Value-Added Location Services) + +To be studied in future release. + +2. Individual solutions, not listed under bullet 1 may be adopted in technical specification with appropriate enhancements. + +# Annex A: Change history + +| Change history | | | | | | | | | +|----------------|--------------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2021-07 | SA6#44-e | S6-211767 | - | - | - | Skeleton document proposal | | 0.0.0 | +| 2021-07 | SA6#44-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-211768, S6-211769, S6-211771, S6-211772, S6-211792 | | 0.1.0 | +| 2021-07 | SA6#44-e | | | | | Corrections of reference numbers in clause 4.1 and the bullet list in clause 5.1 | | 0.1.1 | +| 2021-09 | SA6#45-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-212066, S6-212067, S6-212086, S6-212176 | | 0.2.0 | +| 2021-10 | SA6#45-bis-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-212296, S6-212298, S6-212395, S6-212477 | | 0.3.0 | +| 2021-11 | SA6#46-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-212704, S6-212706, S6-212759, S6-212828, S6-212836, S6-212837 | | 0.4.0 | +| 2022-04 | SA6#48-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-220949, S6-220950 | | 0.5.0 | +| 2022-05 | SA6#49-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-221459, S6-221460, S6-221461, S6-221487 | | 0.6.0 | +| 2022-08 | SA6#50-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-222220, S6-222446, S6-222447, S6-222448, S6-222449, S6-222450, S6-222598 | | 0.7.0 | +| 2022-10 | SA6#51-e | | | | | Implementation of the following p-CRs approved by SA6:
S6-222636, S6-222637, S6-222639, S6-222928, S6-222929, S6-222930, S6-223052 | | 0.8.0 | +| 2022-11 | SA6#52 | | | | | Implementation of the following p-CRs approved by SA6:
S6-223118, S6-223119, S6-223120, S6-223121, S6-223122 | | 0.9.0 | +| 2022-12 | SA#98-e | SP-221270 | | | | Submitted for Approval at SA#98-e | | 1.0.0 | +| 2022-12 | SA#98-e | SP-221270 | | | | MCC Editorial update for publication after TSG SA approval (SA#98-e) | | 18.0.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-97/raw.md b/raw/rel-18/23_series/23700-97/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..703134dfe16bdb6c494a4d450614c1bc4ed275d0 --- /dev/null +++ b/raw/rel-18/23_series/23700-97/raw.md @@ -0,0 +1,1327 @@ + + +# 3GPP TR 23.700-97 V18.1.0 (2023-06) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Application Capability Exposure for IoT Platforms; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G', and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Key Issues ..... | 8 | +| 4.1 Key issue #1: Background Data Transfer negotiation ..... | 8 | +| 4.2 Key issue #2: Application server monitoring and control of traffic ..... | 8 | +| 4.3 Key issue #3: IoT Platform PSM monitoring and configuration ..... | 9 | +| 4.4 Key issue #4: Configuration of Communication Patterns..... | 9 | +| 4.5 Key issue #5: NIDD configuration..... | 10 | +| 4.6 Key issue #6: Device Triggering services..... | 10 | +| 5 Solutions..... | 11 | +| 5.1 Solution #1: Application Service Management Service ..... | 11 | +| 5.1.1 Functional model for application service management..... | 11 | +| 5.1.1.1 General..... | 11 | +| 5.1.1.2 On-network functional model description ..... | 11 | +| 5.1.2 Functional entities description..... | 11 | +| 5.1.2.1 General..... | 11 | +| 5.1.2.2 Application service management client..... | 11 | +| 5.1.2.3 Application service management server ..... | 12 | +| 5.1.3 Configuring VAL server..... | 12 | +| 5.1.4 Request-response model..... | 12 | +| 5.1.4.1 ASM server requesting for on-demand status..... | 12 | +| 5.1.4.2 ASM Client pushes service experience report to the ASM Server ..... | 13 | +| 5.1.4.3 ASM Server pulls service experience report from the ASM Client ..... | 14 | +| 5.1.4.4 ASM Server determines corrective action ..... | 15 | +| 5.1.5 Subscribe-notify model ..... | 15 | +| 5.1.5.1 ASM server subscribes to the monitoring status information..... | 15 | +| 5.1.5.2 VAL server notifies the monitoring status information..... | 16 | +| 5.1.6 Reference Points..... | 16 | +| 5.1.6.1 General..... | 16 | +| 5.1.6.2 ASM-C..... | 16 | +| 5.1.6.3 ASM-UU..... | 16 | +| 5.1.6.4 ASM-S ..... | 16 | +| 5.2 Solution #2: IoT Platform deployment options ..... | 17 | +| 5.2.1 General ..... | 17 | +| 5.2.2 Deployment models in single PLMN operator domain..... | 17 | +| 5.2.2.1 General..... | 17 | +| 5.2.2.2 Single network exposure access model ..... | 17 | +| 5.2.2.3 Distributed network exposure access model..... | 18 | +| 5.3 Solution #3: IoT Platform Functional Models ..... | 19 | +| 5.3.1 General ..... | 19 | +| 5.3.2 On-network functional models ..... | 19 | +| 5.4 Solution #4: Device triggering ..... | 22 | +| 5.4.1 General ..... | 22 | +| 5.4.2 Procedures and information flows ..... | 22 | +| 5.4.2.1 Procedure ..... | 22 | +| 5.4.3 Evaluation..... | 23 | +| 5.5 Solution #5: Application Server status monitoring via CAPIF ..... | 23 | +| 5.5.1 Description ..... | 23 | +| 5.5.1.1 AS service status monitoring ..... | 23 | + +| | | | +|-----------------|-----------------------------------------------------------------------------------|-----------| +| 5.5.2 | Evaluation ..... | 24 | +| 5.6 | Solution #6: BDT configuration..... | 24 | +| 5.6.1 | General ..... | 24 | +| 5.6.2 | Procedures and information flows ..... | 24 | +| 5.6.2.1 | General ..... | 24 | +| 5.6.2.2 | Request and Select Background Data Transfer Policy ..... | 24 | +| 5.6.3 | Evaluation ..... | 26 | +| 5.7 | Solution #7: UE unified traffic pattern and monitoring management..... | 27 | +| 5.7.1 | General ..... | 27 | +| 5.7.2 | Procedures and information flows ..... | 27 | +| 5.7.2.1 | General ..... | 27 | +| 5.7.2.2 | UE unified traffic pattern and monitoring management subscription procedure ..... | 27 | +| 5.7.2.4 | Traffic pattern configuration request procedure ..... | 29 | +| 5.7.2.5 | Information Flows..... | 30 | +| 5.7.2.5.1 | UE unified traffic pattern and monitoring management subscription request ..... | 30 | +| 5.7.2.5.2 | UE unified traffic pattern and monitoring management subscription response..... | 31 | +| 5.7.2.5.3 | UE unified traffic pattern update notification ..... | 31 | +| 5.7.2.5.4 | Traffic pattern configuration request..... | 31 | +| 5.7.2.5.5 | Traffic pattern configuration response ..... | 32 | +| 5.7.3 | Management and 5GC exposure procedures ..... | 32 | +| 5.7.3.1 | General ..... | 32 | +| 5.7.3.2 | CP configuration procedure ..... | 32 | +| 5.7.3.3 | UE unified traffic pattern management procedure ..... | 33 | +| 5.7.3.4 | Network parameter coordination procedure ..... | 34 | +| 6 | Overall Evaluation ..... | 35 | +| 6.1 | Architecture evaluation ..... | 35 | +| 6.2 | Solution evaluations ..... | 36 | +| 6.2.1 | General ..... | 36 | +| 6.2.2 | Key issue #2: Application server monitoring and control of traffic ..... | 36 | +| 7 | Conclusions..... | 37 | +| 7.1 | Solution conclusions ..... | 37 | +| Annex A: | Change history ..... | 38 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document is a technical report which identifies SEAL functionality to support application capability exposure to general purpose servers or 3rd party IoT applications via IoT Platforms. Key issues and corresponding solutions necessary to ensure efficient use and deployment of IoT Platforms in the 5G network are included. + +The study takes into consideration the existing work for Core Network exposure in 3GPP TS 23.502 [2] and provides recommendations for normative work. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [3] 3GPP TR 23.503: "Policy and charging control framework for the 5G System (5GS)". +- [4] 3GPP TR 22.101: "Service aspects; Service principles". +- [5] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs" +- [6] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows" +- [7] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications" +- [8] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2". +- [9] 3GPP TR 23.700-98: "Study on Enhanced architecture for enabling Edge Applications". +- [10] 3GPP TS 29.122: " T8 reference point for Northbound APIs". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +Internet of Things (IoT): Network supporting interconnection of devices, machines, and low complexity entities. + +IoT Application: An application catering to one or more vertical domains which includes communication functionality for the Internet of Things. + +IoT Client: An entity that provides the client-side functionalities corresponding to a specific IoT Application. + +IoT Platform: An entity hosting a collection of services and enabling capabilities that supports IoT Applications. + +IoT Platform service: A generic name for a common service or enabling capability provided by an IoT Platform. + +IoT Platform Provider: A mobile network operator or a 3rd party service provider offering IoT Platform services to multiple 3rd party service providers or ASPs. + +IoT Server: An entity that provides the server side functionalities corresponding to a specific IoT Application. + +NOTE: The normative phase work will determine the mappings between these entities and SEAL entities. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|------------------------------------------| +| ASM | Application Service Management | +| ASP | Application Service Provider | +| BDT | Background Data Transfer | +| CAPIF | Common API Framework for northbound APIs | +| CIoT | Cellular IoT | +| CP | Control Plane | +| CPP | Communication Patterns Parameters | +| MIoT | Massive IoT | +| NEF | Network Exposure Function | +| NIDD | Non-IP Data Delivery | +| SEAL | Service Enablement Application Layer | +| SCEF | Service Capability Exposure Function | +| TAU | Tracking Area Update | +| VAL | Vertical Application Layer | + +# 4 Key Issues + +## 4.1 Key issue #1: Background Data Transfer negotiation + +The cellular network provides background data transfer (BDT) capabilities which save network resources and reduce device energy consumption. The 5GS provides procedures for BDT negotiation services as described in 3GPP TS 23.502 [2] clause 4.16.7. The corresponding NEF services (see 3GPP TS 23.502 [2] clause 5.2.6.6) allow the servers to provide parameters for requesting or optimizing the background data traffic for a set of UEs. + +Scenarios in which an IoT Platform interfaces with the Core Network to request future Background Data Transfer (BDT) Policies on behalf of IoT Servers need to be investigated further. In such scenarios the IoT Platform Provider leverages for its services a different business relationship with the MNO than the ASPs providing the individual IoT Applications. For example, a Smart City Platform may be configured to understand the reference to a charging rate based on the agreement with the operator (see 3GPP TS 23.503 [3] clause 6.1.2.4). At the same time, the ASP providing green building IoT applications hosted by the IoT Platform may rely on no special operator agreements. + +In such scenarios, the IoT Servers provide the IoT Platform information such as expected data volume per UE, preferred time window or optional location, for a set of targeted IoT Clients. The IoT Platform negotiates future BDT policies with the Core Network as detailed in 3GPP TS 23.502[2] clause 4.16.7. Then the relevant information from the selected BDT policy is provided to the initiating IoT Servers, in order to initiate the data transfer. + +Hence, it is required to study: + +- How the SEAL functional model and deployment options may be leveraged for the implementation of IoT Platforms supporting such scenarios. +- Whether and how the IoT Platform in this scenario can: + - determine the reference to the charging rate (based on agreement with the operator) without exposure of this information to the IoT Servers. + - aggregate requirements/ requests from multiple IoT Servers resulting in a single future BDT negotiation request, e.g., when the same group of UEs is targeted. + - select a BDT Policy from a set of Possible Transfer Policies provided by the Core Network, based on IoT Server input. + +## 4.2 Key issue #2: Application server monitoring and control of traffic + +Clause 31 of 3GPP TS 22.101 [4] has provided requirements for control of traffic from UE-based applications toward associated server. When an application on a third-party server or the third-party server itself becomes congested or fails, the traffic towards that server needs to be controlled to avoid/mitigate potential issues caused by resulting unproductive use of 3GPP network resources. Following are some of the requirements: + +*The 3GPP network shall be able to control (i.e., block and/or prioritize) traffic from UEs to an application on a third-party server or the third-party server itself without affecting traffic to other applications on the third-party server or to other third-party servers.* + +*The 3GPP network shall be able to receive a status indication from the third-party server when an application on it is experiencing congestion or failure, and when normal operation resumes. Such a status indication may be sent periodically, and/or when the status of the application changes.* + +*The 3GPP network shall be able to detect and monitor a third-party server's operational status e.g., congestion levels, failure, and unavailability of the third-party server.* + +Consider a scenario where an IoT application server serves millions of devices. In an event where the application server's response time is increased due to high traffic congestion at the application server, it is required to be able to control (i.e., block and/or prioritize) the traffic from the UEs or IoT devices towards the application server. + +Hence, it is required to study: + +- 1) How to enhance the enabler layer (e.g., SEAL, CAPIF) to support service monitoring of third-party application servers? +- 2) How to monitor a third-party server's operational status e.g., congestion levels, failure, and unavailability of the third-party server? How to control/influence the traffic when the third-party application server is experiencing congestion or failure, and when normal operation resumes? + +## 4.3 Key issue #3: IoT Platform PSM monitoring and configuration + +The cellular network exposes the capabilities for IoT Servers to provide network parameters such as: maximum response time, maximum latency, and suggested number of downlink packets. These parameters may then be used by the Core Network to derive periodic TAU Timer and Active time for the PSM mode, or to configure in-network extended buffering. + +IoT Platforms provide services to multiple IoT Servers with different services for the same UEs using PSM mode. Each IoT Server is aware only of its own communication requirements, e.g., communication schedules, delay tolerance for regular or high-priority messaging. Based on these communication requirements, some IoT Servers may be able to derive how long the UE should be unreachable for power saving purposes, or how long the UE should stay active before returning to PSM. In the meantime, other IoT Servers may be agnostic of the of underlying network used, therefore unable to derive such information. + +If separate Core Network parameter configurations are derived individually by each IoT Server for the same UE, the CN determines the final value. However, this determination does not have any service-level context information. In some cases, the greatest optimizations are achieved when the calculations take in consideration the current network parameter configuration, which currently can be inferred only through the use of device monitoring. + +When extended buffering is employed, the Network Parameter configuration can also be used by the application layer for retransmission timer configuration. + +Scenarios in which an IoT Platform interfaces with the Core Network to provide optimal configuration of network parameters determined based on the communication characteristics from multiple IoT Servers need to be investigated further. + +Hence, it is required to study whether and how the needs of multiple IoT servers can be satisfied via a single SEAL IoT Platform for the following: + +- Capability to determine optimal network parameter values based on communication characteristics (e.g., communication schedules, delay tolerance) of services from multiple IoT Servers. +- Capability to configure device monitoring and receive Monitoring Event notifications via exposure APIs. +- Capability to provide the network parameter values (e.g., maximum response time) via exposure APIs, to the Core Network. +- Capability to expose the derived network parameter configuration (e.g., from monitoring events) to the application layer. + +## 4.4 Key issue #4: Configuration of Communication Patterns + +Many IoT devices have predictable communication behaviour. The Communication Pattern Parameters (CPP) Provisioning network exposure API has been introduced to make this information available to the network for resource planning and optimizations (see 3GPP 29.522 [5] clause 4.4.5). This capability provides optimizations for the devices as well, by way of reduction of signalling, energy saving, fewer sleep/awake transitions, etc. + +IoT Servers should be able to provide the IoT Platform information on the communication behavior of the application(s) supported. In turn, the IoT platform should be able to aggregate the communication patterns of multiple applications interacting with the same UE before providing them to the underlying network. + +Given the scale and the importance of this functionality, the CPP Provisioning capability also supports providing single configurations for UE groups, e.g., for support of MIoT. An IoT platform implemented using SEAL services should be + +enabled to implement CPP Provisioning for groups of UE, along with performing group management. However, the IoT Platform needs to be enabled to be provided with corresponding input by the individual IoT Servers. + +Hence, it is required to study: + +- whether and how use of the CPP Provisioning API can be enabled on IoT Platforms implemented using SEAL services, using configurations provided by multiple IoT Servers for the same UE. +- whether and how use of CPP Provisioning API use can be enabled on IoT Platforms implemented using SEAL services to provide configurations for UE groups managed via the IoT Platform. + +## 4.5 Key issue #5: NIDD configuration + +Since Release 13, 3GPP introduced the ability to send data to and from the UE in NAS messaging through the "Control Plane (CP) CIoT Optimizations" feature. Since no data plane set up is required, using the CP CIoT optimizations results in a reduced total number of control plane messages that are required to send short data transactions. CIoT Optimizations include the option of exchanging NEF-anchored Non-IP Data. + +Use of Non-IP Data Delivery (NIDD) requires an initial NEF configuration step, which includes MTC Provider Information and Reliable Data Service Configuration, both of which usually require a pre-established relationship with the MNO. In addition, for the purpose of sending mobile-terminated Group NIDD messages, the NIDD Configuration procedure is used by the NEF to resolve the mapping of External Group Identifier to individual UEs. Therefore, an IoT platform implemented using SEAL services should be enabled to perform NIDD configuration for UE groups on behalf of the IoT Servers. + +Hence, it is required to study whether and how NIDD configuration services by the IoT Platform implemented using SEAL services, on behalf of one or more IoT Servers, may be enabled. Configuration of group NIDD services should be also included in the study. + +## 4.6 Key issue #6: Device Triggering services. + +Currently, the SEAL specification in 3GPP TS 23.434 [6] does not include functionality for leveraging the Device Triggering network exposure API. + +Typically, commercial IoT Platforms store and maintain a "digital twin" of the device. Such digital twin is accessed and used by the device (e.g., to publish sensor readings to the IoT Platform or to receive commands from the IoT Platform) as well as by the IoT Applications to retrieve sensor readings of a device or to issue commands to a device. This digital twin has several benefits since it allows the IoT Platform to reduce communication loads and allows devices to go to sleep. This can be done without impacting the availability of device information to the IoT Applications. + +The communication between the IoT Applications and the device is asynchronous and is managed by the IoT platform. The IoT platform needs to perform device triggering when synchronization between the digital twin is needed and the UE needs to establish connectivity. + +Hence, it is required to study whether the IoT Applications should directly use the existing network exposure capability for device triggering or whether the IoT Platform should be enhanced to provide device triggering support on behalf of the IoT Applications. + +# 5 Solutions + +## 5.1 Solution #1: Application Service Management Service + +### 5.1.1 Functional model for application service management + +#### 5.1.1.1 General + +The Application Service Management (ASM) service provides application service monitoring and traffic control service. The functional model for the application service management is based on the generic functional model specified in clause 6 of 3GPP TS 23.434 [6]. It is organized into functional entities to describe a functional architecture which addresses the support for application service management aspects for vertical applications. The on-network functional model is specified in this clause. + +#### 5.1.1.2 On-network functional model description + +Figure 5.1.1.2-1 illustrates the generic on-network functional model for application service management. + +![Figure 5.1.1.2-1: On-network functional model for application service management. The diagram shows three main components: UE, 3GPP network system, and VAL server(s). The UE contains VAL client(s) and Application Service Management Client. The 3GPP network system contains VAL-UU, ASM-UU, and T8 / N33 interfaces. The VAL server(s) contains VAL server(s) and Application Service Management Server. The diagram is divided into two horizontal sections: VAL (top) and SEAL (bottom). The VAL section shows the VAL client(s) connected to the VAL server(s) via the VAL-UU interface. The SEAL section shows the Application Service Management Client connected to the Application Service Management Server via the ASM-UU interface. The Application Service Management Client is also connected to the VAL client(s) via the ASM-C interface. The Application Service Management Server is also connected to the VAL server(s) via the ASM-S interface. The T8 / N33 interface is shown between the 3GPP network system and the Application Service Management Server.](18442e4e239480f0c3c95b547aa8fde2_img.jpg) + +Figure 5.1.1.2-1: On-network functional model for application service management. The diagram shows three main components: UE, 3GPP network system, and VAL server(s). The UE contains VAL client(s) and Application Service Management Client. The 3GPP network system contains VAL-UU, ASM-UU, and T8 / N33 interfaces. The VAL server(s) contains VAL server(s) and Application Service Management Server. The diagram is divided into two horizontal sections: VAL (top) and SEAL (bottom). The VAL section shows the VAL client(s) connected to the VAL server(s) via the VAL-UU interface. The SEAL section shows the Application Service Management Client connected to the Application Service Management Server via the ASM-UU interface. The Application Service Management Client is also connected to the VAL client(s) via the ASM-C interface. The Application Service Management Server is also connected to the VAL server(s) via the ASM-S interface. The T8 / N33 interface is shown between the 3GPP network system and the Application Service Management Server. + +**Figure 5.1.1.2-1: On-network functional model for application service management** + +NOTE: The normative phase work will determine whether and how service-based interfaces are used in this architecture. + +The interface between ASM client and ASM server is ASM-UU interface. The ASM client interacts with VAL client using ASM-C interface and ASM server interacts with VAL server using ASM-S interface. + +The ASM server communicates with the SCEF via T8 reference point or communicates with the NEF via N33 reference point to control application specific traffic from the underlying 3GPP network system. + +### 5.1.2 Functional entities description + +#### 5.1.2.1 General + +The functional entities for application service management SEAL service are described in the following subclauses. + +#### 5.1.2.2 Application service management client + +The application service management client acts as a SEAL client for application service monitoring and traffic control function. + +#### 5.1.2.3 Application service management server + +The ASM server is a functional entity used to configure one or more application servers related to 3GPP system information as well as the network. It also acts as a co-ordination layer in subscribing to the VAL server and 3GPP network for any changes in the configuration and inform the other in order to perform necessary actions (like blocking or controlling traffic). + +### 5.1.3 Configuring VAL server + +To monitor status of the application service, the ASM server can configure the VAL server to monitor status information. + +![Sequence diagram for Figure 5.1.3-1: Configuring VAL server. The diagram shows two lifelines: VAL server and ASM Server. The ASM Server sends a message '1. ASM configuration request' to the VAL server. The VAL server responds with '2. ASM configuration response'.](853f59c89931a666c07903b31d098277_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant ASM Server + Note right of ASM Server: 1. ASM configuration request + VAL server->>ASM Server: 2. ASM configuration response +``` + +Sequence diagram for Figure 5.1.3-1: Configuring VAL server. The diagram shows two lifelines: VAL server and ASM Server. The ASM Server sends a message '1. ASM configuration request' to the VAL server. The VAL server responds with '2. ASM configuration response'. + +**Figure 5.1.3-1: Configuring VAL server** + +- 1) In order to configure the VAL server, the ASM server sends ASM Configuration request towards VAL server including all parameters to be monitored the VAL server. The parameters include average request queue length, average time to process request, CPU usage, memory usage, etc. +- 2) Upon received the request, the VAL server sends response and starts monitoring all activities. + +NOTE: It is to be addressed in the normative phase whether configuring VAL server procedure is required or not. + +### 5.1.4 Request-response model + +#### 5.1.4.1 ASM server requesting for on-demand status + +The ASM server can request the VAL server to provide its status information. The ASM server may choose to request status information periodically, which can give the ASM server the possible trend of the VAL server status. Figure 5.1.4.1-1 shows the procedure for the ASM server to request on-demand status request from the VAL server. + +![Sequence diagram for Figure 5.1.4.1-1: ASM server requesting for on-demand status. The diagram shows two lifelines: ASM Server and VAL Server. The ASM Server has a self-call '1. Based on configuration or request from other entities, decides to request status of the VAL server'. It then sends '2. ASM on-demand status request' to the VAL Server. The VAL Server responds with '3. ASM on-demand status response'. Finally, the ASM Server has a self-call '4. Upon trigger, share the status information to VAL Clients or other interested entities'.](426efb7efdc753a13f2fa16f7bff9429_img.jpg) + +``` +sequenceDiagram + participant ASM Server + participant VAL Server + Note left of ASM Server: 1. Based on configuration or request from other entities, decides to request status of the VAL server + ASM Server->>VAL Server: 2. ASM on-demand status request + VAL Server->>ASM Server: 3. ASM on-demand status response + Note left of ASM Server: 4. Upon trigger, share the status information to VAL Clients or other interested entities +``` + +Sequence diagram for Figure 5.1.4.1-1: ASM server requesting for on-demand status. The diagram shows two lifelines: ASM Server and VAL Server. The ASM Server has a self-call '1. Based on configuration or request from other entities, decides to request status of the VAL server'. It then sends '2. ASM on-demand status request' to the VAL Server. The VAL Server responds with '3. ASM on-demand status response'. Finally, the ASM Server has a self-call '4. Upon trigger, share the status information to VAL Clients or other interested entities'. + +**Figure 5.1.4.1-1: ASM server requesting for on-demand status** + +- 1) Based on configurations such monitoring status information request from other entities (e.g., VAL service provider), ASM server initiates the on-demand status request towards the VAL server. +- 2) The ASM server sends an on-demand status request to the VAL server. The request includes the configuration parameters whose status needs to be included in the response. +- 3) The VAL server immediately responds to the ASM server with a report containing status information identified by the ASM server and available to the VAL server. +- 4) Upon receiving the report, the ASM server updates the monitoring status of the VAL Server to the other VAL UE(s), VAL Client(s) or 3GPP network as required. + +#### 5.1.4.2 ASM Client pushes service experience report to the ASM Server + +The ASM client keeps monitoring the different service KPIs as experienced for the application service. The KPIs include application specific performance measurements like end-to-end response time, connection bandwidth, request rate, server availability time, etc. On request from user or VAL client or any other trigger conditions, the ASM client sends the service experience report about a VAL server to the ASM server. Figure 5.1.4.2-1 illustrates a scenario of ASM Client pushes service experience report to the ASM Server. + +Pre-condition: + +- 1). ASM client determines to send service experience report based on certain criteria (e.g. VAL User request, VAL client request, any preconfigured or explicit configured triggering event, periodic event, like so) + +![Sequence diagram showing the interaction between an ASM Client and an ASM Server. The client sends a 'Push service experience request' to the server. The server then performs internal steps: 'Store the report / feedback', 'Data collection', and 'Corrective action' (indicated by a dashed box). Finally, the server sends a 'Push service experience Response' back to the client.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +``` +sequenceDiagram + participant ASM Client + participant ASM Server + Note right of ASM Server: 2. Store the report / feedback + Note right of ASM Server: 3. Data collection + Note right of ASM Server: 5. Corrective action + ASM Client->>ASM Server: 1. Push service experience request + ASM Server-->>ASM Client: 4. Push service experience Response +``` + +Sequence diagram showing the interaction between an ASM Client and an ASM Server. The client sends a 'Push service experience request' to the server. The server then performs internal steps: 'Store the report / feedback', 'Data collection', and 'Corrective action' (indicated by a dashed box). Finally, the server sends a 'Push service experience Response' back to the client. + +**Figure 5.1.4.2-1: ASM Client pushes service experience report to the ASM Server** + +- 1). The ASM client sends Push service experience request to the ASM server. The request contains service experience report about a VAL server (e.g. end-to-end response time as experienced by client, connection bandwidth, request rate by client, VAL server availability, etc) and includes the VAL UE ID, VAL service ID, VAL server identity for which the report is being sent and time stamp of the report. +- 2). Upon receiving the Push service experience request from the ASM client, the ASM server stores the report in to the database or permanent storage. + +- 3). The ASM server may take further actions based on the analysis of the report as shared by the ASM client. + - a) Based on service experience report, the ASM server may decide to collect additional information from other UEs or ASM clients which use the same VAL server (e.g. by using pull service experience procedure as specified in clause 5.1.4.3). + - 4). The ASM server sends Push service experience response to the ASM client. +- NOTE: Step 3 and 4 can be performed in parallel. +- 5). The ASM server may determine the corrective action as specified in clause 5.1.4.4. If the issue is identified with the VAL UE, the ASM server may inform the corrective actions to be taken by the VAL UE. + +#### 5.1.4.3 ASM Server pulls service experience report from the ASM Client + +Figure 5.1.4.3-1 illustrates the procedure for the ASM server to pull the service experience report from the ASM clients. The procedure can be initiated by the ASM server upon receiving a Push service experience request from an ASM client or upon receiving a request from application service provider (application server) to get the service experience report from the clients or any other event that requires the ASM server to determine the service experience data. + +![Sequence diagram showing the procedure for the ASM Server to pull the service experience report from the ASM Client. The diagram involves two main participants: ASM Client and ASM Server. The sequence of messages is: 1. Pull service experience request (from ASM Server to ASM Client); 2. take user consent to send report / feedback (internal to ASM Client, shown in a dashed box); 4. Pull service experience Response (from ASM Client to ASM Server); 4. Store the report / feedback (internal to ASM Server, shown in a solid box); 5. Corrective action (internal to ASM Server, shown in a dashed box).](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` +sequenceDiagram + participant ASM Server + participant ASM Client + Note right of ASM Server: 4. Store the report / feedback + Note right of ASM Server: 5. Corrective action + ASM Server->>ASM Client: 1. Pull service experience request + Note left of ASM Client: 2. take user consent to send report / feedback + ASM Client->>ASM Server: 4. Pull service experience Response +``` + +Sequence diagram showing the procedure for the ASM Server to pull the service experience report from the ASM Client. The diagram involves two main participants: ASM Client and ASM Server. The sequence of messages is: 1. Pull service experience request (from ASM Server to ASM Client); 2. take user consent to send report / feedback (internal to ASM Client, shown in a dashed box); 4. Pull service experience Response (from ASM Client to ASM Server); 4. Store the report / feedback (internal to ASM Server, shown in a solid box); 5. Corrective action (internal to ASM Server, shown in a dashed box). + +**Figure 5.1.4.3-1: ASM Server pulls service experience report from the ASM Client** + +- 1). The ASM server sends Pull service experience request to the ASM client. The request contains identity of the specific VAL server for which the service experience report is required. The request includes the VAL service ID and VAL server identity for which the report is requested. +- 2). Upon receiving the Pull service experience request from the ASM server, the ASM client takes user consent to send the report if the user consent is not available already. +- 3). The ASM client sends the Pull service experience response to the ASM server. The response contains result indicating whether the report is available or not. If report is available, the response contains service experience report about a VAL server (e.g. end-to-end response time as experienced by client, connection bandwidth, request rate by client, VAL server availability, etc) and includes the VAL UE ID, VAL service ID, VAL server identity for which the report is being sent and time stamp of the report. +- 4). The ASM server stores the service experience report into the database or permanent storage. +- 5). The ASM server may takes the corrective action as specified in clause 5.1.4.4. + +#### 5.1.4.4 ASM Server determines corrective action + +Based on the collective analysis of all reports, the ASM server performs following actions: + +- 1) Determining the entity producing the issue, i.e. whether the reported issue is at VAL client or VAL server or 3GPP network. + +NOTE 1: How the ASM server determines whether the issue is at the VAL client, VAL server or the 3GPP network is implementation specific + +- 2) Once the entity causing the issue is identified, the ASM Server need to determine the corrective action for that entity. + +NOTE 2: The ASM server may subscribe for monitoring events (e.g. UE reachability, Communication failure, PDU Session Status) to 5GC as specified in clause 5.2.6.2 of 3GPP TS 29.502 [2] and may uses the information received via notification (along with the service experience reports received from ASM client) in determining the entity producing the issue and the possible corrective action for that entity. + +NOTE 3: ASM server logic and algorithm to determine the corrective action based on the entity causing the issue (i.e. issue is at VAL client or VAL server or the 3GPP network), is out of scope of this specification and implementation specific. + +- 3) ASM server informs the corrective action towards the entity causing the issue. + +NOTE 4: How ASM server indicates the suggestion for action to VAL layer entities is implementation specific. + +### 5.1.5 Subscribe-notify model + +#### 5.1.5.1 ASM server subscribes to the monitoring status information + +Figure 5.1.5.1-1 shows the procedure for the ASM server to subscribe to the monitoring status information of the VAL server. The ASM server does not need to configure the VAL server in advance. + +![Sequence diagram showing the ASM server requesting monitoring status information from the VAL server.](220869911a1ecfa1dd4aa6d750319aad_img.jpg) + +``` +sequenceDiagram + participant ASM Server + participant VAL Server + Note left of ASM Server: 1. Based on configuration or request from other entities, decides to subscribe status of the VAL server + ASM Server->>VAL Server: 2. ASM monitoring information subscribe request + VAL Server-->>ASM Server: 3. ASM monitoring information subscribe response +``` + +The diagram illustrates a sequence of interactions between an ASM Server and a VAL Server. It begins with a note on the ASM Server side stating, "1. Based on configuration or request from other entities, decides to subscribe status of the VAL server". This is followed by a message "2. ASM monitoring information subscribe request" sent from the ASM Server to the VAL Server. Finally, a message "3. ASM monitoring information subscribe response" is sent from the VAL Server back to the ASM Server. + +Sequence diagram showing the ASM server requesting monitoring status information from the VAL server. + +**Figure 5.1.5.1-1: ASM server requesting for on-demand status** + +- 1) Based on configurations request from other entities to provide monitoring status information periodically or based on event, ASM server decides to initiate the monitoring information subscribe request to the VAL server. +- 2) The ASM server sends a monitoring information subscribe request to the VAL server. The request includes all parameters to be monitored for UE and VAL server. The parameters include average request queue length, average time to process request, CPU usage, memory usage, etc. The request also includes events when the VAL server needs to send the notification. +- 3) The VAL server sends a monitoring information subscribe response to the ASM server containing success or failure of the request. + +#### 5.1.5.2 VAL server notifies the monitoring status information + +Figure 5.1.5.2-1 shows the notification from VAL server towards the ASM server on occurrence of the event. + +Pre-conditions: + +- 1) The ASM server is subscribed to the monitoring status information. + +![Sequence diagram showing the VAL server notifying the ASM server about a monitoring event. The diagram includes two lifelines: ASM Server and VAL Server. Step 1a shows an event occurring on the VAL Server. Step 1b shows the VAL Server sending a notification to the ASM Server. Step 2 shows the ASM Server sharing the status information with VAL Clients or other interested entities.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant ASM Server + Note right of VAL Server: 1a. Event occurs (status being monitored has crossed threshold value) + VAL Server->>ASM Server: 1b. ASM monitoring information notify + Note left of ASM Server: 2. Upon trigger, share the status information to VAL Clients or other interested entities + +``` + +Sequence diagram showing the VAL server notifying the ASM server about a monitoring event. The diagram includes two lifelines: ASM Server and VAL Server. Step 1a shows an event occurring on the VAL Server. Step 1b shows the VAL Server sending a notification to the ASM Server. Step 2 shows the ASM Server sharing the status information with VAL Clients or other interested entities. + +**Figure 5.1.5.2-1: VAL server notifies the monitoring status information** + +- 1) When the event occurs as specified by the ASM server in the subscription request, the VAL server sends monitoring information notification to the ASM server with a report containing status information identified by the ASM server and available to the VAL server. +- 2) Upon receiving the report, the ASM server updates the monitoring status of the VAL to the other VAL UE(s), VAL Client(s) or 3GPP network as required. + +### 5.1.6 Reference Points + +#### 5.1.6.1 General + +This clause describes the reference points of the architecture for application service management. + +#### 5.1.6.2 ASM-C + +This is the interface between ASM Client and VAL Client. It is used by ASM client to share information regarding application service monitoring and provisioning of UE clients. + +#### 5.1.6.3 ASM-UU + +This is the interface between ASM Client and ASM Server. It is utilized by ASM Server to configure UE and provide policies related to the application service. The ASM server uses this interface to provide notifications about possible actions to control the traffic. + +#### 5.1.6.4 ASM-S + +This is the interface between ASM Server and VAL Server. It is used for provisioning and monitoring of VAL AS as per the policies and profiles of the VAL service. The 3GPP network status for the VAL service is monitored by ASM Server and notified to the VAL server if changes for it to take suitable action. This is service-based interface where VAL server and ASM Server exposes services as APIs, to be invoked by other entities. + +### 5.1.7 Evaluation + +The solution addresses KI#2 related to Application server monitoring. The solution proposes functional model for application service management, where ASM server collects data from VAL server or ASM client (along with VAL + +client) and if required, it decides corrective action to take for VAL client or VAL server. ASM server logic and algorithm to determine the corrective action is implementation specific. The solution proposes data collection procedures using request-response model and also subscribe-notify model. + +## 5.2 Solution #2: IoT Platform deployment options + +### 5.2.1 General + +IoT Platforms enable applications and services from multiple verticals by providing a set of common services for deploying dynamic, performant, scalable and resilient services which may be underlying-network agnostic. + +Fig 5.2.1-1 depicts a generic IoT Platform with IoT Platform Common Services (IoT-PCS) servers enabling a set of applications deployed using corresponding servers (IoT-App), which may belong to different verticals. On the device side, corresponding IoT-PCS and IoT-App clients enable the client-side functionality. + +![Figure 5.2.1-1: Generic representation of services enabled via IoT Platforms. The diagram shows two main components: a Device and an IoT Platform. The Device contains IoT-App1 Client, IoT-AppM Client, and IoT-PCS Client. The IoT Platform contains IoT-App1 Server, IoT-App2 Server, IoT-AppN Server, and IoT-PCS Server(s).](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates the generic representation of services enabled via IoT Platforms. It is divided into two main components: a Device and an IoT Platform. + +**Device:** This component is represented by a rounded rectangle. It contains three sub-components: "IoT-App1 Client", "IoT-AppM Client", and "IoT-PCS Client". The first two are small boxes at the top, separated by a dashed line, and the third is a larger box at the bottom. + +**IoT Platform:** This component is represented by a larger rounded rectangle. It contains four sub-components: "IoT-App1 Server", "IoT-App2 Server", "IoT-AppN Server", and "IoT-PCS Server(s)". The first three are small boxes at the top, separated by a dashed line, and the fourth is a larger box at the bottom. + +Figure 5.2.1-1: Generic representation of services enabled via IoT Platforms. The diagram shows two main components: a Device and an IoT Platform. The Device contains IoT-App1 Client, IoT-AppM Client, and IoT-PCS Client. The IoT Platform contains IoT-App1 Server, IoT-App2 Server, IoT-AppN Server, and IoT-PCS Server(s). + +**Figure 5.2.1-1: Generic representation of services enabled via IoT Platforms** + +The following clauses introduce functional models for supporting a variety of IoT Platform deployments based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [6]. + +**NOTE:** The IoT Platform functional and deployment models in this document focus only on SEAL functionality to support application capability exposure to general purpose servers or 3rd party IoT applications. + +### 5.2.2 Deployment models in single PLMN operator domain + +#### 5.2.2.1 General + +IoT Platform deployment models for single PLMN operator domain case are described in this clause. + +The following models are differentiated primarily based on which entities have network exposure access and may implement the necessary functionality. Therefore, for the purpose of network exposure, IoT-PCS servers are implemented as SEAL servers. While some IoT-PCS services may be implemented as VAL services, the representation of that implementation option is abstracted in the following models. + +#### 5.2.2.2 Single network exposure access model + +Figure 5.2.2.2-1 illustrates the single network exposure access deployment model in single PLMN operator domain + +![Figure 5.2.2.2-1: Single network exposure access deployment model in single PLMN operator domain. The diagram shows a UE containing an IoT-App VAL client(s) and an IoT-PCS SEAL client(s). The IoT-App client connects to an IoT-App VAL server(s) via the VAL-UU interface. The IoT-PCS client connects to an IoT-PCS SEAL server(s) via the SEAL-UU interface. Both the IoT-App VAL server(s) and the IoT-PCS SEAL server(s) connect to the 3GPP network system via Network interfaces. The SEAL-C interface is shown between the IoT-App VAL client(s) and the IoT-PCS SEAL client(s) within the UE. The SEAL-S interface is shown between the IoT-App VAL server(s) and the IoT-PCS SEAL server(s).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Figure 5.2.2.2-1: Single network exposure access deployment model in single PLMN operator domain. The diagram shows a UE containing an IoT-App VAL client(s) and an IoT-PCS SEAL client(s). The IoT-App client connects to an IoT-App VAL server(s) via the VAL-UU interface. The IoT-PCS client connects to an IoT-PCS SEAL server(s) via the SEAL-UU interface. Both the IoT-App VAL server(s) and the IoT-PCS SEAL server(s) connect to the 3GPP network system via Network interfaces. The SEAL-C interface is shown between the IoT-App VAL client(s) and the IoT-PCS SEAL client(s) within the UE. The SEAL-S interface is shown between the IoT-App VAL server(s) and the IoT-PCS SEAL server(s). + +Figure 5.2.2.2-1: Single network exposure access deployment model in single PLMN operator domain + +In this model network interfaces are available to the IoT-PCS servers providing SEAL services via the SEAL-S reference point to IoT Application (IoT-App) servers as VAL servers. The IoT-PCS servers communicate with the SCEF via T8 reference point or with the NEF via N33 reference point. + +The interface between the IoT-PCS client and IoT-PCS server is an instance of a SEAL-UU reference point, e.g., CM-UU. The IoT-PCS client interacts with IoT-App client (as a VAL client) using an instance of a SEAL-C reference point. The IoT-PCS server interacts with IoT-App server(s) over instance(s) of SEAL-S reference point(s). + +#### 5.2.2.3 Distributed network exposure access model + +Figure 5.2.2.3-1 illustrates the distributed network exposure access deployment model in single PLMN operator domain + +![Figure 5.2.2.3-1: Distributed network exposure access deployment model in single PLMN operator domain. The diagram shows a UE containing an IoT-App VAL client(s) and an IoT-App and IoT-PCS SEAL client(s). The IoT-App VAL client(s) connects to an IoT-App VAL server(s) via the VAL-UU interface. The IoT-App and IoT-PCS SEAL client(s) connects to an IoT-PCS SEAL server(s) via the SEAL-UU interface. The IoT-App VAL server(s) connects to the IoT-App SEAL server(s) via the *SEAL-S* interface (internal to IoT-App). The IoT-PCS SEAL server(s) connects to the IoT-App SEAL server(s) via the SEAL-S and SEAL-X interfaces. The SEAL-C interface is shown between the IoT-App VAL client(s) and the IoT-App and IoT-PCS SEAL client(s) within the UE. The 3GPP network system is shown with Network interfaces connecting to the IoT-App and IoT-PCS SEAL client(s) and the IoT-PCS SEAL server(s).](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +\*SEAL-S\* - Internal to IoT-App + +Figure 5.2.2.3-1: Distributed network exposure access deployment model in single PLMN operator domain. The diagram shows a UE containing an IoT-App VAL client(s) and an IoT-App and IoT-PCS SEAL client(s). The IoT-App VAL client(s) connects to an IoT-App VAL server(s) via the VAL-UU interface. The IoT-App and IoT-PCS SEAL client(s) connects to an IoT-PCS SEAL server(s) via the SEAL-UU interface. The IoT-App VAL server(s) connects to the IoT-App SEAL server(s) via the \*SEAL-S\* interface (internal to IoT-App). The IoT-PCS SEAL server(s) connects to the IoT-App SEAL server(s) via the SEAL-S and SEAL-X interfaces. The SEAL-C interface is shown between the IoT-App VAL client(s) and the IoT-App and IoT-PCS SEAL client(s) within the UE. The 3GPP network system is shown with Network interfaces connecting to the IoT-App and IoT-PCS SEAL client(s) and the IoT-PCS SEAL server(s). + +Figure 5.2.2.3-1: Distributed network exposure access deployment model in single PLMN operator domain + +In this model network interfaces are available to the IoT-PCS servers as well as to the IoT-App servers, therefore they both implement SEAL services. + +The IoT Application uses both SEAL and VAL servers and clients. The IoT-PCS server(s) provides additional SEAL services via the SEAL-S reference point to IoT-App VAL servers. + +The IoT-PCS and IoT-App SEAL servers communicate with the SCEF via T8 reference point or with the NEF via N33 reference point. It is assumed that each SEAL service deployed may be provided to a given IoT Application by either or both SEAL servers and that the IoT Platform provider can configure the PCS and IoT Applications in the IoT Platform with policies determining unambiguously which SEAL service to be used for the IoT application operations. The IoT-PCS and IoT-App SEAL servers may interact over an instance of SEAL-X reference point. + +The interface between the IoT-PCS SEAL client and IoT-PCS SEAL server is an instance of a SEAL-UU reference point, e.g., GM-UU. The interface between the IoT-App SEAL client and IoT-App SEAL server is also instance of a SEAL-UU reference point, e.g., CM-UU. + +The SEAL clients interact with VAL clients using SEAL-C reference points. The IoT-PCS SEAL server interacts with IoT-App VAL server over an instance of a SEAL-S reference point. + +## 5.3 Solution #3: IoT Platform Functional Models + +### 5.3.1 General + +The functional model for IoT Platform services is based on the generic SEAL functional model specified in 3GPP TS 23.434 [6] clause 6. It is organized into functional entities to describe a functional architecture which addresses the support for IoT Platforms. + +### 5.3.2 On-network functional models + +Figure 5.3.2-1 illustrates the generic on-network functional model for IoT Platform services in single network exposure access deployment mode. + +![Figure 5.3.2-1: Functional model for IoT-PCS (single network exposure access). The diagram shows three main components: UE, 3GPP network system, and IoT-App/PCS servers. The UE contains an IoT-App VAL client(s) and an IoT-PCS SEAL client(s). The 3GPP network system is in the center. The right side contains an IoT-App VAL server(s) and an IoT-PCS SEAL server(s). Connections include VAL-UU between IoT-App VAL client and server, IP-C between IoT-App VAL client and IoT-PCS SEAL client, IP-UU between IoT-PCS SEAL client and server, and IP-S between IoT-App VAL server and IoT-PCS SEAL server. A dashed line separates the VAL and SEAL layers. A 'Network interfaces' label is shown between the 3GPP network system and the IoT-PCS SEAL server.](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +Figure 5.3.2-1: Functional model for IoT-PCS (single network exposure access). The diagram shows three main components: UE, 3GPP network system, and IoT-App/PCS servers. The UE contains an IoT-App VAL client(s) and an IoT-PCS SEAL client(s). The 3GPP network system is in the center. The right side contains an IoT-App VAL server(s) and an IoT-PCS SEAL server(s). Connections include VAL-UU between IoT-App VAL client and server, IP-C between IoT-App VAL client and IoT-PCS SEAL client, IP-UU between IoT-PCS SEAL client and server, and IP-S between IoT-App VAL server and IoT-PCS SEAL server. A dashed line separates the VAL and SEAL layers. A 'Network interfaces' label is shown between the 3GPP network system and the IoT-PCS SEAL server. + +**Figure 5.3.2-1: Functional model for IoT-PCS (single network exposure access)** + +The IoT-PCS client communicates with the IoT-PCS server over the IP-UU reference point, which is an instance of the SEAL-UU generic reference point. The IoT-PCS client provides IoT platform common services functionality to the + +IoT-App client(s) over IP- C reference point, which is an instance of the SEAL-C reference point. The VAL IoT-App server communicates with the IoT-PCS server over the IP-S reference point, which is an instance of the SEAL-S generic reference point. + +The IoT-PCS server communicates with the SCEF via T8 reference point. The IoT-PCS server communicates with the NEF via N33 reference point by mechanisms defined in clause 5.2.6.2 of 3GPP TS 23.502 [2]. + +When IoT Applications are deployed in a stand-alone mode, without the use of an IoT Platform service, the functional model in Figure 5.3.2-2 applies. In this case, SEAL services and network exposure may be implemented internally to IoT-App. + +![Figure 5.3.2-2: Functional model for stand-alone IoT Applications (without IoT-PCS services). The diagram shows three main components: UE, 3GPP network system, and IoT-App. The UE contains 'IoT-App VAL client(s)' and 'IoT-App and SEAL client(s)'. The IoT-App contains 'IoT-App VAL server(s)' and 'IoT-App SEAL server(s)'. Reference points are labeled: VAL-UU between UE and 3GPP network system; IP-UU between UE and 3GPP network system; IP-C between UE's client components; IP-S* between IoT-App's server components. A dashed line separates the VAL and SEAL layers. A note indicates *IP-S* - Internal to IoT-App.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +The diagram illustrates the functional model for stand-alone IoT Applications. It consists of three main entities: UE (User Equipment), 3GPP network system, and IoT-App. The UE is divided into two layers: VAL (top) and SEAL (bottom). The VAL layer contains 'IoT-App VAL client(s)'. The SEAL layer contains 'IoT-App and SEAL client(s)'. The IoT-App is also divided into two layers: VAL (top) and SEAL (bottom). The VAL layer contains 'IoT-App VAL server(s)'. The SEAL layer contains 'IoT-App SEAL server(s)'. Reference points are indicated: VAL-UU between the UE and the 3GPP network system; IP-UU between the UE and the 3GPP network system; IP-C between the VAL client(s) and the SEAL client(s) within the UE; IP-S\* between the VAL server(s) and the SEAL server(s) within the IoT-App. A dashed line separates the VAL and SEAL layers. A note at the bottom right indicates that \*IP-S\* is internal to the IoT-App. + +Figure 5.3.2-2: Functional model for stand-alone IoT Applications (without IoT-PCS services). The diagram shows three main components: UE, 3GPP network system, and IoT-App. The UE contains 'IoT-App VAL client(s)' and 'IoT-App and SEAL client(s)'. The IoT-App contains 'IoT-App VAL server(s)' and 'IoT-App SEAL server(s)'. Reference points are labeled: VAL-UU between UE and 3GPP network system; IP-UU between UE and 3GPP network system; IP-C between UE's client components; IP-S\* between IoT-App's server components. A dashed line separates the VAL and SEAL layers. A note indicates \*IP-S\* - Internal to IoT-App. + +**Figure 5.3.2-2: Functional model for stand-alone IoT Applications (without IoT-PCS services)** + +For stand-alone IoT applications, the IoT-App client communicates with the IoT-App server over the IP-UU reference point, which is an instance of the SEAL-UU generic reference point. The IoT-App client provides application-specific services to the IoT-App client(s) over IP- C reference point, which is an instance of the SEAL-C reference point. The VAL IoT-App server(s) communicate with the IoT-App SEAL server over the IP-S reference point, which is an instance of the SEAL-S generic reference point. + +The IoT-App server communicates with the SCEF via T8 reference point and with the NEF via N33 reference point. + +When an IoT Application designed based on a stand-alone model, is deployed in conjunction with an IoT platform, inter-service communication is required between the two SEAL servers. Figure 5.3.2-3 illustrates the functional model for inter-service communications between an IoT-PCS SEAL Server and an IoT-App SEAL Server. + +![Diagram of inter-service communication between IoT-App and IoT-PCS SEAL servers. The IoT-App is divided into VAL and SEAL layers. The SEAL layer contains an IP-S and an IoT App SEAL server. The IoT App SEAL server connects to an external IoT-PCS SEAL server via the SEAL-X3 reference point.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram shows an IoT-App block divided into two layers by a dashed line: VAL (top) and SEAL (bottom). The VAL layer contains an 'IoT-App VAL server'. The SEAL layer contains an 'IP-S' and an 'IoT App SEAL server'. A solid line labeled 'SEAL-X3' connects the 'IoT App SEAL server' to an external 'IoT-PCS SEAL server' block. + +Diagram of inter-service communication between IoT-App and IoT-PCS SEAL servers. The IoT-App is divided into VAL and SEAL layers. The SEAL layer contains an IP-S and an IoT App SEAL server. The IoT App SEAL server connects to an external IoT-PCS SEAL server via the SEAL-X3 reference point. + +**Figure 5.3.2-3: Inter-service communication between IoT-App and IoT-PCS SEAL servers** + +For inter-service communications, an IoT-App SEAL Server communicates with the IoT-PCS server over the SEAL-X3 reference point. In this deployment, both SEAL servers provide network exposure access, resulting in a distributed network exposure access deployment. Figure 5.3.2-4 depicts the resulting deployment. Note that this deployment aligns with the distributed network exposure access model introduced by the solution in clause 5.2, while using the proposed IoT-PCS-specific instances of SEAL reference points. + +![Functional model for IoT-PCS showing distributed network exposure access. It includes UE, 3GPP network system, and IoT-App components with various interfaces like VAL-UU, IP-UU, IP-C, IP-S, and SEAL-X3.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +This functional model diagram shows three main components: UE, 3GPP network system, and IoT-App. The UE contains 'IoT-App VAL client(s)' in the VAL layer and 'IoT-App and IoT-PCS SEAL client(s)' in the SEAL layer. The IoT-App contains 'IoT-App VAL server(s)' in the VAL layer and 'IoT-App SEAL server(s)' in the SEAL layer. The 3GPP network system includes 'Network interfaces' and 'IoT-PCS SEAL server(s)'. Interfaces shown include VAL-UU, IP-UU, IP-C, IP-S, and SEAL-X3. A note at the bottom right indicates '\*IP-S\* - Internal to IoT-App'. + +Functional model for IoT-PCS showing distributed network exposure access. It includes UE, 3GPP network system, and IoT-App components with various interfaces like VAL-UU, IP-UU, IP-C, IP-S, and SEAL-X3. + +**Figure 5.3.2-4: Functional model for IoT-PCS (distributed network exposure access)** + +## 5.4 Solution #4: Device triggering + +### 5.4.1 General + +An IoT-PCS Server may initiate a device trigger to a UE to cause it to establish a connection to the IoT-PCS Server, to connect to another server on the platform, to provide updated information, etc. The IoT-PCS Server may initiate the device trigger itself (implicit) or it may be initiated by a request that the IoT-PCS Server receives from IoT-App VAL Servers (explicit). + +### 5.4.2 Procedures and information flows + +#### 5.4.2.1 Procedure + +![Sequence diagram of the Device Triggering Procedure. The diagram shows four lifelines: IoT-PCS Client, 3GPP Network, IoT-PCS Server, and IoT-App VAL Server. The sequence of messages is: 1. An optional request from the IoT-App VAL Server to the IoT-PCS Server. 2. The IoT-PCS Server determines to initiate device triggering. 3. The IoT-PCS Server initiates the TS 23.682 Device Triggering procedure with the 3GPP Network. 4. An optional response from the IoT-PCS Server to the IoT-App VAL Server.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +sequenceDiagram + participant IoT-App VAL Server + participant IoT-PCS Server + participant 3GPP Network + participant IoT-PCS Client + + Note right of IoT-App VAL Server: 1.(optional) IoT-App request + IoT-App VAL Server-->>IoT-PCS Server: 1.(optional) IoT-App request + Note right of IoT-PCS Server: 2. IoT-PCS determines to initiate device triggering + IoT-PCS Server->>3GPP Network: 3. TS 23.682 Device Triggering procedure + Note right of IoT-PCS Server: 4. (optional) IoT-App response + IoT-PCS Server-->>IoT-App VAL Server: 4. (optional) IoT-App response + +``` + +Sequence diagram of the Device Triggering Procedure. The diagram shows four lifelines: IoT-PCS Client, 3GPP Network, IoT-PCS Server, and IoT-App VAL Server. The sequence of messages is: 1. An optional request from the IoT-App VAL Server to the IoT-PCS Server. 2. The IoT-PCS Server determines to initiate device triggering. 3. The IoT-PCS Server initiates the TS 23.682 Device Triggering procedure with the 3GPP Network. 4. An optional response from the IoT-PCS Server to the IoT-App VAL Server. + +Figure 5.4.2.1-1: Device Triggering Procedure + +- 1). The device triggering procedure may be initiated based on an optional interaction between the IoT-PCS Server and an IoT-App VAL Server. For example, the IoT-App VAL Server may send an explicit API request, or the IoT-App VAL Server may send another message based on which the IoT-PCS determines to start the device triggering procedure. +- 2). The IoT-PCS Server determines to initiate the device triggering. The IoT-PCS Server may use UE Availability and/or pre-configured information to determine the timing of the Device Triggering request, e.g. the trigger may be sent to ensure that a target UE in PSM mode is reachable when resuming communications. +- 3). The IoT-PCS Server performs the device triggering procedure described in 3GPP TS 23.682 [7] clause 5.2. The procedure requires that the UE Identifier, port number(s) and protocol information are available at the IoT-PCS Server. + +NOTE: It is to be addressed in the normative phase how the port number(s) and protocol information are being made available to the IoT-PCS Server + +As part of the procedure, the IoT-PCS Server receives a Device Triggering delivery status report from SCEF/NEF indicating the success of the delivery. + +- 4). If a request was received in step 1, the IoT-PCS Server responds to the request. + +Based on the trigger purpose derived from the payload, the targeted IoT-PCS Client or IoT-App Client performs the corresponding actions (e.g., connect to the IoT-App VAL Server). + +### 5.4.3 Evaluation + +This solution addresses Key Issue #6, enabling the IoT-PCS to provide device triggering support on behalf of the IoT Applications. + +## 5.5 Solution #5: Application Server status monitoring via CAPIF + +### 5.5.1 Description + +This solution addresses KI#2 by providing enhanced CAPIF services for managing application server (AS) status. The CAPIF core function (CCF) takes the responsibility to monitor AS service status. The CCF may expose the monitored AS service status to CCF service consumers (e.g. API invoker) via enhanced service discovery and event exposure procedures. + +NOTE: One AS can provide one or more AS services. + +#### 5.5.1.1 AS service status monitoring + +When a 3rd party Application Server provides its service (also see KI#2 and sol#8 in 3GPP TR 23.700-98 [9]), it acts as Application Exposure Function (AEF) in CAPIF. + +The application services provided by the AS can be published in the CCF so that the services are discoverable by the API invoker. When an AS acting as an AEF publishes its service API to the CCF, the AS updates its service API status (active, inactive) at the CCF. Table 5.5.1.1-1 shows the impact (with **bold** text) on the existing service API publish information flows in 3GPP TS 23.222 [8] as example, the same addition applies for the service API update request (e.g. to update service API status) and interconnection service API publish request. + +**Table 5.5.1.1-1: Service API publish request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API publisher information | M | The information of the API publisher may include identity, authentication and authorization information | +| Service API information | M | The service API information includes the service API name, service API type, service API status (e.g. active, inactive) , communication type, description, Serving Area Information (optional), AEF location (optional), interface details (e.g. IP address, port number, URI), protocols, version numbers, and data format. | +| Shareable information | O (see NOTE) | Indicates whether the service API or the service API category can be published to other CCFs. And if sharing, a list of CAPIF provider domain information where the service API or the service API category can be published is contained. | +| NOTE: If the shareable information is not present, the service API is not allowed to be shared. | | | + +For service API discovery, the CCF consumer (e.g. API invoker) can discover the service API status via service API discovery procedure or be notified about the service API status change via CAPIF event exposure procedure. The Application publishing function (APF) can update the service API status to the CCF. + +The service status exposed by CCF is supported by "Availability of service APIs" event in clause 8.8.6 of 3GPP TS 23.222 [8]. + +### 5.5.2 Evaluation + +This solution provides monitoring of service API status monitoring for the AS using CAPIF, which addresses KI#2. The control of application traffic towards the AS is up to the consumer of the AS service API to decide after AS service API discovery. + +## 5.6 Solution #6: BDT configuration + +### 5.6.1 General + +For an IoT Platform, the use of Background Data Transfer (BDT) allows IoT-App VAL Servers to use transmission time windows that are/cost and/or throughput favorable. The network provider is also enabled to provide better network resource management for predictable usage of downlink data. + +### 5.6.2 Procedures and information flows + +#### 5.6.2.1 General + +The Background Data Transfer feature requires an initial step in which policies are requested and negotiated. BDT Policy requests to the 3GPP network are based on an expected time window and UE set, with additional optional information e.g., expected data volume per UE. The UE set may be indicated as an expected number of UEs, a group ID or geographical area. + +The feature allows for the server involved to negotiate the policies proposed by the network. It also allows the server to enable notifications to be sent, should network conditions affect future BDT policies. + +Based on the BDT policies obtained using the procedures detailed in this clause, an IoT-App VAL server can initiate a data transfer to the client at the negotiated time and with the negotiated charging rates. The data transfer between the IoT-App VAL Server and the IoT-App VAL Client is performed without IoT-PCS Server enablement, but the IoT-App VAL Server may utilize functionality exposed by SEALDD or 5GMSG Servers. Service layer functionality for the purpose of facilitating the data transfer with the negotiated policy is not in scope of this specification. + +#### 5.6.2.2 Request and Select Background Data Transfer Policy + +Figure 5.6.2.2-1 depicts a general procedure for the request and configuration of traffic policies for BDT initiated by a request from an IoT-App VAL Server. + +![Sequence diagram showing the general procedure for configuration of Background Data Transfer. The diagram involves three main entities: 3GPP Network, IoT-PCS Server, and IoT-App VAL Server. The procedure consists of three steps: 1. Request background data transfer configuration from IoT-App VAL Server to IoT-PCS Server; 2. TS 29.522 Resource management of background data transfer procedure (shown as a block between 3GPP Network and IoT-PCS Server); 3. Response to background data transfer configuration from IoT-PCS Server to IoT-App VAL Server.](0fa26005ab105a07af4fda20b2554987_img.jpg) + +``` +sequenceDiagram + participant IoT-App VAL Server + participant IoT-PCS Server + participant 3GPP Network + Note left of 3GPP Network: 2. TS 29.522 Resource management of background data transfer procedure + IoT-App VAL Server->>IoT-PCS Server: 1. Request background data transfer configuration + IoT-PCS Server->>IoT-App VAL Server: 3. Response to background data transfer configuration +``` + +Sequence diagram showing the general procedure for configuration of Background Data Transfer. The diagram involves three main entities: 3GPP Network, IoT-PCS Server, and IoT-App VAL Server. The procedure consists of three steps: 1. Request background data transfer configuration from IoT-App VAL Server to IoT-PCS Server; 2. TS 29.522 Resource management of background data transfer procedure (shown as a block between 3GPP Network and IoT-PCS Server); 3. Response to background data transfer configuration from IoT-PCS Server to IoT-App VAL Server. + +Figure 5.6.2.2-1: General Procedure for configuration of Background Data Transfer + +**Step 1:** An IoT-App VAL Server requests IoT-PCS Server to negotiate with the 3GPP network a background data transfer policy. + +The request includes expected data volume, expected number of UEs, expected time window for the background data transfer. The request may also include group ID, geographic information for the UEs, a request expiration time, guidance for policy selection. If guidance for policy selection is not included, the IoT-App VAL Server indicates if IoT-PCS Server may choose independently from among multiple transfer policies. + +**Step 2:** Based on the request expiration time and Service Provider policies, IoT-PCS Server may determine to delay interactions with the 3GPP network in order to negotiate on behalf of multiple IoT-App VAL Servers. + +The IoT-PCS Server performs the resource management of background data transfer procedure described in 3GPP TS 23.502 [2] clause 4.16.7.2. The procedure requires that expected data volume, expected number of UEs, and expected time window are provided by the IoT-PCS Server. If the IoT-PCS Server determined to negotiate on behalf of multiple IoT-App VAL Servers, the parameters included reflects a superset of the individual IoT-App VAL Server requests. + +**NOTE 1:** The IoT-PCS Server determines to negotiate on behalf of multiple IoT-App VAL Servers based on implementation options and local policies. For example, if the request expiration time and expected time window are sufficiently large and, respectively, far away in time, the IoT-PCS Server may be allowed to delay the negotiations with the 3GPP network in case another request is received, targeting the same group of UEs. If another request is received with expected time windows sufficiently close and if the guidance for policy selection allows, a single policy/time window may be negotiated instead. This allows the UE group to wake up only once for multiple background data transfers. + +The 3GPP network determines one or more applicable transfer policies based on the requesting Background Data Transfer parameters. A list of transfer policies is provided to the IoT-PCS Server. Each transfer policy includes mandatory Reference ID, charging rating group reference and allocated time window and optional maximum UL and DL bandwidth. The IoT-PCS Server uses ASP policies and the transfer selection guidance (if available) to select a policy. The IoT-PCS Server informs the 3GPP Network of the selected transfer policy. + +**NOTE 2:** Based on 3GPP TS 23.503[3] clause 6.1.2.4. it is assumed that the IoT-PCS server is configured to understand the charging rating group reference based on agreements with the operator. + +**NOTE 3:** Policy selection guidance options such as "lowest cost", "highest throughput", etc. are to be determined in the normative phase. + +**NOTE 4:** The IoT-PCS server sets the warning notification based on local policies. + +**Step 3:** The IoT-PCS Server responds to the IoT-App VAL Server, providing the Reference ID and allocated time window of the background data transfer policy. + +#### 5.6.2.3 Reselect Background Data Transfer Policy + +Figure 5.6.2.3-1 depicts a general procedure for reselecting BDT policies after BDT warning. + +![Sequence diagram showing the general procedure for reselecting BDT policies after warning. The diagram involves three lifelines: 3GPP Network, IoT-PCS Server, and IoT-App VAL Server. Step 1: 3GPP Network sends a 'BDT Policy negotiate notify' to the IoT-PCS Server. Step 2: A box labeled 'TS 23.502 procedure for BDT warning notification (steps 11-16)' is shown between the 3GPP Network and IoT-PCS Server. Step 3: The IoT-PCS Server sends a 'Response to background data transfer configuration' to the IoT-App VAL Server.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant 3GPP Network + participant IoT-PCS Server + participant IoT-App VAL Server + Note left of IoT-PCS Server: 2. TS 23.502 procedure for BDT warning notification (steps 11-16) + 3GPP Network->>IoT-PCS Server: 1. BDT Policy negotiate notify + IoT-PCS Server->>IoT-App VAL Server: 3. Response to background data transfer configuration + +``` + +Sequence diagram showing the general procedure for reselecting BDT policies after warning. The diagram involves three lifelines: 3GPP Network, IoT-PCS Server, and IoT-App VAL Server. Step 1: 3GPP Network sends a 'BDT Policy negotiate notify' to the IoT-PCS Server. Step 2: A box labeled 'TS 23.502 procedure for BDT warning notification (steps 11-16)' is shown between the 3GPP Network and IoT-PCS Server. Step 3: The IoT-PCS Server sends a 'Response to background data transfer configuration' to the IoT-App VAL Server. + +**Figure 5.6.2.3-1: General Procedure for reselecting BDT policies after warning** + +**Step 1:** The 3GPP Network, via NEF, sends the BDT warning (BDT Policy negotiate) notification to the IoT-PCS server. The notification includes the affected BDT policy Reference ID and list of candidate BDT policies. + +Each of the BDT policies in the candidate BDT list includes mandatory Reference ID, charging rating group reference and time window, as well as optional maximum UL and DL bandwidth. + +**Step 2:** The IoT-PCS Server checks the new BDT policies included in the candidate list of the BDT warning notification. The IoT-PCS Server determines whether the notification affects multiple IoT-App VAL Servers or not. The IoT-PCS Server uses ASP policies and the transfer selection guidance (if available) provided with the initial IoT-App VAL Server request to select a policy. + +The IoT-PCS Server informs the 3GPP Network of the selected transfer policy or that no new policy has been selected by using steps 11-16 of the procedure for BDT warning notification in 3GPP TS 23.502[2] clause 4.16.7.3. + +**Step 3:** The IoT-PCS Server ends a new response to the IoT-App VAL Server, providing information about the new policy, or that no policy is available. If a new BDT policy is available, the information provided to the IoT-App VAL Server includes the ID of the applicable policy and the time window. + +### 5.6.3 Evaluation + +This solution addresses Key Issue #1. The solution allows the IoT-PCS to aggregate requirements/ requests from multiple IoT-App Servers and to select a set of BDT policies after negotiation with the Core Network, based on all IoT-App Server inputs. The solution also enables the IoT-PCS to determine the reference to the charging rate (based on agreement with the operator) without exposure of this information to the IoT Servers. At the same time, the solution does not affect the ability of IoT-App VAL/SEAL Servers to directly interact with 5GS for BDT negotiation, if so configured. + +The solution addresses only BDT policy negotiation, with the data transfer being performed without IoT-PCS Server enablement. IoT-App VAL Servers may utilize functionality exposed by SEALDD or 5GMSG Servers for facilitating the data transfer. + +The interactions with the Core Network are fully specified and require no changes. The request and response for BDT configuration exchanged between the IoT-App VAL Server and IOT-PCS server (i.e., steps 1 and 3 in 5.6.2.2) require specification. Therefore, this is a viable solution. + +## 5.7 Solution #7: UE unified traffic pattern and monitoring management + +### 5.7.1 General + +### 5.7.2 Procedures and information flows + +#### 5.7.2.1 General + +UE unified traffic pattern and monitoring management procedures allow IoT-PCS to offer services leveraging several CN exposure APIs: communication patterns configuration, network parameter values configuration and UE monitoring event management. + +#### 5.7.2.2 UE unified traffic pattern and monitoring management subscription procedure + +An IoT-App VAL or SEAL server can indicate to the IoT-PCS server its interest in receiving UE unified traffic patterns and monitoring management services by sending the UE unified traffic pattern and monitoring management subscription request. + +The subscription requests from each IoT-App VAL or SEAL server also include the traffic pattern configuration of the requester, which refers to application-level patterns of data traffic. The IoT-PCS server aggregates the traffic patterns obtained from the requestors (and described in Table 5.7.2.5.1-2) to determine the UE unified traffic patterns per UE. The UE unified traffic patterns are described via Table 5.7.2.5.3-1 for the UE unified traffic pattern update notification. These aggregated traffic patterns per UE (termed UE unified traffic pattern) are updated/adjusted by the IoT-PCS Server based on information obtain from UE monitoring. + +![Sequence diagram of the UE unified traffic pattern and monitoring management subscription procedure.](82b40cb8b2a5ac361973859400fa128a_img.jpg) + +``` +sequenceDiagram + participant IoT-App VAL Server/ IoT-App SEAL Server + participant IoT-PCS Server + Note right of IoT-PCS Server: 3. Aggregates requests and parameters per UE, establishes the UE unified traffic pattern (per UE) + Note right of IoT-PCS Server: 4. (conditional) Management and 5GC exposure procedures (see clause 5.7.3) + IoT-App VAL Server/ IoT-App SEAL Server->>IoT-PCS Server: 1. UE unified traffic pattern and monitoring management subscription request + IoT-PCS Server-->>IoT-App VAL Server/ IoT-App SEAL Server: 2. UE unified traffic pattern and monitoring management subscription response +``` + +The diagram illustrates the subscription procedure between an IoT-App VAL Server/ IoT-App SEAL Server and an IoT-PCS Server. The sequence of messages is as follows: + +- The IoT-App VAL Server/ IoT-App SEAL Server sends a "1. UE unified traffic pattern and monitoring management subscription request" to the IoT-PCS Server. +- The IoT-PCS Server responds with a "2. UE unified traffic pattern and monitoring management subscription response". +- On the IoT-PCS Server side, a box indicates "3. Aggregates requests and parameters per UE, establishes the UE unified traffic pattern (per UE)". +- Below that, another box indicates "4. (conditional) Management and 5GC exposure procedures (see clause 5.7.3)". + +Sequence diagram of the UE unified traffic pattern and monitoring management subscription procedure. + +Figure 5.7.2.2-1: UE unified traffic pattern and monitoring management subscription procedure + +1. In order to subscribe to the IoT-PCS Server services, the IoT-App VAL/ SEAL server sends the UE unified traffic pattern and monitoring management request, as detailed in clause 5.7.2.5. The subscription request may include IoT-App traffic pattern configuration, which provides the traffic patterns of the specific IoT-App VAL/SEAL Server. The request may also include Management subscription indications which indicate to the IoT PCS server which management and 5GC exposure procedures the IoT-App VAL/SEAL server allows the IoT-PCS Server to perform on its behalf. +2. Upon receipt of the request, the IoT-PCS server sends a UE unified traffic pattern and monitoring management subscription response. +3. The IoT-PCS Server aggregates UE unified traffic pattern and monitoring management subscription requests from different IoT-App VAL/SEAL servers and determines the UE unified traffic pattern per UE (using the traffic patterns of all the IoT-Apps communicating with the UE). If the IoT-PCS Server determines that additional or updated IoT-App traffic pattern configurations are needed, it requests them from the IoT-App Servers using the Traffic pattern configuration request procedure in clause 5.7.4. +4. Depending on the subscription requests received and local policies, the IoT-PCS Server executes one or more management and 5GC exposure procedure (per UE). Management and 5GC exposure procedures are detailed in clause 5.7.3. + +The IoT-PCS Server determines the management procedures required to be executed on behalf of the IoT-App VAL/SEAL Servers .based on the received management subscription indications as follows: + +- If the CP configuration indication is provided, the IoT-PCS executes the CP configuration procedure detailed in clause 5.7.3.2. +- If the UE unified traffic pattern monitoring management indication is provided, the IoT-PCS Server executes steps 1-3 of the UE unified traffic pattern monitoring procedure detailed in clause 5.7.3.3. +- If the UE unified traffic pattern monitoring update notification indication is provided, the IoT-PCS Server executes the steps 1-4 of the UE unified traffic pattern monitoring procedure detailed in clause 5.7.3.3. +- If the Network parameter coordination indication is provided, the IoT-PCS executes the network parameter coordination procedure detailed in clause 5.7.3.4. + +NOTE 1: The IoT-PCS Server translates the management subscription indications received from different IoT-App VAL/SEAL Servers into per-UE management indications based on local policies and configurations. For example, an IoT-PCS Server may be configured to execute a management procedure for a UE if at least one IoT-App VAL/SEAL Server indicates it. Another IoT-PCS Server may be configured to provide all the management procedures for the UEs using the platform independent of IoT-App Server subscription indications. + +NOTE 2: Corresponding subscription update request and unsubscribe request procedures will complement this functionality in the normative phase. These would allow the update of the subscription request parameters and the deletion of the entire subscription, respectively. + +#### 5.7.2.3 UE unified traffic pattern update notification procedure + +An IoT-PCS Server can provide updated UE unified traffic pattern information to IoT-App VAL or SEAL servers by sending UE unified traffic pattern update notifications as shown in figure 5.7.2.3-1. The UE unified traffic pattern management procedure detailed in clause 5.7.3.3. is an example of procedure which may result in UE unified traffic pattern updates at the IoT-PCS server, based on which UE unified traffic pattern update notifications are provided. + +Pre-conditions: + +- 1) The IoT-App Val/SEAL server has subscribed for UE unified traffic pattern and monitoring management services, requesting to receive UE unified traffic pattern update notifications + +![Sequence diagram for UE unified traffic pattern update notification procedure](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` +sequenceDiagram + participant IoT-PCS Server + participant IoT-App VAL Server/ IoT-App SEAL Server + Note left of IoT-App VAL Server: IoT-App VAL Server/ +IoT-App SEAL Server + Note right of IoT-PCS Server: IoT-PCS Server + IoT-PCS Server->>IoT-App VAL Server: 1. UE unified traffic pattern update notification +``` + +The diagram shows a sequence of messages between two entities: 'IoT-App VAL Server/ IoT-App SEAL Server' on the left and 'IoT-PCS Server' on the right. A single message arrow labeled '1. UE unified traffic pattern update notification' points from the IoT-PCS Server to the IoT-App VAL Server/ IoT-App SEAL Server. + +Sequence diagram for UE unified traffic pattern update notification procedure + +**Figure 5.7.2.3-1: UE unified traffic pattern update notification procedure** + +1. The IoT-PCS server sends the UE unified traffic pattern update notification when either of the following occurs: + - Monitoring events lead to updates in the UE unified traffic pattern (e.g., to schedule elements in Table 5.7.2.5.3-1) the IoT-PCS server sends a corresponding notification to the IoT-App VAL/SEAL server. Other notifications may be provided, e.g., if the stationary indication changes. + - An NP Configuration Notification is received with a new set of applied network parameters and if the IoT-PCS Server determines that the new configuration is incompatible with the current UE unified traffic pattern (see also clause 5.7.3.3 step 3). + +#### 5.7.2.4 Traffic pattern configuration request procedure + +To obtain information about service-specific traffic patterns for a UE, the IoT-PCS server can request traffic pattern configuration from the IoT-App VAL/SEAL server. This procedure may be used for example to request traffic patterns from IoT-App Servers which did not initiate UE unified traffic pattern and monitoring management, but which nevertheless communicate with the UE. + +![Sequence diagram for Traffic pattern configuration request](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` +sequenceDiagram + participant IoT-PCS Server + participant IoT-App VAL Server/ IoT-App SEAL Server + Note left of IoT-App VAL Server: IoT-App VAL Server/ +IoT-App SEAL Server + Note right of IoT-PCS Server: IoT-PCS Server + IoT-PCS Server->>IoT-App VAL Server: 1. Traffic pattern configuration request + IoT-App VAL Server-->>IoT-PCS Server: 2. Traffic pattern configuration response +``` + +The diagram shows a sequence of messages between two entities: 'IoT-App VAL Server/ IoT-App SEAL Server' on the left and 'IoT-PCS Server' on the right. Two message arrows are shown: '1. Traffic pattern configuration request' pointing from the IoT-PCS Server to the IoT-App VAL Server/ IoT-App SEAL Server, and '2. Traffic pattern configuration response' pointing from the IoT-App VAL Server/ IoT-App SEAL Server back to the IoT-PCS Server. + +Sequence diagram for Traffic pattern configuration request + +**Figure 5.7.2.4-1: Traffic pattern configuration request** + +1. In order to obtain the service-specific traffic pattern configuration for a UE, the IoT-PCS Server sends traffic pattern configuration request to the IoT-App VAL/ SEAL server. The request parameters indicate the UE(s) for which the request is made. +2. Upon receipt of the request, the IoT-App VAL/SEAL server sends a response. The parameters include one or more traffic pattern elements. + +#### 5.7.2.5 Information Flows + +##### 5.7.2.5.1 UE unified traffic pattern and monitoring management subscription request + +Table 5.7.2.5.1-1 describes the information flow for the UE unified traffic pattern and monitoring management subscription request from the IoT-App VAL/SEAL server to the IoT-PCS server. + +**Table 5.7.2.5.1-1: UE unified traffic pattern and monitoring management subscription request** + +| Information element | Monitoring | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------------------------------------| +| IoT-App VAL UE ID | M | UEs hosting IoT-App clients for which the subscription is requested | +| IoT-App VAL service ID | M | Identity of the VAL service for which the subscription is requested. | +| Management subscription indications | M | At least one of the following indications is to be provided | +| > CP configuration indication | O | Indicates whether CP configuration by the IoT-PCS Server with 5GC is requested. (see NOTE 1) | +| > UE unified traffic pattern monitoring management indication | O | Indicates that management of the UE unified traffic pattern is requested | +| > UE unified traffic pattern update notification indication | O | Indicates that notifications for updates of the UE unified traffic pattern monitoring is requested | +| > Network parameter coordination indication | O | Indicates whether network parameter coordination by the IoT-PCS with 5GC is requested (see NOTE 1) | +| IoT-App traffic pattern configuration | O | Traffic pattern configuration of the VAL service for this UE, as described in table 5.7.2.5.1-2. | +| NOTE 1: The CP configuration and the network parameter coordination functionality are also subject to policies available at the IoT-PCS Server. | | | + +**Table 5.7.2.5.1-2: IoT-App traffic pattern configuration** + +| Information element | Monitoring | Description | +|-----------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Schedule elements | O | List of schedule elements applicable to the traffic patterns of the VAL service for this UE. Each schedule element is composed from seven fields: second, minute, hour, day of month, month, day of week and year. Each element indicates times or durations when the service traffic occurs. Multiple schedule elements can be used to create complex scheduling. (see NOTE 3) | +| Expiration time | O | Identifies when the IoT-App traffic pattern parameter configuration expire. If absent, it indicates that there is no expiration time. | +| Stationary indication | O | Identifies whether the UE is expected to be stationary or mobile while communicating using this traffic pattern configuration | + +NOTE 3: The following is an example of a schedule element with the fields: second, minute, hour, day of month, month, day of week and year: + +\*; 0-30 ; 2; \*; Jan-Sept; Tues; \*. + +This schedule element, when used for IoT-App VAL traffic patterns translates to the following in the CpProvisioning API as described in 3GPP TS 29.122[10] clause 5.10: + +- periodicCommunicationIndicator: TRUE +- communicationDurationTime: 30 min +- periodicTime: 1 week + +- scheduledCommunicationTime: Tues, 2:00-2:30 +- validityTime: calculated using the Jan-Sept range and the provided expiration time. + +NOTE: The format of this IE is to be provided in stage 3. The purpose of this description is to clarify how the same element can contain multiple periodicities, specify start/stop times, etc. + +##### 5.7.2.5.2 UE unified traffic pattern and monitoring management subscription response + +Table 5.7.2.5.2-1 describes the information flow for the UE unified traffic pattern and monitoring management subscription response from the IoT-PCS server to the IoT-App VAL/SEAL server. + +**Table 5.7.2.5.2-1: UE unified traffic pattern and monitoring management subscription response** + +| Information element | Monitoring | Description | +|---------------------|------------|----------------------------------------------------------| +| Result | M | Indicates success or failure of the subscription request | + +##### 5.7.2.5.3 UE unified traffic pattern update notification + +Table 5.7.2.5.3-1 describes the information flow for the UE unified traffic pattern update notification from the IoT-PCS server to the IoT-App VAL/SEAL server. + +**Table 5.7.2.5.3-1: UE unified traffic pattern update notification** + +| Information element | Monitoring | Description | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE ID | M | UE for which the UE unified traffic pattern update notification is provided for. | +| Schedule elements | O | Schedule element applicable to the unified traffic patterns of the UE. A schedule element is composed from seven fields: second, minute, hour, day of month, month, day of week and year. Each element indicates times or durations of UE availability. | +| Stationary indication | O | Identifies whether the UE is expected to be stationary or mobile while communicating using this UE unified traffic pattern, as determined by the IoT-PCS Server | +| Cause | O | This element is mandatory when the notification is provided to inform of a parameter configuration applied by the network which is incompatible with the existing Traffic Patterns. (see NOTE)
The element is optional when the notification informs of UE unified traffic pattern updates, providing additional information on the reason for the UE unified traffic pattern update (e.g. monitoring events received) | +| NOTE: | For notifications of incompatible configurations, the normative phase can consider whether adding an optional element with a proposed IoT-PCS Server UE unified traffic pattern update is beneficial. | | + +##### 5.7.2.5.4 Traffic pattern configuration request + +Table 5.7.2.5.4-1 describes the information flow for the Traffic pattern configuration request from the IoT-PCS server to the IoT-App VAL/SEAL server. + +**Table 5.7.2.5.4-1: Traffic pattern configuration request** + +| Information element | Monitoring | Description | +|---------------------|------------|--------------------------------------------------------------| +| UE ID | M | UE for which the Traffic pattern configuration is requested. | + +##### 5.7.2.5.5 Traffic pattern configuration response + +Table 5.7.2.5.5-1 describes the information flow for the Traffic pattern configuration response from the IoT-App server to the IoT-PCS server. + +**Table 5.7.2.5.5-1: Traffic pattern configuration response** + +| Information element | Monitoring | Description | +|---------------------------------------|------------|--------------------------------------------------------------------------------------------------| +| UE ID | M | UE for which the Traffic pattern configuration is provided | +| IoT-App traffic pattern configuration | M | Traffic pattern configuration of the VAL service for this UE, as described in table 5.7.2.5.1-2. | + +### 5.7.3 Management and 5GC exposure procedures + +#### 5.7.3.1 General + +#### 5.7.3.2 CP configuration procedure + +The CP configuration procedure uses the information received by the IoT-PCS Server from the IoT-App regarding predictable communication behaviour of their services to provide information to 5GC for resource planning purposes, using an existing network exposure API. + +Pre-conditions: + +1. IoT-PCS Server determines to provide the service for a specific UE after receiving CP configuration indications in UE unified traffic pattern and monitoring management subscription requests, subject to policy. + +![Sequence diagram of the CP configuration procedure between 5GC and IoT-PCS Server.](0977b81510f7649846289ee785d20e74_img.jpg) + +``` + +sequenceDiagram + participant 5GC + participant IoT-PCS Server + Note right of IoT-PCS Server: 1. Determines CP from individual traffic pattern configurations + 5GC->>IoT-PCS Server: + Note over 5GC, IoT-PCS Server: 2. CP parameter provisioning (TS 29.122 clause 4.4.9) + IoT-PCS Server->>5GC: + +``` + +The diagram illustrates the CP configuration procedure. It shows two main entities: 5GC and IoT-PCS Server. The IoT-PCS Server first performs an internal step: '1. Determines CP from individual traffic pattern configurations'. Then, a message is sent from the 5GC to the IoT-PCS Server, labeled '2. CP parameter provisioning (TS 29.122 clause 4.4.9)'. Finally, a response is sent from the IoT-PCS Server back to the 5GC. + +Sequence diagram of the CP configuration procedure between 5GC and IoT-PCS Server. + +**Figure 5.7.2.2-1: CP configuration procedure** + +1. The IoT-PCS Server stores all Traffic pattern configurations received for the UE in subsequent UE unified traffic pattern and monitoring management subscription procedures and determines the UE unified traffic pattern. The IoT-PCS Server can also initiate Traffic pattern configuration requests to obtain additional configurations. The IoT-PCS Server uses the UE unified traffic pattern to determine a CpParameterSet, as defined in 3GPP TS 29.122[10], for the CpProvisioning API. +2. The IoT-PCS Server determines based on local policy when the CpProvisioning API is to be invoked and executes the CP parameter provisioning procedure described in 3GPP TS 29.122[10] clause 4.4.9. + +#### 5.7.3.3 UE unified traffic pattern management procedure + +The UE unified traffic pattern management procedure is used to determine and manage a unified traffic pattern applicable to a specified UE. The IoT-PCS Server then uses the 5GC exposure of UE monitoring events to update the UE unified traffic pattern. + +Pre-conditions: + +1. IoT-PCS Server determines to provide the service for a specific UE if either of the following conditions is true: + - a) It receives UE unified traffic pattern monitoring management indications in UE unified traffic pattern and monitoring management subscription requests; or + - b) It determines to provide Network parameter coordination services for the UE. + +![Sequence diagram showing the UE unified traffic pattern and monitoring management subscription procedure between 5GC and IoT-PCS Server.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +``` +sequenceDiagram + participant 5GC + participant IoT-PCS Server + Note right of IoT-PCS Server: 1. Determines an initial UE unified traffic pattern + Note over 5GC, IoT-PCS Server: 2. Set up UE monitoring + Note right of IoT-PCS Server: 3. Update UE unified traffic pattern based on UE monitoring event notifications + Note right of IoT-PCS Server: 4. (conditional) Notify subscribers of UE unified traffic pattern updates +``` + +The diagram illustrates the interaction between the 5GC and the IoT-PCS Server. The IoT-PCS Server initiates the process by determining an initial UE unified traffic pattern (Step 1). It then sets up UE monitoring (Step 2), which involves an interaction with the 5GC. Based on UE monitoring event notifications, the IoT-PCS Server updates the UE unified traffic pattern (Step 3). Finally, it conditionally notifies subscribers of UE unified traffic pattern updates (Step 4). + +Sequence diagram showing the UE unified traffic pattern and monitoring management subscription procedure between 5GC and IoT-PCS Server. + +**Figure 5.7.3.3-1: UE unified traffic pattern and monitoring management subscription procedure** + +The IoT-PCS Server determines an initial UE unified traffic pattern, e.g. by using all Traffic pattern configurations received for the UE . + +2. The IoT-PCS Server determines, based on local policy that UE monitoring events are to be configured and executes the corresponding Monitoring procedure as described in 3GPP TS 29.122 [10] clause 4.4.2. +3. The IoT-PCS Server updates the UE unified traffic pattern based on the received monitoring events as follows: + - If a Monitoring Notification report for UE\_REACHABILITY is received, and *idleStatusInfo* information is provided in the report, the IoT-PCS Server changes the schedule element of the UE unified traffic pattern such that the duration of activity is set to the value of the *activeTime* parameter configured in the *idleStatusInfo*. + +- If a Monitoring Notification report for AVAILABILITY\_AFTER\_DDN\_FAILURE is received after a UE transitions to idle mode, the IoT-PCS Server updates the schedule element of the UE unified traffic pattern such that: the start of an activity window is based on the Idle Timestamp, with a periodicity equal to the TAU/RAU Timer; the duration of the activity window indicates the Active Time value. + - If a Monitoring Notification report for COMMUNICATION\_FAILURE is received The IOT-PCS updates the schedule element of the UE unified traffic pattern to indicate that no communications are currently available (e.g. by using a keyword such as "NULL"). Local policies may specify events/ thresholds further defining when the IoT-PCS may provide a UE unified traffic pattern update based on monitoring events. For example, the update may be provided only after repeated communication failures are received within a timespan, or only if high reliability communications are expected. It is recommended that UE Reachability monitoring is also enabled in conjunction with the Communication Failure monitoring. This enables the IoT-PCS to provide updated timing information once the UE becomes reachable again. + - If a Monitoring Notification report for LOSS\_OF\_CONNECTIVITY is received, the IoT-PCS Server changes the schedule element of the UE unified traffic pattern to indicate that no communications are currently available +4. Conditional: The IoT-PCS Server notifies subscribers of the UE unified traffic pattern updates, as described in clause 5.7.2.3 + +#### 5.7.3.4 Network parameter coordination procedure + +The network parameter coordination procedure uses UE unified traffic pattern information to influence aspects of UE/network behaviour such as the UE's PSM and extended idle mode DRX. For this purpose, parameter values may be suggested for Maximum Latency and Maximum Response Time for a UE. 5GC may choose to accept, reject or modify the suggested configuration parameter value. + +Pre-conditions: + +1. IoT-PCS Server determines to provide the service for a specific UE after receiving Network parameter coordination indications in UE unified traffic pattern and monitoring management subscription requests, subject to policy. +2. IoT-PCS Server determines and manages UE unified traffic patterns as described in clause 5.7.3.3. + +![Sequence diagram of the network parameter coordination procedure between 5GC and IoT-PCS Server.](836b0790cef5469a167fa8931df4e408_img.jpg) + +``` +sequenceDiagram + participant 5GC + participant IoT-PCS Server + Note right of IoT-PCS Server: 1. Determines to provide network parameter configuration to 5GC + IoT-PCS Server->>5GC: 2. Network parameter configuration (3GPP TS 29.122 clause 4.4.12) +``` + +The diagram is a sequence diagram illustrating the network parameter coordination procedure. It features two lifelines: 5GC on the left and IoT-PCS Server on the right. The process begins with a self-call on the IoT-PCS Server lifeline, labeled '1. Determines to provide network parameter configuration to 5GC'. Following this, a message is sent from the IoT-PCS Server to the 5GC, labeled '2. Network parameter configuration (3GPP TS 29.122 clause 4.4.12)'. + +Sequence diagram of the network parameter coordination procedure between 5GC and IoT-PCS Server. + +**Figure 5.7.3.4-1: Network parameter coordination procedure** + +1. The IoT-PCS Server determines to provide Network parameter configuration to 5GC. This determination can be based on updates to the UE unified traffic patterns resulting from interactions with IoT-App Servers (e.g. Traffic pattern configuration updates), on local policies, etc. + +The IoT-PCS Server determines parameters the needed for NpConfiguration data structure as specified in 3GPP TS 29.122[10] from the UE unified traffic patterns as follows: + +- *maximumLatency* – This value tells the network how long the UE is allowed to sleep. Setting it to 0 will disable PSM, extended idle mode DRX, and extended buffering. The IoT-PCS can extract the periodicity derived from the UE unified traffic pattern, which includes the schedule elements for the UEs communications with all IoT-Apps. The IoT-PCS Server sets *Maximum Latency* to be approximately the periodicity of the active periods derived from the schedule element of the UE unified traffic pattern. + - *maximumResponseTime* – When the UE uses PSM, Maximum Response Time tells the network how long the UE should stay reachable after a transition to idle. When the UE uses eDRX, Maximum Response Time is used by the network to determine when to send a reachability notification before a UE's paging occasion. The IoT-PCS Server extracts a duration of activity from the schedule element of the UE unified traffic pattern and sets *Maximum Response Time* to reflect the duration of activity, indicating how long the UE should stay reachable for downlink communications. +2. The IoT-PCS Server performs the Network Parameter Configuration procedure as described in 3GPP TS 29.122[10] clause 4.4.12. + +NOTE: The values provided by IoT-PCS Server to 5GC in the Network parameter configuration procedure may or may not be accepted by the network. If they are not accepted, 5GC responds accordingly and the previous values apply, or new values are provided. The new values are used by IoT-PCS Server as described in clause 5.7.3.3, when they were provided via monitoring event notifications. + +### 5.7.3 Evaluation + +The solution addresses Key Issues #3 and #4. + +The solution captured in this clause except sub-clause 5.7.3.2 allows the IoT-PCS to aggregate scheduling information and monitoring requests from multiple IoT-App Servers. Aggregated monitoring in the application layer can greatly reduce the signalling burden on the exposure interfaces, i.e. T8/ N33, especially for MIoT. + +In addition, the solution enables IoT Platforms to integrate network-agnostic ASs (i.e. without SCEF/NEF APIs) and to provide them with UE monitoring and scheduling features. IoT-PCS Server is also used to use application-level scheduling to derive 5GC PSM configurations on behalf of multiple IoT-App servers. At the same time, this solution does not affect the ability of IoT-App VAL/SEAL Servers to directly interact with 5GS for UE monitoring. Therefore, the UE unified traffic pattern management features, provide a viable solution recommended for the normative phase. + +The UE unified traffic pattern management procedure can be considered in the normative phase as enhancement to NRM event monitoring (as an alternative to IoT-PCS functionality). The IoT-PCS server can aggregate network parameter configurations for its serviced IoT App servers. However, additional coordination from different IoT-PCS servers and other AFs (not served by IoT-PCS server) is done in the 3GPP CN. + +The procedure for CP configuration in clause 5.7.3.2 addresses KI #4. However, given the SCEF/NEF capabilities to deal with multiple CP configurations per UE, such a solution does not provide significant advantages, therefore it is not proposed to be considered for the normative phase. + +# --- 6 Overall Evaluation + +## 6.1 Architecture evaluation + +This clause provides an evaluation of the application architecture for enabling application capability exposure to general purpose servers or 3rd party IoT applications via IoT Platforms. + +A summary of the architecture and key issues specified in this technical report are listed in Table 6.1-1. The architecture enhancements proposed in clauses 5.1 and 5.3 describe the. + +**Table 6.1-1 Architecture evaluation** + +| Architecture solution | Applicable key issues (clause reference) | Dependency on other working groups | +|---------------------------------------------------------|------------------------------------------|------------------------------------| +| 5.3 IoT Platform functional model | Supports all key issues | None | +| 5.1 Functional model for application service management | Supports key issue 2 | None | + +## 6.2 Solution evaluations + +### 6.2.1 General + +All the key issues and solutions specified in this technical report are listed in Table 6.2.1-1. It includes the mapping of the key issues (clause 4) to the solutions and corresponding solution evaluations. It also lists the dependencies on other working groups that will need consideration during the Release 18 normative phase. + +**Table 6.2.1-1 Key issue and solutions** + +| Key issues (evaluation clause reference) | Solution | Solution (clause reference) | Dependency on other working groups | +|-----------------------------------------------------------------|---------------------------------------------------------------------------|-----------------------------|------------------------------------| +| #1: Background Data Transfer negotiation | #2: Provisioning of Edge Data Network configuration | 5.2 | None | +| #2: Application server monitoring and control of traffic | #1: Application Service Management Service | 5.1 | None | +| | #5: Application Server status monitoring via CAPIF | 5.5 | None | +| #3: Key issue #3: IoT Platform PSM monitoring and configuration | #7: UE unified traffic pattern and monitoring management (except 5.7.3.2) | 5.7 | SA2 | +| #4: Key issue #4: Configuration of Communication Patterns | #7: UE unified traffic pattern and monitoring management (clause 5.7.3.2) | 5.7 | N/A | +| #5 Key issue #5: NIDD configuration | none | N/A | N/A | +| #6 Key issue #6: Device Triggering services. | Solution #4: Device triggering | 5.4 | None | + +### 6.2.2 Key issue #2: Application server monitoring and control of traffic + +Solution #1 (Application Service Management Service) and solution #5 (Application Server status monitoring via CAPIF) addresses the key issue#2. + +Solution #1 proposes application service management using SEAL server. The solution proposes data collection procedures using request-response model and also subscribe-notify model. If required, the ASM server decides corrective action to take for VAL client or VAL server. + +NOTE: For solution#1, whether configuring VAL server procedure is required or not – will be considered in normative work. + +Solution #5 proposes to enhance CAPIF service to monitoring application server status. When an AS acting as an AEF publishes its service API to the CCF, the AS updates its service API status (active, inactive) at the CCF. The API invoker can discover the service API status via service API discovery procedure or be notified about the service API status change via CAPIF event exposure procedure. + +Both solutions can be considered as a base for normative work. + +# 7 Conclusions + +## 7.1 Solution conclusions + +This technical report completes the study on application architecture for enabling application capability exposure to general purpose servers or third party IoT applications via IoT Platforms, with the following considerations for normative work: + +1. Definition of terms and abbreviations captured in clause 3 will be reused as needed. +2. The application architecture enhancements for enabling application capability exposure to general purpose servers or 3rd party IoT applications via IoT Platforms are summarized in clause 6.1. +3. The IoT platform deployment options detailed in clause 5.2 will be analysed in the normative phase, to determine whether a new IoT PCS SEAL service is necessary. Applicable IoT-PCS -related procedures are to be implemented in the normative phase using existing SEAL services (e.g. NRM) whenever there is relevance to other verticals or enablers. +4. The following individual solutions, corresponding to the key issues, will be considered as candidate solutions: + - a. for Key issue #1 (Background Data Transfer negotiation): + - i. Solution #6 (BDT configuration) as NRM functionality. + - b. for Key issue #2 (Application server monitoring and control of traffic): + - i. Solution #1 (Application Service Management Service) as ASM SEAL functionality; and + - ii. Solution #5 (Application Server status monitoring via CAPIF) as new CAPIF functionality. + - c. for Key issue #3 (IoT Platform PSM monitoring and configuration) + - i. Solution #7 (UE unified traffic pattern and monitoring management) except clauses 5.7.3.2, 5.7.3.4, as NRM functionality. + - d. for Key issue #4 (Configuration of Communication Patterns): + - i. Clause 5.7.3.2 of Solution #7 (CP configuration procedure) addresses the key issue but does not provide enough enhancement over existing SCEF/NEF functionality. Therefore, no functionality is considered for normative phase. + - e. for Key issue #5 (NIDD configuration): + - i. No solutions introduced have been agreed, therefore no functionality is considered for normative phase. + +**Editor's Note: The conclusion for Key Issue #6 is FFS** + +# Annex A: Change history + +| Change history | | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | Tdoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2021-07 | SA6#44-e | S6-211702 | | | | TR Skeleton | | 0.0.0 | +| 2021-07 | SA6#44-e | | | | | S6-211703, S6-211857. Editorials: renamed TBD sub-clauses 4.1, 5.1 as 4.x, 5.x, deleted change history guidance table from skeleton. Modified Annex A title from skeleton to fix table of contents formatting. | | 0.1.0 | +| 2021-09 | SA6#45-e | | | | | S6-212113, S6-212121. Editorials: added one abbreviation, minor grammatical corrections | | 0.2.0 | +| 2021-10 | SA6#45-bis-e | | | | | S6-212372, S6-212373, S6-212476. Editorials: added several abbreviations, changed one to avoid ambiguity, miscellaneous grammatical corrections. | | 0.3.0 | +| 2021-11 | SA6#46-e | | | | | S6-212714, S6-212827 | | 0.4.0 | +| 2021-11 | SA6#46-e | | | | | Editorial correction history box | | 0.4.1 | +| 2022-03 | SA6#47-e | | | | | S6-220326, S6-220331, S6-220364, S6-220456. Editorials: corrected formatting for the new text; added 3GPP TS 23.682 reference; added "3GPP" to existing references for consistency. | | 0.5.0 | +| 2022-05 | SA6#48-e | | | | | S6-220879, S6- 220948, Editorials: corrected a plural to singular in new text for 5.1.4.2, corrected 5.5.1.1.clause number, corrected reference to Table 5.5.1.1-1, applied formats as needed | | 0.6.0 | +| 2022-06 | SA6#49-e | | | | | S6-221307, S6- 221394, S6-221395. Editorials: Corrected number for Figure 5.6.2.3-1, deleted a repeated "3GPP" in step 1 of 5.6.2.2, added a reference, removed double blanks between words. | | 0.7.0 | +| 2022-07 | SA6#49-bis-e | | | | | S6-221968. Editorials: Formatting, corrected meeting numbers in Annex B. | | 0.8.0 | +| 2022-09 | SA6#50-e | | | | | S6-222090, S6-222474, S6-222597, S6-222607. Editorials: Formatting, added reference [10] in clause 2 and text, corrected numbering for figures 5.7.3.3-1 and 5.7.3.4-1, changed KI #2 evaluation from being clause 6.2 to being clause 6.2.2 | | 0.9.0 | +| 2022-09 | SA#97-e | SP-220946 | | | | Presentation for information at SA#97-e | | 1.0.0 | +| 2022-10 | SA6#51-e | | | | | S6-222974, S6-222975. Deleted old figures 5.7.2.2-1 and 5.7.3.4-1 as S6-222975 replaced them without deletion of the old. | | 1.1.0 | +| 2023-03 | SA6#53 | | | | | S6-230851 | | 1.2.0 | +| 2023-03 | SA#99 | SP-230274 | | | | Presentation for approval at SA#99 | | 2.0.0 | +| 2023-03 | SA#99 | SP-230274 | | | | MCC Editorial update for publication after TSG SA approval (SA#99) | | 18.0.0 | +| 2023-06 | SA#100 | SP-230705 | 0002 | 2 | D | TR 23.700-97 Conclusion update and clean-up | | 18.1.0 | +| 2023-06 | SA#100 | SP-230705 | 0003 | | D | TR 23.700-97 General clean-up | | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-98/raw.md b/raw/rel-18/23_series/23700-98/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a1111892aea739a947e2de33c0b682e97c3b4dbe --- /dev/null +++ b/raw/rel-18/23_series/23700-98/raw.md @@ -0,0 +1,9069 @@ +# 3GPP TR 23.700-98 V18.1.0 (2023-03) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced Architecture for enabling Edge Applications; (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, stylized font with a red signal wave icon below the 'P', and the text 'A GLOBAL INITIATIVE' underneath. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| TOC \o "1-9" Foreword..... | 13 | +| Introduction ..... | 14 | +| 1 Scope..... | 15 | +| 2 References..... | 15 | +| 3 Definitions of terms, symbols and abbreviations ..... | 16 | +| 3.1 Terms..... | 16 | +| 3.2 Symbols..... | 16 | +| 3.3 Abbreviations ..... | 16 | +| 4 Key issues ..... | 17 | +| 4.1 Key issue #1: Enhanced notification service to the EEC ..... | 17 | +| 4.2 Key issue #2: Enablement of Service APIs exposed by EAS ..... | 18 | +| 4.3 Key issue #3: Enhancements to service continuity planning ..... | 18 | +| 4.4 Key issue #4: EDGE-5 ..... | 19 | +| 4.5 Key issue #5: Alignment of EDGEAPP and ETSI MEC ..... | 20 | +| 4.6 Key issue #6: Edge services support across ECSPs..... | 20 | +| 4.7 Key issue #7: Application traffic filter exposure ..... | 21 | +| 4.8 Key issue #8: EAS selection synchronization..... | 22 | +| 4.9 Key issue #9: Enhancement of dynamic EAS instantiation triggering ..... | 23 | +| 4.10 Key issue #10: Support for roaming UEs..... | 23 | +| 4.11 Key issue #11: ACR between EAS and Cloud Application Server ..... | 24 | +| 4.12 Key issue #12: EEL service differentiation..... | 24 | +| 4.13 Key issue #13: Edge enabler layer support for EAS synchronization ..... | 24 | +| 4.14 Key issue #14: Application traffic influence for initially selected EAS ..... | 25 | +| 4.15 Key issue #15: Support of constrained devices for Edge..... | 26 | +| 4.16 Key issue #16: support of NAT deployed within the edge data network ..... | 26 | +| 4.17 Key issue #17: Discovery of a common EAS ..... | 26 | +| 4.18 Key issue #18: EAS bundles ..... | 27 | +| 4.19 Key issue #19: ACR scenario combination..... | 28 | +| 4.20 Key issue #20: Supporting composite EASs..... | 28 | +| 4.21 Key issue #21: Simultaneously EAS connectivity in ACR..... | 28 | +| 4.22 Key issue #22: EAS discovery in Edge Node sharing scenario ..... | 30 | +| 4.23 Key issue #23: Reliable Edge service ..... | 30 | +| 4.24 Key issue #24: SEAL capability access for EEL support ..... | 31 | +| 5 Architectural requirements..... | 31 | +| 5.1 General requirements ..... | 31 | +| 5.1.1 General ..... | 31 | +| 5.2 Enablement of Service APIs exposed by EAS..... | 31 | +| 5.2.1 General ..... | 31 | +| 5.2.2 Requirements..... | 31 | +| 5.3 ECS discovery ..... | 32 | +| 5.3.1 General ..... | 32 | +| 5.3.2 Requirements..... | 32 | +| 5.4 Alignment of EDGEAPP and ETSI MEC..... | 32 | +| 5.4.1 General ..... | 32 | +| 5.4.2 Requirements..... | 32 | +| 5.5 Common EAS ..... | 33 | +| 5.5.1 General ..... | 33 | +| 5.5.2 Requirements..... | 33 | +| 6 Enhanced Application Architecture ..... | 33 | +| 6.1 Option #1: Roaming architecture ..... | 33 | +| 6.1.1 Architecture enhancements..... | 33 | +| 6.1.1.1 Local breakout roaming architecture: Local breakout to access H-ECS ..... | 33 | +| 6.1.1.2 Home-routed EDGE-4 access to H-ECS ..... | 34 | + +| | | | +|----------|--------------------------------------------------------------------------------------------------|----| +| 6.1.2 | Identities ..... | 35 | +| 6.1.3 | Cardinality rules ..... | 35 | +| 6.2 | Option #2: Non-roaming architecture ..... | 35 | +| 6.2.1 | Architecture enhancements..... | 35 | +| 6.2.2 | Identities ..... | 35 | +| 6.2.3 | Cardinality rules ..... | 35 | +| 6.3 | Option #3: Edge Notification Server architecture..... | 35 | +| 6.3.1 | Architecture enhancements..... | 36 | +| 6.3.1.1 | Edge Notification Server (ENS) ..... | 36 | +| 6.3.1.2 | ENS Discovery ..... | 37 | +| 6.4 | Option #4: Constrained devices with limited capabilities..... | 37 | +| 6.4.1 | Architecture enhancements..... | 37 | +| 6.4.1.1 | General..... | 37 | +| 6.4.1.2 | Architecture ..... | 37 | +| 6.4.2 | Identities ..... | 38 | +| 6.4.3 | Cardinality rules ..... | 38 | +| 6.5 | Option #5: Architecture for ACR between EAS and CAS without CES..... | 38 | +| 6.5.1 | Architecture enhancements..... | 38 | +| 6.5.2 | Identities ..... | 39 | +| 6.5.3 | Cardinality rules ..... | 39 | +| 6.6 | Option #6: Architecture for ACR between EAS and CAS with CES..... | 40 | +| 6.6.1 | Architecture enhancements..... | 40 | +| 6.6.2 | Identities ..... | 40 | +| 6.6.3 | Cardinality rules ..... | 41 | +| 6.7 | Option #7: Architecture for Common EAS selection with central binding server ..... | 41 | +| 6.7.1 | Architecture enhancements..... | 41 | +| 6.7.2 | Identities ..... | 41 | +| 6.7.3 | Cardinality rules ..... | 41 | +| 6.8 | Option #8: Architecture for ACR update in service continuity planning ..... | 41 | +| 6.8.1 | Architecture enhancements..... | 41 | +| 6.8.2 | Identities ..... | 42 | +| 6.8.3 | Cardinality rules ..... | 42 | +| 6.9 | Option #9: EEL utilization of SEAL services deployed in EDN..... | 42 | +| 6.9.1 | Architecture enhancements..... | 42 | +| 6.9.2 | Identities ..... | 43 | +| 6.9.3 | Cardinality rules ..... | 43 | +| 6.10 | Option #10: EDGEAPP architecture in edge node sharing..... | 43 | +| 6.10.1 | Architecture enhancements..... | 43 | +| 6.10.2 | Identities ..... | 43 | +| 6.10.3 | Cardinality rules ..... | 43 | +| 6.11 | Option #11: EDGEAPP architecture enhanced with Central AC Association Repository..... | 44 | +| 6.11.1 | Architecture enhancements..... | 44 | +| 6.11.2 | Identities ..... | 44 | +| 6.11.3 | Cardinality rules ..... | 44 | +| 6.12 | Option #12: Architecture for Federation and Roaming ..... | 45 | +| 6.12.0 | Assumptions ..... | 45 | +| 6.12.1 | Architecture enhancements..... | 45 | +| 6.12.2 | Enhanced functional entities..... | 46 | +| 6.12.2.1 | Edge Configuration Server (Edge Repository)..... | 46 | +| 6.12.3 | Reference point..... | 46 | +| 6.12.3.1 | EDGE-10 ..... | 46 | +| 6.12.4 | Cardinality rules ..... | 46 | +| 7 | Solutions..... | 47 | +| 7.0 | Mapping of solutions to key issues ..... | 47 | +| 7.1 | Solution #1: Service provisioning via push notification ..... | 49 | +| 7.1.1 | Architecture enhancements..... | 49 | +| 7.1.2 | Solution description..... | 49 | +| 7.1.2.1 | General..... | 49 | +| 7.1.2.2 | Procedure ..... | 49 | +| 7.1.3 | Solution evaluation ..... | 50 | +| 7.2 | Solution #2: Traffic filter support for EDGE-3 API addressing application traffic detection..... | 51 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------------------|----| +| 7.2.1 | Architecture enhancements..... | 51 | +| 7.2.2 | Solution description..... | 51 | +| 7.2.3 | Solution evaluation..... | 52 | +| 7.3 | Solution #3: Service provisioning triggering via SMS over NAS ..... | 52 | +| 7.3.1 | Architecture enhancements..... | 52 | +| 7.3.2 | Solution description..... | 52 | +| 7.3.2.1 | General..... | 52 | +| 7.3.2.2 | Procedure ..... | 52 | +| 7.3.3 | Solution evaluation ..... | 54 | +| 7.4 | Solution #4: ECS discovery through serving ECS to support edge services across ECSPs ..... | 54 | +| 7.4.1 | Architecture enhancements..... | 54 | +| 7.4.2 | Solution description..... | 54 | +| 7.4.2.1 | General..... | 54 | +| 7.4.2.2 | Procedure ..... | 55 | +| 7.4.3 | Solution evaluation ..... | 56 | +| 7.5 | Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs..... | 56 | +| 7.5.1 | Architecture enhancements..... | 56 | +| 7.5.2 | Solution description..... | 57 | +| 7.5.2.1 | General..... | 57 | +| 7.5.2.2 | Procedure ..... | 57 | +| 7.5.3 | Solution evaluation ..... | 59 | +| 7.6 | Solution #6: ACR update in service continuity planning..... | 59 | +| 7.6.1 | Architecture enhancements..... | 59 | +| 7.6.2 | Solution description..... | 59 | +| 7.6.2.1 | ACR modification solution..... | 59 | +| 7.6.2.1.1 | EEC-based ACR modification procedure ..... | 59 | +| 7.6.2.1.2 | EES-based modification procedure ..... | 60 | +| 7.6.2.1.3 | ACR modification execution procedure..... | 61 | +| 7.6.3 | Solution evaluation ..... | 62 | +| 7.7 | Solution #7: EES monitors UE mobility for service continuity planning..... | 62 | +| 7.7.1 | Architecture enhancements..... | 62 | +| 7.7.2 | Solution description..... | 62 | +| 7.7.2.1 | General..... | 62 | +| 7.7.2.2 | Procedure ..... | 62 | +| 7.7.3 | Solution evaluation ..... | 64 | +| 7.8 | Solution #8: EAS Service API enablement using CAPIF ..... | 64 | +| 7.8.1 | Architecture enhancements..... | 64 | +| 7.8.2 | Solution description..... | 65 | +| 7.8.2.1 | General..... | 65 | +| 7.8.2.2 | CAPIF operations in Edge Enabler Layer ..... | 65 | +| 7.8.2.3 | Service KPIs in CAPIF for EAS Service APIs..... | 67 | +| 7.8.3 | Solution evaluation ..... | 71 | +| 7.9 | Solution #9: Application traffic influence trigger from EAS..... | 71 | +| 7.9.1 | Architecture enhancements..... | 71 | +| 7.9.2 | Solution description..... | 71 | +| 7.9.2.1 | General..... | 71 | +| 7.9.2.2 | Procedure ..... | 71 | +| 7.10 | Solution #10: low power mode support ..... | 72 | +| 7.10.1 | Architecture enhancements..... | 72 | +| 7.10.2 | Solution description..... | 72 | +| 7.10.2.1 | General..... | 72 | +| 7.10.2.2 | Procedure ..... | 73 | +| 7.11 | Solution #11: A deployment option for alignment with ETSI MEC using CAPIF ..... | 74 | +| 7.11.1 | Architecture enhancements..... | 74 | +| 7.11.2 | Solution description..... | 74 | +| 7.11.2.1 | General..... | 74 | +| 7.11.2.2 | Procedure ..... | 75 | +| 7.11.3 | Solution evaluation ..... | 75 | +| 7.12 | Solution #12: Service continuity planning permission ..... | 75 | +| 7.12.1 | Architecture enhancements..... | 75 | +| 7.12.2 | Solution description..... | 76 | +| 7.12.2.1 | General..... | 76 | + +| | | | +|------------|--------------------------------------------------------------------------------------------|----| +| 7.12.2.2 | Procedure ..... | 76 | +| 7.12.3 | Solution evaluation ..... | 77 | +| 7.13 | Solution #13: Update ECS configuration information ..... | 77 | +| 7.13.1 | Architecture enhancements..... | 77 | +| 7.13.2 | Solution description..... | 77 | +| 7.13.3 | Solution evaluation ..... | 78 | +| 7.14 | Solution #14: V-ECS Discovery via the H-ECS ..... | 78 | +| 7.14.1 | Architecture enhancements..... | 78 | +| 7.14.2 | Solution description..... | 78 | +| 7.14.2.1 | General ..... | 78 | +| 7.14.2.2 | Procedure ..... | 78 | +| 7.14.2.2.1 | V-ECS Discovery via the H-ECS by request-response..... | 78 | +| 7.14.2.2.2 | V-ECS Discovery via the H-ECS by subscribe-notify..... | 80 | +| 7.14.3 | Solution evaluation ..... | 81 | +| 7.15 | Solution #15: Initial EAS selection declaration ..... | 81 | +| 7.15.1 | Architecture enhancements..... | 81 | +| 7.15.2 | Solution description..... | 81 | +| 7.15.3 | Solution evaluation ..... | 83 | +| 7.16 | Solution #16: EAS discovery for different users ..... | 83 | +| 7.16.1 | Architecture enhancements..... | 83 | +| 7.16.2 | Solution description..... | 83 | +| 7.16.2.1 | General ..... | 83 | +| 7.16.2.2 | Procedure ..... | 83 | +| 7.16.3 | Solution evaluation ..... | 83 | +| 7.17 | Solution #17: Traffic influence for initial EAS discovery ..... | 84 | +| 7.17.1 | Architecture enhancements..... | 84 | +| 7.17.2 | Solution description..... | 84 | +| 7.17.2.1 | General ..... | 84 | +| 7.17.2.2 | Procedure ..... | 84 | +| 7.17.3 | Solution evaluation ..... | 84 | +| 7.18 | Solution #18: Constraint device in EDGEAPP ..... | 85 | +| 7.18.1 | Architecture enhancements..... | 85 | +| 7.18.2 | Solution description..... | 85 | +| 7.18.3 | Solution evaluation ..... | 86 | +| 7.19 | Solution #19: EES determines the selected ACR scenario ..... | 87 | +| 7.19.1 | Architecture enhancements..... | 87 | +| 7.19.2 | Solution description..... | 87 | +| 7.19.2.1 | General ..... | 87 | +| 7.19.2.2 | Procedure ..... | 87 | +| 7.19.3 | Solution evaluation ..... | 88 | +| 7.20 | Solution #20: Propagation of EEL notifications to EEC using Edge Notification Server ..... | 88 | +| 7.20.1 | Architecture enhancements..... | 88 | +| 7.20.2 | Solution description..... | 88 | +| 7.20.2.1 | General ..... | 88 | +| 7.20.2.2 | Notification delivery over a direct Notification Channel Procedure ..... | 88 | +| 7.20.2.3 | Notification delivery using a Push Server Procedure (indirect Notification Channel)..... | 90 | +| 7.20.3 | Solution evaluation ..... | 92 | +| 7.21 | Solution #21: Prediction expiration time for service continuity planning enhancement ..... | 92 | +| 7.21.1 | Architecture enhancements..... | 92 | +| 7.21.2 | Solution description..... | 92 | +| 7.21.2.1 | General ..... | 92 | +| 7.21.2.2 | Procedure ..... | 93 | +| 7.21.3 | Solution evaluation ..... | 94 | +| 7.22 | Solution #22: Support simultaneous EAS connectivity in ACR..... | 94 | +| 7.22.1 | Architecture enhancements..... | 94 | +| 7.22.2 | Solution description..... | 94 | +| 7.22.2.1 | Solution for traffic influence..... | 94 | +| 7.22.3 | Solution evaluation ..... | 97 | +| 7.23 | Solution #23: UE identification with NAT ..... | 97 | +| 7.23.1 | Architecture enhancements..... | 97 | +| 7.23.2 | Solution description..... | 97 | +| 7.23.2.1 | General ..... | 97 | + +| | | | +|--------------|------------------------------------------------------------------------------------------------------------|-----| +| 7.23.2.2 | Procedure ..... | 98 | +| 7.23.3 | Solution evaluation ..... | 99 | +| 7.24 | Solution #24: ACR between EAS and CAS with CES ..... | 100 | +| 7.24.1 | Architecture enhancements..... | 100 | +| 7.24.2 | Solution description..... | 100 | +| 7.24.2.0 | General ..... | 100 | +| 7.24.2.1 | ACR Scenarios..... | 101 | +| 7.24.2.1.1 | CAS decided ACR scenario ..... | 101 | +| 7.25.2.2.2 | "Discover T-EAS" for CAS ..... | 101 | +| 7.24.3 | Solution evaluation ..... | 101 | +| 7.25 | Solution #25: ACR between EAS and CAS without CES ..... | 101 | +| 7.25.1 | Architecture enhancements..... | 101 | +| 7.25.2 | Solution description..... | 101 | +| 7.25.2.1 | General ..... | 101 | +| 7.25.2.2 | Procedure ..... | 101 | +| 7.25.2.2.1 | Updated 3GPP TS 23.558 clause 8.8.2.2 Initiation by EEC using regular EAS Discovery ..... | 101 | +| 7.25.2.2.2 | Updated 3GPP TS 23.558 clause 8.8.2.3 EEC executed ACR via S-EES..... | 103 | +| 7.25.2.2.3 | Updated 3GPP TS 23.558 clause 8.8.2.4 S-EAS decided ACR scenario ..... | 105 | +| 7.25.2.2.4 | Updated 3GPP TS 23.558 clause 8.8.2.5 S-EES executed ACR ..... | 107 | +| 7.25.2.2.5 | EEC initiated ACR..... | 109 | +| 7.25.2.2.6 | CAS initiated ACR..... | 109 | +| 7.25.2.2.6.1 | EES discovery via service provision triggering ..... | 110 | +| 7.25.2.2.6.2 | CAS initiated ACR via ECS..... | 111 | +| 7.25.3 | Solution evaluation ..... | 112 | +| 7.26 | Solution #26: Bundled EASs..... | 112 | +| 7.26.1 | Architecture enhancements..... | 112 | +| 7.26.2 | Solution description..... | 112 | +| 7.26.2.1 | General ..... | 112 | +| 7.26.2.2 | Handling of EAS bundle information by the EEC ..... | 116 | +| 7.26.2.3 | Handling of EAS bundle information and EAS bundle requirements by the EES ..... | 116 | +| 7.26.2.4 | Handling of EAS bundle information by the ECS..... | 116 | +| 7.26.2.5 | Handling of EAS bundle when the bundle EAS are registered on the multiple EESs in the same EDN ..... | 117 | +| 7.26.2.5.1 | ACR procedure for bundled EAS located on multiple EES within EHE for S-EES executed ACR..... | 117 | +| 7.26.2.5.2 | ACR procedure for bundled EAS located on multiple EES within same EHE for S-EAS decided ACR scenario ..... | 119 | +| 8.2.6 | EES Profile ..... | 121 | +| 8.5.3.2 | EAS discovery request..... | 122 | +| 7.26.3 | Solution evaluation ..... | 122 | +| 7.27 | Solution #27: Enabling AC Association Aware services by selecting common EASs ..... | 123 | +| 7.27.1 | Architecture enhancements..... | 123 | +| 7.27.2 | Solution description..... | 123 | +| 7.27.2.1 | General ..... | 123 | +| 7.27.2.2 | New Information Elements ..... | 123 | +| 7.27.2.2.1 | AC Association Profile..... | 123 | +| 7.27.2.2.1.1 | Description ..... | 123 | +| 7.27.2.2.1.2 | Determining grouping based on AC Association type ..... | 124 | +| 7.27.2.3 | Enhancements to existing Information Elements ..... | 125 | +| 7.27.2.4 | Enhancements to Service Provisioning for determining common EES ..... | 127 | +| 7.27.2.4.1 | Using the "assumed common EES" option (option i) ..... | 127 | +| 7.27.2.4.2 | Determining common EES with CAAR (option ii) ..... | 127 | +| 7.27.2.5 | Enhancements to EAS Discovery for determining common EAS ..... | 128 | +| 7.27.2.6 | Enhancements to ACR..... | 128 | +| 7.27.2.7 | Other procedural enhancements..... | 129 | +| 7.27.2.8 | New procedures ..... | 130 | +| 7.27.2.8.1 | New procedures for option ii..... | 130 | +| 7.27.2.8.1.1 | General ..... | 130 | +| 7.27.2.8.1.2 | EES Update of AC Associations with CAAR (option ii)..... | 130 | +| 7.27.2.8.1.3 | ECS Query of AC Associations with CAAR (option ii) ..... | 130 | +| 7.27.3 | Solution evaluation ..... | 130 | +| 7.28 | Solution #28: Common EAS discovery using EAS selection information..... | 131 | + +| | | | +|------------|-------------------------------------------------------------------------------|-----| +| 7.28.1 | Architecture enhancements..... | 131 | +| 7.28.2 | Solution description..... | 131 | +| 7.28.2.1 | General..... | 131 | +| 7.28.2.2 | Procedure ..... | 131 | +| 7.28.3 | Solution evaluation..... | 133 | +| 7.29 | Solution #29: Discovery of a common EAS ..... | 133 | +| 7.29.1 | Architecture enhancements..... | 133 | +| 7.29.2 | Solution description..... | 134 | +| 7.29.2.1 | General..... | 134 | +| 7.29.2.2 | Procedure ..... | 135 | +| 7.29.2.3 | Enhanced Service provisioning request..... | 137 | +| 7.29.2.4 | Enhanced EAS discovery filters ..... | 137 | +| 7.29.2.5 | New Group profile common information element ..... | 139 | +| 7.29.2.6 | Enhanced EDN configuration information ..... | 139 | +| 7.29.3 | Solution evaluation..... | 140 | +| 7.30 | Solution #30: Common EAS selection..... | 141 | +| 7.30.1 | Architecture enhancements..... | 141 | +| 7.30.2 | Solution description..... | 141 | +| 7.30.3 | Solution evaluation..... | 143 | +| 7.31 | Solution #31: Discover common EAS ..... | 143 | +| 7.31.1 | Architecture enhancements..... | 143 | +| 7.31.2 | Solution description..... | 143 | +| 7.31.2.1 | General..... | 143 | +| 7.31.2.2 | Procedure for EEC(s) connected to different EES(s) ..... | 144 | +| 7.31.2.3 | Procedure for EEC(s) connected to same EES ..... | 146 | +| 7.31.2.4 | Procedure for Edge enabler layer support for common EAS announcement..... | 148 | +| 7.31.2.5 | Enhancements to 3GPP TS 23.558 Table 8.2.2-1 AC Profile ..... | 149 | +| 7.31.2.6 | Enhancements to 3GPP TS 23.558 8.3.3.2.2 ..... | 149 | +| 7.31.3 | Solution evaluation..... | 150 | +| 7.32 | Solution #32: Dynamic EAS instantiation triggering and notification ..... | 150 | +| 7.32.1 | Architecture enhancements..... | 150 | +| 7.32.2 | Solution description..... | 150 | +| 7.32.2.1 | General..... | 150 | +| 7.32.2.2 | Dynamic EAS instantiation triggering and notification procedures ..... | 151 | +| 7.32.3 | Solution evaluation..... | 152 | +| 7.33 | Solution #33: Support for EEC Discovery of EAS(es) before instantiation ..... | 153 | +| 7.33.1 | Architecture enhancements..... | 153 | +| 7.33.2 | Solution description..... | 153 | +| 7.33.2.1 | General..... | 153 | +| 7.33.2.2 | Procedure ..... | 153 | +| 7.33.3 | Solution evaluation..... | 155 | +| 7.34 | Solution #34: EDGE-5 APIs ..... | 156 | +| 7.34.1 | Architecture enhancements..... | 156 | +| 7.34.2 | Solution description..... | 156 | +| 7.34.2.1 | General..... | 156 | +| 7.34.2.2 | Procedure ..... | 156 | +| 7.34.2.2.1 | General ..... | 156 | +| 7.34.2.2.2 | AC registration request..... | 156 | +| 7.34.2.2.3 | EAS discovery request ..... | 157 | +| 7.34.2.2.4 | ACR request..... | 158 | +| 7.34.2.2.5 | AC subscription request ..... | 159 | +| 7.34.2.2.6 | AC notification..... | 160 | +| 7.34.3 | Solution evaluation..... | 161 | +| 7.35 | Solution #35: EEC selected ACR scenarios..... | 161 | +| 7.35.1 | Architecture enhancements..... | 161 | +| 7.35.2 | Solution description..... | 161 | +| 7.35.2.1 | General..... | 161 | +| 7.35.2.2 | Procedure ..... | 161 | +| 7.35.3 | Solution evaluation..... | 163 | +| 7.36 | Solution #36: Alignment of EDGEAPP and ETSI MEC ..... | 163 | +| 7.36.1 | Architecture enhancements..... | 163 | +| 7.36.2 | Solution description..... | 163 | + +| | | | +|------------|----------------------------------------------------------------------------------------|-----| +| 7.36.2.1 | General..... | 163 | +| 7.36.2.2 | Alignment of EAS registration and MEC application registration..... | 163 | +| 7.36.2.3 | Alignment of EDGE-9 and Mp3..... | 166 | +| 7.36.3 | Solution evaluation..... | 166 | +| 7.37 | Solution #37: ACR request trigger timing ..... | 166 | +| 7.37.1 | Architecture enhancements..... | 166 | +| 7.37.2 | Solution description..... | 166 | +| 7.37.2.1 | Procedure ..... | 167 | +| 7.37.2.2 | Enhancements to procedures in TS 23.558..... | 167 | +| 7.37.2.2.1 | Enhancements to 'Initiation by EEC using regular EAS Discovery' in clause 8.8.2.2..... | 167 | +| 7.37.2.2.2 | Enhancements to 'EEC executed ACR via S-EES' in clause 8.8.2.3 ..... | 167 | +| 7.37.2.2.3 | Enhancements to 'EEC executed ACR via T-EES' in clause 8.8.2.6 ..... | 168 | +| 7.37.3 | Solution evaluation..... | 169 | +| 7.38 | Solution #38: ACR coordination..... | 169 | +| 7.38.1 | Architecture enhancements..... | 169 | +| 7.38.2 | Solution description..... | 169 | +| 7.38.2.1 | General..... | 169 | +| 7.38.2.2 | Procedure ..... | 169 | +| 7.38.3 | Solution evaluation..... | 171 | +| 7.39 | Solution #39: EAS selection synchronization at registration..... | 171 | +| 7.39.1 | Architecture enhancements..... | 171 | +| 7.39.2 | Solution description..... | 171 | +| 7.39.2.1 | General..... | 171 | +| 7.39.2.2 | Procedure ..... | 171 | +| 7.39.3 | Solution evaluation..... | 176 | +| 7.40 | Solution #40: EAS instantiation status provisioned by ECS..... | 176 | +| 7.40.1 | Architecture enhancements..... | 176 | +| 7.40.2 | Solution description..... | 176 | +| 7.40.2.1 | General..... | 176 | +| 7.40.2.2 | Procedure ..... | 176 | +| 7.40.3 | Solution evaluation..... | 178 | +| 7.41 | Solution #41: Interaction with ADAES for edge load analytics ..... | 179 | +| 7.41.1 | Architecture enhancements..... | 179 | +| 7.41.2 | Solution description..... | 179 | +| 7.41.2.1 | General..... | 179 | +| 7.41.2.2 | Procedure ..... | 179 | +| 7.41.3 | Solution evaluation..... | 180 | +| 7.42 | Solution #42: EAS selection and instantiation in EES..... | 180 | +| 7.42.1 | Architecture enhancements..... | 180 | +| 7.42.2 | Solution description..... | 180 | +| 7.42.3 | Solution evaluation..... | 181 | +| 7.43 | Solution #43: EAS discovery for Edge node sharing..... | 182 | +| 7.43.1 | Architecture enhancements..... | 182 | +| 7.43.2 | Solution description..... | 182 | +| 7.43.2.1 | General..... | 182 | + +| | | | +|------------|------------------------------------------------------------------------------|-----| +| 7.43.2.2 | Publish/unpublish and fetch application ..... | 182 | +| 7.43.2.3 | EAS discovery without published application info ..... | 184 | +| 7.43.2.4 | EAS discovery with published application info ..... | 185 | +| 7.43.3 | Solution evaluation ..... | 187 | +| 7.44 | Solution #44: EAS discovery for Edge node sharing ..... | 187 | +| 7.44.1 | Architecture enhancements..... | 187 | +| 7.44.2 | Solution description..... | 187 | +| 7.44.2.1 | General ..... | 187 | +| 7.44.2.2 | Publish/unpublish and fetch application ..... | 187 | +| 7.44.2.3 | EAS discovery for edge node sharing Procedure ..... | 190 | +| 7.44.2.4 | Get list of all registered EAS from partner OP ..... | 191 | +| 7.44.3 | Solution evaluation ..... | 191 | +| 7.45 | Solution #45: EAS discovery in Edge Node sharing scenario ..... | 192 | +| 7.45.1 | Architecture enhancements..... | 192 | +| 7.45.2 | Solution description..... | 192 | +| 7.45.2.1 | General ..... | 192 | +| 7.45.2.2 | EAS discovery Procedure ..... | 192 | +| 7.45.2.3 | T-EAS discovery Procedure ..... | 193 | +| 7.45.3 | Solution evaluation ..... | 194 | +| 7.46 | Solution #46: EEC selected ACR scenario for EAS bundles..... | 194 | +| 7.46.1 | Architecture enhancements..... | 194 | +| 7.46.2 | Solution description..... | 195 | +| 7.46.2.1 | General ..... | 195 | +| 7.46.2.2 | Procedure ..... | 195 | +| 7.46.3 | Solution evaluation ..... | 197 | +| 7.47 | Solution #47: EES determines the selected ACR scenario for EAS bundles ..... | 197 | +| 7.47.1 | Architecture enhancements..... | 197 | +| 7.47.2 | Solution description..... | 197 | +| 7.47.2.1 | General ..... | 197 | +| 7.47.2.2 | Procedure ..... | 197 | +| 7.47.3 | Solution evaluation ..... | 199 | +| 7.48 | Solution #48: Edge server set and edge service set..... | 199 | +| 7.48.1 | Architecture enhancements..... | 199 | +| 7.48.2 | Solution description..... | 199 | +| 7.48.2.1 | General ..... | 199 | +| 7.48.2.2 | Reliability support with Sets..... | 199 | +| 7.48.2.3 | EES binding update ..... | 201 | +| 7.48.2.4 | Context Transfer procedure ..... | 201 | +| 7.48.3 | Solution evaluation ..... | 202 | +| 7.49 | Solution #49: ACR for EAS composition ..... | 202 | +| 7.49.1 | Architecture enhancements..... | 202 | +| 7.49.2 | Solution description..... | 202 | +| 7.49.3 | Solution evaluation ..... | 202 | +| 7.50 | Solution #50: Enhanced ECS for federation of services ..... | 202 | +| 7.50.1 | Architecture enhancements..... | 202 | +| 7.50.2 | Solution description..... | 202 | +| 7.50.2.1 | ECS registration with the ECS-ER ..... | 202 | +| 7.50.2.2 | ECS querying ECS-ER ..... | 203 | +| 7.50.2.3 | Service provisioning for Federation and/or Roaming..... | 204 | +| 7.51 | Solution #51: EEC sharing UE Mobility requirement ..... | 206 | +| 7.51.1 | Architecture enhancements..... | 206 | +| 7.51.2 | Solution description..... | 206 | +| 7.51.2.1 | Enhancements to EEC Registration..... | 206 | +| 7.51.2.1.1 | Enhancements to EEC registration request ..... | 206 | +| 7.51.3 | Solution evaluation ..... | 206 | +| 7.52 | Solution #52: EES policy differentiation ..... | 206 | +| 7.52.1 | Architecture enhancements..... | 206 | +| 7.52.2 | Solution description..... | 207 | +| 7.52.3 | Solution evaluation ..... | 208 | +| 7.53 | Solution #53: Support for EAS synchronization..... | 208 | +| 7.53.1 | Architecture enhancements..... | 208 | +| 7.53.2 | Solution description..... | 209 | + +| | | | +|----------|----------------------------------------------------------------------------------|-----| +| 7.53.2.1 | EAS Discovery to request support for content synchronization..... | 209 | +| 7.53.3 | Solution evaluation..... | 210 | +| 7.54 | Solution #54: EEL assist the application layer to determine the common EAS ..... | 210 | +| 7.54.1 | Architecture enhancements..... | 210 | +| 7.54.2 | Solution description..... | 210 | +| 7.54.2.1 | General..... | 210 | +| 7.54.2.2 | Procedure ..... | 210 | +| 7.54.3 | Solution evaluation ..... | 211 | +| 7.55 | Solution #55: Non-roaming UE location invocation..... | 211 | +| 7.55.1 | Architecture enhancements..... | 211 | +| 7.55.2 | Solution description..... | 211 | +| 7.55.2.1 | General..... | 211 | +| 7.55.2.2 | Non-roaming UE location invocation of EES ..... | 212 | +| 7.55.3 | Solution evaluation..... | 213 | +| 8 | Deployment scenarios..... | 213 | +| 9 | Involved entities and relationships..... | 214 | +| 9.1 | Federation and Roaming ..... | 214 | +| 9.1.1 | General ..... | 214 | +| 10 | Overall evaluation ..... | 215 | +| 10.0 | General ..... | 215 | +| 10.1 | Architecture enhancements ..... | 215 | +| 10.1.1 | Support for Terminal Equipment (TE) ..... | 215 | +| 10.1.2 | Roaming architecture..... | 215 | +| 10.1.3 | Architecture for Federation and Roaming ..... | 215 | +| 10.2 | Key issue evaluations..... | 216 | +| 10.2.0 | General ..... | 216 | +| 10.2.1 | Key issue #1: Enhanced notification service to the EEC ..... | 220 | +| 10.2.2 | Key issue #2: Enablement of Service APIs exposed by EAS ..... | 221 | +| 10.2.3 | Key issue #3: Enhancements to service continuity planning ..... | 222 | +| 10.2.4 | Key issue #4: EDGE-5 ..... | 222 | +| 10.2.5 | Key issue #5: Alignment of EDGEAPP and ETSI MEC ..... | 223 | +| 10.2.6 | Key issue #6: Edge services support across ECSPs ..... | 223 | +| 10.2.8 | Key issue #8: EAS selection synchronization ..... | 225 | +| 10.2.9 | Key issue #9: Enhancement of dynamic EAS instantiation triggering ..... | 225 | +| 10.2.10 | Key issue #10: Support for Roaming UEs ..... | 227 | +| 10.2.11 | Key issue #11: ACR between EAS and Cloud Application Server ..... | 229 | +| 10.2.12 | Key issue #12: EEL service differentiation..... | 230 | +| 10.2.13 | Key issue #13: Edge enabler layer support for EAS synchronization..... | 230 | +| 10.2.14 | Key issue #14: Application traffic influence for initially selected EAS ..... | 230 | +| 10.2.15 | Key issue #15: Support of constrained devices for Edge ..... | 231 | +| 10.2.16 | Key issue #16: support of NAT deployed within the edge data network..... | 231 | +| 10.2.17 | Key issue #17: Discovery of a common EAS ..... | 231 | +| 10.2.18 | Key issue #18: EAS bundles ..... | 232 | +| 10.2.19 | Key issue #19: ACR scenario combination..... | 232 | +| 10.2.20 | Key issue #20: Supporting composite EASs..... | 233 | +| 10.2.21 | Key issue #21: Simultaneously EAS connectivity in ACR..... | 233 | +| 10.2.22 | Key issue #22: EAS discovery in Edge Node sharing scenario ..... | 233 | +| 10.2.23 | Key issue #23: Reliable Edge service..... | 234 | +| 10.2.24 | Key issue #24: SEAL capability access for EEL support ..... | 234 | +| 11 | Conclusions..... | 235 | +| 11.1 | General ..... | 235 | +| 11.2 | Conclusions for normative work..... | 235 | +| 11.2.1 | General conclusions..... | 235 | +| 11.2.2 | Architecture enhancement conclusions ..... | 235 | +| 11.2.3 | Solution conclusions..... | 236 | + +| | | +|--------------------------------------------------------------------------------------------------------|------------| +| Annex A (Informative): ETSI MEC and EDGEAPP system comparison ..... | 240 | +| A.1 General ..... | 240 | +| A.2 Service consumer and service provider ..... | 240 | +| A.3 EAS/MEC application profile provisioning ..... | 240 | +| A.4 EAS registration and EAS discovery ..... | 241 | +| Annex B (Informative): Deployment and Evolution options of EDGEAPP and ETSI MEC platforms ..... | 242 | +| B.1 General ..... | 242 | +| B.2 Deployment options ..... | 243 | +| B.2.1 Deployment Option-1: Collocated Platforms ..... | 243 | +| B.2.2 Deployment Option-2: Converged architecture ..... | 243 | +| B.2.2.1 General ..... | 243 | +| B.2.2.2 Evolution Options ..... | 244 | +| B.2.2.2.1 General ..... | 244 | +| B.2.2.2.2 Evolution Option #1- Enhancement of a deployed MEP to support the functionality of EES ..... | 244 | +| B.2.2.2.3 Evolution Option #2 Enhancement of a deployed EES to support the functionality of MEP ..... | 245 | +| B.2.3 Deployment Option-3: non-Collocated Platforms ..... | 245 | +| Annex C (informative): Change history ..... | 246 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- Introduction + +Rel-17 TS 23.558 [2] defines the application layer architecture to enable edge applications over 3GPP networks. It includes features such as ECS discovery, service provisioning, EAS discovery, EEC/EAS/EES registration, network and Edge Enabler Layer capability exposure, service continuity support with seamless service continuity and EEC context continuity etc. along with cardinality rules, deployment options, involved relationships and mapping with ETSI MEC [3] and GSMA OP [4] architectures. + +This TR documents a study on architecture and procedure enhancements to improve the Rel-17 architecture for enabling edge applications, and to support emerging industry requirements. + +# --- 1 Scope + +The present document is a technical report capturing the study on enhanced architecture for enabling edge applications over 3GPP networks. The study bases the enhancements on the work done in 3GPP TS 23.558 [2] and takes into consideration other related work done within and outside 3GPP i.e. ETSI MEC [3] and GSMA OP [4]. + +The aspects of the study include identifying new key issues, architecture requirements, related architecture enhancements and solutions, cardinality rules, deployment options, and involved entities and relationships to enhance the Rel-17 architecture for enabling edge applications. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TR 23.558: "Architecture for enabling Edge Applications". +- [3] ETSI ISG MEC ETSI GS MEC 003, "Multi-access Edge Computing (MEC); Framework and Reference Architecture". +- [4] GSMA OPG.02: "Operator Platform Telco Edge Requirements", +- [5] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [6] 3GPP TR 23.758: "Study on application architecture for enabling Edge Applications". +- [7] 3GPP TR 23.721: "Study on Sponsored Data Connectivity Improvements". +- [8] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [9] 3GPP TS 23.203: "Policies and Charging control architecture; Stage 2". +- [10] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [11] 3GPP TS 23.503: "Policies and Charging control architecture; Stage 2". +- [12] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1". +- [13] ETSI GS MEC 010-2: "Multi-access Edge Computing (MEC); MEC Management; Part 2: Application lifecycle, rules and requirements management". +- [14] ETSI GS MEC 011 v3.0.5: "Multi-access Edge Computing (MEC); Edge Platform Application Enablement". +- [15] ETSI GS MEC 001: "Multi-access Edge Computing (MEC); Terminology ". +- [16] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2". + +- [17] 3GPP TS 29.522: "Network Exposure Function Northbound APIs; Stage 3". +- [18] 3GPP TS 29.122: "T8 reference point for Northbound APIs". +- [19] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2". +- [20] 3GPP TS 28.538: "Management and orchestration; Edge Computing Management". +- [21] 3GPP TR 22.944: "Report on service requirements for UE functionality split". +- [22] ETSI GS MEC 021 V2.2.1 (2022-00), "Multi-access Edge Computing (MEC); Application Mobility Service API". +- [23] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". + +# --- 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1], 3GPP TS 23.558 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1] and 3GPP TS 23.558 [2]. + +**Cloud data network:** A data network having a set of servers deployed in a central place and capable of serving UEs from wider coverage area, as opposed to the edge data network. + +**Primary ECS:** An ECS whose address information is configured with the EEC. EEC is authorized to communicate with the Primary ECS directly. + +NOTE: The term 'Primary ECS' can be replaced with 'Configured ECS' during the normative phase. + +**Primary ECSP:** An ECSP for which the UE has authorization to obtain service. + +**Partner ECS:** A federation partner of the Primary ECS. EEC is not configured with the address information of Partner ECSs. + +**Partner ECSP:** An ECSP with whom the Primary ECSP has a service level agreement for resource sharing i.e. a federation partner of the Primary ECSP. + +## 3.2 Symbols + +None. + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1], 3GPP TS 23.558 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1] and 3GPP TS 23.558 [2]. + +| | | +|-------|------------------------------------------------| +| ADAES | Application Data Analytics Enablement Services | +| AEF | API Exposing Function | +| AMBR | Aggregate Maximum Bit Rate | +| AMF | API Management Function | +| APF | API Provider Function | +| APN | Access Point Name | +| APNS | Apple Push Notification Service | +| BS | Binding Server | +| CAAR | Central AC Association Repository | +| CAPIF | Common API Framework | + +| | | +|---------|-------------------------------------------------| +| CAS | Cloud Application Server | +| CBS | Central Binding Server | +| CCF | CAPIF Core Function | +| CES | Cloud Enabler Server | +| EDGEAPP | Edge Application | +| EHE | Edge Hosting Environment | +| ENS | Edge Notification Server | +| ER | Edge Repository | +| ETSI | European Telecommunications Standards Institute | +| FCM | Firebase Cloud Messaging | +| HR | Home Routed | +| KI | Key Issue | +| LBO | Local Break Out | +| LCM | Life Cycle Management | +| MANO | MANagement and Orchestration | +| MEC | Multi-access Edge Computing | +| MECAPP | MEC Application | +| MEP | MEC Platform | +| MEF | MEC Federator | +| NAT | Network Address Translators | +| NFV | Network Function Virtualization | +| NSSAI | Network Slice Selection Assistance Information | +| NWDAF | Network Data Analytics Function | +| OAM | Operations, Administration and Management | +| OMA | Open Mobile Alliance | +| PCF | Policy Control Function | +| PFD | Packet Flow Description | +| PSA | PDU Session Anchor | +| RFSP | RAT/Frequency Selection Priority | +| SEAL | Service Enabler Layer Architecture | +| SMF | Session Management Function | +| UDM | User Data Management | +| URSP | UE Route Selection Policy | +| UUID | Universally Unique Identifier | + +# --- 4 Key issues + +## 4.1 Key issue #1: Enhanced notification service to the EEC + +The EEC can be notified with the updated information for edge computing service by EES and ECS over EDGE-1 and EDGE-4, respectively. The notification services available to the EEC (i.e. service provisioning notification, EAS discovery notification, ACR information notification) are specified in release 17, but the details on the notification mechanism is not addressed. In this regard, additional ways (e.g. push notification mechanism and application triggering specified in 3GPP TS 23.501 [5], etc.) of providing the updates to the EEC in real time need to be studied. + +Open issues: + +1. Whether and how the EEC acquires the notification target address or a notification channel URI to receive the notifications? +2. Whether and how EEC, ECS and EES support push notification mechanism. Whether and what additional functional entity is necessary for this? +3. How are the EEC subscriptions and/or notification targets treated in mobility scenario (e.g. during ACR scenario)? +4. Whether and how to utilize application triggering method specified in 3GPP TS 23.501 [5] to provide notifications to the EEC? + +## 4.2 Key issue #2: Enablement of Service APIs exposed by EAS + +As specified in 3GPP TS 23.558 [2] (Rel-17), the Edge Enabler Layer exposes Service APIs towards the EASs. The exposed Service APIs include the capabilities provided by EES as specified in the clause 8.6 of 3GPP TS 23.558 [2] (Rel-17) and the capabilities provided by the 3GPP core network as specified in the clause 8.7 of 3GPP TS 23.558 [2] (Rel-17). + +However, there are several use cases and requirements to exploit Service APIs exposed by EASs (provided by Application service providers) which can be invoked by the other EASs such as Cloud/Edge/Split Rendering in AR/VR use cases; and video content delivery exploiting separate services such as content caching, video encoding/decoding, and video analytics. + +With the enablement of Service APIs exposed by EASs in the Edge Enabler Layer, there may expect several benefits to the involved business roles in the edge computing services. For example, Application service providers may simplify the Edge Application logic by composing the service components provided by the other EASs at the network edge; and open a new business to provide one or more service components to be executed and invoked by the other EASs at the network edge. + +In order to enable the use of Service APIs exposed by EASs in the Edge Enabler Layer, there have been relevant studies in 3GPP TR 23.758 [6] (Rel-17), which result in Sol#15 as follows: + +- Solution #15: Edge Application Server's service APIs publish and discovery using CAPIF: + - The Edge Enabler Server can support edge application (owned by 3rd party or by PLMN operator) access to the service APIs offered by other Edge Application Servers within and across the Edge Data Network by providing CAPIF functions in a distributed or centralized manner. + +Based on the Rel-17 study result, this key issue focuses on addressing the following open issues. + +Open issues: + +1. Identify any gaps in CAPIF to enable EAS Service APIs in the EDGEAPP architecture based on the Sol#15 of 3GPP TR 23.758 [6] (Rel-17). + - In terms of e.g. service-specific attributes for API publish/discovery, API availability subscription/notification across EES/CCF +2. If any, whether and how to enhance CAPIF capabilities to address the gap identified as above? + +## 4.3 Key issue #3: Enhancements to service continuity planning + +In 3GPP TS 23.558 [2], the service continuity planning was specified as part of the Edge Enabler Layer value-add features for supporting seamless service continuity, when information about planned, projected, or anticipated behaviour is available at EESs or provided by EECs. + +This key issue studies potential enhancements to the service continuity planning feature, based on additional criteria for detecting a planned ACR, e.g. the network conditions / analytics monitoring, the DN performance monitoring, the expected/predicted UE route etc. This key issue also studies potential enhancements to the service continuity planning feature to allow the EEC to send a timely ACR request. Finally, the key issue studies scenarios when the planned UE behavior changes after the launch of the service and the ACR needs to be modified due to these changes, e.g. due to UE mobility change. + +Open Issues: + +1. How to rely on the capability of EES/EEC to detect whether the UE moves to the predicted location or not for service continuity planning? +2. Whether and how the EEL can support the determination of the ACR request trigger timing in case of service continuity planning? +3. How to deal with scenarios when the ACR needs to be modified, e.g. due to UE mobility? +4. Whether and what additional capability exposure is required from the 5GS (e.g. NWDAF, OAM) to enhance the service continuity planning? + +5. Potential impact on information exchanged between EAS and EEL. +6. Potential impact on information to communicate within the EEL. + +## 4.4 Key issue #4: EDGE-5 + +According to the latest version of the EDGEAPP specification in 3GPP TS 23.558 [2]: + +"EDGE-5 reference point enables interactions between AC(s) and the EEC." + +That specification also notes: + +"NOTE: Detailed specification of this reference point is out of scope of this release of this specification." + +According to the latest version of the FS\_EDGEAPP specification in 3GPP TR 23.758 [6]: + +"The interactions between Application Client(s) and the Edge Enabler Client in the UE are supported by the EDGE-5 reference point. This reference point supports: + +- Obtaining information about Edge Application Servers that Application Client require to connect; +- Notifications about events related to the connection between Application Clients and their corresponding Edge Application Servers, such as: when an Application Client needs to reconnect to a different Edge Application Server; +- Providing Application Client information (such as its profile) to be used for various tasks such as, identifying the appropriate Edge Application Server instance to connect to; and +- Provide the identity of the desired Edge Application Server to the Edge Enabler Client to enable it to use that identity as a filter when requesting information about Edge Application Servers." + +The necessary functionality of the EDGE-5 interface needs to be studied for Release 18: + +- What functionality should an EEC provide to an AC (see the interactions copied from 3GPP TR 23.758 [6] and the procedures and information flows specified in 3GPP TS 23.558 [2])? + +The following aspects may also need to be studied for Release 18 based upon the provided functionality of the EDGE-5 interface: + +1. Whether the cardinality as currently captured in 3GPP TS 23.558 [2] is to be modified: + +"The following cardinality rules apply for EDGE-5: + +- a) One AC may communicate with only one EEC; and +- b) One EEC may communicate with one or more AC(s) concurrently." + +2. Whether and how an AC can discover available EEC(s)? +3. Whether mutual authentication and authorization between an AC and an EEC is necessary, and if so, how is that accomplished? +4. What APIs should be exposed from an EEC to an AC to support that functionality? +5. Whether a notification mechanism is necessary from an EEC to an AC? +6. Whether and how an AC registers to an EEC? +7. Whether and how an AC de-registers from an EEC? +8. Whether and how an AC detects an abnormal termination of an EEC? +9. Whether and how an EEC detects an abnormal termination of an AC? +10. Whether user's consent is necessary to either AC or EEC operation, and if so, how is it provided? + +11. Whether and how can EDGE-5 support constrained devices with limited capabilities (such as a terminal equipment as defined in TR 21.905) over EDGE-5? One use case may include, for example TE (terminal equipment) has a role of edge device such as AI cameras for object detections or IoT sensors and UE has a role of gateway such as IoT gateway, if UE is vehicle or robotic surgery equipment to operate on a patient. In that case, constrained devices may be connected in large numbers to UE. + +NOTE 1: The aspects of defining end-user consent/authorization over APIs and aspects of mutual authentication and authorization between an AC and an EEC are in the scope of SA3. + +NOTE 2: The aspects of the usage of end-user consent/authorization over APIs is in the scope of SA6. + +## 4.5 Key issue #5: Alignment of EDGEAPP and ETSI MEC + +As described in Annex C of 3GPP TS 23.558 [2] (Rel-17), both EDGEAPP and ETSI MEC can provide support for hosting different edge applications. According to Annex C: "Both EAS and MEC application are application servers and can provide similar application specific functionalities. EAS utilizes the services of EES as specified in this document whereas MEC application utilizes the services provided by MEC platform as specified in ETSI GS MEC 003." As discussed in Annex B.2 of draft GS MEC 003 [3] (v3.0.4), the EES and MEC platform can also be collocated in an implementation. + +While the 3GPP TS 23.558 [2] and ETSI GS MEC 003 [3] provide an initial view about the alignment of the two platforms, this KI intends to address the following: + +1. Study and analyse different deployment options of EDGEAPP and ETSI MEC platforms. +2. Functional architecture and gap analysis between EDGEAPP and ETSI MEC to determine complementary and possibly overlapping APIs and other related functionalities. Annex A captures a comparison of the architectures to facilitate the gap analysis. +3. Recommendation and enhancements based upon the outcome of (1) and (2). + +NOTE 1: Backward compatibility is an important aspect of any recommendations & enhancements and will be considered during the study of this KI. + +NOTE 2: This KI is limited to alignment aspects within 3GPP capabilities. + +## 4.6 Key issue #6: Edge services support across ECSPs + +An edge service or an EAS (e.g. V2X server) can be provided via different EDNs deployed by different ECSPs. Each ECSP may not have the required infrastructure to install the EAS in every EDN due to financial, regulatory and operation constraints. It is assumed that a UE can access the same edge service served by different EASs which are registered to different EESs and deployed by different ECSPs, which have a service level agreement to share edge services. These ECSPs can deploy EESs to serve different PLMNs or different coverages of the same PLMN. A typical scenario is depicted in Figure 4.6-1. + +![Diagram illustrating EAS deployment by different ECSPs. On the left, ECSP_1 (ECS1) is connected to a blue box labeled EDN1. Inside EDN1 are two boxes labeled EAS1 and EAS2, and a box labeled EES1. On the right, ECSP_2 (ECS2) is connected to a light blue box labeled EDN2. Inside EDN2 are two boxes labeled EAS3 and EAS2, and a box labeled EES2. Below both EDN1 and EDN2 are boxes labeled UE, with a large arrow pointing from the UE under EDN1 to the UE under EDN2.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Diagram illustrating EAS deployment by different ECSPs. On the left, ECSP\_1 (ECS1) is connected to a blue box labeled EDN1. Inside EDN1 are two boxes labeled EAS1 and EAS2, and a box labeled EES1. On the right, ECSP\_2 (ECS2) is connected to a light blue box labeled EDN2. Inside EDN2 are two boxes labeled EAS3 and EAS2, and a box labeled EES2. Below both EDN1 and EDN2 are boxes labeled UE, with a large arrow pointing from the UE under EDN1 to the UE under EDN2. + +**Figure 4.6-1 EAS deployed by different ECSPs** + +In Figure 4.6-1, the EAS2 resident in EDN1 and EDN2 provides the same service. The UE may be configured with the ECS1 configuration information (e.g. if the UE is a subscriber of ECSP\_1). It is not clear how to provision the ECS2 configuration information, deployed by ECSP\_2 (a partner of ECSP\_1), to the UE when the UE is out of the service area of EAS2 in ECSP1 and cannot find a suitable EES within ECSP1 to discover and connect to EAS2. The same issue exists when EAS2 becomes unavailable due to other reasons, e.g. overload, or in cases where ECSP\_1 does not deploy EAS2 at all and relies on partner ECSP\_2 to provide the edge service. + +Besides, the UE may have already accessed the EAS2 in the EDN1 and is getting service from that EAS. In that case, it is not clear how to support service continuity due to UE mobility when the UE moves out of the service area of the EAS2 in EDN1 and goes to the service area of the EAS2 in EDN2. + +Furthermore, the target EDN and source EDN are operated by different ECSP which may not have SLA with each other, then the S-EES may not be able to communicate with a T-EES (discovered from ECS) due to lack of SLA. Unfortunately, in Rel17 this failure may only be detect upon EDGE-9 interaction. + +The following study is needed: + +1. Identify potential enhancements to the existing architecture defined in Rel-17 to enable inter-ECSP interactions. +2. Study potential impact to support ECS discovery and service provisioning based on UE location. +3. Whether and how EEC registers with an EES deployed by a partner ECSP? +4. Study potential impact to support service continuity. +5. How is EEC context continuity maintained across ECSPs with or without ACR? +6. How the ECS can discover a T-EES having SLA with S-EES based on the federation agreements between ECSPs before EDGE-9 interaction? + +## 4.7 Key issue #7: Application traffic filter exposure + +3GPP TS 23.558 [2] has specified EDGE-3 exposure with different APIs. The session with QoS API provides the capability for the EAS to influence the QoS for the application traffic via EES. The ACR management event API supports "User plane path change", "ACR monitoring" and "ACR facilitation" and all events support to detect user plane path change for the application traffic. + +The current definition of session with QoS API and ACR management event API only supports simple IP flow description. E.g. in 3GPP TS 23.558 [2], table 8.6.6.3.2-1 IP flow description identifies the application traffic by 3 or 5 tuples. + +**Table 8.6.6.3.2-1: Session with QoS create request** + +| Information element | Status | Description | +|----------------------------------|--------|-----------------------------------------------------------------------------------------| +| EASID | M | The identifier of the EAS | +| Security credentials | M | Security credentials of the EAS | +| UE IP address (NOTE 1) | O | The UE IP address. | +| UE ID (NOTE 1) | O | The identifier of the UE (i.e. GPSI) | +| UE Group ID (NOTE 1) | O | Identifies a group of UEs (i.e. internal group ID or external group ID) | +| IP flow description | M | The IP flow description for the application traffic. | +| Requested QoS reference (NOTE 2) | O | Refers to pre-defined QoS information for the data session between AC and EAS (NOTE 3). | +| ... | ... | ... | + +Only supporting IP flow description in EDGE-3 exposure APIs is not enough. EPS already supported the application traffic (e.g. encrypted application traffic) detection by more filters than IP flow description for the application (e.g. considering in Rel-14 study 3GPP TR 23.721 [7]) and more traffic filters are supported via PFD management procedure as described in 3GPP TS 23.682 [10] and 3GPP TS 23.203 [9], and such capability is also supported in 5GS in 3GPP TS 23.502 [8] and 3GPP TS 23.503 [11] correspondingly. The EEL should provide the same level of traffic filter for identifying the application traffic. + +Open issues: + +1. How to support more application traffic filter for session with QoS API. +2. How to support more application traffic filter for ACR management event API. + +## 4.8 Key issue #8: EAS selection synchronization + +Currently, EAS discovery may result in multiple EASs being discovered for a specific AC. The discovery request may trigger at the EES operations such as dynamic instantiation (3GPP TS 23.558 [2] clause 8.12). However, the EEC may select only one or some of the discovered EASs to enable AC communications or may not begin communications right after a discovery. For a discovered but unselected EAS, operations such as EAS instantiation or state change are unnecessary and inefficient. + +From a different perspective, the registration procedure results in EEC context establishment at EES, with associated service session management. The EES process for determining EAS selection for service sessions is not specified, and there is no method to synchronize this information with the EEC. Moreover, following a registration the EEC does not have EAS endpoint information which could be leveraged for initiating service sessions, although the registration results in reservation of resources in the EDN. + +In another case, many IoT devices are configured for bursty communications at large intervals of time, without service continuity requirements and with many semi-static (e.g. provisioned over-the-top) parameters. For example, a set of EASs may be maintained at the EEC with the expectation of providing signalling optimizations. However, this EEC information cannot be currently leveraged by the system as intended. + +While basic edge functionality can be enabled assuming ideal implementations of an algorithm through which the EES determines that a registered EAS is providing services to an AC, inefficiencies in EAS capability use and enabling service session functionality immediately after registration remain. Hence, it is required to study: + +1. How to enable the EES to accurately determine the EAS(s) capabilities needed by EEC for service sessions in order to perform optimal EAS instantiation operations. +2. Whether and how the service session communications between ACs and EASs can be enabled by the EEC as soon as the EDN capabilities are available after registration. +3. Whether and how to enable the EES to leverage pre-existent EAS information at the EEC in order to enable service session communications efficiently for IoT devices. + +## 4.9 Key issue #9: Enhancement of dynamic EAS instantiation triggering + +In order to ensure efficient utilization of EDN resources for EAS deployment, it should be possible to have the proper number of EAS instances in the EDN to accommodate the load for applications. The dynamic EAS instantiation triggered by the EES is supported in release 17, but further details are not addressed. The EES may invoke EAS dynamic instantiation triggering to the EAS management system, e.g. for considering the service load/capacity of EAS (e.g. number of service session); and for considering the EEC's requesting service characteristics (e.g. location, latency). In this regard, the followings need to be studied further. + +Open issues: + +1. What kind of information can be acquired by edge enabling layer and utilized by an EES to decide to trigger dynamic EAS instantiation and which entities can provide such information to an EES +2. Whether and how to support dynamic EAS termination triggering in order to enable dynamic scaling of EAS (i.e. scale in as needed). + +NOTE: The aspects of the interaction between EES and EAS management system is in the scope of SA5. + +## 4.10 Key issue #10: Support for roaming UEs + +When a UE is roaming in VPLMN, EDN configuration information for edge computing service in VPLMNs may not be available at all ECS deployed in HPLMN (termed H-ECS). The EEC in the UE thus needs to obtain information for V-ECSs (ECS available in VPLMN) to obtain service provisioning information in VPLMN based on the business relationship between HPLMN operator, VPLMN operator, and related ECSP(s). + +In one scenario, the EEC in the roaming UE needs to discover the availability of edge computing services via ECS(s) available in VPLMN. + +In Rel-17, ECS discovery based on VPLMN ID addressed in clause 8.3.2 of 3GPP TS 23.558 [2] do not cover some cases, e.g. when there are multiple available ECSs via the VPLMN for the roaming UE. Therefore, it is required to study ECS discovery in VPLMN and subsequent service provisioning for all relevant deployment models. + +Additionally, it is required to clarify how an EEC hosted in the roaming UE can be authenticated and authorized to access the edge computing services available in the VPLMN. The related requirement is described in GSMA OPG as follows: "Access of roaming subscribers to edge applications in the visited network shall be subject to authorisation by the subscriber's Home OP and the Visited OP". Note that EEC authentication/authorization in Rel-17 is not clarified in roaming situation. It is thus required to study the architectural support necessary for SA3-defined procedures for EEC authentication/ authorization in roaming scenarios. + +The following aspects shall be studied to support roaming UEs: + +1. Roaming-related deployment scenarios (if any) to be supported, and which may be differentiated by: (i) the relationship between the ECS provider and the PLMN operators, (ii) whether connectivity to an ECS can be established in both involved PLMNs. +2. How the EEC in the roaming UE knows the availability of ECS(s) and/or EES(s) and discovers them in the VPLMN? +3. Whether and how edge computing service continuity is supported when transitioning between an HPLMN and VPLMN. +4. How to support authentication and authorization for an EEC hosted in the roaming UE. +5. Whether and how to support topology hiding on inter-PLMN/ECSP interfaces on the edge enabler layer. + +## 4.11 Key issue #11: ACR between EAS and Cloud Application Server + +When a UE moves to a new location, different EASs or Cloud Application Server (CAS) can be more suitable for serving the ACs in the UE. Such transitions can result from a non-mobility event also, requiring support to maintain the continuity of the service. + +This key issue is to support service continuity for ACs in the UE to minimize service interruption while switching the application server between Edge and Cloud. To support service continuity, the application context is transferred between EAS and CAS. + +Rel-17 Edge Computing work is limited to the service continuity between the EAS(s) and identified several scenarios for service continuity. Detailed study is required to enable service continuity between EAS and CAS, covering the following open issues: + +1. Whether and how to detect that ACR is required between EAS and CAS +2. Whether and how to decide that ACR is required between EAS and CAS +3. Whether and how to perform ACR between EAS and CAS +4. Whether and how to perform post ACR actions +5. Whether EEL is required on the cloud deployment and what are the potential impacts to the CAS architecture +6. Whether and what are the impacts of CAS initiated ACR. + +## 4.12 Key issue #12: EEL service differentiation + +The service differentiation in Rel-17 is very general and not detailed (e.g. ECS use local policy to determine service provisioning). Details to enable an ECSP to provide different service quality levels should be specified. Such as a principle based on the role of service consumer. For example, a premium user must get the nearest available edge, or there should be certain applications available only to the premium users and so on. + +Open issues: + +- What service differentiation should be enabled by the EEL? +- Which procedure should be enhanced to support service differentiation? +- Which functional entity is responsible for defining or managing the service differentiation? + +## 4.13 Key issue #13: Edge enabler layer support for EAS synchronization + +It is possible for the ASP to provide EAS (with same service) in different EDNs. For example, a gaming service provider may have deployed game servers in different EDNs to serve its users. It is required for an EAS to synchronize the particular communication session among other EAS(s). In figure 4.13-1, consider: + +- 1) a multi-user gaming session-1 is active between 5 gaming users where 2 users are in EDN1 served by EAS-1X (ASP1), while other 3 users are in EDN2 served by EAS-2X (ASP1); +- 2) at same time (when gaming session-1 is active), another gaming session-2 is also active between different set of users, where some users are in EDN2 served by EAS-2X (ASP1), while other users are in EDN3 served by EAS-3X (ASP1). + +It is required for EAS(s) to synchronize among each other for specific communication session (e.g. multi-user game session) in order to serve the users properly. It is required to study how Edge enabler layer can support EAS from EDN1 to find other EAS(s) in other EDN(s) to synchronize with. + +![Diagram showing three edge nodes (EDN1, EDN2, EDN3) each containing an EAS (EAS-1X, EAS-2X, EAS-3X) and an EES (EES1, EES2, EES3). Each EAS is connected to a UE(s) via an ECS (ECS1, ECS2, ECS3). Dashed arrows indicate synchronization: 'Sync for session-1' between EAS-1X and EAS-2X, and 'Sync for session-2' between EAS-2X and EAS-3X.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates three edge nodes (EDN1, EDN2, EDN3) deployed by the same ASP (ASP1). Each node contains an EAS (EAS-1X, EAS-2X, EAS-3X) and an EES (EES1, EES2, EES3). The EAS is connected to a UE(s) via an ECS (ECS1, ECS2, ECS3). Dashed arrows indicate synchronization: 'Sync for session-1' between EAS-1X and EAS-2X, and 'Sync for session-2' between EAS-2X and EAS-3X. + +Diagram showing three edge nodes (EDN1, EDN2, EDN3) each containing an EAS (EAS-1X, EAS-2X, EAS-3X) and an EES (EES1, EES2, EES3). Each EAS is connected to a UE(s) via an ECS (ECS1, ECS2, ECS3). Dashed arrows indicate synchronization: 'Sync for session-1' between EAS-1X and EAS-2X, and 'Sync for session-2' between EAS-2X and EAS-3X. + +**Figure 4.13-1 EAS (with same service) deployed by same ASP in different EDNs** + +Further, referring to 3GPP TS 23.558 Annex A.4, the application architecture supports SEAL application server functions and Application Enabler Server functions available at the edge. While SEAL application server functions can be made available as an EAS at the edge, it is also possible that certain SEAL application server functions are available either or both at the edge and at the cloud. When the server functions of an application are available both at the edge and at the cloud, there may be a need for interaction between the two corresponding application servers. + +This key issue is to support interaction between the two application server functions deployed at the edge or both at the edge and at the cloud. + +Open issues: + +- 1) Whether and how to enable EAS to find other EAS(s) with multi-user communication session to synchronize? +- 2) Whether and how to enable EAS to find other interested EAS(s) with specific service to synchronize? +- 3) Whether and how to enable EAS to discover and interact with another application server function deployed on the cloud for context synchronization? +- 4) Whether and how edge enabler layer could provide support to EAS synchronization? + +## 4.14 Key issue #14: Application traffic influence for initially selected EAS + +The application traffic is between the AC and EAS and 3GPP CN provides the underlying connectivity for the application traffic. The EEC starts with EAS discovery first in order to offer EAS(s) to AC to start communication with the initially selected EAS. Later on, if the EAS relocation criteria is met, the EAS relocation procedure happens, which consists of EAS discovery, application traffic influence, application context transfer and AC communication with the new EAS. + +Currently, it is not clear in the specification how to influence the application traffic with best optimal user plane routing when initial EAS discovery is completed in the application layer. + +Open issues: + +- Whether and how the EEL can be involved to influence the application traffic routing in AC communication with the initially selected EAS. +- Whether and how EEL configuration information that may influence application traffic routing. +- Which entities can configure or provide information for application traffic influence routing. + +## 4.15 Key issue #15: Support of constrained devices for Edge + +Energy efficiency requirements are relevant for battery driven low-power IoT devices. Those devices may require edge computing services in a local DN for low-latency and employ the SA6 specified edge enablers. + +Clause 6.15 of 3GPP TS 22.261 [12] has provided requirements for energy efficiency for devices, for instance: the 5G system shall support UEs using small rechargeable and single coin cell batteries; and shall support mechanisms to improve battery life for a UE over what is possible in EPS. + +In the existing EDGEAPP architecture as described in TS 23.558 [2], many procedures and services are defined for EEC to interaction with EES/ECS. It is needed to study what impact the support for constrained UE may have on EDGEAPP architecture and what procedure can be improved. + +Open issues: + +- Whether there are any impacts on the EDGEAPP architecture for constrained UE. +- Whether and how the existing EDGEAPP architecture and procedures, for constrained UE to network communication (i.e. EDGE-1 and EDGE-4), e.g. can be improved to reduce power consumption. + +## 4.16 Key issue #16: support of NAT deployed within the edge data network + +In operational deployments of cloud infrastructures including at the edge, Network Address Translation (NAT) are oftentimes deployed. + +Such an operational constraint will prevent the EES to have an IP address of the UE that is known by the underlying 3GPP network. + +Open issue: + +- How the EES can access 3GPP network services pertaining to a UE when the edge data network employs Network Address Translators (NATs). +- How AF specific and temporary UE IDs can be managed at the Edge Enabler Layer? + +## 4.17 Key issue #17: Discovery of a common EAS + +An ASP can deploy several EASs providing the same service in different locations within the EDN. + +For certain use cases involving real-time communication in a multi-user session, both between AC and EAS and between different ACs via the EAS, it may be necessary or beneficial to use services from a single common EAS to meet the strict latency requirements and to avoid the need for inter-EAS synchronization. The use cases may include, for example, a team of robots coordinating together on a manufacturing floor, a team of surgeons using VR headsets and robotic surgery equipment to operate together on a patient, or a group of trucks using V2X for platooning. + +Dependent on the use case, the EEL may apply different additional criteria to determine this common EAS. E.g. it could be desirable to determine the EAS so that the latency for all the ACs in the session is approximately the same or that the latency for a specific AC is minimized. + +![Diagram illustrating several EASs (EAS-1(A), EAS-1(B), EAS-1(C)) deployed in different locations within the same EDN (EDN1). The diagram shows three User Equipment (UE) units (UE1, UE2, UE3) connected to the EDN. UE1 is connected to EES-x, which is connected to EAS-1(A). UE2 is connected to EAS-1(B). UE3 is connected to EES-y, which is connected to EAS-1(C). The EAS units are shown within a light blue box labeled EDN1. An ECS (Edge Controller Server) is shown outside the EDN box.](715219db84ec2a5622d09f9d822b4550_img.jpg) + +Diagram illustrating several EASs (EAS-1(A), EAS-1(B), EAS-1(C)) deployed in different locations within the same EDN (EDN1). The diagram shows three User Equipment (UE) units (UE1, UE2, UE3) connected to the EDN. UE1 is connected to EES-x, which is connected to EAS-1(A). UE2 is connected to EAS-1(B). UE3 is connected to EES-y, which is connected to EAS-1(C). The EAS units are shown within a light blue box labeled EDN1. An ECS (Edge Controller Server) is shown outside the EDN box. + +**Figure 4.17-1 Several EASs (with same service) deployed in different locations in the same EDN** + +Open issues: + +- 1) Whether and how the ACs/EECs of different users can select or be provisioned the same EAS within an EDN? + +**NOTE:** This open issue is dealing with the issue how different EECs can perform EAS discovery so that they select the same EAS within an EDN, whereas KI#13 is dealing with the issue how, after different EECs have selected different EASs located in different EDNs, these EASs can synchronize their contexts. + +- 2) Whether and how the ACs/EECs of different users can select or be provisioned a common EAS, even if initially the EECs are communicating with different EDNs? +- 3) Whether and how the EEL can support service continuity to ensure that when ACs require the use of service from a common EAS and an ACR operation is needed, ACR operations can be coordinated so that upon completion of the ACR operations the ACs again have services provided by a common EAS. + +## 4.18 Key issue #18: EAS bundles + +Rel-17 EEL procedures are designed such that services like EAS discovery and service continuity support are performed per EAS, where individual EASs are uniquely identified using EAS endpoints (e.g. URI, FQDN, IP address). + +However, to provide services to the end user a typical AC communicates with multiple endpoints i.e. multiple EASs. This creates an EAS bundle, which impacts the support provided by the Edge Enabler Layer. Taking an example of an online game where to support large number of users, different game functions are split across multiple servers; like, a game engine for game state and user input management, in-game chat server for communication between players and a capture server for capturing rendered images, encoding, and transporting them to the player's device. If each of these EASs are discovered, controlled, and relocated individually, it may impact the overall quality of service. For e.g. ACR failing for the game engine should cancel the ACR of the capture server to maintain their proximity. + +This key issue is to study the impacts on the EEL's support functions created by such EAS bundles or dependencies between the EASs. + +![Figure 4.18-1 EAS bundle example: A diagram showing an AC (Application Client) connected to a cloud containing three EAS (Edge Application Server) nodes: EAS 1, EAS 2, and EAS 3. Arrows indicate connections from the AC to each EAS node.](163688ca8da9787f5d48edd68d8cc75b_img.jpg) + +Figure 4.18-1 EAS bundle example: A diagram showing an AC (Application Client) connected to a cloud containing three EAS (Edge Application Server) nodes: EAS 1, EAS 2, and EAS 3. Arrows indicate connections from the AC to each EAS node. + +**Figure 4.18-1 EAS bundle example** + +NOTE: This KI does not focus on enabling communication between the EASs, rather, it focuses on coordination at the EEL. + +Open issue: + +- How can the EEL identify EAS bundles? +- What are the impacts on EEL procedures due to EAS bundles e.g. when the bundled EASs are served by the same EES and require ACR due to UE mobility? + +## 4.19 Key issue #19: ACR scenario combination + +Multiple ACR scenarios are specified in 3GPP TS 23.558[2] clause 8.8. Applications can utilize one or more ACR scenarios. Different combinations of utilizing ACR scenarios by Applications should be enabled by the Edge Enabler Layer (e.g. only one ACR scenario allowed or several ACR scenarios allowed). + +Open issues: + +- Whether and how the EEL can support the determination of the ACR scenario for one AC? + +## 4.20 Key issue #20: Supporting composite EASs + +In order for EAS to provide services (weather, transportation, maps, etc.) in partnership with other EASs, EAS context processing and composite EAS support may be required at edge-compatible layers. When ACR occurs due to UE mobility, a method of rearranging the composite EAS context may be required to provide continuous service of the composite EASs. In addition, there may be a need for a method for finding an EAS that provides services to composite EASs within the EDN in which the UE has moved. + +Although EAS can discover and communicate other EAS APIs through CAPIF's functions, but for service continuity, it may be necessary to discover EASs providing composite EASs and relocation the context of EASs that provided composite capabilities. + +![Figure 4.20-1 Composite EAS example: A diagram showing an AC (Application Client) connected to a composite EAS box. Inside the box, EAS 1 is connected to the AC and has arrows pointing to EAS 2, EAS 3, and EAS 4. EAS 2 is connected to EAS 3. This illustrates a composite EAS structure where multiple EAS nodes provide services together to the AC.](826227f3016572a1a1e791c12e2ed86e_img.jpg) + +Figure 4.20-1 Composite EAS example: A diagram showing an AC (Application Client) connected to a composite EAS box. Inside the box, EAS 1 is connected to the AC and has arrows pointing to EAS 2, EAS 3, and EAS 4. EAS 2 is connected to EAS 3. This illustrates a composite EAS structure where multiple EAS nodes provide services together to the AC. + +**Figure 4.20-1 Composite EAS example** + +NOTE: This KI focuses on coordination at the EEL when the composite EASs provide services to the AC on a UE. + +Open issues: + +- Whether and how the EEL can support to composite EAS context management. +- Whether and how the EEL can support the relocation of the composite EAS context for service continuity. +- Whether and how the EEL can discover EAS that provides the services of the composite EASs. + +## 4.21 Key issue #21: Simultaneously EAS connectivity in ACR + +In 3GPP TS 23.548 [19], there is a use case where application client needs to connect to both S-EAS and T-EAS during service continuity. Details are specified in clause 6.3.4 and Annex F of 3GPP TS 23.548 [19]. + +For AC triggered application context relocation, clause 8.8.2.2 of 3GPP TS 23.558 [2] describes the scenario for the service continuity initiated by EEC using regular EAS discovery. In step 5, the EEC and AC jointly decides the T-EAS to be used and in step 8 the AC is triggered by the EEC to start ACT. + +![Sequence diagram illustrating the ACR initiated by the EEC and ACs. The diagram shows four phases: Phase I: ACR Detection, Phase II: ACR Decision, Phase III: ACR Execution, and Phase IV: Post-ACR Clean up. Lifelines include T-EAS, S-EAS, AC, EEC, ECS, T-EES, and S-EES. The process involves UE location update, decision making, service provisioning, T-EAS discovery, T-EAS selection, App Context Relocation Request, EEC context relocation, application signalling and traffic migration, and finally Post-ACR Clean-up.](0c9723d1620cf51bc2b7a380ce7e23c0_img.jpg) + +``` + +sequenceDiagram + participant T-EAS + participant S-EAS + participant AC + participant EEC + participant ECS + participant T-EES + participant S-EES + + Note left of T-EAS: Phase I: ACR Detection + EEC->>AC: 1. UE location update + + Note left of T-EAS: Phase II: ACR Decision + AC->>EEC: 2. Decision + + Note left of T-EAS: Phase III: ACR Execution + EEC->>ECS: 3. Service Provisioning for new location + EEC->>T-EAS: 4. T-EAS discovery + AC->>EEC: 5. T-EAS selection + EEC->>AC: 6. App Context Relocation Request + EEC->>T-EES: 7. EEC context relocation + + Note left of T-EAS: 8. App signalling and traffic migration + Note right of T-EAS: Context migration (Ctxt Id) + Note right of T-EAS: 8b. App traffic + Note right of T-EAS: 8c. App signalling + + Note left of T-EAS: Phase IV: Post-ACR Clean up + AC->>EEC: 9. Post-ACR Clean-up + +``` + +Sequence diagram illustrating the ACR initiated by the EEC and ACs. The diagram shows four phases: Phase I: ACR Detection, Phase II: ACR Decision, Phase III: ACR Execution, and Phase IV: Post-ACR Clean up. Lifelines include T-EAS, S-EAS, AC, EEC, ECS, T-EES, and S-EES. The process involves UE location update, decision making, service provisioning, T-EAS discovery, T-EAS selection, App Context Relocation Request, EEC context relocation, application signalling and traffic migration, and finally Post-ACR Clean-up. + +Figure 4.21-1: ACR initiated by the EEC and ACs + +Figure 4.21-1 illustrates one ACR scenario example in SA6 EDGEAPP. If the AC needs to connect to the T-EAS first to trigger ACT, the AC has two application sessions simultaneously during the service continuity. There could be more ACR scenarios applicable for this type of ACT. There are potential improvements in EEL to facilitate such simultaneous connectivity. For example, whether and how to influence the application traffic to maintain both S-PSA + +and T-PSA during the service continuity and the feature interaction between simultaneous EAS connectivity and service continuity. NOTE: In Rel-17, EES can optimize the user plane routing before AC starts the application signalling with the T-EAS, but that does not consider the need for simultaneous EAS connectivity. + +Open issues: + +- Whether and how EEL can influence the application traffic routing considering the need to maintain both S-PSA and T-PSA for simultaneous connectivity with both S-EAS and T-EAS, during the service continuity. +- What the feature interaction is for simultaneous EAS connectivity and service continuity (including planning). + +## 4.22 Key issue #22: EAS discovery in Edge Node sharing scenario + +Based on GSMA OPG.02 [4] Operator Platform Telco Edge Requirements, Edge Node sharing scenario has been identified in GSMA OPG.02 [4] clause 3.3.5. + +The deployment case is as follows: + +1. OP B deploys application in the OP A (partner OP). OP B wants to scale its services for the region covered by OP A by using OP A's edge infrastructure. +2. User belongs to the OP B. +3. If OP B finds that the most suitable application that can serve the user is available in OP A (partner OP), then OP B requests the edge computing service from OP A (partner OP). + +NOTE 1: The user is referred to the subscribers who have edge service authorizations. + +Based on the deployment case, it is not clear how to discover and determine the EAS(s) deployed in OP A for OP B users. + +![Diagram of the Edge Node sharing scenario. Partner A contains OP A, APP#1, and an Edge Resource. Partner B contains OP B, a Network, and a User device. An IP connection links APP#1 in Partner A to the Network in Partner B. A dashed double-headed arrow connects OP A and OP B. A curved arrow points from OP A to the Edge Resource. A dashed arrow points from the Network to OP B.](84a01685710d24f113b18758ed3c6fcb_img.jpg) + +``` + +graph LR + subgraph Partner_A [Partner A] + OP_A[OP A] + APP1[APP#1] + ER[Edge Resource] + end + subgraph Partner_B [Partner B] + OP_B[OP B] + Network[Network] + User[User] + end + OP_A <--> OP_B + APP1 --- Network + OP_A -- curved arrow --> ER + Network -.-> OP_B + User --> Network + +``` + +Diagram of the Edge Node sharing scenario. Partner A contains OP A, APP#1, and an Edge Resource. Partner B contains OP B, a Network, and a User device. An IP connection links APP#1 in Partner A to the Network in Partner B. A dashed double-headed arrow connects OP A and OP B. A curved arrow points from OP A to the Edge Resource. A dashed arrow points from the Network to OP B. + +Figure 4.22-1 Edge Node sharing scenario + +The following study is needed: + +1. How can EES discover and determine a EAS which allows (subscribers of OP B) to avail its services? +2. Whether EES and EAS of OP A can use OP B's network functions. + +NOTE 2: The key issue assumes OP A and OP B has the same Edge Computing Architecture (i.e. EDGEAPP). + +## 4.23 Key issue #23: Reliable Edge service + +When the Edge services are deployed in a virtualized environments (i.e. built for cloud), it is expected that the overall reliability of the system shall be at least the same as the reliability of non-virtualized system. Therefore, the EDGEAPP service-based architecture as depicted in figure 6.2-1 of 3GPP TS 23.558 [2] should be designed in a way that seamless replacement, addition or removal of services is possible and does not require specific (re-)configuration of both the running and the new component(s). + +The ECS/EES may experience unexpected events (e.g. hardware/link issue in nature disaster) and expected events (e.g. graceful shutdown for maintenance) in service. + +The highly reliable edge computing aims to provide fault tolerance, high availability and service resilience for the application services as well as the application supporting layer. + +This KI focuses on how edge computing (EDGEAPP in SA6) can provide high reliability in EES/ECS and to support highly reliable EAS in SA6 application layer. + +NOTE: SA5 is responsible for the management of 3GPP functions including edge entity LCM and the interactions with ETSI NFV MANO. This is, however, not in the scope of this KI. + +Open issues: + +- Whether and what mechanisms the EES/ECS can use for high reliability in EES/ECS services during expected events and unexpected events in the service. +- Whether and what mechanisms the EES/ECS can provide to support highly reliable EAS during expected events and unexpected events in the service. + +NOTE: The reliability mechanism should make the network changes due to events transparent to the User. + +## 4.24 Key issue #24: SEAL capability access for EEL support + +Annex A.4 of 3GPP TS 23.558 describes deployments of EES with SEAL services and Application Enabler Services as consumers. Based on this description, EES capabilities are available to SEAL servers over the EDGE-3 reference point. + +Annex A.4.2 of 3GPP TS 23.558 describes deployments of SEAL services at the edge, with EASs as consumers. For this case, the re-exposure of SEAL services is designed based on CAPIF implementation by EES. + +EESs may also be a consumers of SEAL services such as location reporting, group management, event monitoring, etc. which are currently exposed via SEAL-S and SEAL-E reference points. New services under development (e.g. ADAES) may also be adopted as SEAL services and may be both consumers and producers of services at the EES. + +Open issues: + +- How EEL accesses and utilizes SEAL capabilities deployed within the EDN. + +# --- 5 Architectural requirements + +## 5.1 General requirements + +### 5.1.1 General + +NOTE: Any additional general architecture requirements shall be added to clause 5.2.1 of 3GPP TS 23.558 [2]. + +## 5.2 Enablement of Service APIs exposed by EAS + +### 5.2.1 General + +This clause specifies the requirements for EAS Service API enablement in the EDGEAPP architecture to address the KI#2 in the clause 4.2. + +### 5.2.2 Requirements + +The following are the architectural requirements to support EAS Service APIs in the EDGEAPP Rel-18 architecture. + +#### 1) EAS capability exposure + +- The application layer architecture shall support exposure of EAS's capabilities to the other EASs. + +#### 2) EAS Service API publication + +- The application layer architecture shall support EAS to publish its exposing Service API information to EES +- The application layer architecture shall support EAS to update the published EAS Service API information on the EES. +- The application layer architecture shall provide mechanisms for the EAS to publish and update KPIs of its Service APIs when available. + +#### 3) EAS Service API discovery + +- The application layer architecture shall provide mechanisms for an EAS to discover available EAS Service APIs. + +#### 4) Subscription service + +- The application layer architecture shall provide subscription and notification mechanisms enabling an EAS to receive changes in dynamic information of EAS Service APIs from an EES. +- The application layer architecture shall provide subscription and notification mechanisms enabling an EAS to receive changes in availability of EAS Service APIs from an EES. + +## 5.3 ECS discovery + +### 5.3.1 General + +This clause specifies the requirements for ECS discovery to address the key issue #6 on edge services support across ECSPs in clause 4.6 and to the key issue #10 on support for roaming UEs in clause 4.10. + +### 5.3.2 Requirements + +The following is the architectural requirement to support ECS discovery in the EDGEAPP Rel-18 architecture. + +- The application layer architecture shall provide mechanisms for ECS to discover available ECS(s) which may have suitable EES(s), to support UE mobility between ECSPs. +- The Edge Enabler Layer architecture shall provide mechanisms for provisioning the EEC with available ECS(s) which may have suitable EES(s), to support UE mobility between ECSPs. + +## 5.4 Alignment of EDGEAPP and ETSI MEC + +### 5.4.1 General + +This clause specifies the architecture requirements for alignment of EDGEAPP and ETSI MEC to address the key issue #4. + +### 5.4.2 Requirements + +The following requirements will serve as the guiding principles for the alignment of EDGEAPP and ETSI MEC architectures. + +1. The scope of 3GPP alignment efforts between EDGEAPP and ETSI MEC shall be limited to architecture enhancements that apply only to EDGEAPP. + +NOTE: 3GPP will liaise with ETSI ISG MEC for architecture recommendation (if any). + +2. The architecture enhancements to support alignment shall ensure backwards compatibility with the existing EDGEAPP architecture. + 3. The architecture enhancements shall not consider to align features exclusive to the each of the EDGEAPP and ETSI MEC architectures, i.e. the architecture enhancements shall only focus on the overlapping aspects between the EDGEAPP and ETSI MEC architectures. The alignment aspects in the present release of this specification includes the following: + - a. alignment of EAS profile (EDGEAPP) and appInfo (ETSI MEC), + - b. alignment of EDGE-3/Mp1 reference points + - c. alignment of EDGE-9/Mp3 reference points + - d. usage of CAPIF between the two architectures +- NOTE: The term alignment does not imply that the reference points will be exact equivalents. +4. The architecture enhancements shall ensure that EDGEAPP architecture can remain as a standalone or a complete system i.e. EDGEAPP can be deployed independent of the ETSI MEC architecture. + 5. The architecture enhancements shall analyse impacts to other working groups e.g. SA2, SA3 and SA5. + +## 5.5 Common EAS + +### 5.5.1 General + +This clause specifies requirements for common EAS discovery, such that a group of ACs can get service from the same EAS. + +### 5.5.2 Requirements + +1. Edge Enabler Layer shall enable a group of application clients to discover a common EAS i.e. same EASID, EAS endpoint and EDN. + - a. The Edge enabler layer shall provide a mechanism to support common EAS selection for a dynamic group. + - b. The Edge enabler layer shall provide a common EAS selection mechanism for a static group. +2. Edge Enabler Layer shall enable a group of application clients to be relocated to a different common EAS. + +NOTE: Relocation to a different common EAS can happen due to several reasons such as EAS unavailability, relocation of all UEs to a new EDN due to mobility etc. + +# --- 6 Enhanced Application Architecture + +## 6.1 Option #1: Roaming architecture + +This clause describes the architecture for roaming UEs, addressing Key Issue #10. + +### 6.1.1 Architecture enhancements + +#### 6.1.1.1 Local breakout roaming architecture: Local breakout to access H-ECS + +This architecture uses ECSs provided in HPLMN and VPLMN, in which the EEC in the UE obtains services from V-ECS and V-EES. In this architecture, the H-ECS is associated with HPLMN, while the V-ECS and the EDN which the UE accesses is associated with VPLMN. A new reference point EDGE-10 is defined between ECSs. Figure 6.1.1.1-1 shows the architecture for this model. + +NOTE: H-ECS and V-ECS can be provided by the same ECSP. + +![Diagram of local breakout roaming architecture showing connections between UE, 3GPP Core Network, Edge Data Network, VPLMN, and HPLMN with various EDGE interfaces.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +This diagram illustrates the local breakout roaming architecture. At the top, a UE (User Equipment) box contains AC (Access Controller) and EEC (Edge Execution Controller) components. The AC is connected to the EEC via EDGE-5. The EEC connects to a central 3GPP Core Network. The AC sends 'Application Data Traffic' to an Edge Data Network. The 3GPP Core Network connects to the Edge Data Network via EDGE-7 (to EAS), EDGE-1, EDGE-2, and EDGE-4. The Edge Data Network contains EAS, EES, and EDGE-9. EAS connects to EES via EDGE-3. EES connects to EDGE-9 via EDGE-6. The 3GPP Core Network also connects to a V-ECS via EDGE-8. A dashed line separates the VPLMN (Visited PLMN) above from the HPLMN (Home PLMN) below. Below the dashed line, another 3GPP Core Network box is shown, which connects to the H-ECS via EDGE-8. The V-ECS connects to the H-ECS via EDGE-10. The H-ECS connects to the bottom 3GPP Core Network via EDGE-4. + +Diagram of local breakout roaming architecture showing connections between UE, 3GPP Core Network, Edge Data Network, VPLMN, and HPLMN with various EDGE interfaces. + +Figure 6.1.1.1-1: Local breakout roaming architecture: Local breakout to access H-ECS + +#### 6.1.1.2 Home-routed EDGE-4 access to H-ECS + +This architecture uses ECSs provided in HPLMN and VPLMN, in which the EEC in the UE obtains services from V-ECS and V-EES. Figure 6.1.1.2-1 shows the architecture for home routed roaming architecture for this model. + +![Diagram of home-routed access to H-ECS, showing a similar architecture to the previous one but with different routing paths for data traffic through the core networks.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +This diagram illustrates the home-routed access to H-ECS architecture. It follows a similar layout to the previous diagram. The UE (containing AC and EEC) connects to a 3GPP Core Network via EDGE-5. The AC sends 'Application Data Traffic' to the Edge Data Network (containing EAS, EES, and EDGE-9) via EDGE-7. The 3GPP Core Network connects to the Edge Data Network via EDGE-1, EDGE-2, and EDGE-4. The EEC connects to the 3GPP Core Network. The 3GPP Core Network also connects to the V-ECS via EDGE-8. A dashed line separates the VPLMN above from the HPLMN below. Below the dashed line, the 3GPP Core Network connects to the H-ECS via EDGE-8. The V-ECS connects to the H-ECS via EDGE-10. The H-ECS connects back to the 3GPP Core Network via EDGE-4. In this architecture, the data traffic from the EEC is routed through the 3GPP Core Network, then through the H-ECS, and finally back to the 3GPP Core Network before reaching the V-ECS. + +Diagram of home-routed access to H-ECS, showing a similar architecture to the previous one but with different routing paths for data traffic through the core networks. + +Figure 6.1.1.2-1: Home-routed access to H-ECS + +In the HR roaming scenario, the roaming architecture is valid if the UE is supported to access the EDN in the VPLMN (i.e. the local access to the EDN of the VPLMN is supported in the HR roaming scenario). The traffic toward the EDN in the VPLMN (i.e. EDGE-1 traffic and application data traffic between AC and EAS) is not home routed to the HPLMN while the traffic between the EEC and H-ECS over is home routed via VPLMN and HPLMN. + +NOTE: How to support local access to the EDN for the VPLMN in HR roaming scenarios is SA2's responsibility. + +### 6.1.2 Identities + +None. + +### 6.1.3 Cardinality rules + +None. + +## 6.2 Option #2: Non-roaming architecture + +This clause describes the architecture for non-roaming UEs. + +### 6.2.1 Architecture enhancements + +Compared with the Rel-17 EDGEAPP architecture for the non-roaming scenario, a new reference point EDGE-10 is defined between ECSs. Figure 6.2.1-1 shows the architecture for this model. + +NOTE: ECSs communicating via EDGE-10 may be provided by different ECSPs. + +![Diagram of Non-roaming architecture showing UE, AC, EEC, 3GPP Core Network, Edge Data Network, EAS, EES, and ECS components and their interfaces.](ee8536b235eb6aad21e2048fd5308900_img.jpg) + +The diagram illustrates the non-roaming architecture. On the left, a 'UE' (User Equipment) box contains 'AC' (Application Controller) and 'EEC' (Edge Enabler Client). 'AC' is connected to 'EDGE-5', which in turn connects to the '3GPP Core Network'. 'EEC' is also connected to the '3GPP Core Network'. The '3GPP Core Network' is connected to the 'Edge Data Network' on the right. 'EDGE-7' connects 'AC' to 'EAS' (Edge Application Server) in the 'Edge Data Network'. 'EDGE-1' and 'EDGE-2' connect the '3GPP Core Network' to 'EES' (Edge Enabler Server) in the 'Edge Data Network'. 'EDGE-4' and 'EDGE-8' connect the '3GPP Core Network' to 'ECS' (Edge Configuration Server) in the 'Edge Data Network'. 'EDGE-3' connects 'EAS' to 'EES'. 'EDGE-6' connects 'EES' to 'ECS'. 'EDGE-9' is an interface on 'EES', and 'EDGE-10' is an interface on 'ECS'. A large arrow labeled 'Application Data Traffic' points from 'AC' to 'EAS'. + +Diagram of Non-roaming architecture showing UE, AC, EEC, 3GPP Core Network, Edge Data Network, EAS, EES, and ECS components and their interfaces. + +Figure 6.2.1-1: Non-roaming architecture + +### 6.2.2 Identities + +None. + +### 6.2.3 Cardinality rules + +None. + +## 6.3 Option #3: Edge Notification Server architecture + +This clause provides an enhanced application architecture based on Rel-17 architecture by incorporating an Edge Notification Server addressing Key Issue #1, "Enhanced notification service to the EEC". + +### 6.3.1 Architecture enhancements + +This clause describes the new Edge Notification Server (ENS) functional element and the new interfaces (i.e EDGE-11, EDGE-12 and EDGE-13) needed to enable interactions in between EEC-ENS, EES-ENS and ECS-ENS respectively. + +Figure 6.3.1-1 illustrates the reference point representation of the architecture for Edge Enabling Application with the inclusion of the Edge Notification Server and the reference points EDGE-11, EDGE-12 and EDGE-13. The Figure also shows an OEM Push server which is outside of the PLMN. + +NOTE 1: The OEM Push server and the Push Function in the UE, as shown in Figure 6.3.1-1, are outside the scope of this TR and SA6. + +NOTE 2: The details of communication between the ENS and the OEM Push server is outside the scope of this TR and SA6. + +![Figure 6.3.1-1: Enhanced architecture using an Edge Notification Server. The diagram shows the interaction between a UE, 3GPP Core Network, and Edge Data Network. The UE contains an Application Client(s), an Edge Enabler Client, and a Push Function. The 3GPP Core Network is the central transit area. The Edge Data Network contains Edge Application Server(s), Edge Enabler Server(s), Edge Configuration Server, and Edge Notification Server. Interfaces are labeled EDGE-1 through EDGE-13. A dashed line separates the PLMN (UE, Core Network, and ENS) from the OEM Push Server outside the PLMN.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +The diagram illustrates the enhanced architecture for Edge Enabling Application. It is divided into three main components: UE, 3GPP Core Network, and Edge Data Network. The UE contains an Application Client(s), an Edge Enabler Client, and a Push Function. The 3GPP Core Network is the central transit area. The Edge Data Network contains Edge Application Server(s), Edge Enabler Server(s), Edge Configuration Server, and Edge Notification Server. Interfaces are labeled as follows: EDGE-1 (between UE and Edge Enabler Server), EDGE-2 (between 3GPP Core Network and Edge Enabler Server), EDGE-3 (between Edge Application Server(s) and Edge Enabler Server), EDGE-4 (between UE and Edge Configuration Server), EDGE-5 (between Application Client(s) and Edge Enabler Client), EDGE-6 (between Edge Enabler Server and Edge Configuration Server), EDGE-7 (between Application Client(s) and Edge Application Server(s)), EDGE-8 (between 3GPP Core Network and Edge Configuration Server), EDGE-9 (between Edge Enabler Server and Edge Configuration Server), EDGE-11 (between UE and Edge Notification Server), EDGE-12 (between Edge Enabler Server and Edge Notification Server), and EDGE-13 (between Edge Configuration Server and Edge Notification Server). A dashed line labeled PLMN separates the internal network components from the OEM Push Server, which is outside the PLMN and connected to the Edge Notification Server. + +Figure 6.3.1-1: Enhanced architecture using an Edge Notification Server. The diagram shows the interaction between a UE, 3GPP Core Network, and Edge Data Network. The UE contains an Application Client(s), an Edge Enabler Client, and a Push Function. The 3GPP Core Network is the central transit area. The Edge Data Network contains Edge Application Server(s), Edge Enabler Server(s), Edge Configuration Server, and Edge Notification Server. Interfaces are labeled EDGE-1 through EDGE-13. A dashed line separates the PLMN (UE, Core Network, and ENS) from the OEM Push Server outside the PLMN. + +**Figure 6.3.1-1: Enhanced architecture using an Edge Notification Server** + +NOTE 3: ENS is an optional feature of the EDGEAPP architecture. + +#### 6.3.1.1 Edge Notification Server (ENS) + +ENS is the optional central notification server which receives notifications from EES (EDGE-12) and ECS (EDGE-13) and based on the preferred notification delivery method indicated by EEC (over EDGE-11), delivers the notifications to EEC through either a Pull or a Push delivery method. + +Functionalities of ENS are: + +- Enabling EEC to request for a Callback URL to be used in its event subscription creation with EES and ECS; + +- b) Enabling EEC to request for an optional Channel URL to receive notifications from the ENS directly (e.g. via Long-polling or WebSocket); +- c) Enabling EEC to request receiving notifications from the ENS indirectly through a preferred Push server (e.g. FCM, APNS, OMA Push); +- d) Setting up a Pull or Push notification channel with EEC based on EEC's preferred notification delivery method (e.g. Long-polling, WebSocket) requested; +- e) Receiving Notifications from EES and ECS at the Callback URL and passing them onto the EEC either over a notification Channel (e.g. Long-polling, WebSocket) which is setup directly with the EEC or indirectly (i.e. an implicit notification channel) via a Push server (e.g. FCM, APNS, OMA Push); + +#### 6.3.1.2 ENS Discovery + +For a given EEC, the associated ENS's information (e.g. URI(s), FQDN(s), IP address(es)) and optionally the ENS Provider Identifier are obtained from the ECS as part of the initial provisioning activity (see clause 8.3 in 23.558). + +This approach ensures regardless of how many EECs a UE has or how many ENSs are deployed in the network (e.g. one ENS per ECSP or a single ENS by MNO), a given EEC would always receive the appropriate ENS endpoint to communicate and open a notification channel with. + +NOTE 1: Depending on the number of EECs (in the UE) and the number of associated ENS(s) in the network (i.e. one ENS per ECSP or a single ENS by MNO), an UE may simultaneously interact with multiple ENSs (one per ECSP) or a single ENS deployed by the MNO. + +## 6.4 Option #4: Constrained devices with limited capabilities + +### 6.4.1 Architecture enhancements + +#### 6.4.1.1 General + +This architecture option adds support for certain constrained devices which either don't have enough capabilities to execute its own EEC (e.g. the constrained device may not have a Mobile Termination entity) or do not execute its own EEC to save essential resources such as processing power and battery. Such constrained devices (e.g. terminal equipments as defined in TR 22.944 [21]) will benefit by being able to utilize services of an EEC running on a different UE, using EDGE-5. + +#### 6.4.1.2 Architecture + +![Figure 6.4.1.2-1: Architecture supporting constrained devices. The diagram shows three main components: UE, 3GPP Core Network, and Edge Data Network. The UE contains 'Application Client(s)' and an 'Edge Enabler Client'. The 3GPP Core Network is a central block. The Edge Data Network contains 'Edge Application Server(s)', 'Edge Enabler Server(s)', and an 'Edge Configuration Server'. A separate 'TE' (Terminal Equipment) box contains 'Application Client(s)'. Arrows labeled with EDGE interfaces connect these components: EDGE-5 between UE and TE; EDGE-7 between UE and Edge Application Server(s); EDGE-1 and EDGE-2 between UE and Edge Enabler Server(s); EDGE-4 and EDGE-8 between UE and Edge Configuration Server; EDGE-3 between Edge Application Server(s) and Edge Enabler Server(s); EDGE-6 between Edge Enabler Server(s) and Edge Configuration Server; and EDGE-9 between Edge Enabler Server(s) and the Edge Data Network boundary. A double-headed arrow labeled 'Application Data Traffic' connects the UE's Application Client(s) to the Edge Application Server(s).](0019f09403376d6444ee323591fa2e98_img.jpg) + +Figure 6.4.1.2-1: Architecture supporting constrained devices. The diagram shows three main components: UE, 3GPP Core Network, and Edge Data Network. The UE contains 'Application Client(s)' and an 'Edge Enabler Client'. The 3GPP Core Network is a central block. The Edge Data Network contains 'Edge Application Server(s)', 'Edge Enabler Server(s)', and an 'Edge Configuration Server'. A separate 'TE' (Terminal Equipment) box contains 'Application Client(s)'. Arrows labeled with EDGE interfaces connect these components: EDGE-5 between UE and TE; EDGE-7 between UE and Edge Application Server(s); EDGE-1 and EDGE-2 between UE and Edge Enabler Server(s); EDGE-4 and EDGE-8 between UE and Edge Configuration Server; EDGE-3 between Edge Application Server(s) and Edge Enabler Server(s); EDGE-6 between Edge Enabler Server(s) and Edge Configuration Server; and EDGE-9 between Edge Enabler Server(s) and the Edge Data Network boundary. A double-headed arrow labeled 'Application Data Traffic' connects the UE's Application Client(s) to the Edge Application Server(s). + +Figure 6.4.1.2-1: Architecture supporting constrained devices + +NOTE 1: The architecture option should utilize existing functionalities specified by SA2 and avoid creating new requirements for system architecture. + +NOTE 2: How the TE communicates with the UE (e.g. Bluetooth, Wi-Fi, Cellular, ProSe, LPWA, zigBee, wired connection etc.) is out of scope of SA6. + +### 6.4.2 Identities + +None. + +### 6.4.3 Cardinality rules + +None. + +## 6.5 Option #5: Architecture for ACR between EAS and CAS without CES + +This clause describes the architecture for enabling interactions between EAS and Cloud Application Server (CAS), addressing Key Issue #11. + +### 6.5.1 Architecture enhancements + +Figure 6.5.1-1 shows the architecture enabling interactions between EAS and CAS, without Cloud Enabler Server (CES). Compared to the EDGEAPP (Rel-17) architecture, new entity Cloud Application Server is proposed along with the new reference points EDGE-14 (between EES and CAS), EDGE-15 (between ECS and CAS) and EDGE-16 (between 3GPP Core Network and CAS). + +![Figure 6.5.1-1: Architecture with Cloud Application Server (CAS) and without CES. The diagram shows the interaction between a UE, 3GPP Core Network, Cloud Application Server(s), Edge Application Server(s), Edge Enabler Server(s), Edge Data Network, and Edge Configuration Server. Key reference points include EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, EDGE-14, EDGE-15, and EDGE-16. Application Data Traffic is shown flowing between the UE and the Cloud Application Server(s) via EDGE-16, and between the Edge Application Server(s) and the Cloud Application Server(s) via EDGE-14.](f20786b603b41e24b5d5899f710b5947_img.jpg) + +The diagram illustrates the architecture for Option #5. On the left, the UE contains an 'Application Client(s)' and an 'Edge Enabler Client'. The 'Application Client(s)' connects to the '3GPP Core Network' and has a bidirectional 'Application Data Traffic' connection to the 'Cloud Application Server(s)' via the 'EDGE-16' reference point. The 'Edge Enabler Client' connects to the '3GPP Core Network' via 'EDGE-5'. The '3GPP Core Network' connects to the 'Edge Data Network' via 'EDGE-1' and 'EDGE-2'. The 'Edge Data Network' contains 'Edge Enabler Server(s)' and 'Edge Application Server(s)'. The 'Edge Enabler Client' connects to the 'Edge Enabler Server(s)' via 'EDGE-4'. The 'Edge Enabler Server(s)' connects to the 'Edge Data Network' via 'EDGE-3' and 'EDGE-9'. The 'Edge Application Server(s)' connects to the 'Edge Data Network' via 'EDGE-6'. The 'Edge Application Server(s)' has a bidirectional 'Application Data Traffic' connection to the 'Cloud Application Server(s)' via the 'EDGE-14' reference point. The 'Cloud Application Server(s)' connects to the 'Edge Data Network' via the 'EDGE-15' reference point. The 'Edge Configuration Server' connects to the 'Edge Data Network' via 'EDGE-8' and to the 'Edge Enabler Server(s)' via 'EDGE-9'. + +Figure 6.5.1-1: Architecture with Cloud Application Server (CAS) and without CES. The diagram shows the interaction between a UE, 3GPP Core Network, Cloud Application Server(s), Edge Application Server(s), Edge Enabler Server(s), Edge Data Network, and Edge Configuration Server. Key reference points include EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, EDGE-14, EDGE-15, and EDGE-16. Application Data Traffic is shown flowing between the UE and the Cloud Application Server(s) via EDGE-16, and between the Edge Application Server(s) and the Cloud Application Server(s) via EDGE-14. + +**Figure 6.5.1-1: Architecture with Cloud Application Server (CAS) and without CES** + +In this solution, the Cloud Application Server (CAS) interaction with EES is supported via EDGE-14 reference point and CAS is supported by ECS via EDGE-15 reference point. The CAS and EAS interaction is supported as Application Data Traffic, which is out-of-scope of this specification. The CAS interaction with the 3GPP core network happens over EDGE-16 reference point, which is similar to EDGE-7 reference point. + +NOTE: What functionalities of EDGE-9 and EDGE-6 are to be reused for EDGE-14 and EDGE-15 respectively will be addressed in normative phase. + +Since the EAS may have service area restriction, once the UE is moving out of the current edge coverage, to keep service continuity, the application client needs to connect to either another EAS in new EDN or the CAS. + +The architecture supports ACR between edge and cloud deployments for the following conditions: + +- Condition 1: For the locations where EDN is not available, the ACR support is based on the failed Service provisioning response (i.e. the non-availability of the EDN at a particular location) from the ECS. +- Condition 2: When AC profiles are sent in Service provisioning request and particular EAS is not available then EDN non-availability for that EAS is inferred through Service provisioning response. +- Condition 3: For the locations where EDN is available but the EAS is not available, the ACR support is based on the indication from the EES (in the EAS discovery response) about the non-availability of the EAS at that particular location. +- Condition 4: EAS and EDN are available but EAS is overloaded or not in a position to serve the EEC/UE due to any reason. +- Condition 5: For a UE location, when CAS is serving and a suitable EAS is available at the edge, ACR can be initiated for continuing the service delivery via EAS. + +### 6.5.2 Identities + +None. + +### 6.5.3 Cardinality rules + +None. + +## 6.6 Option #6: Architecture for ACR between EAS and CAS with CES + +### 6.6.1 Architecture enhancements + +![Figure 6.6.1-1: Illustration of application architecture with Edge and Cloud server deployment. The diagram shows three main network domains: UE (User Equipment), 3GPP Core Network, and Cloud Data Network. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP Core Network contains an Edge Data Network with Edge Application Server(s), Edge Enabler Server(s), and Edge Configuration Server. The Cloud Data Network contains Cloud Application Server(s) and Cloud Enabler Server(s). Arrows indicate 'Application Data Traffic' flows between the UE and the Edge Data Network, and between the Edge Data Network and the Cloud Data Network. Various reference points (EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, EDGE-1', EDGE-2', EDGE-3', EDGE-6', EDGE-7', EDGE-9') are labeled on the interfaces between the components.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +Figure 6.6.1-1: Illustration of application architecture with Edge and Cloud server deployment. The diagram shows three main network domains: UE (User Equipment), 3GPP Core Network, and Cloud Data Network. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP Core Network contains an Edge Data Network with Edge Application Server(s), Edge Enabler Server(s), and Edge Configuration Server. The Cloud Data Network contains Cloud Application Server(s) and Cloud Enabler Server(s). Arrows indicate 'Application Data Traffic' flows between the UE and the Edge Data Network, and between the Edge Data Network and the Cloud Data Network. Various reference points (EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, EDGE-1', EDGE-2', EDGE-3', EDGE-6', EDGE-7', EDGE-9') are labeled on the interfaces between the components. + +**Figure 6.6.1-1: Illustration of application architecture with Edge and Cloud server deployment** + +In this solution, the Cloud Application Server (CAS) is supported by Cloud Enabler Server (CES) via EDGE-3' reference point and CES is supported by ECS via EDGE-6' reference point. The CES communicates with EES or another CES via EDGE-9' reference point. The EEC utilizes EDGE-1' reference point to communicate with the CES. The CES and CAS interact with 3GPP Core Network via EDGE-7' reference point and EDGE-2' reference point, respectively. + +From concept wise, the CAS and CES are servers deployed in a cloud data network and EAS and EES are servers deployed in an edge data network. If certain EAS and EES in the edge data network are capable of supporting more UEs than regular edge server and can serve UE from anywhere (N6 routable), their roles become those of CAS and CES, respectively. + +The EDGE prime reference points have the similar functions as the existing EDGE reference points. For instance, CASs are registered via EDGE-3' in CES to enable CES to offer suitable CAS via EDGE-1' to EEC; and CESs are registered via EDGE-6' in ECS to enable ECS to offer suitable CES via EDGE-4 to EEC. + +The differences in EDGE prime reference points comparing to existing EDGE reference points are: + +- The CAS does not have service area restriction in CAS profile when registered into CES. +- The CES does not have service area restriction in CES profile when registered into ECS. + +NOTE: The detailed differences for EDGE prime reference points and the cardinality rules will be addressed in normative phase. + +### 6.6.2 Identities + +None. + +### 6.6.3 Cardinality rules + +None. + +## 6.7 Option #7: Architecture for Common EAS selection with central binding server + +### 6.7.1 Architecture enhancements + +![Diagram of EDGEAPP architecture enhanced with binding server. The diagram shows three main components: UE, 3GPP Core Network, and Edge Data Network. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP Core Network is represented by a central vertical bar. The Edge Data Network contains Edge Application Server(s), Edge Enabler Server(s), and Edge Configuration Server. A Central Binding Server is shown outside the Edge Data Network. Arrows indicate traffic flow: Application Data Traffic from UE to Edge Application Server(s) via EDGE-7. Other reference points are: EDGE-5 (UE internal), EDGE-1 (UE to Edge Enabler Server), EDGE-2 (UE to Edge Enabler Server), EDGE-4 (UE to Edge Configuration Server), EDGE-8 (UE to Edge Configuration Server), EDGE-3 (Edge Application Server to Edge Enabler Server), EDGE-9 (Edge Enabler Server internal), EDGE-6 (Edge Enabler Server to Edge Configuration Server), and EDGE-17 (Edge Enabler Server to Central Binding Server).](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +Diagram of EDGEAPP architecture enhanced with binding server. The diagram shows three main components: UE, 3GPP Core Network, and Edge Data Network. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP Core Network is represented by a central vertical bar. The Edge Data Network contains Edge Application Server(s), Edge Enabler Server(s), and Edge Configuration Server. A Central Binding Server is shown outside the Edge Data Network. Arrows indicate traffic flow: Application Data Traffic from UE to Edge Application Server(s) via EDGE-7. Other reference points are: EDGE-5 (UE internal), EDGE-1 (UE to Edge Enabler Server), EDGE-2 (UE to Edge Enabler Server), EDGE-4 (UE to Edge Configuration Server), EDGE-8 (UE to Edge Configuration Server), EDGE-3 (Edge Application Server to Edge Enabler Server), EDGE-9 (Edge Enabler Server internal), EDGE-6 (Edge Enabler Server to Edge Configuration Server), and EDGE-17 (Edge Enabler Server to Central Binding Server). + +**Figure 6.7.1-1: EDGEAPP architecture enhanced with binding server** + +The EDGE-17 reference point is introduced to support EES interaction with binding server. The EES can store, update and remove the binding information via EDGE-17 reference point. + +The binding server is deployed in a central cloud and it is a single server maintaining binding information. + +NOTE 1: Whether binding server can be deployed in EDN can be considered during normative. + +NOTE 2: CBS can be co-located with an ECS in a deployment. + +### 6.7.2 Identities + +None. + +### 6.7.3 Cardinality rules + +None. + +## 6.8 Option #8: Architecture for ACR update in service continuity planning + +### 6.8.1 Architecture enhancements + +Enhancement of the service continuity planning capability is expected to support update of ACR. As can be seen at the Figure 7.6.1-1, this solution proposes the ACR update capabilities as enhancements after the ACR launch to deal with UE behavior changes. This includes a Detection entity, a Decision Update entity and an ACR update execution entity. These entities can be different based on the scenarios identified in TS 23.558, clause 8.8.2. + +![Figure 6.8.1-1: high level illustration of proposed service continuity planning enhancements. The diagram shows a sequence of steps: Detection, Decision, EAS Discovery, T-EAS Selection, ACR launch, ACR execution, EEC Context Relocation, ACT, and Post-ACR Clean-up. Above the ACR execution step, a dashed box labeled 'Proposed enhancements to Service Continuity Planning service' contains Detection, Decision Update, and ACR Update. An arrow labeled 'ACR modification' points from the ACR Update box to the ACR execution step.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The diagram illustrates a sequence of steps for service continuity planning. The main sequence consists of: Detection, Decision, EAS Discovery, T-EAS Selection, ACR launch, ACR execution, EEC Context Relocation, ACT, and Post-ACR Clean-up. Above the ACR execution step, a dashed box labeled 'Proposed enhancements to Service Continuity Planning service' contains three sub-steps: Detection, Decision Update, and ACR Update. An arrow labeled 'ACR modification' points from the ACR Update box to the ACR execution step. + +Figure 6.8.1-1: high level illustration of proposed service continuity planning enhancements. The diagram shows a sequence of steps: Detection, Decision, EAS Discovery, T-EAS Selection, ACR launch, ACR execution, EEC Context Relocation, ACT, and Post-ACR Clean-up. Above the ACR execution step, a dashed box labeled 'Proposed enhancements to Service Continuity Planning service' contains Detection, Decision Update, and ACR Update. An arrow labeled 'ACR modification' points from the ACR Update box to the ACR execution step. + +Figure 6.8.1-1: high level illustration of proposed service continuity planning enhancements + +### 6.8.2 Identities + +None. + +### 6.8.3 Cardinality rules + +None. + +## 6.9 Option #9: EEL utilization of SEAL services deployed in EDN + +### 6.9.1 Architecture enhancements + +![Figure 6.9.1-1: EEL utilization of SEAL services deployed in EDN. The diagram shows the architecture involving UE, Edge Data Network, and 3GPP network system. The UE contains an Application specific client, Edge Enabler Client, and SEAL clients. The Edge Data Network contains an Application Specific Server (as EAS), Edge Enabler Server(s), and SEAL Server(s). The 3GPP network system is shown as a central component. Interfaces are labeled: VAL-UU, EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, SEAL-UU, SEAL-C, SEAL-S, and 3GPP Interfaces.](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) + +The diagram shows the architecture for EEL utilization of SEAL services deployed in EDN. It is divided into three main components: UE, Edge Data Network, and 3GPP network system. The UE contains an Application specific client, Edge Enabler Client, and SEAL clients. The Edge Data Network contains an Application Specific Server (as EAS), Edge Enabler Server(s), and SEAL Server(s). The 3GPP network system is shown as a central component. Interfaces are labeled: VAL-UU, EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, SEAL-UU, SEAL-C, SEAL-S, and 3GPP Interfaces. The diagram also shows the interaction between the UE and the Edge Data Network through the 3GPP network system. + +Figure 6.9.1-1: EEL utilization of SEAL services deployed in EDN. The diagram shows the architecture involving UE, Edge Data Network, and 3GPP network system. The UE contains an Application specific client, Edge Enabler Client, and SEAL clients. The Edge Data Network contains an Application Specific Server (as EAS), Edge Enabler Server(s), and SEAL Server(s). The 3GPP network system is shown as a central component. Interfaces are labeled: VAL-UU, EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, SEAL-UU, SEAL-C, SEAL-S, and 3GPP Interfaces. + +Figure 6.9.1-1: EEL utilization of SEAL services deployed in EDN + +This architecture illustrates the deployment scenario specified in key issue #24. Vertical application layer server(s) and SEAL server(s) are deployed in EDN. The EES consumes SEAL services deployed in EDN over SEAL-S reference point. The EEC consumes the services from SEAL client(s) over SEAL-C reference point. The EEC consumes the services from SEAL client(s) over SEAL-C reference point. + +### 6.9.2 Identities + +None. + +### 6.9.3 Cardinality rules + +None. + +## 6.10 Option #10: EDGEAPP architecture in edge node sharing + +### 6.10.1 Architecture enhancements + +The solution addresses how to discover an EAS that is deployed in the partner's OP (i.e. OP-A) in edge node sharing case and is based on architecture enhancement in EDGEAPP with ECS-ER (Edge Repository). + +Figure 6.10.1-1 shows two operator platforms can communicate with each other via EDGE-9 and EDGE-18, EEC in UE communicates with EES and ECS of OP-B and EAS is registered in EES of OP-A via EDGE-3. EDGE-18 is a new reference point used between ECS-ERs. + +![Diagram of EDGEAPP architecture in edge node sharing showing UE, Operator platform B, and Operator platform A with their internal components and reference points.](aa9441a5971655a79987d70fc551b26a_img.jpg) + +The diagram illustrates the EDGEAPP architecture in edge node sharing across three main entities: UE, Operator platform B, and Operator platform A. + +- UE (User Equipment):** Contains an **Application Client(s)** and an **Edge Enabler Client**. The Application Client(s) is connected to the Edge Enabler Client via **EDGE-5**. The Edge Enabler Client is connected to Operator platform B via **EDGE-1** and **EDGE-4**. +- Operator platform B:** Contains an **Edge Enabler Server(s)**, an **Edge Configuration Server**, and an **ECS-Edge Repository**. The Edge Enabler Server(s) is connected to the Edge Configuration Server via **EDGE-6**. The Edge Configuration Server is connected to the ECS-Edge Repository via **EDGE-10**. The Edge Enabler Server(s) is connected to Operator platform A via **EDGE-9**. The ECS-Edge Repository is connected to Operator platform A via **EDGE-18**. +- Operator platform A:** Contains an **Edge Application Server(s)**, an **Edge Enabler Server(s)**, an **Edge Configuration Server**, and an **ECS-Edge Repository**. The Edge Application Server(s) is connected to the Edge Enabler Server(s) via **EDGE-3**. The Edge Enabler Server(s) is connected to the Edge Configuration Server via **EDGE-6**. The Edge Configuration Server is connected to the ECS-Edge Repository via **EDGE-10**. + +Diagram of EDGEAPP architecture in edge node sharing showing UE, Operator platform B, and Operator platform A with their internal components and reference points. + +Figure 6.10.1-1: EDGEAPP architecture in edge node sharing + +### 6.10.2 Identities + +None. + +### 6.10.3 Cardinality rules + +None. + +## 6.11 Option #11: EDGEAPP architecture enhanced with Central AC Association Repository + +### 6.11.1 Architecture enhancements + +As described in clause 7.27.0, multiple options for the implementation of this solution are provided. Option (ii) relies on the introduction of new functionality termed Central AC Association Repository (CAAR). CAAR functionality can be implemented by ECS or as an independent CAAR server. + +This clause introduces architectural enhancements based on the assumption that the SP deploys an independent server which hosts the CAAR functionality, and which communicates with multiple ECSs and each of the EESs serving Common EAS groups. + +NOTE 1: The architectural enhancement introduced in this clause is optional. It can be used for the option "with CAAR" (ii) (as described in clause 7.27.0). CAAR functionality can be integrated with ECS. + +![Diagram of EDGEAPP architecture enhanced with Central AC Association Repository (CAAR).](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +The diagram illustrates the architecture for EDGEAPP enhanced with a Central AC Association Repository (CAAR). It shows three main components: UE (User Equipment), 3GPP Core Network, and Edge Data Network. The UE contains 'Application Client(s)' and an 'Edge Enabler Client'. The 3GPP Core Network is a central block. The Edge Data Network contains 'Edge Application Server(s)', 'Edge Enabler Server(s)', and an 'Edge Configuration Server'. The CAAR is shown as a separate box on the right. Reference points are labeled as follows: EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, EDGE-19, and EDGE-20. Arrows indicate data flow: 'Application Data' from UE to Edge Application Server(s); EDGE-7 between UE and Edge Application Server(s); EDGE-1 between UE and Edge Enabler Server(s); EDGE-2 between UE and Edge Enabler Server(s); EDGE-4 between UE and Edge Configuration Server; EDGE-8 between UE and Edge Configuration Server; EDGE-3 between Edge Application Server(s) and Edge Enabler Server(s); EDGE-9 between Edge Enabler Server(s) and Edge Configuration Server; EDGE-19 between Edge Enabler Server(s) and CAAR; EDGE-6 between Edge Configuration Server and CAAR; and EDGE-20 between Edge Configuration Server and CAAR. + +Diagram of EDGEAPP architecture enhanced with Central AC Association Repository (CAAR). + +**Figure 6.11.1-1: EDGEAPP architecture enhanced with Central AC Association Repository** + +The EDGE-19 reference point is introduced to support EES interaction with a Central AC Association Repository (CAAR). The EES can store, update, and remove information about the AC associations it provides services to via EDGE-19 reference point. + +The EDGE-20 reference point is introduced to support ECS interaction with CAAR. The ECS can query the AC association information via EDGE-20 reference point. + +NOTE 2: It is to be determined in the normative phase whether CAAR and Binding Server from solution #30 can be merged. + +### 6.11.2 Identities + +None. + +### 6.11.3 Cardinality rules + +None. + +## 6.12 Option #12: Architecture for Federation and Roaming + +### 6.12.0 Assumptions + +This solution assumes the following: + +1. PLMN subscription for edge computing services between the user and the MNO may not be restricted to only certain edge services or applications. +2. Edge service authorization(s) between the user and the ECSP may not be restricted to only certain edge services or applications. +3. Agreements between ECSPs are to share edge computing infrastructure and applications with other ECSP partners and their subscribers. These agreements are not restricted to only certain edge services or applications. +4. ASP may not have sufficient means or information to configure the UE with respect to the federation (e.g. the AC cannot be pre-configured with the ECS information, the AC is not edge-aware, the ASP does not provide AC to the UE, there is no CAS available or the CAS cannot redirect the UE to the partner ECSP). + +### 6.12.1 Architecture enhancements + +A federation can include multiple ECSP(s) where both, MNOs and the ECSPs can deploy multiple ECSs each. ECSs provide EES and EAS deployment information to the requestor. ECSs, EESs and EASs can be enabled or disabled dynamically based on prevailing requirements, available resources etc. so relying on pre-configuration or policy-based federation may result in use of stale pre-configurations and policies. Therefore, it is essential to maintain this information in real-time and enable an ECS to discover it on a need basis. + +This architecture option requires that the each ECSP in the federation of ECSPs designate one ECS as the center of information for that federation. This designated ECS acts as the edge repository (ECS-ER) of the federation. It stores and maintains up to date information about edge deployments of the federation. ECSs deployed by the ECSPs of the federation register and provide edge deployment information to this designated ECS. The designated ECSs of each ECSPs shares the information about the edge deployment to each other. + +Following figure illustrates the enhanced architecture: + +![Figure 6.12.1-1: Architecture enhanced with Edge repository. The diagram shows three main components: UE, 3GPP Core Network, and Edge Data Network. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP Core Network is a central vertical block. The Edge Data Network contains Edge Application Server(s), Edge Enabler Server(s), Edge Configuration Server, and Edge Configuration Server (Edge Repository). Arrows indicate traffic and signaling paths between these components, labeled with EDGE interfaces (EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, EDGE-10).](d79d33da852cb7bca3e87b400a15c3e8_img.jpg) + +The diagram illustrates the architecture enhanced with an Edge repository. It is divided into three main vertical sections: UE (User Equipment), 3GPP Core Network, and Edge Data Network. + +- UE:** Contains two boxes: "Application Client(s)" and "Edge Enabler Client". An arrow labeled "EDGE-5" connects the Application Client(s) to the Edge Enabler Client. +- 3GPP Core Network:** A central vertical block. It has interfaces labeled "EDGE-1", "EDGE-2", "EDGE-4", "EDGE-7", "EDGE-8", and "EDGE-10". +- Edge Data Network:** Contains four boxes: "Edge Application Server(s)", "Edge Enabler Server(s)", "Edge Configuration Server", and "Edge Configuration Server (Edge Repository)". + - An arrow labeled "EDGE-7" connects the Application Client(s) in the UE to the Edge Application Server(s). + - An arrow labeled "EDGE-1" connects the Edge Enabler Client in the UE to the Edge Enabler Server(s). + - An arrow labeled "EDGE-2" connects the Edge Enabler Client in the UE to the Edge Enabler Server(s). + - An arrow labeled "EDGE-4" connects the Edge Enabler Client in the UE to the Edge Configuration Server. + - An arrow labeled "EDGE-8" connects the Edge Enabler Client in the UE to the Edge Configuration Server (Edge Repository). + - An arrow labeled "EDGE-3" connects the Edge Application Server(s) to the Edge Enabler Server(s). + - An arrow labeled "EDGE-9" connects the Edge Enabler Server(s) to the Edge Configuration Server. + - An arrow labeled "EDGE-6" connects the Edge Enabler Server(s) to the Edge Configuration Server. + - An arrow labeled "EDGE-10" connects the Edge Configuration Server to the Edge Configuration Server (Edge Repository). + +A large horizontal arrow labeled "Application Data Traffic" points from the Application Client(s) in the UE, through the 3GPP Core Network, to the Edge Application Server(s) in the Edge Data Network. + +Figure 6.12.1-1: Architecture enhanced with Edge repository. The diagram shows three main components: UE, 3GPP Core Network, and Edge Data Network. The UE contains an Application Client(s) and an Edge Enabler Client. The 3GPP Core Network is a central vertical block. The Edge Data Network contains Edge Application Server(s), Edge Enabler Server(s), Edge Configuration Server, and Edge Configuration Server (Edge Repository). Arrows indicate traffic and signaling paths between these components, labeled with EDGE interfaces (EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, EDGE-9, EDGE-10). + +**Figure 6.12.1-1: Architecture enhanced with Edge repository** + +NOTE 1: There can be an EDGE-4 interface between the EEC and the Edge Configuration Server (Edge Repository). + +NOTE 2: ECS-ER does not perform resource management. Resource management is SA5's responsibility. + +There can be alternate deployments for this edge repository, for e.g.: + +- each ECSP can deploy its own edge repository; or +- multiple ECSPs can use the same ECS-ER as their edge repository; or +- each MNO can deploy an edge repository for all ECSPs associated with the MNO. + +NOTE 3: The interface and the interactions (e.g. ECS discovery, registration etc.) required between the ECS-ERs, and their potential alignment with ETSI MEC will be considered during the normative work. + +NOTE 4: Address information of partner ECSs in a federation can be locally configured in the primary ECS. + +NOTE 5: Possible mapping of the interfaces and roles of new entities with GSMA PRD will be considered in the normative work. + +### 6.12.2 Enhanced functional entities + +#### 6.12.2.1 Edge Configuration Server (Edge Repository) + +ECS that acts as edge repository (ECS-ER) provides supporting functions needed for roaming and federation. + +Functionalities of ECS-ER are: + +- a) Receiving and storing information about edge computing resources from other ECS(s) of the ECSP; +- b) Receiving and storing information about edge computing resources from other ECS-ER(s) of the federation; +- c) Providing information about Edge computing resources to other ECS-ER(s) of the federation. + +**Editor's Note:** Comparison and alignment of ECS-ER definition with the MEC Federator (MEF) as defined by ETSI MEC GS 040, which is aimed to host EWBI as defined by GSMA OPG, is FFS. + +### 6.12.3 Reference point + +#### 6.12.3.1 EDGE-10 + +EDGE-10 reference point enables interactions between the ECS and the ECS acting as edge repository. It supports: + +- a) registration and de-registration of the ECS to the ECS acting as edge repository; and +- b) retrieval or discovery of information about other ECS(s) of the federation. + +NOTE: Comparison and potential alignment of interactions between ECS and ECS-ER e.g. ECS discovery, registration etc. with corresponding ETSI MEC procedures will be considered in the normative work. + +### 6.12.4 Cardinality rules + +Following cardinality rules apply to the ECS-ER that acts as edge repository: + +- a) One ECS-ER per ECSP may be deployed to support the federation; + +Following cardinality rules apply for EDGE-10: + +- a) One or more ECS may communicate with the ECS that acts as edge repository. + +# 7 Solutions + +## 7.0 Mapping of solutions to key issues + +Table 7.0-1 Mapping of solutions to key issues + +| | KI
#
1 | KI
#
2 | KI
#
3 | KI
#
4 | KI
#
5 | KI
#
6 | KI
#
7 | KI
#
8 | KI
#
9 | KI
#
10 | KI
#
11 | KI
#
12 | KI
#
13 | KI
#
14 | KI
#
15 | KI
#
16 | KI
#
17 | KI
#
18 | KI
#
19 | KI
#
20 | KI
#
21 | KI
#
22 | KI
#
23 | KI
#
24 | +|---------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------| +| Sol #1 | X | | | | | | | | | | | | | | | | | | | | | | | | +| Sol #2 | | | | | | | X | | | | | | | | | | | | | | | | | | +| Sol #3 | X | | | | | | | | | | | | | | | | | | | | | | | | +| Sol #4 | | | | | | X | | | | X | | | | | | | | | | | | | | | +| Sol #5 | | | | | | X | | | | X | | | | | | | | | | | | | | | +| Sol #6 | | | X | | | | | | | | | | | | | | | | | | | | | | +| Sol #7 | | | X | | | | | | | | | | | | | | | | | | | | | | +| Sol #8 | | X | | | | | | | | | | | | | | | | | | | | | | | +| Sol #9 | | | | | | | | | | | | | | X | | | | | | | | | | | +| Sol #10 | | | | | | | | | | | | | | | X | | | | | | | | | | +| Sol #11 | | X | | | X | | | | | | | | | | | | | | | | | | | | +| Sol #12 | | | X | | | | | | | | | X | | | | | | | | | | | | | +| Sol #13 | | | | | | X | | | | X | | | | | | | | | | | | | | | +| Sol #14 | | | | | | | | | | X | | | | | | | | | | | | | | | +| Sol #15 | | | | | | | | X | | | | | | X | | | | | | | | | | | +| Sol #16 | | | | | | | | | | | | X | | | | | | | | | | | | | +| Sol #17 | | | | | | | | | | | | | | X | | | | | | | | | | | +| Sol #18 | | | | | | | | | | | | | | | X | | | | | | | | | | +| Sol #19 | | | | | | | | | | | | | | | | | | | X | | | | | | +| Sol #20 | X | | | | | | | | | | | | | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|---------|--|--|---|---|---|--|---|---|--|---|--|---|--|--|---|---|---|---|--|--|---|---|--|---| +| Sol #21 | | | X | | | | | | | | | | | | | | | | | | | | | | +| Sol #22 | | | | X | | | | | | | | | | | | | | | | | X | | | | +| Sol #23 | | | | | | | | | | | | | | | X | | | | | | | | | | +| Sol #24 | | | | | | | | | | X | | | | | | | | | | | | | | | +| Sol #25 | | | | | | | | | | X | | | | | | | | | | | | | | | +| Sol #26 | | | | | | | | | | | | | | | | | X | | | | | | | | +| Sol #27 | | | | | | | | | | | | | | | | X | | | | | | | | | +| Sol #28 | | | | | | | | | | | | | | | | X | | | | | | | | | +| Sol #29 | | | | | | | | | | | | | | | | X | | | | | | | | | +| Sol #30 | | | | | | | | | | | | | | | | X | | | | | | | | | +| Sol #31 | | | | | | | | | | | | X | | | | X | | | | | | | | | +| Sol #32 | | | | | | | | X | | | | | | | | | | | | | | | | | +| Sol #33 | | | | | | | | X | | | | | | | | | | | | | | | | | +| Sol #34 | | | | X | | | | | | | | | | | | | | | | | | | | | +| Sol #35 | | | | | | | | | | | | | | | | | | X | | | | | | | +| Sol #36 | | | | | X | | | | | | | | | | | | | | | | | | | | +| Sol #37 | | | X | | | | | | | | | | | | | | | | | | | | | | +| Sol #38 | | | | | | | | | | | | | | | | | | X | | | | | | | +| Sol #39 | | | | | | | X | | | | | | | | | | | | | | | | | | +| Sol #40 | | | | | | | | X | | | | | | | | | | | | | | | | | +| Sol #41 | | | | | | | | | | | | | | | | | | | | | | | | X | +| Sol #42 | | | | | | | | X | | | | | | | | | | | | | | | | | +| Sol #43 | | | | | X | | | | | | | | | | | | | | | | | X | | | +| Sol #44 | | | | | | | | | | | | | | | | | | | | | | X | | | +| Sol #45 | | | | | | | | | | | | | | | | | | | | | | X | | | + +| | | | | | | | | | | | | | | | | | | | | | | | | | +|---------|--|--|--|--|--|---|--|--|--|---|---|---|--|--|--|---|---|---|--|--|---|---|--|--| +| Sol #46 | | | | | | | | | | | | | | | | | X | | | | | | | | +| Sol #47 | | | | | | | | | | | | | | | | | X | | | | | | | | +| Sol #48 | | | | | | | | | | | | | | | | | | | | | | X | | | +| Sol #49 | | | | | | | | | | | | | | | | | | X | | | | | | | +| Sol #50 | | | | | | X | | | | X | | | | | | | | | | | | | | | +| Sol #51 | | | | | | | | | | | X | | | | | | | | | | | | | | +| Sol #52 | | | | | | | | | | | X | | | | | | | | | | | | | | +| Sol #53 | | | | | | | | | | | | X | | | | | | | | | | | | | +| Sol #54 | | | | | | | | | | | | | | | | X | | | | | | | | | +| Sol #55 | | | | | | | | | | | | | | | | | | | | | X | | | | + +## 7.1 Solution #1: Service provisioning via push notification + +### 7.1.1 Architecture enhancements + +None. + +### 7.1.2 Solution description + +#### 7.1.2.1 General + +The following solution corresponds to the key issue #1 on enhanced notification service to the EEC in clause 4.1. + +In this solution, push notification mechanism is utilized to enhance the service provisioning procedure. It is assumed that at least one push server is available to ECS and the UE has push function supporting the interaction with the push server. + +#### 7.1.2.2 Procedure + +Pre-conditions: + +1. The UE supports push notification service and the associated push server can be accessed by the ECS. +2. The address of push server is pre-configured in the Push function. + +![Sequence diagram illustrating Service provisioning via push notification. Lifelines: UE (containing EEC and Push Function), Push Server, and ECS. The sequence starts with 1a. EEC registers for push notification. 1b. Get push token from the Push server. 1c. Push token delivery. 2. Service provisioning subscribe request (Push token, Push server information). 3. Process request. 4. Service provisioning subscribe response. 5. Push notification request (Push token, EEC ID, EEC port ID, EDN config. Info). 6. Push notification.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant UE as UE (EEC, Push Function) + participant PS as Push Server + participant ECS as ECS + Note left of UE: 1a. EEC registers for push notification + UE->>PS: 1b. Get push token from the Push server + PS-->>UE: 1c. Push token delivery + UE->>ECS: 2. Service provisioning subscribe request (Push token, Push server information) + Note right of ECS: 3. Process request + ECS-->>UE: 4. Service provisioning subscribe response + Note right of ECS: 5. Push notification request (Push token, EEC ID, EEC port ID, EDN config. Info) + ECS->>PS: 5. Push notification request + PS-->>UE: 6. Push notification + +``` + +Sequence diagram illustrating Service provisioning via push notification. Lifelines: UE (containing EEC and Push Function), Push Server, and ECS. The sequence starts with 1a. EEC registers for push notification. 1b. Get push token from the Push server. 1c. Push token delivery. 2. Service provisioning subscribe request (Push token, Push server information). 3. Process request. 4. Service provisioning subscribe response. 5. Push notification request (Push token, EEC ID, EEC port ID, EDN config. Info). 6. Push notification. + +**Figure 7.1.2.2-1: Service provisioning via push notification** + +1. The EEC registers with the push function within the UE. The EEC acquires a push token and push server information from the push function. + +NOTE: The push server provides the push function in the UE with a push token, which is delivered to the EEC. + +2. The EEC sends a service provisioning subscribe request to the ECS. The service provisioning request includes push token, push server information (e.g. address) in addition to information elements in clause 8.3.3.3.4 of 3GPP TS 23.558 [2] v17.0.0. The push server address is included as Notification Target Address. +3. Upon receiving the request, the ECS performs an authorization check as in clause 8.3.3.2.3.2 of 3GPP TS 23.558 [2] and further verify if push notification can be used. If the request is authorized and push server can be used for notification, the ECS creates and stores subscription resource for service provisioning. +4. If the processing of the request was successful, the ECS responds with a service provisioning subscription response. +5. If an event occurs at the ECS that satisfies trigger conditions for updating service provisioning of a subscribed EEC and the corresponding subscription is for push notification, the ECS sends push notification request to the push server that is identified by the push server information provided by the EEC in the step 2. The push notification request sent from the ECS to the push server contains the push token, EEC information (e.g. identification or port ID) and service provisioning notification message. +6. The push server sends the service provisioning notification message to the EEC via the push function, which in turn and delivers the notification message to the corresponding EEC. + +### 7.1.3 Solution evaluation + +The proposed solution addresses Key Issue #1. The solution is based on Rel-17 service provisioning subscribe procedure and the push notification mechanism supported in a UE. This approach does not require EEC to persistently keep the session with ECS for receiving notification message. Instead, the UE reuses the session kept by the push function and push notification server. + +This solution does not introduce impact on Rel-17 architecture. + +## 7.2 Solution #2: Traffic filter support for EDGE-3 API addressing application traffic detection + +### 7.2.1 Architecture enhancements + +None. + +### 7.2.2 Solution description + +The EAS can provide the domain name to the EES as traffic descriptor and EES can further provision the domain name to the 3GPP CN. The following figure 7.2.2-1 depicts the solution sketch for the Session with QoS create operation with **bold** text showing the enhancement to the existing procedure in 3GPP TS 23.558 [2], clause 8.6.6.2. Such solution allows the EAS to provide fruitful traffic filters to be applied for the intended session with requested QoS. + +![Sequence diagram for Session with QoS API: create operation. The diagram shows interactions between EAS, EES, and 3GPP Core Network. Step 1: EAS sends a 'Session with QoS create request (traffic filter other than IP)' to EES. Step 2: EES performs internal operations (2a. PFD management, 2b. Subscribe PDU session status monitoring, 2c. Request data session with specific QoS) with the 3GPP Core Network. Step 3: EES sends a 'Session with QoS create response' back to EAS. Step 4: EES performs 'PDU session status notification; Request data session with specific QoS' with the 3GPP Core Network.](9b686adccf125267a013fa25721231a3_img.jpg) + +``` + +sequenceDiagram + participant EAS + participant EES + participant 3GPP Core Network + Note right of EES: 2a. PFD management + Note right of EES: 2b. Subscribe PDU session status monitoring + Note right of EES: 2c. Request data session with specific QoS + Note right of EES: 4. PDU session status notification; Request data session with specific QoS + + EAS->>EES: 1. Session with QoS create request (traffic filter other than IP) + EES->>3GPP Core Network: 2c. Request data session with specific QoS + 3GPP Core Network-->>EES: + EES->>EAS: 3. Session with QoS create response + EES->>3GPP Core Network: 4. PDU session status notification; Request data session with specific QoS + +``` + +Sequence diagram for Session with QoS API: create operation. The diagram shows interactions between EAS, EES, and 3GPP Core Network. Step 1: EAS sends a 'Session with QoS create request (traffic filter other than IP)' to EES. Step 2: EES performs internal operations (2a. PFD management, 2b. Subscribe PDU session status monitoring, 2c. Request data session with specific QoS) with the 3GPP Core Network. Step 3: EES sends a 'Session with QoS create response' back to EAS. Step 4: EES performs 'PDU session status notification; Request data session with specific QoS' with the 3GPP Core Network. + +Figure 7.2.2-1: Session with QoS API: create operation + +In step 1, the EAS requests establishment of a data session between the AC and the EAS with a specific QoS, the EAS sends the domain name as traffic descriptor which also indicates the applicable protocol and matching criteria (e.g. TLS SNI). In step 2a, the EES invokes the PFD management procedure with the 3GPP CN as described in 3GPP TS 23.682 [10] and 3GPP TS 23.502 [8] with an application id that may be derived from the EASID according to local policy. Further the EES provides the same application id for requesting data session with specific QoS in step 2c or step 4. + +NOTE: PFD management is optionally supported in MNO, if EES cannot invoke step 2a, it responds EAS with appropriate error. + +If the EAS provides only IP flow description as the traffic filter, the EES can provide the application id (which may be derived from the EASID) to the 3GPP CN when requesting data session with specific QoS and rely on further traffic classification mechanism in MNO to apply specific QoS for the application traffic. In that case, the EES skips the PFD management procedure in step 2a. + +Similar approach can be applied for the ACR management event API for EAS to consume EES service. + +The EAS can also send other specific filters (e.g. URI) to the EEL allowing a fruitful application traffic detection in the 3GPP CN, such filters will be used by the EES in the PFD management procedure in step 2a. + +### 7.2.3 Solution evaluation + +This solution address KI#7. It enhances the existing Session with QoS API and ACR management event API in 3GPP TS 23.558 [2] with support for traffic filters more than IP flow description. + +## 7.3 Solution #3: Service provisioning triggering via SMS over NAS + +### 7.3.1 Architecture enhancements + +None. + +### 7.3.2 Solution description + +#### 7.3.2.1 General + +The following solution corresponds to the key issue #1 on enhanced notification service to the EEC. + +In this solution, application triggering (device triggering) via SMS over NAS method specified in 3GPP TS 23.501 [5] is utilized to provide the updated EDN configuration information to the EEC. + +The EEC indicates to the ECS that SMS over NAS is supported. Then, the ECS checks if the SMS over NAS can be utilized and perform EEC triggering by using SMS over NAS. + +#### 7.3.2.2 Procedure + +Pre-conditions: + +1. The EEC is able to check if the UE supports the SMS over NAS; +2. The EEC is able to decode the need to trigger the operation indicated in the SMS; and +3. The ECS is allowed to use Nnef\_Trigger\_Delivery service. + +![Sequence diagram showing EEC triggering via SMS over NAS to perform service provisioning. The diagram involves two lifelines: EEC and ECS. Step 1: EEC sends a message '1. Indicate that SMS over NAS supported' to ECS. Step 2: ECS sends a message '2. Response' back to EEC.](68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS + Note right of EEC: 1. Indicate that SMS over NAS supported + EEC->>ECS: 1. Indicate that SMS over NAS supported + Note left of ECS: 2. Response + ECS->>EEC: 2. Response + +``` + +Sequence diagram showing EEC triggering via SMS over NAS to perform service provisioning. The diagram involves two lifelines: EEC and ECS. Step 1: EEC sends a message '1. Indicate that SMS over NAS supported' to ECS. Step 2: ECS sends a message '2. Response' back to EEC. + +**Figure 7.3.2.2-1: EEC triggering via SMS over NAS to perform service provisioning** + +1. The EEC determines that the UE supports the SMS over NAS by checking if the UE capability support the SMS delivery over NAS and if the UE is allowed by the core network to use SMS delivery over NAS (e.g. whether the UE is indicated by the core network that SMS over NAS is allowed during Registration procedure or UE Configuration Update procedure as specified in TS 23.502 [8]). If the SMS over NAS is supported and allowed in the UE, the EEC sends an indication of SMS over NAS supported to the ECS. This indication may be included in the service provisioning request message and sent to the ECS. +2. The ECS acknowledges to the EEC by sending a message including whether the EEC triggering via SMS over NAS is available for service provisioning or not. When the EDN configuration information in the ECS is updated, the ECS triggers EEC to initiate service provisioning request by utilizing the SMS over NAS as described in the below figure 7.3.2.2-2. + +![Sequence diagram showing EEC triggering via SMS over NAS to perform service provisioning. The diagram involves three lifelines: UE (containing EEC and MT), 5GC/NEF, and ECS. Step 1: ECS performs '1. Determine Trigger Needed'. Step 2: ECS sends '2. Nnef_Trigger_Delivery req' to 5GC/NEF. Step 3: 5GC/NEF performs '3. MT SMS Delivery' to the MT within the UE. Step 4: 5GC/NEF sends '4. Nnef_Trigger_Delivery response' to ECS. Step 5: 5GC/NEF sends '5. Nnef_Trigger_Delivery Notify' to ECS. Step 6: MT triggers EEC to perform service provisioning request. Step 7: EEC sends '7. Service provisioning request/response' to ECS.](8642df2e3828b25d27362bec6d5a0eae_img.jpg) + +``` + +sequenceDiagram + participant UE as UE (EEC, MT) + participant 5GC/NEF + participant ECS + Note right of ECS: 1. Determine Trigger Needed + ECS->>5GC/NEF: 2. Nnef_Trigger_Delivery req + Note over UE: 3. MT SMS Delivery + 5GC/NEF->>ECS: 4. Nnef_Trigger_Delivery response + 5GC/NEF-->>ECS: 5. Nnef_Trigger_Delivery Notify + Note left of UE: 6. Triggering EEC to perform service provisioning request + EEC->>ECS: 7. Service provisioning request/response + +``` + +Sequence diagram showing EEC triggering via SMS over NAS to perform service provisioning. The diagram involves three lifelines: UE (containing EEC and MT), 5GC/NEF, and ECS. Step 1: ECS performs '1. Determine Trigger Needed'. Step 2: ECS sends '2. Nnef\_Trigger\_Delivery req' to 5GC/NEF. Step 3: 5GC/NEF performs '3. MT SMS Delivery' to the MT within the UE. Step 4: 5GC/NEF sends '4. Nnef\_Trigger\_Delivery response' to ECS. Step 5: 5GC/NEF sends '5. Nnef\_Trigger\_Delivery Notify' to ECS. Step 6: MT triggers EEC to perform service provisioning request. Step 7: EEC sends '7. Service provisioning request/response' to ECS. + +**Figure 7.3.2.2-2: EEC triggering via SMS over NAS to perform service provisioning** + +1. The ECS determines to perform EEC triggering via SMS over NAS for service provisioning (e.g. when the EDN configuration information is updated). +2. The ECS invokes Nnef\_Trigger\_Delivery service to send a trigger delivery request message to the NEF as described in clause 4.13.2 of 3GPP TS 23.502 [8]. The message includes indication to trigger service provisioning, EEC ID, UE ID, and ECS information (e.g. address). + +3. The NEF delivers the triggering information via MT SMS Delivery procedure as specified in TS 23.502 [8]. The indication to trigger service provisioning, EEC ID, ECS information are included as the triggering payload in the triggering information +4. The NEF sends Nnef\_Trigger\_Delivery service response message to the ECS to inform that the ECS-provided information in step 2 is successfully delivered to the SMS-SC as in clause 4.13.2 of 3GPP TS 23.502 [8]. +5. The NEF sends Nnef\_Trigger\_Delivery Notify message to the ECS to inform that the SMS message is successfully delivered to the UE as in clause 4.13.2 of 3GPP TS 23.502 [8]. +6. The UE receives the SMS message containing the ECS-provided triggering information (indication to trigger service provisioning, EEC ID, ECS information) from the 5GC via Mobile Terminated SMS Delivery as in clause 4.13.3 of 3GPP TS 23.502 [8] and the EEC is triggered to perform service provisioning request toward the ECS identified by the ECS information contained in the SMS message. +7. The EEC may send a service provisioning request to the ECS identified by the triggering information contained in the SMS. + +### 7.3.3 Solution evaluation + +The solution addresses Key Issue #1: Enhanced notification service to the EEC. + +The solution utilizes application triggering (device triggering) via SMS over NAS method specified in 3GPP TS 23.501 [5]. This solution does not require EEC to persistently keep the session with ECS for receiving the updated EDN configuration information. + +This solution has the following impact on the EEC and ECS: + +- EEC supports to perform service provisioning when receiving application triggering SMS containing ECS-provided triggering information; +- ECS supports application triggering service provided by the core network (e.g. Nnef\_Trigger\_Delivery service). + +This solution does not introduce any impact on Rel-17 architecture. + +NOTE: This solution can be extended to enhance EDGE-1 notification service. + +## 7.4 Solution #4: ECS discovery through serving ECS to support edge services across ECSPs + +### 7.4.1 Architecture enhancements + +For a roaming scenario, Option #1 in the clause 6.1 is the basis for this solution. + +### 7.4.2 Solution description + +#### 7.4.2.1 General + +The following solution corresponds to the key issue #6 on edge services support across ECSPs in clause 4.6 and to the key issue #10 on support for roaming UEs. + +The scenario assumption of this solution is that the ECS1 may determine a potential ECS information (e.g. address, endpoint or service API information) based on pre-configuration or may discover service API information exposed by that ECS via CAPIF discovery procedure as specified in TS 23.222 [16]. In this solution, it is assumed that the ECSP1 and ECSP2 have a service level agreement to share edge services. If the ECS1 cannot discover a suitable EES to serve the UE at the current location (e.g. all the EESs registered on the ECS1 do not cover the given UE location), the ECS1 discovers another ECS2 which may have suitable EES based on UE location and provides it to the requesting EEC or EES. + +NOTE: To configure sufficient information to the ECS, the ECS(s) information related to other ECSPs may be available at the OAM system due to the inter-ECSP relationship establishment, which is then used by the OAM system of an ECSP to configure its ECS. If required, the information of available applications in a partner ECSP and the corresponding service areas are included in the configured information. Inter-ECSP relationship establishment is according to the business relationship between the ECSPs and is out of the scope of SA6. The OAM to configure its ECS for inter-ECSP relationship is under the scope of SA5. + +In a roaming scenario, after a UE selects a PLMN and performs the registration procedure, the EEC gets ECS information to use edge computing service in the VPLMN as follows: + +- The EEC may have been pre-configured or provisioned with V-ECS information. +- The EEC may try to send a service provisioning request message including service PLMN ID to the H-ECS and retrieves V-ECS information or, if possible, EDN configuration information for VPLMN. The EEC may perform service provisioning procedure with the V-ECS if the H-ECS provides V-ECS information to the EEC as show in figure 7.4.2.2-1. This solution provides a procedure for this aspect. +- The EEC may try to derive V-ECS address information from the VPLMN identifier. For example, an EEC can combine the VPLMN identifier and an ECSP code (or ECSP ID) assigned to an edge computing service provider (e.g. "ECS .ECS.MNC .mcc .3gppNetwork.org "). + +In a roaming scenario, if a V-ECS information is provided by 5GC, the EEC shall use the provided information for the subsequent service provisioning request. + +NOTE: In a roaming scenario, current solution provides a procedure to one method for the EEC gets ECS information to use edge computing service in the VPLMN. The precedence among different methods is not the scope of this solution. + +#### 7.4.2.2 Procedure + +In this solution, when the ECS1 receives the request of EES from the EEC or source EES, the ECS1 discovers another ECS2 which may have suitable EES and responds with the ECS2 information. After that, the EEC or source EES sends the request of EES to the ECS2. + +Pre-conditions: + +1. ECSP1 and ECSP2 have a service level agreement to share edge services. +2. The EEC has a business relationship/subscription to the ECSP1. +3. The EEC has ECS1 address information and can access to the ECS1 (in roaming scenario, ECS1 and ECS2 indicate the H-ECS and the V-ECS, respectively). + +![Sequence diagram for Solution 4 for edge services support across ECSPs. Lifelines: EEC, EES1, ECS1, ECS2, EES2. ECSP1 contains EEC, EES1, and ECS1. ECSP2 contains ECS2 and EES2. The sequence starts with 0. EES registration from EES2 to ECS2. Then 1a. Service provisioning request from EEC to ECS1. 1b. Retrieve EES request from EES1 to ECS1. A box labeled '2. if a suitable EES to serve the UE can not be found based on ECS1's profile, ECS1 discovers another ECS2 which may have suitable EES' is shown. 3a. Service provisioning response (List of ECS(s)) from ECS1 to EEC. 3b. Service provisioning response (List of ECS(s)) from ECS1 to EES1. 4a. Service provisioning from ECS(s) (a horizontal bar spanning EEC, EES1, ECS1, and ECS2). 4b. Retrieve EES from ECS(s) (a horizontal bar spanning EES1, ECS1, and ECS2).](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +Sequence diagram for Solution 4 for edge services support across ECSPs. Lifelines: EEC, EES1, ECS1, ECS2, EES2. ECSP1 contains EEC, EES1, and ECS1. ECSP2 contains ECS2 and EES2. The sequence starts with 0. EES registration from EES2 to ECS2. Then 1a. Service provisioning request from EEC to ECS1. 1b. Retrieve EES request from EES1 to ECS1. A box labeled '2. if a suitable EES to serve the UE can not be found based on ECS1's profile, ECS1 discovers another ECS2 which may have suitable EES' is shown. 3a. Service provisioning response (List of ECS(s)) from ECS1 to EEC. 3b. Service provisioning response (List of ECS(s)) from ECS1 to EES1. 4a. Service provisioning from ECS(s) (a horizontal bar spanning EEC, EES1, ECS1, and ECS2). 4b. Retrieve EES from ECS(s) (a horizontal bar spanning EES1, ECS1, and ECS2). + +**Figure 7.4.2.2-1: Solution 4 for edge services support across ECSPs** + +1. The ECS1 receives request for obtaining EES information, this procedure may be triggered by following events: + +1a. The EEC sends a service provisioning request to the ECS. It is assumed that the EEC has been pre-configured or has provisioned with the address (e.g. URI) of the ECS1. The request may include the UE location. For roaming scenario, the request may also include serving PLMN ID of the UE hosting the EEC. + +1b. The S-EES (EES1) sends the retrieve EES request to the ECS in order to identify the T-EES which has an EAS available to serve the UE. + +2. If the request does not contain the UE location information, the ECS1 interacts with 3GPP core network to retrieve the UE location. If the ECS1 cannot discover a suitable EES to serve the UE at the received or retrieved UE location based on the received information (e.g. all the EESs registered on the ECS1 do not cover the given UE location), the ECS1 discovers potential ECSs which may have suitable EES based on the information such as the UE location. + +For roaming scenario, if the request does not contain the serving PLMN ID, the ECS1 may interact with 3GPP core network to retrieve serving PLMN ID. The H-ECS checks if the edge computing service for the EEC can be supported in the VPLMN identified by serving PLMN ID according to the roaming agreement with VPLMN operator for given ECSPs. The ECS1 discovers the potential ECSs, e.g. ECS2 which have suitable EES based on the serving PLMN ID. Optionally, the ECS1 may send a request to ECS2 to verify whether the ECS2 is available. If yes, ECS2 returns the success response to the ECS1. Otherwise, a failure response/code is returned. + +The H-ECS can check if the edge computing service for the EEC can be supported in the VPLMN based on the roaming agreement on edge computing services between PLMNs or service agreement between ECSPs. In the roaming scenario, roaming agreement on edge computing service can be addressed by SA2 based on the principles in clause 9.1. + +NOTE 1: The ECS1 can filter the list of the discovered ECSs based on the information elements provided via the service provisioning request, ECSP policy configured in ECS, or UE-specific service information. Details of ECSP and UE-specific service information is out of scope. + +NOTE 2: This solution does not exclude other ways for ECS 1 to determine ECS 2. Other solution for determining ECS2 by ECS1 can be utilized in this procedure when the multiple ECSs are available for an EEC. + +3. ECS1 sends a response message including the list of ECSs information and failure cause indicating redirection to another ECS (for service provisioning request or retrieve EES request) to the requester of step 1 if the ECS1 cannot discover a EES: + +3a. In response to the request in step 1a, the ECS1 sends the response message to the EEC. + +3b. In response to the request in step 1b, the ECS1 sends the response message to the S-EES. + +4. The EEC or source EES can send the request (e.g. resends a service provisioning request or retrieve EES request) to one of the ECSs received from the ECS1 e.g. the ECS2. Correspondingly, the EEC or source EES receives response from the ECS2. + +### 7.4.3 Solution evaluation + +Solution 4 solves the problems of KI#10 and KI#6. After discovering another ECS2 which may have suitable EES, the ECS1 sends respond to the EEC or source EES with the ECS2 information. Then the EEC or source EES can send the request to the ECS2 directly to retrieve suitable EES. It is possible that some enhancements on ECS are needed to support ECS discovery. + +This solution relies on having sufficient information (e.g. ECSP policy, UE-specific service information, or ECSs information) configured or available in an ECS to determine candidate ECSs in step 2. + +The Solution #4 will use any agreed solution for determining ECS2 by ECS1. + +## 7.5 Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs + +### 7.5.1 Architecture enhancements + +A new reference point is required between ECSs, which is described as EDGE-10 in the clause 6.1.1.1. + +For a roaming scenario, Option #1 in the clause 6.1 is the basis for this solution. + +### 7.5.2 Solution description + +#### 7.5.2.1 General + +The following solution corresponds to the key issue #6 on edge services support across ECSPs in clause 4.6 and to the key issue #10 on support for roaming UEs in clause 4.10. + +The scenario assumption of this solution is that the ECS1 may determine the ECS2 information (e.g. address, endpoint or service API information) based on pre-configuration or may discover service API information exposed by that ECS via CAPIF discovery procedure as specified in TS 23.222 [16]. + +In this solution, it is assumed that the ECSP1 and ECSP2 have a service level agreement to share edge services. If the ECS1 cannot discover a suitable EES to serve the UE at the current location (e.g. all the EESs registered on the ECS1 do not cover the given UE location), the ECS1 discovers another ECS2 which may have suitable EES and discovers the EES via the ECS2. + +NOTE: To configure sufficient information to the ECS, the ECS(s) information related to other ECSPs may be available at the OAM system due to the inter-ECSP relationship establishment, which is then used by the OAM system of an ECSP to configure its ECS. If required, the information of available applications in a partner ECSP and the corresponding service areas are included in the configured information. Inter-ECSP relationship establishment is according to the business relationship between the ECSPs and is out of the scope of SA6. The OAM to configure its ECS for inter-ECSP relationship is under the scope of SA5. + +#### 7.5.2.2 Procedure + +In this solution, when the ECS1 receives the request of EES from the EEC / source EES, the ECS1 discovers another ECS2 which may have suitable EES and discovers the EES via the ECS2. The ECS1 then provides the EES information to the EEC / source EES in the response. + +Pre-conditions: + +1. ECSP1 and ECSP2 have a service level agreement to share edge services. +2. The EEC has a business relationship/subscription to the ECSP1. +3. The EEC has ECS1 address information and can access to the ECS1 (in roaming scenario, ECS1 and ECS2 indicate the H-ECS and the V-ECS respectively). + +![Sequence diagram for Solution 5 for edge services support across ECSPs. Lifelines: EEC, EES1, ECS1, ECS2, EES2. The diagram shows the interaction between these entities to discover and register edge services.](6df5629bc2fc6d82f1a1edf9d7340113_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES1 + participant ECS1 + participant ECS2 + participant EES2 + + Note right of ECS1: ECSP1 + Note right of ECS2: ECSP2 + + EES2->>ECS2: 0. EES registration + EEC-->>ECS1: 1a. Service provisioning request + EES1-->>ECS1: 1b. Retrieve EES request + Note right of ECS1: 2. if a suitable EES to serve the UE can not be found based on ECS1's profile , ECS1 discovers another ECS2 which may have suitable EES + Note right of ECS1: 3. discover target EES + ECS1-->>EEC: 4a. Service provisioning response + ECS1-->>EES1: 4b. Retrieve T-EES response + +``` + +Sequence diagram for Solution 5 for edge services support across ECSPs. Lifelines: EEC, EES1, ECS1, ECS2, EES2. The diagram shows the interaction between these entities to discover and register edge services. + +**Figure 7.5.2.2-1: Solution 5 for edge services support across ECSPs** + +1. The ECS1 receives request for obtaining EES information, this procedure may be triggered by following events: + - 1a. The EEC sends a service provisioning request to the ECS. It is assumed that the EEC has been pre-configured or has provisioned with the address (e.g. URI) of the ECS1. The request may include the UE location. For roaming scenario, the request may also include serving PLMN ID of the UE hosting the EEC. + - 1b. The S-EES (EES1) sends the Retrieve EES request to the ECS in order to identify the T-EES which has an EAS available to serve the UE. + +2. If the request does not contain the UE location information, the ECS1 interacts with 3GPP core network to retrieve the UE location. If the ECS1 cannot discover a suitable T-EES to serve the UE at the received or retrieved UE location based on the received information (e.g. all the EESs registered on the ECS1 do not cover the given UE location), the ECS1 discovers another ECS2 which may have suitable EES based on the information such as the UE location. + +For roaming scenario, if the request does not contain the serving PLMN ID, the ECS1 may interacts with 3GPP core network to retrieve serving PLMN ID. The H-ECS checks if the edge computing service for the EEC can be supported in the VPLMN identified by serving PLMN ID according to the roaming agreement with VPLMN operator for given ECSPs. The ECS1 discovers the ECS2 which have suitable EES based on the serving PLMN ID. + +The H-ECS can check if the edge computing service for the EEC can be supported in the VPLMN based on the roaming agreement on edge computing services between PLMNs or service agreement between ECSPs. In the roaming scenario, roaming agreement on edge computing service can be addressed by SA2 based on the principles in clause 9.1. + +3. The ECS1 further discovers a target EES whose service area can cover the UE location via the ECS2. The ECS1 may interact with the ECS2 directly or indirectly via e.g. a Federation manager. +4. ECS sends the response to the requester of step 1: + - 4a. In response to the request in step 1a, ECS1 sends the EES information to the EEC. + - 4b. In response to the request in step 1b, ECS1 sends the Retrieve EES response to the requesting EES (EES1). + +### 7.5.3 Solution evaluation + +This solution addresses KI#6 and KI#10. The EEC or the EES gets the requested EES information from ECS2 via ECS1. It is possible that some enhancements on ECS are needed to support service provisioning and EES retrieval request across the ECSPs. + +This relies on preconfigured information of ECS2 at ECS1. The solution will use any agreed solution for determining ECS2 by ECS1. + +## 7.6 Solution #6: ACR update in service continuity planning + +### 7.6.1 Architecture enhancements + +Option #8 in the clause 6.8 is the basis for this solution. + +### 7.6.2 Solution description + +The solution addresses the key issue #3 and the open issue on how to deal with scenarios when the ACR needs to be modified, e.g. due to UE mobility. + +The solution can have two different solution variants based on the type of service continuity planning update. One possible solution is to modify the ACR service after the launch (described in 7.6.2.1) and another possible solution is the pause of the ACR services for a pre-defined time or till the detection entity decides to resume the ACR (described implicitly in 7.6.2.1 as part of EEC-based modification procedure). ACR pause allows the EEC after the detection of an expected/predicted UE location and/or mobility change with low confidence level, to decide on pausing the ACR and to send to S-EES/T-EES the pause decision and the required time for the pause, or under which criteria the ACR will resume (or a further ACR modification request may follow after some time period if EEC identifies that ACR can continue). + +#### 7.6.2.1 ACR modification solution + +##### 7.6.2.1.1 EEC-based ACR modification procedure + +Pre-conditions: + +1. The ACR has been launched. + +![Sequence diagram illustrating the EEC-based ACR modification procedure. Lifelines: AC, EEC, 5GS, S-EES / T-EES, S-EAS, T-EAS. The sequence starts with AC and EEC detecting a change in UE mobility. EEC then makes an ACR update decision. EEC sends an ACR modification request to S-EES / T-EES. S-EES / T-EES performs the ACR modification execution. S-EES / T-EES sends an ACR modification response to EEC. Finally, EEC sends a notification of ACR modification to AC.](35a7554182eb055209552843f341a1ae_img.jpg) + +``` + +sequenceDiagram + participant AC + participant EEC + participant 5GS + participant S-EES / T-EES + participant S-EAS + participant T-EAS + + Note left of AC: 1. detect a change of expected/predicted UE mobility + Note left of EEC: 2. ACR update decision + EEC->>S-EES / T-EES: 3. ACR modification request + Note right of S-EES / T-EES: 4. ACR modification execution + S-EES / T-EES->>EEC: 5. ACR modification response + Note left of AC: 6. Notification of ACR modification + +``` + +Sequence diagram illustrating the EEC-based ACR modification procedure. Lifelines: AC, EEC, 5GS, S-EES / T-EES, S-EAS, T-EAS. The sequence starts with AC and EEC detecting a change in UE mobility. EEC then makes an ACR update decision. EEC sends an ACR modification request to S-EES / T-EES. S-EES / T-EES performs the ACR modification execution. S-EES / T-EES sends an ACR modification response to EEC. Finally, EEC sends a notification of ACR modification to AC. + +**Figure 7.6.2.1.1-1: EEC-based ACR modification procedure** + +1. The EEC detects a change of the expected UE behaviour. In particular, it may receive from the AC (over EDGE-5) an indication that the expected/predicted UE location and/or mobility changed. Such message can include the current and new expected/predicted location or current and new expected mobility/speed/direction/velocity, and/or an expected change of the UE route/trajectory. +2. The EEC identifies that one or more ACR updates are needed based on the change of the UE behaviour and decides the type of the ACR update to be an ACR modification or an ACR pause/resume. ACR pause or resume can be a variant of ACR modification and indicates that the ACR needs to be halted for a given time or till further notice (e.g. an ACR resume as ACR update may be decided after some time period if EEC identifies that ACR can continue). +3. The EEC sends an ACR modification request to the S-EES or T-EES (for EEC executed ACR via T-EES scenario) to indicate an ACR modification and to provide the updated parameters, such as the expected completion time. The request also includes the necessary parameters (e.g. IDs) to indicate the ACR that is requested to be updated. In case of ACR pause, this message indicates the request for an ACR pause and can provide the duration for the pause (time to wait) or under which criteria the ACR is expected to resume. In case of ACR resume, this message indicates the request for an ACR to be resumed after a pause. +4. S-EES or T-EES determines the ACR to be modified based on the request in step 3. The ACR modification, is executed by the execution entity as described in clause 7.6.2.1.3. +5. The S-EES (or T-EES for EEC executed ACR via T-EES scenario) sends an ACR modification response to the EEC to notify on the result. +6. The EEC may optionally provide a notification to the AC (over EDGE-5) to inform on the ACR modification result. + +NOTE: This procedure has impacts on EDGE-5 interface. + +##### 7.6.2.1.2 EES-based modification procedure + +Pre-conditions: + +1. The ACR has been launched. + +![Sequence diagram illustrating the S-EES-based ACR modification procedure. Lifelines: AC, EEC, 5GS, S-EES, S-EAS, T-EES, T-EAS. The sequence of steps is: 1. detect a change of expected/predicted UE mobility (S-EES to S-EES), 2. ACR modification decision (S-EES to S-EES), 3. ACR modification execution (S-EES to T-EES), 4. ACR modification notification (S-EES to EEC), 5. Notification of ACR modification (EEC to AC).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant AC + participant EEC + participant 5GS + participant S-EES + participant S-EAS + participant T-EES + participant T-EAS + + Note right of S-EES: 1. detect a change of expected/predicted UE mobility + Note right of S-EES: 2. ACR modification decision + Note right of S-EES: 3. ACR modification execution + S-EES->>EEC: 4. ACR modification notification + EEC-->>AC: 5. Notification of ACR modification + +``` + +Sequence diagram illustrating the S-EES-based ACR modification procedure. Lifelines: AC, EEC, 5GS, S-EES, S-EAS, T-EES, T-EAS. The sequence of steps is: 1. detect a change of expected/predicted UE mobility (S-EES to S-EES), 2. ACR modification decision (S-EES to S-EES), 3. ACR modification execution (S-EES to T-EES), 4. ACR modification notification (S-EES to EEC), 5. Notification of ACR modification (EEC to AC). + +**Figure 7.6.2.1.2-1: S-EES-based ACR modification procedure** + +1. The S-EES detects a change of the expected UE behaviour. In particular, S-EES acting as AF, may receive a UE location report or a monitoring event report from 5GC (assuming that S-EES has subscribed to consume 5GC services like LCS or NEF monitoring events). Such UE location report or monitoring event report may help indicating that the UE is not going to be at the predicted location at the given time and is expected to deviate by the original planning. +2. The S-EES identifies that one or more ACR updates are needed based on the information on the change of the UE behaviour. The S-EES then decides for each ACR, the type of the ACR update to be an ACR modification and the parameters that need to be updated, such as the expected completion time. +3. S-EES or T-EES determines the ACR(s) to be modified based on the decision in step 2. For each ACR identified to be updated in step 2, the ACR modification is executed by the execution entity as described in clause 7.6.2.1.3. +4. The S-EES sends an ACR modification notification to EEC to notify on the result. +5. The EEC may optionally provide a notification to the AC (over EDGE-5) to inform on the ACR that is modified. + +##### 7.6.2.1.3 ACR modification execution procedure + +Figure 7.6.2.1.3-1 illustrates the ACR modification execution procedure as used in the procedures in 7.6.2.1.1 and 7.6.2.1.2. + +Pre-condition: + +1. An ACR has been launched between EEC, S-EES, S-EAS, T-EES and S-EAS, where S-EES and T-EES can be the same or different; and one of the following preconditions holds: + - 1.1 The S-EES or T-EES has received an ACR modification request from EEC, e.g. according to the step 3 of the EEC-based ACR modification procedure in solution 6 in clause 7.6.2.1.1; or + - 1.2 The S-EES has decided an ACR modification, e.g. according to step 3 of EES-based modification procedure in solution 6 in clause 7.6.2.1.2. + +![Sequence diagram illustrating the ACR modification execution procedure. Lifelines: EES, Remote EES, S-EAS or T-EAS (Corresponding to the EES), and T-EAS or S-EAS (Corresponding to the remote EES). The sequence of messages is: 1. ACR Modification notification With updated parameters from EES to S-EAS or T-EAS; 2. ACR modification Indication with updated parameters from S-EAS or T-EAS to EES; 3. ACR modification indication response from EES to Remote EES; 4. ACT update (a block spanning the bottom of the S-EAS/T-EAS and T-EAS/S-EAS lifelines).](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant EES + participant Remote EES + participant S-EAS or T-EAS as S-EAS or T-EAS +(Corresponding to the EES) + participant T-EAS or S-EAS as T-EAS or S-EAS +(Corresponding to the remote EES) + + Note right of T-EAS or S-EAS: 4. ACT update + + EES->>S-EAS or T-EAS: 1. ACR Modification notification +With updated parameters + S-EAS or T-EAS-->>EES: 2. ACR modification Indication +with updated parameters + EES-->>Remote EES: 3. ACR modification indication +response + +``` + +Sequence diagram illustrating the ACR modification execution procedure. Lifelines: EES, Remote EES, S-EAS or T-EAS (Corresponding to the EES), and T-EAS or S-EAS (Corresponding to the remote EES). The sequence of messages is: 1. ACR Modification notification With updated parameters from EES to S-EAS or T-EAS; 2. ACR modification Indication with updated parameters from S-EAS or T-EAS to EES; 3. ACR modification indication response from EES to Remote EES; 4. ACT update (a block spanning the bottom of the S-EAS/T-EAS and T-EAS/S-EAS lifelines). + +**Figure 7.6.2.1.3-1: ACR modification execution procedure** + +1. If the EAS has subscribed to receive ACR notify for modification, the EES shall notify the EAS about the need to update the ACR. The EES shall include the updated parameters in the notification to the EAS. + +Depending on the ACR scenario, the EES can be either of S-EES or T-EES. If it is S-EES, the EAS will be S-EAS. Otherwise if the EES is T-EES, the EAS will be T-EAS. + +2. The EES processes the updated parameters. The EES sends the updated parameters to the remote EES, if the updated parameter can be used by the remote EES to handle the messages from the corresponding EAS, e.g. expected completion time if provided in step 3 of clause 7.6.2.1.1 for the waiting time for the ACR status update. + +When EES from step 1 is S-EES the remote EES will be the T-EES. Otherwise if the EES is T-EES, the remote EES will be S-EES. + +3. In response to the message in step 2, the remote EES responds and confirms the reception and acceptance of the updated parameters. + +NOTE: It is assumed that the updated parameters (e.g. updated completion time) do not require the update of any of the EEC context information. + +4. If in step 1 the S-EAS receives the ACR notify for modification, it may initiate ACT update process with the T-EAS. Otherwise if in step 1, T-EAS receives the ACR notify for modification, it may initiate the ACT update process. S-EAS and T-EAS may perform step 4 in an application specific time and manner any time after the notification in step 1. + +### 7.6.3 Solution evaluation + +This solution provides the procedures to update the parameters of an ACR in service continuity planning. It addresses the third open issue of the KI#3, to handle scenarios when the ACR needs to be modified, e.g. due to UE mobility. The solution does not require enhancement to the existing architecture in Release 17. + +## 7.7 Solution #7: EES monitors UE mobility for service continuity planning + +### 7.7.1 Architecture enhancements + +None. + +### 7.7.2 Solution description + +#### 7.7.2.1 General + +The following solution corresponds to the key issue#3 on enhancements to service continuity planning in clause 4.3 + +#### 7.7.2.2 Procedure + +In this solution, the EES is responsible to identify the ACR type in ACR detection part or receive the ACR type from the EAS and the EEC. When application context transmission is complete, the EAS will send ACR status update message to the EES, once EES detects that UE moves to the predicted/expected location, the EES will notify EEC ACR complete message, then the EEC can be aware of the completion of ACR. With this solution the EAS will not need to monitor the UE mobility and determine when to send the ACR status update message to the EES. + +Compared to the procedure specified in 3GPP TS 23.558 clause 8.8.2.5, the following differences are captured below: + +2. The detection entities (EEC, S-EAS, S-EES) detect the ACR may be required and identify the ACID and related ACR type (normal ACR or service continuity planning). +3. If the EEC or S-EAS detect the ACR event, the EEC or S-EAS should inform S-EES with ACID, ACR type and predicted/expected UE location or EAS service area in the ACR launching procedure. +10. when S-EAS detects application context transmission is complete, the S-EAS sends ACR status update request message to the S-EES with ACID. +11. Once S-EES detects the UE has moved to the predicted/expected UE location or EAS service area, then the S-EES sends ACR complete notify message to the EEC. + +Compared to the procedure specified in 3GPP TS 23.558 clause 8.8.2.3, the following differences are captured below: + +4. The EEC performs ACR launching procedure indicating S-EES with ACR type (normal ACR or service continuity planning) and predicted/expected UE location or EAS service area.7. When S-EAS detects application context transmission is complete, the S-EAS sends ACR status update request message to the S-EES with ACID. +9. Once S-EES detects the UE has moved to the predicted/expected UE location or EAS service area, then the S-EES sends ACR complete notify message to the EEC indicating that UE has moved to the predicted location. + +##### Enhancements to 3GPP TS 23.558 clause 8.8.3.4 ACR launching procedure + +Figure 8.8.3.4-1 illustrates the ACR launching procedure by the EEC or the S-EAS. If this procedure is triggered by the EEC, depending on the ACR action indicated in the ACR request, the procedure is used for either ACR initiation or ACR determination. If this procedure is triggered by the S-EAS, the procedure is used for ACR determination. + +Pre-condition: + +1. The EEC has been authorized to communicate with the EES as specified in clause 8.11, if the procedure is triggered by the EEC; and +2. Information related to the S-EES is available with the S-EAS, if the procedure is triggered by the S-EAS. + +![Sequence diagram illustrating the ACR launching procedure. The diagram shows three steps: 1. ACR request from EEC or S-EAS to EES; 2. Authorization check and processing the request by EES; 3. ACR response from EES to EEC or S-EAS.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant EEC or S-EAS + participant EES + Note right of EES: 2. Authorization check and processing the request + EEC or S-EAS->>EES: 1. ACR request + EES-->>EEC or S-EAS: 3. ACR response + +``` + +Sequence diagram illustrating the ACR launching procedure. The diagram shows three steps: 1. ACR request from EEC or S-EAS to EES; 2. Authorization check and processing the request by EES; 3. ACR response from EES to EEC or S-EAS. + +**Figure 8.8.3.4-1: ACR launching procedure** + +1. The EEC or the S-EAS sends an ACR request message to the EES in order to start ACR. The ACR request message includes ACR type to indicate whether the ACR is for normal ACR or service continuity planning. The ACR request message includes Predicted/Expected UE location or EAS service area to indicate that the EES should detect whether the UE has moved to the Predicted/Expected UE location or EAS service area or not in ACR clean-up phase. The ACR request message includes ACR action to indicate either ACR initiation request or ACR determination request. If the procedure is triggered by the S-EAS, the ACR request message is only for ACR determination. + +An ACR request for ACR initiation: + +- includes an indication of whether the EEC requests the EES to perform EAS notification; and +- provides information used by EES to perform AF traffic influence as in 3GPP TS 23 501 [2]. + +An ACR request for ACR determination informs the EES that the need for ACR has been detected at EEC. + +2. The EES checks if the requestor is authorized for this operation. If authorized, the EES processes the request and performs the required operations. + +If the request in step 1 is for ACR initiation: + +- the EES may use information provided in the request to apply the AF traffic influence with the N6 routing information of the T-EAS in the 3GPP Core Network (if applicable), as described in 3GPP TS 23.501 [2], clause 5.6.7.1; and +- if the EAS notification indication is provided in the step 1 request and the EAS has subscribed to receive such notification, the EES shall notify the EAS about the need to start ACR. + +If the request in step 1 is for ACR determination, the EES decides to execute ACR as described in clause 8.8.2.5. + +3. The EES responds to the requestor's request with an ACR response message. + +##### Enhancements to 3GPP TS 23.558 clause 8.8.4.4 ACR request + +Table 8.8.4.4-1 describes information elements for the ACR request sent from the EEC either to the S-EES or T-EES. + +**Table 8.8.4.4-1: ACR request** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. EECID or EASID). | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| UE identifier (NOTE 4) | O | The identifier of the UE (i.e. GPSI). | +| ACR type | M | Indicates whether the ACR is for normal ACR or service continuity planning | +| Predicted/Expected UE location or EAS service area (NOTE 5) | O | The predicted/expected location information of the UE. The UE location is described in clause 7.3.2 or the predicted/expected EAS service area as described in clause 7.3.3.3 | +| Prediction expiration time (NOTE 6) | O | The time the UE reaches the Predicted/Expected UE location or EAS service area at the latest | +| ACR action (NOTE 3) | M | Indicates the ACR action (ACR initiation or ACR determination) | +| ACR initiation data (NOTE 2) | O | ACR initiation IEs to be included in an ACR request message when ACR action indicates it is ACR initiation request. | +| > T-EAS Endpoint | M | Endpoint information (e.g. URI, FQDN, IP 3-tuple) of the T-EAS. | +| > DNAI of the T-EAS | O | DNAI information associated with the T-EAS. | +| > N6 Traffic Routing requirements | O | The N6 traffic routing information and/or routing profile ID corresponding to the T-EAS DNAI. | +| > EAS notification indication | M | Indicates whether to notify the EAS about the need of ACR. | +| > S-EAS endpoint (NOTE 1) | O | Endpoint information of the S-EAS | +| ACR determination data (NOTE 2) | O | ACR determination IEs to be included in an ACR request message when ACR action indicates it is ACR determination request. | +| > S-EAS endpoint | M | Endpoint information of the S-EAS | +| NOTE 1: This IE shall be present if the EAS notification indication indicates that the EAS needs to be informed. | | | +| NOTE 2: Either ACR initiation or ACR determination shall be included corresponding to the ACR action. | | | +| NOTE 3: This IE shall indicate ACR determination if the request originates from the S-EAS. | | | +| NOTE 4: This IE shall be present if the request originates from the EEC. | | | +| NOTE 5: This IE shall be present if the ACR type indicates the ACR procedure is for service continuity planning. | | | +| NOTE 6: This IE may be present if the request is from EEC and the ACR type indicates the ACR procedure is for service continuity planning. | | | + +NOTE: "Prediction expiration time" and "expected completion time" in solution #6 are the same IE. + +NOTE: The ACR cancellation can be triggered when UE doesn't move to the location monitored by the EES. + +### 7.7.3 Solution evaluation + +This clause provides an evaluation of the solution. + +This solution address KI#3. It enhances the existing service continuity procedure in 3GPP TS 23.558 [2] with support for the EES monitoring UE mobility for service continuity planning. With this solution, the EAS will not need to monitor the UE mobility and determine when to send the ACR status update message to the EES. + +## 7.8 Solution #8: EAS Service API enablement using CAPIF + +### 7.8.1 Architecture enhancements + +None. + +### 7.8.2 Solution description + +#### 7.8.2.1 General + +This solution addresses the Key issue #2: Enablement of Service APIs exposed by EAS as specified in the clause 4.2 by supporting for an EAS to expose its Service APIs towards the other EASs. + +As specified in TS 23.558 (Rel-17), the Edge Enabler Layer exposes Service APIs towards the EASs. The exposed Service APIs include the capabilities provided by EES (clause 8.6 of TS 23.558); the capabilities provided by the 3GPP core network (clause 8.7 of TS 23.558); and SEAL service APIs (clause A.4 of TS 23.558). + +In this solution, the Edge Enabler Layer also supports for an EAS to expose its Service APIs (i.e. EAS Service APIs) towards the other EASs in order to fulfil the architectural requirements specified in the clause 5.2. This solution exploits CAPIF specified in 3GPP TS 23.222 [16] to support publication/discovery, and change subscription of EAS Service APIs as studied in Sol#15 of TR 23.758 (Rel-17) with the following architectural assumptions within the CAPIF architecture: + +- An EAS may act as an API provider by implementing API provider domain functions (i.e. API exposing function, API publishing function, and API management function) +- An EAS may act as an API invoker +- An EES may act as a CAPIF provider by implementing CAPIF core function (CCF) + +Note: + +- EES provides support for the logging and audit of EAS API invocation as described in 3GPP TS 23.222[16], clause 8.19 and clause 8.22. +- EES control the service API access as specified in clause 8.12 of 3GPP TS 23.222 [16]. + +Based on the architectural assumption above, the essential operations regarding EAS Service APIs complying with CAPIF are as follows: + +- An EAS (acting as API provider) may publish its EAS Service APIs to EES (acting as CAPIF provider) and EES may further publish the EAS service APIs to remote EES via CCF interconnection. +- An EAS (acting as API invoker) may discover EAS Service APIs from EES (acting as CAPIF provider) and EAS Service APIs from remote EES via CCF interconnection +- An EAS (acting as API invoker) may subscribe to be notified of dynamic information or availability of EAS Service APIs from EES (acting as CAPIF provider) +- As EAS1(acting as API invoker) discovers EAS2 (acting as API provider) from EES, it can invoke the Service APIs directly from EAS2 + +#### 7.8.2.2 CAPIF operations in Edge Enabler Layer + +The Figure 7.8.2.2-1 depicts the essential operational steps for EAS Service API enablement using the CAPIF operations as shown in Annex A of TS 23.222 [16]. + +Pre-conditions: + +1. The EAS #A-1 and EAS #A-2 have completed the EAS registration with the EES #A. + +![Sequence diagram showing CAPIF operations in Edge Enabler Layer for EAS Service API enablement. The diagram involves four lifelines: EAS #A-1 (API Invoker), EAS #A-2 (API provider domain functions), EES #A (CCF), and EES #B (CCF). The sequence of messages is: 1. API provider domain functions registration (CAPIF-5) from EAS #A-2 to EES #A; 2. Service API publication (CAPIF-4) from EAS #A-2 to EES #A; 3. API invoker Onboarding (CAPIF-1) from EAS #A-1 to EES #A; 4. Service API discovery (CAPIF-1) from EAS #A-1 to EES #A; 5. Service API invocation (CAPIF-2) from EAS #A-1 to EAS #A-2; 6. Event subscription/notification (CAPIF-1) from EAS #A-1 to EES #A; 7. CCF interconnection (CAPIF-6) from EES #A to EES #B.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant EAS_A1 as EAS #A-1 +API Invoker + participant EAS_A2 as EAS #A-2 +API provider domain functions + participant EES_A as EES #A +CCF + participant EES_B as EES #B +CCF + + Note right of EAS_A2: 1. API provider domain functions registration (CAPIF-5) + EAS_A2->>EES_A: 1. API provider domain functions registration (CAPIF-5) + Note right of EAS_A2: 2. Service API publication (CAPIF-4) + EAS_A2->>EES_A: 2. Service API publication (CAPIF-4) + Note right of EAS_A1: 3. API invoker Onboarding (CAPIF-1) + EAS_A1->>EES_A: 3. API invoker Onboarding (CAPIF-1) + Note right of EAS_A1: 4. Service API discovery (CAPIF-1) + EAS_A1->>EES_A: 4. Service API discovery (CAPIF-1) + Note right of EAS_A1: 5. Service API invocation (CAPIF-2) + EAS_A1->>EAS_A2: 5. Service API invocation (CAPIF-2) + Note right of EAS_A1: 6. Event subscription/notification (CAPIF-1) + EAS_A1->>EES_A: 6. Event subscription/notification (CAPIF-1) + Note right of EES_A: 7. CCF interconnection (CAPIF-6) + EES_A->>EES_B: 7. CCF interconnection (CAPIF-6) + +``` + +Sequence diagram showing CAPIF operations in Edge Enabler Layer for EAS Service API enablement. The diagram involves four lifelines: EAS #A-1 (API Invoker), EAS #A-2 (API provider domain functions), EES #A (CCF), and EES #B (CCF). The sequence of messages is: 1. API provider domain functions registration (CAPIF-5) from EAS #A-2 to EES #A; 2. Service API publication (CAPIF-4) from EAS #A-2 to EES #A; 3. API invoker Onboarding (CAPIF-1) from EAS #A-1 to EES #A; 4. Service API discovery (CAPIF-1) from EAS #A-1 to EES #A; 5. Service API invocation (CAPIF-2) from EAS #A-1 to EAS #A-2; 6. Event subscription/notification (CAPIF-1) from EAS #A-1 to EES #A; 7. CCF interconnection (CAPIF-6) from EES #A to EES #B. + +**Figure 7.8.2.2-1: CAPIF operations in Edge Enabler Layer for EAS Service API enablement** + +1. The EAS #A-2 (AMF) registers its API provider domain functions to the EES #A (CCF) via CAPIF-5. +2. The EAS #A-2 (APF) publishes its exposing Service API(s) to the EES #A (CCF) via CAPIF-4. +3. The EAS #A-1 (API invoker) performs onboarding process with the EES #A (CCF) via CAPIF-1. +4. The EAS #A-1 (API invoker) discovers from the EES #A (CCF) a Service API required to run via CAPIF-1. +5. The EAS #A-1 (API invoker) invokes the Service API provided by EAS #A-2 (AEF) via CAPIF-2 as discovered from the EES #A (CCF). +6. The EAS #A-1 (API invoker) subscribes to notifications of any updates of target Service APIs on the EES #A (CCF) via CAPIF-1. +7. The EES #A (CCF) and EES #B (CCF) inter-operate with each other via CAPIF-6 for interconnection operations for publication and discovery of Service APIs managed by each EES. + +The Figure 7.8.2.2-2 depicts the distributed deployment of EESs (CCFs) as shown in clause 7.4 of TS 23.222 [16]. + +![Diagram illustrating the Distributed EES (CCF) deployment for API invocation across EES. The diagram shows a central CCF #C connected to two EES units, EES #A (CCF #A) and EES #B (CCF #B), via CAPIF-6 reference points. EES #A is connected to EAS #A-1 (API Invoker) via CAPIF-1/1e and to EAS #A-2 via CAPIF-3/3e. EES #B is connected to EAS #B via CAPIF-3/3e. All EES units and EAS #A-2 and EAS #B expose Service APIs to CCF #C via CAPIF APIs.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +graph LR + CCF_C[CCF #C] ---|CAPIF-6| EES_A[EES #A (CCF #A)] + CCF_C ---|CAPIF-6| EES_B[EES #B (CCF #B)] + EES_A ---|CAPIF-1/1e| EAS_A1[EAS #A-1 (API Invoker)] + EES_A ---|CAPIF-3/3e| EAS_A2[EAS #A-2] + EES_B ---|CAPIF-3/3e| EAS_B[EAS #B] + EES_A --- CAPIF_APIs_A((CAPIF APIs)) + EES_B --- CAPIF_APIs_B((CAPIF APIs)) + EAS_A2 --- Service_APIs_A2((Service APIs)) + EAS_B --- Service_APIs_B((Service APIs)) + CAPIF_APIs_A --- CCF_C + CAPIF_APIs_B --- CCF_C + Service_APIs_A2 --- CCF_C + Service_APIs_B --- CCF_C + +``` + +Diagram illustrating the Distributed EES (CCF) deployment for API invocation across EES. The diagram shows a central CCF #C connected to two EES units, EES #A (CCF #A) and EES #B (CCF #B), via CAPIF-6 reference points. EES #A is connected to EAS #A-1 (API Invoker) via CAPIF-1/1e and to EAS #A-2 via CAPIF-3/3e. EES #B is connected to EAS #B via CAPIF-3/3e. All EES units and EAS #A-2 and EAS #B expose Service APIs to CCF #C via CAPIF APIs. + +**Figure 7.8.2.2-2 Distributed EES (CCF) deployment for API invocation across EES** + +The essential operations regarding EES deployment and across EES API invocation complying with CAPIF are as follows + +- In the distributed deployment, EES#A (acting as CCF#A) and EES#B (acting as CCF#B) interact with CCF#C via CAPIF-6 reference point. The CCF#C assumes the role of a centralized repository of the service APIs in the PLMN trust domain.(e.g. Service APIs exposed by EAS #A-2 and EAS #B in the Figure) +- The EES#A and EES#B publishes the service API(which are published by EAS #A-2 and EAS #B respectively) provided by its connected API exposing function(s) to CCF#C, and obtains the service API information provided by other EES from centralized CCF#C +- EAS#A-1 (acting as API invoker) is able to discover and invoke the service APIs provided by EAS#B connected to CCF#B + +#### 7.8.2.3 Service KPIs in CAPIF for EAS Service APIs + +In TS 23.558, "Service KPI" IEs are specified to provide information about service characteristics provided by EASs; or required by ACs. This is used for discovery or provisioning of EASs which meet the Service KPIs required by ACs. + +In the similar manner, Service KPIs of EASs (as API Providers) need to be specified in CAPIF to be used for discovery or provisioning of EAS Service APIs which meet the Service KPIs required by EASs (as API Invokers). + +The proposed IEs in CAPIF as specified in 3GPP TS 23.222 [16] related to Service KPIs can be summarized as follows: + +- 1) Service KPIs provided by EAS as API Provider + - a. Service API publish request + - i. Service API information + - Service KPI (new IE): information about service characteristics provided by the Service API; can be mapped to EAS Service KPIs in EAS Profile [TS 23.558] of the EAS providing the Service API +- 2) Service KPIs required by EAS as API Invoker + - a. Onboard API invoker response + - i. Service API information + - Service KPI per API (new IE): information about service characteristics provided by the Service API which is allowed to access + - b. Service API discover request + +- i Query information + - Service KPI (new IE): information about service characteristics as a criterion for discovering matching Service APIs required by the API invoker + - c. Service API discover response + - i Service API information + - Service KPI per API (new IE): information about service characteristics provided by the Service API corresponding to the discovery request +- 3) Service KPIs for CAPIF interconnection between EESs +- a. Interconnection API publish request + - i Service API information + - Service KPI (new IE): information about service characteristics provided by the Service API which is published across CCFs (i.e. implemented in EESs) + - b. Interconnection service API discover request + - i Query information + - Service KPI (new IE): information about service characteristics as a criterion for discovering matching Service APIs across CCFs (i.e. implemented in EESs) + +The relevant information elements of CAPIF are listed as follows. The highlighted with bold text is proposed to add for supporting the Service KPIs. + +**Table 7.8.2.3-1: Service API publish request (Table 8.3.2.1-1 of TS 23.222 [16])** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API publisher information | M | The information of the API publisher may include identity, authentication and authorization information | +| Service API information | M | The service API information includes the service API name, service API type, communication type, description, Serving Area Information (optional), AEF location (optional), interface details (e.g. IP address, port number, URI), protocols, version numbers, and data format, (new) Service KPI . | +| Shareable information | O (see NOTE) | Indicates whether the service API or the service API category can be published to other CCFs. And if sharing, a list of CAPIF provider domain information where the service API or the service API category can be published is contained. | +| NOTE: If the shareable information is not present, the service API is not allowed to be shared. | | | + +**Table 7.8.2.3-2: Onboard API invoker response (Table 8.1.2.2-1 of TS 23.222 [16])** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Onboarding status | M | The result of onboarding request i.e. success indication is included if the API invoker is granted permission otherwise failure. | +| Enrolled information | O
(see NOTE 1) | Information from the provisioned API invoker profile which may include information to allow the API invoker to be authenticated and to obtain authorization for service APIs | +| Service API information | O
(see NOTE 2) | The service API information includes the service API name, service API type, communication type, description, Serving Area Information (optional), AEF location (optional), interface details (e.g. IP address, port number, URI), protocols, version numbers, and data format, (new) Service KPI . | +| Reason | O
(see NOTE 3) | This element indicates the reason when onboarding status is failure. | +| NOTE 1: Information element shall be present when onboarding status is successful. | | | +| NOTE 2: Information element may be present when onboarding status is successful. | | | +| NOTE 3: Information element shall be present when onboarding status is failure. | | | + +**Table 7.8.2.3-3: Service API discover request (Table 8.7.2.1-1 of TS 23.222 [16])** + +| Information element | Status | Description | +|---------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| API invoker identity information | M | Identity information of the API invoker discovering service APIs | +| Query information | M | Criteria for discovering matching service APIs (e.g. service API type, Serving Area Information (optional), preferred AEF location (optional), interfaces, protocols, (new) Service KPI ) (see NOTE) | +| NOTE: It should be possible to discover all the service APIs. | | | + +**Table 7.8.2.3-4: Service API discover response (Table 8.7.2.2-1 of TS 23.222 [16])** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates the success or failure of the discovery of the service API information | +| Service API information
(see NOTE 2) | O
(see NOTE 1) | List of service APIs corresponding to the request, including API description such as service API name, service API type, Serving Area Information (optional), interface details (e.g. IP address, port number, URI), protocols, version, data format, (new) Service KPI | +| CAPIF core function identity information | O
(see NOTE 1) | Indicates the CAPIF core function serving the service API category provided in the query criteria | +| NOTE 1: The service API information or the CAPIF core function identity information or both shall be present if the Result information element indicates that the service API discover operation is successful. Otherwise both shall not be present. | | | +| NOTE 2: If topology hiding is enabled for the service API, the interface details shall be the interface details of AEF acting as service communication entry point for the service API. | | | + +**Table 7.8.2.3-5: Interconnection API publish request (Table 8.25.2.1-1 of TS 23.222 [16])** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CCF information | M | The information of the CAPIF core function which publishes APIs, may include identity, authentication and authorization information | +| Service API information | O
(see NOTE 1) | The service API information includes the service API name, service API type, communication type, description, Serving Area Information (optional), AEF location (optional), interface details (e.g. IP address, port number, URI), protocols, version numbers, and data format, (new) Service KPI . | +| Service API category | O
(see NOTE 1) | The category of the service APIs to be published, (e.g. V2X, IoT) | +| Shareable information | O
(see NOTE 2) | Indicates whether the service API or the service API category can be published to other CCFs. And if sharing, a list of CAPIF provider domain information where the service API or the service API category can be published is contained. | +| NOTE 1: At least one of the Service API information or Service API category shall be present. | | | +| NOTE 2: If the shareable information is not present, the service API is not allowed to be shared. There is one and only one CAPIF provider domain information sharable via the CAPIF-6e interface. | | | + +**Table 7.8.2.3-6: Interconnection service API discover request (Table 8.25.2.3-1 of TS 23.222 [16])** + +| Information element | Status | Description | +|---------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CAPIF core function identity information | M | Identity information of the CAPIF core function discovering service APIs | +| Query information | M | Criteria for discovering matching service APIs or CAPIF core function (e.g. service API type, Serving Area Information (optional), preferred AEF location (optional), interfaces, protocols, service API category, (new) Service KPI ) (see NOTE) | +| NOTE: It should be possible to discover all the service APIs. | | | + +The EAS Service KPIs is defined as below + +**Table 7.8.2.3-7: EAS Service KPIs** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------| +| Maximum Request rate | O | Maximum request rate from the API Invoker supported by the server. | +| Maximum Response time | O | The maximum response time advertised for the API Invoker's service requests. | +| Availability | O | Advertised percentage of time the server is available for the API Invoker's use. | +| Available Compute | O | The maximum compute resource available for the API Invoker. | +| Available Graphical Compute | O | The maximum graphical compute resource available for the API Invoker. | +| Available Memory | O | The maximum memory resource available for the API Invoker. | +| Available Storage | O | The maximum storage resource available for the API Invoker. | +| Connection Bandwidth | O | The connection bandwidth in Kbit/s advertised for the API Invoker's use. | +| NOTE: If API invoker is on UE then the maximum response time includes the round-trip time of the request and response packet, the processing time at the server and the time required by the server to consume 3GPP Core Network capabilities, if any. | | | + +In TS 23.222 [16], the Service KPIs can be specified as a part of *Query information* and *Service API information* in abstract, so that the Service KPI IE can be implemented as one or more new attributes of *ServiceAPIDescription* data type in TS 29.222 (but it's up to the CT3's work). + +### 7.8.3 Solution evaluation + +This solution allows for an EAS to expose its Service APIs towards the other EASs. It exploits CAPIF as specified in 3GPP TS 23.222 [16] for publication/discovery, and change subscription of EAS Service APIs. + +This solution addresses the key issue #2: enablement of service APIs exposed by EAS as specified in the clause 4.2; and fulfils the architectural requirements for enablement of service APIs exposed by EAS as specified in the clause 5.2. + +This solution relies on the EDGEAPP architecture as specified in TS 23.558 [2] with extended capabilities of EAS and EES for publication/discovery of EAS Service APIs but there is no impact to the APIs and procedures of EDGEAPP since the extended capabilities can be realized using CAPIF. + +This solution relies on the CAPIF as specified in TS 23.222 [16] with some updates on the information elements of the CAPIF APIs for publish/discovery. + +## 7.9 Solution #9: Application traffic influence trigger from EAS + +### 7.9.1 Architecture enhancements + +None. + +### 7.9.2 Solution description + +#### 7.9.2.1 General + +This solution addresses key issue 14. An EAS can explicitly request EES including necessary information to influence the EAS traffic from UE(s). Then the EES can trigger the AF request to influence traffic routing towards the 3GPP CN for one or more UE(s) accessing the EAS. + +#### 7.9.2.2 Procedure + +![Sequence diagram showing the procedure for AF influence the traffic for EAS. The diagram involves three entities: EAS, EES, and 5GC. The sequence of messages is: 1. EAS sends an 'EAS traffic influence request' to EES. 2. EES performs an 'Authorization check and processing the request' (shown as a self-call). 3. EES sends an 'Application traffic influence' message to 5GC. 4. 5GC sends an 'EAS traffic influence response' back to EAS.](37819f1170c36655c57129b6bd8a5ceb_img.jpg) + +``` +sequenceDiagram + participant EAS + participant EES + participant 5GC + Note right of EES: 2. Authorization check and processing the request + Note right of 5GC: 3. Application traffic influence + EAS->>EES: 1. EAS traffic influence request + EES-->>EES: + EES->>5GC: + 5GC-->>EAS: 4. EAS traffic influence response +``` + +Sequence diagram showing the procedure for AF influence the traffic for EAS. The diagram involves three entities: EAS, EES, and 5GC. The sequence of messages is: 1. EAS sends an 'EAS traffic influence request' to EES. 2. EES performs an 'Authorization check and processing the request' (shown as a self-call). 3. EES sends an 'Application traffic influence' message to 5GC. 4. 5GC sends an 'EAS traffic influence response' back to EAS. + +Figure 7.9.2.2: AF influence the traffic for EAS + +1. The EAS sends an EAS traffic influence request. +2. The EES performs an authorization check to verify whether the EAS has the authorization to request application traffic influence. The EES includes target DNAI, traffic descriptor information and N6 routing information at + +target DNAI in the Nnef\_TrafficInfluence\_Create/Update Request to the NEF, or Npcf\_PolicyAuthorization\_Create/Update Request to the PCF. + +3. Upon successful authorization, the EES sends the traffic influence request to 5GC to influence the traffic for EAS as described in 3GPP TS 23.501, clause 5.6.7.1. +4. The EES sends the EAS traffic influence response. + +**Table 7.9.2.2-1: EAS traffic influence request** + +| Information element | Status | Description | +|----------------------|--------|------------------------------------------------------------------------------------------------| +| EASID | M | Identifier of the EAS | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | + +**Table 7.9.2.2-2: EAS traffic influence response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| Successful response | O | Indicates that the traffic influence request was successful. | +| Failure response | O | Indicates that the traffic influence request has failed. | +| > Cause | O | Indicates the cause of failure | + +### 7.9.3 Solution evaluation + +This solution addresses key issue 14, it is applicable to the scenario where the EAS triggers the EES to perform traffic influence. This solution has no impact to the R17 EDGEAPP architecture. + +## 7.10 Solution #10: low power mode support + +### 7.10.1 Architecture enhancements + +None. + +### 7.10.2 Solution description + +#### 7.10.2.1 General + +The following solution corresponds to the key issue #15 on supporting of constrained devices for Edge. + +For the constrained UEs, there are two aspects should be considered to reduce the power consumption, one is help UE turn into idle mode or DRX mode when there is no traffic transmitting between UE and network, another one is help to reduce the traffic data rate when UE is connected to the network with transmitting packets. + +EEC can get the knowledge about the constrained UE. When the applications are running with high power consumption, or the UE decides that the battery level is low and should start power saving, the EEC should send messages to EES with carrying such indication for low-power consumption requirement and specific application identifier. + +When EES gets low-power consumption indication from EEC, the EES should trigger two methods to satisfy the constrained UE requirement. + +Method1: EES should send the message to corresponding EAS through EDGE-3 that the data rate should be reduced, so that the downlink data will be reduced and UE do not need to process high-bandwidth traffic. How to balance the low-power consumption requirement and the UE experience is based on the EAS implementation. + +Method2: EES should send the UE's low-power consumption indication to 3GPP core network. The 3GPP system may trigger some specific policies or treatment for such applications and UEs e.g. changing the QoS profile AM policies e.g. update UE-AMBR, UE- slice MBR, RFSP index and/or service area restriction, for those UEs as specified in TS 23.502 clause 4.15.6.9, and changing the SM policies e.g. downgrade the QoS (e.g. reducing Requested Guaranteed Bitrate, Requested Maximum Bitrate) as specified in TS 23.502 clause 4.15.6.6. + +This method may not satisfy the high-level experience of the application but can support the application running basically. + +#### 7.10.2.2 Procedure + +Pre-condition: + +1. The AC-EAS cannot handle the negotiation at the application layer. + +![Sequence diagram illustrating the low power mode support procedure. The diagram shows four lifelines: EEC, EES, EAS, and 3GPP core network. The sequence of messages is: 1. EEC sends low-power indication to EES; 2a. EES sends low power indication to EAS; 2b. EES requests 3GPP CN to change policies; 3a. EAS response; 3b. 3GPP network response; 4. EES response to EEC.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES + participant EAS + participant 3GPP as 3GPP core network + Note left of EEC: 1. EEC sends low-power indication to EES + EEC->>EES: + Note right of EES: 2a. EES sends low power indication to EAS + EES->>EAS: + Note right of EES: 2b. EES requests 3GPP CN to change policies + EES->>3GPP: + Note right of EAS: 3a. EAS response + EAS->>EES: + Note right of 3GPP: 3b. 3GPP network response + 3GPP->>EES: + Note right of EES: 4. EES response to EEC + EES->>EEC: + +``` + +Sequence diagram illustrating the low power mode support procedure. The diagram shows four lifelines: EEC, EES, EAS, and 3GPP core network. The sequence of messages is: 1. EEC sends low-power indication to EES; 2a. EES sends low power indication to EAS; 2b. EES requests 3GPP CN to change policies; 3a. EAS response; 3b. 3GPP network response; 4. EES response to EEC. + +**Figure 7.10.2.2-1: low power mode support** + +1. The EEC sends low-power consumption indication to EES with UE Identifier, EEC ID, AC ID, low-power consumption indicator, which indicating a constrained UE, and triggers the low power consumption enhancement. +- 2a. When EES gets the low-power consumption indication, the EES may send low power indication to EAS to request corresponding EAS to reduce the downlink packets, which can help constrained UE process the application with constrained power consumption. The request could provide the UE Identifier(s). +- 2b. When EES gets the low-power consumption indication, the EES may request 3GPP core network to update the QoS policy to support constrained UE, e.g. EES could act as an AF to set up a session with required QoS procedure as specified in TS 23.502 clause 4.15.6.6. +- 3a. The EAS responds to EES to indicate the low-power processing is successful or failure. +- 3b. the 3GPP core network responds to EES with successful or failure. +4. EES response to EEC. + +### 7.10.3 Solution evaluation + +This solution addresses KI#15 by either sending the message to corresponding EAS to reduce data rate, or triggering some specific policies or treatment for such applications and UEs to reduce the Requested Guaranteed Bitrate, Requested Maximum Bitrate. + +Editor's note: Whether this solution works for all scenarios and should it be considered in the normative work is FFS. + +Editor's note: It is FFS whether downgrade the QoS can achieve the UE power saving. + +## 7.11 Solution #11: A deployment option for alignment with ETSI MEC using CAPIF + +### 7.11.1 Architecture enhancements + +None. + +### 7.11.2 Solution description + +#### 7.11.2.1 General + +This solution addresses "KI#5: Alignment of EDGEAPP and ETSI MEC" in alignment with ETSI MEC using CAPIF for exposing and invoking Service APIs as well as "KI#2: Enablement of Service APIs exposed by EAS" for exposing EAS Service APIs to ETSI MEC entities. It specifies a CAPIF deployment option for: + +1. allowing EASs to invoke MEC services, and +2. exposing Service APIs provided by EES or EAS (as described in KI#2) to MEC Applications + +The following architecture is proposed to use CAPIF for alignment with ETSI MEC in terms of exposing EAS/EES Service APIs and invoking MEC Services as a deployment option. + +Based on the proposed deployment option, the alignment of EDGEAPP and ETSI MEC could be done by mapping or complementing their own APIs to CAPIF APIs, especially for invoking/exposing Service APIs and MEC Services. + +Note that Figure 7.11.2.1-1 below is to illustrate what EDGEAPP and ETSI MEC could look like when they exploit CAPIF for invoking and exposing their APIs. There is no such architecture defined in EDGEAPP or ETSI MEC as shown in Figure 7.11.2.1-1. + +![Figure 7.11.2.1-1: A deployment option for alignment with ETSI MEC using CAPIF. The diagram shows three main architectural layers separated by dashed lines. The top layer, 'EAS + API Invoker', contains an 'API Invoker' and an 'EAS' block. It has an outgoing arrow labeled 'Invoking MEC Service (CAPIF-2)'. The middle layer, 'EES + CAPIF Provider + API Provider', contains a 'CAPIF Core Function', an 'EES' block with 'EES Service APIs', and a 'Service APIs' block with 'API exposing function', 'API publishing function', and 'API management function'. It receives arrows labeled 'Discover EAS Service API & MEC Service (CAPIF-1)', 'Invoking EES Service API (EDGE-3)', and 'Invoking EES Service API (CAPIF-2)'. The bottom layer, 'MEC Platform + CAPIF Provider + API Provider', contains a 'CAPIF Core Function', 'MEC Services' (MEP, MEC App), and a 'Service APIs' block similar to the middle layer. It receives an arrow labeled 'Invoking EAS Service API (CAPIF-2)'. A dashed line labeled 'CCF Inter-connection (CAPIF-6)' separates the middle and bottom layers. On the left, an 'EAS + API Provider' block contains 'EAS Service APIs', 'EAS', and a 'Service APIs' block, with an arrow labeled 'CAPIF-3,4,5' pointing to the middle layer's CAPIF Core Function.](bd57a547bec253d4179e5c4491c53dbb_img.jpg) + +Figure 7.11.2.1-1: A deployment option for alignment with ETSI MEC using CAPIF. The diagram shows three main architectural layers separated by dashed lines. The top layer, 'EAS + API Invoker', contains an 'API Invoker' and an 'EAS' block. It has an outgoing arrow labeled 'Invoking MEC Service (CAPIF-2)'. The middle layer, 'EES + CAPIF Provider + API Provider', contains a 'CAPIF Core Function', an 'EES' block with 'EES Service APIs', and a 'Service APIs' block with 'API exposing function', 'API publishing function', and 'API management function'. It receives arrows labeled 'Discover EAS Service API & MEC Service (CAPIF-1)', 'Invoking EES Service API (EDGE-3)', and 'Invoking EES Service API (CAPIF-2)'. The bottom layer, 'MEC Platform + CAPIF Provider + API Provider', contains a 'CAPIF Core Function', 'MEC Services' (MEP, MEC App), and a 'Service APIs' block similar to the middle layer. It receives an arrow labeled 'Invoking EAS Service API (CAPIF-2)'. A dashed line labeled 'CCF Inter-connection (CAPIF-6)' separates the middle and bottom layers. On the left, an 'EAS + API Provider' block contains 'EAS Service APIs', 'EAS', and a 'Service APIs' block, with an arrow labeled 'CAPIF-3,4,5' pointing to the middle layer's CAPIF Core Function. + +Figure 7.11.2.1-1: A deployment option for alignment with ETSI MEC using CAPIF + +The proposed deployment option can be realized with the following implementations: + +##### 1) 3GPP EDGEAPP + +- a. EES may implement CAPIF Core Function to manage the Service APIs exposed by EAS and EES; +- b. EES may implement CAPIF Core Function to interconnect with CCF of ETSI MEC via CAPIF-6 +- c. EAS may implement CAPIF API Provider functions in order to expose EAS Service APIs to EDGEAPP EASs or ETSI MEC Applications +- d. EAS may implement CAPIF API Invoker function to invoke EAS Service APIs or ETSI MEC Services +- e. EAS may invoke EES Service APIs via EDGE-3 +- f. EES may implement CAPIF API Provider functions in order to expose EES Service APIs (e.g. UE location API, AC information exposure API, etc.) to API invokers (e.g. EASs, ETSI MEC Applications) + - i.e. EES Service APIs (as well as EAS Service APIs) need to be published to CAPIF Core Function + +##### 2) ETSI MEC (out of the SA6 scope) + +- a. ETSI MEC (e.g. MEP) may implement CAPIF Core Function to manage the MEC Services exposed by MEP and MEC App. +- b. ETSI MEC (e.g. MEP) may implement CAPIF Core Function to interconnect with CCF of EDGEAPP EES via CAPIF-6 +- c. ETSI MEC (e.g. MEP, MEC App.) may implement CAPIF API Provider functions in order to enable EDGEAPP EASs to invoke MEC Services via CAPIF-2 +- d. ETSI MEC (e.g. MEC App.) may implement CAPIF API Invoker function to invoke EDGEAPP EAS|EES Service APIs + +NOTE: Refer to Annex B.2 of ETSI GS MEC 011 [14] for mapping MEC service management API to CAPIF APIs. + +#### 7.11.2.2 Procedure + +The procedures for API publication, API discovery, API invocation, and CCF interconnection are as specified in TS 23.222 [16]. + +### 7.11.3 Solution evaluation + +This solution provides a deployment option for alignment with ETSI MEC using CAPIF. + +This solution addresses KI#5: Alignment of EDGEAPP and ETSI MEC as specified in the clause 5.5; and KI#2: Enablement of Service APIs exposed by EAS as specified in the clause 5.2. + +This solution relies on the EDGEAPP architecture as specified in TS 23.558 [2] with extended roles of EAS and EES as CAPIF entities and extended roles of ETSI MEC entities like MEP as CAPIF entities to support the alignment of discovery and invocation of EES|EAS Service APIs and MEC Services by ETSI MEC and EDGEAPP entities, respectively. + +This solution also relies on the CAPIF as specified in TS 23.222 [16]. + +## 7.12 Solution #12: Service continuity planning permission + +### 7.12.1 Architecture enhancements + +None. + +### 7.12.2 Solution description + +#### 7.12.2.1 General + +This solution addresses the key issue #3 on enhancements to service continuity planning and the key issue #12 on EEL service differentiation. + +In this solution, the EEC provides its capability to perform service continuity planning and the EES can provide information about allowing the service continuity planning. + +#### 7.12.2.2 Procedure + +Pre-conditions: + +1. EEC knows whether the planned or predicted UE mobility behaviour is available. +2. The EES is locally configured with the UE-specific service information (as specified in the NOTE 2 in clause 8.5.2.2 of TS 23.558) and the ECSP policy indicating whether the service continuity planning is allowed or not for each EAS(s). + +NOTE: Details of the ECSP policy and how to configure such ECSP policy into the EES is not the scope of this solution + +![Sequence diagram showing the service continuity planning permission during EEC Registration procedure. The diagram involves two lifelines: EEC and EES. Step 1: EEC sends an 'EEC registration request' to EES. Step 2: EES performs 'Process the request (Policy authorization for the service continuity planning)'. Step 3: EES sends an 'EEC Registration response' back to EEC, with a note 'indicating whether service continuity planning is allowed or not'.](303fadfb9def251d1575d6221199b158_img.jpg) + +``` +sequenceDiagram + participant EEC + participant EES + Note right of EES: 2. Process the request +(Policy authorization for the +service continuity planning) + EEC->>EES: 1. EEC registration request + EES-->>EEC: 3. EEC Registration response + Note left of EEC: indicating whether service continuity planning is +allowed or not +``` + +Sequence diagram showing the service continuity planning permission during EEC Registration procedure. The diagram involves two lifelines: EEC and EES. Step 1: EEC sends an 'EEC registration request' to EES. Step 2: EES performs 'Process the request (Policy authorization for the service continuity planning)'. Step 3: EES sends an 'EEC Registration response' back to EEC, with a note 'indicating whether service continuity planning is allowed or not'. + +**Figure 7.12.2.2-1: Service continuity planning permission during EEC Registration procedure** + +1. The EEC provides EEC Service Continuity Support or indication to request service continuity planning permission when sending EEC Registration request. The request message may contain the capability of EEC to detect and provide information about planned or predicted UE mobility behaviour (e.g. including whether the UE moves to the expected/predicted location or not). +2. If the EEC Registration request message includes EEC Service Continuity Support or indication to request service continuity planning permission, the EES verifies if the service continuity planning is allowed or not for the EEC based on the ECSP policy or the request from the EAS provider. If the EEC indicates to the EES in step 1 that it cannot detect information about predicted UE mobility behaviour, then the EES monitors predicted UE mobility (e.g. including whether the UE moves to the expected/predicted location or not for service continuity planning.). + +If AC profile(s) is provided in step 1, the EES may verify whether the service continuity planning is allowed or not for each EAS(s) matched with the AC profile(s) based on the ECSP policy or the request from the EAS provider. + +3. The EES sends EEC Registration response including indication on whether service continuity planning is allowed or not. + +If the EEC receives the indication that service continuity planning is allowed in step 3, and after the available ACR scenarios are determined for the EEC, the EEC detects or acquires the planned or predicted UE mobility behaviour according to the determined ACR scenarios. If the EES verifies and indicates the service continuity planning permission per application to the EEC in step 2-3, the EEC performs the required detection or + +acquisition of the planned or predicted UE mobility behaviour for the EASs allowed for service continuity planning according to the determined ACR scenarios. + +If the EEC is indicated that service continuity planning is not allowed, the EEC does not issue the application context relocation request for service continuity planning. + +NOTE: If the EEC is indicated that service continuity planning is not allowed, the EEC does not perform detecting or acquiring the planned or predicted UE mobility behaviour for the purpose of service continuity planning. + +### 7.12.3 Solution evaluation + +This solution addresses the key issue #3 on enhancements to service continuity planning and the key issue #12 on EEL service differentiation. The proposed solution enables ECSP(s) to allow the service continuity planning selectively for UEs or for applications. For example, the service continuity will be enabled only if the resources are sufficient and if the UE (e.g. of a premium user) is allowed for the predicted application context relocation. In this regard, the solution #13 proposes potential impact on information to communicate within EEL in order to enable service differentiation of the service continuity planning. Specifically, the solution introduces the following impacts on the EEC and the EES: + +- The EEC supports to provide indication to request service continuity planning permission and its capability to perform service continuity planning; and +- The EES supports to verify if the service continuity planning is allowed and provide information about the permission of the service continuity planning to the EEC. + +## 7.13 Solution #13: Update ECS configuration information + +### 7.13.1 Architecture enhancements + +None. + +### 7.13.2 Solution description + +This solution addresses key issue #6 on edge services support across ECSPs and key issue #10 on support for roaming UEs in the case where the ECS manages other ECSP's EES information. + +This solution proposes to include supported PLMN ID(s) and optionally supported ECSP ID(s) in the ECS in the ECS configuration information as described in the following table: + +**Table 7.13.2-1: ECS configuration information per ECS** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------| +| ... | ... | ... | +| Supported PLMN ID(s) | O | The identifier of the PLMNs of which EDN configuration information can be provided by the ECS as spatial validity condition. | +| >Supported ECSP List (NOTE) | O | The identifier of the ECSP(s) that is contracted with the ECS Provider and its information is available at the ECS, i.e. EES provider ID(s) | +| >> ECSP ID | M | Identifier of the ECSP | +| NOTE: If the ECSP providing EESs does not want to expose its EES deployment information or business relationship-related information to other ECSPs, this IE is not be included. | | | + +NOTE 1: In Table 7.13.2-1, the Supported ECSP List information can be associated per PLMN based on the relationships in clause 9.1.1. If ECSPs and PLMN operators do not want to explicitly expose their relationship in the ECS configuration information, the Supported ECSP List information may either not be associated with the Supported PLMN ID or not be included. + +NOTE 2: Except in LBO roaming scenario, when the ECS configuration in Table 7.13.2-1 is successfully stored in the UDM, the H-SMF can provide ECS Configuration Information including a VPLMN ID. In this case, UE can use the ECS Configuration Information to get EDN configuration information of the VPLMN only when the UE is registered via a cell of the VPLMN. + +The above ECS configuration information may be provisioned to the 5GC procedure (see 3GPP TS 23.502 [8]) or configured in an ECS so that it can be used to select proper other ECS in solution #4 of clause 7.4. + +NOTE 3: How to provision the updated ECS configuration information via the 5GC is SA2's responsibility. + +### 7.13.3 Solution evaluation + +This solution addresses key issue #10 on support for roaming UEs. + +This solution proposes to include additional information in the ECS configuration information in order to provide the 5G core network and the EEC with PLMN ID(s), which can be used to select ECS to be used in scenarios of roaming. + +This solution has no architectural enhancements. + +## 7.14 Solution #14: V-ECS Discovery via the H-ECS + +### 7.14.1 Architecture enhancements + +The EDGE-10 reference point, which is shown in clause 6.1.1.1, may be used between the V-ECS and H-ECS. + +### 7.14.2 Solution description + +#### 7.14.2.1 General + +This solution addresses aspects of Key Issue #10. Specifically, the solution explains how the EEC in the roaming UE knows the availability of ECS(s) and/or EES(s) and discovers them in the VPLMN. + +The principle of this solution is that, when roaming, the H-ECS provides information to the UE so that the EEC can communicate with an ECS in the VPLMN (i.e. a V-ECS). The UE can then use a home routed PDU Session to communicate with an H-ECS and an LBO PDU Session to communicate with a V-ECS. In this solution, the home network does not need to provide V-EES information to the EEC. The EEC can discover V-EES information by interacting directly with the V-ECS. + +As explained in 3GPP TS 23.501 [5]: *"The HPLMN can control via subscription data per DNN and per S-NSSAI whether a PDU Session is to be set-up in HR or in LBO mode."* This solution explains how the H-ECS can provide information to the UE that can be used to establish an LBO PDU Session that is used to reach a V-ECS. + +As one option, the H-ECS can provide an FQDN or an IP Address of a V-ECS to the EEC. When the UE accesses the provided FQDN or IP Address, URSP rules may steer the UE to use a DNN/S-NSSAI combination that can be used to reach the V-ECS (e.g. an LBO Session). + +As a second option, the H-ECS can provide a DNN / S-NSSAI combination to the EEC. In this case, the DNN / S-NSSAI combination may be used to send a PDU Session Establishment Request that will result in an LBO PDU Session. The SMF in the VPLMN may then send ECS Address Configuration Information to the UE as described in 3GPP TS 23.548 [19]. The EEC may then use the ECS FQDN or IP Address from the ECS Address Configuration Information to reach the V-ECS. + +#### 7.14.2.2 Procedure + +The procedures present high-level overview of Solution #14. + +##### 7.14.2.2.1 V-ECS Discovery via the H-ECS by request-response + +![Sequence diagram illustrating V-ECS Discovery via the H-ECS by request-response. The diagram shows interactions between EEC, H-ECS, 3GPP Core Network, V-ECS #1, and V-ECS #2. The process involves a Service Provisioning Request from EEC to H-ECS, a Monitoring Request/Response between H-ECS and 3GPP Core Network, a V-ECS Information Request from H-ECS to V-ECS #1, a V-ECS Information Response from V-ECS #1 to H-ECS, a Service Provisioning Response (V-ECS Contact Information) from H-ECS to EEC, a PDU Session Establishment between EEC and 3GPP Core Network, a Service Provisioning Request from EEC to V-ECS #2, and a Service Provisioning Response from V-ECS #2 to EEC.](164d1b48231be457522b31965610ea3b_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant H-ECS + participant 3GPP Core Network + participant V-ECS #1 + participant V-ECS #2 + + Note right of H-ECS: 2. Monitoring Request / Response + Note right of 3GPP Core Network: 6. PDU Session Establishment + + EEC->>H-ECS: 1. Service Provisioning Request + H-ECS->>3GPP Core Network: 2. Monitoring Request / Response + H-ECS-->>V-ECS #1: 3. V-ECS Information Request + V-ECS #1-->>H-ECS: 4. V-ECS Information Response + H-ECS->>EEC: 5. Service Provisioning Response (V-ECS Contact Information) + EEC->>3GPP Core Network: 6. PDU Session Establishment + EEC->>V-ECS #2: 7. Service Provisioning Request + V-ECS #2->>EEC: 8. Service Provisioning Response + +``` + +Sequence diagram illustrating V-ECS Discovery via the H-ECS by request-response. The diagram shows interactions between EEC, H-ECS, 3GPP Core Network, V-ECS #1, and V-ECS #2. The process involves a Service Provisioning Request from EEC to H-ECS, a Monitoring Request/Response between H-ECS and 3GPP Core Network, a V-ECS Information Request from H-ECS to V-ECS #1, a V-ECS Information Response from V-ECS #1 to H-ECS, a Service Provisioning Response (V-ECS Contact Information) from H-ECS to EEC, a PDU Session Establishment between EEC and 3GPP Core Network, a Service Provisioning Request from EEC to V-ECS #2, and a Service Provisioning Response from V-ECS #2 to EEC. + +**Figure 7.14.2.2.1-1: V-ECS Discovery via the H-ECS by request-response** + +1. The EEC sends a Service Provisioning Request to an ECS in the home network via a home routed PDU session. As described in 3GPP TS 23.558 [2], clause 8.3.3.3.7, the Service Provisioning Request may include the identity of the PLMN that the UE is currently registered to. +2. If the Service Provisioning Request from the EEC did not include a PLMN ID, then the ECS may invoke the NEF's monitoring event API with the monitoring type set to ROAMING\_STATUS and the plmnIndication set to TRUE as described in 3GPP TS 29.522 [17] and 3GPP TS 29.122 [18]. The ECS receives a response from the NEF. The response indicates if the UE is roaming and the identity of the UE's serving PLMN. +3. If the H-ECS is already provisioned with ECS Discovery Information that can be sent to the UE (e.g. via OAM), then steps 3 and 4 may be skipped. In this step, the H-ECS may send a V-ECS Information Request to a V-ECS of the PLMN that the UE is currently registered in order to obtain the information that should be sent to the UE so that the UE can establish an LBO PDU Session in the VPLMN. The V-ECS Information Request can include the UE's location information. + +The H-ECS can use the PLMN ID to determine the V-ECS to contact. For example, this can be based on a DNS lookup or the addresses of V-ECSs may have been pre-configured in the H-ECS (e.g. via OAM). If the VPLMN hosts multiple V-ECSs, then which V-ECS is resolved can be based on configuration. + +4. The V-ECS responds to the H-ECS with a V-ECS Information Response. The V-ECS Information Response can include a DNN (O), and S-NSSAI (O) that can be used by the UE to establish an LBO PDU Session in the VPLMN. The V-ECS can use the UE's location to determine what DNN (O), and S-NSSAI (O) should be sent to the UE in order to cause the UE to establish an LBO PDU Session with a suitable DNN/S-NSSAI combination. + +**NOTE:** The information that is used by the H-ECS to contact the V-ECS can be different than the information that is used by the EEC to contact a V-ECS. As shown in Figure 7.14.2.2-1, the ECS that is contacted by the UE may be different. + +Example 1: The UE only requires a DNN/S-NSSAI combination to establish an LBO PDU Session and get provisioned with a V-ECS FQDN during PDU Session Establishment. + +4. The ECS sends a Service Provisioning Response. The Service Provisioning Response may include a new information element called ECS Discovery Information. The ECS Discovery Information may include ECS Contact Information (O, i.e. an FQDN of an ECS in the VPLMN), ECS Provider ID (O), DNN (O), and S-NSSAI (O). +6. The UE establishes an LBO PDU Session that will be used to communicate with a V-ECS and/or to obtain ECS Contact Information from the VPLMN. + +The ECS Discovery Information from step 5 may include only ECS Contact Information. In this case, URSP rules may steer the UE to use a DNN/S-NSSAI combination that can be used to reach the ECS (e.g. an LBO Session). + +The ECS Discovery Information from step 5 may include a DNN / S-NSSAI combination. In this case, the combination may be used to send a PDU Session Establishment Request that will result in an LBO session. The SMF in the VPLMN may then send ECS Address Configuration Information to the UE as described in 3GPP TS 23.548 [19]. + +7. The EEC sends a Service Provisioning Request to an ECS in the visited network. The ECS that is contacted in this step (i.e. V-ECS-2) may be different than the ECS that was contacted in steps 3 and 4 (i.e. V-ECS-1). The ECS address was obtained in step 5 or step 6. +8. The EEC receives a Service Provisioning Response via the LBO PDU session that was established in step 6. As described in step 5, the ECS service provisioning response may include ECS Contact Information for other ECS(s) in the VPLMN. For example, the ECS that was contacted in step 7 may be a "primary" ECS of the VPLMN and the "primary" ECS of the VPLMN may provide the UE with ECS Contact Information for other ECS(s) in this step. + +##### 7.14.2.2.2 V-ECS Discovery via the H-ECS by subscribe-notify + +![Sequence diagram for V-ECS Discovery via the H-ECS by subscribe-notify. The diagram shows interactions between EEC, H-ECS, 3GPP Core Network, V-ECS #1, and V-ECS #2. The process involves subscription, monitoring, information requests, and subsequent service provisioning.](b612b838f94982799a69461ffb078a73_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant H-ECS + participant 3GPP Core Network + participant V-ECS #1 + participant V-ECS #2 + + Note left of EEC: PDU Session Establishment (Step 8) + EEC->>H-ECS: 1. Service Provisioning Subscription Request + H-ECS->>3GPP Core Network: 2. Monitoring Subscription Request / Response + 3GPP Core Network-->>H-ECS: 3. Service Provisioning Subscription Response + H-ECS->>3GPP Core Network: 4. Monitoring Notify + H-ECS-->>V-ECS #1: 5. V-ECS Information Request + V-ECS #1-->>H-ECS: 6. V-ECS Information Response + H-ECS->>EEC: 7. Service Provisioning Notify (V-ECS Contact Information) + Note right of 3GPP Core Network: PDU Session Establishment (Step 8) + EEC->>V-ECS #2: 9. Service Provisioning Request + V-ECS #2-->>EEC: 10. Service Provisioning Response + +``` + +Sequence diagram for V-ECS Discovery via the H-ECS by subscribe-notify. The diagram shows interactions between EEC, H-ECS, 3GPP Core Network, V-ECS #1, and V-ECS #2. The process involves subscription, monitoring, information requests, and subsequent service provisioning. + +Figure 7.14.2.2.2-1: V-ECS Discovery via the H-ECS by subscribe-notify + +1. The EEC sends a Service Provisioning Subscription Request to an ECS in the home network via a home routed PDU session. As described in 3GPP TS 23.558 [2], clause 8.3.3.3.7, the Service Provisioning Subscription Request may include the identity of the PLMN that the UE is currently registered to. +2. The ECS invokes the NEF's monitoring event API with the monitoring type set to ROAMING\_STATUS and the plmnIndication set to TRUE as described in 3GPP TS 29.522 [17] and 3GPP TS 29.122 [18]. The H-ECS receives a response from the NEF. +3. The ECS sends Service Provisioning Subscribe Response to the EEC. +4. If the UE is roaming and is detected by the 5GC network, the 5GC sends notification to the H-ECS. The notification indicates if the UE is roaming and the identity of the UE's serving PLMN. + +Steps 5 and 6 are the same as steps 3 and 4 of Figure 7.14.2.2.1-1. If the H-ECS is already provisioned with ECS Discovery Information that can be sent to the UE (e.g. via OAM), then steps 5 and 6 may be skipped. + +7. The ECS sends Service Provisioning Notify to the EEC. The Service Provisioning Notify may include a new information element called ECS Discovery Information. The ECS Discovery Information may include ECS Contact Information (i.e. an FQDN of an ECS in the VPLMN, O), ECS Provider ID (O), DNN (O), and S-NSSAI (O). + +Steps 8-10 is the same as steps 6-8 of Figure 7.14.2.2.1-1. + +### 7.14.3 Solution evaluation + +Solution #4 and this solution share the principle that the home network can provide the UE with information that is used to contact a V-ECS. In solution #4 the V-ECS information may be an address, endpoint or service API information. In this solution, the V-ECS information can include a DNN (O) and/or S-NSSAI (O). The DNN / S-NSSAI can be used to establish an LBO PDU Session. Once the UE establishes an LBO PDU Session, Rel-17 procedures can be used to discover the V-ECS address. This solution and Solution #5 both include an option where EDGE-10 is used between the H-ECS and V-ECS to obtain the V-ECS information that can be sent to the UE. For example, the V-ECS may provide the H-ECS with a DNN/S-NSSAI combination that can be used by the UE to establish an LBO PDU Session. This solution additionally includes an option where OAM provisioning is used to provide the H-ECS with the V-ECS information. + +## 7.15 Solution #15: Initial EAS selection declaration + +### 7.15.1 Architecture enhancements + +None. + +### 7.15.2 Solution description + +This solution addresses KI#8 and KI#14. In this solution, the EES can know the selected EAS and the EES is enabled to trigger the EAS traffic influence after initial EAS is being determined. + +![Sequence diagram for Initial EAS selection declaration showing interactions between EEC, ECS, and EES.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS + participant EES + Note over EEC, ECS: 1. Service provisioning + Note over EEC, ECS, EES: 2. EAS discovery + Note over EEC: 3. Determine EAS to be used + EEC->>EES: 4. Selected EAS announcement request + Note over EES: 5. Influence traffic for the selected EAS + EES->>EEC: 6. Selected EAS announcement response + +``` + +The diagram illustrates the sequence of messages for the initial EAS selection declaration. It involves three entities: EEC (Edge Enabling Center), ECS (Edge Cloud Server), and EES (Edge Enabling Server). The sequence starts with '1. Service provisioning' between EEC and ECS. This is followed by '2. EAS discovery' involving all three entities. Then, '3. Determine EAS to be used' occurs within the EEC. Next, the EEC sends a '4. Selected EAS announcement request' to the EES. The EES then performs '5. Influence traffic for the selected EAS' and finally sends a '6. Selected EAS announcement response' back to the EEC. + +Sequence diagram for Initial EAS selection declaration showing interactions between EEC, ECS, and EES. + +**Figure 7.15.2-1: Initial EAS selection declaration** + +In Figure 7.15.2-1 step 1 and 2, the EEC performs the start-up procedures for initial service provisioning and EAS discovery. EEC may send EAS discovery to multiple EESs. If registration is required by an EES, EEC registers into the EES before EAS discovery. + +In step 3, the EEC (or AC and EEC) selects the initial EAS from the discovered EAS candidates. + +In step 4, the EEC sends Selected EAS declaration request with AC ID, EAS ID, EAS endpoint and UE ID to the selected EES (which is determined based on the selected EAS). + +The EES, in step 5: + +- may apply the EAS traffic influence with the N6 routing information of the EAS in the 3GPP Core Network, based on application KPIs and if the EAS traffic influence was not done before. + +NOTE 1: EES can also influence the EAS traffic in advance. + +The EEC is then responded by the selected EES with success/failure of the request in step 6. + +NOTE 2: It is up to the AC to decide when to connect to the selected EAS (either immediately or wait for a while) once the AC knows the selected EAS. + +NOTE 3: The AC is not depicted in above figure for simplicity and solution to address interaction between AC and EEC is related to KI#4 for step 1 to 3. + +Table 7.15.2-1 describes information elements for the selected EAS announcement request sent from the EEC to the serving EES. + +**Table 7.15.2-1: Selected EAS announcement request** + +| Information element | Status | Description | +|-----------------------|--------|-------------------------------| +| UE ID | M | The identifier of the UE. | +| AC ID | O | The Application Client ID. | +| Security credentials | M | Security credentials. | +| Selected EAS ID | M | Selected EAS identifier. | +| Selected EAS Endpoint | M | Endpoint of the selected EAS. | + +Currently, the EES can be aware of ongoing AC-EAS session if EAS uses EDGE-3 exposure APIs with UE IP address as input. The APIs are Eees\_UEIdentifier and Eees\_SessionWithQoS. + +NOTE 4: SSC creation requires EEC Context existence. It can be determined in the normative phase whether the timing for SSC creation depends on when Eees\_UEIdentifier or Eees\_SessionWithQoS is invoked. It can also be possible that the SSC is not created at all during the entire AC-EAS communication period. + +As an alternative to sending the Selected EAS announcement request, registered EECs can provide an EEC registration update providing or updating the Selected EAS Endpoint IE, as introduced by solution #39. + +### 7.15.3 Solution evaluation + +This solution addresses KI#14. It allows the EES to be aware of the selected EAS in initial service start so that the EES can control application traffic influence for the initial application traffic. This solution also addresses KI#8 about how the EES is aware of the application session information. It is a viable solution. + +## 7.16 Solution #16: EAS discovery for different users + +### 7.16.1 Architecture enhancements + +None. + +### 7.16.2 Solution description + +#### 7.16.2.1 General + +The following solution corresponds to the key issue #12 on service differentiation for users. + +In this solution, the User information corresponding to service permission level is introduced to achieve service differentiation. + +The User information corresponding to service permission level could be a list of UE identifier(s) associated with service permission level. It enables EES support to handle the information of user priority or something like "allowed-list", or EAS deployment segmentation in EDN. And it is provided to EES by EAS during the EAS registration or EAS registration update. + +#### 7.16.2.2 Procedure + +In this solution, when EES receives the EAS discovery request, in addition to service permission level filter, the EES identifies the EAS based on received User information. + +### 7.16.3 Solution evaluation + +This solution addresses KI#12. This requires the EAS to provide its subscription information (e.g. which users are gold-plan users) to the EEL and let EEL handle the service differentiation, which is not reasonable in the real use cases, especially when the ASP and the ECSP are different organizations. In addition, the User information, or a list of UE identifiers, are dynamic information and can be too large to send in the EAS profile and to store in the EES. Therefore, this solution based on the User information from the EAS is not viable. + +## 7.17 Solution #17: Traffic influence for initial EAS discovery + +### 7.17.1 Architecture enhancements + +None. + +### 7.17.2 Solution description + +#### 7.17.2.1 General + +The following solution corresponds to the key issue#14 on application traffic influence for initial EAS discovery clause 4.14. + +#### 7.17.2.2 Procedure + +In this solution, the EES will decide whether to perform traffic influence for the AC before the real data transmission between the AC and the EAS considering the AC type, requirement of the AC and so on, since AC may not connect to the EAS immediately after obtain the EAS information, in this case, the execution of traffic influence is unnecessary. + +![Sequence diagram illustrating the traffic influence for initial EAS discovery. The diagram shows three participants: EEC, EES, and 5GC. The sequence of messages is: 1. EEC sends an 'EAS discovery request (AC profile)' to EES. 2. EES performs 'Determination of traffic influence execution' (shown as a self-call). 3. EES sends a 'traffic influence' message to 5GC. 4. EES sends an 'EAS discovery response' back to EEC.](c9d8a18a6137ad054b841d7a614afb48_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES + participant 5GC + Note right of EES: 2. Determination of traffic influence execution + EEC->>EES: 1. EAS discovery request (AC profile) + EES->>5GC: 3. traffic influence + EES->>EEC: 4. EAS discovery response + +``` + +Sequence diagram illustrating the traffic influence for initial EAS discovery. The diagram shows three participants: EEC, EES, and 5GC. The sequence of messages is: 1. EEC sends an 'EAS discovery request (AC profile)' to EES. 2. EES performs 'Determination of traffic influence execution' (shown as a self-call). 3. EES sends a 'traffic influence' message to 5GC. 4. EES sends an 'EAS discovery response' back to EEC. + +**Figure 7.17.2.2-1: Traffic influence for initial EAS discovery** + +1. The EEC determines to perform EAS discovery before the real data transmission between the AC and the EAS based on the response time in the AC profile. The EEC sends the EAS discovery request to the EES. The request contains the AC type, AC Service KPIs. +2. Upon receiving the request from the EEC, if the AC has high requirement on response time, then the EES will select one EAS and determine to perform application traffic influence for this AC before the real data transmission between the AC and the EAS, based on the AC type, AC Service KPIs, response time. If the AC does not have high requirement on response time, then the EES will not perform application traffic influence immediately. +3. The EES sends the AF request to the 5GC optimizing the user plane path between the UE and the EAS, if the EES determines to perform application traffic influence immediately. +4. The EES sends the EAS discovery response to the EEC. The response contains the discovered EAS list with EAS being traffic influenced. The EEC sends the EAS discovery response to the AC. + +### 7.17.3 Solution evaluation + +The solution #17 is applicable to the scenario where the EES selects the EAS and performs the traffic influence immediately for the selected EAS after EEC sent EAS discovery request. It is a viable solution. + +**NOTE:** The EES may only be able to use the Service KPIs to determine whether to perform traffic influence immediately or not. + +## 7.18 Solution #18: Constraint device in EDGEAPP + +### 7.18.1 Architecture enhancements + +None. + +### 7.18.2 Solution description + +This solution addresses KI#15. In this solution, in order to reduce power consumption in the UE, it specifies the EEC with Reduced Capabilities (RedEEC). The RedEEC skips EEC registration and the EAS discovery procedure is enhanced to delegate the EAS selection to EES. Figure 7.18.2-1 illustrates the details interactions. + +![Sequence diagram illustrating service provisioning and EAS discovery for a constraint device. The diagram shows interactions between EEC, ECS, and EES. Step 1: Service provisioning (EEC to ECS). Step 2: EAS discovery request (UE type) (EEC to EES). Step 3: EAS discovery response (selected EAS in discovered EAS) (EES to EEC). Step 4: Send selected EAS to AC or repeat step 3 with another EES selected in step 2 (EEC internal action).](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS + participant EES + Note over EEC, ECS: 1. Service provisioning + EEC->>EES: 2. EAS discovery request (UE type) + EES-->>EEC: 3. EAS discovery response (selected EAS in discovered EAS) + Note left of EEC: 4. Send selected EAS to AC or repeat step 3 with another EES selected in step 2 + +``` + +Sequence diagram illustrating service provisioning and EAS discovery for a constraint device. The diagram shows interactions between EEC, ECS, and EES. Step 1: Service provisioning (EEC to ECS). Step 2: EAS discovery request (UE type) (EEC to EES). Step 3: EAS discovery response (selected EAS in discovered EAS) (EES to EEC). Step 4: Send selected EAS to AC or repeat step 3 with another EES selected in step 2 (EEC internal action). + +**Figure 7.18.2-1: service provisioning and EAS discovery for constraint device** + +In step 1, EEC performs service provisioning. For EAS discovery, the EEC sends the request to a selected EES from the candidate EES(s) and indicates UE type to EES in step 2. In step 3, the EES performs EAS discovery as described in clause 8.5.2.2 of 3GPP TS 23.558 [2] and in addition selects a suitable EAS from discovered candidate EAS(s) if UE type indicates constraint device, then the EES sends EAS discovery response to the EEC including the selected EAS information in the Discovered EAS list. In step 5, if the EAS discovery response contains successful result, the EEC sends to AC the received selected EAS information and the EAS discovery and selection procedure ends; otherwise, the EEC repeats step 2 with next selected candidate EES. + +NOTE: The EEC can interact with each candidate EES if no appropriate EAS can be selected by EES. + +Table 7.18.2-1 and table 7.18.2-1 below show the detailed impact (highlighted with **bold** text) for EAS discovery request and response. + +**Table 7.18.2-1: EAS discovery request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requestor identifier | M | The ID of the requestor (e.g. EECID) | +| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| EAS discovery filters | O | Set of characteristics to determine required EASs, as detailed in Table 8.5.3.2-2. | +| UE location | O | The location information of the UE. The UE location is described in clause 7.3.2. | +| Target DNAI (NOTE) | O | Target DNAI information which can be associated with potential T-EAS(s) | +| EEC Service Continuity Support | O | Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC or, if this message is sent by the EEC to discover a T-EAS, which ACR scenario(s) are intended to be used for the ACR. | +| EES Service Continuity Support (NOTE) | O | The IE indicates if the S-EES supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EES or, if the EAS discovery is used for an S-EES executed ACR according to clause 8.8.2.5, which ACR scenario is to be used for the ACR. | +| EAS Service Continuity Support (NOTE) | O | The IE indicates if the S-EAS supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EAS or, if the EAS discovery is used for an S-EAS decided ACR according to clause 8.8.2.4, which ACR scenario is to be used for the ACR. | +| UE type | O | Indicates UE or device type (e.g. constraint device) | +| NOTE: This IE shall not be included when the request originates from the EEC. | | | + +**Table 7.18.2-2: EAS discovery response** + +| Information element | Status | Description | +|-----------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Successful response | O | Indicates that the EAS discovery request was successful. | +| > Discovered EAS list | O | List of discovered EAS(s). Each element includes the information described below. Based on UE type, only one EAS may be included. | +| >> EAS profile | M | Profile of the EAS. Each element is described in clause 8.2.4 | +| >> Lifetime | O | Time interval or duration during which the information elements in the EAS profile is valid and supposed to be cached in the EEC (e.g. time-to-live value for an EAS Endpoint) | +| Failure response | O | Indicates that the EAS discovery request failed. | +| > Cause | O | Indicates the cause of EAS discovery request failure. | + +In service continuity, to offload UE from monitoring triggers (e.g. location change) to start ACR, EEC can announce its support for EDN side decided ACR scenarios (clause 8.8.2.4 and clause 8.8.2.5 of 3GPP TS 23.558 [2]) so that EEC only need to passively receive ACR information notifications. + +### 7.18.3 Solution evaluation + +This solution addresses KI#15 with EAS discovery and selection procedure for constrained device using EDGEAPP. The EEC relies on EES to select an appropriate EAS (the EEC does not need to select an EAS among discovered EAS list from candidate EESs). + +## 7.19 Solution #19: EES determines the selected ACR scenario + +### 7.19.1 Architecture enhancements + +None. + +### 7.19.2 Solution description + +#### 7.19.2.1 General + +The following solution corresponds to the Key issue #19: ACR scenario combination. + +#### 7.19.2.2 Procedure + +In this solution, the EES is responsible to determine the selected ACR scenario for each AC based on the ACR scenarios supported by AC, EEC, EES and EAS. When the EES determines the selected ACR scenario for one AC, the EES will send the selected ACR scenario for the AC to the EEC and the EAS, then the EEC will notify the AC with the selected ACR scenario. With this solution the EES can determine which ACR approach can be enabled for the AC and EAS considering the detailed information (e.g EAS features, KPIs) of both the AC and the EAS and thus also avoiding the overlapping of ACR initiations by multiple entities which introduce unnecessary signalling to resolve co-existence issues. + +Furthermore, the EES can determine the ACR mode (single-ACR scenario or multi-ACR scenarios) for each AC considering the AC service KPI (e.g. Connection bandwidth, Request rate, Response time). Using single ACR scenario to detect the ACR can save the signalling interaction for ACR detect, ACR decision and ACR execution but may not be able to detect ACR event timely. Using multiple ACR scenarios to detect the ACR can detect ACR event more timely but may increase the signalling interaction for ACR detect, ACR decision and ACR execution. + +![Sequence diagram showing the interaction between EEC, EES, and EAS for ACR scenario selection. The steps are: 1. EAS sends a subscription request to EES; 2. EES sends a subscription response to EAS; 3. EEC sends a request to EES; 4. EES determines the ACR scenario; 5. EES sends a notification to EAS; 6. EES sends a notification to EEC.](fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES + participant EAS + Note right of EES: 4. Determination of ACR scenario + EAS->>EES: 1. ACR scenario selection subscription request + EES-->>EAS: 2. ACR scenario selection subscription response + EEC->>EES: 3. ACR scenario selection request + EES-->>EAS: 5. ACR scenario selection notification + EES-->>EEC: 6. ACR scenario selection notification + +``` + +Sequence diagram showing the interaction between EEC, EES, and EAS for ACR scenario selection. The steps are: 1. EAS sends a subscription request to EES; 2. EES sends a subscription response to EAS; 3. EEC sends a request to EES; 4. EES determines the ACR scenario; 5. EES sends a notification to EAS; 6. EES sends a notification to EEC. + +**Figure 7.19.2.2-1: EES determines the selected ACR scenario** + +1. The EAS sends an ACR scenario selection subscription request to the EES. +2. The EES sends an ACR scenario selection subscription response to the EAS with the subscription result. +3. The EEC sends ACR scenario selection request to the EES, the request contains the AC service continuity support and EEC service continuity support indicating which ACR scenarios are supported by the AC and the EEC. +4. The EES obtains the AC service continuity support and EEC service continuity support from UE and EAS service continuity support, then the EES determines the ACR mode (single-ACR scenario or multi-ACR + +scenarios) for the AC and may be based on the ACR scenarios supported by AC, EEC, EES and EAS. The EES can select appropriate ACR scenario(s) for the AC from the intersection of the ACR scenarios supported by AC, EEC, EES and EAS. + +NOTE 1: The EES can also determine the ACR mode considering AC service KPI (e.g. Connection bandwidth, Request rate, Response time), which is implementation specific. + +NOTE 2: ACR mode including single-ACR scenario or multi-ACR scenario for one specific AC. + +NOTE 3: The ACR mode, if required or not, will be considered in normative work. + +NOTE 4: The ACR scenario supported by the EAS is available in the EAS service continuity support of the EAS profile. + +**Editor's note:** It is FFS how the EES can know the supported service continuity scenarios of the T-EES and T-EAS. + +5. The EES sends the ACR scenario selection notification to the EAS, the notification contains one or more selected ACR scenario(s) and related ACID. +6. The EES sends the ACR scenario selection response to the EEC including the selected ACR scenario and related ACID, then the EEC may notify the AC with the selected ACR scenario. + +NOTE 5: Using multiple ACR scenario can detect ACR timely. + +### 7.19.3 Solution evaluation + +It allows the EES to determine the selected ACR scenario. It is a viable solution. A new API (ACR scenario selection procedure) is used in this solution. + +NOTE: The selection of a single ACR scenario and therefore single ACR detection entity may not be suitable for time sensitive applications. + +## 7.20 Solution #20: Propagation of EEL notifications to EEC using Edge Notification Server + +### 7.20.1 Architecture enhancements + +Architecture enhancement in clause 6.3 is the basis for this solution. + +### 7.20.2 Solution description + +#### 7.20.2.1 General + +The following solution corresponds to the key issue #1, "enhanced notification service to the EEC" as described in clause 4.1. + +In this solution, ENS is used as a centralized notification server enhancing EEL's notifications delivery mechanism to EEC. Such an architectural enhancement allows the EEC to inform EEL of its preferred method (e.g. Long-polling, WebSocket, FCM, APNS, OMA Push) of receiving notifications and enables Edge Application architecture to flexibly provide a diverse set of methods for notifications delivery to EEC. + +#### 7.20.2.2 Notification delivery over a direct Notification Channel Procedure + +In this procedure, based on EEC's request on the preferred method of notification delivery (i.e. Log-polling or WebSocket), a direct notification channel in between the EEC and ENS is established. + +NOTE: Notification delivery method using a Push server is described in clause 7.20.2.3. + +Pre-conditions: + +1. EEC is aware of the ENS's endpoint through provisioning +2. EES and ECS are authorized to interact with the ENS +3. EEC is authorized to interact with the ENS, EES and ECS + +![Sequence diagram showing notification delivery over a direct Notification Channel. The diagram involves four lifelines: EEC, ENS, EES, and ECS. The sequence starts with EEC sending a preferred notification delivery method (direct channel) to ENS. ENS processes the request and returns a Callback URL and a Channel URL. EEC opens the notification channel using the Channel URL. EEC then sends a create subscription request to EES. EES processes the request and returns a subscription response. EEC sends a create subscription request to ECS. ECS processes the request and returns a subscription response. ENS then pushes a notification to the Callback URL. EEC receives the notification over the notification channel. EES and ECS also push notifications to the Callback URL. EEC receives these notifications over the notification channel.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ENS + participant EES + participant ECS + + Note right of ENS: 2. Process request + EEC->>ENS: 1. Preferred notification delivery method (direct channel) + ENS-->>EEC: 3. Receive a Callback URL and a Channel URL + EEC->>ENS: 4. Open notification channel (Channel URL) + EEC->>EES: 5. Create subscription (Callback URL) + Note right of EES: 6. Process request + EES-->>EEC: 7. Subscription response + EEC->>ECS: 8. Create subscription (Callback URL) + Note right of ECS: 9. Process request + ECS-->>EEC: 10. Subscription response + Note right of ENS: 11. Event occurs + ENS->>EEC: 12. Push notification to Callback URL + Note right of EES: 14. Event occurs + EES->>EEC: 15. Push notification to Callback URL + Note right of ECS: 16. Push notification over notification channel + EEC->>ENS: 13. Push notification over notification channel + +``` + +Sequence diagram showing notification delivery over a direct Notification Channel. The diagram involves four lifelines: EEC, ENS, EES, and ECS. The sequence starts with EEC sending a preferred notification delivery method (direct channel) to ENS. ENS processes the request and returns a Callback URL and a Channel URL. EEC opens the notification channel using the Channel URL. EEC then sends a create subscription request to EES. EES processes the request and returns a subscription response. EEC sends a create subscription request to ECS. ECS processes the request and returns a subscription response. ENS then pushes a notification to the Callback URL. EEC receives the notification over the notification channel. EES and ECS also push notifications to the Callback URL. EEC receives these notifications over the notification channel. + +**Figure 7.20.2.2-1: Notification delivery over a direct Notification Channel** + +1. The EEC sends a request to ENS for a direct notification channel (e.g. by indicating either a Long-polling (Pull) or a WebSocket (Push) notification delivery method). +2. Upon receiving the request, the ENS performs an authorization check and further verifies if the requested notification delivery method (e.g. Long-polling or WebSocket ) can be used. If the request is authorized and the requested notification delivery method can be used, the ENS assigns a Callback URL and an associated Channel URL for the EEC and stores the information for its subsequent use (i.e. any notification received at the assigned Callback URL will be made available over the associated Channel for consumption by the EEC). +3. If the processing of the request was successful, the ENS responds with the assigned Callback URL and Channel URL +4. EEC, upon receiving the Callback URL and Channel URL, based on the type of direct notification channel (e.g. Long-polling or WebSocket) it wishes to have with ENS, would either starts polling the Channel URL (e.g. HTTP GET Channel URL) for events or uses the Channel URL and prepares it for the Push delivery (e.g. uses the channel URL and upgrades it to a WebSocket notification channel as per WebSocket protocol and in essence opens the notification channel for the flow of notifications as they arrive at ENS). +5. The EEC sends a EAS discovery subscription request and/or ACR information subscription request (as described in clauses 8.5.3.4 and 8.8.4.8 of 3GPP TS 23.558 v17.0.0 respectively) to the EES with the Notification Target Address IE set to the Callback URL received from the ENS in step 3 above. +6. Upon receiving the request, the EES performs an authorization check (as described in clauses 8.5.2.3.2 or 8.8.3.5.2 of TS 23.558 depending on the subscription request in step 5) and if the request is authorized, the EES creates the associated subscription resource. +7. EES responds to EEC with the subscriptionId of the created resource. +8. The EEC sends a service provisioning subscribe request (as described in clause 8.3.3.3.4 of 3GPP TS 23.558 v17.0.0) to the ECS with the Notification Target Address IE set to the Callback URL received from the ENS in step 3 above. +9. Upon receiving the request, the ECS performs an authorization check as described in clause 8.3.3.2.3.2 of TS 23.558 and if the request is authorized, the ECS creates the associated subscription resource. + +10. ECS responds to EEC with the subscriptionId of the created resource. +11. Some events of interest to EEC occurs in ECS that satisfies trigger conditions for updating service provisioning of a subscribed EEC and the corresponding subscription directs the ECS to push the event to the Callback URL which is terminated at the ENS. +12. ECS pushes the notification to the Callback URL +13. ENS, upon receiving an event at the given Callback URL, identifies the associated Channel URL (which it created and assigned to the EEC in step 2 above) and determines which notification delivery method was requested by the EEC (as per step 1 above). ENS forwards the notification to EEC either by responding to the Long-polling request (if EEC is using the Long-polling method) or pushes the notification to the EEC (if EEC is using a Push method such as the WebSocket delivery method), +14. Some events of interest to EEC occurs in EES that satisfies trigger conditions for updating a subscribed EEC with the EAS discovery information or ACR related information (e.g. ACR complete event) and the corresponding subscription directs the EES to push the event to the Callback URL which is terminated at the ENS. +15. EES pushes the notification to the Callback URL +16. ENS, upon receiving an event at the given Callback URL, identifies the associated Channel URL (which it created and assigned to the EEC in step 2 above) and determines which notification delivery method was requested by the EEC (as per step 1 above). ENS forwards the notification to EEC either by responding to the Long-polling request (if EEC is using the Long-polling method) or pushes the notification to the EEC (if EEC is using a Push method such as the WebSocket delivery method). + +#### 7.20.2.3 Notification delivery using a Push Server Procedure (indirect Notification Channel) + +In this procedure, based on EEC's request that the preferred method of notification delivery being via a Push server, there is no need for a direct notification channel between the EEC and ENS. Instead, ENS forwards the notifications through an identified Push server to the EEC. In other words, based on EEC's request, an indirect notification channel between the EEC and ENS with the Push server as an intermediary is established. + +NOTE 1: This procedure reuses the Push function setup steps 1a, 1b and 1c described in solution #1 (see clause 7.1.2.2). + +Pre-conditions: + +1. EEC is aware of the ENS's endpoint through provisioning +2. EES and ECS are authorized to interact with the ENS +3. EEC is authorized to interact with the ENS, EES and ECS +4. ENS is aware of the Push server endpoint and is authorized to interact with it + +![Sequence diagram illustrating notification delivery using a Push Server. Lifelines: UE (EEC, Push Function), Push Server, ENS, EES, ECS. The process involves registration, token delivery, request to ENS, subscription creation with EES and ECS, and subsequent push notifications triggered by events in the ECS.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant UE as UE (EEC, Push Function) + participant PS as Push Server + participant ENS as ENS + participant EES as EES + participant ECS as ECS + + Note left of UE: 1a. EEC registers for push notification + UE->>PS: 1b. Get push token from the Push server + PS-->>UE: 1c. Push token delivery + UE->>ENS: 2. Preferred notification delivery method (Push Server) + ENS->>EES: 3. Process request + ENS-->>UE: 4. Receive a Callback URL + UE->>EES: 5. Create subscription (Callback URL) + EES->>ECS: 6. Process request + EES-->>UE: 7. Subscription response + EES->>ECS: 8. Create subscription (Callback URL) + ECS->>EES: 9. Process request + ECS-->>UE: 10. Subscription response + Note right of ECS: 11. Event occurs + ECS->>ENS: 12. Push event to Callback URL + ENS->>PS: 13. Push notification + PS-->>UE: 14. Push notification + Note right of ECS: 15. Event occurs + ECS->>ENS: 16. Push event to Callback URL + ENS->>PS: 17. Push notification + PS-->>UE: 18. Push notification + +``` + +Sequence diagram illustrating notification delivery using a Push Server. Lifelines: UE (EEC, Push Function), Push Server, ENS, EES, ECS. The process involves registration, token delivery, request to ENS, subscription creation with EES and ECS, and subsequent push notifications triggered by events in the ECS. + +**Figure 7.20.2.3-1: Notification delivery using a Push Server** + +1. The EEC registers with the push function within the UE. The EEC acquires a push token and push server information from the push function. This step is depicted as sub-steps 1a, 1b and 1c in Figure 7.20.2.2-1. + +NOTE 2: The push server provides the push function in the UE with a push token, which is delivered to the EEC. + +2. The EEC sends a request to ENS for an indirect notification channel via the identified Push server. The request contains the Push server information as well as the EEC's push token (see step 1) +3. Upon receiving the request, the ENS performs an authorization check and further verifies if the requested notification delivery method (i.e. Push server) can be used. If the request is authorized and the requested notification delivery method can be used, the ENS assigns a Callback URL for the EEC and stores the information for its subsequent use (i.e. any notification received at the assigned Callback URL will be forwarded to the associated Push server for consumption by the EEC). +4. If the processing of the request was successful, the ENS responds with the assigned Callback URL. +5. The EEC sends a EAS discovery subscription request and/or ACR information subscription request (as described in clauses 8.5.3.4 and 8.8.4.8 of 3GPP TS 23.558 v17.0.0 respectively) to the EES with the Notification Target Address IE set to the Callback URL received from the ENS in step 4 above. +6. Upon receiving the request, the EES performs an authorization check (as described in clauses 8.5.2.3.2 or 8.8.3.5.2 of TS 23.558 depending on the subscription request in step 5) and if the request is authorized, the EES creates the associated subscription resource. +7. EES responds to EEC with the subscriptionId of the created resource. +8. The EEC sends a service provisioning subscribe request (as described in clause 8.3.3.3.4 of 3GPP TS 23.558 v17.0.0) to the ECS with the Notification Target Address IE set to the Callback URL received from the ENS in step 4 above. +9. Upon receiving the request, the ECS performs an authorization check as described in clause 8.3.3.2.3.2 of TS 23.558 and if the request is authorized, the ECS creates the associated subscription resource. +10. ECS responds to EEC with the subscriptionId of the created resource. +11. Some events of interest to EEC occurs in ECS that satisfies trigger conditions for updating service provisioning of a subscribed EEC and the corresponding subscription directs the ECS to push the event to the Callback URL which is terminated at the ENS. + +12. ECS pushes the notification to the Callback URL +13. ENS, upon receiving an event at the given Callback URL, identifies the associated Push server and the EEC's push token (which it received from EEC in step 2 above) and pushes the notification to the identified Push server using the given EEC's push token notification. +14. Push server forwards the notification to the EEC via the push function. +15. Some events of interest to EEC occurs in EES that satisfies trigger conditions for updating a subscribed EEC with the EAS discovery information or ACR related information (e.g. ACR complete event) and the corresponding subscription directs the EES to push the event to the Callback URL which is terminated at the ENS. +16. ECS pushes the notification to the Callback URL +17. ENS, upon receiving an event at the given Callback URL, identifies the associated Push server and the EEC's push token (which it received from EEC in step 2 above) and pushes the notification to the identified Push server using the given EEC's push token notification. +18. Push server forwards the notification to the EEC via the push function. + +### 7.20.3 Solution evaluation + +The proposed solution addresses Key Issue #1. + +The Edge Notification Server enables an EDGEAPP architectural mechanism via which many different ways of pushing notifications to the EEC would become possible. Hence, the best notification delivery method can be offered to the EEC/UE for the use case at hand as per EEC's request based on the given UE's limitations. + +The Edge Notification Server should be viewed as an umbrella for different notification deliver methods to the EEC, one of which is solution #1 as per clause 7.1. Such an EDGEAPP architectural enhancement provides the needed flexibility to handle different use cases while considering varying UE's limitations. + +The Edge Notification Server is considered an optional feature of the EDGEAPP architecture. + +## 7.21 Solution #21: Prediction expiration time for service continuity planning enhancement + +### 7.21.1 Architecture enhancements + +None. + +### 7.21.2 Solution description + +#### 7.21.2.1 General + +The following solution corresponds to the key issue #3 Enhancements to service continuity planning in clause 4.3. + +In service continuity planning, the ACR is performed for a predicted or expected location of the UE in the future. Since the prediction is for a future location in a future time, a prediction expiration time is introduced to take account for the future time window in which the prediction is expected to happen. Therefore, in this solution, EEC includes its expectation or knowledge of the time that it expects the prediction to happen within the ACR request at latest. This is the time that the EEC requests the T-EAS to wait for the AC to connect at latest. The EESs can consider this time in deciding the time that they will wait for the ACR status update from the corresponding EASs. + +EES can take into account the prediction expiration time in processing the ACR request message, e.g. accepting or rejecting the request. In case that the request is authorized and accepted by the EES, it also includes it in the notification (if any) to the EAS. Similarly, EAS can take into account the prediction expiration time in performing ACT. T-EAS and T-EES will receive the prediction expiration time and may consider it in deciding whether and for how long to wait for the UE to connect to them. + +#### 7.21.2.2 Procedure + +Figure 7.21.2.2-1 illustrates the EEC triggered ACR scenario for service continuity planning. + +Pre-condition: + +1. The EEC has been authorized to communicate with the EES. +2. EEC has detected the need for ACR for an expected/predicted location in the future. + +![Sequence diagram illustrating the EEC triggered ACR scenario for service continuity planning. The diagram shows interactions between EEC, EES, Remote EES, S-EAS or T-EAS (Corresponding to the EES), and T-EAS or S-EAS (corresponding to the remote EES). The process is divided into three phases: ACR Request, ACR Execution, and ACR Clean-up.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES + participant Remote EES + participant S-EAS or T-EAS as S-EAS or T-EAS +(Corresponding to the EES) + participant T-EAS or S-EAS as T-EAS or S-EAS +(corresponding to the remote EES) + + Note left of EEC: Pre-condition: 1. EEC authorized; 2. Need for ACR detected + + EEC->>EES: 1. ACR request. Including prediction expiration time + Note right of EES: 2. Authorization check, Process the request + EES->>S-EAS or T-EAS: 2a. ACR notification including prediction expiration time + EES-->>EEC: 3. ACR response + + Note left of EES: ACR Execution + EES->>Remote EES: 4a. ACR Information including prediction expiration time + Remote EES->>T-EAS or S-EAS: 4b. ACR notification including prediction expiration time + Remote EES-->>EES: 4c. ACR Information response + Note right of EES: 5a. EEC context relocation + Note right of T-EAS or S-EAS: 5b. ACT + + Note left of EES: ACR Clean-up + EES->>S-EAS or T-EAS: 6. ACR status update + Note right of EES: 7. ACR complete notify + +``` + +Sequence diagram illustrating the EEC triggered ACR scenario for service continuity planning. The diagram shows interactions between EEC, EES, Remote EES, S-EAS or T-EAS (Corresponding to the EES), and T-EAS or S-EAS (corresponding to the remote EES). The process is divided into three phases: ACR Request, ACR Execution, and ACR Clean-up. + +**Figure 7.21.2.2-1: EEC triggered ACR scenario for service continuity planning** + +1. The EEC sends an ACR request message to the EES with initiation or determination action. Depending on the ACR scenario, the EES can be either of S-EES or T-EES. + +In case of service continuity planning the ACR request message may include also the prediction expiration time to indicate the time that the EEC expects the prediction takes place at latest. This is the time that the EEC requests the T-EAS to wait for the AC to connect at latest. + +2. The EES checks if the requestor is authorized for this operation. If authorized, the EES processes the request and performs the required operations. + +2a. If authorized and if EES decides to continue the ACR, if the EAS notification indication is provided in the step 1 request and the EAS has subscribed to receive such notification, the EES shall notify the EAS about the need to start ACR. In that case, if the request in step 1 includes a prediction expiration time, the EES includes it in the notification to EAS. + +If the request in step 1 is to S-EES this EAS is the S-EAS. Otherwise if the request of step 1 is to T-EES, this EAS is the T-EAS. + +3. The EES responds to the requestor's request, i.e. EEC, with an ACR response message. +4. (a) If the action in the request in step 1 is initiation, the EES sends the information and parameters of the ACR to the remote EES. Otherwise if the action is determination the EES first discovers the T-EES and T-EAS, and then sends the information and parameters of the ACR to the T-EES. + +(b) If the remote EAS has subscribed to receive such notification, the remote EES shall notify the EAS about the need to ACR and includes corresponding parameters of the ACR, e.g. prediction expiration time if it is provided in the request in step 1. + +(c) The remote EES sends the response back to the EES to confirm it has received the ACR parameters. + +If the request in step 1 is to S-EES the remote EES is the T-EES. Otherwise if the request of step 1 is to T-EES, the remote EES is the S-EES. + +If the "Prediction expiration time" is not acceptable for the T-EAS, e.g. due to resource status, the EAS can reject the ACT. In that case the ACT fails. + +5. The ACR is executed depending on the ACR scenario. S-EAS and T-EAS perform application context transfer (ACT) in an application specific time and manner. The EAS may use the prediction expiration time received in step 2a to decide on whether and how to perform the ACT. The T-EAS may also consider it in deciding whether and for how long to wait for the AC of the UE to connect to it. +6. The EAS sends the failure or success message in the ACR status update based on the results of step 5b. EAS can consider the prediction expiration time received in step 2a, if provided, to send the message in step 6. + +If the request in step 1 is to S-EES this EAS is the S-EAS. Otherwise if the request of step 1 is to T-EES, this EAS is the T-EAS. + +If the ACT as per step 5 is performed, and the AC (UE) does not connect to the T-EAS by "Prediction expiration time", the EAS can send ACT failure with the appropriate cause to the EES. In that case, the T-EAS can delete the transferred application context. + +7. The EES sends the ACR complete notify to the EEC with failure or success result. The EES also considers the failure or success message received in step 6 in the ACR complete notification. + +NOTE: The "Prediction expiration time" is not processed by the EES in this solution. Whether and how the EES can use this IE is out of the scope of this solution. + +### 7.21.3 Solution evaluation + +The Solution addresses KI#3 by including a prediction expiration time withing ACR request from the EEC. This information can be used by T-EAS to adjust its waiting time for the UE to reach the service area. + +## 7.22 Solution #22: Support simultaneous EAS connectivity in ACR + +### 7.22.1 Architecture enhancements + +None. + +### 7.22.2 Solution description + +#### 7.22.2.1 Solution for traffic influence + +To solve the issue about traffic influence to maintain both S-PSA and T-PSA to support simultaneous connectivity with both S-EAS and T-EAS during the service continuity, the AC includes the need for simultaneous EAS connectivity in the AC profile and the AC profile is sent to EEC via EDGE-5 reference point so that the EEC can request such need in the ACR request sent to EES. Then the EES, at the time of requesting traffic influence towards 3GPP CN, provides additional requirement for simultaneous PSA connectivity as described in clause 6.3.4 of 3GPP TS 23.548 [19]. + +Figure 7.22.2.1-1 describes the detailed interaction between the AC and EEC for AC registration procedure (a possible way to provide AC profile to EEC). + +![Sequence diagram of AC Registration procedure. Lifelines: AC and EEC. Step 1: AC sends '1. AC Registration request (AC profile)' to EEC. Step 2: EEC performs '2. store the AC profile'. Step 3: EEC sends '3. AC Registration response (result)' back to AC.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant AC + participant EEC + Note right of EEC: 2. store the AC profile + AC->>EEC: 1. AC Registration request (AC profile) + EEC-->>AC: 3. AC Registration response (result) + +``` + +Sequence diagram of AC Registration procedure. Lifelines: AC and EEC. Step 1: AC sends '1. AC Registration request (AC profile)' to EEC. Step 2: EEC performs '2. store the AC profile'. Step 3: EEC sends '3. AC Registration response (result)' back to AC. + +**Figure 7.22.2.1-1: AC Registration procedure** + +1. The AC sends AC registration request to EEC, the request includes the AC profile (see table 7.22.2.1-1). +2. The EEC authorizes the AC registration request and stores the AC profile. +3. The AC is responded with AC registration response (success/failure). + +**Table 7.22.2-1: AC Profile** + +| Information element | Status | Description | +|------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACID | M | Identity of the AC. | +| AC Type | O | The category or type of AC (e.g. V2X). This is an implementation specific value. | +| Preferred ECSP list | O | When used in a service provisioning request, this IE indicates to the ECS which ECSPs are preferred for the AC. The ECS may use this information in the selection of EESs. | +| AC Schedule | O | The expected operation schedule of the AC (e.g. time windows) | +| Expected AC Geographical Service Area | O | The expected location(s) (e.g. route) of the hosting UE during the AC's operation schedule. This geographic information can express a geographic point, polygon, route, signalling map, or waypoint set. | +| AC Service Continuity Support | O | Indicates if service continuity support is required or not for the application. The IE also indicates which ACR scenarios are supported by the AC and which of these are preferred by the AC. | +| Simultaneous EAS connectivity information in service continuity | O | Indicates if simultaneous EAS connectivity is needed and the inactive time guidance for keeping connectivity towards the S-EAS. | +| List of EASs | O | List of EAS that serve the AC along with the service KPIs required by the AC | +| > EASID | M | Identifier of the EAS | +| > Expected AC Service KPIs | O | KPIs expected in order for ACs to receive currently required services from the EAS | +| > Minimum required AC Service KPIs | O | Minimum KPIs required in order for ACs to receive meaningful services from the EAS | + +Figure 7.22.2.1-2 describes the detailed interaction between the EEC and EES during service continuity (i.e. ACR). + +![Sequence diagram illustrating the ACR initiation procedure between EEC and EES.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` +sequenceDiagram + participant EEC + participant EES + Note left of EEC: 0. EEC is informed about AC profile(s) + EEC->>EES: 1. ACR request + Note right of EES: 2. Authorization check and processing the request + EES->>EEC: 3. ACR response +``` + +The diagram shows a sequence of interactions between the EEC (Edge Enabler Client) and the EES (Edge Enabler Server). The process starts with the EEC being informed about AC profile(s) (step 0). The EEC then sends an ACR request (step 1) to the EES. The EES performs an authorization check and processing the request (step 2) and returns an ACR response (step 3) to the EEC. + +Sequence diagram illustrating the ACR initiation procedure between EEC and EES. + +**Figure 7.22.2.1-2: ACR initiation procedure** + +0. The EEC is informed about AC profiles (e.g. during AC registration procedure as depicted in Figure 7.22.2.1-1). +1. The EEC triggers ACR request (type: initiation) to EES, the request includes the simultaneous EAS connectivity information in service continuity (see table 7.22.2.1-2) which was previously received as part of the AC profile (see table 7.22.2.1-1). +2. The EES authorizes the ACR request. Then the EES may use information provided in the request to apply the AF traffic influence with the N6 routing information of the T-EAS and Simultaneous EAS connectivity information in the 3GPP Core Network (if applicable), as described in clause 5.6.7.1 of 3GPP TS 23.501 [5] and clause 6.3.4 of 3GPP TS 23.548 [19]. + +**Editor's note:** Since the 3GPP CN only supports simultaneous PSA connectivity in SSC mode 3 or session breakout, it is FFS whether EES should firstly know PDU session capability before invoking AF traffic influence API. + +3. The EEC is responded with ACR response (success/failure). + +**Table 7.22.2.1-2: ACR request** + +| Information element | Status | Description | +|----------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------| +| Requestor Identifier | M | Unique identifier of the requestor (i.e. EECID or EASID). | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| EASID | O | Identifier of the EAS | +| UE identifier | O | The identifier of the UE (i.e. GPSI). | +| ACID | O | The identifier of the AC. | +| ACR action | M | Indicates the ACR action (ACR initiation or ACR determination) | +| ACR initiation data | O | ACR initiation IEs to be included in an ACR request message when ACR action indicates it is ACR initiation request. | +| > T-EAS Endpoint | M | Endpoint information (e.g. URI, FQDN, IP 3-tuple) of the T-EAS. | +| > Previous T-EAS Endpoint (NOTE 7) | O | Endpoint information (e.g. URI, FQDN, IP 3-tuple) of the T-EAS of the previous ACR. | +| > DNAI of the T-EAS | O | DNAI information associated with the T-EAS. | +| > N6 Traffic Routing requirements | O | The N6 traffic routing information and/or routing profile ID corresponding to the T-EAS DNAI. | +| > Simultaneous EAS connectivity information | O | Indicates if simultaneous EAS connectivity is needed and the inactive time guidance for keeping connectivity towards the S-EAS. | +| > EAS notification indication | M | Indicates whether to notify the EAS about the need of ACR. | +| ... | ... | ... | +| > S-EAS endpoint | O | Endpoint information of the S-EAS | +| ACR determination data | O | ACR determination IEs to be included in an ACR request message when ACR action indicates it is ACR determination request. | +| > S-EAS endpoint | M | Endpoint information of the S-EAS | + +### 7.22.3 Solution evaluation + +This solution addresses KI#4 about "Whether and how an AC registers to an EEC". During the AC registration, the AC is able to indicate its desire for keeping Simultaneous EAS Connectivity. This solution addresses KI#21 about traffic influence. The EES interacts with 3GPP CN to satisfy AC need during ACR request processing. + +## 7.23 Solution #23: UE identification with NAT + +### 7.23.1 Architecture enhancements + +None. + +### 7.23.2 Solution description + +#### 7.23.2.1 General + +This solution corresponds to KI#16 on support of NAT deployed within the edge data network. + +In this solution, the EEC provides either the CN network assigned IP address (i.e. the private IP address of the UE) or its UE ID (if it already has one) to the EES to obtain the UE identifier (Edge UE ID) from the EES. If the UE ID is not provided, EES uses the private IP address of the UE provided by the EEC to invoke the CN capability to translate UE's IP address to its UE ID (e.g. UE'sExternal UE ID). + +Once obtained, the EEC passes the Edge UE ID to the AC, which provides it to the EAS for use over EDGE-3 interface. This also allows the UE to protect its privacy by providing an option to obtain from the EES an Edge UE ID to share + +with the EAS(s) via the AC(s) instead of exposing its UE ID (if it already has one) to the AC(s). With EAS and EES both being aware of the Edge UE ID, issues pertaining to NAT and UE identification with privacy are resolved. + +NOTE 1: The UE ID provided by EEC is in the form of MSISDN. + +NOTE 2: SA3 coordination may be needed corresponding to privacy. + +#### 7.23.2.2 Procedure + +Figure 7.23.2.2 illustrates the procedure for the EEC to obtain the Edge UE ID from the EES and provide to the AC. + +![Sequence diagram illustrating the procedure for the EEC to obtain the Edge UE ID from the EES and provide to the AC. The diagram shows four lifelines: AC, EEC, EES, and EAS. The sequence of messages is: 1. AC sends an Edge UE ID request to the EEC. 2. EEC sends an Edge UE ID request to the EES. 3. EES translates the UE's Private IP Address or NATed IP Address and Port Number to UE ID. 4. EES sends an Edge UE ID response to the EEC. 5. EEC sends an Edge UE ID response to the AC. 6. EEC shares the Edge UE ID with the EAS. 7. EEC invokes EDGE-3 services using the Edge UE ID. 8. EEC invokes EDGE-1 services using the Edge UE ID. 9. EEC invokes CN capability APIs.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` + +sequenceDiagram + participant AC + participant EEC + participant EES + participant EAS + + Note right of EES: 3. Translate UE's a) Private IP Address +OR b) NATed IP Address and Port +Number to UE ID + + AC->>EEC: 1. Edge UE ID request + EEC->>EES: 2. Edge UE ID request + EES-->>EEC: 4. Edge UE ID response + EEC-->>AC: 5. Edge UE ID response + Note over AC, EAS: 6. Share Edge UE ID with the EAS + Note right of EES: 7. Invoke EDGE-3 services using the Edge UE ID + Note right of EEC: 8. Invoke EDGE-1 services using the Edge UE ID + Note right of EES: 9. Invoke CN capability APIs + +``` + +Sequence diagram illustrating the procedure for the EEC to obtain the Edge UE ID from the EES and provide to the AC. The diagram shows four lifelines: AC, EEC, EES, and EAS. The sequence of messages is: 1. AC sends an Edge UE ID request to the EEC. 2. EEC sends an Edge UE ID request to the EES. 3. EES translates the UE's Private IP Address or NATed IP Address and Port Number to UE ID. 4. EES sends an Edge UE ID response to the EEC. 5. EEC sends an Edge UE ID response to the AC. 6. EEC shares the Edge UE ID with the EAS. 7. EEC invokes EDGE-3 services using the Edge UE ID. 8. EEC invokes EDGE-1 services using the Edge UE ID. 9. EEC invokes CN capability APIs. + +**Figure 7.23.2.2-1: EEC obtaining UE ID from the EES** + +1. AC sends an Edge UE ID request to the EEC. The request may include the list of EASIDs for which the AC is requesting the Edge UE ID information. +2. The EEC upon receiving the request validates if AC is authorized to request this information. If AC is authorised, the EEC sends the Edge UE ID request to the EES. The request includes either the CN assigned private IP address of the UE or its UE ID (if it already has one) and may include the list of EASIDs if provided by the AC. + +NOTE 1: EEC can also send this request without receiving a request from AC in step 1. + +NOTE 2: Private IP address used by AC and private IP address used by EEC can be the same or different (if different PDU sessions are used). The request from EEC can include either of the IP addresses. + +3. Upon receiving the request from EEC, the EES authorizes the EEC. If authorized and the UE ID is not included in the request the EES invokes the CN capability APIs. There are three alternate approaches: + - a. EES invokes Nnef\_UEId\_Get for translating the UE's Private IP address to its UE ID as defined in 3GPP TS 23.502 [08] clause 4.15.10. If the request from EEC includes a list of EASIDs, the EES may invoke the Nnef\_UEId\_Get API for each EAS individually to obtain EAS specific UE ID(s); OR + +- b. Alternatively (to step 3a), EES invokes the CN capability APIs for translating UE's NATed IP Address and the port number to its UE ID. Optionally, EAS may also provide UE's NATed IP address and port number to EES to obtain UE ID; OR +- c. Alternatively (to step 3.a. or step 3.b.), EES invokes the CN capability APIs for translating UE's EECID to its UE ID. + +NOTE 3: For step 3.a., coordination with SA2 is required if SA2 supports to check whether EEC could get the IP domain information and expose it to EES to solve the IP address overlapping issue. + +NOTE 4: For step 3.b. and 3.c., the request from EEC in Step 2 may not include UE's Private IP address. + +NOTE 5: For step 3.b. and 3.c., coordination with SA2 is required to check whether this can be implemented as alignment work in Rel-18. + +The EES generates temporary Edge UE ID(s) which may be the same as the 3GPP CN provided UE ID or may be assigned by the EES itself. If UE ID is included in the request received from EEC, the EES generates temporary Edge UE ID. The temporary Edge UE ID may be specific for the EASs included in request received from EEC in step 2, in which case upon receiving a request on EDGE-3 interface, the EES matches the EASID in the request with EASIDs to which the Edge UE ID was assigned before processing the request. + +- 4. The EES sends the Edge UE ID response to the EEC including the Edge UE ID(s). +- 5. Upon receiving the response from the EES, the EEC provides the Edge UE ID information to the AC by sending the Edge UE ID response. +- 6. The AC provides the Edge UE ID information to the EAS. + +NOTE 6: Details on how the AC provides the information to the EAS is out of scope. + +- 7. Once received from the AC, the EAS uses the Edge UE ID to invoke the APIs provided by the EES over EDGE-3 interface (e.g. T-EAS Discovery, UE location request, ACR request, and EELManagedACR services). +- 8. Once received from the EES, the EEC uses the Edge UE ID to invoke API provided by the EES over EDGE-1 interface (e.g. EAS Discovery and ACR request services). +- 9. The EES uses the UE ID received from the EEC or obtained from the CN in step 3 to invoke the 3GPP CN capabilities as in TS 23.558, Clause 8.10.3. This step can be performed following triggers that require 3GPP CN capabilities to be invoked (e.g. on receiving a request over EDGE-1 or EDGE-3), in which case, to invoke the 3GPP CN capabilities the EES uses the UE ID associated with the Edge UE ID included in the trigger. + +NOTE 7: This procedure has impacts on EDGE-5 interface. + +### 7.23.3 Solution evaluation + +This solution solves open issues of KI#16. The solution provides three approaches to obtain UE ID. In the first approach of this solution EES translates the EEC provided UE's private IP address to its UE ID using the CN provided capability (Nnef\_UEId\_Get). This UE ID is then shared back to the EEC, which provides it to the AC. AC can then share the UE ID with the EAS for use over EDGE-3 interface. + +In some network deployments, there may be a private IP address overlap issue where more than one UE is assigned the same private IP address. Support from SA2 is required in such cases. + +In second approach (as captured in step 3.b. of clause 7.23.2.2), EES uses NATed/public IP of the UE to obtain the UE ID. In a third approach (as captured in step 3.c. of clause 7.23.2.2), EES uses the globally unique EECID to obtain the UE ID. These approaches require enhancement of 3GPP CN. + +NOTE: These two additional approaches require coordination with SA2 to handle this as part of the alignment work in Rel-18. In particular, the third approach would additionally require enhancement of the 3GPP CN to maintain an association between the EECID and UE ID, which also requires coordination with SA2. Furthermore, additional coordination is required with SA3 in determining whether there is any security issue in using an identifier, i.e. the EECID, which is not provided by the 3GPP CN to map to a UE ID. + +In all approaches, the solution also allows the EES to convert the CN or EEC provided UE ID to Edge UE ID, which is managed by the EES. Edge UE ID ensures privacy of the UE ID and allows the EES to assign EAS specific IDs for + +controlled access over EDGE-3 interface. EEC can request the Edge UE ID on its own, this allows the EEC to use the received Edge UE ID over EDGE-1 interface. + +Coordination with SA3 is required to check whether there is a security issue if the EEC shares its private IP address or MSISDN with a trusted 3rd party EES. + +In this solution, whether EESs use the same or different algorithms to generate Edge UE ID and whether the Edge UE ID should be unique should be specified in normative work. + +## 7.24 Solution #24: ACR between EAS and CAS with CES + +### 7.24.1 Architecture enhancements + +Architecture enhancements in clause 6.6 is the basis for this solution. + +### 7.24.2 Solution description + +#### 7.24.2.0 General + +![Diagram illustrating UE movement between two EDNs and a Cloud DN. The UE moves from an EES in the first EDN to a CES in the Cloud DN, and then to an EES in the second EDN. The EES in the first EDN is connected to an EAS. The CES in the Cloud DN is connected to a CAS. The EES in the second EDN is connected to an EAS.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +The diagram shows three network domains: two Edge Data Networks (EDN) and one Cloud DN. In the first EDN (left cloud), there is an S EAS and an S EES. A UE (represented by a mobile device icon) is connected to the S EES. In the Cloud DN (bottom), there is an S CAS and an S CES. The UE is shown moving from the S EES in the first EDN to the S CES in the Cloud DN, and then to the S EES in the second EDN (right cloud). The S EES in the second EDN is connected to an S EAS. The movement of the UE is indicated by large green arrows. + +Diagram illustrating UE movement between two EDNs and a Cloud DN. The UE moves from an EES in the first EDN to a CES in the Cloud DN, and then to an EES in the second EDN. The EES in the first EDN is connected to an EAS. The CES in the Cloud DN is connected to a CAS. The EES in the second EDN is connected to an EAS. + +Figure 7.24.2-2: UE moves from one EDN to Cloud DN then to another EDN + +As depicted in figure 7.24.2-2, since the EAS may have service area restriction, once the UE is moving out of the current edge coverage, to keep service continuity, the application client needs to connect to either another EAS in new EDN or the CAS. For the latter case, when CES is deployed, the EES may interact with the CES via EDGE-9' reference point and application context is transferred between the EAS and CAS. Later, if the UE is moving to an area with edge coverage, the CES interacts with the EES via EDGE-9' reference point and application context is transferred between the CAS and EAS. + +#### 7.24.2.1 ACR Scenarios + +The ACR scenarios in TS 23.558 can be extended to include ACR between EAS and CAS. The extension would also include extensions to relevant procedures used in the ACR Scenarios (e.g. Service provisioning, T-EAS discovery, ACR request). + +##### 7.24.2.1.1 CAS decided ACR scenario + +TS 23.558 clause 8.8.2.4 "S-EAS decided ACR scenario" can be updated to allow "CAS decided ACR scenario". The S-EAS can be the CAS, the S-EES can be the CES when ACR happens between CAS and EAS. The CES will, therefore, need to be part of the EEL that facilitate the discovery of the T-EAS by interacting with the ECS. + +Since in this procedure T-EAS discovery is used by the CAS – in step 3 – to discover the T-EAS the procedure in TS 23.558 clause 8.8.3.2 "Discover T-EAS" is also updated as described in clause 7.25.2.2.2. + +##### 7.25.2.2.2 "Discover T-EAS" for CAS + +TS 23.558 clause 8.8.3.2 "Discover T-EAS" can be updated to allow CAS to discover T-EAS. The S-EAS can be the CAS, the S-EES can be the CES when ACR happens between CAS and EAS. Therefore, the CES has to be part of the EEL to facilitate the discovery of the T-EAS by interacting with the ECS. + +### 7.24.3 Solution evaluation + +This solution addresses KI#11. The introduction of CES deployed in the central DN enables application service continuity using EDGEAPP mechanisms. + +The solution provides ACR scenario parity support for relocating application session between EAS and CAS, existing 5 ACR scenarios (including service continuity planning) can be supported with introduction of CES. + +## 7.25 Solution #25: ACR between EAS and CAS without CES + +### 7.25.1 Architecture enhancements + +Architecture enhancements in clause 6.5 is the basis for this solution. + +### 7.25.2 Solution description + +#### 7.25.2.1 General + +The following solution addresses open issues of key issue #11, ACR between EAS and Cloud Application Server. + +#### 7.25.2.2 Procedure + +The scenarios specified in 3GPP TS 23.558 (Rel-17) clause 8.8 have been updated to consider the ACR between EAS and Cloud Application Server. + +##### 7.25.2.2.1 Updated 3GPP TS 23.558 clause 8.8.2.2 Initiation by EEC using regular EAS Discovery + +The scenario handles ACR as a result of the UE moving to, or the UE expecting to move to, a new location which is outside the service area of the serving EAS. It further relies on the EEC being triggered as a result of the UE's movement. + +This scenario is based on Service Provisioning (as specified in TS 23.558) and DNS procedures to discover the CAS that shall serve the AC as a result of the UE's new location, and that shall receive the Application Context from the serving EASs. The scenario below describes the relocation of a single application context to a CAS. However, it should be repeated for each active AC in the UE for which EAS or EDN is not available on that UE location. + +![Sequence diagram showing the ACR process initiated by the EEC and AC across four phases: ACR Detection, ACR Decision, ACR Execution, and Post-ACR Clean up. Lifelines include CAS, S-EAS, AC, EEC, ECS, and S-EES.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant CAS + participant S-EAS + participant AC + participant EEC + participant ECS + participant S-EES + + Note left of CAS: Phase I: ACR Detection + EEC->>AC: 1. UE location update + Note left of CAS: Phase II: ACR Decision + AC->>EEC: 2. Decision + Note left of CAS: Phase III: ACR Execution + EEC->>AC: 3. Service Provisioning for new location + AC->>EEC: 4. Suitable EDN unavailable + EEC->>AC: 5. DNS query/discovery + AC->>EEC: 6a. ACR request + EEC->>S-EES: 6b. App Context Relocation Request + Note left of CAS: Phase IV: Post-ACR Clean up + S-EES->>AC: 7. Application Context Transfer + AC->>S-EAS: 8. ACR status update + S-EAS->>EEC: 9. ACR complete notify + +``` + +Sequence diagram showing the ACR process initiated by the EEC and AC across four phases: ACR Detection, ACR Decision, ACR Execution, and Post-ACR Clean up. Lifelines include CAS, S-EAS, AC, EEC, ECS, and S-EES. + +**Figure 7.25.2.2.1-1: Updated 3GPP TS 23.558 Figure 8.8.2.2-1: ACR initiated by the EEC and AC** + +The pre-conditions: + +1. The AC in the UE already has a connection to a corresponding S-EAS; +2. The preconditions for the Service provisioning - Request/Response model as specified in TS 23.558 with regards to the EEC are fulfilled; and +3. The EEC is triggered when it obtains the UE's new location or is triggered by another entity such as an ECS notification. + +Phase I: ACR Detection + +1. The EEC detects the UE location update as a result of a UE mobility event and is provided with the UE's new location as described in TS 23.558. The EEC can also detect an expected or predicted UE location in the future as described in TS 23.558. + +NOTE 1: If the EEC is triggered by an external entity such as by a notification from the ECS, unavailability of new EESs (to be used as T-EESs) is provided by that notification and step 3 below is skipped. + +Phase II: ACR Decision + +2. Either the AC or the EEC makes the decision to perform the ACR. + +NOTE 2: Which applications require ACR can be decided based on the application profile, e.g. requirement of service continuity of the application. + +###### Phase III: ACR Execution + +3. The EEC performs Service Provisioning (as specified in TS 23.558) for all active applications that require ACR. Since the location of the UE has changed, this procedure results in unavailability of T-EESs that are relevant to the supplied applications and the new location of the UE. If the service provisioning is done without supplying the application information but EES information is provisioned, the EEC attempts discovering relevant T-EAS with the EES provisioned in the service provisioning response, if any. Service provisioning or discovery of relevant T-EAS may not result in EES configuration or T-EAS is not discovered respectively. + +If the change in UE's location does not trigger a need to change the serving EAS, the subsequent steps will not take place. The EEC remains connected to the serving EESs and the ACs remain connected to their corresponding serving EASs. + +4. If the change in the UE's location triggers a need to change the S-EAS but the EEC is not provided with a T-EAS, the EEC informs the AC of the unavailability of a suitable EDN for the new location of the UE. +5. The AC triggers the UE to perform DNS resolution for the CAS relevant for the AC. The UE may need to establish a new PDU connection to the CAS. +- 6a. The AC sends ACR request to the EEC and the EEC responds ACR response to the AC. +- 6b. The EEC performs ACR launching procedure (as described in TS 23.558) to the S-EES with the ACR action indicating ACR initiation and the corresponding ACR initiation data (along with the details of the CAS and without the need to notify the EAS). The S-EES may apply the AF traffic influence with the N6 routing information of the CAS in the 3GPP Core Network (if applicable), as described in TS 23.558. +7. The AC is triggered by the EEC to start ACT. The AC decides to initiate the transfer of application context from the S-EAS to the CAS. + +After the ACT is completed, the AC remains connected to the CAS and disconnects from the S-EAS; the EEC is informed of the completion of the ACT. + +The S-EAS or CAS can further decide to terminate the ACR, and the CAS can discard the application context (e.g. based on monitoring the location of the UE). It is up to the implementation of the S-EAS and CAS whether and how to make such a decision. + +##### Phase IV: Post-ACR Clean up + +8. The S-EAS sends the ACR status update message to the S-EES as specified in TS 23.558. +9. If the status in step 8 indicates a successful ACT, the S-EES sends the ACR information notification (ACR complete) message to the EEC to confirm that the ACR has completed as specified in TS 23.558. + +The CAS can perform the required CN capability exposure subscriptions upon receiving the application context. + +##### 7.25.2.2.2 Updated 3GPP TS 23.558 clause 8.8.2.3 EEC executed ACR via S-EES + +In this scenario, the EEC is triggered as a result of the UE's movement as described in 8.8.1.1 of TS 23.558. Figure 7.25.2.2.2-1 illustrates the EEC executing ACR via the S-EES. + +##### Pre-condition: + +1. The AC at the UE already has a connection to the S-EAS; and +2. The EEC is able to communicate with the S-EES. + +![Sequence diagram showing the EEC executed ACR process across four phases: ACR Detection, ACR Decision, ACR Execution, and Post-ACR Clean up. Lifelines include EEC, S-EAS, S-EES, ECS, and CAS.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant S-EAS + participant S-EES + participant ECS + participant CAS + + Note left of EEC: Phase I: ACR Detection + Note left of EEC: 1. Detection + + Note left of EEC: Phase II: ACR Decision + Note left of EEC: 2. Decision + + Note left of EEC: Phase III: ACR Execution + Note right of EEC: 3. T-EAS Discovery + Note right of EEC: 4. App Context Relocation Request + Note right of EEC: 5. Application context is transferred between S-EAS and T-EAS + + Note left of EEC: Phase IV: Post-ACR Clean up + Note right of EEC: 6. ACR status update + Note right of EEC: 7. ACR complete notify + +``` + +Sequence diagram showing the EEC executed ACR process across four phases: ACR Detection, ACR Decision, ACR Execution, and Post-ACR Clean up. Lifelines include EEC, S-EAS, S-EES, ECS, and CAS. + +**Figure 7.25.2.2.2-1: Updated 3GPP TS 23.558 Figure 8.8.2.3-1: EEC executed ACR** + +###### **Phase I: ACR Detection** + +1. The EEC detects that ACR may be required as described in clause 8.8.1.1 of TS 23.558. The EEC may detect that ACR may be required for an expected or predicted UE location in the future as described in clause 8.8.1.1 of TS 23.558. + +###### **Phase II: ACR Decision** + +2. The EEC decides to proceed required procedures for triggering ACR. + +###### **Phase III: ACR Execution** + +3. The EEC performs Service Provisioning (as specified in TS 23.558) for all active applications that require ACR. Since the location of the UE has changed, this procedure results in unavailability of T-EESs that are relevant to the supplied applications and the new location of the UE, as per the assumption of this scenario. Service provisioning or discovery of relevant T-EAS may not result in EES configuration or T-EAS is not discovered respectively. The AC triggers the UE to perform DNS resolution for the cloud application server relevant for the AC. The UE may need to establish a new PDU connection to the CAS. + +NOTE 1: Several EEC registrations with different EESs may result from T-EAS discovery process during a single ACR operation. + +NOTE 2: The EEC before determining to execute step 4 tries to discover T-EAS from one or more EESs (received in the service provisioning response). If none of the contacted EES(s) have required T-EAS then proceed with step 4. + +4. The EEC performs ACR launching procedure (as described in clause 8.8.3.4 of TS 23.558) to the S-EES with the ACR action indicating ACR initiation and the corresponding ACR initiation data (along with the details of the CAS and with the need to notify the EAS). The S-EES authorises the request from the EEC. The S-EES decides to execute ACR based on the information received from the EEC and/or EAS profile. The S-EES may apply the AF traffic influence with the N6 routing information of the CAS in the 3GPP Core Network (if applicable) and sends the ACR management notification for the "ACT start" event to the S-EAS, as described in clause 8.6.3, to initiate ACT between the S-EAS and the CAS. If the EEC has not subscribed to receive ACR information notifications for ACR complete events from the S-EES, the EEC subscribes for the notifications as described in clause 8.8.3.5.2 of TS 23.558. + +5. The S-EAS transfers the application context to the CAS at implementation specific time. This process is out of scope of the present specification. + +NOTE 3: The S-EAS or CAS can further decide to terminate the ACR, and the CAS can discard the application context based on information received from EEL and/or other methods (e.g. monitoring the location of the UE). It is up to the implementation of the S-EAS and CAS whether and how to make such a decision. + +###### Phase IV: Post-ACR Clean up + +6. The S-EAS sends the ACR status update message to the S-EES as specified in clause 8.8.3.8 of TS 23.558. +7. If the status in step 7 indicates a successful ACT, the S-EES sends the ACR information notification (ACR complete) message to the EEC to confirm that the ACR has completed as specified in clause 8.8.3.5.3 of TS 23.558. + +NOTE 4: The CAS can perform capability exposure subscription with 3GPP CN directly, upon receiving the application context, which may be helpful for handling future ACR scenarios e.g. ACR from cloud to edge. + +##### 7.25.2.2.3 Updated 3GPP TS 23.558 clause 8.8.2.4 S-EAS decided ACR scenario + +In this scenario, the S-EAS may detect the need of ACR locally or is notified by the S-EES via ACR management notifications for "ACR monitoring" events. The S-EAS make the decision about whether to perform the ACR, and starts the ACR at a proper time. + +Pre-conditions: + +1. The S-EAS may depend on the receipt of certain User plane path management events from the S-EES, e.g. "user plane path change" events or "ACR monitoring" events, to detect the need for an ACR. For the following procedure it is assumed that the S-EAS has subscribed to continuously receive the respective events from the S-EES; and +2. The EEC has subscribed to receive ACR information notifications for target information notification events and ACR complete events from the S-EES, as described in clause 8.8.3.5.2 of TS 23.558. + +![Sequence diagram illustrating the S-EAS decided ACR process across four phases: Detection, Decision, Execution, and Clean up. Lifelines: EEC, S-EAS, S-EES, ECS, CAS. The diagram shows the flow of information and control between these entities to perform the ACR.](8642df2e3828b25d27362bec6d5a0eae_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant S-EAS + participant S-EES + participant ECS + participant CAS + + Note left of EEC: Phase I: ACR Detection + S-EAS->>S-EES: 1. Detection + Note left of EEC: Phase II: ACR Decision + S-EAS->>S-EAS: 2. Decision + Note left of EEC: Phase III: ACR Execution + S-EAS->>ECS: 3. T-EAS Discovery + S-EAS->>CAS: 4. Selected CAS declaration + EEC->>S-EES: 5. Target information notification + S-EAS->>CAS: 6. Application context is transferred between S-EAS and CAS + Note left of EEC: Phase IV: Post-ACR Clean up + S-EAS->>S-EES: 7. ACR status update + EEC->>S-EES: 8. ACR complete notify + +``` + +Sequence diagram illustrating the S-EAS decided ACR process across four phases: Detection, Decision, Execution, and Clean up. Lifelines: EEC, S-EAS, S-EES, ECS, CAS. The diagram shows the flow of information and control between these entities to perform the ACR. + +**Figure 7.25.2.2.3-1: Updated 3GPP TS 23.558 Figure 8.8.2.4-1: S-EAS decided ACR** + +S-EAS decided ACR is outlined with four main phases: detection, decision, execution and clean up. + +Phase I: ACR Detection + +1. The S-EAS either receives ACR management notifications from source Edge Enabler Sever indicating that ACR may be required ("ACR monitoring" event), or self detects the need for ACR (e.g. upon receipt of a "user plane path change" event). If the ACR management notification indicates "ACR monitoring" event, then the notification will also contain the CAS information (see clause 8.6.3.2.3 of TS 23.558). The S-EAS may detect that ACR may be required for an expected or predicted UE location in the future as described in clause 8.8.1.1 of TS 23.558. + +NOTE 1: How the S-EAS self detects the local need for ACR is outside the scope of this specification. + +Phase II: ACR Decision + +2. The S-EAS makes the decision to perform the ACR + +NOTE 2: How the S-EAS determines when to start the ACR is outside the scope of this specification. + +##### Phase III: ACR Execution + +3. If the ACR required is self detected, the S-EAS requests the S-EES to discover the targets as described in TS 23.558. When S-EES determines that no relevant EAS is available for the UE's location it finds out the details of the CAS, e.g. via DNS query/discovery, and provides the details of the CAS to the S-EAS. After S-EAS determines to use CAS, the S-EAS may apply the AF traffic influence with the N6 routing information of the CAS in the 3GPP Core Network (if applicable). + +NOTE 3: EAS endpoint in discovery could be a FQDN of CAS, identical with the FQDN used in DNS query. + +4. The S-EAS sends selected CAS declaration message to S-EES, to inform S-EES the determined CAS to use as described in clause 8.8.3.7 of TS 23.558. +5. Based on the CAS selection information received from the S-EAS, the S-EES sends the target information notification to the EEC as described in clause 8.8.3.5.3 of TS 23.558. +6. The S-EAS transfers the application context to the CAS selected in step 3. This process is out of scope of the present specification. + +NOTE 4: The S-EAS or CAS can further decide to terminate the ACR, and the CAS can discard the application context based on information received from EEL and/or other methods (e.g. monitoring the location of the UE). It is up to the implementation of the S-EAS and CAS whether and how to make such a decision. + +##### Phase IV: Post-ACR clean up + +7. The S-EAS sends the ACR status update message to the S-EES as specified in clause 8.8.3.8 of TS 23.558. +8. If the status in step 8 indicates a successful ACT, the S-EES sends the ACR information notification (ACR complete) message to the EEC to confirm that the ACR has completed as specified in clause 8.8.3.5.3 of TS 23.558. + +NOTE 5: The CAS can perform capability exposure subscription with 3GPP CN directly, upon receiving the application context, which may be helpful for handling future ACR scenarios e.g. ACR from cloud to edge. + +##### 7.25.2.2.4 Updated 3GPP TS 23.558 clause 8.8.2.5 S-EES executed ACR + +Figure 7.25.2.2.4-1 illustrates the S-EES detecting, deciding and executing ACR from the S-EAS to the CAS. This may include EELManagedACR by S-EES when initiated by S-EAS as per clause 8.8.3.6 of TS 23.558. + +###### Pre-condition: + +1. The AC at the UE already has a connection to the S-EAS; +2. The EEC is able to communicate with the S-EES; +3. The EEC has subscribed to receive ACR information notifications for target information notification events and ACR complete events from the S-EES, as described in clause 8.8.3.5.2 of TS 23.558; +4. The S-EAS optionally subscribed to receive ACR management notifications for "ACR facilitation" events to the S-EES, in order to enable detection at S-EAS. +5. In case of EELManagedACR, the CAS has subscribed to receive ACT status notifications as described in clause 8.8.3.6.2.3 of TS 23.558. + +![Sequence diagram showing the S-EES executed ACR process. Lifelines: EEC, S-EAS, S-EES, ECS, CAS. The process is divided into four phases: Phase I: ACR Detection, Phase II: ACR Decision, Phase III: ACR Execution, and Phase IV: Post-ACR Clean up. Steps include initiation, detection, decision, execution, and cleanup.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant S-EAS + participant S-EES + participant ECS + participant CAS + + Note right of S-EAS: 1. Initiate EEL managed ACR + S-EAS->>S-EES: + Note left of S-EES: Phase I: ACR Detection + EEC->>EEC: 2. Detection + S-EAS->>S-EAS: 2. Detection + S-EES->>S-EES: 2. Detection + Note left of S-EES: Phase II: ACR Decision + S-EES->>EEC: 3. Inform S-EES + S-EES->>S-EAS: 4. Decision of application context relocation + Note left of S-EES: Phase III: ACR Execution + S-EES->>ECS: 5. T-EAS discovery + ECS->>EEC: 6. Target information notification + S-EES->>S-EAS: 7. Initiate application traffic influence + S-EES->>EEC: 8. ACR management notification + S-EAS->>CAS: 9. Application context is transferred between S-EAS and CAS + Note left of S-EES: Phase IV: Post-ACR Clean up + S-EES->>S-EAS: 10. ACR status update + S-EES->>EEC: 11. ACR complete notify + +``` + +Sequence diagram showing the S-EES executed ACR process. Lifelines: EEC, S-EAS, S-EES, ECS, CAS. The process is divided into four phases: Phase I: ACR Detection, Phase II: ACR Decision, Phase III: ACR Execution, and Phase IV: Post-ACR Clean up. Steps include initiation, detection, decision, execution, and cleanup. + +**Figure 7.25.2.2.4-1: Updated 3GPP TS 23.558 Figure 8.8.2.5-1: S-EES executed ACR** + +1. The S-EAS may initiate EELManagedACR with S-EES as specified in clause 8.8.3.6 of TS 23.558. In this step, the S-EAS and S-EES negotiate an address of the Application Context storage to S-EES. The S-EAS puts the Application Context at this address which can be further accessed by the S-EES when the ACT is required. + +In this case, the S-EES executes steps 2 (i.e. S-EES detection), 4, 5, 6, 7, 8, 9 and 11. Rest of steps are skipped. + +###### Phase I: ACR Detection + +2. Detection entities (S-EAS, S-EES, EEC) detect that ACR may be required as described in clause 8.8.1.1 of TS 23.558. The detection by the S-EES may be triggered by the User Plane path change notification received from the 3GPP Core Network due to S-EAS request for "ACR facilitation" event (see clause 8.6.3 of TS 23.558) or due to step 1. + +The detection entity may detect that ACR may be required for an expected or predicted UE location in the future as described in clause 8.8.1.1 of TS 23.558. + +###### Phase II: ACR Decision + +3. The detection entity performs ACR launching procedure (as described in clause 8.8.3.4 of TS 23.558) with the ACR action indicating ACR determination and the corresponding ACR determination data. +4. The S-EES authorises the message if received. The S-EES decides to execute ACR based on the information received or local detection, and the information of EEC context or EAS profile, and then proceed the below steps. + +###### Phase III: ACR Execution + +5. The S-EES determines the targets via the Discover T-EAS procedure in clause 8.8.3.2 of TS 23.558. When S-EES determines that no relevant EAS is available for the UE's location it finds out the details of the CAS, e.g. via DNS query/discovery. +6. The S-EES sends the target information notification to the EEC as described in clause 8.8.3.5.3 of TS 23.558. +7. The S-EES may apply the AF traffic influence with the N6 routing information of the CAS in the 3GPP Core Network (if applicable). +8. The S-EES sends the ACR management notification (e.g. as notification for "ACR facilitation" event or "ACT start" event as described in clause 8.6.3 or due to step 1) to the S-EAS to initiate ACT between the S-EAS and the CAS. +9. The Application Context is transferred from S-EAS to the CAS at implementation specific time. In the case of EELManagedACR, the S-EES accesses the Application Context from the address as per step 1 and the S-EES either engage in the ACT from S-EAS to the CAS (obtained as per step 5) in a secure way or S-EES shares the storage location of the Application Context with the CAS. Further the CAS accesses the Application Context. The S-EAS may also perform the ACT directly with CAS, the specification of such process is out of scope of the present document. + +NOTE 1: The Application Context is encrypted and protected by the application layer. The S-EES engages in the packet level transport of the Application Context and has no visibility to the content of the Application Context. + +NOTE 2: The S-EAS or CAS can further decide to terminate the ACR, and the CAS can discard the application context based on information received from EEL and/or other methods (e.g. monitoring the location of the UE). It is up to the implementation of the S-EAS and CAS whether and how to make such a decision. + +###### Phase IV: Post-ACR Clean up + +10. The S-EAS sends the ACT status update message to the S-EES as specified in clause 8.8.3.8 of TS 23.558. +11. If the status in step 10 indicates a successful ACT, the S-EES sends the ACR information notification (ACR complete) message to the EEC to confirm that the ACR has completed as specified in clause 8.8.3.5.3 of TS 23.558. + +NOTE 3: The Application Client mechanism to support switchover of the application traffic to CAS is out of scope of the specification. + +##### 7.25.2.2.5 EEC initiated ACR + +In this case, when AC is currently served by a CAS, the EEC detects the need for ACR and makes the decision about whether to perform the ACR and starts the ACR at a proper time. + +The EEC detects the need for ACR and decides to trigger ACR. If the EEC has a valid S-EES information (i.e. AC connected to an EAS before connecting to the CAS), the procedure is similar to the "Initiation by EEC using regular EAS Discovery" and "EEC executed ACR scenario via S-EES" as specified in TS 23.558 [2], clause 8.8.2.2 and clause 8.8.2.3; otherwise, the procedure is similar as "EEC executed ACR scenario via T-EES" as specified in TS 23.558 [2] clause 8.8.2.6. The procedures are with the difference that the CAS replaces the S-EAS. + +##### 7.25.2.2.6 CAS initiated ACR + +In this scenario, the CAS detects the need for ACR and makes the decision about whether to perform the ACR and starts the ACR at a proper time. + +When ACR happens between EAS and CAS, the S-EAS can be the CAS. During the ACR execution phase, the CAS needs to know the EES before continuing with T-EAS discovery. Once the CAS knows the EES, the T-EAS discovery and the remaining steps are similar to the "S-EAS decided ACR scenario" as specified in TS 23.558 clause 8.8.2.4, where the CAS acts like the S-EAS. + +###### 7.25.2.2.6.1 EES discovery via service provision triggering + +Assumptions: + +1. The ASP of the CAS or the CAS provider has a business relationship with the ECSP. +2. The ASP of the CAS or the CAS provider can validate the received EES endpoint received from the UE. This process is out of scope of 3GPP. +3. The EES can perform an authorization check to verify the CAS, similar to the EES can perform an authorization check on the EAS for registration and discovery. +4. It is assumed that in some cases the UE Identifier may not be shared with the CAS for privacy reasons (e.g. the user may not want to share its MSISDN outside of the EEL). + +![Sequence diagram for EES discovery via service provision triggering. Lifelines: EEC, AC, CAS, EES, ECS. The process is divided into three phases: Phase I: ACR Detection, Phase II: ACR Decision, and Phase III: ACR Execution. In Phase I, CAS sends a '1. Detection' message to EES. In Phase II, CAS sends a '2. Decision' message to EES. In Phase III, CAS sends a '3. Trigger Service Provisioning' message to EEC via AC. EEC then sends a '4. Service Provisioning' message to ECS. Finally, EEC sends a '5. Share UE Identifier and EES endpoint information' message to CAS.](ca5566458a134032dd860e88fdaa0d2b_img.jpg) + +``` +sequenceDiagram + participant EEC + participant AC + participant CAS + participant EES + participant ECS + + Note left of EEC: Phase I: ACR Detection + CAS->>EES: 1. Detection + Note left of EEC: Phase II: ACR Decision + CAS->>EES: 2. Decision + Note left of EEC: Phase III: ACR Execution + CAS->>EEC: 3. Trigger Service Provisioning + EEC->>ECS: 4. Service Provisioning + EEC->>CAS: 5. Share UE Identifier and EES endpoint information +``` + +Sequence diagram for EES discovery via service provision triggering. Lifelines: EEC, AC, CAS, EES, ECS. The process is divided into three phases: Phase I: ACR Detection, Phase II: ACR Decision, and Phase III: ACR Execution. In Phase I, CAS sends a '1. Detection' message to EES. In Phase II, CAS sends a '2. Decision' message to EES. In Phase III, CAS sends a '3. Trigger Service Provisioning' message to EEC via AC. EEC then sends a '4. Service Provisioning' message to ECS. Finally, EEC sends a '5. Share UE Identifier and EES endpoint information' message to CAS. + +**Figure 7.25.2.2.6.1-1: EES discovery via service provision triggering** + +1. The CAS detects the need for ACR. The CAS can detect ACR due to the UE location change to select and perform ACR to a suitable EAS in the service area. + +NOTE 1: How the CAS detects need for ACR is outside the scope of this specification. + +2. The CAS makes the decision to perform the ACR. + +NOTE 2: How the CAS determines when to start the ACR is outside the scope of this specification. + +3. The CAS triggers the EEC via the AC to perform service provisioning. + +NOTE 3: How the CAS triggers service provisioning is out of scope. + +4. The EEC performs service provisioning as described in TS 23.558 clause 8.3.3. + +5. The CAS receives EES endpoint information and optionally the UE Identifier from the AC. To preserve the privacy of the UE, the EEC can forward the Edge UE ID obtained from the EES as in Solution#23 as a UE Identifier. If the service provisioning in step 4 fails the CAS will not continue with ACR. + +NOTE 4: Detail on how the AC provides this information to the CAS is out of scope. + +NOTE 5: When the CAS performs the EAS discovery operation, the EES checks whether the requesting CAS is authorized to perform the discovery operation and may decide to reject or accept the request. + +NOTE 6: How the CAS determines when to start the ACR is outside the scope of this specification. + +###### 7.25.2.2.6.2 CAS initiated ACR via ECS + +Assumptions: + +1. The CAS has the business relationship with the ECSP. +2. The CAS can obtain the UEID information. + +![Sequence diagram for CAS initiated ACR via ECS](47e8c2042061e08a14e012472e9fdbaa_img.jpg) + +The diagram is a sequence diagram illustrating the interaction between six entities: EEC, AC, CAS, ECS, T-EES, and T-EAS. The process is divided into four phases: + +- Phase I: ACR Detection**: The CAS performs a self-detection (1. Detection). +- Phase II: ACR Decision**: The CAS performs a self-decision (2. Decision). +- Phase III: ACR Execution**: The CAS interacts with other entities: (3. Retrieve T-EES) to ECS, (4. T-EAS discovery) to T-EES, and (5. Application context is transferred between CAS and T-EAS). +- Phase IV: Post-ACR Clean up**: The CAS sends a notification (6. ACR complete notify) to the EEC. + +Sequence diagram for CAS initiated ACR via ECS + +Figure 7.25.2.2.6.2-1: CAS initiated ACR via ECS + +1. The CAS detects the ACR event. +2. The CAS determines the ACR is required which the service can be relocated to the edge. +3. The CAS can perform the Retrieve T-EES procedure to the ECS for the T-EES information as specified in TS 23.558 clause 8.8.3.3. +4. The CAS can perform the T-EAS discovery procedure to the T-EES for the T-EAS information as specified in TS 23.558 clause 8.8.3.3. +5. The application context is transferred between CAS and the T-EAS which is up to application layer's implementation. + +6. The CAS can send the target information via the ACR complete notify to the AC which is up to application layer's implementation, the target information including the T-EAS information. + +NOTE 1: An update of EEC context relocation procedure is to be specified in order to enable context transfer from the previous EDNs to the target EDN. Or without EEC context transfer, new registration with T-EES may be performed. + +NOTE 2: The EEC registration to the T-EES may be required after the ACR. + +NOTE 3: To preserve privacy, how the Edge UE ID can be obtained and used instead of the UE ID will be addressed during normative. + +### 7.25.3 Solution evaluation + +The procedures described in solution #25 has a mixed use of regular DNS query and EDGEAPP EAS discovery. When a T-EAS cannot be discovered using the EDGEAPP mechanism, EDGEAPP entities (e.g. AC) falls back to regular DNS query. It supports ACR scenarios for ACR from EAS to CAS, and it also supports ACR scenarios for ACR from CAS to EAS. For ACR from CAS to EAS, the solution requires the CAS and AC interactions, which is out of scope of this specification. Whether the scenario assumptions are valid requires further evaluation. + +## 7.26 Solution #26: Bundled EASs + +### 7.26.1 Architecture enhancements + +None. + +### 7.26.2 Solution description + +#### 7.26.2.1 General + +This solution corresponds to KI#18 on EAS bundles. + +NOTE: Overlap with any solution for KI#20 must be considered during normative. + +The solution extends the AC profile, EAS profile and EES profile to introduce the following new IEs and their handling by different EEL functions: + +- EAS bundle information: EAS bundle information (e.g. EAS bundle ID, information of associated EASs) establishes an association between the EASs. Edge Enabler Layer handles the Edge Application Servers belonging to the same bundle as required by the bundle requirements. When included in the EAS profile, EAS Bundle information denotes the bundle to which the EAS belongs. When included in the AC profile EAS Bundle information is used to perform different Edge Enabler Layer operations, such as EAS discovery. +- EAS bundle requirements: This IE provides the Edge Enabler Layer the requirements that apply to the bundle of EAS. The requirements may include combined discovery and combined ACR. + +Both, EAS bundle information and EAS bundle requirements, are provided by the ASP. EAS bundle information can be a list of EASs or a bundle ID, however, detailed format of the EAS bundle ID is out of scope. + +**Table 7.26.2.1-1: AC Profile** + +| Information element | Status | Description | +|---------------------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACID | M | Identity of the AC. | +| AC Type | O | The category or type of AC (e.g. V2X). This is an implementation specific value. | +| Preferred ECSP list | O | When used in a service provisioning request, this IE indicates to the ECS which ECSPs are preferred for the AC. The ECS may use this information in the selection of EESs. | +| AC Schedule | O | The expected operation schedule of the AC (e.g. time windows) | +| Expected AC Geographical Service Area | O | The expected location(s) (e.g. route) of the hosting UE during the AC's operation schedule. This geographic information can express a geographic point, polygon, route, signalling map, or waypoint set. | +| AC Service Continuity Support | O | Indicates if service continuity support is required or not for the application. The IE also indicates which ACR scenarios are supported by the AC and which of these are preferred by the AC. | +| List of EASs | O | List of EAS that serve the AC along with the service KPIs required by the AC | +| > EASID | M | Identifier of the EAS | +| > Expected AC Service KPIs | O | KPIs expected in order for ACs to receive currently required services from the EAS, as described in Table 8.2.3-1 | +| > Minimum required AC Service KPIs | O | Minimum KPIs required in order for ACs to receive meaningful services from the EAS, as described in Table 8.2.3-1 | +| EAS bundle information | O | Information of the EAS bundle which AC requires. | +| EAS bundle requirements | O | Requirements associated with the EAS bundle. | +| > Coordinated EAS discovery | O | Indicates if AC requires coordinated EAS discovery. | +| > Coordinated ACR | O | Indicates if AC requires coordinated ACR.

The IE may further indicate what actions must be taken if ACR for one or more bundled EAS fails e.g. ACR for all other EAS that are part of the bundle must be cancelled or not. | + +**Table 7.26.2.1-2: EAS Profile** + +| Information element | Status | Description | +|-----------------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EASID | M | The identifier of the EAS | +| EAS Endpoint | M | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS. This information maybe discovered by EEC and exposed to ACs so that ACs can establish contact with the EAS. | +| List of EAS bundle information | O | List of EAS bundles to which the EAS belongs and related bundling requirements. | +| > EAS bundle information | M | Information of the bundle to which EAS belongs. | +| > EAS bundle requirements | O | Requirements associated with the bundle | +| >> Coordinated EAS discovery | O | Indicates if EAS discovery request for one of the bundled EAS is received, then EAS discovery response should include information of all the EASs belonging to the bundle. | +| >> Coordinated ACR | O | Indicates if EAS ACR is initiated for one of the bundled EAS, then ACR should be initiated for all the EASs belonging to the bundle.

The IE may further indicate what actions must be taken if ACR for one or more bundled EAS fails e.g. ACR for all other EAS that are part of the bundle must be cancelled or not. | +| ACID(s) | O | Identifies the AC(s) that can be served by the EAS | +| EAS Provider Identifier | O | The identifier of the ASP that provides the EAS. | +| EAS Type | O | The category or type of EAS (e.g. V2X) | +| EAS description | O | Human-readable description of the EAS | +| EAS Schedule | O | The availability schedule of the EAS (e.g. time windows) | +| EAS Geographical Service Area | O | The geographical service area that the EAS serves. ACs in UEs that are located outside that area shall not be served. | +| EAS Topological Service Area | O | The EAS serves UEs that are connected to the Core Network from one of the cells included in this service area. ACs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. | +| EAS Service KPIs | O | Service characteristics provided by EAS, detailed in Table 8.2.5-1 | +| EAS service permission level | O | Level of service permissions e.g. trial, gold-class supported by the EAS | +| EAS Feature(s) | O | Service features e.g. single vs. multi-player gaming service supported by the EAS | +| EAS Service continuity support | O | Indicates if the EAS supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EAS. | +| List of EAS DNAI(s) | O | DNAI(s) associated with the EAS. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [2].

It is a subset of the DNAI(s) associated with the EDN where the EAS resides. | +| List of N6 Traffic Routing requirements | O | The N6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI. | +| EAS Availability Reporting Period | O | The availability reporting period (i.e. heartbeat period) that indicates to the EES how often it needs to check the EAS's availability after a successful registration. | +| EAS Status | O | The status of the EAS (e.g. enabled, disabled, etc.) | + +**Table 7.26.2.1-3: EES Profile** + +| Information element | Status | Description | +|------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EESID | M | The identifier of the EES | +| EES Endpoint | M | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EES. This information is provided to the EEC to connect to the EES. | +| EASIDs | M | List of EASIDs registered with the EES. | +| > EAS bundle information | O | Information of the bundle to which EAS belongs. | +| EEC registration configuration | M | Indicates whether the EEC is required to register on the EES to use edge services or not. | +| EES Provider Identifier | O | The identifier of the ECSP that provides the EES Provider. | +| EES Topological Service Area | O | The EES serves UEs that are connected to the Core Network from one of the cells included in this service area. EECs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. | +| EES Geographical Service Area | O | The area being served by the EES in Geographical values (as specified in clause 7.3.3.3) | +| List of EES DNAI(s) | O | DNAI(s) associated with the EES. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [2].

It is a subset of the DNAI(s) associated with the EDN, where the EES resides. | +| EES Service continuity support | O | Indicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES. | + +**Table 7.26.2.1-4: EAS discovery filters** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------| +| List of AC characteristics (NOTE 1) | O | Describes the ACs for which a matching EAS is needed. | +| > AC profile (NOTE 2) | M | AC profile containing parameters used to determine matching EAS. AC profiles are further described in Table 8.2.2-1. | +| List of EAS characteristics (NOTE 1, NOTE 3) | O | Describes the characteristic of required EASs. | +| > EASID | O | Identifier of the required EAS. | +| > EAS bundle information | O | Information of the EAS bundle which AC requires. | +| > EAS provider identifier | O | Identifier of the required EAS provider | +| > EAS type | O | The category or type of required EAS (e.g. V2X) | +| > EAS schedule | O | Required availability schedule of the EAS (e.g. time windows) | +| > EAS Geographical Service Area | O | Location(s) (e.g. geographical area, route) where the EAS service should be available. | +| > EAS Topological Service Area | O | Topological area (e.g. cell ID, TAI) for which the EAS service should be available. See possible formats in Table 8.2.7-1. | +| > Service continuity support | O | Indicates if the service continuity support is required or not. | +| > Service permission level | O | Required level of service permissions e.g. trial, gold-class | +| > Service feature(s) | O | Required service features e.g. single vs. multi-player gaming service | +| NOTE 1: Either "List of AC characteristics" or "List of EAS characteristics" shall be present.
NOTE 2: "Preferred ECSP list" IE shall not be present.
NOTE 3: The "List of EAS characteristics" IE must include at least one optional IE, if used as an EAS discovery filter. | | | + +**Table 7.26.2.1-5: Retrieve EES request** + +| Information element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------------------------------| +| EESID | M | Unique identifier of the EES. | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| EASID | M | The EASID. | +| EAS bundle information | O | Information of the EAS bundle which AC requires. | +| Target DNAI | O | The target DNAI information which can be associated with potential T-EES(s) and/or T-EAS(s). | +| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) | +| UE location | O | The location information of the UE. The UE location is described in clause 7.3.2. | + +#### 7.26.2.2 Handling of EAS bundle information by the EEC + +If AC profile contains an EAS bundle information, the EEC uses it while performing operations on EDGE-1 interface. + +#### 7.26.2.3 Handling of EAS bundle information and EAS bundle requirements by the EES + +The EES may receive the EAS bundle information from the EEC, EAS or another EES and the EAS bundle requirements from the EAS. + +Upon receiving the EAS bundle information and EAS bundle requirements as part of the EAS registration request from the EAS, the EES stores the information and associates the EAS with other EASs providing the same EAS bundle information. The EAS bundle requirements are used by the EES while providing services on EDGE-1, EDGE-3 and EDGE-9 interfaces. + +Upon receiving the EAS bundle information as part of the: + +- EAS discovery request from the EEC, EAS or another EES, and depending on the EAS bundle requirements the EES provides in the EAS discovery response information of all the EASs which are part of the EAS bundle. +- ACR request from the EEC or the EAS, and depending on the EAS bundle requirements the EES takes appropriate ACR related action (e.g. initiate ACR, cancel ACR etc.) for all the EASs which are part of the EAS bundle. +- Retrieve T-EES request from the S-EES, and depending on the EAS bundle information, the ECS provides in the Retrieve T-EES response information of the T-EES(s) within the same EDN for the bundle EAS. + +#### 7.26.2.4 Handling of EAS bundle information by the ECS + +*Editor's note: Changes to the EES profile and handling by ECS may not be required depending on the feedback from SA4 on requirements (e.g. similar latency) for EAS bundles.* + +*Editor's note: Changes to the EES profile and handling by ECS may not be required or should be enhanced if SA5 cannot guarantee a deployment with EASs deployed in different EDNs satisfying EAS bundle requirements (i.e. similar latency, if it exists).* + +The ECS may receive the EAS bundle information from the EES during EES registration. + +Upon receiving the EAS bundle information as part of the EES registration, the ECS stores the information and associates the EES with other EESs providing the same EAS bundle information. + +Upon receiving the EAS bundle information as part of the: + +- Service provisioning request from the EEC or Retrieve EES request from the EES, the ECS in response provides information of all the EESs which provided the same EAS bundle information. + +#### 7.26.2.5 Handling of EAS bundle when the bundle EAS are registered on the multiple EESs in the same EDN + +The scenario assumption of this solution is that there is a coordinated ACR requirement for KI#18, i.e. the bundled EAS may need to be relocated together. + +**Editor's note:** This solution will not be used if SA4 don't have requirement for coordinated ACR in EAS bundle case; and solution needs to be revisited if SA4 clarifies such requirement existence. + +The EES may receive the EAS bundle information from the EEC. The EEC may receive the one or more EES information from the ECS when the bundle EAS located on multiple EES from same Edge Hosting Environment. + +NOTE 1: The Edge Hosting Environment is an environment providing support required for Edge Application Server's execution, which can be seen as the data center + +NOTE 2: The terminology of bundled EAS will be aligned with the meeting conclusion. + +NOTE 3: EDN may have one or more discrete data centers/EHE with the common outbound entry point of transport network, multiple EASs in one data centers/EHE has the same transport network performance. + +**Editor's note:** This solution will not be used for the case where SA5 can ensure that all EASs of the bundle are registered on the same EES when the EAS bundle is in the same EDN. Coordination with SA5 is required. + +Upon receiving the EAS bundle information as part of the: + +- Service provisioning request from the EEC, the ECS can determine the EES based on the bundled EAS information e.g. EAS bundle requirements, the ECS may select one or more EES which support all of the bundled EAS within the same EHE based on the EES EHE information obtained in the EES profile. Then the ECS provides associated EES(s) information (one or more EES information) in the service provisioning response. +- The EAS discovery request or selected EAS announcement request from the EEC contains bundled EAS distribution information (e.g. associated EES(s) information) +- When ACR happens on one of the bundled EAS, the associated EES can trigger the ACR for all the EAS in the bundled EAS by coordinated with other S-EES as per bundled EAS distribution information. + +##### 7.26.2.5.1 ACR procedure for bundled EAS located on multiple EES within EHE for S-EES executed ACR + +In this procedure, the EES#1 is responsible to notify the associated EES#2 with the need of application context relocation. To ensure that the associated target EES(s) are in the same EHE, EES#1 may perform retrieve T-EES procedure and T-EAS discovery procedure considering the bundled EAS information and notify the associated EES2 with the target EHE information. + +Pre-conditions: + +1. The S-EES can obtain the associated EES information. + +![Sequence diagram illustrating the ACR for bundled EAS located on multiple EES within same EHE. The diagram shows interactions between S-EAS#1, S-EES#1, ECS, S-EES#2, S-EAS#2, and T-EES. The sequence of messages is: 1. ACR detection (S-EAS#1/S-EES#1); 2. ACR requirement for bundle EAS request (S-EES#1 to S-EES#2); 3. ACR requirement for bundle EAS (S-EES#2 to S-EAS#2); 4. ACR requirement for bundle EAS response (S-EES#2 to S-EES#1); 5. Retrieve T-EES (S-EES#1 to ECS); 6. Target EHE announcement request (Target EHE) (S-EES#1 to S-EES#2); 7. Target EHE announcement response (S-EES#2 to S-EES#1); 8. Retrieve T-EES (S-EES#2 to ECS); 9. T-EAS discovery (S-EES#1 and S-EES#2); 10. Application context Transmission (S-EAS and T-EES).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant S-EAS#1 + participant S-EES#1 + participant ECS + participant S-EES#2 + participant S-EAS#2 + participant T-EES + + Note left of S-EAS#1: 1. ACR detection + S-EES#1->>S-EES#2: 2. ACR requirement for bundle EAS request + Note right of S-EES#2: 3. ACR requirement for bundle EAS + S-EES#2->>S-EES#1: 4. ACR requirement for bundle EAS response + Note left of ECS: 5. Retrieve T-EES + S-EES#1->>S-EES#2: 6. Target EHE announcement request (Target EHE) + S-EES#2->>S-EES#1: 7. Target EHE announcement response + Note right of ECS: 8. Retrieve T-EES + Note left of S-EES#1: 9. T-EAS discovery + Note right of S-EES#2: 9. T-EAS discovery + Note left of S-EAS#1: 10. Application context Transmission + +``` + +Sequence diagram illustrating the ACR for bundled EAS located on multiple EES within same EHE. The diagram shows interactions between S-EAS#1, S-EES#1, ECS, S-EES#2, S-EAS#2, and T-EES. The sequence of messages is: 1. ACR detection (S-EAS#1/S-EES#1); 2. ACR requirement for bundle EAS request (S-EES#1 to S-EES#2); 3. ACR requirement for bundle EAS (S-EES#2 to S-EAS#2); 4. ACR requirement for bundle EAS response (S-EES#2 to S-EES#1); 5. Retrieve T-EES (S-EES#1 to ECS); 6. Target EHE announcement request (Target EHE) (S-EES#1 to S-EES#2); 7. Target EHE announcement response (S-EES#2 to S-EES#1); 8. Retrieve T-EES (S-EES#2 to ECS); 9. T-EAS discovery (S-EES#1 and S-EES#2); 10. Application context Transmission (S-EAS and T-EES). + +**Figure 7.26.2.5.1-1: ACR for bundled EAS located on multiple EES within same EHE** + +1. The S-EAS#1 or the S-EES#1 detect the ACR event and determine to perform the application context relocation. +2. If the S-EES#1 obtain the associated EES(s) information which containing multiple EESs, the S-EES#1 send the ACR requirement for bundled EAS request to the associated EES (e.g. EES#2) obtained in the EAS discovery request or selected EAS announcement request from the EEC, indicating that there is a need for ACR and the S-EES#1 will determine target EHE for the bundled EAS. +3. The S-EES#2 may notify the EAS#2 that there is a need for ACR. +4. The S-EES#2 sends the ACR requirement for bundled EAS response. +5. The S-EES#1 send Retrieve T-EES request message to the ECS, the request message contains the all bundled EAS information. Upon receiving the request, the ECS can determine the T-EES and target EHE for the bundled EAS based on the bundled EAS information to ensure that the all the T-EES and T-EAS are within the same EHE. Then the ECS return the T-EES information and the target EHE for the bundled EAS to the S-EES#1. +6. S-EES#1 send the Target EHE announcement request message to the S-EES#2 including the target EHE information. +7. S-EES#2 will return the target EHE announcement response to the S-EES #1. +8. The S-EES#2 will send the Retrieve T-EES request message to the ECS, the request message contains the target EHE information. Upon receiving the request, the ECS can determine the T-EES for S-EES#2 based on the target EHE information. +9. The S-EES#1 will perform the T-EAS discovery for the S-EAS#1; the S-EES#2 will perform the T-EAS discovery for the S-EAS#2. +10. The application context transmission is performed between S-EAS and T-EAS. + +##### 7.26.2.5.2 ACR procedure for bundled EAS located on multiple EES within same EHE for S-EAS decided ACR scenario + +![Sequence diagram illustrating the ACR procedure for bundled EAS located on multiple EES within same EHE for S-EAS decided ACR scenario. The diagram shows interactions between S-EAS#1, S-EES#1, ECS, S-EES#2, S-EAS#2, and T-EES.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant S-EAS#1 + participant S-EES#1 + participant ECS + participant S-EES#2 + participant S-EAS#2 + participant T-EES + + Note over S-EAS#1, S-EES#1: 1. ACR detection + S-EAS#1->>S-EES#1: 2. ACR requirement for bundle EAS request + S-EES#1->>S-EES#2: 3. ACR requirement for bundle EAS + S-EES#2-->>S-EES#1: 4. ACR requirement for bundle EAS response + S-EES#1-->>S-EAS#1: 5. EAS discovery request + S-EAS#2->>S-EES#2: 5. EAS discovery request + Note over S-EES#1, ECS: 6. Retrieve T-EES + S-EES#1->>ECS: 7. Target EHE announcement request (Target EHE) + ECS-->>S-EES#1: 8. Target EHE announcement response + Note over S-EES#2, ECS: 9. Retrieve T-EES + S-EES#2->>ECS: 10. T-EAS discovery + Note over S-EES#1, S-EAS#2: 10. T-EAS discovery + S-EES#1-->>S-EAS#1: 11. EAS discovery response + S-EES#2-->>S-EAS#2: 11. EAS discovery response + Note over S-EAS#1, S-EAS#2: 12. Application context Transmission + +``` + +Sequence diagram illustrating the ACR procedure for bundled EAS located on multiple EES within same EHE for S-EAS decided ACR scenario. The diagram shows interactions between S-EAS#1, S-EES#1, ECS, S-EES#2, S-EAS#2, and T-EES. + +**Figure 7.26.2.5.2-1: ACR for bundled EAS located on multiple EES within same EHE** + +1. The S-EAS#1 or the S-EES#1 detect the ACR event and determine to perform the application context relocation. +2. The S-EAS#1 send the ACR requirement for bundled EAS request indicating that there is a need for ACR to the S-EES#1, and the S-EES#1 will determine the target EHE for the bundled EAS. If the S-EES#1 obtain the associated EES(s) information which containing multiple EESs (e.g. EES#2) obtained in the EAS discovery request or selected EAS announcement request from the EEC, the S-EES#1 will notify the associated S-EES#2 with the ACR requirement for bundled EAS. +3. The S-EES#2 may notify the EAS#2 that there is a need for ACR. +4. The S-EES#2 sends the corresponding response message of ACR requirement for bundled EAS request. Furthermore, the S-EES#1 will send the corresponding response message of ACR requirement for bundled EAS request to the S-EAS#1. +5. S-EAS#1 send the EAS discovery request message to the S-EES#1. S-EAS#2 send the EAS discovery request message to the S-EES#2 +6. The S-EES#1 send Retrieve T-EES request message to the ECS, the request message contains the all bundled EAS information. Upon receiving the request, the ECS can determine the T-EES and target EHE for the bundled EAS based on the all bundled EAS to ensure that the all the T-EES and T-EAS are within the same EHE. Then the ECS return the T-EES information and the target EHE for the bundled EAS to the S-EES#1. +7. S-EES#1 send the Target EHE announcement request message to the S-EES#2 including the target EHE information. +8. S-EES#2 will return the target EHE announcement response to the S-EES #1. +9. The S-EES#2 will send the Retrieve T-EES request message to the ECS, the request message contains the target EHE information. Upon receiving the request, the ECS can determine the T-EES for S-EES#2 based on the target EHE information. + +10. The S-EES#1 will perform the T-EAS discovery for the S-EAS#1; the S-EES#2 will perform the T-EAS discovery for the S-EAS#2. +11. The S-EES#1 will send the EAS discovery response message to the S-EAS#1; the S-EES#2 will send the EAS discovery response message to the S-EAS#2; +12. The application context transmission is performed between S-EAS and T-EAS. + +##### Enhancements to 3GPP TS 23.558 clause 8.3.3.3.3 + +8.3.3.3.3                      Service provisioning response + +**Table 8.3.3.3.3-1: Service provisioning response** + +| Information element | Status | Description | +|-----------------------------------------|----------|---------------------------------------------------------------------------------| +| Successful response | O | Indicates that the service provisioning request was successful. | +| > List of EDN configuration information | M | List of EDN configuration information as defined in Table 8.3.3.3.3-2. | +| Associated EES information | O | EES information which support all of the bundled EAS within the same EHE | +| Failure response | O | Indicates that the service provisioning request failed. | +| > Cause | O | Indicates the cause of service provisioning request failure. | + +##### Enhancements to 3GPP TS 23.558 clause 8.2.6 + +### 8.2.6 EES Profile + +The EES profile includes information about the EES and the services it provides. + +**Table 8.2.6-1: EES Profile** + +| Information element | Status | Description | +|--------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EESID | M | The identifier of the EES | +| EES Endpoint | M | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EES. This information is provided to the EEC to connect to the EES. | +| EASIDs | M | List of EASIDs registered with the EES. | +| EEC registration configuration | M | Indicates whether the EEC is required to register on the EES to use edge services or not. | +| EES Provider Identifier | O | The identifier of the ECSP that provides the EES Provider. | +| EES Topological Service Area | O | The EES serves UEs that are connected to the Core Network from one of the cells included in this service area. EECs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. | +| EES Geographical Service Area | O | The area being served by the EES in Geographical values (as specified in clause 7.3.3.3) | +| List of EES DNAI(s) | O | DNAI(s) associated with the EES. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [2].

It is a subset of the DNAI(s) associated with the EDN, where the EES resides. | +| EES EHE | O | EHE associated with the EES. | +| EES Service continuity support | O | Indicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES. | + +NOTE: The list of EES DNAI(s) can include the DNAI(s) of the EAS(s) registered with the EES. + +Enhancements to 3GPP TS 23.558 clause 8.5.3.2 + +#### 8.5.3.2 EAS discovery request + +Table 8.5.3.2-1 describes information elements for the EAS discovery request. Table 8.5.3.2-2 provides further detail about the EAS Discovery Filter information element. + +**Table 8.5.3.2-1: EAS discovery request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requestor identifier | M | The ID of the requestor (e.g. EECID) | +| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| EAS discovery filters | O | Set of characteristics to determine required EASs, as detailed in Table 8.5.3.2-2. | +| UE location | O | The location information of the UE. The UE location is described in clause 7.3.2. | +| Target DNAI (NOTE) | O | Target DNAI information which can be associated with potential T-EAS(s) | +| EEC Service Continuity Support | O | Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC or, if this message is sent by the EEC to discover a T-EAS, which ACR scenario(s) are intended to be used for the ACR. | +| EES Service Continuity Support (NOTE) | O | The IE indicates if the S-EES supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EES or, if the EAS discovery is used for an S-EES executed ACR according to clause 8.8.2.5, which ACR scenario is to be used for the ACR. | +| EAS Service Continuity Support (NOTE) | O | The IE indicates if the S-EAS supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EAS or, if the EAS discovery is used for an S-EAS decided ACR according to clause 8.8.2.4, which ACR scenario is to be used for the ACR. | +| Associated EES information | O | EES information which support all of the bundled EAS within the same EHE | +| > EES ID | O | The identifier of the EES | +| > EES Endpoint | O | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EES. This information is provided to the EEC to connect to the EES. | +| >> Bundled EAS information | O | Bundled EAS registered to this EES which AC requires | +| NOTE: This IE shall not be included when the request originates from the EEC. | | | + +### 7.26.3 Solution evaluation + +This solution addresses the open issues of KI#18. + +To identify the EAS bundles, the solution introduces EAS bundle information in the EAS profiles, allowing an EAS to be part of one or more EAS bundles. This information is then used by the ECS and the EES at the time of service provisioning and EAS discovery. To support the queries from the EEC, the EAS bundle information is also added in the AC profiles. + +The solution also allows EASs to indicate requirements related to the bundle, such as requesting coordinated EAS discovery or coordinated ACR (considering all scenarios). + +The solution also identifies the impacts on several EEL information flows and procedures to handle the EAS bundle information and related requirements. + +## 7.27 Solution #27: Enabling AC Association Aware services by selecting common EASs + +### 7.27.0 General + +This clause proposes solutions for KI#17 based on two distinct assumptions for achieving a common EES (which is necessary before determining a common EAS). The options corresponding to the two assumptions are termed "assumed common EES" and "with CAAR". CAAR functionality and deployment options are described as part of this solution. + +These two alternatives can be summarized as follows: + +- (i) Determine common EAS based on the assumption that common EES has been achieved/ pre-provisioned (option termed "assumed common EES"). + +NOTE 1: The requirements and underlying assumptions for this option are to be detailed in the normative phase. + +- (ii) Determine common EAS based on the assumption that ACs to be associated are mobile and may span multiple EDNs. This option uses a new functionality for maintaining information on AC Association serviced per EES (i.e. option "with CAAR" functionality), in order to optimize common EES discovery. + +The following descriptions apply to both alternatives for determining Common EES, unless sub-clause titles or clarifying NOTEs specify otherwise. + +This solution also relies upon the following assumption: + +- The ACID definition from TS 23.558 [2] v17.5.0 clause 7.2.5 applies, allowing ACs with the same or different ACIDs (which belong to different applications) to discover and use a common EAS. + +### 7.27.1 Architecture enhancements + +This solution uses the architecture option specified in clause 6.11. + +### 7.27.2 Solution description + +#### 7.27.2.1 General + +This solution addresses key issue #17 on discovery of a common EAS in clause 4.17. + +The solution describes enhancements to several edge procedures that enable ACs/EECs of different UEs to share AC association information with the EEL. This AC association is formed such that the services for the associated ACs are optimized by selecting a common EAS. + +NOTE: In the following descriptions within this solution, the term "Associated ACs" is used to denote a set of ACs on different UEs for which the association described above has been configured via an AC association Profile. How the AC association Profile is determined is out of scope of the current specification. + +#### 7.27.2.2 New Information Elements + +##### 7.27.2.2.1 AC Association Profile + +###### 7.27.2.2.1.1 Description + +The AC association Profile (AAP) is proposed as a new IE in TS 23.558: + +**Table 7.27.2.2.1.1-1: AC association Profile** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Association ID (NOTE 1) | M | Identifier of the Association | +| AC association type | M | Choice of dynamic grouping (multi-user multi-session, etc.), pre-grouped or none (default) | +| List of UE filter criteria | O | Information for filtering the UEs with associated ACs. | +| > UE group ID | O | If present, it indicates a 3GPP Group ID pre-provisioned (e.g. as External Group ID) to the UEs with ACs in the associated group/association. | +| > UEs service area | O | If provided, it indicates the Service area for determining other UEs in the association. The UE location is described in clause 7.3.2. The optional additional EAS selection criteria describe criteria for the EAS selection (e.g. "same latency for all" or "lowest latency for the own UE location"). | +| List of associated ACs characteristics | O | Information for determining the associated ACs. | +| > common ACID | O | If provided, all ACs in the association have the same AC ID as indicated | +| > common ACs Type | O | If provided, all ACs in the association have the same AC Type as indicated | +| > common ACs Schedule | O | If provided, all ACs in the association have the same AC Schedule as indicated | +| > List of Common EAS aggregate Service KPIs | O | Service characteristics provided by the common EAS, detailed in Table 8.2.5-1. The characteristics are described to meet the requirements for the AC association. | +| NOTE 1: It is to be determined in the normative phase whether and how this IE can also include an Association ID type, format or numbering (e.g. system-wide unique numbering, etc.) | | | + +NOTE: The list of IEs in Table 7.27.2.2.1.1-1 and whether AC association information should be provided in a new AC association Profile IE, or via existing IEs, is to be determined in the normative phase. + +###### 7.27.2.2.1.2 Determining grouping based on AC Association type + +AC Association Profiles (AAPs) are assumed to be provisioned using procedures out of scope of the current document. + +- **AC associations of type *pre-grouped*** are those for which the application of grouping criteria is done out-of-band (i.e. via an external group ID). Each of the association members is provided with an AAP which includes AC Association type (i.e. pre-grouped), UE group ID (same for all the ACs and equal to the external group ID) and List of Common EAS aggregate Service KPIs. This allows pre-grouped associations to be used for a variety of usecases. The AC grouping is then performed at EEL based only on this, limited AAP information. +- **AC associations of type *dynamic grouping*** are those for which the AAP provides characteristics/ criteria of the individual ACs (or corresponding UEs) within the association, with the AC grouping being performed at EEL based on the entire AAP information. + +The "List of associated AC characteristics" and the "UE filter criteria" IEs are used as characteristics for filtering the ACs in the dynamic association. + +Therefore, for AC associations of type dynamic grouping, the possibilities for EEL-based grouping are: + +1. Based on a matching associated ACs characteristics +2. Based on UE service area +3. Combinations of the above + +For all AC association types, if the "List of Common EAS aggregate Service KPIs" IEs is present in the AAP, it is used to determine the EAS(s) suitable to act as common EAS for the association, in addition to the EAS discovery filters. If + +the IE is not present in the AAP, common EAS determination relies upon other parameters provided, e.g. EAS discovery filters. + +AC Association ID is a unique identifier of an association within the EEL deployment or the system. The ID is necessary for uniquely identifying AC associations in the absence of the full AAP information. + +#### 7.27.2.3 Enhancements to existing Information Elements + +The enhancements captured (marked with bold text) in tables within this clause are proposed to Information Element tables in 3GPP TS 23.558 [2]. Enhancements to requests, responses and notifications are described in the following clauses via procedural descriptions. + +**Table 7.27.2.3-1: EAS discovery filters** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------| +| List of AC characteristics (NOTE 1) | O | Describes the ACs for which a matching EAS is needed. | +| > AC profile (NOTE 2) | M | AC profile containing parameters used to determine matching EAS. AC profiles are further described in Table 8.2.2-1. | +| List of EAS characteristics (NOTE 1, NOTE 3) | O | Describes the characteristic of required EASs. | +| > EASID | O | Identifier of the required EAS. | +| > EAS provider identifier | O | Identifier of the required EAS provider | +| > EAS type | O | The category or type of required EAS (e.g. V2X) | +| > EAS schedule | O | Required availability schedule of the EAS (e.g. time windows) | +| > EAS Geographical Service Area | O | Location(s) (e.g. geographical area, route) where the EAS service should be available. | +| > EAS Topological Service Area | O | Topological area (e.g. cell ID, TAI) for which the EAS service should be available. See possible formats in Table 8.2.7-1. | +| > Service continuity support | O | Indicates if the service continuity support is required or not. | +| > Service permission level | O | Required level of service permissions e.g. trial, gold-class | +| > Service feature(s) | O | Required service features e.g. single vs. multi-player gaming service | +| AC association profile | O | Describes an association between ACs and an association between ACs and a common EAS. | +| NOTE 1: Either "List of AC characteristics", "List of EAS characteristics" or AC association profile shall be present. | | | +| NOTE 2: "Preferred ECSP list" IE shall not be present. | | | +| NOTE 3: The "List of EAS characteristics" IE must include at least one optional IE, if used as an EAS discovery filter. | | | + +NOTE 1: The enhancement to EEC Context shown in table 7.27.2.3-2 is necessary for the option "with CAAR" (ii) as described in clause 7.27.0. It is to be determined in the normative phase whether this functionality is necessary for the "assumed common EES" (i) as described in clause 7.27.0. + +**Table 7.27.2.3-2: EEC Context** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EEC ID | M | Unique identifier of the EEC. | +| EEC Context ID | M | Identifier assigned to the EEC Context | +| Source EES Endpoint | M | The endpoint address (e.g. URI, IP address) of the EES that provided EEC context ID. | +| UE Identifier | O | The identifier of the hosting UE (i.e. GPSI or identity token) | +| List of EDGE-1 subscriptions | O | List of subscriptions IDs for capability exposure to the EEC ID (NOTE 1). | +| UE location | O | Latest UE location of the UE hosting the EEC which was available at the EES. | +| List of AC Profiles | O | Information about the ACs as described in Table 8.2.2-1. | +| List of AC association profiles | O | List of all AC associations applicable to the EEC | +| List of Service Session Contexts | O | List of associated Service Session Context IEs. Each Service Session Context includes information maintained by the EES for the services (involving UE related resources) received from an EAS registered to the EES. | +| > Service Session Context | M | Service Session Context is described in Table 8.2.8-2 (NOTE 2) | +| NOTE 1: The corresponding EDGE-1 subscription information may include 3GPP CN subscription information such as subscription correlation ID | | | +| NOTE 2: Whether the Service Session Context IE needs to contain AC Association ID as optional element, is to be determined in the normative phase. | | | + +NOTE 2: The enhancement to EDN configuration information shown in table 7.27.2.3-3 is necessary for the option "with CAAR" (ii) as described in clause 7.27.0. only. + +The IE enhancement is used to provide EECs in the service provisioning phase with information about which EESs already act as common EESs serving AC associations, and which are candidates. This enables the EEC to determine which EES to choose if common EAS association services are needed. Note that the service provisioning response can also be limited by ECS policies to include only the EDNs/EESs which provide such services. The information about served AC Associations per EES is provided by EESs to ECS using CAAR functionality. + +**Table 7.27.2.3-3: EDN configuration information** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EDN connection information (NOTE 1) | M | Information required by the UE to establish connection with the EDN. | +| > DNN/APN | M | Data Network Name/Access Point Name | +| > S-NSSAI | O | Network Slice information | +| > EDN Topological Service Area | O | The EDN serves UEs that are connected to the Core Network from one of the cells included in this service area. See possible formats in Table 8.2.7-1. | +| List of EESs | M | List of EESs of the EDN. | +| > EESID | M | The identifier of the EES | +| > EES Endpoint | M | The endpoint address (e.g. URI, IP address) of the EES | +| > EASIDs (NOTE 2) | O | List of EASIDs registered with the EES. | +| > EES Provider identifier | O | The identifier of the EES Provider (such as ECSP) | +| > EES Topological Service Area | O | The EES serves UEs that are connected to the Core Network from one of the cells included in this service area. EECs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. | +| > EES Geographical Service Area | O | The area being served by the EES in Geographical values (as specified in clause 7.3.3.3) | +| > List of EES DNAI(s) | O | DNAI(s) associated with the EES/EAS. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [2]. | +| > EES Service continuity support | O | Indicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES. | +| > EEC registration configuration | M | Indicates whether the EEC is required to register on the EES to use edge services or not. | +| >List of association IDs (NOTE 3) | O | List of association IDs of the AC associations the EES is serving | +| Lifetime | O | Time duration for which the EDN configuration information is valid and supposed to be cached in the EEC. | +| NOTE 1: If the UE is provisioned or pre-configured with URSP rules by the HPLMN, the UE handles the precedence between EDN connection info and URSP rules as defined in 3GPP TS 23.503 [12] clause 6.1.2.2.1. EDN connection info is considered to be part of UE Local Configurations. | | | +| NOTE 2: EAS information is limited to the EEC requested applications. If no AC profiles were present in the service provisioning request, the EAS information is subject to the ECSP policy (e.g. no EAS information or a subset of EAS information related to the EES). | | | +| NOTE 3: Whether the list needs to contain the entire AC association Profile, or the IDs are sufficient, is to be determined in the normative phase. | | | + +#### 7.27.2.4 Enhancements to Service Provisioning for determining common EES + +##### 7.27.2.4.1 Using the "assumed common EES" option (option i) + +If the "assumed common EES" option is used, procedures for determining common EES are not necessary. + +##### 7.27.2.4.2 Determining common EES with CAAR (option ii) + +During the service provisioning procedure defined in 3GPP TS 23.558 [2], the presence of an AC association Profile in the request triggers the use of the enhancements detailed in this clause. + +The service provisioning response is used to provide information about which EESs already act as Common EESs, i.e. providing services to AC associations, as well as candidates. In this option, the EES information is provided to EECs via the EDN Configuration Information in the service provisioning response, and it can be obtained by ECS using CAAR queries. + +**Enhancements to 3GPP TS 23.558 clause 8.3.3 Service Provisioning:** + +Steps: + +1. The service provisioning request (3GPP TS 23.558 [2] Table 8.3.3.3.2-1) from EEC to ECS is enhanced to include an AC association Profile. +2. Upon receiving the request, the ECS uses the AC association Profile information (e.g. association IDs) to query the (EES ID, AC association ID list) tuples stored by CAAR to determine whether an EES is already serving the AC association(s). The ECS uses the AC association ID(s) to query the CARR using the procedure in 7.27.2.8. +3. If the processing of the request with AC association Profile information was successful, the ECS responds to the EEC with a service provisioning response. The ECS uses the EES(s) obtained from the step 2 CAAR query to update the enhanced EDN configuration information (Table 7.27.2.3-4) with EES(s) already serving the AC association and sends it in the provisioning response. + +#### 7.27.2.5 Enhancements to EAS Discovery for determining common EAS + +During the EAS discovery procedure defined in 3GPP TS 23.558 [2], if the EEC sends an EAS discovery request to an EES including AC association Profile it triggers the use of the enhancements detailed in this clause. Based on the AC association Profile, the EES determines an EAS discovery result that includes a common EAS for the AC association. + +##### Enhancements to 3GPP TS 23.558 [2] clause 8.5.2.2 EAS Discovery (request-response model) + +Additional pre-condition: + +1. An AC association Profile has been provided to the EEC. + +Steps: + +1. The EEC sends an EAS discovery request to the EES. The EAS discovery request includes an AC association Profiles. Included in the AC association Profile is information regarding an association between AC(s) on this UE and other ACs indicating that the use of a common EAS is required. +2. Upon receiving the request, the EES determines whether a common EAS is available to provide services to the associated ACs that meet the criteria specified in the AC association Profile (i.e. List of Common EAS aggregate Service KPIs). +3. If the processing of the request was successful, the EES responds to the EEC with an EAS discovery response which includes information about the discovered common EAS able to provide services to the associated ACs. + +#### 7.27.2.6 Enhancements to ACR + +During the detection, decision-making and execution phases of the ACR procedures defined in 3GPP TS 23.558 [2], an AC association Profile can be used to identify ACs requiring a common EAS. This information can be used in the ACR procedures to coordinate the transitioning of an AC to a common EAS or transitioning a group of already associated ACs from a common S-EAS to a common T-EAS. + +NOTE 1: Coordination of the ACRs for AC association members is to be addressed in the normative phase. + +##### Enhancements to 3GPP TS 23.558[2] clause 8.8.3.2 Discover T-EAS procedure + +Steps: + +1. The S-EES checks if a registered or cached T-EAS satisfies the AC association Profile (e.g. Common EAS aggregate Service KPIs) stored in the EEC context and can serve as a common EAS for the associated ACs. +2. The EAS discovery filter (Table 7.27.2.3-1) within the EAS discovery request issued from the S-EES to the T-EES includes AC association Profile information (e.g. Common EAS aggregate Service KPIs). +3. The T-EES discovers the T-EAS(s) utilizing the Common EAS aggregate Service KPIs of the AC association profile, such that a common EAS able to serve the associated ACs is provided in the response. + +##### Enhancements to 3GPP TS 23.558 clause 8.8.3.3 Retrieve T-EES procedure: + +NOTE 2: In the "assumed common EES" (i) option, T-EES equals S-EES, so no enhancements are required for 3GPP TS 23.558 clause 8.8.3.3. + +Steps: + +1. The T-EES retrieve request (3GPP TS 23.558 [2] Table 8.8.4.6-1) from the S-EES to the ECS is enhanced to optionally include AC association Profile. +2. The ECS interacts with the 3GPP core network to retrieve the UE locations. + +The ECS determines a common T-EES for the AC association. + +NOTE 3: The ECS uses AC association Profile, UE location, as well as CAAR query as detailed in clause 7.27.2.8 to make this determination. + +In addition, if an "associated UE group ID" is provided in the AC association Profile, the ECS can interact with the 3GPP core network to determine the number of UEs present in candidate EES(s) service area(s). Alternatively, the ECS uses "Associated UEs service area" in the AC association Profile to determine whether the candidate EES service area meets the needs of the AC association. The ECS uses the associated UE group ID and UE locations to determine whether T-EESs are candidates for serving the AC association. + +##### Enhancements to 3GPP TS 23.558 clause 8.8.3.4 ACR launching procedure + +Steps: + +1. The ACR request message (3GPP TS 23.558 [2] Table 8.8.4.4-1) sent to the EES by EEC is enhanced to optionally include an AC association ID. +2. If the request in step 1 is for ACR initiation and if the EAS notification indication in ACR initiation data is provided in the step 1 request and the EAS has subscribed to receive such notification, the EES includes the association ID of the AC association in the notification. + +The notified EAS uses the AC association ID during the ACR status update procedure and stores it with the Application context maintained. The content of the application content maintained by EAS is out of scope of the current document. + +##### Enhancements to 3GPP TS 23.558 [2] clause 8.8.3.8 ACR status update procedure + +Steps: + +1. The EAS sends the ACR status update request message (3GPP TS 23.558 [2] Table 8.8.4.19-1) to the S-EES that is enhanced to include an association ID of the AC association for which the ACR has been performed. + +NOTE 4: S-EAS obtains the association ID via pre-provisioning, from an ACR management event notification or directly from the AC and stores it in the Application Context. T-EAS obtains the association ID via pre-provisioning or via ACT. + +2. If ACR is successful, the receiving EES uses the association ID information to update the information about the AC associations served. + +In the option "with CAAR" (ii) the EES update is to the information available at CAAR. The S-EES removes its corresponding (association ID, EES ID) tuple from CAAR. The T-EES adds its corresponding (association ID, EES ID) tuple to CAAR. + +NOTE 5: In the "assumed common EES" (i) option, no enhancement to step 2 is required. + +#### 7.27.2.7 Other procedural enhancements + +##### Enhancements to 3GPP TS 23.558[2] clause 8.9.1.1 EEC Context handling at EEC registration + +If the EEC registration request does not include a previously assigned EEC Context ID value, the receiver EES creates an EEC Context. The receiver EES assigns an EEC context ID and sets the source EES Endpoint to its own Endpoint. + +The EEC ID, UE Identifier and List of AC association profiles are set based on the corresponding registration request parameters. + +##### **Enhancements to 3GPP TS 23.558[2] clause 8.9.1.5 Other EEC Context handling** + +When the EES determines that a registered EAS is providing services to an AC which is part of an AC association Profile, the EES updates the corresponding Service Session context with the Association ID. Conversely, when the EES determines that a Service Session is no longer used within an AC association, the EES removes the Association ID from the corresponding Service Session context. + +In the option "with CAAR" (ii) the EES also updates the information about served AC Associations available at CAAR accordingly. During ACR, the S-EES removes its corresponding (association ID, EES ID) tuple from CAAR. The T-EES adds its corresponding (association ID, EES ID) tuple to CAAR. + +#### **7.27.2.8 New procedures** + +##### **7.27.2.8.1 New procedures for option ii** + +###### **7.27.2.8.1.1 General** + +The new procedures described in clauses 7.27.2.8.1.2 and 7.27.2.8.1.3 are necessary for option (ii) + +The CAAR function is that of maintaining information on AC Association serviced per EES and can also be integrated in ECS functionality. + +###### **7.27.2.8.1.2 EES Update of AC Associations with CAAR (option ii)** + +The EES procedure for updating AC Association information available at CAAR uses an update request in which the following information is provided to the CAAR: EES ID, list of association IDs of the associations being served, registrar ECS information including list of EDNs. This information is updated by EES when any of this information changes or is about to change (e.g. in advance of EES de-registration). + +###### **7.27.2.8.1.3 ECS Query of AC Associations with CAAR (option ii)** + +The ECS procedure for querying the AC Association information at CAAR uses the association IDs received (e.g. in a service provisioning request) and its own ECS information. The response provides a list of its registered EESs which serve the AC Association Profiles IDs being queried for. + +**NOTE:** Whether and how CAAR queries are used to direct EECs to a different ECS for the purpose of receiving services consistent with the AC Association is to be addressed in the context of enabling inter-ECSP deployments. + +### **7.27.3 Solution evaluation** + +This solution addresses Key Issue #17, discovery of a common EAS, while providing the following functionality addressing the first two open issues of KI #17: + +1. Introduces specific, clarifying, and consistent terminology for use in the common EAS scenario, e.g. "AC association", "pre-grouped" (AC Association), "dynamic grouping" (AC Association), etc. +2. Harmonizes support for usecases in which determining a common EES is not necessary (i.e. "assumed common EES" option) with support for usecases in which determining a common EES is necessary (i.e. option "with CAAR") as described in clause 7.27.0. +3. Provides support for various types of AC associations, i.e. "pre-grouped" and "dynamic grouping", as described in clause 7.27.2.2.1.2. as well as details on determining grouping (in clause 7.27.2.2.1.2) +4. Describes (in clause 7.27.2.8) new procedures for interaction with CAAR + +5. Specifies the impact of introducing this functionality on the following existing procedures: Service provisioning, EAS discovery and EEC context handling. + +The usage of common AC types and common AC schedule as the criteria for determining group of UEs should be validated further. + +The usage of UEs service area as the standalone criteria for determining group of UEs without any associated AC information should be validated further. + +Solution #27 provides the following functionality addressing the last open issue of KI #17: + +1. Description of ACR-related procedures. Specifically, impacts on all the following ACR-related procedures are detailed: Discover T-EAS, Retrieve T-EES, ACR launching, ACR status update. +2. Coordination of ACR operations is partly addressed in clause 7.27.2.6 by indicating the information which can be used to address this issue. The clause includes a NOTE clarifying that based on this information, the procedures for coordination of the ACRs for AC association members are to be addressed in the normative phase. + +This solution can impact Rel-17 architecture though through the introduction of CAAR as a new entity. + +To solve any potential issues resulting from the un-synchronized CAAR query and update leading to a race condition, an ACR procedure may be used to steer UEs to one common EAS. + +## 7.28 Solution #28: Common EAS discovery using EAS selection information + +### 7.28.1 Architecture enhancements + +None + +### 7.28.2 Solution description + +#### 7.28.2.1 General + +The following solution corresponds to the key issue #17 on Discovery of a common EAS. + +#### 7.28.2.2 Procedure + +This solution is based on the following principles: + +1. Each EAS instance can be identified uniquely across EDNs. +2. EAS Selection Information can be stored in the AC profile as the EAS selection information. +3. For service provisioning, the EEC can include EAS selection information in the AC profile to discover the EES / EDN where a common EAS is available +4. For EAS discovery, the EEC can include the EAS selection information in the AC profile to discover a common EAS. + +This solution assumes that an EAS can only register to a single EES within an EDN, as per Rel-17 version of TS 23.558 [2] clause 6.6.3.3 on reference point cardinality for EDGE-3. Therefore, it is assumed that all UEs discovering the common EAS must do so via the EES where the common EAS is registered. Additionally, requirements such as EEC registration must be followed by the UEs discovering a common EAS. + +This solution is compliant with ACID definition as per Rel-17 version of TS 23.558 [2] clause 7.2.5 and allows ACs with the same or different ACID (which belong to applications) to discover and use a common EAS. + +Figure 7.28.2.2-1 presents an overview of the procedures for discovery of a common EAS; the scenario represented involves a first UE (e.g. UE-1/AC-1/EEC-1) discovering and using an EAS and a second UE (e.g. UE-2/AC-2/EEC-2) discovering the same EAS used by the first UE-1. + +![Sequence diagram illustrating Common EAS discovery using EAS selection information. The diagram shows interactions between AC-1, EEC-1, ECS, EES, AC-2, and EEC-2. The steps are: 1. AC registration, service provisioning and EAS discovery; 2. EAS selection; 3. AC registration (incl EAS selection info.); 4. Service provisioning (incl EAS selection info.); 5. EAS discovery and EAS selection declaration (incl EAS selection info.).](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +``` + +sequenceDiagram + participant AC1 as AC-1 + participant EEC1 as EEC-1 + participant ECS as ECS + participant EES as EES + participant AC2 as AC-2 + participant EEC2 as EEC-2 + + Note over AC1, EEC1, ECS, EES: 1. AC registration, service provisioning and EAS discovery + Note over EEC1: 2. EAS selection + Note over AC2, EEC2: 3. AC registration (incl EAS selection info.) + Note over ECS, EES: 4. Service provisioning (incl EAS selection info.) + Note over AC2, EEC2, ECS, EES: 5. EAS discovery and EAS selection declaration (incl EAS selection info.) + +``` + +Sequence diagram illustrating Common EAS discovery using EAS selection information. The diagram shows interactions between AC-1, EEC-1, ECS, EES, AC-2, and EEC-2. The steps are: 1. AC registration, service provisioning and EAS discovery; 2. EAS selection; 3. AC registration (incl EAS selection info.); 4. Service provisioning (incl EAS selection info.); 5. EAS discovery and EAS selection declaration (incl EAS selection info.). + +**Figure 7.28.2.2-1: Common EAS discovery using EAS selection information** + +Pre-conditions: + +- The EAS has registered to the EES +1. The AC-1 registers to EEC-1, and according to Rel-17 procedures defined in TS 23.558, the EEC-1 performs service provisioning with the ECS and performs EAS discovery with the EES. Additionally, the EEC can perform EAS selection declaration if required. + 2. The EEC-1 selects one of the discovered EAS to be used as the common EAS. The EEC-1 uses the EAS Selection Information to form the EAS selection information which can be used to uniquely identify the common EAS within and across EDNs. The EEC-1 can provide the EAS selection information to AC-1. + 3. Not shown on figure 7.28.2.2-1, AC-2 residing on UE-2 can be provided with EAS selection information. How AC-2 obtains the EAS selection information is out of SA6 scope, for example it may be obtained via direct interaction between AC-1 and AC-2 or interaction between AC-2 and the service provider of the EAS. + +The AC-2 includes the EAS selection information in its AC profile and then registers with EEC-2, or alternatively updates its existing AC registration with EAS selection information. + +NOTE: If an EAS was discovered prior to receiving EAS selection information, the AC can update its AC profile to trigger step 4 and step 5 to discover the common EAS. + +4. The EEC-2 can perform a service provisioning procedure and includes the AC profile that contains the EAS selection information. The ECS considers the EAS selection information (e.g. the EESID) when selecting the EES and chooses the EES with a matching EESID. The service provisioning response includes the EDN configuration information that contains the EES where the common EAS is registered. Step 4 is optional if the EESID included in the EAS selection information is already known by EEC-2, in such case the EEC-2 can proceed to step 5. Not shown on the figure, the EEC may need to register to the EES if required by service provisioning. +5. The EEC-2 selects the EES according to the EAS selection information. If the EAS profile of the common EAS is not known at the EEC-2, the EEC-2 can perform the EAS discovery with the selected EES, and includes the AC profile in the EAS discovery request. The EEC-2 performs the EAS selection declaration with the EES; the EES considers if the EEC-2 can use the common EAS. The EAS selection declaration response received at the EEC-2 indicates success/failure; if successful, the AC-2 can access the same common EAS as AC-1. + +### 7.28.3 Solution evaluation + +The KI #17 has the following open issues: + +- 1) Whether and how the ACs/EECs of different users can select or be provisioned the same EAS within an EDN? + +NOTE: This open issue is dealing with the issue how different EECs can perform EAS discovery so that they select the same EAS within an EDN, whereas KI#13 is dealing with the issue how, after different EECs have selected different EASs located in different EDNs, these EASs can synchronize their contexts. + +- 2) Whether and how the ACs/EECs of different users can select or be provisioned a common EAS, even if initially the EECs are communicating with different EDNs? +- 3) Whether and how the EEL can support service continuity to ensure that when ACs require the use of service from a common EAS and an ACR operation is needed, ACR operations can be coordinated so that upon completion of the ACR operations the ACs again have services provided by a common EAS. + +Overall evaluation of Solution #28: + +- a) Enables an AC/EEC to select the same EAS as another EEC within an EDN by extending EAS discovery procedure with EAS selection information. +- b) Enables ACs/EECs of different users to select or be provisioned a common EAS, even if initially the EECs are communicating with different EDNs, by firstly extending service provisioning procedure with EAS selection information, and secondly performing the EAS discovery procedure within that common EDN. +- c) Maintains compatibility with ACR operations by extending pre-existing service provisioning and EAS discovery procedures which are used by ACR procedures. + +Editor's note: It is FFS whether this solution requires detailed procedure updates to show the common EAS selection information. + +Editor's note: This solution requires detailed procedure updates as per bullets a), b) and c) and it is FFS to show the enhancements to existing procedures. + +Editor's note: In the race condition situation (multiple UEs selects different EASs during step 2), how to coordinate common EAS selection is FFS. + +## 7.29 Solution #29: Discovery of a common EAS + +### 7.29.1 Architecture enhancements + +None. + +### 7.29.2 Solution description + +#### 7.29.2.1 General + +The following solution addresses open issues 1 and 2 of key issue #17, discovery of a common EAS. + +**Editor's note:** The solution for open issue 3, support of service continuity, is FFS. + +**NOTE:** The communication between AC and AS and between ACs is out of scope of SA6. In the following, some of this communication is only described to enable a better understanding of how the procedures under SA6 responsibility may be embedded in the overall procedure. The description is not intended to exclude scenarios using a different application level communication. + +It is assumed that when users want to participate in a real-time multi-user session, their ACs will register with an application server (AS) in the cloud. The AS configures the ACs to form an AC group to which the AS assigns a globally unique Group ID (e.g. a UUID as described in RFC 4122). + +During the registration with the AS, users will provide their UE location information to the AS. Dependent on the use case, the location information can be given, e.g. in the format of GPS coordinates, a Cell Identity or a Tracking Area Identity. Furthermore, dependent on the application, during the registration the users may be asked to consent to exchanging the location of their UEs with each other. If users consent, then the UE location information is exchanged between the ACs via application level signalling via the AS in the cloud. + +Based on the UE location information received from the ACs, the AS determines the Expected group geographical service area. Dependent on the use case this can be a single coordinate, e.g. the center of mass of the UE/AC locations or the location of a UE/AC taking a specific role in the group (e.g. in a V2X scenario the first truck in platoon), or it can be a geographical area including the current UE/AC locations (without disclosing individual UE/AC locations). The AS provides Group ID, Expected group geographical service area and, if applicable, the locations of the other ACs to each of the ACs. + +Dependent on the application, the distribution of the Group ID and the other parameters by the AS can be triggered by different events, e.g. upon explicit request of a user or when a certain minimum number of users have registered. + +Upon receipt of the Group ID, together with the other parameters, each AC requests its EEC to perform EAS discovery. + +During service provisioning, the Requested EES geographical service area is received by the ECS and used by it to determine a common EES, by comparing it with the EES geographical service area received from each EES during EES registration. + +##### **EAS discovery based on individual UE locations** + +Later, during EAS discovery, the EEC-1 of user 1 provides the common EES with its own location and with the locations of the other UEs/EECs. Based on the location information of all EECs involved in the session and possibly other information included in the EAS discovery request, e.g. Group ID, the EES determines a common EAS and indicates it to the EEC-1. + +When EEC-2 of user 2 provides the EES with the same set of location information for all the EECs, then the EES will determine the same EAS again. + +##### **EAS discovery based on other information** + +If users do not consent to share their individual UE location information with other users, then only the Expected group geographical service area is distributed by the AS to the ACs via application level signalling. Additionally, the AS may send a "group size for EAS discovery" parameter to each AC. + +Later, during EAS discovery, each EEC provides the common EES with its own location and optionally, in the Group profile IE, the Expected Group geographical service area or the "group size for EAS discovery" parameter or both. + +The EES may initiate determination of a common EAS for the EECs based on different criteria, dependent the received parameters and the application, e.g.: + +- immediately upon receipt of the first EAS discovery request, based on the Expected Group geographical service area, if available; +- when the number of EAS discovery request is greater or equal to the "group size for EAS discovery" parameter; or +- a certain time after receipt of the first EAS discovery request, + +taking into account the UE location information received from the EECs by this point in time and possibly other information included in the EAS discovery request, e.g. Group ID. + +##### **Handling of "late-coming" ACs** + +If a late-coming AC wants to join the multi-user group session after the initial EAS discovery was initiated, it may register with the AS. After registration it will receive from another AC in application layer signalling, e.g. via the AS, the EDN configuration information necessary to connect to the common EES. The details of this signalling are out-of-scope of SA6. The AC can then register with the EES and perform EAS discovery, providing its Group ID. The EES determines the EAS based on the Group ID. + +#### **7.29.2.2 Procedure** + +The following procedure demonstrates the signalling for 2 UEs only, but the same principles can be applied to a larger number of UEs. + +Pre-conditions: + +1. ACs have registered with an AS in the cloud to participate in a real-time multi-user session. During the registration, the AS provided the ACs with the Group ID and the Expected group geographical service area (which may be a single coordinate or an area including the UE locations, see clause 7.29.2.1). Dependent on user consent, the AS also forwards the location information of the other UE(s) to each of the ACs. If user consent is not available, the AS may send a "group size for EAS discovery" parameter to the ACs. + + + +![Sequence diagram illustrating the discovery of a common EAS. The diagram shows interactions between two User Equipment (UE) groups (AC-1, UE 1, EEC-1 and AC-2, UE 2, EEC-2), an ECS, an EES, and an EAS-1(A). The sequence starts with AC-1 and AC-2 registering with their respective EECs. Then, both EECs send Service Provisioning Requests to the ECS. The ECS responds with EDN configuration info. Next, both EECs send EAS Discovery Requests to the EES. The EES responds with EAS-1(A) information to both EECs.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant AC1 as AC-1 + participant UE1 as UE 1 + participant EEC1 as EEC-1 + participant AC2 as AC-2 + participant UE2 as UE 2 + participant EEC2 as EEC-2 + participant ECS + participant EES + participant EAS1A as EAS-1(A) + + Note left of AC1: AC-1, UE 1, EEC-1 + Note left of AC2: AC-2, UE 2, EEC-2 + + AC1->>EEC1: 1. AC Registration + AC2->>EEC2: 2. AC Registration + EEC1->>ECS: 3. Service Provisioning Request (Group profile IE) + EEC2->>ECS: 4. Service Provisioning Request (Group profile IE) + ECS->>EEC1: 5. Service Provisioning Response (EDN configuration info) + ECS->>EEC2: 6. Service Provisioning Response (EDN configuration info) + EEC1->>EES: 7. EAS Discovery Request (Group profile IE) + EEC2->>EES: 8. EAS Discovery Request (Group profile IE) + EES->>EEC1: 9. EAS Discovery Response (EAS-1(A)) + EES->>EEC2: 10. EAS Discovery Response (EAS-1(A)) + +``` + +Sequence diagram illustrating the discovery of a common EAS. The diagram shows interactions between two User Equipment (UE) groups (AC-1, UE 1, EEC-1 and AC-2, UE 2, EEC-2), an ECS, an EES, and an EAS-1(A). The sequence starts with AC-1 and AC-2 registering with their respective EECs. Then, both EECs send Service Provisioning Requests to the ECS. The ECS responds with EDN configuration info. Next, both EECs send EAS Discovery Requests to the EES. The EES responds with EAS-1(A) information to both EECs. + +**Figure 7.29.2.2-1: Discovery of a common EAS** + +1.-2. Each AC requests its EEC to perform EAS discovery. The request includes the AC profile, the Group profile IE, including optionally, the Expected group geographical service area, or the location information of the other UEs involved in the multi-user session in the request. + +3.-4. EEC1 and EEC2 initiate service provisioning, including the AC profile, the Group profile IE including the Expected group geographical service area. + +5.-6. Based on the AC profile, Group profile including the Expected group geographical service area and the other information provided by the EEC, the ECS determines a suitable common EES and includes it in the service provisioning response. If more than one suitable EES is available, the ECS can use additional information as input parameter to determine a unique EES. + +NOTE 1: For example, the ECSs can use the Group ID and an algorithm shared between the ECSs to derive the common EES from the list of available EESs. + +If the ECS wants to provision the EECs with additional EESs, e.g. for service continuity, then the common EES is included as first EES in the first entry of the list of EDN configuration information. + +7.-8. EEC1 and EEC2 initiate EAS discovery towards the common EES, including the AC profile, the Group profile IE which optionally includes the Expected group geographical service area or the location information of all UEs involved in the multi-user session. + +9.-10. The EES initiates determination of a common EAS for the EECs based on different criteria, dependent the received parameters and the application, e.g.: + +i) immediately upon receipt of the first EAS discovery request, based on the Expected Group geographical service area or the location information of all UEs involved in the multi-user session, if received; + +ii) when the number of EAS discovery request is greater or equal to the "group size for EAS discovery" parameter; or + +iii) a pre-defined time after receipt of the first EAS discovery request, + +taking into account the Expected Group geographical service area or the UE location information received by this point in time and possibly other information included in the EAS discovery request, e.g. Group ID. + +NOTE 2: The EES can also utilize the capabilities of the 3GPP core network to determine a UE location. + +The EES includes the determined common EAS, e.g. EAS-1(A), in the EAS discovery response. + +#### 7.29.2.3 Enhanced Service provisioning request + +The following enhancement (highlighted with bold text) to the Service provisioning request in 3GPP TS 23.558 [2] is proposed: + +**Table 7.29.2.3-1 (TS 23.558: Table 8.3.3.3.2-1): Service provisioning request** + +| Information element | Status | Description | +|--------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------| +| EECID | M | Unique identifier of the EEC. | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| AC Profile(s) | O | Information about services the EEC wants to connect to, as described in Table 8.2.2-1. | +| EEC Service Continuity Support | O | Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC. | +| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) | +| Connectivity information | O | List of connectivity information for the UE, e.g. PLMN ID, SSID. | +| UE location | O | The location information of the UE. The UE location is described in clause 7.3.2. | +| AC Group profile(s) | O | List of AC group profiles of the multi-user session that an AC wants to join. | + +#### 7.29.2.4 Enhanced EAS discovery filters + +The following enhancement (highlighted with bold text) to the EAS discovery filters in 3GPP TS 23.558 [2] is proposed: + +**Table 7.29.2.4-1 (TS 23.558: Table 8.5.3.2-2): EAS discovery filters** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------------| +| List of AC characteristics (NOTE 1) | O | Describes the ACs for which a matching EAS is needed. | +| > AC profile (NOTE 2) | M | AC profile containing parameters used to determine matching EAS. AC profiles are further described in Table 8.2.2-1. | +| > AC Group profile | O | AC group profile of the multi-user session that the AC wants to join. | +| List of EAS characteristics (NOTE 1, NOTE 3) | O | Describes the characteristic of required EASs. | +| > EASID | O | Identifier of the required EAS. | +| > EAS provider identifier | O | Identifier of the required EAS provider | +| > EAS type | O | The category or type of required EAS (e.g. V2X) | +| > EAS schedule | O | Required availability schedule of the EAS (e.g. time windows) | +| > EAS Geographical Service Area | O | Location(s) (e.g. geographical area, route) where the EAS service should be available. | +| > EAS Topological Service Area | O | Topological area (e.g. cell ID, TAI) for which the EAS service should be available. See possible formats in Table 8.2.7-1. | +| > Service continuity support | O | Indicates if the service continuity support is required or not. | +| > Service permission level | O | Required level of service permissions e.g. trial, gold-class | +| > Service feature(s) | O | Required service features e.g. single vs. multi-player gaming service | +| NOTE 1: Either "List of AC characteristics" or "List of EAS characteristics" shall be present.
NOTE 2: "Preferred ECSP list" IE shall not be present.
NOTE 3: The "List of EAS characteristics" IE must include at least one optional IE, if used as an EAS discovery filter. | | | + +#### 7.29.2.5 New Group profile common information element + +The following new common EAS AC Group profile information element is proposed to 3GPP TS 23.558 [2]: + +**Table 7.29.2.5-1: AC Group profile IE** + +| | | | +|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Group ID | M | Identity of the group of ACs. | +| ACID | M | Identity of the AC that wants to join the multi-user session. | +| List of EASs | O | List of EAS that serve the AC group along with the service KPIs required by the AC group. | +| > EASID | M | Identifier of the EAS | +| > Expected AC Service KPIs | O | KPIs expected in order for the ACs in the AC group to receive currently required services from the EAS, as described in Table 8.2.3-1. | +| > Minimum required AC Service KPIs | O | Minimum KPIs required in order for ACs in the AC group to receive meaningful services from the EAS, as described in Table 8.2.3-1 | +| Expected Group Geographical Service Area (NOTE) | O | Dependent on the application, this IE can indicate, e.g. a small circle around the centre of mass of the UE/AC locations or around the location of a specific UE/AC for which certain service KPIs are to be optimised, or an area including the own UE location and the locations of one or more other UEs that want to join the multi-user session. | +| Other UE locations (NOTE) | O | The location information of other UEs involved in a multi-user session. The UE location is described in TS 23.558, clause 7.3.2. | +| NOTE: | Only one of the parameters "Expected Group Geographical Service Area" and "Other UE locations" may be included. "Other UE locations" shall only be included if users have consented to share their individual UE location information with other users at the application level. | | + +#### 7.29.2.6 Enhanced EDN configuration information + +The following enhancement (highlighted with bold text) to the EDN configuration information in 3GPP TS 23.558 [2] is proposed: + +**Table 7.29.2.6-1 (TS 23.558: Table 8.3.3.3.3-2): EDN configuration information** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EDN connection information (NOTE 1) | M | Information required by the UE to establish connection with the EDN. | +| > DNN/APN | M | Data Network Name/Access Point Name | +| > S-NSSAI | O | Network Slice information | +| > EDN Topological Service Area | O | The EDN serves UEs that are connected to the Core Network from one of the cells included in this service area. See possible formats in Table 8.2.7-1. | +| List of EESs | M | List of EESs of the EDN. | +| > EESID | M | The identifier of the EES | +| > EES Endpoint | M | The endpoint address (e.g. URI, IP address) of the EES | +| > EASIDs (NOTE 2) | O | List of EASIDs registered with the EES. | +| > EES Provider identifier | O | The identifier of the EES Provider (such as ECSP) | +| > EES Topological Service Area | O | The EES serves UEs that are connected to the Core Network from one of the cells included in this service area. EECs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. | +| > EES Geographical Service Area | O | The area being served by the EES in Geographical values (as specified in clause 7.3.3.3) | +| > List of EES DNAI(s) | O | DNAI(s) associated with the EES/EAS. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [2]. | +| > EES Service continuity support | O | Indicates if the EES supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EES. | +| > EEC registration configuration | M | Indicates whether the EEC is required to register on the EES to use edge services or not. | +| > Security Credential | O | Indicates the security credential sent by the ECS. The security credential is used by EEC to communicate with the EES as specified in 3GPP TS 33.558 [23], clause 6.2. | +| Lifetime | O | Time duration for which the EDN configuration information is valid and supposed to be cached in the EEC. | +| NOTE 1: If the UE is provisioned or pre-configured with URSP rules by the HPLMN, the UE handles the precedence between EDN connection info and URSP rules as defined in 3GPP TS 23.503 [12] clause 6.1.2.2.1. EDN connection info is considered to be part of UE Local Configurations. | | | +| NOTE 2: EAS information is limited to the EEC requested applications. If no AC profiles or AC Group profiles were present in the service provisioning request, the EAS information is subject to the ECSP policy (e.g. no EAS information or a subset of EAS information related to the EES). | | | + +### 7.29.3 Solution evaluation + +The proposed solution addresses Key Issue #17, discovery of a common EAS. It introduces a new AC Group profile IE, with group specific attributes that provide information that can enable the Edge Enabler Layer to select an appropriate common EES (as part of service provisioning) and then common EAS (as part of EAS discovery) based on the application layer requirements. + +The dynamic information contained in the AC Group profile IE would be made available at runtime through an AC's interaction with the AS to which it is registered. The information provided by the AS may include either an expected group geographical service area or location information of other UEs involved in the multi-user session. It is assumed that if this geographical information (i.e. expected group geographical service area or location information of other UEs) is provided by the AC(s)/EEC(s) to the EEL during service provisioning and EAS discovery, and more than one EAS is available to provide the same service in different locations, the geographical information can assist the ECS with determining the common EES and the EES with determining the common EAS most suitable to meet the latency requirements of the multi-user session. + +Location information of other UEs involved in the multi-user session will not be provided to each AC by the AS unless the users involved in the multi-user session have consented to sharing of their individual UE location information. The application layer mechanism for a user to share consent with the AS is outside the scope of SA6. + +This solution does not introduce impact on Rel-17 architecture. + +## 7.30 Solution #30: Common EAS selection + +### 7.30.1 Architecture enhancements + +Architecture enhancements in clause 6.7 is the basis for this solution. + +### 7.30.2 Solution description + +This solution addresses KI#17. + +The UEs can be grouped together to consume EAS services on the same EAS endpoint. + +The group information (e.g. group id) can be used as part of the binding information to support anchor those UEs to the same EAS. The binding information are maintained on a Binding Server (BS). When an EES is aware of the selected EAS (e.g. via EEC sent EAS selection declaration), the BS is contacted by the EES and the BS can decide whether to proceed the currently selected EAS or instruct to use another EAS (which already has other established session(s) for the group). + +The EDN id is used to identify EDN and is also part of the binding information. Figure 7.30.2-1 show the detailed procedure with a Central Binding Server (CBS) for common EAS pre-selection in EES. + +In the following figures, ACs with same AC ID on different UEs is shown as example, it is also possible that ACs with different AC IDs supplied by the same AC provider (e.g. AC developed for iphone and AC developed for Android phone) need to communicate with each other via EAS. It is assumed that the CBS can be accessed by all EESs deployed in different EDNs. + +Pre-conditions: + +1. The EEC is aware of the group info from AC via EDGE-5 reference point. + +![Sequence diagram titled 'Figure 7.30.2-1: select a common EAS for UEs, common EAS pre-selection in EES'. The diagram shows the interaction between AC 1 (UE1), EEC 1 (UE1), EES 1, CBS, AC 1 (UE2), EEC 2 (UE2), EES 2, and CBS. The process involves EES 1 pre-selecting an EAS and then EES 2 finding an existing binding for the group, recommending the common EAS (EES 1's selection) to EEC 2.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant AC1_UE1 as AC 1 (UE1) + participant EEC1_UE1 as EEC 1 (UE1) + participant EES1 as EES 1 + participant CBS + participant AC1_UE2 as AC 1 (UE2) + participant EEC2_UE2 as EEC 2 (UE2) + participant EES2 as EES 2 + + Note left of AC1_UE1: EDN1 + + EEC1_UE1->>EES1: 1. EAS discovery request (UE1, AC1, group info) + EES1->>CBS: 2. group binding request (UE1, AC1, group info, EES1, EAS ID, EAS endpoint, EDN1) + CBS-->>EES1: 3. No existing binding found; create new binding + CBS-->>EES1: 4. group binding response + EES1-->>EEC1_UE1: 5. EAS discovery response + EEC1_UE1->>AC1_UE1: 6. Selected EAS + Note right of AC1_UE1: 7. AC connects to EAS + + EEC2_UE2->>EES2: 8. EAS discovery request (UE2, AC1, group info) + EES2->>CBS: 9. group binding request (UE2, AC1, group info, EES2, EAS ID, EAS endpoint, EDN1) + CBS-->>EES2: 10. existing binding found for the group + CBS-->>EES2: 11. group binding response (recommend to use a common EAS) + EES2-->>EEC2_UE2: 12. EAS discovery response + EEC2_UE2->>AC1_UE2: 13. Selected EAS + Note right of AC1_UE2: 14. AC connects to EAS + +``` + +Sequence diagram titled 'Figure 7.30.2-1: select a common EAS for UEs, common EAS pre-selection in EES'. The diagram shows the interaction between AC 1 (UE1), EEC 1 (UE1), EES 1, CBS, AC 1 (UE2), EEC 2 (UE2), EES 2, and CBS. The process involves EES 1 pre-selecting an EAS and then EES 2 finding an existing binding for the group, recommending the common EAS (EES 1's selection) to EEC 2. + +**Figure 7.30.2-1: select a common EAS for UEs, common EAS pre-selection in EES** + +In EDN1: + +1. During EAS discovery, EEC 1 sends EAS discovery request to EES 1 including EAS ID, UE ID (of UE1), AC ID (of AC1) and group info (e.g. group id x). +2. The EES 1 pre-selects an EAS and sends group binding request message to CBS with the received information from EEC 1 and in addition the EDN id (of EDN 1). +3. There is no existing binding information found so that the CBS creates a new binding information for the UE group. +4. The CBS responds group binding request with a result indicating OK to proceed with the requested EAS. +- 5-7. With the received EAS information, the EES 1 responds the EAS discovery request with the selected EAS to the EEC 1 and consequently AC1 connects to the selected EAS after being informed by EEC 1. + +In the same EDN (i.e. EDN1): + +8. During EAS discovery, EEC 2 sends EAS discovery request to EES 2 with the selected EAS information including EAS ID, UE ID (of UE2), AC ID (of AC1) and group info (e.g. group id x). +9. The EES 2 pre-selects an EAS and sends group binding request message to CBS with the received information from EEC 2 and in addition the EDN id (of EDN 1). +10. The CBS finds existing binding information for the UE group based on group info. +11. The CBS responds with a result indicating recommendation to use common EAS (including the associated EES info) which is EES 1 selected EAS. +- 12-14. With the received EAS information, the EES 2 responds the EAS selection to the EEC 2 and consequently AC1 connects to the common EAS. EEC 2 may contact EES 1 for subsequent procedures (e.g. EEC registration, ACR subscription). + +NOTE: It is assumed that within an EDN (with proper dimensioning for the service area), the EAS service experience is almost the same for all ACs distributed in the EDN. For instance, the EAS can measure the RTT for connected AC with consideration of the user plane routing optimization in CN and DN so that the EAS can estimate its service area during deployment stage to ensure relative fairness for all ACs distributed in the EDN (e.g. > 95% ACs having RTT < 200ms). + +The binding update may be done for a common EAS when: + +- 1) EAS service continuity (e.g. a new common EAS is selected by the current EAS due to load re-balancing reason in the same EDN) happens. In this case, the EES receives the T-EAS discovery from EEC or S-EAS or triggers T-EAS discovery by itself, then the EES pre-selects T-EAS and update the binding information in the CBS. +- 2) AC in a group terminates the application session. In this case, the EES is informed by EAS/EEC about the session termination and updates the binding information in the CBS for the terminated AC. The group binding for the common EAS still remains the same. + +The binding information in the CBS is created upon the 1st AC's need to discover an EAS, therefore, when the last AC in a group terminates the application session, the binding information for the group is removed in the CBS. + +For group-based session termination (e.g. EAS decides to terminate session for all ACs in a group), the common EAS may trigger its EES to remove the binding information for the group in the CBS. + +For common EAS pre-selection in the UE, the procedure is similar as Figure 7.30.2-1 with the difference that the (T-EAS pre-selection is done by the EEC. + +### 7.30.3 Solution evaluation + +This is a viable solution addressing the KI#17. This solution proposes a new entity CBS to maintain the selected common EAS which is determined by the 1st UE's activity in a group in an EDN and has impact to the (T-)EAS discovery procedure. Both initial EAS discovery and subsequent T-EAS discovery in ACR are covered by this solution. + +This solution relies on group information (e.g. group id) conveyed from the AC to the EEC. As a pre-condition, the group is formed before EEC triggers EAS discovery. A pre-configured group can take advantage of this solution to enable common EAS selection. For dynamic group, it can also use this solution to select a common EAS in an EDN. + +For fairness of all involved ACs in a group to communicate with common EAS, this solution has assumption that the service area is properly dimensioned during EAS deployment so the EAS can ensure good and fair service experience for the ACs within its service area. + +NOTE: This solution does not address how to enable data synchronization among common EASs, which is within the scope of KI#13. + +## 7.31 Solution #31: Discover common EAS + +### 7.31.1 Architecture enhancements + +None. + +### 7.31.2 Solution description + +#### 7.31.2.1 General + +The following solution addresses open issues of key issue #17 (Discovery of a common EAS) and key issue #13 (Edge enabler layer support for EAS synchronization). + +As specified in TS 23.558 (Rel-17), the EEC of one user may select EAS which is different from the EAS selected by another user although both users are part of the same communication session. If different EASs are selected for the users of the same communication session, then different EASs need to synchronize with each other in order to maintain the communication session. + +For certain use cases involving real-time communication in a multi-user session, both between AC and EAS and between different ACs via the EAS, it may be necessary or beneficial to use services from a single common EAS to meet the strict latency requirements and to avoid the need for inter-EAS synchronization. + +Dependent on the use case, the EEL may apply different additional criteria to determine this common EAS. E.g. it could be desirable to determine the EAS so that the latency for all the ACs in the session is approximately the same or that the latency for a specific AC is minimized. + +#### 7.31.2.2 Procedure for EEC(s) connected to different EES(s) + +The following procedure demonstrates the Discovery of a common EAS. + +The procedure supports selection of a common EAS: + +- for the same ACID on UEs of different Users (aware or unaware of each other), within the same EDN +- for group of ACIDs on UEs of same User within the same EDN +- per group within the same EDN and for the same ACID(s) +- for new UEs requesting to join after a common EAS is already selected. + +Pre-conditions: + +1. AC Profile is enhanced with Grouping required information that tells whether the AC requires a multi-user session or multi-AC session etc. +2. EAS registers to EES according to clause 8.4.3 EAS Registration in TS 23.558. +3. EEC-1 is registered to EES-1 and EEC-2 is registered to EES-n. +4. EEC-1 may receive list of EESes from ECS relevant to the group-ID. + +![Sequence diagram illustrating Common EAS discovery where EEC(s) are connected to different EES(s). The diagram shows interactions between EEC-1, EES-1, EES-n, and EEC-2. EEC-1 initiates discovery, receives a response from EES-1, and determines an EAS. It then announces this to EES-1. EES-1 determines other EESes to inform and announces the common EAS to EES-n. EES-n performs steps similar to EEC-1's discovery with EEC-2, checks if the common EAS is available, and responds to EES-1.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant EEC-1 + participant EES-1 + participant EES-n + participant EEC-2 + + Note left of EEC-1: 1. Trigger for EAS discovery + EEC-1->>EES-1: 2. EAS discovery request (Grouping required) + EES-1-->>EEC-1: 3. EAS discovery response + Note left of EEC-1: 4. Determine EAS to be used + EEC-1->>EES-1: 5. Selected EAS announcement request + EES-1-->>EEC-1: 6. Selected EAS announcement response + Note right of EES-1: 7. Determine other EESes to be informed about common EAS + EES-1->>EES-n: 8. Announce common EAS request + EES-n-->>EES-1: 9. Announce common EAS response + Note right of EES-n: 10. Same as Step 2, between EEC-2 and EES-n + Note right of EES-n: 11. Check if common EAS is already available + Note right of EES-n: 12. Same as Step 3, between EEC-2 and EES-n + +``` + +Sequence diagram illustrating Common EAS discovery where EEC(s) are connected to different EES(s). The diagram shows interactions between EEC-1, EES-1, EES-n, and EEC-2. EEC-1 initiates discovery, receives a response from EES-1, and determines an EAS. It then announces this to EES-1. EES-1 determines other EESes to inform and announces the common EAS to EES-n. EES-n performs steps similar to EEC-1's discovery with EEC-2, checks if the common EAS is available, and responds to EES-1. + +**Figure 7.31.2.2-1: Common EAS discovery - EEC(s) connected to different EES(s)** + +1. EEC-1 received a trigger to initiate EAS discovery. +2. EEC-1 performs the EAS discovery, as described in TS 23.558 V17.3.0, where an enhanced AC profile including Grouping required information is included in the request towards EES-1. Grouping required can be for a multi-user session or multi-AC session or a combination of both. Group ID IE (which indicates the ID for grouping of Users of same AC or grouping of ACs.) is present only when the expectation is to enable multiple groups while the UEs are connected to EDN for the same EASID. +3. EES-1 considers Grouping required information as one of the discovery filters to decide the list of EASes to return in the response to EEC-1's EAS discovery request. The EES-1 checks if there is already a selected EAS + +corresponding to the received Grouping required information from EEC-1. If it exists then the EES-1 returns the selected EAS. Otherwise, the EES-1 determines the list of EAS as specified in TS 23.558 (Rel-17). + +4. When multiple EASs are discovered for a specific AC, the EEC-1 may select one or more EASs to enable AC communication with one of the selected EASs i.e. the EEC-1 (or AC and EEC-1) selects the initial EAS from the discovered EAS candidates, considering the Grouping required information. + 5. EEC-1 sends a Selected EAS announcement request with AC ID, EASID, EAS endpoint, and UE ID to the selected EES-1 (which is determined based on the selected EAS). The request shall include Group ID IE if this information is present in Step-2. EES-1 can decide whether to proceed with the currently selected EAS or instruct to use another EAS (which already has other established session(s) for the group). The mapping of selected common EAS with grouping required information and Group ID (if present) is stored at EES-1. If EEC knows the list of EESes, then the request message may contain all the EESs information for the group ID received from the ECS. + 6. EEC-1 is then responded to by the selected EES-1 with the success/failure of the request. If EES-1 decides to use another EAS in Step-5, then the response includes information about the new EAS back to EEC-1. + 7. If EES-1 has not received the list of other EESes information from EEC-1, EES-1 determines which other EESes to be informed about the selected EAS e.g. serving the same AC within the EDN as per the procedure in clause 8.8.3.3 of TS 23.558 for the EES-1 to retrieve the EES-n information from the ECS. + - 7.1 Selected EES-1 contacts ECS along with EASID information of the Selected EAS to determine which other EES(s) serve the same EASID. Otherwise, EES-1 uses the list of other EESes as received in Step-5 above. + - 7.2 ECS provides endpoint information of other EES(s) as described in table 8.3.3.3.3-2, corresponding to the requested EASID information. + 8. Selected EES-1 then declares common EAS selection to all the determined EESes (EES-n) along with the Grouping required information and Group ID (if present). + 9. EES-n stores the received common EAS information along with the Grouping required information and Group ID (if present) and sends back an acknowledgement to EES-1. + 10. Upon receiving a trigger, similar to step-2, EEC-2 performs the EAS discovery, as described in TS 23.558 V17.3.0, where an enhanced AC profile including Grouping required information and optionally Group ID is included in the request towards EES-n. +- NOTE: Race conditions e.g. EAS discovery before announcement in Step 8, can occur in this solution. +11. EES-n checks if there is already a selected EAS corresponding to the received Grouping required information from EEC-2. + 12. If a common EAS is available, EES-n then informs the selected EAS to the EEC-2. When Group ID is present in Step-10, EES-n checks if common EAS is selected corresponding to the Group ID and inform the selected common EAS to the EEC-2. Otherwise, Step 3 to Step 9 are performed to select and announce a common EAS. + +The EDN configuration information received from ECS may then be used by EEC-1 and EEC-2 for establishing a connection to the common EAS. + +#### 7.31.2.3 Procedure for EEC(s) connected to same EES + +The following procedure demonstrates the Discovery of a common EAS when EEC(s) are connected to same EES. + +The procedure supports selection of a common EAS: + +- for the same ACID on UEs of different Users (aware or unaware of each other), within the same EDN +- for group of ACIDs on UEs of same User within the same EDN +- per group within the same EDN and for the same ACID(s) +- for new UEs requesting to join after a common EAS is already selected. + +Pre-conditions: + +1. AC Profile is enhanced with Grouping required information that tells whether the AC requires a multi-user session or multi-AC session etc. +2. EAS registers to EES according to clause 8.4.3 EAS Registration in TS 23.558. +3. EEC-1 and EEC-3 are registered to EES-1. + +![Sequence diagram for Common EAS discovery - EEC(s) connected to same EES. Lifelines: EEC-1, EES-1, EEC-3. Steps: 1. Trigger for EAS discovery (EEC-1); 2. EAS discovery request (Grouping required) (EEC-1 to EES-1); 3. EAS discovery response (EES-1 to EEC-1); 4. Determine EAS to be used (EEC-1); 5. Selected EAS announcement request (EEC-1 to EES-1); 6. Selected EAS announcement response (EES-1 to EEC-1); 7. Same as Step 2, between EEC-3 and EES-1; 8. Check if common EAS is already available (EES-1); 9. Same as Step 3, between EEC-3 and EES-1 including Common EAS.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` +sequenceDiagram + participant EEC-1 + participant EES-1 + participant EEC-3 + Note left of EEC-1: 1. Trigger for EAS discovery + EEC-1->>EES-1: 2. EAS discovery request (Grouping required) + EES-1-->>EEC-1: 3. EAS discovery response + Note left of EEC-1: 4. Determine EAS to be used + EEC-1->>EES-1: 5. Selected EAS announcement request + EES-1-->>EEC-1: 6. Selected EAS announcement response + Note right of EES-1: 7. Same as Step 2, between EEC-3 and EES-1 + Note right of EES-1: 8. Check if common EAS is already available + Note right of EES-1: 9. Same as Step 3, between EEC-3 and EES-1 including Common EAS +``` + +Sequence diagram for Common EAS discovery - EEC(s) connected to same EES. Lifelines: EEC-1, EES-1, EEC-3. Steps: 1. Trigger for EAS discovery (EEC-1); 2. EAS discovery request (Grouping required) (EEC-1 to EES-1); 3. EAS discovery response (EES-1 to EEC-1); 4. Determine EAS to be used (EEC-1); 5. Selected EAS announcement request (EEC-1 to EES-1); 6. Selected EAS announcement response (EES-1 to EEC-1); 7. Same as Step 2, between EEC-3 and EES-1; 8. Check if common EAS is already available (EES-1); 9. Same as Step 3, between EEC-3 and EES-1 including Common EAS. + +**Figure 7.31.2.3-1: Common EAS discovery - EEC(s) connected to same EES** + +Steps 1 to 6. Same as steps 1 to 6 of clause 7.31.2.2. + +7. Upon receiving a trigger, EEC-3 performs the EAS discovery, same as in step 2 of clause 7.31.2.2. + +8. EES-1 checks the stored information if a common EAS is available corresponding to the received enhanced AC profile. + +9. If stored information exists then the EES-1 returns the common selected EAS. Otherwise, the EES-n determines the list of EAS as specified in TS 23.558 (Rel-17). + +The EDN configuration information received from ECS may then be used by EEC-1 and EEC-3 for establishing a connection to the common EAS. + +#### 7.31.2.4 Procedure for Edge enabler layer support for common EAS announcement + +The following solution corresponds to the key issue #13 Edge enabler layer support for EAS synchronization. If users are connected to multiple EESs with non-overlapping service area, then how to enable EAS to find other EAS(s) with multi-user communication session to synchronize. The procedure demonstrates the edge enabler layer support for the announcement of a selected EAS between EES(s) for enabling EAS synchronization. + +Pre-conditions: + +1. AC Profile is enhanced with Grouping required information that tells whether the AC requires a multi-user session or multi-AC session etc. +2. EAS registers to EES according to clause 8.4.3 EAS Registration in TS 23.558. +3. EEC-1 is registered to EES-1 and EEC-2 is registered to EES-n. + +![Sequence diagram illustrating the Edge enabler layer support for common EAS announcement. The diagram shows two pairs of entities: EEC-1 and EES-1 on the left, and EES-n and EEC-2 on the right. The process starts with both pairs performing '1. Discover common EAS'. Then, EES-1 performs '2. Determine other EESs to be informed about common EAS'. Next, EES-1 sends a '3. Announce common EAS request' to EES-n. Finally, EES-n sends a '4. Announce common EAS response' back to EES-1.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) + +``` + +sequenceDiagram + participant EEC-1 + participant EES-1 + participant EES-n + participant EEC-2 + + Note left of EES-1: 1. Discover common EAS + Note right of EES-n: 1. Discover common EAS + Note right of EES-1: 2. Determine other EESs to be informed about common EAS + EES-1->>EES-n: 3. Announce common EAS request + EES-n-->>EES-1: 4. Announce common EAS response + +``` + +Sequence diagram illustrating the Edge enabler layer support for common EAS announcement. The diagram shows two pairs of entities: EEC-1 and EES-1 on the left, and EES-n and EEC-2 on the right. The process starts with both pairs performing '1. Discover common EAS'. Then, EES-1 performs '2. Determine other EESs to be informed about common EAS'. Next, EES-1 sends a '3. Announce common EAS request' to EES-n. Finally, EES-n sends a '4. Announce common EAS response' back to EES-1. + +**Figure 7.31.2.4-1: Edge enabler layer support for common EAS announcement** + +1. EEC and EES performs the common EAS discovery procedure as described in steps 1 to 6 of clause 7.31.2.3. +2. EES determines which other EESs to be informed about the selected common EAS e.g. serving the same EASID within the EDN as per the procedure in clause 8.8.3.3 of TS 23.558 for the EES to retrieve the other EES information from the ECS. + - 2.1 EES contacts ECS along with EASID information of the selected common EAS to determine which other EES(s) serve the same EASID. + - 2.2 ECS provides endpoint information of other EES(s) as described in table 8.3.3.3-2, corresponding to the requested EASID information. +3. EES then declares selected common EAS to all the determined EES(s) along with the Grouping required information and Group ID (if present). +4. Receiving EES stores the received selected common EAS information along with the Grouping required information and Group ID (if present) and sends back an acknowledgement to the sending EES. + +The EES(s) receiving the selected common EAS information which is different from the one it has selected a common EAS, EASs are notified about the other common EASs via EDGE-3 notifications. EASs may initiate EAS-EAS sync as decided and supported by the application and the details of the same are out of scope of this specification. + +NOTE: Whether all EASs (of the same EASID) needs to be notified about the other common EASs will be considered during normative. + +#### 7.31.2.5 Enhancements to 3GPP TS 23.558 Table 8.2.2-1 AC Profile + +The following enhancements (highlighted with bold text) are proposed to Table 8.2.2-1 of TS 23.558 [2]. + +**Table 8.2.2.1: AC Profile (enhanced)** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACID | M | Identity of the AC. | +| AC Type | O | The category or type of AC (e.g. V2X). This is an implementation specific value. | +| Grouping required | O | Indicates Grouping is required for the application. | +| > multi-user session (NOTE 1) | O | Indicates application requires multi-user session | +| > multi-AC session (NOTE 1) | O | Indicates multiple ACs would be part of the session | +| >> List of ACIDs (NOTE 2) | O | Indicates one or more ACIDs need to be served by the same EAS, to be part of the session | +| Preferred ECSP list | O | When used in a service provisioning request, this IE indicates to the ECS which ECSPs are preferred for the AC. The ECS may use this information in the selection of EESs. | +| AC Schedule | O | The expected operation schedule of the AC (e.g. time windows) | +| Expected AC Geographical Service Area | O | The expected location(s) (e.g. route) of the hosting UE during the AC's operation schedule. This geographic information can express a geographic point, polygon, route, signalling map, or waypoint set. | +| AC Service Continuity Support | O | Indicates if service continuity support is required or not for the application. The IE also indicates which ACR scenarios are supported by the AC and which of these are preferred by the AC. | +| List of EASs | O | List of EAS that serve the AC along with the service KPIs required by the AC | +| > EASID | M | Identifier of the EAS | +| > Expected AC Service KPIs | O | KPIs expected in order for ACs to receive currently required services from the EAS, as described in Table 8.2.3-1 | +| > Minimum required AC Service KPIs | O | Minimum KPIs required in order for ACs to receive meaningful services from the EAS, as described in Table 8.2.3-1 | +| NOTE 1: Either one of these or both are present depending on the application scenario. | | | +| NOTE 2: Atleast one ACID is mandatory when multi-AC session IE is present. | | | + +#### 7.31.2.6 Enhancements to 3GPP TS 23.558 8.3.3.2.2 + +Service provisioning procedure in clause 8.3.3.2.2 based on request/response model is enhanced with the following: + +Step 1 is enhanced with -The request message may contains the group information for common EAS selection (e.g. group ID, expected service area) can be provided by the EES within the service provisioning request. + +Step 2 is enhanced with -For the common EAS case, the ECS can determines the alternative EESs for the certain group based on the group information for common EAS selection (e.g. group ID, expected service area) in step 1 + +NOTE: The same EES list will be provided to all the UE in the same group. + +### 7.31.3 Solution evaluation + +The proposed solution addresses Key Issue #17 and Key Issue #13. + +For Key Issue #17: Proposes EAS discovery method enhanced with information required for discovering a common EAS when the same ACID on UEs of different Users (aware or unaware of each other) are within the same EDN, group of ACIDs on UEs of same User are within the same EDN, per group within the same EDN for the same ACID(s), new UEs joining late. + +Proposal covers two main cases – when EEC(s) are registered to same EES and when EEC(s) are registered to different EES(s). + +When EEC(s) are registered to different EES(s) and each EES can select their own common EAS as in Figure 7.31.2.3-1, sync may be performed between EAS-EAS as per application requirement. + +When EEC(s) are registered to different EES(s) and a common EAS is selected across multiple EES as in Figure 7.31.2.2-1, race condition can occur, which is not resolved. + +For Key Issue #13: In order for EAS to know which other EAS to perform synchronization with, EES(s) share their common EAS selection information to other EES(s) as in Figure 7.31.2.4-1, without the involvement of centralized server. The mechanism for EES to announce common EAS information within EDN and across EDN requires further technical evaluation and discussion during normative. + +This solution does not introduce impact on Rel-17 architecture. + +## 7.32 Solution #32: Dynamic EAS instantiation triggering and notification + +### 7.32.1 Architecture enhancements + +None. + +### 7.32.2 Solution description + +#### 7.32.2.1 General + +This solution addresses the Key issue #9: Enhancement of dynamic EAS instantiation triggering for efficient utilization of EDN resources for EAS deployment. + +As specified in TS 23.558 (Rel-17), EES may trigger the EAS instantiation dynamically if there is no instantiated EAS that matches the requesting service characteristics during EAS discovery. + +By collecting one or more of these triggering input events, EES may determine if there is a need for EAS instantiation based on the pre-configured information about instantiable EASs with further considering the requesting service characteristics (e.g. location, latency) by EEC or service load/capacity (e.g. number of service sessions) of EAS. If such a need for EAS instantiation determined, EES may send a report for a need of the EAS instantiation to the ECSP management system (which is specified in TS 28.538 [20]) to consider instantiating the target EAS that is determined to instantiate by invoking an MnS API of the ECSP management system. + +When the target EAS has been instantiated, the EES may obtain the EAS profile based on the updated configuration information by the ECSP management system. Then EES may further notify the instantiation result of the target EAS with the EAS profile to the corresponding EECs in order to inform the EECs of the availability of the EAS instance. + +In this solution, the EAS discovery subscribe-notify procedures are re-used as specified in the clause of 8.5.2.3 of TS 23.558 [2]. EEC may request EES for subscribing to EAS discovery. When the EES gets informed of the EAS instantiation, the EES notifies the EECs whose EAS discovery filters match with the EAS instance. + +NOTE 1: How and when a triggering is determined by EES is upon implementation and out the scope of this solution. + +NOTE 2: The pre-configured information about instantiable EASs may be provided by the ECSP management system but such a mechanism is out of the SA6 scope. + +NOTE 3: With the EAS instantiation request, EES just provides its indication for demanding instantiation of the target EAS to the ECSP management system. Any decision or further actions to the requests are up to the ECSP management system. + +NOTE 4: The MnS APIs for EAS instantiation request/notification should be provided by the ECSP management system and should be consulted with SA5. + +The solution can be summarized as follows: + +##### Dynamic EAS instantiation triggering and notification + +- a. Triggering inputs events: + - i. No available EAS instances matched during EAS discovery +- b. Triggering determination: + - i. Up to EES implementation + - ii. Based on the triggering input events and pre-configured information about instantiable EASs + - iii. Further considerations: + - EEC's requesting service characteristics (e.g. location, latency) as specified in EAS discovery filters + - EAS's service load/capacity (e.g. number of service sessions) maintained by EES +- c. Triggering actions + - i. Invoking an MnS API of the ECSP management system for reporting a need of instantiation of a target EAS +- d. Post-triggering actions + - i. Receiving a notification for instantiation result from the ECSP management system by configuration update + - ii. Notifying the EAS instantiation to the corresponding EECs which have initiated the triggering input events for EAS availability change. + +#### 7.32.2.2 Dynamic EAS instantiation triggering and notification procedures + +The Figure 7.32.2.2-1 depicts the essential operational steps for dynamic EAS instantiation triggering and notification procedures. + +Pre-conditions: + +- 1. EES is pre-configured with the information about instantiable EASs which may be provided by the ECSP management system. + +![Sequence diagram illustrating Dynamic EAS instantiation triggering and notification procedures. Lifelines: EEC #1, EEC #2, EES, MnS (ECSP Mgmt.), and EAS. The process involves subscription requests, a determination for instantiation, a report to MnS, a response, instantiation determination, registration, and final notifications to EECs.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant EEC1 as EEC #1 + participant EEC2 as EEC #2 + participant EES + participant MnS as MnS (ECSP Mgmt.) + participant EAS + + Note right of EES: 3. Determination for a need of EAS Instantiation + + Note right of MnS: 6. EAS Instantiation Determination & Actions + + Note right of EAS: 7. EAS Registration if instantiated + + EEC1->>EES: 1a. EAS Discovery Subscription Request + EES-->>EEC1: 2a. EAS Discovery Subscription Response + EEC2->>EES: 1b. EAS Discovery Subscription Request + EES-->>EEC2: 2b. EAS Discovery Subscription Response + EES->>MnS: 4. Report for a need of EAS Instantiation + MnS-->>EES: 5. Response to the report + MnS->>EAS: 6. EAS Instantiation Determination & Actions + EAS->>EES: 7. EAS Registration if instantiated + EES-->>EEC1: 8a. EAS Discovery Notification + EES-->>EEC2: 8b. EAS Discovery Notification + +``` + +Sequence diagram illustrating Dynamic EAS instantiation triggering and notification procedures. Lifelines: EEC #1, EEC #2, EES, MnS (ECSP Mgmt.), and EAS. The process involves subscription requests, a determination for instantiation, a report to MnS, a response, instantiation determination, registration, and final notifications to EECs. + +**Figure 7.32.2.2-1: Dynamic EAS instantiation triggering and notification procedures** + +- 1a-1b. EECs proceed EAS discovery subscription request with EES, which are triggering input events for dynamic EAS instantiations. +- 2a-2b. EES sends an EAS discovery subscription response to the EEC. +3. Based on the triggering input events, the EES determines if there is a need for EAS instantiation considering the requesting service characteristics provided by EAS discovery filters; or service load/capacity (e.g. number of service sessions) of EAS maintained by the EES. +4. If such a need for EAS instantiation determined, EES sends a report for a need of the EAS instantiation to the ECSP management system for considerations to instantiate the target EAS by invoking an MnS API of the ECSP management system. +5. The MnS of the ECSP management system responds to the EES with indicating that the requesting EAS instantiation will be considered. +6. The ECSP management system determines if the requested EAS instantiation is acceptable by analyzing the deployment requirements and available resources; and proceeds the corresponding actions. (out of scope of this specification) +7. If the target EAS is instantiated successfully, the EES gets informed by an EAS registration procedure of the instantiated EAS with the EAS information (e.g. EAS profile). +- 8a-8b. The EES notifies the EAS instantiation result with EAS discovery notification including the EAS profile to the relevant EECs which have already initiated the triggered input events for the target EAS instance. + +### 7.32.3 Solution evaluation + +This solution allows for an EES to dynamically trigger the EAS instantiation using 1) indication of a need for EAS instantiation to the ECSP management system; and 2) the EAS discovery notification for informing EEC of the result of the EAS instantiation with the EAS profile. + +This solution addresses the key issue #9: enhancement of dynamic EAS instantiation triggering as specified in the clause 4.9. + +This solution relies on the EDGEAPP architecture as specified in TS 23.558 [2] with extended capabilities of EES to determine if there is a need for EAS instantiation considering the requesting service characteristics by EEC or service load/capacity of EAS. + +This solution also relies on an MnS API for indication of a need for EAS instantiation, which shall be provided by the ECSP management system by consulting with SA5. + +## 7.33 Solution #33: Support for EEC Discovery of EAS(es) before instantiation + +### 7.33.1 Architecture enhancements + +None. + +### 7.33.2 Solution description + +#### 7.33.2.1 General + +The following solution corresponds to key issue #9 on enhancements of dynamic EAS instantiation triggering. This solution helps ensure that the proper number of EAS instances are instantiated in the EDN and the solution addresses what information may be utilized by an EES to decide to trigger dynamic EAS instantiation. + +In this solution, the EES is configured by the Management Service (MnS) with information on EAS(s) that can be dynamically instantiated in an EDN; this list provides the information elements needed for requesting EAS instantiation. + +This solution updates the discovery procedure so that EEC can discover EAS(es) executable in an EDN, whether they are instantiated or not. The solution then introduces a new EAS selection procedure so that the EEC can indicate to the EES that it wants to access the services of an EAS that is not yet instantiated. The benefit of this procedure is that EAS instantiation happens after an EEC has selected an EAS, and only at the EES associated with the selected EAS. The solution dissociates EAS discovery, which can be performed with multiple EESes, or can have been performed in a distant past (e.g. relies on caching), from the EAS selection performed at the EEC by providing information elements to the EES about the selection and imminent use of an EAS. + +#### 7.33.2.2 Procedure + +This procedure presents a high-level overview of Solution #33. + +![Sequence diagram showing the high-level overview of solution #33. The diagram involves four main entities: UE (User Equipment) containing AC (Access Controller) and EEC (Edge Enclave Controller); EDN (Edge Data Network) containing EES (Edge Enclave Server), EAS (Edge Enclave Server), and ECS (Edge Enclave Controller); and MnS (Management Service). The sequence of interactions is as follows: 1. MnS deploys EES and EAS(es) per initial deployment requirement. 2. EES registers with ECS. 3. EEC performs service provisioning procedure with ECS. 4. EEC performs EAS discovery with EES(es). 5. EAS selection. 6. EEC sends an EAS selection request to the EES. 7. EES invokes MnS for EAS instantiation (if required). 8. EAS registration (on successful instantiation). 9. EES sends an EAS selection response to the EEC. 10. AC accesses the selected EAS.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EDN + participant MnS + Note right of EDN: EES/EAS initial deployment + Note right of EDN: 1. MnS deploys EES and EAS(es) per initial deployment requirement + Note right of EDN: EES registration + Note right of EDN: 2. EES registers with ECS + Note right of UE: Service provisioning + Note right of UE: 3. EEC performs service provisioning procedure with ECS + Note right of UE: EAS discovery + Note right of UE: 4. EEC performs EAS discovery with EES(es) + Note right of UE: EAS selection + Note right of UE: 5. EAS selection + Note right of UE: 6. EAS selection request + Note right of EDN: 7. EES invokes MnS for EAS instantiation (if required) + Note right of EDN: 8. EAS registration (on successful instantiation) + Note right of UE: 9. EAS selection response + Note right of UE: EAS usage + Note right of UE: 10. AC access selected EAS + +``` + +Sequence diagram showing the high-level overview of solution #33. The diagram involves four main entities: UE (User Equipment) containing AC (Access Controller) and EEC (Edge Enclave Controller); EDN (Edge Data Network) containing EES (Edge Enclave Server), EAS (Edge Enclave Server), and ECS (Edge Enclave Controller); and MnS (Management Service). The sequence of interactions is as follows: 1. MnS deploys EES and EAS(es) per initial deployment requirement. 2. EES registers with ECS. 3. EEC performs service provisioning procedure with ECS. 4. EEC performs EAS discovery with EES(es). 5. EAS selection. 6. EEC sends an EAS selection request to the EES. 7. EES invokes MnS for EAS instantiation (if required). 8. EAS registration (on successful instantiation). 9. EES sends an EAS selection response to the EEC. 10. AC accesses the selected EAS. + +**Figure 7.33.2.2-1: High-level overview of solution #33** + +1. On initial deployment, the Management Service (MnS) is requested to perform EES deployment and can additionally be requested to perform initial EAS deployment. Details on requesting EES and EAS instantiation is specified in 3GPP TS 28.538 [20]. + +To support the dynamic EAS instantiation functionality, the EES needs a list of EAS that it is allowed to dynamically instantiate and corresponding EAS information elements needed for requesting EAS instantiation. + +NOTE 1: How the dynamic EAS instantiation information is made available to the EES is implementation specific in Rel-17 and in the scope of SA5 for Rel-18. + +2. EES registers to the ECS following the procedures described in 3GPP TS 23.558 [2] clause 8.4.4. The EES profile may include EAS that the EES is allowed to instantiate. + +3. EEC performs the service provisioning following the procedures described in 3GPP TS 23.558 [2] clause 8.3.3. +4. When the AC requests application server access, the EEC can perform EAS discovery with one or more EES, or alternatively the EEC can use cached EAS information following the procedures described in 3GPP TS 23.558 [2] clause 8.5. In this solution, the EES may suspend the EAS instantiation and the EAS discovery response may include information about EAS(s) that are not currently instantiated (e.g. EAS discovery response may be updated with Instantiable EAS List (O) information element or EAS Endpoint may be optional in EAS Profile to infer uninstantiated EAS). + +NOTE 2: Due to new behaviour in EES and EAS discovery response message change, stage 3 should consider backward compatibility with R17 EES behaviour for EEC without such enhanced capability as step 6. + +5. The EEC performs EAS selection and can select an EAS that is not currently instantiated. +6. If the EEC selects an EAS that is not currently instantiated, then the EEC informs the EES of the selected EAS by sending an EAS selection request to the EES. Otherwise, the procedure continues to step 10. + +EAS selection request is a new message that contains the following information elements: Requestor identifier (M), UE identifier (O), Security credentials (M), Selected EAS ID (M). + +7. The EAS selection request triggers the EES to verify if the instantiation of the selected EAS is required; since the selected EAS is not instantiated, the EES requests the MnS to perform EAS instantiation for the selected EAS. Upon reception of the EAS instantiation request, MnS verifies EAS instantiation requirements and performs EAS instantiation as specified in 3GPP TS 28.538 [20]. + +Upon instantiation of the EAS by the MnS, the EES is informed by MnS of the result of EAS instantiation. + +NOTE 3: The instantiated EAS can be discovered by other EECs and used by other ACs. + +8. Step 7 happens only if EAS instantiation triggered in step 6 was successful. At start-up, newly instantiated EAS registers to the EES following procedures described in 3GPP TS 23.558 [2] clause 8.4.3. +9. Using the EAS instantiation result received from the MnS in step 6 and the registration information provided at EAS registration in step 7; the EES sends the EAS selection response to the EEC to provide EAS connectivity information. + +EAS selection response is a new message that contains the following information elements: Response Status (M), EAS Profile (O), Failure cause (O). + +If the EAS instantiation result received from the MnS in step 8 indicates failure, the EES shall reject the EAS selection request and respond with an appropriate failure cause. + +10. The AC accesses the selected EAS. + +If the EAS selection request failed, the EEC may retry the EAS selection request taking into account the received failure cause. + +### 7.33.3 Solution evaluation + +Overall evaluation of Solution #33: + +- a) Enables the EES to inform the ECS at EES registration about available EASID(s), regardless of instantiated and instantiable EAS(es). +- b) Enables an EEC to discover uninstantiated EAS(s) by updating the EAS discovery response to allow the EES to additionally include EAS(s) that are not instantiated but can be instantiated by the EES. This allows to keep instantiated EAS to a minimum. +- c) Enables the EEC to inform the EES of the EAS selected by the EEC by sending an EAS selection request. This provides insights to the EES about imminent EAS usage and helps the EES in performing efficient EAS management. +- d) Enables the EES to evaluate if EAS instantiation is needed upon receiving the EAS selection request. This allows the EES to evaluate if an EAS has become available, and otherwise trigger EAS instantiation only if needed. + +## 7.34 Solution #34: EDGE-5 APIs + +### 7.34.1 Architecture enhancements + +None. + +### 7.34.2 Solution description + +#### 7.34.2.1 General + +This solution corresponds to key issue #4 on EDGE-5 reference point between ACs and the EEC. + +The solution provides an API for the AC to request for EEC's services for edge enablement corresponding to EEC's capabilities. Using this API, AC may request the EEC for EEL services. The solution defines APIs for one-time request/response operations for EAS discovery and ACR operations. Additionally, The AC can request an AC subscription. The EEC creates the subscription and when required, performs necessary operations such as EAS discovery, ACR etc. delivering notifications to the AC as required. + +NOTE: EEC can initiate any EDGE-1 or EDGE-4 operation without receiving a request or without receiving AC related information from the AC. + +#### 7.34.2.2 Procedure + +##### 7.34.2.2.1 General + +The solution provides the following procedures: + +- AC registration request; +- EAS discovery request; +- ACR request; +- AC subscription; and +- AC notification. + +NOTE: Details on how the AC and EEC communicate with each other is out of scope. + +##### 7.34.2.2.2 AC registration request + +Pre-conditions: + +1. The AC can communicate with the EEC. + +NOTE 1: Details on how the AC and EEC communicate with each other is out of scope. + +![Sequence diagram of AC registration request procedure](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` +sequenceDiagram + participant AC + participant EEC + Note right of EEC: 2. Request validation + AC->>EEC: 1. AC registration request + EEC->>AC: 3. AC registration response +``` + +The diagram illustrates the AC registration request procedure. It features two lifelines: AC (Application Client) and EEC (Edge Enabling Center). The sequence of messages is as follows: 1. AC sends an 'AC registration request' to EEC. 2. EEC performs 'Request validation' (shown in a box on the EEC lifeline). 3. EEC sends an 'AC registration response' back to AC. + +Sequence diagram of AC registration request procedure + +**Figure 7.34.2.2.2-1: AC registration request procedure** + +1. The AC sends an AC registration request to the EEC. The request includes the AC profile, AC's security credentials and optionally the EAS characteristics and EAS discovery filters. The request may also include a list of EEC's services that AC requires the EEC to handle. The request additionally includes ECS configuration information if the AC is edge-aware and configured with the ECS configuration information. + +NOTE 2: The ASP providing the AC and the ECSP providing the ECS can have edge computing service provider service agreement as in clause 9. The ECS configuration information configured in the AC is based on the service agreement. + +2. The EEC checks AC's security credentials and validates the request. + +3. If the request is successfully validated, the EEC registers the information provided in the request and responds back to the AC with AC registration response. The AC registration response includes the list of capabilities supported by the EEC e.g. which service continuity scenarios are supported by the EEC. If the request in step 1 included a list of EEC's services AC requires from the EEC, the response also includes a list of EEC's services that AC is authorized for. + +NOTE 3: The mechanisms used for authentication and authorization between AC and EEC is out of scope of this specification. EEC can use local policies, user preferences, ASP services agreement(s) (see clause 9) to authorize the request from the AC. + +NOTE 4: Additional procedures between AC and EEC to update the registration or deregister are necessary. + +NOTE 5: When the ECS configuration information is provided from an AC, the EEC can use the ECS configuration for initial service provisioning for the AC that provided the ECS configuration information if there is no ECS configuration information is provided from the 5GC. + +##### 7.34.2.2.3 EAS discovery request + +Pre-conditions: + +1. The AC can communicate with the EEC. + +![Sequence diagram illustrating the EAS discovery request procedure between AC and EEC.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant AC + participant EEC + Note right of EEC: 2. Request validation + Note right of EEC: 3. EAS discovery + AC->>EEC: 1. EAS discovery request + EEC-->>AC: 4. EAS discovery response + +``` + +The diagram shows a sequence of four messages between an AC (Application Client) and an EEC (Edge Enabler Client). + 1. The AC sends an 'EAS discovery request' to the EEC. + 2. The EEC performs 'Request validation' (shown in a box). + 3. The EEC performs 'EAS discovery' (shown in a box). + 4. The EEC sends an 'EAS discovery response' back to the AC. + +Sequence diagram illustrating the EAS discovery request procedure between AC and EEC. + +**Figure 7.34.2.2.3-1: EAS discovery request procedure** + +1. The AC sends an EAS discovery request to the EEC. The request includes AC's security credentials and may include AC profile and EAS discovery filters. +2. The EEC checks AC's security credentials and validates the request. +3. If the request is successfully validated, the EEC determines if the required EAS is available or not. The EEC may use information cached or preconfigured at the EEC or may use the EAS discovery procedures to query the EES. If step 1 includes the AC profile or EAS discovery filters, then the EEC may utilize the provided AC profile and filters, to form the EAS discovery request towards EES. If step 1 does not include AC profile and EAS discovery filters, and AC registration was performed, the EEC may utilize the AC profile provided by the AC during AC registration. The EEC also needs to take user privacy requirements, e.g. regarding the disclosure of location information towards the network into account. If required, e.g. when EAS discovery procedures returns a list of EASs, the EEC performs EAS selection based on the information received in step 1 and the AC profile. The EEC can perform EAS discovery with different EESs before selecting an EAS. + +NOTE 1: SA3 recommendations, if any, on how the user or the AC can consent, e.g. to the disclosure of location information and the use of the AC ID in the signalling towards the network must be considered during normative. + +NOTE 2: If required, the EEC can perform service provisioning procedure, or EEC registration procedure or both, before performing the EAS discovery procedures. EEC may already have captured EESs and EASs availability for present location; so that the AC's request (step #1) can be replied to quickly and efficiently. + +NOTE 3: The EEC can include AC profiles of more than one AC in the EAS discovery request sent to the EES. + +4. The EEC responds back to the AC with the EAS discovery response. The response includes the EAS profile(s) of the available EAS(s). + +##### 7.34.2.2.4 ACR request + +Pre-conditions: + +1. The AC can communicate with the EEC. + +![Sequence diagram of ACR request procedure between AC and EEC.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` +sequenceDiagram + participant AC + participant EEC + Note right of EEC: 2. Request validation + AC->>EEC: 1. ACR request + EEC->>AC: 3. ACR response +``` + +The diagram illustrates the ACR request procedure. It features two lifelines: AC (left) and EEC (right). The sequence of messages is as follows: 1. AC sends an 'ACR request' message to EEC. 2. EEC performs 'Request validation' (shown as a self-message on the EEC lifeline). 3. EEC sends an 'ACR response' message back to AC. + +Sequence diagram of ACR request procedure between AC and EEC. + +**Figure 7.34.2.2.4-1: ACR request procedure** + +1. The AC sends an ACR request to the EEC. The request includes AC's security credentials, type of requested operation (i.e. ACR detection, ACR initiation) and AC profile. If the request is to initiate the ACR, the request may also include the target EAS information. +2. The EEC checks AC's security credentials and validates the request. +3. If the request is successfully validated, the EEC process the request from the AC. If the type of requested operation in the request received in step 1 is: + - ACR detection, then the EEC determines if ACR is required or not. If it is required, the EEC uses one of the EEC initiated ACR scenarios or launches ACR with action "determination", leading to S-EES executed ACR; + - ACR initiation, then the EEC uses one of the EEC initiated ACR scenarios and initiate ACR. If the request in step 1 also includes target information, the EEC uses it to select the ACR targets; + +##### 7.34.2.2.5 AC subscription request + +Pre-conditions: + +1. The AC can communicate with the EEC. + +![Sequence diagram illustrating the AC subscription request procedure between AC and EEC.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant AC + participant EEC + Note right of EEC: 2. Request validation + Note right of AC: 4. Execute EEC services + AC->>EEC: 1. AC subscription request + EEC->>AC: 3. AC subscription response + +``` + +The diagram shows a sequence of interactions between an AC (Application Client) and an EEC (Edge Enabler Client). + 1. The AC sends a solid arrow labeled '1. AC subscription request' to the EEC. + 2. A dashed box labeled '2. Request validation' is shown on the EEC side. + 3. The EEC sends a solid arrow labeled '3. AC subscription response' back to the AC. + 4. A dashed box labeled '4. Execute EEC services' is shown on the AC side. + +Sequence diagram illustrating the AC subscription request procedure between AC and EEC. + +**Figure 7.34.2.2.5-1: AC subscription request procedure** + +1. The AC sends an AC subscription request to the EEC. The request includes AC's security credentials, a list of EEC's services that AC requires the EEC to handle, and related parameters such as AC profile. If the subscription request includes: + - EAS discovery or EAS dynamic information subscription, then the request may include EAS discovery filters + - ACR management, then the request may include type of ACR operations: + - ACR monitoring, where the EEC monitors the need for ACR and notifies the AC as and when required e.g. on receiving ACR related notifications on EDGE-1 interface. + - EEC managed ACR, where the EEC monitors the need for ACR. If need for ACR is detected, then the EEC decides and initiates ACR using one of the EEC initiated ACR scenarios. The EEC notifies the AC about the imminent ACR and may include the target information. +2. The EEC checks AC's security credentials and validates the request. +3. If the request is successfully validated, the EEC creates the subscription and sends an AC subscription response message to the AC. The response includes the list of services that the EEC will handle and related details. +4. The EEC executes the services e.g. EAS discovery, ACR management, and notifies the AC with information as necessary. The EEC may use locally cached information or configurations while providing services to the AC. + +NOTE: Additional procedures between AC and EEC to update the subscription or to unsubscribe are necessary. + +##### 7.34.2.2.6 AC notification + +Pre-conditions: + +1. The AC has subscribed to the EEC. + +![Sequence diagram illustrating the EAS discovery notification procedure. It shows two lifelines: AC (Application Context) and EEC (Edge Enclave). The EEC sends a message labeled '1. Trigger for AC notification' to the AC. The AC then sends a response message labeled '2. AC notification' back to the EEC.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant AC + Note right of EEC: 1. Trigger for AC notification + EEC->>AC: 2. AC notification + +``` + +Sequence diagram illustrating the EAS discovery notification procedure. It shows two lifelines: AC (Application Context) and EEC (Edge Enclave). The EEC sends a message labeled '1. Trigger for AC notification' to the AC. The AC then sends a response message labeled '2. AC notification' back to the EEC. + +**Figure 7.34.2.2.6-1: EAS discovery notification procedure** + +1. An event occurs at the EEC that satisfies trigger conditions for notifying a AC e.g. EEC detects a need for Application Context Relocation. +2. The EEC sends an AC notification to the AC with relevant information related to the event triggered in step 1. + +### 7.34.3 Solution evaluation + +This solution relates to KI#4 on EDGE-5 interface. The solution provides multiple procedures to allow uniform interaction of ACs with the EECs. The solution specifies procedures for AC registration, EAS discovery requests/response, ACR related request/response and AC's subscription to EEC. + +The solution has no impacts on Rel-17 cardinalities defined for EDGE-5. Aspects related to mutual authentication, authorization and user consent require inputs from SA3. + +## 7.35 Solution #35: EEC selected ACR scenarios + +### 7.35.1 Architecture enhancements + +None + +### 7.35.2 Solution description + +#### 7.35.2.1 General + +The following solution corresponds to the key issue #19 on ACR scenario combination. + +#### 7.35.2.2 Procedure + +In this solution, the EEC is responsible to determine the ACR scenario(s) that should be used for an AC and EAS pair. The EEC performs ACR selection at EAS selection time. + +The following ACR selection outcomes are possible: + +- The EEC can select no ACR scenario which indicates that service continuity is not supported or needed. +- The EEC can select one ACR scenario which indicates that service continuity is supported and needed, but that ACR coordination is not needed. +- The EEC can select two or more ACR scenarios which indicates that service continuity is supported and needed, and that ACR coordination is needed. + +ACR coordination ensures that only one of the selected ACR scenarios proceeds through the ACR execution phase. Coordination of concurrent ACR execution is out of scope of this solution. + +Figure 7.35.2.2-1 presents an overview of the procedures for ACR selection at the EEC. + +Pre-condition: + +- EEC has performed service provisioning procedure with the ECS. + +![Sequence diagram showing the interaction between EEC, S-EES, and S-EAS for ACR selection. The steps are: 1. EAS discovery (EEC to S-EES), 2. EAS and ACR selection (internal to EEC), 3. selected EAS announcement request (incl. ACR scenario list) (EEC to S-EES), 4. ACR selection notification (S-EES to S-EAS), 5. selected EAS announcement response (S-EES to EEC).](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant S-EES + participant S-EAS + Note left of EEC: 1. EAS discovery + Note left of EEC: 2. EAS and ACR selection + EEC->>S-EES: 3. selected EAS announcement request (incl. ACR scenario list) + S-EES->>S-EAS: 4. ACR selection notification + S-EES->>EEC: 5. selected EAS announcement response + +``` + +Sequence diagram showing the interaction between EEC, S-EES, and S-EAS for ACR selection. The steps are: 1. EAS discovery (EEC to S-EES), 2. EAS and ACR selection (internal to EEC), 3. selected EAS announcement request (incl. ACR scenario list) (EEC to S-EES), 4. ACR selection notification (S-EES to S-EAS), 5. selected EAS announcement response (S-EES to EEC). + +**Figure 7.35.2.2-1 EEC selected ACR scenarios** + +1. The EEC performs EAS discovery using procedures defined in 3GPP TS 23.558 [2] clause 8.5 to obtain a list of discovered EAS(s). + +The discovered EAS list contains EAS(s) that are compatible with the AC and EEC ACR capabilities provided in the EAS discovery request or subscription. + +2. The EEC (or AC and EEC) selects one EAS from the discovered EAS list. + +Additionally, the EEC selects the ACR scenario(s) that should be used for the given AC and selected EAS. ACR selection can result in zero or more ACR scenarios being selected. For selecting the ACR, the EEC minimally considers the ACR capabilities of the AC from AC Profile, of the EEC (known locally), of the EES from service provisioning response received from the ECS (pre-requisite), and of the EAS from EAS Profile and obtained at EAS discovery. + +NOTE: ACR selection criteria minimally can include ACR capabilities of the AC/EEC/EES/EAS; other criterias are possible and left out of scope of the current solution. + +**Editor's note: Whether AC service KPI also will be considered by the EEC to decide on the ACR scenario(s) is FFS.** + +3. The EES uses the list of selected ACR scenarios to determine if it should perform ACR detection and/or ACR decision. + +4. The EES sends an ACR selection notification to the selected EAS providing the selected ACR scenario list. Not shown on the figure, the EAS previously subscribed to receive ACR notifications. The EAS uses the selected ACR scenarios list to determine if it should perform ACR detection and/or ACR decision. + +5. The EES sends the selected EAS declaration response to the EEC indicating success or failure of the EAS announcement request. + +### 7.35.3 Solution evaluation + +Solution #35 enables the following aspects for ACR scenario(s) selection for one AC: + +- a) ACR scenario(s) selection is performed at the EEC and happens after EAS selection has been performed at the EEC (or AC and EEC). This ensures that the service session (e.g. AC/EAS pair) are known by the EEC before it selects ACR scenario list. +- b) the EEC minimally considers each of the AC/EEC/EES/EAS ACR capabilities in order to form an ACR scenario list; the list can include zero ACR scenarios (e.g. ACR not needed) or more. This provides the benefit of covering all possible ACR combinations; expressed differently, it is possible to not use ACR and it is possible to involve multiple participants to perform ACR detection. +- c) the EEC propagates the ACR scenario list to the selected EES by sending a selected EAS announcement request; and the EES propagates the ACR scenario list to the selected EAS by sending an ACR selection notification. This allows every ACR participant to learn which ACR scenarios have been selected, and allows every participant to initiate ACR detection according the selected ACR scenario list. Additionally, only the EES and selected EAS are informed of the ACR selection list. + +## 7.36 Solution #36: Alignment of EDGEAPP and ETSI MEC + +### 7.36.1 Architecture enhancements + +Architecture requirements in clause 5.4 will serve as the guiding principles for the alignment of EDGEAPP and ETSI MEC architectures. + +### 7.36.2 Solution description + +#### 7.36.2.1 General + +This solution is to address KI# 5: Alignment of EDGEAPP and ETSI MEC. + +In particular, the solution addresses the third open issue, which is providing solutions based on the observations, study, and comparison of ETSI MEC and EDGEAPP specifications. + +#### 7.36.2.2 Alignment of EAS registration and MEC application registration + +According to Annex C of 3GPP TS 23.558 [2] MEC application and MEC platform in ETSI MEC correspond respectively to EAS and EES in 3GPP specification. Similarly, Mp1 interface corresponds to EDGE-3. According to observation A.3-1 in Annex A, registration of an instance of an application is supported by both ETSI MEC and 3GPP. Additionally, observation A.3-2 further clarifies that some of the IEs of the EAS profile may overlap with the ones defined in AppInfo, while some other IEs are specific to each of the EAS profile or AppInfo. + +In order to support registration of an application on EES it is required that the registration request includes at least the mandatory IEs that are required for EAS registration, i.e. EAS ID and EAS endpoint. On the other hand, according to ETSI GS MEC 011 [14] the application registration request must include AppName and App Provider. + +AppInfo which is defined in ETSI GS MEC 011 [14] includes AppName and App Provider as mandatory IEs and endpoint as an optional IE. AppName can be considered equivalent to EAS ID. Similarly, App Provider corresponds to EAS Provider Identifier. Endpoint in ETSI GS MEC 011 [14] can be directly mapped to EAS endpoint. See Table 7.36.2.2-1 for a comparison between the EAS profile and appInfo. + +**Table 7.36.2.2-1: Comparison between EAS Profile and appInfo** + +| IE in EAS profile | Status | IE in appInfo [14] | Status [14] | Remarks | +|-------------------|--------|--------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------| +| EASID | M | appName | M | 3GPP specification [2]: The EASID identifies a particular application for e.g. SA6Video, SA6Game etc. For example, all Edge | + +| | | | | | +|-------------------------------|---|--------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | | SA6Video Servers will share the same EASID.
NOTE: The definition of the EASID is out of scope of this specification.

ETSI MEC specification [14]: Name of the application. It shall be consistent with the appName in the AppD, if an AppD is available. In AppD, it is defined as: Name to identify the MEC application.

In both specifications, the IE is used to identify a particular application. The purpose of the IE is the same in both specifications, and can be considered equivalent. | +| EAS Endpoint | M | endpoint | O | 3GPP specification [2]: Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS.

ETSI MEC specification [14]: Endpoint information (e.g. URI, FQDN, IP address) of the application server, which is part of the application functionalities.

The purpose of the IE is the same in both specifications, and can be considered equivalent. | +| ACID(s) | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS Provider Identifier | O | App Provider | M | 3GPP specification [2]: The identifier of the ASP that provides the EAS.

ETSI MEC specification [14]: Provider of the application. It shall be consistent with the appProvider in the AppD, if an AppD is available.

The purpose of the IE is the same in both specifications, and can be considered equivalent. | +| EAS Type | O | appCategory | O | 3GPP specification [2]: The category or type of EAS (e.g. V2X)

ETSI MEC specification [14]: Category of the application.

The purpose of the IE is the same in both specifications, and can be considered equivalent. | +| EAS description | O | AppD
> appDescription | O | 3GPP specification [2]: Human-readable description of the EAS.

ETSI MEC specification [14]: Human readable description of the MEC application.

The purpose of the IE is the same in both specifications, and can be considered equivalent. | +| EAS Schedule | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS Geographical Service Area | O | | | The IE is not applicable in application registration in ETSI MEC. | + +| | | | | | +|-----------------------------------------|---|--------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EAS Topological Service Area | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS Service KPIs | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS service permission level | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS Feature(s) | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS Service continuity support | O | | | The IE is not applicable in application registration in ETSI MEC. | +| List of EAS DNAI(s) | O | | | The IE is not applicable in application registration in ETSI MEC. | +| List of N6 Traffic Routing requirements | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS Availability Reporting Period | O | | | The IE is not applicable in application registration in ETSI MEC. | +| EAS Status | O | | | The IE is not applicable in application registration in ETSI MEC. | +| | | appDId | O | ETSI MEC specification [14]: The application descriptor identifier. It is managed by the application provider to identify the application descriptor in a globally unique way. Shall be present if the application instance is instantiated by the MEC Management. | +| | | appInstanceId | O | ETSI MEC specification [14]: Identifier of the application instance. Shall be present if the application instance is instantiated by the MEC Management. | +| | | appServiceRequired | O | ETSI MEC specification [14]: Describes services a MEC application requires to run. ServiceDependency is defined in ETSI GS MEC 010-2 [13]. It shall shall not be provided if an AppD is available. | +| | | appServiceOptional | O | ETSI MEC specification [14]: Describes services a MEC application may use if available. ServiceDependency is defined in ETSI GS MEC 010-2 [13]. It shall shall not be provided if an AppD is available. | +| | | appFeatureRequired | O | ETSI MEC specification [14]: Describes features a MEC application requires to run. FeatureDependency is defined in ETSI GS MEC 010-2 [13]. It shall shall not be provided if an AppD is available. | +| | | appFeatureOptional | O | ETSI MEC specification [14]: Describes features a MEC application may use if available. FeatureDependency is defined in ETSI GS MEC 010-2 [13]. It shall shall not be provided if an AppD is available. | + +NOTE 1: The appInfo currently appears in the draft version of ETSI GS MEC 011 V3.0.6 (2022-03) [14]. In the current draft version, two additional IEs, isEAS and easProfile, are included in the appInfo to hold the place for providing EAS profile. These two IEs are not applicable to this solution, which analyses correspondence between IEs in EAS profile and appInfo. + +This solution proposes to enable the application to perform registration on EES according to the mapping between appInfo and EAS profile. + +NOTE 2: The solution does not impact the procedures. + +#### 7.36.2.3 Alignment of EDGE-9 and Mp3 + +EDGE-9 interface in EDGEAPP architecture is used to support mobility of user from one EES to another EES. On the other hand, ETSI MEC has not specified APIs over Mp3. Mp3 reference point between MEC platforms is used for control communication between MEC platforms [3] with a separate application mobility service [22] being provided in support of mobility of users between MEC hosts within a MEC system. The present study does not identify overlap or equivalent functionality between the APIs on EDGE-9 and Mp3 interfaces; therefore, currently no alignment is required. + +### 7.36.3 Solution evaluation + +This solution is based on the principles set in clause 5.4 and addresses alignment by mapping between overlapping APIs in EDGEAPP and ETSI MEC. In that regard, for EDGE-3 and Mp1 the solution enables the application to perform registration on EES according to the mapping between appInfo [14] and EAS profile. + +The present study does not identify overlap or equivalent functionality between the APIs on EDGE-9 and Mp3 interfaces; therefore, currently no alignment is required. + +The solution does not require changes in architecture and procedures. + +## 7.37 Solution #37: ACR request trigger timing + +### 7.37.1 Architecture enhancements + +None. + +### 7.37.2 Solution description + +This solution corresponds to the key issue #3 on enhancements to service continuity planning. + +To support the determination of the ACR request trigger timing in case of service continuity planning, this solution proposes to introduce "General context holding time" as shown in table 7.37.2-2. This IE is an indication of the maximum time the EAS holds the application context for a UE to move to its service area after receiving an ACR notification from the EES following an ACR request from the EEC. "General context holding time" can be provided to the EES during the EAS registration request or EAS registration update (when there is a change). + +Since the EASID of the EAS identifies the type of the application context (e.g. SA6Video, SA6Game etc) as described in TS 23.558 clause 7.2.4, "General context holding time" determined can depend on the EASID (type of the application context). + +This IE can then be provided to the EEC during the discovery so that the EEC can use the time to decide when to make an ACR request. The EEC may provide "prediction expiration time" as in Solution#21 in the ACR request as per its predictions by making sure it does not exceed the "General context holding time". + +"General context holding time" can be determined or updated due to factors such as resource usage and policy setting such as the policy of the ECSP providing the EHE where the EAS is hosted. In such a case, the T-EAS sends the EAS registration update request and the EES updates the "General context holding time" in the EAS profile. + +**Table 7.37.2-2: EAS Profile** + +| Information element | Status | Description | +|-------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EASID | M | The identifier of the EAS | +| EAS Endpoint | M | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS. This information maybe discovered by EEC and exposed to ACs so that ACs can establish contact with the EAS. | +| General context holding time | O | The time that the EAS holds the context before the AC connects to the EAS in case of ACR for service continuity planning. It is an indication of the time the EAS holds the application context for a UE to move to its service area after receiving an ACR notification from the EES following an ACR request from the EEC. | +| ACID(s) | O | Identifies the AC(s) that can be served by the EAS | + +#### 7.37.2.1 Procedure + +#### 7.37.2.2 Enhancements to procedures in TS 23.558 + +The EEC can use the "General context holding time" to make a timely ACR request by performing an ACR launching procedure when it predicts to move to the service area of the discovered EAS within the time indicated in the IE. To reflect this, the procedures in service continuity scenarios in clause 8.8.2.2, clause 8.8.2.3, and clause 8.8.2.6 of 3GPP TS 23.558 [2] – Initiation by EEC using regular EAS Discovery, EEC executed ACR via S-EES, and EEC executed ACR via T-EES – are enhanced as follows: + +##### 7.37.2.2.1 Enhancements to 'Initiation by EEC using regular EAS Discovery' in clause 8.8.2.2 + +4. The EEC performs EAS discovery (as specified in clause 8.5) for the desired T-EASs by querying the T-EEs that were established in step 3 (or provided in the notification from the ECS – if it was the trigger). If EEC registration configuration for the EESs established in step 2 indicates that EEC registration is required, the EEC performs EEC registration with the EESs (as specified in clause 8.4.2.2.2) before sending the EAS discovery request. Step 5 is skipped if EAS discovery procedure results in only one discovered T-EAS. + +**When in step 1 the ACR for service continuity planning is triggered, and the "General context holding time" is included in the replied EAS discovery response, the EEC can make ACR request before it reaches respective T-EAS service area within the time period indicated by the IE.** + +5. The AC and EEC select the T-EAS to be used for the application traffic. + +NOTE 1: Several EEC registrations with different EESs may result from T-EAS discovery process during a single ACR operation. + +6. The EEC performs ACR launching procedure (as described in clause 8.8.3.4) to the S-EES with the ACR action indicating ACR initiation and the corresponding ACR initiation data (without the need to notify the EAS). The S-EES may apply the AF traffic influence with the N6 routing information of the T-EAS in the 3GPP Core Network (if applicable), as described in clause 8.8.3.4. If the EEC has not subscribed to receive ACR information notifications for ACR complete events from the S-EES, the EEC subscribes for the notifications as described in clause 8.8.3.5.2. + +##### 7.37.2.2.2 Enhancements to 'EEC executed ACR via S-EES' in clause 8.8.2.3 + +###### Phase I: ACR Detection + +1. The EEC detects that ACR may be required as described in clause 8.8.1. The EEC may detect that ACR may be required for an expected or predicted UE location in the future as described in clause 8.8.1. + +###### Phase II: ACR Decision + +2. The EEC decides to proceed required procedures for triggering ACR. + +###### Phase III: ACR Execution + +3. The EEC determines the T-EES by using the provisioned information or performing service provisioning procedure per clause 8.3 of the present document. When in step 1 the ACR for service continuity planning is triggered, then the Connectivity information and UE Location in the Service Provisioning (as specified in clause 8.3) procedure contains the expected Connectivity information and expected UE Location. If the UE is within the service area of the T-EES, upon selecting T-EES the UE may need to establish a new PDU connection to the target EDN. If EEC registration configuration for the T-EES indicates that EEC registration is required, the EEC performs EEC registration with the selected T-EES as specified in clause 8.4.2.2.2. The EEC can then discover and select T-EAS by performing EAS Discovery with the T-EES per clause 8.5.2 of the present document. + +**When in step 1 the ACR for service continuity planning is triggered, and the "General context holding time" is included in the replied EAS discovery response, the EEC can make ACR request before it reaches respective T-EAS service area within the time period indicated by the IE.** + +NOTE 1: Several EEC registrations with different EESs may result from T-EAS discovery process during a single ACR operation. + +4. The EEC performs ACR launching procedure (as described in clause 8.8.3.4) to the S-EES with the ACR action indicating ACR initiation and the corresponding ACR initiation data (with the need to notify the EAS). The S-EES authorises the request from the EEC. The S-EES decides to execute ACR based on the information received from the EEC, EEC context and/or EAS profile. The S-EES may apply the AF traffic influence with the N6 routing information of the T-EAS in the 3GPP Core Network (if applicable) and sends the ACR Notify message to the S-EAS to initiate ACT between the S-EAS and the T-EAS. If the EEC has not subscribed to receive ACR information notifications for ACR complete events from the S-EES, the EEC subscribes for the notifications as described in clause 8.8.3.5.2. + +##### 7.37.2.2.3 Enhancements to 'EEC executed ACR via T-EES' in clause 8.8.2.6 + +###### Phase I: ACR Detection + +1. The EEC detects that ACR may be required as described in clause 8.8.1. The EEC may detect that ACR may be required for an expected or predicted UE location in the future as described in clause 8.8.1. + +###### Phase II: ACR Decision + +2. The EEC decides to proceed with required procedures for ACR. + +NOTE 1: If supported, the AC can be involved in the decision. It is out of scope of the present document how the AC is involved. + +###### Phase III: ACR Execution + +3. The EEC determines the T-EES by using the provisioned information or performing service provisioning procedure per clause 8.3. When in step 1 the ACR for service continuity planning is triggered, then the Connectivity information and UE Location used in the service provisioning procedure contain the expected Connectivity information and expected UE Location. If the UE is within the service area of the T-EES, upon selecting the T-EES the UE may need to establish a new PDU connection to the target EDN. If EEC registration configuration for the T-EES indicates that EEC registration is required, the EEC performs registration with the selected T-EES as specified in clause 8.4.2.2.2. The EEC performs EAS Discovery with the T-EES per clause 8.5.2. + +**When in step 1 the ACR for service continuity planning is triggered, and the "General context holding time" is included in the replied EAS discovery response, the EEC can make ACR request before it reaches respective T-EAS service area within the time period indicated by the IE.** + +NOTE 2: Several EEC registrations with different EESs may result from T-EAS discovery process during a single ACR operation. + +4. The EEC performs ACR launching procedure (as described in clause 8.8.3.4) to the T-EES with the ACR action indicating ACR initiation and the corresponding ACR initiation data (with the need to notify the EAS). If the received ACR initiation request contains an EEC context ID and the S-EES Endpoint, the T-EES performs an EEC Context Pull relocation (clause 8.9.2.2). The T-EES may apply the AF traffic influence with the N6 routing information of the T-EAS in the 3GPP Core Network (if applicable). Then the T-EES sends the ACR Notify message to the T-EAS. The EEC also subscribes to receive ACR information notifications for ACR complete events from the T-EES, as described in clause 8.8.3.5.2. + +### 7.37.3 Solution evaluation + +This solution addresses open issue #2, open issue #5, and open issue #6 of KI#3. + +This solution introduces a "General Context Holding Time" IE in the EAS profile which can be determined based on the EASID of the EAS which identifies the type of application context, ECSP policy setting, and other factors such as resource usage. The "General Context Holding Time" is the time the EAS holds the application context before the UE reaches the T-EAS service area following an ACR request. + +The solution allows this "General Context Holding Time" to be sent from the EES to the EEC in the EAS discovery response. Therefore, the EEC can make an ACR request before it reaches the respective T-EAS service area when it is predicted or planned to move to the T-EAS service area within the time indicated by the IE. With this, the issue of the determination of the ACR request trigger timing in case of service continuity planning is addressed. + +The potential impact on the information to communicate within the EEL is only by introducing a "General Context Holding Time" IE in the EAS profile. Accordingly, clause 8.8.2.2, clause 8.8.2.3, and clause 8.8.2.6 need to be updated to use the "General Context Holding Time" for ACR triggering. + +## 7.38 Solution #38: ACR coordination + +### 7.38.1 Architecture enhancements + +None + +### 7.38.2 Solution description + +#### 7.38.2.1 General + +The following solution corresponds to the key issue #19 on ACR scenario combination. + +#### 7.38.2.2 Procedure + +Multiple ACR scenarios can be selected and the detection entity can start detecting the need for ACR. In this solution, the decision-making entity (e.g. EEC, EES, EAS) of any selected scenario triggers the ACR. However, once the ACR procedure is triggered, the EES notifies the decision-making entities of other scenario(s) about the start of the ACR. Once the ACR procedure is completed, the EES notifies the decision-making entities of other scenario(s) about the completion of the ACR (success or failure). The decision-making entities of other scenario(s) may avoid triggering another ACR till one ACR procedure is in progress and notification about the completion of the ACR is received. + +The solution proposes to enhance ACT status subscription procedure as specified in clause 8.8.3.6.2.3 of 3GPP TS 23.558 [2] and ACR information subscription as specified in clause 8.8.3.5.2 of 3GPP TS 23.558 [2] to subscribe for ACR execution start event. + +Further, the solution proposes to enhance all scenarios specified in clause 8.8.2 of 3GPP TS 23.558 [2] to send notification of start of ACR execution phase as follows: + +Pre-condition: + +- 1) More than one ACR scenarios are selected as specified in solution#19 or solution#35. + +![Sequence diagram illustrating ACR coordination between EES, S-EAS, and EEC. The process starts with EES triggering the ACR (1). EES then sends an ACR management event notification (ACT Start) to S-EAS (2a) and an ACR information notification to EEC (2b). Finally, EES performs ACR procedures (3).](476d6fb9044a040636d52619c7c43b1a_img.jpg) + +``` + +sequenceDiagram + participant EES + participant S-EAS + participant EEC + Note left of EES: 1) ACR is triggered (i.e. T-EAS is discovered and execution of one of the ACR scenario is started) + EES->>S-EAS: 2a. ACR management event notification (ACT Start) + EES->>EEC: 2b. ACR information notification (to indicate start of the ACR) + Note left of EES: 3. perform ACR procedures (as specified in the scenarios) + +``` + +Sequence diagram illustrating ACR coordination between EES, S-EAS, and EEC. The process starts with EES triggering the ACR (1). EES then sends an ACR management event notification (ACT Start) to S-EAS (2a) and an ACR information notification to EEC (2b). Finally, EES performs ACR procedures (3). + +**Figure 7.38.2.2-1: ACR coordination** + +- 1) The ACR is triggered by one of the decision making entity (i.e. EAS or EES or EEC) and T-EAS is discovered. +- 2a) If EEC or EES has initiated ACR, then the EES sends ACR management event notification (ACT Start) to the S-EAS indicating the start of the ACR execution. The notification message includes ACR identity (ACID, EEC ID (or UE ID), S-EAS endpoint and T-EAS endpoint). + +- 2b) If S-EAS or EES has initiated ACR, then the EES sends ACR information notification to EEC indicating the start of the ACR execution. The notification message includes ACR identity (ACID, EEC ID (or UE ID), S-EAS endpoint and T-EAS endpoint). + +NOTE: ACT initiation can be considered as a start of the execution phase. + +- 3) The ACR procedure is performed as specified in the scenario (in clause 8.8.2 of 3GPP TS 23.558 [2]) + +If concurrent ACR requests happens the EES rejects the additional ACR requests. + +##### Enhancements to clause 8.8.3.5.3 ACR information notification procedure + +Step 2 of the procedure will be modified as follows (in bold) + +2. The EES sends an ACR information notification to the EEC with the ACR information determined in step 1. The ACR information notification may include ACID to indicate the application context relocation of the AC is complete. If the S-EES has received the successful EEC Context Push response from T-EES, along with registration ID and the registration expiration time in the EEC Context Push relocation procedure, then the ACR information notification towards EEC also includes the registration ID and registration expiration time under EEC context relocation status (for successful status). **Upon receiving the target information notification to indicate about start of the ACR execution, the EEC prevents triggering a second ACR execution for the same identity (ACID, EEC ID (or UE ID), S-EAS endpoint and T-EAS endpoint) until the current ACR execution is completed.** + +##### Enhancements to clause 8.6.3.2.3 Notify (for ACR management event notification) + +Step 1-d will be modified as follows (bold): + +- d. If "ACT start/stop" event is subscribed, during the ACR launch if the EEC indicates the need to notify the EAS in the ACR request as described in clause 8.8.3.4, the EES shall send notification to the EAS to inform it about the need to start or stop the ACT to or from another EAS. **The notification message includes ACR identity (ACID, EEC ID (or UE ID), S-EAS endpoint and T-EAS endpoint).** +2. The EES sends ACR management event notification to the EAS. The EES includes the ACR management event notification information of the UE(s) and optionally the timestamp. If the event triggering the notification is DNAI change, the timestamp can be included to indicate the age of the user plane path management event notification information. The EES may only provide part of information included in the user plane path management event notification from 3GPP network (e.g. target DNAI). If the EAS had provided "Indication of EAS acknowledgement", the EES waits for acknowledgement from the EAS before it sends AF acknowledgement to the 3GPP core network. + +If the event is "ACT start/stop", the notification shall include the endpoint address of the other EAS and the UE ID. **Upon receiving the notification about the start of the ACR execution with "ACT start" event, The S-EAS prevents triggering a second ACR execution for the same identity (ACID, EEC ID (or UE ID), S-EAS endpoint and T-EAS endpoint) until the current ACR execution is completed.** + +### 7.38.3 Solution evaluation + +The solution addresses Key issue #19. The solution proposes to coordinate among decision making entities to make sure single ACR remains in execution phase while allowing multiple entities to detect ACR for different scenarios. The solution proposes modify existing ACR scenarios to utilize existing event notifications to S-EAS or EEC at start of the execution phase. The solution also proposes to modify ACR information notification and ACR management event notification procedures. The solution is a viable solution. + +## 7.39 Solution #39: EAS selection synchronization at registration + +### 7.39.1 Architecture enhancements + +None. + +### 7.39.2 Solution description + +#### 7.39.2.1 General + +The following solution addresses Key Issue #8. + +In this solution, the EES leverages pre-existent EAS information at the EEC to enable EAS selection and the synchronization/ alignment of the information about selected EAS(s) between the EEC and EES. This information is provided in the EEC registration request and includes the AC Profiles and an optional list of pre-configured EAS endpoints (e.g. for constrained IoT devices). + +The solution also enables EES to use this information to make a determination of the EASs available for service session communications as soon as the EDN capabilities are available after registration. The EES may then determine whether dynamic EAS instantiation triggering should be performed. The EEC is then provided with EAS information in the registration response. With this solution, ACs can establish communications with the EASs immediately after an initial registration. + +#### 7.39.2.2 Procedure + +The following text captures the solution by describing the necessary 3GPP TS 23.558 changes (relative to v17.1.0 in bold font) as shown below: + +**\*\*\* Enhancement based on TS 23.558 v. 17.4.0 \*\*\*** + +### 8.2.2 AC Profile + +An AC Profile includes information about AC used to determine services and service characteristics required. + +**Table 8.2.2-1: AC Profile** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACID | M | Identity of the AC. | +| AC Type | O | The category or type of AC (e.g. V2X). This is an implementation specific value. | +| Preferred ECSP list | O | When used in a service provisioning request, this IE indicates to the ECS which ECSPs are preferred for the AC. The ECS may use this information in the selection of EESs. | +| AC Schedule | O | The expected operation schedule of the AC (e.g. time windows) | +| Expected AC Geographical Service Area | O | The expected location(s) (e.g. route) of the hosting UE during the AC's operation schedule. This geographic information can express a geographic point, polygon, route, signalling map, or waypoint set. | +| AC Service Continuity Support | O | Indicates if service continuity support is required or not for the application. The IE also indicates which ACR scenarios are supported by the AC and which of these are preferred by the AC. | +| List of EASs | O | List of EAS that serve the AC along with the service KPIs required by the AC | +| > EASID | M | Identifier of the EAS | +| > Selected EAS Endpoint (NOTE) | O | Endpoint information (e.g. URI, FQDN, IP 3-tuple) of a pre-provisioned or EEC selected EAS. | +| > Expected AC Service KPIs | O | KPIs expected in order for ACs to receive currently required services from the EAS, as described in Table 8.2.3-1 | +| > Minimum required AC Service KPIs | O | Minimum KPIs required in order for ACs to receive meaningful services from the EAS, as described in Table 8.2.3-1 | +| NOTE: Endpoint information shall be provided only for pre-provisioned or EEC selected EASs. | | | + +Editor's note: It is FFS whether more information other than Selected EAS endpoint is required and whether a new information table can used to represent it instead of AC profile. + +\*\*\* Enhancement based on TS 23.558 v. 17.4.0 \*\*\* + +##### 8.4.2.2.2 EEC registration + +Figure 8.4.2.2.2-1 illustrates EEC registration procedure. + +Pre-conditions: + +1. The EEC is authorized to access the EES for the purpose of performing registration and has received relevant security credentials as specified in clause 8.11; and +2. The EEC has received service provisioning information from the ECS, including information for accessing the EES. + +![Sequence diagram of the EEC registration procedure. The diagram shows two lifelines: EEC and EES. The sequence of messages is: 1. EEC sends an 'EEC registration request' to EES. 2. EES performs 'Request validation'. 3. EES performs 'Retrieve EEC's Context' (indicated by a dashed box). 4. EES sends an 'EEC registration response' back to EEC.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES + Note right of EES: 2. Request validation + Note right of EES: 3. Retrieve EEC's Context + EEC->>EES: 1. EEC registration request + EES-->>EEC: 4. EEC registration response + +``` + +Sequence diagram of the EEC registration procedure. The diagram shows two lifelines: EEC and EES. The sequence of messages is: 1. EEC sends an 'EEC registration request' to EES. 2. EES performs 'Request validation'. 3. EES performs 'Retrieve EEC's Context' (indicated by a dashed box). 4. EES sends an 'EEC registration response' back to EEC. + +**Figure 8.4.2.2.2-1: EEC registration procedure** + +1. The EEC sends EEC registration request to the EES. The request from the client includes the security credentials received after successful authorization for edge computing services and may include a proposed expiration time. The request also optionally includes information indicating to the EES how the EEC expects to use the services of the EES. + +If the EEC is moving to this EES from the purview of another EES, called S-EES, the request from the EEC may include the identity and endpoint of the S-EES and an EEC context ID that was provided by the S-EES to maintain continuity of the EEC context and to authorize EEC context relocation. If the EEC registration is being performed as part of ACR, the EEC shall not include the S-EES endpoint and the EEC context ID. + +2. Upon receiving the request from the EEC, the EES validates the registration request and verifies the security credentials. The EES further determines whether the requirements that were indicated in the AC Profile(s) can be fulfilled **e.g. without failing to meet the requirements of the already registered EECs**, and reserves corresponding resources **(e.g. for EASs)**. + +**If the EEC provides in the registration request the EAS selection request indicator and based on EES local policies, the EES selects EASs providing the capabilities required by the AC Profile(s), reserves the corresponding resources and provides the information to the EEC in the registration response. If an AC Profile includes the "Selected EAS Endpoint" IE, the AC Profile is ignored in the EAS selection process.** + +**If the EEC provides in the registration request a UE type, the EES may use this information to apply UE-type-specific local policies.** + +**NOTE 1: This functionality is to be aligned with how a "constrained device" is identified by the EES. The alignment is to be determined in the normative phase considering other solutions.** + +**NOTE 2: Without any indication from UE (either EAS selection request indication or UE type), the EES handling is as per R17 procedure.** + +3. Upon successful validation of the request, if the received EEC registration request contains an EEC context ID and a S-EES Endpoint, the EES performs a EEC Context Pull relocation (clause 8.9.2.2) from the S-EES. The source and target EES perform EEC Context handling as detailed in clause 8.9.1. + +**NOTE 3: Only a single EEC Context ID may be provided in the EEC registration request.** + +**NOTE 4: In this version of specification, each registration procedure relocates a single EEC context.** + +**NOTE 5: Step 3 is executed when EEC determines to change its connection from S-EES to T-EES and ACR is not required.** + +If the EEC registration request fails after the EEC Context Pull relocation, e.g. the EES cannot reserve the necessary resources while meeting the capability requirements of the existing registered EECs, the EES shall determine the EEC Context information stale and send a failure response with a corresponding cause. + +- The EES sends a successful EEC registration response, which includes the registration ID and may include a newly assigned EEC context ID. If step 3 was executed, the EEC registration response also includes EEC context retrieval result. The EEC stores the new EEC context ID and uses it if and when it registers with another EES. The EES may also provide an expiration time to indicate to the EEC when the registration will automatically expire. To maintain the registration, the EEC shall send a registration update request prior to the expiration. If a registration update request is not received prior to the expiration time, the EES shall treat the EEC as implicitly de-registered. + +If the EEC context relocation status indicates that the EEC context relocation was not successful, then the EEC performs the required EDGE-1 subscriptions at the T-EES. + +##### 8.4.2.2.3 EEC registration update + +Figure 8.4.2.2.3-1 illustrates EEC registration update procedure. + +Pre-conditions: + +- EEC has already registered with the EES. + +![Sequence diagram illustrating the EEC registration update procedure. The diagram shows two lifelines: EEC and EES. The EEC sends a '1. EEC registration update request' to the EES. The EES performs a '2. Registration update authorization check' (indicated by a self-call). Finally, the EES sends a '3. EEC registration update response' back to the EEC.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES + Note right of EES: 2. Registration update authorization check + EEC->>EES: 1. EEC registration update request + EES->>EEC: 3. EEC registration update response + +``` + +Sequence diagram illustrating the EEC registration update procedure. The diagram shows two lifelines: EEC and EES. The EEC sends a '1. EEC registration update request' to the EES. The EES performs a '2. Registration update authorization check' (indicated by a self-call). Finally, the EES sends a '3. EEC registration update response' back to the EEC. + +Figure 8.4.2.2.3-1: EEC registration update procedure + +- The EEC sends EEC registration update request to the EES. The request from the client includes the security credentials received after successful authorization for edge computing services and may include a proposed expiration time and AC profile(s) **parameters, including new or updated selected EAS information**. +- Upon receiving the request from the EEC, the EES validates the registration update request and verifies the security credentials. +- Upon successful validation of the request, the EES sends a successful registration update response, which may include updated expiration time to indicate to the EEC when the updated registration will automatically expire. To maintain the registration, the EEC shall send a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the EES shall treat the EEC as implicitly de-registered. + +\*\*\* Enhancement based on TS 23.558 v. 17.4.0 \*\*\* + +##### 8.4.2.3.2 EEC registration request + +Table 8.4.2.3.2-1 describes information elements in the EEC registration request from the EEC to the EES. + +**Table 8.4.2.3.2-1: EEC registration request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------| +| EECID | M | Unique identifier of the EEC. | +| UE Identifier | O | The identifier of the hosting UE (i.e. GPSI or identity token) | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| AC Profile(s) | O | Profiles of ACs for which the EEC provides edge enabling services. AC Profiles are further described in Table 8.2.2-1. | +| EEC Service Continuity Support | O | Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC. | +| EAS selection request indicator | O | Indicates the request for EAS selection support from the EES (e.g. for constrained device)". | +| UE type | O | Indicates UE or device type (e.g. constrained device) (NOTE 1) | +| Proposed expiration time | O | Proposed expiration time for the registration. | +| EEC context ID (NOTE 2) | O | Identifier of the EEC context obtained from a previous registration. | +| Source EESID (NOTE 2 ) | O | Identifier of the EES that provided EEC context ID. | +| Source EES Endpoint (NOTE 2) | O | The endpoint address (e.g. URI, IP address) of the EES that provided EEC context ID. | +| NOTE 1: The EES may use this information when applying implementation-dependent policies, such as EAS discovery or EAS selection policies complying to Release-17 specified behaviour. | | | +| NOTE: 2 This IE shall not be present when EEC registration is performed as part of ACR. | | | + +##### 8.4.2.3.3 EEC registration response + +Table 8.4.2.3.3-1 describes information elements in the EEC registration response from the EES to the EEC. + +**Table 8.4.2.3.3-1: EEC registration response** + +| Information element | Status | Description | +|---------------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Successful response | O | Indicates that the registration request was successful. | +| > Registration ID | M | Identifier of the EEC registration. | +| > Expiration time | M | Indicates the expiration time of the registration. To maintain an active registration status, a registration update is required before the expiration time. | +| > EEC context ID | O | Identifier of the EEC Context information available at the EES that performed the registration. | +| > EEC Context Relocation status | O | Indicates whether the EEC context retrieval from the S-EES was successful or not. | +| > Discovered EAS list | O | List of EASs discovered to provide the capabilities required by the AC Profiles. If the request includes the EAS selection request indicator, then Discovered EAS list shall contain only one selected EAS. If the EES selects no EASs, the list may be empty. | +| >> EAS profile | M | Profile of the EAS. Each element is described in clause 8.2.4. Only includes the mandatory IEs in the EAS Profile. | +| Failure response | O | Indicates that the registration request failed. | +| > Cause | M | Provides the cause for registration request failure. | + +\*\*\* End of TS 23.558 enhancements \*\*\* + +### 7.39.3 Solution evaluation + +This solution addresses all KI#8 issues by enabling EECs to obtain EES selection assistance or to leverage pre-existent EAS information at the EEC and to indicate its EAS selection via EEC registration update. In turn, service session communications can be enabled as soon as the EDN capabilities are available after registration and the EES is better enabled to perform optimal EAS instantiation after registration, if needed. + +In addition, the solution addresses KI#15 by minimizing EDGE-1 interactions for EECs for which EAS selection assistance is provided by EEL. + +## 7.40 Solution #40: EAS instantiation status provisioned by ECS + +### 7.40.1 Architecture enhancements + +None. + +### 7.40.2 Solution description + +#### 7.40.2.1 General + +The following solution corresponds to key issue #9 on enhancements of dynamic EAS instantiation triggering. This solution helps ensure that the proper number of EAS instances are instantiated in the EDN and the solution addresses what information may be utilized by an EES to decide to trigger dynamic EAS instantiation. + +In this solution, the EES is configured by the Management Service (MnS) with information on EAS(s) that can be dynamically instantiated in an EDN; this list provides the information elements needed for requesting EAS instantiation. + +This solution updates the EES profile provided to the ECS in the EES registration request and provided to the EEC in the service provisioning response. The EES profile provides the EASID(s) available at the EES and for each EASID an EAS instantiation status indicating whether the EES has the EAS(es) instantiated or instantiable, but not yet instantiated. This information can be used by the EEC when choosing the EES(es) for performing EAS discovery. + +The solution then relies on existing Rel-17 EAS discovery request sent to the selected EES to trigger EAS instantiation if needed. The benefit of this solution is that the EEC can learn the EAS instantiation status at service provisioning time which may influence the EES selection. Rel-17 EAS instantiation methodology is unchanged. + +#### 7.40.2.2 Procedure + +This procedure presents a high-level overview of Solution #40. + +![Sequence diagram illustrating the high-level overview of solution #40. The diagram shows interactions between UE (AC, EEC), EDN (EES, EAS, ECS), and MnS (MnS). The process includes initial deployment, EES registration, service provisioning, EAS discovery, EAS instantiation, and EAS usage.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EDN + participant MnS + + Note right of EDN: EES/EAS initial deployment + Note right of EDN: 1. MnS deploys EES and EAS(es) per initial deployment requirement + Note right of EDN: EES registration + Note right of EDN: 2. EES registers with ECS + Note right of UE: Service provisioning + Note right of UE: 3. EEC performs service provisioning procedure with ECS + Note right of UE: EAS discovery + Note right of UE: 4. EAS discovery request + Note right of EDN: 5. EAS instantiation determination + Note right of EDN: 6. EES invokes MnS for EAS instantiation (if required) + Note right of EDN: 7. EAS registration (on successful instantiation) + Note right of UE: 8. EAS discovery response + Note right of UE: EAS usage + Note right of UE: 9. EAS selection + Note right of UE: 10. AC access selected EAS + +``` + +Sequence diagram illustrating the high-level overview of solution #40. The diagram shows interactions between UE (AC, EEC), EDN (EES, EAS, ECS), and MnS (MnS). The process includes initial deployment, EES registration, service provisioning, EAS discovery, EAS instantiation, and EAS usage. + +**Figure 7.40.2.2-1: High-level overview of solution #40** + +1. On initial deployment, the Management Service (MnS) is requested to perform EES deployment and can additionally be requested to perform initial EAS deployment. Details on requesting EES and EAS instantiation is specified in 3GPP TS 28.538 [20]. + +To support the dynamic EAS instantiation functionality, the EES needs a list of EAS that it is allowed to dynamically instantiate, and corresponding EAS information elements needed for requesting EAS instantiation. + +NOTE 1: How the dynamic EAS instantiation information is made available to the EES is implementation specific in Rel-17 and in the scope of SA5 for Rel-18. + +2. The EES registers to the ECS following the procedures described in 3GPP TS 23.558 [2] clause 8.4.4. The EES profile included in the EES registration request may include the EAS instantiation status of each EASIDs, indicating whether each EASID available at the EES is instantiated or instantiable, but not yet instantiated. +3. The EEC performs the service provisioning following the procedures described in 3GPP TS 23.558 [2] clause 8.3.3. +4. When the AC requests application server access, if the EES profile(s) include EAS instantiation status, the EEC can select one or more EES(s) for EAS discovery considering the EAS instantiation status. The EAS discovery procedure is unchanged from 3GPP TS 23.558 [2] clause 8.5. To mitigate the waste of EDN resources, the EEC can select one EES for EAS discovery considering the EAS instantiation status. + +NOTE 2: The EEC can select one EES from the EES list, if the EAS instantiation status corresponding to the EASID requested by AC/EEC is instantiable (but not yet instantiated) + +NOTE 3: The EEC may prefer to select EES(s) for EAS discovery with EAS already instantiated over other EES(s) with uninstantiated EAS, based on EAS instantiation status per EAS ID. + +5. The EAS discovery request triggers the EES to verify if the instantiation of the EAS indicated in the request is required per 3GPP TS 23.558 [2] clause 8.12.1. +6. If the EES determines that EAS instantiation is needed, the EES may request the MnS to perform EAS instantiation for the selected EAS. Upon reception of the EAS instantiation request, MnS verifies EAS instantiation requirements and performs EAS instantiation as specified in 3GPP TS 28.538 [20]. + +Upon instantiation of the EAS by the MnS, the EES is informed by MnS of the result of EAS instantiation. + +NOTE 3: The instantiated EAS can be discovered by other EECs and used by other ACs. + +7. Step 7 happens only if EAS instantiation triggered in step 6 was successful. At start-up, the newly instantiated EAS registers to the EES following procedures described in 3GPP TS 23.558 [2] clause 8.4.3. +8. Using the EAS instantiation result received from the MnS in step 6 and the registration information provided at EAS registration in step 7; the EES sends the EAS discovery response to the EEC to provide EAS connectivity information. + +If the EAS instantiation result received from the MnS in step 6 indicates failure, the EES shall reject the EAS discovery request and respond with an appropriate failure cause. + +9. If the EAS discovery succeeded, the EEC performs EAS selection and informs the AC of the selected EAS; otherwise, the EEC may retry the EAS discovery taking into account the received failure cause. +10. The AC accesses the selected EAS. + +### 7.40.3 Solution evaluation + +Solution evaluation of Solution #40: + +- a) Enables the EES to inform the ECS at EES registration about available EASID(s), including the instantiated and instantiable EAS(es). During service provisioning, this allows the EEC to retrieve the EAS instantiation status at EES(es). +- b) Enables an EEC to use the EAS instantiation status when selecting EES(es) prior to performing EAS discovery, this allows to keep instantiated EAS to a minimum. +- c) Enables the EES to evaluate if EAS instantiation is needed upon receiving the EAS discovery request. This allows the EES to evaluate if an EAS has become available, and otherwise trigger EAS instantiation only if needed. + +## 7.41 Solution #41: Interaction with ADAES for edge load analytics + +### 7.41.1 Architecture enhancements + +None + +### 7.41.2 Solution description + +#### 7.41.2.1 General + +The following solution corresponds to the key issue #24 on SEAL capability access for EEL support. + +#### 7.41.2.2 Procedure + +FS\_ADAES (TR 23.700-36) is discussing edge load analytics service to provide insight on the operation and performance of an EDN and in particular statistics or prediction on parameters related to the EAS / EES load for one or more EAS/EES. + +Such analytics can improve edge support services by allowing the pro-active edge service operation changes to deal with possible edge overload scenarios. For example, this can trigger EAS migration to a different EDN / central DN, or pro-active EAS reselection for a target UE or group of UEs. + +Some EEL services may benefit from using ADAES analytics related to the EDN or EAS service load. In TS 23.558, one of the conditions for service continuity is the EAS/EDN overload situations. In this direction, edge load analytics (predictions, stats) may help pro-actively trigger actions to prevent loss of service due to expected overload. + +Pre-condition: + +- 1) SEAL ADAES services are available at the edge data network and accessible to the EES. + +![Sequence diagram showing the interaction between EAS, EES, and ADAES for edge load analytics. The sequence starts with EES sending a subscription for edge load analytics to ADAES. ADAES responds with edge load analytics derivation and notification to EES. EES then sends an edge load analytics notify to EAS. Finally, EES generates a trigger for EAS/EDN overload based on the service continuity scenario.](a6cf7c02a60c336e0934b5ea40e35b49_img.jpg) + +``` + +sequenceDiagram + participant EAS + participant EES + participant ADAES + Note right of EES: 1. subscription for edge load analytics + EES->>ADAES: 1. subscription for edge load analytics + Note right of ADAES: 2. edge load analytics derivation and notification + ADAES->>EES: 2. edge load analytics derivation and notification + Note right of EES: 3. edge load analytics notify + EES->>EAS: 3. edge load analytics notify + Note right of EES: 4. Generate a trigger for EAS/EDN overload (based on the service continuity scenario) + +``` + +Sequence diagram showing the interaction between EAS, EES, and ADAES for edge load analytics. The sequence starts with EES sending a subscription for edge load analytics to ADAES. ADAES responds with edge load analytics derivation and notification to EES. EES then sends an edge load analytics notify to EAS. Finally, EES generates a trigger for EAS/EDN overload based on the service continuity scenario. + +**Figure 7.41.2.2-1 interaction with ADAES for edge load analytics** + +- 1) The EES subscribes to ADAES (as described in TR 23.700-36 steps 1, 2 in procedure in clause 6.4.1). +- 2) The ADAES derives analytics for the edge load using also offline stats from A-ADRF and edge platform load data (as indicated in TR 23.700-36 6.4.1 step 9) and sends the derived analytics output to the requestor EES (as indicated in TR 23.700-36 6.4.1 step 10). +- 3) The EES can optionally provide the edge load analytics related to the EAS load. + +- 4) The EES or EAS generates a trigger event indicating a predicted or expected EES/EAS overload and a possible action which can be the ACR detection. Such step can be either performed at EAS or EES depending on the service continuity scenario (as captured in clauses 8.8.2.4 and 8.8.2.5 of TS 23.558). It shall be noted that the entity (EAS or EES) that indicates EAS or EES expected overload based on the received load analytics shall be responsible for triggering the action (e.g. ACRs). + +### 7.41.3 Solution evaluation + +This solution provides the procedures to utilize ADAES for enhancing EEL operations based on edge load analytics. It addresses the key issue #24 and the solution feasibility is dependent on the conclusion of the edge load analytics capability in FS\_ADAES (TR 23.700-36) and its specification in SEAL. + +## 7.42 Solution #42: EAS selection and instantiation in EES + +### 7.42.1 Architecture enhancements + +None. + +### 7.42.2 Solution description + +This solution is based on solution #18, with UE type (e.g. constraint device), the EES triggers EAS selection and instantiation for the AC. + +This solution also uses the same principle of instantiable EAS configuration in the EES (provisioned by MnS) as in solution #33. + +Below procedure presents a high-level overview of this solution. + +![Sequence diagram showing the high-level overview of solution #42. Lifelines: UE (AC, EEC), EDN (EES, EAS, ECS), and MnS. The sequence includes: 1. MnS deploys EES and EAS(es) per initial deployment requirement; 2. EES registers with ECS; 3. EEC performs service provisioning procedure with ECS; 4. EEC performs EAS discovery with EES; 5. EAS selection; 6. EES invokes MnS for EAS instantiation (if required); 7. EAS registration (on successful instantiation); 8. EES sends back selected EAS; 9. AC access selected EAS.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE + participant EDN + participant MnS + Note right of EDN: EES/EAS initial deployment + Note right of EDN: 1. MnS deploys EES and EAS(es) per initial deployment requirement + Note right of EDN: EES registration + Note right of EDN: 2. EES registers with ECS + Note right of UE: Service provisioning + Note right of UE: 3. EEC performs service provisioning procedure with ECS + Note right of UE: EAS discovery and selection + Note right of UE: 4. EEC performs EAS discovery with EES + Note right of EDN: 5. EAS selection + Note right of EDN: 6. EES invokes MnS for EAS instantiation (if required) + Note right of EDN: 7. EAS registration (on successful instantiation) + Note right of EDN: 8. EES sends back selected EAS + Note right of UE: EAS usage + Note right of UE: 9. AC access selected EAS + +``` + +Sequence diagram showing the high-level overview of solution #42. Lifelines: UE (AC, EEC), EDN (EES, EAS, ECS), and MnS. The sequence includes: 1. MnS deploys EES and EAS(es) per initial deployment requirement; 2. EES registers with ECS; 3. EEC performs service provisioning procedure with ECS; 4. EEC performs EAS discovery with EES; 5. EAS selection; 6. EES invokes MnS for EAS instantiation (if required); 7. EAS registration (on successful instantiation); 8. EES sends back selected EAS; 9. AC access selected EAS. + +**Figure 7.42.2-1: High-level overview of solution #42** + +- 1-3. Same as solution #33, procedure part step 1 to 3. +4. Same as solution #18, step 2 in procedure part. +5. EES selects an appropriate EAS from the instantiable list. If there is already instantiated EAS in EES satisfying AC requirement, EES proceeds with step 8. +- 6-7. Same as solution #33, procedure part step 7 to 8. +8. Same as solution #18, step 3 in procedure part. In case of EAS instantiation failure or no matched instantiable EAS can be found, the EEC repeats step 4 with another EES. +9. AC connects to the selected EAS. + +### 7.42.3 Solution evaluation + +During the EAS discovery, the EES selects and requests MnS to instantiate an EAS based on the following info: + +- Instantiable EAS information provisioned by MnS; +- UE type (e.g. constraint device) sent from the EEC.; and +- AC requirement. + +This solution improves the dynamic EAS instantiation and addresses open issues in KI #9. + +NOTE: This solution utilizes the UE type as described in solution #18 and the EAS instantiation is done during EAS discovery. + +## 7.43 Solution #43: EAS discovery for Edge node sharing + +### 7.43.1 Architecture enhancements + +This solution uses the architecture option specified in clause 6.10. + +### 7.43.2 Solution description + +#### 7.43.2.1 General + +As specified in clause 3.5.4.3.3 of GSMA OPG.02 [4], Edge node sharing is a scenario wherein an OP, when serving the UNI requests originating from (its own) UCs (i.e. EEC in EDGEAPP term), decides to provide the application from the Edge nodes of a partner OP. + +Scenario is that the EEC in UE does not have access directly to enabler/configuration server in the OP-A (e.g. the EEC is not authorized to access ECS and EES in OP-A, or there is no connectivity between the EEC and OP-A), the OP-B has SLA with OP-A and servers in OP-B can serve the EEC directly (e.g. the EEC has connectivity with OP-B and is authorized to access ECS and EES in OP-B). For the AC in UE, it can access EAS(s) deployed in OP-A. + +Assumption is that OP-B's EESs are deployed everywhere in a region (possibly utilizing/leasing the IaaS offered by partners) and the EAS can be shared to both OP A and OP B. + +**Editor's note:** The scenario assumption in this solution needs to be verified with GSMA before considering this solution in conclusion. + +For the case where there are several partner EDNs coverage for the current UE location and the contracted OP for the EEC cannot provide a desired EAS in its EDN, this solution offers an option so that the EEC contracted OP can use its partner's OP to discover the desired EAS in the partner's EDN for the UE. + +#### 7.43.2.2 Publish/unpublish and fetch application + +It is assumed that EAS deployed in OP-A is shared with OP-B (i.e. ECS-ER of OP-A can share EAS information and associated EES information with ECS-ER of OP-B) in this clause. + +Since the application instance is deployed in the partner's data network, when the leading OP (OP-B) receives a request from the UC, the leading OP (OP-B) needs to contact the partner OP (OP-A) to discover the application instance. In EDGEAPP architecture, the EES, ECS and ECS-ER are entities within the OP. This clause provides ways for the leading OP to discover adequate EES(s) of the partner OP for subsequent communication with the partner OP's EES. + +![Sequence diagram showing publish and unpublish application information between ECS via ECS-ER. Lifelines: ECS (OP-B), ECS-ER (OP-B), ECS-ER (OP-A), ECS (OP-A), EES (OP-A).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant ECS-OP-A as ECS (OP-A) + participant EES-OP-A as EES (OP-A) + participant ECS-OP-B as ECS (OP-B) + participant ECS-ER-OP-A as ECS-ER (OP-A) + participant ECS-ER-OP-B as ECS-ER (OP-B) + + Note right of ECS-OP-A: 1. EES registration + ECS-OP-A->>ECS-ER-OP-A: 2. Application info publish request (EAS ID list, [EES info of OP-A]) + ECS-ER-OP-A-->>ECS-ER-OP-B: 2. Application info publish request (EAS ID list, [EES info of OP-A]) + ECS-ER-OP-B-->>ECS-OP-B: 3. Application info publish response + Note right of EES-OP-A: 4. EES registration update + ECS-OP-A->>ECS-ER-OP-A: 5. Application info publish update request (EAS ID list and/or EES info of OP-A) + ECS-ER-OP-A-->>ECS-ER-OP-B: 5. Application info publish update request (EAS ID list and/or EES info of OP-A) + ECS-ER-OP-B-->>ECS-OP-B: 6. Application info publish update response + Note right of EES-OP-A: 7. EES de-registration + ECS-OP-A->>ECS-ER-OP-A: 8. Application info unpublish request + ECS-ER-OP-A-->>ECS-ER-OP-B: 8. Application info unpublish request + ECS-ER-OP-B-->>ECS-OP-B: 9. Application info unpublish response + +``` + +Sequence diagram showing publish and unpublish application information between ECS via ECS-ER. Lifelines: ECS (OP-B), ECS-ER (OP-B), ECS-ER (OP-A), ECS (OP-A), EES (OP-A). + +**Figure 7.43.2.2-1: publish and unpublish application information between ECS via ECS-ER** + +In step 1, the EES of OP-A is registered in ECS of OP-A over EDGE-6 reference point. Based on the information sharing policy in the ECS of OP-A, the ECS of OP-A sends Application info publish request with a list of EAS IDs and optionally EES information of OP-A in step 2. The EES information of OP-A includes EES endpoint and may include EES provider ID, EES service area and/or EES Service continuity support. Then ECS of OP-B stores the received information and responds with Application info publish response in step 3. Step 2 and 3 are sent via corresponding ECS-ERs (ECS-ER (OP-A) and ECS-ER (OP-B)). + +The ECS of OP-A may receive EES registration update from the EES of OP-A in step 4, then the ECS of OP-A updates the previously published information (EAS ID list and/or EES info of OP-A) towards the ECS of OP-B in step 5. The ECS of OP-B updates the previously stored information and responds with Application info publish update response in step 6. Step 5 and 6 are sent via corresponding ECS-ERs (ECS-ER (OP-A) and ECS-ER (OP-B)). + +The ECS of OP-A may receive EES de-registration from the EES of OP-A in step 7, then the ECS of OP-A requests to remove all previously published information towards the ECS of OP-B in step 8. The ECS of OP-B removes all previously stored information and responds with Application info unpublish response in step 9. Step 8 and 9 are sent via corresponding ECS-ERs (ECS-ER (OP-A) and ECS-ER (OP-B)). + +NOTE 1: The application information published/shared to OP-B can also be done in a notification message under subscribe-notify communication model. + +![Sequence diagram for Figure 7.43.2.2-2: Fetch application information from partner. Lifelines: ECS (OP-B), ECS-ER (OP-B), ECS-ER (OP-A), ECS (OP-A). The sequence shows a request from ECS (OP-B) to ECS (OP-A) via ECS-ER (OP-B) and ECS-ER (OP-A), and a response back from ECS (OP-A) via ECS-ER (OP-A) and ECS-ER (OP-B) to ECS (OP-B).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant ECS as ECS (OP-B) + participant ECS_ER_B as ECS-ER (OP-B) + participant ECS_ER_A as ECS-ER (OP-A) + participant ECS_A as ECS (OP-A) + Note right of ECS: 1. Fetch application info request + ECS->>ECS_A: 1. Fetch application info request + Note right of ECS_A: 2. Fetch application info response + ECS_A-->>ECS: 2. Fetch application info response + +``` + +Sequence diagram for Figure 7.43.2.2-2: Fetch application information from partner. Lifelines: ECS (OP-B), ECS-ER (OP-B), ECS-ER (OP-A), ECS (OP-A). The sequence shows a request from ECS (OP-B) to ECS (OP-A) via ECS-ER (OP-B) and ECS-ER (OP-A), and a response back from ECS (OP-A) via ECS-ER (OP-A) and ECS-ER (OP-B) to ECS (OP-B). + +**Figure 7.43.2.2-2: Fetch application information from partner** + +The ECS (OP-B) may fetch application information from its partner OP (e.g. OP-A) via corresponding ECS-ERs (ECS-ER (OP-A) and ECS-ER (OP-B)) as shown in figure 7.43.2.2-2, periodically. In such a fetch operation, the fetched information includes a list of EAS IDs and EES information of OP-A. + +NOTE 2: If the ECS (OP-B) does not receive EES information of OP-A from the published/notified application information, the ECS (OP-B) can also fetch it from the ECS (OP-A) via the fetch operation. + +NOTE 3: Procedures in this clause is applicable when leading OP's OAM provisioned application sharing info (EAS IDs and EES info) of OP partners is not available in ECS. + +NOTE 4: ECS (OP-B) can also subscribe to application info changes from ECS (OP-A). + +NOTE 5: For message name "application info publish" and "Fetch application info", whether alternate name should be used can be decided in normative work. + +#### 7.43.2.3 EAS discovery without published application info + +It is assumed that EAS deployed in OP-A is shared with OP-B (i.e. EES of OP-A can share EAS information with EES of OP-B) in this clause. + +This procedure is applicable for EAS discovery without published application information between ECSs as described in clause 7.43.2.2. + +![Sequence diagram for Figure 7.43.2.3-1: EAS discovery for edge node sharing, without published application info. Lifelines: EEC, ECS (OP-B), ECS (OP-A), EES (OP-B), EES (OP-A), EAS. The sequence starts with a service provisioning request from EEC to ECS (OP-B), followed by internal steps in ECS (OP-B) to determine edge node sharing and discover T-EES. Then, a service provisioning response is sent from ECS (OP-B) to EEC. Next, an EAS discovery request is sent from ECS (OP-B) to EES (OP-B), which is then forwarded to EES (OP-A) by EES (OP-B). EES (OP-A) sends an EAS discovery response back to EES (OP-B), which then forwards it to ECS (OP-B), which finally sends an EAS discovery response to EEC. A dashed box labeled '0. EAS registration' is shown between EES (OP-A) and EAS.](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS_B as ECS (OP-B) + participant ECS_A as ECS (OP-A) + participant EES_B as EES (OP-B) + participant EES_A as EES (OP-A) + participant EAS + Note right of EEC: 1. Service provisioning request + EEC->>ECS_B: 1. Service provisioning request + Note right of ECS_B: 2. Determines edge node sharing + ECS_B->>ECS_A: 3. Discovers T-EES + Note right of ECS_B: 4. Service provisioning response + ECS_B-->>EEC: 4. Service provisioning response + Note right of ECS_B: 5. EAS discovery request + ECS_B->>EES_B: 5. EAS discovery request + Note right of EES_B: 6. EAS discovery request + EES_B->>EES_A: 6. EAS discovery request + Note right of EES_A: 7. EAS discovery response + EES_A-->>EES_B: 7. EAS discovery response + Note right of EES_B: 8. EAS discovery response + EES_B-->>ECS_B: 8. EAS discovery response + ECS_B-->>EEC: 8. EAS discovery response + Note right of EES_A: 0. EAS registration + EES_A-->>EAS: 0. EAS registration + +``` + +Sequence diagram for Figure 7.43.2.3-1: EAS discovery for edge node sharing, without published application info. Lifelines: EEC, ECS (OP-B), ECS (OP-A), EES (OP-B), EES (OP-A), EAS. The sequence starts with a service provisioning request from EEC to ECS (OP-B), followed by internal steps in ECS (OP-B) to determine edge node sharing and discover T-EES. Then, a service provisioning response is sent from ECS (OP-B) to EEC. Next, an EAS discovery request is sent from ECS (OP-B) to EES (OP-B), which is then forwarded to EES (OP-A) by EES (OP-B). EES (OP-A) sends an EAS discovery response back to EES (OP-B), which then forwards it to ECS (OP-B), which finally sends an EAS discovery response to EEC. A dashed box labeled '0. EAS registration' is shown between EES (OP-A) and EAS. + +**Figure 7.43.2.3-1: EAS discovery for edge node sharing, without published application info** + +In step 0, the EAS may be registered in EES of OP-A over EDGE-3 reference point. + +NOTE 0: The EES (OP-A) also registers into the ECS (OP-A) via EDGE-6 reference point, which is not shown for simplicity. + +In step 1, the service provisioning request happens over EDGE-4 reference point. + +In step 2, the ECS (OP-B) cannot find any desired EAS ID in the EES profile being registered so it determines to use edge service from its partner OP-A. + +In step 3, based on SLA between OPs, the T-EES discovery procedure happens as described in step 3 of solution#5 via EDGE-10 reference point. + +NOTE 1: The ECS (OP-B) can have SLA with other multiple OPs and need to repeat step 3 with more than one partner OP in order to discover T-EES. + +In step 4, the service provisioning response includes the EES (OP-A) endpoint and the ECS (OP-B) determined EES (OP-B) endpoint. The endpoint of EES (OP-B) is determined based on SLA with OP-A so that any EES (OP-B) can be authorized by the EES (OP-A). The endpoint of EES (OP-A) is sent by EES in a way that is transparent to EEC. + +In step 5, the EEC sends EAS discovery request to EES (OP-B) over EDGE-1 reference point and include the endpoint of EES (OP-A) in the request. The endpoint of EES (OP-A) is transferred between the ECS (OP-B) and the EES (OP-B) transparently to the EEC. + +NOTE 2: How the EES (OP-A) endpoint is transferred in a transparent way to EEC between the ECS (OP-B) and the EES (OP-B) is in the scope of SA3. + +In step 6, the EES (OP-B) validates the edge service SLA and sends EAS discovery request over EDGE-9 reference point to the EES (OP-A). + +In step 7, the EES (OP-A) validates the edge service SLA and returns EAS discovery response including the discovered candidate EAS(s) to the EES (OP-B). + +In step 8, the EEC receives the EAS discovery response sent by the EES (OP-B). The EEC may select an EAS for the AC. + +#### 7.43.2.4 EAS discovery with published application info + +It is assumed that EAS deployed in OP-A is shared with OP-B (i.e. EES of OP-A can share EAS information with EES of OP-B) in this clause. + +This procedure is applicable for EAS discovery with published application information between ECSs as described in clause 7.43.2.2. + +![Sequence diagram for EAS discovery for edge node sharing, with published application info. Lifelines: EEC, ECS (OP-B), ECS (OP-A), EES (OP-B), EES (OP-A), EAS. The process involves service provisioning, EAS discovery requests, and responses between these entities.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS as ECS (OP-B) + participant ECA as ECS (OP-A) + participant EEB as EES (OP-B) + participant EEA as EES (OP-A) + participant EAS + + Note right of EEA: 0. EAS registration + EEC->>ECS: 1. Service provisioning request + Note right of ECS: 2. Determines edge node sharing + ECS-->>EEC: 3. Service provisioning response + EEC->>EES: 4. EAS discovery request + Note right of EES: 5. Determines edge node sharing + EES->>ECS: 6. Retrieve EES request + Note right of ECS: 7. Discovers T-EES + ECS-->>EES: 8. Retrieve EES response + EES->>EEA: 9. EAS discovery request + EEA-->>EES: 10. EAS discovery response + EES-->>EEC: 11. EAS discovery response + +``` + +Sequence diagram for EAS discovery for edge node sharing, with published application info. Lifelines: EEC, ECS (OP-B), ECS (OP-A), EES (OP-B), EES (OP-A), EAS. The process involves service provisioning, EAS discovery requests, and responses between these entities. + +**Figure 7.43.2.4-1: EAS discovery for edge node sharing, with published application info** + +In step 0, the EAS may be registered in EES of OP-A over EDGE-3 reference point. + +NOTE 1: The EES (OP-A) also registers into the ECS (OP-A) via EDGE-6 reference point, which is not shown for simplicity. + +In step 1, the service provisioning request happens over EDGE-4 reference point. + +In step 2, the ECS (OP-B) cannot find any desired EAS ID in the EES profile being registered so it determines to use edge node sharing service from its partner OP-A based on its partner's published application information. + +NOTE 2: Step 1 to 3 are optional since EEC may cache the result from the initial service provisioning as described in Rel-17. + +In step 3, the service provisioning response includes the ECS (OP-B) determined EES (OP-B) endpoint. The endpoint of EES (OP-B) is determined based on SLA with OP-A so that any EES (OP-B) can be authorized by the EES (OP-A). + +In step 4, the EEC sends EAS discovery request to EES (OP-B) over EDGE-1 reference point. + +In step 5, since step 4 EAS discovery request doesn't include any additional information about the determination of using edge node sharing in step 2, the EES (OP-B) executes the Rel-17 handling for EAS discovery but cannot find any EAS profile being registered so it determines to use edge node sharing service based on edge service SLA. + +In step 6, the EES (OP-B) sends Retrieve EES request over EDGE-6 reference point to the ECS (OP-B). The request may include an edge node sharing flag indicating edge node sharing is requested so that the ECS (OP-B) can skip checking T-EES(s) registered in the ECS (OP-B). + +For the received EAS ID, since the ECS (OP-B) has EES information that was published by partner OP, the ECS (OP-B) discovers T-EES (i.e. EES(s) from partner) in step 7 and returns discovered EES(s) of OP-A in the Retrieve EES response to the ECS (OP-B) in step 8. + +NOTE 3: The published information shared by the OP partner can be provisioned by OAM of the leading OP. + +In step 9 and 10, the EAS discovery procedure happens over EDGE-9 reference point, which is triggered by the EES (OP-B) and the EES (OP-B) receives the discovered candidate EAS(s). + +NOTE 4: The OP-B can have SLA with other multiple OPs so that step 9 can be executed with more than one partner OP in order to discover candidate EAS(s). + +Finally, the EEC receives the EAS discovery response sent by the EES (OP-B) in step 11. The EEC may select an EAS for the AC. + +### 7.43.3 Solution evaluation + +This solution addresses KI#22 for the EAS discovery in edge node sharing case. + +If the application information is not shared between the ECS of two OPs having partnership, during service provisioning, the partner (i.e. OP-A) EES is provided then EEC triggers EAS discovery towards the EES of the contracted OP (i.e. OP-B) in order to obtain EAS information. Any partner information is transparent to the EEC so that the EEC is not aware of the presence of Partner OP (i.e. OP-A). + +If the application information is shared between the ECS of two OPs having partnership, during service provisioning, the EEC obtains an EES (OP-B) from its OP (i.e. OP-B) and triggers EAS discovery toward the EES (OP-B), then the EES (OP-B) further obtains EESs of a partner OP (OP-A) from its registered ECS (OP-B), continues EAS discovery towards partner OP and returns the discovered EASs to the EEC. + +This solution also addresses KI#6 for Edge services support across ECSPs, specifically the open issue about how the ECS can discover a T-EES having SLA with S-EES based on the federation agreements between ECSPs before EDGE-9 interaction. + +**Editor's note:** Further updates to solution and solution evaluation may be needed which is FFS, e.g. whether ECS-ER is needed to convey the shared application info and if needed whether ECS-ER communication between OPs can be mapped to E/WBI in GSMA OPG. + +## 7.44 Solution #44: EAS discovery for Edge node sharing + +### 7.44.1 Architecture enhancements + +This solution uses the architecture option specified in clause 6.12. + +### 7.44.2 Solution description + +#### 7.44.2.1 General + +This procedure works for a solution assumption, where EES of OP-B is available in the region however the required application is not available/registered with OP-B. In such case, the EES (OP-B) interacts with EES (OP-A) where the application is deployed and shared. The EES (OP-B) provides EASID and EAS Geographical Service) of the discovered EAS to EEC. The EAS can be shared to both OP A and OP B. + +**Editor's note:** The scenario assumption in this solution needs to be verified with GSMA before considering this solution in conclusion. + +#### 7.44.2.2 Publish/unpublish and fetch application + +Since the application instance is deployed in the partner's data network, when the leading OP (OP-B) receives a request from the UC, the leading OP (OP-B) needs to contact the partner OP (OP-A) to discover the application. In EDGEAPP architecture, the EES and ECS are entities within the OP. This clause provides ways for the leading OP to discover EAS of the partner OP for subsequent communication. + +![Sequence diagram showing the interaction between Edge Repository (Designated ECS of OP-B), EES (of OP-B), and EAS-1..n for publishing and unpublishing application information. The sequence starts with EAS registration (step 0) from EAS-1..n to EES. Then, EES sends a publish/unpublish request (step 1) to the Edge Repository. The Edge Repository authorizes the request (step 2) and sends a response (step 2) back to EES.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant ER as Edge Repository (Designated ECS of OP-B) + participant EES as EES (of OP-B) + participant EAS as EAS-1..n + + Note right of EAS: 0) EASs registration as defined in TS 23.558, and determine if EAS is shared with other OP(s) + EAS->>EES: + Note right of EES: 1) Registered EAS Publish Request or Registered EAS Unpublish Request + EES->>ER: + Note left of ER: 2) Authorize the request + ER->>EES: 2) Registered EAS Publish Response or Registered EAS Unpublish Response + +``` + +Sequence diagram showing the interaction between Edge Repository (Designated ECS of OP-B), EES (of OP-B), and EAS-1..n for publishing and unpublishing application information. The sequence starts with EAS registration (step 0) from EAS-1..n to EES. Then, EES sends a publish/unpublish request (step 1) to the Edge Repository. The Edge Repository authorizes the request (step 2) and sends a response (step 2) back to EES. + +**Figure 7.44.2.2-1: publish and unpublish application information between ECS** + +- 0) Once EAS(s) are instantiated in OP-B, the EAS(s) are registered with EES (of OP-B). Upon EAS registration, the EES determines whether the registered EAS is to be shared with other OP(s) or not. +- 1) Based on service level agreement between ECSP-A and ECSP-B if EAS is shared to ECSP-A and also based on EAS registration status, the EES (of OP-B) sends registered EAS information publish or unpublish request to an Edge repository (designated ECS of OP-B). The request includes the registered and allowed EAS for sharing between ECSP-1 and ECSP-2, EASID and EAS Geographical Service. +- 2) The Edge repository checks whether EES is authorized to publish or unpublish registered EAS list or not based on service level agreement. +- 3) If authorized, the Edge repository stores the EAS information and sends registered EAS information publish or unpublish response. + +Editor's note: It is FFS whether registered EAS publish should to be done by EES or ECS to ECS-ER. + +Editor's note: Comparison/alignment of ECS-ER's definition with the MEC Federator (MEF) and the interface required between the ECS-ERs with ETSI MEC (e.g. ETSI MEC GS 040) and GSMA OPG's PRD is FFS. + +![Sequence diagram showing the publish and unpublish application information between two Edge Repositories (OP-A and OP-B).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant ER_A as Edge Repository (Designated ECS of OP-A) + participant ER_B as Edge Repository (Designated ECS of OP-B) + Note right of ER_B: 2) Authorize the request + Note right of ER_B: 4) EASs information updated + ER_A->>ER_B: 1) Registered EAS Information Subscribe Request + ER_B-->>ER_A: 3) Registered EAS Information Subscribe Response + ER_B-->>ER_A: 5) Registered EAS Information Notification + +``` + +The diagram illustrates the interaction between two Edge Repositories, ER\_A (Designated ECS of OP-A) and ER\_B (Designated ECS of OP-B). The sequence of messages is as follows: + + +- ER\_A sends a "1) Registered EAS Information Subscribe Request" to ER\_B. +- ER\_B receives the request and performs an internal authorization step ("2) Authorize the request"). +- ER\_B sends a "3) Registered EAS Information Subscribe Response" back to ER\_A. +- ER\_B performs an internal update step ("4) EASs information updated"). +- ER\_B sends a "5) Registered EAS Information Notification" to ER\_A. + +Sequence diagram showing the publish and unpublish application information between two Edge Repositories (OP-A and OP-B). + +**Figure 7.44.2.2-2: publish and unpublish application information between ECS** + +- 1) Based on service level agreement between ECSP-1 and ECSP-2, the Edge repository of OP-A (i.e. designated ECS of OP-A) sends subscription request to receive registered EAS information (including service area) to Edge repository of OP-B (i.e. designated ECS of OP-B). The request includes required parameters like ECSP identifier, ECS identifier and security parameters. +- 2) Upon receiving the request from Edge repository (of OP-A), the Edge repository (of OP-B) checks whether Edge repository (of OP-A) is authorized to receive registered EAS list or not based on service level agreement. +- 3) The Edge repository (of OP-B) sends subscription response – which indicates result of the subscription (success or failure) and subscription identity (if the result is success). +- 4) The list of registered and allowed EAS is changed on the Edge repository (of OP-B) – that is either new EAS is registered or EAS registration is updated or EAS is deregistered or new EAS is published or already published EAS is unpublished. +- 5) The Edge repository (of OP-B) sends notification to the Edge repository (of OP-A). The notification includes the registered and allowed EAS for edge node sharing service between ECSP-1 and ECSP-2, EASID and EAS Geographical Service. Upon receiving the notification, the Edge repository (of OP-A) stores the information to be used in other procedures (for EAS discovery or get registered EAS information request). + +![Sequence diagram showing the process of getting registered EAS information between two Edge Repositories (OP-A and OP-B).](171115f072e42b379238ed0dd438e9d7_img.jpg) + +``` + +sequenceDiagram + participant ER_A as Edge Repository (Designated ECS of OP-A) + participant ER_B as Edge Repository (Designated ECS of OP-B) + Note right of ER_B: 2) Authorize the request + ER_A->>ER_B: 1) Registered EAS Information Request + ER_B-->>ER_A: 3) Registered EAS Information Response + +``` + +The diagram illustrates the interaction between two Edge Repositories, ER\_A (Designated ECS of OP-A) and ER\_B (Designated ECS of OP-B). The sequence of messages is as follows: + + +- ER\_A sends a "1) Registered EAS Information Request" to ER\_B. +- ER\_B receives the request and performs an internal authorization step ("2) Authorize the request"). +- ER\_B sends a "3) Registered EAS Information Response" back to ER\_A. + +Sequence diagram showing the process of getting registered EAS information between two Edge Repositories (OP-A and OP-B). + +**Figure 7.44.2.2-3: Getting registered EAS information** + +The ECS (OP-A) may fetch application information from its partner OP (e.g. OP-B) as shown in figure 7.44.2.2-3, periodically. In such a fetch operation, the response from ECS-ER (of OP-B) includes a list of EAS IDs (which are registered within OP-A and shared to OP-B) and EES information of OP-B. + +NOTE 2: If the ECS (OP-B) does not receive EES information of OP-A from the published/notified application information, the ECS (OP-B) can also fetch it from the ECS (OP-A) via the fetch operation. + +NOTE 3: Procedures in this clause is applicable when leading OP's OAM provisioned application sharing info (EAS IDs and EES info) of OP partners is not available in ECS. + +#### 7.44.2.3 EAS discovery for edge node sharing Procedure + +Figure 7.44.2.3-1 illustrates the procedure for EAS discovery for Edge Node Sharing scenario, where the EES-B requests list of all registered EASs from partner OP's EES-A or perform EAS discovery based on the discovery filters provided by the EEC. + +Pre-conditions: + +1. ECSP-1 and ECSP-2 have a service level agreement to share edge services. + +![Sequence diagram for EAS discovery for edge node sharing. Lifelines: EEC, EES-B, ECS-B, EES-A, EAS-1..n. The sequence starts with EES-A and EAS-1..n performing registration (1). Then EEC performs service provisioning (2) and registration (3). EEC sends an EAS Discovery request (4) to EES-B. EES-B sends an EAS Discovery Request (5) to EES-A. EES-A returns an EAS Discovery Response (6) to EES-B. Finally, EES-B returns an EAS Discovery response (7) to EEC.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES-B + participant ECS-B + participant EES-A + participant EAS-1..n + + Note right of EES-A: 1) EASs registration as defined in TS 23.558 + Note left of ECS-B: 2) EEC performs Service provisioning + Note left of EES-B: 3) EEC Registration + EEC->>EES-B: 4) EAS Discovery request + EES-B->>EES-A: 5) EAS Discovery Request + EES-A-->>EES-B: 6) EAS Discovery Response + EES-B-->>EEC: 7) EAS Discovery response + +``` + +Sequence diagram for EAS discovery for edge node sharing. Lifelines: EEC, EES-B, ECS-B, EES-A, EAS-1..n. The sequence starts with EES-A and EAS-1..n performing registration (1). Then EEC performs service provisioning (2) and registration (3). EEC sends an EAS Discovery request (4) to EES-B. EES-B sends an EAS Discovery Request (5) to EES-A. EES-A returns an EAS Discovery Response (6) to EES-B. Finally, EES-B returns an EAS Discovery response (7) to EEC. + +**Figure 7.44.2.3-1: EAS discovery for edge node sharing** + +- 1) The EAS may be registered in EES of OP-A over EDGE-3 reference point. The EAS may be dynamically instantiated during EAS discovery processing on the EES (OP-A) and then registered in the EES (OP-A). + +NOTE 1: The EES (OP-A) also registers into the ECS (OP-A) via EDGE-6 reference point, which is not shown for simplicity. + +- 2) if required, EEC performs service provisioning from ECS-B as specified in 3GPP TS 23.558 [2]. + +**Editor's note: If service provisioning procedure is performed, how ECS finds EES, as there may not be desired EAS registered at EES, is FFS.** + +- 3) if required, EEC performs registration to EES-B as specified in 3GPP TS 23.558 [2]. + +- 4) The EEC sends EAS discovery request. The EES-A determines that the required EAS(s) is(are) not registered with the EES, and decides to provide service from partner OP's EAS. + +- 5) the EES-B sends EAS discovery request over EDGE-9 reference point to the EES-A. + +NOTE 2: If required, the EES-B may perform Retrieve T-EES procedure as specified in clause 8.8.3.3 of 3GPP TS 23.558 [2] to retrieve information about EES-A. + +- 6) the EES-A validates the edge service SLA and returns EAS discovery response including the discovered candidate EAS(s) to the EES-B. +- 7) Upon receiving registered EAS information from EES-A (either via notification or request to get all registered EAS information or EAS discovery procedure), the EES sends the EAS discovery response to EEC including matching EAS details. + +NOTE 3: It is up to implementation to decide which option to use to get list of registered EAS(s) from partner OP. + +#### 7.44.2.4 Get list of all registered EAS from partner OP + +Based on service provider policy, the EES-B either requests list of all registered EASs from partner OP's EES-A as specified in this clause, or perform EAS discovery based on the discovery filters provided by the EEC as specified in clause 7.44.2.3. + +NOTE 1: The EES-B may contact Edge Repository (of OP B) to identify EES (of OP A) to trigger request to get all registered EASs or EAS discovery. + +![Sequence diagram showing the interaction between EES-B and EES-A to get a list of all registered EASs. The steps are: 1) EES-B sends a 'Get all Registered EAS Information Request' to EES-A; 2) EES-A performs an internal 'Authorize the request'; 3) EES-A sends a 'Get all Registered EAS Information Response' back to EES-B.](9b686adccf125267a013fa25721231a3_img.jpg) + +``` +sequenceDiagram + participant EES-B + participant EES-A + Note right of EES-A: 2) Authorize the request + EES-B->>EES-A: 1) Get all Registered EAS Information Request + EES-A-->>EES-B: 3) Get all Registered EAS Information Response +``` + +Sequence diagram showing the interaction between EES-B and EES-A to get a list of all registered EASs. The steps are: 1) EES-B sends a 'Get all Registered EAS Information Request' to EES-A; 2) EES-A performs an internal 'Authorize the request'; 3) EES-A sends a 'Get all Registered EAS Information Response' back to EES-B. + +**Figure 7.44.2.4-1: Get list of all registered EASs from partner OP** + +Following steps shows procedure to request list of all registered EASs from EES-A. + +- 1) If the EES-B does not have full application knowledge at the time of EAS discovery request from the EEC, the EES triggers request to EES-A to provide list of all registered and allowed EAS information. The request includes required parameters like ECSP identifier, EESID and security parameters. +- 2) Upon receiving the request from EES-1, the EES-2 checks whether EES-1 is authorized to receive registered EAS list or not based on service level agreement. +- 3) If authorized, the EES-A sends registered EAS information response. The response includes the registered and allowed EAS for edge node sharing service between OP-A and OP-B, EASID and EAS Geographical Service. Otherwise, the EES-A sends the failure response. Upon receiving the success response, the EES-B stores the information to be used during EAS discovery procedure. + +NOTE 2: The request to get list of all registered EASs from EES-A to EES-B can be triggered anytime based on implementation. + +### 7.44.3 Solution evaluation + +This solution addresses KI#22 for the EAS discovery in edge node sharing case. This solution requires architecture enhancement to have a dedicated ECS (i.e. ECS-ER) in order to exchange the required information among partner OPs. This solution enables EAS discovery for edge node sharing scenario, where the EES-B either requests list of all registered EASs from partner OP's EES-A or perform EAS discovery based on the discovery filters provided by the EEC. Based on received registered EAS information from EES-A, the EES-B uses the information while providing the EAS discovery response to the EEC. This solution is a viable solution. + +## 7.45 Solution #45: EAS discovery in Edge Node sharing scenario + +### 7.45.1 Architecture enhancements + +None. + +### 7.45.2 Solution description + +#### 7.45.2.1 General + +The following solution corresponds to the key issue#22 on EAS discovery in Edge Node sharing scenario in clause 4.22. The scenario assumption is that the EES service (OP A) can be shared to the Operator B. The Operator B can rent the edge resource from the Operator A for the EAS deployment and also rent the EES service from the Partner A. + +![Diagram illustrating the architecture for EAS discovery in an Edge Node sharing scenario. The diagram is divided into two regions: SOUTH REGION and NORTH REGION (Edge Node Sharing). In the SOUTH REGION, there is an 'Operator B' Edge node containing 'EAS#2 (Operator B)' and 'EES#B (Operator B)'. Below this is a 'Local UPF (South Region)'. In the NORTH REGION, a dashed box labeled 'Partner A's shared edge resource' contains 'EAS#1 (Operator B)', 'Cloudlet (Shared Resource)', and 'EAS#3 (Operator A)'. Below this is 'EES#A (Shared with other Operators)'. A red arrow labeled 'PaaS' points from the North Region's EES#A down to a 'Local UPF (South Region)'. At the bottom, a large oval represents the 'PLMN of Operator B', containing 'PLMN of Operator B at South Region' and 'PLMN of Operator B at North Region'. A 'UC' (User Equipment) is connected to the North Region's PLMN, which is connected to the 'Local UPF (South Region)'.](15e4a144a88176b71ea3eff2722253b0_img.jpg) + +Diagram illustrating the architecture for EAS discovery in an Edge Node sharing scenario. The diagram is divided into two regions: SOUTH REGION and NORTH REGION (Edge Node Sharing). In the SOUTH REGION, there is an 'Operator B' Edge node containing 'EAS#2 (Operator B)' and 'EES#B (Operator B)'. Below this is a 'Local UPF (South Region)'. In the NORTH REGION, a dashed box labeled 'Partner A's shared edge resource' contains 'EAS#1 (Operator B)', 'Cloudlet (Shared Resource)', and 'EAS#3 (Operator A)'. Below this is 'EES#A (Shared with other Operators)'. A red arrow labeled 'PaaS' points from the North Region's EES#A down to a 'Local UPF (South Region)'. At the bottom, a large oval represents the 'PLMN of Operator B', containing 'PLMN of Operator B at South Region' and 'PLMN of Operator B at North Region'. A 'UC' (User Equipment) is connected to the North Region's PLMN, which is connected to the 'Local UPF (South Region)'. + +**Editor's note:** The scenario assumption in this solution needs to be verified with GSMA before considering this solution in conclusion. + +#### 7.45.2.2 EAS discovery Procedure + +In this solution, the EES is responsible to determine the EAS base on the desired ECSP information of the UE and the ECSP information of the EAS. With this solution, the EES can discovery and determine the considering the ECSP information of both the UE and the EAS, and thus UE can get edge computing service from the EAS deployed by ECSP serving its UE. + +Pre-conditions: + +1. OP A and OP B have a service level agreement to share edge EES services. +2. EAS deployed by the OP B in OP A. +3. The EAS register to the EES (OP A) with EAS ECSP ID (e.g. OP B). +4. EES (OP A) which is deployed by OP A but shared to OP B can register to ECS (OP B) + +**Editor's note:** It is FFS whether the EES (OP A) which is deployed by OP A but shared to OP B can register to ECS (OP B) is required or not. + +**Enhancement on the 3GPP TS 23.558 clause 8.3.3 Service Provisioning and 8.5 EAS discovery** + +![Sequence diagram illustrating the service provisioning and EAS discovery procedure. Lifelines: EEC, ECS (OP B), EES (OP A), and EAS (OP B). The sequence starts with 0a. EAS register to the EES (OP A) with the EAS ECSP ID, followed by 0b. EES register to the ECS (OP B). Then, 1. Service provisioning request from EEC to ECS (OP B), 2. Service provisioning response (EES (OP A)) from ECS (OP B) to EEC, 3. EAS discovery request (UE ECSP ID) from EEC to EES (OP A), and 4. EAS discovery response (EAS (OP B)) from EES (OP A) to EEC.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS as ECS (OP B) + participant EES as EES (OP A) + participant EAS as EAS (OP B) + + Note right of EAS: 0a. EAS register to the EES (OP A) with the EAS ECSP ID + EAS->>EES: 0a. EAS register to the EES (OP A) with the EAS ECSP ID + Note right of EES: 0b. EES register to the ECS (OP B) + EES->>ECS: 0b. EES register to the ECS (OP B) + + EEC->>ECS: 1. Service provisioning request + ECS-->>EEC: 2. Service provisioning response (EES (OP A)) + EEC->>EES: 3. EAS discovery request (UE ECSP ID) + EES-->>EEC: 4. EAS discovery response (EAS (OP B)) + +``` + +Sequence diagram illustrating the service provisioning and EAS discovery procedure. Lifelines: EEC, ECS (OP B), EES (OP A), and EAS (OP B). The sequence starts with 0a. EAS register to the EES (OP A) with the EAS ECSP ID, followed by 0b. EES register to the ECS (OP B). Then, 1. Service provisioning request from EEC to ECS (OP B), 2. Service provisioning response (EES (OP A)) from ECS (OP B) to EEC, 3. EAS discovery request (UE ECSP ID) from EEC to EES (OP A), and 4. EAS discovery response (EAS (OP B)) from EES (OP A) to EEC. + +**Figure 7.45.2.2-1: service provisioning and EAS discovery procedure** + +1. The EEC send the service provisioning request message to the ECS (OP B), the request message may contain the required EASID information +2. Upon receiving the request message, the ECS (OP B) determine the EES (OP A), when the required EAS is available in the OP A +3. The EEC sends the EAS discovery request to the EES (OP A) in the OP A which is shared to the Operator B, the request message contains the UE home ECSP (e.g OP B's information ) information. +4. Then the EES (OP A) in the OP A determines the EAS considering the ECSP information of both the UE and the EAS, e.g. UE home ECSP, ECSP of the EAS. + +#### 7.45.2.3 T-EAS discovery Procedure + +In this solution, the T-EES is responsible to determine the T-EAS base on the desired ECSP information of the UE and the ECSP information of the EAS. With this solution, the T-EES can discover and determine the T-EAS considering the ECSP information of both the UE and the EAS, and thus UE can get edge computing service from the T-EAS deployed by ECSP serving its UE. + +NOTE: The EEC's home ECSP ID (identifying OP) information is used to indicate which ECSP (e.g. OP)'s service is subscribed by the EEC. + +Pre-conditions: + +1. OP A and OP B have a service level agreement to share edge EES services. +2. EAS deployed by the OP B in OP A. +3. The T-EAS register to the T-EES (OP A) with EAS ECSP ID (e.g. OP B). +4. S-EES (OP A) and T-EES (OP A) which is deployed by OP A but shared to OP B can register to ECS (OP B) +5. The ECS (OP B) will only return the OP A's T-EES for edge node sharing case.. + +##### Enhancement on the 3GPP TS 23.558 clause 8.8.3.3 retrieve T-EES and 8.5 EAS discovery + +![Sequence diagram illustrating the Retrieve T-EES and EAS discovery procedure. Lifelines: S-EAS (OP B), S-EES (OP A), ECS (OP B), T-EES (OP A), T-EAS (OP B). The sequence starts with 0a. EAS register to the EES (OP A) with the EAS ECSP ID, followed by 0b. EES register to the ECS (OP B). Then, 1. EAS discovery request from S-EAS to S-EES. 2. Retrieve T-EES procedure from S-EES to ECS. 3. EAS discovery request from S-EES to T-EES. 4. EAS discovery response from T-EES to S-EES. 5. EAS discovery response from S-EES to S-EAS.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant S-EAS as S-EAS (OP B) + participant S-EES as S-EES (OP A) + participant ECS as ECS (OP B) + participant T-EES as T-EES (OP A) + participant T-EAS as T-EAS (OP B) + + Note right of T-EES: 0a. EAS register to the EES (OP A) with the EAS ECSP ID + Note right of ECS: 0b. EES register to the ECS (OP B) + S-EAS->>S-EES: 1. EAS discovery request + S-EES->>ECS: 2. Retrieve T-EES procedure + S-EES->>T-EES: 3. EAS discovery request + T-EES-->>S-EES: 4. EAS discovery response + S-EES-->>S-EAS: 5. EAS discovery response + +``` + +Sequence diagram illustrating the Retrieve T-EES and EAS discovery procedure. Lifelines: S-EAS (OP B), S-EES (OP A), ECS (OP B), T-EES (OP A), T-EAS (OP B). The sequence starts with 0a. EAS register to the EES (OP A) with the EAS ECSP ID, followed by 0b. EES register to the ECS (OP B). Then, 1. EAS discovery request from S-EAS to S-EES. 2. Retrieve T-EES procedure from S-EES to ECS. 3. EAS discovery request from S-EES to T-EES. 4. EAS discovery response from T-EES to S-EES. 5. EAS discovery response from S-EES to S-EAS. + +**Figure 7.45.2.X-1: Retrieve T-EES and EAS discovery procedure** + +1. The S-EAS send the EAS discovery request message to the S-EES (OP A), the request message may contain the EEC's home ECSP ID (e.g. identifying OP B's information). +2. The S-EES (OP A) perform the Retrieve T-EES procedure to the ECS (OP B) +3. Upon receiving the T-EES(OP A) information, the S-EES (OP A) sends the EAS discovery request message to the T-EES (OP A) which is shared to the Operator B, the request message contains the EEC's home ECSP ID (e.g. identifying OP B's information) +4. Then the T-EES (OP A) in the OP A determines the T-EAS considering the ECSP information of both the EEC and the EAS, e.g. EEC's home ECSP ID (e.g. identifying OP B's information), ECSP of the EAS. Then the T-EES (OP A) send the EAS discovery response message to the S-EES(OP A), the response message contains the T-EAS (OP B) information. +5. The S-EES (OP A) in the OP A send the EAS discovery response message to the S-EAS(OP B), the response message contains the T-EAS (OP B) information. + +**Editor's note: It is FFS whether other OP's EES will be returned to the S-EES of OP A** + +### 7.45.3 Solution evaluation + +This solution addresses KI#22 for the EAS discovery in edge node sharing case. This solution is applicable to the case where the EES (OP A) can be shared to the OP B, and the EAS deployed by OP-B in the OP A can only provide the service to the OP B's UE. The EES can determine the EAS or T-EAS based on the EEC's ECSP ID (e.g. identifying OP B's information) information and EAS's ECSP (e.g. OP) information. And this solution is a viable solution. + +NOTE: The EEC's ECSP ID (e.g. identifying OP's information) information is used to indicate which ECSP (e.g. OP)'s service is subscribed by the EEC. + +## 7.46 Solution #46: EEC selected ACR scenario for EAS bundles + +### 7.46.1 Architecture enhancements + +None. + +### 7.46.2 Solution description + +#### 7.46.2.1 General + +This solution corresponds to the key issue #18 on EAS bundles, and is proposed to make decisions on ACR scenarios for EAS bundles based on solution #35 of EEC selected ACR scenarios, to avoid the misaligned relocation between bundled EAS(s), by considering the AC/EEC/EES(s)/EAS(s) ability of handling bundled EAS ACR. + +The scenario assumption of this solution is that there is a coordinated ACR requirement for KI#18, i.e. the bundled EAS may need to be relocated together. + +**Editor's note:** This solution will not be used if SA4 don't have requirement for coordinated ACR in EAS bundle case; and solution needs to be revisited if SA4 clarifies such requirement existence. + +**Editor's note:** This solution may not be required depending on the feedback from SA5, e.g. if the bundled EASs register to the same EES. + +Compared with solution #35, this solution: + +- focus on the EAS bundles scenario where bundled EAS(s) for one AC associated with one EES or multiple EES(s) +- additionally considering the AC/EEC/EES(s)/EAS(s) ability of handling bundled EAS ACR to determined ACR scenario for EAS bundles. + +NOTE: This solution is based on existence of bundled EAS ACR in solution #26, the AC/EEC/EAS/EES capability to support EAS bundle ACR will use any agreed name for bundled ACR scenario in solution #26. + +#### 7.46.2.2 Procedure + +In this solution, the bundled EAS list is introduced in AC profile, to represent that the multiple EAS(s) are to serve the same AC. The associated EES list is introduced to describe the EES(s) where the bundled EAS(s) is registered in. The EEC can be responsible to make decisions on ACR scenarios selection for EAS bundles. In the following procedure, the bundled EAS list consists of EAS#1 and EAS#2, and the associated EES list includes EES#1 and EES#2, where EAS#1 and EAS#2 are registered in EES#1 and EES#2, respectively. + +![Sequence diagram illustrating the EEC selected ACR scenarios for EAS bundles. The diagram shows interactions between EEC, ECS, EES#1, EES#2, EAS#1, and EAS#2. The process involves EAS registration, EES registration, service provisioning, EAS discovery, determination of ACR scenario, and selected EAS announcement requests and responses.](768b8ab0d55761b205087c079df1e6e6_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS + participant EES#1 + participant EES#2 + participant EAS#1 + participant EAS#2 + + Note right of EES#1: 1. EAS registration + EAS#1->>EES#1: + Note right of EES#2: 2. EAS registration + EAS#2->>EES#2: + Note right of ECS: 3. EES registration + EES#1->>ECS: + Note right of ECS: 4. EES registration + EES#2->>ECS: + Note right of ECS: 5. Service provisioning + ECS->>EEC: + Note right of ECS: 6. EAS discovery + ECS->>EEC: + Note right of ECS: 7. EAS discovery + ECS->>EEC: + Note left of EEC: 8. Determination of ACR scenario + EEC->>EES#1: 9. Selected EAS announcement request + EES#1->>EAS#1: 10. ACR scenario selection notification + EAS#1->>EES#1: 11. Selected EAS announcement response + EES#1->>EEC: 12. Selected EAS announcement request + EEC->>EES#2: 13. ACR scenario selection notification + EES#2->>EAS#2: + EAS#2->>EES#2: + EES#2->>EEC: 14. Selected EAS announcement response + +``` + +Sequence diagram illustrating the EEC selected ACR scenarios for EAS bundles. The diagram shows interactions between EEC, ECS, EES#1, EES#2, EAS#1, and EAS#2. The process involves EAS registration, EES registration, service provisioning, EAS discovery, determination of ACR scenario, and selected EAS announcement requests and responses. + +**Figure 7.46.2.2-1: EEC selected ACR scenarios for EAS bundles** + +- 1-2. The EAS sends an EAS registration request to the EES, the request includes the EAS ability of handling bundled EAS ACR (e.g. bundled EAS list) in EAS profile (as extension in EAS service continuity support). +- 3-4. The EES sends an EES registration request to the ECS, the request includes the EES ability of handling bundled EAS ACR (e.g. bundled EAS list, and/or notify other bundled EAS(s) to perform ACR) in EES profile (as extension in EES service continuity support). +5. EEC performs service provisioning with ECS, and ECS returns the EES list with the EES ability of handling bundled EAS ACR and the EES service continuity support to EEC. + +- 6-7. The EEC performs EAS discovery using procedures defined in 3GPP TS 23.558 [2] clause 8.5 to obtain a list of discovered EAS(s), with the EAS ability of handling bundled EAS ACR. + 8. The EEC (or AC) selects bundled EAS(s) from the discovered EAS list. The EEC selects the ACR scenario(s) for EAS bundles that should be used for the given AC and selected EAS(s) by considering the ACR scenarios support by AC, EEC, EES(s) and EAS(s), and the AC/EEC/EES(s)/EAS(s) abilities of handling bundled EAS ACR. ACR selection can result in zero or more ACR scenarios being selected. For selecting the ACR, the EEC minimally considers the ACR capabilities of the AC from AC Profile, of the EEC (known locally), of the EES(s) from service provisioning response received from the ECS (pre-requisite), and of the EAS(s) from EAS Profile and obtained at EAS discovery. +- NOTE: The enhancement of ACR scenario, if required, will be considered in normative work. +9. The EEC sends the selected ACR scenario(s) to EES in selected EAS announcement request, the EES uses the list of selected ACR scenarios to determine if it should perform ACR detection and/or ACR decision. + 10. The EES sends an ACR selection notification to its registered EAS(s) which are part of the bundled EAS(s), providing the selected ACR scenario list. Not shown on the figure, the EAS previously subscribed to receive ACR notifications. The EAS uses the selected ACR scenarios list to determine if it should perform ACR detection and/or ACR decision. + 11. The EES sends the selected EAS declaration response to the EEC indicating success or failure of the EAS announcement request. + - 12-14: The EEC sends the selected ACR scenario(s) with related ACID and EASID to other associated EES(s) and the other bundled EAS(s). + +### 7.46.3 Solution evaluation + +This solution addresses KI#18. To satisfy the coordinated ACR requirements (i.e. the bundled EAS may need to be relocated together), the EEC can act as decision entity to select ACR scenario(s) for EAS bundles, based on the AC/EEC/EES(s)/EAS(s) abilities of handling bundled EAS ACR. + +## 7.47 Solution #47: EES determines the selected ACR scenario for EAS bundles + +### 7.47.1 Architecture enhancements + +None. + +### 7.47.2 Solution description + +#### 7.47.2.1 General + +This solution corresponds to the key issue #18 on EAS bundles where multiple EES(s) are involved, and is proposed to make decisions on ACR scenarios for EAS bundles based on solution #19 of EES determined ACR scenarios, to avoid the misaligned relocation between bundled EAS(s), by considering the AC/EEC/EES(s)/EAS(s) ability of handling bundled EAS ACR. + +The scenario assumption of this solution is that there is a coordinated ACR requirement for KI#18, i.e. the bundled EAS may need to be relocated together. + +**Editor's note:** This solution will not be used if SA4 don't have requirement for coordinated ACR in EAS bundle case; and solution needs to be revisited if SA4 clarifies such requirement existence. + +**Editor's note:** This solution may not be required depending on the feedback from SA5, e.g. if the bundled EASs register to the same EES. + +Compared with solution #19, this solution: + +- focus on the EAS bundles scenario where bundled EAS(s) for one AC associated with multiple EES(s) +- additionally considering the AC/EEC/EES(s)/EAS(s) ability of handling bundled EAS ACR to determined ACR scenario for EAS bundles. + +NOTE: This solution is based on existence of bundled EAS ACR in solution #26, the AC/EEC/EAS/EES capability to support EAS bundle ACR will use any agreed name for bundled ACR scenario in solution #26. + +#### 7.47.2.2 Procedure + +In this solution, the bundled EAS list is introduced in AC profile, to represent that the multiple EAS(s) serve the same AC. The associated EES list is introduced to describe the EES(s) where the EAS(s) in the bundled EAS(s) are registered in. An EES can be responsible to make decisions on ACR scenarios selection for EAS bundles. In the following procedure, the bundled EAS list consists of EAS#1 and EAS#2, and the associated EES list includes EES#1 and EES#2, where EAS#1 and EAS#2 registered in EES#1 and EES#2, respectively. + +![Sequence diagram illustrating the procedure where EES determines the selected ACR scenario for EAS bundles. The diagram shows interactions between EEC, EES#1, EES#2, EAS#1, and EAS#2. The process starts with service provisioning and EAS discovery. EAS#1 and EAS#2 send ACR scenario selection subscriptions to EES#1 and EES#2 respectively. The EEC sends an ACR scenario selection request to EES#1. EES#1 determines the ACR scenario and sends a response to the EEC. The EEC then sends an ACR scenario selection notification to EES#1. EES#1 sends a selected ACR scenario announcement request to EAS#1. EAS#1 sends a selected ACR scenario announcement response to EES#1. Finally, EES#1 sends an ACR scenario selection notification to EES#2.](b612b838f94982799a69461ffb078a73_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant EES#1 + participant EES#2 + participant EAS#1 + participant EAS#2 + + Note over EEC, EAS#2: 0. Service provisioning, EAS discovery + Note over EES#1, EAS#1: 1. ACR scenario selection subscription + Note over EES#2, EAS#2: 2. ACR scenario selection subscription + EEC->>EES#1: 3. ACR scenario selection request + Note over EES#1: 4. Determination of ACR scenario + EES#1->>EEC: 5. ACR scenario selection response + EEC->>EES#1: 6. ACR scenario selection notification + EES#1->>EAS#1: 7. Selected ACR scenario announcement request + EAS#1->>EES#1: 8. Selected ACR scenario announcement response + EES#1->>EES#2: 9. ACR scenario selection notification + +``` + +Sequence diagram illustrating the procedure where EES determines the selected ACR scenario for EAS bundles. The diagram shows interactions between EEC, EES#1, EES#2, EAS#1, and EAS#2. The process starts with service provisioning and EAS discovery. EAS#1 and EAS#2 send ACR scenario selection subscriptions to EES#1 and EES#2 respectively. The EEC sends an ACR scenario selection request to EES#1. EES#1 determines the ACR scenario and sends a response to the EEC. The EEC then sends an ACR scenario selection notification to EES#1. EES#1 sends a selected ACR scenario announcement request to EAS#1. EAS#1 sends a selected ACR scenario announcement response to EES#1. Finally, EES#1 sends an ACR scenario selection notification to EES#2. + +**Figure 7.47.2.2-1 EES determines the selected ACR scenario for EAS bundles** + +0. The EEC performs service provisioning procedure and EAS discovery procedure, obtains the discovered bundled EAS list, the associated EES list, the EAS ability of handling bundled EAS ACR (e.g. bundled EAS list) in EAS profile (as extension in EAS service continuity support), and the EES ability of handling bundled EAS ACR (e.g. bundled EAS list, and/or notify other bundled EAS(s) to perform ACR) in EES profile (as extension in EES service continuity support). +- 1-2. The EAS sends an ACR scenario selection subscription request to the EES, the EES sends an ACR scenario selection subscription response to the EAS with the subscription result. +3. The EEC sends ACR scenario selection request to one of EES, the request contains the AC service continuity support and EEC service continuity support indicating which ACR scenarios are supported by the AC and the + +EEC. The request also contains the bundled EAS list, the associated EES list, the AC/EEC/EES(s)/EAS(s) ability of handling bundled EAS ACR (e.g. bundled EAS list, and/or notify other bundled EAS(s) to perform ACR). + +4. Based on the AC service continuity support, EEC service continuity support, the bundled EAS list, the AC/EEC/EES(s)/EAS(s) abilities of handling bundled EAS ACR and EAS service continuity support, the EES determines the suitable ACR scenario(s) for the bundled EAS(s) scenario. The EES can select the appropriate ACR scenario(s) for the bundled EAS(s) scenario from the intersection of the ACR scenarios supported by AC, EEC, EES(s) and EAS(s). + +NOTE: The enhancement of ACR scenario, if required, will be considered in normative work. + +5. The EES sends the ACR scenario selection response to the EEC, including the selected ACR scenario with related ACID and EASID, then EEC may notify the AC with the selected ACR scenario. +6. The EES sends the ACR scenario selection notification to its registered EAS(s) which are part of the bundled EAS(s), including the selected ACR scenario with related ACID and EASID. +7. The EES sends the selected ACR scenario selection announcement request to other associated EES(s), including the selected ACR scenario with related ACID and EASID. +8. The other associated EES(s) send the selected ACR scenario announcement response to the EES. +9. The other associated EES(s) sends the ACR scenario selection notification to its registered EAS(s) which are part of the bundled EAS(s), including the selected ACR scenario with related ACID and EASID. + +### 7.47.3 Solution evaluation + +This solution addresses KI#18. To satisfy the coordinated ACR requirements (i.e. the bundled EAS may need to be relocated together), the EES can act as decision entity to determine ACR scenario(s) for EAS bundles, based on the AC/EEC/EES(s)/EAS(s) abilities of handling bundled EAS ACR. + +## 7.48 Solution #48: Edge server set and edge service set + +### 7.48.1 Architecture enhancements + +None. + +### 7.48.2 Solution description + +#### 7.48.2.1 General + +This solution is related to KI#23 on Reliable Edge service. + +NOTE: The reference to 3GPP TS 23.501 [5] is used in the study to avoid repeating the text in set-based service resilience. In normative work all the procedures and concepts need to be specified based on EDGEAPP terms and EES/ECS-based information transfer procedures. + +#### 7.48.2.2 Reliability support with Sets + +By adopting the NF set and NF service set approach, as specified in clause 5.21.3 of 3GPP TS 23.501 [5], an edge server set and edge service set can be introduced to enable an EES/ECS to provide reliable services to the edge service consumers (e.g. EAS, EEC). + +Equivalent Edge servers may be grouped into Edge server sets, e.g. several EES instances are grouped into an EES set. Edge servers within an Edge server set are interchangeable because they share the same context data, and may be deployed in different locations, e.g. different data centres. An Edge server (e.g. EES) is composed of one or multiple Edge Services. Within an Edge server, an Edge service may have multiple instances. These multiple Edge Service instances can be grouped into Edge Service Set if they are interchangeable with each other because they share the same context data. + +NOTE 1: How equivalent EESs are determined (e.g. based on KPIs, service area) to group into an EES set (e.g. by O&M or other means) will be considered in normative work. + +UE is not required to host multiple instances of the same EEC but the EEC is able to perform re-connection due to ECS/EES service failure. + +Likewise, for service binding, it can be used by edge service producer and consumer to indicate a particular context (e.g. EEC context, EDGE-3 subscription context) that is bound to an edge service instance, edge server instance, edge service set or edge server set. The basic principle for binding is to exchange binding information between consumer and producer so that they know how to connect to alternative in case of service failure depending on level of binding (e.g. edge server set level, edge service set level). + +For subscribe-notify type of interaction, the binding is needed between the edge service consumer and edge service producer. As an example, the EDGE-3 API operation Eees\_UELocation\_Subscribe is used to depict the impact: + +![Sequence diagram illustrating the UE location API: Subscribe operation between EAS and EES.](1b896a95bc9974ad01fac7ac6f541a96_img.jpg) + +``` + +sequenceDiagram + participant EAS + participant EES + Note right of EES: 2. Subscribe UE location + Note right of EES: 3. Subscribe UE expected behavior analytics + Note right of EES: 5. Detection of Location of the UE + Note right of EES: 9. Update UE location subscription and UE expected behavior analytics + + EAS->>EES: 1. UE location subscribe request (binding indication 1) + EES->>EAS: 4. UE location subscribe response (binding indication 2) + EES->>EAS: 6. UE location API Notification (updated binding indication 2) + EAS->>EES: 7. UE location API Notification Ack. (updated binding indication 1, updated binding indication 1) + EAS->>EES: 8. UE location subscribe update request (updated binding indication 1) + EES->>EAS: 10. UE location subscribe update response (updated binding indication 2) + +``` + +The sequence diagram shows the interaction between EAS (Edge Service Consumer) and EES (Edge Service Producer) for the UE location API: Subscribe operation. The sequence of messages is as follows: + +- EAS sends a "UE location subscribe request (binding indication 1)" to EES. +- EES performs internal steps: "Subscribe UE location" and "Subscribe UE expected behavior analytics". +- EES sends a "UE location subscribe response (binding indication 2)" back to EAS. +- EES performs internal step: "Detection of Location of the UE". +- EES sends a "UE location API Notification (updated binding indication 2)" to EAS. +- EAS responds with "UE location API Notification Ack. (updated binding indication 1, updated binding indication 1)" to EES. +- EAS sends a "UE location subscribe update request (updated binding indication 1)" to EES. +- EES performs internal step: "Update UE location subscription and UE expected behavior analytics". +- EES sends a "UE location subscribe update response (updated binding indication 2)" back to EAS. + +Sequence diagram illustrating the UE location API: Subscribe operation between EAS and EES. + +**Figure 7.48.2.2-1: UE location API: Subscribe operation** + +To create a binding for UE location notification, in step 1, the UE location subscribe request may include a Binding Indication 1 referring to EAS service instance, EAS service set, EAS instance or EAS set and additionally includes a service name of the EAS as specified in Table 6.3.1.0-1 of TS 23.501 [5]. The EAS service set ID, EAS service instance ID and service name relate to the service of EAS that will handle the notification. The EES selects the target for the related notifications using the notification endpoint received in the subscription request. If the notification endpoint included in the subscription is not reachable, the Binding Indication received is used to discover an alternative notification endpoint, as specified in Table 6.3.1.0-1 of TS 23.501 [5]. + +NOTE 2: SCP related description in TS 23.501 [5] is out of the scope of current study and therefore not applicable for EDGEAPP. The routing binding indication described in TS 23.501 [5] is not applicable for EDGEAPP, consequently. + +If the Binding Indication for Notifications needs to be updated, the EAS may initiate a location subscription update request (step 8) to the NF service producer with an updated Binding Indication 1 or may include the updated Binding Indication 1 in the acknowledgment of a Notification. + +Binding for the subscription resource at the EES can also be created. In step 4, the UE location subscribe response message may contain a Binding Indication 2 referring to EES service instance, EES instance or EES Set. The EAS selects the target for the related request to the EES, such as the request to update the subscription shown in step 8 of Figure 7.48.2.2-1, using the received Binding Indication 2 as specified in Table 6.3.1.0-1 of TS 23.501 [5]. + +If the Binding Indication for Subscription needs to be updated, the EES may provide an updated binding indication 2 in a notification request (step 6) to the EAS or in the response (step 10) to a subsequent location subscription update request from the EAS. + +For request-response type of interaction, as another example to provide reliable service, the EES registration procedure is enhanced with binding indication sent by the ECS. The EES uses the binding indication in the EES registration response to select the target for subsequent interaction (e.g. EES registration update request). The ECS may update the binding in EES registration update response. + +NOTE 3: For stateless request-response (e.g. Ees\_UELocation\_Get operation), there is no need to include binding information in response message. + +NOTE 4: More EEL specific procedure adaptation with Edge service set and Edge server set can be done in normative work by following above principle. + +#### 7.48.2.3 EES binding update + +In case when ECSP has decided to gracefully shutdown the EES due to maintenance (or any other reason), the EES, as a service producer, may inform its consumers (e.g. EEC, EAS) about the EES instance unavailability via binding update as specified in clause 6.5.3.3 of 3GPP TS 29.500 [2]. The consumer (e.g. EEC, EAS), re-connects to another EES instance within the same EES set for subsequent communication. + +An EES can be taken graciously out of service as follows: + +- the EES instance pushes all related context to the selected alternate EES instance as specified in clause 7.48.2.4; and +- the EES instance notifies all its consumers like EECs and EASs (which are subscribed for binding update information). + +The consumer may also detect the EES unavailability by itself (e.g. request is not responded) that the EES instance is not available anymore, another available EES instance within the same EES set is connected by the consumer. + +NOTE 1: Whether re-selection of the EES is required and the procedure for re-selection of edge service instance can be addressed in the normative work. + +For EES sent notification, it is assumed that the consumer(s) are subscribed to receive the binding update notification. + +NOTE 2: Whether consumers need to have a dedicated subscription per EES instance level or existing service subscription in EES can be re-used is to be decided in normative work. Any further consumer action upon receiving the binding update information or upon detecting the EES unavailability by itself can be specified during normative work. + +NOTE 3: In this solution, the EES service end point in a set is different. Multiple EESs using the same virtual IP address is out of the scope. + +#### 7.48.2.4 Context Transfer procedure + +Network Function/NF Service Context Transfer procedure as specified in clause 5.21.4 of 3GPP TS 23.501 [5], can be adopted for EES. The EEC Context Transfer Procedures allow transfer of EEC and EAS Contexts from a EES instance (as a S-EES) to another EES instance (as a T-EES) within the same EES set, e.g. before the Source EES can gracefully close its service. + +- The EES instance can push all registered EEC and EAS contexts to another EES instance within the same EES Set. In order to push all registered EEC and EAS contexts to the T-EES, the S-EES sends EEC Context Push + +request as specified in clause 8.9.2.3 of 3GPP TS 23.558 [2]. The request further includes additional information elements as specified in Table 7.48.2.2-1. + +**Table 7.48.2.2-1: Additional IEs for EEC Context Push request** + +| Information element | Status | Description | +|------------------------------|--------|--------------------------------------------------------------------------------| +| List of EEC Contexts | O | List of registered EEC Contexts to sync with target EES from the same EES Set. | +| List of EAS Profiles | O | List of registered EAS profiles to sync with target EES from the same EES Set. | +| List of EDGE-3 subscriptions | O | List of subscriptions IDs over EDGE-3. | +| Identifier | M | Identifies EES Set. | + +NOTE: If list of EAS profiles information element is present, then the T-EES considers it as an indication for the content synchronization between EESs within same EES Set. + +- b) Upon receiving context push request, the T-EES validates and authorizes the S-EES. If the S-EES is authorized and both S-EES and T-EES are part of same EES Set, then the T-EES stores the information for synchronization – e.g. list of EEC contexts and list of EAS profiles. + +### 7.48.3 Solution evaluation + +The solution addresses KI#23 related to Reliable Edge service. The solution proposes to adopt a mechanism like Network Reliability support with Sets as specified in 3GPP TS 23.501 [5] for EDGEAPP. The binding mechanism is described for subscription request and service response in EEL. The solution also provides EEL procedures to support reliability in EEL – like EES planned removal, context transfer between EES instances of same EES Set. + +## 7.49 Solution #49: ACR for EAS composition + +### 7.49.1 Architecture enhancements + +None. + +### 7.49.2 Solution description + +This solution addresses the case of a single AC-EAS session where the EAS consumes other edge services, therefore acting as (or forming) a composite EAS. In this use case the AC is not aware of the EAS being part of a composite service, therefore ACRs can be initiated by the EEC or servers (EES, EAS) in DN as described in all Rel-17 ACR scenarios. + +NOTE: The single EAS to which the AC is connected is termed "connecting EAS", while the other EASs within the composite service are termed "component EASs". The "connecting EAS" and "component EASs" form an EAS composition. + +After the initial AC-EAS connection, the connecting EAS may utilize the EDGEAPP discovery mechanisms to find the other services (component EASs) necessary to provide the composite service, and communicates with them. During ACR of the single AC-EAS session, once the connecting EAS is aware of ACR happening, it is the connecting EAS's responsibility to find target EASs (e.g. using EDGEAPP discovery mechanism) for the component EASs, and to trigger ACT, if needed. The component EASs may be served by the same EES as the connecting EAS, or by different EESs. + +NOTE: In order to trigger ACT for the other component EASs, after discovery the connecting EAS can send the endpoints of the targets to the sources, or can send the endpoints of sources to the targets. This is out of the scope of the current study. + +### 7.49.3 Solution evaluation + +This solution addresses KI#20 and there is no impact identified in EEL for EAS composition. + +## 7.50 Solution #50: Enhanced ECS for federation of services + +### 7.50.1 Architecture enhancements + +This solution uses the architecture option #12 and relates to the assumptions specified in clause 6.12. + +### 7.50.2 Solution description + +#### 7.50.2.1 ECS registration with the ECS-ER + +ECS registers with the ECS-ER and provides the information such as EDN configuration information, applications available via the ECS etc. Figure 7.50.2.1-1 illustrates the procedure. + +Pre-conditions: + +1. The ECS has the address (e.g. URI) of the ECS-ER. + +![Sequence diagram illustrating ECS registration with ECS-ER. The diagram shows two lifelines: ECS and ECS (Edge Repository). The sequence of messages is: 1. ECS registration request from ECS to ECS (Edge Repository); 2. Process request from ECS (Edge Repository) to ECS (Edge Repository); 3. ECS registration response from ECS (Edge Repository) to ECS.](1c94fd3cebf58af136144f14160d128e_img.jpg) + +``` + +sequenceDiagram + participant ECS + participant ER as ECS (Edge Repository) + Note right of ER: 2. Process request + ECS->>ER: 1. ECS registration request + ER->>ER: 2. Process request + ER->>ECS: 3. ECS registration response + +``` + +Sequence diagram illustrating ECS registration with ECS-ER. The diagram shows two lifelines: ECS and ECS (Edge Repository). The sequence of messages is: 1. ECS registration request from ECS to ECS (Edge Repository); 2. Process request from ECS (Edge Repository) to ECS (Edge Repository); 3. ECS registration response from ECS (Edge Repository) to ECS. + +**Figure 7.50.2.1-1: ECS registration with ECS-ER** + +1. The ECS sends the ECS registration request to the ECS-ER. The request from the ECS includes the ECS configuration information (ECS address and the ECS provider information) along with its security credentials. EDN configuration information etc. The request also includes a list of EES/EASs available via the ECS in order to publish the information to other ECS-ER(s). The request may include a proposed expiration time for the registration, and may include list of partner ECSPs that are allowed to receive its information. +2. Upon receiving the request from the ECS, the ECS-ER verifies the security credentials of the ECS and stores the ECS registration information obtained in step 1. +3. The ECS-ER sends an ECS registration response indicating success or failure of the registration operation. The ECS-ER may provide an expiration time to indicate to the ECS when the registration will automatically expire. To maintain the registration, the ECS sends a registration update request prior to the expiration time. If a registration update request is not received prior to the expiration time, the ECS-ER treats the ECS as implicitly de-registered. + +NOTE 1: ECS registration update and ECS deregistration procedures are required. + +NOTE 2: Name of the message flows will be determined during normative. + +#### 7.50.2.2 ECS querying ECS-ER + +When required to find a partner ECS, the ECS queries the ECS-ER by providing information such as the location of the UE, application required by the UE etc. In response the ECS-ER provides ECS configuration information of partner + +ECS(s) providing the required application at the location indicated by the primary ECS. Figure 7.50.2.2-1 illustrates the procedure. + +Pre-conditions: + +1. The ECS is part of a federation and has the address information of the ECS-ER. +2. The ECS has received a service provisioning request from an EEC or a T-EES discovery request from an EES, where EDN information for the requested application is not available at the ECS. + +![Sequence diagram illustrating the ECS querying ECS-ER procedure. The diagram shows three steps: 1. ECS discovery request from ECS to ECS (Edge Repository); 2. Process request from ECS (Edge Repository) to ECS; 3. ECS discovery response from ECS (Edge Repository) to ECS.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +``` + +sequenceDiagram + participant ECS + participant ER as ECS (Edge Repository) + Note right of ER: 2. Process request + ECS->>ER: 1. ECS discovery request + ER-->>ECS: 3. ECS discovery response + +``` + +Sequence diagram illustrating the ECS querying ECS-ER procedure. The diagram shows three steps: 1. ECS discovery request from ECS to ECS (Edge Repository); 2. Process request from ECS (Edge Repository) to ECS; 3. ECS discovery response from ECS (Edge Repository) to ECS. + +Figure 7.50.2.2-1: ECS querying ECS-ER + +1. The ECS sends a ECS discovery request to the ECS-ER. The request contains information of the ECS, Service Provisioning filters received from the EEC or the EES and UE's current location. If the UE hosting the EEC is roaming in a V-PLMN (determined using the serving PLMN information in the received service provisioning request, or by interacting with the H-PLMN), then the ECS discovery request includes the information of the serving PLMN i.e. the V-PLMN. +2. The ECS-ER authorizes the received request. If authorized, the ECS-ER processes the request and gathers the information of partner ECS(s) that can satisfy the query parameters received in step 1. +3. The ECS-ER sends a ECS discovery response to the ECS. The response includes ECS configuration information of the Partner ECS(s) available in the H-PLMN and/or the V-PLMN, depending on the serving PLMN of the UE as indicated in step 1. The Primary ECS caches the received information for further use. + +NOTE 1: In addition to the request/response model, a subscribe/notify model will also be provided by the ECS-ER, where ECS-ER will notify subscribed ECSs based on local policies, subscription filters and ECSP partnership information provided by the registered ECSs. + +NOTE 2: To process the service provisioning requests from the EEC or retrieve T-EES request from the S-EES, the ECS can use preconfigured information or information configured via OAM, or a discovery mechanism as specified in clause 7.50.2.2. + +#### 7.50.2.3 Service provisioning for Federation and/or Roaming + +If the Primary ECS is unable to fulfil Service Provisioning request of an EEC it retrieves information of the partner ECS(s) that provide the required application at UE's location and provide the list of retrieved partner ECS configuration information to the EEC in the Service provisioning response. Figure 7.50.2.3-1 illustrates the procedure. + +![Sequence diagram showing ECS discovery for Federation and/or Roaming between EEC and Primary ECS.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant Primary ECS + Note right of Primary ECS: 2. EEC authentication/authorization and policy enforcement + Note right of Primary ECS: 3. ECS determines that EDN configuration information for some of the required application(s) is not available with it. + Note right of Primary ECS: 4. ECS retrieves ECS configuration information of partner ECS(s) that provide the required application(s) + Note right of Primary ECS: 5. Filtering based on local policy and EEC's profile for service differentiation + EEC->>Primary ECS: 1. Service Provisioning request + Primary ECS-->>EEC: 6. Service Provisioning response + +``` + +The diagram illustrates a sequence of interactions between an EEC (Edge Enabling Client) and a Primary ECS (Edge Enabling Server). The sequence starts with the EEC sending a 'Service Provisioning request' (step 1) to the Primary ECS. The Primary ECS then performs 'EEC authentication/authorization and policy enforcement' (step 2). It then determines if EDN configuration information for some required applications is not available (step 3). Based on this, it retrieves ECS configuration information of partner ECS(s) that provide the required applications (step 4). Finally, it applies filtering based on local policy and the EEC's profile for service differentiation (step 5). The Primary ECS then sends a 'Service Provisioning response' (step 6) back to the EEC. + +Sequence diagram showing ECS discovery for Federation and/or Roaming between EEC and Primary ECS. + +**Figure 7.50.2.3-1: ECS discovery for Federation and/or Roaming** + +1. The EEC sends a service provisioning request to the Primary ECS. This request is same as the service provisioning request specified in 3GPP TS 23.558 [2]. Additionally, in case the UE hosting the EEC is roaming to a V-PLMN, the service provisioning request may include the V-PLMN ID. +2. Upon receiving the request, the Primary ECS performs authorization and policy enforcement as specified in 3GPP TS 23.558 [2]. +3. The Primary ECS identifies required EDN configuration information based on the received request in step 1 and checks in step 2. The Primary ECS determines that EDN configuration information for at least one of the required applications (i.e. EAS) is not available. +4. Based on the determination in step 3, the Primary ECS retrieves ECS configuration information of partner ECS(s) that provide the required application(s) at the UE's location. The Primary ECS can use for e.g. preconfigured information, information configured via OAM, or a discovery mechanism (see clause 7.50.2.2) as available. + +NOTE: The Primary ECS can use for preconfigured information, information configured via OAM, or a discovery mechanism as available in any order. + +5. On retrieving the ECS configuration information of partner ECS(s), the Primary ECS applies any local policy or EEC profile-based filtering for service differentiation. +6. The Primary ECS sends service provisioning response to the EEC. The response is same as specified in 3GPP TS 23.558 [2]. Additionally, it includes a list of Partner ECS(s) which provide the applications required by the EEC. The information includes ECS provider information, list of EAS(s) available via the EES's registered with Partner ECS etc. The response either includes the ECS address information, if the EEC is authorized to communicate directly with the Partner ECS, or it includes an indication that the Partner ECS must be reached via the Primary ECS. For the Partner ECS(s) that may be communicated directly, the response also includes authorization information required by the EEC to communicate with the Partner ECS. + +The response may also include EDN configuration information for the EAS(s) available via the Primary ECS, if any. + +## 7.51 Solution #51: EEC sharing UE Mobility requirement + +### 7.51.1 Architecture enhancements + +None. + +### 7.51.2 Solution description + +The solution addresses KI#12. + +#### 7.51.2.1 Enhancements to EEC Registration + +The solution proposes the EEC to share indication for mobility support requirement (e.g. whether the UE is fixed or not) in EEC registration request message. The solution proposes to enhance EEC registration procedure specified in clause 8.4.2.2.2 and EEC registration update procedure as specified in clause 8.4.2.2.3 as follows: + +- The EEC registration request or EEC registration update request from the EEC may include indication for mobility support requirement (e.g. whether UE is fixed or not) to the EES. +- Upon receiving the request from EEC, the EES stores the information as part of EEC context for future usage. + +NOTE: When the information received in the EEC registration request indicates the mobility support requirement, the EES may decide not to subscribe to NEF or NWDAF for UE location information or its analytics, but rather perform one time location or less frequent fetch of the UE and store it. + +##### 7.51.2.1.1 Enhancements to EEC registration request + +Table 7.51.2.1.1-1 describes the additional information elements in the EEC registration request and EEC registration update request from the EEC to the EES. + +**Table 7.51.2.1.1-1: additional IE for EEC registration request and EEC registration update request** + +| Information element | Status | Description | +|------------------------------|--------|---------------------------------------------------------| +| mobility support requirement | O | Indicates UE or device requires mobility support or not | + +NOTE: How EEC gets information about UE being fixed is out of scope of specification. + +### 7.51.3 Solution evaluation + +The solution addresses KI#12. The solution proposes to enhance the EEL specifically EEC registration and EEC registration update procedures to provide indication whether the UE requires mobility support or not to the EES. + +The EES may use this information to decide whether or not to subscribe to NEF or NWDAF for UE location information or its analytics, but rather perform one time location or less frequent fetch of the UE location and store it. Such a decision is up to EES implementation. + +The solution is viable solution. + +## 7.52 Solution #52: EES policy differentiation + +### 7.52.1 Architecture enhancements + +None. + +### 7.52.2 Solution description + +The KI#12 is about EEL service differentiation. EEL includes EEC, EES and ECS (and possibly new entities in Rel-18 study) to support the applications over the top. + +In TS 23.558, Annex B.1, it says: + +The edge computing service provider and the PLMN operator can be part of the same organization. + +In this solution, the scenario assumption is that: + +- the ECSP providing the EES and PLMN operator are the same organization. +- the ECSP/EES provider (e.g. ECSP#1, EES provider#1) will only deploy its EES in the edge and not deploy its own ECS for its EES, and the ECSP/EES provider (e.g. ECSP#1, EES provider#1) will rely on another ECSP/ECS provider (e.g. ECSP#2, ECS provider#2) to register its EES based on service agreement. + +NOTE 1: Whether this solution also applies for ECSP providing both its EES and its ECS (with EES registered in the ECS) can be determined in the normative work. + +**Editor's note: Whether ASP only has service agreement with ECSP/ECS provider, or both ECSP/ECS provider and ECSP/ECS provider is FFS.** + +**Editor's note: Whether EEC only has service agreement with EES/ECS provider, or both ECSP/ECS provider and ECSP/ECS provider is FFS.** + +For instance, the EES, after receiving EAS discovery request, obtains the PLMN subscription data for the user. Then the EES acts differently when provisioning EAS candidates to the service consumer (e.g. EEC) based on PLMN subscription data for the user. For instance, policy can be the max. number of applications for edge computing, e.g. EES can only support max. 5 applications for a user without payment (for trial purpose in edge computing service). Another example is temporal and spatial conditions for providing edge service like EAS discovery under different Edge service levels. More detailed PLMN subscription data for a user is implementation specific in EES and out of the scope of the study. + +NOTE 2: EEC is an application in the UE, which can be used by different users. For instance, Alice pays 10 dollars per month to ECSP company X as EES provider to enjoy VIP service for facilitating edge computing. While Bob is a free user to ECSP company X who just wants to try company X provided EES service. Company X's EES can provide differentiated service to different users based on PLMN subscription data. In addition, in a deployment it is possible that the company X's EES is one of many EESs managed by company Y's ECS (which also manages other company's EES). + +**Editor's note: Whether the edge service related information in PLMN subscription is stored in each EES or a central place by the EES provider is FFS.** + +Since this is a user contract subscription with EES providers and ECS may host multiple EESs provided by different ECSPs, the EEC needs to contact the EES(s) which is provided by EES service provider(s) holding valid PLMN subscription data for the user. This requires the EEC to provide its desired EES service provider(s) in the service provisioning procedure as depicted in figure 7.52.2-2. With such information, the ECS is able to provision the EEC with EES(s) based on EES registered provider information, i.e. if available, the ECS identifies the EES(s) based on the UE-specific service information (e.g. EES provider ID) at the ECS and the UE location. + +![Sequence diagram showing service provisioning request/response between EEC and ECS. The EEC sends a 'Service provisioning request (incl. EES provider ID)' to the ECS. The ECS responds with 'Process request' and then a 'Service provisioning response' back to the EEC.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant EEC + participant ECS + Note right of ECS: 2. Process request + EEC->>ECS: 1. Service provisioning request (incl. EES provider ID) + ECS-->>EEC: 3. Service provisioning response + +``` + +Sequence diagram showing service provisioning request/response between EEC and ECS. The EEC sends a 'Service provisioning request (incl. EES provider ID)' to the ECS. The ECS responds with 'Process request' and then a 'Service provisioning response' back to the EEC. + +**Figure 7.52.2-2: Service provisioning – Request/Response** + +Table 7.52.2-1 shows the additional impact for the information flow of the service provisioning request. + +**Table 7.52.2-1: Service provisioning request** + +| Information element | Status | Description | +|---------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------| +| EECID | M | Unique identifier of the EEC. | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| AC Profile(s) | O | Information about services the EEC wants to connect to, as described in Table 8.2.2-1. | +| EEC Service Continuity Support | O | Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC. | +| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) | +| Connectivity information | O | List of connectivity information for the UE, e.g. PLMN ID, SSID. | +| UE location | O | The location information of the UE. The UE location is described in clause 7.3.2. | +| EES provider identifiers | O | The list of desired EES provider IDs, by the EEC. | + +NOTE 3: The EES provider identifier is also applicable for the subscribe-notify model of service provisioning procedure (i.e. included in the service provisioning subscription request). This can be considered in the normative work. + +### 7.52.3 Solution evaluation + +This solution addresses KI#12 which enables EEL service differentiation. The EES is able to distinguish different users and applies different policies for the user based on subscription information. In order to address the correct EES having the corresponding PLMN subscription data for the user, the ECS is able to identify the EES(s) during service provisioning procedure based on EEC supplied EES provider identifier and registered EES provider identifier. + +## 7.53 Solution #53: Support for EAS synchronization + +### 7.53.1 Architecture enhancements + +None. + +### 7.53.2 Solution description + +#### 7.53.2.1 EAS Discovery to request support for content synchronization + +Figure 7.53.2.1-1 illustrates a scenario of EAS Discovery to request support for content synchronization. To indicate support for content synchronization, the EAS may include an indication in EAS registration request. The EES requests the EES to discover other EASs who are involved in same group. The EES discovers EASs with same EASID and checks whether required group is available or not. + +Pre-conditions: + +- 1) EAS-1 and EAS-2 are from different service providers and are registered with EES. +- 2) EAS-1 and EAS-2 support content synchronization. + +![Sequence diagram illustrating EAS Discovery to request for content synchronization. The diagram shows three lifelines: EAS-1, EES, and EAS-2. The sequence of messages is: 1. EAS-2 sends an EAS Registration (Indication to support content sync) to EES. 2. EAS-1 sends an EAS Discovery request (with indication for content synchronization) to EES. 3. EES performs an internal action: Discover EAS based on different parameters (ACID, Schedule, Service provider). 4. EES sends an EAS discovery response to EAS-1. 5. A horizontal bar at the bottom indicates Content synchronization between EAS-1 and EAS-2.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` + +sequenceDiagram + participant EAS-1 + participant EES + participant EAS-2 + Note right of EES: 1. EAS Registration (Indication to support content sync) + EAS-2->>EES: 1. EAS Registration (Indication to support content sync) + Note left of EES: 2. EAS Discovery request (with indication for content synchronization) + EAS-1->>EES: 2. EAS Discovery request (with indication for content synchronization) + Note right of EES: 3. Discover EAS based on different parameters (ACID, Schedule, Service provider) + EES->>EAS-1: 4. EAS discovery response + Note bottom: 5. Content synchronization + +``` + +Sequence diagram illustrating EAS Discovery to request for content synchronization. The diagram shows three lifelines: EAS-1, EES, and EAS-2. The sequence of messages is: 1. EAS-2 sends an EAS Registration (Indication to support content sync) to EES. 2. EAS-1 sends an EAS Discovery request (with indication for content synchronization) to EES. 3. EES performs an internal action: Discover EAS based on different parameters (ACID, Schedule, Service provider). 4. EES sends an EAS discovery response to EAS-1. 5. A horizontal bar at the bottom indicates Content synchronization between EAS-1 and EAS-2. + +**Figure 7.53.2.1-1: EAS Discovery to request for content synchronization** + +- 1) The EAS-2 performs EAS registration with EES as specified in 3GPP TS 23.558. In the registration request, the EAS includes indication to support content synchronization; +- 2) The EAS-1 sends EAS discovery request to discover EAS as specified in clause 8.8.3.2 of 3GPP TS 23.558 to EES indicating the request is to initiate content sharing with discovered EAS(s). The request may include group identity. +- 3) Upon receiving the request, the EES authorizes the EAS, and if the EAS is authorized to discover the EAS information, the EES identifies the EAS(s) based on the provided EAS discovery filters and EAS(s) supporting content synchronization. To apply discovery filters, the EES matches the ACID(s), schedule of the EAS, EAS Geographical Service Area, EAS Topological Service Area, etc. + +NOTE 1: How group id and interaction between EES and EAS to discover EAS will be considered in normative work. + +- 4) The EES sends the EAS discovery response to EAS-1 including list of EAS(s) which supports content synchronization. +- 5) EAS-1 and EAS-2 synchronizes the content which is out of scope of this specification. + +### 7.53.3 Solution evaluation + +The solution address the KI#13 and specifically to open issue 2. The solution enhances the EAS registration and Target EAS discovery procedure. The solution enables the EAS to discover another EAS(s) with support for content synchronization. + +## 7.54 Solution #54: EEL assist the application layer to determine the common EAS + +### 7.54.1 Architecture enhancements + +This solution is based on architecture option in clause 6.5.1. + +### 7.54.2 Solution description + +#### 7.54.2.1 General + +The following solution corresponds to the key issue#17: Discovery of a common EAS. + +The scenario assumption is the Edge enabler layer can provide a mechanism to support common EAS selection for the centralized group management server, and the group information is created by a centralized group management server (e.g. login server for gaming), meanwhile the association between the user and group is also managed by the centralized group management server. The EEL should provide the supporting service to assist the centralized group management server for the EAS selection. This solution is used for the dynamic group to discover a common EAS. + +![Diagram illustrating the scenario for EEL assisting the application layer. At the top, a 'Center cloud' contains a 'Login server'. Below it, two 'UE' (User Equipment) icons, labeled 'UE#1' and 'UE#2', are connected to the 'Login server' via blue lines. The 'Login server' is connected to two 'Gaming server' boxes, 'Gaming server #1 (EAS#1)' and 'Gaming server #2 (EAS#2)'. Each gaming server box contains an 'EES' (Edge Enabler Server) icon and an 'EDN' (Edge Data Network) icon. Red arrows point from 'UE#1' and 'UE#2' to the 'EES#1' and 'EES#2' respectively. Green arrows labeled 'Provide service deployment information' point from the 'Login server' to both 'EES#1' and 'EES#2'. A box labeled 'ECS' is connected to both 'EES#1' and 'EES#2' via grey lines.](18722c46c9e8475524e634dedd08bac2_img.jpg) + +Diagram illustrating the scenario for EEL assisting the application layer. At the top, a 'Center cloud' contains a 'Login server'. Below it, two 'UE' (User Equipment) icons, labeled 'UE#1' and 'UE#2', are connected to the 'Login server' via blue lines. The 'Login server' is connected to two 'Gaming server' boxes, 'Gaming server #1 (EAS#1)' and 'Gaming server #2 (EAS#2)'. Each gaming server box contains an 'EES' (Edge Enabler Server) icon and an 'EDN' (Edge Data Network) icon. Red arrows point from 'UE#1' and 'UE#2' to the 'EES#1' and 'EES#2' respectively. Green arrows labeled 'Provide service deployment information' point from the 'Login server' to both 'EES#1' and 'EES#2'. A box labeled 'ECS' is connected to both 'EES#1' and 'EES#2' via grey lines. + +Figure 7.54.2.1-1: Scenario for EEL assisting the application layer + +#### 7.54.2.2 Procedure + +In this solution, the centralized group management server (e.g. login server for gaming) is responsible to determine the group, and the group information is also maintained by the centralized group management server. The EEL only provide the Edge deployment information to the centralized group management server. Furthermore, this solution is intend to provide the assist for the centralize group management server (e.g. login server for gaming) and this solution will not impact the R17 EDGEAPP architecture. Besides, the centralized group management server can be the CAS which has the capability to allocate and manage the group. + +Pre-conditions: + +1. CAS allocated the group and manage the association between the user and group based on the service request from AC. + +- CAS can be pre-configured with the ECS address information based on the business relationship between ECSP and ASP. + +![Sequence diagram showing the interaction between AC, CAS, ECS, and EES. The sequence of messages is: 0. group allocation (CAS to ECS), 1. Service provisioning (CAS to ECS), 2. EAS discovery (CAS to EES), and 3. Common EAS information notification (CAS to AC).](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +``` + +sequenceDiagram + participant AC + participant CAS + participant ECS + participant EES + Note right of CAS: 0. group allocation + CAS->>ECS: 1. Service provisioning + Note right of CAS: 2. EAS discovery + CAS->>EES: + Note right of CAS: 3. Common EAS information notification + CAS->>AC: + +``` + +Sequence diagram showing the interaction between AC, CAS, ECS, and EES. The sequence of messages is: 0. group allocation (CAS to ECS), 1. Service provisioning (CAS to ECS), 2. EAS discovery (CAS to EES), and 3. Common EAS information notification (CAS to AC). + +**Figure 7.54.2.2-1: EEL assisting the application layer** + +- The CAS send the service provisioning request message to the ECS. The request message contains the group location information based on the UE location of the certain group. The ECS can return the EES information based on the group location information. +- Then the CAS send the EAS discovery request message to the EES. The request message contains AC information and the group location information based on the UE location of the certain group. The EES can return the EAS information based on the AC information and the group location information. +- Upon receiving the EAS information, the CAS send the common EAS information to the AC which in the certain group. + +NOTE 1: When UE group location changed due to UE join/leave, the CAS can determine whether the common EAS need to be changed. + +NOTE 2: CAS can perform the service provisioning and EAS discovery procedure. + +NOTE 3: Any impacts due to new entity CAS triggering service provisioning and EAS discovery shall be considered during the normative phase. + +NOTE 4: The interaction between AC and EAS is out of 3GPP scope. + +### 7.54.3 Solution evaluation + +This clause provides an evaluation of the solution. + +This solution address KI#17. This solution is used for the dynamic group case, the EEL provide the service provisioning service and EAS discovery service to the application layer (e.g. centralized group management server). The EEL implementation will not be impacted in this solution. This is a viable solution. + +## 7.55 Solution #55: Non-roaming UE location invocation + +### 7.55.1 Architecture enhancements + +None. + +### 7.55.2 Solution description + +#### 7.55.2.1 General + +This solution addresses key issue 22 + +The edge resource of OP A need to know OP B's information to invoke UE location information. The OP A's EES or EAS should receive OP B's information by EAS discovery request or pre configure by agreement OP A with OP B. + +Operator A's entities can invoke operator B's NEF using the PLMN information provided from the EAS discovery request message. The EES A can obtain the PLMNID of the service provider B from the EAS discovery request of the EES B. The EES A may request the terminal location from the NEF B by utilizing the obtained PLMNID of the business operator B. + +Editor's note: It is FFS whether the solution is used to solve the solution#43, 44, 45. + +Editor's note: It is FFS whether the EES#a need to obtain this information from OP B's NEF in solution #43 and 44. + +**Table 7.26.2.1-2: EAS discovery request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Requestor identifier | M | The ID of the requestor (e.g. EECID) | +| UE Identifier | O | The identifier of the UE (i.e. GPSI or identity token) | +| Security credentials | M | Security credentials resulting from a successful authorization for the edge computing service. | +| EAS discovery filters | O | Set of characteristics to determine required EASs, as detailed in Table 8.5.3.2-2. | +| UE location | O | The location information of the UE. The UE location is described in clause 7.3.2. | +| Connectivity information | O | List of connectivity information for the UE, e.g. PLMN ID | +| Target DNAI (NOTE) | O | Target DNAI information which can be associated with potential T-EAS(s) | +| EEC Service Continuity Support | O | Indicates if the EEC supports service continuity or not. The IE also indicates which ACR scenarios are supported by the EEC or, if this message is sent by the EEC to discover a T-EAS, which ACR scenario(s) are intended to be used for the ACR. | +| EES Service Continuity Support (NOTE) | O | The IE indicates if the S-EES supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EES or, if the EAS discovery is used for an S-EES executed ACR according to clause 8.8.2.5, which ACR scenario is to be used for the ACR. | +| EAS Service Continuity Support (NOTE) | O | The IE indicates if the S-EAS supports service continuity or not. The IE also indicates which ACR scenarios are supported by the S-EAS or, if the EAS discovery is used for an S-EAS decided ACR according to clause 8.8.2.4, which ACR scenario is to be used for the ACR. | +| NOTE: This IE shall not be included when the request originates from the EEC. | | | + +#### 7.55.2.2 Non-roaming UE location invocation of EES + +Pre-conditions: + +1. OP A may have a PLMN address of OP B as a network agreement with OP B; +2. When the EEC requests service provisioning to the ECS, it may include PLMN information serving the UE; + +NOTE 1: At least one of the above operations shall be performed. + +![Sequence diagram showing UE location invocation from EES A to NEF B. Step 1: EES A determines if UE location is required and sends an invoke message to NEF B. Step 2: NEF B performs a UE location check or subscription and sends a notification back to EES A.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant EES A + participant NEF B + Note right of EES A: 1. Determine or detect whether the UE location is required or received UE location invoke message from the EAS. + EES A->>NEF B: + Note right of NEF B: 2. UE location check or subscription and UE location notification + NEF B->>EES A: + +``` + +Sequence diagram showing UE location invocation from EES A to NEF B. Step 1: EES A determines if UE location is required and sends an invoke message to NEF B. Step 2: NEF B performs a UE location check or subscription and sends a notification back to EES A. + +**Figure 7.55.2-1: UE location invocation to the OPB's NEF** + +In Figure 7.55.2-2, The EES A or EAS A may obtain an NEF B address through an edge node sharing agreement between OP A and OP B. The EES A may also receive an EAS A discovery request message from the EES B, including OP B information. This enhances the UE location API, one of the EES exposure function to EAS in TS 23.558 8.6.2. + +- 1 EES A can receive UE location API call messages from EAS A or capture services that require UE location (e.g. UE location tracking, UP route management event notification, traffic impact, etc.) EES A may generate UE location request messages using PLMN ID,, and UEID. + +2. The EES A may check or subscription UE location information to the NEF B. + +If EAS A can use NEF B's API, it may directly send a UE location information request message or a UE location subscription request message. + +NOTE: The EES utilizes the capabilities of the 3GPP core network as specified in clause TS 23.558 8.10.3. + +The NEF B can perform a procedure to authenticate the requested edge entity and UE by checking the UEID and PLMN ID in the message sent by EES A. + +The NEF B may send UE location information in the notification. + +If EES A receives a UE location invoke message from EAS A, EES A may provide UE location information to EAS A. or; + +When the NEF B receives a request for UE location information from the EAS A, the NEF B may send the UE location information in the notification message and provide the UE location to the EAS A. + +### 7.55.3 Solution evaluation + +This solution introduces how OP B's EAS and EES acquire UE location information using OP A's network functions of when using edge resources of service providers that are not subscribed by UE in ENS scenarios. + +# 8 Deployment scenarios + +NOTE: Deployment models based on conclusions of Key issues will be considered in the normative work. + +# 9 Involved entities and relationships + +## 9.1 Federation and Roaming + +### 9.1.1 General + +This clause describes the relationship of edge computing service providers, PLMN operators, application service providers and end users, taking federation and roaming into account. + +![Diagram illustrating the relationships involved in edge computing service – federation and roaming. The diagram shows four main entities: Application service provider(s), End user, Edge computing service provider A, and PLMN operator X. The Application service provider(s) is connected to the End user via an 'ASP service agreement(s)'. The Application service provider(s) is also connected to the Edge computing service provider A via an 'Edge computing service provider service agreement(s)'. The End user is connected to the PLMN operator X via a 'PLMN subscription arrangement'. The Edge computing service provider A is connected to the PLMN operator X via a 'PLMN operator service agreement(s)'. The Edge computing service provider A is also connected to the Edge computing service provider B via a 'Federation agreement'. The PLMN operator X is connected to the PLMN operator Y via a 'Service agreement'. The End user is also connected to the Edge computing service provider A via 'Edge service authorization(s)'.](12de9b926df0384ec07702671827c9cd_img.jpg) + +``` + +graph TD + ASP((Application service provider(s))) <--> |"ASP service agreement(s)"| EU((End user)) + ASP <--> |"Edge computing service provider service agreement(s)"| ECSPA((Edge computing service provider A)) + EU <--> |"PLMN subscription arrangement"| PLMNX((PLMN operator X)) + ECSPA <--> |"PLMN operator service agreement(s)"| PLMNX + ECSPA <--> |"Federation agreement"| ECSPB((Edge computing service provider B)) + PLMNX <--> |"Service agreement"| PLMNY((PLMN operator Y)) + EU <--> |"Edge service authorization(s)"| ECSPA + +``` + +Diagram illustrating the relationships involved in edge computing service – federation and roaming. The diagram shows four main entities: Application service provider(s), End user, Edge computing service provider A, and PLMN operator X. The Application service provider(s) is connected to the End user via an 'ASP service agreement(s)'. The Application service provider(s) is also connected to the Edge computing service provider A via an 'Edge computing service provider service agreement(s)'. The End user is connected to the PLMN operator X via a 'PLMN subscription arrangement'. The Edge computing service provider A is connected to the PLMN operator X via a 'PLMN operator service agreement(s)'. The Edge computing service provider A is also connected to the Edge computing service provider B via a 'Federation agreement'. The PLMN operator X is connected to the PLMN operator Y via a 'Service agreement'. The End user is also connected to the Edge computing service provider A via 'Edge service authorization(s)'. + +**Figure 9.1.1: Relationships involved in edge computing service – federation and roaming** + +The end user is the consumer of the applications provided by the application service provider (ASP). End user: + +- can have ASP service agreement with a single or multiple application service providers. +- has a PLMN subscription arrangement with a PLMN operator (HPLMN). The UE used by the end user can register on the HPLMN network and network of its roaming partners. +- can have authorization to access edge services of a single or multiple ECSPs. + +The ASP consumes the edge services (e.g. infrastructure, platform) provided by the ECSP. ASP: + +- can have edge computing service provider service agreement with a single or multiple ECSPs. + +The PLMN operator provides connectivity between the end user and the edge services provided by the ECSP. PLMN operator: + +- can have the PLMN operator service agreement with a single or multiple ECSPs. +- can have service agreement for roaming including agreements for Edge Computing services, and/or federation with a single or multiple PLMN operators. + +The ECSP provides the edge services. ECSP: + +- can have PLMN operator service agreement with a single or multiple PLMN operators which provide edge computing support. +- can have federation partnership to share edge services with a single or multiple ECSPs. + +The ECSP and the PLMN operator can be part of the same organization. + +# --- 10 Overall evaluation + +## 10.0 General + +This clause provides a summary of architecture enhancements and solution evaluations and related solution assumptions. The evaluations and solutions are applicable only for the corresponding scenario assumptions.. + +## 10.1 Architecture enhancements + +#### 10.1.1 Support for Terminal Equipment (TE) + +The architecture enhancement captured as option#4 introduces support for TEs in the EdgeApp architecture. The interface between the TEs and the UEs running the EEC is out of scope of SA6. + +With this enhancements ACs running on a TE will be able to communicate with the EEC running on a UE to avail services of the EEC over EDGE-5 interface. No specific enhancement over EDGE-5 is identified during the study to support this functionality. + +### 10.1.2 Roaming architecture + +The architecture enhancement captured as option#1 introduces two ways to support roaming UEs hosting the EEC in the EdgeApp architecture as follows: + +- Local breakout roaming architecture: Local breakout to access H-ECS + +This architecture uses H-ECS and V-ECS associated with HPLMN and VPLMN, respectively. In the LBO roaming scenario, the EEC is able to communicate with the H-ECS to obtain the information for V-ECS via Local Breakout Session. Likewise, the EEC accesses V-ECS and V-EES via Local Breakout Session. + +A new reference point EDGE-10 is defined between H-ECS and V-ECS to support for the EEC in the roaming UE to access V-ECS. + +- Home-routed roaming architecture: Home routed EDGE-4 access to H-ECS + +In the HR roaming scenario, the roaming architecture assumes that the local access to the EDN of the VPLMN is supported for the UE hosting the EEC via HR roaming session. The traffic toward the EDN of the VPLMN (i.e. EDGE-1 traffic and application data traffic) is not routed via the HPLMN while the traffic between the EEC and H-ECS is routed via VPLMN toward HPLMN. Such a local access to the EDN of the VPLMN in the scenario where HR roaming session is used requires enhancements in 5G core networks, which in the scope of SA2. + +A new reference point EDGE-10 is defined between H-ECS and V-ECS to support for the EEC in the roaming UE to access V-ECS. + +### 10.1.3 Architecture for Federation and Roaming + +The architecture enhancement captured as option#12 enhances the ECS with a new functionality of an Edge Repository. The enhanced ECS accepts registration of other ECSs of the ECSP. The ECS registration also enables ECS to publish their registered EASS information and the enhanced ECS maintains information of which application is available via which ECS for the ECSP. + +With this enhancement, an ECS can query the ECS-ER to find partner ECS(s) that provide the required application. This improves the accuracy and reduces the time taken to generate the service provisioning response sent to the EEC or the EES; therefore improving the chances of service continuity during ACR procedures. + +## 10.2 Key issue evaluations + +### 10.2.0 General + +All the key issues and solutions specified in this technical report are listed in Table 10.2.0-1. + +The table provides a mapping of the key issues to the related solutions. It also lists the dependencies on other working groups. + +#### **Table 10.2.0-1 Key issue and solutions** + +| Key issues
(evaluation clause reference) | Solution | Solution
(clause reference) | | Dependency on
other working
groups | +|-----------------------------------------------------------|----------------------------------------------------------------------------------------------------|--------------------------------|-----|------------------------------------------| +| Key issue #1: Enhanced notification service to the EEC | Solution #1: Service provisioning via push notification | 7.1 | | | +| | Solution #3: Service provisioning triggering via SMS over NAS | 7.3 | | | +| | Solution #20: Propagation of EEL notifications to EEC using Edge Notification Server | 7.20 | | | +| Key issue #2: Enablement of Service APIs exposed by EAS | Solution #8: EAS Service API enablement using CAPIF | 7.8 | | | +| | Solution #11: A deployment option for alignment with ETSI MEC using CAPIF | 7.11 | | | +| Key issue #3: Enhancements to service continuity planning | Solution #6: ACR update in service continuity planning | 7.6 | | | +| | Solution #7: EES monitors UE mobility for service continuity planning | 7.7 | | | +| | Solution #12: Service continuity planning permission | 7.12 | | | +| | Solution #21: Prediction expiration time for service continuity planning enhancement | 7.21 | | | +| | Solution #37: ACR request trigger timing | 7.37 | | | +| Key issue #4: EDGE-5 | Solution #22: Support simultaneous EAS connectivity in ACR | 7.22 | | SA3 | +| | Solution #34: EDGE-5 APIs | 7.34 | | | +| Key issue #5: Alignment of EDGEAPP and ETSI MEC | Solution #11: A deployment option for alignment with ETSI MEC using CAPIF | 7.11 | | SA5 | +| | Solution #36: Alignment of EDGEAPP and ETSI MEC | 7.36 | SA5 | | +| Key issue #6: Edge services support across ECSPs | Solution #4: ECS discovery through serving ECS to support edge services across ECSPs | 7.4 | | | +| | Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs | 7.5 | | | +| | Solution #13: Update ECS configuration information | 7.13 | | SA2 | +| | Solution #43: EAS discovery for Edge node sharing | 7.43 | | | +| | Solution 50: Enhanced ECS for federation of services | 7.50 | | SA3 | +| Key issue #7: Application traffic filter exposure | Solution #2: Traffic filter support for EDGE-3 API addressing application traffic detection | 7.2 | | | +| Key issue #8: EAS selection synchronization | Solution #15: Initial EAS selection declaration | 7.15 | | | + +| Key issues
(evaluation clause reference) | Solution | Solution
(clause reference) | | Dependency on
other working
groups | +|--------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------|--|------------------------------------------| +| | Solution #39: EAS selection synchronization at registration | 7.39 | | | +| Key issue #9: Enhancement of dynamic EAS instantiation triggering | Solution #32: Dynamic EAS instantiation triggering and notification | 7.32 | | SA5 | +| | Solution #33: Support for EEC Discovery of EAS(es) before instantiation | 7.33 | | SA5 | +| | Solution #40: EAS instantiation status provisioned by ECS | 7.40 | | SA5 | +| | Solution #42: EAS selection and instantiation in EES | 7.42 | | SA5 | +| Key issue #10: Support for roaming UEs | Solution #4: ECS discovery through serving ECS to support edge services across ECSPs | 7.4 | | SA3 | +| | Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs | 7.5 | | SA3 | +| | Solution #13: Update ECS configuration information | 7.13 | | SA2 | +| | Solution #14: V-ECS Discovery via the H-ECS | 7.14 | | SA3 | +| | Solution 50: Enhanced ECS for federation of services | 7.50 | | SA3 | +| Key issue #11: ACR between EAS and Cloud Application Server | Solution #24: ACR between CAS and EAS | 7.24 | | | +| | Solution #25: ACR between EAS and Cloud Application Server | 7.25 | | | +| Key issue #12: EEL service differentiation | Solution #12: Service continuity planning permission | 7.12 | | | +| | Solution #16: EAS discovery for different users | 7.16 | | | +| | Solution #51: EEC sharing UE Mobility requirement | 7.51 | | | +| Key issue #13: Edge enabler layer support for EAS synchronization | Solution #31: Discover common EAS | 7.31 | | | +| | Solution #53: Support for EAS synchronization | 7.53 | | | +| Key issue #14: Application traffic influence for initially selected EAS | Solution #9: Application traffic influence trigger from EAS | 7.9 | | | +| | Solution #15: Initial EAS selection declaration | 7.15 | | | +| | Solution #17: Traffic influence for initial EAS discovery | 7.17 | | | +| Key issue #15: Support of constrained devices for Edge | Solution #10: low power mode support | 7.10 | | | +| | Solution #18: Constraint device in EDGEAPP | 7.18 | | | +| Key issue #16: support of NAT deployed within the edge data network | Solution #23: UE identification with NAT | 7.23 | | SA2, SA3 | +| Key issue #17: Discovery of a common EAS | Solution #27: Enabling AC Association Aware services by selecting common EASs | 7.27 | | | + +| Key issues
(evaluation clause reference) | Solution | Solution
(clause reference) | | Dependency on
other working
groups | +|-------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------|--|------------------------------------------| +| | Solution #28: Common EAS discovery using EAS selection information | 7.28 | | | +| | Solution #29: Discovery of a common EAS | 7.29 | | | +| | Solution #30: Common EAS selection | 7.30 | | | +| | Solution #31: Discover common EAS | 7.31 | | | +| | Solution #54: EEL assist the application layer to determine the common EAS | 7.54 | | | +| Key issue #18: EAS bundles | Solution #26: Bundled EASs | 7.26 | | | +| | Solution #46: EEC selected ACR scenario for EAS bundles | 7.46 | | | +| | Solution #47: EES determines the selected ACR scenario for EAS bundles | 7.47 | | | +| Key issue #19: ACR scenario combination | Solution #19: EES determines the selected ACR scenario | 7.19 | | | +| | Solution #35: EEC selected ACR scenarios | 7.35 | | | +| | Solution #38: ACR coordination | 7.38 | | | +| Key issue #20: Supporting composite EASs | Solution #49: ACR for EAS composition | 7.49 | | | +| Key issue #21: Simultaneously EAS connectivity in ACR | Solution #22: Support simultaneous EAS connectivity in ACR | 7.22 | | | +| Key issue #22: EAS discovery in Edge Node sharing scenario | Solution #43: EAS discovery for Edge node sharing | 7.43 | | | +| | Solution #44: EAS discovery for Edge node sharing | 7.44 | | | +| | Solution #45: EAS discovery in Edge Node sharing scenario | 7.45 | | | +| | Solution #55: Non-roaming UE location invocation | 7.55 | | | +| Key issue #23: Reliable Edge service | Solution #48: Edge server set and edge service set | 7.48 | | | +| Key issue #24: SEAL capability access for EEL support | Solution #41: Interaction with ADAES for edge load analytics | 7.41 | | | + +#### 10.2.1 Key issue #1: Enhanced notification service to the EEC + +The open issues studied in the key issue #1 are as follows: + +1. Whether and how the EEC acquires the notification target address or a notification channel URI to receive the notifications? +2. Whether and how EEC, ECS and EES support push notification mechanism. Whether and what additional functional entity is necessary for this? +3. How are the EEC subscriptions and/or notification targets treated in mobility scenario (e.g. during ACR scenario)? + +4. Whether and how to utilize application triggering method specified in 3GPP TS 23.501 [5] to provide notifications to the EEC? + +To address the open issues aforementioned, there are three solutions proposed as follows: + +- Solution #1: Service provisioning via push notification + - It utilizes the push notification mechanism to enhance the service provisioning procedure, assuming that at least one push server is available to ECS and the UE has push function supporting the interaction with the push server. +- Solution #3: Service provisioning triggering via SMS over NAS + - It utilizes application triggering (device triggering) via SMS over NAS method specified in 3GPP TS 23.501 [5] to inform the EEC of the need to perform service provisioning. +- Solution #20: Propagation of EEL notifications to EEC using Edge Notification Server + - It proposes a centralized notification server, called Edge Notification Server, to enhance EEL's notifications delivery mechanism to EEC. The proposed Edge Notification Server interacts with EEC, EES and ECS respectively via the newly proposed interfaces as described in the clause 6.3. + +The Solution #1 provides detailed operations of EEC and ECS to enable the service provisioning via the push notification mechanism. + +The Solution #3 provides a detailed interaction between EEC and ECS to check if the SMS over NAS is supported and accompanied EDGE-8 operation of ECS for triggering EEC to perform service provisioning request. + +The Solution #20 provides architecture enhancements using an Edge Notification Server, which is an optional functional entity. It also proposes a detailed role of the Edge Notification Server and procedures between ENS and other functional entities (EEC, EES and ECS). The Edge Notification Server functionality will be specified as generic notification service in SEAL TS 23.434 [23] by generalizing to vertical applications. Edge Notification Server functionality leverages generic notification service from SEAL TS 23.434 [23]. + +The above enhanced notification services utilizing push notification, application triggering via SMS over NAS and leveraging generic notification service from SEAL in lieu of Edge Notification Server will be addressed in the normative phase. + +Push notification service in Solution #20 will be leveraged (including generic notification service from SEAL TS 23.434) by Solution #1, during service provisioning. + +#### 10.2.2 Key issue #2: Enablement of Service APIs exposed by EAS + +The open issues studied in the key issue #2 are as follows: + +1. Identify any gaps in CAPIF to enable EAS Service APIs in the EDGEAPP architecture in terms of e.g. service-specific attributes for API publish/discovery, API availability subscription/notification across EES/CCF +2. If any, whether and how to enhance CAPIF capabilities to address the gap identified as above + +In order to address the open issues aforementioned, there are two solutions proposed as follows: + +- Solution #8: EAS Service API enablement using CAPIF + - It exploits CAPIF as specified in 3GPP TS 23.222 [16] to support publication/discovery, and change subscription of EAS Service APIs for API invoking by the other EASs +- Solution #11: A deployment option for alignment with ETSI MEC using CAPIF + - It exploits CAPIF as specified in 3GPP TS 23.222 [16] as a deployment option for exposing EAS Service APIs to ETSI MEC entities (i.e. MEP and MEC applications) + +The Solution #8 provides 1) a detailed role of EAS and EES as CAPIF entities in order to support publication/discovery, and change subscription of EAS Service APIs; and 2) a new IE, Service KPIs, for CAPIF APIs. + +The Solution #11 provides a detailed role of EAS and EES as CAPIF entities in order to support discovery and invocation of EAS Service APIs for ETSI MEC entities. + +EES supporting EAS's and other entity's (e.g. ETSI MEP or MEC App.) access to service APIs exposed by other EAS, in the context of CAPIF, will be addressed in the normative phase. The newly identified IE for CAPIF APIs has an impact to 3GPP TS 23.222 [16] to be addressed in the normative phase. + +#### 10.2.3 Key issue #3: Enhancements to service continuity planning + +The open issues studied in the Key Issue#3 are as follows: + +Open Issues: + +1. How to rely on the capability of EES/EEC to detect whether the UE moves to the predicted location or not for service continuity planning? +2. Whether and how the EEL can support the determination of the ACR request trigger timing in case of service continuity planning? +3. How to deal with scenarios when the ACR needs to be modified, e.g. due to UE mobility? +4. Whether and what additional capability exposure is required from the 5GS (e.g. NWDAF, OAM) to enhance the service continuity planning? +5. Potential impact on information exchanged between EAS and EEL. +6. Potential impact on information to communicate within the EEL. + +This clause provides an overall evaluation of the key issue #3: Enhancements to service continuity planning. The solution #6, solution #7, solution#12, solution#21, solution#37 cover different aspects for the open issue in the KI#3. + +Solution#6 addresses the open issue #3 by introducing a new procedure to modify ACR parameters. Specifying the signaling required for the procedure are to be addressed in the normative phase (without impacting AC). + +The solution #7 is used for solving the open issue#6. And solution #7 is applicable to the scenario where the EAS may not have the capability of monitoring the UE mobility for service continuity planning. Solution #7 will not impact the EDGEAPP architecture defined in the Rel-17. + +The Solution #12 enables to allow the service continuity planning selectively for a given UE or an application. This principle of Solution # 12 is that the permission of service continuity planning can be determined by the EES for the purpose of service differentiation, then the EEC performs the required detection or acquisition of the planned or predicted UE mobility behaviour for the EASs allowed for service continuity planning according to the determined ACR modes. The principle of solution #12 is to be addressed in the normative work. Further investigation in normative work is required for sol#12 to evaluate backward compatibility issue in this solution. + +Solution #21 addresses KI#3 by including a prediction expiration time within ACR request from the EEC. This information can be used by T-EAS to adjust its waiting time for the UE to reach the service area. It is proposed to update the ACR request in normative phase to include prediction expiration time. + +Solution #37 covers open issue #2, open issue #5, and open issue #6 of KI#3. It introduces "General context holding timing" IE in the EAS profile. This information can be used by the EEC to trigger ACR request before reaching T-EAS service area when predicted or planned to move to the service area within the time provided in the IE. It is proposed to update TS 23.558 according to what is proposed in solution #37 in the normative phase. + +#### 10.2.4 Key issue #4: EDGE-5 + +KI#4 required study of multiple open issues related to the interface between the Application Client and the Edge Enabler Client. + +Solution #34 provides a set of procedures that fulfil the open issues. No need to modify the cardinalities of EDGE-5 interface were identified during the study. The solution provides methods for an AC to register to an EEC, perform EAS discovery, perform ACR related requests in different modes and subscribe for EEC capabilities. Architecture enhancement option#4 depicts how constrained devices such as TEs can utilize EDGE-5 to communicate with an EEC running on a UE. + +No need was identified during the study to provide methods for discovery of EECs by the AC or for detection of abnormal termination of EEC or ACs. + +Aspects related to mutual authentication, authorization and user consent are SA3's responsibility. Any recommendation from SA3 shall be considered during normative phase. + +NOTE: Coordination with CT groups is required for this KI. + +#### 10.2.5 Key issue #5: Alignment of EDGEAPP and ETSI MEC + +The open issues of this KI are as follows: + +1. Study and analyse different deployment options of EDGEAPP and ETSI MEC platforms. +2. Functional architecture and gap analysis between EDGEAPP and ETSI MEC to determine complementary and possibly overlapping APIs and other related functionalities. Annex A captures a comparison of the architectures to facilitate the gap analysis. +3. Recommendation and enhancements based upon the outcome of (1) and (2). + +The principle and requirements for the alignment of EDGEAPP and ETSI MEC have been captured in clause 5.4, where the following alignment aspects have been listed: + +- a. alignment of EAS profile (EDGEAPP) and appInfo (ETSI MEC), +- b. alignment of EDGE-3/Mp1 reference points +- c. alignment of EDGE-9/Mp3 reference points +- d. usage of CAPIF between the two architectures + +Additionally, two solutions have been proposed to address the above open issues: + +- Solution #11: This solution relies on the EDGEAPP architecture as specified in TS 23.558 [2] and CAPIF as specified in TS 23.222 [16]. + - The solution extends the roles of EAS, EES and ETSI MEC entities like MEP as CAPIF entities to support the alignment of discovery and invocation of EES/EAS Service APIs and MEC Services by ETSI MEC and EDGEAPP entities, respectively. + - The solution addresses alignment aspect d in clause 5.4. +- Solution #36: This solution is based on the principles set in clause 5.4 and provides a mapping between overlapping APIs in EDGEAPP and ETSI MEC. + - The solution addresses the alignment aspects a, b and c in clause 5.4. + - The solution enables the application to perform registration on EES according to the mapping between appInfo [14] and EAS profile. This aspect of the solution addresses the alignment aspects a and b in clause 5.4. + - The solution in the present study does not identify overlap or equivalent functionality between the APIs on EDGE-9 and Mp3 interfaces; therefore, currently no alignment is required. This aspect of the solution addresses the alignment aspect c in clause 5.4. + +The solutions do not require changes in architecture and procedures. + +### 10.2.6 Key issue #6: Edge services support across ECSPs + +The open issues of this KI are as follows: + +1. Identify potential enhancements to the existing architecture defined in Rel-17 to enable inter-ECSP interactions. +2. Study potential impact to support ECS discovery and service provisioning based on UE location. + +3. Whether and how EEC registers with an EES deployed by a partner ECSP? +4. Study potential impact to support service continuity. +5. How is EEC context continuity maintained across ECSPs with or without ACR? +6. How the ECS can discover a T-EES having SLA with S-EES based on the federation agreements between ECSPs before EDGE-9 interaction? + +To address the open issues the following solutions has been proposed: + +- Solution #4: ECS discovery through serving ECS to support edge services across ECSPs + - After discovering another ECS2 which may have suitable EES, the ECS1 sends respond to the EEC or source EES with the ECS2 information. Then the EEC or source EES can send the request to the ECS2 directly to retrieve suitable EES. + - Solution #4 relies on having sufficient information (e.g. ECSP policy, UE-specific service information, or ECSs information) configured or available in an ECS to determine candidate. +- Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs + - The EEC or the EES gets the requested EES information from ECS2 via ECS1. If the ECS1 cannot discover a suitable EES to serve the UE at the current location (e.g. all the EESs registered on the ECS1 do not cover the given UE location), the ECS1 contacts another ECS2 which may have suitable EES and discovers the EES via ECS2. + - Solution #5 relies on preconfigured information of ECS2 at ECS1. + +NOTE: In Solutions #4 and #5, to configure sufficient information to the ECS, the ECS(s) information related to other ECSPs may be available at the OAM system due to the inter-ECSP relationship establishment, which is then used by the OAM system of an ECSP to configure its ECS. If required, the information of available applications in a partner ECSP and the corresponding service areas are included in the configured information. Inter-ECSP relationship establishment is according to the business relationship between the ECSPs and is out of the scope of SA6. The OAM to configure its ECS for inter-ECSP relationship is under the scope of SA5. + +- Solution #13: Update ECS configuration information + - This solution proposes to include additional optional IEs in the ECS configuration information. The information can be used in solutions 4 and 5 to find and select ECS2. ECS information shared in Solution 13 is limited to the ECSs whose information is available through H-PLMN. +- Solution #50: Enhanced ECS for federation of services + - When configured information is not available with the ECS, with the enhancement proposed in this solution ECS can query an ECS-ER to obtain information of partner ECS that provide service provisioning for a particular application. This allows to reduce the time required to provide service provisioning response while ensuring that the required application is available. + +Solution #5 is applicable to scenarios where the UE has home routing agreement with its service provider for service provisioning. + +Solution #13 provides additional optional IEs to be used within solution #4 and #5 to find and select ECS2. + +Solution #50 can be used along with solution #4, solution #5 and solution #13. + +All the above solutions will use any agreed solution for determining ECS2 by ECS1. + +Detailed signalling to provide ECS2 address to the requesting EEC or EES based on solution #4 is to be addressed in normative phase. Signalling between ECS1 and ECS2 to discover and retrieve provisioning to the requesting EEC or T-EES for the requesting EES will be addressed in normative phase according to solution #5. A new interface EDGE-10 between ECS1 and ECS2 is used in Solution #5. Also, in normative phase, if required, the additional optional IEs are added to ECS configuration information provided by ECS to 5GC according to Solution #13. + +### 10.2.7 Key issue #7: Application traffic filter exposure + +The open issues studied in the key issue #7 are as follows: + +1. How to support more application traffic filter for session with QoS API. +2. How to support more application traffic filter for ACR management event API. + +To address the open issues aforementioned, solution 2 is proposed as follows: + +- Solution #2: Traffic filter support for EDGE-3 API addressing application traffic detection + - Allows the EAS to provide the domain name as traffic descriptor (indicates the applicable protocol and matching criteria) to the EES, which further invokes the PFD management procedure with the 3GPP CN as described in 3GPP TS 23.682 [10] and 3GPP TS 23.502 [8]. + +The Solution #2 provides detailed operation between EAS and EES for specific filters, and the EES invoking the PFD management procedure with the 3GPP CN. + +### 10.2.8 Key issue #8: EAS selection synchronization + +Solution #39 addresses KI#8 about how to enable the EES to leverage pre-existent EAS information at the EEC in order to enable service session communications efficiently for IoT devices. The solution proposes EAS selection request indicator to be sent in EEC registration request (for constrained device) to request the EES for EAS selection support. If the indication is present, the EES includes discovered EAS list along with EAS profile in the response. + +Solution #15 allows the EES to be informed of the EAS selected by EEC when the initial EAS services start, so that the EAS selection information is synchronized between the EEC and EES. This solution provides the option for registered + +EECs to use the existing EEC registration update to provide this information. It also provides the option, for any EEC, to use a new proposed API to provide this information to the EES. + +Solutions #39 and #15 are complementary and are both viable. + +### 10.2.9 Key issue #9: Enhancement of dynamic EAS instantiation triggering + +The open issues studied in the key issue #9 are as follows: + +1. What kind of information can be acquired by edge enabling layer and utilized by an EES to decide to trigger dynamic EAS instantiation and which entities can provide such information to an EES +2. Whether and how to support dynamic EAS termination triggering in order to enable dynamic scaling of EAS (i.e. scale in as needed). + +To address the first open issue, the following solutions have been proposed: + +- Solution #32: Dynamic EAS instantiation triggering and notification + - proposes that the EES determines if EAS instantiation triggering is needed when EAS discovery subscription request is received from the EEC and no available EAS instances are matched. + - proposes that the triggering determination is based on the EAS availability, according to the EAS discovery filter and EAS service load/capacity +- Solution #33: Support for EEC Discovery of EAS(es) before instantiation + - the pre-condition is that EAS instantiation status (e.g. instantiated or instantiable, but not yet instantiated) is not included in EES profile. + - proposes that the EEC obtains the EAS instantiation status in EAS profile through EAS discovery procedure. + - has the different EES behavior with R17 when receiving the EAS discovery request message, i.e. the EAS instantiation is suspended. + - proposes that the EES determines if EAS instantiation triggering is needed when it receives an EAS selection message from the EEC indicating the intention of the EEC to use an EAS. + - proposes that the triggering determination is based on the EEC intention of using an EAS and on the EAS availability. +- Solution #40: EAS instantiation status provisioned by ECS + - the pre-condition is that EAS instantiation status (e.g. instantiated or instantiable, but not yet instantiated) is included in EES profile. + - proposes that the EEC obtains the EAS instantiation status in EES profile through service provisioning procedure. + - proposes that the EEC performs EES selection according to the EAS instantiation status. + - proposes that the EES determines if EAS instantiation triggering is needed when it receives an EAS discovery message from EEC, this is consistent with R17, and no new message is introduced. + - proposes that the triggering determination is based on the EAS availability. +- Solution #42: EAS selection and instantiation in EES + - the pre-condition is that EAS instantiation status (e.g. instantiated or instantiable, but not yet instantiated) is not included in EES profile. + - proposes that the EEC indicates EES (e.g. via UE type) to request EES to select and instantiate (if needed) EAS. + - proposes that the triggering determination is based on the the EAS availability. + +Solutions high level overview: + +- Solution #32 clarifies aspects of EAS instantiation present in Rel-17 TS 23.558 and does not introduce new functionality. +- Solution #33, solution #40 and solution #42 introduce changes for making uninstantiated EAS identified before selecting one to minimize EAS resources usage in the EDN for use cases with different pre-conditions (e.g. whether the EAS instantiation status is included in the EES profile). + +An aspect cited in Key Issue #9 is how to "ensure efficient utilization of EDN resources for EAS deployment, it should be possible to have the proper number of EAS instances in the EDN to accommodate the load for applications" + +Solution #32 on EDN resource utilization + +- has the limitations of Rel-17: every possible EAS type (e.g. EASID) needs to be instantiated in every EDNs where they are offered to be discoverable, and every EES instance offering an EAS type must have at least one EAS instance registered to be discoverable. + +Solution #33, solution #40 and solution #42 on EDN resource utilization + +- improves Rel-17: all possible EAS types (e.g. EASIDs) do not need to be instantiated to be discoverable. + +Another aspect is the difference in EEC obtaining EAS instance. + +- In solution #33, EAS discovery procedure is enhanced to identify the EAS before instantiation, and introduce a new EAS selection message to obtain the instantiated EAS instance after successful instantiation. +- In solution #40 and solution #42, instantiated EAS instance is discovered in EAS discovery response after successful instantiation. + +The second open issue is not addressed by the above solutions. Thus, the second open issue will not be pursued in this release. It is not resolved how to address the issue that dynamic termination triggering may be triggered unexpectedly for an operator and has a significant impact on operational management. Scaling is also an operational aspect and is included in the scope of SA5. Main purpose of using scaling is to ensure a stable operation of a system or service. + +### 10.2.10 Key issue #10: Support for Roaming UEs + +This clause provides an overall evaluation for Key Issue #10, "Support for roaming UEs". + +Solution #4, Solution #5, Solution #13, and Solution #14 and Solution #50 all address aspects of Key Issue #10. + +One aspect of Key Issue #10 is how the EEC in the roaming UE knows the availability of ECS(s) and discovers them in the VPLMN. + +- Solution #4 and Solution #14 share the principle that the home network can provide the EEC in the UE with information that is used to contact a V-ECS. In both solutions, this information is provided in the Service Provisioning Response. + - In solution #4, the V-ECS information can be an address, endpoint or service API information. + - In Solution #14, the V-ECS information can include an FQDN or an IP Address of a V-ECS. + - In Solution #14, the V-ECS information can include a DNN (O) and/or S-NSSAI (O). The DNN / S-NSSAI can be used to establish an LBO PDU Session. Once the UE establishes an LBO PDU Session, Rel-17 procedures can be used to discover the V-ECS address. +- In Solution #13, it is proposed that PLMN ID(s) can be sent with ECS Address Configuration Information. As in Rel-17, ECS Address Configuration Information is sent to the UE by the SMF during PDU Session Establishment and/or PDU Session Modification. +- In Solution #5, V-ECS address information is not sent to the UE. + +Another aspect of Key Issue #10 is how the EEC in the roaming UE knows the availability of EES(s) and discovers them in the VPLMN. + +- Solution #4, Solution #14, and Solution #13 share the principle that the EEC in the UE is provided with information to contact ECS(s) in the VPLMN. The EEC can then contact an ECS in the VPLMN to discover EES(s) in the VPLMN. +- In Solution #5, the H-ECS uses the EDGE-10 interface to obtain information from the V-ECS about what EES(s) are available in the VPLMN. The H-ECS then sends the information about the EES(s) in the VPLMN to the EEC in the Service Provisioning Response. + +Another aspect, which is addressed by all Key Issue #10 solutions, is what information the HPLMN uses to determine what information about edge computing services in the VPLMN to send to the UE. + +- In Solution #13, ECS Address Configuration Information(s) can be stored in the UE's subscription and PLMN ID(s) can be stored with each ECS Address Configuration Information. The SMF sends all ECS Address Configuration Information(s) and PLMN ID(s) from the UE's subscription to the UE. The UE can determine what ECS Address Configuration Information(s) to use based on what PLMN it is registered to. +- Solution #4, Solution #5, and Solution #14 share the principle that the ECS uses the PLMN ID of the PLMN where the UE is currently registered to determine what information about edge computing services in the VPLMN to send to the UE. +- The Rel-17 Service Provisioning Request can already include the UE Location. The UE Location can be expressed as a Tracking Area Identity. The Tracking Area Identity includes a PLMN ID. +- Solution #4 and Solution #5 share the principle that, if location is not included in the Service Provisioning Request, the ECS interacts with the Core Network to obtain the UE's location. Allowing the ECS to obtain the UE's location in this manner can be done with minimal impact to normative specifications. For example, the ECS can obtain the UE's location by invoking existing NEF API(s). +- In Solution #4, Solution #5 and Solution #14, if a VPLMN ID is not included in the Service Provisioning Request, the ECS obtains the PLMN ID by interacting with the Core Network. Solution #14 explains that the ECS can do this by invoking the NEF's monitoring event API with the monitoring type set to ROAMING\_STATUS and the plmnIndication set to TRUE as described in 3GPP TS 29.522 [17] and 3GPP TS 29.122 [18]. Allowing the ECS to obtain the UE's PLMN ID in this manner can be done with minimal impact to normative specifications. For example, the ECS can obtain the UE's location by invoking the existing NEF monitoring event API. +- Solution #4 relies on having sufficient information (e.g. ECSP policy, or UE-specific service information, or ECSs information) configured or available in an ECS to determine candidate ECSs. +- Solution #5 relies on preconfigured information of ECS2 at ECS1. + +NOTE 1: In Solutions #4 and #5, to configure sufficient information to the ECS, the ECS(s) information related to other ECSPs may be available at the OAM system due to the inter-ECSP relationship establishment, which is then used by the OAM system of an ECSP to configure its ECS. If required, the information of available applications in a partner ECSP and the corresponding service areas are included in the configured information. Inter-ECSP relationship establishment is according to the business relationship between the ECSPs and is out of the scope of SA6. The OAM to configure its ECS for inter-ECSP relationship is under the scope of SA5. + +NOTE 2: It cannot be assumed that all ECS(s) will have access to NEF API(s). + +Another aspect, which is addressed by all Key Issue #10 solutions, is how the HPLMN obtains the information about edge computing services in the VPLMN to send to the UE. Solution #4, Solution #5, Solution #13, and Solution #14 all require that the home network (i.e. the H-ECS or H-SMF) determine what V-ECS(s) that are used by the EEC. In Solution #4, Solution #13, and Solution #14 the information about the V-ECS(s) is sent to the EEC. In Solution #5, the V-ECS(s) are contacted by the H-ECS to obtain EES information to the send to the EEC. In Solution #4, Solution #5, Solution #13, and Solution #14, the home network (i.e. the H-ECS or H-SMF) must determine what V-ECS(s) that are used by the UE. + +- In Solution #13, ECS Address Configuration Information(s) is stored in the UE's subscription as is done in Rel-17. The information for each V-ECS that the UE can use would need to be stored in the UE's subscription. ECS information shared in Solution 13 is limited to the ECSs whose information is available through H-PLMN. +- In Solution #4, the ECS of the HPLMN uses the location information and/or VPLMN ID to discover what V-ECS information (e.g. address, endpoint or service API information) to send to the UE. The discovery can be + +based on pre-configuration or the H-ECS can discover service API information exposed by that ECS via CAPIF discovery procedure as specified in TS 23.222 [16] + +- In Solution #5, the ECS of the HPLMN uses the location information and/or VPLMN ID to discover V-ECS information (e.g. address, endpoint or service API information). The discovery can be based on pre-configuration or the H-ECS can discover service API information exposed by that ECS via CAPIF discovery procedure as specified in TS 23.222 [16]. The H-ECS then queries the V-ECS to obtain EES information to send to the UE. It is assumed that the ECS uses existing Rel-17 mechanisms from TS 23.558 [2] to determine what EES information to send to the EEC. For example, the ECS can identify the EES(s) based on the provided AC profile(s), the UE location, UE-specific service information, or an ECSP policy. +- In Solution #14, the ECS of the HPLMN uses the VPLMN ID to discover V-ECS information (e.g. address, endpoint or service API information). The H-ECS then uses the EDGE-10 interface to query the V-ECS to obtain information to send to the UE. The query can include the UE's location and the information that is sent to the UE can be a DNN / S-NSSAI combination that can be used by the UE to establish an LBO PDU Session in the VPLMN. The V-ECS can use the UE's location to determine what DNN / S-NSSAI combination that is sent to the UE in order to cause the UE to establish an LBO PDU Session. The H-ECS can use the PLMN ID to determine the V-ECS to contact. For example, this can be based on a DNS lookup or the addresses of V-ECSs can have been pre-configured in the H-ECS (e.g. via OAM). If the VPLMN hosts multiple V-ECSs, then which V-ECS is resolved can be based on configuration. +- In solution #14, H-ECS uses UE location, in its request towards V-ECS. +- Solution #5 and Solution #14 both involve interaction between the V-ECS and H-ECS and both solutions largely rely on pre-configuration for how the H-ECS determines what V-ECS to contact. Since there can be multiple ECSs (e.g. from different ECSPs) deployed in the V-PLMN, it can be crucial to contact appropriate ECS based on EEC's requirements provided in the service provisioning request or EES's requirements provided in the retrieve T-EES request, e.g. in case of service continuity situation. Also, EDGE-10 enhancements based on solutions to other key issues (e.g. Key Issue #6) might be considered in order to allow the H-ECS to perform a more dynamic discovery, or determination, of the V-ECS to contact. + +Information of the V-ECS associated with the V-PLMN is assumed to be available at the H-ECS e.g. through pre-configurations. + +NOTE 3: One V-ECS can be shared across multiple PLMNs for roaming related service provisioning. + +An important point of Key issue #10 is that the UE needs to obtain information for V-ECSs (ECS available in VPLMN) to obtain service provisioning information in VPLMN. + +- In solution #13, the new information that is sent to the UE is the PLMN ID(s) with ECS Address Configuration Information. +- In solution #4, the new information that is sent to the EEC in the UE is V-ECS address, endpoint or service API information. +- In solution #5, the new information that is sent to the EEC in the UE is VPLMN EES Information in the Service Provisioning Response from the H-ECS. +- In solution #14, the new information that is sent to the EEC in the UE is a V-ECS address or a DNN / S-NSSAI combination that can be used by the EEC to establish an LBO Session in the VPLMN. + +Solution #50 provides enhancements so that an ECS can query an ECS-ER to obtain information of partner ECS that provide service provisioning for a particular application. This allows to reduce the time required to provide service provisioning response while ensuring that the required application is available with the V-ECS when configured information is not available with the ECS. Solution #50 can be used along with Solution 4, Solution 5, Solution 13 and Solution 14. + +When the EEC contacts an H-ECS, there are cases where the H-ECS can detect that the UE is roaming and can obtain service provisioning from a V-ECS. In Rel-18, the Service Provisioning Response will be updated to allow the H-ECS to provide a V-ECS information to the EEC on EDGE-4. As described in Solutions #4 and #14, the V-ECS information sent to the EEC can include address (FQDN or an IP Address), endpoint or service API information of a V-ECS. + +There are deployment scenarios where the EEC needs to access the ECS via an LBO session. There are cases where the UE is not pre-configured with a DNN / S-NSSAI combination that can be used to establish an LBO PDU session that can be used to reach the V-ECS. Thus, as described in Solution #14, the Service Provisioning Response will be updated + +to allow the H-ECS to provide a DNN / S-NSSAI combination to the EEC. The DNN / S-NSSAI combination can be used by the EEC to establish an LBO PDU Session in the VPLMN. Per existing Rel-17 behaviour and as defined in TS 23.548 [19], if the EEC does not have contact information for a V-ECS, the EEC can obtain V-ECS Address Configuration information from the V-SMF during PDU Session Establishment. + +In Rel-17, it is already possible for an H-SMF to provide ECS Address Configuration information to the UE during PDU Session Establishment or in a PDU Session Modification Command. As explained in TS 23.548 [19] "The UDM in the HPLMN can provide the SMF (in HPLMN in HR case, in VPLMN in LBO case) with ECS address configuration information that depends on the serving PLMN of the UE." The Rel-17 approach requires that the UDM detect when the UE's serving PLMN changes and only sends the UE ECS Address Configuration information that is associated with the PLMN that is currently serving the UE. In Rel-18, the principles of Solution #13 will be followed so that the UE ECS Address Configuration information that is sent to the UE during PDU Session Establishment and PDU Session Modification can include PLMN ID(s). + +As described in Solution #5, there are cases where the H-ECS is able to provision the EEC with information about EES(s) that are in the VPLMN. The H-ECS can use the EDGE-10 to obtain information from the V-ECS about what EES(s) are available in the VPLMN. The principles of Solution #5 will be followed to enhance the Service provisioning procedure to allow the H-ECS to provide the EEC with information about EES(s) in the VPLMN. + +### 10.2.11 Key issue #11: ACR between EAS and Cloud Application Server + +There are two solutions in the TR, CES-less solution is described in solution #25, and solution with CES is described in solution #24. + +With CES, ACR feature parity can be supported in the ACR between CAS and EAS utilizing all EDGEAPP developed features (e.g. AS discovery, AS registration). Comparing to CES-less solution, it needs a new function entity in the central DN to support CAS, and CES is part of the EEL. The CES has the same functions as the EES without having service area restriction. The CAS registers in CES in order to be discoverable by the EEC using EDGEAPP EAS discovery mechanism, the CES registers in ECS in order to be discoverable by the EEC using EDGEAPP service provisioning procedure. CAS registration to CES is an additional functionality that need to be supported for all CAS(s). + +For CES-less solution as described in solution #25, it has a mixed use of regular DNS query and EDGEAPP EAS discovery. When a T-EAS cannot be discovered using the EDGEAPP mechanism, EDGEAPP entities (e.g. AC) falls back to regular DNS query. It supports ACR scenarios as described in solution #25 for ACR from EAS to CAS, it also supports ACR scenarios for ACR from CAS to EAS. + +Both solutions can be considered in the normative work, the CES can be considered as an optional entity in the EDGEAPP architecture. They share the same EDGEAPP EAS discovery/service provisioning procedure when trying to discover appropriate EAS. If there is CES available and registered in the ECS in the network, the EDGEAPP mechanism returns CES in service provisioning response to the EEC/S-EES or the S-EAS obtains CAS from CES via S-EES based on the request from EEC/S-EES or the S-EAS to initiate ACR to Cloud and EDGEAPP mechanism follows; otherwise, regular DNS is used to find CAS due to EDGEAPP mechanism failure (no EES configuration or T-EAS is not discoverable). + +What functionalities of EDGE-9 and EDGE-6 are to be reused for EDGE-14 and EDGE-15 respectively in clause 6.5 and the detailed differences for EDGE prime reference points and the cardinality rules in clause 6.6, will be addressed in the normative phase. + +### 10.2.12 Key issue #12: EEL service differentiation + +Solution #12 (Service continuity planning permission) address KI #12. + +Solution #12 allows ECSPs to selectively enable service continuity planning based on policy authorization for EEC's service continuity capability. The EEC provides its capability to perform service continuity planning and request permission for service continuity planning. The EES verifies the use and provides the response whether service continuity planning is allowed for the EEC or not. + +The solution#51 addresses KI#12. The solution proposes to enhance the EEL specifically EEC registration and EEC registration update procedures to provide indication whether the UE requires mobility support or not to the EES. + +Solution #52 provides an option to provide service differentiation for EES users to address KI #12. It also provides a way to address the corresponding EES having valid PLMN subscription data for the EES users which improves the service provisioning procedure. + +### 10.2.13 Key issue #13: Edge enabler layer support for EAS synchronization + +This clause provides an overall evaluation for the key issue #13 Edge enabler layer support for EAS synchronization. + +The open issues include: + +- 1) Whether and how to enable EAS to find other EAS(s) with multi-user communication session to synchronize? +- 2) Whether and how to enable EAS to find other interested EAS(s) with specific service to synchronize? +- 3) Whether and how to enable EAS to discover and interact with another application server function deployed on the cloud for context synchronization? +- 4) Whether and how edge enabler layer could provide support to EAS synchronization? + +Open issues 1) and 2) requires discovering of another EAS for specific service to synchronize. Clause 7.31.2.4 of solution #31 (Discover common EAS) addresses these two open issues by determining other EESes for announcing selected EAS information for specific service. + +Further, regarding open issue 4) about edge enabler layer providing support to EAS synchronization, clause 7.31.2.4 of solution #31 specifies selected EAS notification to relevant EASs via EDGE-3. However, the details of actual EAS to EAS synchronization itself is out of scope of this solution. + +Solution #53 (Support for EAS synchronization) addresses KI#13. The solution enhances the EAS registration and Target EAS discovery procedure. The solution enables the EAS to discover another EAS(s) with support for content synchronization. + +### 10.2.14 Key issue #14: Application traffic influence for initially selected EAS + +This clause provides an overall evaluation of the key issue #14 Application traffic influence for initially selected EAS. The solution #9, solution #15 and solution #17 are complementary to each other. + +The solution #9 is applicable to the scenario where the EAS triggers the EES to perform traffic influence without necessitating requests to be made on a per UE basis. + +The solution #15 is applicable to the scenario where the EEC (or AC and EEC) selects the EAS after EAS discovery and then provides a selected EAS declaration request to the EES, which may be used by the EES to make traffic influence decisions if those haven't already been performed. + +The solution #17 is applicable to the scenario where the EES selects the EAS and performs traffic influence immediately for the selected EAS after EEC sent EAS discovery request based on attributes in the EEC provided AC profile, providing the selected EAS to the EEC in the EAS discovery response. + +All 3 solutions result in network resources being reserved to varying degrees before actual use, where this may be lower in the UE specific solutions of solution 15 and 17. + +### 10.2.15 Key issue #15: Support of constrained devices for Edge + +The open issues of key issue #15 are as follows: + +- Whether there are any impacts on the EDGEAPP architecture for constrained UE. +- Whether and how the existing EDGEAPP architecture and procedures, for constrained UE to network communication (i.e. EDGE-1 and EDGE-4), e.g. can be improved to reduce power consumption. + +To address the first open issue, architecture enhancement evaluation in clause 10.1.1 will be considered in the normative work. + +To address the second open issue, solution #18 provides EAS discovery procedure enhancement and the minimum supported procedures for ACR to reduce power consumption in UE with EEC with reduced capabilities. + +### 10.2.16 Key issue #16: support of NAT deployed within the edge data network + +The open issues of key issue #16 are as follows: + +- How the EES can access 3GPP network services pertaining to a UE when the edge data network employs Network Address Translators (NATs). +- How AF specific and temporary UE IDs can be managed at the Edge Enabler Layer? + +Solution #23 solves these open issues by reusing SA2 defined CN capability (Nnef\_UEId\_Get) to translate UE's private IP address to its UE ID. The solution also allows the EES to convert the CN or EEC provided UE ID to Edge UE ID, which is managed by the EES. The Edge UE ID can be specific to the EAS and can be temporary as required. Support from SA2 is required to address potential IP address overlap issues in some network deployments. Support from SA3 is required for any security related issues. As an alternative, if SA2 supports translation of the globally unique EECID to UE ID, then the EEC would not be required to provide either its private IP address or MSISDN and the potential IP address overlap issue is avoided. + +As a further alternative, if SA2 supports translation of UE's public IP address to its UE ID, EES can use the public IP address for translation. In this case, EAS can also provide UE's public IP address to the EES over EDGE-3 UE ID API defined in Rel-17 TS 23.558 [2]. + +### 10.2.17 Key issue #17: Discovery of a common EAS + +The open issues of key issue #17 are as follows: + +- 1) Whether and how the ACs/EECs of different users can select or be provisioned the same EAS within an EDN? + +NOTE: This open issue is dealing with the issue how different EECs can perform EAS discovery so that they select the same EAS within an EDN, whereas KI#13 is dealing with the issue how, after different EECs have selected different EASs located in different EDNs, these EASs can synchronize their contexts. + +- 2) Whether and how the ACs/EECs of different users can select or be provisioned a common EAS, even if initially the EECs are communicating with different EDNs? +- 3) Whether and how the EEL can support service continuity to ensure that when ACs require the use of service from a common EAS and an ACR operation is needed, ACR operations can be coordinated so that upon completion of the ACR operations the ACs again have services provided by a common EAS. + +Solution#31 complements solution#27, when there is a centralized repository deployed in an ECSP provider (common to solution #27 and solution#30). + +Solution#31 complements solution#29 when there is no centralized repository deployed by an ECSP provider. + +Solution#28 is mostly application layer implementation, with minimum enhancements to the mechanisms in Rel-17. + +### 10.2.18 Key issue #18: EAS bundles + +The open issues of key issue #18 are as follows: + +- How can the EEL identify EAS bundles? +- What are the impacts on EEL procedures due to EAS bundles e.g. when the bundled EASs are served by the same EES and require ACR due to UE mobility? + +Solution #26 solves these open issues by enhancing the AC, EAS and EES profiles. Enhancements include adding EAS bundle information and EAS bundle requirements in the identified profiles. The solution also enhances EAS discovery filters and Retrieve EES request. Further, handling of these IEs at the EEC, EES and ECS is also described. + +Solution #46 and solution #47 address the KI#18. To satisfy the coordinated ACR requirements (i.e. the bundled EAS may need to be relocated together), the EEC or the EES can act as decision entity to determine ACR scenario selection for EAS bundles, based on the AC/EEC/EES(s)/EAS(s) abilities of handling bundled EAS ACR. + +### 10.2.19 Key issue #19: ACR scenario combination + +This clause provides an overall evaluation of Key issue #19, "ACR scenario combination". + +Solution #19, Solution #35 and Solution #38 address aspects of Key issue #19. + +An open issue that is cited in Key Issue #19 is whether "Different combinations of utilizing ACR scenarios by Applications should be enabled by the Edge Enabler Layer (e.g. only one ACR scenario allowed or several ACR scenarios allowed).". All solutions agree that ACR scenario(s) combination should be allowed. + +- Solution #19 has the following notes which suggest that a single ACR scenario or multi-ACR scenarios are allowed. + - "NOTE 1: Using multiple ACR scenario can detect ACR timely" + - "NOTE 2: The selection of a single ACR scenario and therefore single ACR detection entity may not be suitable for time sensitive applications" +- Solution #35 proposes to establish an ACR scenarios list which can include zero ACR scenario or a single ACR scenario or multi-ACR scenarios. +- Solution #38 proposes to coordinate multiple ACR decision making-entities suggesting that multi-ACR scenarios are allowed. + +Which EEL entity selects the ACR scenario(s) combination? Solution #19 and Solution #35 take a different approach. + +- Solution #19 proposes the EES to select a single ACR scenario or multi-ACR scenarios when requested by the EEC. Solution#19 is applicable to the scenario where the EES determines the ACR scenario for the AC based on the EAS, EES, EEC, AC service continuity support. + - A new ACR scenario selection request is needed to provide AC and EEC service continuity information to the EES, and the EES already knows EES/EAS service continuity information +- Solution #35 proposes the EEC to select zero ACR scenario or a single ACR scenario or multi-ACR scenarios when the EAS is selected at the EEC. Solution#35 is applicable to the scenario where the EEC determines the ACR scenario based on the EAS, EES, EEC, AC service continuity support. + - Per Rel-17, the EEC already has the service continuity information from the EES/EAS/AC/EEC, and no new message is needed to make the ACR selection. +- Whether Solution #19 and Solution #35 are also applicable for subsequent ACR and necessary improvement require further study in normative work. +- Solution #38 relies on Solution #19 or Solution #35 for ACR scenario(s) selection. + +How is the ACR scenario(s) list communicated to the ACR decision-making entities? Solution #19 and Solution #35 partially differ in how the ACR scenario(s) list is communicated to ACR decision-making entities (e.g. EEC/EES/EAS). + +- Solution #19 proposes that the EES informs the EEC of the selected ACR scenario(s) via a new ACR scenario selection notification, which contains the selected ACR scenario(s) list. +- Solution #35 proposes that the EEC informs the EES of the selected ACR scenario(s) list via a new selected EAS announcement request. +- Both Solutions #19 and Solution #35 propose that the EAS subscribes to ACR scenario selection, and that the EES informs the EAS via a new ACR selection notification. +- Solution #38 relies on Solution #19 or Solution #35 for communicating the ACR scenario selection to the ACR decision-making entities. + +How do EEL ACR decision-making entities (e.g. EEC/EES/EAS) use the selected ACR scenario(s) list? + +- Solution #19 and Solution #35 indicate that each ACR decision-making entity (e.g. EEC/EES/EAS) uses the ACR scenario list to decide if ACR detection needs to be initiated. +- Solution #38 relies on Solution #19 or Solution #35 for initiating ACR detection at the decision-making entities. + +How is ACR execution coordinated after ACR detection happens? + +- Solution #19 and Solution #35 do not specify how ACR execution is coordinated +- Solution #38 proposes to extend existing ACR management event notification (EES/EAS) and the ACR information notification (EES/EEC) to explicitly indicate that an ACR has started executing to prevent other ACR decision-making entities from initiating ACR execution. Solution #38 is not dependent on Solution #19 and Solution #35; Solution. #38 is only required when multi-ACR scenarios are selected. + +### 10.2.20 Key issue #20: Supporting composite EASs + +The open issues of key issue #20 are as follows: + +- Whether and how the EEL can support to composite EAS context management. +- Whether and how the EEL can support the relocation of the composite EAS context for service continuity. +- Whether and how the EEL can discover EAS that provides the services of the composite EASs. + +Solution #49 addresses the 3rd open issue. The EEL provides discovery service to AC connected EAS so that other component EASs can be discovered and selected by the AC connected EAS based on need. + +### 10.2.21 Key issue #21: Simultaneously EAS connectivity in ACR + +Solution #22 enhances AC profile and EDGE-1 ACR procedure to enable EES to influence the traffic for simultaneous EAS connectivity during service continuity. The detailed impact to 3GPP TS 23.558 [2] and remaining EN in clause 7.22.2.1 for SA2 coordination will be addressed in the normative phase. + +### 10.2.22 Key issue #22: EAS discovery in Edge Node sharing scenario + +This clause provides an overall evaluation of Key issue #22, "EAS discovery in Edge Node sharing scenario". + +- 1) Solution #43 and #44 works for a scenario where EESs from OP B are deployed and available everywhere in a region, the required EAS is not available with OP B, the EAS can be shared to all operators in the federation and OP B identifies that the most suitable EAS is in Partner OP. + - a) Solution #43 proposes to use ECS-ER entity (as defined in clause 6.x), where Application info is published from ECS-ER (OP-A) to ECS-ER (OP-B). And when required ECS (OP-B) fetches application information from ECS-ER (OP-B). In case, if application information is not published, EEC sends service provisioning request to ECS (OP-B) which discovers T-EES and shares the T-EES information to EEC in a transparent way. EEC in turn includes T-EES information in EAS discovery request towards EES which contact T-EES to fetch application information. + - b) Solution #44 proposes to use ECS-ER entity (as defined in clause 6.x), where EES publishes the registered EAS information to ECS-ER. ECS-ER of different operators in federation can subscribe to each other to get registered EAS information. Alternatively, ECS-ER (OP-A) can get the registered EAS information directly from ECS-ER (OP-B). When EEC sends EAS discovery request, the EES (OP-B) can get EES (OP-A) information from ECS-ER and performs ES discovery towards EES (OP-A). Upon receiving the EAS discovery response from EES (OP-A), the EES (OP-B) shares the EAS details to EEC. +- 2) Solution #45 works for a scenario that EES service (OP A) can be shared to the Operator B. The OP B can access the edge resource from the Partner OP for the EAS deployment and also access the EES service from the Partner OP. + - a) Solution #45 proposes to enhance service provisioning and EAS discovery procedures. The ECS (OP-B) determines that the required EAS is available with EES (OP-A), and includes EES (OP-A) in the service provisioning response. EEC (OP-B) sends the EAS discovery request to EES (OP-A) which provides EAS details to EEC. + +Solutions are to be considered during the normative work based on GSMA feedback. + +### 10.2.23 Key issue #23: Reliable Edge service + +The open issues of key issue #23 are as follows: + +- Whether and what mechanisms the EES/ECS can use for high reliability in EES/ECS services during expected events and unexpected events in the service. +- Whether and what mechanisms the EES/ECS can provide to support highly reliable EAS during expected events and unexpected events in the service. + +Solution #48 addresses all open issues by providing support for reliable edge service with service set. + +The principle used in solution #48 can also be applicable to other application enabling services (e.g. SEAL) and detailed solution can be discussed in respective work item. + +### 10.2.24 Key issue #24: SEAL capability access for EEL support + +The open issue in Key Issue #24 is: + +- How EEL accesses and utilizes SEAL capabilities deployed within the EDN. + +Solution #41 solves this issue by utilizing SEAL ADAES for enhancing EEL operations based on edge load analytics. The ADAES capability in TR 23.700-36 was concluded and provides a mechanism which allows EES and EAS to receive EES/EAS edge load measurements to enhance operations like service continuity. This solution is feasible, and the only dependency is the expected specification of the ADAES feature related to edge analytics (expected in TS 23.436). + +NOTE: Whether EEC can also use SEAL ADAE layer to receive overload condition of EAS/EES can be considered in normative work. + +# --- 11 Conclusions + +## 11.1 General + +This technical report fulfils the objectives of the study on application architecture for enabling Edge Applications. The report includes the following: + +1. Definition of terms and abbreviations used in the study (clause 3); +2. Key issues identified by the study (clause 4) and corresponding architectural requirements (clause 5); +3. Enhancements to edge application architecture specified in 3GPP TS 23.558, corresponding to the key issues and architectural requirements (clause 6); +4. Individual solutions addressing the key issues (clause 7); +5. Set of deployment options (clause 8) and updated business relationships considering Federation and Roaming support (clause 9); and +7. Overall evaluations of all the solutions (clause 10). + +Some of the individual solutions have dependency on other working groups within 3GPP. This dependency is summarized in overall evaluations (clause 10). + +NOTE: For the objectives with dependency on other SA WGs, the solution(s) for the normative work can be progressed with close coordination with the dependent WGs. If the dependencies are not resolved within the release timeframe, the solutions will be removed or down-scoped to avoid the dependencies. + +## 11.2 Conclusions for normative work + +### 11.2.1 General conclusions + +The study concludes with following general considerations for the normative work: + +1. Definition of terms and abbreviations captured in clause 3 will be reused; +2. Architectural requirements identified in clause 5 will be used for updated baseline architectural requirements; and +3. Deployment scenarios and involved business relationships will be considered as captured in clause 8 and clause 9 respectively. Additional deployment models and their implications on the solutions will be considered. +4. The solutions are applicable only for the corresponding scenario assumptions. + +### 11.2.2 Architecture enhancement conclusions + +The study concludes with following architectural enhancements considerations for the normative work: + +1. Architecture enhancements from clause 6 corresponding to the concluded solutions will be used for updating baseline edge application architecture specified in 3GPP TS 23.558: + - a. architecture corresponding to solution #20 as specified in clause 6.3 and additionally leveraging generic notification service from SEAL. + - b. architecture enhancement as specified in clause 6.4 + - c. architecture enhancement to support service provisioning in LBO and HR roaming scenarios as specified in clause 6.1 + +### 11.2.3 Solution conclusions + +The study concludes with following solution considerations for the normative work: + +1. Following individual solutions, corresponding to the key issues, will be considered as candidate solutions: + - i. for Key issue #1 (Enhanced notification service to the EEC): + - a. Solution #1: Service provisioning via push notification + - SEAL Notification Service will be specified in TS 23.434 [23] to support the Solution #1 + - The usage of SEAL Notification Service in TS 23.558 [2] will be captured to Solution #1 + - b. Solution #3: Service provisioning triggering via SMS over NAS + - The usage of SMS over NAS to trigger service provisioning procedure will be specified in TS 23.558 [2] as per Solution #3. + - c. Solution #20: Propagation of EEL notifications to EEC using Edge Notification Server + - SEAL Notification Service will be specified in TS 23.434 [23] to support the Solution #20 + - The usage of SEAL Notification Service in TS 23.558 [2] will be captured to Solution #20 + - ii. for Key issue #2 (Enablement of Service APIs exposed by EAS): + - a. Solution #8: EAS Service API enablement using CAPIF + - iii. for Key issue #3 (Enhancements to service continuity planning): + - a. Solution #6: ACR update in service continuity planning + - b. Solution #7: EES monitors UE mobility for service continuity planning + +- c. Solution #12: Service continuity planning permission + - d. Solution #21: Prediction expiration time for service continuity planning enhancement + - e. Solution#37: ACR request trigger timing +- iv. for Key issue #4 (EDGE-5): + - a. Solution #34 (EDGE-5 APIs) +- v. for Key issue #5 (Alignment of EDGEAPP and ETSI MEC): + - a. Solution #11: This solution relies on the EDGEAPP architecture as specified in TS 23.558 [2] and CAPIF as specified in TS 23.222 [16]. The solution does not require changes in architecture and procedures. + - b. Solution #36: This solution is based on the principles set in clause 5.4 and provides a mapping between overlapping APIs in EDGEAPP and ETSI MEC. The solution does not require changes in architecture and procedures. + - c. The different aspects of alignment of EDGEAPP and ETSI MEC covered by the Solution #11 and #36, may be captured as informative annex(es) in TS 23.558. +- vi. for Key issue #6 (Edge services support across ECSPs): + - a. Solution #4 ECS discovery through serving ECS to support edge services across ECSPs: Detailed signalling to provide ECS2 address to the requesting EEC or EES based on solution #4 is to be specified in normative phase. + - b. Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs: Signalling between ECS1 and ECS2 to discover and retrieve provisioning to the requesting EEC or T-EES for the requesting EES will be specified in normative phase according to solution #5. A new interface EDGE-10 between ECS1 and ECS2 is used in Solution #5. + - c. Solution #13: Update ECS configuration information: if required, the additional optional IEs are added to ECS configuration information provided by ECS to 5GC according to Solution #13. + - d. Solution #50: Enhanced ECS for federation of services: enhancements will be specified in the normative phase so that an ECS can query an ECS-ER to obtain information of partner ECS that provide service provisioning for a particular application. +- vii. for Key issue #7 (Application traffic filter exposure): + - a. Solution #2: Traffic filter support for EDGE-3 API addressing application traffic detection +- viii. for Key issue #8 (EAS selection synchronization): + - a. Solution #39 (EAS selection synchronization at registration) +- b. Solution #15 (Initial EAS selection) +- ix. for Key issue #9 (Enhancement of dynamic EAS instantiation triggering): + - a. Solution #32 (Dynamic EAS instantiation triggering and notification) + - b. Solution #33 (Support for EEC Discovery of EAS(es) before instantiation) + - c. Solution #40 (EAS instantiation status provisioned by ECS) + - d. Solution #42 (EAS selection and instantiation in EES) +- x. for Key issue #10 (Support for roaming UEs): + - a. Solution #4 ECS discovery through serving ECS to support edge services across ECSPs: Detailed signalling to provide V-ECS address to the requesting EEC or EES based on solution #4 is to be specified in normative phase. + +- b. Solution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs: Signalling between H-ECS and V-ECS to discover and retrieve provisioning to the requesting EEC or T-EES for the requesting EES will be specified in normative phase according to solution #5. A new interface EDGE-10 between H-ECS and V-ECS is used in Solution #5. + - c. Solution #13: Update ECS configuration information: if required, the additional optional IEs are added to ECS configuration information provided by ECS to 5GC according to Solution #13. + - d. Solution #14: V-ECS Discovery via the H-ECS: the Service Provisioning Response will be updated to allow the H-ECS to provide a DNN / S-NSSAI combination to the EEC. The DNN / S-NSSAI combination can be used by the EEC to establish an LBO PDU Session in the VPLMN. + - e. Solution #50: Enhanced ECS for federation of services: enhancements will be specified in the normative phase so that an ECS can query an ECS-ER to obtain information of partner ECS that provide service provisioning for a particular application. +- xi. for Key issue #11 (ACR between EAS and Cloud Application Server): +- a. Solution #24 (ACR between EAS and CAS with CES) + - b. Solution #25 (ACR between EAS and CAS without CES) +- xii. for Key issue #12 (EEL service differentiation): +- a. Solution #12 (Service continuity planning permission) + - b. Solution #51 (EEC sharing UE Mobility requirement) + - c. Solution #52 (EES policy differentiation) +- xiii. for Key issue #13 (Edge enabler layer support for EAS synchronization): +- a. Solution #31 (Discover common EAS) clause 7.31.2.4 + - b. Solution #53 (Support for EAS synchronization) +- xiv. for Key issue #14 (Application traffic influence for initially selected EAS): +- a. Solution #9 (Application traffic influence trigger from EAS) + - b. Solution #15 (Initial EAS selection declaration) + - c. Solution #17 (Traffic influence for initial EAS discovery) +- xv. for Key issue #15 (Support of constrained devices for Edge): +- a. Solution #18: Constraint device in EDGEAPP +- xvi. for Key issue #16 (Support of NAT deployed within the edge data network): +- a. Solution #23 (UE identification with NAT) +- xvii. for Key issue #17 (Discovery of a common EAS): +- a. Solution #27 (Enabling AC Association Aware services by selecting common EASs) + - b. Solution #28 (Common EAS discovery using EAS selection information) + - c. Solution #29 (Discovery of a common EAS) + - d. Solution #30 (Common EAS selection) + - e. Solution #31 (Discover common EAS) +- NOTE 1: Selecting one of the solutions or merging into one or more solutions shall be considered during the normative phase. +- xviii. for Key issue #18 (EAS bundles): + +- a. Solution #26 (Bundled EASs) + - b. Solution #46 (EEC selected ACR scenario for EAS bundles) + - c. Solution #47 (EES determines the selected ACR scenario for EAS bundles) +- xix. for Key issue #19 (ACR scenario combination), see also clause 10.2.19: +- a. The principle of Solution #19, #35, #38 that the EEL will offer support for utilizing a combination of ACR scenario(s) will be followed. + - b. The principle of Solution #35 that the EAS selection entity performs selection of the ACR scenario combination will be followed; the EEC will select zero ACR scenario or a single ACR scenario or multi-ACR scenarios in the ACR scenario list according to the EEL participants service continuity capabilities and AC requirements. + - c. The principle of Solution #35 that the ACR scenario list is communicated to the EES via the selected EAS announcement request will be followed, the EAS announcement request will be enhanced with the ACR scenario list. + - d. The principle of Solution #19 and #35 that the ACR scenario list is communicated to the EAS via the ACR selection notification and that the EAS will subscribe to such notification will be followed; the ACR selection notification will provide the selected ACR scenario list. + - e. The principle of Solution #19 and #35 that each ACR decision-making entity (e.g. EEC/EES/EAS) will use the ACR scenario list to decide if ACR detection needs to be performed will be followed; a gating condition that the ACR scenario is present in the ACR selected scenario list will be added to the ACR detection phase of every ACR scenario. + - f. The principle of Solution #38 that ACR execution will be coordinated after ACR detection happens will be followed; the ACR management event notification and the ACR information notification will be enhanced with information about start of ACR execution. +- xx. for Key issue #20 (Supporting composite EASs): +- a. Solution #49 (Supporting EAS composition) There is no impact identified in Rel-18 EDGEAPP for solution #49 but the use case can be captured in informative annex of TS 23.558 [2] to provide usage guideline for EAS developers. +- xxi. for Key issue #21 (Simultaneously EAS connectivity in ACR): +- a. Solution #22: Support simultaneous EAS connectivity in ACR +- xxii. for Key issue #22 (EAS discovery in Edge Node sharing scenario): +- a. Solution #43 (EAS discovery for Edge node sharing) + - b. Solution #44 (EAS discovery for Edge node sharing) + - c. Solution #45 (EAS discovery in Edge Node sharing scenario) +- NOTE 2: One or more solutions or merged solution from above solution will be considered during the normative work based on GSMA feedback. +- a. Solution #55 (Non-roaming UE location invocation) +- xxiii. for Key issue #23 (Reliable Edge service): +- a. Solution #48 (Edge server set and edge service set) +- xxiv. for Key issue #24 (SEAL capability access for EEL support): +- a. Solution #41 (Interaction with ADAES for edge load analytics) + +2. Individual solutions, not listed under bullet 1 may be adopted in technical specification with appropriate enhancements. + +# --- Annex A (Informative): ETSI MEC and EDGEAPP system comparison + +## A.1 General + +This Annex compares EDGEAPP architecture R17 as defined in 3GPP TS 23.558 [2] and ETSI MEC architecture [3] and provides a gap analysis, addressing the objective in Key issue #5 in clause 4.5. + +## --- A.2 Service consumer and service provider + +The functionalities enabled via the Mp1 reference point between MEC applications and MEC platform is mainly described in ETSI GS MEC011 [14]. The related functionality includes MEC service registration/deregistration, MEC service discovery and event notifications. Other functionality includes MEC service availability, traffic rules, DNS and time of day. + +From ETSI MEC's perspective, there are two types of MEC Applications, i.e. MEC Application that consumes MEC Services and MEC Application that provides MEC service(s). For the MEC Application that provides MEC service(s), the MEC Application sends a service registration request to the MEC platform to register the MEC service during the MEC Application start-up procedure. As for the MEC Application that consumes MEC Services, the MEC Application can send a service query request to the MEC platform to discover a MEC service. It should be noted that the API of registration and discovery is defined for MEC service. + +In R17 of SA6, the EES can take the role of the CAPIF core function, and the vertical application enabler server acting the AEF and publish the vertical application enabler server APIs to the EES. Further, the vertical application enabler server APIs is discovered by the EASs acting as the API invoker during the service API discover procedure as specified in 3GPP TS 23.222 [16]. + +In clause 4.2, the Key issue #2 plans to study Enablement of Service APIs exposed by EAS. The R17 of EDGEAPP only defines the functionality of EAS acting as an invoker, which is similar to MEC Application that consumes MEC Services defined in ETSI MEC: + +**[Observation A.2-1]** The R17 of EDGEAPP only defines the functionality of EAS acting as an invoker, which is similar to MEC Application that consumes MEC Services defined in ETSI MEC. According to the Key issue #2 in clause 4.2, The EAS acting as a service provider is expected to be defined in R18 and expose service APIs. + +**[Observation A.2-2]** According to the Key issue #2 in clause 4.2, the EAS can act as a service provider and EES can act as CAPIF core function so different services will be discoverable at different EESs. How the information of a service registered at one MEC platform is made available to other platforms in the same MEC system is not explicitly specified within ETSI MEC, while in EDGEAPP, as EES supports CAPIF core function, the EAS service published on EES1 can be discovered by EAS registered on EES2 through CAPIF-6 or CAPIF-6e. + +## --- A.3 EAS/MEC application profile provisioning + +ETSI MEC and EDGEAPP defined different style of EAS/MEC application profile provisioning. The information flows for lifecycle management of MEC applications is described in ETSI GS MEC010-2 [13]. The informational flows for the optional MEC Application registration are described in ETSI GS MEC 011 [14]. The MEC application can start producing or consuming MEC Services after the MEC Application is instantiated and running. The application information (AppInfo), which can be regarded as the MEC application profile, represents the information provided by the MEC application instance as part of the "application registration request" message. The attributes of the AppInfo are available from the clause 7.1.2.6 of ETSI GS MEC011 [14]: + +Some fields in AppInfo are intentionally not duplicating the EAS profile (if present) with conflicting parameters but should be consistent with them. This is highlighted in NOTE 1 and NOTE 2, for example. It can be seen that unlike AppD [13], which is mainly used in the management plane for instantiating an application, and is static in nature, AppInfo carries the runtime information about the MEC application instance. + +In EDGEAPP, the EAS profile is provided in the EAS registration request. According to clause 8.2.4 of 3GPP TS 23.558 [2] the information element of the EAS profile is listed as below: + +**Table A.3-2: EAS Profile** + +| Information element | Status | Description | +|-----------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| EASID | M | The identifier of the EAS | +| EAS Endpoint | M | Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the EAS. This information maybe discovered by EEC and exposed to ACs so that ACs can establish contact with the EAS. | +| ACID(s) | O | Identifies the AC(s) that can be served by the EAS | +| EAS Provider Identifier | O | The identifier of the ASP that provides the EAS. | +| EAS Type | O | The category or type of EAS (e.g. V2X) | +| EAS description | O | Human-readable description of the EAS | +| EAS Schedule | O | The availability schedule of the EAS (e.g. time windows) | +| EAS Geographical Service Area | O | The geographical service area that the EAS serves. ACs in UEs that are located outside that area shall not be served. | +| EAS Topological Service Area | O | The EAS serves UEs that are connected to the Core Network from one of the cells included in this service area. ACs in UEs that are located outside this area shall not be served. See possible formats in Table 8.2.7-1. | +| EAS Service KPIs | O | Service characteristics provided by EAS, detailed in Table 8.2.5-1 | +| EAS service permission level | O | Level of service permissions e.g. trial, gold-class supported by the EAS | +| EAS Feature(s) | O | Service features e.g. single vs. multi-player gaming service supported by the EAS | +| EAS Service continuity support | O | Indicates if the EAS supports service continuity or not. This IE also indicates which ACR scenarios are supported by the EAS. | +| List of EAS DNAI(s) | O | DNAI(s) associated with the EAS. This IE is used as Potential Locations of Applications in clause 5.6.7 of 3GPP TS 23.501 [14]. It is a subset of the DNAI(s) associated with the EDN where the EAS resides. | +| List of N6 Traffic Routing requirements | O | The N6 traffic routing information and/or routing profile ID corresponding to each EAS DNAI. | +| EAS Availability Reporting Period | O | The availability reporting period (i.e. heartbeat period) that indicates to the EES how often it needs to check the EAS's availability after a successful registration. | +| EAS Required Service APIs | O | A list of the Service APIs that are required by the EAS | +| EAS Status | O | The status of the EAS (e.g. enabled, disabled, etc.) | + +Comparison of AppInfo in 7.1.2.6 of ETSI GS MEC 011 [14] and EAS Profile in Table A.3.2 shows that: + +**[Observation A.3-1]** Both ETSI MEC and EDGEAPP provides similar types of EAS/MEC application profile provisioning. Both the EAS Profile and MEC Application Instance (AppInfo) is provided during the application registration request. + +**[Observation A.3-2]** Some IEs of the EAS profile may overlap with the ones defined in AppInfo (e.g. EAS ID vs. appName, EAS Provider Identifier vs. appProvider, EAS Endpoint vs. endpoint). Both AppInfo and EAS Profile has many optional IEs, whether and how to address their differences in SA6 is FFS. + +## A.4 EAS registration and EAS discovery + +In R17 of EDGEAPP, the EAS Registration procedure is defined to allow an EAS to provide its information to an EES in order to enable its discovery as defined in clause 8.4.3 of 3GPP TS 23.558 [2]. The EAS discovery procedure is used to provide EAS information to the EEC. After the EEC is provisioned with the EAS information, it can establish a connection to the EAS. Besides, in the service continuity scenario, the source EAS may send an EAS discovery request to the EES to discover a target EAS (providing same functionality as the source EAS) to serve the UE as defined in clause 8.8.3.2 of 3GPP TS 23.558 [2]. + +However, in current ETSI MEC specification, no APIs for MEC Application registration is defined because it is assumed that all MEC Application are on-boarded and managed by MEC Orchestrator, which was specified in ETSI GS + +MEC 010-2 [13]. API for MEC Application discovery is not defined since the existing MEC service is either defined from the MEC Application's perspective or it is consumed by the MEC Application rather than the UE. + +Therefore, the comparison EAS registration and EAS discovery of EDGEAPP [2] and ETSI MEC specification [13] shows that: + +**[Observation A.4-1]** The EAS registration and EAS discovery mechanism is defined in R17 of SA6 and ETSI MEC introduced MEC application registration (ETSI GS MEC 011 v3.0.6). It is FFS whether and how to address such differences in SA6, e.g. in support of ETSI MEC. + +**[Observation A.4-2]** ETSI MEC platform(MEP) supports service registration. In the registration parameter "ServiceInfo", there is a mandatory field "consumedLocalOnly" used to indicate that the service can only be consumed by the MEC applications located in the same locality, which means ETSI MEC services (produced by Authorized MEC APPs) registered and exposed on MEP can be invoked by MEC consumer APPs deployed on the same or another MEC host. + +# Annex B (Informative): Deployment and Evolution options of EDGEAPP and ETSI MEC platforms + +## B.1 General + +This clause provides the analysis to address the first open issue of KI#5, which intends to study and analyse different deployment options of EDGEAPP and ETSI MEC platforms. In that regard, this clause describes the following foreseen types of deployment and evolution scenarios for deployment of EDGEAPP and ETSI MEC. + +Annex C of TS 23.558 provides a relationship between EDGEAPP and ETSI MEC architectures as in figure below. + +![Diagram illustrating the relationship in EDGEAPP and ETSI MEC architecture. The diagram shows the flow of application data traffic from UE (Application Clients(s)) through the 3GPP Core Network to the MEC platform. The MEC platform is connected to the 3GPP Core Network via EDGE-7, EDGE-1, EDGE-2, EDGE-6, EDGE-9/Mp3, EDGE-4, and EDGE-8 interfaces. The MEC platform is also connected to the 3GPP Core Network via the EES (EDGE-3) and MEC Application (Mp1) components. The MEC platform is further connected to the Option for management and orchestration based on ETSI MEC, which includes the MEC Platform Manager, MEC Orchestrator, and Operation Support System (OSS). The MEC Platform Manager is connected to the MEC Orchestrator via Mm3 and Mm5 interfaces. The MEC Orchestrator is connected to the Operation Support System (OSS) via Mm1 and Mm2 interfaces. The Operation Support System (OSS) is connected to the User app LCM proxy via Mm8 and Mm9 interfaces. The User app LCM proxy is connected to the Customer Facing Service (CFS) Portal via Mx1 and Mx2 interfaces. The Customer Facing Service (CFS) Portal is connected to the Device app via Mx1 and Mx2 interfaces. The diagram also includes a legend indicating that ellipses depict reference points grouping two interfaces, EDGE* depict 3GPP SA6 interfaces, and Mp*, Mx* and Mm* depict ETSI MEC interfaces.](cdd4dfacab004e9979caed3fffea69e5_img.jpg) + +Legend: + +- Ellipse depicts a reference point grouping two interfaces +- EDGE\* depict 3GPP SA6 interfaces +- Mp\*, Mx\* and Mm\* depict ETSI MEC interfaces + +Diagram illustrating the relationship in EDGEAPP and ETSI MEC architecture. The diagram shows the flow of application data traffic from UE (Application Clients(s)) through the 3GPP Core Network to the MEC platform. The MEC platform is connected to the 3GPP Core Network via EDGE-7, EDGE-1, EDGE-2, EDGE-6, EDGE-9/Mp3, EDGE-4, and EDGE-8 interfaces. The MEC platform is also connected to the 3GPP Core Network via the EES (EDGE-3) and MEC Application (Mp1) components. The MEC platform is further connected to the Option for management and orchestration based on ETSI MEC, which includes the MEC Platform Manager, MEC Orchestrator, and Operation Support System (OSS). The MEC Platform Manager is connected to the MEC Orchestrator via Mm3 and Mm5 interfaces. The MEC Orchestrator is connected to the Operation Support System (OSS) via Mm1 and Mm2 interfaces. The Operation Support System (OSS) is connected to the User app LCM proxy via Mm8 and Mm9 interfaces. The User app LCM proxy is connected to the Customer Facing Service (CFS) Portal via Mx1 and Mx2 interfaces. The Customer Facing Service (CFS) Portal is connected to the Device app via Mx1 and Mx2 interfaces. The diagram also includes a legend indicating that ellipses depict reference points grouping two interfaces, EDGE\* depict 3GPP SA6 interfaces, and Mp\*, Mx\* and Mm\* depict ETSI MEC interfaces. + +**Figure B.1-1: Relationship in EDGEAPP and ETSI MEC architecture** + +**Editor's note:** Whether and how to enhance EDGE-9 or Mp3 is FFS. + +## B.2 Deployment options + +### B.2.1 Deployment Option-1: Collocated Platforms + +Based on Figure B.1-1, the two platforms (EES and MEC Platform) are co-located, and made by a single (unique) equipment, which is compliant with both standards. However, the actual deployment details of two platforms is implementation specific (Figure B.2.1-1). + +![Diagram of Deployment Option-1: Collocated Platforms. A large outer rectangle contains three inner boxes. At the top, 'EES' and 'MEC Platform' are side-by-side. Below them is a single box labeled 'Physical/NFV Infrastructure'.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +Diagram of Deployment Option-1: Collocated Platforms. A large outer rectangle contains three inner boxes. At the top, 'EES' and 'MEC Platform' are side-by-side. Below them is a single box labeled 'Physical/NFV Infrastructure'. + +Figure B.2.1-1: EES and MEC Platform as two different AFs on a single Physical/NFV Infrastructure + +### B.2.2 Deployment Option-2: Converged architecture + +#### B.2.2.1 General + +From the practical and business perspective, it is possible that an operator has deployed ETSI MEC architecture in its MEC sites to provide edge service since the stage 1 work of ETSI MEC has been already finished for a period of time. At the same time, the operator still cannot deploy EDGEAPP architecture since the stage 3 work of EDGEAPP is still not completed at the time being. + +On the other hand, it is assumed that an enhanced architecture, including a converged architecture as depicted in Figure B.2.2-1, will be introduced after completion of release 18. The converged architecture is expected to satisfy the following requirement: + +- The MEP+EES is able to satisfy all the functionalities of MEP defined in ETSI and EES defined in SA6. +- A uniform API is defined for the EAS and MEC app, i.e. EDGE-3 and Mp1 are unified into one interface and the EAS and MEC app will consume the same service from the MEP+EES. +- EDGE-9 and Mp3 are unified into one interface. + +NOTE: Management of MEP+EES is under the scope of SA5. + +![Diagram of Converged architecture for EDGEAPP and ETSI MEC alignment. Two boxes, 'EDN_1' and 'EDN_2', are shown. Each box contains 'EAS' and 'MEC App' at the top, 'MEP+EES' in the middle, and 'Physical/NFV infrastructure' at the bottom. A dashed line labeled 'EDGE-9/ Mp3' connects the 'MEP+EES' box in 'EDN_1' to the 'MEP+EES' box in 'EDN_2'. An ellipsis '...' follows 'EDN_2'.](1bf34e86af3591c80bfbc1c318f811c0_img.jpg) + +Diagram of Converged architecture for EDGEAPP and ETSI MEC alignment. Two boxes, 'EDN\_1' and 'EDN\_2', are shown. Each box contains 'EAS' and 'MEC App' at the top, 'MEP+EES' in the middle, and 'Physical/NFV infrastructure' at the bottom. A dashed line labeled 'EDGE-9/ Mp3' connects the 'MEP+EES' box in 'EDN\_1' to the 'MEP+EES' box in 'EDN\_2'. An ellipsis '...' follows 'EDN\_2'. + +Figure B.2.2.1-1 Converged architecture for EDGEAPP and ETSI MEC alignment + +The two platforms (EES and MEC Platform) are co-located which can be implemented as a single AF (e.g. realized as one VNF) compliant with both standards (Figure B.2.2-2). + +![Figure B.2.2.1-2: A diagram showing two stacked rectangular boxes within a larger outer box. The top box is labeled 'EES + MEC Platform' and the bottom box is labeled 'Physical/NFV Infrastructure'.](a3472689858b068ef469213682965325_img.jpg) + +Figure B.2.2.1-2: A diagram showing two stacked rectangular boxes within a larger outer box. The top box is labeled 'EES + MEC Platform' and the bottom box is labeled 'Physical/NFV Infrastructure'. + +**Figure B.2.2.1-2: EES and MEC Platform as a single AF on a single NFV Infrastructure (NFVI)** + +#### B.2.2.2 Evolution Options + +##### B.2.2.2.1 General + +In this clause the converged architecture is the architecture described in clause B.2.2 and satisfies the requirements listed in that clause. + +##### B.2.2.2.2 Evolution Option #1- Enhancement of a deployed MEP to support the functionality of EES + +After the completion of Release 18, an operator may determine to upgrade/evolve the ETSI MEC architecture to the converged architecture if the operator deployed ETSI MEC architecture in its MEC sites to provide edge service in the early stage. The MEP needs to be upgraded to the MEP+EES for supporting the functionality of EES defined in 3GPP SA6. The deployment and evolution scenario is depicted in Figure B.2.2.2-1. + +![Figure B.2.2.2-1: A diagram illustrating the evolution of MEC architecture. The 'Early stage' shows two boxes, EDN_1 and EDN_2, each containing two 'MEC App' boxes and a 'MEP' box. A red dashed line labeled 'Mp3' connects the 'MEP' boxes. A large downward arrow indicates a transition to the 'Later stage'. In the 'Later stage', the 'MEP' boxes are replaced by 'MEP+EES' boxes, and a new 'EAS' box is added to each. A red dashed line labeled 'EDGE-9/ Mp3' connects the 'MEP+EES' boxes.](5fbb4f0de01736f1293333e599410c99_img.jpg) + +Figure B.2.2.2-1: A diagram illustrating the evolution of MEC architecture. The 'Early stage' shows two boxes, EDN\_1 and EDN\_2, each containing two 'MEC App' boxes and a 'MEP' box. A red dashed line labeled 'Mp3' connects the 'MEP' boxes. A large downward arrow indicates a transition to the 'Later stage'. In the 'Later stage', the 'MEP' boxes are replaced by 'MEP+EES' boxes, and a new 'EAS' box is added to each. A red dashed line labeled 'EDGE-9/ Mp3' connects the 'MEP+EES' boxes. + +**Figure B.2.2.2-1 Evolution Option #1- An early stage deployed MEP is enhanced to support the functionality of EES in a later stage.** + +In Figure B.2.2.2-1, the EDN\_1 and EDN\_2 are deployed by the same operator. + +##### B.2.2.2.3 Evolution Option #2 Enhancement of a deployed EES to support the functionality of MEP + +After the completion of Release 18, an operator may opt to upgrade/evolve the EDGEAPP architecture to the converged architecture if the operator deployed EDGEAPP architecture in its EDNs to provide edge service in the early stage. The deployment and evolution scenario is depicted in Figure B.2.2.2.3-1. + +![Diagram illustrating the evolution of EDGEAPP architecture from Early stage to Later stage.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +The diagram illustrates the evolution of the EDGEAPP architecture from an early stage to a later stage. In the 'Early stage', two edge nodes, EDN\_1 and EDN\_2, are shown. Each node contains two EAS (Edge Application Server) units and an EES (Edge Enabler Server). A red dashed line labeled 'EDGE-9' connects the EES of EDN\_1 to the EES of EDN\_2. A large downward arrow indicates the transition to the 'Later stage'. In the 'Later stage', the architecture has evolved. EDN\_1 now contains an EAS, a MEC App, and a combined MEP+EES unit. EDN\_2 contains a similar configuration. A red dashed line labeled 'EDGE-9/ Mp3' connects the MEP+EES units of EDN\_1 and EDN\_2. Ellipses indicate additional nodes in both stages. + +Diagram illustrating the evolution of EDGEAPP architecture from Early stage to Later stage. + +Figure B.2.2.2.3-1 Evolution Option #2- Enhancement of a deployed EES to support the functionality of MEP + +### B.2.3 Deployment Option-3: non-Collocated Platforms + +The two platforms are non-collocated, and reside in two different data networks, where EES is in the Mobile Network Operator (MNO) domain while the ETSI MEC platform is in another MNO domain (Figure B.2.3-1). + +![Diagram illustrating the deployment of EES and MEC Platform as two different AFs in two different EDNs.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +The diagram shows two separate edge nodes, EDN#1 and EDN#2, separated by a vertical dashed line. EDN#1 contains an EES (Edge Enabler Server) and a 'Physical/NFV Infrastructure' block. EDN#2 contains a 'MEC Platform' and a 'Physical/NFV Infrastructure' block. This illustrates that the EES and MEC Platform are separate entities residing in different edge nodes. + +Diagram illustrating the deployment of EES and MEC Platform as two different AFs in two different EDNs. + +Figure B.2.3-1: EES and MEC Platform as two different AFs in two different EDNs + +# --- Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-07 | SA6#44-e | S6-211758 | | | | TR Skeleton | 0.0.0 | +| 2021-07 | SA6#44-e | | | | | S6-211754, S6-211759, S6-211760 | 0.1.0 | +| 2021-09 | SA6#45-e | | | | | S6-212048, S6-212054, S6-212087, S6-212103, S6-212115, S6-212142, S6-212166, S6-212167, S6-212168, S6-212169, S6-212170, S6-212171 | 0.2.0 | +| 2021-10 | SA6#45-BIS-e | | | | | S6-212478, S6-212402, S6-212479, S6-212480, S6-212481, S6-212482, S6-212207, S6-212411, S6-212206, S6-212403, S6-212483, S6-212401, S6-212484, S6-212486, S6-212456 | 0.3.0 | +| 2021-12 | SA6#46-BIS-e | | | | | S6-212720, S6-212730, S6-212748, S6-212796, S6-212807, S6-212813, S6-212829, S6-212830, S6-212831, S6-212832 | 0.4.0 | +| 2022-02 | SA6#47-e | | | | | S6-220077, S6-220457, S6-220458, S6-220459, S6-220460, S6-220340, S6-220461, S6-220274, S6-220420, S6-220462, S6-220479, S6-220299, S6-220102, S6-220463, S6-220464, S6-220465, S6-220466, S6-220468, S6-220480, S6-220469, S6-220470, S6-220349, S6-220454, S6-220455 | 0.5.0 | +| 2022-03 | SA6#47-e | | | | | Missing clause 7 from S6-220274 implemented. | 0.5.1 | +| 2022-04 | SA6#48-e | | | | | S6-220632, S6-220730, S6-220769, S6-220864, S6-220868, S6-220913, S6-220914, S6-220951, S6-220952, S6-220953, S6-220954, S6-220955, S6-220956, S6-220957, S6-220958, S6-220959, S6-220960, S6-220961, S6-220962, S6-220963, S6-220966, S6-220977, S6-220978 | 0.6.0 | +| 2022-05 | SA6#49-e | | | | | S6-221056, S6-221331, S6-221272, S6-221442, S6-221431, S6-221330, S6-221462, S6-221463, S6-221488, S6-221353, S6-221464, S6-221465, S6-221466, S6-221489, S6-221467, S6-221468, S6-221490, S6-221432, S6-221429, S6-221491, S6-221399, S6-221492, S6-221357, S6-221469, S6-221493, S6-221494, S6-221470, S6-221261, S6-221434, S6-221435, S6-221387, S6-221260, S6-221198 | 0.7.0 | +| 2022-05 | SA6#49-e | | | | | Implemented editorials related to S6-221429 and S6-221494. | 0.7.1 | +| 2022-06 | SA#96 | SP-220463 | | | | Presentation for information at SA#96 | 1.0.0 | +| 2022-06 | SA#96 | SP-220684 | | | | Implement missed changes as per S6-221432 and S6-221442. | 1.0.1 | +| 2022-07 | SA6#49-bis-e | | | | | S6-221883, S6-221969, S6-221885, S6-221970, S6-221971, S6-221887, S6-221862, S6-221799, S6-221972, S6-221973, S6-221974, S6-221975, S6-221937, S6-221938, S6-221939, S6-221996, S6-221940, S6-221524, S6-221525, S6-221976, S6-221977, S6-221978, S6-221889, S6-221997, S6-221775, S6-221801, S6-221979, S6-221983, S6-221980, S6-221793, S6-221981, S6-221982, S6-221627, S6-221672, S6-221984, S6-221935, S6-221985, S6-221986, S6-221620, S6-221988, S6-221989, S6-221688 | 1.1.0 | +| 2022-07 | SA6#49-bis-e | | | | | Reimplementation of S6-221980 | 1.1.1 | +| 2022-09 | SA6#50-e | | | | | S6-222577, S6-222121, S6-222483, S6-222486, S6-222395, S6-222307, S6-222575, S6-222576, S6-222599, S6-222600, S6-222370, S6-222028, S6-222029, S6-222345, S6-222578, S6-222080, S6-222532, S6-222500, S6-222579, S6-222580, S6-222581, S6-222477, S6-222601, S6-222460, S6-222602, S6-222308, S6-222582, S6-222495, S6-222583, S6-222138, S6-222584, S6-222504, S6-222585, S6-222586, S6-222096, S6-222425, S6-222111 | 1.2.0 | +| 2022-10 | SA6#51-e | | | | | S6-222887, S6-222950, S6-223012, S6-222688, S6-223053, S6-222955, S6-222918, S6-223020, S6-223055, S6-223056, S6-223057, S6-222958, S6-223008, S6-223011, S6-223007, S6-223058, S6-223059, S6-223060, S6-222937, S6-223061, S6-222728, S6-222848, S6-222873, S6-223080, S6-222712, S6-223062, S6-223079, S6-222861, S6-222862, S6-222952, S6-223063, S6-223064, S6-223065, S6-223066, S6-222963, S6-223067, S6-223019, S6-222944, S6-222781, S6-222834 | 1.3.0 | +| 2022-11 | SA6#52 | | | | | S6-223255, S6-223256, S6-223257, S6-223371, S6-223540, S6-223322, S6-223541, S6-223125, S6-223375, S6-223542, S6-223377, S6-223570, S6-223629, S6-223630, S6-223262, S6-223543, S6-223609, S6-223406, S6-223617, S6-223394, S6-223574, S6-223575, S6-223395, S6-223222, S6-223631, S6-223632, S6-223611, S6-223402, S6-223403, S6-223259, S6-223404 | 1.4.0 | +| 2022-11 | SA6#52 | | | | | Fixing S6-223395 implementation error. | 1.4.1 | +| 2022-12 | SA#98-e | SP-221225 | | | | Submitted for Approval at SA#98-e | 2.0.0 | +| 2022-12 | SA#98-e | SP-221225 | | | | MCC Editorial update for publication after TSG SA approval (SA#98-e) | 18.0.0 | +| 2023-03 | SA#99 | SP-230282 | 0003 | | F | Editorial correction in KI#2, Sol#49 and #51 | 18.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------|--------| +| 2023-03 | SA#99 | SP-230282 | 0004 | 2 | F | Open issue #2 will not be pursued in KI#9 of evaluation in Rel18 | 18.1.0 | +| 2023-03 | SA#99 | SP-230282 | 0005 | | F | Editorial corrections | 18.1.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23700-99/raw.md b/raw/rel-18/23_series/23700-99/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2cc508a6635c9a570ce294e9fdaf5576863b8d70 --- /dev/null +++ b/raw/rel-18/23_series/23700-99/raw.md @@ -0,0 +1,3424 @@ + + +# 3GPP TR 23.700-99 V18.2.0 (2023-06) + +*Technical Report* + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Network Slice Capability Exposure for Application Layer Enablement (NSCALE) (Release 18)** + +![5G Advanced logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for 5G Advanced, featuring a stylized '5G' with a green signal wave icon above the 'G' and the word 'ADVANCED' in smaller letters to the right. + +5G Advanced logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a bold, black, stylized font. Below the 'P' is a red signal wave icon. Underneath the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. + +The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. + +This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions of terms, symbols and abbreviations..... | 9 | +| 3.1 Terms..... | 9 | +| 3.2 Symbols..... | 9 | +| 3.3 Abbreviations ..... | 9 | +| 4 Application architecture for network slice capability enablement..... | 10 | +| 4.1 Architectural requirements..... | 10 | +| 4.1.1 General requirements..... | 10 | +| 4.1.2 Security requirements ..... | 10 | +| 4.1.3 Registration requirement ..... | 10 | +| 4.1.4 Discovery requirement ..... | 10 | +| 4.1.5 Lifecycle management requirement ..... | 10 | +| 4.2 Application architecture ..... | 11 | +| 4.2.1 General ..... | 11 | +| 4.2.2 Architecture ..... | 11 | +| 4.2.3 Functional elements..... | 13 | +| 4.2.3.1 Network slice Capability Enablement client ..... | 13 | +| 4.2.3.2 Network slice Capability Enablement server..... | 13 | +| 4.2.4 Service-based interfaces ..... | 13 | +| 4.2.5 Reference points description ..... | 13 | +| 4.2.5.1 VAL-UU ..... | 13 | +| 4.2.5.2 NSCE-UU ..... | 14 | +| 4.2.5.3 NSCE-C ..... | 14 | +| 4.2.5.4 NSCE-S..... | 14 | +| 4.2.5.5 NSCE-E ..... | 14 | +| 4.3 Cardinality rules ..... | 14 | +| 4.3.1 General ..... | 14 | +| 4.3.2 Functional Entity Cardinality ..... | 14 | +| 4.3.2.1 VAL Client ..... | 14 | +| 4.3.2.2 NSCE Client ..... | 14 | +| 4.3.2.3 NSCE Server..... | 14 | +| 4.3.2.6 VAL Server..... | 14 | +| 4.3.3 Service Cardinality ..... | 15 | +| 5 Key issues ..... | 15 | +| 5.1 Key issue 1: Network slice capability management enhancements ..... | 15 | +| 5.2 Key issue 2: Application layer exposed network slice lifecycle management ..... | 15 | +| 5.3 Key issue 3: Discovery & registration aspects for management service exposure..... | 16 | +| 5.4 Key issue 4: Network slice fault management capability ..... | 16 | +| 5.5 Key issue 5: Communication service management exposure ..... | 17 | +| 5.6 Key issue 6: Application layer QoS verification capability enablement ..... | 18 | +| 5.7 Key issue 7: Network slice related performance and analytics exposure ..... | 18 | +| 5.8 Key issue 8: Support for requirements translation..... | 19 | +| 5.9 Key issue 9: Support for trust enablement ..... | 19 | +| 5.10 Key Issue 10: Support for managing trusted third-party owned application(s)..... | 20 | +| 5.11 Key issue 11: Slice requirement alignment..... | 20 | +| 5.12 Key issue 12: Network slice capability exposure in the edge data network ..... | 21 | +| 5.13 Key issue 13: Delivery of the existing Network Slice information to the trusted third-party ..... | 21 | +| 5.14 Key issue 14: Network Slice creation to the third-party and UE ..... | 22 | +| 6 Solutions..... | 23 | +| 6.0 Mapping of Solutions to Key Issues ..... | 23 | +| 6.1 Solution 1: Automatic application layer network slice management..... | 24 | + +| | | | +|-----------|--------------------------------------------------------------------------------------|----| +| 6.1.1 | Solution description..... | 24 | +| 6.1.1.1 | General..... | 24 | +| 6.1.1.2 | Automatic application layer network slice lifecycle management ..... | 25 | +| 6.1.2 | Solution evaluation..... | 26 | +| 6.2 | Solution 2: Network slice fault management capability ..... | 26 | +| 6.2.1 | Solution description..... | 26 | +| 6.2.1.1 | General..... | 26 | +| 6.2.1.2 | Network slice fault management capability exposure ..... | 27 | +| 6.2.2 | Solution evaluation..... | 28 | +| 6.3 | Solution 3: Slice API configuration and translation..... | 28 | +| 6.3.1 | Solution description..... | 28 | +| 6.3.1.1 | General..... | 28 | +| 6.3.1.2 | slice API configuration ..... | 29 | +| 6.3.1.3 | Slice API translation ..... | 30 | +| 6.3.2 | Solution evaluation..... | 31 | +| 6.4 | Solution 4: QoS verification capability..... | 32 | +| 6.4.1 | Solution description..... | 32 | +| 6.4.1.1 | General..... | 32 | +| 6.4.1.2 | QoS verification capability ..... | 32 | +| 6.4.2 | Solution evaluation..... | 33 | +| 6.5 | Solution 5: Network slice related performance and analytics exposure ..... | 33 | +| 6.5.1 | Solution description..... | 33 | +| 6.5.1.1 | General..... | 33 | +| 6.5.1.2 | Network slice related performance and analytics exposure..... | 33 | +| 6.5.1.2.1 | KQI and performance data report from NSCE client..... | 35 | +| 6.5.2 | Solution evaluation..... | 36 | +| 6.6 | Solution 6: VAL server authorization and authentication via slice enabler layer..... | 37 | +| 6.6.1 | Solution description..... | 37 | +| 6.6.1.1 | General..... | 37 | +| 6.6.1.2 | VAL server authorization and authentication via slice enabler layer..... | 37 | +| 6.6.2 | Solution evaluation..... | 38 | +| 6.7 | Solution 7: network slice capability registration..... | 38 | +| 6.7.1 | Solution description..... | 38 | +| 6.7.1.1 | General..... | 38 | +| 6.7.1.2 | Capability exposure registration ..... | 38 | +| 6.7.2 | Solution evaluation..... | 39 | +| 6.8 | Solution 8: Discovery of management service exposure ..... | 39 | +| 6.8.1 | Solution description..... | 39 | +| 6.8.1.1 | General..... | 39 | +| 6.8.1.2 | Procedure ..... | 39 | +| 6.8.2 | Solution evaluation..... | 41 | +| 6.9 | Solution 9: Support for managing trusted third-party owned application(s) ..... | 41 | +| 6.9.1 | Solution description..... | 41 | +| 6.9.1.1 | General..... | 41 | +| 6.9.1.2 | Network slice quota management capability exposure..... | 41 | +| 6.9.2 | Solution evaluation..... | 42 | +| 6.10 | Solution 10: Network slice application policy management capability ..... | 42 | +| 6.10.1 | Solution description..... | 42 | +| 6.10.1.1 | General..... | 42 | +| 6.10.1.2 | Network slice application policy management capability ..... | 42 | +| 6.10.2 | Solution evaluation..... | 44 | +| 6.11 | Solution 11: Communication service management exposure ..... | 44 | +| 6.11.1 | Solution description..... | 44 | +| 6.11.1.1 | General..... | 44 | +| 6.11.1.2 | Use Case of Communication service lifecycle management..... | 44 | +| 6.11.1.3 | Communication service creation ..... | 47 | +| 6.11.1.4 | Communication service modification..... | 47 | +| 6.11.1.5 | Communication service disengagement ..... | 48 | +| 6.11.2 | Solution evaluation..... | 48 | +| 6.12 | Solution 12: SEAL enhancement..... | 48 | +| 6.12.1 | Solution description..... | 48 | +| 6.12.2 | Solution evaluation..... | 49 | + +| | | | +|----------|---------------------------------------------------------------------------------------------|----| +| 6.13 | Solution 13: Network Slice Allocation by VAL server ..... | 50 | +| 6.13.1 | Solution description..... | 50 | +| 6.13.1.1 | General..... | 50 | +| 6.13.1.2 | Network Slice Allocation by VAL Server..... | 50 | +| 6.13.2 | Solution evaluation..... | 52 | +| 6.14 | Solution 14: Interaction between the NSCE servers ..... | 52 | +| 6.14.1 | Solution description..... | 52 | +| 6.14.2 | Information collection from multiple NSCE servers..... | 52 | +| 6.14.3 | Solution evaluation..... | 52 | +| 6.15 | Solution 15: UE triggered network slice adaptation ..... | 53 | +| 6.15.1 | Solution description..... | 53 | +| 6.15.1.1 | General..... | 53 | +| 6.15.2 | Solution evaluation..... | 57 | +| 6.16 | Solution 16: Multi-Network slice management capability ..... | 57 | +| 6.16.1 | Solution description..... | 57 | +| 6.16.1.1 | General..... | 57 | +| 6.16.1.2 | Multi-Network slice management capability..... | 57 | +| 6.16.2 | Solution evaluation..... | 59 | +| 6.17 | Solution 17: Multi-Network slice resource optimization ..... | 59 | +| 6.17.1 | Solution description..... | 59 | +| 6.17.1.1 | General..... | 59 | +| 6.17.1.2 | Multi-Network slice management capability..... | 59 | +| 6.17.2 | Solution evaluation..... | 61 | +| 6.18 | Solution 18: Network Slice Information Delivery ..... | 61 | +| 6.18.1 | Solution description..... | 61 | +| 6.18.1.1 | General..... | 61 | +| 6.18.1.2 | Network Slice Information delivery ..... | 62 | +| 6.18.1.3 | Network Slice Information subscription..... | 63 | +| 6.18.1.4 | Network Slice Information Notify ..... | 64 | +| 6.18.1.5 | Network Slice Information delivery while registration ..... | 65 | +| 6.18.2 | Solution evaluation..... | 66 | +| 6.19 | Solution 19: Slice requirements alignment capability..... | 67 | +| 6.19.1 | Solution description..... | 67 | +| 6.19.1.1 | General..... | 67 | +| 6.19.1.2 | Slice requirements alignment capability..... | 67 | +| 6.19.2 | Solution evaluation..... | 68 | +| 6.20 | Solution 20: Network slice optimization based on AF policy ..... | 68 | +| 6.20.1 | Solution description..... | 68 | +| 6.20.1.1 | General..... | 68 | +| 6.20.1.2 | OAM event triggered network slice optimization ..... | 69 | +| 6.20.1.3 | NWDAF event triggered network slice optimization..... | 70 | +| 6.20.1.4 | NSCE server triggered network slice optimization ..... | 71 | +| 6.20.1.5 | AF policy provisioning ..... | 72 | +| 6.20.2 | Solution evaluation..... | 73 | +| 6.21 | Solution 21: Solution on predictive slice modification in edge based NSCE deployments ..... | 73 | +| 6.21.1 | Solution description..... | 73 | +| 6.21.1.1 | General..... | 73 | +| 6.21.1.1 | Procedure ..... | 74 | +| 6.21.2 | Solution evaluation..... | 75 | +| 6.22 | Solution #22: Slice policy and configuration alignment..... | 75 | +| 6.22.1 | Solution description..... | 75 | +| 6.22.1.1 | General..... | 75 | +| 6.22.1.2 | Procedure ..... | 75 | +| 6.22.2 | Solution evaluation..... | 76 | +| 7 | Identities and commonly used values ..... | 77 | +| 7.1 | General ..... | 77 | +| 7.2 | VAL server ID..... | 77 | +| 7.3 | NSCE server ID..... | 77 | +| 7.4 | NSCE client ID..... | 77 | +| 7.5 | VAL client ID..... | 77 | +| 7.6 | UE ID ..... | 77 | + +| | | | +|---------------------------------------------------------------------------------|------------------------------------------------------------------------------|-----------| +| 7.7 | slice coverage area ..... | 77 | +| 7.8 | NSCE service area..... | 77 | +| 8 | Overall evaluation ..... | 78 | +| 8.1 | General ..... | 78 | +| 8.2 | Solution evaluations ..... | 78 | +| 8.2.1 | General ..... | 78 | +| 8.2.2 | Overall Evaluation for KI#1 ..... | 79 | +| 8.2.3 | Overall Evaluation for KI#10 ..... | 79 | +| 8.2.4 | Overall Evaluation for KI#12 ..... | 79 | +| 8.3 | Architecture evaluations..... | 80 | +| 9 | Conclusions..... | 80 | +| Annex A | Deployment models ..... | 83 | +| A.1 | Deployment scenarios ..... | 83 | +| A.1.1 | General ..... | 83 | +| A.1.2 | Centralized NSCE deployment..... | 83 | +| A.1.3 | Distributed NSCE deployment ..... | 83 | +| A.1.3.1 | NPN NSCE deployment..... | 84 | +| A.1.3.2 | Edge NSCE deployment..... | 84 | +| A.2 | Deployment of NSCE server(s) in relation to VAL server and 3GPP system ..... | 85 | +| Annex B (informative): Business models and relationships for NSCALE..... | | 86 | +| Annex B.1: | Relevance to SA5 models ..... | 86 | +| Annex B.2: | Business relationships..... | 88 | +| Annex C:Change history ..... | | 90 | + +# Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +| | | +|-------------------|------------------------------------------------| +| should | indicates a recommendation to do something | +| should not | indicates a recommendation not to do something | +| may | indicates permission to do something | +| need not | indicates permission not to do something | + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +| | | +|---------------|----------------------------------------| +| can | indicates that something is possible | +| cannot | indicates that something is impossible | + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +| | | +|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| will | indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document | +| will not | indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document | +| might | indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document | +| might not | indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document | + +In addition: + +| | | +|---------------|-----------------------------------------------------------------------------------| +| is | (or any other verb in the indicative mood) indicates a statement of fact | +| is not | (or any other negative verb in the indicative mood) indicates a statement of fact | + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The study identifies the SA1 requirements and potential vertical requirements of network slice capability exposure that have yet to be realized, and proposes application architecture aspects solutions and enhancements to SEAL. Based on any gaps found between requirements and existing capabilities, the present document includes: identification of key issues, solutions, corresponding evaluations and conclusions to ensure the efficient network slice capability exposure. + +The study takes into consideration the SEAL architecture specified in 3GPP TS 23.434 [2], network slicing related architecture and services (such as services of NEF) specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4], network slicing management capability provisioning and architecture specified in 3GPP TS 28.531 [5] and 3GPP TS 28.533 [6], requirements specified in TS 22.261 [7]. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + +- For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows". +- [3] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". +- [4] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". +- [5] 3GPP TS 28.531: "Management and orchestration; Provisioning". +- [6] 3GPP TS 28.533: "Management and orchestration; Architecture framework". +- [7] 3GPP TS 22.261: "Service requirements for the 5G system". +- [8] 3GPP TS 28.532: "Management and orchestration; Generic management services". +- [9] 3GPP TR 22.835: "Study on enhanced access to and support of network slices". +- [10] 3GPP TS 28.545: "Management and orchestration; Fault Supervision (FS) ". +- [11] 3GPP TS 28.535: "Management and orchestration; Management services for communication service assurance; Requirements". +- [12] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". +- [13] 3GPP TS 28.550: "Management and orchestration; Performance assurance". +- [14] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3". +- [15] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics". +- [16] 3GPP TS 32.111-1: "Management and orchestration; Fault management, Part 1: 3G fault management requirements". +- [17] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". +- [18] 3GPP TS 22.263: "Services and System Aspects; Service requirements for video, imaging and audio for professional applications (VIAPA)". +- [19] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [20] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2". +- [21] 3GPP TS 33.434: "Security aspects of Service Enabler Architecture Layer (SEAL) for verticals". +- [22] 3GPP TS 29.536: "5G System; Network Slice Admission Control Service; Stage 3". +- [23] 3GPP TS 32.404: "Performance Management (PM); Performance measurements; Definitions and template". +- [24] 3GPP TS 28.554: "Management and orchestration ; 5G end to end Key Performance Indicators (KPI)". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----------|---------------| +| | | +|----------|---------------| + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------------|-------------| +| | | +|----------------|-------------| + +| | | +|-------------|----------------------------------------------------------------| +| ASP | Application Service Provider | +| Auto-NS-LCM | Automatic Application Layer Network Slice Lifecycle Management | +| EDN | Edge Data Network | +| EGMF | Exposure Governance Management Function | +| GST | Generic Network Slice Template | +| KPI | Key Performance Indicator | +| KQI | Key Quality Indicator | +| MnS | Management Service | +| NEF | Network Exposure Function | +| NEST | Network Slice Template | +| NOP | Network Operator | +| NSCE | Network Slice Capability Enablement | +| NSaaS | Network Slice as a Service | +| NSI | Network Slice Instance | +| NSSI | Network Slice Subnet Instance | +| NWDAF | Network Data Analytics Function | +| NSACF | Network Slice Admission Control Function | +| NSC | Network Slice consumer | +| NSP | Network Slice Provider | +| NSMF | Network Slice Management Function | +| OAM | Operation, administration and maintenance | +| QoE | Quality of Experience | +| S-NSSAI | Single Network Slice Selection Assistance Information | +| VAL | Vertical Application Layer | + +# 4 Application architecture for network slice capability enablement + +## 4.1 Architectural requirements + +### 4.1.1 General requirements + +[AR.4.1.1-a] The application enablement layer shall support interaction with 3GPP network management system to consume network slice management service. + +NOTE: The consuming of the network slice management service related procedures are specified in TS 28.531[5]. + +NOTE: The Network Slice Capability Enablement (NSCE) layer acts a service consumer utilizing the management services exposed by EGMF as defined in SA5 TS 28.533[6] if authorized. + +[AR-4.1.1-b] The NSCE architecture shall support one or more applications from the same vertical. + +[AR-4.1.1-c] The NSCE client shall be able to communicate to multiple NSCE servers. + +[AR-4.1.1-d] The API interactions between the vertical application server(s) and NSCE server(s) shall conform to CAPIF as specified in 3GPP TS 23.222 [20]. + +[AR-4.1.1-e] The NSCE server(s) shall provide a service API compliant with CAPIF as specified in 3GPP TS 23.222 [20]. + +### 4.1.2 Security requirements + +[AR-4.1.2-a] The application architecture shall provide mechanisms to authorize the usage of network slicing related services by the VAL servers and NSCE clients. + +[AR-4.1.2-b] The application architecture shall support mutual authentication and authorization check between clients and servers, servers and servers that interact. + +NOTE: The authentication and authorization aspects related to VAL servers and NSCE enablers are out scope of this study and to be addressed by SA3, in TS 33.434[21]. + +### 4.1.3 Registration requirement + +[AR.4.1.3-a] The application layer architecture shall provide mechanisms for an VAL server to register onto the NSCE servers. + +### 4.1.4 Discovery requirement + +[AR.4.1.4-a] The application layer architecture shall provide mechanisms for the discovery of NSCE services exposure to the VAL server. + +### 4.1.5 Lifecycle management requirement + +[AR.4.1.5-1] The application layer architecture shall provide a mechanism for lifecycle management of network slice to VAL server. + +[AR.4.1.5-2] The application layer architecture shall provide a mechanism for lifecycle management of network slice communication service to VAL server. + +### 4.1.6 Performance data retrieval requirement + +[AR.4.1.6-1] The application layer architecture shall provide a mechanism to the VAL server to compare between the requested and actual slice QoS. + +[AR.4.1.6-2] The application layer architecture shall provide a mechanism to support aggregation of slice performance information retrieved from all applicable sources. + +[AR.4.1.6-3] The application layer architecture shall provide a mechanism to the VAL server to retrieve that aggregated slice performance data. + +## 4.2 Application architecture + +### 4.2.1 General + +This clause provides the overall architecture description: + +- Clause 4.2.2 describes the application architecture in the service based representation and reference point representation; +- Clause 4.2.3 describes the functional entities; + +### 4.2.2 Architecture + +![Figure 4.2.2-1: Architecture for network slice capability enablement – Service based representation. The diagram shows a User Equipment (UE) on the left and a network slice capability enablement server on the right, separated by a dashed vertical line. Inside the UE, there is a 'VAL client' and a 'Network slice capability Enablement client' connected by the 'Uns-ce' interface. The 'Network slice capability Enablement client' connects to a horizontal service interface line. On the right side of the line, there is an 'Application function(AF) [VAL Server]' connected via the 'Nas[Sval]' interface and an 'Application function(AF) [Network slice capability Enablement server]' connected via the 'Naf[Sncse]' interface.](18442e4e239480f0c3c95b547aa8fde2_img.jpg) + +``` +graph LR + subgraph UE + VC[VAL client] + NSCEC[Network slice capability Enablement client] + VC --- Uns-ce[Uns-ce] + NSCEC + end + NSCEC --- SBI((Service Based Interface)) + subgraph Network + VALServer[Application function(AF) [VAL Server]] + NSCEServer[Application function(AF) [Network slice capability Enablement server]] + VALServer --- NasSval[Nas[Sval]] + NSCEServer --- NafSncse[Naf[Sncse]] + end +``` + +Figure 4.2.2-1: Architecture for network slice capability enablement – Service based representation. The diagram shows a User Equipment (UE) on the left and a network slice capability enablement server on the right, separated by a dashed vertical line. Inside the UE, there is a 'VAL client' and a 'Network slice capability Enablement client' connected by the 'Uns-ce' interface. The 'Network slice capability Enablement client' connects to a horizontal service interface line. On the right side of the line, there is an 'Application function(AF) [VAL Server]' connected via the 'Nas[Sval]' interface and an 'Application function(AF) [Network slice capability Enablement server]' connected via the 'Naf[Sncse]' interface. + +**Figure 4.2.2-1 Architecture for network slice capability enablement – Service based representation** + +Figure 4.2.2-1 exhibits the service-based interfaces for providing and consuming network slice capability enablement services. + +The mechanisms for service discovery in the service-based representation depicted in figure 4.2.2-1 are as follows: + +- The network slice capability enablement server could provide service to VAL server and NSCE client through interface Snsce. + +Figure 4.2.2-2 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in 3GPP TS 23.501[3] and TS 28.533[6]. + +![Figure 4.2.2-2: Architecture for network slice capability enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation. The diagram shows two Application functions (AF) at the top: 'Application function(AF) [Network slice capability Enablement server]' and 'Application function(AF) [VAL Server]'. Both are connected to a central Service Based Interface (SBI). Below the SBI, three network functions are connected: PCF (via Npcf), SCEF+NEF/NEF (via Nnef), and EGMF (via MnS).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Figure 4.2.2-2: Architecture for network slice capability enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation. The diagram shows two Application functions (AF) at the top: 'Application function(AF) [Network slice capability Enablement server]' and 'Application function(AF) [VAL Server]'. Both are connected to a central Service Based Interface (SBI). Below the SBI, three network functions are connected: PCF (via Npcf), SCEF+NEF/NEF (via Nnef), and EGMF (via MnS). + +**Figure 4.2.2-2: Architecture for network slice capability enablement utilizing the 5GS network services based on the 5GS SBA – Service based representation** + +Figure 4.2.2-3 depicts the network slice capability enablement architecture in the non-roaming case, using the reference point representation showing how various entities interact with each other. + +![Figure 4.2.2-3: Architecture for network slice capability enablement – reference points representation. The diagram is divided into three vertical sections: VAL UE, 3GPP network system, and VAL server(s). The VAL UE contains 'VAL client(s)' and 'Network slice capability enablement client'. The 3GPP network system contains 'NSCE-UU', 'N33/N5', and 'NSCE-OAM'. The VAL server(s) contains 'Network slice capability enablement server'. Reference points are labeled: VAL-UU between VAL client(s) and 3GPP network system; NSCE-C between VAL client(s) and Network slice capability enablement client; NSCE-UU between Network slice capability enablement client and 3GPP network system; NSCE-S between VAL server(s) and Network slice capability enablement server. A dashed line separates the VAL section from the SEAL section.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +Figure 4.2.2-3: Architecture for network slice capability enablement – reference points representation. The diagram is divided into three vertical sections: VAL UE, 3GPP network system, and VAL server(s). The VAL UE contains 'VAL client(s)' and 'Network slice capability enablement client'. The 3GPP network system contains 'NSCE-UU', 'N33/N5', and 'NSCE-OAM'. The VAL server(s) contains 'Network slice capability enablement server'. Reference points are labeled: VAL-UU between VAL client(s) and 3GPP network system; NSCE-C between VAL client(s) and Network slice capability enablement client; NSCE-UU between Network slice capability enablement client and 3GPP network system; NSCE-S between VAL server(s) and Network slice capability enablement server. A dashed line separates the VAL section from the SEAL section. + +**Figure 4.2.2-3: Architecture for network slice capability enablement – reference points representation** + +The network slice capability enablement client communicates with the network slice capability enablement server over the NSCE-UU reference point. The network slice capability enablement client provides the support for network slice capability enablement functions to the VAL client(s) over NSCE-C reference point. The VAL server(s) communicates with the network slice capability enablement server over the NSCE-S reference point. The network slice capability enablement server, acting as AF, may communicate with the 5G Core Network functions via NEF (N33) reference point (for interactions with PCF, NSACF, etc.), or interacting with PCF directly via N5, if permitted. The network slice capability enablement server may interact with OAM system over NSCE-OAM reference point, as consumer in both NSaaS and NoP model (for Network Slice Provisioning capabilities, Performance Assurance, Fault Supervision etc.). + +NOTE: The NSCE-OAM reference point can be realized by the services exposed by EGMF as defined in TS 28.533[6]. + +Figure 4.2.2-4 illustrates the architecture for interconnection between NSCE servers. + +![Diagram illustrating the interconnection between two NSCE servers. The diagram is divided into two layers by a dashed horizontal line: VAL (top) and SEAL (bottom). In the VAL layer, each server has a 'VAL server(s)' block. In the SEAL layer, each server has an 'NSCE-S' block connected to a 'Network slice capability enablement server' (labeled 1 and 2). The two Network slice capability enablement servers are connected to each other via an 'NSCE-E' reference point.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +graph TD + subgraph VAL + VAL_server_1[VAL server(s)] + VAL_server_2[VAL server(s)] + end + subgraph SEAL + NSCE_S_1[NSCE-S] + NSCE_S_2[NSCE-S] + NSCE_E[NSCE-E] + NSCE_S_1 --- NSCE_E --- NSCE_S_2 + end + VAL_server_1 --- NSCE_S_1 + VAL_server_2 --- NSCE_S_2 + NSCE_S_1 --- NSCE_E + NSCE_E --- NSCE_S_2 + NSCE_S_1 --- NSCE_S_2 + NSCE_S_1 --- Network_slice_capability_enablement_server_1[Network slice capability enablement server 1] + NSCE_S_2 --- Network_slice_capability_enablement_server_2[Network slice capability enablement server 2] + Network_slice_capability_enablement_server_1 --- NSCE_E + Network_slice_capability_enablement_server_2 --- NSCE_E + +``` + +Diagram illustrating the interconnection between two NSCE servers. The diagram is divided into two layers by a dashed horizontal line: VAL (top) and SEAL (bottom). In the VAL layer, each server has a 'VAL server(s)' block. In the SEAL layer, each server has an 'NSCE-S' block connected to a 'Network slice capability enablement server' (labeled 1 and 2). The two Network slice capability enablement servers are connected to each other via an 'NSCE-E' reference point. + +**Figure 4.2.2-4: Interconnection between NSCE servers** + +The NSCE server could interact with another NSCE server over NSCE-E reference point. + +### 4.2.3 Functional elements + +#### 4.2.3.1 Network slice Capability Enablement client + +The network slice capability enablement client functional entity acts as the application client for the slice enablement. The network slice capability enablement client interacts with the network slice capability enablement server to trigger a network slice related operations. This trigger may be due to an application QoS requirement change, a service operation change, a network slice status change, etc. The NSCE client may receive a network slice related notification from the NSCE server. The NSCE client may optionally notify the VAL client on the network slice / DNN change. + +#### 4.2.3.2 Network slice Capability Enablement server + +The network slice capability enablement server functional entity provides application layer enablement to support the network slice management and control with/without invoking control and management plane capabilities from SA2 and SA5 pertaining to network slicing. Such enablement supports the network slice related operations such as the mapping or migration of one or more vertical applications to one or more network slices, triggering the dynamic network slice lifecycle management, NSI/NSSI monitoring, etc. + +### 4.2.4 Service-based interfaces + +The architecture for enabling network slice capability enablement service contains the following service-based interfaces: + +Sval: Service-based interface exhibited by VAL server. + +Snsce: Service-based interface exhibited by NSCE server. + +Unsce-c: Service-based interface exhibited by NSCE client. + +NOTE: Detailed specification of Unsce-c is based on implementation. + +### 4.2.5 Reference points description + +#### 4.2.5.1 VAL-UU + +The interactions related to vertical application layer support functions between VAL client and VAL server are supported by VAL-UU reference point. This reference point is an instance of Uu reference point as described in 3GPP TS 23.401 [9] and 3GPP TS 23.501 [10]. + +NOTE: The details of VAL-UU reference point is out of scope of the present document. + +#### 4.2.5.2 NSCE-UU + +The interactions between a NSCE client and the corresponding NSCE server are generically referred to as NSCE-UU reference point. This reference point supports fault data, QoE data and KQI data provisioning etc. + +#### 4.2.5.3 NSCE-C + +The interactions between the VAL client(s) and the NSCE client(s) within a VAL UE are generically referred to as NSCE-C reference point. This reference point supports obtaining information about network slice that VAL client(s) require, application client information (such as its KQI) provisioning etc. + +#### 4.2.5.4 NSCE-S + +The interactions between the VAL server and the NSCE server are generically referred to as NSCE-S reference point. This reference point supports network slice capability exposure such as: application layer slice lifecycle management, fault diagnosis, slice API configuration and mapping, QoS verification, slice performance analytics exposure etc. + +#### 4.2.5.5 NSCE-E + +The interactions between the NSCE servers are generically referred to as NSCE-E reference point. This reference point supports information collection from other NSCE servers. + +**Editor's Note:** The supported capabilities for NSCE-E are FFS. + +## 4.3 Cardinality rules + +### 4.3.1 General + +The cardinality rules are applied to the architecture specified in clause 4.2. The cardinality rules are based on functional elements. The functional elements cardinality specifies the multiplicity of the functional elements that can exist as per the architecture. + +### 4.3.2 Functional Entity Cardinality + +#### 4.3.2.1 VAL Client + +The following cardinality rules apply for VAL Clients: + +- a) One or more VAL Clients may be located in a UE. + +#### 4.3.2.2 NSCE Client + +The following cardinality rules apply for NSCE Clients: + +- a) One or more NSCE Client(s) may be located in a UE. + +#### 4.3.2.3 NSCE Server + +The following cardinality rules apply for NSCE Server: + +- a) One or more NSCE Server(s) may be located in an PLMN; and +- b) One or more NSCE Server(s) may be located in an PLMN per Network slice Provider. + +#### 4.3.2.6 VAL Server + +The following cardinality rules apply for VAL Servers: + +- a) One or more VAL Server(s) may be served by one NSCE server. + +### 4.3.3 Service Cardinality + +- a) One NSCE server may enable one or more Network slice(s) identified by S-NSSAI(s); +- b) One Network slice can only be enabled and served by one NSCE server. +- c) The NSCE servers may provide service in the same or in different Tracking Areas. + +# --- 5 Key issues + +## 5.1 Key issue 1: Network slice capability management enhancements + +SEAL is the service enabler architecture layer common to all vertical applications over 3GPP systems. It provides the functions like location management, group management, configuration management, identity management, key management, network resource management and network slice capability management as defined in 3GPP TS 23.434 [2]. + +Network slicing is a general network capability which can be applied for many vertical industries. The network slice capability management service in 3GPP TS 23.434 [2] only provides capability of network slice adaptation between NSCE server and the NSCE client. However, for such capability both control plane and management plane interactions need to be considered since there is close coupling between the per UE session and the per slice related actions. For example, the SEAL/NSCE layer may need to be aware of the slice provisioning parameters (NSI/NSSI configuration) which can be provided by the slice management system. Furthermore, NSI/NSSI performance monitoring from management system (e.g. NSI/ NSSI status) may be useful to be known at the enabler layer, since this may affect the application to slice re-mapping triggering (e.g. to re-map to the least congested slice); and may also impact other SEAL provided functionalities (e.g. QoS/resource control, group management etc). + +Open issues: + +- Whether and which enhancement to SEAL network slice capability management service is required having in mind SA2 and SA5 slice related exposure? +- Whether a potential enhancement to SEAL network slice capability management functional model is required? +- Whether new or enhanced APIs are needed to support the potential SEAL enhancements? +- How the network slice capability (such as management service (MnS)) consumption may trigger and impact the value-add services provided by the SEAL layer? + +## 5.2 Key issue 2: Application layer exposed network slice lifecycle management + +It is specified in clause 6.10 of 3GPP TS 22.261 [7] that 5G network is required to provide suitable APIs to allow a trusted third-party to create, modify, scale and delete network slices used for the third-party. As specified in 28.531 [5], SA5 has defined the network slice lifecycle management service. SA6 can provide a more concise application layer exposed network slice lifecycle management with additional functionality for verticals. It can help vertical do the lifecycle management without knowledge of SA5 O&M defined interfaces and APIs. In addition, with the network slice related information (such as network slice status reported from NSACF), the SA6 could trigger some slice lifecycle management operations automatically to provide a value-added lifecycle management service. It is not clear how to expose the network slice lifecycle management service from application perspective with providing additional value on top of existing SA5 solution. + +NOTE: The interface which may be used in this KI is specified in TS 28.532 [8], and the enabler layer could use the interface exposed by EGMF defined in TS 28.533[6]. + +Hence, it is required to study the following issues: + +- How to integrate and expose the SA5 and SA2 network slice related capability to provide some value-added lifecycle management service from application layer? +- Whether and how additional service APIs are required to be supported for application layer enablement of network slice lifecycle management? +- Whether and how CAPIF can be leveraged for additional service APIs. + +## 5.3 Key issue 3: Discovery & registration aspects for management service exposure + +There are use cases (being discussed also in SA1, TR 22.835 [9]), where the applications (e.g. gaming or online video applications) may access the 5GS over multiple slices for different services (e.g. based on the user membership); or have different priorities on different slices based on Application Service Provider (ASP) request. As an example, a mobile network operator has provisioned a set of network slices (Slice#1, Slice#2, Slice#3) which may be used by different ASPs (e.g. Slice#1 for online video services, Slice#2 for gaming, Slice#3 for eMBB or IOT service). Different ASPs may use these slices (or a subset of them) for different services that they offer. Furthermore, when an application changes the network slices to be accessed, it should be agnostic to the UEs accessing the service and should be performed automatically. + +The vertical enablement layer (SEAL, vertical-specific enablers) supports the exposure of telco provided services to the vertical / application service provider (ASP). Such telco-provided services traditionally covered the 3GPP control plane services (provided by SA2); however, these can be extended to 3GPP management domain services (provided by SA5) which may be useful for allowing the ASP to monitor and manage the slices used by the UEs. The enabler layer can be seen as a trusted application entity that interacts with the management system on behalf of ASP to allow the exposure of management services related to the offered slices. It can be used to trigger dynamic slice-related actions and also reduce complexity at the ASP side. + +In this extended notion of vertical enablement (to cover the 3GPP management service exposure), the vertical/ slice customer needs to be able to 1) discover the relevant Network Slice Instances and the respective capabilities such as coverage offered, RAT/ frequencies, to 2) discover the management services (based on TS 28.533 [6]) which can be exposed as part of the offered slices, and 3) register to the 3GPP management domain via the vertical enabler layer for consuming the management services. + +This study needs to investigate: + +- Whether and how SEAL needs to be enhanced to support the discovery of the offered slices and the offered management services related to these slices, to the vertical/ASP; +- Whether and how SEAL needs to be enhanced to support the registration of the vertical applications to the 3GPP management domain. + +## 5.4 Key issue 4: Network slice fault management capability + +As the requirement captured in TS 22.261 [7], *based on operator policy, the 5GS shall provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party according to operator policy.* + +In addition, the descriptions of network diagnostics are captured in clause F.2, TS 22.261 [7] as following: + +*Network diagnostics helps with scanning, diagnosing and identifying problems within a network. Diagnostics includes gathering data and continuously providing sufficient performance parameters that characterize the quality of the network connection. This includes data of the physical connection as well as of logical links and sub-networks. Exposure of relevant (and possibly aggregated) performance parameters ensures a quick reaction in case of failure as well as identifying network connectivity, performance and other related problems.* + +*Network diagnostic information needs to be generated automatically and, in case of a hosted or virtual network deployment, be made available to the tenant of the network via a suitable API.* + +The alarm data can be used to help the third-party to diagnose the fault problem of the services, locate the fault causes, and to be aware of the potential fault. In TS 28.545 [10], the fault supervision management services are standardized by which the alarm of the network slice instance from network resource aspects can be subscribed and reported. This alarm information together with the application function's fault report and communication service related knowledge can be + +utilized by the SEAL/NSCE to diagnose and locate the cause of the service performance deterioration and the fault of the communication services, and then exposed the fault report to the third-party. For example, if the status of the required communication is not correct, the SEAL/NSCE derives this alarm information from application functions. In this case, it is the SEAL/NSCE's responsibility to detect whether this fault is caused by the 5GS network or not and exposed the fault report to the third-party. If it is, then the SEAL/NSCE may inform the management functions the location of the fault and ask for the maintenance of the managed functions to clear the fault. + +In addition, the two business relationships of network slice as a service and network slice as NOP internals may considered separately for the capabilities exposed in each scenarios. The coordination with SA5 is needed to fill the gap between the communication services (from the verticals' point of view) and the 5G network. + +Open issues: + +- Whether and how additional APIs dedicated to network slice fault management capability are required? +- How to define the APIs to expose the fault report to verticals client/server +- How to coordinate with fault supervision management services provided by O&M systems defined in SA5 to fill the gap in fault management. + +## 5.5 Key issue 5: Communication service management exposure + +In clause 6.10 of TS 22.261 [7], following requirements are defined: + +*Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to define and reconfigure the properties of the communication services offered to the third-party.* + +*The 5G system shall support the means for disengagement (tear down) of communication services by an authorized third-party* + +In addition, in clause 6.23.1 of TS 22.261 [7], it defines that QoS monitoring can be used for assessing and assuring the dependability of the communication services. + +In SA5 TS 28.535 [11], management services to assure the communication service as per agreement (for example a SLS) with a communication service (only network slice as a service scenario) consumer (e.g. enterprise) have been defined. For other scenarios, the communication services from the verticals aspects required by SA1 (e.g., vertical automation communication services, URLLC services) are not discussed in SA5 + +From the vertical industry perspective, they may be more concerned about how to operate the communication services provided by 5GS to meet the business requirements on application level. Take V2X service as an example, there is a specific service of cooperative driving for vehicle platooning information exchange, and the vertical has some requirements on this service, including end-to-end latency between two UEs. Therefore, the service enable layer needs to provide such capabilities for vertical industries, including lifecycle management and quality assurance of communication services from the verticals' perspective. For example, with the QoE/QoS data of communication services collected from vertical application layer, SA6 may need to provide some value-added communication services management and/or assurance services. + +It is not clear how to expose the communication service management service from application perspective with providing additional value on top of existing SA5 solution. + +Hence, it is required to study the following issues: + +- What kinds of service APIs are required to be supported for application layer exposure of communication services life cycle management? +- What kinds of additional service APIs are required to be supported for application layer exposure of communication services SLA assurance? +- How to support above capabilities in the enable layer? +- How to coordinate with SA5 functionalities to fill the gap between the communication services (from the verticals' point of view) and the 5G network. + +## 5.6 Key issue 6: Application layer QoS verification capability enablement + +In clause 6.23 of TS 22.261 [7], it is defined the requirements about QoS monitoring that 5G system shall be able to assessing and assuring the dependability of the communication services. + +In clause F.1 of TS 22.261 [7], it is discussed how QoS monitoring information can be used for assurance purposes. In step "Customer rating of QoS", it mentions that the customer can compare the QoS achieved by the provider with the QoS requirements and its own experience of the QoS. + +In clause SA5 TS 28.552 [12], it defined QoS measurements reports with different Filters from perspective of OAM, e.g. 5QI, QIC, S-NSSAI, PLMN. + +In some cases, the verticals and the service provider reach an agreement on the SLA, however with this SLA requirement, the VAL client may also suffer unsatisfied experience. Hence, it could be possible to provide Vertical application layer the capability of comparing the QoS achievement status together with the OAM QoS data versus real customer QoS data (e.g., MOS) collected from VAL client to check whether the existing QoS data is able to satisfy the VAL client's. + +It is not clear how to expose the QoS verification capabilities on top of existing SA5 solution. + +Hence, it is required to study the following issues: + +- What kinds of additional service APIs are required to be supported for application layer enablement of QoS verification? +- What kinds of additional service APIs are required to obtain the real vertical QoS to support the QoS verification? +- How to support above capabilities in the enable layer? + +## 5.7 Key issue 7: Network slice related performance and analytics exposure + +As specified in clause 6.10 of 3GPP TS 22.261 [7], 5G network is requested to support a 3rd party to get the network status information of a private slice dedicated for the 3rd party. The 5G network collects various kinds of data, such as performance measurements in TS 28.552 [12] and analytics data as specified in 3GPP TS 28.104 [15] and the analytics data from NWDAF and NSACF exposed by NEF. However, to get the information efficiently, the verticals are supposed to know, which entity to interact with to get the desired information, how to extract useful information from data which is collected using different statistical methods from different entities, which is challenging for some verticals. The network slice capability exposure enabler layer can aggregate and process the data from different source, making the network information exposure more orderly and easier to read. For example, for the slice related performance and analytics come from multiple sources, the enabler layer could help to organize and aggregate the information. For some applications utilizing multiple S-NSSAI, the enabler layer could help to organize and aggregate the information so that it is exposed and displayed based on the application level rather than slices level. + +Hence, it is required to study the following: + +- Whether and how information about available (SA2 and SA5) slice performance and analytics should be exposed to a third party with added value? +- Whether and how available slice performance and analytics related information could be aggregated or processed to support an efficient information exposure? +- Whether and how additional service APIs are required to be supported at SEAL for the network slice measurements and analytics exposure? +- Whether and how CAPIF can be leveraged for additional service APIs? + +## 5.8 Key issue 8: Support for requirements translation + +Requirements for network slice from different verticals may vary from one to another, in terms of performance and capability requirements. For example, for the performance related requirements, the live video streaming cares more on bandwidth while V2X cares more on latency and jitters. For the capabilities related requirements, V2X may requests the positioning while future factory may request the self-control and management. To satisfy the requirements, vertical has to interact with several 5GS entities and understand the specific network parameters, such as the attributes in the service profile as defined in TS 28.541 [14]. Slice enabler layer could act as a mediator between the vertical customer and the 5GS to decompose and translate the requirements. + +Besides, the verticals are more focused on the KQI or QoE of the applications and services. For example, in a scenario of future factory, the robots are used to enable the intelligent delivering, the third-parties have a requirement on the application latency between the robots and the robots control system, the slice enabler may decompose this application latency requirement to 5GS network latency requirement (e.g., the network latency requirements specified in TS 28.541[14] as *packet transmission latency (millisecond) through the RAN, CN, and TN part of 5G network or the UL/DL packet delay measurement between UE and PSA UPF for a QoS Flow* defined in TS 23.501[3]) and forward it to the 5GS systems. Another example is that to support the service of the imaging for professional applications as defined in TS 22.261[7], the imaging system latency of the application as defined in TS 22.263[x] is required which may not only depends on the 5GS network transmission latency but also will be influenced by the network throughput and network bandwidth. The NSCE are responsible for the translation from the vertical's KQI/QoE requirements to 5GS network requirements based on the knowledge of the industry profiles and 5G network (the definition of the KQI/OoE is service and application specific and is out the scope of this study). + +However, to cope with the various requirements, it is needed to specify the operations and procedure on how to translate them more efficiently, such as in the unified manner with unified format/model/template. In such way, the slice enabler layer is capable of translating requirements from the vertical, to service consumption or service API invocation and configurations to the respective 5GS domains. The service could be provided from control plane, management plane and SA6 slice enabler layer itself, or the combinations of services above. + +There are two main aspects in requirements translation: 1) one is how the vertical requirements could be collected, whether and how the template is needed? 2) The other is how to transfer the requirements into actions, whether and how API translation is needed? + +This key issue aims to discuss how to configure and translate the requirements to service consumption and configuration in a way that the slice capability exposure is 1) agnostic to the underlying telecom infrastructure, 2) hides the complexity of telecom infrastructure, 3) doesn't impact/restrict the level of exposure to the vertical and 4) that is resilient to dynamic changes that may happen due to application portability or telco-provided API status changes. + +Therefore, the open issues include: + +- Whether and how the vertical requirements could be collected at the slice enabler to allow the translation to network service consumption and configuration, +- Whether and how API translation is needed to support the requirements translation. + +## 5.9 Key issue 9: Support for trust enablement + +A vertical application may use the slice enabler services (which can be seen as a trusted 3rd party to the MNO) to request management services as well as control plane services for a new slice on demand, based on an agreement between the vertical and the network slice provider. + +However, the creation of a new slice will require a form of trust between the vertical/end application and the 5GS (management and control plane) for authorizing/authenticating the application request and enabling the vertical app to consume management / control services related to the requested slice. + +The vertical application may not be trusted by the OAM or the 5GC, and is therefore not able to access management and control services. Also, there can be two way of accessing these services after authorization, via direct exposure or indirectly via the enabler server. + +So, the key issue will study: + +- How to enable the authorization/authentication of the vertical application to consume telco-provided services (management and control plane), based on the vertical applications request. + +- How to enable the authorization/authentication of the vertical application to consume telco-provided services (management and control plane) indirectly via the slice enabler layer, based on the vertical applications request. + +## 5.10 Key Issue 10: Support for managing trusted third-party owned application(s) + +As per 3GPP TS 22.261 [7], it is possible for trusted third-party to use a dedicated network slice for diverse use cases. Further, it provides following requirement to manage applications: + +*"Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to manage this trusted third-party owned application(s) in the operator's Service Hosting Environment."* + +It is also possible for the third-party to offer its consumers different contract qualities level (e.g. gold, silver and bronze). In clause 5.7.1 of 3GPP TR 22.835 [9], following use case has been specified: + +*"For gaming or online video applications, the end users, who have subscription with MNOs who may provide multiple network slices to different users or services, may still have different priority or membership e.g. VIP maintained by 3rd party Service Provider (SP). And depending on the priority or membership information from 3rd party SP perspective, based on the agreement between SP and MNO, the UE have different priority for the available network slices."* + +In clause 4.2.11.2 of 3GPP TS 23.502 [4] specifies following: + +*"When for all the Requested S-NSSAI(s) provided in step 2 the NSACF returned the maximum number of UEs per network slice has been reached and if one or more subscribed S-NSSAIs are marked as default in the subscription data and not subject to Network Slice Admission Control, the AMF can decide to include these Default Subscribed S-NSSAIs in the Allowed NSSAI. Otherwise, the AMF rejects the UE request for registration. In the Registration Reject message the AMF includes the rejected S-NSSAI(s) in the rejected NSSAI parameter, and for each rejected S-NSSAI the AMF includes a reject cause to indicate that the maximum number of UEs per network slice has been reached and optionally a back-off timer."* + +Upon reaching maximum UEs slice quota, the 5GC may reject the registration request on the S-NSSAI from the gold quality level customer which may not be desirable by the trusted third party. This happens since 5GC is not aware of the relevant application information e.g. contract qualities level of the UE making the registration request. + +The third party application needs to provide high priority to the higher level of contract qualities and so it needs to manage such connections. + +It is also specified in 3GPP TS 22.261 [7] that the 5G system shall support a mechanism to optimize resources of network slices (e.g., due to operator deploying different frequency to offer different network slices) based on network slice usage patterns and policy (e.g., application preference) of a UE or group of UEs. + +In particular, this KI will address: + +- Whether and how the AF can provide application policy information to the operator's Service Hosting Environment to enable automatic management of application resources? +- What application policy information needs to be specified by the trusted third-party AF that can be automatically evaluated by the operator's Service Hosting Environment? +- Whether and how the AF can manage use of the application resources in the operator's Service Hosting Environment on a per user characteristic? + +## 5.11 Key issue 11: Slice requirement alignment + +As described in clause 6.1.2.2, TS 22.261[7], *the 5G system shall allow the operator to create, modify, and delete a network slice*, verticals have strong desires for the slice/service self-management. Initially, they may translate the communication service parameters to slice parameters (*serviceProfile* provided to OAM as defined SA5) and order a slice with certain slice requirements parameters and their values. + +The verticals will put their best effort into slice requirements translation. However, they are not able to guarantee that all the potential factors will be considered to generate the optimal slice requirements parameters on the first try. After the service is executed on the required slice, the slice may not fully match the service real-time running conditions, for + +example, maybe only 60% of the slice resource is used to support the service, and rest of the slice resource is always idle, or the slice resource is insufficient due to under-provisioning. Or in some cases, there may be some unforeseen exceptions (e.g., unexpected traffic changes) and the current configured slice requirements parameters are not able to fulfil the requirements, for example, more resources are required to address the exceptions. + +In order to achieve the maximum return of investment and ensure the slice/service self-management, the verticals expect a more optimal service profile which contains the exact value of those slice requirements parameters to support to the executing services' demands, i.e., by monitoring the network performance statistics to align the slice requirements between verticals and network providers. Furthermore, the action of alignment is not triggered by a single event but considers the statistics of the network performance during a certain time period. From the management perspective, third-party is able to modify the slice requirements (*serviceProfile* defined in TS 28.541[14]) by perform the operation of *modifyMOIAtributes* listed in table 6.1-1 in TS 28.531[5] to support the slice requirements alignment. + +This key issue is to study how to enable better alignment between the vertical needs and the slice requirements parameters. + +NOTE: All the potential changes to the slice are based on existing SA2 and SA5 service/capability. + +Open issues: + +- Whether and How the SEAL network slice capability management service supports better alignment between vertical needs and slice requirements parameters for initial service requirements and ongoing service conditions? +- How does the SEAL network slice capability management service determine and indicate that VAL server policy (e.g., requirements provided when adding or changing slices) requests or actions result in suggested changes to the NSCE service provider policy (e.g., allowed NS profile operations or parameter ranges) or to VAL policies? + +## 5.12 Key issue 12: Network slice capability exposure in the edge data network + +The network slice deployed in the core network has a certain distance from the customer, so the delay will be affected to a certain extent and cannot meet the operation requirements of low latency equipment. Moreover, a variety of service data need to be processed in the core network, the scale of data traffic is large, the backhaul network needs to bear a large load and consume more bandwidth. For example, the differential protection service has strict requirements for latency in power industry. + +In order to meet the personalized services requirements of vertical industries, network slices are deployed by using the computing, storage and communication capabilities of the edge data network, so as to realize the localized processing of the service, reduce the service transmission latency and enhance the service performance. + +How to expose the network slice capability deployed in the edge data network to the vertical industry or the third parties is worthy of our study. + +Open issues: + +- How could the NSCE server deployed inside the EDN interact with the NSCE server outside the EDN? Whether and how could the NSCE server interact with other NSCE serve? +- Whether and how could the NSCE server inside the EDN manage the network slice that has resource outside the EDN? +- Whether and how does SEAL need to be enhanced to support NSCE client to interact with NSCE server in the EDN and NSCE server outside the EDN? + +## 5.13 Key issue 13: Delivery of the existing Network Slice information to the trusted third-party + +There are many requirements on Network Slice Exposure specified in clause 6.10 of 3GPP TS 22.261 [7]. + +*Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party.* + +*Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party.* + +*Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party.* + +*Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a UE to a network slice used for the third-party.* + +*Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a service to a network slice used for the third-party.* + +*Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to assign a UE to a network slice used for the third-party, to move a UE from one network slice used for the third-party to another network slice used for the third-party, and to remove a UE from a network slice used for the third-party based on subscription, UE capabilities, and services provided by the network slice.* + +In order to satisfy the above requirements, the third party should know the Network Slice existence in prior to the proper operation related to the Network Slice. + +The 3rd party service providers may know the existence of Network Slice through a way of delivery from the NSCE as an entity of NSP, which manages information of Network Slice for the 3rd party service providers. The concept of Network slice delivery is described in TS 28.530 clause 4.1.8. + +Which information should be contained and delivered is another important point for delivery of the existing Network Slice. When 3rd party service providers activate the existing Network slice, 3rd party service providers should analyze the specific information of Network Slice such as set of service, capability, QoE, bandwidth and so on in order to figure out to meet their service requirements. What kind of information is necessary to 3rd party service providers may vary according to the services of the 3rd party service providers. With the regards, NSCE servers collect and manage information on Network Slice which 5GS may provide. It may be enough to indicate the standardized NEST (e.g, MBB, URLLC, massive IOT, etc.). Security aspects have to be considered. If there is a need for resource reservation per customer, then a dedicated slice is needed. + +Open issues: + +- When does the Network Slice delivery occur? +- Which information of Network Slice does need to be contained when delivered? Or is it enough the delivery indicates the standardized NEST such MBB, URLLC, massive IOT? +- Whether and how management domain capabilities (e.g. MnS) corresponding to the network slice need to be delivered via the NSCE server? +- How the deployment of NSCE server (e.g. at NSP or NSC side) affects the level of slice information to be delivered? + +## 5.14 Key issue 14: Network Slice creation to the third-party and UE + +The requirements specified in clause 6.10 of 3GPP TS 22.261 [7] says, + +*Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party.* + +This requirement interprets that the third-party can allocate the Network Slice for its service with suitable APIs provided by 5G Network. It can be implemented based on whether an appropriate Network Slice for the third-party service does exist or not. In case the appropriate Network Slice exists, the third-party request to use the Network Slice for the service, and the corresponding entities modifies the info of the Network Slice properly. In case the appropriate Network Slice does not exist, then the third-party request to create the new Network slice. This procedure should be + +handled with interaction between VAL server, NSCE and 5G network. Security aspects have to be considered. If there is a need for resource reservation per customer, then dedicated slice is needed. + +After the Network Slice allocation is requested, UE should be notified that the Network Slice for the third-party service is used. It is obvious that the UE utilizes the info of Network Slice in URSP or local configuration to transport the data of the third-party service. With the regard, without notification to the UE, the Network Slice will not be used for the service. When notified, SA6 needs to take it consideration whether the notification is transported over NSCE layer. If transported over NSCE layer, then it should be considered whether UE applies the new allocated Network Slice into URSP. + +NOTE 1: The application enablement layer will not circumvent nor try to replace solutions required at the network layer defined by SA2 nor the management layer defined by SA5. + +# Open Issues + +- What kind of information should be required for creating a new Network Slice for the third-party service (between NSP and NSC)? Any minimum set of information should be considered such as Service/Slice Type, Device Type or QoS Index? +- Whether and how is the notification transported over NSCE layer? +- Whether does UE apply the new allocated Network Slice into URSP when transported over NSCE layer? + +# 6 Solutions + +## 6.0 Mapping of Solutions to Key Issues + +Table 6.0-1: Mapping of Solutions to Key Issues + +| | Ke
y
iss
ue
1 | Ke
y
iss
ue
2 | Ke
y
iss
ue
3 | Ke
y
iss
ue
4 | Ke
y
iss
ue
5 | Ke
y
iss
ue
6 | Ke
y
iss
ue
7 | Ke
y
iss
ue
8 | Ke
y
iss
ue
9 | Ke
y
iss
ue
10 | Ke
y
iss
ue
11 | Ke
y
iss
ue
12 | Ke
y
iss
ue
13 | Ke
y
iss
ue
14 | +|------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------|---------------------------|----------------------------|----------------------------|----------------------------|----------------------------|----------------------------| +| Solution 1 | X | X | | | | | | | | | | | | | +| Solution 2 | X | | | X | | | | | | | | | | | +| Solution 3 | | | | | | | | X | | | | | | | +| Solution 4 | X | | | | | X | | | | | | | | | +| Solution 5 | X | | | | | | X | | | | | | | | +| Solution 6 | | | | | | | | | X | | | | | | +| Solution 7 | | | X | | | | | | | | | | | | + +| | | | | | | | | | | | | | | | +|-------------|---|--|---|--|---|--|--|--|--|---|---|---|---|---| +| Solution 8 | | | X | | | | | | | | | | X | | +| Solution 9 | | | | | | | | | | X | | | | | +| Solution 10 | | | | | | | | | | X | | | | | +| Solution 11 | X | | | | X | | | | | | | | | | +| Solution 12 | X | | | | | | | | | | | | | | +| Solution 13 | | | | | | | | | | | | | | X | +| Solution 14 | X | | | | | | | | | | | X | | | +| Solution 15 | X | | | | | | | | | | | | | | +| Solution 16 | X | | | | | | | | | | | | | | +| Solution 17 | X | | | | | | | | | | X | | | | +| Solution 18 | | | | | | | | | | | | | X | | +| Solution 19 | | | | | | | | | | | X | | | | +| Solution 20 | | | | | | | | | | X | | | | | +| Solution 21 | | | | | | | | | | | | X | | | +| ... | | | | | | | | | | | | | | | + +## 6.1 Solution 1: Automatic application layer network slice management + +### 6.1.1 Solution description + +#### 6.1.1.1 General + +This solution aims to address the issues identified in Key Issue 2. + +This solution provides a procedure for automatic application layer network slice management performed by the network slice capability enablement server based on network slice status collected from 5GS and QoE collected from application layer. + +When network slice capability enablement server receives a request for automatic application layer network slice management from VAL server, the network slice capability enablement server performs the service operations including detecting and subscribing the event which may trigger the automatic network slice lifecycle management, making the network slice lifecycle management recommendation/decision, triggering the network slice management operations, notifying the consumer about the network slice information. + +#### 6.1.1.2 Automatic application layer network slice lifecycle management + +Figure 6.1.1.2-1 illustrates an automatic application layer network slice lifecycle management solution based on network slice related data and QoE collected from application layer. + +Pre-conditions: + +1. The VAL client has requested a network slice provisioning; +2. The VAL server has subscribed to the network slice capability enablement server for automatic network slice management; +3. The network slice enabler layer is registered/capable for interacting with 5GS such as triggering network slice LCM operations, and has collected current network slice capabilities. + +![Sequence diagram illustrating the automatic application layer network slice lifecycle management process between VAL server, network slice capability enablement server, and 5GS.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCES as network slice capability enablement server + participant 5GS + + Note right of NSCES: 2. Authentication and authorization and Network slice lifecycle management operation determination + Note right of NSCES: 3. Trigger Network slice lifecycle management operation(s) + Note right of NSCES: 5. Trigger for providing the network slice status or QoE + + VAL server->>NSCES: 1. Automatic application layer network slice lifecycle management request + NSCES-->>5GS: 3. Trigger Network slice lifecycle management operation(s) + 5GS-->>NSCES: 5a. network slice status information + NSCES-->>VAL server: 4. Automatic application layer network slice lifecycle management response + VAL server-->>NSCES: 5b. application layer QoE information + NSCES-->>VAL server: 7. Network slice lifecycle management suggestion request + VAL server-->>NSCES: 8. Network slice lifecycle management suggestion response + NSCES-->>5GS: 9. Trigger Network slice lifecycle management operation(s) + NSCES-->>VAL server: 10. Automatic application layer network slice lifecycle management response + +``` + +Sequence diagram illustrating the automatic application layer network slice lifecycle management process between VAL server, network slice capability enablement server, and 5GS. + +**Figure 6.1.1.2-1: Automatic application layer network slice lifecycle management** + +1. The vertical server sends a request for automatic application layer network slice lifecycle management (auto-NS-LCM), with network slice requirements (e.g. delay, throughput, load, the maximum number of users supported, etc.). The request can indicate the level of auto-NS-LCM that is required, such as whether to notify the VAL server/consumer before performing the auto-NS-LCM. The request may also indicate the trigger conditions, such as by providing the monitored parameters and the corresponding thresholds. + +2. After receiving the request, the network slice capability enablement server checks that the user is authenticated and authorized to perform the corresponding auto-NS-LCM operations, and filters the unauthorized requests, if any. +3. If authenticated and authorized, the network slice capability enablement server, acting as the network slice LCM service consumer, triggers the AllocateNsi request (see TS 28.531 clause 6.5.1 [5]) towards the respective management service provider, based on the network slice capabilities and network slice requirements. +4. The network slice capability enablement server sends the auto-NS-LCM response to the VAL server with the result(s) of the network slice LCM operation(s). +5. According to network slice requirements, network slice capability enablement server triggers the provision of network slice status and QoE metrics. + - 5a. The network slice status could be collected through subscribing or requesting to 5GS. For example, to monitor the slice load, it could subscribe to/request the relevant service(s), such as AnalyticsExposure defined in TS 23.502 [4] clause 5.2.6.16, provisioning data report exposure for NSI in clause 5 of TS 28.532 [8]. If the trigger conditions are not indicated in the subscription, the network slice capability enablement server may help to configure an appropriate trigger condition, such as report period or thresholds. + - 5b. Also, the network slice capability enablement server could get the information of QoE metrics from the application layer domain. +6. Once the trigger condition or a combination of trigger conditions are met, based on requirements and network slice capabilities with updated information in Step 5, such as change in QoE, change in network slice status etc., the network slice capability enablement server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s), such as modifyNsi/AllocateNsi/DeallocateNsi request as specified in TS 28.531 [5]. +7. Optionally, if it is indicated in the request to notify the VAL server/consumer before performing the auto-NS-LCM, the network slice capability enablement server sends the network slice LCM recommendation(s) with network slice status to VAL server, to see whether takes the recommendation(s) or not. +8. Optionally, sending the response indicating the decision made by VAL server to network slice capability enablement server. +9. Based on decision made by VAL server or network slice capability enablement server, the network slice capability enablement server performs the corresponding operation(s). +10. According to the corresponding operation(s) result, the network slice capability enablement server sends the response to the VAL server. + +### 6.1.2 Solution evaluation + +The proposed solution addresses Key Issue #2. SA5 provides the network slice lifecycle management, while this solution provides a procedure for automatic application layer network slice management performed by the network slice capability enablement server based on network slice status collected from 5GS and QoE collected from application layer. With automatic application layer network slice management, the consumer's requirement could be better met without having to interact with 5GS frequently. This solution does not introduce impact on 5GS architecture. It will possible need enhancement of SA6 SEAL architecture enhancement to support the interaction with OAM system, but the interface for interaction with the OAM system is still being studied in SA5. + +## 6.2 Solution 2: Network slice fault management capability + +### 6.2.1 Solution description + +#### 6.2.1.1 General + +This solution addresses the key issue 4 of network slice fault management described in clause 5.4. + +This solution provides a possible procedure to illustrate the network slice fault management capability exposed by NSCE server. + +To enable the VAL server to monitor the problems of a network, the NSCE layer should help the VAL server to scanning, diagnosing and identifying problems within a network. The performance data and alarm data from multiple sources is helpful to characterize the quality of the network connection. + +#### 6.2.1.2 Network slice fault management capability exposure + +Figure 6.2.1.2-1 illustrates the network slice fault management process to address the key issue 4 of network slice fault management described in clause 5.4. + +Pre-conditions: + +1. The VAL client has subscribed to the network slice fault management capability. +2. The network slice enabler layer is capable to interact with NEF and OAM system. +3. The VAL client has checked the status of application layer. + +![Sequence diagram illustrating the Network slice fault management process. The participants are VAL Server, NSCE Server, NSCE Client, OAM, and 5GC. The process starts with the VAL Server sending a 'Fault diagnosis request' to the NSCE Server. The NSCE Server then performs two internal steps: 'Retrieve network slice specific performance data and analytics data from 5GC and OAM system' (indicated by a dashed box) and 'Retrieve network slice related fault data from OAM system'. Next, the NSCE Server sends a 'Network slice related fault data request' to the NSCE Client, which responds with a 'Network Slice related fault data response'. The NSCE Server then performs 'Network and Service diagnosis' and sends a 'Fault diagnosis response' back to the VAL Server. Finally, the NSCE Server sends a 'Fault diagnosis report' to the OAM system.](15e4a144a88176b71ea3eff2722253b0_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE Server + participant NSCE Client + participant OAM + participant 5GC + + Note right of NSCE Server: 2.Retrieve network slice specific performance data and analytics data from 5GC and OAM system + Note right of NSCE Server: 3.Retrieve network slice related fault data from OAM system + Note right of NSCE Server: 6.Network and Service diagnosis + + VAL Server->>NSCE Server: 1.Fault diagnosis request + NSCE Server-->>NSCE Client: 4.Network slice related fault data request + NSCE Client-->>NSCE Server: 5. Network Slice related fault data response + NSCE Server-->>VAL Server: 7.Fault diagnosis response + NSCE Server-->>OAM: 8.Fault diagnosis report + +``` + +Sequence diagram illustrating the Network slice fault management process. The participants are VAL Server, NSCE Server, NSCE Client, OAM, and 5GC. The process starts with the VAL Server sending a 'Fault diagnosis request' to the NSCE Server. The NSCE Server then performs two internal steps: 'Retrieve network slice specific performance data and analytics data from 5GC and OAM system' (indicated by a dashed box) and 'Retrieve network slice related fault data from OAM system'. Next, the NSCE Server sends a 'Network slice related fault data request' to the NSCE Client, which responds with a 'Network Slice related fault data response'. The NSCE Server then performs 'Network and Service diagnosis' and sends a 'Fault diagnosis response' back to the VAL Server. Finally, the NSCE Server sends a 'Fault diagnosis report' to the OAM system. + +**Figure 6.2.1.2-1: Network slice fault management process** + +1. The VAL server sends a request to NSCE server to request for the fault diagnosis of the applications and networks when it detected a fault in the application layer, the services and the network slices. This request may be triggered by the errors of the applications detected by the VAL server itself, or the VAL server may periodically collect the fault diagnostic report subscribing to the network slice fault management capability. The fault information of applications may be included in this request. For example, the Service Availability Failure Events e.g, described as Fallback events carried out by the Dual SIM cellular device. +2. On receiving the request from VAL server, NSCE server retrieves the performance data of network slice from 5GS. For OAM system, the APIs defined in clause 11.3, TS 28.532[8] is utilized. For CN functions, the APIs of Nnwdaf\_AnalyticsInfo service defined in clause 7.3, TS 23.288[17] can be utilized. + +The analytics data defined in clause 6.3 to clause 6.14, TS 23.288[17], network slice instance related performance data defined in clause 5, TS 28.552[12] and network analytics data in clause 8.3 and clause 8.4 TS 28.104[15] exposed by OAM system may be acquired. + +3. NSCE server retrieves the alarms of network slice instances from OAM system via the procedures defined in clause 6.1, TS 28.545[10], and the alarms are defined in clause 4.1.1.1, TS 32.111-1 [16], e.g., the fault of communication, environmental, equipment, processing error, QoS for device/resource/file/functionality/smallest. +4. NSCE server may request the alarm information (e.g., the 5GS network is not work or the required performance is under the threshold which leads the service's problem) collected by NSCE client if possible. The information collected by the NSCE client depends on the third-parties' requirements and implementation. +5. NSCE client report the requested fault information to NSCE server. +6. NSCE server correlates the applications, services and the network resources of the specific network slice instances which supports the applications and services with the S-NSSAI, NSI ID (*nSInstanceId* defined in TS 28.541[14]), Application Identifier (defined in 23.501[3]), and then diagnoses the causes of the fault of the applications or services by analysing the fault information from different sources. For example, the RAN function of the slice instance which is utilized to support the service of the smart grid application, for a certain time duration, the smart grid suffered the bad experience caused by Service Availability Failure Events, and in the RAN function is detected continuously to report an alarm of environmental fault in the same time duration, then the environment fault may be the root cause of the Service Availability Failure and should be prioritized to be solved. The fault may be identified with "critical", "major", "minor", "ignore" to show its prioritization. +7. NSCE server response to VAL server with the reports of fault diagnostic result to indicate the causes of the failures of the applications or services. If there is no problem within the 5GS network, the VAL server may be requested to check the application layer itself again. +8. If the NSCE server detects that the application/service error is caused by the 5GS, the VAL server may send the fault diagnosis report to OAM system to indicate the server fault which causes the application/service failure by utilizing the NSCE-OAM interface. + +NOTE: The APIs utilized to send the fault diagnosis report to OAM will re-utilize the fault management services in TS 28.532[8] exposed by EGMF as defined in TS 28.533[6]. + +### 6.2.2 Solution evaluation + +The solution addresses the key issue #4 and this solution will have interaction with both the 5GC and OAM to collect the alarm information and network analytics data and also could acquire application fault data from VAL server or VAL client. For the NSCE server and NSCE client, it will possible need enhancement of the existed Rel-17 architecture to perform network and service level diagnosis. Also, fault diagnosis service in service level should also need to be added in the existed network architecture. + +## 6.3 Solution 3: Slice API configuration and translation + +### 6.3.1 Solution description + +#### 6.3.1.1 General + +This solution aims to address the issues identified in Key Issue 8. + +This contribution provides a solution for the API configuration and translation and proposes the translation of the service API as invoked by the end applications to slice APIs based on the API configuration and application to slice mapping. Slice APIs can be defined as customized/tailored sets of service APIs (which can be either NEF northbound APIs or OAM provided APIs or enabler layer/SEAL provided APIs) and can be mapped to particular slice instances. The slice APIs can be a bundled or combined API comprising of different types of APIs, which will be used to expose the telco (5GS/SEAL)-provided services as needed by the applications of the slice customer. Each slice API may be configured per network slice instance. + +This solution provides a support functionality to the vertical application specific layer and configures the exposure of APIs in a slice-tailored manner. It is assumed that the VAL server is not initially aware of the all the API exposure capabilities and information which will be needed for the given slice based on the SLA, and NSCE plays a vital role in configuring and translating the slice API based on the per slice requirements to service APIs. + +This solution has two procedures: + +- a procedure on the slice API configuration +- a procedure on the slice API translation + +#### 6.3.1.2 slice API configuration + +In this procedure, the VAL server initially provides an application requirement to enabler server including the service KPIs and the subscribed/preferred slices. Then, the slice enabler configures the mapping of the VAL application to a slice API which is a combination/bundling of northbound APIs (from both management and control plane). In particular, a slice API (or SDK) consists of telco-provided/platform dependent service APIs (e.g. NEF, OAM, SEAL, etc), and provides an abstraction/simplification on top of them. The procedure also covers the scenario where a trigger event occurs (e.g. QoS degradation, slice load) and the mapping configuration or the slice API configuration needs to change. In this scenario, the slice enabler updates the configuration of the API and provides a notification to the VAL server. + +Figure 6.3.1.2-1 illustrates a solution for the slice API configuration. + +Pre-conditions: + +1. The VAL server has registered to receive network slice capability enablement services + +![Sequence diagram for Slice API configuration showing interactions between VAL Server, Network Slice Capability Exposure Server, and 5GS/SEAL service/API providers.](e9b43ac020435f8121e8592f31afdc52_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCES as Network Slice Capability Exposure Server + participant 5GS/SEAL service/API providers + + Note right of NSCES: 2. slice API configuration & mapping to VAL application + Note right of 5GS/SEAL service/API providers: 3. subscription / registration to 5GS/SEAL services + + VAL Server->>NSCES: 1. VAL application requirement request + NSCES-->>VAL Server: 4. VAL application requirement response + NSCES-->>VAL Server: 5. slice API information + 5GS/SEAL service/API providers->>NSCES: 6. Trigger Event + Note right of NSCES: 7. Evaluation and slice API configuration update + Note right of 5GS/SEAL service/API providers: 8. subscription / registration update to 5GS services + NSCES-->>VAL Server: 9. event notification + +``` + +Sequence diagram for Slice API configuration showing interactions between VAL Server, Network Slice Capability Exposure Server, and 5GS/SEAL service/API providers. + +Figure 6.3.1.2-1: Slice API configuration + +1. The VAL server sends a VAL application requirement request to the network slice capability enablement server. This request provides the service requirements / KPIs, the capability exposure requirements and a preferred/subscribed slice identification (e.g. S-NSSAI or ENSI) +2. The network slice capability enablement server maps the VAL application requirement to a slice API which includes a list of APIs which are needed to be consumed as part of this service capability exposure (such APIs can be NEF APIs as specified in TS 29.522 clause 5 e.g. related to network monitoring, slice status, analytics exposure, SEAL APIs as specified in TS 23.434, OAM provided APIs). Such mapping can be determined at the network slice capability enablement server based on the VAL application exposure requirements or can be pre-configured per slice instance. The criteria for the mapping are the capability exposure requirement per slice (based on GST parameters, or from service/slice profile] as well as the capability exposure permissions/authorization for the API invoker. + +The network slice capability enablement server may also store the mapping of the slice API to the service API list and per service API information (e.g. data encoding, transport technology, API protocol and versions) + +NOTE: For OAM provided APIs, the consumption of the network slice management service related procedures are specified in TS 28.531[5]. + +3. The network slice capability enablement server subscribes/registers to consume the corresponding APIs from the 5GS (NEF and OAM) and SEAL service producers. For example, network slice capability enablement server may subscribe to consume NEF monitoring events, or SLA monitoring from OAM. +4. The network slice capability enablement server sends a VAL application requirement response to notify on the result of the request and indicate whether configuration of the slice API can be possible or not. +5. The network slice capability enablement server sends the slice API information and optionally the slice to service API mapping to the VAL server. +6. A trigger event is captured by the service/API providers (e.g. control plane, management plane, SEAL) or the VAL server side (application server relocation to different EDN/DN, UE mobility to different EDN, application change of behaviour) or any other API related event captured by the network slice capability enablement server (e.g. failure, unavailability, high load). +7. The network slice capability enablement server processes the trigger event and checks and updates the mapping of service APIs to the slice APIs. The objective is to keep the slice APIs unchanged, so the VAL server is not aware of any change (if not triggered by VAL server). To accomplish this, the service APIs may need to be updated accordingly. For example, if one service API changes (e.g. due to high load, unavailability, ..) the mapping to service APIs should be updated (e.g. if service API is a Location API which is provided by 5GC in the first place, the update would trigger the remapping to a Location API from SEAL LMS) to avoid affecting the slice API. +8. The network slice capability enablement server updates the subscription/registration to the underlying 5GS and SEAL service producers, if an update on the service APIs (e.g. NEF APIs, SEAL APIs, OAM provided APIs) is needed. +9. The network slice capability enablement server optionally notifies the VAL server on the slice/service API related updates. + +#### 6.3.1.3 Slice API translation + +This procedure follows the 6.3.1.2 and aims to describe how the slice API invocation request is translated to service API invocations after the slice API configuration mapping. In this procedure, the network slice capability enablement server initially receives a slice API invocation request from the vertical application based on step 5 of 6.3.1.2. Then, the network slice capability enablement server based on the slice API request fetches the service APIs to be invoked based on the slice API configuration and performs invocation requests to the corresponding service API providers. + +As example, a slice API is requested for an IIOT slice. This may translate to: NSI Monitoring from Management Domain #1, NSSI Monitoring from Management Domain #2, network/QoS monitoring from NEF#1, Location monitoring from SEAL LMS, slice-related analytics from NWDAF (via NEF). Such translation could be based on the slice API configuration mapping of 6.3.1.2. + +Figure 6.3.1.3-1 illustrates a solution for the slice API translation based on the configuration. + +Pre-conditions: + +1. The VAL server has registered to receive network slice capability enablement services. +2. The slice API mapping to the VAL server has been performed based on 6.3.1.2 step 2 and the slice API information is provided to the VAL server based on 6.3.1.2 step 5. + +![Sequence diagram illustrating Slice API translation. The diagram shows three main entities: VAL Server, Network Slice Capability Exposure Server, and Service/Slice API provider. The sequence of interactions is: 1. slice API invocation request from VAL Server to Network Slice Capability Exposure Server; 2. Mapping of slice API to service APIs (based on 6.x.1.2 step 2) within the Network Slice Capability Exposure Server; 3. Trigger invocation requests for all service APIs of slice API within the Network Slice Capability Exposure Server; 4. service API invocation request from Network Slice Capability Exposure Server to Service/Slice API provider; 5. service API authentication within the Service/Slice API provider; 6. service API invocation response from Service/Slice API provider to Network Slice Capability Exposure Server; 7. slice API invocation Response from Network Slice Capability Exposure Server to VAL Server.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant Network Slice Capability Exposure Server + participant Service/Slice API provider + Note right of Network Slice Capability Exposure Server: 2. Mapping of slice API to service APIs (based on 6.x.1.2 step 2) + Note right of Network Slice Capability Exposure Server: 3. Trigger invocation requests for all service APIs of slice API + VAL Server->>Network Slice Capability Exposure Server: 1. slice API invocation request + Network Slice Capability Exposure Server->>Service/Slice API provider: 4. service API invocation request + Note right of Service/Slice API provider: 5. service API authentication + Service/Slice API provider-->>Network Slice Capability Exposure Server: 6. service API invocation response + Network Slice Capability Exposure Server-->>VAL Server: 7. slice API invocation Response + +``` + +Sequence diagram illustrating Slice API translation. The diagram shows three main entities: VAL Server, Network Slice Capability Exposure Server, and Service/Slice API provider. The sequence of interactions is: 1. slice API invocation request from VAL Server to Network Slice Capability Exposure Server; 2. Mapping of slice API to service APIs (based on 6.x.1.2 step 2) within the Network Slice Capability Exposure Server; 3. Trigger invocation requests for all service APIs of slice API within the Network Slice Capability Exposure Server; 4. service API invocation request from Network Slice Capability Exposure Server to Service/Slice API provider; 5. service API authentication within the Service/Slice API provider; 6. service API invocation response from Service/Slice API provider to Network Slice Capability Exposure Server; 7. slice API invocation Response from Network Slice Capability Exposure Server to VAL Server. + +**Figure 6.3.1.3-1: Slice API translation** + +1. The VAL server sends a slice API invocation request to the network slice capability enablement server. This request provides slice API information (name, type, communication methods, protocols,...), based on the received information in step 5 of 6.3.1.2. Service APIs are indicated above can be NEF APIs as specified in TS 29.522, SEAL APIs as specified in TS 23.434, OAM provided APIs) + +NOTE 1: For OAM provided APIs, the consumption of the network slice management service related procedures are specified in TS 28.531[5]. + +2. After receiving the request, the network slice capability enablement server checks that the user is authenticated and authorized to perform the slice API invocation and maps the requested slice API to a service APIs (based on the VAL server ID / slice ID and procedure in clause 6.6.1.2). + +NOTE 2: If CAPIF is used, the network slice capability enablement server acts as AEF, and the authorization is obtained by CCF. + +3. The network slice capability enablement server generates a trigger for service API invocation requests to all the service APIs within the slice API. + +4. The network slice capability enablement server sends a service API invocation request to the producers of the service APIs within the slice API. This may include the originated service API invoker identity information (VAL server) as well as the direct API invoker information, authorization information, service API and slice API identification. + +5. The service API provider authenticates the API invoker and authorizes the request. + +NOTE 3: If CAPIF is used, the requests are sent to the corresponding AEFs of the API provider's domain, and the authorization is obtained by CCF. + +6. The network slice capability enablement server receives the service API invocation response as a result of the service API invocation. + +7. The network slice capability enablement server sends to the VAL server a slice API invocation response as a result of the slice API invocation. + +### 6.3.2 Solution evaluation + +The solution addresses the key issue #8 on requirements translation; and discusses the API translation and configuration aspects. Solution #3 requires interaction with API producers in 3GPP network systems, based on already defined procedures. This includes interaction with 5GC (acting as trusted AF) for subscribing to and invoking NEF services; the interaction with OAM / MnS producers (or EGMF) for consuming OAM services, and the interaction with SEAL for invoking SEAL APIs. + +The solution is feasible and proposes the enhancement NSCE server capabilities to translate / bundle service APIs (of different producers and types) to slice APIs. The definition of the slice APIs and the interaction with the VAL server are expected to be specified during the normative phase. + +## 6.4 Solution 4: QoS verification capability + +### 6.4.1 Solution description + +#### 6.4.1.1 General + +This solution aims to address the issues identified in Key Issue 6. + +This solution provides a procedure to illustrate the QoS verification capability by the network slice capability enablement server. + +To enable the VAL server to verify QoS data of a network, the NSCE layer should help the VAL server to check whether the existing QoS data is able to satisfy the VAL client's requirement. + +#### 6.4.1.2 QoS verification capability + +Figure 6.4.1.2-1 illustrates the QoS verification capability process to address the key issue 6 of Application layer QoS verification capability exposure described in clause 5.6. + +Pre-conditions: + +1. The VAL client has subscribed to the QoS verification capability. +2. The VAL client has subscribed to the capability of Network slice related performance and analytics exposure. +3. The network slice enabler layer is capable to interact with NEF/NWDAF and OAM system. + +![Sequence diagram of the QoS verification process. Lifelines: VAL Server, NSCE Server, NSCE Client, OAM, 5GC. The process involves a request from VAL Server to NSCE Server, followed by data retrieval from 5GC and OAM, then a QoE data request/response between NSCE Server and VAL Server, then a network and service QoE data request/response between NSCE Server and NSCE Client, followed by data verification and analyses by NSCE Server, and finally a QoS verification response from NSCE Server to VAL Server.](e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg) + +``` +sequenceDiagram + participant VAL Server + participant NSCE Server + participant NSCE Client + participant OAM + participant 5GC + + Note right of NSCE Server: 2.Retrieve network slice QoS data from 5GC and OAM system + VAL Server->>NSCE Server: 1.QoS verification request + NSCE Server->>VAL Server: 3. QoE data request + VAL Server->>NSCE Server: 4.QoE data response + NSCE Server->>NSCE Client: 5.Network and service QoE data request + NSCE Client-->>NSCE Server: 6. Network and service QoE data response + Note left of NSCE Server: 7. data verification and analyses + NSCE Server->>VAL Server: 8.QoS verification respond +``` + +Sequence diagram of the QoS verification process. Lifelines: VAL Server, NSCE Server, NSCE Client, OAM, 5GC. The process involves a request from VAL Server to NSCE Server, followed by data retrieval from 5GC and OAM, then a QoE data request/response between NSCE Server and VAL Server, then a network and service QoE data request/response between NSCE Server and NSCE Client, followed by data verification and analyses by NSCE Server, and finally a QoS verification response from NSCE Server to VAL Server. + +Figure 6.4.1.2-1: QoS verification process + +1. The VAL server sends a request to NSCE server to verify the service/application QoS data. + +2. On receiving the request from VAL server, NSCE server retrieves the QoS data of network slice from 5GC and OAM system. For OAM system, the APIs defined in clause 11.3, TS 28.532[15] is utilized, the performance data specified in TS 28.552[12] and analytics data specified in TS 28.104[16] can be collected. For CN functions, the APIs of Nnwdaf\_AnalyticsInfo service defined in clause 7.3, TS 23.288[18] is utilized. The data of QoS information defined in TS 23.501[3]. +3. NSCE server sends a request to application layer to request the QoE data (e.g., MOS). +4. VAL server sends the requested QoE data to NSCE server. +5. NSCE server may send a request to NSCE client to collect the QoE data of network and services if possible. +6. NSCE client report the requested data collected by itself if possible, the information collected by the NSCE client depends on the third-parties' implementations. +7. NSCE server verifies and analyses QoS data of network slice instance, Comparing QoS achieved status together with the OAM QoS data versus real customer QoE data (e.g., MOS) collected from VAL client to check whether the existing QoS data is able to satisfy the VAL client's to generate the QoS verification report as required by VAL server for specific period of time. +8. NSCE server sends the service/application QoS verification response to VAL server. + +### 6.4.2 Solution evaluation + +The proposed solution addresses Key Issue #6, the solution provides a procedure for application layer the capability of QoS verification by the network slice capability enablement server, which has interaction with both the 5GC and OAM to collect the QoS data from N33 and NSCE-OAM interface respectively, acquires network and service QoE data from NSCE client by NSCE-UU interface and obtains application QoE data from VAL server by NSCE-S interface to compare QoE data and QoS data, checking whether the existing QoS data is able to satisfy the real customer QoE data. + +This solution does not introduce impact on 5GS architecture and SEAL architecture, the NSCE server has the capability to translate and compare QoE data and QoS data." + +## 6.5 Solution 5: Network slice related performance and analytics exposure + +### 6.5.1 Solution description + +#### 6.5.1.1 General + +This solution addresses the key issue 7 of performance and analytics exposure described in clause 5.7. + +This solution provides a possible procedure to illustrate the network slice related performance and analytics exposure capability provided by network slice capability enablement server. + +To enable the third-party to adjust the network slice or to configure the information which associates a service/UE to a network slice, the third-party is allowed to monitor the performance data and analytics data of the network slice, service or application. The network slice related performance data may be collected from multiple sources (e.g., OAM system or 5GC functions) to help the NSCE layer to perform data aggregation or analyses to generate the data required by the third-party. The solutions of performance data and analytics data exposed to the third-party needs to be studied. + +#### 6.5.1.2 Network slice related performance and analytics exposure + +Figure 6.5.1.2-1 illustrates the network slice related performance and analytics exposure process to address the key issue 7 of performance and analytics exposure described in clause 5.7. + +Pre-conditions: + +1. The VAL client has subscribed to the capability of Network slice related performance and analytics exposure. +2. The network slice enabler layer is capable to interact with NEF and OAM system. + +![Sequence diagram illustrating the Network slice related performance and analytics exposure process. The diagram shows interactions between VAL Server, NSCE Server, NSCE Client, and 5GS. The process starts with the VAL Server sending a service performance/analytics data request to the NSCE Server. The NSCE Server then requests authorization from the NSCE Client. The NSCE Client then retrieves network slice specific performance data and analytics data from the 5GS and OAM system. The NSCE Client then provides network and service related KQI or performance data to the NSCE Server. The NSCE Server performs data correlation and analyses. Finally, the NSCE Server sends a service performance/analytics data report back to the VAL Server.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE Server + participant NSCE Client + participant 5GS + Note right of NSCE Server: 2.Request authorization + Note right of NSCE Client: 3.Retrieve network slice specific performance data and analytics data from 5GC and OAM system + Note right of NSCE Client: 4.Network and service related KQI or performance data from NSCE Client + Note right of NSCE Server: 5. Data Correlation and analyses + VAL Server->>NSCE Server: 1.Service performance/analytics data request + NSCE Server->>NSCE Client: 2.Request authorization + NSCE Client->>5GS: 3.Retrieve network slice specific performance data and analytics data from 5GC and OAM system + 5GS-->>NSCE Client: 4.Network and service related KQI or performance data from NSCE Client + NSCE Client->>NSCE Server: 5. Data Correlation and analyses + NSCE Server->>VAL Server: 6.Service performance/analytics data report + +``` + +Sequence diagram illustrating the Network slice related performance and analytics exposure process. The diagram shows interactions between VAL Server, NSCE Server, NSCE Client, and 5GS. The process starts with the VAL Server sending a service performance/analytics data request to the NSCE Server. The NSCE Server then requests authorization from the NSCE Client. The NSCE Client then retrieves network slice specific performance data and analytics data from the 5GS and OAM system. The NSCE Client then provides network and service related KQI or performance data to the NSCE Server. The NSCE Server performs data correlation and analyses. Finally, the NSCE Server sends a service performance/analytics data report back to the VAL Server. + +**Figure 6.5.1.2-1: Network slice related performance and analytics exposure process** + +1. The VAL server sends a request to NSCE server to collect the desired service/application specific performance data and analytics data, the detailed content of the reported data depends on the type of the application and services (the KQI and QoE data may be included with in the request). For example, the VAL may request the NSCE server to report the performance and analytics report of the service of the imaging for professional applications. The request may contain the interested geographical area. + +NOTE 1: It is not shown in the figure that VAL client could also trigger step1. It may be triggered by a specific event or request from the VAL client. Besides, the VAL client can trigger this procedure if the performance issue are detected by the VAL client itself. + +NOTE 2: Both periodical or ad-hoc reporting are possible, the VAL layer can request a periodical reporting or a one-off reporting. The result of the reporting can be subscribed by the VAL layer; it can request both or any one of them. + +2. The NSCE server shall check if the VAL server is authorized to get the network slice performance and analytics data. +3. On receiving the request from VAL server, NSCE server retrieves the performance data and analytics data of network slice from 5GS. For OAM system, the APIs defined in clause 11.3, TS 28.532[8] is utilized. For CN functions, the APIs of Nnwdaf\_AnalyticsInfo service defined in clause 7.3, TS 23.288[17] is utilized. + +The performance and analytics data such as the Observed Service experience statistics, Load level information of a Network Slice defined in TS 23.288[18], network slice status defined in TS 23.502[4] clause 5.2.21, and analytics data defined in TS 23.288[17], network slice instance related performance data defined in TS 28.552[12] and network analytics data in TS 28.104[15] exposed by OAM system may be acquired. For example, when the performance and analytics report of the service of the imaging for a professional application is required, the imaging system latency as defined in TS 22.263[18] should be reported and analysed. In this case, the NSCE requests the OAM system to report the one-way/Round-trip packet delay of a specific S-NSSAI between PSA UPF and NG-RAN in clause 5.4, TS 28.552[12] and requests the NWDAF to report the User Data Congestion Analytics report defined in clause 6.8, TS 23.288[17]. + +4. NSCE server retrieves the KQI data of services (e.g., the jitter duration of a video service), the network performance related data and the end users information (e.g., 5G UE's running time) by following the procedures defined in Figure 6.5.1.2-1 and Figure 6.5.1.2-2. + +5. NSCE server correlates and analyses the performance data of network slice instance, the analytics data of group of UEs and the KQI/QoE data to generate the performance data and analytics data report as required by VAL server for specific period of time. + +NOTE 3: How the data analytics correlation happens is out of scope of NSCALE study + +6. NSCE server sends the service/application related performance data and analytics response to VAL server. For example, when the performance and analytics report of the service of the imaging for a professional application is required, the report may acquire the calculated imaging system latency of the application, and level (e.g., good, normal, poor) of the latency. + +##### 6.5.1.2.1 KQI and performance data report from NSCE client + +Figure 6.5.1.2.1-1 and 6.5.1.2.1-2 illustrate the procedure to acquire instant KQI/performance data and KQI/performance data report from NSCE client respectively. + +![Sequence diagram showing the process of instant KQI/performance data reporting between an NSCE Server and an NSCE Client.](446100c084b94817a19c319fa776b412_img.jpg) + +``` +sequenceDiagram + participant NSCE Server + participant NSCE Client + Note right of NSCE Server: 1. Instant KQI or performance data report configuration + NSCE Server->>NSCE Client: 1. Instant KQI or performance data report configuration + Note left of NSCE Client: 2. KQI or performance data report response + NSCE Client-->>NSCE Server: 2. KQI or performance data report response + Note left of NSCE Client: 3. Instant KQI or performance data report + NSCE Client-->>NSCE Server: 3. Instant KQI or performance data report +``` + +Sequence diagram showing the process of instant KQI/performance data reporting between an NSCE Server and an NSCE Client. + +**Figure 6.5.1.2.1-1: Process of instant KQI/performance data reporting** + +1. NSCE server sends a request to NSCE client to ask for instantly reporting of the KQI and performance (e.g., the jitter duration of a video service), the network performance related data (e.g., the downlink/uplink RSRP of serving cell measured by 5G UE) and the end users information (e.g., 5G UE's running time). + +NOTE 1: The APIs over the NSCE-UU interface utilized to achieve the instant KQI/performance data from NSCE client is to be defined in normative work. + +2. On receiving the request described in step1, the NSCE client sends the response to notify NSCE server whether the request is received successfully. +3. NSCE client reports the requested data (e.g., the jitter duration of a video service, 5G UE's running time) once the data is measured. + +NOTE 2: In this study, general functionalities and procedures of NSCE are defined, the required data depends on the concrete scenarios. The data measured by NSCE client may depend on the study of SEALDD. + +![Sequence diagram showing the process of reporting KQI/performance data between an NSCE Server and an NSCE Client.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` +sequenceDiagram + participant NSCE Server + participant NSCE Client + Note right of NSCE Server: 1. KQI or performance data report request + NSCE Server->>NSCE Client: 1. KQI or performance data report request + Note left of NSCE Client: 2. KQI or performance data report response + NSCE Client->>NSCE Server: 2. KQI or performance data report response + Note right of NSCE Server: 3. KQI or performance data report retrieving + NSCE Server->>NSCE Client: 3. KQI or performance data report retrieving + Note left of NSCE Client: 4. KQI or performance data report + NSCE Client->>NSCE Server: 4. KQI or performance data report +``` + +Sequence diagram showing the process of reporting KQI/performance data between an NSCE Server and an NSCE Client. + +**Figure 6.5.1.2.1-2: Process of reporting KQI/performance data** + +1. NSCE server sends a request to NSCE client to request the report collection of KQI data (e.g., the jitter duration of a video service), the network performance related data and the end users information (e.g., 5G UE's running time), and the time period of the data collection may be included in this request. + +NOTE 1: The APIs over the NSCE-UU interface utilized to achieve the instant KQI/performance data from NSCE client is to be defined in normative work. + +2. On receiving the request described in step1, the NSCE client sends the response to notify NSCE server whether the request is received successfully. +3. NSCE server sends a request to retrieve the data desired report, the data type and the time duration may be indicated in this request. +4. NSCE client sends the requested data report (e.g., the report of the jitter duration of a video service, 5G UE's running time) collected by itself. + +NOTE 2: In this study, general functionalities and procedures of NSCE are defined, the required data depends on the concrete scenarios. The data measured by NSCE client may depend on the study of SEALDD. + +### 6.5.2 Solution evaluation + +The solution addresses the key issue #7 and this solution will have interaction with 5GC and OAM system to acquire KQI and performance data from N33 and NSCE-OAM interface, it also acquires KQI and performance data from NSCE Client by NSCE-UU interface. For the NSCE Client, it has the capabilities of KQI and performance data measurement and collection from Unsce-c interface. The data measurement may also depend with SEALDD. The NSCE Server could capture the KQI and performance data from 5GC and OAM system as well as NSCE Clients. The third applications or verticals can extract the performance data of network and analysis result from NSCE Server. + +## 6.6 Solution 6: VAL server authorization and authentication via slice enabler layer + +### 6.6.1 Solution description + +#### 6.6.1.1 General + +This solution aims to address the issues identified in Key Issue 9. + +When a vertical application from third party wants to request management services as well as control plane services for a new slice on demand, it needs the authorization and authentication from 5GC. The vertical application may not be trusted by the OAM or the 5GC, it needs to interact with OAM and 5GC via the enabler server. + +#### 6.6.1.2 VAL server authorization and authentication via slice enabler layer + +Figure 6.6.1.2-1 illustrates the VAL server authorization and authentication via slice enabler layer. + +Pre-conditions: + +1. The NSCE server can be seen as a trusted AF to interact with 5GC and has registered to the OAM. +2. The NSCE server has been authorized to act as a middle layer to do the authentication and authorization. + +![Sequence diagram illustrating VAL server authorization and authentication via slice enabler layer. The diagram shows three lifelines: VAL server, NSCE server, and 5GS. The sequence of messages is: 1. VAL server sends an authorization and authentication request for a network slice management and control request to the NSCE server. 2. The NSCE server performs an authorization and authentication check. 3. The NSCE server sends an authorization and authentication response back to the VAL server. 4. The NSCE server triggers a network slice management and control operation, which is shown as a message to the 5GS.](4c731b7bb6a5851992b8b7440b4e9356_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant 5GS + Note right of NSCE server: 2. authorization and authentication check + VAL server->>NSCE server: 1. Authorization and authentication for a network slice management and control request + NSCE server-->>VAL server: 3. Authorization and authentication response + NSCE server->>5GS: 4. Network slice management and control operation + +``` + +Sequence diagram illustrating VAL server authorization and authentication via slice enabler layer. The diagram shows three lifelines: VAL server, NSCE server, and 5GS. The sequence of messages is: 1. VAL server sends an authorization and authentication request for a network slice management and control request to the NSCE server. 2. The NSCE server performs an authorization and authentication check. 3. The NSCE server sends an authorization and authentication response back to the VAL server. 4. The NSCE server triggers a network slice management and control operation, which is shown as a message to the 5GS. + +**Figure 6.6.1.2-1: VAL server authorization and authentication via slice enabler layer** + +1. The vertical server sends a request for authorization and authentication to the NSCE server with its identity and the requested network slice management and control capability (e.g. request for establish a new network slice). +2. After receiving the request, the NSCE server authenticates and authorizes the VAL server based on its identity and requested capability. + +The procedure of authentication and authorization could refer to API invoker authenticate and authorize as specified in TS 23.222[20] clause 8.10.3 and 8.11.3, if applicable. + +NOTE: the authentication and authorization mechanism will be in scope of SA3. + +3. Upon authorized and authenticated, NSCE server sends the authorization and authentication response and information to VAL server with the token. +4. The NSCE server triggers the network slice management and control operation. + +### 6.6.2 Solution evaluation + +The solution 6 proposed the producer of authorization and authentication for VAL server to address the Key Issue 9. As an authorized middle layer, the NSCE server authenticates and authorizes the VAL server based on its identity and requested capability. The API invoker authenticate and authorize functionalities of CAPIF could be utilized if applicable. After that, the VAL server can be trusted by 5GC and OAM. + +The solution is feasible. And this solution does not introduce impact on 5GS architecture and SEAL architecture. + +## 6.7 Solution 7: network slice capability registration + +### 6.7.1 Solution description + +#### 6.7.1.1 General + +This solution aims to address the issues identified in Key Issue 3. + +This solution provides a possible procedure to perform the VAL server registration. + +The vertical enablement layer (SEAL, vertical-specific enablers) supports the exposure of telco provided services to the VAL. After registered in the enablement layer, the VAL server could be authorized to access network slice related exposure capabilities, e.g. monitoring of network/UE performance. + +#### 6.7.1.2 Capability exposure registration + +![Sequence diagram for Capability exposure registration showing interactions between VAL server and NSCE Server.](144e1d61e8738b22dcf4a683f869ac6f_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE Server + Note right of NSCE Server: 2.Registration check + VAL server->>NSCE Server: 1.VAL server registration request + NSCE Server->>VAL server: 3.VAL server registration response +``` + +The diagram illustrates the interaction for capability exposure registration. It features two main entities: the VAL server and the NSCE Server. The process begins with the VAL server sending a '1.VAL server registration request' to the NSCE Server. Upon receiving the request, the NSCE Server performs a '2.Registration check', represented by a self-call on the NSCE Server lifeline. Finally, the NSCE Server sends a '3.VAL server registration response' back to the VAL server. + +Sequence diagram for Capability exposure registration showing interactions between VAL server and NSCE Server. + +**Figure 6.7.1.2-1: Capability exposure registration** + +1. The VAL server sends the registration request to the NSCE server with its identity, and may also include interested service and level of exposure requirement. +2. The NSCE server does the registration check by verifying whether all the necessary information has been provided and is reasonable. If the VAL server is already registered with the same registration information, the request will be rejected by the NSCE server. If the VAL server is already registered and updated information is received in the registration request, the request will be accepted by the NSCE server and the existing registration context of that VAL server will be updated based on the latest registration request. + +The procedure of registration check could refer to API invoker on-boarding as specified in TS 23.222[20] clause 8.1.3 if applicable. + +3. After the registration procedure, the NSCE server sends the response to the VAL server indicating could initiate the authorization and authentication and further to do the service discovery. + +### 6.7.2 Solution evaluation + +This solution solves the Key Issue 7 by proposing a procedure to register the VAL server in the slice enabler layer. The on-boarding functionalities of CAPIF could be utilized if applicable. This solution does not introduce impact on 5GS architecture and SEAL architecture. + +## 6.8 Solution 8: Discovery of management service exposure + +### 6.8.1 Solution description + +#### 6.8.1.1 General + +This solution aims to address the issues identified in Key Issue 3 and more specifically the first open issue supporting the discovery of the offered slices and the offered management services related to these slices, to the vertical/ASP. This solution also addresses partially Key Issue #13, and in particular the point on "Whether and how management domain capabilities (e.g. MnS) corresponding to the network slice need to be delivered via the NSCE server?" + +To be able to utilise capabilities/features of the management system the applications must be made aware of existence of such features and capabilities. All management domain (MD) features/capabilities come with a pre-configured exposure, where this can be configured by the operator for a given slice. This exposure is used to decide which application can see which information regarding the capability/feature. Exposure refers to the permissions that the 3rd party entity has gained over its use of the management service, e.g., the ability to read, or execute or modify or delete can be considered as different sorts of exposure. + +A MD feature/capability is anything of use offered by the management system to the 3rd party application. Therefore, a new feature could be a managed entity, a MnS or management API, any software, hardware, or other functionality – for example, new technology support, new coverage area, new network slice type or instance, new NFs or new network slice subnet type or instance. + +This solution provides a mechanism which is aligned with SA5 ongoing work related to the MnS registry exposure for external discovery (see TR 28.824 clauses 5.4 and 7.1), which enables the initial discovery of MnS for a given slice based on VAL server request, and the discovery of new/modified MnS. + +#### 6.8.1.2 Procedure + +In this procedure, the VAL server initially requests the new MnS which are supported by a target slice and based on this request the NSCE server requests from the OAM the MnS discovery (via EGMF). Then, the OAM/MnS registry derives the details to be exposed based on the NSCE server/VAL server permissions and provides the list of MnS for the given slice and the access details via the NSCE server to the VAL server. This procedure also includes the case when a new/modified MnS is deployed at the MD for the given slice, and the OAM/MnS registry provides this information directly to VAL server via EGMF (assuming that VAL server has registered to the MD). + +Pre-conditions: + +1. The VAL server has registered to receive NSCE services +2. The NSCE server is trusted by the 3GPP MD. +3. MnS registry at OAM is aware of the allowed MnS and the exposure levels for a given slice + +Figure 6.8.1.2-1 illustrates a solution for the MnS discovery support. + +![Sequence diagram illustrating MnS discovery support. The diagram shows interactions between Management Service Registry/OAM, Exposure Gateway to 3GPP MD (e.g. EGMF), NSCE Server, and VAL server. The steps are: 1. Service Discovery request (APP ID, MD ID, Slice ID) from VAL server to NSCE Server; 2. Translation of VAL server requirement to MnS requirement by NSCE Server; 3. Discovery of MnS by NSCE server; 4. Service/Management Data from NSCE Server to VAL server; 5. VAL application registration to NSCE server; 6. New or modified MnS/capability for target slice details to be exposed per NSCE server ID based on new/modified MnS; 7. Discovery of new/modified MnS by NSCE Server; 8. New or modified MnS/Capability for target slice from NSCE Server to VAL server.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE Server + participant Exposure Gateway to 3GPP MD (e.g. EGMF) + participant Management Service Registry/OAM + + Note right of VAL server: 1. Service Discovery request (APP ID, MD ID, Slice ID) + VAL server->>NSCE Server: 1. Service Discovery request (APP ID, MD ID, Slice ID) + Note right of NSCE Server: 2. Translation of VAL server requirement to MnS requirement + NSCE Server->>NSCE Server: 2. Translation of VAL server requirement to MnS requirement + Note right of NSCE Server: 3. Discovery of MnS by NSCE server + NSCE Server->>NSCE Server: 3. Discovery of MnS by NSCE server + Note right of NSCE Server: 4. Service/Management Data + NSCE Server->>VAL server: 4. Service/Management Data + Note right of VAL server: 5. VAL application registration to NSCE server + VAL server->>NSCE Server: 5. VAL application registration to NSCE server + Note left of NSCE Server: 6. New or modified MnS/capability for target slice +Derive Details to be exposed per NSCE server ID +based on new/modified MnS + NSCE Server->>NSCE Server: 6. New or modified MnS/capability for target slice +Derive Details to be exposed per NSCE server ID +based on new/modified MnS + Note right of NSCE Server: 7. Discovery of new/modified MnS by NSCE Server + NSCE Server->>NSCE Server: 7. Discovery of new/modified MnS by NSCE Server + Note right of NSCE Server: 8. New or modified MnS/Capability for target slice + NSCE Server->>VAL server: 8. New or modified MnS/Capability for target slice + +``` + +Sequence diagram illustrating MnS discovery support. The diagram shows interactions between Management Service Registry/OAM, Exposure Gateway to 3GPP MD (e.g. EGMF), NSCE Server, and VAL server. The steps are: 1. Service Discovery request (APP ID, MD ID, Slice ID) from VAL server to NSCE Server; 2. Translation of VAL server requirement to MnS requirement by NSCE Server; 3. Discovery of MnS by NSCE server; 4. Service/Management Data from NSCE Server to VAL server; 5. VAL application registration to NSCE server; 6. New or modified MnS/capability for target slice details to be exposed per NSCE server ID based on new/modified MnS; 7. Discovery of new/modified MnS by NSCE Server; 8. New or modified MnS/Capability for target slice from NSCE Server to VAL server. + +Figure 6.8.1.2-1: MnS discovery support + +The steps of this embodiment are as follows: + +1. The VAL server requests from NSCE server the expected exposure capability type and the related exposure level for a target slice or for a given VAL application, using the VAL application ID, the MD ID and optionally the slice ID. +2. The NSCE server translates the expected exposure capability type in to MnS exposure requirement. +3. The NSCE server coordinates with the 5GS and discovers the related network service(s), by triggering the MnS service discovery as specified in TS 28.533[6], clause 5.1.1 and 6.1.1. The 5GS, acting as the discovery service producer, sends the discovery result including related exposure information such as management service identifier, management service information and management service producer information to the NSCE server. +4. The NSCE server sends the service/management data based on step 3, including the list of MnS and the corresponding exposure details to the VAL server. Here to mention that based on exposure level, the exposure details may be different. +5. VAL server registers to NSCE server for the management domain capability exposure for the subscribed slice. + +The registration procedure of the VAL server to NSCE server for management capability exposure is based on Solution #7. + +6. The MnS registry discovers new or modified MnS in the 3GPP MD. The MnS registry derives the details to be exposed to the VAL server (via the NSCE server), based on the exposure level configured by the new or modified MnS and the exposure levels of registered VAL applications and NSCE server. The MnS change could be triggered due to changes on: + +- New/modified management service producers +- New/modified managed entities – such as new radio, new technology or new NFs +- New/modified technical support – such as support in a new geography or coverage area +- Availability of new management data – e.g. related to slice performance + +7. The MnS registry sends to the NSCE server the new / modified MnS, as discovered in step 6. + +8. The information on the discovered new/modified MnS is sent from the NSCE server to VAL server. + +### 6.8.2 Solution evaluation + +The solution addresses the key issue #3 and key #13; and in particular the discovery aspects related to the MnS exposure. Solution #8 is non-overlapping and complementary to Solution #7 (which describes the Registration aspects). This solution is viable and important for allowing the VAL server to discover the MnS from OAM initially and based on MnS updates from the 3GPP MD. This solution will interact with OAM initially to trigger MnS service discovery and also OAM when new or modified MnS parameters change, it will inform NSCE server on the updated/new MnS info. This solution uses already supported SA5 capabilities when interacting with OAM. + +## 6.9 Solution 9: Support for managing trusted third-party owned application(s) + +### 6.9.1 Solution description + +#### 6.9.1.1 General + +This solution addresses the key issue 10 for managing trusted third-party owned application(s) as specified in clause 5.10. + +This solution provides a possible procedure to illustrate the process of the VAL server requesting to manage network slice quota to NSCE server. This solution enables the trusted third-party AF to provide application policy information to the operator's Service Hosting Environment. This solution also enables automatic management of application resources. + +#### 6.9.1.2 Network slice quota management capability exposure + +Figure 6.9.1.2-1 illustrates the network slice quota management process to address the key issue 10 for managing trusted third-party owned application(s). + +Pre-conditions: + +1. The network slice enabler layer is capable to interact with NEF. + +![Sequence diagram illustrating the network slice quota management process between VAL server, NSCE Server, and 5GC/NEF.](e3319047c7987784f0b4d2a62db9f26d_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE Server + participant 5GC/NEF + Note right of NSCE Server: 2) Subscribe to network slice quota events + VAL server->>NSCE Server: 1) Network Slice quota management request + NSCE Server->>VAL server: 3) Network slice quota management response + Note right of NSCE Server: 2) Upon receiving notification about network slice quota events, perform VAL server specific action + +``` + +The diagram shows a sequence of interactions between three entities: VAL server, NSCE Server, and 5GC/NEF. + 1. The VAL server sends a 'Network Slice quota management request' to the NSCE Server. + 2. The NSCE Server sends a 'Subscribe to network slice quota events' message to the 5GC/NEF. + 3. The NSCE Server sends a 'Network slice quota management response' back to the VAL server. + 4. Later, the NSCE Server sends a notification to the 5GC/NEF: 'Upon receiving notification about network slice quota events, perform VAL server specific action'. + +Sequence diagram illustrating the network slice quota management process between VAL server, NSCE Server, and 5GC/NEF. + +**Figure 6.9.1.2-1: Network slice quota management process** + +1. The VAL server initiates network slice quota management request towards the NSCE server. The request includes VAL service ID, Slice identity, identity of the type of the quota, specific type of action to take (e.g. release low priority users as identified by 5GC, release list of users as identified by the VAL server, etc) and optionally list of UEs on which specific action to apply. The message also includes unique identity for the request in order to update or cancel the action based on change of the requirement or service provider's policy. +2. Upon receiving the request from the VAL server to manage the network slice quota, the NSCE server authorises the VAL server and if VAL server is authorized, the NSCE server subscribes to the network slice quota events. + +The NSCE server includes possible actions (e.g. maximum number of UEs per slice is reached, etc) expected from 3GPP core network upon reaching the network slice quota threshold. + +NOTE: The network slice quota events is not supported in release 18. + +3. The NSCE server sends the network slice quota management response specifying the result. +4. Upon receiving notification from the 5GC/NEF about network slice quota threshold, the NSCE server may request the 5GC to perform specific action if not specified already. + +### 6.9.2 Solution evaluation + +The proposed solution addresses Key Issue #10. This solution enables NSCE server to request the 5GC to perform specific action upon reaching network slice quota threshold. While SA2 has no mechanisms for AF managing UEs with different qualities/priority level within a slice in release 18. + +## 6.10 Solution 10: Network slice application policy management capability + +### 6.10.1 Solution description + +#### 6.10.1.1 General + +This solution aims to address the issues identified in Key Issue 10. + +This solution provides a possible procedure to illustrate the process of the VAL server requesting to manage network slice through NSCE server when reaching UEs slice quota threshold. This solution enables the trusted third-party AF to provide network slice access management policy based on the UE's priority, contract qualities level, etc. This solution also helps to avoid traffic loss in case of slice congestion and make adjustment beforehand considering the application policy from AF. + +#### 6.10.1.2 Network slice application policy management capability + +Figure 6.10.1.2-1 illustrates the application policy capability process to address the key issue 10 described in clause 5.10. + +Pre-conditions: + +1. The VAL server is authorized to use the slice event reporting exposure and slice adaptation trigger capability. +2. The network slice enabler layer is capable to interact with NEF/NWDAF/NSACF and OAM system. +3. NSCE has added UEs to different slices based on UE priority, QoS reservation. High priority UEs with dedicated reserved resources are in one slice. + +![Sequence diagram illustrating the Network slice application policy management process. The diagram shows interactions between four entities: VAL server, NSCE server, 5GS, and OAM. The process starts with the VAL server sending a 'Slice event reporting exposure Request' to the NSCE server. The NSCE server responds with 'Request authorization' and 'Slice event exposure subscribe Request'. The 5GS sends an 'Event Trigger' to the NSCE server, which then sends a 'Slice event Notify' to the VAL server. The VAL server sends a 'Slice adaptation trigger' to the NSCE server. The NSCE server then sends a 'Retrieve network slice status' request to both the 5GS and OAM. The 5GS and OAM return status information, which the NSCE server uses for 'Network slice adaptation analysis and trigger adjustment action(s)' and 'Network slice lifecycle management operation(s)'.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant 5GS + participant OAM + + Note right of NSCE server: 2. Request authorization + Note right of NSCE server: 3. Slice event exposure subscribe Request + + VAL server->>NSCE server: 1. Slice event reporting exposure Request + NSCE server-->>VAL server: 2. Request authorization + NSCE server-->>VAL server: 3. Slice event exposure subscribe Request + NSCE server->>5GS: 4. Slice event subscribe Request + 5GS-->>NSCE server: 4. Slice event subscribe Response + Note right of 5GS: 5. Event Trigger + 5GS->>NSCE server: 6. Slice event Notify + NSCE server->>VAL server: 7. Slice event notify + VAL server->>NSCE server: 8. Slice adaptation trigger + Note right of NSCE server: 9. Retrieve network slice status + NSCE server->>5GS: 9. Retrieve network slice status + NSCE server->>OAM: 9. Retrieve network slice status + Note right of NSCE server: 10. Network slice adaptation analysis and trigger adjustment action(s) + Note right of NSCE server: 11. Network slice lifecycle management operation(s) + +``` + +Sequence diagram illustrating the Network slice application policy management process. The diagram shows interactions between four entities: VAL server, NSCE server, 5GS, and OAM. The process starts with the VAL server sending a 'Slice event reporting exposure Request' to the NSCE server. The NSCE server responds with 'Request authorization' and 'Slice event exposure subscribe Request'. The 5GS sends an 'Event Trigger' to the NSCE server, which then sends a 'Slice event Notify' to the VAL server. The VAL server sends a 'Slice adaptation trigger' to the NSCE server. The NSCE server then sends a 'Retrieve network slice status' request to both the 5GS and OAM. The 5GS and OAM return status information, which the NSCE server uses for 'Network slice adaptation analysis and trigger adjustment action(s)' and 'Network slice lifecycle management operation(s)'. + +**Figure 6.10.1.2-1: Network slice application policy management process** + +1. The VAL server initiates network slice event reporting exposure request towards the NSCE server. The request includes VAL service ID, Event Filter (such as slice identity, event type, etc.), Event Reporting filter (such as whether the notification is threshold based or periodical). The message also includes notification threshold or periodicity based on the Event Reporting filter settings. +- 2-3. Upon receiving the request from the VAL server to manage the network slice quota event reporting, the NSCE server authorises the VAL server and if VAL server is authorized, the NSCE server subscribes to the network slice quota (the number of UE or PDU sessions) events, including the slice identity (S-NSSAI) and threshold/periodicity information. According to 3GPP TS 23.502 [4], there can be multiple NSACFs serving the same network slice and different threshold can be set based on the policy of trusted third-party AF. The event subscription procedure is described in clause 4.15.3.2.10 of TS 23.502 [4], and the APIs defined in clause 6.2 of TS 29.536 [22] can be utilized. +4. The NSCE server receives the network slice event notification response specifying the result after 5GC confirms the subscription. +- 5-6. When the event (e.g. the number of UE or PDU sessions has reached the threshold for specific slice) happens, the notification is sent from 5GC to NSCE server including the Event Reporting information (such as percentage of the maximum number of UEs or percentage of the maximum number of the PDU Sessions established on the network slice). The event notification procedure is specified in clause 4.15.3.2.10 of TS 23.502 [4]. +7. The notification is forwarded from NSCE server to VAL server including the Event ID, Event filter and Event reporting information. +8. The VAL server initiates network slice adaptation trigger request to the NSCE server. +9. The NSCE server retrieves the network slice related status information from 5GC and OAM. For OAM system, the services defined in clause 11.3 of TS 28.532 [8] and clause 5 of TS 28.552 [12] can be utilized. For CN functions, the services of Nnwdaf\_AnalyticsInfo service defined in clause 7.3 of TS 23.288 [17] can be utilized. +10. The NSCE server makes network slice adaptation analysis on network status information from 5GS and makes slice adjustment decision. NSCE server can make slice lifecycle management operations for specific slice as specified in step 11. + +11. The NSCE server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s) (e.g. to allocate more RAN resources for UEs with high priority), such as modifyNsi request as specified in TS 28.531 [5]. + +### 6.10.2 Solution evaluation + +The proposed solution addresses Key Issue #10, the solution provides a high level procedure for the capability of network congestion handling when reaching UEs slice quota threshold. Based on VAL request, the NSCE server can define preferred slice maximum capacity threshold and get notification when the threshold is reached. Both the 5GC and OAM can be interacted by NSCE server to collect slice related status information. Based on VAL request, the NSCE server can make adjustment slice resource allocation (max number of registered UEs and max number of PDU sessions) having in mind the increased demand. SA5 has defined slice service profile parameters modification (as specified in TS 28.541 [14]) to change the maximum number of UEs/maximum number of PDU sessions in a slice. This solution does not introduce impact on 5GS architecture, the NSCE server has the capability to analyze network status data and decide how to make slice resource adjustment. The NSCE server can potentially have lack of knowledge of the actual hardware limitations of 5GC/NSACF. During normative phase it would be decided if NSCE server will manage RAN parameters for slice adaptation. It might be the case that SA5 has its own solution for adapting network slice capacity (max number of registered UEs and max number of PDU sessions per slice). During normative phase it will be decided if the NSCE server shall inform the VAL server about the result of NSCE slice adaptation. During the normative phase actual APIs will be described. The SA6 SEAL will possibly need enhancement to support the interaction with 5GS and OAM system. + +## 6.11 Solution 11: Communication service management exposure + +### 6.11.1 Solution description + +#### 6.11.1.1 General + +This solution aims to address the issues identified in Key Issue 5. + +This solution provides a procedure for communication services management including the communication service lifecycle and communication assurance performed by the network slice capability enablement server. + +To enable the verticals to create/modify/disengagement a communication service, the NSCE layer helps the VAL server to subscribe the slice services to allocate the network slices to fulfil the communication services. Also the NSCE server is able to perform the network slice related analyses to help the verticals to assure the communication service. + +#### 6.11.1.2 Use Case of Communication service lifecycle management + +Figure 6.11.1.2-1 illustrates one possible procedure of communication service management to address the communication service lifecycle management and communication service assurance + +Pre-conditions: + +1. The VAL client ordered slice services to offer its communication services. +2. The network slice enabler layer is registered/capable for interacting with 5GS such as triggering network slice LCM operations. + +![Sequence diagram for Communication service creation](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server as network slice capability enablement server + participant 5GS + Note right of NSCE server: 2.SLA determination + Note right of NSCE server: 3. Network Slice allocation + VAL server->>NSCE server: 1. Communication service creation request + NSCE server-->>VAL server: 4. Communication service creation response +``` + +The diagram illustrates a sequence of four messages between three entities: VAL server, network slice capability enablement server (NSCE), and 5GS. The sequence starts with the VAL server sending a '1. Communication service creation request' to the NSCE server. The NSCE server then performs internal steps '2.SLA determination' and '3. Network Slice allocation', which are shown in boxes below the server lifeline. Finally, the NSCE server sends a '4. Communication service creation response' back to the VAL server. + +Sequence diagram for Communication service creation + +**Figure 6.11.1.2-1: Communication service creation** + +1. The VAL server sends a request to NSCE server to create a communication service, e.g., the VAL server requests to create a video service in a future factory, the requirements of the video service (for instance, the service ID, the number of the UEs, the coverage area of the video service, the mobility information of the UEs, the resolution of the video service) is included in this request. +2. NSCE server translates the communication service requirements (e.g., for a video service, the mobility information and the resolution of the video) then determines the network SLA (e.g., *dLtThptPerSlice*, *uLtThptPerSlice*, latency as defined in *serviceProfile* TS 28.541[14]). The NSCE may perform the translation by pre-configured industry profiles or by KQI-KPI translation algorithms which are out scope of standard. +3. NSCE server initiates the Slice Service subscription procedures by utilizing the management service of network slice creation as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5. The slice creation request may fail due to the shortage of network resources. +4. NCSE server sends the communication service creation response to VAL server. If the slice creation failed in step3, the NSCE server may ask the VAL sever to modify the service requirements. + +![Sequence diagram for Communication service modification](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server as network slice capability enablement server + participant 5GS + Note right of NSCE server: 2. SLA update + Note right of NSCE server: 3. Network Slice Update + VAL server->>NSCE server: 1. Communication service reconfiguration request + NSCE server-->>VAL server: 4. Communication service reconfiguration response +``` + +The diagram illustrates the interaction for communication service modification. It features three lifelines: VAL server, network slice capability enablement server, and 5GS. The sequence begins with the VAL server sending a '1. Communication service reconfiguration request' to the network slice capability enablement server. The server then performs internal steps labeled '2. SLA update' and '3. Network Slice Update'. Finally, it sends a '4. Communication service reconfiguration response' back to the VAL server. + +Sequence diagram for Communication service modification + +**Figure 6.11.1.2-2: Communication service modification** + +1. VAL server sends the communication service reconfiguration request to the NSCE server to reconfigure the properties of the communication service if the SLA is not able to satisfy current service requirements (e.g., reconfigure the resolution requirements of the communication service) or the VAL server predicts that service requirements changes sometime in the future (e.g., some new cameras are to be supported). +2. NSCE server translates the communication requirements according the reconfigured communication properties then updates the network SLA. +3. NSCE server initiates the Slice Service update procedures by utilize the management service of network slice modification as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5. +4. NCSE server sends the communication service modification response to VAL server. + +![Sequence diagram for Communication service disengagement](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server as network slice capability enablement server + participant 5GS + Note right of NSCE server: 2. Network Slice deallocation + VAL server->>NSCE server: 1. Communication service disengagement request + NSCE server-->>VAL server: 3. Communication service disengagement response +``` + +The diagram illustrates the interaction for communication service disengagement. It features three lifelines: VAL server, network slice capability enablement server, and 5GS. The sequence begins with the VAL server sending a '1. Communication service disengagement request' to the network slice capability enablement server. The server then performs an internal step labeled '2. Network Slice deallocation'. Finally, it sends a '3. Communication service disengagement response' back to the VAL server. + +Sequence diagram for Communication service disengagement + +**Figure 6.11.1.2-3: Communication service disengagement** + +1. The VAL server sends a request to NSCE server to disengage the communication service when the communication service ends. + +2. NSCE server initiates the Slice Service de-allocation procedures by utilizing the management service of network slice de-allocation as defined in clause 6.1, TS 28.531[5] exposed by EGMF defined in SA5. +3. NCSE server sends the communication service disengagement response to VAL server. + +#### 6.11.1.3 Communication service creation + +![Sequence diagram for Communication service creation](69e5f1993021af230d08c08aac97d9df_img.jpg) + +``` +sequenceDiagram + participant VAL_Server + participant NSCE_Server + Note right of VAL_Server: 1. Communication Service creation service subscription + VAL_Server->>NSCE_Server: 1. Communication Service creation service subscription + Note left of NSCE_Server: 2. Communication Service creation service notification + NSCE_Server-->>VAL_Server: 2. Communication Service creation service notification +``` + +The diagram illustrates the interaction between a VAL\_Server and an NSCE\_Server for communication service creation. The VAL\_Server sends a 'Communication Service creation service subscription' message to the NSCE\_Server. The NSCE\_Server responds with a 'Communication Service creation service notification' message back to the VAL\_Server. + +Sequence diagram for Communication service creation + +**Figure 6.11.1.3-1: Communication service creation** + +Figure 6.11.1.3-1 shows the APIs of service subscription of communication service creation as step 1 and step 4 of Figure 6.11.1.2-1. + +#### 6.11.1.4 Communication service modification + +![Sequence diagram for Communication service reconfiguration](18291be12b470a557e8c9f3a74e021be_img.jpg) + +``` +sequenceDiagram + participant VAL_Server + participant NSCE_Server + Note right of VAL_Server: 1. Communication Service reconfiguration subscription + VAL_Server->>NSCE_Server: 1. Communication Service reconfiguration subscription + Note left of NSCE_Server: 2. Communication Service reconfiguration notification + NSCE_Server-->>VAL_Server: 2. Communication Service reconfiguration notification +``` + +The diagram illustrates the interaction between a VAL\_Server and an NSCE\_Server for communication service modification. The VAL\_Server sends a 'Communication Service reconfiguration subscription' message to the NSCE\_Server. The NSCE\_Server responds with a 'Communication Service reconfiguration notification' message back to the VAL\_Server. + +Sequence diagram for Communication service reconfiguration + +**Figure 6.11.1.4-1: Communication service reconfiguration** + +Figure 6.11.1.4-1 shows the APIs of service subscription of communication service reconfiguration as step 1 and step 4 of Figure 6.11.1.2-2. + +#### 6.11.1.5 Communication service disengagement + +![Sequence diagram showing communication service disengagement between VAL_Server and NSCE_Server. Step 1: VAL_Server sends a 'Communication Service disengagement subscription' to NSCE_Server. Step 2: NSCE_Server sends a 'Communication Service disengagement notification' back to VAL_Server.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +``` + +sequenceDiagram + participant VAL_Server + participant NSCE_Server + Note right of VAL_Server: 1. Communication Service disengagement subscription + VAL_Server->>NSCE_Server: 1. Communication Service disengagement subscription + Note left of NSCE_Server: 2. Communication Service disengagement notification + NSCE_Server->>VAL_Server: 2. Communication Service disengagement notification + +``` + +Sequence diagram showing communication service disengagement between VAL\_Server and NSCE\_Server. Step 1: VAL\_Server sends a 'Communication Service disengagement subscription' to NSCE\_Server. Step 2: NSCE\_Server sends a 'Communication Service disengagement notification' back to VAL\_Server. + +**Figure 6.11.1.5-1: Communication service reconfiguration** + +Figure 6.11.1.5-1 shows the APIs of service subscription of communication service reconfiguration as step 1 and step 3 of Figure 6.11.1.2-3. + +### 6.11.2 Solution evaluation + +The solution addresses the key issue #5 of communication service management exposure. In this solution, the NSCE server interacts with VAL server to acquire/update the requirements of the communication service if a communication services is required to create/update. After the determination of the SLA of network slice according to the communication services requirements, the NSCE Server will have interactions with OAM system to trigger the network slice allocation/modification/deallocation by utilize the network slice related management services exposed by EGMF defined in SA5. The existing management services defined in SA5 are able to support the solution described in clause 6.11.1. The APIs over S-NSCE interface to be defined in normative phase: + +1. APIs of service subscription of communication service creation (for instance, to create a service, the service ID, the number of the UEs, the coverage area of the service, the mobility information of the UEs) +2. APIs of service subscription of communication service reconfiguration +3. APIs of service subscription of communication service disengagement + +## 6.12 Solution 12: SEAL enhancement + +This solution aims to address the issues "which enhancement to SEAL network slice capability management service is required" identified in Key Issue 1. + +This solution illustrates the impact on SEAL by analyzing the existing solutions. + +### 6.12.1 Solution description + +The following solutions provide the new service which could enhance the SEAL network slice capability management service defined in TS 23.434: + +- Solution 1 provides the Automatic application layer network slice management service based on the collected network slice status from 5GS and QoE from application layer; +- Solution 2 provides the Network slice fault management capability based on collected alarm information from 5GS and application fault data from application layer; +- Solution 3 provides the Slice API configuration by mapping the VAL application requirement to a slice API, and API translation service by mapping the slice API to service API; + +- Solution 4 and solution 5 provide the QoS verification service and the performance and analytics exposure based on the QoS and performance data 5GS, and KQI and QoE data from NSCE Client. +- Solution 8 provides the Discovery of management service exposure by triggering the MnS service discovery; +- Solution 9 provides a possible procedure to illustrate the process of the VAL server requesting to manage network slice quota, but it does not specify specific follow up action(s). Solution 10 provides the Network slice application policy management capability based on slice quota by triggering the network slice lifecycle management. Solution 20 provides service of AF policy based network slice optimization by utilizing the network slice related management services. The three solutions may be merged in the normative work to enhance the SEAL. +- Solution 11 provides the Communication service management exposure; + +Solution 13 provides a Network Slice allocation service, where the NSCE layer performs the Network Slice allocation operation on behalf of the VAL server, and sends the allocated Network Slice information (e.g., S-NSSAI) to the NSCE Client. + +- Solution 14 provides a service of information collection among the NSCE servers. This service requires an interface between NSCE servers. +- Solution 15 provides enhancements to the existing NSCE client functionality by separating the network slice adaptation subscription/notification functionality from the slice adaption triggering. Also, it enables the NSCE server to receive location requirements, schedule time window requirements and access type within the network slice adaptation request sent from the NSCE client. +- Solution 16 and solution 17 provide Multi-Network slice monitoring service and Multi-Network slice resource optimization service for network slice from multi-networks (e.g. the PNI-NPN network and PLMN network) through NSCE server in a combined manner. +- Solution 18 provides service of Network Slice Information delivery. It could be done via request and subscribe/notify operation, also it could be done along with the registration procedure. +- Solution 19 provides service of slice requirement alignment by comparing the slice requirements with network current situations to estimate if the current slice requirements are properly configured. +- Solution 21 provides service of predictive slice modification in edge based NSCE deployments, which is mainly for the NSaaS scenario when an expected migration happens for a UE or group of UEs from an EDN to another. + +The following solutions could utilize the exiting services of CAPIF, and may not introduce enhancement to SEAL. + +- Solution 6 provides the authorization and authentication capability. +- Solution 7 provides the registration capability. + +Solution 1, 2, 3, 4, 5, 8, 10, 11, 13, 16, 17, 18, 19, 20, 21 require the interface between OAM and NSCE server (OAM-NSCE interface defined by SA5). Solution 14, 16, 17, 21 require the interface between the NSCE servers (NSCE-E interface). Therefore the SEAL NSCE architecture could consider to support the NSCE-E interface. + +### 6.12.2 Solution evaluation + +This solution analyzes all the solutions that could provide services to enhance SEAL service. The above analysis could be taken into consideration while working on the conclusion. + +## 6.13 Solution 13: Network Slice Allocation by VAL server + +### 6.13.1 Solution description + +#### 6.13.1.1 General + +The NSCE layer performs the Network Slice allocation operation on behalf of the VAL server. The non-trusted 3rd party application (i.e., VAL server) can not access to the 5GS management system directly. So, the NSCE server needs to perform the authentication and authorization for the registration of VAL server on behalf of 5G MnS. This procedure follows the clause 6.7 Solution 7 network slice capability registration. + +The Network Slice creation that is triggered by the VAL server depends upon network operator policy. The network slice capabilities and management options offered to the customer are determined by a business agreement prior to and outside of the scope of 3GPP standards. + +The VAL server can identify the Network slice in Network Slice creation request with the Network Slice indicator (e.g., S-NSSAI). + +Upon network slice allocation, the NSCE server acts as the network slice provisioning MnS consumer. The NSCE server requests 'AllocacatedNsi' operation to the network slice provisioning MnS producer as specified in TS 28.531. When the 'AllocatedNsi' operation is received, the network slice provisioning MnS Producer in 5GS performs charging mechanism as specified in TS 28.202. + +The NSCE server sends the allocated Network Slice information (e.g., S-NSSAI) to the NSCE Client, after the Network Slice allocation to the VAL server is successful. + +NOTE: If the UE is provisioned with URSP rules by the network operator, the UE handles the precedence between the delivered network slice info via NSCE layer info and URSP rules as defined in 3GPP TS 23.503 [12] clause 6.1.2.2.1. How the UE uses the Network Slice info delivered via NSCE layer in relation to the URSP is implementation dependent. + +With the above regards, The NSCE layer performs the below for the Network Slice Allocation by the VAL server. + +- Network Slice Allocation operation on behalf of VAL Server as specified in TS 28.531 +- Delivery of the Network Slice Allocation result +- Delivery of the allocated Network Slice Information to NSCE client + +The VAL server as a Network Slice consumer makes use of the APIs provided from NSCE server to allocate the Network Slice for the Network Slice Lifecycle management for its service. + +#### 6.13.1.2 Network Slice Allocation by VAL Server + +This subclause depicts the procedure of the Network Slice Allocation by the VAL server, when the VAL server needs to allocate the Network Slice, interaction with 5GS via the NSCE layer. + +![Sequence diagram illustrating Network Slice Allocation by the VAL server. The diagram shows interactions between VAL Server, NSCE server, 5GS, and NSCE Client. The process involves ordering a network slice, creating it, allocating it with AF guidance, and then storing the information at the client.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS + participant NSCE Client + + Note over VAL Server, NSCE server: Network Slice Information Delivery + + VAL Server->>NSCE server: 1. Order a Network Slice + VAL Server->>NSCE server: 2. Network Slice creation request + Note over NSCE server, 5GS: 3. Network Slice Allocation & AF Guidance on URSP rule determination per VAL UE + NSCE server->>VAL Server: 4. Network Slice creation response + NSCE server->>NSCE Client: 5. Network Slice allocation information delivery + Note over NSCE Client: 6. Store Allocated Network Slice Information (e.g., S-NSSAI) + NSCE Client->>NSCE server: 7. Network Slice allocation information response + +``` + +Sequence diagram illustrating Network Slice Allocation by the VAL server. The diagram shows interactions between VAL Server, NSCE server, 5GS, and NSCE Client. The process involves ordering a network slice, creating it, allocating it with AF guidance, and then storing the information at the client. + +**Figure 6.13.1.2-1: Network Slice Allocation by the VAL server** + +1. The VAL server makes an request to create the Network Slice. + +The VAL server specifies the Network Slice requirements for the VAL service. The Network Slice requirement at the VAL server may be specified with the attributes of GST (which results in NEST) as specified in GSMA NG.116. + +2. The VAL server requests the Network Slice creation with the Network Slice requirements. + +The Network Slice creation request includes the VAL Service ID, VAL UE's ID List, S-NSSAI and so on. + +3. The NSCE server performs the Network Slice Allocation. The NSCE server as network slice provisioning MnS consumer requests of 'AllocacatedNsi' operation as specified in TS 28.531. + +When the 'AllocatedNsi' operation is received, the network slice provisioning MnS Producer performs charging mechanism as specified in TS 28.202. + +The NSCE server performs AF-driven guidance for URSP determination to 5GS per VAL UE. + +NOTE 1: According to the network operator policy, the NSCE server acting as AF may send the created network slice information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in TS23.502 clause 4.15.6.10, TS 23.503 clause 6.6.2.2, TS 23.548 clause 6.2.4). This guidance may create the new route selection parameters to indicate sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic. + +4. The NSCE server sends the result of Network Slice Allocation to the VAL server. + +5. The NSCE server delivers the Network Slice Allocation Information to the NSCE Clients of VAL UEs based on the VAL UE's ID list from step 2, in case the Network Slice Allocation is successful, if the NSCE server does not perform AF-driven guidance for URSP determination to 5GS in step 3. + +The Network Slice Allocation Information contains the VAL service ID, S-NSSAI, DNN and so on. + +6. The NSCE client stores and applies the Network Slice Allocation Information. + +7. The NSCE client sends the Network Slice Allocation Information response to the NSCE server. + +NOTE 2: If the UE is provisioned with URSP rules by the network operator, the UE handles the precedence between the delivered network slice info via NSCE layer info and URSP rules as defined in 3GPP TS 23.503 [12] clause 6.1.2.2.1. How the UE uses the Network Slice info delivered via NSCE layer in relation to the URSP is implementation dependent. + +### 6.13.2 Solution evaluation + +The proposed solution addresses the KI #14. + +This solution provides the procedure for NSCE layer to operate the Network Slice allocation on behalf of the VAL server. This allows the NSCE layer to interact with both the VAL server and 5GS MnS for allocating Network Slice and makes use of the operation of 5GS MnS defined in SA5. The interaction between NSCE server and NSCE client is required for informing the Network slice to be used for the service provided from the VAL server. + +The APIs of NSCE layer expect to be defined for the Network slice allocation for the VAL server in the normative phase. + +## 6.14 Solution 14: Interaction between the NSCE servers + +### 6.14.1 Solution description + +This solution aims at addressing the KI #12 and KI #1. It proposes procedures of interaction between the NSCE servers. + +### 6.14.2 Information collection from multiple NSCE servers + +The owner of the centralized/national NSCE server including the MNO and vertical could have requirement to collect the slice status from edge/provincial NSCE server. The collected information could be used to optimize network resource allocation after some analysis. + +Pre-condition: + +1. NSCE server#2 has agreement with NSCE server#1 to provide the collected slice information. + +![Sequence diagram showing information collection between NSCE server 1 and NSCE server 2.](507e8bc710c80563f5ee9e2f0ebb603d_img.jpg) + +``` +sequenceDiagram + participant NSCE server 1 + participant NSCE server 2 + Note right of NSCE server 2: 2.authentication + NSCE server 1->>NSCE server 2: 1.monitoring request + NSCE server 2->>NSCE server 1: 3. Slice information report +``` + +The diagram is a sequence diagram with two lifelines: 'NSCE server 1' and 'NSCE server 2'. The interaction consists of three steps: 1. 'NSCE server 1' sends a 'monitoring request' to 'NSCE server 2'. 2. 'NSCE server 2' performs an 'authentication' step (shown in a box). 3. 'NSCE server 2' sends a 'Slice information report' back to 'NSCE server 1'. + +Sequence diagram showing information collection between NSCE server 1 and NSCE server 2. + +**Figure 6.14.2: Information collection from multiple NSCE servers** + +1. The NSCE server#1 sends out the information collection subscription request with expected period and interested slice ID, e.g., List of SNSSAI. This step could be done by pre-configuration. +2. The NSCE server#2 shall check if the NSCE server#1 is authorized to get the network slice information. +3. After authenticated, the NSCE server#2 sends collected slice information to NSCE server#1. The Network slice related performance and analytics exposure could be re-utilized. + +### 6.14.3 Solution evaluation + +This solution addresses the KI #12 and KI #1 by providing a interaction procedure between the NSCE servers. In this solution, the NSCE server interacts with another NSCE server to monitor/collect the network slice information. The + +Network slice related performance and analytics exposure could be re-utilized to do the network slice information collection/monitoring. + +The APIs over NSCE-E interface to be defined in normative phase: + +1. APIs of NSCE server registration on another NSCE server. +2. APIs of service subscription of information collection across NSCE server. + +## 6.15 Solution 15: UE triggered network slice adaptation + +### 6.15.1 Solution description + +#### 6.15.1.1 General + +This pCR provides a solution for Key Issue #1 regarding UE triggered network slice adaptation. + +The solution is provided via enhancements to existing TS 23.434 text as shown below, highlighted in yellow. + +\*\*\* Enhancement based on TS 23.434 v. 18.0.0 \*\*\* + +#### 16.3.2.4 Procedure for VAL UE-triggered and network-based network slice adaptation for VAL application + +Figure 16.3.2.4-1 illustrates the VAL UE-triggered and network-based procedure where the NSCE server supports the network slice adaptation with the underlying 3GPP system for the VAL UEs of the VAL application. + +Pre-condition: + +- The NSCE client has connected to the NSCE server; + +![Sequence diagram illustrating the network slice adaptation procedure for a VAL application. The diagram shows four main entities: VAL UE (containing VAL client and NSCE client), NSCE server, and 5GC. The sequence of messages is: 1. VAL application requirement change (from VAL client to NSCE client); 2. Network slice adaptation trigger request (from NSCE client to NSCE server); 3. Network slice adaptation trigger per VAL UE (from NSCE server to 5GC); 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination) (from 5GC to NSCE server); 5. Network slice adaptation trigger response (from NSCE server to NSCE client).](52f68e21acc86c9aaab2f5abc51a9748_img.jpg) + +``` + +sequenceDiagram + participant VAL UE as VAL UE (VAL client, NSCE client) + participant NSCE server + participant 5GC + Note left of VAL UE: 1. VAL application requirement change + VAL UE->>NSCE server: 2. Network slice adaptation trigger request + NSCE server->>5GC: 3. Network slice adaptation trigger per VAL UE + 5GC->>NSCE server: 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination) + NSCE server->>VAL UE: 5. Network slice adaptation trigger response + +``` + +Sequence diagram illustrating the network slice adaptation procedure for a VAL application. The diagram shows four main entities: VAL UE (containing VAL client and NSCE client), NSCE server, and 5GC. The sequence of messages is: 1. VAL application requirement change (from VAL client to NSCE client); 2. Network slice adaptation trigger request (from NSCE client to NSCE server); 3. Network slice adaptation trigger per VAL UE (from NSCE server to 5GC); 4. Network slice adaptation per VAL UE (AF guidance on URSP rule determination) (from 5GC to NSCE server); 5. Network slice adaptation trigger response (from NSCE server to NSCE client). + +Figure 16.3.2.4-1: Network slice adaptation for VAL application + +1. The VAL client provides a new application requirement to the NSCE client, indicating a new service profile for the VAL application. This may be in the form of a change at the application QoS requirements, **location requirement, time window requirement, access type preference (e.g., 3GPP, non-3GPP or multi-access), service operation change, or other application-related parameters.** +2. The NSCE client sends a network slice adaptation trigger **request** to the NSCE server for the VAL application. This trigger may be in the form of exact requested network slice (and optionally DNN) for the VAL UE of the VAL application; or indication that the VAL application needs to be remapped to a different network slice (and optionally DNN). **The trigger may also include additional parameters based on the step 1 request, including** + +requested location criteria, time window, access type preference, associated group id or UE IP address preservation indicator. + +NOTE 1 : How the requested network slice is known by the NSCE client is out of scope of this release. + +3. The NSCE server processes the request and triggers the network slice configuration per VAL UE within the VAL Application. + +NOTE 2: How the NSCE server decides to trigger the network slice configuration is implementation dependent. + +NOTE 3: Whether and how the NSCE server triggers the network slice adaptation for all the VAL UEs within the VAL Application is out of scope of this release. + +4. The NSCE server acting as AF provides the updated S-NSSAI, location criteria, time window, access type preference, associated group id or UE IP address preservation indicator and DNN per VAL UE. In particular, NSCE server sends this information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in TS23.502 clause 4.15.6.10, TS 23.503 clause 6.6.2.2, TS 23.548 clause 6.2.4). This guidance may update the route selection parameters to indicate different sets of PDU Session information (DNN, S-NSSAI, location criteria, time window, access type preference, associated group id or UE IP address preservation indicator) that can be associated with applications matching the application traffic. 5GC uses this information to update the URSP to the affected UE(s). + +NOTE 4: NSCE server provides the updated S-NSSAI, DNN, location criteria, time window and access type preference, associated group id or UE IP address preservation indicator as a suggestion/guidance to PCF; however it is up to PCF to decide whether to perform the slice/DNN re-mapping + +5. The NSCE server ~~may~~ sends a ~~notification~~ response to the NSCE client indicating success or failure. + +### 16.3.2.X Procedure for VAL UE network slice adaptation subscription + +Figure 16.3.2.X-1 illustrates the VAL UE network slice adaptation subscription procedure. + +Pre-condition: + +- The NSCE client has connected to the NSCE server. + +![Sequence diagram for VAL UE network slice adaptation subscription. The diagram shows four lifelines: VAL UE (containing VAL client and NSCE client), NSCE server, and 5GC. The sequence of messages is: 1. NSCE client sends a 'Network slice adaptation subscription request' to the NSCE server. 2. The NSCE server sends a 'Subscribe to VAL UE network slice adaptations' message to the 5GC (indicated by a dashed box). 3. The NSCE server sends a 'Network slice adaptation subscription response' back to the NSCE client.](2c3bf03decbeb6a8038deccc5a796b46_img.jpg) + +``` + +sequenceDiagram + participant VAL UE + subgraph VAL UE + VC[VAL client] + NC[NSCE client] + end + participant NSCE server + participant 5GC + Note right of NSCE server: 2. Subscribe to VAL UE network slice adaptations + NC->>NSCE server: 1. Network slice adaptation subscription request + NSCE server-->>5GC: 2. Subscribe to VAL UE network slice adaptations + NSCE server-->>NC: 2. Network slice adaptation subscription response + +``` + +Sequence diagram for VAL UE network slice adaptation subscription. The diagram shows four lifelines: VAL UE (containing VAL client and NSCE client), NSCE server, and 5GC. The sequence of messages is: 1. NSCE client sends a 'Network slice adaptation subscription request' to the NSCE server. 2. The NSCE server sends a 'Subscribe to VAL UE network slice adaptations' message to the 5GC (indicated by a dashed box). 3. The NSCE server sends a 'Network slice adaptation subscription response' back to the NSCE client. + +Figure 16.3.2.X-1: VAL UE network slice adaptation subscription + +1. The NSCE client sends a network slice adaptation subscription request to the NSCE server to subscribe to network slice adaptations. The subscription request includes identifiers of the VAL UE, VAL application, network slice and a notification target address. +2. The NSCE server processes the request by checking if the NSCE client is authorized to initiate the network slice adaptation subscription request. Further, the NSCE server acting as an AF may subscribe via the NEF to receive network slice adaptation notifications (i.e., changes to URSP rules) applicable to the VAL UE. + +3. The NSCE server replies with a network slice adaptation subscription response to the NSCE client indicating the subscription status. + +### 16.3.2.X Procedure for VAL UE network slice adaptation notification + +Figure 16.3.2.X-1 illustrates the VAL UE network slice adaptation notification procedure. + +Pre-condition: + +- The NSCE client has connected to the NSCE server; + +![Sequence diagram for VAL UE network slice adaptation notification. Lifelines: VAL client, NSCE client, NSCE server, 5GC. The diagram shows three steps: 1. NSCE server detects adaptation (inside 5GC), 2. NSCE server sends notification to NSCE client, 3. NSCE client notifies VAL client (dashed box).](71b0a68b4dd64961465d2b0e790538de_img.jpg) + +``` + +sequenceDiagram + participant VAL client + participant NSCE client + participant NSCE server + participant 5GC + Note right of 5GC: 1. Detect VAL UE network slice adaptation + NSCE server->>NSCE client: 2. Network slice adaptation notification + Note left of VAL client: 3. Notify VAL client of network slice adaptation + +``` + +Sequence diagram for VAL UE network slice adaptation notification. Lifelines: VAL client, NSCE client, NSCE server, 5GC. The diagram shows three steps: 1. NSCE server detects adaptation (inside 5GC), 2. NSCE server sends notification to NSCE client, 3. NSCE client notifies VAL client (dashed box). + +Figure 16.3.2.4-1: VAL UE network slice adaptation notification + +1. The NSCE server detects network slice adaptation (i.e., changes to URSP rules) has occurred for the VAL UE. +2. The NSCE server sends a network slice adaptation notification to the NSCE client. The NSCE server includes information regarding the type of network slice adaptation event that has occurred. +3. The NSCE client optionally notifies the VAL client of the network slice adaptation. + +##### 16.3.2.2.3 Network slice adaptation trigger request + +Table 16.3.2.2.3-1 describes the information flow of network slice adaptation trigger request from the NSCE client to the NSCE server. + +Table 16.3.2.2.3-1: Network slice adaptation trigger request + +| Information element | Status | Description | +|------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------| +| VAL UE ID(s) | M | The VAL UE ID(s) within the VAL service, for which the network slice adaptation trigger applies | +| VAL service ID | M | The VAL service ID of the VAL application for which the network slice configuration may correspond to. | +| Requested S-NSSAI | M | Indication of the new S-NSSAI which is requested. | +| Requested DNN | O | Indication of the new DNN which is requested. | +| Requested time window | O | Indication of the new scheduled time window that is requested | +| Requested location criteria | O | Indication of the new location criteria that is requested | +| Requested access type preference | O | Indication of the new access type (3GPP, non-3GPP or multi-access) preference that is requested. | +| Requested associated group id | O | Indication of the group id that is requested | +| Requested UE IP address preservation indicator | O | Indication that UE IP address preservation is requested | + +##### 16.3.2.2.4 Network slice adaptation notification trigger response + +Table 16.3.2.2.4-1 describes the information flow of network slice adaptation notification trigger response from the NSCE server to the NSCE client and optionally to the VAL client. + +**Table 16.3.2.2.4-1: Network slice adaptation notification trigger response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| Result | M | Result includes success or failure of the network slice adaptation. | + +#### 16.3.2.2.X Network slice adaptation subscription request + +Table 16.3.2.2.X-1 describes the information flow of network slice adaptation subscription request from the NSCE client to the NSCE server. + +**Table 16.3.2.2.X-1: Network slice adaptation subscription request** + +| Information element | Status | Description | +|-----------------------------|--------|---------------------------------------------------------------------------------------------------------------------| +| VAL UE ID(s) | M | The VAL UE ID(s) within the VAL service, for which the network slice adaptation subscription applies | +| VAL service ID | M | The VAL service ID of the VAL application for which the network slice adaptation subscription corresponds to. | +| S-NSSAI | M | Indication of the applicable S-NSSAI. | +| DNN | O | Indication of the applicable DNN. | +| Notification Target Address | M | The Notification Target Address (e.g., URL) where the notifications destined for the NSCE client should be sent to. | + +##### 16.3.2.2.X Network slice adaptation subscription response + +Table 16.3.2.2.X-1 describes the information flow of network slice adaptation subscription response from the NSCE server to the NSCE client. + +**Table 16.3.2.2.X-1: Network slice adaptation subscription response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Successful response | O | Indicates that the subscription request was successful. | +| > Subscription ID | M | Subscription identifier corresponding to the subscription. | +| > Expiration time | O | Indicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time. | +| Failure response | O | Indicates that the subscription request failed. | +| > Cause | O | Indicates the cause of subscription request failure | + +##### 16.3.2.2.X Network slice adaptation notification + +Table 16.3.2.2.X-1 describes the information flow of network slice adaptation notification from the NSCE server to the NSCE client. + +**Table 16.3.2.2.X-1: Network slice adaptation notification** + +| Information element | Status | Description | +|--------------------------------------|--------|-------------------------------------------------------------------------------------| +| Subscription ID | M | Subscription identifier corresponding to the subscription. | +| Network slice adaptation information | M | Information regarding the type of network slice adaptation event that has occurred. | + +\*\*\* End of TS 23.434 v. 18.0.0 Enhancements \*\*\* + +### 6.15.2 Solution evaluation + +The solution addresses key issue #1. The solution provides enhancements to the existing NSCE client functionality by separating the network slice adaptation subscription/notification functionality from the slice adaption triggering. This enables an NSCE client to subscribe and receive network slice adaptation notifications from a NSCE server independent of issuing a network slice adaptation trigger request to the NSCE server. The solution also addresses the open issue on enhancements needed to the information to be provided in the UE triggered network slice adaptation procedure. These enhancements enable the NSCE server to receive location requirements, schedule time window requirements and access type within the network slice adaptation request sent from the NSCE client to NSCE server. This enables the NSCE server to provide this information within the AF-driven URSP guidance requests it sends to PCF. + +## 6.16 Solution 16: Multi-Network slice management capability + +### 6.16.1 Solution description + +#### 6.16.1.1 General + +This solution aims to address the issues identified in Key Issue 1. + +This solution provides a possible procedure to illustrate the process of the VAL server requesting to manage network slice from multi-networks (e.g. the PNI-NPN network and PLMN network) through NSCE server. This solution enables the trusted third-party AF to manage its own PNI-NPN (public network integrated non-public network) and its private slice(s) in the PLMN in a combined manner as specified in clause 6.10.2 of 3GPP TS 22.261 [7]. In the case that communication services of a PNI-NPN is extended through a PLMN (e.g. the service is supported by a slice in the PNI-NPN and a slice in the PLMN) as described in clause 6.1.2.4 of 3GPP TS 22.261 [7], the NSCE server can make the performance monitoring and analysis for dedicated service from multiple networks and offer consolidated service performance report to trusted third-party AF. + +#### 6.16.1.2 Multi-Network slice management capability + +Figure 6.16.1.2-1 illustrates the slice management process to address the key issue 1 described in clause 5.1. + +Pre-conditions: + +1. The network slice enabler layer is capable to interact with both PNI-NPN and PLMN 5GC or OAM system. +2. PNI-NPNs are deployed as network slices of the PLMN. + +![Sequence diagram of Network slice application QoS monitoring process. Lifelines: VAL UE (NSCE Client), PLMN Domain (5GS, NSCE Server), PNI-NPN1, PNI-NPN2, NSCE Server, VAL server. The process involves 8 steps: 1. Service QoS monitoring report exposure Request from VAL server to NSCE Server; 2. Request authentication and authorization from NSCE Server; 3. Retrieve PNI-NPN slice performance data from PNI-NPN1 and PNI-NPN2; 4. Retrieve PLMN slice performance data from 5GS; 5. UE QoE monitoring data exposure Request from NSCE Server to NSCE Client; 6. UE QoE monitoring data exposure Response from NSCE Client to NSCE Server; 7. Performance data verification and consolidation analysis from NSCE Server; 8. Slice QoS monitoring report exposure Response from NSCE Server to VAL server.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant VAL_UE as VAL UE (NSCE Client) + subgraph PLMN_Domain [PLMN Domain] + participant 5GS + participant NSCE_Server_PLMN as NSCE Server + end + participant PNI_NPN1 as PNI-NPN1 + participant PNI_NPN2 as PNI-NPN2 + participant NSCE_Server as NSCE Server + participant VAL_server as VAL server + + Note right of VAL_server: 1. Service QoS monitoring report exposure Request + VAL_server->>NSCE_Server: 1. Service QoS monitoring report exposure Request + Note right of NSCE_Server: 2. Request authentication and authorization + NSCE_Server-->>VAL_server: 2. Request authentication and authorization + Note right of NSCE_Server: 3. Retrieve PNI-NPN slice performance data + NSCE_Server->>PNI_NPN1: 3. Retrieve PNI-NPN slice performance data + NSCE_Server->>PNI_NPN2: 3. Retrieve PNI-NPN slice performance data + Note right of NSCE_Server: 4. Retrieve PLMN slice performance data + NSCE_Server->>5GS: 4. Retrieve PLMN slice performance data + Note right of NSCE_Server: 5. UE QoE monitoring data exposure Request + NSCE_Server->>VAL_UE: 5. UE QoE monitoring data exposure Request + Note right of VAL_UE: 6. UE QoE monitoring data exposure Response + VAL_UE-->>NSCE_Server: 6. UE QoE monitoring data exposure Response + Note right of NSCE_Server: 7. Performance data verification and consolidation analysis + NSCE_Server-->>VAL_server: 7. Performance data verification and consolidation analysis + Note right of NSCE_Server: 8. Slice QoS monitoring report exposure Response + NSCE_Server-->>VAL_server: 8. Slice QoS monitoring report exposure Response + +``` + +Sequence diagram of Network slice application QoS monitoring process. Lifelines: VAL UE (NSCE Client), PLMN Domain (5GS, NSCE Server), PNI-NPN1, PNI-NPN2, NSCE Server, VAL server. The process involves 8 steps: 1. Service QoS monitoring report exposure Request from VAL server to NSCE Server; 2. Request authentication and authorization from NSCE Server; 3. Retrieve PNI-NPN slice performance data from PNI-NPN1 and PNI-NPN2; 4. Retrieve PLMN slice performance data from 5GS; 5. UE QoE monitoring data exposure Request from NSCE Server to NSCE Client; 6. UE QoE monitoring data exposure Response from NSCE Client to NSCE Server; 7. Performance data verification and consolidation analysis from NSCE Server; 8. Slice QoS monitoring report exposure Response from NSCE Server to VAL server. + +**Figure 6.16.1.2-1: Network slice application QoS monitoring process** + +1. The VAL server initiates service QoS monitoring report exposure request towards the NSCE server. The request includes VAL server ID, application ID, Network ID. The message also includes application key performance indicator (such as end-to-end delay, throughput, QoE data from UE, etc.) list, monitoring period and monitoring zone. +2. Upon receiving the request from the VAL server to manage the network slice QoS monitoring report, the NSCE server makes authentication and authorization of the VAL server and if VAL server is not authorized, the NSCE server replies with failure response. +3. The NSCE server makes mapping from application ID that received from VAL server to slice identities (S-NSSAIs allocated in each network) and retrieves the network slice related status information from PNI-NPN networks, such as performance measurements in TS 28.552 [12] and analytics data as specified in 3GPP TS 28.104 [15]. +4. The NSCE server retrieves the network slice related performance information from PLMN 5GC networks (e.g. NWDAF) or OAM. For OAM system, the services defined in clause 11.3 of TS 28.532 [8] and clause 5 of TS 28.552 [12] can be utilized. For CN functions, the services of Nnwdaf\_AnalyticsInfo service defined in clause 7.3 of TS 23.288 [17], performance measurements in TS 28.552 [12] and analytics data as specified in 3GPP TS 28.104 [15] can be utilized. The PLMN operator can choose to deploy NSCE-Server acting as the entry of PLMN capability exposure which can be optional. +5. The NSCE server sends Service QoE data request to NSCE clients in monitoring zone which includes application ID to request the QoE data of specific application. +6. The NSCE client sends the requested QoE data (e.g. MOS, stalling ratios, etc.) response to NSCE server. + +NOTE 1: In step 5 and step 6, the NSCE client may need to retrieve information from VAL client that is out of scope of the present document. + +7. The NSCE server verifies and analyses performance data of network slice instance that received from both PNI-NPN and PLMN networks as well as QoE data provided by VAL client, then NSCE server make consolidation performance report for specific application among different kinds of networks in specific period of time/location zone. + +8. The NSCE server sends the network slice QoS monitoring response towards VAL server. + +### 6.16.2 Solution evaluation + +This solution addresses the KI #1 by providing a procedure of performance monitoring and analysis for dedicated service from multiple networks by the NSCE server, to help the trusted third-party AF to manage its own PNI-NPN (public network integrated non-public network) and its private slice(s) in the PLMN in a combined manner. This solution has no impact on the 5GS architecture, and it may require the interactions between NSCE servers to retrieve the network slice related status information. + +The APIs over NSCE-S interface to be defined in normative phase: + +1. APIs of network slice resource optimization request and response. + +## 6.17 Solution 17: Multi-Network slice resource optimization + +### 6.17.1 Solution description + +#### 6.17.1.1 General + +This solution aims to address the issues identified in Key Issue#1 and Key Issue#1. + +This solution provides a possible procedure to illustrate the process of the VAL server requesting to manage network slice from multi-networks (e.g. the PNI-NPN network and PLMN network) through NSCE server. This solution enables the trusted third-party AF to manage its own PNI-NPN (public network integrated non-public network) and its private slice(s) in the PLMN in a combined manner as specified in clause 6.10.2 of 3GPP TS 22.261 [7]. In the case that communication services of a PNI-NPN is extended through a PLMN (e.g. the service is supported by a slice in the PNI-NPN and a slice in the PLMN) as described in clause 6.1.2.4 of 3GPP TS 22.261 [7], the NSCE server can monitor the slice usage status of multiple networks and make resource adjustment between different networks to realize optimized and efficient resource usage among slices of multiple networks. + +#### 6.17.1.2 Multi-Network slice management capability + +Figure 6.17.1.2-1 illustrates the slice management process to address the key issue 1 described in clause 5.1. + +Pre-conditions: + +1. The network slice enabler layer is capable to interact with both PNI-NPN and PLMN 5GC or OAM system. +2. PNI-NPNs are deployed as network slices of the PLMN. + +![Sequence diagram of Network slice application resource optimization process. Lifelines: 5GS, NSCE Server (within PLMN Domain), PNI-NPN1, PNI-NPN2, NSCE Server, and VAL server. The process involves a request from VAL server to NSCE Server, authentication, status data retrieval from PNI-NPN and PLMN networks, analysis, and subsequent LCM requests to PNI-NPN and PLMN networks, ending with a response to the VAL server.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant VAL_server as VAL server + participant NSCE_Server_1 as NSCE Server + participant PNI_NPN1 as PNI-NPN1 + participant PNI_NPN2 as PNI-NPN2 + participant NSCE_Server_2 as NSCE Server + subgraph PLMN_Domain [PLMN Domain] + participant 5GS + participant NSCE_Server_3 as NSCE Server + end + + Note right of VAL_server: 1. Slice resource optimization Request + VAL_server->>NSCE_Server_1: 1. Slice resource optimization Request + Note right of NSCE_Server_1: 2. Request authentication and authorization + NSCE_Server_1->>NSCE_Server_2: 2. Request authentication and authorization + Note right of NSCE_Server_2: 3. Retrieve PNI-NPN slice Status data + NSCE_Server_2->>PNI_NPN1: 3. Retrieve PNI-NPN slice Status data + NSCE_Server_2->>PNI_NPN2: 3. Retrieve PNI-NPN slice Status data + Note right of NSCE_Server_2: 4. Retrieve PLMN slice status data + NSCE_Server_2->>5GS: 4. Retrieve PLMN slice status data + NSCE_Server_2->>NSCE_Server_3: 4. Retrieve PLMN slice status data + Note right of NSCE_Server_2: 5. Data verification and optimization analysis + NSCE_Server_2->>NSCE_Server_2: 5. Data verification and optimization analysis + Note right of NSCE_Server_2: 6. Slice LCM (ModifyNsi) Request + NSCE_Server_2->>PNI_NPN1: 6. Slice LCM (ModifyNsi) Request + Note right of PNI_NPN1: 7. Slice LCM (ModifyNsi) Response + PNI_NPN1->>NSCE_Server_2: 7. Slice LCM (ModifyNsi) Response + Note right of NSCE_Server_2: 8. Slice LCM (ModifyNsi) Request + NSCE_Server_2->>5GS: 8. Slice LCM (ModifyNsi) Request + Note right of 5GS: 9. Slice LCM (ModifyNsi) Response + 5GS->>NSCE_Server_2: 9. Slice LCM (ModifyNsi) Response + Note right of NSCE_Server_2: 10. Slice resource optimization Responset + NSCE_Server_2->>VAL_server: 10. Slice resource optimization Responset + +``` + +Sequence diagram of Network slice application resource optimization process. Lifelines: 5GS, NSCE Server (within PLMN Domain), PNI-NPN1, PNI-NPN2, NSCE Server, and VAL server. The process involves a request from VAL server to NSCE Server, authentication, status data retrieval from PNI-NPN and PLMN networks, analysis, and subsequent LCM requests to PNI-NPN and PLMN networks, ending with a response to the VAL server. + +**Figure 6.17.1.2-1 Network slice application resource optimization process** + +1. The VAL server initiates network slice resource optimization request towards the NSCE server. The request includes VAL server ID, application ID, Network ID. The message also includes preferred optimization zone. +2. Upon receiving the request from the VAL server to make the network slice resource optimization, the NSCE server makes authentication and authorization of the VAL server and if VAL server is not authorized, the NSCE server replies with failure response. +3. The NSCE server makes mapping from application ID that received from VAL server to slice identities (S-NSSAIs allocated in multiple networks) and retrieves the network slice related status information from 5GC or OAM of PNI-NPN networks, such as NF(s) load in 5GC and network utilization in access network as defined in TS 28.535 [11]. +4. The NSCE server retrieves the network slice related status information from PLMN networks from 5GC or OAM of PLMN networks, such as NF(s) load in 5GC and network utilization in access network as defined in TS 28.535 [11]. The PLMN operator can choose to deploy NSCE-Server acting as single entry of PLMN capability exposure which can be optional. +5. The NSCE server verifies and analyses status data of network slice instance that received from both PNI-NPN and PLMN networks as well as network slice QoS monitoring response (optional), then NSCE server makes resource optimization decision among different kinds of networks in specific location zone. +- 6-7. The NSCE server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s), such as modifyNsi request as specified in TS 28.531 [5] to PNI-NPN network. Based on decision made by NSCE server, the network slice management entity (such as NSMF) performs the corresponding operation(s). +- 8-9. The NSCE server determines whether and what network slice LCM operations should be taken and makes the decision(s)/recommendation(s), such as modifyNsi request as specified in TS 28.531 [5] to PLMN network. Based on decision made by NSCE server, the network slice management entity (such as NSMF) performs the corresponding operation(s). The PLMN operator can choose to deploy NSCE-S acting as single entry of PLMN capability exposure which can be optional. +10. The NSCE server sends the network slice resource optimization response towards VAL server. + +### 6.17.2 Solution evaluation + +This solution addresses the KI #1 by providing a network slice resource optimization procedure to enable the NSCE server making multiple networks resource adjustment by utilizing the network slice related management services. This solution has no impact on the 5GS architecture, and it may require the interactions between NSCE servers to retrieves the network slice related status information. + +The APIs over NSCE-S interface to be defined in normative phase: + +1. APIs of network slice resource optimization request and response. + +## 6.18 Solution 18: Network Slice Information Delivery + +### 6.18.1 Solution description + +#### 6.18.1.1 General + +This solution aims to address the issues identified in Key Issue 13. + +The NSCE layer provides the feature of Network Slice information delivery. The Network Slice information is necessary for the VAL server to manage the network slice for their service such as preparation, creation, activation and termination (tear-down) of network slice. + +The Network Slice information that is delivered to the VAL server depends upon network operator policy. The network slice capabilities and management options offered to the customer are determined by a business agreement prior to and outside of the scope of 3GPP standards. + +In initial phase of Network slice Lifecycle, the network slice is defined by Network Slice Provider (NSP). When the Network Slice is defined, the NSP with 5G system may create Network Slice Service Profile with the appropriate values, which characterize the network slice. It refers to the Generic Network Slice Template (GST) and Network Slice Type (NEST) which are standardized by 3GPP, GSMA and is called S-NEST. In addition, the NEST can be defined specifically by NSP itself, which is called P-NEST. According to NSP's policy, the Network Slice Information can be derived from the information in Network Slice - ServiceProfile. + +The VAL server needs to know which the characterized Network Slice service types and capabilities it is authorized to use. The VAL server retrieves authorized Network Slice information defined by NSP (e.g., S-NEST, P-NEST) from the NSCE server. + +The NSCE layer performs the below. + +- Retrieval of Network Slice ServiceProfile in 5GS (e.g., NSMF) as specified in TS 28.532[8] +- Conversion of Network Slice ServiceProfile (specified in TS 28.541) to Network Slice Information +- Creation of Network Slice Information +- Storing of Network Slice Information +- Delivery of Network Slice Information to VAL server that the Network Slice Customer is authorized to use. + +NOTE: The Network Slice Information provided to the VAL server depends on service agreements + +The VAL server as a Network Slice consumer makes use of the delivered Network Slice information for the Network Slice Lifecycle management for its service. + +#### 6.18.1.2 Network Slice Information delivery + +This subclause depicts the procedure of the Network Slice Information delivery to the VAL server via NSCE layer, when the VAL server requests the Network Slice Information after registration. + +NOTE: The Network Slice Information provided to the VAL server depends on service agreements out of the scope of 3GPP. + +Pre-condition + +1. The NSCE server should have the agreement with MNO (NOP) for retrieval of ServiceProfile, if the NSCE server is the external entity. + +![Sequence diagram illustrating Network Slice Information delivery. Lifelines: VAL Server, NSCE server, and 5GS. The sequence starts with the NSCE server sending a '1. NS ServiceProfile Retrieval' message to the 5GS. The 5GS responds with '2. NS Information Compose & Store' to the NSCE server. The VAL Server then sends a '3. NS Info. Request' to the NSCE server. The NSCE server performs '4. Authorization' and finally sends a '5. NS Info. Response' back to the VAL Server.](8bd7adf738ea4b7e65e0d6f67e122d55_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS + Note right of NSCE server: 1. NS ServiceProfile Retrieval + NSCE server->>5GS: 1. NS ServiceProfile Retrieval + 5GS-->>NSCE server: 2. NS Information Compose & Store + Note right of NSCE server: 2. NS Information Compose & Store + VAL Server->>NSCE server: 3. NS Info. Request + Note right of NSCE server: 4. Authorization + NSCE server-->>VAL Server: 5. NS Info. Response + +``` + +Sequence diagram illustrating Network Slice Information delivery. Lifelines: VAL Server, NSCE server, and 5GS. The sequence starts with the NSCE server sending a '1. NS ServiceProfile Retrieval' message to the 5GS. The 5GS responds with '2. NS Information Compose & Store' to the NSCE server. The VAL Server then sends a '3. NS Info. Request' to the NSCE server. The NSCE server performs '4. Authorization' and finally sends a '5. NS Info. Response' back to the VAL Server. + +**Figure 6.18.1.2-1: Network Slice Information delivery** + +1. The NSCE server retrieves the Network Slice ServiceProfile from 5GS (e.g., NSMF) when the NSCE server acting as a NSP prepares a Network Slice to be provided. The NSCE server follows the procedure to request/receive the Network Slice Service Profile with 'getMOIAttributes' operation as specified in TS 28.532[8]. + +NOTE: If NSCE server and NSMF are in same operator, then the NSCE server gets access directly to NSMF. The delivered Network Slice Service Profile contains the values of attributes such as PLMN, S-NSSAI, SST, maximum number of UEs, maximum number of PDU sessions, Coverage Area, Latency, Data volume, etc which specify the Network Slice characteristics, as specified in clause of ServiceProfile in TS 28.541. + +2. The NSCE server, as Network Slice as a Service, creates and stores the Network Slice information. When NSCE server retrieves the Network Slice Information, it is necessary for NSCE server to convert the attributes in Network Slice ServiceProfile to the Network Slice information for readable information and to compose the Network Slice information, according to the NSP's policy. + +In order to reduce to request often the Network Slice Information Retrieval, the NSCE server stores the Network Slice information. + +3. The VAL server requests the Network Slice Information to the NSCE server. If the VAL server needs to know the specific attribute value for its service, then the attribute name of Network Slice (e.g., S-NSSAI, SST, Coverage Area, etc.) can be added in the Request message. + +4. The NSCE server performs to check whether the requesting VAL server is registered or not. The NSCE server identifies which the Network Slice Customer is authorized to use. +5. The NSCE server sends the Network Slice Information, if the VAL server is registered and authorized. The NSCE server rejects to the request of the Network Slice Information, if not registered. + +#### 6.18.1.3 Network Slice Information subscription + +This subclause depicts the procedure of the Network Slice Information delivery to the VAL server via NSCE layer, when the VAL server subscribes to the Network Slice Information after registration. + +The Network Slice information that is delivered to the VAL server depends upon network operator policy. The network slice capabilities and management options offered to the customer are determined by a business agreement prior to and outside of the scope of 3GPP standards. + +![Sequence diagram for Network Slice Information subscription. Lifelines: VAL Server, NSCE server, 5GS. The sequence starts with the NSCE server sending a '1. NS ServiceProfile Retrieval' message to the 5GS. The 5GS responds with '2. NS Information Compose & Store' to the NSCE server. The VAL Server then sends a '3. NS Info. Subscribe request' to the NSCE server. The NSCE server performs '4. Authorization' and finally sends a '5. NS Info. Subscribe Response' back to the VAL Server.](9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS + Note right of NSCE server: 1. NS ServiceProfile Retrieval + NSCE server->>5GS: 1. NS ServiceProfile Retrieval + 5GS-->>NSCE server: 2. NS Information Compose & Store + VAL Server->>NSCE server: 3. NS Info. Subscribe request + Note right of NSCE server: 4. Authorization + NSCE server-->>VAL Server: 5. NS Info. Subscribe Response + +``` + +Sequence diagram for Network Slice Information subscription. Lifelines: VAL Server, NSCE server, 5GS. The sequence starts with the NSCE server sending a '1. NS ServiceProfile Retrieval' message to the 5GS. The 5GS responds with '2. NS Information Compose & Store' to the NSCE server. The VAL Server then sends a '3. NS Info. Subscribe request' to the NSCE server. The NSCE server performs '4. Authorization' and finally sends a '5. NS Info. Subscribe Response' back to the VAL Server. + +**Figure 6.18.1.3-1: Network Slice Information subscription** + +1. The NSCE server retrieves Network Slice ServiceProfile from 5GS (e.g., NSMF). The NSCE server follows the procedure to request/receive the Network Slice Service Profile with 'getMOIAttributes' operation as specified in TS 28.532[8]. + +NOTE: If NSCE server and NSMF are in same operator, then the NSCE server gets access directly to NSMF. The delivered Network Slice Service Profile contains the values of attributes such as PLMN, S-NSSAI, SST, maximum number of UEs, maximum number of PDU sessions, Coverage Area, Latency, Data volume, etc which specify the Network Slice characteristics, as specified in clause of ServiceProfile in TS 28.541. + +2. The NSCE server, as Network Slice as a Service, creates and stores the Network Slice information. When NSCE server retrieves the Network Slice Information, it is necessary for NSCE server to convert the attributes in Network Slice ServiceProfile to the Network Slice information for readable information and to compose the Network Slice information, according to the NSP's policy. + +In order to reduce to request often the Network Slice ServiceProfile Retrieval, the NSCE server stores the Network Slice information. + +3. The VAL server subscribes to the Network Slice Information in the NSCE server. If the VAL server needs to know the specific attribute value for its service, then the attribute name of Network Slice Information can be added in the Subscription message. + +4. The NSCE server performs to check whether the requesting VAL server is registered or not. The NSCE server identifies which Network Slice Information the Network Slice Customer is authorized to use. +5. The NSCE server sends the authorized Network Slice Information, if the VAL server is registered. The NSCE server rejects to the request of the Network Slice Information, if not registered. + +Whenever NSCE server performs the Network Slice Information Retrieval and receives the updated values to the attributes of Network Slice Service Profile, the updated Network Slice information will be notified to the VAL server, if the NSC is authorized to receive this information. + +#### 6.18.1.4 Network Slice Information Notify + +This subclause depicts the procedure of the Network Slice Information delivery to the VAL server via NSCE layer, in case the NSCE server notifies the Network Slice Information after subscription. The notification occurs whenever the Network Slice information is updated. + +Pre-conditions: + +1. The NSCE server performs to retrieve the Network Slice Information from 5GS (e.g., NSMF). The NSCE server follows the procedure to request/receive the Network Slice Service Profile with 'subscription' operation as specified in TS 28.532[8]. + +The delivered Network Slice Service Profile contains the values of attributes such as PLMNInfoList, S-NSSAI, SST, maximum number of UEs, maximum number of PDU sessions, Coverage Area, Latency, Data volume, etc which specify the Network Slice characteristics, as specified in clause of ServiceProfile in TS 28.541. + +2. When NSCE server retrieves the Network Slice ServiceProfile from 5GS (e.g., NSMF), it is necessary for NSCE server to convert the attributes in Network Slice ServiceProfile to the Network Slice information for readable information and to compose the Network Slice information, according to the NSP's policy. + +In order to reduce to request often the Network Slice Information Retrieval, the NSCE server stores the Network Slice information. + +3. The VAL server subscribes to the Network Slice Information to the NSCE server. + +NOTE: Network Slice Provider may define the scope and condition for notification of Network Slice information to the 3rd party. + +![Sequence diagram for Network Slice Information Notify. Lifelines: VAL Server, NSCE server, 5GS. The sequence starts with NSCE server and 5GS performing 'NS ServiceProfile Retrieval'. Then NSCE server performs 'NS Information Compose & Store'. Next, VAL Server and NSCE server exchange 'NS Info Subscription Request/Response'. From 5GS to NSCE server, message '1. ServiceProfile update' is sent. Then NSCE server performs '2. NS Information Update'. Finally, NSCE server sends '3. NS Info. Notify' to VAL Server.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS + Note right of NSCE server: NS ServiceProfile Retrieval + Note right of NSCE server: NS Information Compose & Store + VAL Server->>NSCE server: NS Info Subscription Request/Response + Note right of NSCE server: 1. ServiceProfile update + Note right of NSCE server: 2. NS Information Update + NSCE server->>VAL Server: 3. NS Info. Notify + +``` + +Sequence diagram for Network Slice Information Notify. Lifelines: VAL Server, NSCE server, 5GS. The sequence starts with NSCE server and 5GS performing 'NS ServiceProfile Retrieval'. Then NSCE server performs 'NS Information Compose & Store'. Next, VAL Server and NSCE server exchange 'NS Info Subscription Request/Response'. From 5GS to NSCE server, message '1. ServiceProfile update' is sent. Then NSCE server performs '2. NS Information Update'. Finally, NSCE server sends '3. NS Info. Notify' to VAL Server. + +**Figure 6.18.1.4-1: Network Slice Information Notify** + +1. The NSCE server receives the Network Slice Service Profile from 5GS (e.g., NSMF) as a result of subscription of Network Slice Service Profile as specified in TS 28.531. + +NOTE: If NSCE server and NSMF are in same operator, then the NSCE server gets access directly to NSMF. The delivered Network Slice Service Profile contains the values of attributes such as ServiceProfileID, PLMNInfoList, S-NSSAI, SST, maximum number of UEs, maximum number of PDU sessions, Coverage Area, Latency, Data volume, etc which specify the Network Slice characteristics, as specified in clause of ServiceProfile in TS 28.541. + +When NSCE server receives the Network Slice ServiceProfile, it is necessary for NSCE server to convert the attributes in Network Slice ServiceProfile to the Network Slice information for readable information. + +2. The NSCE server updates the Network Slice information. +3. The NSCE server sends the updated Network Slice Information to the subscribed VAL servers, such as PLMNInfoList, S-NSSAI, SST, SliceQoS, UE density and so on. + +#### 6.18.1.5 Network Slice Information delivery while registration + +This subclause depicts the procedure of the Network Slice Information delivery to the VAL server via NSCE layer, when the VAL server registers to the NSCE server. + +Pre-conditions: + +1. The NSCE server performs to retrieve the Network Slice ServiceProfile from 5GS (e.g., NSMF). The NSCE server follows the procedure to request/receive the Network Slice Service Profile with 'getMOIAttributes' operation as specified in TS 28.532[8]. + +NOTE: If NSCE server and NSMF are in same operator, then the NSCE server gets access directly to NSMF. + +The delivered Network Slice Service Profile contains the values of attributes such as PLMN, S-NSSAI, SST, maximum number of UEs, maximum number of PDU sessions, Coverage Area, Latency, Data volume, etc which specify the Network Slice characteristics, as specified in clause of ServiceProfile in TS 28.541. + +2. When NSCE server retrieves the Network Slice ServiceProfile, it is necessary for NSCE server to convert the attributes in Network Slice ServiceProfile to the Network Slice Information for readable information and to compose the Network Slice information according to the NSP's policy. + +In order to reduce to request often the Network Slice Information Retrieval, the NSCE server stores the Network Slice information. + +![Sequence diagram showing Network Slice Information delivery while registration. Lifelines: VAL Server, NSCE server, 5GS. The process involves: 1. VAL Server sends a Registration Request with NS Info request indicator to NSCE server. 2. NSCE server performs a Registration check. 3. NSCE server sends a Registration Response with NS Info to VAL Server. Internal steps on the NSCE server include NS ServiceProfile Retrieval and NS Information Compose & Store.](74d23510f27b21403a7be84820821863_img.jpg) + +``` +sequenceDiagram + participant VAL Server + participant NSCE server + participant 5GS + Note right of NSCE server: NS ServiceProfile Retrieval + Note right of NSCE server: NS Information Compose & Store + VAL Server->>NSCE server: 1. Registration Request with NS Info request indicator + NSCE server->>NSCE server: 2. Registration check + NSCE server->>VAL Server: 3. Registration Response with NS Info +``` + +Sequence diagram showing Network Slice Information delivery while registration. Lifelines: VAL Server, NSCE server, 5GS. The process involves: 1. VAL Server sends a Registration Request with NS Info request indicator to NSCE server. 2. NSCE server performs a Registration check. 3. NSCE server sends a Registration Response with NS Info to VAL Server. Internal steps on the NSCE server include NS ServiceProfile Retrieval and NS Information Compose & Store. + +**Figure 6.18.1.5-1: Network Slice Information delivery while registration** + +1. The VAL server requests to register to the NSCE server with the indicator of the Network Slice information request, if necessary. +2. The NSCE server performs the registration check as specified in clause 6.7 Solution 7: network slice capability registration. +3. The NSCE server sends the Network Slice information (e.g., PLMNInfoList, S-NSSAI, SST, SliceQoS, UE density and so on), which corresponds to the indicator of the Network Slice information, in the Registration Response message if the Registration is accepted. + +### 6.18.2 Solution evaluation + +The proposed solution addresses the KI #13 on Network Slice Information delivery. + +The solution provides the procedure for NSCE server to operate the Network Slice information delivery to the VAL server. This allows the NSCE layer to interact with both 5GS MnS and the VAL server for retrieval of Network Slice ServiceProfile and for delivery of Network Slice information. This solution makes use of the operation of 5GS MnS defined in SA5 for retrieval of Network Slice Service Profile. The Network slice information can be delivered to the VAL server with various ways according to the deployment + +The solution is feasible and viable for NSaaS scenario when the VAL server needs to be informed on the Network Slice information. The APIs of the NSCE server capabilities expect to be defined for the Network Slice Information delivery to the VAL server in the normative phase. + +## 6.19 Solution 19: Slice requirements alignment capability + +### 6.19.1 Solution description + +#### 6.19.1.1 General + +This solution aims to address the issue identified in Key Issue 11 of slice requirement alignment. + +This solution provides a procedure to illustrate slice requirements alignment capability by the network slice capability enablement server in case that the initial slice requirements are not configured properly or the slice requirements need modifications to meet the adjusted service requirements. + +To enable the VAL server to configure the optimal slice requirements parameters to align with the real vertical needs, the NSCE layer is able to monitor the network performance statistics and to evaluate whether the current slice requirements parameters are reasonable to achieve the maximum return of investment. To enable the slice/service self-management, the NSCE server may have the capability to generate and configure more reasonable slice requirements parameters. To avoid frequently reconfiguration of network slice requirements, the action of alignment is triggered by the evaluation of network performance statistics during a certain time period but not by a single event. + +#### 6.19.1.2 Slice requirements alignment capability + +Figure 6.19.1.2-1 provides a possible procedure of slice parameters alignment to address the key issue 11 described in clause 5.11. + +Pre-conditions: + +1. The VAL Server has subscribed to the slice requirements alignment capability +2. The NSCE Server has subscribed to the service of network slice performance management provided by EGMF. +3. The NSCE server has subscribed to the service of network slice provisioning provided by EGMF. + +![Sequence diagram of the slice requirements alignment process between VAL Server, NSCE Server, and EGMF.](ef8f4838401ece0abd51d63b897fa388_img.jpg) + +``` +sequenceDiagram + participant VAL Server + participant NSCE Server + participant EGMF + Note right of NSCE Server: 2. authorization + Note right of NSCE Server: 4. Retrieve KPI and performance data from OAM system + Note right of NSCE Server: 5. Slice requirements update + Note right of NSCE Server: 6. Network Slice Modification(Slice Requirements modification) + VAL Server->>NSCE Server: 1.Slice requirements alignment request + NSCE Server-->>VAL Server: 3.Slice requirements alignment response + NSCE Server->>EGMF: 4.Retrieve KPI and performance data from OAM system + NSCE Server-->>NSCE Server: 5. Slice requirements update + NSCE Server->>EGMF: 6. Network Slice Modification(Slice Requirements modification) + NSCE Server-->>VAL Server: 7. Notification of the updated slice requirements +``` + +The diagram illustrates the slice requirements alignment process involving three main entities: VAL Server, NSCE Server, and EGMF. The sequence of interactions is as follows: 1. The VAL Server sends a 'Slice requirements alignment request' to the NSCE Server. 2. The NSCE Server performs an 'authorization' step. 3. The NSCE Server sends a 'Slice requirements alignment response' back to the VAL Server. 4. The NSCE Server sends a 'Retrieve KPI and performance data from OAM system' request to the EGMF. 5. The NSCE Server performs a 'Slice requirements update' step. 6. The NSCE Server sends a 'Network Slice Modification(Slice Requirements modification)' request to the EGMF. 7. Finally, the NSCE Server sends a 'Notification of the updated slice requirements' to the VAL Server. + +Sequence diagram of the slice requirements alignment process between VAL Server, NSCE Server, and EGMF. + +Figure 6.19.1.2-1: Slice requirements alignment process + +1. The VAL server sends a slice requirements alignment request to NSCE server to require the NSCE server to check whether the slice requirements (by configuring the attributes of *serviceProfile*) matches the real network slice usage status, the request may include the S-NSSAI, the ID of the VAL server, the slice requirements parameters (attributes of *serviceProfile*) which is requested to be aligned. +2. The NSCE server checks if the VAL server is authorized to trigger the service of slice requirements alignment. +3. The NSCE server response to VAL server with the result of slice requirements alignment request, e.g., the slice requirements alignment request is accepted. +4. On receiving the request from VAL server, NSCE server retrieves the network slice related performance data and KPIs (e.g., the average PRB usage, the distribution of the PRB usage) defined in TS 28.552[12] by utilize performance assurance management services exposed by EGMF. +5. NSCE server compares the slice requirement parameters of network slice (the values of attributes of *serviceProfile*, e.g., radioSpectrum, the maxNumberOfUEs) with network slice performance statistics (e.g., active number of users, the average PRB usage, the distribution of the PRB usage of the S-NSSAI) to generate the optimal slice requirements for the required service (represented by S-NSSAI) of the vertical and determine whether the network slice modification operations should be taken. This step depends on implementation (e.g., if the VAL client experience are satisfied while the network slice resources are with low utilization, the resources required in the slice requirements could be reduced). +6. If NSCE decides to update the slice requirements, the NSCE server performs the network slice modification operation, as defined in clause 7.6, TS 28.531[5] exposed by EGMF defined in SA5, the *serviceProfile* will be re-configured by utilizing the modifyMOIAttributes operation. +7. NSCE server sends the notifications to VAL server to notify the change of the slice requirements parameters. + +### 6.19.2 Solution evaluation + +This solution addresses the key issue #11 of slice requirement alignment. In this solution, the NSCE server interacts with VAL Server and OAM system respectively to compare the slice requirements with network current situations to estimate if the current slice requirements are properly configured. The network situation can be monitored by utilize the performance assurance related management services exposed by EGMF. The alignment of slice requirements is a semi-static operation which is not triggered by a single event but considers the network performance statistics during a certain time period. Besides, this solution has no impact on the actual business arrangement between the third-party and the MNO, which only performs adjustments within the bounds of the actual SLA. + +## 6.20 Solution 20: Network slice optimization based on AF policy + +### 6.20.1 Solution description + +#### 6.20.1.1 General + +This solution aims at providing potential procedures for KI#10. It provides a mechanism to optimize the network slice parameters for the vertical applications (by triggering the slice modification), based on network slice usage patterns and policy of application, e.g., to trigger some slices operation when the pre-configured thresholds are met. + +The AF policy can be in form of a policy profile which contains the listed trigger event and expected action. + +For example, the trigger events can be: + +- Slice load exceeding the threshold (a numeric value or a percentage of the maximum number), +- A specific time period (e.g., summer vacation or spring festival). + +The event list above is not exhaustive list, and just something for information. + +When one or more event(s) are triggered, then network slice optimization operations are expected to be triggered. + +The expected network slice optimization operations could be: + +- Network slice modification for network slice(s), +- Or just sending out the notification. + +Then some examples of policy are: + +- In June, trigger the slice modification to decrease the slice with 10%, with updated network slice related requirement (e.g. maximum number of UEs, latency, and throughput). +- When the max number of PDU sessions is reached, trigger the slice modification to expand with 20% this parameter for slice capacity. +- When the uplink throughput threshold is reached, trigger the slice modification to expand with 20% this parameter. + +According to the trigger event, slice optimization can be triggered by OAM as describe in 6.20.1.2, triggered by NWDAF as describe in 6.20.1.3, or triggered by NSCE server itself as describe in 6.20.1.4. + +#### 6.20.1.2 OAM event triggered network slice optimization + +Figure 6.20.1.2 illustrates the procedure of OAM event triggered Network slice optimization. + +In this clause, the AF policy is triggered by the network slice management data reported from OAM. The measured object is defined in item f) of measurement definitions (3GPP TS 32.404 [23], TS 28.552 [12]) and in item d) of KPI definitions (TS 28.554 [24]). + +The policy in this clause is when the network slice is vertical owned private slice, the vertical request to only activate part of the network slice at the beginning considering the energy saving. Based on the monitored connected UE or established PDU session or Downstream Throughput, more resource could be activated by triggering the modification of uLThptPerSlice/dLThptPerSlice/maximum number of UEs/maximum number of PDU session. + +Pre-conditions: + +1. The NSCE server is authorized to get network slice management data notification from OAM; +2. The VAL server is authorized to the NSCE server for network slice optimization. +3. There is enough network capacity when the expected action is to expand the network slice. +4. The AF policy has been pre-configured on the VAL server based on the agreement with NSCE server which is not conflicts with the SLA. +5. The AF policy has been provided to the NSCE server as specified in clause 6.20.1.5. + +![Sequence diagram illustrating the network slice optimization procedure triggered by OAM. The diagram shows five steps: 1. VAL server sends a 'Network slice optimization service subscription request' to NSCE server. 2. NSCE server sends a 'Network slice management data subscription and notification' to OAM. 3. OAM sends a 'Network slice optimization response' to NSCE server. 4. NSCE server performs 'Slice modification'. 5. NSCE server sends a 'Network slice optimization notify' to VAL server.](472a73112a9b2ed65777d54d33a3ba9c_img.jpg) + +``` +sequenceDiagram + participant VAL server + participant NSCE server + participant OAM + Note left of VAL server: 1. Network slice optimization service subscription request + VAL server->>NSCE server: 1. Network slice optimization service subscription request + Note right of NSCE server: 2. Network slice management data subscription and notification + NSCE server->>OAM: 2. Network slice management data subscription and notification + Note left of VAL server: 3. Network slice optimization response + OAM->>NSCE server: 3. Network slice optimization response + Note right of NSCE server: 4. Slice modification + NSCE server->>NSCE server: 4. Slice modification + Note left of VAL server: 5. Network slice optimization notify + NSCE server->>VAL server: 5. Network slice optimization notify +``` + +Sequence diagram illustrating the network slice optimization procedure triggered by OAM. The diagram shows five steps: 1. VAL server sends a 'Network slice optimization service subscription request' to NSCE server. 2. NSCE server sends a 'Network slice management data subscription and notification' to OAM. 3. OAM sends a 'Network slice optimization response' to NSCE server. 4. NSCE server performs 'Slice modification'. 5. NSCE server sends a 'Network slice optimization notify' to VAL server. + +Figure 6.20.1.2: Network slice optimization triggered by OAM + +1. VAL server sends network slice optimization service subscription request to NSCE server. The request contains the policy ID indicating the OAM based trigger event. The policy in this clause is: When the max number of PDU sessions is reached, trigger the slice modification to expand slice capacity by modify the throughput/maximum number of UEs/maximum number of PDU session. +2. To monitor the trigger event, the NSCE server translates the trigger event to service API(s) with necessary parameter, and subscribe to it by sending network slice management data subscription request to OAM. To get the monitored performance metric, the notifyThresholdCrossing as defined in TS 28.532[8] clause 11.3.1.3 which is filled in with corresponding S-NSSAI in objectInstance could be used. +3. NSCE server sends the network slice optimization response to the VAL server to confirm network slice optimization service subscription. +4. Upon receiving the notification which indicating the trigger event is triggered, the NSCE server performs the expected action which is to trigger the slice modification/slice allocation by sending the modifyNsi/allocateNSI request as specified in TS 28.531 [5] with updated parameter throughput/maximum number of UEs/maximum number of PDU session as specified in the AF policy. The OAM responds back to NSCE server that the requested slice modification was successful or not. + +NOTE 1: The parameters available for modification are based on the agreement with NSCE server. + +NOTE 2: The slice modification could be done by Auto-NS-LCM as defined in clause 6.1. + +5. The NSCE server provides a network slice optimization notification to the VAL server. + +NOTE 3: There is no expectation to have constant and exact mapping between slice configuration parameters and actual traffic load of the same slice. + +#### 6.20.1.3 NWDAF event triggered network slice optimization + +Figure 6.20.1.3 illustrates the procedure of NWDAF event triggered Network slice optimization. + +The policy in this clause is when Network Slice load predictions (Predicted Number of PDU Session establishments at the Network Slice) exceeds the threshold with high confidence, then the OAM needs to be notified to prepare for network slice modification in advance with excepted parameters including the throughput/maximum number of UEs/maximum number of PDU session. + +Pre-conditions: + +1. The NSCE server is authorized to get network slice analytics notification from NWDAF; +2. The VAL server is authorized to the NSCE server for network slice optimization. +3. There is enough network capacity when the expected action is to expand the network slice. +4. The AF policy has been pre-configured on the VAL server based on the agreement with NSCE server which is not conflicts with the SLA. +5. The AF policy has been provided to the NSCE server as specified in clause 6.20.1.5. + +![Sequence diagram illustrating Network slice optimization triggered by NWDAF. The diagram shows five steps: 1. VAL server sends a network slice optimization service subscription request to NSCE server. 2. NSCE server sends an NWDAF event subscribe to 5GC. 3. 5GC sends a network slice optimization response to VAL server. 4. NSCE server sends a slice modification to OAM. 5. NSCE server sends a network slice optimization notification to VAL server.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant 5GC + participant OAM + Note right of NSCE server: 2. NWDAF event subscribe + VAL server->>NSCE server: 1. Network slice optimization service subscription request + NSCE server->>5GC: 2. NWDAF event subscribe + 5GC-->>VAL server: 3. Network slice optimization response + NSCE server->>OAM: 4. Slice modification + NSCE server-->>VAL server: 5. Network slice optimization notification + +``` + +Sequence diagram illustrating Network slice optimization triggered by NWDAF. The diagram shows five steps: 1. VAL server sends a network slice optimization service subscription request to NSCE server. 2. NSCE server sends an NWDAF event subscribe to 5GC. 3. 5GC sends a network slice optimization response to VAL server. 4. NSCE server sends a slice modification to OAM. 5. NSCE server sends a network slice optimization notification to VAL server. + +**Figure 6.20.1.3: Network slice optimization triggered by NWDAF** + +1. VAL server sends network slice optimization service subscription request to NSCE server. The request contains the policy ID indicating the NWDAF based trigger event. The policy in this clause is: when Network Slice load predictions (Predicted Number of PDU Session establishments at the Network Slice) exceeds the threshold with high confidence, then the OAM needs to be notified to prepare for network slice modification in advance with excepted parameters throughput/maximum number of UEs/maximum number of PDU session. +2. To monitor the trigger event, the NSCE server translates the trigger event to service API(s) with necessary parameter, and subscribe to the NWDAF prediction by using the Nnwdaf\_AnalyticsSubscription\_Subscribe or Nnwdaf\_AnalyticsInfo\_Request as defined in TS 23.288[17] clause 6.1.1, and the procedures are defined in TS 23.288[17] clause 6.3.4, and clause 6.8. +3. NSCE server sends the network slice optimization response to the VAL server to confirm network slice optimization service subscription. +4. Upon receiving the notification which indicating the trigger event is triggered, the NSCE server performs the expected action which is to trigger the slice modification by sending the modifyNsi request as specified in TS 28.531 [5] with updated parameter throughput/maximum number of UEs/maximum number of PDU session as specified in the AF policy. The OAM responds back to NSCE server that the requested slice modification was successful or not. +5. The NSCE server provides a network slice optimization notification to the VAL server. + +NOTE 1: The parameters available for modification are based on the agreement with NSCE server. + +NOTE 2: The slice modification could be done by Auto-NS-LCM as defined in clause 6.1. + +5. The NSCE server provides a network slice optimization notification to the VAL server. + +NOTE 3: There is no expectation to have constant and exact mapping between slice configuration parameters and actual traffic load of the same slice. + +#### 6.20.1.4 NSCE server triggered network slice optimization + +Figure 6.20.1.4 illustrates the procedure of NSCE server triggered Network slice optimization. + +The policy in this clause is in June, triggering the slice modification/slice de-allocation to decrease the slice with 10%, with updated network slice capacity by triggering the modification of uLThptPerSlice/dLThptPerSlice/maximum number of UEs/maximum number of PDU session. + +Pre-conditions: + +1. The VAL server is authorized to the NSCE server for network slice optimization. + +2. There is enough network capacity when the expected action is to expand the network slice. +3. The AF policy has been pre-configured on the VAL server based on the agreement with NSCE server which is not conflicts with the SLA. +3. The AF policy has been provided to the NSCE server as specified in clause 6.20.1.5. + +![Sequence diagram for Network slice optimization triggered by NSCE server. Participants: VAL server, NSCE server, 5GC, OAM. 1. VAL server to NSCE server: Network slice optimization service subscription request. 2. NSCE server internal: Network slice optimization trigger event procession. 3. NSCE server to VAL server: Network slice optimization response. 4. NSCE server, 5GC, OAM interaction: Slice optimization. 5. NSCE server to VAL server: Network slice optimization notification.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +``` + +sequenceDiagram + participant VAL as VAL server + participant NSCE as NSCE server + participant 5GC as 5GC + participant OAM as OAM + VAL->>NSCE: 1. Network slice optimization service subscription request + Note over NSCE: 2. Network slice optimization trigger event procession + NSCE-->>VAL: 3. Network slice optimization response + Note over NSCE, OAM: 4. Slice optimization + NSCE-->>VAL: 5. Network slice optimization notification + +``` + +Sequence diagram for Network slice optimization triggered by NSCE server. Participants: VAL server, NSCE server, 5GC, OAM. 1. VAL server to NSCE server: Network slice optimization service subscription request. 2. NSCE server internal: Network slice optimization trigger event procession. 3. NSCE server to VAL server: Network slice optimization response. 4. NSCE server, 5GC, OAM interaction: Slice optimization. 5. NSCE server to VAL server: Network slice optimization notification. + +**Figure 6.20.1.4: Network slice optimization triggered by NSCE server** + +1. VAL server sends network slice optimization service subscription request to NSCE server. The request contains the policy ID indicating the NSCE server based trigger event. +2. The NSCE server translates pre-configured policy to trigger event(s) with necessary parameter, by monitoring the time period and slice usage. +3. NSCE server sends the network slice optimization response to the VAL server to confirm network slice optimization service subscription. +4. Upon the trigger event is triggered, e.g. the arrival at a specific time period (summer vacation, spring festival etc.), the NSCE server takes actions by triggering the slice modification with parameter uLThptPerSlice/dLThptPerSlice/maximum number of UEs/maximum number of PDU session as specified in the AF policy. The OAM responds back to NSCE server that the requested slice modification was successful or not. + +NOTE 1: The parameters available for modification are based on the agreement with NSCE server. + +NOTE 2: The slice modification could be done by Auto-NS-LCM as defined in clause 6.1. + +5. The NSCE server provides a network slice optimization response to the VAL server. + +NOTE 3: There is no expectation to have constant and exact mapping between slice configuration parameters and actual traffic load of the same slice. + +#### 6.20.1.5 AF policy provisioning + +Figure 6.20.1.5 illustrates the procedure of AF policy provisioning from VAL to NSCE server. + +![Sequence diagram for AF policy provisioning. The diagram shows three steps: 1. VAL server sends an AF policy provisioning request to the NSCE server. 2. The NSCE server performs an AF policy check. 3. The NSCE server sends an AF policy provisioning response back to the VAL server.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + Note right of NSCE server: 2. AF policy check + VAL server->>NSCE server: 1. AF policy provisioning request + NSCE server-->>VAL server: 3. AF policy provisioning response + +``` + +Sequence diagram for AF policy provisioning. The diagram shows three steps: 1. VAL server sends an AF policy provisioning request to the NSCE server. 2. The NSCE server performs an AF policy check. 3. The NSCE server sends an AF policy provisioning response back to the VAL server. + +Figure 6.20.1.5: AF policy provisioning + +1. VAL server sends AF policy provisioning request to NSCE server. The request contains the policy, VAL server ID and S-NSSAI. +2. The NSCE server checks whether the policy is conflict with the service profile and other pre-configured policy. If yes, the request could be rejected. +3. NSCE server sends the AF policy provisioning response to the VAL server to indicating whether the request is successful or not. If it is successful, policy ID is provided to VAL server. + +### 6.20.2 Solution evaluation + +The solution addresses the key issue #10. In this solution, the NSCE server optimizes the network slice for the vertical applications based on AF policy. After receiving the policy from AF, the NSCE Server may have interactions with 5GC and OAM system to monitor the network slice, and then trigger the network slice modification by utilize the network slice related management services exposed by EGMF defined in SA5. This solution is based on the capacity supported by SA2 and SA5 and does not introduce impact on 5GS architecture. While the SA6 SEAL will possibly need enhancement to support the interaction with 5GS and OAM system. The APIs interface needs to be defined in normative phase: + +1. APIs of policy/service subscription of network slice modification. +2. APIs to provide the AF policy to NSCE server. + +## 6.21 Solution 21: Solution on predictive slice modification in edge based NSCE deployments + +### 6.21.1 Solution description + +#### 6.21.1.1 General + +The solution addresses the key issue #12 and in particular the open issues: + +- How could the NSCE server deployed inside the EDN interact with the NSCE server outside the EDN? Whether and how could the NSCE server interact with other NSCE server? +- Whether and how does SEAL need to be enhanced to support NSCE client to interact with NSCE server in the EDN and NSCE server outside the EDN? + +This scenario targets mainly deployments where the slice enabler is deployed at the edge and the migration to different DN will require that the ongoing slice is supported at the target area to ensure meeting the application session requirements. The slice parameters monitoring at the target area (e.g. for per NSI/NSSI resource situation) need to be known at the server NSCE server to allow for pro-active slice (or slice subnet) modification trigger to avoid degradation of the application service performance. + +In this procedure, the NSCE server initially receives an expected/predicted UE location/mobility change request outside an EDN service area for one or more UEs within the VAL application session (e.g. such session can be an indirect V2V session or a multiplayer gaming session). Then, service or target NSCE server checks with 5GS (OAM, 5GC) whether the serving slice is available and can offer the same performance at the target EDN. Thereafter, NSCE server evaluates the need for a slice modification (e.g. a slice lifecycle related trigger change) e.g. a slice subnet resource adaptation to allow for optimizing the application performance at the target area. Based on this decision/recommendation, it provides the action to the OAM and supports the re-mapping of NSCE server for the NSCE client proactively, before UE mobility happens. + +#### 6.21.1.1 Procedure + +Figure 6.21.1.2-1 illustrates the solution to Key Issue #12 on network slice capability exposure in the edge data network to allow for slice modification when a vertical application migrates to a different EDN supported by different NSCE server. + +Pre-conditions: + +1. The VAL server has subscribed to the network slice capability enablement server +2. Initially, VAL client of VAL UE is mapped to Slice#1, and NSCE client of VAL UE has established a connection to NSCE server#1 (S-NSCE server). +3. The S-NSCE server has already discovered the T-NSCE server and its area of coverage. + +![Sequence diagram illustrating the support for predictive slice modification in distributed NSCE server deployments. The diagram shows interactions between VAL client, NSCE client, 5GC, S-NSCE server @ EDN#1, T-NSCE server @ EDN#2, VAL Server, and Slice Provisioning MnS @OAM.](45578bd3ed11d45af63ce00e28bab2f8_img.jpg) + +``` + +sequenceDiagram + participant VAL_client as VAL client + participant NSCE_client as NSCE client + participant 5GC + participant S_NSCE_server as S-NSCE server @ EDN#1 + participant T_NSCE_server as T-NSCE server @ EDN#2 + participant VAL_Server as VAL Server + participant Slice_Provisioning as Slice Provisioning MnS @OAM + + Note left of VAL_client: VAL client and NSCE client + VAL_Server->>S_NSCE_server: 1. Application service continuity requirement request + S_NSCE_server->>5GC: 2. Query network/slice conditions at target area + S_NSCE_server->>Slice_Provisioning: 3. Query MD capabilities / slice config parameters at target area + Note right of S_NSCE_server: 4. Determine the need for slice related lifecycle change and generate a trigger action based on the predicted VAL application mobility + S_NSCE_server->>Slice_Provisioning: 5a. Slice modification trigger request + Slice_Provisioning->>S_NSCE_server: 5b. Slice modification trigger response + Note left of 5GC: 6. NSCE client association from S-NSCE server to T-NSCE server (NSCE session re-establishment, modification) + +``` + +Sequence diagram illustrating the support for predictive slice modification in distributed NSCE server deployments. The diagram shows interactions between VAL client, NSCE client, 5GC, S-NSCE server @ EDN#1, T-NSCE server @ EDN#2, VAL Server, and Slice Provisioning MnS @OAM. + +**Figure 6.21.1.2-1: Support for predictive slice modification in distributed NSCE server deployments** + +- 1a/1b. The VAL server sends to S-NSCE server a VAL application service continuity requirement due to predicted/expected UE or group UE mobility to an area covered by a different EDN. Such UE predicted mobility can be based on analytics received by NWDAF or ADAES or can be predicted by the VAL layer (VAL server or VAL UE). +2. S-NSCE server acting as AF, may interact with 5GC to query the UE specific information (location, UE connection capabilities) as well as network conditions (network monitoring from NEF) and/or slice related analytics on the slice load (from NWDAF as specified in TS 23.288). + +3. S-NSCE server may also interact with OAM to query on the up to date configured slice parameters e.g. slice RRM policies, modification of the NSI/NSSI resources (see TS 28.531[5], 5.1.12) at the target area and measurements for the slice at the target area. +4. S-NSCE server checks whether new NSCE service area supports slice #1 and if slice #1 offers similar performance in target area. Here we assume that the S-NSCE is aware of the per application QoS requirements / KPIs (or has acquired this information from the VAL server). + +If the current slice doesn't fulfil these requirements, S-NSCE interacts with T-NSCE server (by sending the VAL application service continuity requirement and optionally a proposed action) to negotiate and jointly determine the need for a slice lifecycle change at the target area and translates this to a trigger action towards OAM (slice provisioning MnS producer). This trigger action can be the outcome of the negotiation and can be a requested slice modification or the slice #1 creation/instanciation at the target area (this may happen if a group of UEs are moving to the target area and use slice #1, so it may be beneficial to create slice #1 at the target area). Such trigger action can be generated by either the S-NSCE server or the T-NSCE server based on the deployment. + +- 5a/b. Then, S- or T-NSCE server may send the trigger action to the slice provisioning MnS at OAM (e.g. slice modification for network slice) based on the expected/predicted VAL UE or VAL group mobility. Following the MnS provides a response with a positive or negative result. +6. After the slice lifecycle change execution (based on the indication in 5b), if the NSCE client needs to be remapped to different NSCE server (due to the expected change of UE location), the NSCE client establishes a new connection with T-NSCE and terminates the one with S-NSCE (in case of subscription-based interaction), or in case of request-based interaction, it updates the mapping at the client side, and maintains the new NSCE server address / ID and may also request for report configuration information for the target NSCE area. + +### 6.21.2 Solution evaluation + +The solution addresses the key issue #12 on network slice capability exposure in the edge data network, and in particular the interaction between NSCE servers (deployed at different EDNs) when an expected migration happens for a UE or group of UEs from an EDN to another. Solution #X requires interaction with 5GC (acting as trusted AF) for querying network/slice condition at the target area and the interaction with OAM / slice provisioning MnS producer for consuming OAM services. + +The solution is feasible and viable mainly for the NSaaS scenario (where the NSCE server is the NSP and the VAL server is the NSC) and proposes the enhancement NSCE server capabilities to deal with scenarios when NSCE servers are deployed at the edge / distributed and a trigger can be related to UE/group predicted mobility from one edge area to another. + +## 6.22 Solution #22: Slice policy and configuration alignment + +### 6.22.1 Solution description + +#### 6.22.1.1 General + +This solution addresses the KI 11 bullet on resolving misalignments between VAL server policy (e.g., requirements provided when adding or changing slice) and the NSCE service provider policy (NSPP). + +The VAL server policy can be in the form of a profile or configuration which the VAL server requests to be applied or maintained by NSCE, e.g., a profile including the configuration of several services using the same network slice. Alternatively, the VAL server policy can be provided together with the request for an action, e.g., adding a network slice. When the action requested also includes a VAL server policy to be applied, it needs to be aligned with the existing network slice policies available at NSCE i.e., NSPPs. + +#### 6.22.1.2 Procedure + +Figure 6.22.1.2 illustrates the procedure for slice policy and configuration alignment + +Pre-conditions: + +1. The NSCE service provider policy (NSPP) is available at the NSCE Server. + +NOTE 1: It is assumed that NSPP includes ranges of NS capabilities which can be adapted via NSCE, along with conditions under which such adaptations are allowed. This policy is used by NSCE also in other TR solutions to determine whether parameters in NS management operations are within allowed ranges, e.g., clause 6.10.2.1 step 10, fig 6.11.1.2-1 steps 2 and/or 3, fig 6.11.1.2-2 steps 2 and/or 3, clause 6.13.1.2 step 3, clause 6.13.1.2 step 3, clause 6.17.1.2 step 5., clause 6.19.1.2 step 5., etc. + +2. The VAL server is authorized to receive NSCE services. + +![Sequence diagram illustrating Policy alignment between VAL server, NSCE server, and 5GS.](350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg) + +``` + +sequenceDiagram + participant VAL server + participant NSCE server + participant 5GS + Note right of NSCE server: 2. Compare and harmonize + VAL server->>NSCE server: 1. Provisioning or action request (VAL policy) + NSCE server-->>VAL server: 3. Response + NSCE server-->>5GS: 4. Indication + +``` + +The diagram shows a sequence of interactions between three entities: VAL server, NSCE server, and 5GS. + 1. The VAL server sends a 'Provisioning or action request (VAL policy)' to the NSCE server. + 2. The NSCE server performs an internal 'Compare and harmonize' step. + 3. The NSCE server sends a 'Response' back to the VAL server. + 4. The NSCE server sends an 'Indication' to the 5GS. + +Sequence diagram illustrating Policy alignment between VAL server, NSCE server, and 5GS. + +**Figure 6.22.1.2: Policy alignment** + +1. VAL server sends a provisioning or action request to NSCE server. The request contains the VAL policy. + +NOTE 2: The request in this step is described generically and can correspond to one or more requests to be defined in the normative phase to support other solutions. For example, the request corresponds to clause 6.1.1.2 step 1, clause 6.9.1.2 step 1, clause 6.10.1.2 step 8, clause 6.11.1.1 step 1, clause 6.11.1.2 step 1, clause 6.13.1.2 step 2, clause 6.17.1.2 step 1 etc. The response in step 3 is to be defined in a complementary manner. + +2. The NSCE server checks whether the provided VAL policy conflicts with the NSCE service provider policy. If not, the action requested, if any, is performed. + +If the VAL policy conflicts with the NSCE service provider policy, the NSCE server can determine parameters harmonizing the two configurations. The NSCE server determines parameters harmonizing the configurations if previously authorized. + +NOTE 3: In the normative phase, this step can be implemented, for example, as part of the following: clause 6.1.1.2 steps 2, 6 or 9, clause 6.10.2.1 step 10, fig 6.11.1.2-1 steps 2 and/or 3, fig 6.11.1.2-2 steps 2 and/or 3, clause 6.13.1.2 step 3, clause 6.13.1.2 step 3, clause 6.17.1.2 step 5., clause 6.19.1.2 step 5., etc. + +3. NSCE server sends the VAL server a response indicating whether the VAL policy conforms with NSPP. If the policies conflicted, the NSCE server provides optional parameters values that allow the policies to be harmonized. If the policies did not conflict, the response indicates that there is alignment. If an action was also requested in step 1, the result of the action can be provided in the response. + +4. The NSCE Server can provide a notification to 5GS with the result of the compare and harmonize procedure. + +NOTE 4: In the normative phase the specification of this step is to be aligned with SA5 specifications + +### 6.22.2 Solution evaluation + +The solution addresses key issue #11 on slice requirement alignment by addressing misalignments between VAL server policy (e.g., requirements provided when adding or changing slices) and the NSCE service provider policy. The solution provides clarity to the how requirements and parameters from the two different domains may be harmonized/aligned, in order to allow other NSCE functions to be performed. + +In the normative phase, this solution can be used to provide clarifications and enhancements to a number of procedures. Alternatively, this solution can be implemented as a stand-alone process similar to the one described in clause 6.19., with the slice requirement updates resulting mainly from interactions between VAL Server and NSCE Server (not from interactions between NSCE and EGMF, as captured in the clause 6.19. solution), + +The solution in this clause can be used to enhance request/response messaging and procedural steps specified within the scope of other solutions. Therefore, the solution is feasible and can be used to complement other key issues. + +# --- 7 Identities and commonly used values + +## 7.1 General + +The following clauses list identities and commonly used values that are used in this technical report. + +## 7.2 VAL server ID + +The VAL server ID uniquely identifies the VAL server. + +## 7.3 NSCE server ID + +The NSCE server ID uniquely identifies the Network Slice Capability enablement server. + +## 7.4 NSCE client ID + +The Network Slice Capability enablement client ID identifies a particular NSCE client. + +## 7.5 VAL client ID + +The VAL Client ID identifies the client side of a particular vertical application. + +In case that the UE is running mobile OS, the Application Client ID is a pair of OSId and OSAppId. + +## 7.6 UE ID + +The UE ID uniquely identifies a particular UE within a PLMN domain. Following identities can be used: + +- GPSI, as defined in 3GPP TS 23.501 [02]. + +## 7.7 slice coverage area + +The slice coverage area is the area where the network slice is available in the whole PLMN or in one or more Tracking Areas of the PLMN. + +## 7.8 NSCE service area + +The NSCE service area is the area where the Network Slice Capability Enablement server owner provides its services. It is equal to the collection of coverage area of slices it can enable. + +The NSCE service area can be expressed as a Topological Service Area (e.g. a list of TA), a Geographical Service Area (e.g. Geographical coordinates) or both. + +NOTE: The NSCE server service area is not smaller than the collection of slice(s) coverage area(s) the NSCE server can enable. + +# 8 Overall evaluation + +## 8.1 General + +The following clauses contain an overall evaluation of the solutions presented in this technical report, their applicability to the identified key issues and dependencies on other working groups which will need consideration. + +## 8.2 Solution evaluations + +### 8.2.1 General + +All the key issues and solutions specified in this technical report are listed in Table 8.2.1-1. It includes the mapping of the key issues to the solutions and corresponding solution evaluations. It also lists the dependencies on other working groups that will need consideration during the Release 18 normative phase. + +**Table 8.2.1-1: Key issue and solutions** + +| Key issues
(evaluation clause reference) | Solution | Dependency
on other
working
groups | +|------------------------------------------------------------------------|---------------------------------------------------------------------------------|---------------------------------------------| +| KI 1: Network slice capability management enhancements | Solution 12: SEAL enhancement | | +| | Solution 15: UE triggered network slice adaptation | | +| | Solution 16: Multi-Network slice management capability | | +| | Solution 17: Multi-Network slice resource optimization | | +| KI 2: Application layer exposed network slice lifecycle management | Solution 1: Automatic application layer network slice management | | +| KI 3: Discovery & registration aspects for management service exposure | Solution 7: Network slice capability registration | | +| | Solution 8: Discovery of management service exposure | SA 5 | +| KI 4: Network slice fault management capability | Solution 2: Network slice fault management capability | | +| KI 5 : Communication service management exposure | Solution 11 :Communication service management exposure | | +| KI 6: Application layer QoS verification capability enablement | Solution 4: QoS verification capability | | +| KI 7: Network slice related performance and analytics exposure | Solution 5: Network slice related performance and analytics exposure | | +| KI 8: Support for requirements translation | Solution 3: Slice API configuration and translation | SA 5 | +| KI 9: Support for trust enablement | Solution 6: VAL server authorization and authentication via slice enabler layer | SA 3 | +| KI 10: Support for managing trusted third-party owned application(s) | Solution 9: Support for managing trusted third-party owned application(s) | SA 2 | +| | Solution 10: Network slice application policy management capability | | +| | Solution 20: Network slice optimization based on AF policy | | + +| | | | +|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--| +| KI 11: Slice requirement alignment | Solution 19: Slice requirements alignment capability | | +| KI 12: Network slice capability exposure in the edge data network | 6.14 Solution 14: Interaction between the NSCE servers. | | +| | Solution 21: Solution on predictive slice modification in edge based NSCE deployments | | +| KI 13: Delivery of the existing Network Slice information to the trusted third-party | Solution 18: Network Slice Information Delivery | | +| KI 14: Network Slice creation to the third-party and UE | Solution 13: Network Slice Allocation by VAL server | | + +### 8.2.2 Overall Evaluation for KI#1 + +This clause provides an overall evaluation of the key issue #1 Network slice capability management enhancements. + +The Solution #12 analyzes potential new services that could enhance the SEAL and the potential enhancement to SEAL NSCE architecture. + +The solution #15 provides enhancements to the existing NSCE client functionality by separating the network slice adaptation subscription/notification functionality from the slice adaption triggering. + +The solution #16 and solution #17 provides enhancements to the NSCE functionality by supporting the NSCE services including the network slice monitoring and network slice optimization in multi-Networks. Detailed signalling and APIs of making multiple networks resource adjustment and slice monitoring are to be addressed in normative phase. + +Solution #15, solution #16 and solution #17 could be considered in the normative work. + +### 8.2.3 Overall Evaluation for KI#10 + +This clause provides an overall evaluation of the key issue #10 supporting for managing trusted third-party owned application(s). + +Solution #9 provides a possible procedure of the VAL server requesting to manage network slice quota by providing specific type of action to take (e.g. release low priority users as identified by 5GC, release list of users as identified by the VAL server, etc) and optionally list of UEs on which specific action to apply to NSCE Server. While SA2 has no mechanisms for AF managing UEs with different qualities/priority level within a slice. + +The Solution #10 illustrates the process of the VAL server requesting to manage network slice when reaching UEs slice quota threshold. The slice adjustment is mainly to modify the network slice and the decision is made based on network status information from 5GS. + +Solution #20 illustrates the process of optimizing the network slice (modify the network slice ) based on policy of application, which could be triggered by not only predicted network slice status, but also network slice management data. + +The solution #10 and solution#20 could be considered to be merged during the normative work, and the detailed APIs are to be addressed in normative phase. + +### 8.2.4 Overall Evaluation for KI#12 + +This clause provides an overall evaluation of the key issue #12 Network slice capability exposure in the edge data network. The solution #14 and solution #21 are complementary to each other. + +The solution #14 is applicable when the monitoring of network slice supported by different edge deployed NSCE servers is needed to form an overview of the whole network. + +The solution #21 is to optimize the application performance when the one or more UEs is predicted to migrate between different NSCE server. + +Both solutions need the support of interaction between the NSCE servers, and the detailed API could be considered in the normative work. + +## 8.3 Architecture evaluations + +The architecture specified in clause 4.2 describes the application architecture for network slice capability enablement. + +A summary of the architecture and key issues specified in this technical report are listed in Table 8.3-1. + +**Table 8.3-1: Architecture evaluation** + +| Architecture solution | Applicable key issues (clause reference) | Dependency on other working groups | +|--------------------------------------------------------------------|-----------------------------------------------|------------------------------------| +| 4 Application architecture for network slice capability enablement | Supports all key issues specified in clause 5 | SA2 and SA5 | + +The architecture is compliant to all the architectural requirements listed under clause 4.1. + +# --- 9 Conclusions + +This technical report fulfills the objectives of the study on application architecture for enabling Network Slice Capability Exposure. The report includes the following: + +1. Definition of terms and abbreviations used in the study (clause 3); +2. Architectural requirements and detailed application architecture for enabling Network Slice Capability Enablement (clause 4); +3. Deployment model and business model in Annex +3. Key issues identified by the study (clause 5); +4. Individual solutions addressing the key issues (clause 6); +5. A list of identities and commonly used values (clause 7); and +6. Overall evaluations of all the solutions (clause 8); + +Some of the individual solutions have dependency on other working groups within 3GPP. This dependency is summarized in overall evaluations (clause 7). + +For NSCALE in normative work in 3GPP Rel-18, it is recommended to define: + +1. Terms and abbreviations, the definition of terms and abbreviations captured in clause 3 will be reused; +2. Common attributes/parameters provided by NSCE, the list of identities and commonly used values captured in clause 7 will be reused with appropriate enhancements; +3. Requirements on NSCE, the architectural requirements identified in clause 4 will be used as baseline architectural requirements; +4. Application architecture for enabling Network Slice Capability Exposure, the architectures as specified in clause 4 will be used as baseline architecture; +5. APIs and attributes/parameters thereof provided by NSCE, following individual solutions, corresponding to the key issues, will be considered as candidate solutions: + - a. for Key issue #2 (Application layer exposed network slice lifecycle management): + - i. Solution #1 (Automatic application layer network slice management); + +- b. for Key issue #3 (Discovery & registration aspects for management service exposure): + - i. Solution #7 (Network slice capability registration); + - ii. Solution #8 (Discovery of management service exposure); +- c. for Key issue #4 (Network slice fault management capability): + - i. Solution #2 (Network slice fault management capability); +- d. for Key issue #5 (Communication service management exposure): + - i. Solution #11 (Communication service management exposure); +- e. for Key issue #6 (Application layer QoS verification capability enablement): + - i. Solution #4: QoS verification capability; +- f. for Key issue #7 (Network slice related performance and analytics exposure): + - i. Solution #5 (Network slice related performance and analytics exposure); +- g. for Key issue #8 (Support for requirements translation): + - i. Solution #3 (Slice API configuration and translation); +- h. for Key issue #9 (Support for trust enablement): + - i. Solution #6 (VAL server authorization and authentication via slice enabler layer); +- i. for Key issue #10 (Support for managing trusted third-party owned application(s)): + - i. Solution #10 (Network slice application policy management capability); + - ii. Solution #20(Network slice optimization based on AF policy); +- j. for Key issue #11 (Slice requirements alignment): + - i. Solution #19 (Application layer slice SLA alignment); +- k. for Key issue #12 (Network slice capability exposure in the edge data network): + - i. Solution #14 (Interaction between the NSCE servers); + - ii. Solution #21 (Predictive slice modification in edge based NSCE deployments); +- l. for Key issue #1 (SEAL enhancement): + - i. Solution #15 (UE triggered network slice adaptation) + - ii. Application architecture; + - iii. Solution #16 (Multi-Network slice management capability); + - iv. Solution #17 (Multi-Network slice resource optimization); +- m. for Key issue #14 (Network Slice creation to the third-party and UE): + - i. Solution #13 (Network Slice Allocation by VAL server); +- n. for Key issue #13 (Delivery of the existing Network Slice information to the trusted third-party): + - i. Solution #18 (Network Slice Information Delivery). + +Since solution #9 (Support for managing trusted third-party owned application(s)) is not technically viable currently, so it is recommended solution#9 shall not move forward to normative phase. + +Individual solutions, not listed under bullet 5 may be adopted in technical specification with appropriate enhancements; + +6. Potential enhancement of SEAL services, the enhancement to the SEAL service is summarized in solution 12. The normative work of SEAL enhancement will take solution 12 and the conclusion of corresponding solutions into consideration. + +# Annex A Deployment models + +## A.1 Deployment scenarios + +### A.1.1 General + +In addition to SA2 and SA5 network slicing capabilities, the NSCE service provides application layer enablement to support the network slice management and control in the granularity of slice which is identified by S-NSSAI. + +A network slice can have only one owner and one NSCE service provider. NSCE service provider and slice owner can be different. For example the slice owner is VAL server, but the NSCE service provider is MNO. + +This clause describes examples of deployment models with respect to different deployment scenarios as follows. + +### A.1.2 Centralized NSCE deployment + +Figure A.1.2 shows a fundamental deployment of NSCE server whose service area covering the whole PLMN. It is also possible slice coverage area to be smaller than the NSCE service area. One NSCE server can also be responsible for local slices covering only small service areas. + +The network slice capability enablement service is provided with the view of whole PLMN in this scenario. + +![Figure A.1.2: Illustration of centralized NSCE deployment. The diagram shows a 'VAL server(s)' box above an 'NSCE server #1' box. Below these is a large box labeled 'PLMN' containing a grid. The grid has columns for 'S-NSSAI-1', '...', and 'S-NSSAI-N'. Rows are labeled '5GC' and 'RAN'. To the left of the grid is an 'OAM' box. A dashed line labeled 'NSCE service area' encompasses the entire PLMN box.](d074df4244ecf1bcd74fc55886a902f9_img.jpg) + +Figure A.1.2: Illustration of centralized NSCE deployment. The diagram shows a 'VAL server(s)' box above an 'NSCE server #1' box. Below these is a large box labeled 'PLMN' containing a grid. The grid has columns for 'S-NSSAI-1', '...', and 'S-NSSAI-N'. Rows are labeled '5GC' and 'RAN'. To the left of the grid is an 'OAM' box. A dashed line labeled 'NSCE service area' encompasses the entire PLMN box. + +Figure A.1.2: Illustration of centralized NSCE deployment + +### A.1.3 Distributed NSCE deployment + +The distributed deployment refers to the deployment model in which the service area only covers some specific areas as shown below (based on geographical coordinates or TA list(s)). + +![Figure A.1.3: Illustration of distributed NSCE deployment. The diagram shows two identical server stacks ('VAL server(s)' above 'NSCE server') labeled '#1' and '#2'. Each stack is connected to a 'PLMN' box. The first PLMN box contains a grid for 'S-NSSAI-1' to 'S-NSSAI-N' with '5GC' and 'RAN' rows, and an 'OAM' box. The second PLMN box contains a grid for 'S-NSSAI-N+1' to 'S-NSSAI-N+M' with '5GC' and 'RAN' rows, and an 'OAM' box. A dashed line labeled 'NSCE service area' covers only the first PLMN box.](804d0a82d8a6692f2115c8a216a54d15_img.jpg) + +Figure A.1.3: Illustration of distributed NSCE deployment. The diagram shows two identical server stacks ('VAL server(s)' above 'NSCE server') labeled '#1' and '#2'. Each stack is connected to a 'PLMN' box. The first PLMN box contains a grid for 'S-NSSAI-1' to 'S-NSSAI-N' with '5GC' and 'RAN' rows, and an 'OAM' box. The second PLMN box contains a grid for 'S-NSSAI-N+1' to 'S-NSSAI-N+M' with '5GC' and 'RAN' rows, and an 'OAM' box. A dashed line labeled 'NSCE service area' covers only the first PLMN box. + +Figure A.1.3: Illustration of distributed NSCE deployment + +Examples of distributed deployment including NPN NSCE deployment and edge NSCE deployment which are shown below in A.1.3.1 and A.1.3.2. + +When there are multiple NSCE servers managed by same provider, NSCE server(s) may be subscribed for providing the network slice statistics to another NSCE server to provide a global view. + +There can be two use cases to provide the NSCE service in the distributed deployment: + +One use case is that the edge/NPN deployed NSCE is about a slice service area which is equivalent to the edge/NPN area. For this scenario, if the edge/NPN deployed NSCE wants to access the NEF/NWDAF/NSACF services or to receive policies from OAM, it needs to interact to the global NSCE. + +A further use case could be that some NSCE services (e.g. MnS discovery) are locally provided to edge -native VAL servers (for example as a micro-service), whereas other capabilities are provided for the whole PLMN area. So, the edge/NPN NSCE includes a subset of capabilities which are edge native. The local deployment of such capabilities can allow for more efficient services to the edge deployed VAL servers (e.g. for QoS verification, the edge deployed NSCE can receive more timely KQI/QoE measurements and can process them locally before triggering an event). + +#### A.1.3.1 NPN NSCE deployment + +Figure X.1.3.1 shows the NPN NSCE server deployment. This case is valid if a geographical match between slice coverage area, NPN coverage area and NSCE service area is pre-configured. The matching may be pre-configured by network operator based on the TA list. The service area of the NSCE server equals to the area of the NPN in this case. The slice(s) coverage area may equals to the area of the NPN, but it is also possible slice coverage area to be smaller than the NPN service area. + +The NSCE server is deployed in Non-public network to provide the network slice capabilities exposure application service based on the interaction with NPN-5GC and NPN-OAM. + +![Diagram illustrating NPN NSCE deployment. A large light green rectangle represents the 'NSCE service area'. Inside it, a smaller rectangle labeled 'NPN#1' contains two stacked green boxes: 'VAL server(s)#1' on top and 'NSCE server #1' below. Below these boxes, a dashed line separates them from a section labeled 'S-NSSAI-1 | ... | S-NSSAI-N'. At the bottom, a green box is divided into two rows: 'NPN-5GC' and 'NPN-RAN'. To the left of this box, a vertical label 'NPN - OAM' is present.](0adcd19063a66145a465add40bf956e6_img.jpg) + +Diagram illustrating NPN NSCE deployment. A large light green rectangle represents the 'NSCE service area'. Inside it, a smaller rectangle labeled 'NPN#1' contains two stacked green boxes: 'VAL server(s)#1' on top and 'NSCE server #1' below. Below these boxes, a dashed line separates them from a section labeled 'S-NSSAI-1 | ... | S-NSSAI-N'. At the bottom, a green box is divided into two rows: 'NPN-5GC' and 'NPN-RAN'. To the left of this box, a vertical label 'NPN - OAM' is present. + +Figure A.1.3.1: Illustration of NPN NSCE deployment + +#### A.1.3.2 Edge NSCE deployment + +Figure X.1.3.2 shows the edge NSCE deployment cases when the NSCE server is deployed in the EDN using LADNs as described in Annex A.2.4 of TS 23.558[x]. This case is valid if a geographical match between slice coverage area, LADN service area (which is EDN service area) and NSCE service area is pre-configured. The matching can be based on the TA list or geographical coordinates. The service area of the NSCE server equals to the area of the LADN in this + +case. The slice(s) coverage area may equals to the area of the LADN(EDN), but it is also possible slice coverage area to be smaller than the LADN(EDN) service area. + +The NSCE server is deployed in EDN to provide the network slice capabilities exposure application service based on the interaction with EDN-5GC and EDN-OAM. + +![Figure A.1.3.2: Illustration of edge NSCE deployment. The diagram shows an EDN#1 box containing 'VAL server #1' and 'NSCE server #1'. To the left of the EDN box is a light green box labeled 'NSCE service area'. Below the EDN box is a dashed box labeled 'LADN service area'. Inside the LADN service area, there are two rows: 'ED N-5GC' and 'OA M-LADN-EDN-RAN'. Above these rows, within the LADN service area, are labels 'S-NSSAI-1 ... S-NSSAI-N'.](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +Figure A.1.3.2: Illustration of edge NSCE deployment. The diagram shows an EDN#1 box containing 'VAL server #1' and 'NSCE server #1'. To the left of the EDN box is a light green box labeled 'NSCE service area'. Below the EDN box is a dashed box labeled 'LADN service area'. Inside the LADN service area, there are two rows: 'ED N-5GC' and 'OA M-LADN-EDN-RAN'. Above these rows, within the LADN service area, are labels 'S-NSSAI-1 ... S-NSSAI-N'. + +Figure A.1.3.2: Illustration of edge NSCE deployment + +## A.2 Deployment of NSCE server(s) in relation to VAL server and 3GPP system + +To support the centralized/distributed, the NSCE server(s) will have different deployment models and different relation with VAL server and 3GPP system. This clause describes examples of deployment models of NSCE server(s) in relation to VAL server and 3GPP system. + +Figure X.2-1 illustrates the centralized NSCE deployment. The NSCE server can be deployed in PLMN domain by MNO, or deployed in VAL service provider domain by vertical. + +![Figure A.2-1: Illustration of centralized NSCE deployment. This is a vertical block diagram. At the top is a box labeled 'VAL server(s)'. Below it is a box labeled 'NSCE server'. At the bottom is a box labeled '3GPP network system'. The connection between VAL server(s) and NSCE server is labeled 'NSCE-S'. The connection between NSCE server and 3GPP network system is labeled 'Network interface'.](5ec2b6e9c9133bfbb26789d85dc49774_img.jpg) + +Figure A.2-1: Illustration of centralized NSCE deployment. This is a vertical block diagram. At the top is a box labeled 'VAL server(s)'. Below it is a box labeled 'NSCE server'. At the bottom is a box labeled '3GPP network system'. The connection between VAL server(s) and NSCE server is labeled 'NSCE-S'. The connection between NSCE server and 3GPP network system is labeled 'Network interface'. + +Figure A.2-1: Illustration of centralized NSCE deployment + +Figure A.2-2 illustrates the distributed NSCE deployment. The NSCE servers can be deployed in PLMN domain by MNO, deployed in VAL service provider domain by vertical, or deployed in 3rd party domain by 3rd party. The VAL + +server can communicate with multiple NSCE servers via NSCE-S as long as other NSCE servers are discovered and accessible. Or, the VAL server can communicate with other NSCE servers via NSCE-E if needed. + +![Diagram illustrating distributed NSCE deployment. At the top is a 'VAL server(s)' box. Below it are two 'NSCE server' boxes. The VAL server(s) is connected to both NSCE servers via 'NSCE-S' interfaces. The two NSCE servers are connected to each other via an 'NSCE-E' interface. Each NSCE server is connected to a '3GPP network system' box at the bottom via a 'Network interface'.](1c79f31a718d63814feb28ab46f64f19_img.jpg) + +``` + +graph TD + VAL[VAL server(s)] -- NSCE-S --> NSCE1[NSCE server] + VAL -- NSCE-S --> NSCE2[NSCE server] + NSCE1 -- NSCE-E --> NSCE2 + NSCE1 -- Network interface --> 3GPP[3GPP network system] + NSCE2 -- Network interface --> 3GPP + +``` + +Diagram illustrating distributed NSCE deployment. At the top is a 'VAL server(s)' box. Below it are two 'NSCE server' boxes. The VAL server(s) is connected to both NSCE servers via 'NSCE-S' interfaces. The two NSCE servers are connected to each other via an 'NSCE-E' interface. Each NSCE server is connected to a '3GPP network system' box at the bottom via a 'Network interface'. + +**Figure A.2-2: Illustration of distributed NSCE deployment** + +# Annex B (informative): Business models and relationships for NSSCALE + +## Annex B.1: Relevance to SA5 models + +According to TS 28.530, the roles related to 5G networks and network slicing management include among others: + +- Communication Service Provider (CSP): Provides communication services. Designs, builds and operates its communication services. The CSP provided communication service can be built with or without network slice. +- Communication Service Customer (CSC): Uses communication services. +- Network Operator (NOP): Designs, builds and operates networks and provides related services, including network services and network slices. + +Also, according to TS 28.530: "In case of Network Slice as a Service (NSaaS) (cf. clause 4.1.6), the Communication Service Provider (CSP) role can be refined into NSaaS Provider (NSaaSP) role – or, in short, Network Slice Provider (NSP) - and the Communication Service Customer (CSC) role can be refined into NSaaS Customer (NSaaSC) role – or, in short, Network Slice Customer (NSC). A NSC can, in turn, offer its own communication services to its own customers, being thus CSP at the same time. A tenant might take the role of a NSC." + +Figure 4.1.6.1 of TS 28.530 illustrates some examples on how network slices can be utilized to deliver communication services, including network slice as a Service. For simplicity this figure omits the details of how NFs are being managed and does not show their groupings into network slice subnet: + +- a) A Network Slice as a Service (NSaaS) is provided to CSC-A by CSP-A. Unlike the communication service delivered to end customers, in NSaaS, the offered service is the actual network slice. +- b) CSC-A can use the network slice obtained from CSP-A to support own Communication Services or may add additional network functions to the obtained NSaaS and offer the resulting combination as a new network slice to CSP-B. In this case, CSC-A plays the role of NOP-B and builds his own network. The network slice obtained by CSC-A from CSP-A becomes a "building block" or a network slice subnet of CSC-A in its role of NOP-B. The NOP-B (a.k.a. CSC-A) combines this network slice subnet with other network slice subnets and offers the new network slice subnet as network slice to CSP-B. +- c) CSP-B can use the network slice obtained from CSC-A / NOP-B to deliver communication services to its end customers (as CSC-B). + +![Figure 4.1.6.1: Examples of Network Slice as a Service (NSaaS) being utilized to deliver communication services to end customers. The diagram is split into two parts, (a) and (b), each showing a 'Management view' and a 'Network view'. In part (a), the Management view shows CSP-A (top) with NSaaS, which offers to NOP-A (bottom) with NS. An arrow labeled 'associates' points from NS to a central NS. In part (b), the Management view shows CSP-B (top) with CS, which offers to CSC-B (top right) and CSC-A / NOP-B (bottom right) with NS. An arrow labeled 'offer' points from CS to CSC-B. Both parts show a Network view with NF (Network Function) blocks and a DN (Data Network) block. In (a), the Network Slice is shown as a shaded area containing two NF blocks. In (b), the Network Slice is shown as a shaded area containing two NF blocks and a DN block. Arrows connect the Management view components to the Network view components.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Figure 4.1.6.1: Examples of Network Slice as a Service (NSaaS) being utilized to deliver communication services to end customers. The diagram is split into two parts, (a) and (b), each showing a 'Management view' and a 'Network view'. In part (a), the Management view shows CSP-A (top) with NSaaS, which offers to NOP-A (bottom) with NS. An arrow labeled 'associates' points from NS to a central NS. In part (b), the Management view shows CSP-B (top) with CS, which offers to CSC-B (top right) and CSC-A / NOP-B (bottom right) with NS. An arrow labeled 'offer' points from CS to CSC-B. Both parts show a Network view with NF (Network Function) blocks and a DN (Data Network) block. In (a), the Network Slice is shown as a shaded area containing two NF blocks. In (b), the Network Slice is shown as a shaded area containing two NF blocks and a DN block. Arrows connect the Management view components to the Network view components. + +**Figure 4.1.6.1: Examples of Network Slice as a Service (NSaaS) being utilized to deliver communication services to end customers [TS 28.530]** + +**[Observation B.1-1]** For the NSaaS model, NSCE can be defined as an NSC of the NSP, which in turn offers its own communication services to its own customers, being thus CSP at the same time. + +**[Observation B.1-2]** A Network Slice in NSaaS model can be combined with additional functions, and a new slice can be provided by the CSC-A which acts as NOP-B. In such model, the NSCE server can provide enablement services for the new slice provided by the NOP-A customer. + +**[Observation B.1-3]** It is not necessary that the NOP-B "slice parameters" are the same as the NOP-A "slice parameters"; hence the slice areas for the resulting slice can be different from the slice area provided by NOP-B/CSC-A. + +TS 28.530 also specifies the "network slices as NOP internals" model. In this model, the network slices are not part of the NOP service offering and hence are not visible to its customers. However, the NOP, to provide support to communication services, may decide to deploy network slices, e.g. for internal network optimization purposes. This model allows CSC to use the network as the end user or optionally allows CSC to monitor the service status (assurance of the SLA associated with the internally offered network slice). The CSP should be able to provide the service status information (e.g. service performance, fault information, traffic data, etc) to CSC via the management exposure interface. + +![Diagram illustrating the network slice as NOP internals model. It shows three layers: Management view, Network view, and CSC. The Management view contains a CSP box with a CS circle, which is connected to a CSC box via an 'offer' arrow. Below the CSP box is a NOP box containing an NS circle. The Network view contains a Network Slice box with two NF boxes and a DN box. A dashed line connects the NS circle in the NOP box to the Network Slice box.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +The diagram illustrates the network slice as NOP internals model. It is divided into three horizontal layers. The top layer is labeled 'CSC' and contains a box labeled 'CSP' which in turn contains a circle labeled 'CS'. An arrow labeled 'offer' points from the 'CS' circle to the 'CSC' box. The middle layer is labeled 'Management view' and contains a shaded box labeled 'NOP' which contains a circle labeled 'NS'. A solid vertical line connects the 'CS' circle in the 'CSP' box to the 'NS' circle in the 'NOP' box. The bottom layer is labeled 'Network view' and contains a 3D box labeled 'Network Slice' which contains two boxes labeled 'NF' and a box labeled 'DN'. A dashed vertical line connects the 'NS' circle in the 'NOP' box to the 'Network Slice' box. + +Diagram illustrating the network slice as NOP internals model. It shows three layers: Management view, Network view, and CSC. The Management view contains a CSP box with a CS circle, which is connected to a CSC box via an 'offer' arrow. Below the CSP box is a NOP box containing an NS circle. The Network view contains a Network Slice box with two NF boxes and a DN box. A dashed line connects the NS circle in the NOP box to the Network Slice box. + +**Figure 4.1.7.1: Examples of network slice as NOP internals [TS 28.530]** + +**[Observation B.1-4]** For the network slices as NOP internals model, the NSCE server can be only defined as part of NOP to translate the slice specific requirements to communication service requirements and vice versa. + +## Annex B.2: Business relationships + +NSCE layer provides value added services to VAL customers, based on consuming 5GS services related to slicing (from OAM, 5GC) and based on interacting with the VAL UE side. The variety of services and the deployment aspects depend on the different assumptions for the slice owner / provider, the slice customer and the enablement service provider. With respect to NSSCALE, the NSCE server can play different roles based on the business models. For example, NSCE server can be: + +- deployed by NOP / MNO +- deployed by an Edge / Cloud Provider, as a trusted 3rd party +- deployed by a vertical industry, which can be the end slice customer + +From business perspective, if the NSCE server is not part of vertical or MNO, the following business model apply. In Figure X.2-1, the different interactions among all the involved entities are provided. More specifically, in this model the end user is the consumer of the applications provided by the vertical/ASP and can have app-level service agreement with vertical/ASP(s). The end user/UE also has a PLMN subscription arrangement with the MNO. The UE used by the end user is allowed to be registered on the MNO's network. MNO (via OAM) can have a slice SLA with the vertical / ASP, which is optional when vertical customer is the NSC. In addition, due to the involvement of a NSCE service provider, additional agreements can be possible between the NSCE server and VAL/ASP layer and the NOP/MNO(s): + +- the enablement service agreement between VAL/ASP layer and the NSCE service provider include the agreement on the value-added services, which in case on NSaaS these are services related to the consumed slice from NOP. So, the end customer (VAL) subscribes to NSCE server for receiving additional services for optimizing the slice utilization. In case that the NSCE server is a NSP towards VAL customer, then such agreement can relate to slice SLA (for the slice provided by the NSCE server). +- the service agreement between MNO and NSCE service provider is for consuming 5GS services (and being also authorized and trusted to provide additional services on top). Such agreement could be also a slice SLA for the scenarios when NSCE server is the NSC of the MNO (in NSaaS model). + +![Diagram showing business relationships between Vertical/ASP, End user/UE, Network Slice Capability Enabler (NSCE), and MNO.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +The diagram illustrates the business relationships between four entities: Vertical / ASP, End user / UE, Network Slice Capability Enabler (NSCE), and MNO. The relationships are as follows: + +- Vertical / ASP** and **End user / UE** are connected by a double-headed arrow labeled "App-level service agreement". +- Vertical / ASP** and **Network Slice Capability Enabler (NSCE)** are connected by a double-headed arrow labeled "Enablement service agreement". +- Network Slice Capability Enabler (NSCE)** and **MNO** are connected by a double-headed arrow labeled "Service agreement, Slice SLA". +- End user / UE** and **MNO** are connected by a double-headed arrow labeled "PLMN subscription arrangement". +- A dashed arrow labeled "slice SLA" points from **Vertical / ASP** to **MNO**. + +Diagram showing business relationships between Vertical/ASP, End user/UE, Network Slice Capability Enabler (NSCE), and MNO. + +Figure B.2-1: Business relationships + +# Annex C: Change history + +| Change history | | | | | | | | +|----------------|--------------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2021-07 | SA6#44-e | | | | | TR skeleton | 0.0.0 | +| 2021-07 | SA6#44-e | | | | | TR Skeleton agreed in SA6#44: S6-211848
Implemented pCRs approved in SA6#44: S6-211849, S6-211850, S6-211851, S6-211782
Editorial changes by the rapporteur | 0.1.0 | +| 2021-09 | SA6#45-e | | | | | Implemented pCRs approved in SA6#45: S6-212161, S6-212162, S6-212080, S6-212079, S6-211949, S6-211965, S6-211967, S6-212163, S6-212144, S6-212069
Editorial changes by the rapporteur | 0.2.0 | +| 2021-10 | SA6#45-bis-e | | | | | Implemented pCRs approved in SA6#45-bis: S6-212202, S6-212204, S6-212207, S6-212210, S6-212474, S6-212400
Editorial changes by the rapporteur | 0.3.0 | +| 2021-11 | SA6#46-e | | | | | Implemented pCRs approved in SA6#46: S6-212765, S6-212761, S6-212763, S6-212597, S6-212536, S6-212546, S6-212726, S6-212727, S6-212733, S6-212736, S6-212764, S6-212724, S6-212725, S6-212755, S6-212770;
Editorial changes by the rapporteur. | 0.4.0 | +| 2022-02 | SA6#47-e | | | | | Implemented pCRs approved in SA6#47: S6-220421, S6-220098, S6-220338, S6-220305, S6-220097, S6-220307, S6-220445, S6-220446, S6-220447, S6-220126, S6-220334, S6-220448, S6-220337, S6-220339, S6-220308, S6-220322.
Editorial changes by the rapporteur. | 0.5.0 | +| 2022-03 | SA#95-e | SP-220091 | | | | Presentation for information at SA#95-e | 1.0.0 | +| 2022-04 | SA6#48-e | | | | | Implemented pCRs approved in SA6#48: S6-220783, S6-220793, S6-220941, S6-220942, S6-220786, S6-220787, S6-220943, S6-220791, S6-220812, S6-220603, S6-220815, S6-220816, S6-220940
Editorial changes by the rapporteur. | 1.1.0 | +| 2022-05 | SA6#49-e | | | | | Implemented pCRs approved in SA6#49: S6-221454, S6-221281, S6-221053, S6-221063, S6-221341, S6-221291, S6-221292, S6-221293, S6-221294, S6-221295, S6-221296, S6-221297, S6-221455, S6-221456, S6-221151, S6-221314, S6-221348
Editorial changes by the rapporteur. | 1.2.0 | +| 2022-06 | SA6#49-bis-e | | | | | Implemented pCRs approved in SA6#49-bis: S6-221962, S6-221961, S6-221963, S6-221964, S6-221965, S6-221966, S6-221967, S6-221602, S6-221606, S6-221645, S6-221823, S6-221786, S6-221863 | 1.3.0 | +| 2022-09 | SA6#50-e | | | | | Implemented pCRs approved in SA6#49-bis: S6-222082, S6-222804, S6-222153, S6-222188, S6-222187, S6-222462, S6-222190, S6-222191, S6-222192, S6-222193, S6-222194, S6-222463, S6-222464, S6-222574
Editorial changes by the rapporteur. | 1.4.0 | +| 2022-09 | SA#97-e | SP-220911 | | | | Presentation for approval at SA#97-e | 2.0.0 | +| 2022-09 | SA#97-e | | | | | MCC editorial update for publication after TSG SA approval (SA#97) | 18.0.0 | +| 2022-12 | SA#98-e | SP-221246 | 0002 | | D | Correction of clause 4 | 18.1.0 | +| 2022-12 | SA#98-e | SP-221246 | 0003 | 1 | F | Evaluation of sol#9 | 18.1.0 | +| 2023-06 | SA#100 | SP-230706 | 0005 | | F | Solve the ENs | 18.2.0 | \ No newline at end of file diff --git a/raw/rel-18/23_series/23958/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/raw/rel-18/23_series/23958/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2916a6bef6c79bb75a6c208c2ca9b984a97f1e0 --- /dev/null +++ b/raw/rel-18/23_series/23958/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85d11f861ded5a94d5367d2af86caa5500ceafdc04c233f5012330fd7d1ac41e +size 63400 diff --git a/raw/rel-18/23_series/23958/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/raw/rel-18/23_series/23958/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa9385430ce069081a50f5058b8e68ab75131721 --- /dev/null +++ b/raw/rel-18/23_series/23958/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a3d6f60b0130bec239c87d56fa49ba00f5dbccfaa7485f2ed7a30386aeef7ae +size 91414 diff --git a/raw/rel-18/23_series/23958/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/raw/rel-18/23_series/23958/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b81609d3524607d795d225cac935fb254bbbd86e --- /dev/null +++ b/raw/rel-18/23_series/23958/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08c96f79d1e310697d99a966839ef2fe78bbdf4ec6ad76e1c7b59cff75acaed3 +size 9669 diff --git a/raw/rel-18/23_series/23958/64662465bba247703fdec49c8f3309f9_img.jpg b/raw/rel-18/23_series/23958/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af4341e854543dbfb07ec9430a84006b86fac3f7 --- /dev/null +++ b/raw/rel-18/23_series/23958/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04fe500bfef117d927121c8a48e6933b954a74d9d3230d5f971f0c93fe5be2c0 +size 5788 diff --git a/raw/rel-18/23_series/23958/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/raw/rel-18/23_series/23958/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acfedbb67fe547a807feb5e3d38afc071defdd36 --- /dev/null +++ b/raw/rel-18/23_series/23958/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:286406af93f7e2f08cbbd4f81a29b44a55a5471c12fc31065685f310e0b23e54 +size 86652 diff --git a/raw/rel-18/23_series/23958/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/raw/rel-18/23_series/23958/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..487f7ceee66f876a8470e9d4b0202a712b7da8d8 --- /dev/null +++ b/raw/rel-18/23_series/23958/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b1df5a5ce1e27b44b9a8507aea7cb6e57284a55aa0a47d92ebfc88384ae4d2c +size 35266 diff --git a/raw/rel-18/23_series/23958/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/raw/rel-18/23_series/23958/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59f5eb61019b54db379e9104a493ee8bd1bb99d3 --- /dev/null +++ b/raw/rel-18/23_series/23958/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d13a73ebe48b0c5b922e060bfaea083dd9c6aa831885752df618a311e769c775 +size 57600 diff --git a/raw/rel-18/23_series/23958/b90144cfbb81a2d610d920240fda689d_img.jpg b/raw/rel-18/23_series/23958/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fdc042bd994493b5cccef63f736a5270dd8240e --- /dev/null +++ b/raw/rel-18/23_series/23958/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea1e73ba806375f3a59f514935d4b73ae4c64350220d55c8fffe37eaf272a2d5 +size 73853 diff --git a/raw/rel-18/23_series/23958/dbe553cf16dd14073b89a8263a428664_img.jpg b/raw/rel-18/23_series/23958/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cee16d4b3f51729f810e48cef5011215b59e67e --- /dev/null +++ b/raw/rel-18/23_series/23958/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e97b84f0f5b3d74c6141ee070f3a432b64aef13fe7bbd7fac2585e7618e439dc +size 81609